Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Error....VSS (volume shadow copy service) Hardware provider error

45 views
Skip to first unread message

rajesh

unread,
Aug 29, 2008, 8:56:01 AM8/29/08
to
Hi

I am developing a new VSS Hardware Provider for a iSCSI target.

For the stub implementation i think of simulating the snapshot process,

i think of ->
taking a persistent snapshot (using vshadow) of one of the iscsi target node
which is already exposed to the system( using iscsi initiator)

In the hardware implementation part i exposed another same sized iscsi node
as the resultant snapshot.

i populate the basic VDS_LUN_INFORMATION during gettarget luns (like product
id, vendorid etc as these values are same for all the iscsi nodes)

then during the locateluns process i issue iscsicli command to surface the
particular iscsi node to the system and issue scsi inquiry command to the
drive to populate the remaing vds lun info which was left out during
gettarget luns process.

i populate all that is required during gettargetluns method
but the snapshot process returns error,

#1 The method FillInLunInfo is being called several times over.

#2 After, (several) FillInLunInfo calls, OnLunEmpty is called.
however i checked VDS_LUN_INFORMATION has correct values for the
target LUN though.

I appreciate any help in nailing this down.

Thanks

Geoff

unread,
Oct 7, 2008, 1:52:58 PM10/7/08
to
On Aug 29, 6:56 am, rajesh <raj...@discussions.microsoft.com> wrote:
ic VDS_LUN_INFORMATION during gettarget luns (like product
> id, vendorid etc as these values are same for all the iscsi nodes)
>
> then during the locateluns process i issue iscsicli command to surface the
> particular iscsi node to the system and issue scsi inquiry command to the
> drive to populate the remaing vds lun info which was left out during
> gettarget luns process.

GetTargetLuns must give VSS an shadow copy identifier it can use after
LocateLuns to conclude this lun that just surfaced is indeed the
shadow copy created earlier.
If all you fill out in the VDS_LUN_INFORMATION is generic stuff, VSS
can not recognize the shadow copy when it surfaces during LocateLuns.

nkshi...@gmail.com

unread,
Aug 13, 2013, 2:35:02 AM8/13/13
to
Hi Rajesh,

can you give me any information on how to issue the iscsicli command to make the volume visible on my windows server box? I'm getting a MISSING_DISK error from windows after gettargetluns .. and an event in the event log that says "shadow copy lun failed to appear"

Thanks, hope to hear from you soon,
nikhil.
0 new messages