IBM Tivoli Storage Managerfor WindowsVersion 7.1.1

Administrator's Guide

���

IBM Tivoli Storage Managerfor WindowsVersion 7.1.1

Administrator's Guide

���

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

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 . . . . . . . . . . . . . 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 . . . . . . . . . . 46Security 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 . . . . . 63

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 . . . . . . . 66Devices on storage area networks . . . . . . 67LAN-free data movement. . . . . . . . . 68Network-attached storage . . . . . . . . 69Mixed 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 . . . . . 82Cache copies for files stored on disk . . . . . . 83Freeing space on disk . . . . . . . . . . . 83Scratch FILE volumes . . . . . . . . . . . 84Volume history file and volume reuse . . . . . 84

Chapter 5. Attaching devices for theserver . . . . . . . . . . . . . . . 85Attaching a manual drive. . . . . . . . . . 85Attaching an automated library device . . . . . 86Device alias names . . . . . . . . . . . . 87Displaying information about devices with tsmdlst 88Selecting a device driver . . . . . . . . . . 90

Drivers for IBM devices . . . . . . . . . 90Drivers for non IBM devices. . . . . . . . 91Installing device drivers for IBM 3494 libraries . 92

© Copyright IBM Corp. 1993, 2014 iii

|||

Installing the Tivoli Storage Manager devicedriver . . . . . . . . . . . . . . . 92Uninstalling the Tivoli Storage Manager devicedriver . . . . . . . . . . . . . . . 93Using Windows device drivers with theGENERICTAPE format . . . . . . . . . 93Creating a file to list devices and their attributes 94Controlling devices with the Tivoli StorageManager device driver. . . . . . . . . . 94

Installing the Centera SDK for Centera sharedlibraries . . . . . . . . . . . . . . . 95

Chapter 6. Configuring storage devices 97Planning for device configuration . . . . . . . 98

Manually configuring devices . . . . . . . 98Configuring devices using Tivoli Storage Managercommands . . . . . . . . . . . . . . 103

Defining Tivoli Storage Manager storage objectswith commands . . . . . . . . . . . 104Determining backup strategies . . . . . . 107Determining the media and device type forclient backups . . . . . . . . . . . . 107

Configuring IBM 3494 libraries . . . . . . . 108Categories in an IBM 3494 library . . . . . 108Configuring an IBM 3494 library for use by oneserver . . . . . . . . . . . . . . . 109Sharing an IBM 3494 library among servers . . 114Migrating a shared IBM 3494 library to a librarymanager . . . . . . . . . . . . . . 116Sharing an IBM 3494 library by staticpartitioning of drives . . . . . . . . . . 117

ACSLS-managed libraries . . . . . . . . . 121Configuring an ACSLS-managed library . . . 121Configuring an ACSLS library with a singledrive device type . . . . . . . . . . . 122Configuring an ACSLS library with multipledrive device type . . . . . . . . . . . 123Setting up an ACSLS library manager server 125Setting up an ACSLS library client server . . . 126Checking in and labeling ACSLS libraryvolumes . . . . . . . . . . . . . . 127

Managing virtual tape libraries . . . . . . . 128Considerations for using virtual tape libraries 128Adding a virtual tape library to yourenvironment. . . . . . . . . . . . . 129Defining or deleting all drives and paths for asingle library . . . . . . . . . . . . 130

Configuring Tivoli Storage Manager servers toshare SAN-connected devices . . . . . . . . 131

Setting up server communications . . . . . 131Setting up the library manager server . . . . 131Setting up the library client servers . . . . . 133

Configuring Tivoli Storage Manager for LAN-freedata movement. . . . . . . . . . . . . 134

Validating your LAN-free configuration . . . 135Troubleshooting device configuration . . . . . 135

Displaying device information. . . . . . . 136Troubleshooting problems with devices. . . . 136Impact of device changes on the SAN . . . . 137

Increased block size for writing to tape . . . . . 138

Chapter 7. Managing removable mediaoperations. . . . . . . . . . . . . 141Defining volumes . . . . . . . . . . . . 141Managing volumes . . . . . . . . . . . 142

Partially-written volumes . . . . . . . . 142Volume inventory for automated libraries . . . 142Changing the status of database-backup anddatabase-export volumes . . . . . . . . 143

Preparing media for automated libraries . . . . 143Labeling media . . . . . . . . . . . . 143Checking media into automated library devices 144Write-once, read-many tape media . . . . . 147

