ibmtivoli storage manager for linux version 7.1 · this edition applies to version 7, release 1,...

IBM Tivoli Storage Managerfor LinuxVersion 7.1.1

Administrator's Guide

��

Note:Before using this information and the product it supports, read the information in “Notices” on page 1119.

Second edition (September 2014)

This edition applies to version 7, release 1, modification 1 of IBM Tivoli Storage Manager (product numbers5608-E01, 5608-E02, 5608-E03), and to all subsequent releases and modifications until otherwise indicated in neweditions.

© Copyright IBM Corporation 1993, 2014.US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contractwith IBM Corp.

Contents

About this publication . . . . . . . . xiiiWho should read this guide . . . . . . . . xiiiPublications . . . . . . . . . . . . . . xiiiConventions used in this guide . . . . . . . xiii

New for IBM Tivoli Storage ManagerVersion 7.1 . . . . . . . . . . . . . xvNew in this release . . . . . . . . . . . . xv

Operations Center updates . . . . . . . . xvTivoli Monitoring for Tivoli Storage Managerupdates . . . . . . . . . . . . . . xviUpdates for the Tivoli Storage Manager servercomponent . . . . . . . . . . . . . xvii

Best practices for Version 7.1 . . . . . . . . xixMaximum daily capability for datadeduplication . . . . . . . . . . . . xixServer startup and setting ulimits . . . . . . xixDuplicate identification processes and memoryrequirements . . . . . . . . . . . . . xxConfiguring the server to prevent issues withdatabase backups . . . . . . . . . . . xx

Part 1. Tivoli Storage Managerbasics . . . . . . . . . . . . . . . 1

Chapter 1. Tivoli Storage Manageroverview . . . . . . . . . . . . . . 3Data protection services . . . . . . . . . . 5Data protection operations . . . . . . . . . . 7

Progressive incremental backups . . . . . . 12Storage-pool and server-inventory backups . . . 12

How client data is stored . . . . . . . . . . 13Tivoli Storage Manager data management process 14Data movement to server storage . . . . . . 15Management of server storage . . . . . . . 16Consolidation of backed-up client data . . . . 17

Interfaces to Tivoli Storage Manager . . . . . . 18

Chapter 2. Tivoli Storage Managerserver concepts . . . . . . . . . . . 21Storage configuration and management . . . . . 21

Tivoli Storage Manager storage objects . . . . 22Disk devices . . . . . . . . . . . . . 24Storage pools and storage-pool volumes . . . . 24Removable media operations . . . . . . . 30

Policy-based data management . . . . . . . . 36Policy components . . . . . . . . . . . 36Client operations controlled by policy . . . . 38Management classes . . . . . . . . . . 40How files and directories are associated with amanagement class . . . . . . . . . . . 43

Management of client operations . . . . . . . 46Tasks for client nodes . . . . . . . . . . 46

Security management . . . . . . . . . . 48Schedules for client operations . . . . . . . 49

Server management . . . . . . . . . . . 50Server-operation management . . . . . . . 50The server database and recovery log. . . . . 51Sources of information about the server . . . . 53Tivoli Storage Manager server networks . . . . 53Data export and import . . . . . . . . . 54

Server and client data protection . . . . . . . 54Disaster recovery . . . . . . . . . . . 55

Part 2. Configuring and managingstorage devices . . . . . . . . . . 57

Chapter 3. Planning for server storage 59Road map for key device-related task information 60Supported library types . . . . . . . . . . 61Tivoli Storage Manager device classes . . . . . 64

Disk devices . . . . . . . . . . . . . 64Removable media . . . . . . . . . . . 64Files on disk as sequential volumes (FILE) . . . 64Files on sequential volumes (CENTERA) . . . 65Sequential volumes on another Tivoli StorageManager server (SERVER) . . . . . . . . 66

Device configurations . . . . . . . . . . . 66Devices on local area networks . . . . . . . 67Devices on storage area networks . . . . . . 67LAN-free data movement. . . . . . . . . 69Network-attached storage . . . . . . . . 70Mixed device types in libraries . . . . . . . 72Library sharing . . . . . . . . . . . . 74

Chapter 4. Magnetic disk devices . . . 75Requirements for disk systems . . . . . . . . 75Comparison of random access and sequential accessdisk devices . . . . . . . . . . . . . . 77Configuring random access volumes on disk devices 81Configuring FILE sequential volumes on diskdevices . . . . . . . . . . . . . . . . 82Varying disk volumes online or offline . . . . . 83Cache copies for files stored on disk . . . . . . 84Freeing space on disk . . . . . . . . . . . 84Scratch FILE volumes . . . . . . . . . . . 85Volume history file and volume reuse . . . . . 85

Chapter 5. Attaching devices for theserver . . . . . . . . . . . . . . . 87Attaching a manual drive to your system . . . . 87Attaching an automated library device to yoursystem . . . . . . . . . . . . . . . . 88

Setting the library mode . . . . . . . . . 89Selecting a device driver . . . . . . . . . . 89

IBM device drivers . . . . . . . . . . . 89Tivoli Storage Manager device drivers . . . . 90

© Copyright IBM Corp. 1993, 2014 iii

|||

Device special file names . . . . . . . . . . 90Correcting device special file names withSANDISCOVERY . . . . . . . . . . . 91

Tivoli Storage Manager server device utilities . . . 91autoconf (Auto configure devices) . . . . . . 91

Installing and configuring device drivers . . . . 92Installing device drivers for IBM SCSI tapedevices . . . . . . . . . . . . . . . 92Installing device drivers for IBM 349x libraries 94Configuring Tivoli Storage Manager passthrudrivers for tape devices and libraries . . . . . 95Installing zSeries Linux fibre-channel adapter(zfcp) device drivers . . . . . . . . . . 96Information about your system's SCSI devices . . 96Preventing tape labels from being overwritten . . 97

Installing the Centera SDK for Centera sharedlibraries . . . . . . . . . . . . . . . 98

Chapter 6. Configuring storagedevices . . . . . . . . . . . . . . 101Configuring libraries for use by one server . . . 102

Example: Configure a SCSI or virtual tapelibrary with a single drive device type . . . . 103Example: Configure a SCSI or virtual tapelibrary with multiple drive device types . . . 104Example: Configure an ACSLS library with asingle drive device type . . . . . . . . . 106Example: Configure an ACSLS library withmultiple drive device types. . . . . . . . 107Example: Configure a 3494 library with a singledrive device type . . . . . . . . . . . 108Example: Configure a 3494 library with multipledrive device types . . . . . . . . . . . 109

Configuring library sharing. . . . . . . . . 110Example: Configure library sharing for SCSI orvirtual tape libraries . . . . . . . . . . 111Example: Configure library sharing for ACSLSlibraries . . . . . . . . . . . . . . 113Example: Configure library sharing for 3494libraries . . . . . . . . . . . . . . 114

Managing virtual tape libraries . . . . . . . 114Considerations for using virtual tape libraries 115Adding a virtual tape library to yourenvironment . . . . . . . . . . . . . 116Defining or deleting all drives and paths for asingle library . . . . . . . . . . . . 117

Migrating a shared IBM 3494 library to a librarymanager . . . . . . . . . . . . . . . 118Sharing an IBM 3494 library by static partitioningof drives . . . . . . . . . . . . . . . 119Removable file device configuration . . . . . . 119

Example of removable file support . . . . . 120Labeling requirements for removable file devicetypes . . . . . . . . . . . . . . . 121

Configuration for libraries controlled by mediamanager programs . . . . . . . . . . . 121

Setting up Tivoli Storage Manager to work withan external media manager . . . . . . . . 122Externally controlled IBM Tivoli StorageManager media. . . . . . . . . . . . 123

Configuring manually mounted devices . . . . 124

Defining devices as part of a manual library . . 124Labeling volumes . . . . . . . . . . . 125

Configuring IBM Tivoli Storage Manager forLAN-free data movement . . . . . . . . . 126

Validating your LAN-free configuration . . . 127SAN discovery functions for non-root users . . 127

Configuring the Tivoli Storage Manager server touse z/OS media server storage . . . . . . . 128

Tivoli Storage Manager for z/OS Mediaoverview . . . . . . . . . . . . . . 128Data flow in a Tivoli Storage Manager for z/OSMedia environment . . . . . . . . . . 128Planning for z/OS media server operations . . 130Configuration tasks . . . . . . . . . . 132

Impacts of device changes on the SAN . . . . . 135

Chapter 7. Managing removable mediaoperations. . . . . . . . . . . . . 137Preparing removable media . . . . . . . . 137

Labeling removable media volumes . . . . . 138Checking new volumes into a library . . . . 141Write-once, read-many tape media . . . . . 146

Managing the volume inventory . . . . . . . 148Controlling access to volumes . . . . . . . 148Reusing tapes in storage pools . . . . . . 149Setting up a tape rotation . . . . . . . . 149Reusing volumes used for database backupsand export operations . . . . . . . . . 151Maintaining a supply of scratch volumes . . . 151

Managing volumes in automated libraries . . . . 152Changing the status of a volume . . . . . . 152Removing volumes from a library . . . . . 153Managing a full library . . . . . . . . . 153Auditing a library's volume inventory . . . . 154Maintaining a supply of scratch volumes in anautomated library . . . . . . . . . . . 155Operations with shared libraries . . . . . . 155

Managing server requests for media . . . . . . 157Managing libraries . . . . . . . . . . . 158

Requesting information about libraries . . . . 159Updating libraries . . . . . . . . . . . 159Deleting libraries . . . . . . . . . . . 160

