What can DPM back up?

Use the System Center Data Protection Manager (DPM) support matrix to review the workloads that can be protected. In the following table, the Workload column is the workload type or technology. The Version column lists the supported workload versions. Client computers and Server workloads are broken out by operating system Version because the DPM installation and Protection and recovery details vary. DPM installation lists where the DPM software can be installed. Protection and recovery lists details about the workload, such as supported storage container, or supported deployment. Use the matrix for DPM 2016 and Semi-Annual Channel releases: 1801 and 1807.

Protection support matrix

Workload Version DPM installation DPM - System Center SAC DPM - System Center 2016 Protection and recovery
System Center VMM VMM 2016,
VMM 2012, SP1, R2
Physical server

Hyper-V virtual machine
Y Y All deployment scenarios: Database
Client computers (64-bit and 32-bit) Windows 10 Physical server

Hyper-V virtual machine

VMware virtual machine
Y Y Volume, share, folder, files, deduped volumes

Protected volumes must be NTFS. FAT and FAT32 aren't supported.

Volumes must be at least 1 GB. DPM uses Volume Shadow Copy Service (VSS) to take the data snapshot and the snapshot only works if the volume is at least 1 GB.
Client computers (64-bit and 32-bit) Windows 8.1 Physical server

Hyper-V virtual machine
Y Y Volume, share, folder, files, deduped volumes

Protected volumes must be NTFS. FAT and FAT32 aren't supported.

Volumes must be at least 1 GB. DPM uses Volume Shadow Copy Service (VSS) to take the data snapshot and the snapshot only works if the volume is at least 1 GB.
Client computers (64-bit and 32-bit) Windows 8.1 Windows virtual machine in VMWare (protects workloads running in Windows virtual machine in VMWare) Y Y

From Update Rollup 5 onwards
Volume, share, folder, files, deduped volumes

Protected volumes must be NTFS. FAT and FAT32 aren't supported.

Volumes must be at least 1 GB. DPM uses Volume Shadow Copy Service (VSS) to take the data snapshot and the snapshot only works if the volume is at least 1 GB.
Client computers (64-bit and 32-bit) Windows 8 Physical server

On-premises Hyper-V virtual machine
Y Y Volume, share, folder, files, deduped volumes

Protected volumes must be NTFS and at least 1 GB.
Client computers (64-bit and 32-bit) Windows 8 Windows virtual machine in VMWare (protects workloads running in Windows virtual machine in VMWare) Y Y Volume, share, folder, files, deduped volumes

Protected volumes must be NTFS. FAT and FAT32 aren't supported.

Volumes must be at least 1 GB. DPM uses Volume Shadow Copy Service (VSS) to take the data snapshot and the snapshot only works if the volume is at least 1 GB.
Client computers (64-bit and 32-bit) Windows 7 Physical server

On-premises Hyper-V virtual machine
Y Y Volume, share, folder, files, deduped volumes

Protected volumes must be NTFS and at least 1 GB.
Client computers (64-bit and 32-bit) Windows 7 Windows virtual machine in VMWare (protects workloads running in Windows virtual machine in VMWare) Y Y Volume, share, folder, files, deduped volumes

Protected volumes must be NTFS. FAT and FAT32 aren't supported.

Volumes must be at least 1 GB. DPM uses Volume Shadow Copy Service (VSS) to take the data snapshot and the snapshot only works if the volume is at least 1 GB.
Servers (32-bit and 64-bit) Windows Server 2016 Azure virtual machine (when workload is running as Azure virtual machine)

Windows virtual machine in VMWare (protects workloads running in Windows virtual machine in VMWare)

Physical server

On-premises Hyper-V virtual machine
Y

Not Nano server
Y
Not Nano server
Volume, share, folder, file, system state/bare metal), deduped volumes
Servers (32-bit and 64-bit) Windows Server 2012 R2 - Datacenter and Standard Azure virtual machine (when workload is running as Azure virtual machine) Y Y Volume, share, folder, file

DPM must be running on at least Windows Server 2012 R2 to protect Windows Server 2012 deduped volumes.
Servers (32-bit and 64-bit) Windows Server 2012 R2 - Datacenter and Standard Windows virtual machine in VMWare (protects workloads running in Windows virtual machine in VMWare) Y Y Volume, share, folder, file, system state/bare metal)

DPM must be running on Windows Server 2012 or 2012 R2 to protect Windows Server 2012 deduped volumes.
Servers (32-bit and 64-bit) Windows Server 2012/2012 with SP1 - Datacenter and Standard Physical server

On-premises Hyper-V virtual machine
Y Y Volume, share, folder, file, system state/bare metal

