ibmtivoli storage manager for oracle solaris version 7.1€¦ · defining device classes for...

IBM Tivoli Storage Managerfor Oracle SolarisVersion 7.1.1

Administrator's Guide

��

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

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

Tivoli Monitoring for Tivoli Storage Managerupdates . . . . . . . . . . . . . . xvUpdates for the Tivoli Storage Manager servercomponent . . . . . . . . . . . . . xv

Best practices for Version 7.1 . . . . . . . . xviiMaximum daily capability for datadeduplication . . . . . . . . . . . . xviiServer startup and setting ulimits . . . . . xviiiDuplicate identification processes and memoryrequirements . . . . . . . . . . . . xviiiConfiguring the server to prevent issues withdatabase backups. . . . . . . . . . . xviii

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

Schedules for client operations . . . . . . . 49Server management . . . . . . . . . . . 50

Server-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. . . . . . . . . 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 . . . . . . . . . . . . . . 77File systems and raw logical volumes for randomaccess storage . . . . . . . . . . . . . 81Configuring random access volumes on disk devices 82Configuring FILE sequential volumes on diskdevices . . . . . . . . . . . . . . . . 83Varying disk volumes online or offline . . . . . 84Cache copies for files stored on disk . . . . . . 84Freeing space on disk . . . . . . . . . . . 85Scratch 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 . . . . . . . . . . . 89

© Copyright IBM Corp. 1993, 2014 iii

|||

Tivoli Storage Manager device drivers . . . . 89Device special file names . . . . . . . . . . 90

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

Tivoli Storage Manager server device utilities . . . 91autoconf (Auto configure devices) . . . . . . 91rmstdev (Detect and delete device special files) 92Displaying information about devices withtsmdlist. . . . . . . . . . . . . . . 92

Installing and configuring device drivers . . . . 93Installing device drivers for IBM SCSI tapedevices . . . . . . . . . . . . . . . 93Installing device drivers for IBM 349x libraries 95

Configuring Tivoli Storage Manager device driversfor vendor acquired SCSI-attached devices . . . . 95Reinstalling or upgrading the Tivoli StorageManager device driver. . . . . . . . . . . 97Editing configuration files . . . . . . . . . 98Preventing tape labels from being overwritten . . 100Installing the Tivoli Storage Manager device driverto Solaris Zones . . . . . . . . . . . . 101

Adding devices to non-global zones . . . . . 101Displaying devices configured in zones. . . . 103Removing devices from non-global zones . . . 104

Installing the Centera SDK for Centera sharedlibraries . . . . . . . . . . . . . . . 105

Chapter 6. Configuring storagedevices . . . . . . . . . . . . . . 107Configuring libraries for use by one server . . . 108

Example: Configure a SCSI or virtual tapelibrary with a single drive device type . . . . 109Example: Configure a SCSI or virtual tapelibrary with multiple drive device types . . . 110Example: Configure an ACSLS library with asingle drive device type . . . . . . . . . 112Example: Configure an ACSLS library withmultiple drive device types . . . . . . . . 113Example: Configure a 3494 library with a singledrive device type . . . . . . . . . . . 114Example: Configure a 3494 library with multipledrive device types . . . . . . . . . . . 115

Configuring library sharing. . . . . . . . . 116Example: Configure library sharing for SCSI orvirtual tape libraries . . . . . . . . . . 117Example: Configure library sharing for ACSLSlibraries . . . . . . . . . . . . . . 119Example: Configure library sharing for 3494libraries . . . . . . . . . . . . . . 120

Managing virtual tape libraries . . . . . . . 120Considerations for using virtual tape libraries 121Adding a virtual tape library to yourenvironment. . . . . . . . . . . . . 122Defining or deleting all drives and paths for asingle library . . . . . . . . . . . . 123

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

Example of removable file support . . . . . 126

Labeling requirements for removable file devicetypes . . . . . . . . . . . . . . . 127

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

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

Configuring manually mounted devices . . . . 130Defining devices as part of a manual library . . 130Labeling volumes . . . . . . . . . . . 131

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

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

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

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

Labeling removable media volumes . . . . . 136Checking new volumes into a library . . . . 139Write-once, read-many tape media . . . . . 144

