Storage Boards Cleanup
To make it easier to find information about HPE Storage products and solutions, we are doing spring cleaning. This includes consolidation of some older boards, and a simpler structure that more accurately reflects how people use HPE Storage.
Disk Arrays
cancel
Showing results for 
Search instead for 
Did you mean: 

VSS Problem with MSA 2212fc and Windows 2008

bouli
Occasional Contributor

VSS Problem with MSA 2212fc and Windows 2008

When i do a VSS full Backup with "Windows Server Backup", the Backup fails with this error: "The operation to read from volume shadow copy on source failed. Detailed Error: Incorrect function"

W2k8 Ent. x64 with VDS/VSS Pack (msa2000-fc-vds-vss-2.4.0.20-x64) installed and MSA 2212fc DC Enh. Model.

Log on MSA shows snapshot is created and deleted:

05-06 10:12:59 108 A629 Volume deleted (volume: VSS090506091250855, SN: 00c0ffd7450a0000a262014a01000000)
05-06 10:12:53 205 A628 Map volume: VSS090506091250855, SN: 00c0ffd7450a0000a262014a01000000 channelBitMap=ffh access=Read/Write LUN=1
05-06 10:12:52 205 A627 Map volume: VSS090506091250855, SN: 00c0ffd7450a0000a262014a01000000 channelBitMap=ffh access=Read/Write LUN=1
05-06 10:12:50 258 A626 Snapshot 737473716c5f74657374000000000000 has been committed for master volume 00c0ffd7450a0000032a004a01000000 [DMS tag: f8725ceb4a0162a2]. Snapshot is now ready for use.
05-06 10:12:50 215 A625 Committed 1 snapshot(s), type 258. [DMS tag: f8725ceb4a0162a2].
05-06 10:12:50 256 A624 Snapshot 737473716c5f74657374000000000000 created for master volume 00c0ffd7450a0000032a004a01000000 but it has not been committed yet. [DMS tag: f8725ceb4a0162a2]. A commit is required before the snapshot can be used.
05-06 10:12:50 214 A623 Created 1 snapshot(s), type 256. [DMS tag: f8725ceb4a0162a2].


EventLog:

Log Name: Application
Source: Microsoft-Windows-Backup
Date: 06.05.2009 11:12:59
Event ID: 517
Task Category: None
Level: Error
Keywords:
User: SYSTEM
Computer: STSQL.int.abrantix.com
Description:
Backup started at '06.05.2009 09:12:47' failed with following error code '2155348041' (None of the source volumes were backed up.). Please rerun backup once issue is resolved.

3 time this error:

Log Name: System
Source: disk
Date: 06.05.2009 11:13:20
Event ID: 15
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: STSQL.int.abrantix.com
Description:
The device, \Device\Harddisk3\DR6, is not ready for access yet.


and about 30 Wanings like this one:

Log Name: Application
Source: VSS
Date: 06.05.2009 11:12:59
Event ID: 12333
Task Category: None
Level: Warning
Keywords: Classic
User: N/A
Computer: STSQL.int.abrantix.com
Description:
Volume Shadow Copy Warning: The provider has reported a storage identifier that is not supported by VSS. Codeset: 1 Type: 5 Size: 4 NextOffset: 24 Association: 1 This identifier will be skipped by VSS.

Operation:
Notifying hardware provider to free a drive
Deleting Volume
Delete Shadow Copies
Delete Shadow Copies

Context:
Volume Name: \\?\mpio#disk&ven_hp&prod_msa2212fc&rev_j200#1&7f6ac24&0&3630434646303044373435414132363231344131303030#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}
Volume Name: \\?\Volume{8c910f8b-3974-11de-98b7-00237da1d4b2}
Snapshot ID: {92ee2bc7-7ceb-444e-86e1-7b7dbd60883f}
Execution Context: Provider
Provider Name: HP StorageWorks MSA2000 Family VSS Provider
Provider Version: 2.4.0.20
Provider ID: {bd04cbf9-212c-4553-9ea5-c5bfb05ccc8f}
Snapshot Context: -1
Execution Context: Coordinator


Does anyone have additional insight on this?