Ibm Spectrum Protect (TSM) Training

 

IBM SPECTRUM PROTECT (TSM) Training Amarpreet Singh Lead Consultant

   

Training Agenda 1

Introduction to IBM SPECTRUM PROTECT (TSM)

5

Storage device management

2

TSM Architecture

6

TSM Physical Storage Devices Introduction

TSM Backup and Archive Functions and 3

Features

7

TSM retention Concepts

4

TSM Database and recoverylog overview and functions

8

TSM health check

©

confidential

 

Introduction to IBM SPECTRUM PROTECT (TSM) IBM Tivoli Storage Manager (TSM) is enhanced Enterprise level data protection software that expedites operational and disaster recovery. TSM offers centralized, automated data protection to help reduce the risks associated with data loss. This highly scalable software helps you manage more data with less infrastructure and simplified administration. Designed for a heterogeneous environment, Tivoli Storage Manager connects over the local area network (LAN), wide area network (WAN), Internet, and storage area network (SAN). This design provides data move and store techniques, comprehensive policy based automation, and data management. Tivoli Storage Manager automates data backup and restore functions and centralizes storage management operations. IBM Tivoli Storage Manager was earlier called as ADSM (Adstar Distributed Storage Manager), till t ill IBM took it over. The name Tivoli came from (Reverse of I LOVe IT) and works on the concept of “Manager of Managers”. • Versions in Production: 6.x, 7.x and 8.x • Tivoli Storage Manager provides :  

Centralized administration for data and storage management



Fully automated data protection Efficient management of information growth



High-speed automated server recovery



Full compatibility with hundreds of storage devices, as well as LAN, WAN, and SAN infrastructures



Optional customized backup solutions for major groupware, enterprise resource planning (ERP) applications, and database products

2

©

confidential

 

Features of Tivoli Storage Manager  • Progressive backup methodology – Saves time and storage space by backing up only new files and modified files. The progressive backup feature uses Tivoli Storage Manager’s own relational database to track data wherever it is stored, delivering direct one-step file restore. Progressive backup eliminates the need for traditional full-plus-incremental or full-plus-differential backup and restore procedures, commonly used by other storage management products. • Tape resource sharing - Enables multiple Tivoli Storage Manager Servers to use the same tape library and drives, optimizing tape hardware asset utilization. • Network-free  rapid recovery - Supports high-speed client data recovery directly from tape or optical devices. Recovery time is minimized by eliminating the use of network and central server resources. • Adaptive differencing technology - Using adaptive differencing, data is transferred to the server either by byte, block, or file level, based on the size of the file being backed up, and the portion of the file that has changed since the last backup. Adaptive differencing technology supports all connectivity strategies, including LANs, WANs, SANs, Internet, and dial-up connections. • Clustering - Tivoli Storage Manager includes enhanced support for High Availability Cluster Multi- Processing (HACMP), Microsoft Cluster Services (MSCS), Novell Cluster Services (NCS) as well as VERITAS Cluster Services (VCS) on Windows. • LAN-free data transfer - An -  An optional module for f or Tivoli Storage Manager effectively exploits SAN environments environment s by moving data transfers from the communication network to a SAN. • Hierarchical Storage Management - An -  An optional module for f or Tivoli Storage Manager automatically and transparently moves unused data files from online disk storage to offline tape storage. In the event that a file is accessed after it has been moved to offline storage, Tivoli Storage Manager transparently recalls the file. • Library and device support - Tivoli Storage Manager Basic Edition supports libraries with up to 3 tape drives and up to 40 cartridge capacity.

3

©

 

TSM Architecture

confidential

4

©

 

TSM Architecture TSM Components • TSM Administrative interfaces • Tivoli Storage Manager Operations Center  • Tivoli Storage Manager Server  • TSM Scheduler Services • TSM Backup-archive client • Tivoli Storage Manager database • Tivoli Storage Manager recovery log • Storage pools • Policy-based management • Media library

confidential

5

©

 

TSM Architecture TSM Components TSM Administrative interfaces You can access TSM Server and TSM client through various interfaces as mentioned below: 

Operations Center accessed through web w eb browser and default secure port 11090



Backup-archive client GUI accessed through dsm dsm (Windows)  (Windows) dsmj  (UNIX)  (UNIX) commands.



Web client GUI accessed through web browser and default port 1581



Backup-archive command line accessed through command dsmc 



Tivoli Storage Manager server command line accessed through dsmadmc, dsmadmc, Operations  Operations Center, and server console.

