Eventually I found something neat in TSM on the third day, it is the TSM for VE (Virtual Environment).
Unit 7: Customizing the Tivoli Storage Manager database and recovery log
Lesson 1: Database and recovery log functions and considerations
Database and recovery log
– Server uses database to manage information about client files
– Recovery log ensure consistency and availability of the database
Information stored in the database
client nodes and administrators/ policies and schedules/ server settings/ location of clients on the server storage/ directory structure/ server operations
Database overview
DB2 database format advantages
Recovery log
– Active log: the transactions have not been committed
– Active log mirror (optional)
– Archive log
– Archive failover log (optional)
Recovery log usage
Keep mirror logs on a separate physical device
Transactions
the unit of work exchanged between server and client
MAX 65,000 objects in one transaction
Monitoring the database and recovery log
query dbspace
query log
dsmserv display log
Lesson 2: TSM database and log space
Managing database space
Database and recovery log sizing
– Database: MIN 2.2 GB, Max 1 TB (5.5), 2 TB (6.2), 4 TB (6.3)
– Active log: MIN 2 GB, MAX 128 GB (recommended to use 120 GB), default 16 GB
– Archive log: 3-4 times of the active log, and only full backups will clear the archive log
Database space usage
determined by the following factors:
– the numbers of the client files to be stored
– how many versions of backed up files are kept
– whether using caching
each version of a file: 400 – 600 bytes
each cached of a file: 100 – 200 bytes
Overhead additional 50%
Estimation: 1 TB of server storage, the DB will be between 10 to 50 GB
Enabling cache
caching is disable by default
Increasing the size of the database
extend dbspace e:\tsm_db\dbs4 (the directory must be empty and accessible to the use ID of the DB manager)
Increasing the size of the active log
Update ACTIVELOGSIZE in dsmserv.opt file:
activelogsize 122880
ACTIVELOGDIR new active log folder
The changes will take effect after restarting the server
Lesson 3: Database options
Server options
– ACTIVELOGDIR
– ACTIVELOGSIZE
– ARCHLOGDIR
– ARCHFAILLOGDIR
– MIRRORLOGDIR
– DBMEMPERCENT (if not defined, the default is 70-80%)
Data transfer options
– MOVEBATCHSIZE
– MOVESIZETHRESH
– TXNGROUPMAX
…
Unit 8: Client configuration
Lesson 1: Client interfaces
3 interfaces
Backup-archive GUI
dsm
Web client interface
Backup-archive command line
C:\program files\Tivoli\TSM\baclient\dsmc
Utilities menu commands
Lesson 2: Administrative control of access
Registration
register node nodename password userid=none
Password management
set passexp days node=nodename (by default 90 days)
set invalidpwlimit number_of_attempts (by default 0)
set minpwlength number_of_characters (by default 0)
Prevent client nodes from accessing the server
lock/ unlock node nodename
Backup operators group
Backup operators
Storage administrators
Lesson 3: Managing client options
Edit dsm.opt file or define client preference in BA GUI
Configuring client options
the option file is read from bottom up, which means the bottom ones have higher priority
Configuring client access to the server
– TCPPORT (default 1500)
– TCPSERVERADDRESS
– COMMMETHOD (tcpip/ tcpip v6/ …)
– NODENAME
The PASSWORDACCESS GENERATE option
to allow the use of the web client
Additional options
some options are not available in the graphical options editor
Precedence of client options
The DOMAIN option
the DOMAIN option specifies what you want to include for an incremental backup
In client option file: DOMAIN C: D: E:
From the command line: dsmc incremental –domain=”G: H:”
dsmc incremental –domain=”ALL-LOCAL –e:” (all local drive except e: drive)
Domain for backup
Lesson 4: Client performance and options
Client options for configuring and improving performance
TXNBYTELIMT option specifies the number of kilobytes that the client program buffers before it sends a transaction to the server
Refer TSM Performance Manual for more details
Setting the TXNGROUPMAX server option
TXNGROUPMAX indicates the maximum number of logical files (client files) that a client can send to the server in a single transaction. The default is 4096 files.
Configuring error logging options
– ERRORLOGNAME
– ERRORLOGRETENTION
– ERRORLOGMAX
unless you specify QUIET, messages will display during the process
Viewing the DSMSCHED.LOG file
dsmsched.log file keeps the schedule logs
Lesson 5: Include-exclude processing
Accessing the include-exclude list
Include-exclude processing order
Read list from bottom up
Exclude directories from backup
TSM BA client builds an internal traverse tree before performing a backup
EXCLUDE.DIR excludes a directory structure from the traverse tree
Client compression, encryption, and adaptive subfile backup processing
include.compression
include.encrypt
include.subfile
Files to be included or excluded from backup
use INCLUDE statement is the client option file to assign a management class for a file or file group
Wild cards and special characters
Lesson 6: Client option sets
Best practice: Use client option sets to set option for groups of client
– define cloptset
– define clientopt
– register node / update node
Defining client option sets
define clientopt prodbackup inclexcl “include d:\plans” seqnumber=20
The FORCE option
Use FORCE to define whether a client node can overwrite an option value (default is NO)
define clientopt prodbackup subfilebackup no force=yes
Copy, query, delete or update a client option set
COPY CLOPTSET prodbackup newcloptset
QUERY CLOPTSET prodbackup
DELETE CLOPTSET prodbackup
UPDATE CLOPTSET prodbackup (change description and sequence option)
Lesson 7: Deleting backup files
Authority to delete a backup file
A client node that has been authorized can also delete backup data
Lesson 8: Encryption and security
Client data encryption
include.encrypt option is the only way to enable encryption on the client
Encryption key
– encryptkey save
– encryptkey prompt
– encryptkey generate
Secure Sockets Layer
SSL provides another level of protection beyond passwords