Disaster Recovery Solution Overview

To enable recovery of JetPatch Manager Console following a disaster scenario, you can deploy the JetPatch Manager Console and database in two data centers, with data replication. Upon failure, you can manually reconfigure the standby server as a single active server and redirect endpoint and administrative traffic to it. The RTO (Recovery Time Objective) in this option is 4-5 minutes.

If a 1-3 hours RTO is satisfactory then you can use the following method: DRP without hardware replication

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.

Articles in this section

Comments

Articles in this section

Related articles