Hello,
I am implementing a Volume Shadow Copy Service (VSS)
Hardware Provider for storage box of my company.
The storage box is a DAS RAID device. It exposes
volumes as SCSI disks to the initiator.
I wish to take snapshot of the volumes created on
these SCSI disks using the hardware provider. Please
note that snapshot logic is already implemented by the
storage box.
I have written a simple Provider and registered it
on Windows 2003, which does nothing, but just traces
the function calls. The problem is that when I call
vshadow(i.e. a sample requester available from
Microsoft), on the NTFS volume created on
this SCSI disk, the call never comes to my Provider.
It even does not even call AreLunsSupported().
I even tried calling just my provider from the
requester, but still without the call going to
AreLunsSupported(), I am getting the error -
VSS_E_VOLUME_NOT_SUPPORTED_BY_PROVIDER.
Can anyone tell me, what is that I am missing? Does
the
Windows VSS service not call all the providers, to
inquire? If it does from where does it come to know
whether a disk is supported by provider or not?
Thanks and Regards,
Priya.
Be a better friend, newshound, and
know-it-all with Yahoo! Mobile. Try it now. http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ
You say that you’ve written a simple provider, was this from scratch
or from the sample provider ?
It’s too long ago for me to remember the specifics of writing a
provider, but it looks as if you’re not registering properly or are
still missing something from the framework.
I suggest going back to the Microsoft provider sample provider,
compiling that and see what happens. In case you hadn’t noticed, the
Microsoft sample is in the 6000 Platform SDK under the WinBase samples.
Mark.
At 06:17 26/03/2008, priya sehgal wrote:
Hello,
I am implementing a Volume Shadow Copy Service (VSS)
Hardware Provider for storage box of my company.
The storage box is a DAS RAID device. It exposes
volumes as SCSI disks to the initiator.
I wish to take snapshot of the volumes created on
these SCSI disks using the hardware provider. Please
note that snapshot logic is already implemented by the
storage box.
I have written a simple Provider and registered it
on Windows 2003, which does nothing, but just traces
the function calls. The problem is that when I call
vshadow(i.e. a sample requester available from
Microsoft), on the NTFS volume created on
this SCSI disk, the call never comes to my Provider.
It even does not even call AreLunsSupported().
I even tried calling just my provider from the
requester, but still without the call going to
AreLunsSupported(), I am getting the error -
VSS_E_VOLUME_NOT_SUPPORTED_BY_PROVIDER.
Can anyone tell me, what is that I am missing? Does
the
Windows VSS service not call all the providers, to
inquire? If it does from where does it come to know
whether a disk is supported by provider or not?
Thanks and Regards,
Priya.
Hello Mark,
Thanks for the reply.
Yes, I used the Windows Sample provider, provided by
Microsoft also and just inserted few tracing
functions.
But, I am still facing this problem.
The provider is registered properly. This is because
AreLunsSupported() function of my provider is called
for volumes present on my local disks. It is
only for this SCSI disk that I see nowhere my provider
being called.
Is there some specific SCSI attribute, that we need
to set for this SCSI disk?
I guess that the Windows VSS Service is reading some
attribute from the disks and based on that it decides
whether to call hardware provider or not .
Thanks in advance,
Priya
— “Mark S. Edwards” wrote:
>
> You say that you’ve written a simple provider, was
> this from scratch
> or from the sample provider ?
>
> It’s too long ago for me to remember the specifics
> of writing a
> provider, but it looks as if you’re not registering
> properly or are
> still missing something from the framework.
>
> I suggest going back to the Microsoft provider
> sample provider,
> compiling that and see what happens. In case you
> hadn’t noticed, the
> Microsoft sample is in the 6000 Platform SDK under
> the WinBase samples.
>
> Mark.
>
> At 06:17 26/03/2008, priya sehgal wrote:
> >Hello,
> >I am implementing a Volume Shadow Copy Service
> (VSS)
> >Hardware Provider for storage box of my company.
> >The storage box is a DAS RAID device. It exposes
> >volumes as SCSI disks to the initiator.
> >I wish to take snapshot of the volumes created on
> >these SCSI disks using the hardware provider.
> Please
> >note that snapshot logic is already implemented by
> the
> >storage box.
> >
> >I have written a simple Provider and registered it
> >on Windows 2003, which does nothing, but just
> traces
> >the function calls. The problem is that when I call
> >vshadow(i.e. a sample requester available from
> >Microsoft), on the NTFS volume created on
> >this SCSI disk, the call never comes to my
> Provider.
> >It even does not even call AreLunsSupported().
> >
> >I even tried calling just my provider from the
> >requester, but still without the call going to
> >AreLunsSupported(), I am getting the error -
> >VSS_E_VOLUME_NOT_SUPPORTED_BY_PROVIDER.
> >
> >Can anyone tell me, what is that I am missing? Does
> >the
> >Windows VSS service not call all the providers, to
> >inquire? If it does from where does it come to know
> >whether a disk is supported by provider or not?
> >
> >Thanks and Regards,
> >Priya.
> >
> >
>
>
> —
> NTDEV is sponsored by OSR
>
> For our schedule of WDF, WDM, debugging and other
> seminars visit:
> http://www.osr.com/seminars
>
> To unsubscribe, visit the List Server section of OSR
> Online at
> http://www.osronline.com/page.cfm?name=ListServer
>
____________________________________________________________________________________
Be a better friend, newshound, and
know-it-all with Yahoo! Mobile. Try it now. http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ
Sounds to me like you’re not fully implementing the required SCSI
Inquiry data with Page 83h.
See the logo specs on WHDC for all the info regarding what is
required of SCSI devices and identification data in Page 83h.
Mark.
At 08:26 26/03/2008, priya sehgal wrote:
Hello Mark,
Thanks for the reply.
Yes, I used the Windows Sample provider, provided by
Microsoft also and just inserted few tracing
functions.
But, I am still facing this problem.
The provider is registered properly. This is because
AreLunsSupported() function of my provider is called
for volumes present on my local disks. It is
only for this SCSI disk that I see nowhere my provider
being called.
Is there some specific SCSI attribute, that we need
to set for this SCSI disk?
I guess that the Windows VSS Service is reading some
attribute from the disks and based on that it decides
whether to call hardware provider or not .
Thanks in advance,
Priya
— “Mark S. Edwards” wrote:
>
> >
> > You say that you’ve written a simple provider, was
> > this from scratch
> > or from the sample provider ?
> >
> > It’s too long ago for me to remember the specifics
> > of writing a
> > provider, but it looks as if you’re not registering
> > properly or are
> > still missing something from the framework.
> >
> > I suggest going back to the Microsoft provider
> > sample provider,
> > compiling that and see what happens. In case you
> > hadn’t noticed, the
> > Microsoft sample is in the 6000 Platform SDK under
> > the WinBase samples.
> >
> > Mark.
> >
> > At 06:17 26/03/2008, priya sehgal wrote:
> > >Hello,
> > >I am implementing a Volume Shadow Copy Service
> > (VSS)
> > >Hardware Provider for storage box of my company.
> > >The storage box is a DAS RAID device. It exposes
> > >volumes as SCSI disks to the initiator.
> > >I wish to take snapshot of the volumes created on
> > >these SCSI disks using the hardware provider.
> > Please
> > >note that snapshot logic is already implemented by
> > the
> > >storage box.
> > >
> > >I have written a simple Provider and registered it
> > >on Windows 2003, which does nothing, but just
> > traces
> > >the function calls. The problem is that when I call
> > >vshadow(i.e. a sample requester available from
> > >Microsoft), on the NTFS volume created on
> > >this SCSI disk, the call never comes to my
> > Provider.
> > >It even does not even call AreLunsSupported().
> > >
> > >I even tried calling just my provider from the
> > >requester, but still without the call going to
> > >AreLunsSupported(), I am getting the error -
> > >VSS_E_VOLUME_NOT_SUPPORTED_BY_PROVIDER.
> > >
> > >Can anyone tell me, what is that I am missing? Does
> > >the
> > >Windows VSS service not call all the providers, to
> > >inquire? If it does from where does it come to know
> > >whether a disk is supported by provider or not?
> > >
> > >Thanks and Regards,
> > >Priya.
> > >
> > >
> >
> >
> > —
> > NTDEV is sponsored by OSR
> >
> > For our schedule of WDF, WDM, debugging and other
> > seminars visit:
> > http://www.osr.com/seminars
> >
> > To unsubscribe, visit the List Server section of OSR
> > Online at
> > http://www.osronline.com/page.cfm?name=ListServer
> >
>
>
>
>
> ____________________________________________________________________________________
>Be a better friend, newshound, and
>know-it-all with Yahoo! Mobile. Try it
>now. http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ
>
>—
>NTDEV is sponsored by OSR
>
>For our schedule of WDF, WDM, debugging and other seminars visit:
>http://www.osr.com/seminars
>
>To unsubscribe, visit the List Server section of OSR Online at
>http://www.osronline.com/page.cfm?name=ListServer