One JetPatch Manager Console is designated as active, and another, in a remote datacenter, as standby. The standby server's services are stopped. The active JetPatch Manager Console uses a primary database in its same datacenter; a hot standby database is ready, in read-only mode, in the standby server's datacenter. JetPatch-provided scripts set up the databases, replicate VAI content between the JetPatch ManagerConsole via Rsync, and replicate the database via asynchronous log shipping.
Endpoint connections to the primary server are by hostname rather than by IP address, and upon failure of the primary datacenter you activate the standby deployment and update DNS records to redirect endpoint and administrative traffic to it.
Note: for WSUS DR, install connectors on both and then add/remove WSUS DS and add new WSUS upon event.