Managing the volume inventory . . . . . . . 146Controlling access to volumes . . . . . . . 146Reusing tapes in storage pools . . . . . . 147Setting up a tape rotation . . . . . . . . 147Reusing volumes used for database backupsand export operations . . . . . . . . . 149Maintaining a supply of scratch volumes . . . 149Maintaining a supply of volumes in a librarycontaining WORM media . . . . . . . . 150

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

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

Requesting information about libraries . . . . 157Updating libraries . . . . . . . . . . . 158Deleting libraries . . . . . . . . . . . 159

Managing drives . . . . . . . . . . . . 159Requesting information about drives . . . . 159Updating drives . . . . . . . . . . . 160Drive encryption . . . . . . . . . . . 161Validating data during read/write operations totape . . . . . . . . . . . . . . . 162Cleaning drives . . . . . . . . . . . 166Deleting drives . . . . . . . . . . . . 171

Managing paths . . . . . . . . . . . . 171Requesting information about paths . . . . . 171Updating paths. . . . . . . . . . . . 171Deleting paths . . . . . . . . . . . . 172

Managing data movers . . . . . . . . . . 172Requesting information about data movers . . 172Updating data movers . . . . . . . . . 172Deleting data movers. . . . . . . . . . 173

iv IBM Tivoli Storage Manager for Oracle Solaris: Administrator's Guide

Tape alert messages . . . . . . . . . . . 173

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

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

Defining devices and paths . . . . . . . . . 177Defining libraries . . . . . . . . . . . 177Defining drives. . . . . . . . . . . . 178Defining data movers . . . . . . . . . 180Defining paths . . . . . . . . . . . . 180Shared FILE volumes. . . . . . . . . . 181

Defining device classes . . . . . . . . . . 182Sequential-access device types . . . . . . . 184Defining tape device classes . . . . . . . 185Defining device classes for removable mediadevices . . . . . . . . . . . . . . 191Defining sequential-access disk (FILE) deviceclasses. . . . . . . . . . . . . . . 192Defining LTO device classes . . . . . . . 196Defining SERVER device classes . . . . . . 199Defining device classes for StorageTek VolSafedevices . . . . . . . . . . . . . . 200Defining device classes for CENTERA devices 202Obtaining information about device classes . . 203How Tivoli Storage Manager fills volumes . . 204

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

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

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

Configuring Tivoli Storage Manager for NDMPoperations . . . . . . . . . . . . . . 215

Configuring Tivoli Storage Manager policy forNDMP operations . . . . . . . . . . . 216Tape libraries and drives for NDMP operations 219Attaching tape library robotics for NAS-attachedlibraries . . . . . . . . . . . . . . 223Registering NAS nodes with the Tivoli StorageManager server. . . . . . . . . . . . 227Defining a data mover for a NAS file server . . 228Defining paths for NDMP operations . . . . 228Labeling and checking tapes into the library . . 232Scheduling NDMP operations . . . . . . . 233Defining virtual file spaces . . . . . . . . 233Tape-to-tape copy to back up data . . . . . 233Tape-to-tape copy to move data . . . . . . 234

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

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

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

Directory-level backup and restore . . . . . . 240Directory-level backup and restore for NDMPoperations . . . . . . . . . . . . . 240Backing up and restoring with snapshots . . . 241

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

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

Properties of storage pool definitions . . . . 246Example: Defining storage pools . . . . . . 249Example: Updating storage pools. . . . . . 251Example: Setting up server storage . . . . . 252

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

Random-access storage pool volumes . . . . 255Sequential-access storage pool volumes. . . . 256Preparing volumes for random-access storagepools . . . . . . . . . . . . . . . 258Preparing volumes for sequential-access storagepools . . . . . . . . . . . . . . . 259Updating storage pool volumes . . . . . . 261Access modes for storage pool volumes . . . 262

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

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

Deduplicating data . . . . . . . . . . . 288Data deduplication overview . . . . . . . 289Data deduplication limitations. . . . . . . 292Planning guidelines for data deduplication . . 294Detecting possible security attacks duringclient-side data deduplication . . . . . . . 306Evaluating data deduplication in a testenvironment. . . . . . . . . . . . . 307Managing deduplication-enabled storage pools 309Controlling data deduplication . . . . . . 313

Contents v