Tivoli Storage Manager Operations Center IBM Tivoli Storage Manager Operations Center is a new added dashboard-style management interface starting from TSM V6.4 to simplify TSM operations and monitoring. You You can use the Operations Center, command-line interfaces, backup-archive graphical user interface (GUI), and a web client interface to manage your Tivoli Storage Manager environment. Tivoli Storage Manager Server Tivoli Storage Manager server refers to an instance, not a physical system. syst em. A single single system can run multiple instances of the server. In a typical local area network or LAN configuration, c onfiguration, the Tivoli Storage Storage Manager server stores to the storage media the backup or archive data from the backup-archive clients that it supports. The server also has a database to manage data, including policy management objects, users and administrators, and client nodes.

confidential

6

©

confidential

 

TSM Architecture TSM Components TSM Scheduler Services Tivoli Storage Manager includes a central scheduling component to automatically process the administrative commands c ommands and backup-archive client operations during the specific time period when the schedule is activated. An administrator is responsible to create and maintain the schedules in each policy domain. Tivoli Storage Manager scheduling is split into two categories administrative scheduling  and  and backup-archive client scheduling . 

Administrator-defined schedules allow for the automation of Tivoli Storage Manager server and backup-archive client operations. A comprehensive



and integrated set of schedules can provide the basis for efficient data management with little need for intervention during normal operations. Scheduling Tivoli Storage Manager backup-archive client operations consists of schedules s chedules on the Tivoli Storage Manager server and a scheduler component that runs on the Tivoli Storage Manager backup-archive client machine.

TSM Backup-archive client  A backup-archive client is usually usually a server. Application servers and file servers, and also desktop workstations and portable portable PCs, are backup-archive clients to the Tivoli Storage Manager server. Physical client systems are registered on the server as nodes. File servers, workstations, and database servers that are backed up, are referred to as clients. •

The Tivoli Storage Manager backup-archive client is a service that sends data to and retrieves data from a Tivoli Storage Manager server. The Tivoli Storage Manager backup-archive client must be installed on every machine that transfers data to server-managed s erver-managed storage called storage pools. This machine might be a workstation, a file, or a database server.

•

The Tivoli Storage Manager server uses a unique node name for identifying each Tivoli Storage Manager backup-archive client c lient instance. The Tivoli Storage Manager backup-archive client supports encryption, and can use a password for authenticating communications between the Tivoli Storage Manager backup-archive client and server.

7

©

confidential

 

TSM Architecture TSM Components Tivoli Storage Manager database From version 6, the Tivoli Storage Manager database is built on DB2. This database is part of Tivoli Storage Manager and you must not manage it as a DB2 database. The information that the database stores includes the file name, file size, management class, copy group, location of the files in Tivoli Storage Manager server storage, and all other information except for the data. Data is stored in a storage pool. •

When the Tivoli Storage Manager server is installed, a database and recovery logs are created. Tivoli Storage Manager saves information in the

•

Tivoli Storage Manager database database about each file, logical volume, or database that it backs up, archives, or migrates. The Tivoli Storage Manager database is the heart of Tivoli Storage Manager. You You need take backup of this database in regular intervals in order to restore the database to the current state if any disaster occurs.

Tivoli Storage Manager recovery log The server uses the recovery log as a scratch pad for the database, recording information about client and server actions while the actions are performed. Changes to the database are recorded in the recovery log to maintain a consistent consist ent database image. The recovery log stores data that is required to back up a restored database to the most recent committed transaction. Starting TSM V6, the Recoverylog consists of Activelog, Archivelog,  Active mirror log and Archive failover log.

8

©

confidential

 

TSM Architecture TSM Components Storage pools Storage pools are collections of similar media that provide storage for backed up, archived, and migrated files. These pools can c an be chained to create a storage hierarchy. You You can use any supported sequential media in all copy storage pools. There are 2 important process which moves client backups within the storage st orage hierarchy. •

Migration:: Data moves from the primary disk pool directly to tape pools. Migration

•

Copy data: data: Data moves from the primary disk pool to file pools or disk pools to tape pools

 A storage pool volume volume is the basic unit of storage for the Tivoli Storage Storage Manager storage pools. A volume might might be a logical volume, a standard file system file, a tape cartridge, or an optical cartridge. A unique volume identifier identifies identifies each volume. v olume.

Policy-based management Backup-archive client data is centrally managed by business policy. The administrator creates policies and stores them in the database on the server. Policies are defined based on the business requirements for data backup and retention. These requirements, sometimes referred to as a storage service level agreement (SLA), identify when to perform backups, how long and how many copies c opies of files to retain, and other requirements that the customer specifies. This feature makes it possible for different departments with different types of data to have their own customized storage management plan

Media library IBM Tivoli Storage Manager supports a variety of library types, including manual libraries, SCSI libraries, 349X and 358X (LTO) libraries, and external libraries. A tape library is essentially a box that holds drives and cartridges, and provides automation for tape operation.