Managing media in automated libraries . . . . 149Changing the status of automated libraryvolumes . . . . . . . . . . . . . . 149Removing volumes from automated libraries 150Returning partially written volumes toautomated libraries . . . . . . . . . . 150Returning reclaimed volumes to a library . . . 151Auditing volume inventories in libraries . . . 151Adding scratch volumes to automated librarydevices . . . . . . . . . . . . . . 152Setting up volume overflow locations forautomated libraries . . . . . . . . . . 152Modifying volume access modes . . . . . . 153Shared libraries. . . . . . . . . . . . 154Category numbers for IBM 3494 libraries . . . 155Media reuse in automated libraries . . . . . 155

Media management in manual libraries . . . . 156Tivoli Storage Manager server requests . . . . . 157

Starting the administrative client as a serverconsole monitor . . . . . . . . . . . 157Displaying information about volumes that arecurrently mounted. . . . . . . . . . . 157Displaying information about mount requeststhat are pending . . . . . . . . . . . 158Replying to mount requests . . . . . . . 158Canceling mount requests . . . . . . . . 158Responding to requests for volume checkin . . 159Dismounting idle volumes . . . . . . . . 159Dismounting volumes from stand-aloneremovable-file devices . . . . . . . . . 160Obtaining tape alert messages . . . . . . . 160

Tape rotation . . . . . . . . . . . . . 160Labeling volumes using commands . . . . . . 162Tivoli Storage Manager media-manager support 162Using external media managers to control media 163

Requirements for managing media in externallibraries . . . . . . . . . . . . . . 163

Troubleshooting database errors . . . . . . . 164Managing libraries . . . . . . . . . . . 164

Obtaining information about libraries . . . . 164Updating automated libraries . . . . . . . 165Deleting libraries . . . . . . . . . . . 166

Managing drives . . . . . . . . . . . . 166Requesting information about drives . . . . 166Updating drives . . . . . . . . . . . 167Using drive encryption . . . . . . . . . 168Validating data during read/write operations totape . . . . . . . . . . . . . . . 169Replacing tape drives. . . . . . . . . . 173

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

Cleaning drives . . . . . . . . . . . 177Deleting drives . . . . . . . . . . . . 182

Managing paths . . . . . . . . . . . . 182Obtaining information about paths . . . . . 182Updating paths. . . . . . . . . . . . 183Deleting paths . . . . . . . . . . . . 183

Managing data movers . . . . . . . . . . 183Obtaining information about data movers . . . 184Updating data movers . . . . . . . . . 184Deleting data movers. . . . . . . . . . 184

Managing disks . . . . . . . . . . . . 184Obtaining information about disks . . . . . 185Updating disks . . . . . . . . . . . . 185Deleting disks . . . . . . . . . . . . 185

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

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

Defining devices and paths . . . . . . . . . 189Defining libraries . . . . . . . . . . . 189Defining drives. . . . . . . . . . . . 190Defining data movers . . . . . . . . . 192Defining paths . . . . . . . . . . . . 193

Defining device classes . . . . . . . . . . 194Sequential-access device types . . . . . . . 195Defining tape device classes . . . . . . . 196Defining device classes for removable mediadevices . . . . . . . . . . . . . . 203Defining sequential-access disk (FILE) deviceclasses. . . . . . . . . . . . . . . 204Defining LTO device classes . . . . . . . 208Defining SERVER device classes . . . . . . 211Defining device classes for StorageTek VolSafedevices . . . . . . . . . . . . . . 212Defining device classes for CENTERA devices 214Obtaining information about device classes . . 215How Tivoli Storage Manager fills volumes . . 216

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

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

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

Configuring Tivoli Storage Manager for NDMPoperations . . . . . . . . . . . . . . 227

Configuring Tivoli Storage Manager policy forNDMP operations . . . . . . . . . . . 228Tape libraries and drives for NDMP operations 231

Attaching tape library robotics for NAS-attachedlibraries . . . . . . . . . . . . . . 234Registering NAS nodes with the Tivoli StorageManager server. . . . . . . . . . . . 239Defining a data mover for a NAS file server . . 240Defining paths for NDMP operations . . . . 240Labeling and checking tapes into the library . . 244Scheduling NDMP operations . . . . . . . 245Defining virtual file spaces . . . . . . . . 245Tape-to-tape copy to back up data . . . . . 245Tape-to-tape copy to move data . . . . . . 246

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

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

File-level backup and restore for NDMP operations 249Interfaces for file-level restore . . . . . . . 250International characters for NetApp file servers 251File level restore from a directory-level backupimage . . . . . . . . . . . . . . . 252

Directory-level backup and restore . . . . . . 252Directory-level backup and restore for NDMPoperations . . . . . . . . . . . . . 252Backing up and restoring with snapshots . . . 253

Backup and restore using NetApp SnapMirror toTape feature . . . . . . . . . . . . . . 253NDMP backup operations using Celerra file serverintegrated checkpoints . . . . . . . . . . 254Replicating NAS nodes with NDMP backup data 255

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

