To see primary and secondary replicated data set (RDS) details
vradmin printvol
vradmin -l printrvg
To see replication status
vradmin -g dg_name -l repstatus rvg_name
To check free space in a DG
vxdg -g dg_name free
To see basic RVG configuration including RVG roles and states, rlink names and states, data/srl volume names and states
vxprint –ht
vxprint -Pl
To see current status of the rlink - what mode its currently in, and how much data is currently being logged for the rlink (run on a primary node)
vxrlink -g disk_group status rlink_name
To see how many messages secondary RVG is behind the primary (run on secondary)
vxrlink -g disk_group -T updates rlink_name
To see extended statistics for the rlink such as how many blocks have been sent over the network, the round trip time, the current replication speed, any errors etc.
vxrlink -g disk_group stats rlink_name
To displaying port numbers (ports should be identical on primary and secondary)
/usr/sbin/vrport
To change port numbers (values stored persistently in /etc/vx/vvrports. Restart affected daemon)
/usr/sbin/vrport daemon new_port_number
To recover from SRL Overflow (dcm_logging flag shown on primary rlink). Performing a DCM replay will set rlinks to inconsistent until the replay is complete. As such good practice would be to create snapshots of data volumes on the secondary node before starting the replay (hence the cache/cachesize attributes for the vradmin resync command).
vxrvg –g disk_group resync rvg_name OR
vradmin –g disk_group resync rvg_name [cache=cache_object|cachesize=size]
vradmin printvol
vradmin -l printrvg
To see replication status
vradmin -g dg_name -l repstatus rvg_name
To check free space in a DG
vxdg -g dg_name free
To see basic RVG configuration including RVG roles and states, rlink names and states, data/srl volume names and states
vxprint –ht
vxprint -Pl
To see current status of the rlink - what mode its currently in, and how much data is currently being logged for the rlink (run on a primary node)
vxrlink -g disk_group status rlink_name
To see how many messages secondary RVG is behind the primary (run on secondary)
vxrlink -g disk_group -T updates rlink_name
To see extended statistics for the rlink such as how many blocks have been sent over the network, the round trip time, the current replication speed, any errors etc.
vxrlink -g disk_group stats rlink_name
To displaying port numbers (ports should be identical on primary and secondary)
/usr/sbin/vrport
To change port numbers (values stored persistently in /etc/vx/vvrports. Restart affected daemon)
/usr/sbin/vrport daemon new_port_number
To recover from SRL Overflow (dcm_logging flag shown on primary rlink). Performing a DCM replay will set rlinks to inconsistent until the replay is complete. As such good practice would be to create snapshots of data volumes on the secondary node before starting the replay (hence the cache/cachesize attributes for the vradmin resync command).
vxrvg –g disk_group resync rvg_name OR
vradmin –g disk_group resync rvg_name [cache=cache_object|cachesize=size]
