tivoli storage manager for copy services - ibm...

Tivoli® Storage Manager

for Advanced Copy Services

Installation and User’s Guide for DB2 UDB

Version 5.3

GC32-1780-00

��

Note

Before using this information and the product it supports, read the general information under “Notices” on page 69.

First Edition (March 2006)

This edition applies to Version 5 Release 3 Modification 3 of IBM Tivoli Storage Manager for Advanced Copy

Services for DB2 UDB (product number 5608-ACS) and to any subsequent releases until otherwise indicated in new

editions or technical newsletters. Make sure you are using the correct edition for the level of the product.

Order publications through your sales representative or branch office serving your locality.

Your feedback is important in helping to provide the most accurate and high-quality information. If you have

comments about this book or any other IBM Tivoli Storage Manager documentation, please see “Contacting IBM

Software Support” on page 67.

© Copyright International Business Machines Corporation 2000, 2006. All rights reserved.

US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract

with IBM Corp.

Contents

About this guide . . . . . . . . . . . v

Who should read this guide . . . . . . . . . v

Publications . . . . . . . . . . . . . . v

IBM Tivoli Storage Manager library . . . . . v

Related publications . . . . . . . . . . vi

Accessing terminology online . . . . . . . viii

Accessing publications online . . . . . . . viii

Ordering publications . . . . . . . . . viii

Tivoli Technical Training . . . . . . . . . viii

Support information . . . . . . . . . . . ix

IBM Tivoli Storage Manager Web site . . . . . ix

IBM Tivoli Storage Manager for Advanced Copy

Services for DB2 UDB Web site . . . . . . . ix

Conventions used in this book . . . . . . . . ix

Typeface conventions . . . . . . . . . . ix

Chapter 1. Introducing ACS for DB2

UDB . . . . . . . . . . . . . . . . 1

Key features . . . . . . . . . . . . . . 1

Multi-partition DB2 UDB database support . . . 1

Centralized configuration via the Configuration

Wizard . . . . . . . . . . . . . . . 1

Integration with Tivoli Storage Manager client

command-line interface . . . . . . . . . . 1

Multiple backup host support . . . . . . . 2

Multiple snapshot backups . . . . . . . . 2

Policy-based management of snapshot backups . . 2

Additional features . . . . . . . . . . . . 2

DB2 UDB database backup . . . . . . . . 2

DB2 UDB database restore . . . . . . . . . 3

Incremental FlashCopy backup and restore . . . 3

Scheduled backups . . . . . . . . . . . 3

Compatibility with Tivoli Storage Manager . . . 3

IBM Subsystem Device Driver (SDD) support . . 3

ACS for DB2 UDB on HACMP . . . . . . . 4

File system consistency check . . . . . . . . 4

Globalization support . . . . . . . . . . 4

Chapter 2. ACS for DB2 UDB Concepts 5

Process concepts . . . . . . . . . . . . . 5

Federated backup . . . . . . . . . . . . 5

Federated restore . . . . . . . . . . . . 5

Database concepts . . . . . . . . . . . . 5

Configuration name . . . . . . . . . . . 5

Multi-partition database . . . . . . . . . 5

Single partition database . . . . . . . . . 6

File concepts . . . . . . . . . . . . . . 6

Node configuration file (db2nodes.cfg) . . . . . 6

User LUN file . . . . . . . . . . . . . 6

Metadata file . . . . . . . . . . . . . 7

Host concepts . . . . . . . . . . . . . . 7

Backup System . . . . . . . . . . . . 7

Production System . . . . . . . . . . . 7

Node concepts . . . . . . . . . . . . . . 7

Backup worker node . . . . . . . . . . . 7

DB2 worker node . . . . . . . . . . . . 8

Agent node . . . . . . . . . . . . . . 8

Target node . . . . . . . . . . . . . . 8

Master node . . . . . . . . . . . . . 8

Chapter 3. Installing ACS for DB2 UDB 9

1. Hardware and software requirements . . . . . 9

Backup host requirements . . . . . . . . . 9

Production host requirements . . . . . . . 12

2. Install the client . . . . . . . . . . . . 14

3. Install ACS for DB2 UDB . . . . . . . . . 15

Chapter 4. Configuring ACS for DB2

UDB . . . . . . . . . . . . . . . . 17

1. Planning for DB2 UDB backups . . . . . . . 17

2. Set up policy and nodes on the Tivoli Storage

Manager server . . . . . . . . . . . . . 18

3. Set up target nodes for communication . . . . 20

4. Set up the disk storage subsystem . . . . . . 21

Subsystem Device Driver configurations . . . . 23

5. Validate the DB2 UDB setup . . . . . . . . 24

6. Launch the Configuration Wizard . . . . . . 24

Chapter 5. Planning your DB2 UDB

backups . . . . . . . . . . . . . . 25

Backup process overview . . . . . . . . . . 25

Backup destination . . . . . . . . . . . . 26

Local disks . . . . . . . . . . . . . 26

Tivoli Storage Manager . . . . . . . . . 28

Scheduled (automated) backup . . . . . . . . 28

Example 1 . . . . . . . . . . . . . . 29

Example 2 . . . . . . . . . . . . . . 29

Example 3 . . . . . . . . . . . . . . 30

Incremental backup . . . . . . . . . . . . 30

Preview your backup settings . . . . . . . . 31

Example 1 . . . . . . . . . . . . . . 31

Example 2 . . . . . . . . . . . . . . 32

Chapter 6. Planning your DB2 UDB

restores . . . . . . . . . . . . . . 33

Restore process overview . . . . . . . . . . 33

Restoring from local disks . . . . . . . . . 33

Example 1 . . . . . . . . . . . . . . 34

Example 2 . . . . . . . . . . . . . . 34

Example 3 . . . . . . . . . . . . . . 34

Example 4 . . . . . . . . . . . . . . 35

Restoring from the Tivoli Storage Manager server 36

Example . . . . . . . . . . . . . . 36

Point in time restore . . . . . . . . . . . 36

Example . . . . . . . . . . . . . . 37

Chapter 7. Commands . . . . . . . . 39

Backup DB2udb . . . . . . . . . . . . . 39

Backup DB2udb Syntax . . . . . . . . . 40

© Copyright IBM Corp. 2000, 2006 iii

Backup DB2udb Parameters . . . . . . . . 40

Query DB2config . . . . . . . . . . . . 41

Query DB2config Syntax . . . . . . . . . 41

Query DB2config Parameters . . . . . . . 41

Query DB2udb . . . . . . . . . . . . . 42

Query DB2udb Syntax . . . . . . . . . . 42

Query DB2udb Parameters . . . . . . . . 42

Query Systeminfo . . . . . . . . . . . . 43

Query Systeminfo Syntax . . . . . . . . . 43

Query Systeminfo Parameters . . . . . . . 43

Restore DB2udb . . . . . . . . . . . . . 44

Restore DB2udb Syntax . . . . . . . . . 45

Restore DB2udb Parameters . . . . . . . . 45

Withdraw DB2udb . . . . . . . . . . . . 46

Withdraw DB2udb Syntax . . . . . . . . 47

Withdraw DB2udb Parameters . . . . . . . 47

Chapter 8. Messages . . . . . . . . . 49

Appendix A. Alternative procedures . . 63

Configuring system options files to the same server 63

ba/bin Directory . . . . . . . . . . . 63

api/bin Directory . . . . . . . . . . . 63

Configuring multiple server stanzas . . . . . . 64

Restoring hdisks for SDD . . . . . . . . . . 64

Appendix B. Support information . . . 65

Searching knowledge bases . . . . . . . . . 65

Searching the information center . . . . . . 65

Searching the Internet . . . . . . . . . . 65

Obtaining fixes . . . . . . . . . . . . . 65

Receiving weekly support updates . . . . . . 66

Contacting IBM Software Support . . . . . . . 67

Determining the business impact . . . . . . 67

Describing problems and gathering information 68

Submitting problems . . . . . . . . . . 68

Notices . . . . . . . . . . . . . . 69

Trademarks . . . . . . . . . . . . . . 70

Index . . . . . . . . . . . . . . . 73

iv

About this guide

IBM Tivoli Storage Manager for Advanced Copy Services for DB2 UDB is referred to as

ACS for DB2 UDB throughout this book. ACS for DB2 UDB supersedes the product,

Data Protection for Enterprise Storage Server® for DB2 UDB.

ACS for DB2 UDB is a comprehensive storage management software application. It

uses advanced copy services to perform online backups and local restore of DB2

Universal Database Enterprise Server Edition databases to Tivoli Storage Manager

server storage. This publication explains how to install, configure, and use ACS for

DB2 UDB.

Tivoli Storage Manager is a client-server licensed product that provides storage

management services in a multi-platform computer environment.

Who should read this guide

The target audience for this publication are DB2 administrators, system installers,

system users, and system administrators.

In this book, it is assumed that you have an understanding of the following

applications:

v Tivoli Storage Manager server

v Tivoli Storage Manager backup-archive client

v Tivoli Storage Manager Application Program Interface

v IBM TotalStorage Enterprise Storage Server administration

v IBM TotalStorage DS6000 administration

v IBM TotalStorage DS8000 administration

v IBM TotalStorage SAN Volume Controller administration

v DB2 UDB database administration

It is also assumed that you have an understanding of the following operating

system:

v AIX®

Publications

This section lists related IBM Tivoli Storage Manager publications. It also describes

how to access Tivoli® publications online and how to order Tivoli publications.

IBM Tivoli Storage Manager library

The following documents are available in the IBM Tivoli Storage Manager library:

v IBM Tivoli Storage Manager for UNIX and Linux Backup-Archive Clients Installation

and User’s Guide

Provides information for an end-user to install, configure, and use the Tivoli

Storage Manager client on UNIX and Linux operating systems.

v IBM Tivoli Storage Manager for AIX Administrator’s Guide

Provides concepts and procedures for configuring and customizing the Tivoli

Storage Manager server on AIX operating systems.

v IBM Tivoli Storage Manager for AIX Administrator’s Reference

© Copyright IBM Corp. 2000, 2006 v

Provides details about administrative commands, server options, and server

utilities for Tivoli Storage Manager server on AIX operating systems.

v IBM Tivoli Storage Manager Messages

Provides explanations and suggested actions for messages issued by the Tivoli

Storage Manager server program for storage management services, the

administrative client graphical user interface, administrative command line

client, data protection clients, and backup-archive client.

v IBM Tivoli Storage Manager: Problem Determination Guide

This guide describes how to diagnose problems with Tivoli Storage Manager.

v IBM Tivoli Storage Manager Using the Application Program Interface

Provides information to help you add Tivoli Storage Manager application

program interface calls to an existing application and to write programs with

general-use program interfaces that obtain the services of Tivoli Storage

Manager.

v IBM Tivoli Storage Manager for SAN for AIX Storage Agent User’s Guide

Provides an overview of LAN-free data transfer and detailed explanations about

configuring and using the Tivoli Storage Manager client, storage agent, and

server.

Related publications

The following IBM publications provide additional information.

v IBM DB2 UDB Command Reference Version 8

Provides information about using system commands, the operation of the

command line processor, using SQL statements from the command line, and

descriptions for all the database manager commands.

v IBM DB2 UDB Administration Guide: Planning Version 8

Provides an overview of database concepts and information about issues such as

logical and physical database design.

v IBM DB2 UDB Administration Guide: Implementation Version 8

Provides database administration information on implementation issues such as

creating databases and related database objects, altering databases and related

database objects, controlling database access, and auditing databases..

v IBM DB2 UDB Administration Guide: Performance Version 8

Provides information on product architecture and processes, performance issues

relating to both applications and the database environment, the SQL compiler,

the SQL explain facility, operational performance, the governor, scaling your

configuration, the redistribution of data, benchmarking, and configuring.

v IBM TotalStorage DS6000 Introduction and Planning Guide

This publication provides an overview of the IBM TotalStorage DS6000, and

provides the feature codes for ordering standard and optional features. It also

provides planning guidelines for DS6000 installation and configuration.

v IBM TotalStorage DS6000 Host Systems Attachment Guide

This guide provides information about:

– Attaching the IBM DS6000 to an open-systems host with Small Computer

System Interface (SCSI) adapters.

– Attaching the DS6000 to an open-systems host with fibre-channel adapters.

– Connecting IBM Enterprise Systems Connection ESCON cables to an IBM

S/390 and IBM (zSeries) host systems.

vi

– Connecting IBM Enterprise Systems Fibre Connection (FICON) cables to an

S/390 and zSeries host systems.v IBM TotalStorage DS6000 Command-Line Interface User’s Guide

This guide introduces the IBM TotalStorage DS command-line interfaces (CLI). It

also provides command syntax and reference information for commands that

can be used through the IBM TotalStorage DS6000 Command Line Interfaces.

v IBM TotalStorage DS8000 Introduction and Planning Guide

This publication provides an overview of the IBM TotalStorage DS8000, and

provides the feature codes for ordering standard and optional features. It also

provides planning guidelines for DS8000 installation and configuration.

v IBM TotalStorage DS8000 User’s Guide

This publication provides the procedures for using the IBM TotalStorage DS8000.

It includes an overview of the DS8000 and guidelines for:

– Operating the DS8000.

– Operating the Hardware Management Console.

– Using optional software for the DS8000.

– Migrating data to the DS8000.

– Analyzing problems.

– Disaster Recovery.v IBM TotalStorage DS8000 Host Systems Attachment Guide

This guide provides information about:

– Attaching the IBM DS8000 to an open-systems host with Small Computer

System Interface (SCSI) adapters.

– Attaching the DS8000 to an open-systems host with fibre-channel adapters.

– Connecting IBM Enterprise Systems Connection ESCON cables to an IBM

S/390 and IBM (zSeries) host systems.

– Connecting IBM Enterprise Systems Fibre Connection (FICON) cables to an

S/390 and zSeries host systems.v IBM TotalStorage SAN Volume Controller Configuration Guide

Provides information about how to configure the SAN Volume Controller.

v IBM TotalStorage SAN Volume Controller Configuration Guide Supplement (VSS)

Provides information about how to install and use Microsoft Volume Shadow

Copy service with the SAN Volume Controller.

v IBM TotalStorage SAN Volume Controller Planning Guide

This publication introduces the IBM TotalStorage SAN Volume Controller, its

components and its features. It also provides planning guidelines for installing

and configuring the SAN Volume Controller.

v CIM Agent and Console for IBM TotalStorage SAN Volume Controller

Provides license information for IBM TotalStorage Common Information Model

Agent.

v IBM TotalStorage SAN Volume Controller CIM Agent Developer’s Reference

This Guide helps developers retrieve and abstract CIM Agent object classes and

properties. This will help developers to use object classes and models to create

copy services and LUN masking.

v HACMP Smart Assist for DB2 User's Guide

This publication helps system administrators and customer engineers responsible

for planning and configuring an HACMP high-availability environment for DB2.

v High Availability Cluster Multi-Processing for AIX 5L Planning and Installation Guide

About this guide vii


for planning and installing an HACMP cluster.

v High Availability Cluster Multi-Processing for AIX Administration Guide


for configuring, managing, and troubleshooting an HACMP cluster.

Accessing terminology online

The Tivoli Software Glossary includes definitions for many of the technical terms

related to Tivoli software. The Tivoli Software Glossary is available at the following

Tivoli software library Web site:

http://publib.boulder.ibm.com/tividd/glossary/tivoliglossarymst.htm

The IBM Terminology Web site consolidates the terminology from IBM product

libraries in one convenient location. You can access the Terminology Web site at the

following Web address:

http://www.ibm.com/ibm/terminology

Accessing publications online

IBM® posts publications for this and all other Tivoli products, as they become

available and whenever they are updated, to the Tivoli software information center

Web site. Access the Tivoli software information center by first going to the Tivoli

software library at the following Web address:

http://www.ibm.com/software/tivoli/library/

Scroll down and click the Product manuals link. In the Tivoli Technical Product

Documents Alphabetical Listing window, click the <Tivoli Storage Manager> link

to access the product library at the Tivoli software information center.

Note: If you print PDF documents on other than letter-sized paper, set the option

in the File → Print window that allows Adobe Reader to print letter-sized

pages on your local paper.

Ordering publications

You can order many Tivoli publications online at the following Web site:

http://www.elink.ibmlink.ibm.com/public/applications/publications/cgibin/pbi.cgi

You can also order by telephone by calling one of these numbers:

v In the United States: 800-879-2755

v In Canada: 800-426-4968

In other countries, contact your software account representative to order Tivoli

publications.

Tivoli Technical Training

For Tivoli technical training information, refer to the following IBM Tivoli

Education Web site:

http://www.ibm.com/software/tivoli/education

viii

http://publib.boulder.ibm.com/tividd/glossary/tivoliglossarymst.htm

http://www.ibm.com/ibm/terminology

http://www.ibm.com/software/tivoli/library/



http://www.ibm.com/software/tivoli/education

Support information

If you have a problem with your IBM software, you want to resolve it quickly. IBM

provides the following ways for you to obtain the support you need:

v Searching knowledge bases: You can search across a large collection of known

problems and workarounds, Technotes, and other information.

v Obtaining fixes: You can locate the latest fixes that are already available for your

product.

v Contacting IBM Software Support: If you still cannot solve your problem, and

you need to work with someone from IBM, you can use a variety of ways to

contact IBM Software Support.

For more information about these three ways of resolving problems, see

Appendix B, “Support information,” on page 65.

IBM Tivoli Storage Manager Web site

Technical support information and publications are available at the following

address: http://www.ibm.com/software/sysmgmt/products/support/IBMTivoliStorageManager.html

By accessing the Tivoli Storage Manager home page, you can access subjects that

interest you. You can also keep up-to-date with the newest Tivoli Storage Manager

product information.

IBM Tivoli Storage Manager for Advanced Copy Services for

DB2 UDB Web site

The IBM Tivoli Storage Manager for Advanced Copy Services for DB2 UDB Web

site contains a knowledge base of articles and information related to backup and

restore issues. Access this information at:

http://www.ibm.com/software/sysmgmt/products/support/IBMTivoliStorageManagerforAdvancedCopyServices.html

Conventions used in this book

This guide uses several conventions for special terms and actions, operating

system-dependent commands and paths.

Typeface conventions

This guide uses the following typeface conventions:

Bold

v Commands, keywords, authorization roles, or other information that you

