Setting Up DPM Chaining
Updated: November 1, 2013
Applies To: System Center 2012 - Data Protection Manager, System Center 2012 SP1 - Data Protection Manager
Chaining, as the name suggests, lets you create a chain of System Center 2012 – Data Protection Manager (DPM) servers protecting the next DPM server in the chain.
Cyclic protection is aimed at smaller architectures like in a branch office, where two DPM servers can protect each other.
To set up chaining
Install the DPM protection agent on the DPM server that you want to protect from the DPM server you want to protect it from.
Configure secondary protection for the data sources protected by the DPM server you are protecting.
|In the DPM Administrative Console of one DPM server, you cannot view the data sources that the DPM protection agent already protects. This feature prevents you from protecting data sources repeatedly.|
Assume an architecture where you have two DPM servers, DPM1 and DPM2. Each of these servers protects one or more data sources of their own. To set up chaining for these two servers, do the following:
Install the DPM protection agent from DPM1 to DPM2 and vice versa.
Configure secondary protection on DPM2 for servers that DPM1 protects.
Configure secondary protection on DPM1 for servers that DPM2 protects.
What is protected on the DPM server
In DPM, the secondary DPM server supports protection for the following items from the primary DPM server:
The databases in the instance of SQL Server on the primary DPM server.
All local volumes and application data on the primary DPM server.
All replicas on the primary DPM server that the primary DPM server directly protects.
For additional resources, see Information and Support for System Center 2012.
Tip: Use this query to find online documentation in the TechNet Library for System Center 2012. For instructions and examples, see Search the System Center 2012 Documentation Library.