Displaying statistics about server-side datadeduplication . . . . . . . . . . . . 322Displaying statistics about client-side datadeduplication . . . . . . . . . . . . 323Querying file spaces for information aboutdeduplicated data . . . . . . . . . . . 326Scenarios for data deduplication . . . . . . 327Data deduplication and data compatibility . . 332Data deduplication and disaster recoverymanagement . . . . . . . . . . . . 334

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

Guidelines for using the simultaneous-writefunction . . . . . . . . . . . . . . 336Limitations that apply to simultaneous-writeoperations . . . . . . . . . . . . . 337Controlling the simultaneous-write function . . 338Simultaneous-write operations: Examples . . . 342Planning simultaneous-write operations . . . 356Simultaneous-write function as part of a backupstrategy: Example . . . . . . . . . . . 360

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

Reclaiming space in sequential-access storage pools 371Reclaiming volumes with the most reclaimablespace . . . . . . . . . . . . . . . 372Starting reclamation manually or in a schedule 372Optimizing drive usage using multipleconcurrent reclamation processes . . . . . . 373Reclaiming volumes in a storage pool with onedrive . . . . . . . . . . . . . . . 374Reducing the time to reclaim tape volumes withhigh capacity . . . . . . . . . . . . 375Reclamation of write-once, read-many (WORM)media . . . . . . . . . . . . . . . 375Controlling reclamation of virtual volumes . . 375Reclaiming copy storage pools and active-datapools . . . . . . . . . . . . . . . 376How collocation affects reclamation . . . . . 380

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

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

Moving data from one volume to another volume 402

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

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

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

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

Deleting storage pools . . . . . . . . . . 416Deleting storage pool volumes . . . . . . . 417

Deleting empty storage pool volumes . . . . 417Deleting storage pool volumes that contain data 418

Part 3. Managing client operations 419

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

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

Connecting nodes with the server . . . . . . 427Required client options . . . . . . . . . 427UNIX and Linux client options . . . . . . 428

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

Comparing network-attached nodes to local nodes 429Adding clients through the administrativecommand line client . . . . . . . . . . . 430

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

Chapter 12. Managing client nodes 431Managing nodes . . . . . . . . . . . . 431

Managing client nodes across a firewall . . . 432Updating client node information . . . . . 434

vi IBM Tivoli Storage Manager for Oracle Solaris: Administrator's Guide

|||

Automatic deployment feature for thebackup-archive client . . . . . . . . . . 434Renaming client nodes . . . . . . . . . 435Locking and unlocking client nodes . . . . . 435Deleting client nodes . . . . . . . . . . 436Consolidating multiple clients under a singleclient node name . . . . . . . . . . . 436Displaying information about client nodes. . . 439Overview of remote access to webbackup-archive clients . . . . . . . . . 441Managing client access authority levels . . . . 442

Managing file spaces . . . . . . . . . . . 445Defining client nodes and file spaces . . . . 446Supporting Unicode-enabled clients . . . . . 448Displaying information about file spaces . . . 457Moving data for a client node . . . . . . . 458Deleting file spaces . . . . . . . . . . 458

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

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

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

Reviewing the standard policy . . . . . . 470Getting users started . . . . . . . . . . 471Changing policy . . . . . . . . . . . 472File expiration and expiration processing . . . 472

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

Incremental backup . . . . . . . . . . 473Selective backup . . . . . . . . . . . 475Logical volume backup . . . . . . . . . 476Archive . . . . . . . . . . . . . . 476Automatic migration from a client node . . . 477

Creating your own policies . . . . . . . . . 478Defining and updating a policy domain . . . 479Managing backup copy groups . . . . . . 480Defining and updating an archive copy group 486Policy set validation and activation . . . . . 488Example: Sample policy objects . . . . . . 489Example: Create a new policy . . . . . . . 492

Policy configuration scenarios . . . . . . . . 493Configuring policy for direct-to-tape backups 494Configuring policy for Tivoli Storage Managerapplication clients . . . . . . . . . . . 495Policy for logical volume backups . . . . . 495Configuring policy for NDMP operations . . . 496Configuring policy for LAN-free datamovement . . . . . . . . . . . . . 497Policy for Tivoli Storage Manager servers asclients . . . . . . . . . . . . . . . 499

Setting policy to enable point-in-time restore forclients . . . . . . . . . . . . . . . 499

