Table of Contents

Introduction to Tivoli Storage Manager......................................................................................
Introduction...................................................................................................................... 5
Objectives........................................................................................................................ 5
IBM Tivoli Storage Manager.............................................................................................5
TSM platform support....................................................................................................... 5
IBM Tivoli Storage Manager.............................................................................................6
Backup /Restore............................................................................................................... 6
Archive/Restore – Long Term Storage Functionality........................................................7
Tivoli Storage Manager Products.....................................................................................8
Installing Tivoli Storage Manager on AIX..........................................................................9
Prerequisites Required by the ITSM Server.....................................................................9
Basic Components Installed by IBM Tivoli Storage Manager.........................................10
Install IBM Tivoli Storage Manager License on AIX........................................................11
Registering and Querying Licenses from the Command Line.........................................11
Backup/Archive Client Prerequisites..............................................................................12
Backup archive client Installation Steps.........................................................................13

Install and Configure Tape Library Attached to the IBM Tivoli Storage Manager Server
......................................................................................................................................................
Introduction..................................................................................................................... 15
Objective........................................................................................................................ 15
Install and Configure Tape Library Attached to the IBM Tivoli Storage Manager Server.15
Prepare Tape Cartridges for Use in an IBM Tivoli Storage Manager Tape Library.........17
Checking in Volumes...................................................................................................... 18
Create Scratch Tapes by Using the LABEL LIBV Command..........................................19
Checking Out Volumes................................................................................................... 19
Auditing a Library........................................................................................................... 20

Managing Storage Pools and Storage Pool Volumes..............................................................
Introduction..................................................................................................................... 22
Objectives....................................................................................................................... 22
Storage Pools, Storage Pool Hierarchies & Storage Pool Volumes...............................22
Storage Pool Hierarchies............................................................................................... 23
Device Classes............................................................................................................... 23
Device Class and Storage Pool......................................................................................25
Defining Storage pools................................................................................................... 25
Update / query storage pools......................................................................................... 26
Defining storage pool volumes.......................................................................................26
Deleting Storage Pools and Volumes.............................................................................26
Automatic Data Movement............................................................................................. 27
Storage Pool Migration................................................................................................... 28
Reclamation................................................................................................................... 29
Collocation...................................................................................................................... 30

Scheduler....................................................................................................................................
Introduction..................................................................................................................... 32
Objectives....................................................................................................................... 32
Overview of Schedules................................................................................................... 32
Central Scheduling Mode - Client Polling.......................................................................33
Central Schedule Mode - Server Prompted....................................................................33
Selecting Schedule Methods.......................................................................................... 34
Additional Scheduling options........................................................................................ 35
Additional Client Polling Options....................................................................................35
Additional Server Prompted Options..............................................................................36
Identify Tasks/Actions that can be Scheduled for Clients...............................................37
Consistent Client Return Codes.....................................................................................38
Managing Client/Server Sessions..................................................................................38

Maples ESM Technologies Ltd 1

Defining Schedules........................................................................................................ 39
Using Command Line to define the schedule.................................................................40
Schedule Example......................................................................................................... 40
Using Commandline to define Association.....................................................................41

Client Configuration...................................................................................................................
Introduction..................................................................................................................... 43
Objectives....................................................................................................................... 43
Identify the types of Clients............................................................................................ 43
Using the command line................................................................................................. 43
Using the web client....................................................................................................... 44
Using GUI....................................................................................................................... 44
Administrative Control of Access....................................................................................44
Configuring Client Access to Server...............................................................................45
Define include/exclude option......................................................................................... 47
Include/exclude processing............................................................................................ 47

Backup-Archive Client Functions.............................................................................................
Introduction..................................................................................................................... 50
Objectives....................................................................................................................... 50
Types of Backups Available from the GUI......................................................................50
Incremental (Complete) and Journal-based Backup......................................................50
Journal-based Backup.................................................................................................... 51
Incremental by date (only).............................................................................................. 52
Incremental (without journal).......................................................................................... 53
Always backup selective................................................................................................ 54
Snapshot image backup................................................................................................. 55
Restore operation........................................................................................................... 55
Point-in-time restore....................................................................................................... 56
Archive Process............................................................................................................. 56

Policy Management....................................................................................................................
Introduction..................................................................................................................... 58
Objectives....................................................................................................................... 58
Policy Management........................................................................................................ 58
Policy Specification........................................................................................................ 58
Copy Group Attributes.................................................................................................... 61
Policy set........................................................................................................................ 61
Command line to define policy set..................................................................................62
Validating a policy set..................................................................................................... 62
Management class......................................................................................................... 63
How are files bound to management class.....................................................................63

Privilege classes.........................................................................................................................
System privileges........................................................................................................... 66
Storage privileges........................................................................................................... 67
Unrestricted Storage Privileges......................................................................................68
Restricted Storage Privilege........................................................................................... 68
Policy Privileges............................................................................................................. 68
Operator privilege........................................................................................................... 69
Analyst privilege............................................................................................................. 69

Database & Recovery Log..........................................................................................................
Introduction..................................................................................................................... 72
Objectives....................................................................................................................... 72
Database and Recovery Log.......................................................................................... 72
Transactions................................................................................................................... 73
Recovery Log Transaction Modes..................................................................................74
Normal Mode.................................................................................................................. 74
Roll Forward Mode......................................................................................................... 75

Maples ESM Technologies Ltd 2

Space Allocation............................................................................................................. 75
Database and Recovery Log Space...............................................................................76
Estimating the size of the database................................................................................76
Cached and copy Storage pool sizes.............................................................................77
Overhead....................................................................................................................... 78
Estimating the Size of the Recovery Log........................................................................79
Reducing the Database and Recovery Log Space.........................................................79

Monitoring and Logging Events................................................................................................
Introduction..................................................................................................................... 82
Objectives....................................................................................................................... 82
Monitoring and Logging Events......................................................................................82
Client Message Candidates............................................................................................ 83
Client Event Formatting.................................................................................................. 84
Message Formatting....................................................................................................... 84
Client Event Processing................................................................................................. 85
Enabling Client Events for the Storage manager console..............................................86
Storing Clients in the Activity Log...................................................................................87
Querying Client Events in the Activity Log......................................................................88

Backing up the database............................................................................................................
Introduction..................................................................................................................... 90
Objectives....................................................................................................................... 90
Backing up the database................................................................................................ 90
Full Backup versus Incremental Backup........................................................................91
Database (out-of-band) snapshot Backup......................................................................91
Database Backup Command.......................................................................................... 92
Database Backup Related Commands..........................................................................93
QUERY DB..................................................................................................................... 93
QUERY VOLHISTORY................................................................................................... 93
DELETE VOLHISTORY................................................................................................. 94

Maples ESM Technologies Ltd 3

Introduction to Tivoli Storage Manager Maples ESM Technologies Ltd 4 .

disaster planning and recovery. TSM automates storage management tasks by eliminating labor and cost intensive manual procedures for backup. WAN. solution scalability. you will be able to identify  How IBM Tivoli Storage Manager serves as a tool for data management and protection. and impact the overall infrastructure as well as individual mission-critical applications. The TSM server software provides built-in device drivers for directly connecting more than 300 different device types from every major manufacturer. TSM facilitates flexible and scalable storage management policies to support complicated business needs for storage management and disaster recovery. All common LAN. and recovery. Most importantly.Introduction to Tivoli Storage Manager Introduction This unit provides an introduction to IBM Tivoli Storage Manager and describes the major functions and features that are currently available. space management.  Major components of the IBM Tivoli Storage Manager solution  IBM Tivoli Data Protection products that are part of the IBM Tivoli Storage Manager solution IBM Tivoli Storage Manager Today’s storage management needs go beyond traditional backup and recovery solutions. and optical storage devices. tape. Data is the currency of today's e-business economy. and it supports hundreds of disk. disaster recovery. archive. TSM provides an enterprise solution for data protection. The TSM server application is supported on over 10 platforms. and record retention. Objectives On the completion of this unit. IBM Tivoli Storage Manager (TSM) is a storage management application built for the enterprise. TSM platform support TSM protects and manages data on more than 30 operating platforms. Maples ESM Technologies Ltd 5 . and planning to store this data needs to encompass data reliability. and SAN infrastructures are also supported by TSM.

smart-data-move and store techniques and comprehensive policy-based automation all work together to minimize data protection administration costs and the impact to both computers and networks.IBM Tivoli Storage Manager  Stores backup and archive copies of data on offline storage  Scales to protect hundreds of computers running a dozen operating systems  Provides intelligent data move and store techniques  Allows business critical applications that run 24x365 to use data protection with no interruption in service IBM Tivoli Storage Manager protects your organization’s data from hardware failures and other errors by storing backup and archive copies of data on offsite storage. Scaling to protect hundreds of computers running a dozen OS ranging from laptops to mainframes and connected together via the internet. Optional modules allow business-critical applications that must run 24x365 to utilize Storage Manager’s centralized data protection with no interruption to their service Tivoli Storage Manager Products Figure 3 Maples ESM Technologies Ltd 6 . WANs or LANs. Storage Manager’s centralized Web- based management.

Tivoli Storage Manager for Databases exploits the backup-certified utilities and interfaces provided for Oracle. IBM Tivoli Storage Manager for ERP specifically designed and optimized for the SAP R/3 environment provides automated data protection. Maples ESM Technologies Ltd 7 . This ability greatly reduces the performance impact of data protection on the LAN while also reducing CPU utilization on both client and server. reduces the CPU performance impact of data backups and restores on the R/3 server. this module automates data protection tasks and allows database servers to continue running their primary applications while they backup and restore data to and from offline storage. Tivoli Storage Manager for ERP builds on the SAP database. by automatically and transparently migrating rarely accessed files to Storage Device. 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 Databases is a software module that works with IBM Tivoli Storage Manager to protect a wide range of application data via the protection of the underlying databases management systems holding that data. It works with the WebSphere Application Server software to provide an applet GUI to do reproducible. 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. automated online backup of a WebSphere Application Server environment. and greatly reduces the administrator workload necessary to meet data protection requirements. configuration data. including the WebSphere administration database (DB2 Universal Database). 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. In conjunction with Tivoli Storage Manager. This software module helps IBM Tivoli Storage Manager and its other data protection modules to perform high- efficiency data backups and archives of your most business-critical applications while eliminating nearly all performance impact on database or ERP servers. and deployed application program files. a set of database administration functions integrated with R/3 for database control and administration. IBM Tivoli Storage Manager for Hardware improves the data protection of your business- critical databases and ERP applications that require 24x365 availability. 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. either directly to tape or to the Storage Manager Disk storage pool. Microsoft SQL Server. and Informix. while the files most frequently used remain in the local file system. The IBM Tivoli Storage Manager for Storage Area Networks extension allows SAN- connected Storage Manager Servers and Storage Manager Client computers to make maximum use of their direct network connection to storage. and defers the need to purchase additional disk storage. IBM Tivoli Storage Manager for Space Management frees administrators and users from manual file system pruning tasks.

In the unlikely event of an IBM Tivoli Storage Manager Database recovery. and retention period can be assigned at the individual file level and stored in the database. TSM DATABASE AND RECOVERY LOG The specially designed IBM Tivoli Storage Manager database retains information about all client system and user files. operators can restore the database to the exact point of a failure by rolling the recovery log forward after restoring from the latest database backup. which means data that describes data. the database uses a recovery log to roll back any changes made if a storage transaction is interrupted before it completes. To maintain data integrity. disaster recovery. Also.TSM Concepts: IBM Tivoli Storage Manager is implemented as a client-server software application consisting of an IBM Tivoli Storage Manager server software component. and the scheduling of client and administrative tasks. PROGRESSIVE BACKUP METHODOLOGY Maples ESM Technologies Ltd 8 . and other complementary IBM Tivoli and vendor software products. IBM Tivoli Storage Manager Backup-Archive client. Client data attributes such as storage destination. providing automatic volume switching after a media failure. The flexibility of the IBM Tivoli Storage Manager database enables customers to define storage management policies around business needs for individual clients or groups of clients. The IBM Tivoli Storage Manager database also ensures reliable storage management processes. number of versions. both the IBM Tivoli Storage Manager Database and recovery log can be mirrored for availability. This is known as a two-phase commit. business policies. This database retains information called metadata.

Figure Saves time and disk space by backing up only new files and modified files. in comparison with other methods such as Full+Incremental or Full+Differential backup schemes. Traditional Backup Methods Full + Incremental Figure Full + Differential Figure Progressive Backup Methodology IBM Tivoli Storage Manager’s file-level progressive backup methodology. wasting both network and media resources. followed by regular incremental or differential backups (usually once a day). to recover the latest version of a file or an entire system. The progressive backup feature uses its own relational database to track data wherever it is stored. IBM Tivoli Storage Manager maintains a pointer in its database to the latest version of each file for each client. The reorganization of the physical storage media to store each client’s data Maples ESM Technologies Ltd 9 . This eliminates the need for base-plus-incrementals tapes. The multistep restore process of such products requires restoration of the last full backup. creating a full backup.The IBM Tivoli Storage Manager architecture uses an intelligent backup methodology that provides efficiencies during both the backup and restoration of client data. along with more-recent incremental or differential backups. During the initial client backup. IBM Tivoli Storage Manager backs up all eligible files. Subsequently. and then additional periodic full backups (usually once a week). prevents unnecessary backups of unchanged data to reduce and consolidate the recovery tape-set. It also offers a more efficient use of storage resources by not storing redundant data and a faster recovery by not restoring multiple versions of the same file. commonly used for restore procedures in other storage management products. This less-efficient backup method results in redundant weekly full backups of files that have not changed. eliminating the need for another full backup to consolidate the files into a single image. Other backup products require an initial full backup. delivering direct one-step file restore. files are backed up again only if they are new or have changed since the last backup.

