Can the SQL server that has the Veeam dB on it be backed up in Veeam?

[BassFisherdba]

Can the SQL server that has the Veeam database on it get backed up using the Veeam application? I was told that you shouldn't do it.

If the server can't get backed up, how can files get restored if they are needed? Could a backup be done of just the server and not the dB? At least this way some files could get backed up.

Thanks

[d.artzen]

Why would you want/need to do that? The correct way to backup the Veeam Database is to configure a configuration backup in the VBR console to one of your repos (best not the Veeam Server itself, so you don't lose it if the server is lost). In case of a failure of the Veeam Server you just install a new one and import the configuration backup.

[Mildur]

Hi Mark

As noted by Daniel, the configuration database should be protected by a configuration backup job. Restoring from an encrypted configuration database backup will make sure that you can restore credentials as well. Credentials must be provided again if you restore the configuration from an SQL backup to a new backup server.

But it won't cause any issues if you create a application aware backup of the SQL database of your backup server.
May I ask, are you using a shared server for the configuration database and other production workloads, such as a fileserver? This is not recommended because of security considerations. Someone attacking your file server with admin permissions could also use MSSQL queries to manipulate your Veeam configuration database and disable security related settings of your backup server.
Always protect your backup and configuration database server from any non-authorized access. Use dedicated server (non-production) for your backup environment.

Best,
Fabian

[BassFisherdba]

The Veeam SQL Server is locked down to only the database administrators. The server is only used for Veeam, no other application is installed, not even SSMS.

An easy explanation why you would want to have the "Veeam SQL Server" not the dB. Correct that the configuration dB rebuilds the dB.

If you would ever have a security incident and need to look at SQL logs from 2 to 3 months ago, you would not be able to do it because there isn't a backup of the SQL server. Rebuilding the dB isn't going to help get files back from a few months ago.

So far, if I understand what is being said - the Veeam SQL Server (not the dB or configuration backup), it's not recommended that the Veeam SQL Server itself should not get backed up using a Veeam scheduled job. I've talked to a few support people and got the same thing.

[BassFisherdba]

We just got off a call with Veeam support and you can have your Veeam SQL server as a scheduled job in the application. That being said there are specifics it will\wont do.

A Veeam backup with backup dBs on your server, except the Veeam dB, those will be skipped.
A backup of the server will happen just fine.
If the application is also installed on the SQL server (not the best thing) you cannot have a veeam backup job.

Figured this one out, thanks to Veeam support.