This is the Part 2 of the Tivoli Storage Manager (TSM) Tutorials on TSM Basic Concepts Introduction. To read Part 1 go to this link Tivoli Storage Manager (TSM) Basic Concepts and architecture - Part 1.
TSM Database and Recovery Log
Protecting the Database and Storage Pools explains the functions of the TSM database, active log, archive log, and storage pools, and how to protect them with backups.
- The Tivoli Storage Manager database contains information about registered client nodes, policies, schedules, and the client data in storage pools. The database is key to the operation of the server.
- 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 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 startup operations.
- The database does not store client data; it points to the locations of the client files in the storage pools. The Tivoli Storage Manager database contains information about the Tivoli Storage Manager server.
- The recovery log helps to ensure that a failure such as a system power outage or application error does not leave the database in an inconsistent state. The recovery log is essential when you restart the Tivoli Storage Manager or the database, and is required if you must restore the database. The recovery log consists of these logs:
The active log files record transactions that are in progress on the server.
Log mirror (optional)
The active log mirror is a copy of the active log that can be used if the active log files cannot be read. All changes made to the active log are also written to the log mirror.
Archive log
The archive log contains copies of closed log files that had been in the active log.
Archive failover log (optional)
The archive failover log, also called a secondary archive log, is the directory that the server uses to store archive log files when the archive log directory is full.
Also Read: How to increase or decrease TSM DB, active log and archive log size ?
- Monitor the database, log space, and file systems where the directories are located to ensure that space is always available. You can monitor the database and recovery log space whether the server is online or offline. To restore a damaged or lost database you must have a database backup. You must also have copies of the files that are required to recover the database and client data. Database backup media and setup files can be stored offsite for protection.
TSM Library & Storage Management
Managing Storage Media describes tasks and concepts associated with media management including scratch tapes, tape labeling, checkin and checkout, volume access, movement to offsite storage, expiration, reclamation, and media errors.
Also Read: TSM Storage Pool Concepts (V7 Revised)
Storage pool hierarchies
You can arrange storage pools in a storage hierarchies, which consist of at least one primary storage pool to which a client node backs up, archives, or migrates data. Typically, data is stored initially in a disk storage pool for fast client restores, and then moved to a tape-based storage pool, which is slower to access but which has greater capacity.
Migration
Caching in disk storage pools
When cache is enabled, the migration process leaves behind duplicate copies of files after the server migrates these files to the next storage pool in the storage hierarchy.
Deduplicating data
Writing data simultaneously to primary, copy, and active-data pools
You can write data simultaneously to a primary storage pool, copy storage pools, and active-data pools. The simultaneous-write function increases your level of data protection and reduces the amount of time required for storage pool backup.
Keeping client files together using collocation
Reclaiming space in sequential-access storage pools
Space on a sequential-access storage volume becomes reclaimable as files expire or are deleted from the volume.
Monitoring storage-pool and volume usage
Also Read: Monitoring and Managing Tape Volumes
Moving data from one volume to another volume
You might need to move data from one volume to another volume in the same or a different storage pool, use the MOVE DATA command. The volumes can be on-site volumes or off-site volumes.
Moving data belonging to a client node
You can move data located in a sequential-access storage pool for one or more nodes, or for a single node with selected file spaces, using the MOVE NODEDATA command.
TSM Scheduling & Daily Operations
Scheduling and Monitoring Daily Operations explains scheduling of daily events on how to monitor Tivoli Storage Manager.
- You can schedule administrative commands to tune server operations and to start functions that require significant server or system resources during times of low usage. Automating these operations allows the administrator to ensure that server resources are available when needed by clients.
- Tivoli Storage Manager includes a central scheduling component that allows the automatic processing of administrative commands during a specific time period when the schedule is activated. Schedules that are started by the scheduler can run in parallel.
- All scheduled events, including their status, are tracked by the server. An event record is created in the server database whenever processing of a scheduled command is created or missed.
- To help manage schedules for administrative commands, you can request information about scheduled and completed events. You can request general or exception reporting queries.
- Tivoli Storage Manager provides for automation of common administrative tasks with server scripts that are stored in the database. Tivoli Storage Manager supports macros on the administrative client. A macro is a file that contains one or more administrative client commands.
The following actions
describes some of the items that are important to monitor TSM Server daily:
- Verify that the database file system has enough space.
- Examine the database percent utilization, available free space, and free-pages.
- Verify that there is enough disk space in the file systems that contain Active log, Archive log, Mirror log, Archive failover log.
- Verify that the instance directory file system has enough space.
- Verify that the database backups completed successfully, and that they are running frequently enough.
- Check the database and recovery log statistics.
- Search the summary table for failed processes.
- Search the activity log for error messages.
- Check the status of sequential access storage pools.
- Check how many scratch volumes are available.
- Determine if there are any tape drives offline, or their paths that are offline.
- Determine if there are any libraries offline, or their paths that are offline.
- Check for failed or missed schedules.
0 Comment to "Tivoli Storage Manager (TSM) basic components and daily operations Overview"
Post a Comment