Mmmm.... not necessarily.
Backups are done with two basic kinds of threads:
* Producer thread that scans the file system looking for changed files,
and queuing up transactions of changed files to be backed up.
* Consumer thread that picks the transactions off the queue from the
producer thread, then backs up the txn.
There is also a performance monitor thread that keeps an eye out for how
well the consumer thread is keeping up with work provided by the producer.
If the consumer needs some help (producer is creating more work than the
consumer can keep up with), then a new consumer thread (backup session)
could be started.
The performance monitor also keeps an eye on how the producer thread is
doing with processing file specifications, e.g., C:, E:, F:. If the
producer is too busy processing one file spec (scanning the file system),
then another producer could be started to work on another file spec.
Likewise the performance monitor will shut down producer or consumer
threads if they are too idle, i.e., not enough work for them to do.
So even with a lower RESOURCEUTILIZATION setting, it is possible for more
than one backup session to kick off... if there is sufficient work to do.
If the client is processing a file system with very few changes (for
example), there might not be enough work to kick off another backup
session.
Higher RESOURCEUTILIZATION settings tell the client that it can initiate
another producer, in which case you'll also get another backup sessin.
But in general, RESOURCEUTILIZATION is more of a "suggestion" to the
client, than a mandate. So even with a higher setting, it is not
guaranteed that you'll get a bunch of backup sessions if there is not
enough work to warrant it.
Regards,
Andy
Andy Raibeck
IBM Software Group
Tivoli Storage Manager Client Product Development
Level 3 Team Lead
Internal Notes e-mail: Andrew Raibeck/Tucson/IBM@IBMUS
Internet e-mail: storman AT us.ibm DOT com
IBM Tivoli Storage Manager support web page:
http://www.ibm.com/software/sysmgmt/products/support/IBMTivoliStorageManager.html
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" <ADSM-L AT VM.MARIST DOT EDU> wrote on 09/20/2007
10:47:22 AM:
> I believe the performance tuning guide explains the resourceutilization
> parameter better. In short, you have to set it to at least 5 to get 2
> backup sessions.
>
>
>
> ______________________________
>
> John Monahan
> Consultant
> Logicalis, Inc.
> 5500 Wayzata Blvd Suite 315
> Golden Valley, MN 55416
> Office: 763-417-0552 x109
> Mobile: 952-221-6938
> Fax: 763-417-0554
> John.Monahan AT us.logicalis DOT com
> http://www.us.logicalis.com
>
>
>
>
> David Longo <David.Longo AT HEALTH-FIRST DOT ORG>
> Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
> 09/19/2007 05:42 PM
> Please respond to
> "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
>
>
> To
> ADSM-L AT VM.MARIST DOT EDU
> cc
>
> Subject
> Windows clients Resourceutilization
>
>
>
>
>
>
> I have used RESOURCEutilization on AIX clients for a long
> time and works fine. I have a Windows client I would like to use it on.
>
> TSM Server is 5.3.4.0 and Windows client is 5.2.2.5, W2K SP4.
> It is an IBM x345 (8670-61X), with 2x 2.8 Ghz Xeon CPU and
> 1 GB RAM.
>
> I set to Resourceutil 4 and it still just uses one backup session.
> There are multiple drives on this system and would like to use
> multiple sessions. I even looked at the manual for 5.4 clients and
> has no more info about this parameter.
>
> What is needed or what is the determining factor in actually
> using multiple backup sessions on Windows clients? (I use
> the basic Client scheduler - not Acceptor Daemon.)
>
> Thanks,
> David Longo
>
>
> #####################################
> This message is for the named person's use only. It may
> contain confidential, proprietary, or legally privileged
> information. No confidentiality or privilege is waived or
> lost by any mistransmission. If you receive this message
> in error, please immediately delete it and all copies of it
> from your system, destroy any hard copies of it, and notify
> the sender. You must not, directly or indirectly, use,
> disclose, distribute, print, or copy any part of this message
> if you are not the intended recipient. Health First reserves
> the right to monitor all e-mail communications through its
> networks. Any views or opinions expressed in this message
> are solely those of the individual sender, except (1) where
> the message states such views or opinions are on behalf of
> a particular entity; and (2) the sender is authorized by
> the entity to give such views or opinions.
> #####################################
|
