On 10/01/17 22:25, Alan Brown wrote:
> On 10/01/17 06:04, Charles wrote:
>>
>> Have modified /etc/init.d/bacula-sd (Debian Jessie), adding mt rewoffl
>> and
>> mtx unload commands immediately before bacula-sd is started.
>>
>
> That should do the trick, although I'd add mt unlock to make absolutely
On 09/01/17 23:01, Dimitri Maziuk wrote:
>
> What are you trying to achieve? I agree that "virtual autochanger" is a
> mind boggle with no obvious practical use, but why are you looking at it
> in the first place?
The primary advantage of the virtual autochanger is you can more easily
use removab
On 10/01/17 06:04, Charles wrote:
>
> Have modified /etc/init.d/bacula-sd (Debian Jessie), adding mt rewoffl
> and
> mtx unload commands immediately before bacula-sd is started.
>
That should do the trick, although I'd add mt unlock to make absolutely
sure.
>> ...
>> Other than that: update vol
On Tuesday 2017-01-10 08:51:15 Lloyd Brown wrote:
> On 01/09/2017 01:11 PM, Josip Deanovic wrote:
> > I have never needed it but I have tested few minutes ago and I can
> > confirm that it works as expected.
> > In my test I have configured a restore job and added a line such as
> > this: ClientRun
On 1/10/2017 4:49 AM, Timo Neuvonen wrote:
>
> I'm not trying to achieve anything special, I'm rather trying to avoid doing
> anything unnecessarily complicated.
> I just want to set up (and to fully understand my set-up) a simple but
> working file storage device for a small business / home offi
On 2017-01-10 03:49, Timo Neuvonen wrote:
> What confused me is that the example conf files supplied with current Bacula
> releases don't give an example of the very basic disk-based setup, but just
> show how to setup a virtual disk autochanger.
> The whitepapers that Kern referred gave me an imp
On 01/09/2017 01:11 PM, Josip Deanovic wrote:
>
> I have never needed it but I have tested few minutes ago and I can
> confirm that it works as expected.
> In my test I have configured a restore job and added a line such as this:
> ClientRunAfterJob = "/etc/bacula/scripts/bla"
>
> It will run on t
Hi there.I have the following definition in my catalog backup based on the DiskBakupDesign White paper, which is not running.What am I doing wrong? Thanks for your time.-fuz# Backup the catalog database (after the nightly save)Job { Name = "BackupCatalog" JobDefs = "DefaultJob" Level = Full FileS
> > I'm still wondering if this really is the
> > simplest way of implementing the file storage?
> >
> > What would I lose if I simply had only one of the two device resources,
> > no autochanger resource at all, and the jobs would refer directly to the
> > device resource? I think it should work t
