cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
Veritas.com
Support

How to re-create RVG

Go to solution
grigori
Level 5

‎08-06-2015 02:45 AM

I have mistankly deleted 2 disks that were used as cachevol for secondary RVG and data in secondary become unaccessible, for that i went through deleting the DG and succeeded.

now i am trying to create RVG group again, for that i should delete both RVG in main and DR which seems impossible, even dissociate SRL volume from primary RVG seems impossible

any hint please?

BR, 

0 Kudos
1 ACCEPTED SOLUTION

Accepted Solutions

Go to solution
mikebounds
Level 6
Partner Accredited

‎08-06-2015 04:50 AM

Steps are freeze replication group on both nodes and then on SYS1 run

  1. vxrlink -g DB2hrDG dis rlk_SYS2-rep_DB2-rvg 
  2. vxrlink -g DB2hrDG det rlk_SYS2-rep_DB2-rvg
  3. vxedit -g DB2hrDG rm rlk_SYS2-rep_DB2-rvg
  4. Look at flags in vxprint -Vl - (lowercase L on end) and if RVG is a primary  then run:
    vradmin  -g DB2hrDG delpri DB2-rvg

    else if RVG is a secondary then run:

    vxrvg -g DB2hrDG  stop DB2-rvg (may need to use -f)
    vxvol -g DB2hrDG dis <vol_name> for each of the volumes in the RVG (all volumes in the diskgroup including the SRl -so example):
    vxvol -g DB2hrDG dis SYS1_DB2_DB1 

    Then:
    vxedit -g DB2hrDG rm DB2-rvg
     
  5. Now can create your RDS as normal using:
    vradmin createpri
    vradmin addsec
  6. And start replication
    vradmin -a startrep
     

For steps 6 and 7, these are not full commands, but if you type them as above they will give you the syntax - example:

# vradmin createpri
VxVM VVR vradmin ERROR V-5-52-19 Incorrect number of arguments
VxVM VVR vradmin INFO V-5-52-37
    Usage: vradmin [-g diskgroup] [-nodcm] createpri rvg vol1,vol2,... srl

Let me know if you need any more help for steps 6 and 7.

 

Mike

View solution in original post

0 Kudos
6 REPLIES 6

Go to solution
mikebounds
Level 6
Partner Accredited

‎08-06-2015 02:47 AM

Please post output of:

vxprint -VPl
vxprint -v

from both nodes.

Mike

0 Kudos

Go to solution
grigori
Level 5

‎08-06-2015 03:20 AM

hi Mark,

outputs below:

root@SYS2 # vxprint -VPI
Disk group: DB1hrDG

TY NAME         ASSOC        KSTATE   LENGTH   PLOFFS   STATE    TUTIL0  PUTIL0
rl rlk_SYS1-rep_DB1-rvg DB1-rvg CONNECT - -     ACTIVE   -       -
rv DB1-rvg    -            ENABLED  -        -        ACTIVE   -       -
root@SYS2 # vxprint -v
Disk group: OFFLINEBackup

TY NAME         ASSOC        KSTATE   LENGTH   PLOFFS   STATE    TUTIL0  PUTIL0
v  OFFLINE-Backup1 fsgen     ENABLED  5492455424 -      ACTIVE   -       -

Disk group: DB2hrDG

TY NAME         ASSOC        KSTATE   LENGTH   PLOFFS   STATE    TUTIL0  PUTIL0
v  SYS2_DB2_DB1 fsgen  ENABLED  2243868672 -      ACTIVE   -       -
v  SYS2_DB2_DB2 fsgen  ENABLED  2243868672 -      ACTIVE   -       -
v  SYS2_DB2_DB3 fsgen  ENABLED  2243868672 -      ACTIVE   -       -
v  SYS2_DB2_DB4 fsgen  ENABLED  2243868672 -      ACTIVE   -       -
v  SYS2_DB2_DB5 fsgen  ENABLED  2243868672 -      ACTIVE   -       -
v  SYS2_DB2_DB6 fsgen  ENABLED  2243868672 -      ACTIVE   -       -
v  SYS2_DB2_DB7 fsgen  ENABLED  2243868672 -      ACTIVE   -       -
v  SYS2_DB2_DB8 fsgen  ENABLED  2243868672 -      ACTIVE   -       -
v  SYS2_DB2_DB9 fsgen  ENABLED  2243868672 -      ACTIVE   -       -
v  SYS2_DB2_Process fsgen ENABLED 1616820224 -    ACTIVE   -       -
v  SYS2_DB2_SRL fsgen  ENABLED  419346432 -       ACTIVE   -       -
v  SYS2_DB2_Script fsgen ENABLED 209631232 -      ACTIVE   -       -

