0% found this document useful (0 votes)

569 views329 pages

Data Protection Manager

This document provides an overview of how System Center Data Protection Manager (DPM) works to protect data. DPM creates and maintains replicas of protected data sources that are stored on the DPM server's storage pool. Protection agents track changes to protected data and transfer them to the DPM server to synchronize the replicas. The method of synchronization depends on whether file data or application data is being protected. DPM regularly creates recovery points that can be used for data recovery. Protection is managed through protection groups that contain common protection settings for collections of protected data sources.

Uploaded by

tetkaC

We take content rights seriously. If you suspect this is your content, claim it here.

Available Formats

Download as PDF, TXT or read online on Scribd

0% found this document useful (0 votes)

569 views329 pages

Data Protection Manager

Uploaded by

tetkaC

We take content rights seriously. If you suspect this is your content, claim it here.

Available Formats

Download as PDF, TXT or read online on Scribd

You are on page 1/ 329

Overview
Data Protection Manager
How does DPM work?
What can DPM back up?
DPM-compatible tape libraries
Get Started
DPM build versions
DPM release notes
What's new in DPM
What DPM supports
How To
Plan Your DPM Environment
Get ready to deploy DPM servers
Prepare your environment for DPM
Prepare data storage
Identify compatible tape libraries
Identify data sources you want to protect
Install or Upgrade DPM
Install DPM
Upgrade your DPM installation
Add Modern Backup storage
Deduplicate DPM storage
Deploy DPM
Deploy the DPM protection agent
Deploy protection groups
Configure firewall settings
Protect Workloads
Back up Hyper-V virtual machines
Back up Exchange with DPM
Back up SharePoint with DPM
Back up SQL Server with DPM
Back up client computers with DPM
Back up file data with DPM
Back up system state and bare metal
Back up and restore VMware servers
Back up and restore VMM servers
Prepare to back up a generic data source
Prepare machines in workgroups and untrusted domains for backup
Back up the DPM server
Monitor and Manage
Monitor DPM
Set up DPM logging
Generate DPM reports
Use SCOM to manage and monitor DPM servers
Improve replication performance
Use central console to manage DPM servers
Data Protection Manager
2 minutes to read

Every organization needs a business continuity and disaster recovery (BCDR ) strategy to make sure resources are
available during planned and unplanned outages, and that you're able to recover to normal working conditions
when things go wrong. Your BCDR strategy requires keeping your data safe and recoverable, and keeping your
business workloads, applications, and services continuously available. System Center Data Protection Manager
(DPM ) is a robust enterprise backup and recovery system that contributes to your BCDR strategy by facilitating the
backup and recovery of enterprise data.
You can deploy System Center Data Protection Manager (DPM ) for:
Application-aware backup: Application-aware back up of Microsoft workloads, including SQL Server,
Exchange, and SharePoint.
File backup: Back up files, folders and volumes for computers running Windows server and Windows client
operating systems.
System backup: Back up system state or run full, bare-metal backups of physical computers running
Windows server or Windows client operating systems.
Hyper-V backup: Back up Hyper-V virtual machines (VM ) running Windows or Linux. You can back up an
entire VM, or run application-aware backups of Microsoft workloads on Hyper-V VMs running Windows.
Get a full list in What can DPM back up?
DPM can store backup data to:
Disk: For short-term storage DPM backs up data to disk pools.
Azure: For both short-term and long-term storage off-premises, DPM data stored in disk pools can be
backed up to the Microsoft Azure cloud using the Azure Backup service.
Tape: For long-term storage you can back up data to tape, which can then be stored offsite.
When outages occur and source data is unavailable, you can use DPM to easily restore data to the original source
or to an alternate location. That way, if the original data is unavailable because of planned or unexpected issues, you
can easily restore data from an alternate location. DPM uses SQL Server as its database and you protect the DPM
server itself for disaster recovery purposes. The following diagram provides an overview of DPM backup
functionality.
Next steps
Learn more in How does DPM work?
How does DPM work?
12 minutes to read

