THE MAIN FEATURES IN TSM 6:
2) SERVER LEVEL DEDUPLICATION
====================================
4) IN TSM 6 WE NEED TO MENTION THE DEVICE CLASS IN TSM DATABASE DEFINTION FOR AUTOMATIC BACKUP OF TSM DB
SET DBRECOVERY deviceclassname (Set the device class for automatic backup of the tsm server database)"
set dbrecovery TSMDB
IN TSM6 WE HAVE DATA DEDUPLICATION AVAILABLE AND DATA DUPLICATION CAN BE USED IN BOTHE THE WAYS
Deduplcation is process of deleting the duplicate data.
1: CLIENT LEVEL DEDUPLICATION 2) SERVER LEVEL DEDUPLICATION 1: CLIENT LEVEL DEDUPLICATION
FOR CLIENT LEVEL DEDUPLICATION WE NEED TO ENABLE THE FOLLOWING PARAMETERS IN DSM.OPT WE NEED TO ADD THE FLOOWING PARAMETERE
DATADEDUPLICATION YES
AND WHILE REGISTERING THE NODE IN TSM SERVER, WE NEED TO ADD THE FOLLOWING PARAMETER DEDUPLICATION=CLIENTOrserver
2) SERVER LEVEL DEDUPLICATION
TO ENABLE SERVER SIDE DEDUPLICATION, WE NEED ENABLE DEDUPLICATION=YES IN TAPE STORAGE POOL DEFINTION.
in tsm 6.3 we have node replication option available, by using node replication, we can replicate node data from one tsm server to another tsm server
to enable node replication, first we need to have server to server communication and we need to set the replication server in both source and target tsm server
set replicationserver tsmservername
once we set the replication servers then in source server we need to replicate(copy) the node data from source tsm server to target tsm server by using the following command
Replicate node nodename
then data replicates to target server, the advantage of replication is, if source tsm server is not available, we can access the node data from target server
=====================================================================================
=====================================================================================
IN TSM 6 IF WE WANT TO THE DATABASE VOLUMES USE THE FOLLWOING COMMAND Q DBSPACE
tsm: ADSM_CLPTSM001>Q DBSPACE
Location Total Space(MB) Used Space(MB) Free Space(MB) --- --- --- ---
/home/tsminst1/tsmdb01 262,016.00 23,504.24 238,511.76 /home/tsminst1/tsmdb02 262,016.00 23,504.24 238,511.76 /home/tsminst1/tsmdb03 262,016.00 23,504.24 238,511.76 /home/tsminst1/tsmdb04 262,016.00 23,504.24 238,511.76 tsm: ADSM_CLPTSM001>
To increase the TSM database size in TSM 6, we don’t need to create TSM Database volumes and extend the DB
We can directly create the database directory by using the following command
Def dbspace directoryname
Automatically space is allocated the TSM database by TSM Database Manager (depends on the directory size)
=====================================================================================
=================================
IN TSM 6 IF WE WNAT TO CHECK ACTIVE LOG AND ARCHIVE LOG USE THE FOLLWOING COMMAND tsm: ADSM_CLPTSM001>Q LOG F=D
Active Log Directory: /home/tsminst1/tsmlog Total Space(MB): 131,072
Used Space(MB): 30,300 Free Space(MB): 100,772
Archive Log Directory: /home/tsminst1/tsmarchlog Total Size of File System (MB): 133,051.00
Space Used on File System (MB): 2,201.38 Free Space(MB): 130,849.62
Mirror Log Directory: /home/tsminst1/tsmlogmirror Total Size of File System (MB): 133,051.00
Space Used on File System (MB): 102,433.81 Free Space(MB): 30,617.19
Archive Failover Log Directory: /home/tsminst1/tsmarchlogfailover Total Size of File System (MB): 131,004.00
Space Used on File System (MB): 32.21 Free Space(MB): 130,971.80
=====================================================================================
=============================================================================
Infrastructure set up or environment setup:
If interviewer asks about the environment setup, we need to answer like this 1) no of tsm servers we are supporting 10
2) We are taking backup of 2000 clients and each tsm server is taking backup 200 clients 3) We are taking file system backup, oracle backups and sql backup and exchange backup 4) We are using IBM 3583 and ibm3584 tape libraries
5) We are using LTO4 tape drives and LTO4 tapes
5) Daily backup data size of each tsm server is approx. 1 TB (as it is incremental backup) and weekend backup data size is approx. 6 TB for each tsm server
6) We are using service center ticketing tool
=====================================================================================
=============================================================
Manager round:
1) Which ticketing tool u r using and version?
A: Service now ticketing tool
2) Priorities in ticketing tool and explain which what all requests will come for priorities?
P1: need to respond within 15 minutes and need to resolve with in 1 Hour P2: need to respond with in 1 Hour and need to resolve within 4 Hours P3: need to respond within 4 Hours and need to resolve within 8 Hours P4: need to respond within 8 hours and need to resolve within 2 days.
3) Tickets dispatch process and status in ticketing tool?
Tickets Directly come to Ticketing Tool and we need to accept the Tickets from the Queue I.e any restore request, any new backup configuration requests, directly comes to Ticketing tool In ticketing tool we have Distribution list and tickets will be assigned to our DL
Then we need to accept the Tickets from the queue and work on it
If any backup failure, L1 team(monitoring team) will create ticket and assign it to backup team queue
4) Clearly explain incident management, problem management and change management and what all issues u faced?
Incident means: any backup failure or any restore request will be raised as incident these incidents Have priorities Like p1, p2, p3,p4
Problem management means, if the backup is continuously failing (3 consecutive failures) For this we need to raise a problem ticket and work on it
Change management: if any change need to be performed Like Hard ware replacement in Tape Library Or any new backup configuration for this we need to go through the change process, we need to get the Approval from customer, then only we need to implement the change as per the schedule
5) what all major issues u faced and solved
Major issues means, Gripper failure issues in the tape library, then I had logged a call with IBM to replace the failed gripper not to impact the production servers backups
=====================================================================================
====
Backup set:
Backup set is group of active files, that can be stored in particular media, (backup sets maintains active files only)
the advantage of backup set is we can recover the data from the tapes without tsm server interventions Syntax to generate backup is
Generate backupset backupsetname nodename devciceclass=deviceclassname retention=days ex; Generate backupset TESTBACKUPSET VEDA devciceclass=fileclass retention=360
to check whether the backup set is running or not use the following command q pr in TSM servers to check whether the backup set is completed or not, use the following command
q Volhist t=backupset
Command to restore the tsm server database if tsm db is corrupted:
Dsmserv restore db devciceclass=deviceclassname volume=volumename
To check whether the db backup is completed or not, use the foolwing command q db f=d or q volhist t=dbb
There are two options to check in which tape db backup is happened
1) check the plan file which is generated by running prepare command in TSM server 2)q volhist t=dbb (if we can loginto the tsm server)
=====================================================================================
===============================
DB mirror copy and log mirror copy:
def dbcopy sourcedbvolumename targetdbvolumename f=size Def logcopy sourcelogvolumename targetlogvolumename f=size (MB)
the advantage of db and log mirror copies are if any db or log volume is corrupted, in that case we can recover the data from mirror volumes
=====================================================================================
=========================================================================
Procedure to start the TSM server in TSM 6 log into to the tsm server as root
Sudo su - root
Then go to the /home directory cd /home
log into the DB2 instance Sudo su - tsminst1
then run the following command
./start_tsmserver or dsmserv quiet &
TSM Performance tuning:
EXPInterval:
Specifies the interval, in hours, between an automatic inventory expiration run by the TSM server.
Inventory expiration removes client backup and archive file copies from the server.
Expiration processing is very CPU and I/O intensive. If possible, it should be run when other TSM processes are not occurring. To enable this, either schedule expiration once per day, or set EXPInterval to 0 and manually start the process with the EXPIRE INVENTORY command at the server. The default is 24.
Expiration processing can also be scheduled in an administrative schedule.
MAXNUMMP:
The MAXNUMMP setting for the node, in the server, specifies the maximum number of mount points a node is allowed to use on the server and can be set to an integer from 0-999.
MAXSessions:
Specifies the maximum number of simultaneous client sessions that can connect with the TSM server.
MAXSessions 25 (default) MAX SCHEDULE SESSIONS:
Specifies the maximum number of SCHEDULE sessions that can RUN IN the TSM server.
Move Batch Size and MOVESIZETHRESH:
This option specifies the number of files that are to be moved and grouped together in a batch, within the same server transaction.
The default value for MOVEBatchsize is 40 and the maximum value is 1000. The default value for MOVESizethresh is 500 and the maximum value is 2048.
MOVEBatchsize and MOVESizethresh options help tune the performance of server processes that involve the movement of data between storage media.
RESTOREINTERVAL:
Restartable restores allow restores to continue after an interruption without starting at the beginning.
This reduces duplicate effort or manual determination of where a restore process was terminated.
A new server option, RESTOREINTERVAL, defines the amount of time an interrupted restore can remain in the Restartable state.
RESTOREINTERVAL minutes (default 1,440 minutes) TSM Client tuning parameters:
Specifies if compression is enabled on the TSM client. The default is No.
Tivoli Storage Manager backup and restore performance with a large number of clients,
Consider using Tivoli Storage Manager Client compression. Compressing the data on the client reduces demand on the network and on the Tivoli Storage Manager server. The reduced amount of data on the server continues to provide performance benefits whenever this data is moved, such as for storage pool migration and storage pool backup.
However, client compression may significantly reduce the performance of each individual client--the reduction will be more pronounced on the slowest client systems.
Compression Yes (multiple clients, slow network, slow server) MEMORYEFFICIENTBACKUP:
With the MEMORYEFFICIENTBACKUP option, TSM backs up one directory at a time. By default, TSM backs up all the directories at once.
The default option is very memory intensive. To save memory on clients with a limited amount of memory and large filesystem files, turn MEMORYEFFICIENTBACKUP on.
RESOURCEUTILIZATION:
Resourceutilization is a client option used to regulate the level of resources (i.e. number of concurrent sessions) the TSM client and server can use during processing.
Multiple sessions are created automatically through a single invocation of a TSM backup/restore or archive/retrieve command.
TAPEPrompt:
The TAPEPrompt option specifies if you want TSM to wait for a tape to be mounted for a backup, archive, restore or retrieve operation, or prompt you for your choice.
TAPEPrompt No
=================================================================================
Sessions Status in TSM server when you give “Q SESS” command in TSM server RUN: sessions is running
Idlew: TSM server waiting for communication from client
Mediawait: waiting for tape mount
Recdw: server is waiting for a message from client
Sendw: tsm server is sending data to client(restore session)
=====================================================================================
==============
Tape drive technology and tape technology Normal capacity Compress LTO1 100 GB 200GB LTO2 200GB 400 GB LTO3 400 gb 800 GB LTIO4 800 GB 1.6 tb