|Oracle Calendar Server Administrator's Guide
Part Number B10093-01
A regular schedule of node maintenance is the best protection against unscheduled down time and loss of data. Following the procedures outlined below will minimize problems and ensure that your calendar server runs smoothly and without interruption.
This chapter outlines the following tasks:
The following system monitoring procedures should be performed on a daily basis:
unistatus utility displays the current status of the calendar server. For full information on use and syntax, see the calendar server Reference Manual, Appendix C, "Utilities."
/users/unisondirectory or file system. For more information on calculating the storage requirements for your node, see Appendix A, "Disk Space and Memory".
/users/unison/logdirectory. This task can be automated by "grep"ing/searching the log files for specific errors, and e-mailing the results to the calendar server administrator.
/users/unison/log/dbv.log. This file is created only if there is a problem and should be manually removed once the problem is resolved. If the file is present and is not empty, you might analyze the contents and use the
unidbfixutility (contact your support provider for the most current version), or consult your support provider for further assistance.
A nightly backup of the calendar database (
/users/unison/db) and configuration files (
/users/unison/misc) is your best protection against database corruption that may occur as a result of a power failure or disk crashes. While database corruption is rare, even under the aforementioned conditions, nightly backups serve as a safeguard in the event that your database cannot be restored. For more information, see "Back up and restore".
The following system maintenance procedures should be done after hours on a monthly basis:
unidssyncas required to ensure that the information in the node(s) is synchronized with that in the directory server. For full information on use and syntax, see the calendar server Reference Manual, Appendix C, "Utilities."
unirmoldutility should be run monthly to remove all events and tasks older than 12-18 months. For full information on use and syntax, see the calendar server Reference Manual, Appendix C, "Utilities."
unidbfixutility. Contact your support provider for the most current version of this comprehensive database maintenance and repair utility.
unidbfixutility should be run in check mode once a week with the calendar server running, and in fix mode once a month with the calendar server down. If the weekly check discovers an error, it should be corrected immediately using
unidbfixin fix mode; if the weekly check produces a warning, maintenance can be delayed until the monthly fix.
unidsdiffto detect and resolve any discrepancies in the mapping between users and resources in the directory server with those in the calendar server node. For full information on use and syntax, see the calendar server Reference Manual, Appendix C, "Utilities." You should perform this synchronization procedure every 2-4 weeks or as required when making a batch of changes to the calendar node, particularly when deleting users. You may also synchronize your calendar and directory servers through the Admin GUI.
[ENG] stats = TRUEin
unison.ini. When a client connection is closed, stats results are appended to the
/users/unison/log/stats.logfile. After analysis, set
[ENG] stats = FALSEto disable logging, as the file grows quickly.
To minimize the impact on your users, back up your calendar server only during periods of low user activity. If you use an external directory server, back up your directory server concurrently with your calendar server to minimize inconsisencies should it become necessary to restore a backup.
You have three options for backing up your calendar server:
unidbbackup utility is recommended, as it provides on-line or `hot' backups, important in the context of installations requiring 24-hour access to their calendar data. An on-line backup can not be achieved by simply copying the database files while the server is still running, as the files on disk are not necessarily an accurate reflection of the state of the database at any given time. If you choose to copy the database files directly, you must stop your server to allow all database contents to be written to the disk first.
unidbbackup is running:
unidbrestore is the complementary utility used for database restoration. For full information on the use and syntax of the
unidbrestore utilities, see the calendar server Reference Manual, Appendix C, "Utilities."
unidbbackuputility through the command line or using the Database Backup dialog box of the Admin GUI. A backup will be made of all database and configuration files on your calendar server. If more than one node exists on the host,
unidbbackupwill back up each in turn.
unidbrestoreto restore the backup. Your calendar database and configuration files will be restored to the
/users/unisondirectory on the host.
This operation restores only the database and configuration files. Calendar data stored in a directory server must be restored separately. If you have any reason to expect that inconsistencies may exist between the data in the calendar server and that in the directory server, use the
Archived backups should be managed to ensure full data recovery capabilities without sacrificing large amounts of disk space. Remove backups that are no longer needed.