I'm pretty new to EQ and just getting my head round the basics at the moment. I've inherited a number of old and new arrays and just wanted to run a few design considerations - thanks in advance for looking. Here's what I've got
3 x PS400E - All 14 x 750GB SATA, connected to a 1GB network, currently only being used as dumb offline storage, all default storage, all one group.
2 x PS6010E - Both 16 x 1TB SATA, connected to a 1GB network located on a different subnet (unused at present)
1 x PS6010X - 16 x 600GB SAS, connected to a 10GB network, located on a different subnet (unused at present)
The three groups above are all located on different subnets on our network, this is what I have in mind - there's no requirement for snapshots or replication at this point.
Group 1
3 x PS400E - Single storage pool configured with RAID10, primarily used to store non-critical VM's and adhoc offline storage
1 x PS6010X - Single storage pool configured with RAID10, used to store critical VM's (Oracle DB etc)
Group 2
2 x PS6010E - Single storage pool configured with RAID10, used to store Novell and Groupwise volumes
Q1
Group 1 will contain members on different subnets, is this possible?
Q2
What are the actual benefits of creating storage pools? Is it purely to separate out different types of data? For instance if on my 3 x PS400E I created 2 storage pools, one for web based VM's and one for application VM's what would be the actual benefit if any, the only thing I can see is a disadvantage in if you ran out of space in one pool.
Is storage pools just a way of ensuring you don't end up mixing different drive speeds?
Q1: In order for it to be a supported configuration, you would have to have full routing between all the IP subnets. Which makes the router a choke point and lessens the value of having them on different subnets. Plus routing adds a small amount of latency, which obviously not a good thing. The array will try to use any available port to reach an initiator.
Q2: There are a number of benefits to storage pools. One you increase the iSCSI connection count from 512 to 512 per storage pool for a max of 1024. That will be going up even more in a future release of firmware.
Storage tiering allows you finer control over your storage. The SATA/SAS separation being a large benefit. This insures that you can get the maximum performance from your SAS arrays. Combined with SANHQ you can determine which volumes require what level of performance and move the volumes appropriately. Plus, that can be done in real time without making any changes to the host.
Thanks for your help Don, I found an EQ document regarding storage and tiering so that's helping a lot. My SAS/SATA mix group over two subnets is worrying me slightly with the router latency so may suggest move them to the same subnet. The complexity for the network team is the PS6010X is 10GB which the older PS400E's are all 1GB.
"Thanks for your help Don, I found an EQ document regarding storage and tiering so that's helping a lot. My SAS/SATA mix group over two subnets is worrying me slightly with the router latency so may suggest move them to the same subnet. The complexity for the network team is the PS6010X is 10GB which the older PS400E's are all 1GB.
Pete"
Pete,
1Gb and 10Gb separation is another great reason for using multiple pools. While in the same pool with the same RAID pol, you are effecctively relegating the 10Gb array to a 1Gb array when you consider the host POV since the host will have to effectively wait for the blocks from the 1Gb arrays no matter how fast the other array is.
WRT the L3 configuraiton. L3 from the array perspectve complicates things somewhat. Most customers implementing L3 with EQL keep the arrays in one subnet and put the hosts in different subnets. Again, routing latency can be much longer than L2 hop latency, so keep an eye on it.
Many thanks for you help on this - much appreciated. Going to hopefully set up the arrays this week. From what I remember should you ideally upgrade all arrays in the same group to the same firmware?
Donald_Williams
72 Posts
503
0
Posted May 6th, 2010 10:00
Q2: There are a number of benefits to storage pools. One you increase the iSCSI connection count from 512 to 512 per storage pool for a max of 1024. That will be going up even more in a future release of firmware.
Storage tiering allows you finer control over your storage. The SATA/SAS separation being a large benefit. This insures that you can get the maximum performance from your SAS arrays. Combined with SANHQ you can determine which volumes require what level of performance and move the volumes appropriately. Plus, that can be done in real time without making any changes to the host.
-don