9

©

confidential

 

TSM Backup and Archive Functions and Features Backup and Restore Functions Tivoli Storage Manager can create backups of both files and raw logical volumes. When backing up files, the Tivoli Storage Manager server database keeps a list of all files and their attributes: att ributes: time, date, size, access control lists, and extended attributes. It treats raw logical volumes as separate entities, and the management class policy applies to the entire image. No tracking of individual files occurs in an image backup because it is treated as an object. •

Backup: Creates a copy of a file to protect against the operational loss or destruction of that Backup: Creates t hat file. Customers control backups by defining the backup frequency and number of versions.

•

Restore: Places backup copies of files into a customer-designated system or workstation after the loss of a file. By default, the backup r estores and Restore: Places replaces the most recent version of each active file that is requested.

Four levels of backup are available as follows: •

Byte level, small amounts of data, for example, on notebook computers.

•

Block level, bigger amounts of data, between 40 KB and 2 MB.

• •

File level, normal files Image level, which includes file system and files

10

©

 

TSM Backup and Archive Functions and Features Progressive incremental backup Tivoli Storage Manager uses progressive backup methodology,, also known as incremental backups by default methodology Features: •

Backup of only new or changed files

•

No redundant or full backups

•

Tracks data at the file level

•  Accurate restore of files to a point-in-time copy •

Requires less storage space compared to full backup

•

Requires less network bandwidth

•

Uses less time

•

Shorter backup window time frames • Faster restores

Traditional backups of a weekly full backup, plus incremental backups require more time and space than the Tivoli Storage Manager’s incremental forever concept. TSM supports different kinds of backup methods/types such as Full, Incremental, Differential, Progressive Incr emental, Adaptive subfile and Image backup etc

confidential

11

©

confidential

 

TSM Backup and Archive Functions and Features Archive and Retrieve Functions The Tivoli Storage Manager archive function stores selected files unconditionally on the server, serv er, according to the applicable management class limits. Unconditionally means no version limit, and the files are retained for the defined time period regardless of whether they are deleted on the client or not.  Archiving is useful when you want to store data that is infrequently infrequently accessed but must remain available. Also, Also, it is common to have a legal requirement to archive business records for extended periods of time. t ime. Tivoli Storage Manager Manager has the capability of archiving for 30 years. •

Archive: Creates a copy of a file f ile or set of files for vital record retention of data, such as patent information, financial information, or medical records. You control the length of time to keep an archive in storage s torage by defining the retention period. With this feature, customers can keep unlimited archive copies of a file.

•

Retrieve: Users Retrieve:  Users can copy c opy an archive file from the storage pool to the workstation. works tation. The archive copy in the storage pool is unaffected.

Difference between Backup and Archive •

Backup copies files or directories from a client node to server storage. More than one backup version can exist in server storage, but only one

backup version is the active version. •  Archive copies data or files to other storage media, usually usually for long-term storage or security. security. Only one version exists.

12

©

confidential

 

TSM Backup and Archive Functions and Features Disaster Recovery Manager (DRM) The Tivoli Storage Manager disaster recover manager (DRM) function offers various options to configure, control, and automatically generate a disaster recovery plan. The plan contains the information, scripts, and procedures to automate restores and help ensure quick recovery of your data after a disaster. It also manages and tracks the media that your data is stored on, whether on-site, in transit, or in a vault. Your Your data can easily be found if disaster occurs. The scripts can help you document your basic information technology recovery strategy, the steps to rebuild your core systems, sy stems, and the critical machines that you must recover.

With Disaster Recovery Manager, you can accomplish the following tasks: •

Prepare a Disaster Recovery Plan.

•

Manage off-site volumes and track media.

•

Manage client data.

13

©

confidential

 

IBM Tivoli Storage Manager (TSM) Product Family Tivoli Storage Manager Basic Edition Backup and Restore

For Application Protection Tivoli Storage Manager for Mail

 Archive and Retrieve

Tivoli Storage Manager for Databases

Data Reduction (deduplication)

Tivoli Storage Manager for Enterprise Resource Planning (ERP)

Tivoli Storage Manager Extended Edition (Basic plus..) Disaster recovery management Backup via NDMP for NAS Large libraries, additional tape support

Tivoli Storage Manager for Microsoft SharePoint Tivoli Storage Manager for Virtual Environments Tivoli Storage Manager FastBack for Microsoft Exchange

For Space Management, Archiving Tivoli Storage Manager for Space Management Tivoli Storage Manager HSM for Windows Tivoli Storage Manager for Storage Area Networks (SAN) System Storage Archive Manager IBM Information Archive For z/OS Protection Tivoli Storage Manager for z/OS Media (NEW)

