Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP
Newer
Older
100644 401 lines (311 sloc) 13.575 kb
8a97ae0 new confkeys
sukria authored
1 # Backup Manager Configuration File
674201f release 0.5.8b
sukria authored
2 #
8a97ae0 new confkeys
sukria authored
3 # * This configuration file is divided into sections.
4 # The 'global' section is mandatory, every keys defined in
5 # this section are inherited in the other sections.
c89a6b2 2005-10-05 Alexis Sukrieh <sukria@backup-manager.org>
sukria authored
6 # * There is one section per "backup method", you have to
7 # fill the section of the chosen method.
674201f release 0.5.8b
sukria authored
8 #
9 ##############################################################
10
11 ##############################################################
e00ad0c yeah
sukria authored
12 # Repository - everything about where archives are
8a97ae0 new confkeys
sukria authored
13 #############################################################
e90e822 2006-01-05 Alexis Sukrieh <sukria@backup-manager.org>
sukria authored
14
8a97ae0 new confkeys
sukria authored
15 # Where to store the archives
16 export BM_REPOSITORY_ROOT="/var/archives"
e90e822 2006-01-05 Alexis Sukrieh <sukria@backup-manager.org>
sukria authored
17
8a97ae0 new confkeys
sukria authored
18 # For security reasons, the archive repository and the generated
19 # archives will be readable/writable by a given user/group.
026f318 Version 0.6.1
sukria authored
20 # This is recommended to set this to true.
21 export BM_REPOSITORY_SECURE="true"
e90e822 2006-01-05 Alexis Sukrieh <sukria@backup-manager.org>
sukria authored
22
8a97ae0 new confkeys
sukria authored
23 # The repository will be readable/writable only by a specific
026f318 Version 0.6.1
sukria authored
24 # user:group pair if BM_REPOSITORY_SECURE is set to true.
8a97ae0 new confkeys
sukria authored
25 export BM_REPOSITORY_USER="root"
26 export BM_REPOSITORY_GROUP="root"
749edba Added support of BM_REPOSITORY_CHMOD and BM_ARCHIVE_CHMOD.
sukria authored
27 # You can also choose the permission to set the repository, default
28 # is 770, pay attention to what you do there!
29 export BM_REPOSITORY_CHMOD="770"
7a80abf Now every backup methods are implemented in lib/backup-methods.sh
sukria authored
30
8a97ae0 new confkeys
sukria authored
31 ##############################################################
32 # Archives - let's focus on the precious tarballs...
33 ##############################################################
e90e822 2006-01-05 Alexis Sukrieh <sukria@backup-manager.org>
sukria authored
34
8666282 Fixes for bug #82, BM_TARBALL_TARGETS[] replaces BM_TARBALL_DIRECTORIES
sukria authored
35 # Each archive generated will be chmoded for security reasons
36 # (BM_REPOSITORY_SECURE should be enabled for this).
749edba Added support of BM_REPOSITORY_CHMOD and BM_ARCHIVE_CHMOD.
sukria authored
37 export BM_ARCHIVE_CHMOD="660"
38
8a97ae0 new confkeys
sukria authored
39 # Number of days we have to keep an archive (Time To Live)
40 export BM_ARCHIVE_TTL="5"
e90e822 2006-01-05 Alexis Sukrieh <sukria@backup-manager.org>
sukria authored
41
674201f release 0.5.8b
sukria authored
42 # Do you want to replace duplicates by symlinks?
8a97ae0 new confkeys
sukria authored
43 # (archive-DAY is a duplicate of archive-(DAY - 1) if they
674201f release 0.5.8b
sukria authored
44 # are both the same size).
026f318 Version 0.6.1
sukria authored
45 export BM_ARCHIVE_PURGEDUPS="true"
e90e822 2006-01-05 Alexis Sukrieh <sukria@backup-manager.org>
sukria authored
46
1ce9cd9 Syncing the CVS repo with the very last source tree...
sukria authored
47 # Prefix of every archive on that box (default is HOSTNAME)
8a97ae0 new confkeys
sukria authored
48 export BM_ARCHIVE_PREFIX="$HOSTNAME"
49
50 # The backup method to use.
72f36d8 Added examples for the svn backup method.
sukria authored
51 # Available methods are:
52 # - tarball
f878234 2005-11-10 Alexis Sukrieh <sukria@sukria.net>
sukria authored
53 # - tarball-incremental
72f36d8 Added examples for the svn backup method.
sukria authored
54 # - mysql
55 # - svn
56 # - pipe
a0b9eb9 2005-12-05 Alexis Sukrieh <sukria@backup-manager.org>
sukria authored
57 # - none
58 # If you don't want to use any backup method (you don't want to
59 # build archives) then choose "none"
8a97ae0 new confkeys
sukria authored
60 export BM_ARCHIVE_METHOD="tarball"
d29639d Initial revision
sukria authored
61
8a97ae0 new confkeys
sukria authored
62 ##############################################################
63 # Section "TARBALL"
64 # - Backup method: tarball
65 #############################################################
e90e822 2006-01-05 Alexis Sukrieh <sukria@backup-manager.org>
sukria authored
66
8a97ae0 new confkeys
sukria authored
67 # Archive filename format
68 # long : host-full-path-to-folder.tar.gz
69 # short : parentfolder.tar.gz
70 export BM_TARBALL_NAMEFORMAT="long"
e90e822 2006-01-05 Alexis Sukrieh <sukria@backup-manager.org>
sukria authored
71
67a148d + backup-manager.conf.tpl (closes: #29)
sukria authored
72 # Type of archives, available types are tar, tar.gz, tar.bz2, dar, zip.
8a97ae0 new confkeys
sukria authored
73 export BM_TARBALL_FILETYPE="tar.gz"
e90e822 2006-01-05 Alexis Sukrieh <sukria@backup-manager.org>
sukria authored
74
213c6f2 2006-03-28 Alexis Sukrieh <sukria@backup-manager.org>
sukria authored
75 # You can choose to build archives remotely over SSH.
76 # You will then need to fill the BM_UPLOAD_SSH variables
77 # (BM_UPLOAD_SSH_HOSTS, BM_UPLOAD_SSH_USER, BM_UPLOAD_SSH_KEY).
78 # If this boolean is set to true, archive will be saved locally (in
79 # BM_REPOSITORY_ROOT but will be built by the remote host).
8666282 Fixes for bug #82, BM_TARBALL_TARGETS[] replaces BM_TARBALL_DIRECTORIES
sukria authored
80 # Thus, BM_TARBALL_DIRECTORIES will be used for backup remote directories.
213c6f2 2006-03-28 Alexis Sukrieh <sukria@backup-manager.org>
sukria authored
81 # Those archive will be prefixed with the remote host name.
82 export BM_TARBALL_OVER_SSH="true"
83
8a97ae0 new confkeys
sukria authored
84 # Do you want to dereference the files pointed by symlinks ?
026f318 Version 0.6.1
sukria authored
85 # enter true or false (true can lead to huge archives, be careful).
86 export BM_TARBALL_DUMPSYMLINKS="false"
e90e822 2006-01-05 Alexis Sukrieh <sukria@backup-manager.org>
sukria authored
87
8666282 Fixes for bug #82, BM_TARBALL_TARGETS[] replaces BM_TARBALL_DIRECTORIES
sukria authored
88 # Directories you want to backup as tarballs.
89 # This is an array, take care to increment the index for
90 # each item.
91 declare -a BM_TARBALL_TARGETS
92
93 BM_TARBALL_TARGETS[0]="/etc"
94 BM_TARBALL_TARGETS[1]="/boot"
95
96 export BM_TARBALL_TARGETS
e90e822 2006-01-05 Alexis Sukrieh <sukria@backup-manager.org>
sukria authored
97
67a148d + backup-manager.conf.tpl (closes: #29)
sukria authored
98 # Files to exclude when generating tarballs, you can put absolute
99 # or relative paths, Bash wildcards are possible.
8e7d623 Added /tmp as a default blacklist item.
sukria authored
100 export BM_TARBALL_BLACKLIST="/dev /sys /proc /tmp"
d29639d Initial revision
sukria authored
101
67a148d + backup-manager.conf.tpl (closes: #29)
sukria authored
102 # With the "dar" filetype, you can choose a maximum slice limit.
6d42954 2006-01-17 Alexis Sukrieh <sukria@backup-manager.org>
sukria authored
103 export BM_TARBALL_SLICESIZE="1000M"
104
514c5c9 2006-03-29 Alexis Sukrieh <sukria@backup-manager.org>
sukria authored
105 # Extra options to append to the tarball generation
106 # (take care to what you do; this will be silently added to the
107 # command line.)
108 export BM_TARBALL_EXTRA_OPTIONS=""
109
d29639d Initial revision
sukria authored
110 ##############################################################
f878234 2005-11-10 Alexis Sukrieh <sukria@sukria.net>
sukria authored
111 # The tarball-incremental method uses the same keys as the
112 # tarball method, plus two others.
113 #############################################################
e90e822 2006-01-05 Alexis Sukrieh <sukria@backup-manager.org>
sukria authored
114
f878234 2005-11-10 Alexis Sukrieh <sukria@sukria.net>
sukria authored
115 # Which frequency to use for the master tarball?
116 # possible values: weekly, monthly
117 export BM_TARBALLINC_MASTERDATETYPE="weekly"
e90e822 2006-01-05 Alexis Sukrieh <sukria@backup-manager.org>
sukria authored
118
f878234 2005-11-10 Alexis Sukrieh <sukria@sukria.net>
sukria authored
119 # Number of the day, in the BM_TARBALLINC_MASTERDATETYPE frequency
120 # when master tarballs should be made
121 export BM_TARBALLINC_MASTERDATEVALUE="1"
e90e822 2006-01-05 Alexis Sukrieh <sukria@backup-manager.org>
sukria authored
122
f878234 2005-11-10 Alexis Sukrieh <sukria@sukria.net>
sukria authored
123 # Examples: you want to make maser tarballs every friday:
124 # BM_TARBALLINC_MASTERDATETYPE="weekly"
125 # BM_TARBALLINC_MASTERDATEVALUE="5"
126 #
127 # Or every first day of the month:
128 # BM_TARBALLINC_MASTERDATETYPE="monthly"
129 # BM_TARBALLINC_MASTERDATEVALUE="1"
130
131 ##############################################################
e00ad0c yeah
sukria authored
132 # Backup method: MYSQl
8a97ae0 new confkeys
sukria authored
133 #############################################################
e90e822 2006-01-05 Alexis Sukrieh <sukria@backup-manager.org>
sukria authored
134
c89a6b2 2005-10-05 Alexis Sukrieh <sukria@backup-manager.org>
sukria authored
135 # This method is dedicated to MySQL databases.
136 # You should not use the tarball method for backing up database
e00ad0c yeah
sukria authored
137 # directories or you may have corrupted archives.
e90e822 2006-01-05 Alexis Sukrieh <sukria@backup-manager.org>
sukria authored
138 # Enter here the list of databases to backup.
139 # Wildcard: __ALL__ (will dump all the databases in one archive)
140 export BM_MYSQL_DATABASES="__ALL__"
141
142 # The best way to produce MySQL dump is done by using the "--opt" switch
143 # of mysqldump. This make the dump directly usable with mysql (add the drop table
144 # statements), lock the tables during the dump and other things.
145 # This is recommended for full-clean-safe backups, but needs a
146 # privileged user (for the lock permissions).
147 export BM_MYSQL_SAFEDUMPS="true"
148
e00ad0c yeah
sukria authored
149 # The user who is allowed to read every databases filled in BM_MYSQL_DATABASES
150 export BM_MYSQL_ADMINLOGIN="root"
e90e822 2006-01-05 Alexis Sukrieh <sukria@backup-manager.org>
sukria authored
151
e00ad0c yeah
sukria authored
152 # its password
153 export BM_MYSQL_ADMINPASS=""
e90e822 2006-01-05 Alexis Sukrieh <sukria@backup-manager.org>
sukria authored
154
c89a6b2 2005-10-05 Alexis Sukrieh <sukria@backup-manager.org>
sukria authored
155 # the host where the database is
e00ad0c yeah
sukria authored
156 export BM_MYSQL_HOST="localhost"
e90e822 2006-01-05 Alexis Sukrieh <sukria@backup-manager.org>
sukria authored
157
e00ad0c yeah
sukria authored
158 # the port where MySQL listen to on the host
159 export BM_MYSQL_PORT="3306"
e90e822 2006-01-05 Alexis Sukrieh <sukria@backup-manager.org>
sukria authored
160
e00ad0c yeah
sukria authored
161 # which compression format to use? (gzip or bzip2)
162 export BM_MYSQL_FILETYPE="bzip2"
163
8a97ae0 new confkeys
sukria authored
164 ##############################################################
72f36d8 Added examples for the svn backup method.
sukria authored
165 # Backup method: svn
166 #############################################################
e90e822 2006-01-05 Alexis Sukrieh <sukria@backup-manager.org>
sukria authored
167
72f36d8 Added examples for the svn backup method.
sukria authored
168 # Absolute paths to the svn repositories to archive
169 export BM_SVN_REPOSITORIES=""
e90e822 2006-01-05 Alexis Sukrieh <sukria@backup-manager.org>
sukria authored
170
72f36d8 Added examples for the svn backup method.
sukria authored
171 # You can compress the resulting XML files
172 # Supported compressor are: bzip2 and gzip
173 export BM_SVN_COMPRESSWITH="bzip2"
174
175 ##############################################################
8a97ae0 new confkeys
sukria authored
176 # Backup method: pipe
177 #############################################################
e90e822 2006-01-05 Alexis Sukrieh <sukria@backup-manager.org>
sukria authored
178
b29dd5c 2005-10-23 Alexis Sukrieh <sukria@sukria.net>
sukria authored
179 # The "pipe" method is a generic way of making archive.
180 # Its concept is simple, for every kind of archive you want
181 # to make, you give: a command which will send output on stdout,
182 # a name, a file type and optionnaly, a compressor.
183
184 # Be careful, this feature uses arrays!
185 declare -a BM_PIPE_COMMAND
186 declare -a BM_PIPE_NAME
187 declare -a BM_PIPE_FILETYPE
188 declare -a BM_PIPE_COMPRESS
189
190 # You can virtually implement whatever backup scenario you like
191 # with this method.
192 #
193 # The resulting archives will be named like this:
194 # $BM_ARCHIVE_PREFIX-$BM_PIPE_NAME.$DATE.$BM_PIPE_FILETYPE
195 # If you specified a BM_PIPE_COMPRESS option, the resulting filename
196 # will change as expected (eg, .gz if "gzip").
197 #
198 # Here are a couple of examples for using this method:
199
200 # Archive a remote MySQL database through SSH:
7febcad 2005-10-24 Alexis Sukrieh <sukria@sukria.net>
sukria authored
201 # BM_PIPE_COMMAND[0]="ssh host -c \"mysqldump -ufoo -pbar base\""
202 # BM_PIPE_NAME[0]="base"
203 # BM_PIPE_FILETYPE[0]="sql"
204 # BM_PIPE_COMPRESS[0]="gzip"
b29dd5c 2005-10-23 Alexis Sukrieh <sukria@sukria.net>
sukria authored
205 # This will make somthing like: localhost-base.20050421.sql.gz
206
207 # Archive a specific directory, on a remote server through SSH:
7febcad 2005-10-24 Alexis Sukrieh <sukria@sukria.net>
sukria authored
208 # BM_PIPE_COMMAND[0]="ssh host -c \"tar -c -z /home/user\""
209 # BM_PIPE_NAME[0]="host.home.user"
210 # BM_PIPE_FILETYPE[0]="tar.gz"
211 # BM_PIPE_COMPRESS[0]=""
b29dd5c 2005-10-23 Alexis Sukrieh <sukria@sukria.net>
sukria authored
212 # This will make somthing like: localhost-host.home.user.20050421.tar.gz
e00ad0c yeah
sukria authored
213
7febcad 2005-10-24 Alexis Sukrieh <sukria@sukria.net>
sukria authored
214 export BM_PIPE_COMMAND
215 export BM_PIPE_NAME
216 export BM_PIPE_FILETYPE
217 export BM_PIPE_COMPRESS
e00ad0c yeah
sukria authored
218
8a97ae0 new confkeys
sukria authored
219 ##############################################################
220 # Section "UPLOAD"
00dfa77 2005-12-05 Alexis Sukrieh <sukria@backup-manager.org>
sukria authored
221 # You can upload archives to remote hosts with different
222 # methods.
d29639d Initial revision
sukria authored
223 #############################################################
e90e822 2006-01-05 Alexis Sukrieh <sukria@backup-manager.org>
sukria authored
224
a0b9eb9 2005-12-05 Alexis Sukrieh <sukria@backup-manager.org>
sukria authored
225 # Which method to use for uploading archives, you can put
226 # multiple methods here.
227 # Available methods:
228 # - scp
a1b9ed1 2006-04-22 Alexis Sukrieh <sukria@backup-manager.org>
sukria authored
229 # - ssh-gpg
a0b9eb9 2005-12-05 Alexis Sukrieh <sukria@backup-manager.org>
sukria authored
230 # - ftp
231 # - rsync
514c5c9 2006-03-29 Alexis Sukrieh <sukria@backup-manager.org>
sukria authored
232 # - s3
a0b9eb9 2005-12-05 Alexis Sukrieh <sukria@backup-manager.org>
sukria authored
233 # - none
e90e822 2006-01-05 Alexis Sukrieh <sukria@backup-manager.org>
sukria authored
234
a0b9eb9 2005-12-05 Alexis Sukrieh <sukria@backup-manager.org>
sukria authored
235 # If you don't want to use any upload method (you don't want to
236 # upload files to remote hosts) then choose "none"
00dfa77 2005-12-05 Alexis Sukrieh <sukria@backup-manager.org>
sukria authored
237 export BM_UPLOAD_METHOD=""
e90e822 2006-01-05 Alexis Sukrieh <sukria@backup-manager.org>
sukria authored
238
514c5c9 2006-03-29 Alexis Sukrieh <sukria@backup-manager.org>
sukria authored
239 # where to upload (global to all methods. Not required to be set for S3)
8a97ae0 new confkeys
sukria authored
240 export BM_UPLOAD_HOSTS=""
e90e822 2006-01-05 Alexis Sukrieh <sukria@backup-manager.org>
sukria authored
241
00dfa77 2005-12-05 Alexis Sukrieh <sukria@backup-manager.org>
sukria authored
242 # Where to put archives on the remote hosts (global)
243 export BM_UPLOAD_DESTINATION=""
d29639d Initial revision
sukria authored
244
00dfa77 2005-12-05 Alexis Sukrieh <sukria@backup-manager.org>
sukria authored
245 ##############################################################
246 # The SSH method
247 #############################################################
e90e822 2006-01-05 Alexis Sukrieh <sukria@backup-manager.org>
sukria authored
248
00dfa77 2005-12-05 Alexis Sukrieh <sukria@backup-manager.org>
sukria authored
249 # the user to use for the SSH connections/transfers
250 export BM_UPLOAD_SSH_USER=""
e90e822 2006-01-05 Alexis Sukrieh <sukria@backup-manager.org>
sukria authored
251
00dfa77 2005-12-05 Alexis Sukrieh <sukria@backup-manager.org>
sukria authored
252 # The private key to use for opening the connection
253 export BM_UPLOAD_SSH_KEY=""
e90e822 2006-01-05 Alexis Sukrieh <sukria@backup-manager.org>
sukria authored
254
00dfa77 2005-12-05 Alexis Sukrieh <sukria@backup-manager.org>
sukria authored
255 # specific ssh hosts
256 export BM_UPLOAD_SSH_HOSTS=""
e90e822 2006-01-05 Alexis Sukrieh <sukria@backup-manager.org>
sukria authored
257
376ff5b 2005-12-19 Alexis Sukrieh <sukria@backup-manager.org>
sukria authored
258 # port to use for SSH connections (leave blank for default one)
259 export BM_UPLOAD_SSH_PORT=""
e90e822 2006-01-05 Alexis Sukrieh <sukria@backup-manager.org>
sukria authored
260
00dfa77 2005-12-05 Alexis Sukrieh <sukria@backup-manager.org>
sukria authored
261 # destination for ssh uploads (overrides BM_UPLOAD_DESTINATION)
262 export BM_UPLOAD_SSH_DESTINATION=""
1ce9cd9 Syncing the CVS repo with the very last source tree...
sukria authored
263
00dfa77 2005-12-05 Alexis Sukrieh <sukria@backup-manager.org>
sukria authored
264 ##############################################################
a1b9ed1 2006-04-22 Alexis Sukrieh <sukria@backup-manager.org>
sukria authored
265 # The SSH-GPG method
266 # The ssh-gpg method uses the same configuration keys as the
267 # ssh method, plus one other
268 #############################################################
269
270 # The gpg public key used for encryption, this can be a short
271 # or long key id, or a descriptive name. See gpg man page for
272 # all possibilities how to specify a key.
273 export BM_UPLOAD_SSHGPG_RECIPIENT=""
274
275 ##############################################################
00dfa77 2005-12-05 Alexis Sukrieh <sukria@backup-manager.org>
sukria authored
276 # The FTP method
277 #############################################################
e90e822 2006-01-05 Alexis Sukrieh <sukria@backup-manager.org>
sukria authored
278
a69eb90 Closes: #76, to be tested.
sukria authored
279 # Do you want to use FTP passive mode?
280 # This is mandatory for NATed/firewalled environments
281 export BM_UPLOAD_FTP_PASSIVE="true"
282
77124f8 Fixed bug #28: adding support for BM_UPLOAD_FTP_TTL.
sukria authored
283 # You can specify a time to live for archives uploaded with FTP
284 # This can let you use different ttl's locally and remotely
285 # By default, BM_ARCHIVE_TTL will be used.
286 export BM_UPLOAD_FTP_TTL=""
287
00dfa77 2005-12-05 Alexis Sukrieh <sukria@backup-manager.org>
sukria authored
288 # the user to use for the FTP connections/transfers
289 export BM_UPLOAD_FTP_USER=""
e90e822 2006-01-05 Alexis Sukrieh <sukria@backup-manager.org>
sukria authored
290
00dfa77 2005-12-05 Alexis Sukrieh <sukria@backup-manager.org>
sukria authored
291 # the FTP user's password
292 export BM_UPLOAD_FTP_PASSWORD=""
e90e822 2006-01-05 Alexis Sukrieh <sukria@backup-manager.org>
sukria authored
293
67a148d + backup-manager.conf.tpl (closes: #29)
sukria authored
294 # FTP specific remote hosts
00dfa77 2005-12-05 Alexis Sukrieh <sukria@backup-manager.org>
sukria authored
295 export BM_UPLOAD_FTP_HOSTS=""
e90e822 2006-01-05 Alexis Sukrieh <sukria@backup-manager.org>
sukria authored
296
00dfa77 2005-12-05 Alexis Sukrieh <sukria@backup-manager.org>
sukria authored
297 # purge archives on remote hosts before uploading?
026f318 Version 0.6.1
sukria authored
298 export BM_UPLOAD_FTP_PURGE="false"
e90e822 2006-01-05 Alexis Sukrieh <sukria@backup-manager.org>
sukria authored
299
00dfa77 2005-12-05 Alexis Sukrieh <sukria@backup-manager.org>
sukria authored
300 # destination for FTP uploads (overrides BM_UPLOAD_DESTINATION)
301 export BM_UPLOAD_FTP_DESTINATION=""
d29639d Initial revision
sukria authored
302
514c5c9 2006-03-29 Alexis Sukrieh <sukria@backup-manager.org>
sukria authored
303 ##############################################################
304 # The S3 method
305 #############################################################
306
307 # The Amazon S3 method requires that you secure an S3
308 # account. See http://aws.amazon.com
309
310 # The bucket to upload to. This bucket must be dedicated to backup-manager
311 export BM_UPLOAD_S3_DESTINATION=""
312
313 # the S3 access key provided to you
314 export BM_UPLOAD_S3_ACCESS_KEY=""
315
316 # the S3 secret key provided to you
317 export BM_UPLOAD_S3_SECRET_KEY=""
318
319 # purge archives on remote hosts before uploading?
320 export BM_UPLOAD_S3_PURGE="false"
d29639d Initial revision
sukria authored
321
0950922 - Changed configuration keys according to bug #10
jimmy authored
322 ##############################################################
00dfa77 2005-12-05 Alexis Sukrieh <sukria@backup-manager.org>
sukria authored
323 # The RSYNC method
0950922 - Changed configuration keys according to bug #10
jimmy authored
324 #############################################################
325
326 # Which directories should be backuped with rsync
b340bce 2005-12-05 Alexis Sukrieh <sukria@backup-manager.org>
sukria authored
327 export BM_UPLOAD_RSYNC_DIRECTORIES=""
0950922 - Changed configuration keys according to bug #10
jimmy authored
328
47614ef rsync is now an upload method.
jimmy authored
329 # Destination for rsync uploads (overrides BM_UPLOAD_DESTINATION)
330 export BM_UPLOAD_RSYNC_DESTINATION=""
331
0950922 - Changed configuration keys according to bug #10
jimmy authored
332 # The list of remote hosts, if you want to enable the upload
333 # system, just put some remote hosts here (fqdn or IPs)
47614ef rsync is now an upload method.
jimmy authored
334 # Leave it empty if you want to use the hosts that are defined in
335 # BM_UPLOAD_HOSTS
336 export BM_UPLOAD_RSYNC_HOSTS=""
337
338 # Do you want to dereference the files pointed by symlinks?
026f318 Version 0.6.1
sukria authored
339 # enter true or false (true can lead to huge archives, be careful).
340 export BM_UPLOAD_RSYNC_DUMPSYMLINKS="false"
0950922 - Changed configuration keys according to bug #10
jimmy authored
341
d29639d Initial revision
sukria authored
342 ##############################################################
8a97ae0 new confkeys
sukria authored
343 # Section "BURNING"
083cb8b 2005-12-09 Alexis Sukrieh,,, <set EMAIL_ADDRESS environment variable>
sukria authored
344 # - Automatic CDR/CDRW/DVDR burning
d29639d Initial revision
sukria authored
345 #############################################################
346
083cb8b 2005-12-09 Alexis Sukrieh,,, <set EMAIL_ADDRESS environment variable>
sukria authored
347 # the method of burning archives from the list :
6ba364f 2006-03-09 Alexis Sukrieh <sukria@backup-manager.org>
sukria authored
348 # - DVD : burn archives on a DVD medium
349 # (that doesn't need formatting, like DVD+RW).
083cb8b 2005-12-09 Alexis Sukrieh,,, <set EMAIL_ADDRESS environment variable>
sukria authored
350 #
6ba364f 2006-03-09 Alexis Sukrieh <sukria@backup-manager.org>
sukria authored
351 # - DVD-RW : blank the DVD medium and burn archives
352 # (recommanded for DVD-RW media).
083cb8b 2005-12-09 Alexis Sukrieh,,, <set EMAIL_ADDRESS environment variable>
sukria authored
353 #
6ba364f 2006-03-09 Alexis Sukrieh <sukria@backup-manager.org>
sukria authored
354 # - CDRW : blank the CDRW and burn the whole
355 # ARCHIVES_REPOSITORY or only
356 # the generated archives.
357 #
358 # - CDR : burn the whole ARCHIVES_REPOSITORY or
359 # only the generated archives.
360 # - none : disable the burning system
083cb8b 2005-12-09 Alexis Sukrieh,,, <set EMAIL_ADDRESS environment variable>
sukria authored
361
89e2bfe fixed some mistake in the default conffile
sukria authored
362 export BM_BURNING_METHOD="none"
d29639d Initial revision
sukria authored
363
674201f release 0.5.8b
sukria authored
364 # When the CD is burnt, it is possible to check every file's
365 # MD5 checksum to see if the CD is not corrupted.
89e2bfe fixed some mistake in the default conffile
sukria authored
366 export BM_BURNING_CHKMD5="false"
d29639d Initial revision
sukria authored
367
674201f release 0.5.8b
sukria authored
368 # The device to use for mounting the cdrom
d29639d Initial revision
sukria authored
369 export BM_BURNING_DEVICE="/dev/cdrom"
370
674201f release 0.5.8b
sukria authored
371 # You can force cdrecord to use a specific device
372 # Fill in the full path to the device to use or even
373 # e.g. BM_BURNING_DEVFORCED="/dev/cdrom"
374 # If none specified, the default cdrecord device will be used.
375 export BM_BURNING_DEVFORCED=""
e90e822 2006-01-05 Alexis Sukrieh <sukria@backup-manager.org>
sukria authored
376
79c645c 2005-11-08 Alexis Sukrieh <sukria@sukria.net>
sukria authored
377 # enter here the max size of your media
378 # (usal sizes are 4200 for DVD media and 700 or 800 for CDR media)
89e2bfe fixed some mistake in the default conffile
sukria authored
379 export BM_BURNING_MAXSIZE="650"
d29639d Initial revision
sukria authored
380
381
382 ##############################################################
383 # Advanced settings, use this with care.
384 #############################################################
385
7a80abf Now every backup methods are implemented in lib/backup-methods.sh
sukria authored
386 # Every output made can be sent to syslog
026f318 Version 0.6.1
sukria authored
387 # set this to "true" or "false"
388 export BM_LOGGER="true"
7a80abf Now every backup methods are implemented in lib/backup-methods.sh
sukria authored
389
390 # You can choose which facility to use
391 export BM_LOGGER_FACILITY="user"
392
d29639d Initial revision
sukria authored
393 # Enter here some shell script.
394 # It will be executed before the first action of backup-manager.
395 export BM_PRE_BACKUP_COMMAND=""
396
397 # Enter here some shell script.
398 # It will be executed after the last action of backup-manager.
399 export BM_POST_BACKUP_COMMAND=""
400
Something went wrong with that request. Please try again.