Switching Protection If the Primary DPM Server Fails

Applies To: System Center Data Protection Manager 2007

If the primary DPM server fails, the secondary DPM server can continue protection of protected computers. To continue protection, you must switch protection of the protected computers to the secondary DPM server. After you have switched protection to the secondary DPM server, you can also use it to perform recovery functions.

Important

To recover Windows SharePoint Services data directly from the secondary DPM server to the protected computer when Windows SharePoint Services uses an instance of SQL Server on another computer, you must switch protection for both the Windows SharePoint Services server and the SQL Server-based computer to the secondary DPM server.

To switch protection to the secondary DPM server

• On the secondary DPM server, in DPM Management Shell, run the Start-ProductionServerSwitchProtection cmdlet.

  -or-

• On the secondary DPM server, at a command prompt, run the Switch-Protection.ps1 script, using the following syntax:

  Switch-Protection.ps1 -dpmservername Name -psname Name -protectiontype Type -username User -password Password -domain Domain

Switch-Protection.ps1 Parameters

Parameter	Description
-dpmservername	The name of the server to which you are switching protection
-psname	The name of the protected computer for which you are switching protection
-protectiontype	The type of protection the server will provide: primary or secondary
-username -password	Credentials for an account with domain administrator privileges
-domain	The domain to which the protection computer belongs

When the primary DPM server is available again, you switch protection back to the primary DPM server to enable the primary DPM server to resume protection of the computers. You must also switch protection on the secondary DPM server to enable it to resume secondary protection of the data sources protected by the primary DPM server.

When you resume secondary protection, the replicas for the protected data sources are inactive. You must add the data sources to a protection group on the secondary DPM server again, using the automatic replica creation option, and then the replicas will become active.

Note

After you resume secondary protection, if the replicas are not inactive, run Switch-Protection.ps1 on the secondary DPM server again.

Example

The following example shows how to switch primary protection for computer SQL1 to the secondary DPM server, DPM2, for recovery or continued protection, by running the following command on DPM2:

Switch-Protection.ps1 -dpmservername  dpm2 -psname sql1 -protectiontype primary  -username administrator -password Pass123 -domain dc990

The following example shows how to switch primary protection for computer SQL1 back to the primary DPM server, DPM1.

First, run the following command on DPM1:

Switch-Protection.ps1 -dpmservername  dpm1 -psname sql1 -protectiontype primary -username administrator -password Pass123 -domain dc990

Second, run the following command on DPM2:

Switch-Protection.ps1 -dpmservername  dpm2 -psname sql1 -protectiontype secondary  -username administrator -password Pass123 -domain dc990

Note

The Switch-Protection.ps1 script is available on the DPM 2007 product DVD. During DPM setup, the script is installed to the installation path at \Microsoft DPM\DPM\bin.

See Also

Concepts

Backing Up DPM by Using a Secondary DPM Server
Recovering Protected Computers