Thanks for the reply. Nope, no Surebackup being used.
The reason for this is simply the environment here. We'd have 250+ more jobs to add on top of the nightly backup jobs. The main issue I saw is that a Veeam server starts to buckle under the load of about 100 concurrent jobs. Things just begin to error out at that point. This is also the reason I use Hyper-V replication rather than Veeam, despite the I/O hit
I'm hoping V8 is more scalable for us. Our DB and application servers easily handle the load, its just the Veeam application itself that has problems. We've mostly worked around this.
Do you know of any other customers of our "branch office" environment running Sure Backup jobs everywhere? I mean, it just adds so much more complexity. For instance, when Veeam runs an restore using "Other OS" and creates the Linux appliance, it occasionally doesn't remove the appliance after ending the job. We have to go out manually and do this. I'm worried we'd see more problems like this get introduced.
Would running active full backups clear out any corruption in the backup chain? If it builds an entirely new chain, I would consider that an acceptable risk. I could simply run an active full each week, reducing my risk.