Whilst trying to understand why the test failover takes so long we have focussed in on the 5 minute average per VM that it takes to update the networking. We have a customisation set to change the ip address to DHCP, this runs before power on and typically takes around 4: 56 to complete on each VM (as an average). This is clearly just updating the vmx file? any thoughts on how we can reduce this time period or any other options we can try to improve the general performance.
One problem is the amount of datastores to rescan 30+ but this network point keeps jumping off the page...
I haven´t done any testing with the IP customizations until now, but I can tell you that it is not "just updating" the vmx file.
In older version of SRM VMware used the sysprep tools to realize this customization. With 5.0 VMware has it´s own "tool" to do this. But by fact this informations are still stored on the OS layer of the VM i can imagin that this process takes a little bit time (but I don´t know if 5 minutes is normal).
Ok i was curious
Just did a test in my lab and it took me in total 3 minutes to boot a VM with a IP change (see attachment).
If you compare a VM without the IP customization you will notice that you have 3 steps less:
In my test I took an blank XP installation. If you take an Windows 2008 Server with some services running etc. I can imagin that these 3 steps can cost you some minutes, because its an additional boot process.