TSM Material Veda

8/17/2019 TSM Material Veda

1/104

TSM 5.5 and TSM 6.3

TSM(TIVOLI STORAGE MANAGER)

THE FIRST NAME OF THE TSM IS ADSM AND AFTER THAT IT WAS ACQUIRED BY IBM, THEN ADSM NAME

HAS BEEN CHANGED TO TSM (TIVOLI STORAGE MANAGER)

TSM IS A ENTREPRISE BACKUP TECHNOLOGY AND BY UISNG TSM WE CAN SECURE THE CUSTOMER DATA

FROM DISASTER.

BY UISNG TSM WE CAN TAKE BACKUP AND ARCHIVE OF THE CUSTOMER DATA

BACKUP: TAKING ADDITIONAL COPY OF THE DATA WHICH IS CHANGING REGULARLY THAT CAN BE USED

FOR SHORT TERM STORAGE

IN BACKUP WE HAVE VERSIONING CONCEPT

RECOVERING THE DATA FROM BACKUP IS CALLED RESTORE

ARCHIVE;

TAKING ADDITIONAL COPY OF THE DATA WHICH IS NOT CHANGING REGULARLY THAT CAN BE USED FOR

LONG TERM STORAGE

IN ARCHIVE WE DO NOT HAVE VERSIONING CONCEPT, WHENEVER WE ARCHIVE THE CUSTOMER DATA

IT ALWAYS TAKES FULL BACKUP ONLY AND ARCHIVE ALWAYS MAITAINS ONLY ONE VERSION.

THE ADVANTAGE OF TAKING ARCHIVE IS WE CAN RE USE HARDWARE OR SPACE IN THE

CLIENT/CUSTOMER MACHINE

RECOVERING THE DATA FROM ARCHIVE IS CALLED RETREIVE

FEATURES OF TSM:

1: PROGRESSIVE INCREMENTAL BACKUP METHODOLOGY OR INCREMENTAL BACKUP

2: TAPE RESOURCE SHARING

3: LAN FREE BACKUP

1: PROGRESSIVE INCREMENTAL BACKUP METHODOLOGY:

IN PROGRESSIVE INCREMENTAL BACKUP METHODOLOGY TSM INITIALLY(FIRST TIME)IT TAKES THE FULL

BACKUP OF THE SYSTEM AND SECOND INCREMENTAL BACKUP ONWARDS IT TAKES THE BACKUP OF

ONLY MODIFIED FILES AND NEW FILES IN THE SYSTEM


2/104

2: TAPE RESOURCE SHARING:

BY UISNG TAPE RESOURCE SHARING CONCEPT, SINGLE NODE DATA OR MULTIPLE NODES DATA CAN BE

STORED AMONG SINGLE TAPE OR MULTIPLE TAPES

3: LAN FREE BACKUP:

BY UISNG LANFREE BACKUP, IF THE CLIENT DAILY BACKUP DATA SIZE IS MORE THAN 150 GB,IBM

RECOMMENDED TO CONFIGURE LAN FREE BACKUP. IN LAN FREEBACKUP DATA WILL BE TRANSFERED

DIRECTLY TO THE TAPE WITH OUT LAN

IN LAN FREE BACKUP DATA TRANSFER HAPPENS THROUGH FIBRE CHANNEL AND BY USING FIBER

CHANNEL DATA TRANSFERMATION WILL BE VERY FASTER

IN NORMAL LAN BACKUPS DATA TRANFORMATION HAPPENS THROUGH SCSI CABLES

COMPARE TO SCSI CABLES FIBRE CHANNELS ARE VERY COSTLIER AND DATA TRANFERMATION WILL BE

FASTER THAN SCSI CABLES

TYPES OF BACKUPS IN TSM:

INCREMENTAL BACKUP OR PROGREESIVE INCREMENTAL BACKUP:

IN INCREMENTAL BACKUP CONCEPT, INITIALLY(FIRST TIME BACKUP) IT TAKES FULL BACKUP OF THE

SYSTEM AND SECOND INCREMENTAL BACKUP ONWRADS IT TAKES THE BACKUP OF ONLY MODIFIED

FILES AND NEW FILES IN SYSTEM

COMMAND TO RUN THE INCREMENTAL BACKUP IS:

I OR INCREMENTAL

SELECTIVE BACKUP:

BY USING SELECTIVE BACKUP, WE CAN TAKE BACKUP OF PARTICULAR FILE OR FOLDER FROM THE

SYSTEM

SLECTIVE BACKUP IS ALWAYS FULL BACKUP ONLY

COMAND TO TAKE SELECTIVE BACKUP IS;

SELECTIVE DIRECTORYNAME - SU=YES

EX:

SELECTIVE D:\TEST\* -SU=YES

HERE * SPECIFIES ALL THE FILES WHICH ARE IN TEST FOLDER

FILES ARE IN THE FORMAT OF .TXT,.DOC.,.JPG


3/104

-SU=YES SPECIFIES ALL THE SUBFOLDERS WHICHA ARE IN THE TEST FOLDER

IMAGE BACKUP:

BY USING IMAGE BACKUP WE CAN TAKE THE BACKUP OF TOTAL DRIVE AS A SINGLE OBJECT

IN IMAGE BACKUP CONCEPT WE CAN NOT TAKE BACKUP OF PARTICULAR FILE OR FOLDER IN DRIVE

EVEN WE WANT TO RESTORE THE DATA FROM IMAGE BACKUP, WE CAN RECOVER TOTAL DRIVE ONLY,

WE CAN NOT RECOVER PARTICULAR FILE OR FOLDER FROM IMAGE BACKUP

THE REASON FOR TAKING IMAGE BACKUP IS, IF TOTAL DRIVE GOT CORRUPTED,, IN THAT CASE WE CAN

RECOVER TOTAL DRIVE DATA FROM IMAGE BACKUP

COMMAND TO TAKE IMAGE BACKUP IS:

BACKUP IMAGE D: E: F:

JOURNALBASED BACKUP:

IN JOURNAL BASED BACKUP CONCEPT WE NEED TO INSTALL JOURNAL ENGINE SERVICE WHILE

INSTALLING THE TSM CLIENT SOFTWARE AND WE NEED TO CREATE JOURNAL DATABASE, THE

JOURANAL DATABASE WILL USE SOME SPACE IN LOCAL DRIVE OF THE CLIENT SYSTEM

WHAT JOURNAL ENGINE WILL DO IS, IT WILL TRACK WHAT EVER THE CHANGES HAPPENING IN THE

CLIENT MACHINE AND THOSE CHNAGES WILL BE CAPTURED BY JOURNAL ENGINE AND STORES IN THE

JOURNAL DATABASE.

WHEN THE SCHEDULE INCREMENTAL BACKUP STARTS INSTEAD OF SCANNING THE WHOLE MACHINE TO

TRACK THE CHANGES, TSM DIRECTLY CONTACTS THE JOURNAL DATABASE AND TAKES THE BACKUP OF

THE FILES FROM JOURNAL DATABASE

THE ADVANTAGE OF JOURNALBASED BACKUP IS, BACKUP PERFORMANCE WILL BE VERY FASTER AND

THERE IS NO NETWORK TRAFFIC

JOURNAL BASED BACKUP CAN BE USED IN LOW NETWORK BANDWIDTH ENVIRONMENTS.

COMPONENTS OF TSM:

1) TSM DATABASE

2) RECOVERY LOG

3) STORAGE POOLS

4) POLICY MANAGEMENT

5) SCHEDULING


4/104

6) BA CLIENT

7) ADMINISTRATIVE INTERFACE

1) TSM DATABASE:

IT IS MAIN PART OF THE TSM SERVER, IT MAINTAINS META DATA IFORMATION, NODE INFORMATION,

SCHEDULE INFORMATION, POLICY INFORMATION AND LOCATION OF THE DATA(WHICH TAPE THE DATA

IS STORED)

TSM DATABASE IN BUILT WITH SQL AND THE MAXIMUM SIZE OF THE TSM DATBASE in TM 5.5 is 530GB

METADATA: IT IS STRUCTURE OF THE DATA (LOCATION OR DDRESS), META DATA SIZE ALWAYS IN BYTES

OR KILO BYTESS.

TSM Database uses Local drive of the system in which machine the TSM server is installed and we need

to create database volumes in TSM server

The Information which stores in TSM server database, that information stores in the TSM database

volumes.

2) RECOVERY LOG:

WHAT EVER TRANSACTIONS (BACKUPS) HAPPEN TO THE TSM SERVER DATBASE, RECOVERY LOG

MAITAINS RECORDS OF THOSE TRANSCTIONS

Recover log uses Local drive of the system in which machine the TSM server is installed and we need to

create Log volumes in TSM server

The Information which stores in TSM server Recover log, that information stores in the TSM recover log

volumes.

THERE RE TWO TYPES OF MODES IN RECOVER LOG:

a) NORML MODE

b) ROLL FORWARD MODE

NORMAL MODE: THE DEFAULT MODE OF THE RECOVERY LOG IS NORML MODE, WHEN THE RECOVERY

LOG IS IN NORMAL MODE, WHAT EVER TRANSACTIONS HAPPEN TO THE TSM SERVER DATABASE,

RECOVERY LOG MAINTAINS RECORDS OF THOSE TRANSACTIONS, ONCE THE TRANSACTION IS

COMPLETED, THOSE RECORDS WILL BE ERASED FROM THE RECOVERY LOG

THE DISADVANTAGE OF NORMAL MODE IS WE CAN NOT RECOVER THE TSM SERVER DATABSE TO THE

MOST CURRENT STATE.

ROLL FORWARD MODE: WHEN THE RECOVERY LOG IS IN ROLLFORWARD MODE, WHAT EVER

TRNSACTIONS HAPPEN TO THE TSM SERVER DATABASE, RECOVER LOG MAINTAINS RECORDS OF THOSE


5/104

TRANSACTIONS, EVEN THE TRANSACTIONS ARE COMPPLETED, THOSE RECORDS STILL EXISTS IN THE

RECOVERY LOG

WHENEVER WE TAKE THE TSM DATABSE BACKUP, THEN ONLY THOSE RECORDS WILL BE ERASED FROM

THE RECOVERY LOG.

THE ADVANTAGE OF ROLLFORWARD MODE IS, WE CAN RECOVER THE TSM SERVER DTABASE TO THE

MOST CURRENT STATE(up to date)

THE MAXIMUMS SIZE OF RECOVER LOG IS 13 GB

NOTE: WHEN BACKUP STRTS FOR MACHINE, BY DEFAULT TWO SESSIONS ESTBLISH BETWEEN TSM

CLIENT AND TSM SERVER

ONE SESSIONS IS FOR MET DATA AND ANOTHER SESSIONS IS FOR ACTUAL DATA

WHEN THE DATA TRANSFER STARTS FROM TSM CLIENT TO TSM SERVER, THAT DATA TRANSFER CAN BE

CALLED AS TRANSACTION.

3) STORAGE POOLS:

Storage pools are the place or location where the client actual data stores or storage pools are the

collection of volumes

There the three types of storage pools in TSM

a) Primary storage pools

b) Copy storage pools

c) Active data pools

Primary storage pools

In primary storage pools we have the following

1) Primary disk storage pool

2) Primary tape storage pool

1)Primary disk storage pool: primary disk storage pool also can be called as random access storage pool,

when the client back starts initially actual data goes to disk storage pool and once he disk storage pool

is full, then the data will be migrated from disk stgpool to tape storage pool

Moving the data from disk storage pool to tape storage pool is called migration

2) Primary tape storage pool: Primary tape storage pool also can be called as sequential access storage

pool. Primary storage pool uses tapes in the tape library and primary storage pool tapes always should


6/104

be within the tape library, when the data migrates from disk storage pool to tape storage pools, finally

data stores in the tapes

b) copy storage pools:

By using copy storage pools, we can take the backup of the data from primary tape to copy tapes, copy