Running expiration processing to delete expiredfiles . . . . . . . . . . . . . . . . 500

Running expiration processing automatically 500Using commands to control expirationprocessing . . . . . . . . . . . . . 501Additional expiration processing with disasterrecovery manager . . . . . . . . . . . 501

Protection and expiration of archive data . . . . 502Data retention protection . . . . . . . . 502Deletion hold . . . . . . . . . . . . 503

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

Reclamation and the SnapLock feature . . . . 505Set up SnapLock volumes as Tivoli StorageManager WORM FILE volumes . . . . . . 509

Distributing policy using enterprise configuration 510

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

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

Encrypting data on tape . . . . . . . . . . 512Choosing an encryption method . . . . . . 513Changing your encryption method andhardware configuration . . . . . . . . . 514

Securing sensitive client data . . . . . . . . 515Setting up shredding . . . . . . . . . . 516Ensuring that shredding is enforced . . . . . 517

Creating and using client backup sets . . . . . 519Generating client backup sets on the server . . 520Restoring backup sets from a backup-archiveclient . . . . . . . . . . . . . . . 524Moving backup sets to other servers. . . . . 524Managing client backup sets . . . . . . . 525

Enabling clients to use subfile backup . . . . . 528Setting up clients to use subfile backup. . . . 529Managing subfile backups . . . . . . . . 529

Archiving data . . . . . . . . . . . . . 530Archive operations overview . . . . . . . 531Managing storage usage for archives . . . . 531

Chapter 15. Scheduling operations forclient nodes . . . . . . . . . . . . 535Prerequisites to scheduling operations . . . . . 535Scheduling a client operation . . . . . . . . 536

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

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

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

Contents vii

Adding new schedules . . . . . . . . . 543Copying existing schedules . . . . . . . . 544Modifying schedules . . . . . . . . . . 544Deleting schedules . . . . . . . . . . 544Displaying information about schedules . . . 545

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

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

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

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

Part 4. Maintaining the server . . . 559

Chapter 17. Managing the storageenvironment from the OperationsCenter . . . . . . . . . . . . . . 561Operations Center overview . . . . . . . . 561Alert monitoring overview . . . . . . . . . 562Configuration tasks for alert monitoring . . . . 563Opening the Operations Center . . . . . . . 564

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

License registration . . . . . . . . . . 568License compliance . . . . . . . . . . 569Role of processor value units in assessinglicensing requirements . . . . . . . . . 570Estimating processor value units . . . . . . 573Collecting processor value unit information in aVMware host environment . . . . . . . . 575

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

Halting the server . . . . . . . . . . . . 586Moving the Tivoli Storage Manager server toanother system . . . . . . . . . . . . . 587Date and time on the server . . . . . . . . 588Managing server processes . . . . . . . . . 588

Requesting information about server processes 589Canceling server processes . . . . . . . . 589Preempting operations . . . . . . . . . 590

Changing names in Tivoli Storage Manager . . . 592Setting the server name . . . . . . . . . 592

Changing the host name for a Tivoli StorageManager server. . . . . . . . . . . . 592

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

Deleting information about volume history . . . 594Getting help on commands and error messages . . 595

Chapter 19. Automating serveroperations. . . . . . . . . . . . . 597Basic administrative command schedules . . . . 598

Defining the schedule . . . . . . . . . 598Verifying the schedule . . . . . . . . . 599

Schedule parameters . . . . . . . . . . . 599Scheduling commands to run by using classic orenhanced command schedules. . . . . . . 601

Copying schedules . . . . . . . . . . . 602Deleting schedules . . . . . . . . . . . 603Scheduled event records. . . . . . . . . . 603

Querying events . . . . . . . . . . . 603Removing event records from the database . . 604

Tivoli Storage Manager server scripts . . . . . 604Defining a server script . . . . . . . . . 605Managing server scripts . . . . . . . . . 609Running a server script . . . . . . . . . 613

Administrative client macros . . . . . . . . 613Writing commands in a macro. . . . . . . 614Writing comments in a macro . . . . . . . 615Including continuation characters in a macro 615Including substitution variables in a macro . . 616Running a macro . . . . . . . . . . . 616Command processing in a macro . . . . . . 617

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

