It might be possible to determine this information from SQL statements --
for example, look at all backups with BACKUP_DATE in the time frame of the
36 GB backups, then again with BACKUP_DATE in the time frame of the prior
("normal") backup and see what the differences are. But this is probably
more trouble than it is worth. After all, even if you knew which file
names were the cause of the increase, that in and of itself wouldn't
really tell you much more than you already know. Since you are (probably)
trying to dig a little deeper, at some point you'll need to talk to the
user.

If it were me, I'd continue trying to contact the user. If this presents a
real problem for your TSM server and you can't get a response from the
user, then you might consider disabling the node and notifying the user
(and maybe his manager) that it will remain disabled until you are able to
get a hold of him to discuss the situation.

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.




Zoltan Forray/AC/VCU <zforray AT VCU DOT EDU>
Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
01/14/2002 09:19
Please respond to "ADSM: Dist Stor Manager"


        To:     ADSM-L AT VM.MARIST DOT EDU
        cc:
        Subject:        Re: Handling spikes in storage transfer



That is my issue. I know the node and filesystem. I need to know what
files are being backed-up.

The file system isn't increasing, just what files are being
updated/changed and since the increase seems to be fairly consistent, it
is probably just a few files.

----------------------------------------------------------------------------------------------------
Zoltan Forray
Zoltan Forray
Virginia Commonwealth University - University Computing Center
e-mail: zforray AT vcu DOT edu  -  voice: 804-828-4807




Nicholas Cassimatis <nickpc AT US.IBM DOT COM>
Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
01/14/2002 11:05 AM
Please respond to "ADSM: Dist Stor Manager"


        To:     ADSM-L AT VM.MARIST DOT EDU
        cc:
        Subject:        Re: Handling spikes in storage transfer


If you know what node it is (sounds like you do), you can run "q occ"
daily, and see what filesystem is increasing the number of files stored
and
space occupied.  Once you know the filesystem, you can approach the system
owner with a more direct question.  Can't help with the non-response part
(maybe some BOFHing is required).

Nick Cassimatis
nickpc AT us.ibm DOT com

Today is the tomorrow of yesterday.