Chapter 1.

Introducing Tivoli Storage Manager

Tivoli Storage Manager is an enterprise-wide storage management application. It provides automated storage management services to workstations, personal computers, and file servers from a variety of vendors, with a variety of operating systems. Tivoli Storage Manager includes the following components: Server Server program The server program provides backup, archive, and space management services to the clients. You can set up multiple servers in your enterprise network to balance storage, processor, and network resources. Administrative interface The administrative interface allows administrators to control and monitor server activities, define management policies for clients, and set up schedules to provide services to clients at regular intervals. Administrative interfaces available include a command-line administrative client and a Web browser interface. Tivoli Storage Manager allows you to manage and control multiple servers from a single interface that runs in a Web browser. Server database and recovery log The Tivoli Storage Manager server uses a database to track information about server storage, clients, client data, policy, and schedules. The server uses the recovery log as a scratch pad for the database, recording information about client and server actions while the actions are being performed. Server storage The server can write data to hard disk drives, disk arrays and subsystems, stand-alone tape drives, tape libraries, and other forms of random- and sequential-access storage. The media that the server uses are grouped into storage pools. The storage devices can be connected directly to the server, or connected via local area network (LAN) or storage area network (SAN). Client Nodes A client node can be a workstation, a personal computer, a file server, a network-attached storage (NAS) file server, or even another Tivoli Storage Manager server. The client node has Tivoli Storage Manager client software installed (except for NAS file servers using NDMP). A client node is registered with the server. Backup-archive client The backup-archive client allows users to maintain backup versions of files, which they can restore if the original files are lost or damaged. Users can also archive files for long-term storage and retrieve the archived files when necessary. Users themselves or administrators can register workstations and file servers as client nodes with a Tivoli Storage Manager server. The storage agent is an optional component that may also be installed on a system that is a client node. The storage agent enables LAN-free data movement for client operations. Application program interface (API) The API allows you to enhance existing applications to use the backup, archive, restore, and retrieve services that Tivoli Storage Manager provides. Tivoli Storage Manager API clients can register as client nodes with a Tivoli Storage Manager server.

Tivoli Storage Manager supports separately licensed, optional products. These include: Tivoli Data Protection for applications (application clients) Application clients allow users to perform online backups of data for applications such as database programs. After the application program initiates a backup or restore, the application client acts as the interface to Tivoli Storage Manager. The Tivoli Storage Manager server then applies its storage management functions to the data. The application client can perform its functions while application users are working, with minimal disruption. Tivoli Data Protection for NDMP The Tivoli Data Protection for NDMP product allows you to use Tivoli Storage Manager with the Network Data Management Protocol (NDMP) to back up and restore file systems stored on a network-attached storage (NAS) file server. The data on the NAS file server is backed up to a tape library. See Chapter 6, Setting Up Tivoli Data Protection for NDMP for more information. Tivoli Space Manager Tivoli Space Manager provides space management services for workstations on some platforms. Tivoli Space Manager automatically migrates files that are less frequently used to server storage, freeing space on the workstation. The migrated files are also called spacemanaged files. Users can recall space-managed files automatically simply by accessing them as they normally would from the workstation. Tivoli Space Manager is also known as the hierarchical storage management (HSM) client. For information about supported operating systems for clients, see the Tivoli Storage Manager Web site: http://www.tivoli.com/support/storage_mgr/tivolimain.html Client programs such as the backup-archive client and the HSM client (space manager) are installed on systems that are connected through a LAN and are registered as client nodes. From these client nodes, users can back up, archive, or migrate files to the server. The following sections present key concepts and information about Tivoli Storage Manager. The sections describe how Tivoli Storage Manager manages client files based on information provided in administratordefined policies, and manages devices and media based on information provided in administrator-defined Tivoli Storage Manager storage objects. The final section gives an overview of tasks for the administrator of the server, including options for configuring the server and how to maintain the server.
Concepts: "How Tivoli Storage Manager Stores Client Data" How the Server Manages Storage Configuring and Maintaining the Server

How Tivoli Storage Manager Stores Client Data

Tivoli Storage Manager policies are rules that determine how the client data is stored and managed. The rules include where the data is initially stored, how many backup versions are kept, how long archive copies are kept, and so on. You can have multiple policies and assign the different policies as needed to specific clients, or even to specific files.

Policy assigns a location in server storage where data is initially stored. Server storage is divided into storage pools that are groups of storage volumes. Server storage can include hard disk, optical, and tape volumes. When you install Tivoli Storage Manager, you have a default policy that you can use. For details about this default policy, see The Standard Policy. You can modify this policy and define other policies. Clients use Tivoli Storage Manager to store data for any of the following purposes: Backup and restore The backup process copies data from client workstations to server storage to ensure against loss of data that is regularly changed. The server retains versions of a file according to policy, and replaces older versions of the file with newer versions. Policy includes the number of versions and the retention time for versions. A client can restore the most recent version of a file, or can restore earlier versions. Archive and retrieve The archive process copies data from client workstations to server storage for long-term storage. The process can optionally delete the archived files from the client workstations. The server retains archive copies according to the policy for archive retention time. A client can retrieve an archived copy of a file. Instant archive and rapid recovery Instant archive is the creation of a complete set of backed-up files for a client. The set of files is called a backup set. A backup set is created on the server from the most recently backed-up files that are already stored in server storage for the client. Policy for the backup set consists of the retention time that you choose when you create the backup set. You can copy a backup set onto compatible portable media, which can then be taken directly to the client for rapid recovery without the use of a network and without having to communicate with the Tivoli Storage Manager server. Migration and recall Migration, a function of the Tivoli Space Manager program, frees up client storage space by copying files from workstations to server storage. On the client, the Tivoli Space Manager program replaces the original file with a stub file that points to the original in server storage. Files are recalled to the workstations when needed. This process is also called hierarchical storage management (HSM). Once configured, the process is transparent to the users. Files are migrated and recalled automatically. Policy determines when files are considered for automatic migration. On the UNIX systems that support the Tivoli Space Manager program, policies determine whether files must be backed up to the server before being migrated. Space management is also integrated with backup. If the file to be backed up is already migrated to server storage, the file is backed up from there. Figure 1 shows how policy is part of the Tivoli Storage Manager process for storing client data.

