First off, I want to say that I've spent a large amount of time scanning the forums and internet for a solution to my problem with no luck. Here's the situation, as best as I can describe it:
We currently have 2 2012 R2 DPM servers. Let's call them DPM1 and DPM2. DPM 1 was originally, before my employment here, setup as a primary DPM server backing up a Hyper-V HostServer1 (server 2012 R2) that had 4 virtuals on it. DPM was setup to backup JUST the virtuals on HostServer1, nothing native on the host itself (files, etc.)
At some point later on DPM2 Server was created, and I believe setup as a Secondary DPM server to DPM1. (I'm not completely certain of this, as it does not appear to be setup that way now, but I can't tell for sure) but I believe it was because of the
specific error I'm getting (more on that in a moment)
We want to start backing up the virtuals that are on HostServer1 using DPM2, instead of DPM1. Again, before I started here, the previously person removed all content from DPM1 (protection groups and replica's of the 4 virtual servers that were on
HostServer1, and uninstalled the DPM1 client from HostServer1.
Today I am attempting to add back protection of this HostServer1, but to DPM2. I am able to successfully install the DPM client from DPM2 to HostServer1. When I create a new protection group to DPM2, and navigated down the protection options,
I can see the 4 virtuals running on HostServer1. Here's the weird thing:
I can ADD 3 of the 4 virtuals to the protection group without issue, and successfully back them up! However, ONE virtual, when I check the box throws this error:
"You have chosen to protect replicas on another DPM server (primary DPM server). We recommend that you protect the DPM database of the primary DPM server along with the replicas. Without protecting the DPM Database, you will not be able
to recover the replicas of the primary DPM server in case of a disaster where the DPM Database and the replicas are lost."
It then throws this error:
"One or more of the selected data sources are already configured for protection on the primary DPM server. When you switch back protection, the replicas of these data sources will be protected from the primary DPN server. (ID: 31162)"
If I continue through the PG setup wizard, I see that under the PG game, the DPM1 server name listed, and then this one virtual listed underneath it and the replica shows "unable to configure protection."
I have found numerous threads with this error, but the solutions (ranging from running PS scripts using Attatch-ProductionServer.ps1, to Remove-ProductionServer.ps1 from the primary DPM1 box, etc.) all have failed. Some of these threads are similar
it seems, to my issue, but most of the threads seem to be with an issue when the DPM client is on a protected server, instead of a Hyper-V box running off of a Hyper-V Host, as in my case.
I am either barking up the wrong tree, or not implementing these available DPM PS scripts properly. Can anyone assist me in pointing out what I might be doing wrong, or if that's not the issue, point me in the right direction?
The odd thing here is that 3 of the 4 virtuals work fine when I moved them to DPM2. Only one virtual (which doesn't have a DPM agent on it) throws this error. Somehow, it's as if this particular .vhd has something tagged on it that's making DPM2
think that it's being protected somehow, by DPM1, which is not, or no longer, the case. If it was a DPMDB issue, why are 3 of the 4 other virtuals working fine?
There may be missing information here that's causing this confusing; I'm not entirely sure all 4 were originally backed up by DPM1; but I *BELIEVE* they were. it could be just the troublesome virtual was, not %100 certain of that.
There has to be some way to clear out the reference to DPM1 from this HostServer1, virtual, or DPMDB right? Wherever the issue lies? I would think it's in one of those.
We are not interested in having a Primary or Secondary server any longer, so if the fix somehow lies in clearing out all references the 2 DPM servers of "Primary vs. Secondary", that's fine too. We want 2 separate DPM servers protection two
different sets of Hyper-V hosts, unaware of each other.
Any assistance would be much appreciated!