07-22-2015 03:02 AM
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 fix
root@node1:# vradmin -g ossdg -l repstatus ossrvg
Replicated Data Set: ossrvg
Primary:
Host name: punjab_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
Config Errors:
delhi_core-ossrvg: Primary-Primary configuration
root@node1:# vxprint -PV
Disk group: ossdg
TY NAME ASSOC KSTATE LENGTH PLOFFS STATE TUTIL0 PUTIL0
rl to_delhi_core_ossrvg ossrvg ENABLED - - PAUSE - -
rv ossrvg - ENABLED - - ACTIVE - -
root@node1:/ericsson/hagcs/etc# vxprint -Pl
Disk group: ossdg
Rlink: to_delhi_core_ossrvg
info: timeout=500 packet_size=1452 rid=0.1329
latency_high_mark=10000 latency_low_mark=9950
bandwidth_limit=none
state: state=PAUSE
synchronous=off latencyprot=off srlprot=override
assoc: rvg=ossrvg
remote_host=delhi_core-ossrvg IP_addr=10.161.21.197 port=4145
remote_dg=ossdg
remote_dg_dgid=1374151282.15.node1
remote_rvg_version=30
remote_rlink=to_punjab_core_ossrvg
remote_rlink_rid=0.7142
local_host=punjab_core-ossrvg IP_addr=10.161.54.197 port=4145
protocol: UDP/IP
flags: write enabled attached primary_paused consistent disconnected asynchronous
root@node1:/ericsson/hagcs/etc#
=========================================
root@node2:/ericsson/hagcs/etc# vradmin -g ossdg -l repstatus ossrvg
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
Config Errors:
punjab_core-ossrvg: Primary-Primary configuration
root@node2:/ericsson/hagcs/etc# vxprint -PV
Disk group: ossdg
TY NAME ASSOC KSTATE LENGTH PLOFFS STATE TUTIL0 PUTIL0
rl to_punjab_core_ossrvg ossrvg ENABLED - - ACTIVE - -
rv ossrvg - ENABLED - - ACTIVE - -
root@node2:/ericsson/hagcs/etc# vxprint -Pl
Disk group: ossdg
Rlink: to_punjab_core_ossrvg
info: timeout=500 packet_size=1452 rid=0.7142
latency_high_mark=10000 latency_low_mark=9950
bandwidth_limit=none
state: state=ACTIVE
synchronous=off latencyprot=off srlprot=autodcm
assoc: rvg=ossrvg
remote_host=punjab_core-ossrvg IP_addr=10.161.54.197 port=4145
remote_dg=ossdg
remote_dg_dgid=1384451046.29.node2
remote_rvg_version=30
remote_rlink=to_delhi_core_ossrvg
remote_rlink_rid=0.1329
local_host=delhi_core-ossrvg IP_addr=10.161.21.197 port=4145
protocol: UDP/IP
checkpoint: point1
flags: write enabled attached consistent disconnected asynchronous dcm_logging resync_started
root@node2:/ericsson/hagcs/etc#
Please provide me fix
Solved! Go to Solution.
07-22-2015 10:14 PM
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
07-22-2015 04:05 AM
What I see is your secondary node is dcm_logging state, I would suggest to run a fbsync (refer command below) from new primary (old secondary) as this will resync back data & will make your old primary as secondary. Once the DCM replay is complete & both nodes are in sync, you can switch back the roles using vradmin command or using a VCS GUI
# vradmin -g <diskgroup> fbsync <rvg>
G
07-22-2015 04:36 AM
node2 is current primary and old secondary
so, current primary is dcm logging
Hence we need to run vradmin -g <diskgroup> fbsync <rvg> on node 2
Is it correct ?
07-22-2015 04:53 AM
Correct
G
07-22-2015 08:08 AM
Hi Gaurav,
getting below error ?
root@node2:/# vradmin -g <dg > fbsync rvg
Message from Primary:
VxVM VVR vradmin ERROR V-5-52-478 Cannot perform incremental synchronization: RLINK to_delhi_core_ossrvg on host punjab_core-ossrvg not in CONNECT state
07-22-2015 08:57 AM
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 ?
07-22-2015 10:14 PM
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