Re: [Bacula-users] Is Virtual Autochanger for Multiple Disks writing still working?

2017-01-17 Thread Josh Fisher
On 1/17/2017 12:14 PM, Heitor Faria wrote: Hello Heitor, Hello, Kern! Thanks for the quick reply. Bacula is quite literal (i.e. any spurious characters can cause problems). Please try replacing your: Changer Command = "/dev/null" with either: Changer Command =

Re: [Bacula-users] Is Virtual Autochanger for Multiple Disks writing still working?

2017-01-17 Thread Heitor Faria
> Hello Heitor, Hello, Kern! Thanks for the quick reply. > Bacula is quite literal (i.e. any spurious characters can cause problems). > Please try replacing your: > Changer Command = "/dev/null" > with either: > Changer Command = /dev/null > or > Changer Command = "" I tried both ways. Now

Re: [Bacula-users] Is Virtual Autochanger for Multiple Disks writing still working?

2017-01-17 Thread Kern Sibbald
Hello Heitor, Bacula is quite literal (i.e. any spurious characters can cause problems). Please try replacing your: Changer Command = "/dev/null" with either: Changer Command = /dev/null or C

[Bacula-users] Is Virtual Autochanger for Multiple Disks writing still working?

2017-01-17 Thread Heitor Faria
Hello, Bacula Users, I'm setting up an environment according to the "2.2 Using a Virtual Autochanger" section of: http://blog.bacula.org/whitepapers/CommunityDiskBackup.pdf Using: 7.4.4 (20 September 2016) x86_64-unknown-linux-gnu debian 7.7 version, built from source. I remember it used to

Re: [Bacula-users] How to fix Bacula after tape autoloader dysfunction?

2017-01-17 Thread Charles
On 12/01/17 16:17, Charles wrote: ... > To be thorough, the bacula-sd init script should not only run the mt > rewoffl and mtx unload commands; it should also error trap their output. > I suspect that, when our autoloader and backup server are powered up at > the same time, the autoloader does not

Re: [Bacula-users] Restore problem out of the blue - scratch pool is suddenly "invalid"

2017-01-17 Thread Kern Sibbald
Hello Phil, I have not yet figured out what is going wrong here, or what triggered Bacula to think it is trying to use a Volume directly from the Scratch pool. I am going to look at the code in more detail to see if I can find the problem. In any case, I am planning to remove the code as in