This copy of the file is known as the ACTIVE version. This may be set at a specific number or to UNLIMITED. ACTIVE AND INACTIVE FILE VERSIONS: One of the most important concepts in IBM Tivoli Storage Manager data management is the difference between an active backup version and an inactive backup version.physically together on a small number of media — in order to provide faster access in the case of a complete system recovery — is done transparent to the client and is completely automated on the server using data metainformation stored in the server database.). meaning they will never be expired Important: An ACTIVE file version is never expired. This version now becomes the ACTIVE version and the copy from Monday becomes an INACTIVE. This parameter controls how long to retain all remaining inactive files and may be set at a specific number of days or to NOLIMIT. If it has. the oldest INACTIVE version is deleted from IBM Tivoli Storage Manager storage and will no longer be able to be restored. Monday at 9 p. _ How long to keep: The RETEXTRA parameter controls how much time must elapse before an INACTIVE file version is considered expired. The most recent backed-up version of the file is always the ACTIVE version. IBM Tivoli Storage Manager will keep storing a new ACTIVE version and inactivating the previous active version. IBM Tivoli Storage Manager will keep this file version indefinitely When the file is deleted: Maples ESM Technologies Ltd 10 . IBM Tivoli Storage Manager uses this ACTIVE version already stored to check back with your workstation to determine whether the file has changed since the last backup. IBM Tivoli Storage Manager server stores this file. Even if you never change a particular file after the first incremental backup. IBM Tivoli Storage Manager controls the retention of its ACTIVE and INACTIVE versions of a file that exist on a client machine by using two criteria defined in the Management Class: _ How many versions: The parameter that controls the number of backup versions is called VEREXIST. When you run an incremental backup again (say. it is backed up again. Once this limit is exceeded. The next time you run a backup operation (say. Tuesday at 9 p.). up to the limit of the total number of versions defined to be retained in the management class.m. When the file exists in the client: Assume a new file is created on your workstation. as long as it still exists on the original client.m.

Typically. you can configure IBM Tivoli Storage Manager to manage the last inactive copy differently. the backup procedure had four versions of the same file (January 22 being the active and most recent copy. All stored versions of the file now automatically become INACTIVE. It may be set at a specific number of days or to NOLIMIT. so that you can keep that file for a longer period of time. when the next incremental backup is run. an ACTIVE file version is stored along with INACTIVE versions as long as the file is still resident on the client system. configure RETONLY to be either the same value or longer than RETEXTRA because it functions as a grace period before expiring the file. and 22. The absence of an ACTIVE file version in IBM Tivoli Storage Manager storage indicates that the file has been deleted from the client machine. The figure ( )shows an example of a file (file1) that was first backed up on January 1 and then on January 5. meaning they will never be expired. This number is normally less than or equal to the number you have for VEREXIST.The process of maintaining the ACTIVE and INACTIVE versions (up to the management class limit) continues until the file is deleted from the original client. meaning they will never be expired. 15. This parameter controls how long to retain all remaining inactive files except for the last one and may be set at a specific number of days or to NOLIMIT. and the January 1 copy being expired due to VEREXIST limits). . As files get expired by RETEXTRA. 20. This would happen if the management class setting for number of versions of a deleted file to retain is less than the number of versions of an existing file to retain. How long to keep files: The RETEXTRA parameter controls how much time must elapse before an INACTIVE file version is considered expired. the server detects that the file no longer exists on the client. On January 22. Therefore. For a file deleted on a client machine. If the file is deleted. When file1 is deleted on the client on January 23 and expiration runs. all file1 Maples ESM Technologies Ltd 11 . IBM Tivoli Storage Manager uses different criteria: How many files: The parameter that controls the number of inactive backup versions is called VERDELETED. If this occurs. How long to retain the last file: The RETONLY parameter controls the last inactive copy of a file. and some of the oldest versions of the file may also be deleted. then only INACTIVE version(s) of the file will exist in server storage. . so the only copy is now in IBM Tivoli Storage Manager storage.

RETONLY). For example. These files are now handled by RETEXTRA until their expiration value is reached. The retention period is measured from the time when the file version becomes inactive. each storage pool represents one type of media. You can add or remove volumes without interrupting server operations. A file version is expired either because it is superseded by version control (VEREXISTS. 2000. In our example. Because VERDELETED is set as 2.versions become inactive and the IBM Tivoli Storage Manager server uses the VERDELETED information to reduce the number of inactive files. In this way you can increase or decrease the size of a storage pool dynamically without Maples ESM Technologies Ltd 12 . STORAGE POOL HIERARCHY: A storage pool is a collection of storage pool volumes. VERDELETED) or it is older than the retention period (RETEXTRA. When a file version is no longer retained. Usually. Figure 6-19 shows a scenario in which the last inactive backup copy of file1 will be kept up to March 9th. Retention only applies to INACTIVE files because ACTIVE files are never expired. a storage pool for a 4-mm digital audio tape device (DAT) represents collections of only 4-mm tapes. Retention The retention period of a file version is the length of time in which that file is maintained by IBM Tivoli Storage Manager and accordingly is available to be restored to the client. then it is expired from the IBM Tivoli Storage Manager database. A storage pool created on a disk has files formatted under IBM Tivoli Storage Manager as volumes and are collectively grouped in the storage pool. old versions of the file are immediately expired. VEREXIST should be greater than or equal to VERDELETED (VEREXIST >= VERDELETED) and RETONLY should be greater than or equal to RETEXTRA (RETONLY >= RETEXTRA). Now file1 has only two versions in the IBM Tivoli Storage Manager server (January 20 and January 22).

keeping client data on tape or optical media is a requirement. especially where there are many clients to back up concurrently. IBM Tivoli Storage Manager will automatically migrate files to the next storage pool in the hierarchy (usually on tape or optical) while the client continues its backup operation. . whereby a client initially backs up to a storage pool. Random access devices refer to magnetic disks. making the backups direct to tape may not give the best performance. This migration process is controlled by high and low thresholds set on the storage pool. and many small files are being backed up. In most cases. When this storage pool fills up. Therefore. IBM Tivoli Storage Manager provides a storage pool hierarchy. Sequential devices usually refer to tape devices and/or optical devices IBM Tivoli Storage Manager enables you to configure storage pools to provide the best combination of performance throughput and data permanence.any interruption to the IBM Tivoli Storage Manager service. The two main categories of devices supported for storage pools are random access and sequential devices. However. The collocation option generally would be used in situations where the client Maples ESM Technologies Ltd 13 . usually on disk. COLLOCATION: Collocation gives administrators a way to store all of the files belonging to a specific client on a minimal number of sequential access volumes (usually tapes).

administrators face the key challenge of using tape media efficiently. “virtual” empty spaces begin to appear on the tape volume. when these files reach their expiry date. Remaining active files on the tape volume are rewritten to other tape volumes. each client’s restore can be completed simultaneously and independently. IBM Tivoli Storage Manager addresses this challenge with an innovative tape reclamation feature used to free up entire tape (or optical) volumes in sequential storage pools. this fragmentation wastes space on the tapes and slows the restore process because of the time required to skip over empty spaces.requires a fully optimized recovery time. Often a particular tape volume will contain files that expire on different dates. Figure illustrates this process for a single tape volume. Collocation also makes it possible to avoid conflicts in the restore process. As individual files get marked for expiration. When the collocation feature is used. As a result. IBM Tivoli Storage Manager automatically initiates a process to reclaim the volume. they can be written only from beginning to end). the amount of space that can be reclaimed on a volume increases over time. such as when a single tape volume would have to be mounted to restore data for two different clients. Because tapes are sequential media (that is. it is not possible to rewrite new data into the spaces occupied by expired files. Maples ESM Technologies Ltd 14 . then the original volume is returned to scratch. TAPE RECLAMATION In optimizing their data storage requirements. Figure illustrates the basic operation of the collocation option as backup data is migrated from one storage pool to the next. After this available space reaches a specified threshold.

Internet Protocol (IP) communication bandwidth can then be used to improve service levels for end users and customers. This improves tape hardware asset utilization. This minimizes recovery time by eliminating the use of network and central services resources. SAN technology provides an alternative path for data movement between the IBM Tivoli Storage Manager client and the server. Data movement is off-loaded from the LAN and from the server processor and allows for greater scalability. LAN-free backups decrease the load on the LAN by introducing a Storage Agent. A LAN-free backup environment is shown in Figure Maples ESM Technologies Ltd 15 .TAPE RESOURCE SHARING Enables multiple Tivoli Storage Manager servers to use the same tape library and drives. The Storage Agent handles the communication with the IBM Tivoli Storage Manager server over the LAN but sends the data directly to SAN attached tape devices. and tape hardware asset utilization. recovery performance. The Storage Agent can be thought of as a small IBM Tivoli Storage Manager server (without a database or recovery log) that is installed and run on the IBM Tivoli Storage Manager client machine. NETWORK-FREE RAPID RECOVERY Supports high-speed client data recovery directly from a tape or CD-ROM. relieving the IBM Tivoli Storage Manager server from the actual I/O transfer. tape) are accessible to both the client and the server through the SAN. Shared storage resources (disk. LAN-FREE DATA TRANSFER Effectively exploits SAN environments by moving back-end office and IT data transfers from the communication network to a dedicated data network or SAN.

Figure 1 Maples ESM Technologies Ltd 16 . When backing up files. the Tivoli Storage Manager Server database keeps a list of all files and their attributes (time. This speed is achieved because the number of IBM Tivoli Storage Manager data transfer sessions is transparently optimized based on available system resources. This new feature boosts performance backups to more than three times faster than the rate of a single-threaded session. date. and extended attributes). size. Backup /Restore Tivoli Storage Manager can perform backups of both files and raw logical volumes. At each file backup operation. deleted and changed files.DYNAMIC MULTITHREADED TRANSFER Permits multiple clients to simultaneously transfer data to and from the same Tivoli Storage Manager server. this list is compared to the current file system on the client workstation to determine new. access control lists.

the most recent version of each active file requested is replaced. Figure 2 Maples ESM Technologies Ltd 17 . Restore: Places backup copies of files into a customer-designated system or workstation after the loss of a file.between 40KB and 2MB).Backup: Creates a copy of a file to protect against the operational loss or destruction of that file. By default. file level (normal files). Archive/Restore – Long Term Storage Functionality The Tivoli Storage Manager Archive function stores selected files unconditionally on the server. block level (bigger amounts of data . according to the applicable management class limits. and image level (includes file system and files). Customers control backup by defining the backup frequency and number of versions. Unconditionally means that there is no version limit and they will be retained for the defined time period regardless of whether they are deleted on the client. There are 4 levels of backup available: byte level (small amounts of data like laptops).

or if you want to delete files. yet still have the ability to retrieve them if required. Archive: Creates a copy of a file or set of files for vital record retention of data. It is very common to have a legislative requirement to archive business records for long periods of time. Customers control archive by defining the retention period. list and select software. The archive copy in the storage pool is not affected.Archived files are useful if you want to take a snapshot of particular files. Select the input device. and accept new license agreements. Installing Tivoli Storage Manager on AIX The AIX installation of IBM Tivoli Storage Manager is performed using smit or smitty. such as patent information. financial information or customer records. and the archive function is ideal for this purpose. freeing up space. The packages selected during the server installation on AIX include:  Server code  Message catalog  License Support  Web Server Admin Maples ESM Technologies Ltd 18 . Choose Software Installation and Maintenance >>Install and Update Software >> Install and Update from ALL Available Software. This feature enables the customers to keep unlimited archive copies of a file. Retrieve: A function that allows users to copy an archive file from the storage pool to the workstation.

Datacenter Server  Sun Solaris 8 (64 bit).com (for both 32-bit and 64-bit)  tivoli. Datacenter Edition .1)  Microsoft Internet Explorer 5.0 (which provides Java Swing support) or later  Netscape Navigator 4. and HTTP for Linux. SuSE Enterprise  Server 7 or SuSE Enterprise Server 8/United Linux 1. or 9 (64 bit)  OS/400® PASE V5R1 or V5R2  OS/390® z/OS V1R1.server.11 (11i Version 1.4.webadmin Figure 4 Maples ESM Technologies Ltd 19 .0  Linux on zSeries: SuSE Linux Enterprise Server 8 The TSM Administrative Web interface.server.7 or later with the Java Plug-In (JRE 1.tsm.0) (32 bit and 64 bit)  Windows Server 2003 .Standard Edition .tsm.webhelp  tivoli.tsm.10 enterprise SMP.rte for 32-bit  tivoli. Datacenter Edition .0 (32 bit or 64 bit) or 11.3.4 to optimize performance of the Java backup-archive client. named pipes. Enterprise Edition .1 or later (32 bit or 64 bit) or AIX 5.9-e. Enterprise Edition .server. or later.32 bit.Prerequisites Required by the ITSM Server Supported Server platforms for the TSM Server are as follows:  IBM AIX® AIX 5L 5.32 bit.aix5. V2R10 or later  Linux on pSeries: SuSE Enterprise Server 8  Linux on xSeries: Red Hat Linux Advanced Server 2.2 (32 bit or 64 bit)  HP-UX 11.tsm. IBM Tivoli Storage Manager supports the following communication protocols: TCP/IP.0 or later with the Java Plug-In (JRE 1.tsm.3.rte For either architecture.1) It is recommended that you install and use JRE 1. install the following Tivoli Storage Manager packages for Web administration support:  tivoli. Server. The following Tivoli Storage Manager packages install the IBM Tivoli Storage Manager server:  tivoli. and Web client require one of the following:  Netscape Navigator 6.en_US.1 or 2. Advanced Server.64 bit.32 bit.msg.64 bit  Windows 2000 Professional. Web Proxy.server.

 BACKUPPOOL is disk storage for backed up data.DSK (on most platforms) identifies the fully-qualified name of the database and recovery log. Figure 5 Maples ESM Technologies Ltd 20 .  SPACEMGPOOL is disk storage for data this is not used frequently (to save space).log file.  DISKPOOL is only for Windows.Basic Components Installed by IBM Tivoli Storage Manager The basic Tivoli Storage Manager Server installation will create the following:  IBM Tivoli Storage Manager Database contains information about policy.trace file located in the ITSM server installation directory.  DSMSERV. Installations can be verified on Windows systems by viewing the initserv. schedules. etc. examine the contents of the install. On AIX systems.  DSMSERV.  Recovery Log contains information about all changes to the database.OPT contains server configuration options. activity log.  ARCHIVEPOOL is disk storage for archived data.

You can use the REGister LICense command to register a new license with the Storage Manager server.license. When registered. the following Tivoli Storage Manager packages install the IBM Tivoli Storage Manager server:  tivoli.tsm. Storage Manager requires the mgsyslan.cert  tivoli.tsm. If a Storage Manager system exceeds the terms of its license agreement. one of the following occurs:  The server issues a warning message indicating that it is not in compliance with the licensing terms. the licenses are stored in a file named NODELOCK in the current directory that the server was started from.cert  tivoli.license. Licenses are stored in files called enrollment certificate files.lic license for each managed system that moves data to and from storage over a local area network (LAN).tsm.aix5.license.Install IBM Tivoli Storage Manager License on AIX If you are running with 32-bit hardware. These certificates are files that contain licensing information for the server product.rte64 Registering and Querying Licenses from the Command Line To find out what you are licensed for you can issue the Query LICense command.license.tsm.rte If you are running with 64-bit hardware. install the following Tivoli Storage Manager packages:  tivoli.  Operations fail because the server is not licensed for specific features. The following are examples of enrollment certificate files to register additional clients: Maples ESM Technologies Ltd 21 .

 emcsymm.lic for Tivoli Data Protection for Informix./dsmserv TSM Administrative Interfaces: The TSM server can be administered through Server console .tsm.  spacemgr.  lnotes. Starting TSM Server: To start the server from the /usr/tivoli/tsm/server/bin directory. Administrative command line and administrative web interface Server Console: The server console prompt appears in the system which runs the TSM server .  oracle.lic for library manager accessing a shared library.  mgsyslan.lic for Tivoli Data Protection for Oracle.aix5.lic for each managed system that moves data using the AIX AFS/DFS client.  mssql. regardless of the kernel mode.  informix.  afsdfs.lic for Tivoli Space Manager. issue the following command: register license file=mgsyslan.lic for Tivoli Data Protection for EMC Symmetrix R/3.lic for each managed system that moves data across a SAN.lic for each library in the Extended Device Category.devices.  mgsyssan.1 and later.  essr3.lic for Tivoli Data Protection for MS SQL.rte is required.lic for Tivoli Data Protection for EMC Symmetrix. To register 20 managed systems that move data over a local area network.  msexch. batch or interactive mode. (i) Console Mode Maples ESM Technologies Ltd 22 .lic for each managed system that moves data across a LAN.aix5.lic for Tivoli Data Protection for R/3.lic for Tivoli Data Protection for ESS.lic for Tivoli Data Protection for Lotus Domino.lic for Tivoli Disaster Recovery Manager.tsm.  r3. drm.  libshare. tivoli.lic for Tivoli Data Protection for Lotus Notes.devices  tivoli. enter: .  emcsymr3.devices. The administrative client session can be started in Console.lic for Tivoli Data Protection for MS Exchange.rte For AIX 5.lic for Tivoli Data Protection for ESS R/3. mount.en-US.  ess.msg. Administrative Command line TSM Client software has to be installed to get the Administrative client command line for issuing administrative commands.  library.tsm.  domino.lic number=20 Install the Device Driver on AIX The packages installed during the server installation process that provide SCSI and FCP support are  tivoli.

 The administrative client session was canceled with the CANCEL SESSION command. To start administrative client interface in console mode and have TSM redirect the output to a file enter the following command: Dsmadmc -id=<userid> -password=<password> -consolemode – outfile=<filename> (ii) Mount Mode Tivoli Storage Manager displays messages related to media mount activities when started in mount mode. specify the -OUTFILE Option with a destination file name. Your administrative client session automatically ends when the command has processed. You cannot enter any administrative commands in console mode.OUT file. To have Tivoli Storage Manager redirect all output to a file. To start administrative client interface in mount mode and have TSM redirect the output to a file enter the following command : Dsmadmc -id=<userid> -password=<password> -mountmode – outfile=<filename> (ii) Batch Mode Use batch mode to enter a single administrative command. enter: Dsmadmc -id=<userid> -password=<password> -outfile=abc.out query status (iii) Interactive Mode Use the interactive mode to enter a series of administrative commands. You can automatically restart your administrative client session by entering another command each time the tsm: servername > prompt appears. The interactive mode of the administrative client is disconnected if one or more of the following Conditions is true:  The server was stopped using the HALT command.Tivoli Storage Manager displays requests and status messages to all administrative clients that are started in console mode . to issue the QUERY STATUS command in batch mode with the output redirected to the ABC.  Commands were not issued from the administrative client session for the length of time specified with the IDLETIMEOUT server option in dsmserv. Maples ESM Technologies Ltd 23 . For example.opt file. You cannot enter any administrative commands in mount mode.

7.0)  Linux/390 and zSeries 2.1. 8. TurboLinux 7.5. SuSE 7.0.2 (32-bit and 64-bit)  HP/UX 11. then the TSM administrator has to register the node with the initial password using the following command: Register node <nodename> <password> Installing and Configuring B/A Client Installing B/A Client Backup/Archive Client Prerequisites IBM Tivoli Storage Manager clients:  AIX 5.2.4 kernel (SuSE Linux Enterprise Server 7 and 8) Maples ESM Technologies Ltd 24 .0. and Advanced Server 2.1 and 5.Administrative Web Interface To connect to the TSM server for administration using web browser type http://<TSM Server Name / IP Address>:1580 Registering a Node in TSM server A client has to registered in TSM server for performing backup / restore operations.4 kernel (SuSE 8. and 8. 11i ( 32-bit and 64-bit)  Linux x86 2. If the registration method is closed. when the client connects to the TSM server.0)  Linux for pSeries 2.1.3.3. Registration can be of two types: (i)Open If the registration method is open the client can register the node. 8. 8. and SLES 7 and 8. You can enable open registration by entering the following command from an administrative Client command line: Set registration open (ii)Closed The default registration method is closed.4 kernel (Red Hat 7.

