Table of Contents
Advertisement
CMS High Availability Overview
Typically, master and cloned instances are installed on different machines, and
those machines are placed behind a load balancer. The load balancer accepts HTTP
and HTTPS requests made to the CMS system and directs those requests
appropriately between the two machines. In the event that one machine fails, the
load balancer will transparently redirect all requests to the machine that is still up
and running until such time as the other machine is brought back online. The
cloning feature in CMS also supports scalability by assigning the same task to
separate instances on different machines (e.g., handling certificate requests) in a
seemless way.
The following subsystems can be cloned and run on different hosts:
•
Certificate Manager (CA) (see "Certificate Manager" on page 85)
•
Data Recovery Manager (DRM) (see "Data Recovery Manager" on page 197)
•
Online Certificate Status Manager (see "OCSP Responder" on page 165)
Architecture of a Failover System
The diagram in Figure 16-1 shows one way to set up a cloned CMS system. In this
system, a separate OCSP Responder subsystem is handling certificate verification
by taking advantage of the CRL Publishing feature.
664
Netscape Certificate Manager System Administrator's Guide • June 2003
Advertisement
Table of Contents
