Isabel,

If this is B/A client, the problem is with the compression. Try
COMPRESSALWAYS NO. It has its own pros & cons.
If its is TDP, problems are different and need different approach. Look
what Gerhard wrote about TDPI.

Zlatko Krastev
IT Consultant




Please respond to "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
Sent by:        "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
To:     ADSM-L AT VM.MARIST DOT EDU
cc:

Subject:        Re: ANR0534W - size estimate exceeded

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
>