Skip to main content

 
Professional certification
  >  
Certifications
  >  
Test information

Test 894: IBM Tivoli Storage Manager V5.4 Administration


Overview Objectives Test Preparation

Section 1: Concepts

  1. Given access to IBM Tivoli Storage Manager documentation, IBM Redbooks, the IBM Tivoli Storage Manager support website and/or access to IBM Tivoli Storage Manager training, read documents and or attend training to learn backup methods in order to understand the types of backups, restore, archive and retrieve methods available in IBM TSM. With emphasis on performing the following steps:
    1. Read documents and or attend IBM Tivoli Storage Manager Implementation training.
    2. Explain Incremental backup.
    3. Explain Incremental by date backup.
    4. Explain Selective backup.
    5. Explain Group backup.
    6. Explain Image backup.
    7. Explain Subfile backup.
    8. Explain Classic restore.
    9. Explain no query restore.
    10. Explain point in time restore.
    11. Explain restartable restore.
    12. Explain how to generate backup set.
    13. Explain restore from backup set.
    14. Explain archive.
    15. Explain retrieve.
    16. Explain IBM TSM journaling.
    17. Explain Network Attached Storage (NAS) Network Data Management Protocol (NDMP) backups.

  2. Given access to IBM Tivoli Storage Manager documentation, Redbooks, the IBM Tivoli Storage Manager support website and/or access to IBM Tivoli Storage Manager training, read IBM TSM documentation and or attend training to learn IBM TSM Policy Domain, Policy set, Management class and backup and archive copygroups. With emphasis on performing the following steps:
    1. Read and/or attend IBM TSM Implementation training.
    2. Explain IBM TSM Policy Domain.
    3. Explain IBM TSM Policy set.
    4. Explain IBM TSM Management classes.
    5. Explain IBM TSM backup/archive copygroups.

  3. Given access to IBM Tivoli Storage Manager documentation, Redbooks, the IBM Tivoli Storage Manager support website and/or completion of IBM Tivoli Storage Manager training, explain VERExists, VERDeleted, RETExtra and RETOnly to understand versioning parameters in copygroup. With emphasis on performing the following steps:
    1. Read IBM TSM documents and/or attend IBM TSM Implementation training.
    2. Explain VERExists.
    3. Explain VERDeleted.
    4. Explain RETExtra.
    5. Explain RETOnly.

  4. Given access to IBM Tivoli Storage Manager documentation, Redbooks, the IBM Tivoli Storage Manager support website and/or completion of IBM Tivoli Storage Manager training, explain primary random access storage pools, primary sequential access storage pools and explain copy sequential access storage pools in order to understand storage hierarchy.
  5. Given business requirements for data retention, explain benefits of backup sets, backups, and archives to understand when to use backups vs. archives. With emphasis on performing the following steps:
    1. Explain benefits of backups.
    2. Explain benefits of archives.
    3. Explain benefits of backup sets.

  6. Given access to IBM Tivoli Storage Manager documentation, Redbooks, the IBM Tivoli Storage Manager support website and/or access to IBM Tivoli Storage Manager training, read documentation and/or attend training in order to explain the purpose of Include and Exclude processing , identify the Include and Exclude rules and explain Exclude statement options. With emphasis on performing the following steps:
    1. Read IBM TSM documentation and/or attend IBM TSM Implementation training.
    2. Explain the purpose of Include and Exclude processing.
    3. Identify the Include and Exclude rules.
    4. Explain Exclude statement options.

  7. Given access to IBM Tivoli Storage Manager documentation, Redbooks, the IBM Tivoli Storage Manager support website and/or access to IBM Tivoli Storage Manager training, read docs and/or attend training in order to distinguish between types of collocation and the benefits and drawbacks of each. With emphasis on performing the following steps:
    1. Read IBM TSM documentation and/or attend IBM TSM Implementation training.
    2. Explain collocation.
    3. Explain collocation by group.
    4. Explain collocation by filespace.
    5. Explain collocation by node.
    6. Explain collocation of active-data pools.

  8. Given access to appropriate documentation explain how multiple stanzas allow access to multiple nodes and multiple servers from a single physical system to understand the benefits of multiple stanzas.
    1. Explain how multiple stanzas in the dsm.sys file allow access to multiple TSM servers.
    2. Explain how multiple stanzas allow multiple nodes to be configured on a single system.

  9. Given access to IBM Tivoli Storage Manager documentation, Redbooks, the IBM Tivoli Storage Manager Support website and/or access to IBM Tivoli Storage Manager training, read docs and/or attend training in order to distinguish between types of storage pools and the benefits and uses of each.
    1. Read IBM TSM documentation and/or attend IBM TSM Implementation training.
    2. Explain primary storage pools.
    3. Explain copy storage pools.
    4. Explain active data pools.
    5. Explain random storage pools.
    6. Explain sequential storage pools.

