Re: TSM 5.1 on Solaris 8 64-bit - performance tuning question

You'll need to set 2 things....I think I read where you already have
maxnummp set to 4. Now you need to set resourceutilization to10. The ru
formula is described in the performance tuning guide.

Bob McCole
Manager, Computing Services
American Management Systems, Inc.




                    Kent Monthei
                    <Kent.J.Monthe       To:     ADSM-L AT VM.MARIST DOT EDU
                    i AT GSK DOT COM>           cc:
                    Sent by:             Subject:     Re: TSM 5.1 on Solaris 8 
64-bit - performance tuning
                    "ADSM: Dist           question
                    Stor Manager"
                    <ADSM-L AT VM DOT MAR
                    IST.EDU>


                    11/11/2002
                    06:11 PM
                    Please respond
                    to "ADSM: Dist
                    Stor Manager"






Mark, thanks.  However, this is the initial full/cold backup of 20
populated mountpoints.  Also, the CopyGroup CopyMode is set to Absolute,
not Modified.

-thanks

Kent Monthei
GlaxoSmithKline





"Mark Stapleton" <stapleto AT BERBEE DOT COM>

Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
11-Nov-2002 17:39
Please respond to "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>




        To:     ADSM-L

        cc:
        Subject:        Re: TSM 5.1 on Solaris 8 64-bit - performance
tuning question

>>We're trying to take advantage of ResourceUtilization in the newer
>>multi-threaded TSM Client, but I'm having trouble getting the Client to
>>consistently start/maintain 4 data sessions to tape. ResourceUtilization
>>is set to 8.  Throughout most of the backup, 5-6 sessions are active.
>>However we are only seeing 2 mounted tapes most of the time, and the
>>backup duration is nearly twice what it should be.

From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU]On Behalf Of
Ricardo Ribeiro
> Try using this value "Maximum Mount Points Allowed=4" to update
> your client
> node, this should tell the client to use this many drives...

You also have to remember that you're not going to be able to keep four
data
threads continuously open during the entire backup session, unless you're
backing up a large number of large files (>1 GB). Threads normally open
and
close due to demand from the client; setting resourceutilization to 8
merely
guarantees a *maximum* of four data threads.

--
Mark Stapleton (stapleton AT berbee DOT com)
Certified TSM consultant
Certified AIX system engineer
MCSE