Feature Request: Unable to remove conflicting instance objects in Veeam Copy jobs

[chris.williams]

I've currently have a case opened with VEEAM Support (case# 07724249) where I am continuing to receive Backup Copy Job Warnings due to AWS instances that have been deleted and restored. Based on feedback from support there is no option in the Veeam Backup UI to find old instance related in the "Backups" section.

Moving Instances from one subnet to another in AWS require deleing the Instance and then restoring it to a new subnet. Since we use Veeam
for AWS it makes sense to utilize it to accomplish this, however not having the ability to clean up the old instance currently causes unnecessary alerts and errors.

Please consider adding an option in the new version to allow removing old instances from jobs to avoid unnecessary alerts and errors.

Thanks!

Chris

[nielsengelen]

Hi Chris,

Are you protecting your resources by adding them specifically or using tags as a source?

[chris.williams]

I'm adding instances specifically to the Veeam jobs.

[nielsengelen]

When you perform a restore, they will receive a new ID so this behavior does sound logic.

Normally, if you use a tag as source, we can rescan the tag on every policy run and ensure we pick up the restored instance. And then retention should apply on any invalid backups.