DPM must be running on at least Windows Server 2012 R2 to protect Windows Server 2012 deduped volumes.
Servers (32-bit and 64-bit) Windows Server 2012/2012 with SP1 - Datacenter and Standard Azure virtual machine (when workload is running as Azure virtual machine) Y Y Volume, share, folder, file

DPM must be running on at least Windows Server 2012 R2 to protect Windows Server 2012 deduped volumes.
Servers (32-bit and 64-bit) Windows Server 2012/2012 with SP1 - Datacenter and Standard Windows virtual machine in VMWare (protects workloads running in Windows virtual machine in VMWare) Y Y Volume, share, folder, file, system state/bare metal

DPM must be running on at least Windows Server 2012 R2 to protect Windows Server 2012 deduped volumes.
Servers (32-bit and 64-bit) Windows Server 2008 R2 SP1 - Standard and Enterprise Physical server

On-premises Hyper-V virtual machine
Y

You need to be running SP1 and install Windows Management Frame 4.0
Y

You need to install Windows Management Frame 4.0
Volume, share, folder, file, system state/bare metal
Servers (32-bit and 64-bit) Windows Server 2008 R2 SP1 - Standard and Enterprise Azure virtual machine (when workload is running as Azure virtual machine) Y

You need to install Windows Management Frame 4.0
Y

You need to be running SP1 and install Windows Management Frame 4.0
Volume, share, folder, file
Servers (32-bit and 64-bit) Windows Server 2008 R2 SP1 - Standard and Enterprise Windows virtual machine in VMWare (protects workloads running in Windows virtual machine in VMWare) Y

You need to install Windows Management Frame 4.0
Y

You need to be running SP1 and install Windows Management Frame 4.0
Volume, share, folder, file, system state/bare metal
Servers (32-bit and 64-bit) Windows Server 2008 R2 Physical server

On-premises Hyper-V virtual machine
Y Y Volume, share, folder, file, system state/bare metal
Servers (32-bit and 64-bit) Windows Server 2008 R2 Azure virtual machine (when workload is running as Azure virtual machine) N N Volume, share, folder, file
Servers (32-bit and 64-bit) Windows Server 2008 R2 Windows virtual machine in VMWare (protects workloads running in Windows virtual machine in VMWare) N N Volume, share, folder, file, system state/bare metal
Servers (32-bit and 64-bit) Windows Server 2008 SP2 Physical server

On-premises Hyper-V virtual machine
N N Volume, share, folder, file, system state/bare metal
Servers (32-bit and 64-bit) Windows Server 2008 SP2 Windows virtual machine in VMWare (protects workloads running in Windows virtual machine in VMWare) Y Y Volume, share, folder, file, system state/bare metal
Servers (32-bit and 64-bit) Windows Storage Server 2008 SP2 Physical server

On-premises Hyper-V virtual machine
Y Y Volume, share, folder, file, system state/bare metal
SQL Server SQL Server 2017 Physical server

On-premises Hyper-V virtual machine

Azure virtual machine

Windows virtual machine in VMWare (protects workloads running in Windows virtual machine in VMWare)
Y Y (UR5 Onwards) All deployment scenarios: database
SQL Server SQL Server 2016 SP1 Physical server

On-premises Hyper-V virtual machine

Azure virtual machine

Windows virtual machine in VMWare (protects workloads running in Windows virtual machine in VMWare)
Y Y (UR4 onwards) All deployment scenarios: database
SQL Server SQL Server 2016 Physical server

On-premises Hyper-V virtual machine

Azure virtual machine

Windows virtual machine in VMWare (protects workloads running in Windows virtual machine in VMWare)
Y Y (UR2 Onwards) All deployment scenarios: database
SQL Server SQL Server 2014 Azure virtual machine (when workload is running as Azure virtual machine) Y Y All deployment scenarios: database
SQL Server SQL Server 2014 Windows virtual machine in VMWare (protects workloads running in Windows virtual machine in VMWare) Y Y All deployment scenarios: database
SQL Server SQL Server 2012 with SP2 Physical server

On-premises Hyper-V virtual machine
Y Y All deployment scenarios: database
SQL Server SQL Server 2012 with SP2 Azure virtual machine (when workload is running as Azure virtual machine) Y Y All deployment scenarios: database
SQL Server SQL Server 2012 with SP2 Windows virtual machine in VMWare (protects workloads running in Windows virtual machine in VMWare) Y Y All deployment scenarios: database
SQL Server SQL Server 2012, SQL Server 2012 with SP1 Physical server