must use.

v Example: Log on to the server as root user.

italics

v Values or variables that you must provide.

v Emphasized words and phrases.

v Example: The node name of the production node and backup node must not

be the same.

bold italics

About this guide ix

http://www.ibm.com/software/sysmgmt/products/support/IBMTivoliStorageManager.html




v Options and parameters.

v Example: Specify the value for the compression option.

monospace

v Directories, parameters, URLs, and output examples.

v Example: The product is installed in the /usr/tivoli/tsm/client/ba/bin

directory.

UPPER CASE

v Environment variables associated with Tivoli Storage Manager, operating

systems, or DB2 UDB.

v Example: Make sure the DSM_DIR environment variable is set correctly.

x

Chapter 1. Introducing ACS for DB2 UDB

ACS for DB2 UDB minimizes the impact of performing backups of DB2 UDB

databases using Tivoli Storage Manager on database server systems. ACS for DB2

UDB off-loads the transfer of backup data from a production database server to a

backup server. The DB2 UDB database must reside on storage subsystem volumes.

ACS for DB2 UDB features high-efficiency backup and recovery of business-critical

applications. This feature minimizes backup-related downtime and user disruption

on the Production System host.

Key features

These key features are available with ACS for DB2 UDB:

v Multi-partition DB2 UDB database support

v Centralized configuration via the Configuration Wizard

v Integration with Tivoli Storage Manager client command-line interface

v Multiple backup host support

v Multiple snapshot backups

v Policy-based management of snapshot backups

This section describes key features of ACS for DB2 UDB.

Multi-partition DB2 UDB database support

ACS for DB2 UDB provides the ability to back up and restore a DB2 UDB database

that is partitioned across multiple hosts. This type of multi-partition database

consists of multiple logical DB2 UDB database partitions distributed across one or

more hosts running on AIX operating systems. Database operations are performed

concurrently across all database partitions, thus allowing very large databases to be

backed up and restored more efficiently. ACS for DB2 UDB performs a federated

backup of a distributed multi-partition database from a single end user interface.

See “Multi-partition database” on page 5 for more detailed information.

Centralized configuration via the Configuration Wizard

The Configuration Wizard (launched via the Tivoli Storage Manager Java GUI)

provides a centralized interface from which to configure DB2 UDB, Tivoli Storage

Manager, and storage subsystem settings. Instead of manually setting options and

values in a setup file, this GUI utility guides you through each step of the

configuration process and prompts you for required information. These

configuration settings become represented (like an alias) by a configuration name

that you specify in the Configuration Wizard. The internal validation checking of

the Configuration Wizard prevents incorrect information from being specified. As a

result, potential configuration mistakes are corrected early in the setup process.

Use the Configuration Wizard after setting up your other applications as described

in Chapter 4, “Configuring ACS for DB2 UDB,” on page 17.

Integration with Tivoli Storage Manager client command-line

interface

ACS for DB2 UDB uses the Tivoli Storage Manager backup-archive client

command line interface exclusively. This integration also makes ACS for DB2 UDB

more reliant on backup-archive client options. See Chapter 7, “Commands,” on

page 39

© Copyright IBM Corp. 2000, 2006 1

for detailed information about commands and options. In addition, ACS

for DB2 UDB messages use the client message prefix ANS. A list of ACS for DB2

UDB messages is available in Chapter 8, “Messages,” on page 49.

Multiple backup host support

ACS for DB2 UDB supports environments that contain multiple backup hosts.

These multiple backup hosts off-load the backup of the DB2 UDB database from

the Production System to the backup hosts. Multiple backup hosts not only limit

downtime for the Production System during backup processing but can also serve

as part of a comprehensive disaster recovery plan. See “Backup System” on page 7

for more information.

Multiple snapshot backups

ACS for DB2 UDB allows both active and inactive snapshot backups to exist

simultaneously on local disks and on Tivoli Storage Manager storage. This

provides extensive coverage of your backed up data and assists in overall backup

and disaster recovery planning. See “Point in time restore” on page 36 for an

example of how multiple snapshot backups can be used to complement a backup

strategy.

Policy-based management of snapshot backups

DB2 UDB databases backed up with ACS for DB2 UDB are managed through

Tivoli Storage Manager server policy. This provides flexibility when planning the

number of backups to maintain on both local disks and Tivoli Storage Manager

server storage. It also provides the opportunity for specialized policies for each

storage destination. “Local disks” on page 26 and “Tivoli Storage Manager” on

page 28 describe how Tivoli Storage Manager server policy affects these backup

destinations. In addition, “2. Set up policy and nodes on the Tivoli Storage

Manager server” on page 18 provides detailed instructions on how to set up your

policy.

Additional features

These features are also available with ACS for DB2 UDB:

v Back up DB2 UDB databases to local storage subsystem disks and Tivoli Storage

Manager server storage with minimal impact and downtime on the production

DB2 UDB database server

v Restore DB2 UDB databases from local storage subsystem disks and Tivoli

Storage Manager server storage to a host on your Production System

v Incremental FlashCopy backup and restore

v Schedule backup operations

v Compatibility with Tivoli Storage Manager Media Management functions

v Support IBM Subsystem Device Driver (SDD) functions

v Globalization support

This section describes additional features of ACS for DB2 UDB.

DB2 UDB database backup

ACS for DB2 UDB uses snapshot capabilities of storage subsystems, such as the

incremental FlashCopy feature available with the DS and Enterprise Storage Server

family of storage subsystems, to create a point-in-time copy of database volumes

from a DB2 UDB host on the Production System. The copied database volumes can

then be backed up to Tivoli Storage Manager server storage by one or more

2

backup hosts on the Backup System. Because the Backup System performs most of

the processing, the production host can dedicate processor time to other

applications. This greatly reduces any backup-related performance impact on the

Production System.

You can also perform a FlashCopy backup of multiple DB2 UDB databases. These

databases can reside on either a single production host or on multiple production

hosts in the Production System.

See Chapter 5, “Planning your DB2 UDB backups,” on page 25 for more detailed

information.

DB2 UDB database restore

ACS for DB2 UDB can restore a single partition on a host, all partitions on a host,

or the entire DB2 UDB database from any version available on storage subsystem

disks or from Tivoli Storage Manager server storage. See Chapter 6, “Planning your

DB2 UDB restores,” on page 33 for more detailed information. You can also restore

DB2 UDB data to a state that existed at a specified point in time. See “Point in

time restore” on page 36 for an example of this type of restore.

Incremental FlashCopy backup and restore

ACS for DB2 UDB uses the Enterprise Storage Server incremental FlashCopy

feature to create a point in time copy of a DB2 UDB database. This improves

performance as the background copy between the Enterprise Storage Server Source

Volumes and Target Volumes is made without having to copy all the tracks from

the Source Volumes to the Target Volumes. Enterprise Storage Server incremental

FlashCopy applies to the storage hardware level copy (the FlashCopy made

between the Source Volumes and Target Volumes) and does not apply to the

application level copy (the copy of the database that is backed up to the Tivoli

Storage Manager server).

See “Incremental backup” on page 30 for more detailed information.

Scheduled backups

You can schedule automated DB2 UDB backups from the Tivoli Storage Manager

server. You can select when the backups occur without waiting for off-peak hours

or maintenance downtime. Scheduled backups can play an important role in your

overall backup strategy. See “Scheduled (automated) backup” on page 28 for more

detailed information.

Compatibility with Tivoli Storage Manager

All Tivoli Storage Manager storage devices and media management capabilities are

available to ACS for DB2 UDB. You can share the devices used for other backups

or give DB2 UDB exclusive use of certain devices and media. ACS for DB2 UDB

also supports media and tape management for off-site vaulting.

IBM Subsystem Device Driver (SDD) support

ACS for DB2 UDB provides support for IBM SDD Version 1.6.0 (or later). SDD

resides on the host servers (Production System and Backup System) with the native

device driver for the storage subsystem. SDD uses redundant connections between

the host server and disk storage to provide enhanced performance through I/O

Chapter 1. Introducing ACS for DB2 UDB 3

access path balancing and data availability. Refer to your SDD documentation for

further information. See “Subsystem Device Driver configurations” on page 23 for

supported SDD configurations.

ACS for DB2 UDB on HACMP

ACS for DB2 UDB can be set up to operate in a High Availability Cluster

Multi-Processing (HACMP) environment. Refer to your HACMP and DB2 UDB

documentation for information about setting up and administrating DB2 UDB in

an HACMP environment. See “Related publications” on page vi for a brief list of

available publications.

File system consistency check

ACS for DB2 UDB backup processing can fail when file systems used in FlashCopy

processing are inconsistent. For example, inconsistency can occur when data files

or table space containers extend during FlashCopy processing, a JFS log logical

volume is striped across multiple volumes within the same volume group, or

changes are made to the file system during FlashCopy processing. Inode changes

can also create inconsistency such as when a file is created or deleted, or when a

write call causes a block to be allocated. To prevent backup failures, ACS for DB2

UDB checks for file system consistency on database volumes used in FlashCopy

processing. This is especially important when a database is backed up to storage

subsystem Target Volumes for use in local FlashCopy restore processing.

Globalization support

ACS for DB2 UDB messages, documentation, and Configuration Wizard can be

viewed in the following languages:

v Brazilian Portuguese

v French

v German

v Italian

v Japanese

v Korean

v Simplified Chinese

v Spanish

v Traditional Chinese

4

Chapter 2. ACS for DB2 UDB Concepts

This chapter describes concepts that are used to describe ACS for DB2 UDB

features and processes.

Process concepts

Federated backup

A federated backup is the back up of data that is distributed on multiple locations

independent of the physical location of the data. The locations can be on the same

system or on different systems. The data is managed by the application rather than

by a particular host. This type of backup maintains the logical view of the data as

it is viewed by the application. The backed up data is managed on the Tivoli

Storage Manager server as if it came from one name space.

Federated restore

A federated restore is a restore of data from backup storage to the same location

where it existed at the time of the original backup. As a result, maintaining file

system consistency is important for a federated restore to be successful.

Database concepts

Configuration name

This name represents a series of options and settings (like an alias) that defines the

DB2 UDB, Tivoli Storage Manager, and storage subsystem environment in which

ACS for DB2 UDB operates. You specify the configuration name in the

Configuration Wizard after all other configuration tasks are performed for that

specific database. The configuration name is important because it is the primary

name by which your database configuration is identified by ACS for DB2 UDB. For

example, the configuration name is required to perform these tasks:

v Back up a DB2 UDB database (backup db2udb).

v Confirm that the Configuration Wizard successfully transferred your settings to

the master node (query db2config).

v View a list of local and Tivoli Storage Manager snapshot backups (query

db2udb).

v View system and environment information (query systeminfo).

v Restore a DB2 UDB partition or database (restore db2udb).

v Withdraw persistent FlashCopy relationships for storage subsystem volumes

(withdraw db2udb).

The configuration name is also used to identify the user LUN file associated with

the database configured within the DB2 UDB database instance.

Multi-partition database

A multi-partition database consists of a Production System with one (or more) DB2

UDB hosts, with each host having one (or more) database partitions. Database

operations run simultaneously across all the partitions as if the database is a single

logical entity. This type of database environment is recommended when a database


is too large for a single host to manage operations efficiently. ACS for DB2 UDB

can perform the following tasks in a multi-partition database environment:

v Back up an entire DB2 UDB database to local disk (backupdestination=local),

Tivoli Storage Manager server storage (backupdestination=tsm), or to both

destinations (backupdestination=both).

v Restore an entire DB2 UDB database from local disk (backupdestination=local) or

Tivoli Storage Manager server storage (backupdestination=tsm).

v Restore a single partition of a DB2 UDB database from local disk

(backupdestination=local) or Tivoli Storage Manager server storage

(backupdestination=tsm).

v Restore all partitions of a DB2 UDB database (which reside on a single host)

from local disk (backupdestination=local) or Tivoli Storage Manager server

storage (backupdestination=tsm).

Single partition database

A single partition database consists of a Production System with a single host that

contains a DB2 UDB database with a single partition. The Backup System consists

of a single host. ACS for DB2 UDB can perform the following tasks in this

environment:

v Back up an entire DB2 UDB database to local disk (backupdestination=local),

Tivoli Storage Manager server storage (backupdestination=tsm), or to both

destinations (backupdestination=both).

v Restore an entire DB2 UDB database from local disk (backupdestination=local) or

Tivoli Storage Manager server storage (backupdestination=tsm).

File concepts

Node configuration file (db2nodes.cfg)

In a partitioned database system, the node configuration file (db2nodes.cfg)

contains configuration information for all database partitions that exist in a

database instance. This file is created and managed by DB2, not ACS for DB2 UDB,

and is required for Tivoli Storage Manager backup recovery tasks. This file is

backed up to the Tivoli Storage Manager server by ACS for DB2 UDB and is

available for restore in the event that the database instance is lost. Here is an

example of a node configuration file for hosts identified as adminhost, testhost, and

backuphost:

0 adminhost 0

1 testhost 1

2 backuphost 2

User LUN file

This file contains the set of LUNs and the host name(s) of the backup worker

node(s). These LUNs are dedicated backup Target Volumes and are statically

assigned to the backup host(s) for backup processing. There must be enough LUNs

specified in this file to contain the number of local backup versions defined in the

backup policy. For example, in the DB2 instance users, the database customers is

distributed over ten LUNs and the policy is defined to contain three local backup

versions. As a result, the LUN file must have thirty LUNs specified for the local

backups. The user creates this file on the host where the DB2 catalog resides. The

path to this file is specified in the Configuration Wizard.

6

Metadata file

A set of metadata is created for each DB2 database partition. This information is

gathered from the database partitions during backup processing and is distributed

to all participating DB2 worker nodes during restore processing to verify that the

hardware and volume configuration is correct. This metadata information is used

to recreate the Target Volume LUNs.

Host concepts

Backup System

The Backup System consists of one (or more) dedicated hosts (backup hosts) that

are used for performing ACS for DB2 UDB tasks. The main task of the Backup

System is to off-load the backup of the DB2 UDB database from the Production

System to the Backup System. The Backup System limits downtime for the

Production System by creating an instant point-in-time copy of data and making

this data available to the Backup System for functions such as verifying that the

data copy is consistent or optionally, backing up the data for long-term storage on

the Tivoli Storage Manager server. For the best performance results, use one

backup host for each production host in the Production System.

The Backup System is characterized by the following:

v The nodes that comprise the Backup System (except for the master node) are

considered backup worker nodes.

v You designate one of the hosts as the master node to coordinate all of the

backup and restore activities.

v As part of the Tivoli Storage Manager configuration, the nodes that comprise the

Backup System are also registered to the Tivoli Storage Manager server as agent

nodes.

Production System

The Production System consists of one (or more) distributed hosts participating in

the multi-partition database to be backed up. The data can be distributed over one

(or more) hosts while maintaining a single logical view of the data. ACS for DB2

UDB backs up the multi-partition database distributed over multiple hosts in a

manner that is consistent, has minimal impact on Production Database server

operations, and preserves the view of the data.

The Production System is characterized by the following:

v The DB2 hosts that comprise the Production System are considered DB2 worker

nodes.

v As part of the Tivoli Storage Manager configuration, the nodes that comprise the

Production System are also registered to the Tivoli Storage Manager server as

agent nodes.

Node concepts

Backup worker node

All of the hosts that compose the Backup System (other than the master node) are

considered backup worker nodes. These nodes perform the backup and restore

tasks for the databases partitions associated with their host.

Chapter 2. ACS for DB2 UDB Concepts 7

DB2 worker node

All of the DB2 hosts that compose the Production System are considered DB2

worker nodes. These nodes participate in the backup and restore tasks for the

databases partitions associated with their host.

Agent node

An agent node is a client node (host) on the Backup System and the Production

System that has allowed a target node to perform backup and restore operations

on its behalf. You register the agent nodes when setting up the Tivoli Storage

Manager server. You specify the agent node with the Configuration Wizard during

setup.

Target node

The target node (multinode or asnode) is defined on the Tivoli Storage Manager

server in order to manage the back up and restore of the distributed multi-host,

multi-partition database as a single logical federated operation. It represents a DB2

UDB database instance and all of the agent nodes (hosts) registered on the Backup

System and the Production System that are available for ACS for DB2 UDB

processing. Although all of the agent nodes (hosts) in the ACS for DB2 UDB

environment are registered to the Tivoli Storage Manager server, communication

between ACS for DB2 UDB and the Tivoli Storage Manager server is performed by

this target node. As a result, backed up data on Tivoli Storage Manager server

storage is managed by a single node (target node) instead of several nodes.

The master node operates as an target node to coordinate activity between the

Production System nodes and the Backup System nodes. The target node must

have authority to delete its own backup files from the Tivoli Storage Manager

server. The target node and associated agent nodes are specified in the

Configuration Wizard. Each agent node is defined as either a DB2 worker node or

a backup worker node and associated with the corresponding DB2 host or backup

host.

Master node

The master node distributes tasks among all the agent nodes and synchronizes all

activities during backup and restore processing. This node is specified in the

Configuration Wizard during configuration. The master node is characterized by

the following:

v It is a target node.

v It must be a host physically located on the Backup System.

v It is the node from which all backup, restore, and query operations are issued.

v It is also the node contacted by the Tivoli Storage Manager server during a

scheduled backup.

8

Chapter 3. Installing ACS for DB2 UDB

Attention

For current information concerning installation of ACS for DB2 UDB, refer to

the README.ACSDB2 file shipped on the product installation media.

This chapter provides information about hardware and software requirements as

well as instructions on how to install the Tivoli Storage Manager backup-archive

client and ACS for DB2 UDB. This information is presented in three sections:

1. Hardware and software requirements

This section describes the hardware and software levels required by ACS

for DB2 UDB for each host. Note that there are different requirements for

backup hosts and production hosts.

2. Install the client

This section describes how to install the Tivoli Storage Manager

backup-archive client filesets (required by ACS for DB2 UDB) on each host.

3. Install ACS for DB2 UDB

This section describes how to install ACS for DB2 UDB on each host.

ACS for DB2 UDB and other applications in your environment must be configured

after successful installation. See Chapter 4, “Configuring ACS for DB2 UDB,” on

page 17 for instructions.

1. Hardware and software requirements

Backup host requirements

