After Data Protection Manager (DPM) backup fails, you are unable to delete broken recovery checkpoints for a virtual machine that was created by Hyper-V. When you try to do this, you discover that there's no option listed for a virtual machine in the Hyper-V Manager Console GUI as shown below.

For complete details regarding this problem as well as a resolution, please see the following:

KB3059372 - You can't delete a recovery checkpoint for a virtual machine in Data Protection Manager (https://support.microsoft.com/en-us/kb/3059372/)

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

~ Mike Jacquet | Senior Support Escalation Engineer

Hello everyone, Mike Jacquet here from the DPM support team at Microsoft. I would like to share some registry settings that you may not be aware of that can alter the behavior of DPM, enable features, eliminate uncommon errors, and help with troubleshooting. Many of these registry settings were introduced and documented in DPM update rollups, on TechNet or the blogs, however unless you are already familiar with these settings they may be hard to discover on your own.

Please note that this is not a comprehensive list of all DPM registry settings. There are many settings that are part of a default DPM installation that are not covered here.

CAUTIONSerious problems can occur if you modify the registry incorrectly. These problems could require you to reinstall the operating system. Microsoft cannot guarantee that these problems can be solved. Modify the registry at your own risk. Always make sure that you back up the registry before you modify it, and that you know how to restore the registry if a problem occurs.

Diagnostics

Logging was introduced in DPM 2007 and enhanced in DPM 2010. The ability to adjust the verbosity of the logging is helpful when troubleshooting an issue where normal logging may not have enough empirical information leading up to the error.

You can enable verbose logging using the following entries:

NOTE Binary = MSDPM (for engine), DPMRA (for Agent), DPMLA (for Library Agent), DPMAccessManager (for Access Manager), DpmBackup (for DPM backup), DpmWriter (for DPM writer), DPMUI (For DPM console mmc), DPMCLI (for DPM power shell console).

NOTE The tracelogPath location setting is global across of all binaries.

NOTE Service restart is required before TraceLogPath and TraceLogLevel will be used. Delete or rename the TraceLogLevel to disable verbose logging.

NOTE DPM Log files are located in one of the following locations:

- DPM SERVER 2007/2010 (or if upgraded to DPM 2012) logs are in the C:\Program files\Microsoft DPM\DPM\temp folder.
- DPM SERVER 2012 and SP1 logs are in the C:\Program Files\System Center 2012\DPM\DPM\temp folder.
- DPM SERVER 2012 R2 logs are in the C:\Program Files\System Center 2012 R2\DPM\DPM\temp folder.
- PROTECTED SERVER logs are always in C:\Program files\Microsoft Data Protection Manager\DPM\temp

The DPMUI and DPMCLI error logs will be located in the users profile under one the following locations depending on DPM version:

C:\Users\<USERNAME>\AppData\Roaming\Microsoft\<DPM PRODUCT VERSION DIRECTORY> 

- Microsoft System Center 2012 Data Protection Manager
- Microsoft System Center 2012 R2 Data Protection Manager
- Microsoft System Center 2012 Service Pack 1 Data Protection Manager
- Microsoft System Center Data Protection Manager
- Microsoft System Center Data Protection Manager 2010

NOTE DPM will create log files with an extension of <binary>*.errlog.crash should the <binary> service crash.  These .crash files are not limited by the <binary>TraceLogMaxNum setting so it is advisable to monitor the log location and manually delete the .crash files manually.

More information can be found in this TechNet article.

DPM 2012 Service Pack 1 introduced online Azure backup capability that uses a different agent. You can also enable verbose logging for online backups:

NOTE Obengine service restart is required before TraceLogLevel will be used:

C:>Net stop obengine
C:\Net start obengine

Logs are located under C:\Program Files\Microsoft Azure Recovery Services Agent\Temp

Agent Communications

These were introduced in DPM 2010 to support client protection in mixed TPC IP4 and IP6 environment. DPM will work in a pure IPv6 environment, however if DPM has both IPv4 and IPv6 addresses, we expect the Protected Server (PS) to have IPv4 enabled as our preferred channel is IPv4. If some of the agents have only IPv6 enabled then we must have only IPv6 on DPM and on all PS's.

With that said, there is a workaround to this but it was not thoroughly tested therefore not supported by Microsoft. If you set the registry key below, DPM should work properly in a mixed environment.

Please note that this is not formally supported, but good for testing to see if it helps.

