Has anybody else experienced issues with SRM and customising IPs?
I have 24 VMs which I recover using SRM. When I'm not using the customise IP option, they recover fine besides manually entering their network settings. However when I customise each VM with their appropriate IP settings, the recovery always fails.
I have found the issue to be SRM ignoring the priority groups when it comes to these activities for each VM:
- Configure Storage
- Configure Test Network
- Guest Startup
- Customise IP
- Guest Shutdown
Then the VM priority order actually works from this point for:
- Power On
- Wait for VMware tools
After SRM finishes the "Create Writeable Storage Snapshot" step, it then completes ALL of the steps highlighted in red for every single VM at once! This is causing the cluster to overload and pretty much cause every VM to fail.
VMware have acknowledged this as an issue and suggested I try the work around of using blank steps with a prompt to resolve the issue. However it doesn't fix it. I've successfully ran several recovery jobs using Customise IP with only 3 VMs and it works perfectly because it isn't starting many VMs at once.
I have raised a feature request with VMware however I've been told it is too late to be looked at for the up coming release. So it 'might' be addressed in the following one....if they consider fixing it.
The way I see it at the moment, if customise IP can't even work with 24 VM's (SRM starter pack is 25) then it is completely useless. It's a shame because it was one of the main selling points as to why I picked a VMware + SRM solution.
Has anybody else experienced this issue and if so, do you have a temporary fix for it?
Regards
Leigh