|
|
Sponsored Content
Operating Systems
Linux
Red Hat
SAN/LVM question
Post 302534935 by msarro on Wednesday 29th of June 2011 07:47:23 AM
06-29-2011
The p2000 has gotten a bit of a dust off from the MSA2k series, thank god. They no longer require downtime to add additional shelves (verified by HP) on any of the platforms.
The logs need to be kept around for at least a few days (our operations team will be firing some scripts off at them for data mining purposes). However after that I don't see a reason why they couldn't get moved to a different location and gzipped (after say 30 days).
Each RAID 5 is currently split up into about 5 different LUNs, so none of the LUNs will be larger than 1TB a piece. Each one will be a PV, and those will get put together as VG's for each type of server (well for the two primary server types, then one for db backups, one for cross site backups, and finally one vg for the other server types). So no single PV should be larger than 1.5TB.
That's a really good point about the spare. I hadn't thought about that when I was designing it. I'm not sure if it will be possible to sacrifice the additional storage space, but if archiving after, say, 30 days is possible I'm pretty sure that will free up more than enough storage. We do have 4 hour/24x7 support from HP under our contract with them so we should be covered for speedy hardware replacements. Sadly the SNMP implementation for the P2000 isn't the best.
I actually went to a bunch of vendors and the issue was no one had a system that could run on DC power except HP. They tried to sell us a P4000 SAN, which is in fact a P2000 back end with a DL380 on the front, and that's it (it may run their proprietary storage software or something, not sure). So we found out the parts and put it together ourselves. Dell has pretty much no DC offerings, and everything from Hitachi fell well outside my budget for the storage requirements. We don't currently have a business relationship with IBM for that to have been considered (basically have to stick with the approved vendor list).
Any other advice? I appreciate everyone's feedback. Its looking like there are placers where my original design was over engineered and places where it was underengineered. Sadly I don't have access to storage specialists who aren't vendors so peer review of my design can't happen too well in house
The logs need to be kept around for at least a few days (our operations team will be firing some scripts off at them for data mining purposes). However after that I don't see a reason why they couldn't get moved to a different location and gzipped (after say 30 days).
Each RAID 5 is currently split up into about 5 different LUNs, so none of the LUNs will be larger than 1TB a piece. Each one will be a PV, and those will get put together as VG's for each type of server (well for the two primary server types, then one for db backups, one for cross site backups, and finally one vg for the other server types). So no single PV should be larger than 1.5TB.
That's a really good point about the spare. I hadn't thought about that when I was designing it. I'm not sure if it will be possible to sacrifice the additional storage space, but if archiving after, say, 30 days is possible I'm pretty sure that will free up more than enough storage. We do have 4 hour/24x7 support from HP under our contract with them so we should be covered for speedy hardware replacements. Sadly the SNMP implementation for the P2000 isn't the best.
I actually went to a bunch of vendors and the issue was no one had a system that could run on DC power except HP. They tried to sell us a P4000 SAN, which is in fact a P2000 back end with a DL380 on the front, and that's it (it may run their proprietary storage software or something, not sure). So we found out the parts and put it together ourselves. Dell has pretty much no DC offerings, and everything from Hitachi fell well outside my budget for the storage requirements. We don't currently have a business relationship with IBM for that to have been considered (basically have to stick with the approved vendor list).
Any other advice? I appreciate everyone's feedback. Its looking like there are placers where my original design was over engineered and places where it was underengineered. Sadly I don't have access to storage specialists who aren't vendors so peer review of my design can't happen too well in house
|
|
10 More Discussions You Might Find Interesting
1. Filesystems, Disks and Memory
I'm setting up a CentOS 5 server that will be connected to an HP EVA4000. My previous experience is with an HP VA7400 and HP-UX. In HP-UX I can add "alternate paths" to a volume group in order to have redundant paths to the SAN via dual fiber channel HBAs just by either adding them with... (3 Replies)
Discussion started by: deckard
3 Replies
2. AIX
I have a question about SAN commands
I have almost 15Tb of disk on my san
but assigned and something else I have almost 11Tb
There is a command to know, what its my real total storage capacity and
another command to know how much I used .?
Thanks again in advance (0 Replies)
Discussion started by: lo-lp-kl
0 Replies
3. Linux
Hi All,
I am planning to do a LVM replicate to another server.
Example :
server1.foo.com has / , /boot , swap and few LVM partitions. All are in /dev/sda disk of size 80GB. /dev/sda5 is a LVM partition which has only one vg00 and it has 2 LV's (/var and /usr) and a SAN storage connected to... (0 Replies)
Discussion started by: rakrhn
0 Replies
4. Filesystems, Disks and Memory
Hi All,
I am planning to do a LVM replicate to another server.
Example :
server1.foo.com has / , /boot , swap and few LVM partitions. All are in /dev/sda disk of size 80GB. /dev/sda5 is a LVM partition which has only one vg00 and it has 2 LV's (/var and /usr) and a SAN storage connected to... (0 Replies)
Discussion started by: rakrhn
0 Replies
5. Red Hat
Hi all;
I have a quick question about LVM.
2.6.18-92.1.18.el5
Distributor ID: RedHatEnterpriseServer
Description: Red Hat Enterprise Linux Server release 5.3 (Tikanga)
Release: 5.3
Codename: Tikanga
I was going through /etc/lvm.conf and I am not clear with lvm meta... (0 Replies)
Discussion started by: maverick_here
0 Replies
6. UNIX for Dummies Questions & Answers
I've three partitions on /dev/sda: sda1, sda2 sda3. There is FREE space between sda2 and sda3 and sda3 ends on the last sector. sda2 and sda3 have the same number of sectors allocated and so are the exact same size.
/dev/sda2 is already part of the VG VolGroup. However, what puzzles me is that... (0 Replies)
Discussion started by: Devyn
0 Replies
7. AIX
HACMP two-node cluster with mirrored LVM.
HACMP two-node cluster with two SAN storages mirrored using LVM. Configured 2 disk heartbeat networks - 1 per each SAN storage. While performing redundancy tests. Once one of SAN storage is down - cluster is going to ERROR state. What are the guidelines... (2 Replies)
Discussion started by: OdilPVC
2 Replies
8. UNIX for Dummies Questions & Answers
Hi,
I have below code for disk creation
disk_list=$(ls /dev/sd)
for disk in $disk_list
do
pvcreate $i
done
So what my understanding is first it is checking the disk under /dev sdb,sdc,sdd,...sdz whether 25 disk are existing
if not then its creating the 25 physical volume.
I... (4 Replies)
Discussion started by: stew
4 Replies
9. HP-UX
Hi,
I am very new to HP-UX, and we're going to be doing a SAN migration.
We're going to take down the machine, and zone it to the new SAN.
My question is, will the device names change and will that interfere with the LVM?
If the new disks come in with different device names, how would I... (3 Replies)
Discussion started by: BG_JrAdmin
3 Replies
10. Filesystems, Disks and Memory
Good morning.
For testing purpose i have buy a SAN DISK SHELF
i need now a controller(hsv300) and a switch SAN
Is my first SAN so i'm a little confused about cables.
For testing we use an old rx2600 hp server
the adapter is HP A6795AX A6795-62001
Some fast questions:
i need an fc/fc cable... (7 Replies)
Discussion started by: Linusolaradm1
7 Replies
LEARN ABOUT MOJAVE
fp
fp(7d) Devices fp(7d) NAME
fp - Sun Fibre Channel port driver DESCRIPTION
The fp driver is a Sun fibre channel nexus driver that enables fibre channel topology discovery, device discovery, fibre channel adapter port management and other capabilities through well-defined fibre channel adapter driver interfaces. The fp driver requires the presence of a fabric name server in fabric and public loop topologies to discover fibre channel devices. In pri- vate loop topologies, the driver discovers devices by performing PLOGI to all valid AL_PAs, provided that devices do not participate in LIRP and LILP stages of loop initialization. CONFIGURATION
The fp driver is configured by defining properties in the fp.conf file. The fp driver supports the following properties: mpxio-disable Solaris I/O multipathing is enabled or disabled on fibre channel devices with the mpxio-disable property. Specifying mpxio-disable="no" activates I/O multipathing, while mpxio-disable="yes" disables the feature. Solaris I/O multipathing may be enabled or disabled on a per port basis. Per port settings override the global setting for the specified ports. The following example shows how to disable multipathing on port 0 whose parent is /pci@8,600000/SUNW,qlc@4: name="fp" parent="/pci@8,600000/SUNW,qlc@4" port=0 mpxio-disable="yes"; manual_configuration_only Automatic configuration of SCSI devices in the fabric is enabled by default and thus allows all devices discovered in the SAN zone to be enumerated in the kernel's device tree automatically. The manual_configuration_only property may be configured to disable the default behavior and force the manual configuration of the devices in the SAN. Specifying manual_configuration_only=1 disables the automatic con- figuration of devices. FILES
/kernel/drv/fp 32-bit ELF kernel driver (x86) /kernel/drv/amd64/fp 64-bit ELF kernel driver (x86) /kernel/drv/sparcv9/fp 64-bit ELF kernel driver (SPARC) /kernel/drv/fp.conf fp driver configuration file. ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |mpxio-disable |Unstable | +-----------------------------+-----------------------------+ |manual_configuration_only |Obsolete | +-----------------------------+-----------------------------+ |Availability |SUNWfctl | +-----------------------------+-----------------------------+ SEE ALSO
cfgadm_fp(1M), prtconf(1M), stmsboot(1M), driver.conf(4), attributes(5), fcp(7D), fctl(7D), scsi_vhci(7D) Writing Device Drivers Fibre Channel Physical and Signaling Interface (FC-PH) ANSI X3.230: 1994 Fibre Channel Generic Services (FC-GS-2) Project 1134-D Fibre Channel Arbitrated Loop (FC-AL) ANSI X3.272-1996 Fibre Channel Protocol for SCSI (FCP) ANSI X3.269-1996 SCSI-3 Architecture Model (SAM) Fibre Channel Private Loop SCSI Direct Attach (FC-PLDA) ANSI X3.270-1996 SCSI Direct Attach (FC-PLDA) ANSI X3.270-1996 SCSI Direct Attach (FC-PLDA) NCITS TR-19:1998 Fabric Loop Attachment (FC-FLA), NCITS TR-20:1998 SunOS 5.10 2 Dec 2004 fp(7d)