Before installing ACS for DB2 UDB, make sure the following hardware and

software levels exist.

Backup host hardware

The following hardware must exist before installing ACS for DB2 UDB:

Table 1. Minimum hardware requirements for the Backup hosts.

Hardware Description Special Consideration

One (or

more)

workstations

pSeries To distribute the backup load for your

multi-partition databases, configure two (or

more) pSeries workstations for your Backup

System .


Table 1. Minimum hardware requirements for the Backup hosts. (continued)


One disk

storage

subsystem

One of the following disk

storage subsystems:

v IBM Enterprise Storage

Server Model Fxx

v IBM Enterprise Storage

Server Model 800

v IBM TotalStorage DS6000

v IBM TotalStorage DS8000

v IBM TotalStorage SAN

Volume Controller 2.1

The storage subsystem must be attached (via

SCSI or Fibre Channel) to each pSeries

workstation in the Backup System.

Enterprise Storage Server

The FlashCopy Version 2 feature

must be at a level expected to match

FlashCopy backup requirements.

IBM TotalStorage DS6000

Microcode level 6.0.0.438 (or later).



IBM TotalStorage SAN Volume Controller

Storage Engine 2145-4F2.

Disk space 6 MB None.

Memory 76 MB More memory is recommended.

Backup host software

The following software must exist on each dedicated host in the Backup System

before installing ACS for DB2 UDB:

Table 2. Minimum software requirements for the Backup hosts.

Software Version Special Consideration

AIX operating system1 One of the

following versions:

v 5.2 (32-bit or

64-bit)

v 5.3 (32-bit or

64-bit)

The following maintenance pack must be

installed:

v AIX 5.2: Maintenance Pack 52-004 (or

later).


later).


Copy Services

Command-Line Interface

(CLI)

2.3 (or later) Required on all the Backup System hosts

when using an IBM Enterprise Storage

Server Model Fxx or Model 800 disk

storage subsystem.

IBM Common Interface

Model (CIM) Agent for

DS Open (API)

5.1.0.25 (or later) Required for DS6000 or DS8000

environments only. Software can be

installed on the Backup System or on a

separate machine.

Pegasus Common

Interface Model (CIM)

Server and Base Providers

available on the Expansion

Pack CD for your level of

AIX operating system.

2.3.2.2 Filesets:

sysmgt.pegasus.cimserver.rte

sysmgt.pegasus.osbaseproviders

Secure Sockets Layer (SSL)

package available from

the AIX Toolbox for Linux

Applications for POWER

Systems CD.

Shipped with your

base operating

system software.

None.

10

Table 2. Minimum software requirements for the Backup hosts. (continued)


IBM Subsystem Device

Driver (SDD) with Host

Attachment Scripts.

v SDD: 1.6.0.2

v Scripts: 1.1.0.3

(or later)

Required for SAN Volume Controller

environment. Recommended for DS6000 or

DS8000 environment.

Tivoli Storage Manager

backup-archive client

Enterprise Storage

Server:

v 5.3.0 (32-bit)

DS6000, DS8000, or

SAN VC:

v 5.3.2 (32-bit)

Install on all the Backup System hosts. The

backup-archive client Image Plug-in Utility

must also be installed on all the Backup

System hosts.


API

Enterprise Storage

Server:

v 5.3.0 (32-bit)

DS6000, DS8000, or

SAN VC:

v 5.3.2.x (32-bit)

The Tivoli Storage Manager API is a

separate installation package that is part of

the backup-archive client package. ACS for

DB2 UDB requires that you install the

32-bit Tivoli Storage Manager API even

though you may operate your DB2 UDB

Server on a 64-bit AIX workstation.

1 The following AIX environments are supported:

v AIX 5.2 DB2 Production System with an AIX 5.2 Backup System



Note that an AIX 5.3 DB2 Production System with an AIX 5.2 Backup

System is NOT supported.


Production host requirements

Before installing ACS for DB2 UDB, make sure the following hardware and

software levels exist on each dedicated host in the Production System.

Production host hardware

The following hardware must exist before installing ACS for DB2 UDB:

Table 3. Minimum hardware requirements for the Production hosts


One workstation pSeries To create a multi-partition database

environment, the Production System must

contain one (or more) pSeries workstations

with each host containing one (or more)

database partitions.

One disk storage

subsystem

One of the

following disk

storage subsystems:

v IBM Enterprise

Storage Server

Model Fxx

v IBM Enterprise

Storage Server

Model 800

v IBM TotalStorage

DS6000

v IBM TotalStorage

DS8000

v IBM TotalStorage

SAN Volume

Controller 2.1

The storage subsystem must be attached

(via SCSI or Fibre Channel) to each pSeries

workstation in the Production System.


The FlashCopy Version 2 feature

must be at a level expected to

match FlashCopy backup

requirements.




Microcode level 6.0.500.46 (or

later).

IBM TotalStorage SAN Volume Controller

Storage Engine 2145-4F2.

Disk space 25 MB None.

Memory 128 MB More memory is recommended.

Production host software

The following software must exist before installing ACS for DB2 UDB:

Table 4. Minimum software requirements for the Production hosts


AIX operating system1 One of the

following versions:

v 5.2 (32-bit or

64-bit)

v 5.3 (32-bit or

64-bit)

The following maintenance pack must be

installed:


later).


later).


Copy Services

Command-Line Interface

(CLI)

2.3 (or later) Install on the Production System host

where the catalog node resides when using

an IBM Enterprise Storage Server Model

Fxx or Model 800 disk storage subsystem.

IBM Common Interface

Model (CIM) Agent for

DS Open (API)

5.1.0.25 (or later) Required for DS6000 or DS8000

environments only. Software can be

installed on the Production System or on a

separate machine.

12

Table 4. Minimum software requirements for the Production hosts (continued)


Pegasus Common

Interface Model (CIM)

Server and Base Providers

available on the Expansion

Pack CD for your level of

AIX operating system.

2.3.2.2 Filesets:

sysmgt.pegasus.cimserver.rte

sysmgt.pegasus.osbaseproviders

Secure Sockets Layer (SSL)

package available from

the AIX Toolbox for Linux

Applications for POWER

Systems CD.

Shipped with your

base operating

system software.

None.

IBM Subsystem Device

Driver (SDD) with Host

Attachment Scripts.

v SDD: 1.6.0.2

v Scripts: 1.1.0.3

(or later)

Required for SAN Volume Controller

environment. Recommended for DS6000 or

DS8000 environment.

DB2 UDB Server for AIX 8.2 All DB2 hosts participating in a partitioned

database must be installed on the same

version of AIX.


backup-archive client

Enterprise Storage

Server:

v 5.3.0 (32-bit)

DS6000, DS8000, or

SAN VC:

v 5.3.2 (32-bit)

Install on all the Production System hosts.

The backup-archive client Image Plug-in

Utility must also be installed on all the

Production System hosts.


API

Enterprise Storage

Server:

v 5.3.0 (32-bit)

DS6000, DS8000, or

SAN VC:

v 5.3.2.x (32-bit)

The Tivoli Storage Manager API is a

separate installation package that is part of

the backup-archive client package. ACS for

DB2 UDB requires that you install the

32-bit Tivoli Storage Manager API even

though you may operate your DB2 UDB

Server on a 64-bit AIX workstation.

1 The following AIX environments are supported:




Note that an AIX 5.3 DB2 Production System with an AIX 5.2 Backup

System is NOT supported.

Tivoli Storage Manager server Version 5.3 must be available over the network to all

Production System and Backup System hosts.


2. Install the client

Attention: Important! Follow this procedure to install the Tivoli Storage Manager

backup-archive client on each host in the Backup System and Production System.

Table 5. Tivoli Storage Manager client and API filesets

Fileset Name Description

tivoli.tsm.client.ba Installs Tivoli Storage Manager backup-archive

client common files, command-line interface,

GUI, and administrative client command-line

interface.

tivoli.tsm.client.api.32bit Installs the 32-bit API.

tivoli.tsm.client.msg.lang Installs the NL messages where lang is the

appropriate language code.

1. Insert the CD-ROM containing the client package into the CD-ROM drive.

2. Log on to the host as root user.

3. Type smitty install at the command prompt and press Enter.

4. Select Install and Update Software and press Enter.

5. Select Install and Update From ALL Available Software and press Enter.

6. At the INPUT device / directory for software prompt, press the F4 key and

select /dev/cd0 in the entry field and press Enter.

7. At the SOFTWARE to install prompt, press the F4 key. Select the Tivoli Storage

Manager filesets you want to install and press Enter.

8. Select the options you want and press Enter to begin the installation.

Note: Make sure you have installed the Tivoli Storage Manager 32-bit API (even

when operating in a 64-bit environment) as the 32-bit API is required by

ACS for DB2 UDB.

Attention

Repeat this procedure on each host in the Backup System and Production

System before installing ACS for DB2 UDB.

14

3. Install ACS for DB2 UDB

Attention: Important! Follow this procedure to install ACS for DB2 UDB on each

host in the Backup System and Production System.

Table 6. ACS for DB2 UDB filesets

Fileset Name Description

tivoli.tsm.client.hdw.acs.db2 Installs ACS for DB2 UDB code.

tivoli.tsm.client.hdw.acs.db2.books Installs ACS for DB2 UDB documentation.

tivoli.tsm.loc.client.hdw.acs.db2.ela Installs the ACS for DB2 UDB Electronic

License Agreement. You must accept the

agreement in order for ACS for DB2 UDB to

install.

1. Insert the CD-ROM containing the client package into the CD-ROM drive.

2. Log on to the host as root user.

3. Type smitty install at the command prompt and press Enter.

4. Select Install and Update Software and press Enter.

5. Select Install and Update From ALL Available Software and press Enter.

6. At the INPUT device / directory for software prompt, press the F4 key and

select /dev/cd0 in the entry field and press Enter.

7. At the SOFTWARE to install prompt, press the F4 key. Select the ACS for DB2

UDB filesets you want to install and press Enter.

8. Select the options you want. Make sure you set ACCEPT new license

agreements? to Yes. (The default is No). Press Enter to begin the installation.

Attention

Repeat this procedure on each host in the Backup System and Production

System. Once you have installed ACS for DB2 UDB on each host, proceed to

Chapter 4, “Configuring ACS for DB2 UDB,” on page 17 to set up your

production environment.


Chapter 4. Configuring ACS for DB2 UDB

This chapter describes the tasks you must perform to configure ACS for DB2 UDB

and provides examples for your reference. These tasks are:

1. Planning for DB2 UDB backups

2. Set up policy and nodes on the Tivoli Storage Manager server

3. Set up target nodes for communication

4. Set up the disk storage subsystem

v Subsystem Device Driver configurations5. Validate the DB2 UDB setup

6. Launch the Configuration Wizard

1. Planning for DB2 UDB backups

DB2 UDB hosts and partitions:

__ Locate the directory where the DB2 UDB server is installed. This path is

specified in the Configuration Wizard.

__ Identify the hosts where the database (to be configured) is distributed.

__ Determine the number of backup hosts dedicated to ACS for DB2 UDB

backup processing only. If you plan to back up data to the Tivoli Storage

Manager server, determine the number of database partitions to be backed

up by each backup host.

DB2 UDB target database:

__ The target database (Production System) to be backed up must be configured

on storage subsystem volumes.

DB2 UDB catalog and table spaces:

__ Note that the Configuration Wizard is launched on the host where the DB2

catalog resides.

__ Place DB2 User and System table space containers in one or more volume

groups on storage subsystem volumes. Place the system catalog table space

container (SYSCATSPACE) on a separate volume group consisting of storage

subsystem volumes configured for the catalog database partition. Temporary

table space containers MUST be placed on storage subsystem volumes. These

temporary table space containers are copied during FlashCopy processing.


DB2 UDB instance:

__ The DB2 UDB database instance must be available on the Production System.

The database instance name, password, and home directory are specified in

the Configuration Wizard.

__ Make sure root user is part of the DB2 SYSADM group. Issue this command

to locate the SYSADM group for your instance:

db2 get database manager configuration

Add root to the SYSADM group.

DB2 UDB and disk storage volume groups:

__ DB2 UDB user data, system data, and temporary data must reside on

Database Managed Storage (DMS) or System Managed Storage (SMS) table

spaces. DMS or SMS table spaces can be allocated on a Journaled File System

(JFS, JFS2) or on AIX raw devices only. JFS and raw volumes must be

configured on storage subsystem volumes.

__ When creating file systems for your database on volume groups with storage

subsystem volumes, make sure the JFS log is located on a single volume

within the volume group. The FlashCopy backup may fail if the JFS log is

spanned across multiple volumes within the volume group.

DB2 UDB recovery logs:

__ Keep the volume groups for recovery logs separate from the volume groups

for user data, system data, and temporary data. This ensures that the

recovery logs are not overwritten during a FlashCopy restore from local

storage subsystem volumes.

__ ACS for DB2 UDB does not back up recovery logs. Use the DB2 user exit

program (db2uext2.cdisk for example) for archiving and retrieving recovery

logs to or from the Tivoli Storage Manager server.

2. Set up policy and nodes on the Tivoli Storage Manager server

__ Step 1. Create a policy domain on the Tivoli Storage Manager server to be

used exclusively for DB2 UDB backups. For example, to create the

policy domain db2domain, issue this command

define domain db2domain

__ Step 2. Define a management class for backups residing on local disks and a

management class for backups residing on Tivoli Storage Manager

server storage. Different management classes provide the opportunity

for specialized policies for each storage destination. For example, you

can maintain six versions of local FlashCopy backups of a given DB2

UDB database while maintaining only two versions of the same

database on Tivoli Storage Manager server storage. Such policies can

maximize storage resources and provide more control over your

storage strategy.

Perform these steps to define a management class:

__ Step a. Define a policy set that will contain your management

class. Make sure to define the policy set to the domain

created in Step 1. For example, to create the policy set

db2policyset in the db2domain domain, issue this command:

define policyset db2domain db2policyset

__ Step b. Define a management class for backups residing on local

disks. This management class is specified in the

18

Configuration Wizard as the ″LOCAL Backup Management

Class.″ For example, to define management class

db2localmgmtclass to policy set db2policyset in the db2domain

domain, issue this command:

define mgmtclass db2domain db2policyset db2localmgmtclass

__ Step c. Define a copy group to this management class. The server

will use this copy group to manage backups residing on

local disks. Therefore, specify policies for your data such as

v the storage pool where data is stored (destination

parameter);

v how frequently the data can be backed up (frequency

parameter);

v the maximum number of backup versions to maintain for

data currently on local disks (verexists parameter);

v the number of days to retain a backup version after the

backup version has become inactive (retextra parameter).

In this example, the command defines copy group

db2localgroup to storage pool db2localpool in management

class db2localmgmtclass in policy set db2policyset in the

db2domain domain. It also retains up to five backup versions

of data while the data exists on the host.

define copygroup db2domain db2policyset db2localmgmtclass

db2localgroup type=backup destination=db2localpool

verexists=5

Attention: Repeat Step 2a through Step 2c to define a

management class and copy group for backups that will

reside on Tivoli Storage Manager server storage. This

management class is specified in the Configuration Wizard

as the ″TSM Backup Management Class.″ Then proceed to

Step 2d.

__ Step d. Activate the policy set db2policyset by issuing this

command:

activate policyset db2domain db2policyset

__ Step 3. Register a nodename for each host on the Production System and the

Backup System to the Tivoli Storage Manager server. Consider the

following caveats before issuing the register node command on the

server command line:

v You can define a new nodename on each host for ACS for DB2 UDB

or use an existing backup-archive client nodename.

v Make sure each node is registered to the policy domain created in

Step 1 under ″Policy.″

v Determine which node will be your target node. The target node will

represent the database instance and will perform backup and restore

operations on behalf of other nodes in your environment (known as

agent nodes) via proxy authority. Each target node must have

authority to delete its own backup files from the server. Therefore,

specify the backdelete=yes parameter when registering this node.

v Be aware that all hosts on the Production System and the Backup

System are considered agent nodes. These nodes own the data and

will have backup and restore operations performed for them by the

target node. Agent nodes are associated with their hosts in the

Configuration Wizard.

Chapter 4. Configuring ACS for DB2 UDB 19

Example: To register nodename nodeA with password pwdnodeA to

policy domain db2domain, issue this command:

register node nodeA pwdnodeA domain=db2domain

__ Step 4. Grant proxy authority between the agent node and the target nodes.

Do this by issuing the grant proxynode command on the server

command line. Repeat this command for each target node and agent

node.

Example: To grant nodeA (target node) proxy authority over nodeB

(agent node), issue this command:

grant proxynode target=nodeA agent=nodeB

__ Step 5. Determine which backup host will serve as the master node. This

master node will be the host that synchronizes and coordinates all

backup and restore activities. It is also the node from which all backup,

restore, and query operations are issued. The master node is specified

in the Configuration Wizard.

__ Step 6. For an Enterprise Storage Server subsystem, locate the Java Runtime

Environment (JRE) installation directory on the master node. The path

is specified in the Configuration Wizard.

3. Set up target nodes for communication

The client user options file (dsm.opt) and client system options file (dsm.sys) that

you must edit are located (by default) in the client installation directory:

/usr/tivoli/tsm/client/ba/bin.

Attention

Specify these options on each node in the Production System and Backup

System.

__ Step 1. In the dsm.opt file, specify the servername option with the name you

want to use to identify the Tivoli Storage Manager server and to begin

a stanza containing options for that server in the dsm.sys file. For

example:

servername serverA

Do not change the server stanza name (servername) in the dsm.opt file

after completing a successful local backup (backupdestination=local).

The query db2udb and restore db2udb commands will fail if the

server stanza name in the dsm.opt file changes after completing a

successful local backup.

__ Step 2. In the dsm.sys file, specify the servername option with the name used

to identify the Tivoli Storage Manager server in the dsm.opt file.

Specify these options and values within the stanza for that server:

servername serverA

commmethod TCPip

tcpport <port address>

tcpserveraddress <yourserver.xyzinc.com>

nodename <your nodename>

passwordaccess generate

schedmode prompted

20

The servername option in the dsm.opt and dsm.sys files defines server

stanza names only. The tcpserveraddress option controls which server

is actually contacted.

If you would like to maintain settings for more than one server in the dsm.sys file,

see “Configuring multiple server stanzas” on page 64 for instructions.