Properties of storage pool definitions . . . . 258Example: Defining storage pools . . . . . . 261Example: Updating storage pools. . . . . . 263Example: Setting up server storage . . . . . 264

Task tips for storage pools . . . . . . . . . 265Managing storage pool volumes . . . . . . . 267

Random-access storage pool volumes . . . . 267Sequential-access storage pool volumes. . . . 267Preparing volumes for random-access storagepools . . . . . . . . . . . . . . . 269Preparing volumes for sequential-access storagepools . . . . . . . . . . . . . . . 270Updating storage pool volumes . . . . . . 272Access modes for storage pool volumes . . . 273

Setting up a storage pool hierarchy . . . . . . 275Example: Defining a storage pool hierarchy . . 275Example: Updating a storage pool hierarchy . . 276How the server groups files for storage . . . 276Where the server stores files . . . . . . . 277Example: How the server determines where tostore files in a hierarchy . . . . . . . . . 278Backing up the data in a storage hierarchy . . 279Staging client data from disk to tape . . . . 284Migrating files in a storage pool hierarchy. . . 285

Caching in disk storage pools . . . . . . . . 298How the server removes cached files . . . . 299

Contents v

Effect of caching on storage pool statistics . . . 299Deduplicating data . . . . . . . . . . . 299

Data deduplication overview . . . . . . . 300Data deduplication limitations. . . . . . . 303Planning guidelines for data deduplication . . 305Detecting possible security attacks duringclient-side data deduplication . . . . . . . 317Evaluating data deduplication in a testenvironment. . . . . . . . . . . . . 318Managing deduplication-enabled storage pools 320Controlling data deduplication . . . . . . 324Displaying statistics about server-side datadeduplication . . . . . . . . . . . . 333Displaying statistics about client-side datadeduplication . . . . . . . . . . . . 334Querying file spaces for information aboutdeduplicated data . . . . . . . . . . . 337Scenarios for data deduplication . . . . . . 338Data deduplication and data compatibility . . 343Data deduplication and disaster recoverymanagement . . . . . . . . . . . . 345

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

Guidelines for using the simultaneous-writefunction . . . . . . . . . . . . . . 347Limitations that apply to simultaneous-writeoperations . . . . . . . . . . . . . 348Controlling the simultaneous-write function . . 349Simultaneous-write operations: Examples . . . 353Planning simultaneous-write operations . . . 367Simultaneous-write function as part of a backupstrategy: Example . . . . . . . . . . . 371

Keeping client files together using collocation . . 372The effects of collocation on operations . . . . 374How the server selects volumes with collocationenabled . . . . . . . . . . . . . . 376How the server selects volumes with collocationdisabled . . . . . . . . . . . . . . 378Collocation on or off settings . . . . . . . 378Collocation of copy storage pools andactive-data pools . . . . . . . . . . . 379Planning for and enabling collocation . . . . 380

Reclaiming space in sequential-access storage pools 382Reclaiming volumes with the most reclaimablespace . . . . . . . . . . . . . . . 383Starting reclamation manually or in a schedule 383Optimizing drive usage using multipleconcurrent reclamation processes . . . . . . 384Reclaiming volumes in a storage pool with onedrive . . . . . . . . . . . . . . . 385Reducing the time to reclaim tape volumes withhigh capacity . . . . . . . . . . . . 386Reclamation of write-once, read-many (WORM)media . . . . . . . . . . . . . . . 386Controlling reclamation of virtual volumes . . 386Reclaiming copy storage pools and active-datapools . . . . . . . . . . . . . . . 387How collocation affects reclamation . . . . . 391

Estimating space needs for storage pools . . . . 392Estimating space requirments in random-accessstorage pools . . . . . . . . . . . . 392

Estimating space needs in sequential-accessstorage pools . . . . . . . . . . . . 394

Monitoring storage-pool and volume usage . . . 394Monitoring space available in a storage pool 394Monitoring the use of storage pool volumes . . 397Monitoring migration processes . . . . . . 405Monitoring the use of cache space on diskstorage . . . . . . . . . . . . . . 408Obtaining information about the use of storagespace . . . . . . . . . . . . . . . 409

Moving data from one volume to another volume 413Data movement within the same storage pool 414Data movement to a different storage pool . . 415Data movement from offsite volumes in copystorage pools or active-data pools . . . . . 415Moving data . . . . . . . . . . . . 416

Moving data belonging to a client node . . . . 419Moving data in all file spaces belonging to oneor more nodes . . . . . . . . . . . . 419Moving data in selected file spaces belonging toa single node . . . . . . . . . . . . 420Obtaining information about data-movementprocesses . . . . . . . . . . . . . . 421Troubleshooting incomplete data-movementoperations . . . . . . . . . . . . . 421

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

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

