Accepted Solutions
There are couple of interesting points here...
Firstly, the others in this thead are correct - SRM failovers all the VMs in the datastore - really the only way to recovery on VM out of datastore that contains 20 is to have a recovery plan just for it - you place 19 of the VMs into the "don't power on" area, and the single VM in the Normal Priority. The whole 20 get recovered during test - but effectively only one VM would be active. It's a clumsy work around which might not serve your purposes - and useless if you want to press run...
We will have to wait until the arrays are VM-ware - where the storage array "knows" that the volumes/luns are formatted for VMFS/NFS, and detect the file type of vmx/vmdk. Things are going in that direction - the new Clarrion CX4 and Navisphere give you excellent visablity to your VM right down to the size and type of virtual disk - within Navisphere...
As for what consitutes a failure. Some people would argue that the lost of one datastore couldn't be considered as disaster - given that might be recoverable by some sort of snapshot that local to the array, rather than replication to another geographical location. As ever i guess depends on the size and scope of your infrastructure...
Finally, automatic failover. With the SDK and some work with .net it is possible to automate the recovery plans. But i feel its dangerous terriritory - because you could could easily get split-brain/false positives. Really, if you looking at that kind of availability - perhaps a stretched HA cluster with something like NetApp's Metro cluster is was needs to be considered...
Regards
Mike Laverick
RTFM Education
Author of the SRM Book:http://www.rtfm-ed.co.uk/2010/03/22/new-administrating-vmware-site-recovery-manager-4-0/
Free PDF or at-cost Hard Copy
There are couple of interesting points here...
Firstly, the others in this thead are correct - SRM failovers all the VMs in the datastore - really the only way to recovery on VM out of datastore that contains 20 is to have a recovery plan just for it - you place 19 of the VMs into the "don't power on" area, and the single VM in the Normal Priority. The whole 20 get recovered during test - but effectively only one VM would be active. It's a clumsy work around which might not serve your purposes - and useless if you want to press run...
We will have to wait until the arrays are VM-ware - where the storage array "knows" that the volumes/luns are formatted for VMFS/NFS, and detect the file type of vmx/vmdk. Things are going in that direction - the new Clarrion CX4 and Navisphere give you excellent visablity to your VM right down to the size and type of virtual disk - within Navisphere...
As for what consitutes a failure. Some people would argue that the lost of one datastore couldn't be considered as disaster - given that might be recoverable by some sort of snapshot that local to the array, rather than replication to another geographical location. As ever i guess depends on the size and scope of your infrastructure...
Finally, automatic failover. With the SDK and some work with .net it is possible to automate the recovery plans. But i feel its dangerous terriritory - because you could could easily get split-brain/false positives. Really, if you looking at that kind of availability - perhaps a stretched HA cluster with something like NetApp's Metro cluster is was needs to be considered...
Regards
Mike Laverick
RTFM Education
Author of the SRM Book:http://www.rtfm-ed.co.uk/2010/03/22/new-administrating-vmware-site-recovery-manager-4-0/
Free PDF or at-cost Hard Copy