Move all databases to a different database server

This article contains information and steps for moving all the databases associated with Microsoft® Office SharePoint® Server 2007 from one database server to a new database server that has a different name. The following databases can be moved by using this procedure: • • • • • • Databases for Shared Services Providers (SSPs) Search databases for SSPs Content databases Search database Central Administration content database Configuration database

This article does not provide information about how to migrate or move the entire Office SharePoint Server 2007 farm. For more information about how to move the complete farm from one set of farm servers to another, see Move to another farm (http://go.microsoft.com/fwlink/?LinkId=141018). This article does not provide information about how to move only content databases. For more information about how to move only the content databases from one database server to another, see Move content databases (http://go.microsoft.com/fwlink/?LinkId=141019). This article does not provide information about how to move single sign-on (SSO) databases. If you are using SSO, you must move the SSO database separately. For more information, see Back up and restore SSO (http://go.microsoft.com/fwlink/?LinkId=141020). This article does not provide information about how to upgrade the database server. For more information about how to upgrade to Windows Server® 2008, see Installing Windows Server 2008 (http://go.microsoft.com/fwlink/?LinkId=140803) or see the documentation included with the software. For more information about how to upgrade to Microsoft SQL Server® 2008, see Installing SQL Server 2008 (http://go.microsoft.com/fwlink/?LinkId=141021) or see the documentation included with the software. Important: The following are the minimum required to perform this procedure:

• •

You must be a member of the Farm Administrators SharePoint group.

On the computer that is running the SharePoint Central Administration Web site, you must be a member of the Administrators group.

Back up an SSP by performing the following steps: a. To back up an SSP. b. on the Application Management page.com/fwlink/?LinkId=141023) procedure.• On the database server from which the databases are being moved: o o • You must be a member of the Administrators group. This will make all farm sites and assets unavailable to users until the process is complete. change to the following directory: %COMMONPROGRAMFILES%\Microsoft shared\Web server extensions\12\Bin. 1. You must be a member of the db_backupoperator fixed database role. Record the associated Web applications that are listed on the Manage This Farm’s Shared Services page. On the drive on which SharePoint Products and Technologies is installed.microsoft. type the following command: stsadm -o backup -directory <\\server name\folder name> -backupmethod full -item <SSP name> where \\server name\folder name is the UNC path of the backup folder and where SSP name is the name of . Record which Web applications are associated with the SSP by performing the following steps: a. Prepare the new database server by using the Prepare the database servers (http://go. type the following command: stsadm -o backup -showtree Note: Items enclosed by square brackets ([ ]) cannot be directly selected for backup but are backed up when their parent item is selected. Be sure to follow any applicable policies and guidelines for handling databases. If you do not already know what node you want to back up. Move all databases to a different database server Important: This task requires you to stop the complete farm. You must be a member of the db_owner fixed database role. click Create or configure this farm’s shared services. In some environments. in the Office SharePoint Server Shared Services section. On the database server to which the databases are being moved: • • • You must be a member of the Administrators group. On the SharePoint Central Administration Web site. you must coordinate the move procedures with the database administrator.

and click Delete. On the disk on which Microsoft SharePoint Products and Technologies is installed. and then click OK. b. change to the following directory: %COMMONPROGRAMFILES%\Microsoft shared\Web server extensions\12\Bin. Right-click an SSP content database. in the Services snap-in. Remove the SSP by performing the following steps: a. and then press ENTER: stsadm -o deletessp -title <SSP name> -deletedatabases -force where SSP name is the name of the SSP that you want to remove. type the following command. c. Perform steps c and d for each SSP content database. To remove an SSP. On the Delete Object page. a. On the server that is running the Central Administration Web site. Delete the SSP content databases. e. verify that the database you want to delete is selected.the SSP that you want to back up. c. d. expand Databases. To detach the SSP content database from the SharePoint farm. point to Tasks. All databases associated with the SSP will be automatically included in the backup. Repeat these steps for each SSP that you want to back up. d. type the following command and press ENTER: stsadm -o -deletecontentdb -url <URL> -databasename <database name> where URL is the URL of the SSP administration application from which the content database will be detached and database name is the name of the content database to be detached. b. Start SQL Server Management Studio and connect to the database server. stop the following services: • • • • • • Microsoft Single Sign-On service Office Document Conversions Launcher service Office Document Conversions Load Balancer service Office SharePoint Server Search service Windows SharePoint Services Administration service Windows SharePoint Services Search service . In Object Explorer. Stop the farm by performing the following steps: e. Repeat steps b and c for each SSP.

b. c. Start SQL Server Management Studio and connect to the database server. type iisreset /stop. k.bak) files that you want to move. Right-click the database that you want to restore. . In the Backup set area. and then copy or move them to the destination server. point to Restore. Do not move any databases or other files at this time. type a description of the backup. or use the default. the setting for the backup set is 0 days so that it never expires. i. type a name or use the default. Windows SharePoint Services Timer service Windows SharePoint Services Tracing service Windows SharePoint Services VSS Writer service At the command prompt. Restore databases on the destination database server. Click Database. expand Databases. the backup set can be overwritten by any subsequent backups with the same name. Repeat step 6 on each server in the farm. In Windows Explorer. In Object Explorer. point to Tasks. d. Click OK to back up the database. In the Description text box. Right-click the configuration database (usually named SharePoint_Config). select the type of backup that you want to perform from the Backup type list. a. in the Name text box. b. or use the default. Important: In some environments. h. f. Back up the databases on the source database server. see Overview of Recovery Models (http://go. Specify how long the backup should be kept. In Object Explorer. By default.microsoft.• • • f. expand Databases. j. point to Tasks. locate the database backup (. In the Back Up Database dialog box. In the Destination section. When the backup set expires. For more information about which backup type to use.com/fwlink/?LinkId=114396&clcid=0x409). Start SQL Server Management Studio and connect to the database server. and click Database. a. g. this step must be performed by the database administrator. specify a location to store the backup set. Repeat steps c through j for the remaining databases in the farm. Move only the backup files to the destination database server. and then click Back Up. c. e. g.

In the Restore Database dialog box. select RESTORE WITH RECOVERY. Copy to the destination database server all the SQL Server logins. and permissions for the databases. see Microsoft Help and Support article 240872. fixed database roles. i. you must create a SQL Server connection alias. For information about how to copy SQL Server roles and permissions to the destination database server. How to resolve permission issues when you move a database between servers that are running SQL Server (http://go. change to the following directory: %COMMONPROGRAMFILES%\Microsoft Shared\Web server extensions\12\Bin.com/fwlink/?LinkId=114420&clcid=0x409). If you are using a named instance of SQL Server. How to transfer logins and passwords between instances of SQL Server (http://go. Important: There are two different procedures for redirecting the farm to the new database server. Repeat steps c through h for each database that you are restoring. For troubleshooting information. see Microsoft Help and Support article 246133. When you use an unnamed instance of SQL Server. g. this step must be performed by the database administrator. click Options. and select the backup set or sets that you want to restore. do not select the other options in this section. renameserver does not rename named instances of SQL Server. For more information about named instances. Important: In some environments. the stsadm -o renameserver operation can be used to change the name of the database server that a farm refers to.microsoft. The third option. • • h. RESTORE WITH STANDBY is not used in this scenario. In the case of SharePoint Products and Technologies. e. select only Overwrite the existing database. In the Recovery state section: • If you have included all the transaction logs that you must restore. Refer the farm to the new database server. you can create a SQL Server alias that is used by all servers (including the front-end Web servers and application servers) to connect to the instance of SQL Server. The default values for destination and source typically suit most recovery scenarios.com/fwlink/? LinkId=123469&clcid=0x409). A connection alias is an alternative name that you can use to make a connection to an instance of SQL Server. fixed server roles. However.microsoft. If you must restore additional transaction logs. . see Using Named Instances (http://go. In the Select a page pane. Click OK to complete the restore operation. specify the destination and the source. Unless your environment or policies require otherwise. In the Restore options section. select RESTORE WITH NORECOVERY.com/fwlink/?LinkId=144252).d.microsoft. Use the following procedure if you are using an unnamed instance of SQL Server: a. f. On the disk on which SharePoint Products and Technologies is installed.

b. Repeat steps a through f on all servers that connect to SQL Server. in the Server name box. Start the new farm by performing the following steps: a. click Add. In the Network libraries area. On the General tab. Start the SQL Server Native Client Network Utility (%SYSTEM%\cliconfg. Repeat steps a and b on all servers that connect to SQL Server. and then click OK. type iisreset /start. c. enter the name of the current instance of SQL Server. On the Alias tab. The Add Network Library Configuration dialog box appears. Repeat step 12 on each server in the farm.exe). Type the following command. Use the following procedure if you are using a named instance of SQL Server: a. In the Connection parameters area. start the following services: • • • • • • • • • b. Microsoft Single Sign-On service Office Document Conversions Launcher service (optional) Office Document Conversions Load Balancer service (optional) Office SharePoint Server Search service Windows SharePoint Services Administration service Windows SharePoint Services Search service Windows SharePoint Services Timer service Windows SharePoint Services Tracing service Windows SharePoint Services VSS Writer service (optional) At the command prompt. enter the new server name and instance to associate with the alias. In the Server alias box. c. and then press ENTER: stsadm -o renameserver -oldservername <name of the source database server> -newservername <name of the destination database server> For more information. In the Services snap-in. click TCP/IP. verify that TCP/IP is enabled.com/fwlink/?LinkId=141025). .microsoft. see Renameserver: Stsadm operation (Office SharePoint Server) (http://go.

To obtain the backup GUID for the specific backup that you want to restore. and SQL Server instance is the name of the SQL Server instance where the SSP databases should be restored. select the SSP that you restored from the SSP Name list. in the Office SharePoint Server Shared Services section. click Create or configure this farm’s shared services. type the following command. b. GUID from backuphistory is the GUID for the specific backup package that you want to restore. and then click OK. and press ENTER: stsadm -o backuphistory -directory <UNC path> where UNC path is the path to the shared folder that contains the backup. To restore an SSP. On the Manage This Farm’s Shared Services page. and then press ENTER: stsadm -o restore -directory <UNC path> -backupid <GUID from backuphistory> -restoremethod new -newdatabaseserver <SQL Server instance> where UNC path is the UNC path of the backup shared folder. c. . On the Change Default Shared Services Provider page. On the SharePoint Central Administration Web site. click Change Default SSP. on the Application Management page. type the following command. b. Configure a restored SSP to be the default SSP: a.Restore an SSP to the new location. a. Repeat step 13 for each SSP that you want to move.

AS TO THE INFORMATION IN THIS DOCUMENT. mechanical. and SharePoint are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries. Windows. This white paper is for informational purposes only. and Microsoft cannot guarantee the accuracy of any information presented after the date of publication. copyrights. photocopying.The information contained in this document represents the current view of Microsoft Corporation on the issues discussed as of the date of publication. stored in or introduced into a retrieval system. or other intellectual property. recording. SQL Server. trademarks. or otherwise). trademarks. or transmitted in any form or by any means (electronic. Microsoft. without the express written permission of Microsoft Corporation. or for any purpose. . copyrights. patent applications. The names of actual companies and products mentioned herein may be the trademarks of their respective owners. All rights reserved. or other intellectual property rights covering subject matter in this document. no part of this document may be reproduced. Because Microsoft must respond to changing market conditions. EXPRESS. MICROSOFT MAKES NO WARRANTIES. ©2009 Microsoft Corporation. IMPLIED OR STATUTORY. Microsoft may have patents. Except as expressly provided in any written license agreement from Microsoft. the furnishing of this document does not give you any license to these patents. Complying with all applicable copyright laws is the responsibility of the user. it should not be interpreted to be a commitment on the part of Microsoft. Without limiting the rights under copyright.