Deleting storage pools . . . . . . . . . . 427Deleting storage pool volumes . . . . . . . 428

Deleting empty storage pool volumes . . . . 428Deleting storage pool volumes that contain data 429

Part 3. Managing client operations 431

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

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

Connecting nodes with the server . . . . . . 439Required client options . . . . . . . . . 439UNIX and Linux client options . . . . . . 440

Updating the password for scheduling operations 440Creating or updating a client options file . . . . 440

Using a text editor to create or configure a clientoptions file . . . . . . . . . . . . . 441

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

|||

Using the client configuration wizard to createor update a client options file . . . . . . . 441

Comparing network-attached nodes to local nodes 441Adding clients through the administrativecommand line client . . . . . . . . . . . 442

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

Chapter 12. Managing client nodes 445Managing nodes . . . . . . . . . . . . 445

Managing client nodes across a firewall . . . 446Updating client node information . . . . . 448Automatic deployment feature for thebackup-archive client . . . . . . . . . . 448Renaming client nodes . . . . . . . . . 449Locking and unlocking client nodes . . . . . 449Deleting client nodes . . . . . . . . . . 450Consolidating multiple clients under a singleclient node name . . . . . . . . . . . 450Displaying information about client nodes. . . 453Overview of remote access to webbackup-archive clients . . . . . . . . . 455Managing client access authority levels . . . . 456

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

Managing client option files . . . . . . . . 473Creating client option sets on the server . . . 473Managing client option sets . . . . . . . 475

Managing IBM Tivoli Storage Manager sessions 476Displaying information about IBM TivoliStorage Manager sessions . . . . . . . . 476Canceling an IBM Tivoli Storage Managersession . . . . . . . . . . . . . . 477When a client session is automatically canceled 478Disabling or enabling access to the server . . . 479Managing client restartable restore sessions . . 480

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

Reviewing the standard policy . . . . . . 484Getting users started . . . . . . . . . . 485Changing policy . . . . . . . . . . . 486File expiration and expiration processing . . . 486

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

Incremental backup . . . . . . . . . . 487Selective backup . . . . . . . . . . . 489Logical volume backup . . . . . . . . . 490Archive . . . . . . . . . . . . . . 490Automatic migration from a client node . . . 491

Creating your own policies . . . . . . . . . 492Defining and updating a policy domain . . . 493Managing backup copy groups . . . . . . 494Defining and updating an archive copy group 500

Policy set validation and activation . . . . . 502Example: Sample policy objects . . . . . . 503Example: Create a new policy . . . . . . . 506

Policy configuration scenarios . . . . . . . . 507Configuring policy for direct-to-tape backups 508Configuring policy for Tivoli Storage Managerapplication clients . . . . . . . . . . . 509Policy for logical volume backups . . . . . 509Configuring policy for NDMP operations . . . 510Configuring policy for LAN-free data movement 511Policy for Tivoli Storage Manager servers asclients . . . . . . . . . . . . . . . 513Setting policy to enable point-in-time restore forclients . . . . . . . . . . . . . . . 513

Running expiration processing to delete expiredfiles . . . . . . . . . . . . . . . . 514

Running expiration processing automatically 514Using commands to control expirationprocessing . . . . . . . . . . . . . 515Additional expiration processing with disasterrecovery manager . . . . . . . . . . . 515

Protection and expiration of archive data . . . . 516Data retention protection . . . . . . . . 516Deletion hold . . . . . . . . . . . . 517

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

Reclamation and the SnapLock feature . . . . 519Set up SnapLock volumes as Tivoli StorageManager WORM FILE volumes . . . . . . 523

Distributing policy using enterprise configuration 524

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

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

Encrypting data on tape . . . . . . . . . . 526Choosing an encryption method . . . . . . 527Changing your encryption method andhardware configuration . . . . . . . . . 528

Securing sensitive client data . . . . . . . . 529Setting up shredding . . . . . . . . . . 530Ensuring that shredding is enforced . . . . . 531

Creating and using client backup sets . . . . . 533Generating client backup sets on the server . . 534Restoring backup sets from a backup-archiveclient . . . . . . . . . . . . . . . 538Moving backup sets to other servers. . . . . 538Managing client backup sets . . . . . . . 539

Enabling clients to use subfile backup . . . . . 542Setting up clients to use subfile backup. . . . 543Managing subfile backups . . . . . . . . 543

Archiving data . . . . . . . . . . . . . 544Archive operations overview . . . . . . . 545Managing storage usage for archives . . . . 545

Chapter 15. Scheduling operations forclient nodes . . . . . . . . . . . . 549Prerequisites to scheduling operations . . . . . 549Scheduling a client operation . . . . . . . . 550

Contents vii

