Hi

I'm having issues with successfully changing some VM servers which are in a clustered Hyper V 2012 R2 environment from a DPM 2012 R2 server located in one site to the other. 

The VMs themselves were recently migrated over from one site to the other in Hyper-V and are working fine. This required the Protection Group in DPM which was backing up successfully from the original site to be stopped (ORIGINALSITEDPM). I kept the restore points. Then I set it up again on the DPM server on the other site for DR. 

Two of the VM servers are now backing up on DPM just fine, but 7 out of the 9 have not. I get the following errors on the failing servers Unable to configure protection :-

Details:-

Affected area: \Online\SERVERNAME
Occurred since: 09/09/2015 10:59:43
Description: DPM could not start a recovery, consistency check, or initial replica creation job for Microsoft Hyper-V \Online\SERVERNAME on ORIGINALSITEDPM for following reason:
 (ID 3170)
The operation failed for Microsoft Hyper-V \Online\SERVERNAME on ORIGINALSITEDPM because the data source is not available. (ID 30169 Details: VssError:The specified object was not found.
 (0x80042308))
More information
Recommended action: To troubleshoot this issue, verify the following:
1) The data source is online.
2) The data source is not in a restoring state.
3) The application VSS writer is running.
4) The data source is accessible.
5) The data source is not missing.
6) If the data source is a member of a SharePoint farm, verify it still exists in the SharePoint farm configuration.
For more information on this error, go to http://go.microsoft.com/fwlink/?LinkId=132612.
Run configure protection job again...
Resolution: To dismiss the alert, click below
Inactivate

The bit that puzzles me is why it is using the ORIGINALSITEDPM reference at all in the error, since these devices are located on the production cluster and are now in the Inactive Protection on the ORIGINALSITEDPM server, just like the other ones which did work fine. This error is showing on the NEWSITEDPM which is strange. So far I have tried:

1. Rebooted both DPM servers on both sites

2. Deleted the Protection Group and Recreated it several times

3.Tried starting/stopping/restarting DPM agent on HyperV hosts

4. Followed through any articles I could find online 

I have not tried rebooting the VMs as yet because they are 24/7 prouction boxes and I wanted to exhaust all other avenues first

Thanks

 

• Edited by alig69 Friday, September 11, 2015 9:04 AM

Thanks for the reply, however I have tried the steps suggested and am still getting the same problem. 

Our DPM 2012 R2 servers are both on version 4.2.1338. (Update Roll-up 7)

One other warning message I get is as follows when I create the protection group :-



Now this would make you think that the original DPM server is still protecting the servers, but it is not. Some of them are in the Inactive Protection Group, but so are some of the servers which are backing up fine. I certainly don't wish to lose old replicas if possible.

We have also now rebooted the VMs involved and this has had no effect on the problem

Thanks

Hi,

The issue seems to be that you have secondary protection enabled, and you cannot move protected data sources between DPM servers.  This is covered in the below TechNet article.

Unsupported Scenarios for DPM
http://technet.microsoft.com/en-us/library/dn554221.aspx#BKMK_Install

Look in installation and deployment issues section under the heading "Moving protected servers with DPM secondary servers"