By Calvin Zito, aka @HPStorageGuy
Today we announced the new HP StorageWorks X1000 G2 and X3000 G2 Network Storage Systems. (
Fair warning: we're announcing these products a couple of days prior to updating the web page and data sheets - they should be available by November 15 The pages are now live). I believe we are the first vendor to ship a unified storage product (file-based NAS and block-based iSCSI) product based on Microsoft Storage Server 2008 R2. Take an industry leading ProLiant server, mix in a little Storage Server 2008 R2, add a bit of HP Automated Storage Manager, and throw in HP Insight Control for Microsoft Systems Center and HP Integrated Lights-Out (iLO) management to simplify things even more and you see a living example of how HP Converged Infrastructure comes together in a storage product. It's a beautiful thing!
In today's post I have a video with the X1000/X3000 product manager Jim Hankins. You may remember that we did some updates to this same family earlier this year and I did a podcast with Jim talking about what was new. The video today is the first of two - this one takes a look at all of the products in the family, explaining the difference between the X1000 and X3000 and talking a bit about the hardware. As you'll see, a couple of the products have been updated to take advantage of the latest ProLiant DL380 G7 servers. Here's my vlog:
In my next article, I'll include another video with Jim, this time giving a demo of the user interface and talking about what's new in Microsoft Storage Server 2008 R2 that the X1000 and X3000 take advantage of. There are a couple of very cool features so be sure to check back tomorrow.
One other logistic note: I now have a playlist on our Hewlett Packard YouTube channel. This is where I'm posting all of my vlogs going forward. YouTube playlist URLs are ugly long URLs so I'm using what I hope is an easy to remember bit.ly URL for you to get to my vlogs: http://bit.ly/ATSB-videos - and of course ATSB stands for Around the Storage Block. With bit.ly URLs, the capitalization has to be right so note that.
(Editor note: corrected a wrong URL on 11/11/10)