The SAN I’m installing in the lab at work is a HP P4000 (Lefthand) virtual SAN appliance (VSA). While the majority of the online conversation for the VSA centres on VMware, there is a supported Hyper-V VSA, and obviously that’s the one I want to use.
I set up the storage server, a HP DL370 G6 with lots of disk, and got W2008 R2 SP1 Hyper-V up and running. I didn’t go Windows 8 beta because I only want to run RTM software for the underlying bits of the lab that don’t get wiped/etc – more on that once the lab environment is built.
Then I ran the setup.exe for the VSA and that’s where I wasted many hours because it kept failing with this error:
While ‘Unmounting the configuration drive…’
A search found one result and the suggestions in that forum post were about as helpful as standing on one foot, bouncing counter-clockwise, touching the tip of my nose, and signing the national anthem backwards.
I decided to dig a little deeper and found that HVSA_Original.VHD was a compressed file. Hmm … interesting! I then did the following:
- Uncompressed the HVSA_Original.VHD file and moved it to the folder where I’d create my VSA VM
- Created a new VM for the VSA in Hyper-V Manager
- Attached HVSA_Original.VHD to the new VSA VM
- Attached another new fixed VHD to the VM’s SCSI controller
- Powered up the VM … it appears to be based on CentOS
- “Logged into” the VM and ran the setup wizard to set the hostname and IPv4 configuration
- Set up the CMC to remotely configure and manage the VSA
- Configured a P4000 cluster and provisioned a LUN
- Bob’s your uncle! I think I’ve never managed a P4000 before. EVA was much easier but P4000 has more potential, hence the complexity I suppose.
This blog post is the property of Aidan Finn (@joe_elway / http://www.aidanfinn.com) and may not be reused in any manner without prior consent of Aidan Finn. You may quote one paragraph from this blog post if you link to the original blog post.