.TH bkpadmin 8 "28 November 2011" "distorted.org.uk backup"
.SH NAME
bkpadmin \- backup archive administration
.SH SYNOPSIS
.B bkpadmin
.I command
.RI [ argument ...]
.PP
Commands recognized:
.PP
.B help
.br
.B initvol
.I tag
.I device
.br
.B mount
.RI [ tag ]
.br
.B umount
.br
.B initmeta
.br
.B chkmeta
.br
.B prep
.I asset
.I level
.RI [ date
.I time
.IR tz ]
.br
.B abort
.I asset
.br
.B fail
.I asset
.br
.B level
.I asset
.br
.B hash
.I asset
.I file
.I hash
.br
.B commit
.I asset
.br
.B check
.I asset
.I label
.br
.B catalogue
.I asset
.br
.B outdated
.I asset
.br
.B test
.I command
.RI [ argument ...]
.SH DESCRIPTION
The
.B bkpadmin
command assists with the maintenance of disk backup volumes.  A backup
volume contains a hierarchy of backed up data, as follows.  The volume
stores data for a number of client
.IR hosts .
Each host has a number of
.I assets
which need to be backed up.  Each time an asset is backed up, the backup
files are collected together and assigned a
.IR label .
.PP
The
.I host
names don't actually need to correspond to actual hosts, though that's
the intent.  Rather, they correspond to mutually untrusting sources of
backup data.  Each host is represented locally by a user named
.BI bkp- host \fR.



.SH BUGS
There's far too much local policy embedded in here: LVM volume naming,
user naming, key management, and so on.  Splitting this out would be a
really good idea, though probably not for the faint of heart.