Traveler - HA not working - nsf related?

When setting up HA for Traveler should the traveler\map*.nsf files be replicated between the traveler servers?

They currently share the SQL HA database and I can see that this is working using “http:\server\lotustraveler.nsf”. This shows both servers and also that the users move from one server to the other when traveler is shutdown on one of the servers.

The problem is that the traveler clients fail to sync after I shutdown traveler on the first server.

Why should this be?

Thanks

Ron

Subject: Individual test

If I go to http://server01/servlet/traveler http://server01/servlet/traveler or http://serverdr/servlet/traveler http://server01/servlet/traveler" they both show IBM Notes Traveler Version: 9.0.0.0 Build 201303041735 running on server01 on the User Status page.

I know that DNS names are not pointing to the same servers / IP addresses.

Why would this be happening?

Subject: external traveler hostname

the external server URL is the url that phone get recorded in their profile doc, if thats hardcoded to the primary server (or missing)
then your proxy failover may not be coming into play

check your server doc → Notes Traveler Tab ->Basics

Subject: Load balancer…

Sounds like your load balancer is not routing the HTTP sessions to the second server when the first is shutdown.

Subject: maybe try testing independent of the LB

outside of synching / failover verify that you can use the phone to access http resources on both Traveler servers directly.
I’d recommend verify domino/http/traveler is ok then focus on why LB isnt failing you over once you’ve proven to yourself that both servers are accessible directly.

Subject: Further tests

I can access / connect to the Traveler servers independently. The ShowActive and ShowUser verify this.

We are not using load balancing. The second traveler server is purely for DR.

The problem is that when using the DR Traveler and I shutdown Traveler or HTTP on the primary server; the Traveler devices I lose the ability to sync. Only if Traveler and HTTP tasks are running on the primary server do they connect/sync with the DR one.

The method of switching that we are using is to manually change the IP address that our reverse proxy server points too.

It seems to point to a forwarding of HTTP traffic from our reverse proxy server. The think is that I have this pointing to the DR Traveler so I can’t see why I have the problem.

Subject: Late update

Issue was the web server was allow sending requests only to one server.

Subject: External Server url

The External Server url is the same on both servers.

Any other thoughts as to what the problem may be?

Thanks