Forum Discussion

symsonu's avatar
symsonu
Level 6
9 years ago

need to fix vvr replication

  Earlier node 1 was primary and node2 was secondary Node1 crashed and node 2 become primary. Now, we have brought node1 up as below and below is the status of rlink   Please provide f...
business continuity
Replicator Option
Solaris
Troubleshooting
  • Gaurav_S's avatar
    Gaurav_S
    9 years ago

    Hi,

    Yep, the status appears as failback resync which is good ..

    Can you ensure that data is getting flushed using vxrlink command ?

    delhi_core-ossrvg# vxrlink -g <dg> -i5 status to_punjab_core_ossrvg

    monitor the same for some time, it should show the data getting reduced ..

     

    G

symsonu's avatar
symsonu
Level 6
9 years ago

I resumed the link on node1

 

vxrlink resume and linkname

 

it automaticaly went to below state , there was no need to execute fb synch manualy

 

oot@node2:/# vradmin -g dg -l repstatus rvg
Replicated Data Set: ossrvg
Primary:
  Host name:                  delhi_core-ossrvg
  RVG name:                   ossrvg
  DG name:                    ossdg
  RVG state:                  enabled for I/O
  Data volumes:               24
  VSets:                      0
  SRL name:                   oss_srl_vol
  SRL size:                   400.00 G
  Total secondaries:          1

Secondary:
  Host name:                  punjab_core-ossrvg
  RVG name:                   ossrvg
  DG name:                    ossdg
  Rlink from Primary:         to_punjab_core_ossrvg
  Rlink to Primary:           to_delhi_core_ossrvg
  Configured mode:            asynchronous
  Latency protection:         off
  SRL protection:             autodcm
  Data status:                inconsistent
  Replication status:         resync in progress (failback synchronization)
  Current mode:               asynchronous
  Logging to:                 DCM (contains 64865696 Kbytes) (failback logging)
  Timestamp Information:      N/A
  Bandwidth Limit:            N/A

 

 

Is it fine ?