Since you haven't got any replies. I throw a stab at it being a San Admin.
I do also have 2 EVA 5000's same location though..
Consceptually. You would need VC w/HA (not just ESX HA)
I wonder if you granted access to the replicated volume in Site B to the ESX server over there and added it to the cluster, then should Site A go down Vcenter HA should kick in at Site B and turn on all the VM's against thier locally attached EVA at site B.
Don't know if that'd work...but Alteast u get a free bump.
GL. I'm also interested in this.
Maybe I should describe what is happening at present. If we initiate a manual failover from one EVA to the other, all VMs will hang and the VMFS volume can no longer be seen even though Continuous Access has presented the replicated volume back to the ESX servers. In order to see the volume we have to rescan the storage adapters and then refresh the datastores in VC. Then I can restart the VMs. The problem arises when one of the ESX servers goes down at the same time as a Continuous Access failover. Then, the VMs that were running on that server appear grayed out in VC and say disconnected. Most right-click options are also grayed out including power on/off, remove from inventory, etc.
Glad to have your input on this.
When you have a site failover but you can connect to the vc.
You can (cold) migrate the virtual machines to the running ESX servers.
HA clusters can do this for you.
Vmware has posted the following document about HA:
Automating High Availability (HA) Services with VMware HA
OK this is no problem, doing the same thing with Clariions.
present the LUNs to you a esx box in you DR site.
i VC delete the cluster that has failed, this will remove all disconected hosts and VMs.
browse the data store from the DR esx host and add the vms back into the inventory and power on.
This would pose a problem for me as my customer is looking for an automated disaster tolerant solution for maybe 100 VM's.