How to move Microsoft Provisioning Server (MPS) databases to a clustered virtual SQL Server 2000 named instance (888265)

Assess your environment

These instructions assume that you have prepared the cluster servers and that you have a working MPS server. For example, your environment may be similar to the following:

• One cluster that is named CluCar with 2 nodes that are named dlg1 and dlg2
• One virtual SQL Server 2000 named instance of VSQL1\INST1
• One MPS server that is installed on a default instance of SQL Server 2000. This MPS server is named MPS01
• All the following MPS databases are installed on the default SQL Server 2000 instance on the MPS server:
  • MPFConfig
  • MPFAudit
  • MPFTranLogData
  • HECustomerDB

When you have the completed the migration that is described in this article, your environment will be similar to the following:

• The MPS service and the Provisioning Engine Microsoft COM+ application are running on the MPS server (MPS01).
• All MPS databases are running on the clustered virtual SQL Server 2000 named instance.

back to the top

Prepare the servers

To help with the migration, copy the Service Provisioning folder from the Hosted Exchange 2003 CD to a local hard disk drive that is on the MPS server. Hosted Exchange 2003 is one of the Microsoft Solutions for Microsoft Windows-based Hosting. Additionally, copy this folder to the two SQL Server 2000 clustered nodes. In this article, you must run the Mpf.msi command from the \Service Provisioning\MPS 1.0\MPF\Standard folder.

back to the top

Move the customer database (HECustomerDB)

1. Paste the following code in an XML editor or Notepad:

   <?xml version="1.0" encoding="utf-8" ?>
   <request>
    <procedure>
     <execute namespace="Hosted Exchange" procedure="SetCustomerDatabaseLocation" impersonate="1">
      <executeData>
       <databaseName>HeCustomerDb</databaseName>
       <serverName>VSQL1\INST1</serverName>
       <preferredDomainController>your.domanController.com</preferredDomainController>
      </executeData>
      <after source="executeData" destination="data" mode="merge" />
     </execute>
    </procedure>
   </request>

2. In the code, replace the databaseName, the serverName, and the preferredDomainController (DC) with the new values, and then save the file as Move.xml on the MPS server (MPS01).
3. On the MPS server (MPS01), run the following command at a command prompt:

   provtest.exe move.xml

4. Copy the HECustomerDB database from the MPS server (MPS01) to the virtual SQL Server 2000 named instance VSQL1\INST1.
   
   Note You can do this by using one of the following methods:
   • By using SQL Server backup and restore commands
   • By using the Copy Database Wizard in Enterprise Manager.
   We recommend that you use the Copy Database Wizard because the wizard copies database permissions and database roles.

back to the top

Move the MPS databases

1. On the MPS server (MPS01), run the Mpf.msi command, and then remove the following components:
   • Transaction log database
   • Audit database
   • Resource manager database
   Note When you are prompted, type MPS01 or your MPS server name for the Config Server Name value.
2. Log on to the first clustered node (dlg1) where SQL Server 2000 is running, run the Mpf.msi command, and then install the following components:
   • Transaction log database
   • Audit database
   • Resource manager database
   When you are prompted, type the configuration information that is in the following table:

   Property	Value
   Transaction Log server	VSQL1\INST1 (SQL Server 2000 virtual server)
   Audit Database Server	VSQL1\INST1 (SQL Server 2000 virtual server)
   Resource Manager Server	VSQL1\INST1 (SQL Server 2000 virtual server)
   Config Server Name	MPS01 (MPS server)

   Note Replace the SQL Server 2000 virtual server named instance and the MPS server name in this table to match your configuration.
3. Log on to the second clustered node (dlg2) where SQL Server 2000 is running, run the Mpf.msi command, and then install the Transaction log database component. When you are prompted, type the following configuration information:

   Property	Value
   Transaction Log server	VSQL1\INST1 (SQL Server 2000 virtual server)
   Config Server Name	MPS01 (MPS server)

   Note Replace the SQL Server 2000 virtual server named instance and the MPS server name in this table to match your configuration.
4. On the MPS server (MPS01), stop the MPS services to make sure that no more requests can be performed on the MPS server. To do this, follow these steps:
   1. Click Start, click Programs, click Administrative Tools, and then click Services.
   2. Right-click Provisioning Queue Manager Service, and then click Stop.
   3. Click Start, click Program, click Administrative Tools, and then click Component Services.
   4. Expand Component Services, expand Computers, expand My Computer, expand COM+ Applications, right-click Provisioning Engine, and then click Shut down.
5. Log on to the virtual SQL Server 2000 named instance VSQL1\INST1, and then delete the following databases:
   • MPFAudit
   • MPFTranLogData
   • Resource Manager database
6. In Enterprise Manager, use the Copy Database Wizard to move the following database from the MPS server (MPS01) to the virtual SQL Server 2000 named instance VSQL1\INST1:
   • MPFAudit
   • MPFTranLogData
   • Resource Manager databases
   Note You may have to detach and then reattach some databases because of some lock issues.
7. Log on to the first clustered node (dlg1), and then follow these steps:
   1. Rerun the Mpf.msi command and only change the value of the Config Server Name property to VSQL1\INST1.
      
      Note The following registry entry will be updated:

      [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Provisioning] "Configuration Server"="VSQL1\\INST1"

   2. If the Provisioning Engine COM+ application is running on this node, restart the application.
8. Log on to the second clustered node (dlg2), and then follow these steps:
   1. Rerun the Mpf.msi command and only change the value of the Config Server Name property to VSQL1\INST1.
      
      Note The following registry entry will be updated:

      [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Provisioning] "Configuration Server"="VSQL1\\INST1"

   2. If the Provisioning Engine COM+ application is running on this node, restart the application.
9. Log on to the MPS server (MPS01), and then follow these steps:
   1. Rerun the Mpf.msi command and only modify the value of the Config Server Name property to VSQL1\INST1.
      
      Note The following registry entry will be updated:

      [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Provisioning] "Configuration Server"="VSQL1\\INST1"

   2. Restart the MPS service and the Provisioning Engine COM+ application.

Note When a SQL Server 2000 failover occurs, you must restart the Provisioning Queue Manager service.

back to the top