Adminstrative schedules are used make sure that there is a continuity in Backup cycle .
Backup client data Schedule the backups in a proper manner and ensure the backups
are completed in time.
Daily incremental backups
Weekly backup for the faster restores
Log and archive backups should go to the right storage pools in case of LAN free
environment
Make sure to cancel the reclamation or any admin schedule process before backup
schedule start
TSM DB Backup
If you are in roll-forward mode you should consider the size of the recovery log.
In this mode, the recovery log keeps all transactions since the last database
backup and normally requires more space than normal mode does.
We can make use of dbbackup triggers to avoid the out of space in recovery logs
Define DBBackuptrigger DEVclass=devclassname LOGFullpct=percentage
( 50% default ) NUMINCremental=number (6 default)
Snapshot backups can be used during Disaster recovery . It can be used for Point in
restore but not for most recent backups
It will not affect normal incremental series
It will not flush the recovery log space
Proper estimation about the sizes of recovery log and DB log need to be considered.
Make use of DBB triggers and space triggers
Mirroring on Recovery log can help in case of media failures and it does not require more
space
DB backups on scratches
If your backups are stored on site, and you suffer from a disaster, your backups are likely
to also be destroyed. Make sure that your database backups are safe.
For those sites that are running operations 24 hours a day, the database mirroring feature
is the only way to protect against a database media failure.
Schedule database backup immediately following storage pool backup
Use Disaster Recovery Manager to automate the recovery of the TSM database
Recovery Procedures
Database and storage pool information
Hardware information
Best practices make a proper naming convention while you prepare for a DRM
If you do not have a DRM plan schedule the admin schedules to take backup of
Device configuration file and volume history file
It just take the backup of these file or refreshes the file by reading the database to have a
proper sync
Have a proper script to automate the DRM Media movements and to send the offsite
volumes .
Expiration
To have a proper sync and bound with management classes defined on client data
Runs on db, to remove the metadata of obsolete versions .
exp interval 12 ( dsmserv.opt, if 0 - default automated, admin schedule, server restart ,
command manually by expire inventory )
duration parameter
it requires tables in db
MIGRATION
To prevent automatic migration from running, set HIGHMIG attribute of the storage pool
definition to 100.
3 types
manual
admin schedule
update stg stgpoolname hi=0 low=0
but we need to update back to the values
RECLAMATION
We can reclaim unused space or
Parallel
It allows commands in script to run parallelly
Privilege class
Any administrator can issue this command.
Syntax
>>-PARALLEL----------------------------------------------------><
SERIAL
Use this command in a script to ensure that any preceding commands are
complete before proceeding and to ensure any following commands are run
serially.
When a script starts, all commands run serially until a PARALLEL command is
encountered.
Privilege class
Any administrator can issue this command.
Syntax
>>-SERIAL------------------------------------------------------><
Return Code
The script return code following a PARALLEL command will be the same as the
script return code prior to the PARALLEL command. When a SERIAL command
is encountered, the script return code will be set to the maximum return code from
any previous commands run in parallel.
Example
/*run multiple commands in parallel and wait for them to complete before
proceeding*/
PARALLEL
/*back up Three storage pools simultaneously*/
BACKUP STGPOOL PRIMPOOL1 COPYPOOL1 WAIT=YES
BACKUP STGPOOL PRIMPOOL2 COPYPOOL2 WAIT=YES
BACKUP STGPOOL PRIMPOOL3 COPYPOOL3 WAIT=YES
/* wait for all previous commands to finish and set up running serial commands*/
SERIAL
/*after the backups complete, migrate stgpools simultaneously*/
PARALLEL
MIGRATE STGPOOL PRIMPOOL1 DURATION=90 WAIT=YES
MIGRATE STGPOOL PRIMPOOL2 DURATION=90 WAIT=YES
MIGRATE STGPOOL PRIMPOOL3 DURATION=90 WAIT=YES
/*wait for all previous commands to finish*/
SERIAL
/*after migration completes, relcaim storage pools simultaneously*/
PARALLEL
RECLAIM STGPOOL PRIMPOOL1 DURATION=120 WAIT=YES
RECLAIM STGPOOL PRIMPOOL2 DURATION=120 WAIT=YES
RECLAIM STGPOOL PRIMPOOL3 DURATION=120 WAIT=YES
Example
To Illustrate this, assume that the reuse delay parameter is set to 0 so that tapes become
scratch tapes as soon as they are empty.
Monday
A TSM Database Backup is taken on Monday
Tape A1 currently has data for Node ZZ
Tuesday
The data for Node ZZ on tape A1 expires and because the reuse delay parameter is set
to 0 tape A1 becomes a scratch tape
Tape A1 is now immediately used to backup node YYs data
Wednesday
For some reason, you have to restore to the last TSM database backup which was
taken on the Monday.
Because the database is now running as at Monday TSM believes that tape A1 holds
the data for Node ZZ. A decision is made to restore data for Node ZZ which resides
on A1 and TSM complains that the volume is corrupt because the data on the tape is
not what TSM is expecting. In this case if the reuse delay parameter had been set to 2
days then tape A1 would not have been written on and the restore would work as
expected.
Command
Where STGPOOL_NAME is the name of the storage pool and days is the value for
the REUSEDELAY parameter
Example - for 2 days
UPDATE STGPOOL TAPEPOOL REUSEDELAY=2
Best practices using the scripts : Automate the admin schedules using the scripts and
generate the reports .
Canceling Process
UNIX
Explanation : TSM has the list of tables . AWK is used to capture the process number
that need to be cancelled
@echo off
IF EXIST OUT DEL OUT
dsmadmc -id=USERID -password=PASSWORD "q process" | findstr "Space
Reclamation" | awk '{print $1}' > IN
GSAR -s, -r -f IN OUT
IF NOT EXIST OUT ( COPY IN OUT)
ELSE
(ECHO > NUL)
Sending Mails In case of TSM server is down notify the TSM admin
Using return code or dsmserv process
# Check every five minutes to ensure that the TSM application is running
00,05,10,15,20,25,30,35,40,45,50,55 * * * * /usr/local/bin/serverup_check
#########
dsmadmc -id=xxx -pass=xxx 'quit'
#Whether the server is up or down it will return you to the
#prompt
# Now test the return code
if [ $? != 0 ] ;
then
mail -s "TSM IS DOWN" you@domain.com
Fi
#########
In many cases
Health checks
IMP files
DB status