Database: Overview . . . . . . . . . . 620Connecting the server to the database withTCP/IP . . . . . . . . . . . . . . 621Monitoring the database and recovery log . . . 622Recovery log management . . . . . . . . 624

Capacity planning . . . . . . . . . . . . 627Estimating database space requirements . . . 627Estimating recovery log space requirements . . 631Disk space requirements for the server databaseand recovery log . . . . . . . . . . . 644Monitoring space utilization for the databaseand recovery logs . . . . . . . . . . . 645

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

Reducing the size of the database . . . . . . 650Reducing the size of the database for V7.1servers . . . . . . . . . . . . . . 651Reducing the size of the database for all otherservers . . . . . . . . . . . . . . 651

Table and index reorganization schedules . . . . 652Restrictions to table and index reorganization 653Scheduling table or index reorganization . . . 654Reorganizing tables offline . . . . . . . . 655

viii IBM Tivoli Storage Manager for Oracle Solaris: Administrator's Guide

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

||||||||

||

Locating space to reorganize indexes and tablesoffline . . . . . . . . . . . . . . . 657

Managing logs for the database . . . . . . . 657Increasing the size of the active log . . . . . 657Reducing the size of the active log . . . . . 658Compressing archive logs . . . . . . . . 658Adding optional logs after server initialization 659Specifying alternative locations for database logfiles . . . . . . . . . . . . . . . 659

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

Transaction processing . . . . . . . . . . 664Files moved as a group between client andserver . . . . . . . . . . . . . . . 665

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

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

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

Setting up communications for enterpriseconfiguration and enterprise event logging . . 672Setting up communications for commandrouting . . . . . . . . . . . . . . 676Updating and deleting servers. . . . . . . 680

Setting up enterprise configurations . . . . . . 681Enterprise configuration scenario . . . . . . 682Creating the default profile on a configurationmanager . . . . . . . . . . . . . . 686Creating and changing configuration profiles 687Getting information about profiles . . . . . 694Subscribing to a profile . . . . . . . . . 697

Refreshing configuration information . . . . . 701Managing problems with configuration refresh 702

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

Managing multiple servers from a web-basedinterface . . . . . . . . . . . . . . 705Routing commands . . . . . . . . . . 706Setting up server groups . . . . . . . . 708Querying server availability . . . . . . . 712

Storing data on another server as virtual volumes 712Setting up source and target servers for virtualvolumes . . . . . . . . . . . . . . 714

Performance limitations for virtual volumeoperations . . . . . . . . . . . . . 715Performing operations at the source server . . 716Reconciling virtual volumes and archive files 719

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

Exporting restrictions. . . . . . . . . . 722Deciding what information to export . . . . 722Deciding when to export . . . . . . . . 723

Exporting data directly to another server . . . . 724Options to consider before you export data . . 725Preparing to export to another server forimmediate import . . . . . . . . . . . 728Monitoring the server-to-server export process 730Exporting administrator information to anotherserver . . . . . . . . . . . . . . . 731Exporting client node information to anotherserver . . . . . . . . . . . . . . . 731Exporting policy information to another server 732Exporting server data to another server . . . 732

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

Previewing data export or import . . . . . 733Planning for sequential media used to exportdata . . . . . . . . . . . . . . . 734Exporting tasks. . . . . . . . . . . . 735Importing data from sequential media volumes 738Monitoring export and import processes . . . 749Exporting and importing data from virtualvolumes . . . . . . . . . . . . . . 753

Part 5. Monitoring operations . . . 755

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

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

Cognos status and trend reports . . . . . . 768Create custom Cognos reports . . . . . . . 775Scheduling Cognos reports to be emailed . . . 775Sharing Cognos Reports . . . . . . . . . 776

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

IBM Tivoli Monitoring reporting queries . . . 777

Contents ix

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

|||

||

||

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

Requesting information about IBM TivoliStorage Manager definitions . . . . . . . 781Requesting information about client sessions 782Requesting information about server processes 783Requesting information about server settings 784Querying server options . . . . . . . . . 784

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

Using SELECT commands . . . . . . . . 785Using SELECT commands in Tivoli StorageManager scripts . . . . . . . . . . . 788Querying the SQL activity summary table . . . 789Creating output for use by another application 790

Using the Tivoli Storage Manager activity log . . 790Requesting information from the activity log 791Setting a retention period for the activity log 792Setting a size limit for the activity log . . . . 792

