I just need to provision FAST Cache for my array (CX4-480).
I have 4 available disks that I split into two buses excluding 0_0.
Documents "EMC FAST Cache, A Detailed Review" and emc251589 are very useful, but I need advise whether I configure my mirror(s) as 2 sets of 2 disks or 1 set of 4.
What would be a better setup and why if you can answer.
this is from the same solution you mentioned earlier:
The highest level of availability can be achieved by binding the Primary and Secondary for each RAID 1 pair are on different buses (i.e. not just different enclosures on the same bus). However this does add to the complexity of configuring FAST Cache, because the configuration would need to be done using the secure CLI. This is not considered necessary for most implementations, but is done to further reduce the chances of multiple drive failures (which are already unlikely).
by the way did you see recommendation that if you have 2 or 4 drives:
As a general rule, when configuring FAST Cache, make sure all of the drives involved are either entirely contained within enclosure 0_0 (only recommended for 2 or 4 drive FAST Cache configurations) or entirely in enclosures other than 0_0. Either of these recommended configurations will not result in unnecessary rebuilds upon array power-downs. Please see emc285141for further information about the use of Bus 0 Enclosure 0.
Just select the number of drives and let the array do the magic. You can run "naviseccli -h getrg -messner" to see how it picked the devices. I bet you one pair will be two disks on bus 1 and the other pair on bus 3.
dynamox
11 Legend
•
20419 Posts
•
87439 Points
811
0
Posted May 30th, 2012 19:00
this is from the same solution you mentioned earlier:
The highest level of availability can be achieved by binding the Primary and Secondary for each RAID 1 pair are on different buses (i.e. not just different enclosures on the same bus). However this does add to the complexity of configuring FAST Cache, because the configuration would need to be done using the secure CLI. This is not considered necessary for most implementations, but is done to further reduce the chances of multiple drive failures (which are already unlikely).