Thanks for responses!

I will try the following:
1) set highmig fairly low during main backup time so there'll be enough space in
diskpool
2) set maxsize to a value that I know is lower than the filesizes where the
message occurs

Still it would be better to solve the actual problem: the TSM-Client sending the
wrong filesize!!!

Greetings,
Isabel

Tomas Hrouda schrieb:

> Gerhardt,
>
> sending of incorrect filesize obviously happens (by my experiences) when
> commpression is turned on and compressed file grows up to original file. Try
> to use no compression or COMPRESSALWAYS NO to avoid bad file size prediction
> by client. It was discussed here sometimes in the past.
>
> Hope this helps.
> Tom
>