However, I was a bit shocked to find out, that default is to use a Windows-based Postgres database with no granular options to backing up or restoring this database. A bit ironic for a backup application.
As I see it, the only options are the Configuration Backup (maybe?), where the shortest interval is daily, or snapshot backup of the virtual machine.
And I don't even want to think about how to restore this in a disaster situation.
This may have been fine, when the local database only contained Veeam data, which was mostly static and could be recreated from the configuration backup.
But now it also contains actual production data, which needs to be protected at the same level as VMs, files and databases?
How do I perform continuous WAL backup? Where is the 3-2-1-1-0 rule? How do I validate this backup?
According to Veeam support, such features are currently not supported and I need to create my own backup process using pg_dump. I bit ironic for a backup application
With focus shifting towards Postgres, but claims to still support VBR on Windows for the foreseeable future, I think it is critical to mitigate this.
Either through better backup functionality in VBR, support for Postgres backup on Windows or possibly an external unmanaged database as an 'appliance', which could be backed up by Veeam.
As is, I am hesitant to commit resources to rolling out backup of Entra, if such basic functionality is lacking.