I have had many problems with caching turned on for storage pools.  It seems
that the backup attempts to calculate the amount of space needed to store
the object, but if the object is compressed, and compression is turned on,
the size of the object can actually expand, making it too big to be stored
in the storage pool, and you will receive the message.

There may be other options that you can set on the caching to eliminate the
problem, but I always just turned caching off not wanting to deal with it.

Does this sound like something that could be happending to you?

bob

On Fri, Jan 09, 2004 at 11:22:47AM -0600, Coats, Jack wrote:
> My environment is Windows 2K with TSM 4.2.3.1 ... yep it is old, but
> hopefully in May we can upgrade :)
>
> I have one client that is getting this mesage ( server out of storage) and
> the backup fails.
>
> The diskpool where the backups go is about 200G with caching turned on
> (should hold
> a couple of days of backups) and the database and recovery logs have had a
> high water
> mark of about 71% and 26% respectively (currently about 70% and 0.4%).
>
> Where should I be looking for the problem?
>
> I see nothing in the servers log files that are related.
>
> ... Jack