Export (0) Print
Expand All

Move all databases (Office Forms Server 2007)

Office 2007

Updated: May 21, 2009

Applies To: Office Forms Server 2007

 

Topic Last Modified: 2009-05-11

This content is preliminary content. It might be incomplete and is subject to change.

This article contains information and steps to move all of the databases associated with Microsoft Office Forms Server 2007 from one database server to another database server in the same farm. You might want to move all of the databases if you are upgrading the hardware or the software on the database server — for example, moving from a 32-bit to a 64-bit version of Microsoft SQL Server 2005.

ImportantImportant:
This task requires that you stop the complete farm. This will make all farm sites and assets unavailable to users until the process is completed.

This article does not provide information about how to migrate or move the Office Forms Server 2007 farm from one group of servers to another group of servers. For more information about how to move the complete farm from one set of farm servers to another, see Move and migrate servers and server farms (Office SharePoint Server 2007)

This article does not provide information about how to move only content databases. If you want to move only the content databases from one database server to another, see Move content databases (Office SharePoint Server 2007).

This article does not provide information about how to move Single Sign-On (SSO). If you are using SSO, you must move the SSO database separately. For more information, see Back up and restore SSO (Office SharePoint Server 2007).

This article does not provide information about how to upgrade SQL Server 2005 on the database server. For more information about how to upgrade SQL Server 2005, see the SQL Server 2005 documentation.

You must move the following databases associated with Office Forms Server 2007:

  • Databases for Shared Services Providers (SSPs)

  • Search databases for the SSPs

  • Search database for SSP

  • Content databases

  • Search database

  • Central Administration content database

  • Configuration database

The following are required to perform the procedures for this task:

  • You must be logged on to the server that is running the SharePoint Central Administration Web site.

  • If you are using the Stsadm command-line tool, you must be a member of the Administrators group on the computer that is running Central Administration.

  • You must have membership in the following on the database server:

    • db_backupoperator fixed database role to back up the databases.

    • The local Administrators group on the destination server that is running SQL Server 2005 or an instance of SQL Server to restore the databases.

  • You must coordinate the move procedures with the database administrator (DBA). Steps that require the involvement of the DBA are signified by the prefix “[DBA]”.

This section summarizes the procedures that you must follow to complete the move process for all the databases associated with Office Forms Server 2007. To see the actual procedure steps, see each procedure following the overview.

In the move process, you will use Office Forms Server 2007 tools and SQL Server 2005 tools. Moving all of the databases from one database server to another database server consists of the following steps:

  1. Record which Web applications are associated with the SSPs.

  2. Perform a full back up of the SSPs.

  3. Use the Stsadm command-line tool to remove the SSPs from the farm.

  4. Completely stop the farm by stopping the services associated with Office SharePoint Server 2007 and by stopping Internet Information Services (IIS).

  5. [DBA] Back up the following databases by using SQL Server 2005 tools:

    • Content databases

    • Central Administration content database

    • Configuration database

    • Windows SharePoint Services Help Search database

    The other databases in the farm are backed up and restored with the SSPs.

  6. [DBA] Copy or move the database backup files to the destination database server.

  7. [DBA] Restore the databases that you backed up by using SQL Server on the destination database server by using SQL Server 2005 tools.

  8. [DBA] Copy to the destination server all of the SQL Server logins, fixed server roles, fixed database roles, and permissions for these databases.

  9. Run the Stsadm renameserver operation on the server that is running Central Administration.

  10. Restart the server that is running Central Administration to apply the changes and ensure that the services, Web sites, and application pools associated with Office SharePoint Server 2007 are started.

  11. Restore the SSP from the backup.

    NoteNote:
    The first SSP you restore will become the default SSP. To change which SSP is the default, use the “Configure the restored SSP to be the default SSP” Procedure later in this article.

This information is important to record so that you associate the correct Web applications with the SSP when you restore the SSP later in this article.

ImportantImportant:
Member of the Farm Administrators SharePoint group is the minimum required to complete this procedure.
Record which Web applications are associated with the SSP
  1. In Central Administration, on the Application Management page, in the Office SharePoint Server Shared Services section, click Create or configure this farm’s shared services.

  2. Record the associated Web applications that are listed on the Manage This Farm’s Shared Services page.

