When you attach a content database, make sure that the root site for the Web application is included in the first content database that you attach. In other words, before you continue, examine the root of the Web application in the original server farm to determine the first site collection. After you attach the database that contains the root site, you can attach the other content databases for the Web application in any order. You do not have to create any site collections to store the content before you attach the database; this process creates the site collections for you. Make sure that you do not add any new site collections until you have restored all the content databases.
Important:
If you are moving the content databases across domains or forests or into another environment that has different service accounts, ensure that the permissions for the service accounts are still correct before you attach the databases.
You can use either the Mount-SPContentDatabase cmdlet in Windows PowerShell or the addcontentdb Stsadm command to attach a content database to a Web application. Using the SharePoint Central Administration pages to attach a content database is not supported for upgrading.
Ensure that the account you use to attach the databases is a member of the db_owner fixed database role for the content databases that you want to upgrade.
Important:
If you were using forms-based authentication, you will need to configure claims-based authentication for your Web application before you attach any databases. You must also create a policy to grant Full Control to the Web application to the user account that will be performing the database attach upgrade.
For more information, see Configure forms-based authentication for a claims-based Web application (SharePoint Server 2010).
Tip:
You cannot attach the same content database more than once to a farm, even on different Web applications. Each site collection in a content database has a GUID that is associated with it, which is registered in the configuration database. Therefore, you cannot add the same site collection twice to the farm, even in separate Web applications. Although you can successfully attach the database in this situation, you will be unable to start the site collection.
If you need a duplicate copy of a site collection in the same farm, first attach the database that contains the site collection to a separate farm, and then use the Stsadm backup and restore operations to copy the site collection over to the other farm. The Stsadm backup and restore process creates a new GUID for the site collection.
To attach a content database to a Web application by using Windows PowerShell
Verify that you meet the following minimum requirements: See Add-SPShellAdmin.
On the Start menu, click All Programs.
Click Microsoft SharePoint 2010 Products.
Click SharePoint 2010 Management Shell.
At the Windows PowerShell command prompt, type the following command:
Copy Code
Mount-SPContentDatabase -Name
Where:
Updateuserexperience is the choice to update to the new user experience or stay in the old user experience (part of Visual Upgrade). When you include this parameter, the site is set to preview the new user experience. Omit this parameter if you want the site to remain in the old user experience after upgrade. For more information, see Plan visual upgrade (SharePoint Server 2010).
For more information, see Mount-SPContentDatabase.
Note:
We recommend that you use Windows PowerShell when performing command-line administrative tasks. The Stsadm command-line tool has been deprecated, but is included to support compatibility with previous product versions.
To attach a content database to a Web application by using the Stsadm command-line tool
On the drive on which SharePoint Products and Technologies is installed, change to the following directory: %COMMONPROGRAMFILES%\Microsoft shared\Web server extensions\12\Bin.
Type the following command, and then press ENTER:
stsadm -o addcontentdb -url
[-databaseserver
[-databasepassword
[-preserveolduserexperience true/false ]
[-sitemax
[-assignnewdatabaseid] [-clearchangelog]
Note:
When you set the preserveolduserexperience parameter to true, the sites in the content database keep the look of the previous version after upgrade. When you set this parameter to false, the sites are upgraded to the new look and feel. The default for this parameter is true, which preserves the old look and feel.
This parameter is part of the Visual Upgrade feature. For more information, see Plan visual upgrade (SharePoint Server 2010).
For more information, see Addcontentdb: Stsadm operation (Office SharePoint Server).
Verification: Verify upgrade for the first database
After you have attached a database, you can use the Upgrade Status page in Central Administration to check the status of upgrade on your site collections. After the upgrade process is complete, you can review the upgrade log file to see whether there were any issues during upgrade. Also, you can review each upgraded site to find and address any issues with how the content is displayed. For more information, see Verify upgrade and review upgraded sites (SharePoint Server 2010).
To view the Upgrade Status page
In Central Administration, click Upgrade and Migration, and then click Check upgrade status.
To open the upgrade log file
The upgrade error log file and the upgrade log file are located at %COMMONPROGRAMFILES%\Microsoft Shared\web server extensions\14\LOGS. The logs are named in the following format: Upgrade-YYYYMMDD-HHMMSS-SSS-error.log and Upgrade-YYYYMMDD-HHMMSS-SSS.log, where YYYYMMDD is the date and HHMMSS-SSS is the time (hours in 24-hour clock format, minutes, seconds, and milliseconds). An example for an upgrade error log is Upgrade-20090415-132126-374-error.log, and an example for an upgrade log is Upgrade-20090415-132126-374.log.
Note:
The upgrade log file includes the name of the content database being upgraded.
Upgrade the shared services database
Before you can upgrade any My Sites in your environment, you must configure the User Profile service and Managed Metadata service and upgrade the Shared Services Provider (SSP) database. To do this, you must perform the following tasks:
Create an application pool for the User Profile service.
Verify that the Managed Metadata service is enabled.
Enable the User Profile service and upgrade the SSP database.
Note:
When you upgrade the SSP database, the audience information is also upgraded.
Create a new proxy for the User Profile service application and associate it with the default proxy group.
The following procedures provide the steps for these tasks.
Important:
The steps in the following sections assume that you have not yet enabled the User Profile service application or the User Profile Synchronization service. If you have already enabled these services, follow these steps to create a separate instance of the User Profile service application. You can associate your existing User Profile Synchronization service with the new User Profile service application.
To create an application pool for the User Profile service by using Windows PowerShell
Verify that you meet the following minimum requirements: See Add-SPShellAdmin.
On the Start menu, click All Programs.
Click Microsoft SharePoint 2010 Products.
Click SharePoint 2010 Management Shell.
To create the application pool, at the Windows PowerShell command prompt, type the following command:
Copy Code
New-SPServiceApplicationPool -Name
-Account
Where:
For more information, see New-SPServiceApplicationPool.
To verify that the Managed Metadata service is enabled
In SharePoint Central Administration, on the Application Management page, click Manage service applications.
Verify that the Managed Metadata service is started.
For more information about how to enable and manage this service, see Managed metadata administration (SharePoint Server 2010).
To enable the User Profile service and upgrade your SSP database by using Windows PowerShell
Verify that you meet the following minimum requirements: See Add-SPShellAdmin.
On the Start menu, click All Programs.
Click Microsoft SharePoint 2010 Products.
Click SharePoint 2010 Management Shell.
To enable the User Profile service and upgrade the SSP database, at the Windows PowerShell command prompt, type the following command:
Copy Code
New-SPProfileServiceApplication -applicationpool
Where:
For more information, see New-SPProfileServiceApplication.
To create the proxy for the User Profile service and associate it with the default proxy group by using Windows PowerShell
Verify that you meet the following minimum requirements: See Add-SPShellAdmin.
On the Start menu, click All Programs.
Click Microsoft SharePoint 2010 Products.
Click SharePoint 2010 Management Shell.
To configure the proxy for the User Profile service, at the Windows PowerShell command prompt, type the following command:
Copy Code
New-SPProfileServiceApplicationProxy -ServiceApplication
Where:
DefaultProxyGroup specifies that the User Profile service application proxy be added to the default proxy group for the local farm.
For more information, see New-SPProfileServiceApplicationProxy.
Make sure that your farm administration account has Full Control of the Use Profile service. Use the following procedure to grant the farm administration account full control.
Update permissions on the User Profile service
In SharePoint Central Administration, on the Application Management page, click Manage Service Applications.
Click the User Profile Service Application row (not the link) and then, on the ribbon, click Administrators.
In the Administrators for User Profile Service Application dialog box, in the To add an account, or group, type or select it below and click 'Add' box, type the farm administrator account and the account you are using to run the User Profile service, and then click Add.
In the Permissions for
Start the User Profile Synchronization service
In SharePoint Central Administration, on the System Settings page, click Manage Services on Server.
Next to the User Profile Synchronization service, click Start.
In the Select the User Profile Application dialog box, select the application you just created.
In the Service Account Name and Password section, type and confirm the password for the service account.
Click OK.
Important:
After you have enabled the User Profile Synchronization service, you can reapply the settings that you used for User Profile Synchronization from your Office SharePoint Server 2007 environment in your new environment. Reapply settings such as connections, property mappings, and filters. For more information about how to configure this service, see Configure profile synchronization (SharePoint Server 2010).
Note that the User Profile Synchronization service is not available in a stand-alone environment. You must have a server farm installation to use this service.
Now you are ready to upgrade My Sites.
Upgrade My Sites
If you have My Sites in your environment, you can upgrade them after you have upgraded the Shared Services Provider (SSP) database. You should have created the My Site host Web application when you created your new environment. To upgrade My Sites, you configure the My Site host URL, and then upgrade the content databases that contain My Sites.
To configure the My Site host URL
In Central Administration, on the Manage Service Applications page, click the User Profile service application that you want to associate with My Sites.
On the Manage Profile Service: User Profile Service page, click Setup My Sites.
Enter the information to set up My Sites, including the new My Site host location and personal site location.
The My Site host is a site collection on the content database, which will have a URL like http:// Fabrikam/my. The personal site path is the managed path at which all My Sites will be created. If you entered "personal" in the Location box, My Sites would be created at http:// Fabrikam/personal/username).
After you set up My Sites, you must reset Internet Information Services (IIS) by opening a Command Prompt window and typing iisreset /noforce at the command prompt.
Now that you have created the My Site host URL, you can upgrade My Sites. Follow the steps in Add the content databases to the Web applications later in this article to attach and upgrade the database or databases that contain My Sites. You can upgrade My Sites at any time after you have upgraded the SSP database and configured the My Site host URL.
Attach the remaining databases
After you restore the first content database and verify the upgrade by reviewing the upgrade log file, you can continue by restoring and upgrading the next database or databases. You can attach multiple databases at the same time in separate Command Prompt windows to run multiple upgrades at one time. After you successfully restore and upgrade all the sites, content databases, and SSP databases, you can review the sites to make sure that they were upgraded correctly.
Verification: Verify upgrade for additional databases
After upgrading any additional databases, view the Upgrade Status page to monitor progress and verify that the upgrade process is complete. Review the log file to identify any other issues, and then review each upgraded site to find and address any issues with how the content is displayed
