we have three primary and three secondary dpm 2012sp1 servers.
Im starting to think that the primary/secondary concept is a bit overkill in for us.
If it's supported, and not too stupid, i'd like to stop protecting some servers on the primary retaining the short-term data, and then pick the protected member up on the secondary server to protect it directly instead of secondarly.
1. stop all protection for the PS on the PrimaryDPM.
2. Remove the attached agent on the primary with "Remove-ProductionServer.ps1"
3. run setdpmserver -dpmservername <secondary>
4. attach the PS to the secondary dpmserver
5. Add the, say C-drive on the PS to a PG.
With or without a retained diskdata on the secondary, I end up with this when the C-drive is added to a PG
Affected area: C:\
Occurred since: 2014-04-22 16:54:27
Description: DPM could not start a recovery, consistency check, or initial replica creation job for Volume C:\ on primarydpmserver for following reason:
(ID 3170)
The operation failed for Volume C:\ on secondarydpm 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
Is this even supported?
if so, how can I get the secondary srever to 'forget' that it had previously protected a PS secondarly?
Ivarson
