Target DPU Has a New IP Address / Moving the Target to New Network - Connect IT Community

/* * These styles apply ONLY to the header and footer assets. */ * { padding: 0; margin: 0; box-sizing: border-box; } .super-nav { display: flex; justify-content: flex-end; align-items: center; margin: 0 auto; max-width: 1264px; padding-left: 40px; padding-right: 40px; height: 40px; text-align: right; } .super-nav a { color: #34427c; margin-right: 20px; padding: 10px; text-decoration: none; } .super-nav a:hover, .super-nav a:focus { background-color: #f7f9fa; } .footer { background: #f5f5f6; color: #555a62; font-size: 14px; line-height: 1.5; padding: 0; } .footer-image { background-image: url("/themes/kaseya/assets/images/footerImage.png"); height: 500px; background-repeat: no-repeat; background-size: cover; margin-top: -100px; } .footer-wrap { padding-left: 18px; padding-right: 18px; max-width: 1236px; margin: 0 auto; } .footer-main-content { background-color: #000; padding: 100px 0; } .footer .footer-col-title { color: #ffffff; font-weight: 700; font-size: 13px; padding-bottom: 10px; text-transform: uppercase; } .footer .footer-link { color: #9b9ca0; text-decoration: none; } .footer .footer-link:hover, .footer .footer-link:focus, .footer .footer-link:active { text-decoration: underline; } .footer-main-content .footer-link { padding-top: 10px; } .footer-row { display: flex; flex-wrap: wrap; justify-content: space-between; align-items: center; margin: -3px; } .footer-main-content-row { align-items: flex-start; } .footer-bottom-content { padding: 10px; align-items: center; } .footer-col { padding: 0 3px; display: flex; flex-direction: column; } .footer-col-copyRight { justify-content: flex-start; color: #9b9ca0; flex: 1; display: flex; } .footer-last-col { flex-direction: row; } .footer-last-col .footer-link { padding-right: 10px; text-transform: uppercase; } @media screen and (max-width: 768px) { .super-nav { padding-right: 0; } .footer-image { height: 250px; } .footer-main-content { padding: 40px 0; } .footer .footer-col-title { padding-top: 10px; } .footer-row:not(.footer-main-content-row) { display: block; } .footer-col:not(.footer-main-content-col) { width: 100%; text-align: center; padding: 10px 0; } .footer-main-content-col { width: 50%; } .footer-last-col { flex-direction: column; } .footer-last-col .footer-link { padding-bottom: 10px; } } /*# sourceMappingURL=styles.css.map */ Ask the Community Groups

Target DPU Has a New IP Address / Moving the Target to New Network - Connect IT Community | Kaseya

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
1. 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.
1. Example:
2. 50.150.200.100 UnitrendsDPU-nonVPN
3. #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
1. 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.
2. 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.
1. Now verify that the db on the target can talk to the source: psql bpdb -h SourceName
2. 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.