1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
|
dirvish for Debian
------------------
Here's a simple step-by-step example of how to use dirvish to make a backup of
your root partition on a second disk which is mounted as /backup :
- Firstly, note that the example files listed below can be found in
/usr/share/doc/dirvish/examples/ as master.conf and default.conf.root .
Don't forget to modify the client line! (see below)
- In /etc/dirvish/master.conf put the following:
bank:
/backup
exclude:
lost+found/
core
*~
.nfs*
Runall:
root 22:00
expire-default: +15 days
expire-rule:
# MIN HR DOM MON DOW STRFTIME_FMT
* * * * 1 +3 months
* * 1-7 * 1 +1 year
* * 1-7 1,4,7,10 1
* 10-20 * * * +4 days
# * * * * 2-7 +15 days
Lines beginning with "#" are comments.
The "bank" (the safety deposit kind) defines where the data to be stored; in
this example it's at /backup .
The exclude stanza is a default list of filenames that are not to be
backupped.
The Runall stanza tells which "vaults" (area of storage inside the bank) to
backup during the daily run. Note that each vault contains at least one
branch; for simple usage you can basically ignore branches and then the
"default" branch will be used for a vault.
The time next to the vault name defines the timestamp of the backup; it is
forced to be in the past. This means that if the time stated is 22:00, and
the backup is made at 01:00, then the backup will have the date of the
previous day, which keeps the names of the backups consistent, even if the
backup was delayed for some reason. Also, people expect backups to contain
the state of things at the _end_ of the date shown, so setting the time to
the end of the day will keep the date as expected, even if for some reason
the backup is made after 00:00.
In short: make sure that the time listed is earlier than when the backup
will be made, preferably before midnight, and everything will be OK.
The expire-default line defines the default age after which backups will
expire, i.e. be removed by dirvish-expire.
The expire-rule stanza is for refining how long before a backup expires;
e.g. the first line has "1" for DOW (day of week), i.e. Monday. Hence
backups made on a Monday will stay around for 3 months. The second line says
that backups made in the first week of the month (DOM = day of month) won't
expire until after one year. An empty time spec is the same as "never".
- After having defined the global configuration above, a configuration for
each branch needs to be defined. Remember that each vault contains at least
one branch, and in our simple example this is simply the "default" branch.
The configuration file for the default branch is
$BANK/$VAULT/dirvish/default.conf, where $BANK is the definition of the bank
from the global config, and $VAULT is the name of the vault ("root" in our
example). So, in /backup/root/dirvish/default.conf put the following:
client: thishost
tree: /
xdev: 1
index: gzip
image-default: %Y%m%d
exclude:
/var/cache/apt/archives/*.deb
/var/cache/man/**
/tmp/**
/var/tmp/**
*.bak
The client line defines which system the data is to come from. If this is to
be a local backup i.e. the backup is made on the same system, put the output
from the hostname command here. dirvish will then know that the network is
not to be used.
The tree line defines which directory tree is to be backed up for this vault
definition.
The xdev line tells dirvish to stay on the same filesystem as the one
where the tree starts, i.e. to only backup that one filesystem. This is
a must when the backup is made to a filesystem mounted on the same tree!
Otherwise e.g. /backup would also be backupped, which won't work of course.
If the backup is on the same filesystem, exclude patterns will have to be
used. Also ensure that /proc isn't looked at by dirvish, as access to
"files" there can crash your system! Other "special" filesystems such as
devfs, sysfs and NFS mounts must also be excluded (all of which the xdev
option conveniently does for you; i.e. it's best to always backup per
filesystem).
The image-default line defines the default name of each image; the setting
above uses the year, month, and day of month.
The exclude stanza defines what files to exclude from this vault's backup,
in addition to those excludes specified in the master.conf file. See the
manpage for rsync (the "EXCLUDE PATTERNS" section) for more information.
It's important to remember that exlude patterns starting with a / begin are
anchored to the top of the gievn tree, not the root of the client.
The index: line specifies that an index file of the image is to be created
and stored and compressed with gzip.
- The definition is now complete. To initialize the first image, run the
following command:
dirvish --vault root --init
This will now create an initial backup image for root.
- From now on, the daily run of dirvish-runall will backup those vaults that
are defined in the global config in the Runall stanza.
- The daily run of dirvish-expire will examine the summary file (in the image
subdirectories inside the vault) to determine which images to remove. The
time of expiry is actually determined when the image is created. For this,
the expire rules in the global config and in the vault-specific (actually
branch-specific, remember?) config if rules exist in that config, which
overrule the global config, are used.
Note that dirvish-expire will never remove the last good image in a branch.
The best time to run dirvish-expire is just before dirvish-runall, so that
the expired images will be deleted just before the new one is created, thus
making space available for the new image. This is what the Debian
dirvish-cronjob script does (see next point).
In no circumstances should dirvish-expire and dirvish-runall run
simultaneously (as both of these can heavily impact system performance, and
running together may lead to problems); running either of these together
with updatedb (for the "locate" command) should also be avoided. Speaking
of updatedb: it's probably best to exclude the dirvish banks from the
updatedb scan! Using a separate filesystem for the bank, and only mounting
that when necessary, precludes the need to update /etc/updatedb.conf .
- The Debian installation includes a cron configuration that runs
dirvish-expire and dirvish-runall every night at 23:04. You can modify
the cron entry itself in /etc/cron.d/dirvish and the script that is run
is /etc/dirvish/dirvish-cronjob which can also be modified if necessary
(e.g. to mount and umount /backup).
- If running dirvish over the network is intended, you may want to investigate
setting up ssh so that rsync will run over ssh without passwords or
passphrases being asked. This is basically an ssh FAQ... search for
authorized_keys and/or ssh-agent.
- For more information, see the HOWTO file and FAQ.html in
/usr/share/doc/dirvish/ , and the dirvish and dirvish.conf manpages.
Also take a look at the dirvish homepage: http://dirvish.org/ .
You may also consider subscribing to the (low traffic) dirvish mailinglist,
see http://dirvish.org/mailman/listinfo/dirvish where you can also find an
archive of the list.
-- Paul Slootman <paul@debian.org>, Tue, 22 Apr 2003 14:09:50 +0200
updated Wed, 23 Jan 2019 11:45:00 +0100
|
