cancel
Showing results for 
Search instead for 
Did you mean: 

disk layout redesign & migration question

mike_li
Not applicable
I have a EMC Symmetrix 8830. Solaris 8, Oracle Ver 9.2 and DB size is ~220GB and mainly reads happening. From vxprint there are 11 disk members oracle files are in a striped volume (c6t17d21-d25) and concatenated volumes (c6t17d67s+c6t17d41 and c6t17d67s+c6t17d42). I read that Veritas software stripe over EMC HW stripe is not recommended and I'm planning to migrate from current disk layout to concatenated volumes. Could someone recommend the steps to migrate current mixed disklayout to one single concatenated disklayout in a Veritas 3.5 env, within limited maintenance time window. I would like to keep current LUN sizes and logical volumes because the filesystems sizes will have to remain the same if possible.

Thank you in advance.
Mike
512byte blocks:
dm oradg01 c6t17d9s2 sliced 1024 17674495 - CONCAT
dm oradg02 c6t17d8s2 sliced 1024 17674495 - CONCAT
dm oradg03 c6t17d7s2 sliced 1024 17674495 - CONCAT

dm oradg04 c6t17d25s2 sliced 1024 70704895 - STRIPE
dm oradg05 c6t17d24s2 sliced 1024 70704895 - STRIPE
dm oradg06 c6t17d23s2 sliced 1024 70704895 - STRIPE
dm oradg07 c6t17d22s2 sliced 1024 70704895 - STRIPE
dm oradg08 c6t17d21s2 sliced 1024 70704895 - STRIPE

dm oradg09 c6t17d67s2 sliced 2623 35349120 - CONCAT
dm oradg10 c6t17d41s2 sliced 3839 70700160 - CONCAT
dm oradg11 c6t17d42s2 sliced 3839 70700160 - CONCAT
1 REPLY 1

Joerg_Hallbauer
Not applicable
I wouldn't recommend using CONCAT for database volumes in the general case. Basically, what I would recommend is the following:

1) Separate LOGs from data (i.e. put them on different LUNs)
2) Stripe your data
3) Separate your data and indexes on separate LUNs if you can

--joerg