Monitoring Tivoli Storage Manager accountingrecords . . . . . . . . . . . . . . . 793Logging IBM Tivoli Storage Manager events toreceivers . . . . . . . . . . . . . . . 794

Enabling and disabling events . . . . . . . 795Beginning and ending event logging . . . . 796Logging events to the IBM Tivoli StorageManager server console and activity log . . . 796Logging events to a file exit and a user exit . . 797Logging events to the Tivoli Enterprise Console 798Logging events to an SNMP manager . . . . 802Enterprise event logging: logging events toanother server . . . . . . . . . . . . 808Querying event logging . . . . . . . . . 809User exit and file exit receivers . . . . . . 810

Part 6. Protecting the server . . . 815

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

Secure Sockets Layer and Transport LayerSecurity communication . . . . . . . . . 818Administrative authority and privilege classes 819Setting up Secure Sockets Layer and TransportLayer Security . . . . . . . . . . . . 821

Securing the server console . . . . . . . . . 831Managing access to the server and clients . . . . 832

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

Managing passwords and logon procedures . . . 839Configuring a directory server for passwordauthentication . . . . . . . . . . . . 841Setting the policy for an LDAP-authenticatedpassword. . . . . . . . . . . . . . 843

Configuring the Tivoli Storage Manager serverto authenticate passwords with an LDAPdirectory server . . . . . . . . . . . 844Registering nodes and administrator IDs toauthenticate passwords with an LDAP directoryserver . . . . . . . . . . . . . . . 845Updating nodes and administrator IDs toauthenticate passwords with a directory server . 846Determining which nodes and administrator IDsare configured to authenticate with an LDAPserver . . . . . . . . . . . . . . . 847Modifying the default password expirationperiod for passwords that are managed by theTivoli Storage Manager server . . . . . . . 847Scenarios for authenticating passwords . . . . 850

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

Backing up the server database . . . . . . 854Protecting infrastructure setup files . . . . . 862

Client data protection . . . . . . . . . . 867Protecting the data that is in primary storagepools . . . . . . . . . . . . . . . 867Auditing storage pool volumes . . . . . . 872Fixing damaged files . . . . . . . . . . 881

Scenario: Protecting the database and storage pools 883Recovering the database and client data . . . . 885

Restoring the database . . . . . . . . . 886Restoring storage pools and storage poolvolumes . . . . . . . . . . . . . . 892Restoring and recovering an LDAP server . . . 899Audit the LDAP server . . . . . . . . . 900

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

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

Chapter 28. Replication of client nodedata . . . . . . . . . . . . . . . 905Automatic failover for data recovery overview . . 906Source and target node-replication servers. . . . 907

Replication server configurations . . . . . . 907Policy management for node replication . . . 909Node replication processing . . . . . . . 910

Planning for node replication . . . . . . . . 921Determining server database requirements fornode replication . . . . . . . . . . . 922Estimating the total amount of data to bereplicated. . . . . . . . . . . . . . 923Estimating network bandwidth required forreplication . . . . . . . . . . . . . 924Calculating the time that is required forreplication . . . . . . . . . . . . . 924Selecting a method for the initial replication . . 925

x IBM Tivoli Storage Manager for Oracle Solaris: Administrator's Guide

Scheduling incremental replication after theinitial replication . . . . . . . . . . . 927

Node replication restrictions . . . . . . . . 928Task tips for node replication . . . . . . . . 931

Change replication rules. . . . . . . . . 931Add and remove client nodes for replication 931Manage replication servers . . . . . . . . 932Validate a configuration and preview results 933Manage replication processing. . . . . . . 933Monitor replication processing and verify results 934

Setting up the default replication configuration . . 935Step 1: Setting up server-to-servercommunications . . . . . . . . . . . 936Step 2: Specifying a target replication server . . 939Step 3: Configuring client nodes for replication 940

Customizing a node replication configuration . . 942Changing replication rules . . . . . . . . 942Scenario: Converting to node replication fromimport and export operations . . . . . . . 948Adding and removing client nodes forreplication . . . . . . . . . . . . . 949Managing source and target replication servers 952

Verifying a node replication setup beforeprocessing . . . . . . . . . . . . . . 955Managing data replication . . . . . . . . . 956

