Configuring Failover and Redundancy for Omnissa Access in a Single Datacenter

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. Also, complete directory configuration in the Omnissa Access service before you clone the appliance.

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.

1. Recommendations for Omnissa Access Cluster
   Follow these guidelines for setting up a Omnissa Access cluster.
2. Change Omnissa Access FQDN to Load Balancer FQDN
   Before you clone the Omnissa Access virtual appliance, you must change its Fully Qualified Domain Name (FQDN) to match the load balancer FQDN.
3. Create Multiple workspace-va Virtual Appliances
   For failover, your enterprise can clone the workspace-va virtual appliance to create multiple virtual appliances of the same type to distribute traffic and eliminate potential downtime.
4. Assign a New IP Address to Cloned Omnissa Access Virtual Appliance
   You must assign a new IP address to each cloned virtual appliance before you power it on. The IP address must be resolvable in DNS. If the address is not in the reverse DNS, you must also assign the host name.
5. Enabling Directory Sync in Omnissa Access on Another Instance in the Event of a Failure
   Configure multiple instances of Directory Sync for automatic failover in case a node fails to sync.
6. Removing a Omnissa Access Node from a Cluster
   If a node in the Omnissa Access cluster is not functioning correctly and you are unable to recover it, you can remove it from the cluster with the Remove Node command. The command removes the node entries from the Omnissa Access database.