Decide where to locate DPM servers
Updated: November 1, 2013
Applies To: System Center 2012 - Data Protection Manager, System Center 2012 R2 Data Protection Manager, System Center 2012 SP1 - Data Protection Manager
When considering locations for System Center 2012 - Data Protection Manager (DPM) deployment, note the following:
DPM must be deployed in Windows Server 2012 R2, Windows Server 2012, Windows Server 2008 or Windows Server 2003 Active Directory Domain Services (AD DS) to support its protection and recovery operations.
DPM can protect servers and workstations across domains within a forest that has a two-way trust relationship with the domain that the DPM server is located in. If there is not a two-way trust across domains, you must have a separate DPM server for each domain.
DPM supports data protection across forests as long as you establish a forest-level, two-way trust between the separate forests. To set up a forest-level trust relationship, both domains must be in Windows Server 2008 forest mode.
When deciding where to locate your DPM server, consider the network bandwidth between the DPM server and the protected computers. If you are protecting data over a wide area network (WAN), there is a minimum network bandwidth requirement of 512 kilobits per second (Kbps).
DPM supports teamed network adapters (NICs) . Teamed NICs are multiple physical adapters that are configured to be treated as a single adapters by the operating system. Teamed NICs provide increased bandwidth by combining the bandwidth available using each adapter, and failover to the remaining adapter when an adapter fails. DPM can use the increased bandwidth achieved by using teamed adapter on the DPM server.
Another consideration for the location of your DPM servers is the need to manage tapes and tape libraries manually, such as adding new tapes to the library or removing tapes for offsite archive.
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.