Tivoli Storage FlashCopy Manager  For Desktop / Laptop Protection Tivoli Storage Manager FastBack for Workstations

Tivoli Storage Manager EE for z/OS Media (NEW) For Bare Machine Recovery Tivoli Storage Manager for System Backup and Recovery (AIX) Cristie Bare Machine Recovery (reseller) Cristie TBMR (reseller) Tivoli Storage Manager FastBack for Bare

14

Machine Recovery

©

confidential

 

TSM Database and recoverylog overview and functions Tivoli Storage Manager Database (DB2) Overview The Tivoli Storage Manager database contains information that is needed for server operations and information about client data that is backed up, archived, and space-managed. The database does not store client data. The database includes the following information • • • • •

Client nodes and administrators Policies and schedules Server settings Locations of client files on server storage Directory structures

• Server operations, for example, activity logs and event records •  Access control information for administrative clients • Information about registered client nodes • Encryption key • Deduplication index • Disaster recovery plans Tivoli Storage Manager V7 database features • • • • •

Automatic statistics collection: Automatic collection: Automatic statistics collection helps to improve database performance by collecting up-to-date table statistics. Automatic database reorganization: Automatic reorganization: Automatic reorganization of the database tables is done based on the statistics gathered. SQL queries: You queries: You can get information from the server database with full-function SQL queries. The database makes more sophisticated SQL queries on the data possible. To use some of the capabilities, you might require more advanced SQL skills to develop new tools. Database audits: Audits audits: Audits on the database run automatically as needed to ensure consistency. c onsistency. Separate audits that might be long-running are not needed. Database buffer size: The size: The database manager automatically adjusts the values for several memory configuration parameters that are based on requirements of the workload of the system.

15

©

confidential

 

TSM Database and recoverylog overview and functions Tivoli Storage Manager Recovery log The recovery log helps ensure that a sudden failure does not leave the database in an inconsistent state. The recovery log is also necessary for restoring the database. All changes to the database since the last database backup are saved in the recovery log. With roll-forward mode and an intact recovery log, you can recover the database up to its most current state, st ate, the point at which the database was lost. The T he recovery log keeps all transactions since the last database backup. Frequent database backups reduce r ecovery log storage requirements. After a full backup finishes, recovery log records that precede the backup are deleted. The recovery log consists of the following logs •

Active log: The active log stores all the transactions that are not yet committed. The active log always contains the most recent log records.

•

s tored copy of the previous active log. Archived log files are stored until they are included in a database Archive log: The log: The archive log is a closed and stored backup. This log is not needed for normal processing, but it is needed to recover the database.\

•

Archive failover log: The log: The archive failover log is the directory that the server uses to store s tore archive log files that cannot be stored in the archive log directory.

•

Log mirror: The mirror: The log mirror is a duplicate copy of the active log. All changes that are made to the active log are also written to the t he log mirror. Having the log mirror for the active log can protect the database from a hardware failure that affects the active log. Place the log mirror on a different physical device.

Changes to the database are recorded in the recovery log for maintaining a consistent database image.

16

©

confidential

 

TSM Database and recoverylog overview and functions TSM Database size estimation The size of your Tivoli Storage Manager database depends on the number of client files to store and how Tivoli Storage Manager manages them. If you can estimate the maximum number of files that might be in server storage at any time, you can use the following information to come up with a useful database size estimate. • • •

Each version of a file that Tivoli Storage Manager stores requires about 400 to 600 bytes of bytes of database space. Each cached or storage pool copy of a file requires about 100 to 200 bytes of bytes of database space. Caching is turned off by default. It is used only to move from one storage pool to next. Overhead can increase the required space s pace by an additional 50%.

Maximum and Minimum size allowed for Database and Recovery log • • •

Database Minimum size: 2.2 GB Maximum size: 4 TB

Consider restore time when deciding how large the database should be. • • • •

Active log Minimum size: 2 GB Maximum size: 128 GB Default size: 16 GB

 Active log space requirements increase when you use data deduplication. deduplication. • • •

Archive log Large enough to contain the logs that the previous full backup generates Cleared only in the case of a full backup

17

©

confidential

 

Storage device management Tivoli Storage Manager Storage Pools Functions •

Files cantobe placedtoinitially on different pools according to therecovery stated storage management policy. Files are then moved automatically to other devices adhere free space, space storage utilization, performance, and requirements.

•  A storage destination destination identifies the storage pool where client client data goes when it is backed up, archived, or migrated. The management management class, which is a part of policy management, includes the backup and archive copy group definitions. These definitions specify the storage destination. Types of Storage Pools There 3 types of storage pools in pools  in Tivoli Storage Manager  •

