Hi Dave! My largest production server has a rather low fragmentation level (about 2 %). Another one, which is slowly being phased out, has a percentage of 60%!!!! Both machines have a lot of nodes removed in the past, but only the big one has nodes added. So my guess is that TSM reuses the fragmented space for new nodes, but of course I cannot prove this. Kindest regards, Eric van Loon KLM Royal Dutch Airlines
-----Original Message----- From: David Nicholson [mailto:[EMAIL PROTECTED] Sent: Friday, October 08, 2004 16:22 To: [EMAIL PROTECTED] Subject: Re: AW: DSMSERV UNLOADDB Hi Eric, Thanks for the info! The older of the 2 servers returned a percent_frag of "-0.01" the newer returned a percent_frag of "27.44". The older server is 4 years old...the newer is 3 years old. Seems strange the newer server would have such a significantly higher frag %. Any idea what kinds of activity result in fragmentation? Is unload/reload the answer here or will the server make efficient use of these fragments over time? Is unload/reload a performance solution or utilization solution or both? or neither? Thanks in advance, Dave "Loon, E.J. van - SPLXM" <[EMAIL PROTECTED]> Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> 10/08/2004 10:10 AM Please respond to "ADSM: Dist Stor Manager" To: [EMAIL PROTECTED] cc: Subject: Re: AW: DSMSERV UNLOADDB Hi David! Try the following SQL statement: SELECT CAST((100 - (CAST(MAX_REDUCTION_MB AS FLOAT) * 256 ) / (CAST(USABLE_PAGES AS FLOAT) - CAST(USED_PAGES AS FLOAT) ) * 100) AS DECIMAL(4,2)) AS PERCENT_FRAG FROM DB It will give you the fragmentation level. Kindest regards, Eric van Loon KLM Royal Dutch Airlines -----Original Message----- From: David Nicholson [mailto:[EMAIL PROTECTED] Sent: Friday, October 08, 2004 15:47 To: [EMAIL PROTECTED] Subject: Re: AW: DSMSERV UNLOADDB Hi All, I am surprised by the significant reduction is Pct Utilized. I thought in previous discussions that Unload/Reload had minimal impact on utilization. I have (2) TSM 5.2.2 servers on AIX with 40GB db's that are 90% used. I haven't done a unload/reload since there creation 3 years ago...do I have an opportunity here? Thanks in advance, Dave "Yuhico, Alexandra" <[EMAIL PROTECTED]> Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> 10/07/2004 02:39 PM Please respond to "ADSM: Dist Stor Manager" To: [EMAIL PROTECTED] cc: Subject: Re: AW: DSMSERV UNLOADDB guys.... I've finished the DSMSERV LOADDB!!! previous q db gave a Maximum reduction of zero and a PCT Util of 68% but my current q db shows the following : Available Assigned Maximum Maximum Page Total Used Pct Max. Space Capacity Extension Reduction Size Usable Pages Util Pct (MB) (MB) (MB) (MB) (bytes) Pages Util --------- -------- --------- --------- ------- --------- --------- ----- ----- 32,768 32,768 0 17,436 4,096 8,388,608 3,928,814 46.8 46.8 Now... silly question... how do you edit the crontab? I thought it was crontab -C but that doesn't seem to work Alexandra -----Original Message----- From: Sternecker, Peter [mailto:[EMAIL PROTECTED] Sent: Friday, 8 October 2004 2:16 AM To: [EMAIL PROTECTED] Subject: AW: AW: DSMSERV UNLOADDB well, well he is right as always. OH NO , no best shell discussion 8-). Peter Sternecker R+V Allgemeine Versicherung AG * mailto:[EMAIL PROTECTED] > -----Ursprüngliche Nachricht----- > Von: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Im > Auftrag von Richard Sims > Gesendet: Donnerstag, 7. Oktober 2004 17:56 > An: [EMAIL PROTECTED] > Betreff: Re: AW: DSMSERV UNLOADDB > > > On Oct 7, 2004, at 11:34 AM, Sternecker, Peter wrote: > > > if your TSM-Server runs on Unix > > > > shell command | tee path_to_logfile > > > > this sends output to the terminal and the logfile. > > That will pipe Stdout, but not Stderr, where scary stuff > goes. You may instead want to do > > shell command 2>&1 | tee path_to_logfile > > or more conveniently use Cshell: > > command |& tee path_to_logfile > > This keeps important msgs from being lost. > > Richard Sims > This e-mail is privileged and may contain confidential information intended only for the person(s) named above. If you receive this e-mail in error, please notify the addressee immediately by telephone or return e-mail. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted. ********************************************************************** For information, services and offers, please visit our web site: http://www.klm.com. This e-mail and any attachment may contain confidential and privileged material intended for the addressee only. If you are not the addressee, you are notified that no part of the e-mail or any attachment may be disclosed, copied or distributed, and that any other action related to this e-mail or attachment is strictly prohibited, and may be unlawful. If you have received this e-mail by error, please notify the sender immediately by return e-mail, and delete this message. Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries and/or its employees shall not be liable for the incorrect or incomplete transmission of this e-mail or any attachments, nor responsible for any delay in receipt. ********************************************************************** ********************************************************************** For information, services and offers, please visit our web site: http://www.klm.com. This e-mail and any attachment may contain confidential and privileged material intended for the addressee only. If you are not the addressee, you are notified that no part of the e-mail or any attachment may be disclosed, copied or distributed, and that any other action related to this e-mail or attachment is strictly prohibited, and may be unlawful. If you have received this e-mail by error, please notify the sender immediately by return e-mail, and delete this message. Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries and/or its employees shall not be liable for the incorrect or incomplete transmission of this e-mail or any attachments, nor responsible for any delay in receipt. **********************************************************************
