DAILYDUMP — User Commands

NAME

dailydump − Script to do daily dumps

SYNOPSIS

dailydump [−i] [startFs]

startFsStart dumping with the named filesystem.

−iInitialize the tape drive, remove the weekly dump lock file, and exit.

DESCRIPTION

This script does a level-1 dump of all filesystems that are normally backed up. (A level-1 dump captures all changes since the previous level-0 dump for the given filesystem.) It is normally invoked in the wee hours of the morning by cron.

When the script has completed, it sends mail to the current dumper (see the man page for weeklydump), giving the amount of free space left on the current tape. If there are detectable errors, mail is sent to the dumper with an error message.

There are normally two reasons for manually invoking dailydump. The first is to re-enable the daily dumps after the weekly dumps have completed. This is what the −i option is for. It ensures that the lock file used by the weekly dumps is gone, and it initializes the tape currently in the drive. (The dumps won’t actually commence until invoked by cron).

The other reason for invoking dailydump by hand is to restart the dumps if the machine running them crashed before the dumps could finish. In this case the user should specify the filesystem that was being dumped when the machine crashed. The dumps will begin immediately.

When invoking dailydump, be sure you’re running as root.

FILES

All of the following files are in /sprite/admin/dump:

doingdaily.activestatus file used to detect crashes. Contains the name of the host running the dumps.

doingweeklylock file to prevent daily dump from running

dumpdateslist of filesystems dumped, at what time, what tape, etc.

dumplistlist of filesystems to dump

dumplogvery large status log from the dump programs

tapelistlist of tape devices to use. Dailydump uses the first drive on the list.

KEYWORDS

dump, tape, backup