Primary Storage Pool: It Pool: It is the first destination of client backups. It can c an either Disk, Tape Tape or FILE device class.

•

Copy storage pool: Backup copies of active and inactive data from primary storage pools for off-site storage. Copy storage s torage pools contain backups of the primary storage pools. You can backup storage pool data to disk, which uses a file device class, c lass, or removable media, such as tape.

•

Active-data pools: pools: Backup copies only of active data for fast restoration of client data. Active-data pools only contain the latest, or active version of data. Use them in the following situations



With sequential-access disk (FILE)



With sequential-access tape or optical



To collocate active versions of backup data



For backup data only, not for archive or HSM data



With the disaster recovery manager 

Defining storage pools • Example: • define stgpool testpool disk description="test storage s torage pool" maxsize=5m highmig=70 lowmig=30 cache=yes nextstgpool=destpool 

18

©

confidential

 

Storage device management Storage Pool Volumes  A volume is the basic unit of storage for Tivoli Storage Manager Manager storage pools. Tivoli Storage Storage Manager volumes can be mainly mainly classified according to status: private status:  private &  & scratch scratch  volumes. A private volume is volume is a labeled volume that is in use or owned by an application, and may contain valid data. You must define each private volume. A scratch volume is volume is a labeled volume that is empty or contains no valid data and that can be used to satisfy any request to mount a scratch volume. v olume. When data is written to a scratch volume, its status is changed c hanged to private, and it is defined as part of the t he storage pool for which the mount request was made. When valid data is moved from the volume and the volume is reclaimed, the volume returns to t o scratch status and can be reused by any storage pool associated with the library. • Defining storage pool volumes for disk To define storage pool volumes for a disk storage pool, use the following command DEFine VOLume poolname volname Formatsize=Format_size  Formatsize=Format_size   •

For example:

DEFine VOLume BACKUPPOOL /opt/tsmdata/v7 formatsize=500

Device Class Overview  A device class represents a set of storage devices with similar availability availability,, performance, and storage characteristics. •

Storing backup, archive, or space-managed data, primary storage pools.

•

Storing copies of primary storage pool data, copy storage pools.

•

Storing database backups.

•

Exporting or importing Tivoli Storage Manager data

19

©

confidential

 

TSM Physical Storage Devices Introduction Types of Physical Storage Devices used in TSM Environment The combination of the library, drives, and their device class represents the physical device environment. A physical library is a collection of one or more drives that shares similar media mounting requirements. Each drive mechanism within a device, that uses removable media, is represented by a drive object.For devices with multiple drives, including automated libraries, each drive is separately defined and must be associated with a library library.. A drive is a hardware device that is capable of performing operations on a specific type of sequential media. Drive definitions include such information as the element address, for drives in SCSI libraries, how often the drive is cleaned, for tape drives, and whether or not the drive is online. These are the terms we use in TSM environment. •

Library: A device that organizes Library: A organizes and holds one or more media, tape, or disk volumes and an an optional robotic mechanism. Use the define library library command and the define path command.

•

Drive: A Drive:  A hardware device capable of performing operations on a specific s pecific type of sequential media. Use the define drive command.

•

Device class: A class: A category that represents a device type that defines the media that the library uses. Use Us e the define devclass command

Types of Physical Libraries •

Tape libraries load required Tape Library example, TS3500 : Tivoli Storage Manager servers frequently store extremely large amounts of data. Tape tapes into drives automatically, which might be expandable, depending on model.

•

Virtual Tape Library (VTL) example, TS 7650: VTLs are disk devices that can simulate s imulate tape by using a software or firmware interface. VTLs might have built-in functions for compression and data deduplication. They are easily configurable when you perform LAN-free backups to disk.

•

Disk example, DS8000 : DS8000 : Disks can be large or small, and might be attached directly to the Tivoli Storage Manager server or connected by using a SAN. Tivoli Storage Manager can store data on Random Access disk pools and store data by using tape volumes that Tivoli Storage Manager software simulates

20

©

confidential

 

TSM Physical Storage Devices Introduction How to find devices on AIX •

# lsdev -Cc disk 

hdisk0 Available Available 40-60-00-4,0 16 Bit SCSI Disk Drive • • • •

# lsdev -Cc tape rmt0 Available 1P-08-00-0,0 4.0 GB 4mm Tape Drive rmt1 Available 1P-08-00-2,0 4.0 GB 4mm Tape Drive smc0 Available 1P-08-00-3,0 IBM 7336 Tape Medium Changer 

