i have two quetion
for our scenario : we have to AHV clusters production and DR.
in our scenario we need to stop the main be active after powered on when resolve the issue becouse if the main server goes down the DR will be active and after resolve the issue the two cluster will be active active?
Q2: How to stop auto power on for VMs on AHV ?
that means when the main site be on after solve the issue I do not need the VM powered on automaticlly.. I need to power it manually
.
Hi
Hi TRABELSI,
What are you using for DR i.e. Leap, Metro, Async?
Could you re-word your first question? You need a way to ensure that once the disaster is resolved you do not have both sites (Prod and DR) up and running at the same time?
Hi TRABELSI,
What are you using for DR i.e. Leap, Metro, Async?
Could you re-word your first question? You need a way to ensure that once the disaster is resolved you do not have both sites (Prod and DR) up and running at the same time?
we are going to use Async...Is metro available on AHV ?
about the first question, I mean that when Prod site come back we will find that both of sites are active
Q2: How to stop auto power on for VMs on AHV ?
means when the Prod site come back I need to powered on all VMs manually Not auto
My apologies, I missed the AHV tag. Metro is available for ESXi and Hyper-V but not AHV.
There is a failback process Data Protection and Recovery with Prism Element: Failing Back a Protection Domain that mentions “Deactivate and destroy the VMs by using the following hidden nCLI command. Run this command only when the Protection Domain is active on the secondary site because this command deletes the VMs from the primary site.” as step four.
On AHV VMs do not power on automatically as the CVMs must be up and running first to service storage traffic for the user VMs. Are you observing a different behaviour?
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
