repost from : scug.dk
One of my favorite features in Data Protection Manager is the ability to easily protect remote DPM servers and keep a extra copy of protected data offsite
This part will show how to protect a DPM server data , there will be a separate post on what is needed to be able to recover the DPM server if a hardware failure occurs and also the ability to switch protection servers.
On the 2nd server in the is case DemoDPM02 we need to push a agent install to the source DPM server DemoDPM01
Regular Install of DPM Agent
With the test setup being Windows 2008 R2 no hotfixes or reboots are needed so a fast install.
And we can see the agent showing up in unprotected computer group
In this example we have a DPM server (DemoDPM01) that contains a protection group that have 10 days retention range to disk locally
Then we need to setup a protection group
When we select the DemoDPM01 we have a new group called Protected Servers , there we can browse to the server that we want to create a additional copy of.
We will setup the protection group to disk as no libraries are in the DemoDPM02 Server
The flexibility of DPM is show here where we can make a separate retention range for the data so we don’t need to keep the data at the same retention range on both sites.
If you go into “modify synchronization start time” its possible to enable over the wire compression at the cost of cpu usage but on low bandwidth or lines where traffic is charged its recommended.
and as with normal agent install we need to sync the data set the first time.
And after a short wait we have data moved to the second DPM server
And now we have a replication between the 2 DPM servers , very easy to setup and easy to maintain , there needs to be a procedure in place to add the protected servers to the remote DPM group.