Migrating the RMS Databases

Updated: June 1, 2008

Applies To: Windows Server 2003, Windows Server 2003 R2, Windows Server 2003 with SP1, Windows Server 2003 with SP2

There are instances in which a database server needs to be retired. An RMS database server hardware upgrade is one example. Before the database server is retired, the configuration database must be moved to a different database server. To protect the data in the configuration database, including the key pairs that it contains, you should carefully plan and implement a migration.

We recommend creating a CNAME alias for the RMS database server and then configuring RMS to use this alias. This eliminates the need to manually change the database server name in the RMS configuration database if the name of the server changes. When using a CNAME alias, you would only have to update the alias record.

Before you begin the configuration database migration, ensure that you have the following information:

  • The account name and password that was originally used to provision the servers in the RMS cluster that use this database.

  • If a software-based cryptographic service provider (CSP) is used for storing the RMS private key, the RMS private key password that was originally specified during provisioning. If a hardware security module (HSM) is used to store the RMS private key password, this step is not required.

noteNote
Migrating the configuration database does not require a new server licensor certificate or a new server private key because RMS retains the settings from the original configuration database.

You should back up the RMS databases before doing anything on the database server. If this is not an option, you must, at a minimum, export your server licensor certificate. For more information about exporting the server licensor certificate, see To Export Your Server Licensor Certificate to a File. If an error occurs when the databases are migrated, you can import the server licensor certificate into a new RMS installation and consume content that was rights-protected with the older installation.

To migrate a configuration database, use the following steps:

  • Update the RMS configuration database to reflect the name of the new database server name.

  • Update the web.config files and registry on each server in the RMS cluster to use the new database server name

ImportantImportant
This topic assumes that the RMS databases have already been copied to the new database server hosting the RMS databases.

Update the RMS configuration database to use the new database server name

The name of the database server that is hosting the RMS databases is stored in the RMS configuration database. After the database files have been migrated to the new database server, you must update the RMS configuration database. This can be done by using either the RMS Config Editor tool from the RMS Administration Toolkit or by using SQL Management Studio.

To update the RMS database server name by using RMS Config Editor, use the following steps:

