ADSM-L

Betr.: Server 3.1.2.1 file expiration/back file versioning

1999-02-06 05:26:00
Subject: Betr.: Server 3.1.2.1 file expiration/back file versioning
From: "Hensel, Matthias" <Matthias.Hensel AT SCHERING DOT DE>
Date: Sat, 6 Feb 1999 11:26:00 +0100
     Where is the fix to be found?

     As well on index.storsys... as in Karlsruhe I am not able to locate
a
     directory .../3.1.2.13 as mentioned below?

     Whats wrong?

     Matthias


____________________________ Antwort-Abtrennung
________________________________
Betreff: Server 3.1.2.1 file expiration/back file versioning
Autor:  ,Colin Dawson [SMTP:redhead AT US.IBM DOT COM] bei BE2183
Datum:    05.02.99 22:09


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
Colin Dawson
ADSM Server Development
<Prev in Thread] Current Thread [Next in Thread>