Posts Tagged ‘uptime’

Ensure Users Stay Online During a System Failure with RHUB’s High Availability Cluster

October 13th, 2014

Real-time collaboration tools have made significant strides in the last few years, evolving from a tool of convenience to a necessity in most organizations. As a result of such evolution, uptime has become a crucial issue. Once invitations have been sent, sales and marketing staff cannot simply reschedule a webinar because of an uptime issue. In order for tech support to provide customers with superior support, they must be able to stay with those customers and rest assured that interactive meetings will not be interrupted.

Fortunately, there is a solution available. RHUB’s High Availability Cluster architecture has made it possible for customers to effectively handle all types of situations. For example, with the RHUB High Availability Cluster, it is possible for servers to work together simultaneously, thus ensuring high availability. In the event that one server is down, the other server will automatically begin delivering service.

Two servers are required for the RHUB High Availability function. This includes a master server as well as a slaver server. As soon as the High Availability begins, the master server will start providing service to the TurboMeeting users. The slave server will stand by until it is called into service if the master server goes offline. Based on the availability of a server, the master and slave server roles change in an automatic fashion. If the initial master server should go offline for a period of up to 20 seconds, the current slave server will automatically begin filling the master server role and remain so until it goes offline.

An Ethernet port is provided to each server, making it possible for you to connect the port to your LAN. The figure below shows how this is deployed. The two servers are not required to be on the same network, although this is recommended.

Deploying the RHUB HA Cluster Is Easy with the Following Steps:

1. Ensure that your Database Is Backed Up
This is vital. Due to the fact that the database of the slave server will be replaced by the master server’s database every minute, you will need to back up your database prior to setup and beginning the HA servers. It is also advisable to back up the master and the slave server databases on a daily basis.

2. Setup the HA Servers
Ensure that both the HA servers possess the same IP. You will also need to configure your firewall to port forward these ports: 443 (TCP), 80 (TCP), 8889 (TCP & UDP) to these IP
address, as well.

3. Begin or Stop High Availability Servers
You may stop or start the HA server with the click of a button. After the HA server begins, it will remain started until you stop the server by clicking the Stop HA Server button. It should be noted that the status of the HA stop/start will not be affected in the event that the server is powered on or off. The HA server holding the production database is the Primary Master Server. You will need to configure and ensure that the primary master server is working first.

4. Check the status of the HA Server
Next, you will need to check the status of the High Availability server. This is done by clicking the Refresh button located on the HA management page. The HA running status works independently of the TurboMeeting Server’s running status. This means that you should not assume that the TurboMeeting server application is running or even operating properly simply because the HA is running. Likewise, if the HA has a stopped status, this does not indicate that the TurboMeeting server application has also ceased to run.

Would you like to know more about RHUB’s Web Conferencing & Remote Support Servers? Are you interested in knowing more about High Availability Configuration? If so, call us at 1-866-758-0984 or email us at

  • Share/Save/Bookmark