Test 899: IBM Tivoli Storage Manager V5.4 Implementation

Section 1: Planning

1. Given a qualified, feasible customer service level agreement, and business and legal data retention requirements, apply these agreements to the policy workshop recommendations so that a qualified, validated data retention plan for TSM is produced. With emphasis on performing the following steps:
1. Determine feasibility of customer's service level agreement request with current version of TSM.
2. Apply Business and legal data retention requirements to policy retention requirements.
3. Review policy retention recommendations.
4. Produce a data retention plan.


2. Given the SLAs and design requirements, evaluate the features of TSM to design a solution which meets requirements while minimizing cost. With emphasis on performing the following steps:
1. Interpret business SLAs and retention requirements into technical requirements.
2. Translate technical requirements into features of TSM.
3. Evaluate the cost of each of the features in TSM which can be applied to the technical requirements.
4. Design a TSM solution which meets the requirements with the minimum cost.


3. Given the knowledge of a proposed TSM server environment, a working internet connection and an internet browser, compare the characteristics of the proposed environment with system requirements so that compliance is confirmed. With emphasis on performing the following steps:
1. Open internet browser.
2. Navigate to IBM web site
3. Navigate to IBM Tivoli Storage Manager Product web page.
4. Select server requirements.
5. Select entry for appropriate server platform.
6. Review requirements.
7. Compare proposed server environment to requirements.


4. Given client hardware, network protocols and applications, discover customer hardware, identify OS software, determine network connectivity and locate applications running, so that a list of hardware, operating systems software and OS configuration requirements for TSM is produced. With emphasis on performing the following steps:
1. Discover customer's hardware to be used with TSM.
2. Identify Operating systems used on discovered hardware.
3. Determine network connectivity and protocols available.
4. Locate applications running on hardware to be used with TSM.


5. Given the configuration management information about the customer environment, identify the systems and applications in the environment so that a list of required TSM nodes can be determined. With emphasis on performing the following steps:
1. Identify the systems and applications in the environment.
2. Map the systems and application to TSM client nodes.


6. Given customer requirements and a knowledge of the TSM product family, identify special application requirements to design an appropriate TSM solution. With emphasis on performing the following steps:
1. Gather customer requirements.
2. Obtain knowledge of IBM TSM related products.
3. Compare TSM family products with customer requirements.
4. Recommend appropriate TSM family.


7. Given hardware, operating systems, and network connectivity requirements, evaluate bare machine recovery so that the most appropriate methodology can be determined.
1. Determine customer's hardware to be used with TSM. With emphasis on performing the following steps:
2. Identify Operating systems used on hardware.
3. Determine network connectivity and protocols available.
4. Determine the most appropriate bare machine recovery method for the customer's environment.


8. Given the SLAs, design requirements, existing hardware, and hardware preferences, evaluate the infrastructure and design goals, so that a TSM solution which meets requirements and maps to specific hardware is produced. With emphasis on performing the following steps:
1. Interpret network infrastructure to determine if it’s sufficient to meet needs.
2. Determine if a SAN solution should be deployed for TSM and the systems where it should be deployed.
3. Evaluate the disk infrastructure of the customer to determine what’s appropriate for the TSM server and client.
4. Evaluate TSM server hardware to determine what’s appropriate for the TSM server.
5. Design a TSM solution which meets the requirements with a given hardware.


9. Given customer requirements and a knowledge of the TSM v5.4, identify features to best address the customer requirements so that an appropriate TSM solution is designed. With emphasis on performing the following steps:
1. Gather customer requirements.
2. Obtain knowledge of IBM TSM v5.4 server features.
3. Identify TSM v5.4 server features which meet customer requirements.
4. Recommend appropriate TSM v5.4 server and client features.


10. Given the customer's hardware, total amount of data to be saved, percentage of daily change rate for the data, the network connectivity available, and policy recommendations, evaluate the infrastructure and requirements, so that TSM backup methods for client data can be recommended. With emphasis on performing the following steps:
1. Determine customer's available hardware.
2. Identify total amount of data to be saved.
3. Identify percentage of data that is changed daily.
4. Determine network connectivity and protocols available.
5. Review TSM policy recommendations for client servers.


11. Given the SLAs, design requirements, network infrastructure, amounts of data, and types of data, determine TSM storage, feature and database configuration so that the number and location of TSM server instances in a particular design is planned.

Interpret network infrastructure to determine where it would be appropriate to place TSM servers. With emphasis on performing the following steps:
1. Determine the number of copy pools and versions required in TSM to meet design requirements.
2. Determine the features of TSM to be used to meet design requirements.
3. Estimate the size of TSM server databases in the environment.


