System Center Data Protection Manager (DPM) 2010 and Disaster Recovery
In System Center Data Protection Manager (DPM) 2007 SP1, you can protect only the primary DPM server with a secondary DPM server. With System Center Data Protection Manager (DPM) 2010 Beta allows more complex and cost-effective disaster recovery scenarios through cyclic protection and chaining.
Cyclic protection enables two DPM servers to protect each other, and is typically aimed at smaller architectures, such as in a branch office.
Chaining allows you to create a chain of DPM servers in which each server protects the next server in the chain.
In DPM 2010 Beta, a secondary DPM server can be used to protect the following:
- 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 are directly protected by primary DPM server.
Before you configure secondary protection for your servers, you must ensure that the DPM server or selected DPM servers are not being protected by other DPM servers. Before you can protect the replicas and database of the primary DPM server, you must start the DPM Writer and SQL Server VSS Writer services on the primary DPM server.
If the primary DPM server fails, the secondary DPM server can continue protection of protected computers. To continue protection, you must switch protection to the secondary DPM server by clicking the critical data sources of the selected protection group and select Switch disaster protection.
The Display pane shows the protected computer (secondary DPM server) as Protection-Switched.
When the primary DPM server is available again, you must switch protection back to the primary DPM server to enable the primary DPM server to resume protection of the protected computers. by right-click the critical data sources of the selected protection groups for which protection has been switched, and then select Switch disaster protection
