This article covers the installation/upgrade of System Center 2012 R2 Data Protection Manager (DPM 2012 R2, or simply DPM). While the installation and upgrade process is similar, please note that you cannot upgrade a DPM 2012 server directly to DPM 2012 R2. DPM 2012 Service Pack 1 with Update Rollup 3 (V4.1.3417.0) or later is required.

Installation Requirements

At the time of this writing, the software requirements for DPM 2012 R2 are as follows. Some apply only to new installations. Upgrades from DPM 2012 SP1 may not require the items with an asterisk (*)

• Windows Server 2008 R2 SP1 or later.
• DPM upgrade requires DPM 2012 SP1 UR3 (4.1.3417.0) or later.
• Pre-installed SQL Server. Only the latest versions of SQL Server 2008 and SQL Server 2012 are supported. While it is possible to protect SQL Server 2014 using DPM 2012 R2, SQL Server 2014 cannot be used as a DPM configuration database to store backup information for workloads it protects.
• Microsoft .NET Framework 4.0 (setup automatically installs this if not present).
• Visual C++ 2010 Redistributables (setup automatically installs this if not present).
• Windows Single Instance (setup automatically installs this if not present).
• Windows Installer 4.5 or later (setup automatically installs this if not present).
• Windows PowerShell 3.0 (setup automatically installs this if not present).
• Microsoft Application Error Reporting (setup automatically installs this if not present).

For the most current information regarding complete hardware and software requirements for DPM 2012 R2, please see the following:

Preparing your environment for System Center 2012 R2 Data Protection Manager (DPM)

Other Pre-Installation Considerations

Other items of note regarding the installation or upgrade of DPM 2012 R2 include the following:

• As stated above, you must have an instance of SQL Server installed and running for the DPM database. The instance can be collocated on the DPM server or on a remote computer.
• You will need a disk to be used as dedicated space for DPM data storage.
• The DPM protection agent must be installed on computers you want to protect.
• The computer on which you install DPM must be a member of an Active Directory domain.
• You must be logged on to the AD domain and have administrative privileges on the server where you want to upgrade or install DPM 2012 R2.
• You cannot install DPM on the following:
  • A management server for Microsoft System Center Operations Manager. This includes any version of OpsMgr 2007 OpsMgr 2012/OpsMgr 2012 R2.
  • An application server (other than Hyper-V).
  • A computer that has cluster services enabled, including a Hyper-V cluster.

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.

Installing Software Prerequisites

While many of the prerequisites will automatically be installed as needed when running DPM 2012 R2 setup, it is generally a good idea to have these prerequisites installed beforehand. This way, if there are an issue with the installation of a prerequisite it can be addressed before attempting the installation of DPM itself. Below we will go into detail on installing some of the required prerequisites before performing a standard DPM installation.

Update Rollup 3 for System Center 2012 Service Pack 1

If you are performing an upgrade from DPM 2012 SP1 to DPM 2012 R2, you must be running DPM 2012 SP1 UR3 (version 4.1.3417.0) or later. Information on how to obtain and install Update Rollup 3 for System Center 2012 Service Pack 1 can be found in the following Microsoft KB article:

