Series 500 Implementation

NAME

autobkup − backup or archive file system

SYNOPSIS

/etc/autobkup [−archive] [−fsck]

Remarks:

This manual entry describes autobkup as implemented on the Series 500 computers. 

Autobkup is only supported on the HP 90000 Series 500. 

DESCRIPTION

Autobkup uses find(1) and cpio(1) to save on the default tape drive (/dev/rct, which must be a tape autochanger) a cpio archive of all files which have been modified since the modification time of /etc/archivedate.  Autobkup should be periodically invoked by cron(1M) at night, or when the system is otherwise idle. 

The −archive option causes autobkup to save all files, regardless of their modification date, then update /etc/archivedate using touch(1). 

The −fsck option causes autobkup to start a file system consistency check (without correction) after the backup is complete.  This is the normal mode of nightly operation.  For correct results, it is important that the system be effectively single-user while fsck is running, especially if it is allowed to automatically fix whatever inconsistencies it finds.  Autobkup does not ensure that the system is single-user. 

Autobkup is an enhanced version of backup(1M) and supports tape autochangers such as the HP 35401.  Autobkup executes a background process /etc/bkserver which intercepts and responds to tcio’s prompts for a new special file name and allows the next tape in the magazine to be loaded automatically by the tape autochanger. 

You should edit /etc/autobkup to customize it for your system. 

The following parameters are supported and can be customized:

backupdirs specifies which directories to recursively back up (usually ., meaning all directories);

backuplog file name where start and finish times, block counts, and error messages are logged;

archive file name whose date is the date of the last archive;

remind file name that is checked by /etc/profile to remind the next person who logs in to change the backup tape;

rootdev character special file of root device for fsck;

outdev specifies the output device for the backed-up files. 

masterpty filename of the master side of the pseudo-terminal. 

slavepty filename of the slave side of the pseudo-terminal. 

fscklog file name where start and finish times and fsck output is logged. 

mytty the terminal from which attributes are taken for the pseudo-terminal. 

You may want to make other changes, such as whether or not fsck does automatic correction (according to its arguments), where cpio output is directed, other information logging, etc. 

In all cases, the output from autobkup is a normal cpio archive file (or volume) which can be read using tcio (if used to generate the backup) and cpio with the −c option. 

To run autobkup from cron, use a crontab entry similar to this:     * 2 * * 1-6 ( cd / ; /etc/autobkup ) >/dev/null 2>&1

FILES

/etc/bkserver
/etc/archivedate
parameterized file names

SEE ALSO

backup(1M), cpio(1), find(1), touch(1), cron(1M), fsck(1M). 

See the HP-UX System Administrator Manual provided with your system for recommended ways to backup and restore your file system. 

BUGS

Refer to BUGS in cpio(1). 

Autobkup cannot archive file systems that are  larger than the capacity of a single magazine of tapes.  For larger file systems, duplicate the autobkup script and customize each copy to separately archive the file systems mounted on separate mass storage devices. 

If autobkup is left running overnight and runs out of tapes, autobkup terminates, leaving the find process still waiting. You need to kill this process when you return. 

Under some error conditions /etc/bkserver terminates, leaving the find, cpio and tcio processes still waiting.  You need to kill these processes when you return. 
 
 
 

Hewlett-Packard Company  —  April 12, 1993