On the Coda File Server designated as the SCM, verify that /vice/db/dumplist contains correct backup schedule for your volumes. If you were using createvol_rep for volume creation, you should have been prompted about the backup schedule for new volume. The dumplist contains three fields: volume id specified as its hex value, the full/incremental backup schedule, and a comment which is generally the human readable volume name. For example:

7f000001                 IFIIIII                   s:coda
7f000002                 IIIIIFI                   u:satya
7f000003                 0325476                   u:jan

The first column specifies the volume id to be backed up, the second column specifies the backup schedule by the day of the week beginning Sunday, and the third column is a comment, usually the volume name in human readable form. So, the volume id 7f000001 is scheduled for a F ull backup every Monday, and a level 1 I ncremental - Tuesday through Sunday and from the comment, we know this is a system volume called coda . Likewise, the second volume 7f000002 is scheduled for a Full backup on Friday with a level 1 incremental being done Saturday through Thursday and is a user volume called satya . The last entry shows that it is also possible to numerically identify which dumplevels are to be made on each day.

On the SCM, modify /vice/db/vicetab to indicate which host is acting as the backup coordinator and which partitions on the backup server are to be used by the backup coordinator to store the dump files. On a triply replicated system, vicetab might look like this:

tye             /vicepa         ftree  width=8,depth=5
taverner        /vicepa         ftree  width=8,depth=5
tallis          /vicepa         ftree  width=8,depth=5
dvorak          /backup1        backup
dvorak          /backup2        backup
dvorak          /backup3        backup
dvorak          /backup4        backup

vicetab , in addition to listing information on the servers providing replicated data, must also include information on the backup coordinator with backup coordinator's name in the first column, the backup partitions in the second column, and the designation backup in the third column. The 4th column is not used for the backup sub-system. Please see the vicetab (5) man page for additional information.

The number of partitions available for dumping may be controlled by the system administrator. Because the volume of data may be both large and variable, the backup program intelligently decides where to store individual dump files based on size across the specified backup partitions. The directories in the sample vicetab , are assumed to be separate local disk partitions. An organized central symbolic link tree is created by the backup.sh script in the directory /backup that points to the actual files scattered across the /backup1 , /backup2 , and /backup3 given in this example.

On the Backup Coordinator, the backup binaries and shell scripts need to be installed. The following directories should be have been created under /vice upon the installation of the Coda backup package:

/backup
/vice/backup
/vice/backuplogs
/vice/db
/vice/vol        
/vice/lib
/vice/spool
/vice/srv

The primary binaries that should be installed under /usr/sbin to get started are:

backup
backup.sh
bldvldb.sh
merge
updateclnt
updatesrv
updfetch
tape.pl

Once it has been verified that the backup system is installed, the files /vice/db/hosts , /vice/db/files should be manually copied from the SCM to the same location on the Backup Coordinator. These are needed the first time by the updateclt daemon the when it runs. Also, Coda currently relies on the BSD dump and restore command to manipulate the tapes. A copy of dump package should be installed on the backup coordinator. BSD dump is available for all UNIX and UNIX like operating systems we have successfully run Coda on. Please check with your OS Vendor if you need help obtaining a copy.