Configuring Failover and Redundancy for Omnissa Access in a Single Data Center

To achieve failover and redundancy, you can add multiple Omnissa Access virtual appliances in a cluster. If one of the appliances shuts down for any reason, Omnissa Access is still available.

To create the cluster, you first install and configure a Omnissa Access virtual appliance, then you clone it. Cloning the virtual appliance creates a duplicate of the appliance with the same configuration as the original. You can customize the cloned virtual appliance to change the name, network settings, and other properties as required.

Before you clone the Omnissa Access virtual appliance, you must configure it behind a load balancer and change its Fully Qualified Domain Name (FQDN) to match the load balancer FQDN.

After cloning, you assign the cloned virtual appliance a new IP address before powering it on. The cloned virtual appliance IP address must follow the same guidelines as the IP address of the original virtual appliance. The IP address must resolve to a valid host name using forward and reverse DNS.

All nodes in the Omnissa Access cluster are identical and nearly stateless copies of each other. Syncing to Active Directory and to resources that are configured, such as Horizon or ThinApp, is deactivated on the cloned virtual appliances.