Hi,
I'm having a big problem with my bacula configuration.
It is supposed to create a new large archive every time a job is run,
with a.o. the job name and start date and time in the name.
Now some time ago I changed this scheme, made it small chunks (50 MB),
many chunks for one archive. I didn'
I am, but not in a way that makes much difference to you.
I have a script that moves backup disk volumes in a particular directory
that are older than a certain number of days to Glacier; the volumes in
that directory get populated by migration jobs from the primary pool.
I'm skeptical about doin
On 5/3/2013 4:56 PM, Dimitri Maziuk wrote:
> On 05/03/2013 02:53 PM, Josh Fisher wrote:
>
>> ... What you are
>> considering would require a new device assignment each time a new volume
>> is needed. While possible, it is way more complex that it appears at
>> first glance.
> PS. I think the potent
