After applying Hot fix 38 for Backup Exec 11d or upgrading to Backup Exec 12.x, differential backups fail when using the SQL Agent to backup the Backup Exec Database (BEDB)

Article:TECH59669  |  Created: 2008-01-16  |  Updated: 2013-11-03  |  Article URL http://www.symantec.com/docs/TECH59669
Article Type
Technical Solution

Product(s)

Issue



After applying Hot fix 38 for Backup Exec 11d or upgrading to Backup Exec 12.x, differential backups fail when using the SQL Agent to backup the Backup Exec Database (BEDB)


Error



V-79-57344-33938 - "The Backup Exec SQL Agent was not used to create the last full backup of this database. You must use the SQL Agent to run a full backup before you run a differential backup or transaction log backup. "


Solution



In Backup Exec 11D (post Hot fix 38) and in Backup Exec 12.x, a change has been made to the Backup Exec Agent for Microsoft SQL Server. Backup Exec now runs a reference check against the Microsoft SQL instance, to verify if the last database backup was taken with the Backup Exec SQL Agent. This change helps maintain the integrity of the SQL backups.

Backup Exec provides its own database maintenance by default at 04:00 a.m. daily. (This can be changed in Tools | Options | Database Maintenance) This includes a Full database backup of the BEDB. Since this is a non-SQL agent backup, the next differential backup that uses the SQL agent will fail.

The Backup Exec Database (BEDB and BE_DLO if the Desktop and Laptop Option is installed) do not need to be included in the SQL Agent's database backup selections.

To prevent this error from occurring the BEDB can be removed from the selection list. (See figure 1)

The database dump file of the BEDB can then be selected for backup. The bedb.bak is located by default in C:\Program Files\Symantec\Backup Exec\Data

If using the SQL agent to protect the BEDB is desired, database maintenance will need to be disabled. (not recommended)

Figure 1
 

Symantec Corporation has acknowledged that the above-mentioned issue is present in the current version(s) of the product(s) mentioned at the end of this article. Symantec Corporation is committed to product quality and satisfied customers.

This issue is currently being considered by Symantec Corporation to be addressed in the next major revision of the product.  There are no plans to address this issue by way of a patch or hotfix in the current or previous versions of the software at the present time.  Please note that Symantec Corporation reserves the right to remove any fix from the targeted release if it does not pass quality assurance tests or introduces new risks to overall code stability.  Symantec's plans are subject to change and any action taken by you based on the above information or your reliance upon the above information is made at your own risk.

Please be sure to refer back to this document periodically as any changes to the status of the issue will be reflected here.
Please contact your Symantec Sales representative or the Symantec Sales group for upgrade information including upgrade eligibility to the release containing the resolution for this issue.  For information on how to contact Symantec Sales, please see    http://www.symantec.com


 

Supplemental Materials

SourceETrack
Value1250882
Description

Database maintenance prevents the SQL agent from running Differential backups of the BEDB


SourceUMI
Valuev-79-57344-33938
Description

The Backup Exec SQL Agent was not used to create the last full backup of this database. You must use the SQL Agent to run a full backup before you run a differential backup or transaction log backup



Legacy ID



302941


Article URL http://www.symantec.com/docs/TECH59669


Terms of use for this information are found in Legal Notices