-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I'm not under the impression that anything changed with Max Wait Time
anyway.
Christian Sakshaug wrote:
> You have probability right, RelaseNotes file :)
>
> But I cannot se anything about "Max Wait Time", only perhaps.
>
> "- New Client Connect Wai
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,
Christian Sakshaug
Ryan Novo
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Christian Sakshaug wrote:
> Good morning
>
> It seems like everything is just fine again. Last night I removed the
> "Max Wait Time" from the job resource and everything works again (every
> job is OK).
>
> I have probably used the "Max Wait Time"
Good morning
It seems like everything is just fine again. Last night I removed the
"Max Wait Time" from the job resource and everything works again (every
job is OK).
I have probably used the "Max Wait Time" wrong in my configuration.
What about to make a "Migrate from ver >= ver" section in t
After some more testing it seems that the backup also stops when only
running alone.
I cannot see any pattern now. It seems thats jobs with small amounts and
large amounts of data/files have problems running alone or concurrent
with other jobs.
The client in this job is the same server that ar
Hey
Have tested some more now, it seems that jobs that I was getting error
after "normal schedule" is working when I have a small number of
concurrent jobs running.
I wonder what have been change since 2.0.3 that could have this affects?
I have been reading the changelog and documentation and
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 start and when you start a second run
the console freeze up for about 2 minutes and then everything is normal
again, is this normal.
Thanks
Christoff
On Thursday 13 Se
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
