VSS error, Event ID 6005


D

Dimitri

The VSS 6005 error appears in the event log every time
a scheduled Ntbackup task runs on a Windows Server 2003
Dell PowerEdge 2650 box. The Dell box is attached to
a Dell RAID Array and a Dell tape drive. The scheduled
Ntbackup task is as follows:

ntbackup backup <directory path> /a /v:no
/d "<set description>" /t "<tape name>" /hc:blush:n /m normal /l:s

where <directory path> is on a volume that contains no
database files. The backup appears to succeed, despite
the VSS error.

SQL Server 2000 is installed on this host. Its master
database is located on the same disk as <directory path>
but on a different volume (C:, instead of D:). Other
database data and log files exist on other disks
(in the RAID array). The recovery model for the other
database instances is "full" and the instances get backed up
to tape via SQL server tasks, both for full backups and
for transaction log backups.

As seen from the "vssadmin list writers" outputs appended
at the end of this message, the SQL Server VSS writer is
in a failed state soon after the VSS error occurs. At other
times, every VSS writer appears to be in a stable state.

It may be unrelated, but this error first started appearing
the day the host's BIOS, RAID Controller firmware and
RAID drivers were all updated to the most recent version.
However, an identically configured host with identically
configured tape backup tasks shows no signs of trouble
after the BIOS/firmware/driver update.

Any ideas? Thanks.

Dimitri

=====
Error:
=====
Date: 2/21/2005
Time: 11:46:59 PM
Source: VSS
Type: Error
Event ID: 6005

Description:
Sqllib error: Database %1 is stored on multiple volumes,
only some of which are being shadowed. For more
information, see Help and Support Center
at http://go.microsoft.com/fwlink/events.asp.

Data as Bytes:
0000: 53 51 4c 53 4e 41 50 43 SQLSNAPC
0008: 34 30 35 00 00 00 00 00 405.....
0010: 53 51 4c 53 4e 41 50 43 SQLSNAPC
0018: 32 39 37 00 00 00 00 00 297.....
=====
Note that the format string directive "%1" has not been
replaced with a valid database instance name.


==================================================================
"vssadmin list writers" output, executed on 02/21/2005 at 11:49 PM:
==================================================================
vssadmin 1.1 - Volume Shadow Copy Service administrative command-line
tool
(C) Copyright 2001 Microsoft Corp.

Writer name: 'System Writer'
Writer Id: {e8132975-6f93-4464-a53e-1050253ae220}
Writer Instance Id: {69789b62-7664-4d68-aba6-e008832fee13}
State: [5] Waiting for completion
Last error: No error

Writer name: 'MSDEWriter'
Writer Id: {f8544ac1-0611-4fa5-b04b-f7ee00b03277}
Writer Instance Id: {dfc3f1cb-36a8-4a36-851d-8ea158441bda}
State: [8] Failed
Last error: Retryable error

Writer name: 'WMI Writer'
Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
Writer Instance Id: {38ecac41-1f6c-4616-b0e4-3c329cc6e524}
State: [5] Waiting for completion
Last error: No error

Writer name: 'Event Log Writer'
Writer Id: {eee8c692-67ed-4250-8d86-390603070d00}
Writer Instance Id: {c27396ab-ef73-4e41-96da-c70aafe7ecbd}
State: [5] Waiting for completion
Last error: No error

Writer name: 'COM+ REGDB Writer'
Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}
Writer Instance Id: {1640ab8f-b25a-493c-9968-7951ae76c6f4}
State: [5] Waiting for completion
Last error: No error

Writer name: 'Registry Writer'
Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
Writer Instance Id: {36239cf0-b752-49a0-bd91-f88f2fd602f4}
State: [5] Waiting for completion
Last error: No error
=====


==================================================================
"vssadmin list writers" output, executed on 02/22/2005 at 14:22 PM:
==================================================================
vssadmin 1.1 - Volume Shadow Copy Service administrative command-line
tool
(C) Copyright 2001 Microsoft Corp.

Writer name: 'System Writer'
Writer Id: {e8132975-6f93-4464-a53e-1050253ae220}
Writer Instance Id: {c80bb47f-d604-406b-ad42-f85daebaad76}
State: [1] Stable
Last error: No error

Writer name: 'FRS Writer'
Writer Id: {d76f5a28-3092-4589-ba48-2958fb88ce29}
Writer Instance Id: {30383cc5-ea5d-43c7-8785-71b946f39213}
State: [1] Stable
Last error: No error

Writer name: 'NTDS'
Writer Id: {b2014c9e-8711-4c5c-a5a9-3cf384484757}
Writer Instance Id: {8a77b71a-29ac-4b9f-8c9c-a257be4e3ade}
State: [1] Stable
Last error: No error

Writer name: 'COM+ REGDB Writer'
Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}
Writer Instance Id: {47b191a1-0c12-48bb-8a6f-730d67cd2607}
State: [1] Stable
Last error: No error

Writer name: 'MSDEWriter'
Writer Id: {f8544ac1-0611-4fa5-b04b-f7ee00b03277}
Writer Instance Id: {4aa66c01-0abe-4d93-bc92-d9c483e36d37}
State: [1] Stable
Last error: No error

Writer name: 'Event Log Writer'
Writer Id: {eee8c692-67ed-4250-8d86-390603070d00}
Writer Instance Id: {b469c8b6-f494-4263-81e6-f2653e92a2ed}
State: [1] Stable
Last error: No error

Writer name: 'Registry Writer'
Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
Writer Instance Id: {1d6b2212-5b48-45ba-ac35-1038bca71a3d}
State: [1] Stable
Last error: No error

Writer name: 'BITS Writer'
Writer Id: {4969d978-be47-48b0-b100-f328f07ac1e0}
Writer Instance Id: {02fa97bf-df72-4638-af22-6d02af0e743a}
State: [1] Stable
Last error: No error

Writer name: 'WMI Writer'
Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
Writer Instance Id: {0639ebfd-995f-48a9-919b-8fcfea2ec079}
State: [1] Stable
Last error: No error
=====
 
Ad

Advertisements


Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Similar Threads


Top