SQL transaction logs may not be truncated in Backup Exec 22.2

book

Article ID: 100060204

calendar_today

Updated On:

Description

Error Message

The job log includes the following message:

Running a full-copy backup on database 'database name' on SQL Server 'sql server\instance' because the database size has changed since the last full, changing the total number of pages in the databases. This may cause block level incremental or differential backup method to work in unexpected manner. Backup Exec will continue to take full-copy backup of this database until a full backup is run.
 

Cause

SQL log backups unexpectedly switch to a full-copy backup if any of the following situations occur:

a) AOFO (Advanced Open File Option) enabled full backup has not been executed.
b) The size of the database file has increased since the last AOFO-enabled full backup.

 

Resolution

This issue is resolved in Backup Exec 23

A hotfix is now available for this issue. Backup Exec 22.2 Hotfix 917391

Please refer to the following articles for design changes in Backup Exec 22.2:

Block Level-Incremental\Differential backup of SQL database switches to Copy-Full backup

 

Workaround:

Run a full backup with AOFO enabled. (Figure 2)
Once the AOFO-enabled full backup is successfully completed, AOFO can be disabled if it is not required.

Figure 2.

 

 

 

Issue/Introduction

Although the SQL server log backup jobs complete successfully, the transaction logs may not be truncated in Backup Exec 22.2. Backup time and/or size in bytes may also increase. When this issue occurs, the backup sets view shows log backups as 'SQL/Copy' instead of 'SQL/Log'. (Figure 1) Figure 1.

Additional Information

ETrack: 4130612 SW Download: UPD917391