Feature Request: Browse entire repository

[warrenwh]

Hi team,

When browsing say Outlook backups, you have the option of switching on the "include items deleted by user" feature.

1. It would be good if that could be switched on automatically (via a user preference setting). At the moment you have to click on a mailbox first - then flick switch resulting in two refreshes of info.
2. The full function of this button doesn't match its label. It can also show mailboxes that have been deleted BUT are stored in that dated backup job. Is a whole mailbox an item deleted by a user?

But an even better function would be the ability - perhaps via a different switch or a user preference - that when flicked on, would display ALL content stored in the Veeam repository (and show alphabetically).

When a user's account is deleted in M365, it then falls off the backup policy list (if using partial organization) and it stops being backed up as part of the policy job.

But when you need to go browsing/hunting for a particular user's mailbox you need to remember when the last backup job that this user was covered by to see the most up-to-date data replica. You flick the switch to "include items deleted by user" to then find that the mailbox you are looking for doesn't exist as it wasn't included in the last backup job. This is not convenient and can lead to much anxiety and distrust that Veeam actually backed up that data. I note there is a request in this forum already to expose that "last backup" date on a report for a similar reason.

There is currently no way to keep track of when the last backup for a user was done. So, you have to rely on stab-in-the-dark guessing - not fun when you have a 7- or 10-year retention period.

Yes, the browser mailbox list may take longer to load - I'm personally fine with that as it would be quicker for that to load than to individually hunt through various backups.

Searching through backup policy logs isn't workable as these get deleted whenever there is a version upgrade. Mine have gone missing multiple times now.

Please consider.

Regards,
Warren

[tomsinner]

I get where you're coming from, Warren, but honestly I don’t see how a full repo-wide alphabetical browse would work in practice. It goes against how Veeam structures and indexes data per job, and loading everything at once could seriously impact performance, especially in large environments.
Buckshot Roulette