On BOTH the DPM Server and the Protected Server, set the following registry key:

Agent communication timeouts

Description: The DPM service was unable to communicate with the protection agent on PS_Server.domain.com. (ID 2019 Details: An existing connection was forcibly closed by the remote host (0x80072746))

NOTE ID Numbers may vary but the error code 0x80072746 is consistent.

This can be caused by very slow network connectivity which causes the backup sender (DPMRA on the Protected Server) to timeout. To address this, add the following on both the DPM Server and the Protected Server(s), then restart the DPMRA service for the change to take effect. Be sure there are no active jobs before restarting the DPMRA services.

Description: The DPM service was unable to communicate with the protection agent on Clust-01.Domain.com. (ID 52 Details: The semaphore timeout period has expired (0x80070079))

170359 - How to modify the TCP/IP maximum retransmission time-out (http://support.microsoft.com/kb/170359/EN-US)

Apply on both DPM and Protected servers:

Application (SQL/ Exchange) Protection

Introduced in DPM 2007 hotfix KB 970867.

DPM performs a Volume Shadow Copy Service (VSS) full backup. Because the application transaction logs are deleted when the DPM backup job is completed, the DPM backup may interfere with other backup methods that are backing up transactional applications such as Microsoft SQL Server or Microsoft Exchange. By adding the below value on the protected server, DPM will perform copy only backups which will not truncate log files.

Add the following value on the protected server:

NOTE The same can be accomplished for SQL Server by configuring DPM to synchronize right before recovery point as seen in the figure below.

If the selection ‘Just before a recovery point’ is used then incremental backups won’t get scheduled. This option is a way of telling DPM that the user is interested only in express full backups and not incremental backups which truncate the logs.

Introduced in DPM 2010 to support a copy only backup for SharePoint farms that are using log shipping. 

As an example - On a SharePoint farm, you configure SQL to ship its logs to an alternate SQL server and replicate the farm for disaster recovery.  This process truncates the SQL log files and therefore DPM will not need to.

On the DPM server, create the following key:

As an example, if your SharePoint farm is using a SQL server named SPSql_01 and the instance is named SP2010, then you would just look for the config database and the REG_DWORD would be similar to:

SPSql_01\SP2010\SharePoint_Config_907565b-d867-43b9-9371-2d9d69c0ecf1

SQL 4200 Express Full Limit Alert

When trying to perform more than 4200 SQL Server Express full backups, DPM may generate the following Alert:

A DPM server can have a maximum of 4200 Express Full backups of SQL Server per week. If you exceed this limit, the DPM server may miss the backup SLA and eventually it may become unresponsive. You currently have #### Express Full backups of SQL Server on Server1.contoso.com (ID: 32630)"

This is a proactive Warning Alert raised by DPM to let the user know that they have either 1) protected too many SQL data sources belonging to the same Protected Server, or 2) has set the Express Full frequency too high, or 3) a combination of both. If the user ignores this alert DPM should just continue to work, however there can be two possible outcomes. First, if the individual databases are very small and have little churn, the backups will work just fine. If the databases are larger and have a lot of churn, some Express Full backups will fail with errors such as “another backup is going on at the same time”. This will result in missed SLA for effected databases.

To eliminate the alert at the expense of possible missed backups, add the following on the DPM server, then run through the modify protection group wizard for the protection group containing the SQL Server protection without making changes.

SQLExpressFullPerPSLimit defines how many Express Full backups you can create per protected server.

SQLExpressFullLimit defines how many you can create in total from that DPM server.

Make each of them larger than the default of 0x1068 (4200 decimal).

Client Protection

DPM 2010 introduced Windows Client protection. The settings below were introduced to help with overall performance as per the TechNet articles.

Optimizing Client Computer Performance

NOTE The default value for WaitInMSPerRequestForClientRead DWORD is 50 (32H). This means the DPM agent will wait 50ms per read cycle to locate changed data. You can increase the value to 75 or 100 decimal to reduce IO on the disk to improve machine responsiveness at the cost of longer backup times. If you want to increase backup speed at the expense of responsiveness, reduce the value to 40 or 30 decimal.

Scaling up Client Protection

For Task Throttling:

The GUIDs control certain types of DPM tasks and you may need to tweak only certain ones to fit your needs. Below are the meanings and why you might want to reduce them.