How to install and Configure Tape Library Before you install and configure Tape Tape library to TSM server, you first have to install suitable device drivers and double check the drives are visible by using OS commands. • DEFine LIBRary library_name LIBType=library_type LIBType=library_type • DEFine PATH PATH source_name destination_name LIBRary=library_name SCRType=SERV SCRType=SERVer er DESTType= DESTType=LIBRary LIBRary DEVice=device_name • DEFine Drive library_name drive_name • DEFine PA PATH TH source_name destination_name SCRT SCRType=SERV ype=SERVer er DESTType= DESTType=DRive DRive DEVice=device_name Library manager & Library client concepts TSM introduced dynamic sharing of direct connected tape-libraries between servers to address the following goals. Use Tape library resource more efficiently. Optimize the use of scratch tape by dynamically sharing them across multiple TSM servers Library manager: The task of the library manager is to t o physically control the library. All the communication with the library is done by this server. The library manager will also serialize the access to the tape drives, so that only one server is using a tape drive at any time. Library client: The library client uses the library server for the handling of the physical hardware. The client sends the requests to the t he library manager, manager, and afterwards reads or writes to the tape t ape drive it was given access to. t o.

21

©

 

Migration Process  Automatic data movement between storage pools balances the performance and cost of different storage devices while ensuring adequate free space to meet new space allocations. This process is known as migration. For each storage pool, you define low and high migration thresholds. Migration thresholds are based on a percentage of the storage pool’s total data capacity. The low threshold identifies the amount of free space needed to meet the daily processing requirements of your business. The high threshold triggers migration and ensures that enough free space isavailable while migration occurs. The difference between the high and low thresholds indicates the approximate amount of data that is migrated. There are two ways to initiate a migration: 

Update the storage pool, modifying the values of HIghmig, LOwmig, or both.



Use the migrate stgpool command in Tivoli Storage Manager 

confidential

22

©

 

TSM Reclamation process Reclamation is a server process that t hat consolidates data and free space on tape (or optical) volumes in sequential storage pools. Over time, versions of backed-up files expire, or perhaps files are deleted from client file systems. It is common for tape volumes to contain files that will expire on different dates. When the expiration process occurs, expired ex pired and deleted files are marked as no longer required, and the tape volumes on which these files are stored s tored now have empty space where the files physically resided . Over time, as more and more files are expired from a tape volume, its active data spaces become fragmented by the increasing empty space. Reclamation means moving the active data to another volume in the same storage pool. When all the data is moved from the original tape to another, the original becomes empty, and is typically returned to a status of “scratch”. A scratch tape can be re-used for any function for which the server requires a volume.

confidential

23

©

 

TSM Collocation s erver Collocation is the process by which the server minimizes the number of sequential access storage volumes to keep files of a single s ingle client node or file space of a client node. You can set collocation for each sequential access storage pool when you define or update the pool. By using collocation, you reduce the number of volume mount operations, and the amount of time searching database entries when users restore, retrieve, or recall multiple files. Thus, collocation improves access time for these operations. If collocation is enabled and reclamation occurs, the server tries to reclaim the files for each client node or client file space onto a minimal number of volumes. Collocation cannot collocate data that is already in a storage pool volume. The following options are available for collocation c ollocation when you use the define stgpool or update stgpool commands stgpool  commands 

No



Node



File space



Group by node



Group by file space

confidential

24

Group by file space ©

 

TSM EXPIRE INVENTORY

Expiration is the process, where the expired object (backed up files which have crossed its retention) gets deleted from TSM inventory. It is advisable to run expiration process at least once in a day day.. Once expiration process completes successfully succes sfully,, TSM db size could come down by few fractions. To invoke expiration process manually,, execute the command manually expire inventory inventory.. Command to manually starts inventory expiration processing: Expire Inventory Beginnodeid=xxxx Endnodeid=yyyy

confidential

25

©

 

TSM Policy Management Overview  A TSM policy policy management address the following business (SLA) (SLA) requirements •

Data to back up: Specify the items to store as back up objects.

•

Data to archive: Specify the items to store as archive objects.

•

Location to store the data: Specify the storage pools to use.

•

Number of versions to retain: Specify the number of inactive versions, in addition to the active version, to keep when the data still exists on the client c lient node.

•

The retention period: Specify the duration to store the data associated with the policy.

Policies include the following elements. •

Policy Domain: A Domain: A set of rules that are applied to a group of nodes that the same set of policy constraints manage, as defined by the policy sets. A node can be defined to only one policy domain per server. A node can be defined to more than one Tivoli Storage Manager server.

Define domain description= •

Policy Set: A Set: A collection of management class (MC) definitions. A policy domain can contain a number of policy sets. However, only one policy set in a domain is active at a time.

Define policyset •