ImportantImportant:
You must be a member of the Farm Administrators SharePoint group to perform this procedure.
Back up the SSP by using Central Administration
  1. In Central Administration, on the Operations page, in the Backup and Restore section, click Perform a backup.

  2. On the Perform a Backup – Step 1 of 2: Select Component to Backup page, select the check box next to the SSP.

  3. At the top of the page, click Continue to Backup Options.

  4. On the Perform a Backup – Step 2 of 2: Select Backup Options page, in the Type of Backup section, select the Full option.

  5. In the Backup File Location section, type the Universal Naming Convention (UNC) path of the location where the backup will be stored.

  6. Click OK to start the backup.

ImportantImportant:
Membership in the Administrators group on the local computer and membership in the db_owner fixed database role on the database server are the minimum required to complete this procedure.
You must use the Stsadm command-line tool to remove the SSP.
CautionCaution:
Ensure that you back up the SSP before running this command. The databases are deleted on the databases server when the –force parameter is used.
Remove the SSP by using the Stsadm command-line tool
  1. On the drive on which SharePoint Products and Technologies is installed, change to the following directory: %COMMONPROGRAMFILES%\Microsoft shared\Web server extensions\12\Bin.

  2. To remove an SSP, type the following command, and then press ENTER:

    stsadm -o deletessp –title <SSP name> -force

    where SSPname is the name of the SSP that you want to remove.

    ImportantImportant:
    Do not use the -deletedatabases parameter.

Before you can move all of the databases, you must stop the farm to ensure that no changes are made while the databases are moved.

ImportantImportant:
Membership in the Administrators group is the minimum required to complete these procedures.
Stop the farm
  1. In the Services snap-in on the server that is running Central Administration, stop the following services:

    • 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

  2. Stop Internet Information Services. You can do this by using the iisreset /stop operation at a command prompt.

