This is Part 6 in a series of migrating SharePoint from SBS 2003 to SBS 2011. Series posts are:
Introduction – Overview
Part 1 – Caveats and Considerations
Part 2 – Preparation steps on v2
Part 3 – Upgrading v2 database to WSS v3
Part 4 – Attaching upgraded database to WSS v3
Part 5 – Check WSSv3 for migration to Foundation 2010
Part 6 – Move database to SBS 2011
Part 7 – Post migration steps and considerations
In this part we are going to move the WSS v3 database across to SBS 2011.
After running the ststadm –preupgradecheck shown in the last post and not having any issues, the next step in the process is to copy the databases from the staging WSS v3 server to the SBS 2011 machine.
The easiest way to do this is simply to stop the SQL service on the WSS v3 box. If you installed WSS v3 in a standard configuration the SQL database is Embedded Edition (##SSEE) so locate the Windows Internal Database service and right mouse click on it and select Stop.
Now, locate the raw SharePoint content database files on your WSS v3 server. These are the same ones that you copied from SBS 2003 but are now upgraded to SharePoint v3. Copy these files to you SBS 2011 server.
As with the migration from SBS 2003 to WSS v3, I recommend you backup your default SharePoint 2010 environment via a SharePoint specific backup prior to commencing. This makes it much easier and quicker to roll back if necessary. Now you can still do a backup via the good old STSADM command but Microsoft recommends that we do as much as we can with Powershell. So here’s our chance to get our hands dirty with Powershell.
To launch Powershell select Start | All Programs | Microsoft SharePoint 2010 Products | SharePoint 2010 Management Shell. Make sure that you run it as administrator as shown above.
After you accept the UAC you should see a DOS box with a blinking cursor as shown above. Type the following command:
Backup-spsite http://companyweb -path c:\companyweb.bak -force
This will create a backup of the SBS 2011 Companyweb site at c:\companyweb.bak. As before I’d also recommend an export of the site. To this type the following PowerShell command:
Export-spweb http://companweb -path “c:\companyweb.exp” -force
This will create an export backup of the SBS 2011 Companyweb site at c:\companyweb.exp. Leave the PowerShell console open for the time being and view http://companyweb.
SBS 2011 has a fax center which is unique to SBS 2011 and is much easier to backup individually and restore in SharePoint than attempt to recreate. So once Companyweb is displayed click on Fax Center. Then select the Library tab at the top of the page to reveal the ribbon.
In the ribbon select Library Settings (to the right).
In the middle, under the Permissions and Management column select Save document library as template.
Enter the details as shown above but make sure you check the option at the bottom to Include Content.
This will create and save a list template in the List Template Gallery. Simply visit the Gallery and click on the Fax Center template you just created and save it somewhere on your hard disk.
Return to your Powershell console and enter the following command:
As the screen shot shows you’ll be prompted to confirm this. Once complete the existing SharePoint content database has been removed from Companyweb.
You now need to attach the databases you copied from you staging WSS v3 to your SBS 2011 server. When you attach them it is also probably a good idea to rename them to ShareWebDb just to remain consistent going forward. This rename process will firstly require you to detach the existing ShareWebDB from SQL Express 2008 R2, attach the copied databases renaming in the process. This isn’t too difficult and I’m not going to go through it here.
Once you have attached the copied databases to SQL Server you run the following command at the Powershell console:
Mount-spcontentdatabase “sharewebdb” -webapplication http://companyweb
This will reconnect the new (copied from WSS v3) databases (now called ShareWebDb) to http://companyweb. During this process you will see a percentage complete displayed as the WSS v3 databases are converted to SharePoint 2010 format.
When that is successful, the final step in the process is to convert the interface from WSS v3 to SharePoint 2010 (as SharePoint 2010 can allow migrated WSS v3 sites to still run with the old look and feel). To do this execute the following Powershell commands:
Foreach ($s in $webapp.sites)
If you now visit http://companyweb you should see your old content displayed in the new SharePoint 2010 interface.
In the next post I’ll cover off some tidy up, including how to re-import the Fax Center, enable health and analytics reporting as well a few other things I believe ‘must’ be done to make SharePoint 2010 as functional as possible.