TSM FAQ'S

1) when recovery log gets full ? what are the reasons

 In TSM the data gets written to Recovery log before it gets commited to database , and so it happens that a situation comes in when the recovery log getts filled so a administrator should make sure the size of teh log and when the log reaches 70% the admin should take the database backup to avoid the server crash due to recovery log getting filled.

 2)what is recovery log pinning ?

 It happens many times that a backup session gets hanged , other session are not able to run and because of it the recovery log gets pinned which keeps on increasing the size of the log , so to aviod recovery log pinning we have to either change the schedule timing of the specific node which pins the recovery log or else heck back in your Activity Log for ANE session conclusion messages for that client, to see if it's performingB/A client work (rather than TDP) and check past session statistics for a sense of sizes, rates, and duration. This can reveal if what the client has been doing has been getting more outrageous over time, or whether the current session is anomalous. If the networking seems ploddingly slow from the stats, that can get fixed. It needs analysis. Talk to the client admin and see if they made recent changes, or are aware of unusual data activity.

 Check with recovery log pinning in this site

http://people.bu.edu/rbs/ADSM.QuickFacts

 3)what are the steps if recovery log gets full?

 First if the log is at 97% , we need to take a DATABASE backup immediately and if the server crashes due to recoery log getting filled then we have to recover it using the format the recovery log then extending it and then taking a db backup and then reduce the size of recovery log so that you are not poked by Operating system team

4)what are read and write errors in tapes?

use select statement to see the error

 5)what is log mode i.e roll forward and normal mode

 In case a server crashes

 Normal mode : The server can be recovered until the last DB BACKUP

 Roll forward mode : The server can be recovered to the most recent state when the server crashed but this mode occupies much of your log space .

 6)what is shchedmode prompted and polling?

 Prompted :If a client has selected the server-prompted mode, the client first contacts the server to notify the server that it is running and the client is able to receive new

 schedule notifications. The server responds to let the client know if it has

 schedules or not. The client then sleeps until the server contacts it. If the server detects that a new schedule is ready to run, it contacts the client and informs It  that the client must start a new operation. The client receives the schedule  definition and starts the operation.

 Polling :If a client has selected the client polling scheduling mode, the client contacts the  server to find out if there is a schedule defined for it and when it should be run.

 The client continues to contact the server at regular intervals set in the client’s  options file so that it can respond dynamically to any changes made to its

 schedules by the administrator. The administrator can also override this interval  by setting a server parameter.

 7)how to recover data from bad tapes?

 Its simple

 First you need to identify the tape which has high number of read and write or viceversa and then set it's access to unavailbel

 then from server command line we need to issue command

Restore vol volumename preview=yes (mention the bad volume name)

 check in act log the copy of the bad volume and get the volume loaded in the library and then issue the same command with preview=no

Restore vol volumename preview=no

 this will restore the volume then you can ask you tape operator to destroy the bad volume physically and from server end you can use use

Destroy volume badvolumename (this is done to update the database)

 what is tape life cycle? any document

 For this you will have to read the concepts book for a detailed explanation and its easy

 explain the states of a tape in library , i guess you go through IBM Tivoli Storage Management Concepts (page number 325 )