msg.lang Installs the NL messages for API.64bit.client. 6 Backup archive client Installation Steps tivoli.aix51.  From the AIX command line. z/OS V1R1. tivoli.client.64bit.client. type smitty install and press Enter. tivoli. Windows Server 2003 (32 bit or 64 bit). Version 5. tivoli. 7.image Installs the image backup component into the /usr/tivoli/tsm/client/ba/bin directory.64bit.api. and V1R4)  OS/400 5. American English messages are already included in the backup-archive client code. Advanced Server.tsm. insert the CD-ROM into the CD-ROM drive device. 8.1.aix51.books Installs the PDF and HTML book files into the /usr/tivoli/tsm/client/books directory. tivoli.base Installs the backup-archive client files (command-line and GUI).1.web Installs the Web client into the /usr/tivoli/tsm/client/ba/bin directory.client.  Select Install and Update Software and press Enter. American English messages are already included in the API client code. The default installation directory is /usr/tivoli/tsm/client/ba/bin/lang.1 or 5.msg.lang Installs NL messages for the Backup-Archive client.ba. V1R2.tsm.2 API client  SGI IRIX UNIX.64bit.5 with EFS or XFS File Systems (with V5.1 functional client)  Sun Solaris.common Installs the Tivoli Storage Manager common files into the /usr/tivoli/tsm/client/ba/bin directory. and mount the CD-ROM drive. tivoli. zSeries USS (S/390 V2R10 with SMP/E. where lang is the language identifier. Where lang is the language identifier. Windows 2000 Professional.ba. where lang is the language identifier. or 9 (32-bit or 64 bit)  Tru64 UNIX.client. 6  OS/390. The default installation directory is /usr/tivoli/tsm/client/api/bin/lang. and Datacenter Server  Windows NT 4.tsm.  Select Install and Update From ALL Available Software and press Enter.client.0 SP5 and SP6a (with V5.tsm. for example Ja_JP for Japanese. for example Ja_JP for Japanese.tsm.client.api Installs the 64 bit API into the /usr/tivoli/tsm/client/api/bin64 directory. Macintosh.ba.ba.aix51. Release 6. administrative client (command-line) into the /usr/tivoli/tsm/client/ba/bin directory. Maples ESM Technologies Ltd 25 . V1R3.tsm.1 functional client)  Novell NetWare 5.ba.nas Installs the NAS backup component into the /usr/tivoli/tsm/client/ba/bin directory. To install Tivoli Storage Manager from the CD-ROM:  Log in as the root user.64bit. X(10).aix51. tivoli.ba. tivoli.tsm.aix51. Where lang is the language identifier.aix51.  Server.tsm.ba.x  Novell NetWare 5.1A (with V5.tsm.client. tivoli.1 functional client)  Windows XP (32 bit and 64 bit).64bit.client.

0. and press Enter. the dsm. Servername SERVER_A COMMmethod TCPIP TCPport 1500 TCPServeraddress 10.  Select the options you want and press Enter to begin the installation. The Tivoli Storage Manager files are installed in the /usr/tivoli/tsm/client/ba/bin directory Configuring B/A client: To connect to the TSM server. press the F4 key and select the CD-ROM device containing the installation CD-ROM or specify the directory containing the installation images.0. if you want to run a single command .10 TSM Client Interfaces: TSM provides the following interface for performing client operations: Backup Archive command line Backup Archive GUI Backup Archive Command Line Interface: (i)Batch mode Enter dsmc followed by the command. Select the Tivoli Storage Manager filesets you want to install and press Enter.sys which is available in the client installation directory.  At the SOFTWARE to install prompt. the node should be configured with the following details: TSM server name Communication Method IP address of the TSM server TCP port number to be used for connecting to the server These details can be given in the client option file dsm. press the F4 key.10 and use TCP port 1500 for client communication. At the INPUT device/directory for software prompt.0. Example To connect to the TSM server SERVER_A configured with IP Address 10.sys will have the following lines included in it.0. Example Maples ESM Technologies Ltd 26 .

dat -password=<password> (ii)Interactive mode To start a client command session in interactive mode. type dsm Install & Configure Tape Library Attached to the IBM Tivoli Storage Manager Server Maples ESM Technologies Ltd 27 .To archive the file abc. enter quit at the tsm> prompt Backup Archive GUI To start a GUI session . enter either of the following commands:  dsmc  dsmc loop When you press Enter. this prompt is displayed on your screen: tsm> To end an interactive session.dat in the directory critical. type the following command dsmc archive /critical/abc.

Drive definitions are required to map individual drives to TSM and the operating system When configuring the Tape library in TSM server. sharing similar media mounting characteristics. and possibly robotic devices (depending on library type). each drive and a device class. Maples ESM Technologies Ltd 28 . TSM Library Types TSM provides support for two types of libraries:  MANUAL MANUAL libraries contain devices with drives that require an operator to mount media.Install and Configure Tape Library Attached to the IBM Tivoli Storage Manager Server Introduction In this unit you will learn how to connect and configure a tape library to the TSM server Objective On completion of this unit. the physical and logical device configuration has to be done in a sequence. The library identifies whether TSM sends tape mount requests to an operator or a robotic picker. Steps for configuring the physical definition of a library includes Step1 A Libraryrepresents a collection of one or more drives. Each tape or optical disk device must be associated with a TSM library so that the TSM Server knows which drives are available for mounting media. The physical definition for the library has to be configured followed by the logical configuration. you will be able to  Configure a tape library local attached to the IBM Tivoli Storage Manager  Prepare tape cartridges for use in an IBM Tivoli Storage Manager managed tape Library Tape Library Configuration To define an optical disk or tape device to TSM. the administrator must define a library.

Step2 Library Path Defines the path for access between Server and Library Step3 Drive A drive is a hardware device capable of performing operations on a specific type of sequential media. For devices with multiple drives. and labeling prefixes. Step 4 Drive Path Defines the path for access between Server and Library Step Deviceclass TSM storage object that represents a device. TSM supports only the DISK device class. The administrator must define a device class for each unique device type in the TSM environment. how often the drive is cleaned (for tape drives). each drive is separately defined to TSM. Examples of TSM device types include: For random access storage. The DISK device class is predefined by TSM. A device class for a tape drive must also specify a library. including automated libraries. and whether or not the drive is online.  SCSI SCSI libraries contain devices with drives for which media is mounted automatically. Drive definitions can include such information as the element address (for drives in SCSI libraries). A device class contains information about the device type and the way the device manages its media including definitions such as recording format. estimated capacity. You cannot modify the DISK device class Maples ESM Technologies Ltd 29 .

 The tape volume naming convention (PREFIX). TSM supports the following device types: Device Type Description 3570 IBM 3570 cartridge tape devices 3590 IBM 3590 tape drives 4MM 4mm tape drives. since the default does not consider the use of compression by the client or tape hardware.  The maximum minutes before idle tape is demounted (MOUNTRetention). OPTICAL Optical drives that use 5.25-inch write-once read-many optical cartridges Tape device classes allow the installation to control:  Whether you will be using cartridge or reel tape (DEVtype). such as IBM 7206-005 8MM 8mm tape drives. or CDROM media) Storage volumes that are actually files archived in the server storage of SERVER another TSM server (a target server) WORM Optical drives that use 5. removable file REMOVABLEFILE systems (for example.For sequential access storage.  The estimated volume capacity (ESTCAPacity). such as IBM 7208-001 and 7208-011 DLT Digital linear tape (DLT) drives DTF Digital tape format FILE Storage volumes that are files in the file system of the server machine GENERICTAPE Tape drives supported by a Windows tape device driver. such as the IBM 7207 Removable media devices that are attached as local.  The maximum tapes that can be simultaneously mounted (MOUNTLimit).25-inch re writable optical cartridges QIC Quarter-inch cartridge tape drives. Maples ESM Technologies Ltd 30 . Iomega Zip or Jaz drives.

. Figure 6 Maples ESM Technologies Ltd 31 .

only a single SCSI ID is required. Detailed instructions should be in the documentation that came with your hardware. Notes: Power off your system before attaching a device to prevent damage to the hardware. Determine the SCSI IDs available on the adapter card to which you are attaching the device.html Select one of the following under Supported Devices:  For AIX.ibm. but have different LUNs. Follow the manufacturer’s instructions to set the SCSI ID for the drives and library controller to the unused SCSI IDs that you found. Also. and one for the library or autochanger controller. Find one unused SCSI ID for each drive. Usually this means setting switches on the back of the device. If each device does not have a unique SCSI ID. if not already installed.com/software/tivoli/products/storage-mgr/platforms. d. c. Install the SCSI or FC adapter card in your system. Follow the manufacturer’s instructions to attach the device to your server system hardware. you may have serious system problems. Note: Each device connected in a chain to a single SCSI bus must be set to a unique SCSI ID. For these libraries. b. Check the documentation for your device. the drives and the autochanger share a single SCSI ID. In some automated libraries. you must attach a terminator to the last device in the chain of devices connected on one SCSI adapter card. SUN and Windows  For iSeries  For Linux Maples ESM Technologies Ltd 32 .Connect the Library Figure 7 Perform the following steps to attach an automated library device: a. HP. The list of supported device types is available on-line at: http://www-3.

Configuring a Tape Library: Example: Configure a 3581 SCSI based tape library in TSM server. online and offline. Labeling Tapes with LABEL LIBVOLUME Maples ESM Technologies Ltd 33 . Tapes that are part of the scratch pool are eligible to be selected for use. Tapes may be checked into IBM Tivoli Storage Manager as either scratch or private. Once a tape is selected. The drive type is LTO. Step 1 Defining a library Define library 3581lib Prepare Tape Cartridges for Use in an IBM Tivoli Storage Manager Tape Library Figure 8 Tapes must first be labeled and then added to the inventory of tapes available to IBM Tivoli Storage Manager. data remains on the tape until it is expired or moved. There are two different methods to checkin a tape. or label and checkin in one step. You can label then checkin. The tape can then be reclaimed and returned to the scratch pool.

You can label volumes with the LABEL LIBVOLUME command. 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. Checking media into an automated library involves adding them to the library volume inventory. Maples ESM Technologies Ltd 34 . and the manual device is attached to SCSI address 5. and may contain valid data. you can issue the CHECKIN parameter. Figure 9 A private volume is a labeled volume that is in use or owned by an application. its status is changed to private. The following example demonstrates using the LABEL LIBVOLUME command to label tapes for a manual library and for an automated library. and it can only be used to satisfy a request to mount that volume by name. You want to insert media into the device's entry/exit ports and you want the device's bar code reader to read bar code labels and overwrite existing labels with the information on the bar code label. When data is written to a scratch volume. make the volumes available to Tivoli Storage Manager Devices by checking the volumes into the library volume inventory using the CHECKIN LIBVOLUME command. Automated Library Device: label libvolume storagelibname checkin=scratch search=yes overwrite=yes labelsource=barcode Checking in Volumes After volumes have been labeled.If you label volumes with LABEL LIBVOLUME command. Private volumes do not return to scratch when they become empty. Assume the automated device is attached to SCSI address 4. You must define each private volume.

Using one command (LABEL LIBVOL) significantly reduces the time and interaction required during these two labor- intensive operations. barcode. however. This command. Figure 10 Checking Out Volumes You can remove volumes from automated libraries by issuing the CHECKOUT LIBVOLUME command Figure 11 Maples ESM Technologies Ltd 35 . such as the search. The LABEL LIBVOL command allows all the functionality of the DSMLABEL command. does not replace the previous method of DSMLABEL followed by CHECKIN LIBVOL to prevent large-scale tape labeling from tying up the server’s resources.Create Scratch Tapes by Using the LABEL LIBV Command The LABEL LIBVOLume command combines the DSMLABEL and CHECKIN LIBVOL commands which were used in previous versions of TSM. and overwrite options. LABEL LIBVOL also checks the volumes into the library as either private or scratch volumes.

Auditing the volume inventory ensures that the information maintained by the Tivoli Storage Manager server is consistent with the physical media in the library. or Tivoli Storage Manager requests that the operator remove the volume from a drive within the device. Maples ESM Technologies Ltd 36 . you can issue the CHECKOUT LIBVOLUME command with the SEARCH=BULK parameter. Auditing a Library Figure 12 You can issue the AUDIT LIBRARY command to audit the volume inventories of automated libraries. Tivoli Storage Manager moves the media to the entry/exit port of the device if it has one. Tivoli Storage Manager ejects the volume to the next available entry/exit port. The audit is useful when the inventory has been manually manipulated.Tivoli Storage Manager mounts each volume and verifies its internal label before checking it out of the volume inventory. Tivoli Storage Manager deletes missing volumes and updates the locations of volumes that have moved since the last audit. For automated libraries with multiple entry/exit ports. After a volume has been checked out. Tivoli Storage Manager cannot add new volumes during an audit.

Managing Storage Pools & Storage Pool Volumes Maples ESM Technologies Ltd 37 .

Data storage may be composed of optical media. Maples ESM Technologies Ltd 38 . and sequential tape media. This includes planning. and deleting storage volumes and storage pools depending on level of privilege class. preparing. and recovery requirements. Files are automatically moved to other devices to satisfy free space. direct access storage. space utilization. storage. you should be able to do the following:  Describe purpose of Storage Pools. performance. The database serves as the inventory or index to client files within data storage. you will learn how to create hierarchical storage pools of different media types to allow for efficient management of your data. Storage Pool Hierarchies & Storage Pool Volumes  Create a Storage Pool  Design and configure storage pools based on given customer requirements  Manage Storage Pool Volumes Storage Pools. monitoring. or operator privilege can manage data storage. Objectives On completion of this unit. Data storage is actually defined as a collection of storage pools.Managing Storage Pools and Storage Pool Volumes Introduction In this unit. An administrator with system. Storage Pool Hierarchies & Storage Pool Volumes Figure 13 Data storage pools are where the server stores files which are backed up and archived. Files may be initially placed on different storage pools according to the desired storage management policy.

For each storage pool. you can define a storage pool which consists of storage volumes residing on high-performance DASD. leaving the original volumes available for reuse. 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. if users need immediate access to certain data. Then. users can associate this storage pool as a destination for their files by binding the appropriate management class. The difference between the high and low thresholds indicates the approximate amount of data that will be migrated. For example. you define low and high migration thresholds.Storage Pool Hierarchies Figure 14 Storage Pool: A storage pool is a named set of volumes that is the destination of backed- up or archived data. This process is known as Maples ESM Technologies Ltd 39 . To reduce tape mounts and to use the space on tape volumes most effectively 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. The purpose of storage pools is to match user requirements for data with the physical characteristics of storage devices. The high threshold is used to trigger migration and ensure that enough free space is available while migration is performed. The low threshold identifies the amount of free space needed to satisfy the daily processing requirements of your business. This process is known as migration. Storage pools can be chained to create a storage hierarchy as given in Fig 14 Automatic Data Movement Automatic data movement between storage pools is used to balance the performance and cost of different storage devices while ensuring an adequate free space to satisfy new space allocations.

then the migration process ends. and a warning message is issued to the administrator If multiple migration processes are running (controlled by the MIGPROCESS parameter of the DEFine STGpool command). For each tape storage pool. We recommend that you do not specify a value less than 50% to avoid tape volume reclamation to multiple volumes. you define a reclamation threshold. another client node is chosen by using the same criteria as described above. which indicates the amount of space consumed by data that is no longer valid before triggering reclamation. If the amount of space used in the storage pool is now below the low migration threshold. TSM first identifies which client node has backed up or migrated the largest single file space or has archived files that occupy the most space. the server migrates all files from every file space belonging to that client for those files whose number of days in the storage pool exceeds the value specified by the MIGDELAY parameter. migration ends. Figure 18 Maples ESM Technologies Ltd 40 . If not. If the value for that parameter has been set to YES. If the value for MIGCONTINUE has been set to NO. the files for more than one node may be chosen for migration at the same time. The oldest files are migrated first until the low migration threshold is reached. No migration occurs if there is no next storage pool. then TSM continues the migration process based on how long the files have been in the storage pool. When the server identifies the client node based on these criteria. 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.reclamation. Figure 17 Storage Pool Migration When the high migration threshold is reached in a storage pool. and the migration process continues. TSM migrates files from the pool to the next storage pool in chain.

if space is needed to store new data in the disk storage pool.  It can require more space for the TSM database. However. so that subsequent retrieval requests can be satisfied quickly. the files are cached) until space is needed for new files.If the cache option is enabled. When cache is enabled. The copies remain in the disk storage pool. a copy of the file remains on fast disk storage after the server migrates the primary file to another storage pool. files that are migrated remain on disk storage (that is. 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. Reclamation Figure 19 Maples ESM Technologies Ltd 41 . using cache has some important disadvantages:  It can increase the time for client backup operations to complete. The advantage of using cache for a disk storage pool is that cache can improve how quickly the server retrieves some files. cached files are erased and the space they occupied is used for the new data. However. You may want to consider using a disk storage pool with cache enabled for storing space- managed files that are frequently accessed by clients. but in a cached state. You can enable cache by specifying CACHE=YES when you define or update a storage pool. When you use cache.

the volume is eligible for reclamation. To have TSM collocate data in a storage pool by client node. files become obsolete because of aging or limits on the number of versions of a file. set collocation to FILESPACE. you reduce the number of volume mount operations required when users restore. Reclamation is the process of reclaiming this space. Unused space from expired or deleted logical files is removed as the aggregate file is copied to another volume during reclamation Collocation 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. When the percentage of reclaimable space exceeds a specified level (the reclamation threshold). You can set a reclamation threshold for each sequential access storage pool when you define or update the pool. or recall many files from the storage pool. When multiple volumes are eligible for reclamation. TSM reclaims the eligible volumes in random order.Space on a sequential volume becomes reclaimable as files expire or are deleted from the volume. By using collocation. retrieve. Collocation thus improves access time for these operations. The server checks whether reclamation is needed at least once per hour and begins space reclamation for eligible volumes. set collocation to YES. For example. You can set collocation for each sequential access storage pool when you define or update the pool. the server tries to reclaim the files for each client node or client file space onto a minimal number of volumes Figure 20 Maples ESM Technologies Ltd 42 . Space within aggregate files is also reclaimed during the reclamation process. If collocation is enabled and reclamation occurs. To have TSM collocate data in a storage pool by client file space. An aggregate is a physical file that contains multiple logical files backed up or archived from a client in a single transaction.

Maples ESM Technologies Ltd 43 .

or space-managed data (primary storage pools). TSM knows the device characteristics of the storage pool media and how to access it Types of Storage Pools: TSM server has two types of storage pools for different purposes. Each device is associated with a device class that specifies the device type and how the device manages its media. Each device class is characterized by its device type.  Store copies of primary storage pool data (copy storage pools).  Store database backups. It is through this mapping that. One device class can be associated with multiple storage pools. Each storage pool is associated with only one device class. when data is written to or accessed from a storage pool. which indicates the type of storage volumes that are used to store data. Storage pools are mapped to a device class. archive. They are Primary Storage Pool Copy Storage Pool Maples ESM Technologies Ltd 44 .Device Class and Storage Pool Figure 16 TSM uses the device class to determine which device and storage volume type to use to:  Store backup.  Export or import TSM data.

a tape device class ) You can move copy storage pool volumes offsite and still have the server track the volumes. or export file data. Primary storage pool volumes are always located onsite. recall. retrieve. A primary storage pool can use random access storage (DISK device class) or sequential access storage (tape) The server has three default. the data is stored in a copy storage pool. Defining Storage pools Use the following command to define a storage pool: DEFine STGpool Maples ESM Technologies Ltd 45 . Moving Copy storage pool volumes offsite provides a means of recovering from an onsite disaster. primary storage pools: ARCHIVEPOOL The default destination for files that are archived from client nodes BACKUPPOOL The default destination for files that are backed up from client nodes SPACEMGPOOL For space-managed files that are migrated from Tivoli Storage Manager for Space Management client nodes (HSM clients) Copy Storage Pools: Copy Storage Pool When an administrator backs up a primary storage pool.Primary Storage Pool When a user tries to restore. A copy storage pool can use only sequential access storage (for example. the requested file is obtained from a primary storage pool if possible. random access.

with caching enabled. Store any files larger than 1GB in subordinate pool TAPEPOOL Enable collocation of files for client nodes.(i)Defining a Primary Storage Pool – Random Access Define stgpool <stgpoolname> DISK pooltype=primary description=<description> access=readwrite/readonly/unavailable Maxsize=<nolimit/maximumfilesize> crcdata=<yes/no> nextstgpool=<stgpoolname> highmig=<value> Lowmig=<value> cache=yes/no migprocess=<1/number> migdelay=<0/days> migcontinue=<yes/no> copystgpools=<copystgpool1.copystgpool2> copycontinue=<yes/no> Please refer to Admin reference for details of the command parameters Example Define a primary storage pool. DISKPOOL. The command is Define stgpool DISKPOOL disk description="disk storage pool" maxsize=10m highmig=60 lowmig=30 cache=yes nextstgpool= TAPEPOOL (ii) Defining a Primary Storage Pool – Sequential Access DEFine STGpool pool_name device_class_name POoltype = Primary DESCription = description ACCess = READWrite/ READOnly/ UNAVailable MAXSIze = NOLimit / maximum_file_size CRCData = No/Yes NEXTstgpool = pool_name HIghmig = 90/percent LOwmig = 70 /percent REClaim = 60/percent RECLAIMSTGpool = pool_name COLlocate = no/Yes/ FILespace MAXSCRatch = number REUsedelay= 0 /days OVFLOcation = location MIGDelay =0 / days MIGContinue = No / Yes DATAFormat = NATive /NONblock /NETAPPDump /CELERRADump / NDMPDump COPYContinue= Yes/ no COPYSTGpools = copy_pool_name Please refer to Admin reference for details of the command parameters Example Define a primary storage pool named LTOPOOL to the LTO device class (with a device type of LTO) with a maximum file size of 1GB. Store any files larger than 10MB in subordinate storage pool named TAPEPOOL. to use the DISK device class. Allow as many as 5 scratch volumes for this storage pool. The command is Define stgpool LTOPOOL LTO maxsize=1g nextstgpool=TAPEPOOL collocate=yes maxscratch= 5 Maples ESM Technologies Ltd 46 . and the low migration threshold to 30 percent. Set the high migration threshold to 60 percent. Limit The maximum file size to 10MB.

For the syntax of the commands refer to the Tivoli Storage Manager Administrator's Guide or issue the HELP UPDate STG. or HELP QUERY command as an administrator. If you do not explicitly update a parameter. To prepare a volume:  Label the volume. Use the DEFine Volume command unless you allowed scratch volumes in the storage DEFine VOLume poolname volname Formatsize=[Format_size] Maples ESM Technologies Ltd 47 . Defining storage pool volumes Use the DEFINE VOLUME command to assign a random or sequential access volume to be used for storage within an existing storage pool. it checks the volume name in the header to ensure that the correct volume is being accessed. you must prepare volumes for use. LTOPOOL2. Delay the reuse of volumes for 45 days. For sequential access storage pools with other than FILE device type. Allow up to 50 scratch volumes For this 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. use the CHECKIN LIBVOLUME command to check the volume into the library. before issuing this command you must allocate and/or format the volume by using the DSMFMT utility or a version of it. it remains unchanged. to the LTO device class. You can use this command to modify selected parameters for the specified storage pool. The parameters to update are the same as the parameters when you define a storage pool. unless you allow scratch volumes for the storage pool. When the server accesses a sequential access volume.(iii) Defining a Copy Storage Pool – Sequential Access DEFine STGpool pool_name device_class_name POoltype = Copy DESCription = description ACCess = READWrite / READOnly /UNAVailable COLlocate = No/Yes/FILespace REClaim = 100/ percent MAXSCRatch = number REUsedelay = 0/ days OVFLOcation= location DATAFormat =NATive/ NONblock CRCData = No /Yes Please refer to Admin reference for details of the command parameters Example Define a copy storage pool.  For storage pools in automated libraries. Command Define stgpool LTOPOOL2 LTO pooltype=copy maxscratch=50 reusedelay=45 Update / query storage pools Commands to Update and Query storage pools are as follows: UPDate STGpool poolname <parameters> Query STGpool poolname <parameters> Use the UPDate STGpool command to change any parameters in an existing storage pool. Use the Query STGpool command to display information about one or more storage pools. For a random access volume.

you must first delete all volumes assigned to the specified storage pool. the files within the volume. To determine the contents stored on a volume. In order to use this command. This command can be used to delete a volume assigned to either a primary or copy storage pool. it is recommended that you delete the volumes one at a time. Explicitly request to discard all files in the storage volume by specifying the following option: DISCARDDATA= YES DELete VOLume volumename Use the DELete VOLume command to delete a storage pool volume and. QUERY CONTENT. Maples ESM Technologies Ltd 48 . optionally. You cannot delete a storage pool that is defined as a subordinate storage pool. use the Query CONtent command.Example : DEFine VOL BACKUPPOOL /usr/tivoli/tsm/server/bin/vol6 Formatsize=2 Deleting Storage Pools and Volumes Delete storage pools and storage volumes with the following commands: MOVE DATA MOVE DATA. DELete STGpool poolname Use the DELete STGpool command to delete a storage pool. Use the MOVE DATA command to move all files to another volume. Concurrent volume deletion can adversely affect server performance. If you are deleting several volumes.

Scheduler Maples ESM Technologies Ltd 49 .

or have failed. Objectives After completing this unit you should be able to:  Describe the difference between client polling and server prompted methods  Identify and describe scheduler options available  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 Overview of Schedules Figure 21 IBM Tivoli Storage Manager uses schedules to allow administrators to automate operations. The administrative interfaces to defining. and other processes. and event records can be deleted from the database as needed to recover database space. The administrator can query the log to determine whether the scheduled events have completed successfully or not. Each scheduled operation is called an event and is tracked by the server and recorded in the database. deleting schedules will be discussed here. have completed. updating. Maples ESM Technologies Ltd 50 . It records scheduled operations that are in progress.Scheduler Introduction Central scheduling enables automation of backup. archive.

the TSM client periodically queries or polls the server for a scheduled operation and the date/time that the operation is to start. The client then waits until it is time to start the scheduled operation and executes the operation. the administrator can determine the number of client/server sessions that may be used by central scheduling. Central Scheduling Mode .Client Polling Figure 22 In client polling.Server Prompted Figure 23 Maples ESM Technologies Ltd 51 . In addition. Client polling is initiated by the client starting the TSM client scheduling program using the command line interface. The program will continue to query the server and execute schedules until the user explicitly stops the program or the machine is shut down.The administrator is responsible for building and maintaining the schedules and has the authority to prioritize workstations. The Central Scheduler supports two modes of scheduling: client polling and server prompted. Central Schedule Mode . To start the program the client enters DSMC SCHEDULE.

Selecting Schedule Methods Figure 24 Maples ESM Technologies Ltd 52 . and executes the operation. 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. either successfully or unsuccessfully. To enable server prompted scheduling. The client then queries the server for the operation. the client notifies the server that the operation has completed. change the client options file so that the SCHEDMODE is PROMPTED. Server prompted is initiated by the client starting the Tivoli Storage Manager client scheduling program using the command line interface. Upon completing the operation.In server prompted mode. To start the program the client enters DSMC SCHEDULE.

Any is the default and recommended value.On the server. Your TSM administrator can also set this option. On the client . this option goes in the client system options file. Use the RETRYPERIOD option to specify 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 option is specified as follows: SCHEDMODe POlling | PRompted This option is ignored except during the execution of the DSMC SCHEDULE command. The default is not to prune the log. the administrator with system privilege must specify which central scheduling modes will be supported by the server. that value overrides what you specify in the client options file after your client node successfully contacts the TSM server. this option goes in the client system options file. output from scheduled commands appears on your screen. Use the SCHEDLOGRETENTION option to specify the number of days to keep entries in the schedule log and whether to save the pruned entries. It is also directed to the file you specify with this option. For UNIX clients. this option goes in the client system options file Maples ESM Technologies Ltd 53 . All clients support this option. Users (root users on UNIX systems) set the scheduling mode on client nodes. Additional Scheduling options Additional scheduling options include:  SCHEDLOGNAME  SCHEDLOGRETENTION  MAXCMDRETRIES  RETRYPERIOD Use the SCHEDLOGNAME option to specify the name and location of a file where you want Tivoli Storage Manager to store the schedule log. Your TSM administrator can also set this option. All clients support this option. For UNIX clients. the dsm.Which indicates the server can support clients using either client-polling or server-prompted scheduling.Which indicates that only clients using server-prompted mode will be accepted.  PRompted . which invokes the client portion of the central scheduling function.opt file must be updated with the SCHEDMODE option which is used to specify which mode the client scheduler will operate in. that value overrides what you specify in the client options file after your client node successfully contacts the TSM server. Tivoli Storage Manager prunes the log after every schedule is run if you tell Tivoli Storage Manager to prune. Use the MAXCMDRETRIES option to specify the maximum number of times you want the client scheduler on your workstation to attempt to process a scheduled command that fails. For UNIX clients.  POlling . If your TSM administrator specifies a value for this option. 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).Which indicates that only clients using client-polling will be accepted. this option goes in the client system options file. For UNIX clients. If your TSM administrator specifies a value for this option. The Set SCHEDMODes command is used and the supported parameters are:  ANY . When you run the SCHEDULE command.

