Re: Amount of Data Backed Up Each Night

If your server is at 3.7 or higher you can run a query against the
summary table.  Cut & paste the following into a file, then in dsmadmc
say

macro <file_name>

The query is --

/*                                              */
/* macro file to make a daily summary           */
/*                                              */
set sqldatetimeformat i
set sqldisplaymode w
set sqlmathmode r
commit
select count(*) as count, sum(bytes) as bytes, activity -
 from adsm.summary -
  where date(start_time) = current date - 1 day -
     or date(end_time) = current date - 1 day -
   group by activity
commit


Sample output:

   COUNT: 32
   BYTES: 282977537
ACTIVITY: ARCHIVE

   COUNT: 738
   BYTES: 54885231102
ACTIVITY: BACKUP

   COUNT: 1
   BYTES: 1393352704
ACTIVITY: INCR_DBBACKUP

   COUNT: 6
   BYTES: 57752170496
ACTIVITY: MIGRATION

   COUNT: 6
   BYTES: 397846233
ACTIVITY: RESTORE

   COUNT: 9
   BYTES: 45623899069
ACTIVITY: STGPOOL BACKUP


--
--------------------------
--------------------------
Bill Colwell
Bill Colwell
C. S. Draper Lab
Cambridge, Ma.
bcolwell AT draper DOT com
--------------------------
In <OF4AA0D31E.601A757C-ON88256A26.005E67EB AT tivoli DOT com>, on 04/06/01
In <OF4AA0D31E.601A757C-ON88256A26.005E67EB AT tivoli DOT com>, on 04/06/01
   at 02:34 PM, Andy Raibeck <Andrew_Raibeck AT TIVOLI DOT COM> said:

>Actually the LASTSESS_SENT field is for data sent for *any* TSM client
>operation, not just for the last backup. So if between the time the backup
>finished and the SELECT statement is run, the user performs some other
>operation... even something like DSMC QUERY SESSION... then the
>LASTSESS_SENT field will reflect data from that operation, not the last
>backup. Thus I would not recommend using this, as it is not entirely
>reliable for this purpose.

>For example:

>DSMC INCREMENTAL
>   LASTSESS_SENT reflects data sent during incremental backup

>DSMC SELECTIVE C:\MYFILE.TXT
>   LASTSESS_SENT reflects data sent during backup of c:\myfile.txt

>DSMC QUERY SESSION
>   LASTSESS_SENT reflects data sent (very small amount) for QUERY SESSION

>SELECT NODE_NAME, LASTSESS_SENT FROM NODES
>   Output reflects value from the above QUERY SESSION command.

>As this sequence shows, you could get misleading information using this
>method.

>Regards,

>Andy

>Andy Raibeck
>IBM Tivoli Systems
>Tivoli Storage Manager Client Development
>e-mail: araibeck AT tivoli DOT com
>"The only dumb question is the one that goes unasked."


>"Anderson, Chris D." <CDAnderson AT WEST DOT COM>@VM.MARIST.EDU> on 04/06/2001
>09:48:38 AM

>Please respond to "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>

>Sent by:  "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>


>To:   ADSM-L AT VM.MARIST DOT EDU
>cc:
>Subject:  Re: Amount of Data Backed Up Each Night



>Run this query command and it will give you the node name and how much data
>that node sent from it's last backup.
>select NODE_NAME,LASTSESS_SENT from nodes

>Chris Anderson
>WIC Systems Administrator
>CDAnderson AT West DOT com


