One of the things that is not discussed well at all in Microsoft's documentation on MOSS 2007 is the steps you have to go through to properly move a content database. If not done correctly you can get lots of fun errors like this:
Failure trying to synch web application A duplicate site ID was found. This might be caused by restoring a content database from one server farm into a different server farm without first removing the original database and then running stsadm -o preparetomove. If this is the cause, the stsadm -o preparetomove command can be used with the -OldContentDB command line option to resolve this issue.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
The word is starting to get out about using the preparetomove command but what do you do when you have already moved the database? That is when this great posting from Cory Burns comes in handy. Cory does a great job of explaining some little known stsadm commands that can help you get your SSP synchronization straightened out and remove those repeating event log errors.
http://blogs.technet.com/corybu/archive/2007/06/01/detaching-databases-in-moss-2007-environments.aspx
No comments:
Post a Comment