Around the Storage Block Blog
Find out about all things data storage from Around the Storage Block at HP Communities.

HP LeftHand P4000 Peer Motion demo

CartoonCalvin100X100.JPGBy Calvin Zito, @HPStorageGuy  vmw-vexpert.jpg

I had a lot of fun and learned a ton myself over the last few days by getting some hands on time with our HP LeftHand P4000.  Let me briefly recap what I've done so far:

 

  • In my first post titled HP LeftHand Zero to VSA, I showed the new installer for our Virtual SAN Appliance (VSA) that makes installing a VSA very easy - I counted 5 steps. 
  • Part 2 is titled HP LeftHand P4000 Centralized Management Console (CMC) demo and in this video I show the CMC being used to do some basic provisioning tasks with the P4000 VSA's I created in part 1 - tasks like create a management group, a cluster, a volume and then connect the volume to a host.

Today's video is cool!

I really enjoyed doing the hands on I'll show you today.  I used Peer Motion software to do a cluster swap and volume migration.  As I was doing this, I thought it would be awesome to have a video playing on the P4000 volume that was part of the cluster swap or volume migration - so you can see that this happened without impacting the "users" - in this case me.

 

First a little background on Peer Motion

There's a new white paper about Peer Motion that is almost finished - so instead of me trying to be creative in talking about it, here's an excerpt from the paper:

 

Peer Motion is HP’s data migration technology which offers HP LeftHand users two simple and flexible methods of moving data volumes within a LeftHand SAN. Those methods are volume migration and cluster swap.  Volume Migration and Cluster Swap employ storage federated software, to transparently move application workloads between tiers of data storage and/or storage clusters in a LeftHand environment. Peer Motion on HP LeftHand supports all P4000 storage models - spanning from the P4000 Virtual SAN Appliance (VSA) to the midrange and high performance P4000 storage systems.

 

In short, Peer Motion enables dynamic resource leveling of LeftHand storage clusters without storage downtime and/or maintenance window outage.  Resource leveling for LeftHand systems is quick, easy and executed within a few simple steps thus eliminating the need for long term storage planning and complicated budget forecasting.

 

Sometimes it's easy to be skeptical about what a vendor document says - when you see how quick and easy this stuff was on the video, you won't be skeptical.   Check out the video:

 

 

 

That wraps up what I wanted to show you today.  I'm hoping that my R&D guys can get me the resources to do a multi-site SAN and we'll simulate a site level failure in the near future.  That will be fun!  In the mean time, we do weekly live demos of the P4000 that you can join.  Go to www.hp.com/go/P4000Webinar to sign up. As I've told you before, you can get a full featured trial of the P4000 with our 60 trial of the VSA - get it at www.hp.com/go/TryVSA.

Comments
HCM(anon) | ‎05-22-2012 07:40 PM

Can the P4000 VSA be used to create a stretched storage cluster?

I'd like to build a demo of a vSphere Metro Cluster in a lab setting.

| ‎05-23-2012 02:42 AM

HCM - absolutely.  I want to do that in my next hands-on-lab but need my tech marketing guys to help me have my stretched cluster on two IP networks. 

ChrisA(anon) | ‎05-23-2012 11:06 AM

Hi,

 

I'm a little new with the P4000 and I was wondering if you could answer some quick questions.

 

I have 4 x P4300 SAS units to use as VMware datastores. 2 nodes in Primary room and 2 nodes in Secondary network. I also have 2 x P4300 MDL SAS which will be used for back-ups.

 

I was thinking of configuring it as below for seamless failover.

Management Group1 - SAS

Site_Primary (set as primary)

P4300_NODE1

P4300_NODE3

Site_Secondary

P4300_NODE2

P4300_NODE4

Cluster 1 with all 4 nodes and managed with it's in Failover Manager

 

Management Group2 - MDL SAS

Site_Primary (set as primary)

P4300_NODE11

Site_Secondary

P4300_NODE22

Cluster 1 with both nodes and managed with it's in Failover Manager

Michael-C(anon) | ‎05-25-2012 09:14 AM

If a volume is moving between clusters and therefore VIP's how does the client maitain access with no downtime?

 

I would have thought at the very least a rescan would be needed to pick up the volume?

| ‎05-25-2012 04:10 PM

Chris,

You should make sure the Failover Manager VM is not on the SAN - this is a best practice you really need to make sure you implement.

 

Otherwise looks good if you are want the ultimate high availability setup.  For more flexibility, you might consider having both clusters in the same management group.  You could then Peer Motion volumes between clusters and still do Remote Copy between them as well.

| ‎05-25-2012 04:44 PM

Michael - you have to enter the 2nd VIP in the iSCSI Initiator before you move the LUN.  The two Cluster must be within the same Management Group as well. If you do this, you have no downtime while moving LUNs. The iSCSI Protocol can handle this.

Leave a Comment

We encourage you to share your comments on this post. Comments are moderated and will be reviewed
and posted as promptly as possible during regular business hours

To ensure your comment is published, be sure to follow the community guidelines.

Be sure to enter a unique name. You can't reuse a name that's already in use.
Be sure to enter a unique email address. You can't reuse an email address that's already in use.
Type the characters you see in the picture above.Type the words you hear.
Search
About the Author
25+ years experience around HP Storage. The go-to guy for news and views on all things storage..
About the Author(s)
  • 25+ years experience around HP Storage. The go-to guy for news and views on all things storage..
  • This profile is for team blog articles posted. See the Byline of the article to see who specifically wrote the article.


Follow Us