Error "0xe0008443 - One or more SQL Database consistency checks have failed" appears in the backup job log while backing up Microsoft SQL Server or SQL databases.
Final error: 0xe0008443 - One or more SQL Database consistency checks have failed.
Final error category: Resource Errors
For additional information regarding this error refer to link V-79-57344-33859
The job log also reports the following error:
"An unknown or unexpected database error occurred while attempting a DBCC."
V-79-65323-3224 - An error occurred on a query to database
UMI Code: V-379-57859 : There was a problem running the DBCC
SQL has found some inconsistencies with the database/s mentioned in the job log.
Backup Exec has the ability to check the logical and physical consistency of SQL data before and/or after a backup. SQL reports any consistency check failures in the Backup Exec job log. Veritas recommends running consistency checks either before or after SQL backups.
Backup Exec's backup job definition uses a 'Physical_Only' SQL consistency check before backup by default. Full checks with/without indexes are also options. Additionally, by default a backup job will continue even if the DBCC fails. Confirm this setting in the job definition per Figure 1 below.
The consistency check that is run is actually a part of the SQL program and Backup Exec merely triggers the consistency check. If errors are reported, try running the DBCCs manually through SQL.
How to check the Database consistency in SQL:
1. Open SQL Management Studio and connect to the SQL instance
2. Click on "New Query".
3. Type the following commands and click on "Execute"
Note: DatabaseName is the name of the database that is visible in the Job log of the failed SQL job.
For more information, see the Microsoft SQL Server documentation.
If default settings were used for the SQL backup job properties then run;
dbcc checkdb WITH PHYSICAL_ONLY
The results will show you if SQL has encountered any inconsistencies or not. If inconsistencies are encountered, please contact your SQL Administrator to resolve the inconsistencies. If the independent run of DBCC does not show any errors but when ran with the Backup job it still does, use the error listed in the error.log for SQL to determine root cause and actions.