HCL Traveler Server High Availability

HCL Domino Domino Forum
,
1

Hi All,

Currently we have a single standalone Traveler server 14.0.1 in Main office and everything going smoothly.

However, as per our management instruction, we need to setup another Traveler server in another location (network connectivity available to Main office), so that if Main office server goes down the HCL verse users will fail over to another traveler server automatically. I know it can be possible with Traveler HA setup.

We already have Microsoft SQL enterprise server in place with license.

I just want to know, which is the simple IP Sprayer can achieve this and also if some one have any good document with diagram to share with me would be more helpful.

Regards,

2

Hello,

You can use any load balancer which has basic capabilities of HTTP load balancing.

There are many simple load balancers.

https://logz.io/blog/best-open-source-load-balancers/

You can just try to use any one of them and see if it works fine.

However it is recommended that, both Traveler servers in HA should be in same network (LAN) for good speed. Be sure to check best practices for HA.

Here are some useful links.

https://help.hcl-software.com/traveler/11.0.0/habestpractices.html

https://help.hcl-software.com/traveler/11.0.0/deployanipsprayerorloadbalancer.html

Thank you.

Sandeep

3

@Sandeep Deshpande great summary of where to find this information, thank you!

4

Hello,

To establish a High Availability (HA) environment for your HCL Traveler 14.0.1 servers, deploying an IP sprayer or load balancer is essential. This setup ensures that if the primary server in your primary location becomes unavailable, user requests are automatically redirected to the secondary server at the alternate location.

IP Sprayer Options mentioned as below:

  1. F5 BIG-IP
  2. Kemp LoadMaster.
  3. NGINX:
  4. HAProxy

Key Steps for Configuring Traveler HA:

  1. Enterprise Database Configuration:

    • Utilize your existing Microsoft SQL Enterprise server to set up a shared database accessible by all Traveler servers in the HA pool.
    • Ensure that the database permissions and schema are appropriately configured for Traveler.

  2. Traveler Server Deployment:

    • Install and configure HCL Traveler on the new server at the secondary location.
    • Ensure that both the primary and secondary servers are configured identically to maintain consistency across the HA pool.

  3. Domino Clustering:

    • Configure Domino clustering to synchronize data between the Traveler servers, ensuring seamless failover and data consistency.

  4. Load Balancer Configuration:

    • Deploy your chosen IP sprayer or load balancer to distribute client requests between the Traveler servers.
    • Configure health checks to monitor server availability and implement sticky sessions to maintain session persistence.

Please refer below product documentation for your better understanding.

https://help.hcl-software.com/traveler/14.0.0/configuringthelotusnotestravelerhighavailabilitypool.html

https://help.hcl-software.com/traveler/11.0.0/Plan_reverse_proxy.html

Thanks

Hitesh G