[FEATURE REQUEST] - Expiration Date Information

[CarlosEsteves]

Hello team,

I want to come with a request and if it is already in place, you can explain me how to check.

Is it possible to check the expiration date of a backup vbk or vib or the full chain?

In other backup tools we have the backup date and in another column the expiration date.

Thanks

[HannesK]

Hello,
no, not today... just curious, what do you try to achieve?

Let's say you know this file is needed till 27th March 2026, what do you do with that information?

Best regards
Hannes

[CarlosEsteves]

Try to have clear view based in the retention of the expiration date of a chain.

It is not often, but sometimes people ask for some backup information related to expiration date.

[HannesK]

okay, we discussed it and put it on the list for potential improvements. no timeline for implementation though.

[adamV]

Hi Veeam Team,

I would like to suggest a small improvement for the Orphaned backups view in Veeam Backup & Replication.

When a backup job is deleted, the existing backup data is moved under Orphaned backups. If the original job had day-based retention, the backup may still be deleted automatically according to the original retention policy. However, the UI does not clearly show when this will happen.

My suggestion is to add a new column to the Orphaned backups view, for example:

"Automatic deletion date" or "Retention cleanup date"

The column could show:
- the expected automatic deletion date if day-based retention applies;
- "Retained until manually deleted" if the backup was protected by restore point-based retention and no calendar-based deletion date can be calculated;
- "No automatic deletion date" or a similar status if the backup will remain indefinitely.

Reason:
In real environments, backup jobs are often deleted or recreated during migrations, redesigns, infrastructure changes, or troubleshooting. In addition, some backups are kept for archive or long-term retention purposes. In these cases, the backup job itself may no longer exist as an active job, while the backup data remains available on disk or object storage.

From an operational point of view, it is important to know whether an orphaned backup will be cleaned up automatically, and if yes, when. It is also important to clearly identify backups that are intended to remain as archive data and require manual lifecycle management.

Without this information, administrators have to manually investigate retention settings or repository usage, which increases the risk of unexpected storage consumption, accidental cleanup of archived data, or uncertainty about which backups are still retained intentionally.

Expected benefit:
This feature would make orphaned backup lifecycle management clearer and safer. It would help administrators understand which orphaned backups will be cleaned up automatically, which ones require manual action, and which ones are intentionally kept as archive data.

Thank you.

[HannesK]

Hello,
and welcome to the forums.

I merged your request to a similar request. Would the above solve your demand?

Best regards
Hannes

[iDeNt_5]

+1

[CarlosEsteves]

That is also a good request, but my request was to have it for all the backup data we have