Generally seen with cached diskpools and files that grow with compression... TSM pre-allocates based on listed size by the OS and in the case of cached diskpools, frees that amount of cached space to take the file. If you have compression yes and compressalways yes AND if a file grows during compression, then you will see the failure such as listed below... To avoid such situations use "compression yes" and "compressalways no" and that will generally prevent this problem.
Dwight E. Cook Software Application Engineer III Science Applications International Corporation 509 S. Boston Ave. Suit 220 Tulsa, Oklahoma 74103-4606 Office (918) 732-7109 -----Original Message----- From: Farren Minns [mailto:[EMAIL PROTECTED]] Sent: Tuesday, April 02, 2002 3:16 AM To: [EMAIL PROTECTED] Subject: Client Message - size estimate exceeded Hi TSMers TSM server 3.7.3.8 running on Solaris 2.7 machine. Getting the following message for one of our NT client nodes. 04/01/02 22:14:20 ANR0534W Transaction failed for session 43012 for node PUBEARLY (WinNT) - size estimate exceeded and server is unable to obtain additional space in storage pool BACKUPPOOL. I have looked at the help for the message and from what I can see there are a number of possible reasons. But I have never seen it before for any client and was wondering is anyone out there had had dealings with this and what remedies they used to solve it. The backup eventually completes OK with just one failed file. Unfortunately, I cannot see which one as the person in charge of the NT machines is away on holiday at the moment. I would like to gather some more inf. before I next speak to him. Can anyone help with this one. Many thanks in advance All the best Farren Minns - Trainee Solaris & TSM system admin. John Wiley & Sons Ltd