9037ebb9-5c1b-4ab8-a446-052b13485f57 = Initial Replication - Reduce this if you plan on adding lots of new clients to protection at one time - this will limit the simultaneous transfer of data from X number of clients.

3d859d8c-d0bb-4142-8696-c0d215203e0d = Delta Replication (synchronizations) - reduce this to help with all clients trying to synchronize at the same time after an extended outage.

c4cae2f7-f068-4a37-914e-9f02991868da = Validate and Fix up (consistency check) - reduce this to throttle repairing replica volumes that need consistency checks.

To adjust the collocation factor: The default was 10 in DPM 2010 and was increased to 30 in DPM 2012.

Restoring Client backup data

This is new inKB 2465832.

The administrator of a client computer must set the name of non-admin users who have to have permissions to perform end-user recovery of protected data of a client computer. To do this, the administrator must add the following registry key and value for each of these non-admin users. This is single key that contains a comma-separated list of client users without any leading or trailing spaces. You do not have to add this key separately for each non-admin user.

MORE INFORMATION: This is a hands off solution to allow all users that use a machine to be able to restore their own files.

1) Using Notepad, create these two .cmd files and save them in c:\temp (be sure the .txt extension is removed).

<addperms.cmd>

2) Using Windows Scheduler, schedule addperms.cmd to run daily. Any new users that log onto the machine will automatically be added to the registry and have the ability to restore their own files.

Library / Tape Management

Introduced in DPM 2007 feature pack KB 949779

Added feature to better use tape capacity by co-locating data from multiple protection groups that have a similar retention range.

For DPM 2007 / DPM 2010 - see the following information: Things you can do to help Data Protection Manager utilize your tapes full capacity

IMPORTANT NOTE The TapeExpiryTolerance value is depreciated in DPM 2012 and later. You can now create protection group co-location sets (Pgset) to have better control over tape co-location.

For DPM 2012 and later see the following information: Colocate data from different protection groups on tape

First introduced in DPM 2007 KB 970868

Detailed inventories can raise alerts for failure on each slot. If you have set many slots, too many alerts may be raised. Additionally, alerts are raised for each slot when you cancel the library detailed inventories. To prevent the alerts from being raised add the following value on the DPM Server.

NOTE After you apply the update and the registry setting, you can still determine whether the DI jobs failed or succeeded in the jobs view.

Support for IBM System Storage TS2900 Tape Autoloader KB 2465832

NOTE The RSMCompatMode registry value is used to specify multiple flags for DPM. The following are the flags that are set by this registry value:

• 1 = RSM_COMPAT_INIT_ELEMENT_STATUS
• 4 = RSM_COMPAT_IGNORE_TAPE_INVENTORY_RESULT
• 8 = RSM_COMPAT_CLEANER_EXCEPTION
•16 = TS2900 compatibility

Dell TL2000 / TL4000 and IBM 35XX libraries require the RSMCompatMode registry value to be 0xD or 13 Decimal, however 0x1D will also work fine with those libraries.

Short Erase

When a user erases a tape, by default DPM will do a long erase on that tape which takes longer. DPM 2010 introduced the ability to do a short erase by adding the following value.

NOTE Setting to 0 (zero) will cause DPM to use a short erase. In order to set it back to using the long erase, simply delete the UseShortErase value.

Media Usage

The following two settings were introduced in the below updates:

DPM 2010 Update Rollup 6 KB 2718797
DPM 2012 Update Rollup 2 KB 2706783

Expiry dates for valid datasets that are already written to tape are changed when the retention range is changed during a protection group modification.

A protection group is configured for long-term tape recovery points together with custom long-term recovery goals. Recovery Goal 1 has a smaller retention range than the other recovery goals. In this configuration, if the protection group is changed to remove Recovery Goal 1 and to keep other recovery goals, datasets that were created by Recovery Goal 1 have their retention range changed to the retention range of the other recovery goals.

Tapes are not reusable until the day after the day of expiry. This is true because DPM waits until midnight to run the reclamation job that marks tapes as reusable.

MMC crash when opening library tab

When running DPM 2010 or DPM 20102 and using a tape library with many slots, the DPM MMC will crash on opening. Often after several attempts, the console will finally open. This is usually seen when more than 1500 slots are presented to DPM for use.

Tape I/O errors 0x8007045D

