cancel
Showing results for 
Search instead for 
Did you mean: 

Migrating Oracle RAC database to new SAN storage

Bill_Ranck
Level 4

I have used mirroring in the past to migrate from old SAN storage to new SAN storage with Oracle databases running and no downtime.  I need to do this again, however the environment is different.  This time I have Oracle RAC using raw connections (no ASM) to the data.  Will this work just the same?  I see a white paper specifically stating that ASM volumes should not be mirrored, but that is not the situation here.  Just Oracle using "raw" disk groups. 

Edit:  I should also mention, these systems are using Sun Cluster.

Looking at the disk group I see lots of volumes, apparently created by Oracle, but if Veritas can see them, I assume it can mirror them correctly, but still that warning in the white paper worries me.  Anyone have any suggestions, or caveats?  Can I just mirror to new storage and then break the mirror when it's finished?

I have Veritas Volume Manager 4.1

Here is a listing showing all the volumes in the one diskgroup:

# vxprint -v -g ebsrawdg
TY NAME         ASSOC        KSTATE   LENGTH   PLOFFS   STATE    TUTIL0  PUTIL0
v  a_archive01_751m.dbf fsgen ENABLED 1538048  -        ACTIVE   -       -
v  a_int01_851m.dbf fsgen    ENABLED  1742848  -        ACTIVE   -       -
v  a_media01_1201m.dbf fsgen ENABLED  2459648  -        ACTIVE   -       -
v  a_nolog01_61m.dbf fsgen   ENABLED  124928   -        ACTIVE   -       -
v  a_queue01_501m.dbf fsgen  ENABLED  1026048  -        ACTIVE   -       -
v  a_queue02_501m.dbf fsgen  ENABLED  1026048  -        ACTIVE   -       -
v  a_ref01_1501m.dbf fsgen   ENABLED  3074048  -        ACTIVE   -       -
v  a_ref02_1002m.dbf fsgen   ENABLED  2052096  -        ACTIVE   -       -
v  a_summ01_1002m.dbf fsgen  ENABLED  2052096  -        ACTIVE   -       -
v  a_txn_data01_1002m.dbf fsgen ENABLED 2052096 -       ACTIVE   -       -
v  a_txn_data02_1002m.dbf fsgen ENABLED 2052096 -       ACTIVE   -       -
v  a_txn_data03_1002m.dbf fsgen ENABLED 2052096 -       ACTIVE   -       -
v  a_txn_data04_2049m.dbf fsgen ENABLED 4196352 -       ACTIVE   -       -
v  a_txn_ind01_1002m.dbf fsgen ENABLED 2052096 -        ACTIVE   -       -
v  a_txn_ind02_1002m.dbf fsgen ENABLED 2052096 -        ACTIVE   -       -
v  a_txn_ind03_1002m.dbf fsgen ENABLED 2052096 -        ACTIVE   -       -
v  a_txn_ind04_1002m.dbf fsgen ENABLED 2052096 -        ACTIVE   -       -
v  a_txn_ind05_751m.dbf fsgen ENABLED 1538048  -        ACTIVE   -       -
v  a_txn_ind06_1001m.dbf fsgen ENABLED 2050048 -        ACTIVE   -       -
v  cntrl01.dbf  fsgen        ENABLED  206848   -        ACTIVE   -       -
v  cntrl02.dbf  fsgen        ENABLED  206848   -        ACTIVE   -       -
v  cntrl03.dbf  fsgen        ENABLED  206848   -        ACTIVE   -       -
v  crs_ocr_raw_101m fsgen    ENABLED  206848   -        ACTIVE   -       -
v  crs_vote_raw_21m fsgen    ENABLED  43008    -        ACTIVE   -       -
v  ctxd01_21m.dbf fsgen      ENABLED  43008    -        ACTIVE   -       -
v  ctxd02_21m.dbf fsgen      ENABLED  43008    -        ACTIVE   -       -
v  log01a_11m.dbf fsgen      ENABLED  22528    -        ACTIVE   -       -
v  log01b_11m.dbf fsgen      ENABLED  22528    -        ACTIVE   -       -
v  log02a_11m.dbf fsgen      ENABLED  22528    -        ACTIVE   -       -
v  log02b_11m.dbf fsgen      ENABLED  22528    -        ACTIVE   -       -
v  log03a_11m.dbf fsgen      ENABLED  22528    -        ACTIVE   -       -
v  log03b_11m.dbf fsgen      ENABLED  22528    -        ACTIVE   -       -
v  log04a_11m.dbf fsgen      ENABLED  22528    -        ACTIVE   -       -
v  log04b_11m.dbf fsgen      ENABLED  22528    -        ACTIVE   -       -
v  odm_101m.dbf fsgen        ENABLED  206848   -        ACTIVE   -       -
v  olap_101m.dbf fsgen       ENABLED  206848   -        ACTIVE   -       -
v  owad01_11m.dbf fsgen      ENABLED  22528    -        ACTIVE   -       -
v  portal01_101m.dbf fsgen   ENABLED  206848   -        ACTIVE   -       -
v  spfileappsdb_6m.ora fsgen ENABLED  12288    -        ACTIVE   -       -
v  sysaudit_ts_01_2049m.dbf fsgen ENABLED 4196352 -     ACTIVE   -       -
v  sysaux01_1001m.dbf fsgen  ENABLED  2050048  -        ACTIVE   -       -
v  system01_1002m.dbf fsgen  ENABLED  2052096  -        ACTIVE   -       -
v  system02_1002m.dbf fsgen  ENABLED  2052096  -        ACTIVE   -       -
v  system03_1002m.dbf fsgen  ENABLED  2052096  -        ACTIVE   -       -
v  system04_1002m.dbf fsgen  ENABLED  2052096  -        ACTIVE   -       -
v  system05_1002m.dbf fsgen  ENABLED  2052096  -        ACTIVE   -       -
v  system06_751m.dbf fsgen   ENABLED  1538048  -        ACTIVE   -       -
v  system07_751m.dbf fsgen   ENABLED  1538048  -        ACTIVE   -       -
v  system08_751m.dbf fsgen   ENABLED  1538048  -        ACTIVE   -       -
v  system09_751m.dbf fsgen   ENABLED  1538048  -        ACTIVE   -       -
v  system10_1002m.dbf fsgen  ENABLED  2052096  -        ACTIVE   -       -
v  system11_1002m.dbf fsgen  ENABLED  2052096  -        ACTIVE   -       -
v  temp01_1101m.dbf fsgen    ENABLED  2254848  -        ACTIVE   -       -
v  temp02_1101m.dbf fsgen    ENABLED  2254848  -        ACTIVE   -       -
v  temp03_1101m.dbf fsgen    ENABLED  2254848  -        ACTIVE   -       -
v  temp04_2049m.dbf fsgen    ENABLED  4196352  -        ACTIVE   -       -
v  temp05_2049m.dbf fsgen    ENABLED  4196352  -        ACTIVE   -       -
v  temp06_2049m.dbf fsgen    ENABLED  4196352  -        ACTIVE   -       -
v  temp07_2049m.dbf fsgen    ENABLED  4196352  -        ACTIVE   -       -
v  tools01_501m.dbf fsgen    ENABLED  1026048  -        ACTIVE   -       -
v  undo01_2001m.dbf fsgen    ENABLED  4098048  -        ACTIVE   -       -
v  undo02_2001m.dbf fsgen    ENABLED  4098048  -        ACTIVE   -       -
v  xxfms_data.dbf fsgen      ENABLED  206848   -        ACTIVE   -       -

3 REPLIES 3

Gaurav_S
Moderator
Moderator
   VIP    Certified

well I have had a check over SFRAC guides, I don't see anywhere mentioned not to mirror the raw volumes.... Veritas mirror is a block to block copy, so to my understanding it should work ...

Gaurav

Bill_Ranck
Level 4
Thanks for the reassurance.  Can I assume Veritas will do the right thing with the Sun Cluster.  It seems to know these are shared Sun Cluster disks (has the shared indicator when doing vxdisk list command). 

I clearly need to get the Sun Cluster DID numbers set up first with the new disk space, let Veritas find them, and then mirror onto them.

Gaurav_S
Moderator
Moderator
   VIP    Certified
sorry but I didn't get that, setting up DID for new disk space ?

You will be setting up DID for sure for disks.... & once you are doing a mirroring, volume's major & minor numbers rae unchanged.... its just plexes are being added to existing volumes & Sun cluster has nothing to do with plexes ... so I believe nothing to worry atlest for volumes & its DID number

Gaurav