Managing drives . . . . . . . . . . . . 160Requesting information about drives . . . . 161Updating drives . . . . . . . . . . . 161Drive encryption . . . . . . . . . . . 162Validating data during read/write operations totape . . . . . . . . . . . . . . . 164Cleaning drives . . . . . . . . . . . 168Deleting drives . . . . . . . . . . . . 173

Managing paths . . . . . . . . . . . . 173Requesting information about paths . . . . . 173Updating paths. . . . . . . . . . . . 173Deleting paths . . . . . . . . . . . . 174

Managing data movers . . . . . . . . . . 174Requesting information about data movers . . 174Updating data movers . . . . . . . . . 174Deleting data movers. . . . . . . . . . 175

Tape alert messages . . . . . . . . . . . 175

iv IBM Tivoli Storage Manager for Linux: Administrator's Guide

Chapter 8. Tips for defining devices 177Definitions for storage devices. . . . . . . . 177

Example: Mapping devices to device classes . . 178Example: Mapping storage pools to deviceclasses and devices . . . . . . . . . . 178

Defining devices and paths . . . . . . . . . 179Defining libraries . . . . . . . . . . . 179Defining drives. . . . . . . . . . . . 180Defining data movers . . . . . . . . . 182Defining paths . . . . . . . . . . . . 182Shared FILE volumes. . . . . . . . . . 183

Defining device classes . . . . . . . . . . 184Sequential-access device types . . . . . . . 186Defining tape device classes . . . . . . . 187Defining device classes for removable mediadevices . . . . . . . . . . . . . . 193Defining sequential-access disk (FILE) deviceclasses. . . . . . . . . . . . . . . 194Defining LTO device classes . . . . . . . 198Defining SERVER device classes . . . . . . 201Defining device classes for StorageTek VolSafedevices . . . . . . . . . . . . . . 202Defining device classes for CENTERA devices 204Obtaining information about device classes . . 205How Tivoli Storage Manager fills volumes . . 206

Chapter 9. Using NDMP for operationswith NAS file servers . . . . . . . . 209NDMP requirements . . . . . . . . . . . 209

Interfaces for NDMP operations . . . . . . 212Data formats for NDMP backup operations . . 212

NDMP operations management . . . . . . . 213Managing NAS file server nodes . . . . . . 213Managing data movers used in NDMPoperations . . . . . . . . . . . . . 214Dedicating a Tivoli Storage Manager drive toNDMP operations . . . . . . . . . . . 214Storage pool management for NDMP operations 215Managing tables of contents . . . . . . . 215Preventing long-running, inactive NDMPconnections from closing . . . . . . . . 216

Configuring Tivoli Storage Manager for NDMPoperations . . . . . . . . . . . . . . 217

Configuring Tivoli Storage Manager policy forNDMP operations . . . . . . . . . . . 218Tape libraries and drives for NDMP operations 221Attaching tape library robotics for NAS-attachedlibraries . . . . . . . . . . . . . . 225Registering NAS nodes with the Tivoli StorageManager server. . . . . . . . . . . . 229Defining a data mover for a NAS file server . . 230Defining paths for NDMP operations . . . . 230Labeling and checking tapes into the library . . 234Scheduling NDMP operations . . . . . . . 235Defining virtual file spaces . . . . . . . . 235Tape-to-tape copy to back up data . . . . . 235Tape-to-tape copy to move data . . . . . . 236

Backing up and restoring NAS file servers usingNDMP . . . . . . . . . . . . . . . 236

NAS file servers: backups to a single TivoliStorage Manager server . . . . . . . . . 237Backing up NDMP file server to Tivoli StorageManager server backups. . . . . . . . . 238

File-level backup and restore for NDMP operations 239Interfaces for file-level restore . . . . . . . 240International characters for NetApp file servers 241File level restore from a directory-level backupimage . . . . . . . . . . . . . . . 242

Directory-level backup and restore . . . . . . 242Directory-level backup and restore for NDMPoperations . . . . . . . . . . . . . 242Backing up and restoring with snapshots . . . 243

Backup and restore using NetApp SnapMirror toTape feature . . . . . . . . . . . . . . 243NDMP backup operations using Celerra file serverintegrated checkpoints . . . . . . . . . . 244Replicating NAS nodes with NDMP backup data 245

Chapter 10. Managing storage poolsand volumes. . . . . . . . . . . . 247Defining storage pools . . . . . . . . . . 247

Properties of storage pool definitions . . . . 248Example: Defining storage pools . . . . . . 251Example: Updating storage pools. . . . . . 253Example: Setting up server storage . . . . . 253

Task tips for storage pools . . . . . . . . . 255Managing storage pool volumes . . . . . . . 257

Random-access storage pool volumes . . . . 257Sequential-access storage pool volumes. . . . 257Preparing volumes for random-access storagepools . . . . . . . . . . . . . . . 259Preparing volumes for sequential-access storagepools . . . . . . . . . . . . . . . 260Updating storage pool volumes . . . . . . 263Access modes for storage pool volumes . . . 264

Setting up a storage pool hierarchy . . . . . . 265Example: Defining a storage pool hierarchy . . 266Example: Updating a storage pool hierarchy . . 266How the server groups files for storage . . . 267Where the server stores files . . . . . . . 268Example: How the server determines where tostore files in a hierarchy . . . . . . . . . 268Backing up the data in a storage hierarchy . . 270Staging client data from disk to tape . . . . 275Migrating files in a storage pool hierarchy. . . 276

Caching in disk storage pools . . . . . . . . 289How the server removes cached files . . . . 290Effect of caching on storage pool statistics . . . 290

Deduplicating data . . . . . . . . . . . 290Data deduplication overview . . . . . . . 291Data deduplication limitations. . . . . . . 294Planning guidelines for data deduplication . . 296Detecting possible security attacks duringclient-side data deduplication . . . . . . . 308Evaluating data deduplication in a testenvironment. . . . . . . . . . . . . 309Managing deduplication-enabled storage pools 311Controlling data deduplication . . . . . . 315Displaying statistics about server-side datadeduplication . . . . . . . . . . . . 324

Contents v

Displaying statistics about client-side datadeduplication . . . . . . . . . . . . 325Querying file spaces for information aboutdeduplicated data . . . . . . . . . . . 328Scenarios for data deduplication . . . . . . 329Data deduplication and data compatibility . . 334Data deduplication and disaster recoverymanagement . . . . . . . . . . . . 336

Writing data simultaneously to primary, copy, andactive-data pools . . . . . . . . . . . . 337

Guidelines for using the simultaneous-writefunction . . . . . . . . . . . . . . 338Limitations that apply to simultaneous-writeoperations . . . . . . . . . . . . . 339Controlling the simultaneous-write function . . 340Simultaneous-write operations: Examples . . . 344Planning simultaneous-write operations . . . 358Simultaneous-write function as part of a backupstrategy: Example . . . . . . . . . . . 362

Keeping client files together using collocation . . 363The effects of collocation on operations . . . . 365How the server selects volumes with collocationenabled . . . . . . . . . . . . . . 367How the server selects volumes with collocationdisabled . . . . . . . . . . . . . . 369Collocation on or off settings . . . . . . . 369Collocation of copy storage pools andactive-data pools . . . . . . . . . . . 370Planning for and enabling collocation . . . . 371

Reclaiming space in sequential-access storage pools 373Reclaiming volumes with the most reclaimablespace . . . . . . . . . . . . . . . 374Starting reclamation manually or in a schedule 374Optimizing drive usage using multipleconcurrent reclamation processes . . . . . . 375Reclaiming volumes in a storage pool with onedrive . . . . . . . . . . . . . . . 376Reducing the time to reclaim tape volumes withhigh capacity . . . . . . . . . . . . 377Controlling reclamation of virtual volumes . . 377Reclaiming copy storage pools and active-datapools . . . . . . . . . . . . . . . 378How collocation affects reclamation . . . . . 382

Estimating space needs for storage pools . . . . 383Estimating space requirments in random-accessstorage pools . . . . . . . . . . . . 383Estimating space needs in sequential-accessstorage pools . . . . . . . . . . . . 385

Monitoring storage-pool and volume usage . . . 385Monitoring space available in a storage pool 385Monitoring the use of storage pool volumes . . 388Monitoring migration processes . . . . . . 396Monitoring the use of cache space on diskstorage . . . . . . . . . . . . . . 399Obtaining information about the use of storagespace . . . . . . . . . . . . . . . 400

Moving data from one volume to another volume 404Data movement within the same storage pool 405Data movement to a different storage pool . . 406Data movement from offsite volumes in copystorage pools or active-data pools . . . . . 406

Moving data . . . . . . . . . . . . 407Moving data belonging to a client node . . . . 410

Moving data in all file spaces belonging to oneor more nodes . . . . . . . . . . . . 410Moving data in selected file spaces belonging toa single node . . . . . . . . . . . . 411Obtaining information about data-movementprocesses . . . . . . . . . . . . . . 412Troubleshooting incomplete data-movementoperations . . . . . . . . . . . . . 412

Renaming storage pools . . . . . . . . . . 413Defining copy storage pools and active-data pools 413

Example: Defining a copy storage pool . . . . 415Properties of primary, copy, and active-datapools . . . . . . . . . . . . . . . 415Copying active versions of client backup data toactive-data pools . . . . . . . . . . . 417Selection for active file versions . . . . . . 417

Deleting storage pools . . . . . . . . . . 418Deleting storage pool volumes . . . . . . . 419

Deleting empty storage pool volumes . . . . 419Deleting storage pool volumes that contain data 420

Part 3. Managing client operations 421