4. Set up the disk storage subsystem

__ Step 1. Make sure the pSeries hosts are connected to the storage subsystem.

__ Step 2. For an Enterprise Storage Server subsystem, locate the path to the

Copy Services command line interface code as this path is specified in

the Configuration Wizard.

For DS and SAN VC subsystems, the CIM Agent (ICAT) must be

configured correctly on the host where the ICAT server resides. This

host and associated port number are specified in the Configuration

Wizard. Follow these steps to configure the CIM Agent (ICAT) for

non-SSL connectivity:

a. Change to the directory where the CIM Agent is installed. The

default location is /opt/IBM/cimagent.

b. Issue the stopcimom command to stop the administrative agent.

c. Locate the cimom.properties file and specify the following values:

ServerCommunication=HTTP

Port=5988

DigestAuthentication=False

d. Issue the startcimom command to start the administrative agent.

e. View the Administrative log file, cimom.log, located (by default) in

the /usr/tank/admin/log directory, to verify the port number and

the CIM Agent version level.

f. Once the administrative agent completes the start up process, run

the verifyconfig program to verify that the CIM Agent is configured

correctly. For example:

verifyconfig -u <userid> -p <password>

__ Step 3. Create the LUNs in the storage subsystem to be used. Make sure that

Copy Services is enabled for this storage subsystem. LUNs containing

the DB2 UDB database (Source Volumes) must be accessible to the

Production System. LUNs intended to be used as the Target Volumes

must be accessible to the Backup System. Assign a set of Target

Volumes for each database partition to the appropriate backup host.

The Source Volumes and Target Volumes must be the same size and

reside on the same storage subsystem. Each source LUN must have a

number of target LUNs to allow backup versions that are defined in

the backup policy.


__ Step 4. On the production host where the DB2 catalog is located, create a file

(user LUN file) that contains the dedicated backup Target Volumes for

each backup host. The user LUN file must follow this format:

<backup hostname>:

<lunid>

<lunid>

<backup hostname>:

<lunid>

<lunid>

The path to this file is specified in the Configuration Wizard. This file

is automatically transferred to the /usr/tivoli/tsm/client/ba/bin

directory on the master node after configuration completes and is

renamed as cflnfct_<configuration name>.

For example, on an Enterprise Storage Server subsystem, a user LUN

file for configuration name admindb and backup hosts buphost1 and

buphost2 would look like the following (cflnfct_admindb):

buphost1:

10194025

10294025

10394025

10494025

10594025

10694025

10794025

buphost2:

20194025

20294025

20394025

20494025

20594025

20694025

20794025

For DS storage subsystems:

buphost1:

13019010001

13019010002

13019010003

13019010004

13019010005

13019010006

13019010007

buphost2:

1301901100A

1301901100B

1301901100C

1301901100D

1301901100E

1301901200A

1301901200B

22

For SAN VC storage subsystems, caption names are used instead of

numerical serial numbers. For example:

buphost1:

tdp_hdw8

tdp_hdw9

buphost2:

tdp_hdw5

tdp_hdw6

__ Step 5. For an Enterprise Storage Server subsystem, determine the Copy

Services user name, password, and path to the installation directory.

This information is specified in the Configuration Wizard.

__ Step 6. Determine the DB2 authentication information, such as the DB2

instance name and password. This information is specified in the

Configuration Wizard.

__ Step 7. For an Enterprise Storage Server subsystem, determine the host name

for the primary Copy Services server (server A).

For DS and SAN VC subsystems, determine the host where the ICAT

server resides, the associated port number, and the user ID and

password used to connect to the CIM Agent. This information is

specified in the Configuration Wizard.

__ Step 8. For an Enterprise Storage Server subsystem, determine the host name

for the backup Copy Services server (server B). This name is specified

in the Configuration Wizard.

Subsystem Device Driver configurations

ACS for DB2 UDB supports the following Subsystem Device Driver (SDD)

configurations:

v SDD is not installed on the Production System and the volume group that

contains the DB2 UDB database has AIX hdisk devices.

v SDD is installed and configured on the Production System and the volume

group that contains the DB2 UDB database has AIX vpath devices.

v SDD is installed and configured on the Production System and the volume

group that contains the DB2 UDB database has AIX hdisk devices.

v SDD is installed and configured on the Production System but not on the

Backup System.

v SDD is installed and configured on the Backup System but not on the

Production System.

v SDD is installed and configured on both the Production System and the Backup

System.

Note that ACS for DB2 UDB does not support SDD volume groups that contain a

DB2 UDB database which has a combination of hdisk and vpath devices.


5. Validate the DB2 UDB setup

__ Step 1. Make sure the recovery logs are located on a volume group that is

separate from the volume groups where data resides.

__ Step 2. Make sure that archive is enabled.

__ Step 3. Make sure each database partition contains its own set of one (or more)

volume groups that are configured with the LUNs created on the

storage subsystem.

6. Launch the Configuration Wizard

Use the Configuration Wizard to complete the configuration process:

__ Step 1. Log in to the production host (where the DB2 catalog is located) as root

user. Launch the Tivoli Storage Manager Java GUI by issuing the dsmj

command.

__ Step 2. In the Menu Bar, select Utilities→Configuration Wizard→ACS for DB2

UDB.

__ Step 3. Follow the prompts on your screen to complete the configuration

process.

When a database is created, database partitions are created for all the partition

servers specified in the node configuration file (db2nodes.cfg). As a result, if more

than one database is created in a database instance, all the databases share the

same node configuration file and therefore contain the same number of hosts and

database partitions. The db2nodes.cfg file is located in the /home/<db2user>/sqllib

directory where <db2user> is the name of the DB2 user that owns the database

instance.

You can run the query db2config command to confirm that the Configuration

Wizard successfully transferred your settings to the master node. This command

queries the DB2 UDB, Tivoli Storage Manager, and storage subsystem environment.

See “Query DB2config” on page 41 for more details about this command.

24

Chapter 5. Planning your DB2 UDB backups

This chapter describes the different types of backups that can be performed and

provides recommendations toward creating a comprehensive backup strategy.

Backup process overview

A backup request contains information about the DB2 UDB database, the DB2

instance, the backup destination, and related storage subsystem options. Beginning

with the node where the database catalog is located, the backup master node

contacts all of the database nodes and backup nodes that will participate in the

backup operation to ensure that these nodes contain supported levels of Tivoli

Storage Manager, DB2 UDB, and AIX. The backup master node queries the

database configuration on each of the nodes to determine the DB2 UDB database

partitions. A set of metadata is created for each DB2 database partition. The

backup master node gathers this information from the DB2 worker nodes. Once

the set of database source LUNs is determined, a matching set of target LUN

containers is located.

Next, the backup master node coordinates the operation which consists of

quiescing the DB2 database, initializing the backup, and resuming database

components to minimize downtime on the production database. The Target

Volumes are mounted on the Backup System in order to validate the volumes that

are used in backup processing. Optionally, the data is then moved to the Tivoli

Storage Manager server by the Backup System.

Consider these facts when planning for your DB2 UDB backups:

v Make sure that you do not have a file system (mounted or unmounted) on the

Backup System with the same name as a database file system to be backed up

from the Production System. ACS for DB2 UDB can fail on the Backup System if

this occurs.

v When backing up a database residing on a raw logical volumes, ACS for DB2

UDB gives temporary Read/Write permission to the raw volume device special

file on the Backup System.

v Backup processing affects the user and system data components of the DB2 UDB

database only. DB2 UDB log files and temporary tables are not affected. The

database administrator is responsible for periodically backing up the DB2 UDB

database logs. It is recommended that the archive logs be backed up to the

Tivoli Storage Manager server after every full database online backup.

v Back up configuration files (especially db2nodes.cfg) regularly to the Tivoli

Storage Manager server so that they are available in the event that the database

instance is lost.

v DB2 UDB data is backed up at the database level only. Partitions and table

spaces cannot be backed up as individual components.

v Note that you cannot run two backup db2udb commands for the same database

concurrently.

A status log file (<database_alias>.log) is maintained by the client which records

events associated with backup and restore operations. This file is located in the

directory specified by the DSM_LOG environment variable. If this environment


variable is not specified, the status log file is located in the default client

installation directory (/usr/tivoli/tsm/client/ba/bin). Refer to this file for

information regarding your operations.

Backup destination

ACS for DB2 UDB provides two back up destinations:

v Local disks

v Tivoli Storage Manager

Local disks

A local backup operation (backupdestination=local) performs a snapshot backup of

a DB2 UDB database within a DB2 UDB instance and stores the backed up data on

local storage subsystem disks. Metadata files and configuration files associated

with the backup are sent to the Tivoli Storage Manager server. This type of backup

is recommended when quick periodic backups and fast recovery times are needed.

For example, by maintaining multiple backup copies on local storage subsystem

disks, backup and recovery times are much faster than when backing up data to

Tivoli Storage Manager server storage. However, the following factors can impact a

local backup:

Local storage space

Sufficient local storage space must be available for this backup strategy to

be successful. Make sure there is enough available storage space assigned

to the disks to accommodate your ACS for DB2 UDB backup operations.

Environment and storage resources also impact how many backup versions

are maintained on local storage (for fast recovery) and how many backup

versions are maintained on Tivoli Storage Manager server storage (longer

term storage). It is recommended that different sets of policies be created

for both local backups and Tivoli Storage Manager backups.

The procedure, “2. Set up policy and nodes on the Tivoli Storage Manager

server” on page 18, provides step by step instructions on how to set up

these policies.

Frequency of local backups

For DS and Enterprise Storage Server storage subsystems, there can be no

more than two backups occurring while the background copy process is

pending. As a result, local backups should be initiated at a frequency that

will prevent more than two such backups from occurring. For SAN VC

storage subsystems, only one backup is allowed to occur while the

background copy process is pending. A new backup is not performed until

the background copy process for the previous backup completes. As a

result, local backups for SAN VC storage subsystems should be initiated at

a frequency greater than the time required for the background copy

process to complete.

Management policy local backups

The number specified by the Tivoli Storage Manager server verexists

parameter (defined in the copy group of the management class to which

the local backup belongs) manages the number of local backup versions

maintained by the Tivoli Storage Manager server. The value of this

parameter must be equal or larger than the number of Target Volume sets

allocated for local backups. For example, if verexists=3, then at least three

sets of Target Volumes must be allocated for the backup to complete

successfully. If only two sets of Target Volumes are allocated, the third and

subsequent backup attempt will fail. If more sets of Target Volumes exist

26

than the number specified by the verexists parameter, these sets are

ignored by the Tivoli Storage Manager server.

When the number of local backup versions reaches the number specified

by the verexists parameter, Tivoli Storage Manager reuses one of the sets of

Target Volumes based upon these settings:

v If the backup has copytype=noincr specified, the Target Volume set

representing the oldest full copy is used. This is true only when there

are no local full backups in a state of ″background copy pending″ or

there are no backups to Tivoli Storage Manager server storage in

progress on other full copy Target Volume sets.

v If the backup has copytype=incr specified, the Target Volume set

established with the incremental relationship is used. This is true only

when the background copy processes for the previous incremental is

complete. If this is the first incremental backup, all previous full backups

must be in a complete state before the oldest full backup can be used for

an incremental backup.

v If the backup has copytype=any specified, the oldest Target Volume set

for which there are no other background copy processes (for either the

full volume copy or the incremental refresh copy) is used. If the Target

Volume set used is a full volume copy, the backup will be a full volume

copy. If the Target Volume set used is an incremental refresh, the backup

will be an incremental refresh. Be aware that in this copytype=any

situation, the backup fails if both a full volume copy and incremental

refresh background copy process is pending or there are backups to

Tivoli Storage Manager server storage in progress.

At most there can only be two backups that are in a state of background

copy pending at any time for DS and Enterprise Storage Server storage

subsystems: one full local backup and one incremental backup. When this

situation occurs, the backup version in a state of background copy pending

is not available for restore. A backup version can only be restored when

the background copy process completes.

See “2. Set up policy and nodes on the Tivoli Storage Manager server” on

page 18 for detailed instructions about setting up management classes.

The policy management of local backups is responsible for reconciling the local

backup repository with the information stored on the Tivoli Storage Manager

server. For example, if Target Volume LUNs that were used for a local backup are

removed from the storage subsystem, the information representing the backup on

the Tivoli Storage Manager server must be reconciled. Likewise if the Tivoli

Storage Manager server policy has determined that a local backup copy is no

longer needed, the local backup manager must free the Target Volume LUNs to the

storage subsystem so that these LUNs can be used for future backup operations.

You can perform a local backup manually on the command line interface with the

backup db2udb command or as a scheduled backup by defining a command

schedule on the Tivoli Storage Manager server to execute the backup db2udb

command.

Chapter 5. Planning your DB2 UDB backups 27


A Tivoli Storage Manager backup operation (backupdestination=tsm) uses a

snapshot of a DB2 UDB database within a DB2 UDB instance to store the backed

up data on Tivoli Storage Manager server storage. DB2 UDB data, metadata files,

and configuration files associated with the backup are sent to the Tivoli Storage

Manager server. Although this type of backup typically takes longer to process

than a local backup, a Tivoli Storage Manager backup is necessary when long term

storage is needed such as saving DB2 UDB data on tape for archival purposes.

Tivoli Storage Manager backups are also necessary for disaster recovery situations

when the storage subsystems that are used for local backups are unavailable. By

maintaining multiple backup copies on Tivoli Storage Manager server storage, a

point in time archival copy is available should Target Volumes on the storage

subsystem become corrupt or deleted. Note that no background copy processing

occurs when data is backed up to Tivoli Storage Manager server storage only.

You can perform a Tivoli Storage Manager server backup manually on the

command line interface with the backup db2udb command or as a scheduled

backup by defining a command schedule on the Tivoli Storage Manager server to

execute the backup db2udb command.

Example 1

This command creates a snapshot backup on the Tivoli Storage Manager server of

database myDB within database instance myInstance, where the database

configuration name is myDB:

dsmc backup db2udb -database=myDB -backupdestination=tsm

Example 2

This command uses a snapshot of database myDB within database instance

myInstance (where the database configuration name is myDB) to store the backed

up data on storage subsystem disks and send a snapshot image to the Tivoli

Storage Manager server:

dsmc backup db2udb -database=myDB -backupdestination=both

Scheduled (automated) backup

Scheduled backups allow your DB2 UDB data to be backed up automatically to the

destination of your choice. A recommended scheduled backup strategy should

consist of frequent backups to local disks (backupdestination=local) as well as

backups to both local and Tivoli Storage Manager server storage

(backupdestination=both) on a less frequent basis. The frequent backups to local

disks should be scheduled to occur during a time period that is greater than the

time it takes to complete a backup to Tivoli Storage Manager server storage

(including background copy processing). For example, schedule several backups

per day to locals disks while scheduling only one backup per day to Tivoli Storage

Manager server storage.

Consider the following information when planning your scheduled backups:

v The node configuration file (db2nodes.cfg) as well as other configuration files

should be backed up to the Tivoli Storage Manager server so that they are

available in the event that a database instance is lost.

v The master node is the node that is contacted by the Tivoli Storage Manager

server to run the scheduled backup.

v The schedule must contain the backup db2udb command.

28

v Each proxy node used in the schedule must have the Tivoli Storage Manager

Client Acceptor Daemon (CAD), dsmcad, running.

v To ensure your backups were successful, you can use the query systeminfo

command to view the scheduler log file (dsmsched.log), located in the same

directory where the client error log file (dsmerror.log) is located. For example:

dsmc query systeminfo db2udb schedlog

v During a scheduled backup, the client error log file (dsmerror.log) is placed in

the directory from which the scheduler is started or the value specified with the

DSM_LOG environment variable.

Example 1

This example demonstrates how to set up a basic backup schedule:

1. Log on to the Tivoli Storage Manager server with the Tivoli Storage Manager

Administrative Client by entering this command:

dsmadmc -id=<adminid> -password=<adminpassword>

2. Define a command schedule:

define schedule <domain name> <schedule_name> action=command

objects="dsmc backup db2udb -database=<dbconfigname>

-backupdestination=local" startdate=<date> starttime=<start time>

3. Define an association between this schedule and your target node:

define association <domain name> <schedule name> <target node>

4. Define an association between this schedule and your master node:

define association <domain name> <schedule name> <master node>

5. Log on to the master node and start the client scheduler with this command:

dsmc schedule

Note that if there is more than one backup host in your Backup System and

you plan to define more than one schedule, define the first schedule on the

master node and subsequent schedules on the other backup hosts.

Example 2

This example assumes that a backup to both Tivoli Storage Manager server storage

and local disks (including background copy processing) takes four hours to

complete. One way to implement a thorough backup strategy for this situation is

to define two backup schedules.

For example, one schedule performs a backup to local disks every four hours (4

am, 8 am, 12 pm, 4 pm, 8 pm, 12 am):


objects="dsmc backup db2udb -database=<dbconfigname> -backupdestination=local

starttime=00:00 duration=1 durunits=hours period=4 perunits=hours priority=2"

Another schedule performs a backup to both local disks and Tivoli Storage

Manager server storage at 12 am:


objects="dsmc backup db2udb -database=<dbconfigname> -backupdestination=both

starttime=00:00 duration=1 durunits=hours period=24 perunits=hours priority=1"

Note that since a single schedule cannot perform the 12 am backup to local disks

and the 12 am backup to both local disks and Tivoli Storage Manager server

storage, the Tivoli Storage Manager server priority parameter is used to specify

which schedule takes priority.


In these examples, the priority=1 value ensures that the backup to both local disks

and Tivoli Storage Manager server storage is performed. However, since a since a

single schedule cannot perform both backup schedules at the same time, the 12 am

backup to local disks will be missed as the schedule will miss its backup window.

As a result, there will be a missed event in the central scheduler, even though the

goal of implementing a thorough backup strategy is still met.

Example 3

Like the previous example, this example also assumes that a backup to both Tivoli

Storage Manager server storage and local disks (including background copy

processing) takes four hours to complete. However, instead of defining two backup

schedules as shown in Example 2, this example defines a separate schedule for

each start time. For example:

4 am and 4 pm backup to local disks:



starttime=04:00 duration=1 durunits=hours period=12 perunits=hours"

8 am and 8 pm backup to local disks:




12 pm backup to local disks:




12 am backup to both local disks and Tivoli Storage Manager server storage:


objects="dsmc backup db2udb -database=<dbconfigname> -backupdestination=both

starttime=00:00 duration=1hour period=24hours"

Although several schedules must be defined for these two backup destinations,

this method still implements a thorough backup strategy for this situation.

Incremental backup

An incremental backup (copytype=incr) produces a snapshot image (with

background copy) of all the changes that have occurred to the storage subsystem

Source Volumes since the previous snapshot (incremental or regular full backup)

was taken. This backup copy type uses incremental snapshot capabilities of storage

subsystems, such as the incremental FlashCopy feature available with the DS and

Enterprise Storage Server family of storage subsystems. The background copy

process makes a copy of the physical path from the Source Volumes to the Target

Volumes and copies this information to the Target Volumes when processing

initializes. The ″in process″ relationship between the Source Volumes and Target

Volumes ends when background copy processing completes. Background copy

processing normally takes several hours to complete and this time can increase

with larger databases.

By specifying copytype=incr, you can have a backup version available for local

restore quickly and are also able to schedule backups to occur more frequently.

Also, the production database server is available immediately after the incremental

backup is initiated (a process that lasts only a few minutes). However, you cannot

30

restore a backup version while a state of background copy pending exists for the

previous backup. Note that if the original database LUNs are overwritten, the

restore will be a full volume background copy.

Perform incremental backups during normal production operations and maintain

both local and Tivoli Storage Manager backups as a coordinated set of backup

data. For example, if an administrator removes LUNs that are used for tracking a

local backup, the corresponding information on the Tivoli Storage Manager server

would need to be updated to reflect that a particular backup version (or versions)

was no longer available to the user. An incremental backup will record those

changes.

You can maintain control of your incremental backup strategy by specifying

copytype=incr with the backup db2udb command during backup processing.

However, specify copytype=any to allow Tivoli Storage Manager to determine

when to use incremental with background copy. If more than one local incremental

backup version is available, only one set of Target Volumes are used in the backup

operation. Note that the copytype parameter is ignored when performing a back

up to Tivoli Storage Manager storage only. In that case, a no copy (copy-on-write

snapshot image) is performed.

Note: SAN VC does not support incremental backups. If copytype=incr is specified

for databases residing on a SAN VC storage subsystem, ACS for DB2 UDB

defaults to the following copy types:

v If backupdestination=both or backupdestination=local is specified, a copy

copy type is performed.

v If backupdestination=tsm, is specified, a nocopy copy type is performed.

Preview your backup settings

Before performing a backup, it is recommended that you view your environment

settings to determine whether the database and hardware resources are configured

properly to ensure a successful backup. For example, you can determine whether

sufficient target LUNs are available to create at least one local backup. You can

view your settings by specifying the preview parameter with the backup db2udb

command.

Example 1

First, this command previews the user environment for database configuration

myDB:

dsmc backup db2udb -database=myDB -backupdest=local -copytype=noincr -preview


The following output displays:

IBM Tivoli Storage Manager

Command Line Backup/Archive Client Interface

Client Version 5, Release 3, Level 3.0

Client date/time: 09/29/05 13:51:49

(c) Copyright by IBM Corporation and other(s) 1990, 2006. All Rights Reserved.

Node Name: TRIPLE_3N1SVC

Session established with server SERVER1: AIX-RS/6000

Server Version 5, Release 3, Level 1.0

Server date/time: 09/29/05 13:54:46 Last access: 09/29/05 13:54:44

Accessing as node: svc_asnode

Detailed status information written to log ’/home/acct1/trace.out’.

Backup preview of DB2 UDB database ’myDB’ invoked.

Gathering information for backup preparation to backup destination ’LOCAL’.

Initializing Enterprise Storage Server FlashCopy snapshot.

ANS2733I The backup DB2 UDB preview command indicates there are sufficient

resources for a backup operation.

Then, this command creates a local snapshot backup of database myDB within

database instance myInstance, where the database configuration name is myDB:

dsmc backup db2udb -database=myDB -backupdest=local -copytype=noincr

Example 2

This command creates a snapshot backup on the Tivoli Storage Manager server of

database myDB within database instance myInstance, where the database

configuration name is myDB:

dsmc backup db2udb -database=myDB -backupdestination=tsm

32

Chapter 6. Planning your DB2 UDB restores

This chapter describes the different types of restores that can be performed and

provides recommendations toward creating a comprehensive restore strategy.

Restore process overview

Initiate a DB2 UDB restore from the backup master node. The restore is performed

from a snapshot image stored on either a local storage subsystem or on the Tivoli

Storage Manager server. The restore request contains information about the

database and instance to be restored and the backup destination from which to

restore. You can also specify a point-in-time from which to restore the backup. A

DB2 UDB database can be restored at the following levels:

v As a single partition of a database in a multi-partition environment.

v As all partitions residing on a single host in a multi-host database environment.

v As an entire database in a single or multi-partition environment.

ACS for DB2 UDB restore processing affects the user and system data components

of the DB2 UDB database only. DB2 UDB log files and temporary tables are not

affected. The database administrator is responsible for periodically backing up the

DB2 UDB database logs. It is recommended that the archive logs be backed up to

the Tivoli Storage Manager server after every full database online backup.

Be aware that in order for a restore to complete successfully, the settings contained

in the db2nodes.cfg file (used for the restore) must be the same as the settings

contained in the db2nodes.cfg file used during the original backup. For example,

assume a backup is performed using a db2nodes.cfg file that contains settings for a

multi-partition database (hostA contains partition 0 and partition 1, hostB

contains partition 2 and partition 3). After this backup is performed, hostB fails

and partition 2 and partition 3 failover to hostA. An attempt to restore the

database with the configuration (db2nodes.cfg file) used during the original

backup will fail as the settings are now different. For the restore to complete

successfully, hostB must be recovered and the database configured to the settings

contained in the db2nodes.cfg file used during the original backup.

Restoring from local disks

A restore from local disks (local restore) uses the snapshot feature to restore a local

snapshot backup residing on storage subsystem disks (instead of Tivoli Storage

Manager server storage) to the original Source Volumes on the production host. If

the original backup was made to storage subsystem disks, metadata is restored to

the backup master node (the only Backup System node involved in restore

processing). The information from the metadata files is sent to the participating

DB2 nodes to verify that the hardware and volume configuration is correct. Local

restores are recommended as a quick recovery of your data in the event of a major

failure such as the loss of the storage structures of the operating system after the

original backup. Also, if you were unable to back up to Tivoli Storage Manager

server storage due to lack of sufficient storage or network constraints, you can

restore your data from local storage subsystem disks.

Be aware that local restore processing overwrites the data on all the storage

subsystem volumes on the production host where the table space container is


located for the associated database. As a result, it is recommended that you specify

a dedicated volume group for the database log path. Recovery of the database to

the current point in time is not possible if log files are overwritten during local

restore processing and an archived version of the current database logs is not

available. Local restore will only restore data that was backed up locally. Note that

the node from which the restore operation is performed must have authority to

delete its own backup files from the Tivoli Storage Manager server.

If a local restore reverts the database to a previous configuration, you must

perform a backup before making additional configuration changes to the database.

This backup is required when the database resides on a SAN VC storage

subsystem. It is recommended that you perform a local backup immediately after

the completion of a background copy of a successful local restore for all storage

subsystems.

Use the command, “Restore DB2udb” on page 44, to perform a local restore. You

can also view local snapshot backups with the command, “Query DB2udb” on

page 42.

Example 1

This command restores the active backup version (most recent) of DB2 UDB

database myDB (within the database instance myInstance) from a local snapshot

backup:

dsmc restore db2udb -database=myDB -backupdestination=local

Example 2

This command restores the active backup version (most recent) of all data from

DB2 UDB database myDB (within the database instance myInstance) defined to host

production_1 from a local snapshot backup:

dsmc restore db2udb -database=myDB -dbhostname=production_1

-backupdestination=local

Example 3

This command restores the active backup version (most recent) of all data from

DB2 UDB database myDB (within the database instance myInstance) defined to host

production_1, on partition 12, from a local snapshot backup:

dsmc restore db2udb -database=myDB -dbhostname=production_1 -dbpartitionn=12


or

dsmc restore db2udb -database=myDB -dbhostname=production_1 -dbpartitionn=host0012


34

Example 4

This command restores an inactive (inactive) backup version of DB2 UDB database

townd from a local snapshot backup:

dsmc restore db2udb -database=townd -inactive -pick

However, note that the use of the pick parameter displays a list of all available

inactive backups of DB2 UDB database townd from which to choose:

TSM Scrollable PICK Window - Restore DB2 UDB Database

# Backup Date/Time Size A/I Type Database Name

-----------------------------------------------------------------------

1. | 08/17/05 13:13:22 1.56 GB A LOCAL -FULL townd

2. | 08/17/05 12:59:09 1.56 GB I LOCAL -FULL townd

|

|

0---------10--------20--------30--------40--------50--------60--------7

<U>=Up <D>=Down <T>=Top <B>=Bottom <R#>=Right <L#>=Left <E>=Expand <O>=Ok <C>=Cancel

pick>2

By entering 2, the inactive backup version with the date and time stamp of

08/17/05 12:59:09 is restored and the following output information displays:






Node Name: BEAR01_TOWND

Session established with server SERVER01_530_342: AIX-RS/6000



Accessing as node: TOWND_ASNODE

Detailed status information written to log ’/home/tsmlog/bing.trace’.

Restoring local hardware configuration files.

Restoring 778 /townd/tivoli/tsm/client/ba/bin/mfTSMDB2_townd_0 -->

-->/usr/tivoli/tsm/client/ba/bin/mfTSMDB2_townd_0 [Done]

Restoring 778 /townd/tivoli/tsm/client/ba/bin/mfTSMDB2_townd_1 -->

-->/usr/tivoli/tsm/client/ba/bin/mfTSMDB2_townd_1 [Done]

Restore of DB2 UDB database ’townd’ invoked.

Gathering current DB2 configuration for ’LOCAL’ restore.

Verifying current configuration with configuration at backup time.

Initializing Enterprise Storage Server FlashCopy snapshot.

Stopping the database manager.

Creating Full-copy snapshot.

Starting the database manager.

Local restore of DB2 UDB database ’townd’ completed pending completion

of background copy process.

The DB2 UDB operation has terminated.

Perform a database roll forward recovery before using the database.

Chapter 6. Planning your DB2 UDB restores 35

Restoring from the Tivoli Storage Manager server

This type of operation restores data stored on Tivoli Storage Manager server

storage. Data is restored directly to the Production System where the data is sent to

the Source Volumes. Note that the backup master node is the only Backup System

node involved in restore processing. Typically, data should be restored from Tivoli

Storage Manager server storage less frequently than from local backups due to the

fact that most backups are stored on Tivoli Storage Manager server storage as part

of a long-term backup strategy. In the event that backed up data residing on local

storage subsystem disks becomes corrupt or accidentally deleted, you can restore

backed up copies of the lost data from Tivoli Storage Manager server storage.

Use the command, “Restore DB2udb” on page 44 to perform a restore from Tivoli

Storage Manager server storage. You can also view backups residing on the Tivoli

Storage Manager server with the command, “Query DB2udb” on page 42.

Example

This command restores DB2 UDB database myDB (within the database instance

myInstance) from a backup stored on the Tivoli Storage Manager server:

dsmc restore db2udb -database=myDB -backupdestination=tsm

Point in time restore

This type of operation restores data to the state that existed at the specified point

in time. For example, if one of several backup images on local storage subsystem

disks becomes corrupt, a point in time restore allows you to restore data from a

time prior to when the corruption occurred. Data backed up on or before the

specified time is processed. Data backed up after this time are ignored. This type

of restore can also be used to recover configuration information to a prior

condition should that information no longer be available.

Use the pitdate parameter (to establish a date) with the pittime parameter (to

establish a time) when using the command “Restore DB2udb” on page 44. You can

view backups that are available to restore with the command “Query DB2udb” on

page 42.

36

Example

This command queries all active and inactive backup copies of DB2 UDB database

mydb (within the database instance myinst) which are stored as local snapshot

backups and Tivoli Storage Manager backups:

dsmc query db2udb -database=mydb -backupdestination=both -inactive -detail

A list of active and inactive backups is displayed. Note that by specifying the

detail parameter, host and partition information is also displayed:






Node Name: MYDBINST_MASTER

Session established with server TSMSERVER1: Windows



Accessing as node: MYDBINST_ASNODE

Size Backup Date Backup Type A/I Database

---- ----------- ----------- --- --------

973,078,528 B 04/05/05 10:46:56 LOCAL -INCR A mydb

DB2 UDB Database Instance: mydbinst DB2 UDB Database Name: MYDB

Host Name: host1

Partition Name: NODE0000


973,078,528 B 04/04/05 16:07:06 LOCAL -FULL I mydb

DB2 UDB Database Instance: mydbinst

Host Name: host1



973,078,528 B 04/03/05 15:08:27 TSM I mydb

DB2 UDB Database Instance: mydbinst

Host Name: host1



Based upon the available backups, this command restores the full backup version

of the DB2 UDB database mydb (within the database instance myinst), that was

originally taken on 04/04/05 at time 16:07:06, from local storage subsystem disks:

dsmc restore db2udb -database=mydb -backupdestination=local

-pitdate=04/04/05 -pittime=16:07:06

Chapter 6. Planning your DB2 UDB restores 37

Chapter 7. Commands

ACS for DB2 UDB provides the following commands:

Table 7. What is new

Task Command More information

Back up a DB2 UDB database backup db2udb “Backup DB2udb”

Confirm that the Configuration

Wizard successfully transferred

your settings to the master node

query db2config “Query DB2config” on

page 41

View a list of local and Tivoli

Storage Manager snapshot

backups

query db2udb “Query DB2udb” on

page 42

View system and environment

information

query systeminfo “Query Systeminfo” on

page 43

Restore a DB2 UDB partition or

database

restore db2udb “Restore DB2udb” on

page 44

Withdraw persistent FlashCopy

relationships for storage

subsystem volumes

withdraw db2udb “Withdraw DB2udb” on

page 46

Backup DB2udb

The backup db2udb command backs up a DB2 UDB database within a DB2 UDB

instance. You can store the backed up data in these locations:

v locally on storage subsystem disks;

v on the Tivoli Storage Manager server; or

v on both storage subsystem disks and the Tivoli Storage Manager server.

The node on which the backup db2udb command is entered must have authority

to delete its own backup files from the Tivoli Storage Manager server. You can

assign this authority with the Tivoli Storage Manager server register node or

update node command. This authority must exist in order to use the backup

db2udb command.

Note that you cannot run two backup db2udb commands for the same database

concurrently.

See Chapter 5, “Planning your DB2 UDB backups,” on page 25 for detailed

information about the types of backups you can perform and recommendations

toward creating a backup strategy.


Backup DB2udb Syntax

�� DSMC Backup DB2udb -DATABase= dbconfigname �

� Local

-BACKUPDESTination=

Tsm

Any

Both

-COPYType=

Incr

NOIncr

�

� -PREView

No

-COMPRESSIon=

Yes

��

Backup DB2udb Parameters

-DATABase=

Specify the DB2 UDB configuration name provided in the Configuration

Wizard. This parameter is required.

-BACKUPDESTination=

Specify one of the following backup destinations:

Local A local snapshot backup is performed. This is the default.

See “Local disks” on page 26 for detailed information,

recommendations, and examples of this type of backup.

Tsm A snapshot image is sent to the Tivoli Storage Manager server.

See “Tivoli Storage Manager” on page 28 for detailed information,

recommendations, and examples of this type of backup.

Both A local snapshot backup is performed and the snapshot image is

sent to the Tivoli Storage Manager server.

-COPYType=

Specify the type of copy operation to perform. Copy operations assist in

controlling the use of incremental backups with background copy. You can

specify:

Any Allows Tivoli Storage Manager to determine whether to use incr or

noincr based upon existing backups. See 27 for details about the

copytype=any value.

Incr Incremental with background copy is performed. This backs up all

changes to the disk since the previous backup. Use the incr value

when explicit control of incremental backups is desired.

NOIncr

Incremental with background copy is not performed. Use the

noincr value when explicit control of incremental backups is

desired.

Since this is an optional parameter, the type of copy operation is

determined (by default) by the specified backup destination. For example:

v When backupdestination=Local or backupdestination=Both, a copy

operation is performed. This produces a full volume snapshot

(background copy).

40

v When backupdestination=TSM, a nocopy operation is performed. This

produces a copy-on-write snapshot (no background copy) and the

copytype parameter is ignored.

See “Incremental backup” on page 30 for detailed information and

recommendations about this type of processing.

-PREView

Specify that a backup preview operation is performed. This operation

determines whether the product database and hardware resources are

configured properly to ensure a successful backup. This parameter is

ignored when backupdestination=TSM is specified.

-COMPRESSIon

Specify whether to compress files before they are backed up. You can

specify:

No Files are not compressed before they are backed up. This is the

default.

Yes Files are compressed before they are backed up.

Query DB2config

The query db2config command queries the DB2 UDB, Tivoli Storage Manager, and

storage subsystem to confirm that the Configuration Wizard successfully

transferred your settings to the master node. This is the node from which the ACS

for DB2 UDB commands are issued.

Query DB2config Syntax

�� DSMC Query DB2CONFig -DATABase= dbconfigname

20

-SCROLLLines=

n

�

� No

-SCROLLPrompt=

Yes

��

Query DB2config Parameters

-DATABase=


Wizard.

-SCROLLLines=

Specify the number of lines of information to display on your screen at one

time. You can specify from 1 to 80. The default value is 20. Use this option

when you set scrollprompt to Yes.

-SCROLLPrompt=

Specify whether you want Tivoli Storage Manager to stop and wait after

displaying the number of lines of information you specified with the

scrolllines option, or scroll through and stop at the end of the information

list.

No Scrolls to the end of the list and stops. This is the default.

Chapter 7. Commands 41

Yes Stops and waits after displaying the number of lines you specified

with the scrolllines option. The following prompt displays at the

bottom of the screen:

Press ’Q’ to quit, ’C’ to continuous scroll, or ’Enter’ to continue.

Query DB2udb

The query db2udb command queries the Tivoli Storage Manager server for a list

of local and Tivoli Storage Manager snapshot backups.

