Backing Up DPM by Using a Secondary DPM Server cross-forest
Microsoft System Center Data Protection Manager (DPM) 2007 Service Pack 1 (SP1) provides enhanced support for Protecting Data cross-forest In this article I will demonstrate how to backup your Primary DPM server with a Secondary DPM server in different forest.
Introduction:
DPM server can back up other DPM servers. A DPM server that protects data sources directly is called the primary DPM server. A DPM server that protects other DPM servers is called the secondary DPM server. The secondary DPM server can protect both the databases and the replicas on the primary DPM server. A DPM server can provide both secondary protection for another DPM server and primary protection for data sources.
The following illustration shows a sample topology using a primary DPM server and a secondary DPM server. In the illustration, the primary DPM server protects volumes C and D of the file server. The secondary DPM server protects the database of the primary DPM server, and also protects the replicas of volumes C and D of the file server.
Using the topology shown in the illustration, if data loss occurs on the file server, you can recover the data from the primary DPM server. If the primary DPM server fails, the secondary DPM server can continue protection of the file server while the primary DPM server is unavailable, and you can recover the databases and replicas to the rebuilt primary DPM server from the secondary DPM server.
A DPM server that is providing secondary protection cannot be protected by another DPM server. For example, Server1 provides primary protection for Computer1, and Server2 provides secondary protection for Server1. Server1 cannot provide secondary protection for Server2. A primary DPM server cannot be protected by more than one secondary DPM server.
Scenario:
We have two forests Forest 1 and Forest2
Forest1: has lab.lcl domain and the DPM server name is DPM. lab.lcl (Primary DPM) .
Forest2 :has Judytech.local and the DPM server name is DPM2.Judytech.local (Secondary DPM).
In order to backup "DPM.lab.lcl" using "DPM2.Judytech.local" we have to establish a two way forest Trust of Type Forest because DPM needs to query the computer account of the principal DPM in active directory and that needs Kerberos , and the Trust of Type Forest is the only trust supporting Kerberos .
To back up a primary DPM server using a secondary DPM server :
- On the secondary DPM server(DPM2.Judytech.local), install a protection agent on the primary DPM server (DPM. lab.lcl). No restart is required.
- If the server doesn’t appear in the computer list, please type the server name in the Computer name Filed,
Click add , then Next
Type the admin user name and passwod
In the Cluster Warrning press OK
In the Chose restart Method select NO I will restart the selected Computer later
In the summary Window click Install
To enable protection of the replicas, you must establish communications between the secondary DPM server and the data sources protected by the primary DPM server. When local data sources are protected on a cluster node, you should enable protection for each cluster node in addition to the cluster. To establish communications, perform the following steps:
On the Agents tab in the Management task area, select a primary DPM server.
In the Details pane, next to Protected servers enabled for protection, click Modify.
Screen clipping taken: 7/12/2009, 4:39 AM
In the View details of protected computers dialog box, select one or more computers, and then click Enable protection.
Screen clipping taken: 7/12/2009, 4:40 AM
Type the user name and password for a domain account that is a member of the local administrators group on all selected computers, and then click OK.
The Protection enabled column in the View details of protected computers dialog box will change to Yes.
You can use an existing protection group or create a new protection group for the primary DPM servers. The following items can be protected from a primary DPM server on which is protection agent is installed and which is configured for protection:
- The databases in the instance of SQL Server on the primary DPM server
- All volumes on the primary DPM server (Shares will not be visible separately)
- All replicas on the primary DPM server.