Defining client schedules . . . . . . . . 551Associating client nodes with schedules . . . 552Starting the scheduler on the clients . . . . . 552Displaying schedule information . . . . . . 553Checking the status of scheduled operations . . 553

Creating schedules for running command files . . 554Updating the client options file to automaticallygenerate a new password . . . . . . . . . 555Configuring the scheduler to run under thesite-server account. . . . . . . . . . . . 555Overview of the Tivoli Storage Manager schedulerrunning as a Windows service . . . . . . . . 556

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

Adding new schedules . . . . . . . . . 559Copying existing schedules . . . . . . . . 560Modifying schedules . . . . . . . . . . 560Deleting schedules . . . . . . . . . . 560Displaying information about schedules . . . 561

Managing node associations with schedules . . . 561Adding new nodes to existing schedules . . . 562Moving nodes from one schedule to another 562Displaying nodes associated with schedules . . 562Removing nodes from schedules . . . . . . 563

Managing event records . . . . . . . . . . 563Displaying information about scheduled events 563Managing event records in the server database 565

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

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

Part 4. Maintaining the server . . . 575

Chapter 17. Managing the storageenvironment from the OperationsCenter . . . . . . . . . . . . . . 577Operations Center overview . . . . . . . . 577Alert monitoring overview . . . . . . . . . 578Configuration tasks for alert monitoring . . . . 579Opening the Operations Center . . . . . . . 580Changing the Operations Center configuration . . 581

Changing the hub server . . . . . . . . 581Removing a spoke server . . . . . . . . 581Restoring the configuration to the preconfiguredstate . . . . . . . . . . . . . . . 582Starting and stopping the web server . . . . 583Restarting the initial configuration wizard . . . 584Setting the language of daily email reports . . 585

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

License registration . . . . . . . . . . 588License compliance . . . . . . . . . . 589Role of processor value units in assessinglicensing requirements . . . . . . . . . 590Estimating processor value units . . . . . . 593Collecting processor value unit information in aVMware host environment . . . . . . . . 595

Starting the Tivoli Storage Manager server . . . 596Starting the server on Windows . . . . . . 596Running multiple server instances on a singlesystem . . . . . . . . . . . . . . 600

Halting the server . . . . . . . . . . . . 601Moving the Tivoli Storage Manager server toanother system . . . . . . . . . . . . . 602Date and time on the server . . . . . . . . 603Managing server processes . . . . . . . . . 603

Requesting information about server processes 604Canceling server processes . . . . . . . . 604Preempting operations . . . . . . . . . 605

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

Add or update server options . . . . . . . . 608Add or update a server option withoutrestarting the server . . . . . . . . . . 609

Deleting information about volume history . . . 609Getting help on commands and error messages . . 610

Chapter 19. Automating serveroperations. . . . . . . . . . . . . 611Basic administrative command schedules . . . . 612

Defining the schedule . . . . . . . . . 612Verifying the schedule . . . . . . . . . 613

Schedule parameters . . . . . . . . . . . 613Scheduling commands to run by using classic orenhanced command schedules. . . . . . . 615

Copying schedules . . . . . . . . . . . 616Deleting schedules . . . . . . . . . . . 617Scheduled event records. . . . . . . . . . 617

Querying events . . . . . . . . . . . 617Removing event records from the database . . 618

Tivoli Storage Manager server scripts . . . . . 618Defining a server script . . . . . . . . . 619Managing server scripts . . . . . . . . . 623Running a server script . . . . . . . . . 627

Administrative client macros . . . . . . . . 627Writing commands in a macro. . . . . . . 628Writing comments in a macro . . . . . . . 629Including continuation characters in a macro 629Including substitution variables in a macro . . 630Running a macro . . . . . . . . . . . 630Command processing in a macro . . . . . . 631

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

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

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

Database: Overview . . . . . . . . . . 634Connecting the server to the database withTCP/IP . . . . . . . . . . . . . . 635Monitoring the database and recovery log . . . 636Recovery log management . . . . . . . . 638

Capacity planning . . . . . . . . . . . . 641Estimating database space requirements . . . 641Estimating recovery log space requirements . . 645Disk space requirements for the server databaseand recovery log . . . . . . . . . . . 658Monitoring space utilization for the databaseand recovery logs . . . . . . . . . . . 659

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

Reducing the size of the database . . . . . . 664Reducing the size of the database for V7.1servers . . . . . . . . . . . . . . 665Reducing the size of the database for all otherservers . . . . . . . . . . . . . . 665

Table and index reorganization schedules . . . . 666Restrictions to table and index reorganization 667Scheduling table or index reorganization . . . 668Reorganizing tables offline . . . . . . . . 669Locating space to reorganize indexes and tablesoffline . . . . . . . . . . . . . . . 671

