Administering a Calendar server

Archiving and updating the database (2)

You should periodically update your database by removing past events, then saving these events in an archival database. Do so by first pausing the server processes and then selecting option 2 (Archive and update calendar database) from the Calendar Administration screen. If you do not do this, the calendar database may become extremely large, degrading system performance.

The default expiration time is 30 days; that is, each time you choose this option all events that are over 30 days old are removed from the current database and stored in the archival database.

To archive and update the database, follow these steps:

  1. Pause the server processes by selecting option 8 from the Calendar Administration menu. Pausing the server processes must be done before many calendar maintenance operations and is described in ``Pausing and resuming the server (8)''.

  2. Enter 2 at the Calendar Administration menu.

  3. Enter a different expiration value in days if you do not want to accept the default value of 30. You cannot enter a value less than 7.

    The data is archived in the directory /usr/lib/sco/oadb/date, where date is the expiration date of the events you archived. Press <Return> to return to the Calendar Administration menu.

  4. Use option 8 to resume the server processes, unless you want to perform other tasks that require you to pause the server.
To restore an archived database, use option 4 (merge two calendar databases) as described in ``Merging two calendar databases (4)''.

Next topic: Verifying data integrity (3)
Previous topic: Viewing calendar statistics / troubleshooting (1)

© 2003 Caldera International, Inc. All rights reserved.
SCO OpenServer Release 5.0.7 -- 11 February 2003