Hi
I’m in the process of designing a Metro Availability architecture between two identical AHV clusters, with each site having its own Prism Central.
The first cluster has already been deployed, and some VMs have been migrated to it from the customer’s legacy VMware environment. Once those VMs were running on the first AHV cluster, I assigned them a temporary local Protection Policy (within the same cluster and PC) as a precaution, in case a restore was needed during the following days. The idea is to have at least 1 daily recovery point with a retention of 7 days.
At the moment, all these VMs are located in the cluster’s default container. In order to implement Metro Availability between both clusters, my understanding is that I need to:
-
Create a new container with the same name on both clusters
-
Migrate the VMs from the default container to this new Metro container
-
Then create the sync policy between both sites
-
etc.
Since these VMs are already in production, I’d like to minimize service impact as much as possible.
My questions are:
-
What is the recommended and safest way to migrate production VMs from the default container to a new container? Is storage live migration the preferred approach, or are there any caveats or best practices to consider?
-
What happens to the existing recovery points created by the local Protection Policy once the VM is migrated to a different container? Should those recovery points (or the temporary Protection Policy) be removed before migrating the VMs?
Thanks in advance!
