TM 5021 Inst

IBM Tivoli Storage Manager 5.
5 Implementation and Administration

Instructors Training Guide
S150-2877-00
March 2008
Copyright Notice Copyright 2008 IBM Corporation, including this documentation and all software. All rights reserved. May only be used pursuant to a Tivoli Systems Software License Agreement, an IBM Software License Agreement, or Addendum for Tivoli Products to IBM Customer or License Agreement. No part of this publication may be reproduced, transmitted, transcribed, stored in a retrieval system, or translated into any computer language, in any form or by any means, electronic, mechanical, magnetic, optical, chemical, manual, or otherwise, without prior written permission of IBM Corporation. IBM Corporation grants you limited permission to make hardcopy or other reproductions of any machine-readable documentation for your own use, provided that each such reproduction shall carry the IBM Corporation copyright notice. No other rights under copyright are granted without prior written permission of IBM Corporation. The document is not intended for production and is furnished as is without warranty of any kind. All warranties on this document are hereby disclaimed, including the warranties of merchantability and fitness for a particular purpose. Note to U.S. Government UsersDocumentation related to restricted rightsUse, duplication or disclosure is subject to restrictions set forth in GSA ADP Schedule Contract with IBM Corporation. Trademarks The following are trademarks of IBM Corporation or Tivoli Systems Inc.: IBM, Tivoli, AIX, Cross-Site, NetView, OS/2, Planet Tivoli, RS/6000, Tivoli Certified, Tivoli Enterprise, Tivoli Ready, TME. In Denmark, Tivoli is a trademark licensed from Kjbenhavns Sommer - Tivoli A/S. Microsoft, Windows, Windows NT, and the Windows logo are trademarks of Microsoft Corporation in the United States, other countries, or both. UNIX is a registered trademark of The Open Group in the United States and other countries. C-bus is a trademark of Corollary, Inc. in the United States, other countries, or both. Java and all Java-based trademarks are trademarks of Sun Microsystems, Inc. in the United States, other countries, or both. Lotus is a registered trademark of Lotus Development Corporation. PC Direct is a trademark of Ziff Communications Company in the United States, other countries, or both and is used by IBM Corporation under license. ActionMedia, LANDesk, MMX, Pentium, and ProShare are trademarks of Intel Corporation in the United States, other countries, or both. SET and the SET Logo are trademarks owned by SET Secure Electronic Transaction LLC. For further information, see http://www.setco.org/aboutmark.html. Other company, product, and service names may be trademarks or service marks of others. Notices References in this publication to Tivoli Systems or IBM products, programs, or services do not imply that they will be available in all countries in which Tivoli Systems or IBM operates. Any reference to these products, programs, or services is not intended to imply that only Tivoli Systems or IBM products, programs, or services can be used. Subject to valid intellectual property or other legally protectable right of Tivoli Systems or IBM, any functionally equivalent product, program, or service can be used instead of the referenced product, program, or service. The evaluation and verification of operation in conjunction with other products, except those expressly designated by Tivoli Systems or IBM, are the responsibility of the user. Tivoli Systems or IBM may have patents or pending patent applications covering subject matter in this document. The furnishing of this document does not give you any license to these patents. You can send license inquiries, in writing, to the IBM Director of Licensing, IBM Corporation, North Castle Drive, Armonk, New York 10504-1785, U.S.A.
Course Revision History
Introduction
The Tivoli Worldwide Education Course Development team, IBM Tivoli Support and Services, the GEO Delivery Managers, and instructors from all three geographical regions have been involved in the design, development, and review of this course. This is an update of IBM Tivoli Storage Manager 5.4 Implementation and Administration, Part One.
General Revisions to this Course
Students Training Guide

The course title was changed. All materials have been reviewed for grammatical and consistent format errors and corrected. The Instructor fix requests received from the GEO Delivery Managers were evaluated and applied where appropriate. New slide templates have been applied. Screen captures have been updated for TSM 5.5. Graphics have been updated. TSM 5.5 features were incorporated (including concurrent access to storage pool with device type of FILE, TCP/IP version 6 support, Secure Sockets Layer option, support for long file names, the auditlogging option, AIX JFS2 snapshot integration, and changes in encryption support). Linux requirements and installation overview added. See the Detailed Revisions for unit-by-unit changes.
Instructors Training Guide

New Instructor Notes were added.
Detailed Revisions
There are recorded presentations of the changes to the slides on your Instructors Resources CD.
TSM 5.5 Implementation and Administration Preface Unit 1: IBM Tivoli Storage Manager Overview Unit 2: Installing IBM Tivoli Storage Manager Unit 3: Administrative Interfaces and Privileges Unit 4: Storage Media Devices Introduction
Changes from TSM 5.4 Implementation and Administration, Part One New Training Roadmap has been added.
Supported platforms were updated. Screen capture of Web page was added. Linux requirements and installation overview has been added. The query examples were chnaged to q admin and q db.
Determining element number sldie updated. Defining and updating ADP moved to Lesson 4 in Unit 10. overview and collocation od ADPs remain. Collocation section was reworked. Collocation by Groups was moved to after Collocation Volume Selection examples. Concurrent access to FILE volumes was added. Slide or active-data pool commands was corrected and slide with define stgpool command syntax was added.
Unit 5: Managing Storage Pools and Storage Pool Volumes
Query OCCupancy command added

Copy domain and update domain commands added. These commands will be used in the active-data pool exercises in Unit 10. Server-to-server exports can be suspended and restarted was added.
Unit 6: Policy Management
IBM Tivoli Storage Manager 5.5 Implementation and Administration
Copyright IBM Corp. 2008
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
TSM 5.5 Implementation and Administration Unit 7: Customizing the TSM Database and Recovery Log Unit 8: Client Configuration
Changes from TSM 5.4 Implementation and Administration, Part One
Encryption support has been updated. TCP/IP version 6 added as a commmethod. SSL was added. Support for long object names was added. Lesson 5: Archive and Retrieve was moved to after Lesson 6: Backup and Restore Command Line. Now Backup and Restore CLI follows Backup and Restore GUI in the Studnets Guide. No changes to the Students Exercises. AIX JFS2 snapshot added. Open file support for Windows 64-bit added. File names in Restore CLI slides have been changed. Defining and updating ADP from Unit 5 is now Lesson 4. Changes to Student Exercises: new Exercise 7 Define an active-data pool with command line new Exercise 8 Update a policy domain to have an active-data pool destination with command line existing Exercise 9 (formerly exercise 7) Use the Administration Center to create a maintenance script to backup primary storage pool new Exercise 10 Perform a simultaneous write to backuppool and adpool. new Exercise 11 (optional) Use Administration Center to create a new device class, new active-data pool, and policy domain for use with the active-data pool. Solutions are not provided, only hints. The new exercises 7 and 8 will require that the students recall commands covered in Units 5 and 6.
Unit 9: Backup-Archive Client Functions
Unit 10: Protecting the Database and Storage Pools
Unit 11: Automating Operations Unit 12: Monitoring and Event Logging Appendix A Appendix B

Auditlogging and auditlogname options added.
Course Materials
The following table contains the part numbers for the course materials, along with any part numbers that are being replaced.
Item IBM Tivoli Storage Manager 5.5 Implementation and Administration Students Training Guide IBM Tivoli Storage Manager 5.5 Implementation and Administration Instructors Training Guide IBM Tivoli Storage Manager 5.5 Implementation and Administration Student Exercises for AIX IBM Tivoli Storage Manager 5.5 Implementation and Administration Student Exercises for Windows IBM Tivoli Storage Manager 5.5 Implementation and Administration Student Exercises for Linux IBM Tivoli Storage Manager 5.5 Implementation and Administration Student Resources CD IBM Tivoli Storage Manager 5.5 Implementation and Administration Instructor Resources CD IBM Tivoli Storage Manager 5.5 Implementation and Administration Classroom Setup CD
Part Number S150-2878-00 S150-2877-00 S150-2875-00
Replaces S150-2387-00
S150-2386-00 S150-2388-00 S150-2385-00
S150-2874-00
S150-2876-00
n/a
SK5T-8060-00
SK5T-7295-00
SK5T-8061-00
SK5T-7296-00
SK5T-8062-00
SK5T-7297-00
Instructor Preparation
Introduction
This section is a compilation of notes by the course developer to help others deliver IBM Tivoli Storage Manager 5.5 Implementation and Administration. It gives an overview of the course, instructions for setting up the classroom, and other information that instructors should have to make the class a success. This is an updated version of the IBM Tivoli Storage Manager 5.4 Implementation and Administration, Part One course. The title has changed as well as the version number.
Course Components
The following materials and equipment are needed to deliver the training. The Instructor Kit: Instructors Training Guide Instructor Resources CD, including, printable Instructor Notes, the PowerPoint Slideshow, and recordings of the course changes, by unit. Course Setup Guide CD Student Exercises for AIX Student Exercises for Linux Student Exercises for Windows
The Student Kit, for each student: Students Training Guide Student Exercises for AIX Student Exercises for Linux Student Exercises for Windows
Student Resources CD, including documentation, RedBooks, PowerPoint presentation on Operational Reporting, Field Guides, Technical Notes, and policy planning worksheets.
Classroom Setup Instructions

Follow the instructions on the Classroom Setup Guide on the Classroom Setup CD. Files needed for backup exercises are on the Classroom Setup CD, as well.
PC Projection Unit
Much of the day is spent on a lengthy slide presentation delivered with a PC-based projection unit. The make and operation of the projection system is apt to vary among classrooms, but there are some common considerations that need to be taken into account. First, the slides are best viewed on a typical 4 x 4 screen. This means arranging for the projector to be a good distance from the screen, not on the instructor's podium where an overhead project might belong. Most projectors have remote controls, so it is not necessary to place it in reach of the instructor. (It behooves the instructor to get in some practice operating the projector from the remote prior to class.) Most projectors can be adjusted for different graphics resolutions and screen sizes. Some experimentation prior to class may be required to get the best results. It is necessary to project the entire area of the slide, since some utilize the whole frame. Many projection systems cannot support video output to the projector and the PC monitor at the same time. This means the instructor must be prepared to deliver the lecture without turning around to look at the projection screen. This is best accomplished by working from the Instructors Training Guide, which contains all the slides used in the lectures. The Instructor Notes table has room for you personal comments and reminders for delivery.
Timing Guidelines
Reasonable target times for pacing the course lecture and exercises are shown in the following table.
Unit Day 1 Unit 1 Unit 2 Unit 3 Day 2 Unit 4 Unit 5 Unit 6 Day 3 Unit 7 Unit 8 Day 4 Unit 9 Unit 10 Day 5 Unit 11 Unit 12 Appendix A Appendix B
Hours
1 2 3
1 2.5 2.5
2.5 3.5
3 3
2 2 1* 1*
* The appendices can be reduced or expanded to fit the remaining time.
Suggestions for Delivery
Audience
This course is intended for system administrators and implementers who will be responsible for implementing an IBM Tivoli Storage Manager 5.5 solution.
Required Skills/Knowledge
The following list contains the prerequisite knowledge or Tivoli product knowledge an attendee must have prior to taking the course: All students should have a working knowledge of Internet browsers. All students should have a basic understanding of client-server concepts. For classes taught on a Windows platform, the students should have the skills to navigate through Windows 2003 applications. For classes taught on a Linux platform, the students should have experience using the Linux command-line interface, allocating file system space, and connecting devices to a Linux server. For classes taught on an AIX platform, the students should have experience using the AIX command-line interface, allocating file system space, and connecting devices to an AIX server.
Demonstrations
Prompts for instructor demonstrations have been removed from the PowerPoint slide show presentation. Suggested demonstrations are in the Instructor Notes, which are included on the Instructor Resources CD. The students will not be installing the Integrated Solutions Console (ISC) due to time constraints. The demonstration of the ISC installation, as well as navigation demonstrations of the Administration Center, would be very beneficial for the students.
Student Exercises
There are three Student Exercise Guides: AIX, Linux, and Windows. These exercises have been tested successfully, by a variety of course developers, on a variety of Windows 2003, Red Hat Linux, and AIX machines. If you are having a problem during course preparation testing or in the classroom, verify the hardware and software requirements in the Course Setup Guide.
Altering the Flow of the Course

If you have a preferred delivery that differs from the design of the course, please ensure the altered sequence meets the course and unit learning objectives. As you test the lab exercises, you will note that some of the exercises depend on the previous exercises successful completion. If you change the course flow, you will need to make adjustments to the exercises. At the end of the course, have the students fill out the course evaluation.
Instructor Notes
The Instructor Notes table follows this document. A printable table of Instructor Notes is also available on the Instructor Resources CD.
Changes
The majority of the changes to this course are listed in the Revision History document. Even if you are familiar with the previous course, please review the PowerPoint slide show presentation to review the new slides and graphics.
IBM Tivoli Storage Manager 5.5 Implementation and Administration Instructor Notes
Instructor Notes for IBM Tivoli Storage Manager 5.5 Implementation and Administration March 2008 Location Topic Note Preface This course is designed to give the students the necessary skills to install and run TSM. Emphasize the use of the Administration Center in the class, because it is the preferred method of administering TSM (as requested by Development and Support). In many cases there are multiple methods or commands to perform the same function. You can share additional methods with the students. Where applicable, demonstrate the Administration Center. Preface x Suggestions in this Course Ensure the students know the Best Practices mentioned in the product documentation and in this course are suggestions based on product testing and monitoring in a variety of test and production environments. The do not override policies and requirements of their environment. .
Unit 1 1-1 Introduction This Overview includes the most basic elements of Storage Manager. Assure students that more detailed information will be provided as each subject is addressed in upcoming units. Demonstrate the backup-archive GUI.
1-15
Backup-Restore Functions
IBM Tivoli Storage Manager 5.5 Implementation and Administration This document may be reproduced for use in classroom training.
Unit 2 2-1 Topic Introduction Note Emphasize the importance of carefully reviewing all of the documentation material provided with the product before beginning an installation. The course follows the suggested installation flow: TSM Server, ISC, Administration Center. SNMP DPI You can configure the SNMP subagent to send traps to an SNMP manager, such as NetView, and to provide support for a management information base (MIB). For details about configuring SNMP for use with Tivoli Storage Manager, see the IBM Tivoli Storage Manager Administrator's Guide. The subagent communicates with the snmpd daemon, which in turn communicates with a management application. The snmpd daemon must support the DPI protocol. Agents are available on AIX . The subagent process is separate from the Tivoli Storage Manager server process, but the subagent gets the information from a server options file. When the SNMP management application is enabled, it can get information and messages from servers. TCP/IP version 6 is now supported. The students do not install the ISC in their lab exercises, due to time constraints. There are screen captures for the installation steps. Suggestion: Demonstrate the installation of the ICS while covering this unit. RSM services should be disabled. See Installation Guide.
(R)
2-5
TSM System Requirements
2-8
ISC Installation
2-17
Device DriversWindows
2-40
Web Browser
To determine JRE level, type java fullversion at OS prompt.
2-46
Query System
The query system command consolidates the output from a number of query commands with a number of SQL SELECT commands. The query commands can obtain detailed information about specific areas of the server, while the SELECT statements can produce summaries of certain key areas. In many situations it is helpful to both the TSM administrator and other support personnel to obtain an overview of the TSM installation. This is addressed by the introduction of the query system command. Commands which can be issued by administrators with various privileges are also presented; however, the detailed syntax is not discussed.
Unit 3 3-4
Topic ISC, Administration Center Introduction
Note Demonstrate opening and navigating the ISC and Administration Center.
3-8
Navigating the Administration Center
These slides show the opening of each task in the tree and the actions available for the tasks. This is a good place to do a demonstration.
3-19
Support Utility
Appendix B has tips on what to do before calling IBM Support.
3-29
Lesson 4: GUI
At this point, you enter TSM.
3-30
Backup-Archive GUI
The dsmcad process must be started (dsm or dsmj on UNIX).
3-32
Command Line
You can add the Use Command Line action to the Administration Center Favorites. Remind the students that the default Linux path is /opt, not /usr as it is with AIX.
3-32 Command Line Let the students know that the Administrative command line is invoked when executing the dsmadmc.exe program found in the baclient directory (C:\Program Files\Tivoli\TSM\baclient) The default TCP/IP port address is 1580. Trivia: Program naming convention appears to be DSM=for product code, formerly ADSM; ADM=for administrator; C=for command line.
3-32
Command Line
Experience has shown that students get confused in lab exercises with the differences between the Administrative command-line interface and the backup-archive command-line client. It is important that you make sure students understand the difference between the command-line interfaces, DSMADMC for administrative and DSMC for clients.
3-39
Administrator Authority
Refer to the IBM Tivoli Storage Manager Administrators Guide and the IBM Tivoli Storage Manager Administrators Reference for complete lists of the commands and the list of tasks that the different levels of TSM administrator privilege can perform.
3-40
Privilege Classes
There are two differences between what an administrator with restricted and unrestricted privileges can do: The unrestricted administrator can issue commands which affect all domains and pools, whereas the restricted administrator can only issue commands which affect the domain and pools to which they are authorized. The unrestricted administrator can issue all policy and storage commands, whereas the restricted administrator can only issue a subset of those commands.
Unit 4 4-4 Topic Connect a SCSI library Note For other types of libraries, such as fibre channel libraries, refer to the procedures provided by the manufacturer. Mention the A-Tape library.
4-8
Element number
Many libraries can automatically detect the element number.
4-11
Working with Media
If you define a volume explicitly with Define Vol, the volume becomes private and empty.
4-13
Labeling tapes
The use of dsmlabel is no longer a supported method now that autolabel, label libvolume, and the Administration Center can perform the function.
Unit 5 5-10 Topic Storage Destination Note If backing up a mail server, it is best to go directly to tape.
5-12
Defining Storage Pools
The devclass in the define stgpool command is the name of the previously defined devicetype TSM object.
5-17
Deleting Storage Pools and Volumes Move Data
The q content command looks to a TSM table and not to the tape cartridge.
5-19
Use the parameter reconstruct=yes with aggregates.
5-21
Concurrent Storage Pool Volume Access Automatic data Movement
New feature
5-24
New method for calculating migration thresholds for storage pools associated with sequential-access disk (FILE) devices. In previous releases of Tivoli Storage Manager, migration thresholds for storage pools associated with sequential-access disk (FILE) devices were based on volume utilization. In this release, migration thresholds are based on a percentage of the storage pools total data capacity. For example, a sequential-access disk storage pool with a capacity of 100 TB and a high migration threshold of 70% is migrated when the pool contains 70 TB of data. Mention the possible problems with aggregate migration.
5-29
Reclamation
5-30
Single Drive Reclamation Collocation Example
Check to see if students have a single drive library. If nobody has one, skip the next 2 pages. The data belonging to Client D will go to the volume with the most free space.
5-35
5-36
Collocation Example 2
The data belonging to Client D will go to the volume with the most free space.
Unit 6 6-1 Topic Introduction Note Begin to introduce the concept of having business requirements for data management or service level agreement between the client and TSM administration personnel in the IT organization.
6-10
Policy Set
Created automatically when you use the Administration Center.
6-11
Defining MC
Include-Exclude is covered in Unit 8.
6-14
Copy Group
A copy group contains the parameters regarding how to manage the data (objects) belonging to the client, how many versions of backup to keep, and how long to keep the archive data. Notice that you can specify zero, one or two copy groups in a management class. If a management class is defined with no copy groups, users will receive warning messages if they choose to bind their files to this management class. When bound to this management class, files will never be backed up or archived. However, as a precautionary measure, TSM is designed to cover this problem by using the grace retention periods for backup and archive defined in the policy domain. This chart is to be used to go through what happens as TSM is backing up a changed file every day. Use the letter A for active and the letter I for inactive. Notice on day 6, the file goes unchanged. Go through the process for each day. If possible, project slides on a writable surface. If not, draw the diagram on a writable surface. On day 1 the file is changed or created. That evening it is backed up. Ask the students if the file on TSM storage would be Active or Inactive. Answer: Active. Write the letter A under the box for backup 1 on day 1. Follow this logic through to day 4. Write the letter I on all the extra versions. Ask the students what happens on day 4 to backup version 1. Answer: It will expire, because we are only keeping three versions of the file. Cross out the versions other than the first three on days 4, 5, and 6.
6-23
Expiration, Part 1
6-24 Expiration, Part 2 This takes over where we left off in the previous slide. Fill in active and inactive under the boxes. You should have done this on the board in the previous visual. Ask the students why backup 1 on day 4 is gone. Answer: Because we are keeping only three versions based on VERExist=3. Notice that the file goes unchanged from day 5 on. Ask the students what happens to extra backup 2 and 3 and on what days. Answer: On day 33 extra backup 2 should expire. Fill in active and inactive under the boxes. Cross it off the board and write 33 by the first ?. Ask the students why, if we were keeping three versions, there is only one left. Answer: Because retainextra is set to 30 and needs to be no limit if you always want three versions. This is very important emphasize. Ask the students when the active backup will expire. Answer: It will not expire. Ask the students why backup 2 expired on day 33. Answer: It became inactive on day 3 and you add 30 days based on RETEXTRA=30. Use a story about a resume being updated daily. Then on Day 5 no more changes are made because the salary was doubled and the person was given a car as a bonus. Complete the process by erasing the file on the morning of day 4. Ask the students what happens now. Answer: Backup 3 will go inactive. Mark it on the board with the letter I. Ask the students how many extra copies will be there after the incremental backup on day 4. Verdeleted is set to 1 so we lose backups 2 and 1. Mark them out on the board. Ask the students when the only backup will expire. Answer: Around day 64. Retonly is set to 60. Now, resume.doc is expired. The employee likes the new car and decides to stay with the company, and no longer needs the resume. Point out what happens when you activate a policy set. But first review what a domain is. Ask students what goes inside a domain. Answer: Policy sets. Ask students what goes inside a policy set. Answer: Management classes. Ask students what goes inside management classes. Answer: Copy groups. With each answer write the name on the board in the visual in the appropriate box that is policy set, management class, and copy group. Ask students what happens when you activate. Answer: TSM makes a copy of the policy set, and names it ACTIVE. You cannot change the active policy set. You can change only the one from which it was activated. Ask students what is the minimum number of policy sets you can have in an active valid configuration. Answer: Two, the one you defined, and the active one.
6-25
Expiration, Part 3
6-31
Validate and Activate Policy Set
6-32 Binding MC Be sure students understand the difference between active and inactive. If time allows, walk through another expiration example.
6-39
Summary
Unit 7 7-9 Topic Recovery Log Space Note If the volumes are physically allocated on the same disk, it would be best to allocate a single volume and optional mirrors to avoid performance problems. It is not advisable to use optical storage for the database or the recovery log because of performance characteristics. Increasing the recovery log size can increase the TSM server startup time.
7-13
Estimate Recovery Log Size
Common practice is to set the recovery log size to the maximum. An alternate method is qlog f=d, backup the database, reset logconsumption.
7-13
Estimate Recovery Log Size
In both normal mode and roll-forward mode, the volume of TSM transactions affects how large you should make your recovery log. As more clients are added and the volume of concurrent transactions increases, you should extend the size of the log. In roll-forward mode you must also consider how often you perform database backups. In this mode, the recovery log keeps all transactions since the last database backup and typically requires significantly more space than is required in normal mode.
7-14
Creating Additional Volumes
Each time you define a new database or recovery log volume, you provide additional space to the database or recovery log. For performance reasons, define more than one volume for the database and recovery log, and place these volumes on separate disks to allow simultaneous access to different parts of the database or recovery log. When possible, assign each database and recovery log volume to separate disk strings, preferably on disks with different control units and channels. To protect database and recovery log volumes from media failure, you can use the mirroring feature. To use disk space efficiently, allocate a few large disk volumes rather than many small disk volumes. In this way, you avoid losing space to TSM overhead processing.
10
7-19 Mirroring TSM provides nondisruptive and immediate recovery from physical failures on database and recovery log volumes through mirroring. If a mirrored volume encounters a media failure, the server automatically places the failing volume offline and continues database operations using the mirrored copies. After the failed disk is replaced and made available to the server, it is automatically synchronized with the intact copies. The hardware dual copy could also be used to provide protection from media failures. The advantage of using dual copy is faster write performance because the server issues a single write and the storage control asynchronously writes the additional copy. With mirroring, multiple writes are issued at the same time. Mirroring is not recommended with RAID 5, unless it is mirrored to a separate RAID array.
7-19
Mirroring
Database volume copies increase the availability of the database and provide safeguards against media failure. You can have as many as two volume copies of an existing database volume. After each database volume copy is defined, the server attempts to synchronize the volume copy with the database. Recovery log volume copies increase the availability of the recovery log and provide safeguards against media failure. You can have as many as two volume copies of an existing recovery log volume. After each recovery log volume copy is defined, the server attempts to synchronize the volume copy with the recovery log. The 2-step process (dsmfmt and define) is not covered in order to make the topic less confusing for beginning storage administrators. You can include it if you want to.
7-23
The define spacetrigger command
If space trigger was set during installation, you can only modify it using the command line. Mention the define spacetrigger stg command and how it differs from space triggers for the database and recovery log.
11
Unit 8 8-4 Topic Command Line Note Refer to the IBM Tivoli Storage Manager Administrator Reference Guides for other platforms. Demonstrate navigation of backup-archive GUI.
8-7
GUI
8-16
Client Options
The backup-archive client is enhanced to support backup and restore of directories in a more intuitive and logical way. If none of the options are used, both directories and files are backed up or restored. The DIRSONLY and FILESONLY options can only be specified on backup or restore commands using the backup-archive command line client. The options cannot be put in the client user options file (dsm.opt).
8-17
Client Options
Tivoli Storage Manager now supports fully qualified object names of up to 8704 bytes in length. This support is available for backup and restore functions, and is dependent on whether or not the client also supports the byte length. Long names might be abbreviated in message or query output due to length. You can display them using the DISPLAY OBJNAME command.
12
8-20 Graphical Options Editor Defining a TSM client option set is a two-step process. First, the client option set is defined, and then, the options are defined to it. A graphical options editor (available under Edit > Preferences) is provided with the backup-archive GUI. The graphical options editor makes the process of updating the TSM client options more user friendly and less error prone. The options editor groups the options in the following categories: General: Set general processing options for TSM such as nodename and errorlog. Backup: Set backup processing options. Restore: Set restore processing options such as file replace. Include-Exclude: Specify Include-Exclude processing options. Scheduler: Specify processing options for scheduled TSM work. For example, options that influence scheduling services such as schedule mode and schedule log file handling. Regional Settings: Set locale options for your client node. Authorization: Specify authorization options for your client. Web Client: Specify processing options for your TSM Web client. Command Line: Specify TSM command-line client processing options. Diagnostic: Specify type of tracing to perform in the event of a problem with your TSM client. Communication: Update TCP/IP communication options such as TSM server name, TCP window and buffer sizes. Refer to the TSM Client Options chart. All system services components are now backed up as part of system state. This eliminates the need to schedule a separate backup for system services or specifying systemservices in the domain. You will not be able to back up individual system services components; however, individual components can be restored.
8-26
Options
13
8-32 Include-Exclude Determine if the files specified will be selected for backup based upon the include-exclude list provided. Remember, if it is not excluded, it is included. bob.log is excluded (matched on line 1) fileone is included (matched on default) /home/nobody/data/file1.dat is excluded (matched on line 2) /usr/lwp/resume.ibm (included matched on line 4) /usr/lwp/data/file1.dat is excluded (matched on line 3)
8-50
Encryption and Security
Transparent encryption support Support has been added for transparent encryption, using the encryptkeygenerate option.
8-53
SSL
Communications between the Tivoli Storage Manager server and the backup-archive client, administrative command-line client (dsmadmc), and client Application Programming Interface are always password protected. However, you can now add another level of data protection by using Secure Sockets Layer (SSL). SSL is the standard technology for creating encrypted links between servers and clients. SSL provides a secure channel for servers and clients to communicate over open communications paths.
14
Unit 9 Unit 9 Topic General Note Note Client node proxy support Backup time can be reduced with client node proxy support. Tivoli Storage Manager nodes, when authorized as agent nodes, can be directed to back up or restore data on behalf of another node (the target node). This enables concurrent operations from multiple nodes to store data to the same target node and file space in parallel. Client nodes can also be configured with proxy node authority to support many of the systems that can be configured to support clustering failover. The asnodename option also allows data to be restored from a different system than the one which performed the backup. Client node proxy is not in the Student Guide, because there is so many concepts already covered. Mention it to the students, if you feel it is appropriate. Mention that Incremental by Date is not often used.
9-5
Incremental by Date Without Journal
9-5
Use when the backup window is exceeded.
9-22
Restore
The difference in No Query Restore and Classic Restore was take from this class and put into the Part Two class, so as to not overload the students. You might want to give a brief overview.
15
9-25 Point-in-Time Restore A point-in-time restore recovers a file space or a directory to the state it had at a prior date and time. A point-in-time restore is difficult to perform using the TODATE and TOTIME options with the restore command. A point-in-time restore is selected from the backup-archive GUI by selecting a point-in-time date from the Restore window. Pointin-time restores are started from the TSM backup-archive command line by using the command-line options. The use of point-in-time restore has a number of dependencies and considerations. Incremental backups performed using the Incremental by Date method are not true incremental backups. A point-in-time restore cannot be performed when this type of incremental backup is used. When performing a point-in-time restore, file filtering is done by the TSM server as opposed to other restores where all the file filtering is done by the TSM client. Having the TSM client server doing the file filtering can potentially lead to reduced restore times. Copy group values with no limits such as VEREXIST and VERDELETED can result in large numbers of backup copies being maintained by the server. This is compounded in situations where users can run multiple incremental backups a day. If such values are to be used, use of the copygroup FREQUENCY parameter, to control the interval between incremental backups, should be considered. 9-43 Student Exercises, Part 1 Even though the topics have been covered by this point, the lab exercises for command-line backup and restore are in Student Exercises, Part 2. This is to make the two lab sessions more equal in time. Open file support and online image backup are now available for Windows 64-bit operating systems. Open file support and online image backup are now supported on Windows 64-bit operating systems, and Volume Shadowcopy Service (VSS) is now a supported snapshot provider on both 32bit and 64-bit Windows versions, excluding Windows XP. With this support, the fileleveltype and imagetype options are being replaced by snapshotproviderfs and snapshotproviderimage, respectively. AIX JFS2 snapshot integration for snapshot-based image backup and snapshot-based file level backup and archive. Snapshot-based image backup and file backup and archive support is available for AIX 5.3 or later JFS2 file systems. This support provides consistent backup of the files and snapshotbased images. The imagetype=dynamic, snapshot, and static options have been replaced by the dynamicimage and snapshotproviderimage options
9-62
Windows Image Snapshot
9-64
Logical Volume Image Backup
16
Unit 10 10-16 Topic Database Backup Related Commands Restoring the Server Restoring The Database Note The last database backup cannot be deleted unless the parameter force=yes is used. Review how Disaster Recovery Manager automated this process. Ask the students where TSM will get the needed information to restore the database if it is damaged and the VOLHISTORY and DEVCONFIG files are not present. Answer: You would have to know the volumes to mount in the correct order and you would have to rebuild the device config file manually. To restore the database to a specific point in time, use the dsmserv restore db command. TSM restores the database as follows: Reads the volume history file to locate the last regular backup that occurred on or before the specified date and time. Using the device configuration file, requests a mount of the first volume, which should contain the beginning of the regular backup. Restores the backup data from the first volume. 10-28 Best Practices Ask the students if they would mirror the database or the recovery log, if there was only space to mirror one. Answer: Mirror the recovery log, since the database can be backed up. Defining and updating ADPs was moved from Unit 5 to Lesson 4, Unit 10, since it required knowledge of Policies. Emphasize the importance of multiple copy storage pools Ask the students how many commands would have to be issued to back up the primary pool hierarchy for local media failure and disaster recovery (both on-site and off-site). Answer: 4. Ask the students to give the command to back up the storage pool hierarchy from their TSM server in lab to a copy storage pool named on-site. Answer: backup stgpool backuppool on-site backup stpool archivepool on-site
10-25 10-26
10-30 10-40 10-42
Active-data pools Define A Copy Storage Pool Backup Storage Pool Hierarchy
10-52
Accessing Damaged Files
Use the preview option.
17
Unit 11 11-13 11-17 Topic Additional Client Polling Options Randomization Note Restart scheduler after resetting mode. Use this scenario to show the alternative to randomizing. There are 450 clients around the country that need to be backed up. We could assign one person the task of coming up with 450 individual schedules to evenly spread the work over the six hour window. Remember that randomizing does not evenly spread the work around but randomly spreads the work around. With 450 individual schedules we could start one backup at 1:00 and one at 1:06, and so on. We could even allow for the fact that one node backs up faster than another and set the schedules start time appropriately. That would take a lot of administrative work. A better approach would be to define ONE schedule for all nodes. Set the start time to 01:00:00. Write that in the STARTTIME box. Tell the students that our current TSM server MAXSESSIONS it set to 100. Write that in the box. MAXSCHEDULED SESSIONS is set to 80%. Write that in the box. Ask the students how many schedules will start at 01:00. Answer: 80. Ask the class what will happen when one of the 80 schedules is completed. Answer: Another will start. Ask the class when the TSM server will stop starting new schedules. Answer: When all schedules have run or the startup window is past. Ask the class what if in the morning we find that there are some schedules that did not run, but we had network and server resources available? Answer: We can adjust MAXSESSIONS or MAXSCHEDULE SESSIONS up. Ask the class what if the reverse was true. Answer: Lower those values. Adjusting MAXSESSIONS or MAXSCHEDULE SESSIONS can be a big advantage to server prompted scheduling. We can adjust the amount of work and not have to rewrite schedules. Ask the class what happens if a client is associated with two schedules that have the same startup time. Answer: TSM provides a way of prioritizing schedules so that the more critical scheduled operation is completed first by the client.
11-18
Defining Schedules
11-37
Command Line to Query Schedule
Demonstrate how to set up a client backup at 21:00 (9:00 p.m.) every night.
18
Unit 12 12-8 Topic Event Receiving Note Client messages eligible for sending to the server are formatted as client events. This ensures that all client events have a common format.
12-9
Event Filtering
Before client events can be passed to the server they have to be enabled at the server. The enable event command has been added to manage central logging and monitoring. It enables logging of client and server events.
12-14
Enabling Client Events
One of the main goals when designing the central logging function is to provide an efficient solution. Only a set of client messages are logged as events to the server.
12-16
Storing Client Events in the Activity Log
Client events can be disabled for the activity log. Show command: disable events actlog info node=<nodename>
12-17
Retention Period Parameter ACTLOGRET
12-25
Operational Reporting Optional Windows Exercise
Auditlogging and auditlogname options The auditlogging option generates an audit log with an entry for each file that is processed during an incremental, selective, archive, restore, or retrieve operation. The auditlogname option specifies the path and file name where you want to store audit log information. This option applies when audit logging is enabled. If time permits, have the students perform an optional exercise on installation and configuration of Operational Reporting. Use the Installing Operational Reporting.pdf, file, and excerpt from the IBM Tivoli Storage Manager 5.5 Administration Guide, located on the Instructor and Student Resources CDs.
19
Appendix A A-1 Topic Additional TSM Product Information Note If time permits, you can cover this material. The slides are in your PowerPoint slide show.
Appendix B B-1
Topic Problem Determination
Note If time permits, you can cover this material. The slides are in your PowerPoint slide show.
20

Students Training Guide
S150-2878-00
March 2008
Copyright Notice Copyright 2008 IBM Corporation, including this documentation and all software. All rights reserved. May only be used pursuant to a Tivoli Systems Software License Agreement, an IBM Software License Agreement, or Addendum for Tivoli Products to IBM Customer or License Agreement. No part of this publication may be reproduced, transmitted, transcribed, stored in a retrieval system, or translated into any computer language, in any form or by any means, electronic, mechanical, magnetic, optical, chemical, manual, or otherwise, without prior written permission of IBM Corporation. IBM Corporation grants you limited permission to make hardcopy or other reproductions of any machine-readable documentation for your own use, provided that each such reproduction shall carry the IBM Corporation copyright notice. No other rights under copyright are granted without prior written permission of IBM Corporation. The document is not intended for production and is furnished as is without warranty of any kind. All warranties on this document are hereby disclaimed, including the warranties of merchantability and fitness for a particular purpose. Note to U.S. Government UsersDocumentation related to restricted rightsUse, duplication or disclosure is subject to restrictions set forth in GSA ADP Schedule Contract with IBM Corporation. Trademarks The following are trademarks of IBM Corporation or Tivoli Systems Inc.: IBM, Tivoli, AIX, Cross-Site, NetView, OS/2, Planet Tivoli, RS/6000, Tivoli Certified, Tivoli Enterprise, Tivoli Ready, TME. In Denmark, Tivoli is a trademark licensed from Kjbenhavns Sommer - Tivoli A/S. Microsoft, Windows, Windows NT, and the Windows logo are trademarks of Microsoft Corporation in the United States, other countries, or both. UNIX is a registered trademark of The Open Group in the United States and other countries. C-bus is a trademark of Corollary, Inc. in the United States, other countries, or both. Java and all Java-based trademarks are trademarks of Sun Microsystems, Inc. in the United States, other countries, or both. Lotus is a registered trademark of Lotus Development Corporation. PC Direct is a trademark of Ziff Communications Company in the United States, other countries, or both and is used by IBM Corporation under license. ActionMedia, LANDesk, MMX, Pentium, and ProShare are trademarks of Intel Corporation in the United States, other countries, or both. SET and the SET Logo are trademarks owned by SET Secure Electronic Transaction LLC. For further information, see http://www.setco.org/aboutmark.html. Other company, product, and service names may be trademarks or service marks of others. Notices References in this publication to Tivoli Systems or IBM products, programs, or services do not imply that they will be available in all countries in which Tivoli Systems or IBM operates. Any reference to these products, programs, or services is not intended to imply that only Tivoli Systems or IBM products, programs, or services can be used. Subject to valid intellectual property or other legally protectable right of Tivoli Systems or IBM, any functionally equivalent product, program, or service can be used instead of the referenced product, program, or service. The evaluation and verification of operation in conjunction with other products, except those expressly designated by Tivoli Systems or IBM, are the responsibility of the user. Tivoli Systems or IBM may have patents or pending patent applications covering subject matter in this document. The furnishing of this document does not give you any license to these patents. You can send license inquiries, in writing, to the IBM Director of Licensing, IBM Corporation, North Castle Drive, Armonk, New York 10504-1785, U.S.A.
Table of Contents
Table of Contents
IBM Tivoli Storage Manager 5.5 Implementation and Administration Preface
Course Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ii Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ii Where to Find the Training Schedules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .iii Course Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .iv Course Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . v Agenda . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .vi Course Outline . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii Typographical Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .ix Product Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .ix Software Release Numbers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .ix Product Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . x Suggestions in this Course . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . x
Unit 1: IBM Tivoli Storage Manager Overview

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2 Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3
Lesson 1: Protecting Data with IBM Tivoli Storage Manager . . . . . . . . . . . . . .1-4

IBM Tivoli Storage Manager: An Enterprise-Wide Solution . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4 IBM Tivoli Storage Manager Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5 Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-6 Tivoli Storage Manager Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-7 Scheduler . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-8 Backup-Archive Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-9 Tivoli Storage Manager Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-10 Tivoli Storage Manager Recovery Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-11 Storage Pools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-12 Policy-Based Approach to Data Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-13 Tape Library . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-14 Backup-Restore Functionality Provided by IBM Tivoli Storage Manager . . . . . . . . . . . . . . . . . 1-15 Long-Term Storage Capabilities Provided through the Archive-Retrieve Function . . . . . . . . . 1-16 Administrator Management Capabilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-17 The Administration Center on the Integrated Solutions Console . . . . . . . . . . . . . . . . . . . . . . . 1-18 Managing IBM Tivoli Storage Manager with the Administration Center . . . . . . . . . . . . . . . . . . 1-19 Automation Capabilities Provided by IBM Tivoli Storage Manager . . . . . . . . . . . . . . . . . . . . 1-19
Lesson 2: Data Storage and Data Management . . . . . . . . . . . . . . . . . . . . . .1-20

Types of Storage Media on which Tivoli Storage Manager Stores Data . . . . . . . . . . . . . . . . . 1-20 Optional IBM Tivoli Storage Manager Products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-21 IBM Tivoli Storage Managers Disaster Preparation and Recovery . . . . . . . . . . . . . . . . . . . 1-22
Lesson 3: Licensing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-23

IBM Tivoli Storage Manager Licensing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-23 Upgrading from IBM Tivoli Storage Manager Express . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-23 Review Questions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-24
Table of Contents
Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-27
Unit 2: Installing IBM Tivoli Storage Manager

Lesson 1: Installation Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-3

IBM Tivoli Storage Manager 5.5 Packaging Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . System Requirements for IBM Tivoli Storage Manager Server . . . . . . . . . . . . . . . . . . . . . . . . . System Requirements for Linux IBM Tivoli Storage Manager Server . . . . . . . . . . . . . . . . . . . Backup-Archive Client Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Integrated Solutions Console and TSM Administration Center . . . . . . . . . . . . . . . . . . . . . . . . . ISC and Administration Center Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installing IBM Tivoli Storage Manager on Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Main Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Select Product to Install . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Install TSM Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Follow the Wizard Steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Customer Information and Select Type Screens . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installing and Completing the InstallShield Wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TSM Server Licenses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Install Language Packs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Install Device Drivers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installing Tivoli Storage Manager on AIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Complete the Smit or Smitty Installation Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . AIX Installation Steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . AIX Installation Steps, continued . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installing Message Catalog (Languages) and Device Driver . . . . . . . . . . . . . . . . . . . . . . . Installing Tivoli Storage Manager on Linux . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Basic installation steps for Red Hat Linux 4: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3 2-5 2-6 2-7 2-8 2-9
Lesson 2: Installing IBM Tivoli Storage Manager . . . . . . . . . . . . . . . . . . . . . .2-10

2-10 2-10 2-11 2-12 2-13 2-13 2-14 2-15 2-16 2-17 2-18 2-19 2-20 2-21 2-22 2-23 2-23
Lesson 3: What the Server Installs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-25

Basic Components Installed by IBM Tivoli Storage Manager . . . . . . . . . . . . . . . . . . . . . . . . . 2-25 Files Created during Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-27 Verify that the Server Installation Has Completed Successfully . . . . . . . . . . . . . . . . . . . . . . . . 2-28
Lesson 4: Installing the IBM Integrated Solutions Console ISC . . . . . . . . . . .2-29

Verify Space Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Accept License Agreement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Select Directory, Paths, and Review Installation Information . . . . . . . . . . . . . . . . . . . . . . . . ISC Installation Steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-30 2-31 2-32 2-33
Lesson 5: Administration Center Installation . . . . . . . . . . . . . . . . . . . . . . . . .2-34

ISC Configuration and Option Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-35 InstallShield Installs the Administration Center . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-36
Lesson 6: Installing the Backup-Archive Client . . . . . . . . . . . . . . . . . . . . . . .2-37

Destination Folder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-38 Custom Install . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-39 Web Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-40
Lesson 7: Initial Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-41

Initial Configuration Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Environmental Wizard Performance Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Server Initialization Wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Server Volume Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Client Node Configuration and Prepare Media Wizards . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-41 2-42 2-43 2-44 2-45
Lesson 8: The Query Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-46

2 IBM Tivoli Storage Manager 5.5 Implementation and Administration Copyright IBM Corp. 2008
Table of Contents
The Powerful Query System Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Standard Format Query Result . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Detailed Format Query Result . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Query Activity Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Student Exercise . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Review Questions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2-46 2-47 2-48 2-49 2-50 2-51 2-53
Unit 3: Administrative Interfaces and Privileges

Lesson 1: Interfaces for Tivoli Storage Manager . . . . . . . . . . . . . . . . . . . . . . .3-3

Available Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3
Lesson 2: The Integrated Solutions Console and Administration Center . . . . .3-4

Overview of the Integrated Solutions Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4 Tivoli Storage Managers Administration Center . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5 Logging on to the Integrated Solutions Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-6 How the Integrated Solutions Console Recognizes Your Tivoli Storage Manager Authority . . . 3-7 Navigating the Administration Center . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-8 Exploring the Task Trees . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-8 Navigating the Administration Center . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-9 Menus and Wizards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-10 Select Action Menus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-11 Health Monitor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-11 Enterprise Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-12 Storage Devices, Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-13 Policy Domains and Client Nodes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-14 Server Maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-15 Reporting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-16 Disaster Recovery Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-17 Starting and Stopping the Administration Center . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-18 Administration Center Support Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-19 Adjusting the Session Timeout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-20
Lesson 3: Using the ISC to Manage Tivoli Storage Manager . . . . . . . . . . . . .3-21

Creating a Tivoli Storage Manager Administrator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Creating a Tivoli Storage Manager Administrator, continued . . . . . . . . . . . . . . . . . . . . . . . . Granting the iscadmin Access to the Administration Center . . . . . . . . . . . . . . . . . . . . . . . . . . Adding a Tivoli Storage Manager Server to the Administration Center . . . . . . . . . . . . . . . . . . Using the Health Monitor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configuring the Health Monitor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Database and Recovery Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Tivoli Storage Manager database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Tivoli Storage Manager recovery log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Activity Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-21 3-22 3-23 3-24 3-25 3-26 3-27 3-27 3-27 3-28
Lesson 4: IBM Tivoli Storage Managers Graphical User Interface (GUI) . . .3-29
Tivoli Storage Manager Windows Server GUI: Management Console . . . . . . . . . . . . . . . . . 3-29 The GUI for Backup-Archive Clients . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-30 Web Backup-Archive Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-31
Lesson 5: Command Lines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-32

Some keyboard keys used . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Using Syntax Diagrams . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Example of Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Accessing the Administrative Command Line from the Administration Center . . . . . . . . . . . . Output of a Command-line Query . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3-33 3-34 3-35 3-36 3-37

3
Table of Contents
Lesson 6: Administrative Authority . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-39

Privilege Classes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Registering an Administrator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Managing Administrative Authority . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Granting Authority to Administrators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Extending Authority for Administrators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Reducing Authority for Administrators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Reducing Privilege Classes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Revoking Authority for Administrators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Removing an Administrator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Export/Import of Administrator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Student Exercise . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Review Questions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-40 3-41 3-42 3-42 3-42 3-43 3-43 3-43 3-44 3-45 3-46 3-47 3-49
Lesson 7: Export/Import . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-45
Unit 4: Storage Media Devices Introduction

Lesson 1: Installing and Configuring a Tape Library Attached to the IBM Tivoli Storage Manager Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-3
Installing and Configuring a Tape Library . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3 Connecting a SCSI Library . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-4 Supported Device Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-5 Getting Device Information from the Tivoli Storage Manager Device Driver . . . . . . . . . . . . . . . 4-6 Use tsmdlst to Find Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-7 Determining Numbers for Libraries with Multiple Drives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-8 Configuring Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-10
Lesson 2: Working with Media . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-11

The Difference between Scratch and Private Volumes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . The Life Cycle of Tape Cartridges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Labeling Tapes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Label Libvolume . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . AUTOLABEL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Checking Out Volumes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Checking In Volumes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Auditing a Library . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Review Questions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-11 4-12 4-13 4-13 4-14 4-15 4-16 4-17 4-18 4-21

Lesson 1: Storage Pools, Hierarchies, and Storage Pool Volumes . . . . . . . . .5-3

Storage Pools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-3 Storage Pool Hierarchies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-4 Active-Data Pools and the Storage Hierarchy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-5 Device Classes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-6 Device Class and Storage Pool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-9 Storage Destination . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-10 Disk-Only or Tapeless Backup Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-11 Defining Storage Pools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-12
Table of Contents
Update and Query Storage Pools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Active-data Pools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Before Storing Data in an Active-data Pool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Using the Administration Centers Create Storage Pool Wizard . . . . . . . . . . . . . . . . . . . . . . . Create Storage Pool Wizard, continued . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Policy Domain Wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Creating or Defining Storage Pool Volumes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Defining Storage Pool Volumes for Disk . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Deleting Storage Pools and Volumes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . How to Move Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Concurrent Storage Pool Volume Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Overflow Location for Storage Pool Media . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Database Tracking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Storage Pool Migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Using the Administration Center for Migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Reclamation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Single Drive Reclamation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Example of Single Drive Reclamation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Collocation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Collocation Volume Selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Collocation Volume Selection Example 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Collocation Volume Selection Example 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Collocation by Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Collocation of Active Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Collocation of Active Data with the Administration Center . . . . . . . . . . . . . . . . . . . . . . . . . . Copy Active Data Form . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Student Exercise . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Review Questions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5-13 5-14 5-15 5-16 5-17 5-18 5-19 5-21 5-22 5-24 5-26 5-27 5-27 5-29 5-30 5-32 5-34 5-35 5-36 5-37 5-39 5-40 5-41 5-42 5-43 5-44 5-45 5-46 5-47 5-50
Lesson 2: Automatic Data Movement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-29

Lesson 1: How TSM Manages Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-3

Centrally Managed by Business Policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-3 Policy Management Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-4 How Tivoli Storage Manager Stores Client Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-5
Lesson 2: Defining Policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-6

Policy Domain . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-6 Using the Administration Center to Define Policy Domains . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-7 Using the Command Line to Define a Domain . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-8 Define a New Policy Set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-9 Using the Command Line to Define a Policy Set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-10 Defining Management Classes for Policy-driven Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-11 Using the Administration Center to Define Management Class . . . . . . . . . . . . . . . . . . . . . . . . 6-12 Using Command Line to Define Management Class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-13
Lesson 3: Working with Copy Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-14

Copy Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Using the Command Line to Define a Copy Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Using the Command Line to Define a Copy Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Copy Group Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Default Server Policies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Policy Settings in STANDARD Domain . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6-14 6-15 6-17 6-17 6-19 6-20

5
Table of Contents
Lesson 4: Expiration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-21

Expire inventory manually starts inventory expiration processing. The inventory expiration process removes client backup and archive file copies from server storage based on policy specified in the backup and archive copy groups of the management classes to which the files are bound. . . . 6-21 Related Server Option: EXPINterval Hours . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-22 Example of Expiration Processing: Part 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-23 Example of Expiration Processing: Part 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-24 Tivoli Storage Manager File Backup Processing: Part 3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-25 Storage Management Archive File Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-27 Specifying the Management Class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-28 Policy Domain Grace Retention Periods . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-29 Assign Default Management Class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-30 Validate and Activate Policy Sets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-31 Bind Files to the Management Class (MC) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-32 Rebinding Management Classes to Backup Versions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-33 Copy Domain . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-34 Export/Import of Policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-35 Student Exercise . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-36 Review Questions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-37 Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-39
Unit 7: Customizing the Tivoli Storage Manager Database and Recovery Log
Lesson 1: The Purpose of the Database and Recovery Log . . . . . . . . . . . . . .7-3

Database and Recovery Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Transactions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Recovery Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Normal Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Roll-Forward Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Database Space Allocation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Determine How Many Database Volumes You Need . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Recovery Log Space Allocation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Determine How Many Database Volumes You Need . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-3 7-5 7-6 7-6 7-7 7-8 7-8 7-9 7-9
Lesson 2: Sizing the Database and Recovery Log . . . . . . . . . . . . . . . . . . . . .7-10

Estimating Space Requirements for the Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-10 Cached Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-12 Estimating the Size of the Recovery Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-13
Lesson 3: Adding Space . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-14

Creating Additional Volumes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . AIX Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Linux Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Windows Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Database and Recovery Log Space . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Using the Administration Center . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-14 7-15 7-15 7-15 7-15 7-16 7-17
Lesson 4: Reducing the Database and Recovery Log Space . . . . . . . . . . . .7-18 Lesson 5: Mirroring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-19
Database and Recovery Log Mirroring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-19 Using the Administration Center to Mirror . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-20 Mirroring Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-21
Lesson 6: BUFPOOLSIZE Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-22

6
Table of Contents
Lesson 7: Space Triggers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-23

Define Spacetrigger . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Student Exercise . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Review Questions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-23 7-25 7-26 7-29
Unit 8: Client Configuration

Lesson 1: Client Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-3

Identify the Client Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-3 The Backup-Archive Command Line . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-4 Using the Command-line Interface Loop . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-5 Backup-Archive Command-line Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-5 The Web Client Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-6 The Backup-Archive GUI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-7 Utilities Menu Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-8 Change Password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-8 Node Access List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-8 Access Another Node . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-8 View Policy Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-9 Delete Archived Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-9 Delete Backup Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-9 Delete Filespace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-9 Setup Wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-10 Preview Include-Exclude . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-10 Query DiskInfo Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-10 Create ASR Diskette . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-10
Lesson 2: Administrative Control of Access . . . . . . . . . . . . . . . . . . . . . . . . . .8-11

Registration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Password Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Set Password Expiration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Set Invalid Sign-on Limit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Set Minimum Password Length . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Prevent Client Nodes from Accessing the Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Backup Operators Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configuring Client Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Example of DSM.OPT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Editing the Client Options File with the GUI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Using the Graphical Options Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configure Client Access to the Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PASSWORDACCESS GENERATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Additional Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Identify Precedence of Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Override Configuration Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . The Domain Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Domain for Backup: Client Configuration Wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Client Options Available to Configure and Improve Performance . . . . . . . . . . . . . . . . . . . . . . Sever Option: TXNGROUPMAX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configuring Error Logging Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . DSMSCHED.LOG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-11 8-12 8-12 8-12 8-13 8-14 8-15 8-17 8-18 8-19 8-20 8-21 8-23 8-24 8-24 8-24 8-25 8-26 8-27 8-28 8-29 8-30
Lesson 3: Managing Client Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-16
Lesson 4: Client Performance and Options . . . . . . . . . . . . . . . . . . . . . . . . . .8-27
Lesson 5: Include-Exclude Processing Rules . . . . . . . . . . . . . . . . . . . . . . . .8-31

Copyright IBM Corp. 2008 IBM Tivoli Storage Manager 5.5 Implementation and Administration 7
Table of Contents
Include-Exclude Processing Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Exclude Directories from Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . EXCLUDE.DIR Statement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Backup of Excluded Directories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Compression, Encryption, and Adaptive Subfile Backup Processing . . . . . . . . . . . . . . . . . . Identify Files to Be Included or Excluded from Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Metacharacters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Include-Exclude Wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Include-Exclude Using the Backup-Archive Tree . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Include-Exclude Exercise . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Identify the Value of Client Option Sets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Define Include-Exclude Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Use Sequence Numbers in an Option Set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Use the FORCE Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Copy, Query, Delete, or Update a Client Option Set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Create an Option Set with the Administration Center . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Summary of Client Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
8-32 8-33 8-33 8-34 8-35 8-36 8-37 8-38 8-39 8-40 8-43 8-43 8-44 8-44 8-45 8-46 8-47
Lesson 6: Client Option Sets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-41
Lesson 7: Delete Backup Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-48 Lesson 8: Encryption and Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-50
Encryption . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Encryption Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Encryption and Archiving . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Encryption and Unattended Restores . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Encryption Key . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Secure Sockets Layer (SSL) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Student Exercise . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Review Questions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-50 8-51 8-51 8-51 8-52 8-53 8-54 8-55 8-57

Lesson 1: Types of Backups Available . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-3

Types of Backups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Incremental (Complete) Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Incremental by Date Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Incremental (without Journal) Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Selective (Always Backup) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . How Journal-Based Backups Work . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . File Level Backups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-3 9-5 9-5 9-5 9-6 9-7 9-8
Lesson 2: Overview of Backup Sets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-9

Backup Set Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-9 Additional Backup Set Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-10 Point-in-Time File Selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-11 Backup Set Table of Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-12
Lesson 3: Performing Client Backups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-13

Using the TSM Backup-Archive GUI and Web Client to Back Up Files from a Client . . . . . . . Select Files and Perform a Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Review Backup Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Use the Find Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Results of a Filter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Use the Estimate Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Select Always Backup as Type of Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
8
9-13 9-14 9-16 9-17 9-18 9-19 9-19
Table of Contents
Using the GUI to Delete Backup Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-20
Lesson 4: Restoring Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-21

Restore Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Restore Files Using the GUI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Active and Inactive Version of a File to Restore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Modify Restore Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Point-in-Time Restore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Backup Set GUI for Restore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Restartable Restores . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Restartable Restore Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Restartable Restore Database Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Using the Backup-Archive Command Line . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Perform an incremental Backup on the Command Line . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Selective Backup Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Use the Query Filespace Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Delete Backup Command Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Restore Backed Up Files Using the dsmc restore Command . . . . . . . . . . . . . . . . . . . . . . . . . Use the dsmc restore Command with the PICK Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Using the dsmc restore Command with Overwrite . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Use the LATEST Option with the dsmc restore Command . . . . . . . . . . . . . . . . . . . . . . . . . . . Restore to New Location Using PRESERVEPATH Restore Option . . . . . . . . . . . . . . . . . . . . Use the IFNEWER with the dsmc restore Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Using the PITDATE and PITTIME Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Restartable Restore Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Student Exercise . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Overview of Archive and Retrieve . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Archive and Retrieve Using the GUI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . First-time Archive Processes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Archiving Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Archive Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Archive Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Unique Archive Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Archive Packages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Override Archive Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . V2 Archive (files only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . How Retrieve Works . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Retrieving Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Retrieve Using the GUI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Retrieve Archive Packages Using the GUI Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Retrieve Options; Modify Retrieve and Collision Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-21 9-22 9-23 9-24 9-25 9-26 9-27 9-28 9-30 9-31 9-32 9-33 9-34 9-35 9-36 9-37 9-38 9-39 9-40 9-41 9-42 9-42 9-43 9-44 9-46 9-47 9-48 9-49 9-49 9-49 9-50 9-51 9-51 9-52 9-53 9-54 9-54 9-55
Lesson 5: Backup and Restore with the Command Line . . . . . . . . . . . . . . . .9-31
Lesson 6: Archive and Retrieve . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-44
Lesson 7: Archive and Retrieve Command Line . . . . . . . . . . . . . . . . . . . . . .9-56 Lesson 8: Command Options for Backup, Archive, Restore, and Retrieve . .9-58
Backup, Archive, Restore, and Retrieve of Directories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-60
Lesson 9: The Types of backups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-61

Image Backup Overview; Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Windows Snapshot Image Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Open File Support with LVSA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Windows Incremental Image (Date Only) Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Logical Volume Image Backup: AIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . AIX and Linux Snapshot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Subfile Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . NAS File System Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Student Exercise . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Review Questions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9-61 9-62 9-62 9-63 9-64 9-66 9-67 9-68 9-70 9-71
9
Table of Contents
Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-73

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-2 Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-2
Lesson 1: Tivoli Storage Manager Database and Storage Pool Protection Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10-3
Tivoli Disaster Recovery Manager Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-4 The Disaster Recovery Plan File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-5 Using the Administration Center for Disaster Recovery Management . . . . . . . . . . . . . . . . . 10-6
Lesson 2: Backing Up the Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10-7

Tivoli Storage Manager Database Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-7 Full Backup Plus Incremental Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-8 Database (Snapshot) Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-9 Database Backup Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-10 Initiating a Database Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-12 DBBackuptrigger and Log Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-13 Define DBBackuptrigger Command Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-14 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-14 Database Backup Related Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-16 Query DB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-16 Query Volhistory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-16 Delete Volhistory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-17
Lesson 3: Database Recovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10-18

Restoring the Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Roll-Forward Recovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Point-in-Time Recovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Backing Up Volume and Device-Related Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Restoring the Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Database Restore Command Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Restoring to a Specific Point in Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Best Practices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Backup of Storage Pool Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Define a Copy Storage Pool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Define Stgpool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Define Stgpool Command Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Define Volume . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Backing Up the Storage Pool Hierarchy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Simultaneous Write to Multiple Copy Storage Pools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Using Simultaneous Write with Active-data Pools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Setting up Simultaneous Write with the Administration Center . . . . . . . . . . . . . . . . . . . . . . Handling Off-Site Volumes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Update Volumes * Access=Offsite . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Reclamation of Off-Site Volumes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Update Volume * Access=Readwrite . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Restoration of Storage Pool Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Accessing Damaged Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Maintaining the Integrity of Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Recovering from a Media Loss . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Restore Volume Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Restore Volume Command Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Recovering Storage Pool Volumes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Restore Storage Pool Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Backup and Recovery Best Practices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10
10-19 10-20 10-21 10-23 10-25 10-26 10-26 10-28 10-32 10-34 10-34 10-34 10-35 10-36 10-37 10-38 10-39 10-40 10-41 10-42 10-43 10-44 10-46 10-48 10-49 10-51 10-51 10-53 10-54 10-55
Lesson 4: Storage Pool Backup and Recovery . . . . . . . . . . . . . . . . . . . . . .10-30
Table of Contents
Protecting Your Database and Storage Pool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-57 REUSEDELAY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-57 Daily Administration Cycle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-58
Lesson 5: Tivoli Storage Manager Maintenance Plans . . . . . . . . . . . . . . . .10-59

How to Set Up a Maintenance Plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TSM Database Management Tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Student Exercise . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Review Questions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-60 10-67 10-69 10-70 10-73
Unit 11: Automating Operations

Lesson 1: Scheduling Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11-3

Overview of Schedules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-3 Scheduling Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-4
Lesson 2: Client Scheduling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11-5

Traditional Scheduling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-6 About CAD-managed Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-6 Central Scheduling Mode: Client Polling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-7 Central Schedule Mode: Server Prompted . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-8 Selecting Schedule Methods . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-9 Additional Client Scheduling Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-11 MAXSCHEDSESSIONS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-12 Additional Client Polling Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-13 Additional Server Prompted Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-14 Preschedule and Postschedule Processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-15 Consistent Client Return Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-16 Example of Randomizing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-17 Defining Schedules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-18 Parameters for Defining Schedules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-19 Defining Schedules: Server-Prompted Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-22 Defining Schedules Using the Administration Center . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-23 Client Node Schedules with the Administration Center . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-24 Using the Command Line to Define a Schedule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-25 Enhanced Scheduling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-26 Examples of Calendar-Based Schedules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-27 Schedule Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-28 Relative Date and Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-29 Relative Date . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-29 Relative Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-29 Copying a Schedule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-30 Using the Command Line to Define an Association . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-31 One-Time Scheduled Client Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-33 Preventing Unwanted Schedule Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-35 Options to Prevent Unwanted Schedule Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-36 Using the Command Line to Query Schedule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-37
Lesson 3: Administrative Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11-38

Automating Administrative Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Scheduling an Administrative Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Administrator Scheduling Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Examples of Defining Administrative Schedules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Defining Administrative Schedules Using the Administration Center . . . . . . . . . . . . . . . . . . . Additional Functions to Schedule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Student Exercise . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11-38 11-40 11-41 11-42 11-43 11-44 11-45

11
Table of Contents
Review Questions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-46 Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-49
Unit 12: Monitoring and Event Logging

Lesson 1: Client Event Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .12-3

Monitoring and Logging Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Client Messages Logged on the Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Loggable Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Nonloggable Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . API Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Client Event Formatting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Common Message Repository . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Event Formatting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Event Content . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Message Formatting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-3 12-4 12-4 12-4 12-5 12-6 12-6 12-6 12-7 12-7
Lesson 2: Event Receiving . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .12-8

Event Filtering and Logging Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-9 Begin Eventlogging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-9 Enable Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-9 Disable Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-10 Query Enable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-11 Query Eventrules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-11 End Eventlogging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-12
Lesson 3: Working with Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .12-13

Client Event Processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Enabling Client Events for the Tivoli Storage Manager Console . . . . . . . . . . . . . . . . . . . . . . Storing Client Events in the Activity Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Pruning the Activity Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Retention Period Parameter ACTLOGRET . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Querying Events in the Activity Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Managing Event Logs with the Administration Center . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Client Log Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Audit Logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-13 12-14 12-16 12-17 12-17 12-18 12-20 12-21 12-22
Lesson 4: Monitoring and Reporting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .12-23

Database Reporting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-23 SQL Select . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-24
Lesson 5: IBM Tivoli Storage Manager Operational Reporting . . . . . . . . . .12-25

Benefits of Operational Reporting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Operational Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Hourly Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Automatic Backup Failure Notification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . For More Information: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Student Exercise . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Review Questions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-26 12-27 12-28 12-29 12-29 12-30 12-31 12-33
Appendix A: Additional TSM Product Information

IBM Tivoli Storage Manager Product Information on the Web . . . . . . . . . . . . . . . . . . . . . . . . . . A-2 Optional Products for IBM Tivoli Storage Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-3 Bare Machine Recovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-5
12
Table of Contents
IBM System Storage Archive Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-6 Optional Additions to IBM Tivoli Storage Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-7 Hierarchical Storage Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-8 IBM Tivoli Storage Manager for Space Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-9 IBM Tivoli Storage Manager HSM for Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-10 IBM Tivoli Storage Manager for Storage Area Networks . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-11 Continuous Data Protection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-12
Appendix B: Problem Determination

Resolving Problems with Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-2 Problem Determination . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-4 Diagnosing the Problem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-5 Diagnosing the Problem, continued . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-6 TSM Problem Determination Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-7 What To Do before Calling Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-9 Additional Resources for TSM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-10 Education . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-11 Product Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-12 Documentation on www.ibm.com . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-13 Other Publications and Product Web Sites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-14 TSM Support Web Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-15 Additional Assistance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-16
Tivoli Professional Certification

Special Offer For Having Taken This Course . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . I Why Get Certified? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . I What Is Role-based Certification? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . I When Should I Attempt a Certification Exam? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . II Where Can I Take a Certification Exam and How Much Do They Cost? . . . . . . . . . . . . . . . . . . . . II Where Can I Get More Information? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . II
13
Table of Contents
14
Preface
Student Guide
2008 IBM Corporation
Preface
Course Description
This five-day instructor-led course provides hands-on practice in implementing a data management strategy with IBM Tivoli Storage Manager 5.5. The course begins with installing the IBM Tivoli Storage Manager 5.5 server, backup-archive clients, and the Integrated Solution Console Administration Center. Students create simple storage pools and subsequently learn to configure hierarchies of storage pools to manage the flow of data from disk to tape media. Next, storage pools are mapped to the data sent by client nodes through IBM Tivoli Storage Manager policies that provide the rules to implement data management service level agreements. Students define new policy domains, policy sets, management classes, backup copy groups, and archive copy groups. To authorize administrators to perform specific storage tasks, students register administrators and grant the privileges required to support specified responsibilities. Students back up and restore client data, as well as manage long-term and off-site data management through archiving and retrieving of client data. After learning to backuprestore and archive-retrieve data, students practice automating client operations by creating new IBM Tivoli Storage Manager schedules. To monitor client operations, students subsequently learn to configure and manage storage events. Finally, students will learn how to protect their IBM Tivoli Storage Manager server by automating the backup and restore of the IBM Tivoli Storage Manager databases and storage pools from off-site data storage pools. The Student Exercises are written for Windows 2003, Redhat Linux 4, and AIX 5.3. The lecture material covers all supported Intel and UNIX platforms. This course should be followed by IBM Tivoli Storage Manager 5.5 Advanced Administration, Tuning, and Troubleshooting.
Audience
This course is intended for system administrators and implementers who will be responsible for implementing an IBM Tivoli Storage Manager 5.5 solution.
ii
Preface
Where to Find the Training Schedules

The latest information about IBM Tivoli education offerings can be found online at http://www.ibm.com/software/tivoli/education/
IBM Software Group | Tivoli software
Where to Find More Information

Training Roadmaps Online
http://www.ibm.com/software/tivoli/education/
If you have any questions about IBM education offerings, send an e-mail to the appropriate alias for your region: Americas: tivamedu@us.ibm.com Asia Pacific: tivtrainingap@au1.ibm.com EMEA: tived@uk.ibm.com
iii
Preface
Course Prerequisites
The following list contains the prerequisite knowledge or Tivoli product knowledge that you must have before taking the course: All students should have a working knowledge of Internet browsers. All students should have a basic understanding of client-server concepts. For classes taught on a Windows platform, the students should have the skills to navigate through Windows 2003 applications. For classes taught on a Linux platform, the students should have the skills to navigate through Red Hat Linux 4 applications. For classes taught on a UNIX platform, you should have experience using the UNIX command-line interface, allocating filesystem space, and connecting devices to a UNIX server.
iv
Preface
Course Objectives
Course Objectives
Upon completion of this course, you will be able to:
Discuss the features of IBM Tivoli Storage Manager. Install IBM Tivoli Storage Manager server and backup-archive client. Navigate the Administrative interfaces. Explain the concepts of attaching a tape library and preparing media. Create and manage storage pools and storage pool volumes. Define policy management to meet business requirements. Customize the IBM Tivoli Storage Manager database and recovery log. Configure the backup-archive client. Backup, restore, archive, and retrieve client data. Protect the IBM Tivoli Storage Manager database and storage pools. Schedule administrative tasks. Monitor server and client messages and events.
3
Preface
Agenda
Agenda: Days 1 - 3
Day 1 :
Unit 1: IBM Tivoli Storage Manager Overview Unit 2: Installing IBM Tivoli Storage Manager Server and Client Unit 3: Administrative Interfaces and Privileges
Day 2:
Unit 4: Storage Media Devices Introduction Unit 5: Managing Storage Pools and Storage Pool Volumes Unit 6: Policy Management
Day 3:
Unit 7: Customizing the Tivoli Storage Manager Database and Recovery Log Unit 8: Client Configuration
4
Agenda: Days 4 and 5

Day 4:
Unit 9: Backup-Archive Client Functions Unit 10: Protecting the Database and Storage Pools
Day 5:
Unit 11: Automating Operations Unit 12: Monitoring and Event Logging Appendix A Appendix B
vi
Preface
Course Outline
The following is a high-level description of the contents of this course. This course contains 12 units. Each unit has an overview presentation, and most have a series of student exercises designed to reinforce the concepts presented. This course contains the following units: Unit 1: IBM Tivoli Storage Manager Overview This unit provides an introduction to IBM Tivoli Storage Manager and describes the major functions and features that are currently available. Unless otherwise stated, the topics introduced in this unit will be explained in greater detail in following units. Unit 2: Installing IBM Tivoli Storage Manager Server and Client This unit provides the requirements for the Integrated Solutions Console and the IBM Tivoli Storage Manager components. Topics include basic installation and configuration of the IBM Tivoli Administration Center, IBM Tivoli Storage Manager server, backup-archive client, and device driver. Unit 3: Administrative Interfaces and Privileges This unit explores the new IBM Tivoli Storage Managers Administration Center, as well as the other available user interfaces for managing IBM Tivoli Storage Manager. The levels of administrative authority required to administer IBM Tivoli Storage Manager are also presented. Unit 4: Storage Media Devices Introduction This unit introduces devices used to store data. Basic concepts of attaching a tape library and preparing media to work with IBM Tivoli Storage Manager are also discussed. Unit 5: Managing Storage Pools and Storage Pool Volumes In this unit, you will see how to create hierarchical storage pools of different media types to allow for efficient management of your data. Unit 6: Policy Management Policy management enables the administrator to determine a set of rules explaining how IBM Tivoli Storage Manager will treat data. This set of rules is composed of policy domains, policy sets, management classes, and copy groups.
vii
Preface
Unit 7: Customizing The Tivoli Storage Manager Database and Recovery Log The Tivoli Storage Manager database is used by the server to manage information about client files. The Tivoli Storage Manager recovery log is used to ensure the consistency and availability of the database. This unit covers how to choose the size and location of the database and recovery log. You will also configure the database and recovery log for improved performance.
Unit 8: Client Configuration This unit describes how to manage and configure client options and invoke the backup-archive interfaces available with IBM Tivoli Storage Manager.
Unit 9: Backup-Archive Client Functions The backup-archive client communicates with the server and invokes the client functions of Tivoli Storage Manager. The backup-archive client is supported on a variety of platforms that might reside on a user workstation or a LAN server. This unit describes the various methods available to back up, restore, archive, and retrieve data, and what options are available to customize these processes to fit your needs.
Unit 10: Protecting the Database and Storage Pools This unit covers backing up and recovering the Tivoli Storage Manager database, recovery log, and storage pools.
Unit 11: Automating Operations Central scheduling enables automation of backup, archive, and other processes. Scheduling of IBM Tivoli Storage Manager operations can be done with an external scheduler or with the built-in Tivoli Storage Manager scheduler. The Tivoli Storage Manager administrative interfaces for defining, updating, and deleting schedules will be described in this unit.
Unit 12: Monitoring and Event Logging Tivoli Storage Manager provides the ability to log client messages as server events. This unit introduces Tivoli Storage Manager logging and monitoring functions.
viii
Preface
Typographical Conventions
In this course, the following typographical conventions are used.
Convention BOLD UPPERCASE
Usage Options and parameters, when not shown in examples, will appear in BOLD UPPERCASE. Commands, keywords, file names, authorization roles, URLs, or other information that you must use literally appear in bold. Variables and values that you must provide appear in italics. Words and phrases that are emphasized also appear in italics. New terms appear in bold italics when they are defined in the text. Command examples, output, and system messages appear in a monospace font. In this manual, the arrow character is used as a path arrow. The arrow indicates the path to the named window.
Bold
Italics
Bold Italics Monospace
>
Product Information
Software Release Numbers

The Tivoli software and release numbers referred to in this guide are shown in the following table.
Tivoli Software IBM Tivoli Storage Manager
Release Number 5.5
ix
Preface
Product Documentation
IBM Tivoli product documentation is available on the Student Resources CD. For access to documentation outside the classroom environment, visit the IBM Web site.
Suggestions in this Course

Suggestions and best practices provided in this course are the results of product testing and monitoring in a variety of test and production environments. Results may vary in your environment. Refer to the documentation for your platform for more information.
1-1
Introduction
This unit provides an introduction to IBM Tivoli Storage Manager and describes the major functions and features that are currently available. Unless otherwise stated, the topics introduced in this unit will be explained in greater detail in following units. Note: In this course, IBM Tivoli Storage Manager is also referred to as Tivoli Storage Manager and TSM. Most of the IBM Tivoli Storage Manager commands are platform independent. The examples in this course are shown for Windows and AIX platforms. Refer to the documentation for the other supported platforms for specifics pertaining to commands issued outside of Tivoli Storage Manager. When commands are shown in mixed case, the capitalized letters are the command shortcut. For the command to query the system, you only need to type q sys. The shortcut looks like this:
Query SYStem
Other terms used in this course: Administrative Client: A program that is used to manage the TSM server API: Application program interface Backup-Archive Client: A program that allows backup and recovery of data Client (TSM client): A TSM managed node GUI: Graphical User interface LAN: Local area network Navigation Tree: An expandable menu that shows directory structures Node (managed node): A workstation or file server with the client installed SAN: Storage area network Select action menu: Drop-down menu or expandable text box menu in the Administration Center Server (TSM server): A program that manages Tivoli Storage Manager functions Storage Agent: A program that allows backup and recovery on a SAN WAN:Wide area network
1-2
Objectives
Objectives
Upon completion of this unit, you will be able to:
Identify how IBM Tivoli Storage Manager serves as a tool for data management and protection.
Identify major components of the IBM Tivoli Storage Manager solution.
Identify the IBM Tivoli Data optional products that are part of the IBM Tivoli Storage Manager solution.
1-3
Unit 1: IBM Tivoli Storage Manager Overview Protecting Data with IBM Tivoli Storage Manager
Lesson 1: Protecting Data with IBM Tivoli Storage Manager

IBM Tivoli Storage Manager: An EnterpriseWide Solution
Overview of IBM Tivoli Storage Manager: An Enterprise-Wide Solution

IBM Tivoli Storage Manager stores copies of data off-site. IBM Tivoli Storage Manager scales to protect hundreds of computers running a variety of operating systems. IBM Tivoli Storage Manager provides intelligent data move and store techniques.
Local Area Network
Storage Area Network
IBM Tivoli Storage Manager protects your organizations data from hardware failures and other errors by managing backup and archive copies of data. These copies should be stored off-site. Designed for a heterogeneous environment, IBM Tivoli Storage Manager connects over the local area network (LAN), wide area network (WAN), Internet, and storage area network (SAN) to provide smart data move and store techniques, comprehensive policybased automation and data management. Optional modules allow business-critical applications that must run twenty-four hours a day, seven days a week (24x7), to use Tivoli Storage Managers centralized data protection with no interruption to their service.
1-4
IBM Tivoli Storage Manager Components

IBM Tivoli Storage Manager Components

TSM backup-archive and Web clients
Administration Center administrative scheduler recovery log backup-archive scheduler
storage pools TSM database policy-based management
storage devices
TSM server
4
Administrative Interface Tivoli Storage Manager Server Scheduler Backup-Archive Client Tivoli Storage Manager Database Tivoli Storage Manager Recovery Log Storage Pools Policy-Based Management Tape Library
For information about supported devices, check the IBM Tivoli Storage Manager supported devices links at http://www.ibm.com/software/tivoli/products/storage-mgr/ platforms.html.
1-5
Interface
Interfaces
Interface: Administration Center GUI Backup-Archive (BA) Client GUI How interface is accessed: ISC logon
dsm
(Windows)
dsmj (UNIX)
Web Client GUI BA Client Command Line TSM Server Command Line TSM Sever GUI Web browser and port 1581
dsmc dsmadmc, Administration

Center, and Server Console Windows MMC Console
The Tivoli Storage Manager Administration Center, which operates on the Integrated Solutions Console (ISC), provides a task-oriented graphical user interface for storage administrators. Tasks such as creating server maintenance scripts, scheduling, adding storage devices, setting policy domains, user management, and viewing the Health Monitor are some of the tasks the Administration Center provides. Command line, graphical user interface (GUI), and a Web client are also provided. Administrative interfaces are covered in Unit 3.
1-6
Tivoli Storage Manager Server

Tivoli Storage Manager Server

In a traditional LAN configuration, the role of a Tivoli Storage Manager server is to store the backup or archive data from the backuparchive clients that it supports to storage media. The server also has a database of information to keep track of the data it manages, including policy management objects, users and administrators, and client nodes. Tivoli Storage Manager server refers to an instance, not a physical system. You can have multiple instances of the server on the same system.
1-7
Scheduler
Scheduler
Administrator-defined schedules allow for the automation of Tivoli Storage Manager server and backup-archive client operations. A comprehensive and integrated set of schedules can provide the basis for efficient data management with little need for intervention during normal operations. Scheduling Tivoli Storage Manager backup-archive client operations consists of schedules on the Tivoli Storage Manager server and a scheduler component that runs on the Tivoli Storage Manager backuparchive client machine.
Administrative scheduling and client scheduling are covered in Unit 11.
1-8
Backup-Archive Client
Backup-Archive Client
The TSM backup-archive client is a service which sends data to and retrieves data from, a TSM server. The TSM backup-archive client must be installed on every machine that needs to transfer data to server-managed storage called storage pools. This machine might be a workstation or a file or database server. The TSM server uses a unique node name to identify each TSM backuparchive client instance. The TSM backup-archive client supports encryption, and a password can be used to authenticate communications between the TSM backup-archive client and server.
A backup-archive client can actually be a server. Application servers and file servers, as well as desktop workstations and portable PCs, are backup-archive clients to the Tivoli Storage Manager server.
1-9
Tivoli Storage Manager Database

Tivoli Storage Manager Database

Tivoli Storage Manager saves information in the Tivoli Storage Manager database about each file, raw logical volume, or database that it backs up, archives, or migrates. This information includes the file name, file size, management class, copy group, location of the files in Tivoli Storage Manager server storage, and all other information except for the data. Data is stored in a storage pool. The Tivoli Storage Manager database is the heart of IBM Tivoli Storage Manager. Later in this course you will see how to protect the TSM database, because without the database, data cannot be restored.
The Tivoli Storage Manager database does not require database administration skills to manage. The TSM database is discussed in Unit 7.
1-10
Tivoli Storage Manager Recovery Log

Tivoli Storage Manager Recovery Log

The recovery log, which is structured like the Tivoli Storage Manager database, keeps track of all changes made to the database. If a system outage were to occur, a record of the changes would be available for recovery.
10
The recovery log is covered in Unit 7.
1-11
Storage Pools
Storage Pools
Storage pools are collections of like media that provide storage for backed up, archived, and migrated files. These pools can be chained in order to create a storage hierarchy. Any supported sequential media can be used in all copy storage pools. Data migration, left diagram: from the primary disk pool to copy file pools or copy disk pools to tape pools primary storage pool copy storage pools Data migration, right diagram: from the primary disk pool directly to tape pools
11
Managing storage pools and storage pool volumes is covered in Unit 5. In Unit 10, protecting the storage pools is described. A storage pool volume is the basic unit of storage for the IBM Tivoli Storage Manager storage pools. A volume can be a logical volume, a standard file system file, a tape cartridge, or an optical cartridge. Each volume is identified by a unique volume identifier.
1-12
Policy-Based Approach to Data Management

Backup-archive client data is centrally managed by business policy. Policies are created by the administrator and stored in the database on the server.
Policy-Based Approach to Data Management

Policies enable data management based on business requirements by defining: Which files are eligible for back up Which files are eligible for archive Where the data is stored How long the data is retained How many versions are retained
12
Policies are defined based on the business requirements for data backup and retention. These requirements, sometimes referred to as a storage service level agreement, identify when backups will be performed, how long and how many copies of files will be retained, and other requirements specified by the customer. This feature makes it possible for different departments with different types of data to have their own customized storage management plan. Policies are covered in Unit 6.
1-13
Tape Library
Tape Library
IBM Tivoli Storage Manager supports a variety of library types, including manual libraries, SCSI libraries, 349X and 358X (LTO) libraries, and external libraries. A tape library is essentially a box that holds drives and cartridges, and provides automation for tape operation.
13
Configuration steps for adding a tape library are discussed in Unit 4.
1-14
Backup-Restore Functionality Provided by IBM Tivoli Storage Manager

Tivoli Storage Manager can perform backups of both files and raw logical volumes. When backing up files, the Tivoli Storage Manager server database keeps a list of all files and their attributes (time, date, size, access control lists, and extended attributes).
Backup-Restore Functionality with IBM Tivoli Storage Manager
BACKUP
The backup-archive clients send copies of files to Tivoli Storage Manager server.
RESTORE
The files are returned to the backup-archive client. .
The Tivoli Storage Manager server stores the copies in the storage pools.
When a restore is requested by the backup-archive client, the storage pool sends the copy back to the server.
14
Raw logical volumes are treated as separate entities, and the management class policy is applied to the entire image as a whole. There is no tracking of individual files in an image backup because it is treated as a separate object. Backup: Creates a copy of a file to protect against the operational loss or destruction of that file. Customers control backups by defining the backup frequency and number of versions. Restore: Places backup copies of files into a customer-designated system or workstation after the loss of a file. By default, the most recent version of each active file requested is replaced.
There are four levels of backup available: byte level (small amounts of data, like on notebook computers), block level (bigger amounts of data, between 40 KB and 2 MB), file level (normal files), and image level (includes file system and files). IBM Tivoli Storage Manager uses Progressive Backup Methodology, also known as Incremental backups. Backup and restore functions are covered in Unit 10.
Copyright IBM Corp. 2008 IBM Tivoli Storage Manager 5.5 Implementation and Administration
1-15
Long-Term Storage Capabilities Provided through the Archive-Retrieve Function

The Tivoli Storage Manager archive function stores selected files unconditionally on the server, according to the applicable management class limits. Unconditionally means that there is no version limit, and the files will be retained for the defined time period regardless of whether they are deleted on the client.
Archive-Retrieve Functionality with IBM Tivoli Storage Manager
ARCHIVE
The backup-archive clients send copies of files for retention to Tivoli Storage Manager server.
RETRIEVE
A copy of the files are returned to the backup-archive client. .
The Tivoli Storage Manager server stores the copies in the storage pools.
When a retrieve is requested by the backup-archive client, the storage pool sends a copy of the data retained in the storage pool.
15
Archiving is useful when you want to store data that is infrequently accessed but must still be kept available. Also it is not uncommon to have a legal requirement to archive business records for extended periods of time, and the archive function is ideal for this purpose. IBM Tivoli Storage Manager has the capability of archiving for 30 years. Archive: Creates a copy of a file or set of files for vital record retention of data, such as patent information, financial information, or customer records. Customers control archive by defining the retention period. This feature enables customers to keep unlimited archive copies of a file. Retrieve: Allows users to copy an archive file from the storage pool to the workstation. The archive copy in the storage pool is not affected.
Archive and retrieve functions are covered in Unit 9.
1-16
Administrator Management Capabilities

IBM Tivoli Storage Manager enables customers to register administrators and to grant administrators the ability to accomplish specific tasks. Administrators can access the user interfaces to issue queries and perform Tivoli Storage Manager tasks. To perform other server functions, administrators must be granted authority by being assigned one or more administrative privilege classes.
E
Administrator Management Capabilities

System Privileges Storage Privileges Operator Privileges
All Tivoli Storage Manager server tasks. Database, recovery log, and storage pool management. Commands for server availability, resource usage, and physical media management. Policy domain, policy set, management class, copy group, and schedule management. Review and reset server statistics. Client actions, product usage, and activity monitoring.
16
Policy Privileges
Analyst Privileges Node Privileges
1-17
The Administration Center on the Integrated Solutions Console

IBM Tivoli Storage Managers Administration Center on the Integrated Solutions Console
The Administration Center provides centralized IBM Tivoli Storage Manager enterprise management from the Integrated Solutions Console (ISC).
17
The graphical user interface (GUI) for managing IBM Tivoli Storage Manager administrative functions is called the Administration Center. This GUI runs on IBMs Integrated Solutions Console (ISC), a WebSphere application designed for centralized management of IBM enterprise applications, including IBM Tivoli Storage Manager.
1-18
Managing IBM Tivoli Storage Manager with the Administration Center

Managing IBM Tivoli Storage Manager with the Administration Center

Benefits of the IBM Tivoli Storage Manager Administrative Center: Centralized Web administration of multiple TSM servers Access to administrative command line Administrative task wizards to manage: Enterprise configuration Storage devices Policies Client nodes Service maintenance
Administration Center
18
These tasks will be explored in detail in the following units of this course.
Automation Capabilities Provided by IBM Tivoli Storage Manager

IBM Tivoli Storage Manager includes a central scheduling component that allows the automatic processing of administrative commands and backup-archive client operations during a specific time period when the schedule is activated. An administrator is responsible for creating and maintaining the schedules in each policy domain. Tivoli Storage Manager scheduling is split into two categories: administrative scheduling and backup-archive client scheduling. Note: IBM Tivoli Storage Managers administration functions can also be issued from a command line. Some command-line examples are included in this course. For details on command-line syntax, refer to the users documentation provided with your product.
1-19
Unit 1: IBM Tivoli Storage Manager Overview Data Storage and Data Management
Lesson 2: Data Storage and Data Management

Types of Storage Media on which Tivoli Storage Manager Stores Data
Storage media can be disks and sequential media, like optical and tape, assigned to a storage pool, which is the data area on the Tivoli Storage Manager server that holds client backuparchive data. For sequential access storage, Tivoli Storage Manager supports many device and media types. To obtain the most recent list of supported devices, check the IBM Web site.
Types of Storage Media on which Tivoli Storage Manager Stores Data
Tivoli Storage Manager server
storage pools
Tivoli Storage Manager supports many tape and optical libraries and a variety of storage media types for copy storage pools, such as:
WORM Optical Disk
CD-RW DVD-RAM File

19
Storage pools contain backup files, archived files and space managed files. These storage pools are chained in order to create a storage hierarchy. The disk pool is usually first in the chain and is generally followed by tape. This is called a hierarchy.
1-20
Optional IBM Tivoli Storage Manager Products

This course covers the basic IBM Tivoli Storage Manager functions. These additional products and features are briefly discussed in Appendix A and covered in other IBM Tivoli Storage Manager classes.
Optional Products for IBM Tivoli Storage Manager

IBM Tivoli Storage Manager for Mail IBM Tivoli Storage Manager for Hardware IBM Tivoli Storage Manager for Databases IBM Tivoli Storage Manager for Application Servers IBM Tivoli Storage Manager for Enterprise Resource Planning
These products were previously known as Tivoli Data Protection agents, or TDPs.
IBM Tivoli Storage Manager for System Backup and Recovery

Previously known as Tivoli SysBack
IBM System Storage Archive Manager

Previously known as IBM Tivoli Storage Manager for Data Retention
20
1-21
IBM Tivoli Storage Managers Disaster Preparation and Recovery

IBM Tivoli Storage Managers Disaster Recovery

With Disaster Recovery Management, you can: Prepare a disaster recovery plan. Manage your off-site volumes and track media. Manage your client data.
21
IBM Tivoli Storage Managers Disaster Preparation and Recovery, or Disaster Recovery Manager (DRM), is covered in detail in the IBM Tivoli Storage Manager Extended Edition 5.5 Disaster Recovery Manager course (see the IBM Web site for IBM Tivoli Storage Manager curriculum roadmap). It is discussed here, since DRM is mentioned as a best practice for protecting your TSM database. IBM Tivoli Storage Managers Disaster Preparation and Recovery offers various options to configure, control, and automatically generate a disaster recovery plan containing the information, scripts, and procedures needed to automate restoration and help ensure quick recovery of your data after a disaster. It also manages and tracks the media on which your data is stored, whether on-site, in transit, or in a vault, so that your data can be easily located if disaster strikes. The scripts can help you document your basic information technology recovery strategy, the steps to rebuild your core systems, and the critical machines that you must recover.
1-22
Unit 1: IBM Tivoli Storage Manager Overview Licensing
Lesson 3: Licensing
IBM Tivoli Storage Manager Licensing
There are three license types for IBM Tivoli Storage Manager version 5.5. They are tsmbasic.lic for the basic version of IBM Tivoli Storage Manager 5.5, tsmee.lic for the Extended Edition of IBM Tivoli Storage Manager version 5.5, and dataret.lic for the IBM Tivoli Storage Manager for Data Retention version 5.5.
IBM Tivoli Storage Manager Licensing

Licensing for all systems must be at either the IBM Tivoli Storage Manager or IBM Tivoli Storage Manager Extended Edition level. Licenses cannot be mixed at a site level. There are three license files: tsmbasic.lic tsmee.lic dataret.lic
For licensing information, refer to the document titled IBM Tivoli Storage Manager Read This First.
22
For the Extended Edition license, you choose the advanced storage management functions you will need. Always read the documentation shipped with the product code for the latest information on licensing.
Upgrading from IBM Tivoli Storage Manager Express

When the TSM Extended Edition license is installed on a system upgrading from TSM Express, it automatically upgrades the Express license.
1-23
Review Questions
1. Which of these actions copies the file, and then copies the changed portion of that file to protect it against operational loss or destruction? a. archive b. backup c. retrieve d. restore 2. Which of the following functions returns the backup copies of files? a. return b. recall c. retrieve d. restore 3. IBM Tivoli Storage Manager uses a _______________ backup methodology to back up only changed data. 4. The Tivoli Storage Manager ___________ client must be installed on every machine that will transfer data to server-managed storage. 5. IBM Tivoli Storage Manager saves information in the TSM _________________ about each file that it backs up, archives, or migrates.
1-24
Review answers begin on the next page.
1-25
Review Answers
1. Which of these actions copies the file, and then copies the changed portion of that file to protect it against operational loss or destruction? a. archive b. backup c. retrieve d. restore b. backup 2. Which of the following functions returns the backup copies of files? a. return b. recall c. retrieve d. restore d. restore 3. IBM Tivoli Storage Manager uses a _______________ backup methodology to back up only changed data. progressive or incremental 4. The Tivoli Storage Manager ___________ client must be installed on every machine that will transfer data to server-managed storage. backup-archive 5. IBM Tivoli Storage Manager saves information in the Tivoli Storage Manager _________________ about each file that it backs up, archives, or migrates. database
1-26
Summary
Summary
You should now be able to:
Identify how IBM Tivoli Storage Manager serves as a tool for data management and protection. Identify major components of the IBM Tivoli Storage Manager solution. Identify the IBM Tivoli Data Protection products that are part of the IBM Tivoli Storage Manager solution.
23
1-27
1-28
2-1
Introduction
This unit provides the requirements for the Integrated Solutions Console and the IBM Tivoli Storage Manager components. Topics include basic installation and configuration of the IBM Tivoli Administration Center, IBM Tivoli Storage Manager server, backup-archive client, and device driver.
Objectives
Objectives
Describe the Integrated Solutions Console installation requirements. Install IBM Tivoli Storage Manager Administration Center. Install IBM Tivoli Storage Manager server. Install IBM Tivoli Storage Manager backup-archive clients. Install the administrative command line. Describe the IBM Tivoli Storage Manager device driver installation.
2-2
Unit 2: Installing IBM Tivoli Storage Manager Installation Overview
Lesson 1: Installation Overview

Installation Overview
Refer to the IBM Tivoli Storage Manager Installation Guide for your platform for the steps to perform the installation. TSM 5.5 Installation Guide
The following components will need to be installed: IBM Tivoli Storage Manager Server IBM Tivoli Storage Manager Backup-Archive Client IBM Integrated Solutions Console (ISC) IBM Tivoli Storage Manager Administration Center
IBM Tivoli Storage Manager 5.5 Packaging Contents

Tivoli Storage Manager: Operational Reporting Administration Center Linux Server HP-UX Server Solaris Server Windows Server AIX Server Desktop Clients (Windows Clients)

2-3
AIX Clients OS/400 API Clients Linux CLients UNIX Clients (non-AIX)
IBM Integrated Solutions Console version 6.0.1.1 (version 6.0.1 with fix pack 1): Note: If ISC 5.1 is installed, the package will install ISC 6.0.1.0 and then install ISC Fix Pack 1. If ISC 6.0.1.0 is already installed, the package will only install ISC Fix Pack 1. In all cases, ISC 6.0.1.1 will become the installed version. AIX for use with Tivoli Storage Manager Administration Center Windows for use with Tivoli Storage Manager Administration Center Linux xSeries for use with Tivoli Storage Manager Administration Center Solaris for use with Tivoli Storage Manager Administration Center
2-4
System Requirements for IBM Tivoli Storage Manager Server

System Requirements for IBM Tivoli Storage Manager Server

Requirements for: Hardware AIX 64-bit RISC System/6000 or pSeries system AIX 5.3 or above running in a 64-bit environment 200 MB 1 GB TCP/IP (version 4 or 6) Shared Memory Mozilla 1.0.2, 1.3, and 1.4 Mozilla Firefox 1.0 Windows Intel Pentium processor or compatible multiprocessor based system Microsoft Windows 2003 Server
Operating System
Disk Space Memory Client Communication Method Web Browser
110 MB 128 MB (256 MB is preferred) TCP/IP (version 4 or 6) Named Pipes Shared Memory Microsoft Internet Explorer 6.x Mozilla 1.0.2, 1.3, and 1.4 Netscape 6.2 and 7.
4
This course describes performing a new installation. To update an existing version of Tivoli Storage Manager, refer to the product documentation. Install and use JRE 1.4.1 or later to optimize performance of the Java backup-archive client. Tivoli Storage Manager implements a simple network management protocol (SNMP) subagent. You can configure the SNMP subagent to send traps to an SNMP manager, such as Tivoli NetView, and to provide support for a management information base (MIB). For details about configuring SNMP for use with Tivoli Storage Manager, see the IBM Tivoli Storage Manager Administrator's Guide for your platform.
2-5
System Requirements for Linux IBM Tivoli Storage Manager Server
System Requirements for Linux IBM Tivoli Storage Manager Server

Linux IA64 server requirements:
An ITANIUM 256 MB of RAM 72 MB hard disk space Operating system requirements: Red Hat Enterprise Linux 4 or 5 SUSE Linux Enterprise Server 9 or 10 Version 2.3.3-98 or higher of the GNU C libraries installed on the Tivoli Storage Manager machine. Communication Protocol: TCP/IP (version 4 or 6) Shared Memory Protocol
Linux X86 server requirements:

An i686 symmetric multiprocessor (SMP), or uniprocessor (UP) 256 MB of RAM 72 MB hard disk space Operating system requirements: Red Hat Enterprise Linux 4 or 5 SUSE Linux Enterprise Server 9 or 10 Asianux 2.0 Version 2.2.5-213 or higher of the GNU C libraries installed on the Tivoli Storage Manager machine. Communication Protocol: TCP/IP (version 4 or 6) Shared Memory Protocol
Refer to the IBM Web site and documentation for requirement for Linux on zSeries server and Linux on Power server.
5
Supported Platforms Listed on www.ibm.com
Always refer to the IBM Web site for the latest information about supported operating environments for Tivoli Storage Manager.
2-6
Backup-Archive Client Prerequisites

IBM Tivoli Storage Manager, version 5.5 clients are supported on the following operating systems: AIX 5.3 (32-bit and 64-bit) and AIX 6.1 (64 bit) HP-UX 11i v2 (32-bit or 64-bit) and HP-UX 11i v3 Linux Itanium 2 (SUSE Linux Enterprise Server 9 or 10; Red Hat Enterprise Linux 4.0 or 5.0) Linux x86/x86_64 (SUSE Linux Enterprise Server 9 or 10; Red Hat Enterprise Linux 4.0 or 5.0; Asianux 2.0; Novell OES) Linux on POWER (SUSE Linux Enterprise Server 9 or 10; Red Hat Enterprise Linux 4.0 or 5.0) Linux for zSeries (SUSE Linux Enterprise Server 9 or 10; Red Hat Enterprise Linux 4.0 or 5.0) Macintosh OS X (10.5) Novell NetWare 6.5 SP5, 6, 7 z/OS UNIX System Services (z/OS V1R7, V1R8, or V1R9) Sun Solaris 9 or10 32-bit or 64-bit kernel mode (SPARC) Sun Solaris 10 32-bit and 64bit kernel mode (x86) Tru64 UNIX, Version 5.1A (with V5.1 functional client) Windows XP (32 bit and 64 bit), Windows Server 2003 (32 bit or 64 bit), Windows Vista (except Automated System Recovery)
2-7
Integrated Solutions Console and TSM Administration Center

Integrated Solutions Console and TSM Administration Center

B-A Client B-A Client B-A Client B-A Client B-A Client
TSM Administration Center
TSM Server
TSM Server
B-A Client
ISC
TSM Server
B-A Client B-A Client
B-A Client
The Administration Center is a Web-based interface that can be used to centrally configure and manage IBM Tivoli Storage Manager servers. The Administration Center is installed as an IBM Integrated Solutions Console component. The Integrated Solutions Console, an IBM WebSphere application, allows you to install and access components provided by multiple IBM applications. It makes tasks easier by grouping previously separate tasks together to make a process simpler such as adding hardware or creating new storage pools.
2-8
ISC and Administration Center Requirements

ISC and Administration CenterHardware Requirements

Physical memory Disk space 1 GB or more for runtime installations Installation media location: 505 MB Temporary space: 75 MB Installation location: 650 MB Refer to the Installation Guide and README file (on your Student Resources CD). Double the physical memory A network adapter and connection to a physical network that can carry IP packets Always check the IBM Web site for latest requirements.
8
Processor Virtual memory or swap space Network connectivity
Also required: Port 8421 A static IP address A configured, fully qualified host name
Administration Center Requirements

Only ISC 6.0.1.1 is supported. ISC platforms supported:
SUSE Linux Enterprise Server (SLES) 10 Solaris 10 Red Hat Enterprise Linux (RHEL) 5 Internet Explorer 7 for XP Internet Explorer 7 for Vista Firefox 2.0
TSM Server 5.4.0 or higher. Migration is handled by the install package.

Browsers: Microsoft Internet Explorer 6.x (Windows only) Mozilla 1.0.2, 1.3 and 1.4, including Mozilla Firefox 1.0 JRE 1.4.1 or higher Macromedia Flash Plug-in (required for the included tutorials)
9
See the README file for details regarding operating system fixes and patches.

2-9
Unit 2: Installing IBM Tivoli Storage Manager Installing IBM Tivoli Storage Manager
Lesson 2: Installing IBM Tivoli Storage Manager

Installing IBM Tivoli Storage Manager on Windows
Main Menu
Installing IBM Tivoli Storage Manager Server on Windows: Main Menu
10
After inserting the IBM Tivoli Storage Manager Windows Server CD, the CD browser appears with a main menu. IBM Tivoli Storage Manager will let you know if it detects a previous version installed. Installing Tivoli Storage Manager Server on Windows is a simple InstallShield process. You will be prompted to enter the language for the installation. This language setting applies only to the language used for the installation.
2-10
Select Product to Install

Select Product to Install
11
Selecting Install Products will display the Install Products window. The installation sequence is indicated by the product layout provided on the Install Products screen. The default user ID is admin and the default password is admin.
2-11
Install TSM Server

Install TSM Server
12
Start Installation and Accept License Agreement
13
2-12
Follow the Wizard Steps
Customer Information and Select Type Screens
Customer Information and Select Type Screens
14
Use the Custom installation type if you want to specify parameters such as an installation directory or language support.
Note: If all of your servers have the default name, SERVER1, you will be able to add only one of them to the Administration Center. Use the set servername command to specify the new server name.
2-13
Installing and Completing the InstallShield Wizard
Installing
15
Server Installation is Complete
16
2-14
TSM Server Licenses

TSM Server Licenses
17
License Installation
Complete all wizard steps.
18
2-15
Install Language Packs

.
Install Language Packs, If Required
19
2-16
Install Device Drivers
Install Device Drivers
Use IBM device drivers for IBM libraries.
Complete all wizard steps.
20
To use a device, you must install the appropriate device driver. Tivoli Storage Manager provides its own device driver for non-IBM devices. For Windows platforms, an InstallShield Wizard is provided for modifying, repairing, installing, or removing the IBM Tivoli Storage Manager device driver. Tivoli Storage Manager also supports non-IBM vendor device drivers if the devices are associated with the GENERICTAPE device class and the hardware vendor also supports that device driver. Using a device class other than GENERICTAPE with a non-IBM vendor device driver is not suggested. The Tivoli Storage Manager device driver is generally preferred for use with Tivoli Storage Manager. It is required for use with automated library devices and optical disk devices unless you are using Windows Removable Storage Manager to manage media. Refer to your device manufacturers documentation.
2-17
Installing Tivoli Storage Manager on AIX
Installing Tivoli Storage Manager on AIX

The packages selected during the server installation on AIX include:
Server code Message catalog License support

smitty
21
The AIX installation of IBM Tivoli Storage Manager 5.5 is performed using smit or smitty. Choose Software Installation and Maintenance > Install and Update Software > Install and Update from ALL Available Software. Select the input device, list and select software, and accept new license agreements. The server directory (/usr/tivoli/tsm/server/bin) contains: Storage pool volumes (backup.dsm, archive.dsm, spcmgmt.dsm) Database volume (db.dsm) Recovery log volume (log.dsm) Server code and licensing
Using smit or smitty, fill in the fields to install the Tivoli Storage Manager server. When installing the IBM Tivoli Storage Manager Server on AIX, you will choose between the 32-bit platform and the 64-bit platform files. Issue the following command to see if your AIX system is 32 bit or 64 bit.
bootinfo -K

2-18
The following packages install the Tivoli Storage Manager server: tivoli.tsm.server.com (for both 32 bit and 64 bit) tivoli.tsm.server.rte for 32 bit tivoli.tsm.server.aix5.rte
Complete the Smit or Smitty Installation Fields
Complete the Smit or Smitty Installation Fields
22
2-19
AIX Installation Steps
AIX Installation Steps

1. Halt the Tivoli Storage Manager server from the Tivoli Storage Manager server console or from an Administrative client session. 2. Log in as the root user. If you do not log in as root, certain key Tivoli Storage Manager functions will not work properly. 3. Load the AIX server CD into the selected drive. 4. Access smit and make selections according to the level of your AIX operating system.
smitty install_update
5. Then select
Install and Update Software Install and Update from ALL Available Software
23
AIX Installation Steps, continued

6. Select the INPUT device that you are using for the installation. You can enter the drive name in the window or press F4 to access the device list. If you press F4, select the CD drive that you are using for the installation (for example, /dev/cd0). 7. Press Enter. 8. Select Software to Install. The value of the environment variable LANG controls which translated messages, help, and device selection messages in smit are automatically installed. 9. Press F4 or Esc + 4 for the latest available software packages. 10. Select the appropriate file sets to install for your configuration: F7 or Esc + 7. 11. Accept new license agreements. 12. If you are working in a language other than U.S. English, you must also install your specific language pack in addition to the required U.S. English language pack. 13. Press Enter.
24
2-20

14. Set COMMIT software updates? to yes: F4 or Esc + 4. 15. Set SAVE replaced files? to No. 16. Check the default settings for the options on this window. Ensure all your selected file sets show success. 17. Press Enter. 18. smit responds:
ARE YOU SURE?...
19. Press Enter. This installation can take several minutes. 20. After the installation is complete, press F10 to exit from smit, and remove the CD.
25
2-21
Installing Message Catalog (Languages) and Device Driver
Installing a Message Catalog for a Specific Language on AIX

If you are running with 32-bit or 64-bit hardware, install the message catalogs that correspond to the appropriate language for the environment.
For example: tivoli.tsm.msg.en_US.server
26
Installing the Device Driver on AIX

The packages installed during the server installation process that provide SCSI and Fibre Channel Protocol (FCP) support are:
tivoli.tsm.msg.en-US.devices tivoli.tsm.devices.aix5.rte
For AIX 5.1 and later, tivoli.tsm.devices.aix5.rte is required, regardless of the kernel mode.
Use IBM device drivers for IBM libraries.
27
2-22
Installing Tivoli Storage Manager on Linux
Linux Installation Overview

There is one directory that contains the RPM packages for each platform supported by Tivoli Storage Manager on Linux. The directory content is as follows: ia64/ - contains rpm packages to be installed on 64-bit Red Hat Enterprise Linux 4 and 5; SUSE Linux Enterprise Server 9 and 10 i686/ - contains rpm packages to be installed on Red Hat Enterprise Linux 4 and 5; SUSE Linux Enterprise Server 9 and 10 s390x/ - contains rpm packages to be installed on Red Hat Enterprise Linux 4 and 5; SUSE Linux Enterprise Server 9 and 10 ppc64/glibc-2.3/ - contains rpm packages to be installed on Red Hat Enterprise Linux 4; SUSE Linux Enterprise Server 9 and 10 noarch/ - contains packages for support on various languages other than English and they are to be installed on any Tivoli Storage Manager supported Linux environment. Refer to the IBM Tivoli Storage Manager for Linux Version 5.5 Installation Guide for more details.
28
Basic installation steps for Red Hat Linux 4:

1. Log in as the root user. If you do not log in as root, you will not be able to install Tivoli Storage Manager. 2. Tivoli Storage Manager will be installed from the local directory /opt/tivoli/ server_install. To install the server on Linux, you must accept the license agreement. Perform the following steps. a. Run the install_server script.
# cd /opt/tivoli/server_install # ./install_server
b. The installation menu will display the license agreement and ask for you to accept them. To accept the license agreement, press 1, and Enter. 3. After you have accepted the license agreement, a menu will be displayed with all the available RPM packages for the corresponding platform. To display the remaining items in the menu, press the spacebar.

2-23
4. Choose BASIC INSTALL by typing B to install the Tivoli Storage Manager server. The install_server script will issue the rpm -i command to perform a fresh install of the following Tivoli Storage Manager packages: a. TIVsm-server-5.5.0.0 b. TIVsm-licenses-5.5.0.0 5. Type Y and Enter to continue with the basic install process. The script then goes back to the main installation menu. 6. Type Q and Enter to quit the installation script. 7. The server has successfully installed.
2-24
Unit 2: Installing IBM Tivoli Storage Manager What the Server Installs
Lesson 3: What the Server Installs

Basic Components Installed by IBM Tivoli Storage Manager

TSM database schedule
DSMSERV.OPT DSMSERV.DSK
policy
recovery log
BACKUPPOOL ARCHIVEPOOL SPACEMGPOOL DISKPOOL

(Windows)
FILPOOL1
(Windows; Minimum Configuration) 29
When the installation is complete, the TSM server will have created the components listed on the slide. These components will be explored in greater detail in following units.
Basic Components Installed by IBM Tivoli Storage Manager

The basic Tivoli Storage Manager server installation will create the following: TSM Database: Contains information about policy, schedules, and the activity log. Recovery Log: Contains information about all changes to the database. DSMSERV.OPT: Contains server configuration options. DSMSERV.DSK: (on most platforms) Identifies the fully qualified name of the database and recovery log.
2-25
BACKUPPOOL: Disk storage for backed up data. ARCHIVEPOOL: Disk storage for archived data. SPACEMGPOOL: Disk storage for data. This pool is used to save space. DISKPOOL: Disk storage on Windows only. FILPOOL1: Disk storage with a device class of file, on Windows (using the minimal configuration option) only. POLICIES: The two default Policy Sets are named ACTIVE and STANDARD. SCHEDULES: The two default schedules are named DAILY_INCR and WEEKLY_INCR.
2-26
Files Created during Installation

Files Created during Installation

Server installation created files
Database file Database size Recovery log file Recovery log size Server option file Backuppool file Backuppool size Archivepool file Archivepool size Diskpool file Diskpool size Spacemgpool file Spacemgpool size spcmgmt.dsm 8 MB spcmgmt.dsm 8 MB
30
AIX
db.dsm 17 MB log.dsm 9 MB dsmserv.opt backup.dsm 8 MB archive.dsm 8 MB not applicable db.dsm 17 MB
Linux
Windows
db1.dsm 13 MB log1.dsm 9 MB dsmserv.opt Points to diskpool
log.dsm 9 MB dsmserv.opt backup.dsm 8 MB archive.dsm 8 MB not applicable
Points to diskpool
disk1.dsm 4 MB Points to diskpool
When installing with the minimal configuration method, Filpool1 is created.
2-27
Verify that the Server Installation Has Completed Successfully

Verify that the Server Installation Has Completed Successfully

Verify the server has successfully installed by issuing several QUERY commands from an administrative client or the server console. Query commands are covered later in this unit. Use the format=detail option. query status: shows if the server is enabled query stgpool: shows that the installation set up storage pools query db: shows that the installation set up the default database query log: shows that the installation set up the default recovery log query option: shows that the installation set up options in dsmserv.opt file
Once you have the backup-archive client installed, back up client data from a backup-archive client to verify the server was installed successfully. Do not exceed your storage pool capacity.
31
Installations can be verified on Windows systems by viewing the initserv.log file. On AIX systems, examine the contents of the install.trace file located in the TSM server installation directory.
2-28
Unit 2: Installing IBM Tivoli Storage Manager Installing the IBM Integrated Solutions Console ISC
Lesson 4: Installing the IBM Integrated Solutions Console ISC
Installing the IBM Integrated Solutions Console (ISC)
32
Course prerequisites assume program installation knowledge on your Tivoli Storage Manager server and client platform. Installation is one case where platform-specific issues come up. This class uses the Windows 2003, AIX, or Red Hat Linux platforms for the exercises. After reading the README file for system fixes and patches, install the ISC by following the InstallShield steps.
2-29
Verify Space Requirements
Space for Installation
33
Use the information in the README file to plan which server to use for the ISC.
2-30
Accept License Agreement

License Agreement
34
User ID and Password
35
In the lab exercises, the user ID is iscadmin and the password is iscadmin.

2-31
Select Directory, Paths, and Review Installation Information

Directory and Ports
36
Review before Installing
37
2-32
ISC Installation Steps

Installation Steps
38
ISC Installation Summary
39
2-33
Unit 2: Installing IBM Tivoli Storage Manager Administration Center Installation
Lesson 5: Administration Center Installation

Administration Center Installation
40
After installing the ISC, install the IBM Tivoli Storage Manager Administration Center.
2-34
ISC Configuration and Option Summary

Verify or Update ISC Configuration Information
After accepting the license agreement, verify or update ISC information.

41
Installation Options Summary
After entering the ISC ID and password and enabling non-English language support if updating from a previous version, review the installation summary page and begin the installation.
42
2-35
InstallShield Installs the Administration Center

InStallShield Wizard
43
Successful Installation
http://<hostname>:8421/ibm/console
44
2-36
Lesson 6: Installing the Backup-Archive Client
Backup-Archive Client Installation
45
The Windows platform provides an InstallShield Wizard for the IBM Tivoli Storage Manager client. Note that you must do a Custom installation in order to have the administrative client installed. Be sure to read all readme documentation provided before you start installing any Tivoli Storage Manager code.
Unit 2: Installing IBM Tivoli Storage Manager Installing the Backup-Archive Client
Destination Folder
Destination Folder
46
The default user ID and password are client.
2-38
Custom Install
On AIX, the dsmadmc interface is installed automatically.
Custom Install Include Administrative Client Command Line
47
Language Packs
48
2-39
Web Client
Web Client
The Web client runs on port 1581 with the following browsers: Microsoft Internet Explorer 5.0 or higher with JRE 1.4.1 or higher. Mozilla 1.4 or higher, or Mozilla Firefox 1.0 with (JRE 1.4.1 or higher AIX and Linux clients). To run the Web client from Mozilla browsers, enable JavaScript must be selected. This setting is enabled by default, but to verify it: 1. Open Mozillas Edit menu and select Preferences. 2. In the Preferences window under Category, select Advanced and Scripts & Plug-ins. 3. Ensure there is a check mark next to Enable JavaScript for Navigator.
49
2-40
Unit 2: Installing IBM Tivoli Storage Manager Initial Configuration
Lesson 7: Initial Configuration

Initial Configuration Tasks
Initial Configuration Tasks
The Configuration Wizards will guide you through configuring your server.
50
2-41
Environmental Wizard Performance Options
Environmental Wizard Performance Options
51
2-42
Server Initialization Wizard

Server Initialization Wizard
52
The default directory for Windows is c:\program files\tivoli\tsm\server1.
2-43
Server Volume Information

Server Volume Information
53
Set the path and initial size of the following volumes: Database volume Recovery log volume Disk storage pool volume
2-44
Client Node Configuration and Prepare Media Wizards

Client Node Configuration Wizard
54
Prepare Media Wizard
55
2-45
Unit 2: Installing IBM Tivoli Storage Manager The Query Command
Lesson 8: The Query Command

Introducing the Query Command

How much What is the status of
Use the query command to obtain information about TSM components and operations.
56
Throughout this course you will be use the query command to gather information about the components and operations of Tivoli Storage Manager. For a complete list of query commands, refer to the IBM Tivoli Administrators Reference Guide for your platform.
Note: Query commands are not case-sensitive.
The Powerful Query System Command

The Query System command is a single command that gathers consolidated information regarding Tivoli Storage Manager configuration and capacity. Query System command combines the query and select commands to list information such as:
2-46
Server options and status Processes and sessions DB and log configuration
Storage pool configuration Device configuration Policies information Schedules and nodes
Standard Format Query Result

Standard Format Query Result

To query administrator: Q admin
To query database:
Q DB
57
These examples show the results of the query admin and query database commands when issued from the command line. The format of the output is called STANDARD. These commands will be covered later in the course. They are displayed here to demonstrate the different formats you can use with the query command.
2-47
Detailed Format Query Result

This example shows the results of the query DB format=detail command when issued from the command line. The format of the output is called detail. These query commands can be shortened as: q db f=d.
Detailed Format Query Result

For a detailed query, use the Format=Detail option (F=D). Q DB F=D
58
2-48
Query Activity Log

Query Activity Log
The activity log records all the messages sent to the server console during server operations, except query commands issued on the console. Any error messages sent to the server console are also stored in the activity log.
59
Examples of messages sent to the activity log include: When client sessions start or end When migration starts and ends When backup versions expire What data is exported to tape When expiration processing is performed What export or import processing is performed
Student Exercise
Student Exercise
60
Open your Student Exercises and perform the exercises for this unit.
2-50
Review Questions
1. The IBM Tivoli Storage Manager ___________________, which is part of the Integrated Solutions Console, allows the administrator to centrally configure and manage IBM Tivoli Storage Manager servers. 2. What is the best way to find out which platforms or devices are supported for the most current version of IBM Tivoli Storage Manager? a. Look at the Student's Training Guide. b. Check the IBM Tivoli Storage Manager Web site for the latest information. c. Assume that any device or platform will work. d. Check any Quick Start Guide. 3. True or False? Install and use JRE 1.4.1 or higher to optimize performance of the Java backup-archive client. 4. True or False? Installations can be verified on Windows systems by viewing the installserv.log file.
2-51
Review Answers
1. The IBM Tivoli Storage Manager ___________________, which is part of the Integrated Solutions Console, allows the administrator to centrally configure and manage IBM Tivoli Storage Manager servers. Administration Center 2. What is the best way to find out which platforms or devices are supported for the most current version of IBM Tivoli Storage Manager? a. Look at the Student's Training Guide. b. Check the IBM Tivoli Storage Manager Web site for the latest information. c. Assume that any device or platform will work. d. Check any Quick Start Guide. b. Check the IBM Tivoli Storage Manager Web site for the latest information. 3. True or False? Install and use JRE 1.4.1 or higher to optimize performance of the Java backup-archive client. true 4. True or False? Installations can be verified on Windows systems by viewing the installserv.log file. false
2-52
Summary
Summary
Describe the Integrated Solutions Console installation requirements. Install IBM Tivoli Storage Managers Administration Center. Install IBM Tivoli Storage Manager server. Install IBM Tivoli Storage Manager backup-archive clients. Install the administrative command line. Describe the IBM Tivoli Storage Manager device driver installation.
61
2-53
2-54
3-1
Introduction
This unit explores the IBM Tivoli Storage Managers Administration Center, as well as the other available user interfaces for managing IBM Tivoli Storage Manager. The levels of administrative authority required to administer IBM Tivoli Storage Manager are also presented.
Objectives
Objectives
Identify the types of interfaces available. Navigate the Administration Center on the Integrated Solutions Console. Identify the levels of authority for the different job roles. Create and remove a TSM administrator.
3-2
Unit 3: Administrative Interfaces and Privileges Interfaces for Tivoli Storage Manager
Lesson 1: Interfaces for Tivoli Storage Manager

Available Interfaces
Available Interfaces
Interface: Administration Center GUI Backup-Archive (BA) Client GUI How interface is accessed: ISC logon
dsm
(Windows)
dsmj (UNIX)
Web Client GUI BA Client Command Line TSM Server Command Line TSM Sever GUI Web browser and port 1581
dsmc dsmadmc, Administration

Center, and Server Console Windows MMC Console
Once an administrator accesses the Administration Center with an Administration Center user ID and password, all TSM servers controlled through the Administration Center can be managed. In this unit you will explore all the interfaces, including navigation of the Administration Center.
3-3
Unit 3: Administrative Interfaces and Privileges The Integrated Solutions Console and Administration Center
Lesson 2: The Integrated Solutions Console and Administration Center

Overview of the Integrated Solutions Console
Overview of the Integrated Solutions Console (ISC)

The Integrated Solutions Console allows you to install components provided by multiple IBM applications and access them from a single interface. This course addresses the IBM Tivoli Storage Managers Administration Center, which runs on the ISC.
The IBM Tivoli Storage Manager Administration Center is launched from the Integrated Solutions Console.
3-4
Tivoli Storage Managers Administration Center

IBM Tivoli Storage Manager Administration Center

The Administration Center: Allows access to the Tivoli Storage Manager server functions from any workstation, using a supported Web browser. Allows Web access to the command line.
Benefits of the Administration Center

Makes learning Tivoli Storage Manager easier for the new user. Implements a task-oriented user interface. The Administration Center uses wizards to simplify the following: Running reports Creating server maintenance scripts Scheduling Adding storage devices
The Administration Center provides a new server status Health Monitor which makes TSM server status easier to visualize. Only a single login is required once the Tivoli Storage Manager server connection has been added.
6
3-5
Logging on to the Integrated Solutions Console

Logging on to the Integrated Solutions Console

http://<hostname>:8421/ibm/console
A single login to remember.
The Integrated Solutions Console can be used to manage multiple software products.
3-6
How the Integrated Solutions Console Recognizes Your Tivoli Storage Manager Authority
Once ISC users log in to the console, they must add a Tivoli Storage Manager server connection, providing their Tivoli Storage Manager administrative ID and password. When a connection is established, the administrative privilege associated with the Tivoli Storage Manager ID is recognized by the ISC user ID. Now only one login is necessary.
How the ISC Recognizes Your TSM Authority
ISC user ID
Add a TSM server connection
TSM Administrative ID and Authority
ISC authority mapped to TSM user ID
All people who use the Integrated Solutions Console to work with Tivoli Storage Manager need to have their own ISC login ID and password, and their own TSM administrative ID and password.
If the authority of the Tivoli Storage Manager administrative ID is changed, the change is immediately effective in the ISC. There is no need to log out and log back in to the ISC.
3-7
Exploring the Task Trees

Exploring the Administration Center Tasks
Integrated Solutions Console settings
Tivoli Storage Manager tree for Administration Center tasks
The items in the left panel expand to show the tasks you can perform with the Administration Center.
3-8

Navigating the Administration Center: Welcome
10
Administration Center Tutorials

http://publib.boulder.ibm.com/infocenter/ieduasst/tivv1r0/index.jsp
11
3-9
Menus and Wizards
Selecting Actions
2 2 1 1
1. In the servers table, select server. 2. Open the Select Action menu.
12
Wizards
The wizard will guide you through the form to complete the Action and then summarize the actions.
13
3-10
Select Action Menus
Health Monitor
Health Monitor
Health Monitor actions Use the Health Monitor to determine the overall status of server operations and to obtain detailed information about client node schedules, the server database and recovery log, and the status of storage devices managed by the server. The health monitor also provides access to the server activity log, which allows you to view messages generated during server operations.
14
3-11
Enterprise Management
Enterprise Management
Enterprise Management actions The table shows all servers that you have added to the console. Use enterprise management to define servers to one another, which allows them to communicate and transfer data. Defined servers can be centrally managed using the commandrouting feature. A defined server can also be configured to store another server's data using virtual volumes. A server's enterprise configuration role determines whether it can distribute or receive configuration information.
15
3-12
Storage Devices, Servers

Storage Devices, Servers

Storage Devices servers actions Select a server and use the table action list to work with its storage pools, device classes, and data movers. The table shows all servers that have been added to the console.
16
3-13
Policy Domains and Client Nodes

Policy Domains and Client Nodes

Policy Domains and Client Nodes actions The table shows the servers you have added to the console, and the policy domains defined for those servers. Policy domains help you to apply consistent rules for data management to groups of client nodes. Click a server name to work with its policy domains.
17
3-14
Server Maintenance
Server Maintenance
Server Maintenance actions The table shows the servers you have added to the console, and identifies the servers for which maintenance scripts have been created. Maintenance scripts perform routine server maintenance operations according to a schedule you specify. As a best practice, create a maintenance script for every server.
18
3-15
Reporting
Reporting
Reporting actions The table shows the reports you can run against one or more servers. Use reports to view detailed information about your Tivoli Storage Manager environment.
19
3-16
Disaster Recovery Management


Disaster Recovery Management actions The table shows all of the servers that have been added to the Administration Center by the current administrator. For the servers that are licensed for IBM Tivoli Storage Manager Extended Edition, you can use the Disaster Recovery Manager function to automatically generate a disaster recovery plan and track media.
20
3-17
Starting and Stopping the Administration Center

Starting and Stopping the Administration Center

To start the server on Windows: your_isc_root PortalServer\bin\startISC.bat administrator password To stop the server on Windows: your_isc_root PortalServer\bin\stopISC.bat administrator password Where: your_isc_root is the root directory for your Integrated Solutions Console administrator is the administrator user ID for your Integrated Solutions Console password is the password for the administrator
The commands to start and stop the ISC are case sensitive, as are many of the search fields in the ISC. Read the Installation Guide for your platform for more details.
21
The installation program automatically starts the Integrated Solutions Console after a successful installation. If you shut down the system after the initial installation, any servers that were started will be stopped.
3-18
Administration Center Support Utility

Administration Center Support Utility

The Administration Center Support Utility is used to: 1. Turn all tracing on. 2. Turn all tracing off. 3. Turn a single trace class on. 4. Update the maximum memory size Administration Center can use. 5. Update the Administration Center session timeout setting. 6. Collect trace files, logs and system information to send to support. 7. View the log file for this utility.
22
3-19
Adjusting the Session Timeout

Adjusting the Session Timeout

The session timeout is the amount of idle time that the server will wait before forcing the Administrator to log in again. The default is 30 minutes. To change the session timeout: 1. Start the Administration Center Support Utility. 2. Go to the ISC directory under Tivoli\dsm\bin and type: SupportUtil.bat on Windows, or SupportUtil.sh on UNIX. 3. After starting the tool, press option 5 to update the session timeout setting.
These commands are case-sensitive.
23
Adjusting the Session Timeout on Windows

C:\Program Files\IBM\ISC601\Tivoli\dsm\bin>supportUtil.bat Administration Center Support Utility - Main Menu ================================================== 1. Turn all tracing on 2. Turn all tracing off 3. Turn a single trace class on 4. Update the maximum memory size Administration Center can use 5. Update the Administration Center session timeout setting 6. Collect trace files, logs and system information to send to support 7. View the log file for this utility 8. . 9. Exit Enter Selection: 5
24
3-20
Unit 3: Administrative Interfaces and Privileges Using the ISC to Manage Tivoli Storage Manager
Lesson 3: Using the ISC to Manage Tivoli Storage Manager

Creating a Tivoli Storage Manager Administrator
Creating a Tivoli Storage Manager Administrator
25
3-21
Creating a Tivoli Storage Manager Administrator, continued

Creating a Tivoli Storage Manager Administrator, continued
26
In the example here, the authority is Operator.
3-22
Granting the iscadmin Access to the Administration Center

Granting the iscadmin Access to the Administration Center

In the navigation tree, expand Console Settings. 1. Click User and Group Management. 2. In the table, click All Portal User Groups. 3. Click TSM_AdminCenter. 4. Click New user, select iscadmin, and click OK.
30
3-23
Adding a Tivoli Storage Manager Server to the Administration Center

Adding a Tivoli Storage Manager Server to the Administration Center
31
3-24
Using the Health Monitor

The Health Monitor: Detailed Health Information for Tivoli Storage Manager
You can view details including: Schedule Information Database and Recovery Log Information Activity Log Storage Device Status
32
Preparing to Configure
33
3-25
Configuring the Health Monitor

Configuring the Health Monitor
Change the password here. The initial password is ADMIN_CENTER.
34
View Health Details
Select the radio button next to a server, and from the Select Action menu choose View Health Details.
35
3-26
Database and Recovery Log

TSM Administration Centers Database and Recovery Log Tasks
36
Tivoli Storage Manager database

Tivoli Storage Manager saves information in the Tivoli Storage Manager database about each file, raw logical volume, or database that it backs up, archives, or migrates.
Tivoli Storage Manager recovery log

The recovery log, which is structured like the Tivoli Storage Manager database, keeps track of all changes made to the database.
3-27
Activity Log
Activity Log
37
Activity Log Information
Using the Filtering options provided, you can limit the amount of information presented in the table.
38
3-28
Unit 3: Administrative Interfaces and Privileges IBM Tivoli Storage Managers Graphical User Interface (GUI)
Lesson 4: IBM Tivoli Storage Managers Graphical User Interface (GUI)

Tivoli Storage Manager Windows Server GUI: Management Console
Tivoli Storage Manager Windows Server GUI: Management Console

Access the IBM Tivoli Storage Manager Console from the program folder:
All Programs >Tivoli Storage Manager > Management Console
39
The TSM Console is a Microsoft Management Console snap-in that provides: Wizards to assist with Tivoli Storage Manager administration and configuration tasks. A method to access the command line. A Windows-style tree view of the storage management resource network. Network scan utilities that can be used to locate Tivoli Storage Manager client nodes and server nodes for remote management. A notification feature that can be used to alert operators of Tivoli Storage Manager mount requests and status messages.
3-29
The GUI for Backup-Archive Clients

The GUI for Backup-Archive Clients

DSM
will start the GUI from the Windows command line, or access the Backup-Archive GUI from All Programs > Tivoli Storage Manager > Backup-Archive GUI. will start the GUI from the UNIX command line.
DSMJ
40
Use this interface to perform backup, restore, archive, and retrieve of client data.
3-30
Web Backup-Archive Client
Web Backup-Archive Client

Once the Web client is installed, you can use the Web client to perform backup, archive, restore, and retrieve operations from any browser that is running Java Runtime Environment (JRE) 1.4.1 or above. You will need a TSM administrative user ID with system privilege, policy privilege, client access authority, or client owner authority. To access the Web client, enter the following URL from any supported browser: http://your_machine_name:1581 where your_machine_name is the host name of the machine running the Web client.
Port 1581 is the default port number. You can set a different port number using the httpport option. The Web client GUI can be launched in the Administration Center without the administrator needing to sign on again. In order for this to be fully secured, SSL needs to be enabled for the Integrated Solutions Console server.
41
3-31
Unit 3: Administrative Interfaces and Privileges Command Lines
Lesson 5: Command Lines

The backup-archive command line is used to perform backup, restore, archive and retrieve functions. The administrative command line allows administrators to control and monitor the server through administrative commands.
Command Lines
BACKUP-ARCHIVE CLIENT COMMAND LINE: Start the backup-archive client command line at the operating system prompt. The paths may vary, but the default paths are as follows: Windows: Program Files > Tivoli > TSM > baclient AIX: /usr/tivoli/tsm/client/ba/bin Linux: /opt/tivoli/tsm/client/ba/bin To start the backup-archive client command line, type: dsmc On Windows, the backup-archive command line can be opened from All Programs > Tivoli Storage Manager > Backup-Archive Command Line. ADMINISTRATIVE COMMAND LINE: Start the administrative command line at the operating system prompt. The paths may vary, but the default paths are as follows: Windows: Program Files > Tivoli > TSM > baclient AIX: /usr/tivoli/tsm/client/ba/bin Linux: /opt/tivoli/tsm/client/ba/bin To start the administrative command line, type: dsmadmc From the Administration Center, select Server, click Select Action, select Use Command Line.
42
Use the console mode from an administrative client to monitor export or import operations or to capture processing messages to an output file. For example, you can keep a console open to watch processes for successful completion. Manual tape mount requests can also be viewed on the console. To start an administrative session in console mode, enter:
dsmadmc -consolemode
Command recall is available for both the administrative client and the backup-archive client. This enables you to recall and edit previously entered commands.
3-32
Some keyboard keys used
Key F3 or ESC Ctrl C Backspace Left arrow Right arrow Up arrow Down arrow Tab Left Tab Ctrl Left arrow or Ctrl L Ctrl Right arrow or Ctrl R Home End Ctrl D or Ctrl Delete Enter
Description Exits the command line. Cancels the command line. Moves the cursor one space back and deletes text. Moves the cursor one space to the left. Moves the cursor one space to the right. Displays the command last entered. Displays the command entered after the command currently displayed. Moves the cursor five positions to the right. Moves the cursor five positions to the left. Moves the cursor to the beginning of the previous word. Moves the cursor to the beginning of the next word. Moves the cursor to the beginning of the line. Moves the cursor to the end of the line. Deletes the text from the cursor to the end of the line. Executes the command.
3-33
Using Syntax Diagrams

How to Read Syntax Diagrams
This excerpt is from the IBM Tivoli Storage Manager for Windows Administrators Reference.
43
Update Storagepool Syntax Diagram
44
3-34
Example of Parameters
Example of Parameters
45
3-35
Accessing the Administrative Command Line from the Administration Center

Accessing the Administrative Command Line from the Administration Center
You can access the command line from any Select Action window.
46
3-36
Output of a Command-line Query

Output of a Command-line Query
47
Rearranging the Data in Output

table
list
table list
48
3-37
Command Assistance
49
Syntax of many of the common query commands are available.
3-38
Unit 3: Administrative Interfaces and Privileges Administrative Authority
Lesson 6: Administrative Authority

TSM Administrator Management Capabilities

System Privileges Storage Privileges Operator Privileges
All Tivoli Storage Manager server tasks. Database, recovery log, and storage pool management. Commands for server availability, resource usage, and physical media management. Policy domain, policy set, management class, copy group, and schedule management. Review and reset server statistics. Client actions, product usage and activity monitoring.
50
Policy Privileges
Analyst Privileges Node Privileges
IBM Tivoli Storage Manager enables customers to register administrators and to grant administrators the ability to accomplish specific tasks. After administrators are registered, they can make queries and request help from the command line. To perform other server functions, they must be granted authority by being assigned one or more administrative privilege classes.
3-39
Privilege Classes
TSM Privilege Classes
51
An administrator with system privilege can distribute administrative tasks by: Registering administrators. Granting one or more administrative privilege classes to other administrators. Allowing separation of tasks. Allowing delegation of authority. Varying commands by privilege class.
This slide shows how you can divide the administrative tasks through the five privilege classes.
3-40
Registering an Administrator
Registering an Administrator
Syntax:
REGister Admin userid password FORCEPwreset=No|Yes Contact=contactinfo

Example:
TSM administrator
REGister Admin BGoode rs1paswd Passexp=120 contact=B. Goode, x1234

Using the Administration Center: 1. Click Enterprise Management in the Tivoli Storage Manager tree. 2. In the Servers table, select a server. 3. Click Select Action, select Server Properties. 4. In the servers properties notebook, click the Administrators tab. 5. In the table, click Select Action, select Add Administrator.
52
TSM server
To register an administrator, use the following command:
3-41
Managing Administrative Authority

Managing Administrative Authority

Administrative authority can be assigned and managed according to each individuals job requirements. The privilege class determines which administrative tasks the administrator can perform.
GRANT AUTHORITY REVOKE AUTHORITY
You must have one of the following privileges to grant or revoke client access or client owner authority: System privilege Policy privilege in the clients domain
53
Granting Authority to Administrators

You can grant authority with the grant authority command. For example, to grant administrator Mack restricted policy privilege for the domain SALESPOLDOM, enter the following command:
grant authority mack domains=salespoldom
Extending Authority for Administrators

You can grant and extend authority with the grant authority command. If an ID already has some level of authority, granting additional authority adds to any existing privilege classes; it does not override those classes. For example, Jenny was just promoted from operator to storage administrator for the labs. To add unrestricted storage privilege and restricted policy privilege for both LAB domains for Jenny, enter the following command:
grant authority jenny class=storage domains=LAB1, LAB2

3-42
Reducing Authority for Administrators

You can revoke part of the authority of an administrator with the revoke authority command. For example, rather than revoking all of the privilege classes for administrator Suki, you want to revoke only the operator authority and the policy authority to policy domain SERVPOLDOM. You enter the following command:
revoke authority Suki classes=operator domains=servpoldom
Reducing Privilege Classes

You can reduce the authority of an administrator simply by revoking one or more privilege classes and granting one or more other classes. For example, administrator Lotte has system authority. To reduce authority for Lotte to the operator privilege class, do the following: 1. Revoke the system privilege class by entering:
revoke authority lotte classes=system
2. Grant operator privilege class by entering:

grant authority lotte classes=operator
Revoking Authority for Administrators

You can revoke the authority of an administrator with the revoke authority command. To revoke all administrative privilege classes, do not specify any privilege classes, policy domains, or storage pools. For example, to revoke both the storage and operator privilege classes from administrator Lucy enter:
revoke authority lucy
3-43
Removing an Administrator
Removing an Administrator
Syntax:
REMove Admin userid

Example:
remove admin bob
TSM administrator
You cannot remove the last administrator with system privilege from the system. You also cannot remove the SERVER_CONSOLE user ID (which has system privilege) from the system.
TSM server
54
You can also remove an administrator who will no longer be responsible for IBM Tivoli Storage Manager operations by using the remove admin command.
3-44
Unit 3: Administrative Interfaces and Privileges Export/Import
Lesson 7: Export/Import
You can export or import administrator, node, server, or policy information. You can export the complete server or just parts of it. For example, clients of just one department and their stored data can be exported. The export commands are operating system independent, and create a copy of specified server information or client data. This copy is not a substitute for disaster recovery. Export and import are relatively time-consuming processes. So it is designed primarily for one-time data movement. Data can be exported to sequential media or to another IBM Tivoli Storage Manager server on the network.
Export/Import of Administrator
Export/Import of Administrator
Use the export admin command to export administrator definitions, such as name, password, contact information, administrative privilege classes, and whether the client node ID is locked.
Export admin * toserver=servergray previewimport=yes
55
The export admin command moves administrator information such as name, password, privilege classes, and whether the administrator is locked from server access.

3-45
Student Exercise
Student Exercise
56
3-46
Review Questions
1. In the Administration Center, you can use the __________________ to determine the overall status of server operations. 2. True or False? The only way to access the Tivoli Storage Manager command line is from the console of the operating system. 3. True or False? The IBM Tivoli Storage Manager Console is a Microsoft Management Console snap-in that provides a backup-archive utility for client data. 4. If you have _________________ authority you can perform all IBM Tivoli Storage Manager tasks. 5. What command starts an administrative command line? a. adsm b. dsmc c. admc d. dsmadmc
3-47
Review Answers
1. In the Administration Center, you can use the __________________ to determine the overall status of server operations. Health Monitor 2. True or False? The only way to access the Tivoli Storage Manager command line is from the console of the operating system. false 3. True or False? The IBM Tivoli Storage Manager Console is a Microsoft Management Console snap-in that provides a backup-archive utility for client data. false 4. If you have _________________ authority you can perform all IBM Tivoli Storage Manager tasks. system 5. What command starts an administrative command line? a. adsm b. dsmc c. admc d. dsmadmc d. dsmadmc
3-48
Summary
Summary
Identify the types of interfaces available. Navigate the Administration Center on the Integrated Solutions Console. Identify the levels of authority for the different job roles. Create and remove an TSM administrator.
57
3-49
3-50
4-1
Introduction
This unit introduces devices used to store data. Basic concepts of attaching a tape library and preparing media to work with IBM Tivoli Storage Manager are also discussed.
Objectives
Objectives
Identify the device types. Explain how to configure a locally attached tape library to IBM Tivoli Storage Manager. Explain how to prepare tape cartridges for use in an IBM Tivoli Storage Manager managed tape library. Explain how to check media in and out of the library.
4-2
Unit 4: Storage Media Devices Introduction Installing and Configuring a Tape Library Attached to the IBM Tivoli Storage Manager Server
Lesson 1: Installing and Configuring a Tape Library Attached to the IBM Tivoli Storage Manager Server
Installing and Configuring a Tape Library
Installing and Configuring a Media Library

Library A device that organizes and holds one or more media (tape or disk) volumes, and an optional robotic mechanism. Use define library command. Device Class Represents a device type which defines the media used in the library. A virtual library. Use the define devclass command. Drive A hardware device capable of performing operations on a specific type of sequential media. Use the define drive command. Slot The storage media location in the library. Use the define path command.
3
The combination of the library, drives, and their device class represents the physical device environment. A physical library is a collection of one or more drives that share similar media mounting requirements. Each drive mechanism within a device (that uses removable media) is represented by a drive object. For devices with multiple drives, including automated libraries, each drive is separately defined and must be associated with a library. A drive is a hardware device capable of performing operations on a specific type of sequential media. Drive definitions can include such information as the element address (for drives in SCSI libraries), how often the drive is cleaned (for tape drives), and whether or not the drive is online.
4-3
Connecting a SCSI Library

Connecting a SCSI Library
Perform the following steps to attach an automated library device: 1. Install the SCSI adapter card in your system, if not already installed. 2. Determine the SCSI IDs available on the adapter card to which you are attaching the device. Find one unused SCSI ID for each drive, and one for the library or autochanger controller. In some automated libraries, the drives and the autochanger share a single SCSI ID but have different logical unit numbers (LUNs). For these libraries, only a single SCSI ID is required. Check the documentation for your device. 3. Follow the instructions from the manufacturer to set the SCSI ID for the drives and library controller to the unused SCSI IDs that you found. Usually you need to set switches on the back of the device. Note: Each device connected in a chain to a single SCSI bus must be set to a unique SCSI ID. If each device does not have a unique SCSI ID, you may have serious system problems. 4. Follow the instructions from the manufacturer to attach the device to your server system hardware. Note: Power off your system before attaching a device to prevent damage to the hardware. Also, you must attach a terminator to the last device in the chain of
4-4
devices connected on one SCSI adapter card. Detailed instructions should be in the documentation that came with your hardware.
Supported Device Types
Supported Device Types

The list of supported device types is available online at:
Go to the IBM Web site, and then navigate to:
www.ibm.com/software/sysmgmt/products/support/IBMTivoliStorageManager.html
Select one of the following under Supported Devices:

AIX, HP, SUN, and Windows iSeries Linux
Note: If your device is not listed on the supported list of devices, it is very likely that it is not supported.
4-5
Getting Device Information from the Tivoli Storage Manager Device Driver
Use the wizards associated with the TSM Management Console to initiate the Device Configuration wizard and view existing device configuration information. IBM devices require IBM device drivers. Non-IBM devices require TSM device drivers.
Getting Device Information from the Tivoli Storage Manager Wizard
All connected libraries will be listed in the wizard.
4-6
Use tsmdlst to Find Devices

Use tsmdlst to Find Devices on Windows

1. Click Start > Programs > Accessories > Command Prompt. The command prompt dialog box appears.
2. Change directories to the directory in which the Tivoli Storage Manager Console been installed. For default installations, the path is:
c:\program files\tivoli\tsm\console
3. To view the information, enter the following command: tsmdlst > devlist.txt
4. To view the file, enter the following command: notepad devlist.txt

7
To view a listing of devices and their attributes, you can use the tsmdlst command.
Finding Devices on AIX
# lsdev -Cc disk hdisk0 Available 40-60-00-4,0 16 Bit SCSI Disk Drive # lsdev -Cc tape rmt0 Available 1P-08-00-0,0 4.0 GB 4mm Tape Drive rmt1 Available 1P-08-00-2,0 4.0 GB 4mm Tape Drive smc0 Available 1P-08-00-3,0 IBM 7336 Tape Medium Changer # lsdev -Cc adsmtape mt0 Available 1P-08-00-0,0 Tivoli Storage Manager Tape Drive mt1 Available 1P-08-00-2,0 Tivoli Storage Manager Tape Drive
4-7
Determining Numbers for Libraries with Multiple Drives

The element number indicates the physical location of a drive within an automated library. IBM Tivoli Storage Manager needs the element number to connect the physical location of the drive to the drive's SCSI address. When you define a drive, the element numbers are only required for SCSI type libraries. The element number can be detected automatically depending on the capabilities of the library. ELEMent=AUTODetect in the DEFINE/UPDATE DRIVE command is supported.for many libraries. This is dependent on the hardware. Refer to the information on your tape library on the IBM Web site for more details.
Determining Numbers for Libraries with Multiple Drives
Worksheet from IBM Web site
To get information on determining element numbers, go to the following Web page: http://www.ibm.com/software/sysmgmt/products/support/ IBM_TSM_Supported_Devices_for_AIXHPSUNWIN.html Find the device worksheet that applies to your device, and determine the alias name for the device. The device name for each drive has the form mtx. The device name for the library controller has the form lbx. In both cases, x is the number assigned when the drive and library were set up with its device driver.
4-8
Alias names appear in the form mtx.y.z.n or lbx.y.z.n or opx.y.z.n, where: mt: Indicates the device is a tape device. For example: mt3 (Tape drive at SCSI ID 3, LUN 0, bus 0, port 0) mt5.0.0.1 (Tape drive at SCSI ID 5, LUN 0, bus 0, port 1). lb: Indicates the device is the controller for an automated library device. For example: lb4.1 (Library at SCSI ID 4, LUN 1, bus 0, port 0.). op: Indicates the device is an optical device. For example: op4 (Optical drive at SCSI ID 4, LUN 0, bus 0, port 0). x: Indicates the SCSI ID for the targeted device. y: Indicates the logical unit number (LUN) for the targeted device. z: Indicates the bus number supported by the adapter device driver. n: Indicates the port number for the SCSI adapter device driver.
Enter the device special file name in the worksheet. Keep the Worksheets. The information you record on the worksheets can help you when you need to perform operations such as adding volumes to an autochanger. Keep them for future reference.
4-9
Configuring Devices
After the device is installed and recognized by the operating system, you will need to configure the device.
Commands to Configure SCSI Devices

Define a library: define library robotmount libtype=scsi Define a tape path for the library: define path server1 robotmount srctype=server desttype=library device=lb3.0.0.0 Define a drive: define drive robotmount tap01 elem=autodetect Define a path for the drive: define path server1 tap01 srctype=server desttype=drive library=robotmount device=mt3.0.0.0
10
Use the audit library command and check the activity log to ensure you were successful. Perform the steps, in the order shown on the slide, for each drive.
4-10
Unit 4: Storage Media Devices Introduction Working with Media
Lesson 2: Working with Media

The Difference between Scratch and Private Volumes
Tivoli Storage Manager classifies its volumes into two categories: private and scratch.
The Difference between Scratch and Private Volumes
SCRATCH VOLUMES:
Are empty or contain no valid data. Change status to PRIVATE when data is written to them. Can be used to satisfy any request to mount a scratch volume.
PRIVATE VOLUMES:
May contain valid data. Are used or owned by an application. Can only be used to satisfy a request to mount the specified volume.
11
A private volume is a labeled volume that is in use or owned by an application and may contain valid data. You must define each private volume, and it can only be used to satisfy a request to mount that volume by name. Private volumes do not return to scratch when they become empty. A scratch volume is a labeled volume that is empty or contains no valid data and can be used to satisfy any request to mount a scratch volume. When data is written to a scratch volume, its status is changed to private. You can change the status of volumes by issuing the update libvolume command. The command allows you to assign a private status to a scratch volume or to assign a scratch status to a private volume. The private volumes must be administrator-defined volumes

4-11
with either no data or invalid data. They cannot be partially written volumes containing active data. Volume statistics are lost when volume statuses are modified.
The Life Cycle of Tape Cartridges

Tapes must first be labeled and then added to the inventory of tapes available to IBM Tivoli Storage Manager. Tapes may be checked into IBM Tivoli Storage Manager as either scratch or private. Tapes that are part of the scratch pool are eligible to be selected for use. Once a tape is selected, data remains on the tape until it has expired or moved. The tape can then be reclaimed and returned to the scratch pool.
The Life Cycle of Tape Cartridges
Start reuse if defined to storage pool.

12
There are several methods for checking in a tape. They can be checked in online or offline. You can label and check in all in one step (label libvol), or use the autolabel=yes feature when defining a 349X, ACSLS, SCSI, external, or manual library.
4-12
Labeling Tapes
Labeling Tapes
The label libvolume command: label libvolume storagelibname checkin=scratch search=bulk labelsource=barcode or The AUTOLABEL parameter with the define library command: define library autodltlib libtype=scsi autolabel=yes
13
Label Libvolume
If you label volumes with the label libvolume command, you can issue the CHECKIN parameter. You can label volumes with the label libvolume command. The following example demonstrates using the label libvolume command to label tapes for both manual and automated libraries. Assume the automated device is attached to SCSI address 4, and the manual device is attached to SCSI address 5. You want to insert media into the entry and exit ports of the device, and you want the bar code reader to read bar code labels and overwrite existing labels with the information on the bar code label.
To search the entry and exit port, enter:

Search=bulk
To search inside the library, enter:

Search=yes

4-13
AUTOLABEL
The AUTOLABEL parameter: Can be used with the define library and update library commands. Can be more efficient than using the label libvolume command, which requires you to mount volumes separately. Can be used with all library types except shared. Will use the barcode values for 349X, ACSLS, and SCSI libraries, and whatever volume name given by the external application for external libraries. Will prompt you for a label with manual libraries.
The AUTOLABEL parameter allows you to checkin volumes without a label. The server will label both blank and incorrectly labeled tapes when they are initially mounted, using the barcode as the volume name. Using the AUTOLABEL parameter eliminates the need to prelabel a set of tapes. AUTOLABEL is specified as a parameter on the library with possible values of NO (default), YES, or OVERWRITE. If you use the AUTOLABEL parameter, you must check in tapes by specifying CHECKLABEL=BARCODE on the checkin libvolume command.
4-14
Checking Out Volumes

You can remove volumes from automated libraries by issuing the checkout libvolume command.
Checking Out Volumes

TSM mounts each volume and verifies the internal label before checking it out. After being checked out, the volume is moved to the entry or exit port if the device has one. If it does not, the operator is requested to remove the volume from the drive within the device. checkout libvolume checkout libvolume tapelib volx checklabel=yes remove=bulk
You can also check out volumes for a library from the Administration Center:
1. Click Storage Devices in the Tivoli Storage Manager tree. 2. In the Libraries for all Servers table, click a library name. 3. In the properties notebook for the library, click the Volumes tab. 4. In the Volumes table, click Select Action, select Check Out Volumes.
14
For automated libraries with multiple entry and exit ports, you can issue the checkout libvolume command with the REMOVE=BULK parameter. Tivoli Storage Manager ejects the volume to the next available entry and exit port.
4-15
Checking In Volumes
After the volumes have been labeled, make the volumes available to Tivoli Storage Manager devices by checking the volumes into the library volume inventory using the checkin libvolume command. Checking media into an automated library involves adding them to the library volume inventory.
Checking In Volumes
checkin libvolume tapelib volx search=no status=scratch checkin libvolume tapelib search=yes status=scratch checklabel=barcode query libvolume
You can check in and label volumes for a library from the Administration Center:
1. Click Storage Devices in the Tivoli Storage Manager tree. 2. In the Libraries for all Servers table, click a library name. 3. In the librarys properties notebook, click the Volumes tab. 4. In the Volumes table, click Select Action, select Add Volumes.
15
4-16
Auditing a Library
You can issue the audit library command to audit the volume inventories of automated libraries.
Auditing a Library
vol_002
vol_002
slot 1
2
vol_007
slot 1
slot 2
vol_007
slot 2
slot 3
vol_008
slot 3
vol_008
In figure 2, vol_007 and vol_008 are manually removed and replaced.
3
The AUDIT LIBRARY command will update the library inventory.
?
slot 1
?
slot 2
audit library tapelib checklabel=barcode
slot 3
16
Auditing the volume inventory ensures that the information maintained by the Tivoli Storage Manager server is consistent with the physical media in the library. The audit is useful when the inventory has been physically moved. Tivoli Storage Manager deletes missing volumes and updates the locations of volumes that have moved since the last audit. Tivoli Storage Manager cannot add new volumes during an audit. It is suggested that you not move tapes within the library.
Review Questions
1. Tivoli Storage Manager has two status types for a tape volume. A ___________ volume is a labeled volume that is in use or owned by Tivoli Storage Manager, and may contain valid data. 2. A ___________ volume is empty or contains no valid data, and can be used to satisfy any request to mount a scratch volume. 3. The __________ command is useful when the inventory has been physically moved. 4. The _____________ is a number that indicates the physical location of a drive within an automated library.
4-18
4-19
Review Answers
1. Tivoli Storage Manager has two status types for a tape volume. A ___________ volume is a labeled volume that is in use or owned by Tivoli Storage Manager, and may contain valid data. private 2. A ___________ volume is empty or contains no valid data, and can be used to satisfy any request to mount a scratch volume. scratch 3. The __________ command is useful when the inventory has been physically moved. audit library 4. The _____________ is a number that indicates the physical location of a drive within an automated library. element number
4-20
Summary
Summary
Identify the device types. Explain how to configure a locally attached tape library to IBM Tivoli Storage Manager.
Explain how to prepare tape cartridges for use in an IBM Tivoli Storage Manager managed tape library.
Explain how to check media in and out of tape library.
17
4-21
4-22
5-1
Introduction
In this unit, you will see how to create hierarchical storage pools of different media types to allow for efficient management of your data.
Objectives
Objectives
Describe the purpose of storage pools, storage pool hierarchies, and storage pool volumes. Create a storage pool. Design and configure storage pools based on given customer requirements. Manage storage pool volumes.
5-2
Unit 5: Managing Storage Pools and Storage Pool Volumes Storage Pools, Hierarchies, and Storage Pool Volumes
Lesson 1: Storage Pools, Hierarchies, and Storage Pool Volumes

Storage Pools
Data storage pools are where the server stores files that are backed up and archived. The database serves as the inventory or index to client files within data storage.
Storage Pools
Client sends data to server. Server records data storage information in TSM database.
Server writes data to disk pool.
Data is moved from disk pool to next defined storage pool.
Storage pools: Are a collection of like media (same device class) Provide storage for backed up, archived, or migrated files Support a variety of devices Can be chained together to create storage hierarchy
3
Data storage may be composed of direct access storage and sequential tape media. Files may be initially placed on different storage pools according to the desired storage management policy. Files are automatically moved to other devices to satisfy free space, space utilization, performance, and recovery requirements. An administrator with system, storage, or operator privilege can manage data storage. This includes planning, preparing, monitoring, and deleting storage volumes and storage pools depending on level of privilege class. Data storage is actually defined as a collection of storage pools.

5-3
Storage Pool Hierarchies

Storage Pool Hierarchies

more expensive faster
less expensive
slower
Storage pools can be chained to create a storage hierarchy.

4
A storage pool is a named set of volumes, belonging to the same device class, which is the destination of backed up or archived data. A device class is a grouping of like devices, such as disk or tape. The purpose of storage pools is to match user requirements for data with the physical characteristics of storage devices. For example, if users need immediate access to certain data, you can define a storage pool, which consists of storage volumes residing on highperformance DASD (direct access storage device an IBM term for a hard disk). Then, users can associate this storage pool as a destination for their files by binding the appropriate management class. Storage pools can be chained to create a storage hierarchy.
5-4
Active-Data Pools and the Storage Hierarchy
Active-Data Pools and the Storage Hierarchy

Copy storage pool: Copies of active or inactive data from primary storage pools for offsite storage. Active-data pools on disk: Copies of active data for fast restore of client data. Active-data pools on tape: Copies of active data to reduce the number of tapes stored offsite.
storage hierarchy with active and inactive data
Active-data pools: Can be used with sequential-access disk (FILE) Can be used with sequential-access tape or optical Can collocate active versions of backup data Can be used for backup data only; no archive or HSM data
Active-data pools are covered in greater detail in Unit 10.
5-5
Device Classes
Device Classes
Random Access:
Sequential Access:
Define additional tape device classes to reflect specific devices, media, and procedures. DEFine DEVClass DEVType=type of device
def devc autodlt_class devt=dlt format=drive library=autodltlib00
6
A device class represents a set of storage devices with similar availability, performance, and storage characteristics. These device types are managed by Tivoli Storage Manager. Tivoli Storage Manager uses the device class to determine which device and storage volume type to use to: Store backup, archive, or space-managed data (primary storage pools). Store copies of primary storage pool data (copy storage pools). Store database backups. Export or import Tivoli Storage Manager data.
One device class can be associated with multiple storage pools. Each storage pool is associated with only one device class. Each device class is characterized by its device type, which indicates the type of storage volumes that are used to store data. For random access storage, Tivoli Storage Manager supports only the DISK device class. The DISK device class is predefined by Tivoli Storage Manager. However, you can define many storage pools associated with the DISK device class. You cannot modify the DISK device class. For sequential access storage, Tivoli Storage Manager supports the following device types, including the FILE device class; drive space designated for use as a virtual storage device.
5-6
Device Type 3570 3583 3590 3592 4 MM 8 MM DLT DTF FILE GENERICTAPE OPTICAL QIC
Description IBM 3570 cartridge tape devices IBM 3583 tape drives IBM 3590 tape drives IBM 3592 tape drives 4 mm tape drives, such as IBM 7206-005 8 mm tape drives, such as IBM 7208-001 and 7208011 Digital linear tape (DLT) drives Digital tape format Standard files are used to represent individual media volumes. Data is written to file volumes sequentially, as if they were tape volumes. Tape drives supported by a Windows tape device driver Optical drives that use 5.25-inch rewritable optical cartridges Quarter-inch cartridge tape drives, such as the IBM 7207 Removable media devices that are attached as local, removable file systems (for example, Iomega Zip or Jaz drives, or CD media) Storage volumes that are actually files archived in the server storage of another Tivoli Storage Manager server (a target server) Optical drives that use 5.25-inch write-once read-many optical cartridges A device type for StorageTek drives in a LAN-free configuration (except VOLSAFE which has its own devtype) Linear Tape-Open (LTO) devices Network-attached storage devices Also StorageTek tape media referred to as WORM (Write Once Read Many) tape technology
REMOVABLEFILE
SERVER
WORM
Ecartridge LTO NAS VOLSAFE
5-7
Based on the tape environment, an administrator with system privilege can define as many different device classes for tape storage pools as needed. Each tape device class is uniquely identified by its name. Not all device classes are available on all platforms. Tape device classes allow the installation to control the following: Whether you will be using cartridge or reel tape (DEVtype). The maximum tapes that can be simultaneously mounted (MOUNTLimit). The maximum minutes before idle tape is demounted (MOUNTRetention). The tape volume naming convention (PREFIX). The estimated volume capacity (ESTCAPacity), since the default does not consider the use of compression by the client or tape hardware.
5-8
Device Class and Storage Pool

Device Class and Storage Pool

Storage pools are mapped to a specific device class. TSM handles data in a storage pool according to the device characteristics.
device class with device type of tape
device class with device type of disk
DEFine DEVClass DEVType=type of device

7
Each device is associated with a device class that specifies the device type and how the device manages the media. If you have two libraries you will need two device classes. Storage pools are mapped to a device class. Through this mapping, when data is written to, or accessed from a storage pool, Tivoli Storage Manager knows the device characteristics of the storage pool media and how to access it. If the device is not listed on the IBM support page, it is probably not supported.
5-9
Storage Destination
Storage Destination
stgpool_A
disk tape sales

stgpool_B
disk file tape accounting
stgpool_D
sales
stgpool_C
accounting
8
A storage destination identifies the storage pool where client data is sent when it is backed up, archived, or migrated. It is specified in the backup and archive copy group definitions that are included in the management class, which is part of policy management. Policy management is covered in Unit 6. Data placement is also influenced by storage pool settings that may restrict read/write access and limit the size of files placed in the storage pool.
5-10
Disk-Only or Tapeless Backup Overview

Disk-Only or Tapeless Backup Overview

There are two types of disk pools: Random access
Tivoli Storage Manager provides a predefined disk device class that is used with all disk devices.
Sequential access
To create large, sequential access file-type storage pools, issue the following command:
define devclass devclassname devtype=file

Since each volume in a file device class is a file, the volume name must be a fully-qualified file name.
9
The storage volumes are actually files. Data is written sequentially into standard files in the file system of the server machine. You can define this device class by issuing a define devclass command with the DEVTYPE=FILE parameter. Both disk storage pool formats also have the capability of providing a space trigger for automatic allocation of storage pool space, which can result in increased efficiency of disk storage pools. This will reduce the potential for disk fragmentation and maintenance downtime. Do not use raw partitions with a device class type of FILE.
5-11
Defining Storage Pools

The following tasks are associated with managing storage pools and their volumes.
Creating or Defining Storage Pools

Use the following command to define a storage pool:
DEFine STGpool poolname devclass
For example: DEFine STGpool lastinchain devclass=tape
Create a storage pool from the Administration Center:

1. Click Storage Devices in the Tivoli Storage Manager tree. 2. In the Servers table, select a server. 3. Click Select Action, select View Storage Pools. 4. In the storage pools portlet for the server, click Select Action, select Create a Storage Pool.
10
During installation, Tivoli Storage Manager provides predefined random access storage pools: BACKUPPOOL: A storage destination for user files that are backed up to the server. ARCHIVEPOOL: A storage destination for user files that are archived to the server. SPACEMGPOOL: A storage destination for files migrated from user nodes. DISKPOOL: Only for Windows systems. FILPOOL1: A default storage pool of device class FILEDEV1 created as a default Next Storage Pool for both ARCHIVEPOOL and BACKUPOOL when you install a minimum configuration on Windows only.
Example:
define stgpool pool1 disk description="test1 storage pool" maxsize=5m highmig=70 lowmig=30 cache=yes nextstgpool=test2
5-12
Update and Query Storage Pools

Update and Query Storage Pools

Use the following command to update storage pools:
UPDate STGpool poolname

Use the following command to update storage pools:
Query STGpool poolname
Use the following command to show which storage pools contain client file spaces for a node and how much space they occupy:
Query OCCupancy nodename

You can also use the Administration Center to view and modify storage pools.
11
Use the update stgpool command to change any parameter in an existing primary, copy, or active-data storage pool. If you do not explicitly update a parameter, it remains unchanged. The parameters to update are the same as the parameters when you define a storage pool. Use the query stgpool command to display information about one or more storage pools. The query occupancy command displays: Node name Type (backup, archive, or space managed) Filespace name and number Storage pool names Number of files Physical and logical space occupied
For the syntax of the commands, refer to the IBM Tivoli Storage Manager Administrator's Guide or issue the help update stg or help query command as an administrator.

5-13
Creating or Defining Storage Pool Volumes
Creating or Defining Storage Pool Volumes

Command to define storage pool volumes:
DEFine VOLume poolname volname
Create volumes in a storage pool from the Administration Center: 1. Click Storage Devices in the Tivoli Storage Manager tree. 2. In the Servers table, select a server. 3. Click Select Action, select View Storage Pools. 4. In the storage pools portlet for the server, click a storage pool name. 5. In the properties notebook for the storage pool, click the Volumes tab. 6. In the volumes table, click Select Action, select Add Volume.
12
Use the define volume command to assign a random or sequential access volume to be used for storage within an existing storage pool. You can define a volume to either a primary storage pool or a copy storage pool. You must define each volume to be used in a storage pool unless you allow scratch volumes for the storage pool. Before issuing this command for a random access volume, you must allocate and format the volume by using Tivoli Storage Manager command define volume with the FORMATSIZE parameter. For sequential access storage pools with a device type other than FILE or SERVER, you must prepare volumes for use. When the server accesses a sequential access volume, it checks the volume name in the header to ensure that the correct volume is being accessed.
5-14
To prepare a volume: 1. Label the volume. 2. For storage pools in automated libraries, use the checkin libvolume command to check the volume into the library. 3. Use the define volume command unless you allowed scratch volumes in the storage pool by specifying a nonzero MAXSCRATCH parameter.
>>--DEFine Volume--poolname--volume-----------------------> +-ACCess--=--READWrite-------+ >--+----------------------------+-------------------------+-ACCess--=---+-READWrite----+ (2) +-READOnly-----+ +-UNAVailable--+ | (1) |
-OFfsite----- >--+------------------------------------------------+---> | (2) .-Wait--=--No----- . |
-Formatsize---=--megabytes--+-------------------+ .-Wait--=--No----- . >--+------------------------------------------------+---> | (3) -LOcation------=--location- (1) This value is valid only for volumes assigned to copy storage pools. (2) This parameter is valid only for random access volumes. (3) This parameter is valid only for sequential access volumes.
5-15
Defining Storage Pool Volumes for Disk

Defining Storage Pool Volumes for Disk

Commands to define storage pool volumes: DEFine VOLume poolname volname Formatsize=Format_size DEFine VOL BACKUPPOOL /usr/tivoli/tsm/dbvol/vol6 Formatsize=200 DEFine VOL ARCHIVEPOOL E:\dbvol\vol5 F=200
13
5-16
Deleting Storage Pools and Volumes

Deleting Storage Pools and Volumes

Before deleting a storage pool, you must delete all volumes in that storage pool.
Delete storage pools and storage volumes with the following commands:
DELete VOLume volumename Query CONtent DELete STGpool poolname
14
Before you begin deleting all volumes that belong to the storage pool, change the access mode of the storage pool to unavailable so that no files can be written to or read from volumes in the storage pool. To delete an empty storage pool volume, use the delete volume command:
DELete VOLume volumename
Tivoli Storage Manager does not allow you to delete a volume that contains data unless you specify DISCARDDATA=YES on the delete volume command.
DELete VOLume volumename DISCARDData=YES
The delete volume command can be used to delete a volume assigned to either a primary or copy storage pool. If during the processing of this command for a primary storage pool volume, Tivoli Storage Manager deletes the primary copy of a file (not a cached copy), then Tivoli Storage Manager also deletes any copies of that file residing in copy storage pools. If you are deleting several volumes, it is suggested that you delete the volumes one at a time. Concurrent volume deletion can adversely affect server performance. If archive retention protection is enabled, the data cannot be deleted until the retention period has been met.

5-17
The query content command is used to determine the contents stored on a volume by querying a Tivoli Storage Manager database table. Use the delete stgpool command to delete a storage pool. In order to use this command, you must first delete all volumes assigned to the specified storage pool. You cannot delete a storage pool that is defined as a subordinate storage pool. For more information on subordinate storage pools, see the NEXTSTGPOOL parameter in the define stgpool command. Do not delete a storage pool that is specified as a destination for a management class or copy group in the ACTIVE policy set. For additional parameters, refer to the IBM Tivoli Storage Manager Administrators Reference Guide for your platform.
5-18
How to Move Data

How to Move Data

MOVE DATA
You can move files from one volume to another volume in the same or a different storage pool using the MOVE DATA command. move data source_vol_name target_STGpool
MOVE NODEDATA
You can use the MOVE NODEDATA command to move file spaces for a node from one storage pool to another. move nodedata nodename fromstgpool=source_STGpool tostgpool=target_STGpool
16
Before deleting a storage pool, be sure you have moved all the data you need to retain by issuing the move data command to move the data to another storage pool. To move data from stgvol.1 to stgvol.2 in the same storage pool, issue the following command:
MOVe Data stgvol.1 stgvol.2
The move nodedata command can be used to move data in a sequential access storage pool for one or more nodes and is useful for consolidating data for a specific node within a storage pool. This is helpful for reducing number of volume mounts required during a restore operation. The move nodedata command can also be used to move data for a node to a different storage pool. This is helpful for preparing for client restore processing by first moving data to a random access storage pool. The move nodedata process performs the following tasks: Creates a list of nodes and file spaces to move based on the criteria of the user specified in the move nodedata command. Starts a queue thread to determine a list of volumes to process.
5-19
he volumes added to this list meet the following criteria: Access of READWRITE or READONLY. Have data for the node and file spaces specified by the user.
The volumes list created also becomes the list of volumes to exclude. Once the queue thread is complete a process thread is started. The number of process threads started is determined by the MAXPROCESS parameter. Each process thread that is started performs the following tasks: Selects a volume from the volume list. Processes each bitfile in the volume to determine whether it should be moved. Uses the move data functions to batch up the file and to move the bitfile.
The RECONSTRUCT option specifies whether to reconstruct file aggregates during data movement. Reconstruction removes empty space that has accumulated during deletion of logical files from an aggregate.
5-20
Concurrent Storage Pool Volume Access

Concurrent Storage Pool Volume Access

The Tivoli Storage Manager server allows concurrent read-access and write-access to a volume in a storage pool with the device type of FILE.
The following client sessions can concurrently read and write to FILE volumes: BACKUP RESTORE ARCHIVE RETRIEVE
The following server processes have concurrent read access to FILE volumes: BACKUP DB BACKUP STGPOOL COPY ACTIVEDATA EXPORT/IMPORT NODE EXPORT/IMPORT SERVER GENERATE BACKUPSET RESTORE STGPOOL RESTORE VOLUME
15
Concurrent access improves restore performance by allowing multiple clients access to the same volume at the same time. Server processes that do not have concurrent access to FILE volumes include: AUDIT VOLUME DELETE VOLUME MIGRATION MOVE DATA MOVE NODEDATA RECLAMATION
5-21
Overflow Location for Storage Pool Media

Overflow Location for Storage Pool Media
Text that lists physical location, shown with the MOVE MEDIA command. Used when library becomes full. Applicable to primary or copypool volumes. Volumes must be manually moved to overflow location. Used to associate location of volumes outside of the library. update stgpool archivepool ovflocation=locker24
17
Database Tracking
Use database tracking to update volume location to specified overflow location. Overflow storage pools allow the Tivoli Storage Manager administrator to better manage storage pools that grow beyond the capacity of the library. Database tracking is intended to be used primarily for long-term archive storage pools where the data is maintained on-site but is rarely retrieved for Tivoli Storage Manager processing. The first stage in implementing an overflow storage pool is to define the location of the volumes when they overflow from the library. This may be done either with the define stgpool or update stgpool command and the OVFLOCATION parameter. This parameter is a text description of where the volumes may be found. There is no default value for this parameter. The description may be up to 255 characters in length. The second step is to move the media to the overflow location. Issue the move media command to move media from the library to the overflow location. For example, to move all full volumes in the specified storage pool out of the library.
move media * stgpool=archivepool
At this point, you can check in new scratch volumes.

5-22
The overflow location for a storage pool may be displayed by using the query stgpool f=d (format=detail) command. This command produces output showing the storage pool name, type, associated device class, estimated capacity, and the overflow location.
5-23
Unit 5: Managing Storage Pools and Storage Pool Volumes Automatic Data Movement
Lesson 2: Automatic Data Movement

Migration
Automatic Data MovementMigration
stgpool_A Sales migration path 1. disk (stgpool_D) 2. tape (stgpool_C) stgpool_B Accounting migration path 1. disk (stgpool_A) 2. file (stgpool_B) 3. tape (stgpool_C)
stgpool_D
sales
stgpool_C
accounting
18
Automatic data movement between storage pools is used to balance the performance and cost of different storage devices while ensuring adequate free space to satisfy new space allocations. This process is known as migration. For each storage pool, you define low and high migration thresholds. Migration thresholds are based on a percentage of the storage pools total data-capacity. The low threshold identifies the amount of free space needed to satisfy the daily processing requirements of your business. The high threshold is used to trigger migration and ensure that enough free space is available while migration is performed. The difference between the high and low thresholds indicates the approximate amount of data that will be migrated. To reduce tape mounts and to use the space on tape volumes most effectively (when collocation is not used), ensure that the amount of data that is migrated from a disk storage pool is a multiple of the capacity of a tape volume in the next storage pool. Automatic data movement is also used to free up space on tape volumes by consolidating active data from fragmented tape volumes onto a single volume, leaving the original volumes available for reuse. This process is known as reclamation. For each tape storage pool, you define a reclamation threshold, which indicates the amount of space consumed by data that is no
5-24
longer valid before triggering reclamation. The best practice is to specify a value not less than 50% in order to avoid tape volume reclamation to multiple volumes.
Storage Pool Migration

Storage Pool Migration
When the high threshold is reached, files are migrated to the specified next-in-chain storage pool.
Migration ends when the amount of space used in the storage pool reaches the low migration threshold.
19
No migration occurs if there is no next storage pool. Tivoli Storage Manager first identifies which client node has backed up or migrated the largest single file space, or has archived files that occupy the most space. When the server identifies the client node based on these criteria, the server migrates all files from every file space belonging to that client. The migration applies to those files whose number of days in the storage pool exceeds the value specified by the MIGDELAY parameter. After the files for the first client node are migrated to the next storage pool, the server checks the low migration threshold for the storage pool to determine if the migration process should be stopped. If the amount of space used in the storage pool is now below the low migration threshold, migration ends. If not, using the same criteria as previously described, Tivoli Storage Manager chooses another client node, and the migration process continues. If the value for MIGCONTINUE has been set to YES, then Tivoli Storage Manager continues the migration process based on how long the files have been in the storage pool. The oldest files are migrated first until the low migration threshold is reached. If the value for MIGCONTINUE has been set to NO, then the migration process ends, and a warning message will be issued to the administrator.
5-25
If multiple migration processes are running (controlled by the MIGPROCESS parameter of the define stgpool command), the files for more than one node may be chosen for migration at the same time. If the cache option is enabled, files that are migrated remain on disk storage (that is, the files are cached) until space is needed for new files. You can enable caching by specifying CACHE=YES when you define or update a disk storage pool. When caching is enabled, the migration process leaves behind duplicate copies of files on disk after the server migrates these files to subordinate storage pools in the storage hierarchy. The copies remain in the disk storage pool, but in a cached state, so that subsequent retrieval requests can be satisfied quickly. However, if space is needed to store new data in the disk storage pool, cached files are erased and the space they occupied is used for the new data. The advantage of using a cache for a disk storage pool is that caching can improve how quickly the server retrieves some files. When you use a cache, a copy of the file remains on fast disk storage after the server migrates the primary file to another storage pool. You may want to consider using a disk storage pool with caching enabled for storing space-managed files that are frequently accessed by clients. However, using a cache has some important disadvantages, such as: It can increase the time for client backup operations to complete. It can require more space for the Tivoli Storage Manager database.
The migrate stgpool command allows you to manually run migration for a random access or sequential access primary storage pool.
5-26
Using the Administration Center for Migration
Using the Administration Center for Migration, Screen 1
1. Click Storage Devices in the Tivoli Storage Manager tree. 2. In the Servers table, select a server. 3. Click Select Action, select View Storage Pools.
4. In the storage pools portlet for the server, click a storage pool name. 5. In the properties notebook for the storage pool, click the Migration tab.
20
1. 2. 3. 4. 5.
Click Storage Devices in the Tivoli Storage Manager tree. In the Servers table, select a server. Click Select Action, select View Storage Pools. In the storage pools portlet for the server, click a storage pool name. In the properties notebook for the storage pool, click the Migration tab.
21
5-27
Select the Next storage pool
22
(caching)
1. 2. 3. 4.
Click Storage Devices in the Tivoli Storage Manager tree. In the Servers table, select a server. Click Select Action, select View Storage Pools. In the servers storage pools portlet, click a storage pool name.
5. In the storage pools properties notebook, click the Migration tab.

23
5-28
Reclamation
Reclamation
Reclamation is a process of consolidating the remaining data from many sequential access volumes onto fewer new sequential access volumes. Lower threshold = more tapes; faster reclamation. Higher threshold = fewer tapes, longer reclamation. TAPE_SP1
100%
reclamation threshold 60%
Use the RECLAIM STGPOOL command to initiate an automatic drive reclamation for a sequential access primary or copy storage pool. Empty tapes move back to scratch or private pools. Reclamation of an active-data pool recovers space used by inactive and deleted files.
24
Space on a sequential volume becomes reclaimable as files expire or are deleted from the volume. Reclamation is the process of reclaiming this space. For example, files become obsolete because of aging or limits on the number of versions of a file. When the percentage of reclaimable space exceeds a specified level (the reclamation threshold), the volume is eligible for reclamation. The server checks whether reclamation is needed at least once per hour and begins space reclamation for eligible volumes. You can set a reclamation threshold for each sequential access storage pool when you define or update the pool. When multiple volumes are eligible for reclamation, Tivoli Storage Manager reclaims the eligible volumes in random order. Space within aggregate files is also reclaimed during the reclamation process. An aggregate is a physical file that contains multiple logical files backed up or archived from a client in a single transaction. Unused space from expired or deleted logical files is removed as the aggregate file is copied to another volume during reclamation. The reclaimstgpool command allows you to manually run reclamation for a sequential access primary or copy storage pool.
5-29
Single Drive Reclamation

Single Drive Reclamation

Space reclamation
Sequential access media storage pools
RECLAIM STGPOOL storage pool parameter

Used as a staging area during reclamation
Space requirements
No minimum size Size related to reclamation threshold or storage pool to be reclaimed
25
The reclaimstgpool command points to another storage pool that can be used as the holding area for the data being consolidated. The storage pool specified as the reclaim storage pool may be any primary storage pool on the system or a new primary storage pool created for this purpose. The only disk pool allowed is one with DEVTYPE=FILE. A copy storage pool may not be defined as a reclaim storage pool because data may be only copied to or from a copy storage pool, not moved.
5-30
Example of Single Drive Reclamation

Example of Single Drive Reclamation

Reclaim storage pool:
Enables data to be reclaimed within the hierarchy. Must be sequential access media. Has the pool being reclaimed as its next storage pool.
define stg filepool file define stg tapepool 3570 reclaimstg=filepool upd stg filepool next=tapepool
26
Single drive reclamation is effectively an automation of the move data command and storage pool migration. The move data process moves only the data which has not expired from the storage pool to be reclaimed to the reclaimstgpool. This data may then be migrated back down the Tivoli Storage Manager storage hierarchy to the now empty storage pool volumes. The second half of the single drive reclamation process involves Tivoli Storage Manager migration. A reclaim storage pool should have the storage pool being reclaimed as its next storage pool in the Tivoli Storage Manager hierarchy. This allows data moved into the reclaim storage pool by the reclamation process to be migrated back down through the Tivoli Storage Manager hierarchy. In the example shown above, the TAPEPOOL is a storage pool defined within a single drive library. The TAPEPOOL is defined with the DISKPOOL as its reclaim storage pool, and the DISKPOOL is defined with the TAPEPOOL as its next storage pool.
5-31
Collocation
Collocation
volumes in collocated storage pools A B Files for Client Node A Files for Client Node B volumes in a non-collocated storage pool A and B
Benefits of collocation:
Keeps client data together Can significantly reduce tape mount requests Has faster retrieval time
Costs of collocation:
Uses more tapes Has longer backup time
27
Collocation is a process in which the server attempts to keep files belonging to a single client node or to a single file space of a client node on a minimal number of sequential access storage volumes. You can set collocation for each sequential access storage pool when you define or update the pool. There are four options for collocation when using the define stgpool or update stgpool commands: No Group Node File Space
With collocation, less time is spent searching database entries. By using collocation, you reduce the number of volume mount operations required when users restore, retrieve, or recall many files from the storage pool. Collocation thus improves access time for these operations.
5-32
If collocation is enabled and reclamation occurs, the server tries to reclaim the files for each client node or client file space onto a minimal number of volumes. Collocation cannot collocate data already in a storage pool volume.
5-33
Collocation Volume Selection

Collocation Volume Selection

Setting COLLOCATION=NODE will cause Tivoli Storage Manager to try to put data for one node on as few volumes as possible, using the following selection criteria: A volume that already contains files from the same client node. An empty predefined volume. An empty scratch volume. A volume with the most free space among volumes that already contain data. Setting COLLOCATION=FILESPACE will cause Tivoli Storage Manager to try to put data for file space for one client node on as few volumes as possible, using the following selection criteria: A volume that already contains files from the same file space of that client node. An empty predefined volume. An empty scratch volume. A volume containing data from the same client node. Among volumes that contain data, the one with the most free space.
28
5-34
Collocation Volume Selection, Example 1


A
primary storage pool
A C D
A C
B D
B C D
B C D
tape pool
s tA n e a i t Cl da
s B nt a e i t Cl da
s tC n e a i Cl dat
g lin ll fil fu % 20
h tc ra pty) c s m (e
r fo d up e rv k se ac re B_b ty) D mp (e
Where does data for client D go?

29
5-35

With only three tapes defined to the storage pool, where will the data for Client D go?

A
A C D
A C
B D
B C D
B C D
tape pool
s tA n i e ta Cl da
s tB n e a i t Cl da
s tC n ie ta Cl da
r fo d up e rv k se ac re B_b ty) D mp (e
Where does data for client D go?

30
After the data for Client D goes to the tape for Client A, and a new tape is added, use the move data command to recollocate.
5-36
Collocation by Groups
Collocation by Groups
Groups of nodes can be defined, and the server can then collocate data based on these groups.
Accounting Sales
ntin g
ou Acc
les Sa
31
The define collocgroup command is used to define the group for collocation.
define collocgroup groupname
The define collocmember command is used to add a client node to a collocation group.
define collocmember groupname node1,node2
Some of the benefits of collocation by group are as follows: Reduces unused tape capacity by allowing more collocated data on individual tapes. Minimizes mounts of target volumes. Minimizes database scanning and reduce tape passes for sequential-to-sequential transfer.
Minimizes database scanning which reduces tape passes for sequential-to-sequential transfers, such as reclamation.
5-37
Collocation of Active Data

Collocation of Active Data

There are two ways active data can be collocated to active-data pools: Writing data to multiple pools by using simultaneous write. Simultaneous write is covered in Unit 10. Copying data to an active-data pool using the COPY ACTIVEDATA command. Only active versions of backup data is copied from a primary storage pool to an active-data pool.
copy activedata primary pool name activedata pool name
You can also use the Administration Center to copy active data.
32
5-38
Collocation of Active Data with the Administration Center

View Storage Pools Actions
33
Active-data pool related actions: Create Storage Pool Modify Storage Pool Copy Active Data
5-39
Copy Active Data Form

Copy Active Data Form
34
The Copy Active-data form: Is similar to Backup Storage Pool, but handles active-data pools. Is valid for pools with NATIVE or NONBLOCK format. Enforces that pool data format is the same as source primary pool.
5-40
Student Exercise
Student Exercise
35
5-41
Review Questions
1. Data that is backed up or archived is stored on _______________ in a storage pool. 2. A storage pool is a named set of volumes that all use the same _________ class. 3. Storage pools are chained to create a ______________. 4. The _______________ command is used to define a storage pool. 5. The _______________ command is used to update any parameters in an existing storage pool. 6. The _______________ command is used to query information about one or more storage pools. 7. ________________ is an option in which the Tivoli Storage Manager server attempts to keep files belonging to a single client node or to a single file space of a client node on a minimal number of tape volumes. 8. To have Tivoli Storage Manager collocate data in a storage pool by client file system, set the collocation option to __________. 9. What do you call the process that automatically moves data from a pool to the next storage pool? 10. Which command is available to move the data from a single node out of one storage pool and into another storage pool?
5-42
5-43
Review Answers
1. Data that is backed up or archived is stored on _______________ in a storage pool. volumes 2. A storage pool is a named set of volumes that all use the same ___________ class. device 3. Storage pools are chained to create a ______________. hierarchy 4. The _______________ command is used to define a storage pool. DEFine STGpool 5. The _______________ command is used to update any parameters in an existing storage pool. UPDate STGpool 6. The _______________ command is used to query information about one or more storage pools. Query STGpool 7. ________________ is an option in which the Tivoli Storage Manager server attempts to keep files belonging to a single client node or to a single file space of a client node on a minimal number of tape volumes. Collocation 8. To have Tivoli Storage Manager collocate data in a storage pool by client file system, set the collocation option to __________. filespace 9. What do you call the process that automatically moves data from a pool to the next storage pool? migration
5-44
10. Which command is available to move the data from a single node out of one storage pool into another storage pool? the move nodedata command
5-45
Summary
Summary
Describe the purpose of storage pools, storage pool hierarchies, and storage pool volumes. Create a storage pool. Design and configure storage pools based on given customer requirements. Manage storage pool volumes.
36
5-46
5-47
5-48
6-1
Introduction
Policy management enables the administrator to determine a set of rules explaining how IBM Tivoli Storage Manager will treat data. This set of rules is composed of policy domains, policy sets, management classes, and copy groups.
Objectives
Objectives
Define a new policy domain. Define a new policy set. Define a new management class. Define a new backup copy group. Assign a default management class. Validate a policy set. Activate a policy set. Manage policies with the Administration Center.
6-2
Unit 6: Policy Management How TSM Manages Data
Lesson 1: How TSM Manages Data

Centrally Managed by Business Policy
Centrally Managed by Business Policy
Business Requirements for Data Management

What Data to Backup What Data to Archive Where to Store the Data Number of Versions to Retain The Retention Period
6-3
Policy Management Overview

Policy Management Overview

Policy Domain Active Policy Set Management Class Backup Backup Copy Copy Group Group Archive Archive Copy Copy Group Group
TSM servers
Policies, which are created by the administrator and stored in the database on the server, can be updated and the updates retroactively applied to already managed data. You might have one policy or many depending on business needs. Policies include several elements:
Policy Domain: A set of rules applied to a group of nodes managed by the same set of policy constraints as defined by the policy sets. A node may only be defined to one policy domain per server. A node may be defined to more than one Tivoli Storage Manager server. Policy Set: A collection of management class (MC) definitions. A policy domain may contain a number of policy sets, however, only one policy set in a domain can be active at a time. Management Class: A collection of management attributes describing backup and archive characteristics. There are two sets of MC attributes, one for backup and one for archive. A set of attributes is called a copy group. There is a backup copy group and an archive copy group. For Tivoli Space Manager clients only, there are parameters that affect space management.
6-4
How Tivoli Storage Manager Stores Client Data

How Tivoli Storage Manager Stores Client Data
The client binds files to management class.
The file information is stored in the TSM database.
The files are stored in storage pools.
6-5
Unit 6: Policy Management Defining Policy
Lesson 2: Defining Policy

Policy Domain
Policy Domain
Policy Domain
Client nodes are assigned to a policy domain. Policy domains are groups of one or more policies. Policy domains are stored in the TSM database. Policy domain names may be from 1 to 30 characters. There is no limit to the number of defined policy domains. A client node can only be associated with one policy domain.
Active Policy Set Management Class Backup Backup Copy Copy Group Group Archive Archive Copy Copy Group Group
Default DefaultPolicy PolicySet Set
A policy domain provides you with a logical way of managing backup and archive policies for a group of nodes with common needs. It is a collection of one or more nodes and one or more policies. Each domain is an object stored in the Tivoli Storage Manager database with a name that contains from 1 to 30 characters. Policy domain names should be meaningful. There is no limit to the number of policy domains that can be defined on a Tivoli Storage Manager server. A client node can be associated with only one policy domain on a specific Tivoli Storage Manager server. However, a client or node may be registered (defined) to more than one server. Each domain may have one or more clients or nodes associated with it. The clients or nodes may be running on the same or different platforms. Some installations may only require a single policy domain. A policy domain also contains a grace period backup and an archive retention period. This grace period acts as a safety net to insure that data backed up or archived in a storage pool is not inadvertently deleted.
6-6
Using the Administration Center to Define Policy Domains

Policy Management with the Administration Center: Policy Domain
1. Click Policy Domains and Client Nodes in the Tivoli Storage Manager tree. 2. In the Servers table, select the name of a server. 3. In the policy domains notebook of the server, click Select Action, and select Create a Policy Domain.
6-7
Using the Command Line to Define a Domain

Using the Command Line to Define a Domain

Policy Domain UNIX Active Policy Set
Use the define domain command to define a policy domain for the UNIX clients.
Management Class Backup Backup Copy Copy Group Group Archive Archive Copy Copy Group Group
define domain UNIX description=Policy domain for UNIX clients

8
Domainname: Specifies the name of the policy domain to be defined. This parameter is required. The maximum length of this name is 32 characters. DESCription=description: Specifies a text string that describes the policy domain. This parameter is optional, but it is suggested to provide a meaningful description. The maximum length of the description is 255 characters. BACKRETention=bkretvalue: Specifies the number of days (from the date the backup versions became inactive) to retain backup versions of files that no longer exists on the client system. This is a grace period. ARCHRETention=arch: Specifies the number of days (from the date of archive) to retain archive copies that are bound to a management class that no longer exists on the client system. This is a grace period.
Related commands include: update domain and delete domain. Remember, a policy domain also contains a grace period backup and an archive retention period.
6-8
Define a New Policy Set

Policy Set
There can be only one active policy set per policy domain. There may be any number of inactive policy sets. The policy set is stored in the server database. Policy set names may be from 1 to 30 characters. A policy set is a collection of management classes. A policy set contains one default management class.

9
Each policy set contains a default management class and can contain any number of additional management classes. Policy sets are used to implement different policies based on user and business requirements. Use the assign defmgmtclass command to specify an existing management class as the default management class for a particular policy set. You must assign a default management class for a policy set before you can activate that policy set. It is suggested that the default management class contains both an archive copy group and a backup copy group.
ASsign DEFMGmtclass domainname setname classname
In the Administration Center, you work only with the active policy set.
6-9
Using the Command Line to Define a Policy Set

Using the Command Line to Define a Policy Set

Policy Domain UNIX Active Policy Set lab Management Class Backup Backup Copy Copy Group Group
Use the define policyset command to define a policy set named lab in the UNIX policy domain.
Archive Archive Copy Copy Group Group
define policyset UNIX lab description='Policy set for UNIX clients in the lab'
10
Domainname: Specifies the name of the policy domain to which the policy set belongs. This parameter is required. Setname: Specifies the name you want to assign to the policy set. This parameter is required. The maximum length of this name is 30 characters. Description: Describes the new policy set using a text string. This parameter is optional. The maximum length of the description is 255 characters. It is suggested you use the description since this will define the policy set once it becomes active.
6-10
Defining Management Classes for Policydriven Backup

Management Classes (MC)

A management class represents a business requirements policy or service level agreement. A management class is associated with a backup copy group and archive copy group. The default management class does not require a backup copy group or an archive copy group, but it is a good idea. Clients may explicitly select a management class. Management class information is stored in the server database. Management class names may contain from 1 to 30 characters. A management class can contain a backup copy group, an archive copy group, both copy groups or no copy groups.
11
A management class associates backup and archive groups with files and specifies if and how client node files are migrated to storage pools. Users can bind (which means, associate) their files to a management class through the include-exclude list. Includeexclude lists are discussed in Unit 9.
6-11
Using the Administration Center to Define Management Class
Policy Management with the Administration CenterManagement Class
12
To define a management class using the Administration Center, perform the following steps: 1. Click Policy Domains and Client Nodes in the Tivoli Storage Manager tree. 2. In the Servers table, select the name of a server. 3. In the policy domains notebook of the server, select the name of a domain. 4. In the properties portlet of the domain, click Management Classes. 5. In the table, click Select Action, select Create Management Class.
6-12
Using Command Line to Define Management Class

Using Command Line to Define Management Policy Domain UNIX Class

Active Policy Set lab
Use the define mgmtclass command to define the management class that is named UNIXMC.
define mgmtclass UNIX lab UNIXMC
Management Class UNIXMC Backup Backup Copy Copy Group Group
13
The parameters of the define mgmtclass command are shown below:
Domainname: Specifies the name of the policy domain to which the management class belongs. This parameter is required. Setname: Specifies the name of the policy set to which the management class belongs. This parameter is required. Classname: Specifies the name of the new management class. This parameter is required. Description: Specifies a description of the management class. This parameter is optional. The maximum length of the description is 255 characters. Enclose the description in quotation marks if it contains any blank characters.
6-13
Unit 6: Policy Management Working with Copy Groups
Lesson 3: Working with Copy Groups

Copy Groups
A copy group contains the specific storage management attributes that describe how the server is to manage backed up or archived files.
Copy Groups
Policy Domain Active Policy Set Management Class Backup Backup Copy Copy Group Group
Copy groups contain the parameters that control the generation and expiration of backup and archive data. There are two types of copy groups: backup and archive. Each management class can contain up to two copy groups. If there are two copy groups, they will be:
One for backups One for archives
All copy groups are named STANDARD.

14
6-14
Using the Command Line to Define a Copy Group

Define Copygroup Parameters

Policy Domain Active Policy Set Management Class Backup Backup Copy Copy Group Group
DOMAINNAME SETNAME CLASSNAME STANDARD TYPE=BACKUP (optional; default) TYPE=ARCHIVE DESTINATION FREQUENCY=FREQVALUE VEREXISTS (Backup only) VERDELETE (Backup only) RETEXTRA (Backup only) RETONLY (Backup only) RETVER (Archive only) RETINIT (Archive only) RETMIN (Archive only) MODE=MODE SERIALIZATION=SERIALVALUE
15
Use the define copygroup command to define a new backup or archive copy group within a specified policy domain, policy set, and management class. Additional define copygroup command parameters: DOMAINNAME: Specifies the name of the policy domain for which you are defining the copy group. This parameter is required. SETNAME: Specifies the name of the policy set for which you are defining the copy group. This parameter is required. CLASSNAME: Specifies the name of the management class for which you are defining the copy group. This parameter is required. STANDARD: Specifies the name of the copy group as STANDARD. This parameter is optional. The name of the copy group must be STANDARD, which is the default value. Type=Backup: Specifies that you want to define a backup copy group. The default parameter is BACKUP. This parameter is optional. Type=Archive: Specifies that you want to define an archive copy group. The default parameter is ARCHIVE. This parameter is optional.
6-15
FREQuency=freqvalue: Specifies the minimum interval, in days, between successive backups. This parameter is optional. VERExists: Specifies the maximum number of backup versions to retain for files that are currently on the client file system. This parameter is optional. The default value is 2. VERDelete: Specifies the maximum number of backup versions to retain for files that have been deleted from the client file system after being backed up using Tivoli Storage Manager. This parameter is optional. The default value is 1. RETExtra: Specifies the number of days to retain a backup version after that version becomes inactive. A version of a file becomes inactive when the client stores a more recent backup version, or when the client deletes the file from the workstation and then runs a full incremental backup. The server deletes inactive versions based on retention time even if the number of inactive versions does not exceed the number allowed by the VEREXISTS or VERDELETED parameters. This parameter is optional. The default value is 30 days. RETOnly: Specifies the number of days to retain the last backup version of a file that has been deleted from the client file system. This parameter is optional. The default value is 60. RETVer: Specifies the number of days to keep an archive copy. This parameter is optional. The default value is 365. RETInit: Specifies when the retention time specified by the RETVER attribute is initiated. This parameter is optional. The default value is CREATION. RETMin: Specifies the minimum number of days to keep an archive copy after it has been archived. This parameter is optional. The default value is 365. MODE=mode: Specifies whether a file should be backed up based on changes made to the file since the last time it was backed up. This parameter is optional. The MODE value is only used for incremental backup. This value is ignored during selective backup. The default value is MODIFIED. SERialization=serialvalue: Specifies how files or directories are handled if they are modified during backup processing and what Tivoli Storage Manager should do if a modification occurs. This parameter is optional. The default value is SHRSTATIC.
6-16
Using the Command Line to Define a Copy Group

Using the Command Line to Define a Copy Group Policy Domain UNIX
Use the define copygroup command to define the backup copy group and archive copy group for the UNIXMC management class.
Active Policy Set lab Management Class UNIXMC Backup Backup Copy Copy Group Group
define copygroup UNIX lab UNIXMC standard destination=diskpool define copygroup UNIX lab UNIXMC standard type=archive destination=archivepool

16
Copy Group Attributes

The attributes in the copy group define: The storage pool destination where the backed up or archived data is to be stored. The minimal interval, in days, between backup and archive operations. Whether the file is to be backed up regardless of whether it has been modified since the last backup. Whether the file can be in use when a user attempts to back up or archive the file. The maximum number of different backup versions that may be retained for files no longer on the file system of the client. The retention period, in days, for all but the most recent backup version, and for the last remaining backup version that is no longer on the file system of the client. The number of days that an archive copy is to be retained.
6-17
The set of backup parameters defines the following attributes: frequency mode (modified or absolute) destination copy serialization number of versions number of versions when the file is deleted retention days for all but the last version retention days for the last version when the file is deleted
The set of archive parameters defines the following attributes: frequency (always CMD) mode (always ABSOLUTE) destination copy serialization retention days for archive copies
6-18
Default Server Policies

Default Server Policies
Tivoli Storage Manager provides a predefined policy domain, policy set, management class, backup copy group, and archive copy group. Each policy is stored on the server and named STANDARD.
STANDARD Policy Domain Active Policy Set Management Class Backup Copy Group Archive Copy Group
BACKRETention=30 ARCHRETention=365
17
Using the policy objects provided in Tivoli Storage Manager allows you to begin using IBM Tivoli Storage Manager immediately. As you become familiar with Tivoli Storage Manager you can tailor the standard policies. Backup Retention Grace Period: Specifies the number of days to retain a backup version when the server is unable to rebind the file to an appropriate management class. The default is 30 days. Archive Retention Grace Period: Specifies the number of days to retain an archive copy when the server is unable to rebind the file to an appropriate management class. The default is 365 days.
Issuing the register client node command will fail if STANDARD is deleted.
6-19
Policy Settings in STANDARD Domain

Policy Settings in STANDARD Domain

These values come with Tivoli Storage Manager in the STANDARD Domain:
Type = Backup DESTination = Backuppool VERExists = 2 VERDeleted = 1 RETExtra = 30 RETOnly = 60 SERialization = SHRSTatic
Type = Archive DESTination = Archivepool FREQuency = Cmd RETver = 365 MODE = ABSolute SERialization = SHRSTatic
18
6-20
Unit 6: Policy Management Expiration
Lesson 4: Expiration
Expiration is the process by which files are identified for deletion because their expiration date or retention period has passed. Backed up or archived files are marked expired by IBM Tivoli Storage Manager based on the criteria defined in the backup or archive copy group. Expire inventory manually starts inventory expiration processing. The inventory expiration process removes client backup and archive file copies from server storage based on policy specified in the backup and archive copy groups of the management classes to which the files are bound.
Expire Inventory
19
6-21
Related Server Option: EXPINterval Hours

Related Server Option: EXPINterval Hours

The EXPINterval Hours option: Specifies the number of hours between automatic inventory expiration runs. Has a minimum value of 0, where automatic expiration does not occur and must be started with the expire inventory command. Has a maximum value of 336 hours (14 days). Has a default value of 24 hours. Inventory expiration is resource intensive. You can set the EXPINterval to 0 and schedule expiration during slower periods.
20
Copies of files that have expired are not deleted from server storage until expiration processing occurs. You can run expiration processing either automatically or by command. You control automatic expiration processing by using the expiration interval option (EXPINTERVAL) in the Tivoli Storage Manager options file (dsmserv.opt). Expiration processing then deletes eligible backup versions and archive file copies. Backup versions are eligible based on policy in the backup copy group (how long and how many inactive versions are kept). Archive file copies are eligible based on policy in the archive copy group (how long archived copies are kept). If you need to cancel inventory expiration, use the command
cancel expiration.
Do not cancel the process.
6-22
Example of Expiration Processing: Part 1


day
changed
backup versions
resume.doc
Frequency = 0 Verexists = 3 Verdeleted = 1 Retextra = 30 Retonly = 60 Mode = modified
changed
changed
changed
changed
21
The slide shows the life cycle of a backed up client file as it is stored in a TSM storage pool. A scheduled incremental backup and expire inventory run every day and the copy group values for this file are: Frequency = 0 Verexists = 3 (Maximum) Verdeleted = 1 Retextra = 30 (File exists on workstation) Retonly = 60 (File deleted from workstation) Mode = modified
Use the chart in the slide to consider what happens as TSM is backing up a changed file every day. For this scenario, on day 6, the file goes unchanged. On day 1 the file is changed or created. That evening it is backed up. The file would be marked as active. The same logic applies through day 4. Follow this logic through to day 4. Put the letter I (for inactive) on the extra versions. On day 4, because we are only keeping three versions of the file, the fourth backup is removed. Versions beyond the first three for days 4, 5, and 6 would not be kept.
6-23


day
changed
backup versions
resume.doc
changed
changed
changed
A = active I = inactive
22
Assume a scheduled incremental backup and expire inventory run every day and that backup and copy group values for this file are: Frequency = 0 Verexists = 3 (Maximum) Verdeleted = 1 Retextra = 30 (File exists on workstation) Retonly = 60 (File deleted from workstation) Mode = modified
In this example, notice that the backup 1 on day 4 is gone because we are keeping only three versions based on VERExist=3. Notice, too, that the file goes unchanged after day 4. In this case, can you predict the results for day 33? On day 33, you would expect to see only one version. This is because RETAINEXTRA is set to 30 and needs to be NO LIMIT if you always want three versions. Can you predict when backup 2 would expire?
6-24
Backup 2 would expire on day 33 because it became inactive on day 3 and you would add 30 days based on RETEXTRA=30.
Tivoli Storage Manager File Backup Processing: Part 3


day
changed
backup versions
resume.doc
changed changed
A = active I = inactive
23
Assume a scheduled incremental backup and expire inventory run every day and that copy group values for this file are: Frequency = 0 Verexists = 3 (Maximum) Verdeleted = 1 Retextra = 30 (File exists on workstation) Retonly = 60 (File deleted from workstation) Mode = modified
Can you predict what happens if the file is erased on the morning of day 4? Backup 3 will go inactive if the file is deleted. How many extra copies will be there after the incremental backup on day 4?
6-25
To determine this, notice that VERDELETED is set to 1. This means that backups 1 and 2 will be lost.
Can you predict when the only backup will go away? The only backup will go away on day 64 because RETONLY is set to 60.
6-26
Storage Management Archive File Management

Storage Management Archive File Management

JAN 2008 FEB 2008 MAR 2008 APR 2008
Retain archive copy for 12 months.
Archived 01/01/08
MAY 2008
Archived 01/01/08
JUN 2008
Archived 01/01/08
JUL 2008
Archived 01/01/08
AUG 2008
Archived 01/01/08
SEP 2008
Archived 01/01/08
OCT 2008
Archived 01/01/08
NOV 2008
Archived 01/01/08
DEC 2008
Archived 01/01/08
Archived 01/01/08
Archived 01/01/08
Archived 01/01/08
The expiration processing is run on 01/01/09, after 12 months.
There is no versioning with archiving.
JAN 2009
Archived 01/01/08
24
The RETAIN VERSION that is specified in the archive copy group specifies the number of days an archived copy remains in data storage. When the specified number of days elapses for the archived copy of the file, IBM Tivoli Storage Manager deletes the file from data storage. Unlike the backup function, archive does not allow multiple versions of data files and directories.
6-27
Specifying the Management Class

Specifying the Management Class
25
The management class specified in the policy domain defines the backup and archive criteria for client nodes in the policy domain. Client users have the option of creating an include-exclude list to identify what files are eligible for backup services and to specify how IBM Tivoli Storage Manager will manage backed up or archived files. The INCLUDE and EXCLUDE options are specified in the client option file. If you do not specify the Management Class, the default Management Class is used.
6-28
Policy Domain Grace Retention Periods

Policy Domain Grace Retention Periods

The policy domain grace retention period is specified in define domain command.
Backup retention grace period defaults to 30 (BACKRETention=30). Archive retention grace period defaults to 365 (ARCHRETention=365).
The policy domain grace retention period is used when default MGMTCLASS has no copy group for backup and archive.
One of the following situations must also apply:

MGMTCLASS for backup no longer contains backup copy group. MGMTCLASS for an archive no longer contains archive copy group. MGMTCLASS no longer exists.
26
Each policy domain contains a backup grace retention period and an archive grace retention period. The grace retention period is used to protect backup versions and archive copies from immediately being deleted when the default management class does not contain a backup or archive copy group.
6-29
Assign Default Management Class

Assign Default Management Class
Use the assign defmgmtclass command to specify a management class as default.
ASSIGN DEFMGMTCLASS UNIX lab UNIXMC
27
You must assign a default management class for a policy set before you can activate that policy set. To ensure clients can always back up and archive files, choose a default management class that contains both an archive copy group and a backup copy group. DOMAIN_NAME: Specifies the policy domain to which the management class belongs. POLICY_SET_NAME: Specifies the policy set for which you want to assign a default management class. You cannot assign a default management class to the ACTIVE policy set. CLASS_NAME: Specifies the management class that is to be the default management class for the policy set.
6-30
Validate and Activate Policy Sets
Validate and Activate Policy Sets

Use the validate policyset command to verify that a policy set is complete and valid prior to activating it. VALIDATE POLICYSET UNIX lab Use the activate policyset command to specify a policy set as the Active policy set for a policy domain. ACTIVATE POLICYSET UNIX lab When a policy set is activated, its contents are copied to a policy set that has the reserved name ACTIVE. Policy sets are automatically validated and activated when you use the Administration Center to define or modify the management class.
28
The validate command examines the management class and copy group definitions in a specified policy set and reports on conditions that need to be considered if the policy set is to be activated. After a change is made to a policy set, and the policy set is validated, then the policy set must be activated to make it the ACTIVE policy set. The validate policy set command will fail if any of the following conditions exist: A default management class is not defined for the policy set. A copy group within the policy set specifies a copy storage pool as a destination. A management class specifies a copy pool as the destination for space-managed files.
When a policy set is activated, the contents of the policy set are copied to a policy set that has the reserved name ACTIVE. Once activated, there is no real relationship between the policy set that has been activated (copied to ACTIVE) and the contents of the ACTIVE policy set. The original policy set can still be modified, but the copied definitions in the ACTIVE policy set can only be modified by activating another policy set.
6-31
Bind Files to the Management Class (MC)

Bind Files to the Management Class (MC)

incremental backup
Monday
/usr/WhatsUp.doc
archive
Monday BigFile.txt MC_ARCH_1
inactive versions
Wednesday
MC1 /usr/WhatsUp.doc
Friday
MC1 /usr/WhatsUp.doc
active version
MC1
Tuesday BigFile.txt MC_ARCH_2
Friday BigFile.txt MC_ARCH_1
Bind /usr/*.doc files to management class MC1: include /usr/*.doc MC1
The MC is bound to the file during backups. All backup versions of a file are bound to the same MC. Backup versions of a file can be rebound to a different MC.
The MC is bound to the file during archive. Archive files are never rebound to a different MC. Different archives of the same file may have a different MC.
29
Binding is the process of associating a file name with a management class name. Files are bound to a management class name when: A user can bind a file to a specific management class name using the INCLUDE option on an include-exclude list. A user can bind a file to a management class name using the ARCHMC option when archiving a file. A user can bind a directory to a management class name using the DIRMC option when backing up a file. The client node can bind a file to the default management class in the active policy set, when a user does not bind to a specific management class name.
Rebinding is the process of associating a file with a new management class name. Archive files are never rebound since each archive operation creates a different archive copy.
6-32
Rebinding Management Classes to Backup Versions

Rebinding Management Classes to Backup Versions

Backup versions are rebound to a different management class name in the following cases:
Users change the management class assigned to a file by specifying a different management class in an include-exclude list and then performing an incremental or selective backup.
An administrator activates a policy that does not contain the management class.
An administrator assigns a client node to a different policy domain and the active policy set in that policy domain does not have a management class with the same name.
30
All backup versions are re-bound to the new MGMTCLASS. If the management class to which files are bound is deleted, IBM Tivoli Storage Manager uses the attributes of the default management class to manage the backup versions.
6-33
Copy Domain
Copy and Update a Domain

To copy an existing domain to create a new domain, issue the following command:
copy domain original_domain new_domain

Update the new domain to specify DESCription BACKRETention ARCHRETention ACTIVEDESTination
update domain new_domain description=description' backretention=value archretention=value activedestination=active-data pool name
31
To copy an existing domain named priority to create a new domain named critical, issue the following command:
copy domain priority critical
Update the new critical domain to specify the following updates: An active-data pool named adpool as the destination for active versions of backup data A backup retention grace period of 120 days An archive retention grace period of 2 years (730 days)
Issue the following command:

update domain critical description='Critical Policy Domain' backretention=120 archretention=730 activedestination=adpool
6-34
Export/Import of Policy
Export/Import of Policy
Use the export policy command to export definitions for policy domains, policy sets, management classes, backup and archive copy groups, and schedules to another server. export policy replacedefs=yes toserver=servergray
32
The export policy command moves policy information from one or more policy domains. Policy information includes policy domain and set definitions, management class definitions, backup, copy group and archive group definitions, schedule definitions for each policy domain, and client node associations.
6-35
Student Exercise
Student Exercise
33
6-36
Review Questions
1. The __________ command examines the management class and copy group definitions in a specified policy set and reports on conditions that need to be considered if the policy set is to be activated. a. activate b. bind c. validate d. reclamation 2. Each management class can contain up to ______ copy groups. 3. Each policy is stored on the server and named ___________. 4. True or False? A TSM client node can be associated with multiple policy domains on the same Tivoli Storage Manager server. 5. Copies of files that have expired are not deleted from server storage until ______________________ occurs.
6-37
Review Answers
1. The __________ command examines the management class and copy group definitions in a specified policy set and reports on conditions that need to be considered if the policy set is to be activated. a. activate b. bind c. validate d. reclamation c. validate 2. Each management class can contain up to ______ copy groups. two 3. Each policy is stored on the server and named ___________. Standard 4. True or False? A TSM client node can be associated with multiple policy domains on the same Tivoli Storage Manager server. false 5. Copies of files that have expired are not deleted from server storage until _______________ occurs. expiration processing
6-38
Summary
Summary
Define a new policy domain. Define a new policy set. Define a new management class. Define a new backup copy group. Assign a default management class. Validate a policy set. Activate a policy set. Manage policies with the Administration Center.
34
6-39
6-40
7-1
Introduction
The Tivoli Storage Manager database is used by the server to manage information about client files. The Tivoli Storage Manager recovery log is used to ensure the consistency and availability of the database. This unit covers how to choose the size and location of the database and recovery log. You will also configure the database and recovery log for improved performance.
Objectives
Objectives
Identify the purpose of the database and recovery log volumes. Choose the location of the database and recovery log. Determine the size of the database and recovery log. Configure the database and recovery log to optimize performance. Configure the database and recovery log for high availability.
7-2
Unit 7: Customizing the Tivoli Storage Manager Database and Recovery Log The Purpose of the Database and Recovery Log
Lesson 1: The Purpose of the Database and Recovery Log


TSM server
The TSM database is used by the server to manage information about client files.
The recovery log ensures consistency and availability of the database.
backup-archive client
3
The Tivoli Storage Manager database contains information that is needed for server operations and information about client data that has been backed up, archived, and spacemanaged. The database does not store client data. Instead, the database points to the locations of the client files in the storage pools. The database includes information about: Client nodes and administrators Policies and schedules Server settings Locations of client files on server storage Server operations (for example, activity logs and event records)
7-3
The recovery log contains information about database updates that have not yet been committed. Updates can include activities such as defining a management class, backing up a client file, and registering a client node. Changes to the database are recorded in the recovery log to maintain a consistent database image.
7-4
Transactions
Transactions
backup-archive clients
A transaction is the unit of work exchanged between the TSM client and TSM server. To support multiple transactions from concurrent client sessions, the server holds the transaction log records in the recovery log buffer until they can be written to the recovery log. The transaction is committed. TRANSACTION COMMIT is the writing of all the log records for that transaction to the recovery log. The TSM database is updated.
4
recovery log buffer
The transaction records remain in the buffer pool until the active buffer becomes full or IBM Tivoli Storage Manager forces log records to the recovery log. The log records are moved to the recovery log volume disk when the transaction is committed. Changes resulting from transactions are held in the buffer pool temporarily and are not made to the database immediately. Therefore, the database and recovery log are not always consistent. When all records for a transaction are written to the recovery log, IBM Tivoli Storage Manager updates the database. The transaction is then committed to the database. At some point after a transaction is committed, the server deletes the transaction record from the recovery log. When a transaction occurs, the Tivoli Storage Manager server performs the following actions: 1. Reads a database page into the database buffer and updates it. A page is a 4096 byte block that is transferred as a unit between memory and disk storage. 2. Writes a transaction log record to the recovery log to describe the action that is occurring and associates it with the database page in case the database page needs to be rolled back during recovery. 3. Writes the database page to the database, releasing it from the buffer pool. The page remains in the buffer pool until buffer space is needed for another page.

7-5
Recovery Log
The recovery log is used by the server to keep a record of all changes to the database. When a change occurs, the recovery log is updated with some transaction information prior to the database being updated. This enables uncommitted transactions to be rolled back during recovery, so the database remains consistent.
Recovery Log
Log space in normal mode is managed as a circular array of blocks. Out of log space causes in-process transactions to stop. Log space is freed when transactions commit or stop. Log records changes prior to database update.
Old New
Use normal mode for first complete backup, then change to roll-forward.
5
The recovery log functions in two modes: normal mode and roll-forward mode.
Normal Mode
When the transaction log record is written to the recovery log, a recovery point is recorded in it, and the data is committed to the database. A point of consistency is a time when all recoverable information in the database matches the data managed by the server. If the database needs to be recovered, the server uses the recovery point in the recovery log to bring the database back to its last point of consistency. If a failure occurs before a transaction is committed to the database, the server rolls back any changes made to the database pages. The log is treated as a circular array of blocks with the head (the newest log records) always chasing the tail (oldest records). The server will never let the head overtake and overwrite the tail; it must take some other action. As transactions commit, they free up log space and allow the tail to move forward. The recovery log saves some records for transactions that
7-6
have already been committed, but only to the extent necessary to perform redo processing on recovery.
Roll-Forward Mode
In roll-forward mode, all changes made to the database since the last database backup are saved in the recovery log. With roll-forward mode and an intact recovery log, you can recover the database up to its most current state (the point at which the database was lost). The recovery log keeps all transactions since the last database backup. In this mode you should significantly increase the recovery log size. However, frequent database backups reduce recovery log storage requirements (after a backup is completed, recovery log records preceding the backup are deleted).
7-7
Database Space Allocation

?N
TSM Database Space Allocation

Considerations:
The database is predominately read-oriented. The TSM database volumes should be distributed across disks for improved performance.
Refer to the IBM Tivoli Storage Manager Performance Tuning Guide for more information.
Determine How Many Database Volumes You Need

Database access is predominately read-oriented. Placing the database volumes over multiple physical volumes may improve performance because this allows the logical volume manager to spread the I/O load over more volumes. This is also true when mirroring is used because the logical volume manager schedules read operations to the least busy volume in a mirror set. However, keep the number of volumes reasonable (less than 12), to reduce space used for logical volume manager overhead. The maximum database size limit is 530 GB. If you notice a performance problem, consider adding another TSM server.
7-8
Recovery Log Space Allocation

Recovery Log Space Allocation

Considerations: The recovery log is predominately write-oriented. The recovery log should not be distribute over multiple disks. The log file maximum size limit is 13 GB. Refer to the IBM Tivoli Storage Manager Performance Tuning Guide for more information.
Allocate on separate physical volume from database.
Determine How Many Database Volumes You Need

Access to the recovery log is predominately write-oriented with the writes and the few reads clustered together. The writes are done in a moving cursor format, which does not lend itself to multiple volume optimizations. Therefore, fewer recovery log volumes are appropriate. Mirroring has little effect on the performance of the recovery log. The maximum log file size limit is 13 GB. Using the Administration Center, you can create 12 GB recovery logs. Volumes used to contain the database and the recovery log must be disk volumes.
7-9
Unit 7: Customizing the Tivoli Storage Manager Database and Recovery Log Sizing the Database and Recovery Log
Lesson 2: Sizing the Database and Recovery Log

Estimating Space Requirements for the Database
Estimating Space Requirements

Each version of a file that Tivoli Storage Manager stores requires about 400 to 600 bytes of database space. Each cached file, copy storage pool file, and active-data pool file requires about 100 to 200 bytes of database space. Caching is turned off by default. It is only used for moving from one storage pool to next. Overhead could increase the required space up to an additional 25%.
The size of your Tivoli Storage Manager database depends on the number of client files to be stored and how Tivoli Storage Manager manages them. If you can estimate the maximum number of files that might be in server storage at any time, you can use the following information to come up with a useful database size estimate: Each version of a file that Tivoli Storage Manager stores requires about 400 to 600 bytes of database space. Each cached or copy storage pool copy of a file requires about 100 to 200 bytes of database space. Caching is turned off by default. It is only used for moving from one storage pool to next. Overhead could increase the required space up to an additional 25%.
7-10
In the following example, the computations are probable maximums.The numbers are not based on the use of file aggregation. In general, the more that small files are aggregated, the less database space required.
Estimating the Size of the Database

Backed up files Up to 500,000 client files might be backed up. Storage policies call for retaining up to three copies of backed up files. Archived files Up to 100,000 files might be archived copies of client files. Space-managed files Up to 200,000 files migrated from client workstations might be in server storage. [(500,000 X 3 ) + 100,000 + 200,000)] x 600 bytes = 1.0 GB Copy storage pool files All primary storage pools are backed up to the copy storage pool: (1,500,000 + 100,000 + 200,000) x 200 bytes = 343 MB Active-data pool files All the active client backup data in primary storage pools is copied to the activedata pool. Assume that 500,000 versions of the 1,500,000 backup files in the primary storage pool are active. 500,000 x 200 bytes = 95 MB Estimated database size is 1.5 GB File space (1.0 GB) + copy space (343 MB + 95 MB = 438 MB)
9
7-11
Cached Files
Cached Files
Disk pool caching:
Cached copy requires 100 - 200 bytes of database space. Average file size is about 10 KB. About 100,000 files are in cache at any one time. 100,000 files x 200 bytes = 20
MB
Caching is enabled in the disk storage pool. The disk pool has a capacity of 5 GB and uses the default high migration threshold (90%) and low migration threshold (70%). Thus, if migration begins at 90% and stops at 70%, 20% of the disk pool, or 1 GB, is occupied by cached files.
10
7-12
Estimating the Size of the Recovery Log

In both normal mode and roll-forward mode, the volume of Tivoli Storage Manager transactions affects how large you should make your recovery log. As more clients are added and the volume of concurrent transactions increases, you should extend the size of the log. In roll-forward mode you must also consider how often you perform database backups. In this mode, the recovery log keeps all transactions since the last database backup and typically requires significantly more space than is required in normal mode. In roll-forward mode, you need to determine how much recovery log space is used between database backups. For example, if you plan daily incremental backups, you should check your daily usage over a period of time. You can use the following procedure to make your estimate.
Estimating the Size of the Recovery Log

Easy estimation rules for recovery log size requirements: (1 KB of recovery log space) x (daily number of transactions) or 5% to 10% of total database size for normal mode and 10% to 15% of total database size for roll-forward mode
11
For example, over a period of a week the highest cumulative consumption value was 500 MB. If you set your recovery log to 650 MB you should have sufficient space between daily backups.
7-13
Unit 7: Customizing the Tivoli Storage Manager Database and Recovery Log Adding Space
Lesson 3: Adding Space

DEFine DBVolume volume_name Formatsize=format size EXTend DB mb
DEFine LOGVolume volume_name Formatsize=format size EXTend LOG mb

12
Define: Use the define dbvolume command to define a new database volume and use the define logvolume command to define a new recovery log volume. Another method to allocate a new Tivoli Storage Manager database volume is by using the define dbvolume command with the FORMATSIZE option from either the Tivoli Storage Manager console or an administrative client. Extend: Use the extend db command to increase the amount of space that can be used by the database within all the database volumes previously allocated to Tivoli Storage Manager. Use the extend log command to increase the amount of space that can be used by the recovery log within all the recovery log volumes previously allocated to Tivoli Storage Manager.
7-14
Examples
AIX Example
DEFine DEF DEFine DEF EXTend EXTend EXT EXT DBVolume volume_name Formatsize=[format size] DBVol /usr/tivoli/TSM/server/dbvol/db2.dsm F=12 LOGVolume volume_name Formatsize=[format size] LOGVol /usr/tivoli/TSM/server/rclog/log2.dsm F=8 DB mb LOG mb db 12 log 8
Linux Example
DEFine DEF DEFine DEF EXTend EXTend EXT EXT DBVolume volume_name Formatsize=[format size] DBVol /opt/tivoli/TSM/server/dbvol/db2.dsm F=12 LOGVolume volume_name Formatsize=[format size] LOGVol /opt/tivoli/TSM/server/rclog/log2.dsm F=8 DB mb LOG mb db 12 log 8
Note: For UNIX users, the database name is case sensitive. Remember this when typing in the name of your volume. It is a best practice not to have your database and logs in the /bin directory.
Windows Example
DEFine DEF DEFine DEF EXTend EXTend EXT EXT DBVolume volume_name Formatsize=[format size] DBVol D:\TSM\SERVER\db2.dsm F=12 LOGVolume volume_name Formatsize=[format size] LOGVol D:\TSM\SERVER\log2.dsm F=8 DB mb LOG mb db 12 log 8
7-15
Database and Recovery Log Space

Volumes used to contain the database and the recovery log must be disk volumes.
Database and Recovery Log Space Considerations
Available Space Assigned Capacity Maximum % Used Maximum Reduction % Utilization Volumes used for database and recovery log must be disk volumes. All volumes treated as a single logical volume.
13
Maximum Extension
IBM Tivoli Storage Manager treats all volumes associated with the database or with the recovery log as a single logical volume. The logical volume manager maps data between logical and physical storage, allowing database and recovery log data to span physical disks. No reorganization of the database or recovery log is required. The amount of available space for the database or recovery log equals the combined space of all volumes defined to the database or recovery log. As data is added, Tivoli Storage Manager tracks the percentage of utilization, which is the amount of space used at a specific point in time. Be aware that the maximum amount of space used by the recovery log can vary significantly throughout the day, as it is proportional to the transaction load on the system. The maximum amount of space used by the database is more consistent with the utilization percentage, because the amount of database space consumed grows in proportion to the number of objects inserted into the database. Note: It is a good practice to always have extension space available.
7-16
Using the Administration Center

Using the Administration Center to Create, View, and Modify Database and Log Volumes
14
TSM Administration Centers Database and Recovery Log Tasks
15
7-17
Unit 7: Customizing the Tivoli Storage Manager Database and Recovery Log Reducing the Database and Recovery Log Space
Lesson 4: Reducing the Database and Recovery Log Space

Reducing the Database and Recovery Log Space

REDUCE DB size
REDUCE LOG size
You should only need to run these commands if you want to redesign the volume layouts, or if you redefine volume to Tivoli Storage Manager.
16
There are some additional commands that can be used to decrease both database and recovery log space. Use the reduce db command to decrease the amount of space that can be used by the database. To reduce the capacity of the database, you must reduce the database in 4 MB increments. If you do not specify the reduction in 4 MB increments, Tivoli Storage Manager rounds the number to the next 4 MB partition. Use the reduce log command to decrease the amount of space that can be used by the recovery log. To reduce the capacity of the recovery log, you must reduce the recovery log in 4 MB increments. If you do not specify the reduction in 4 MB increments, Tivoli Storage Manager rounds the number to the next 4 MB partition. The log must be in normal mode.
For example, if you specify 11 MB, the server will round up to 12 MB when doing the extend or reduce operation. This does not apply to data storage. There is no notion of extending or reducing storage pool storage other than in volume increments.
7-18
Unit 7: Customizing the Tivoli Storage Manager Database and Recovery Log Mirroring
Lesson 5: Mirroring
Database and Recovery Log Mirroring
Database and Recovery Log Mirroring
Does not disrupt recovery.
Reads from device with best response time.
log1 DB1
mirror
DB1 copy
log1 copy
17
The availability of the database and recovery log is ensured, by providing protection from logical errors and from device or media failures. Mirroring offers additional flexibility to that of using a hardware dual copy. Mirroring has the following benefits: Three copies can be supported. You have finer control over what is mirrored. Copies may be on physical volumes that reside on different storage control units. Support for multiple and different direct access storage device types. Read performance improves with mirroring because the server will read from the device with the best response time.
7-19
Note: It is not advisable to independently mirror volumes used for the database or recovery log, although it is allowed.
Using the Administration Center to Mirror

Using the Administration Center to Mirror Volumes
18
7-20
Mirroring Examples
Mirroring Examples
Mirror database volume 4: define database copy primary copy mirror copy Formatsize=size def dbcopy e:\tsmdata\server1\db4.dsm f=12 k:\mirs\db4mir.dsm
def dbcopy /usr/tivoli/tsm/server/bin/db4.dsm /usr/tivoli/tsm/server/mirs/db4mir.dsm f=12 Mirror log volume 2: define log copy primary copy mirror copy Formatsize=size def logcopy e:\tsmdata\server1\log2.dsm k:\mirs\log2mir.dsm f=8 def logcopy /usr/tivoli/tsm/server/bin/log2.dsm /usr/tivoli/tsm/server/mirs/log2mir.dsm f=8
19
To format and define a mirror, issue the following command:

define database copy primary copy mirror copy formatsize=size
7-21
Unit 7: Customizing the Tivoli Storage Manager Database and Recovery Log BUFPOOLSIZE Parameters
Lesson 6: BUFPOOLSIZE Parameters

IBM Tivoli Storage Manager can dynamically adjust the size of the database buffer pool or you can adjust it manually. The database buffer pool is storage that is used as a cache allowing database pages to remain in memory for long periods of time. This enables the server to make continuous updates to pages without requiring input or output operations from external storage.
BUFPOOLSIZE Parameters
Server expiration processing resets the database buffer pool before the next processing starts and examines if the database buffer pool cache hit ratio is above 98%. If the cache hit ratio is lower than 98%, the database buffer pool will be increased; if it is higher, the buffer pool size will not change. Increasing the database buffer pool will not use more than 10% of available real storage.
BUFPOOLSIZE The minimum size is 256 KB The maximum size is limited by available memory The default is 32768 KB Suggested size is 131072 KB for server with 1 GB real memory (10% to 15% of real memory).
20
To have the server automatically tune the BUFPOOLSIZE option, set the SELFTUNEBUFPOOLSIZE option to YES. The default is NO. If you specify YES for the SELFTUNEBUFPOOLSIZE server option, the database buffer pool is dynamically adjusted. The cache hit ratio statistics for the buffer pool are reset at the beginning of expiration. After expiration processing completes, the buffer pool size is adjusted dynamically. Use the setopt bufpoolsize command to change the buffer pool size.
7-22
Unit 7: Customizing the Tivoli Storage Manager Database and Recovery Log Space Triggers
Lesson 7: Space Triggers

Define Spacetrigger
Define Spacetrigger
Use the define spacetrigger command to define settings for triggers that determine when and how Tivoli Storage Manager prepares additional space when predetermined thresholds have been exceeded in the database and recovery logs. DEFine SPACETrigger db fullpct=80 spaceexpansion=20 expansionprefix=c:\tsmserver\ mirrorprefixes=f:\mirvol1\,g:\mirvol2\ max=10000 DEFine DBCopy Query SPACETrigger db
Operation Results:
DB Full Percentage DB Space Expansion Percentage ---------- ----------80 20 DB DB Maximum Expansion Size Prefix (Megabytes) ------------ ----------C:\tsmserver 10000 Mirror Prefix1 Mirror Prefix2
------------ ---------F:\mirvol2\ F:\mirvol1\
Space triggers can be created, viewed, and modified with the Administration Center.
21
When the server performs an internal data movement operation, such as migration, reclamation, move data, or storage pool backup or restore, it will adjust the values of automatic performance tuning parameters, if configured, to achieve optimal performance. To prevent running out of log space during these operations, use the define spacetrigger command to allow for expansion of the recovery log. Administrator-defined space triggers tell the Tivoli Storage Manager server when to increase the size of the database or log. Space triggers define a maximum utilization percentage. When that utilization percentage is reached, the first step is to increase the size of the database or log, using space previously allocated but not used. The extend command is used to do this. If there is no previously allocated space, or if there is insufficient space to reduce the utilization percentage below the trigger value, the database or log is expanded. The first step in expanding the database is to allocate a new volume. A volume prefix name and the amount of space by which to extend as a percentage of the existing database or log must be predefined. A constraining upper limit can be defined for the database or log to prevent
7-23
extension beyond a certain point. When volume allocation formatting is finished, the database or log will be extended by the size of the newly allocated volumes. Mirrored volumes will be allocated as well if the database or log is mirrored. The define spacetrigger command defines settings for the database and recovery log that determine when and how Tivoli Storage Manager deals with space shortages in the database and recovery log. The first parameter specifies whether the database or log is to be managed by automatic space trigger extension (the example shown is for a database). Database triggers are covered in Unit 10. The following parameters can be added.
Parameter
Fullpct=percentage
Description Specifies that when this value is reached Tivoli Storage Manager will acquire more space for expansion. Specifies the expansion size as a percentage of the existing size. Tivoli Storage Manager creates new volumes in multiples of 9 MB to achieve the required size. Specifies the prefix to use when creating the expanded files. The prefix name can include one or more directory separator characters (for example: J:\tsmtivoli storage managerserv\). Storage Manager does not check the prefix name for validity and automatic expansion can fail if invalid. Specifies the maximum allowable size of the database or log. If below this size when the utilization trigger is reached, the expansion will proceed, even if the expanded size exceeds this maximum size setting. Subsequent expansions will then fail because this size was exceeded. Specifies the prefix or prefixes that Tivoli Storage Manager uses to create new files for database or recovery log copy volumes.
SPACEexpansion= percentage
EXPansionprefix= prefixname
MAXimumsize=number
MIRRORprefixes
Note: To specify a directory as your prefix and allow the server to create files in that directory, use a backslash at the end of the directory you are specifying. Put quotation marks around the mirror prefix to ensure the directory separator characters are interpreted correctly.
7-24
Student Exercise
Student Exercise
22
7-25
Review Questions
1. True or False? The recovery log is predominately read-oriented. 2. In which mode is the recovery log treated as a circular array of blocks with the head (the newest log records) always chasing the tail (oldest records)? a. Normal mode b. Roll-forward mode 3. In which mode does the recovery log track all transactions between database backups? a. Normal mode b. Roll-forward mode 4. To prevent running out of log space during these operations, use the ____________command to allow for expansion of the recovery log. 5. To have the server automatically tune the BUFPOOLSIZE option, set the ___________________________ option to YES. a. BUFFPOOLMEMSIZEON b. SELFTUNEBUFPOOLSIZE c. MAXSIZEBUFFPOOL d. SELFTUNEBUFPOOLMEM
7-26
7-27
Review Answers
1. True or False? The recovery log is predominately read-oriented. false 2. In which mode is the recovery log treated as a circular array of blocks with the head (the newest log records) always chasing the tail (oldest records)? a. Normal mode b. Roll-forward mode a. Normal mode 3. In which mode does the recovery log track all transactions between database backups? a. Normal mode b. Roll-forward mode b. Roll-forward mode 4. To prevent running out of log space during these operations, use the ____________command to allow for expansion of the recovery log. define spacetrigger 5. To have the server automatically tune the BUFPOOLSIZE option, set the ___________________________ option to YES. a. BUFFPOOLMEMSIZEON b. SELFTUNEBUFPOOLSIZE c. MAXSIZEBUFFPOOL d. SELFTUNEBUFPOOLMEM b. SELFTUNEBUFPOOLSIZE
7-28
Summary
Summary
Identify the purpose of the database and recovery log volumes. Choose the location of the database and recovery log. Determine the size of the database and recovery log. Configure the database and recovery log to optimize performance. Configure the database and recovery log for high availability.
23
7-29
7-30
Unit 8:
Client Configuration
8-1
Introduction
This unit describes how to manage and configure client options and invoke the backuparchive interfaces available with IBM Tivoli Storage Manager.
Objectives
Objectives
Upon completion of this unit you will be able to:
Identify the types of clients and how to invoke them. Register client nodes. Configure client access to the server. Control client access to the server. Set up client options. Use include-exclude to control client backup processing.
8-2
Unit 8: Client Configuration Client Interfaces
Lesson 1: Client Interfaces

Identify the Client Interfaces
Identify the Client Interfaces
Command Line Web Client Session Backup-Archive GUI
You can use the graphical user interface (GUI), the command line, or the Web client to perform tasks. More information on all these interfaces is available online and in the product manuals.
8-3
The Backup-Archive Command Line

The Backup-Archive Command Line
TSM server
>dsmc
backup-archive command line
Start the client command line at the operating system prompt. Your path may vary, but the default paths are as follows: Windows: Program Files > Tivoli > TSM > baclient AIX: /usr/tivoli/tsm/client/ba/bin Linux: /opt/tivoli/tsm/client/ba/bin
4
The client can be invoked by using the command line and typing dsmc at the system command prompt in the directory path where the client was installed. For example:
c:\Program Files\Tivoli\tsm\baclient dsmc
The client invokes a session with the server until the command is completed. The command dsmc can be followed by a keyword. For example, the dsmc incremental command is shown below:
dsmc i
When authentication is on, a password must be entered on the command line or the user will be prompted to enter a password. The password is encrypted and will not display when prompted. For Solaris, HU-UX and Linux, start the backup-archive client command line from:
/opt/tivoli/tsm/client/ba/bin
8-4
Using the Command-line Interface Loop

The dsmc loop command is another command-line interface option used to enter a series of Tivoli Storage Manager commands. The loop will invoke a server session until the quit command causes the session to drop. While in the loop you can enter as many commands as you like without preceding the command with the dsmc command-line interface prefix. Entering dsmc without a parameter will invoke the command-line interface loop.
Backup-Archive Command-line Syntax

Backup-Archive Command-line Syntax

Rules of command-line syntax are as follows:
When using the command line, the command syntax rules must be followed. All commands begin with dsmc (in lower case letters on some platforms). Options are always preceded with a dash (-), and often times followed by an equal sign (=) with a value assigned to the option. The file specification follows the rules of the platform. For example, a DOS file specification might read: C:\USER\MYFILE.DAT Wildcard metacharacters are also allowed. HELP is available on all commands using the help or ? command following the dsmc prefix.
8-5
The Web Client Interface

To use the Web client, specify the URL of the client machine running the Web client in your browser, and the client port 1581. For example: http://x.x.x.x:1581
The Web Client Interface
http://x.x.x.x:1581
The Web client runs on the following browsers:

Mozilla 1.4 or higher. Microsoft Internet Explorer 5.0 or later.
Browser must have JRE (Java Runtime Environment) 1.4.1 or higher.
Refer to the Backup-Archive Client Requirements section for the specific operating system levels supported for the Web clients. TCP/IP is the only communication protocol supported for this client interface.
8-6
The Backup-Archive GUI

The Backup-Archive GUI

The dsm command will start the GUI from the Windows command line. The dsmj command will start the Java GUI from a UNIX command line.
8-7
Utilities Menu Commands

Utilities Menu Commands

These functions are available to the client through the Utilities Menu of the Backup-Archive GUI:
Change Password Node Access List Access Another Node View Policy Information Delete Archive Data Delete Backup Data Delete Filespace Setup Wizard Preview Include-Exclude Query Diskinfo Create ASR Diskette
8
Change Password
A password is required when authorization is on. The change password function allows you to change your password at any time.
Node Access List

This option is used in conjunction with the access another node command. In this window, you are able to create or modify rules that will enable another node to access your file spaces backed up on a Tivoli Storage Manager server.
Access Another Node

One user can give another user access to their files on the Tivoli Storage Manager server by way of the Node Access List window. This window is found in the Tivoli Storage
8-8
Manager client GUI. Node access can also be granted with the set access command on the command line. The second user may use the Access Another Node window in the Tivoli Storage Manager client GUI. The FROMNODE option when used with the restore or retrieve command can return node objects from one client to another. The Access Another Node functionality is supported in the Tivoli Storage Manager Web client. This allows one node to restore objects backed up or archived from one node to another node with a Tivoli Storage Manager Web client agent.
View Policy Information

The View Policy Information window displays the management classes available to you. This information includes the copy group information for both the backup and archive copy groups.
Delete Archived Data

You can delete the entire archive package or individual files you no longer need stored on the Tivoli Storage Manager server. The administrator can override this option. This applies only if the object is not protected by data retention protection policies.
Delete Backup Data

You can delete individual backup copies from the Tivoli Storage Manager server without deleting the entire file space, if your administrator has given you authority. An example would be to delete files that were backed up, but were later found to contain viruses.
Delete Filespace
Use this utility if you do not need a file space. When you select the delete filespace command from the menu a delete confirmation request prompt displays. You can also remove a file space using the delete filespace command at the command line.
8-9
Setup Wizard
The client configuration wizard is accessible from here. The Setup Wizard will run you through all the steps necessary to configure the Tivoli Storage Manager client and Web client.
Preview Include-Exclude
The preview command allows you to view the objects to be backed up or archived according to the include-exclude list, prior to sending any data to the server.
Query DiskInfo Command

The query diskinfo command is available to the client through the Utilities Menu of the Web interface. The query diskinfo command allows users and administrators to get the LUNs and serial IDs of all disks accessible by the client machine without having to actually log on to the client machines. During Tivoli Storage Manager configuration for server-free data movement, the administrator must obtain the information for the disks that will used for storage. This is necessary to ensure that only one client node will be able to perform a server-free backup or restore operation for any given disk in the Storage Area Network (SAN).
Create ASR Diskette

You should create a recovery diskette any time there is a hardware configuration change or service pack update to your machine. Tivoli Storage Manager generates and backs up the required ASR files during system object (Windows XP) and system state (Windows 2003) backup. The ASR recovery diskette creation process will place the latest backup of these files on the diskette. You must have administrative authority to create a ASR diskette.
8-10
Unit 8: Client Configuration Administrative Control of Access
Lesson 2: Administrative Control of Access

Registration
Before a user can request Tivoli Storage Manager services, the node must be registered with the server.
Registration
Each node must be registered with the server and requires an option file with a pointer to the server. This can be done several ways. Register a node at the administrative command line with the following command:
register node nodename password userid=none
From the Administration Center: 1. Click Policy Domains and Client Nodes in Tivoli Storage Manager tree. 2. In the Servers table, click a server name. 3. In the policy domains notebook for the server, click a domain name. 4. In the properties portlet for domain, click Client Nodes . 5. In the table, click Select Action, select Create a Client Node. Client nodes can also be viewed and modified with the Administration Center.
Registration can be set to open or closed. Open means the client node is automatically registered when a session is started. The administrator does not have to register this node. Closed registration means the client node must be registered by the administrator.
8-11
Password Management
Password Management
When will my password expire? How many attempts do I have? How long must my password be?
Set password expiration

set PASSExp days node=nodename
Set invalid sign-on limit

set invalidpwlimit number of attempts
Set minimum password length

set minpwlength number of characters
10
Administrators have a variety of commands and options that can be used to limit and control access to the system.
Set Password Expiration

By default, the server sets a password expiration of 90 days. The expiration period begins when an administrator or client node is first registered to the server. If a user password is not changed within this period, the server prompts the user to change the password the next time the user tries to access the server.
set PASSExp 120 node=lab1 or set PASSExp 120 admin=testadmin
Set Invalid Sign-on Limit

By default, IBM Tivoli Storage Manager does not check the number of times a user attempts to log in with an invalid password. You can set a limit on consecutive invalid password attempts for all client nodes. When the limit is exceeded, the server locks the
8-12
node. The following example sets a system-wide limit of three consecutive invalid password attempts:
set invalidpwlimit 3
Set Minimum Password Length

By default, IBM Tivoli Storage Manager does not check the length of a password. The administrator can specify a minimum password length that is required for IBM Tivoli Storage Manager passwords. The following example shows how to set the minimum password length to eight characters:
set minpwlength 8
8-13
Prevent Client Nodes from Accessing the Server

Prevent Client Nodes from Accessing the Server
TSM Administrator
lock node nodename unlock node nodename
11
You can prevent a client node from accessing the system by using the lock node command. When you lock a node when it already has a session, the lock will not take effect until the system is restarted. You can reverse this by using the unlock node command. There are several reasons why a node might be locked. A node locks when there are too many invalid password attempts. An administrator may choose to lock a node to keep it from being included in an upcoming scheduled event.
8-14
Backup Operators Group

Backup Operators Group

Members of the backup operators group can override security restrictions for the sole purpose of backing up or restoring files. Storage administrators do not need to use an Administrator ID for purposes of backup and recovery. Backup operators are users or groups which have the back up and restore of files and directories security settings. Members of the backup operators group can backup and restore an entire machine, including system state and system services data. Supported on Windows 2003 and Vista Not supported on Windows 2000 or XP
12
8-15
Unit 8: Client Configuration Managing Client Options
Lesson 3: Managing Client Options

Managing Client Options

There are three ways to manage client options:
Text editor
Utilities menu in the backup-archive GUI
Server generated option sets
13
8-16
Configuring Client Options

Configuring Client Options

There are two files which retain client options, and whichever is used depends on the operating systems:
Windows
dsm.opt
UNIX
dsm.opt dsm.sys
14
On multi-user systems, like UNIX and Linux, the client options are in both files: dsm.opt and dsm.sys. The dsm.sys file contains the system-wide options, where dsm.opt is specific to the client. On other systems, like Windows 2003, the client options are in dsm.opt. This is a file that a client can edit, containing a default set of processing options that identify the server, communication method, backup and archive options, and scheduling options. When entering options in your client options file (dsm.opt), use these guidelines: Each comment must have an asterisk (*) as the first character in a line. Comments and options cannot be entered on the same line. Enter each option on a separate line and enter all parameters for an option on the same line. Enter one or more blank spaces between parameters. 8440 bytes is the maximum number of bytes for a file name and file path combined.
The file name itself cannot exceed 256 bytes. the path leading to the file cannot exceed 8184 bytes.
8-17
directory names (including the directory delimiter) within a path are limited to 256 bytes.
Remember, the Unicode representation of a character can occupy several bytes, so the maximum number of characters in a file name can vary. It is a good idea to indent options with spaces or tabs.
The server can manage client option sets, which is covered later in this unit.
Example of DSM.OPT
Example of DSM.OPT
15
8-18
Editing the Client Options File with the GUI

Editing the Client Options File with the GUI

Edit from the GUI
From the Utilities menu, select Setup Wizard. This will launch the Tivoli Storage Manager Client Configuration Wizard. On the first panel of the Tivoli Storage Manager Client Configuration Wizard, make sure Help me configure the TSM Backup Archive Client is selected.
Edit from the GUI graphical options editor Edit >> Preferences
16
Using the backup-archive GUI (more options available): Open the Edit menu and select Preferences. Make any necessary changes, and then click OK to save those changes.
Using the Setup Wizard (basic options only): Open the Utilities menu and select Setup Wizard. Select the Help me configure the TSM Backup Archive Client check box. Click the Next button. Select the Update my options file radio button.
8-19
Using the Graphical Options Editor

Changing the backup-archive client configuration files using a text editor is potentially an error-prone task.
Using the Graphical Options Editor

The graphical options editor appends options to the end of the option file. The graphical options editor updates the client configuration files DSM.OPT and DSM.SYS (UNIX and Linux clients only) if any options are changed. The client configuration files can still be updated using a text editor on the clients. The graphical options editor uses the Tivoli Storage Manager variables DSM_DIR and DSM_CONFIG to locate the client configuration file.
17
The graphical options editor will query the server for options that are stored centrally in client option set on the server. It is important to NOTE that the graphical options editor will only update or add client options to the options files on the client. Client option sets on the Tivoli Storage Manager server are not updated. The centrally stored options are displayed by the graphical options editor. Only client options that the backup-archive client is authorized to update can be changed with the graphical options editor.
8-20
Configure Client Access to the Server

Configure Client Access to the Server
communication method TCP port TCP server address node name
The following communication parameters must be set in the client options file: TCPPORT TCPServeraddress COMMMethod NODename
18
IBM Tivoli Storage Manager uses several communications parameters that must be set. These options are TCPPORT, TCPSERVERADDRESS, COMMMETHOD, and NODENAME. TCPPORT: Use the TCPPORT option to specify a TCP/IP port address of the server. The TCP/IP port address is used to communicate with a Tivoli Storage Manager server. The range of values is 1000 to 32767. The default is 1500.
TCPPORT port_address
TCPSERVERADDRESS: Use the TCPSERVERADDRESS option to specify the TCP/ IP address for a Tivoli Storage Manager server. To use the TCP/IP communication protocol, you must include the TCPSERVERADDRESS option in your client option file. The other TCP/IP options have default values which you can modify only if you want to change the default value. Provide a 1- to 64-character TCP/IP address for a Tivoli Storage Manager server. The value you specify for this parameter can be a TCP/IP Internet domain name or an IP address. COMMMETHOD: Use the COMMMETHOD option to specify the communication method you are using to provide connectivity for client-server communication. Some of the communication methods that can be used with the COMMMETHOD option include:
8-21
SHAREDMEM: The Shared Memory communication method. This communication method option is possible when the Tivoli Storage Manager Server and Tivoli Storage Manager Client are on the same machine. TCPIP: The Transmission Control Protocol/Internet Protocol (TCP/IP) version 4, communication method. NAMEDPIPE: The Named Pipe option specifies the name of a named pipe to use for communication between a Tivoli Storage Manager server and Tivoli Storage Manager client on the same Windows workstation. V6TCPIP: The Transmission Control Protocol/Internet Protocol (TCP/IP) version 6 communication method. This method is not supported for all functions, including NDMP, Windows Microsoft Management Console, and the Administration Center. Refer to the documentation for a complete list of functions which are not supported. TCPIP (version 4) and V6TCPIP (version 6) can be used in dedicated or intermixed environments.
Please refer to the Tivoli online documentation for a complete listing of communication methods. NODENAME: Use the NODENAME option to identify your workstation to the server. The nodename can be a 1- to 64-character name that will be used to identify the node for which you want to request Tivoli Storage Manager services. For Windows systems, the default is the name of the machine if you do not use this option. For UNIX, the default is the same as the name returned by the hostname command. The NODENAME option goes in your client system options file dsm.sys. For UNIX environments, dsm.opt is used.
8-22
PASSWORDACCESS GENERATE
Passwordaccess generate support is activated by specifying PASSWORDACCESS GENERATE in a client option file.
dsm.opt dsm.opt file file
19
The password of the IBM Tivoli Storage Manager backup-archive client is encrypted and stored in a file on the client system. If a client receives a return code from the IBM Tivoli Storage Manager server indicating that the password has expired, the client generates a new random password. The PASSWORDDIR backup-archive client option is used to specify the location of the encrypted password file. The Win32 backup-archive client is an exception to this rule as it stores the encrypted IBM Tivoli Storage Manager client password in the registry.
8-23
Additional Options
Additional Options
There are several groups of options. We will discuss some of them in detail. Here is a global overview of the groups: Communication options Node options Backup and archive processing options Restore and retrieve processing options Scheduling options Format and language options Command processing options Authorization options Error processing options Transaction processing options Web client options Diagnostics options
Some options are not available in the graphical options editor.
20
Identify Precedence of Options

If you have an option in both the central client option set and in the client option file (dsm.opt) the central client option set will override the client option file.
Override Configuration Options

An administrator at the server can override a subset of client options, for instance, scheduling mode. Options can be specified when invoking the command line or GUI client, which then overrides the options without having to make a change to the actual options file. The exception is the DOMAIN statement that is added to the client option file. When the options are changed, the client should be restarted.
8-24
The Domain Option

The Domain Option

If you do not specify local drives with the DOMAIN option in your client options file, the default is all local drives. When you use this option with the incremental command, it adds the local drives you specify to what is defined in your client options file. For example, if you enter: DOMAIN C: D: E: in the client option file and you enter: dsmc incremental domain=g: h: on the command line, IBM Tivoli Storage Manager performs an incremental backup for your c:, d:, e:, g:, and h: local drives.
(g: and h: are added by using domain)
To include all the local drives except for the e: drive enter the following command: dsmc incremental -domain=ALL-LOCAL -e:
21
This description applies generally to all platforms. Consider the term local drives to mean volumes or file systems if one of those terms applies to your platform. For more specific information about this option, see the appropriate IBM Tivoli Storage Manager BackupArchive Client Installation and Users Guide manual for your platform. Use the DOMAIN option to specify the drives you want to include in your client domain for incremental backup. When you use this option in your client option file, it defines your default client domain. The DOMAIN option is an additive option, so it will not override other options. IBM Tivoli Storage Manager uses your default client domain to determine which local drives to process during an incremental backup in the following situations: You run an incremental backup using the incremental command without specifying which local drives to process. Your IBM Tivoli Storage Manager administrator defines a schedule to run an incremental backup for you, but does not specify which local drives to process.
For UNIX clients, this option goes in the client user options file. ALL-LOCAL backs up all local hard drives, the systemobject domain (Windows 2000, XP), the systemstate domain (Windows Server 2003), and the systemservices domain (Windows Server 2003). This is the default.
8-25
All system services components are backed up as part of system state. You cannot back up individual system services components; however, individual components can be restored. You can exclude individual system services components. Place the exclude.systemservice (or exclude.systemobject for Windows XP) options in the client options file (dsm.opt). You can also set these options on the Include-Exclude tab, Define Include-Exclude Options section of the Preferences editor.
Domain for Backup: Client Configuration Wizard

Domain for Backup: Client Configuration Wizard
22
Using the IBM Tivoli Storage Manager Client Configuration Wizard, select the domains and type of backup from a list.
8-26
Unit 8: Client Configuration Client Performance and Options
Lesson 4: Client Performance and Options

Client Options Available to Configure and Improve Performance
Client Options Available to Configure and Improve Performance

file 1 file 4 file 6 file 5 transaction file 2
The TXNBYTELIMIT option specifies the number of kilobytes the client program buffers before it sends a transaction to the server.
file 3
Initial command line only option.

TSM server
Refer to the Performance Tuning Guide

23
There are some client options that are valid on the initial command line only. Many of these options establish the run-time environment, such as the COMMMETHOD and OPTFILE options. Options in this category are not valid in interactive, macro, or scheduler modes. They generate an error and cause processing to stop. Refer to the IBM Tioli Storage Manager Performance and Tuning Guide for more details.
8-27
Sever Option: TXNGROUPMAX

Server Option: TXNGROUPMAX
single transaction Maximum number of files
The TXNGROUPMAX option in the server options file indicates the maximum number of logical files (client files) that a client may send to the server in a single transaction.
Set the TXNGROUPMAX option in the dsmserv.opt file.

24
TXNGROUPMAX is the number of files that are transferred as a group between a client and the server between transaction commit points. It is possible to affect the performance of client backup, archive, restore, and retrieve operations by using a larger value for the TXNGROUPMAX option. You can use the TXNGROUPMAX option to increase performance when Tivoli Storage Manager writes to tape. This performance can be considerable when a user transfers multiple small files. Either set the TXNGROUPMAX option by editing the dsmserv.opt file on the server, or use the setopt command. The value range is 4 - 65,000. The default is 256 objects. For more tips on performance tuning, refer to the IBM Tivoli Storage Manager Performance and Tuning Guide.
8-28
Configuring Error Logging Options

Configuring Error Logging Options
dsmerror.log
day 1
pruning
dsmerror.log
day 2
dsmerror.log
Place these options in the client option file: errorlogname errorlogretention errorlogmax
dsmerror.log
day 3 day 4
dsmerror.log
Unless you specify QUIET, messages will display on your screen during Tivoli Storage Manager processes.
day 5
25
ERRORLOGNAME: Use the ERRORLOGNAME option to specify the path and name of the file where you want Tivoli Storage Manager to store information about errors that occur during processing. ERRORLOGRETENTION: Use the ERRORLOGRETENTION option to specify the number of days to keep entries in the error log, and whether to save the pruned entries. The error log is pruned when the first error is written to the log after a Tivoli Storage Manager session is started and after every schedule is run. If the only Tivoli Storage Manager session you run is the scheduler, and you run it 24 hours a day, the error log might not be pruned according to your expectations. You must stop the session and restart it to allow the log to be pruned when the next error is written. It is suggested that you set your log to be kept for 7 days. ERRORLOGMAX: The ERRORLOGMAX option specifies the maximum size of the error log, in megabytes. If you change from ERRORLOGMAX to ERRORLOGRETENTION, all existing log entries are retained and the log is pruned using the ERRORLOGRETENTION criteria. If you change from ERRORLOGRETENTION to ERRORLOGMAX, all records in the existing log are copied to the pruned log, the existing log is emptied, and logging begins under the new log-wrapping criteria. If you change the value of the ERRORLOGMAX option, the existing log is extended or shortened to accommodate the new size. If the value is reduced, the oldest entries are deleted to reduce the file to the new size.

8-29
QUIET: The QUIET option prevents messages from displaying on your screen during Tivoli Storage Manager processing. For example, when you run either the incremental or selective backup command, Tivoli Storage Manager displays information about each file it backs up. Use the QUIET option to reduce the number of entries you have to look through. When you use the QUIET option, certain error information still displays on your screen, and messages are written to log files. If you do not specify QUIET, Tivoli Storage Manager uses the default option, VERBOSE. It is suggested that you set this to QUIET.
DSMSCHED.LOG
DSMSCHED.LOG
When you run the schedule command as a service, output is directed to the dsmsched.log file, as well as the application event log. By default, the dsmsched.log file is in the current directory unless you change the path and file name using the SCHEDLOGNAME option. The amount of detail is determined by whether VERBOSE or QUIET is set in the dsm.opt file. After scheduled work is performed, check the schedule log for the following entry to verify that all work completed successfully:
Scheduled event eventname completed successfully.
26
To specify the number of days to keep log file entries in the schedule log, use the SCHEDLOGRETENTION option. This is covered in Unit 11.
8-30
Unit 8: Client Configuration Include-Exclude Processing Rules
Lesson 5: Include-Exclude Processing Rules

Include-Exclude Processing Rules
The list is read from the BOTTOM UP. 1
STOP (when you make a match). 2
If it is not EXCLUDED, it is INCLUDED. 3

27
8-31
Include-Exclude Processing Example

Include-Exclude Processing Example

C:\TSM\critproj1\my.doc (rule 3)
EXclude *.doc INclude c:\TSM\...\*.doc EXclude c:\TSM\critproj1\*.doc Does rule 3 match the file?
Yes
C:\TSM\critproj2\user.doc (rule 2)
Does rule 2 match the file?

D:\TSM\critproj1\form.txt (default)
Yes
Does rule 1 match the file? No include
Yes
E:\TSM\data\base.doc (rule 1)
exclude
28
Use the flowchart to determine whether a file will be included or excluded from processing according to the include-exclude rules provided. The include-exclude process is a bottom up process in that the last include-exclude statement is checked first. When the file matches the statement, exclude processing ends for that file. The include-exclude list is generated in the configuration options file. The exclude list in the options file can be overridden by the include-exclude options on the command. The graphic shows an example.
8-32
Exclude Directories from Backup

Exclude Directories from Backup

TSM
project2
project3
The Tivoli Storage Manager backuparchive client builds an internal traverse tree before performing a backup. The EXCLUDE.DIR statement excludes a directory structure from the traverse tree. It prevents directories and directory attributes from being backed up. If you use the following EXCLUDE.DIR statement: EXCLude.dir c:\TSM\project2\subdir1 What will happen to the costs file? What will happen to the plans file? What will happen to the dates file?
29
subdir1
subdir2
costs
plans
dates
EXCLUDE.DIR Statement
EXCLUDE.DIR Excludes a directory structure from backup and from being traversed during incremental backup. EXCLUDE.FILE Can be abbreviated to EXCLUDE and excludes files from backup. A directory is traversed even if all the files from that directory are excluded. If a directory structure is excluded using EXCLUDE.DIR, subdirectories in the excluded directory tree are not eligible for backup. Any INCLUDE statement that includes part of an excluded directory structure is ignored at backup time.
8-33
Backup of Excluded Directories

Even though a directory structure is excluded using the new EXCLUDE.DIR statement, subdirectories and files within the excluded directory structure can be explicitly backed up. The exclude statement goes in the client user option file (DSM.OPT) on single user Tivoli Storage Manager clients like Windows, and in the include-exclude file referred to by the client system option file (DSM.SYS) on multiuser operating systems like UNIX.
include /home/dir1/subdir2 exclude.dir /home/dir1 include /home/dir1/subdir1
In the previous example, the include statement for the /home/dir1/subdir1 and /home/ dir1/subdir2 directory is ignored when an incremental backup is performed. This is because the subdirectory has been excluded using an EXCLUDE.DIR statement.
dsmc> selective -subdir=yes /home/* dsmc> selective /home/dir1/subdir1/*
The first selective backup command backs up all files, except files in the excluded directory (home/dir1). This is because the EXCLUDE.DIR statement is honored for subdirectories. The second selective backup command backs up files in the /home/dir1/subdir1. This is an explicit backup of an excluded directory that overrides the EXCLUDE.DIR statement. What will happen to the costs file? (excluded) What will happen to the plans file? (included) What will happen to the dates file? (included)
8-34
Compression, Encryption, and Adaptive Subfile Backup Processing

Compression, Encryption, and Adaptive Subfile Backup Processing

Tivoli Storage Manager processes exclude.dir and other include-exclude statements first. Tivoli Storage Manager then considers: include.compression include.encrypt include.subfile For example, consider the following include-exclude list: exclude c:\lab\file.txt include.compression c:\lab\file.txt include.encrypt c:\lab\file.txt include.subfile c:\lab\file.txt Tivoli Storage Manager examines the exclude c:\lab\file.txt statement first and determines that c:\lab\file.txt is excluded from backup processing and is, therefore, not a candidate for compression, encryption, or adaptive subfile backup processing.
30
COPMPRESSION: The compression option compresses files before you send them to the server. ENCRYPTION: You can encrypt the data that is sent to the server during a backup or archive operation using standard encryption. ADAPTIVRE SUBFILE BACKUP: Allows you to perform a backup over a network device with limited bandwidth, such as a modem. An adaptive subfile backup sends only changed portions of a file to the server during successive backup operations instead of sending the entire file. If you want to include specific files or groups of files for compression, encryption, and adaptive subfile backup processing during a backup or archive operation, you must set the compression option to yes to enable processing for: the following actions Compression Encryption Adaptive subfile backup processing
8-35
Identify Files to Be Included or Excluded from Backup

Identify Files to Be Included or Excluded from Backup
TSM server
You can assign a management class for a file or file group by using an INCLUDE statement in your client options file. For example, to associate all the files in the costs directory with a management class named project, you would enter: Include c:\tsm\project2\costs\* project
31
The include-exclude list allows you to establish files that are to be included in or excluded from backup processing. The include statement is used for two purposes. One is to specify exceptions to the exclude list. The other is to associate a management class with a file or group of files. The include statement is also used during archive to determine the management class, while the exclude statement is not checked during the archive processing. Unless you have the EXCLUDE.DIR statement, directory type files are always included in the backup, even when all the files within the directory are excluded. The include-exclude list uses metacharacters to select files to be included or excluded. Some metacharacters differ depending on the client platform. These metacharacters allow you to specify wildcard processing. The metacharacters can also be used in the command line to specify the file specification on most commands.
8-36
Metacharacters
Character ? * \... /...
Function One and only one character matched as a wildcard Match any number of characters as a wildcard Windows: Match any directory UNIX: Match any directory
Example us?r.doc us*.doc \...\user.doc /.../user.doc
Some Examples of Metacharacters on Selected Platforms Objective Match one character Match n characters Match n directories Directory separator Open character class Character class range Close character class Literal escape Drive separator AIX ? * /... / [ ] \ none DOS ? * \... \ [ ] \ : HP ? * /... / [ ] \ : Win ? * \... \ [ ] \ : Mac ? * .... : [ ] \ : Lin ? * /... / [ ] \ : Sun ? * /... / [ ] \ :
8-37
Include-Exclude Wizard
Include-Exclude Wizard
The wizard helps users create an includeexclude statement that is intuitive and easy to use. The exclude wizard window opens for already included files. The include wizard window opens for excluded files. The files section is disabled for Directory objects. The Preview the include-exclude statement check box should be selected to view excluded files.
32
8-38
Include-Exclude Using the Backup-Archive Tree

Include-Exclude in the Backup-Archive Tree
Exclude Include
Excluded directories appear on the backup-archive tree with this icon:
33
You can include or exclude a file in the backup-archive tree, by selecting the file, then clicking the include or exclude button.
8-39
Include-Exclude Exercise
Include-Exclude Exercise
Domain: /usr/ /home/ 1. Exclude /home/admin/*.* 2. Exclude /home/nobody/.../* 3. Exclude /usr/lwp/* 4. Include /usr/lwp/resume.* STOP (when you make a match).
Included or Excluded? __________ /home/admin/bob.log __________ /home/admin/fileone __________ /home/nobody/data/file1.dat __________ /usr/lwp/resume.ibm __________ /usr/lwp/data/file1.dat
34
Determine if the files specified will be selected for backup based upon the include-exclude list provided. Remember, if it is not excluded, it is included.
8-40
Unit 8: Client Configuration Client Option Sets
Lesson 6: Client Option Sets

Client Option Sets

Client option sets can be centrally managed for multiple clients. When a client option set is created, you define a name for the option set, and can provide a description of the option set. For example: define cloptset prodbackup description=Backup options for Production.dept.
Option sets can be created with the Administration Center.
The client option set is empty when it is first defined.
Use client option sets to set options for groups of clients.

35
Perform the following steps to create a client option set and have the clients use the option set: 1. Create the client option set with the define cloptset command. The define cloptset command defines the option set name and description. The name can be up to 64 characters in length and should not include embedded blanks. The option set description can be up to 255 characters in length and should be enclosed in quotation marks if embedded blanks are used. To issue this command, the administrator needs to have system or unrestricted policy privilege. 2. Add client options to the option set with the define clientopt command. Once the option set has been defined to Tivoli Storage Manager, options and their values must be defined to the option set. This is done with the define clientopt command. The options set name, option name, and option value must be supplied. Optionally, either or both a sequence number and force value may be supplied.
8-41
3. Specify which clients should use the option set with the register node or update node command. Once a client option set and the client options have been defined, nodes may be associated with that set. This is done by using either the CLOPTSET option on the register node command for new nodes, or on the update node command for existing nodes. Clients can be attached to only one client option set, but client option sets can be used to centrally manage multiple clients.
8-42
Identify the Value of Client Option Sets

Identify the Value of Client Option Sets

first
prodbackup prodbackup client clientoption option set set patents
second
plans
backup-archive clients: Production department
TSM server The server automatically assigns sequence numbers to the specified options, or you can choose to specify the sequence number for order of processing. For example: define clientopt prodbackup inclexcl include d:/plans seqnumber=20 define clientopt prodbackup inclexcl include c:/patents seqnumber=10
36
Sequence numbers identify the order for processing. Client option sets allow the administrator to specify additional options that may not be included in the option file (dsm.opt) for the client. You can specify which clients use the option set with the register node or update node commands. The client can use these defined options during a backup, archive, restore, or retrieve process. The options defined in a client option set are a subset of the available client options. Options such as communication method are still stored on the client machine. To allow the administrator to control these options centrally, it is possible to specify that individual options cannot be overridden in the client machine.
Define Include-Exclude Options

Two of the options that may be defined to a client option set are INCLUDE and EXCLUDE. When these parameters are specified in client option files, an additional parameter for the management class to be used also may be provided.
8-43
Use Sequence Numbers in an Option Set
The options are processed starting with the highest sequence number. Any include-exclude statements in the server client option set have priority over the include-exclude statements in the local client option sets. The server include-exclude statements are always enforced and placed at the bottom of the include-exclude list and evaluated before the client includeexclude statements. If the server option set has several include-exclude statements, the statements are processed starting with the highest sequence number. The client can use the query inclexcl command to view the include-exclude statements in the order in which they are processed. query inclexcl also displays the source of each include-exclude statement. Use double-digit numbers like 10 and 20, so that you have more space between sequence numbers to add in new statements.
Use the FORCE Option

Use the FORCE Option
TSM administrator
TSM server
backup-archive clients: Production department
The FORCE parameter allows an administrator to specify whether a client node can override an option value. The default is NO. If FORCE=YES, the client cannot override the value. The following example shows how to prevent a client from performing a subfile backup: define clientopt prodbackup subfilebackup no force=yes
37
The sequence number assigned to a client option is used when the same option is defined more than once. Options such as INCLUDE may be defined to a client option set many times and the sequence is crucial. The FORCE option is used to specify options that cannot be overridden by the local option file for the client. To stop an option being overridden by the client, it should be defined to the option set with FORCE=YES. The default is NO.
8-44
Copy, Query, Delete, or Update a Client Option Set

Copy, Query, Delete, or Update a Client Option Set

COPY CLOPTSET prodbackup newcloptset QUERY CLOPTSET prodbackup DELETE CLOPTSET prodbackup UPDATE CLOPTSET prodbackup
The update command is used to change the description and sequence option. From the Administration Center: 1. Click Policy Domains and Client Nodes in Tivoli Storage Manager tree. 2. In the Servers table, click the name of a server. 3. In the policy domains notebook for the server, click the name of a domain. 4. In the properties portlet for the domain, click Option Sets. 5. In the table, select an option set. 6. Click Select Action, select Modify Option Set.
38
Client option sets can be copied, queried, deleted, or updated using the copy, query, delete, and update cloptset commands. Individual client options within an option set can be deleted using the delete clientopt command. The sequence number of a client option may be changed using the update clientopt command. It is also possible to create a file that has include-exclude statements, and you can point a client to that file. This is convenient when you want to create one set of statements and point multiple clients at it.
8-45
Create an Option Set with the Administration Center

Create an Option Set with the Administration Center
39
Client options sets are defined in the server database and are used by the clients that you designate. 1. Select Policy Domains and Client Nodes in the Tivoli Storage Manager tree. 2. Click the Domain Name with which you want to work. The Domain Properties are displayed. 3. Click the triangle next to Option Sets to expand it. 4. Select Create an Option Set.
8-46
Summary of Client Options
Summary of Client Options

Client options are a group of options that are set in the client options file. IBM Tivoli Storage Manager processes options in the following order:
1. Options defined on the server with server-enforced client options. The server overrides client values with FORCE=YES. 2. Options entered locally on the command line. 3. Options defined on the server for a schedule using the options parameters. 4. Options entered locally in the options file. 5. Options received from the server with client options not enforced by the server. The server does not override client values when FORCE=NO is used. 6. Default option values.
40
8-47
Unit 8: Client Configuration Delete Backup Files
Lesson 7: Delete Backup Files
Delete a Backup File

Files that have been backed up can be deleted by an authorized administrator. A client node that has been authorized can also delete backup data. Does not apply to files protected with IBM Tivoli Storage Manager for Data Retention.
Virus Scan Report: The GrindingHalt virus has been detected in Download_file.doc.
Download_file.doc
41
A good example of the reason a backed up file would need to be deleted is the removal of a file infected with a virus.
8-48
Unit 8: Client Configuration Delete Backup Files
Client Settings to Authorize Client Node Authority to Delete
Navigate to the client node and display properties.

42
Give the Client Node Authority to Delete
43
8-49
Unit 8: Client Configuration Encryption and Security
Lesson 8: Encryption and Security

Encryption
To ensure the security of the backed up data, the Tivoli Storage Manager client implements an encryption function, which allows for encrypting the data before sending it to the TSM server. Encryption helps secure backed up data during transmission. Once the data is stored on the Tivoli Storage Manager server, it is unreadable. The include.encrypt option is the only way to enable encryption on the client.
44
Encryption
Encryption enables the user to choose which files are subject to encryption with include-exclude processing. All files matching the pattern on the include.encrypt specification will be encrypted before the data is sent to the server. Encryption uses a very simple key management system, which means that the user either must remember the encryption key password during restore or store it locally on the client system. The encryption processing is the last task on the client system before the data is sent to the server; other client operations such as compression happen before encryption is done. Encryption works for backup as well as for archive.
8-50
Encryption Considerations
Encryption is CPU-intensive. Because of the nature of the encryption process, it adds a lot of additional computing requirements on the client CPU. You should decide very carefully which data items really need to be encrypted and control them using the include-exclude statements. The administrator has the option to overwrite client selections using client options sets.
Encryption and Archiving

Especially in the case of long-term archiving of data, problems can occur with the simple key management scheme. If data is archived using encryption, organizational rules have to ensure that the encryption key password remains available for retrieve. Cyclic password changes or no external password management can cause situations in which data cannot be retrieved successfully.
Encryption and Unattended Restores

When restoring data using the scheduling function, it is possible that files will not be restored because the needed encryption key password is not stored locally (PROMPT mode) or the restored files are encrypted with a different key than the stored encryption key password. No key, no data.
8-51
Encryption Key
Encryption Key
Place the encryptkey option in the client options file (dsm.opt or dsm.sys). There are three options for managing the key used to encrypt the files:
encryptkey save encryptkey prompt encryptkey generate
backup
archive
45
With the SAVE option, the encryption key password is saved in the Tivoli Storage Manager clients password file. A prompt is issued for the initial encryption key password. After the initial prompt, the encryption key password saved in the password file is used for backups and archives matching the include.encrypt specification. With the PROMPT option, you manage the encryption key password. You are prompted for the encryption key password when the Tivoli Storage Manager client begins a backup or archive operation. A prompt for the same key is issued when restoring or retrieving the encrypted file. With the GENERATE option, an encryption key password is dynamically generated when the Tivoli Storage Manager client begins a backup or archive. This generated key password is used for the backups of files matching the include.encrypt specification. The generated key password is kept on the Tivoli Storage Manager server in an encrypted form. The key password is returned to the Tivoli Storage Manager client for decryption during restore and retrieve operations.
8-52
Secure Sockets Layer (SSL)

Secure Sockets Layer (SSL)

Use Secure Sockets Layer to have another level of protection beyond passwords.
46
Secure Sockets Layer is the standard technology for creating encrypted connections between servers and clients. SSL provides secure communications for servers and clients over open communications paths, through the use of digital certificates. Refer to the IBM Tivoli Storage Manager Administrators Guide for your platform for information on configuring SSL.
8-53
Student Exercise
Student Exercise
47
8-54
Review Questions
1. The administrator defines a clientopt value in the central client option set. What is the default value for the FORCE option: yes or no? 2. True or False? There is more than one way to access and create or update a client option set. 3. True or False? The client include-exclude list is processed differently on different client platforms. 4. True or False? Before a user can request Tivoli Storage Manager services, the node must be registered with the server. 5. True or False? There is no default archive description. 6. True or False? The backup-archive client acts differently depending on the Tivoli Storage Manager server platform.
Review Answers
1. The administrator defines a clientopt value in the central client option set. What is the default value for the FORCE option: yes or no? no 2. True or False? There is more than one way to access and create or update a client option set. true 3. True or False? The client Include-Exclude list is processed differently on different client platforms. false 4. True or False? Before a user can request Tivoli Storage Manager services, the node must be registered with the server. true 5. True or False? There is no default archive description. false 6. True or False? The backup-archive client acts differently depending on the Tivoli Storage Manager server platform. false
8-56
Summary
Summary
Identify the types of clients and how to invoke them. Register client nodes. Configure client access to the server. Control client access to the server. Set up client options. Use include-exclude to control client backup processing.
48
8-57
8-58
9-1
Introduction
The backup-archive client communicates with the server and invokes the client functions of Tivoli Storage Manager. The backup-archive client is supported on a variety of platforms that might reside on a user workstation or a LAN server. This unit describes the various methods available to back up, restore, archive, and retrieve data, and what options are available to customize these processes to fit your needs.
Objectives
Objectives
Describe and compare the kinds of backups possible. Use the Tivoli Storage Manager Backup-Archive Graphical User Interface to back up and restore files from a client. Use the command line to back up and restore files from a client. Use the Tivoli Storage Manager Backup-Archive Graphical User Interface to archive and retrieve client files.
9-2
Unit 9: Backup-Archive Client Functions Types of Backups Available
Lesson 1: Types of Backups Available

Types of Backups
Types of Backups
Progressive or Incremental Backup Complete Date Only Without Journal Selective Backup (Always Backup) Journal-Based Backups Image Backup Logical Volume Backup Subfile Backup NAS File System Backup Backup Sets
IBM Tivoli Storage Manager uses by default the intelligent Progressive or Incremental backup strategy. Only files that have changed or that are new are backed up, reducing the amount of data transfer on your network and system. Progressive backup does away with the need to do resource intensive nightly full backups, and gives you faster restores because it only needs to restore the version of the file requested. Progressive backup needs to back up less data, thus saving network bandwidth, tapes, and management overhead. Selective backups are backups of files specified by the user. The files are backed up regardless of whether or not the file has changed. This is a full backup. Journal-based Windows backups improve performance of Incremental and Selective backups by utilizing the journal engine service to note the changed files, rather than file scanning.
9-3
Image backups are full volume backups for Windows clients, which uses the snapshot function of Tivoli Storage Manager. Logical volume backups are used to improve restoration performance. Periodically, the logical volume is backed up, before the scheduled daily incremental backups. If a logical volume needs to be restored, the logical volume backup is restored first, followed by the subsequent incrementals. With subfile backup, the Windows backup-archive client dynamically determines the most efficient approach for creating backup copies to improve backup performance over dial-up connections. Backups are either performed by changed bytes, changed blocks, or changed files. Network attached storage (NAS) filesystem backups are enabled through the support of Network Data Management Protocol (NDMP). Tivoli Storage Manager Windows, AIX, and Solaris servers can efficiently back up and restore network attached storage (NAS) file system images to automated tape drives or libraries that are attached to Network Appliance and EMC Celerra NAS file servers. NDMP support is available only on IBM Tivoli Storage Manager Extended Edition. Backup sets are portable, self-contained copies of backups, which can result in a rapid recovery without the TSM server or network availability. Backup sets are created by an administrator. Note: With UNIX symbolic links, only the path information that the symbolic link contains is backed up. For more information on logical volume, subfile, image and NAS filesystem backups, refer to your IBM Tivoli Storage Manager Administrators Guide.
9-4
Incremental (Complete) Backup

The incremental backup function, also known as incremental (complete), backs up all your files that have changed since they were last backed up and all your files that were created since the last backup. The incremental backup function does not back up files that are excluded by your include-exclude list.
Incremental by Date Backup

For a disk or volume to be eligible for incremental by date backups, you must have performed at least one full incremental backup of that entire disk or volume. Running an incremental backup of only a directory branch or individual file will not make the disk or volume eligible for incremental by date backups. To perform an incremental by date backup using the GUI, select the Incremental (date only) option from the type of backup pull-down menu or use the incrbydate option with the incremental command. The client backs up only those files whose modification date and time is later than the date and time of the last incremental backup of the file system on which the file resides. Files added by the client after the last incremental backup, but with a modification date earlier than the last incremental backup, are not backed up. Files that were renamed after the last incremental backup, but otherwise remain unchanged will not be backed up. Incremental by date however, will not check for frequency, new files, deleted files, changes in file attributes, or rebinding of files.
Incremental (without Journal) Backup

The process of running an incremental (without journal) backup proceeds as follows: 1. The client starts the session, and asks for the backup information. 2. There is a search in the TSM database for the information about the client files. 3. If there is no information, meaning there has never been a backup before, a full incremental backup will take place. 4. If there is information in the database, that information about which files have been changed is relayed, and then TSM performs an incremental backup.
9-5
Selective (Always Backup)

The selective backup always attempts to back up the objects you selected. Use a selective backup when you want to back up specific files or directories regardless of whether a current copy of those files exists on the server.
9-6
How Journal-Based Backups Work

How Journal-Based Backups Work

On clients with the journal engine service running, file and directory changes are recorded in a journal. This list of changes in the journal enables incremental backups to proceed without either querying the server or scanning the local file system. Journal-based backups are supported for Windows XP, and 2003 (32- and 64-bit) clients. The main difference between journal-based backup and incremental backup is how TSM creates the list of files to be backed up. In a progressive incremental backup the list of files is created by scanning the entire file system on the client and comparing that list with a list of files on the server. With journal-based backup, the TSM backup-archive client gets the list of backups by examining the entries created by the Journal Based Backup Daemon.
Journal-based backup is supported on all Windows clients. If you install the journal engine service and it is running, then by default the incremental command will automatically perform a journal-based backup on selected file systems that are being monitored by the journal engine service. IBM Tivoli Storage Manager does not use the journaling facility inherent in Windows NTFS file systems or any other journaled file system. In order to successfully perform a journal-based backup, several conditions must be met, which include: The journal service must be set up to monitor the file system that contains the files and directories being backed up. A full incremental backup has to have been run successfully at least once on the file system being backed up. The file space image of the file system at the server must not have been modified by an administrative command since the last full incremental backup.
The storage management policy for the files being backed up must not have been updated since the last full incremental backup.
9-7
File Level Backups

File Level Backups; Scenario

Apr. 4 Apr. 5
file modified Apr. 4 file modified Apr. 4
Apr. 6
file modified Apr. 4
Apr. 7
file modified Apr. 4 file modified Apr. 4 file modified Apr. 4
file modified Apr. 5
Comparison of File Level Backups

Apr. 4
Incremental complete; journaling Backed up Delete notify Incremental; no journaling Backed up Delete notify Incremental by date Backed up Delete notify Incremental mode=absolute Backed up Delete notify Selective Backed up Delete notify A,B,C A,B,C A,B,C,D B,C,D A,B,C
Apr. 5
C
Apr. 6
D
Apr. 7
D A D A D
A,B,C
A,B,C
A,B,C
A,B,C
A,B,C,D
B,C,D A
9-8
Unit 9: Backup-Archive Client Functions Overview of Backup Sets
Lesson 2: Overview of Backup Sets

Overview of Backup Sets

A backup set is a group of active versions of files, copied onto portable media. Backup sets can be restored on the client, locally, without the TSM server being available.
Backup sets must be generated by an administrator.
Although the creation of backup sets is not a client function, they are an important feature of backups. Using the most recent backup versions stored on the server, a Tivoli Storage Manager administrator can generate a complete set of client files (backup set). These backup sets can be used to retain a copy of client files for a longer period of time (Instant Archive) or for recovery of a client system, without server or network, when the backup set is copied onto portable media and restored locally (Rapid Recovery). The generate backupset command runs as a background process on the server. The restore backupset command restores a backup set from the server, a local file, or a local tape device.
Backup Set Considerations

Administrator generates backup set.
9-9
System, policy or owner authority required. Carefully consider the FORMAT parameter defined in the device class. Sequential media must be readable on the local drive of the client machine. Device class maps a tape device common with client. Unique description for easy management. Retention option to define the backup set expiration. Backup set volumes tracked in volume history file. Command line only for file level restore.
Additional Backup Set Commands

QUERY BACKUPSET UPDATE BACKUPSET DELETE BACKUPSET QUERY BACKUPSETCONTENT QUERY VOLHISTORY TYPE=BACKUPSET
Note: Backup sets can also be generated in the Administration Center.
9-10
Point-in-Time File Selection
Point-in-Time File Selection
Backup sets allow a point-in-time to be specified (default is TODAY, NOW). Files that were active at a specified date and time are included in backup sets. In-progress backups do not affect selection of files.
Backup sets cannot include deleted or expired files. Backup set date and time is PITDATE and PITTIME. If PITDATE is specified, the default PITTIME is midnight.
Data Type: File

When generating backup sets, the server will search for the active version of a file in an active-data pool associated with a FILE device class, if such a pool is available. The following search order is used: 1. 2. 3. 4. 5. An active-data pool associated with a FILE device class A random-access disk (DISK) storage pool A primary or copy storage pool associated with a FILE device class An active-data pool associated with onsite removable media (tape or optical) A mounted (idle) sequential-access volume from a primary, copy, or active-data pool 6. A sequential-access volume available in an automated library 7. A sequential-access volume available in a manual library All backup set commands add DATATYPE or WHEREDATATYPE parameter Data types cannot coexist; a given backup set has a specific data type Node name, backup set name, and data type are needed to uniquely identify a backup set.
9
9-11
Backup Set Table of Contents

Backup Set Table of Contents

Tables of contents (TOC) for backup sets are created as part of backup set generation. By default, when generating a backup set containing files and directories, the server will attempt to create a table of contents for a new backup set, but will not fail the backup set generation process if it cannot do so. You can, however, choose to require a table of contents by setting the TOC parameter to YES. When generating a backup set that contains API data or images, the server will require that a table of contents is generated. You cannot override this default. In either case, if a table of contents is required and the server cannot create it, the backup set generation process will fail.
10
Backup Set Table of Contents, continued

Tables of contents: Are stored on the server even if the media for the backup set has been moved offsite. Can be generated for existing backup sets that do not contain a table of contents. Can be re-generated when a backup set is defined on a new server, or if using a user-generated copy on a different medium. The GENERATE BACKUPSETTOC command allows a table of contents to be created for backup sets that do not have one. GENERATE BACKUPSETTOC may be used after a backup set is added to the server with the DEFINE BACKUPSET command or for backup sets that were generated by an earlier release of the Tivoli Storage Manager server.
11
9-12
Unit 9: Backup-Archive Client Functions Performing Client Backups
Lesson 3: Performing Client Backups

Using the TSM Backup-Archive GUI and Web Client to Back Up Files from a Client
Backup-Archive GUI; Backup
12
9-13
Select Files and Perform a Backup

Select Files and Perform a Backup
Click the Backup button. Select the type of backup.
4 3
Select the objects to back up.
Click the box to the left of the directory to select all files in a directory for backup.
Click the folder next to the directory to see the list of files selected for backup.
13
From the Windows system command line, type dsm to start the GUI. From a UNIX system command line, type dsmj to start the GUI. To access the Web client, use port 1581 and a supported Web browser. 1. Select Backup from the GUI main window. 2. Expand directory tree to see folders and files. 3. Select objects to back up. 4. Select the type of backup from Select Action menu: Incremental (complete) Incremental (date only) Always Backup Incremental (without journal)
5. Click Backup.
9-14
Take a moment to look over the backup-archive GUI directory tree. You will see that your local files, network files, RAW volumes, removable objects, and system objects are represented in the tree. The selection box next to a branch can have the following states: Not selected (empty) Partially selected (partially filled) Implicitly selected (filled) Fully selected (checked)
9-15
Review Backup Results

Review Backup Results
14
While the backup is running, this window will be displayed, which shows the progress of your backup. When it is finished, the window will show the results of the backup.
9-16
Use the Find Function

Use the Find Function
From the backup menu select Edit > Find and you get the screen shown. Fill in your criteria and click Search. You get a separate screen with files that fit your criteria.
15
Click the button at the top of the screen that looks like a flashlight or select Edit > Find to start the Find function. Notice the names of the files in the TSM directory. The Find function filters or searches for files stored locally on a client's disk or for files on the TSM server. Invoking the Find function starts a window to filter files or search for files matching certain criteria. The files matching the filter of find criteria can then be selected to perform a Tivoli Storage Manager action (back up, archive, retrieve, restore, or delete archive file). The Find Function is case sensitive.
9-17
Results of a Filter
Results of a Filter
04/21/2001 11/08/2004 04/21/2001 11/10/2004 04/21/2001 01/21/2005
Similar to the search function, the filter displays results as shown.
16
When you select names that start with the letter T and then click the Filter button instead of Find, the file names listed from the TSM directory will include just the file names that begin with the letter T. So, Find Files gives you another window from which you can select files, and Filter modifies the files displayed in the backup window.
9-18
Use the Estimate Function

The estimate function uses information gathered during previous backups (historical data) to estimate how long it will take for a backup to complete. If you have never backed up an item before, there will be no estimate information available. The estimation is calculated using the average transfer rate and average compression rate from previous operations. The estimate function calculates the number of bytes the currently selected objects occupy by scanning the selected directories or requesting file information from the TSM server. The historical data is stored on disk for the client. If the client connects to multiple servers, then it is recorded on a per server basis.
Select Always Backup as Type of Backup

Select Always Backup as Type of Backup
For a selective backup, choose Always backup from the menu.
17
Selecting files when performing a selective backup is the same as with the incremental back-up. The Find Files and Filter options can also be used with the selective backup just as with the incremental backup.
9-19
Using the GUI to Delete Backup Data
Using the GUI to Delete Backup Data
18
Select the Delete option from the menu. You can delete active objects, inactive objects, or all objects. Select a folder of files that have been previously backed up from the directory tree on the left. The items will appear in the right pane. In the right pane, select the backup object to be deleted, and click the Delete button.
9-20
Unit 9: Backup-Archive Client Functions Restoring Files
Lesson 4: Restoring Files

Restore Overview
Restore Overview
Restore is the process of copying a backup version of a file from the Tivoli Storage Manager server to the client system over the specified communication method.
Users must request to restore their own files. Users can restore the files of others as authorized. Tivoli Storage Manager server sends a copy of file to client, but the backup remains on the server. The user is able to restore backed up files to a specific point in time. Users can do restores through the GUI, client command line, or through a schedule. A user can restore files to a location other than where they were backed up.
19
If a file is damaged, the user (Tivoli Storage Manager client) can request that the system restore the current or a specific backup version without the aid of an administrator. A user may only restore files that he or she has backed up unless he or she has been granted authority to the backup files of another person. When a user restores a backup version of a file, Tivoli Storage Manager sends a copy of the file to the client node. The backup version remains in the Tivoli Storage Manager server. If more than one backup version exists, a user can restore the active backup version of the file or any inactive backup versions.
9-21
Restore Files Using the GUI

Backup-Archive GUI; Restore
20
The restore GUI queries the TSM server for a list of files that have been backed up and presents them in the same format as the backup GUI. Simply select the files you want to restore. You can also use the Find function to select files. The Find function gives you the same options as those for doing a backup but will look for backed up files on the TSM server from which to select for restoring.
9-22
Active and Inactive Version of a File to Restore

Active and Inactive Versions of a File to Restore

1
Before you select the file you want to restore: 1. Click View 2. Select Display active/inactive files. When you select the files you want to restore, you have a list of active and inactive files.
21
In order to restore a specific version of a file, you must select View and display. When the screen shown is presented, select Original location. The preserve path options are covered later in this unit.
9-23
Modify Restore Options

Modify Restore Options

1
1. Select a file to restore and click Options. 2. Select Replace from the menu, and click OK, and Restore.
22
The Modify restore and collision options panel offers several choices for your restore process. Choosing All selected files and directories recovers both files and directories. Choosing Files only recovers files only. Choosing Directories only recovers directories only.
You can also specify what actions to take on files that already exist. You can even specify how to restore for image by choosing image only, or image plus incremental directories and files. The options you specify are effective during the current client operation, but they are not saved for the next operation.
9-24
Point-in-Time Restore
Point-in-Time Restore
A Point-in-time Restore restores files to a past state that existed at a specific date and time, as opposed to the current state of the last backup. Options for GUI and command-line point-in-time restores:
File space, directory, or file level restore GUI window PITTIME hh:mm:ss PITDATE mm/dd/yyyy NLS enabled

Incremental backups notify of deleted files.
Frequency determines point-in-time resolution for deleted files Fault tolerant restore Restartable restore Backup retention period Number of backup versions kept
23
No query restore process used.

Policy definition considerations.

Tivoli Storage Manager uses a point-in-time (PIT) restore to restore a file space, directory, or file to the version equal to or before the point in time. Incremental backups are necessary to capture the fact that files have been deleted. Support for PIT restore is essential to be able to recover a file space or directory to a time when it was known to be in a good or consistent state. For example, a PIT restore can eliminate the effect of data corruption or recover a configuration to a prior date or time. When a PIT restore is performed, new files that have been created on the client after the PIT date are not deleted. Point-in-time restores that do include deleted files are possible when incremental backups are run on the client because the server is only notified about files that are deleted from a client file space during an incremental backup. Incremental backups should run frequently enough to provide the necessary point-in-time resolution. Files that have been deleted from a client file space between two incremental backups might be restored during a point-intime restore.
9-25
Backup Set GUI for Restore

Backup Set GUI for Restore
The first time you expand the Local folder to restore a backup set, this task box is displayed.
24
To find the volume name of the backup set, issue the following command:
q backupset f=d
9-26
Restartable Restores
Restartable Restores
Resumes at point of interruption New restore states Active Restartable Restarts on transaction boundary
Restore failure
Point of restart
Transparent to client No Query Restore process used

Transactions
Restore progress
25
If an error occurs in the middle of a restore, the user can start another restore specifying the same source and destination. If the restore is started within the restart period allowed, the restore will start from where it left off. If a restore is restarted, some files may be restored again depending on how much of the Tivoli Storage Manager transaction was complete when the error occurred. A restarted restore starts at a transaction boundary as defined by the TSM client and server options TXNGROUPMAX and TXNBYTELIMIT.
9-27
Restartable Restore Commands


query restore Lists restartable restores. Displays file specification, destination, nodename, and owner. restart restore Select from list of restartable restores. Restore continues from point of interruption. cancel restore
(administrative command)
Restart not performed when canceled by administrator. Client cannot restart the restore. Restart not performed when canceled by administrator. Client can restart the restore.
cancel sessions
(administrative command)
26
The backup archive GUI and command-line support restartable restores. The backup archive GUI contains a menu option to restart a restartable restore.The query restore command, reports active restores with the associated session number. Restartable restores are reported with negative session numbers, which makes them easier to identify. Query restore: Lists the active and restartable sessions. Restart restore: Restarts a restartable restore session. The user is presented a list of restartable restore sessions by number. Cancel restore: Cancels a restartable restore session and removes it from the list by asking the user which session to cancel.
9-28
Restore sessions can also be canceled in the normal manner by an administrator using the cancel session command. Doing this stops the session but leaves a restartable restore session. When a restartable restore session is canceled using the cancel session administrative command, the client node can restart the restartable restore session using the restart command. When a restartable restore session is canceled using the cancel restore administrative command, the client node cannot restart the session.
Cancel session
Cancel restore
To ensure a consistent restore, the client file space that is restored during a restartable restore is locked when a restartable restore is in running state. All Tivoli Storage Manager move operations for sequential media containing files from the node or file space are prevented. TSM client backups that affect data being restored are also prevented.
9-29
Restartable Restore Database Information

Restartable Restore Database Information

Server option RESTOREINTERVAL:
Defines how long a restore session can be restarted. Default 24 hours, maximum 1 week.
Restartable restores expire:

After a successful restore. When the following command is issued: CANCEL RESTORE When the TSM process RESTOREINTERVAL has passed. When a move operation is initiated, such as: Migration Reclaim Move data During expiration processing.
27
The server option, RESTOREINTERVAL, sets the length of time restartable restore sessions are held in the restartable state. Information regarding the status of the restore is kept in the Tivoli Storage Manager database. The default is to keep the restartable restore session information for 24 hours. RESTOREINTERVAL is defined in the server options file (DSMSERV.OPT) and can be changed dynamically. The restartable restore state is removed from the Tivoli Storage Manager database following a successful restore or when the restore is canceled by either the client or a Tivoli Storage Manager administrator. The restartable restore state is also removed by some TSM server processes after the RESTOREINTERVAL has elapsed. Server data movement operations such as migration, reclamation, and move data commands remove the restartable restore state from the Tivoli Storage Manager database when they run. The restore state is also removed during the expiration process. Expiration process is when files are identified for deletion because their expiration date or retention period has passed.
9-30
Unit 9: Backup-Archive Client Functions Backup and Restore with the Command Line
Lesson 5: Backup and Restore with the Command Line

Using the Backup-Archive Command Line
Using the Backup-Archive Command Line

dsmc
Change directories to the backup-archive client and type dsmc to start the command line. C:\Program Files\Tivoli\TSM\baclient>dsmc Or navigate to the backup-archive command line. Syntax for command line: dsmc action keyword option=value filespec
28
The backup-archive command line offers more options to back up and restore data. There is also more than one method to invoke the same command line. Options available to this command include: DOMAIN PASSWORD COMPRESSION QUIET/VERBOSE
For other options, refer to the IBM Tivoli Storage manager Administrators Guide for your platform.

9-31
All options on the command line override the options specified in the configuration options file, except the domain option which adds to the options file domain option. The file specification filename parameter is different than the -DOMAIN= option in that this parameter will override the domain option in the configuration options file.
Perform an incremental Backup on the Command Line

Perform an Incremental Backup on the Command Line
29
When you run an incremental backup on the command line, you see a breakdown of the results from start to finish.
9-32
Selective Backup Examples

Selective Backup Examples

To back up all the files in the d:\proj directory, use the following command:
dsmc sel d:\proj\*
To include all subdirectories for the same backup:
dsmc sel -subdir=yes d:\proj\*
30
The selective command backs up files that you specify. If these files become damaged or lost, you can replace them with backup versions from the server. When you run a selective backup, all the files are candidates for backup unless you exclude them from backup, or if they do not meet management class requirements for serialization.
9-33
Use the Query Filespace Command

Use the Query Filespace Command

Issue the command: Query FILESpace from the backup-archive client to see whether the Last Incr Date signifies that a recently performed incremental backup has completed successfully.
31
The query filespace command displays a list of file spaces in Tivoli Storage Manager storage. You can also specify a single file space name to query.
9-34
Delete Backup Command Syntax

Delete Backup Command Syntax

Windows:
To delete all files backed up from the d:\project directory with the extension of .txt, issue the following command:
delete backup d:\project\*.txt

To select files to delete, that were backed up from the d:\project directory, use the pick option:
delete backup -pick AIX:
d:\project\*.*
To delete all files backed up from the /usr/lab/project directory with a file extension of .txt, issue the following command:
delete backup "/usr/lab/project/*.txt"

To select files to delete, that were backed up from the /usr/lab/project directory, use the pick option:
delete backup pick /usr/lab/project/*"

32
Linux: To delete all files backed up from the /opt/lab/project directory with a file extension of .txt, issue the following command:
delete backup "/opt/lab/project/*.txt"
To select files to delete, that were backed up from the /opt/lab/project directory, issue the command with the pick option:
delete backup pick /opt/lab/project/*"
9-35
Restore Backed Up Files Using the dsmc restore Command

Restore Backed Up Files Using the dsmc restore Command

Restore the c:\projects\lab.ppt file to its original directory.
dsmc restore c:\projects\lab.ppt

If you do not specify a destination, the files are restored to their original location.
C:
data
temp
projects
lab.p
pt
tech.doc
tech.xls
33
The default restore method is the no query method, unless inactive, pick, latest, fromdate, and todate are specified, or it is a restore of NetWare NDS. To force the use of classic restore, use ?* in the source file specification rather than *. For example:
c:\projects\2007\?* or /home/projects/2007/?*
You can only use a single specification.
9-36
Use the dsmc restore Command with the PICK Option

The restore function allows you to restore files from the command line. The restore command is: Preceded by dsmc. Followed by options and a file specification of files to restore from the server.
Use the dsmc restore Command with the PICK Option

The PICK option creates a list of backup versions, images, or archive copies that match the file specification you enter. From the list, you can select the versions to process. Include the INACTIVE option to view both active and inactive objects.
dsmc restore -pick -inactive c:\data\*

C:
data
temp
projects
tech .doc
tech.xls
lab.ppt
34
Use the PICK option to list active and inactive backups stored on the server. It can be used to choose a backup version that is older than the most recent backup. Use the INACTIVE option to instruct Tivoli Storage Manager to restore an inactive backup if an active one is not available.
9-37
Using the dsmc restore Command with Overwrite

Using the dsmc restore Command with Overwrite

Restore all the files matching tech*.doc to their original locations, overwriting existing files.
dsmc restore replace=yes c:\data\tech*.doc
C:
data
temp
projects
tech .doc tech 2.do c
tech.doc
tech2.doc
tech.xls
lab.ppt
35
9-38
Use the LATEST Option with the dsmc restore Command

Use the LATEST Option with the dsmc restore Command

Use the LATEST option with the following commands to restore the most recent backup version of a file, even if the backup is inactive. restore restore group restore was Only active versions are considered for a restore unless you use either the INACTIVE or the LATEST option.
C:
dsmc restore latest c:\projects\*
data
temp
projects
tech.doc
tech.xls
lab.p pt lates versio t n
36
9-39
Restore to New Location Using PRESERVEPATH Restore Option

Restore to New Location Using PRESERVEPATH Restore Option

Restore preserving directory structure
Complete: restores complete path Partial: restores partial path None: does not preserve directory structure
The PRESERVEPATH restore option is available with the backup-archive command line. This option allows users to specify how directory structures are handled when performing restore to a new location. It creates the lowest-level source directory as a subdirectory of the target directory. Files from the source directory are stored in the new subdirectory. The PRESERVEPATH restore option can be specified with one of the following options: Partial or subtree: Creates the lowest-level source directory as a subdirectory of the target directory. Files from the source directory are stored in the new subdirectory. Subtree is the default. Complete: Restores the entire path, starting from the root, into the specified directory. The entire path includes all the directories except the file space name. Nobase: Restores the contents of the source directory without the lowest-level, or base directory, into the specified destination directory. None: Restores all selected source files to the target directory. No part of the source path at or above the source directory is reproduced at the target. If you specify subdir=yes, Tivoli Storage Manager restores all files in the source directories to the single target directory.
9-40
directories to restore
PRESERVEPATH command-line option

Complete, Partial (subtree), Nobase, or None The default is Partial
37
Use the IFNEWER with the dsmc restore Command

Use the IFNEWER Option with the dsmc restore Command

The IFNEWER option replaces an existing file with the latest backup version only if the backup version is newer than the existing file. dsmc restore ifnewer c:\data\tech.doc
C:
data
temp
projects
tech .do Jan. c 24 2008
tech.doc Jan. 22 2008
tech.xls
lab.ppt
38
Use the IFNEWER option to instruct Tivoli Storage Manager to replace an existing file with the backup if the backup is newer than the existing file.
9-41
Using the PITDATE and PITTIME Options

Using the PITDATE and PITTIME Options

Use the PITDATE option with the PITTIME option to establish a point in time for which you want to display or restore the latest version of your backups. If PITTIME is not specified, it defaults to 23:59:59. Restore the 9:00 AM Jan. 24, 2008 version of c:\data\tech.doc, replacing the current version. dsmc restore pitt=09:00:00 pitd=01/24/08 c:\data\tech.doc
C:
data
temp
projects
tech .do Jan. c 24 2008 09:00 am
tech.doc Jan. 26 2008
tech.xls
lab.ppt
39
The TODATE and TOTIME or FROMDATE and FROMTIME options specify a date and time range for restore processing. TODATE: Use the TODATE option to specify the latest date of files to be listed. TSM does not list files backed up after the specified date. Use this option with the FROMDATE option to list files backed up between the from date and the to date. TOTIME: Use the TOTIME and TODATE with FROMTIME and FROMDATE to request a list of files that were backed up within a window of time. You cannot use the no query method with the todate option.

The restartable restore can be performed from the command line as well. You can use the query restore command to find out if your client has any restartable restore sessions in the server database. Restartable restore sessions have a negative session number. Do not select a pittime during a backup window
9-42
Student Exercise, Part 1

40
Open your Student Exercises and perform the exercises for the preceding lessons.
9-43
Unit 9: Backup-Archive Client Functions Archive and Retrieve
Lesson 6: Archive and Retrieve

Overview of Archive and Retrieve
Overview of Archive and Retrieve

Archive creates a copy of specified files and stores them for a specified time.
Retrieve copies archived files from the storage pool to the client node for use. The retrieve operation does not affect the archive copy in the storage pool.
41
Archiving is used to preserve files for later use or for records. Archiving can be used to request Tivoli Storage Manager to copy files, subdirectories, and directories for long-term storage on media controlled by Tivoli Storage Manager. When users archive files, they can choose to have Tivoli Storage Manager erase the original files from their workstation after the files are archived. Do so with caution. Tivoli Storage Manager uses archive packages to identify groups of archived files. Tivoli Storage Manager retrieves the directories first, and then adds the files to the directories. Archived copies can be retrieved from the directory tree. Filters can be used to identify copies from the directory tree.

9-44
Authorized users can retrieve archive copies of files owned by someone else. For UNIX symbolic links, the file to which the symbolic link points can be archived, but under the name of the symbolic link.
9-45
Archive and Retrieve Using the GUI

Archive and Retrieve Using the GUI
This is the Archive and Retrieve section of the Tivoli Storage Manager GUI. Click the Archive button, and TSM will begin preparations for use.
42
The archive GUI presents a list of files in the same format as seen in the backup GUI. Select the files you want to archive and click the Archive button. You can also use the Find function to select files. The Find function gives you the same options as those for performing a backup.
9-46
First-time Archive Processes

First-time Archive Processes
43
The first time you select the Archive button on the main menu, these two messages will be displayed. For the first message click Yes, and for the second message, click OK. These messages will not appear again.
9-47
Archiving Files
You can archive multiple files, directories, or subdirectories together. Archiving is processed differently from backup in that a copy is stored on the server regardless of change status or frequency of backup. Files can be grouped by description for easy retrieval. Archives can trigger the deletion of the original file or can just make a copy of the original file. You can add a descriptive tag onto a file for easy retrieval. A separate copy group is used for archive and backup so that each management class can handle the differences between backup and archive.
Archiving Files
2007 lab s result
The archive function allows you to group important files by an associated description to archive and later retrieve.
44
9-48
Archive Descriptions
Archive descriptions are added to expedite the retrieval of files by ensuring the correct file is found. An archive description is a 255-character text field that identifies archived files and directories.
If you do not enter a description, Tivoli Storage Manager assigns the following default archive description: Archive Date: mm/dd/yyyy (where mm/dd/yyyy is the current date)
45
When files are archived using the backup-archive client, an archive description is required. The archive description is a 255-byte text field that can contain information relevant to the files and directories archived. TSM stores the archive descriptions in a new format internally in the TSM database. An initial conversion process occurs when you starts a GUI archive function. This conversion process can be long running if you own a large number of archived files. The conversion process can be canceled and restarted at a later time.
The archive description can be used to locate and identify files and directories without the knowledge of the physical client file spaces from which they were archived.
Unique Archive Descriptions

When the archive function is selected from the backup-archive GUI, a list of all previously used archive descriptions is displayed. The displayed archive descriptions can be used on subsequent archives.

9-49
Archive Packages
Archive Packages
Archived files with common description Archive or retrieve
Archive or retrieve complete package. Retrieve individual files in package. Add files to existing package. Delete files from package.
New package
Created using unique archive description. Default description
Archive Date: mm/dd/yyyy
Retrieve using the GUI client

Display archived files hierarchically. Grouped by archive descriptions.
46
An archive package is a set of files and directories archived with a common, unique archive description. All files archived require a description. Specifying a unique archive description creates a new package. Archive packages can be encrytped and use password management. Note: Remember, passwords may change for each archive and can potentially be required for up to 30 years.
9-50
Override Archive Options

Override Archive Options
Use the filter option to select files that match a pattern. 1. Select Delete files after Archive. 2. Click OK.
2
47
In the Archive Options window you can: Compress or compress always Have TSM delete the files from your workstation after they are successfully archived Choose to override the include list Select the management class you want for this file
V2 Archive (files only)

Select V2 Archive to archive only selected files without archiving the entire directory of the files (as in ADSM Version 2 archiving). The default action is for the entire directory of selected files to be archived unless you specify the V2 Archive option. In addition, if you select a directory to archive, all files and subdirectories in its path are archived. However, by clicking V2 Archive, any selected directory and its subdirectories are not archived, but only the files in its path.

9-51
The option you specify is effective during the current client operation, but it is not saved for the next operation. Select Override include-exclude list to override the management classes associated with objects using the include-exclude list.
How Retrieve Works

How Retrieve Works
When you retrieve a file, TSM sends a copy of the file to the client node. The archived file remains on the TSM server. Tivoli Storage Manager retrieves the directories first, then adds the files to the directories. Archive copies can be retrieved from the directory tree. Authorized users can retrieve archive copies of files owned by someone else.
48
9-52
Retrieving Files
Retrieving Files
The retrieve function allows you to copy an archived file from the storage pool back to your system.
49
9-53
Retrieve Using the GUI

Retrieve Using the GUI
2 1
Once you select Retrieve panel: from the main
1. Expand the tree to find archive files to retrieve. 2. Select the files. 3. Click the Retrieve button.
50
The retrieve GUI looks just like the restore GUI. Expand the directory tree where it shows client node name and observe the differences that archive packages introduced. The retrieve Find function works similarly to the restore Find function. You can select files based upon modified, accessed, or archived dates. If you click the set button on the Archived line you will be able to specify various options for archived dates.
Note: For more information on retrieve, see the appropriate reference manual for your platform. The retrieve window shows objects that you have previously archived to the server. You can use this window to select objects that you want to retrieve. You can also run an estimate for the retrieve or change processing options.
Retrieve Archive Packages Using the GUI Client

The retrieve GUI displays archived files hierarchically in a collapsible directory tree. The files are grouped by their archive descriptions. Expanding the collapsible description tree displays the individual directories and files of which the archive package consists.
9-54
Retrieve Options; Modify Retrieve and Collision Options

Retrieve Options; Modify Retrieve and Collision Options
51
The modify retrieve and collision options screen allows you to specify what objects to retrieve and what actions to take for files that already exist.
9-55
Unit 9: Backup-Archive Client Functions Archive and Retrieve Command Line
Lesson 7: Archive and Retrieve Command Line

Archive Using the Command Line

Archive all files in the c:\lab1\project directory with a file extension of .txt. dsmc archive c:\lab1\project\*.txt Archive the home/lab2/compl.doc file and assign a description to the archive. dsmc archive /home/lab2/2007/compl.doc description=Compliance standards for 2007
dsmc archive
52
The archive command archives a single file, selected files, or all files in a directory and its subdirectories on a TSM server. Directories are archived. You can archive files that you want to keep in their present condition. To release storage space on your workstation, delete files as you archive them. Retrieve the archived files to your workstation whenever you need them again.
The options available for Archive are: ARCHMC: Use the ARCHMC option to name the available management class in the active policy set of your policy domain. DELETEFILES: Use the DELETEFILES option to delete archived files from your workstation after they are stored on the server.
9-56
Unit 9: Backup-Archive Client Functions Archive and Retrieve Command Line
DESCRIPTION: Use the DESCRIPTION option to assign a description to a file when you archive it. If you do not remember the name of an archived file, you can use the DESCRIPTION option to retrieve the file. DIRSONLY: Use the DIRSONLY option to back up and restore only directories. FILESONLY: Use the FILESONLY option to back up and restore only files.
When you archive a symbolic link, TSM archives the file to which the symbolic link points. It does not archive path information for the directory. If you archive a symbolic link that points to a directory, TSM archives the files contained in the directory (and its subdirectories if the SUBDIR option is set to yes) under the name of the symbolic link. You can use the retrieve command to retrieve files.
Retrieve Using the Command Line

Retrieve the c:\lab1\projects\*.txt file to its original directory. dsmc retrieve c:\lab1\projects\*.txt Retrieve the /home/lab2/2004/compl.doc file under a new name and directory. dsmc retrieve /home/lab2/2007/compl.doc /home/lab2/2006/compl.doc description=Compliance standards for 2007
dsmc retrieve
53
Indicate the file you want to retrieve and a destination. If you do not indicate a destination, the files are retrieved to their original location.
9-57
Unit 9: Backup-Archive Client Functions Command Options for Backup, Archive, Restore, and Retrieve
Lesson 8: Command Options for Backup, Archive, Restore, and Retrieve

Command Options for Backup, Archive, Restore, and Retrieve

The following command options are available:
FROMTIME TODATE FROMDATE TOTIME FROMNODE FROMOWNER PICK VIRTUALNODENAME SUBDIR
54
FROMTIME: Use the FROMTIME option with the FROMDATE and TOTIME option to specify a beginning time or a window of time. TODATE: Use the TODATE option to specify the latest date of files to be listed. TSM does not list files backed up or archived after the specified date. Use this option with the FROMDATE option to list files backed up or archived between the from date and the to date. TOTIME: Use the TOTIME and TODATE with FROMTIME and FROMDATE to request a list of files that were backed up or archived within a window of time. For example, you could request files that were backed up or archived between 6:00 a.m. on June 1, 2002, and 11:59 p.m. on June 30, 2002. FROMNODE: Use the FROMNODE option to see a list of file space names on another node on whose behalf you can restore or retrieve files. FROMOWNER: Use the FROMOWNER option to specify an alternative owner from which to restore files. The owner must grant access to use the files.
9-58
PICK: Use the PICK option to display a list of backed up or archived files that match the file specification you enter. From the list, you can select the versions to restore. VIRTUALNODENAME: The VIRTUALNODENAME option specifies the node name of your workstation when you want to restore or retrieve files to a different workstation. SUBDIR: The SUBDIR option specifies whether you want to include subdirectories of named directories for processing on the following commands: archive delete archive delete backup incremental query archive query backup restore restore backupset retrieve selective
9-59
Backup, Archive, Restore, and Retrieve of Directories

The backup-archive client supports archiving and retrieving of directories. Directories with associated access control lists (ACL) or trustee rights are archived when the files are archived and are retrieved when the files are retrieved.
Backup, Archive, Restore, and Retrieve of Directories

Command-line options are provided to support archive and retrieve of directories.
DIRSONLY When this option is specified, only the directories and their attributes are archived or retrieved.
FILESONLY When this command-line option is specified, only the files and their attributes are archived or retrieved. The default is to archive or retrieve both directories and files.
55
Directories that are archived use the same archive description as the files with which they are archived.
9-60
Unit 9: Backup-Archive Client Functions The Types of backups
Lesson 9: The Types of backups

Image Backup Overview; Windows
Image Backup Overview; Windows

The Image Backup for Windows XP and Windows 2003:
Performs an online or offline image backup depending on the image type setting in your Include.Image statement in the Include-Exclude Preferences page or in the client options file. If the image type is set to Snapshot, then the client performs an online image backup. If the image type is set to Static, then the client performs an offline image backup. If there is no Include.Image statement or no image type setting, then the client defaults to performing an online image backup if the Logical Volume Snapshot Agent (LVSA) is installed. If the LVSA is not installed, then the client defaults to performing an offline image backup.
56
From your local workstation, you can back up one or more volumes as a single object (image backup) on your system. These volumes can be formatted FAT, FAT32, NTFS, or unformatted RAW volumes. If a volume is NTFS-formatted, only those blocks used by the file system will be backed up. You cannot restore single files from an image backup, only a full image restore. Image backup is visible only if the image plug-in is installed. Example of an option file entry for image backups: INCLUDE.IMAGE C: IMAGETYPE=SNAPSHOT SNAPSHOTFSIDLERETRIES=50 SNAPSHOTFSIDLEWAIT=1S,100MS SNAPSHOTCACHELOCATION=D:\: include.fs D: fileleveltype=dynamic DOMAIN.IMAGE C:
9-61
Windows Snapshot Image Backup

Windows Snapshot Image Backup

A nondisruptive, online backup for Windows clients, using the Tivoli Storage Manager snapshot function. This function allows a backup of an entire file system or raw volume as a single object. An image backup provides the following benefits: Faster backup and restore of file systems containing a large number of many small files. Conserves resources on the server during backups since only one entry is required for the image. Provides a point-in-time logical volume restore. Restores a file system or raw logical volume that has been corrupted. Provides a baseline for Disaster Recovery Management.
57
A snapshot image backup performs an online image backup of a volume in which the volume remains active and available for read and write operations during the backup. This function is available only if the Tivoli Storage Manager Logical Volume Snapshot Agent is installed and available. You cannot do an image backup of the system drive or the volume containing the snapshot cache. Put the snapshotproviderfs option in dsm.opt to enable snapshot-based file backup and archive operations, and to specify a snapshot provider. Use the snapshotproviderimage option to enable snapshot-based online image backup, and to specify a snapshot provider. Providers include Volume Shadowcopy Service (VSS) and Logical Volume Snapshot Agent (LVSA). VSS is not supported on Windows XP. If you use VSS, you do not need to install LVSA.
Open File Support with LVSA

The IBM Tivoli Storage Manager client for 32-bit and 64-bit Windows XP, and 2003 have the Logical Volume Snapshot Agent (LVSA) that allows a snapshot backup of files that are open (or locked) by other applications.

9-62
If you do not have the LVSA installed, Tivoli Storage Manager attempts to back up open files. Some files are open exclusively for the application that opened them. If Tivoli Storage Manager encounters such a file, it cannot read it for backup purposes. If you are aware of such file types in your environment, you should exclude them from backup to avoid seeing error messages in the log file.
Windows Incremental Image (Date Only) Backup

Windows Incremental Image (Date Only) Backup

Incremental Image (Date Only) Backup does the following: Performs an incremental-by-date of last image backup. Backs up files that have changed in your volume since your last image backup. Does not mark files inactive on the server for files that have been deleted from your client machine.
58
You can perform incremental-by-date of last image backup regardless of whether the full image was backed up using offline or online image backup. Use the image backup in combination with the regular incremental backups to make restore easier.
9-63
Logical Volume Image Backup: AIX

Logical Volume Image Backup Overview: AIX

AIX: Back up a logical volume as a single object (image backup) on your system. The traditional static image backup prevents write access to the volume by other system applications during the operation. Use the dynamicimage option to back up the volume as is without remounting it read-only.
Corruption of the backup may occur if applications write to the volume while the backup is in progress.
59
Options file entry:

include.image /<dir> dynamicimage=yes
Command-line syntax:
dynamicimage=<value>
Values: Yes: Use this option only if the volume cannot be unmounted and remounted as read-only. Tivoli Storage Manager backs up the volume as is without remounting it as read-only. Corruption of the backup can occur if applications write to the volume while the backup is in progress. In this case, run fsck after a restore and manually mount the file system in order to regain access to the volume. This option is valid for AIX, Solaris, HP-UX and all Linux clients. No: Use this option if you do not want to perform a dynamic image backup. This is the default. The default behavior depends on the platform and file system type. For platforms and file systems that support snapshot, namely AIX JFS2 file systems and LINUX LVM file systems, the default is snapshot-based image backup. For all other UNIX platforms and file systems, the default is static image backup.
9-64
Types of images: Dynamic: Specifies that you want to perform an image backup if the volume cannot be unmounted and remounted as read-only. Tivoli Storage Manager backs up the volume as is without remounting it as read-only. Static: Performs an image backup during which the volume is unmounted and remounted read-only. This is the default for AIX, HP-UX, and Solaris. Valid for AIX, Solaris, HP-UX, Linux86, Linux IA64, Linux pSeries, Linux iSeries, and Linux zSeries. Snapshot: Specifies that you want to perform a snapshot image backup during which the volume is available to other system applications. This is the default for file systems residing on a logical volume created by the Linux Logical Volume Manager. Valid for AIX 5.3 and greater JFS2 file systems, Linux86 and Linux IA64 clients only.
9-65
AIX and Linux Snapshot

AIX and Linux Snapshot

The snapshotproviderimage option enables snapshot-based image backup, and to specify a snapshot provider for AIX 5.3 and greater JFS2 and LINUX_LVM file systems. The snapshotproviderfs option enables snapshot-based file backup and archive operations, and to specify a snapshot provider for AIX 5.3 and greater JFS2 file systems.
You must be a root user to perform a snapshot-based file backup or archive operation.
For Linux86 and Linux IA64: By default, Tivoli Storage Manager performs a snapshot image backup of file systems residing on a logical volume created by the Linux Logical Volume Manager, during which the volume is available to other system applications.
60
Snapshotproviderimage and Snapshotproviderfs: Options file entry:

snapshotprovideri <value> include.image <dir> snapshotprovideri=<value> snapshotproviderfs <value> include.fs <dir> snapshotproviderfs=<value>
Command line syntax:

-snapshotprovideri=<value> -snapshotproviderfs=<value>
Values: JFS LINUX_LVM NONE
9-66
Subfile Backup
Subfile Backups
Backups
file on client day 1 day 2 day 3 day 4 backed up object base file delta file 1 delta file 2 delta file 3
Restore +
base file Delta file 3
=
restored file on client
61
backed up objects
Sometimes, if communication lines are slow or unreliable, you will want to send the minimal amount of data over the communication line. With the subfile backup feature you can back up only the changed portion of a file instead of transferring the whole file to the server every time. Only the changed portion of the file is backed up relative to the last complete backup of the file. A full backup is the base or reference file. The changed portion is called a delta file. All changes since the last complete backup of the file are included in this delta file. As you can see in the graphic, on the first day the file is created and backed up. On day two a change is made and only the changed portion is backed up. On the third day another change is made, so now the two changes are combined and backed up as one file. The same with the third day. All three changes are combined and saved as one delta file. In the case of a restore, this allows for the restore of the whole file by restoring only two subfile components, one delta file containing all three changes and the last complete backup of the base file. The adaptive subfile backup, as well as the restore of a base and delta file, is a background process. All necessary file data separations or reconstructions happen in the background on the backup-archive client. All other TSM features, such as policy management or faulttolerant backup and restore, still fully apply. Adaptive subfile backups can be used with incremental and selective backups and will work together with client data compression and encryption.
9-67
Subfile backup technology is not used for very small files (less than 1 KB in size) or for very large files (greater than 2 GB). If the delta file size exceeds 60 percent of the base file, a new base file will be transferred.
NAS File System Backup

NAS File System Backup

LAN/WAN (tcp/ip) control
backup-archive client NAS file server TSM server
data
62
When backing up NAS files systems, the Tivoli Storage Manager server uses Network Data Management Protocol, or NDMP, to connect to the NAS file server to initiate, to control, and to monitor a file system backup or restore operation. Since TSM is using NDMP on the NAS file server, the NAS file servers are essentially backup-ready. With this feature of TSM, you can back up to storage devices without moving the data over the LAN. The storage devices have to be under the direct control of the NAS file server, which means that they have to be directly attached or connected through a supported SAN environment. An NDMP backup is usually an image backup because the NAS filer performs the backup as an entity without telling TSM about the content. So the TSM server administers only one image object that has been backed up. Additionally, TSM can create a table of contents (TOC) during backup and store the TOC afterwards in a dedicated storage pool. The TOC enables TSM to restore a single file from a NAS backup image. Each time a single file restore from an NAS image backup is performed, IBM Tivoli Storage Manager will load the TOC from the dedicated storage pool into a temporary database table. You are able to
9-68
configure how long the TOC is stored in the temporary table. Even without the TOC you are able to restore single files from a NAS backup image. In that special case exact information about the single file and the image it resides in must be provided for restore. Although an NDMP backup is usually started and controlled by a TSM server, a TSM Web client is also able to initiate and control an NDMP backup or restore. NDMP support is available only on IBM Tivoli Storage Manager Extended Edition.
9-69

63
Open your Student Exercises and perform the exercises for the preceding lessons.
9-70
Review Questions
1. Which type of backup performs an online Windows 2000 image backup of a volume in which the volume remains active and available for read and write operations during the backup? 2. Use a(n) _______________ backup when you want to back up specific files or directories regardless of whether a current copy of those files exists on the server. 3. In order to successfully perform a journal-based backup, ____________ must be set up to monitor the file system that contains the files and directories being backed up. 4. Use the ____________ option on the command line with the dsmc restore command to list active and inactive backups stored on the server. This option is used to choose a backup version that is older than the most recent backup. 5. Use the ____________ option on the command line dsmc restore to instruct Tivoli Storage Manager to replace an existing file with the backup if the backup is newer than the existing file.
Review Answers
1. Which type of backup performs an online Windows 2000 image backup of a volume in which the volume remains active and available for read and write operations during the backup? Snapshot Image Backup 2. Use a(n) _______________ backup when you want to back up specific files or directories regardless of whether a current copy of those files exists on the server. Always (Selective) 3. In order to successfully perform a journal-based backup, ____________ must be set up to monitor the file system that contains the files and directories being backed up. the journal engine service 4. Use the ____________ option on the command line with the dsmc restore command to list active and inactive backups stored on the server. This option is used to choose a backup version that is older than the most recent backup. PICK 5. Use the ____________ option on the command line dsmc restore to instruct Tivoli Storage Manager to replace an existing file with the backup if the backup is newer than the existing file. IFNEWER
9-72
Summary
Summary
Describe and compare the kinds of backups possible. Use the Tivoli Storage Manager Backup-Archive Graphical User Interface to back up and restore files from a client. Use the command line to back up and restore files from a client. Use the Tivoli Storage Manager Backup-Archive Graphical User Interface to archive and retrieve client files.
64
9-73
9-74
10-1
Introduction
This unit covers backing up and recovering the Tivoli Storage Manager database, recovery log, and storage pools.
Objectives
Objectives
Back up the IBM Tivoli Storage Manager database. Recover the IBM Tivoli Storage Manager database. Back up the storage pools. Recover the storage pools.
10-2
Unit 10: Protecting the Database and Storage Pools Tivoli Storage Manager Database and Storage Pool Protection Requirements
Lesson 1: Tivoli Storage Manager Database and Storage Pool Protection Requirements
Tivoli Storage Manager Database and Storage Pool Protection Requirements

Have a copy of the Tivoli Storage Manager database for a sufficient number of days.
Number of days to retain copy depends on the business requirements. For example, a company with a five-day work week may want to keep copies for at least three days.
Have at least one copy of all storage pool data.

Consider having two copies. One copy is kept on-site; one copy is kept off-site. Active-data pools are good for on-site copies, if you want to restore current files only.
10-3
Tivoli Disaster Recovery Manager Functions

Tivoli Disaster Recovery Manager Functions
Creates Disaster Recovery Plan file Manages off-site media Maintains client information Centralizes the disaster recovery process Provides scripts to automate recovery Provides electronic vaulting of backups
Disaster Recovery Manager is a function within IBM Tivoli Storage Manager Extended Edition that assists you in preparing a disaster recovery plan. You can use the plan as a guide for disaster recovery and for auditing purposes to certify IBM Tivoli Storage Manager servers ability to recover. The following functions are provided: Generates a Disaster Recovery Plan file Handles off-site recovery media Maintains client recovery information in the IBM Tivoli Storage Manager server database Centralizes the management of the disaster recovery process Provides scripts to automate recovery Provides electronic vaulting of storage pool and database backups
IBM Tivoli Storage Manager Extended Edition must be installed and licensed before you can use IBM Tivoli Disaster Recovery Manager (DRM). Server-to-server communication, included in TSM Extended Edition, allows the use of a remote server for electronic vaulting.

10-4
The Disaster Recovery Plan File

The Disaster Recovery Plan File

Contact names and phone numbers Recovery procedures Database and storage pool information Hardware device information Contents of: Server options file Device configuration file Volume history file Scripts with commands
For more information on Disaster Recovery Manager, refer to the curriculum roadmap for scheduling and enrollment in: IBM Tivoli Storage Manager Extended Edition 5.5 Disaster Recovery
5
With DRM you can create a Disaster Recovery Plan file to help you restore your Tivoli Storage Manager server. After storage pool and database backups, the backup volumes and the Plan are sent off-site. Every time you run the prepare command, a new Recovery Plan file is created. This function has also been added to the Administration Center. The Recovery Plan file contains the following stanzas that make up the Plan: Instructions that you define (for example: contact names and telephone numbers) The recovery procedure A list of required database and storage pool backup volumes and their location Types of devices that are required to read the volumes Database and recovery log space requirements Copies of the server options file Device configuration and volume history information Commands for performing database recovery, primary storage pool recovery, and registering licenses Machine and recovery media information that you define

10-5
Using the Administration Center for Disaster Recovery Management


The table shows all of the servers that have been added to the Administration Center by the current administrator. For the servers that are licensed for IBM Tivoli Storage Manager Extended Edition, you can use the Disaster Recovery Manager function to automatically generate a disaster recovery plan and track media. Disaster Recovery Management actions
10-6
Unit 10: Protecting the Database and Storage Pools Backing Up the Database
Lesson 2: Backing Up the Database

Tivoli Storage Manager Database Backup
Types of Storage Manager Database Backup

Full backup + Incremental backups
Database out-of-band (snapshot) backup
Tivoli Storage Manager can perform full plus incremental backups of the database to tape while the server is running and available to clients. With the Tivoli Storage Manager recovery log in normal mode, the backup media can then be stored on-site or off-site and can be used to recover the database up to the point of the backup. You can run full or incremental backups as often as needed to ensure that the database can be restored to an acceptable point in time. You can provide even more complete protection if you specify that Tivoli Storage Manager run roll-forward mode. With Tivoli Storage Manager in roll-forward mode and with an intact recovery log, you can recover the database up to its most current status.
10-7
Full Backup Plus Incremental Backup

Full Database Backups

A full backup occurs when: Database has never been backed up. Maximum incremental backups reached. Database has been extended or reduced. Recovery log mode changed to roll-forward (default = normal).
For backups, an administrator can weigh the trade-offs between running full backups and running incremental backups. A full backup takes longer to run than an incremental because it copies the entire database. However, recovery time is faster with a full backup because only one set of volumes needs to be loaded to restore the entire database. A full backup is required under specific conditions, but an administrator can choose to run as many as 32 incremental backups between each full backup. An incremental backup takes less time to run because it copies only those database pages that have changed since the last time the database was backed up. However, incremental backups increase the time it takes to recover a database because a regular backup must be loaded first, followed by some or all of the incremental backups in the same database backup series.
10-8
Database (Snapshot) Backup

Database Snapshot Backup

A database snapshot backup:
Does not interrupt the normal backup series. Is integrated into Disaster Recovery Manager processing as well as volume history processing. Can be taken off-site. Full + incremental backup series stay on-site for availability.
A snapshot backup is a full backup that does not interrupt the full plus incremental backup series. It is also referred to as an out-of-band database backup. This backup can be stored off-site for disaster recovery purposes. A database snapshot backup is tracked by the volume history and can be used for a restore of the Tivoli Storage Manager database to the point in time when the snapshot was performed. A database snapshot backup does not empty the recovery log.
10-9
Database Backup Command

Database Backup Command

Backup DB DEVclass=devclassname Type=Incremental|Full|DBSnapshot VOLumenames=volname(s) Scratch=Yes|No Wait=Yes|No
10
Use the backup db command to back up the database.
Parameter
Description Specifies the name of the sequential access device class to use for the backup. Be sure that you have used the DEVCONFIG option in the DSMSERV.OPT file to specify an external file in which to store a backup copy of device class definitions. If you do not have this file and your Tivoli Storage Manager database is damaged or lost and must be restored, the definitions created by using the define devclass command will not be available and must be recreated manually. This parameter is required. Specifies the type of backup to run. This parameter is optional. The default value is INCREMENTAL. Specifies the volumes to use for the backup. You can specify more than one volume by separating each volume name with a comma, with no intervening spaces.
DEVCLASS=DEVCLASSNAME
TYPE=TYPEVALUE
VOLUMENAMES=VOLNAME
10-10
Parameter
SCRATCH=SCRATCHVALUE
Description Specifies whether scratch volumes can be used for the backup. This parameter is optional. The default value is YES. Specifies whether to wait for the server to complete processing this command in the foreground. The default value is NO. The first backup of your database must be a regular backup. You can run up to 32 incremental backups between regular backups. To perform a regular backup of your database to the TAPECLASS device class, for example, enter:
backup db type=full devclass=tapeclass
WAIT=WAITVALUE
In this example, Tivoli Storage Manager writes the backup data to scratch volumes. You can also specify volumes by name. After a regular backup, you can perform incremental backups, which copy only the changes to the database since the previous backup. Run an incremental backup of the database, using a scratch volume. Assume a device class of FILE for the backup:
backup db devclass=file type=incremental
10-11
Initiating a Database Backup

Initiating a Database Backup

Scheduling backups Backup db command Suggested way to do backups Specifying automatic backups Define dbbackuptrigger command Based on recovery log threshold Complements the scheduled backups Safety valve: ensures you do not run out of log space Only with roll-forward mode Running manual backups Can be initiated at any time
11
The Tivoli Storage Manager administrator can choose any combination of the following methods to back up the Tivoli Storage Manager database: Scheduled backups Backups based upon trigger levels Manual backups
10-12
DBBackuptrigger and Log Mode

By setting a database backup trigger you can reduce the likelihood that the recovery log will run out of space before the next backup.
DBBackuptrigger and Log Mode
The following commands are used to define the database backup trigger and log modes:
DEFine DBBackuptrigger DEVclass=devclassname LOGFullpct=percentage NUMINCremental=number
set logmode rollforward The database and log backup triggers, and setting the log mode can be managed with the Administration Center.
12
10-13
Define DBBackuptrigger Command Syntax
Parameter
Description Specifies the name of the sequential access device class to use for backups. This parameter is required. If the mount limit for the device class specified has already been reached (all drives are busy) when the backup runs, Tivoli Storage Manager automatically cancels lower priority operations, such as reclamation, to make a mount point available for the backup. Specifies the name of the sequential access device class to use for incremental backups. Specifies when Tivoli Storage Manager automatically backs up the database, based on the percentage of available space used for the recovery log. When the percentage of space used for the recovery log exceeds this value, Tivoli Storage Manager performs an automatic backup of the database and removes unnecessary records from the recovery log. Specifies the maximum number of incremental backups that can be run before a regular backup is required. You can specify a value from 0-32, where 0 specifies that Tivoli Storage Manager runs only regular backups automatically. This parameter is optional.
DEVCLASS=DEVCLASSNAME
INCRDEVCLASS
LOGFULLPCT=PERCENTAGE
NUMINCREMENTAL=NUMBER
Example
Define the setting of the database backup trigger at 80%. Run two incremental backups to every regular backup of the database. Assume a device class of FILE for the backup. Use the following command.
define dbbackuptrigger devclass=file logfullpct=80 numincremental=2
Run the query status command, and it will return the mode the recovery log is in.
10-14
SET LOGMODE
NORMAL
Description Specifies that Tivoli Storage Manager saves only those recovery log records that are needed to recover the database in case of a system failure. This is the default for the log mode. Specifies that Tivoli Storage Manager saves enough log records to ensure that the database can be restored to its most current state using the most recent database backup series and recovery log records.
ROLLFORWARD
10-15
Database Backup Related Commands

Database Backup Related Commands

Query DB Format=Detail
Pct. Util: xx% Max Pct. Util: xx% Incremental since last full: x Changed since last backup (MB) xxx Query VOLHistory Date/Time 01/24/2008 13:04:02 Volume Type: BACKUPFULL Backup Series: 3 Backup Operation: 0 Volume Seq: 1 Device Class: TESTBKDB Volume Name: D:\TSMSERVER\9326461.DDB DELete VOLHistory TODate=TODAY-7 Type=DBBACKUP
Volume history can be deleted with the Administration Center.

Tivoli Disaster Recovery Manager (DRM) can manage the volume history file. If you have implemented DRM, this step is not necessary.
13
Query DB
To help you determine how much storage space a regular or incremental backup will require, use the q db command. This command displays the number of changed megabytes in the database.
Query Volhistory
Use the q volh command to display sequential volume history information that has been collected by the server. Volume history information includes data such as date and time of use for the following types of volumes:
10-16
Volumes not in storage pools. Volumes used to back up a Tivoli Storage Manager database (regular or incremental). Volumes used to dump a Tivoli Storage Manager database.
Volumes used to export administrator, node, policy, or server data. Backup sets.
Query VOLHistory Type=typevalue
The TYPEVALUE specifies the type of records to display from the volume history file. This parameter is optional. The default is ALL. Possible values are:
Typevalue
ALL DBBACKUP
Description Specifies that all history information is displayed. Specifies to display only records that contain information about volumes used for backups (regular or incremental). Specifies a full backup that does not interrupt the current full plus incremental backup series. Also referred to as database out-of band or snapshot backup. Specifies to display only records that contain information about volumes used for online database dumps. Specifies to display only records that contain information about volumes used for exporting data.
DBSNAPSHOT
DBDUMP
EXPORT
Delete Volhistory
Use the delete volhistory command to delete sequential volume history information collected by the server when the information is no longer needed. For example, you may want to delete information about volumes used for obsolete database backups. When volume history information about volumes that are not in storage pools is deleted, the volumes return to scratch status if they were acquired by Tivoli Storage Manager as scratch volumes. For scratch volumes with device type FILE, the files are deleted. Do not delete sequential volume history information until you no longer need it. Do not delete the volume history information for database dump, database backup, or export volumes that reside in automated libraries unless you want to return the volumes to scratch status. When the delete volhistory command removes volume information for database dump, database backup, or export volumes, the volumes are automatically returned to scratch status if they reside in automated libraries. These volumes are then available for reuse by the server, and the information stored on them may be overwritten when the server reuses the volume for some other purpose, such as storage pool volumes or other database backups.
10-17
Unit 10: Protecting the Database and Storage Pools Database Recovery
Lesson 3: Database Recovery

TSM Database Recovery

The TSM database contains all information required to perform backup and restore functions.
= =
Restore
If you lose the TSM database, you can no longer restore files.
14
10-18
Restoring the Database

Restoring the Database

Tivoli Storage Manager provides three types of recovery, all initiated with the command: DSMSERV RESTORE DB
Point-in-time recovery Roll-forward to most recent state recovery Single database volume recovery
15
10-19
Roll-Forward Recovery
Roll-Forward Recovery
+ + + + +
1 full + up to 32 incremental database backups + roll-forward log

mirroring + roll-forward = comprehensive protection Benefits of a roll-forward recovery of the TSM database: Database can be restored to most recent state. Single database volume can be restored. No auditing of the database or storage pools is required after the restore. If the copy of the log is not available, you will need to audit the storage pools.
16
Roll-forward recovery to most recent state provides the ability to restore a database to its most current state if the recovery log is available. Mirroring and roll-forward recovery together provide the most comprehensive protection for a Tivoli Storage Manager database. Here are some considerations when enabling roll-forward recovery: Restoring the database to its most current state allows a site to protect against loss of client and server files due to a hardware failure on the Tivoli Storage Manager server. Since there is no requirement for auditing the database and storage pools after a database restore the recovery time is much faster. If there is a media failure on a database volume, only that volume needs to be restored, which reduces the time to recover the Tivoli Storage Manager database. The recovery log must be defined with a larger size because Tivoli Storage Manager must save additional recovery log records. The size of the recovery log depends on the frequency of required backups, how the database backup trigger is set, and the volume of Tivoli Storage Manager transactions. The maximum size of the recovery log is 13 GB. Mirrored copies of the recovery log consume additional disk space because of the larger recovery log size. However, it is still advisable to mirror your recovery log as well as the database, if you have enough disk space.
10-20
Point-in-Time Recovery
Point-in-Time Recovery
+ + + +
1 full + up to 32 incremental database backups in a database backup series.

Performing a point-in-time recovery of the TSM database: The recovery log is smaller. Database audit is not need after the restore. The most recent state cannot be restored. Single database volume cannot be restored. Auditing of storage pools is required after a database restore.
17
Point-in-time recovery is normally used for exceptional situations such as disaster recovery or removing the effects of software logic or other types of errors that can cause an inconsistency in the database. If an administrator enables roll-forward recovery, point-intime recovery is also available. For disaster recovery purposes, an administrator can run regular or incremental backups as often as necessary to ensure that a Tivoli Storage Manager database can be restored to an acceptable point in time and can send those backups to an off-site location for safekeeping. It is important to perform database backup with storage pool backup to provide disaster recovery services for the server. To restore a database to a specific point in time to remove the effects of an error that caused an inconsistency in a database, an administrator can use some or all of the backups contained in a database backup series. An administrator can also choose to enable point-in-time recovery only. The considerations of enabling point-in-time recovery only are: When only point-in-time recovery is enabled, the recovery log can be defined with a smaller size, and mirrored copies of the recovery log consume less disk space. Since there is no requirement for auditing the database after a database restore, the recovery time is much faster compared to the database salvage utility.
10-21
The database cannot be restored to its most current state. It can only be restored to the point in time when the particular backup series used to restore the database was created. Because restoring a single database volume requires roll-forward recovery, the entire database must be restored, even if only one volume is damaged. After the database has been restored, you have to audit the sequential storage pool volumes based on the information in the volume history file. You also must audit the disk storage pool volumes.
You will still need to mirror the recovery log, even if you use only point-in-time recovery. If the recovery log is gone, you will need to run the audit storagepool command.
10-22
Backing Up Volume and Device-Related Information

Backing Up Volume and Device-Related Information

backup volhist
volume history files
backup devconfig
device configuration files
18
Volume history information is automatically collected by the server for use in performing database recovery. The volume history information collected by the server is maintained in the Tivoli Storage Manager database. The Tivoli Storage Manager server collects the following types of volume history information: Volumes used to back up a Tivoli Storage Manager database. Volumes used to export administrator, node, policy, or server data. Sequential access storage pool volumes that have been reused, added, or deleted.
Use the backup volhistory command to request that the server save sequential volume history information to one or more files. Volume history information includes data such as date and time of use for the following types of volumes: Volumes used to back up a Tivoli Storage Manager database (regular or incremental). Volumes used to dump a Tivoli Storage Manager database. Volumes used to export administrator, node, policy, or server data. Sequential access volumes that have been added to storage pools.
10-23
Sequential access volumes that have been reused in storage pools reclamation or move data operations. Sequential access volumes that have been removed by using the del volume command or removed during reclamation of scratch volumes.
Device, drive, and library definitions are also stored in the Tivoli Storage Manager database. Device configuration information consists of device class definitions created using the define devclass command. On an AIX server, it also includes drive and library definitions created using the define drive and define library commands. Use the backup devconfig command to specify one or more files in which to store a backup copy of the device class definitions created using the define devclass command, library definitions created using the define library command, and drive definitions created using the define drive command.
10-24
Restoring the Server

Restoring the Server

You will need copies of these files and backups to restore your server
volhist.out dsmserv.opt devconfig.out
database backup storage pool backup
or you can use Tivoli Disaster Recovery Manager.

Use the dsmserv loadformat command to recreate the dsmserv.dsk file.
19
Keep current copies of these files off-site for safekeeping. Keep the output of the query system file off-site.
10-25
Database Restore Command Examples

Database Restore Command Examples

Restoring a database to its most current state: DSMSERV RESTORE DB PREVIEW=No|Yes Restoring a single database volume to its most current state: DSMSERV RESTORE DB DBVolume=volname PREVIEW=No|Yes Restoring a database to a specific point in time; history file available: DSMSERV RESTORE DB TODate=date TOTime=time Source=DBBackup|DBSnapshot PREVIEW=No|Yes
20
The dsmserv restore db utility uses backed up versions of the database either created manually with the backup db command or versions created with the automatically triggered database backups.
Restoring to a Specific Point in Time

If a backup copy of volume history information is available, you can restore a database to a specific point in time. TODate = date specifies the date to which to restore the database. This parameter is required. Possible values are: MM/DD/YYYY Specifies that you want to restore a database using the most recent backup series that was created prior to a specific date. TODAY Specifies that you want to restore a database using the most recent backup series that was created prior to the current date.
10-26
If the volume history file is unavailable, you can use one or more dsmserv restore db utilities to restore a Tivoli Storage Manager database to a specific point in time. For example, if you need to load a regular backup and one or more incremental backups, you can issue a dsmserv restore db command to restore the regular backup, and then issue an additional dsmserv restore db command for each incremental backup. When you use multiple dsmserv restore db utilities, you must specify COMMIT = NO for each command except the last one you issue. For the last dsmserv restore db command, you must specify COMMIT = YES to place the database in a consistent and usable state. If the volume history file is not available, you need to tell restore db which volumes to restore. VOLNAME: Specifies the names of one or more volumes to use to restore the database. You can specify more than one backup volume by separating each volume name with a comma, with no intervening spaces. You must list the volumes in the order in which the backup was stored. For example, if you want to use the backup volumes TAPE01, TAPE02, and TAPE03, specify the following volumes:
VOLUMENAMES=TAPE01,TAPE02,TAPE03
10-27
Best Practices
Best Practices
Use automatic backup triggers. Use space triggers. Use recovery log mirroring. Store backup of DEVCNFG.OUT, VOLHIST.OUT, and DSMSERV.OPT off-site. Complement with database mirroring for 24 x 7 environments (operate 24 hours a day, 7 days a week). Define volume history and device class backup files. Back up the database using administrator scheduling facility. Schedule database backup immediately following storage pool backup. Store backup volumes off-site. Use Disaster Recovery Manager to automate the recovery of the TSM database.
21
With the space management function, Tivoli Storage Manager is able to store active client data. In order to restore the database to the most recent state the roll-forward mode must be set. Using this mode, you are able to restore the database up to the last ended transaction. Use automatic backup triggers. By defining the database trigger you are protected from a situation that the database recovery log becomes full before the scheduled backup is run. If the automatic backup is run too often, you must adjust the size of the recovery log or change the percent of space used to trigger backup to run automatically. Use space trigger. Use the space trigger to increase the size of the database and recovery log by defining the percentage you will increase the database and recovery log, when a specified utilization percentage is reached. Use recovery log mirroring if you have enough space. The recovery log is vital for restoring to the most recent state. If you are using mirroring for recovery log, you are protected against media failure, and you can always restore to the most recent state even if one of the recovery logs suffers from a media failure.

10-28
Store backup volumes off-site. All backup volumes should be stored off-site to protect them from a disaster at the installation site.
Store backup of DSMSERV.OPT and DSMSERV.DSK off-site. Copies of the DSMSERV.OPT and DSMSERV.DSK files should be stored offsite to protect them from disaster recovery at the installation site.
Complement with database mirroring for environments that operate 24 hours a day. For those sites that are running operations 24 hours a day, the database mirroring feature is the only way to protect against a database media failure.
Define volume history and device class backup files. The volume history and device class backup files are used during database restore. If the volume history information is not available when doing point-in-time restore, you will not know which storage pool to audit. Consequently, you world need to audit all storage pools. If the device configuration is not available you have to define all device classes, drives, and libraries manually.
Back up database using the administrator scheduling facility. Schedule a regular backup once a week and an incremental backup once a day.
Schedule database backup immediately after the storage pool backup. If you are using the storage pool copy to take a backup of the primary storage pool, you should schedule the database backup to be run when the storage copy pool has been completed. If you do that, you will have a database backup that reflects the storage pool backup. If there is a disaster recovery situation, you can use the database backup and the storage copy pool backups to restore the Tivoli Storage Manager environment. These backups would restore the environment to the time backups were sent to an off-site location.
Consider using Disaster Recovery Manager. Refer to the Training Roadmap on the IBM Web site for information on IBM Tivoli Disaster Recovery Manager education.
10-29
Unit 10: Protecting the Database and Storage Pools Using Active Data-pools
Lesson 4: Using Active Data-pools

Active-data pools provide Tivoli Storage Manager administrators with the ability to seperate active and inactive data in the storage hierarchy. By having seperate active-data pools, you can have faster restores and more efficient storage pool utilization.
Active-data Pools
Copy storage pool: Copies of active or inactive data from primary storage pools for offsite storage. Active-data pools on disk: Copies of active data for fast restore of client data. Active-data pools on tape: Copies of active data to reduce the number of tapes stored offsite.
storage hierarchy with active and inactive data
22
Benefits of active-data pools on sequential-access disk (FILE):

Optimized access to active versions for fast restore Reduced size of disk pool if only active versions are stored Reduced data movement in preparation for restore of active data
Benefits of active-data pools on tape:

Reduced storage requirement (on-site or off-site) while protecting data against media failure or disaster Simplified tape management because of fewer tapes
10-30
Defining and Updating Active-data Pools

Defining and Updating Active-data Pools

To create an active-data pool, use the DEFINE STGPOOL command with the ACTIVEDATAPOOL parameter.
DEFine STGpool pool_name device_class_name POoltype=ACTIVEDATApool MAXSCRatch=####

To specify the name of an active-data pool where the server simultaneously writes data during a client backup operation, update the primary storage pool with the ACTIVEDATAPOOL option.
UPDate STGpool pool_name device_class_name ACTIVEDATApool=active-data_pool_name

Refer to the IBM Tivoli Storage Manager Administrators Reference Guide for all parameters and syntax.
You can also use the Administration Center to define active-data pools.
23
Define Storage Pool Command Syntax; Active Data

Required parameters: pool_name device_class_name POoltype=ACTIVEdata MAXSCRatch=number
24
10-31
Before Storing Data in an Active-data Pool

Before Storing Data in an Active-data Pool

Domains are used to filter which nodes can store data into an active-data pool. Before Tivoli Storage Manager writes data to an active-data pool, it verifies that the node owning the data is assigned to a domain that has the active-data pool defined in the ACTIVEDESTINATION parameter. To use an existing domain: Use the UPDATE DOMAIN command and specify the list of active-data pools in the ACTIVEDESTINATION parameter. To restrict which nodes can write to an active-data pool: Define a new domain and specify the list of active-data pools in the ACTIVEDESTINATION parameter. Update the node definitions to assign the nodes to the new domain. Complete the policy structure. Domains are covered in Unit 6.
25
Administrators must decide whether to copy and update an existing domain or establish a new policy in which the domain will authorize nodes to store data into an active-data pool.
10-32
Using the Administration Centers Create Storage Pool Wizard

Create Storage Pool Wizard; General Step
26
Create Storage Pool Wizard; Active-data Pool Step
27
10-33
Create Storage Pool Wizard, continued

Create Storage Pool Wizard; Active-data Pool (ADP) Domain Step
28
Create Storage Pool Wizard; Summary Panel
29
10-34
Policy Domain Wizard

Policy Domain Wizard
Policy Domains are covered in Unit 6.
30
Domain Wizard: Summary, Command Issued
The command used: UPDATE DOMAIN <user_domain_name> <other user parameters..> ACTIVEDEST=ADP1,ADP2
31
10-35
Unit 10: Protecting the Database and Storage Pools Storage Pool Backup and Recovery
Lesson 5: Storage Pool Backup and Recovery

Storage Pool Backup and Recovery

Storage pool backup and recovery:
Automatically switches to a duplicate copy if the primary file is damaged. Backs up without interruption of service. Restores one volume in a storage pool. restore volume Restores a complete storage pool. restore stgpool Supports disaster recovery. With incremental backups, have a copy storage pool for every primary storage pool.
32
Back up without interruption of services. The design allows incremental backups to be taken while the server is operational and available to clients. The administrator can decide which storage pools should be backed up, and then can also schedule these backups using the central scheduling feature of TSM. The storage pool backups can be run at a time convenient for the business.
Restore one volume in a storage pool. Restore individual volumes within a storage pool to recover from a media failure.
Restore a complete storage pool. Restore all damaged volumes within a storage pool to recover from a complete loss of a storage pool.
10-36
Support disaster recovery. Identify removable media volumes containing storage pool backup data to be sent to an off-site location for disaster recovery purposes. Provide management for the volumes that are stored off-site for disaster recovery protection. Address the issues of file expiration, volume reclamation, and volume rotation. Identify which volumes will return to the on-site location if you need to recover from a major disaster or from loss of a few volumes at the on-site location.
Automatically switch to a duplicate copy if the primary file is damaged. If you cannot obtain the primary file, the duplicate copy should automatically be used, if one is available.
10-37
Backup of Storage Pool Files

Backup of Storage Pool Files

Copy storage pool: Sequential only. Multiple primary pools can use one copy pool. Back up each primary storage pool hierarchy to same copy pool. Back up to copy pool: Is independent of client backups. Retains file level granularity. Is an incremental backup of files. Initiate backup: Manually with command or Administration Center. Automatically with administrative command scheduling. Once per primary pool. primary backup pool primary archive pool
copy pool
copy pool
33
Use the backup stgpool command to create backup copies of files that reside in a primary storage pool, and store the backup copies in a copy storage pool. If a file is already duplicated in the specified copy storage pool, a new copy of the file is not made in that copy pool. One primary pool can use multiple copy storage pools. You have many copy storage pools for each primary storage pool; you are not limited to two or three backup copies. Each copy pool requires additional database and storage pool space, a potentially important consideration. By supporting multiple copy storage pools, TSM supports both media and disaster recovery by physically separating these copies. This separation reduces the risk of losing data as a result of a disaster. You create multiple backup copies of a primary pool by initiating the backup of the primary storage pool for each copy pool. The incremental backup is performed for each copy storage pool. The files are copied only if they are not already in that copy or if the copy in the copy pool has a different insertion date (that is, the file has changed since it was last copied into the copy pool). The copy pool with all on-site volumes is used for media failure. Because all volumes are stored on-site, they may be destroyed if a disaster occurs.

10-38
You can use the copy pool with on-site volumes to provide a way to reduce the potential for data integrity loss due to media failure or other problems. If the primary file is not available or becomes corrupted, TSM will access and use a duplicate file from a copy storage pool. Disaster recovery is the reason for providing copy storage pools with off-site volumes. Off-site volumes in this disaster recovery copy storage pool are never automatically used by TSM. The volumes in this copy pool should be marked with the access mode of OFFSITE to make sure that TSM does not request a mount of the volume. The off-site volumes in the disaster recovery copy storage pool should be stored off-site with the database backup to make sure that you can recover the TSM environment if there is a disaster. You will get an error message when trying to access files from a copy storage pool that contains off-site volumes only. You can temporarily move the volume on-site and recover the files from volumes that belong to the disaster recovery storage pool.
10-39
Define a Copy Storage Pool

Define a Copy Storage Pool
on-site volumes
off-site volumes
DEFine STGpool poolname deviceclassname POoltype=Copy DESCription=description ACCess=READWrite|READOnly|UNAViable COLlocate=No|GRoup|NODe|Filespace REClaim=percent RECLAIMPRocess number RECLAMATIONType=THRESHold OFFSITERECLAIMLimit= NOLimit|number MAXSCRatch=number REUsedelay=0|days OVFLOcation=location DATAFormat=NATive|NONblock CRData=Yes|No
You can use the Administration Center to copy storage pools.

34
Define Stgpool
Use the define stgpool command to name a set of volumes as a primary storage pool or a copy storage pool. The volumes in a pool belong to the same device class. A copy storage pool is used to store backup copies of files that are in primary storage pools.
Define Stgpool Command Syntax
Parameter
POOLNAME
Description Specifies the name of the copy storage pool to be defined. This parameter is required. The maximum length of the name is 30 characters.
10-40
Parameter
Description Specifies the name of the sequential access device class to which this copy storage pool is assigned. This parameter is required. You can specify any device class except DISK. Specifies that you want to define a copy storage pool. This parameter is required. Specifies a description of the copy storage pool to be defined. This parameter is optional. The maximum length of the description is 255 characters. Specifies how users and system processes (like reclamation) can access files in the copy storage pool. This parameter is optional. The default value is READWRITE. Specifies whether TSM attempts to keep data belonging to a single client node or group of nodes assigned to as few volumes as possible. This parameter is optional. The default value is NO. Specifies when to initiate reclamation of fragmented space on volumes in the copy storage pool, based on the percentage of reclaimable space on a volume. Specifies the maximum number of scratch volumes that can be requested by TSM. This parameter is required.
DEVCLASSNAME
POOLTYPE=COPY
DESCRIPTION=DESCRIPTION
ACCESS=ACCESSMODE
COLLOCATE=COLLOCATION
RECLAIM=RECLAIMVALUE
MAXSCRATCH= MAXSCRATCHVALUE
For more options, refer to the IBM Tivoli Storage Manager Administrators Reference Guide for your platform.
Define Volume
Use the define volume command to assign a random or sequential access volume to be used for storage within an existing storage pool. You can define a volume to either a primary storage pool or a copy storage pool. You must define each volume to be used in a storage pool, unless you allow scratch volumes for the storage pool.
10-41
Backing Up the Storage Pool Hierarchy
Backing Up the Storage Pool Hierarchy
Backup STGpool primarypool copypool MAXPRocess=1 Preview=NO|YES|VOLumesonly

35
To back up files in a primary storage pool hierarchy to an on-site copy storage pool, issue the following commands:
backup stgpool primary_disk onsite backup stgpool primary_tape onsite
The number specified by MAXPROCESS does not limit the number of tape drives used.
10-42
Simultaneous Write to Multiple Copy Storage Pools

Simultaneous Write to Multiple Copy Storage Pools and Active-Data Pools

Simultaneous writes to primary pools and up to three copy pools and active-data pools take place during: Client backup, archive, and space-management operations. Server import operations.
copypool_1
storage hierarchy copypool_2 active-data pool_1

36
To allow for client data to be written simultaneously to multiple copy storage pools, the storage pool must contain a list of the additional copy storage pools (up to ten). Do not change the copy storage pool list in the storage pool hierarchy. If there is a different copy storage pool list, then all resources currently held are released in order to obtain the resources of the new copy storage pool list. Once the session has a storage pool that has a copy storage pool list, the operation session will continue to use the Simultaneous Write path. Target pools can have different device classes. There can be limited availability of mount points. Simultaneous writes should be used in conjunction with storage pool backup.
10-43
Using Simultaneous Write with Active-data Pools

Using Simultaneous Write with Active-Data Pools
Use the ACTIVEDATAPOOLS parameter for the DEFINE STGPOOL and UPDATE STGPOOL commands. This practice specifies the names of active-data pools where the server simultaneously writes data during a client backup operation.
37
Use the simultaneous write function to automatically copy client data to two copy storage pools, COPYPOOL1 and COPYPOOL2, and an active-data pool, ACTIVEDATAPOOL, during a backup operation. With DISKPOOL and TAPEPOOL already defined as your storage pool hierarchy, issue the following commands to enable simultaneous write:
define stgpool copypool1 mytapedevice pooltype=copy define stgpool copypool2 mytapedevice pooltype=copy define stgpool activedatapool mydiskdevice pooltype=activedata update stgpool diskpool copystgpools=copypool1,copypool2 activedatapools=activedatapool
Refer to the IBM Tivoli Storage Manager Administrative Guide for more information.
10-44
Setting up Simultaneous Write with the Administration Center

Setting up Simultaneous Write with the Administration Center

Modify Storage Pool Notebook
38
10-45
Handling Off-Site Volumes

Handling Off-Site Volumes
Set access mode to OFFSITE Use location No mount request UPDate Volume Volname ACCess=Offsite Location=Vault
39
You will need to change the status of the tapes that were used to perform the copy storage pool for off-site disaster recovery as not available to TSM. The status change is done with the update volume command specifying ACCESS = OFFSITE. TSM does not issue mount requests for off-site volumes. .
10-46
Update Volumes * Access=Offsite

UPDATE VOLUME * ACCESS=OFFSITE

Update each volume used during the backup one at a time, or use the following command to update all volumes used with one command. update volume * access=offsite location=Stone Mountain wherestgpool=offsite whereaccess=readwrite,readonly wherestatus=filling,full
Use the following command to create a list of volumes to send offsite. query media * stg=* wherestgpool=off-site whereaccess=readwrite,readonly wherestatus=filling,full
40
This process can be automated with Disaster Recovery Manager.
10-47
Reclamation of Off-Site Volumes

Reclamation of Off-Site Volumes

How?
.....
ON-Site
Softwa r e Packag ----- FRAGIL e E -----
I N S T A L L
C U S T O M I
file A
ite OFF-S
cal Point : Fo 011 From erver To: S
Reclamation 100%
file B
file A file B
file B
file A
Query VOLume UPDate VOLume

41
This sequence ensures that the files on the new copy storage pool volumes are sent off-site and are not inadvertently kept on-site because of reclamation.
10-48
Update Volume * Access=Readwrite

UPDATE VOLUME * ACCESS=READWRITE
To obtain a list of empty off-site volumes, issue the following command. query volume * access=offsite status=empty stg=OFF-SITE Bring the volumes identified above on-site and update their access to readwrite. update volume * access=readwrite location=Back Home wherestgpool=off-site whereaccess=offsite wherestatus=empty
42
The administrator periodically returns outdated backup database volumes. These volumes are displayed with the query volhistory command and can be released for reuse with the delete volhistory command. Consider scheduling this task.
10-49
Restoration of Storage Pool Files

Restoration of Storage Pool Files

copy pools
Restore damaged files.
Restore damaged volumes.
Restore damaged volumes within a storage pool.

43
File Level Backups TSM does storage pool backups on the file level to allow for recovery at different levels. Depending on the situation, you sometimes have to restore only files that have been damaged. In the event of a media failure, you can restore individual volumes, or you may have to restore multiple primary storage pool volumes because of a major failure. TSM supports recovery in all these situations.
Damaged Files A damaged file is one for which a data integrity error has been detected, such as when a client attempts to restore, retrieve, or recall the file or during an audit volume operation. If a data integrity error is detected for a file in either a primary or a copy storage pool, that copy of the file is marked as damaged in the database. If the same file is stored in other storage pools, the status of those file copies is not changed. File copies which have been marked as damaged are not:
Restored, retrieved, or recalled to clients Moved with migration, reclamation, or move data Restored during a restore stgpool or restore volume operation (if the backup copy in the copy storage pool is damaged)
10-50
To facilitate restore processing of entire volumes, DESTROYED volume access mode is introduced. If a volume has an access mode of DESTROYED, it is not mounted for either read or write access. The restore volume command recreates files that reside on a volume or volumes in the same primary storage pool. This command can be used to recreate files for one or more primary volumes that have been lost or physically damaged. When you issue the restore command against a storage pool volume, the volume will have an access mode of DESTROYED, and all files that have been backed up from this volume will be restored to the other volumes in that pool. Damaged Volumes within a Storage Pool The restore stgpool command restores files on any volumes that have been designated as DESTROYED using the update volume command. This command also restores all files in a storage pool that have previously been identified as having data integrity errors. The restore stgpool command is useful for restoring a large number of volumes (more than can be practically listed using a single restore volume command) after a major disaster, or for recreating damaged primary files. Support and Enhancements for Windows 2000 -RSM (Removable Storage Media) This service included with Windows 2000 facilitates communication among applications, robotic media changers, and media libraries. It enables multiple applications to share local robotic media libraries and tape or disk drives, and manage removable media with a single-server system.
10-51


Tivoli Storage Manager automatically accesses the copy storage pool file if the volume is on-site. Client requests access to file A. File A is marked damaged in the primary storage pool. The undamaged copy of file A in the on-site copy storage pool is accessed. The primary storage pool can be recreated from the on-site copy storage pool.
A B C D

A C D B C C D B C D
on-site copy storage pool
Run the following command periodically to restore damaged files:
restore stgpool <primary_pool>
preview=yes
44
TSM automatically accesses copy storage pool file if volume is on-site. Normally a file is obtained from the primary storage pool whenever an attempt is made to access that file. However, TSM will attempt to access the file from a copy storage pool if the primary copy of the file cannot be obtained because the primary file copy has been previously marked damaged. TSM will also use the duplicate copy if the primary file is stored on a volume which is UNAVAILABLE, DESTROYED, or OFFLINE. For certain operations (restore, retrieve, or recall of files to clients and export of file data), TSM will also access a file from a copy storage pool if the primary file is located in a storage pool that is UNAVAILABLE. If the file is stored on a volume with ACCESS=OFFSITE, the file will not be obtained from the copy pool. Instead an error message will be issued to the client.
Run restore stgpool periodically to restore damaged files. If a primary file copy is marked as damaged and a usable backup copy exists in a copy storage pool, the primary file can be recreated using the restore stgpool command. To recreate damaged files in the primary pool, you can define a schedule that executes the following command:
RESTORE STGPOOL primarypool
10-52
The restore stgpool command will restore all damaged files in the primary pool. If you are using off-site copy volumes only, these volumes must be brought onsite before you can issue the restore stgpool command. Otherwise, TSM will write an error message saying that the files on offline volumes cannot be restored. The restore stgpool command can be issued with a PREVIEW option to obtain a list of required copy storage pool volumes.
10-53
Maintaining the Integrity of Files

Maintaining the Integrity of Files

To maintain the data integrity of user files, you can: Detect damaged files before the users do using the restore storagepool command with the PREVIEW=YES option. Reset the damaged status of files if the error that caused the change to damaged status was temporary. Correct files that are marked as damaged. If you find and repair tape damage, run the audit volume command with the FIX=YES option. If you cannot repair the volume, change the volume access to destroyed with the command update volume ACCESS=DESTROYED.
RESTORE STORAGEPOOL <pool_name> PREVIEW=YES
45
Tape media can become unstable over time.
10-54
Recovering from a Media Loss

Recovering from a Media Loss

Use the command to restore a damaged volume in a primary pool. The command will restore volumes with an access mode of DESTROYED. Damaged files on other volumes in the primary pool are also restored. Files are restored to other volumes in the primary pool. Files remaining on the damaged volume after the restore can be analyzed for the cause of the damage. primary storage pool
vol_01 vol_02 vol_03
RESTORE VOLUME poolname

on-site copy storage pool
vol_02
vol_01
vol_03
46
In this scenario, an operator inadvertently destroys a tape volume (VOL2) belonging to the primary storage pool. An administrator performs the following actions to recover the data stored on the destroyed volume by using the on-site copy storage pool:
restore volume VOL2
This command sets the access mode of VOL2 to DESTROYED and attempts to restore all the files that were stored on VOL2. The files are not actually restored to VOL2, but to another volume in the primary storage pool. All references to the files on VOL2 are deleted from the database, and the volume itself is deleted from the database. The restoration of a volume may be incomplete. Use the query content command to get more information on the remaining files on volumes for which restoration was incomplete. The restoration may be incomplete for one or more of the following reasons: Files were either never backed up or the backup copies are marked as damaged. A copy storage pool was specified on the restore command, but files were backed up to a different copy storage pool. Volumes in the copy storage pool needed to perform the restore operation are offsite or unavailable.
10-55
If the query content VOL2 command showed files remaining, you would have to take some action. Analyze the cause for the situation. You may have to delete the volume with DISCARDDATA=YES to get the volume out of the storage pool.
DELETE VOLUME VOL2 DISCARDDATA=YES
10-56
Restore Volume Command

Use the restore volume command to restore all files that are currently stored on one or more volumes in the same primary storage pool and that were previously backed up to copy storage pools by using the backup stgpool command.
Restore Volume Command

vol_01
vol_02
vol_03
RESTORE VOLUME VOL_01 MAXP=2 on-site copy storage pool

vol_01 vol_02 vol_03
RESTORE Volume volname COPYstgpool=copypol NEWstgpool=newprimarypool MAXPRocess=numprocesses (1)Preview=No|Yes Wait=No|Yes

47
Restore Volume Command Parameters
Parameter
Description Specifies the name of the volume in a primary storage pool to which the files will be restored. This parameter is required. You can specify a list of volumes if all volumes in the list belong to the same primary storage pool. The items in the list are separated by commas with no intervening spaces.
VOLNAME
10-57
Parameter
Description Specifies the name of the copy storage pool from which the files are to be restored. This parameter is optional. If this parameter is not specified, files are restored from any copy pool in which copies can be located. Specifies the name of the new storage pool to which the files will be restored. This parameter is optional. If this parameter is not specified, files are restored to the primary storage pool to which the volume or volumes being restored belong. Specifies the maximum number of parallel processes that are used for restoring files. By using multiple, parallel processes, you may be able to improve throughput for the restore operation. This parameter is optional. You can specify a value from 1-999, inclusive. The default value is 1. Specifies whether you want to preview the restore operation without actually restoring data. This parameter is optional. The default value is NO. If you specify YES this option displays: The number of files and the number of bytes that will be restored. A list of copy storage pool volumes containing files that will be restored. These are volumes that must be mounted if you actually perform the restore. A list of any volumes containing files that are not restorable.
COPYSTGPOOL=COPYPOOL
NEWSTGPOOL= NEWPRIMARYPOOL
MAXPROCESS=NUMPROCESSES
PREVIEW=VALUE
WAIT=WAITVALUE
Specifies whether to wait for the server to complete processing this command in the foreground. This parameter is optional. The default value is NO.
10-58
Recovering Storage Pool Volumes

Perform the following tasks to recover storage pool volume. 1. Determine the copy pool volumes needed to restore. Determine the copy pool volumes that contain the backup copies of the files that were stored on the volume that was destroyed by entering:
RESTORE VOLUME volumename(s) preview=yes
2. Set the access mode of the copy volumes to UNAVAILABLE. Set the access mode of the damaged volumes identified as UNAVAILABLE to prevent reclamation by entering:
UPDATE VOLUME volumename(s) access=unavailable
3. Bring the identified volumes to the on-site location. Bring the identified volumes to the on-site location and set their access mode to READONLY by entering:
UPDATE VOLUME volumename(s) access=readonly
4. Restore the destroyed files. Restore the destroyed files by entering:

RESTORE VOLUME volumename(s)
5. Set the access mode of the volumes to OFFSITE. Set the access mode of the copy pool volumes to OFFSITE by entering:
UPDATE VOLUME volumename(s) access=offsite
6. Return the volumes to the off-site location.
10-59
Restore Storage Pool Command

Restore Storage Pool Command

A C D B C C D B C D
RESTORE STG PRIMARY on-site copy storage pool

A B C D
UPDATE Volume volname ACCESS=destroyed RESTORE STGpool primarypool NEWstgpool=newprimarypool MAXPRocess=numprocesses Preview=No|Yes Wait=No|Yes
48
Use the restore stgpool command to restore files from one or more copy storage pools to a primary storage pool. The files must have been copied to the copy storage pools by using the backup stgpool command. When you use this command, TSM restores all files that belong to the specified primary storage pool and that meet one of the following criteria: The primary copy of the file has been identified as having data integrity errors during a previous operation. The primary copy of the file resides on a volume that has an access mode of DESTROYED.
After the files are restored, the old references to these files in the primary storage pool are deleted from the database. TSM now locates these files on the volumes to which they were restored rather than on the volumes on which they were previously stored. If a destroyed volume becomes empty because all files have been restored to other locations, the destroyed volume is automatically deleted from the database.
10-60
Backup and Recovery Best Practices

Backup and Recovery Best Practices

Here are some suggestions for applying storage pool backup functions to your environment:
Back up each primary storage pool hierarchy to the same copy pool. Consider using at least one copy pool for on-site recovery and one for disaster recovery. Use administrative command scheduling to automate storage pool backups. Save the volume history (VOLHIST.out), device configuration file (DEVCNFG.out), and output of the query system command. Send offsite along with DSMSERV.OPT .
Use the Administration Center to create a script for the following tasks: Back up the primary storage pools and database. Create a Recovery Plan File if using Disaster Recovery Manager.
49
Back up entire primary storage pool hierarchy to the same copy pool. TSM is smart enough to recognize that when a file migrates down the storage hierarchy, it does not need to be copied again into a copy pool. Or, if you move a file with the move data command, TSM can recognize this situation. Migration works if you have set up your configuration so that each primary storage pool hierarchy is copied to the same copy pool.
Consider using at least one copy pool for on-site recovery and one for disaster recovery. It is useful to have one backup copy of a primary pool that is kept on-site to be used for media failures or damaged files. Remember that if you access a file that is damaged in the primary storage pool, TSM will automatically let you access the copy in the copy pool, if the copy pool volumes are on-site. To be prepared for disaster situations, have one backup copy of a primary pool that is used for off-site storage. The primary pool is copied to on-site volumes in this special disaster recovery copy pool, and then the administrator can change the volume access mode to OFFSITE and physically move the volumes to an off-site location.
Use administrative command scheduling to automate storage pool backups.

10-61
The administrative command scheduling facility can be used to automate storage pool backups. The backup stgpool command can be scheduled to initiate at regular intervals. Back up the storage pool first. Back up the storage pools first. By backing up storage pools first, you ensure that all storage pool files are recorded in the database. You may end up with extra records in the database, but at least there should be a record for each file in the storage pools. Also, since the storage pool backups may take longer than the database backup, the storage pools should be backed up first to further reduce the inconsistencies between the database and the storage pools. Back up the database and storage pool together. To prepare for server disaster recovery, both the server database and storage pools should be backed up at the same time. In this way, the database and storage pools will match (be in sync) to a greater degree. Save the volume history and device configuration file. To ensure the integrity of the storage pool data, save the volume history and device configuration files and send them off-site. Use Disaster Recovery Manager.
10-62
Protecting Your Database and Storage Pool

Protecting Your Database and Storage Pool

To protect your storage pools: Create a copy storage pool. Do a backup of the primary storage pools to the copy storage pool.
Things to do today
Daily tasks: Back up primary storage pools to copy storage pools. Back up the database. Save the volume history file, the device configuration file, and the output of the query system command. Move storage pool volumes, database backup, volume history file, and the device configuration file off-site.
50
REUSEDELAY
You should delay the reuse of any reclaimed volumes in copy storage pools for as long as you keep your oldest database backup. Delaying reuse may help you to recover data under certain conditions during recovery from a disaster. When you define or update a sequential access storage pool, you can use the REUSEDELAY parameter. This parameter specifies the number of days that must elapse before a volume can be reused or returned to scratch status after all files have expired, deleted, or moved from the volume. If REUSEDELAY is set to 0, you run the risk of data loss.
10-63
Daily Administration Cycle

Daily Administration Cycle

incremental backups of client data
back up first stgpool back up next stgpool back up TSM database back up devconfig/volhist migration eject off-site volumes and insert scratch volumes expiration processing clients hours of operations 08:00 18:00
51
reclamation processing
This is one example of the daily operations of an IBM Tivoli Storage Manager administrator. Fortunately, the administrator for this company has automated these functions with maintenance plans and scheduled administrative scripts.
10-64
Unit 10: Protecting the Database and Storage Pools Tivoli Storage Manager Maintenance Plans
Lesson 6: Tivoli Storage Manager Maintenance Plans

Tivoli Storage Manager Maintenance Plans

Processes can be scripted to: Back up the primary storage pools. Back up the server database. Update a basic disaster recovery plan. Migrate stored data from primary storage pools to the next level storage pools. Remove expired data from server storage. Reclaim fragmented tapes by consolidating active data.
Use the Administration Center to create a separate script for each TSM server in your environment.
52
The Tivoli Storage Manager maintenance plans use a Web interface wizard to build scripted plans. Here are some benefits of the maintenance plans: Generate a custom maintenance plan for each server. Expand the maintenance plan as the server environment changes. Provide a schedule for the maintenance plan to run daily. Allow the maintenance plan to be viewed and edited by the administrator.
10-65
How to Set Up a Maintenance Plan
How to Begin
Select Server Maintenance in the Tivoli Storage Manager tree, and the Server Maintenance page will display as shown.
53
Selecting the Specific Server and Task
Select the server you want to make the script for, and from the Select Action menu select Create maintenance script. The options to modify and to remove a script are also available from the same menu.
54
10-66
Server Maintenance
The Server Maintenance wizard appears. Click Next.
55
Selecting a Device
The left side of the screen shows the sequence of processes that will be scheduled. The arrow indicates that the step being scripted is Back Up Server Database. Select the device to be used from the menu and select the radio button next to the type of backup that will be performed. Click Next.
56
10-67
Back Up Storage Pools
Back Up Storage Pools is the next task to be scripted. Now a relationship must be added. Select Add a Relationship.
57
Add a Relationship
Select a storage pool to back up and up to three copy storage pools where the backup will be stored, and click OK.
58
10-68
Back Up Storage Pools
The BACKUPPOOL data will now go to the COPYPOOL. Click Next.
59
Migrate Stored Data
Select the storage pool to migrate, set the migration threshold, and set the amount of time the process can run before it is canceled. Click Next to continue.
60
10-69
Expire Stored Data
If you want to limit the amount of time allowed for the expiration process, set that value here, and click Next to continue.
61
Reclamation
Select the storage pool to run reclamation for, set the percent of unused space which will be the trigger to start the reclamation process, and set the amount of time the process is allowed to run.
62
10-70
Schedule of Maintenance
Set the schedule for the script, including date and time, and click Finish.
63
Finish
The check mark under the Maintenance Script heading indicates a maintenance script has been created for this server.
64
Server Properties and Scripts
65
You can verify that a scripted maintenance plan has been created for this server by viewing Server Properties. Select the radio button next to the server and use the SELECT ACTION menu to select Server Properties. Then select the scripts from the left panel.
10-72
TSM Database Management Tool

TSM Database Management Tool

Tool is provided to estimate space to be recovered. A database reorganization is needed infrequently. A decision to reorganize would depend on: The database size. The estimated amount of space to be recovered. Use patterns of the databases. Issue the following command: ESTIMATE DBREORGSTATS
TSM must be stopped to reorganize the database.
66
Over time, the server database may experience fragmentation. Reorganizing the database can improve query performance. You can use the estimate dbreorgstats command to estimate how much space can be recovered if a reorganization is performed. The estimate allows you to determine if a reorganization will offer any space savings. The command performs the following: Scans all tables defined in the TSM server. Processes a single table at a time. Finishes one table and progresses to another until all tables areevaluated. Traverse tables leaf pages from lowest order page (page with the lowest order key) to the highest order page (page with the highest order key).
Reads the records in table leaf pages in ascending key order and records statistics about: Records processed Logical leaf pages needed Tables processed
After evaluating all tables, this command will display information about the minimum estimated amount of database space that would be recovered if a database reorganization were performed.
10-73
When process completes, messages show the results of processing. (ANR1784I) Results of the last time process was run are also shown in q db f=d.
Follow the procedure for Reorganizing the Database in the Tivoli Storage Manager Administrators Guide.
10-74
Student Exercise
Student Exercise
67
10-75
Review Questions
1. True or False? You can recover information from a TSM storage pool without the TSM database. 2. A(n) ____________________ backup takes less time to run because it copies only those database pages that have changed since the last time the database was backed up. 3. A ___________________ backup is a full backup that does not interrupt the full plus incremental backup series. 4. True or False? The main reason to do incremental backups is because you use fewer tapes. 5. True or False? It is a good idea to mirror your database and recovery log. 6. True or False? The IBM Tivoli Storage Manager maintenance plan runs monthly virus scans.
IBM Tivoli Storage Manager 5.5 Implementationand Adminstration
10-77
Review Answers
1. True or False? You can recover information from a TSM storage pool without the TSM database. false 2. A(n) ____________________ backup takes less time to run because it copies only those database pages that have changed since the last time the database was backed up. Incremental 3. A ___________________ backup is a full backup that does not interrupt the full plus incremental backup series. Snapshot 4. True or False? The main reason to do incremental backups is because you use fewer tapes. False 5. True or False? It is a good idea to mirror your database and recovery log. True 6. True or False? The IBM Tivoli Storage Manager maintenance plan runs monthly virus scans. False
10-78
Summary
Summary
Back up the IBM Tivoli Storage Manager database. Recover the IBM Tivoli Storage Manager database. Back up the storage pools. Recover the storage pools.
68
10-79
10-80
11-1
Introduction
Central scheduling enables automation of backup, archive, and other processes. Scheduling of IBM Tivoli Storage Manager operations can be done with an external scheduler or with the built-in Tivoli Storage Manager scheduler. The Tivoli Storage Manager administrative interfaces for defining, updating, and deleting schedules will be described in this unit.
Objectives
Objectives
Describe the difference between client polling and server prompted methods. Identify and describe available scheduler options. Associate scheduler options with the schedule method to which it applies. Identify the tasks that can be scheduled for a client. Create a schedule. Copy a schedule. Define association of client to schedule.
11-2
Unit 11: Automating Operations Scheduling Options
Lesson 1: Scheduling Options

Overview of Schedules
Overview of Schedules
Two types of scheduling: Client scheduling
Administrative scheduling on the server
Tivoli Storage Manager uses schedules to allow you to automate operations. Each scheduled operation is called and is tracked by the server and recorded in the database. Scheduled operations that are in progress, have completed, or have failed are recorded. You can query the log to determine whether the scheduled events have completed successfully or not. Event records can be deleted from the database as needed to recover database space. The administrator is responsible for building and maintaining the schedules and has the authority to prioritize workstations. In addition, the administrator can determine the number of client server sessions that may be used by central scheduling. The Central Scheduler supports two modes of scheduling: Client Polling and Server Prompted. For environments that occupy multiple time zones, schedules run in the time zone of the server.
11-3
Unit 11: Automating Operations Scheduling Options
Scheduling Options
Scheduling Options
MAXSCHEDSESSIONS* MAXCMDRETRIES RETRYPERIOD QUERYSCHEDPERIOD RANDOMIZE* SCHEDCMDDISABLE SCHEDMODE SESSIONINITIATION SCHEDLOGNAME SCHEDLOGRETENTION
dsm.sys dsm.opt
POSTSCHEDCMD POSTNSCHEDCMD PRESCHEDCMD PRENSCHEDCMD MANAGEDSERVICES TPCCLIENTADDRESS TPCCLIENTPORT SRVPREPOSTSCHEDDISABLED SRVPREPOSTSNAPDISABLED SCHEDRESTRETRDISABLED
There are several processing options which impact the performance of the client scheduler. You can define most of these options in the client options file (dsm.opt or dsm.sys) on the Tivoli Storage Manager client. Some of these options can be set globally on the Tivoli Storage Manager server for all Tivoli Storage Manager clients. * Server defined
4
There are several processing options which impact the behavior of the client scheduler. On the Tivoli Storage Manager client, you can define most of these options in the client options file (dsm.opt). However, some of these options can be set globally on the Tivoli Storage Manager server for all Tivoli Storage Manager clients. These options will be described throughout this unit.
11-4
Unit 11: Automating Operations Client Scheduling
Lesson 2: Client Scheduling
Client Scheduling
Client scheduling Backup-Restore and Archive-Retrieve Client operating system commands and scripts One-time scheduled commands Two modes of client scheduling: Client Polling Server Prompted
11-5
Traditional Scheduling
Traditional Scheduler Services and Client Acceptor Services

Traditional Scheduler Services
Started with command dsmc sched command. Remains active, even after scheduled backup is complete. Requires higher use of system resources when idle. Tivoli Storage Manager client options and Tivoli Storage Manager server override options are only processed once when dsmc sched is started. You must restart the scheduler process for updated Tivoli Storage Manager options to take effect.
Client Acceptor Services

The Tivoli Storage Manager Client Acceptor service (CAD) can be installed and configured to manage the scheduler. The CAD serves as an external timer for the scheduler. When the scheduler is started, it queries the server for the next scheduled event. The event is either executed immediately or the scheduler exits. The CAD restarts the scheduler when it is time to execute the scheduled event.
6
About CAD-managed Services

Using client acceptor services can reduce the number of background processes. The client acceptor (CAD) is a Web client process which uses an HTTP service that serves the Web client Java applet to the Web browsers. The program that starts the client acceptor process is called dsmcad. On Windows, the client acceptor is installed and run as a service.
Refer to the IBM Tivoli Storage Managers Backup-Archive Installation and Users Guide for more information.
11-6
Central Scheduling Mode: Client Polling

The client polling technique is supported for all client workstations, all communication methods, and on all servers.
Central Scheduling Mode: Client Polling
backup-archive client
TSM server
1. The client queries the server for a scheduled operation. 2. The server sends the schedule to the client. 3. The client waits for start time, then begins the scheduled operation.
All communication methods are supported.

7
In client polling, the TSM client periodically queries or polls the server for a scheduled operation and the date and time that the operation is to start. The client then waits until it is time to start the scheduled operation and executes the operation. Client polling is initiated when the client starts the TSM client scheduling program using the command line. To start the program, enter dsmc schedule. The program will continue to query the server and execute schedules until you explicitly stop the program or the machine is shut down.
11-7
Central Schedule Mode: Server Prompted

The server-prompted technique is supported for all client workstations that use TCP/IP as the communication method with the server.
Central Scheduling Mode: Server Prompted
1. Client registers its TCP/IP address with the server. 2. Server notifies the client that a scheduled operation should be performed.
3. Client queries the server for the scheduled operation, then begins that operation.
TCP/IP is the only communication method supported.

8
In server-prompted mode, the Tivoli Storage Manager client registers its TCP/IP address with the server and waits until the server contacts the client to notify the client that a scheduled operation should be performed. The client then queries the server for the operation and executes the operation. Upon completing the operation, the client notifies the server that the operation has completed, either successfully or unsuccessfully. Server-prompted mode is initiated by the client starting the Tivoli Storage Manager client scheduling program using the command line. To start the program, enter dsmc schedule. To enable server prompted scheduling, change the client option sets so that the SCHEDMODE is PROMPTED.
11-8
Selecting Schedule Methods

There are two places where you specify a scheduling mode: the server and the client.
Selecting Schedule Methods

Scheduling mode can be set by the administrator on the server. or Scheduling mode can be set in the options file on the client.
dsm.opt
dsm.sys
SET SCHEDMODes SCHEDMODe POLLing | PRompted

Options: ANY (default and suggested method)
Polling PRompted
On the server, the administrator with system privileges must specify which central scheduling modes will be supported by the server. The Set SCHEDMODes command is used, and the supported parameters are: ANY: Indicates the server can support clients using either client polling or server prompted scheduling. ANY is the default and suggested value. POLLING: Indicates that only clients using client polling will be accepted. PROMPTED: Indicates that only clients using server-prompted mode will be accepted.
On the client, the options file must be updated with the SCHEDMODE option that is used to specify which mode the client scheduler will operate in. The option is specified as follows:
SCHEDMODe POlling | PRompted
This option is ignored except during the execution of the dsmc schedule command, which invokes the client portion of the central scheduling function.

11-9
Users (root users on UNIX systems) set the scheduling mode on client nodes. They specify either the client polling or the server-prompted scheduling mode on the command line or in the client user options file (client system options file on UNIX systems).
11-10
Additional Client Scheduling Options

Additional Client Scheduling Options

MAXCMDRETRIES RETRYPERIOD SCHEDMODE SCHEDLOGNAME SCHEDLOGRETENTION SCHEDCMDDISABLE MANAGEDSERVICES
dsm.sys dsm.opt
MAXSCHEDSESSIONS
(must be set by an administer with System Privilege)
10
MAXCMDRETRIES: Specifies the maximum number of times you want the client scheduler on your workstation to attempt to process a scheduled command that fails. The TSM administrator can also set this option. If the TSM administrator specifies a value for this option, that value overrides what you specify in the client options file after your client node successfully contacts the TSM server. All clients support this option. For UNIX clients, this option goes in the client system options file. Set maxcmdretries: This command is used to specify the maximum number of times that a scheduler on a client node can retry a scheduled command that fails.
RETRYPERIOD: Specifies the number of minutes you want the client scheduler to wait between attempts to process a scheduled command that fails or between unsuccessful attempts to report results to the server. The TSM administrator can also set this option. If the TSM administrator specifies a value for this option, that value overrides what you specify in the client option file after your client node successfully contacts the TSM server. All clients support this option. For UNIX clients, this option goes in the client system options file. Set retryperiod: This command is used to specify the number of minutes the scheduler on a client node waits between retry attempts after a failed attempt to contact the server or after a scheduled command fails to process. Clients can set their own retry period at the time their scheduler program is started. You can use this command to set a global value for the retry period, which
11-11
will override the value specified by all clients. The value for the client is overridden only if the client is able to connect with the server. When setting the period between retry attempts, set a time period that permits more than one retry attempt within a typical startup window. This command is used in conjunction with the set maxcmdretries command to regulate the period of time and the number of retry attempts to execute a failed command.
SCHEDMODE: Specifies whether you want to use the polling mode (the client node periodically queries the server for scheduled work) or the prompted mode (the server contacts the client node when it is time to start a scheduled operation). All communication methods can use the client polling mode, but only TCP/IP can use the server prompted mode. SCHEDLOGNAME: Specifies the name and location of a file where you want Tivoli Storage Manager to store the schedule log. For UNIX clients, this option goes in the client system options file. When you run the schedule command, output from scheduled commands appears on the screen and can be directed to the file you specify with this option. SCHEDLOGRETENTION: Specifies the number of days to keep entries in the schedule log and whether to save the pruned entries. Tivoli Storage Manager prunes the log after every schedule is run if you tell Tivoli Storage Manager to prune. The default is not to prune the log. For UNIX clients, this option goes in the client system options file. SCHEDCMDDISABLE: Specifies whether to disable the scheduling of generic commands specified by your Tivoli Storage Manager administrator. MANAGEDSERVICES: Specifies whether the Storage Manager Client Acceptor service manages the Web client, the scheduler, or both.
MAXSCHEDSESSIONS
An administrator with System Privlege can set MAXSCHEDSESSIONS. Set maxschedsessions: This command is used to regulate the number of sessions that the server can use for processing scheduled work. This command specifies the maximum number of scheduled sessions as a percentage of the total number of server sessions available.
Set MAXSCHedsessions schedulepercent 80
To check, issue query status. Maxschedsessions is displayed as a number, not a percentage. This setting should be changed if client nodes receive messages that server sessions are not available when trying to execute scheduled events. If you find that scheduled sessions are not contacting the server, you may have a network error.

11-12
Additional Client Polling Options

Additional Client Polling Options
Command: DSMC -SCHEDMODE=POLLING Options file: schedmode polling

dsm.opt
dsm.sys
queryschedperiod (how often to contact the server) query sched
11
QUERYSCHEDPERIOD: The value for this parameter can be set by each client node at the time the client scheduler program is started. You can set a global value for the period between attempts by the client to contact the server for scheduled work. This value overrides the value specified by the client. Set queryschedperiod: This command is used to regulate the frequency with which client nodes contact the server to obtain scheduled work when they are running in the client polling mode. Use the QUERYSCHEDPERIOD option to specify the number of hours you want the client scheduler to wait between attempts to contact the TSM server for scheduled work. This option applies only when the DSMC SCHEDMODE option is set to POLLING. Tivoli Storage Manager uses this option only when the dsmc schedule command is running. For UNIX clients, this option goes in the client system options file dsm.sys.
11-13
Additional Server Prompted Options

Additional Server Prompted Options
dsm.opt
TCPCLIENTAddress
TCPCLIENTPort
dsm.sys
Client options file example: SCHEDMODe COMMmethod TCPCLIENTAddress TCPCLIENTPort Prompted TCPip Addressdomain_name dot_address 1501
12
TCPCLIENTADDRESS: Specifies a TCP/IP address if your client node has more than one address, and you want the server to contact a different address than the one used to make initial contact with the server. For UNIX clients, this option goes in the client system options file. TCPCLIENTPORT: Specifies a TCP/IP port number if you want the TSM server to contact a different port than the one used to make initial contact with the server. If the default or specified port is busy, Tivoli Storage Manager attempts to use any other available port. For UNIX clients, this option goes in the client system options file.
11-14
Preschedule and Postschedule Processing

Options are provided to allow preschedule processing and postschedule processing during the client schedule process execution. These options can be overwritten by the OPTION parameter in the schedule definition.
Preschedule and Postschedule Processing

Server prompts client to begin scheduled backups. The preschedule command string begins first. Quiesce DB, Onarchive DB TSM scheduled actions begin. Back up resultant files from Onarchive. The postschedule command string begins last Check results. Back up. PREschedulecmd=command string or PRENschedulecmd=command string POSTschedulecmd=command string or POSTNschedulecmd=command string
13
PRESCHEDULECMD and PRENSCHEDULECMD specify client OS commands that you want executed prior to the TSM schedule process. The difference between PRESCHEDULECMD and PRENSCHEDULECMD is that with PRESCHEDULECMD the schedule process waits for the client OS commands to complete before executing, whereas with PRENSCHEDULECMD, the schedule process does not wait. POSTSCHEDULECMD and POSTNSCHEDULECMD specify client OS commands that you want executed after the TSM scheduled action. The difference between POST and POSTN is the same as for PRE and PREN: POST waits for the OS commands to complete, whereas POSTN does not wait.
11-15
Consistent Client Return Codes

Consistent Client Return Codes
return code
meaning
. . .
14
The command-line client and scheduler provide reliable, consistent, and documented return codes and provide automation of client operations through user-written scripts. Administrators can now distinguish between scheduled backups that complete successfully with no skipped files and scheduled backups that complete successfully with one or more skipped files. Also, if the pre-schedulecmd command ends with nonzero return codes, the scheduled event will not run. This ensures that scheduled events will not run if prescheduled commands do not complete successfully.
11-16
Example of Randomizing
Example of Randomizing
NODE A NODE B NODE B NODE A NODE C NODE C
01:30
03:01
05:00
05:45
Randomize Period
Randomize Period
22:00 Polls Starts Randomize% = 50
01:00 Startup Window
04:00
05:00
06:00
07:00
Scatter schedule start times across window. Balance network and server loads. % specification Defines portion of the startup window in which start times will randomly occur. Randomization period based on time client polls. Client polling mode only.
15
The purpose of randomizing the start time is to scatter scheduled work across the startup window. Randomizing balances the load on the server as well as the load on the networks without having to duplicate schedules except for their start times. Set randomize: This command is used to specify the degree to which start times are randomized within the startup window of each schedule for clients using the client polling mode. The maximum percentage of randomization allowed is 50%. This limit ensures that half of the startup window is available for retrying scheduled commands that have failed.
11-17
Defining Schedules
Defining Schedules
Defining schedules involves the following: System or policy privilege is required. Schedules are defined with a define schedule command. Schedules apply to a particular policy domain. Define association command associates client with schedule.
16
Schedules are created and maintained in the TSM database by an administrator with either system or policy privileges and are defined with a define schedule command and apply to a particular policy domain. Administrators use the define association command to associate clients (that are in the domain) with a schedule. A client may be associated with more than one schedule, and any number of schedules can be defined in a policy domain. A client executes schedules serially.
11-18
Parameters for Defining Schedules

Parameters for Defining Schedules

Policy Domain Name Schedule Name Description Action Options Objects Priority Start Date Start Time Duration Duration Units Indefinite Period Period Units Day of Week Expiration
17
POLICY DOMAIN NAME: Specifies the name of the policy domain to which this schedule belongs. This parameter is required. SCHEDULE NAME: Specifies the name of the schedule to be defined. This parameter is required. The maximum length of the name is 30 characters. DESCRIPTION: Specifies a description of the schedule. This parameter is optional. The maximum description length is 255 characters. The description must be enclosed in quotation marks if it contains any blank characters. The default is no description. ACTION: Specifies the action that occurs when this schedule is executed. This parameter is optional. The default value is INCREMENTAL. Possible values are: INCREMENTAL: Specifies that this schedule initiates the backup of any files that have changed since the last backup and for which the specified time between backups has elapsed. SELECTIVE: Specifies that this schedule backs up only the files specified with the OBJECTS parameter. ARCHIVE: Specifies that this schedule archives the files specified with the OBJECTS parameter.
11-19
RESTORE: Specifies that this schedule restores the files specified with the OBJECTS parameter. RETRIEVE: Specifies that this schedule retrieves the files specified with the OBJECTS parameter. COMMAND: Specifies that the action is to be a client operating system command string specified with the OBJECTS parameter. MACRO: Specifies that a macro whose file name is specified with the OBJECTS parameter is to be executed.
OPTIONS: Specifies options that are supplied to the dsmc command at the time the schedule is executed. Only those options that are valid on the dsmc command line may be specified for this parameter. This parameter is optional. You can specify most options from the client option file. Each option is preceded by a hyphen and delimited with a space. The option string must be enclosed in quotation marks if it contains any blank characters. OBJECTS: Specifies the objects for which the specified action is performed. This parameter is required except when ACTION = INCREMENTAL. The allowed objects depend on the action you specify with the ACTION parameter and the operating system used by the clients associated with the schedule. PRIORITY: Specifies the priority value for a schedule. This parameter is optional. You can specify an integer in the range of 1-10, inclusive, with 1 being the highest priority and 10 being the lowest. The default value is 5. If two or more schedules for a given client have the same window start time, this value determines the order of execution. The schedule with the highest priority starts first. START DATE: Specifies the date for the beginning of the window in which the schedule is first executed. This parameter is optional. The default value is the current date. This parameter is used in conjunction with the STARTTIME parameter to specify when the initial startup window begins. START TIME: Specifies the time for the beginning of the window in which the schedule is first executed, in HH:MM format. This parameter is optional. The default value is the current time. This parameter is used in conjunction with the STARTDATE parameter to specify when the initial startup window begins. DURATION: Specifies the number of units that define the length of the startup window. This parameter is optional. This value must be in the range of 1-999, inclusive. The default value is 1. This parameter is used in conjunction with the DURUNITS parameter to specify the length of the startup window. For example, if you specify DURATION = 20 and DURUNITS = MINUTES, the schedule must be started within 20 minutes of the start date and start time. DURATION UNITS: Specifies the time units used to determine the duration of the window in which the schedule can start. This parameter is optional. The default value is HOURS. This parameter is used in conjunction with the
11-20
DURATION parameter to specify how long the startup window remains open to execute the schedule. INDEFINITE: Specifies that the startup window has an indefinite duration. The schedule can run any time after the scheduled start time until the schedule expires. You cannot specify duration units of INDEFINITE unless you also specify PERIOD UNITS as ONETIME. PERIOD: Specifies the length of time between startup windows for this schedule. This parameter is optional. You can specify an integer in the range of 1-999, inclusive. The default value is 1. This parameter is used in conjunction with the PERUNITS parameter to specify the period between startup windows. For example, if you specify PERIOD = 5 and PERUNITS = DAYS (assuming that DAYOFWEEK = ANY), the operation is scheduled every five days after the initial start date and start time. PERIOD UNITS: Specifies the time units used to determine the period between startup windows for this schedule. This parameter is optional. The default value is DAYS. DAY OF WEEK: Specifies the day of the week on which the startup window begins. This parameter is optional. If the beginning of the calculated startup window falls on a day that does not correspond with your value for the DAY OF WEEK parameter, the startup window will be shifted forward in 24-hour increments until the DAY of WEEK parameter is satisfied. If you select a value for DAY OF WEEK other than ANY, depending on the values for PERIOD and PERIOD UNITS, schedules may not be executed when you would expect. Use the query event command to project when schedules will be executed and thereby ensure that the desired result is achieved. The default value is ANY. EXPIRATION: Specifies the date on which this schedule is no longer used, use the MM/DD/YYYY format. This parameter is optional. The default value is NEVER.
11-21
Defining Schedules: Server-prompted Example

Defining Schedules: Server-prompted Example

Register Schedule Start TSM server backup-archive client
set maxsessions
100 90
DSM.OPT DSM.SYS (UNIX) SCHEDMODE PROMPTED COMMMETHOD TCPIP
set maxschedsessions set schedule prompted
define schedule DOMAIN SCHEDULENAME 23:30 ACTION=I, STARTT = DUR=6, PERIOD=1 DURU=HOURS, PERU=DAYS DAYOFWEEK=WEEKDAY
18
11-22
Defining Schedules Using the Administration Center

Defining Schedules Using the Administration Center
Client Node Schedule: 1. Click Policy Domains and Client Nodes in the Tivoli Storage Manager tree. 2. In the Servers table, click the name of a server. 3. In the policy domains notebook for the server, click the name of a domain. 4. In the properties portlet for the domain, click Node Schedules. 5. In the table, click Select Action, select Create a Schedule.
Schedules can also be Viewed and Modified with the Administration Center.
19
Use the Web interface to create a new schedule. A schedule can have two forms, depending on whether the schedule applies to client operations or administrative commands. The syntax and parameters for each form are defined separately.
11-23
Client Node Schedules with the Administration Center

Client Node Schedules with the Administration Center
20
11-24
Using the Command Line to Define a Schedule

There are two styles of schedules: classic (default) and enhanced.
Using the Command Line to Define a Schedule

To define a classic schedule on the command line, use the following command. DEFine SCHedule domainname schedulename Type=Client DESCription=description ACTion=action OPTions=optionstring OBJects=objectstring PRIority=priorityvalue STARTDate=startdate STARTTime=starttime DURation=durationvalue DURUnits=durunitsvalue PERUnits=perunitsvalue PERiod=periodvalue DAYofweek=dayofweekvalue EXPiration=expirationvalue
UPDATE Schedule... DELETE Schedule...

21
Example:
define schedule xyz_critical_project weekly_backup startdate=06/07/2003 starttime=23:00 duration=4 durunits=hours perunits=weeks dayofweek=saturday options=-quiet
For more details, issue the help define schedule command.
11-25
Enhanced Scheduling
Enhanced Scheduling
The enhanced schedule style, also known as calendar-based scheduling, increases flexibility for client and administrative schedules. Calendar-based scheduling can be defined with Administration Center or with the command line. To define an enhanced style schedule on the command line, issue the following command. define schedule test_lab starttime=20:00 \ action=archive object=/home/lab/tests/* \ duration=1 durunits=hour schedstyle=enhanced month=mar,jun,sep,dec \ weekofmonth=last dayofweek=fri
22
Schedules can be classic or enhanced, depending on how the interval to the next execution is defined. Classic schedules allow the period to be as small as an hour. Enhanced schedules allow actions to be executed on specific days. The Tivoli Storage Manager scheduler provides calendar-based scheduling for increased flexibility of client and administrative schedules. SCHEDSTYLE defines either the interval between times when a schedule should run or the days on which it should run. The style can be either classic or enhanced. The default is the classic syntax. For classic schedules, these parameters are allowed: PERIOD, PERUNITS, and DAYOFWEEK. These parameters are not allowed: MONTH, DAYOFMONTH, and WEEKOFMONTH.
For enhanced schedules, these parameters are allowed: MONTH, DAYOFMONTH, WEEKOFMONTH, and DAYOFWEEK. These parameters are not allowed: PERIOD and PERUNITS.
11-26
Examples of Calendar-Based Schedules

Examples of Calendar-Based Schedules with the Administration Center

Some examples of schedules that can be created are: First and third Tuesday of every month Last Friday of every month 1st and 15th day of every month 10th day of last month in each quarter First Saturday or Sunday of every month Every Monday, Wednesday, and Friday
23
11-27
Schedule Example
Schedule Example
24:00 Backup
Start
Backup
Start
actual backup time startup window
01:00
01:00
Startup window: Starttime = 01:00 Function: Action = Incremental Backup Time between windows: Period = 2 days Duration = 6 hours
Action must start within startup window. Action may not complete within window. Scheduled operations run serially on client. Event log maintained on server.
24
A schedule is given a startup window that defines when a scheduled operation is to start. The client must start the scheduled operation within the startup window. If the client or the network is unavailable during the startup window, the client will wait until the next occurrence of the schedule's startup window to begin the operation. The scheduled operation must start within the window, however, it may complete outside of the window. A log is maintained on the server, which records information about the scheduled events. The administrator can query the log for information about started, completed, and failed events.
11-28
Relative Date and Time

Relative Date and Time

In defining schedules, date and time can be specified relative to the execution of the command. Relative time syntax:
DATE=mm/dd/yyyy DATE=TODAY DATE= + number of days DATE= - number of days
Relative time syntax:

TIME=hh:mm:ss TIME=NOW TIME=NOW + number of hours: number of minutes TIME=NOW - number of hours: number of minutes
25
Relative Date
Date specification can be written as a displacement from the current date. The current date is furnished with the keyword TODAY.
Relative Time
Time specification can be written as a displacement from the current time. The current time is furnished with the keyword NOW.
11-29
Copying a Schedule
The copy schedule command copies the schedule to another domain. An administrator can define any number of schedules in a policy domain.
Copying a Schedule
Schedule descriptions and parameters are copied with the copy schedule command. The copied schedule can then be edited.
To copy the LABSYS schedule from policy domain DOMAIN1 to DOMAIN2 and name the new schedule LABSYSNEW, enter the following command. copy schedule domain1 labsys domain2 labsysnew
26
11-30
Using the Command Line to Define an Association

Use the define association command to associate one or more clients with a schedule. Client nodes that are associated with a schedule initiate Tivoli Storage Manager functions according to that schedule.
Using the Command Line to Define an Association
d e fi n e as
socia
tion
Policy Domain STANDARD
define association
tion ocia s s a
schedule daily_incr
ine def
define association standard daily_incr client name

27
DOMAINNAME Specifies the name of the policy domain to which the schedule belongs. This parameter is required. SCHEDULENAME: Specifies the name of the schedule that you want to associate with one or more clients. This parameter is required. NODENAME: Specifies the name of the client node to be associated with the specified schedule. This parameter is required. You can specify a list of clients that you want to associate with the specified schedule. Commas, with no intervening spaces, separate the items in the list. You can use a pattern matching expression to specify a name. All matching clients are associated with the specified schedule. In some commands, such as the query commands, you can use wildcard characters to create a pattern-matching expression that specifies more than one object. Using wildcard characters makes it easier to tailor a command to your needs.
11-31
The wildcard characters you use depend on the operating system from which you issue commands. For example, you can use wildcard characters such as an asterisk (*) to match any (0 or more) characters or you can use a question mark (?), or a percent sign (%) to match exactly one character. If a client is listed, but is already associated with the specified schedule or is not assigned to the domain to which the schedule belongs, the command has no effect for that client.
11-32
One-Time Scheduled Client Commands

One-Time Scheduled Client Commands

The DEFINE CLIENTACTION command is issued on the server. If schedule mode is prompted, the action begins in three to ten minutes. If schedule mode is polling, the time interval is set by the QUERYSCHEDPERIOD client option.
The SET CLIENTACTDURATION command sets how long the one-time schedule remains active. The client action duration can be viewed with the QUERY STATUS command. The defaults for a client action are: Schedule priority is set to 1 Duration is set to 5 days Period is set to Onetime Scheduler services must be running.
28
Define clientaction: Allows a TSM administrator to have a command executed on a TSM client without defining a schedule and associating the schedule with the client. With the define clientaction command, the command executes once only. Clients may be selected from multiple domains by the use of the NODE and DOMAIN parameters. Pattern matching expressions may be used in the node list specified, and if no nodes are selected, the action is sent to all nodes. When a command is specified with the define clientaction command, the speed with which that command is executed depends entirely upon the scheduling mode for the desired client. If the client schedule mode is server-prompted, then the command is executed immediately. If the client concerned is using a schedule mode of POLLING, then the action is executed the next time the client queries the server for its schedules (governed by the QUERYSCHEDPERIOD client parameter). WAIT=[YES | NO] parameter, when used with define clientaction command, specifies whether to wait for a scheduled client operation to complete. WAIT=YES allows for the clientaction command to complete before processing the next step. This synchronous operation provides the serialization in a script. The default is NO.
11-33
Clients for which actions are defined must have their scheduled client running. Set clientactduration: Specifies the duration in days for the schedule and the number of days it is retained in the TSM database before automatically being deleted. If this value is set to 0, the schedule duration is indefinite and the schedule and associations are not deleted. Only schedules and associations defined by the define clientaction are deleted from the TSM database automatically. The value of CLIENTACTDURATION may be viewed with the query status command. The defaults for a client action are: Schedule priority is set to 1. Duration is set to 5 days. Period is set to Onetime.
11-34
Preventing Unwanted Schedule Actions

Preventing Unwanted Schedule Actions

There are three ways in which a Tivoli Storage Manager administrator using the scheduler could potentially execute an unwanted operation on a client machine:
Executing a scheduled operating system command operation (action=cmd). Executing a scheduled operating system command operation using the preschedule or postschedule or presnapshot or postsnapshot command defined in the Tivoli Storage Manager server client option set or define schedule command. Executing a scheduled restore or retrieve operation (action=restore or action=retrieve).
29
11-35
Options to Prevent Unwanted Schedule Actions

Options to Prevent Unwanted Schedule Actions

The SRVPREPOSTSCHEDDISABLED option disallows a preschedule or postschedule command defined by the Tivoli Storage Manager administrator from executing on the client machine. The SRVPREPOSTSNAPDISABLED option disallows a presnapshot or postsnapshot command defined by the Tivoli Storage Manager administrator from executing on the client machine. The SCHEDRESTRETRDISABLED option disallows the execution of a restore or retrieve schedule operation.
30
If a preschedule or postschedule command is defined by both the client and the Tivoli Storage Manager administrator, the command defined by the Tivoli Storage Manager administrator will not override the corresponding command defined in the client option file. If a presnapshot or postsnapshot command is defined by both the client and the Tivoli Storage Manager administrator, the command defined by the Tivoli Storage Manager administrator will not override the corresponding command defined in the client option file.
11-36
Using the Command Line to Query Schedule

Output fields from the query schedule command:
Schedule Name: Description: Schedule Style: Action: Options: Objects: Priority: Next Execution: Duration: Period: Day of Week: Month: Day of Month: Week of Month: Expiration:
The format equal detail (f=d) option with the command requests and lists the output in a different format and provides more details.
Using the Command Line to Query Schedule
31
11-37
Unit 11: Automating Operations Administrative Tasks
Lesson 3: Administrative Tasks

Automating Administrative Tasks
Automating Administrative Tasks
Administrator commands can be handled by Tivoli Storage Manager scheduler to: Automate server operations. Ensure server resources are available to clients. Ensure server functions performed with minimal manual intervention.
32
TSM server includes a central scheduling component that is used to schedule the automatic execution of client functions. This scheduler provides facilities for defining, updating, querying, and deleting client schedules, associating schedules with one or more client nodes, and reporting on the success or failure for each scheduled event. A similar mechanism is required to automate server operations. Many of the administrative commands can be used to tune server operations and start functions that require significant server or system resources. The ability to automate the execution of these commands helps the administrator ensure that: Server resources are available when needed by clients Server functions are performed with minimal manual intervention
Each TSM schedule can schedule only one administrative command. When the schedule executes, it has the same authority as when the administrator originally defined it. It can be

11-38
in the ACTIVE or INACTIVE state. The default is INACTIVE. The active state indicates that the schedule is eligible for execution when the specified command window occurs. An administrator can also schedule commands that activate or inactivate other scheduled commands. The following processes are not supported by the administrative command scheduler: Command macros (as used on the administrative client) Redirection of command output
11-39
Scheduling an Administrative Command

Scheduling an Administrative Command
What to consider when scheduling an administrative command: Type of schedule command can be administrative or client. Type=Administrative Type=Client Output from execution of administrative tasks is sent to the activity log. Administrative tasks are not associated with a policy domain.
33
The query event and delete event commands are modified to view and remove administrative command schedule status. A Type=Administrative is added to events so that you can discriminate between Type=Client and Type=Administrative. Redirection of command output is not allowed; instead, output is written to the activity log. Using the administrative client and the query actlog command, the output can be collected at a later time and placed in a file. Schedules defined as Type=Client are identified by policy domain and schedule names. Schedules defined as Type=Administrative are only qualified by a schedule name. The schedules do not need to be associated to nodes or servers by names.
11-40
Administrator Scheduling Commands

Administrator Scheduling Commands

Examples of administrator actions which can be scheduled: Lower threshold to immediately start migration. Lower threshold to immediately start reclamation. TSM server database backup. Inventory expiration. Storage pool backup.
Use the Administration Center to create maintenance scripts for these tasks.
Things to do today
34
If you define a schedule to lower the high threshold to zero, when the schedule executes, migration will automatically begin. You can then have a schedule that resets the threshold to your usual percentage. To improve tape drive usability, ensure that reclamation occurs during hours when backup or threshold migration does not occur. You can schedule a command to lower the threshold for reclamation processing to zero, so that when the command executes, reclamation will automatically begin. TSM server database backup can be automated to ensure a regularly scheduled backup is taken. Because file inventory expiration is a CPU-consuming job, you can schedule it for hours when the CPU load is low. Backup of the TSM server storage pool volumes can be automated to ensure that this task is done periodically and concurrently with the TSM server database backup.
11-41
Examples of Defining Administrative Schedules

Examples of Defining Administrative Schedules

Define a schedule named BACKUP_ARCHIVEPOOL that backs up the primary storage pool ARCHIVEPOOL to the copy storage pool RECOVERYPOOL. The backup runs at 6 p.m. every three days.
define schedule backup_archivepool type=administrative cmd="backup stgpool archivepool recoverypool" active=yes starttime=18:00 period=3
Define a schedule named BACKUP_ARCHIVEPOOL that backs up the primary storage pool ARCHIVEPOOL to the copy storage pool RECOVERYPOOL. Select an enhanced schedule and run on the following days of the month: 7, 14, 21, and 28.
define schedule backup_archivepool type=administrative cmd="backup stgpool archivepool recoverypool" schedstyle=enhanced dayofmonth=7,14,21,28
35
11-42
Defining Administrative Schedules Using the Administration Center

Defining Administrative Schedules Using the Administration Center
Administrative Schedule: 1. Click Storage Devices in the Tivoli Storage Manager tree. 2. In the Servers table, click a server name. 3. In the properties portlet for the server, click the Administrative Schedules tab. 4. In the table, click Select Action, and select Create a Schedule.
Schedules can also be Viewed and Modified with the Administration Center.
36
Administration Center Administrative Schedules
37
11-43
Additional Functions to Schedule

Additional Functions to Schedule
Other functions that you might want to schedule include:

Export-Import Changing device class mount point limits Volume history maintenance (deletion of unneeded records) All administrative commands except query actlog
38
You may want to change how many devices are allocated to different server activities, such as migration. For example, you may want fewer devices during the day and more at night because during the day the devices might be shared with other applications. Because volume history records are cumulative, you can delete older records periodically. The output of a scheduled administrative command is directed to the console and recorded in the activity log. Consequently, if Tivoli Storage Manager allowed you to schedule the query actlog command, the activity log size would immediately double.
Note: The following client scheduling constructs do not apply to administrative command schedules:
11-44
Maximum scheduled sessions Schedule randomization percentage Maximum command retries Retry period Scheduling modes
Student Exercise
Student Exercise
39
11-45
Review Questions
1. In _________________ mode, the Tivoli Storage Manager client registers its TCP/IP address with the server and waits until the server contacts the client to notify the client that a scheduled operation should be performed. 2. In ________________ mode, the TSM client periodically queries or polls the server for a scheduled operation and the date and time that the operation is to start. The client then waits until it is time to start the scheduled operation and executes the operation. 3. On the server, the administrator with system privilege must specify which central scheduling modes will be supported by the server. The set schedmodes command is used and the supported parameters include (select three): a. ANY b. SERVER c. CLIENT d. POLLING e. PROMPTED 4. With ________________ the schedule process waits for the client OS commands to complete before executing, whereas with ______________________, the schedule process does not wait. (PREschedulecmd/PRENschedulecmd) 5. The ____________________ command copies the schedule to another domain.
11-46
11-47
Review Answers
1. In _________________ mode, the Tivoli Storage Manager client registers its TCP/IP address with the server and waits until the server contacts the client to notify the client that a scheduled operation should be performed. prompted 2. In ________________ mode, the TSM client periodically queries or polls the server for a scheduled operation and the date and time that the operation is to start. The client then waits until it is time to start the scheduled operation and executes the operation. client polling 3. On the server, the administrator with system privilege must specify which central scheduling modes will be supported by the server. The set schedmodes command is used and the supported parameters include (select three): a. ANY b. SERVER c. CLIENT d. POLLING e. PROMPTED a. ANY, d. POLLING, and e. PROMPTED 4. With ________________ the schedule process waits for the client OS commands to complete before executing, whereas with ______________________, the schedule process does not wait. (PREschedulecmd/PRENschedulecmd) PREschedulecmd, PRENschedulecmd 5. The ____________________ command copies the schedule to another domain. copy schedule
11-48
Summary
Summary
Describe the difference between client polling and server prompted methods. Identify and describe available scheduler options. Associate scheduler options with the schedule method to which it applies. Identify the tasks that can be scheduled for a client. Create a schedule. Copy a schedule. Define association of client to schedule.
40
11-49
11-50
12-1
Introduction
Tivoli Storage Manager provides the ability to log client messages as server events. This unit introduces Tivoli Storage Manager logging and monitoring functions.
Objectives
Objectives
Identify client message candidates. Describe client event formatting. Query the activity log for events. Query the event log. Select from summary. Centralize event logging on the TSM server. Create reports with the select statement. Control event logging.
12-2
Unit 12: Monitoring and Event Logging Client Event Messages
Lesson 1: Client Event Messages

Monitoring and Logging Events
IBM Tivoli Storage Manager provides the ability to log certain client messages as events on the Tivoli Storage Manager server.
Monitoring and Logging Events
The events are monitored from the TSM server.
Client messages (events) are logged on the TSM server.
TSM server backup-archive clients
This lesson explains which messages can be logged and how client event monitoring is configured, including: Which client messages can be logged as events and how these messages are formatted. How client events are enabled and processed. How client events are stored, displayed, and queried.
IBM Tivoli Storage Manager 5.5 Implementationand Administration
12-3
Client Messages Logged on the Server

Client Messages Logged on the Server

Messages which are logged: Error conditions Client statistics Messages which are not logged: Session, communication, and TCA (Trusted Communication Agent) errors Client memory errors Informational messages Server disabled messages
For API messages, the API application is responsible for placing text into the string buffer.
4
Loggable Messages
The intention of client error logging is to notify the server of problems encountered during a client operation. Therefore, client message candidates are those messages that reflect an error condition. Client statistics are also passed to the server.
Nonloggable Messages
The following message types are not logged as events: Session, communication, and TCA errors: When encountering a session, communication, or a Trusted Communication Agent (TCA) error, the client is unable to initiate a session with the Tivoli Storage Manager server. Therefore the client cannot pass any message of this type to the server. Client memory errors: Because of insufficient memory resources, the client is not able to log these types of messages.
12-4
Informational messages: Informational messages do not contain an error condition and therefore are not logged. Server disabled messages: During the client sign-on procedure the Tivoli Storage Manager server provides information to the client about which messages should be logged to the server. Disabled messages are not passed to the server.
API Messages
For all application programming interface (API) related messages, it is the responsibility of the API to place an appropriate message text into the string buffer.
12-5
Client Event Formatting

Client Event Formatting

Common message repository
Contains new messages to facilitate central error logging. Command line and GUI share same repository.
Event formatting
Logged locally on client as ANS message. Externally appears in 4000-4999 range. Event message assigned ANE messages: ANE4007E.
The event message contains enough information that the message can be processed outside where it has occurred. Where it is applicable, the event contains the name of the object and file space.
Common Message Repository

Eligible messages are grouped in a common, shared repository. The repository resides on both the client and the server, and contains new messages for all client events and related event data. The command line and GUI clients share the repository.
Event Formatting
Client messages in the ANS4000 to ANS4999 range are eligible to be sent to the server as client events. Eligible client messages will be sent to the server as events using an ANE prefix instead of ANS. These client messages will be logged locally in the client schedule or error logs as appropriate.
12-6
Event Content
Client event messages contain enough information to be processed outside of the context where the message occurred. The client assigns the correct message number and provides information about related object or file space names. The server adds information such as time stamp, node name, or any other relevant information.
Message Formatting
Message Formatting
Messages are seen in the following format:
A N [ R S E ] # # # # [ I W E S]
Type: Levels:
R = Server S = Client E = Event
I = Info W = Warning E = Error S = Severe
For help, type H
####
6
12-7
Unit 12: Monitoring and Event Logging Event Receiving
Lesson 2: Event Receiving

Tivoli Storage Manager client and server events can be passed to external interfaces. This lesson describes these interfaces and how they are configured.
Event Receiving
Eligible events
Any client message which can be logged All server messages with an associated message number
Event receivers
TSM server console Activity log Event viewer (Windows) File exit User exit Server-to-server event logging Tivoli Enterprise Console (TEC) Tivoli NetView SNMP manager (AIX only)
7
Client messages are divided into two types of messages: loggable and nonloggable messages. All loggable messages can be enabled as events. Unlike client messages, there is no distinction for server events. Any server message that has an associated message number is an event. All events, regardless of being client or server events, can be enabled or disabled for the event receivers. Each interface supported by the central logging mechanism is called an event receiver. Events from clients or servers can be passed to one or more of the receivers. It is possible to send the same events to different receivers or to enable a group of events for specific receivers. You can choose any combination that suits your needs.
12-8
Event Filtering and Logging Commands

Event Filtering and Logging Commands

BEGIN EVENTLOGGING
Starts event logging for the specified receiver.
ENABLE EVENTS Enables specific events to be passed to one or more receiver. DISABLE EVENTS Disables specific events for one or more receiver. QUERY ENABLED Displays a list of enabled or disabled events. QUERY EVENTRULES
Displays a summary of enabled events.
END EVENTLOGGING Stops event logging for the specified receiver.
Begin Eventlogging
This command begins event logging for one or more receivers. Event logging is automatically turned on for receivers configured by default (server console and activity log). To begin event logging for the NetView receiver, enter:
tsm> begin eventlogging netview
If no receiver is specified, or if ALL is specified, logging begins for all configured receivers.
Enable Events
This command is used to enable specific events or groups of events for one or more receivers. With this command the following options are specified: Receiver name Message number or message severity

12-9
Node name (optionally)
Issue the following command:

tsm> enable event console,file all nodename=*
If the NODENAME parameter is specified, the events entered must be client events. When enabling individual client events, the four-digit message number must be prefixed with ANE:
tsm> enable event userexit ANE4027,ANE4034 node=*
This prefix enables all nodes to send the following client events to a user exit:
ANE4027 internal program message encountered and ANE4034 unknown system error
To enable only server events for a receiver, omit the NODENAME parameter. Individual server messages have to be specified with the prefix ANR:
tsm> enable event snmp ANR0131
This prefix enables the server error message Server DB space exhausted for the SNMP receiver.
Disable Events
The disable event command works similarly to the enable event command but instead of enabling specific events, the specified events are disabled. The command requires the same parameters, which are: Receiver name Message name or message severity Node name (optionally) The parameter specifications are based on the same rules as they are for the enable event command. You cannot disable server events.
12-10
Query Enable
The query enable command displays either a list of enabled events or a list of disabled events whichever is shorter. To display all enabled server events for receiver file enter:
tsm> query enable file
All server events are disabled for the receiver file. In the following example, no server events are enabled for this receiver.
Query Enable
To query enabled client events of node DBSERVER1 for the console receiver, enter the following command:
query enable console node=DBSERVER1

964 client events are enabled for node DBSERVER1 for the CONSOLE receiver. The following client events are DISABLED for node DBSERVER 1 for the CONSOLE receiver: ANE4000, ANE4007, ANE4014, ANE4021, ANE4030, ANE4994 ANE4001, ANE4008, ANE4015, ANE4022, ANE4031, ANE4002, ANE4009, ANE4016, ANE4023, ANE4032, ANE4003, ANE4010, ANE4017, ANE4024, ANE4033, ANE4004, ANE4011, ANE4018, ANE4025, ANE4034, ANE4005, ANE4012, ANE4019, ANE4028, ANE4992, ANE4006, ANE4013, ANE4020, ANE4029, ANE4993,
In this example, client events have been enabled and certain individual events disabled. The result will be the shorter of the enabled or disabled events list.
Query Eventrules
The query eventrules command displays a summary of events enabled:
tsm> query eventrules Date/Time Server Event Rules -------------------- -----------------------------------08/08/2000 09:21:33 ENABLE EVENTS FILE ALL 08/09/2000 13:15:29 ENABLE EVENTS SNMP ALL 08/14/2000 17:53:49 ENABLE EVENTS USEREXIT ERROR
12-11
Entering query eventrules displays the enabled server events. Entering the same command with a NODE= option will display enabled client events for that node or nodes.
End Eventlogging
The counterpart to the begin eventlogging command is the end eventlogging command. It stops event logging for one or more receivers. An administrator may want to end event logging for performance reasons.
12-12
Unit 12: Monitoring and Event Logging Working with Events
Lesson 3: Working with Events

Client Event Processing
Client Event Processing
10
When an eligible client message occurs, the message number is looked up in the client message event repository and assigned the appropriate ANE message number. The event message is formatted with the related object or file space name and is sent to the Tivoli Storage Manager server in this format. The server receives the event message and then adds information such as node name from where the event was received. The session number from which the original client error message originated is also added. If the event has been enabled for the Tivoli Storage Manager console, the event appears as soon as the information has been formatted. Message prefixes are: ANR: Server message ANS: Client message ANE: Event message
12-13
Enabling Client Events for the Tivoli Storage Manager Console

Enabling Client Events for the Tivoli Storage Manager Console

Display on the TSM console: Individually Message name By severity Warning, error, severe For specific nodes
critical project server
Message (events)
database servers
ANE40000E session 34 ANE40003E session 35 ANE40007E session 36
TSM console
laboratory systems
enable events console error, severe node=*
11
This example illustrates client events that are enabled for the Tivoli Storage Manager console. The default setting is ALL ENABLED. When enabling disabled events, the following information must be specified: The destination to which events are passed for monitoring. In this case, the destination is the Tivoli Storage Manager console. The console will show all related event information. For example, if the message occurred during a scheduled operation, the schedule name is also displayed. Which messages are enabled for the server console. The selection can be done by a list of individual message names, severity types, or a combination of both. If all loggable messages should be tracked, specify ALL. Which client nodes participate in central logging. When client events are enabled, a node name must be specified. You can specify a list of node names, or node names can be specified by using the wildcard character (*).

12-14
To enable all nodes to log events of ERROR or SEVERE severity to the Tivoli Storage Manager console, the following enable event command can be issued by an administrator:
tsm> enable events console error,severe node=*
Client events are displayed as soon as they have occurred on the client and have been passed to the Tivoli Storage Manager server. Client events should not be disabled.
12-15


TSM server database database servers servers
server events
critical critical project project server server
Message Message (events) (events)
event filter
laboratory laboratory systems systems
activity log table
12
Tivoli Storage Manager server events are always stored in the activity log and cannot be disabled. Server information in the activity log is often needed to resolve critical situations. All client events are also enabled for the server activity log by default.
12-16
Pruning the Activity Log

Pruning the Activity Log

Prune the log based on age of the entries. SET ACTLOGRETENTION Prune the log based on configured maximum allowed size. When maximum size is reached, the log is pruned, starting with the oldest activity log records, until the activity log size no longer exceeds the configured maximum size allowed. SET ACTlogretention size in MB MGMTSTYLE=Size SET ACTlogretention days MGMTSTYLE=Date
Use the query status command to display the management type and value of the setting for the activity log.
13
If the activity log occupies less space than the maximum allowed, no pruning is done. This log management option is in addition to the existing option to prune the log based on age of the entries. The query status command is updated to display the management type and value of the setting for the activity log.
Retention Period Parameter ACTLOGRET

The server option ACTLOGRET specifies how long activity log records are kept in the Tivoli Storage Manager database. Administrators should also consider the ACTLOG parameter setting. Many client events stored in the activity log increases Tivoli Storage Manager database usage. A short-term retention period reduces Tivoli Storage Manager database usage, but as server and client events are deleted after the specified time frame, they cannot be queried after that. The same retention period is used for server and client events. The ACTLOGRET parameter defaults to one day at installation. Considering setting the ACTLOGRET parameter to 14 days.
12-17
Querying Events in the Activity Log

Querying Events and the Activity Log

query event (query scheduled and completed events)
Use this command to display the status of scheduled events. The time and date parameters allow you to limit the query to events that were scheduled to occur within the specified times and dates. The command syntax differs for queries that apply to scheduled client operations and to scheduled administrative commands.
query actlog (query the activity log)

Use this command to display messages generated by the server. The activity log contains all messages that are sent to the server console under normal operation. The results of commands entered at the server console are not recorded in the activity log, unless the command affects or starts a background process or client session. Error messages are displayed in the activity log.
14
The query actlog command has the following parameters for extended event querying.
Parameter
ORIGINATOR NODENAME
Description Event origin: Server, client, or all events. Client node name: To display all events that derived from this node. Schedule name and related domain name: To display all events that have been logged for the specified scheduled client activity. Session ID of Tivoli Storage Manager client session: To display all logged events that originated from the specified client session. Owner name: To display all events that have been logged for a particular owner.
SCHEDULENAME AND DOMAINNAME
SESSION ID
OWNERNAME
12-18
Parameter
Description Specifies a text string that you want to search for in the activity log. Enclose the string expression in quotation marks if it contains blanks. You can use text and a wildcard character to specify this string. This parameter is optional.
SEARCH
The following example command queries for any client events in the last seven days from the node named critproj, associated with the DAILY_INC client schedule:
tsm> query actlog begindate=-7 originator=client node=critproj sched=daily_inc
12-19
Managing Event Logs with the Administration Center
Managing Event Logs with the Administration Center
15
Event Logging, Event Receivers, SNMP Logging, and Tivoli Enterprise Console options can be defined and viewed in the Administration Center, in a servers properties notebook.
12-20
Client Log Files

Client Log Files

dsmsched.log Status information for the Tivoli Storage Manager scheduler service. Information about which schedule runs next and which files are processed. File name can be changed by specifying the schedlogname option in the options file. dsmerror.log Contains information about any errors that occur during processing. errorlogname specifies the fully qualified path and file name of the file where you want to store information about errors that occur during processing. dsmwebcl.log Web client messages are written to the Web client log file, dsmwebcl.log. dsmwebcl.log files reside in the directory you specify with the DSM_LOG environment variable or in the current working directory.
16
12-21
Audit Logs
Audit Logs
Auditlogging and Auditlogname The auditlogging option generates an audit log with an entry for each file that is processed during an incremental, selective, archive, restore, or retrieve operation. The auditlogname option specifies the path and file name where you want to store audit log information. This option applies when audit logging is enabled.
02/02/0818:04:24 ANS1650I Command: sel c:\results\file.txt 02/02/0818:04:24 ANS1651I Backed Up: \\project\c$\results\file.txt 02/02/0818:04:24 ANS1652I Archived: \\project\c$\results\file.txt 02/02/0818:04:24 ANS1653I Updated: \\project\c$\results\file.txt 02/02/0818:04:24 ANS1654E Failed: \\project\c$\results\file.txt 02/02/0818:04:24 ANS1655I Restored: \\project\c$\results\file.txt 02/02/0818:04:24 ANS1656I Retrieved: \\project\c$\results\file.txt 02/02/0818:04:24 ANS1657I Expired: \\project\c$\results\file.txt 02/02/0818:04:24 ANS1658I Deleted: \\project\c$\results\file.txt 02/02/0818:04:24 ANS1659I Skipped: \\project\c$\results\file.txt
17
The audit log can be configured for either basic or full level of information. The example in the slide is the basic level. In addition to all of the events recorded in the basic level, the full level records information for a file that has been excluded or not sent during a progressive incremental backup operation because there was no change in the file. The audit log should not be a substitute for the standard error log (dsmerror.log) or the schedule log (dsmsched.log).
12-22
Unit 12: Monitoring and Event Logging Monitoring and Reporting
Lesson 4: Monitoring and Reporting
Database Reporting
The Select statement can be used to query the Tivoli Storage Manager server database using SQL select statements.
Database Reporting
Some queries require server time and resources and can impact performance.
18
An open database connectivity (ODBC) driver is provided with Tivoli Storage Manager. This driver allows desktop database products such as Lotus Approach or Microsoft Access to be connected to the Tivoli Storage Manager server database. This connection enables administrators to use these tools to perform Tivoli Storage Manager server queries in an easy-to-use graphical manner. You can fill the recovery log if you run a select statement against the backup or archive tables.
12-23
Unit 12: Monitoring and Event Logging Monitoring and Reporting
SQL Select
SQL Select
SQL SELECT Statement Syntax SELECT column_name | aggregate_function [ AS output_column_name ], ... FROM table_name, ... [ WHERE predicate ] [ GROUP BY [table_name.] column_name ] [ HAVING predicate ] [ ORDER BY output_column_name [ ASC | DESC ], ...
19
The simplest form of a select statement is to select all columns from a table. To use the SQL interface, a basic understanding of the SQL select statement is required. The syntax of the TSM select statement is compliant with ANSI SQL syntax but limited from the full specification provided by the SQL92/93 standard. These limitations reduce query complexity and the corresponding load on the Tivoli Storage Manager server database. An SQL select statement can be divided into a number of clauses. Type help select for online assistance.
12-24
Unit 12: Monitoring and Event Logging IBM Tivoli Storage Manager Operational Reporting
Lesson 5: IBM Tivoli Storage Manager Operational Reporting

Introduction to IBM Tivoli Storage Manager Operational Reporting

Operational Reporting automates routine monitoring and reporting tasks to indicate whether a server requires attention.
Operational Reporting focuses on the information available in the TSM database and does not maintain a separate database of information. This makes it very useful for day-to-day operations but not for trending and advanced analysis.
The Operational Reporting application is on a CD shipped with IBM Tivoli Storage Manager code.
20
There is additional information on TSM Operational Reporting on your Student Resources CD.
12-25
Benefits of Operational Reporting

Benefits of Operational Reporting

Operational Reporting provides the following benefits: Easy to install and use. Minimizes the amount of time needed to administer Tivoli Storage Manager. Reports and monitors can be viewed interactively from a Web site or in e-mail. Reports and monitors can be customized and extended. Custom report and monitor templates can be shared. Automatically notifies clients of missed or failed schedules by e-mail.
21
12-26
Operational Reports
Daily Report
22
Backup-Archive Client Summary
23
12-27
Hourly Monitoring
Hourly Monitor
24
Hourly monitoring identifies issues that require attention.
12-28
Automatic Backup Failure Notification

Automatic Backup Failure Notification
Refer to the documentation on your Student Resources CD for more information on Operational Reporting.
25
Administrators or node owners can be notified by desktop message, e-mail, or text message paging when a scheduled backup did not complete (missed or failed). This feature is enabled in the Microsoft Management Console (MMC).
For More Information:

Refer to the presentation entitled TSM OperReports.ppt, TSM Field Guide: A Brief Introduction to IBM Tivoli Storage Manager Operations, and the Redpaper entitled Integrating IBM Tivoli Storage Manager Operational Reporting with Event Management, on your Student Resources CD. This Redpaper outlines how it is possible to integrate management and reporting in IBM Tivoli Storage Manager environments into an enterprise-wide IT monitoring and management solution. It shows how IBM Tivoli Storage Manager Operational Reporting can be used to simplify the monitoring and reporting on the status of TSM environment and how this can be displayed centrally on an enterprise event management console.
12-29
Student Exercise
Student Exercise
26
12-30
Review Questions
1. True or False? The monitoring of client events will only monitor scheduled client activity. 2. True or False? The only client messages that can be logged are those that reflect an error condition. 3. True or False? The activity log is used to store client and server events. 4. True or False? The query actlog command allows you to query a specific node's centrally logged events. 5. True or False? Eligible client and server events can be reported to interfaces external to the Tivoli Storage Manager server. 6. True or False? For a given event the Tivoli Storage Manager administrator has to choose which single event receiver is to receive the event.
Review Answers
1. True or False? The monitoring of client events will only monitor scheduled client activity. false 2. True or False? The only client messages that can be logged are those that reflect an error condition. false 3. True or False? The activity log is used to store client and server events. true 4. True or False? The query actlog command allows you to query a specific node's centrally logged events. true 5. True or False? Eligible client and server events can be reported to interfaces external to the Tivoli Storage Manager server. true 6. True or False? For a given event the Tivoli Storage Manager administrator has to choose which single event receiver is to receive the event. false
12-32
Summary
Summary
Identify client message candidates. Describe client event formatting. Query the activity log for events. Query the event log. Select from summary. Centralize event logging on the TSM server. Create reports with the select statement. Control event logging.
27
12-33
12-34
Appendix A: Additional Product Information
A-1
IBM Tivoli Storage Manager Product Information on the Web

IBM Tivoli Storage Manager Product Information on the Web

http://www-306.ibm.com/software/tivoli/products/storage-mgr/
Once you have reached the Storage and Optimization Web page, you can navigate to specific products, storage solutions, and other links, including IBM TotalStorage solutions. One IBM TotalStorage product that can enhance your storage solution is IBM TotalStorage Productivity Center. The IBM TotalStorage Productivity Center (TPC) includes: IBM TotalStorage Productivity Center for Data (previously known as IBM Tivoli Storage Resource Manager) IBM TotalStorage Productivity Center for Fabric (previously known as IBM Tivoli Storage Area Network Manager) IBM TotalStorage Productivity Center for Disk IBM TotalStorage Productivity Center for Replication
A-2
Optional Products for IBM Tivoli Storage Manager

IBM Tivoli Storage Manager Family of Offerings
IBM Tivoli Storage Manager for Mail IBM Tivoli Storage Manager for Hardware IBM Tivoli Storage Manager for Databases IBM Tivoli Storage Manager for Application Servers IBM Tivoli Storage Manager for Enterprise Resource Planning
The above were previously known as Tivoli Data Protection agents, or TDPs.
IBM Tivoli Storage Manager for System Backup and Recovery

Previously known as Tivoli SysBack.

IBM offers a variety of data protection products (Tivoli Data Protection or TDP) that work with IBM Tivoli Storage Manager to protect enterprise data. IBM Tivoli Storage Manager for Mail is a software module for IBM Tivoli Storage Manager that automates the data protection of e-mail servers running either Lotus Domino or Microsoft Exchange. This module utilizes the application program interfaces (APIs) provided by e-mail application vendors to perform online hot backups without shutting down the e-mail server and improves data restore performance. IBM Tivoli Storage Manager for Hardware improves the data protection of your business-critical databases and Enterprise Resource Planning (ERP) applications that require 24-hour by 365-day availability. This software module helps IBM Tivoli Storage Manager and its other data protection modules perform high-efficiency data backups and archives of your most business-critical applications. These operations are performed with minimal impact on database or ERP servers. IBM Tivoli Storage Manager for Databases is a software module that works with IBM Tivoli Storage Manager to exploits the backup-certified utilities and interfaces provided for Oracle, Microsoft SQL Server, and Informix.Tivoli Storage Manager for Databases in conjunction with Tivoli Storage Manager automates data protection tasks. Database servers can continue running their primary applications while they back up and restore data to and from offline storage.
A-3
IBM Tivoli Storage Manager for Application Servers is a software module that works with IBM Tivoli Storage Manager to better protect the infrastructure and application data and improve the availability of WebSphere Application Servers. It works with the WebSphere Application Server software to provide an applet GUI to do reproducible, automated online backup of a WebSphere Application Server environment, including the WebSphere administration database (DB2 Universal Database), configuration data, and deployed application program files. Specifically designed and optimized for the SAP R/3 environment, IBM Tivoli Storage Manager for Enterprise Resource Planning (ERP). Provides automated data protection Reduces the CPU performance impact of data backups and restores on the R/3 server Reduces the administrative workload necessary to meet data protection requirements Is built on the SAP database Includes a set of database administration functions integrated with R/3 for database control and administration
These topics are covered in the IBM Tivoli Storage Manager 5.5 Advanced Administration, Tuning, and Troubleshooting course (see the IBM Tivoli Storage Manager curriculum roadmap).
A-4
Bare Machine Recovery

Bare Machine Recovery

To assist with recovery from a catastrophic system or hardware failure, there are three applications IBM Tivoli Storage Manager uses for a comprehensive Bare Machine Recovery (BMR) solution.
IBM Tivoli Storage Manager for System Backup and Recovery (Tivoli SysBack) for AIX and Solaris
Cristie Bare Machine Recovery for Windows, Linux, HP, and Solaris (go to www.cristie.com for supported platforms)
Windows Automated System Recovery (ASR) for Windows XP or 2003
This topic is covered in the IBM Tivoli Storage Manager 5.5 Extended Edition Disaster Recovery course (see the IBM Tivoli Storage Manager curriculum roadmap).
A-5


File retention helps meet legal regulatory requirements.
IBM System Storage Archive Manager is a dedicated Tivoli Storage Manager server that is modified to provide: Archive retention protection Event-based retention policy Deletion hold and release capability Explicit data interface from content management programs IBM DR550 hardware is supported IBM System Storage Archive Manager is a Separately licensed feature.

5
IBM System Archive Storage Manager facilitates compliance with the most stringent regulatory requirements in the most flexible and function-rich manner. It helps manage and simplify the retrieval of the ever-increasing amount of data that organizations must retain for strict records retention regulations. Many of the regulations demand the archiving of records, e-mails, design documents, and other data for many years, in addition to requiring that the data is not changed or deleted. This topic is covered in Chapter 4 of the Understanding the IBM TotalStorage DR550 RedBook, on your Student Resources CD.
A-6
Optional Additions to IBM Tivoli Storage Manager

Optional Additions to Tivoli Storage Manager

IBM Tivoli Storage Manager Extended Edition
Hierarchical Storage Management (HSM) Products: IBM Tivoli Storage Manager for Space Management IBM Tivoli Storage Manager HSM for Windows
Complementary Products: IBM Tivoli Storage Manager for Storage Area Networks Tivoli Continuous Data Protection (CDP) for Files
A-7
Hierarchical Storage Management
Hierarchical Storage Management or HSM

Hierarchical Storage Management (HSM) migrates files from your local file system to storage, and then recalls the files as needed.
Migrating files to a distributed storage device takes advantage of lowercost storage resources that are available in your network environment for infrequently used files, thus allowing more free space on your local system.
IBM Tivoli Storage Manager supports: IBM Tivoli Storage Manager for Space Management (for UNIX) IBM Tivoli Storage Manager HSM for Windows
A-8
IBM Tivoli Storage Manager for Space Management

IBM Tivoli Storage Manager for Space Management

TSM Server TSM UNIX Client
/ storage pool data /usr /data
migrate recall
8
IBM Tivoli Storage Manager for Space Management frees administrators and users from manual file system pruning tasks and defers the need to purchase additional disk storage by automatically and transparently migrating rarely accessed files to Tivoli Storage Manager storage while the files most frequently used remain in the local file system.
A-9
IBM Tivoli Storage Manager HSM for Windows

IBM Tivoli Storage Manager HSM for Windows

TSM Windows Client
TSM Server
storage pool data
data
migrate recall
9
IBM Tivoli Storage Manager Hierarchical Storage Management for Windows helps you control runaway storage growth by facilitating the movement of inactive Windows files to cost-appropriate media. Because it is a policy-based management system, you can specify the criteria. For example, you can select files based on the last date the file was accessed or modified, or the file type. Your selection determines where files are stored. As a result, the solution helps you maximize the cost-effectiveness of your storage devices while supporting your business priorities. With Tivoli Storage Manager HSM for Windows, you can automatically migrate individual files, parts of Windows file system, or complete file systems to an IBM Tivoli Storage Manager server. To the data owners, migrated files appear on the local file system as they did before they were migrated, but they occupy less disk space on the local file system. You can access, open and update these migrated files just as you would any other file.
A-10
IBM Tivoli Storage Manager for Storage Area Networks

IBM Tivoli Storage Manager for Storage Area Networks

TSM Server Tape or Disk Library
LAN (client metadata)
SAN (client data)
TSM Clients, with the Storage Agent installed
LAN-free backups and restores use storage area networks (SANs) for data movement between clients and the server, decreasing the network traffic on the local area network (LAN). Shared storage resources (disk, tape) are accessible to both the client and the server over the SAN.
10
The IBM Tivoli Storage Manager for Storage Area Networks extension allows SANconnected Tivoli Storage Manager servers and Tivoli Storage Manager backup-archive client computers to make maximum use of their direct network connection to storage. This software extension allows both servers and client computers to make the bulk of their backup-restore and archive-retrieve data transfers over the SAN instead of the LAN, either directly to tape or to the Tivoli Storage Manager disk storage pool. This ability greatly reduces the performance impact of data protection on the LAN while also reducing CPU utilization on both client and server.
A-11
Continuous Data Protection

What is Tivoli Continuous Data Protection (CDP) for Files?

IBM Continuous Data Protection (CDP) for Files is an integrated recovery solution that provides complete data protection in case of corruption, user error, virus, or system failure. Tivoli CDP for Files installs and configures in minutes, and runs in the background.
Replication
Disk-to-disk duplication Fast Real-time for high-importance files Tolerant of transient networks Multiple targets
Traditional Backup
Versioning of files Point-in-time restore Central administration Archiving (vaulting) Retention Highly scalable
11
With Tivoli Continuous Data Protection for Files, you can specify as many as three target backup or replication areas for: High-priority files Local disk File server Network-attached storage (NAS) appliance IBM Tivoli Storage Manager server
These areas will capture every save of a file when it occurs to help protect against corruption, file loss, or system loss.
A-12
Appendix B:Problem Determination
B-1
Resolving Problems with Features
TSM Features Address Problems
Sometimes a problem can be resolved by evoking features of IBM Tivoli Storage Manager.
The TSM Development teams have addressed what were once common problems for storage administrators and created features and options to make it easier to protect your data.
Some performance situations can be addressed with TSM features. The following charts examine a few of the features and how they can resolve performance issues.
B-2
Mapping TSM Solutions to Common Problems

Feature
Active-Data Pools Administrator Center Backup Sets
Description
Storage pools defined to contain only active data. Task-orientated interface to manage one or more Tivoli Storage Manager servers. Collection of backed up files, stored as a single object on specific media.
Solution Provided
Reduces restore times and storage requirements. Centralized management of enterprise systems. Can be used for client restore without network or server.
Client Option Sets Collocation
system command line, type DSM to start the GUI. A collection of client options that can be applied Sets options for groups of
to multiple clients. Enables the server to keep all files belonging to a client node or a client file space on a minimal number of sequential access storage volumes. Allows creation of a group of nodes for collocation. Tapeless backups use disks as storage media. Part of the Administration Center, which is used to monitor system status. clients. Reduces restore times.
Collocation Groups Disk-to-Disk Backup Health Monitor
Does not require a tape for every node. Faster restore time. Minimized fragmentation, utilizes inexpensive disks. Centralized monitoring of storage tasks. 3
Mapping TSM Solutions to Common Problems

Feature
Include-Exclude Migration of Files in a Storage Pool Hierarchy Online Image Backup
Description
Lists that customize which files are considered for backup or archive. Automatic migration to the next storage pool in the hierarchy maintains free space in the primary storage pool. Creates a point-in-time image backup, or
Solution Provided
Does not use space or time on files which do not require protection. Ensures sufficient space in the faster storage pools at the top of the storage pool hierarchy. Allows other applications to
system command line, DSM the GUI. and changing continue accessing snapshot, at the volume level,type in which the to start
volume remains in an available state during the backup. The backup-archive client delays the start of the volume snapshot until volume activity is idle for a specified amount of time, thus allowing for a more stable snapshot. the contents of the volume during backup.
Progressive Backup Methodology Reclamation
Only files that have changed are candidates to be backed up (incremental backups).
Reduces network traffic and improves processor utilization by minimizing data transfer time. More efficient use of storage space. Efficient tape utilization and reduced restore times (fewer tapes). 4
As data expires and leaves unused space on the tape, the remaining data can be moved, allowing the empty space to be reused.
B-3
Problem Determination
Problem Determination Objectives

To be successful, you should:
Learn the steps for problem determination when the TSM server has experienced a failure. Understand how the suggestions made for volume placement, mirroring, and backup of TSM provide for TSM recovery. Learn how to manually recover the TSM server in the event of a catastrophic failure. Disaster Recovery Manager can automate this process; an instructor-led class is available. Understand how to recover in the event of database failure, data corruption on a volume, or volume destruction.
Steps for Problem Determination

Consider these questions while diagnosing a problem:
What is the problem? Where did it occur? When did it begin? What action was being performed? Were any messages issued? How frequently does the error occur?
??
6
Follow these steps:

Verify that devices are still accessible to the system and to TSM. Search the online Knowledge Base at IBM.com to match error messages or problem descriptions. Test other operations to better determine the scope and impact of the problem. Testing may also help determine if a specific sequence of events causes the problem.
B-4
Diagnosing the Problem

Considerations when Diagnosing the Problem

There are many areas to look at when a problem occurs. Movement of data starts at the disk on the client and moves to either a disk or tape media on the server. Data moves through many components (clients, networks, servers, and storage devices). Bottlenecks can occur in any of these components. Points of consideration:
Drivers Adapters Network issues Memory Routers Other applications
7
Diagnosing a Client Problem

Examine any error messages that were issued. Examine the server activity log messages for this session. Is this an error in communicating with the server? Were client options changed? Were policy settings changed on the server? Is the client being run with the QUIET option? Verify INCLUDE-EXCLUDE syntax and ordering. Was this the correct TSM server? Identify when and where the problem occurs. If the problem can be duplicated, try to minimize the circumstances under which it can occur. Collect documentation.
8
B-5
Diagnosing the Problem, continued

Diagnosing a Server Problem

Check the server activity log. Check HELP for TSM messages issued for the problem. Can the problem be duplicated? Is the problem an error in reading or writing to a device? Have any server options or settings been changed? Did a scheduled client operation fail? Did the server run out of space? Are connections by clients or administrators failing? Collect documentation.
Hints and Tips for Libraries, Drives and Device Drivers Problem Diagnoses
Has the operating system changed? Has the host bus adapter (HBA) or SCSI adapter connecting to the device been changed, updated, or replaced? Has the adapter firmware changed? Has the cabling between the computer and device changed? Are any of the cable connections loose? Has the device firmware changed? Are there error messages in the system error log for this device? Has a device driver changed?
10
B-6
TSM Problem Determination Guide

The TSM Problem Determination Guide is full of very helpful information, which may provide answers to questions you have about TSM. You may be able to avoid having to call support if you refer to this guide first.
TSM Problem Determination Guide
11
B-7
Diagnosing a Problem Sample Page
12
B-8
What To Do before Calling Support

What to Do before Calling Support

Review logs: ACTLOG EVENTLOG DSMERROR.LOG DSMSCHED.LOG Review the documentation for your operating system. Review the Problem Determination Guide. Check the IBM Tivoli Storage Manager Knowledge Base on the Web:
www.ibm.com/software/sysmgmt/products/support
Issue the query systeminfo command, when instructed by TSM Support, and review the output file. If you still need to call support, they will direct you in what information needs to be gathered. Use caution when issuing traces. Trace functions can require a lot of time and system resources.
13
Information to Gather for Support

Have the following information ready when you report a problem: The Tivoli Storage Manager server version, release, modification, and service level number. You can get this information by entering the query status command at the Tivoli Storage Manager command line. The Tivoli Storage Manager client version, release, modification, and service level number. You can get this information by entering dsmc at the command line. The communication protocol (for example, TCP/IP), version, and release number that you are using. The activity that you were doing when the problem occurred, listing the steps that you followed before the problem occurred. A description of the symptom or error encountered. The exact text of any error messages relating to the symptom or error encountered. Error logs or other related documentation for the problem. Use the query actlog server command and collect the server activity log messages starting 30 minutes prior to the problem until 30 minutes after the problem.
14
B-9
Reporting a Problem
You can contact IBM Customer Support in one of the following ways: Visit the Tivoli Storage Manager technical support Web site. Submit a problem management record (PMR) electronically at IBMLink. Submit a problem management record (PMR) electronically at IBM Software Support. Customers in the United States can call 1-800-IBM-SERV (1-800-426-7378). International customers should consult the Web site for customer support telephone numbers. Hearing-impaired customers should visit the TDD/TTY Voice Relay Services and Accessibility Center Web site. You can also review the IBM Software Support Guide. When you contact IBM Software Support, be prepared to provide identification information for your company so that support personnel can readily assist you. Company identification information is needed to register for online support available on the Web site.
15
Additional Resources for TSM

Additional Resources for TSM

Education Documentation shipped with Tivoli Storage Manager Other Publications IBM Web sites User Groups Welcome to TSM Training.
16
B-10
Education
Education
The following slides show the IBM Tivoli Storage Manager 5.5 Curriculum Roadmap, which shows the courses in the order they should be taken. Check the IBM Web site for the availability of the courses. From the IBM home page, select: Welcome Training to TSM Tivoli Training. Storage and Optimization
17
Where to Find More Information: Training Web Page http://www.ibm.com/software/tivoli/education/
18
B-11
Product Documentation
Documentation Included with IBM Tivoli Storage Manager 5.5

The publications shipped with IBM Tivoli Storage Manager 5.5 are also available on the IBM Web site. For your convenience, the publications for AIX and Windows have been included on your Student Resources CD, as well.
Also included on your Student Resources CD:

Windows and AIX User Guides RedBooks and RedPapers Problem Determination Guide Performance and Tuning Guide Operational Reporting presentation Database, policy and storage pool planning forms Technical Field Guides
19
B-12
Documentation on www.ibm.com
Documentation on www.ibm.com
http://publib.boulder.ibm.com/infocenter/tivihelp/index.jsp
20
Product Manuals on the Web
Product Manuals on the Web
21
B-13
Other Publications and Product Web Sites
Other Publications
RedBooks: http://www.redbooks.ibm.com/ Search for Tivoli Storage
Start with this RedBook: IBM Tivoli Storage Management Concepts
Tivoli Field Guides:

http://www.ibm.com/software/sysmgmt/products/support/Field_Guides.html
22
TSM Information on the Web

The product Web site: www.ibm.com/software/tivoli/products/storage-mgr/
IBM Tivoli Storage Manager Knowledge Base Web site: www.ibm.com/software/sysmgmt/products/support Other useful Web sites (these forums are not maintained by IBM): www.adsm.org and http://search.adsm.org
23
B-14
TSM Support Web Page
Tivoli Support Web Page

http://www.ibm.com/software/sysmgmt/products/support/IBMTivoliStorage ManagerExtendedEdition.html
24
IBM Support Assistant
IBM Support Assistant (ISA) is available in the download section at the TSM Support page: http://www.ibm.com/software/sysmgmt/products/support/IBMTivoliStorageManager.html
25
B-15
Additional Assistance
TSM Basic Concepts Poster

Free IBM Tivoli Storage Manager Concepts Poster Version 5.3.2 (SC32-9464-00) Orderable from the IBM Web site. Go to: Software > Tivoli > Solutions > Storage and Optimization.
26
User Groups
www.tivoli-ug.org
27
B-16

As an individual, becoming a Tivoli Certified Professional has helped me to progress further in my career and gain job satisfaction. To the company, it has helped build up the confidence and trust to the customer. At the end of the day, you win, the company wins, and the customer wins.
Special Offer For Having Taken This Course

For having completed this course, you are entitled to a 15% discount on your next exam at any Thomson Prometric or Pearson VUE testing center. Use this special promotion code when registering online or by phone to get the discount: 15CSWR. (This offer may be withdrawn. Please check with the testing center as described later in this section.)
Why Get Certified?

It is a demonstration of value to your customer through increased overall performance with shorter time cycles to deliver applications. Technical certifications assist technical professionals to obtain more visibility to potential customers. In tough economic times it is good to be able to make yourself stand out from your competition.
What Is Role-based Certification?

All IBM certifications are based on job roles. They focus on a job a person must do with a product, not just the products features and functions. The two primary job roles used by Tivoli Professional Certification are the IBM Certified Deployment Professional and the IBM Certified Advanced Deployment Professional.
When Should I Attempt a Certification Exam?

After completing this course, you should review the test objectives and sample test on the IBM Certification Web site (URL follows) that correspond with the exam you wish to take. A general guideline is to play a major role in at least two product deployments, getting as much hands-on experience working with the product as possible before you attempt the exam. Exam questions are written by experts in the deployment of this product and most of the material covered is taken from their experience working with the product in real world commercial environments. You will find supplemental readings and other study material on the Web site as well.
Where Can I Take a Certification Exam and How Much Do They Cost?
All IBM certification exams are available at Thomson Prometric and Pearson VUE testing centers worldwide. In addition, testing is offered at a discount or for free at many IBM conferences and events, including many Tivoli User Group (TUG) meetings. Exam costs vary from country to country. Please see the Thomson Prometric or Pearson VUE Web sites for the exact cost at the testing center you plan to use.
Where Can I Get More Information?

The Tivoli Certification Program http://www.ibm.com/certify/ or contact us at certify@us.ibm.com Tivoli Certification Study Guides http://www.redbooks.ibm.com (search for certification study guide) Tivoli Support Technical Exchange Calls http://www.ibm.com/software/sysmgmt/products/support/supp_tech_exch.html Tivoli Certification Study Groups Send an e-mail inquiry to tivcert@us.ibm.com Thomson Prometric testing centers http://www.prometric.com Pearson VUE testing centers http://www.vue.com/ibm/
II
Notes:
IBM Ticoli Storage Manager 5.5 Implementation and Administration
-1
S150-2877-00
March 2008
Printed in Ireland
S150-2877-00
CT4SYEN

TM 5021 Inst

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

TM 5021 Inst

Uploaded by

Copyright:

Available Formats

IBM Tivoli Storage Manager 5.

5 Implementation and Administration

Course Revision History

General Revisions to this Course

Students Training Guide

Course Revision History

Instructors Training Guide

Unit 5: Managing Storage Pools and Storage Pool Volumes

Query OCCupancy command added

Unit 6: Policy Management

IBM Tivoli Storage Manager 5.5 Implementation and Administration

Copyright IBM Corp. 2008

Course Revision History

Changes from TSM 5.4 Implementation and Administration, Part One

Unit 9: Backup-Archive Client Functions

Unit 10: Protecting the Database and Storage Pools

Auditlogging and auditlogname options added.

Copyright IBM Corp. 2008

IBM Tivoli Storage Manager 5.5 Implementation and Administration

Course Revision History

Part Number S150-2878-00 S150-2877-00 S150-2875-00

S150-2386-00 S150-2388-00 S150-2385-00

IBM Tivoli Storage Manager 5.5 Implementation and Administration

Copyright IBM Corp. 2008

Classroom Setup Instructions

IBM Tivoli Storage Manager 5.5 Implementation and Administration

Copyright IBM Corp. 2008

* The appendices can be reduced or expanded to fit the remaining time.

Copyright IBM Corp. 2008

IBM Tivoli Storage Manager 5.5 Implementation and Administration

Suggestions for Delivery

IBM Tivoli Storage Manager 5.5 Implementation and Administration

Copyright IBM Corp. 2008

Altering the Flow of the Course

Copyright IBM Corp. 2008

IBM Tivoli Storage Manager 5.5 Implementation and Administration

IBM Tivoli Storage Manager 5.5 Implementation and Administration

Copyright IBM Corp. 2008

Copyright IBM Corp. 2008

TSM System Requirements

To determine JRE level, type java fullversion at OS prompt.

Copyright IBM Corp. 2008

Topic ISC, Administration Center Introduction

Navigating the Administration Center

Appendix B has tips on what to do before calling IBM Support.

At this point, you enter TSM.

The dsmcad process must be started (dsm or dsmj on UNIX).

Copyright IBM Corp. 2008

Copyright IBM Corp. 2008

Many libraries can automatically detect the element number.

Working with Media

Copyright IBM Corp. 2008

Defining Storage Pools

Deleting Storage Pools and Volumes Move Data

Use the parameter reconstruct=yes with aggregates.

Concurrent Storage Pool Volume Access Automatic data Movement

Single Drive Reclamation Collocation Example

Copyright IBM Corp. 2008

Created automatically when you use the Administration Center.

Include-Exclude is covered in Unit 8.

Copyright IBM Corp. 2008

Validate and Activate Policy Set

Copyright IBM Corp. 2008