Section 2: Daily Operations

  1. Given the business's backup requirements, central scheduler is active, SCHEDMode is set to polling, clients have been registered, have connection to the server, scheduler is running service/daemon and has been associated to a specific schedule, start an admin session, update the schedule and then stop/start client scheduler service/daemon to update its' schedule. With emphasis on performing the following steps:
    1. Start administrative command line.
    2. Update the correct schedule.
    3. Stop and restart the client schedule service/daemon.

  2. Given a running server and query requirements, start the command line administrative console (dsmadmc) and redirect output as required for reports to successfully complete the queries. With emphasis on performing the following steps:
    1. Start administrative command line.
    2. Execute desired queries.
    3. Redirect output (as required) for reports, etc.

  3. Given a scheduled nightly backup, the locations of dsmsched.log and dsmerror.log and permission to read the log files, issue and obtain output from event queries, review the dsmsched.log and dsmerror.log for successful completion and error messages respective to determine the status of a nightly backup. With emphasis on performing the following steps:
    1. Issues/obtain output from query event.
    2. Review output from query event.
    3. Review dsmsched.log file for start and stop times to determine backup duration and success.
    4. Review dsmerror.log file for discrepancies and unsuccessful conditions that may need further action.
    5. Review dsmwebcl.log for discrepancies and unsuccessful conditions that may need further action.

  4. Given a TSM client on Windows, a requirement to backup a file regardless of its' status (open vs. closed), LVSA is installed and the correct identification of the copygroup and type that affects these files, define serialization for open files, define cache file for LVSA, start LVSA service and ensure open files are included in the backup per customer requirement. With emphasis on performing the following steps:
    1. Modify serialization for open files. Update serialization in copygroup: [domain][policyset][mgmt class} standard type=
    2. Install LVSA as part of windows install.
    3. Define cache file for LVSA.
    4. Start LVSA service.
    5. Ensure files are included.

  5. Given a running TSM server, run "QUERY DB" and "QUERY LOG" from an open administrative command line to review the database and recovery log capacity. With emphasis on performing the following steps:
    1. Open administrative command line.
    2. Run Q DB
    3. Run Q Log

  6. Given access to the server’s OS, run the "df -k" on UNIX or check the "disk properties" on Windows to review the space availability. With emphasis on performing the following steps:
    1. Run O/S command to check space. UNIX: df -k Win: right click drive check property entry.

  7. Given a running administrative command line, a configured and attached tape library and a known number of total tape slots in a tape library, run the "SELECT" command to check for available scratch tapes, run the "SELECT" command to get tape count, check out tapes if all slots are full and when scratch tapes are low label and check-in additional tapes in order to manage scratch volumes. With emphasis on performing the following steps:
    1. Run command to check available scratch tapes: select count(*) from libvolumes where status ="scratch".
    2. Select Count (*) from libvolumes to get tape count.
    3. If all slots are full then check out tapes.
    4. If available scratch tape is low review 2.12
    5. Ability to label volumes in multiple ways.
    6. Calculate daily estimation of scratch tape requirements.

  8. Given a running dsmadmc session, a configured and attached library and tape available to be checked out, run the "CHECKOUT LIBVOL" command to check out tape volumes. With emphasis on performing the following steps:
    1. Run checkout libvolume command.
    2. Verify the correct volume is checked out query libvol.
    3. Physically remove the tape volume.

  9. Given a configured and attached library, a running administrative command line, new tapes are ready for use and are loaded into the I/O ports of the library, check in the tape as private if returning tape to restore data, check in the tape as scratch if loading a previously labeled tape and label a new tape, so that scratch and data tapes are available to TSM. With emphasis on performing the following steps:
    1. If returning tapes to library that still contain data (for restore) run checkin LIBVOL status= private.
    2. If adding tapes previously labeled run checkin LIBVOL status= scratch command.
    3. If adding new tapes run Label LIBVOL command.
    4. Run QUERY LIBVOL to verify tape is successfully labeled/checked-in.

  10. Given the data from a completed backup is stored in the primary storage pool, the next storage pool is defined and pre-defined thresholds are set, change the high and low migration thresholds using the "UPDATE STGPOOL" command to force data migration. With emphasis on performing the following steps:
    1. Issue update command UPD STG to change hi and low thresholds to zero.
    2. Issue UPDATE command to reset high low thresholds to original values.
    3. Issue command QUERY PROCESS to verify migration is running.

  11. Given a requirement for an off-site copy of backup data, the data resides on the primary storage pool, enough media is available and enough tape drives are available, check tape library to ensure enough tape drives are available and backup the storage pool from the command line so that data in the primary storage pool is also on the copy pool. With emphasis on performing the following steps:
    1. Check tape library to ensure scratch volumes are available.
    2. Check tape drives to ensure availability.
    3. Run command to check tape availability select count (*) from LIBVOLS where status=SCRATCH. Run command BA STG [primary pool name][Copy pool name] maxproc=2.
    4. Using command line issue dsmadmc or from ISC select stgpools.
    5. Issue BACKUP STGPOOL command.

  12. Given the TSM DB version controls will expire the database entries and expiration is processed every 24 hours, from the administrative command line issue the expiration command to remove expired data. With emphasis on performing the following steps:
    1. From administrative command line issue (dsmadmc) or from ISC select database.
    2. Issue expiration command EXPIRE INVENTORY.

  13. Given a completed client backup cycle, available space for a DB backup, run the database backup from the administrative command line and verify the database was successfully backed up. With emphasis on performing the following steps:
    1. Start administrative command line.
    2. Run database backup.
    3. Verify database backup completed successfully.

  14. Given I/O errors on volumes and the tape status is changed by TSM to READONLY, run the administrative command line, audit the volume, restore the lost data and remove the damaged tape from the library in order to correct volume errors and create new volumes. With emphasis on performing the following steps:
    1. Issue command using administrative command line (dsmadmc) or use ISC to check status of volumes (QUERY VOLUME F=D).
    2. Issue command to change volume status to read write.
    3. Issue command to validate and audit volume.
    4. Correct volume errors by recalling offsite tape and copying files.

  15. Given a volume and data to be moved in the foreground and available storage space, from the administrative command line change the volume to READONLY and move the data to ensure successful data movement. With emphasis on performing the following steps:
    1. Start administrative command line (dsmadmc).
    2. Change volume to read only.
    3. Run MOVE DATA command with wait=YES parameter.

  16. Given that client node information and node data must be exported, update the node to allow for deletion of backups and run the "EXPORT NODE" command to export node data. With emphasis on performing the following steps:
    1. Start administrative command line (dsmadmc).
    2. Update node to allow for deletion of backups. update node backdel=YES
    3. Run EXPORT NODE command.