12. Given customer requirements, knowledge of hardware components and a basic knowledge of TSM design, identify appropriate hardware components needed so that an appropriate TSM solution can be determined. With emphasis on performing the following steps:
1. Gather customer requirements.
2. Obtain knowledge of hardware characteristics.
3. Obtain a basic knowledge of TSM solution design.
4. Apply solution design and hardware component knowledge to customer requirements. @Recommend appropriate hardware to implement the TSM solution.

Section 2: Installation

1. Given the network and hardware that meet requirements for TSM, determine and verify the configuration of existing hardware, so that TSM software can be installed and configured. With emphasis on performing the following steps:
1. Verify latest TSM 5.4 system requirements on the Tivoli support Web site.
2. Ensure that the required operating system is installed.
3. Ensure that the required browser is installed.
4. Test the system for network connectivity.
5. Verify disk and volume or directory space requirements are set up correctly.
6. Verify characteristics of tape device and verify that it is set up correctly.


2. Given a correctly set up system and network which meet the requirements, and access to the TSM code, follow the documented TSM server installation steps for Windows so that the TSM server is installed on the system. With emphasis on performing the following steps:
1. Read appropriate documentation and Support Flashes on the IBM Web site.
2. Insert TSM server CD or run downloaded code.
3. Select demonstration language.
4. Click Install Products.
5. Select TSM server.
6. Accept License Agreement.
7. Select setup type (Complete or Custom).
8. Click Install in the Ready to Install the Program window.
9. Click Install.
10. When the Install Shield Wizard Completed dialog appears, click finish.


3. Given a correctly set up system and network which meet the requirements, and access to the TSM code, follow the documented TSM server installation steps for AIX so that the TSM server is installed on the system. With emphasis on performing the following steps:
1. Read appropriate documentation and Support Flashes on the IBM Web site.
2. Log in as root user.
3. Insert TSM server CD or run downloaded code.
4. In the Common Desktop Environment, access SMIT in the System_Admin folder of the Application Manager and make selections according to the level of your AIX operating system
5. Click the SMIT icon and select Software Installation and Maintenance.
6. List software to install.
7. Set both Automatically Install Required Software and Accept New License Agreement to Yes.
8. Select the file sets you want to install.
9. If you are working in a language other than US English, you must also install your specific language pack in addition to the required U.S. English language pack.
10. Click Install.
11. Exit SMIT when the installation is complete.


4. Given that the environment requirements are met and the TSM server is correctly installed, work through the Install Products dialog so that the license files are installed. With emphasis on performing the following steps:
1. From the Install Products dialog, click Tivoli Storage Manager Server Licenses.
2. In the Setup Type dialog, select Complete or Custom.
3. In the Ready to Install the Program window, click Install.
4. When the Install Shield Wizard Completed dialog appears, click Finish.


5. Given that the environment requirements are met and the TSM server is correctly installed, work through the Install Products dialog so that the language packs are installed. With emphasis on performing the following steps:
1. From the Install Products dialog, click Tivoli Storage Manager Server Language Packs.
2. Select the appropriate language to install.
3. Click Install.


6. Given that the environment requirements are met and the TSM server is correctly installed, work through the Install Products dialog so that the device drivers are installed. With emphasis on performing the following steps:
1. From the Install Products dialog, click Tivoli Storage Manager Device Driver.
2. Complete the Customer Information Panel.
3. In the Setup Type dialog, select Complete or Custom.
4. In the Ready to Install the Program window, click Install. When the Install Shield Wizard @Completed dialog appears, click Finish.


7. Given that the environment requirements are met and the TSM server is correctly installed, perform the installation steps for the Integrated Solutions Console so that the Integrated Solutions Console is operating. With emphasis on performing the following steps:
1. Insert the Integrated Solutions Console CD into your CD drive.
2. Start one of the installation wizards and follow the instructions.
3. Check the box to accept the license agreement.
4. Change the Integrated Solutions Console user ID and password.
5. Verify installation by accessing the console through a supported Web browser: http:// :8421/ibm/console.


8. Given that the environment requirements are met and the TSM server and the Integrated Solutions Console are correctly installed, perform the installation steps so that the TSM Administration Center can manage the Tivoli Storage Manager servers. With emphasis on performing the following steps:
1. Start the Tivoli Storage Manager Version 5.4 servers.
2. Give each server a unique name.
3. Use the Administration Center CD or image to install the Administration Center on the same system as the Integrated Solutions Console.
4. Start one of the installation wizards and follow the instructions.
5. Check the box to accept the license agreement.
6. Verify installation by accessing the console through a supported Web browser: http:// :8421/ibm/console.
7. Add connections for all the Tivoli Storage Manager servers managed by the Administration Center.


