I'm in the process of demoing VMware's SRM.
The install is good and I can easily run a restore for a single machine.
I'm developing a recovery script for a single application is spread across about 10 servers, a couple sql servers, a couple app servers, a client access machine among a few others.
The priority groups are defined exactly as they should be and I don't need to add any intra group definitions.
When I test my recovery plan I'm seeing priority 1 VMs fire first, priority 2 not at all, and some - about half - of the priority 3 VMs boot. It looks like things eventually move on, still using this odd ordering. What the heck is happening here? Is it related to the method SRM uses to change the IP addresses? Something in the hardware version and/or VMware Tools?
All ESXi hosts and vSphere is 5.5. I'm using vSphere replication and SRM 5.8.1.