Chapter 11. Adding client nodes . . . 423Overview of clients and servers as nodes . . . . 423Installing client node software . . . . . . . . 424Registering nodes with the server . . . . . . 424

Accepting default closed registration or enablingopen registration . . . . . . . . . . . 425Registering nodes with client options sets . . . 427Registering a network-attached storage fileserver as a node . . . . . . . . . . . 427Registering a source server as a node on a targetserver . . . . . . . . . . . . . . . 428Registering an API to the server . . . . . . 428

Connecting nodes with the server . . . . . . 429Required client options . . . . . . . . . 429UNIX and Linux client options . . . . . . 430

Creating or updating a client options file . . . . 430Using a text editor to create or configure a clientoptions file . . . . . . . . . . . . . 430Using the client configuration wizard to createor update a client options file . . . . . . . 430

Comparing network-attached nodes to local nodes 431Adding clients through the administrativecommand line client . . . . . . . . . . . 432

Enabling open registration . . . . . . . . 432Example: registering three client nodes usingthe administrative command line . . . . . . 432

Chapter 12. Managing client nodes 433Managing nodes . . . . . . . . . . . . 433

Managing client nodes across a firewall . . . 434Updating client node information . . . . . 436Automatic deployment feature for thebackup-archive client . . . . . . . . . . 436Renaming client nodes . . . . . . . . . 437Locking and unlocking client nodes . . . . . 437

vi IBM Tivoli Storage Manager for Linux: Administrator's Guide

|||

Deleting client nodes . . . . . . . . . . 438Consolidating multiple clients under a singleclient node name . . . . . . . . . . . 438Displaying information about client nodes. . . 441Overview of remote access to webbackup-archive clients . . . . . . . . . 443Managing client access authority levels . . . . 444

Managing file spaces . . . . . . . . . . . 447Defining client nodes and file spaces . . . . 448Supporting Unicode-enabled clients . . . . . 450Displaying information about file spaces . . . 459Moving data for a client node . . . . . . . 460Deleting file spaces . . . . . . . . . . 460

Managing client option files . . . . . . . . 461Creating client option sets on the server . . . 461Managing client option sets . . . . . . . 463

Managing IBM Tivoli Storage Manager sessions 464Displaying information about IBM TivoliStorage Manager sessions . . . . . . . . 464Canceling an IBM Tivoli Storage Managersession . . . . . . . . . . . . . . 465When a client session is automatically canceled 466Disabling or enabling access to the server . . . 467Managing client restartable restore sessions . . 468

Chapter 13. Implementing policies forclient data . . . . . . . . . . . . . 471Basic policy planning. . . . . . . . . . . 471

Reviewing the standard policy . . . . . . 472Getting users started . . . . . . . . . . 473Changing policy . . . . . . . . . . . 474File expiration and expiration processing . . . 474

How Tivoli Storage Manager selects files for policyoperations . . . . . . . . . . . . . . 475

Incremental backup . . . . . . . . . . 475Selective backup . . . . . . . . . . . 477Logical volume backup . . . . . . . . . 478Archive . . . . . . . . . . . . . . 478Automatic migration from a client node . . . 479

Creating your own policies . . . . . . . . . 480Defining and updating a policy domain . . . 481Managing backup copy groups . . . . . . 482Defining and updating an archive copy group 488Policy set validation and activation . . . . . 490Example: Sample policy objects . . . . . . 491Example: Create a new policy . . . . . . . 494

Policy configuration scenarios . . . . . . . . 495Configuring policy for direct-to-tape backups 496Configuring policy for Tivoli Storage Managerapplication clients . . . . . . . . . . . 497Policy for logical volume backups . . . . . 497Configuring policy for NDMP operations . . . 498Configuring policy for LAN-free datamovement . . . . . . . . . . . . . 499Policy for Tivoli Storage Manager servers asclients . . . . . . . . . . . . . . . 501Setting policy to enable point-in-time restore forclients . . . . . . . . . . . . . . . 501

Running expiration processing to delete expiredfiles . . . . . . . . . . . . . . . . 502

Running expiration processing automatically 502

Using commands to control expirationprocessing . . . . . . . . . . . . . 503Additional expiration processing with disasterrecovery manager . . . . . . . . . . . 503

Protection and expiration of archive data . . . . 504Data retention protection . . . . . . . . 504Deletion hold . . . . . . . . . . . . 505

Protecting data using the NetApp SnapLocklicensed feature. . . . . . . . . . . . . 506

Reclamation and the SnapLock feature . . . . 507Set up SnapLock volumes as Tivoli StorageManager WORM FILE volumes . . . . . . 511

Distributing policy using enterprise configuration 512

Chapter 14. Managing data for clientnodes. . . . . . . . . . . . . . . 513Validating node data . . . . . . . . . . . 513

Performance considerations for data validation 514Validating node data during a client session . . 514

Encrypting data on tape . . . . . . . . . . 514Choosing an encryption method . . . . . . 515Changing your encryption method andhardware configuration . . . . . . . . . 516

Securing sensitive client data . . . . . . . . 517Setting up shredding . . . . . . . . . . 518Ensuring that shredding is enforced . . . . . 519

Creating and using client backup sets . . . . . 521Generating client backup sets on the server . . 522Restoring backup sets from a backup-archiveclient . . . . . . . . . . . . . . . 526Moving backup sets to other servers. . . . . 526Managing client backup sets . . . . . . . 527

Enabling clients to use subfile backup . . . . . 530Setting up clients to use subfile backup. . . . 531Managing subfile backups . . . . . . . . 531

Archiving data . . . . . . . . . . . . . 532Archive operations overview . . . . . . . 533Managing storage usage for archives . . . . 533

Chapter 15. Scheduling operations forclient nodes . . . . . . . . . . . . 537Prerequisites to scheduling operations . . . . . 537Scheduling a client operation . . . . . . . . 538

Defining client schedules . . . . . . . . 539Associating client nodes with schedules . . . 540Starting the scheduler on the clients . . . . . 540Displaying schedule information . . . . . . 541Checking the status of scheduled operations . . 541

Creating schedules for running command files . . 542Updating the client options file to automaticallygenerate a new password . . . . . . . . . 543

Chapter 16. Managing schedules forclient nodes . . . . . . . . . . . . 545Managing IBM Tivoli Storage Manager schedules 545

Adding new schedules . . . . . . . . . 545Copying existing schedules . . . . . . . . 546Modifying schedules . . . . . . . . . . 546Deleting schedules . . . . . . . . . . 546Displaying information about schedules . . . 547

Contents vii

Managing node associations with schedules . . . 547Adding new nodes to existing schedules . . . 548Moving nodes from one schedule to another 548Displaying nodes associated with schedules . . 548Removing nodes from schedules . . . . . . 549

Managing event records . . . . . . . . . . 549Displaying information about scheduled events 549Managing event records in the server database 551

Managing the throughput of scheduled operations 552Modifying the default scheduling mode . . . 552Specifying the schedule period for incrementalbackup operations . . . . . . . . . . . 555Balancing the scheduled workload for the server 555Controlling how often client nodes contact theserver . . . . . . . . . . . . . . . 557

Specifying one-time actions for client nodes . . . 559Determining how long the one-time scheduleremains active . . . . . . . . . . . . 559

Part 4. Maintaining the server . . . 561

Chapter 17. Managing the storageenvironment from the OperationsCenter . . . . . . . . . . . . . . 563Operations Center overview . . . . . . . . 563Alert monitoring overview . . . . . . . . . 564Configuration tasks for alert monitoring . . . . 565Opening the Operations Center . . . . . . . 566Changing the Operations Center configuration . . 567

Changing the hub server . . . . . . . . 567Removing a spoke server . . . . . . . . 567Restoring the configuration to the preconfiguredstate . . . . . . . . . . . . . . . 568Starting and stopping the web server . . . . 569Restarting the initial configuration wizard . . . 570Setting the language of daily email reports . . 571

Chapter 18. Managing serveroperations. . . . . . . . . . . . . 573Licensing Tivoli Storage Manager. . . . . . . 573

License registration . . . . . . . . . . 574License compliance . . . . . . . . . . 575Role of processor value units in assessinglicensing requirements . . . . . . . . . 576Estimating processor value units . . . . . . 579Collecting processor value unit information in aVMware host environment . . . . . . . . 581

Starting the Tivoli Storage Manager server . . . 582Starting the server on AIX, HP-UX, Linux, andSolaris . . . . . . . . . . . . . . . 582Running multiple server instances on a singlesystem . . . . . . . . . . . . . . 591

Halting the server . . . . . . . . . . . . 592Stopping the server when it is running as abackground process . . . . . . . . . . 593

Moving the Tivoli Storage Manager server toanother system . . . . . . . . . . . . . 593Date and time on the server . . . . . . . . 594Managing server processes . . . . . . . . . 594

Requesting information about server processes 595Canceling server processes . . . . . . . . 596Preempting operations . . . . . . . . . 596

Changing names in Tivoli Storage Manager . . . 598Setting the server name . . . . . . . . . 598Changing the host name for a Tivoli StorageManager server. . . . . . . . . . . . 599

Add or update server options . . . . . . . . 600Add or update a server option withoutrestarting the server . . . . . . . . . . 600

Deleting information about volume history . . . 600Getting help on commands and error messages . . 601

Chapter 19. Automating serveroperations. . . . . . . . . . . . . 603Basic administrative command schedules . . . . 604

Defining the schedule . . . . . . . . . 604Verifying the schedule . . . . . . . . . 605

Schedule parameters . . . . . . . . . . . 605Scheduling commands to run by using classic orenhanced command schedules. . . . . . . 607