The node on which the query db2udb command is entered must have authority to

delete its own backup files from the Tivoli Storage Manager server. You can assign

this authority with the Tivoli Storage Manager server register node or update

node command. This authority must exist in order to use the query db2udb

command.

Query DB2udb Syntax

�� DSMC Query DB2udb

-DATAbase=

dbconfigname

�

� Local

-BACKUPDESTination=

Tsm

Both

-Detail

-INActive �

� 20

-SCROLLLines=

n

No

-SCROLLPrompt=

Yes

��

Query DB2udb Parameters

-DATABase=


Wizard.

-BACKUPDESTination=

Specify the type of restore to query:

Both The restore is queried from snapshot backups stored both locally

and on the Tivoli Storage Manager server.

Local The restore is queried from a local snapshot backup.

Tsm The restore is queried from a snapshot backup stored on the Tivoli

Storage Manager server.

-Detail

Specify this parameter to display detailed information about the hosts and

partitions that were backed up.

-INActive

Use this option to display both active and inactive versions.

42

-SCROLLLines




-SCROLLPrompt




list.






Query Systeminfo

The query systeminfo command gathers information about your system and

outputs this information to a file or the console. Use the query systeminfo to

gather specific information about the system and environment associated with the

name provided in the Configuration Wizard of the DB2 UDB database within the

database instance. Use the query db2config command to verify that the

Configuration Wizard successfully transferred the DB2 UDB, Tivoli Storage

Manager, and storage subsystem settings to the backup master node.

Query Systeminfo Syntax

�� DSMC Query SYSTEMInfo DB2UDB

-DATAbase=

dbconfigname

�

� item

options ��

Query Systeminfo Parameters

-DATABase=


Wizard.

item Specify one or more items from which you want to gather information.

You can specify the following items:

dsmoptfile

The contents of the dsm.opt file.

dsmsysfile

The contents of the dsm.sys file.

env Environment variables.

errorlog

The Tivoli Storage Manager error log file.

file Attributes for the file name that you specify.


inclexcl

Compiles a list of include-exclude in the order in which they are

processed during backup operations.

options

Compiled options.

osinfo Name and version of the client operating system.

policy Policy set dump.

schedlog

The contents of the Tivoli Storage Manager schedule log (usually

dsmsched.log).

encrypt

Available encryption methods.

options Specify whether to direct the output to a file or to the console. You can

specify the following options:

-console

Displays the information on the console.

-filename=outputfilename

Directs the information to be stored in the specified file. If a file

name is not specified, the information is stored in the dsminfo.txt

file by default.

Restore DB2udb

The restore db2udb command performs a snapshot restore of the following data

which was backed up with the backup db2udb command:

v An entire DB2 UDB database within a DB2 UDB instance.

v All partitions on a database host.

v A single database partition.

The node on which the restore db2udb command is entered must have authority

to delete its own backup files from the Tivoli Storage Manager server. You can

assign this authority with the Tivoli Storage Manager server register node or

update node command. This authority must exist in order to use the restore

db2udb command.

See Chapter 6, “Planning your DB2 UDB restores,” on page 33 for detailed

information about the types of restores you can perform and recommendations

toward creating a restore strategy.

44

Restore DB2udb Syntax

�� DSMC Restore DB2udb -DATAbase= dbconfigname �

� -DBHostname=

dbhostname

-DBPARTITIONName=

partition name �

� Local

-BACKUPDESTination=

Tsm

-INActive

-PIck

-PITDate=

�

� -PITTime=

20

-SCROLLLines=

n

No

-SCROLLPrompt=

Yes

��

Restore DB2udb Parameters

-DATABase=


Wizard. This parameter is required.

-DBHostname=

Specify the name of a database host when restoring a single database host.

All of the database partitions on that host are restored.

-DBPARTITIONName=

Specify the database partition name or number when restoring a single

database partition. This parameter must be specified in conjunction with

the DBHostname parameter.

-BACKUPDESTination=

Specify one of the following types of restore to perform:

Local The restore is performed from a local snapshot backup. This is the

default.

See “Restoring from local disks” on page 33 for detailed

information, recommendations, and examples of this type of

restore.

Note: If a local restore reverts the database to a previous

configuration, you must perform a backup before making

additional configuration changes to the database. This

backup is required when the database resides on a SAN VC

storage subsystem. It is recommended that you perform a

local backup immediately after the completion of a

background copy of a successful local restore for all storage

subsystems.

Tsm The restore is performed from a snapshot image stored on the

Tivoli Storage Manager server.

See “Restoring from the Tivoli Storage Manager server” on page 36

for detailed information, recommendations, and examples of this

type of restore.


-INActive

Use this option to display both active and inactive versions.

-PIck Create a list of backup versions or images that match the database

specification you enter. Select the version to restore from the list that

displays. You can use this option as a filter with the INActive option to

view both active and inactive versions.

-PITDate=

Specify the date at which you want to display or restore the latest version

of your backups. Databases backed up on or before the specified date are

processed. Backup versions you create after this date are ignored. You can

specify the pittime option with this option to establish a time (as well as a

date) at which you want to display or restore the latest version of your

backups.

-PITTime=

Specify the time at which you want to display or restore the latest version

of your backups. Databases backed up on or before the specified time are

processed. Backup versions you create after this time are ignored. Specify

this option with the pitdate option to establish a time (along with a date)

at which you want to display or restore the latest version of your backups.

See “Point in time restore” on page 36 for detailed information,

recommendations, and an example of this type of restore.

-SCROLLLines=




-SCROLLPrompt=




list.






Withdraw DB2udb

The withdraw db2udb command withdraws persistent relationships for all storage

subsystem volumes for a specified DB2 UDB database. It can be used to delete

local backups with background copy and also to delete incremental backups.

The node on which the withdraw db2udb command is entered must have

authority to delete its own backup files from the Tivoli Storage Manager server.

You can assign this authority with the Tivoli Storage Manager server register node

or update node command. This authority must exist in order to use the withdraw

db2udb command.

46

Withdraw DB2udb Syntax

�� DSMC WITHDraw DB2udb -DATAbase= dbconfigname

-INActive

-PIck �

� -PITDate=

-PITTime= ��

Withdraw DB2udb Parameters

-DATABase=

Specify the name of the DB2 UDB database and instance provided in the

Configuration Wizard. This parameter is required.

-INActive

Use this option (with the PIck option) to display both active and inactive

versions.

-PIck Create a list of backup versions or images that match the database

specification you enter. Select the version to withdraw from the list that

displays. You can use this option as a filter with the INActive option to

view both active and inactive versions.

-PITDate=

Specify the date at which you want to display or withdraw persistent

FlashCopy relationships. Relationships associated with databases backed

up on or before the specified date are processed. Relationships created after

this date are ignored. You can specify the pittime option with this option

to establish a time (as well as a date) at which you want to display or

withdraw persistent FlashCopy relationships.

-PITTime=

Specify the time at which you want to display or withdraw persistent

FlashCopy relationships. Relationships backed up on or before the

specified time are processed. Relationships created after this time are

ignored. Specify this option with the pitdate option to establish a time

(along with a date) at which you want to display or withdraw persistent

FlashCopy relationships.


Chapter 8. Messages

ANS2051W The local snapshot repository was not

found on location.

Explanation: The specified directory for the local

snapshot location does not exist.

System action: Processing continues.

User response: A new local snapshot repository will

be build in the specified directory.

ANS2052E Information about the disk subsystem is

missing.

Explanation: The local snapshot repository could not

be initialized due to missing information about the disk

subsystem.

System action: Processing stops.

User response: The application ensures that the disk

subsystem is initialized properly. Check for preceding

error messages.

ANS2053E A memory allocation error has occurred

in file filename, line number linenumber.

Explanation: Enough memory was not available to

continue processing.

System action: Processing ends.

User response: Ensure that your system has sufficient

real and virtual memory. Close unnecessary

applications.

ANS2054E Operating system error errno: messagetext.

Explanation: The application encountered an

unexpected message error during the execution of a

system function. The respective operating system error

and message text will be displayed.


User response: Check the specific error message.

ANS2055I The local snapshot manager could not

be locked.

Explanation: The local repository is locked by another

application. This process will proceed when the other

application unlock the local repository.


User response: None.

ANS2056I Waiting maximal timeout seconds until

the lock is released by the other

application.

Explanation: During the local repository is locked by

another application, the program will wait a specific

period of time to proceed. In mySAP environment is

that time 1 hour.



ANS2057E Local snapshot manager not initialized.

Explanation: The local snapshot repository was used

without previous initialization.


User response: The system normally ensures that the

local repository is initialized. Check for preceding error

messages.

ANS2058E The data container with ID dcID could

not be updated in the local repository.

Explanation: During a FlashCopy backup the target

set record in the local repository is updated with the

correspondent properties. A failure occurred during

that process.


User response: Check for preceding error messages

like memory allocation error or other system error.

ANS2059E Cannot find a target data container that

match with the source data container.

Explanation: During a FlashCopy backup, DP for

Hardware tries to find a target data container that

match to the source data container to satisfy the

FlashCopy backup. A matching target data container

could not be found.


User response: See the rules for select one of multiple

target data containers. For example, this message will

be displayed if the user is trying to start a FlashCopy

backup of type ’INCR’ and all the target sets are being

used for the FlashCopy type ’COPY’. Make sure also

that the target volumes are available to the backup

system and the syntax is correct for the following setup

file parameters: 1. shark_target_volume 2.

shark_copy_service_code 3. java_home_directory 4.

primary_copyservices_servername 5. shark_username 6.

shark_password


ANS2060W Cannot find a volume in the target data

container dcID to match with the source

srcvol.

Explanation: This warning message indicates that for

the specific source not any target volume could be

found in this target data container that matches for a

FlashCopy operation. If multiple target data containers

are being used, the processing will continue checking

the volumes of the next target data container.



ANS2061W The target data container with ID dcid

was not found in the local repository.

Explanation: An inquire of the data container with the

specified ID could not be satisfied because that target

set does not exists in the local repository.

System action: Processing may continue.

User response: The application that is requesting the

inquire will decide whether or not the error should end

the program. Check for following messages.

ANS2062W Could not find a target data container in

the state state to fulfill the requested

criteria.

Explanation: A data container in the specified state

was not found in the local repository to satisfy specific

criteria requested by the application.


User response: Which criteria have been passed is

application specific. Check for following messages. The

application will decide whether or not that warning

should end the program.

ANS2063W The local snapshot repository already

exists on the directory location.

Explanation: An application tried to create the local

repository in a directory that already exists.


User response: The application will decide whether or

not that warning should end the program. Check for

following messages.

ANS2064I The local snapshot repository will be

created on the directory location.

Explanation: The local snapshot repository containing

information about the state of the data containers is

being created.



ANS2065I The local snapshot repository could not

be created on the directory location.

Explanation: A failure occurred creating the local

snapshot repository.


User response: Look for a operating system error

message.

ANS2066E Cannot read the .fct file filename.

Explanation: The .fct file containing the target data

containers was not found or is not accessible.


User response: Check the name, the path and the

right of the file.

ANS2067E The exception CLsmException was

thrown. Reason: txt.

Explanation: An unexpected error occurred processing

a function of the local snapshot repository.


User response: Check the specific reason.

ANS2068E No target LUNs were found for the data

container dcID in the .fct file filename.

Explanation: The program will search in the .fct file

for each specific data container a list of entries with the

label <PREFIX>TARGET_VOLUME where the prefix

depends on the hardware type. Either you have a

wrong label for the target volumes of the specified data

container or this data container in the .fct file does not

have any target LUNs.


User response: This error can only occurred if the

application does not have a GUI where the user

provides the input of the target data containers and the

format will automatically be checked. If so, please

check the format of the .fct file.

ANS2069E Cannot read the file filename of the local

snapshot repository.

Explanation: The system keeps some information

about the state of the data containers locally in a file.

This file was not found or is not accessible.


User response: Check the name, the path and the

right of the file.

50

ANS2070E The repository state file filename is

empty or has a wrong format.



This file was found but the expected format of the data

in not correct.


User response: Normally the system ensures that the

format of this file is correct. Check for preceding error.

ANS2071E The data container dcID could not be

inserted in the local snapshot repository.



Inserting an entry for a new data container occurred an

error.


User response: This is an unexpected error. Check for

preceding error. If not any other error can be seen,

collect the logs and traces and contact the support.

ANS2072E An unexpected error was encountered

processing a Data Protection for

Hardware function. TDP function name

: function-name TDP function :

function-desc TDP return code : TSM-rc

TDP file : file-name (line-number)

Explanation: None.


User response: Contact the TDP administrator with

the information provided in this message.

ANS2073E The file filename of the local snapshot

repository could not be opened for

writing.


about the state of the data containers in the local

snapshot repository. Opening a file of this repository

occurred an error.


User response: Check the rights permission of that

file.

ANS2094W Unable to assign any database partitions

for back up by the Backup Worker Node

’bkupWrkr’.

Explanation: The list of target LUNs specified by user

for this backup worker node did not match in size any

of the source LUNs for any of the database partitions.

Hence no database partitions could be assigned for

backup to this backup worker node.


User response: Please assign target LUNs to backup

worker nodes so that they match in size with all the

source LUNs of a particular database partition. Also

distribute the target LUNs among all the backup

worker nodes so that there is a good load balancing of

the number of database partitions backed up by each

backup worker node.

ANS2095E JAVA HOME value ’target’ specified in

configuration is incorrect.

Explanation: The path name specified for java home is

not correct.


User response: Please check the value of java home

specified during configuration to make sure it is a valid

path name of the directory where JRE is installed on

master backup node. Use configuration wizard to

update java home value for the configuration.

ANS2096E Unable to read configuration

information for database name ’dbname’.

Explanation: The system was unable to read

configuration information for the database name

specified in the (-DATABASENAME) option.


User response: Check the spelling of the

(-DATABASENAME) option specified and ensure the

DB2 UDB configuration wizard has been used to create

the configuration information for this name.

ANS2097E Unable to establish a session with the

TDP server as target node ’target’ using

agent node ’agent’.

Explanation: None.


User response: Ensure that the multinode name exists

on the server and that the agent node has the proper

authority to target node listed.

ANS2098E One or more of the node names in the

DB2 UDB TSM configuration file are

not registered correctly as proxynode

agents.

Explanation: None.


User response: Check the TDP error log for a list of

node names that have been configured incorrectly.

Correct the problem by executing the DB2 UDB

configuration wizard.

Chapter 8. Messages 51

ANS2099W The node name ’nodename’ in the DB2

UDB TSM configuration file is not

registered as an agent for target node

name ’targetnode’.

Explanation: None.



ANS2100E Neither source volume id nor target

volume id is in the volume list.

Explanation: None.



ANS2700E The (-DATABASE) option must be

specified with the BACKUP, RESTORE,

QUERY and WITHDRAW DB2UDB

commands.

Explanation: None.


User response: Refer to the user’s guide of the

corresponding platform for the correct syntax of the

QUERY UDB command.

ANS2701E The attempted DB2UDB operation was

unsuccessful, check the TDP error log

for any additional information.

Explanation: This message is reserved for DB2 UDB.

System action: Reserved.

User response: This message is reserved for DB2 UDB.

ANS2702E The DB2 UDB Utility plug-in module

was not found or could not be loaded.

Explanation: Processing stops.

System action: None.

User response: Run ″dsmc show plugins″ at the TDP

command-line client prompt to see the available

plug-ins on the system and verify the path which is

being used to load the plug-ins. If the plugin path is

available and the DB2 UDB Utility plug-in, libPiDB2.a,

is present, ensure that the LIBPATH variable is set to

the DB2 UDB product’s library path, for example,

LIBPATH=/usr/opt/db2_08_01/lib.

ANS2703E The (-DBHOSTNAME) option must be

specified when using the

(-DBPARTITIONNAME) option for the

RESTORE DB2UDB command.

Explanation: None.





ANS2704E The (-BACKUPDESTINATION) option

cannot be ″BOTH″ when issuing the


Explanation: When using the RESTORE DB2UDB

command, the (-BACKUPDESTINATION) option can

be set to ″TSM″ or ″LOCAL″, but not ″BOTH″ unless

using the (-PICK) option. When using the (-PICK)

option the (-BACKUPDESTINATION) option can be

″TSM″, ″LOCAL″, or ″BOTH″.





ANS2705S No DB2 UDB partitions are available for

restore.

Explanation: No DB2 UDB partitions are available on

the TDP server for restore. This is most likely due to a

previous backup that was aborted before the backup

terminated. The DB2 UDB database and selected

partitions cannot be restored.


User response: Issue the TDP client command QUERY

DB2UDB command with the -DETAIL parameter using

the same database, file, and date criteria to see if any

database partitions are available for restore.

Alternatively restore the DB2 UDB database from a

different backup.

ANS2706E A DB2 UDB request failed. TDP

function name : function-name TDP

function : function-desc TDP return code :

TSM-rc TDP reason code : TSM-reason

DB2 return code : DB2-rc DB2 reason

code : DB2-reason SQL-msg

Explanation: None.


User response: Contact the DB2 UDB administrator

with the SQL information provided in this message.

ANS2707E A failure occurred while initializing the

DB2 UDB appplication for db partition

part-num. The TDP return code is rc.

Explanation: None.


User response: Check the TDP error log for failures

prior to this message.

52


processing a DB2 UDB request. TDP



TSM-rc TDP file : file-name (line-number)

Explanation: None.




ANS2709W A duplicate disk ID ’disk-id’ was found

on the following DB2 database

partitions: partition ’partition-prefix1db-num1’ hostname ’host1’ partition

’partition-prefix1db-num1’ hostname ’host2’

These DB2 partitions cannot be restored

individually.

Explanation: Each DB2 database partition should have

it’s own set of physical resources and logical volume

groups. If the logical volume groups are shared by two

database partitions, an artificial dependency between

the two partitions is created at the logical volume

group level. If one DB2 database partition is restored

without restoring the other database partition, the latter

database partition could have information out of synch.

System action: Processing continues. The database

partition backup objects are marked so that they can

not be restored individually, in other words outside the

context of restoring the entire host or entire DB2

database.

User response: Contact the DB2 or storage

administrator to determine if the DB2 database

partitions can be segregated to their own volume

groups.

ANS2710W A duplicate disk ID ’disk-id’ was found

on the following DB2 database

