XX is no longer processed by this job make sure this change is intentional

[balcarras]

Hi,

We inadvertently added some VM's to a copy job, these have now been removed however every time the copy job runs it reports about the VM's which we've removed!

How can I stop the messages appearing " XX is no longer processed by this job. Make sure this change is intentional"

Thanks.

[PTide]

Hi,

If you don't need backup copies for the servers that you've accidentally added into Backup Copy, then go to "Backups" - "Disk" node, pick the backups produced by the copy job that throws the warning, locate the backups belonging to the servers that you've removed form the copy job, and choose "Remove from disk".

Thanks!

[balcarras]

Thanks - perfect answer.

[t481]

Hello,
Is it possible to archive the old backups first before deleting from disk i.e archvie to S3 for example?

[veremin]

Only if you're using Scale-Out Backup Repository with Capacity Tier enabled. Thanks!

[danswartz]

I imagine you could restore the guest from the backup copy repository (without powering on), do a VeeamZip, then delete the guest?

[veremin]

Sorry for providing misleading answer, I thought you were talking about ability to automatically move the oldest part of backup chain to object storage first (before deletion), thus, I mentioned Capacity Tier as an option. Unfortunately, Capacity Tier won't help in your case. Thanks!