Copying schedules . . . . . . . . . . . 608Deleting schedules . . . . . . . . . . . 609Scheduled event records. . . . . . . . . . 609

Querying events . . . . . . . . . . . 609Removing event records from the database . . 610

Tivoli Storage Manager server scripts . . . . . 610Defining a server script . . . . . . . . . 611Managing server scripts . . . . . . . . . 615Running a server script . . . . . . . . . 619

Administrative client macros . . . . . . . . 619Writing commands in a macro. . . . . . . 620Writing comments in a macro . . . . . . . 621Including continuation characters in a macro 621Including substitution variables in a macro . . 622Running a macro . . . . . . . . . . . 622Command processing in a macro . . . . . . 623

Chapter 20. Managing the databaseand recovery log . . . . . . . . . . 625Database and recovery log overview . . . . . 625

Database: Overview . . . . . . . . . . 626Connecting the server to the database withTCP/IP . . . . . . . . . . . . . . 627Monitoring the database and recovery log . . . 628Recovery log management . . . . . . . . 630

Capacity planning . . . . . . . . . . . . 633Estimating database space requirements . . . 633Estimating recovery log space requirements . . 637Disk space requirements for the server databaseand recovery log . . . . . . . . . . . 650Monitoring space utilization for the databaseand recovery logs . . . . . . . . . . . 651

Increasing the size of the database . . . . . . 652Manually redistributing data and reclaimingspace after you add directories to the database . 655

Reducing the size of the database . . . . . . 656Reducing the size of the database for V7.1servers . . . . . . . . . . . . . . 657

viii IBM Tivoli Storage Manager for Linux: Administrator's Guide

|||||||||||||||||||||||||||

|||||

Reducing the size of the database for all otherservers . . . . . . . . . . . . . . 657

Table and index reorganization schedules . . . . 658Restrictions to table and index reorganization 659Scheduling table or index reorganization . . . 660Reorganizing tables offline . . . . . . . . 661Locating space to reorganize indexes and tablesoffline . . . . . . . . . . . . . . . 663

Managing logs for the database . . . . . . . 663Increasing the size of the active log . . . . . 663Reducing the size of the active log . . . . . 664Compressing archive logs . . . . . . . . 664Adding optional logs after server initialization 665Specifying alternative locations for database logfiles . . . . . . . . . . . . . . . 665

Moving the database and recovery log on a server 668Moving both the database and recovery log . . 668Moving only the database . . . . . . . . 669Moving only the active log, archive log, orarchive failover log . . . . . . . . . . 669

Transaction processing . . . . . . . . . . 670Files moved as a group between client andserver . . . . . . . . . . . . . . . 671

Chapter 21. Managing a network ofTivoli Storage Manager servers . . . 673Concepts for managing server networks . . . . 673

Enterprise configuration . . . . . . . . . 674Command routing. . . . . . . . . . . 675Central monitoring for the Tivoli StorageManager server. . . . . . . . . . . . 675Data storage on another server . . . . . . 676Examples: management of multiple TivoliStorage Manager servers . . . . . . . . 676

Enterprise-administration planning . . . . . . 678Setting up communications among servers . . . 678

Setting up communications for enterpriseconfiguration and enterprise event logging . . 678Setting up communications for commandrouting . . . . . . . . . . . . . . 682Updating and deleting servers. . . . . . . 686

Setting up enterprise configurations . . . . . . 687Enterprise configuration scenario . . . . . . 688Creating the default profile on a configurationmanager . . . . . . . . . . . . . . 692Creating and changing configuration profiles 693Getting information about profiles . . . . . 700Subscribing to a profile . . . . . . . . . 703

Refreshing configuration information . . . . . 707Managing problems with configuration refresh 708

Returning managed objects to local control . . . 708Setting up administrators for the servers . . . . 709Managing problems with synchronization ofprofiles . . . . . . . . . . . . . . . 709Switching a managed server to a differentconfiguration manager . . . . . . . . . . 710Deleting subscribers from a configuration manager 710Renaming a managed server . . . . . . . . 711Completing tasks on multiple servers . . . . . 711

Managing multiple servers from a web-basedinterface . . . . . . . . . . . . . . 711

Routing commands . . . . . . . . . . 712Setting up server groups . . . . . . . . 714Querying server availability . . . . . . . 718

Storing data on another server as virtual volumes 718Setting up source and target servers for virtualvolumes . . . . . . . . . . . . . . 720Performance limitations for virtual volumeoperations . . . . . . . . . . . . . 721Performing operations at the source server . . 722Reconciling virtual volumes and archive files 725

Chapter 22. Exporting and importingdata . . . . . . . . . . . . . . . 727Reviewing data that can be exported and imported 727

Exporting restrictions. . . . . . . . . . 728Deciding what information to export . . . . 728Deciding when to export . . . . . . . . 729

Exporting data directly to another server . . . . 730Options to consider before you export data . . 731Preparing to export to another server forimmediate import . . . . . . . . . . . 734Monitoring the server-to-server export process 736Exporting administrator information to anotherserver . . . . . . . . . . . . . . . 737Exporting client node information to anotherserver . . . . . . . . . . . . . . . 737Exporting policy information to another server 738Exporting server data to another server . . . 738

Exporting and importing data by using sequentialmedia volumes . . . . . . . . . . . . . 739

Previewing data export or import . . . . . 739Planning for sequential media used to exportdata . . . . . . . . . . . . . . . 740Exporting tasks. . . . . . . . . . . . 741Importing data from sequential media volumes 744Monitoring export and import processes . . . 755Exporting and importing data from virtualvolumes . . . . . . . . . . . . . . 759

Part 5. Monitoring operations . . . 761

Chapter 23. Daily monitoring from theOperations Center . . . . . . . . . 763

Chapter 24. Reporting and monitoringwith Tivoli Monitoring for TivoliStorage Manager . . . . . . . . . . 765Types of information to monitor with TivoliEnterprise Portal workspaces . . . . . . . . 766Monitoring operations daily with Tivoli Monitoringfor Tivoli Storage Manager . . . . . . . . . 770Monitoring Tivoli Storage Manager real-time data 772Viewing historical data and running reports . . . 773Cognos Business Intelligence . . . . . . . . 773

Cognos status and trend reports . . . . . . 774Create custom Cognos reports . . . . . . . 782Scheduling Cognos reports to be emailed . . . 782Sharing Cognos Reports . . . . . . . . . 783

Contents ix

|||

||||||||||||||||||

|||

||

||

Modifying the IBM Tivoli Monitoring environmentfile to customize agent data collection . . . . . 785

IBM Tivoli Monitoring reporting queries . . . 785Backing up and restoring Tivoli Monitoring forTivoli Storage Manager . . . . . . . . . . 788

Backing up Tivoli Monitoring for Tivoli StorageManager . . . . . . . . . . . . . . 789Restoring Tivoli Monitoring for Tivoli StorageManager . . . . . . . . . . . . . . 802

Chapter 25. Command-basedmonitoring methods . . . . . . . . 811Using IBM Tivoli Storage Manager queries todisplay information . . . . . . . . . . . 811

Requesting information about IBM TivoliStorage Manager definitions . . . . . . . 811Requesting information about client sessions 812Requesting information about server processes 813Requesting information about server settings 814Querying server options . . . . . . . . . 814

Using SQL to query the IBM Tivoli StorageManager database . . . . . . . . . . . . 815

Using SELECT commands . . . . . . . . 815Using SELECT commands in Tivoli StorageManager scripts . . . . . . . . . . . 818Querying the SQL activity summary table . . . 819Creating output for use by another application 820

Using the Tivoli Storage Manager activity log . . 820Requesting information from the activity log 821Setting a retention period for the activity log 822Setting a size limit for the activity log . . . . 822

Monitoring Tivoli Storage Manager accountingrecords . . . . . . . . . . . . . . . 823Logging IBM Tivoli Storage Manager events toreceivers . . . . . . . . . . . . . . . 824

Enabling and disabling events . . . . . . . 825Beginning and ending event logging . . . . 826Logging events to the IBM Tivoli StorageManager server console and activity log . . . 826Logging events to a file exit and a user exit . . 827Logging events to the Tivoli Enterprise Console 828Logging events to an SNMP manager . . . . 832Enterprise event logging: logging events toanother server . . . . . . . . . . . . 838Querying event logging . . . . . . . . . 839User exit and file exit receivers . . . . . . 840

Part 6. Protecting the server . . . 845

Chapter 26. Managing Tivoli StorageManager security . . . . . . . . . . 847Securing communications . . . . . . . . . 847

Secure Sockets Layer and Transport LayerSecurity communication . . . . . . . . . 848Administrative authority and privilege classes 849Setting up Secure Sockets Layer and TransportLayer Security . . . . . . . . . . . . 851

Securing the server console . . . . . . . . . 861Managing access to the server and clients . . . . 862

Managing Tivoli Storage Manager administratorIDs . . . . . . . . . . . . . . . . 862Restricting a non-root user ID from completingbackups as root. . . . . . . . . . . . 868

Managing passwords and logon procedures . . . 869Configuring a directory server for passwordauthentication . . . . . . . . . . . . 871Setting the policy for an LDAP-authenticatedpassword. . . . . . . . . . . . . . 873Configuring the Tivoli Storage Manager serverto authenticate passwords with an LDAPdirectory server . . . . . . . . . . . 874Registering nodes and administrator IDs toauthenticate passwords with an LDAP directoryserver . . . . . . . . . . . . . . . 875Updating nodes and administrator IDs toauthenticate passwords with a directory server . 876Determining which nodes and administrator IDsare configured to authenticate with an LDAPserver . . . . . . . . . . . . . . . 877Modifying the default password expirationperiod for passwords that are managed by theTivoli Storage Manager server . . . . . . . 877Scenarios for authenticating passwords . . . . 880

