To backup the calendar database using the Sun StorEdge or Legato backup software:
Copy the Sun StorEdge or Legato nsrfile binary file to the /usr/lib/nsr directory.
Create these symbolic links in the /usr/lib/nsr directory:
icsasm -\> /opt/SUNWics5/cal/sbin/icsasm nsrfile -\> /usr/lib/nsr/nsrfile
Change to the /opt/SUNWics5/cal/sbin directory and run the csbackup utility with the -l option. For example:
cd /opt/SUNWics5/cal/sbin ./csbackup -l
The -l option creates a backup directory image under the current directory. The files in this directory are empty and are used only to provide information to the backup program about how calendars will be stored on the backup media. If the backup directory already exists, it is synchronized with the current directory structure.
Use the save command to back up calendar data. For example:
/usr/bin/nsr/save -s /opt/SUNWics5/cal/sbin/budir
You can also use the Sun StorEdge or Legato backup GUI to schedule backups by setting up a client save set to periodically backup the database.
Notes Do not modify the .nsr files. These generated files contain directives that are interpreted by the save command and the icsasm command during the backup process.
Calendar Server does not support the incremental backup feature. Do not use this feature because the backup directory is only an image of the folder structure and contains no actual data.
You cannot backup a calendar with a name that contains non-ASCII characters or the forward slash (/).
Automate the backup procedure.
The preceding steps describe how to run a backup manually. Set up the backup program’s backup command to run the Calendar Server csbackup command-line utility before the running the backup program’s save command to achieve an automated backup process.