Disk group: DB1hrDG

TY NAME         ASSOC        KSTATE   LENGTH   PLOFFS   STATE    TUTIL0  PUTIL0
v  SYS1_DB1_DB1 DB1-rvg ENABLED 2243868672 -    ACTIVE   -       -
v  SYS1_DB1_DB2 DB1-rvg ENABLED 2243868672 -    ACTIVE   -       -
v  SYS1_DB1_DB3 DB1-rvg ENABLED 2243868672 -    ACTIVE   -       -
v  SYS1_DB1_DB4 DB1-rvg ENABLED 2243868672 -    ACTIVE   -       -
v  SYS1_DB1_DB5 DB1-rvg ENABLED 2243868672 -    ACTIVE   -       -
v  SYS1_DB1_DB6 DB1-rvg ENABLED 2243868672 -    ACTIVE   -       -
v  SYS1_DB1_DB7 DB1-rvg ENABLED 2243868672 -    ACTIVE   -       -
v  SYS1_DB1_Process DB1-rvg ENABLED 1616820224 - ACTIVE  -       -
v  SYS1_DB1_SRL DB1-rvg ENABLED 419346432 SRL   ACTIVE   -       -
v  SYS1_DB1_Script DB1-rvg ENABLED 209631232 -  ACTIVE   -       -

 

root@SYS1 #  vxprint -VPI
Disk group: DB1hrDG

TY NAME         ASSOC        KSTATE   LENGTH   PLOFFS   STATE    TUTIL0  PUTIL0
rl rlk_SYS2-rep_DB1-rvg DB1-rvg CONNECT - -     ACTIVE   -       -
rv DB1-rvg    -            ENABLED  -        -        ACTIVE   -       -

Disk group: DB2hrDG

TY NAME         ASSOC        KSTATE   LENGTH   PLOFFS   STATE    TUTIL0  PUTIL0
rl rlk_SYS2-rep_DB2-rvg DB2-rvg DETACHED - -    STALE    -       -
rv DB2-rvg    -            ENABLED  -        -        ACTIVE   -       -
root@SYS1 #
root@SYS1 # vxprint -v
Disk group: DB1hrDG

TY NAME         ASSOC        KSTATE   LENGTH   PLOFFS   STATE    TUTIL0  PUTIL0
v  SYS1_DB1_DB1 DB1-rvg ENABLED 2243868672 -    ACTIVE   -       -
v  SYS1_DB1_DB2 DB1-rvg ENABLED 2243868672 -    ACTIVE   -       -
v  SYS1_DB1_DB3 DB1-rvg ENABLED 2243868672 -    ACTIVE   -       -
v  SYS1_DB1_DB4 DB1-rvg ENABLED 2243868672 -    ACTIVE   -       -
v  SYS1_DB1_DB5 DB1-rvg ENABLED 2243868672 -    ACTIVE   -       -
v  SYS1_DB1_DB6 DB1-rvg ENABLED 2243868672 -    ACTIVE   -       -
v  SYS1_DB1_DB7 DB1-rvg ENABLED 2243868672 -    ACTIVE   -       -
v  SYS1_DB1_Process DB1-rvg ENABLED 1616820224 - ACTIVE  -       -
v  SYS1_DB1_SRL DB1-rvg ENABLED 419346432 SRL   ACTIVE   -       -
v  SYS1_DB1_Script DB1-rvg ENABLED 209631232 -  ACTIVE   -       -

