IBM E16RMLL-I - Tivoli Storage Manager Implementation Manual page 549

So out of the total time of 406 seconds, it takes 308 seconds to process the
35332 directories and realize that only two objects have changed. In addition, the
server is queried for the objects available, resulting in a search and transfer of 82
MB worth of inventory information, as shown with producer session 134 in
Example 15-23. Not only do we have to collect the information from the server,
we need to transfer it through the network to make it available for the client
session to check for changed objects.
Example 15-23 TSM server query session information
q se
tsm: LOCHNESS_SERVER1>
Sess Comm. Sess Wait
Number Method State Time
------ ------ ------ ------ ------- ------- ----- -------- --------------------
121 Tcp/Ip Run 0 S
134 Tcp/Ip IdleW 1 S
Now we run the same operation, but with JBB enabled. The statistics are shown
in Example 15-24.
Example 15-24 Journal-based backup statistics
Session established with server LOCHNESS_SERVER1: Windows
Server Version 5, Release 3, Level 2.2
Server date/time: 02/23/06
Incremental backup of volume '/home'
Querying Journal for '/home'
Processing 1 Journal entries for '/home'
Successful incremental backup of '/home'
Total number of objects inspected:
Total number of objects backed up:
Total number of objects updated:
Total number of objects rebound:
Total number of objects deleted:
Total number of objects expired:
Total number of objects failed:
Total number of bytes transferred:
Data transfer time:
Network data transfer rate:
Aggregate data transfer rate:
Objects compressed by:
Elapsed processing time:
Bytes Bytes Sess Platform Client Name
Sent Recvd Type
8.4 K 456 Admin WinNT
82.0 M 1.8 K Node AIX
17:12:31 Last access: 02/23/06
1
1
0
0
0
0
0
88.03 KB
0.00 sec
17,737.50 KB/sec
43.80 KB/sec
0%
00:00:02
Chapter 15. Performance considerations
ADMIN
BANDA
17:11:38
519