- Community Home
- >
- Storage
- >
- Entry Storage Systems
- >
- Disk Enclosures
- >
- StorageWorks Virtual Arrays/va7xxx-series
Disk Enclosures
1752681
Members
5157
Online
108789
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
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
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Go to solution
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
02-23-2004 07:58 AM
02-23-2004 07:58 AM
In configuring a new va7110, the concept of "image disks" is vague. The User and Service Guide states that one of the functions of an image disk is:
"The image disks have space reserved for copies, or 'images', of the write
cache and virtualization data structures stored in the controller NVRAM."
What is not clear however, is *how much* space is reserved. Is this similar to a parity stripe where the bulk of the disk's capacity is available for storage, or are the disks fully reserved and unavailable for data?
Thank you,
_Dave_
"The image disks have space reserved for copies, or 'images', of the write
cache and virtualization data structures stored in the controller NVRAM."
What is not clear however, is *how much* space is reserved. Is this similar to a parity stripe where the bulk of the disk's capacity is available for storage, or are the disks fully reserved and unavailable for data?
Thank you,
_Dave_
Solved! Go to Solution.
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-23-2004 08:54 PM
02-23-2004 08:54 PM
Solution
Hello,
Not all image disk is reserved for images.
The NVRAM data, which contains the critical LUN map information, can be written to disk on the VA. Two disks on the VA, called â image disksâ are used for this purpose. The NVRAM data is backed up to the image disks every 4 seconds by default.
Finally, the maps saved off to disk are based on the amount of RAM that exist in your controllers, so it's not necessary for firmware to use all complete disk.
Best regards,
Not all image disk is reserved for images.
The NVRAM data, which contains the critical LUN map information, can be written to disk on the VA. Two disks on the VA, called â image disksâ are used for this purpose. The NVRAM data is backed up to the image disks every 4 seconds by default.
Finally, the maps saved off to disk are based on the amount of RAM that exist in your controllers, so it's not necessary for firmware to use all complete disk.
Best regards,
Keep the faith
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.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP