Resolution for MSSQL Backup Error - "BACKUP LOG Is Not Allowed While The Recovery Model Is SIMPLE" in BDRShield

Resolution for MSSQL Backup Error - "BACKUP LOG Is Not Allowed While The Recovery Model Is SIMPLE" in BDRShield

KB ID: 84
Issue:
Encountering the error message: "Msg 4208, Level 16, State 1, Server [servername], Line 1 The statement BACKUP LOG is not allowed while the recovery model is SIMPLE. Use BACKUP DATABASE or change the recovery model using ALTER DATABASE. Msg 3013, Level 16, State 1, Server [servername], Line 1 BACKUP LOG is terminating abnormally" during MSSQL backup.
Cause:
The error occurs when attempting to execute the "BACKUP LOG" command on a database with the recovery model set to "SIMPLE."
Solution:
To avoid the aforementioned issue, follow these recommended backup strategies with MSSQL server plugin in BDRShield clients:
a) Configure a separate backup job for the 'Master' database with 'FULL' backup schedule alone, as 'DIFFERENTIAL and TRANSACTIONAL' log backups cannot be done on the master database. Also, 'master' has to be restored first when restoring SQL Server for disaster recovery.
b) Databases with 'Recovery Model' as 'Simple' should be configured with 'FULL' backup type and optionally with 'DIFFERENTIAL Log' backup types, as 'TRANSACTIONAL' log backups cannot be performed.
c) Databases with 'Recovery Model' as 'Full' or 'Bulk Logged' should be configured with 'FULL' backup type and optionally with 'DIFFERENTIAL' and 'TRANSACTIONAL LOG' backup.
Additionally, it is recommended to implement the following backup schedule:
1. Execute a full database backup on a monthly basis.
2. Perform differential backups on a weekly basis.
3. Perform transaction log backups on a daily basis.
Adjust the frequency based on the size of your database and acceptable data loss for your company. If databases are changing rapidly, consider a combination of options such as differential backups and transaction log backups to minimize data loss.
For clients with rapidly changing databases, setting a maximum number of kept differential backups helps manage backup space usage. Transaction logs, capturing changes since the last backup, are automatically purged during the next Full/Differential backup schedule.
Implementing a well-thought-out backup schedule aligns with best practices and ensures efficient MSSQL Server backup operations with BDRShield.