The official blog for Windows Server Essentials and Small Business Server support and product group communications.
EPS Team Blogs
[Today's post comes to us courtesy of Shawn Sullivan from Commercial Technical Support]
This post is an extension of Part Two of this series, where we are discussing how to migrate Companyweb with a larger content database to a SQL 2008 R2 Standard instance. In the last post we covered the configuration of the SQL instance on the Premium second server, which leaves us with the final steps of physically migrating the database to this server.
Note: At the end of this entire process, make sure you update the CNAME record for Companyweb in DNS to point to the SBS 2011 server. Otherwise your web client will try to contact the source server when you browse http://companyweb rather than the SBS 2011 server.
The three servers that will be involved in this process are:
The tasks that will be performed are:
In this example, the content database on my Source SBS Server is called ShareWebDB, which is the default name given to it by SBS 2008 setup. If there was an SBS 2003 server in the domain previously, the database could be named STS_<servername>_1. If you are unsure what the name of your content database is, you can find out what it is by running the following command:
“%ProgramFiles%\Common Files\Microsoft Shared\Web Server Extensions\12\BIN” stsadm –o enumcontentdbs –url http://Companyweb
Once you have the name, you are ready to back it up. If you haven’t already, install SQL Management Studio; you will need it during this process. At this point, proceed with the following:
Now that you have the backup file on the removable drive, simply plug it in and then restore the file into the Sharepoint instance you created in part two on Server Two.
The remainder of these steps will be taken on the SBS 2011 server. At this point we are essentially swapping the new content database for the old one that contains the site that we want to migrate. Although there is no user data yet in the new content database, it does contain the SBS 2011 Fax Center library, which we will want to keep. To do this, we’ll first export it before dismounting the new content database:
We are now ready to swap the database. This involves dismounting the one attached to the local SQL instance and mounting the one attached to the SQL server on the network:
Finally, import the Fax Center library backup into the migrated database:
After all of this, you will have a functioning Companyweb site on the SBS 2011 server that will look exactly like it did on the source server. You can use the Visual Upgrade feature in Sharepoint 2010 to update the look and feel, however you should properly plan for this especially if you have made customizations to your site that could be affected. For more information, see http://technet.microsoft.com/en-us/library/ff607998.aspx
You may need to runas admin to open up the SQL. Just get in the habit of 'runas admin' for everything :-)