Disaster Recovery and High-Availability (HA) Solutions 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 5-7 minutes.

If 5-7 mins RTO with automatic failover is needed, then please see HA article.
If a 1-3 hours RTO is satisfactory then you can use the following method: DRP without hardware replication
Otherwise, can use daily vm backups for both manager and database servers

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.

For WSUS we recommend setting it up the MSFT recommended Load Balancing and HA Procedure

Articles in this section

Comments

Articles in this section

Related articles