How do I maintain backups after moving VMs from a 2012 cluster to a 2012R2 cluster?
I've DPM2012 R2 and it was backing up VMs in a Win 2012 cluster. All good. New Windows 2012 R2 cluster created. Storage detached from existing nodes (iSCSI SAN) and presented to new nodes. Imported VMs, with both register (retain ID) and some copy (new
ID). But if I want to back any of them up, it seems to see them all as new machines. I just want to continue on as nothing in the VMs have changed, just the name in DPM i.e. vm.oldcluster.domain whereas it's now vm.newcluster.domain. Any advice would
be greatly appreciated.
-
Edited by
DP100009
Wednesday, June 24, 2015 6:34 PM
June 24th, 2015 11:09am
Many thanks for coming back to me. It didn't seem to make any difference. Please note they don't have VMM so what I did instead, I substituted the name of the VMM server in your example with a cluster node. It didn't generate an error but nothing appears
to have changed. So when I go to modify the existing protection group and pick the same VM but from a different cluster name, it still insists on seeing it as a new one I'm afraid. If I've to do this for all VMs, I'm going to run out of space
June 25th, 2015 8:22am
Oh dear. Ok. I guess I can't do what I want to do then. Won't have enough space but I'll have to figure something else out so. But if I can ask another question, if I need to restore, would that be an issue? The VM won't have changed but as DPM sees the
VMs as vm.newcluster now, if I did have to restore, what would I have to do, as the historical backups will be vm.oldcluster? As time goes on, this will be less of an issue as new backups will have built up.
June 25th, 2015 9:05am
You can restore to another Hyper-V host or a network share. If you want to restore to the new cluster you have to restore to a node first and later on make that restored machine highly available.
June 25th, 2015 9:07am
Other recent topics