Chapter 27. Protecting and recoveringthe server infrastructure and clientdata . . . . . . . . . . . . . . . 883Protecting the database and infrastructure setupfiles . . . . . . . . . . . . . . . . 883

Backing up the server database . . . . . . 884Protecting infrastructure setup files . . . . . 892

Client data protection . . . . . . . . . . 897Protecting the data that is in primary storagepools . . . . . . . . . . . . . . . 897Auditing storage pool volumes . . . . . . 902Fixing damaged files . . . . . . . . . . 911

Scenario: Protecting the database and storage pools 913Recovering the database and client data . . . . 915

Restoring the database . . . . . . . . . 916Restoring storage pools and storage poolvolumes . . . . . . . . . . . . . . 922Restoring and recovering an LDAP server . . . 929Audit the LDAP server . . . . . . . . . 930

Restoring to a point-in-time in a shared libraryenvironment. . . . . . . . . . . . . . 931

Restoring to a point-in-time for a librarymanager server . . . . . . . . . . . . 931Restoring to a point-in-time of a library clientserver . . . . . . . . . . . . . . . 931Example: Recovering to a point-in-time. . . . 932

Chapter 28. Replication of client nodedata . . . . . . . . . . . . . . . 935Automatic failover for data recovery overview . . 936Source and target node-replication servers. . . . 937

Replication server configurations . . . . . . 937Policy management for node replication . . . 939Node replication processing . . . . . . . 940

Planning for node replication . . . . . . . . 951

x IBM Tivoli Storage Manager for Linux: Administrator's Guide

Determining server database requirements fornode replication . . . . . . . . . . . 952Estimating the total amount of data to bereplicated. . . . . . . . . . . . . . 953Estimating network bandwidth required forreplication . . . . . . . . . . . . . 954Calculating the time that is required forreplication . . . . . . . . . . . . . 954Selecting a method for the initial replication . . 955Scheduling incremental replication after theinitial replication . . . . . . . . . . . 957

Node replication restrictions . . . . . . . . 958Task tips for node replication . . . . . . . . 961

Change replication rules. . . . . . . . . 961Add and remove client nodes for replication 961Manage replication servers . . . . . . . . 962Validate a configuration and preview results 963Manage replication processing. . . . . . . 963Monitor replication processing and verify results 964

Setting up the default replication configuration . . 965Step 1: Setting up server-to-servercommunications . . . . . . . . . . . 966Step 2: Specifying a target replication server . . 969Step 3: Configuring client nodes for replication 970

Customizing a node replication configuration . . 972Changing replication rules . . . . . . . . 972Scenario: Converting to node replication fromimport and export operations . . . . . . . 978Adding and removing client nodes forreplication . . . . . . . . . . . . . 979Managing source and target replication servers 982

Verifying a node replication setup beforeprocessing . . . . . . . . . . . . . . 985Managing data replication . . . . . . . . . 986

Replicating data by command . . . . . . . 986Controlling throughput for node replication . . 991Disabling and enabling node replication . . . 994Managing replicated client-node data using thetarget replication server policies . . . . . . 998Purging replicated data in a file space . . . . 1001Replicating client node data after a databaserestore . . . . . . . . . . . . . . 1001

Monitoring node replication processing andverifying results . . . . . . . . . . . . 1003

Displaying information about node replicationsettings . . . . . . . . . . . . . . 1003Displaying information about running andcompleted node replication processes . . . . 1004Displaying the activity log of a replicationprocess . . . . . . . . . . . . . . 1004Displaying summary records of replicationprocesses . . . . . . . . . . . . . 1005Measuring the effectiveness of a replicationconfiguration . . . . . . . . . . . . 1005Measuring the effects of data deduplication onnode replication processing . . . . . . . 1005Retaining replication records . . . . . . . 1006

Recovering and storing client data after a disaster 1007Converting client nodes for store operations ona target replication server . . . . . . . . 1007

Removing a node replication configuration . . . 1008

Chapter 29. Configuring clusteredenvironments . . . . . . . . . . . 1009Clustered environment overview . . . . . . 1009

Cluster nodes . . . . . . . . . . . . 1010Configuring a Linux environment for clustering 1010

Overview of a two-node Tivoli StorageManager cluster using Tivoli SystemAutomation . . . . . . . . . . . . 1010Setting up a Tivoli Storage Manager clusterwith Tivoli System Automation . . . . . . 1015Prerequisites to configuring a Linux clusteredenvironment with Tivoli System Automation . 1016Installing and configuring Tivoli StorageManager components on the primary andsecondary nodes . . . . . . . . . . . 1016Installing Tivoli System Automation on theprimary and secondary nodes . . . . . . 1019Configuring storage resources . . . . . . 1023Upgrading the Tivoli Storage Manager serverthat is configured with Tivoli SystemAutomation . . . . . . . . . . . . 1024

Chapter 30. Disaster recoverymanager . . . . . . . . . . . . . 1027Preparing for disaster recovery . . . . . . . 1028Disaster recovery manager checklist . . . . . 1030Managing the Disaster Recovery Manager tasks 1035The disaster recovery plan file . . . . . . . 1037

Breaking out a disaster recovery plan file. . . 1037Structure of the disaster recovery plan file . . 1037Example disaster recovery plan file. . . . . 1039

Querying defaults for the disaster recovery planfile . . . . . . . . . . . . . . . . 1056

Specifying defaults for the disaster recoveryplan file . . . . . . . . . . . . . . 1056Specifying defaults for offsite recovery mediamanagement . . . . . . . . . . . . 1060

Specifying recovery instructions for your site . . 1062Specifying information about your server andclient node machines . . . . . . . . . . 1064Specifying recovery media for client machines 1066Creating and storing the disaster recovery plan 1067

Storing the disaster recovery plan locally . . . 1068Storing the disaster recovery plan on a targetserver . . . . . . . . . . . . . . 1069

Managing disaster recovery plan files stored ontarget servers . . . . . . . . . . . . . 1069

Displaying information about recovery planfiles . . . . . . . . . . . . . . . 1069Displaying the contents of a recovery plan file 1070Restoring a recovery plan file . . . . . . 1070Expiring recovery plan files automatically . . 1071Deleting recovery plan files manually . . . . 1071

Moving backup media for disaster recoveryoperations . . . . . . . . . . . . . . 1072

Moving copy storage pool and active-data poolvolumes offsite . . . . . . . . . . . 1074Moving copy storage pool and active-data poolvolumes onsite . . . . . . . . . . . 1076

Recovering from a disaster . . . . . . . . 1077

Contents xi

|||

Recovering the server scenario . . . . . . 1078Recovering the client scenario . . . . . . 1081

Recovering with different hardware at therecovery site . . . . . . . . . . . . . 1084

Automated SCSI library at the original andrecovery sites . . . . . . . . . . . . 1084Automated SCSI library at the original site anda manual SCSI library at the recovery site . . 1085Managing copy storage pool volumes andactive-data pool volumes at the recovery site . 1086

Chapter 31. Integrating disasterrecovery manager and nodereplication into your disasterrecovery strategy . . . . . . . . . 1089Plan for a disaster recovery strategy . . . . . 1090Tier 0: No disaster recovery capability. . . . . 1091Tier 1: Offsite vaulting from a single productionsite . . . . . . . . . . . . . . . . 1091Tier 2: Offsite vaulting with a recovery site . . . 1092Tier 3: Electronic vaulting of critical data . . . . 1092Tier 4: Active data management at peer sites . . 1093Tier 5: Synchronous replication . . . . . . . 1094Tier 6: Synchronous replication with coupling orclustering applications . . . . . . . . . . 1095

Part 7. Appendixes . . . . . . . 1097

Appendix A. External mediamanagement interface description . . 1099CreateProcess call . . . . . . . . . . . 1099

Processing during server initialization . . . . . 1100Processing for mount requests . . . . . . . 1100Processing for release requests . . . . . . . 1101Processing for batch requests . . . . . . . . 1101Error handling . . . . . . . . . . . . 1102Begin batch request . . . . . . . . . . . 1102End batch request . . . . . . . . . . . 1102Volume query request . . . . . . . . . . 1103Initialization requests . . . . . . . . . . 1104Volume eject request. . . . . . . . . . . 1104Volume release request . . . . . . . . . . 1105Volume mount request . . . . . . . . . . 1106Volume dismount request . . . . . . . . . 1109

Appendix B. User exit and file exitreceivers . . . . . . . . . . . . . 1111Sample user exit declarations . . . . . . . . 1111Sample user-exit program . . . . . . . . . 1113Readable text file exit (FILETEXTEXIT) format 1114

Appendix C. Accessibility featuresfor the Tivoli Storage Managerproduct family . . . . . . . . . . 1117

Notices . . . . . . . . . . . . . 1119Trademarks. . . . . . . . . . . . . . 1121Privacy policy considerations . . . . . . . . 1121

Glossary . . . . . . . . . . . . . 1123

Index . . . . . . . . . . . . . . 1125

xii IBM Tivoli Storage Manager for Linux: Administrator's Guide

About this publication

IBM® Tivoli® Storage Manager is a client/server program that provides storagemanagement solutions to customers in a multi-vendor computer environment.Tivoli Storage Manager provides an automated, centrally scheduled,policy-managed backup, archive, and space-management facility for file serversand workstations.

This publication provides concept information about Tivoli Storage Manager, inaddition to chapters that help you configure, administer, use, and monitor theTivoli Storage Manager server environment.