tapes also uses the tapes with the tape library, Once the primary tape data is backed up to copy tapes,

we need to eject the copy tapes from the tape library and we need send the copy tapes to offsite

location

The reason for taking backup of primary tape data to copy tape is, if any of the primary tape is damaged,

in that case we can recover the primary tape data from copy tapes by using restore volume process.

c) Active data pools:

active data pools contains only active versions of the client data, the advantage of active data pools are,

recovery performance will be very faster, if any latest backup data needs be recovered.

4) Policy management concept:

Policy management concept describes, how tsm treats the client data i.e how many no of versions, how

many no of days and where to store the client data (name of stg pool)

In policy management we have the following parameters:

Hierarchy of policy management is as below:

1) Policy Domain

2) Policy Set

3) Management Class

4) Copy Group

a) Backup

b) Archive

POLICY DOMAIN:

Policy domain is set or group of nodes is called as policy domain. Policy domain contains policy set and

in each policy domain we can have multiple policy sets but at a time only policy set can be activated.

Def Dom domainname

Ex:

Def dom testdom


7/104

POLICY SET:

Policy set contains Management class AND in one policy set we can have multiple Management classes.

But always one management class is default one.

Def pol domainname policysetname

Ex:

Def pol testdom testpol

Management Class:

Management class contains Copygroup and in copy group we have two types, those are backup copy

group and archive copy group

Backup copy group: The client data which is backedup, that data uses the backup copy group

Archive copy group: The Client data which is archived, that data uses the archive copy group

Syntax to define management class:

Def mgmt domainname policysetname mgmtclassname

EX:

DEF MGMT TESTDOM TESTPOL TESTMGMT

Assigning the management class to default one:

Assign defmgmt domainname policysetname managementclassname

EX:

ASSIGN DEFMGMT TESTDOM TESTPOL TESTMGMT

The reason for assigning the management class to default one is, the nodes which are assigned to the

policy domain, those nodes by default use the default managemnet class.

COPY GROUP:

COPY GROUP CONTAINS RETENTION PARAMETERS WHICH CONTROLS THE CUSTOMER DATA

SYNTAX TO DEFINE BACKUP COPY GROUP:

DEF COPYG DOMAINNAME POLICYSETNAME MGMTCLASSNAME T=BACKUP

DESTINATION=STGPOOLNAME VEREXIST=5 VERDEL=3 RETEXTRA=30 RETONLY=60

SERIALIZATION=STATIC/SHARED STATIC/DYNAMIC/SGHARED DYNAMIC MODE=MODIFIES/ABSOLUTE


8/104

Ex;

Def copyg testdom testpol testmgmt t=b destination=storagepoolname verexist=3 verdel=1 retextra=30

retonly=60 serialization=static/shared static/dynamic/shared dynamic mode=modified

PARAMETERS UNDER BACKUP COPYGROUP

1)VERSION EXIST: (verexist)

This parameter specifies, how many number of versions the TSM server can maintain for file

If we mention verexist=3 then three versions of the file can be maintained in TSM server

2) VERSION DELETE: (verdelete)

This parameter specifies, how many number of versions of a file the TSM server can maintain for a

file, once the file is deleted from the client system

If we mention verdel=2 then two versions of the file mainatain by TSM server, once the file is deleted

form the client system

3) Retention extra: (Retextra)

This parameter specifies, how many number of days, the tsm server can maintain the inactive files.

If we mention Retextra=30, then inactive files can be maintained for 30 days and after 30 days inactive

files will be deleted from the TSM server

4) RETENTION ONLY: (RETONLY)

This parameter how many number of days, the TSM server can maintain the last copy of the file, Once

the file is deleted from the client system.

If we mention retonly=60, then last copy of the file will be maintained for 60 days and after 60 days, last

copy also be deleted from the TSM serve

6) SERIALIZATION:

This parameter specifies, how TSM treats the open files, open files are nothing but, if the file is being

used by any other user or application, when the backup is running, then TSM treats those files as open

files

There are four options in serialization: and those are Static/shared static/dynamic/ shared dynamic

a) Static:

If the serialization is in static mode, then TSM tries to take the backup of the open file for one time and

TMS will not take the backup of the file (which means the file will be skipped from the backup)


9/104

b) Shared static:

If the serialization is in shared static mode, then TSM tries to take the backup of the file for four times

and even fourth time also the file is being in use, then TSM will not take the backup of the files.

The default mode of the serialization is shared static.

c) DYNAMIC:

If the Serialization is in dynamic mode, then TSM tries to take the backup pf the file for one time and it

take the backup of the file, regardless whether the file is being in use or not

d) SHARED DYNAMIC:

if the serialization is in shared dynamic mode, then TSM tries to take the backup of the file for four

times, even fourth time also, the file is being in use, then TSM takes the backup of the file, regardless,

the file is being in use or not.

e)Mode=(modified/absolute):

The default one is mode=modified

Modified: if we use modified option, then TSM takes the backup only modified and changed file when

incremental backup is running

Absolute: If we use absolute option, then TSM takes backup of all the files regardless whether the files

are being modified or not, when the incremental backup is running.

SYNTAX TO DEFINE ARCHIVE COPY GROUP:

DEF COPYG DOMAINNAME POLICYSETNAME MGMTCLASSNAME T=ARCHIVE

DESTINATION=STGPOOLNAME RETVERSION=360

Ex;

def copyg testdom testpol testmgmt t=archive destonation=storage pool name retversion=365

RETENSION VERSION: (RETVER)

This parameter specifies how many number of days, the TSM server can maintain the archive data

The default value of the retversion is 365

VALIDATING AND ACTIVATION OF POLICY SET:

Once we defined copy groups, then we need to validate and activate the policyset by using the following

commands

Validate pol domainname policysetname:


10/104

Validate pol testdom testpol

Activate pol domainname policysetname:

Activate pol testdom testpol

The reason for Validating and activating the Policyset:

Ø Validating the policy set is nothing but TSM Server verifies the policy Mgmt hierarchy is defined in

correct order or not.

Sometimes validating policy set fails, if we forgot assigning the management class default one or if we

give the destination parameter as copy storage pool

Ø once the validation of policy set is done, we need to activate the policy set.

MANAGEMENT CLASS BINDING:

Sometimes customer wants different retentions, but he wants to implement this with in the same policy

domain and same policyset but with different management classes, in this case we need to create

multiple managemnet classes in the same policy domain and same policyset

For example we have two managemnet classes’ testmgmt and testmgmt1 created in same policy

domain TESTDOM and same policyset TESTPOL

Few clients need to use testmgmt and few clients need to use testmgmt1

In this scenario, we need to make one managemnet class testmgmt to default one and the nodes which

are assigned to policy domain testdom, those nodes by default uses the default managemnet class

The other nodes which needs to be used the another managemnet class testmgmt1, for those nodes we

need to add the management class definition in client configuration file dsm.opt which is available in

client machine BA client directory dsm.opt with the foolwing syntax;

