If a third-party software tool is taking copy-only SQL Server backups, those will not interfere with the backup chain so SQL Backup Master won’t warn about them. Why is it a potential problem if another software tool is also taking SQL Server backups? Note that copy-only database backups are ignored during backup chain validation, as they don’t interfere with the SQL Server backup chain. Such messages can be logged as warnings (default) or errors, depending on backup job settings. If a possible conflict is detected, SQL Backup Master writes an “invalid backup chain detected” message to the log.
Specifically, when a differential or transaction log backup is started, SQL Backup Master analyzes SQL Server’s backup history table and checks to see if the most recent backup was also created by SQL Backup Master. The goal of backup chain validation is to warn users when other third-party applications could potentially interfere with the SQL Server backup chain.
This article describes the goal and function of this feature.
SQL Backup Master 6.3 includes a new feature called backup chain validation that is responsible for generating “invalid backup chain detected” messages.