The method System Center Data Protection Manager (DPM ) uses to protect data varies according to the type of
data being protected, and the method of protection you select. This article serves as a primer for how DPM
functions. It is intended to educate those new to DPM, or those who may have basic questions about how DPM
works. This article covers Disk-Based protection processes, Tape-Based protection processes, recovery process, as
well as the protection policy.

Disk-based protection process

To provide disk-based data protection, the DPM server creates and maintains a replica, or copy, of the data that is
on protected servers. The replicas are stored in the storage pool which consists of a set of disks on the DPM server,
or on a custom volume. The following illustration shows the basic relationship between a protected volume and its
replica.

Whether you are protecting file data or application data, protection begins with the creation of the replica of the
data source.
The replica is synchronized, or updated, at regular intervals according to the settings that you configure. The
method that DPM uses to synchronize the replica depends on the type of data being protected. For more
information, see The File Data Synchronization Process and The Application Data Synchronization Process. If a
replica is identified as being inconsistent, DPM performs a consistency check, which is a block-by-block verification
of the replica against the data source.
A simple example of a protection configuration consists of a DPM server and a protected computer. The computer
is protected when you install a DPM protection agent on the computer and add its data to a protection group.
Protection agents track changes to protected data and transfer the changes to the DPM server. The protection
agent also identifies data on a computer that can be protected and is involved in the recovery process. You must
install a protection agent on each computer that you want to protect by using DPM. Protection agents can be
installed by DPM or you can install protection agents manually using applications such as Systems Management
Server (SMS ).
Protection groups are used to manage the protection of data sources on computers. A protection group is a
collection of data sources that share the same protection configuration. The protection configuration is the
collection of settings that are common to a protection group, such as the protection group name, protection policy,
disk allocations, and replica creation method.
DPM stores a separate replica for each protection group member in the storage pool. A protection group member
can be any of the following data sources:
A volume, share, or folder on a desktop computer, file server, or server cluster.
A storage group on an Exchange server or server cluster
A database of an instance of SQL Server or server cluster
NOTE
DPM does not protect data stored in USB drives.

The file data synchronization process

In DPM, for a file volume or share on a server, the protection agent uses a volume filter and the change journal to
determine which files have changed and then performs a checksum procedure for these files to synchronize only
the changed blocks. During synchronization, these changes are transferred to the DPM server and then applied to
the replica to synchronize the replica with the data source. The following figure illustrates the file synchronization
process.

If a replica becomes inconsistent with its data source, DPM generates an alert that specifies which computer and
which data sources are affected. To resolve the problem, the administrator repairs the replica by initiating a
synchronization with consistency check, also known as simply a consistency check, on the replica. During a
consistency check, DPM performs a block-by-block verification and repairs the replica to bring it back into
consistency with the data source.
You can schedule a daily consistency check for protection groups or initiate a consistency check manually.
At regular intervals that you can configure, DPM creates a recovery point for the protection group member. A
recovery point is a version of the data from which data can be recovered.
The application data synchronization process
For application data, after the replica is created by DPM, changes to volume blocks that belong to application files
are tracked by the volume filter.
How changes are transferred to the DPM server depends on the application and the type of synchronization. The
operation that is labeled synchronization in DPM Administrator Console is analogous to an incremental backup,
and it creates an accurate reflection of the application data when combined with the replica.
During the type of synchronization that is labeled express full backup in DPM Administrator Console, a full
Volume Shadow Copy Service (VSS ) snapshot is created but only changed blocks are transferred to the DPM
server.
Each express full backup creates a recovery point for application data. If the application supports incremental
backups, each synchronization also creates a recovery point. The synchronization type supported by each type of
application data is summarized as follows:
For protected Exchange data, synchronization transfers an incremental VSS snapshot using the Exchange
VSS writer. Recovery points are created for each synchronization and express full backup.
SQL Server databases that are log-shipped, in read-only mode, or that use the simple recovery model do
not support incremental backup. Recovery points are created for each express full backup only. For all other
SQL Server databases, synchronization transfers a transaction log backup, and recovery points are created
for each incremental synchronization and express full backup. The transaction log is a serial record of all the
transactions that have been performed against the database since the transaction log was last backed up.
Windows SharePoint Services and Microsoft Virtual Server do not support incremental backup. Recovery
points are created for each express full backup only.
Incremental synchronizations require less time than performing an express full backup. However, the time required
to recover data increases as the number of synchronizations increases. This is because DPM must restore the last
full backup and then restore and apply all the incremental synchronizations up to the point in time selected for
recovery.
To enable faster recovery time, DPM regularly performs an express full backup, a type of synchronization that
updates the replica to include the changed blocks.
During the express full backup, DPM takes a snapshot of the replica before updating the replica with the changed
blocks. To enable more frequent recovery point objectives, as well as to reduce the data loss window, DPM also
performs incremental synchronizations in the time between two express full backups.
As with the protection of file data, if a replica becomes inconsistent with its data source, DPM generates an alert
that specifies which server and which data source are affected. To resolve the problem, the administrator repairs
the replica by initiating a synchronization with consistency check on the replica. During a consistency check, DPM
performs a block-by-block verification and repairs the replica to bring it back into consistency with the data
sources.
You can schedule a daily consistency check for protection groups or initiate a consistency check manually.
The difference between file data and application data
Data that exists on a file server and which needs to be protected as a flat file qualifies as file data, such as Microsoft
Office files, text files, batch files, and so forth.
Data that exists on an application server and which requires DPM to be aware of the application qualifies as
application data, such as Exchange storage groups, SQL Server databases, Windows SharePoint Services farms,
and Virtual Server.
Each data source is presented in DPM Administrator Console according to the type of protection that you can
select for that data source. For example, in the Create New Protection Group Wizard, when you expand a server
that contains files and is also running Virtual Server and an instance of SQL Server, the data sources are treated as
follows:
If you expand All Shares or All Volumes, DPM displays the shares and volumes on that server and will
protect any data source selected in either of those nodes as file data.
If you expand All SQL Servers, DPM displays the instances of SQL Server on that server and will protect
any data source selected in that node as application data.
If you expand Microsoft Virtual Server, DPM displays the host database and virtual machines on that server
and will protect any data source selected in that node as application data.

Tape-based protection process

When you use short-term disk-based protection and long-term tape-based protection, DPM can back up data from
the replica volume to tape so that there is no impact on the protected computer. When you use tape-based
protection only, DPM backs up the data directly from the protected computer to tape.
DPM protects data on tape through a combination of full and incremental backups from either the protected data
source (for short-term protection on tape or for long-term protection on tape when DPM does not protect the data
on disk) or from the DPM replica (for long-term protection on tape when short-term protection is on disk).
NOTE
If a file was open when the replica was last synchronized, the backup of that file from the replica will be in a crash consistent
state. A crash consistent state of the file will contain all data of the file that was persisted to disk at the time of last
synchronization. This applies only to file system backups. Application backups will always be consistent with the application
state.

For specific backup types and schedules, see Planning Protection Groups

Recovery process
The method of data protection, disk-based or tape-based, makes no difference to the recovery task. You select the
recovery point of data that you want to recover, and DPM recovers the data to the protected computer.
DPM can store a maximum of 64 recovery points for each file member of a protection group. For application data
sources, DPM can store up to 448 express full backups and up to 96 incremental backups for each express full
backup. When storage area limits have been reached and the retention range for the existing recovery points is not
met yet, protection jobs will fail.

NOTE
To support end-user recovery, the recovery points for files are limited to 64 by Volume Shadow Copy Service (VSS).

As explained in The File Data Synchronization Process and The Application Data Synchronization Process, the
process for creating recovery points differs between file data and application data. DPM creates recovery points
for file data by taking a shadow copy of the replica on a schedule that you configure. For application data, each
synchronization and express full backup creates a recovery point.
The following illustration shows how each protection group member is associated with its own replica volume and
recovery point volume.

Administrators recover data from available recovery points by using the Recovery Wizard in DPM Administrator
Console. When you select a data source and point in time from which to recover, DPM notifies you if the data is on
tape, whether the tape is online or offline, and which tapes are needed to complete the recovery.
DPM gives administrators the ability to enable their end users to perform their own recoveries by leveraging the
Previous Versions feature in Windows. If you do not want to provide this capability to your end users, you recover
the data for desktop computers using the using the Recovery Wizard.

Protection policy
DPM configures the protection policy, or schedule of jobs, for each protection group based on the recovery goals
that you specify for that protection group. Examples of recovery goals are as follows:
"Lose no more than 1 hour of production data"
"Provide me with a retention range of 30 days"
"Make data available for recovery for 7 years"
Your recovery goals quantify your organization's data protection requirements. In DPM, the recovery goals are
defined by retention range, data loss tolerance, recovery point schedule, and, for database applications, the express
full backup schedule.
The retention range is how long you need the backed-up data available. For example, do you need data from today
to be available a week from now? Two weeks from now? A year from now?
Data loss tolerance is the maximum amount of data loss, measured in time, that is acceptable to business
requirements, and it will determine how often DPM should synchronize with the protected server by collecting
data changes from the protected server. You can change the synchronization frequency to any interval between 15
minutes and 24 hours. You can also select to synchronize just before a recovery point is created, rather than on a
specified time schedule.
The recovery point schedule establishes how many recovery points of this protection group should be created. For
file protection, you select the days and times for which you want recovery points created. For data protection of
applications that support incremental backups, the synchronization frequency determines the recovery point
schedule. For data protection of applications that do not support incremental backups, the express full backup
schedule determines the recovery point schedule.

NOTE
When you create a protection group, DPM identifies the type of data being protected and offers only the protection options
available for the data.

Auto discovery process

Auto discovery is the daily process by which DPM automatically detects new or removed computers on the
network. Once a day, at a time that you can schedule, DPM sends a small packet (less than 10 kilobytes) to the
closest domain controller. The domain controller responds to the LDAP request with the computers in that domain,
and DPM identifies new and removed computers. The network traffic created by the auto discovery process is
minimal.
Auto discovery does not discover new and removed computers in other domains. To install a protection agent on a
computer in another domain, you must identify the computer by using its fully qualified domain name.

DPM directory structure

When you begin protecting data with DPM, you will notice that the installation path of DPM contains three folders
in the Volumes directory:
\Microsoft DPM\DPM\Volumes\DiffArea
\Microsoft DPM\DPM\Volumes\Replica
\Microsoft DPM\DPM\Volumes\ShadowCopy
The DiffArea folder contains mounted shadow copy volumes that store the recovery points for a data source.
The Replica folder contains mounted replica volumes.
The ShadowCopy folder contains local backup copies of the DPM database. In addition, when you use
DPMBackup.exe to create backup shadow copies of the replicas for archive by third-party backup software, the
backup shadow copies are stored in the ShadowCopy folder.

DPM Telemetry
DPM does not collect any telemetry. If you are sending the data to Azure, the information needed by Azure Backup
is sent to Microsoft. It does not contain any PII.
What can DPM back up?
15 minutes to read

This article details the workloads that DPM can back up.
Use the following matrix for DPM 2016 and Semi-Annual Channel releases: 1801 and 1807:
Workloads – The workload type of technology.
Version – Supported VMM version for the workloads.
DPM installation – The computer/location where you wish to install DPM.
Protection and recovery – List the detailed information about the workloads such as supported storage
container or supported deployment.
Use the following matrix for DPM 2019:
Workloads – The workload type of technology.
Version – Supported VMM version for the workloads.
DPM installation – The computer/location where you wish to install DPM.
Protection and recovery – List the detailed information about the workloads such as supported storage
container or supported deployment.

Protection support matrix

The following sections details the protection support matrix for DPM:
Applications Backup
VM Backup
Linux
Applications Backup
WORKLOAD VERSION DPM INSTALLATION PROTECTION AND RECOVERY

Client computers (64-bit) Windows 10 Physical server Volume, share, folder, files,
deduped volumes
Hyper-V virtual machine
Protected volumes must be
VMware virtual machine 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.
WORKLOAD VERSION DPM INSTALLATION PROTECTION AND RECOVERY

Servers (64-bit) Windows Server 2019, Azure virtual machine Volume, share, folder, file,
2016, 2012 R2, 2012 (when workload is running system state/bare metal),
as Azure virtual machine) deduped volumes

