Of course, before we can (try to) speed up the client, we need to know where the bottleneck lies. The problem could very well be something other than the amount of data you are backing up.
When the backup starts, periodically (every 5 minutes, for example) run QUERY SESSION on the server side so you can get an idea of how much data is being sent to the client during the initial backup query; after that, use the QUERY SESSION to get an idea of how quickly data is moving between client and server Traversal of the file system can also have a profound impact. Even if you are not actually backing up a lot of the data, it can take a long time to traverse 8+ million files. RESOURCEUTILIZATION of 5 might help... see reference info for this option in the client manual. Regards, Andy Andy Raibeck IBM Software Group Tivoli Storage Manager Client Development Internal Notes e-mail: Andrew Raibeck/Tucson/[EMAIL PROTECTED] Internet e-mail: [EMAIL PROTECTED] The only dumb question is the one that goes unasked. The command line is your friend. "Good enough" is the enemy of excellence. "ADSM: Dist Stor Manager" <[email protected]> wrote on 2005-09-28 15:51:44: > hi, i have a question : > > any ideas how to speed up AIX client backup of 8,259,711 files ? > it's not about size , these 8 mil files have cca. 3GB even less ... > > client aix 5.2 via TCP network LAN to aix 5.2 with TSM 5.3.1.4 > with SATA cache pools ... data compression forced by server > > Elapsed processing time: 12:40:47 > objects compressed by LOUSY 17% > > it can be it, right ? anyone has something similar ? i hope yes :-) > > thanks > goran > > PS: i'll try to "off" data compression when the node will not be accessing > server, which is rarely ... LOOL