Some tape drives do not handle multi-buffer IO very well and can lead to tape drive IO device errors. This IO error may result in DPM tape backup jobs failing or the tape being closed out and marked offsite ready before it is full. If you look in the DPMRACURR.ERRLOG after such a failure, you will find error code 0x8007045D that means "The request could not be performed because of an I/O device error". Reducing the buffer size helps in most cases.

NOTE If you set the value to 0x1 it may help with backup, however restores require a minimum of 2 buffers so it is advised to set it for 0x2 or more.

Prior to the BufferQueueSize setting, you could use a value called TapeSize. If the tape driver returns an IO_DEVICE_ERROR and the amount of data written by DPM is more than TapeSize value (in MBs), DPM will auto convert IO_DEVICE_ERROR to END_OF_TAPE_REACHED and span to next media without any issues.

Default behavior is for DPM to treat any I/O error after more than 30GB is written to tape as an “end of media” command. The TapeSize is now depreciated so please use the BuferQueueSize to fix I/O errors.

Another solution that also seems to help resolve the above IO error 0x8007045D is to add the following Storport key and BusyRetryCount value to each of the tape devices.

To get a list of all the tape devices in your DPM Server that need the registry key added, run the following command from an administrative command prompt. That will return a list of tape drive Scsi\DeviceID\Instance that you can use to make the above change.

C:\Windows\system32>wmic tapedrive list brief

Below would be the registry keys to add to the DPM server based on the above output from the WMIC command.

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\SCSI\Sequential&Ven_IBM&Prod_ULTRIUM-TD3\5&31cf2afa&0&000001\Device Parameters\StorPort]
"BusyRetryCount"=dword:000000fa

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\SCSI\Sequential&Ven_IBM&Prod_ULTRIUM-TD3\5&31cf2afa&0&000002\Device Parameters\StorPort]
"BusyRetryCount"=dword:000000fa

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\SCSI\Sequential&Ven_IBM&Prod_ULTRIUM-TD3\5&31cf2afa&0&000003\Device Parameters\StorPort]
"BusyRetryCount"=dword:000000fa

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\SCSI\Sequential&Ven_IBM&Prod_ULTRIUM-TD3\5&31cf2afa&0&000004\Device Parameters\StorPort]
"BusyRetryCount"=dword:000000fa

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\SCSI\Sequential&Ven_IBM&Prod_ULTRIUM-TD3\5&31cf2afa&0&000005\Device Parameters\StorPort]
"BusyRetryCount"=dword:000000fa

Prompting Timeout

During a tape backup, if a tape becomes full and there are no other tapes marked Free, Free (contains data) or Expired in the library, or if you are using a standalone tape drive that needs you to manually change the tape, DPM will raise an alert to prompt for another free tape to continue backup. The same is true during a restore. If a needed tape is not in the library an alert will be raised. By Default, DPM It will wait for 1 hour before failing the job.

This prompting timeout can be configured by adding this registry entry on the DPM Server. Restart the DPMRA service for it to take effect.

DPM Update Rollup

DPM Update Rollup setup will make a backup of the DPMDB prior to applying the update. You can alter the location of where that backup is stored using the following registry values. The backup file will be called QFEDPMDB.bak.

DPM Update Rollups may fail when DPM services do not stop or start in an allotted time. If you look in the update log, you will find entries with the error 8007041d which means "The service did not respond to the start or control request in a timely fashion". Below is a sample of a timeout trying to start the DPMWriter service, but the same can be logged for other DPM Services.

1: PatchCA: 2: start dpmwriter returned hr=8007041d
1: PatchCA: 2: Error in EnableAndStartService. hr=8007041d
1: PatchCA: 2: EnableDpmServices returned hr 0x8007041d

When a service starts, the service communicates to the Service Control Manager how long the service must have to start (the time-out period for the service). If the Service Control Manager does not receive a "service started" notice from the service within this time-out period, the Service Control Manager terminates the process that hosts the service. This time-out period is typically less than 30 seconds. If you do not adjust this time-out period, the Service Control Manager ends the process.

To eliminate that timeout error add the following value and restart the DPM server. Note that 30000 is in milliseconds, which is 5 minutes.

IMPORTANT The above issue was fixed in DPM 2012 R2 UR6.

Bypass DPM filter block level tracking