On-premises Hyper-V virtual machine
Y Y All deployment scenarios: database
SQL Server SQL Server 2012, SQL Server 2012 with SP1 Azure virtual machine (when workload is running as Azure virtual machine) Y Y All deployment scenarios: database
SQL Server SQL Server 2012, SQL Server 2012 with SP1 Windows virtual machine in VMWare (protects workloads running in Windows virtual machine in VMWare) Y Y All deployment scenarios: database
SQL Server SQL Server 2008 R2 Physical server

On-premises Hyper-V virtual machine
Y Y All deployment scenarios: database
SQL Server SQL Server 2008 R2 Azure virtual machine (when workload is running as Azure virtual machine) Y Y All deployment scenarios: database
SQL Server SQL Server 2008 R2 Windows virtual machine in VMWare (protects workloads running in Windows virtual machine in VMWare) Y Y All deployment scenarios: database
SQL Server SQL Server 2008 Physical server

On-premises Hyper-V virtual machine
Y Y All deployment scenarios: database
SQL Server SQL Server 2008 Azure virtual machine (when workload is running as Azure virtual machine) Y Y All deployment scenarios: database
SQL Server SQL Server 2008 Windows virtual machine in VMWare (protects workloads running in Windows virtual machine in VMWare) Y Y All deployment scenarios: database
Exchange Exchange 2016 Physical server

On-premises Hyper-V virtual machine
Y Y Protect (all deployment scenarios): Standalone Exchange server, database under a database availability group (DAG)

Recover (all deployment scenarios): Mailbox, mailbox databases under a DAG

Backup of Exchange over ReFS not supported
Exchange Exchange 2016 Windows virtual machine in VMWare (protects workloads running in Windows virtual machine in VMWare) Y Y Protect (all deployment scenarios): Standalone Exchange server, database under a database availability group (DAG)

Recover (all deployment scenarios): Mailbox, mailbox databases under a DAG

Backup of Exchange over ReFS not supported
Exchange Exchange 2013 Physical server

On-premises Hyper-V virtual machine
Y Y Protect (all deployment scenarios): Standalone Exchange server, database under a database availability group (DAG)

Recover (all deployment scenarios): Mailbox, mailbox databases under a DAG

Backup of Exchange over ReFS not supported
Exchange Exchange 2013 Windows virtual machine in VMWare (protects workloads running in Windows virtual machine in VMWare) Y Y Protect (all deployment scenarios): Standalone Exchange server, database under a database availability group (DAG)

Recover (all deployment scenarios): Mailbox, mailbox databases under a DAG

Backup of Exchange over ReFS not supported
Exchange Exchange 2010 Physical server

On-premises Hyper-V virtual machine
Y Y Protect (all deployment scenarios): Standalone Exchange server, database under a database availability group (DAG)

Recover (all deployment scenarios): Mailbox, mailbox databases under a DAG

Backup of Exchange over ReFS not supported
Exchange Exchange 2010 Windows virtual machine in VMWare (protects workloads running in Windows virtual machine in VMWare) Y Y Protect (all deployment scenarios): Standalone Exchange server, database under a database availability group (DAG)

Recover (all deployment scenarios): Mailbox, mailbox databases under a DAG

Backup of Exchange over ReFS not supported
SharePoint SharePoint 2016 Physical server

On-premises Hyper-V virtual machine

Azure virtual machine (when workload is running as Azure virtual machine)

Windows virtual machine in VMWare (protects workloads running in Windows virtual machine in VMWare)
Y Y (UR2 Onwards) Protect (all deployment scenarios): Farm, frontend web server content

Recover (all deployment scenarios): Farm, database, web application, file or list item, SharePoint search, frontend web server

Note that protecting a SharePoint farm that's using the SQL Server 2012 AlwaysOn feature for the content databases isn't supported.
SharePoint SharePoint 2013 Physical server

On-premises Hyper-V virtual machine
Y Y Protect (all deployment scenarios): Farm, frontend web server content

Recover (all deployment scenarios): Farm, database, web application, file or list item, SharePoint search, frontend web server

Note that protecting a SharePoint farm that's using the SQL Server 2012 AlwaysOn feature for the content databases isn't supported.
SharePoint SharePoint 2013 Azure virtual machine (when workload is running as Azure virtual machine) - DPM 2012 R2 Update Rollup 3 onwards Y Y Protect (all deployment scenarios): Farm, SharePoint search, frontend web server content

Recover (all deployment scenarios): Farm, database, web application, file or list item, SharePoint search, frontend web server