Section 3: Server Management

  1. Given appropriate administrator privileges on OS and system has available raw logical volumes, verify the available space is configured and on OS, run "dsmfmt" commands to format TSM DB recovery log and disk storage pool. With emphasis on performing the following steps:
    1. Verify that the raw logical space is configured for OS.
    2. Run TSM command DSMFMT to format the database.
    3. Run TSM command DSMFMT to format the stgpool.

  2. Given a formatted database and log and the appropriate TSM privileges and authority run the following TSM commands 'DEFINE DB VOLUME', 'EXTEND DB', 'DEFINE LOGVOLUME', 'EXTEND LOG', 'QUERY DBVOLUME', 'QUERY DB', 'QUERY LOGVOLUME' and 'QUERY LOG' so that space has been allocated for TSM database and log. With emphasis on performing the following steps:
    1. Run TSM command DEFINE DBVOLUME.
    2. Run TSM command EXTEND DB.
    3. Run TSM command DEFINE LOGVOLUME.
    4. Run TSM command EXTEND LOG.
    5. Run TSM command QUERY DBVOLUME.
    6. Run TSM command QUERY DB.
    7. Run TSM command QUERY LOGVOLUME.
    8. Run TSM command QUERY LOG.

  3. Given formatted and allocated TSM database and logs with sufficient space for mirroring, run the following TSM commands: 'DEFINE DBCOPY', 'DEFINE LOGCOPY', 'QUERY DBVOLUME' and 'QUERY LOGVOLUME' so that database mirror and log mirror are defined. With emphasis on performing the following steps:
    1. Run TSM command DEFINE DBCOPY.
    2. Run TSM command DEFINE LOGCOPY.
    3. Run TSM command QUERY DBVOLUME.
    4. Run TSM command QUERY LOGVOLUME.

  4. Given administrator has appropriate TSM privileges and authority, devclass is defined and scratch volumes are available, run TSM command 'backup db' and run TSM command 'query process' so that the TSM database is backed up to file or tape. With emphasis on performing the following steps:
    1. Run TSM command BACKUP DB and enter either TYPE =FULL, TYPE=INC OR TYPE= DBSNAPSHOP.
    2. Run TSM command QUERY PROCESS.

  5. Given configured LAN or SAN automated tape library run the following TSM commands 'define library', 'define path', 'query library' and 'query path' so that the TSM library and path are defined. With emphasis on performing the following steps:
    1. Run TSM command DEFINE LIBRARY LIBTYPE=<>.
    2. Run TSM command DEFINE PATH SOURCE_NAME DESTINATION_NAME SRCTYPE=<>.
    3. Run TSM command QUERY LIBRARY.
    4. Run TSM command QUERY PATH.

  6. Given allocated storage pool space, requirements for whether primary storage pool will be disk or tape and whether storage pool will be copied sequentially, run the following TSM commands 'define stgpool', 'update stgpool' and 'query stgpool' so that disk, tape and copy stgpools are defined. With emphasis on performing the following steps:
    1. Run TSM command DEFINE STGPOOL STGPOOL_NAME for disk.
    2. Run TSM command DEFINE STGPOOL STGPOOL_NAME POOLTYPE=PRIMARY.
    3. Run TSM command DEFINE STGPOOL STGPOOL_NAME POOLTYPE=COPY.
    4. Run TSM command UPDATE STGPOOL.
    5. Run TSM command QUERY STGPOOL.

  7. Given appropriate administrator privileges and business requirements for data management, define domains, policy sets, management class and copy group and then validate and activate policyset so that the TSM policy is configured. With emphasis on performing the following steps:
    1. Run TSM command DEFINE DOMAIN.
    2. Run TSM command DEFINE POLICYSET.
    3. Run TSM command DEFINE MGMTCLASS.
    4. Run TSM command DEFINE COPYGROUP TYPE=BACKUP.
    5. Run TSM command DEFINE COPYGROUP TYPE=ARCHIVE.
    6. Run TSM command ASSIGN DEFMGMTCLASS.
    7. Run TSM command VALIDATE POLICYSET.
    8. Run TSM command ACTIVATE POLICYSET.

  8. Given appropriate administrator privileges and business requirements for data management, define client option set, query client option set and define client option so that client option set is defined. With emphasis on performing the following steps:
    1. Run TSM command DEFINE CLOPTSET.
    2. Run TSM command QUERY CLOPTSET.
    3. Run TSM command DEFINE CLIENTOPT.

  9. Given appropriate administrator privileges and a need to script commands, run the 'define script' and 'query script' commands so that the script is defined. With emphasis on performing the following steps:
    1. Run TSM command DEFINE SCRIPT SCRIPT_NAME.
    2. Run TSM command QUERY SCRIPT.

  10. Given appropriate administrator privileges and scheduling requirements, run the 'define schedule type=administrative' and 'query schedule type=administrative' so that an administrative schedule is defined. With emphasis on performing the following steps:
    1. Run TSM command DEFINE SCHEDULE TYPE=ADMINISTRATIVE.
    2. Run TSM command QUERY SCHEDULE TYPE=ADMINISTRATIVE.

  11. Given appropriate administrator privileges and requirements for scheduling client schedules, run the 'define schedule' command including node name and schedule name, define schedule to appropriate policy domain, query schedule and associate client node to appropriate schedule. With emphasis on performing the following steps:
    1. Run TSM command DEFINE SCHEDULE DOMAIN_NAME SCHEDULE_NAME INCR, SEL, ARCHIVE, RESTORE, RETRIEVE.
    2. Run TSM command DEFINE SCHEDULE DOMAIN_NAME SCHEDULE_NAME ACTION =< >.
    3. Run TSM command DEFINE ASSOCIATION DOMAIN_NAME SCHEDULE_NAME NODE_NAME.
    4. Run TSM command QUERY SCHEDULE.
    5. Run TSM command QUERY ASSOCIATION.

  12. Given appropriate administrator privileges and business requirements, specify the TSM server parameters to set number of server sessions, retry periods and client polling frequency and randomizing so that client and server sessions are balanced. With emphasis on performing the following steps:
    1. Regulate the number of sessions the server can use with SET MAXSCHEDSESSIONS SCHEDULEPERCEN < %>.
    2. Specify max number of times a scheduler or client can retry if failed with SET MAXCMDRETRIES command.
    3. Set number of minutes the scheduler or client waits between retry attempts with SET RETRYPERIOD command.
    4. Regulate frequency client contacts server to obtain scheduled work in client polling mode with SET QUERYSCHEDPERIOD command.
    5. Specify the degree to which start times are randomized within startup window of schedule on clients using client polling mode with SET RANDMIZATION command.

  13. Given appropriate administrator privileges, business requirements, and node name and password, determine node's policy domain, register the node to the server and verify the node definitions are correct so that the node is registered. With emphasis on performing the following steps:
    1. Determine the policy domain that the client will be defined to.
    2. Choose the parameters that are applicable to that node.
    3. Run TSM command REGISTER NODE.
    4. Verify node definitions are set correctly. Run QUERY NODE.

  14. Given appropriate administrator privileges for OS and TSM, business requirements, available TSM backup archive client software, known client node information, verify the prerequisites have been met, follow the documented installation instructions, modify the client options file and verify connectivity to the TSM server to have a working TSM client. With emphasis on performing the following steps:
    1. Verify the prerequisites.
    2. Follow the backup-archive clients' installation and user's guide and README file.
    3. Modify dsm.opt/dsm.sys files with appropriate options.
    4. Verify connectivity to TSM server is valid.

  15. Given the appropriate administrator privileges, business requirements and a node with the backup-archive client installed and configured, ensure password parameters are correct, provide password and user ID, start client services and the correct port is used with the browser to set up the web client. With emphasis on performing the following steps:
    1. Verify password access is set to generate in dsm.sys/dsm.opt file.
    2. Generate TSM password by starting backup-archive client command line DSMC QUERY SESSION.
    3. Enter user ID and password after prompted.
    4. Start the client acceptor daemon.
    5. Verify the TSM remote client agent daemon in startup file.
    6. Access the web client by entering URL from browser http://machine_name:1581.

  16. Given appropriate administrator privileges, business requirements, a node with the backup-archive client installed and configured, available SAN tape drive and storage agent software, follow the documented installation instructions, setup and verify server to server communication, update tape library definition for sharing, update 'dsmsta.opt', 'dsm.opt' and 'dsm.sys' for LAN free to set up and configure LAN free for TSM storage agents. With emphasis on performing the following steps:
    1. Verify administrator rights/privileges.
    2. Verify available OS space.
    3. Install storage agent and other required software components based on installation guide and README.
    4. Configure TSM Server for LAN-Free per installation guide and README.
    5. Setup server to server communication on TSM server and storage agent.
    6. Verify servers are able to communicate with each other.
    7. Update device class definitions for disk or tape media.
    8. Update tape library definitions shared=yes.
    9. Update dsmsta.opt file on the storage agent with appropriate options.
    10. Modify dsm.sys/dsm.opt file with LAN free options.
    11. Verify LAN free connection.
    12. Update path definitions for LAN free connection.
    13. Start storage agent.
    14. Storage Agent maintenance/upgrade requirements.

  17. Given appropriate administrator privileges and disaster recovery requirements, verify license, specify recovery information, move backup media and prepare daily tasks so that Disaster Recovery Manager is set up. With emphasis on performing the following steps:
    1. Verify license Extended Edition.
    2. Specify recovery instructions.
    3. Specify information about server and client nodes.
    4. Specify recovery media.
    5. Create and store DRM plan.
    6. Move backup media to offsite.
    7. Summary of DRM daily tasks.
    8. Validate the recovery plan for use in a disaster.

