Have jobs configured basically as "host" (items job contains is only vcenter host, which means anything there gets backed up). Someone creates a "test" vm and "accidentally" leaves it associated with the ESX host and it gets backed up. 20 days later I still see restore points for that VM - tried setting retention to 1 and it didn't disappear. Other than completely delete the job.. or even the backup files, triggering a full backup again, is there any other way to age out vm backups for vm's that no longer exist?
Second question (which is another source of frustration when folks like moving VM's around):
is it possible to have many unique jobs all pointing at the same dedupe store (vrb file on cifs)? Also noticed that when doing data-center item backups and a host moves and falls under a different job, that the whole thing is taken again; also leaving the old backup to hang out on the old store, until I redo the backup job completely.
Best practice to have backups targetted to VM, ESX Host, Data Center, or vcenter? I don't want to reconfig jobs every time someone decides to do a vmotion
if I need to clarify anything, let me know, or if this is best suited as a support case - we have that too
Im open to selecting individual VM's in backup jobs.. but that still doesn't solve the host vmotion thing unless I can have multi-job per dedupe store right?
TIA!