Veeam database availability

[tjdoc]

Hi,
When planning where the Veeam database should be located in our environment (our intention is to use MSSQL on a different server to the VBR server), I'd like to know how much this needs to be highly available.
So if the Veeam database is not available for some reason, does this stop Veeam from working altogether? Would backup jobs etc fail?

Mainly thinking should the database be in a SQL always on setup or not.


Thanks for any guidance...

[Andreas Neufert]

It really depends on your needs.

Yes, Jobs will fail when the database is not available as we can not update metadata.
However there is a (very) short database timeout integrated.

Always On would be a very expensive way of protecting the server.
Maybe just protect VBR Server and Database with a second instance of VBR that you hold at another place. Maybe even replicate the server or use near CDP to protect this server and failover with Instant Restore or Replica/CDP failover the system when needed.

[tjdoc]

Hi Andreas, thanks for replying.
Is the best practice then to install the SQL server on the same server as the VBR, rather than a separate SQL instance on another?
(We will also do config db backups to another host)

The main requirement is to make sure Veeam and its database are not offline for any length of time (other than something like an upgrade or patch).

Thanks

[tyler.jurgens]

One of the ways I prefer to scale VBR installations is to split off the SQL Database onto its own server. However, I do so only for scale, not for resiliency. Doing so I can apply some best practices for SQL servers that don't necessarily apply to the VBR server itself.

[tjdoc]

Thanks Tyler
We only have a small environment of about 50 vm's to backup (quite a lot of data though).
I have found some best practice guides (https://bp.veeam.com/vbr/2_Design_Struc ... abase.html) which suggest a local PostGres database would be best.

Any thoughts if this would be sufficient?

[tyler.jurgens]

Yes, for that size of workload a local PostgreSQL instance is sufficient.

[tjdoc]

Thank you for the advice, appreciate it!