Who should read this guideThis guide is intended for anyone who is registered as an administrator for TivoliStorage Manager. A single administrator can manage Tivoli Storage Manager, orseveral people can share administrative responsibilities.

You should be familiar with the operating system on which the server resides andthe communication protocols required for the client/server environment. You alsoneed to understand the storage management practices of your organization, suchas how you are currently backing up workstation files and how you are usingstorage devices.

PublicationsThe Tivoli Storage Manager product family includes IBM Tivoli StorageFlashCopy® Manager, IBM Tivoli Storage Manager for Space Management, IBMTivoli Storage Manager for Databases, and several other storage managementproducts from IBM Tivoli.

To view IBM product documentation, see http://www.ibm.com/support/knowledgecenter/.

Conventions used in this guidev Command to be entered on the Linux command line:

> dsmadmc

v Command to be entered on the command line of an administrative client:query devclass

In the usage and descriptions for administrative commands, the term characterscorresponds to the number of bytes available to store an item. For languages inwhich it takes a single byte to represent a displayable character, the character tobyte ratio is 1 to 1. However, for DBCS and other multi-byte languages, thereference to characters refers only to the number of bytes available for the item andmay represent fewer actual characters.

© Copyright IBM Corp. 1993, 2014 xiii

http://www.ibm.com/support/knowledgecenter/http://www.ibm.com/support/knowledgecenter/

xiv IBM Tivoli Storage Manager for Linux: Administrator's Guide

New for IBM Tivoli Storage Manager Version 7.1

Many features in the Tivoli Storage Manager Version 7.1 server are new forprevious Tivoli Storage Manager users.

New in this releaseNew features and other changes, including fixes for problems, are available in theTivoli Storage Manager Version 7.1.1 server.

Operations Center updatesNew features are available in Tivoli Storage Manager Operations Center Version7.1.1.

The following enhancements were made to the Operations Center for Version 7.1.1:

Navigation, customization, and reporting

You can now complete the following tasks:v Use improved linking to navigate between pages of the Operations

Center more easilyv Use advanced filters to construct custom views of table datav Bookmark and use shared links to commonly accessed web pagesv Customize the Operations Center login page to include text that you

providev Configure daily email reports on client coverage and server statusv If you have a Tivoli Storage Manager Suite for Unified Recovery license,

compare the amount of data you are managing with what yourentitlement allows

Alerts You can now complete the following tasks from the Alerts page:v Add an alert by specifying the message that triggers the alertv Select which administrators receive email notifications for an alertv Change the category for an alertv Delete an alert definition for a message, so the message no longer

triggers an alert

ClientsYou can now complete the following tasks from the Clients page:v View client schedulesv Add client schedulesv Modify client schedulesClient details now include diagnosis information. Use the Diagnosis pageto view client errors and recommendations for how to resolve them. Youcan also view client log messages to help you diagnose problems withoutaccessing the client system.

ServicesYou can now view the following policy domain details on the Servicespage:

© Copyright IBM Corp. 1993, 2014 xv

v Properties of the policy domain, such as the default management classand the retention grace period

v The files and related objects that were examined and expired over theprevious two weeks

v The active policy set for the policy domainServers

You can now view maintenance schedules from the Servers page.

Storage PoolsYou can now complete the following tasks from the Storage Pools page:v Manually migrate storage pool datav Manually reclaim storage pool spacev View the following storage pool details:

– Properties of the storage pool, such as the device class and utilization– The storage pool capacity that was used over the previous two weeks– Volumes that are assigned to the storage pool

v Edit certain storage pool properties

For more information about these enhancements, see the Operations Center help.

To open the help, hover over the help icon ? in the Operations Center menubar.

Tivoli Monitoring for Tivoli Storage Manager updatesTivoli Monitoring for Tivoli Storage Manager Version 7.1 includes updatedcomponents and a new dashboard to view Cognos® reports.

IBM Tivoli Monitoring for Tivoli Storage Manager includes the following changesin version 7.1:v You can use the Dashboard Application Services Hub web interface to access

Tivoli Common Reporting.v New Cognos reports are available:

– Storage pool deduplication savings– Disk utilization trends

v The existing BIRT reports that were available in previous releases are availableas Cognos reports.

v You can now restrict communications to use the Transport Layer Security (TLS)1.2 protocol. For your system to be in compliance with the NIST SP800-131Asecurity standard, you must specify KSK_SSL_DISABLE_LEGACY_TLS=1 in the agentinstance environment file.

Related reference:“Cognos status and trend reports” on page 774

xvi IBM Tivoli Storage Manager for Linux: Administrator's Guide

Updates for the Tivoli Storage Manager server componentNew features are available in the Tivoli Storage Manager Version 7.1.1 servercomponent.

Recover damaged files from a replication serverWith Tivoli Storage Manager Version 7.1.1, you can use node replication processingto recover damaged files. When this feature is enabled, the system detects anydamaged files on a source replication server and replaces them with undamagedfiles from a target replication server.

You can enable this feature for specific client nodes. When you use the REGISTERNODE command to define a node, or the UPDATE NODE command to update a node,you can specify whether data from damaged files is recovered automaticallyduring the replication process.

In addition to configuring nodes for file recovery, you can override the filerecovery setting that is specified for a node. By specifying a parameter on theREPLICATE NODE command for a single replication instance, you can start a processthat replicates the node and recovers damaged files. Alternatively, you can start areplication process for the sole purpose of recovering damaged files.

To use this feature, you must install Tivoli Storage Manager V7.1.1 on the sourceand target replication servers, and ensure that file recovery is enabled.Related tasks:“Recovering damaged files from a replication server” on page 912

Manage replicated data with policies that are defined on thetarget replication serverWith Tivoli Storage Manager Version 7.1.1, you can use the policies that aredefined on the target replication server to manage replicated client-node dataindependently from the source replication server. In previous releases, client nodedata on the target replication server was managed by policies on the sourcereplication server.

When this feature is enabled, you can use the policies on the target replicationserver to complete the following tasks:v Maintain more or fewer versions of replicated backup files between the source

and target replication servers.v Retain replicated archive files for more or less time on the target replication

server than they are being maintained on the source replication server.

If you keep fewer versions of files or retain files for less time on the targetreplication server, you can reduce the amount of storage that is required for thisserver.

To use this feature, you must install Tivoli Storage Manager V7.1.1 on the sourceand target replication servers. Then, you must verify the differences between thepolicies for client nodes on the source and target replication servers. Finally, youcan enable the policies on the target replication server.Related tasks:“Enabling the target replication server policies” on page 1000

New for IBM Tivoli Storage Manager Version 7.1 xvii

Restrict SSL protocols to TLS 1.2 or laterWith Tivoli Storage Manager Version 7.1.1, you can prevent the use of SecureSockets Layer (SSL) protocols earlier than TLS 1.2 with the new server option,SSLDISABLELEGACYTLS.

The SSLDISABLELEGACYTLS option specifies whether to use protocols earlier thanTransport Layer Security (TLS) 1.2 for Secure Sockets Layer (SSL) sessions betweenthe server and the backup-archive client or storage agent.

Use offline reorganization of tables and indexesWith Tivoli Storage Manager Version 7.1.1, you can reorganize indexes and tablesoffline to maintain server stability and improve database performance. To enablethis feature, set the DISABLEREORGTABLE, DISABLEREORGINDEX, andDISABLEREORGCLEANUPINDEX server options.

You can specify these server options in the dsmserv.opt file to resolve thefollowing issues:v Delays when you reorganize tables, which prevents reorganization on other

tables.v Server that halts because the active log becomes full during index

reorganization.v Server applications cancel when you use reorganization to resolve deadlocks.

Compress archive logsWith Tivoli Storage Manager Version 7.1.1, you can enable or disable compressionof the archive log files that are written to the archive log directory. By compressingthe archive log files, you reduce the amount of space that is required to store them.

To enable or disable compression of the archive log files, set the ARCHLOGCOMPRESSserver option in the dsmserv.opt file.Related tasks:“Compressing archive logs” on page 664

Compress database backupsWith Tivoli Storage Manager Version 7.1.1, you can choose which Tivoli StorageManager database backups are compressed.

To enable this feature, specify the COMPRESS parameter on the BACKUP DB or SETDBRECOVERY commands.

The size of the Tivoli Storage Manager database has increased with the use of datadeduplication. As a result, the space requirements for the database backups alsoincreased. By compressing volumes that are created during database backups, youreduce the amount of space that is required for your database backups.

xviii IBM Tivoli Storage Manager for Linux: Administrator's Guide

Verify tape volumesYou can now audit any volume in a tape library by using the AUDIT LIBVOLUMEcommand, which is available in Tivoli Storage Manager Version 7.1.1 for somelibrary types and tape drives. When this command is issued, an entire physicaltape volume is audited instead of just a storage pool volume.

With the AUDIT LIBVOLUME command, you can determine if a volume is intact. Theverification process is completed by the tape drive. If errors are detected, you canuse the AUDIT VOLUME command to fix storage pool volumes on the tape.

For information about supported library types and drives, and details on using theAUDIT LIBVOLUME command, see the server reference information.

Validate pages during database backup processingTivoli Storage Manager Version 7.1.1 uses IBM DB2® database technology tovalidate database pages during database backup processing.

Best practices for Version 7.1Learn about best practices that you can implement for the Tivoli Storage ManagerVersion 7.1 server and client.

Maximum daily capability for data deduplicationYou can deduplicate data for a single Tivoli Storage Manager server up to arecommended daily maximum amount of 30 TB, or the amount that is outlined foryour blueprint configuration.

