Hello everyone...
Bryan, that was a very good idea, but did not solved entirely... The thing
is, in my SD server, I have one Device for Incremental and another for
Diff/Full backup. In my Schedule resource, I have this:
Run = Level=Incremental Pool=pool.inc FullPool=pool.full feb-jun on 1st sat
at 23:00
The FullPool parameter is very important, because if a Job is ran by this
Schedule and a Full backup has never been done before, Bacula will upgrade
this Job to a Full Backup and then will use the values in the Pool
"pool.full" to put the Backup data in.
Since I had to remove de "Storage" option from the Pool resource, every
time Bacula upgrade a Job from Inc to Full, it does not change de Storage,
so it stops asking to mount a new volume...
NOW I'm completely stuck, don't know what to do... Any help would be very
much appreciated...
Thanks!
2012/5/28 Rodrigo Renie Braga <rodrigore...@gmail.com>
> Bryan, that ideia is just BRILLIANT!!!! It worked like a charm...
>
> With only one note: I was using the "storage" option inside the Pool
> resource (not in the Job), and apparently the Pool resource overrides any
> other resources, so I just had to remove this option from the Pool to add
> it to the Job resource for each client...
>
> Once again, Bacula did not let me down, neither did this mailing list...
>
> Thanks again Bryan!
>
>
> 2012/5/28 Bryan Harris <bryanlhar...@gmail.com>
>
>> Hello,
>>
>> On May 27, 2012, at 11:28 PM, Rodrigo Renie Braga wrote:
>>
>> My ideal solution which Bacula, apparently, DOES NOT SUPPORT: make the
>> "Address" option on the Storage resource optional, meaning that if not
>> specified, the SD Address that Bacula will send to the FD is the same one
>> that the Director used to connect on the FD on the first place. That would
>> be just awesome…
>>
>>
>> For each vlan, can you create a new storage resource within the director?
>> Each storage resource change the name of the storage resource plus change
>> the address of the storage resource (Address, not SDAddress).
>>
>> You only have need of one single storage daemon, because this one daemon
>> listens on *all* IP addresses (if you remove the SDAddress option).
>>
>> However, I think you can have as many "pointers" to this storage daemon
>> as you want. Each one has a unique name and points to a unique IP address,
>> but really they are all pointing to the same storage daemon. And this one
>> daemon listens on all available addresses of the machine (if you remove the
>> SDAddress option).
>>
>> Then in your job config,
>>
>> job = job1
>> storage = storage_on_vlan1
>> ...
>> job = job2
>> storage = storage_on_vlan2
>> …
>> job = job3
>> storage = storage_on_vlan3
>>
>> And so on.
>>
>> Bryan
>>
>
>
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
