4 \section{The FileSet Resource}
5 \label{FileSetResource}
6 \index[general]{Resource!FileSet}
7 \index[general]{FileSet Resource}
9 The FileSet resource defines what files are to be included or excluded in a
10 backup job. A {\bf FileSet} resource is required for each backup Job. It
11 consists of a list of files or directories to be included, a list of files
12 or directories to be excluded and the various backup options such as
13 compression, encryption, and signatures that are to be applied to each
16 Any change to the list of the included files will cause Bacula to
17 automatically create a new FileSet (defined by the name and an MD5 checksum
18 of the Include/Exclude contents). Each time a new FileSet is created,
19 Bacula will ensure that the next backup is always a Full save.
21 \section{Character Sets}
22 \index[general]{Character Sets}
23 Bacula is designed to handle most character sets of the world,
24 US ASCII, German, French, Chinese, ... However, it does this by
25 encoding everything in UTF-8, and it expects all configuration files
26 (including those read on Win32 machines) to be in UTF-8 format.
27 UTF-8 is typically the default on Linux machines, but not on all
28 Unix machines, nor on Windows, so you must take some care to ensure
29 that your locale is set properly before starting Bacula.
30 On most modern Win32 machines, you can edit the conf files with {\bf
31 notebook} and choose output encoding UTF-8.
33 To ensure that Bacula configuration files can be correctly read including
34 foreign characters the {bf LANG} environment variable
35 must end in {\bf .UTF-8}. An full example is {\bf en\_US.UTF-8}. The
36 exact syntax may vary a bit from OS to OS, and exactly how you define
39 Bacula assumes that all filenames are in UTF-8 format on Linux and
40 Unix machines. On Win32 they are in Unicode (UTF-16), and will
41 be automatically converted to UTF-8 format.
48 \index[dir]{Directive!FileSet}
49 Start of the FileSet resource. One {\bf FileSet} resource must be
50 defined for each Backup job.
52 \item [Name = \lt{}name\gt{}]
54 \index[dir]{Directive!Name}
55 The name of the FileSet resource. This directive is required.
57 \item [Ignore FileSet Changes = \lt{}yes|no\gt{}]
58 \index[dir]{Ignore FileSet Changes}
59 \index[dir]{Directive!Ignore FileSet Changes}
60 Normally, if you modify the FileSet Include or Exclude lists,
61 the next backup will be forced to a Full so that Bacula can
62 guarantee that any additions or deletions are properly saved.
64 If this directive is set to {\bf yes}, any changes you make to the
65 FileSet Include or Exclude lists, will not force a Full during
68 The default is {\bf no}, in which case, if you change the Include or
69 Exclude, Bacula will force a Full backup to ensure that everything is
70 properly backed up. We strongly recommend against setting this
71 directive to yes, since doing so may cause you to have an incomplete
74 \item [Enable VSS = \lt{}yes|no\gt{}]
75 \index[dir]{Enable VSS}
76 \index[dir]{Directive!Enable VSS}
77 If this directive is set to {\bf yes} the File daemon will be notified
78 that the user wants to use a Volume Shadow Copy Service (VSS) backup
79 for this job. The default is {\bf yes}. This directive is effective
80 only for VSS enabled Win32 File daemons. It permits a consistent copy
81 of open files to be made for cooperating writer applications, and for
82 applications that are not VSS away, Bacula can at least copy open files.
83 For more information, please see the
84 \ilink{Windows}{VSS} chapter of this manual.
86 \item [Include \{ Options \{\lt{}file-options\gt{}\} ...;
87 \lt{}file-list\gt{} \} ]
88 \index[dir]{Include \{ [ Options \{\lt{}file-options\gt{}\} ...]
89 \lt{}file-list\gt{} \} }
90 \index[dir]{Directive!Include}
92 \item [Options \{ \lt{}file-options\gt{} \} ]
93 \index[dir]{Options \{ \lt{}file-options\gt{} \} }
95 \item [Exclude \{ \lt{}file-list\gt{} \}]
96 \index[dir]{Exclude \{ \lt{}file-list\gt{} \} }
97 \index[dir]{Directive!Exclude}
101 The Include resource must contain a list of directories and/or files to be
102 processed in the backup job. Normally, all files found in all
103 subdirectories of any directory in the Include File list will be backed up.
104 Note, see below for the definition of \lt{}file-list\gt{}.
105 The Include resource may also contain one or more Options resources that
106 specify options such as compression to be applied to all or any subset of
107 the files found when processing the file-list for backup. Please see
108 below for more details concerning Options resources.
110 There can be any number of {\bf Include} resources within the FileSet, each
111 having its own list of directories or files to be backed up and the backup
112 options defined by one or more Options resources. The {\bf file-list}
113 consists of one file or directory name per line. Directory names should be
114 specified without a trailing slash with Unix path notation.
116 Windows users, please take note to specify directories (even c:/...) in
117 Unix path notation. If you use Windows conventions, you will most likely
118 not be able to restore your files due to the fact that the Windows
119 path separator was defined as an escape character long before Windows
120 existed, and Bacula adheres to that convention (i.e. \\ means the next character
123 You should always specify a full path for every directory and file that you
124 list in the FileSet. In addition, on Windows machines, you should {\bf
125 always} prefix the directory or filename with the drive specification in
126 lower case (e.g. {\bf c:/xxx}) using Unix directory name separators
129 Bacula's default for processing directories is to recursively descend in
130 the directory saving all files and subdirectories. Bacula will not by
131 default cross filesystems (or mount points in Unix parlance). This means
132 that if you specify the root partition (e.g. {\bf /}), Bacula will save
133 only the root partition and not any of the other mounted filesystems.
134 Similarly on Windows systems, you must explicitly specify each of the
135 drives you want saved (e.g.
136 {\bf c:/} and {\bf d:/} ...). In addition, at least for Windows systems, you
137 will most likely want to enclose each specification within double quotes
138 particularly if the directory (or file) name contains spaces. The {\bf df}
139 command on Unix systems will show you which mount points you must specify to
140 save everything. See below for an example.
142 Take special care not to include a directory twice or Bacula will backup
143 the same files two times wasting a lot of space on your archive device.
144 Including a directory twice is very easy to do. For example:
151 Options { compression=GZIP }
156 on a Unix system where /usr is a subdirectory (rather than a mounted
157 filesystem) will cause /usr to be backed up twice. In this case, on Bacula
158 versions prior to 1.32f-5-09Mar04 due to a bug, you will not be able to
159 restore hard linked files that were backed up twice.
161 If you have used Bacula prior to version 1.36.3, you will note three things in
162 the new FileSet syntax:
165 \item There is no equal sign (=) after the Include and before the opening
166 brace (\{). The same is true for the Exclude.
167 \item Each directory (or filename) to be included or excluded is preceded by a {\bf File
168 =}. Previously they were simply listed on separate lines.
169 \item The options that previously appeared on the Include line now must be
170 specified within their own Options resource.
171 \item The Exclude resource does not accept Options.
172 \item When using wild-cards or regular expressions, directory names are
173 always terminated with a slash (/) and filenames have no trailing slash.
176 The Options resource is optional, but when specified, it will contain a
177 list of {\bf keyword=value} options to be applied to the file-list.
178 See below for the definition of file-list.
179 Multiple Options resources may be specified one after another. As the
180 files are found in the specified directories, the Options will applied to
181 the filenames to determine if and how the file should be backed up. The
182 wildcard and regular expression pattern matching parts of the
183 Options resources are checked in the order they are specified in the
184 FileSet until the first one that matches. Once one matches, the
185 compression and other flags within the Options specification will
186 apply to the pattern matched.
188 A key point is that in the absence of an Option or no other Option is
189 matched, every file is accepted for backing up. This means that if
190 you want to exclude something, you must explicitly specify an Option
191 with an {\bf exclude = yes} and some pattern matching.
193 Once Bacula determines that the Options resource matches the file under
194 consideration, that file will be saved without looking at any other Options
195 resources that may be present. This means that any wild cards must appear
196 before an Options resource without wild cards.
198 If for some reason, Bacula checks all the Options resources to a file under
199 consideration for backup, but there are no matches (generally because of wild
200 cards that don't match), Bacula as a default will then backup the file. This
201 is quite logical if you consider the case of no Options clause is specified,
202 where you want everything to be backed up, and it is important to keep in mind
203 when excluding as mentioned above.
205 However, one additional point is that in the case that no match was found,
206 Bacula will use the options found in the last Options resource. As a
207 consequence, if you want a particular set of "default" options, you should put
208 them in an Options resource after any other Options.
210 It is a good idea to put all your wild-card and regex expressions inside
211 double quotes to prevent conf file scanning problems.
213 This is perhaps a bit overwhelming, so there are a number of examples included
214 below to illustrate how this works.
216 The directives within an Options resource may be one of the following:
220 \item [compression=GZIP]
221 \index[dir]{compression}
222 \index[dir]{Directive!compression}
223 All files saved will be software compressed using the GNU ZIP
224 compression format. The compression is done on a file by file basis by
225 the File daemon. If there is a problem reading the tape in a single
226 record of a file, it will at most affect that file and none of the other
227 files on the tape. Normally this option is {\bf not} needed if you have
228 a modern tape drive as the drive will do its own compression. In fact,
229 if you specify software compression at the same time you have hardware
230 compression turned on, your files may actually take more space on the
233 Software compression is very important if you are writing your Volumes
234 to a file, and it can also be helpful if you have a fast computer but a
235 slow network, otherwise it is generally better to rely your tape drive's
236 hardware compression. As noted above, it is not generally a good idea
237 to do both software and hardware compression.
239 Specifying {\bf GZIP} uses the default compression level 6 (i.e. {\bf
240 GZIP} is identical to {\bf GZIP6}). If you want a different compression
241 level (1 through 9), you can specify it by appending the level number
242 with no intervening spaces to {\bf GZIP}. Thus {\bf compression=GZIP1}
243 would give minimum compression but the fastest algorithm, and {\bf
244 compression=GZIP9} would give the highest level of compression, but
245 requires more computation. According to the GZIP documentation,
246 compression levels greater than six generally give very little extra
247 compression and are rather CPU intensive.
249 \item [signature=SHA1]
250 \index[dir]{signature}
252 \index[dir]{Directive!signature}
253 An SHA1 signature will be computed for all The SHA1 algorithm is
254 purported to be some what slower than the MD5 algorithm, but at the same
255 time is significantly better from a cryptographic point of view (i.e.
256 much fewer collisions, much lower probability of being hacked.) It adds
257 four more bytes than the MD5 signature. We strongly recommend that
258 either this option or MD5 be specified as a default for all files.
259 Note, only one of the two options MD5 or SHA1 can be computed for any
262 \item [signature=MD5]
263 \index[dir]{signature}
265 \index[dir]{Directive!signature}
266 An MD5 signature will be computed for all files saved. Adding this
267 option generates about 5\% extra overhead for each file saved. In
268 addition to the additional CPU time, the MD5 signature adds 16 more
269 bytes per file to your catalog. We strongly recommend that this option
270 or the SHA1 option be specified as a default for all files.
272 \item [verify=\lt{}options\gt{}]
274 \index[dir]{Directive!verify}
275 The options letters specified are used when running a {\bf Verify
276 Level=Catalog} as well as the {\bf DiskToCatalog} level job. The options
277 letters may be any combination of the following:
285 compare the permission bits
288 compare the number of links
300 compare the access time
303 compare the modification time (st\_mtime)
306 compare the change time (st\_ctime)
309 report file size decreases
312 compare the MD5 signature
315 compare the SHA1 signature
318 A useful set of general options on the {\bf Level=Catalog} or {\bf
319 Level=DiskToCatalog} verify is {\bf pins5} i.e. compare permission bits,
320 inodes, number of links, size, and MD5 changes.
324 \index[dir]{Directive!onefs}
325 If set to {\bf yes} (the default), {\bf Bacula} will remain on a single
326 file system. That is it will not backup file systems that are mounted
327 on a subdirectory. If you are using a *nix system, you may not even be
328 aware that there are several different filesystems as they are often
329 automatically mounted by the OS (e.g. /dev, /net, /sys, /proc, ...).
330 With Bacula 1.38.0 or later, it will inform you when it decides not to
331 traverse into another filesystem. This can be very useful if you forgot
332 to backup a particular partition. An example of the informational
333 message in the job report is:
337 rufus-fd: /misc is a different filesystem. Will not descend from / into /misc
338 rufus-fd: /net is a different filesystem. Will not descend from / into /net
339 rufus-fd: /var/lib/nfs/rpc_pipefs is a different filesystem. Will not descend from /var/lib/nfs into /var/lib/nfs/rpc_pipefs
340 rufus-fd: /selinux is a different filesystem. Will not descend from / into /selinux
341 rufus-fd: /sys is a different filesystem. Will not descend from / into /sys
342 rufus-fd: /dev is a different filesystem. Will not descend from / into /dev
343 rufus-fd: /home is a different filesystem. Will not descend from / into /home
347 Note: in previous versions of Bacula, the above message was of the form:
351 Filesystem change prohibited. Will not descend into /misc
355 If you wish to backup multiple filesystems, you can explicitly
356 list each filesystem you want saved. Otherwise, if you set the onefs option
357 to {\bf no}, Bacula will backup all mounted file systems (i.e. traverse mount
358 points) that are found within the {\bf FileSet}. Thus if you have NFS or
359 Samba file systems mounted on a directory listed in your FileSet, they will
360 also be backed up. Normally, it is preferable to set {\bf onefs=yes} and to
361 explicitly name each filesystem you want backed up. Explicitly naming the
362 filesystems you want backed up avoids the possibility of getting into a
363 infinite loop recursing filesystems. Another possibility is to
364 use {\bf onefs=no} and to set {\bf fstype=ext2, ...}.
365 See the example below for more details.
367 If you think that Bacula should be backing up a particular directory
368 and it is not, and you have {\bf onefs=no} set, before you complain,
378 where you replace {\bf filesystem} with the one in question. If the
379 {\bf Device:} number is different for / and for your filesystem, then they
380 are on different filesystems. E.g.
385 Size: 4096 Blocks: 16 IO Block: 4096 directory
386 Device: 302h/770d Inode: 2 Links: 26
387 Access: (0755/drwxr-xr-x) Uid: ( 0/ root) Gid: ( 0/ root)
388 Access: 2005-11-10 12:28:01.000000000 +0100
389 Modify: 2005-09-27 17:52:32.000000000 +0200
390 Change: 2005-09-27 17:52:32.000000000 +0200
394 Size: 4096 Blocks: 16 IO Block: 4096 directory
395 Device: 308h/776d Inode: 2 Links: 7
396 Access: (0755/drwxr-xr-x) Uid: ( 0/ root) Gid: ( 0/ root)
397 Access: 2005-11-10 12:28:02.000000000 +0100
398 Modify: 2005-11-06 12:36:48.000000000 +0100
399 Change: 2005-11-06 12:36:48.000000000 +0100
403 Also be aware that even if you include {\bf /home} in your list
404 of files to backup, as you most likely should, you will get the
405 informational message that "/home is a different filesystem" when
406 Bacula is processing the {\bf /} directory. This message does not
407 indicate an error. This message means that while examining the
408 {\bf File =} referred to in the second part of the message, Bacula will
409 not descend into the directory mentioned in the first part of the message.
410 However, it is possible that the separate filesystem will be backed up
411 despite the message. For example, consider the following FileSet:
420 where {\bf /var} is a separate filesystem. In this example, you will get a
421 message saying that Bacula will not decend from {\bf /} into {\bf /var}. But
422 it is important to realise that Bacula will descend into {\bf /var} from the
423 second File directive shown above. In effect, the warning is bogus,
424 but it is supplied to alert you to possible omissions from your FileSet. In
425 this example, {\bf /var} will be backed up. If you changed the FileSet such
426 that it did not specify {\bf /var}, then {\bf /var} will not be backed up.
432 \item [portable=yes|no]
433 \index[dir]{portable}
434 \index[dir]{Directive!portable}
435 If set to {\bf yes} (default is {\bf no}), the Bacula File daemon will
436 backup Win32 files in a portable format, but not all Win32 file
437 attributes will be saved and restored. By default, this option is set
438 to {\bf no}, which means that on Win32 systems, the data will be backed
439 up using Windows API calls and on WinNT/2K/XP, all the security and
440 ownership attributes will be properly backed up (and restored). However
441 this format is not portable to other systems -- e.g. Unix, Win95/98/Me.
442 When backing up Unix systems, this option is ignored, and unless you
443 have a specific need to have portable backups, we recommend accept the
444 default ({\bf no}) so that the maximum information concerning your files
447 \item [recurse=yes|no]
449 \index[dir]{Directive!recurse}
450 If set to {\bf yes} (the default), Bacula will recurse (or descend) into
451 all subdirectories found unless the directory is explicitly excluded
452 using an {\bf exclude} definition. If you set {\bf recurse=no}, Bacula
453 will save the subdirectory entries, but not descend into the
454 subdirectories, and thus will not save the files or directories
455 contained in the subdirectories. Normally, you will want the default
458 \item [sparse=yes|no]
460 \index[dir]{Directive!sparse}
461 Enable special code that checks for sparse files such as created by
462 ndbm. The default is {\bf no}, so no checks are made for sparse files.
463 You may specify {\bf sparse=yes} even on files that are not sparse file.
464 No harm will be done, but there will be a small additional overhead to
465 check for buffers of all zero, and a small additional amount of space on
466 the output archive will be used to save the seek address of each
467 non-zero record read.
469 {\bf Restrictions:} Bacula reads files in 32K buffers. If the whole
470 buffer is zero, it will be treated as a sparse block and not written to
471 tape. However, if any part of the buffer is non-zero, the whole buffer
472 will be written to tape, possibly including some disk sectors (generally
473 4098 bytes) that are all zero. As a consequence, Bacula's detection of
474 sparse blocks is in 32K increments rather than the system block size.
475 If anyone considers this to be a real problem, please send in a request
476 for change with the reason.
478 If you are not familiar with sparse files, an example is say a file
479 where you wrote 512 bytes at address zero, then 512 bytes at address 1
480 million. The operating system will allocate only two blocks, and the
481 empty space or hole will have nothing allocated. However, when you read
482 the sparse file and read the addresses where nothing was written, the OS
483 will return all zeros as if the space were allocated, and if you backup
484 such a file, a lot of space will be used to write zeros to the volume.
485 Worse yet, when you restore the file, all the previously empty space
486 will now be allocated using much more disk space. By turning on the
487 {\bf sparse} option, Bacula will specifically look for empty space in
488 the file, and any empty space will not be written to the Volume, nor
489 will it be restored. The price to pay for this is that Bacula must
490 search each block it reads before writing it. On a slow system, this
491 may be important. If you suspect you have sparse files, you should
492 benchmark the difference or set sparse for only those files that are
496 \item [readfifo=yes|no]
497 \index[dir]{readfifo}
498 \index[dir]{Directive!readfifo}
499 If enabled, tells the Client to read the data on a backup and write the
500 data on a restore to any FIFO (pipe) that is explicitly mentioned in the
501 FileSet. In this case, you must have a program already running that
502 writes into the FIFO for a backup or reads from the FIFO on a restore.
503 This can be accomplished with the {\bf RunBeforeJob} directive. If this
504 is not the case, Bacula will hang indefinitely on reading/writing the
505 FIFO. When this is not enabled (default), the Client simply saves the
506 directory entry for the FIFO.
508 Unfortunately, when Bacula runs a RunBeforeJob, it waits until that
509 script terminates, and if the script accesses the FIFO to write
510 into the it, the Bacula job will block and everything will stall.
511 However, Vladimir Stavrinov as supplied tip that allows this feature
512 to work correctly. He simply adds the following to the beginning
513 of the RunBeforeJob script:
519 \item [noatime=yes|no]
521 \index[dir]{Directive!noatime}
522 If enabled, and if your Operating System supports the O\_NOATIME file
523 open flag, Bacula will open all files to be backed up with this option.
524 It makes it possible to read a file without updating the inode atime
525 (and also without the inode ctime update which happens if you try to set
526 the atime back to its previous value). It also prevents a race
527 condition when two programs are reading the same file, but only one does
528 not want to change the atime. It's most useful for backup programs and
529 file integrity checkers (and bacula can fit on both categories).
531 This option is particularly useful for sites where users are sensitive
532 to their MailBox file access time. It replaces both the {\bf keepatime}
533 option without the inconveniences of that option (see below).
535 If your Operating System does not support this option, it will be
536 silently ignored by Bacula.
539 \item [mtimeonly=yes|no]
540 \index[dir]{mtimeonly}
541 \index[dir]{Directive!mtimeonly}
542 If enabled, tells the Client that the selection of files during
543 Incremental and Differential backups should based only on the st\_mtime
544 value in the stat() packet. The default is {\bf no} which means that
545 the selection of files to be backed up will be based on both the
546 st\_mtime and the st\_ctime values. In general, it is not recommended
549 \item [keepatime=yes|no]
550 \index[dir]{keepatime}
551 \index[dir]{Directive!keepatime}
552 The default is {\bf no}. When enabled, Bacula will reset the st\_atime
553 (access time) field of files that it backs up to their value prior to
554 the backup. This option is not generally recommended as there are very
555 few programs that use st\_atime, and the backup overhead is increased
556 because of the additional system call necessary to reset the times.
557 However, for some files, such as mailboxes, when Bacula backs up the
558 file, the user will notice that someone (Bacula) has accessed the
559 file. In this, case keepatime can be useful.
560 (I'm not sure this works on Win32).
562 Note, if you use this feature, when Bacula resets the access time, the
563 change time (st\_ctime) will automatically be modified by the system,
564 so on the next incremental job, the file will be backed up even if
565 it has not changed. As a consequence, you will probably also want
566 to use {\bf mtimeonly = yes} as well as keepatime (thanks to
567 Rudolf Cejka for this tip).
569 \item [checkfilechanges=yes|no]
570 \index[dir]{checkfilechanges}
571 \index[dir]{Directive!checkfilechanges}
572 On versions 2.0.4 or greater,
573 if enabled, the Client will checks size, age of each file after
574 their backup to see if they have changed during backup. If time
575 or size mismatch, an error will raise.
578 zog-fd: Client1.2007-03-31_09.46.21 Error: /tmp/test mtime changed during backup.
581 In general, it is recommended to use this option.
583 \item [hardlinks=yes|no]
584 \index[dir]{hardlinks}
585 \index[dir]{Directive!hardlinks}
586 When enabled (default), this directive will cause hard links to be
587 backed up. However, the File daemon keeps track of hard linked files and
588 will backup the data only once. The process of keeping track of the
589 hard links can be quite expensive if you have lots of them (tens of
590 thousands or more). This doesn't occur on normal Unix systems, but if
591 you use a program like BackupPC, it can create hundreds of thousands, or
592 even millions of hard links. Backups become very long and the File daemon
593 will consume a lot of CPU power checking hard links. In such a case,
594 set {\bf hardlinks=no} and hard links will not be backed up. Note, using
595 this option will most likely backup more data and on a restore the file
596 system will not be restored identically to the original.
598 \item [wild=\lt{}string\gt{}]
600 \index[dir]{Directive!wild}
601 Specifies a wild-card string to be applied to the filenames and
602 directory names. Note, if {\bf Exclude} is not enabled, the wild-card
603 will select which files are to be included. If {\bf Exclude=yes} is
604 specified, the wild-card will select which files are to be excluded.
605 Multiple wild-card directives may be specified, and they will be applied
606 in turn until the first one that matches. Note, if you exclude a
607 directory, no files or directories below it will be matched.
609 You may want to test your expressions prior to running your
610 backup by using the bwild program. Please see the
611 \ilink{Utilities}{bwild} chapter of this manual for
612 more. You can also test your full FileSet definition by using
613 the \ilink{estimate}{estimate} command in the Console
614 chapter of this manual.
615 It is recommended to enclose the string in double quotes.
617 \item [wilddir=\lt{}string\gt{}]
619 \index[dir]{Directive!wilddir}
620 Specifies a wild-card string to be applied to directory names only. No
621 filenames will be matched by this directive. Note, if {\bf Exclude} is
622 not enabled, the wild-card will select directories files are to be
623 included. If {\bf Exclude=yes} is specified, the wild-card will select
624 which files are to be excluded. Multiple wild-card directives may be
625 specified, and they will be applied in turn until the first one that
626 matches. Note, if you exclude a directory, no files or directories
627 below it will be matched.
629 It is recommended to enclose the string in double quotes.
631 You may want to test your expressions prior to running your
632 backup by using the bwild program. Please see the
633 \ilink{Utilities}{bwild} chapter of this manual for
634 more. You can also test your full FileSet definition by using
635 the \ilink{estimate}{estimate} command in the Console
636 chapter of this manual.
637 An example of excluding with the WildDir option on Win32 machines is
640 \item [wildfile=\lt{}string\gt{}]
641 \index[dir]{wildfile}
642 \index[dir]{Directive!wildfile}
643 Specifies a wild-card string to be applied to non-directories. That
644 is no directory entries will be matched by this directive.
645 However, note that the match is done against the full path and filename,
646 so your wild-card string must take into account that filenames
647 are preceded by the full path.
649 is not enabled, the wild-card will select which files are to be
650 included. If {\bf Exclude=yes} is specified, the wild-card will select
651 which files are to be excluded. Multiple wild-card directives may be
652 specified, and they will be applied in turn until the first one that
655 It is recommended to enclose the string in double quotes.
657 You may want to test your expressions prior to running your
658 backup by using the bwild program. Please see the
659 \ilink{Utilities}{bwild} chapter of this manual for
660 more. You can also test your full FileSet definition by using
661 the \ilink{estimate}{estimate} command in the Console
662 chapter of this manual.
663 An example of excluding with the WildFile option on Win32 machines is
667 \item [regex=\lt{}string\gt{}]
669 \index[dir]{Directive!regex}
670 Specifies a POSIX extended regular expression to be applied to the
671 filenames and directory names, which include the full path. If {\bf
672 Exclude} is not enabled, the regex will select which files are to be
673 included. If {\bf Exclude=yes} is specified, the regex will select
674 which files are to be excluded. Multiple regex directives may be
675 specified within an Options resource, and they will be applied in turn
676 until the first one that matches. Note, if you exclude a directory, no
677 files or directories below it will be matched.
679 It is recommended to enclose the string in double quotes.
681 The regex libraries differ from one operating system to
682 another, and in addition, regular expressions are complicated,
683 so you may want to test your expressions prior to running your
684 backup by using the bregex program. Please see the
685 \ilink{Utilities}{bwild} chapter of this manual for
686 more. You can also test your full FileSet definition by using
687 the \ilink{estimate}{estimate} command in the Console
688 chapter of this manual.
691 \item [regexfile=\lt{}string\gt{}]
692 \index[dir]{regexfile}
693 \index[dir]{Directive!regexfile}
694 Specifies a POSIX extended regular expression to be applied to
695 non-directories. No directories will be matched by this directive.
696 However, note that the match is done against the full path and
697 filename, so your regex string must take into account that filenames
698 are preceded by the full path.
699 If {\bf Exclude} is not enabled, the regex will select which files are
700 to be included. If {\bf Exclude=yes} is specified, the regex will
701 select which files are to be excluded. Multiple regex directives may be
702 specified, and they will be applied in turn until the first one that
705 It is recommended to enclose the string in double quotes.
707 The regex libraries differ from one operating system to
708 another, and in addition, regular expressions are complicated,
709 so you may want to test your expressions prior to running your
710 backup by using the bregex program. Please see the
711 \ilink{Utilities}{bregex} chapter of this manual for
715 \item [regexdir=\lt{}string\gt{}]
716 \index[dir]{regexdir}
717 \index[dir]{Directive!regexdir}
718 Specifies a POSIX extended regular expression to be applied to directory
719 names only. No filenames will be matched by this directive. Note, if
720 {\bf Exclude} is not enabled, the regex will select directories
721 files are to be included. If {\bf Exclude=yes} is specified, the
722 regex will select which files are to be excluded. Multiple
723 regex directives may be specified, and they will be applied in turn
724 until the first one that matches. Note, if you exclude a directory, no
725 files or directories below it will be matched.
727 It is recommended to enclose the string in double quotes.
729 The regex libraries differ from one operating system to
730 another, and in addition, regular expressions are complicated,
731 so you may want to test your expressions prior to running your
732 backup by using the bregex program. Please see the
733 \ilink{Utilities}{bregex} chapter of this manual for
737 \item [exclude=yes|no]
739 \index[dir]{Directive!exclude}
740 The default is {\bf no}. When enabled, any files matched within the
741 Options will be excluded from the backup.
744 \item [aclsupport=yes|no]
745 \index[dir]{aclsupport}
746 \index[dir]{Directive!aclsupport}
747 The default is {\bf no}. If this option is set to yes, and you have the
748 POSIX {\bf libacl} installed on your system, Bacula will backup the file
749 and directory UNIX Access Control Lists (ACL) as defined in IEEE Std
750 1003.1e draft 17 and "POSIX.1e" (abandoned). This feature is
751 available on UNIX only and depends on the ACL library. Bacula is
752 automatically compiled with ACL support if the {\bf libacl} library is
753 installed on your system (shown in config.out). While restoring the
754 files Bacula will try to restore the ACLs, if there is no ACL support
755 available on the system, Bacula restores the files and directories but
756 not the ACL information. Please note, if you backup an EXT3 or XFS
757 filesystem with ACLs, then you restore them to a different filesystem
758 (perhaps reiserfs) that does not have ACLs, the ACLs will be ignored.
760 \item [ignore case=yes|no]
761 \index[dir]{ignore case}
762 \index[dir]{Directive!ignore case}
763 The default is {\bf no}. On Windows systems, you will almost surely
764 want to set this to {\bf yes}. When this directive is set to {\bf yes}
765 all the case of character will be ignored in wild-card and regex
766 comparisons. That is an uppercase A will match a lowercase a.
768 \item [fstype=filesystem-type]
770 \index[dir]{Directive!fstype}
771 This option allows you to select files and directories by the
772 filesystem type. The permitted filesystem-type names are:
774 ext2, jfs, ntfs, proc, reiserfs, xfs, usbdevfs, sysfs, smbfs,
775 iso9660. For ext3 systems, use ext2.
777 You may have multiple Fstype directives, and thus permit matching
778 of multiple filesystem types within a single Options resource. If
779 the type specified on the fstype directive does not match the
780 filesystem for a particular directive, that directory will not be
781 backed up. This directive can be used to prevent backing up
782 non-local filesystems. Normally, when you use this directive, you
783 would also set {\bf onefs=no} so that Bacula will traverse filesystems.
785 This option is not implemented in Win32 systems.
788 \item [hfsplussupport=yes|no]
789 \index[dir]{hfsplussupport}
790 \index[dir]{Directive!hfsplussupport}
791 This option allows you to turn on support for Mac OSX HFS plus
794 \item [strippath=\lt{}integer\gt{}]
795 \index[dir]{strippath}
796 \index[dir]{Directive!strippath}
797 This option will cause {\bf integer} paths to be stripped from
798 the front of the full path/filename being backed up. This can
799 be useful if you are migrating data from another vendor or if
800 you have taken a snapshot into some subdirectory. This directive
801 can cause your filenames to be overlayed with regular backup data,
802 so should be used only by experts and with great care.
805 {\bf \lt{}file-list\gt{}} is a list of directory and/or filename names
806 specified with a {\bf File =} directive. To include names containing spaces,
807 enclose the name between double-quotes. Wild-cards are not interpreted
808 in file-lists. They can only be specified in Options resources.
810 There are a number of special cases when specifying directories and files in a
811 {\bf file-list}. They are:
814 \item Any name preceded by an at-sign (@) is assumed to be the name of a
815 file, which contains a list of files each preceded by a "File =". The
816 named file is read once when the configuration file is parsed during the
817 Director startup. Note, that the file is read on the Director's machine
818 and not on the Client's. In fact, the @filename can appear anywhere
819 within the conf file where a token would be read, and the contents of
820 the named file will be logically inserted in the place of the @filename.
821 What must be in the file depends on the location the @filename is
822 specified in the conf file. For example:
827 Options { compression=GZIP }
828 @/home/files/my-files
833 \item Any name beginning with a vertical bar (|) is assumed to be the name of
834 a program. This program will be executed on the Director's machine at
835 the time the Job starts (not when the Director reads the configuration
836 file), and any output from that program will be assumed to be a list of
837 files or directories, one per line, to be included.
839 This allows you to have a job that, for example, includes all the local
840 partitions even if you change the partitioning by adding a disk. The
841 examples below show you how to do this. However, please note two
843 1. if you want the local filesystems, you probably should be
844 using the new {\bf fstype} directive, which was added in version 1.36.3
845 and set {\bf onefs=no}.
848 2. the exact syntax of the command needed in the examples below is very
849 system dependent. For example, on recent Linux systems, you may need to
850 add the -P option, on FreeBSD systems, the options will be different as
853 In general, you will need to prefix your command or commands with a {\bf
854 sh -c} so that they are invoked by a shell. This will not be the case
855 if you are invoking a script as in the second example below. Also, you
856 must take care to escape (precede with a \textbackslash{}) wild-cards,
857 shell character, and to ensure that any spaces in your command are
858 escaped as well. If you use a single quotes (') within a double quote
859 ("), Bacula will treat everything between the single quotes as one field
860 so it will not be necessary to escape the spaces. In general, getting
861 all the quotes and escapes correct is a real pain as you can see by the
862 next example. As a consequence, it is often easier to put everything in
863 a file and simply use the file name within Bacula. In that case the
864 {\bf sh -c} will not be necessary providing the first line of the file
873 Options { signature = SHA1 }
874 File = "|sh -c 'df -l | grep \"^/dev/hd[ab]\" | grep -v \".*/tmp\" \
875 | awk \"{print \\$6}\"'"
880 will produce a list of all the local partitions on a Red Hat Linux system.
881 Note, the above line was split, but should normally be written on one line.
882 Quoting is a real problem because you must quote for Bacula which consists of
883 preceding every \textbackslash{} and every " with a \textbackslash{}, and
884 you must also quote for the shell command. In the end, it is probably easier
885 just to execute a small file with:
894 File = "|my_partitions"
899 where my\_partitions has:
904 df -l | grep "^/dev/hd[ab]" | grep -v ".*/tmp" \
909 If the vertical bar (|) in front of my\_partitions is preceded by a
910 backslash as in \textbackslash{}|, the program will be executed on the
911 Client's machine instead of on the Director's machine.
912 Please note that if the filename is given within quotes, you
913 will need to use two slashes. An example, provided by John Donagher,
914 that backs up all the local UFS partitions on a remote system is:
919 Name = "All local partitions"
921 Options { signature=SHA1; onefs=yes; }
922 File = "\\|bash -c \"df -klF ufs | tail +2 | awk '{print \$6}'\""
928 The above requires two backslash characters after the double quote (one
929 preserves the next one). If you are a Linux user, just change the {\bf ufs}
930 to {\bf ext3} (or your preferred filesystem type), and you will be in
933 If you know what filesystems you have mounted on your system, e.g.
934 for Red Hat Linux normally only ext2 and ext3, you can backup
935 all local filesystems using something like:
941 Options { signature = SHA1; onfs=no; fstype=ext2 }
948 \item Any file-list item preceded by a less-than sign (\lt{}) will be taken
949 to be a file. This file will be read on the Director's machine (see
950 below for doing it on the Client machine) at the time
951 the Job starts, and the data will be assumed to be a list of directories or
952 files, one per line, to be included. The names should start in column 1 and
953 should not be quoted even if they contain spaces. This feature allows you to
954 modify the external file and change what will be saved without stopping and
955 restarting Bacula as would be necessary if using the @ modifier noted above.
961 Options { signature = SHA1 }
962 File = "</home/files/local-filelist"
967 If you precede the less-than sign (\lt{}) with a backslash as in
968 \textbackslash{}\lt{}, the file-list will be read on the Client machine
969 instead of on the Director's machine. Please note that if the filename
970 is given within quotes, you will need to use two slashes.
975 Options { signature = SHA1 }
976 File = "\\</home/xxx/filelist-on-client"
981 \item If you explicitly specify a block device such as {\bf /dev/hda1}, then
982 Bacula (starting with version 1.28) will assume that this is a raw partition
983 to be backed up. In this case, you are strongly urged to specify a {\bf
984 sparse=yes} include option, otherwise, you will save the whole partition
985 rather than just the actual data that the partition contains. For example:
990 Options { signature=MD5; sparse=yes }
996 will backup the data in device /dev/hd6.
998 Ludovic Strappazon has pointed out that this feature can be used to backup a
999 full Microsoft Windows disk. Simply boot into the system using a Linux Rescue
1000 disk, then load a statically linked Bacula as described in the
1001 \ilink{ Disaster Recovery Using Bacula}{RescueChapter} chapter of
1002 this manual. Then save the whole disk partition. In the case of a disaster,
1003 you can then restore the desired partition by again booting with the rescue
1004 disk and doing a restore of the partition.
1005 \item If you explicitly specify a FIFO device name (created with mkfifo), and
1006 you add the option {\bf readfifo=yes} as an option, Bacula will read the FIFO
1007 and back its data up to the Volume. For example:
1016 File = /home/abc/fifo
1021 if {\bf /home/abc/fifo} is a fifo device, Bacula will open the fifo,
1022 read it, and store all data thus obtained on the Volume. Please note,
1023 you must have a process on the system that is writing into the fifo, or
1024 Bacula will hang, and after one minute of waiting, Bacula will give up
1025 and go on to the next file. The data read can be anything since Bacula
1026 treats it as a stream.
1028 This feature can be an excellent way to do a "hot" backup of a very
1029 large database. You can use the {\bf RunBeforeJob} to create the fifo
1030 and to start a program that dynamically reads your database and writes
1031 it to the fifo. Bacula will then write it to the Volume. Be sure to
1032 read the \ilink{readfifo section}{readfifo} that gives a
1033 tip to ensure that the RunBeforeJob does not block Bacula.
1035 During the restore operation, the inverse is true, after Bacula creates
1036 the fifo if there was any data stored with it (no need to explicitly
1037 list it or add any options), that data will be written back to the fifo.
1038 As a consequence, if any such FIFOs exist in the fileset to be restored,
1039 you must ensure that there is a reader program or Bacula will block, and
1040 after one minute, Bacula will time out the write to the fifo and move on
1043 \item A file-list may not contain wild-cards. Use directives in the
1044 Options resource if you wish to specify wild-cards or regular expression
1048 \section{FileSet Examples}
1049 \index[general]{Examples!FileSet }
1050 \index[general]{FileSet Examples}
1052 The following is an example of a valid FileSet resource definition. Note,
1053 the first Include pulls in the contents of the file {\bf /etc/backup.list}
1054 when Bacula is started (i.e. the @), and that file must have each filename
1055 to be backed up preceded by a {\bf File =} and on a separate line.
1076 File = /usr/lib/another_file
1082 In the above example, all the files contained in /etc/backup.list will
1083 be compressed with GZIP compression, an SHA1 signature will be computed on the
1084 file's contents (its data), and sparse file handling will apply.
1086 The two directories /root/myfile and /usr/lib/another\_file will also be saved
1087 without any options, but all files in those directories with the extensions
1088 {\bf .o} and {\bf .exe} will be excluded.
1090 Let's say that you now want to exclude the directory /tmp. The simplest way
1091 to do so is to add an exclude directive that lists /tmp. The example
1092 above would then become:
1113 File = /usr/lib/another_file
1123 You can add wild-cards to the File directives listed in the Exclude
1124 directory, but you need to take care because if you exclude a directory,
1125 it and all files and directories below it will also be excluded.
1127 Now lets take a slight variation on the above and suppose
1128 you want to save all your whole filesystem except {\bf /tmp}.
1129 The problem that comes up is that Bacula will not normally
1130 cross from one filesystem to another.
1131 Doing a {\bf df} command, you get the following output:
1136 Filesystem 1k-blocks Used Available Use% Mounted on
1137 /dev/hda5 5044156 439232 4348692 10% /
1138 /dev/hda1 62193 4935 54047 9% /boot
1139 /dev/hda9 20161172 5524660 13612372 29% /home
1140 /dev/hda2 62217 6843 52161 12% /rescue
1141 /dev/hda8 5044156 42548 4745376 1% /tmp
1142 /dev/hda6 5044156 2613132 2174792 55% /usr
1143 none 127708 0 127708 0% /dev/shm
1144 //minimatou/c$ 14099200 9895424 4203776 71% /mnt/mmatou
1145 lmatou:/ 1554264 215884 1258056 15% /mnt/matou
1146 lmatou:/home 2478140 1589952 760072 68% /mnt/matou/home
1147 lmatou:/usr 1981000 1199960 678628 64% /mnt/matou/usr
1148 lpmatou:/ 995116 484112 459596 52% /mnt/pmatou
1149 lpmatou:/home 19222656 2787880 15458228 16% /mnt/pmatou/home
1150 lpmatou:/usr 2478140 2038764 311260 87% /mnt/pmatou/usr
1151 deuter:/ 4806936 97684 4465064 3% /mnt/deuter
1152 deuter:/home 4806904 280100 4282620 7% /mnt/deuter/home
1153 deuter:/files 44133352 27652876 14238608 67% /mnt/deuter/files
1157 And we see that there are a number of separate filesystems (/ /boot
1158 /home /rescue /tmp and /usr not to mention mounted systems).
1159 If you specify only {\bf /} in your Include list, Bacula will only save the
1160 Filesystem {\bf /dev/hda5}. To save all filesystems except {\bf /tmp} with
1161 out including any of the Samba or NFS mounted systems, and explicitly
1162 excluding a /tmp, /proc, .journal, and .autofsck, which you will not want to
1163 be saved and restored, you can use the following:
1168 Name = Include_example
1173 wildfile = "/.journal"
1174 wildfile = "/.autofsck"
1187 Since /tmp is on its own filesystem and it was not explicitly named in the
1188 Include list, it is not really needed in the exclude list. It is better to
1189 list it in the Exclude list for clarity, and in case the disks are changed so
1190 that it is no longer in its own partition.
1192 Now, lets assume you only want to backup .Z and .gz files and nothing
1193 else. This is a bit trickier because Bacula by default will select
1194 everything to backup, so we must exclude everything but .Z and .gz files.
1195 If we take the first example above and make the obvious modifications
1196 to it, we might come up with a FileSet that looks like this:
1202 Include { !!!!!!!!!!!!
1204 wildfile = "*.Z" example
1205 wildfile = "*.gz" doesn't
1214 The *.Z and *.gz files will indeed be backed up, but all other files
1215 that are not matched by the Options directives will automatically
1216 be backed up too (i.e. that is the default rule).
1218 To accomplish what we want, we must explicitly exclude all other files.
1219 We do this with the following:
1240 The "trick" here was to add a RegexFile expression that matches
1241 all files. It does not match directory names, so all directories in
1242 /myfile will be backed up (the directory entry) and any *.Z and *.gz
1243 files contained in them. If you know that certain directories do
1244 not contain any *.Z or *.gz files and you do not want the directory
1245 entries backed up, you will need to explicitly exclude those directories.
1246 Backing up a directory entries is not very expensive.
1248 Bacula uses the system regex library and some of them are
1249 different on different OSes. The above has been reported not to work
1250 on FreeBSD. This can be tested by using the {\bf estimate job=job-name
1251 listing} command in the console and adapting the RegexFile expression
1252 appropriately. In a future version of Bacula, we will supply our own
1253 Regex code to avoid such system dependencies.
1255 Please be aware that allowing Bacula to traverse or change file systems can be
1256 {\bf very} dangerous. For example, with the following:
1261 Name = "Bad example"
1263 Options { onefs=no }
1270 you will be backing up an NFS mounted partition ({\bf /mnt/matou}), and since
1271 {\bf onefs} is set to {\bf no}, Bacula will traverse file systems. Now if {\bf
1272 /mnt/matou} has the current machine's file systems mounted, as is often the
1273 case, you will get yourself into a recursive loop and the backup will never
1276 As a final example, let's say that you have only one or two
1277 subdirectories of /home that you want to backup. For example,
1278 you want to backup only subdirectories beginning with the letter
1279 a and the letter b -- i.e. /home/a* and /home/b*. Now, you might first
1287 wilddir = "/home/a*"
1288 wilddir = "/home/b*"
1296 The problem is that the above will include everything in /home. To get
1297 things to work correctly, you need to start with the idea of exclusion
1298 instead of inclusion. So, you could simply exclude all directories
1299 except the two you want to use:
1306 RegexDir = "^/home/[c-z]"
1315 And assuming that all subdirectories start with a lowercase letter, this
1318 An alternative would be to include the two subdirectories desired and
1319 exclude everything else:
1326 wilddir = "/home/a*"
1327 wilddir = "/home/b*"
1339 \section{Backing up Raw Partitions}
1340 \index[general]{Backing up!Partitions }
1341 \index[general]{Backing up Raw Partitions }
1343 The following FileSet definition will backup a raw partition:
1348 Name = "RawPartition"
1350 Options { sparse=yes }
1357 While backing up and restoring a raw partition, you should ensure that no
1358 other process including the system is writing to that partition. As a
1359 precaution, you are strongly urged to ensure that the raw partition is not
1360 mounted or is mounted read-only. If necessary, this can be done using the {\bf
1361 RunBeforeJob} directive.
1364 \section{Excluding Files and Directories}
1365 \index[general]{Directories!Excluding Files and }
1366 \index[general]{Excluding Files and Directories }
1368 You may also include full filenames or directory names in addition to using
1369 wild-cards and {\bf Exclude=yes} in the Options resource as specified above by
1370 simply including the files to be excluded in an Exclude resource within the
1371 FileSet. For example:
1376 Name = Exclusion_example
1398 \section{Windows FileSets}
1399 \index[general]{Windows FileSets }
1400 \index[general]{FileSets!Windows }
1401 If you are entering Windows file names, the directory path may be preceded by
1402 the drive and a colon (as in c:). However, the path separators must be
1403 specified in Unix convention (i.e. forward slash (/)). If you wish to include
1404 a quote in a file name, precede the quote with a backslash
1405 (\textbackslash{}). For example you might use the following
1406 for a Windows machine to backup the "My Documents" directory:
1411 Name = "Windows Set"
1418 File = "c:/My Documents"
1424 For exclude lists to work correctly on Windows, you must observe the following
1428 \item Filenames are case sensitive, so you must use the correct case.
1429 \item To 2~exclude a directory, you must not have a trailing slash on the
1431 \item I2~f you have spaces in your filename, you must enclose the entire name
1432 in double-quote characters ("). Trying to use a backslash before the space
1434 \item If you are using the old Exclude syntax (noted below), you may not
1435 specify a drive letter in the exclude. The new syntax noted above
1436 should work fine including driver letters.
1439 Thanks to Thiago Lima for summarizing the above items for us. If you are
1440 having difficulties getting includes or excludes to work, you might want to
1441 try using the {\bf estimate job=xxx listing} command documented in the
1442 \ilink{Console chapter}{estimate} of this manual.
1444 On Win32 systems, if you move a directory or file or rename a file into the
1445 set of files being backed up, and a Full backup has already been made, Bacula
1446 will not know there are new files to be saved during an Incremental or
1447 Differential backup (blame Microsoft, not me). To avoid this problem, please
1448 {\bf copy} any new directory or files into the backup area. If you do not have
1449 enough disk to copy the directory or files, move them, but then initiate a
1453 \paragraph*{A Windows Example FileSet}
1454 \index[general]{FileSet!Windows Example }
1455 \index[general]{Windows Example FileSet }
1457 The following example was contributed by Russell Howe. Please note that
1458 for presentation purposes, the lines beginning with Data and Internet
1459 have been wrapped and should included on the previous line with one
1464 This is my Windows 2000 fileset:
1466 Name = "Windows 2000"
1472 # Exclude Mozilla-based programs' file caches
1473 WildDir = "[A-Z]:/Documents and Settings/*/Application
1474 Data/*/Profiles/*/*/Cache"
1475 WildDir = "[A-Z]:/Documents and Settings/*/Application
1476 Data/*/Profiles/*/*/Cache.Trash"
1477 WildDir = "[A-Z]:/Documents and Settings/*/Application
1478 Data/*/Profiles/*/*/ImapMail"
1480 # Exclude user's registry files - they're always in use anyway.
1481 WildFile = "[A-Z]:/Documents and Settings/*/Local Settings/Application
1482 Data/Microsoft/Windows/usrclass.*"
1483 WildFile = "[A-Z]:/Documents and Settings/*/ntuser.*"
1485 # Exclude directories full of lots and lots of useless little files
1486 WildDir = "[A-Z]:/Documents and Settings/*/Cookies"
1487 WildDir = "[A-Z]:/Documents and Settings/*/Recent"
1488 WildDir = "[A-Z]:/Documents and Settings/*/Local Settings/History"
1489 WildDir = "[A-Z]:/Documents and Settings/*/Local Settings/Temp"
1490 WildDir = "[A-Z]:/Documents and Settings/*/Local Settings/Temporary
1493 # These are always open and unable to be backed up
1494 WildFile = "[A-Z]:/Documents and Settings/All Users/Application
1495 Data/Microsoft/Network/Downloader/qmgr[01].dat"
1497 # Some random bits of Windows we want to ignore
1498 WildFile = "[A-Z]:/WINNT/security/logs/scepol.log"
1499 WildDir = "[A-Z]:/WINNT/system32/config"
1500 WildDir = "[A-Z]:/WINNT/msdownld.tmp"
1501 WildDir = "[A-Z]:/WINNT/Internet Logs"
1502 WildDir = "[A-Z]:/WINNT/$Nt*Uninstall*"
1503 WildDir = "[A-Z]:/WINNT/sysvol"
1504 WildFile = "[A-Z]:/WINNT/cluster/CLUSDB"
1505 WildFile = "[A-Z]:/WINNT/cluster/CLUSDB.LOG"
1506 WildFile = "[A-Z]:/WINNT/NTDS/edb.log"
1507 WildFile = "[A-Z]:/WINNT/NTDS/ntds.dit"
1508 WildFile = "[A-Z]:/WINNT/NTDS/temp.edb"
1509 WildFile = "[A-Z]:/WINNT/ntfrs/jet/log/edb.log"
1510 WildFile = "[A-Z]:/WINNT/ntfrs/jet/ntfrs.jdb"
1511 WildFile = "[A-Z]:/WINNT/ntfrs/jet/temp/tmp.edb"
1512 WildFile = "[A-Z]:/WINNT/system32/CPL.CFG"
1513 WildFile = "[A-Z]:/WINNT/system32/dhcp/dhcp.mdb"
1514 WildFile = "[A-Z]:/WINNT/system32/dhcp/j50.log"
1515 WildFile = "[A-Z]:/WINNT/system32/dhcp/tmp.edb"
1516 WildFile = "[A-Z]:/WINNT/system32/LServer/edb.log"
1517 WildFile = "[A-Z]:/WINNT/system32/LServer/TLSLic.edb"
1518 WildFile = "[A-Z]:/WINNT/system32/LServer/tmp.edb"
1519 WildFile = "[A-Z]:/WINNT/system32/wins/j50.log"
1520 WildFile = "[A-Z]:/WINNT/system32/wins/wins.mdb"
1521 WildFile = "[A-Z]:/WINNT/system32/wins/winstmp.mdb"
1523 # Temporary directories & files
1524 WildDir = "[A-Z]:/WINNT/Temp"
1525 WildDir = "[A-Z]:/temp"
1527 WildDir = "[A-Z]:/tmp"
1528 WildDir = "[A-Z]:/var/tmp"
1531 WildDir = "[A-Z]:/RECYCLER"
1534 WildFile = "[A-Z]:/pagefile.sys"
1536 # These are programs and are easier to reinstall than restore from
1538 WildDir = "[A-Z]:/cygwin"
1539 WildDir = "[A-Z]:/Program Files/Grisoft"
1540 WildDir = "[A-Z]:/Program Files/Java"
1541 WildDir = "[A-Z]:/Program Files/Java Web Start"
1542 WildDir = "[A-Z]:/Program Files/JavaSoft"
1543 WildDir = "[A-Z]:/Program Files/Microsoft Office"
1544 WildDir = "[A-Z]:/Program Files/Mozilla Firefox"
1545 WildDir = "[A-Z]:/Program Files/Mozilla Thunderbird"
1546 WildDir = "[A-Z]:/Program Files/mozilla.org"
1547 WildDir = "[A-Z]:/Program Files/OpenOffice*"
1550 # Our Win2k boxen all have C: and D: as the main hard drives.
1558 Note, the three line of the above Exclude were split to fit on the document
1559 page, they should be written on a single line in real use.
1561 \paragraph*{Windows NTFS Naming Considerations}
1562 \index[general]{Windows NTFS Naming Considerations }
1563 \index[general]{Considerations!Windows NTFS Naming }
1565 NTFS filenames containing Unicode characters should now be supported
1566 as of version 1.37.30 or later.
1568 \section{Testing Your FileSet}
1569 \index[general]{FileSet!Testing Your }
1570 \index[general]{Testing Your FileSet }
1572 If you wish to get an idea of what your FileSet will really backup or if your
1573 exclusion rules will work correctly, you can test it by using the {\bf
1574 estimate} command in the Console program. See the
1575 \ilink{estimate}{estimate} in the Console chapter of this
1578 As an example, suppose you add the following test FileSet:
1585 File = /home/xxx/test
1594 You could then add some test files to the directory {\bf /home/xxx/test}
1595 and use the following command in the console:
1599 estimate job=<any-job-name> listing client=<desired-client> fileset=Test
1603 to give you a listing of all files that match.