HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Legacy
- >
- Windows Server 2003
- >
- Re: writing a VSS Hardware provider
Windows Server 2003
1827147
Members
3075
Online
109716
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-01-2009 01:55 AM
09-01-2009 01:55 AM
writing a VSS Hardware provider
Hi All,
I am trying to write a hardware provider with the help of sample hardware provider given in VSS SDK. After a call to "FillInLunInfo" API, the VSS debug information shows a call to "CVssHardwareProviderWrapper::IsMatchLun". I can't find from where this call is being done in the provider. Also, I could not find this interface in the SDK.
I am getting an error in this interface itself as "Luns mis-match".
How can I solve this problem ? Please can anyone guide me on this ?
-Thanks
I am trying to write a hardware provider with the help of sample hardware provider given in VSS SDK. After a call to "FillInLunInfo" API, the VSS debug information shows a call to "CVssHardwareProviderWrapper::IsMatchLun". I can't find from where this call is being done in the provider. Also, I could not find this interface in the SDK.
I am getting an error in this interface itself as "Luns mis-match".
How can I solve this problem ? Please can anyone guide me on this ?
-Thanks
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-09-2009 11:47 PM
09-09-2009 11:47 PM
Re: writing a VSS Hardware provider
Hi,
writing a VSS hardware provider is something I would think is deeply into developer territory.
Usually developers working for some hardware manufacturer will need some sort of developer relationship/support with Microsoft. It is also assumed the developer has full know-how about the hardware (timing, firmware, functions/limitations etc) - otherwise a similar developer relationship/support is needed with the hardware manufacturer.
HP already publishes VSS hardware providers for their storage systems. And from Microsoft info: http://msdn.microsoft.com/en-us/library/aa381442(VS.85).aspx
"The capabilities of a hardware provider depend on the capabilities of the underlying hardware. Consequently, the degree to which each manufacturer implements the API can vary. For example, manufacturers can include additional methods to optimize configurations, monitor and dynamically tune performance, automate fault management, or provide other beneficial functionality."
So, naturally the "additional methods" that a hardware manufacturer includes may address funtionality of the storage subsystem that Microsoft did not envision or does not need to care about at the OS level.
Cheers,
Rune
writing a VSS hardware provider is something I would think is deeply into developer territory.
Usually developers working for some hardware manufacturer will need some sort of developer relationship/support with Microsoft. It is also assumed the developer has full know-how about the hardware (timing, firmware, functions/limitations etc) - otherwise a similar developer relationship/support is needed with the hardware manufacturer.
HP already publishes VSS hardware providers for their storage systems. And from Microsoft info: http://msdn.microsoft.com/en-us/library/aa381442(VS.85).aspx
"The capabilities of a hardware provider depend on the capabilities of the underlying hardware. Consequently, the degree to which each manufacturer implements the API can vary. For example, manufacturers can include additional methods to optimize configurations, monitor and dynamically tune performance, automate fault management, or provide other beneficial functionality."
So, naturally the "additional methods" that a hardware manufacturer includes may address funtionality of the storage subsystem that Microsoft did not envision or does not need to care about at the OS level.
Cheers,
Rune
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
Company
Support
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP