SUMMARY
How to reestablish hot copy replication if moving the source or target DPU to a new network.
ISSUE
There is a source and a target that was working, but now the target has moved to a new location and has been assigned a new ip. Now, replication needs to be reactivated.
RESOLUTION
- Confirm that port 1194 was open on both firewalls for source and target.
- Open two SSH sessions, one to the source and then to the target . Verify that tun0 is present: ifconfig
- If not, use service openvpn restart to restart Openvpn service. Verify with ifconfig again that tun0 has returned.
- From source to target, ping the new ip address to verify that there is connectivity, then confirm the same from target to source. Resolve pinging as necessary.
- vi the hosts table: vi /etc/hosts
- Comment out the old nonVPN from the hosts file, then create a new nonVPN entry for the new ip address on both the source and target.
- Example:
- 50.150.200.100 UnitrendsDPU-nonVPN
- #192.168.0.75 UnitrendsDPU-nonVPN
-
psql -U postgres bpdb -c "select * from bp.systems" : On the target, check the systems table on the target and verify that is_active is set to t for the source DPU
- If not, use the command psql -U postgres bpdb -c "update bp.systems set is_active='t' where system_id='X'" where X is the specific system id for the DPU you need from the table.
- Now verify that the db on the target can talk to the source: psql bpdb -h SourceName
- If still not communicating, ssh to the source and run the command: cmc_grant grant TargetName to grant management rights on the source database.
- Now verify that the db on the target can talk to the source: psql bpdb -h SourceName
- Update the bp.systems table on the Target again: psql -U postgres bpdb -c "update bp.systems set is_active='t' where system_id='X'"
- Now restart the openvpn services on source and target: service openvpn restart
- Now verify that jobs are starting to move again.