DIRMC TESTMGMT1 or include “*:/…/…/* ” TESTMGMT2

The other node starts using the second management class TESTMGMT1

5) Scheduling:

It is automated process of taking backup of the client system and to run the TSM admin jobs (TSMMaintenance jobs or TSM Housekeeping jobs).

There are two types of schedules in TSM Server they are:

a) Client Schedule

b) Admin schedule


11/104

a) CLIENT SCHEDULE:

By using client schedules we can take the backup of the client systems.

Syntax to define client schedule:

Def schedule domainname schedulename t=client action=i/selective/imagebackup startdate=date

start=time period=1 periodunits=days duration=1 durationunits=hours schedulestyle=classing/enhanced

Ex:

Def sched testdom testsched t=client action=I startd=today startt=now action=I duration=1

durationunits=hours period=1 perunits=days

Parameters under Client Scheduling:

A) START DATE:

This parameter specifies from which date the schedule has to begin.

B) START TIME:

This parameter specifies at what time of the day the schedule has to be run or executed.

c) DURATION and DURATION UNITS

This parameter specifies the length of the schedule start up window.

For example if you give duration=1 and duration units=hours and the schedule start time is 7 PM, then

the schedule may starts at any time between 7PM to 8 PM

e) PERIOD and PERIOD UNITS

This Parameter specifies how frequent the schedule has to be run. Period is mentioned in Number.

If we give period=1 perunits=days then the schedule run for every one day.

g)SCHEDULE STYLE:

There are two types of schedule styles in TSM they are

1) Classic

2) Enhanced

Default schedule style of TSM server is Classic. In real- time also we will configure schedule under Classic

style only.


12/104

In classic schedule we have the following options to run the schedules

Daily, weekly, monthly, yearly

And in Enhanced schedule we have the following options

Day of week, week of month, month of the year

SCHEDULE MODES:

There are two types of schedule Modes in TSM Server.

a)

Client polling

b)

Server prompted

a) CLIENT POLLING:

In this mode client machine contacts with the TSM Server and asks the TSM Server whether there is any

schedule to be run for this client machine at this moment, then TSM Server notifies to the client, that

there is no schedule at that point of time, then the client goes to sleep mode and again after some time

client contacts the TSM Server.

So Client continuously contacts the TSM Server until it gets the Schedule details from the TSM server.

For configuring client polling mode we have to modify the client configuration file i.e., dsm.opt file like

this, Enter the below command in dsm.opt file to configure client pooling mode:

Schedmode polling

The disadvantage of the client polling mode is there will be network utilization in the environment

because clients continuously contacts the TSM server.

b) SERVER PROMPTED:

In this mode TSM Server itself contacts the node or client machine regarding the schedule and notifies

to the client that there is a schedule to be run for this client machine.

Then client receives the schedule details for the TSM server and starts the backup of the client system

Once the backup is completed, then client sends a notification to the TSM server stating that the

schedule backup got completed successfully

To configure schedule mode as server prompted then we have to mention the below command in client

configuration file i.e., dsm.opt file.

Schedmode prompted


13/104

The Advantage of server prompted mode is , there won’t be any network utilization in the environment

and we can also run the backups from TSM server itself.

Schedmode prompted can be used in high security environments

B) ADMIN SCHEDULE:

This admin schedules run on TSM Server. To maintain the TSM Server clean. This jobs or schedules are

also known as TSM admin/ Maintenance/housekeeping jobs.

There are different types of Admin jobs they are:

a)STORAGE POOL BACKUP:

By using storage pool backup, we can take the backup of primary tape data to copy tapes

After taking backup of primary tape data to copy tapes, then we need eject the copy tapes from Tape

library and we need to send those offsite location.

The Advantage of taking backup of primary tape data to copy is tape is, if any of the primary tape is

damaged, we can recover the primary tape data from copy tapes

Backup stg primarystoragepoolname copystoragepoolname maxpr=number

Maxprocess parameter specifies how many number of parallel process run at a time

b)TSM DB BACKUP:

By using TSM DB backup, we can take the backup of TSM server database.

Whenever we take the TSM DB backup we always use scratch or new tapes for TSM DB backup.

Backup db devciceclass=deviceclassname type=full scratch=yes/no

Once TSM Database backup is completed, then we need to eject the copy tapes and TSM db backup

tapes from the tape library and we need to send those tapes to offsite location.

c) EXPIRE INVENTORY PROCESS:

It is a process of deleting the expired data from the TSM Server database based on the retention

parameters

“Expire inventory” duration=60

Duration parameter specifies how many number of minutes the expiration process should run, if we give

duration=60, then expiration process runs for 60 minutes and after 60 minutes, expiration process will

be automatically cancelled by TSM server

d)MIGRATION:


14/104

Initially when the client backup starts the actual data is transferred to primary disk storage pool and

once the disk storage pool is full then the data from disk storage pool will be migrated to primary tape

storage pool..

Migrate stgstgpoolname low=%

Here parameter LOW specifies how much percentage of the data should be moved to primary tape

storage pool.

If we give LOW=0, then data completely moved to tape storage pool and then disk storage pool

becomes empty

Moving the data from disk storage pool to tape storage pool is called migration.

e)RECLAMATION:

It is process of moving the unexpired data from fragmented tapes to another filling tapes, after moving

the data from fragmented tapes to another filling tape, then the fragmented tape becomes empty and

those tapes can be reused as scratch

1) ONSITE RECLAMATION:

It is process of moving the unexpired data from fragmented tapes to another filling tapes. After moving

the unexpired data from fragmented tapes, then fragmented tapes become empty and those tapes can

be reused as scratch tapes with in the tape library.

If we perform the reclamation for onsite tapes that process can be called as on-site reclamation.

Note: Fragmented tapes are nothing but, the tapes which are less percentage utilized and their statusshown as full

After data expiration Meta data entries will be deleted from the TSM DB database, But the actual data

still remains in the tapes, but in the TSM server database the tapes percentage utilization shows as less

but their status shows in FULL

When we run the reclamation for those volumes, then UN expired data will be moved to another filling

tape and then the tape becomes scratch tape.

Reclaim stg storagepoolname threshold=%

Ex: Reclaim stg tapestg Th=90

Here reclamation threshold (Th), we have given as 90, then reclamation runs for the volumes which are

0-10% utilized with in the storage pool TAPESTG and those volumes data will be moved to another filling

tape, after moving the data, the tapes become scratch tapes and those tapes can be reused as scratch.


15/104

Note: Reclamation can be performed on sequential access volumes (Tapes) only, we cannot perform the

reclamation on disk volumes

Reclamation can be performed on storage pool level, when we run the reclamation data moves form

tape to tape only

2) OFFSITE- RECLAMATION:

Offsite data expires in the same way of onsite data during the expiration process, when offsite tapes are

eligible for reclamation, then TSM Identifies the onsite volumes which contains the valid data remaining

in the offsite volumes. Then we start the reclamation for offsite volumes in TSM server, then TSM

mounts the onsite volumes and copy the data to another copy filling and copy new tape and again this

copy tapes need to be sent offsite

Once the data is copied, then the Copy tape which is in offsite location will be updated to

VAULTRETEREIVE state in the TSM server database, we need to recall those tapes from offsite and those

tapes can be used as scratch tapes.

Reclaim stg copystoragepoolname threshold=%

SYNTAX TO DEFINE ADMIN SCHEDULE:

DEF SCHEDULE SCHEDULENAME T=ADMIN CMD=”COMMAND TO RUN” ATIVE=YES STARTDATE=DATE

STARTTIME=TIME PERIOD=1 PERU=DAYS DURATION=1 DURU=HOURS

Procedure to create Admin schedule to run the Storage pool backup:

Def schedule STGBACKUP t=admin cmd=”backup stg primarystg copystg maxpr=2” active=yesstartd=date startt=time duration=1 durationunits=hours period=1 perunits=days

=====================================================================================

===============================================================================

Device class:

Device class represents set of storage devices and type of the Device

TSM Server supports multiple storage device classes.

They are DISK, LTO AND FILE DEVICEES

1) DISK DEVICE CLASS:

By using Disk Device Class we can create primary Disk storage pools. Disk device class also can be called

as random access device class, by default at the time of installation itself we get Disk device class. We


16/104

have to create disk storage pools by using disk device class, once the primary disk storage pool is created

then we have to create the volumes for this disk storage pool.

PRIMARY DISK STORAGE POOL CREATION:

IN TSM SERVER WE NEED TO CHECK THE AVAILABLE DEVICE CLASSES BY USING “Q DEVC” COMMAND

BY DEFAULT WE CAN SEE THE DISK DEVICE CLASS IN TSM SERVER AND BY UISNG DISK DEVICE CLASS WE

CAN CREATE DISK STORAGE POOL, WE DON’T NEED TO CREATE DISK DEVIVE CLASS IN TSM SERVER

SEPARATELY

SYNTAX TO DEFINE DISK STORAGE POOL BY USING DISK DEVICE CLASS:

DEF STG STGNAME DEVICECLASSNAME POOLTYPE=PRIMARY LOWMIN=70 HIMIG=90

EX:

Define stg TESTSTG DISK Pooltype=primary LOWMIN=70 HIMIG=90

ONCE WE CREATED THE DISK STORAGE POOL, WE NEED TO CREATE STORAGE POOL VOLUMES BY USING

THE FOLLOWING COMMAD

SYNTAX;

DEF VOL VOLUMENAME STGPOOLNAME F=SIZE (MB)

EX:

Def vol TESTSTG F:\TESTSTG\teststg1.dsm f=1000



ONCE WE CREATED THE STORAGE POOL VOLUMES, SPACE IS AUTOMATICALLY ALLOCATED TO THE

STORAGE POOL

TSM USES THE LOCAL SPACE FOR THE DISK STGPOOL AND WE NEED TO SELECT ANY OF THE DRIVE OF

THE SYSTEM, IN WHICH MACHINE TSM SERVER IS INSTALLED

HERE WE ARE USING SPACE IN F DRIVE FOR DISK STORAGE POOL and the CAPACITY of disk storage pool

is 3 GB

2) LTO CLASS:

By using LTO device class we can create primary and copy tape storage pools

LTO device class also can be called as sequential access device class


17/104

Before defining LTO device class, we have to define Tape Library in TSM server and after defining the

tape library, we need to define the LTO class by using tape library. Under LTO class we have to define

primary and copy tape storage pools which consists of tapes.

Command to define a library:

Def library libraryname librarytype=SCSI

EX; DEF LIBRRAY 1BM3584 librarytype=SCSI

THE FOLLOWING ARE THE IBM TAPE LIBRARIES WHICH ARE SUPPORTED BY IBM

1BM3583, IBM3584, TS3100, TS3310

Procedure to define LTO class:

ONCE WE DEFINED THE TAPE LIBRARY, THEN WE NEED TO DEFINE DEVICECLASS WITH TYPE LTO with the

following command

Def devc deviceclassname devt=LTO library=libraryname mountlimit=number mountretention=minutes

Ex:

DEF DEVC LTOCLASS DEVCT=LTO LIBRARY=IBM3584 MOUNTLIMIT=20 MOUNTRETENTION=60

HERE WE HAVE DEFINED THE DEVICE CLASS NAME LTOCLASS WITH TYPE LTO

MOUNT LIMIT: Here mount limit parameter specifies how many no. of tape mounts the device class

should allow at a time.

MOUNT RETENTION: This parameter specifies how many no. of minutes the tape can be in ideal state in

the tape drive once the read/ write operation was done on the mounted tape.

If we specify mount retention=60 then the tape will be in ideal state in the tape drive for 60 minutes and

after 60 minutes the tape will automatically dismounted from the tape drive.

If any tape request comes in between or within 60 minutes when the tape is in ideal state then the tape

will get dismounted automatically and new tape will get mounted.

ONCE WE DEFINED THE LTO DEVICE CLASS THEN WE NEED TO DEFINE THE PRIMARY AND COPY TAPE

STORAGE POOLS BY USING THE LTOCLASS

CREATING PRIMARY TAPE STORAGE POOL BY USING device class LTOCLASS:

DEF STG STGPOOLNAME DEVICECLASSNAME POOLTYPE=PRIMARY MAXSCRATCH=NUMBER

EX:

DEF STG TAPESTG LTOCLASS POOLTYPE=P MAXSCRATCH=100


18/104

HERE MAXSCARATCH PARAMETER SPECIFIES THE MAXIMUM NO OF TAPES THE STORAGE POOL

TAPESTG CAN USE THE TAPES WITH IN THE TAPE LIBRARY.

CREATING COPY TAPE STORAGE POOL BY UISNG LTOCLASS:

DEF STG STGPOOLNAME DEVICECLASSNAME POOLTYPE=COPY MAXSCRATCH=NUMBER

EX:

DEF STG COPYSTG LTOCLASS POOLTYPE=COPY MAXSCRATCH=100

NOTE: NOW WE HAVE CREATED TWO STGPOOLS TAPESTG AND COPYSTG BY UISNG THE LTOCLASS

NOW BOTH THE PRIMARY AND COPYSTGPOOL USES THE TAPES WITH IN THE TAPE LIBRARY

3)FILE DEVICE CLASS:

By using file device class we can use disk as sequential access device. File device class also can be called

as sequential access device class.

Command to define file device class is:

Def devc deviceclassname device=file directory=location mountlimit=20 mountretention=60 maxsize=2G

EX:

DEF DEVC FILECLASS DEVCT=FILE DIRECTORY=’F:\’ MAXSIZE=2G MOUNTLIMIT=20

MOUNTRETENTION=60

HERE WE HAVE CRETAED A FILE DEVICE CLASS WITH NAME FILECLASS AND THIS DEVICE CLASS USED F:DRIVE IN THE MACHINE AS SEQUENTIAL ACCESS

HERE F: DRIVE LOCAL DRIVE OF THE MACHINE IN WHICH MACHINE TSM SERVER IS INSTALLED.

DIRECTORY:

This parameter specifies, the location of the disk which are using as sequential access

Max size:

This parameter specifies the max Size of the each volume which are created by using file device class

and that volumes acts as sequential access

The Volumes which are created by using file device class that volume suffix with .BFS

ONCE WE CREATED THE FILE DEVICE CLASS, THEN WE NEED TO CREATE STGPOOLS BY USING FILE

DEVICE CLASS FILE CLASS


19/104

When the data is Coming to the storage pools which are created by using file device class that data

stores in the F drive( based on the directory location in File device class) and volumes will be

automatically created with .BFS and each volume size is depends on the maxsize parameter in the file

device class definition.

SYATNTAX TO CRETAE PRIMARY AND COPY STGPOOLS BY USING FILE DEVICE CLASS FILECLASS:

DEF STG STGNAME DEVCNAME POOLT=P MAXSCRATCH=100

EX:

DEF STG TAPESTG FILECLASS POOLT=P MAXSCRATCH=100

HERE STGPOOL TAPESTG CAN CREATE MAXIMUM 100 VOLUMES IN THE DIRECTORY LOCATION F:

AND EACH VOLUME SIZE IS 2GB, I.E THE STG TAPESTG CAPACITY IS 200GB

THE VOLUMES WHICH ARE CRETAED BY UISNG FILE DEVICE CLASS ARE SUFFIX WITH .BFS

CREATING COPY STGPOOL BY USING FILE DEVICE CLASS FILECLASS:

DEF STG COPYSTG FILECLASS POOLT=COPY MAXCSRATCH=100

THIS COPY STORAGE POOL COPYSTG ALSO CAN CREATE MAXIMUM 100 VOLUMES IN F DIVE AND EACH

VOLUME SIZE IS 2G, BASED ON THE MAXCAPACITY PARAMETER IN FILEDEVICE CLASS DEFINTION.

NOTE:

IN OUR LAB ENVIRONMENT, AS WE DONOT HAVE TAPE LIBARRAY WE ARE USING FILE DEVICE CLASS TO

CREATE SEQUENTIAL ACCESS STORAGE POOLS

NOW THE LAB STARTS FROM HERE:

REGISTERING TSM ADMINISTRATOR:

1) REG ADMIN ADMINNAME ADMINPASSWORD

tsm: VEDATSM>REG ADMIN NAGESH NAGESH

ANR2068I Administrator NAGESH registered.

2:TO CHECK THE AVAILABLE ADMINS IN TSM SERVER

tsm: VEDATSM>Q ADMIN

Administrator Days Since Days Since Locked? Privilege Classes

Name Last Access Password Set


20/104

-------------- ------------ ------------ ---------- ----------------------

ADMIN


21/104

(MB) (MB) (MB) (MB) (bytes) Pages Util

--------- -------- --------- --------- ------- --------- --------- ----- -----

4,000 3,012 988 3,008 4,096 771,072 921 0.1 0.1

2)CREATING DATABASE VOLUMES:

DEFINE DBV VOLUMENAME F=SIZE (SIZE IN MEGA BYTES)

tsm: VEDA-PC_SERVER1>DEF DBV D:\TSMDB\DB1.DSM F=2000

ANR2491I Volume Creation Process starting for D:\TSMDB\DB1.DSM, Process Id 3.

ANS8003I Process number 3 started.

3)CHECK THE TSM DATABASE VOLUMES:

Q DBV

tsm: VEDA-PC_SERVER1>Q DBV

Volume Name Copy Volume Name Copy Volume Name Copy

(Copy 1) Status (Copy 2) Status (Copy 3) Status

---------------- ------ ---------------- ------ ---------------- ------

D:\TSMDB\DB1.DSM Sync'd Undef- Undef-

ined ined

D:\TSMDB\DB2.DSM Sync'd Undef- Undef-

ined ined

4)ASSIGNING THE SPACE TO TSM DATABASE

EXTEND DB SIZE (SIZE IN MB)

tsm: VEDA-PC_SERVER1>EXTEND DB 1000

ANR2248I Database assigned capacity has been extended.

5) REDUCING THE TSM DATABASE SIZE

REDUCE DB SIZE


22/104

tsm: VEDA-PC_SERVER1>REDUCE DB 1000

ANR2250I Database assigned capacity has been reduced.

6) DELETING DATBASE VOLUMES:

tsm: VEDA-PC_SERVER1>DEL DBV D:\TSMDB\DB4.DSM

ANR2243I Database volume D:\TSMDB\DB4.DSM deleted.

=====================================================================================

========

TSM RECOVERY LOG:

TO CHECK THE RECOVERY LOG

tsm: VEDA-PC_SERVER1>Q LOG

Available Assigned Maximum Maximum Page Total Used Pct Max.

Space Capacity Extension Reduction Size Usable Pages Util Pct

(MB) (MB) (MB) (MB) (bytes) Pages Util

--------- -------- --------- --------- ------- --------- --------- ----- -----

8 8 0 0 4,096 1,536 398 25.9 26.6

2) TO CHECK THE RECOVERY LOG VOLUMES:

tsm: VEDA-PC_SERVER1>Q LOGV

Volume Name Copy Volume Name Copy Volume Name Copy

(Copy 1) Status (Copy 2) Status (Copy 3) Status

---------------- ------ ---------------- ------ ---------------- ------

C:\PROGRAM Sync'd Undef- Undef-

FILES\TIVOLI\T- ined ined

SM\SERVER1\LOG-

1.DSM

3) CREATING RECOVERY LOG VOLUMES:


23/104

DEF LOGV VOLUMENAME F=SIZE

tsm: VEDA-PC_SERVER1>DEF LOGV D:\TSMLOG\LOG1.DSM F=2000

ANR2491I Volume Creation Process starting for D:\TSMLOG\LOG1.DSM, Process Id 11.


4) ASSIGNING SPACE TO RECOVERY LOG

EXTEND LOG SIZE

tsm: VEDA-PC_SERVER1>EXTEND LOG 2000

ANR2269I Recovery log extension process initiated (process ID 12).


5) DELETING RECOVERY LOG VOLUME:

DEL LOGV VOLUMENAME

tsm: VEDA-PC_SERVER1>DEL LOGV "C:\PROGRAM FILES\TIVOLI\TSM\SERVER1\LOG1.DSM"

ANR2264I Delete process initiated for recovery log volume C:\PROGRAM

FILES\TIVOLI\TSM\SERVER1\LOG1.DSM (process id 16).


6) REDUCING REOVERY LOG SIZE:

REDUCE LOG SIE

tsm: VEDA-PC_SERVER1>REDUCE LOG 2000

ANR2270I Recovery log assigned capacity has been reduced.

=====================================================================================

STORAGE POOL CREATION:

DISK STORAGE POOL CREATION:

1) TO CHECK THE STORAGE POOL

tsm: VEDA-PC_SERVER1>Q STG

Storage Device Estimated Pct Pct High Low Next Stora-


24/104

Pool Name Class Name Capacity Util Migr Mig Mig ge Pool

Pct Pct

----------- ---------- ---------- ----- ----- ---- --- -----------

ARCHIVEPOOL DISK 0.0 M 0.0 0.0 90 70 FILPOOL1

BACKUPPOOL DISK 0.0 M 0.0 0.0 90 70 FILPOOL1

DISKPOOL DISK 4.0 M 0.0 0.0 90 70

FILPOOL1 FILEDEV1 0.0 M 0.0 100.0 90 70

SPACEMGPOOL DISK 0.0 M 0.0 0.0 90 70

2)CHECK THE DEVICE CLASS:

Q DEVC

tsm: VEDA-PC_SERVER1>Q DEVC

Device Device Storage Device Format Est/Max Mount

Class Access Pool Type Capacity Limit

Name Strategy Count (MB)

--------- ---------- ------- --------- ------ -------- ------

DISK Random 0

3) BY USING DISK DEVICE CLASS, WE CAN CREATE DISK STORAGE POOL

DEF STG STGPOOLNAME DEVICECLASSNAME POOLTYPE=PRIMARY NEXTSTG=TAPESTGPOOLNAME

(TARGET STGPOOL NAME)

tsm: VEDA-PC_SERVER1>DEF STG TESTSTG DISK POOLTYPE=PRIMARY

ANR2200I Storage pool TESTSTG defined (device class DISK).

Q STG




Pct Pct


25/104

----------- ---------- ---------- ----- ----- ---- --- -----------

TESTSTG DISK 0.0 M 0.0 0.0 90 70

4) CREATING STORAGE POOL VOLUMES:

DEFINE VOLUME STGPOOLNAME VOLUMENAME F=SIZE (MB)

tsm: VEDA-PC_SERVER1>DEF VOL TESTSTG D:\TESTSTG\VOLI.DSM F=3000

ANR2491I Volume Creation Process starting for D:\TESTSTG\VOLI.DSM, Process Id 18.


NOW THE STORAGE POOL TESTSTG CAPACITY IS 3 GB




Pct Pct

----------- ---------- ---------- ----- ----- ---- --- -----------

TESTSTG DISK 3 G 0.0 0.0 90 70

tsm: VEDA-PC_SERVER1>DEF VOL TESTSTG D:\TESTSTG\VOL2.DSM F=3000

ANR2491I Volume Creation Process starting for D:\TESTSTG\VOL2.DSM, Process Id 19.





Pct Pct

----------- ---------- ---------- ----- ----- ---- --- -----------

TESTSTG DISK 6 G 0.0 0.0 90 70

5) TO CHECK THE STGPOOL VOLUMES:

Q VOLUME == IT DISPLAYS ALL THE STORAGE POOL VOLUMES


26/104

tsm: VEDA-PC_SERVER1>Q VOL

Volume Name Storage Device Estimated Pct Volume

Pool Name Class Name Capacity Util Status

------------------------ ----------- ---------- --------- ----- --------

D:\TESTSTG\VOL2.DSM TESTSTG DISK 3.0 G 0.0 On-Line

D:\TESTSTG\VOLI.DSM TESTSTG DISK 3.0 G 0.0 On-Line

6) TO CHECK VOLUMES FOR PARTICULAR STGPOOL:

Q VOL STG=TAPESTG

tsm: VEDA-PC_SERVER1>Q VOL STG=TESTSTG



------------------------ ----------- ---------- --------- ----- --------



7) DELETING STORGAE POOL VOLUME:

DEL VOLUME VOLUMENAME




------------------------ ----------- ---------- --------- ----- --------




tsm: VEDA-PC_SERVER1>DEL VOL D:\TESTSTG\VOLI.DSM


27/104

ANR2220W this command will delete volume D:\TESTSTG\VOLI.DSM from its storage pool after verifying

that the volume contains no data.

Do you wish to proceed? (Yes (Y)/No (N)) Y




------------------------ ----------- ---------- --------- ----- --------



DEFINING FILE DEVICE CLASS:

DEF DEVC DEVCNAME DEVT=FILE DIRECTORY='PATH' MAXCAP=SIZE

tsm: VEDA-PC_SERVER1>DEF DEVC FILECLASS DEVT=FILE DIRECTORY='E:\FILEDEVC\' MAXCAP=4G

ANR2203I Device class FILECLASS defined.

=====================================================================================

===

CREATING PRIMARY SEQUENTIAL ACCESS STORAGE POOLBY USING FILE DEVICE CLASS FILECLASS:

DEF STGT STGNAME DEVCNAME POOLT=PRIMARY MAXSCRATCH=NOOF SCRATCH VOLUMES

tsm: VEDA-PC_SERVER1>

tsm: VEDA-PC_SERVER1>DEF STG TAPESTG FILECLASS POOLT=PRIMARY MAXSCRATCH=50

ANR2200I Storage pool TAPESTG defined (device class FILECLASS).

CREATING COPY SEUENTIAL ACCESS STORAGE POOL:

DEF STGT STGNAME DEVCNAME POOLT=COPY MAXSCRATCH=NOOF SCRATCH VOLUMES

tsm: VEDA-PC_SERVER1>DEF STG COPYSTG FILECLASS POOLT=COPY MAXSCRATCH=50

ANR2200I Storage pool COPYSTG defined (device class FILECLASS).


28/104




Pct Pct

----------- ---------- ---------- ----- ----- ---- --- -----------

COPYSTG FILECLASS 0.0 M 0.0

TAPESTG FILECLASS 0.0 M 0.0 100.0 90 70

TESTSTG DISK 12 G 0.0 0.0 90 70

tsm: VEDA-PC_SERVER1>UPD STG TESTSTG NEXTSTG=TAPESTG

ANR2202I Storage pool TESTSTG updated.




Pct Pct

----------- ---------- ---------- ----- ----- ---- --- -----------

COPYSTG FILECLASS 0.0 M 0.0

TAPESTG FILECLASS 0.0 M 0.0 100.0 90 70

TESTSTG DISK 12 G 0.0 0.0 90 70 TAPESTG

=====================================================================================

======

POLICY CREATION:

DEFINING POLICY DOMAIN

DEF DOM DOMAINNAME

tsm: VEDA-PC_SERVER1>DEF DOM TESTDOM


29/104

ANR1500I Policy domain TESTDOM defined.

Policy Activated Activated Number of Description

Domain Policy Default Registered

Name Set Mgmt Nodes

Class

--------- --------- --------- ---------- ------------------------

TESTDOM 0

CREATING POLICYSET:

DEF POLICYSET DOMAINNAME POLICYSETNAME

tsm: VEDA-PC_SERVER1>DEF POL TESTDOM TESTPOL

ANR1510I Policy set TESTPOL defined in policy domain TESTDOM.

tsm: VEDA-PC_SERVER1>Q POL

Policy Policy Default Description

Domain Set Name Mgmt

Name Class

Name

--------- --------- --------- ------------------------

TESTDOM TESTPOL

CREATING MANAGEMENT CLASS:

DEF MGMT DOMAINNAME POLICYSETNAME MGMTCLASSNAME

tsm: VEDA-PC_SERVER1>DEF MGMT TESTDOM TESTPOL TESTMGMT

ANR1520I Management class TESTMGMT defined in policy domain TESTDOM, set TESTPOL.

tsm: VEDA-PC_SERVER1>Q MGMT

Policy Policy Mgmt Default Description

Domain Set Name Class Mgmt


30/104

Name Name Class ?

--------- --------- --------- --------- ------------------------

TESTDOM TESTPOL TESTMGMT Yes

ASSIGNING THE MANAGEMENT TO DEFAULT MANAGEMENT CLASS:

ASSIGN DEFMGMT DOMAINNAME POLCYSETNAME MGMTCLASSNAME

tsm: VEDA-PC_SERVER1>ASSIGN DEFMGMT TESTDOM TESTPOL TESTMGMT

ANR1538I Default management class set to TESTMGMT for policy domain TESTDOM, set

TESTPOL.

CREATING COPY GROUPS:

BACKUP COPY GROUP

DEF COPYG DOMAINNAME POLICYSETNAME MGMTCLASSNAME T=BACKUP

DESTINATION=STGPOOLNAME VERSIONE=5 VERDEL=3 RETEXTRA=60 RETONLY=90

tsm: VEDA-PC_SERVER1>DEF COPYG TESTDOM TESTPOL TESTMGMT T=BACKUP DESTINATION=TESTSTG

VEREXIST=5 VERDEL=3 RETEXTRA=60 RETONLY=90

ANR1530I Backup copy group STANDARD defined in policy domain TESTDOM, set TESTPOL,

Management class TESTMGMT.

tsm: VEDA-PC_SERVER1>Q COPYG T=B

Policy Policy Mgmt Copy Versions Versions Retain Retain

Domain Set Name Class Group Data Data Extra Only

Name Name Name Exists Deleted Versions Version

--------- --------- --------- --------- -------- -------- -------- -------

STANDARD ACTIVE STANDARD STANDARD 2 1 30 60

TESTDOM TESTPOL TESTMGMT STANDARD 5 3 60 90

CREATING ARCHIVE COPY GROUP:

DEF COPYG DOMAINNAME POLICYSETNAME MGMTCLASSNAME T=ARCHIVE DESTINATION=TESTSTG

RETVERSION=400


31/104

tsm: VEDA-PC_SERVER1>DEF COPYG TESTDOM TESTPOL TESTMGMT T=ARCHIVE DESTINATION=TESTSTG

RETVER=400

ANR1535I Archive copy group STANDARD defined in policy domain TESTDOM, set TESTPOL,

management class TESTMGMT.

tsm: VEDA-PC_SERVER1>Q COPYG T=A

Policy Policy Mgmt Copy Retain

Domain Set Name Class Group Version

Name Name Name

--------- --------- --------- --------- --------

TESTDOM TESTPOL TESTMGMT STANDARD 400

VALIDATING THE POLICYSET:

VALIDATE POL DOMAINNAME POLICYSETNAME

tsm: VEDA-PC_SERVER1>VALIDATE POL TESTDOM TESTPOL

ANR1557W The space management migration destination in management class TESTMGMT does not

refer to a defined storage pool: SPACEMGPOOL. If this pool does not exist when policy

set TESTPOL is activated, clients will fail when using this management class to migrate

Space-managed files to the server.

ANR1515I Policy set TESTPOL validated in domain TESTDOM (ready for activation).

ACTIVATING THE POLICYSET:

ACTIVATE POL DOMAINNAME POLICYSETNAME

tsm: VEDA-PC_SERVER1>ACTIVATE POL TESTDOM TESTPOL




space-managed files to the server.

Do you wish to proceed? (Yes (Y)/No (N)) Y


32/104




space-managed files to the server.

ANR1514I Policy set TESTPOL activated in policy domain TESTDOM.

=====================================================================================

=================

REGISTERING NODE IN TSM SERVER:

REGISTER NODE NODENAME NODEPASSWORD DOM=POLICYDOMAINNAME USERID=NONE

tsm: VEDA-PC_SERVER1>REG NODE Veda-PC VEDA-PC DOM=TESTDOM USERID=NONE

ANR2060I Node VEDA-PC registered in policy domain TESTDOM.

NOTE: IF WE DON'T GIVE USERID=NONE PARAMETER WHILE REGISTERING THE NODE, THEN THE NODE

CAN ACTA AS TSM ADMINISTARTOR ID AND BY UISNG THIS NODENAME AND NODE PASSWORD, WE

CAN LOGIN TO THE TSM SERVER

BEFORE CLIENT COMMINICATES WITH TSM SERVER:

sm: VEDA-PC_SERVER1>Q N

Node Name Platform Policy Domain Days Since Days Since Locked?

Name Last Acce- Password

ss Set

------------------------- -------- -------------- ---------- ---------- -------

VEDA-PC (?) TESTDOM


33/104

------------------------- -------- -------------- ---------- ---------- -------

VEDA-PC WinNT TESTDOM which is used for client command line

dsm =====> for client GUI

dsm.opt =====> client configuration file

3)open the dsm.opt(client configuration file) file in BA client directory and add the following parameters

Commmethod TCPIP

Tcpport 1501

tcpserveraddress 127.0.0.1

nodename VEDA-PC

Passwordaccess generate

DOMAIN D: E:

4) Click on dsmc in BA client directory

Then it will ask for userid and password

Userid should be node name which is registered in TSM server and password should be node password,

which is given while registering the node

Note: if we don't give passwordaccess generate parameter in dsm.opt file, each time we login to the

client, it will prompt for userid and password


34/104

if we mention passwordaccess generate then password file will be generated and it stores in windows

registry, when we login to the client, it reads the password file from windows registry’s we don't need to

give userid and password each time we login to the client

5) Then tsm client prompt will come like this

tsm>

Then type i and hit enter button, then incremental backup starts

Tsm>i

TSM SERVER SIDE PROCEDURE:

To check the backup status, in TSM server give "q sess" command

6) to run the manual migration give the following command in TSM server console

tsm: VEDHATSM>migrate stg TESTSTG low=0

then migration process starts and data will be moved from disk stgpool to tape stgpool

to check the migration process use "q pr" command in TSM server console

7) To take the stgpool backup use the following command in TSM server

Backup stg tapestg copystg maxpr=2

To check stgpoolbackup process in TSM server use "q pr" command in TSM server

8)To take the TSM dbbackup use the following command

Backup db devc=fileclass t=full

To check TSM backup process in TSM server use "q pr" command in TSM server

To check the TSM DB backup status use the following command, whether it is completed or not.

q Db f=d or q volhist t=dbb

9) To check the current running processes in TSM server use

q Process command

10) To cancel the particular process in TSM server

Use "can process processnumber"

11)To check the backup session in TSM server use " q sess " command


35/104

12)TO Cancel backup for a particular node use the following command in TSM server

can sess sessionnumber

Restore procedure:

1: open TSM client GUI in BA client directory click DSM

Then TSM GUI will open, then click on restore option

Select view menu and select display active/inactive files

Select the file which needs restored in the left hand pane (option called local)

then click on restore option in the top left corner

Select the radio destination location

Click on select option and browse the destination location

Then click on restore tab

==============================================================

==============================================================

Configuring schedule backup:

Defining client schedule in TSM server

Def sched testdom testsched t=client action=i startd=today startt=20:19:00

Once defined the schedule, we need to add the node that schedule

Def assoc testdom testsched SRILAKSHMI-PC

In client side we need to configure the client scheduler service,

open the client GUI by clicking on DSM in BA client directory

Then select utilities menu and select setup wizard

Then select the check box "help me to configure TSM client scheduler"

Then select the check box, "install new scheduler"

Click on next and then give the TSM client scheduler service name


36/104

click on next and select the location of the dsm.opt file

the location of the opt file is by default

c:/programfiles/tivoli/tsm/baclient/dsm.opt

click on next and give the node name and node password which is registered in TSM server

click on next, then we have to mention the location of the

log files dsmsched.log and dsmerror.log

click on next button and click on finish

then scheduler service will be successfully installed and it will ask to start the TSM client scheduler

service

then select the radio button "YES"

then TSM scheduler service will start

Once scheduler service is configured in TSM client machine, we need to check the schedule status in

TSM server by using the following command

q eve * * n=nodename

Then schedule status may in the following format

Future ----which means the schedule backup will run in future

Pending===the schedule backup about to start

Started==== backup started

Missed --backup not started for the client, due to some issues

Failed === backup started but due some interruption, backup got failed.

=====================================================================================

=====================================================

TO check last 24 hours missed failed backups

q Eve * * begind=-1 endd=-0 ex=yes

Here one * represents policy domain name and another * represents schedules name

If don't give ex=yes, then it displays all missed and failed and completed backups

if we give ex=yes, then it displays only missed and failed backups


37/104

As a TSM administrator we need to work on missed and failed backups.

Note: dsmsched.log and dsmerror.log are the client configuration files and these files contain the

reasons for the backup failures

when the schedule backup gets fail or missed, we need check the dsmsched.log and dsmerror.log to find

out the reason

=====================================================================================

==============================================================================

1)To check the schedules details for particular node

q Sched * n=nodename f=d

2) To check the available schedules in TSM server

q Sched * *

First * represents policy domain name

Second * represents schedule name

3) to check the nodes which are associated to particular schedule

q Assoc * *

First * represents policy domain name

Second * represents schedule name

=====================================================================================

================================================

Defining schedule to take selective backup

def sched domainname schedname t=client action=selective objects="Directory name" startd=date

startt=time

ex:

Def sched testdom seltivesched t=client action=selective objects="E:\WNA1000M_SW_v1.1.0.20\* -

su=yes" startd=date startt=time

=====================================================

Defining schedule to take image backup


38/104

Def sched domainname schedname t=client action=imagebackup objects="directory name" startd=date

startt=time

Example:

Def sched TESTDOM IMAGEBACKUP t=client action=imagebackup objects="E:" startd=date

startt=19:50:00

---------------------------------------------------

To check what are drives for particular backed by TSM server

In TSM server each drive can be treated as file space

q Fi nodename

=============================================

To check in which tapes the data stored for a particular node

q Nodedata nodename

==========================================================

One time schedule or immediate schedule

Def clinetaction nodename Dom=domainname action=selective objects="directory"

Def clinetaction SRILAKSHMI-PC Dom=TESTDOM action= i

One time schedule is used to run the backup from TSM server itself, when the backup missed or failed

This onetime schedule can be defined by using clinetaction

this schedule run for onetime only(it will not run daily)

==========================================================

To check the particular process details sin TSM server

q Actlog se='process: processnumber'

Ex:

q Actlog se='process: 3'

==


39/104

DRM(Disaster Recovery manager):

By using DRM concept we can perform the tape movement from onsite to offsite and offsite to onsite

Implementing DRM:

First we need to check drm status in TSM server by using the following command

q Drmstatus

1) We need set the location of the plan file by using the following command

SET DRMPLANPREFIX 'E:\PLANFILE\'

Note: Plan file contains all TSM server configuration information and this plan will v\be generated by

running "prepare" command in TSM server and this planfile will be stored in the directory E:\PLANFILE\

By using plan file we can recover the TSM server from the disaster.

2)we need to set the DRM primary storage pool name(the primary storage pools, which are defined in

TSM server)

SET DRMPRIMSTGPOOL TAPESTG

3)we need to set the DRM copy storage pool name(the copy storage pools, which are defined in TSM

server)

SET DRMCOPYSTGPOOL COPYSTG

4) We need set database expiration days(this parameter specified the maximum no of db backup copiesthe TSM can maintain in offsite location)

SET DRMDBBACKUPEXPIREDAYS 5

5) we need to set drm plan file expiration

This parameter specifies the maximum no of plan files copies the TSM server can maintain

SET DRMRPFEXPIREDAYS 5

===========================================================

Tape movement from Onsite=====> offsite

1) We need to identify the copy tapes and TSM db backup tapes which needs to be sent to offsite

location by using the following command

q Drm * wherestate=mountable (Mo)


40/104

2) Once we identified the copy tapes and TSM DB backup tape by using the above command, we need to

make a note of copy tapes and DB backup , after that we need to eject the tapes from the tape library by

using the following command

Move drm * wherestate=mo tostate=valut

then tapes will be ejected from the tape library and those tapes will be available in Library I/O station

then we need to inform onsite media team to collect the tapes from library i/o station, then onsite

media will collect the tapes from the library 1/o and hand over the tapes to courier, then courier will

collect the tapes and store the tapes in offsite location

===================================================

Tape movement from offsite to Onsite

1) First we need to list out the tapes which are eligible for recall from offsite after offsite reclamation is

completed (empty tapes)

q Drm * wherestate=vailuretreive

Once we listed out the tapes which are in vaultretreive state(empty tapes), then we need to ask media

team to bring the tapes from offsite location, then media team will ask the courier to bring the tapes

from offsite

2) Once we asked the media team to bring the tapes from offsite, then we need to change the status of

those volumes from vaultretreive to courierretreive by using the following command

Move drm * wherestate=vaultre tostate=courierretreive

3) Once courier brings the tapes from offsite to onsite, then media team will inform us stating that tapes

have been arrived from offsite to onsite then we need to ask media team to load the tapes into library

I/O station

Once the media team loaded the tapes into library I/O station, then we need to change the status of

those volumes from courierretreive to onsiteretreive

Move drm * wherestate=courierre tostate=onsitere

4) After that we need to load the tapes as scratch (empty) into the tape library

Tape Library configuration:

1) First we need to zone the tape library and tape drives to the TSM server operating system this can be

done by storage team

2) Once zoning done by storage team, we need to install library drivers (media changer drivers) and tape

drive drivers (LTO drivers) in TSM server operating system level


41/104

3) Once drivers are installed, we need to check tape library and tape drives in TSM server operating

system level

Right click on my computer====> click on manage==click on device manager===> then tape library and

tape drives are visible in right hand pane

4) Next we need to define the tape library in TSM server level (TSM server console)

Def library libraryname

As we are using IBM tape libraries, library models will be in the following format

IBM3583, IBM3584, TS3310.TS3100

EX: DEF LIBRARY IBM3584

ONCE WE DEFINED THE TAPE LIBRARY, WE NEED TO DEFINE LIBRARY PATH IN TSM SERVER

SYNTAX TO DEFINE LIBRARY PATH:

DEFINE PATH SOURCENAME DESTINATIONNAME SOURCETYPE=SERVER DESTINATIONTYPE=LIBRARY

DEVICE=DEVICENAME ONLINE=YES

SOURCENAME=TSM SERVERNAME

DESTINATIONNAME=LIBRARYNAME

SOURCETYPE=SERVER

DESTINATIONTYPE=LIBRARY

DEVICE=DEVICENAME

FOR WINDOWS MACHINES LIBARY DEVICES NAMES CAN BE IDENTIFIED IN DEVICE INFORMATIOM

CLICK ON MANAGEMENT CONSOLE==>SELECT TSM SERVER1==>CLICK ON DEVICE INFORMATION

FOR WINDOWS MACHINES LIBRRAY DEVICE NAMES CAN BE IN THE FOLLOWING FORMAT

LB3.0.0.1 OR LB3.1.0.0 (DEPENDS ON LIBRARY DRIVER VERSION)

ONCE LIBRRAY DEVICE NAME IS IDENFIED IN DEVICE INFORMATION, THEN WE NEED TO DEFINE LIBRARYPATH

DEF PATH VEDATSM IBM3584 SOURCETYPE=SERVER DESTINATIONT=LIBRARY DEVICE=LB3.0.1.0

ONLINE=YES

NOW TAPE LIBRAY DETECTS BY TSM SERVER


42/104

ONCE WE DEFINED THE LIBRARY AND LIBRARY PATH, THEN WE NEED TO DEFINE TAPE DRIVES AND

DRIVES PATHS IN TSM SERVER

SYNTAX TO DEFINE TAPE DRIVE IN TSM SERVER:

DEF DRIVE LIBRARYNAME DRIVENAME 0NLINE=YES

FOR EXAMPLE IF WE HAVE 5 DRIVES IN TAPE LIBRARY THEN WE NEED DEFINE 5 DRIVS IN TSM SERVER

DEF DRIVE IBM3584 DRIVE1 ONLINE=YES

ONCE WE DEFINED THE TAPE DRIVE, THEN WE NEED TO DEFINE DRIVE PATH IN TSM SERVER

SYNTAX TO DEFINE DRIVE PATH:

DEF PATH SOURCENAME DESTINATIONNAME SOURCET=SERVER DESTINATIONT=DRIVE

LIBRARY=LIBRARYNAME DEVICE=DEVICENAME ONLINE=YES

EX:

DEF PATH VEDATSM DRIVE1 SOURCET=SERVER DESTINATIONT=DRIVE LIBRARY=IBM3584

DEVICE=MT3.1.0.0 ONLINE=YES

FOR WINDOWS MACHINES TAPE DRIVES DEVICE NAMES CAN BE IN THE FOLLOWING FORMAT

MT3.0.1.0, MT3.1.0.0

THIS CAN BE CHECKED IN DEVICE INFORMATION

CLICK ON MANAGEMENT CONSOLE==>SELECT TSM SERVER1==>CLICK ON DEVICE INFORMATION

NOTE:

TO CHECK THE TAPE DRIVES, WHEN THE TSMSERVER IS installed IN LINUX OR AIX

lsdev -Cc Tape

TO CHECK THE TAPE DRIVE DEVICE NAME WHEN THE TSMSERVER IS installed IN LINUX OR AIX

lscfg -vl rmt*

TO check the library device names, WHEN THE TSMSERVER IS installed IN LINUX OR AIX

lscfg -vl smc*

IN Linux and aix tape library device names can be in the following format

/dev/smc0 or /dev/smc1

IN Linux and aix tape drive device name should be in the following format


43/104

/dev/rmt0. /dev/rmt1

=====================================================================================

==========

Tape checkin process:

BY using tape checkin we can load the tapes into the tape library

Command

Checkin libvol libraryname search=bulk/yes/no status=scratch/private

ex:

Search=bulk

if we run the checkin command with search=bulk parameters, then TSM will search all the I/O stations

of the Tape library and it loads all the tapes which are available in the I/O stations

chekcin libvol IBM3584 search=bulk status=scratch

serach=yes:

if we run the checkin command with search=yes parameter then TSM searches for the tapes with in the

tape library which are not identified by the TSM server database(q libvol library name volumename or q

libvol * volumename (command gives no matching found output))

Checkin libvol IBM3584 SERACH=YES VOLUMELIST=VOLUME1, VOLUME2,VOLUME3.......

STATUS=SCRATCH

SERACH=NO;

IF WE RUN THE CHECKIN COMMAND WITH SEARCH=NO PARAMETER, ONLY PARTICULAR VOLUME

(NAMED VOLUME) CAN BE CHECKEDIN INTO THE TAPE LIBRARY FROM LIBRRAY I/O STATION

CHECKIN LIBVOL IBM3584 VOLUMENAME SEARCH=NO STATUS=SCRATCH

BY DEFAULT SEARCH=NO IN CHECKIN COMMAND

==========================================================

TAPE EJECT OR TAPE CHECKOUT PROCESS:

BY USING CHECKOUT COMMAND WE CAN EJECT THE TAPES FROM THE TAPE LIBRARY TO LIBRARY I/O

STATION


44/104

CHECKOUT LIBVOL LIBRARYNAME VOLUMENAME REMOVE=BULK/YES/NO

REMOVE=BULK:

IF WE RUN THE CHECKOUT COMMAND WITH REMOVE=BULK PARAMETER THEN TSM WILL DIRECTLY

EJECT THE TAPE FROM THE TAPE LIBARRAY TO LIBRARY I/O STATION

CHECKOUT LIBVOL LIBRARYNAME VOLUMENAME REMOVE=BULK

REMOVE=YES:

IF WE RUN THE CHECKOUT COMMAND WITH REMOVE=YES PARAMETER, THEN TSM WILL START TAPE

EJECT PROCESS AND IT WIL ASK FOR USER CONFIRMATION TO EJECT THE TAPE

CHECKOUT LIBVOL LIBRARYNAME VOLUMENAME REOVE=YES

THEN USER NEEDS TO GIVE CONFIRMATION BY USING THE FOLLWING PROCESS

Q REQUET

001 REQUEST OUTSTANDING

REPLY 001==== TO GIVE CONFIRMATION

COMMAND ACCEPTED

Q PROCESS

2 PROCESS NUMBER

Q ACT SE="PROCESS: 2"

======================================================

REMOVE=NO:

IF WE RUN THE CHECKOUT COMMAND WITH REMOVE=NO PARAMETER, THEN TSM WILL REMOVE THE

TAPE FROM THE TSM DATABASE INVENTORY AND IT MOVES THE TAPE FROM STORAGESLOT TO ANY

EMPTY STORAGE SLOT OF THE TAPE LIBRARY(NOT THE LIBRARY I/O STATION)

CHECKOUT LIBVOL LIBRARYNAME VOLUMENAME REMOVE=NO

===============================================

LABELING A NEW TAPE:

WHENEVER WE LOAD THE NEW TAPES (FIRST TIME LOADING THE TAPES INTO THE TAPE LIBRARY) INTO

THE TAPE LIBRRAY, WE MUST LABLE THOSE TAPES AND THEN WE NEED TO LOAD THOSE TAPES AS

SCRATCH TAPES INTO THE TAPE LIBRRAY


45/104

LABLE LIBVOL LIBRAYNAME SEARCH=BULK CHECKIN=SCRATCH LABLESOURCE=BARCODE

IF WE FORGOT TO LABLE THE NEW TAPES (IF WE DIRECTLY USE CHECKIN COMMAND), THYEN THOSE

TAPES WILL BE LOADED AS PRIVATE TAPES INTO THE TAPE LIBRRAY

TO CHECK THE VOLUMES AVAILABLE WITH IN THETAPE LIBRARY OR NOT, USE THEFOLLWING

COMMAND IN TSMSERVER CONSOLE

Q LIBVOL * VOLUMENAME OR Q LIBVOL LIBRRAYNAME VOLUMENAME

=====================================================================================

========

SERVER TO SERVER COMMUNICATION:

BY USING SERVER TO SERVER COMMUNICATION, WE CAN ESTABLISH THE COMMUNICATION BETWEEN

TSM SERVERS

TO IMPLIMENT THE SREVER TO SERVER COMMUNICATION, WE NEED TO DEFINE SOURCE TSM SERVER

AS A SERVER IN TARGET TSM SERVER AND TARGET TSM SERVER AS A SERVER IN SOURCE TSM SERVER

SYNTAX TO DEFINE SERVER:

DEF SERVER SERVERNAME SERVERPASS HLAADDRESS=IPADDRESSOFTSM SREVER

LLAADDRESS=PORTNUMBEROF TSM SERVER COMMMETHOD=TCPIP

FOR EXAMPLE WE HAVE TWO TSM SERVERS VEDATSM1 AND VEDATSM2

TO IMPLEMENT THE COMMUNICATION BETWEEN THESE TWO TSM SERVERS

FIRST WE NEED TO DEINE VEDATSM1 AS A SERVER IN VEDATSM2 TSM SERVER BY USING THE

FOLLOWING COMMAND

VEDATSM2 :> DEF SERVER VEDTASM1 ADSM HLAADDRESS=IPADDRESSOF VEDATSM1

LLAADDRESS=PORTNOF VEDATSM1 COMMMETHOD=TCPIP

NOTE: TSM SERVER IPADDRESS AND PORT NUMBER CAN BE CHECKED BY USING "Q STATUS"

COMMAND IN TSM SERVER.

SECOND WE NEED TO DEFINE VEDATSM2 AS A SERVER IN VEDATSM1 SERVER

VEDATSM1 :> DEF SERVER VEDATSM2 ADSM HLAADDRESS=IPADDRESSOF VEDATSM2

LLAADDRESS=PORTNOFVEDATSM2 COMMMETHOD=TCPIP

ONCE WE DEFINED BOTH THE SERVERS, THEN WE NEED TO ENABLE CROSSDEFINE PARAMETER IN BOTH

THE TSM SERVER BY USING THE FOLLOWING COMMAND

SET CROSSDEFINE YES


46/104

CROSSDEFINE PARAMETER CAN BE IDENTIFIED BY USING "Q STATUS" COMMAND

BY UISNG SREVER TO SREVER COMMUNICATION WE CAN IMPORT/EXPORT THE NODE DATA, SCHEDULE

INFORMATION, POLICY INFORMATION FROM ONE TSM SERVER TO ANOTHER TSM SERVER

FOR EXAMPLE WE HAVE TWO NODES A,B AND A NODE BACKED BY VEDATSM1 SERVER AND B NODE

BACKED BY VEDATSM2

IF WE WANT TO EXPORT NODE "A" DATA FROM VEDATSM1 TO VEDATSM2 TSM SERVER USE THE

FOLLOWING PROCEDURE

SYNTAX;

EXPORT NODE NODENAME FILEDATA=ALL FROMSERVER=SOURCETSMSERVERNAME

TOSERVER=TARGETTSMSERVERNAME

EX:

EXPORT NODE A FILEDATA=ALL FROMSERVER=VEDATSM1 TOSERVER=VEDATSM2

SHARED LIBRARY CONCEPT:

BY USING SHARED LIBRARY CONCEPT SINGLE TAPE LIBRARY CAN BE SHARED AMONG MULTIPLE TSM

SERVERS

IN SHARED LIBRARY CONCEPT ONE TSM SERVER ACTS AS A LIBRARY MANAGER AND REST OF THE TSM

SERVERS ACTS AS LIBRARY CLIENTS

IN THE TSM SERVER WHICH IS ACTING AS A LIBRARY MANAGER, IN THAT TSM SERVER WE NEED TO

DEFINE THE TAPE LIBRRAY WITH SHARED=YES PARAMETER

DEF LIBRARY IBM3584 SHARED=YES

NEXT WE NEED TO DEFINE THE TAPE DRIVES AND DRIVE PATHS IN LIBRARY MANAGER TSM SERVER.

THE OTHER TSM SERVERS WHICH ARE ACTING AS A LIBRRAY CLINETS, IN THOSE TSM SERVERS WE NEED

TO DEFINE THE TAPE LIBRARY WITH THE FOLLOWING COMMAND

DEF LIBRARY IBM3584 SHARED=NO PRIMARYLIBRARYMANAGER=LIBRARY MANAGERTSM SERVER NAME

FOR EXAMPLE WE HAVE THREE TSM SERVER TSM1 AND TSM2, TSM2 AND WE HAVE 15 TAPE DRIVES IN

THE TAPE LIBRARY,IF WE WANT TO SHARE THIS TAPE LIBRARY AMONG THESE THREE TSM SERVERS

1) WE ARE CHOOSING TSM1 AS LIBRARY LIBRRAY MANAGER,THEN IN TSM1 SERVER WE NEED TO

DEFINE THE TAPE LIBRARY WITH THE FOLLOWING COMMAND


47/104

TSM1>DEF LIBRARY IBM3584 SHARED=YES

ONCE WE DEFINED THE TAPE LIBRARY IN LIMBRARY MANAGER, THEN WE NEED TO DEFINE LIBRARY

PATH IN LIBRARY MANAGER TSM SERVER

DEF PATH SOURCENAME DESTINATIONNAME SOURCCET=SERVER DESTT=LIBRAARY


HERE SOURCE NAME AS LIBRARY MANAGER TSM SERVER NAME AND DESTINATION NAME AS LIBRARY

NAME

2) WE NEED TO DEFINE THE TAPE DRIVES IN TSM1 SERVER


;

:

:


3) ONCE WE DEFINED THE TAPE DRIVES, THEN WE NEED DEFINE PATH TO THE TAPE DRIVES

DEF PATH TSM1 DRIVE1 SOURCET=SERVER DESTT=DRIVE LIBRARY=IBM3584 DEVICE=DEVICENAME

ONLINE=YES

:

:

:

DEF PATH TSM1 DRIVE15 SOURCET=SERVER DESTT=DRIVE LIBRARY=IBM3584 DEVICE=DEVICENAME

ONLINE=YES

4) NEXT WE NEED TO DEFINE DRIVE PATHS FROM TSM2 AND TSM3 SERVERS TO TAPE DRIVES FROM

TSM1 SERVER

DEFING DRIVE PATH FROM TSM2 TO TAPE DRIVES IN TSM1 SERVER

TSM1>DEF PATH TSM2 DRIVE1 SOURCET=SERVER DESTT=DRIVE LIBRARY=IBM3584



48/104

:

:



DEFINING DRIVE PATH FROM TSM3 TO TAPE DRIVES IN TSM1 SERVER



:

:



5) ONCE WE DEFINED THE TAPE DRIVES AND DRIVE PATHS, WE NEED TO DEFINE TAPE LIBRARY IN THE

TSM SERVERS TSM2 AND TSM3 WHICH ARE ACTING AS A LIBRARY CLIENTS WITH FOLLOWING

COMMAND

TSM2>DEF LIBRARY IBM3584 PRIMARYLIBRARYMANAGER=TSM1

TSM3>DEF LIBRARY IBM3584 PRIMARYLIBRARYMANAGER=TSM1

NOTE: IF WE WANT TO IMPLIMENT THE SHARED LIBRARY CONCEPT, WE MUST HAVE SERVER TO SERVER

COMMUNICATION.

IN SHARED LIBRRAY CONCEPT TAPE CHECKIN CAN BE DONE FROM LIBRARY MANAGER TSM SERVER

ONLY

IF WE WANT TO EJECT THE TAPES, WE CAN PERFORM FROM ANY OF THE TSM SERVER

==============================================================

SERVER GROUP:

By using server group, we can perform command routing between TSM SERVERS

TO IMPLIMENT THE SERVER GROUP, WE NEED TO DEFINE SERVER GROUP IN TSM SERVER


49/104

SYNTAX:

DEF SERVERGROUP GROUPNAME

EX: DEF SERVERGROUP TSM

ONCE WE DEFINED THE SERVER GROPUP, THEN WE NEED TO ADD TSM SERVERS AS MEMBERS IN THAT

SERVER GROUP

SYNTAX:

DEF GROUPMEMBER SERVERGROUPNAME MEMBER1.MEMBER2, MEMBER3...

EX:

DEF GROUPMEMBER TSM TSM1, TSM2, TSM3

HERE MEMBER1.MEBER2, MEMBER3 ARE THE TSM SERVERS NAMES WHICH ARE PART OF A SERVER

GROUP

WE NEED DEFINE THE SAME SERVER GROUP AND GROUP MEMBERS IN ALL THE TSM SERVERS

TSM1,TSM2,TSM3 WITH THE SAME PROCEDURE

ONCE WE IMPLIMENTED THE SERVER GROUP, IF WE WANT TO KNOW WHAT ARE THE PROCESSES

RUNNING ON ALL THE THREE TSM SERVERS TSM1,TSM2,TSM3, THEN WE CAN CHECK FROM EITHER

TSM1 OR TSM2 OR TSM3

IF WE WANT TO CHECK FROM TSM1 SREVER USE THE FOLLOWING COMMAND

TSM1>SREVERGROPUNAME:Q PR

EX:

TSM1>TSM:Q PR

TSM1>TSM:Q DB

TO CHECK WHETHER THE SERVER GROUP IS IMPLEMENTED IN TSM SERVER OR NOT, USE THE

FOLLOWING COMMAND

Q SERVERGROUP

=============================================================================

COLLOCATION:

BY USING COLLOCATION, WE CAN SEND PARTICULAR NODE DATA OR GROUP OF NODES DATA TO

MINIMUM NUMBER OF TAPES


50/104

WE HAVE THREE TYPES OF COLLOCATIONS IN TSM

1) COLLOCATION BY NODE

2) COLLOCATION BY GROUP

3) COLLOCATION BY FILE SPACE

BY DEFAULT COLLOCATION IS BY GROUP

TO IMPLEMENT THE COLLOCATION BY GROUP, FIRST WE NEED TO DEFINE COLLOCATION GROUP IN TSM

SERVER WITH THE FOLLWOING COMMAND

SYNTAX:

DEF COLLOCGROUP GROUPNAME

EX:

DEF COLLOCGROUP WINGROUP

ONCE WE DEFINED THE COLLOCATION GROUP, THEN WE NEED TO ADD THE NODES WHICH ARE PART

OF COLLOCATION AS MEMBERS IN THAT COLLOCATION GROUP

SYNTAX: DEF COLLOCMEMBER COLLOCGROUPNAME MEMB1, MEMB2....

EX: DEF COLLOCMEMBER WINGROUP NODE1, NODE2, NODE3, NODE4, NODE5

ONCE WE ADDED THE NODES AS MEMBERS IN THE COLLOCATION GROUP, THEN WE NEED TO CHECK

THE TAPE STORGAEPOOL WITH

Q STG TAPESTG F=D

THEN IT DISPLAYS ONE PARAMETER "COLLOCATION: GROUP"

NEXT WE NEED TO CHECK THE NODES DEFINTIONS WHICH ARE PART OF COLLOCATION GROUP AND WE

NEED TO UPDATE THOSE NODES WITH THE FOLLOWING COMMAND

UPD NODE NODENAME GROUPNAME=COLLOCATIONGROUPNAME

EX: UPD NODE NODE1 GROUPNAME=WINGROUP

UPD NODE NODE2 GROUPNAME=WINGROUP

THE ADVATAGE OF COLLOCATION IS RESTORE PERFORMANCE WILL BE VERY FASTER BECAUSE LESS

NUMBER OF TAPE MOUNTS REQUIRED WHILE RESTORING THE DATA,

THE DISADAVNTAGE IS WE NEED MORE SCRATCH TAPES IN THE TAPE LIBRARY, BECAUSE TSM TRIES TO

SEPERATE EACH FILE OR OBJECT OF A NODE INTO SEPEARTE TAPE


51/104

MIGRATION PERFORMANCE WILL BE VERY SLOW

TO CHECK THE COLLOCATION IN TSM USE THE FOLLOWING COMMAND

Q COLLOCGROUP

INCLUDE/EXCLUDE STATEMENTS:

BY USING INCLUDE/EXCLUDE STATEMENTS WE CAN INCLUDE OR EXCLUDE THE FILES FROM THE BACKUP

EXCLUDING A FILE FROM Backup;

EXCLUDE "*:\...\FILENAME"

IF WE WANT TO EXCLUDE THE FILES WHICH ARE SUFFIXED WITH

.TMP FROM THE BACKUP, THEN WE NEED TO ADD THE FOLLOWING

EXCLUDE STATEMENT IN CLIENT CONFIGURATION FILE DSM.OPT

EXCLUDE "*:\...\*.TMP"

HERE * REPRESENTS ALL THE DRIVES IN THE CLIENT MACHINE

EXCLUDING A DIRECTORY FROM BACKUP:

SYNTAX:

EXCLUDE.DIR “DIRECTORY PATH"

EXCLUDE.DIR '"c:\PROGRAM FILES\ "'

=====================================================

CLIENTOPTIONSET (CLOPTSET):

BY USING CLIENT OPTION SET (CLOPTSET), WE CAN EXCLUDE THE COMMON FILES FROM BACKUP FROM

TSM SERVER ITSELF. FOR THIS WE NEED TO DEFINE CLOPTSET IN TSM SERVER

SYNTAX:

DEF CLOPTSET OPTIONSETNAME

EX; DEF CLOPTSET WINDOWS

ONCE WE DEFINED CLOPTSET, WE NEED TO DEFINE CLIENT OPTION IN THE CLOPTSET WITH FOLLOWING

COMMAND

DEF CLIENTOPTION OPTIONSETNAME OPTIONNAME OPTIONVALUE


52/104

EX: DEF CLIENTOPTION WINDOWS INCLEXCL "EXCLUDE "*:/.../.../*.TMP""

(HERE WINDOWS IS THE CLOPTSETNAME AND INCLEXCL IS THE OPTIONNAME)

ONCE WE DEFINED THE CLIENTOPTION IN THE OPTIONSET, THEN WE NEED TO UPDATE THE NODE

DEFINTION WITH THE FOLLOWING COMMAND

UPD NODE NODENAME CLOPTSET=OPTIONSETNAME

UPD NODE RAJU CLOPTSET=WINDOWS

Q CLOPTSET

=============================================

TSM CLIENT CONFIGURATION FILES:

DSM.OPT

DSMSCHED.LOG===>IT CONTAINS SCHEDULE INFORMATION

DSMEROR.LOG==>IT CONTAINS ERRORS RELATED TO BACKUP FAILURES

WHEN THE NODE BACKUP FAILS,WE NEED TO CHECK DSMERROR.LOG AND DSMSCHED.LOG FILE WHICH

IS IN BA CLIENT DIRECTORY

TSM SERVER CONFIGURATION FILES

DSMSERV.DSK

THIS FILE CONTAINS TSM DATABASE AND RECOVERY LOG VOLUME INFORMATION

DSMSERV.OPT:

THIS FILE CONTAINS ALL CONFIGURATION FILES OF THE TSM SERVER (SAME AS "Q OPT" OUTPUT)

DEVCONFIG.OUT

THIS FILE CONTAINS ALL DEVICE CLASS RELATED INFORMATION. WHICH ARE DEFINED IN THE TSM

SERVER

VOLHIST.OUT:

THIS FILE CONTAINS SEQUENTIAL ACCESS VOLUMES INFORMATION (Q VOLHISTORY)

(THE VOLUMES WHICH ARE CRETAED USING FILE DEVICE CLASS AND TAPE INFORMATION, IF THE TAPE

LIBRRAY IS AVAILABLE)

RESTORE VOLUME:


53/104

BY USING RESTORE VOLUME, WE CAN RESTORE THE PRIMARY TAPE DATA FROM COPY TAPES, IF THE

PRIMARY TAPE IS DAMAGED

SYSTAX TO RESTORE THE VOLUMES IS

RESTORE VOLUME VOLUMENAME PREVIEW=YES

EX:

RESTORE VOLUME TAPE1 PREVIEW=YES (HERE TAPE1 IS DAMAGED)

OUTPUT: XYZ PROCESS STARTED

THEN IT WILL LISI OUT THE COPY TAPES IN WHICH THE PRIMARY TAPE DATA IS RESTORED

THIS COPY TAPES CAN IDENTIFIED IN TSM SERVER ACTIVITY LOG(ACTLOG) BY USING THE PROCESS

NUMBER

Q ACT SE="PROCESS: XYZ" (XYZ IS THE RESTORE VOLUME PROCESS)

ONCE WE IDNTIFIED THE COPY VOLUMES, WE NEED TO BRING THOSE COPY VOLUMES FROM OFFSITE

AND WE NEED TO LOAD THOSE COPY TAPES AS PRIVATE TAPES INTO THE TAPE LIBRARY

ONCE THE COPY TAPES ARE LOADED INTO THE TAPE LIBRRAY, WE NEED TO CHANGE THE ACCESS OF

THOSE VOLUMES TO READONLY

THEN WE NEED TO RESTORE THE PRIMARYTAPE DATA FROM COPY TAPES BY USING FOLLOWING

COMMAND

RESTORE VOLUME VOLUMENAME

(HERE VOLUME NAME IS PRIMARY TAPE NAME WHICH IS DAMAGED)

THEN DAMAGED TAPE DATA WILL RESTORED INTO ANOTHER NEW TAPE

ONCE THE PRIMRAYTAPE DATA IS RESTORED FROM COPY TAPES, THEN WE NEED TO UPDATE THE

ACCESS OF THE DAMAGED PRIMARY TAPE TO DESTROYED

UPD VOLUME VOLUMENAME ACCESS=DESTROYED

AFTER THAT WE NEED TO EJECT THE COPY TAPES FROM THE TAPE LIBRARY AND SEND THOSE TAPES

OFFSITE

============================================================

AUDIT VOLUME:

IF THERE ANY READ OR WRITE ERRORS OOCURED IN A VOLUME IN THAT CASE WE NEED TO GO FOR

AUDIT VOLUME BY USING THE FOLLOWING COMMAND


54/104

AUDIT VOLUME VOLUMENAME FIX=NO/YES

BY DEFAULT FIX=NO

FIX=NO:

IF WE RUN THE AUDIT VOLUME WITH FIX=NO PARAMATER THEN TSM WILL MARK THOSE CORRUPTED

FILES AS DAMAGED IN TSM SERVER DATABASE

AUDIT VOLUME VOLUMENAME FIX=NO

FIX=YES:

IF WE RUN THE AUDIT VOLUME WITH FIX=YES, THEN TSM WILL DLETE THE CORRUPTED FILES FROM

TSM SERVER DATA BASE

AUDIT VOLUME VOLUMENAME FIX=YES

USUALLY WE RUN THE AUDIT VOLUME WITH FIX=NO PARAMETER

IF THERE ARE ONE OR TWO READ/WRITE ERRORS IN A VOLUME, IN THAT CASE WE NEED TO FOR AUDIT

VOLUME

IF THERE ARE MORE THAN 3 ERRORS, IN THAT SITUATION WE NEED TO GO FOR RESTORE VOLUME

IF WE WANT TO CHECK THE READ AND WRITE ERRORS IN A PARTICULAR VOLUME THEN WE NEED USE

"Q VOLUME VOLUMENAME F=D"

====================================================

AUDIT LIBRARY:

IF THERE IS ANY MISMATCHING BETWEEN TSM DATABASE INVENTORY AND LIBRARY INVENTORY, IN

THAT CASE WE NEED TO GO FOR AUDIT LIBRARY

SOME TIME TAPES PHYSICALLY SHOWS WITH IN THE TAPE LIBRARY, BUT NOT IDENTIFIED BY THE TSM

SERVER DATABASE OR TAPES PHYSICALLY NOT IN THE TAPE LIBRARY, BUT SHOWS IN THE TSM SERVER

DATABASE

TO RUN THE AUDIT LIBRARY COMMAND

AUDIT LIBRARY LIBRARYNAME CHECKLABLE=BARCODE

TDP SQL (TIVOLI DATA PROTECTION FOR SQL):

BY USING TDPSQL WE CAN TAKE THE BACKUP OF SQL SERVER DATABASES

1: FULL BACKUP


55/104

2: DIFFERENTIAL

3: LOG BACKUP

FULL: IT TAKES FULL BACKUP OF THE SQL DATABASES

2) DIFFERENTIAL: BY USING DIFFRENTIAL BACKUP WE CAN TAKE WHAT EVER CHANGES HAPPEN TO THE

SQL DATABASE SINCE THE LAST FULL BACKUP AND IT TAKES BACKUP OF THOSE CHANGES UNTIL NEXT

FULL BACKUP RUNS

3) LOG BACKUP: BY USING LOG BACKUP, WE CAN TAKE BACKUP OF THE SQLSERVER TRANSACTION LOGS

WHICH ARE GENERATED DURING INSERTION AND UPDATION OF THE TABLES IN THE SQL SERVER

DATABASES

THESE LOGS STORE IN LOCAL DRIVE OF THE MACHINE, WHERE THE SQL SERVER IS INSTALLED

ONCE THE LOG BACKUP IS COMPLETED, THOSE LOGS WILL BE PURGED (REMOVE) FROM THE DISK

TSM SERVER CIONFIGURATION PART:

IN TSM SERVER WE NEED TO REGISTER SEPERATE NODES, ONE NODE FOR FILE SYSTEM BACKUP AND

ANOTHER NODE FOR SQL DATABASE BACKUPS

REG NODE NODENAME NODEPASS DOM=DOMAINNAME USERID=NONE

FS NODE:

REG NODE VEDA VEDA DOM=FSDOMAIN USERID=NONE

SQL NODE:

REG NODE VEDA_SQL VEDA_SQL DOM=SQLDOM USERID=NONE BACKUPDELETE=YES ARCHDELETE=YES

(IF WE DO NOT ENABLE. BACKDEL AND ARCHDEL PARAMETERS, EXPIRED SQL DATABSE BACKUPS WON'T

BE DELETED)

==========================================================

TSMN CLIENT SIDE CONFIGURATION:

IN CLIENT MACHINE WE NEED TO INSTALL BA CLIENT AND TDP SQL SOFTWARE

THE DEFAULT INSTALLATION DIRECTORY OF BA CLIENT IS

C:\PROGRAM FILES\TIVOLI\TSM\BACLINET

IN THE DSM.OPT FILE WE NEED TO MENTION THE NODE NAME AS VEDA WHICH IS REGISTERED FOR FILE

SYSTEM BACKUP


56/104

THE DEFAULT INSTALLATION DIRECTORY OF TDPSQL IS

C:\PROGRAM FILES\TIVOLI\TSM\TDPSQL

IN THE TDPSQL DIRECTORY WE CAN SEE THE FOLLOWING CONFIGURATION FILES

DSM.OPT

TDPSQLC.EXE (TDPSQL COMAND LINE)

TDPSQL.EXE (TDP SQL GUI)

SQLFULL.SMP

SQLDIIF.SMP

SQLLOG.SMP

IN THE DSM.OPT FILE WHICH IS IN TDPSQL DIRECTORY IN THAT OPT FILE WE NEED TO MENTION THE

NODE NAME AS SQL NODE VEDA_SQL, WHICH IS REGISTERED IN TSM SERVER FOR SQL DABASE

BACKUPS

ONCE OPT FILES ARE CONFIGURED FIRST WE NEED TO SET THE FS NODE PASSWORD BY USING DSMC IN

BACLIENT DIRECTORY AND WE NEED TO SET SQL NODE PASSWORD FROM TDPSQL DIRECTORY

GO TO THE TDPSQL DIRECTORY

C:\PROGRAM FILES\TIVOLI\TSM\TDPSQL THERE WE NEED TO GIVE THE FOLLWOING COMMAND

TDPSQLC CHANGETSMPASSWORD OLDPASSWORD NEWPASSWORD CONFIRMATIONPASSWORD

TDPSQLC CHANGETSMPASSWORD VEDA_SQL VEDA_SQL VEDA_SQL

ONCE SQL NODE PASSWORD IS SET THEN WE NEED TO CHECK THE COMMUNICATION BETWEEN SQL

NODE VEDA_SQL AND TSM SERVER BY USING THE FOLLWOING COMMAND

TDPSQLC QUERY TSM

THIS NEEDS TO BE GIVEN IN TDPSQL DIRECTORY

=====================================================

THERE ARE THREE TYPES OF BACKUPS IN IN TDPSQL:

1: FULL BACKUP

2: DIFFERENTIAL

3: LOG BACKUP


57/104

FULL:IT TAKES FULL BACKUP OF THE SQL DATABASES

COMMAND TO TAKE SQL FULL BACKUP IS

TDPSQLC BACKUP * FULL

THIS NEEDS TO BE RUN IN TDPSQL DIRECTORY

HERE * REPRESENTS ALL THE DATABASES WHICH ARE RESIDING IN THE SQL SERVER

IF WE WANT TO TAKE PARTICULAR DATABASE BACKUP WE NEED TO RUN THE FOLLOWING COMMAND

TDPSQLC BACKUP DATABASE1, DATABASE2..... FULL

2: DIFFRENTIAL BACKUP:

BY USING DIFFRENTIAL BACKUP WE CAN TAKE WHAT EVER CHANGES HAPPEN TO THE SQL DATABASE

SINCE THE LAST FULL BACKUP AND IT TAKES BACKUP OF THOSE CHANGES UNTIL NEXT FULL BACKUP

RUNS

TO TAKE THE MANUAL DIFFERENTIAL BACKUP

TDPSQLC BACKUP * DIFF

3: LOG BACKUP:

BY USING LOG BACKUP, WE CAN TAKE

Documents

TSM Material Veda