X-Git-Url: https://git.wh0rd.org/?p=dump.git;a=blobdiff_plain;f=dump%2Fdump.8.in;h=4f30fabf8c9e51a18bb25c8caae60ad40ea52dea;hp=a6bf3f0805ac5ba1e84ca5b56511dee660ade92a;hb=HEAD;hpb=b79d20f18b7f9219391fb3957746f6c84907d82f diff --git a/dump/dump.8.in b/dump/dump.8.in index a6bf3f0..4f30fab 100644 --- a/dump/dump.8.in +++ b/dump/dump.8.in @@ -26,11 +26,11 @@ .\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF .\" SUCH DAMAGE. .\" -.\" $Id: dump.8.in,v 1.57 2004/07/13 08:17:32 stelian Exp $ +.\" $Id: dump.8.in,v 1.63 2010/03/08 10:57:24 stelian Exp $ .\" .TH DUMP 8 "version __VERSION__ of __DATE__" BSD "System management commands" .SH NAME -dump \- ext2/3 filesystem backup +dump \- ext2/3/4 filesystem backup .SH SYNOPSIS .B dump [\fB\-\fIlevel#\fR] @@ -59,7 +59,7 @@ dump \- ext2/3 filesystem backup [\fB\-W \fR| \fB\-w\fR] .SH DESCRIPTION .B Dump -examines files on an ext2/3 filesystem and determines which files need to be +examines files on an ext2/3/4 filesystem and determines which files need to be backed up. These files are copied to the given disk, tape or other storage medium for safe keeping (see the .B \-f @@ -87,14 +87,15 @@ The following options are supported by .B dump: .TP .BI \-level# -The dump level (any integer). A level 0, full backup, guarantees the -entire file system is copied (but see also the +The dump level (any integer). A level 0, full backup, specified by +.B \-0 +guarantees the entire file system is copied (but see also the .B \-h option below). A level number above 0, incremental backup, tells .B dump to copy all files new or modified since the last dump of a lower level. The -default level is 9. Historically only levels 0 to 9 were usable in +default level is 0. Historically only levels 0 to 9 were usable in dump, this version is able to understand any integer as a dump level. .TP .BI \-a @@ -283,6 +284,12 @@ Inodes which are either directories or have been modified since the last dump are saved in a regular way. Uses of this flag must be consistent, meaning that either every dump in an incremental dump set have the flag, or no one has it. .IP +If you use this option, be aware that many programs that unpack +files from archives (e.g. tar, rpm, unzip, dpkg) may set files' +mtimes to dates in the past. Files installed in this way may not be +dumped correctly using "dump -m" if the modified mtime is earlier +than the previous level dump. +.IP Tapes written using such 'metadata only' inodes will not be compatible with the BSD tape format or older versions of .B restore. @@ -294,7 +301,7 @@ is treated as a prefix and .B dump writes in sequence to .I 001, 002 -etc. This can be useful when dumping to files on an ext2 partition, in order to +etc. This can be useful when dumping to files on an ext2/3/4 partition, in order to bypass the 2GB file size limitation. .TP .BI \-n @@ -428,7 +435,7 @@ option causes .B dump to print out, for all file systems in .I __DUMPDATES__ , -and regognized file systems in +and recognized file systems in .I /etc/mtab and .IR /etc/fstab . @@ -514,8 +521,8 @@ Always start with a level 0 backup, for example: This should be done at set intervals, say once a month or once every two months, and on a set of fresh tapes that is saved forever. .IP \(em -After a level 0, dumps of active file systems are taken on a daily basis, using -a modified Tower of Hanoi algorithm, with this sequence of dump levels: +After a level 0, dumps of active file systems are taken on a daily basis, +with this sequence of dump levels: .RS 14 .B 3 2 5 4 7 6 9 8 9 9 ... .RE @@ -528,6 +535,12 @@ set of tapes per dumped file system is used, also on a cyclical basis. After several months or so, the daily and weekly tapes should get rotated out of the dump cycle and fresh tapes brought in. .PP +Another backup strategy is the Tower of Hanoi sequence, which reuses +older tapes in a way that for newer dates the available restore points +are more frequent, then for older dates (see +http://en.wikipedia.org/wiki/Backup_rotation_scheme for additional +information). +.PP (The 4.3BSD option syntax is implemented for backward compatibility but is not documented here.) .SH ENVIRONMENT @@ -592,13 +605,13 @@ correctly with either pre-0.4b34 or 0.4b34 and later versions of .B dump provided that the machine on which .B dump -is run did not change timezones (which should be a fairly rare occurence). +is run did not change timezones (which should be a fairly rare occurrence). .SH EXIT STATUS .B Dump exits with zero status on success. Startup errors are indicated with an exit code of 1; abnormal termination is indicated with an exit code of 3. .SH BUGS -It might be considered a bug that this version of dump can only handle ext2/3 +It might be considered a bug that this version of dump can only handle ext2/3/4 filesystems. Specifically, it does not work with FAT filesystems. .PP Fewer than 32 read errors (change this with @@ -609,7 +622,7 @@ from dump can be parsed to look for lines that contain the text 'read error'. When a read error occurs, .B dump prints out the corresponding physical disk block and sector number and the -ext2/3 logical block number. It doesn't print out the corresponing file name or +ext2/3/4 logical block number. It doesn't print out the corresponding file name or even the inode number. The user has to use .BR debugfs (8), commands @@ -646,7 +659,7 @@ The backup suite was ported to Linux's Second Extended File System by Remy Card . He maintained the initial versions of .B dump -(up and including 0.4b4, released in january 1997). +(up and including 0.4b4, released in January 1997). .PP Starting with 0.4b5, the new maintainer is Stelian Pop . .SH AVAILABILITY