Warning Message - periodically SQL Logfile Backup

[WinstonWolf]

Hello ,
We become the following Warning Message while backing up an SQL Database Logfile via Application Aware Processing : Failed to perform internal backup (baramundi): At least one full database backup must be performed before transaction log backup can be enabled This Database is set to Recovery Mode "Full" in Windows SQL Server.
Yesterday we make an Full Veeam Backup Job of the SQL Server which hosted this Database and after this the warning is gone, because we make an Full Backup of this Database with Veeam.
But after the next reverse incremental Backup in night the Warning Message appears again. I become also an Error Message in the SQL Database Logfile Backup which says : Transaction logs from some databases were not backed up for the last 21 intervals.


How can we solve this Problem ?

[foggy]

Please contact technical support to investigate this, as it is advised to do with any technical issue you're seeing.

[kte]

is you're rentention of the log backups high enough , more the the time to take a veeam image bckuos every day and so a full SQL backup

[Vitaliy S.]

Do you do any backups of the logs via native tools by any chance?

[kcv]

Any news about this?
We´re getting the same error with our baramundi database.

[Vitaliy S.]

Can you please tell us if you back up this DB natively or just with Veeam? Also, how your backup job is configured in terms of transaction logs backup?

[kcv]

We create the backup only via Veeam.

Retention: 1 days

advanced settings:
reverse incremental

enable application-aware processing
- require successful processing
- process transaction logs with the job
- backup logs every 15min

schedule:
daily at 20:00 everyday

[Vitaliy S.]

Did it start happening only recently or after enabling the transaction logs option? Did you try running full backup as it is stated in the message?

[kcv]

A full backup is created every day at 8 p.m.

[foggy]

I'd recommend contacting support for a closer look then.

[kojoman]

Just for information if someone else runs into this issue:
There is a maintenance plan "Clean up database" inside the baramundi application which changes the recovery model of the database to SIMPLE. Run some maintenance tasks like Shrink database files and index maintenance. At the end the recovery model is configured back to FULL.
Therefore the backup chain gets resetted and transaction log backup isnt working because of a missing full backup.

Workaround is to change the maintenance task inside the baramundi application.