4 \section*{Bacula Frequently Asked Questions}
5 \label{_ChapterStart48}
6 \index[general]{Questions!Bacula Frequently Asked }
7 \index[general]{Bacula Frequently Asked Questions }
8 \addcontentsline{toc}{section}{Bacula Frequently Asked Questions}
10 These are questions that have been submitted over time by the
14 \ilink{the bugs section}{_ChapterStart4} of this document for a list
15 of known bugs and solutions.
17 \subsection*{Frequently Asked Questions}
18 \addcontentsline{toc}{section}{Frequently Asked Questions}
23 \item [What is {\bf Bacula}? ]
24 \index[general]{What is Bacula? }
25 {\bf Bacula} is a network backup and restore program.
27 \item [Does Bacula support Windows?]
28 \index[general]{Does Bacula support Windows? }
29 Yes, Bacula compiles and runs on Windows machines (Win98, WinMe, WinXP,
30 WinNT, and Win2000). We provide a binary version of the Client (bacula-fd),
31 but have not tested the Director nor the Storage daemon. Note, Win95 is no
32 longer supported because it doesn't have the GetFileAttributesExA API call.
35 \item [What language is Bacula written in?]
36 \index[general]{What language is Bacula written in? }
37 It is written in C++, but it is mostly C code using only a limited set of the
38 C++ extensions over C. Thus Bacula is completely compiled using the C++
39 compiler. There are several modules, including the Win32 interface, that
40 are written using the object oriented C++ features. Over time, we are slowly
41 adding a larger subset of C++.
44 \item [On what machines does Bacula run? ]
45 \index[general]{On what machines does Bacula run? }
46 {\bf Bacula} builds and executes on RedHat Linux (versions RH7.1-RHEL 3.0,
47 SUSE, Gentoo, Debian, Mandriva, ...), FreeBSD, Solaris, Alpha, SGI (client),
48 NetBSD, OpenBSD, Mac OS X (client), and Win32 (client).
50 Bacula has been my only backup tool for over four years backing up 5 machines
51 nightly (3 Linux boxes running RedHat, a WinXP machine, and a WinNT machine).
55 \item [Is Bacula Stable? ]
56 \index[general]{Is Bacula Stable? }
57 Yes, it is remarkably stable, but remember, there are still a lot of
58 unimplemented or partially implemented features. With a program of this size
59 (100,000+ lines of C++ code not including the SQL programs) there are bound
60 to be bugs. The current test environment (a twisted pair local network and a
61 HP DLT backup tape) is not exactly ideal, so additional testing on other sites is
62 necessary. The File daemon has never crashed -- running months at a time with
63 no intervention. The Storage daemon is remarkably stable with most of the
64 problems arising during labeling or switching tapes. Storage daemon crashes
65 are rare. The Director, given the multitude of functions it fulfills is also
66 relatively stable. In a production environment, it rarely if ever crashes. Of
67 the three daemons, the Director is the most prone to having problems. Still, it
68 frequently runs several months with no problems.
70 There are a number of reasons for this stability.
73 \item The program was largely written by one person to date
75 \item The program is constantly checking the chain of allocated
76 memory buffers to ensure that no overruns have occurred. \\
77 \item All memory leaks (orphaned buffers) are reported each time the
79 \item Any signal (segmentation fault, ...) generates a
80 traceback that is emailed to the developer. This permits quick resolution of
81 bugs even if they only show up rarely in a production system.\\
82 \item There is a reasonably comprehensive set of regression tests
83 that avoids re-creating the most common errors in new versions of
87 \label{AuthorizationErrors}
89 \item [I'm Getting Authorization Errors. What is Going On? ]
90 \index[general]{I'm Getting Authorization Errors. What is Going On? }
91 For security reasons, Bacula requires that both the File daemon and the
92 Storage daemon know the name of the Director as well as its password. As a
93 consequence, if you change the Director's name or password, you must make
94 the corresponding change in the Storage daemon's and in the File daemon's
97 During the authorization process, the Storage daemon and File daemon also
98 require that the Director authenticates itself, so both ends require the other
99 to have the correct name and password.
101 If you have edited the conf files and modified any name or any password, and
102 you are getting authentication errors, then your best bet is to go back to
103 the original conf files generated by the Bacula installation process. Make
104 only the absolutely necessary modifications to these files -- e.g. add the
105 correct email address. Then follow the instructions in the
106 \ilink{ Running Bacula}{_ChapterStart1} chapter of this manual. You
107 will run a backup to disk and a restore. Only when that works, should you
108 begin customization of the conf files.
110 Another reason that you can get authentication errors is if you are running
111 Multiple Concurrent Jobs in the Director, but you have not set them in the
112 File daemon or the Storage daemon. Once you reach their limit, they will
113 reject the connection producing authentication (or connection) errors.
115 If you are having problems connecting to a Windows machine that previously
116 worked, you might try restarting the Bacula service since Windows frequently
117 encounters networking connection problems.
119 Here is a picture that indicates what names/passwords in which files/Resources
122 \includegraphics{./Conf-Diagram.eps}
124 In the left column, you will find the Director, Storage, and Client
125 resources, with their names and passwords -- these are all in {\bf
126 bacula-dir.conf}. The right column is where the corresponding values
127 should be found in the Console, Storage daemon (SD), and File daemon (FD)
130 Another thing to check is to ensure that the Bacula component you are
131 trying to access has {\bf Maximum Concurrent Jobs} set large enough to
132 handle each of the Jobs and the Console that want to connect
133 simultaneously. Once the maximum connections has been reached, each
134 Bacula component will reject all new connections.
136 \label{AccessProblems}
138 \item [Bacula Runs Fine but Cannot Access a Client on a Different Machine.
140 \index[general]{Bacula Runs Fine but Cannot Access a Client on a Different
142 There are several reasons why Bacula could not contact a client on a
143 different machine. They are:
146 \item It is a Windows Client, and the client died because of an improper
147 configuration file. Check that the Bacula icon is in the system tray and the
148 the menu items work. If the client has died, the icon will disappear only
149 when you move the mouse over the icon.
150 \item The Client address or port is incorrect or not resolved by DNS. See if
151 you can ping the client machine using the same address as in the Client
153 \item You have a firewall, and it is blocking traffic on port 9102 between
154 the Director's machine and the Client's machine (or on port 9103 between the
155 Client and the Storage daemon machines).
156 \item Your password or names are not correct in both the Director and the
157 Client machine. Try configuring everything identical to how you run the
158 client on the same machine as the Director, but just change the Address. If
159 that works, make the other changes one step at a time until it works.
164 \item [My Catalog is Full of Test Runs, How Can I Start Over? ]
165 \index[general]{My Catalog is Full of Test Runs, How Can I Start Over? }
166 If you are using MySQL do the following:
170 cd <bacula-source>/src/cats
177 If you are using SQLite, do the following:
181 Delete bacula.db from your working directory.
182 cd <bacula-source>/src/cats
189 Then write an EOF on each tape you used with {\bf Bacula} using:
193 mt -f /dev/st0 rewind
198 where you need to adjust the device name for your system.
201 \item [I Run a Restore Job and Bacula Hangs. What do I do?]
202 \index[general]{I Run a Restore Job and Bacula Hangs. What do I do? }
203 On Bacula version 1.25 and prior, it expects you to have the correct tape
204 mounted prior to a restore. On Bacula version 1.26 and higher, it will ask
205 you for the tape, and if the wrong one is mounted, it will inform you.
207 If you have previously done an {\bf unmount} command, all Storage daemon
208 sessions (jobs) will be completely blocked from using the drive unmounted, so
209 be sure to do a {\bf mount} after your unmount. If in doubt, do a second {\bf
210 mount}, it won't cause any harm.
213 \item [I Cannot Get My Windows Client to Start Automatically? ]
214 \index[general]{I Cannot Get My Windows Client to Start Automatically? }
215 You are probably having one of two problems: either the Client is dying due
216 to an incorrect configuration file, or you didn't do the Installation
217 commands necessary to install it as a Windows Service.
219 For the first problem, see the next FAQ question. For the second problem,
221 \ilink{ Windows Installation instructions}{_ChapterStart7} in this
226 \item [My Windows Client Immediately Dies When I Start It ]
227 \index[general]{My Windows Client Immediately Dies When I Start It }
228 The most common problem is either that the configuration file is not where it
229 expects it to be, or that there is an error in the configuration file. You
230 must have the configuration file in {\bf
231 c:\textbackslash{}bacula\textbackslash{}bin\textbackslash{}bacula-fd.conf}.
233 To {\bf see} what is going on when the File daemon starts on Windows, do the
238 Start a DOS shell Window.
240 bacula-fd -d100 -c c:\bacula\bin\bacula-fd.conf
245 This will cause the FD to write a file {\bf bacula.trace} in the current
246 directory, which you can examine and thereby determine the problem.
249 \item [When I Start the Console, the Error Messages Fly By. How can I see
251 \index[general]{When I Start the Console, the Error Messages Fly By. How can I see them? }
252 Either use a shell window with a scroll bar, or use the gnome-console. In any
253 case, you probably should be logging all output to a file, and then you can
254 simply view the file using an editor or the {\bf less} program. To log all
255 output, I have the following in my Director's Message resource definition:
259 append = "/home/kern/bacula/bin/log" = all, !skipped
264 Obviously you will want to change the filename to be appropriate for your
268 \item [I didn't realize that the backups were not working on my Windows
269 Client. What should I do? ]
270 \index[general]{I didn't realize that the backups were not working on my Windows
271 Client. What should I do? }
272 You should be sending yourself an email message for each job. This will avoid
273 the possibility of not knowing about a failed backup. To do so put something
278 Mail = yourname@yourdomain = all, !skipped
283 in your Director's message resource. You should then receive one email for
284 each Job that ran. When you are comfortable with what is going on (it took me
285 9 months), you might change that to:
289 MailOnError = yourname@yourdomain = all, !skipped
294 then you only get email messages when a Job errors as is the case for your
297 You should also be logging the Director's messages, please see the previous
298 FAQ for how to do so.
301 \item [All my Jobs are scheduled for the same time. Will this cause
303 \index[general]{All my Jobs are scheduled for the same time. Will this cause
305 No, not at all. Bacula will schedule all the Jobs at the same time, but will
306 run them one after another unless you have increased the number of
307 simultaneous jobs in the configuration files for the Director, the File
308 daemon, and the Storage daemon. The appropriate configuration record is {\bf
309 Maximum Concurrent Jobs = nn}. At the current time, we recommend that you
310 leave this set to {\bf 1} for the Director.
313 \item [Can Bacula Backup My System To Files instead of Tape? ]
314 \index[general]{Can Bacula Backup My System To Files instead of Tape? }
315 Yes, in principle, Bacula can backup to any storage medium as long as you
316 have correctly defined that medium in the Storage daemon's Device resource.
317 For an example of how to backup to files, please see the
318 \ilink{Pruning Example}{PruningExample} in the Recycling
319 chapter of this manual. Also, there is a whole chapter devoted to
320 \ilink{Backing Up to Disk}{_ChapterStart39}.
323 \item [Can Bacula Backup and Restore Files Greater than 2 Gigabytes in
325 \index[general]{Can Bacula Backup and Restore Files Greater than 2 Gigabytes in
327 If your operating system permits it, and you are running Bacula version 1.26
328 or later, the answer is yes. To the best of our knowledge all client system
329 supported by Bacula can handle files larger than 2 Gigabytes.
332 \item [I Started A Job then Decided I Really Did Not Want to Run It. Is
333 there a better way than {\bf ./bacula stop} to stop it?]
334 \index[general]{I Started A Job then Decided I Really Did Not Want to
335 Run It. Is there a better way than ./bacula stop to stop it? } Yes,
336 you normally should use the Console command {\bf cancel} to cancel a Job
337 that is either scheduled or running. If the Job is scheduled, it will
338 be marked for cancellation and will be canceled when it is scheduled to
339 start. If it is running, it will normally terminate after a few
340 minutes. If the Job is waiting on a tape mount, you may need to do a
341 {\bf mount} command before it will be canceled.
344 \item [Why have You Trademarked the Name
345 Bacula\raisebox{.6ex}{{\footnotesize \textsuperscript{\textregistered}}}?]
346 \index[general]{Why have You Trademarked the Name
347 Bacula\textsuperscript{\textregistered}? }
348 We have trademarked the name Bacula to ensure that all media written by any
349 program named Bacula will always be compatible. Anyone may use the name
350 Bacula, even in a derivative product as long as it remains totally compatible
351 in all respects with the program defined here.
354 \item [Why is Your Online Document for Version 1.35 of Bacula when the
355 Currently Release Version is 1.34?]
356 \index[general]{Why is Your Online Document for Version 1.35 of Bacula when the
357 Currently Release Version is 1.34? }
358 As Bacula is being developed, the document is also being enhanced, more often
359 than not it has clarifications of existing features that can be very useful
360 to our users, so we publish the very latest document. Fortunately it is rare
361 that there are confusions with new features.
363 If you want to read a document that pertains only to a specific version,
364 please use the one distributed in the source code.
368 \item [How Can I Be Sure that Bacula Really Saves and Restores All Files? ]
369 \index[general]{How Can I Be Sure that Bacula Really Saves and Restores
370 All Files? } It is really quite simple, but took me a while to figure
371 out how to ``prove'' it. First make a Bacula Rescue disk, see the
372 \ilink{Disaster Recovery Using Bacula}{_ChapterStart38} of this manual.
373 Second, you run a full backup of all your files on all partitions.
374 Third, you run an Verify InitCatalog Job on the same FileSet, which
375 effectively makes a record of all the files on your system. Fourth, you
376 run a Verify Catalog job and assure yourself that nothing has changed
377 (well, between an InitCatalog and Catalog one doesn't expect anything).
378 Then do the unthinkable, write zeros on your MBR (master boot record)
379 wiping out your hard disk. Now, restore your whole system using your
380 Bacula Rescue disk and the Full backup you made, and finally re-run the
381 Verify Catalog job. You will see that with the exception of the
382 directory modification and access dates and the files changed during the
383 boot, your system is identical to what it was before you wiped your hard
385 Alternatively you could do the wiping and restoring to another computer
389 \item [I did a Full backup last week, but now in running an Incremental,
390 Bacula says it did not find a FULL backup, so it did a FULL backup. Why?]
391 \index[general]{I did a Full backup last week, but now in running an
392 Incremental, Bacula says it did not find a FULL backup, so it did a
393 FULL backup. Why? } Before doing an Incremental or a Differential
394 backup, Bacula checks to see if there was a prior Full backup of the
395 same Job that terminated successfully. If so, it uses the date that
396 full backup started as the time for comparing if files have changed. If
397 Bacula does not find a successful full backup, it proceeds to do one.
398 Perhaps you canceled the full backup, or it terminated in error. In
399 such cases, the full backup will not be successful. You can check by
400 entering {\bf list jobs} and look to see if there is a prior Job with
401 the same Name that has Level F and JobStatus T (normal termination).
403 Another reason why Bacula may not find a suitable Full backup is that
404 every time you change the FileSet, Bacula will require a new Full
405 backup. This is necessary to ensure that all files are properly backed
406 up in the case where you have added more files to the FileSet.
407 Beginning with version 1.31, the FileSets are also dated when they are
408 created, and this date is displayed with the name when you are listing
409 or selecting a FileSet. For more on backup levels see below.
411 \label{filenamelengths}
412 \item [How Can You Claim to Handle Unlimited Path and Filename Lengths
413 when All Other Programs Have Fixed Limits?]
414 \index[general]{How Can You Claim to Handle Unlimited Path and Filename
415 Lengths when All Other Programs Have Fixed Limits? } Most of those
416 other programs have been around for a long time, in fact since the
417 beginning of Unix, which means that they were designed for rather small
418 fixed length path and filename lengths. Over the years, these
419 restrictions have been relaxed allowing longer names. Bacula on the
420 other hand was designed in 2000, and so from the start, Path and
421 Filenames have been kept in buffers that start at 256 bytes in length,
422 but can grow as needed to handle any length. Most of the work is
423 carried out by lower level routines making the coding rather easy.
426 \item [What Is the Really Unique Feature of Bacula? ]
427 \index[general]{What Is the Really Unique Feature of Bacula? } Well, it
428 is hard to come up with unique features when backup programs for Unix
429 machines have been around since the 1960s. That said, I believe that
430 Bacula is the first and only program to use a standard SQL interface to
431 catalog its database. Although this adds a bit of complexity and
432 possibly overhead, it provides an amazingly rich set of features that
433 are easy to program and enhance. The current code has barely scratched
434 the surface in this regard (version 1.31).
436 The second feature, which gives a lot of power and flexibility to Bacula
437 is the Bootstrap record definition.
439 The third unique feature, which is currently (1.30) unimplemented, and
440 thus can be called vaporware :-), is Base level saves. When
441 implemented, this will enormously reduce tape usage.
445 \item [If I Do Run Multiple Simultaneous Jobs, How Can I Force One
446 Particular Job to Run After Another Job? ]
447 \index[general]{If I Do Run Multiple Simultaneous Jobs, How Can I Force One
448 Particular Job to Run After Another Job? }
449 Yes, you can set Priorities on your jobs so that they run in the order you
451 \ilink{the Priority record}{Priority} in the Job resource.
455 \item [I Am Not Getting Email Notification, What Can I Do? ]
457 \index[general]{I Am Not Getting Email Notification, What Can I Do? }
458 The most common problem is that you have not specified a fully qualified
459 email address and your bsmtp server is rejecting the mail. The next most
460 common problem is that your bsmtp server doesn't like the syntax on the From
461 part of the message. For more details on this and other problems, please see
463 \ilink{ Getting Email Notification to Work}{email} section of the
464 Tips chapter of this manual. The section
465 \ilink{ Getting Notified of Job Completion}{notification} of the Tips
466 chapter may also be useful. For more information on the {\bf bsmtp} mail
468 \ilink{bsmtp in the Volume Utility Tools chapter}{bsmtp} of this
473 \item [I Change Recycling, Retention Periods, or File Sizes in my Pool
474 Resource and they Still Don``t Work.]
475 \index[general]{I Change Recycling, Retention Periods, or File Sizes in my Pool
476 Resource and they Still Don"t Work. }
477 The different variables associated with a Pool are defined in the Pool
478 Resource, but are actually read by Bacula from the Catalog database. On
479 Bacula versions prior to 1.30, after changing your Pool Resource, you must
480 manually update the corresponding values in the Catalog by using the {\bf
481 update pool} command in the Console program. In Bacula version 1.30, Bacula
482 does this for you automatically every time it starts.
484 When Bacula creates a Media record (Volume), it uses many default values from
485 the Pool record. If you subsequently change the Pool record, the new values
486 will be used as a default for the next Volume that is created, but if you
487 want the new values to apply to existing Volumes, you must manually update
488 the Volume Catalog entry using the {\bf update volume} command in the Console
491 \label{CompressionNotWorking}
492 \item [I Have Configured Compression On, But None of My Files Are
494 \index[general]{I Have Configured Compression On, But None of My Files Are
496 There are two kinds of compression. One is tape compression. This is done by
497 the tape drive hardware, and you either enable or disable it with system
498 tools such as {\bf mt}. This compression works independently of Bacula.
500 Bacula also has compression code, which is normally used only when backing up
501 to file Volumes. There are two conditions for this ''software`` to become
505 \item You must have the zip development libraries loaded on your system when
506 building Bacula and Bacula must find this library, normally {\bf
507 /usr/lib/libz.a}. On RedHat systems, this library is provided by the {\bf
510 If the library is found by Bacula during the {\bf ./configure} it will be
511 mentioned in the {\bf config.out} line by:
520 \item You must add the {\bf compression=gzip} option on your Include
521 statement in the Director's configuration file.
525 \item [Bacula is Asking for a New Tape After 2 GB of Data but My Tape
527 \index[general]{Bacula is Asking for a New Tape After 2 GB of Data but My Tape
529 There are several reasons why Bacula will request a new tape.
532 \item There is an I/O error on the tape. Bacula prints an error message and
533 requests a new tape. Bacula does not attempt to continue writing after an I/O
535 \item Bacula encounters and end of medium on the tape. This is not always
536 distinguishable from an I/O error.
537 \item You have specifically set some size limitation on the tape. For example
538 the {\bf Maximum Volume Bytes} or {\bf Maximum Volume Files} in the
539 Director's Pool resource, or {\bf Maximum Volume Size} in the Storage
540 daemon's Device resource.
543 \label{LevelChanging}
545 \item [Bacula is Not Doing the Right Thing When I Request an Incremental
547 \index[general]{Bacula is Not Doing the Right Thing When I Request an Incremental
549 As explained in one of the previous questions, Bacula will automatically
550 upgrade an Incremental or Differential job to a Full backup if it cannot find
551 a prior Full backup or a suitable Full backup. For the gory details on
552 how/when Bacula decides to upgrade levels please see the
553 \ilink{Level record}{Level} in the Director's configuration
554 chapter of this manual.
556 If after reading the above mentioned section, you believe that Bacula is not
557 correctly handling the level (Differential/Incremental), please send us the
558 following information for analysis:
561 \item Your Director's configuration file.
562 \item The output from {\bf list jobs} covering the period where you are
564 \item The Job report output from the prior Full save (not critical).
565 \item An {\bf llist jobid=nnn} where nnn is the JobId of the prior Full save.
567 \item The Job report output from the save that is doing the wrong thing (not
569 \item An {\bf llist jobid=nnn} where nnn is the JobId of the job that was not
571 \item An explanation of what job went wrong and why you think it did.
574 The above information can allow us to analyze what happened, without it,
575 there is not much we can do.
578 \item [I am Backing Up an Offsite Machine with an Unreliable Connection.
579 The Director Waits Forever for the Client to Contact the SD. What Can I Do?]
580 \index[general]{I am Backing Up an Offsite Machine with an Unreliable Connection.
581 The Director Waits Forever for the Client to Contact the SD. What Can I Do?}
582 Bacula was written on the assumption that it will have a good TCP/IP
583 connection between all the daemons. As a consequence, the current Bacula
584 doesn't deal with faulty connections very well. This situation is slowly being
587 There are several things you can do to improve the situation.
590 \item Upgrade to version 1.32 and use the new SDConnectTimeout record. For
595 SD Connect Timeout = 5 min
600 in the FileDaemon resource.
601 \item Run these kinds of jobs after all other jobs.
605 \item [When I ssh into a machine and start Bacula then attempt to exit,
607 \index[general]{When I ssh into a machine and start Bacula then attempt to exit,
609 This happens because Bacula leaves stdin, stdout, and stderr open for debug
610 purposes. To avoid it, the simplest thing to do is to redirect the output of
611 those files to {\bf /dev/null} or another file in your startup script (the
612 RedHat autostart scripts do this automatically). For example, you start the
617 bacula-dir -c bacula-dir.conf ... 0>\&1 2>\&1 >/dev/null
622 and likewise for the other daemons.
624 \label{RetentionPeriods}
626 \item [I'm confused by the different Retention periods: File Retention,
627 Job Retention, Volume Retention. Why are there so many?]
628 \index[general]{I'm confused by the different Retention periods: File Retention,
629 Job Retention, Volume Retention. Why are there so many? }
630 Yes, this certainly can be confusing. The basic reason for so many is to
631 allow flexibility. The File records take quite a lot of space in the catalog,
632 so they are typically records you want to remove rather quickly. The Job
633 records, take very little space, and they can be useful even without the File
634 records to see what Jobs actually ran and when. One must understand that if
635 the File records are removed from the catalog, you cannot use the {\bf
636 restore} command to restore an individual file since Bacula no longer knows
637 where it is. However, as long as the Volume Retention period has not expired,
638 the data will still be on the tape, and can be recovered from the tape.
640 For example, I keep a 30 day retention period for my Files to keep my catalog
641 from getting too big, but I keep my tapes for a minimum of one year, just in
644 \label{MaxVolumeSize}
645 \item [Why Does Bacula Ignore the MaxVolumeSize Set in my Pool?]
646 \index[general]{Why Does Bacula Ignore the MaxVolumeSize Set in my Pool? }
647 The MaxVolumeSize that Bacula uses comes from the Media record, so most
648 likely you changed your Pool, which is used as the default for creating Media
649 records, {\bf after} you created your Volume. Check what is in the Media
658 If it doesn't have the right value, you can use:
668 \label{ConnectionRefused}
669 \item [In connecting to my Client, I get ''ERR:Connection Refused. Packet
670 Size too big from File daemon:192.168.1.4:9102`` Why?]
671 \index[general]{In connecting to my Client, I get ``:Connection Refused.
672 Packet Size too big from File daemon:192.168.1.4:9102'' Why? }
673 This is typically a communications error resulting from one of the following:
677 \item Old versions of Bacula, usually a Win32 client, where two threads were
678 using the same I/O packet. Fixed in more recent versions. Please upgrade.
679 \item Some other program such as an HP Printer using the same port (9102 in
683 If it is neither of the above, please submit a bug report at
684 \elink{bugs.bacula.org}{http://bugs.bacula.org}.
686 Another solution might be to run the daemon with the debug option by:
690 Start a DOS shell Window.
692 bacula-fd -d100 -c c:\bacula\bin\bacula-fd.conf
697 This will cause the FD to write a file {\bf bacula.trace} in the current
698 directory, which you can examine to determine the problem.