Figure 1. How Tivoli Storage Manager Controls Backup, Archive, and Migration Processes

The steps in the process are as follows: (1) A client initiates a backup, archive, or migration operation. The file involved in the operation is bound to a management class. The management class is either the default or one specified for the file in client options (the client's include-exclude list). (2) If the file is a candidate for backup, archive, or migration based on information in the management class, the client sends the file and file information to the server. (3) The server checks the management class that is bound to the file to determine the destination, the name of the Tivoli Storage Manager storage pool where the server initially stores the file. For backed-up and archived files, destinations are assigned in the backup and archive copy groups, which are within management classes. For space-managed files, destinations are assigned in the management class itself. The storage pool can be a group of disk volumes, tape volumes, or optical volumes. (4) The server stores the file in the storage pool that is identified as the storage destination. The Tivoli Storage Manager server saves information in its database about each file that it backs up, archives, or migrates. If you set up server storage in a hierarchy, Tivoli Storage Manager can later migrate the file to a storage pool different from the one where the file was initially stored. For example, you may want to set up server storage so that Tivoli Storage Manager migrates files from a disk storage pool to tape volumes in a tape storage pool.

Files remain in server storage until they expire and expiration processing occurs, or until they are deleted from server storage. A file expires because of criteria that are set in policy. For example, the criteria include the number of versions allowed for a file and the number of days that have elapsed since a file was deleted from the client's file system. For information on assigning storage destinations in copy groups and management classes, and on binding management classes to client files, see Chapter 12, Implementing Policies for Client Data. For information on managing the database, see Chapter 18, Managing the Database and Recovery Log. For information about storage pools and storage pool volumes, see Chapter 9, Managing Storage Pools and Volumes.

Options for Data Protection

Tivoli Storage Manager provides a variety of backup and archive operations, allowing you to select the right protection for the situation. Table 1 shows some examples of the protection options. Table 1. Examples of Meeting Your Goals with Tivoli Storage Manager For this goal... Back up files that are on a user's workstation, and have the ability to restore individual files. Do this... Use the backup-archive client to perform incremental backups or selective backups.

Back up a file server, and have the ability to restore Use the backup-archive client to perform individual files. incremental backups or selective backups. If the file server is a network-attached storage file server that is supported, you can use Tivoli Data Protection for NDMP to perform image backups. Make restore media portable, or make restores easier to perform remotely. Provide the ability to more easily restore the entire contents of a single logical volume, instead of restoring individual files. Use the backup-archive client to perform incremental backups, and then generate backup sets by using the Tivoli Storage Manager server. Use the backup-archive client to perform logical volume backups (also called image backups).

Set up records retention to meet legal or other long- Use the backup-archive client to occasionally term storage needs. perform archiving. To ensure that the archiving occurs at the required intervals, use central scheduling. Create an archive for a backup-archive client, from data that is already stored for backup. Use the backup-archive client to perform incremental backups, and then generate a backup set by using the Tivoli Storage Manager server. This is also called instant archive. Use the backup-archive client to regularly perform incremental backups (either manually or automatically through schedules). Then do one of the following:

Provide the ability to restore data to a point in time.

Set up policy to ensure that data is preserved in server storage long enough to provide the required service level. See Setting Policy to Enable Point-in-Time Restore for Clients for details. Create backup sets for the backup-archive client on a regular basis. Set the retention time to provide the required service level. See Creating and Using Client Backup Sets for details.

Save a set of files and directories before making significant changes to them.

Use the backup-archive client to archive the set of files and directories. If this kind of protection is needed regularly, consider creating backup sets from backup data already stored for the client. Using backup sets instead of frequent archive operations can reduce the amount of metadata that must be stored in the server's database.

Back up data for an application that runs continuously, such as a database application (for (R) example, DB2 or Oracle) or a mail application (R) (TM) (Lotus Domino ). Exploit disk hardware capable of data snapshots.

Use the appropriate application client. For example, use Tivoli Data Protection for Lotus Domino.

Use the appropriate component that supports the hardware, such as Tivoli Data Protection for IBM (TM) Enterprise Storage Server . Use the backup-archive client with centrally scheduled backups that run during off-shift hours. Monitor the schedule results.

Make backups transparent to end users.

Reduce the load on the LAN by moving backup data Use LAN-free data movement or, for supported network-attached storage (NAS) file servers, use over your SAN. Tivoli Data Protection for NDMP. Schedule the backups of client data to help enforce the data management policy that you establish. If you schedule the backups, rather than rely on the clients to perform the backups, the policy that you establish is followed more consistently. See Chapter 14, Scheduling Operations for Client Nodes. The standard backup method that Tivoli Storage Manager uses is called progressive incremental backup. It is a unique and efficient method for backup. See Progressive Incremental Backup Compared with Other Backup Types. Table 2 summarizes the client operations that are available. In all cases, the server tracks the location of the backup data in its database. Policy that you set determines how the backup data is managed. Table 2. Summary of Client Operations Type of Description Usage Restore options For more

operation Progressive The standard method of incremental backup used by Tivoli backup Storage Manager. After the first, full backup of a client system, incremental backups are done. Incremental backup by date is also available. No additional full backups of a client are required after the first backup. Selective backup Backup of files that are selected by the user, regardless of whether the files have changed since the last backup. Allows users to protect a subset of their data independent of the normal incremental backup process. Helps ensure complete, effective, policy-based backup of data. Eliminates the need to retransmit backup data that has not been changed during successive backup operations.

information The user can restore just See the version of the file Incremental that is needed. Backup and BackupTivoli Storage Manager Archive does not need to restore Installation a base file followed by and User's incremental backups. Guide. This means reduced time and fewer tape mounts, as well as less data transmitted over the network.

The user can restore just See Selective the version of the file Backup and Backupthat is needed. Archive Tivoli Storage Manager Installation does not need to restore and User's a base file followed by Guide. incremental backups. This means reduced time and fewer tape mounts, as well as less data transmitted over the network. The base file plus a maximum of one subfile is restored to the client. See Enabling Clients to Use Subfile Backup and BackupArchive Installation and User's Guide.

Adaptive subfile backup

A backup method that backs up only the parts of a file that have changed since the last backup. The server stores the base file (the complete initial backup of the file) and subsequent subfiles (the changed parts) that depend on the base file. The process works with either the standard progressive incremental backup or with selective backup. Applicable to clients on (R) Windows systems.

Maintains backups of data while minimizing connect time and data transmission for the backup of mobile and remote users.

Journal-

Aids all types of backups Reduces the amount of

Journal-based backup

See Backup-

based backup

(progressive incremental backup, selective backup, adaptive subfile backup) by basing the backups on a list of changed files. The list is maintained on the client by the journal engine service of Tivoli Storage Manager. Full volume backup.

time required for backup. The files eligible for backup are known before the backup operation begins. Applicable to clients on (R) Windows NT and Windows 2000 systems.

has no effect on how files are restored; this depends on the type of backup performed.

Archive Installation and User's Guide.

Image backup

Allows backup of an The entire image is entire file system or raw restored. volume as a single Nondisruptive, on-line backup is possible for object. Can be selected Windows 2000 clients by by backup-archive using the Tivoli Storage clients on UNIX(R) and Manager snapshot Windows systems. function.

See Policy for Logical Volume Backups and BackupArchive Installation and User's Guide. See Chapter 6, Setting Up Tivoli Data Protection for NDMP. See Tivoli Data Protection for IBM ESS for Oracle Databases DB2 UDB Installation and User's Guide, Tivoli Data Protection for IBM ESS for R/3 Installation and User's Guide, and Tivoli Data Protection for EMC Symmetrix for R/3 Installation

Image backup with differential backups Backup using hardware snapshot capabilities

Full volume backup, which can be followed by subsequent differential backups. A method of backup that exploits the capabilities of IBM Enterprise Storage Server (TM) FlashCopy and EMC TimeFinder to make copies of volumes used by database servers. The Tivoli Data Protection for applications and databases then uses the volume copies to back up the database volumes.

Used only for the image backups of NAS file servers, performed by using Tivoli Data Protection for NDMP.

The full image backup plus a maximum of one differential backup are restored.

Implements highSee the referenced efficiency backup and publications for details. recovery of businesscritical applications while virtually eliminating backup-related downtime or user disruption on the database server.

and User's Guide. Archive The process creates a Use for maintaining The selected version of copy of files and stores copies of vital records the file is retrieved on them for a specific time. for legal or historical request. purposes. Note: If you need to frequently create archives for the same data, consider using instant archive (backup sets) instead. Frequent archive operations can create a large amount of metadata in the server database resulting in increased database growth and decreased performance for server operations such as expiration. Frequently, you can achieve the same objectives with incremental backup or backup sets. Although the archive function is a powerful way to store inactive data with fixed retention, it should not be used on a frequent and large scale basis as the primary See Archive and BackupArchive Installation and User's Guide.

backup method. Instant archive The process creates a backup set of the most recent versions of the files for the client, using files already in server storage from earlier backup operations. Use when portability of the recovery media or rapid recovery of a backup-archive client is important. Also use for efficient archiving. The files are restored directly from the backup set. The backup set resides on media that can be mounted on the client system, such as a CD, a tape drive, or a file system. The Tivoli Storage Manager server does not have to be contacted for the restore process, so the process does not use the network or the server. See Creating and Using Client Backup Sets.

Progressive Incremental Backup Compared with Other Backup Types

Tivoli Storage Manager has a unique, efficient method for its standard backups, as well as a number of other methods that are summarized in Table 2. The standard method that Tivoli Storage Manager uses is progressive incremental backup. The terms differential and incremental are often used to describe backups. The terms usually have the following meanings: A differential backup backs up files that have changed since the last full backup. o If a file changes after the full backup, the changed file is backed up again by every subsequent differential backup. o All files are backed up at the next full backup. An incremental backup backs up only files that have changed since the last backup, whether that backup was a full backup or another incremental backup. o If a file changes after the full backup, the changed file is backed up only by the next incremental backup, not by all subsequent incremental backups. o If a file has not changed since the last backup, the file is not backed up.

Tivoli Storage Manager takes incremental backup one step further. After the initial full backup of a client, no additional full backups are necessary because the server, using its database, keeps track of whether files need to be backed up. Only files that change are backed up, and then entire files are backed up, so that the server does not need to reference base versions of the files. This means savings in resources, including the network and storage. If you choose, you can force full backup by using the selective backup function of a client in addition to the incremental backup function. You can also choose to use adaptive subfile backup, in which the server stores the base file (the complete initial backup of the file) and subsequent subfiles (the changed parts) that depend on the base file.

Additional Protection: Storage Pool and Server Database Backups

Built into the server are additional levels of protection for client data:

You can back up storage pools. The data is backed up to copy storage pools, which the server can automatically access if needed to retrieve a file. See Storage Pool Protection: An Overview. You can back up the server's database. The database is key to the server's ability to track client data in server storage. See Database and Recovery Log Protection: An Overview.

These backups can become part of a disaster recovery plan, created automatically by Tivoli Disaster Recovery Manager. See Chapter 23, Using Tivoli Disaster Recovery Manager.

How Data Moves to Server Storage

The Tivoli Storage Manager client traditionally sends its data to the server over the LAN. The server then transfers the data to a device that is attached to the server. With the advent of SAN and network-attached storage, however, Tivoli Storage Manager offers options that enable you to minimize use of the LAN and the use of the computing resources of both the client and the server. LAN-free data movement allows storage agents that are installed on client nodes to move data without sending the data over the LAN to the server. See LAN-Free Data Movement. For network-attached storage, use Tivoli Data Protection for NDMP to avoid data movement over the LAN. See Tivoli Data Protection for NDMP Backups.

Consolidating Backed-up Data for Clients

By grouping the backed-up data for a client, you can minimize the number of media mounts required for client recovery. The server offers you methods for doing this: Collocation The server can keep each client's files on a minimal number of volumes within a storage pool. Because client files are consolidated, restoring collocated files requires fewer media mounts. However, backing up files from different clients requires more mounts. You can have the server collocate client data when the data is initially stored in server storage. If you have a storage hierarchy, you can also have the data collocated when the server migrates the data from the initial storage pool to the next storage pool in the storage hierarchy. Another choice you have is the level of collocation. You can collocate by client or by file space per client. Your selection depends on the size of the file spaces being stored and the restore requirements. See Keeping a Client's Files Together: Collocation. Backup set creation You can generate a backup set for each backup-archive client. A backup set contains all active backed-up files that currently exist for that client in server storage. The process is also called instant archive. The backup set is portable and is retained for the time that you specify. Creation of the backup set consumes more media because it is a copy in addition to the backups that are already stored. See Creating and Using Client Backup Sets.

Moving data for a client node You can consolidate data for a client node by moving the data within server storage. You can move it to a different storage pool, or to other volumes in the same storage pool. See Moving Data by Node.

How the Server Manages Storage

Through the server, you manage its storage -- the devices and media used to store client data. The server integrates the management of storage with the policies that you define for managing client data.

Tivoli Storage Manager Device Support

Tivoli Storage Manager supports the use of a variety of devices for server storage. Tivoli Storage Manager can use direct-attached storage as well as network-attached storage. A current list is available at the Tivoli Storage Manager Web site: http://www.tivoli.com/support/storage_mgr/tivolimain.html Tivoli Storage Manager represents physical storage devices and media with the following administratordefined objects: Library A library is one or more drives (and possibly robotic devices) with similar media mounting requirements. Drive Each drive represents a drive mechanism in a tape or optical device. Data mover A data mover represents a device that accepts requests from Tivoli Storage Manager to transfer data on behalf of the server. Data movers transfer data between storage devices. Path A path represents how a source accesses a destination. For example, the source can be a server, and the destination can be a tape drive. A path defines the one-to-one relationship between a source and a destination. Data may flow from the source to the destination, and back. Device class Each device is associated with a device class that specifies the device type and how the device manages its media. Storage pools and volumes A storage pool is a named collection of volumes that have the same media type. A storage pool is associated with a device class. For example, an 8mm tape storage pool contains only 8mm tape volumes. A storage pool volume is associated with a specific storage pool. For details about device concepts, see Chapter 2, Introducing Storage Devices.

Migrating Data through the Storage Hierarchy

You can organize the server's storage pools into one or more hierarchical structures. This storage hierarchy allows flexibility in a number of ways. For example, you can set policy to have clients send their backup data to disks for faster backup operations, then later have the server automatically migrate the data to tape. See Overview: The Storage Pool Hierarchy.

Removing Expired Data

Policy that you define controls when client data automatically expires from the Tivoli Storage Manager server. The expiration process is how the server implements the policy. For example, you have a backup policy that specifies that three versions of a file be kept. File A is created on the client, and backed up. Over time, the user changes file A, and three versions of the file are backed up to the server. Then the user changes file A again. When the next incremental backup occurs, a fourth version of file A is stored, and the oldest of the four versions is eligible for expiration. To remove data that is eligible for expiration, a server expiration process marks data as expired and deletes metadata for the expired data from the database. The space occupied by the expired data is then available for new data. You control the frequency of the expiration process by using a server option, or you can start the expiration processing by command or scheduled command. See Running Expiration Processing to Delete Expired Files.

Reclaiming Media for Reuse

As server policies automatically expire data, the media where the data is stored accumulates unused space. Other products might require you to implement a tape rotation scheme that allows you to reuse the media only when all data on the media has expired. The Tivoli Storage Manager server implements a different process, called reclamation, that allows you to reuse media without traditional tape rotation. Reclamation is a server process that automatically defragments media by consolidating unexpired data onto other media when the free space on media reaches a defined level. The reclaimed media can then be used again by the server. Reclaiming media allows the automated circulation of media through the storage management process. Use of reclamation can help minimize the number of media that you need to have available.

Configuring and Maintaining the Server

The server comes with many defaults set so that clients can begin using its services immediately. The amount and importance of the data protected by Tivoli Storage Manager, your business process requirements, and other factors make it likely that you need to adjust and customize the server's behavior. Your changing storage needs and client requirements can mean on-going configuration changes and monitoring. The server's capabilities are extensively described in this guide. To get an introduction to the tasks available to an administrator of Tivoli Storage Manager, read the following sections:

Interfaces to Tivoli Storage Manager Configuring and Managing Server Storage Managing Client Operations Maintaining the Server Protecting the Server

Interfaces to Tivoli Storage Manager

Tivoli Storage Manager has the following types of interfaces: Graphical user interfaces. For the clients, there are graphical user interfaces for the backup-archive client and the space manager client (if installed, on supported operating systems). For information about using the interfaces, see the online information or see Quick Start. Web interfaces for server administration and for the backup-archive client. The administrative Web interface allows you to access Tivoli Storage Manager server functions (R) from any workstation with a Web browser that has the appropriate support for Java . The interface also allows Web access to the command line. See Quick Start for information about the administrative Web interface. The Web backup-archive client (Web client) allows an authorized user to remotely access a client to run backup, archive, restore, and retrieve processes. The Web browser must have the appropriate support for Java. See Backup-Archive Installation and User's Guide for requirements. The command-line interface. For information about using the command-line interface of the administrative client, see Administrator's Reference. For information about using the command-line interface of the backuparchive client and other clients, see Backup-Archive Installation and User's Guide for that client. The application program interface. For more information, see Tivoli Storage Manager Using the Application Program Interface . Access to information in the server's database via standard SQL SELECT statements. For reporting purposes, the Tivoli Storage Manager product also provides an ODBC driver. The driver allows you to use a spreadsheet or database program to query the server database for information. See Using SQL to Query the Tivoli Storage Manager Database.

Customizing the Server with the Server Options File

Server options allow you to customize the server and its operations. Some examples of what these options affect are: Server communications Storage

Database and recovery log operations Client transaction performance

Server options are in the server options file. Some options can be changed and made active immediately by using the command, SETOPT. Most server options are changed by editing the server options file and then halting and restarting the server to make the changes active. In this book, specific server options are discussed where they are applicable. See Administrator's Reference for details about the server options file and reference information for all server options.

Configuring and Managing Server Storage

Configuring and managing storage for efficiency and capacity are important tasks for an administrator. The server uses its storage for the data it manages for clients. The storage can be a combination of devices: Disk Tape drives that are either manually operated or automated Optical drives Other drives that use removable media

The devices can be locally attached, or accessible through a SAN. Key decisions in configuring and managing the storage include: Selecting the devices and media that will form the server storage, including library devices that will be shared among Tivoli Storage Manager servers Designing the storage hierarchy for efficient backups and optimal storage usage Using product features that allow the server to provide services to clients while minimizing traffic on the communications network: o LAN-free data movement o Data movement using NDMP to protect data on network-attached storage (NAS) file servers Using the Tivoli Storage Manager product to help you to manage the drives and media, or using an external media manager to do the management outside of the Tivoli Storage Manager product.

For an introduction to key storage concepts, see Chapter 2, Introducing Storage Devices.

Using Hard Disk Devices with Tivoli Storage Manager

Hard disk devices can be used with Tivoli Storage Manager for two purposes: Storage of the database and recovery log Storage of client data that is backed up, archived, or migrated from client nodes

The server can store data on hard disk by using random access volumes (device type of DISK) or sequential access volumes (device type of FILE). The Tivoli Storage Manager product allows you to exploit disk storage in ways that other products do not. You can have multiple client nodes back up to the same disk storage pool at the same time, and still keep the data for the different client nodes separate. Other products also allow you to back up different

systems at the same time, but only by interleaving the data for the systems, leading to slower restore processes. If you have enough disk storage space, data can remain on disk permanently or temporarily, depending on the amount of disk storage space that you have. Restore process performance from disk can be very fast compared to tape. You can have the server later move the data from disk to tape; this is called migration through the storage hierarchy. Other advantages to this later move to tape include: Ability to collocate data for clients as the data is moved to tape Streaming operation of tape drives, leading to better tape drive performance More efficient use of tape drives by spreading out the times when the drives are in use

For information about setting up storage pools on disk devices, see Chapter 3, Using Magnetic Disk Devices. For information about setting up a storage hierarchy, see Overview: The Storage Pool Hierarchy.

Using Removable Media Devices with Tivoli Storage Manager

Removable media devices can be used with Tivoli Storage Manager for the following purposes: Storage of client data that is backed up, archived, or migrated from client nodes Storage of database backups The exporting of data, to move the data to another server

Attaching and Configuring Devices

For information about configuring your removable media devices, see Chapter 4, Attaching Devices to the Server System and Chapter 5, Configuring Storage Devices.

Classifying Devices by Device Type

A device class represents a set of storage devices with similar availability, performance, and storage characteristics. You must define device classes for the drives available to the Tivoli Storage Manager server. You specify a device class when you define a storage pool so that the storage pool is associated with drives. For more information about defining device classes, see Chapter 8, Defining Device Classes.

Managing Removable Media Operations

Routine removable media operations including the following: Preparing media for use Controlling media reuse Ensuring that sufficient media are available Mounting volumes in response to server requests, for manually operated drives Managing libraries and drives

For information about removable media operations, see Chapter 7, Managing Removable Media Operations.

Managing Storage Pools and Volumes

Backed-up, archived, and space-managed files are stored in groups of volumes that are called storage pools. Because each storage pool is assigned to a device class, you can logically group your storage devices to meet your storage management needs. You can establish a hierarchy of storage pools. The hierarchy may be based on the speed or the cost of the devices associated with the pools. Tivoli Storage Manager migrates client files through this hierarchy to ensure the most efficient use of a server's storage devices. The following are other examples of what you can control for a storage pool: Collocation The server can keep each client's files on a minimal number of volumes within a storage pool. Because client files are consolidated, restoring collocated files requires fewer media mounts. However, backing up files from different clients requires more mounts. Reclamation Files on sequential access volumes may expire, move, or be deleted. The reclamation process consolidates the active, unexpired data on many volumes onto fewer volumes. The original volumes can then be reused for new data, making more efficient use of media. Storage pool backup The data on primary storage pools can be backed up to copy storage pools for disaster recovery purposes. Backup to copy storage pools can occur simultaneously as client data is written to the primary storage pool. Cache When the server migrates files from disk storage pools, duplicate copies of the files can remain in cache (disk storage) for faster retrieval. Cached files are deleted only when space is needed. However, client backup operations that use the disk storage pool may have poorer performance. You manage storage volumes by defining, updating, and deleting volumes, and by monitoring the use of server storage. You can also move files within and across storage pools to optimize the use of server storage. For more information about storage pools and volumes and taking advantage of storage pool features, see Chapter 9, Managing Storage Pools and Volumes.

Using HACMP for Server Availability

IBM High Availability Cluster Multi-Processing for AIX (HACMP) detects system failures and manages failover to a recovery processor with a minimal loss of end-user time. You can set up a Tivoli Storage Manager server on a system in an HACMP cluster so that, if the system fails, the Tivoli Storage Manager server will be brought back up on another system in the cluster. In both failover and fallback, it appears that the Tivoli Storage Manager server has crashed or halted and was then restarted. Any transactions that were in progress at the time of the failover or fallback are rolled back, and all completed transactions are still complete. Tivoli Storage Manager clients see this as a communications failure and try to reestablish their connections. See Quick Start for details.

Managing Client Operations

Because the key task of the server is to provide services to clients, many of the server administrator's tasks deal with client operations. Tasks include the following: Registering clients and customizing client operations Ensuring that client operations meet security requirements Providing required levels of service by customizing policies Automating protection by using schedules

Managing Client Nodes

A very basic administrative task is adding client nodes, giving the systems that the nodes represent access to the services and resources of the Tivoli Storage Manager server. The Tivoli Storage Manager server supports a variety of client nodes. You can register the following types of clients and servers as client nodes: Tivoli Storage Manager backup-archive client Tivoli Data Protection application clients Tivoli Space Manager client (called space manager client or HSM client) A NAS file server that uses Tivoli Data Protection for NDMP for backup Tivoli Storage Manager source server (registered as a node on a target server)

When you register clients, you have choices to make about the following: Whether the client should compress files before sending them to the server for backup Whether the client node ID has the authority to delete its files from server storage Whether an administrator ID that matches the client ID is created, for remote client operations

Other important tasks include the following: Controlling client options from the server Client options on client systems allow users to customize backup, archive, and space management operations, as well as schedules for these operations. On most client systems, the options are in a file called dsm.opt. In some cases, you may need or want to provide the clients with options to use. To help users get started, or to control what users back up, you can define sets of client options for clients to use. Client options sets are defined in the server database and are used by the clients that you designate. Among the options that can be in a client option set are the include and exclude options. These options control which files are considered for the client operations. For more information, see Chapter 11, Managing Client Nodes. Allowing subfile backups For mobile and remote users, you want to minimize the data sent over the network, as well as the time that they are connected to the network. You can set the server to allow a client node to back up changed portions of files that have been previously backed up, rather than entire files. The portion of the file that is backed up is called a subfile.

For more information, see Chapter 13, Managing Data for Client Nodes. Creating backup sets for client nodes You can perform an instant archive for a client by creating a backup set. A backup set copies a client node's active, backed-up files from server storage onto sequential media. If the sequential media can be read by a device available to the client system, you can restore the backup set directly to the client system without using the network. The server tracks backup sets that you create and retains the backup sets for the time you specify. For more information, see Chapter 13, Managing Data for Client Nodes. For more information, see Chapter 10, Adding Client Nodes and Chapter 11, Managing Client Nodes.

Managing Security
Tivoli Storage Manager includes security features for user registration and passwords. Registration for clients can be closed or open. With closed registration, a user with administrator authority must register all clients. With open registration, clients can register themselves at first contact with the server. See Registering Nodes with the Server. You can ensure that only authorized administrators and client nodes are communicating with the server by requiring the use of passwords. You can also set the following requirements for passwords: Number of characters in a password. Expiration time. A limit on the number of consecutive, invalid password attempts. When the client exceeds the limit, Tivoli Storage Manager locks the client node from access to the server.

See Managing Passwords. You can control the authority of administrators. An organization may name a single administrator or may distribute the workload among a number of administrators and grant them different levels of authority. For details, see Managing Levels of Administrative Authority.

Implementing Policies for Client Data

As the administrator, you define the rules for client backup, archive, and migration operations, based on user or business requirements. The rules are called policies. Policies identify: The criteria for backup, archive, and migration of client data Where the client data is initially stored How the data is managed by the server (how many backup versions are kept, for how long)

In Tivoli Storage Manager, you define policies by defining policy domains, policy sets, management classes, and backup and archive copy groups. When you install Tivoli Storage Manager, you have a default policy that consists of a single policy domain named STANDARD. The default policy provides basic backup protection for end-user workstations. To provide different levels of service for different clients, you can add to the default policy or create new policy. For example,

because of business needs, file servers are likely to require a policy different from policy for end users. Protecting data for applications such as Lotus Domino also may require a unique policy. For more information about the default policy and establishing and managing new policies, see Chapter 12, Implementing Policies for Client Data.

Scheduling Client Operations

Scheduling client operations can mean better protection for data, because operations can occur consistently without user intervention. Scheduling also can mean better utilization of resources such as the network. Client backups that are scheduled at times of lower usage can minimize the impact on user operations on a network. You can automate operations for clients by using schedules. Tivoli Storage Manager provides a central scheduling facility. You can also use operating system utilities or other scheduling tools to schedule Tivoli Storage Manager operations. With Tivoli Storage Manager schedules, you can perform the operations for a client immediately or schedule the operations to occur at regular intervals. The key objects that interact are: Include-exclude options on each client The include-exclude options determines which files are backed up, archived, or space-managed, and determines management classes, encryption, and type of backup for files. The client can specify a management class for a file or group of files, or can use the default management class for the policy domain. The client specifies a management class by using an INCLUDE option in the client's include-exclude list or file. You can have central control of client options such as INCLUDE and EXCLUDE by defining client option sets on the server. When you register a client, you can specify a client option set for that client to use. See Modifying Client Option Files for details. Association defined between client and schedule Associations determine which schedules are run for a client. Clients are assigned to a policy domain when they are registered. To automate client operations, you define schedules for a domain. Then you define associations between schedules and clients in the same domain. Schedule The schedule determines when a client operation automatically occurs. Schedules that can automate client operations are associated with a policy domain. The scheduled client operations are called events. The Tivoli Storage Manager server stores information about events in its database. For example, you can query the server to determine which scheduled events completed successfully and which failed. Management class

The management class determines where client files are initially stored and how they are managed. The management class contains information that determines how Tivoli Storage Manager handles files that clients backup, archive, or migrate. For example, the management class contains the backup copy group and the archive copy group. Each copy group points to a destination, a storage pool where files are first stored when they are backed up or archived. For a schedule to work on a particular client, the client machine must be turned on. The client must either be running the client scheduler or must allow the client acceptor daemon to start the scheduler when needed. To learn more: For how to set up policy domains and management classes, see Chapter 12, Implementing Policies for Client Data. For how to automate client operations, see Chapter 14, Scheduling Operations for Client Nodes. For how to set up an include-exclude list for clients, see Getting Users Started. For how to run the scheduler on client systems, see the user guides for the clients.

After you have created schedules, you manage and coordinate those schedules. Your tasks include the following: Verify that the schedule ran successfully. Determine how long Tivoli Storage Manager retains event records in the database. Balance the workload on the server so that all scheduled operations complete.

For more information about these tasks, see Chapter 15, Managing Schedules for Client Nodes.

Maintaining the Server

To keep the server running well, you have access to these tasks: Managing server operations, such as controlling client access to the server Automating repetitive administrative tasks Monitoring and adjusting space for the database and the recovery log Monitoring the status of the server, server storage, and clients

If you manage more than one server, you can ensure that the multiple servers are consistently managed by using the enterprise management functions of Tivoli Storage Manager. You can set up one server as the configuration manager and have other servers obtain configuration information from it.

Managing Server Operations

There are a variety of tasks associated with managing server operations: Start and stop the server. Allow and suspend client sessions with the server. Query, cancel, and preempt server processes such as backing up the server database. Customize server options.

Other tasks that are needed less frequently include: Maintain compliance with the license agreement. Move the server.

See Licensing Tivoli Storage Manager. For suggestions about the day-to-day tasks required to administer the server, see Chapter 16, Managing Server Operations.

Automating Server Operations

Repetitive, manual tasks associated with managing the server can be automated through Tivoli Storage Manager schedules and scripts. Using schedules and scripts can minimize the daily tasks for administrators. You can define schedules for the automatic processing of most administrative commands. For example, a schedule can run the command to back up the server's database every day. Tivoli Storage Manager server scripts allow you to combine administrative commands with return code checking and processing. The server comes with scripts that you can use to do routine tasks, or you can define your own. The scripts typically combine several administrative commands with return code checking, or run a complex SQL SELECT command. Scripts can also be scheduled. For more information about automating Tivoli Storage Manager operations, see Chapter 17, Automating Server Operations.

Managing the Database and Recovery Log

The Tivoli Storage Manager database contains information about registered client nodes, policies, schedules, and the client data in storage pools (metadata). The information about the client data, also called metadata, includes the file name, file size, file owner, management class, copy group, and location of the file in server storage. The database is key to the operation of the server. The server records changes made to the database (database transactions) in its recovery log. The recovery log is used to maintain the database in a transactionally consistent state, and to maintain consistency across server start-up operations. You can tune database and recovery log performance automatically or manually. You can set up triggers so that additional space is automatically added to the database and recovery log as needed. For more information about the Tivoli Storage Manager database and recovery log and about the tasks associated with them, see Chapter 18, Managing the Database and Recovery Log.

Monitoring the Tivoli Storage Manager Server

Tivoli Storage Manager provides you with many sources of information about server and client status and activity, the state of the server's database and storage, and resource usage. By monitoring selected information, you can provide reliable services to users while making the best use of available resources. Daily checks of some indicators are suggested. You can use Tivoli Storage Manager queries and SQL queries to get information about the server. An ODBC interface is available.

You can set up automatic logging of information about Tivoli Storage Manager clients and server events. See the following sections for more information about these tasks. Chapter 19, Monitoring the Tivoli Storage Manager Server Using SQL to Query the Tivoli Storage Manager Database Logging Tivoli Storage Manager Events to Receivers Daily Monitoring Scenario

Working with a Network of Tivoli Storage Manager Servers

You may have a number of Tivoli Storage Manager servers in your network, at the same or different locations. Some examples are: Your users are scattered across many locations, so you have located Tivoli Storage Manager servers close to the users to manage network bandwidth limitations. You have set up multiple servers to provide services to different organizations at one location. You have multiple servers on your network to make disaster recovery easier.

Servers connected to a network can be centrally managed. Tivoli Storage Manager provides functions to help you configure, manage, and monitor the servers. An administrator working at one Tivoli Storage Manager server can work with servers at other locations around the world. When you have a network of Tivoli Storage Manager servers, you can simplify configuration and management of the servers by using Enterprise Administration functions. You can do the following: Designate one server as a configuration manager that distributes configuration information such as policy to other servers. See Setting Up an Enterprise Configuration. Route commands to multiple servers while logged on to one server. See Routing Commands. Log events such as error messages to one server. This allows you to monitor many servers and clients from a single server. See Enterprise Event Logging: Logging Events to Another Server. Store data for one Tivoli Storage Manager server in the storage of another Tivoli Storage Manager server. The storage is called server-to-server virtual volumes. See Using Virtual Volumes to Store Data on Another Server for details. Share an automated library among Tivoli Storage Manager servers. See Multiple Tivoli Storage Manager Servers Sharing Libraries. Store a recovery plan file for one server on another server, when using Tivoli Disaster Recovery Manager. You can also back up the server database and storage pools to another server. See Chapter 23, Using Tivoli Disaster Recovery Manager for details.

Exporting and Importing Data

As conditions change, you can move data from one server to another. You can export part or all of a server's data so that you can then import the data to another server. The export process writes the data to sequential media, such as tape or a file on hard disk. For example, you can balance workload among servers by moving client nodes from one server to another. For more information about moving data between servers, see Chapter 21, Exporting and Importing Data.

Protecting the Server

Because the server is protecting client data, it is important to protect the server itself. Tivoli Storage Manager provides a number of ways to protect and recover your server from media failure or from the loss of the Tivoli Storage Manager database or storage pools. Recovery is based on the following preventive measures: Mirroring, by which the server maintains one or more copies of the database or the recovery log, allowing the system to continue when one of the mirrored disks fails Periodic backup of the database Periodic backup of the storage pools Audit of storage pools for damaged files, and recovery of damaged files when necessary Backup of the device configuration and volume history files Validation of the data in storage pools, using cyclic redundancy checking

In addition to taking these actions, you can prepare a disaster recovery plan to guide you through the recovery process by using the Tivoli Disaster Recovery Manager. Tivoli Disaster Recovery Manager is an optional product that assists you in the automatic preparation of a disaster recovery plan. You can use the disaster recovery plan as a guide for disaster recovery as well as for audit purposes to certify the recoverability of the Tivoli Storage Manager server. The disaster recovery methods of Tivoli Disaster Recovery Manager are based on taking the following measures: Sending server backup volumes offsite or to another Tivoli Storage Manager server Creating the disaster recovery plan file for the Tivoli Storage Manager server Storing client machine information Defining and tracking client recovery media

For more information about protecting your server and for details about recovering from a disaster, see Chapter 22, Protecting and Recovering Your Server.