Try increasing the values of this parameter on the server (by using the
command "update node")

txngroupmax= xxxxxx

where xxxxx can range from a value of 4 up to 65000 files  per transaction.
Th default value is 256 so if you have not changed it before, increase it
to an higher value (for ex 2000) and see what happens..

Think about the possibility to use the "virtualmountpoint" option, too.
Here is a brief explanation of this option:


The virtualmountpoint option defines a virtual mount point for a file
system if you want to consider files for backup that begin with a specific
directory within that file system. Using the virtualmountpoint option to
identify a directory within a file system provides a direct path to the
files you want to back up, saving processing time. It is more efficient to
define a virtual mount point within a file system than it is to define that
file system using the domain option, and then to use the exclude option in
your include-exclude options list to exclude the files that you do not want
to back up.

Use the virtualmountpoint option to define virtual mount points for
multiple file systems, for local and remote file systems, and to define
more than one virtual mount point within the same file system. Virtual
mount points cannot be used in a file system handled by automounter.
Note:
If the directory that you want to specify as a virtual mount point is a
symbolic link, set the followsymbolic option to Yes. If that option is set
to no (the default), you are not permitted to use a symbolic link as a
virtual mount point.

After you define a virtual mount point, you can specify the path and
directory name with the domain option in either the default client options
file or on the incremental command to include it for incremental backup
services. When you perform a backup or archive using the virtualmountpoint
option, the query filespace command will list the virtual mount point in
its response along with other file systems. Generally, directories that you
define as virtual mount points are treated as actual file systems and
require that the virtualmountpoint option is specified in the dsm.sys file
to restore or retrieve the data.
Note:
When you specify a virtualmountpoint option, the path that it specifies is
added to the default backup domain (domain ALL-LOCAL). The
virtualmountpoint path is always considered a local "mount point"
regardless of the real file system type it points to.
Supported Clients

This option is valid for all UNIX and Linux clients. The Tivoli Storage
Manager client API does not support this option.
Options File

Place this option in the dsm.sys file.
Syntax

Read syntax diagramSkip visual syntax diagram   .-
---------------------------.
   V                             |
>>---VIRTUALMountpoint directory-+-----------------------------><

Parameters

directory
    Specifies the path and directory name for the directory you want to use
as the virtual mount point for a file system. You cannot use wildcard
characters in either the path or directory names.

    Define only one virtual mount point with each virtualmountpoint option
that you include in your client system options file. Use the
virtualmountpoint option as many times as necessary to define all of the
virtual mount points that you want to use.

Examples

Options file:

virtualmountpoint /afs/xyzcorp.com/home/ellen
virtualmountpoint /afs/xyzcorp.com/home/ellen/test/data

Command line:
    Does not apply.


Hope this help..........


Cordiali saluti / Best regards

Gianluca Perilli

_______________________________________________________

EMEA Support - Storage Global Response Team

e-mail: gianluca_perilli AT it.ibm DOT com

Tivoli Software, IBM Software group

Via Sciangai 53, Rome 00144 - Italy
Office:  +39 06.5966-4581
Mobile: +39 3357840985
Fax:      +39 06.59662077
             +39 06.5966-4581
____________________________________________________



             goc
             <goran.k AT VIP DOT HR>
             Sent by: "ADSM:                                            To
             Dist Stor                 ADSM-L AT VM.MARIST DOT EDU
             Manager"                                                   cc
             <[email protected]
             .EDU>                                                 Subject
                                       how to speed up ...

             28/09/2005 16.51


             Please respond to
             "ADSM: Dist Stor
                 Manager"






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