On Wed, Aug 24, 2011 at 1:50 AM, Olle Romo wrote:
>
> On Aug 23, 2011, at 8:43 AM, Adrian Reyer wrote:
>
>> On Tue, Aug 23, 2011 at 01:38:23AM +0200, Olle Romo wrote:
>>> What I mean is that if I have a drive removed, run the job then
>>> attach
>>> the drive and run the job again, Bacula will do
On Aug 23, 2011, at 8:43 AM, Adrian Reyer wrote:
> On Tue, Aug 23, 2011 at 01:38:23AM +0200, Olle Romo wrote:
>> What I mean is that if I have a drive removed, run the job then
>> attach
>> the drive and run the job again, Bacula will do a full backup of the
>> drive even if it previously had d
On Tue, Aug 23, 2011 at 01:38:23AM +0200, Olle Romo wrote:
> What I mean is that if I have a drive removed, run the job then attach
> the drive and run the job again, Bacula will do a full backup of the
> drive even if it previously had done an incremental backup on the same
> drive. Ideally
What I mean is that if I have a drive removed, run the job then attach
the drive and run the job again, Bacula will do a full backup of the
drive even if it previously had done an incremental backup on the same
drive. Ideally I want it to just continue the incremental backup.
At the moment I
Am Wed, 10 Aug 2011 09:43:05 +0200 schrieb Olle Romo:
> Thank you Uwe. I misunderstood the concept.
>
> Is there a way to have Bacula just continue incremental backup of a
> drive even if it was offline for one run?
>
IMHO no, it will fail if a path is not available.
you could create a sort o
Thank you Uwe. I misunderstood the concept.
Is there a way to have Bacula just continue incremental backup of a
drive even if it was offline for one run?
All best,
Olle
On Aug 9, 2011, at 9:22 AM, Uwe Schuerkamp wrote:
> On Tue, Aug 09, 2011 at 06:07:41AM +0200, Olle Romo wrote:
>> Hi All,
>
On Tue, Aug 09, 2011 at 06:07:41AM +0200, Olle Romo wrote:
> Hi All,
>
> 'Ignore Fileset Changes = yes' doesn't seem to have the effect I was
> hoping for... If a drive is missing on one run, the next time Bacula
> sees the drive it will proceed to backup the entire thing again. I'm
> sure t
Hi All,
'Ignore Fileset Changes = yes' doesn't seem to have the effect I was
hoping for... If a drive is missing on one run, the next time Bacula
sees the drive it will proceed to backup the entire thing again. I'm
sure there's an obvious way to avoid this but I can't seem to find
it... An
Hi,
Thank you for answering.
So as you say the problem is that Bacula checks only the FileSet resource
and not the contents.
Good to know :D
I solved the problem making more or less what I expected, so my client is
saving md5 of the fileset content and comparing before starting the Backup.
T
Hello,
On 5/5/2007 11:41 AM, viashino wrote:
> Hi,
>
> I'm still trying to understand why my setup isn't working as expected.
> I did some tests (thx Arno for pointing me) about the Ignore FileSet
> Changes option.
> This option should be "no" by default as stated on the manual.
Right.
> Here
Hi,
I'm still trying to understand why my setup isn't working as expected.
I did some tests (thx Arno for pointing me) about the Ignore FileSet
Changes option.
This option should be "no" by default as stated on the manual.
Here what I did:
- I added the directive (forced to no) in the example c
Hi,
On 11.11.2005 18:32, John Kodis wrote:
I recently set up Bacula and did a full backup about a week ago, and a
number of incremental since. I then added an additional directory to
the exclude section of the file set resource, and as would be
expected, this caused Bacula to upgrade the next
I recently set up Bacula and did a full backup about a week ago, and a
number of incremental since. I then added an additional directory to
the exclude section of the file set resource, and as would be
expected, this caused Bacula to upgrade the next backup from
incremental to full. I don't want
13 matches
Mail list logo
