Log truncation if using both SQL native backup and DocAve backup functionality

Details:

Use Case

Users may want to use SQL’s native functionality to perform full backups, but may be concerned that the log files will grow too rapidly. How would DocAve backup jobs be affected and when will the log truncation be triggered?

Resolution

As SQL backup and DocAve Platform Backup are both relying on log sequence numbering (LSN), Platform Backup will be affected because LSN is being used by both backup methods. That is to say, even though the SQL backups are full backups only, they will also have impact on the LSN, which will then affect DocAve Platform Backup.

Regarding truncation of the logs, please note that it is a SQL feature that the logs will be truncated automatically after the logs have been backed up. DocAve Platform Backup with Perform log backup after full backup selected will trigger logs truncation and Incremental Backup will also trigger the truncation. However, there may be some delay of the log truncation, which is determined by the internal mechanism of SQL. ​