Another thing to try is to add a separate exclude block to the fileset.
/Jens
> So nobody knows what does it mean?
>
> 08-Apr 11:08 backup-dir: Start Backup JobId 341, Job=poh.2005-04-08_11.08.34
> 08-Apr 11:08 backup-dir: poh.2005-04-08_11.08.34 Fatal error: FD gave bad
> response to Include
What happens if you replace the "@" with a "<" ?
/Jens
> So nobody knows what does it mean?
>
> 08-Apr 11:08 backup-dir: Start Backup JobId 341, Job=poh.2005-04-08_11.08.34
> 08-Apr 11:08 backup-dir: poh.2005-04-08_11.08.34 Fatal error: FD gave bad
> response to Include command: wanted 2000 O
What's working and what's not? Can you see any pattern (backuplevel, OS etc) It
might be compatibility issues between 1.36.2 and 1.34.2.
/Jens
> On server side is 1.36.2
>
> On client side machines are Solaris, FreeBSD and Linux with following
> versions: 1.36.2 and 1.34.2
>
> Incremintal j
