Table of contents
TOC
Collapse the table of content
Expand the table of content

Preparing your environment for System Center 2016 Data Protection Manager

Markgal|Last Updated: 2/7/2017
|
3 Contributors

Applies To: System Center 2016 - Data Protection Manager

Keep these requirements and considerations in mind when you deploy System Center 2016 Data Protection Manager (DPM). If you’re evaluating your environment, see System Requirements for System Center 2016.

First things first

Decide how you want to deploy DPM:

  • As a physical standalone server—You can deploy DPM as a physical standalone server to back up on-premises data. Note that physical DPM servers can’t be deployed in a cluster, but you can manage multiple physical servers from a single console by installing Central Console on System Center Operations Manager.

  • As a Hyper-V virtual machine—You can run DPM as a virtual machine hosted on an on-premises Hyper-V host server, to back up on-premises data. For a list of considerations in this environment see Install DPM as a virtual machine on an on-premises Hyper-V server.

  • As a Windows virtual machine in VMWare—From DPM 2012 R2 with Update 5 onwards, you can deploy DPM to provide protection for Microsoft workloads running on Windows virtual machines in VMWare. In this scenario DPM can be deployed as a physical standalone server, as a Hyper-V virtual machine, or as a Windows virtual machine in VMWare.

  • As an Azure virtual machine—From DPM 2012 R2 Update 3 onwards you can run DPM as a virtual machine in Azure to back up cloud workloads running as Azure virtual machines. For information about this deployment see Install DPM as an Azure virtual machine.

In all deployments you’ll need the following:

  • Instance of SQL Server installed and running for the DPM database. The instance can be collocated on the DPM server or remote.
  • 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.

SQL Server database

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

RequirementDetails
VersionSQL Server 2016 - Standard or Enterprise 64-bit (from DPM 2016 R2 with Update Rollup 2 onwards)
SQL Server 2014 with all service packs and updates - Standard or Enterprise 64-bit
SQL Server 2012 SP2 onwards - Standard or Enterprise 64-bit
RAM4 GB minimum, 8 GB recommended
Disk1 GB minimum, 3 GB recommended
Required featuresDatabase Engine Services, Reporting Services
CollationsSQL_Latin1_General_CP1_CI_AS
Dynamic portsSupported
AlwaysOnNot supported
InstallationInstall SQL Server on a remote server, or on the DPM server. It must be installed and running before you install DPM.
Remote installationInstall in the same domain and time zone as the DPM server.
Installing SQL Server on a domain controller is not supported for DPM.
Read about Setting up a remote SQL Server instance.
If you're deploying DPM as an Azure virtual machine you can specify an Azure virtual machine running SQL Server as a remote SQL Server instance. You can't use an on-premises SQL Server. Using an Azure SQL Database isn't currently supported.
Clustered SQL ServerSupported

DPM server

RequirementDetails
HardwareSee Hardware Requirements for System Center 2016
SoftwareWindows Server 2016, Datacenter and Standard editions
Windows Server 2012 R2, Datacenter and Standard editions
Installation prerequisitesMicrosoft .NET Framework 4.0
Windows Installer 4.5 or later versions
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.
LimitationsYou can install DPM on the operation 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 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.

Disks and storage

RequirementMinimumRecommended
DiskDPM requires:
- Disk for DPM installation including system files, installation files, prerequisite software, and database files
- Disk dedicated to the storage pool
DPM installationDPM 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 pool1.5 times the size of the protected data2-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 hard disk that appears in the operating system.
LimitationsDPM storage pools must be dynamic.
You can't install DPM on the dis 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 back up to tape with iSCSI attached tape libraries. We recommend a separate adapter for that connection. If you're running DPM 2012 R2 with Update Rollup 3 or later you can also use virtual tape libraries with a virtual fibre channel adapter. For more information see [Compatible tape libraries]().
Virtualized DPMWhen DPM is running on a virtual machine it can use this storage:
- .VHD disk that meets the configuration requirements listed in installing DPM in a virtual environment.
- Passthrough disk with host direct attached storage (DAS)
- Passthrough 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.

Protected workloads

RequirementDetails
Protected workload size limitsDPM 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 frameworkAll protected computers need at least .NET Framework 4.0 installed before you install the DPM protection agent.
Windows Management Framework (WMF)If you are protecting a server released prior to Windows Server 2012, you must install the appropriate version of WMF before installing the DPM agent:
- WMF 3.0 for Windows Server 2008 SP 2
- WMF 4.0 for Windows 7, Windows Embedded Standard 7, Windows Server 2008 R2
Windows Server 2012 and later do not require a separate installation of WMF.
Protected workloadsReview the DPM protection support matrix for an up-to-date list of protected workloads.
PrerequisitesDPM protection agent must be installed on protected computer. For more information, see Set up the protection agent.

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

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

Networking

RequirementDetails
DomainThe DPM server should be in a Windows Server 2016, Windows Server 2012 R2, Windows Server 2012, Windows Server 2008 R2, Windows Server 2008, or Windows Server 2003 Active Directory domain.
Domain trustDPM 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't provide protection for computers in workgroups or untrusted domains. For more information see [Back up and restore workloads in workgroups and untrusted domains]().
Network configurationIf 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.

Remote management

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

Install it on a server running System Center 2016 Operations Manager. You'll also need to install the Operations Management agent on the DPM server. See [Install Central Console]().
DPM Management ShellInstall the DPM Management Shell on a client computer to directly manage one or more DPM servers using Windows PowerShell. Install it from the DPM Setup.

The DPM Management Shell can be installed on computers running Windows Server 2008 R2, Windows Server 2012, Windows Server 2012 R2, Windows Server 2016, Windows 7, Windows 8, Windows 8.1, and Windows 10. The computer must be running at least .NET Framework 4.0.
Remote Administration ConsoleSet up a Remote Administration Console 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 Server 2016, Windows 7, Windows 8, Windows 8.1, and Windows 10. The computer must be running at least .NET Framework 4.0.
© 2017 Microsoft