Problem is we just purchased the Snapshot license to get the hardware VSS
provider working with DPM 2010.
Probably a long shot, but have you had any more progress with this?
"Aaron at Wheelersautobody" wrote:
> No, supposedly a more advanced tech should be on the case but our account rep
> just changed and I felt like it was really low priority despite our support
> agreement. So we're in limbo.
>
> Are you running 2008 R2 as well or 2008? And DPM 2010 or 2007?
>
> "Chris Smout" wrote:
>
> > Did you get this issue resolved? We are trying to do exactly the same thing
> > with our MD3000i and the VSS hardware snapshot provider and are experiencing
> > similar issues.
> >
> > Chris
> >
> > "Aaron at Wheelersautobody" wrote:
> >
> > > I've been testing DPM2010 within a VM on Hyper-V 2008R2 and today implemented
> > > our SAN (Dell MD3000i) hardware VDS/VSS provider on the host (also 2008R2).
> > > The snapshot appears to fail on the host, timing out and registering the
> > > following messages in the event log:
> > >
> > > Error 2/25/2010 3:29:40 PM Disk 15 None
> > > The device, \Device\Harddisk5\DR8, is not ready for access yet.
> > > Error 2/25/2010 3:29:19 PM Application Error 1000 (100)
> > > Faulting application name: vssvc.exe, version: 6.1.7600.20532, time
> > > stamp: 0x4ab83bec
> > > Faulting module name: vssvc.exe, version: 6.1.7600.20532, time stamp:
> > > 0x4ab83bec
> > > Exception code: 0xc0000005
> > > Fault offset: 0x00000000000c2bfe
> > > Faulting process id: 0x1e80
> > > Faulting application start time: 0x01cab66163b0565f
> > > Faulting application path: C:\Windows\system32\vssvc.exe
> > > Faulting module path: C:\Windows\system32\vssvc.exe
> > > Report Id: d4a86b21-2254-11df-a14c-00219b9913d6
> > > Error 2/25/2010 3:29:17 PM VSS 12293 None
> > > Volume Shadow Copy Service error: Error calling a routine on a Shadow Copy
> > > Provider {24e4e8a3-69cb-4370-8b7b-c5276cd49765}. Routine details
> > > PreFinalCommitSnapshots({f9bc3048-899f-41b5-a3ef-8af388d9d613}, 1) [hr =
> > > 0x80042302, A Volume Shadow Copy Service component encountered an unexpected
> > > error.
> > > Check the Application event log for more information.
> > > ].
> > >
> > > Operation:
> > > Executing Asynchronous Operation
> > >
> > > Context:
> > > Current State: DoSnapshotSet
> > > Error 2/25/2010 3:29:17 PM VSS 8193 None
> > > Volume Shadow Copy Service error: Unexpected error calling routine
> > > DeviceIoControl(IOCTL_VOLUME_SET_GPT_ATTRIBUTES). hr = 0x80070002, The
> > > system cannot find the file specified.
> > > .
> > >
> > > Operation:
> > > Processing PreFinalCommitSnapshots
> > > Executing Asynchronous Operation
> > >
> > > Context:
> > > Provider Name: SmVssProvider
> > > Provider Version: 10.60.01
> > > Provider ID: {24e4e8a3-69cb-4370-8b7b-c5276cd49765}
> > > Current State: DoSnapshotSet
> > > Error 2/25/2010 3:21:47 PM Virtual Disk Service 9 None
> > > Unexpected provider failure. Restarting the service may fix the problem.
> > > Error code: 80004005@02000014
> > >
> > >
> > >
> > > Additionally I see some iSCSI warnings in the event log. Is this an issue
> > > with DPM, 2008 R2, Hyper-V, the VDS/VSS provider? I'm unsure. I have an
> > > active support ticket with Dell but was unable to determine the cause at
> > > least immediately.
Kevin
Since last posting, I also tried Backup Exec from Symantec which fails with
the exact same problem, but Dell still thinks it's the software. Both
Microsoft and Symantec's software is buggy, while theirs is "working as
designed". Go figure...
I'd suggest opening a support ticket with them. If enough people report the
problem maybe they start doing something about it.