ADSM-L

Re: Server 3.1.2.1 file expiration/back file versioning

2015-10-04 17:47:37
Subject: Re: Server 3.1.2.1 file expiration/back file versioning
From: Remeta, Mark [mailto:MRemeta AT SELIGMANDATA DOT COM]
To: ADSM-L AT VM.MARIST DOT EDU
How can one tell if files are not being expired? Does it log a error message
in the accounting log or something?
Also I did a search for the apar IX85298 and couldn't find anything. I also
could find the fix mentioned for Windows NT. Is there one available for
Windows NT?

Thanks in advance,
Mark


> -----Original Message-----
> From: Colin Dawson [SMTP:redhead AT US.IBM DOT COM]
> Sent: Friday, February 05, 1999 4:10 PM
> To:   ADSM-L AT VM.MARIST DOT EDU
> Subject:      Server 3.1.2.1 file expiration/back file versioning
>
> ADSMer's,
>
>      The ADSM server ptf 3.1.2.1 had an error in the file versioning
> algorithm for backup file processing.  The error was that files that
> exceeded the version constraints for the appropriate policy were not
> marked
> for expiration.  As a result of this, files were not being versioned
> properly and expired.  This error can cause DB utilitization and storage
> pool space to increase as more files are being kept on the server than
> necessary.  The apar that documents this error is IX85298.  In response to
> this error, an emergency fix ptf is available on index.storsys.ibm.com
> under the directory /adsm/fixes/v3r1 and look in the platform appropriat
> directory.  For example, the aix emergency fix is located in
> /adsm/fixes/v3r1/aixsrv/3.1.2.13/IX85298.bff.  This fix corrects the
> versioning algorithm and as files are subsequently backed-up, the
> versioning will be corrected and expiration for these files will again
> process as normal.
>
> -------------------------------------------
> Colin Dawson
> ADSM Server Development
<Prev in Thread] Current Thread [Next in Thread>