This would suggest to me that any inactive objects (modified or deleted)
bound to this management class will be expired/removed from TSM-managed
storage 30 days from their inactivation date (subject to expiration
processing).

>From the TSM Server, the only way I can think of checking this would be by
looking at the INACTIVE objects in the BACKUPS table for this node and count
forward the RETEXTRA/RETONLY days (according to the management class to
which they're bound if not the below) from their DEACTIVATE_DATE. This could
be very resource intensive.

You might be able to find some information from the client side, looking in
the BA client restore panel, checking to view inactive objects, and then
check your newly inactive objects and the management class to which they are
bound.

/David Mc
London, UK

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Jones, Eric J
Sent: 23 March 2010 13:22
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: [ADSM-L] Expiration Questions

Good Morning.
The policy on this particular machine is.
==========================================
Policy
Set Name

--------
ACTIVE

Versions Versions   Retain  Retain
    Data     Data    Extra    Only
  Exists  Deleted Versions Version
-------- -------- -------- -------
No Limit No Limit       30      30
===========================================
Is there a way to see how many files will expire in the next day and/or week
for a particular server/workstation?

Thanks
Eric

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT vm.marist DOT edu] On Behalf Of
David McClelland
Sent: Friday, March 19, 2010 10:07 AM
To: ADSM-L AT vm.marist DOT edu
Subject: Re: [ADSM-L] Expiration Questions

Hi Eric,

When you say, "We have a 30 day policy", could you send the output of a `Q
COPYGROUP` for the relevant management class?

Cheers,

David McClelland
London, UK

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Jones, Eric J
Sent: 19 March 2010 13:04
To: ADSM-L AT VM.MARIST DOT EDU
Subject: [ADSM-L] Expiration Questions

We are running TSM 5.4 server on an AIX machine with our clients(Windows
2003/2008) running also running TSM 5.4.
My question is we changed permissions on all our files on 1 of our servers
32 days ago which caused them all to be backed up again.
We have a 30 day policy on the files for retention so I had expected a large
expiration to take place 2 days ago but it hasn't taken place yet.  Is there
a way to tell
1:  When these files will expire?
2: How many versions of the files are currently on the server and how many
days until they expire?

Thanks
Eric