- Community Home
- >
- Storage
- >
- Entry Storage Systems
- >
- Disk Enclosures
- >
- Re: Fully Pre-Carving an EVA Array - Good or Bad?
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
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
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- 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
тАО12-12-2006 03:13 AM
тАО12-12-2006 03:13 AM
So is pre-carving an EVA to however many standard sized VDISKS to fully reach accepted full occupancy of the Diskgroups considered Good Practice? What about the notion of just de-presenting a VDISK from a server if it is done being used - instead of totally deleting the VDISK?
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-12-2006 04:41 AM
тАО12-12-2006 04:41 AM
Re: Fully Pre-Carving an EVA Array - Good or Bad?
The disk area of a new Vdisk is implicitly erased by the EVA firmware, but the deletion / recreation / zeroing of a new disk takes up time and I/Os.
Remember not to fill a disk group 100% - if I remember correctly, you should leave at least 10 (or was that 5?) raw GigaBytes free.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-12-2006 04:48 AM
тАО12-12-2006 04:48 AM
Re: Fully Pre-Carving an EVA Array - Good or Bad?
The reason we'd like to do this as a standard for all our existing EVA5K's and possibky new ones is based on experience as well.. It takes a fair amount of time carving VDISKs (as well as removing them). Plus it really slows down the arrays durng Vdisk creation as well as deletion.
It also gives us the advantage of not worrying anymore about reaching the 95% occupancy with a very dynamic system... With VDISKS pre-carved and pre-sized, all we have to do is treat it like our XP simply allocate and de-allocate.. We already have processes anyway that ensure once a disk is no longer used by a Volume Manager on UNIX/NT.. it is zeroed out and a database of sorts updated to show it as a free VDISK...
Plus I think it nicely lays out all your VDISKS within your Diskgroups... for optimum Performance..
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-12-2006 07:19 AM
тАО12-12-2006 07:19 AM
Re: Fully Pre-Carving an EVA Array - Good or Bad?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-12-2006 09:06 AM
тАО12-12-2006 09:06 AM
Re: Fully Pre-Carving an EVA Array - Good or Bad?
Why would it take longer?
Educate me please.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-12-2006 04:42 PM
тАО12-12-2006 04:42 PM
Re: Fully Pre-Carving an EVA Array - Good or Bad?
If a disk is ungrouped, all its data must be moved to the remaining disks in the group. If a new disk is added to a group, data from other disks will be moved to the new disk in order to reach the same filling - that's the leveling.
If the disk group has a higher fill factor, more data needs to be moved from/to disks during leveling.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-13-2006 12:53 AM
тАО12-13-2006 12:53 AM
Re: Fully Pre-Carving an EVA Array - Good or Bad?
So regardless of whether we'll have a fully populated diskgroup - either by way of pre-carving or natural progression of filling up the diskgroup, we'll always have a situation of massive "levelling" - right?
Is there also "levelling" that happens when a VDISK is killed/decommisioned or born?
And say I have 48 Disks in a Diskgroup and I only carve a 2GB VDISK - is the EVA architecture such that the VDISK will have bits of its existence on ALL 48 Drives?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-13-2006 01:02 AM
тАО12-13-2006 01:02 AM
Re: Fully Pre-Carving an EVA Array - Good or Bad?
You can use an EVA with 240 disk drives in one single group. The internal structures allow for a full spread over all disk drives, even for a 1 GigaByte Vdisk.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-13-2006 02:15 AM
тАО12-13-2006 02:15 AM
Re: Fully Pre-Carving an EVA Array - Good or Bad?
Deleting a Vdisk doesn't require re-leveling and is pretty quick. That's because you don't need to move/re-create data from other spindles to those remaining in the disk group when you delete a Vdisk. It's just a matter of updating the metadata to reflect the fact that some space is no longer allocated.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-13-2006 02:45 AM
тАО12-13-2006 02:45 AM
Re: Fully Pre-Carving an EVA Array - Good or Bad?
Why am I asking!
One of the taks that needs lots of CPU ressources in an EVA is deleting VDISKs. The larger the VDISK is and the more blocks that are actually allocated the longer it takes.
This was on of the reasons for introducing the containers concept available starting with VCS4.x (EVA3/5k)and XCS5.x (EVA4/6/8k).
With containers you do not need to delet a VDISK anymore; you can convert a VDISK or a snapclone into a container and reuse it as VDISK or as a target for a snapclone.
I believe it is containers you are looking for (unless you are at VCS3.x)
Cheers
Peter