Windows virtual machine in

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

Physical server

On-premises Hyper-V
virtual machine

System Center VMM VMM 2019, 2016 Physical server All deployment scenarios:
Database
Hyper-V virtual machine

SQL Server SQL Server 2019, SQL Physical server All deployment scenarios:
Server 2017, 2016 and database
supported SPs, 2014 and On-premises Hyper-V
supported SPs virtual machine

Azure virtual machine

Windows virtual machine in

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

Exchange Exchange 2019, 2016 Physical server Protect (all deployment

scenarios): Standalone
On-premises Hyper-V Exchange server, database
virtual machine 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 2019, 2016 with Physical server Protect (all deployment
latest SPs scenarios): Farm, frontend
On-premises Hyper-V web server content
virtual machine
Recover (all deployment
Azure virtual machine scenarios): Farm, database,
(when workload is running web application, file or list
as Azure virtual machine) item, SharePoint search,
frontend web server
Windows virtual machine in
VMWare (protects
workloads running in
Windows virtual machine in
VMWare)
VM Backup
WORKLOAD VERSION DPM INSTALLATION PROTECTION AND RECOVERY

Hyper-V host - DPM Windows Server 2019, Physical server Protect: Hyper-V
protection agent on Hyper- 2016, 2012 R2, 2012 computers, Hyper-V VMs
V host server, cluster, or VM On-premises Hyper-V hosted on (cluster shared
virtual machine volumes) CSVs

Recover: Virtual machine,

Item-level recovery of files
and folder, volumes, virtual
hard drives

VMware VMs VMware server 6.0, or 6.5, On-premises Hyper-V VMware VMs on cluster-
6.7 virtual machine shared volumes (CSVs), NFS,
and SAN storage.
Item-level recovery of files
and folders available only
for Windows. VMware
vApps not supported.

Linux
WORKLOAD VERSION DPM INSTALLATION PROTECTION AND RECOVERY

Linux Linux running as Hyper-V On-premises Hyper-V Hyper-V must be running

guest (Hyper-V running on virtual machine on Windows Server 2019,
Windows Server Windows Server 2016,
2016/2019/2012 R2/2012) Windows Server 2012 R2 or
Windows Server 2012.

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.

Protection support matrix

DPM DPM - SYSTEM DPM - SYSTEM PROTECTION AND
WORKLOAD VERSION INSTALLATION CENTER SAC CENTER 2016 RECOVERY

System Center VMM 2016, Physical server Y Y All deployment

VMM VMM 2012, SP1, scenarios:
R2 Hyper-V virtual Database
machine
DPM DPM - SYSTEM DPM - SYSTEM PROTECTION AND
WORKLOAD VERSION INSTALLATION CENTER SAC CENTER 2016 RECOVERY

Client computers Windows 10 Physical server Y Y Volume, share,

(64-bit and 32- folder, files,
bit) Hyper-V virtual deduped
machine volumes

VMware virtual Protected

machine 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 Windows 8.1 Physical server Y Y Volume, share,

(64-bit and 32- folder, files,
bit) Hyper-V virtual deduped
machine 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.
DPM DPM - SYSTEM DPM - SYSTEM PROTECTION AND
WORKLOAD VERSION INSTALLATION CENTER SAC CENTER 2016 RECOVERY

Client computers Windows 8.1 Windows virtual Y Y Volume, share,

(64-bit and 32- machine in folder, files,
bit) VMWare From Update deduped
(protects Rollup 5 onwards volumes
workloads
running in Protected
Windows virtual volumes must be
machine in NTFS. FAT and
VMWare) 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 Windows 8 Physical server Y Y Volume, share,

(64-bit and 32- folder, files,
bit) On-premises deduped
Hyper-V virtual volumes
machine
Protected
volumes must be
NTFS and at least
1 GB.

Client computers Windows 8 Windows virtual Y Y Volume, share,

(64-bit and 32- machine in folder, files,
bit) VMWare deduped
(protects volumes
workloads
running in Protected
Windows virtual volumes must be
machine in NTFS. FAT and
VMWare) FAT32 aren't
supported.

