Data Protection Manager - General announcement
-
Link
There is one optimization change you can make in DPM 2016 using Modern Backup Storage that “may” help reduce the backup times. The issue is that DPM tries to get the size of the recovery point by asking ReFs to count the blocks associated with that recovery point so it can update the DPMUI “storage used” in the UI.
To eliminate that additional calculation that can take a long time and allow the next backup to start you can disable that calculation using the below DPM powershell command.
Manage-DPMDSStorageSizeUpdate.ps1 -ManageStorageInfo StopSizeAutoUpdate
As a result, the “storage consumed” for each data source will not be displayed after a new backup is completed.
The above is covered in the release notes: https://docs.microsoft.com/en-us/system-center/dpm/dpm-release-notes
Section titled: Recovery Points not being pruned, leading to an accumulation of Recovery Points.
If you need to know the amount used for a data source you can use the associated UpdateSizeForDS command.
-
Link
There may be circumstances where the replica volume for a protected data source is under allocated or a very large increase of protected data results in synchronization or recovery point job failures due to inadequate space on the replica.
Type: Recovery point
Status: Failed
Description: DPM is out of disk space for the replica. (ID 58 Details: There is not enough space on the disk (0x80070070))As in previous versions, DPM 2016 has replica auto-grow feature for modern backup storage (MBS) to help increase the replica sizes as the data sources grows. Under normal use conditions this feature works perfectly fine. If a job fails due to out of disk space, it will automatically grow the replica volume and schedule a new synchronization or recovery point job to run one hour in the future. However, if the amount of new data is much larger than the size of the replica after auto-grow, the jobs will continue to fail even as the auto-grow continues to increase the replica size. After two failures, auto-rerun is no longer triggered by default. In DPM 2012 R2 you had the ability to manually grow the replica volume as large as you wanted by using the “modify disk allocation” wizard, however in the DPM 2016 you do not have the ability to manually grow the replica volume using the same wizard. This can cause delays in getting good backups again to meet your SLA. If you know the new size of the protected data or want to grow the replica volume for future data growth in order to prevent future backup failures, you can grow the replica manually.
The below BLOG contains a DPM PowerShell script to make it easy to manually increase a replica volume to the new desired size.
How to increase DPM 2016 replica when using Modern Backup Storage (MBS)
-
Link
When using DPM 2016 to protect SystemState / BMR workloads the storage used for those backups will be higher when using DPM Modern Backup Storage (MBS) as compared to using legacy Logical Disk Manager (LDM) based storage used in DPM 2012 R2.
When DPM initiates a SystemState or BMR backup, Windows Server Backup is used and overwrites the existing WindowsImagebackup folder with the new backup data. For SystemState that folder is on the protected server and later transferred to the DPM Server replica. For BMR, Windows Server Backup overwrites the folder on the Replica volume directly.
When the replica is located on a LDM based volume, Volume Shadow Copy (VSS) snapshots are used for recovery points. When the files are overwritten on the replica volume, VSS performs a read for the original file blocks – compares them to what is about to be written - then either copies the original blocks to the shadow copy (recovery point volume) if different or just lets the write thru if the blocks are identical. This is called Copy On Write (COW). Between backups a lot of the blocks are the same between the files so the shadow copies were relatively small.
Modern Backup Storage (MBS) uses ReFs clones for recovery points. There is no copy on write operation like there are when using VSS, all writes are performed but instead of overwriting the original files the new blocks are written to different locations on the MBS volume. This is called allocate on write, so even blocks that are the same will use different free space on the Refs volume. That results in more storage consumption as each backup will consume the amount of space as a complete SystemState or BMR backup. IE: If the initial replica size shows 24GB used, then all subsequent backups will come very close to consuming the same amount of space. If the backups are taken frequently or have a long retention period the storage usage can be significant.
To mitigate this behavior I would suggest either take fewer BMR / SystemState recovery points, use a reduced retention period, or just plan on needing more storage for SystemState / BMR backups.
-
Link
System Center Data Protection Manager 2012 R2 UR11 added support for VMware host level backup. If you attempt to perform an Item Level Recovery (ILR) from the latest recovery point for a Protected Windows VM, you receive an ID: 958 popup error message with the below details.
IMPORTANT NOTE: This problem is not present in Microsoft Azure Backup Server (MABS) update rollup 1 (UR1) that also added support for VMWare host level backups.
WORKAROUND(S)
===========1) Select an earlier recovery point if the file(s) (version) you want to recover was included in an earlier recovery point.
2) Restore the entire VM to an alternate location and copy the desired file(s) out of that restored VM.
3) Create a new AD-HOC recovery point manually. That will enable ILR to work for all recovery points including the latest one you made manually.UPDATE: This issue is now fixed in DPM 2012 R2 UR13. However, you need to consider the following for the fix to work.
1. For Protection Groups created after applying UR13, Item Level Recovery will work fine.
2. For older Protection Groups, you need to modify the PGs by adding/removing a small VM or making some configuration changes to the PG for the fix to work. - Link
-
Link
SC DPM 2016 brings in features that delivers improvements in multiple key areas of backup efficiency, performance, flexibility and security. With Modern Backup Storage (MBS), DPM 2016 is turning around the way backups are stored by leveraging modern technologies like ReFS Block Cloning, ReFS Allocate On Write and VHDX. This to 3X faster backups and 50% reduction in storage consumption thus reducing overall backup TCO.
https://blogs.technet.microsoft.com/dpm/2016/10/19/announcing-sc-dpm-2016-with-modern-backup-storage/ -
Link
DPM 2016 comes with Modern Backup Storage which delivers 50% storage savings, 3x faster backups, and more efficient storage with Workload-Aware storage. Modern Backup Storage can be used by setting up DPM 2016 on Windows Server 2016.
Add Storage to DPM 2016 -
Link
Very happy to report the release SC DPM 2012 R2 UR11 that adds protection for VMware host level backup of VMs. Here are major features of VMware VM Backup. Here are the few highlights of VMware VM backup.
- Agentless backup
- Backup at vCenter or ESXi level
- Backup VMware VM folders
- Ability to do ILR
- Protect large data center using DPM Scale Out
- Backup to Disk/Cloud
Here are the blogs and articles that are published.
BLOG - Implementing Microsoft DPM host level protection of VMware VMs
BLOG-Announcing VMware VM Backup using System Center Data Protection Manager
-
Link
We have made a bunch of improvements in this update, related to reboot requirements, Enterprise file server backup, online backups and more.
-
Link
After you install DPM 2012 R2 UR7 update (KB3065246), DPM cannot delete expired recovery points. This will lead to extra recovery point volume usage.
Please download and install the fix for this issue.
Fix for a known issue with Update Rollup 7 for System Center 2012 R2 Data Protection Manager
MORE INFORMATION
==============DPM 2012 R2 UR7 introduced a new switch to the powershell cmdlet Get-RecoveryPoint, it now requires a -Datasource switch as seen below:
Get-RecoveryPoint -Datasource $ds
If you have any custom powershell scripts that use that cmdlet, please modify them to use the new -Datasource switch.
-
Link
Below are some handy links for the DPM Console troubleshooter which can help you resolve console crashes and three DPMDB maintenance blogs.
Guided Walkthrough for Troubleshooting Data Protection Manager console issues
DPMDB Maintenance Part 1: Database consistency check and your DPMDB
DPMDB Maintenance Part 2: Identifying and dealing with fragmentation in your DPMDB
DPMDB Maintenance Part 3: Dealing with a large DPMDB -
Link
Hello - Please find the following BLOG on the new streamlined method of registering a DPM 2012 SP1 or later DPM server to backup to Azure. There is no longer a requirement to upload a certificate when registering a DPM server for online backups.
Below are two Blogs on the subject.
How to register a DPM 2012 SP1 or later server to backup to Microsoft Azure
Simplified workflow to configure backup to Azure from DPM -
Link
Please find the following whitepaper detailing how to dedup DPM storage pool to help reduce overall disk storage requirements for disk based backups. This solution requires Windows 2012 R2 and System Center Data Protection Manager 2012 R2
-
Link
For DPM Console crash issues, please review this troubleshooter before posting a new question.
Guided Walkthrough for Troubleshooting Data Protection Manager console issues
-
Link
updated 6-5-13
Hello Everyone,
System Center DPM 2012 is not supported running on Windows Server 2012. We have had reports of DPM 2012 console crashes when navigating to the recovery tab if DPM 2012 is installed on Windows server 2012. This issue is fixed in System Center 2012 SP1 which supports being installed on Windows 2012 operating system.
If you are already in this condition, you have two options:
A) You can upgrade to System Center 2012 Sp1.
B) You can backup the DPMDB, rebuild the DPM server using Windows 2008 R2 install DPM 2012, then restore your current database. The process is explained in the below technet article.
Recovering DPM servers
http://technet.microsoft.com/en-us/library/jj244606.aspxWe also do not support protecting Windows Server 2012 workloads using SCS DPM 2012, you must upgrade to DPM 2012 Sp1. Please do not expect any support for DPM 2012 running on Windows Server 2012, or issues while protecting data sources in Windows Server 2012.
-
0 Votes
How to ask a question efficiently in TechNet forum
Thank you for posting in TechNet forum. The online problem solving can be relatively time consuming because it may demand several messages back and force to fully understand the symptom and ... -
3 Votes
*** Read this before posting to these forums ***
Welcome to the Data Protection Manager community! System Center Data Protection Manager forum provides you an opportunity to join a community of DPM ...Sticky | 2 Replies | 15157 Views | Created by Praveen T [MSFT] - Thursday, May 13, 2010 7:22 PM | Last reply by BobH2 - Wednesday, April 20, 2011 3:06 AM
-
0 Votes
Primary DPM 2012R2 server crashes (reboot) after adding a secondary DPM
Hi there, I have the following issue - my primary DPM server started crashing (reboot) after adding a secondary DPM server. This happened even from the beginning, after attaching ...Unanswered | 5 Replies | 82 Views | Created by Alex Rowdy - Wednesday, April 18, 2018 2:24 PM | Last reply by Alex Rowdy - 53 minutes ago -
0 Votes
VM Migration Problem.
Hi. I have migrate many V Ms between two efferent host without problem but we have exception for 2 or 3. I get error(23008) incompatibility. We set same virtual switch ... -
0 Votes
Planning SCOM Architecture
hi, Through SCOM my organization wants to monitor 1000 Agents, 500 network device and want trend analysis for 2 years I am planning for two Management server with ... -
0 Votes
DPM console Crash
Hi everyone. Im running DPM 2016 on server 2016 with SQL 2012 This was an upgrade from DPM 2012r2 Im trying to add a server to a protection ...Unanswered | 5 Replies | 47 Views | Created by tofieldv - Tuesday, April 17, 2018 8:28 AM | Last reply by Rahul.Choudhary - 12 hours 1 minutes ago -
0 Votes
Repair DPM 2012 r2 server and SQL database do not use DpmBackup and DpmSync?
Hi Everybody, I have SCDPM 2012 R2 server and remote SQL Server for DPM. my problem DPM server host in hyper-v had failure. I can't start that VM. In ...Unanswered | 1 Replies | 28 Views | Created by za_phu - Tuesday, April 17, 2018 6:16 AM | Last reply by Matej Klemencic - Tuesday, April 17, 2018 5:04 PM -
0 Votes
Incorrect storage used space?
Hello All, I have a DPM 2016 server that has 5 2TB disks in a disk pool. The server is backing up a number of SQL data sources. The disk storage screen is showing me numbers that ... -
0 Votes
SQL (DPM) Database Running Out of Space - Advice?
Space available: The table which appears to be consuming the space is: Table Name # Records Reserved (KB) Data (KB) Indexes ... -
1 Votes
Scheduled jobs are not running DPM 2012 R2
Hi, Recently upgraded my dpm 2012 sp1 to 2012 R2 and upgrade went well but i got 'Connection to the DPM service has been lost.(event id:917 and other event ids ...Proposed | 7 Replies | 1317 Views | Created by Sri26 - Sunday, July 20, 2014 8:52 AM | Last reply by Rahul.Choudhary - Saturday, April 14, 2018 7:35 AM -
0 Votes
DPM Semaphore timeout period expired during consistency check
We have 2 DPM servers (one on-site and one remote). The issue resides on the remote DPM server. We recently created a new logical drive, which wiped all data. All replicas became ...Unanswered | 6 Replies | 2113 Views | Created by succ123 - Thursday, August 07, 2014 12:29 PM | Last reply by DirectorBrandX - Friday, April 13, 2018 6:37 PM -
0 Votes
Estimating Azure Backup billing usage for DPM datasources
Hi all, Hi have DPM 2012 R2 in-place and would like to start doing long term backup to Azure. To estimate costs, or at least have an idea of what to expect, I ...Unanswered | 2 Replies | 87 Views | Created by v-rusant - Thursday, April 12, 2018 2:46 PM | Last reply by v-rusant - Friday, April 13, 2018 10:35 AM -
0 Votes
DPM 2016 with Azure Online - Reporting
Hi, I'm sending some of my DPM backups to an Azure Recovery Vault which is working great. However, what I would really like to do is get some reporting so that I can better plan for billing. I ...Proposed | 2 Replies | 332 Views | Created by Kyle Kartan - Monday, February 20, 2017 2:42 PM | Last reply by PMLIO - Tuesday, April 10, 2018 4:50 PM -
0 Votes
DPM 2012 R2 with SQL 2016?
One of my customers currently run DPM 2012 R2 on a SQL Server 2008 R2. They want to upgrade to DPM 2016, but first I need to upgrade the present SQL version to 2016. My first question - is it possible ...Unanswered | 1 Replies | 47 Views | Created by Jaan Meijer - Tuesday, April 10, 2018 7:08 AM | Last reply by Matej Klemencic - Tuesday, April 10, 2018 3:58 PM -
0 Votes
SCCM and Microsoft Azure Backup Server
I'm running SCCM 2016 (v5.0.158.0) on premises with azure backup agent version 2.0.9118.0. I'm backing up SQL databases and replicating to Azure recovery services ... -
0 Votes
DHCP SERVER CALLOUT AND IPV6
Hi, I’m in charge of developping a callout dll for the dhcp server. For the moment this dll only shows a packet that arrives in the dhcp server. An ipv4 packet is routed to ... -
0 Votes
Is SQL 2012 SP4 supported to host the DPM database?
Would like to know if I can upgrade the SQL server that is hosting the DPM database from SQL 2012 SP1 to SQL 2012 SP4. ThanksUnanswered | 3 Replies | 70 Views | Created by strongbad2 - Thursday, April 05, 2018 5:05 PM | Last reply by Matej Klemencic - Friday, April 06, 2018 6:50 PM -
2 Votes
In-Place Upgrade Operating System to Windows Server 2016
Hi everyone. Is this limitation regarding OS upgrade still valid with DPM 2016?: In-place upgrade of the operating system on a server running DPM isn’t ...Answered | 6 Replies | 2196 Views | Created by MarxA - Friday, October 28, 2016 9:32 PM | Last reply by kenk223 - Friday, April 06, 2018 4:03 PM -
1 Votes
DPM 2016 console crashes
DPM 2016 console crashes Hi guys, I am running DPM 2016 with CU4, on Windows Server 2012 R2 fully ...Unanswered | 3 Replies | 160 Views | Created by balboa41 - Wednesday, March 28, 2018 6:42 PM | Last reply by balboa41 - Friday, April 06, 2018 2:36 PM -
0 Votes
DPM 2016 MBS Performance downward spiral
Hi Guys! I´m so pissed, really i´m at a point were i would like to just uninstall and go home. Why? Since we upgrade to DPM 2016 and switched ...Unanswered | 47 Replies | 1251 Views | Created by Intirius - Thursday, January 25, 2018 12:42 PM | Last reply by Christian_Wimmer - Friday, April 06, 2018 1:13 PM -
0 Votes
Online recovery point ETA
I am 75 hours into a "Online recovery point" and have no clue how long this is going to take. Typically ones have been about 6 to 8 hours when they are working nightly. However we had a ...Unanswered | 1 Replies | 66 Views | Created by JustusIV - Wednesday, April 04, 2018 3:03 PM | Last reply by JustusIV - Friday, April 06, 2018 12:17 PM -
0 Votes
DPM 2012 R2 online restore failed and space that used for local restore was not released
Hi All, We are doing online restore and we use D drive (500 GB free space available) as per config. When online recovery from cloud to my backup server D drive ...Proposed | 4 Replies | 83 Views | Created by Ajay Kumar Nakka - Wednesday, April 04, 2018 3:37 AM | Last reply by Tome Lopes - Thursday, April 05, 2018 9:39 PM - Items 1 to 20 of 5062 Next ›
Data Protection Manager - General announcement
-
Link
There is one optimization change you can make in DPM 2016 using Modern Backup Storage that “may” help reduce the backup times. The issue is that DPM tries to get the size of the recovery point by asking ReFs to count the blocks associated with that recovery point so it can update the DPMUI “storage used” in the UI.
To eliminate that additional calculation that can take a long time and allow the next backup to start you can disable that calculation using the below DPM powershell command.
Manage-DPMDSStorageSizeUpdate.ps1 -ManageStorageInfo StopSizeAutoUpdate
As a result, the “storage consumed” for each data source will not be displayed after a new backup is completed.
The above is covered in the release notes: https://docs.microsoft.com/en-us/system-center/dpm/dpm-release-notes
Section titled: Recovery Points not being pruned, leading to an accumulation of Recovery Points.
If you need to know the amount used for a data source you can use the associated UpdateSizeForDS command.
-
Link
There may be circumstances where the replica volume for a protected data source is under allocated or a very large increase of protected data results in synchronization or recovery point job failures due to inadequate space on the replica.
Type: Recovery point
Status: Failed
Description: DPM is out of disk space for the replica. (ID 58 Details: There is not enough space on the disk (0x80070070))As in previous versions, DPM 2016 has replica auto-grow feature for modern backup storage (MBS) to help increase the replica sizes as the data sources grows. Under normal use conditions this feature works perfectly fine. If a job fails due to out of disk space, it will automatically grow the replica volume and schedule a new synchronization or recovery point job to run one hour in the future. However, if the amount of new data is much larger than the size of the replica after auto-grow, the jobs will continue to fail even as the auto-grow continues to increase the replica size. After two failures, auto-rerun is no longer triggered by default. In DPM 2012 R2 you had the ability to manually grow the replica volume as large as you wanted by using the “modify disk allocation” wizard, however in the DPM 2016 you do not have the ability to manually grow the replica volume using the same wizard. This can cause delays in getting good backups again to meet your SLA. If you know the new size of the protected data or want to grow the replica volume for future data growth in order to prevent future backup failures, you can grow the replica manually.
The below BLOG contains a DPM PowerShell script to make it easy to manually increase a replica volume to the new desired size.
How to increase DPM 2016 replica when using Modern Backup Storage (MBS)
-
Link
When using DPM 2016 to protect SystemState / BMR workloads the storage used for those backups will be higher when using DPM Modern Backup Storage (MBS) as compared to using legacy Logical Disk Manager (LDM) based storage used in DPM 2012 R2.
When DPM initiates a SystemState or BMR backup, Windows Server Backup is used and overwrites the existing WindowsImagebackup folder with the new backup data. For SystemState that folder is on the protected server and later transferred to the DPM Server replica. For BMR, Windows Server Backup overwrites the folder on the Replica volume directly.
When the replica is located on a LDM based volume, Volume Shadow Copy (VSS) snapshots are used for recovery points. When the files are overwritten on the replica volume, VSS performs a read for the original file blocks – compares them to what is about to be written - then either copies the original blocks to the shadow copy (recovery point volume) if different or just lets the write thru if the blocks are identical. This is called Copy On Write (COW). Between backups a lot of the blocks are the same between the files so the shadow copies were relatively small.
Modern Backup Storage (MBS) uses ReFs clones for recovery points. There is no copy on write operation like there are when using VSS, all writes are performed but instead of overwriting the original files the new blocks are written to different locations on the MBS volume. This is called allocate on write, so even blocks that are the same will use different free space on the Refs volume. That results in more storage consumption as each backup will consume the amount of space as a complete SystemState or BMR backup. IE: If the initial replica size shows 24GB used, then all subsequent backups will come very close to consuming the same amount of space. If the backups are taken frequently or have a long retention period the storage usage can be significant.
To mitigate this behavior I would suggest either take fewer BMR / SystemState recovery points, use a reduced retention period, or just plan on needing more storage for SystemState / BMR backups.
-
Link
System Center Data Protection Manager 2012 R2 UR11 added support for VMware host level backup. If you attempt to perform an Item Level Recovery (ILR) from the latest recovery point for a Protected Windows VM, you receive an ID: 958 popup error message with the below details.
IMPORTANT NOTE: This problem is not present in Microsoft Azure Backup Server (MABS) update rollup 1 (UR1) that also added support for VMWare host level backups.
WORKAROUND(S)
===========1) Select an earlier recovery point if the file(s) (version) you want to recover was included in an earlier recovery point.
2) Restore the entire VM to an alternate location and copy the desired file(s) out of that restored VM.
3) Create a new AD-HOC recovery point manually. That will enable ILR to work for all recovery points including the latest one you made manually.UPDATE: This issue is now fixed in DPM 2012 R2 UR13. However, you need to consider the following for the fix to work.
1. For Protection Groups created after applying UR13, Item Level Recovery will work fine.
2. For older Protection Groups, you need to modify the PGs by adding/removing a small VM or making some configuration changes to the PG for the fix to work. - Link
-
Link
SC DPM 2016 brings in features that delivers improvements in multiple key areas of backup efficiency, performance, flexibility and security. With Modern Backup Storage (MBS), DPM 2016 is turning around the way backups are stored by leveraging modern technologies like ReFS Block Cloning, ReFS Allocate On Write and VHDX. This to 3X faster backups and 50% reduction in storage consumption thus reducing overall backup TCO.
https://blogs.technet.microsoft.com/dpm/2016/10/19/announcing-sc-dpm-2016-with-modern-backup-storage/ -
Link
DPM 2016 comes with Modern Backup Storage which delivers 50% storage savings, 3x faster backups, and more efficient storage with Workload-Aware storage. Modern Backup Storage can be used by setting up DPM 2016 on Windows Server 2016.
Add Storage to DPM 2016 -
Link
Very happy to report the release SC DPM 2012 R2 UR11 that adds protection for VMware host level backup of VMs. Here are major features of VMware VM Backup. Here are the few highlights of VMware VM backup.
- Agentless backup
- Backup at vCenter or ESXi level
- Backup VMware VM folders
- Ability to do ILR
- Protect large data center using DPM Scale Out
- Backup to Disk/Cloud
Here are the blogs and articles that are published.
BLOG - Implementing Microsoft DPM host level protection of VMware VMs
BLOG-Announcing VMware VM Backup using System Center Data Protection Manager
-
Link
We have made a bunch of improvements in this update, related to reboot requirements, Enterprise file server backup, online backups and more.
-
Link
After you install DPM 2012 R2 UR7 update (KB3065246), DPM cannot delete expired recovery points. This will lead to extra recovery point volume usage.
Please download and install the fix for this issue.
Fix for a known issue with Update Rollup 7 for System Center 2012 R2 Data Protection Manager
MORE INFORMATION
==============DPM 2012 R2 UR7 introduced a new switch to the powershell cmdlet Get-RecoveryPoint, it now requires a -Datasource switch as seen below:
Get-RecoveryPoint -Datasource $ds
If you have any custom powershell scripts that use that cmdlet, please modify them to use the new -Datasource switch.
-
Link
Below are some handy links for the DPM Console troubleshooter which can help you resolve console crashes and three DPMDB maintenance blogs.
Guided Walkthrough for Troubleshooting Data Protection Manager console issues
DPMDB Maintenance Part 1: Database consistency check and your DPMDB
DPMDB Maintenance Part 2: Identifying and dealing with fragmentation in your DPMDB
DPMDB Maintenance Part 3: Dealing with a large DPMDB -
Link
Hello - Please find the following BLOG on the new streamlined method of registering a DPM 2012 SP1 or later DPM server to backup to Azure. There is no longer a requirement to upload a certificate when registering a DPM server for online backups.
Below are two Blogs on the subject.
How to register a DPM 2012 SP1 or later server to backup to Microsoft Azure
Simplified workflow to configure backup to Azure from DPM -
Link
Please find the following whitepaper detailing how to dedup DPM storage pool to help reduce overall disk storage requirements for disk based backups. This solution requires Windows 2012 R2 and System Center Data Protection Manager 2012 R2
-
Link
For DPM Console crash issues, please review this troubleshooter before posting a new question.
Guided Walkthrough for Troubleshooting Data Protection Manager console issues
-
Link
updated 6-5-13
Hello Everyone,
System Center DPM 2012 is not supported running on Windows Server 2012. We have had reports of DPM 2012 console crashes when navigating to the recovery tab if DPM 2012 is installed on Windows server 2012. This issue is fixed in System Center 2012 SP1 which supports being installed on Windows 2012 operating system.
If you are already in this condition, you have two options:
A) You can upgrade to System Center 2012 Sp1.
B) You can backup the DPMDB, rebuild the DPM server using Windows 2008 R2 install DPM 2012, then restore your current database. The process is explained in the below technet article.
Recovering DPM servers
http://technet.microsoft.com/en-us/library/jj244606.aspxWe also do not support protecting Windows Server 2012 workloads using SCS DPM 2012, you must upgrade to DPM 2012 Sp1. Please do not expect any support for DPM 2012 running on Windows Server 2012, or issues while protecting data sources in Windows Server 2012.