I'm not sure that checking the dsmsched.log on the client will help James to
identify how many versions of files have been expired on the TSM server as a
result of the copy group change and subsequent EXPIRE INVENTORY run, but I
agree that checking the output of 'Q OCC' for the client before and after
the expiration is a good plan. You could check the output of some 'Q BACKUP'
commands from the client for some sample files to ensure that there are only
the required number/retention of objects after the change/expiration has
been run. But if you've already made the change and run EXPIRE INVENTORY
without any grabbing any baseline information for this client beforehand
then you're pretty limited in your ability to calculate the delta. If you're
very lucky, the AUDITOCCUPANCY table may not have been updated since the
change and you can run 'Q AUDITOCC <TESTNODE>' to get some information on
volume of data managed from before, then run an 'AUDIT LIC' and then run the
'Q AUDITOCC <TESTNODE>' once again to give you the delta.

HTH,

/David McClelland
London, UK



-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of 
km
Sent: 14 August 2009 00:56
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: [ADSM-L] Change backup copy group settings

On 13/08, James Choate wrote:
> I changed my backup copy group setting for a Policy domain that has one
test node in it from
>
> Versions Data Exists: 35
> Versions Data Deleted: 35
> Retain Extra Versions: 35
> Retain Only Version: 60
>
> To:
> Versions Data Exists: 7
> Versions Data Deleted: 7
> Retain Extra Versions: 7
> Retain Only Version: 14
>
>
> After the backup ran, and expiration ran, is there an easy way to tell how
many files where expired for this client?
>
> Thanks,
> ~james

query occupancy differences before and after the copy group change or check
dsmsched.log on the client, there should be a backup summary with number
of expired files.

-km

No virus found in this incoming message.
Checked by AVG - www.avg.com
Version: 8.5.392 / Virus Database: 270.13.54/2300 - Release Date: 08/13/09
18:16:00