Warning on SQL backup

[zoltank]

I have application aware image processing turned on and am backing up a SQL server which has two databases on it, one with circular logging turned on and one without. Veeam is set to truncate SQL logs. However, because it can't truncate the logs for the DB with circular logging, it gives me a warning.

Is there anyway to suppress that warning message?

[foggy]

You can exclude this database from VSS processing.

[zoltank]

I'd still like the DB to be VSS processed. I just don't want the warning when Veeam can't truncate the logs.

[foggy]

What is the recovery model of the second database? In case it is Simple (actually, no sense in having it Full unless you backup logs for point-in-time recovery), you can set the job to not truncate logs or perform copy-only backup to avoid warnings.

[zoltank]

The second DB is simple.

So far as I know, log truncation is a per VM setting and the DB with logging enable (full recovery mode) requires its logs to be truncated.

[foggy]

Right, log truncation is only needed for databases in Full recovery mode, in Simple mode SQL manages the logs automatically.

[zoltank]

There are two DBs on the SQL server I'm backing up. One is simple recovery and the other is full recovery. Therefore Veeam's log truncation is required, but it then throws the warning because of the DB set to simple recovery.

[foggy]

Ah, got it. But what is the reason of having Full recovery for the other one? Seems you are not backing up logs...

[zoltank]

Veeam is backing up the logs when it backs up the VM.

[foggy]

Ah, so it does backup logs. OP says "Veeam is set to truncate SQL logs", that's why I thought there's no reason in Full recovery model.

As far as I know, there should be a registry value to exclude databases from logs backup as well. Please contact support for details.

[zoltank]

Veeam does truncate the logs, but after the backup.

[foggy]

Right, backup includes subsequent truncation, but still it was not initially clear from the post which option was selected in the job. Nevermind, please let us know whether you manage to address this with the help of support. Thanks.