For UNIX clients. this option goes in the client system options file dsm. This option applies only when the SCHEDMODE option is set to POLLING.Additional Client Polling Options Figure 25 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.sys. and you want the server to contact a different address than the one Maples ESM Technologies Ltd 54 . Tivoli Storage Manager uses this option only when the SCHEDULE command is running. Additional Server Prompted Options Figure 26 Use the TCPCLIENTADDRESS option to specify a TCP/IP address if your client node has more than one address.

used to make initial contact with the server. this option goes in the client system options file. For UNIX clients. For UNIX clients. If the default or specified port is busy. Use the TCPCLIENTPORT option to specify 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. this option goes in the client system options file. Maples ESM Technologies Ltd 55 . Tivoli Storage Manager attempts to use any other available port.

or run an executable script. not all clients can run all scheduled operations. Maples ESM Technologies Ltd 56 . Also. a batch file. or a script on different client operating systems.Identify Tasks/Actions that can be Scheduled for Clients Figure 27 Tivoli Storage Manager cannot run multiple schedules concurrently for the same client node. For example. even though Tivoli Storage Manager allows you to define the schedule on the server and associate it with the client. a Macintosh client cannot run a schedule when the action is to restore or retrieve files. An executable script is also known as a command file.

Set MAXSCHedsessions schedulepercent Maples ESM Technologies Ltd 57 . This facilitates automation of client operations via user-written scripts. This ensures that scheduled events will not run if pre scheduled commands do not complete successfully. and documented return codes. consistent. Administrators can now distinguish between scheduled backups that complete successfully with no skipped files. the scheduled event will not run. This command specifies the maximum number of scheduled sessions as a percentage of the total number of server sessions available. if the preschedulcmd command ends with non-zero return codes.Consistent Client Return Codes Figure 28 The command line client and scheduler provide reliable. Also. Managing Client/Server Sessions Figure 29 Use the SET MAXSCHEDSESSIONS command to regulate the number of sessions that the server can use for processing scheduled work. and scheduled backups that complete successfully with one of more skipped files.

