test

Sun Java System Calendar Server 6.3 Administration Guide

9.6 Enabling Archive Backups for Calendar Server 6.3 Databases

This section contains overview material and instructions for enabling archival backups for Calendar Server databases if you did not configure them when the configuration program ran.

This section covers the following topics:

9.6.1 What are Archive Backups in Calendar Server Version 6.3?

Archive backups consist of a snapshot and the log files that were created for it. The log files are not applied to the snapshot. The archive databases remain on disk until purged. See 9.2.3 How Circular Backups Work in a Calendar Server 6.3 System.

ProcedureTo Enable Archive Backups for a Calendar Server 6.3 System

  1. Log in as an administrator with permission to change the configuration.

  2. Stop Calendar Server services by issuing the stop-cal command.

  3. At a command line, change to the directory where the ics.conf is located:

    cd /etc/opt/SUNWics5/config

  4. Enable archive backups by setting the following ics.conf parameter to “yes”:

    caldb.berkeleydb.archive.enable=”yes”

  5. Specify the directory path for the archive directory:

    caldb.berkeleydb.archive.path=
   /var/opt/SUNWics5/archive_backup_directory

    You might choose to place the archive backups on an alternate disk or disk subsystem in case of a hardware failure on the primary disk drive. Doing this might also reduce I/O contention on the primary drive or subsystem.

    If you have a high availability (HA) configuration, specify the path as a subdirectory in shared storage (/global/cal/). See also, Chapter 6, Configuring Calendar Server 6.3 Software for High Availability (Failover Service).

  6. When you have completed editing the ics.conf file, restart Calendar Server:

    cal-svr-base/SUNWics5/cal/sbin/start-cal

    The calendar services do not need to be stopped to edit the ics.conf file, but you must restart the services in order for the changes to take effect.