Disk group: DB2hrDG

TY NAME         ASSOC        KSTATE   LENGTH   PLOFFS   STATE    TUTIL0  PUTIL0
v  SYS1_DB2_DB1 DB2-rvg ENABLED 2243868672 -    ACTIVE   -       -
v  SYS1_DB2_DB2 DB2-rvg ENABLED 2243868672 -    ACTIVE   -       -
v  SYS1_DB2_DB3 DB2-rvg ENABLED 2243868672 -    ACTIVE   -       -
v  SYS1_DB2_DB4 DB2-rvg ENABLED 2243868672 -    ACTIVE   -       -
v  SYS1_DB2_DB5 DB2-rvg ENABLED 2243868672 -    ACTIVE   -       -
v  SYS1_DB2_DB6 DB2-rvg ENABLED 2243868672 -    ACTIVE   -       -
v  SYS1_DB2_DB7 DB2-rvg ENABLED 2243868672 -    ACTIVE   -       -
v  SYS1_DB2_DB8 DB2-rvg ENABLED 2243868672 -    ACTIVE   -       -
v  SYS1_DB2_DB9 DB2-rvg ENABLED 2243868672 -    ACTIVE   -       -
v  SYS1_DB2_Process DB2-rvg ENABLED 1616820224 - ACTIVE  -       -
v  SYS1_DB2_SRL DB2-rvg ENABLED 419346432 SRL   ACTIVE   -       -
v  SYS1_DB2_Script DB2-rvg ENABLED 209631232 -  ACTIVE   -       -

 

regards

0 Kudos

Go to solution
mikebounds
Level 6
Partner Accredited

‎08-06-2015 04:50 AM

Steps are freeze replication group on both nodes and then on SYS1 run

  1. vxrlink -g DB2hrDG dis rlk_SYS2-rep_DB2-rvg 
  2. vxrlink -g DB2hrDG det rlk_SYS2-rep_DB2-rvg
  3. vxedit -g DB2hrDG rm rlk_SYS2-rep_DB2-rvg
  4. Look at flags in vxprint -Vl - (lowercase L on end) and if RVG is a primary  then run:
    vradmin  -g DB2hrDG delpri DB2-rvg

    else if RVG is a secondary then run:

    vxrvg -g DB2hrDG  stop DB2-rvg (may need to use -f)
    vxvol -g DB2hrDG dis <vol_name> for each of the volumes in the RVG (all volumes in the diskgroup including the SRl -so example):
    vxvol -g DB2hrDG dis SYS1_DB2_DB1 

    Then:
    vxedit -g DB2hrDG rm DB2-rvg
     
  5. Now can create your RDS as normal using:
    vradmin createpri
    vradmin addsec
  6. And start replication
    vradmin -a startrep
     

For steps 6 and 7, these are not full commands, but if you type them as above they will give you the syntax - example:

# vradmin createpri
VxVM VVR vradmin ERROR V-5-52-19 Incorrect number of arguments
VxVM VVR vradmin INFO V-5-52-37
    Usage: vradmin [-g diskgroup] [-nodcm] createpri rvg vol1,vol2,... srl

Let me know if you need any more help for steps 6 and 7.

 

Mike

0 Kudos

Go to solution
grigori
Level 5

‎08-06-2015 05:29 AM

hi Mark,

when executing the delpri command i got the below messages:

Message from Primary:
VxVM VVR vradmin ERROR V-5-52-533 Primary RVG DB2-rvg is started. Use force option -f to override.

should I use the -f option, does this affect any of the mounted volumes? i dont wanna VVR to go down on the primary too so Oracle goes down too

 

thanks

0 Kudos

Go to solution
mikebounds
Level 6
Partner Accredited

‎08-06-2015 08:01 AM

Using -f is fine - it won't effect writes to mounted volumes.

Mike

0 Kudos

Go to solution
grigori
Level 5

‎08-07-2015 07:11 AM

thank you Mike

appriciating your help

 

best regards

0 Kudos