Management Class: A Class: A collection of management attributes that describe backup and archive characteristics. There are two sets of MC attributes, one for backup and one for archive. A set of attributes is a copy group. There is a backup copy group and an archive copy c opy group. For Tivoli Space Manager clients only, only, there are parameters that affect space management.

Define managementclass

confidential

26

©

 

TSM Policy Management Overview •

Copy Groups: A Groups: A copy group contains the specific specific storage management attributes that describe how the server manages backed up orarchived files. Copy groups contain the parameters that control the generation and expiration of backup and archive data. There are two types of copy groups Backup and Archive Each management class contains up to two copy groups. If I f it has two copy groups, one is for backups, and one is for archives. All copy groups are named STANDARD.

The set of backup backup parameters  parameters defines the following attributes: • Frequency • Mode (modified or absolute) • • • • • •

Destination Copy serialization Number of versions Number of versions when the file is deleted Retention days for all but the last version Retention days for the last version when the file is deleted

The set of archive archive parameters  parameters defines the following attributes: • • • • •

Frequency (always CMD) Mode (always ABSOLUTE) Destination Copy serialization Retention days for archive copies

To define a new copy group following command is used, us ed, Define copygroup type=backup destination= verdataexists= verdeleted= retextra= retonly= ©

confidential

 

Serialization SHRSTatic : • Specifies that Tivoli Storage Manager backs up a file or directory only if it is not being modified during backup. Tivoli Storage Storage Manager attempts to perform a backup as many as four times, depending on the value specified for the CHANGINGRETRIES client option. If the file or directory is modified during each backup attempt, Tivoli Storage Manager does not back it up.

STatic: •

Specifies that Tivoli Storage Manager backs up a file or directory only if it is not being modified during backup. Tivoli Storage Storage Manager attempts to perform the backup only once. Platforms that do not support the STATIC option default to SHRSTATIC. SHRSTATIC.

SHRDYnamic  :  : •

Specifies that if the file or directory is being modified during a backup attempt, Tivoli Storage Manager Manager backs up the file or directory during the last attempt even though the file or directory is being modified. Tivoli Storage Manager attempts to perform a backup as many as four times, depending on the value specified for the CHANGINGRETRIES client option.

Dynamic : •

Specifies that Tivoli Storage Manager backs up a file or directory on the first attempt, regardless of whether the file or directory is being modified during backup processing. Specifies how Tivoli Storage Manager handles files or directories when they are modified during backup processing. This parameter is optional. The default value v alue is SHRSTATIC. SHRSTATIC. Possible values are:

28

©

confidential

 

TSM retention Concepts Active and inactive file versions •

One of the most important concepts in Tivoli Storage Manager data management is the difference between an active backup version and an inactive backup version.

•  Assume that a new file is created on your workstation. The next time you run a backup operation operation (say, Monday Monday at 9 p.m.), Tivoli Storage Manager Manager server backs up this file. This copy of the file is known as the ACTIVE version, since it is the most recent version of the file. When you next run an incremental backup (say, Tuesday Tuesday at 9 p.m.), Tivoli Storage Manager uses this ACTIVE version already stored to check back with your workstation to determine whether the file has changed since the last backup. If it has, it is backed up again. This version now becomes the ACTIVE version and the copy fromexists Monday becomes INACTIVE version. The mostwill recent version of theversion file is always the ACTIVE long as the fileup itself still on the originalanclient. Tivoli Storage Storag e Manager keepbacked-up storing a new ACTIVE and inactivating theversion, previousasactive version, to the limit of the total number of versions v ersions defined to be retained in the management class. Once this limit is exceeded, exc eeded, the oldest INACTIVE version is deleted from Tivoli Storage Manager storage and will no longer be able to be restored. •

Tivoli Storage Manager controls the retention of its ACTIVE and INACTIVE versions of a file that exists on a client c lient machine by using two criteria defined in the Management Class:

•

Ver Exists

Nu. of backup versions •

Retextra

Specifies the duration for retaining inactive files •

Verdeleted

Nu of inactive file versions •

RETON

29

The RETONLY parameter parameter controls the last inactive copy of a file ©

 

TSM retention Concepts Version Control

confidential

30

©

 

TSM health check Administrative schedules  An administrative schedule is a directive to trigger an action action within the Tivoli Storage Manager server. server. It consists of a server command and extra parameters describing when the action should happen. As each administrative schedule can only run one server command, the command itself may be a run command, which runs an internally defined server script containing other internal server commands:

 Administrative schedules shall be used for executing the following following admin process, 

Backup Storage pool



Migration



Database Backup



Expiration



Reclamation. (Primary & Copy tape pools)



Creating plan file

confidential

31

©

 

confidential

TSM health check Daily Admin Tasks •

