Skip Headers

Oracle Calendar Server Administrator's Guide
Release 5.5

Part Number B10093-01
Go to Documentation Home
Go to Book List
Book List
Go to Table of Contents
Go to Index
Go to Master Index
Master Index
Go to Feedback page

Go to previous page
Go to next page
View PDF

Node Maintenance

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:

Maintenance procedures

Daily monitoring procedures

The following system monitoring procedures should be performed on a daily basis:


Daily maintenance procedures

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".

Monthly maintenance procedures

The following system maintenance procedures should be done after hours on a monthly basis:

Other maintenance procedures

Back up and restore

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:

The 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.

While unidbbackup is running:

unidbrestore is the complementary utility used for database restoration. For full information on the use and syntax of the unidbbackup and unidbrestore utilities, see the calendar server Reference Manual, Appendix C, "Utilities."

To back up a calendar host:

To restore a calendar host:

  1. Shut down the server.
  2. Run unidbrestore to restore the backup. Your calendar database and configuration files will be restored to the /users/unison directory 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 unidsdiff and unidssync utilities to identify and resolve all discrepancies. For full information on use and syntax, see the calendar server Reference Manual, Appendix C, "Utilities."

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.