ImportantImportant:
Membership in the db_backupoperator fixed database role is the minimum required to complete this procedure.
In some environments, the DBA must perform these steps.
Back up databases on the source database server
  1. Open Microsoft SQL Server Management Studio and connect to the database server.

  2. In Object Explorer, expand Databases.

  3. Right-click the database that you want to back up, point to Tasks, and then click Back Up.

  4. In the Back Up Database dialog box, select the type of backup that you want to perform from the Backup type list. For more information about which backup type to use, see Overview of Recovery Models (http://go.microsoft.com/fwlink/?LinkId=114396&clcid=0x409) in the SQL Server 2005 Books Online.

  5. Under Backup component, select the Database option.

  6. In the Backup Set section, either use the default name provided or specify a name for the backup set in the Name text box.

  7. Specify the expiration date for the backup set. This determines how long, or when, the backup set can be overwritten by any later backups with the same name. By default, the backup set is set to never expire (0 days).

  8. In the Destination section, if the correct path of the backup folder is not listed, you can add the path by clicking Add.

  9. Click OK to back up the database.

  10. Repeat steps 3-9 for each database that you want to move.

ImportantImportant:
Read access to the shared folder on the source computer and Write access to the shared folder on the destination computer is the minimum required to complete these procedures.
In some environments, the DBA must perform these steps.
Copy or move the backup files to the destination database server
  1. In Windows Explorer, browse to the location of the .bak files for the databases.

  2. Select the .bak files for the databases that you want to move, and then either copy or move them to the destination directory.

ImportantImportant:
Membership in dbcreator fixed server role is the minimum required to complete these procedures.
In some environments, the DBA must perform these steps.
Restore databases on the destination database server
  1. Open Microsoft SQL Server Management Studio and connect to the database server.

  2. In Object Explorer, expand the database instance.

  3. Right-click the Databases node, and then click Restore Database.

  4. In the Restore Database dialog box, under Destination for restore, type the name of the database. You must use the identical name for the database that it had on the source database server.

  5. Under Source for restore, select the From device option.

  6. In the Specify Backup dialog box, select File from the Backup media list.

  7. Click Add, and then browse to the .bak file for the database.

  8. Select the .bak file, and then click OK. Click OK again to add the path of the Restore Backup dialog box.

  9. Ensure that the backup set is selected in the Select backup sets to restore list.

  10. In the Select a page pane, click Options.

  11. In the Restore options section, select only Overwrite the existing database. Unless the environment or policies require otherwise, do not select the other options in this section.

  12. In the Recovery state section, select the RESTORE WITH RECOVERY option.

    For more information about these recovery options, see Restore Database (Options Page) (http://go.microsoft.com/fwlink/?LinkId=114420&clcid=0x409).

  13. Click OK to complete the restore operation.

  14. Repeat steps 3-13 for each database that you are moving.

ImportantImportant:
Membership in sysadmin fixed server role is the minimum required to complete these procedures.
In some environments, the DBA must perform these steps.

For information about how to copy SQL Server roles and permissions to the destination database server, see Microsoft Help and Support article 246133 How to transfer logins and passwords between instances of SQL Server (http://go.microsoft.com/fwlink/?LinkId=132636&clcid=0x409). For troubleshooting information, see Microsoft Help and Support article 240872 How to resolve permission issues when you move a database between servers that are running SQL Server (http://go.microsoft.com/fwlink/?LinkId=123469&clcid=0x409).

ImportantImportant:
Membership in the Administrators group on the local computer is the minimum required to complete these procedures.
Run the Stsadm renameserver operation
  1. On the drive where SharePoint Products and Technologies is installed, change to the following directory: %COMMONPROGRAMFILES%\Microsoft Shared\Web server extensions\12\Bin.

  2. Type the following command, and then press ENTER:

    stsadm -o renameserver -oldservername <name of the source database server> -newservername <name of the destination database server>

    For more information, see Renameserver: Stsadm operation (Office SharePoint Server).

ImportantImportant:
Membership in the Administrators group on the local computer is the minimum required to complete these procedures.
Restart the farm
  1. Restart the server that is running Central Administration.

  2. In the Services snap-in, ensure that the following services are started:

    • 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)

  3. In Internet Information Services (IIS) Manager, ensure that the following Web sites are started:

    • SharePoint Central Administration v3

ImportantImportant:
The account that you use to run this procedure must be a member of the Farm Administrators SharePoint group.
The account must also be added to the Administrators group on the database server to perform this procedure. You can remove the account from this group after all the SSPs are restored.
Restore an SSP by using Central Administration
  1. In Central Administration, on the Operations page, in the Backup and Restore section, click Restore from backup.

  2. On the Restore from Backup – Step 1 of 4: Select Backup Location page, type the UNC path of the backup share, and then click OK.

  3. On the Restore from Backup – Step 2 of 4: Select Backup to Restore page, select the full backup of the SSP that you want to restore, and then click Continue Restore Process.

  4. On the Restore from Backup – Step 3 of 4: Select Component to Restore page, select the check box next to the SSP that you want to restore, and then click Continue Restore Process.

  5. On the Restore from Backup – Step 4 of 4: Select Restore Options page, in the Restore Options section, select New configuration.

  6. In the New Names section, type the destination database name in the New database server name box.

  7. In the New directory name box, type the path of the location on the destination server where the .mdf and .ldf files will be stored. This is the %Program Files%\Microsoft SQL Server\<instance name>\MSSQL\DATA directory.

  8. In the New database name text box, type the name of the search database. Use the exact same name as before.

  9. Click OK to start the restore.

Use this procedure if want a different SSP to be the default SSP.

ImportantImportant:
You must be a member of the Farm Administrators SharePoint group to perform this procedure.
Configure the restored SSP to be the default SSP
  1. In Central Administration, on the Application Management page, in the Office SharePoint Server Shared Services section, click Create or configure this farm’s shared services.

  2. On the Manage This Farm’s Shared Services page, click Change Default SSP.

  3. On the Change Default Shared Services Provider page, select the SSP that you restored from the SSP Name list, and then click OK.

This topic is included in the following downloadable book for easier reading and printing:

Was this page helpful?
(1500 characters remaining)
Thank you for your feedback
Show:
© 2014 Microsoft