I do not have accounting turned on, but am thinking about doing so. What
would I need to expect storage-wise if I turn it on? 

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of 
Mark
Stapleton
Sent: Friday, March 23, 2007 10:07 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: [ADSM-L] Shrinking scratch pools - tips?

Filespace data won't tell him anything.
 
If you have TSM accounting turned on, look for the dsmaccnt.log file. That
contains a wealth of historical backup/restore information, broken down by
date and TSM client.
 
--
Mark Stapleton (mark.s AT evolvingsol DOT com)
Senior consultant

________________________________

From: ADSM: Dist Stor Manager on behalf of Stef Coene
Sent: Fri 3/23/2007 9:57 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: [ADSM-L] Shrinking scratch pools - tips?



On Friday 23 March 2007, Bell, Charles (Chip) wrote:
> Since this a GREAT place for info, etc., I though I would ask for
> tips/how-to's on tracking down why my scratch pools are dwindling, for
> LTO/LTO2/VTL. My guess is I have a couple of clients that are sending out a
> vast amount of data to primary/copy. But without a good reporting tool, how
> can I tell? Expiration/reclamation runs fine, and I am going to run a check
> against my Iron Mountain inventory to see if there is anything there that
> should be here. What else would you guys/gals look at?  :-)  Thanks in
> advance!
If you want to sort filespaces by date:

select * from filespaces order by BACKUP_START


Stef
-----------------------------------------
Confidentiality Notice:
The information contained in this email message is privileged and
confidential information and intended only for the use of the
individual or entity named in the address. If you are not the
intended recipient, you are hereby notified that any dissemination,
distribution, or copying of this information is strictly
prohibited. If you received this information in error, please
notify the sender and delete this information from your computer
and retain no copies of any of this information.