partitions: partition ’partition-prefix1db-num1’ hostname ’host1’ partition

’partition-prefix1db-num1’ hostname ’host2’

The DB2 partitions and DB2 hosts listed

cannot be restored individually.

Explanation: Each DB2 database partition should have

it’s own set of physical resources and logical volume

groups. If the logical volume groups are shared by two

database partitions, an artificial dependency between

the two partitions is created at the logical volume

group level. If one DB2 database partition is restored

without restoring the other database partition, or if one

DB2 database host is restored without restoring the

other database host, the latter database partition or host

could have information out of synch.

System action: Processing continues. The database

partition and database host backup objects are marked

so that they can not be restored individually, in other

words outside the context of restoring the entire DB2

database.

User response: Contact the DB2 or storage

administrator to determine if the DB2 database

partitions and hosts can be segregated to their own

volume groups.

ANS2711W Unable to backup configuration files for

DB2 database backup ’db’.

Explanation: The configuration files that are used by

the TDP client for DB2 database backups could not be

processed. Since these files are not critical to the

database backup processing continues normally.


User response: Retry the operation. If the problem

persists contact the TDP administrator.

ANS2712E A non-critical, unexpected error was

encountered processing a DB2 UDB

request. TDP function name :

function-name TDP function : function-desc

TDP return code : TSM-rc TDP file :

file-name (line-number)

Explanation: None.





processing a DB2 UDB request. TDP



TSM-rc TDP explanation : TSM-msg TDP

file : file-name (line-number)

Explanation: None.




ANS2714W The management class ’mc’ specified for

the ’dest’ backup destination is invalid.

The default management class will be

used.

Explanation: None.


User response: Contact the TDP administrator to run

the configuration utility for DB2 UDB and specify a

valid management class.


ANS2715I The filespace ’filespace’ does not exist on

the server.

Explanation: The file system may not yet have been

created on the server or it might have been deleted.



ANS2716E A background copy process is still

pending on local hardware. A restore

operation cannot be initiated until the

background copy process is completed.

Explanation: None.


User response: Wait until the background copy

process completes and retry the restore operation.

ANS2717E The multi-node definition does not have

permission to delete its own backup

files from the server.

Explanation: All DB2 UDB commands require that the

multinode definition has permission to delete its own

backup files from the server in order to properly

reconcile the local backup repository with the server

backup repository.


User response: Have the TDP administrator update

the multinode definition so that it has permission to

delete its own backup files from the server. For

example, on the TDP administrative command-line

client:. dsmadmc update node <multinode name>

backdelete=yes

ANS2718E A previous incremental backup started

on datetime is still in progress.

Explanation: A new incremental local backup can not

be done until preivous incremental backup completes.


User response: Wait until previous backup completes

before starting another incremental local backup.

Alternatively, use different copyType value to perform

a local backup with full copy. TSM local backup policy

only allows one incremental and one full background

copy to be pending at any time, before local backup

resources are reused for a new backup version. A new

local backup would result in a backup with

background copy in pending state.

ANS2719E A previous backup started on ’datetime’,

is using the resources needed for new

backup is still pending.

Explanation: A new backup can not be done until

previous backup completes.


User response: Wait until previous backup completes

before starting another local backup. Alternatively, use

different copyType value to perform a local backup.

TSM local backup policy only allows one incremental

and one full background copy to be pending at any

time, before local backup resources are reused for a

new backup version. A new local backup would result

in a backup with background copy in pending state.

ANS2720E One or more background copies are still

in progress.

Explanation: A new backup can not be done until all

full background copies are completed.


User response: Wait until previous backups complete

before starting another local backup. Alternatively, use

different copyType value to perform a local backup.

TSM local backup policy only allows one incremental

and one full background copy to be pending at any

time, before local backup resources are reused for a

new backup version. A new local backup would result

in a backup with background copy in pending state.

ANS2721I A previous local backup version backup

date ’datetime’ copytype ’name’ has been

deleted for this backup operation (object

name=’filespace namepath-namefile-name’,

ID=’object-id:object-id’).

Explanation: The local resources needed for current

backup operation would be made available by expiring

a previous backup version referenced in the message as

defined in the local backup policy. Refer to TDP

documentation for additional information on local

backup policy.



ANS2722E There is not enough space in the local

repository to complete this backup.

Explanation: This space available in the local

repository is not enough to perform snapshot for this

backup operation. It could happen if there is more

number of local versions kept by the management class

than there is space allocated in the local repository at

configuration time or application configuration has

changed such that previously allocated space is not

enough.

54


User response: Please validate TSM configuration by

running the configuration wizard.

ANS2723I A local backup version backupdate

’datetime’ is deleted because background

copy operation has been cancelled

(object name=’/filespace

name/path-name/file-name’, ID =

’object-id:object-id’).

Explanation: The specified backup instance of the

named object has been deleted on the server and in

local repository because the background copy

operations for this backup version was cancelled. It is

no longer available for restore.



ANS2724E The version of IBM Enterprise Storage

Server is not supported.

Explanation: This product only supports IBM ESS

microcode level 2.3 and 2.4.

System action: Process stops.

User response: Ensure that ESS microcode level 2.3 or

2.4 is installed.

ANS2725W The backup DB2 UDB preview

command indicates there are not enough


Explanation: None.

System action: check the TDP error log for additional

information about the problem.

User response: Correct the problem and re-issue the

BACKUP DB2UDB -PREVIEW command.

ANS2726E The putenv command failed for path =

v1.

Explanation: There was not enough memory in the

environment to successfully set the environment.


User response: Close all unneeded applications and

try the operation again. For UNIX systems that support

resource limits, check to see if the memory resource

limit is too low by entering the following command:

ulimit -a

Based on the resulting data, you can ask the UNIX

system root user to increase resource limits so that it

will override the current default. The UNIX system root

user has the authority to increase resource limits.

ANS2727E ESS Lun ID v1 is not valid.

Explanation: Length of ESS LUN id must be 8

characters.


User response: Make sure the length of ESS Lun id is

8.

ANS2728E The ESS jar file v1 cannot be found.

Explanation: The Enterprise Storage Sub-system Copy

Services JAR file could not be located.


User response: In order to complete Enterprise

Storage Subsystem Copy Services functions the Copy

Services command line functions must be available.

Check the Copy Services command line is installed and

your Copy Services option setting is pointing to the

installation directory of the command line.

ANS2729E Operating system command ’command’

failed; rc=rc.

Explanation: None.


User response: Check the return code from the

operating system for more information about the

failure. Issue the failing command manually to see if

the same failure occurs.

ANS2730E The primary and secondary copy service

servers are down.

Explanation: None.


User response: Start at least one of the ESS copy

service servers. If copy server is already running, check

the value of java home specified during configuration

to make sure it is a valid path name of the directory

where JRE is installed on master backup node. Use

configuration wizard to update java home value for the

configuration.

ANS2731E Cannot open the ESS command output

file v1 for writing.

Explanation: Can’t open this file for writing.


User response: Make sure you have enough space on

your system and write permission to the file.


ANS2732E The ESS LUN ’Serial number string’ are

already in use.

Explanation: One or more LUNs specified in the

message are in use by other FlashCopy operation.

Therefore this FlashCopy operation can not continue.


User response: Release ESS LUN in order to reuse

them.

ANS2733I The backup DB2 UDB preview

command indicates there are sufficient


Explanation: None.



ANS2734E Withdraw command failed because a

TSM backup of this DB2UDB instance

is in progress using the same snapshot

resources.

Explanation: The snapshot established can not be

withdrawn because a ’TSM’ backup is in progress from

the same local backup snapshot.


User response: You must wait until the TSM backup

completes and retry the withdraw command.

Alternatively, you may cancel the TSM backup and

retry the withdraw command.

ANS2735E DB2 UDB is running on different

operating system versions. database

partition ’partition’: OS version ’os-1’

catalog partition: OS version ’os-2’

Explanation: DB2 UDB must be running on the same

operating system versions on all hosts.


User response: Upgrade the operating systems so that

all DB2 UDB hosts are running the same version.

ANS2736E An unexpected response was received

from a remote TDP file system agent.

verb : verb remote host : host return code

: rc reason code : rs msg. string :

msg-string

Explanation: None.




ANS2737E A DB2 UDB database server is not

available. DB2 instance name: instance

DB2 database name: db db partition :

part

Explanation: None.


User response: Contact the DB2 database

administrator to have the database server made

available and retry the operation.

ANS2738E The DB2 UDB log retain value is not set

to ’recovery’. DB2 instance name:

instance DB2 database name: db db

partition : part

Explanation: None.



administrator to have the log retain value set to

’recovery’.

ANS2739E The DB2 UDB user exit for archiving

logs is not enabled. DB2 instance name:

instance DB2 database name: db db

partition : part

Explanation: None.



administrator to have the user exits for archiving logs

enabled.

ANS2740E DB2 UDB is running different versions.

database partition ’partition’: version

’os-1’ catalog partition: version ’os-2’

Explanation: DB2 UDB must be running on the same

version on all hosts.


User response: Upgrade the DB2 UDB version so that

all DB2 UDB hosts are running the same version.

ANS2741I DB2 UDB configuration settings

’filename’ have either not been created

using the Configuration Wizard or they

are not readable. The TDP return code

is rc.

Explanation: DB2 UDB configuration settings are

required for the processing of DB2 UDB commands.

They have either not been created using the

Configuration Wizard or they do not have read

permission.

System action: DB2 UDB operations will fail.

56

User response: Use the Configuration Wizard to create

the DB2 UDB configuration settings.

ANS2742I Deleting local incremental backup

version.

ANS2743E Unable to read configuration file

information for configuration

’configname’.

Explanation: One or more of the TDP DB2 UDB

configuration files could not be read. Refer to the TDP

error log for additional information.


User response: Review the additional messages in the

TDP error log. Launch the TDP configuration wizard

from the DB2 UDB production host which contains the

catalog node to resolve the problem.

ANS2744I TESTFLAG DB2 enabled with the value

of ’value’.

Explanation: None.

System action: This message is informational.


ANS2745I Volume Group Configuration has been

modified.List of logical volumes added

to the Volume Group configuration of

the database since the time of

backup:’value’.

Explanation: Volume group configuration has been

changed since the time of backup by the addition of

new logical volumes.

System action: User will be prompted to select ″Yes″

to continue the restore operation, or to select ″No″ to

stop the restore.

User response: User can select ″Yes″ to continue the

restore operation, in which case the newly added

logical volumes will be deleted. Otherwise, he can

select ″No″ to stop the restore, backup the newly added

logical volumes and then retry the restore. Thus he will

be able to recover the newly added logical volumes

after the restore.

ANS2746I Volume Group Configuration has been

modified.List of physical volumes

added to the Volume Group

configuration of the database since the

time of backup:’value’.

Explanation: Volume group configuration has been

changed since the time of backup by the addition of

new physical volumes.

System action: User will be prompted to select ″Yes″

to continue the restore operation, or to select ″No″ to

stop the restore.

User response: User can select ″Yes″ to continue the

restore operation, in which case the newly added

physical volumes will be removed from the volume

group. User will have to add the physical volumes

once the restore operation is complete. Otherwise, he

can select ″No″ to stop the restore.

ANS2747I DB2 storage config has changed since

previous backup. Retrying to find local

resources for this backup.

Explanation: None.



ANS2748I Changing copyType to default ″any″ for

no-copy snapshot for TSM backup

operation.

Explanation: When backup destination is TSM,

snapshot copy type defaults to no-copy operation. The

is done to optimize performance of the snapshot

operation required for TSM backup.


User response: Do not specify ″copyType″ option for

TSM backups or use ″any″. This will allow TDP to pick

the appropriate default value of copyType.

ANS2749E The backup host ’backup_host’ listed in

the user FlashCopy target input file

cannot be found in the list of

configured backup hosts.

Explanation: The backup hosts specified in the user

FlashCopy target input file must be configured as

backup hosts.


User response: Check the configuration wizard to

determine which backup host names have been

configured. Ensure that the backup hosts specified in

the user FlashCopy target input file appear in the

configuration wizard. If the backup hosts do not appear

in the configuration wizard, either add the backup host

in the configuration wizard or specify a different

backup host name in the user FlashCopy target input

file.

ANS2750I func function invoked for DB2

configuration ’db_config’. backup

destination : backupdest copy type :

copytype preview : preview

Explanation: None.




ANS2751I Verifying multinode information.

Explanation: None.



ANS2752I Initializing DB2 UDB application on

part partition(s).

Explanation: None.



ANS2753I Establishing inter-client communication

with node node(s).

Explanation: None.



ANS2754I Establishing inter-client communication

session. NODENAME : node

MULTI-NODE NAME : multi-node

hostname : host TCP/IP address :

tcpaddr:tcpport

Explanation: None.



ANS2755I Established communications with DB2

catalog partition.

Explanation: None.



ANS2756I Querying database configuration

information from type partition(s).

Explanation: None.



ANS2757I Initializing DB2 UDB application on

backup hosts.

Explanation: None.



ANS2758I Established communications with

backup worker nodes.

Explanation: None.



ANS2759I Policy settings for backup destination

’dest’. Management class : mgmtclass

Backup copygroup : backup_cg Data

versions : data_vers

Explanation: None.



ANS2760I Querying database tablespaces from

database partitions.

Explanation: None.



ANS2761I Mapping database tablespaces to logical

volumes.

Explanation: None.



ANS2762I Mapping logical volumes to physical

entities.

Explanation: None.



ANS2763I Obtaining a list of target devices for

snapshot operation.

Explanation: None.



ANS2764I Initializing snapshot-provider-name

snapshot.

Explanation: None.



58

ANS2765I Quiescing the database partitions.

Explanation: None.



ANS2766I Creating snapshot-type-name snapshot.

Explanation: None.



ANS2767I Resuming the database partitions.

Explanation: None.



ANS2768I Collecting metadata files from each

database partition.

Explanation: None.



ANS2769I Distributing metadata files to backup

hosts.

Explanation: None.



ANS2770I Configuring snapshot volumes on

backup nodes.

Explanation: None.



ANS2771I Sending group objects for backup

destination ’dest’ to the server.

Explanation: None.



ANS2772I Local backup of DB2 UDB database

’dbname’ completed pending completion


Explanation: None.



ANS2773I Unconfiguring snapshot volumes.

Explanation: None.



ANS2774I Unconfiguring snapshot volumes on

backup nodes.

Explanation: None.



ANS2775I Starting the backup of TDP

configuration files for DB2 UDB

database ’’.

Explanation: None.



ANS2776I Moving data to TDP server for

’backup_type’ backup.

Explanation: None.



ANS2777I Monitoring image backup.

Explanation: None.



ANS2778I TSM backup of DB2 UDB database

’db-name’ completed successfully.

Explanation: None.



ANS2779I Restore requested for database

configuration ’config’. DB2 database :

db2db DB2 instance : dinst Backup size :

bsize Backup date : bdatetime Backup

destination : bdest Active state : activ

Explanation: None.




ANS2780I Withdraw requested for database

configuration ’config’. DB2 database :

db2db DB2 instance : dinst Backup size :

bsize Backup date : bdatetime Backup

destination : bdest Active state : activ

Explanation: None.



ANS2781I - Database ’db’ (object id objhi.objlo)

Explanation: None.



ANS2782I - Host ’host’ (object id objhi.objlo)

Explanation: None.



ANS2783I - Partition ’part’ (object id objhi.objlo)

Explanation: None.



ANS2784I Restoring local hardware configuration

file ’filename’.

Explanation: None.



ANS2785I Gathering current DB2 configuration for

’type’ restore.

Explanation: None.



ANS2786I Verifying database configuration

information for type partition(s).

Explanation: None.



ANS2787I Sending metadata files to worker nodes.

Explanation: None.



ANS2788I Verifying hardware configuration

information.

Explanation: None.



ANS2789I Verifying volume manager configuration

information.

Explanation: None.



ANS2790I Stopping the database manager.

Explanation: None.



ANS2791I Starting the database manager.

Explanation: None.



ANS2792I Local restore of DB2 UDB database

’dbname’ completed pending completion


Explanation: None.



ANS2793I TSM restore of DB2 UDB database

’dbname’ completed.

Explanation: None.



ANS2794I Monitoring image restore.

Explanation: None.



60

ANS2795I Withdraw of DB2 UDB database ’name’

backup completed successfully.

Explanation: None.



ANS2796I The DB2 UDB operation has terminated.

Explanation: None.



ANS2797I Current statistics for backup host ’host’:

Total number of volumes in request:

volumes Total number of volumes

completed: complet Total number of

volumes in progress: inprogr Total

number of volumes remaining: remaing

Currently processing volumes: process

Total number of bytes in request: totalda

Total number of bytes transferred: totaltr

Explanation: None.



ANS2798E Unable to start a session from client

node ’nodename’ multi-node ’multi-node’

to client at address ’ip-address:ip-port’.

The TDP return code is rc.

Explanation: None.



ANS2799E An error was encountered during a

session with another client. check the

TDP error log for any additional

information

Explanation: This message is reserved for DB2 UDB.

System action: Reserved.

User response: This message is reserved for DB2 UDB.

ANS13401W The entity name is invalid.

Explanation: A volume with this name could not be

found or is not suitable for server-free operations.

System action: Processing stopped.

User response: Specify the correct name.

ANS13402W name: A system call func failed with code

rc.

Explanation: Failed to get volume information.

System action:

User response: Contact your system administrator or

TDP administrator.

ANS13403W Cannot open the volume name for

reading. System error code err.

Explanation: The volume could not be opened for

reading.

System action:

User response: Contact your system administrator.

ANS13404W Error reading the volume name.

Explanation: The volume could not be read.

System action:


ANS13405W Unknown filesystem fs on volume name.

Explanation: The filesystem found on the volume is

not recognized.


User response: Contact your systems administrator.

ANS13406W Physical mapping of the volume name is

not supported.

Explanation: The logical volume layout is not

currently supported for physical mapping.

System action:

User response: Refer to the documentation for

information on what volume layouts are supported for

physical mapping.

ANS13407W name is not local.

Explanation: The drive or file system is not local and

is not suitable for image backup.

System action: Processing stopped.

User response: Specify a volume that is local.

ANS13408W The volume name contains bad blocks.

Explanation: The volume contains bad blocks and is

not suitable for server-free operations.

