A feature I believe would be extremely useful would be scheduling SureBackup around the completion of a Backup Copy Job. Backup Copy Jobs aren’t scheduled the same as usual jobs so I understand the additional complexity around this however the reason for my request is simple.
One of SureBackup’s primary limitations is Disk IO, if we create a SureBackup job to run after a backup job is complete, a Backup Copy Job could then start consuming IO to transmit this backup to an archive tier, Cloud Connect or to some other secondary repository. This creates contention for IO with SureBackup, impacting the ability to validate virtual machines.
A key example of this behaviour is when VMware Tools fails to start within the traditional 30 seconds (I’m aware of registry keys that can amend this behaviour, but it’s just one example). If we could chain either BCJ’s to run after a backup is validated (so we know we’re copying good data firstly) or even inversely whereby we run SureBackup after the copy just to avoid contending for IO, both of these would help validate recoverability. Currently the best workaround is to schedule SureBackup for a time when you don’t believe that any disk IO contention should occur, but this is a best effort as retention policies can always throw your calculations off!
What do you think, anyone else agree with this?