Managing logs for the database . . . . . . . 671Increasing the size of the active log . . . . . 671Reducing the size of the active log . . . . . 672Compressing archive logs . . . . . . . . 672Adding optional logs after server initialization 673Specifying alternative locations for database logfiles . . . . . . . . . . . . . . . 673

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

Transaction processing . . . . . . . . . . 678Files moved as a group between client andserver . . . . . . . . . . . . . . . 679

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

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

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

Setting up communications for enterpriseconfiguration and enterprise event logging . . 686Setting up communications for commandrouting . . . . . . . . . . . . . . 690Updating and deleting servers. . . . . . . 694

Setting up enterprise configurations . . . . . . 695Enterprise configuration scenario . . . . . . 696

Creating the default profile on a configurationmanager . . . . . . . . . . . . . . 700Creating and changing configuration profiles 701Getting information about profiles . . . . . 708Subscribing to a profile . . . . . . . . . 711

Refreshing configuration information . . . . . 715Managing problems with configuration refresh 716

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

Managing multiple servers from a web-basedinterface . . . . . . . . . . . . . . 719Routing commands . . . . . . . . . . 720Setting up server groups . . . . . . . . 722Querying server availability . . . . . . . 726

Storing data on another server as virtual volumes 726Setting up source and target servers for virtualvolumes . . . . . . . . . . . . . . 728Performance limitations for virtual volumeoperations . . . . . . . . . . . . . 729Performing operations at the source server . . 730Reconciling virtual volumes and archive files 733

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

Exporting restrictions. . . . . . . . . . 736Deciding what information to export . . . . 736Deciding when to export . . . . . . . . 737

Exporting data directly to another server . . . . 738Options to consider before you export data . . 739Preparing to export to another server forimmediate import . . . . . . . . . . . 742Monitoring the server-to-server export process 744Exporting administrator information to anotherserver . . . . . . . . . . . . . . . 745Exporting client node information to anotherserver . . . . . . . . . . . . . . . 745Exporting policy information to another server 746Exporting server data to another server . . . 746

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

Previewing data export or import . . . . . 747Planning for sequential media used to exportdata . . . . . . . . . . . . . . . 748Exporting tasks. . . . . . . . . . . . 749Importing data from sequential media volumes 752Monitoring export and import processes . . . 763Exporting and importing data from virtualvolumes . . . . . . . . . . . . . . 767

Part 5. Monitoring operations . . . 769

Contents ix

||||||||

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

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

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

Cognos status and trend reports . . . . . . 782Create custom Cognos reports . . . . . . . 790Scheduling Cognos reports to be emailed . . . 790Sharing Cognos Reports . . . . . . . . . 791

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

IBM Tivoli Monitoring reporting queries . . . 794Backing up and restoring Tivoli Monitoring forTivoli Storage Manager . . . . . . . . . . 796

Backing up Tivoli Monitoring for Tivoli StorageManager . . . . . . . . . . . . . . 797Restoring Tivoli Monitoring for Tivoli StorageManager . . . . . . . . . . . . . . 810

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

Requesting information about IBM TivoliStorage Manager definitions . . . . . . . 819Requesting information about client sessions 820Requesting information about server processes 821Requesting information about server settings 822Querying server options . . . . . . . . . 822

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

Using SELECT commands . . . . . . . . 823Using SELECT commands in Tivoli StorageManager scripts . . . . . . . . . . . 826Querying the SQL activity summary table . . . 827Creating output for use by another application 828

Using the Tivoli Storage Manager activity log . . 828Requesting information from the activity log 829Setting a retention period for the activity log 830Setting a size limit for the activity log . . . . 830

Monitoring Tivoli Storage Manager accountingrecords . . . . . . . . . . . . . . . 831Logging IBM Tivoli Storage Manager events toreceivers . . . . . . . . . . . . . . . 832

Enabling and disabling events . . . . . . . 833Beginning and ending event logging . . . . 834Logging events to the IBM Tivoli StorageManager server console and activity log . . . 834Logging events to a file exit and a user exit . . 835Logging events to the Tivoli Enterprise Console 836Logging events to an SNMP manager . . . . 840Logging events to the Windows event log . . . 845

Enterprise event logging: logging events toanother server . . . . . . . . . . . . 845Querying event logging . . . . . . . . . 847User exit and file exit receivers . . . . . . 847

Part 6. Protecting the server . . . 853

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

Secure Sockets Layer and Transport LayerSecurity communication . . . . . . . . . 856Administrative authority and privilege classes 857Setting up Secure Sockets Layer and TransportLayer Security . . . . . . . . . . . . 859

Securing the server console . . . . . . . . . 869Managing access to the server and clients . . . . 870

Managing Tivoli Storage Manager administratorIDs . . . . . . . . . . . . . . . . 870