and apply to a particular policy domain. You can set a global value for the period between attempts by the client to contact the server for scheduled work. The client's value is only overridden if the client can contact the server. you may have a network error. You can use the SET MAXCMDRETRIES command to set a global value for the maximum number of retries. 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 Schedules are created and maintained in the TSM database by an administrator with either System or Policy privilege. Each client can set their own retry period at the time their scheduler program is started. Use the SET MAXCMDRETRIES command to specify the maximum number of times that a scheduler on a client node can retry a scheduled command that fails. The MAXCMDRETRIES parameter can be specified by each user at the time their client scheduler program is started. The client's value is overridden only if the client can contact the server. A client may be associated with more than one schedule. The value for the QUERYSCHEDPERIOD parameter can be set by each client node at the time the client scheduler program is started. and any number of schedules can be defined in a policy domain. Use the SET QUERYSCHEDPERIOD command to regulate the frequency with which client nodes contact the server to obtain scheduled work when they are running in the client-polling mode. The client's value is overridden only if the client is able to connect with the server. Use the SET RANDOMIZE command to specify the degree to which start times are randomized within the startup window of each schedule for clients using the client-polling mode. This value overrides the value specified by the client.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 can use this command to set a global value for the retry period which will override the value specified by all clients. set a time period that permits more than one retry attempt within a typical startup window. Maples ESM Technologies Ltd 58 . 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. Schedules are executed serially by a client. are defined with a Define Schedule command. Administrators use the Define Association command to associate clients (that are in the domain) with a schedule. Use the SET RETRYPERIOD command 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. Randomize will be covered in detail later in this unit. which overrides the value specified by the user. When setting the period between retry attempts.

