|
Hello,
Probably the best source of information for how to "debug" problems such as you are having is the Windows chapter of the manual. Specifically it tells you how to get debug output, and for connection problems you should invoke the command line with -d50 or greater. For SD problems, you will, of course, have to run a backup job from the Director while this debug trace is turned on. You can also turn on trace output for the SD, which is *much* simpler. The manual is a bit old and out of date, but what is written is still valid. That said, for getting trace output, it is probably easier to turn on as well as turn on output to a trace file by using the bconsole "setdebug" command. Again the manual (Console manual) explains the setdebug command in more detail. Best regards, Kern On 09/06/2016 11:49 AM, Hodges wrote:
|
------------------------------------------------------------------------------
_______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