9. Given a correctly installed LVSA, enable OFS and IMAGE backup options so that OFS and IMAGE type backups can be performed on a correctly installed TSM BA client. With emphasis on performing the following steps:
1. Determine which drives will need to be backed up using Image Backup.
2. Start the client installation Wizard.
3. In the “Setup Type” panel, select the “Custom” radio button.
4. In the “Custom Setup” panel select “Image Back up” and “Open File Support”.
5. Click the “Next” button. Then click the “Install” button.
6. Monitor Installation.
7. If failure, review TSM error pop up dialog box to determine error.
8. View the install Wizard Completed pop up Box and verify successful install.


10. Given a correctly installed BA Client, implement and configure JBB so that file systems are backed up and data is sent to the server. With emphasis on performing the following steps:
1. Determine which file system and files to use JBB back-up.
2. Determine where to put the directory, where the journal database files will be written.
3. Determine max size of the journal DB.
4. Determine user notification filters.
5. Determine any security options (Account that will has permissions to activate JBB).
6. Start the TSM BA Client GUI.
7. Click on the “Utilities” menu item and select “Setup Wizard”.
8. Check the box next to “Help me configure the TSM Journal Engine”.
9. Select “Install a new TSM Journal Engine”.
10. Step through the rest of the setup Wizard to configure all JBB parameters.
11. Start the Journal Service.
12. Perform an incremental backup to activate JBB.
13. Perform another incremental backup to very JBB has been activated and a JBB backup was performed.
14. View the JBB DB to verify data is available to the server.


11. Given that the operating system and TSM server are running, run the setup wizard selecting the appropriate options so that the TSM Client Options and Administrative client are installed and functioning correctly. With emphasis on performing the following steps:
1. Start the client GUI installation program.
2. In the “Setup Type” panel, select the “Custom” radio button.
3. In the “Custom Setup” panel select “Administrative Client Command Line files”.
4. Click the “Next” button. Then click the “Install” button.
5. Monitor installation.
6. If failure, review TSM error pop up dialog box to determine error.
7. View the install Wizard Completed pop up Box and verify successful install.
8. Open the Administrative command line Client and log on to the TSM Server.


12. Given a working TSM environment, install the Storage Agent and configure TSM server and client, so that LAN-free backups can be performed. With emphasis on performing the following steps:
1. Configure the TSM server (library manager or database server)
2. Define domain that includes a LAN-free Storage pool
3. Install storage agent software for each LAN-free client
4. Define storage agent on server (using “define server” command)
5. Customize the file dsmsta.opt
6. Configure the storage agent using “dsmsta setstorageserver” this is usually done via creating a script.
7. Inspect the resulting device configuration file (dev.cfg)
8. Define paths to storage agent drives on the server
9. Register node on TSM server, and assign it to the domain which goes directly to the @LAN-free tape storage pool
10. Set up TSM client with the correct LAN-free options
11. Enablelanfree yes
12. Lanfreecommmethod tcpip|namedpipe|sharedmem
13. Lanfreetcpserv xyz.sanjose.ibm.com
14. Lanfreetcpp 1500
15. Lanfreeshmport 1580
16. Run TSM server command “Validate Lanfree” to validate LAN-free setup was successful.
17. If the validation test fails review log files.


13. Given an existing TSM server and operational reporting requirements, install and configure the TSM management console and operational reporting so that reports can be sent to appropriate TSM management staff. With emphasis on performing the following steps:
1. Interpret reporting requirements and map them to TSM Operational reporting.
2. Install the TSM Console.
3. Configure Operational Reporting Daily Reports to run against your TSM servers.
4. Configure Operating Reporting e-mails and events to be sent to administrators covering failures and other pertinent data.

Section 3: Configuration

1. Given TSM server is installed, modify the dsmserv.opt and issue server option set commands so that server options are set appropriately. With emphasis on performing the following steps:
1. Configure options in dsmserv.opt which are appropriate to a customer's environment.
2. Configure options using server set commands which are appropriate to a customer's environment.


2. Given a correctly configured TSM server environment, a correctly configured Integrated Solutions Console and an Internet connection, add a TSM server connection to the Administration Center to provide centralized access to the TSM server. With emphasis on performing the following steps:
1. Log on to Internet browser.
2. Navigate to ISC Web page.
3. Select Storage Devices.
4. Select Add Server Connection . . . option in Select Action box.
5. Provide server connection information and select OK.


