- Community Home
- >
- Storage
- >
- HPE Nimble Storage
- >
- Array Setup and Networking
- >
- Should I make one large vvol, or split it up?
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
Forums
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
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
тАО05-20-2022 07:32 AM - last edited on тАО05-20-2022 09:54 AM by support_s
тАО05-20-2022 07:32 AM - last edited on тАО05-20-2022 09:54 AM by support_s
Hello,
Is there any reason to make two or more seperate vvols in vCenter? Or is making one large vVol the best bet? We have 50 VMs. I don't see why it would make sense to split it up? Thanks!
Solved! Go to Solution.
- Tags:
- nimble
- virtualization
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-20-2022 08:28 AM
тАО05-20-2022 08:28 AM
Re: Should I make one large vvol, or split it up?
First question: What storage array are you using?
For Nimble Storage (and as I recall for 3PAR), there is a one-to-one relationship between each VMDK, vCenter VVol and the underlying storage array volumes. With Nimble Storage, there are two entities:
- vCenter VVol datastore
- vCenter VVol
As I recall, each vCenter VVol datastore maps to a Nimble Storage folder.
Each VVol in that datastore folder is a Nimble Storage volume.
Each VM will require a minimum of three VMDKs, so a minimum of three VVols. (See above; one-to-one mapping between VMDK and Nimble Storage volume.)
Note: While I am an HPE Employee, all of my comments (whether noted or not), are my own and are not any official representation of the company
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-20-2022 08:37 AM
тАО05-20-2022 08:37 AM
Re: Should I make one large vvol, or split it up?
We are using AF-232396 , Model AF20
I guess I should have asked, is it better to make multiple vvols in datastore manager in vcenter? Is there any benefit?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-20-2022 08:45 AM
тАО05-20-2022 08:45 AM
SolutionA VVol datastore is a Nimble folder. A Nimble folder can optionally have
- performance -- IOPS and MBPS limits
- capacity -- Usage, provisioned and overdraft limits
See the Nimble Command Reference for details on the underlying folder command.
Note: While I am an HPE Employee, all of my comments (whether noted or not), are my own and are not any official representation of the company
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-20-2022 09:51 AM
тАО05-20-2022 09:51 AM
Re: Should I make one large vvol, or split it up?
Gotcha. So it's a personal preference thing. Thanks Sheldon!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-20-2022 12:05 PM
тАО05-20-2022 12:05 PM
Re: Should I make one large vvol, or split it up?
Great question! Glad that you're thinking about this before implementing the solution. And Sheldon pointed out the correct differences to consider.
If space restrictions are not required, one single large vvol datastore per array pool tends to work in most cases. IOPS can actually be specified on a per volume basis as well, applying it as a VM storage policy.