Debian Codegraph @

manuals/en/problems/faq.tex

raw
1 % TODO: maybe merge all this FAQ in with the appropriate section?
2 % TODO: and use detailed indexing to help reader
3
4 \chapter{\bacula{} Frequently Asked Questions}
5 \label{blb:FaqChapter}
6 \index[general]{Questions!\bacula{} Frequently Asked}
7 \index[general]{\bacula{} Frequently Asked Questions}
8
9 These are questions that have been submitted over time by the
10 \bacula{} users. The following \acs{FAQ} is very useful, but it is not always up to date
11 with newer information, so after reading it, if you don't find what you
12 want, you might try the \bacula{} wiki maintained by Frank Sweetser, which
13 contains more than just a FAQ:
14 \bref{http://wiki.bacula.org}{wiki.bacula.org}
15 or go directly to the FAQ at:
16 \bref{http://wiki.bacula.org/doku.php?id=faq}{wiki.bacula.org/doku.php?id=faq}.
17
18 Please also see
19 \bilink{the bugs section}{blb:BugsChapter} of this document for a list
20 of known bugs and solutions.
21
22 \begin{bdescription}
23 \label{blb:what}
24 %\section{What is \bacula{}?}
25 \item [What is {\bf \bacula{}}? ]
26 \index[general]{What is \bacula{}?}
27 {\bf \bacula{}} is a network backup and restore program.
28
29 %\section{Does \bacula{} support Windows?}
30 \item [Does \bacula{} support Windows?]
31 \index[general]{Does \bacula{} support Windows?}
32 Yes, \bacula{} compiles and runs on Windows machines (Win98, WinMe, WinXP,
33 WinNT, Win2003, and Win2000). We provide a binary version of the Client
34 (\btool{bacula-fd}), but have not tested the Director nor the Storage daemon.
35 Note, Win95 is no longer supported because it doesn't have the
36 \texttt{GetFileAttributesExA} \acs{API} call.
37
38
39 \label{blb:lang}
40 %\section{What language is \bacula{} written in?}
41 \item [What language is \bacula{} written in?]
42 \index[general]{What language is \bacula{} written in?}
43 It is written in \texttt{C++}, but it is mostly \texttt{C} code using only a limited set of
44 the \texttt{C++} extensions over \texttt{C}. Thus \bacula{} is completely compiled using the
45 \texttt{C++} compiler. There are several modules, including the Win32 interface, that
46 are written using the object oriented \texttt{C++} features. Over time, we are slowly
47 adding a larger subset of \texttt{C++}.
48
49 \label{blb:run}
50 %\section{On what machines does \bacula{} run?}
51 \item [On what machines does \bacula{} run? ]
52 \index[general]{On what machines does \bacula{} run?}
53 {\bf \bacula{}} builds and executes on Red Hat Linux (versions RH7.1-RHEL
54 4.0, Fedora, SuSE, Gentoo, Debian, Mandriva, \ldots{}), FreeBSD, Solaris,
55 Alpha, SGI (client), NetBSD, OpenBSD, Mac OS X (client), and Win32.
56
57 \bacula{} has been my only backup tool for over seven years backing up 8
58 machines nightly (6 Linux boxes running SuSE, previously
59 Red Hat and Fedora, a WinXP machine, and a WinNT machine).
60
61
62 \label{blb:stable}
63 %\section{Is \bacula{} Stable?}
64 \item [Is \bacula{} Stable? ]
65 \index[general]{Is \bacula{} Stable?}
66 Yes, it is remarkably stable, but remember, there are still a lot of
67 unimplemented or partially implemented features. With a program of this
68 size (150,000+ lines of \texttt{C++} code not including the \acs{SQL} programs) there
69 are bound to be bugs. The current test environment (a twisted pair
70 local network and a HP DLT backup tape) is not exactly ideal, so
71 additional testing on other sites is necessary. The File daemon has
72 never crashed -- running months at a time with no intervention. The
73 Storage daemon is remarkably stable with most of the problems arising
74 during labeling or switching tapes. Storage daemon crashes are rare
75 but running multiple drives and simultaneous jobs sometimes (rarely)
76 problems.
77 The Director, given the multitude of functions it fulfills is also
78 relatively stable. In a production environment, it rarely if ever
79 crashes. Of the three daemons, the Director is the most prone to having
80 problems. Still, it frequently runs several months with no problems.
81
82 There are a number of reasons for this stability.
83
84 \begin{benumerate}
85 \item The program is constantly checking the chain of allocated
86 memory buffers to ensure that no overruns have occurred.
87 \item All memory leaks (orphaned buffers) are reported each time the
88 program terminates.
89 \item Any signal (segmentation fault, \ldots{}) generates a
90 traceback that is emailed to the developer. This permits quick
91 resolution of bugs even if they only show up rarely in a production
92 system.
93 \item There is a reasonably comprehensive set of regression tests
94 that avoids re-creating the most common errors in new versions of
95 \bacula{}.
96 \end{benumerate}
97
98 \label{blb:AuthorizationErrors}
99 %\section{I'm Getting Authorization Errors. What is Going On?}
100 \item [I'm Getting Authorization Errors. What is Going On? ]
101 \index[general]{Authorization Errors}
102 \index[general]{Concurrent Jobs}
103 For security reasons, \bacula{} requires that both the File daemon and the
104 Storage daemon know the name of the Director as well as its password. As a
105 consequence, if you change the Director's name or password, you must make
106 the corresponding change in the Storage daemon's and in the File daemon's
107 configuration files.
108
109 During the authorization process, the Storage daemon and File daemon
110 also require that the Director authenticates itself, so both ends
111 require the other to have the correct name and password.
112
113 If you have edited the conf files and modified any name or any password,
114 and you are getting authentication errors, then your best bet is to go
115 back to the original conf files generated by the \bacula{} installation
116 process. Make only the absolutely necessary modifications to these
117 files -- e.g. add the correct email address. Then follow the
118 instructions in the \bxlink{Running \bacula{}}{blb:TutorialChapter}{main}{chapter} of
119 the \bmainman{}. You will run a backup to disk and a restore. Only when
120 that works, should you begin customization of the conf files.
121
122 Another reason that you can get authentication errors is if you are
123 running Multiple Concurrent Jobs in the Director, but you have not set
124 them in the File daemon or the Storage daemon. Once you reach their
125 limit, they will reject the connection producing authentication (or
126 connection) errors.
127
128 If you are having problems connecting to a Windows machine that
129 previously worked, you might try restarting the \bacula{} service since
130 Windows frequently encounters networking connection problems.
131
132 Some users report that authentication fails if there is not a proper
133 reverse \acs{DNS} lookup entry for the machine. This seems to be a
134 requirement of gethostbyname(), which is what \bacula{} uses to translate
135 names into IP addresses. If you cannot add a reverse \acs{DNS} entry, or you
136 don't know how to do so, you can avoid the problem by specifying an IP
137 address rather than a machine name in the appropriate \bacula{} conf file.
138
139 Here is a picture that indicates what names/passwords in which
140 files/Resources must match up:
141
142 \bimageH{Conf-Diagram}{Configuration Diagram}{}
143
144 In the left column, you will find the Director, Storage, and Client
145 resources, with their names and passwords -- these are all in
146 \bfilename{bacula-dir.conf}. The right column is where the corresponding values
147 should be found in the Console, Storage daemon (SD), and File daemon (FD)
148 configuration files.
149
150 Another thing to check is to ensure that the \bacula{} component you are
151 trying to access has {\bf Maximum Concurrent Jobs} set large enough to
152 handle each of the Jobs and the Console that want to connect
153 simultaneously. Once the maximum connections has been reached, each
154 \bacula{} component will reject all new connections.
155
156 Please also remember that File daemons with later versions than the
157 Director and Storage daemons are not supported and can result in
158 authorization errors.
159
160 Finally, make sure you have no \bfilename{hosts.allow} or \bfilename{hosts.deny}
161 file that is not permitting access to the site trying to connect.
162
163 \label{blb:AccessProblems}
164 %\section{\bacula{} Runs Fine but Cannot Access a Client on a Different Machine. Why?}
165 \item [\bacula{} Runs Fine but Cannot Access a Client on a Different Machine. Why? ]
166 \index[general]{Cannot Access a Client}
167 There are several reasons why \bacula{} could not contact a client on a
168 different machine. They are:
169
170 \begin{bitemize}
171 \item It is a Windows Client, and the client died because of an improper
172 configuration file. Check that the \bacula{} icon is in the system tray and the
173 the menu items work. If the client has died, the icon will disappear only
174 when you move the mouse over the icon.
175 \item The Client address or port is incorrect or not resolved by \acs{DNS}. See if
176 you can ping the client machine using the same address as in the Client
177 record.
178 \item You have a firewall, and it is blocking traffic on port 9102 between
179 the Director's machine and the Client's machine (or on port 9103 between the
180 Client and the Storage daemon machines).
181 \item Your password or names are not correct in both the Director and the
182 Client machine. Try configuring everything identical to how you run the
183 client on the same machine as the Director, but just change the Address. If
184 that works, make the other changes one step at a time until it works.
185 \item You may also be having problems between your File daemon and your
186 Storage daemon. The name you use in the Storage resource of your
187 Director's conf file must be known (resolvable) by the File daemon,
188 because it is passed symbolically to the File daemon, which then
189 resolves it to get an IP address used to contact the Storage daemon.
190 \item You may have a \bfilename{hosts.allow} or \bfilename{hosts.deny} file that is
191 not permitting access.
192 \end{bitemize}
193
194 \label{blb:startover}
195 %\section{My Catalog is Full of Test Runs, How Can I Start Over?}
196 \item [My Catalog is Full of Test Runs, How Can I Start Over? ]
197 \index[general]{My Catalog is Full of Test Runs, How Can I Start Over?}
198 If you are using \mysql{}, PostgreSQL, or \sqlite{} do the following:
199
200 \begin{bVerbatim}
201 cd /opt/bacula/scripts
202 ./drop_bacula_tables
203 ./make_bacula_tables
204 ./grant_bacula_privileges
205 \end{bVerbatim}
206
207 Then write an \acs{EOF} on each tape you used with {\bf \bacula{}} using:
208
209 \begin{bVerbatim}
210 mt -f /dev/st0 rewind
211 mt -f /dev/st0 weof
212 \end{bVerbatim}
213
214 where you need to adjust the device name for your system.
215
216 \label{blb:restorehang}
217 %\section{I Run a Restore Job and \bacula{} Hangs. What do I do?}
218 \item [I Run a Restore Job and \bacula{} Hangs. What do I do?]
219 \index[general]{I Run a Restore Job and \bacula{} Hangs. What do I do?}
220 On \bacula{} version 1.25 and prior, it expects you to have the correct
221 tape mounted prior to a restore. On \bacula{} version 1.26 and higher, it
222 will ask you for the tape, and if the wrong one is mounted, it will
223 inform you.
224
225 If you have previously done an \bcommandname{unmount} command, all Storage daemon
226 sessions (jobs) will be completely blocked from using the drive
227 unmounted, so be sure to do a \bcommandname{mount} after your unmount. If in
228 doubt, do a second \bcommandname{mount}, it won't cause any harm.
229
230 \label{blb:windowstart}
231 %\section{I Cannot Get My Windows Client to Start Automatically?}
232 \item [I Cannot Get My Windows Client to Start Automatically? ]
233 \index[general]{Windows Auto Start}
234 You are probably having one of two problems: either the Client is dying
235 due to an incorrect configuration file, or you didn't do the
236 Installation commands necessary to install it as a Windows Service.
237
238 For the first problem, see the next FAQ question. For the second
239 problem, please review the \bxlink{Windows Installation Instructions}{blb:Win32Chapter}{main}{chapter} in the\bmainman{}.
240
241 \label{blb:windowsdie}
242 %\section{My Windows Client Immediately Dies When I Start It}
243 \item [My Windows Client Immediately Dies When I Start It]
244 \index[general]{Windows Client Dies}
245 The most common problem is either that the configuration file is not where
246 it expects it to be, or that there is an error in the configuration file.
247 You must have the configuration file in
248 \begin{bVerbatim}
249 c:\bacula\bin\bacula-fd.conf
250 \end{bVerbatim}
251
252 To \textbf{see} what is going on when the File daemon starts on Windows, do the
253 following:
254
255 \begin{bVerbatim}
256 Start a DOS shell Window.
257 cd c:\bacula\bin
258 bacula-fd -d100 -c c:\bacula\bin\bacula-fd.conf
259 \end{bVerbatim}
260
261 This will cause the FD to write a file \bfilename{bacula.trace} in the current
262 directory, which you can examine and thereby determine the problem.
263
264 \label{blb:scroll}
265 \item [When I Start the Console, the Error Messages Fly By. How can I see them? ]
266 \index[general]{Error Messages}
267 Either use a shell window with a scroll bar, or use the gnome-console.
268 In any case, you probably should be logging all output to a file, and
269 then you can simply view the file using an editor or the \btool{less}
270 program. To log all output, I have the following in my Director's
271 Message resource definition:
272
273 \begin{bVerbatim}
274 append = "/home/kern/bacula/bin/log" = all, !skipped
275 \end{bVerbatim}
276
277 Obviously you will want to change the filename to be appropriate for your
278 system.
279
280 \label{blb:nobackup}
281 %\section{My backups are not working on my Windows Client. What should I do?}
282 \item [I didn't realize that the backups were not working on my Windows
283 Client. What should I do? ]
284 \index[general]{Backups Failing}
285 You should be sending yourself an email message for each job. This will avoid
286 the possibility of not knowing about a failed backup. To do so put something
287 like:
288
289 \begin{bVerbatim}
290 Mail = yourname@yourdomain = all, !skipped
291 \end{bVerbatim}
292
293 in your Director's message resource. You should then receive one email for
294 each Job that ran. When you are comfortable with what is going on (it took
295 me 9 months), you might change that to:
296
297 \begin{bVerbatim}
298 MailOnError = yourname@yourdomain = all, !skipped
299 \end{bVerbatim}
300
301 then you only get email messages when a Job errors as is the case for your
302 Windows machine.
303
304 You should also be logging the Director's messages, please see the previous
305 FAQ for how to do so.
306
307 \label{blb:sched}
308 %\section{All my Jobs are scheduled for the same time. Will this cause problems?}
309 \item [All my Jobs are scheduled for the same time. Will this cause problems? ]
310 \index[general]{Schedule problems}
311 No, not at all. \bacula{} will schedule all the Jobs at the same time, but
312 will run them one after another unless you have increased the number of
313 simultaneous jobs in the configuration files for the Director, the File
314 daemon, and the Storage daemon. The appropriate configuration record is
315 \bdirectivename{Maximum Concurrent Jobs = nn}. At the current time, we recommend
316 that you leave this set to \textbf{1} for the Director.
317
318 \label{blb:disk}
319 %\section{Can \bacula{} Backup My System To Files instead of Tape?}
320 \item [Can \bacula{} Backup My System To Files instead of Tape? ]
321 \index[general]{Backup to Disk}
322 Yes, in principle, \bacula{} can backup to any storage medium as long as
323 you have correctly defined that medium in the Storage daemon's Device
324 resource. For an example of how to backup to files, please see the
325 \bxlink{Pruning Example}{blb:PruningExample}{main}{chapter} of the \bmainman{}.
326 Also, there is a whole chapter devoted to \bxlink{Basic Volume Management}{blb:DiskChapter}{main}{chapter} in the \bmainman{}. This chapter was originally written to
327 explain how to write to disk, but was expanded to include volume
328 management. It is, however, still quite a good chapter to read.
329
330 \label{blb:testbackup}
331 %\section{Can I use a dummy device to test the backup?}
332 \item [Can I use a dummy device to test the backup?]
333 Yes, to have a \emph{Virtual} device which just consumes data, you can use a
334 FIFO device (see \bxlink{Stored configuration}{blb:SetupFifo}{main}{chapter}
335 in the \bmainman{}). It's useful to test a backup.
336 \begin{bVerbatim}
337 Device {
338 Name = NULL
339 Media Type = NULL
340 Device Type = Fifo
341 Archive Device = /dev/null
342 LabelMedia = yes
343 Random Access = no
344 AutomaticMount = no
345 RemovableMedia = no
346 MaximumOpenWait = 60
347 AlwaysOpen = no
348 }
349 \end{bVerbatim}
350
351 \label{blb:bigfiles}
352 %\section{Can \bacula{} Backup and Restore Files Bigger than 2 Gigabytes?}
353 \item [Can \bacula{} Backup and Restore Files Bigger than 2 Gigabytes?]
354 \index[general]{Large file support}
355 If your operating system permits it, and you are running \bacula{} version
356 1.26 or later, the answer is yes. To the best of our knowledge all client
357 system supported by \bacula{} can handle files bigger 2 Gigabytes.
358
359 \label{blb:cancel}
360 %\section{I want to stop a job}
361 %% Is there a better way than "./bacula stop" to stop it?}
362 \item [I Started A Job then Decided I Really Did Not Want to Run It. Is
363 there a better way than \btool{./bacula stop} to stop it?]
364 \index[general]{Cancelling jobs}
365 Yes, you normally should use the Console command \bcommandname{cancel} to cancel
366 a Job that is either scheduled or running. If the Job is scheduled, it
367 will be marked for cancellation and will be canceled when it is
368 scheduled to start. If it is running, it will normally terminate after
369 a few minutes. If the Job is waiting on a tape mount, you may need to
370 do a \bcommandname{mount} command before it will be canceled.
371
372 \label{blb:trademark}
373 %\section{Why have You Trademarked the Name \bacula{}?}
374 \item [Why have You Trademarked the Name \bacula{}\bregistered{}?]
375 \index[general]{\bacula{} Trademark}
376 We have trademarked the name \bacula{} to ensure that all media written by any
377 program named \bacula{} will always be compatible. Anyone may use the name
378 \bacula{}, even in a derivative product as long as it remains totally compatible
379 in all respects with the program defined here.
380
381 \label{blb:docversion}
382 %\section{Why is the Online Document for Version 1.39 but the Released Version is 1.38?}
383 \item [Why is the Online Document for Version 1.39 of \bacula{} when the Current Version is 1.38?]
384 \index[general]{Multiple manuals}
385 As \bacula{} is being developed, the document is also being enhanced, more
386 often than not it has clarifications of existing features that can be very
387 useful to our users, so we publish the very latest document. Fortunately
388 it is rare that there are confusions with new features.
389
390 If you want to read a document that pertains only to a specific version,
391 please use the one distributed in the source code. The web site also has
392 online versions of both the released manual and the current development
393 manual.
394
395 \label{blb:sure}
396 %\section{Does \bacula{} really save and restore all files?}
397 \item [How Can I Be Sure that \bacula{} Really Saves and Restores All Files? ]
398 \index[general]{Checking Restores}
399 It is really quite simple, but took me a while to figure
400 out how to ``prove'' it. First make a \bacula{} Rescue disk, see the
401 \bilink{Disaster Recovery Using \bacula{}}{blb:RescueChapter}{main}{chapter}
402 of the \bmainman{}.
403 Second, you run a full backup of all your files on all partitions.
404 Third, you run an Verify InitCatalog Job on the same FileSet, which
405 effectively makes a record of all the files on your system. Fourth, you
406 run a Verify Catalog job and assure yourself that nothing has changed
407 (well, between an InitCatalog and Catalog one doesn't expect anything).
408 Then do the unthinkable, write zeros on your MBR (master boot record)
409 wiping out your hard disk. Now, restore your whole system using your
410 \bacula{} Rescue disk and the Full backup you made, and finally re-run the
411 Verify Catalog job. You will see that with the exception of the
412 directory modification and access dates and the files changed during the
413 boot, your system is identical to what it was before you wiped your hard
414 disk.
415 Alternatively you could do the wiping and restoring to another computer
416 of the same type.
417
418 \label{blb:upgrade}
419 %\section{I want an Incremental but \bacula{} runs it as a Full backup. Why?}
420 \item [I did a Full backup last week, but now in running an Incremental,
421 \bacula{} says it did not find a FULL backup, so it did a FULL backup. Why?]
422 \index[general]{FULL backup not found}
423 Before doing an Incremental or a Differential
424 backup, \bacula{} checks to see if there was a prior Full backup of the
425 same Job that terminated successfully. If so, it uses the date that
426 full backup started as the time for comparing if files have changed. If
427 \bacula{} does not find a successful full backup, it proceeds to do one.
428 Perhaps you canceled the full backup, or it terminated in error. In
429 such cases, the full backup will not be successful. You can check by
430 entering \bcommandname{list jobs} and look to see if there is a prior Job with
431 the same Name that has Level F and JobStatus T (normal termination).
432
433 Another reason why \bacula{} may not find a suitable Full backup is that
434 every time you change the FileSet, \bacula{} will require a new Full
435 backup. This is necessary to ensure that all files are properly backed
436 up in the case where you have added more files to the FileSet.
437 Beginning with version 1.31, the FileSets are also dated when they are
438 created, and this date is displayed with the name when you are listing
439 or selecting a FileSet. For more on backup levels see below.
440
441 See also {\bf Ignore FileSet Changes} in the
442 \bxlink{FileSet Resource definition}{blb:FileSetResource}{main}{chapter} in the \bmainman{}.
443
444 \label{blb:filenamelengths}
445 %\section{Do you really handle unlimited path lengths?}
446 \item [How Can You Claim to Handle Unlimited Path and Filename Lengths
447 when All Other Programs Have Fixed Limits?]
448 \index[general]{Path and Filename Lengths}
449 Most of those other programs have been around for a long time, in fact
450 since the beginning of Unix, which means that they were designed for
451 rather small fixed length path and filename lengths. Over the years,
452 these restrictions have been relaxed allowing longer names. \bacula{} on
453 the other hand was designed in 2000, and so from the start, Path and
454 Filenames have been kept in buffers that start at 256 bytes in length,
455 but can grow as needed to handle any length. Most of the work is
456 carried out by lower level routines making the coding rather easy.
457
458 Note that due to limitations Win32 path and filenames cannot exceed
459 260 characters. By using Win32 Unicode functions, we will remove this
460 restriction in later versions of \bacula{}.
461
462 \label{blb:unique}
463 %\section{What Is the Really Unique Feature of \bacula{}?}
464 \item [What Is the Really Unique Feature of \bacula{}?]
465 \index[general]{Unique Feature of \bacula{}}
466 Well, it is hard to come up with unique features when backup programs
467 for Unix machines have been around since the 1960s. That said, I
468 believe that \bacula{} is the first and only program to use a standard \acs{SQL}
469 interface to catalog its database. Although this adds a bit of
470 complexity and possibly overhead, it provides an amazingly rich set of
471 features that are easy to program and enhance. The current code has
472 barely scratched the surface in this regard (version 1.38).
473
474 The second feature, which gives a lot of power and flexibility to \bacula{}
475 is the Bootstrap record definition.
476
477 The third unique feature, which is currently (1.30) unimplemented, and
478 thus can be called vaporware :-), is Base level saves. When
479 implemented, this will enormously reduce tape usage.
480
481 \label{blb:sequence}
482 %%\section{How can I force one job to run after another?}
483 \item [If I Run Multiple Simultaneous Jobs, How Can I Force One
484 Particular Job to Run After Another Job? ]
485 \index[general]{Multiple Simultaneous Jobs}
486 Yes, you can set Priorities on your jobs so that they run in the order you
487 specify. Please see:
488 \bxlink{the Priority record}{blb:Priority}{main}{chapter} of the \bmainman{} in
489 the Job resource.
490
491 \label{blb:nomail}
492 %\section{I Am Not Getting Email Notification, What Can I Do?}
493 \item [I Am Not Getting Email Notification, What Can I Do? ]
494 \index[general]{No Email Notification}
495 The most common problem is that you have not specified a fully qualified
496 email address and your bsmtp server is rejecting the mail. The next
497 most common problem is that your bsmtp server doesn't like the syntax on
498 the From part of the message. For more details on this and other
499 problems, please see the
500 \bilink{Getting Email Notification to Work}{blb:email} section of the Tips chapter of this manual. The section
501 \bilink{Getting Notified of Job Completion}{blb:notification} of the Tips
502 chapter may also be useful. For more information on the \btool{bsmtp}
503 mail program, please see \bxlink{bsmtp}{blb:bsmtp}{utility}{command} in the
504 \butilityman{}.
505
506 \label{blb:periods}
507 %\section{My retention periods don't work}
508 \item [I Change Recycling, Retention Periods, or File Sizes in my Pool
509 Resource and they Still Don't Work.]
510 \index[general]{blb:Recycling}
511 \index[general]{Retention Periods}
512 \index[general]{Pool changes}
513 The different variables associated with a Pool are defined in the Pool
514 Resource, but are actually read by \bacula{} from the Catalog database. On
515 \bacula{} versions prior to 1.30, after changing your Pool Resource, you must
516 manually update the corresponding values in the Catalog by using the
517 \bcommandname{update pool} command in the Console program. In \bacula{} version 1.30, \bacula{}
518 does this for you automatically every time it starts.
519
520 When \bacula{} creates a Media record (Volume), it uses many default values from
521 the Pool record. If you subsequently change the Pool record, the new values
522 will be used as a default for the next Volume that is created, but if you
523 want the new values to apply to existing Volumes, you must manually update
524 the Volume Catalog entry using the \bcommandname{update volume} command in the Console
525 program.
526
527 \label{blb:CompressionNotWorking}
528 %\section{Why aren't my files compressed?}
529 \item [I Have Configured Compression On, But None of My Files Are
530 Compressed. Why?]
531 \index[general]{Compression}
532 There are two kinds of compression. One is tape compression. This is done by
533 the tape drive hardware, and you either enable or disable it with system
534 tools such as \btool{mt}. This compression works independently of \bacula{},
535 and when it is enabled, you should not use the \bacula{} software
536 compression.
537
538 \bacula{} also has software compression code in the File daemons, which you
539 normally need to enable only when backing up to file Volumes. There are
540 two conditions necessary to enable the \bacula{} software compression.
541
542 \begin{benumerate}
543 \item You must have the \btool{zip} development libraries loaded on your system
544 when building \bacula{} and \bacula{} must find this library, normally
545 \bfilename{/usr/lib/libz.a}. On Red Hat systems, this library is provided by the
546 \btool{zlib-devel} rpm.
547
548 If the library is found by \bacula{} during the \btool{./configure} it will
549 be mentioned in the \bfilename{config.out} line by:
550
551 \begin{bVerbatim}
552 ZLIB support: yes
553 \end{bVerbatim}
554
555 \item You must add the \bdirectivename{compression=gzip} option on your Include
556 statement in the Director's configuration file.
557 \end{benumerate}
558
559 \label{blb:NewTape}
560 \item [\bacula{} is Asking for a New Tape After 2 GB of Data but My Tape
561 holds 33 GB. Why?]
562 \index[general]{Tape capacity}
563 There are several reasons why \bacula{} will request a new tape.
564
565 \begin{bitemize}
566 \item There is an I/O error on the tape. \bacula{} prints an error message and
567 requests a new tape. \bacula{} does not attempt to continue writing after an
568 I/O error.
569 \item \bacula{} encounters and end of medium on the tape. This is not always
570 distinguishable from an I/O error.
571 \item You have specifically set some size limitation on the tape. For example
572 the \textbf{Maximum Volume Bytes} or \textbf{Maximum Volume Files} in the
573 Director's Pool resource, or \textbf{Maximum Volume Size} in the Storage
574 daemon's Device resource.
575 \end{bitemize}
576
577 \label{blb:LevelChanging}
578 %\section{Incremental backups are not working}
579 \item [\bacula{} is Not Doing the Right Thing When I Request an Incremental
580 Backup. Why?]
581 \index[general]{Incremental backups}
582 As explained in one of the previous questions, \bacula{} will automatically
583 upgrade an Incremental or Differential job to a Full backup if it cannot
584 find a prior Full backup or a suitable Full backup. For the gory
585 details on how/when \bacula{} decides to upgrade levels please see the
586 \bxlink{Level record}{blb:Level}{main}{chapter} in the \bmainman{}.
587
588 If after reading the above mentioned section, you believe that \bacula{} is not
589 correctly handling the level (Differential/Incremental), please send us the
590 following information for analysis:
591
592 \begin{bitemize}
593 \item Your Director's configuration file.
594 \item The output from \bcommandname{list jobs} covering the period where you are
595 having the problem.
596 \item The Job report output from the prior Full save (not critical).
597 \item An \bcommandname{llist jobid=nnn} where \texttt{nnn} is the JobId of the prior Full save.
598
599 \item The Job report output from the save that is doing the wrong thing (not
600 critical).
601 \item An \bcommandname{llist jobid=nnn} where \texttt{nnn} is the JobId of the job that was not
602 correct.
603 \item An explanation of what job went wrong and why you think it did.
604 \end{bitemize}
605
606 The above information can allow us to analyze what happened, without it,
607 there is not much we can do.
608
609 \label{blb:WaitForever}
610 %\section{I am waiting forever for a backup of an offsite machine}
611 \item [I am Backing Up an Offsite Machine with an Unreliable Connection.
612 The Director Waits Forever for the Client to Contact the SD. What Can I
613 Do?]
614 \index[general]{Backing Up Offsite Machines}
615 \bacula{} was written on the assumption that it will have a good TCP/IP
616 connection between all the daemons. As a consequence, the current
617 \bacula{} doesn't deal with faulty connections very well. This situation
618 is slowly being corrected over time.
619
620 There are several things you can do to improve the situation.
621
622 \begin{bitemize}
623 \item Upgrade to version 1.32 and use the new SDConnectTimeout record. For
624 example, set:
625
626 \begin{bVerbatim}
627 SD Connect Timeout = 5 min
628 \end{bVerbatim}
629
630 in the FileDaemon resource.
631 \item Run these kinds of jobs after all other jobs.
632 \end{bitemize}
633
634 \label{blb:sshHanging}
635 %\section{SSH hangs forever after starting \bacula{}}
636 \item [When I ssh into a machine and start \bacula{} then attempt to exit,
637 ssh hangs forever.]
638 \index[general]{ssh hangs}
639 This happens because \bacula{} leaves \texttt{stdin}, \texttt{stdout}, and \texttt{stderr} open for
640 debug purposes. To avoid it, the simplest thing to do is to redirect
641 the output of those files to \bfilename{/dev/null} or another file in your
642 startup script (the Red Hat autostart scripts do this automatically).
643 For example, you start the Director with:
644
645 \begin{bVerbatim}
646 bacula-dir -c bacula-dir.conf \ldots{} >/dev/null 0>\&1 2>\&1
647 \end{bVerbatim}
648
649 and likewise for the other daemons.
650
651 \label{blb:RetentionPeriods}
652 %\section{I'm confused by retention periods}
653 \item [I'm confused by the different Retention periods: File Retention,
654 Job Retention, Volume Retention. Why are there so many?]
655 \index[general]{Retention Periods}
656 Yes, this certainly can be confusing. The basic reason for so many is
657 to allow flexibility. The File records take quite a lot of space in the
658 catalog, so they are typically records you want to remove rather
659 quickly. The Job records, take very little space, and they can be
660 useful even without the File records to see what Jobs actually ran and
661 when. One must understand that if the File records are removed from the
662 catalog, you cannot use the \bcommandname{restore} command to restore an
663 individual file since \bacula{} no longer knows where it is. However, as
664 long as the Volume Retention period has not expired, the data will still
665 be on the tape, and can be recovered from the tape.
666
667 For example, I keep a 30 day retention period for my Files to keep my
668 catalog from getting too big, but I keep my tapes for a minimum of one
669 year, just in case.
670
671 \label{blb:MaxVolumeSize}
672 %\section{MaxVolumeSize is ignored}
673 \item [Why Does \bacula{} Ignore the MaxVolumeSize Set in my Pool?]
674 \index[general]{MaxVolumeSize}
675 The MaxVolumeSize that \bacula{} uses comes from the Media record, so most
676 likely you changed your Pool, which is used as the default for creating
677 Media records, \textbf{after} you created your Volume. Check what is in
678 the Media record by doing:
679
680 \begin{bVerbatim}
681 llist Volume=xxx
682 \end{bVerbatim}
683
684 If it doesn't have the right value, you can use:
685
686 \begin{bVerbatim}
687 update Volume=xxx
688 \end{bVerbatim}
689
690 to change it.
691
692 \label{blb:ConnectionRefused}
693 %\section{I get a Connection refused when connecting to my Client}
694 \item [In connecting to my Client, I get "ERR:Connection Refused. Packet
695 Size too big from File daemon:192.168.1.4:9102" Why?]
696 \index[general]{ERR:Connection Refused}
697 This is typically a communications error resulting from one of the
698 following:
699
700
701 \begin{bitemize}
702 \item Old versions of \bacula{}, usually a Win32 client, where two threads were
703 using the same I/O packet. Fixed in more recent versions. Please upgrade.
704 \item Some other program such as an HP Printer using the same port (9102 in
705 this case).
706 \end{bitemize}
707
708 If it is neither of the above, please submit a bug report at
709 \bref{http://bugs.bacula.org}{bugs.bacula.org}.
710
711 Another solution might be to run the daemon with the debug option by:
712
713 \begin{bVerbatim}
714 Start a DOS shell Window.
715 cd c:\bacula\bin
716 bacula-fd -d100 -c c:\bacula\bin\bacula-fd.conf
717 \end{bVerbatim}
718
719 This will cause the FD to write a file \bfilename{bacula.trace} in the current
720 directory, which you can examine to determine the problem.
721
722 %\section{Long running jobs die with Pipe Error}
723 \item [During long running jobs my File daemon dies with Pipe Error, or
724 some other communications error. Why?]
725 \index[general]{Communications Errors}
726 \index[general]{Pipe Errors}
727 \index[general]{slow}
728 \index[general]{Backups!slow}
729 There are a number of reasons why a connection might break.
730 Most often, it is a router between your two computers that times out
731 inactive lines (not respecting the keepalive feature that \bacula{} uses).
732 In that case, you can use the \textbf{Heartbeat Interval} directive in
733 both the Storage daemon and the File daemon.
734
735 In at least one case, the problem has been a bad driver for a Win32
736 NVidia NForce 3 ethernet card with driver (4.4.2 17/05/2004).
737 In this case, a good driver is (4.8.2.0 06/04/2005). Moral of
738 the story, make sure you have the latest ethernet drivers
739 loaded, or use the following workaround as suggested by Thomas
740 Simmons for Win32 machines:
741
742 Browse to:
743 \begin{bVerbatim}
744 Start > Control Panel > Network Connections
745 \end{bVerbatim}
746
747 Right click the connection for the nvidia adapter and select properties.
748 Under the \texttt{General} tab, click ``Configure\ldots{}''. Under the \texttt{Advanced} tab set
749 ``Checksum Offload'' to disabled and click OK to save the change.
750
751 Lack of communications, or communications that get interrupted can
752 also be caused by Linux firewalls where you have a rule that throttles
753 connections or traffic. For example, if you have:
754
755 \begin{bVerbatim}
756 iptables -t filter -A INPUT -m limit --limit 3/second --limit-burst 3 -j DROP
757 \end{bVerbatim}
758
759 you will want to add the following rules \textbf{before} the above rule:
760 \begin{bVerbatim}
761 iptables -t filter -A INPUT --dport 9101 -j ACCEPT
762 iptables -t filter -A INPUT --dport 9102 -j ACCEPT
763 iptables -t filter -A INPUT --dport 9103 -j ACCEPT
764 \end{bVerbatim}
765 This will ensure that any \bacula{} traffic will not get terminated because
766 of high usage rates.
767
768 %\section{How do I tell the Job which Volume to use?}
769 \item[I can't figure out how to tell the job which volume to use]
770 \index[general]{What tape to mount}
771 This is an interesting statement. I now see that a number of people new to
772 \bacula{} have the same problem as you, probably from using programs like \tar{}.
773
774 In fact, you do not tell \bacula{} what tapes to use. It is the inverse. \bacula{}
775 tells you what tapes it wants. You put tapes at its disposition and it
776 chooses.
777
778 Now, if you \textbf{really} want to be tricky and try to tell \bacula{} what to do, it
779 will be reasonable if for example you mount a valid tape that it can use on a
780 drive, it will most likely go ahead and use it. It also has a documented
781 algorithm for choosing tapes -- but you are asking for problems \ldots{}
782
783 So, the trick is to invert your concept of things and put \bacula{} in charge of
784 handling the tapes. Once you do that, you will be fine. If you want to
785 anticipate what it is going to do, you can generally figure it out correctly
786 and get what you want.
787
788 If you start with the idea that you are going to force or tell \bacula{} to use
789 particular tapes or you insist on trying to run in that kind of mode, you will
790 probably not be too happy.
791
792 I don't want to worry about what tape has what data. That is what \bacula{} is
793 designed for.
794
795 If you have an application where you \textbf{really} need to remove a tape each day
796 and insert a new one, it can be done the directives exist to accomplish that.
797 In such a case, one little ``trick'' to knowing what tape \bacula{} will want at
798 2am while you are asleep is to run a tiny job at 4pm while you are still at
799 work that backs up say one directory, or even one file. You will quickly find
800 out what tape it wants, and you can mount it before you go home \ldots{}
801
802 \label{blb:Password generation}
803 %\section{Password generation}
804 \item [How do I generate a password?]
805 \index[general]{MaxVolumeSize}
806
807 Each daemon needs a password. This password occurs in the configuration
808 file for that daemon and in the \bfilename{bacula-dir.conf} file. These passwords are
809 plain text. There is no special generation procedure. Most people just
810 use random text.
811
812 Passwords are never sent over the wire in plain text. They are always
813 encrypted.
814
815 Security surrounding these passwords is best left security to your
816 operating system. Passwords are not encrypted within \bacula{}
817 configuration files.
818 \end{bdescription}