Or forget about Re-IP all-together and setup separate overlapping networks for each site for the purpose of Veeam DR, using site-to-site vpn (or whatever WAN techno you are using).
Re-IP is a huge headache and who knows whether any applications are happy with new IPs.
This is what we do with our DR design. We have a co-lo with the exact same network scheme as production (overlapping network) connected via site-to-site VPN. Just replicate from prod to dr. If we need to failover, just orchestrate them from a second Veeam's server at the dr site. No need to worry about Re-IP. Each site or Veeam server/proxy do know that the other side has the same IP scheme. They access each other via different IPs, of course, that are then double NATed from the firewalls.
Search the Veeam forum as I got the idea from a thread here. And look into setting up overlapping network setup between two sites. We do it with two different firewalls too, SonicWall and Cisco ASA.