Re: How much data is being backed up per client?
For all activity on 12/26, try this: q actlog begind=12/26/2002 begint=00:00 endd=12/27/2002 endt=00:00 search ='ANE4961I' Nelson Kane [EMAIL PROTECTED]To: [EMAIL PROTECTED] Sent by: ADSM: cc: Dist StorSubject: How much data is being backed up per client? Manager [EMAIL PROTECTED] .EDU 12/27/2002 08:58 AM Please respond to ADSM: Dist Stor Manager Season's Greetings Tsm'ers, 1) Can someone tell me how to check the amount of data being backed up per client, and how to obtain the same info for previous days. 2) How much data was in my Disk pool before I migrated it all! Thanks -Kane
Re: How much data is being backed up per client?
A q stg somediskpool f=d will show ... Migration in Progress?: Yes Amount Migrated (MB): 276,894.60 Elapsed Migration Time (seconds): 10,881 ... and once the migration process(es) finish, that should show what was migrated between when migrations first kicked off and when the last one finished (or current time if they are still running as in my example above). Best source of info on client traffic is the dsmaccnt.log file in the tsm server install directory. If you, from an admin session, issue the set accounting on it will start writing accounting records for each client session to the dsmaccnt.log file. Make sure you have plenty of space in the filesystem (depending on how many clients you have and how many sessions they initiate). Then just write some little script/pgm that will sum up the info in the records for the different nodes. Since we have 10 TSM servers, there are some things I do only on a monthly basis... I do thing like generate overall traffic numbers like 12/21/2002 tsmsrvz 1218113360 KB 3574432 sec 12/22/2002 tsmsrvz 451869328 KB 3452613 sec 12/23/2002 tsmsrvz 332773700 KB 1675172 sec 12/24/2002 tsmsrvz 1404730729 KB 2841210 sec 12/25/2002 tsmsrvz 285941973 KB 1306029 sec 12/26/2002 tsmsrvz 292468155 KB 1213964 sec Others that show breakdown of types of traffic by tsm client by tsm server (below are ArchCnt, ArchKB, RetrCnt, RetrKB, BkupCnt, BkupKB, RestCnt, RestKB, CommKB, CommSec) 11/27/2002 tsmsrvx a_client 69 233419808 0 0 0 0 0 0 238684872 34567 11/27/2002 tsmsrvx a_client 5110 4275779270 0 0 0 0 0 0 4276434480 720268 11/28/2002 tsmsrvx a_client 331 1095677328 0 0 0 0 0 0 1114648820 145480 11/29/2002 tsmsrvx a_client 5112 4277868551 0 0 0 0 0 0 4278524072 737904 11/30/2002 tsmsrvx a_client 52 195162800 0 0 0 0 0 0 200597228 29377 others that are totals by server of the different types of traffic (below shows arch KB, bkup KB, retr KB, rest KB, Inbound KB, Outbound KB) 11/27/2002 tsmsrvx 4509199078 0 0 0 4509199078 0 11/28/2002 tsmsrvx 1095677328 0 0 0 1095677328 0 11/29/2002 tsmsrvx 4277868551 0 0 0 4277868551 0 11/30/2002 tsmsrvx 195162800 0 0 0 195162800 0 Dwight -Original Message- From: Nelson Kane [mailto:[EMAIL PROTECTED]] Sent: Friday, December 27, 2002 8:59 AM To: [EMAIL PROTECTED] Subject: How much data is being backed up per client? Season's Greetings Tsm'ers, 1) Can someone tell me how to check the amount of data being backed up per client, and how to obtain the same info for previous days. 2) How much data was in my Disk pool before I migrated it all! Thanks -Kane
Re: How much data is being backed up per client?
Give this a try: 1) SELECT ENTITY, SUM(BYTES) FROM SUMMARY WHERE ACTIVITY='BACKUP' AND START_TIME BETWEEN '-MM-DD HH:MM:00.00' AND '-MM-DD HH:MM:00.00' GROUP BY ENTITY 2) SELECT ENTITY, SUM(BYTES) FROM SUMMARY WHERE ACTIVITY='MIGRATION' AND START_TIME BETWEEN '-MM-DD HH:MM:00.00' AND '-MM-DD HH:MM:00.00' GROUP BY ENTITY Replace the '-MM-DD HH:MM:00.00' with your desired time range, and you can go back as far as your SET SUMMARYRETENTION option allows. Colby -Original Message- From: Nelson Kane [mailto:[EMAIL PROTECTED]] Sent: Friday, December 27, 2002 8:59 AM To: [EMAIL PROTECTED] Subject: How much data is being backed up per client? Season's Greetings Tsm'ers, 1) Can someone tell me how to check the amount of data being backed up per client, and how to obtain the same info for previous days. 2) How much data was in my Disk pool before I migrated it all! Thanks -Kane
Re: How much data is being backed up per client?
On Fri, 2002-12-27 at 09:21, Cook, Dwight E wrote: Best source of info on client traffic is the dsmaccnt.log file in the tsm server install directory. This is not actually true. The accounting log counts the number of bytes passed from client to server, including all retries. If you have a 3GB file that retries 4 times for a backup, and then fails, the accounting log will note 12GB of data when 0 bytes actually backed up. Looking through the server activity log for ANE4961I messages give a more accurate picture. -- Mark Stapleton ([EMAIL PROTECTED])
Re: How much data is being backed up per client?
I do believe that the accounting data gives both the Amount of data, in kilobytes, communicated between the client node and the server during the session and the Amount of backup files, in kilobytes, sent by the client to the server. Mr. Lindsay Morris has a free script on his ServerGraph page that will format out the accounting data. The ANE4961I gives the Total number of bytes transferred during the session, and that includes changing retries. For the amount of data migrated, you can query the SUMMARY table for ACTIVITY=MIGRATION and total up the BYTES column. I would not rely on the summary table to the client backup sessions. There have been so many APARS and supposed fixes for this, that trying to figure out which server and client version actually fix the problem is confusing and a moving target. Plus I belive this is again the total bytes transferred, including retries, and not actually how much data was backed up. Bill Boyer DSS, Inc. A life?...COOL!! Where can I download one? -- ?? -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of Mark Stapleton Sent: Friday, December 27, 2002 11:10 AM To: [EMAIL PROTECTED] Subject: Re: How much data is being backed up per client? On Fri, 2002-12-27 at 09:21, Cook, Dwight E wrote: Best source of info on client traffic is the dsmaccnt.log file in the tsm server install directory. This is not actually true. The accounting log counts the number of bytes passed from client to server, including all retries. If you have a 3GB file that retries 4 times for a backup, and then fails, the accounting log will note 12GB of data when 0 bytes actually backed up. Looking through the server activity log for ANE4961I messages give a more accurate picture. -- Mark Stapleton ([EMAIL PROTECTED])
