I just deployed another SureBackup Job at a customer who wants to test some servers without application testing, because the VMs are no DC, fileserver, etc.
After booting the VM during SureBackup, successfull heartbeat and ping Veeam waits another 120 seconds (default value) for the application initialization.
What is the reason to wait for initialization, if I didn't specify any application to test?
I could, of course, set the time to wait to 0 seconds, but wouldn't it be nicer to set it per defaut to 0 seconds, if no application is selected? You could then manually set it to a higher value if there is an application inside the VM which is needed by another VM which should also be tested and depends on services running on the first VM.
Btw.: Why don't you implement a feature to test if user-specified services have been started correctly? You could provide a GUI where the admin could specify the name of a service which should be tested whether if it is running or not. I have seen several times that a server restore completed successful, but then there where problems with third-party services (which of course could have existed before the restore).
I also suggested a year ago or so a feature to test if a network share running on a file server is reachable. This way an admin could specify one or more shares on a file server in the application group with the corresponding credentials and the VBR server or the proxy application tries to reach that share.
VMCE 7 / 8 / 9, VCP-DC 5 / 5.5 / 6, MCITP:SA