To enable recovery of the 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 the HA article.
- If a 1-3 hour RTO is satisfactory, then you can use the following method: DRP without hardware replication
- Otherwise, can use daily VM backups for both the manager and the database servers
One JetPatch Manager Console is designated as active, and another, located in a remote data center, is designated as standby. The standby server's services are stopped.
The active JetPatch Manager Console utilizes a primary database located in the same datacenter; a hot standby database is available, in read-only mode, on the standby server's datacenter. JetPatch-provided scripts set up the databases, replicate VAI content between the JetPatch Manager Console 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 according to the MSFT-recommended Load Balancing and HA Procedure
Comments
0 comments
Please sign in to leave a comment.