3. Given a working TSM environment, TSM client options file and knowledge of customer environment, configure client and server security-related options so that TSM server and client operates in a custom security designed environment. With emphasis on performing the following steps:
1. Determine security requirements before installing TSM server client.
2. Determine if a firewall will be needed.
3. Determine who will be performing backup.
4. Determine if password encryption be used.
5. Determine is SSL a requirement.
6. Determine if the client or the server be behind a proxy server or firewall.
7. Determine if TSM Ports need to be turned on or turned off for proper operation.
8. Determine your environment Allow only admin backup and restores over certain ports.
9. Determine where passwords files need to be stored ( passworddir).
10. Determine retention policy as related to security.
11. Determine how to preserve file dates related to security.


4. Given the customers hardware, media type available, network connectivity being used, policy recommendations, and the TSM Commands and processes necessary, configure tape library, drives and device class so that the library is ready for use. With emphasis on performing the following steps:
1. Determine customer's hardware available.
2. Identify media types available with customer's hardware.
3. Identify Operating Systems to be used with hardware.
4. Determine network connectivity and protocols available.
5. Review TSM policy recommendations for client servers.
6. Configure library, drives, path and device classes.


5. Given a functioning TSM server, examine number of files to be backed up, so that appropriately sized database and log volumes can be created. With emphasis on performing the following steps:
1. Determine how many files will be backed up, and multiply that by 400 bytes for initial, 200 for each copy (for example, copypool) and 200 for each addition version in a primary.
2. Define database volumes (most TSM databases are limited to 100GB for performance).
3. Define log volumes (size limit is 13 GB).
4. Determine whether to select option to automatically create DB volumes as needed.
5. Determine whether to select option to automatically create Log volumes as needed.


6. Given a functioning TSM server and sufficient storage space, define a primary storage pool so that it is configured and ready for use. With emphasis on performing the following steps:
1. Determine what device class to use
2. Determine what type of storage pool to create.
3. Determine a name for the storage pool
4. Give the pool a max scratch parameter.
5. Set the access mode.
6. Set the nextinchain.
7. Set migration threshold.
8. Specify number of migration processes.


7. Given a functioning TSM environment where client data has been backed up to the primary storage pools, configure copy storage pools, so that primary storage pool backups can be processed. With emphasis on performing the following steps:
1. Determine which primary pool the copypool will be created for.
2. Determine the format of the primary pool as it must be the same data format as the source storage pool (NATIVE, NONBLOCK, or any of the NDMP formats for a regular copy storage pool).
3. Run define stgpool command providing name of pool and appropriate parameters.

Specify the device class
Specify the pooltype as copy
4. Determine if you will be collocating the data in the copy storage pool.
5. Specify the access mode, readonly, readwrite, or unavailable.
6. Specify the maxscratch value.
7. Set reclamation threshold.
8. Set reusedelay.
9. Set offsite reclaim limit to specify the number of reclamation processes allowed.
10. Add volumes.


8. Given an installed TSM server environment, configure active-data pools so that storage pools are designed and configured appropriately. With emphasis on performing the following steps:
1. Determine appropriate use for active-data pools in the TSM solution.
2. Determine where active-data pools will be stored in the TSM solution.
3. Determine which TSM clients will use active-data pools.
4. Log on to Internet browser.
5. Navigate to ISC Web page.
6. Select Storage Devices.
7. Select TSM Server and choose View Storage Pools option in the Select Action box.
8. In newly opened Storage Pool window, select Create a Storage Pool.
9. Enter storage pool information (specifying Sequential Access and Active Data) and select OK.
10. Complete configuration wizard.


9. Given a functioning TSM server and client, and an existing policy domain and policy set, create a management class so that backup and archive copy groups can be added. With emphasis on performing the following steps:
1. Determine for which policy domain and policy set you will create the management class.
2. Use the define mgmtclass command, specifying the policy domain, the policy set, and the name of the management class.


10. Given multiple TSM server instances, configure enterprise management and server-to-server communications so that TSM policy and objects are standardized and TSM administration is centralized. With emphasis on performing the following steps:
1. Determine whether enterprise management is appropriate for a given solution.
2. Configure server-to-server communications.
3. Configure TSM objects to be centrally managed using enterprise management.




11. Given an existing TSM server, SAN or LAN infrastructure, and a supported NDMP device, install and configure TSM support for the NDMP device so that the device can be backed up and restored. With emphasis on performing the following steps:
1. Determine the location of the NAS backups.
2. Set up the tape library for TSM operations.
3. Configure TSM policy and Storage Pools for NDMP operations.
4. Schedule the NDMP backups.


12. Given a correctly installed TSM server, configure TSM client options so that the TSM client backup-archive functions are working properly. With emphasis on performing the following steps:
1. Determine what dsm.opt options are appropriate
2. Launch the TSM client GUI or JAVA GUI.
3. From the Utilities menu, select Setup Wizard. This will launch the Tivoli Storage Manager Client Configuration Wizard.
4. On the first panel of the Tivoli Storage Manager Client Configuration Wizard, make sure Help me configure the TSM Backup Archive Client is selected.
5. Follow the prompts to finish creating your options file. Most options can be set up using the Setup Wizard.
6. include/exclude
7. client communications
8. performance tuning
9. Alternatively Options can set manually by editing the DSM.opt file (Windows) DSM.SYS and DSM.OPT (AIX).


13. Given a correctly installed and configured TSM environment, install and configure the TSM backup-archive client in the cluster environment so that Cluster volumes can be backed up successfully. With emphasis on performing the following steps:
1. Verify Cluster environment.
2. Identify the cluster group/s to manage.
3. Determine where backup operations should be performed (for example, Which node all nodes).
4. Register backup-archive client node definitions on the Tivoli Storage Manager Server for each cluster group.

Define the Domain option as required.
5. Configure the Client Options file (DSM.OPT) for each cluster group. (for example, cluster yes ). The DSM.opt file must reside on the shared volumes. Use the Cluster name for the TSM node name.
6. Validate the setup on each node.
7. On the Administrative command line (on the TSM client machine) issue command

dsmc query session
8. Enter password if prompted
9. Enable Tivoli Storage Manager web client to access the Cluster environment.
10. Edit the DSM.opt file as required
11. Set up any scheduling for cluster node backup.


14. Given a correctly installed and configured TSM environment, configure the BA client so that files are backed up using adaptive subfile backup. With emphasis on performing the following steps:
1. Configure the server to allow this type of backup

On the server issue: SET SUBFILE CLIENT
2. Set the subfilebackup, subfilecachepath and subfilecachesize options in your client options file “dsm.opt
3. set |the subfilebackup option to yes (subfilebackup yes)
4. subfilecachepath (/mydir/cachedir)
5. subfilecachesize (500M)
6. Add an exclude.dir option to your client options file (dsm.opt), which excludes the directory containing the subfile cache information.
7. Exclude.Dir (/mydir/cachedir)
8. Perform an incremental backup.
9. Verify backup completed.
10. Change a couple file’s data this will also change the size.
11. Perform a second incremental backup.
12. Verify only changes to files in step 6 were backed up.


15. Given a functioning TSM environment, configure Disaster Recovery Management, so that the server and the client data can be recovered in the event of a disaster. With emphasis on performing the following steps:
1. Determine which storage pools will be managed by disaster recovery manager.
2. Determine which copy storage pools will be managed by disaster recovery manager.
3. Set the identifier for replacement volumes using the set drmplanvpostfix command.
4. Specify a prefix for the names of the recovery instructions source files in the recovery plan using the set drminstrprefix command.
5. Specify a prefix to the path name of the recovery plan file using the set drmplanprefix command.
6. Set the number of days after creation that a disaster recovery plan file stored on a target server will expire, using the set drmrpfexpiredays command.
7. Create recovery instructions files.
8. Use the define machine command with adsmserver=yes to define machines to be recovered, their location, and the priority of recovery.
9. Issue the define machnodeassociation to associate one or more client nodes with a machine.
10. Issue the insert machine command to add machine characteristics and recovery instructions to the database.
11. Use define recoverymedia command to specify bootable media needed to reinstall the Operating system of a client machine, and associate the machines with media.
12. Use the query drmstatus command to verify the status of your plan.
13. Use the set drmcmdfilename c:\drm\orm\exec.cmd to set the file name where executable commands can be stored.
14. Use the query drmedia or move drmedia to generate executable commands and store them in a file.


