Mark,
Thanks for the reply. I was talking with the DBA for the client in question.
It looks like he requires 130gb and the diskpool's estimated capacity in
MB's is 107668.0
It sounds like we are going to have to buy more disk.
Tommy
----- Original Message -----
From: "Darby, Mark" <Mark.Darby AT HQ.DOE DOT GOV>
To: <ADSM-L AT VM.MARIST DOT EDU>
Sent: Monday, February 10, 2003 5:53 PM
Subject: Re: Diskpool error
> Tommy, the following must be true for the situation in question:
> 1. the disk storage pool in question has CACHE turned on
> 2. COMPRESSION=YES is in effect for the client in question
> 3. COMPRESSALWAYS=NO is NOT in effect for the client in question
> 4. the file being backed up at the time of the error was growing as a
result
> of compression
>
> The reason it is happening is because the above are all in effect and is
> explained by the following partial description of the backup process:
> 1. when a file is to be backed up by the client, it provides the server
with
> an estimate of the amount of space required to store the file
> 2. when, because of compression, a file grows during the backup, the
client
> revises its estimate with the server and, when COMPRESSALWAYS=YES (the
> default) is in effect, continues sending the file, still compressing it
> 3. when CACHE is "turned on" for the storage pool in question, the server
> does not check the "CACHEd file space" for room based on the revised
> estimate (even though it does so at the beginning - in step 1 above)
> 4. if the server does not find "actual free space" (not including cached
> file space that COULD be freed to make room to store the file), the server
> responds as indicated in your problem situation.
>
> There are lots of ways to solve this problem, including using
> COMPRESSALWAYS=NO or turning off COMPRESSION altogether (e.g.,
> COMPRESSION=NO), or (just for the file in question) using (if supported by
> the client platform/level) exclude.compression.
>
> You can also turn off caching for the storage pool in question - does it
> actually provide you any real benefit, anyway?
>
> Regards,
> Mark
>
> -----Original Message-----
> From: Tommy Templeton
> To: ADSM-L AT VM.MARIST DOT EDU
> Sent: 2/10/03 5:38 PM
> Subject: Diskpool error
>
> I got this error during one of my weekend backups. Is anyone else
> familiar with diskpool errors like this? Thanks.
>
> 02/09/03 03:44:25 ANR0534W Transaction failed for session 184 for node
>
> SP2MN5F0 (DB2/6000) - size estimate exceeded and server
>
> is unable to obtain additional space in storage pool
>
> DISKPOOL.
>
>
>
> Tommy Templeton
> Senior System Administrator
> DFA-MMRS
> 601-359-3106
> e-mail - templeton AT mmrs.state.ms DOT us
|
