Preparing your environment for System Center Data Protection Manager
When deploying System Center - Data Protection Manager (DPM) 2016 or later, use the following information to plan your environment.
DPM deployment considerations
One of your first decisions is how to deploy DPM. You can deploy DPM:
As a physical standalone server—You can deploy DPM as a physical standalone server to back up on-premises data. 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—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—DPM can run 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:
- A SQL Server instance, installed and running, to use 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. All SQL Server versions should be Standard or Enterprise 64-bit.
- For the supported versions of SQL, use the service packs that are currently in support by Microsoft.
- For the below supported SQL versions, Standard, Enterprise and Datacenter (64-bit) editions are supported, based on the availability.
SQL Server - supported versions
|DPM version||SQL version|
|DPM 2016||SQL Server 2014 SP2; SQL Server 2012 SP4.|
|DPM 2016 UR2 and later||SQL Server 2016 and SPs as detailed here|
|DPM 1801||SQL Server 2016 and SPs as detailed here|
|DPM 1807 and DPM 2019||- SQL Server 2016 and SPs as detailed here
- SQL Server 2017 as detailed here
SQL Server requirements
|RAM||4 GB minimum, 8 GB recommended|
|Disk||1 GB minimum, 3 GB recommended|
|Required features||Database Engine Services, Reporting Services (for DPM 2019, install SSRS with SQL 2017)
- For Remote SQL, database engine and reporting services must be on the same computer. .
- For remote clustered SQL instance, Database Engine must be on the cluster and SSRS must be on a separate computer, which can be the DPM server or any other computer)
|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||Install in the same domain and time zone as the DPM server.
When used to support DPM, a SQL Server can't share a server with a domain controller.
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 Server||Supported|
If you are upgrading SQL Database to SQL 2017, ensure you install SQL SSRS post SQL upgrade.
|Operating System||Windows Server 2019, Datacenter, and Standard editions
Windows Server 2016, Datacenter, and Standard editions
Windows Server 2012 R2, Datacenter, and Standard editions (Not applicable for DPM 2019)
|Installation prerequisites||Microsoft .NET Framework 4.5 or later (for 2019)
Microsoft .NET Framework 4.0
Windows Installer 4.5 or later versions
Windows PowerShell 3.0
Windows Single Instance Store (SIS)
Microsoft Application Error Reporting
SQL management tools (for DPM 2019)
Setup automatically installs the prerequisites if they aren't already installed.
|Limitations||You 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
- Disk for DPM installation including system files, installation files, prerequisite software, and database files
- Disk dedicated to the storages 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.
|Each protected volume requires a minimum of 300 MB of free space for the change journal. Additionally, you'll need space for DPM to copy the file catalog to a temporary DPM installation location, when archiving. 2-3 GB of free space is recommended for the DPM installation volume.|
|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)
Applies only to DPM 2016/2019 servers upgraded from DPM 2012 R2, that use legacy storage pool.
|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.
Applies only to DPM 2016/DPM 2019 servers upgraded from DPM 2012 R2 that used legacy storage pool.
|- 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 back up to tape with iSCSI attached tape libraries. We recommend a separate adapter for that connection. For additional information, see Compatible tape libraries.
|Virtualized DPM||- DPM running on a virtual machine can use the following storage types:
- .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.
|Modern Backup Storage||Uses basic volumes, cannot be on a dynamic disk.
A single DPM server has a soft limit of 120 TB storage.
Storage recommendations for DPM
- Sector Size should always be consistent across underlying storage (i.e. WS storage) to DPM native storage.
- When storage spaces is used to carve out DPM storage, storage spaces is supported on iSCSI and FC controllers as long as the virtual disks created on top of them are non-resilient (Simple with any number of columns)
- Write- Back cache should always be se to zero while using Storage Spaces for DPM storage.
|Protected workload size limits||DPM 2016 and later with Modern Backup Storage do not have LDM limits.
With DPM 2016 and later, you can protect more data per DPM server. Up to 120 TB of storage limit per DPM server has been tested. However, 120 TB is only a soft limit. Validation is underway to test a higher limit. This guidance will be updated post completion of the validation.
|.NET framework||All protected computers need at least .NET Framework 4.0 installed before you install the DPM protection agent.|
|Windows Management Framework (WMF)
(Not applicable of DPM 2019)
|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 workloads||Review the DPM protection support matrix for an up-to-date list of protected workloads.|
|Prerequisites||DPM 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.
|Domain||The DPM server should be in a Windows Server 2019, Windows Server 2016, Windows Server 2012 R2, Windows Server 2012|
|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. Without two-way trust, DPM can't protect computers in workgroups or untrusted domains. For more information, see Back up and restore workloads 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.
|Central Console||Use the Central Console to administer multiple DPM servers from a single location.
Install it on a server running System Center 2016/2019 Operations Manager. You'll also need to install the Operations Management agent on the DPM server. See Install 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 the DPM Setup.
The DPM Management Shell can be installed on computers running:
DPM 2019 : Windows Server 2019, Windows Server 2016, Windows 8.1, and Windows 10
DPM 2016 : Windows Server 2008 R2, Windows Server 2012, Windows Server 2012 R2, Windows Server 2016, Windows 7, Windows 8, Windows 8.1
Note: DPM 2019 supports x64 bit computers only.
|Remote Administration Console||Set up a Remote Administration Console to manage a single DPM server.
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.
Note: DPM 2019 supports X64 bit computers only.