Issue with new SureBackup Job design - can't exclude old VMs in Repo but not existing in Environment anymore...

[DaStivi]

Hey there i found a small issue with the new SureBackup Job Design, maybe i do missunderstand how its supposed to work... another small thing, before 12.2 you could run a new Backup within the SureBackup Job, but this has been replaced with the test for the whole Job and simultaneously processing of not more then XXX machines, isn't it? so no new backup can be triggerd (from the UI, maybe with script, yes..)

but my real issue now is, when the Surbackup job is running, it tests all VM-Object that have been in backup, so also all Templates are tested and even for example 2 of my old Domain controllers! in this case the original VMs have been deleted already vom vcenter and inside the "Exclusions" on the "linked jobs" page, i can only select exclusions (VMs) from the vcenter environment, hence i can't add the Objects to exclude

the Servers fails testing in Surebackup, because of credentials not working etc... even theoretically you coudld have duplicate IP issues, when one of the VMs-IP has been reassigned to a new one etc..
all in all i think something has been overlooked here?
br
Steve

[DaStivi]

i ended up removing the old backups now, as i didn't need them any longer... might not be a solution for everyone.