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.
Configuring Endpoint Redirection for Disaster Recovery
In a Disaster Recovery (DR) scenario, ensuring that endpoints can seamlessly transition from the Primary environment to the Standby environment is critical. There are two primary methods to achieve this: DNS Redirection or the JetPatch Connector Multi-URL configuration.
Option 1: DNS Redirection (Hostname-Based)
Endpoint connections to the primary server are established by hostname rather than by IP address. Upon failure of the primary datacenter, you activate the standby deployment and update your internal DNS records to redirect endpoint and administrative traffic to the secondary datacenter's IP address.
Pros: Centralized control at the network level.
Cons: Subject to DNS TTL (Time-to-Live) propagation delays; requires manual or scripted DNS updates during failover.
Option 2: JetPatch Connector Multi-URL (Automated Failover)
For a more resilient and automated approach, you can configure the JetPatch Connector to be aware of multiple JetPatch Manager URLs (e.g., both Primary and Standby addresses).
When the Connector service is created using the Multi-URL capability, the agent is provided with a list of prioritized addresses. If the Connector fails to reach the primary URL, it will automatically attempt to communicate with the secondary (Standby) URL without requiring DNS changes.
To implement Multi-URL support:
- Navigate to Agents > Management Agents.
- When creating or editing the JetPatch Connector Management Service, locate the JetPatch Manager URL field.
- Enter the primary URL followed by the secondary URL (e.g., https://primary.jetpatch.com, https://standby.jetpatch.com).
- Deploy or update the Management Service across your endpoints.
Pros: Automated failover; no reliance on DNS propagation; continuous connectivity even if the primary site is completely unreachable.
Note: For detailed steps on setting up this service, refer to Creating a JetPatch Connector Management Service including multi-url.
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.