Section 4: Performance and Problem Determination

  1. Given that the TSM client node on a Windows platform has an 8 hour backup window and 300GB of Total Storage, daily backups are taking twice as long as the available backup window, check backup statistics, aggregate transfer rate, network transfer rate, number of files backed up and number of files inspected in order to improve backup performance. With emphasis on performing the following steps:
    1. Using command line or web access, review client backup statistics. Check aggregate transfer rate against network transfer rate.
    2. Check available network bandwidth and available transfer rate at time of backup. Issue FTP block. Push across network as pre-schedule and command to determine transfer rate.
    3. Check the number of files backed up. Check number of files inspected.
    4. Determine percentage difference of transfer rate versus aggregate rate to validate problem with network or if problem is with TSM inspect process.
    5. If network is cause of problem, then move schedule to less busy time if available.
    6. If unable to move schedule, create primary network for TSM backups by adding separate NIC card.
    7. If inspect is the problem, then use journal backup.

  2. Given the TSM server has (2) 1.8 GHz CPUs with 4 GB of memory, 40 GB TSM DB 80% utilized, (6) LTO tape drives and 660 GB diskpool backup (60) client nodes with 6 TB of Total Storage overall backup performance needs improvement, limit server workload and number of sessions and process during backup windows, turn on instrumentation thresholds to check I/O, read and write to adjust parameters to improve server performance. With emphasis on performing the following steps:
    1. Determine server workload at time of backup by checking byte counts before and after backup.
    2. Limit number of session and processors running during backup.
    3. Turn on performance instrumentation statistics by thread.
    4. Match thread read and write data counts for single session.
    5. If % of read/writes very by 50% increase buffer size to remove bottleneck. Repeat all steps until level is satisfactory.

  3. Given that client backup performance is in need of improvement since the node has 10/100 network connection with 300 GB of Total Storage and an 8 hour backup window, check how much data changes on a daily basis, check that network adapter is not set to autonegotiate, check difference between data inspect rate versus change to determine which network optimization parameters or TSM backup options need to be changed to optimize and tune client backup performance. With emphasis on performing the following steps:
    1. Determine how much data changes on a daily basis.
    2. Use dedicated 1 GB or better network for backup.
    3. Ensure full duplex settings on new network.
    4. Determine if high inspect volumes of backups and if "yes" use Journal-based backups.
    5. Determine if high change percentage of data use multi sessions.

  4. Given access to problem determination guide and administrative command line, check TSM errors, check OS related errors to define the problem and obtain error messages so that you have the necessary information prior to calling IBM Tivoli support. With emphasis on performing the following steps:
    1. Check activity log for errors Q ACT.
    2. Check OS errors: AIX= ERRPT -A, WIN= check event log.
    3. Review TSM error explanation: help error or check error messages manual.
    4. Based on explanation of error, problem determination should point to a specific device or area. Review specific problem determination steps for this issue.
    5. If the problem cannot be resolved, contact IBM Tivoli support.

  5. Given daily backup growth, using activity log and TSM SELECT statements, gather daily statistics to understand and document daily growth and trending to determine capacity of tapes, number of drives and future server needs. With emphasis on performing the following steps:
    1. Build daily trend of total backup data gathered into a spreadsheet or operational reporting tool.
    2. Use operational reporting tool to view statistics.
    3. Issue QUERY DB command and QUERY LOG command to validate amount of space used/available.
    4. Issue audit license command to validate license.
    5. Issue the following commands: Q LIBR, Q VOL and Q LIBVOL to determine capacity of tapes and library storage slots.

  6. Given the TSM Server is down and your attempt to restart generates internal errors, LOGSEG error, determine if an out of space condition exists with either the database or log and take corrective action to extend database or log so that the server is recovered. With emphasis on performing the following steps:
    1. Determine where the problem is by trying to start the server in fore ground. Observe errors: dbvol or logvol.
    2. Find dbvol or logvol locations and verify available disk space with the following commands: DSMSERV DISPLAY DBVOLUME or check diskspace avail - see objective 1.7.
    3. Format a new volume (db or log) DSMSERV DSMFMT. Use a size divisible by 4MB.)
    4. Extend the log or database: DSMSERV Extend [log or database] volname size.
    5. Start the TSM server: sudo../rc.adsmserv>/dev/console&1>2 &.
    6. Start DSMADMC administrator session.
    7. Determine cause of problem. To resolve check the activity log.
    8. Understand how this situation is affected by the LOGMODE you selected.
    9. Run a TSM database backup to clear the recovery log, then reduce the log to remove emergency volume or increase log to meet needs.
    10. Check levels for database backup triggers (obj 3.4) and space triggers (obj 3.5). Adjust as required.

  7. Given a previously working backup fails with TCP/IP errors in the error log, determine status of the hardware and firewall, test and reconfigure the TCP/IP parameters to ensure TCP/IP connectivity is functioning properly. With emphasis on performing the following steps:
    1. Determine status of hardware. Is the hardware plugged is. Is the system running?
    2. Determine status of firewall. Check to see if the firewall is running.
    3. Test TCP/IP configuration. Ping 'hostname'.
    4. Reconfigure TCP/IP parameters as needed.

  8. Given that TSM backups failed and errors on library display, errors in activity log and OS logs, determine drives and paths are online, I/O errors are not media caused. Resolve hardware device issue to correct problem. With emphasis on performing the following steps:
    1. Check TSM drives and paths for errors.
    2. Review/interpret errors from TSM and OS. This should reduce possible problems down to a specific device.
    3. Check device configuration at the OS level. Determine if the devices are available. If they are, proceed to the next task. If they are not, work with the CE and system administrator to make them available.
    4. Use OS or other utility software to help isolate the problem.
    5. Depending on the results from above, you should be able to isolate the problem to one of the following: OS, tape volume, drive or library.
    6. If the root cause is the drive or library, then contact IBM Tivoli support to repair. If OS is the cause, then work with the system administrator to resolve. If the issue is a bad tape volume, then follow process for recovering from a media loss.
    7. After repairs do the following: 1 update drive online=yes update path online=yes 2. audit library 3. test tape movement and read/write to verify fix. 4. check cleaning cartridge usage and replace if necessary.

  9. Given you have an unresolved issue and have opened a PMR with support and they have requested both a trace and execution of specific instructions then you run the trace and send them the results, so that the data can be used to resolve the problem. With emphasis on performing the following steps:
    1. Run traces per specific instructions from support.
    2. Provide trace results to support per their instructions.

  10. Given you have access to the internet, you can find current client and server code/patches, Tivoli's support webpage, obtain TSM documentation (manuals, Redbooks, training materials and README files), review documentation so that you can be a well informed storage administrator. With emphasis on performing the following steps:
    1. TSM upgrades for client, server and tape code can be located at: ftp://software.boulder.ibm.com
    2. Tivoli support main page www.ibm.com/software/sysmgmt/products/support
    3. Review documentation (TSM manuals, Redbooks, training materials, README).
    4. Check resources listed in manuals.
    5. Review TSM Problem Determination Guide.

Test registration

Authorized Prometric test centers (worldwide testing)