tsm:tsm_perf_client
Differences
This shows you the differences between two versions of the page.
| Next revision | Previous revision | ||
|
tsm:tsm_perf_client [2021/01/01 21:25] 127.0.0.1 external edit |
tsm:tsm_perf_client [2021/01/05 17:21] (current) manu |
||
|---|---|---|---|
| Line 13: | Line 13: | ||
| Many of you know that this simply changes the restore from the post TSM 3.1 “No Query Restore” back to the older “Classic” restore. | Many of you know that this simply changes the restore from the post TSM 3.1 “No Query Restore” back to the older “Classic” restore. | ||
| + | |||
| + | ===== TSM client network improvements ===== | ||
| + | |||
| + | Do not use client dedup nor compression if you backup on containers. Data reduction on client side will preserve your bandwith, but ask to TSM admin before. | ||
| + | |||
| + | * **TCPWINDOWSIZE**: Specifies the size, in kilobytes, to use for your client node TCP/IP sliding window. The range of values is 0 through 2048. A value of 0 allows the client to use the operating system default TCP window size. Values from 1 to 2048 indicate that the window size is in the range of 1KB to 2MB. If you specify a value less than 1, the TCP window size defaults to 1. If you specify a value greater than 2048, the TCP window size defaults to 2048. | ||
| + | For backup-archive clients, the default value for this parameter is 63 KB on AIX and Solaris. And 0, the OS default, on the other platforms Linux, Windows and Mac. | ||
| + | For IBM Spectrum Protect for Virtual Environments: Data Protection for VMware, the default value for this parameter is 512 KB. | ||
| + | |||
| + | * **RESOURceutilization**: Specifies the level of resources the IBM Spectrum Protect server and client can use during processing. The range of values that you can specify is 1 - 100. The default value is 2. | ||
| + | |||
| + | * **TCPBuffsize**: The tcpbuffsize option specifies the size of the internal TCP/IP communication buffer used to transfer data between the client node and server. Although it uses more memory, a larger buffer can improve communication performance. | ||
| + | |||
| + | The best way to find the best parameter is using command line like this: | ||
| + | <cli prompt='>'> | ||
| + | C:\Users\admin> dsmc ba c:\tmp\my_big.iso -resourceutilization=10 -tcpwindowsize=32 | ||
| + | </cli> | ||
| + | |||
| + | <code> | ||
| + | Backup-Archive client with limited, high latency network (WAN backups): | ||
| + | =============================== | ||
| + | TCPWINDOWSIZE 512 | ||
| + | RESOURCEUTILIZATION 4 | ||
| + | COMPRESSION Yes | ||
| + | DEDUPLICATION Yes | ||
| + | ENABLEDEDUPCACHE Yes | ||
| + | </code> | ||
| + | |||
| + | Tip: Do not use the client deduplication caching for applications that use the | ||
| + | IBM Spectrum Protect API (TDP). | ||
| + | |||
| + | <code> | ||
| + | Backup/Archive client or Client API with limited network (Gigabit LAN backups): | ||
| + | =============================== | ||
| + | TCPWINDOWSIZE 512 | ||
| + | RESOURCEUTILIZATION 10 | ||
| + | COMPRESSION Yes | ||
| + | DEDUPLICATION Yes | ||
| + | ENABLEDEDUPCACHE No | ||
| + | </code> | ||
| + | |||
| + | <code> | ||
| + | Backup/Archive client or Client API with high speed network (10 Gigabit LAN backups) | ||
| + | =============================== | ||
| + | TCPWINDOWSIZE 512 | ||
| + | RESOURCEUTILIZATION 10 | ||
| + | COMPRESSION No | ||
| + | DEDUPLICATION No | ||
| + | ENABLEDEDUPCACHE No | ||
| + | </code> | ||
| + | |||
| + | * **TCPBUFFSIZE**: The tcpbuffsize option specifies the size of the internal TCP/IP communication buffer used to transfer data between the client node and server. Although it uses more memory, a larger buffer can improve communication performance. Specifies the size, in kilobytes, that you want to use for the internal TCP/IP communication buffer. The range of values is 1 through 512; the default is 32. Depending on the operating system communication settings, your system might not accept all values in the range of 1 through 512. | ||
| ===== Backup with TDP MSSQL ===== | ===== Backup with TDP MSSQL ===== | ||
| Line 42: | Line 94: | ||
| upd node <node_name> maxnummp=10 | upd node <node_name> maxnummp=10 | ||
| </cli> | </cli> | ||
| + | |||
| + | ===== Backup with TDP Exchange ===== | ||
| + | |||
| + | * **/SKIPINTEGRITYCHECK** : Performance can improve with this parameter to bypass integrity checking. There is a risk that is associated with using this parameter. | ||
| + | * For VSS backups, the **RESOURCEUTILIZATION** client option is also important. This option increases or decreases the ability of the client to create multiple sessions. The higher the value, the more sessions the client can start. The range for the option is from 1 to 10. | ||
| + | * **/MINimumbackupinterval=numberOfMinutes** : If you are scheduling the backup of databases in an Exchange Server Database Availability Group, specify the minimum amount of time, in minutes, before a backup of another copy of the same Database Availability Group database can begin. The range is 1 - 9999 | ||
tsm/tsm_perf_client.1609532739.txt.gz · Last modified: 2021/01/01 21:25 by 127.0.0.1
Page Tools
Except where otherwise noted, content on this wiki is licensed under the following license: GNU Free Documentation License 1.3
