Setting Parameters for Backups and Restoration

@UNREVISED

The file `backup-specs' specifies backup parameters for the backup and restoration scripts provided with tar. You must edit `backup-specs' to fit your system configuration and schedule before using these scripts.

@FIXME{This about backup scripts needs to be written: BS is a shell script .... thus ... `backup-specs' is in shell script syntax.}

@FIXME-xref{Script Syntax}, for an explanation of this syntax.

@FIXME{Whats a parameter .... looked at by the backup scripts ... which will be expecting to find ... now syntax ... value is linked to lame ... `backup-specs' specifies the following parameters:}

`ADMINISTRATOR'

The user name of the backup administrator.

`BACKUP_HOUR'

The hour at which the backups are done. This can be a number from 0 to 23, or the string `now'.

`TAPE_FILE'

The device tar writes the archive to. This device should be attached to the host on which the dump scripts are run. @FIXME{examples for all ...}

`TAPE_STATUS'

The command to use to obtain the status of the archive device, including error count. On some tape drives there may not be such a command; in that case, simply use `TAPE_STATUS=false'.

`BLOCKING'

The blocking factor tar will use when writing the dump archive. See section The Blocking Factor of an Archive.

`BACKUP_DIRS'

A list of file systems to be dumped. You can include any directory name in the list--subdirectories on that file system will be included, regardless of how they may look to other networked machines. Subdirectories on other file systems will be ignored. The host name specifies which host to run tar on, and should normally be the host that actually contains the file system. However, the host machine must have GNU tar installed, and must be able to access the directory containing the backup scripts and their support files using the same file name that is used on the machine where the scripts are run (ie. what pwd will print when in that directory on that machine). If the host that contains the file system does not have this capability, you can specify another host as long as it can access the file system through NFS.

`BACKUP_FILES'

A list of individual files to be dumped. These should be accessible from the machine on which the backup script is run. @FIXME{Same file name, be specific. Through NFS ...}

Go to the first, previous, next, last section, table of contents.