2836751 - Description of Update Rollup 3 for System Center 2012 Service Pack 1 (https://support.microsoft.com/en-us/kb/2836751)

Microsoft .NET Framework 4.0

Microsoft .NET 4.0 is required before DPM 2012 R2 will continue setup. Microsoft .NET Framework 4 is installed by default on Windows Server 2012 and later, however you may receive the error below on Windows Server 2008:

If you encounter the error message “Microsoft .NET Framework 4 is not installed on this computer”, it can be installed manually from the \Redist\DotNetFrameworks folder on the DPM installation media as shown below.

To install, execute dotNetFx40_Full_x86_x64.exe to launch the setup wizard.

Windows Management Framework 3.0

Windows Management Framework 3.0 is required before DPM 2012 R2 will continue setup. WMF 3.0 is installed by default on Windows Server 2012 and later, however you may receive the error below on Windows Server 2008:

If you find that you need to install Windows Management Framework 3.0 manually, it can be download from the following location:

Windows Management Framework 3.0 (http://www.microsoft.com/en-us/download/details.aspx?id=34595)

After the installation is complete, be sure to reboot the computer before continuing setup.

Microsoft .NET Framework 3.5

Microsoft .NET Framework 3.5 is a required prerequisite before you can install the Microsoft SQL Server 2012 SP1 Management tools. DPM 2012 R2 setup requires the Microsoft SQL Server 2012 SP1 Management tools when using a remote SQL Server instance. Note that if you are going to pre-install SQL Server locally, it will install the SQL Management tools as part of SQL setup and you can skip this step.

NOTEWhen using a Remote SQL 2008 R2 server, the Microsoft SQL Server 2012 SP1 management tools are backwards compatible with SQL Server 2008 R2. If SQL 2008 R2 is pre-installed locally on the DPM Server, then the Microsoft SQL Server 2008 R2 Management tools will be used by DPM.

Depending on which operating system you are using for DPM 2012 R2, you can either install .NET 3.5 from the DPM installation media, or you can add it as a Windows Server 2012 feature which will require Windows 2012 installation media.

Installing on Windows Server 2008 computers

Microsoft .NET Framework 3.5 can be installed from the \Redist\DotNetFrameworks folder on the DPM installation media as shown below.

Execute dotNetFx35setup.exe to launch the setup wizard. Be aware that installation of this component requires Internet access.

Installing on Windows Server 2012 and Windows Server 2012 R2 computers

You will need to install .NET Framework 3.5 features from the Add Roles and Features wizard as shown below.

During the feature installation, you will need the Windows installation media. Click on Specify an alternate source path to specify the path to the SXS folder as shown here:

Microsoft SQL Server 2012 SP1 Management tools

When specifying a remote SQL Server 2008 R2 or SQL Server 2012 instance to use for the DPM database, DPM 2012 R2 requires that the Microsoft SQL Server 2012 SP1 management tools be installed on the DPM Server.

NOTEAs mentioned previously, when installing DPM 2012 R2 on Windows Server 2012 or Windows Server 2012 R2, you must install .NET Framework 3.5 Features from the Add Roles and Features wizard prior to installing the SQL Server 2012 SP1 management tools or all of the required tools will fail to be installed properly.

The Microsoft SQL Server 2012 SP1 management tools can be downloaded from the following location:

Microsoft® SQL Server® 2012 Service Pack 1 (SP1) Express

Download SQLManagementStudio_X64_ENU.exe (64-bit) or SQLManagementStudio_x86_ENU.exe (32-bit)and run it to start the wizard.

When the wizard starts, select the installation option, then click on the option New SQL Server stand-alone installation or add features to an existing installation.

Be sure that the following features are selected, then complete the installation:

Verifying Software Prerequisites

To verify if a computer has all of the prerequisites installed prior to installing DPM, you can look in Control Panel -> Programs and Features. The screenshot below shows only the DPM prerequisite software that was installed manually. The .NET 3.5 framework can be seen under Windows features. The below screenshot does not include SQL Server itself for the local DPMDB.

Installing and Configuring a Remote SQL Server (optional)

DPM 2012 R2 requires a preinstalled SQL Server 2008 R2 SP2 or SQL Server 2012 SP1 instance to be specified during setup. The SQL instance can be installed on the local computer, on a remote standalone computer or on a clustered SQL server. The steps below provide an example of the steps necessary to install and configure a remote SQL instance using SQL Server 2008 R2 Service Pack 2.

When you use a remote instance of SQL Server for DPM, please note the following:

• The remote instance of SQL Server must be running SQL Server 2008 R2 with Service Pack 2 or later, or SQL Server 2012 SP1, Standard or Enterprise Edition.
• The remote instance of SQL Server cannot be installed on a domain controller.
• The computer running SQL Server must be located in the same domain as the DPM server.
• For the DPM server to access a remote instance of SQL Server through Windows Firewall, on the remote computer you must configure an incoming exception for SQLservr.exe for the specific instance used so that the necessary TCP protocol ports are not blocked. This is covered in detail in the section below titled Setting SQL Firewall rules on a Remote SQL Server.

Installing the remote SQL server

1. On the product media or network share for the SQL Server 2008 installation media, double-click setup.exe and then in the SQL Server Installation Center, click Installation in the navigation pane.

2. On the Installation page, click New SQL Server stand-alone installation or add features to an existing installation.

3. When the SQL Server 2008 Setup Wizard opens, on the Setup Support Rules page, click Show details and review the status of the support rules and correct any failures before proceeding. When all rules have passed, click OK.

4. On the Product Key page, enter a valid license key, and then Next.

5. On the License terms, accept the terms then then Next.

6. On the Setup Support Files page, click Install.

7. On the Setup Role page, select SQL Server Feature Installation and then click Next.

8. On the Feature Selection page, select the following features and click Next:

• Database Engine Services and both sub features, SQL Server Replication and Full-Text Search
• Reporting Services
• Management Tools – Basic (also enables the Management Tools- Complete feature)
• SQL Client Connectivity SDK

9. Review the Installation Rules and then click Next.

10. On the Instance Configuration page, click Named instance, enter a name for the instance of SQL Server and then click Next.

TIPAvoid instance names used by previous DPM installation instances like MSDPM2010, MSDPM2012 etc. Make the instance name unique but intuitive like DPMSQLDB.

11. Review Disk Space Requirements page, then click Next.

12. On the Server Configuration page, use the following table to configure the SQL Server services.

NOTEIt is recommended to use a single, dedicated domain user account to run SQL Server Agent, SQL Server Database Engine, and SQL Server Reporting Services.

13. On the Database Engine Configuration page, accept Windows authentication mode as the authentication mode, and then in the Specify SQL Server administrators area, add the SQL Server administrators group the user account that you will use to connect to the remote instance of SQL Server when you install DPM. To add your own user account, click Add Current User. You can add additional user accounts if needed.

NOTEEnsure that the user account you use is added to the SQL Server administrators group and to the Local Administrators group on the SQL Server.

14. Retain the default settings on all subsequent pages, and then on the Ready to Install page click Install.

Installing the DPM support files on the remote SQL Server

Install the DPM support files (SQLprep) on the remote SQL Server computer by performing the following steps. If the remote SQL Server is a cluster, install the DPM Support tools on all nodes of the cluster.

1. On the remote SQL Server computer, insert the DPM product DVD and start setup.exe. On the DPM Installation menu, click on the DPM remote SQL Prep option.

2. Follow the steps in the wizard to install the Microsoft Visual C++ 2010 Redistributable package.

3. The DPM support files will be installed automatically.

Setting SQL Firewall rules on a Remote SQL Server

DPM needs to be able to communicate to the remote SQL Server using a few TCP protocol ports. By default, the report server listens for HTTP requests on TCP port 80. The default instance (MSSQLSERVER) of the Database Engine always uses TCP port 1433, however that can be changed.

The SQL Server Browser service allows users to connect to instances of the Database Engine that are not listening on port 1433 without knowing the port number. To use SQL Server Browser, you must open UDP port 1434. On the other hand, a named instance of SQL Server (IE: DPMSQLDB) uses Dynamic ports by default. This can also be changed if desired.

In any case, the current port number used by the Database Engine is listed in the SQL Server error log. You can view the error log using SQL Server Management Studio and connecting to the named instance, then viewing the current log under Management -> SQL Server Logs. Look for "Server is listening on ['any' <ipv4> XXXXX]. Where XXXXX is the port number.

If you want to change the TCP port that the SQL Database Engine is listening on, you can do that using the SQL Server Configuration Manager tool:

SQL Server Configuration Manager

Assigning a TCP/IP port number to the SQL Server Database Engine

1. Within the console pane in SQL Server Configuration Manager, expand SQL Server Network Configuration, then expand Protocols for <instance name> and double-click TCP/IP.

2. In the TCP/IP Properties dialog box on the IP Addresses tab, several IP addresses will appear in the format IP1, IP2, up to IPAll. One of these is for the IP address of the loopback adapter, 127.0.0.1. Additional IP addresses will appear for each IP address on the computer. Right-click each address and then click Properties to identify the IP address that you want to configure.

3. If the TCP Dynamic Ports dialog box contains a 0 value, indicating the Database Engine is listening on dynamic ports, delete the value.

4. In the IPn Properties area box in the TCP Port box, type the port number you want that IP address to listen on and then click OK.

5. In the console pane, click SQL Server Services.

6. In the details pane, right-click SQL Server (<instance name>) and then click Restart to stop and restart SQL Server.

The screen shot below shows Dynamic port 49298 being used. If you wanted to change it to be a static port, you would simply remove the Dynamic port number and enter a static port number under the TCP port.

Now that you know the ports used, you can create the necessary firewall rules to allow communication using those ports.

Opening a static port in Windows Firewall for TCP access

To open the necessary static ports on the remote SQL Server computer, complete the following:

1. On the Start menu, click Run, type WF.msc, and then click OK.

2. In Windows Firewall with Advanced Security, on the left pane, right-click Inbound Rules and then click New Rule in the action pane.

3. In the Rule Type dialog box, select Port, and then click Next.

4. In the Protocol and Portsdialog box, select TCP. Select Specific local ports and then type the port number of the instance of the Database Engine, such as 1433 for the default instance. Click Next.

5. In the Action dialog box, select Allow the connection and then click Next.

6. In the Profile dialog box, select any profiles that describe the computer connection environment when you want to connect to the Database Engine and then click Next.

7. In the Name dialog box, type a name and description for this rule and then click Finish.

Opening dynamic ports in Windows Firewall for TCP access

If using dynamic ports on the remote SQL Server computer, complete the following:

1. Open Services.cpl and locate the SQL Server (Instance_name), then double-click to get the "Path to executable".

2. Copy the path (e.g. C:\program files\Microsoft SQL Server\MSSQL11.Instance_name\MSSQL\binn\SQLservr.exe)

3. On the Start menu, click Run, type WF.msc, and then click OK.

4. In the Windows Firewall with Advanced Security, in the left pane, right-click Inbound Rules, and then click New Rule in the action pane.

5. In the Rule Type dialog box, select Program, and then click Next.

6. In the Program dialog box, select This program path. Click Browse, and navigate to the instance of SQL Server that you want to access through the firewall and select the SQLServr.exe and click Next. By default, SQL Server is at C:\Program Files\Microsoft SQL Server\MSSQL11.Instance_name\MSSQL\Binn\SQLservr.exe.

7. In the Action dialog box, select Allow the connection, and then click Next.

8. In the Profile dialog box, select any profiles that describe the computer connection environment when you want to connect to the Database Engine, and then click Next.

9. In the Name dialog box, type a name and description for this rule, and then click Finish.

NOTE When installing DPM and using a SQL cluster, the remote SQL Reporting Server must have port 80 opened so that the DPM server can connect to SQL reporting during and after setup.

Opening ports in Windows Firewall using the command line (optional)

As an alternate method, you can use the command line below to open the required ports. This will work with both static and dynamic ports. Be aware that certain parameters in the example below may need to be modified for your particular environment.

Netsh advfirewall firewall add rule name=DPM_SQLServr.exe dir=in action=allow program=\"%PROGRAMFILES%\Microsoft SQL Server\MSSQL11.INSTANCE_NAME\MSSQL\binn\SQLservr.exe\" profile=Domain

Netsh advfirewall firewall add rule name=DPM_UDP_Port_1434 dir=in action=allow protocol=UDP localport=1434 profile=Domain

Netsh advfirewall firewall add rule name=DPM_TCP_Port_80 dir=in action=allow protocol=TCP localport=80 profile=Domain

Installing the DPM 2012 R2 server

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.

NEW INSTALLATION SCENARIOS

1. Installing DPM 2012 R2 using a pre-installed local dedicated SQL instance.

2. Installing DPM 2012 R2 using a pre-installed Remote standalone SQL instance.

3. Installing DPM 2012 R2 using a pre-installed Remote SQL Clustered Instance. This requires a separate SQL Server used for reporting services.

COMMON UPGRADE SCENARIOS

1. Upgrading DPM 2012 SP1 using a local SQL instance to DPM 2012 R2.

2. Upgrading DPM 2012 SP1 using a remote SQL instance to DPM 2012 R2.

3. Upgrading DPM 2012 SP1 using a local instance and migrating to a remote SQL server instance during setup.

4. Upgrading DPM 2012 SP1 using a remote instance and migrating to a local SQL server instance during setup.

5. Upgrading DPM 2012 SP1 using a local instance and migrating to a remote SQL server Cluster instance during setup.

6. Upgrading DPM 2012 SP1 using a Local instance and migrating to a different local SQL server instance during setup.

7. Upgrading DPM 2012 SP1 using a remote instance and migrating to a different remote SQL server instance during setup.

8. 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

1. 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.

2. Run setup.exe from the root of the DPM 2012 R2 installation media. The DPM Setup screen should appear:

Note how the setup screen is divided into three sections: Install, Before you begin and Additional Resources. Each is explained below.

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.

3. To continue installation, select the Data Protection Manager option. Under the section titled Install.

4. 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.

5. Once the prerequisite checks pass, the Microsoft® System Center 2012 R2 screen will appear.

6. 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.

7. 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.

NOTEThe 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.

TIP 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, so you can ignore them:

Results = 0
* Exception : expecting the following exception. Ignoring intentionally
* Exception : Ignoring the following exception intentionally

Below are a few samples of some errors and warnings you may receive at this point in the process.
Probably the most common will be the popup message here which is generated if the SQL Server instance specified is not accessible. A firewall is the most likely cause. See the section labeled: Setting SQL Firewall rules on a remote SQL Server to remedy this error.

Text: DPM Setup is unable to connect to the specified instance of SQL Server. (ID: 4307)

You may also receive various user credential based error messages such as those in the screen shot below.

The error messages above were the result of using the default local installation of SQL and not using recommended dedicated accounts or a System Account.

8. Enter the necessary information on the Product Registration page and click Next.

9. 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.

10. For the Microsoft Update Opt-In and Customer feedback options pages, choose the appropriate options and click next.

11. Verify the settings on the Summary of Settings page and then select Install or Upgrade to begin the installation. For a new installation of DPM, the Summary of Settings page will appear as follows:

For an upgrade of DPM, the Summary of Settings page will look more like this:

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 as shown below.

The DPMSETUP.LOG will show the details of the specific firewall rules that were added. An example is included here:

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,

J.C. Hornbeck| Solution Asset PM | Microsoft GBS Management and Security Division

Get the latest System Center news onFacebookandTwitter:

System Center All Up: http://blogs.technet.com/b/systemcenter/

Configuration Manager Support Team blog: http://blogs.technet.com/configurationmgr/ 
Data Protection Manager Team blog: http://blogs.technet.com/dpm/ 
Orchestrator Support Team blog: http://blogs.technet.com/b/orchestrator/ 
Operations Manager Team blog: http://blogs.technet.com/momteam/ 
Service Manager Team blog: http://blogs.technet.com/b/servicemanager 
Virtual Machine Manager Team blog: http://blogs.technet.com/scvmm

The Forefront Endpoint Protection blog : http://blogs.technet.com/b/clientsecurity/
The Forefront Identity Manager blog : http://blogs.msdn.com/b/ms-identity-support/
The Forefront TMG blog: http://blogs.technet.com/b/isablog/
The Forefront UAG blog: http://blogs.technet.com/b/edgeaccessblog/

We had an issue with DPM 2012 R2 UR7 that was released on July 28th, 2015. After installing UR7, expired recovery points on the disk were not getting cleaned up, causing an increase in DPM recovery point volume. The issue is fixed now with this re-release of UR7. Please install the update via Microsoft Update or download it via DPM 2012 R2 UR7 KB just like you install other DPM URs.

Existing customers who already installed UR7 before August 21st, 2015

New UR7 bits will not be pushed via Microsoft Update for the customers who installed UR7 before Aug 21, 2015. So they are advised to follow the below steps:

1. Download the updated UR7 bits from DPM 2012 R2 UR7 KB article
2. Manually install the update on the DPM Server that has older UR7 bits installed. The update will automatically update the pruneshadowcopiesDpm2010.ps1 script to fix the issue.

Note:

1. DPM version(4.2.1338.0) will remain the same with our re-release

2. Please update the Azure Backup Agent to latest version(2.0.8719.0) prior to installing DPM UR7 for cloud backups to work seamlessly.

2. If you are usiong2.

~ Chris Butcher| Senior Support Escalation Engineer

When expanding a server using the (+) symbol to create, add or remove protection in System Center 2012 Data Protection Manager, the DPM console UI may crash. Typically when this occurs you will notice that it only happens for specific servers. The stack shows entries similar to the following:

<FatalServiceError><__System><ID>19</ID><Seq>0</Seq><TimeCreated>6/11/2015 7:34:23 PM</TimeCreated><Source>DpmThreadPool.cs</Source><Line>163</Line><HasError>True</HasError></__System><ExceptionType>NullReferenceException</ExceptionType><ExceptionMessage>Object reference not set to an instance of an object.</ExceptionMessage><ExceptionDetails>System.NullReferenceException: Object reference not set to an instance of an object.
   at Microsoft.Internal.EnterpriseStorage.Dls.UI.ObjectModel.FileSystem.FsDataSource.ToString(String format, IFormatProvider formatProvider)
   at Microsoft.Internal.EnterpriseStorage.Dls.UI.Dpw.ProtectionTreeNodeFactory.AddTreeNode(SelectionPage selectionPage, TreeNode parent, ProtectionGroup group, ProtectableObject protectableObject, Datasource datasource, Boolean includeMountPoints)
   at Microsoft.Internal.EnterpriseStorage.Dls.UI.Dpw.SelectionPage.AddFileSystemDataSources(TreeNode parentNode, IList`1 fileSystemObject, Dictionary`2 sourceList)
   at Microsoft.Internal.EnterpriseStorage.Dls.UI.Dpw.SelectionPage.GenerateApplicationTypes(TreeNode parentNode, ProductionServer productionServer, ICollection`1 poList)
   at Microsoft.Internal.EnterpriseStorage.Dls.UI.Dpw.SelectionPage.ps_DatasourceDetectionEvent(Object sender, ProtectableObjectDetectedEventArgs e)
   at Microsoft.Internal.EnterpriseStorage.Dls.UI.ObjectModel.OMCommon.ProductionServer.IssueDatasourceDetectionComplete(Object param)
   at Microsoft.Internal.EnterpriseStorage.Dls.UI.ObjectModel.Utils.ThreadMarshaller.Raise(Object state)</ExceptionDetails></FatalServiceError>

This can occur if there is bad XML in the tbl_IM_Datasource table for a data source using Mount Points.

As a temporary workaround, clicking on the "Refresh" button will allow the server to expand without crashing the console.

To fix the issue, follow these steps:

1. IMPORTANT:” Backup DPMDB using one of the methods described in the following TechNet article:

Backup methods for the DPM database

2. Launch SQL Server Management Studio and connect to the DPM instance.

3. Open a New Query window.

4. Be sure the DPMDB name is in the drop-down, thus indicating that it is the database you will be using.

5. Paste the following SQL code into the query window.  Change 'FQDN_Server' to the FQDN of the server that causes the UI to crash.  This is line 4 in the actual code.

================BEGIN SCRIPT====================

/*
Issue related to DPM UI crash when expanding a server while creating on modifying a protection group.
This issue seems to be related to Mount Point datasources.

Author: Wilson Souza
Created: 07/27/15
Version: 1.0

Instruction: To fix UI crash for a server, replace FQDN_Serverwith the Full server name where the crash was found.
*/

declare   @DSID GUID,
          @Logical nvarchar(max),
          @servername nvarchar(400)

set @servername = 'FQDN_Server'    --replace with the affected server FQDN here.

declare IM_Datasource_Update Cursor
for
(
  -- This query will return all datasources which are root mount points
  select DataSourceId, LogicalPath
  from tbl_IM_ProtectedObject
  where DataSourceId in
  (
     select DataSourceId
     from tbl_IM_DataSource
     where serverid in
     (
        select serverid
        from tbl_AM_Server
        where servername like @servername
     )
     and AppId = '00000000-0000-0000-0000-000000000000'
  )
  and LogicalPath like '%mountpoint%'
  and ProtectedObjectId = DataSourceId
)

Open IM_Datasource_Update

Fetch next from IM_Datasource_Update
into @dsid, @Logical

-- Creating loop to go thru every datasource that matched the search criteria
while @@FETCH_STATUS = 0
Begin

   -- Update ApplicationPath column on table IM_Datasource with LogicalPath column from im_ProtectedObject table
   update tbl_IM_DataSource
   set ApplicationPath = @Logical
   where DataSourceId = @DSID

   -- Updating column is Active to 0. This was the real change that stopped UI crashes.
   update tbl_IM_MountPoint
   set IsActive = 0
   where @DSID = DataSourceId

   Fetch next from IM_Datasource_Update
   into @dsid, @Logical
end

Close IM_Datasource_Update
Deallocate IM_Datasource_Update

================END SCRIPT====================

5. Close and reopen the DPM Console, then see if the issue still occurs when expanding the server without clicking on Refresh button.

6. If there DPM Console UI no longer crashes then create a manual recovery point for any data sources that belongs to that server or cluster.

Special thanks to my colleague Wilson Souza for creating this solution.

Chris Butcher | Senior Support Escalation Engineer | Microsoft GBS Management and Security Division

Get the latest System Center news onFacebookandTwitter:

System Center All Up: http://blogs.technet.com/b/systemcenter/

Configuration Manager Support Team blog: http://blogs.technet.com/configurationmgr/ 
Data Protection Manager Team blog: http://blogs.technet.com/dpm/ 
Orchestrator Support Team blog: http://blogs.technet.com/b/orchestrator/ 
Operations Manager Team blog: http://blogs.technet.com/momteam/ 
Service Manager Team blog: http://blogs.technet.com/b/servicemanager 
Virtual Machine Manager Team blog: http://blogs.technet.com/scvmm

The Forefront Endpoint Protection blog : http://blogs.technet.com/b/clientsecurity/
The Forefront Identity Manager blog : http://blogs.msdn.com/b/ms-identity-support/
The Forefront TMG blog: http://blogs.technet.com/b/isablog/
The Forefront UAG blog: http://blogs.technet.com/b/edgeaccessblog/

DPM 2012 R2

Update Rollup 8 for System Center 2012 R2 Data Protection Manager has been released and is now available to download. The KB article below describes the issues that are fixed as well as installation instructions for Update Rollup 8 for Microsoft System Center 2012 R2 Data Protection Manager.

For complete details as well as a download link, please see the following:

KB3096378 - Description of Update Rollup 8 for System Center 2012 R2 (https://support.microsoft.com/en-us/kb/3096378)

J.C. Hornbeck| Solution Asset PM | Microsoft GBS Management and Security Division

Get the latest System Center news onFacebookandTwitter:

Main System Center blog: http://blogs.technet.com/b/systemcenter/

Configuration Manager Support Team blog: http://blogs.technet.com/configurationmgr/
Data Protection Manager Team blog: http://blogs.technet.com/dpm/
Orchestrator Team blog: http://blogs.technet.com/b/orchestrator/
Operations Manager Team blog: http://blogs.technet.com/momteam/
Service Manager Team blog: http://blogs.technet.com/b/servicemanager
Virtual Machine Manager Team blog: http://blogs.technet.com/scvmm

Microsoft Intune: http://blogs.technet.com/b/microsoftintune/
WSUS Support Team blog: http://blogs.technet.com/sus/
RMS blog: http://blogs.technet.com/b/rms/
App-V Team blog: http://blogs.technet.com/appv/
MED-V Team blog: http://blogs.technet.com/medv/
Server App-V Team blog: http://blogs.technet.com/b/serverappv

Forefront Endpoint Protection blog: http://blogs.technet.com/b/clientsecurity/
Forefront Identity Manager blog: http://blogs.msdn.com/b/ms-identity-support/
Forefront TMG blog: http://blogs.technet.com/b/isablog/
Forefront UAG blog: http://blogs.technet.com/b/edgeaccessblog/
Application Proxy blog: http://blogs.technet.com/b/applicationproxyblog/
The Surface Team blog: http://blogs.technet.com/b/surface/

DPM 2012 R2 UR8

Just a quick FYI on a new KB article that was published. When you try to use the Microsoft Azure Backup (MAB) offline seeding feature, the import job may fail to continue after it sends the drive to Azure for importing. Additionally, the MAB interface displays the following message:

Waiting for Azure Import Job to complete. Please check on Azure management portal for more information on job status.

Additionally, you may see entries that resemble the following in C:\Program Files\Microsoft Azure Recovery Services Agent\Temp\CBEngineCurr.errlog:

... 44B4 3968 10/21 21:02:21.611 69 AzureServiceManagementHelper.cs(320) 0517B3DB-347D-45A8-9DAB-FD7D1EA7D134 FATAL GetImportJobStatus:: Import job with name 'ImportJobName' is not found 44B4 3968 10/21 21:02:21.611 71 backupasync.cpp(1589) [000000001B73B830] 0517B3DB-347D-45A8-9DAB-FD7D1EA7D134 NORMAL PollAzureImportJob :: Import Job: 'ImportJobName' is in pending state: '1' 44B4 3968 10/21 21:02:21.611 71 backupasync.cpp(1607) [000000001B73B830] 0517B3DB-347D-45A8-9DAB-FD7D1EA7D134 WARNING PollAzureImportJob failed with error code: 1b7afbe0 44B4 3968 10/21 21:02:21.611 71 backupasync.cpp(1184) [000000001B73B830] 0517B3DB-347D-45A8-9DAB-FD7D1EA7D134 WARNING Failed: Hr: = [0x80780054] Offline Backup Progress: Failed" .....

For complete details regarding the cause of this error as well as a resolution, please see the following:

KB3119587 - Microsoft Azure Backup offline seeding is stuck at "Waiting for Azure import job to complete" (https://support.microsoft.com/en-us/kb/3119587)

J.C. Hornbeck| Solution Asset PM | Microsoft GBS Management and Security Division

Get the latest System Center news onFacebookandTwitter:

Main System Center blog: http://blogs.technet.com/b/systemcenter/

Configuration Manager Support Team blog: http://blogs.technet.com/configurationmgr/
Data Protection Manager Team blog: http://blogs.technet.com/dpm/
Orchestrator Team blog: http://blogs.technet.com/b/orchestrator/
Operations Manager Team blog: http://blogs.technet.com/momteam/
Service Manager Team blog: http://blogs.technet.com/b/servicemanager
Virtual Machine Manager Team blog: http://blogs.technet.com/scvmm

Microsoft Intune: http://blogs.technet.com/b/microsoftintune/
WSUS Support Team blog: http://blogs.technet.com/sus/
RMS blog: http://blogs.technet.com/b/rms/
App-V Team blog: http://blogs.technet.com/appv/
MED-V Team blog: http://blogs.technet.com/medv/
Server App-V Team blog: http://blogs.technet.com/b/serverappv

Forefront Endpoint Protection blog: http://blogs.technet.com/b/clientsecurity/
Forefront Identity Manager blog: http://blogs.msdn.com/b/ms-identity-support/
Forefront TMG blog: http://blogs.technet.com/b/isablog/
Forefront UAG blog: http://blogs.technet.com/b/edgeaccessblog/
Application Proxy blog: http://blogs.technet.com/b/applicationproxyblog/
The Surface Team blog: http://blogs.technet.com/b/surface/

DPM 2012 R2

System Center DPM 2012 R2 Update Rollup 8 has been out for a month now, we spent a lot of energy in this UR to focus on quality and are getting good feedback from thousands of customers who already installed the update. As a result, we have now made it an “Important Update” on Microsoft Update, so it will be pushed automatically to wider audience and more customers can benefit from all the reliability fixes.

We would recommend customers to upgrade to UR8, if not done already. Below is a recap of the major reliability fixes we made in DPM UR7 and UR8, for more detailed list of bug fixes and features please refer to respective DPM UR KB articles.

~ Sekar Raju

Hi everyone, Sekar Raju here from the Microsoft DPM and Azure backup team with quick support tip for you. When attempting an Azure backup, you may experience a problem where the backup job fails with the following symptoms:

• In Microsoft Azure Backup, you have a backup job that fails with the following error:

Backup has encountered an irrecoverable error. Contact Microsoft Support for further assistance. (0x086C8)

The Error tab on the Job Details dialog will also contain the following:

Job failed with error (Operation failed.(0x086C8)

• The CloudBackup Event Log contains an Event ID 11 similar to the one below:

Log Name:      CloudBackup
Source:           CloudBackup
Date:              <Date/Time>
Event ID:         11
Task Category: None
Level:              Error
Keywords:     
User:              SYSTEM
Computer:      <ServerName>
Description:
The description for Event ID 11 from source CloudBackup cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
If the event originated on another computer, the display information had to be saved with the event.
The following information was included with the event:
<?xml version="1.0"?>
<CBJob><JobId>84d3f434-df64-4595-af6e-xxxxxxxxxxxx</JobId><JobType>Backup</JobType><JobStatus><JobState>Aborted</JobState><StartFileTime>

1308740310939xxxxx</StartFileTime><EndFileTime>1308740393522xxxxx</EndFileTime><FailedFileLog>
</FailedFileLog><ErrorInfo><ErrorCode>34504</ErrorCode><DetailedErrorCode>-2146233088(or)2137452629</DetailedErrorCode><ErrorParamList><CBErrorParam><Name>DLS_ERROR_CODE_NAME</Name>
<Value>34504</Value></CBErrorParam><CBErrorParam><Name>__ErrorSource__</Name><Value>
Service/None/Client</Value></CBErrorParam></ErrorParamList></ErrorInfo><DatasourceStatus>
<CBDatasourceStatus><JobState>Aborted</JobState><LastCompletedJobState>PreparingMedia
</LastCompletedJobState>…

• The following exception appears in CBEngine.log:

12E4        1488        <Date/Time>        71        prepunmanagedutils.h(120)                84D3F434-DF64-4595-AF6E-F7A271EC0581        WARNING        Error occurred, DlsErrorCode - 34504, Exception - FMException: [ErrorCode:SalMetadataVhdCorrupt, DetailedCode:0, Source:Service/None/Client, Message:Corruption is detected. FMException: [ErrorCode:SalMetadataVhdCorrupt, DetailedCode:0, Source:None, Message:Corruption is detected.]

To fix this problem, install the latest version (2.0.9022.0 or later) of the Microsoft Azure Recovery Services Agent. Here are the steps:

1. Close the Microsoft Azure Backup snap-in if it is still running.
2. Download and install latest Microsoft Azure Recovery Services Agent from here.
3. Launch the Microsoft Azure Backup snap-in.
4. Manually start the backup job by clicking the Back up Now option, or optionally wait for the scheduled backup job to start and complete.
5. If the backup job you started on step 4 fails, manually start the backup job one more time or wait for the next scheduled backup job to start and complete. This is because sometimes the first backup with the new agent may fail with the same error, however subsequent backup jobs will successfully complete.

Hope this helps!

Sekar Raju | Senior Support Engineer | Microsoft

Our Blogs

• Configuration Manager: http://blogs.technet.com/configurationmgr/
• Data Protection Manager: http://blogs.technet.com/dpm/
• Orchestrator: http://blogs.technet.com/b/orchestrator/
• Operations Manager: http://blogs.technet.com/momteam/
• Operations Management Suite: https://blogs.technet.microsoft.com/omsblog/
• Service Manager: http://blogs.technet.com/b/servicemanager
• Virtual Machine Manager: http://blogs.technet.com/scvmm
• Microsoft Intune: https://blogs.technet.microsoft.com/intunesupport/
• WSUS: http://blogs.technet.com/sus/
• AD and Azure RMS: http://blogs.technet.com/b/rms/
• Application Virtualization: http://blogs.technet.com/appv/
• MED-V: http://blogs.technet.com/medv/
• Application Proxy: http://blogs.technet.com/b/applicationproxyblog/
• Forefront Endpoint Protection: http://blogs.technet.com/b/clientsecurity/
• Forefront Identity Manager: http://blogs.msdn.com/b/ms-identity-support/
• Forefront TMG: http://blogs.technet.com/b/isablog/
• Forefront UAG: http://blogs.technet.com/b/edgeaccessblog/

DPM 2012 R2

~ Andy Nadarewistsch | Senior Support Escalation Engineer

Hi everyone, Andy Nadarewistsch here from the Microsoft DPM and Azure backup team with quick support tip for you. When attempting an Azure backup, you may experience a problem where the backup job fails immediately with the following symptoms:

1. In Microsoft Azure Backup, you have a backup job that fails immediately with the following error:

Backup cannot be completed. Error: Operation failed.

The Error tab on the Job Details dialog will also contain the following:

Job failed with error (Operation failed. (0x1D4C2))

2. The CloudBackup Event Log contains an Event ID 11 similar to the one below:

Log Name:      CloudBackup
Source:           CloudBackup
Date:              <Date/Time>
Event ID:         11
Task Category: None
Level:              Error
Keywords:     
User:              SYSTEM
Computer:      <ServerName>
Description:

The backup operation has completed with errors.

Looking at details tab shows something similar to the following:

<?xml version="1.0"?> <CBJob><JobId>601c22e6-2283-487c-9d2f-7721ec21e1bf</JobId><JobType>Backup</JobType><JobStatus><JobState>Aborted</JobState><StartFileTime>130966313434530377</StartFileTime><EndFileTime>130966313434530377</EndFileTime><FailedFileLog></FailedFileLog><ErrorInfo><ErrorCode>120002</ErrorCode><DetailedErrorCode>-2147024773</DetailedErrorCode><ErrorParamList/></ErrorInfo><DatasourceStatus><CBDatasourceStatus><JobState>Aborted</JobState><LastCompletedJobState>Initializing</LastCompletedJobState><ErrorInfo><ErrorCode>120002</ErrorCode><DetailedErrorCode>-2147024773</DetailedErrorCode><ErrorParamList/></ErrorInfo><Datasource><DataSourceId>1377471703</DataSourceId><DataSourceName>D:\</DataSourceName></Datasource><ByteProgress><Total>0</Total><Changed>0</Changed><Progress>0</Progress><Failed>0</Failed></ByteProgress><FileProgress><CurrentFile></CurrentFile><Total>0</Total><Changed>0</Changed><Progress>0</Progress><Failed>0</Failed></FileProgress></CBDatasourceStatus></DatasourceStatus></JobStatus></CBJob>

3. The following exception appears in CBEngine.log:

7F28 11C0 01/08 19:30:13.086 18 dsmfsenumerator.cpp(150) [000000001A86EA60] 8A0B2420-2B0F-4AAF-AE82-2B0A04A0773B WARNING Failed: Hr: = [0x8007007b] : FindFirstFile failed For Dir:\\?\D:\Scratch\\Scratch\*

7F28 11C0 01/08 19:30:13.086 18 fsutils.cpp(2354) 8A0B2420-2B0F-4AAF-AE82-2B0A04A0773B WARNING Failed: Hr: = [0x8007007b] : FindFirstFile failed for Path [\\?\D:\Scratch\\Scratch\], FileSpec [*]

The Cause

This issue typically occurs due to a double backslash (“\\”) in the scratch location path in the registry.

The Fix

To fix this problem, modify the following registry keys to reflect the correct path of the scratch location:

HLKM\Software\Microsoft \Windows Azure Backup\Config\ScratchLocation

HLKM\Software\Microsoft \Windows Azure Backup\Config\CloudBackupProvider\ScratchLocation

Here are the steps:

1. Run Regedit.

2. Navigate to the following Registry keys:

HLKM\Software\Microsoft \Windows Azure Backup\Config\

HLKM\Software\Microsoft \Windows Azure Backup\Config\CloudBackupProvider\

3. In each registry key above, double-click the ScratchLocation value and remove the extra “\” in the path, or modify the path to reflect the correct location. Here’s what it would look like when fixing the paths shown in our screen shots above.

4. Once both registry keys have been edited, click OK and then retest the backup. At this point the backup job should complete successfully.

Hope this helps!

Andy Nadarewistsch | Senior Support Escalation Engineer | Microsoft

Our Blogs

• Configuration Manager: http://blogs.technet.com/configurationmgr/
• Data Protection Manager: http://blogs.technet.com/dpm/
• Orchestrator: http://blogs.technet.com/b/orchestrator/
• Operations Manager: http://blogs.technet.com/momteam/
• Operations Management Suite: https://blogs.technet.microsoft.com/omsblog/
• Service Manager: http://blogs.technet.com/b/servicemanager
• Virtual Machine Manager: http://blogs.technet.com/scvmm
• Microsoft Intune: https://blogs.technet.microsoft.com/intunesupport/
• WSUS: http://blogs.technet.com/sus/
• AD and Azure RMS: http://blogs.technet.com/b/rms/
• Application Virtualization: http://blogs.technet.com/appv/
• MED-V: http://blogs.technet.com/medv/
• Application Proxy: http://blogs.technet.com/b/applicationproxyblog/
• Forefront Endpoint Protection: http://blogs.technet.com/b/clientsecurity/
• Forefront Identity Manager: http://blogs.msdn.com/b/ms-identity-support/
• Forefront TMG: http://blogs.technet.com/b/isablog/
• Forefront UAG: http://blogs.technet.com/b/edgeaccessblog/

DPM 2012 R2

Update Rollup 9 for System Center 2012 R2 Data Protection Manager (DPM 2012 R2 UR9) is now available to download. The KB article below describes the issues that are fixed and also contains the installation instructions for this update.

Please note that this update does not require a restart of the production server if you upgrade from Update Rollup 5 for System Center 2012 R2 Data Protection Manager or later.

Existing Data Protection Manager to Windows Azure customers should upgrade to the latest agent (version 2.0.8719.0 or greater). In case this is not installed, online backups will fail, and no Data Protection Manager to Windows Azure operation will work.

For complete details including issues fixed, installation instructions and a download link, please see the following:

3112306 - Update Rollup 9 for System Center 2012 R2 Data Protection Manager (https://support.microsoft.com/en-us/kb/3112306)

J.C. Hornbeck | Solution Asset PM | Microsoft

Our Blogs

• Configuration Manager: http://blogs.technet.com/configurationmgr/
• Data Protection Manager: http://blogs.technet.com/dpm/
• Orchestrator: http://blogs.technet.com/b/orchestrator/
• Operations Manager: http://blogs.technet.com/momteam/
• Operations Management Suite: https://blogs.technet.microsoft.com/omsblog/
• Service Manager: http://blogs.technet.com/b/servicemanager
• Virtual Machine Manager: http://blogs.technet.com/scvmm
• Microsoft Intune: https://blogs.technet.microsoft.com/intunesupport/
• WSUS: http://blogs.technet.com/sus/
• AD and Azure RMS: http://blogs.technet.com/b/rms/
• Application Virtualization: http://blogs.technet.com/appv/
• MED-V: http://blogs.technet.com/medv/
• Application Proxy: http://blogs.technet.com/b/applicationproxyblog/
• Forefront Endpoint Protection: http://blogs.technet.com/b/clientsecurity/
• Forefront Identity Manager: http://blogs.msdn.com/b/ms-identity-support/
• Forefront TMG: http://blogs.technet.com/b/isablog/
• Forefront UAG: http://blogs.technet.com/b/edgeaccessblog/

We are happy to announce that Update Rollup 7 (UR7) for Microsoft System Center 2012 R2 Data Protection Manager is now available for download. Please see the following Knowledge Base article for complete details about fixes and installation instructions for DPM 2012 R2:

3065246 Update Rollup 7 for System Center 2012 R2 Data Protection Manager

Please note that Microsoft recommends that all of the System Center 2012 R2 subcomponents be upgraded to the same Update Rollup version. You can upgrade different System Center subcomponents in any desired sequence. Be aware that using subcomponents that are at different Update Rollup versions could lead to compatibility issues and is not a Microsoft supported scenario. For all the latest information regarding Update Rollup 7 for System Center 2012 R2 please see the following:

3069110 Description of Update Rollup 7 for System Center 2012 R2

J.C. Hornbeck | Solution Asset PM | Microsoft GBS Management and Security Division

Get the latest System Center news on Facebook and Twitter:

System Center All Up: http://blogs.technet.com/b/systemcenter/

Configuration Manager Support Team blog: http://blogs.technet.com/configurationmgr/ 
Data Protection Manager Team blog: http://blogs.technet.com/dpm/ 
Orchestrator Support Team blog: http://blogs.technet.com/b/orchestrator/ 
Operations Manager Team blog: http://blogs.technet.com/momteam/ 
Service Manager Team blog: http://blogs.technet.com/b/servicemanager 
Virtual Machine Manager Team blog: http://blogs.technet.com/scvmm

Microsoft Intune: http://blogs.technet.com/b/microsoftintune/
WSUS Support Team blog: http://blogs.technet.com/sus/
The RMS blog: http://blogs.technet.com/b/rms/
App-V Team blog: http://blogs.technet.com/appv/
MED-V Team blog: http://blogs.technet.com/medv/
Server App-V Team blog: http://blogs.technet.com/b/serverappv
The Surface Team blog: http://blogs.technet.com/b/surface/
The Application Proxy blog: http://blogs.technet.com/b/applicationproxyblog/

The Forefront Endpoint Protection blog : http://blogs.technet.com/b/clientsecurity/
The Forefront Identity Manager blog : http://blogs.msdn.com/b/ms-identity-support/
The Forefront TMG blog: http://blogs.technet.com/b/isablog/
The Forefront UAG blog: http://blogs.technet.com/b/edgeaccessblog/

This article covers the installation/upgrade of System Center 2012 R2 Data Protection Manager (DPM 2012 R2, or simply DPM). While the installation and upgrade process is similar, please note that you cannot upgrade a DPM 2012 server directly to DPM 2012 R2. DPM 2012 Service Pack 1 with Update Rollup 3 (V4.1.3417.0) or later is required.

Installation Requirements

At the time of this writing, the software requirements for DPM 2012 R2 are as follows. Some apply only to new installations. Upgrades from DPM 2012 SP1 may not require the items with an asterisk (*)

• Windows Server 2008 R2 SP1 or later.
• DPM upgrade requires DPM 2012 SP1 UR3 (4.1.3417.0) or later.
• Pre-installed SQL Server. Only the latest versions of SQL Server 2008 and SQL Server 2012 are supported. While it is possible to protect SQL Server 2014 using DPM 2012 R2, SQL Server 2014 cannot be used as a DPM configuration database to store backup information for workloads it protects.
• Microsoft .NET Framework 4.0 (setup automatically installs this if not present).
• Visual C++ 2010 Redistributables (setup automatically installs this if not present).
• Windows Single Instance (setup automatically installs this if not present).
• Windows Installer 4.5 or later (setup automatically installs this if not present).
• Windows PowerShell 3.0 (setup automatically installs this if not present).
• Microsoft Application Error Reporting (setup automatically installs this if not present).

For the most current information regarding complete hardware and software requirements for DPM 2012 R2, please see the following:

Preparing your environment for System Center 2012 R2 Data Protection Manager (DPM)

Other Pre-Installation Considerations

Other items of note regarding the installation or upgrade of DPM 2012 R2 include the following:

• As stated above, you must have an instance of SQL Server installed and running for the DPM database. The instance can be collocated on the DPM server or on a remote computer.
• You will need a disk to be used as dedicated space for DPM data storage.
• The DPM protection agent must be installed on computers you want to protect.
• The computer on which you install DPM must be a member of an Active Directory domain.
• You must be logged on to the AD domain and have administrative privileges on the server where you want to upgrade or install DPM 2012 R2.
• You cannot install DPM on the following:
  • A management server for Microsoft System Center Operations Manager. This includes any version of OpsMgr 2007 OpsMgr 2012/OpsMgr 2012 R2.
  • An application server (other than Hyper-V).
  • A computer that has cluster services enabled, including a Hyper-V cluster.

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.

Installing Software Prerequisites

While many of the prerequisites will automatically be installed as needed when running DPM 2012 R2 setup, it is generally a good idea to have these prerequisites installed beforehand. This way, if there are an issue with the installation of a prerequisite it can be addressed before attempting the installation of DPM itself. Below we will go into detail on installing some of the required prerequisites before performing a standard DPM installation.

Update Rollup 3 for System Center 2012 Service Pack 1

If you are performing an upgrade from DPM 2012 SP1 to DPM 2012 R2, you must be running DPM 2012 SP1 UR3 (version 4.1.3417.0) or later. Information on how to obtain and install Update Rollup 3 for System Center 2012 Service Pack 1 can be found in the following Microsoft KB article:

2836751 – Description of Update Rollup 3 for System Center 2012 Service Pack 1 (https://support.microsoft.com/en-us/kb/2836751)

Microsoft .NET Framework 4.0

Microsoft .NET 4.0 is required before DPM 2012 R2 will continue setup. Microsoft .NET Framework 4 is installed by default on Windows Server 2012 and later, however you may receive the error below on Windows Server 2008:

If you encounter the error message “Microsoft .NET Framework 4 is not installed on this computer”, it can be installed manually from the \Redist\DotNetFrameworks folder on the DPM installation media as shown below.

To install, execute dotNetFx40_Full_x86_x64.exe to launch the setup wizard.

Windows Management Framework 3.0

Windows Management Framework 3.0 is required before DPM 2012 R2 will continue setup. WMF 3.0 is installed by default on Windows Server 2012 and later, however you may receive the error below on Windows Server 2008:

If you find that you need to install Windows Management Framework 3.0 manually, it can be download from the following location:

Windows Management Framework 3.0 (http://www.microsoft.com/en-us/download/details.aspx?id=34595)

After the installation is complete, be sure to reboot the computer before continuing setup.

Microsoft .NET Framework 3.5

Microsoft .NET Framework 3.5 is a required prerequisite before you can install the Microsoft SQL Server 2012 SP1 Management tools. DPM 2012 R2 setup requires the Microsoft SQL Server 2012 SP1 Management tools when using a remote SQL Server instance. Note that if you are going to pre-install SQL Server locally, it will install the SQL Management tools as part of SQL setup and you can skip this step.

NOTE When using a Remote SQL 2008 R2 server, the Microsoft SQL Server 2012 SP1 management tools are backwards compatible with SQL Server 2008 R2. If SQL 2008 R2 is pre-installed locally on the DPM Server, then the Microsoft SQL Server 2008 R2 Management tools will be used by DPM.

Depending on which operating system you are using for DPM 2012 R2, you can either install .NET 3.5 from the DPM installation media, or you can add it as a Windows Server 2012 feature which will require Windows 2012 installation media.

Installing on Windows Server 2008 computers

Microsoft .NET Framework 3.5 can be installed from the \Redist\DotNetFrameworks folder on the DPM installation media as shown below.

Execute dotNetFx35setup.exe to launch the setup wizard. Be aware that installation of this component requires Internet access.

Installing on Windows Server 2012 and Windows Server 2012 R2 computers

You will need to install .NET Framework 3.5 features from the Add Roles and Features wizard as shown below.

During the feature installation, you will need the Windows installation media. Click on Specify an alternate source path to specify the path to the SXS folder as shown here:

Microsoft SQL Server 2012 SP1 Management tools

When specifying a remote SQL Server 2008 R2 or SQL Server 2012 instance to use for the DPM database, DPM 2012 R2 requires that the Microsoft SQL Server 2012 SP1 management tools be installed on the DPM Server.

NOTE As mentioned previously, when installing DPM 2012 R2 on Windows Server 2012 or Windows Server 2012 R2, you must install .NET Framework 3.5 Features from the Add Roles and Features wizard prior to installing the SQL Server 2012 SP1 management tools or all of the required tools will fail to be installed properly.

The Microsoft SQL Server 2012 SP1 management tools can be downloaded from the following location:

Microsoft® SQL Server® 2012 Service Pack 1 (SP1) Express

Download SQLManagementStudio_X64_ENU.exe (64-bit) or SQLManagementStudio_x86_ENU.exe (32-bit) and run it to start the wizard.

When the wizard starts, select the installation option, then click on the option New SQL Server stand-alone installation or add features to an existing installation.

Be sure that the following features are selected, then complete the installation:

Verifying Software Prerequisites

To verify if a computer has all of the prerequisites installed prior to installing DPM, you can look in Control Panel -> Programs and Features. The screenshot below shows only the DPM prerequisite software that was installed manually. The .NET 3.5 framework can be seen under Windows features. The below screenshot does not include SQL Server itself for the local DPMDB.

Installing and Configuring a Remote SQL Server (optional)

DPM 2012 R2 requires a preinstalled SQL Server 2008 R2 SP2 or SQL Server 2012 SP1 instance to be specified during setup. The SQL instance can be installed on the local computer, on a remote standalone computer or on a clustered SQL server. The steps below provide an example of the steps necessary to install and configure a remote SQL instance using SQL Server 2008 R2 Service Pack 2.

When you use a remote instance of SQL Server for DPM, please note the following:

• The remote instance of SQL Server must be running SQL Server 2008 R2 with Service Pack 2 or later, or SQL Server 2012 SP1, Standard or Enterprise Edition.
• The remote instance of SQL Server cannot be installed on a domain controller.
• The computer running SQL Server must be located in the same domain as the DPM server.
• For the DPM server to access a remote instance of SQL Server through Windows Firewall, on the remote computer you must configure an incoming exception for SQLservr.exe for the specific instance used so that the necessary TCP protocol ports are not blocked. This is covered in detail in the section below titled Setting SQL Firewall rules on a Remote SQL Server.

Installing the remote SQL server

1. On the product media or network share for the SQL Server 2008 installation media, double-click setup.exe and then in the SQL Server Installation Center, click Installation in the navigation pane.

2. On the Installation page, click New SQL Server stand-alone installation or add features to an existing installation.

3. When the SQL Server 2008 Setup Wizard opens, on the Setup Support Rules page, click Show details and review the status of the support rules and correct any failures before proceeding. When all rules have passed, click OK.

4. On the Product Key page, enter a valid license key, and then Next.

5. On the License terms, accept the terms then then Next.

6. On the Setup Support Files page, click Install.

7. On the Setup Role page, select SQL Server Feature Installation and then click Next.

8. On the Feature Selection page, select the following features and click Next:

• Database Engine Services and both sub features, SQL Server Replication and Full-Text Search
• Reporting Services
• Management Tools – Basic (also enables the Management Tools- Complete feature)
• SQL Client Connectivity SDK

9. Review the Installation Rules and then click Next.

10. On the Instance Configuration page, click Named instance, enter a name for the instance of SQL Server and then click Next.

TIP Avoid instance names used by previous DPM installation instances like MSDPM2010, MSDPM2012 etc. Make the instance name unique but intuitive like DPMSQLDB.

11. Review Disk Space Requirements page, then click Next.

12. On the Server Configuration page, use the following table to configure the SQL Server services.

NOTE It is recommended to use a single, dedicated domain user account to run SQL Server Agent, SQL Server Database Engine, and SQL Server Reporting Services.

13. On the Database Engine Configuration page, accept Windows authentication mode as the authentication mode, and then in the Specify SQL Server administrators area, add the SQL Server administrators group the user account that you will use to connect to the remote instance of SQL Server when you install DPM. To add your own user account, click Add Current User. You can add additional user accounts if needed.

NOTE Ensure that the user account you use is added to the SQL Server administrators group and to the Local Administrators group on the SQL Server.

14. Retain the default settings on all subsequent pages, and then on the Ready to Install page click Install.

Installing the DPM support files on the remote SQL Server

Install the DPM support files (SQLprep) on the remote SQL Server computer by performing the following steps. If the remote SQL Server is a cluster, install the DPM Support tools on all nodes of the cluster.

1. On the remote SQL Server computer, insert the DPM product DVD and start setup.exe. On the DPM Installation menu, click on the DPM remote SQL Prep option.

2. Follow the steps in the wizard to install the Microsoft Visual C++ 2010 Redistributable package.

3. The DPM support files will be installed automatically.

Setting SQL Firewall rules on a Remote SQL Server

DPM needs to be able to communicate to the remote SQL Server using a few TCP protocol ports. By default, the report server listens for HTTP requests on TCP port 80. The default instance (MSSQLSERVER) of the Database Engine always uses TCP port 1433, however that can be changed.

The SQL Server Browser service allows users to connect to instances of the Database Engine that are not listening on port 1433 without knowing the port number. To use SQL Server Browser, you must open UDP port 1434. On the other hand, a named instance of SQL Server (IE: DPMSQLDB) uses Dynamic ports by default. This can also be changed if desired.

In any case, the current port number used by the Database Engine is listed in the SQL Server error log. You can view the error log using SQL Server Management Studio and connecting to the named instance, then viewing the current log under Management -> SQL Server Logs. Look for "Server is listening on ['any' <ipv4> XXXXX]. Where XXXXX is the port number.

If you want to change the TCP port that the SQL Database Engine is listening on, you can do that using the SQL Server Configuration Manager tool:

SQL Server Configuration Manager

Assigning a TCP/IP port number to the SQL Server Database Engine

1. Within the console pane in SQL Server Configuration Manager, expand SQL Server Network Configuration, then expand Protocols for <instance name> and double-click TCP/IP.

2. In the TCP/IP Properties dialog box on the IP Addresses tab, several IP addresses will appear in the format IP1, IP2, up to IPAll. One of these is for the IP address of the loopback adapter, 127.0.0.1. Additional IP addresses will appear for each IP address on the computer. Right-click each address and then click Properties to identify the IP address that you want to configure.

3. If the TCP Dynamic Ports dialog box contains a 0 value, indicating the Database Engine is listening on dynamic ports, delete the value.

4. In the IPn Properties area box in the TCP Port box, type the port number you want that IP address to listen on and then click OK.

5. In the console pane, click SQL Server Services.

6. In the details pane, right-click SQL Server (<instance name>) and then click Restart to stop and restart SQL Server.

The screen shot below shows Dynamic port 49298 being used. If you wanted to change it to be a static port, you would simply remove the Dynamic port number and enter a static port number under the TCP port.

Now that you know the ports used, you can create the necessary firewall rules to allow communication using those ports.

Opening a static port in Windows Firewall for TCP access

To open the necessary static ports on the remote SQL Server computer, complete the following:

1. On the Start menu, click Run, type WF.msc, and then click OK.

2. In Windows Firewall with Advanced Security, on the left pane, right-click Inbound Rules and then click New Rule in the action pane.

3. In the Rule Type dialog box, select Port, and then click Next.

4. In the Protocol and Ports dialog box, select TCP. Select Specific local ports and then type the port number of the instance of the Database Engine, such as 1433 for the default instance. Click Next.

5. In the Action dialog box, select Allow the connection and then click Next.

6. In the Profile dialog box, select any profiles that describe the computer connection environment when you want to connect to the Database Engine and then click Next.

7. In the Name dialog box, type a name and description for this rule and then click Finish.

Opening dynamic ports in Windows Firewall for TCP access

If using dynamic ports on the remote SQL Server computer, complete the following:

1. Open Services.cpl and locate the SQL Server (Instance_name), then double-click to get the "Path to executable".

2. Copy the path (e.g. C:\program files\Microsoft SQL Server\MSSQL11.Instance_name\MSSQL\binn\SQLservr.exe)

3. On the Start menu, click Run, type WF.msc, and then click OK.

4. In the Windows Firewall with Advanced Security, in the left pane, right-click Inbound Rules, and then click New Rule in the action pane.

5. In the Rule Type dialog box, select Program, and then click Next.

6. In the Program dialog box, select This program path. Click Browse, and navigate to the instance of SQL Server that you want to access through the firewall and select the SQLServr.exe and click Next. By default, SQL Server is at C:\Program Files\Microsoft SQL Server\MSSQL11.Instance_name\MSSQL\Binn\SQLservr.exe.

7. In the Action dialog box, select Allow the connection, and then click Next.

8. In the Profile dialog box, select any profiles that describe the computer connection environment when you want to connect to the Database Engine, and then click Next.

9. In the Name dialog box, type a name and description for this rule, and then click Finish.

NOTE When installing DPM and using a SQL cluster, the remote SQL Reporting Server must have port 80 opened so that the DPM server can connect to SQL reporting during and after setup.

Opening ports in Windows Firewall using the command line (optional)

As an alternate method, you can use the command line below to open the required ports. This will work with both static and dynamic ports. Be aware that certain parameters in the example below may need to be modified for your particular environment.

Netsh advfirewall firewall add rule name=DPM_SQLServr.exe dir=in action=allow program=\"%PROGRAMFILES%\Microsoft SQL Server\MSSQL11.INSTANCE_NAME\MSSQL\binn\SQLservr.exe\" profile=Domain

Netsh advfirewall firewall add rule name=DPM_UDP_Port_1434 dir=in action=allow protocol=UDP localport=1434 profile=Domain

Netsh advfirewall firewall add rule name=DPM_TCP_Port_80 dir=in action=allow protocol=TCP localport=80 profile=Domain

Installing the DPM 2012 R2 server

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.

NEW INSTALLATION SCENARIOS

1. Installing DPM 2012 R2 using a pre-installed local dedicated SQL instance.

2. Installing DPM 2012 R2 using a pre-installed Remote standalone SQL instance.

3. Installing DPM 2012 R2 using a pre-installed Remote SQL Clustered Instance. This requires a separate SQL Server used for reporting services.

COMMON UPGRADE SCENARIOS

1. Upgrading DPM 2012 SP1 using a local SQL instance to DPM 2012 R2.

2. Upgrading DPM 2012 SP1 using a remote SQL instance to DPM 2012 R2.

3. Upgrading DPM 2012 SP1 using a local instance and migrating to a remote SQL server instance during setup.

4. Upgrading DPM 2012 SP1 using a remote instance and migrating to a local SQL server instance during setup.

5. Upgrading DPM 2012 SP1 using a local instance and migrating to a remote SQL server Cluster instance during setup.

6. Upgrading DPM 2012 SP1 using a Local instance and migrating to a different local SQL server instance during setup.

7. Upgrading DPM 2012 SP1 using a remote instance and migrating to a different remote SQL server instance during setup.

8. 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

1. 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.

2. Run setup.exe from the root of the DPM 2012 R2 installation media. The DPM Setup screen should appear:

Note how the setup screen is divided into three sections: Install, Before you begin and Additional Resources. Each is explained below.

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.

3. To continue installation, select the Data Protection Manager option. Under the section titled Install.

4. 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.

5. Once the prerequisite checks pass, the Microsoft® System Center 2012 R2 screen will appear.

6. 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.

7. 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.

TIP 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, so you can ignore them:

Results = 0
* Exception : expecting the following exception. Ignoring intentionally
* Exception : Ignoring the following exception intentionally

Below are a few samples of some errors and warnings you may receive at this point in the process.
Probably the most common will be the popup message here which is generated if the SQL Server instance specified is not accessible. A firewall is the most likely cause. See the section labeled: Setting SQL Firewall rules on a remote SQL Server to remedy this error.

Text: DPM Setup is unable to connect to the specified instance of SQL Server. (ID: 4307)

You may also receive various user credential based error messages such as those in the screen shot below.

The error messages above were the result of using the default local installation of SQL and not using recommended dedicated accounts or a System Account.

8. Enter the necessary information on the Product Registration page and click Next.

9. 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.

10. For the Microsoft Update Opt-In and Customer feedback options pages, choose the appropriate options and click next.

11. Verify the settings on the Summary of Settings page and then select Install or Upgrade to begin the installation. For a new installation of DPM, the Summary of Settings page will appear as follows:

For an upgrade of DPM, the Summary of Settings page will look more like this:

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 as shown below.

The DPMSETUP.LOG will show the details of the specific firewall rules that were added. An example is included here:

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,

J.C. Hornbeck | Solution Asset PM | Microsoft GBS Management and Security Division

Get the latest System Center news on Facebook and Twitter:

System Center All Up: http://blogs.technet.com/b/systemcenter/

Configuration Manager Support Team blog: http://blogs.technet.com/configurationmgr/ 
Data Protection Manager Team blog: http://blogs.technet.com/dpm/ 
Orchestrator Support Team blog: http://blogs.technet.com/b/orchestrator/ 
Operations Manager Team blog: http://blogs.technet.com/momteam/ 
Service Manager Team blog: http://blogs.technet.com/b/servicemanager 
Virtual Machine Manager Team blog: http://blogs.technet.com/scvmm

Microsoft Intune: http://blogs.technet.com/b/microsoftintune/
WSUS Support Team blog: http://blogs.technet.com/sus/
The RMS blog: http://blogs.technet.com/b/rms/
App-V Team blog: http://blogs.technet.com/appv/
MED-V Team blog: http://blogs.technet.com/medv/
Server App-V Team blog: http://blogs.technet.com/b/serverappv
The Surface Team blog: http://blogs.technet.com/b/surface/
The Application Proxy blog: http://blogs.technet.com/b/applicationproxyblog/

The Forefront Endpoint Protection blog : http://blogs.technet.com/b/clientsecurity/
The Forefront Identity Manager blog : http://blogs.msdn.com/b/ms-identity-support/
The Forefront TMG blog: http://blogs.technet.com/b/isablog/
The Forefront UAG blog: http://blogs.technet.com/b/edgeaccessblog/

We had an issue with DPM 2012 R2 UR7 that was released on July 28th, 2015. After installing UR7, expired recovery points on the disk were not getting cleaned up, causing an increase in DPM recovery point volume. The issue is fixed now with this re-release of UR7. Please install the update via Microsoft Update or download it via DPM 2012 R2 UR7 KB just like you install other DPM URs.

Existing customers who already installed UR7 before August 21st, 2015

New UR7 bits will not be pushed via Microsoft Update for the customers who installed UR7 before Aug 21, 2015. So they are advised to follow the below steps:

1. Download the updated UR7 bits from DPM 2012 R2 UR7 KB article
2. Manually install the update on the DPM Server that has older UR7 bits installed. The update will automatically update the pruneshadowcopiesDpm2010.ps1 script to fix the issue.

Note:

1. DPM version(4.2.1338.0) will remain the same with our re-release

2. Please update the Azure Backup Agent to latest version(2.0.8719.0) prior to installing DPM UR7 for cloud backups to work seamlessly.

~ Chris Butcher | Senior Support Escalation Engineer

When expanding a server using the (+) symbol to create, add or remove protection in System Center 2012 Data Protection Manager, the DPM console UI may crash. Typically when this occurs you will notice that it only happens for specific servers. The stack shows entries similar to the following:

<FatalServiceError><__System><ID>19</ID><Seq>0</Seq><TimeCreated>6/11/2015 7:34:23 PM</TimeCreated><Source>DpmThreadPool.cs</Source><Line>163</Line><HasError>True</HasError></__System><ExceptionType>NullReferenceException</ExceptionType><ExceptionMessage>Object reference not set to an instance of an object.</ExceptionMessage><ExceptionDetails>System.NullReferenceException: Object reference not set to an instance of an object.
   at Microsoft.Internal.EnterpriseStorage.Dls.UI.ObjectModel.FileSystem.FsDataSource.ToString(String format, IFormatProvider formatProvider)
   at Microsoft.Internal.EnterpriseStorage.Dls.UI.Dpw.ProtectionTreeNodeFactory.AddTreeNode(SelectionPage selectionPage, TreeNode parent, ProtectionGroup group, ProtectableObject protectableObject, Datasource datasource, Boolean includeMountPoints)
   at Microsoft.Internal.EnterpriseStorage.Dls.UI.Dpw.SelectionPage.AddFileSystemDataSources(TreeNode parentNode, IList`1 fileSystemObject, Dictionary`2 sourceList)
   at Microsoft.Internal.EnterpriseStorage.Dls.UI.Dpw.SelectionPage.GenerateApplicationTypes(TreeNode parentNode, ProductionServer productionServer, ICollection`1 poList)
   at Microsoft.Internal.EnterpriseStorage.Dls.UI.Dpw.SelectionPage.ps_DatasourceDetectionEvent(Object sender, ProtectableObjectDetectedEventArgs e)
   at Microsoft.Internal.EnterpriseStorage.Dls.UI.ObjectModel.OMCommon.ProductionServer.IssueDatasourceDetectionComplete(Object param)
   at Microsoft.Internal.EnterpriseStorage.Dls.UI.ObjectModel.Utils.ThreadMarshaller.Raise(Object state)</ExceptionDetails></FatalServiceError>

This can occur if there is bad XML in the tbl_IM_Datasource table for a data source using Mount Points.

As a temporary workaround, clicking on the "Refresh" button will allow the server to expand without crashing the console.

To fix the issue, follow these steps:

1. IMPORTANT:” Backup DPMDB using one of the methods described in the following TechNet article:

Backup methods for the DPM database

2. Launch SQL Server Management Studio and connect to the DPM instance.

3. Open a New Query window.

4. Be sure the DPMDB name is in the drop-down, thus indicating that it is the database you will be using.

5. Paste the following SQL code into the query window.  Change 'FQDN_Server' to the FQDN of the server that causes the UI to crash.  This is line 4 in the actual code.

================BEGIN SCRIPT====================

/*
Issue related to DPM UI crash when expanding a server while creating on modifying a protection group.
This issue seems to be related to Mount Point datasources.

Author: Wilson Souza
Created: 07/27/15
Version: 1.0

Instruction: To fix UI crash for a server, replace FQDN_Server with the Full server name where the crash was found.
*/

declare   @DSID GUID,
          @Logical nvarchar(max),
          @servername nvarchar(400)

set @servername = 'FQDN_Server'    –replace with the affected server FQDN here.

declare IM_Datasource_Update Cursor
for
(
  — This query will return all datasources which are root mount points
  select DataSourceId, LogicalPath
  from tbl_IM_ProtectedObject
  where DataSourceId in
  (
     select DataSourceId
     from tbl_IM_DataSource
     where serverid in
     (
        select serverid
        from tbl_AM_Server
        where servername like @servername
     )
     and AppId = '00000000-0000-0000-0000-000000000000'
  )
  and LogicalPath like '%mountpoint%'
  and ProtectedObjectId = DataSourceId
)

Open IM_Datasource_Update

Fetch next from IM_Datasource_Update
into @dsid, @Logical

– Creating loop to go thru every datasource that matched the search criteria
while @@FETCH_STATUS = 0
Begin

   — Update ApplicationPath column on table IM_Datasource with LogicalPath column from im_ProtectedObject table
   update tbl_IM_DataSource
   set ApplicationPath = @Logical
   where DataSourceId = @DSID

   — Updating column is Active to 0. This was the real change that stopped UI crashes.
   update tbl_IM_MountPoint
   set IsActive = 0
   where @DSID = DataSourceId

   Fetch next from IM_Datasource_Update
   into @dsid, @Logical
end

Close IM_Datasource_Update
Deallocate IM_Datasource_Update

================END SCRIPT====================

5. Close and reopen the DPM Console, then see if the issue still occurs when expanding the server without clicking on Refresh button.

6. If there DPM Console UI no longer crashes then create a manual recovery point for any data sources that belongs to that server or cluster.

Special thanks to my colleague Wilson Souza for creating this solution.

Chris Butcher | Senior Support Escalation Engineer | Microsoft GBS Management and Security Division

Get the latest System Center news on Facebook and Twitter:

System Center All Up: http://blogs.technet.com/b/systemcenter/

Configuration Manager Support Team blog: http://blogs.technet.com/configurationmgr/ 
Data Protection Manager Team blog: http://blogs.technet.com/dpm/ 
Orchestrator Support Team blog: http://blogs.technet.com/b/orchestrator/ 
Operations Manager Team blog: http://blogs.technet.com/momteam/ 
Service Manager Team blog: http://blogs.technet.com/b/servicemanager 
Virtual Machine Manager Team blog: http://blogs.technet.com/scvmm

Microsoft Intune: http://blogs.technet.com/b/microsoftintune/
WSUS Support Team blog: http://blogs.technet.com/sus/
The RMS blog: http://blogs.technet.com/b/rms/
App-V Team blog: http://blogs.technet.com/appv/
MED-V Team blog: http://blogs.technet.com/medv/
Server App-V Team blog: http://blogs.technet.com/b/serverappv
The Surface Team blog: http://blogs.technet.com/b/surface/
The Application Proxy blog: http://blogs.technet.com/b/applicationproxyblog/

The Forefront Endpoint Protection blog : http://blogs.technet.com/b/clientsecurity/
The Forefront Identity Manager blog : http://blogs.msdn.com/b/ms-identity-support/
The Forefront TMG blog: http://blogs.technet.com/b/isablog/
The Forefront UAG blog: http://blogs.technet.com/b/edgeaccessblog/

DPM 2012 R2

Update Rollup 8 for System Center 2012 R2 Data Protection Manager has been released and is now available to download. The KB article below describes the issues that are fixed as well as installation instructions for Update Rollup 8 for Microsoft System Center 2012 R2 Data Protection Manager.

For complete details as well as a download link, please see the following:

KB3096378 – Description of Update Rollup 8 for System Center 2012 R2 (https://support.microsoft.com/en-us/kb/3096378)

J.C. Hornbeck | Solution Asset PM | Microsoft GBS Management and Security Division

Get the latest System Center news on Facebook and Twitter:

Main System Center blog: http://blogs.technet.com/b/systemcenter/

Configuration Manager Support Team blog: http://blogs.technet.com/configurationmgr/
Data Protection Manager Team blog: http://blogs.technet.com/dpm/
Orchestrator Team blog: http://blogs.technet.com/b/orchestrator/
Operations Manager Team blog: http://blogs.technet.com/momteam/
Service Manager Team blog: http://blogs.technet.com/b/servicemanager
Virtual Machine Manager Team blog: http://blogs.technet.com/scvmm

Microsoft Intune: http://blogs.technet.com/b/microsoftintune/
WSUS Support Team blog: http://blogs.technet.com/sus/
RMS blog: http://blogs.technet.com/b/rms/
App-V Team blog: http://blogs.technet.com/appv/
MED-V Team blog: http://blogs.technet.com/medv/
Server App-V Team blog: http://blogs.technet.com/b/serverappv

Forefront Endpoint Protection blog: http://blogs.technet.com/b/clientsecurity/
Forefront Identity Manager blog: http://blogs.msdn.com/b/ms-identity-support/
Forefront TMG blog: http://blogs.technet.com/b/isablog/
Forefront UAG blog: http://blogs.technet.com/b/edgeaccessblog/
Application Proxy blog: http://blogs.technet.com/b/applicationproxyblog/
The Surface Team blog: http://blogs.technet.com/b/surface/

DPM 2012 R2 UR8

Just a quick FYI on a new KB article that was published. When you try to use the Microsoft Azure Backup (MAB) offline seeding feature, the import job may fail to continue after it sends the drive to Azure for importing. Additionally, the MAB interface displays the following message:

Waiting for Azure Import Job to complete. Please check on Azure management portal for more information on job status.

Additionally, you may see entries that resemble the following in C:\Program Files\Microsoft Azure Recovery Services Agent\Temp\CBEngineCurr.errlog:

… 44B4 3968 10/21 21:02:21.611 69 AzureServiceManagementHelper.cs(320) 0517B3DB-347D-45A8-9DAB-FD7D1EA7D134 FATAL GetImportJobStatus:: Import job with name ‘ImportJobName’ is not found 44B4 3968 10/21 21:02:21.611 71 backupasync.cpp(1589) [000000001B73B830] 0517B3DB-347D-45A8-9DAB-FD7D1EA7D134 NORMAL PollAzureImportJob :: Import Job: ‘ImportJobName’ is in pending state: ‘1’ 44B4 3968 10/21 21:02:21.611 71 backupasync.cpp(1607) [000000001B73B830] 0517B3DB-347D-45A8-9DAB-FD7D1EA7D134 WARNING PollAzureImportJob failed with error code: 1b7afbe0 44B4 3968 10/21 21:02:21.611 71 backupasync.cpp(1184) [000000001B73B830] 0517B3DB-347D-45A8-9DAB-FD7D1EA7D134 WARNING Failed: Hr: = [0x80780054] Offline Backup Progress: Failed” …..

For complete details regarding the cause of this error as well as a resolution, please see the following:

KB3119587 – Microsoft Azure Backup offline seeding is stuck at “Waiting for Azure import job to complete” (https://support.microsoft.com/en-us/kb/3119587)

J.C. Hornbeck | Solution Asset PM | Microsoft GBS Management and Security Division

Get the latest System Center news on Facebook and Twitter:

Main System Center blog: http://blogs.technet.com/b/systemcenter/

Configuration Manager Support Team blog: http://blogs.technet.com/configurationmgr/
Data Protection Manager Team blog: http://blogs.technet.com/dpm/
Orchestrator Team blog: http://blogs.technet.com/b/orchestrator/
Operations Manager Team blog: http://blogs.technet.com/momteam/
Service Manager Team blog: http://blogs.technet.com/b/servicemanager
Virtual Machine Manager Team blog: http://blogs.technet.com/scvmm

Microsoft Intune: http://blogs.technet.com/b/microsoftintune/
WSUS Support Team blog: http://blogs.technet.com/sus/
RMS blog: http://blogs.technet.com/b/rms/
App-V Team blog: http://blogs.technet.com/appv/
MED-V Team blog: http://blogs.technet.com/medv/
Server App-V Team blog: http://blogs.technet.com/b/serverappv

Forefront Endpoint Protection blog: http://blogs.technet.com/b/clientsecurity/
Forefront Identity Manager blog: http://blogs.msdn.com/b/ms-identity-support/
Forefront TMG blog: http://blogs.technet.com/b/isablog/
Forefront UAG blog: http://blogs.technet.com/b/edgeaccessblog/
Application Proxy blog: http://blogs.technet.com/b/applicationproxyblog/
The Surface Team blog: http://blogs.technet.com/b/surface/

DPM 2012 R2

System Center DPM 2012 R2 Update Rollup 8 has been out for a month now, we spent a lot of energy in this UR to focus on quality and are getting good feedback from thousands of customers who already installed the update. As a result, we have now made it an “Important Update” on Microsoft Update, so it will be pushed automatically to wider audience and more customers can benefit from all the reliability fixes.

We would recommend customers to upgrade to UR8, if not done already. Below is a recap of the major reliability fixes we made in DPM UR7 and UR8, for more detailed list of bug fixes and features please refer to respective DPM UR KB articles.

~ Sekar Raju

Hi everyone, Sekar Raju here from the Microsoft DPM and Azure backup team with quick support tip for you. When attempting an Azure backup, you may experience a problem where the backup job fails with the following symptoms:

• In Microsoft Azure Backup, you have a backup job that fails with the following error:

Backup has encountered an irrecoverable error. Contact Microsoft Support for further assistance. (0x086C8)

The Error tab on the Job Details dialog will also contain the following:

Job failed with error (Operation failed.(0x086C8)

• The CloudBackup Event Log contains an Event ID 11 similar to the one below:

Log Name:      CloudBackup
Source:           CloudBackup
Date:              <Date/Time>
Event ID:         11
Task Category: None
Level:              Error
Keywords:     
User:              SYSTEM
Computer:      <ServerName>
Description:
The description for Event ID 11 from source CloudBackup cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
If the event originated on another computer, the display information had to be saved with the event.
The following information was included with the event:
<?xml version=”1.0″?>
<CBJob><JobId>84d3f434-df64-4595-af6e-xxxxxxxxxxxx</JobId><JobType>Backup</JobType><JobStatus><JobState>Aborted</JobState><StartFileTime>

1308740310939xxxxx</StartFileTime><EndFileTime>1308740393522xxxxx</EndFileTime><FailedFileLog>
</FailedFileLog><ErrorInfo><ErrorCode>34504</ErrorCode><DetailedErrorCode>-2146233088(or)2137452629</DetailedErrorCode><ErrorParamList><CBErrorParam><Name>DLS_ERROR_CODE_NAME</Name>
<Value>34504</Value></CBErrorParam><CBErrorParam><Name>__ErrorSource__</Name><Value>
Service/None/Client</Value></CBErrorParam></ErrorParamList></ErrorInfo><DatasourceStatus>
<CBDatasourceStatus><JobState>Aborted</JobState><LastCompletedJobState>PreparingMedia
</LastCompletedJobState>…

• The following exception appears in CBEngine.log:

12E4        1488        <Date/Time>        71        prepunmanagedutils.h(120)                84D3F434-DF64-4595-AF6E-F7A271EC0581        WARNING        Error occurred, DlsErrorCode – 34504, Exception – FMException: [ErrorCode:SalMetadataVhdCorrupt, DetailedCode:0, Source:Service/None/Client, Message:Corruption is detected. FMException: [ErrorCode:SalMetadataVhdCorrupt, DetailedCode:0, Source:None, Message:Corruption is detected.]

To fix this problem, install the latest version (2.0.9022.0 or later) of the Microsoft Azure Recovery Services Agent. Here are the steps:

1. Close the Microsoft Azure Backup snap-in if it is still running.
2. Download and install latest Microsoft Azure Recovery Services Agent from here.
3. Launch the Microsoft Azure Backup snap-in.
4. Manually start the backup job by clicking the Back up Now option, or optionally wait for the scheduled backup job to start and complete.
5. If the backup job you started on step 4 fails, manually start the backup job one more time or wait for the next scheduled backup job to start and complete. This is because sometimes the first backup with the new agent may fail with the same error, however subsequent backup jobs will successfully complete.

Hope this helps!

Sekar Raju | Senior Support Engineer | Microsoft

Our Blogs

• Configuration Manager: http://blogs.technet.com/configurationmgr/
• Data Protection Manager: http://blogs.technet.com/dpm/
• Orchestrator: http://blogs.technet.com/b/orchestrator/
• Operations Manager: http://blogs.technet.com/momteam/
• Operations Management Suite: https://blogs.technet.microsoft.com/omsblog/
• Service Manager: http://blogs.technet.com/b/servicemanager
• Virtual Machine Manager: http://blogs.technet.com/scvmm
• Microsoft Intune: https://blogs.technet.microsoft.com/intunesupport/
• WSUS: http://blogs.technet.com/sus/
• AD and Azure RMS: http://blogs.technet.com/b/rms/
• Application Virtualization: http://blogs.technet.com/appv/
• MED-V: http://blogs.technet.com/medv/
• Application Proxy: http://blogs.technet.com/b/applicationproxyblog/
• Forefront Endpoint Protection: http://blogs.technet.com/b/clientsecurity/
• Forefront Identity Manager: http://blogs.msdn.com/b/ms-identity-support/
• Forefront TMG: http://blogs.technet.com/b/isablog/
• Forefront UAG: http://blogs.technet.com/b/edgeaccessblog/

DPM 2012 R2

~ Andy Nadarewistsch | Senior Support Escalation Engineer

Hi everyone, Andy Nadarewistsch here from the Microsoft DPM and Azure backup team with quick support tip for you. When attempting an Azure backup, you may experience a problem where the backup job fails immediately with the following symptoms:

1. In Microsoft Azure Backup, you have a backup job that fails immediately with the following error:

Backup cannot be completed. Error: Operation failed.

The Error tab on the Job Details dialog will also contain the following:

Job failed with error (Operation failed. (0x1D4C2))

2. The CloudBackup Event Log contains an Event ID 11 similar to the one below:

Log Name:      CloudBackup
Source:           CloudBackup
Date:              <Date/Time>
Event ID:         11
Task Category: None
Level:              Error
Keywords:     
User:              SYSTEM
Computer:      <ServerName>
Description:

The backup operation has completed with errors.

Looking at details tab shows something similar to the following:

<?xml version=”1.0″?> <CBJob><JobId>601c22e6-2283-487c-9d2f-7721ec21e1bf</JobId><JobType>Backup</JobType><JobStatus><JobState>Aborted</JobState><StartFileTime>130966313434530377</StartFileTime><EndFileTime>130966313434530377</EndFileTime><FailedFileLog></FailedFileLog><ErrorInfo><ErrorCode>120002</ErrorCode><DetailedErrorCode>-2147024773</DetailedErrorCode><ErrorParamList/></ErrorInfo><DatasourceStatus><CBDatasourceStatus><JobState>Aborted</JobState><LastCompletedJobState>Initializing</LastCompletedJobState><ErrorInfo><ErrorCode>120002</ErrorCode><DetailedErrorCode>-2147024773</DetailedErrorCode><ErrorParamList/></ErrorInfo><Datasource><DataSourceId>1377471703</DataSourceId><DataSourceName>D:\</DataSourceName></Datasource><ByteProgress><Total>0</Total><Changed>0</Changed><Progress>0</Progress><Failed>0</Failed></ByteProgress><FileProgress><CurrentFile></CurrentFile><Total>0</Total><Changed>0</Changed><Progress>0</Progress><Failed>0</Failed></FileProgress></CBDatasourceStatus></DatasourceStatus></JobStatus></CBJob>

3. The following exception appears in CBEngine.log:

7F28 11C0 01/08 19:30:13.086 18 dsmfsenumerator.cpp(150) [000000001A86EA60] 8A0B2420-2B0F-4AAF-AE82-2B0A04A0773B WARNING Failed: Hr: = [0x8007007b] : FindFirstFile failed For Dir:\\?\D:\Scratch\\Scratch\*

7F28 11C0 01/08 19:30:13.086 18 fsutils.cpp(2354) 8A0B2420-2B0F-4AAF-AE82-2B0A04A0773B WARNING Failed: Hr: = [0x8007007b] : FindFirstFile failed for Path [\\?\D:\Scratch\\Scratch\], FileSpec [*]

The Cause

This issue typically occurs due to a double backslash (“\\”) in the scratch location path in the registry.

The Fix

To fix this problem, modify the following registry keys to reflect the correct path of the scratch location:

HLKM\Software\Microsoft \Windows Azure Backup\Config\ScratchLocation

HLKM\Software\Microsoft \Windows Azure Backup\Config\CloudBackupProvider\ScratchLocation

Here are the steps:

1. Run Regedit.

2. Navigate to the following Registry keys:

HLKM\Software\Microsoft \Windows Azure Backup\Config\

HLKM\Software\Microsoft \Windows Azure Backup\Config\CloudBackupProvider\

3. In each registry key above, double-click the ScratchLocation value and remove the extra “\” in the path, or modify the path to reflect the correct location. Here’s what it would look like when fixing the paths shown in our screen shots above.

4. Once both registry keys have been edited, click OK and then retest the backup. At this point the backup job should complete successfully.

Hope this helps!

Andy Nadarewistsch | Senior Support Escalation Engineer | Microsoft

Our Blogs

• Configuration Manager: http://blogs.technet.com/configurationmgr/
• Data Protection Manager: http://blogs.technet.com/dpm/
• Orchestrator: http://blogs.technet.com/b/orchestrator/
• Operations Manager: http://blogs.technet.com/momteam/
• Operations Management Suite: https://blogs.technet.microsoft.com/omsblog/
• Service Manager: http://blogs.technet.com/b/servicemanager
• Virtual Machine Manager: http://blogs.technet.com/scvmm
• Microsoft Intune: https://blogs.technet.microsoft.com/intunesupport/
• WSUS: http://blogs.technet.com/sus/
• AD and Azure RMS: http://blogs.technet.com/b/rms/
• Application Virtualization: http://blogs.technet.com/appv/
• MED-V: http://blogs.technet.com/medv/
• Application Proxy: http://blogs.technet.com/b/applicationproxyblog/
• Forefront Endpoint Protection: http://blogs.technet.com/b/clientsecurity/
• Forefront Identity Manager: http://blogs.msdn.com/b/ms-identity-support/
• Forefront TMG: http://blogs.technet.com/b/isablog/
• Forefront UAG: http://blogs.technet.com/b/edgeaccessblog/

DPM 2012 R2

Update Rollup 9 for System Center 2012 R2 Data Protection Manager (DPM 2012 R2 UR9) is now available to download. The KB article below describes the issues that are fixed and also contains the installation instructions for this update.

Please note that this update does not require a restart of the production server if you upgrade from Update Rollup 5 for System Center 2012 R2 Data Protection Manager or later.

Existing Data Protection Manager to Windows Azure customers should upgrade to the latest agent (version 2.0.8719.0 or greater). In case this is not installed, online backups will fail, and no Data Protection Manager to Windows Azure operation will work.

For complete details including issues fixed, installation instructions and a download link, please see the following:

3112306 – Update Rollup 9 for System Center 2012 R2 Data Protection Manager (https://support.microsoft.com/en-us/kb/3112306)

J.C. Hornbeck | Solution Asset PM | Microsoft

Our Blogs

• Configuration Manager: http://blogs.technet.com/configurationmgr/
• Data Protection Manager: http://blogs.technet.com/dpm/
• Orchestrator: http://blogs.technet.com/b/orchestrator/
• Operations Manager: http://blogs.technet.com/momteam/
• Operations Management Suite: https://blogs.technet.microsoft.com/omsblog/
• Service Manager: http://blogs.technet.com/b/servicemanager
• Virtual Machine Manager: http://blogs.technet.com/scvmm
• Microsoft Intune: https://blogs.technet.microsoft.com/intunesupport/
• WSUS: http://blogs.technet.com/sus/
• AD and Azure RMS: http://blogs.technet.com/b/rms/
• Application Virtualization: http://blogs.technet.com/appv/
• MED-V: http://blogs.technet.com/medv/
• Application Proxy: http://blogs.technet.com/b/applicationproxyblog/
• Forefront Endpoint Protection: http://blogs.technet.com/b/clientsecurity/
• Forefront Identity Manager: http://blogs.msdn.com/b/ms-identity-support/
• Forefront TMG: http://blogs.technet.com/b/isablog/
• Forefront UAG: http://blogs.technet.com/b/edgeaccessblog/

~ Rupanter Chhabra | Support Engineer | Microsoft

This article discusses the interface for a Recovery Services Backup Vault in the Microsoft Azure Backup management portal. Each section of the interface is examined, including the various options, settings and information available as well as explanations for each. Note that the creation of the Backup Vault itself is not covered as this example assumes that the Backup Vault already exists. The article uses an example Backup Vault named Backuptest that has already been created and focuses purely on the different options available in the various areas of the Backup Vault interface.

If you’d like some additional background regarding Microsoft Azure Backup, here are a few references that will help get you started

• Azure Virtual Machine Backup: https://azure.microsoft.com/en-us/documentation/articles/backup-azure-vms/
• Microsoft Azure Backup: https://azure.microsoft.com/en-us/documentation/articles/backup-azure-backup-windows-server/
• Microsoft Azure Backup Server: https://azure.microsoft.com/en-us/documentation/articles/backup-azure-dpm-introduction/

Quick Start

Many people tend to miss the Quick Start section (in red below) but it can help us in a lot of different ways.

The Quick Start guide has two sections:

Protect On-premises workloads

This is the section that pertains to Microsoft Azure Backup (MAB) and Microsoft Azure Backup Server.

• The first option here is to download the vault credentials. These are the credentials for the vault and are required during registration. Vault credentials expire after two days, so if you are registering or re-registering a server more than two days after downloading the credentials, you will need to download the vault credentials again.

• The second option is to download the various agents:

• MAB Server (Disk to Disk to Cloud)
• MAB for Windows Server, System Center Data Protection Manager and Windows Client
• Agent for Windows Essentials

The agent is required for Microsoft Azure Backup.

Protect Azure Virtual Machines

This section pertains to virtual machine backup. This backup option is only available for virtual machines that are on Microsoft Azure.

• Discover Azure Virtual Machines: If you have the Windows guest agent installed on the virtual machine that you are trying to backup, you can discover it using the Discover button prior to registering it.
• Register Azure Virtual Machines: You need to register the virtual machines that you want to backup using Azure virtual machine backup, and you can register them via the Azure Portal under the Registered Items tab.
• Protect Registered Azure Virtual Machines: You need to initialize protection for the registered virtual machine, then you can back up the virtual machine by scheduling the backup or by clicking on Backup Now.

Dashboard

Now let’s take a look at how our Dashboard looks and what options are available here.

The Dashboard contains information related to your usage, how much storage has been used, the jobs that are running, the machines that are protected, links to various downloadable options and Information regarding you vault.

Usage Overview:

Once protected, the virtual machine count also increases in the Dashboard page summary. This only represents virtual machines backed up in Azure, not the computers that have downloaded an agent and are backing up through MAB server, the agent or via Data Protection Manager (DPM). The Dashboard also shows the number of jobs from the last 24 hours that were successful, have failed, or are still in progress. By clicking on any of these categories, you can drill down into that category in the Jobs page for more details. Values in the dashboard are refreshed once every 24 hours.

Quick Glance:

Here you have links to the following:

1. Microsoft Azure Backup Agent for Windows Server, Data Protection Manager, Windows Client
2. Microsoft Azure Backup Agent for Windows Server Essentials
3. Microsoft Azure Backup Server (Disk to Disk to Cloud)
4. Vault Credentials – Necessary for registration and re-registration
5. Replication Settings – What kind of replication do we want for our Backup Vault
6. Billing model details

Other information:

As you can see above, this section contains additional information regarding your Backup Vault, such as the current status, the location where the backup vault has been created, the vault storage replication configuration, as well as the subscription ID and name. This is just a short overview of what is associated to the Backup Vault.

Registered Items

This section deals with all the items that have been registered with a particular Backup Vault. It might be an Azure virtual machine, or it could be Windows client, a Windows Essential server, etc. Everything registered can be found in this section.

To see the various kinds of registered Items, you first need to change the type of item that you want to view:

• Azure Virtual Machine: A VM that is hosted on Microsoft Azure
• Windows server: Your on-premises computers (servers, clients, etc.)

After selecting the type, you need to click on the Checkmark button that you see on the right-hand side:

After doing that you get the name of the computer, the type and the status (e.g. if it’s registered or in an error state, or if it’s getting registered). You can also select the status from the drop-down list box.

Protected Items

This section deals with all the protected items that are being backed up and protected in a particular Backup Vault. You can also select the type of machine that you want to check the status for, similar to how we did in the Registered Items section. The only difference is that instead of Windows Server, you get an option to view Files and Folders:

After selecting the type, you need to click on the Checkmark button to confirm the selection.

Azure Virtual Machine

Here you can see more details like the name, the type of the machine, the status of the machine (if its protected, or is there an error or warning), details about how many recovery points you have, what policy the Azure machines fall under, and when the newest recovery point was taken.

Files and Folders

As you can see above, here you can view a few more details such as which drive/folder you’re backing up and from which server, as it could be an on-premises server as well. Also included is the type of backup you are performing, the status, the number of recovery points created, as well as the date and time of the oldest and the newest recovery points.

Configure

In the Configure section you can see what kind of storage replication you are using:

Locally Redundant: Locally redundant storage (LRS) replicates your data within the region in which you created your storage account.

Geo Redundant: Geo-redundant storage (GRS) replicates your data to a secondary region that is hundreds of miles away from the primary region.

For more information on storage replication and redundancy types, see the following:

https://azure.microsoft.com/en-in/documentation/articles/storage-redundancy/

Policies

In this section you can see which policies are being used to back up the Azure virtual machines. When you select the policy that you want to see the details for, and there are two tabs: Details and Items.

Details

The Details page contains the name of the policy and what kind of virtual machines the policy is applied to:

You also have the schedule which shows you how often your backup is occurring (daily or weekly), the scheduled time to run the backup, and the time zone for it:

The retention policy specifies the length of time for storing a backup, and you can specify different retention policies based on when the backup is taken. For example, a backup point taken at the end of each quarter may need to be preserved for a longer period for audit purposes, whereas a backup point taken daily, which serves as an operational recovery point, may only need to be preserved for 90 days.

The example above represents the following:

• Daily retention policy: Backups taken daily are stored for 30 days.
• Weekly retention policy: Backups taken every week on Sunday will be preserved for 104 weeks.
• Monthly retention policy: Backups taken on the last Sunday of each month will be preserved for 60 months.
• Yearly retention policy: Backups taken on the first Sunday of every January will be preserved for 10 years.

Items

Under Items you can see which machines are under a specific policy.

Jobs

The Jobs section deals with all of the actions that are performed on and from the Azure portal. The Jobs section gives you the details for any jobs that have been created. It could be anything from registering an Azure machine to running a backup process. For everything that is run from the Azure Portal, a job is created which can be viewed here.

Note that jobs that you run from on-premises machines (Microsoft Azure Backup or Microsoft Azure Backup Server) will not be listed here as those are already listed in the consoles on the servers. This section applies only to actions that are performed on the Microsoft Azure portal.

Here you can filter your results using the following criteria:

1. The type of machine
2. The status of the job:

a. All
b. In Progress
c. Completed
d. Failed
e. Completed with warning
f. Cancelled
g. Cancelling

3. What operation the job was created for:

a. All
b. Register
c. Configure Protection
d. Backup
e. Restore
f. Stop Protection
g. Delete Backup Data
h. Unregister

4. The time range for the job.

After selecting these filters you will see the details:

1. Workload Name: The machine name
2. Type: The type of the machine
3. Operation: Which operation the job is for
4. Status: The current status of the job
5. Date: When the job was started
6. Duration: How much time it took to complete the job

On the bottom of the page, if you don’t select any particular job then you will see two options:

Summary Report: This will generate a report of all the jobs in the time range selected.

Export Jobs: This will export the job details to a Microsoft Excel spreadsheet.

If you just want the details for a specific job, select the job, open the job details, then click EXPORT JOBS and it will generate a Microsoft Excel spreadsheet specific to that particular job.

Rupanter Chhabra | Support Engineer | Microsoft

Our Blogs

• Configuration Manager: http://blogs.technet.com/configurationmgr/
• Data Protection Manager: http://blogs.technet.com/dpm/
• Orchestrator: http://blogs.technet.com/b/orchestrator/
• Operations Manager: http://blogs.technet.com/momteam/
• Operations Management Suite: https://blogs.technet.microsoft.com/msoms/
• Service Manager: http://blogs.technet.com/b/servicemanager
• Virtual Machine Manager: http://blogs.technet.com/scvmm
• Microsoft Intune: https://blogs.technet.microsoft.com/intunesupport/
• WSUS: http://blogs.technet.com/sus/
• AD and Azure RMS: http://blogs.technet.com/b/rms/
• Application Virtualization: http://blogs.technet.com/appv/
• MED-V: http://blogs.technet.com/medv/
• Application Proxy: http://blogs.technet.com/b/applicationproxyblog/
• Forefront Endpoint Protection: http://blogs.technet.com/b/clientsecurity/
• Forefront Identity Manager: http://blogs.msdn.com/b/ms-identity-support/
• Forefront TMG: http://blogs.technet.com/b/isablog/
• Forefront UAG: http://blogs.technet.com/b/edgeaccessblog/