Hallo

Paul Bijnens wrote:

Stefan Noll wrote:

The mangled name I found in log.20040525.0 but not in amdump.1

It really helps if you post that line :-) .
Debugging is difficult using paranormal means.
Is the line above/after normal?

backupserver: log.20040525.0

...
DISK planner neptun /etc
DISK planner neptun /usr/local/sbin
START planner date 20040525
INFO planner Adding new disk neptun:/var/samba/projekte/Laufende/BDS.
START taper datestamp 20040525 label metrix00074 tape 0

INFO planner Incremental of helix:/var/backup/helix bumped to level 2.
...

In amdump.1 everything looks OK.

planner: time 0.627: setting up estimates for neptun:/var/samba/projekte/Laufende/Klingelnberg neptun:/var/samba/projekte/Laufende/Klingelnberg overdue 5 days for level 0 setup_estimate: neptun:/var/samba/projekte/Laufende/Klingelnberg: command 0, options:

    last_level 1 next_level0 -5 level_days 3
    getting estimates 0 (45620) 1 (60) -1 (-1)

That's only the setup for estimate.  What does the result show?
It looks like:

planner: time 80.851: got result for host neptun disk /: 0 -> 45620K, 1 -> 60K, -1 -> -1K

I found in amdump.1 long

What the client sent, yes, but what the server received, we don't know.