There may be times when normal backups may not occur due to errors in the DPM Filter bitmap, a possible resource issue on the machine, or some other unforeseen problem. Under such conditions, you may want DPM to make the backup using consistency check workflow until a permanent solution can be found. To Bypass the DPM filter block level tracking mechanism, you can add this registry value on the protected server, then restart the DPMRA service.

NOTE This will have the same performance impact as a consistency check for every recovery point taken while the ForceFixup is in use.

Please be aware of the following KB Article:

2848751 VM backups in Data Protection Manager fail with "change tracking information is corrupt" error (https://support.microsoft.com/en-us/kb/2848751/en-us)

Auto Heal features

DPM 2010 introduced some Auto Heal features like Auto-grow, Auto-rerun, Auto-CC and Continue on Failure to help resolve backup failures. These features are carried forward and are present in all newer versions of DPM. The below values can be adjusted to better meet your needs to control if and when the Auto Heal feature is utilized.

I don't want to re-invent the wheel here since many of these are already documented in our DPM 2010 blogs, but for completeness of this article I think it's necessary to include them here as well.

More information about some of the above values can be found in the following blog posts:

DPM 2010: Helping you meet SLAs with less effort
How to use and troubleshoot the Auto-heal features in DPM 2010

Co-locating Client, SQL and Hyper-V data sources

Disk co-location was introduced in DPM 2010 to allow a single DPM server to protect more than 300 data sources. The 300 data source limit is due to Windows Logical Disk Manager (LDM) database design that maintains the dynamic volumes created by DPM. Protecting 300 unique data sources requires DPM to create 600 volumes, a replica volume and a recovery point volume. The LDM database has a limit of 2960 records, and a minimum of three records is required per dynamic volume created. Since disk migration may need to occur at a later time, DPM leaves unused LDM records by still staying in the 600 volume limit range. By enabling disk co-location for some data sources, DPM does not need to create as many volumes to protect more data sources.

Below are the default co-location entries:

CLIENT PROTECTION

DSCollocationFactor is the number of data sources that can be collocated on a single replica.

NOTE The default DSCollocationFactor of 30 = 3000 clients per DPM 2012 server and later. This means 30 client machines will use the same DPM Replica volume and recovery point volume. The replica volume size will be a factor of DSCollocationFactor setting times the GB/per client specified when adding the clients to protection group.

To see which client machines are co-located on the same replica volume in a protection group, you can run the below DPM PowerShell commands. Look for co-located client machines that are on the same replicapath (Volume GUID).

Be sure to replace the 'Protectiongroup_Friendly_Name' before running.

$pg = get-protectiongroup (&hostname) | ? { $_.friendlyname -eq 'Protectiongroup_Friendly_Name'}
Get-datasource $pg | sort-object -property replicapath | ft replicapath, ProductionServerName, diskallocation -AutoSize

SQL PROTECTION

DSCollocationFactor: This is the number of SQL data sources that can be collocated on a single replica. DPM will fit as many SQL data Sources as possible up to the specified limit based on the data sources sizes at the time of enumeration and the replica size.

CollocatedReplicaSize: The default value of replica volume created for collocated SQL data sources is 10GB. This can be overridden in the GUI at time of protection. If making changes to the registry, make sure the value entered is a multiple of 1GB (1073741824). The recovery point volume size depends on this value in addition to the retention range specified in the Protection Group. The exact formula is recovery point volume size = (replica volume size * 1.5) * retention days * 0.1 + 1.6GB.

To see which SQL databases are co-located on the same replica volume in a protection group, you can run the below DPM Powershell commands. Look for co-located SQL Databases that are on the same replicapath (Volume GUID).

Be sure to replace the 'Protectiongroup_Friendly_Name' before running.

$pg = get-protectiongroup (&hostname) | ? { $_.friendlyname -eq 'Protectiongroup_Friendly_Name'}
Get-datasource $pg | sort-object -property replicapath | ft replicapath, name, diskallocation -AutoSize

HYPER-V PROTECTION

DSCollocationFactor: This is the number of Hyper-V Guest data sources that can be collocated on a single replica. DPM will fit as many virtual machine data sources as possible up to the specified DSCollocationfactor limit based on the data sources sizes at the time of enumeration and the replica size.

CollocatedReplicaSize: The default value of replica volume created for collocated Virtual machines 250GB. This can be overridden in the GUI at time of protection. If making changes to the registry, make sure the value entered is a multiple of 1GB (1073741824). The recovery point volume size depends on this value in addition to the retention range specified in the Protection Group. The exact formula is recovery point volume size = (replica volume size * 1.5) * retention days * 0.1 + 1.6GB.

The default Hyper-V Co-located replica volume that DPM creates by default is 250GB meaning we will co-locate as many Hyper-V guests that fit on that 250GB volume up to 8 before we create another 250GB volume. You can override the overall replica volume size in the GUI during protection.

- With DPM 2010 RTM you can protect 400 VM’s of an average 50GB with 10% churn rate using a single DPM server (any mix of that delivers ~20TB of total VM space).

- With DPM 2012 RTM you can protect 400 VM’s of average 100GB with 10% churn rate using a single DPM server (any mix of that delivers ~40TB of total VM space).

- With DPM 2012 SP1 or DPM 2012 R2, you can protect 800 VM's of average 100GB each with 10% churn using a single DPM server (any mix of that delivers ~80TB of total VM space).

- With DPM 2012 SP1 later, DPM will allow multiple DPM servers to communicate with nodes in the cluster so now you can scale your hyper-V cluster to 64 nodes and have multiple DPM servers protect the entire cluster.

See the following blog post on scale out Hyper-V protection:

SC 2012 SP1 – DPM: Leveraging DPM ScaleOut feature to protect VMs deployed on a big cluster

A Windows Server 2012 R2 64 node Hyper-V cluster can support 8000 VM's, so 10 DPM 2012 R2 servers each protecting 800 VM's covers all 8000 VM’s.

To see which virtual machines are co-located on the same replica volume in a protection group, you can run the below DPM PowerShell commands. Look for co-located SQL databases that are on the same replicapath (Volume GUID).

Be sure to replace the 'Protectiongroup_Friendly_Name' before running.

$pg = get-protectiongroup (&hostname) | ? { $_.friendlyname -eq 'Protectiongroup_Friendly_Name'}
Get-datasource $pg  | sort-object -property replicapath | ft replicapath, name, diskallocation -AutoSize

Please be aware of these special considerations when dealing with co-located data sources:

Moving Between Co-Located and Non-Co-Located Protection Groups

Stopping Protection for Co-Located Data

Protect, Unprotect, Protect, Unprotect – Understanding how DPM 2010 retention works

In Summary, I hope you find the above information useful and convenient for one stop shopping for DPM related registry values. I will update this blog as new registry setting are introduced in future releases.

Mike Jacquet| 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/

System Center 2012 Data Protection Manager System Center 2012 R2 Data Protection Manager DPM 2012 R2

Microsoft is happy to announce the release of their newest free ebook, Microsoft System Center Data Protection for the Hybrid Cloud (ISBN 9780735695832), by Shreesh Dubey, Vijay Tandra Sistla, Shivam Garg, and Aashish Ramdas; Mitch Tulloch, Series Editor.

If you are responsible for architecting and designing the backup strategy for your organization, especially if you're looking for ways to incorporate cloud backup into your business continuity scenarios, this book is for you. With the increasing trends in virtualization as well as the move to the pubic cloud, IT organizations are headed toward a world where data and applications run in on-premises private clouds as well as in the public cloud. This has key implications for data protection strategy, and it is important to choose the solution that provides the same level of data protection you have afforded so far while allowing you to harness the power of the public cloud.

We will cover how the Azure Backup service has evolved into a first-class platform-as-a-service (PaaS) service in Microsoft Azure that integrates with the on-premises enterprise class backup product, System Center Data Protection Manager (DPM), to provide a seamless hybrid cloud backup solution. Current backup products treat the cloud as a storage endpoint, which we see as a limited-use case for the public cloud. The approach we describe in this book allows you to exploit the full power of the public cloud and gives you the flexibility to manage your backups in a hybrid world.

We have made a steady set of investments in DPM over the last 18 months, and, as of this writing, we have released six update rollups, including customer hot fixes as well as new features in the areas of private cloud protection, storage optimization, and workload support. The last chapter focuses on the most recently released protection for infrastructure-as-a- service (IaaS) virtual machines, which went to preview release in March 2015 and is expected to be generally available by Q3 of calendar year 2015.

This book covers improvements added in DPM 2012 R2 as well as the integration with Microsoft Azure Backup service and assumes you have working knowledge of the DPM 2012 version.

You can download your free copy here.

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/

System Center 2012 R2 Data Protection Manager

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:

3069110Description 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 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/

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/