Author: "John D. Schneider" <john.schneider AT COMPUTERCOACHINGCOMMUNITY DOT COM>
Date: Tue, 13 Apr 2010 08:37:01 -0700
Because of TSM's incremental backup scheme, there is no way to know what files will expire, because their is no way to know what new versions of files will be taking their place in the future. For ex
Author: Michael Green <mishagreen AT GMAIL DOT COM>
Date: Tue, 13 Apr 2010 19:19:46 +0300
John, Please correct me if I'm wrong. select * from syscat.columns where tabname='BACKUPS' shows that there is a column called DEACTIVATE_DATE. I guess if you write a select statement crafted in such
Author: "John D. Schneider" <john.schneider AT COMPUTERCOACHINGCOMMUNITY DOT COM>
Date: Tue, 13 Apr 2010 09:45:57 -0700
Well, I am no expert on this, so I am willing to be corrected by somebody if I don't have this right, but here is my understanding. Yes the deactivate_date will tell you when a given backup object be
Author: Lindsay Morris <lindsay AT TSMWORKS DOT COM>
Date: Tue, 13 Apr 2010 14:02:46 -0400
And like Michael implied, running a select from the BACKUPS table on a production server is liable to kill its performance for a good while. -- Lindsay Morris CEO, TSMworks Tel. 1-859-539-9900 lindsa