Old VM's still in backup files

[jzemaitis]

This seems to be by design, but I'm just wondering if I'm taking the right approach.

Here's my scenario:
My backup jobs are specified per Lun, so all the VM's on one Lun are associated to one backup policy. I'm trying to avoid too much disk activity per Lun. I have a 10 backup retention. When I do a SVMotion to another Lun I update my Veeam jobs to reflect the changes. When I check my backup contents, weeks or months later the old VM is still listed in there, taking up space. The only way I've been able to clean them out is to recreate the entire backup file, starting fresh. I generally rename the old backup folder and let a new one recreate. After several days or a week I'll delete the old folder to save space. This seems to be happening a bit more lately and this cleanup effort is pretty annoying. I don't see any way to clean out old VM's from these backup files. Does anyone have a suggestion?

[Vitaliy S.]

Hello Joe, please review the existing thread for the answer: removing vm backups and backup resiliency. Thank you!

[jzemaitis]

Thanks for the info. Looks like I need to wait for the next release, which is only about 10 days way! That's a great feature to add.

Thanks

[Gostev]

Joe, 10 days away is our new technology announcement, the release is actually scheduled for early Q3.

[jzemaitis]

Owwwwwwwww.... Back to the old method for a while I guess.

Thanks for the info.

[rowdy]

Joe, 10 days away is our new technology announcement, the release is actually scheduled for early Q3.

Beta, anyone?

[Gostev]

Lucky guys with

sign for sure

[TrevorBell]

[rowdy]

Well, or not so lucky if they get corrupt backups in the beta or are unable to restore

[Gostev]

...unless of course you use it in parallel with existing version, or on a few test VMs only

[rowdy]

You always have an answer for everything