Integrating Backup Recovery and Media Services and IBM Tivoli Storage Manager on the IBM eServer iSeries Server

Chapter 6. Next steps: Getting the IBM Tivoli Storage Manager server ready for production 105

When IBM Tivoli Storage Manager expires the volume, because the IBM Tivoli Storage

Manager data is no longer needed, it tells BRMS to expire it. The volume displays as

expired. Now the volume can be written to again, starting with sequence number 1.

Because IBM Tivoli Storage Manager does not check to see if there is any BRMS data on

the volume when it expires the tape, any data that BRMS still needs is overwritten if

something uses that expired volume. You do not want this to happen and later try to use

the media to recover.

6.3 IBM Tivoli Storage Manager advanced storage

This section provides a high-level overview of the IBM Tivoli Storage Manager storage

hierarchy, for a more detailed explanation of IBM Tivoli Storage Manager storage, see

Chapter 8 “Managing Storage Pools and Volumes” in the IBM Tivoli Storage Manager for

OS/400 PASE Administrator’s Guide, GC23-4694.

6.3.1 Overview of IBM Tivoli Storage Manager storage

The IBM Tivoli Storage Manager storage hierarchy is comprised of different storage pools. A

storage pool can be constructed from different types of media such as disk, tape, or a file.

Each pool consists of one or more

storage pool volumes. On iSeries servers, a disk storage

pool volume is a streamed (byte stream) file in the IFS. For sequential access storage pools

(tape or file), volumes are individual tapes or files.

IBM Tivoli Storage Manager storage pools can be further classified as

primary storage pools

and

copy storage pools. This takes into account the fact that data can be duplicated within the

storage hierarchy for disaster recovery purposes. The duplication is performed at the storage

pool level, rather than at the individual storage pool volume level.

Primary storage pools are the place where the original IBM Tivoli Storage Manager client

data is stored on a backup function. They are normally on-site storage pools, either on the

iSeries disk (IFS) or in a tape library. In this example configuration, this is a 3584 tape library.

Copy storage pool volumes can be defined as on site (in a tape library) or off site (ejected and

placed in a secure location for disaster recovery). Each pool is categorized by type and format

with an IBM Tivoli Storage Manager

device class. The device class describes how to access

and use the storage pool volumes. Tape device classes tell IBM Tivoli Storage Manager which

tape library to use on the iSeries server, the number of drives in that library that are available

to IBM Tivoli Storage Manager and the tape format that is used.

In the example configuration used throughout this redbook (shown in Figure 6-9), we created

a 20 GB disk storage pool called BACKUPPOOL. This storage pools consists of four storage

pool volumes that reside in the OS/400 IFS. Each volume is defined as a 5 GB IFS streamed

file in the /tsmvol/backuppool/ directory on the iSeries server (shown on the left side of

Figure 6-9). This is the first step in our IBM Tivoli Storage Manager storage hierarchy

configuration.

Client data can now be saved to the iSeries disk. But how do we migrate that data to tape?

Simple, we create additional storage pools.

In our environment, we create two additional storage pools. The first storage pool we create is

a sequential access storage pool called BACKUPLTO. This storage pool uses tape cartridges

(known as

storage pool volumes in IBM Tivoli Storage Manager) in our 3584 tape library.

These tapes contain all the IBM Tivoli Storage Manager client data migrated from the

BACKUPPOOL disk storage pool and remain available in the 3584 tape library.