16. Given a TSM environment with Disaster Recovery Management in use, configure tape rotation, so that media is utilized efficiently. With emphasis on performing the following steps:
1. Use set commands to change default states or locations, if desired, for offsite recovery media management.
2. Determine state of recovery media using the query drmedia command.
3. Mark the volumes as unavailable to Tivoli Storage Manager and give them to the courier.
4. Indicate the movement of volumes whose current state is MOUNTABLE by issuing the following command: move drmedia * wherestate=mountable.
5. Issue the prepare command after the move drmedia command has been issued to create your Disaster Recovery Plan file.
6. Send all DR media, and plan file in softcopy and hardcopy, offsite.
7. For all volumes in the NOTMOUNTABLE state, DRM updates the volume state to COURIER and the volume location according to the SET DRMCOURIERNAME. If the SET command has not yet been issued, the default location is COURIER.
8. When the vault location confirms receipt of the volumes, issue the MOVE DRMEDIA command in the COURIER state.
9. To display a list of volumes that contain valid data at the vault, issue the following command: query drmedia wherestate=vault.
10. Issue the query drmedia * wherestate=vaultretrieve command to determine non-virtual volumes that can be returned from the vault. Update the location as needed until the volumes are returned.
11. Update the state of these tapes and check them into the library.

Section 4: Performance Tuning and Problem Determination

1. Given an existing TSM server with a tape drive, label and check in tapes so that the TSM server has scratch volumes. With emphasis on the following steps:
1. Label Tape media for the TSM server.
2. Check-in tape media to the TSM server.


2. Given a correctly functioning Administration Center and client machine, navigate through the Policy Domains and Client Nodes wizard so that client nodes can be accessed and managed with the TSM Administration Center. With emphasis on the following steps:
1. Log on to the TSM Administration Center.
2. In the server’s Policy Domains table, click the name of a domain.
3. In the domain’s properties portlet, click Client Nodes.
4. In the Client Nodes table, click Select Action, select Create a Client Node.
5. Enter the client name.
6. Enter contact information.
7. Enter the client’s Web address
8. Select a client option set.
9. Select a client schedule.
10. Verify the client nodes can be accessed by the Administration Center.


3. Given a working TSM environment where there is the need to have one node restore data backed up from another node, create a node access so that one node now has been granted the authority to restore files for another specified node. With emphasis on the following steps:
1. Issue the query access command to determine node access.
2. Set up server to allow client to client node access.
3. Use the GUI to create a node access list.
4. Alternatively on the command line client you can use the set access command.


4. Given a correctly installed and connected TSM environment, perform backup so that successful installation and configuration of the TSM environment can be confirmed. With emphasis on the following steps:
1. Start the TSM backup archive client GUI.
2. Click Backup.
3. Select objects to be backed up.
4. Select type of backup (selective, incremental,)
5. Click Backup.
6. Monitor backup progress.
7. Review the detailed status report and error code to confirm backup completion.
8. If failure, review TSM error log to determine error.


5. Given a correctly installed and connected TSM environment, perform a file restore so that successful installation and configuration of the TSM environment can be confirmed. With emphasis on the following steps:
1. Start the TSM backup archive client GUI.
2. Click Restore.
3. Identify files to restore.
4. Determine version of the file to restore.
5. Select restore options.
6. Click Restore.
7. Monitor progress.
8. Review the detailed status report and error code to confirm restore completion.
9. If failure, review TSM error log to determine error.


6. Given a correctly installed and connected TSM environment, perform archive so that successful installation and configuration of the TSM environment can be confirmed. With emphasis on the following steps:
1. Start the TSM backup-archive GUI.
2. Click Archive.
3. Select objects to be archived.
4. Enter description.
5. Select archive options
6. Click Archive.
7. Monitor archive progress.
8. Review the detailed status report and error code to confirm archive completion.
9. If failure, review TSM error log to determine error.


7. Given a correctly installed and connected TSM environment, perform a retrieve of an archived file so that successful installation and configuration of the TSM environment can be confirmed. With emphasis on the following steps:
1. Start the TSM backup archive client GUI.
2. Click Retrieve.
3. Identify files to retrieve.
4. Select retrieve options.
5. Determine destination of the archived file.
6. Click Retrieve.
7. Monitor progress.
8. Review the detailed status report and error code to confirm restore completion.
9. If failure, review TSM error log to determine error.


8. Given the customers policy requirements, client backup and archive data volume, available storage pool size being used and the amount of TSM Server time available for maintenance, create administrative schedules so that server maintenance is automated. With emphasis on the following steps:
1. Identify media types available with customer's hardware.
2. Identify client backup and archive volume and storage pool sizes.
3. Review TSM policy recommendations for client servers.
4. Determine customers backup time available and TSM server maintenance time available.


9. Given a correctly configured TSM server environment, configure activity log retention option so that the activity log is automatically pruned. With emphasis on the following steps:
1. Query the current value for activity log retention.
2. Determine the change value.
3. Update the value for activity log retention.


