take a look at this thread  [URL]  we use different disk groups for different type of drives, for example we have one disk group for LCFC (500G drives), another group for FC (300G). Another use for disk groups is if you want  to isolate workload for one application, for example we have a dedicated disk group for Exchange because of how sensitive it is to io requirements. Don't get too disk group happy or you will create a bunch of little island and not optical backend utilization. Disk groups are created by CE's. Some CEs like to create a brand new disk group when they add disk, we ask them not to do that ..but to add disks to existing groups as longs as the disk type matches. In my shop we don't "precreate" every single symdev (some shops do that), so when i create new devices i want them to span as many physical drives as possible.
Hi Friends,  Have a couple of queries wrt DMX.  1. Can we selectively remove entries of a particluar symm from symapidb on the management host ?     Consider that a frame has been decommed and I need that frame to removed from the symapidb of the management host. I would like to do this without rebuilding the db !  2. Can a Raid Group spread across more than one Disk Group ?     Example, Diskgroup_0 has a few disks and Diskgroup_1 has few more disks of the same type. Can my RG spread cross both these DiskGroups? If yes, any possible issues ?  Thanks! Mahen.
Delete a symm from symapidb without rebuilding db