Step-by-step: How to setup or upgrade a DPM 2012 standalone server


Updated: May 13, 2016

This section introduces the steps by steps guide of installing or upgrading of a System Center 2012 R2 Data Protection Manager (DPM) standalone server. The installation and the upgrade process is similar. However, you cannot upgrade a DPM 2012 server directly to DPM 2012 R2.

Types of Deployments

DPM 2012 R2 can be deployed in a variety of ways:

  • As a physical standalone server: You can deploy DPM as a physical standalone server to backup 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.

Please note that the installation example in this document is for a physical standalone server.

In this section

Read the following articles for the guide on installing or upgrading a System Center 2012 R2 Data Protection Manager (DPM) standalone server.

  • Installation Requirements

  • Installing and Configuring a SQL Server

  • Installing the DPM 2012 R2 server