10. Given the customers hardware and media types available, database size and estimated threshold, configure TSM database backup trigger so that database is automatically backed up. With emphasis on the following steps:
1. Identify media types available with customer's hardware.
2. Determine TSM Server maintenance time available.
3. Define backup trigger.
4. Set logmode to rollforward.


11. Given a functioning TSM server, set migration thresholds, so that the flow of data through the storage pool is optimized. With emphasis on the following steps:
1. Determine appropriate migration thresholds for your storage pools.
2. Set migration threshold on the storage pool using the HIGHMIG and LOWMIG options on the DEFINE STGPOOL or UPDATE STGPOOL commands identifying a high threshold, a low threshold, and the next storage pool in the chain.
3. Optionally use the update stgpool command to manually force migration.
4. Use the MIGDELAY to delay migration a specified number of days.


12. Given a correctly installed BA Client, implement and configure a schedule so that files are backed up automatically to insure that data is available as needed. With emphasis on the following steps:
1. Determine what needs a scheduled backup, archive, restore and retrieve.
2. Determine how often files need to be backed up, archived, retrieved or restored.
3. Determine what kind of schedule is required (polling or prompted).
4. Define a policy domain on the server.
5. Assign the TSM client (that is scheduled) to the policy domain just defined.
6. Define a schedule name on the Server.
7. Define an association on the server between the TSM client node and the schedule name just created.
8. Invoke the schedule.
9. Verify Schedule log file has all schedule occurrences listed.


13. Given a correctly installed TSM environment, generate a backup set then perform a query of the backupset so that the correct information was generated. With emphasis on the following steps:
1. Determine what files need to be included in a backup set.
2. Determine location for storing the backup set. (portable media, TSM server Client workstation)
3. Create/define a device class.
4. Perform an incremental backup/selective backup of the files to be included in the backupset.
5. Generate a backupset on the server.
6. Assign the backupset to the device class.
7. Assign name and description.
8. Assign retention limit.
9. Specify location of backupset (default is server).
10. Issue a Query Backupset command on the server (or client admin command line) to verify backup set got properly generated.
11. Restore Backupset.


14. Given a correctly configured TSM server environment, review messages from the TSM server activity log so that errors and issues in the TSM environment can be detected. With emphasis on the following steps:
1. Select Server Maintenance in left column.
2. Select TSM Server and choose Server Properties option in the Select Action menu.
3. Select Activity Log Tab.
4. Update filter information and select update table.
5. Review messages in the resulting table.


15. Given a TSM environment with backup and recovery events scheduled, monitor these events so that the administrator in charge is aware of the status of all backup and recovery events. With emphasis on the following steps:
1. Verify that drives are online.
2. Verify that database and recovery log volumes are online and synchronized.
3. Check the status of disk volumes.
4. Check that scratch volumes are available.
5. Check the access state of the tape volumes.
6. Check database and recovery log statistics.
7. Verify that scheduled database backups completed successfully.
8. Check the activity log for error.
9. Install and use Operational Reporting to monitor events.


16. Given a Tivoli Storage Manager environment where Disaster Recovery Management is completely configured and in use, perform the proper steps, in the correct order, so that a complete Disaster Recovery Plan file is generated. With emphasis on the following steps:
1. Complete all client backups.
2. Complete all storage pool backups.
3. Complete the database backup.
4. Run the move drmedia command to update the DR plan and checkout media.
5. Run the prepare command to generate the DR Plan file.




17. Given a Tivoli Storage Manager environment where Disaster Recovery Management is completely configured and in use, and files are being regularly sent off-site, perform a test of the DR Plan so that the recoverability of the server and client files can be verified. With emphasis on the following steps:
1. Deliver DR materials to a designated recovery site.
2. Break out the disaster recovery plan and the DR media and follow the instructions, testing any scripts for automation of recovery where possible.
3. If instructions are insufficient or data is not recoverable, take steps to correct these issues and try the test again.
4. Continue testing and correcting until you successfully recover the TSM server, storage pools, and client data.
5. Conduct a lessons learned discussion and update DR Plan.
6. Create a schedule for testing the Disaster Recovery Plan at least once or twice each year, and allow time during each test to update the plan so until a successful recovery is achieved.




18. Given an existing TSM server, administrative client, and Operational Reporting, extract capacity planning information so that information on current capacity usage for the TSM server can be determined. With emphasis on the following steps:
1. Determine information from the TSM environment which can help an organization do capacity planning.
2. Extract capacity planning information from the summary table and TSM Operational Reporting.
3. Produce Capacity Management Reports which can help size the TSM server.


