Search
Search titles only
By:
Search titles only
By:
Forums
New posts
Search forums
What's new
New posts
Latest activity
Feedback
View Statistics
Members
Current visitors
Buy Sell Trade
WTB
Log in
Register
Search
Search titles only
By:
Search titles only
By:
New posts
Search forums
Menu
Install the app
Install
Reply to thread
Forums
Technology
Computer Hardware
Best enterprise solution for RHEL build environment required
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Message
<blockquote data-quote="booo" data-source="post: 2022793" data-attributes="member: 18666"><p>it goes like this, you have two switches and two dual port hbas on the boxes, the even ports (port 0) on both the hbas go to even fabric (switch 0) and the odd ports (port 1) on both the hbas go to the odd switch. this way, the connection will be resilient to port failure, hba failure and the switch failure. same applies to the array too. this way, you will have around 8 paths to the san lun. no matter which one fails, the storage never goes down.</p><p></p><p>On the other hand if you setup a NAS server, you can have two port ethernet (either 1G or 10G) and then bond them. now each eth port connects to a different network switch. this way you will again get better HA.</p><p></p><p></p><p>This means you need archival type storage and not high performance storage. you can simply do the build on the attached storage and transfer it to the archive (NAS) later. using 80k iops storage for archival is not advisable here as it would be too costly. From what I understand at this point, HP guys are simply trying to leech you by suggesting such thing.</p><p></p><p>So here is what I suggest... If your build process is disk io intensive until the process is done, then you should go for NVM. NVM or flash storage is a PCIe card which would give you around 145k iops. a 1.4 terabyte hdd would cost something like 5k. you can buy two and do a raid 1. Now, once the build is done, archive it on the current SAN(or a new NAS if you are thinking of building one) with more storage.</p><p></p><p>Being that said, I dont know much about blade servers and if they support/sell NVM storage at all. something like this <a href="http://h18006.www1.hp.com/products/storageworks/io_accelerator/" target="_blank">http://h18006.www1.hp.com/products/storageworks/io_accelerator/</a></p><p></p><p></p><p><a href="http://h20566.www2.hp.com/hpsc/doc/public/display?docId=emr_na-c00687518" target="_blank">http://h20566.www2.hp.com/hpsc/doc/public/display?docId=emr_na-c00687518</a> page 5 discusses about it. basically you stripe a volume across a lot of drives (usually all the hdds in the array or storage group) to get faster storage. (RAID 50 RAID 60) etc...</p><p></p><p></p><p>basically vmware esx but opensource and kickass. developed by NASA and Rackspace. very actively being developed.</p></blockquote><p></p>
[QUOTE="booo, post: 2022793, member: 18666"] it goes like this, you have two switches and two dual port hbas on the boxes, the even ports (port 0) on both the hbas go to even fabric (switch 0) and the odd ports (port 1) on both the hbas go to the odd switch. this way, the connection will be resilient to port failure, hba failure and the switch failure. same applies to the array too. this way, you will have around 8 paths to the san lun. no matter which one fails, the storage never goes down. On the other hand if you setup a NAS server, you can have two port ethernet (either 1G or 10G) and then bond them. now each eth port connects to a different network switch. this way you will again get better HA. This means you need archival type storage and not high performance storage. you can simply do the build on the attached storage and transfer it to the archive (NAS) later. using 80k iops storage for archival is not advisable here as it would be too costly. From what I understand at this point, HP guys are simply trying to leech you by suggesting such thing. So here is what I suggest... If your build process is disk io intensive until the process is done, then you should go for NVM. NVM or flash storage is a PCIe card which would give you around 145k iops. a 1.4 terabyte hdd would cost something like 5k. you can buy two and do a raid 1. Now, once the build is done, archive it on the current SAN(or a new NAS if you are thinking of building one) with more storage. Being that said, I dont know much about blade servers and if they support/sell NVM storage at all. something like this [url]http://h18006.www1.hp.com/products/storageworks/io_accelerator/[/url] [url]http://h20566.www2.hp.com/hpsc/doc/public/display?docId=emr_na-c00687518[/url] page 5 discusses about it. basically you stripe a volume across a lot of drives (usually all the hdds in the array or storage group) to get faster storage. (RAID 50 RAID 60) etc... basically vmware esx but opensource and kickass. developed by NASA and Rackspace. very actively being developed. [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
Technology
Computer Hardware
Best enterprise solution for RHEL build environment required
Top
Bottom