- Community Home
- >
- Storage
- >
- Midrange and Enterprise Storage
- >
- StoreVirtual Storage
- >
- Re: HP 4000 VSA - thin or thick provisioning the ...
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
тАО08-12-2010 06:12 AM
тАО08-12-2010 06:12 AM
HP 4000 VSA - thin or thick provisioning the VSA disk
I am presuming that if I would have created the VSA's VMDK as a thin disk, I wouldn't get that alert.
My questions are:
1.)Is there a recommended setting?
Should this be thick or thin provisioned?
2.)Is it OK to use VMware converter to thin provision the VSA disk?
3.)Do I need to worry about that alert at all?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-12-2010 08:58 AM
тАО08-12-2010 08:58 AM
Re: HP 4000 VSA - thin or thick provisioning the VSA disk
And the disks need to be set "independent", because snapshots on a VSA that is a member of a management group are not allowed.
For the vCenter alarm... I create an extra folder in the Datastores view and put an alarm on it that triggers when the used capacity is (e.g.) *LESS* than 80 percent. In that case the alarm will go on when one _removes_ the VSA ;-)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-12-2010 09:47 AM
тАО08-12-2010 09:47 AM
Re: HP 4000 VSA - thin or thick provisioning the VSA disk
Does anybody know if there is a VMware or HP/Lefthand document that says as much?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-12-2010 09:59 AM
тАО08-12-2010 09:59 AM
Re: HP 4000 VSA - thin or thick provisioning the VSA disk
"HP StorageWorks P4000 SAN Solution Quick start guide",
AX694-96002 / c02008675
5 Configure the data disk.
-- Virtual device node must be SCSI (1:0)
-- Mode must be Independent > Persistent
6 Reserve at least 2000 MHz CPU and 1024 MB memory.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-12-2010 10:17 AM
тАО08-12-2010 10:17 AM
Re: HP 4000 VSA - thin or thick provisioning the VSA disk
Sorry.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-12-2010 10:21 AM
тАО08-12-2010 10:21 AM
Re: HP 4000 VSA - thin or thick provisioning the VSA disk
But as I already wrote: I don't think it makes sense for a VSA in production.
(OK. I've used it in a test environment where I created a datastore and put 8 THP-enabled VSAs on it to test a bit with Network-RAID-5 and 6...)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-18-2010 08:35 AM
тАО08-18-2010 08:35 AM