Hi Keith, 1. External scripts is one option - the post-startup script can return success when the DB/listener/etc. can accept connections. the second option is to use a prompt for a fixed amount of time. There are plans to detect guest OS heartbeat via vmtools. For application related verifications, external script should be used in order to make sure the recovery flow can be resumed. 2. It can be expected on certain network configurations - like common switches/ routers/ etc. I would suggest to try and change the MAC address manually to see if that helps, if it does then this process can be automated as an external script. Let's further discuss offline.  Regards, Idan Kentor RecoverPoint Corporate Systems Engineering
Hello,   Trying to find some additional information/experience with the following operational questions during some recent testing:  1. Is there anyway to insert a delay in between the VM power-up sequence? If there is a DB server with Priority 1, but it takes something like 10 minutes for the DB to perform a consistency check and become online and therefore we would want to hold the App VM from booting up until that time passed to ensure successful connection, is there a way to do this other than external scripts? If not, any idea if this is planned for a future release?  2. During testing, are there any nuances on the networking side when using hardcoded MAC's on the source VM's? By choosing an isolated network for each group, it is expected (and seen in most cases) where the copy VM's power-up and should be able to ping each other in that isolated RP network, however I am noticing tests where, upon boot-up, the IP's associated with the VM's are not the same as the source and rather the Windows automatic-configuration IP's - is this expected or could this be due to the hardcoded MAC addresses? I don't see these same results in my lab tests, but I am seeing them at a particular site.  Any help is appreciated,  Thanks!
RP4VM Test/Failover Orchestration Questions