d2dbackup (1) -- disk to disk backup system
d2dbackup {options} { -s | <sourcedir> }
-s read list of files to backup from stdin
<sourcedir> recursively back up that directory
-g|--garbagecollect Look through all backup disks and enforce
that all files obey current retention
policies for specified sourcedir
--restore Restore a directory recursively
--verify Check each last version against live file for diff
--rdeleted When restoring, restore deleted files too
(otherwise they are skipped).
--clobber Overwrite files found when restoring
--report print a report on disk usage instead of running
--profile show performance profiling information
-n|-l list files that would be backed up; do not
actually do anything
-d=<level>|--debug <level> set debugging output to specified level.
see HOWTO.debug_levels
-v|--verbose verbose
-q|--quiet no output will be printed to STDOUT, instead mail
will be sent to ERRORMAIL, but only on errors
-h|--help print this help message
-c|--config <config file> specify config file
-f|--fsconfig <config file> specify source-fs-specific config file
--bdiskstem '/disk' fixed portion of path to bdisks,
such that unix glob "/disk*" covers
all and only bdisks.
--preference-factor <bdisk>:<integer>
set the preference factor for that
BDisk. This option may be repeated
for multiple BDisks.
--blocksize 1024 specify size of df blocks
--mincompress 4096 smaller than this wont be compressed
--diskcheckparam .001 see full docs
--maxdiskcheckcount 200 see full docs
--maxversions 60 max number of versions to save of a file
--maxsize 900100100 max total size of all versions of a file
(see also full docs)
--maxfilesize 5000000000 max size of a file to be backed up at all
--eightbitfilenames include files with names that have eight-bit
characters in them (default is on)
--excludedisks 2 number of consecutive versions required
to be on disparate target disks
--errormail root@your.dom email address for errors
--logfile d2dbackup.log log file
--include <regexp> perl regular expressions to include or exclude
--exclude <regexp> matching files from backup
--dirinclude <regexp> perl regular expressions to include or exclude
--direxclude <regexp> matching directories
--mapsrc2backup <sourcepath>:<backuppath>
add a mapping of source path to backup path.
Multiple such args are allowed on the
command line. Order matters.
--nochecklastv Do not bother to compare the modification time
of the last backup version of each file to
the mod time of the source.
see L<HOWTO.improve_performance>
--diffremove Cycle through the list of versions. Remove
the earlier of pairs of versions that
are identical.
--slow 0.5 Sleep this number of seconds before processing each
directory in the source, to avoid overloading the
source system with IO requests
-t|--sinceepoch <epoch time> use this timestamp as the date
after which to back up, rather than
the date of the timestamp read file
--timestampreadfile <filename> file whose mod time is used as the
date after which to back up
--timestampwritefile <filename> file to touch at the beginning
of the backup run
--timestampfile <filename> sets both ...read and ...write
to this value
-A|--stampreadAtime use the Access time rather than
Modification time of the
timestamp read file
see L<HOWTO.snapshots>
-M|--stampreadMtime (default) use the Modification time of the
timestamp read fileThis backup system operates by copying (compressed versions of) files from a live or source directory into several target directories, each of which is assumed to live on a different cheap disk drive. Each time a backup is done, any files modified since the time of the last backup are copied again, onto new drives if possible. As new versions are written to the backup drives, old versions of those files are deleted, according to configuration parameters for the max number of versions stored for a given file or the max amount of file space the backups of any single file may take up. These parameters may vary adaptively and dynamically as the total amount of free space in the backup drive pool varies.
See separate documentation in README.pod for complete information.
d2dbackup looks for its configuration file, d2dbackup.conf, in the following places, in order:
/etc/d2dbackup.conf
/usr/local/etc/d2dbackup.conf
./d2dbackup.confAll other paths and variables are set in the configuration file.
If no source-filesystem-specific configuration file is specified with the -f option on the command line, but a source file system is specified, d2dbackup will look in the top level of the source file system for a file named ".d2dbackup.fs.conf", and if found use that for the source-filesystem-specific configuration.
d2dbackup.conf(5)
Alex Aminoff, alex_aminoff@alum.mit.edu
Copyright 2002-2004, shared by the National Bureau of Economic Research and Alexander Aminoff
Permission is granted to copy, modify, and use this software under the Gnu General Public License, found in the file LICENSE.
These functions appear in the main d2dbackup script and are documented here due to their importance and criticality.
Die with an error message. Might send email instead or in addition. warningflag, if set, causes function to return rather than die.
Hey! The above document had some coding errors, which are explained below:
=over without closing =back