Some advice is need on our Veeam Backup Azure Storage Options

[gabbas]

We are reviewing our Veeam Backup for Microsoft Azure design to optimise Azure storage costs while maintaining best practices. Currently, our Azure VM backups are stored in GRS storage accounts, with daily backups (31-day retention), monthly backups, yearly backups in a separate GRS repository, and hourly snapshots. We also have a 125TB Veeam Data Vault subscription and use Backup Copy Jobs to maintain an immutable offsite copy of all backups. Given that we already have a secondary immutable copy in Veeam Data Vault, we are questioning whether GRS is still providing sufficient additional value to justify the extra cost compared to LRS.

We are considering creating new LRS-based repositories and directing future backups there while leaving existing backups in the current GRS repositories until they age out naturally. Is this the recommended approach, and would restores continue to work from the existing GRS repositories during the transition? Also, if we retain GRS, can someone explain the practical recovery process during a regional outage (e.g., UK South failure) and how Veeam Backup for Microsoft Azure would access and restore data from the replicated copy in UK West? We would appreciate any guidance on whether this proposed redesign aligns with Veeam best practices and cost-optimisation recommendations. Thanks in advance.

[nielsengelen]

Hi,

There is normally also an option to switch back to LRS from GRS. You can of course create new repositories but you'll have double the storage used for a while.
If you create new repositories but leave the GRS repositories available in VB for Azure, the old backups should be visible and you could perform a restore from them.

If there would be an outage (and maybe your VB for Azure would be out as well), you can setup a new/temporary VB for Azure and import the replicated repositories and since all metadata will be there - you will be able to perform restores.

Does this answer all your questions?