Set up chaining
Updated: April 2, 2014
Applies To: System Center 2012 - Data Protection Manager, System Center 2012 SP1 - Data Protection Manager
You can create a chain of primary and secondary System Center 2012 – Data Protection Manager (DPM) servers, so that each preceding link in the chain (acting as a primary server) is protected by the one that follows it (its secondary server). Protection includes the databases in the instance of SQL Server used on theprimary server, all local volumes and application data on the primary, and all replicas on the primary server that the primary directly protects.
Set up chaining as follows:
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. Note in the DPM console you won’t be able to configure protection for data sources that are already protected by the agent. This prevents you from repeatedly protecting data.
As an example, let’s assume an architecture for 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 you’d 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.
Note that in a primary to secondary backup configuration (chained or cyclic) all DPM servers must be running the same operation system version, service packs, and updates.
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.