Replicating data by command . . . . . . . 956Controlling throughput for node replication . . 961Disabling and enabling node replication . . . 964Managing replicated client-node data using thetarget replication server policies . . . . . . 968Purging replicated data in a file space . . . . 971Replicating client node data after a databaserestore. . . . . . . . . . . . . . . 971

Monitoring node replication processing andverifying results . . . . . . . . . . . . 973

Displaying information about node replicationsettings . . . . . . . . . . . . . . 973Displaying information about running andcompleted node replication processes . . . . 974Displaying the activity log of a replicationprocess . . . . . . . . . . . . . . 974Displaying summary records of replicationprocesses . . . . . . . . . . . . . . 975Measuring the effectiveness of a replicationconfiguration . . . . . . . . . . . . 975Measuring the effects of data deduplication onnode replication processing. . . . . . . . 975Retaining replication records . . . . . . . 976

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

Removing a node replication configuration . . . 978

Chapter 29. Disaster recoverymanager . . . . . . . . . . . . . 979Preparing for disaster recovery . . . . . . . 980Disaster recovery manager checklist . . . . . . 982Managing the Disaster Recovery Manager tasks 987The disaster recovery plan file. . . . . . . . 989

Breaking out a disaster recovery plan file . . . 989Structure of the disaster recovery plan file . . . 989

Example disaster recovery plan file . . . . . 991Querying defaults for the disaster recovery planfile . . . . . . . . . . . . . . . . 1008

Specifying defaults for the disaster recoveryplan file . . . . . . . . . . . . . . 1008Specifying defaults for offsite recovery mediamanagement . . . . . . . . . . . . 1012

Specifying recovery instructions for your site . . 1014Specifying information about your server andclient node machines . . . . . . . . . . 1016Specifying recovery media for client machines 1018Creating and storing the disaster recovery plan 1019

Storing the disaster recovery plan locally . . . 1020Storing the disaster recovery plan on a targetserver . . . . . . . . . . . . . . 1021

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

Displaying information about recovery planfiles . . . . . . . . . . . . . . . 1021Displaying the contents of a recovery plan file 1022Restoring a recovery plan file . . . . . . 1022Expiring recovery plan files automatically . . 1023Deleting recovery plan files manually . . . . 1023

Moving backup media for disaster recoveryoperations . . . . . . . . . . . . . . 1024

Moving copy storage pool and active-data poolvolumes offsite . . . . . . . . . . . 1026Moving copy storage pool and active-data poolvolumes onsite . . . . . . . . . . . 1028

Recovering from a disaster . . . . . . . . 1029Recovering the server scenario . . . . . . 1030Recovering the client scenario . . . . . . 1033

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

Automated SCSI library at the original andrecovery sites . . . . . . . . . . . . 1036Automated SCSI library at the original site anda manual SCSI library at the recovery site . . 1037Managing copy storage pool volumes andactive-data pool volumes at the recovery site . 1038

Chapter 30. Integrating disasterrecovery manager and nodereplication into your disasterrecovery strategy . . . . . . . . . 1041Plan for a disaster recovery strategy . . . . . 1042Tier 0: No disaster recovery capability. . . . . 1043Tier 1: Offsite vaulting from a single productionsite . . . . . . . . . . . . . . . . 1043Tier 2: Offsite vaulting with a recovery site . . . 1044Tier 3: Electronic vaulting of critical data . . . . 1044Tier 4: Active data management at peer sites . . 1045Tier 5: Synchronous replication . . . . . . . 1046Tier 6: Synchronous replication with coupling orclustering applications . . . . . . . . . . 1047

Part 7. Appendixes . . . . . . . 1049

Contents xi

|||

Appendix A. External mediamanagement interface description . . 1051CreateProcess call . . . . . . . . . . . 1051Processing during server initialization . . . . . 1052Processing for mount requests . . . . . . . 1052Processing for release requests . . . . . . . 1053Processing for batch requests . . . . . . . . 1053Error handling . . . . . . . . . . . . 1054Begin batch request . . . . . . . . . . . 1054End batch request . . . . . . . . . . . 1054Volume query request . . . . . . . . . . 1055Initialization requests . . . . . . . . . . 1056Volume eject request . . . . . . . . . . 1056Volume release request . . . . . . . . . . 1057Volume mount request . . . . . . . . . . 1058Volume dismount request . . . . . . . . . 1061