The maximum daily amount includes the following processes that are typical of adaily server cycle:v Ingesting client data on the serverv Deduplicating the client data that is ingested on the serverv Creating a second copy of the datav Reclaiming datav Expiring datav Removing references to extents

You can deduplicate the maximum daily amount of data by using client-side datadeduplication with optimized hardware, such as Solid-State Drives for thedatabase, and overlapping of some server processes during a 24-hour workload.

Server startup and setting ulimitsBefore you start the Tivoli Storage Manager server, verify access rights and userlimits, also known as ulimits.

If you do not verify user limits, the server might become unstable or fail torespond. Set the ulimit value as 65536 for the maximum number of open files.Ensure that the system-wide limit is at least the value of the ulimit.

New for IBM Tivoli Storage Manager Version 7.1 xix

|

|||

||

|

|

|

|

|

|

|||

Duplicate identification processes and memory requirementsTo get the best performance for your data deduplication processes, you can specifyan increased number of duplicate identification processes.

When you create a storage pool for data deduplication, you can now specify 0 - 50parallel processes for server-side duplicate identification.

You can use additional memory to optimize the frequent access of deduplicateextent information that is stored in the Tivoli Storage Manager database.

Configuring the server to prevent issues with databasebackups

With Tivoli Storage Manager Version 7.1, it is no longer necessary to set the APIpassword when you manually configure the server. If you set the API passwordduring the manual configuration process, attempts to back up the database mightfail.

xx IBM Tivoli Storage Manager for Linux: Administrator's Guide

Part 1. Tivoli Storage Manager basics

© Copyright IBM Corp. 1993, 2014 1

2 IBM Tivoli Storage Manager for Linux: Administrator's Guide

Chapter 1. Tivoli Storage Manager overview

IBM Tivoli Storage Manager provides centralized, automated data protection thatcan help reduce the risks that are associated with data loss and help managecompliance with data retention and availability requirements.

Tivoli Storage Manager components are shown in Figure 1 and explained in detail,following the image.

Server

The Tivoli Storage Manager server stores client data to storage media. The serverincludes an inventory in which Tivoli Storage Manager stores information aboutthe client data that it is protecting.

Administrative interfaces for the server include a web-based interface that is calledthe Operations Center and a command-line administrative client. The TivoliStorage Manager server inventory includes the following components, which canbe monitored from the Operations Center:

DatabaseTivoli Storage Manager saves information about each file, logical volume,or database that it backs up, archives, or migrates. This inventory data isstored in the server database. The server database also includesinformation about the policy and schedules for data protection services.Client data is stored in a storage pool.

Recovery logThe recovery log consists of the active and archive logs, and other optionallogs. These logs are records of database transactions, which can be used fordatabase recovery. If a failure occurs, such as a power outage or

ClientsInventory Database and recovery log

Tivoli Storage Manager server

Server storage

Command-lineadministrative

client

OperationsCenter

Server

Administrative interfaces

Applications, virtual machines, systems

Storage pools

Figure 1. Components of the Tivoli Storage Manager environment

© Copyright IBM Corp. 1993, 2014 3

application error, the changes that were made but not committed are rolledback. Then, all committed transactions, which might not yet be written todisk, are redone.

Active logThe active log is a record of the most recent database transactionsthat are not yet committed.

Archive logThe archive log is a record of the most recent database transactionsthat are committed but not yet included in a database backup.

Storage

The Tivoli Storage Manager server can write data to hard disk drives, disk arraysand subsystems, stand-alone tape drives, tape libraries, and other forms ofrandom-access and sequential-access storage. The media that the server uses aregrouped into storage pools.

Storage devices can be connected directly to the server, or connected through alocal area network (LAN) or a storage area network (SAN).

Storage poolsStorage pools are a central Tivoli Storage Manager concept. Understandingthem is key to effectively managing your Tivoli Storage Manager serverenvironment. Storage pools connect the Tivoli Storage Manager policyhierarchy to the storage devices where client data is stored. A storage poolrepresents a set of volumes of the same media type, for example, disk ortape volumes.

Tivoli Storage Manager stores all managed data objects in storage pools.You can organize storage pools into one or more hierarchical structures,and each storage hierarchy can span multiple Tivoli Storage Managerserver instances.

To obtain the best value from your storage investment, you must store dataappropriately in the storage pool hierarchy. A disk pool is often first in thehierarchy and can be followed by a tape pool. Tivoli Storage Managersupports many device and media types for sequential access storage.

Clients

Tivoli Storage Manager clients or client nodes protect data by sending it to a TivoliStorage Manager server. Client software must be installed on the client system, andthe client must be registered with the server.

A client node is usually equivalent to a computer, such as a backup-archive clientthat is installed on a workstation for file system backups. A file space is a group ofclient files that are stored as a logical unit in server storage.

Multiple nodes can be installed on a single computer, as in the case of a MicrosoftSQL server that contains both an application client for SQL database backups and abackup-archive client for file system backups.

You can define the following clients for use with Tivoli Storage Manager:


ApplicationsThe following clients are application clients. Data that is being protectedfor these clients is structured data that requires interaction with backupinterfaces specific to the application:v Tivoli Storage Manager for Enterprise Resource Planningv Tivoli Storage FlashCopy Managerv Tivoli Storage Manager for Databasesv Tivoli Storage Manager for Mailv Tivoli Storage Manager for Virtual Environments

This excludes VMware vSphere clients, which are classified as systemclients.

A virtual machine that is backed up using application client software thatis installed on the virtual machine is also classified as an application client.

Virtual machinesA virtual machine is an individual guest that is hosted within a hypervisor.Each virtual machine is represented as a Tivoli Storage Manager file space.Backups for multiple virtual machines are consolidated together under acommon node. Each virtual machine is stored under a separate file spacefor this common node.

A client is considered a virtual machine when it is protected by either DataProtection for VMware or Data Protection for Microsoft Hyper-V.

SystemsAll other clients, for example, backup-archive and API clients, are classifiedas system clients. These clients back up unstructured data that is containedwithin files and directories.

System clients also include the following items:v A Tivoli Storage Manager source server in a server-to-server virtual

volume configurationv A virtual machine that is backed up using backup-archive client software

that is installed on the virtual machineRelated concepts:Chapter 2, “Tivoli Storage Manager server concepts,” on page 21

Data protection servicesTivoli Storage Manager provides the following data protection services: backupand restore, archive and retrieve, and migrate and recall. These data protectionservices are implemented through policy domains that are defined on the TivoliStorage Manager server.

Backup and restore

A backup creates an extra copy of a data object that can be used for recovery if theoriginal copy is lost or destroyed. A data object can be a file, a directory, or auser-defined data object, such as a database table.

Tivoli Storage Manager uses a progressive incremental backup method. After a firstfull backup, only changed data is moved. This method provides the followingbenefits:v Reduces data redundancy

Chapter 1. Tivoli Storage Manager overview 5

v Uses less network bandwidthv Requires less storage pool spaceTo further reduce storage capacity requirements, Tivoli Storage Manager includesserver-side data deduplication. To reduce network bandwidth, client-side datadeduplication is also available.

Tivoli Storage Manager also works with storage hardware to use other datareduction techniques such as subfile backup, client compression, and devicecompression.

When you restore an object, you copy it back from the server to the client. You canrestore a file, a directory, or all data on a computer.

Archive and retrieve

The archive and retrieve service is for data that must be stored for a long time,such as for regulatory compliance. You might choose to store this data on a tapedevice, which often provides cheaper storage.

Archiving a file copies it and stores it for a specified time to preserve the data forlater use or for records. You can request that files and directories be copied forlong-term storage on media that is controlled by Tivoli Storage Manager. You canalso specify that the original files be erased from the client after the files arearchived.

Retrieving a file copies it from a storage pool to a client node. The retrieveoperation does not affect the archive copy in the storage pool.

Migrate and recall

The migration and recall service is for space management on client systems. Youmight choose to store this data in a VTL so that files can be quickly recalled whenthey are needed.

Space management is the process of maintaining sufficient free storage space on alocal file system by migrating files to server storage. The files can then be recalledto the client node on demand, either automatically or selectively. The goal of spacemanagement is to maximize available media capacity for new data and tominimize access time to data.Related concepts:Chapter 13, “Implementing policies for client data,” on page 471Related tasks:“Policy-based data management” on page 36


Data protection operationsTivoli Storage Manager provides different backup, archive, and restore operations,that allow you to select the right protection for the situation.

Table 1 provides details about backup and archive protection options and how theycan help you meet goals for data management.

Table 1. Examples of meeting your goals with Tivoli Storage Manager

For this goal... Complete this task...

Back up files that are on a user's workstation. Use the backup-archive client to performincremental or selective backups.

Back up data for an application that runscontinuously, such as a database application(for example, DB2 or Oracle) or a mailapplication, such as Lotus® Domino®.

Use the appropriate application client. Forexample, use Tivoli Storage Manager for Mailto protect the LotusDomino application.

Protect virtual machines that are runningVMware or Microsoft Hyper-V.

Use Tivoli Storage Manager for VirtualEnvironments: Data Protection for VMwareor Tivoli Storage Manager for VirtualEnvironments: Data Protection for MicrosoftHyper-V.

Use disk hardware that is capable of datasnapshots.

Use the appropriate component in the IBMTivoli Storage FlashCopy Manager product,such as System Storage® Archive Manager forIBM Enterprise Storage Server® for DB2.

Back up a file server. Use the backup-archive client to performincremental backups or selective backups.

If the file server is a network-attachedstorage file server that is supported, you canhave the server use NDMP to perform imagebackups. This support is available in theTivoli Storage Manager Extended Editionproduct.

