Table of Contents
Advertisement
Restore function invoked.
Restoring
Restore processing finished.
Total number of objects restored:
Total number of objects failed:
Total number of bytes transferred:
Data transfer time:
Network data transfer rate:
Aggregate data transfer rate:
Elapsed processing time:
This example should provide you with a basic idea of the steps needed to
approach and investigate Tivoli Storage Manager performance-related questions
within your environment.
Often the first clue to a performance problem is unexpected results. These
symptoms should be documented for later analysis and possible correlation with
log data provided by the client and the server. Performance tuning is an iterative
process and usually the first performance trace leads to further tracing on either
the client, the network, or the server. Document your changes to the
configuration and keep track of the results after the changes are applied.
As described in 15.1, "How to measure performance" on page 482, the number
of influencing factors is huge, and each requires detailed consideration to
increase overall performance.
Note: If archive performance is an issue, make sure to consult Appendix A,
"Using TSM's Archive Function," in the Tivoli Storage Manager Performance
Tuning Guide, SG32-9101.
15.2 Architecture-based performance tuning
In this section we describe design considerations for a Tivoli Storage Manager
implementation. We first offer conceptual guidelines to follow, as well as provide
a list of parameters for precise tuning.
524,288,000 /home/root/500MBFile [Done]
12,452.21 KB/sec
11,026.84 KB/sec
00:00:46
Chapter 15. Performance considerations
1
0
500.06 MB
41.12 sec
495
Advertisement
Table of Contents
