IBM E16RMLL-I Implementation Guide - Page 536
Client node
![]() |
View all IBM E16RMLL-I manuals
Add to My Manuals
Save this manual to your list of manuals |
Page 536 highlights
You can have the server collocate client data when the data is initially stored in server storage. If you have a storage hierarchy, you can also have the data collocated when the server migrates the data from the initial storage pool to the next storage pool in the storage hierarchy. 15.4 Client node In this section we focus on tuning parameters on the Tivoli Storage Manager client to obtain maximum performance when using Tivoli Storage Manager. These parameters can be changed or added to the client options file. 15.4.1 Transactions This section covers the Tivoli Storage Manager client options that influence the performance and behavior of data movement on and onto the server. TXNBYTELIMIT This specifies the batch size, in kilobytes, for Tivoli Storage Manager server transactions. TXNBYTELIMIT is used together with TXNGROUPMAX. This option reduces the number of server transactions by increasing the amount of data within any one transaction. Therefore, the amount of overhead during backup, restore, archive, and retrieve caused by database commits is reduced. Note: This option can also be defined and adjusted by the server as required during self-tuning operations. A transaction is the unit of work exchanged between the client and the server. Because the client program can transfer more than one file or directory between the client and server before it commits the data to server storage, a transaction can contain more than one object. This is called a transaction group. This option allows you to control the amount of data sent between the client and server before the server commits the data and changes to the server database, thus changing the speed with which the client performs work. The amount of data sent within a single transaction applies when files are batched together during backup or when receiving files from the server during a restore procedure. The administrator can limit the number of files or directories contained within a group transaction using the TXNGROUPMAX option; the actual size of a transaction can be less than your limit. Once this number is reached, the client commits the transaction to the server even if the transaction byte limit is not reached. 506 IBM Tivoli Storage Manager Implementation Guide
![](/manual_guide/products/ibm-e16rmlli-implementation-guide-3588123/536.png)