This is really needed. I don't understand how SureBackup determines a success vs fail when no tests are selected
VM1: No VMware Tools, Network not mapped in Virtual Lab. Heartbeat and Ping test not enabled. After waiting the entire Bootup time, it reports that the VM booted successfully and the status is Success
VM2: VMware Tools installed, Network mapped but the first IP returned in non-routable and a second is accessible. Heartbeat and Ping tests not enabled. SureBackup detects the non-routable IP and reports No destination network for the non-routable and the status is Failed
VM3: VMware tools installed, Network mapped, but due to RDM dependencies, OS will not boot with a failed fsck and we are OK with this as we have a documented plan. Heartbest and Ping tests not enabled. SureBackup reports it did not boot and the status is Failed.
On all 3 of these, I am aware that they will not fully be bootable/testable in SureBackup, which is why I have disabled every test and set a short boot time as I don't want to waste time for them to boot if I can't verify it. My SureBackup job is based on a Linked job. This is my example of just a few situations where either we need to be able to exclude a VM from Surebackup entirely, or just allow a VM that has no tests enable to always show as a success. If I'm not asking SureBackup to test anything, then why would it ever show me a failure? Even more confusing when some instance it still shows a success and others a fail.