HP StoreOnce Backup System overview
Speaker Steve Johnson Product Manager
Steve’s going to talk about why data protection is so key to HP and why HP moved from a "trailing" position in the market to a front runner.
HP started in data protection 30 years ago, first customer was IBM! We started later than competitors, which can be good because you get a better perspective. HP focused on three attributes:
This is real converged infrastructure; common hardware platform, same engine as Proliant and P2000 MSA arrays. It’s the same Linux kernel for StoreOnce as well as X9000 and LeftHand, and common management tools.
What was behind HP’s big move into this technology? Large amount of data growth. Tape is good, but has its limitations; customers are looking for disk based backup. Like Toyota, HP came in at low end and had success – moved up!
Reasons for success: easy to use, rich functionality, competitive rate. Since, we have scaled up to D2D4100 and D2D4300, but finding more customers want us to deliver a couple high-end solutions with same dedup engine.
Hence the HP StoreOnce B6300.
Speaker: Matt Jacoby Technical Marketing Engineer
What is the HP B6200 StoreOnce Backup System?
First scalable backup appliance for the datacenter.
The backend is all virtually connected, so when you log in it asks what you want for your template; you can deploy 4 different ones. Then the wizard takes care of all config. Then you can create VTL and NAS; you can have different ones on the other node. Constant communication – called the “service set” -- between them managing data. In case one node goes down you can switch over. You can balance utilization, can also have one node as a failover. Its dual connected and redundant.
Learn more about HP StoreOnce at www.hp.com/go/storeonce
Editor's note: these are fair raw notes taken during the session.
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, please follow our community guidelines.
