Different types device class objects supported by IBM Spectrum Protect (TSM)

Library objects, Drive objects, and Device-class objects taken together represent physical storage entities. Tapes used for storage should match the drive objects requirements to take the backup to the tapes. TSM server supports wide variety of tape libraries and drives to be used as a storage destination.  A Tape drive object represents a drive mechanism within a library that uses removable media. For devices with multiple drives, including automated libraries, you must define each drive separately and associate it with a library. Drive definitions can include such information as the element address for drives in SCSI or virtual tape libraries (VTLs), how often a tape drive is cleaned, and whether the drive is online. Tivoli Storage Manager drives include tape and optical drives that can stand alone or that can be part of an automated library. Supported removable media drives also include removable file devices such as rewritable CDs.
Ex:     define drive TSMLIB drive01
           define path server01 drive01 srctype=server desttype=drive  library=TSMLIB                              device=/dev/rmt0

Types of Device Class objects supported by IBM TSM

Each device that is defined to Tivoli Storage Manager is associated with one device class, which specifies the device type and media management information, such as recording format, estimated capacity, and labeling prefixes. A device type identifies a device as a member of a group of devices that share similar media characteristics. Device types include a variety of removable media types as well as FILE, CENTERA, and SERVER. A device class for a tape or optical drive must also specify a library.

Disk Devices
Using Tivoli Storage Manager, you can define random-access disk (DISK device type) volumes using a single command. You can also use space triggers to automatically create preassigned private volumes when predetermined space-utilization thresholds are exceeded.

Also Read: What is Cloud Container Storagepool ?

Removable Media
Tivoli Storage Manager provides a set of specified removable-media device types, such as 8MM for 8 mm tape devices, or REMOVABLEFILE for Jaz or DVD-RAM drives. The GENERICTAPE device type is provided to support certain devices that are not supported by the Tivoli Storage Manager server.
Ex:    define devclass LTOTAPE devtype=lto library=TSMLIB format=ultrium4c                                      mountlimit=12 mountretention=5 
          define devclass NASTAPE devtype=nas library=naslib mountretention=0                                       mountlimit=drives  estcapacity=200G

Files on disk as sequential volumes (FILE)
The FILE device type lets you create sequential volumes by creating files on disk storage. To the server, these files have the characteristics of a tape volume. FILE volumes can also be useful when transferring data for purposes such as electronic vaulting or for taking advantage of relatively inexpensive disk storage devices. FILE volumes are a convenient way to use sequential-access disk storage for the following reasons:
  • You do not need to explicitly define scratch volumes. The server can automatically acquire and define scratch FILE volumes as needed.
  • You can create and format FILE volumes using a single command. The advantage of private FILE volumes is that they can reduce disk fragmentation and maintenance overhead.
  • Using a single device class definition that specifies two or more directories, you can create large, FILE-type storage pools. Volumes are created in the directories you specify in the device class definition. For optimal performance, volumes should be associated with file systems.
  • When predetermined space-utilization thresholds have been exceeded, space trigger functionality can automatically allocate space for private volumes in FILE-type storage pools.
The Tivoli Storage Manager server allows concurrent read-access and write-access to a volume in a storage pool associated with the FILE device type. Concurrent access improves restore performance by allowing two or more clients to access the same volume at the same time. Multiple client sessions (archive, retrieve, backup, and restore) or server processes (for example, storage pool backup) can read the volume concurrently. In addition, one client session or one server process can write to the volume while it is being read. Unless sharing with storage agents is specified, the FILE device type does not require you to define library or drive objects. The only required object is a device class.
Ex:   define devclass FILEDEVC devtype=file directory=/opt/FILE

Also Read: Use these 4 TSM Server options to efficiently manage the client backup schedules

Files on sequential volumes (CENTERA)
The CENTERA device type defines the EMC Centera storage device. It can be used like any standard storage device from which files can be backed up and archived as needed. The Centera storage device can also be configured with the Tivoli Storage Manager server to form a specialized storage system that protects you from inadvertent deletion of mission-critical data such as e-mails, trade settlements, legal documents, and so on. The CENTERA device class creates logical sequential volumes for use with Centera storage pools. These volumes share many of the same characteristics as FILE type volumes. With the CENTERA device type, you are not required to define library or drive objects. CENTERA volumes are created as needed and end in the suffix "CNT."
Ex:    define devclass CENTERADEVC devtype=CENTERA                                                             HLADDRESS=,

Sequential volumes on another Tivoli Storage Manager server (SERVER)
The SERVER device type lets you create volumes for one Tivoli Storage Manager server that exist as archived files in the storage hierarchy of another server. These virtual volumes have the characteristics of sequential-access volumes such as tape. No library or drive definition is required. You can use virtual volumes for the following
  • Device-sharing between servers. One server is attached to a large tape library device. Other servers can use that library device indirectly through a SERVER device class.
  • Data-sharing between servers. By using a SERVER device class to export and import data, physical media remains at the original location instead having to be transported.
  • Immediate offsite storage. Storage pools and databases can be backed up without physically moving media to other locations.
  • Offsite storage of the disaster recovery manager (DRM) recovery plan file.
  • Electronic vaulting
Ex:   define devclass Serverdevc devtype=server servername=tsmserver1                                          maxcapacity=500G

What Others are Reading Now...

0 Comment to "Different types device class objects supported by IBM Spectrum Protect (TSM)"

Post a Comment