Preparing to Add High Availability (HA) to a System
A High Availability (HA) system is a local, redundant system that is created, then added to a primary system. In the event of a virtual machine failure, the system falls back to the HA system.
The HA system has the following constraints:
The HA system size must be the same as the primary system size.
The HA system must be at the same release version as the primary system.
If you update the primary system, the HA system must be updated.
If the primary system currently has HA and you are deploying a new HA system, you cannot reuse the virtual machines in the original HA system. Remove the old HA before deploying the new HA system with new virtual machines.
Because this process adds new virtual machines to your system, your current security certificate becomes invalid and requires an updated certificate unless you are using a self-signed certificate.
Your high-availability system
must be configured with the same OVA and patch as your primary system. If the versions of your
primary and high-availability systems do not match, you will be
instructed to upgrade to the higher version of the two.
The HA system internal virtual machines must be on the same subnet as the primary system internal virtual machines.
If you have added public access on the primary system, you must add it to the HA system. Also, the HA system Internet Reverse Proxy virtual machine must be on the same subnet as the primary system Internet Reverse Proxy virtual machine.
Most of the features on your
high-availability system are prohibited. For example you do not have access to
upgrade, SNMP configuration, storage access, or email servers on your
high-availability system. You can view system properties, but modification is
Before You Begin
The following conditions should be met before adding High Availability (HA) to a primary system:
The target primary system is deployed.
There is a redundant network between virtual machines.
The network is a 10gbps high-bandwidth network.
Network Time Protocol (NTP) configured on the primary and HA system, and that the clocks are synchronized.
If you are planning to add HA to a system you are also planning to update, we recommend that you add HA before updating it, then update the combined (primary and HA) system; the HA system is updated automatically when the primary system is updated. If you update the primary system first, then to add HA, you must independently deploy and then update the HA system (so both the primary and HA systems are at the same version).
Verify that all virtual
machines are functioning normally. Determine virtual machine status by viewing
the System Monitor as described in
About Your Dashboard.
We recommend that you take a
snapshot on the high-availability virtual machines before you perform this
procedure. Redo the procedure from the snapshot in case of error.
Record the fully qualified domain name (FQDN) of the high-availability
virtual machine; you must know the FQDN to
add high-availability to the primary system.
Deploying a System for High Availability (HA)
High Availability (HA) is deployed like a primary system, except that during the deployment the system identifies it as a HA system. The HA system is then linked to the primary system that uses the HA system as a fallback in the event of a primary system failure. A primary system failure is transparent to users.
We recommend that you use the same process to deploy the HA system that you used to deploy the primary system. If you do not know which process was used to deploy the primary system, use the Deploying a System Automatically process, unless you are deploying a large (2000 concurrent users) system. All large systems require Deploying a System Manually.
Verify the HA and primary system versions match:
In a separate browser window, sign in to the primary system WebEx Administration site.
On the Dashboard tab, verify that the primary system version number in the System pane matches the version of the HA.If the versions match, continue.
If the primary system is at a later version than the HA system, then you must either redeploy the HA system by using a OVA file with a matching version of the software or update the HA system.
When you update a high-availability system, after you reboot the system and the reboot process appears to be complete, we recommend that you wait an additional 15 minutes before starting your add high-availability system procedure.
Linking a High
Availability System to a Primary System
To link the primary system to a deployed HA system completing the integration of HA into the primary system:
Notify users and administrators that the system is being put into Maintenance Mode.
Sign into the primary system administration site.
System section, select the
instructions on the
Properties page to add the HA system.
Enter the fully-qualified domain name (FQDN)
of the Administration site virtual machine of the high-availability system and
The readiness of both the primary system and the HA system is validated. If both
systems are ready, then you will see a green
Add button. (Do not select it if your
system is not in Maintenance Mode.) If either
system is not ready, an error message is displayed. Fix the error and
attempt the procedure again.
If "Error code:
Database-64" displays, repeat this procedure by using a snapshot of the
high-availability virtual machines.
high-availability system is added and automatically configured to serve as a
backup in the event of a primary system failure.
Maintenance Mode and
Continue to confirm.
reboots. You can sign back into the
Administration site after the restart is complete.