Tivoli Storage Manager for Windows: Administrator's Guide
Figure 125 shows the relationship between TSM device, media, and policy
objects. Together, these storage objects create a virtual model of the
physical device environment. The model allows administrators to
configure TSM to implement strategies and manage client data. The
numbers in the following list correspond to the numbers in the figure.
- (1)
- Administrators register clients and associate them with a policy domain
containing a policy set, management class, and copy groups. See Managing Nodes.
- (2), (3)
- When TSM backs up, archives, or migrates data, it is bound to a management
class. A management class and the backup and archive copy groups within
it specify where files are stored and how they are managed when they are
backed up, archived, or migrated (space-managed files). See Client Migration and Recall.
- (4), (5)
- Storage pools are the destinations for backed-up, archived, or
space-managed files. Copy groups specify storage pools for backed-up or
archived files. Management classes specify storage pools for
space-managed files.
Storage pools are mapped to device classes, which represent devices.
The storage pool contains volumes as indicated by the device type associated
with the device class. For example, a storage pool that is mapped to a
device class with a device type of 8MM contains only 8mm tapes.
All devices require a device class that specifies at least a device
type. Tape and other removable media devices also require a library and
drive for management of media, including the mounting of that media.
- (6)
- Files that are initially stored on disk storage pools can migrate to tape
or other types of storage pools if the pools are set up in a storage
hierarchy.
Figure 125. Putting It All Together

[ Top of Page | Previous Page | Next Page | Table of Contents | Index ]