I've configured some SureBackup jobs at my customers environment and noticed strange behavior. I'm not sure if it's a bug or 'by design' but some improvements can be made here.
Please check the scenario below:
- Backup Job 1
- VM 1
- VM 2
- VM 3
- VM 4 (deleted from job but latest restorepoints still available on disk)
- SureBackup Job 1
- Linked job Backup Job 1
We need a way to skip (e.g. disable network testing) VM4 even when it's not in the job configuration anymore.
Using application groups is not a solution for this because the real jobs have dozens of VM's instead of only 4. Since we cannot configure a maximum of application group VM's to spin up it will exaust our resources in no time.