Install a System Center DPM 2012 R2 server
Updated: May 13, 2016
This section provides an example of installing a standard DPM 2012 R2 server or upgrading an existing server from DPM 2012 SP1.
Installation of DPM 2012 R2 is very different from previous versions. In many ways it has been simplified, and once the prerequisite software is installed, a clean installation of DPM only takes approximately ten minutes to complete. We will walk through the entire process for a common setup and upgrade scenarios, however since many of the steps are redundant, we will concentrate more on the parts that are different.
There are three common installation scenarios and several upgrade scenarios. Each one requires that prerequisite software be preinstalled before setup will continue.
For a new installation
Installing DPM 2012 R2 using a pre-installed local dedicated SQL instance.
Installing DPM 2012 R2 using a pre-installed Remote standalone SQL instance.
Installing DPM 2012 R2 using a pre-installed Remote SQL Clustered Instance. This requires a separate SQL Server used for reporting services.
For common upgrade scenarios
Upgrading DPM 2012 SP1 using a local SQL instance to DPM 2012 R2.
Upgrading DPM 2012 SP1 using a remote SQL instance to DPM 2012 R2.
Upgrading DPM 2012 SP1 using a local instance and migrating to a remote SQL server instance during setup.
Upgrading DPM 2012 SP1 using a remote instance and migrating to a local SQL server instance during setup.
Upgrading DPM 2012 SP1 using a local instance and migrating to a remote SQL server Cluster instance during setup.
Upgrading DPM 2012 SP1 using a Local instance and migrating to a different local SQL server instance during setup.
Upgrading DPM 2012 SP1 using a remote instance and migrating to a different remote SQL server instance during setup.
Upgrading DPM 2012 SP1 using a remote instance and migrating to a remote SQL server Cluster instance during setup.
NOTE There is no direct upgrade from DPM 2012 to DPM 2012 R2. You must be running DPM 2012 SP1 with UR3 KB2877075 (4.0.3417.0) or later in order to upgrade to DPM 2012 R2.
Installation and Upgrade Steps
Log onto the computer that will host DPM (or the existing DPM computer) using a domain user account that is a member of the Local Administrators group.
Run setup.exe from the root of the DPM 2012 R2 installation media. The DPM Setup screen should appear. See below for the explaination of the three sections: Install, Before you begin and Additional Resources.
Install
Data Protection Manager: This option installs DPM 2012 on the computer where you launched the setup wizard.
DPM Central Console: Installing this will allow users to manage multiple DPM servers using an Operations Manager console, or to manage DPM 2010 servers using a standalone DPM console.
DPM Protection Agent: This allows users to install the protection agent directly from the DPM media.
DPM Remote Administration: Remote administration allows users to manage different DPM servers from a single location. This is just a remote console which allows standard DPM functionality but not the advanced features available when leveraging Operations Manager.
DPM Self Service Recovery: This will install the files necessary to use the DPM Self Service Recovery (SSR) tool to recover SQL files from remote computers without the need for the DPM console.
DPM Remote SQL Prep: This gives users the ability to run SQL prep against a SQL installation in order to prepare it to be used as a remote SQL instance for a DPM 2012 R2 installation.
Before you begin
View Release Notes: This is self-explanatory and will open a copy of the release notes.
Read Installation Guide: This will open up a walkthrough for the installation procedures and notes.
Run the Prerequisite Checker: This will direct users to a web location.
Additional Resources
Review License Terms: Gives a view of the Data Protection Manager License terms.
Visit DPM Web Site: As expected, this takes users to the public DPM website.
To continue installation, select the Data Protection Manager option. Under the section titled Install.
The Microsoft Software License Terms page will appear. Accept the EULA and click OK.
Setup will then check to see if the prerequisite software is installed on the system. If the setup process is able to install a missing prerequisite it will do so, otherwise you may be prompted to manually install a missing component.
Once the prerequisite checks pass, the Microsoft® System Center 2012 R2 screen will appear.
On the Welcome screen, click Next. Note that if you are doing an upgrade, you may receive additional warnings such as the ones shown below.
On the Prerequisites check page, you will have two choices for SQL Server configuration. These options are different from previous versions of DPM.
Use stand-alone SQL Server: DPM will use either a local or a remote non-clustered SQL Server instance that already exists.
Use clustered SQL Server: DPM will use a SQL Server cluster instance and a separate SQL server for reporting server instance that already exists.
Scale Considerations when using a common Shared Instance
Each DPMDB requires 2.5 GB of additional RAM. For instance, if 12 DPM servers share one instance of SQL Server, the computer running SQL Server must have 32 GB of additional RAM above the Windows recommended.
The disk volume on which the database is stored should have RAID configuration for better performance.
If using a standalone SQL Server, select the Use stand-alone SQL Server option to have DPM use either a local or remote SQL 2008 R2 SP1 or SQL 2012 SP1 instance. Enter the SQL Server name and instance name in the form of SQLSERV\INSTANCE, valid credentials that have permissions to the SQL server, then click the Check and Install button to begin the system prerequisite check process.
If using a SQL cluster, select the Use clustered SQL server to use a remote SQL 2008 R2 SP1 or SQL 2012 SP1 instance. Enter the SQL Server names and instance names in the form of SQLSERV\INSTANCE, valid credentials that have permissions to the SQL servers, then select the Check and Install button to begin the system prerequisite check process.
If this is an upgrade, the Instance of SQL Server box will be prepopulated with the existing SQL Server name and Instance that DPM 2012 SP1 is currently using. The credentials page will be greyed out as it will use current user credential to perform the upgrade.
NOTE The minimum SQL Server version for either the DPMDB or the Reporting Server is SQL Server 2008 R2 SP2 or SQL 2012 SP1. They do not need to be the same versions for each SQL Instance entered.
The Check and Install process will check to be sure all prerequisites are met. Below is a partial list of checks performed during this phase of setup.
OSVersion is Windows 2008 or newer
SQL server instance(s) specified are valid and accessible via TCP connection
SQL Server version(s) are supported via WMI query
Machine CPU speed and Memory requirements are met
Version of Microsoft management Console meets minimum version
Applicable KB's are installed: KB962975,KB975759,KB2279787,KB2223201
Windows PowerShell meets minimum version
.NET requires reboot
SIS Filter is installed
Windows installer meets minimum version
Reboot is required
SQL Server tools are installed
SQL Agent startup type
Library Sharing is enabled
Active Directory check
SQL Edition
Client TCP Enabled
Does remote SQL have DPM installed
Remote DPMDB found (Migration scenario)
Disk Space requirements met (local and remote)
DPM Support file (SQL prep) for remote SQL DB
DPMDB Version
DPMDB backup check
If there are any problems discovered, the DPM setup process will either popup an error message or show what prerequisite check failed in the details panel.
NOTE You can easily view all prerequisite checks and find problems by running the following commands:
CD C:\Program Files\Microsoft System Center 2012 R2\DPM\DPMLogs
Find /I "=" Dpmsetup.log >dpmchecks.txt
Notepad dpmchecks.txt
The following are good check results:
Results = 0
* Exception : expecting the following exception. Ignoring intentionally
* Exception : Ignoring the following exception intentionally
Enter the necessary information on the Product Registration page and click Next.
The setup process will now confirm the amount of space required in order to install DPM on the Installation settings page as shown below. Note that you can change the location of the DPM program files.
For the Microsoft Update Opt-In and Customer feedback options pages, choose the appropriate options and click Next.
Verify the settings on the Summary of Settings page and then select Install or Upgrade to begin the installation.
NOTE The DPMsetup.log file has moved. It is now located in the C:\Program Files\Microsoft System Center 2012 R2\DPM\DPMLogs folder.
When setup is complete, you will see the status along with the firewall rules that DPM added.
The DPMSETUP.LOG will show the details of the specific firewall rules that were added. An example is included here:
Information : Adding Firewall Exceptions ...
Information : Calling netsh process with arguments : advfirewall firewall add rule name="Microsoft System Center 2012 R2 Data Protection Manager" dir=in program="C:\Program Files\Microsoft System Center 2012 R2\DPM\DPM\bin\msdpm.exe" profile=Any action=allow
Information : Calling netsh process with arguments : advfirewall firewall add rule name="Microsoft System Center 2012 R2 Data Protection Manager Replication Agent" dir=in program="C:\Program Files\Microsoft System Center 2012 R2\DPM\DPM\bin\dpmra.exe" profile=Any action=allow
Information : Calling netsh process with arguments : advfirewall firewall add rule name="Microsoft System Center 2012 R2 Data Protection Manager DCOM setting" dir=in action=allow protocol=TCP localport=135 profile=Any
Information : Calling netsh process with arguments : advfirewall firewall set rule group="@FirewallAPI.dll,-28502" new enable=yes
Information : Calling netsh process with arguments : advfirewall firewall add rule name="DPMAM_WCF_SERVICE" dir=in program="C:\Program Files\Microsoft System Center 2012 R2\DPM\DPM\bin\AMSvcHost.exe" profile=Any action=allow
Information : Calling netsh process with arguments : advfirewall firewall add rule name="DPMAM_WCF_PORT" dir=in action=allow protocol=TCP localport=6075 profile=Any After the DPM setup process completes and you press CLOSE, Windows Update will be launched automatically to look for updates.
As was stated in the beginning, DPM 2012 R2 can be deployed in a variety of ways. Hopefully if you need to setup a standalone DPM 2012 R2 server sometime in the future, the example here will help you get up and going as quickly and as trouble free as possible.