I can´t find any documentation on how to set up a traveler cluster, can someone help me?Is it possible to do it:
-
Using only a domino cluster
-
With a load balancer
I don’t want to use a standby server.
THX
/Jesper
Subject: RE: How to set up a Traveler Cluster?
Traveler cannot be clustered.Traveler can run on a Domino server that is part of a cluster and the Traveler users can have their mail databases on mail clusters (Traveler does handle the clustering of the user mail files), but the Traveler add-in itself cannot be clustered. The Traveler clients must always talk to the same Traveler server.
You can have multiple Traveler servers and divide the user population amongst the servers, but the clients must always communicate with the same server - they cannot go back and forth without doing a reconfigure.
Subject: RE: How to set up a Traveler Cluster?
THX
How should I solve this then? A Load balancer and a script to copy the files between the servers, could that work?
A passive Vmware server with the data on our clustered SAN?
How many users can I have on one server?
/Jesper
Subject: RE: How to set up a Traveler Cluster?
You cannot use a load balancer. You need to “load balance” by which users you assign to which server. If you have 2 servers, you can put half the users in a group that syncs with server A and the other half of the users in a group that syncs with server B. This is not true load balancing because server A may be maxed out while server B is basically idle, but this is the best you are going to do for now.
Thus, you load balance by deciding which server the Traveler users will use. Then, if one server is getting all work and the other is not, you will need to tell the users to reconfigure with the other server. This reconfiguration will delete the existing data on the device and get all new data from the Domino server, so you do not what to do that too often.
The Traveler data is stored in a database, so there isn’t a “file” per user that you could copy from one server to another.
How many users a Traveler server can support depends on the hardware. And, there are 2 numbers of users. One number is the number of users that are being monitored for Auto Sync and the other number is the number of users who are actively syncing to get new data from the server (not Auto Sync, but real data syncing). Because most devices are not actively syncing most of the time, the former number can be much larger than the latter.
Subject: why not dns load balancer?
I am just in operation moving traveler from server B to A with intention to withdraw B. I have installed Traveler on A and changed DNS alias “mobile” from B to A. Now I observe that no client reconfiguration is neccessary. Phones connect to A and works fine. Now I read the post here and recall old method to create DNS-based load balancing. I am on Traveler v.8522
Subject: RE: why not dns load balancer?
You can migrate as you did, but you do not want to have the devices switched servers too often. Each time the devices switch servers, they will “replace data sync” which means that all data will be deleted on the device and a new copy of everything synced from the server to the device. That’s why you should not have a sprayer or load balancer in the front.