Client computers Windows 7 Physical server Y Y Volume, share,

(64-bit and 32- folder, files,
bit) On-premises deduped
Hyper-V virtual volumes
machine
Protected
volumes must be
NTFS and at least
1 GB.

Client computers Windows 7 Windows virtual Y Y Volume, share,

(64-bit and 32- machine in folder, files,
bit) VMWare deduped
(protects volumes
workloads
running in Protected
Windows virtual volumes must be
machine in NTFS. FAT and
VMWare) 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 Windows Server Azure virtual Y Y Volume, share,

and 64-bit) 2016 machine (when Not Nano server folder, file,
workload is Not Nano server system
running as Azure state/bare metal),
virtual machine) deduped
volumes
Windows virtual
machine in
VMWare
(protects
workloads
running in
Windows virtual
machine in
VMWare)

Physical server

On-premises
Hyper-V virtual
machine
DPM DPM - SYSTEM DPM - SYSTEM PROTECTION AND
WORKLOAD VERSION INSTALLATION CENTER SAC CENTER 2016 RECOVERY

Servers (32-bit Windows Server Azure virtual Y Y Volume, share,

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

Servers (32-bit Windows Server Windows virtual Y Y Volume, share,

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

Servers (32-bit Windows Server Physical server Y Y Volume, share,

and 64-bit) 2012/2012 with folder, file,
SP1 - Datacenter On-premises system
and Standard Hyper-V virtual state/bare metal
machine
DPM must be
running on at
least Windows
Server 2012 R2
to protect
Windows Server
2012 deduped
volumes.

Servers (32-bit Windows Server Azure virtual Y Y Volume, share,

and 64-bit) 2012/2012 with machine (when folder, file
SP1 - Datacenter workload is
and Standard running as Azure DPM must be
virtual machine) running on at
least Windows
Server 2012 R2
to protect
Windows Server
2012 deduped
volumes.
DPM DPM - SYSTEM DPM - SYSTEM PROTECTION AND
WORKLOAD VERSION INSTALLATION CENTER SAC CENTER 2016 RECOVERY

Servers (32-bit Windows Server Windows virtual Y Y Volume, share,

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

Servers (32-bit Windows Server Physical server Y Y Volume, share,

and 64-bit) 2008 R2 SP1 - folder, file,
Standard and On-premises You need to be You need to system
Enterprise Hyper-V virtual running SP1 and install Windows state/bare metal
machine install Windows Management
Management Frame 4.0
Frame 4.0

Servers (32-bit Windows Server Azure virtual Y Y Volume, share,

and 64-bit) 2008 R2 SP1 - machine (when folder, file
Standard and workload is You need to You need to be
Enterprise running as Azure install Windows running SP1 and
virtual machine) Management install Windows
Frame 4.0 Management
Frame 4.0

Servers (32-bit Windows Server Windows virtual Y Y Volume, share,

and 64-bit) 2008 R2 SP1 - machine in folder, file,
Standard and VMWare You need to You need to be system
Enterprise (protects install Windows running SP1 and state/bare metal
workloads Management install Windows
running in Frame 4.0 Management
Windows virtual Frame 4.0
machine in
VMWare)

Servers (32-bit Windows Server Physical server Y Y Volume, share,

and 64-bit) 2008 R2 folder, file,
On-premises system
Hyper-V virtual state/bare metal
machine

Servers (32-bit Windows Server Azure virtual N N Volume, share,

and 64-bit) 2008 R2 machine (when folder, file
workload is
running as Azure
virtual machine)
DPM DPM - SYSTEM DPM - SYSTEM PROTECTION AND
WORKLOAD VERSION INSTALLATION CENTER SAC CENTER 2016 RECOVERY

Servers (32-bit Windows Server Windows virtual N N Volume, share,

and 64-bit) 2008 R2 machine in folder, file,
VMWare system
(protects state/bare metal
workloads
running in
Windows virtual
machine in
VMWare)

Servers (32-bit Windows Server Physical server N N Volume, share,

and 64-bit) 2008 SP2 folder, file,
On-premises system
Hyper-V virtual state/bare metal
machine

Servers (32-bit Windows Server Windows virtual Y Y Volume, share,

and 64-bit) 2008 SP2 machine in folder, file,
VMWare system
(protects state/bare metal
workloads
running in
Windows virtual
machine in
VMWare)

Servers (32-bit Windows Physical server Y Y Volume, share,

and 64-bit) Storage Server folder, file,
2008 SP2 On-premises system
Hyper-V virtual state/bare metal
machine

SQL Server SQL Server 2017 Physical server Y Y (UR5 Onwards) All deployment
scenarios:
On-premises database
Hyper-V virtual
machine

Azure virtual
machine

Windows virtual
machine in
VMWare
(protects
workloads
running in
Windows virtual
machine in
VMWare)
DPM DPM - SYSTEM DPM - SYSTEM PROTECTION AND
WORKLOAD VERSION INSTALLATION CENTER SAC CENTER 2016 RECOVERY

SQL Server SQL Server 2016 Physical server Y Y (UR4 onwards) All deployment
SP1 scenarios:
On-premises database
Hyper-V virtual
machine

Azure virtual
machine

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

SQL Server SQL Server 2016 Physical server Y Y (UR2 Onwards) All deployment
scenarios:
On-premises database
Hyper-V virtual
machine

Azure virtual
machine

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

SQL Server SQL Server 2014 Azure virtual Y Y All deployment

machine (when scenarios:
workload is database
running as Azure
virtual machine)

SQL Server SQL Server 2014 Windows virtual Y Y All deployment

machine in scenarios:
VMWare database
(protects
workloads
running in
Windows virtual
machine in
VMWare)

SQL Server SQL Server 2012 Physical server Y Y All deployment

with SP2 scenarios:
On-premises database
Hyper-V virtual
machine
DPM DPM - SYSTEM DPM - SYSTEM PROTECTION AND
WORKLOAD VERSION INSTALLATION CENTER SAC CENTER 2016 RECOVERY

SQL Server SQL Server 2012 Azure virtual Y Y All deployment

with SP2 machine (when scenarios:
workload is database
running as Azure
virtual machine)

SQL Server SQL Server 2012 Windows virtual Y Y All deployment

with SP2 machine in scenarios:
VMWare database
(protects
workloads
running in
Windows virtual
machine in
VMWare)

SQL Server SQL Server 2012, Physical server Y Y All deployment

SQL Server 2012 scenarios:
with SP1 On-premises database
Hyper-V virtual
machine

SQL Server SQL Server 2012, Azure virtual Y Y All deployment

SQL Server 2012 machine (when scenarios:
with SP1 workload is database
running as Azure
virtual machine)

SQL Server SQL Server 2012, Windows virtual Y Y All deployment

SQL Server 2012 machine in scenarios:
with SP1 VMWare database
(protects
workloads
running in
Windows virtual
machine in
VMWare)

SQL Server SQL Server 2008 Physical server Y Y All deployment

R2 scenarios:
On-premises database
Hyper-V virtual
machine

SQL Server SQL Server 2008 Azure virtual Y Y All deployment

R2 machine (when scenarios:
workload is database
running as Azure
virtual machine)
DPM DPM - SYSTEM DPM - SYSTEM PROTECTION AND
WORKLOAD VERSION INSTALLATION CENTER SAC CENTER 2016 RECOVERY

SQL Server SQL Server 2008 Windows virtual Y Y All deployment

R2 machine in scenarios:
VMWare database
(protects
workloads
running in
Windows virtual
machine in
VMWare)

SQL Server SQL Server 2008 Physical server Y Y All deployment

scenarios:
On-premises database
Hyper-V virtual
machine

SQL Server SQL Server 2008 Azure virtual Y Y All deployment

machine (when scenarios:
workload is database
running as Azure
virtual machine)

SQL Server SQL Server 2008 Windows virtual Y Y All deployment

machine in scenarios:
VMWare database
(protects
workloads
running in
Windows virtual
machine in
VMWare)

Exchange Exchange 2016 Physical server Y Y Protect (all

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