Escolar Documentos
Profissional Documentos
Cultura Documentos
TSM PROCEDURE
1. DAILY PROCEDURE
1.1 Login to TSM
1.2 TSM Report
1.3 Client Node Sessions
1.4 Missed / Failed Backup
1.5 Exchange pool Backup
1.6 Checkout Tapes
1.7 Transfer Tapes to Ajman
1.8 Receive Tapes from Ajman
1.9 Checkin Vault retrieve Tapes
1.10 TSM Tape Management
1.11 Scratch New Tapes
3. DR PROCEDURE
3.1 TSM Sever DB Backup Restoration
3.2 TSM File Restoration
3.3 Update Library on DR TSM
3.4 TDPSQL Restoration Settings
3.5 TDPSQL Backup Restoration for specific client
1. DAILY PROCEDURE
TSM Report is generated on the DATAPC workstation desktop. Refresh the report named TSM
COMPLETE REPORT
1.3 Client Node Sessions
To display information about administrative and client node sessions using the
(Query Client Sessions). Using this command, verify if there are still client node sessions
(client backup) that are still communicating with the server. Issue the command:
Q SESSION
1.4.1 Backup of client servers to TSM take place during the night. Backup window starts from 5pm to
6am.
To view the FAILED or MISSED backups, IN-PROGRESS in the last 24 hours:
RUN MISFAIL
1.4.3 To run the FAILED OR MISSED backup by following the procedure of RESTART
FAILED/MISSED backup procedure as follows:
1.4.3.1 In order to get the list of the FAILED/MISSED backup, issue the command:
run misfail
Note: 1. <schedule name> is the name of the client server's scheduled backup that is either failed
or missed
2. Check from which domain does the client schedule belongs
Sample output
Sample output
STATUS MEANING
----------- -----------------------------------------------------------------
Started that the event has begun processing
In Progress Specifies that the scheduled event is running
Pending processing the scheduled operation has not yet begun
Failed the client reports a failure in executing the scheduled operation
Missed the scheduled has not begun
Future Specifies that the beginning for the event is in the future
You can issue the run clievent <schedule name> for several times to check if the
scheduled backup completed successfully
1.4.3.6 After the backup completed successfully, update the client schedule to its original
schedule,issue the command
Note: <time> should be the original schedule of the client server's scheduled backup
1.4.3.7 Go to the server and restart the TSM scheduler again. Exit from the client server.
1.5 Exchange Pool Backup
Daily at 6:30 AM, migration process starts in the background. Migration will be done in two disk
primary storage pools: DISKPOOL and SQLMETAPOOL. This process is necessary to migrate all
amount of data currently residing in the two storage pools to its next storage pool namely
TAPE_POOL and SQL_POOL.
To check if there is any active background process using the command QUERY PROCESS (Query
One or More Server Processes)
Q PROCESS or Q PROC
∙ Daily at 6:45 AM, Back Up of Primary Storage Pools to Copy Storage Pools are started. This is
necessary to have a copy of all primary storage pools to copy storage pool tapes which will
eventually transfer to the Disaster Recovery Site in AJMAN. Full back up of Tivoli Storage Manager
DATABASE to sequential tape is also included in this process as well as backup of VOLUME
HISTORY and generation of disaster recovery plan.
QUERY PROCESS
∙ verify the primary storage copy pool to copy pool is running, issue the command
Q MOUNT
∙ If one of the drive is IDLE, issue the command: DISMOUNT VOLUME <VOLUME_NAME>
If the one drive is free check out Tapes from the library, using
RUN OFFSITETAPES
Then issue Q PROCESS to make sure tapes are being checkout from the library
∙ check the TSM tapes that need to be released from the vault (SCRACTH VOLUMES) in AJMAN
by issuing the command:
RUN VAULTRETRIEVE
∙ checkout all tapes by physically checking out the tapes from the TSM library. Then write down the
all Volume name to the DR Checklist. To make sure which tape is the DB backup, go to
ADCBPROTSM Server -> Start (right click) -> go to C:\Tivoli\TSM\DRplan folder. Open the latest
file and check which volume is the DB backup.
FAST EXPRESS courier will carry the TSM Tapes in fire/tamper proof briefcase and deliver to DR
site operations staff in Ajman. Before handing over the briefcase to the said courier, take
acknowledgement from the courier person.
1.8.1 Verify if the backup of EXCHANGE STORAGE POOL are running by issuing the command:
Q PROCESS
1.8.2 if no more active process running in the background, verify if EXCHANGEPOOL backup to
COPY_POOL is successfully completed by issuing the command:
RUN EXCHBKP
1.8.3 checkout the tapes (Exchange Pool Tapes) to be transfered to Disaster Recovery Site in
AJMAN. But before checking out the tapes, 1 drive should be available.
Q MOUNT
1.8.5 If one drive is free, tapes can now be checkout from the library, using
RUN OFFSITETAPES
1.8.6 Issue Q PROCESS to make sure tapes are being checkout from the library
Include these copy pools for next day’s copy pools that need to be transferred to AJMAN.
1.9.1 Vault Retrieve Tapes that were released from the AJMAN will be received through the FAST
EXPRESS. Check in the tapes as Vault scratch volumes.
1.9.2 One drive should be free to check in the tapes. Issue the command:
Q MOUNT
1.9.6 To make sure that tapes are being check in to the library, issue the command Q PROCESS
1.9.7 To make sure that tapes are successfully checked in to the library, and how many scratch tapes
are available, issue the command:
RUN SCRATCHVOL
1.10 TSM TAPE MANAGEMENT
RUN SCRATCHVOL
RUN OFFSITETAPES
Then issue Q PROCESS to make sure tapes are being checkout from the library
1.10.4 To find the tape count according to the state drmedia
RUN TAPECOUNT
1.10.5 To find which tape is missing or lost, lost tape means the TSM server does not know if
the tape is in vault or in vault retrieve status. Lost tapes are usually happening to
scratch tapes, if user is trying to check in a tape using the run reuse command, and
then no drive is available or the library is already FULL. Tape lost is happening. If this
instance happened, user should note down that the said tape was not successfully
check in into the library. To check what tape is lost or missing, issue the command:
RUN TAPELOST
1.11 Scratch new TSM Tapes
The issue the command: reply nnn command (where nnn is the number)
Then check if the scratch tapes are being added by issuing q proc command.
After the process has been completed, check if the scratch tapes have been successfully added by issuing q
libvol command.
ADCBPROTSM (name of the TSM server name) is maintaining 6 Policy domains. Policy
domain set the rules on how data from different client nodes (client server) are to be
managed, for example in the case of backup, how many versions should be kept, where they
should be stored. Client nodes are grouped together with other nodes with common storage
management requirements into a Policy Domain.
Each policy domain contains one active policy set. A Policy Set contains and helps to
manage a collection of storage management rules for different storage management activities.
The rules are stored, within the Policy Set, in one or more Management Classes. An active policy
set contains one default management class. ADCBPROTSM has the following policy sets:
2.2.2 Click Policy Domains and Client Nodes in the Work Items list. The Policy Domains
work page is displayed with a table that lists the servers that are accessible from the
Administration Center.
2.2.3 Then click ADCBPROTSM on the server list. A list of policy domains will show
2.2.4 In the Domain Name column of the ADBPROTSM server's Policy Domains table,
click the WIN_DOM policy domain. The WIN_DOM Properties portlet is displayed:
2.2.5 In the domain's properties portlet, click Client Nodes. A table is displayed listing all the nodes
assigned to the WIN_DOM policy domain:
2.2.6 In the client nodes table, click Select Action from the drop down list, and then select Create a
Node. The Create Node wizard is displayed:
2.2.7 In the General option, supply the name of the client node and choose the
WIN_DEFAULT option from the drop down list below.
2.2.8 In the Security option, give a password and choose NEVER on the password
expiration
2.2.9 In the Administrators option, choose the first option
2.2.10 Finally, in the Summary option, the name of the new client node is displayed in the
Client Node table for the WIN_DOM policy domain. Click Finish.
2.3 IBM Tivoli Storage Manager BA Client Installation
2.3.1 Install the TSM client on the client machine, a dialog box will appear
2.3.2 Click on the Install Products, and then choose TSM Backup-archive Client –x32
2.4.1 Click Start > Programs > Backup-Archive GUI. The below window will appear,
then click NEXT, choose the TSM Client Configuration and TSM Client scheduler .
2.5.1 Login into TSM Server using the node name as User ID and the password given in registering
TSM client in ISC admin as the password.
2.5.4 In General option, give the schedule name and description, NEXT
2.5.5 Choose Incremental backup
2.5.6 Choose Repeat Daily and give the TIME of the schedule backup
Copy the 3 files ( dsm.opt, sqlfull.log.cmd & sqldiff.cmd ) from the source pc.
2.8.2 On the server Select Start Programs Tivoli Storage Manager BackupArchiveGUI
A wizard menu will appear to help to configure the TSM node.
2.8.3 Select helpme to create service schedule from the wizard.
2.8.4 Put the node name and password (Put server name).
2.8.5 Put the scheduler name (TSM Scheduler). When asked to start scheduler now, select ‘Yes’.
Now the node is configured and ready to take backup through the TSM.
Copy TDPO.opt from any other oracle client and paste in C:\TSM\tivoli\AgentOBA folder.
Modify the node name as the node name given in point 2.
2.9.3 Select any one of the existing Schedule Name & Choose the copy schedule from combo box
which is in the top of the screen.
2.9.4 Enter the name of the server in the field New Schedule Name
2.9.6 Select the Schedule Name & Choose the Update schedule from combo box which is in the top
of the screen.
2.9.7 Edit the field Start Date, Start Time, Period Units & Days of Week.
2.10.4 From the General Tab → click the Select button for the Error Log.
2.10.5 Tick the box of Prune old entries and enter the value 7 Days → Click the OK button.
3. DR Procedure
3.1 DB Backup Restoration
Assumptions –
Empty Drive
Press then by pressing > Go offline and
Use > and go to Command Press
Select Import
Import to Slot (4,5 up to 8)
Drive Door will open, Insert the Cartridge
Door will close
Then press on Go-online.
6. The command line will open as shown in the picture.
7. Before pressing enter, check that the drplan.txt file has exploded into multiple files into the same
directory c:\tivoli\tsm\drplan\.
8. Press enter and wait till you get next prompt. This process may take from 30 minutes to 1
hour. In the meantime check for the file
c:\tivoli\tsm\drplan\LOGANDDB.VOLUMES.INSTALL.LOG
Another window will open automatically when the formatting is completed. Wait till you get a prompt
TSM:SERVER1>
Enter the following command on the command prompt of Window No. 2
register admin admin Password: ‘XXXX’ <ENTER>
grant autho admin class=system <ENTER>
Set servername adcbprotsm <ENTER>
9. Press Enter on command line Window 1 as shown in figure below.
10. The TSM Server automatically checkin the tape you have inserted inside the library. Please wait till
it has checked in the label. You may check the results as shown in figure below. Once drive empty
is displayed on tape drive screen, give command – q libvol to display the following screen shot.
11. The server will automatically start restoring the database once you press enter. (twice)
12. The halting of server may require sometime. Wait till the command prompt Window No. 2 closes,
and you get another prompt to press enter.
Once the window closes your TSM server has been restored.
13. To checkout any tape give the following command on server command line:
checkout libvol ltolib1 VolumeNameOfTape checklabel=no remove =bulk
14. To checkin any tape, the give the following command on server command line after inserting the
tape:
checkin libvol ltolib1 search=yes status=private
3.2 TSM File Restoration
Go to file to LOGON
Nodname :
Usd Id :
Password :
( Make sure you are connected to right Client ) then click Restore button
3.2.1.6 Select Path ( Make sure path must be C:\TSMRestore ) then click Restore Button again
Will display below status screen
After successful restoration please verify the files from below mentioned folders
3.3 Update Library on DR TSM
Restore the TSM DB Backup on DR TSM as normal. After the database is restored do as follows:
The above Update command needs to be given only once after the DB Backup from production is
restored on the DR TSM Server.
3.4.3 To make sure that the restoration will happen from the copy pool of the DR TSM following
changes needs to be made on the client server.
3.4.3.1 On the client server, open the dsm.opt file in C:\tivoli\tsm\tdpsql\dsm.opt & do as follows:
Change the node name to Production node name EG. NodeName – ADCBCPD_SQL
Change the server name to DR TSM Server name EG. TCPServerAddress – adcbdrtsm
Note: While starting the restoration, do not open the MS SQL Enterprise Manager
3.5 Backup Restoration Procedure for Specific Client
3.5.1 Login to the server ex. ADCB01612 server (Middle Closure 3rd Server). Go to TDPSQL GUI as
below:
3.5.9 Once the restore button is clicked, if the tape is already inside the DR TSM Library, then it will
start the restoration
3.5.10 If the tape is not in the TSM Library, then check on the above console screen on the DR TSM
server. It will display Error message as below:
It displays the message Read Access Denied for volume TYW931L3 – Volume access mode =
unavailable. It means that the tape is not available to the server.
3.5.11 Then insert the tape and give the checkin command from the command line on the DR TSM
Server:
(Do not exit the TDPSQL GUI From where we initiated the backup. If you do so it will corrupt
the database. Just minimize and checkin the tape)
3.5.13 checki libvol ltodrlib volume_name stat=priv (where volume_name will be TYW931L3)
eg. checki libvol ltodrlib TYW931L3 stat=priv
3.5.15 Then give q reply # (where # will be the no. received from q reply)
Eg. reply 001
q v volume_name
Eg:- q v TYW840L3
3.5.17 If the volume is other than copy pool then make the volume as unavailable.
3.5.18 To change the copy pool volume available as well to change the mode to read only.
3.5.19 After the above is done, re-initiate the backup from Point no. 5
3.5.20 Repeat from Step for the Following Databases:
a. MATICACPS
b. SAPS