Continuous Replication within same pool
-
We're busy migrating from numerous hypervisors to 2 primary ones with each hypervisor (XCP) having 2 separate storage repositories into a single pool so that they can share a common NAS. We want to setup continuous replication from server A SR1 > server B SR2 and same server B SR1 > server A SR2. This will also allow for the hosts to share a common NAS.
Are there any risks or is this frowned upon to replicate a VM within the same pool? I recall having an issue in the past with a duplicate GUID issue, but not sure if that was applicable to this problem?
-
No risk of duplication since we make a copy, it's not the "same" VM per se (same config, same data but it's another "object" in terms of UUID)
-
Thank you @olivierlambert
So in principle there would be no concern with the design of having 2 hypervisors each with 2x local storage repositories each, and each replicating it's storage to another hypervisor in the same pool? Sorry for being anal about this, as we're going into production with this I'm just trying to be prepared for some strange scenario that can occur? Is this a common practice?
Also, if I do CR, how do I avoid 2 VM's being backed up as we only want to backup the primary / running VM?
-
Yes you can do that, there's a tag on a replicated VM to avoid being replicated again.
