You have probability right, RelaseNotes file :)
But I cannot se anything about "Max Wait Time", only perhaps.
"- New Client Connect Wait directive in Storage daemon so that
users can configure how long SD waits for FD connection."
Anyway, it works :-)
Regards,
Chris
o important between the "major updates, 1.x to 2.x"
but between 2.0.3 to 2.2.0, 2.2.0 -> 2.2.3 has been nice.
Perhaps you guys have allready written that, perhaps I have miss it.
Regards,
Christian Sakshaug
Christian Sakshaug skrev:
> Hey
>
> Have tested some more now,
no
Encryption: no
Volume name(s): CLIENT-Daily-0001
Volume Session Id: 1
Volume Session Time:1189666879
Last Volume Bytes: 8,468,272,411 (8.468 GB)
Non-fatal FD errors:0
SD Errors: 0
FD termination status: Ca
having trouble with both. But with the third (running 2.0.3)
everything is working great/normal.
Regards
Christian Sakshaug
Christoff van Zyl skrev:
> On this subject, I have upgraded from 2.0.3 to 2.2.3 and had the following
> problem.
>
> If you start a manual run, the first job s
Hey
After upgrading to 2.2.3 i'm getting a lot of problems with backup. With
2.0.3 everything worked just great.
Have around XX jobs running from around 00:30 to 06:00 to different
harddrive devices. The storage is against a enterprise DAS's with a fast
frontend server with lots of memory/cpu
Hello people
Anyone have a clue what is wrong here?
My system is Slackware with "Linux 2.6.17.8 SMP"
---
cd bacula-1.38.11/
./configure \
--prefix=/var/bacula \
--sbindir=/usr/sbin \
--bindir=/usr/bin \
--with-job-email=$EMAIL \
--with-dump-email=$EMAIL \
): ***-0001
Volume Session Id: 14
Volume Session Time:1154721554
Last Volume Bytes: 14,817,297,503 (14.81 GB)
Non-fatal FD errors:3
SD Errors: 0
FD termination status: OK
SD termination status: OK
Termination:
