Explore topic-wise InterviewSolutions in .

Answer : q DB f=d q log f=d q EVENT * * t=c q stg f=d q event * t=a

1. MOUNTABLE to non-mountable
2. non-mountable to courier
3. courier to VAULT
4. vault to vault-RETRIEVE
5. vault-retrieve to courier-retrieve
6. courier-retrieve to onsite retrieve
7. CHECK in as private

AUDIT LIBRARY libname

Audit library libname

verexits=30
verdelete=30
retextra=30
retonly=30

verexits=30
verdelete=30
retextra=30
retonly=30

tdpsql.cfg & dsm.opt

tdpsql.cfg & dsm.opt

MAY be DRIVES not FREE, no SPACE in stgpool.

May be drives not free, no space in stgpool.

FULL,INCREMENTAL,SNAPSHOT.

full,incremental,snapshot.

Q volhist ty=dbb

q volhist ty=dbb

FILE,disk.dlt.lto....ETC.

file,disk.dlt.lto....etc.

Ba-client,STORAGE AGENT, SAN BOXES.

Ba-client,storage agent, san boxes.

in ver6.2 we have DEDUPLICATION OPTION.

in ver6.2 we have deduplication option.

by INCREASING the bufpoolsize

by increasing the bufpoolsize

1. PRIMARY stgpool---RANDOM stgpool ---SEQUENTIAL stgpool
2. COPY stgpool
3. ACTIVE stgpool

HOME DIRECTORY of all USERS. (Which are FREQUENTLY CHANGED?)

home directory of all users. (Which are frequently changed?)

will be SCHEDULED in CRONTAB.

will be scheduled in crontab.

DSMC BACKUP QUERY

dsmc backup query

SET SERVER PASSWORD *****

set server password *****

dsmserv.opt, dsmserv.dsk,volhist.out, devconfig.out

dsmserv.opt, dsmserv.dsk,volhist.out, devconfig.out

Q EVENT* *

q event* *

Q STATUS, q SYSTEM

q status, q system

dsmserv.opt, volhist.out, devconfig.out, dsmserv.dsk.

dsmserv.opt, volhist.out, devconfig.out, dsmserv.dsk.

DSMC i or dsmc SEL.

dsmc i or dsmc sel.

INACTIVE, which not LATEST BACKUP. ACTIVE which is latest backup.

Inactive, which not latest backup. Active which is latest backup.

backup is for short period storage and where as archive is for long TERM storing your DATA Backup is having VERSIONS archive does not have versions and backup is full, INCREMENTAL, differential where as archive is as it is snapshot.

backup is for short period storage and where as archive is for long term storing your data Backup is having versions archive does not have versions and backup is full, incremental, differential where as archive is as it is snapshot.

FULL, INCREMENTAL, DIFFERENTIAL.

Full, incremental, differential.

BACKGROUND PROCESS in TDP for HARDWARE. (TDP for ESS).

Background process in TDP for hardware. (TDP for ESS).

DISK STORAGE POOL, TAPE storage pool

Disk storage pool, Tape storage pool

IBM 3584

IBM 3584

No ANSWER.

No answer.

DISK POOL, TAPE pool.

Disk pool, Tape pool.

MOVE drmedia COMMAND is USED.

Move drmedia command is used.

DEVCONFIG.OUT, VOLHIST.OUT, DSMSERV.OPT AND DSMSERV.DSK

DEVCONFIG.OUT, VOLHIST.OUT, DSMSERV.OPT AND DSMSERV.DSK

MONITORING Schedules, DB and RECOVERY Log ETC. Already EXPLAINED.

Monitoring Schedules, DB and Recovery Log etc. Already explained.

Dsm.opt file is the CLIENT file which contains the tsmservername pointing to dsm.sys.

Dsm.sys normally USED in UNIX environment contains the server stanzas and the parameters like NODE name, management class and password ACCESS OPTIONS.

Dsm.opt file is the client file which contains the tsmservername pointing to dsm.sys.

Dsm.sys normally used in UNIX environment contains the server stanzas and the parameters like node name, management class and password access options.

Storing the TRANSACTION, which is not committed to DB and are, REQUIRED for CONSISTENCY of TSM DB.

Storing the transaction, which is not committed to DB and are, required for consistency of TSM DB.

LABELING is NAMING vol. check in is INSERTING the vol to SLOT.

Labeling is naming vol. check in is inserting the vol to slot.

LABEL libvol VOLUME NAME.

label libvol volume name.

PREPARING VOLUMES. LABELING. CHECK in, check out ETC.

Preparing volumes. Labeling. Check in, check out etc.

Check SCHEDULE, DB & RECOVERY log, managing volumes. EXPLAINED EARLIER.

Check Schedule, DB & Recovery log, managing volumes. Explained earlier.

IBM 3584

IBM 3584

TRANSFERRING DATA from DISK to TAPE POOL.

Transferring data from disk to tape pool.

STORING data of a client at MINIMAL VOLUMES. This will help in faster RESTORES as less media mounts will be required during restore.

Storing data of a client at minimal volumes. This will help in faster restores as less media mounts will be required during restore.

It is the process of MOVING the FRAGMENT data from one or more volumes to a different volume, so that the volumes being reclaimed can be used as SCRATCH volumes in TSM again. By using this technique we can save a lot of space in TSM. This process is controlled by RECLAIM threshold PARAMETER of the storage pool.

It is the process of moving the fragment data from one or more volumes to a different volume, so that the volumes being reclaimed can be used as scratch volumes in TSM again. By using this technique we can save a lot of space in TSM. This process is controlled by reclaim threshold parameter of the storage pool.

LIBRARY IBM 3584, 3582 ETC.

Library IBM 3584, 3582 etc.

EXPLAIN the DISK POOL and TAPE POOLS.

Explain the Disk Pool and Tape Pools.

20 GB in TSM 5.3

20 GB in TSM 5.3

Add DATABASE volumes by the command LINE as TSM server will not work if DB is FULL.

Add database volumes by the command line as TSM server will not work if DB is full.

Check DB & RECOVERY log, VOLUME management etc. explained earlier.

Check DB & recovery log, Volume management etc. explained earlier.

First establish server to server communication in the both the SERVERS and REG local NODE as server in in remote and then in local def server. Moving DATA through vaulting.

First establish server to server communication in the both the servers and reg local node as server in in remote and then in local def server. Moving data through vaulting.

If CROSS DEF is on we can ESTABLISH SERVER to server COMMUNICATION.

If cross def is on we can establish server to server communication.