Disaster recovery

There are several methodologies to employ with HCL Traveler to recover from a server crash or failure.

Deploying a HCL Traveler High Availability (HA) pool inherently provides recovery from a server crash or hardware failure. In the event of a failure, device requests and mail monitoring is shifted to the remaining servers in the pool. For more information, refer to High Availability (HA).

Alternatively, it is also possible to set up multiple standalone HCL Traveler servers as potential disaster recovery servers for each other. Each server could have the same access to all the mail files for a user on remote servers. If a HCL Traveler server is not responsive, the user can manually reconfigure the device client settings to point to another HCL Traveler server. Alternatively this failover could be automated using a front end proxy (for example, HCL Safelinx). After a device switches to a new server, the sync anchors no longer match between the server and device. The protocol initiates a sync refresh, where all of the data on the device is replaced by a fresh copy of the data from your mail database. Internally, the HCL Traveler server keeps track of each piece of data that is on a device. If a device switches to another server, then this history is lost due to the fact that these tracking databases are not on the network or shared between HCL Traveler servers. Likewise, switching back to the original server can also result in a sync refresh. This kind of configuration is useful in a disaster recovery scenario where High Availability is not required.