System action: Processing continues using

non-server-free data movement.



ANS13409W Error writing to the volume name.

Explanation: An error occurred while attempting to

write to the volume.

System action:


ANS13410E The operating system refused a TDP

request for memory allocation.

Explanation: TDP requires access to memory in order

to store information as processing proceeds. In this

case, more memory was requested than the operating

system would allocate. Possible reasons include:

The system is low on memory.

The process in which the program runs has

exceeded the maximum memory that it is allowed

to allocate.

Some other error condition occurred that caused the

program to think it is out of memory.

System action: TDP cannot complete the requested

operation.

User response: Close all unneeded applications and

try the operation again. If the operation still fails, try

dividing the task into several smaller units. For

example, if a file specification contains several high

level directories, run the TDP task serially for each

directory. If the TDP task is an incremental backup, use

the option ″-memoryefficientbackup=yes″.

For UNIX systems that support resource limits, check

to see if the memory resource limit is too low by

entering the following command: ulimit -a

Based on the resulting data, you can ask the UNIX

system root user to increase resource limits so that it

will override the current default. The UNIX system root

user has the authority to increase resource limits.

ANS13411E Invalid arguments were passed to

function name.

Explanation: The named function did not receive

correct arguments to proceed. Please check error log for

additional errors following this one for further

explanation.


User response: Retry the operation. If problem persists

contact your TDP administrator.

ANS13412E DiskMapper does not support name for

entity name.

Explanation: The requested function is not

implemented in DiskMapper at this time. Please report

this error to your TSM administrator.


User response: Contact your TDP administrator.

ANS13413I DiskMapper object ’name’ type ’name’ is

not valid.

Explanation: The named object is not valid on the

originating client system.


User response: Retry the operation. If the problem

persists, review the client error log for other messages

that might be related to this problem. Contact your

TDP administrator for additional help.

ANS13414I Disk ’name’ is not part of any container

defined on the system.

Explanation: None.

System action: None. This is informational message.


ANS13415E At least one of the disk containing data

for ’name’ has bad blocks.

Explanation: One or more physical disks containing

data blocks of the above object has bad blocks and the

requested operation can not continue.

System action: The system may find an alternative

method to complete the requested operation, please

check console log and error log for additional

information on corrective actions taken or suggested

user action.

User response: Depending on the operation TDP may

suggest an alternate way to complete the operation.

Check your error log, scheduler log, or console log for

additional information.

62

Appendix A. Alternative procedures

This chapter describes alternative procedures to adjust ACS for DB2 UDB to your

production environment. These procedures are:

v Configuring System Options Files to the Same Server

v Configuring Multiple Server Stanzas

v Editing Your Server Script

v Restoring hdisks for SDD

v Recovering a DB2 UDB Database from the Backup System

Configuring system options files to the same server

The following procedure demonstrates how to configure system options files

(dsm.sys) to point to the same Tivoli Storage Manager server. In these examples,

the client user options files (dsm.opt) in the /usr/tivoli/tsm/client/ba/bin and

/usr/tivoli/tsm/client/api/bin directories are defined for a server with a TCPIP

address of arrow.la.xyzcompany.com.

ba/bin Directory

Example: dsm.opt

servername tdpess

Do not change the server stanza name (servername) in the dsm.opt file after

completing a successful local backup (backupdestination=local). The query db2udb

and restore db2udb commands will fail if the server stanza name in the dsm.opt

file changes after completing a successful local backup.

Example: dsm.sys

servername tdpess

commmethod tcpip

tcpport 1500

tcpserveraddress arrow.la.xyzcompany.com


schedmode prompted

nodename db2udb1

api/bin Directory

Example: dsm.opt

servername tdpdb2

Do not change the server stanza name (servername) in the dsm.opt file after

completing a successful local backup (backupdestination=local). The query db2udb

and restore db2udb commands will fail if the server stanza name in the dsm.opt

file changes after completing a successful local backup.


Example: dsm.sys

servername tdpdb2

commmethod tcpip

tcpport 1500


passwordaccess prompt

nodename db2udb1

The servername option in the dsm.opt and dsm.sys files define server stanza

names only. The tcpserveraddress option controls which server is actually

contacted.

Configuring multiple server stanzas

To configure multiple server stanzas in the system options file (dsm.sys), copy the

option settings from the DB2 UDB dsm.sys file to the ACS for DB2 UDB dsm.sys

file. This is an example of a combined dsm.sys for a server with the name arrow:

servername tdphdw

commmethod tcpip

tcpport 1500



schedmode prompted

nodename db2udb1

servername tdpdb2

commmethod tcpip

tcpport 1500


passwordaccess prompt

nodename db2udb1

Restoring hdisks for SDD

After a backup is performed on a Backup System that has SDD installed, ACS for

DB2 UDB removes the hdisk and vpath devices that correspond to the Target

Volumes. In order to bring up the hdisk and vpath devices again, you must run

the AIX cfgmgr command for every path on the SDD device. The output from the

AIX lsvpcfg command may display fewer hdisk devices for the SDD device than

actually exist. You can restore all the hdisks to the vpath device by issuing the

following AIX commands for all of the Target Volumes:

1. Issue

rmdev -l <vpath#>

2. Issue

mkdev -l <vpath#>

3. Issue

lsvpcfg

All paths to the SDD device should now display.

64

Appendix B. Support information

If you have a problem with your IBM software, you want to resolve it quickly. This

section describes the following options for obtaining support for IBM software

products:

v “Searching knowledge bases”

v “Obtaining fixes”

v “Receiving weekly support updates” on page 66

v “Contacting IBM Software Support” on page 67

Searching knowledge bases

You can search the available knowledge bases to determine whether your problem

was already encountered and is already documented.

Searching the information center

IBM provides extensive documentation that can be installed on your local

computer or on an intranet server. You can use the search function of this

information center to query conceptual information, instructions for completing

tasks, and reference information.

Searching the Internet

If you cannot find an answer to your question in the information center, search the

Internet for the latest, most complete information that might help you resolve your

problem.

To search multiple Internet resources for your product, go to this product support

web site: http://www.ibm.com/software/sysmgmt/products/support/IBMTivoliStorageManager.html and look for the section to search the support

knowledge base. From this section, you can search a variety of resources including:

v IBM technotes

v IBM downloads

v IBM Redbooks™

v Forums and newsgroups

You can also search the IBM Tivoli Storage Manager: Problem Determination Guide for

helpful diagnostic information at this Web site:

http://publib.boulder.ibm.com/infocenter/tivihelp/v1r1/topic/com.ibm.itsmm.doc/update/main.html

Obtaining fixes

A product fix might be available to resolve your problem. To determine what fixes

are available for your IBM software product, follow these steps:

1. Go to the IBM Software Support Web site at

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

2. Click Downloads and drivers in the Support topics section.

3. Select the Software category.

4. Select a product in the Sub-category list.






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

5. In the Find downloads and drivers by product section, select one software

category from the Category list.

6. Select one product from the Sub-category list.

7. Type more search terms in the Search within results if you want to refine your

search.

8. Click Search.

9. From the list of downloads returned by your search, click the name of a fix to

read the description of the fix and to optionally download the fix.

For more information about the types of fixes that are available, see the IBM

Software Support Handbook at

http://techsupport.services.ibm.com/guides/handbook.html.

Receiving weekly support updates

To receive weekly e-mail notifications about fixes and other software support news,

follow these steps:

1. Go to the IBM Software Support Web site at

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

2. Click My support in the upper right corner of the page.

3. If you have already registered for My support, sign in and skip to the next

step. If you have not registered, click register now. Complete the registration

form using your e-mail address as your IBM ID and click Submit.

4. Click Edit profile.

5. In the Products list, select Software. A second list is displayed.

6. In the second list, select the product segment, Storage Management. A third

list is displayed.

7. In the third list, select the product sub-segment, Data Protection. A list of

applicable products is displayed.

8. Select the products for which you want to receive updates, for example, IBM

Tivoli Storage Manager for Advanced Copy Services for DB2 UDB.

9. Click Add products.

10. After selecting all products that are of interest to you, click Subscribe to email

on the Edit profile tab.

11. Select Please send these documents by weekly email.

12. Update your e-mail address as needed.

13. In the Documents list, select Software.

14. Select the types of documents that you want to receive information about.

15. Click Update.

If you experience problems with the My support feature, you can obtain help in

one of the following ways:

Online

Send an e-mail message to [email protected], describing your problem.

By phone

Call 1-800-IBM-4You (1-800-426-4968).

66

http://techsupport.services.ibm.com/guides/handbook.html

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

Contacting IBM Software Support

IBM Software Support provides assistance with product defects.

Before contacting IBM Software Support, your company must have an active IBM

software maintenance contract, and you must be authorized to submit problems to

IBM. The type of software maintenance contract that you need depends on the

type of product you have:

v For IBM distributed software products (including, but not limited to, Tivoli,

Lotus®, and Rational® products, as well as DB2® and WebSphere® products that

run on Windows® or UNIX® operating systems), enroll in Passport Advantage®

in one of the following ways:

Online

Go to the Passport Advantage Web site at

http://www.lotus.com/services/passport.nsf/WebDocs/Passport_Advantage_Home and click How to Enroll.

By phone

For the phone number to call in your country, go to the IBM Software

Support Web site at

http://techsupport.services.ibm.com/guides/contacts.html and click the

name of your geographic region.v For customers with Subscription and Support (S & S) contracts, go to the

Software Service Request Web site at

https://techsupport.services.ibm.com/ssr/login.

v For IBM eServer™ software products (including, but not limited to, DB2 and

WebSphere products that run in zSeries®, pSeries®, and iSeries™ environments),

you can purchase a software maintenance agreement by working directly with

an IBM sales representative or an IBM Business Partner. For more information

about support for eServer software products, go to the IBM Technical Support

Advantage Web site at http://www.ibm.com/servers/eserver/techsupport.html.

If you are not sure what type of software maintenance contract you need, call

1-800-IBMSERV (1-800-426-7378) in the United States. From other countries, go to

the contacts page of the IBM Software Support Handbook on the Web at

http://techsupport.services.ibm.com/guides/contacts.html and click the name of

your geographic region for phone numbers of people who provide support for

your location.

To contact IBM Software support, follow these steps:

1. “Determining the business impact”

2. “Describing problems and gathering information” on page 68

3. “Submitting problems” on page 68

Determining the business impact

When you report a problem to IBM, you are asked to supply a severity level.

Therefore, you need to understand and assess the business impact of the problem

that you are reporting. Use the following criteria:

Severity 1

The problem has a critical business impact. You are unable to use the

program, resulting in a critical impact on operations. This condition

requires an immediate solution.

Appendix B. Support information 67

http://www.lotus.com/services/passport.nsf/ WebDocs/Passport_Advantage_Home

http://www.lotus.com/services/passport.nsf/ WebDocs/Passport_Advantage_Home

http://techsupport.services.ibm.com/guides/contacts.html

https://techsupport.services.ibm.com/ssr/login

http://www.ibm.com/servers/eserver/techsupport.html


Severity 2

The problem has a significant business impact. The program is usable, but

it is severely limited.

Severity 3

The problem has some business impact. The program is usable, but less

significant features (not critical to operations) are unavailable.

Severity 4

The problem has minimal business impact. The problem causes little impact

on operations, or a reasonable circumvention to the problem was

implemented.

Describing problems and gathering information

When describing a problem to IBM, be as specific as possible. Include all relevant

background information so that IBM Software Support specialists can help you

solve the problem efficiently. To save time, know the answers to these questions:

v What software versions were you running when the problem occurred?

v Do you have logs, traces, and messages that are related to the problem

symptoms? IBM Software Support is likely to ask for this information.

v Can you re-create the problem? If so, what steps were performed to re-create the

problem?

v Did you make any changes to the system? For example, did you make changes

to the hardware, operating system, networking software, and so on.

v Are you currently using a workaround for the problem? If so, be prepared to

explain the workaround when you report the problem.

Submitting problems

You can submit your problem to IBM Software Support in one of two ways:

Online

Click Submit and track problems on the IBM Software Support site at

http://www.ibm.com/software/support/probsub.html. Type your

information into the appropriate problem submission form.

By phone

For the phone number to call in your country, go to the contacts page of

the IBM Software Support Handbook at

http://techsupport.services.ibm.com/guides/contacts.html and click the

name of your geographic region.

If the problem you submit is for a software defect or for missing or inaccurate

documentation, IBM Software Support creates an Authorized Program Analysis

Report (APAR). The APAR describes the problem in detail. Whenever possible,

IBM Software Support provides a workaround for you to implement until the

APAR is resolved and a fix is delivered. IBM publishes resolved APARs on the

IBM product support Web pages daily, so that other users who experience the

same problem can benefit from the same resolutions.

For more information about problem resolution, see Searching knowledge bases

and Obtaining fixes.

68

http://www.ibm.com/software/support/probsub.html


Notices

This information was developed for products and services offered in the U.S.A.

IBM may not offer the products, services, or features discussed in this document in

other countries. Consult your local IBM representative for information on the

products and services currently available in your area. Any reference to an IBM

product, program, or service is not intended to state or imply that only that IBM

product, program, or service may be used. Any functionally equivalent product,

program, or service that does not infringe any IBM intellectual property right may

be used instead. However, it is the user’s responsibility to evaluate and verify the

operation of any non-IBM product, program, or service.

IBM may have patents or pending patent applications covering subject matter

described in this document. The furnishing of this document does not give you

any license to these patents. You can send license inquiries, in writing, to:

IBM Director of Licensing

IBM Corporation

North Castle Drive

Armonk, NY 10504-1785 U.S.A.

For license inquiries regarding double-byte (DBCS) information, contact the IBM

Intellectual Property Department in your country or send inquiries, in writing, to:

IBM World Trade Asia Corporation

Licensing

2-31 Roppongi 3-chome, Minato-ku

Tokyo 106, Japan

The following paragraph does not apply to the United Kingdom or any other

country where such provisions are inconsistent with local law:

INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS

PUBLICATION ″AS IS″ WITHOUT WARRANTY OF ANY KIND, EITHER

EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED

WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS

FOR A PARTICULAR PURPOSE.

Some states do not allow disclaimer of express or implied warranties in certain

transactions, therefore, this statement might not apply to you.

This information could include technical inaccuracies or typographical errors.

Changes are periodically made to the information herein; these changes will be

incorporated in new editions of the publication. IBM may make improvements

and/or changes in the product(s) and/or the program(s) described in this

publication at any time without notice.

Any references in this information to non-IBM Web sites are provided for

convenience only and do not in any manner serve as an endorsement of those Web

sites. The materials at those Web sites are not part of the materials for this IBM

product and use of those Web sites is at your own risk.


IBM may use or distribute any of the information you supply in any way it

believes appropriate without incurring any obligation to you.

Licensees of this program who wish to have information about it for the purpose

of enabling: (i) the exchange of information between independently created

programs and other programs (including this one) and (ii) the mutual use of the

information which has been exchanged, should contact:

IBM Corporation

2Z4A/101

11400 Burnet Road

Austin, TX 78758 U.S.A.

Such information may be available, subject to appropriate terms and conditions,

including in some cases payment of a fee.

The licensed program described in this document and all licensed material

available for it are provided by IBM under terms of the IBM Customer Agreement,

IBM International Program License Agreement or any equivalent agreement

between us.

Trademarks

IBM, the IBM logo and the following terms are trademarks of the International

Business Machines Corporation in the United States, other countries, or both:

AIX

AS/400

DB2

DFS

DFSMS/MVS

DFSMShsm

DFSMSrmm

DPI


ESCON

eServer

FICON

FlashCopy

HACMP

Informix

iSeries

Lotus

Lotus 1-2-3

Lotus Approach

Lotus Domino

Lotus Notes

Magstar

MVS

NetView

OpenEdition

OS/2

OS/390

OS/400

Passport Advantage

pSeries

RACF

Rational

Redbooks

RS/6000

S/390

SANergy

SecureWay

StorageSmart

SystemView

Tivoli

Tivoli Enterprise Console

Tivoli Management Enterprise

TotalStorage

TME

VTAM

WebSphere

z/OS

zSeries

Intel, Intel Inside (logos), MMX and Pentium are trademarks of Intel Corporation

in the United States, other countries, or both.

Java and all Java-based trademarks are trademarks of Sun Microsystems, Inc. in the

United States, other countries, or both.

70

Microsoft, Windows, Windows NT, and the Windows logo are trademarks of

Microsoft Corporation in the United States, other countries, or both.

UNIX is a registered trademark of The Open Group in the United States and other

countries.

Linux is a trademark of Linus Torvalds in the United States, other countries, or

both.

Other company, product or service names may be trademarks or service marks of

others.

Notices 71

Index

AACS for DB2 UDB

functions 1, 2

installation requirementshardware 9, 12

software 10, 12

messages 49

options files 63

configuring multiple server

stanzas 64

configuring to same server 63

restore procedure 33

Bbooks

see publications viii

Cconventions

typeface ix

customer supportSee Software Support

Ddsm.opt

example 63

dsm.sysexample 63

Eeducation

see Tivoli technical training viii

examplesoptions files

dsm.opt 63

dsm.sys 63

Ffixes, obtaining 65

Hhardware

installation requirements 9, 12

Iinformation centers, searching for

problem resolution 65

installation requirementshardware 9, 12

SDD environment 23

installation requirements (continued)software 10, 12

Internetsearching for problem resolution 65

Kknowledge bases, searching for problem

resolution 65

Mmanuals

see publications viii

messages 49

multiple server stanzasconfiguration procedure 64

Oonline publications

accessing viii

options filesconfiguring multiple server

stanzas 64

configuring to same server 63

exampledsm.opt 63

dsm.sys 63

ordering publications viii

Pproblem determination

describing problems 68

determining business impact 67

submitting problems 68

publicationsaccessing online viii

ordering viii

Rrestore procedure

manual 33

SSDD

environment requirements 23

restoring hdisks 64

softwareinstallation requirements 10, 12

Software Supportcontacting 67

describing problems 68

determining business impact 67

receiving weekly updates 66

Software Support (continued)submitting problems 68

TTivoli software information center viii

Tivoli technical training viii

training, Tivoli technical viii

troubleshootingmessages 49

typeface conventions ix


��

Program Number: 5608-ACS

Printed in USA

GC32-1780-00