Administering a Calendar server

Merging two calendar databases (4)

You can merge databases from different machines when you create your network, or restore an archived database by merging it with the current database. To merge two databases, you must ensure that the following conditions are true:

The server processes are not running. To pause the server processes, use option 8.
The databases are the correct format. If either database was created under SCO Portfolio version 1.0.1 or earlier, use option 5 to convert the database to the correct format.
Individual calendar names are not used in both databases. To change the name of a user's calendar, use option 6 to move the calendar out of the database, delete the calendar, and move the calendar back in.

If you do not satisfy all of these conditions, error messages appear when you run the merge calendar option. To merge two calendars, follow these steps:

Use the Calendar Administration menu's option 8 (described in ``Pausing and resuming the server (8)'') to pause the server processes.
Enter 4 at the Calendar Administration menu.
Enter the pathname of the database you are adding (the source database) or enter q to quit.
Enter the pathname of the database you are appending to (the destination database) or enter q to quit. The default value is /usr/lib/sco/oadb/caldata; to accept this value, press <Return> without entering a pathname.

After you enter the destination database pathname, the calendars are combined and you return to the Calendar Administration menu.