IBM Lotus Sametime uses DB2 databases. Most of the maintenance for DB2 has been automated, and database backup and recovery is fully outlined in the DB2 information center. See "Developing a backup and recovery strategy
" at http://publib.boulder.ibm.com/infocenter/db2luw/v9/index.jsp
IBM recommends configuring online backup of DB2 for Lotus Sametime products. The specific commands and approach depend on the backup software and hardware, but basically you enable archiving of recovery logs, You must also have a process in place to manage them (for example compress, or copy, or archive and delete).
The following sections list additional best practices for maintaining DB2 in Sametime.
For meeting rooms in Sametime Standard, it is possible to enable full text search which uses DB2. This should probably not be done unless search performance requires it. See "Turning on full text indexing in the Meeting Room Center
" in the Sametime information center.
For Lotus Sametime Advanced see the following topics for information on backing up and tuning DB2:
DB2 9.5 and beyond for Linux has changed the process model, and does not support 32 bit DB2 for production use. If you are are using Linux, use the 64bit operating system and DB2.
For DB2 performance issues, monitor memory use . Do not let your database server run out of memory. Check the db2diag.log file database server for errors. Monitor the database server at start time to make sure all buffer pools start cleanly.
Have your database administrator tune DB2 for specific environments for the amount of memory used, and put the recovery logs on a low-use drive, Many of the database creation or text index scripts (.bat or .sh) have comments in them pointing out options for large or specialized environments.