Appendix B. User exit and file exitreceivers . . . . . . . . . . . . . 1063Sample user exit declarations. . . . . . . . 1063

Sample user-exit program . . . . . . . . . 1065Readable text file exit (FILETEXTEXIT) format 1066

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

Notices . . . . . . . . . . . . . 1071Trademarks . . . . . . . . . . . . . 1073Privacy policy considerations. . . . . . . . 1073

Glossary . . . . . . . . . . . . . 1075

Index . . . . . . . . . . . . . . 1077

xii IBM Tivoli Storage Manager for Oracle Solaris: 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 Oracle Solaris 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 Oracle Solaris: 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.

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 768

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.

© Copyright IBM Corp. 1993, 2014 xv

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 882

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 970

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.

xvi IBM Tivoli Storage Manager for Oracle Solaris: Administrator's Guide

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 658

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.

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 data

New for IBM Tivoli Storage Manager Version 7.1 xvii

|

|||

||

|

|

|

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

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.

xviii IBM Tivoli Storage Manager for Oracle Solaris: Administrator's Guide

|

|

|

|||

Part 1. Tivoli Storage Manager basics

© Copyright IBM Corp. 1993, 2014 1

2 IBM Tivoli Storage Manager for Oracle Solaris: 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 469Related 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 page473.

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

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


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

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

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

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

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


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 serverkeeps track of when files need to be backed up. Only files that change are backedup, and then entire files are backed up, so that the server does not need toreference base versions of the files. This means savings in resources, including thenetwork and storage.

If you choose, you can force full backup by using the selective backup function ofa client in addition to the incremental backup function. You can also choose to useadaptive subfile backup, in which the server stores the base file (the completeinitial backup of the file) and subsequent subfiles (the changed parts) that dependon the base file.Related reference:“Data protection operations” on page 7

Storage-pool and server-inventory backupsTivoli Storage Manager protects client data through storage pool and serverinventory back ups.

Client backup, archive, and space-managed data in primary storage pools can bebacked up to copy storage pools. You can also copy active versions of clientbackup data from primary storage pools to active-data pools. The server canautomatically access copy storage pools and active-data pools to retrieve data.

The server inventory, which includes the database and recovery log, isautomatically backed up to protect critical data. The server inventory is key to theserver's ability to track client data in server storage and recover from a disaster.

These backups can become part of a disaster recovery plan, created automaticallyby the disaster recovery manager.

If you enable node replication, client data can be replicated from one server, asource replication server to another server, a target replication server. Nodereplication allows clients to recover data from the target server if the source serveris unavailable.Related concepts:


Chapter 28, “Replication of client node data,” on page 905“Client data protection” on page 867“Protecting the database and infrastructure setup files” on page 853Related tasks:Chapter 29, “Disaster recovery manager,” on page 979

How client data is storedTivoli Storage Manager policies are rules that determine how client data is storedand managed. The rules include where the data is initially stored, how manybackup versions are kept, how long archive copies are kept, and more.

Policy-based data management helps you focus more on the business requirementsfor protecting data and less on managing storage devices and media. To implementbusiness requirements, which are sometimes called the service level agreement(SLA), you define storage policies.

For example, policy can define the following key data requirements for a businessorganization:v The data to back up and archivev The location for storing the datav The number of versions of data to retainv The time period to retain the data in storage

Policy can also be used to migrate data objects automatically from one storage poolto another. For example, you can initially back up data to storage media such asdisk so that the data is quickly restorable. During off-peak hours, you can migratethe data to less-expensive media such as tape.

Depending on your business needs, you can have one policy or many. Within abusiness organization, for example, different departments with different types ofdata can have their own customized storage management plans.

Administrators define policies on the Tivoli Storage Manager server. Client nodesare assigned to a policy domain. Policies can be updated, and the updates can beretroactively applied to data that is already managed.Related concepts:Chapter 13, “Implementing policies for client data,” on page 469Related tasks:Chapter 10, “Managing storage pools and volumes,” on page 245Chapter 20, “Managing the database and recovery log,” on page 619


Tivoli Storage Manager data management

ibmtivoli storage manager for oracle solaris version 7.1€¦ · defining device classes for...

Documents