7F000002 | IIIFIII | coda.proj |
7F000003 | IFIIIII | coda.user |
Coda comes with a backup program `backup' and a shell script `backup.sh' which runs it. Together they read a list of volumes to be backed up, and do this (if possible). Backup clones the volume to be backed up, then dumps the clone to a file. It supports both full and incremental backups, and is designed to be run daily or weekly.
There is a script `backup.sh' is designed to be run by cron. It is the script used at CMU, and the installation does not attempt to edit it for your cell.
The backup program must backup volumes to a physical partition, since it is intended to be used with some utility like 'dump' to copy the whole partition to tape. The backup procedure is fairly well documented, though the documents do not say that you must customise backup.sh to make it work in your cell. Here are a couple of lines from a sample dumplist file:
| 7F000002 | IIIFIII | coda.proj |
| 7F000003 | IFIIIII | coda.user |
These mean that the volume with groupID 7F000002, named coda.proj, should have a full dump on Wednesdays and incremental dumps every other day, while the other volume has its full dump on Mondays. Dumplist is updated automatically when you create a read-write replicated volume; otherwise you need to edit it by hand.