The following ADSM storage objects are collections of information that the ADSM server uses to communicate with devices and to manage media:
As an ADSM administrator, you define these objects.
Each device is associated with an ADSM device class. A device class contains information about the device type and the way the device manages its media. See Chapter 8. "Defining Device Classes" for more detailed information about device classes.
For devices that access data randomly, ADSM provides a device class named DISK that is already defined and cannot be changed.
For devices such as tape drives that access data sequentially, the administrator must define the device class. Devices that access data sequentially also include FILE and SERVER device types. For FILE device classes, data resides in files on the server's disk storage. For SERVER device classes, data resides in the storage of another ADSM server.
If the sequential device is a tape drive or optical disk, the device class is associated with a library. The library object is required for sequential devices because of the variations in media type (for example, 8mm tape and optical disk) and because of the need to manage multiple drives and automation.
An ADSM library is an administrator-defined collection of one or more drives that share similar media mounting requirements. The library can include an automated mounting mechanism. Each tape or optical disk device must be associated with an ADSM library.
An ADSM library can contain more than one physical device and can contain different types of devices. Use different libraries to identify devices that are mounted by different means (for example, an operator instead of robotics). You can define these types of libraries:
See Chapter 7. "Defining Drives and Libraries" for more information about ADSM libraries.
Each drive mechanism within a tape or optical disk device is represented by an ADSM drive. For devices with multiple drives, including automated libraries, each drive is separately defined to ADSM. Each drive is associated with an ADSM library. See Chapter 7. "Defining Drives and Libraries" for more information about drives.
A storage pool is a named collection of storage volumes that are associated with one device class. Each storage pool represents a collection of volumes that are the same media type. For example, a storage pool that is associated with a device class for 8mm tape contains only 8mm tape volumes. You can control the characteristics of storage pools, such as whether scratch volumes are used, by specifying parameters. For details on the parameters, see Chapter 9. "Managing Storage Pools".
ADSM supplies default disk storage pools that are named BACKUPPOOL, ARCHIVEPOOL, and SPACEMGPOOL. For more information, see "Using Random Access Volumes on Disk Devices".
An ADSM storage pool volume represents space on media that is available for storing ADSM client data. A storage pool volume is associated with a storage pool. For example, 8mm tapes and optical disks become storage pool volumes when they are assigned to an ADSM storage pool.
See Chapter 10. "Managing Storage Pool Volumes" for more information about ADSM storage pool volumes.
To store data in the storage of another ADSM server, you use a SERVER device type in the device class. You also define a server object to communicate with the target server (where data is actually stored).
When you define a server object to an ADSM server (a source server), you specify the communication attributes necessary for establishing a connection to another ADSM server (a target server). The source server can then use the target server as a sequential device for storing data. This data on the target server is one or more archived files that are stored on behalf of the source server.