Managing passwords and logon procedures . . . 876Configuring a directory server for passwordauthentication . . . . . . . . . . . . 879Setting the policy for an LDAP-authenticatedpassword. . . . . . . . . . . . . . 881Configuring the Tivoli Storage Manager serverto authenticate passwords with an LDAPdirectory server . . . . . . . . . . . 882Registering nodes and administrator IDs toauthenticate passwords with an LDAP directoryserver . . . . . . . . . . . . . . . 883Updating nodes and administrator IDs toauthenticate passwords with a directory server . 884Determining which nodes and administrator IDsare configured to authenticate with an LDAPserver . . . . . . . . . . . . . . . 885Modifying the default password expirationperiod for passwords that are managed by theTivoli Storage Manager server . . . . . . . 885Scenarios for authenticating passwords . . . . 888Enabling unified logon with backup-archiveclients . . . . . . . . . . . . . . . 890

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

Backing up the server database . . . . . . 894Protecting infrastructure setup files . . . . . 902

Client data protection . . . . . . . . . . 907Protecting the data that is in primary storagepools . . . . . . . . . . . . . . . 907Auditing storage pool volumes . . . . . . 912Fixing damaged files . . . . . . . . . . 921

Scenario: Protecting the database and storage pools 923Recovering the database and client data . . . . 925

Restoring the database . . . . . . . . . 926Restoring storage pools and storage poolvolumes . . . . . . . . . . . . . . 932

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

|||

||

||

Restoring and recovering an LDAP server . . . 939Audit the LDAP server . . . . . . . . . 940

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

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

Chapter 28. Replication of client nodedata . . . . . . . . . . . . . . . 945Automatic failover for data recovery overview . . 946Source and target node-replication servers. . . . 947

Replication server configurations . . . . . . 947Policy management for node replication . . . 949Node replication processing . . . . . . . 950

Planning for node replication . . . . . . . . 961Determining server database requirements fornode replication . . . . . . . . . . . 962Estimating the total amount of data to bereplicated. . . . . . . . . . . . . . 963Estimating network bandwidth required forreplication . . . . . . . . . . . . . 964Calculating the time that is required forreplication . . . . . . . . . . . . . 964Selecting a method for the initial replication . . 965Scheduling incremental replication after theinitial replication . . . . . . . . . . . 967

Node replication restrictions . . . . . . . . 968Task tips for node replication . . . . . . . . 971

Change replication rules. . . . . . . . . 971Add and remove client nodes for replication 971Manage replication servers . . . . . . . . 972Validate a configuration and preview results 973Manage replication processing. . . . . . . 973Monitor replication processing and verify results 974

Setting up the default replication configuration . . 975Step 1: Setting up server-to-servercommunications . . . . . . . . . . . 976Step 2: Specifying a target replication server . . 979Step 3: Configuring client nodes for replication 980

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

Verifying a node replication setup beforeprocessing . . . . . . . . . . . . . . 995Managing data replication . . . . . . . . . 996

Replicating data by command . . . . . . . 996Controlling throughput for node replication 1001Disabling and enabling node replication . . . 1004Managing replicated client-node data using thetarget replication server policies . . . . . . 1008Purging replicated data in a file space . . . . 1011Replicating client node data after a databaserestore . . . . . . . . . . . . . . 1011

Monitoring node replication processing andverifying results . . . . . . . . . . . . 1013

Displaying information about node replicationsettings . . . . . . . . . . . . . . 1013Displaying information about running andcompleted node replication processes . . . . 1014Displaying the activity log of a replicationprocess . . . . . . . . . . . . . . 1014Displaying summary records of replicationprocesses . . . . . . . . . . . . . 1015Measuring the effectiveness of a replicationconfiguration . . . . . . . . . . . . 1015Measuring the effects of data deduplication onnode replication processing . . . . . . . 1015Retaining replication records . . . . . . . 1016

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

Removing a node replication configuration . . . 1018

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

Cluster nodes . . . . . . . . . . . . 1020Configuring a Windows clustered environment 1020

Microsoft Failover Cluster environmentoverview . . . . . . . . . . . . . 1021Tape failover for nodes in a cluster . . . . . 1022Planning for a clustered environment . . . . 1024Setting up Tivoli Storage Manager in aMicrosoft Failover Cluster . . . . . . . . 1027Maintaining the clustered environment . . . 1029

Chapter 30. Disaster recoverymanager . . . . . . . . . . . . . 1033Preparing for disaster recovery . . . . . . . 1034Disaster recovery manager checklist . . . . . 1036Managing the Disaster Recovery Manager tasks 1041The disaster recovery plan file . . . . . . . 1043

Breaking out a disaster recovery plan file. . . 1043Structure of the disaster recovery plan file . . 1046Example disaster recovery plan file. . . . . 1049

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

