ADSM-L

Re: Expiration

2005-02-01 11:53:18
Subject: Re: Expiration
From: Andrew Raibeck <storman AT US.IBM DOT COM>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Tue, 1 Feb 2005 09:53:00 -0700
Two possible APARs: IC36396, IC34933.

Regards,

Andy

Andy Raibeck
IBM Software Group
Tivoli Storage Manager Client Development
Internal Notes e-mail: Andrew Raibeck/Tucson/IBM@IBMUS
Internet e-mail: storman AT us.ibm DOT com

The only dumb question is the one that goes unasked.
The command line is your friend.
"Good enough" is the enemy of excellence.

"ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU> wrote on 02/01/2005
05:04:01:

> Good Morning.
> I have a question about expiration.
> I have a 90 day policy for data on the servers(Versions Data Exists
> - Nolimit, Version Data Deleted - Nolimit, retain Extra Versions 90
> and Retain Only Version 90).  My question is how can I tell if data
> is being expired and how many files on a particular machine?  What I
> checked is a machine that is backing up everynight with about 2000
> files(SYSETM OBJECT) but the file count keeps growing.  It's been 95
> days since the 1st backup so I would have thought the file count
> would be leveling off.  I see when expiration runs that the server
> is listed for each of it's filespaces but I have no idea how many
> files if any it expired.
> The TSM servers is AIX 5.2 with TSM 5.2.2 and the client is Win2K
> with TSM 5.2.2
> I want to make sure that the old files are expiring so we do not
> keep growing in size.  It's one of many machines so the final count
> for how many files expired in expiration does not tell me which
> machine it came from.
>
> Have a Great Day,
> Eric

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