>> -----Original Message-----
>> From: Kelly J. Lipp [SMTP:lipp AT storsol DOT com]
>> Sent: Friday, April 06, 2001 11:09 AM
>> To:   ADSM-L AT VM.MARIST DOT EDU
>> Subject:      Re: Amount of Data Backed Up Each Night
>>
>> The schedule log file has this in it so you can do an incremental from
>the
>> schedule rather than running a script to get the same information.  This
>> info is also kept in the server activity log and is available via select
>> statements (I believe) from the node table.  One of our SQL gurus should
>> leap in at this point and show us how.
>>
>> Kelly J. Lipp
>> Storage Solutions Specialists, Inc.
>> PO Box 51313
>> Colorado Springs CO 80949-1313
>> (719) 531-5926
>> Fax: (240) 539-7175
>> Email: lipp AT storsol DOT com or lipp AT storserver DOT com
>> www.storsol.com
>> www.storserver.com
>>
>>
>> -----Original Message-----
>> From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU]On Behalf 
>> Of
>> Poehlman, James
>> Sent: Friday, April 06, 2001 9:51 AM
>> To: ADSM-L AT VM.MARIST DOT EDU
>> Subject: Re: Amount of Data Backed Up Each Night
>>
>>
>> My backups run a script on the client that executes the ''dsmc inc''
>> command
>> for each file system to be backed up.  The output is redirected into a
>log
>> file for each filesystem. Add up all the ''bytes transferred'' in the
>> log files.
>>
>>
>> -----Original Message-----
>> From: Dearman, Richard [mailto:rdearm1 AT UIC DOT EDU]
>> Sent: Friday, April 06, 2001 11:09 AM
>> To: ADSM-L AT VM.MARIST DOT EDU
>> Subject: Re: Amount of Data Backed Up Each Night
>>
>>
>> I am new to the ADSM or TSM world.  How do you guys find out how mcuh
>data
>> you are backing up per night.  Is there a command line in ADSM to show
>you
>> this.
>>
>> -----Original Message-----
>> From: Sean McNamara [mailto:mcnams AT PJM DOT COM]
>> Sent: Thursday, April 05, 2001 1:14 PM
>> To: ADSM-L AT VM.MARIST DOT EDU
>> Subject: Re: Amount of Data Backed Up Each Night
>>
>>
>> Dwight,
>>
>>         Just curious - how big are your disk storage pools and what tape
>> robot
>> are you using ?
>>
>> Sean McNamara
>> Senior Analyst
>> PJM Interconnection, L.L.C.
>> 955 Jefferson Ave
>> Norristown, PA  19403
>> (610)666-4206
>> (610)666-4285 (fax)
>>
>>
>> -----Original Message-----
>> From: Cook, Dwight E [mailto:cookde AT BP DOT COM]
>> Sent: Thursday, April 05, 2001 1:59 PM
>> To: ADSM-L AT VM.MARIST DOT EDU
>> Subject: Re: Amount of Data Backed Up Each Night
>>
>>
>> biggest single box is a 2.4 TB db that compresses down to 600 GB backes
>up
>> every other day/night
>> have tons of others that are 500-ish GB's that compress down to 100-200
>GB
>> and back up nightly
>> across all the tsm servers we do 1.5 TB nightly
>>
>> DWight
>>
>> cookde AT bp DOT com
>>
>>
>> -----Original Message-----
>> From: Diana J.Cline [mailto:Diana.Cline AT rossnutrition DOT com]
>> Sent: Thursday, April 05, 2001 12:40 PM
>> To: ADSM-L AT VM.MARIST DOT EDU
>> Subject: Amount of Data Backed Up Each Night
>>
>>
>> Is there anyone else out there who is backing up 300gb per night or more?
>> If so, i'd love to converse with you.
>> ***************************EMAIL  DISCLAIMER**************************
>> This e-mail and any files transmitted with it may be confidential and are
>> intended solely for the use of the individual or entity to whom they are
>> addressed.   If you are not the intended recipient or the individual
>> responsible for delivering the e-mail to the intended recipient, any
>> disclosure, copying, distribution or any action taken or omitted to be
>> taken
>> in reliance on it, is strictly prohibited.  If you have received this
>> e-mail
>> in error, please delete it and notify the sender or contact Health
>> Information  Management (312) 996-3941.