To update the RMS configuration database by using RMS Config Editor

  1. Log on to an RMS server in the cluster as member of the System Administrators database role.

  2. Install the RMS Administration Toolkit from the Microsoft Download Center (http://go.microsoft.com/fwlink/?LinkId=98961).

  3. Navigate to %SystemDrive%:\Program Files\RMS SP2 Administration Toolkit\RMSConfigEditor, and then double-click RMSCONFIGEDITOR.EXE.

  4. In the Server box, type the name of the new server hosting the RMS configuration database, and then click Go.

  5. In the Database box, click DRMS_Config_<RMS cluster name>_<Port>, where <RMS cluster name> is the name of the RMS cluster and <Port> is the TCP port on which RMS communicates, and then click Go.

  6. Click DRMS_ClusterPolicies.

  7. In the results pane, change the value in the PolicyData column of the LoggingDatabaseServer row to the new RMS database server name.

  8. Click Persist.

  9. Change the value in the PolicyData column of the CertificationUserKeyStorageConnectionString row to reflect the new database server. The value should be data source=<new database server name>;integrated where <new database server name> is the name of the new database server.

  10. Click Persist.

  11. Repeat steps 9–10 for the value in the PolicyData column of the DirectoryServicesCacheDatabase row.

  12. In the left pane, click DRMS_PluginProperties.

  13. For PropertyID 101, named PERSISTENT_STORAGE, change the PropertyValue column to reflect the new database server. The value should be data source=<new database server name>;integrated where <new database server name> is the name of the new database server.

  14. Click Persist.

  15. Close RMS Config Editor.

To update the RMS configuration database by using SQL Server Management Studio, do the following steps:

To update the RMS configuration database by using SQL Server Management Studio

  1. Log on to the RMS configuration database server as local Administrator or another user account that is a member of the local Administrators group.

  2. Click Start, point to All Programs, point to Microsoft SQL Server 2005, and then click SQL Server Management Studio.

  3. On the Connect to Server page, ensure that the new database server name is listed in the Server name box, and then click Connect.

  4. Expand Databases, expand DRMS_Config_<RMS cluster name>_<Port>, and then expand Tables.

  5. Right-click DRMS_ClusterPolicies, and then click Open Table.

  6. In the results pane, change the value in the PolicyData column of the LoggingDatabaseServer row to the new RMS database server name.

  7. Change the value in the PolicyData column of the CertificationUserKeyStorageConnectionString row to reflect the new database server. The value should be data source=<new database server name>;integrated where <new database server name> is the name of the new database server.

  8. Repeat steps 6–7 for the value in the PolicyData column of the DirectoryServicesCacheDatabase row.

  9. In the Object Explorer pane, right-click DRMS_PluginProperties, and then click Open Table.

  10. For PropertyID 101, named PERSISTENT_STORAGE, change the PropertyValue column to reflect the new database server. The value should be data source=<new database server name>;integrated where <new database server name> is the name of the new database server.

  11. Close Microsoft SQL Server Management Studio.

Configure each server in the RMS cluster to use the new database server name

To configure each server in the RMS cluster to use the new database server name, you must update the web.config files and update three registry entries. Once this is complete, you must restart Internet Information Services (IIS) for the changes to take effect.

To update the web.config files on each server in the RMS cluster:

To update the web.config files on each server in the RMS cluster

  1. Log on to a server in the RMS cluster as a member of the local Administrators group.

  2. Navigate to %Systemdrive%\inetpub\wwwroot\_wmcs\admin.

  3. Double-click web.config, select the Select the program from a list option, and then click OK.

  4. Click Notepad, clear the Always use the selected program to open this kind of file, and then click OK.

  5. Click Edit, and then click Replace.

  6. In the Find what box, type the name of the database server to be retired that is hosting the RMS databases.

  7. In the Replace with box, type the name of the new database server that is hosting the RMS databases.

  8. Click Replace All, and then click Cancel.

  9. Click File, and then click Save.

  10. Close Notepad.

  11. Repeat steps 2–9 for the web.config files located in the %Systemdrive%\inetpub\wwwroot\_wmcs\certification and %Systemdrive%\inetpub\wwwroot\_wmcs\licensing directories.

  12. Repeat steps 1–11 for each server in the RMS cluster.

Finally, update the registry on each server in the RMS cluster to the new database server name:

CautionCaution
Incorrectly editing the registry may severely damage your system. Before making changes to the registry, you should back up any valued data on the computer.

To update the registry on each server in the RMS cluster

  1. Log on to a server in the RMS cluster as a member of the local Administrators group.

  2. Click Start, and then click Run.

  3. Type regedit.exe, and then click OK.

  4. Navigate to HKEY_LOCAL_MACHINE\Software\Microsoft\DRMS\1.0\KeyProtection.

  5. Change the registry entry named PASSWORDDERIVEDKEY_<old database server name>_DRMS_CONFIG_<RMS cluster name>_<port> to:

    PASSWORDDERIVEDKEY_<old database server name>_DRMS_CONFIG_<RMS cluster name>_<port>

    where:

    • <new database server name> is the name of the old database server.

    • <RMS cluster name> is the name of the RMS cluster.

    • <port> is the TCP port on which RMS communicates.

    • <new database server name> is the name of the new database server.

  6. Navigate to HKEY_LOCAL_MACHINE\System\CurrentControlSet001\Services\DRMS_Logging_<RMS cluster name>_<port>\Params.

  7. Change the ConnectionString registry entry so that the data source value matches the new database server name.

  8. Repeat steps 6–7 for HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\DRMS_Logging_<RMS cluster name>_<port>\Params.

  9. At a command prompt, type IISRESET, and then press ENTER.

  10. Repeat steps 1–9 for every server in the RMS cluster.

Community Additions

ADD
Show: