Backup Sets containing SQL database backups may expire prematurely.

  • Article ID:100033941
  • Modified Date:
  • Product(s):


Baseline SQL full or prior incremental backups may expire even when it has some unexpired incremental backups dependent on it. This issue may occur when all of the following conditions are met:

1) User databases are backed up in the same backup job with the SQL System databases (Master, Model, MSDB).
2) Both Full and Incremental (Automatic or Differential (block level) or incremental (block level)) backup types are being performed of the SQL instance.
3) The retention period of the full backup or earlier incremental backup has expired
4) A depending incremental or differential backup set has not yet expired.

In this scenario when the Incremental SQL backups are run, the SQL system databases will automatically be switched to 'full' backups in a new backup set since non-full backup types are not possible on system databases. MS Article. This switch to a ‘full’ backup creates a new backup set chain within Backup Exec, breaking the dependencies of all the selected databases in this backup job, including User databases. The previous SQL Incremental backup sets will no longer depend on the prior ‘full’ or prior ‘incremental’ backups. If the ‘full’ or prior ‘incremental’ backup set expires, it may be deleted, as the recovery chain protecting those sets is broken.



When the system databases are automatically switched to a full backup method during an incremental backup job, it removes the dependency on the prior backups from the associated user database backup set.  Since the prior full and incremental backups are no longer part of the dependency chain, they can be deleted if the retention period expires before the depending incremental backups.


A hotfix is now available for this issue in the current version of the product mentioned in this article. Refer to the Hotfix link under Related Articles to obtain the hotfix needed to resolve the issue.

Backup Exec 16 Rev 1142 Feature Pack 2 ( 000116194)


To work around this issue, perform either A) or B)

A)  Edit the backup solution such that the Full backup job has a retention setting greater than that of the incremental job so that the Full does not expire before the Incremental has expired.
B) Back up the SQL databases in a separate job from the user databases.


Related Articles

Backup Exec SQL Service BKUPEXEC instance will not start due to damaged database files.

Backup Exec 16 revision 1142 Feature Pack 2

How to restore a Microsoft SQL Server Master Database with Backup Exec for Windows Servers (Automate Master Database Restore)

Was this content helpful?

Get Support