Basics of IBM Tivoli Storage Manager

24,881 views

Published on

Basics of IBM Tivoli Storage manager.
Presentation can be used as notes.

Published in: Technology

Basics of IBM Tivoli Storage Manager

  1. 1. Aniruddha Thombre
  2. 2. Introduction <ul><li>IBM Tivoli Storage Manager was earlier called as ADSM (Adstar Distributed Storage Manager), till IBM took it over. </li></ul><ul><li>IBM Tivoli Storage Manager is a client/server program that provides centralized, automated data protection and storage management solutions to customers in a multivendor computer environment. IBM Tivoli Storage Manager provides a policy-managed backup, archive, and space-management facility for file servers, workstations, applications, and application servers. </li></ul><ul><li>Versions in Production: 5.4 / 5.5, 6.1 </li></ul><ul><li>Major Difference in 5.x & 6.x , metadata limit raised from 530 GB to unlimited </li></ul>
  3. 3. Audience <ul><li>System Admins / Backup Admins </li></ul><ul><li>Those who are new to IBM TSM </li></ul><ul><ul><li>This presentation may serve as notes to recall / refresh your concepts </li></ul></ul><ul><ul><li>It should give you basic understanding </li></ul></ul>
  4. 4. Basic Concepts <ul><li>Backup </li></ul><ul><ul><li>To guard against the loss of information, the backup-archive client can copy files, subdirectories, and directories to media controlled by the server. Backups can be controlled by administrator-defined policies and schedules, or users can request backups of their own data. </li></ul></ul><ul><li>Restore </li></ul><ul><ul><li>When a user restores a backup version of a file, the server sends a copy of the file to the client node. The backup version remains in server storage. Restoring a logical volume backup works the same way. </li></ul></ul><ul><li>Archive & Retrieve </li></ul><ul><ul><li>To preserve files for later use or for records retention, a user with a backup-archive client can archive files, subdirectories, and directories on media controlled by the server. When users archive files, they can choose to have the backup-archive client erase the original files from their workstation after the client archives the files. </li></ul></ul><ul><ul><li>When a user retrieves a file, the server sends a copy of the file to the client node. The archived file remains in server storage. </li></ul></ul><ul><li>Versioning </li></ul><ul><ul><li>Versions are nothing but multiple copies of same file in chronology. </li></ul></ul>
  5. 5. Basic Concepts… <ul><li>Retention Policy </li></ul><ul><ul><li>How many days you want to keep copies OR How many copies you want to retain. </li></ul></ul><ul><ul><li>The final retention depends upon whichever condition of the above is satisfied. </li></ul></ul><ul><ul><li>Default is 30 days for backup, 1 year for archive, default no. of versions is 4 </li></ul></ul><ul><li>Expiration </li></ul><ul><ul><li>Versions keep changing states: Active => Inactive => Obsolete </li></ul></ul><ul><ul><li>You need to start a process to remove pointers of Obsolete files in Meta Data DB </li></ul></ul><ul><ul><li>That process is called as expiration </li></ul></ul><ul><li>Reclamation </li></ul><ul><ul><li>Once you have expired files from your sequential devices, the space has invalid data. </li></ul></ul><ul><ul><li>In order to use the space, you have to move data from one / more sequential devices to other devices (This is very similar to defragmentation, but as defragmentation does not work on sequential devices; you have to Move the data) </li></ul></ul>
  6. 6. Basic Concepts… <ul><li>Collocation </li></ul><ul><ul><li>In order to reduce no. of sequential devices required we may need to collocate the data. </li></ul></ul><ul><ul><li>Collocation need may also arise if we want to avoid reclamation situations. </li></ul></ul><ul><ul><li>Collocation types: By node , By Group, By application </li></ul></ul><ul><li>Data Migration Hierarchy </li></ul><ul><ul><li>Random Storage devices </li></ul></ul><ul><ul><li>Random Storage devices / SAN / NAS etc </li></ul></ul><ul><ul><li>Sequential Storage Devices </li></ul></ul><ul><li>Data Migration </li></ul><ul><ul><li>Data can be migrated from random to random or random to sequential devices. But not from sequential to random devices. </li></ul></ul><ul><ul><li>Data Migration can be triggered and stopped using these two values: </li></ul></ul><ul><ul><ul><li>High Threshold Value (Default is 90%) </li></ul></ul></ul><ul><ul><ul><li>Low Threshold Value (Default is 70%) </li></ul></ul></ul>
  7. 7. Components of Policy <ul><li>Versioning Details </li></ul><ul><li>Retention Details </li></ul><ul><li>Schedules details </li></ul><ul><li>Storage pool detailss not work on sequential devices; you have to Move the data) </li></ul><ul><li>Backup and archive details </li></ul>
  8. 8. Complete Install Requires following: <ul><li>Backup / Archive Clients </li></ul><ul><li>Tivoli Server Manager (Storage Server) </li></ul><ul><li>Integrated Solutions Console </li></ul><ul><li>Administration Center </li></ul>
  9. 9. Components of TSM <ul><li>Storage Pools </li></ul><ul><li>Meta Data DB </li></ul><ul><li>Recovery Logs </li></ul><ul><li>Configured Settings </li></ul>
  10. 10. Metadata DB includes information such as: <ul><li>Object ID, index </li></ul><ul><li>Version </li></ul><ul><li>Status of backup </li></ul><ul><li>Time stamp </li></ul><ul><li>User / Group </li></ul><ul><li>Filespace_name, Filespace_id </li></ul><ul><li>HL_name, LL_name </li></ul><ul><li>Etc. </li></ul>
  11. 11. TSM Server Important Files: <ul><li>DSMServ.exe </li></ul><ul><li>DSMServ.dsk </li></ul><ul><ul><li>Includes FQN, logv, dbv info </li></ul></ul><ul><li>InitServ.log </li></ul><ul><ul><li>Server Installation Logs </li></ul></ul><ul><li>Devcnfg.out </li></ul><ul><ul><li>Device class info, server name, instance name etc. </li></ul></ul><ul><li>Vollist.out </li></ul><ul><ul><li>Volume library info, info of db backups, export info. </li></ul></ul><ul><li>DSMServ.out </li></ul><ul><ul><li>Parameters / Settings for the instance / server. </li></ul></ul>
  12. 12. BA Client Important Files: <ul><li>Dsm.opt </li></ul><ul><ul><li>Node name </li></ul></ul><ul><ul><li>Server address </li></ul></ul><ul><ul><li>Server tcp port </li></ul></ul><ul><ul><li>And other configurable parameters. </li></ul></ul><ul><li>Dsm.exe </li></ul><ul><ul><li>BA Client GUI </li></ul></ul><ul><li>Dsmc.exe </li></ul><ul><ul><li>BA Client CLI </li></ul></ul><ul><li>Dsmadmc.exe </li></ul><ul><ul><li>Administrative utility </li></ul></ul>
  13. 13. Summary <ul><li>Introduction to IBM Tivoli Storage Manager </li></ul><ul><li>Basic Concepts of Storage </li></ul><ul><li>Metadata info </li></ul><ul><li>Components of policy, TSM, TSM Server, BA client </li></ul><ul><li>Please, note this presentation should be used as a note to recall. It may not help you to understand technologies. </li></ul><ul><li>A lot of trademarked words are used, they belong to respective orgs. </li></ul><ul><li>This doc may not contain correct information, so I disclaim any responsibilities. </li></ul>
  14. 14. Resources <ul><li>IBM Redbooks </li></ul><ul><li>Adsm.org </li></ul><ul><li>Publib.boulder.ibm.com </li></ul><ul><li>Lascon.co.uk </li></ul>
  15. 15. Aniruddha Thombre www.aniruddhas.com

×