Note that protecting a SharePoint farm that's using the SQL Server 2012 AlwaysOn feature for the content databases isn't supported.
SharePoint SharePoint 2013 Windows virtual machine in VMWare (protects workloads running in Windows virtual machine in VMWare) Y Y Protect (all deployment scenarios): Farm, SharePoint search, frontend web server content

Recover (all deployment scenarios): Farm, database, web application, file or list item, SharePoint search, frontend web server

Note that protecting a SharePoint farm that's using the SQL Server 2012 AlwaysOn feature for the content databases isn't supported.
SharePoint SharePoint 2010 Physical server

On-premises Hyper-V virtual machine
Y Y Protect (all deployment scenarios): Farm, SharePoint search, frontend web server content

Recover (all deployment scenarios): Farm, database, web application, file or list item, SharePoint search, frontend web server
SharePoint SharePoint 2010 Azure virtual machine (when workload is running as Azure virtual machine) Y Y Protect (all deployment scenarios): Farm, SharePoint search, frontend web server content

Recover (all deployment scenarios): Farm, database, web application, file or list item, SharePoint search, frontend web server
SharePoint SharePoint 2010 Windows virtual machine in VMWare (protects workloads running in Windows virtual machine in VMWare) Y Y Protect (all deployment scenarios): Farm, SharePoint search, frontend web server content

Recover (all deployment scenarios): Farm, database, web application, file or list item, SharePoint search, frontend web server
Hyper-V host - DPM protection agent on Hyper-V host server, cluster, or VM Windows Server 2016 Physical server

On-premises Hyper-V virtual machine
Y Y Protect: Hyper-V computers, cluster shared volumes (CSVs)

Recover: Virtual machine, Item-level recovery of files and folder, volumes, virtual hard drives
Hyper-V host - DPM protection agent on Hyper-V host server, cluster, or VM Windows Server 2012 R2 - Datacenter and Standard Physical server

On-premises Hyper-V virtual machine
Y Y Protect: Hyper-V computers, cluster shared volumes (CSVs)

Recover: Virtual machine, Item-level recovery of files and folder, volumes, virtual hard drives
Hyper-V host - DPM protection agent on Hyper-V host server, cluster, or VM Windows Server 2012 - Datacenter and Standard Physical server

On-premises Hyper-V virtual machine
Y Y Protect: Hyper-V computers, cluster shared volumes (CSVs)

Recover: Virtual machine, Item-level recovery of files and folder, volumes, virtual hard drives
Hyper-V host - DPM protection agent on Hyper-V host server, cluster, or VM Windows Server 2008 R2 SP1 - Enterprise and Standard Physical server

On-premises Hyper-V virtual machine
Y Y Protect: Hyper-V computers, cluster shared volumes (CSVs)

Recover: Virtual machine, Item-level recovery of files and folder, volumes, virtual hard drives
Hyper-V host - DPM protection agent on Hyper-V host server, cluster, or VM Windows Server 2008 SP2 Physical server

On-premises Hyper-V virtual machine
N N Protect: Hyper-V computers, cluster shared volumes (CSVs)

Recover: Virtual machine, Item-level recovery of files and folder, volumes, virtual hard drives
Linux Linux running as Hyper-V guest On-premises Hyper-V virtual machine Y Y Hyper-V must be running on Windows Server 2012 R2 or Windows Server 2016. Protect: Entire virtual machine

Recover: Entire virtual machine

For a complete list of supported Linux distributions and versions, see the article, Linux on distributions endorsed by Azure.
VMware VMs VMware server 5.5, 6.0, or 6.5 On-premises Hyper-V virtual machine Y N VMware VMs on cluster-shared volumes (CSVs), NFS, and SAN storage.
Item-level recovery of files and folders available only for Windows. VMware vApps not supported.

Cluster support

DPM can protect data in the following clustered applications:

  • File servers

  • SQL Server

  • Hyper-V - But if you're protecting a Hyper-V cluster using scaled-out DPM protection, you can't add secondary protection for the protected Hyper-V workloads.

    For Hyper-V running on Windows Server 2008 R2 make sure you have the updated described in KB 975354 installed. For Hyper-V running on Windows Server 2008 R2 in a cluster configuration make sure you have SP2 and KB 971394 installed.

  • Exchange Server - DPM can protect non-shared disk clusters for supported Exchange Server versions (cluster continuous replication), and can also protect Exchange Server configured for local continuous replication.

  • SQL Server - Note that DPM doesn't support the protection of SQL Server databases hosted on cluster-shared volumes (CSVs).

DPM can protect cluster workloads that are located in the same domain as the DPM server, and in a child or trusted domain. If you want to protect data source in untrusted domains or workgroups you'll need to use NTLM or certificate authentication for a single server, or certificate authentication only for a cluster.