Skip to main content

storage area network - Differences between HP and EMC SAN

itemprop="text">

I've managed Dell's EMC and Equallogic
SANs in the past. I was recently put in charge of a Hewlett-Packard P2000 SAN. HP and
EMC use slightly different terminology. I'd like to confirm I understand HP's
terminology. Can you verify/correct some of the definitions
below?




vDisk. A collection of
physical disks grouped into a RAID array. EMC refers to these as "Storage Pools." vDisks
and Storage Pools aren't exactly the same as "RAID groups," but they serve the same
purpose.



Volume. A logical division of a vDisk,
which is presented to a host as a single volume. EMC refers to these as "LUNs", and LUN
is the proper term.



Storage Groups. Distinct
from "Storage Pools," EMC SANs can define "Storage Groups," which can combine multiple
LUNs into a single volume that's presented to hosts. I can't find an equivalent to this
on HP SANs.



Global Spares. Physical hard drives
that are not assigned to any vDisk. If a hard drive in a vDisk fails, the SAN
automatically uses an available spare to replace the drive and make the vDisk fault
tolerant. EMC refers to these as "hot spares." With both vendors, spares do not need to
be assigned to a particular RAID group or vDisk. The SAN will use them for any failed
hard drive.



Regarding Equallogic SANs:
Equallogic arrays create one RAID group and one LUN from all available disks in the
array. The administrator can select only: the type of RAID in the RAID group, and the
number and size of Storage Groups presented to the
hosts.




I think I have these terms
right, but I'd like to verify with someone who's used both vendors' SANs. I'm especially
concerned that I can't find HP's equivalent of Storage Groups. Surely HP has a way to
combine multiple LUNs into one logical volume. Am I missing that setting
somewhere?


itemprop="text">
class="normal">Answer



If this
P2000 is anything like my old MSA4400, then vDisks are volumes that are assigned to
servers as LUNs, but under the covers, what is happening on the HP has little in common
with a Clariion.



The way I remember it, the HP
has a bunch of disks that it sets up in fixed groups (with RAID, I think), and then
vDisks are created that live on these disks with their own virtual raid. So you could
have one vDisk with virtually raid 10, meaning each block or chunk that comprised the
vDisk would be saved twice, and another one with virtually raid 5, meaning that the
chunks would get saved once, but would have distributed
parity.



I'm a little hazy on the details about
the actual disks, whether there was raid under all these vDisks or just a JBOD. I do
remember that we had global spares, because we had several dozen disks of about 100 fail
over the course of three weeks, and the system was able to take the hits until more than
9 were rebuilding at the same time.



Maybe
someone with more recent and specific P2000 experience can chime in here and help, but
this is what I remember.


Comments

Popular posts from this blog

linux - Awstats - outputting stats for merged Access_logs only producing stats for one server's log

I've been attempting this for two weeks and I've accessed countless number of sites on this issue and it seems there is something I'm not getting here and I'm at a lost. I manged to figure out how to merge logs from two servers together. (Taking care to only merge the matching domains together) The logs from the first server span from 15 Dec 2012 to 8 April 2014 The logs from the second server span from 2 Mar 2014 to 9 April 2014 I was able to successfully merge them using the logresolvemerge.pl script simply enermerating each log and > out_putting_it_to_file Looking at the two logs from each server the format seems exactly the same. The problem I'm having is producing the stats page for the logs. The command I've boiled it down to is /usr/share/awstats/tools/awstats_buildstaticpages.pl -configdir=/home/User/Documents/conf/ -config=example.com awstatsprog=/usr/share/awstats/wwwroot/cgi-bin/awstats.pl dir=/home/User/Documents/parced -month=all -year=all...

iLO 3 Firmware Update (HP Proliant DL380 G7)

The iLO web interface allows me to upload a .bin file ( Obtain the firmware image (.bin) file from the Online ROM Flash Component for HP Integrated Lights-Out. ) The iLO web interface redirects me to a page in the HP support website ( http://www.hp.com/go/iLO ) where I am supposed to find this .bin firmware, but no luck for me. The support website is a mess and very slow, badly categorized and generally unusable. Where can I find this .bin file? The only related link I am able to find asks me about my server operating system (what does this have to do with the iLO?!) and lets me download an .iso with no .bin file And also a related question: what is the latest iLO 3 version? (for Proliant DL380 G7, not sure if the iLO is tied to the server model)

hp proliant - Smart Array P822 with HBA Mode?

We get an HP DL360 G8 with an Smart Array P822 controller. On that controller will come a HP StorageWorks D2700 . Does anybody know, that it is possible to run the Smart Array P822 in HBA mode? I found only information about the P410i, who can run HBA. If this is not supported, what you think about the LSI 9207-8e controller? Will this fit good in that setup? The Hardware we get is used but all original from HP. The StorageWorks has 25 x 900 GB SAS 10K disks. Because the disks are not new I would like to use only 22 for raid6, and the rest for spare (I need to see if the disk count is optimal or not for zfs). It would be nice if I'm not stick to SAS in future. As OS I would like to install debian stretch with zfs 0.71 as file system and software raid. I have see that hp has an page for debian to. I would like to use hba mode because it is recommend, that zfs know at most as possible about the disk, and I'm independent from the raid controller. For us zfs have many benefits, ...