Debian Codegraph @

manuals/en/main/basejob.tex

raw
1 \chapter{File Deduplication using Base Jobs}
2 \index[general]{Base Jobs}
3 \index[general]{File Deduplication}
4 \label{blb:basejobs}
5
6 A base job is sort of like a Full save except that you will want the
7 FileSet to contain only files that are unlikely to change in the future
8 (i.e. a snapshot of most of your system after installing it). After the
9 base job has been run, when you are doing a Full save, you specify one or
10 more Base jobs to be used. All files that have been backed up in the Base
11 job/jobs but not modified will then be excluded from the backup. During a
12 restore, the Base jobs will be automatically pulled in where necessary.
13
14 This can be a very nice optimization for your backups. Basically, imagine
15 that you have 100 nearly identical Windows or Linux machines containing the
16 OS and user files. Now for the OS part, a Base job will be backed up once,
17 and rather than making 100 copies of the OS, there will be only one. If
18 one or more of the systems have some files updated, no problem, they will
19 be automatically saved and restored.
20
21 A new Job directive \texttt{Base=Jobx, Joby...} permits you to specify the
22 list of jobs that will be used during a Full backup as base.
23
24 \begin{bVerbatim}
25 Job {
26 Name = BackupLinux
27 Level= Base
28 ...
29 }
30
31 Job {
32 Name = BackupZog4
33 Base = BackupZog4, BackupLinux
34 Accurate = yes
35 ...
36 }
37 \end{bVerbatim}
38
39 In this example, the job \texttt{BackupZog4} will use the most recent version
40 of all files contained in \texttt{BackupZog4} and \texttt{BackupLinux}
41 jobs. Base jobs should have run with \texttt{level=Base} to be used.
42
43 By default, \bacula{} will compare permissions bits, user and group fields,
44 modification time, size and the checksum of the file to choose between the
45 current backup and the BaseJob file list. You can change this behavior with the
46 \texttt{BaseJob} FileSet option. This option works like the \texttt{verify=}
47 one, that is described in the \bilink{FileSet}{blb:FileSetResource} chapter.
48
49 \begin{bVerbatim}
50 FileSet {
51 Name = Full
52 Include = {
53 Options {
54 BaseJob = pmugcs5
55 Accurate = mcs
56 Verify = pin5
57 }
58 File = /
59 }
60 }
61 \end{bVerbatim}
62
63 \paragraph{Important note}: The current implementation doesn't permit to scan
64 a Volume with the \btool{bscan} facility. The result does not permit the restore of files.
65 It is therefore recommended to not prune File or Job records with Basejobs in use.
66
67 \smallskip
68
69 Added in version 8.0.5, the new ``M'' option letter for the Accurate directive
70 in the FileSet Options block, which allows comparing the modification time and/or
71 creation time against the last backup timestamp. This is in contrast to the
72 existing options letters ``m'' and/or ``c'', mtime and ctime, which are checked
73 against the stored catalog values, that could vary accross different machines
74 when using the BaseJob feature.
75
76 The advantage of the new ``M'' option letter for Jobs that refer to BaseJobs is
77 that it will backup files based on the last backup time, which is more useful,
78 because the mtime/ctime timestamps may differ on various Clients, causing
79 unnecessary files to be backed up.
80
81 \begin{bVerbatim}
82 Job {
83 Name = USR
84 Level = Base
85 FileSet = BaseFS
86 ...
87 }
88
89 Job {
90 Name = Full
91 FileSet = FullFS
92 Base = USR
93 ...
94 }
95
96 FileSet {
97 Name = BaseFS
98 Include {
99 Options {
100 Signature = MD5
101 }
102 File = /usr
103 }
104 }
105
106 FileSet {
107 Name = FullFS
108 Include {
109 Options {
110 Accurate = Ms # check for mtime/ctime and Size
111 Signature = MD5
112 }
113 File = /home
114 File = /usr
115 }
116 }
117 \end{bVerbatim}
118
119 \smallskip{}
120 Base Jobs are not compatible with Copy or Migration Jobs.