We actually have one job per VM but we thought it would be better to have multiple similar VMs in the same job in order to get the benefits of deduplication. So that raised us a question, what if one of this backups get corrupted? For example, if I have a job which contains two VMs and the backup gets corrupted, will I be able to restore at least one of them in case of disaster?
I know there's the option "Use per-VM backup files" in the repository but this requires Enterprise Edition and we just have Standard Edition
Nope, you will not be able to restore a VM in case of backup file corruption.
It's recommended approach to add VMs in the job by scope, as it allows to utilize parallel processing and other benefits like deduplication. Thanks!
A few safeguards against corruption:
-SureBackup (would be manual for Standard Edition)
-Backup copy job to another storage system
-More active or synthetic full backups on disk
-Add a replication job in the mix; gives you DR and an additional instance of the VM data
Yes, you're right the parallel processing is enabled by default.
Sorry for the confusing statement, I've meant it's simpler to group VMs by a logic entity in a single job.
However, if your infrastructure is quite small, you can stay with the scenario where you have one VM per job.