19. Given a configured TSM server, policy definitions for administrators, nodes and policies, execute TSM commands so that server information and data can be exported and imported. With emphasis on the following steps:
1. Identify TSM Policy definitions.
2. Identify system administrators.
3. Identify client nodes.
4. Identify policy domains.
5. Issue import/export command.

Section 5: Administration

1. Given the customers hardware, TSM maintenance level, configured Operating system, correct hardware device drivers, and current firmware levels, validate the installation process so that installation problems are detected. With emphasis on the following steps:
1. Identify operational status of customer's hardware and operating system.
2. Identify TSM Server availability.
3. Review TSM activity log, Client event log, OS error logs.
4. Identify Device drivers and firmware levels.


2. Given a correctly configured TSM server environment, navigate to the directory where TSM instance is installed so that logs can be reviewed to aid in problem determination. With emphasis on the following steps:
1. Log on to the server hosting the TSM server software instance.
2. Navigate to the installation directory for the server instance.
3. Review the various logs for this TSM server instance.


3. Given a correctly configured TSM server environment, review error messages from the TSM server activity log so that corrective action can be taken. With emphasis on the following steps:
1. Query the activity log for the period of interest.
2. Identify errors, warnings and suspicious items.
3. Determine the cause aforementioned items.
4. Determine corrective actions to take.


4. Given an issue which needs to be resolved, determine the appropriate TSM resources so that a solution can be provided. With emphasis on the following steps:
1. Understand resources available to help diagnose issues.
2. When an issue occurs in the environment, determine where to look for help in discovering the solution.


5. Given the customers hardware, network environment, and Operating system, determine the cause of failure or lack of connectivity so that corrective action can be taken. With emphasis on the following steps:
1. Identify operational status of customer's hardware and operating system.
2. Identify TSM Server availability.
3. Review TSM activity log, Client event log, OS error logs.
4. Verify TSM communication-related information in the options file.
5. Identify communication devices and connectivity methods.


6. Given the customers hardware and Operating system, determine the cause of failure of a specific storage-related device so that the failure can be corrected. With emphasis on the following steps:
1. Identify operational status of customer's hardware and operating system.
2. Identify TSM Server availability.
3. Review TSM device class, tape drive, library configuration and attached devices.
4. Review TSM activity log, Client event log, OS error logs.


7. Given the customers available hardware and connectivity and TSM Server availability, check the TSM Activity log, and Client error and schedule logs, to locate messages and errors so that the cause of backup failures can be corrected. With emphasis on the following steps:
1. Identify operational status of customer's hardware and operating system.
2. Identify TSM Server availability.
3. Review TSM activity log, Client event log, OS error logs and client schedule logs.
4. Correct issues with client backups.


8. Given a basic performance issue in TSM, adjust TSM server and client parameters so that better performance is achieved and client SLAs are met. With emphasis on the following steps:
1. Investigate current performance of the TSM client and server.
2. Determine where performance falls outside of agreed upon SLAs.
3. Make changes to the TSM client and server solution to improve performance to meet SLAs, including changes to the dsmserv.opt, dsm.opt, and dsm.sys.


9. Given a TSM server, determine issues with bad or corrupt media and attempt to repair or restore them so that the faults with the media are corrected. With emphasis on the following steps:
1. Determine if any tape of disk media in the TSM server is bad or corrupted.
2. Attempt to recover or repair the media with the audit vol command.
3. If media is destroyed, attempt to restore the data with a restore vol or restore pool command.


10. Given a Tivoli Storage Manager environment where the amount of tape media being used is increasing faster than the increase in the amount of data being stored, determine the issues that are causing the inefficient use of media and correct it so that tape rotation is regulated and media usage is optimized. With emphasis on the following steps:
1. Verify that all collocated client data really needs to be collocated.
2. Run an audit lib to make sure the database information on the volumes is correct.
3. Ensure that tape reclamation and expiration are running regularly.
4. Check to see if data retention is on where it should be off.
5. Check the reclamation threshold to see if it’s appropriate.
6. Check the reusedelay to see if it’s set too high.
7. Check the offsite reclaim limit for the storage pool to see if it’s too low.
8. Check the RETMIN parameter in the archive copy group.
9. Check the RETVER parameter on the archive copy group also.
10. Verify deletion hold.
11. Clean tape heads regularly to keep media from wearing out too soon, thus keeping tape media in the rotation longer.