Joseph,
I am not aware of any "IBM position" per se. RESOURCEUTILIZATION is simply
another "tuning knob" that was added to the product. Like any other
setting, the decision of when and how to use it is up to you.
Should you add it to your dsm.opt file? It depends. If your backups are
running fine the way they are, then I see no reason to add it ("if it
ain't broke, don't fix it" is a good rule of thumb). On the other hand, if
your backups are taking longer than necessary, then it is an option to
help improve throughput. The advantages are that it offers a "divide and
conquer" approach to processing your file systems since it will start
multiple, concurrent backup sessions to process different parts of your
file systems. But there is no "free lunch". Some of the costs associated
with multiple backup sessions include: more CPU and disk I/O on the client
machine, heavier use of network bandwidth, heavier TSM server utilization,
and so on.
I'm sure that others will have more to add on this subject.
Regards,
Andy
Andy Raibeck
IBM Software Group
Tivoli Storage Manager Client Development
Internal Notes e-mail: Andrew Raibeck/Tucson/IBM@IBMUS
Internet e-mail: [EMAIL PROTECTED] (change eye to i to reply)
The only dumb question is the one that goes unasked.
The command line is your friend.
"Good enough" is the enemy of excellence.
"Wholey, Joseph (TGA\\MLOL)" <[EMAIL PROTECTED]>
Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
10/31/2002 06:45
Please respond to "ADSM: Dist Stor Manager"
To: [EMAIL PROTECTED]
cc:
Subject: resource utilization
Is it recommended to add this value to the dsm.opt file? Initially, IBM's
recommendation was to use the default value of 2 unless you have a special
circumstances. What is Tivoli's positon at this
time? What are most people doing? What are the drawbacks, if any?
