ADSM-L

Re: [ADSM-L] Archive Log Overflow never empties

2014-11-25 07:41:29
Subject: Re: [ADSM-L] Archive Log Overflow never empties
From: "Rhodes, Richard L." <rrhodes AT FIRSTENERGYCORP DOT COM>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Tue, 25 Nov 2014 12:39:06 +0000
We are also on 6.2.5 and had this happen once.  
I agree, the archive log overflow area does not seem to work as advertised.
I finally just deleted the archive logs in the overflow area after several 
backup.

Rick

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of 
Roger Deschner
Sent: Monday, November 24, 2014 8:27 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Archive Log Overflow never empties

We have four instances of TSM Server 6.2.5 on AIX, which basically
behave pretty well. But on all of them, we occasionally get a little bit
of data overflowing into the Archive Overflow Log filesystem. I don't
know why, because as far as I can tell the Archive Log filesystem has
never been allowed to fill up. But anyway, it never empties out. Full
database backups reliably free space in the Archive Log filesystem, but
the Archive Overflow Log just gradually fills up. One of them is up to
20%, over a period of a year. I saw somewhere that it takes two full
database backups, but there have been many dozens of full backups.

Any idea how I can get the Archive Overflow Log to empty out?

Roger Deschner      University of Illinois at Chicago     rogerd AT uic DOT edu
========== "You will finish your project ahead of schedule." ===========
================= (Best fortune-cookie fortune ever.) ==================


-----------------------------------------
The information contained in this message is intended only for the personal and 
confidential use of the recipient(s) named above. If the reader of this message 
is not the intended recipient or an agent responsible for delivering it to the 
intended recipient, you are hereby notified that you have received this 
document in error and that any review, dissemination, distribution, or copying 
of this message is strictly prohibited. If you have received this communication 
in error, please notify us immediately, and delete the original message.

<Prev in Thread] Current Thread [Next in Thread>