SCHEDULE(ADM) UNIX System V
Name
schedule - database for automated system backups
Description
The schedule database is used in conjunction with
fsphoto(ADM) to partially automate system-wide backups. For
each filesystem to be backed-up, a cyclical schedule of
xbackup(ADM) or cpio(C) levels is specified. (fsphoto uses
cpio(C) or xbackup(ADM), for XENIX or for UNIX filesystems,
respectively.)
This cyclical schedule (or cycle) is a list of dump levels
to perform (including no dump at all) and a pointer to the
last-used element of that list. The pointer is advanced to
the next element of the list on a regular basis (each time
fsphoto is run, usually once per day), starting over at the
beginning each time it falls off the end. It is advanced,
however, only on success - the desired dump must have been
successful.
Each entry in the file is on a separate line. Blank and
comment lines (beginning with ``#'') may be placed anywhere.
Several keywords are recognized:
site sitename
Sitename is passed to fsave as a description to place
on each tape label. Usually, sitename is the name of
the company or a building number.
media drive k sizes... [format]
Device drive is a floppy capable of handling volumes
with any of the listed sizes (in kilobytes). If
specified, format is the UNIX command used to format
the described floppies. This also applies to standard
cartridge tapes.
media drive d density sizes... [format]
Device drive is a density BPI magtape capable of
handling tapes of any of the indicated sizes (in feet).
Like floppies, format is the optional UNIX command used
to format the described tape.
[0-9] size savetime importance marker
Description of each dump level, as described in
fsave(ADM). The defaults are:
Level Size Savetime Importance Marker
0 - "1 year" critical none
1 - "3 months" necessary none
2...7 - "1 month" important none
8 - "2 weeks" useful none
9 - "1 week" precautionary none
All four fields must be specified. A size of - means to use
the first size listed in the appropriate media sizes list.
Keywords should be placed before any filesystem dump
schedules. A filesystem dump schedule is of the form:
/dev/rfilesys cycle
The filesystem resident on device /dev/filesys is to be
backed-up according to cycle, which is a space-
separated list of dump levels (the digits 0 to 9,
passed to dump), or the letter x, meaning no dump
should occur.
A dump cycle must have at least one member, but it may be of
any length. Different filesystems may have cycles of
different lengths.
Here is a sample schedule file:
# SYSTEM BACKUP SCHEDULE
site mymachine
# Media Entries
# 96 tpi 1.2 MB floppy 0
# media /dev/rfd096ds15 k 1200 format /dev/rfd096ds15
# 96 tpi 1.2 MB floppy 1
# media /dev/rfd196ds15 k 1200 format /dev/rfd196ds15
# Cartridge tape 0
# media /dev/rct0 k 60000 125000 150000 tape erase
# 9-track tape drive
# media /dev/rmt0 d 1600 2400 1200 600
# Backup Descriptor Table
# Backup Vol. Save for Vitality Label
# level size how long (importance) marker
0 - "1 year" critical "a red sticker"
1 - "4 months" necessary "a yellow sticker"
8 - "3 weeks" useful "a blue sticker"
9 - "1 week" precautionary none
# Schedule Table
# 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0
# Filesystem MTWTF MTWTF MTWTF MTWTF Method
/dev/rroot 0 x 9 x 9 8 x 9 x 9 1 x 9 x 9 8 x 9 x 9 cpio
/dev/ru 9 0 9 9 9 9 8 9 9 9 9 1 9 9 9 9 8 9 9 9 cpio
In the example above, filesystem /dev/rroot is dumped using
a level 0 dump the first time fsphoto is run (on a Monday),
and if that dump is successful, the next (second) time it
runs (Tuesday), no dump is performed. If doing nothing is
successful, the third time run (Wednesday) a level 9 dump
occurs. If that dump succeeds, no dump occurs the fourth
time (Thursday), but the fifth time fsphoto is run (Friday),
a level 9 dump is made.
Each time a successful dump at the specified level happens,
the pointer advances so that the next run of fsphoto (on the
next weekday) will do the next dump scheduled for that
filesystem. If however, a dump fails (or is interrupted or
postponed by the operator) the pointer is not advanced;
hence, the next time fsphoto is attempted, the same level
dump will again be tried so the sequence will not be broken
(but the timing may be off).
Continuing the example, the nineteenth time fsphoto runs, a
level 9 dump of /dev/rroot is done, no dump is performed the
next (twentieth) time, but the twenty-first time (Monday of
every fifth week) the cycle starts over again at the
beginning with a level 0 dump.
The larger and more rapidly changing filesystems /dev/ru is
dumped more frequently (each time fsphoto is run - once a
day - instead of every other time), and the levels used are
staggered to prevent having to perform two full-scale dumps
(like levels 0 or 1) of the large filesystems on the same
day. The backup cycle period is also shorter, two weeks
instead of four.
The Method field defines the backup utility to be used.
cpio works for both XENIX and UNIX filesystems, but xbackup
works only on XENIX filesystems.
See Also
fsphoto(ADM), fsave(ADM), xbackup(ADM)
Notes
Keywords and filesystem names must not be preceded by any
spaces or tabs.
It is not necessary to specify the name of the ``raw''
(/dev/r*) device for each filesystem, but the backups are
faster if this is done.
Value Added
schedule is an extension of AT&T System V provided by the
Santa Cruz Operation.
(printed 9/14/89) SCHEDULE(ADM)