In this section, we describe common maintenance tasks for the Lotus Notes Traveler system. For a list of recommended maintenance releases for Notes Traveler see this technote
If the system is a stand-alone implentation, you must care only nsf files and logs related to Lotus Notes Traveler and Lotus Domino. If there are VPN server or proxy server, their maintenance is added. When you configure a high availability system, you must maintenance Lotus Notes Traveler, Lotus Domino, enterprise database, and load balancer or IP sprayer.
This section focus on the maintenance of Lotus Notes Traveler, Lotus Domino, and enterprise database. For the maintenance of other components, see their product documents.
The resource that are common for maintenance on both stand-alone and high availability Lotus Notes Traveler environment includes application(*.nsf), database, log, and server.
Lotus Notes Traveler uses LotusTraveler.nsf
to store information about server, users, and devices. Maintain this file same as other applications files. For example, run compact command weekly and run updall or fixup monthly.
For details about nsf maintenance, see
Administrator Guide for Domino Server maintenance
In a stand-alone environment, Lotus Notes Traveler uses a Derby relational database to store the device information, device security information, and synchronization information. In a high availability environment, IBM DB2 or Microsoft SQL database plays this role. You must maintain the database that is used by your Lotus Notes Traveler servers.
To have the Lotus Notes Traveler server, the log files must have sufficient space for the Lotus Notes Traveler to log the operation and configuration information. You can define the log size in the "Lotus Traveler" tab of the server document tab.
"Maximum File Size" is the size of the log file to maintain. Once a log file is rolled over, a time stamp is added to the file name where the "*" is (NTSActivity*.log). The server keeps the number of historical files as defined by the "Maximem Number of Activity Logs Files" parameter on the same tab in the server document.
You can clear all the logs with the tell traveler log clear
command, More details about logging, see 8.6 Logging
The administrator should keep track of the number of devices that are accessing the server and ensure that the proper number of HTTP threads are allocated to the server.
A guideline for estimating of the number of threads that are needed is 1.2 times of the number of devices. If the number of devices accessing the server increases from 800 devices to 1000 devices, the HTTP threads that are allocated to the server should be updated to reflect this change:
- For 800 devices, set the number of HTTP threads to 960.
- For 1000 devices, set the number of HTTP threads to 1200.
Similar to other Lotus Domino servers, the Lotus Notes Traveler server should be restarted periodically for stable running.
Stand-alone environment only
In the version before the Lotus Notes Traveler 8.3.1 Upgrade Pack1, you must defragment the internal database that Traveler used regularly. Though the how Lotus Notes Traveler enters data into this internal database and makes use of the database has changed, however, it is still beneficiary to defragment this database on a regular basis.
You can judge how often you should run defrag by checking the size of /traveler/ntsdb
You must restart the Lotus Notes Traveler to defragment the database. To defragment the Lotus Notes Traveler database, use the following methods:
- Manual defragmentation:
You can instruct the server to defragment the database using the defrag option in the load traveler command:
- Automatic defragmentation:
You can set the NTS_DEFRAG_INTERVAL_DAYS parameter in notes.ini to have the server detects when is the last defragmentation was performed on the server and run the defragmentation function on restart if the defined threshold is passed.
For example, if you want the Lotus Notes Traveler to defragment the database every 30 days, set the parameter as follows:
If this parameter is defined and a defragmentation runs, the following parameter is added to the notes.ini file:
The NTS_LAST_DEFRAG parameter records the last time a defragmentation was run on the server. You can also force a defragmentation by deleting the NTS_LAST_DEFRAG parameter if you have set the NTS_DEFRAG_INTERVAL_DAYS parameter.
High availability environment only
For a high availability deployments of the Lotus Notes Traveler environment, maintaining the enterprise database is essential. Review the product documentation for the required maintenance of the database that you use for the server.