Hello.  I tested this and got the output:

ANR0986I Process 206 for EXPORT NODE running in the BACKGROUND processed 37,158 
items for a total of 10,206,832,635 bytes with a completion state of SUCCESS at 
16:58:30.

So I have 37,158 active items for this particular node, correct?

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of 
TH
Sent: Tuesday, February 03, 2015 12:21 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: [ADSM-L] size of objects in the backups table

Maybe a different way would be suitable for you - try to do EXPORT NODE xxx 
FILEDATA=BACKUPACTIVE PREVIEW=YES

The end of process will give you a total size of active data for a node.

Regards,

Tomasz Hubicki


------ Wiadomość oryginalna ------
Temat: [ADSM-L] size of objects in the backups table
Nadawca: Rhodes, Richard L. <rrhodes AT FIRSTENERGYCORP DOT COM>
Adresat: ADSM-L AT VM.MARIST DOT EDU
Data: Tue Feb 03 2015 15:25:52 GMT+0100

> We are on TSM v6.2.5.
>
> We keep running into the normal question that seems to come up when we start 
> analyzing our backups.  We can tell the number of active/inactive files from 
> the backups table, but not the size, which is in the contents table.  Does 
> anyone have a way to get the active/inactive objects and their size without 
> killing your system with a massive SQL join?  Maybe some kind of SQL join for 
> a specific node.
>
> I just can't believe TSM doesn't provide this info easily from the server!
> (I suppose this belongs under the "Rant" thread!)
>
>
> Rick
>
>
> -----------------------------------------
>
> The information contained in this message is intended only for the personal 
> and confidential use of the recipient(s) named above. If the reader of this 
> message is not the intended recipient or an agent responsible for delivering 
> it to the intended recipient, you are hereby notified that you have received 
> this document in error and that any review, dissemination, distribution, or 
> copying of this message is strictly prohibited. If you have received this 
> communication in error, please notify us immediately, and delete the original 
> message.
>