 There are not as many knobs to tweak on Symmetrix as there are on Clariion but typically we try to stick to these requirements:   1) transaction logs go on striped 2-way mirror devices 2) oltp databases go on striped 2-way mirror devices, data warehouse might be ok in raid-5 3) tempdb is placed on its own device (typically striped 2-way mirror device)   In the end we end up presenting4 metas to the host: one for db, one for logs, one for tempdb and one for sqldump area (raid-5). One thing that we have done in the past for very small database that need a lot of I/O, we created custom size symdev. For example this server needed a small transaction log but it was getting beat up pretty good so we created a "custom" (not our typical symdev size) symdevs. Even thought it's only ~4G device, it's actually spread over 20 physical spindles, each 431MB symdev is two, non-repeating set of spindles.         Meta Configuration       : Striped    Meta Stripe Size         : 960k    (1 Cylinders)    Meta Device Members (10) :        {        ----------------------------------------------------------------------                               BCV  DATA                    RDF  DATA                      ----------------------------  --------------------------        Sym    Cap    Std Inv BCV Inv Pair          R1 Inv R2 Inv Pair        Dev    (MB)   Tracks  Tracks  State         Tracks Tracks State        ----------------------------------------------------------------------    --> 1CCB    431        0       0  Split              -      - N/A        1CCC    431        0       0  Split              -      - N/A        1CCD    431        0       0  Split              -      - N/A        1CCE    431        0       0  Split              -      - N/A        1CCF    431        0       0  Split              -      - N/A        1CD0    431        0       0  Split              -      - N/A        1CD1    431        0       0  Split              -      - N/A        1CD2    431        0       0  Split              -      - N/A        1CD3    431        0       0  Split              -      - N/A        1CD4    431        0       0  Split              -      - N/A        ----------------------------------------------------------------------               4313        0       0                     -      -        }    you will see recommendations for concatenated metas for windows, true they are very easy to expand but they don't provide the same type of performance that you would get from a striped meta. You can perform online expansion of a striped meta, it's just that it requires for you to use 2-way mirror BCVs during the expansion.  There are other options available these days, let's say you had to increase the size of your database volume , you could use PowerPath migrator with TimeFinder/Clone where you would clone smaller volume to bigger volume and PowerPath would continue provide un-interrupted access to the volume. At the end of migration you would simply diskpart the volume to take advantage of the new space.  
Hi  Allocating storage from DMX-4. Need recommendations regarding lun setup for a database on a windows server.  -Very write Intensive (Expecting 70% writes,30% reads)-Need lun size to be 34GB (Hyper size is 8.5GB)-Server has only 2HBA's  1.) What's the best raid type? (RAID 5 or RAID 1, only two available in our env) I would have normally gone for RAID-5 but since we are expecting heavy write, I am worried that the calculation of the parity bit will slow down the writes. But choosing RAID 1 would do any good? [Protection is not important and performance is the priority. Assuming the perfect scenario where no disk goes down [IMAGE] ]  2.) Since hyper size is 8.5GB, meta needs to be created for the size of 34GB. Is striped or concatenated recommended [in the performance point of view and not future expansion prospect]? I was told that the best practise is to give concatenated metas to windows servers. Is this true and why?  3.) Instead of just having the lun mapped to one FA port in each fabric, would mapping the lun to two fa's in each fabric help to improve the performance? [Even if the lun is mapped to two fa's in each fabric, it's only going to masked to one HBA in each fabric, so I was wondering if it would show any improvement in the performance?]  Please let me know if I missed any scenarios to boost the performance. Thanks for the help in advance!!!
Need recommendations regarding lun setup