Export (0) Print
Expand All

Preparing your environment for System Center 2012 R2 Data Protection Manager (DPM)

Updated: July 9, 2014

Applies To: System Center 2012 R2 Data Protection Manager

Keep these requirements and considerations in mind when you deploy System Center 2012 R2 Data Protection Manager (DPM).

If you’re evaluating your environment, see System Requirements for System Center 2012 R2

There are a few prerequisites you’ll need to have in place before you deploy DPM:

  • Instance of SQL Server installed and running for the DPM database.

  • Disk to be used as dedicated space for DPM data storage.

  • DPM protection agent installed on computers and servers you want to protect using DPM.

DPM uses SQL Server as a database to store backup information for workloads, servers, and computers it protects.

 

Requirement Details

Version

SQL Server 2012 with SP1 Standard or Enterprise 64-bit

SQL Server 2012 Standard or Enterprise 64-bit

SQL Server 2008 R2 with SP2 Standard or Enterprise 64-bit

SQL Server 2008 R2 with SP1 2012 Standard or Enterprise 64-bit

RAM

4 GB minimum, 8 GB recommended

Disk

1 GB minimum, 3 GB recommended

Required features

Database Engine Services, Reporting Services

Collations

SQL_Latin1_General_CP1_CI_AS

Dynamic ports

Supported

AlwaysOn

Not supported

Installation

Install SQL Server on a remote server, or on the DPM server. It must be installed and running before you install DPM.

Remote installation

Clustered SQL Server

Supported

SQL Server 2014

Not supported

 

Requirement Details

Hardware

See Hardware Requirements for System Center 2012 R2.

Software

Windows Server 2012 R2, Datacenter and Standard editions

Windows Server 2012, Datacenter and Standard editions

Windows Server 2008 R2 with SP1, Standard and Enterprise editions

Installation prerequisites

Microsoft .NET Framework 4.0

Windows Installer 4.5 or later versions

Microsoft Visual C++ 2008 Redistributable

Microsoft Visual C++ 2008 Redistributable

Windows PowerShell 3.0

Windows Single Instance Store (SIS)

Microsoft Application Error Reporting

Setup automatically installs these if they aren’t already installed.

Limitations

You can install DPM on the operating system volume or on a different volume. 

DPM is designed to run on a dedicated, single-purpose server. Don’t install DPM on:

  • A server running the Application Server role

  • An Operations Manager Management server

  • A server running Exchange

  • A server running on a cluster node

DPM isn’t supported on the Turkish language version of any of the supported Windows Server versions.

 

Requirement Minimum Recommended

Disk

DPM requires:

  • Disk for DPM installation—system files, installation files, prerequisite software, database files

  • Disk dedicated to the storage pool

DPM installation

DPM installation location: 3 GB

Database files drive: 900 MB

System drive: 1 GB

The system drive disk space is required if SQL Server is installed on the DPM server. If SQL Server is remote, you’ll need considerably less disk space for the system drive.

On each protected volume you’ll need a minimum of 300 MB of free space for the change journal. In addition you’ll need space because DPM copies the file catalog to a temporary DPM installation location for archiving. We recommend that the DPM installation volume has 2–3 GB of free space.

Disk for storage pool

1.5 times the size of the protected data

2-3 times the size of the protected data

Logical unit number (LUN)

Maximum of 17 TB for GUID partition table (GPT) dynamic disks

2 TB for master boot record (MBR) disks

Requirements are based on the maximum size of the disk that appears in the operating system.

Limitations

DPM storage pools must be dynamic.

You can’t install DPM on the disk used for the storage pool.

You can attach or associate custom volumes with protected data sources. Custom volumes can be on basic or dynamic disks but you can’t manage the space on these volumes in the DPM Administrator console.

You can only back up to tape with iSCSI attached tape libraries. We recommend a separate adapter for that connection.

Virtualized DPM

When DPM is running on a virtual machine it can use this storage:

  • .VHD disk that meet the configuration requirements listed in Installing DPM in a virtual environment.

  • Passthrough disk with host direct attached storage (DAS)

  • Pass-through iSCSI LUN attached to a host.

  • Passthrough Fibre Channel LUN attached to a host.

  • iSCSI target LUN connected directly to the DPM virtual machine.

  • Fibre Channel LUN connected to the DPM virtual machine using a Windows Server 2012 Virtual Fiber Channel (VFC) controller.

 

Requirement Details

Protected workload size limits

DPM can protect up to 600 volumes. 300 replica volumes and 300 recovery point volumes

At the maximum size protected sources are typically spread across approximately 75 servers and 150 client computers.

To protect this maximum size, DPM needs 120 TB per DPM server, with 80 TB replica space with a maximum recovery point size of 40 TB.

.NET framework

All protected computers need at least .NET Framework 4.0 installed before you install the DPM protection agent.

Protected workloads

  • Computers running client operating systems

  • Computers running server operating systems

  • File Server

  • SQL Server

  • Exchange server

  • SharePoint server

  • Hyper-V server

Review the Support Matrix for DPM Protection for more details.

Prerequisites

DPM protection agent must be installed on protected computers. For more information, see Installing and Configuring Protection Agents.

Protected volumes must be at least 1 GB in size with NTFS formatting.

Server operating systems protected by DPM must be 64-bit.

 

Requirement Details

Domain

The DPM server should be in a Windows Server 2012 R2, Windows Server 2012, Windows Server 2008 R2, Windows Server 2008, or Windows Server 2003 Active Directory domain.

Domain trust

DPM supports data protection across forests as long as you establish a forest-level two-way trust between the separate forests.

DPM can protect servers and workstations across domains within a forest that has a two-way trust relationship with the DPM server domain. If there’s no two-way trust DPM can provide protection for computers in workgroups or untrusted domains.  Managing Protected Computers in Workgroups and Untrusted Domains.

Network configuration

If you’re protecting data over a wide area network (WAN), you’ll need a minimum bandwidth of 512 kilobits per second (Kbps).

DPM doesn’t support disjointed namespaces.

 

Requirement Details

Central Console

Use the Central Console to administer multiple DPM servers from a single location.

Install it on a server running System Center 2012 Operations Manager. You’ll also need to install the Operations Management agent on the DPM server. See Installing Central Console.

DPM Management Shell

Install the DPM Management Shell on a client computer to directly manage one or more DPM servers using Windows PowerShell. Install it from DPM Setup.

The DPM Management Shell can be installed on computers running Windows Server 2008 R2, Windows Server 2012, Windows Server 2012 R2, Windows 7, Windows 8, Windows 8.1. The computer must be running at least Net Framework 4.0.

Remote Desktop Connection

Set up a Remote Desktop Connection to manage a single DPM server.

The DPM Administrator console can’t be installed on a remote computer.

The DPM Management Shell can be installed on computers running Windows Server 2008 R2, Windows Server 2012, Windows Server 2012 R2, Windows 7, Windows 8, Windows 8.1. The computer must be running at least Net Framework 4.0.

 
Was this page helpful?
(1500 characters remaining)
Thank you for your feedback
Show:
© 2014 Microsoft