Welcome to Office Zealot Sign in | Join | Help

Quick Tutorial on Moving a WSS Site

I had someone ask me for instructions on moving a WSS site from one server to another.  There are a few options but the best (I think) is the stsadm utility.

Stsadme.exe is a command-line administration tool that is installed on all servers running WSS and SPS.  This tool performs numerous operations, including site-specific backup and restore functionality.

Here are the steps to move the WSS site.  Note, stsadm includes the restoration of all security as well.

1. On the source server, run the following command line action.  Wait for it to return an 'Operations completed successfully' message.  Depending on the amount of content and/or subsites, this sometimes takes a few seconds.

stsadm.exe -o backup -url http://myserver/sites/thesite -filename c:\stsadm_backup\thesite.dat -overwrite

... where 'myserver' is the server name, 'thesite' is the site you want to move, and c:\stsadm_backup exists as a valid path

Also, here's another trick... If the server balks at the reference to stsadm.exe (i.e. it can't find it).  Search for it on the server and drag and drop it into the cmd box.  You'll see that it has a fully qualified path of “c:\program files\common files\....\stsadm.exe”.

2. Copy the .dat file to a similar location (c:\stsadm_backup) on the destination server.

3. If you are using SPS and want to include the site in the Site Collection, create it (in name only) on the destination server as an empty site.  Note, if you don't do this, the restoration still works but the new site will not be in the Site Collection.

4. On the destination server, run the following command line action.  Wait for it to return an 'Operations completed successfully' message.  Depending on the amount of content and/or subsites, this sometimes takes a few seconds.

stsadm.exe -o restore -url http://myserver/sites/thesite -filename c:\stsadm_backup\thesite.dat -overwrite

5. That's it!  Your site is now moved to the destination server, content full and just as secure...

Published Thursday, March 02, 2006 5:32 AM by Mauro

Comments

Thursday, March 02, 2006 4:09 PM by Anonymous

# re: Quick Tutorial on Moving a WSS Site

You can mark this in the "just in case" category.

One thing that I have found in the past when moving sites is that from time to time GUID's get confused / forget to update.

If you find yourself staring at a screen full of errors where your wonderfully customized data-views should be that is likely the cause.

If that does happen you will want to:
Rename your template (.FWP/.STP) to a .CAB (You can view the contents of a .CAB)
Inside the .CAB file locate and open SCHEMA.XML
From there you can match and edit any mismatched GUID's
You will need cabarc (downloadable from MS) to put it back together.

Hopefully you never have to go through it but in the event that you do that should help get ya started.

Cheers,

Shane
Monday, October 02, 2006 12:12 PM by Anonymous

# re: Quick Tutorial on Moving a WSS Site

Hello,

I was just reading your blog about moving sites and had a few questions.
1. Does this save document versions, issue list history, etc.?

2. Will the URL change or stay the same?

3. Will it save information in a un-ghosted wss site and maintain the same look and feel?

The reason I'm asking these questions is because we are in the process of migrating 3 SPS Portals into one, along with all the WSS sites. We've already moved over all the Portal information, but we still have approximately 500 WSS sites to move over and we are worried about losing document versions, lists, etc.

We are looking for any best practices or lessons learned on this process. Help would be much appreciated!

Thank you,
Dodie Wible
Knowledge Specialist
Stewart Transactions Solutions
dwible@stewart.com
Saturday, October 25, 2008 12:34 PM by Moving a Sharepoint database

# Moving a Sharepoint database

Anonymous comments are disabled