The client must start the scheduled operation within the startup window. or the network is unavailable). A log is maintained on the server. The administrator can query the log for information about started. 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 from a command line administrator or while in the web interface Schedule Example Figure 30 A schedule is given a startup window. which records information about the scheduled events. completed. If the client is unable to do so (for example the terminal is turned off.... which defines when a scheduled operation is to start. the client will wait until the next occurrence of the schedule's startup window to execute the operation. The scheduled operation must start within the window it may complete outside of the window. Maples ESM Technologies Ltd 59 . and failed events.. DELETE Schedule.Using Command Line to define the schedule To define a schedule on the command line use 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.

Using wildcard characters makes it easier to tailor a command to your needs. If a client is listed. You can use a pattern matching expression to specify a name. The wildcard characters you use depend on the operating system from which you issue commands. 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. The items in the list are separated by commas. you can use wildcard characters such as an asterisk (*) to match any (0 or more) characters or you can use a question mark (?). Nodename specifies the name of the client node to be associated with the specified schedule. This parameter is required. Schedulename specifies the name of the schedule that you want to associate with one or more clients. with no intervening spaces. or a percent sign (%) to match exactly one character. This parameter is required. Maples ESM Technologies Ltd 60 . such as the query commands.Using Commandline to define Association Figure 31 Use the DEFine ASSOCiation command to associate one or more clients with a schedule. You can specify a list of clients that you want to associate with the specified schedule. This parameter is required. In some commands. you can use wildcard characters to create a pattern-matching expression that specifies more than one object. For example. All matching clients are associated with the specified schedule. Client nodes that are associated with a schedule initiate Tivoli Storage Manager functions according to that schedule Domainname specifies the name of the policy domain to which the schedule belongs.

Client Configuration Maples ESM Technologies Ltd 61 .

Objectives  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 Identify the types of Clients Figure 32 Using the command line Figure 33 Maples ESM Technologies Ltd 62 .Client Configuration Introduction In this unit we will discuss the types of clients available with IBM Tivoli Storage Manager. and how to invoke. manage and configure them.

0 or later with Java Plug-in 1.3.7 or later with Java Plug-in 1.3.  Netscape Navigator 4. The command dsmc can be followed by the keyword you wish. Using GUI The backup-archive GUI interface can be accessed by clicking Start >> Programs >> Tivoli Storage Manager >> Backup-Archive GUI DSM without the C will start the GUI interface from the command line. Administrative Control of Access Maples ESM Technologies Ltd 63 .1  Microsoft Internet Explorer 5.3. Using the web client To use the web client. specify the URL of the client machine running the web client in your web browser.x. The password is encrypted and will not display when prompted.0 or later with the Java support option installed. a password must be entered on the command line or the user will be prompted to enter a password. For example the dsmc incremental command: dsmc i When authentication is on.The client can be invoked by using the command line interface by typing dsmc at the system command prompt in the directory path where the client was installed.x. Refer to the Backup-Archive Client Requirements section for the specific operating system levels supported for the Web clients. For example http:\x. TCP/IP is the only communication protocol supported for this client interface.1_01.1. The client invokes a session with the server until the command is completed.x:1581 The Web client runs on the following browsers:  Netscape Navigator 6. The minimum JRE level required for Microsoft Internet Explorer browsers running on Windows platforms is JRE 1. and the client port 1581.

OPT  DSM. This can be prevented by the Administrator as shown in the command below. The administrator does not have to register this node. Closed registration means the client node must be registered by the Administrator.  register a node at the admin command line with register node mercedes montana userid=none  register a node through the admin GUI Client Nodes >> Register a new node Registration can be set open or closed. communication method.SYS . and locking/unlocking nodes. an administrative user ID is not automatically defined. Before a user can request Tivoli Storage Manager services. and scheduling options. backup and archive options. and whichever is used depends on the operating systems:  DSM. On other systems like Windows 2000 the client options are in DSM. Configuring Client Access to Server Figure 34 Maples ESM Technologies Ltd 64 . configuring password management. the node must be registered with the server. This is a file that a client can edit. containing a default set of processing options that identify the server. Each node must be registered with the server and requires an option file with a pointer to the server. By registering nodes. you are able to protect the data of your clients. Client Options File There are two client options files.  If an administrative user ID already exists with the same name.You will learn how to configure IBM Tivoli Storage Manager to administer control of access to the server.  You can use this administrative user ID to access the Web backup-archive client from remote locations through a Web browser.  When a node is registered.OPT and DSM.OPT .  Each node must be registered with the server and requires an option file with a pointer to the server. Open means the client node is automatically registered when a session is started. Tivoli Storage Manager automatically creates an administrative user ID with client owner authority over the node.SYS On multiuser systems like UNIX the client options are in both files DSM.

One to 64-character TCP/IP address for a Storage Manager server.sys. and COMMMethod. The default is 1500. The nodename option goes in your client system options file dsm.IBM Tivoli Storage Manager uses several communications parameters that must be set. NODENAME Use the NODename option to identify your workstation to the server. The TCP/IP port address used to communicate with a Storage Manager server. To use the TCP/IP communication protocol. For UNIX. The range of values is 1000 to 32767. These options are the NODename.opt is also used. The other TCP/IP options have default values which you can modify only if you want to change the default value. For Windows NT and Windows 95. the default is the name of the machine if you do not use this option. TCPPORT port_address COMMMETHOD Use the COMMMethod option to specify the communication method you are using to provide connectivity for client-server communication. the default is the same as the name returned by the hostname command. TCPPORT Use the TCPPORT option to specify a server's TCP/IP port address. The value you specify for this parameter can be a TCP/IP Internet domain name or a dot address. dsm. For Unix environments. The nodename can be a 1 to 64-character name which will be used to identify the node for which you want to request Storage Manager services. Maples ESM Technologies Ltd 65 . TCPServeraddress. you must include the tcpserveraddress option in your client options file. TCPSERVERADDRESS Use the TCPSERVERADDRESS option to specify the TCP/IP address for a Storage Manager server.

The Web-based communication method option. The SNMP communication option. The Transmission Control Protocol/Internet Protocol (TCP/IP) communication method.  SNMP.Some of the communication methods that can be used with the COMMMethod option include:  SHAREDMEM. The Shared Memory communication method.  NAMEDPIPE.  HTTP.  TCPIP. This communication method option is possible when the Storage Manager Server and Storage Manager Client are on same UNIX machine. Maples ESM Technologies Ltd 66 . Please refer to the Tivoli online documentation for a complete listing. The Named Pipe option specifies the name of a named pipe to use for communication between a Storage Manager Server and Storage Manager Client on the same Windows workstation.

When these parameters are specified in client options files an additional parameter for the management class to be used also may be provided.. The include statement is used for two purposes.doc) Some Examples of Metacharacters on Selected Platforms Maples ESM Technologies Ltd 67 . unless you have the EXCLUDE. These metacharacters allow you to specify wild card processing. Some metacharacters differ depending on the client platform. Figure 35 Include/exclude processing The Include/Exclude list allows you to establish files which are to be included in or executed from backup processing. while the exclude statement is not checked during the archive processing.doc) \. . Metacharacters include: (Examples are in parenthesis) ? .doc) / ./user..\user.Unix: Match any directory (/.Windows: Match any directory (\. The metacharacters can also be used in the command line to specify the file specification on most commands. .doc) * .Define include/exclude option Two of the options that may be defined to a client options set are INCLUDE and EXCLUDE. The include is also used during archive to determine Management Class. The Include/Exclude list uses metacharacters to select files to be included or excluded..Match any number of characters as a wildcard (us*. The other is to associate a Management Class with a file or group of files..DIR statement.One and only one character matched as a wildcard (us?r. even when all the files within the directory are excluded. Directory type files are always included in the backup.... One is to specify exceptions to the exclude list..

dir The EXCLUDE. Maples ESM Technologies Ltd 68 . \. .DIR: Excludes a directory structure from backup and from being traversed during incremental backup.. \.. - Close Character Class ] ] ] ] ] ] ] Literal Escape \ \ \ \ \ \ \ Drive Separator none : : : : : : Figure 36 Exclude.. If a directory structure is excluded using EXCLUDE.. . .DIR. .... /. .  EXCLUDE. /...  EXCLUDE.. subdirectories in the excluded directory tree are not eligible for backup. Separator / \ \ \ : / Open Character Class [ [ [ [ [ [ [ Character Class Range .Objective AIX DOS OS/2 Win MAC Nov SUN Match one Character ? ? ? ? ? ? ? Match n Characters * * * * * * * Match n dirs.FILE: Can be abbreviated to EXCLUDE and excludes files from backup. \. .DIR statement excludes a directory structure from the internal traverse tree the TSM backup archive client builds internally before performing the backup and prevents directories and directory attributes from being backed up. Excluded directory structures are traversed during incremental backup... Dir.. Any INCLUDE statement that includes part of an excluded directory structure is ignored at backup time.

Backup-Archive Client Functions Maples ESM Technologies Ltd 69 .

The client is supported on a variety of platforms which might reside on an end-user workstation or a LAN server. In this unit we will discuss the various methods available to backup. archive and retrieve data. restore. and all your files that were created since the last backup. This function performs a journal based backup of those file systems previously selected for journaling. The incremental backup function does not back up files that are excluded by your include and exclude list Maples ESM Technologies Ltd 70 . Objectives Upon completion of this unit. you should be able to do the following:  Describe the kinds of backups possible  Use the TSM Backup-archive GUI to backup files from a client  Use the Command Line to backup files from a client  Use the dsmc REStore command to restore files that have been backed up  Use the Backup/Archive GUI client to restore files that have been backed up  Use the Backup/Archive GUI to archive client files  Retrieve Client Files that have been archived  Locate the volume where the archive/backup data is located Types of Backups Available from the GUI Figure 37 Incremental (Complete) and Journal-based Backup The incremental backup function (also known as incremental (complete)) backs up all your files that have changed since they were last backed up.Backup-Archive Client Functions Introduction The client communicates with the server and invokes the client functions of Storage Manager. and what options are available to customize these processes to fit your needs.

several conditions must be met.  A full incremental backup should have been run successfully at least once on the file system being backed up. These include:  The journal service must be set up to monitor the file system that contains the files and directories being backed up.  The file space image of the file system at the server cannot have been modified by an administrative command since the last full incremental. Tivoli Storage Manager does not use the journaling facility inherent in Windows NTFS file systems or any other journaled file system.  The storage management policy for the files being backed up cannot have been updated since the last full incremental. If you install the journal engine service and it is running.Journal-based Backup Figure 38 Journal-based backup is supported on all Windows clients. except the Windows Server 2003 64-bit client. In order to successfully perform a journal-based backup. Maples ESM Technologies Ltd 71 . then by default the incremental command will automatically perform a journal-based backup on selected file systems which are being monitored by the journal engine service.

you must have performed at least one full incremental backup of that entire disk or volume. Files that were renamed after the last incremental backup. 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. Incremental by Date however. but with a modification date earlier than the last incremental backup. are not backed up. but otherwise remain unchanged.Incremental by date (only) Figure 39 For a disk or volume to be eligible for incremental-by-date backups. Files added by the client after the last incremental backup. will not be backed up. 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. will not check for the following:  Frequency  New files  Deleted files  Changes in file attributes  No re-binding of files Maples ESM Technologies Ltd 72 . select the Incremental (date only) option from the type of backup pull-down menu or use the incrbydate option with the incremental command.

Performs an incremental backup without using the journal database backup. If there is no information. If it does find information in the database. the information about which files have been changed is relayed and then it performs an incremental backup. and asks for the backup information. 4. There is a search in the TSM database for the information about the client files.Incremental (without journal) Figure 40 The process of running an incremental (complete) backup goes as follows: 1. meaning there has never been a backup before. 3. a full backup will take place. Maples ESM Technologies Ltd 73 . The client starts the session. 2.

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. Maples ESM Technologies Ltd 74 . This type of backup is also known as "selective backup".Always backup selective Figure 41 Always attempts to back up the objects you selected.

If more than one backup version exists. client command line. Restore operation Restore is the process of copying a backup version of a user's file from the Storage Manager server to the workstation or LAN server.  Clients can request restore their own files  Can restore the files of others as authorized  Storage Manager server sends copy of file to client. Maples ESM Technologies Ltd 75 . Available only if the Tivoli Storage Manager Logical Volume Snapshot Agent is installed and available. A user may only restore files that he/she has backed up unless he/she has been granted authority to another person's backup files.Snapshot image backup Figure 42 Performs an online image backup of a volume in which the volume remains active and available for read and write operations during the backup. or via a schedule If a file is damaged. This item is visible only if the image plug-in is installed and the client is connecting to a Tivoli Storage Manager V5. The backup version remains in Storage Manager server. the user (Storage Manager client) can request without the aid of an administrator.1 or higher server. that the system restores the current or a specific backup version. but backup remains on server  User may be able to restore backed up files to a specific point in time  Users can do restores through GUI. Storage Manager sends a copy of the file to the client node. a user can restore the active backup version of the file or any inactive backup versions. When a user restores a backup version of a file.

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. Point-in-time restore Storage Manager uses a point-in-time (PIT) restore to restore a filespace. This is because the server is only notified about files that are deleted from a client filespace during an incremental backup. or file to the version equal to or before the point in time. Simply select the files you want to restore. You can also use the Find function to select files.  You can archive multiple files. subdirectories. a PIT restore can eliminate the effect of data corruption or recover a configuration to a prior date or time. are possible when incremental backups are run on the client. A user can also do restores through the GUI.  Archive is processed differently from backup in that a copy is stored on the server regardless of change status or frequency of backup.  Storage Manager uses to identify groups of archived files. directory. a user can restore backed up files to a specific point-in-time.  The archive function allows you to group important files by an associated description to archive and later retrieve.  Files can be grouped by description for easy retrieval. When a PIT restore is performed. they can choose to have Storage Manager erase the original files from their workstation after the files are archived. Support for PIT restore is essential to be able to recover a filespace or directory to a time when it was known to be in a good or consistent state.If the policy is properly set up. Point-in-time restores. or subdirectories together. client command line. directories. Incremental backups should run frequently enough to provide the necessary point-in-time resolution. For example.  When users archive files.  Archiving can be used by a user to request Storage Manager to copy files. Files that have been deleted from a client filespace between two incremental backups might be restored during a point-in-time restore. that do include deleted files. new files that have been created on the client after the PIT date are not deleted. or via a schedule. Archive Process  Archiving is used to preserve files for later use or for records.  A separate copy group is used for archive and backup so that each management class can handle the differences between backup and archive. A user can restore files to a location different from where they were backed up. Both the backup-archive GUI client and command line client support PIT restore when used with a Version 3 server. 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. and directories for long-term storage on media controlled by Storage Manager. Incremental backups are necessary to capture the fact that files have been deleted. Maples ESM Technologies Ltd 76 .

Policy Management Maples ESM Technologies Ltd 77 .

and for associating clients with a set of policies from which they may select. only one policy set in a domain can be active at a time.Policy Management Introduction Policy Management enables the administrator to determine a set of rules explaining how IBM Tivoli Storage Manager will treat data. one for backup and one for archive. however. policy sets. A set of attributes is called a copy group. These sets of rules are composed of policy domains. The administrator is also responsible for defining a default policy. may choose to override the default policy and select any other policy that is also in his/her policy domain. however. There is a backup copy group and an archive copy group. There are several ways that the client may do this:  On the Include option which is in the client's configuration or option file  On the DSMC Archive command  On the archive GUI panel Maples ESM Technologies Ltd 78 . Several elements comprise policies:  Policy Domain.  Management Class.  Policy Set. you should be able to do the following tasks to manage your IBM Tivoli Storage Manager environment by policy:  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  Create administrator/user to manage TSM by policy  Activate a Policy Set  Validate a Policy Set Policy Management Policies are created by the administrator and stored in the database on the server. A policy domain may contain a number of policy sets. management classes. The client. one that will be used unless another policy is explicitly selected. A group of nodes managed by the same set of policy constraints as defined by the policy sets. A collection of Management Class (MC) definitions. There are two sets of MC attributes. Objectives Upon completion of this unit. On the server. Policy Specification Policy is defined both at the client and at the server. A collection of management attributes describing backup and archive characteristics. an administrator is responsible for creating policies that will manage the client's data. and copy groups.

This is a grace period. BACKRETention=bkretvalue  Specifies the number of days (from the date of deactivation) to retain backup versions that are bound to a management class that no longer exists on the client's system. DEFine POlicyset domainname setname DESCription description Example: DEF Policyset Windows NEWDEF Domainname. The maximum length of the description is 255 characters. However. Use the DEFINE DOMAIN command as shown to define a new policy domain: DEFine DOMAIN <Domainname> DEScription=<description> BACKRETention=bkretvalue ARCHRETention=arch Example: DEF DOMAIN UNIX Domainname specifies the name of the policy domain to be defined. This parameter is optional. Related commands: Update Domain. DESCription=description  Specifies a text string that describes the policy domain. This parameter is required. Creating a policy set Use the following syntax for the DEFINE POLICYSET command to define a policy set in a specified policy domain. The clients/nodes may be running on the same or different platforms. but it is recommended to provide a meaningful description. Specifies the name of the policy domain to which the policy set belongs. ARCHRETention=arch  Specifies 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's system. This parameter is required. This is a grace period. Setname. Each domain may have one or more clients/nodes associated with it. This parameter is required. Creating a Policy Domain A policy domain provides you with a logical way of managing backup and archive policies for a group of nodes with common needs.1. Specifies the name you want to assign to the policy set. Delete Domain 2. A policy domain also contains a "grace period" backup and archive retention period that acts as a safety net to insure that backed up and archived data in a storage pool is not inadvertently deleted if it looses its backup or archive copy group. Maples ESM Technologies Ltd 79 . Each domain is an object stored in the Storage Manager database with a name from 1-30 characters. A client node can be associated with only one policy domain on a specific Storage Manager server. There is no limit to the number of policy domains that can be defined on a Storage Manager server. The maximum length of this name is 32 characters. a client/node may be registered (defined) to more than one server. Policy domain names should be meaningful. It is a collection of one or more nodes and one or more policies. The maximum length of this name is 30 characters. Some installations may find that they only require a single policy domain.

backup copy group.DESCription. The 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. policy set. and archive copy group. Each policy is stored on the server and named STANDARD. management class. It is advisable to use the description. as you become familiar with Tivoli Storage Manager you can tailor the standard policies. This parameter is optional. Figure 44 The 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. Describes the new policy set using a text string. Using the policy objects provided in Tivoli Storage Manager allows you to begin using IBMTivoli Storage Manager immediately. The maximum length of the description is 255 characters. Tivoli Storage Manager provides a predefined policy domain. since this will define the policy set once it becomes active. Default settings in the default domain These values come with Tivoli Storage Manager in the STANDARD Domain: Attribute Backup Default Archive Default Copy group name Standard Standard Copy type Backup Archive Copy frequency 0 days CMD (Command) Versions data exists Two versions Does not apply Versions data deleted One version Does not apply Retain extra versions 30 days Does not apply Retain only version 60 days Does not apply Copy serialization Shared static Shared static Copy mode Modified Absolute Copy destination Backuppool Archivepool Retain versions Does not apply 365 days Maples ESM Technologies Ltd 80 . The default is 30 days. REGister Client Node will fail if STANDARD is deleted.

Maples ESM Technologies Ltd 81 .

mode (always ABSolute).  Whether the file is to be backed up regardless of whether it has been modified since the last backup. and retention days for archive copies.  The number of days that an archive copy is to be retained.  There can be only one active policy set per policy domain Maples ESM Technologies Ltd 82 . retention days for all but last version. for all but the most recent backup version. Policy set Figure 45 Each policy set contains a default management class. and for the last remaining backup version that is no longer on the client's file system. # versions when file deleted.  The maximum number of different backup versions that may be retained for files no longer on the client's file system. mode (modified/absolute). and retention days for last version when file deleted The set of archive parameters include frequency (always Cmd). # versions. copy serialization. between backup and archive operations.  The minimal interval. Policy sets are used to implement different policies based on user and business requirements. in days. destination.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. in days.  The retention period.  Whether the file can be in use when a user attempts to backup or archive the file. The set of backup parameters include frequency. copy serialization. destination. and can contain any number of additional management classes.

 There may be any number of inactive policy sets. You must assign a default management class for a policy set before you can activate that policy set. The maximum length of this name is 30 characters. ASsign DEFMGmtclass domainname setname classname Command line to define policy set Use the following syntax for the DEFINE POLICYSET command to define a policy set in a specified policy domain. its contents are copied to a policy set that has the reserved name ACTIVE. The maximum length of the description is 255 characters. It is recommended that the default management class contain both an archive copy group and a backup copy group. Maples ESM Technologies Ltd 83 . DESCription. Specifies the name you want to assign to the policy set. This parameter is optional. Use the VALIDATE POLICYSET command to verify that a policy set is complete and valid prior to activating it: VALidate Policyset domainname setname Use the ACTIVATE POLICYSET command to specify a policy set as the ACTIVE policy set for a policy domain.  A copy group within the policy set specifies a copy storage pool as a destination. 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. Setname. ACTivate Policyset domainname setname When a policy set is activated. Validating a policy set 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. Once a change is made to a policy set by changing/adding a management class. the policy set must be activated to make it the "ACTIVE" policyset. Before you activate a policyset it is a good idea to validate it. Specifies the name of the policy domain to which the policy set belongs. It is advisable to use the description.  The policy set is stored in the server database  Policy set names may be from 1 to 30 characters  Collection of management classes  A policy set contains one default management class Use the ASSIGN DEFMGMTCLASS command to specify an existing management class as the default management class for a particular policy set. since this will define the policy set once it becomes active. This parameter is required. >>--DEFine POlicyset--domainname--setname-----> >--------------------------------------------------------------------> +-DESCription--=--description-+ Example: DEF Policyset Windows NEWDEF Domainname. Describes the new policy set using a text string. This parameter is required. and so forth. copy group.

 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
policyset that has been activated (copied to ACTIVE) and the contents of the
ACTIVEpolicyset. The original policy set can still be modified, but the copied definitionsin the
ACTIVE policy set can only be modified by activating another policy set.

Management class

A management class associates backup and archive groups with files, and specifies if and
how client node files are migrated to storage pools. A management class can contain one
backup or archive copy group, both a backup and archive copy group, or no copy groups.
Users can bind (that is, associate) their files to a management class throught the include-
exclude list.

Figure 46

How are files bound to management class

1. A Storage Manager client backs up, archives, or migrates a file.
2. The file is bound to either the default management class or a management class
specified in the client's include-exclude list.
3. If, according to the management class, the file is eligible for backup, archive, or space
management, the client sends the file and file information to the server.
4. The server checks the management class (space management) or copy group
(backup/archive) to determine where in server storage to store the file initially.

If there is not enough space in the initial storage pool, a migration is started. The server
stores the information about the file in the database.

Maples ESM Technologies Ltd 84

Figure 47

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. A management class
can have 0, 1, 2 copy groups. All copy groups are named STANDARD. Each management
class can contain up to two copy groups: one for backup files and one for archive files.

Maples ESM Technologies Ltd 85

Privilege Classes

Maples ESM Technologies Ltd 86

System privileges Figure 49 Maples ESM Technologies Ltd 87 .Privilege classes 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 Figure 48 The figure above shows how you can divide the administrative tasks through the five privilege classes.

such as:  Registering or removing administrators  Granting or revoking administrative authority  Locking or unlocking administrators from the server  Renaming administrators or updating administrator information  Defining or deleting policy statements  Importing or exporting data from the server  Canceling administrative background processes  Setting operating parameters for the server  Defining or deleting storage pools Set the following system parameters:  ACCounting  ACTlogretention  AUthentication  EVentretention  MAXCMDRetries  MAXSCHedsessions  PASSExp  QUERYSCHedperiod  RANDomize  REGistration  RETRYperiod  SCHEDMODes  SERVername Storage privileges Figure 50 Maples ESM Technologies Ltd 88 .An administrator with system privilege has the authority to perform Storage Manager Administrator tasks.

An administrator with unrestricted privileges can:  AUDit Volume  DEFine/DELete Volume  MOVE DATA  UPDate STGpool Restricted Storage Privilege Administrators with restricted storage privilege can issue a subset of the storage commands only for the storage pools for which they have been authorized. and all storage pools. recovery log. He or she can issue commands that affect all existing storage pool as well as any storage pools that are defined in future. They do not have the authority to manage the database or recovery log.Unrestricted Storage Privileges An administrator with unrestricted storage privilege has the authority to manage the database. An unrestricted storage administrator can’t define or delete storage pools. An administrator with restricted privileges can:  DEFine DBVolume/DEVclass/LOGVolume DBCOPY/LOGCopy  DELete DBVolume/DEVclass/LOGVolume  EXtend/REDuce DB/LOG  UPDate DEVclass Policy Privileges Figure 51 Maples ESM Technologies Ltd 89 .

An administrator with restricted policy privilege can issue a subset of the policy commands for the policy domains to which they have been authorized. An unrestricted policy administrator cannot define.An administrator with unrestricted policy privilege has the authority to manage the backup and archive services of the client nodes that are assigned to any policy domain. Operator privilege Figure 52 Administrators with operator privilege control the immediate operation of the TSM server and the availability of the storage media. an administrator with unrestricted policy privilege is automatically authorized to manage the new policy domains. An operator can do the following:  Disable the server to prevent clients from accessing the server  Enable the server for access by the clients  Cancel client-server sessions  Vary disk volumes on or off line for maintenance  Reset the error status for tape volumes  Manage tape mounts  Halt the server when necessary Analyst privilege Figure 53 Maples ESM Technologies Ltd 90 . When new policy domains are defined to the server. or copy policy domains. delete.

They can also trace TSM operations when necessary.An administrator with analyst privilege can issue commands to reset the counters that track server statistics. 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 The figure above shows how you can divide the administrative tasks through the five privilege classes. Maples ESM Technologies Ltd 91 .

Database & Recovery Log Maples ESM Technologies Ltd 92 .

you will learn how to choose the size and location of the database and recovery log. In this unit. you should be able to do the following tasks to manage your IBM Tivoli Storage Manager environment by policy:  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 Database and Recovery Log Figure 54 Maples ESM Technologies Ltd 93 . The Storage Manager recovery log is used to ensure the consistency and availability of the database.Database & Recovery Log Introduction The IBM Storage Manager database is used by the server to manage information about client files. Finally. You will also learn to configure the database and recovery log to optimize performance by using the BUFPOOLSIZE and LOGPOOLSIZE parameters. Objectives On completion of this unit. you will configure the database and recovery log for high availability with mirroring and the SPACETRIGGER parameter.

the server holds transaction log records in the recovery log buffer pool until they can be written to the recovery log. and registering a client node. archived. The transaction is then committed to the database. Reads a database page into the database buffer and updates it. the server: 1. Transactions Figure 55 To support multiple transactions from concurrent client sessions. The database does not store client data. Maples ESM Technologies Ltd 94 . When all records for a transaction are written to the recovery log. the database and recovery log are not always consistent. When a transaction occurs. IBM Tivoli Storage Manager updates the database. Therefore. and space- managed. backing up a client file. 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) The recovery log contains information about database updates that have not yet been committed. A page is a 4096 byte block that is transferred as a unit between memory and disk storage. At some point after a transaction is committed. Changes to the database are recorded in the recovery log to maintain a consistent database image. Updates can include activities such as defining a management class. the database points to the locations of the client files in the storage pools. These records remain in the buffer pool until the active buffer becomes full or IBM Tivoli Storage Manager forces log records to the recovery log. Changes resulting from transactions are held in the buffer pool temporarily and are not made to the database immediately. the server deletes the transaction record from the recovery log.The Tivoli Storage Manager database contains information that is needed for server operations and information about client data that has been backed up. Instead.

Writes the database page to the database. 3. 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. The page remains in the buffer pool until buffer space is needed for another page Maples ESM Technologies Ltd 95 . releasing it from the buffer pool.2.

When a change occurs. The recovery log can also be used for roll forward recovery of the database during disaster recovery. The server will never let the head overtake and overwrite the tail. but only to the extent necessary to perform redo processing on recovery. This enables uncommitted transactions to be rolled back during recovery so the database remains consistent. The log is treated as a circular array of blocks with the head (the newest log records) always chasing the tail (oldest records). they free up log space and allow the tail to move forward. If a failure occurs before a transaction is committed to the database. If the database needs to be recovered. Maples ESM Technologies Ltd 96 . the server uses the recovery point in the recovery log to bring the database back to its last point of consistency. normal mode and roll forward mode Normal Mode When the transaction log record is written to the recovery log.Recovery Log Transaction Modes Figure 56 The recovery log is used by the server to keep a record of all changes to the database. it must take some other action. The recovery log functions in two modes. The recovery log saves some records for transactions that have already been committed. As transactions commit. a recovery point is recorded in it and the data is committed to the database. the recovery log is updated with some transaction information prior to the database being updated. A point of consistency is a time when all recoverable information in the database matches the data managed by the server. the server rolls back any changes made to the database pages.

How Many Recovery Log Volumes Are Needed? In general. consider a second server. database access is predominately read-oriented. 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. Mirroring has little effect on the performance of the recovery log. The maximum database size limit is 5 terabytes. However.  Recovery log o Predominately write-oriented o Do not spread recovery log o Log file maximum size limit is 13 GB  Allocate on separate volumes How Many Database Volumes Are Needed? In general. The writes are done in a moving cursor format which does not lend itself to multiple volume optimization. Beyond this size. 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. access to the recovery log is predominately write-oriented with the writes and the few reads clustered together for the most part. Therefore. Space Allocation Figure 57  Database o Predominately read-oriented o Spread database for performance o It is recommended to limit the size of the database to 40GB. to reduce space used for logical volume manager overhead. keep the number of volumes reasonable (less than 12). fewer recovery log volumes are appropriate. Maples ESM Technologies Ltd 97 . The maximum log file size limit is 13 GB.Roll Forward Mode In roll forward mode all changes made to the database since the last backup are saved in the recovery log.

Be aware that the maximum amount of space used by the recovery log can vary significantly throughout the day. allowing database and recovery log data to span physical disks. 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. No reorganization of the database or recovery log is required. Estimating the size of the database Figure 59 Maples ESM Technologies Ltd 98 . IBM Tivoli Storage Manager treats all volumes associated with the database or with the recovery log as a single logical volume. as it is proportional to the transaction load on the system. because the amount of database space consumed grows in proportion to the number of object inserted into the database. which is the amount of space used at a specific point in time. As data is added. The logical volume manager maps data between logical and physical storage.Database and Recovery Log Space Figure 58 Volumes used to contain the database and the recovery log must be disk volumes. The maximum amount of space used by the database is more consistent with the utilization percentage. Tivoli Storage Manager tracks the percentage of utilization.

000 + 200.000 files migrated from client workstations might be in server storage.500. and space-managed files at 600 bytes per file is: (1.0 GB = 3 GB Cached and copy Storage pool sizes Figure 60 Maples ESM Technologies Ltd 99 . And storage policies call for retaining up to three copies of backed up files: 500.500. In addition. 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. The space required for all backed up.000 files  Archived files Up to 100. It is only done for moving from one storage pool to next.000 + 100. In the example below. archived. Caching is turned off by default.The size of your Storage Manager database depends on the number of client files to be stored and how Tivoli Storage Manager manages them.  Space-managed files Up to 200.000 client files might be backed up. the computations are probable maximums.000 files x 3 copies = 1. the less the required database space.  Overhead could increase the required space up to an additional 25%. the numbers are not based on the use of file aggregation. If you can estimate the maximum number of files that might be in server storage at any time. In general.000 files might be archived copies of client files.000) x 600 = 1.0 GB In this example. 3 x 1. Assume the following numbers for an IBM Tivoli Storage Manager system:  Backed up files Up to 500. the more that small files are aggregated. there are three database servers for which the database and recovery log are being sized.

1 GB. 100.4 GB is required for file versions and cached and copy storage pool files. During SQL queries of the Storage Manager server. Therefore. The size of the recovery log depends on the number of concurrent client sessions and the number of background processes executing on the server. If the average file size is about 10 KB. to backup the database and to restore the database. Note: The maximum size of the Recovery log increased now to 13GB.000) x 200 bytes = 343 MB Cached and copy storage pool files.500. you can roughly estimate the database size as from 1% to 5% of the required server storage space.Caching is enabled in the disk storage pool. about 100. For example. or 1 GB is occupied by cached files.000 files are in cache at any one time. Thus. If it is not practical to estimate the number of files to be covered by your storage management policies. 20% of the disk pool. The disk pool has a capacity of 5 GB and uses the default high migration threshold (90%) and low migration threshold (70%). Up to 50% additional space (or 0. your database should be between 1 GB and 5 GB.4 GB of data space. then. Attention: Be aware that the results are estimates. if you need 100 GB of server storage. require about 0. The database. The more complicated the queries.000 + 200. Significantly increasing the size of your recovery log could also significantly increase the time required to start the server. should be approximately 2.000 files x 200 bytes = 19 MB  Copy storage pool files All primary storage pools are backed up to the copy storage pool: (1.000 + 100. Note: The maximum number of concurrent client sessions is set in the server options. the more space required.7 GB) should be allowed for overhead. intermediate results are stored in temporary tables that require space in the free portion of the database. if migration begins at 90% and stops at 70%. The actual size of the database may differ from the estimate because of factors such as the number of directories and the length of the Maples ESM Technologies Ltd 100 . Overhead Figure 61 Up to this point approximately 1. the use of SQL queries requires additional database space. then.

issue the following command to display the current recovery log statistics: query log format=detail  The Cumulative Consumption field contains the log space in megabytes used by the server since the statistic was last reset. In this mode. the volume of Tivoli Storage Manager transactions affects how large you should make your recovery log. Estimating the Size of the Recovery Log In both normal mode and roll-forward mode. Begin with at least 12 MB for the recovery log. you should begin with at least 25 MB. you need to determine how much recovery log space is used between database backups. You can use the following procedure to make your estimate:  Start by setting your log mode to normal. In roll-forward mode you must also consider how often you perform database backups. Set your recovery log size to this increased value to account for periods of unusually high activity. you should extend the size of the log. Reducing the Database and Recovery Log Space Figure 62 Maples ESM Technologies Ltd 101 .  Repeat steps 2 and 3 over at least one week. In this way you are less likely to exceed your log space if your initial setting is too low for roll-forward mode. If you set your recovery log to 650 MB you should have sufficient space between daily backups. issue the following command to reset the statistic on the amount of recovery log space used since the last reset: reset logconsumption  Just before the next scheduled database backup. the recovery log keeps all transactions since the last database backup and typically requires significantly more space than is required in normal mode. over a period of a week the highest cumulative consumption value was 500 MB. You should periodically monitor your database and recovery log and adjust their sizes as necessary.  After a scheduled database backup. If you will be using the database backup and recovery functions in roll-forward mode. For example. if you plan daily incremental backups. Record the value. For example. you should check your daily usage over a period of time. As more clients are added and the volume of concurrent transactions increases. In roll-forward mode.  Increase the highest cumulative consumption value by 30 to 40 percent.path and file names.

For example. you must reduce the recovery log in 4 MB increments.  Use the REDUCE LOG command to decrease the amount of space that can be used by the recovery log. Tivoli Storage Manager rounds the number to the next 4 MB partition. To reduce the capacity of the recovery log. There is no notion of extending or reducing storage pool storage other than in volume increments Maples ESM Technologies Ltd 102 . Tivoli Storage Manager rounds the number to the next 4 MB partition. you must reduce the database in 4 MB increments. To reduce the capacity of the database.There are some additional commands that can be used to decrease both database and recovery log space. You should only need to run these commands if you want to re-design the volume layouts.  Use the REDUCE DB command to decrease the amount of space that can be used by the database. or if you add new volumes to Tivoli Storage Manager. if you specify 11 MB. If you do not specify the reduction in 4 MB increments. the server will round up to 12 MB when doing the extend or reduce operation. If you do not specify the reduction in 4 MB increments. This does not apply to data storage.

Monitoring and Logging Events Maples ESM Technologies Ltd 103 .

This lesson explains which messages can be logged and how client event monitoring is configured Figure 63  Which client messages can be logged as events and how these messages are formatted. Maples ESM Technologies Ltd 104 . These events can be passed on or reported to external sources.Monitoring and Logging Events Introduction Storage Manager provides the ability to log client messages as server events. you should be able to do the following:  Identify Client Message Candidates  Describe client event formatting  Query the activity log  Query the event log  Select from summary  Centralize Event logging on the TSM Server  Create Reports with the Select Statement  Control Event Logging Monitoring and Logging Events IBM Tivoli Storage Manager provides the ability to log certain client messages as events on the Storage Manager server. This unit introduces Storage Manager logging and monitoring functions. Objectives Upon completion of this unit.

displayed. and queried Maples ESM Technologies Ltd 105 . How client events are enabled and processed.  How client events are stored.

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

 Command line and GUI share same repository. The repository resides on both the client and the server.  Where applicable contains name of object. These client messages will be logged locally in the client schedule or error logs as appropriate. filespace Message Formatting Messages are seen in the following format: A N [ R S E ] # # # # [ I W E S]  R = Server  S = Client  E = Event Levels:  I = Info  W = Warning  E = Error  S = Severe Common Message Formatting Eligible messages are grouped in a common. The repository is shared by the command line and GUI clients.Client Event Formatting Common message repository  Contains new messages to facilitate central error logging. Maples ESM Technologies Ltd 107 .  Externally appear in 4000 . shared repository. Event formatting  Logged locally on client as ANS message. Event Formatting Client messages in the ANS4000 to ANS4999 range are eligible to be sent to the server as client events. Event Content Client event messages contain enough information to be processed outside of the context where the message occurred. and contains new messages for all client events and related event data. Event content  Contains enough information to be processed outside of the text where message occurred. Eligible client messages will be sent to the server as events using an ANE prefix instead of ANS.  Event message assigned ANE messages: ANE4007E.4999 range. The client assigns the correct message number and provides information about related object or filespace names and the server adds information such as timestamp. node name or any other relevant information.

Event message Maples ESM Technologies Ltd 108 . If the event has been enabled for the Storage Manager console it is shown on the console as soon as all the necessary information has been formatted. 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 filespace name and is sent to the Storage Manager server in this format.Client Event Processing Figure 65 When an eligible client message occurs. Message prefixes are  ANR . The server receives the event message and then adds information such as node name from where the event was received and the session number from which the original client error message originated.Server message  ANS .Client message  ANE .

The selection can be done by a list of individual message names. Maples ESM Technologies Ltd 109 . In this case the destination is the Storage Manager console. a node name has to be specified.Enabling Client Events for the Storage manager console Figure 66 When enabling events the following information has to be specified:  To which destination events are passed for monitoring. this can be specified by specifying ALL. the following ENABLE EVENT command can be issued by an administrator: tsm> enable events console error. The console will show all related event information. If all loggable messages should be tracked. severity types or a combination of both.  Which messages are enabled for the server console. For example. To enable all nodes to log events of ERROR or SEVERE severity to the Storage Manager console.severe node=* Client events are displayed as soon as they have occurred on the client and have been passed to the Storage Manager server.  Which client nodes participate in central logging. if the message occurred during a scheduled operation the schedule name is also displayed. When client events are enabled. There can be a list of node names specified or all by using the wildcard character (*).

Client events can be disabled for the activity log. To disable information events for the client node chocolate. the following administrator command would be used: tsm> disable events actlog info node=chocolate Maples ESM Technologies Ltd 110 . All client events are also enabled for the server activity log by default.Storing Clients in the Activity Log Figure 67 Storage Manager server events are always stored in the activity log and cannot be disabled. This is because server information in the activity log is often needed to resolve critical situations.

The following parameters have been added for extended event querying: Parameter Description ORIGINATOR Event origin: SERVER. or ALL events. Owner name: to display all events that have been logged for a OWNERNAME particular owner.Querying Client Events in the Activity Log Figure 68 The QUERY ACTLOG command has been updated in order to enable querying of centrally logged client events from the Storage Manager activity log. Client node name: to display all events that derived from this NODENAME node. Session ID of Storage Manager client session: to display all SESSION ID logged events that originated from the specified client session. associated with the DAILY_INC client schedule: tsm> query actlog begindate=-7 originator=client node=chocolate sched=daily_inc Maples ESM Technologies Ltd 111 . CLIENT. SCHEDULENAME and Schedule name and related domain name: to display all events DOMAINNAME that have been logged for the specified scheduled client activity. The following example command queries for any client events in the last seven days from the node named chocolate.

Backing up the Database Maples ESM Technologies Ltd 112 .

you will be able to do the following:  Backup the IBM Tivoli Storage Manager database  Recover the IBM Tivoli Storage Manager database  Backup the storage pools  Recover the storage pools Backing up the database Types of database backups  Full backup  Incremental backups (default)  Database Out-of Band (Snapshot) backup Full Backup Full backup is required when  Database has never been backed up. Maples ESM Technologies Ltd 113 .  Recovery log mode changed to roll forward (default = normal). You can run regular or incremental backups as often as needed to ensure that the database can be restored to an acceptable point in time.Backing up the database Introduction This unit covers backing up and recovering the Tivoli Storage Manager database. Storage Manager can perform regular and incremental backups of the database to tape while the server is running and available to clients. and storage pools.  Database has been extended or reduced. With the Storage Manager recovery log in normal mode. You can provide even more complete protection if you specify that Storage Manager run roll forward mode.  Maximum incremental backups reached. With Storage Manager in roll-forward mode and with an intact recovery log. you can recover the database up to its most current status. recovery log. 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. Objectives Upon completing this unit.

Full Backup versus Incremental Backup

Figure 69

For backups, an administrator can weigh the trade-offs between running regular backups and
running incremental backups.

A regular backup takes longer to run than an incremental because it copies the entire
database. However, recovery time is faster with a regular backup because only one set of
volumes needs to be loaded to restore the entire database. A regular backup is required
under specific conditions, but an administrator can choose to run as many as 32 incremental
backups between each regular 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.

Database (out-of-band) snapshot Backup

A database out-of-band (snapshot backup)

 Does not interrupt the normal backup series.
 Can be taken off-site.
 Normal backup series stays onsite for availability.
 Is integrated into Disaster Recovery Manager processing as well as volume history
processing.

A snapshot backup is a full backup which does not interrupt the full + incremental backup
series, in other words, it is 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 Storage Manager database to the point-in-time when the snapshot was performed.

Maples ESM Technologies Ltd 114

Database Backup Command

Figure 70

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
DEVclass=devclassname device class definitions. If you do not have this file and your 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
Type=typevalue
value is INCREMENTAL.
Specifies the volumes to use for the backup. You can specify more than one
VOLumenames=volname volume by separating each volume name with a comma, with no intervening
spaces.
Specifies whether scratch volumes can be used for the backup. This
Scratch=scratchvalue
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, 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

Maples ESM Technologies Ltd 115

Database Backup Related Commands

Figure 71

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:

 Volumes not in storage pools.
 Volumes used to back up a Storage Manager database (regular or incremental).
 Volumes used to dump a Storage Manager database.
 Volumes used to export administrator, node, policy, or server data.
 Backup sets.

Query VOLHistory Type=typevalue
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 Description

All Specifies that all history information is displayed.
Specifies to display only records that contain information about volumes used for
DBBackup
backups (regular or incremental).
Database Out-of Band (snapshot) backup is a full backup which does not
DBSnapshot
interrupt the current full+incremental backup series.
Specifies to display only records that contain information about volumes used for
DBDump
online database dumps (done before installation of Version 2 Release 1).
Specifies to display only records that contain information about volumes used for
EXPort
exporting data.

Maples ESM Technologies Ltd 116

the files are deleted. the volumes return to scratch status if they were acquired by Storage Manager as scratch volumes. such as storage pool volumes or other database backups. Do not delete sequential volume history information until you no longer need it. or export volumes that reside in automated libraries unless you want to return the volumes to scratch status. For example. For scratch volumes with device type FILE. database backup. When the DELETE VOLHISTORY command removes volume information for database dump. you may want to delete information about volumes used for obsolete database backups. Maples ESM Technologies Ltd 117 .DELETE VOLHISTORY Use the DELETE VOLHISTORY command to delete sequential volume history information collected by the server when the information is longer needed. When volume history information about volumes not in storage pools is deleted. database backup. 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. the volumes are automatically returned to scratch status if they reside in automated libraries. Do not delete the volume history information for database dump. or export volumes.