Make restore media portable, or makerestores easier to perform remotely.

Use the backup-archive client to performincremental backups, and then generatebackup sets by using the Tivoli StorageManager server. A backup set is a collectionof backed-up data from one client, which isstored and managed as a single object onspecific media in server storage

Back up the entire contents of a single logicalvolume, instead of backing up individualfiles.

Use the backup-archive client to performlogical volume backups (also called imagebackups).

Set up records retention to meet legal orother long-term storage needs.

Use the backup-archive client to occasionallyarchive data. To ensure that the archivingoccurs at the required intervals, use centralscheduling.

Create an archive for a backup-archive client,from data that is already stored for backup.

Use the backup-archive client to performincremental backups, and then generate abackup set by using the Tivoli StorageManager server.Tip: This process is also called instant archive.


Table 1. Examples of meeting your goals with Tivoli Storage Manager (continued)

For this goal... Complete this task...

Restore data to a point in time. Use the backup-archive client to regularlyperform incremental backups, eithermanually or automatically throughschedules. Then do one of the following:

v Set up policy to ensure that data ispreserved in server storage long enough toprovide the required service level.

v Create backup sets for the backup-archiveclient regularly. Set the retention time toprovide the required service level.

Save a set of files and directories before youmake significant changes to them.

Use the backup-archive client to archive theset of files and directories.

If this kind of protection is needed regularly,consider creating backup sets from backupdata that is already stored for the client.Using backup sets instead of frequent archiveoperations can reduce the amount ofmetadata that must be stored in the serverdatabase.

Manage a set of related files, which are notin the same file system, with the samebackup, restore, and server policies.

Use the backup group command on thebackup-archive client to create a logicalgrouping of a set of files, which can be fromone or more physical file systems. The groupbackup process creates a virtual file space inserver storage to manage the files becausethe files might not be from one file systemon the client. Actions such as policy binding,migration, expiration, and export are appliedto the group as a whole.

See the Backup-Archive Clients Installation andUser's Guide for details.

Make backups that are not apparent to users. Use the backup-archive client with centrallyscheduled backups that run during off-shifthours. Monitor the schedule results.

Reduce the load on the LAN by movingbackup data over the SAN.

Use LAN-free data movement or, forsupported network-attached storage (NAS)file servers, use NDMP operations.

Schedule the backups of client data to help enforce the data management policythat you establish. If you schedule the backups, rather than rely on the clients toperform the backups, the policy that you establish is followed more consistently.

The standard backup method that Tivoli Storage Manager uses is called progressiveincremental backup. It is a unique and efficient method for backup.

Table 2 on page 9 summarizes the client operations that are available. In all cases,the server tracks the location of the backup data in its database. Policy that you setdetermines how the backup data is managed.


Table 2. Summary of client operations

Description Usage Restore options For moreinformation

Progressiveincrementalbackup

The standard method ofbackup that is used byTivoli Storage Manager.After the first, fullbackup of a clientsystem, incrementalbackups are done.Incremental backup bydate is also available.

No additional fullbackups of a client arerequired after the firstbackup.

Helps ensure complete,effective, policy-basedbackup of data. Eliminatesthe need to retransmitbackup data that does notchange during successivebackup operations.

The user can restore justthe version of the file thatis needed.

Tivoli Storage Managerdoes not need to restore abase file followed byincremental backups. Thismethod reduces time andrequires fewer tapemounts. Also, less data istransmitted over thenetwork.

See “Incrementalbackup” on page475.

Selectivebackup

Backup of files that areselected by the user,regardless of whether thefiles have changed sincethe last backup.

Allows users to protect asubset of their dataindependent of thenormal incrementalbackup process.

The user can restore justthe version of the file thatis needed.

Tivoli Storage Managerdoes not need to restore abase file followed byincremental backups. Thismethod reduces time andrequires fewer tapemounts. Also, less data istransmitted over thenetwork.

See “Selectivebackup” on page477.

Adaptivesubfilebackup

A backup method thatbacks up only the partsof a file that havechanged since the lastbackup. The server storesthe base file (thecomplete initial backupof the file) andsubsequent subfiles (thechanged parts) thatdepend on the base file.

The process works witheither the standardprogressive incrementalbackup or with selectivebackup.

Applicable to clients onWindows systems.

Maintains backups of datawhile minimizing connecttime and datatransmission for thebackup of mobile andremote users.

The base file plus amaximum of one subfileis restored to the client.

See “Enabling clientsto use subfilebackup” on page530.


Table 2. Summary of client operations (continued)


Journal-basedbackup

Aids all types of backups(progressive incrementalbackup, selective backup,adaptive subfile backup)by basing the backups ona list of changed files.The list is maintained onthe client by the journalengine service of IBMTivoli Storage Manager.

Reduces the amount oftime that is required forbackup. The files eligiblefor backup are knownbefore the backupoperation begins.

Applicable to clients onAIX®, Linux, andWindows systems, exceptWindows 2003 64-bitIA64.

Journal-based backup hasno effect on how files arerestored. Restoreoperations are dependenton the type of backup thatis performed.

See theBackup-ArchiveClients Installationand User's Guide.

Imagebackup

Full volume backup.

Nondisruptive, onlinebackup is possible forWindows clients by usingthe Tivoli StorageManager snapshotfunction.

Allows backup of anentire file system or rawvolume as a single object.Can be selected bybackup-archive clients onLinux, UNIX, andWindows systems.

The entire image isrestored.

See “Policy forlogical volumebackups” on page497.

Imagebackupwithdifferentialbackups

Full volume backup,which can be followed bysubsequent differentialbackups.

Used only for the imagebackups of NAS fileservers, performed by theserver using NDMPoperations.

The full image backupplus a maximum of onedifferential backup arerestored.

See Chapter 9,“Using NDMP foroperations with NASfile servers,” on page209.

Backupusinghardwaresnapshotcapabilities

A method of backup thatuses the capabilities ofIBM Enterprise StorageServer FlashCopy andEMC TimeFinder to makecopies of volumes thatare used by databaseservers. The TivoliStorage FlashCopyManager product thenuses the volume copies toback up the databasevolumes.

Implementshigh-efficiency backupand recovery ofbusiness-criticalapplications whilevirtually eliminatingbackup-related downtimeor user disruption on thedatabase server.

Details depend on thehardware.

See thedocumentation forTivoli StorageFlashCopy Managerathttp://www.ibm.com/support/knowledgecenter/SS36V9.

Groupbackup

A method that backs upfiles that you specify as anamed group. The filescan be from one or morefile spaces. The backupcan be a full or adifferential backup.

Applicable to clients onand Linux, UNIX, andWindows systems.

Creates a consistentpoint-in-time backup of agroup of related files. Thefiles can be in differentfile spaces on the client.All objects in the groupare assigned to the samemanagement class. Theserver manages the groupas a single logical entity,and stores the files in avirtual file space in serverstorage.

A group can be includedin a backup set.

The user can select torestore the entire group orselected members of thegroup. The user canrestore just the version ofthe file that is needed.

See theBackup-ArchiveClients Installationand User's Guide.


http://www.ibm.com/support/knowledgecenter/SS36V9http://www.ibm.com/support/knowledgecenter/SS36V9http://www.ibm.com/support/knowledgecenter/SS36V9http://www.ibm.com/support/knowledgecenter/SS36V9http://www.ibm.com/support/knowledgecenter/SS36V9

Table 2. Summary of client operations (continued)


Archive The process creates acopy of files and storesthem for a specific time.

Use for maintainingcopies of vital records forlegal or historicalpurposes.Note: If you need tofrequently create archivesfor the same data,consider using instantarchive (backup sets)instead. Frequent archiveoperations can create alarge amount of metadatain the server databaseresulting in increaseddatabase growth anddecreased performance forserver operations such asexpiration. Frequently,you can achieve the sameobjectives withincremental backup orbackup sets. Although thearchive function is apowerful way to storeinactive data with fixedretention, it should not beused on a frequent andlarge-scale basis as theprimary backup method.

The selected version ofthe file is retrieved onrequest.

See “Archive” onpage 478.

Instantarchive

The process creates abackup set of the mostrecent versions of thefiles for the client byusing files already inserver storage fromearlier backup operations.

Use when portability ofthe recovery media orrapid recovery of abackup-archive client isimportant. Also use forefficient archiving.

The files are restoreddirectly from the backupset. The backup setresides on media that canbe mounted on the clientsystem, such as a CD, atape drive, or a filesystem. The Tivoli StorageManager server does nothave to be contacted forthe restore process, so theprocess does not use thenetwork or the server.

See “Creating andusing client backupsets” on page 521.

Related tasks:Chapter 15, “Scheduling operations for client nodes,” on page 537


Progressive incremental backupsThe terms differential and incremental are often used to describe backups. Thestandard method of backup used by Tivoli Storage Manager is progressiveincremental.

The terms differential and incremental have the following meanings:v A differential backup backs up files that have changed since the last full backup.

– If a file changes after the full backup, the changed file is backed up again byevery subsequent differential backup.

– All files are backed up at the next full backup.v An incremental backup backs up only files that have changed since the last

backup, whether that backup was a full backup or another incremental backup.– If a file changes after the full backup, the changed file is backed up only by

the next incremental backup, not by all subsequent incremental backups.– If a file has not changed since the last backup, the file is not backed up.

Tivoli Storage Manager takes incremental backup one step further. After the initialfull backup of a client, no additional full backups are necessary because the

ibmtivoli storage manager for linux version 7.1 · this edition applies to version 7, release 1,...

Documents