[FEATURE REQUEST] SureBackup VM Exclusion

[adriangalbincea]

Hi,
If I want to exclude a VM from being processed in Linked Jobs, I need to select it from the actual infrastructure, but let's say you have a job which had an old VM replaced by the new one in the same job. If that VM doesn't exist anymore in the production infrastructure, you cannot exclude it. The only way is to remove it from the backup. It will be handy for immutable repositories when we cannot delete the backup for a specific amount of time

[Mildur]

Hi Adrian

Thank you for your request.

The only way is to remove it from the backup.

Another workaround would be to move the entire VM and its backups to a disabled placeholder backup job. Important: the placeholder job should have the same retention policy as the original job.

Best,
Fabian

[TWuser]

I think this feature request goes back about 12 years.

@Fabian - if using a placeholder job, the only concern for retention is that the backups (including GFS) will inherit retention settings from the new job, correct?

I have multiple jobs with multiple retention policies, but am not going to litter my setup with more than 1 fake job. I am ok with having a single decom retention policy that works for all, though it is a serious limitation for those who need separate retention policies.

[Mildur]

@Fabian - if using a placeholder job, the only concern for retention is that the backups (including GFS) will inherit retention settings from the new job, correct?

Correct.

The request is understood, but there is no ETA I can share today. It is not expected soon.

Best,
Fabian