ad a successful full backup,
> other than the initial one I made before I let him get his hands on
> it. But it has had incrementals most days and many virtual fulls. I
> feel confident that I could restore every valuable file from that
> laptop, though it regularly has failed jobs.
d incrementals most days and many virtual fulls. I
> feel confident that I could restore every valuable file from that
> laptop, though it regularly has failed jobs.
>
>>
>> On 08/14/2013 03:37 PM, Barak Griffis wrote:
>>> Feel free to direct me to a URL, since t
*immensely* when everything has
ground to a halt during a business day and you're explaining that the
restore will take that same 8+ hours, and may have to start over
completely because your links are bad. At restore time, I'd much
rather be restoring at near wire speed from a local s
That's not friendly with unstable/slow links... Does anyone have any
other insightful ideas on how to handle this sort of situation? If I
can't ever get a full because of unstable links then bacula is useless
in my particular setup.
On 08/14/2013 08:59 AM, John Drescher wrote:
>> Feel free to
Feel free to direct me to a URL, since this seems like an obvious newb
question, but I don't see an obvious search result on the webs.
If a job gets interrupted (say network drops out midway through a
full). What happens the next time? does it pick up where it left off
or does it start over?
Ok, thanks!
On 2013-07-25 12:19, John Drescher wrote:
>> So when I make a config change I need to 'reload' and 'update xxx' ?
>
> Configuration changes that involve existing pools or volumes will
> require this.
>
> John
-
So when I make a config change I need to 'reload' and 'update xxx' ?
Barak
On 2013-07-25 09:21, John Drescher wrote:
> On Thu, Jul 25, 2013 at 9:56 AM, Barak Griffis
> wrote:
>> I restarted all 3 daemons many times, but no I didn't 'update pool
>>
r was it a side-effect?
Thanks,
Barak
On 2013-07-25 07:11, Uwe Schuerkamp wrote:
> On Wed, Jul 24, 2013 at 11:22:21AM -0500, Barak Griffis wrote:
>> For some reason, bacula insists on autolabeling with a format of
>> 'TestA-n' where n is the incrementing number. Any i
I'm new to bacula, so take it easy on me.
bacula-sd.conf:
Device {
Name = BacZFS_StDev1
Media Type = BacZFS_StDev1
Archive Device = /bacula_tank/BacZFS_StDev1
LabelMedia = yes;
Random Access = Yes;
AutomaticMount = yes;
RemovableMedia = no;
AlwaysOpen = no;
}
Device {
N
