On Monday 24 July 2006 13:47, Henning Holtschneider wrote:
> Hi,
>
> I upgraded our Bacula server from 1.36.3 to 1.38.11. Since then, I cannot
> run incremental backup jobs on some (!) clients anymore. All I get is this:
Meanwhile, I solved my problems: two clients were still running Bacula 1.34
Hi,
I upgraded our Bacula server from 1.36.3 to 1.38.11. Since then, I cannot run
incremental backup jobs on some (!) clients anymore. All I get is this:
24-Jul 00:00 weissnich-dir: Start Backup JobId 1762,
Job=webfarm3.2006-07-23_23.50.04
24-Jul 00:00 weissnich-dir: webfarm3.2006-07-23_23.50.0
Hello list,
Phil Stracchino wrote:
Sebastian Haas wrote:
Phil Stracchino wrote:
As I promised yesterday, here are the logs. I've enabled debug=100 but
only the FD prints a lot of messages (see attachment), this is what the
DIR prints (I've canceld the job after 15min., cause I saw that bacula
b
Sebastian Haas wrote:
> Phil Stracchino wrote:
>
>>Sebastian Haas wrote:
>>If they changed again today, they should be saved again; otherwise, not.
>> However, I don't expect this to fix your main problem; it will only fix
>>that "DIR and FD clocks differ" warning.
>
> Okay you are right, this do
Phil Stracchino wrote:
> Sebastian Haas wrote:
> If they changed again today, they should be saved again; otherwise, not.
> However, I don't expect this to fix your main problem; it will only fix
> that "DIR and FD clocks differ" warning.
Okay you are right, this doesn't fixed the problem but the
Sebastian Haas wrote:
>>>As the jobs started I've noticed the following message from the director:
>>>29-Sep 00:52 fileserver01-fd: DIR and FD clocks differ by -730 seconds,
>>>FD automatically adjusting.
>>>
>>>The director started the job at 1:05am while the FD's clock was 00:52.
>>>But I would a
Hello,
Phil Stracchino wrote:
> Sebastian Haas wrote:
>
>>I've did a incremental backup last night and I notice that the backup
>>was bigger than I did assumed.
>>
>>I did then an "bls" to show which files bacula backed up, and the most
>>of the files bacula backed up shouldn't changed to the las
Sebastian Haas wrote:
> I've did a incremental backup last night and I notice that the backup
> was bigger than I did assumed.
>
> I did then an "bls" to show which files bacula backed up, and the most
> of the files bacula backed up shouldn't changed to the last backup. By
> the way, I did a full
Dear list,
I've did a incremental backup last night and I notice that the backup
was bigger than I did assumed.
I did then an "bls" to show which files bacula backed up, and the most
of the files bacula backed up shouldn't changed to the last backup. By
the way, I did a full back yesterday.
But
