Summary
The Snapshot preparation fails on a SQL Server that has a "Suspect" Databases present.
Symptoms
The job log reports:
10.0.10.130 sssnap Tue Oct 25 13:54:40 2005 SNBSNP3069E 2052: Writer [MSDEWriter] failed to report the status as success state[8 (FAILED_AT_PREPARE_SNAPSHOT)] status[0x800423f4] (VSS_E_WRITERERROR_NONRETRYABLE)]
10.0.10.130 sssnap Tue Oct 25 13:54:40 2005 SNBSNP3069E 2052: MsSnapShot::check_wrts_report_okay::check_wrt_status rc[-1]
10.0.10.130 sssnap Tue Oct 25 13:54:40 2005 SNBSNP3069E 2052: Failed to check the status of all writers after snapshot rc [-1]
10.0.10.130 sssnap Tue Oct 25 13:54:40 2005 SNBSNP3069E 2052: SnapHandler::backup_apps:backup_components failed rc(-10)
10.0.10.130 sssnap Tue Oct 25 13:54:40 2005 SNBSNP3069E 2052: SnapCMInterface::backup_apps:backup_apps( RC(-16)
10.0.10.130 aph Tue Oct 25 13:54:40 2005 SNBAPH_381E BexException in message (BACKUP_VSS) to module (sssnap), reqrc (-16)
10.0.10.130 aph Tue Oct 25 13:54:40 2005 SNBAPH_126E Func(backup_): Exception (AHException: <AHExceptionxception instance at 6123694> )
10.0.10.155 sssvh Tue Oct 25 13:54:40 2005 SNBSVH_990E APPH backup request failed with exception: <EXCEPTION CATEGORY="BEXEXCEPTION"><CODE>21001</CODE></EXCEPTION>
Also the System Event viewer logs shows:
Event Type: Error
Event Source: VSS
Event Category: None
Event ID: 6013
Date: 10/25/2005
Time: 3:49:53 PM User: N/A
Computer: TSSCBLADE1
Description: The description for Event ID ( 6013 ) in Source ( VSS ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: ICommandText::Execute, 0x80040e14, SQLSTATE: 42000, Native Error: 3013
Error state: 1, Severity: 16
Source: Microsoft OLE DB Provider for SQL Server
Error message: BACKUP DATABASE is terminating abnormally. SQLSTATE: 42000, Native Error: 3202 Error state: 1, Severity: 16 Source: Microsoft OLE DB Provider for SQL Server Error message: Write on '{7E69C854-03E3-4154-98A4-15D6670DC309}6' failed, status = 995. See the SQL Server error log for more details.
Resolution
1) Use the Microsoft SQL Enterprise Manager to check the SQL database to see if any of the databases are showing a Suspect status.
This flag means that the database integrity is suspect for the referenced database. This needs to be corrected prior to running a DPX block level backup.
2) Using the Microsoft SQL Query Analyzer execute the sp_resetstatus to reset the status of a database in Suspect status. For more information on sp_resetstatus see the Resetting the Suspect Status in the SQL Server Books Online.
Execute sp_resetstatus in the master database:
Note: In the example above replace msdb with the database in the Suspect status.
You will see the following output:
3) Stop and restart Microsoft SQL Server.
4) Verify with Microsoft SQL Enterprise Manager that the database status is Normal.