Specifying defaults for the disaster recoveryplan file . . . . . . . . . . . . . . 1067Specifying defaults for offsite recovery mediamanagement . . . . . . . . . . . . 1070

Specifying recovery instructions for your site . . 1072Specifying information about your server andclient node machines . . . . . . . . . . 1074Specifying recovery media for client machines 1078Creating and storing the disaster recovery plan 1079

Storing the disaster recovery plan locally . . . 1080Storing the disaster recovery plan on a targetserver . . . . . . . . . . . . . . 1081Disaster recovery plan environment . . . . 1081

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

Contents xi

|||

Displaying information about recovery planfiles . . . . . . . . . . . . . . . 1083Displaying the contents of a recovery plan file 1084Restoring a recovery plan file . . . . . . 1084Expiring recovery plan files automatically . . 1085Deleting recovery plan files manually . . . . 1085

Moving backup media for disaster recoveryoperations . . . . . . . . . . . . . . 1086

Moving copy storage pool and active-data poolvolumes offsite . . . . . . . . . . . 1088Moving copy storage pool and active-data poolvolumes onsite . . . . . . . . . . . 1090

Recovering from a disaster . . . . . . . . 1091Recovering the server scenario . . . . . . 1092Recovering the client scenario . . . . . . 1095

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

Automated SCSI library at the original andrecovery sites . . . . . . . . . . . . 1098Automated SCSI library at the original site anda manual SCSI library at the recovery site . . 1099Managing copy storage pool volumes andactive-data pool volumes at the recovery site . 1100

Chapter 31. Integrating disasterrecovery manager and nodereplication into your disasterrecovery strategy . . . . . . . . . 1103Plan for a disaster recovery strategy . . . . . 1104Tier 0: No disaster recovery capability . . . . . 1105Tier 1: Offsite vaulting from a single productionsite . . . . . . . . . . . . . . . . 1105Tier 2: Offsite vaulting with a recovery site . . . 1106Tier 3: Electronic vaulting of critical data . . . . 1106Tier 4: Active data management at peer sites . . 1107Tier 5: Synchronous replication . . . . . . . 1108Tier 6: Synchronous replication with coupling orclustering applications . . . . . . . . . . 1109

Part 7. Appendixes. . . . . . . . 1111

Appendix A. External mediamanagement interface description . . 1113CreateProcess call. . . . . . . . . . . . 1113Processing during server initialization . . . . . 1114Processing for mount requests . . . . . . . 1114Processing for release requests . . . . . . . 1115Processing for batch requests . . . . . . . . 1115Error handling. . . . . . . . . . . . . 1116Begin batch request . . . . . . . . . . . 1116End batch request . . . . . . . . . . . 1116Volume query request . . . . . . . . . . 1117Initialization requests . . . . . . . . . . 1118Volume eject request. . . . . . . . . . . 1118Volume release request . . . . . . . . . . 1119Volume mount request . . . . . . . . . . 1120Volume dismount request . . . . . . . . . 1123

Appendix B. User exit and file exitreceivers . . . . . . . . . . . . . 1125Sample user-exit declarations . . . . . . . . 1125Sample user exit program . . . . . . . . . 1127Readable text file exit (FILETEXTEXIT) format 1128

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

Notices . . . . . . . . . . . . . 1133Trademarks. . . . . . . . . . . . . . 1135Privacy policy considerations . . . . . . . . 1135

Glossary . . . . . . . . . . . . . 1137

Index . . . . . . . . . . . . . . 1139

xii IBM Tivoli Storage Manager for Windows: 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 Windows 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 Windows: 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 782

xvi IBM Tivoli Storage Manager for Windows: 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 922

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 1010

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 672

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 Windows: 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 ulimitsIf 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.

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

Part 1. Tivoli Storage Manager basics

© Copyright IBM Corp. 1993, 2014 1

2 IBM Tivoli Storage Manager for Windows: 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:

4 IBM Tivoli Storage Manager for Windows: Administrator's Guide

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 483Related tasks:“Policy-based data management” on page 36

6 IBM Tivoli Storage Manager for Windows: Administrator's Guide

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.

Chapter 1. Tivoli Storage Manager overview 7

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.

8 IBM Tivoli Storage Manager for Windows: Administrator's Guide

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 page487.

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 page489.

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 page542.

Chapter 1. Tivoli Storage Manager overview 9

Table 2. Summary of client operations (continued)

Description Usage Restore options For moreinformation

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 page509.

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 page219.

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.

10 IBM Tivoli Storage Manager for Windows: Administrator'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)

Description Usage Restore options For moreinformation

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 490.

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 533.

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

Chapter 1. Tivoli Storage Manager overview 11

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 cli