The following list describes some of the tasks that are important to monitor daily.



Verify that the database file system has enough space. Examine the database percent utilization, available free space, s pace, and free-pages. Verify that there is enough disk space in the file systems that contain these log files (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 c ompleted successfully, and that they are running frequently enough. Check the database and recovery log statistics. Verify that you have current backup files for device configuration and volume history information. You can find the file names for the backups by

     



looking in the dsmserv.opt file for the DEVCONFIG and VOLUMEHISTORY options. Ensure that file systems where the t he files are stored have sufficient space. Search the summary table for failed processes. Search the activity log for error messages. For storage pools that have deduplication enabled, ensure that processes are completing successfully. Check the status of your storage pools to ensure that there is enough space available. Check for any failed storage pool migrations. Check the status of sequential access storage pools. Check how many scratch volumes v olumes 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. Verify that all of the tapes have the appropriate write-access. Verify the status and settings for disaster recovery manager (DRM). Check for failed or missed schedules. Check the summary table for scheduled sc heduled client operations such as backup, restore, archive, and retrieve.



Check the summary table for scheduled sc heduled server operations such as migration, reclamation, and expiration.

           

32

©

 

TSM Server and Client event logs and activity logs Error codes TSM codes can be found in TSM server ’s activity log, TSM clients schedlog & error log files. TSM error codes will look like, •

AN(R/S/E) XXXX(I/W/E/S) where,

•

ANR states problem on TSM server.

•

ANS states problem on TSM client.

•

ANE States it’s an Event

This will be followed by a 4 digit no which is specific to each and every type of error. The last character can be one among the four, •

E – Indicates an error 

•

I – Indicates information

•

W – Indicates a warning message

•

S – Indicates a severity message

confidential

33

©

confidential

 

TSM Server and Client event logs and activity logs Querying events and the activity log Use the query event command event command to show the status st atus of scheduled events. With the time and date parameters, you can limit the query to events that are scheduled to occur within the specified times and dates. The command syntax: •

Example : query event domainname schedname begindate=11/22/2014 begindate=11/22/2014 enddate=14/24/2014 exceptionsonly=yes

Use the query actlog command actlog command to show messages that the t he server generates. The activity log contains all messages that are sent to the server console c onsole under normal operation. •

Example : query actlog begindate=today-1 begintime=15:00:00 endtime=22:30:00 endtime=22:30:00 search=‘XXXXX’ 

TSM BA Client log files •

dsmsched.log

•

Contains status information for the Tivoli Storage Manager scheduler service.

•

Contains Information about the schedule that runs next and the files that are processed.

•

Change file name by specifying the schedlog name option in the options file.

•

dsmerror.log

•

Contains information about errors that occur during processing.

•

The errorlogname option specifies the fully qualified path and file name of the file to store information about errors that occur during processing.

34

©

 

confidential

 Using SQL commands to query TSM DB2 database You can use SQL queries to get information from the TIvoli T Ivoli storage Manager Database. You can use the SQL SELECT commands to customize a wide variety of queries. Some queries require server time and resources and might impact performance. To To help you find what information is available in the database, Tivoli Storage Manager provides three system catalog tables. SYSCAT.TABLES Contains information about all tables that can be queried with the SELECT command. SYSCAT.COLUMNS Describes the columns in each table. SYSCAT.ENUMTYPES Defines the valid values for each enumerated type and the order of the t he values for each type.

Some Commonly used SQL Queries on TSM 6 & TSM 7 •

TSM DB Utilization SELECT CAST(SUM(100-(free_space_mb*100) / tot_file_system_mb) AS DECIMAL(3,1)) AS PCT_UTILIZED FROM db

•

TSM log recovery utilization (%) SELECT CAST(SUM(used_space_mb *100 / total_space_MB) AS DECIMAL(3,1)) AS PCT_UTILIZED FROM log 

•

Space and number of files stored per client  SELECT node_name,CAST(FLOAT(SUM(physical_mb)) node_name,CAST(FLOAT(SUM(physical_mb)) / 1024 AS DEC(8,2))as "Space in GB", -

•

  SUM(num_files)as"Number of files" files" FROM occupancy GROUP BY node_name

•

Information about drives x paths   SELECT b.source_name, a.library_name, a.drive_name, a.drive_serial, a.drive_serial, b.device FROM drives a, paths b WHERE a.drive_name=b.destination_name

•

Total client data stored (TB)

35

 SELECT CAST(FLOAT(SUM(logical_mb)) CAST(FLOAT(SUM(logical_mb)) / 1024 / 1024 AS DEC(8,2)) FROM FR OM occupancy  ©

 

Q&A

confidential

36

©

 

Thank you

confidential

37