I run into the problem when compression is set on for the client and a file
grows on compression.

TSM allocates space based on the original size of the file. When the file
grows,  there is no longer space for it.

Add
  COMPRESSALWAYS NO

  to the dsm.opt file.


At 11:22 AM 09/01/2004 -0600, you 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.

 -----------------------------------------------------------
   Don Coleman,
   Queen's University Information Technology Services
   Kingston, Ont. Canada  K7L 3N6
   Tel: (613) 533-2034  Fax: (613) 533-2168
   Email: Coleman AT Post.QueensU DOT CA