Migrate content databases
Applies To: Windows SharePoint Services 3.0
Topic Last Modified: 2008-03-03
In this article:
Before you begin
Set the previous version databases to be read-only
Back up the previous version databases using SQL Server
Restore the backup copy to the new farm
Add the databases to the Web applications
Review the upgrade log files for any issues
Repeat the restore and add database procedures for all content databases
When you upgrade by way of a database migration, you essentially perform a backup and restore of your databases (that is, you back them up in the old farm, and then restore them in the new farm). When you restore a database and add it to the farm, the upgrade process runs and upgrades the entire database. The database migration process is similar to the in-place upgrade process; the difference is that the database migration process is performed manually and gradually.
Before you begin, you must create your new server farm environment. For information about creating the new environment, see Prepare the new Windows SharePoint Services 3.0 environment.
After you have set up the new environment, you can follow the steps below to detach and then reconnect the databases to perform the upgrade.
Before you begin
Before backing up and migrating your databases, you must perform the following steps to prepare for the upgrade.
Run the pre-upgrade scan tool on the content in your original environment. If you do not run the pre-upgrade scan tool on your databases before you back them up, you will not be able to upgrade the data on your new server farm. For more information, see Run the pre-upgrade scan tool (Windows SharePoint Services).
Create your new server farm environment. For information about creating the new environment, see Prepare the new Windows SharePoint Services 3.0 environment.
If you have custom site definitions or area definitions in your old environment, create new site definitions and upgrade definition files for these site definitions and deploy them to your new environment. For more information, see the following resources:
Set the previous version databases to be read-only
Be sure you capture all of the data in your backup so that you are restoring and upgrading the current state of your environment. Therefore, set the previous version databases to read-only so that users cannot add or change information in the sites. With the databases set to read-only, users can continue to view content, but they are not able to add or change content.
Important
Before you perform these procedures, be sure that you have run the pre-upgrade scan tool on the sites stored in the databases. If you do not run the pre-upgrade scan tool on the data before you back the databases up, you will not be able to upgrade the data on your new server farm. For more information, see Run the pre-upgrade scan tool (Windows SharePoint Services).
Set a database to read-only in SQL Server 2000
In Microsoft SQL Server Enterprise Manager, right-click the name of the database that you want to set to read-only, and then click Properties.
In the Properties dialog box, click the Options tab.
Under Access, select the Read-only check box, and then click OK.
Set a database to read-only in SQL Server 2005
In SQL Server Management Studio, right-click the name of the database that you want to set to read-only, and then click Properties.
In the Select a page section, click Options.
In the right pane, under Other options, in the State section, next to Database Read-Only, click the down arrow, and then select True.
Back up the previous version databases by using SQL Server tools
Follow the appropriate steps to back up your databases in either SQL Server 2000 or SQL Server 2005. Repeat these steps for each content database in your server farm. Do not perform these steps for the configuration database; you do not need the configuration database because you have created a new one in the new environment.
Back up a database in SQL Server 2000
On your database server, click Start, point to All Programs, point to Microsoft SQL Server, and then click Enterprise Manager.
In SQL Server Enterprise Manager, click the plus sign next to Microsoft SQL Servers.
Click the plus sign next to SQL Server Group.
Click the plus sign next to (local) (Windows NT).
Click the plus sign next to Databases.
Right-click the database you want to back up, point to All Tasks, and then click Backup Database.
In the SQL Server Backup dialog box, in the Name box, specify a name for the backup, and then in the Backup area, select Database - complete.
In the Destination area, either select an existing destination, or:
Click Add.
In the Select Backup Destination box, select File Name, and then next to the File Name box, click the Browse button.
In the Backup Device Location - (local) dialog box, in the File name box, type a file name, and then click OK.
Click OK again to close the Select Backup Destination dialog box.
Click OK to start the backup process.
Click OK to acknowledge that the backup process has completed.
Repeat these steps to back up all of the other content databases that are used by Windows SharePoint Services 3.0 in your environment.
Back up a database in SQL Server 2005
On your database server, click Start, point to All Programs, point to Microsoft SQL Server 2005, and then click SQL Server Management Studio.
In the Connect to Server box, fill in the connection information, and then click Connect.
After connecting to the appropriate instance of the SQL Server 2005 Database Engine, in Object Explorer, expand the server tree by clicking the plus sign next to the server name.
Expand Databases, right-click the database you want to back up, point to Tasks, and then click Back Up. The Back Up Database dialog box appears.
In the Source section, in the Database box, verify the database name.
In the Backup type box, select Full.
Under Backup component, select Database.
In the Backup set section, in the Name text box, either accept the default backup set name that is suggested or type a different name for the backup set.
In the Destination section, specify the type of backup destination by selecting Disk or Tape, and then specify a destination. To create a different destination, click Add.
Click OK to start the backup process.
Repeat the preceding procedure to back up all of the other content databases that are used by Windows SharePoint Services 3.0 in your environment.
Restore the backup copy to the new farm
After you have configured the new environment, you can restore the backup copies of the databases. Start with one database, and then verify that the restoration has worked before you restore the other databases.
You must create a new database to contain the restored data, and then you can restore the backup into that new database. When you create the new database, be sure to create a large transaction log initially. The upgrade process creates many transactions while it runs and if your log is small, it might not be able to grow quickly enough to handle the number of transactions. If the transaction log runs out of space, the upgrade process will fail and you will need to retry attaching the database and upgrading the data.
The following sections provide steps for restoring the backups for both SQL Server 2000 and SQL Server 2005.
Restore the backup copy in SQL Server 2000
First, you create a new database. Then, you restore the backup into that new database.
Create a new database to contain the restored data in SQL Server 2000
Open Enterprise Manager and connect to the server to which the backup is to be restored.
Expand Microsoft SQL Servers, expand SQL Server Group, and then expand (local) Windows NT.
Right-click Databases, and then click New Database.
In the Name box, type the name of the database you want to restore.
On the Data files tab, in the File Name box for the Data file type, verify that the name is the one you want to use.
In the Initial Size (MB) box, adjust the size to approximately the size of the database you want to restore.
On the Transaction Log tab, in the File Name box for the Log file type, verify that the name is the one you want to use.
In the Initial Size (MB) box, adjust the size to approximately three or four times the size of the log file for the database you want to restore.
Make the log file very large to avoid filling it up during the upgrade process. You can always shrink the transaction log again after you have completed the upgrade.
In the File properties section, be sure that the Automatically grow file check box is selected.
In the Maximum file size section, be sure that Unrestricted file growth is selected.
You can change these settings after you perform the upgrade. It is important that the log file not run out of space during the upgrade process.
Click OK to create the database.
Restore a backup copy of a database as a new database in SQL Server 2000
Copy the database backup file to the target computer or share it on the network so that it is accessible from the server.
Open Enterprise Manager and connect to the server to which the backup is to be restored.
Expand Microsoft SQL Servers, expand SQL Server Group, and then expand (local) Windows NT.
Right-click the database you just created, click All Tasks, and then select Restore Database.
The Restore Database dialog box appears.
In the Restore as database box, select the new database.
This is the database to which the backup will be restored.
Select the From device option.
Click the Select Devices button.
In the Choose Restore Devices dialog box, select Disk.
Click the Add button. The Choose Restore Destination dialog box appears.
Enter the file name of the backup file that is to be restored. If the file exists on a network share, provide the UNC share name in the File name text box.
Note
We recommend that you copy the backup to the server and use a local path to restore the database.
Click OK.
The Choose Restore Device dialog box is now updated with the selected file.
Click OK to return to the Restore Database dialog box.
The Devices list is now updated with the file selected in the previous step.
Click the Options tab, and then select the Force restore over existing database check box.
This ensures that the restore operation overwrites the new database you just created.
Click OK in the Restore Database dialog box.
This starts the restore process. Progress and confirmation dialog boxes are displayed as SQL Server performs and completes the restore of the database.
Click OK in the confirmation dialog box.
For more information about restoring a backup to a new database, see SQL Server 2000 Backup and Restore (https://go.microsoft.com/fwlink/?LinkId=93461).
Restore the backup copy in SQL Server 2005
First, you create a new database. Then, you restore the backup into that new database.
Create a new database to contain the restored data in SQL Server 2005
After connecting to the appropriate instance of the SQL Server 2005 Database Engine, in Object Explorer, expand the server tree by clicking the plus sign next to the server name.
Right-click Databases, and then click New Database.
In the Database name box, type the name of the database you want to restore.
In the Owner box, specify an owner if desired.
In the Database files section, in the Logical Name box for the Data file type, verify that the logical name is the one you want to use.
In the Initial Size (MB) box, adjust the size to approximately the size of the database you want to restore.
In the Logical Name box for the Log file type, verify that the logical name is the one you want to use.
In the Initial Size (MB) box, adjust the size to approximately three or four times the size of the log file for the database you want to restore.
Make the log file very large to avoid filling it up during the upgrade process. You can always shrink the transaction log again after you have completed the upgrade.
In the Autogrowth column for the log file, set it to By 10 percent, unrestricted growth.
You can change this setting after you perform the upgrade. It is important that the log file not run out of space during the upgrade process.
Click OK to create the database.
Restore a backup copy of a database in SQL Server 2005 Enterprise Edition
Right-click the database you just created, point to Tasks, point to Restore, and then click Database. The Restore Database dialog box appears.
In the Restore Database dialog box, on the General page, the name of the restoring database appears in the To database list box.
In the To a point in time text box, retain the default (Most recent possible).
To specify the source and location of the backup sets to restore, select From device, and then click the browse button to select the backup file.
In the Specify Backup dialog box, in the Backup media box, be sure that File is selected.
In the Backup location area, click Add.
In the Locate Backup File dialog box, select the file you want to restore, and then click OK.
In the Select the backup sets to restore grid, select the Restore check box next to the most recent full backup.
In the Restore Database dialog box, on the Options page, under Restore options, select the Overwrite the existing database check box.
Click OK to start the restore process.
Add the databases to the Web applications
When you add the content databases, be sure that the root site for the Web application is included in the first content database you add (in other words, the first site collection at the root of the virtual server in your old environment). After you have added the database that contains the root site, you can add the other content databases for the Web application in any order. You do not need to create any site collections to store the content before you add the database; this process creates the site collections for you. Be sure that you do not add any new site collections until you have restored all of the content databases.
You must use the Stsadm command-line tool to add a content database to a Web application.
Note
You cannot add the same content database more than once to a farm, even on different Web applications. Each site collection in a content database has a globally unique identifier (GUID) associated with it, registered in the configuration database. Therefore, it is not possible to add the same site collection twice to the farm, even in separate Web applications. Although you can successfully attach the database in this situation, the site collection cannot be started. 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.exe backup and restore operations to copy the site collection over to the other farm. The backup and restore process creates a new GUID for the site collection.
Add a content database to a Web application by using the Stsadm command-line tool
To add a content database to a Web application, you use the addcontentdb operation.
Important
If you are running Windows SharePoint Services 3.0 in host-header mode, you must perform an additional step to set a host header property before you attach the content databases. This step is not needed if you are running Windows SharePoint Services 3.0 with Service Pack 1 applied. On the command line, run the following command:
stsadm.exe -o setproperty -pn V2UsedHostHeaderMode -pv true
After you add the content databases, you must then set the property to false so the next content database operation is for databases that contain site collections that use managed paths (such as \sites):
stsadm.exe -o setproperty -pn V2UsedHostHeaderMode -pv false
Run the following command:
stsadm -o addcontentdb -url <URL> –databasename <database name>
[-databaseserver <server name>] [-databaseuser <user name>
[ -databasepassword <password>] [-sitewarning <site warning count>]
[-sitemax <site max count>]
The following table explains the parameters for the addcontentdb operation.
| Name | Required/Optional | Description |
|---|---|---|
URL |
Required |
URL of the Web application to which the content database is being added. |
DatabaseName |
Required |
Database name. |
DatabaseServer |
Optional |
Database server name. The default server is used if a value not provided. |
DatabaseUser |
Optional |
Account used for SQL authentication. Must be used in conjunction with databasepassword. |
DatabasePassword |
Optional (however, required if using DatabaseUser) |
The databasepassword parameter should only be used where Windows authentication is not implemented Therefore, in a SQL authentication scenario, you need to pass the databaseuser and databasepassword parameters to authenticate against the database server. Under Windows authentication, you can omit these parameters because the credentials are passed using NTLM. |
SiteWarning |
Optional |
Integer number of site collections allowed in the content database prior to generating a warning event in the Windows event log. |
SiteMax |
Optional |
Specifies the maximum number of site collections allowed in the content database. |
For more information about this operation, see Addcontentdb: Stsadm operation (Windows SharePoint Services).
Review the upgrade log files for any issues
After you have attached the database and the upgrade process has completed, you can review the upgrade log file to see if there were any issues during upgrade. The upgrade log file and the trace log file are located at %COMMONPROGRAMFILES%\Microsoft Shared\web server extensions\12\LOGS. The trace log is named in the following format: Computer_name-YYYYMMDD-HHMM.log, where YYYYMMDD is the date and HHMM is the time (for example, Server1-20061105-1241.log).
Repeat the restore and add database procedures for all content databases
If you have multiple content databases, after you have restored the first content database and verified the upgrade by reviewing the upgrade log file, you can continue by restoring and upgrading the next database. After you have successfully restored and upgraded all of the content databases, you can review the sites to be sure that they upgraded properly. For more information, see Review upgraded sites (Windows SharePoint Services).
Next, follow the steps in Perform post-upgrade steps for an in-place upgrade (Windows SharePoint Services). Because database migration is essentially an in-place upgrade for your content, you can use the same post-upgrade steps. For more post-upgrade steps, see Chapter overview: Perform post-upgrade steps (Windows SharePoint Services).
Download this book
This topic is included in the following downloadable book for easier reading and printing:
See the full list of available books at Downloadable books for Windows SharePoint Services.