Go to page: 1 2 3  Printer Friendly Version

Using STSADM -o export and STSADM -o import

In order to move things around you'll need to get a PRIME export of the site. This can be done with STSADM - o export with as little as the addition of -url and -filename, however, you'll probably want to add a few other options as well. Specifically, you'll want to add -includeusersecurity so that you can get the security information to move and -versions 4 so that all of the versions of the files are moved. There are other options which you can see by simply entering STSADM -o export at a command line.

On the import site, STSADM -o import needs at least the -url and -filename parameters, but you'll probably want to use an additional parameter, -updateversions 2, so that you can force the versioning in the new site to match the old site. Technically this shouldn't be necessary if you start with a blank site (as I'm recommending below), however, it's not a bad idea.

The basic idea for moving a site is that you export it. You then create a blank site in the place where you want to move the site to and then run the import process. This will result in a site at the new location that looks identical to the old one -- except for the limitations mentioned above.

The Third Parties

If you're not up for the limitations of the built in tools or want to reduce your testing workload you can look at third party strategies including AvePoint's suite of tools and Echo Technology's site replication technology.

Special thanks to Dan Evers (MSFT) who provided valuable input during the design phase and Susan Potter (MSFT) who was able to point me in the right direction on PRIME.

Go to page: 1 2 3  Printer Friendly Version