Tivoli Storage Manager Sample Architecture - IBM

More documents

Recommendations

Info

• Active log: Tivoli Storage Manager Deduplication Sample Architecture mklv -y tsmlog -t jfs2 -u 1 -x 100 tsmlog 100 hdisk38 crfs -v jfs2 -d tsmlog -p rw -a agblksize=4096 -m /tsmactlog -A yes • Archive log: mklv -y tsmarchlog -t jfs2 -u 1 -x 455 tsmarchlog 455 hdisk36 crfs -v jfs2 -d tsmarchlog -p rw -a options=rbrw -a agblksize=4096 -m /tsmarchlog -A yes • Random disk storage pool: mklv -y tsmdisk -t jfs2 -u 1 -x 3700 tsmdisk 3700 crfs -v jfs2 -d tsmdisk -p rw -a options=rbrw -a agblksize=4096 -m /tsmdisk -A yes • Sequential file storage pool (note: several of these may be needed depending on capacity) mklv -y tsmfile1 -t jfs2 -x 32768 tsmfile1 32768 crfs -v jfs2 -d tsmfile1 -p rw -a options=rbrw -a agblksize=4096 -m /tsmfile1 -A yes 4.4 TSM server configuration 4.4.1 TSM processing options The following table summarizes TSM server options which are set in dsmserv.opt, as well as, server-wide options which have been set using various set commands on the TSM server. Options (dsmserv.opt) Setting Explanation activelogsize 122880 Slightly below the maximum allowed active log size. allowreorgtable default: yes Allows on-line DB2 table reorg to run allowreorgindex yes Allows on-line DB2 index reorg to run. clientdeduptxnlimit commtimeout 10000 Default: 300 Limit objects using client-side deduplication to 300GB Certain TDP’s benefit from an increased setting for this timeout. Document: Tivoli Storage Manager Deduplication Sample Architecture Date: 09/28/2012 Version: 1.0 Page 16 of 21
dedupdeletionthreads 8 Tivoli Storage Manager Deduplication Sample Architecture deduprequiresbackup Default: Yes deduptier2filesize Default: 100 deduptier3filesize Default: 400 devconf /tsminst1/DEVCONF.txt enableautodbbackup no expinterval 0 idletimeout 240 maxsessions 700 numopenvolsallowed 20 serverdeduptxnlimit 500 Increases the number of threads performing deletion of deduplicated chunks which are no longer referenced. No effect for nodes which use client-side deduplication. For those which use serverside deduplication, storage pool backup completes before deduplication is applied. Only files smaller than 100GB are processed in tier1. Files in the range 100 - 400GB will be processed in tier2. Files 400GB and larger will be processed in tier3. Controls which file the server device configuration information is copied to. A full database backup is only taken once a day and they are scheduled. This disables automatic inventory expiration. Instead, this task is scheduled to run at a specific time every day. Allows idle client sessions to remain through the expected backup window duration. Clients which use client-side deduplication use one additional session. This option controls the number of volumes that a process such as a reclamation process or client restore sessions can hold open at the same time. A small increase to this option is recommended, and some trial and error may be needed. The device class mount limit parameter was also increased because of this change. Limit objects using server-side deduplication to 500GB txngroupmax Default: 4096 Allows more client objects per transaction. volhist /tsminst1/VOLHIST.txt Set options Command Notes Activity log retention set actlogreten 60 Summary record retention set summaryreten 45 Controls which file the server volume history is written to. Max schedule session set maxschedsess 90 Increases the percentage of allowed sessions which can be used for scheduled Document: Tivoli Storage Manager Deduplication Sample Architecture Date: 09/28/2012 Version: 1.0 Page 17 of 21
Page 1 and 2: Tivoli Storage Manager Deduplicatio
Page 3 and 4: Contents Tivoli Storage Manager Ded
Page 9 and 10: 2.2 Protected data Tivoli Storage M
Page 15: Tivoli Storage Manager Deduplicatio
Page 21: Tivoli Storage Manager Deduplicatio

Tivoli Storage Manager Sample Architecture - IBM

Create successful ePaper yourself

Delete template?

Save as template?