HP OpenView Storage Data Protector

Integration Guide
for IBM Applications:
Informix
DB2
Lotus Notes/Domino

Manual Edition: July 2006

Manufacturing Part Number: B6960-96009

Release A.06.00

© Copyright 2006 Hewlett-Packard Development Company, L.P.

Legal Notices
©Copyright 2006 Hewlett-Packard Development Company, L.P.
Hewlett-Packard Company makes no warranty of any kind with regard
to this material, including, but not limited to, the implied warranties of
merchantability and fitness for a particular purpose. Hewlett-Packard
shall not be liable for errors contained herein or for incidental or
consequential damages in connection with the furnishing, performance,
or use of this material.
This document contains proprietary information, which is protected by
copyright. No part of this document may be photocopied, reproduced, or
translated into another language without the prior written consent of
Hewlett-Packard. The information contained in this document is subject
to change without notice.
Microsoft® and MS Windows®, Windows® and Windows NT® are U.S.
registered trademarks of Microsoft Corporation.
Oracle® is a registered U.S. trademark of Oracle Corporation, Redwood
City, California.
UNIX® is a registered trademark of The Open Group
Hewlett-Packard Company shall not be liable for technical or editorial
errors or omissions contained herein. The information is provided “as is”
without warranty of any kind and is subject to change without notice.
The warranties for Hewlett-Packard Company products are set forth in
the express limited warranty statements for such products. Nothing
herein should be construed as constituting an additional warranty.

ii
 Contents
1. Integrating Informix Server and Data Protector
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
Integration Concepts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Configuring the Integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Before You Begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Cluster-Aware Clients . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Configuring Informix Server Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Configuring Informix Instances . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Checking the Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
What You Must Back Up as Filesystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Creating Backup Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Modifying Backup Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Scheduling Backup Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Previewing Backup Sessions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Starting Backup Sessions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Restore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Restore Methods . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Before You Begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Finding Information for Restore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Restoring Using the Data Protector GUI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Restoring Using the Data Protector CLI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Restoring Using Informix Server Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Restoring to Another Informix Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Restoring Using Another Device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Monitoring Sessions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Before You Begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Checks and Verifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

2. Integrating IBM DB2 UDB and Data Protector

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
Integration Concept . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Configuring the Integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
Before You Begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

iii
Contents
Partitioned Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
Configuring DB2 Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
Configuring DB2 Instances . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
Checking the Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
Physically Partitioned Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
Creating Backup Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
Modifying Backup Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
Scheduling Backup Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
Previewing Backup Sessions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
Starting Backup Sessions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
Restore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
Restoring Using the Data Protector GUI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
Restoring Using the Data Protector CLI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
Restoring to a New Database or Another DB2 Instance . . . . . . . . . . . . . . . . . . . . . . 68
Restore in a Partitioned Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
Monitoring Sessions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
Before You Begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
Checks and Verifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76

3. Integrating Lotus Notes/Domino Server and Data Protector

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
Integration Concepts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
Configuring the Integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
Before You Begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
Transaction Logging of Lotus Notes/Domino Server . . . . . . . . . . . . . . . . . . . . . . . . . 84
Creating a Link to the Lotus C API Library . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
Configuring Lotus Notes/Domino Server Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
Configuring the Data Protector Lotus Notes/Domino Server Integration. . . . . . . . . 88
Checking the Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
What Is Backed Up? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
What Is Not Backed Up? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
Creating Backup Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
Modifying Backup Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97

iv
 Contents
Scheduling Backup Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
Previewing Backup Sessions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
Starting Backup Sessions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
Restore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
Restoring Lotus Notes/Domino Server Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
Restore Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
Monitoring Sessions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
Before You Begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
Checking the Lotus Notes/Domino Server Side . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
Checks and Verifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110
Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113

Glossary

Index

v
Contents

vi
 Printing History
Manual updates may be issued between editions to correct errors or
document product changes. To ensure that you receive updated or new
editions, subscribe to the appropriate product support service. See your
HP sales representative for details.
Table 1 Edition History

Part Number Manual Edition Product

B6960-90110 October 2004 Data Protector Release

A.05.50

B6960-96009 July 2006 Data Protector Release

A.06.00

vii
viii
 Conventions
The following typographical conventions are used in this manual.
Table 2

Convention Meaning Example

Italic Book or manual Refer to the HP OpenView

titles, and manual Storage Data Protector
page names Integration Guide for more
information.

Provides emphasis You must follow these steps.

Specifies a variable At the prompt type:

that you must supply rlogin your_name where
when entering a you supply your login name.
command

Bold New terms The Data Protector Cell

Manager is the main ...

Computer Text and items on the The system replies: Press

computer screen Enter

Command names Use the grep command ...

File and directory /usr/bin/X11

names

Process names Check to see if Data

Protector Inet is
running.

Window/dialog box In the Backup Options

names dialog box...

Text that you must At the prompt, type: ls -l

enter

Keycap Keyboard keys Press Return.

ix
 Data Protector provides a cross-platform (Windows and UNIX) graphical
user interface. Refer to the online Help for information about the Data
Protector graphical user interface.

Figure 1 Data Protector Graphical User Interface

x
 Contact Information
General General information about Data Protector can be found at
Information
http://www.hp.com/go/dataprotector

Technical Support Technical support information can be found at the HP Electronic

Support Centers at
http://www.itrc.hp.com
Information about the latest Data Protector patches can be found at
http://www.itrc.hp.com
HP does not support third-party hardware and software. Contact the
respective vendor for support.

Documentation Your comments on the documentation help us to understand and meet

Feedback your needs. You can provide feedback at
[email protected]

Training For information on currently available HP OpenView training, see the

Information HP OpenView World Wide Web site at
http://www.openview.hp.com/training/
Follow the links to obtain information about scheduled classes, training
at customer sites, and class registration.

xi
xii
 Data Protector Documentation
Data Protector documentation comes in the form of manuals and online
Help.

Manuals Data Protector manuals are available in printed format and in PDF
format. Install the PDF files during the Data Protector setup procedure
by selecting the User Interface component on Windows or the
OB2-DOCS component on UNIX. Once installed, the manuals reside in the
<Data_Protector_home>\docs directory on Windows and in the
/opt/omni/doc/C/ directory on UNIX. You can also find the manuals in
PDF format at http://www.hp.com/support/manuals
HP OpenView Storage Data Protector Concepts Guide
This manual describes Data Protector concepts and provides background
information on how Data Protector works. It is intended to be used with
the task-oriented online Help.
HP OpenView Storage Data Protector Installation and Licensing
Guide
This manual describes how to install the Data Protector software, taking
into account the operating system and architecture of your environment.
This manual also gives details on how to upgrade Data Protector, as well
as how to obtain the proper licenses for your environment.
HP OpenView Storage Data Protector Troubleshooting Guide
This manual describes how to troubleshoot problems you may encounter
when using Data Protector.
HP OpenView Storage Data Protector Disaster Recovery Guide
This manual describes how to plan, prepare for, test and perform a
disaster recovery.

xiii
HP OpenView Storage Data Protector Integration Guide
This manual describes how to configure and use Data Protector to back
up and restore various databases and applications. It is intended for
backup administrators or operators. There are four versions of this
manual:

• HP OpenView Storage Data Protector Integration Guide for Microsoft

Applications: SQL Server, Exchange Server, and Volume Shadow Copy
Service
This manual describes the integrations of Data Protector with the
following Microsoft applications: Microsoft Exchange Server
2000/2003, Microsoft SQL Server 7/2000/2005, and Volume Shadow
Copy Service.
• HP OpenView Storage Data Protector Integration Guide for Oracle
and SAP
This manual describes the integrations of Data Protector with Oracle,
SAP R3, and SAP DB.
• HP OpenView Storage Data Protector Integration Guide for IBM
Applications: Informix, DB2, and Lotus Notes/Domino
This manual describes the integrations of Data Protector with the
following IBM applications: Informix Server, IBM DB2, and Lotus
Notes/Domino Server.
• HP OpenView Storage Data Protector Integration Guide for Sybase,
Network Node Manager, and Network Data Management Protocol
This manual describes the integrations of Data Protector with
Sybase, Network Node Manager, Network Data Management
Protocol, and VMware.
HP OpenView Storage Data Protector Integration Guide for HP
OpenView
This manual describes how to install, configure, and use the integration
of Data Protector with HP OpenView Service Information Portal, and HP
OpenView Reporter. It is intended for backup administrators. It
discusses how to use the OpenView applications for Data Protector
service management.

xiv
HP OpenView Storage Data Protector Integration Guide for HP
OpenView Operations for UNIX
This manual describes how to monitor and manage the health and
performance of the Data Protector environment with HP OpenView
Operations (OVO), HP OpenView Service Navigator, and HP OpenView
Performance (OVP) on UNIX.
HP OpenView Storage Data Protector Integration Guide for HP
OpenView Operations for Windows
This manual describes how to monitor and manage the health and
performance of the Data Protector environment with HP OpenView
Operations (OVO), HP OpenView Service Navigator, and HP OpenView
Performance (OVP) on Windows.
There are two versions of the manual:

• for OVO 7.1x, 7.2x

• for OVO 7.5
HP OpenView Storage Data Protector Zero Downtime Backup
Concepts Guide
This manual describes Data Protector zero downtime backup and instant
recovery concepts and provides background information on how Data
Protector works in a zero downtime backup environment. It is intended
to be used with the task-oriented HP OpenView Storage Data Protector
Zero Downtime Backup Administrator’s Guide and the HP OpenView
Storage Data Protector Zero Downtime Backup Integration Guide.
HP OpenView Storage Data Protector Zero Downtime Backup
Administrator’s Guide
This manual describes how to configure and use the integration of Data
Protector with HP StorageWorks Virtual Array, HP StorageWorks
Enterprise Virtual Array, EMC Symmetrix Remote Data Facility and
TimeFinder, and HP StorageWorks Disk Array XP. It is intended for
backup administrators or operators. It covers the zero downtime backup,
instant recovery, and the restore of filesystems and disk images.
HP OpenView Storage Data Protector Zero Downtime Backup
Integration Guide
This manual describes how to configure and use Data Protector to
perform zero downtime backup, instant recovery, and standard restore of
Oracle, SAP R/3, Microsoft Exchange Server 2000/2003, and Microsoft

xv
 SQL Server 2000 databases. The manual also describes how to configure
and use Data Protector to perform backup and restore using the
Microsoft Volume Shadow Copy Service.
HP OpenView Storage Data Protector MPE/iX System User Guide
This manual describes how to configure MPE/iX clients and how to back
up and restore MPE/iX data.
HP OpenView Storage Data Protector Media Operations User's
Guide
This manual provides tracking and management of offline storage
media. It is intended for network administrators responsible for
maintaining and backing up systems. It describes the tasks of installing
and configuring the application, performing daily media operations and
producing reports.
HP OpenView Storage Data Protector Product Announcements,
Software Notes, and References
This manual gives a description of new features of HP OpenView Storage
Data Protector A.06.00. It also provides information on supported
configurations (devices, platforms and online database integrations,
SAN, and ZDB), required patches, and limitations, as well as known
problems and workarounds. An updated version of the supported
configurations is available at http://www.hp.com/support/manuals
There are also four other Product Announcements, Software Notes and
References, which serve a similar purpose for the following:

• OVO UNIX integration

• OVO 7.1x/7.2x Windows integration
• OVO 7.5 Windows integration
• Media Operations

Online Help Data Protector provides context-sensitive (F1) Help and Help Topics for
Windows and UNIX platforms.

xvi
Documentation Map
Abbreviations
Abbreviations in the documentation map that follows are explained
below. The manual titles are all preceded by the words “HP OpenView
Storage Data Protector”

Abbreviation Manual
CLI Command Line Interface Reference Guide
Concepts Concepts Guide
DR Disaster Recovery Guide
GS Getting Started Guide
Help Online Help
IG-IBM Integration Guide—IBM Applications
IG-MS Integration Guide—Microsoft Applications
IG-O/S Integration Guide—Oracle, SAP R/3, and
SAP DB/MaxDB
IG-OV Integration Guide—HP OpenView Service Information
Portal/OpenView Reporter
IG-OVOU Integration Guide—HP OpenView Operations, UNIX
IG-OVOW Integration Guide—HP OpenView Operations 7.1x,
7.2x, Windows
IG-OVOW Integration Guide—HP OpenView Operations 7.5,
Windows
IG-Var Integration Guide—Sybase, Network Node Manager,
NDMP and VMware
Install Installation and Licensing Guide
MO GS Media Operations Getting Started Guide
MO RN Media Operations Product Announcements, Software
Notes, and References
MO UG Media Operations User Guide
MPE/iX MPE/iX System User Guide

xvii
 Abbreviation Manual
PA Product Announcements, Software Notes, and
References
Trouble Troubleshooting Guide
ZDB Admin ZDB Administrator's Guide
ZDB Concpt ZDB Concepts Guide
ZDB IG ZDB Integration Guide

Map
The following table shows where to find information of different kinds.
Shaded squares are a good place to look first.

Integration ZDB MO
Guides
Concepts

Trouble

MPE/iX
Concpt
Admin
OVOW
Install

OVOU
Help

User
IBM

CLI
Var
O/S
MS
DR

OV
GS

GS
PA

PA
IG
Backup X X X X X X X X X X X
CLI X
Concepts/Techniques X X X X X X X X X X X X X
Disaster Recovery X X X
Installation/Upgrade X X X X X X X X X X
Instant Recovery X X X X X
Licensing X X X X
Limitations X X X X X X X X X X
New features X X X
Planning strategy X X X X
Procedures/Tasks X X X X X X X X X X X X X X
Recommendations X X X X
Requirements X X X X X X X X X X
Restore X X X X X X X X X X
Support matrices X
Supported configurations X
Troubleshooting X X X X X X X X X X

xviii
Integrations
Look in these manuals for details of the following integrations:

Integration Guide
HP OpenView Operations (OVO) IG-OVOU, IG-OVOW
HP OpenView Reporter (OVR) IG-OV
HP OpenView Reporter Light IG-OVOW
HP OpenView Service Information Portal IG-OV
(OVSIP)
HP StorageWorks Disk Array XP all ZDB
HP StorageWorks Enterprise Virtual Array all ZDB
(EVA)
HP StorageWorks Virtual Array (VA) all ZDB
IBM DB2 UDB IG-IBM
Informix IG-IBM
Lotus Notes/Domino IG-IBM
Media Operations MO User
MPE/iX System MPE/iX
Microsoft Exchange Servers IG-MS, ZDB IG
Microsoft Exchange Single Mailbox IG-MS
Microsoft SQL Servers IG-MS, ZDB IG
Microsoft Volume Shadow Copy Service (VSS) IG-MS, ZDB IG
NDMP Server IG-Var
Network Node Manager (NNM) IG-Var
Oracle IG-O/S
Oracle ZDB ZDB IG
SAP DB IG-O/S
SAP R/3 IG-O/S, ZDB IG
Sybase IG-Var
Symmetrix (EMC) all ZDB
VMware IG-Var

xix
xx
In This Book
This guide describes how to configure and use Data Protector with IBM
applications.

Audience
It is intended for backup administrators responsible for planning, setting
up, and maintaining network backups. It assumes you are familiar with:

• Basic Data Protector functionality

• Database administration
Conceptual information can be found in the HP OpenView Storage Data
Protector Concepts Guide, which is recommended to fully understand the
fundamentals and the model of Data Protector.

xxi
Organization
The manual is organized as follows:
Chapter 1 “Integrating Informix Server and Data Protector” on
page 1.
Chapter 2 “Integrating Lotus Notes/Domino Server and Data
Protector” on page 79.
Chapter 3 “Integrating IBM DB2 UDB and Data Protector” on
page 45.
Glossary Definition of terms used in this manual.

xxii
1 Integrating Informix Server and
Data Protector

Chapter 1 1
 Integrating Informix Server and Data Protector
Introduction

Introduction
This chapter explains how to configure and use the Data Protector
Informix Server integration. It describes the concepts and methods you
need to understand to back up and restore Informix Server database
objects (dbobjects).
Data Protector integrates with the Informix Dynamic Server (Informix
Server) to back up dbobjects online. During backup, a database server
(Informix instance) is online and actively used.
Data Protector offers interactive and scheduled backups of the following
types:
Table 1-1 Informix Server Backup Types

Full Full backup (level 0).

Incr1 Incremental backup (level 1). Backs up changes since the

last Full backup.

Incr2 Incremental backup (level 2). Backs up changes since the

last Incr1 backup.

Data Protector offers two types of restore:

Table 1-2 Informix Server Restore Types

Complete Restore from any backup. ON-Bar restores dbobjects

database restore concurrently and replays the logical logs once.

Whole-system Restore from a whole-system backup. ON-Bar restores

restore the whole system sequentially with or without restoring
the logical logs. Whole-system restore is appropriate for
small systems, when you do not need to restore logs, for
disaster recovery, or when restoring to another client.

You can also back up and restore dbobjects using the Informix Server
onbar command.
This chapter provides information specific to the Data Protector Informix
Server integration. For general Data Protector procedures and options,
see online Help.

2 Chapter 1
 Integrating Informix Server and Data Protector
Integration Concepts

Integration Concepts
Data Protector integrates with the Informix Server through the Data
Protector Database Library based on a common library called Data
Protector BAR (Backup And Restore). The Data Protector Database
Library channels communication between the Data Protector Session
Manager, and, via the XBSA interface, the Informix Server ON-Bar
utility. Figure 1-1 shows the architecture of the Data Protector Informix
Server integration.

Figure 1-1 Data Protector Informix Server Integration Architecture

Table 1-3 Legend

SM Data Protector Session Manager: Backup Session Manager

during backup and Restore Session Manager during restore.

ON-Bar ON-Bar executes backup and restore requests from Data

Protector and from the Informix Server command line.

Chapter 1 3
 Integrating Informix Server and Data Protector
Integration Concepts

Table 1-3 Legend

XBSA X/Open Backup Services Application Programmer’s Interface,

through which ON-Bar and Data Protector exchange control
and data.

Database A set of Data Protector executables that enable data transfer

Library between an Informix instance and Data Protector.

MA Data Protector General Media Agent.

Backup A list of objects to be backed up, backup devices, and options

Specification to be used.

IDB The Data Protector Internal Database.

Backup is always executed on the Informix Server system via the

Informix Server ON-Bar utility. ON-Bar communicates backup and
restore requests to the Informix instance.
While an Informix instance is responsible for read/write operations to
disk, Data Protector reads from and writes to devices and manages
media.

4 Chapter 1
 Integrating Informix Server and Data Protector
Configuring the Integration

Configuring the Integration

You need to configure an Informix Server user and every Informix
instance you intend to back up or restore.

Prerequisites
• Ensure that you have correctly installed and configured Informix
Server.

— For supported versions, platforms, devices, and other information,

see the HP OpenView Storage Data Protector Product
Announcements, Software Notes, and References or
http://www.hp.com/support/manuals.
— For information on installing, configuring, and using Informix
Server, see the Informix Server online documentation.
• Ensure that you have correctly installed Data Protector. On how to
install Data Protector in various architectures, see the HP OpenView
Storage Data Protector Installation and Licensing Guide.
Every Informix Server system you intend to back up from or restore
to must have the Data Protector Informix Integration component
installed.

Before You Begin

✓ Configure devices and media for use with Data Protector.
✓ To test whether the Informix Server system and the Cell Manager
communicate properly, configure and run a Data Protector filesystem
backup and restore on the Informix Server system.
✓ Windows only: Change the Data Protector Inet service account.
Stop the service and restart it as user informix. For information, see
the online Help index: “changing Data Protector Inet account”.

Cluster-Aware Clients
Configure Informix instances only on one cluster node, since the
configuration files reside on the Cell Manager.

Chapter 1 5
Integrating Informix Server and Data Protector
Configuring the Integration

If you intend to use the Data Protector CLI, set the Data Protector
environment variable OB2BARHOSTNAME to the virtual server name as
follows:
Windows: set OB2BARHOSTNAME=<virtual_server_name>
UNIX: export OB2BARHOSTNAME=<virtual_server_name>

Configuring Informix Server Users

On UNIX, add the Informix Server administrator to the Data Protector
admin or operator user group. For information, see the online Help
index: “adding users”.
This user is typically informix or root in the group informix. To
determine it, check the owner of the Informix Server onbar_d file.
This chapter assumes that your Informix Server user is informix in the
group informix.

Configuring Informix Instances

You need to provide Data Protector with configuration parameters for
the Informix instance:

• Name of the Informix instance.

• Pathname of the Informix Server home directory.
• Windows: Name of the system with the sqlhosts entry in the
Windows Registry.
UNIX: Pathname of the sqlhosts file.
• Name of the Informix instance ONCONFIG file.
Data Protector then creates the Informix instance configuration file on
the Cell Manager and verifies the connection to the instance.
To configure an Informix instance, use the Data Protector GUI or CLI.

Before You Begin

✓ Ensure that the Informix instance is online.

Using the Data Protector GUI

1. In the Context List, click Backup.

6 Chapter 1
 Integrating Informix Server and Data Protector
Configuring the Integration

2. In the Scoping Pane, expand Backup Specifications, right-click

Informix Server, and click Add Backup.
3. In the Create New Backup dialog box, click OK.
4. In Client, select the Informix Server system. In a cluster
environment, select the virtual server.
In Application database, type the Informix instance name.
UNIX only: Type informix in both Username and Group name.

Figure 1-2 Specifying an Informix Instance

Click Next.
5. In Informix Server home directory, specify the pathname of the
Informix Server home directory.
In Full pathname of sqlhosts file, type the following:
Windows: Name of the system with the sqlhosts entry in the
Windows Registry. Use the UNC notation, for example:
\\computer_name.
UNIX: Pathname of the sqlhosts file.

Chapter 1 7
 Integrating Informix Server and Data Protector
Configuring the Integration

In Name of ONCONFIG file, type the name of the Informix instance

ONCONFIG file, located in the following directory:
Windows: <INFORMIXDIR>\etc
UNIX: <INFORMIXDIR>/etc

Figure 1-3 Configuring an Informix Instance (Windows)

Figure 1-4 Configuring an Informix Instance (UNIX)

Click OK.

8 Chapter 1
 Integrating Informix Server and Data Protector
Configuring the Integration

6. If an error occurs, click Details or see “Troubleshooting” on page 39.

7. The Informix instance is configured. Exit the GUI or proceed with
creating the backup specification at step 6 on page 14.

Using the Data Protector CLI

Log in to the Informix Server system as user informix. From the
directory:
Windows: <Data_Protector_home>\bin
HP-UX and Solaris: /opt/omni/lbin
Other UNIX: /usr/omni/bin/
run:
On Windows:
perl -I..\lib\perl util_informix.pl -CONFIG <INFORMIXSERVER>
<INFORMIXDIR> <sqlhosts> <ONCONFIG>
On UNIX:
util_informix.pl -CONFIG <INFORMIXSERVER> <INFORMIXDIR>
<sqlhosts> <ONCONFIG>

Parameter Description
<INFORMIXSERVER> Name of the Informix instance.
<INFORMIXDIR> Pathname of the Informix Server home directory.
<sqlhosts> Windows: Name of the system with the sqlhosts
entry in the Windows Registry. Use the UNC notation,
for example: \\computer_name.
UNIX: Pathname of the sqlhosts file.
<ONCONFIG> Name of the Informix instance ONCONFIG file.
Successful configuration displays the message *RETVAL*0.

Chapter 1 9
 Integrating Informix Server and Data Protector
Configuring the Integration

Figure 1-5 Configuring an Informix Instance (Windows)

Figure 1-6 Configuring an Informix Instance (HP-UX, Solaris)

Handling Errors If an error occurs, the error number is displayed in

the form *RETVAL*<error_number>.
To get the error description:
Windows: On the Cell Manager, see the file
<Data_Protector_home>\help\enu\Trouble.txt
HP-UX and Solaris: Run:
/opt/omni/lbin/omnigetmsg 12 <error_number>
Other UNIX: Run:
/usr/omni/bin/omnigetmsg 12 <error_number>

Checking the Configuration

You can check the configuration of an Informix instance after you have
created at least one backup specification for the Informix instance. Use
the Data Protector GUI or CLI.

10 Chapter 1
 Integrating Informix Server and Data Protector
Configuring the Integration

Using the Data Protector GUI

1. In the Context List, select Backup.

2. In the Scoping Pane, expand Backup Specifications and then
Informix Server. Click the backup specification to display the
Informix instance to be checked.
3. Right-click the Informix instance and click Check configuration.

Using the Data Protector CLI

Log in to the Informix Server system as user informix. From the
directory:
Windows: <Data_Protector_home>\bin
HP-UX and Solaris: /opt/omni/lbin
Other UNIX: /usr/omni/bin/
run:
On Windows:
perl -I..\lib\perl util_informix.pl -CHKCONF
<INFORMIXSERVER>
On UNIX:
util_informix.pl -CHKCONF <INFORMIXSERVER>
where <INFORMIXSERVER> is the name of the Informix instance.

Chapter 1 11
 Integrating Informix Server and Data Protector
Configuring the Integration

Figure 1-7 Checking Configuration (Windows)

Figure 1-8 Checking Configuration (UNIX)

A successful configuration check displays the message *RETVAL*0.

If an error occurs, the error number is displayed in the form
*RETVAL*<error_number>. On how to get the error description, see
“Handling Errors” on page 10.

12 Chapter 1
 Integrating Informix Server and Data Protector
Backup

Backup
The integration provides online database backup of the following types:
Table 1-4 Informix Server Backup Types

Full Full backup (level 0).

Incr1 Incremental backup (level 1). Backs up changes since the

last Full backup.

Incr2 Incremental backup (level 2). Backs up changes since the

last Incr1 backup.

For details on these types and on ON-Bar, see the Backup and Restore
Guide of Informix Server.

What You Must Back Up as Filesystem

ON-Bar backs up all dbobjects except the following, which you must back
up using a filesystem backup:
Table 1-5 What Needs to Be Backed Up as Filesystem

Object Location

ONCONFIG file Windows:

<INFORMIXDIR>\etc
oncfg_<SERVERNAME>.<SERVERNUM> file
UNIX:
Emergency boot file, an Informix Server <INFORMIXDIR>/etc
configuration file called ixbar.<server_id>,
where <server_id> is the value of the
SERVERNUM configuration parameter.

UNIX only: the sqlhosts file

Simple-large-object data in blobspaces disks or optical platters

Chapter 1 13
 Integrating Informix Server and Data Protector
Backup

IMPORTANT How often you need to back up these objects depends on how frequently
they change. However, back up the emergency boot file at least daily and
always after a critical dbspace backup.

What Does Not Need to Be Backed Up?

ON-Bar does not back up the following items because it automatically
re-creates them during a restore:

• Dbspace pages allocated to the Informix instance but not yet allocated
to a tblspace extent.
• Mirror chunks, if the corresponding primary chunks are accessible.
• Temporary dbspaces.

Creating Backup Specifications

Create a backup specification using the Data Protector Manager.

1. In the Context List, click Backup.

2. In the Scoping Pane, expand Backup Specifications, right-click
Informix Server, and click Add Backup.
3. In the Create New Backup dialog box, click OK.
4. In Client, select the Informix Server system. In a cluster
environment, select the virtual server.
In Application database, select the Informix instance to be backed
up.
UNIX only: Type informix in both Username and Group name.
Click Next.
5. If the Informix instance is not configured yet for use with Data
Protector, the Configure Informix dialog box is displayed.
Configure it as described in “Configuring Informix Instances” on
page 6.
6. Select the dbobjects to be backed up. For a whole-system backup,
select all dbobjects.

14 Chapter 1
 Integrating Informix Server and Data Protector
Backup

Figure 1-9 Selecting Backup Objects

Click Next.
7. Select devices to use for the backup.
To specify device options, right-click the device and click Properties.
Specify the number of parallel backup streams in the Concurrency
tab and the media pool you will use.

NOTE Except for whole-system backups, ON-Bar backs up and restores

dbobjects concurrently, creating a new process for each object. The
number of processes is limited by the Informix Server BAR_MAX_BACKUP
configuration parameter. Set the Informix configuration parameter
BAR_MAX_BACKUP to the Data Protector concurrency.

To specify which resource types can be backed up to the device, click

the Informix tab, select the desired resource types, and click OK. See
Figure 1-10 on page 16.
Ensure that the selected devices cover all resource types specified for
backup and are not locked when starting the backup. Ideally, back up
each resource type to a separate device.

Chapter 1 15
 Integrating Informix Server and Data Protector
Backup

IMPORTANT For a logical log backup, always use a separate device and ensure that
the LTAPEDEV parameter in the ONCONFIG file is not set to /dev/null or
''.

Figure 1-10 Specifying Informix Server Resource Types

Table 1-6 Informix Server Resource Types

B blobspace

CD critical dbspace (a root dbspace or a dbspace containing

the physical log or a logical log file)

L logical log

MR master root dbspace

ND noncritical dbspace

R root dbspace

TIP Select an additional set of devices (covering all resource types specified
for backup) so that they can take over if some devices in the primary
group fail. Select the Load balancing option and set the Min and Max
parameters to the number of primary devices.

Click Next.

16 Chapter 1
 Integrating Informix Server and Data Protector
Backup

8. Set backup options (Figure 1-11 and Figure 1-12). For information,
see Table 1-7 on page 18.

Figure 1-11 Informix Server Specific Backup Options (Windows)

Figure 1-12 Informix Server Specific Backup Options (UNIX)

Click Next.
9. Optionally, schedule the backup. See “Scheduling Backup
Specifications” on page 19.
Click Next.
10. Save the backup specification, specifying a name and a backup
specification group.

TIP Preview your backup specification before using it for real. See
“Previewing Backup Sessions” on page 20.

Chapter 1 17
 Integrating Informix Server and Data Protector
Backup

Table 1-7 Informix Server Backup Options

Option Description

Whole Select this option to perform a whole-system backup. This

option is only available if you selected all dbobjects to be
backed up at step 6.
In a whole-system backup, all Informix instance’s dbobjects
from the onbar command are backed up. ON-Bar cannot back
them up concurrently; they are backed up sequentially.
Whole-system backup is useful for small systems, when you do
not need to restore logs, for disaster recovery, or when restoring
to another client.

Pre-exec, Specify a command that will be started by ob2onbar.pl on the

Post-exec Informix Server system before the backup (pre-exec) or after
it (post-exec). Do not use double quotes.
Windows: Provide only the name of the command, which must
reside in the <Data_Protector_home>\bin directory. See
Figure 1-11.
UNIX: Provide the pathname of the command. See Figure
1-12.
If you selected a logical log for backup, it is sensible to add
onmode -l as a pre-exec command to ensure that you always
have a log file to back up. Without a log file to back up, the
backup fails.

Modifying Backup Specifications

To modify your backup specification, click its name in the Scoping Pane
of the Backup context, then click the appropriate tab, and apply the
changes. See Figure 1-13.

18 Chapter 1
 Integrating Informix Server and Data Protector
Backup

Figure 1-13 Modifying a Backup Specification

Scheduling Backup Specifications

You can run unattended backups at specific times or periodically. For
details on scheduling, see the online Help index: “scheduled backups”.

Scheduling Example
To back up logical logs at 8.00 a.m., 1.00 p.m., and 6.00 p.m. during week
days:

1. In the Schedule property page, select the starting date in the

calendar and click Add to open the Schedule Backup dialog box.
2. Under Recurring, select Weekly. Under Time options, select 8 AM.
Under Recurring Options, select Mon, Tue, Wed, Thu, and Fri. See
Figure 1-14.
Click OK.
3. Repeat steps 1 and 2 to schedule backups at 1 p.m. and 6 p.m.
4. Click Apply to save the changes.

Chapter 1 19
 Integrating Informix Server and Data Protector
Backup

Figure 1-14 Scheduling a Backup Specification

Previewing Backup Sessions

Preview the backup session to test it. You can use the Data Protector
GUI or CLI.

Using the Data Protector GUI

1. In the Context List, click Backup.

2. In the Scoping Pane, expand Backup Specifications and then
Informix Server. Right-click the backup specification you want to
preview and click Preview Backup.
3. Specify the Backup type and Network load. Click OK.
The message Session completed successfully is displayed at the end
of a successful preview.

20 Chapter 1
 Integrating Informix Server and Data Protector
Backup

Using the Data Protector CLI

From the directory:
Windows: <Data_Protector_home>\bin
HP-UX and Solaris: /opt/omni/bin/
Other UNIX: /usr/omni/bin/
run:
omnib -informix_list <backup_specification_name> -test_bar

Figure 1-15 Previewing a Backup with Backup Specification ds_street

(Windows)

Chapter 1 21
 Integrating Informix Server and Data Protector
Backup

Figure 1-16 Previewing a Backup with Backup Specification IDS914 (UNIX)

What Happens During the Preview?

1. The Informix Server onbar command is started with the -F option,

which specifies a fake backup. This tests if the Informix instance is
correctly configured for backup.
2. Data Protector tests the Data Protector part of the configuration. The
following is tested:

• Communication between the Informix instance and Data

Protector
• The syntax of the backup specification
• If devices are correctly specified
• If the necessary media are in the devices

Starting Backup Sessions

Interactive backups are run on demand. They are useful for urgent
backups or restarting failed backups.

22 Chapter 1
 Integrating Informix Server and Data Protector
Backup

Backup Methods
Start a backup of dbobjects in any of the following ways:

• Use the Data Protector GUI. See “Using the Data Protector GUI” on
page 23.
• Use the Data Protector CLI. See “Using the Data Protector CLI” on
page 23.
• Use the Informix Server onbar command. See “Using Informix Server
Commands” on page 24.
• UNIX only: Use the Informix Server log_full.sh script. See “Using
Informix Server log_full.sh on UNIX” on page 26.

Before You Begin

✓ Ensure that you have sufficient logical log space to create a backup.
If the amount of free space in all logical log files is less than half a
single log file, Informix Server does not create a backup.
✓ Before a Full backup, print or keep a copy of your ONCONFIG file, the
emergency boot file, and on UNIX, also the sqlhosts file.
✓ Verify data consistency.

Using the Data Protector GUI

1. In the Context List, click Backup.

2. In the Scoping Pane, expand Backup Specifications, and then
Informix Server. Right-click the backup specification you want to
start and click Start Backup.
3. Select the Backup type and Network load. Click OK.
The message Session completed successfully is displayed at the end
of a successful backup session.

Using the Data Protector CLI

From the directory:
Windows: <Data_Protector_home>\bin
HP-UX and Solaris: /opt/omni/bin/
Other UNIX: /usr/omni/bin/

Chapter 1 23
 Integrating Informix Server and Data Protector
Backup

run:
omnib -informix_list <backup_specification_name> [-barmode
<InformixMode>][<List_options>]
where <InformixMode> is one of the following:
full|inf_incr1|inf_incr2

NOTE Data Protector terms full, inf_incr1, and inf_incr2 backup are
equivalent to Informix Server terms level-0, level-1, and level-2 backup,
respectively.

For <List_options>, see the omnib man page.

Examples To start a full backup using the Informix Server backup specification
InformixWhole, run:
omnib -informix_list InformixWhole -barmode full
To start an incremental backup (level 1) of the Informix Server backup
specification InformixIncr, run:
omnib -informix_list InformixIncr -barmode inf_incr1

Using Informix Server Commands

Use the Informix Server onbar command to start a backup of dbobjects
from the Informix Server system where the relevant Informix instance is
located.
Before the backup:

✓ Log in to the Informix Server system as user informix.

✓ Set the following variables:
Table 1-8 Data Protector and Informix Server Variables

ONCONFIG Name of the Informix instance ONCONFIG file.

INFORMIXSQLHOSTS Windows: system on which the sqlhosts entry in the

Windows Registry exists.
UNIX: pathname of the sqlhosts file, for example
/applications/informix/etc/sqlhosts.

24 Chapter 1
 Integrating Informix Server and Data Protector
Backup

Table 1-8 Data Protector and Informix Server Variables

INFORMIXDIR Pathname of the Informix Server home directory

INFORMIXSERVER Name of the Informix instance

OB2APPNAME Name of the Informix instance

OB2BARLIST For backup, name of the backup specification to be used

for the backup.
For restore, name of the backup specification to be used
for salvaging logical logs.

✓ Ensure that the Informix instance is in online or quiescent mode.

Once you start a backup, do not change the mode until the backup
finishes; changing the mode terminates the backup. Only online
dbspaces and blobspaces are backed up. To list online dbobjects, run:
Windows: <INFORMIXDIR>\bin\onstat -d
UNIX: <INFORMIXDIR>/bin/onstat -d
Table 1-9 Backup Modes

Online Use online mode if your Informix instance must be accessible

during the backup. An online backup may impact performance.

Quiescent Use quiescent mode to eliminate partial transactions in a

backup. Quiescent backup may not be practical if you need
continuous access to Informix instances.

✓ Keep a copy of your ONCONFIG file, the emergency boot file, and on
UNIX, also the sqlhosts file, after you create a full backup. You need
this information to restore dbobjects.
To back up a list of dbspaces, run:
onbar -b <dbspace_list>
For example, to back up dbspaces dbspace1 and dbspace3, run:
onbar -b dbspace1, dbspace3
To back up the current logical log file and switch to the next logical log
file, run:
Informix Server 7.3: onbar -l -c
Informix Server 9.4: onbar -b -l -c

Chapter 1 25
 Integrating Informix Server and Data Protector
Backup

For more information, see the Backup and Restore Guide of Informix
Server.

Using Informix Server log_full.sh on UNIX

On UNIX, log_full.sh is used to start a backup of logical log files when
the Informix Server issues a log-full event alarm on the Informix Server.
See “Manual and Continuous Logical Log Backups” on page 26 for
information on logical log file backups.
To enable Informix Server backups from the log_full.sh script:

1. Add the following line to the Informix instance ONCONFIG file:

ALARMPROGRAM <INFORMIXDIR>/etc/log_full.sh.
2. If the Data Protector User Interface is not installed on the Informix
Server system, create an Informix Server backup specification to back
up only logical logs, and edit <INFORMIXDIR>/etc/log_full.sh.
Add the following at the beginning of the file:
export OB2BARLIST=<backup_specification_name>
export OB2APPNAME=<INFORMIXSERVER>
3. If the Data Protector User Interface is installed on the Informix
Server system, create an Informix Server backup specification to back
up logical logs only.

Manual and Continuous Logical Log Backups

To back up logical log files that are full and ready to be backed up, start

• a manual logical log backup to back up all full logical log files and
stop at the current logical log file.
• a continuous logical log backup to back up each logical log file
automatically as it becomes full. Use this backup if you do not want to
monitor the logical log files.
By default, the ALARMPROGRAM configuration parameter is set so that
ON-Bar performs continuous backups.

IMPORTANT If you use continuous backups, ensure that a device is always available
for the logical log backup process.

26 Chapter 1
 Integrating Informix Server and Data Protector
Backup

To perform a manual logical log backup, set the OB2APPNAME and

OB2BARLIST environment variables as described in Table 1-8 on page 24
and run:
onbar -l
To back up the current logical log file and switch to the next logical log
file, run:
Informix Server 7.3: onbar -l -c
Informix Server 9.4: onbar -b -l -c
For more information, see the Backup and Restore Guide of Informix
Server.

Chapter 1 27
 Integrating Informix Server and Data Protector
Restore

Restore
The Data Protector Informix Server integration provides two types of
restore:
Table 1-10 Informix Server Restore Types

Complete Restore from any backup. ON-Bar restores dbobjects

database restore concurrently and replays the logical logs once.

Whole-system Restore from a whole-system backup. ON-Bar restores

restore the whole system sequentially with or without restoring
the logical logs. Whole-system restore is appropriate for
small systems, when you do not need to restore logs, for
disaster recovery, or when restoring to another client.

Restore Methods
Restore dbobjects in any of the following ways:

• Use the Data Protector GUI. See “Restoring Using the Data Protector
GUI” on page 31.
• Use the Data Protector CLI. See “Restoring Using the Data Protector
CLI” on page 35.
• Use the Informix Server onbar command. See “Restoring Using
Informix Server Commands” on page 35.

Before You Begin

✓ Before restoring the root dbspace or performing a whole-system
restore, shut down the Informix instance (cold restore). Log in to the
Informix Server system as user informix and run:
Windows: <INFORMIXDIR>\bin\onmode -ky
UNIX: <INFORMIXDIR>/bin/onmode -ky

NOTE Once the Informix instance is offline, you cannot restore only non-critical
(user) dbspaces. The root dbspace must also be selected for restore.

28 Chapter 1
 Integrating Informix Server and Data Protector
Restore

✓ To restore only non-critical dbspaces, ensure that the Informix

instance is online or in a quiescent mode (warm restore), and that
the non-critical dbspaces to be restored are offline.
To check whether dbspaces are offline, run:
Windows: <INFORMIXDIR>\bin\onstat -d
UNIX: <INFORMIXDIR>/bin/onstat -d

Finding Information for Restore

To restore dbobjects, first find the needed media and the session ID of the
last full backup session. Use the Data Protector GUI or CLI.

Using the Data Protector GUI

In the Internal Database context, expand Objects or Sessions. To view
details on a session, right-click the session and click Properties.

Figure 1-17 Example of Session Properties

Using the Data Protector CLI

Localized database names: If the names of backed up objects contain
characters from different Unicode language groups (for example, if you
are using Japanese and latin characters), you must redirect the output of
Data Protector utilities to use UTF-8 encoding:

✓ Set the environment variable OB2_CLI_UTF8 to 1.

Chapter 1 29
 Integrating Informix Server and Data Protector
Restore

✓ Set the encoding used on the terminal to UTF-8.

If you are using localized databases, and the system locale uses the same
Unicode language group, no changes are required.

1. Go to the directory:
Windows: <Data_Protector_home>\bin
HP-UX and Solaris: /opt/omni/bin/
Other UNIX: /usr/omni/bin/
2. Get a list of Informix Server backed up objects:
omnidb -informix

Figure 1-18 Example of a List of Informix Server Backed Up Objects

3. Get a list of backup sessions for a specific object, including the

session ID:
omnidb -informix object_name

Figure 1-19 Example of a List of Backup Sessions for a Specific Object

30 Chapter 1
 Integrating Informix Server and Data Protector
Restore

IMPORTANT For object copies, use the object’s backup ID (which equals the object’s
backup session ID). Do not use the object’s copy session ID.

To get information on the object’s Backup ID, run:

omnidb -session <session_id> -detail
4. Get a list of media needed for restore:
omnidb -session <session_id> -media

Figure 1-20 Example of Finding Media Needed for Restore

For details on the omnidb command, see the omnidb man page.

Restoring Using the Data Protector GUI

1. In the Context List, click Restore.
2. In the Scoping Pane, expand Informix Server, expand the client
from which the data to be restored was backed up, and then click the
Informix instance you want to restore.
3. In the Source page, select objects for restore. To restore the complete
database or for a whole-system restore, select Restore complete
database.

Chapter 1 31
 Integrating Informix Server and Data Protector
Restore

Figure 1-21 Selecting Objects for Restore

4. In the Options page, set the Informix Server specific restore options.
For information, see Table 1-11 on page 34 or press F1.

32 Chapter 1
 Integrating Informix Server and Data Protector
Restore

Figure 1-22 Informix Server Restore Options

5. In the Devices page, select devices to use for the restore.

6. If you perform a whole-system restore and the Informix instance is in
online mode, take the Informix instance offline by running:
onmode -ky
7. Click Restore.
8. In the Start Restore Session dialog box, click Next.
9. Specify the Report level and Network load.
Click Finish to start the restore.
The message Session completed successfully is displayed at the
end of a successful session.

Chapter 1 33
 Integrating Informix Server and Data Protector
Restore

10. If you performed a whole-system restore, bring the Informix instance

online by running:
onmode -m
Table 1-11 Informix Server Restore Options

Option Description

Backup The backup specification to be used for salvaging logical log

Specification files still on the disk before restoring. Preferably, specify the
backup specification used for the backup of logical logs.

Username UNIX only: User name of the Informix Server backup owner.
onbar is started under the account of the specified user.

User group UNIX only: User group of the Informix Server backup
owner.

Restore to The client to restore to. By default, you restore to the original
client backup client. This option is only valid for a whole-system
restore.

Restore by Use this to restore data up to a specific log number. If further

log number logs exist, ON-Bar does not restore them. This option invokes
onbar -r -n <last_log_number>. For details, see the
Backup and Restore Guide of Informix Server.

Restore by Use this to restore data to a specific point in time. This

date option invokes onbar -r -t <time>. For details, see the
Backup and Restore Guide of Informix Server.

Restore the Select this option to restore the latest backup version.
latest
version

Whole Select this option to perform a whole-system restore. This

database option is only available if you selected Restore complete
restore database in the Source page.
Only use this option when restoring from a whole-system
backup. Data Protector does not automatically detect if a
whole-system backup exists.
Data Protector searches for the last whole-system backup
and restores from that. This option invokes onbar -r -w.
For details, see the Backup and Restore Guide of Informix
Server.

34 Chapter 1
 Integrating Informix Server and Data Protector
Restore

Restoring Using the Data Protector CLI

From the directory:
Windows: <Data_Protector_home>\bin
HP-UX and Solaris: /opt/omni/bin/
Other UNIX: /usr/omni/bin/
run:
omnir -informix -barhost <ClientName> -barcmnd ob2onbar.pl
-user <User>:<Group> -appname <INFORMIXSERVER> -bararg
<OnBarRestoreArguments> [<INFORMIX_OPTIONS>]
<ClientName> Name of the Informix Server system. In a cluster
environment, name of the virtual server.
<INFORMIXSERVER> Name of the Informix instance.
<User>, <Group> UNIX only: the user name and its group name.
<OnBarRestoreArguments> ON-Bar restore arguments. Put each
argument in double quotes.
<INFORMIX_OPTIONS> A subset of general restore options. For
information, see the omnir man page.

Example To restore the Informix instance informix_instance1 on the UNIX

system computer with the bar argument -r rootdbs, run:
omnir -informix -barhost computer -barcmnd ob2onbar.pl -user
informix:informix -appname informix_instance1 -bararg "-r
rootdbs"

Restoring Using Informix Server Commands

Before restoring:

✓ Log in to the Informix Server system as user informix.

✓ Set Data Protector and Informix Server variables as described in
Table 1-8 on page 24.
✓ If a disk failure occurs, salvage logical log files that are still on the
disk by running:
onbar -l -s

Chapter 1 35
Integrating Informix Server and Data Protector
Restore

The following are examples of the onbar command syntax for restore. For
further options, see the Backup and Restore Guide of Informix Server.

Restoring Dbspaces, Blobspaces, and Logical Logs

1. If the Informix instance to be restored is in online mode, take it

offline:
onmode -ky
2. Restore dbspaces, blobspaces, and appropriate logical logs:
Complete database restore: onbar -r
Whole-system restore: onbar -r -w
3. After the restore, bring the Informix instance online:
onmode -m

Restoring Dbspaces and Blobspaces Only

To restore dbspaces and blobspaces without the logical log, run:
onbar -r -p

Restoring a Particular Dbspace or Blobspace

To restore a specific dbspace, for example dbspace_1, run:
onbar -r dbspace_1

Restoring to Another Informix Server

To restore data to an Informix Server system other than that from which
the backup was made:

1. Install the Data Protector Informix Integration software

component on the client to which you want to restore (target client).
2. Create user informix on the target client.
3. Create an Informix instance with the same name and number as the
original Informix instance by using the Informix Server ON-monitor
utility on the target client.
4. Ensure that the Informix instance is online.

36 Chapter 1
 Integrating Informix Server and Data Protector
Restore

5. Configure the Informix instance as described in “Configuring

Informix Instances” on page 6.
6. Take the Informix instance offline.
7. Copy the original Informix Server configuration files (ONCONFIG, the
emergency boot file, oncfg_<SERVERNAME>.<SERVERNUM>, and on
UNIX, also the sqlhosts file) to the target client. Change the client
name in the files to the target client name.
8. Start a whole-system restore of dbobjects as described in “Restoring
Using the Data Protector GUI” on page 31.

Restoring Using Another Device

You can restore using a device other than that used for backup.

Using the Data Protector GUI

On how to specify another device for restore using the Data Protector
GUI, see the online Help index: “restore, selecting devices for”.

Using the Data Protector CLI or Informix Server Commands

If you are restoring using the Data Protector CLI or Informix Server
commands, specify the new device in the file:
Windows:
<Data_Protector_home>\Config\Server\cell\restoredev
UNIX: /etc/opt/omni/server/cell/restoredev
Use the format:
"DEV 1" "DEV 2"
where DEV 1 is the original device and DEV 2 the new device.

IMPORTANT Delete this file after use.

On Windows, use the Unicode format for the file.

Chapter 1 37
Integrating Informix Server and Data Protector
Monitoring Sessions

Monitoring Sessions
You can monitor currently running sessions in the Data Protector GUI.
When you run an interactive backup or a restore session, a monitor
window shows you the progress of the session. Closing the GUI does not
affect the session.
You can also monitor sessions from any Data Protector client with the
User Interface component installed, using the Monitor context.
On how to monitor a session, see the online Help index: “viewing
currently running sessions”.
When ON-Bar encounters an error or a condition that warrants a
warning, it writes a message to the Informix Server ON-Bar message
file. The full pathname of this file is specified in the BAR_ACT_LOG
configuration parameter. For more information on this file, see the
Backup and Restore Guide of Informix Server.
To abort a backup or restore session successfully, set the ON-Bar
BAR_RETRY configuration parameter to 0. This parameter specifies how
many times ON-Bar retries a backup or restore if the first attempt fails.

38 Chapter 1
 Integrating Informix Server and Data Protector
Troubleshooting

Troubleshooting
This section lists general checks and verifications, plus problems you
might encounter when using the Data Protector Informix Server
integration. Start at “Problems” on page 44 and if you cannot find a
solution there, perform general checks and verifications.
For general Data Protector troubleshooting information, see the HP
OpenView Storage Data Protector Troubleshooting Guide.

Before You Begin

✓ Ensure that the latest official Data Protector patches are installed.
See the online Help index: “patches” on how to verify this.
✓ See the HP OpenView Storage Data Protector Product
Announcements, Software Notes, and References for general Data
Protector limitations, as well as recognized issues and workarounds.
✓ See http://www.hp.com/support/manuals for an up-to-date list of
supported versions, platforms, and other information.

Checks and Verifications

If your configuration, backup, or restore failed:

✓ On the Informix Server system, examine system errors reported in

the debug.log and informix.log files, located in the directory:
Windows: <Data_Protector_home>\log
HP-UX and Solaris: /var/opt/omni/log/
Other UNIX: /usr/omni/log/
✓ Make a test backup and restore of any filesystem on the problematic
client. For information, see online Help.
✓ Windows only: Ensure that the Data Protector Inet service is
running under the account informix.
✓ UNIX only: Verify that the onbar_d command has the switch
ownership (s) bit set and that it is owned by the Informix Server user,
for example, informix:informix or root:informix.

Chapter 1 39
 Integrating Informix Server and Data Protector
Troubleshooting

Verify that this user is also the owner of the backup specification, or
in the case of a restore failure, verify that this user is specified for the
restore session, and that it is in the Data Protector operator or
admin group.
If this user is in the Data Protector operator group, ensure that the
See private objects user right of this group is selected. For
information, see the online help index: “user rights, changing”.
Now test if this user, for example user informix, has appropriate
rights in Data Protector. Log in to the Informix Server system as user
informix. From the directory:
HP-UX and Solaris: /opt/omni/bin/utilns/
Other UNIX: /usr/omni/bin/utilns/
run:
testbar -type:informix -perform:checkuser
-bar:<backup_specification_name>

Figure 1-23 Example of Checking the Informix Server User

In this example, the user has all the necessary rights for the backup
specification named InformixWhole.

40 Chapter 1
 Integrating Informix Server and Data Protector
Troubleshooting

If the user informix on the Informix Server system

computer.hp.com does not have the necessary rights, an error
similar to the following will be displayed:
[Critical] From: [email protected] "" Time: 08/06/2005
17:51:41
[131:53] User "[email protected]" is not allowed to
perform a restore.
✓ In a cluster environment, ensure that the environment variable
OB2BARHOSTNAME is set to the virtual server name before performing
procedures from the Data Protector CLI. When the Data Protector
GUI is used, this is not required.
Additionally, if your configuration or backup failed:

✓ Ensure that the Informix instance is online.

Additionally, if your backup failed:

✓ Check the configuration of the Informix instance as described in

“Checking the Configuration” on page 10.
✓ Test the backup specification as described in “Previewing Backup
Sessions” on page 20.

— If this fails, check if the Informix Server part of the test failed:
Run the onbar -b -F command. If the test fails, see the Informix
Server documentation for further instructions.
— If the Data Protector part of the test failed, create an Informix
Server backup specification to back up to a null or file device.
If the backup succeeds, the problem is probably related to devices.
For information on troubleshooting devices, see online Help.
— If the test succeeds, start the backup directly from the Informix
Server system using Informix Server commands. For information,
see “Using Informix Server Commands” on page 24.
If this backup succeeds, the problem may be that the client on
which the Data Protector User Interface is running does not have
enough memory, disk space, or other operating system resources.

Chapter 1 41
Integrating Informix Server and Data Protector
Troubleshooting

Additionally, if your backup or restore failed:

✓ Test the Data Protector data transfer using the testbar utility. Log
in to the Informix Server system as user informix. From the
directory:
Windows: <Data_Protector_home>\bin
HP-UX and Solaris: /opt/omni/bin/utilns/
Other UNIX: /usr/omni/bin/utilns/

— if your backup failed, run:

testbar -type:Informix -appname:<INFORMIXSERVER>
-bar:<backup_specification_name> -perform:backup
where <INFORMIXSERVER> is the name of the Informix instance.
— if your restore failed, run:
testbar -type:Informix -appname:<INFORMIXSERVER>
-bar:<backup_specification_name> -perform:restore
-object:<OBJECT_NAME> -version:<OBJECT_VERSION>
where <INFORMIXSERVER> is the name of the Informix instance,
<OBJECT_NAME> is the name of the object to be restored,
<OBJECT_VERSION> is the object version.
If the test fails:

1. Troubleshoot errors reported by the testbar utility using the

Data Protector troubleshooting file, located on the Cell Manager
in:
Windows: <Data_Protector_home>\help\enu\Trouble.txt
UNIX: /opt/omni/gui/help/C/Trouble.txt
2. On the Informix Server system, examine system errors reported in
the file:
Windows: <Data_Protector_home>\log\debug.log
HP-UX and Solaris: /var/opt/omni/log/debug.log
Other UNIX: /usr/omni/log/debug.log
Additionally, if your restore failed:

✓ Ensure that the backup specification used for salvaging logical logs is
properly configured.

42 Chapter 1
 Integrating Informix Server and Data Protector
Troubleshooting

Checking the Informix Server Side

The following checks may help you solve some Informix Server related
problems.
If your backup or restore failed:

✓ Check the following Informix Server files for error descriptions:

bar_act.log
bar_dbg.log
online.log
Locations of these files are specified in the Informix Server ONCONFIG
file.
Additionally, if your backup failed:

✓ Start a backup, not using Data Protector:

1. Set the BAR_BSALIB_PATH shell variable to:

Windows: <ISMDIR>\bin\libbsa.dll
where <ISMDIR> is the path to the ISM.
UNIX: <INFORMIXDIR>/lib/ibsad001.sl
where <INFORMIXDIR> is the home directory of Informix Server.
2. Use the onbar command to start the backup.
Additionally, if your restore failed:

✓ For a cold restore, verify if the dbspaces you want to restore are
offline:

1. Log in to the Informix Server system as user informix.

2. Run:
Windows: <INFORMIXDIR>\bin\onstat -d
UNIX: <INFORMIXDIR>/bin/onstat -d
where <INFORMIXDIR> is the home directory of Informix Server.
✓ Ensure that the Informix Server configuration files (ONCONFIG, the
emergency boot file, oncfg_<INFORMIXSERVER>.<SERVERNUM>, and on
UNIX, also the sqlhosts file) are not corrupt. If they are corrupt,
restore them manually.

Chapter 1 43
 Integrating Informix Server and Data Protector
Troubleshooting

Problems

Problem Restore to another client fails

If you backed up data to one client, exported the media, and then
imported them to another client in a different cell, the Data Protector
session IDs of backup sessions may be changed in the IDB. However, the
session IDs are not automatically changed in the Informix Server
emergency boot file (ixbar.<server_id>, where <server_id> is the
value of the SERVERNUM configuration parameter). Therefore, the restore
of such objects may fail.

Action Edit the emergency boot file to reflect the changed Data Protector
session IDs. List the changed session IDs during the import procedure.
Information about backed-up objects is stored in the emergency boot file
in the following format:
ODS730 rootdbs R 1 7 0 9 1999008018 2005-08-18 18:10:25 1
Entries 7 and 9 make up make up the Data Protector session ID. Entry 9
is the date and entry 7 the unique session number.
Here, the session ID is 2005/08/18-9. Note that the delimiter in the
date field is "-" in the emergency boot file and "/" in the Data Protector
session ID.
The value of the SERVERNUM configuration parameter is given in entry 4.

Problem Restore fails because the emergency boot file is too large

Action Use the ON-Bar onsmsync utility to remove expired backups from the
Informix Server sysutils database and emergency boot file. For
information on the onsmsync utility, see the Backup and Restore Guide of
Informix Server.

44 Chapter 1
2 Integrating IBM DB2 UDB and
Data Protector

Chapter 2 45
 Integrating IBM DB2 UDB and Data Protector
Introduction

Introduction
This chapter explains how to configure and use the Data Protector IBM
DB2 UDB (DB2) integration. It describes concepts and methods you
need to understand to back up and restore DB2 databases.
Data Protector integrates with IBM DB2 Universal Database Server
(DB2 Server) to back up DB2 database objects online and offline.
Data Protector offers interactive and scheduled backups of the following
types:
Table 2-1 Backup Types

Full Backs up complete DB2 objects.

Incremental Backs up changes since the last Full backup.

Delta Backs up changes since the last backup of any type.

The basic backup unit is a table space. Only table spaces or databases
(DB2 objects) can be selected for backup.
When restoring a database or table space, you can specify restore options
to perform:

• Rollforward recovery
• Version recovery
• Restore to a new database (database only)
• Restore to another instance (database only)
• Restore to another system (database only)
• Automatic restore from incremental or delta backups
Databases are restored offline, table spaces online.

Limitations Table or datafile backup and restore are not supported. Neither are
backup or restore using Data Protector media with the DB2 Command
Line Processor or the DB2 Control Center.
This chapter provides information specific to the Data Protector DB2
Server integration. For general Data Protector procedures and options,
see online Help.

46 Chapter 2
 Integrating IBM DB2 UDB and Data Protector
Integration Concept

Integration Concept
Data Protector integrates with the DB2 Server through a set of modules
responsible for data backup and restore. Figure 2-1 shows the
architecture of the Data Protector DB2 integration.

Figure 2-1 DB2 Integration Architecture

Table 2-2 Legend

SM Data Protector Session Manager: Backup Session Manager

during backup and Restore Session Manager during restore.

db2bar Data Protector module, used for controlling activities

between the DB2 Server and Data Protector backup and
restore.

db2arch Program that backs up and restores DB2 log files.

Chapter 2 47
 Integrating IBM DB2 UDB and Data Protector
Integration Concept

Table 2-2 Legend

libob2db2 Data transferring module, called by DB2 Server.

MA Data Protector General Media Agent.

Backup A list of objects to be backed up, backup devices, and options

Specification to be used.

IDB The Data Protector Internal Database.

While the DB2 Server is responsible for read/write operations to disk,

Data Protector reads from and writes to devices and manages media.

48 Chapter 2
 Integrating IBM DB2 UDB and Data Protector
Configuring the Integration

Configuring the Integration

You need to configure DB2 users and every DB2 instance you intend to
back up or restore to.

Prerequisites
• Ensure you have correctly installed and configured DB2 Server.

— For supported versions, platforms, devices, and other information,

see the HP OpenView Storage Data Protector Product
Announcements, Software Notes, and References or
http://www.hp.com/support/manuals.
— For information on DB2 Server, see the DB2 Administration Guide
and DB2 Server Books Online.
• Ensure you have correctly installed Data Protector. On how to install
the Data Protector IBM DB2 UDB integration in various
architectures, see the HP OpenView Storage Data Protector
Installation and Licensing Guide.
Every DB2 Server system you intend to back up from or restore to
must have the Data Protector DB2 Integration and Disk Agent
components installed.
In a partitioned environment, ensure that the DB2 Integration and
Disk Agent components are installed on all the physical nodes on
which the DB2 database resides.

Before You Begin

✓ Configure devices and media for use with Data Protector.
✓ To test whether the DB2 Server system and the Cell Manager
communicate properly, configure and run a Data Protector filesystem
backup and restore on the DB2 Server system.

Partitioned Environment
In a physically partitioned environment, configure the integration on
every physical node separately.

Chapter 2 49
Integrating IBM DB2 UDB and Data Protector
Configuring the Integration

Ensure that the configuration parameter MaxBSession in the Data

Protector global options file is set to at least twice the number of nodes of
the partitioned database.

Configuring DB2 Users

Ensure the DB2 user has appropriate authorities to perform DB2
backups and restores (either SYSADM, SYSCTRL, or SYSMAINT).
Add user root (UNIX only) and the DB2 user to both the Data Protector
and DB2 admin user groups. For more information, see the online Help
index: “user groups” and “adding users”.
Provide this user in configuration and restore procedures. This user is
needed by Data Protector to start the Data Protector Inet service
(Windows) or process (UNIX).

Configuring DB2 Instances

Provide Data Protector with the DB2 instance’s configuration
parameters:

• DB2 user
• DB2 user’s password
• DB2 instance’s home directory (only in a partitioned environment)
Data Protector then creates a DB2 instance configuration file on the Cell
Manager and verifies the connection to the instance.
These parameters are used for connecting to the DB2 Server system to
perform backups, restores, and other operations, such as listing objects
for backup.
To configure a DB2 instance, use the Data Protector GUI or CLI.

Before You Begin

✓ Ensure the DB2 instance is online.

Using the Data Protector GUI

1. In the Context List, click Backup.

2. In the Scoping Pane, expand Backup Specifications, right-click
DB2 Integration, and click Add Backup.

50 Chapter 2
 Integrating IBM DB2 UDB and Data Protector
Configuring the Integration

3. In the Create New Backup dialog box, click OK.

4. In Client, select the DB2 Server system. In a cluster environment,
select the virtual server.
In Application database, type the DB2 instance’s name.
UNIX only: Type a username and its group name.

Figure 2-2 Specifying a DB2 Instance

Click Next. The Configure DB2 dialog box is displayed.

5. Type the name of the DB2 user and its password. This user must be
configured as described in “Configuring DB2 Users” on page 50.
In a partitioned environment, select DB2 EEE and specify the
pathname of the DB2 instance’s home directory.
Click OK.
6. The DB2 instance is configured. Exit the GUI or proceed with
creating a backup specification at step 6 on page 56.

Chapter 2 51
Integrating IBM DB2 UDB and Data Protector
Configuring the Integration

Using the Data Protector CLI

From the directory:
Windows: <Data_Protector_home>\bin
HP-UX: /opt/omni/lbin
Other UNIX: /usr/omni/bin/
run:
util_db2 -CONFIG <DB2_instance> <username> <password> [<DB2
_instance’s_home>]

Parameter Description
<DB2_instance> Name of the DB2 instance.
<username> DB2 user.
<password> DB2 user’s password.
<DB2_instance’s_home> Home directory (pathname) of the DB2
instance (only in a partitioned environment).

Checking the Configuration

You can check the configuration of a DB2 instance after you have created
at least one backup specification for the DB2 instance. Use the Data
Protector GUI or CLI.

Using the Data Protector GUI

1. In the Context List, select Backup.

2. In the Scoping Pane, expand Backup Specifications and then DB2
Integration. Click a backup specification for the DB2 instance.
3. In the Results Area, right-click the DB2 instance and click Check
configuration.

Using the Data Protector CLI

From the directory:
Windows: <Data_Protector_home>\bin
HP-UX: /opt/omni/lbin

52 Chapter 2
 Integrating IBM DB2 UDB and Data Protector
Configuring the Integration

Other UNIX: /usr/omni/bin/

run:
util_db2.exe -CHKCONF <DB2_instance>

Chapter 2 53
 Integrating IBM DB2 UDB and Data Protector
Backup

Backup
The Data Protector DB2 integration provides three backup types and two
backup modes.
Table 2-3 Backup Types

Full Backs up complete DB2 objects.

Incremental Backs up changes since the last Full backup.

Delta Backs up changes since the last backup of any type.

Table 2-4 Backup Modes

online Database is online.

offline Database is unavailable for use.

To configure a DB2 backup:

1. Create a backup specification for DB2 objects, using the DB2

Database Backup template.
2. To back up archived logs, create a backup specification for the
archived logs, using the Archived_Logs_Backup template. Specify a
different device than the one for backing up DB2 objects.Otherwise,
archived logs cannot be backed up because the device is locked by the
online backup session of DB2 objects.

IMPORTANT Archived logs are automatically backed up whenever a new offline redo
log appears, for example, after the online backup of DB2 objects
completes. Therefore, do not start an online backup of DB2 objects before
creating an archived logs backup specification.
Delete any old archived logs backup specification before creating a new
one.

54 Chapter 2
 Integrating IBM DB2 UDB and Data Protector
Backup

Physically Partitioned Environment

In a physically partitioned environment, create one backup specification
for DB2 database objects and one for archived logs for each physical node
(system) on which the DB2 objects reside.
Ensure that the same DB2 database objects are selected for backup on
all the physical nodes.
Since two devices are required to back up DB2 objects and archived logs
from a single system, the total number of devices (drives) required is
twice the number of physical nodes.
On how to run these backup specifications, see “Starting Backups of
Physically Partitioned DB2 Objects” on page 62.

Creating Backup Specifications

Create a backup specification using the Data Protector Manager.

1. In the Context List, click Backup.

2. In the Scoping Pane, expand Backup Specifications, right-click
DB2 Integration, and click Add Backup.
3. Select a template.
Table 2-5 Backup Templates

DB2 Database Backup Used for backing up only DB2 database objects.

Archived_Logs_Backup Used for backing up only archived logs. This

type of backup specification can be saved, but
not started or scheduled. It is used every time
the User Exit program starts the backup of
archived logs.

Click OK.
4. In Client, select the DB2 Server system. In a cluster environment,
select the virtual server.
In Application database, select the DB2 instance to be backed up.
UNIX only: Type a username and its group name. This user will be
the backup owner.
Click Next.

Chapter 2 55
 Integrating IBM DB2 UDB and Data Protector
Backup

5. If the DB2 Instance is not configured for use with Data Protector, the
Configure DB2 dialog box is displayed. Configure it as described in
“Configuring DB2 Instances” on page 50.
6. Select the DB2 objects you want to back up. The basic backup unit is
a table space. Only table spaces and databases can be selected for
backup. See Figure 2-3.

Figure 2-3 Selecting DB2 Objects

If you select only DB2 temporary table spaces, the backup fails. To
back up DB2 temporary table spaces, select the whole database.

IMPORTANT In a physically partitioned environment, select only one database or

table spaces of the same database.

Click Next.

7. Select devices to use for the backup.

To specify device options, right-click the device and click Properties.
Click Next.
8. Set backup options.
For information on application specific options, see Table 2-6 on
page 58.
Click Next.

56 Chapter 2
 Integrating IBM DB2 UDB and Data Protector
Backup

9. Optionally, schedule the backup. For more information, see

“Scheduling Backup Specifications” on page 58.
Click Next.
10. To perform an offline backup of a particular DB2 object, right-click
the object and click Properties. In the Object Properties dialog
box, select Offline Backup and click OK. See Figure 2-4.

Figure 2-4 Selecting Offline Backup

11. Save the backup specification, specifying a name and a backup

specification group.

TIP Use consistent names for the backup specifications of a physically

partitioned DB2 object. For example, MyObject1, MyObject2 and so on.

Chapter 2 57
 Integrating IBM DB2 UDB and Data Protector
Backup

TIP Preview your backup specification before using it for real. See
“Previewing Backup Sessions” on page 59.

Table 2-6 DB2 Backup Options

Pre-exec Specify a command to be started by db2bar on the DB2

Post-exec Server system before the backup of every selected DB2
object (pre-exec) or after it (post-exec). Do not use double
quotes.
Type only the name of the command, not the pathname. The
command must reside in:
Windows: <Data_Protector_home>\bin
HP-UX: /opt/omni/lbin
Other UNIX: /usr/omni/bin

Parallelism Specify the number of data streams for backing up a

database from a node.
In a partitioned environment, Parallelism must equal the
device concurrency.
Default:1.

Modifying Backup Specifications

To modify your backup specification, click its name in the Scoping Pane
of the Backup context, then click the appropriate tab, and apply the
changes.

Scheduling Backup Specifications

You can run unattended backups at specific times or periodically. For
details on scheduling, see the online Help index: “scheduled backups”.

Example To back up table spaces at 8.00 a.m., 1.00 p.m., and 6.00 p.m. during
week days:

1. In the Schedule property page, select the starting date in the

calendar and click Add to open the Schedule Backup dialog box.

58 Chapter 2
 Integrating IBM DB2 UDB and Data Protector
Backup

2. Under Recurring, select Weekly. Under Time options, select 8 AM.

Under Recurring Options, select Mon, Tue, Wed, Thu, and Fri. See
Figure 2-5. Click OK.
3. Repeat steps 1 and 2 to schedule another backup at 1 p.m., and
another one at 6 p.m.
4. Click Apply to save the changes.

Figure 2-5 Scheduling a Backup Specification

Previewing Backup Sessions

Preview the backup session to test it. Use the Data Protector GUI or CLI.
The preview creates a file <backup_specification_name>_TEST_FILE
in the <Data_Protector_home>\tmp\ directory on the DB2 Server
system. Delete it after the test.

Using the Data Protector GUI

1. In the Context List, click Backup.

Chapter 2 59
Integrating IBM DB2 UDB and Data Protector
Backup

2. In the Scoping Pane, expand Backup Specifications and then DB2

Integration. Right-click the backup specification you want to
preview and click Preview Backup.
3. Specify the Backup type and Network load. Click OK.
The message Session completed successfully is displayed at the end
of a successful preview.

Using the Data Protector CLI

From the directory:
Windows: <Data_Protector_home>\bin
HP-UX and Solaris: /opt/omni/bin/
Other UNIX: /usr/omni/bin/
run:
omnib -db2_list <backup_specification_name> -test_bar

What Happens During the Preview?

The db2bar command is started, which starts the Data Protector
testbar2 command to test:

• Communication within the Data Protector cell

• The syntax of the backup specification
• If devices are correctly specified
• If necessary media are in the devices
Then, the DB2 instance is checked for the presence of selected DB2
objects and whether they are in an appropriate state for backup.

Starting Backup Sessions

Interactive backups are run on demand. They are useful for urgent
backups or for restarting failed backups.
You can start a backup of DB2 objects using the Data Protector GUI or
CLI.

60 Chapter 2
 Integrating IBM DB2 UDB and Data Protector
Backup

Before You Begin

✓ To enable online backups of DB2 objects, set the DB2 logretain and
userexit parameters to ON (in a partitioned environment, on every
node on which the object resides). Then restart the database for the
new parameters to take effect and perform a full offline database
backup.
✓ To enable incremental or delta backups of DB2 objects, set the DB2
trackmod parameter to ON:

1. Run:
db2 update db cfg for <db_name> USING TRACKMOD ON
In a partitioned environment, run the command on every node on
which the DB2 object resides.
2. Restart the database.
3. Perform a full offline database backup to non-Data Protector
media by running:
backup db <db_name>
✓ To enable offline backups of one or several DB2 table spaces (not the
whole database), set the DB2 logretain parameter to ON.

Using the Data Protector GUI

1. In the Context List, click Backup.

2. In the Scoping Pane, expand Backup Specifications and then DB2
Integration. Right-click the backup specification you want to start
and click Start Backup.
3. Select the Backup type and Network load. Click OK.
Successful backup displays the message Session completed
successfully, providing the backup size, which is the size of full and
incremental/delta backups together.

Using the Data Protector CLI

From the directory:
Windows: <Data_Protector_home>\bin
HP-UX and Solaris: /opt/omni/bin/

Chapter 2 61
 Integrating IBM DB2 UDB and Data Protector
Backup

Other UNIX: /usr/omni/bin/

run:
omnib -db2_list <backup_specification_name> [-barmode
<db2_mode>] [<options>] [-preview]

Parameter Description
<db2_mode> Backup type: {-full | -incr | -delta}
<options> For information, see the omnib man page.

Example To perform a full DB2 backup, using the backup specification MyObjects,
and to set data protection to 10 weeks, run:
omnib -db2_list MyObjects -barmode -full -protect weeks 10

Starting Backups of Physically Partitioned DB2 Objects

1. Run the backup specification for the part of DB2 objects residing on
the system with the catalog node. Use the Data Protector GUI or CLI.
2. Run the backup specifications for the other parts of the DB2 objects in
any order.
The order in which you run the backup specifications is only important if
the object resides on the catalog node.

TIP To the first backup specification, add a post-exec script that will
automatically run the other backup specifications. For more information,
see the online Help index: “pre- and post-exec commands for backup
specifications”.

62 Chapter 2
 Integrating IBM DB2 UDB and Data Protector
Restore

Restore
Restore DB2 objects using the Data Protector GUI or CLI.

IMPORTANT Databases are restored offline.

Table spaces are restored online. Only table spaces that are not being
restored are available for use.
A dropped table space can only be restored from a full database backup.

On how to restore a DB2 database to a new database, see “Restoring to a

New Database or Another DB2 Instance” on page 68.
On how to restore partitioned DB2 objects, see “Restore in a Partitioned
Environment” on page 71.

Restoring Using the Data Protector GUI

1. In the Context List, select Restore.
2. In the Scoping Pane, expand DB2 Integration, expand the client
from which the data to be restored was backed up, and then click the
DB2 instance you want to restore.
3. In the Source page, specify whether you want to restore
database/tablespaces or archived logs and then browse for and select
desired DB2 objects. See Figure 2-6.

Chapter 2 63
 Integrating IBM DB2 UDB and Data Protector
Restore

Figure 2-6 Selecting Objects for Restore

IMPORTANT In a physically partitioned environment, select only one database or

several table spaces of the same database.

By default, the latest backup version is restored. To restore a DB2

object from a specific backup version, right-click the object, click
Properties, and specify Backup version in the Properties for
<DB2_object> dialog box. See Figure 2-7.

Figure 2-7 Selecting a Version

64 Chapter 2
 Integrating IBM DB2 UDB and Data Protector
Restore

To restore a database to a new database, right-click the database,

click Properties, and then click the Options tab. Select Restore to
a new database and specify a name for the new database. See Figure
2-8.

Figure 2-8 Restoring to a New Database

4. In the Options page, set the DB2 restore options. For information,
see Table 2-7 on page 65 or press F1.

NOTE For rollforward, the latest backup version of log files is used. To perform
a rollforward using an older version of log files, first restore the desired
log files and then restore the databases/tablespaces with the
Rollforward option cleared. In a partitioned environment, connect to
the catalog node. Finally, perform a rollforward, using DB2 tools.

5. In the Devices page, select devices you want to use for the restore.
6. Click Restore.
7. In the Start Restore Session dialog box, click Next
8. Specify the Report level and Network load.
9. Click Finish to start the restore.
Table 2-7 DB2 Restore Options

Restore to client The client to restore to. By default, DB2 objects are
restored to the source client. This option is only valid
when restoring the whole database.

Chapter 2 65
 Integrating IBM DB2 UDB and Data Protector
Restore

Table 2-7 DB2 Restore Options

Username DB2 user of the target DB2 instance, its group, and
User group password.
Password

Restore to The DB2 instance to restore to. By default, DB2 objects

instance are restored to the source DB2 instance. The instance
must be configured for use with Data Protector as
described in “Configuring DB2 Instances” on page 50.
For details, see “Restoring to a New Database or
Another DB2 Instance” on page 68.

Rollforward Select this option to perform a rollforward recovery.

The database/tablespace is restored to its state at a
specific time. During a rollforward recovery, both
databases/tablespaces and archived logs are restored,
and then the changes recorded in the archived logs are
applied to the database/tablespace. The latest backup
version of log files is used for this purpose. Specify the
rollforward by selecting Rollforward to the end of
the logs or Rollforward to date. When specifying
Rollforward to date, use local time (as set on the
DB2 target server), not coordinated universal time
(UTC).
Rollforward recovery of the system catalog can only be
performed to the end of the logs. You cannot restore
other table spaces of the same database from the same
session simultaneously.
To perform a rollforward recovery in a physically
partitioned environment, restore all the parts with
Rollforward cleared (see “Restore in a Partitioned
Environment” on page 71), connect to the catalog node,
and then start a rollforward using the DB2 Command
Line Processor.
To perform a version recovery, clear this option. The
database/tablespace is restored to its state at the time
of the backup. For a version recovery, you need a full
offline database backup. When restoring from an
online backup with Rollforward cleared, the database
enters the rollforward pending state and becomes
unavailable for use. To make it available, start a
rollforward using the DB2 Command Line Processor or
Command Center (in a partitioned environment, the
rollforward must be started from the catalog node).

66 Chapter 2
 Integrating IBM DB2 UDB and Data Protector
Restore

Restoring Using the Data Protector CLI

From the directory:
Windows: <Data_Protector_home>\bin
HP-UX and Solaris: /opt/omni/bin/
Other UNIX: /usr/omni/bin/
run:
omnir -db2 -barhost <source_client> [-destination
<target_client>]
-instance <target_instance> -dbname <source_db> [-session
<session_ID>] [-newdbname <new_db>] [-frominstance
<source_instance>]
-tsname <table_space> [-session <session_ID>]
-logfile <log_file> [-session <session_ID>]
[-rollforward [-time <YYYY-MM-DD.hh.mm.ss>]]

Parameter Description
<source_client> The DB2 Server system from which DB2 objects
were backed up. In a cluster environment, the name of
the virtual server.
<target_client> The target DB2 Server system (only if you are not
restoring to the source client).
<source_instance> The DB2 instance whose DB2 objects were
backed up.
<target_instance> The target DB2 instance.
<source_db> The database you want to restore.
<new_db> The target database (specify only if not the source
database).
<table_space> The table space you want to restore.
<log_file> The log file you want to restore.
<session_ID> Backup version ID. For object copies, use the object’s
backup ID (which equals the object’s backup session
ID). Do not use the object’s copy session ID.
For more information, see the omnir man page.

Chapter 2 67
 Integrating IBM DB2 UDB and Data Protector
Restore

Example To restore the DB2 database TEMP from the instance DB2Inst on the DB2
Server system degas, and to roll it forward until the 10th of January
2006, 9:15 a.m., run:
omnir -db2 -barhost degas -instance DB2Inst -dbname TEMP
-rollforward time: 2006-01-10.09.15.00

Restoring to a New Database or Another DB2 Instance

To restore a database to a new database in the source DB2 instance or
another instance:

1. Find the containers of the source database:

• To list table spaces of a particular database that reside on a

particular node, connect to that node, then connect to the
database, and run:
db2 list tablespaces
• To list the containers for a particular table space, run:
db2 list tablespace containers for <table_space_number>

NOTE When restoring a crashed database, you cannot use these commands
because the data is lost.

2. Define new table space containers for the non-system table spaces by
adding options for redirection to the DB2 configuration file. From the
directory:
Windows: <Data_Protector_home>\bin
HP-UX: /opt/omni/lbin/
Other UNIX: /usr/omni/bin/
run:
util_cmd -putopt DB2 <target_instance> "<old_container>"
"<new_container>" -sublist Redirection/<source_db>
for every pair of table space containers.

68 Chapter 2
 Integrating IBM DB2 UDB and Data Protector
Restore

Parameter Description
<target_instance> The target instance.
<source_db> The backed up database.
The DB2 user of the target instance must have read and write
permissions for the new containers.
3. In a physically partitioned environment, repeat steps 1 and 2 on
every system.
4. Restore the source database to the new database without specifying
rollforward. Use the Data Protector GUI or CLI.
In a physically partitioned environment, first restore the part of the
database that resided on the system with the catalog node and then
restore the other parts in any order.
After the restore, the new database enters the rollforward pending
state.
5. If you have restored from an offline backup, perform a rollforward
using DB2 tools:

• In a non-partitioned environment, run:

db2 rollforward db <db_name> stop
• In a partitioned environment, run:
db2 terminate
export DB2NODE=<catalog_node_number>
db2 rollforward db <db_name> stop
If you have restored from an online backup, restore the archived logs,
using the Data Protector GUI, and then perform a rollforward, using
DB2 tools:

a. Log in to the source instance.

b. Ensure that you have permissions to write to the archived logs
directory and restore the archived logs, using the Data Protector
GUI.
The archived logs are restored to the same directory from which
they were backed up.

Chapter 2 69
 Integrating IBM DB2 UDB and Data Protector
Restore

c. Copy the archived and redo logs of the source database to the
corresponding log path directories of the new database (in a
partitioned environment, to every node of the target instance).
If the SQLLPATH.TAG file exists in the target log file directory,
delete it to avoid possible database inconsistencies.
d. If you are restoring to another instance, grant the ownership of
the copied logs to the DB2 user of the target instance and log in to
the target instance.
e. Perform a rollforward using DB2 tools:

• In a non-partitioned environment, run:

db2 rollforward db <db_name> [to <time> | to end of
logs] [and complete]
• In a partitioned environment, run:
db2 terminate
export DB2NODE=<catalog_node_number>
db2 rollforward db <db_name> [to <time> | to end of
logs] [and complete]
The following examples are from a non-partitioned environment.

Example 1 To restore the db2db_old database to the db2db_new database from an

online backup (both databases reside in the db2inst instance, the log
files of db2db_old are located in the
/db2_db/db2inst/NODE0000/SQL00003/SQLLOGDIR directory and
"/tmp/db2cont1" is the container for one of the table spaces:

1. Define a new container, "/tmp/db2cont2", for the table space, using

the Data Protector CLI:
/util_cmd -putopt DB2 db2inst "/tmp/db2cont1" \
"tmp/db2cont2" -sublist Redirection/db2db_old
2. Restore the db2db_old database to the db2db_new database, using
the Data Protector CLI:
omnir -db2 -barhost <source_client> -instance db2inst
-dbname db2db_old -newdbname db2db_new
3. Restore all archived logs needed for rollforward, using the Data
Protector GUI.

70 Chapter 2
 Integrating IBM DB2 UDB and Data Protector
Restore

4. Copy the archived and redo logs of the source database to the
corresponding log path directories of the new database.
5. Perform a rollforward to the end of logs, using the DB2 CLI:
db2 rollforward db db2db_new to end of logs

Example 2 To restore the db2db database, from the instance inst1, to the db2db
database in the inst2 instance:

1. Define a new container /tmp/db2cont2 for the table space, using the
Data Protector CLI:
util_cmd -putopt DB2 inst2 "/tmp/db2cont1"
"/tmp/db2cont2" -sublist Redirection/db2db
2. Restore the db2db database to the inst2 instance, using the Data
Protector CLI:
omnir -db2 -barhost <source_client> [-destination
<target_client>] -instance inst2 -dbname
db2db -frominstance inst1

NOTE When restoring to another instance on another system, use the db2 list
tables for all command to list tables.

Restore in a Partitioned Environment

You can restore a partitioned DB2 object to the original database or to a
new database (on another DB2 instance).

Limitations • You can restore an object from a non-partitioned environment to a

partitioned environment (or the reverse), only if the partitioned
environment has only one node (single partition).
• In a physically partitioned environment, automatic recovery is not
possible.

Restoring to the Original Database

Crashed Database To restore a crashed database:

Chapter 2 71
 Integrating IBM DB2 UDB and Data Protector
Restore

1. Connect to the node that was the catalog node of the crashed
database.
2. Create a new database with the same name.
3. Continue with the restore as described in “Restoring to a New
Database or Another DB2 Instance” on page 68.

Physically Partitioned Environment To restore a physically

partitioned DB2 object (residing on more than one system):

1. Restore the part of the DB2 object that resided on the system with the
catalog node, without specifying rollforward. Use the Data Protector
GUI or CLI.
2. Restore all other parts of the DB2 object to the corresponding systems
in any order, without specifying rollforward.
3. Connect to the catalog node and perform a rollforward, using DB2
tools:
db2 terminate
export DB2NODE=<catalog_node_number>
db2 rollforward db <db_name> [[stop]|[to <time>|to end of
logs] [and complete]]

NOTE The order in which you restore the parts of a DB2 object is only
important if the object resides on the catalog node.

Logically Partitioned Environment To restore a logically

partitioned DB2 object (residing on only one system):

• For a version recovery:

1. Restore the object, without specifying rollforward. Use the Data

Protector GUI or CLI.
2. Connect to the catalog node and perform a rollforward:
db2 terminate
export DB2NODE=<catalog_node_number>
db2 rollforward db <db_name> stop

72 Chapter 2
 Integrating IBM DB2 UDB and Data Protector
Restore

• For a rollforward recovery, restore the object, specifying rollforward.

Use the Data Protector GUI or CLI.

Restoring to a New Database or Another Instance

To restore a database to a new database in the original DB2 instance, see
“Restoring to a New Database or Another DB2 Instance” on page 68.
To restore a database to a new database in another DB2 instance:

1. Log in to the target instance.

2. Ensure that the instance has the same node structure (number of
nodes, node groups) as the source instance.
3. Connect to the node with the same node number as the catalog node
of the source database:
EXPORT DB2NODE=<catalog_node_of_the_source_database>
4. Create a database with the same name as the source database:
db2 create db <source_db>
5. Continue with the restore as described in “Restoring to a New
Database or Another DB2 Instance” on page 68.

Chapter 2 73
 Integrating IBM DB2 UDB and Data Protector
Monitoring Sessions

Monitoring Sessions
You can monitor currently running sessions in the Data Protector GUI.
When you run an interactive backup or restore session, a monitor
window shows you the progress of the session. Closing the GUI does not
affect the session.
You can also monitor sessions from any Data Protector client with the
User Interface component installed, using the Monitor context.
On how to monitor a session, see the online Help index: “viewing
currently running sessions”.

NOTE All DB2 timestamps in messages displayed during rollforward recovery

are by DB2 design in Universal Coordinated Time (UCT) format.

74 Chapter 2
 Integrating IBM DB2 UDB and Data Protector
Troubleshooting

Troubleshooting
This section lists general checks and verifications plus problems you
might encounter when using the Data Protector DB2 integration. Start
at “Problems” on page 76 and if you cannot find a solution there, perform
general checks and verifications.
For general Data Protector troubleshooting information, see the HP
OpenView Storage Data Protector Troubleshooting Guide.

Before You Begin

✓ Ensure that the latest official Data Protector patches are installed.
See the online Help index: “patches” on how to verify this.
✓ See the HP OpenView Storage Data Protector Product
Announcements, Software Notes, and References for general Data
Protector limitations, as well as recognized issues and workarounds.
✓ See http://www.hp.com/support/manuals for an up-to-date list of
supported versions, platforms, and other information.

Checks and Verifications

If your configuration, backup, or restore failed:

✓ Examine system errors reported in the debug.log and db2.log files,

located in the directory:
Windows: <Data_Protector_home>\log
HP-UX and Solaris: /var/opt/omni/log/
Other UNIX: /usr/omni/log/
Additionally, if your backup failed:

✓ Test the backup specification as described in “Previewing Backup

Sessions” on page 59.

— If the DB2 part of the preview fails, see the DB2 documentation.

Chapter 2 75
 Integrating IBM DB2 UDB and Data Protector
Troubleshooting

— If the Data Protector part of the preview fails, create a DB2

backup specification to back up to a null or file device. Successful
backup implies that the problem is related to devices. For
information on troubleshooting devices, see online Help.
Additionally, if your backup or restore failed:

✓ Try performing:

— A Data Protector filesystem backup and restore. For information,

see online Help. After troubleshooting the filesystem backup,
restart the DB2 Server and start a backup of DB2 objects again.
— A backup and restore of DB2 objects using DB2 tools.
Additionally, if your restore failed:

✓ Ensure the target DB2 instance is online and configured for use with
Data Protector.

Problems

Problem Online backup is not allowed

DB2 reports: Online backup is not allowed because either
logretain or userexit for roll-forward is not activated, or
a backup pending condition is in effect for the database.

Action After configuring the DB2 database for rollforward recovery (userexit
and logretain ON), first back up the database offline. If online backup is
started first, the above error is reported.

Problem Offline backup of one or several tablespaces is not allowed

When backing up DB2 tablespaces (not the whole database) offline, DB2
reports that offline backup is not allowed because the DB2 logretain
option is not activated or that a backup pending condition is in effect for
the database.

Action Set the DB2 logretain option to ON.

Problem Archived logs are not backed up

If you have created several archived logs backup specifications and
deleted the one created last, the remaining backup specifications are not
used and archived logs are not backed up.

76 Chapter 2
 Integrating IBM DB2 UDB and Data Protector
Troubleshooting

Action Create a new archived logs backup specification.

Problem Incremental backup is not enabled for the database

If you start an incremental backup before a full backup has been
performed, Data Protector reports: Incremental backup is not
enabled for this database.

Action 1. Activate modification tracking by running:

db2 update db cfg for <database_name> USING TRACKMOD ON
2. Restart the database.
3. Perform a full database backup.

Problem Error occurred while accessing an object

DB2 reports: SQL2048N An error occurred while accessing object
<object>. Reason code: <code_number>
The following can be a reason (code number):

1. An invalid object type is encountered.

2. A lock object operation failed. The lock wait may have reached the
lock timeout limit specified in the database configuration.
3. An unlock object operation failed during the processing of a database
utility.
4. Access to an object failed.
5. An object in the database is corrupted.
6. The object being accessed is a table space. Either the table space is
not in the appropriate state for the operation or some containers of
the table space are not available. (LIST TABLESPACES lists the
current table space state.)
7. A delete object operation failed.
8. Tried to load/quiesce into a table that is not defined on this partition.

Action If a lock object operation failed, ensure that the lock timeout limit in the
database configuration is adequate and resubmit the utility command.
Consider using the QUIESCE command to bring the database to a
quiesced state to ensure access.

Chapter 2 77
 Integrating IBM DB2 UDB and Data Protector
Troubleshooting

Problem Cannot list table spaces

Data Protector reports: Cannot list table spaces.

Action • Ensure that the database is not in a backup/restore/rollforward

pending state.
• Ensure that user root (UNIX only) and the DB2 user are in both the
DB2 and Data Protector admin groups.

Problem Restore from an object copy hangs

Action Before restarting the restore:

• Increase the number of Disk Agent buffers for the device used for the
restore.
• If all objects of the backup are recorded in the IDB:

1. In the Internal Database context of the Data Protector GUI,

search for all objects of the backup. The objects are identified by
the same backup ID.
2. Copy each object in a separate object copy session to a separate
device, for example a file library. For each object, use a separate
medium with the non-appendable media policy.
3. Set the highest media location priority for the newly created
copies.

Problem Restore finishes successfully, but rollforward fails

When performing a rollforward recovery from an online backup, restore
finishes successfully, but rollforward fails.

Action Ensure that the archived logs are available. If they are not, restore them
from the last backup.

78 Chapter 2
3 Integrating Lotus Notes/Domino
Server and Data Protector

Chapter 3 79
 Integrating Lotus Notes/Domino Server and Data Protector
Introduction

Introduction
This chapter explains how to configure and use the Data Protector Lotus
Notes/Domino Server integration. It describes the concepts and methods
you need to understand to back up and restore Lotus Notes/Domino
Server.
Data Protector integrates with Lotus Notes/Domino Server to back up
databases and transaction logs online. During backup, the database can
be actively used.
Data Protector backs up all types of databases (NSF, NTF, and BOX). You
can back up and restore specific databases or the whole server (all
databases under Lotus Notes/Domino Server).
You can also back up:

• Archived transaction logs when archived logging is in effect.

• The current transaction log if Lotus Notes/Domino Server 5.0.4 or
later is installed.
Data Protector offers interactive and scheduled backups of the following
types:
Table 3-1 Lotus Notes/Domino Server Backup Types

Full Backs up the selected Lotus Notes/Domino Server databases

and, if selected, transaction logs, including the one currently in
use.

Incremental Backs up the selected Lotus Notes/Domino Server databases

and, if selected, transaction logs, referencing the last backup of
any type.

Data Protector offers the following restore options:

• Restore without recovery.

• Restore of a specific backup version of a Lotus Notes/Domino Server
database and the possibility of applying changes made since the
backup from the transaction log.
• Recovery of Lotus Notes/Domino Server databases to a specific point
in time or to the latest possible consistent state.

80 Chapter 3
 Integrating Lotus Notes/Domino Server and Data Protector
Introduction

• Restore to the same or a different Lotus Notes/Domino Server.

• Restore of databases to a Lotus Notes/Domino Server location other
than originally backed up from.
• Automatic restore of archived transaction logs in the case of recovery.
A database restore is possible even while Lotus Notes/Domino Server is
running, with no impact on other databases currently in use. To enable a
recovery using the logs from an online backup, Lotus Notes/Domino
Server must be set to use archived transaction logging.
This chapter provides information specific to the Data Protector Lotus
Notes/Domino Server integration. For general Data Protector procedures
and options, see online Help.

Chapter 3 81
 Integrating Lotus Notes/Domino Server and Data Protector
Integration Concepts

Integration Concepts
The Data Protector Lotus Notes/Domino Server integration provides
online backup, restore, and recovery of Lotus Notes/Domino Server, using
the Lotus C API. Figure 3-1 shows the architecture of the integration.

Figure 3-1 Data Protector Lotus Notes/Domino Server Integration

Architecture

Table 3-2 Legend

SM Data Protector Session Manager: Backup Session Manager

during backup and Restore Session Manager during restore.

ldbar.exe The central component of the integration, installed on the

Lotus Notes/Domino Server system, which controls activities
between Lotus Notes/Domino Server and Data Protector
backup and restore processes.

Lotus C API The Lotus-defined interface that enables data transfer

between Data Protector and the Lotus Notes/Domino Server.

Notes Data A set of Lotus Notes/Domino Server databases, where users

create, update, store, and track documents in various
formats.

82 Chapter 3
 Integrating Lotus Notes/Domino Server and Data Protector
Integration Concepts

Table 3-2 Legend

MA Data Protector General Media Agent.

Backup A list of objects to be backed up, backup devices, and options

Specification to be used.

IDB The Data Protector Internal Database.

Lotus Notes/Domino Server databases are backed up in parallel. The

number of streams equals the sum of concurrencies of all the devices
used. The concurrency is defined in the backup specification.

Chapter 3 83
Integrating Lotus Notes/Domino Server and Data Protector
Configuring the Integration

Configuring the Integration

You need to configure a Lotus Notes/Domino Server user and every Lotus
Notes/Domino Server you intend to back up or restore.

Prerequisites
• Ensure that you have correctly installed and configured Lotus
Notes/Domino Server.

— For supported versions, platforms, devices, and other information,

see the HP OpenView Storage Data Protector Product
Announcements, Software Notes, and References or
http://www.hp.com/support/manuals.
— For information on installing, configuring, and using Lotus
Notes/Domino Server, see the Lotus Notes/Domino Server
documentation.
• Ensure that you have correctly installed Data Protector. On how to
install Data Protector in various architectures, see the HP OpenView
Storage Data Protector Installation and Licensing Guide.
Every Lotus Notes/Domino Server system you intend to back up from
or restore to must have the Data Protector Lotus Integration
component installed.

Before You Begin

✓ Configure devices and media for use with Data Protector.
✓ To test whether the Lotus Notes/Domino Server system and the Cell
Manager communicate properly, configure and run a Data Protector
filesystem backup and restore on the Lotus Notes/Domino Server
system.

Transaction Logging of Lotus Notes/Domino Server

To enable recovery from an online backup, Lotus Notes/Domino Server
must be set to use transaction logging. This way, transactions are stored
to the transaction log directory and can be used to apply or undo
database transactions during database recovery.

84 Chapter 3
 Integrating Lotus Notes/Domino Server and Data Protector
Configuring the Integration

You can perform daily full backups of transaction logs instead of full
database backups.
Transaction logging works with databases in Domino Release 5 format or
later. After enabling transaction logging, all databases are automatically
logged.
With transaction logging enabled, multiple S0000000.TXN files may
appear in the log directory.
Table 3-3 Transaction Logging Styles

Circular logging The default mode. Lotus Notes/Domino Server

continuously reuses the same log file, which is defined at a
designated size, thus overwriting old transactions once
the transaction log is filled. You can recover only
transactions stored in the transaction log. Archiving of
transaction logs is not possible.

Archived logging Lotus Notes/Domino Server does not reuse log extents
until they are backed up. The system uses transaction logs
to apply or undo database transactions not flushed to disk
for databases that were open when system failure
occurred.

IMPORTANT To back up log files in an incremental backup, transaction logging must

be set to archived logging.

Enabling Transaction Logging

Use Lotus Domino Administrator on the Lotus Notes/Domino Server
system. Alternatively, use Web Administrator or edit the notes.ini
file.
In a cluster environment, enable transaction logging on all cluster nodes.
To enable transaction logging and set archived logging:

1. Start Lotus Domino Administrator.

2. Log on to Lotus Notes/Domino Server and select the Configuration
tab.
3. Expand Server, select All Server Documents, and select the
desired Lotus Notes/Domino Server. See Figure 3-2.

Chapter 3 85
 Integrating Lotus Notes/Domino Server and Data Protector
Configuring the Integration

Figure 3-2 Browsing Lotus Notes/Domino Server

4. Select the Transactional Logging tab and set appropriate values.

See Figure 3-3.

86 Chapter 3
 Integrating Lotus Notes/Domino Server and Data Protector
Configuring the Integration

Figure 3-3 Enabling Archived Transactional Logging

5. Save the settings and restart Lotus Notes/Domino Server for the
changes to take effect.

Creating a Link to the Lotus C API Library

On UNIX systems, create a link to the Lotus C API library to run the
Lotus Integration Agent:

1. Logged in as user root, connect to the Lotus Notes/Domino Server

system.
2. Change to the directory:
HP-UX and Solaris: /opt/omni/lib
AIX: /usr/omni/lib
3. Create a soft link to the library:
HP-UX: ln -s <DOMINO_EXEC>/libnotes.sl libnotes.sl
Solaris: ln -s <DOMINO_EXEC>/libnotes.so libnotes.so
AIX: ln -s <DOMINO_EXEC>/libnotes_r.a libnotes_r.a

Chapter 3 87
 Integrating Lotus Notes/Domino Server and Data Protector
Configuring the Integration

Examples HP-UX:
ln -s /opt/lotus/notes/latest/hppa/libnotes.sl libnotes.sl
Solaris:
ln -s /opt/lotus/notes/latest/sunspa/libnotes.so libnotes.so
AIX:
ln -s /opt/lotus/notes/latest/ibmpow/libnotes_r.a
libnotes_r.a

Configuring Lotus Notes/Domino Server Users

On UNIX, add the Lotus Notes/Domino Server administrator to the Data
Protector admin or operator user group. You need to specify this user in
backup specifications. By default, this user is notes in the group notes.
Additionally, add the operating system user root on the Lotus
Notes/Domino Server system to the Data Protector admin or operator
user group.
For information, see the online Help index: “adding users”.

Configuring the Data Protector Lotus Notes/Domino

Server Integration

Using the Data Protector GUI

1. In the Context list, click Backup.

2. In the Scoping Pane, expand Backup Specifications, right-click
Lotus Server, and click Add Backup.
3. In the Create New Backup dialog box, click OK.
4. In Client, select the Lotus Notes/Domino Server system. In a cluster
environment, select the virtual server.
In Application database, select the name of the Lotus
Notes/Domino Server to be backed up.
UNIX only: Type the username and user group of the Lotus
Notes/Domino Server administrator. This user will be the owner of
the backup.
See Figure 3-4.

88 Chapter 3
 Integrating Lotus Notes/Domino Server and Data Protector
Configuring the Integration

Figure 3-4 Specifying the Lotus Notes/Domino Server System

Click Next.
5. In the Configure Lotus dialog box, specify the pathname of the
notes.ini file on the Lotus Notes/Domino Server system.
Review and – if necessary – update other automatically determined
options.
See Figure 3-5.

Chapter 3 89
 Integrating Lotus Notes/Domino Server and Data Protector
Configuring the Integration

Figure 3-5 Specifying Lotus Notes/Domino Server Data

Click OK.
If an error occurs, click Details or see “Troubleshooting” on
page 108.
6. The integration is configured. Exit the GUI or proceed with creating
the backup specification at step 6 on page 95.

Using the Data Protector CLI

On the Lotus Notes/Domino Server system, run:
Windows:
<Data_Protector_home>\bin\util_notes.exe -CONFIG
-SERVER:<SRV_NAME> -INI:<notes.ini_file>
HP-UX and Solaris:
/opt/omni/lbin/util_notes.exe -CONFIG -SERVER:<SRV_NAME>
-INI:<notes.ini_file> -HOMEDIR:<Lotus_home_directory>
-DATADIR:<Domino_data_directory>
-EXECDIR:<Domino_executables_directory>

90 Chapter 3
 Integrating Lotus Notes/Domino Server and Data Protector
Configuring the Integration

AIX:
/usr/omni/bin/util_notes.exe -CONFIG -SERVER:<SRV_NAME>
-INI:<notes.ini_file> -HOMEDIR:<Lotus_home_directory>
-DATADIR:<Domino_data_directory>
-EXECDIR:<Domino_executables_directory>

Parameter Description
<SRV_NAME> Lotus Notes/Domino Server name.
<notes.ini_file> Pathname of the Lotus Notes/Domino Server
notes.ini file.
<Lotus_home_directory> Pathname of the Lotus Notes/Domino
Server home directory.
<Domino_data_directory> Pathname of the Lotus Notes/Domino
Server data directory.
<Domino_executables_directory> Pathname of the Lotus
Notes/Domino Server executables directory.

Examples Windows:
<Data_Protector_home>\bin\util_notes.exe -CONFIG
–SERVER:BLUE –INI:d:\Lotus\Domino\BLUE\notes.ini
HP-UX and Solaris:
/opt/omni/lbin/util_notes.exe -CONFIG -SERVER:BLUE
-INI:/opt/lotus/notesdata/notes.ini -HOMEDIR:/opt/lotus
-DATADIR:/opt/lotus/notesdata
-EXECDIR:/opt/lotus/notes/latest/hppa

Checking the Configuration

You can check the configuration of the Lotus Notes/Domino Server using
the Data Protector GUI after you have created at least one backup
specification for the Lotus Notes/Domino Server. If you use the Data
Protector CLI, a backup specification is not needed.

Using the Data Protector GUI

1. In the Context List, click Backup.

Chapter 3 91
Integrating Lotus Notes/Domino Server and Data Protector
Configuring the Integration

2. In the Scoping Pane, expand Backup Specifications and then

Lotus Server. Click the backup specification to display the server to
be checked.
3. Right-click the server and click Check Configuration.

Using the Data Protector CLI

On the Lotus Notes/Domino Server system, from the directory:
Windows: <Data_Protector_home>\bin
HP-UX and Solaris: /opt/omni/lbin
AIX: /usr/omni/bin/
run:
util_notes.exe -CHKCONF -SERVER:<SRV_NAME>
Data Protector checks the path to the specified directories and files.
Successful configuration displays the message *RETVAL*0.

Handling Errors If an error occurs, the error number is displayed in

the form *RETVAL*<error_number>.
To view the error description:
Windows: On the Cell Manager, see the file
<Data_Protector_home>\help\enu\Trouble.txt
HP-UX and Solaris: Run:
/opt/omni/lbin/omnigetmsg 12 <error_number>
AIX: Run:
/usr/omni/bin/omnigetmsg 12 <error_number>

92 Chapter 3
 Integrating Lotus Notes/Domino Server and Data Protector
Backup

Backup
The integration provides backup of the following types:
Table 3-4 Lotus Notes/Domino Server Backup Types

Full Backs up the selected Lotus Notes/Domino Server databases

and, if selected, transaction logs, including the one currently in
use.

Incremental Backs up the selected Lotus Notes/Domino Server databases

and, if selected, transaction logs referencing the last backup of
any type. If there is no full Lotus Notes/Domino Server backup
in the IDB, a full backup is performed by default.
If the size of data that has changed since the last backup of a
specific database exceeds the amount set in the Amount of
log option, a full backup of that database is performed.
Otherwise backup of the database is skipped.
If transaction logs are selected, a full backup of transaction
logs that are ready to be archived is performed. Ensure that
transaction logging is set to archived to enable the backup of
logs.

What Is Backed Up?

Lotus Notes/Domino Server databases consist of the following files:

• NSF (Notes Storage Facility) files.

• NTF (Notes Template Facility) files - templates for creating new NSF
databases.
• BOX files - files used by the mail router.
• Transaction log files, named SXXXXXXX.TXN, where XXXXXXX is a 7
digit number that is automatically incremented for every new
transaction file.
Lotus Notes/Domino Server automatically recycles archived
transaction logs after backup.

Chapter 3 93
 Integrating Lotus Notes/Domino Server and Data Protector
Backup

IMPORTANT Archived transaction log files must be backed up frequently, so that log
files do not exceed the defined amount of disk space.

TIP To speed up a Lotus Notes/Domino Server backup, exclude NTF files

from the backup specification. Create a separate backup specification to
back up NTF files. These files do not need to be backed up frequently
because they do not change.

What Is Not Backed Up?

You must back up the following non-database files using a filesystem
backup:

• notes.ini
• desktop.dsk
• all *.id files

Creating Backup Specifications

Create a backup specification using the Data Protector Manager.

1. In the Context list, click Backup.

2. In the Scoping Pane, expand Backup Specifications, right-click
Lotus Server, and click Add Backup.
3. In the Create New Backup dialog box, click OK.
4. In Client, select the Lotus Notes/Domino Server system. In a cluster
environment, select the virtual server.
In Application database, select the Lotus Notes/Domino Server to
be backed up.
UNIX only: Type the username and user group of the Lotus
Notes/Domino Server administrator, who will be the owner of the
backup.
Click Next.

94 Chapter 3
 Integrating Lotus Notes/Domino Server and Data Protector
Backup

5. If Lotus Notes/Domino Server is not configured yet for use with Data
Protector, the Configure Lotus dialog box is displayed. Configure
the integration as described in “Configuring the Data Protector Lotus
Notes/Domino Server Integration” on page 88.
6. Select the Lotus Notes/Domino Server objects to be backed up. See
Figure 3-6.

Figure 3-6 Selecting Backup Objects

Click Next.
7. Select devices to use for the backup.
To specify device options, right-click the device and click Properties.
Click Next.
8. Set backup options. For information on the application specific
options (Figure 3-7), see Table 3-5 on page 96 or press F1.

Chapter 3 95
 Integrating Lotus Notes/Domino Server and Data Protector
Backup

Figure 3-7 Application Specific Options

Click Next.
9. Optionally, schedule the backup. See “Scheduling Backup
Specifications” on page 97.
Click Next.
10. Save the backup specification, specifying a name and a backup
specification group.

TIP Preview your backup specification before using it for real. See
“Previewing Backup Sessions” on page 98.

Table 3-5 Lotus Notes/Domino Server Backup Options

Amount of log Applies to incremental backups. If the database to be

backed up has a smaller log amount than specified, the
backup skips the database. If the database exceeds the
specified log amount, a full backup of the database is
performed.

96 Chapter 3
 Integrating Lotus Notes/Domino Server and Data Protector
Backup

Table 3-5 Lotus Notes/Domino Server Backup Options

Pre-exec, Specify a command that will be started by ldbar.exe on

Post-exec the Lotus Notes/Domino Server system before the backup
(pre-exec) or after it (post-exec). The command must
reside in the directory:
Windows: <Data_Protector_home>\bin
HP-UX and Solaris: /opt/omni/lbin
AIX: /usr/omni/bin
In the backup specification, provide only the filename.

Backup buffer The size of the buffer used for reading and writing data
size during the backup.

Modifying Backup Specifications

To modify your backup specification, click its name in the Scoping Pane
of the Backup context, then click the appropriate tab, and apply the
changes.

Scheduling Backup Specifications

You can run unattended backups at specific times or periodically. For
details on scheduling, see the online Help index: “scheduled backups”.

Scheduling Example
To back up Lotus Notes/Domino Server at 9.00 a.m., 1.00 p.m., and 6.00
p.m. during week days:

1. In the Schedule property page, select the starting date in the

calendar and click Add to open the Schedule Backup dialog box.
2. Under Recurring, select Weekly. Under Time options, select 9 AM.
Under Recurring Options, select Mon, Tue, Wed, Thu, and Fri. See
Figure 3-8.
Click OK.
3. Repeat steps 1 and 2 to schedule backups at 1 p.m. and 6 p.m.
4. Click Apply to save the changes.

Chapter 3 97
 Integrating Lotus Notes/Domino Server and Data Protector
Backup

Figure 3-8 Scheduling Backups

Previewing Backup Sessions

Preview the backup session to test it. You can use the Data Protector
GUI or CLI.

Using the Data Protector GUI

1. In the Context List, click Backup.

2. In the Scoping Pane, expand Backup Specifications and then
Lotus Server. Right-click the backup specification you want to
preview and click Preview Backup.
3. Specify the Backup type and Network load. Click OK.
The message Session completed successfully is displayed at the end
of a successful preview.

98 Chapter 3
 Integrating Lotus Notes/Domino Server and Data Protector
Backup

Using the Data Protector CLI

A test can be performed on the Lotus Notes/Domino Server system or on
any Data Protector client system within the same Data Protector cell
with the Data Protector User Interface installed.
From the directory:
Windows: <Data_Protector_home>\bin
HP-UX and Solaris: /opt/omni/bin/
AIX: /usr/omni/bin/
Run:
omnib -lotus_list <backup_specification_name> -test_bar

What Happens During the Preview?

The command tests the Data Protector part of the configuration. The
following is tested:

• Communication between Lotus Notes/Domino Server and Data

Protector.
• The syntax of the backup specification.
• If devices are correctly specified.
• If the necessary media are in the devices.

Starting Backup Sessions

Interactive backups are run on demand. They are useful for urgent
backups or for restarting failed backups.
You can start the backup using:

• The Data Protector GUI.

• The Data Protector CLI. See the omnib man page.

Using the Data Protector GUI

1. In the Context List, click Backup.

2. In the Scoping Pane, expand Backup Specifications, and then
Lotus Server. Right-click the backup specification you want to start
and click Start Backup.

Chapter 3 99
Integrating Lotus Notes/Domino Server and Data Protector
Backup

3. Select the Backup type and Network load. Click OK.

The message Session completed successfully is displayed at the end
of a successful backup session.

100 Chapter 3
 Integrating Lotus Notes/Domino Server and Data Protector
Restore

Restore
You can restore databases directly to the Lotus Notes/Domino Server
system. When you restore a database, the database is brought offline,
restored, and brought online. Transaction logs are also restored if
needed. If recovery is selected, the restore of archived logs is performed
automatically during the recovery process.
You can restore a database restore while the server is online, if the
database is not being accessed. A newly-restored Lotus Notes/Domino
Server database is not active. If you access it, it will automatically be
brought online, but a recovery using the backed up logs will not be
performed. To get the last possible consistent state of the databases or to
perform a recovery to a specific point in time, use the Recover option.
You can restore a database to:

• Its original location at backup time.

Select this to replace a corrupted or deleted database.
• A different location.
Select this to keep the original database intact.
Recovery to a different client system is not possible.

Restoring Lotus Notes/Domino Server Data

You can restore Lotus Notes/Domino Server objects using:

• The Data Protector GUI.

• The Data Protector CLI. See the omnir man page.
Localized databases only: If the names of backed up objects
contain characters that cannot be displayed using the current
language group (on Windows) or code page (on UNIX):

✓ Set the environment variable OB2_CLI_UTF8 to 1.

✓ Windows only: Set the encoding used by the terminal to UTF-8.

Chapter 3 101
 Integrating Lotus Notes/Domino Server and Data Protector
Restore

If not set, names of backup objects returned by the Data Protector

CLI commands (for example omnidb) may not be usable when
providing the parameters to other Data Protector commands (for
example omnir).

Using the Data Protector GUI

1. In the Context List, click Restore.

2. In the Scoping Pane, expand Lotus Server, expand the client from
which the data was backed up, and select the instance you want to
restore.
3. In the Source page, select objects for restore. See Figure 3-9.

Figure 3-9 Selecting Objects for Restore

NOTE In the Source page all backed up databases are listed. When restoring
multiple databases from a specific backup session, ensure that the
databases were backed up in the selected backup session. If not, the

102 Chapter 3
 Integrating Lotus Notes/Domino Server and Data Protector
Restore

warning Object not found in the database appears at restore time.

Restoring from different backup sessions demands separate restore
sessions. The only exception is when the backup session is not specified.
In such cases, the Lotus Integration Agent finds the latest backup
version of each database for restore.

You can select the backup version in the Options page (Figure 3-10).
Click Browse to select a different version of backup.
4. In the Destination page, set the destination options. For
information, see Table 3-6 on page 105 or press F1.

IMPORTANT If you restore to a location where a database with the same file name
resides as the one being restored, then this database is taken offline and
deleted.

5. In the Options page, set the restore options (Figure 3-10). For
information on the application specific options, see Table 3-7 on
page 106 or press F1.

Chapter 3 103
 Integrating Lotus Notes/Domino Server and Data Protector
Restore

Figure 3-10 Lotus Notes/Domino Server Restore Options

6. In the Devices page, the devices and media for restore are
automatically selected.
You can also restore using a device other than that used for backup.
On how to specify another device for restore, see the online Help
index: “restore, selecting devices for”.
7. Click Restore.
8. In the Start Restore Session dialog box, click Next.
9. Specify the Report level and Network load.
Click Finish to start the restore.
The message Session completed successfully is displayed at the
end of a successful session.

104 Chapter 3
 Integrating Lotus Notes/Domino Server and Data Protector
Restore

Restore Options
Specify destination and restore options specific to the Data Protector
Lotus Notes/Domino Server integration. If the target system is a UNIX
system, specify UNIX specific options as well.
Table 3-6 Destination Options

Target client By default, the target Data Protector Lotus Notes/Domino

Server client is the system from which the application data
was backed up.
Databases can be restored to a Lotus Notes/Domino Server
system other than the one from which the backup was
made. The new target client must be a part of the Data
Protector cell and have the Lotus Notes/Domino Server
integration installed and configured.

Restore to By default, databases are restored to the same directory

original from which they were backed up (either on the original
location system or on some other system you selected).

Restore to new This option enables you to restore your data to another
location directory. Specify the relative path to the Lotus
Notes/Domino Server data directory where you want to
restore your data.

Example Lotus Notes/Domino Server data directory is located in:

Windows: C:\Lotus\Domino\BLUE\
UNIX: /opt/lotus/notesdata/BLUE/
To restore a database to the directory:
Windows: C:\Lotus\Domino\BLUE\restore_dir\
UNIX: /opt/lotus/notesdata/BLUE/restore_dir/
select Restore to new location and type restore_dir. The restored
database filenames are the same as they were at backup time.

Chapter 3 105
 Integrating Lotus Notes/Domino Server and Data Protector
Restore

Table 3-7 Restore Options

Username UNIX only: Username of the Lotus Notes/Domino

Server backup owner, for example, notes.

User group UNIX only: User group of the Lotus Notes/Domino

Server backup owner, for example, notes.
Restore options

Backup version By default, a restore is performed from the last full

backup of the database. Click Browse to select a
backup version other than the last one.

Parallelism Specify how many Lotus Integration Agents will start

for the restore. The default value is 1.

Recover (last Select this to recover the database to the last possible
possible consistent state. This also includes the restore of
consistent archived transaction logs if needed during recovery.
state)
Recovery type options

Point in time The point in time to which the database state should
recovery be recovered. Click Browse to specify the desired date
and time. Only transactions written before the
specified date and time are applied to the database.

Do not recover The default option. Select this to restore databases

without recovering them from the backed up logs.
Transactions made after the backup are not reflected
in the restored databases.

106 Chapter 3
 Integrating Lotus Notes/Domino Server and Data Protector
Monitoring Sessions

Monitoring Sessions
You can monitor currently running sessions in the Data Protector GUI.
When you run an interactive backup or a restore session, a monitor
window shows you the progress of the session. Closing the GUI does not
affect the session.
You can also monitor sessions from any Data Protector client with the
User Interface component installed, using the Monitor context.
On how to monitor a session, see the online Help index: “viewing
currently running sessions”.

Chapter 3 107
Integrating Lotus Notes/Domino Server and Data Protector
Troubleshooting

Troubleshooting
This section lists Lotus Notes/Domino Server checks, general checks and
verifications, plus problems you might encounter when using the Data
Protector Lotus Notes/Domino Server integration. Start at “Problems” on
page 113 and if you cannot find a solution there, go through the checks
and verifications.
For general Data Protector troubleshooting information, see the HP
OpenView Storage Data Protector Troubleshooting Guide.

Before You Begin

✓ Ensure that the latest official Data Protector patches are installed.
See the online Help index: “patches” on how to verify this.
✓ See the HP OpenView Storage Data Protector Product
Announcements, Software Notes, and References for general Data
Protector limitations, as well as recognized issues and workarounds.
✓ See http://www.hp.com/support/manuals for an up-to-date list of
supported versions, platforms, and other information.

Checking the Lotus Notes/Domino Server Side

If you encounter errors when performing the following checks, contact
Lotus Notes/Domino Server support. For more information on these
procedures, see the Lotus Notes/Domino Server documentation.
Windows:

✓ Check if the nNotes.dll library is linked. Run:

<Data_Protector_home>\bin\util_notes.exe -app
If nNotes.dll is not linked, the following error is displayed:

108 Chapter 3
 Integrating Lotus Notes/Domino Server and Data Protector
Troubleshooting

Figure 3-11 Unable to Locate DLL Error

✓ Check if the nNotes.dll library is in the environment path.

If not, add it. By default, nNotes.dll is located in the Lotus
Notes/Domino Server executables directory.
UNIX:

✓ Check the environment variables.

Prior to any Lotus C API call from the Data Protector Lotus
Integration Agent, the Lotus C API must be initialized. For successful
initialization, the following environment variables must be set:
LOTUS=/opt/lotus
NOTES_DATA_DIR=/local/notesdata
HP-UX: Notes_ExecDirectory=<Lotus_home>/notes/latest/hppa
Solaris:
Notes_ExecDirectory=<Lotus_home>/notes/latest/sunspa
AIX: Notes_ExecDirectory=<Lotus_home>/notes/latest/ibmpow
PATH=$PATH:$LOTUS:$NOTES_DATA_DIR:$Notes_ExecDirectory:/o
pt/lotus/bin:$Notes_ExecDirectory/res/C
These variables are usually exported by the Lotus Integration Agent
prior to Lotus C API initialization. If you experience problems with
Lotus C API initialization, export these variables manually or put
them into the omnirc file. On how to use the omnirc file, see the HP
OpenView Storage Data Protector Troubleshooting Guide.
✓ Check if the soft link from the following directory to the Lotus
Notes/Domino Server libnotes library exists on all Lotus
Notes/Domino Server clients in your cell:
HP-UX: /opt/omni/lib/libnotes.sl
Solaris: /opt/omni/lib/libnotes.so
AIX: /usr/omni/lib/libnotes_r.a

Chapter 3 109
 Integrating Lotus Notes/Domino Server and Data Protector
Troubleshooting

The name of the link must be the same as the name of the libnotes
library in the Lotus Notes/Domino Server executables directory.

Example HP-UX:
libnotes.sl -> /opt/lotus/notes/latest/hppa/libnotes.sl
Solaris:
libnotes.so -> /opt/lotus/notes/latest/sunspa/libnotes.so
AIX:
libnotes_r.a ->
/opt/lotus/notes/latest/ibmpow/libnotes_r.a
Check if the soft link works by running:
HP-UX and Solaris: /opt/omni/lbin/util_notes.exe -app
AIX: /usr/omni/bin/util_notes.exe -app
If the soft link is set correctly, the *RETVAL*0 message is displayed.

Checks and Verifications

If your configuration, backup, restore, or recovery failed:

✓ Examine system errors reported in the debug.log file on the Lotus

Notes/Domino Server system, located in the directory:
Windows: <Data_Protector_home>\log
HP-UX and Solaris: /var/opt/omni/log/
AIX: /usr/omni/log/
✓ Verify that the Data Protector software has been installed properly.
See “Verifying Data Protector Client Installation” in the HP
OpenView Storage Data Protector Installation and Licensing Guide
for details.
✓ Check whether the Data Protector Lotus Integration Agent
ldbar.exe is installed on the system.
✓ Windows only: Verify the inet startup parameters on the Lotus
Notes/Domino Server system.

110 Chapter 3
 Integrating Lotus Notes/Domino Server and Data Protector
Troubleshooting

Make sure the Data Protector Inet service is running under a user
that is a member of the Data Protector admin user group. For
information, see the online Help index: “Inet, changing account”.
✓ Check the omnirc environment settings.
On how to use the omnirc file, see the HP OpenView Storage Data
Protector Troubleshooting Guide.
✓ Check errors during the backup or restore session.
Error related to Lotus Notes/Domino Server take the following form:
Lotus ERROR [error #]: <Error description>
Examine the error description and take appropriate actions.
Additionally, if your backup failed:

✓ Check your Lotus Notes/Domino Server configuration as described in

“Checking the Configuration” on page 91.
✓ Perform a filesystem backup of the Lotus Notes/Domino Server
system.
Observe session messages and examine system errors reported in the
debug.log file on the

— Data Protector Lotus Notes/Domino Server client if the Lotus

Notes/Domino Server part of the filesystem backup fails.
— Data Protector Cell Manager system if the Data Protector part of
the filesystem backup fails.
✓ Verify Data Protector internal data transfer using the testbar
utility.

1. From the directory:

Windows: <Data_Protector_home>\bin
HP-UX and Solaris: /opt/omni/bin/utilns
AIX: /usr/omni/bin/utilns
run:
testbar -type:Lotus -appname:<SRV_NAME>
-bar:<backup_specification_name> -perform:backup

Chapter 3 111
Integrating Lotus Notes/Domino Server and Data Protector
Troubleshooting

2. Create a Lotus Notes/Domino Server backup specification to back

up to a null device or file. If the backup succeeds, the problem may
be related to the backup devices.
✓ Start a backup session using ldbar.exe.
You can start a backup of a single database using the Data Protector
CLI, specifying backup options as ldbar.exe command line options.
On the Data Protector Lotus Notes/Domino Server client, from the
directory:
Windows: <Data_Protector_home>\bin
HP-UX and Solaris: /opt/omni/bin
AIX: /usr/omni/bin
run:
Windows:
ldbar.exe -perform:backup -db:<DB_NAME>
-server:<SRV_NAME> -ini:<path to notes.ini file>
-bar:<backup_specification_name>
UNIX:
ldbar.exe -perform:backup -db:<DB_NAME>
-server:<SRV_NAME> -ini:<path to notes.ini file>
-bar:<backup_specification_name> -homedir:<path to Lotus
home> -datadir:<path to Domino data> -execdir:<path to
Domino executables>
The -bar option is mandatory because ldbar.exe reads the device
options from the backup specification as opposed to other options in
the backup specification, which are ignored. Command line options
are used instead.
For other ldbar.exe parameters, run ldbar.exe -help.
✓ Windows only: When Lotus Notes/Domino Server and Windows
Terminal Services coexist on the same system and Lotus
Notes/Domino Server is started from the terminal client program,
Lotus Notes/Domino Server backup cannot be performed.
Windows Terminal Services should not be used to manage Lotus
Notes/Domino Server. However, Lotus Notes/Domino Server backup
can be performed when using the terminal service client program to

112 Chapter 3
 Integrating Lotus Notes/Domino Server and Data Protector
Troubleshooting

start the Data Protector GUI on the system where Lotus

Notes/Domino Server is running. Lotus Notes/Domino Server can be
managed locally or with a VNC program.
Additionally, if your restore failed:

✓ Perform a test restore of any filesystem on the problematic client.

✓ Test a restore session using the ldbar.exe command on the Data
Protector Lotus Notes/Domino Server system. From the directory:
Windows: <Data_Protector_home>\bin
HP-UX and Solaris: /opt/omni/bin
AIX: /usr/omni/bin
run:
ldbar.exe -perform:restore -db:<DB_NAME>
-server:<SRV_NAME> -ini:<path to notes.ini file>
For other ldbar.exe parameters, run ldbar.exe -help.
Additionally, if your recovery failed:

✓ Check if the recovery time parameter is set in a 24 hour format:

yyyy/mm/dd.hh:mm:ss

Example 2006/01/25.18:15:00

Problems

Problem Script failed error

While configuring or starting a backup using the Data Protector GUI,
the following error is displayed:
Script failed. Cannot get information from remote host.

Action On how to solve this problem, see “Checking the Lotus Notes/Domino
Server Side” on page 108.

Problem Lotus Notes/Domino Server freezes during backup

Lotus Notes/Domino Server freezes with the following error:
Fatal Error signal = 0x0000000b PID/TID = xxxx/l

Chapter 3 113
 Integrating Lotus Notes/Domino Server and Data Protector
Troubleshooting

Freezing all server threads ...

This can happen in the following cases:

• The Lotus Notes C API initialization failed.

• UNIX only: If Lotus Notes/Domino Server is not online and the Lotus
Notes/Domino Server daemon logasio is not running, then while the
Lotus Integration Agent is initializing the Lotus C API, the logasio
daemon automatically starts. Since the environment for user notes is
not set because the .profile is not executed, the logasio server
could fail to start.

Action Kill the ldbar.exe or logasio processes:

a. UNIX only: Log in to the Lotus Notes/Domino Server system as user

root.
b. Windows only: Kill all the ldbar.exe processes using Task
Manager.
c. UNIX only: Kill all the ldbar.exe and logasio processes.
d. If Lotus Notes/Domino Server is running, restart it. Before restarting,
ensure that no Lotus Notes/Domino Server processes are still
running.
e. Log in as user notes and check if Lotus Notes/Domino Server
recovered. From the directory:
Windows: <Data_Protector_home>\bin
HP-UX and Solaris: /opt/omni/lbin
AIX: /usr/omni/bin
run: util_notes.exe -box -ini:<path_to_notes.ini>
If everything is working properly, the *RETVAL*0 message is
displayed.

NOTE On UNIX, you need to clean up shared memory and semaphores before
restarting Lotus Notes/Domino Server.

114 Chapter 3
 Integrating Lotus Notes/Domino Server and Data Protector
Troubleshooting

Problem Restore of Lotus Notes/Domino Server 6.0.1 databases failed

During restore, the following error is displayed due to a Lotus
Notes/Domino Server 6.0.1 issue:
[Minor] From: [email protected] "LOTUS" Time:
1/16/2006 9:57:01 AM
Lotus Notes C API 'NSFTakeDatabaseOffline' returned error
3744: Recovery Manager: Preserving backups by skipping fixup
of logged DB without -j switch, DB=%p.

Action Upgrade the Lotus Notes/Domino Server 6.0.1 to 6.0.2.

Problem Restore to another client failed

Action Ensure that Lotus Notes/Domino Server is installed on the target system
and that it has the same non-database files as the Lotus Notes/Domino
Server system whose backup is to be restored. These files must be
restored first from a filesystem backup.

Problem Recovery of restored Lotus Notes/Domino Server NSF database

failed
During recovery, the following error message is displayed:
[Critical] From: [email protected] "BLUE" Time: 19.10.01
17:24:23

Lotus Notes C API 'NSFGetTransLogStyle' returned error

5114:Recovery Manager: Recovery only supported for Backup
Files.
This indicates that at least one database from the restore list was
accessed before the recovery ended, either by Lotus Notes/Domino
Server, a user, or a process.

Action 1. Restart the Lotus Notes/Domino Server system and perform the
restore again.
2. Restore the failed database to a location other than the one it was
backed up from.

Chapter 3 115
 Integrating Lotus Notes/Domino Server and Data Protector
Troubleshooting

Problem Recovery failed with Lotus ERROR [520]

During recovery, the following error message is displayed:
[Critical] From: [email protected] "BLUE" Time: 1.10.01
9:04:23
Lotus Notes C API 'NSFGetTransLogStyle' returned error
520:
This can happen if you have restored several databases but some of them
were not under transaction logging at backup time. Therefore no
database was in the list for recovery. This happens when recovering NTF
databases or an NSF database that is not recoverable.

NOTE No description is listed for error number 520. Several Lotus

Notes/Domino Server error codes are internal and have no description
listed.

Action Try to restore only one database, which you are sure it is recoverable,
and observe messages. It might be that one database in the restore list is
corrupt (was corrupted at backup time) and therefore the Lotus C API
recovery call fails.

116 Chapter 3
Glossary

access rights archived redo log (Oracle specific

See user rights. term)
Also called offline redo log. If the
ACSLS (StorageTek specific term) Oracle database operates in the
The Automated Cartridge System ARCHIVELOG mode, as each online
Library Server (ACSLS) software that redo log is filled, it is copied to an
manages the Automated Cartridge archived log destination. This copy is
System (ACS). the archived redo log. The presence or
absence of an archived redo log is
Active Directory (Windows specific determined by the mode the database is
term) using:
The directory service in a Windows
network. It contains information about • ARCHIVELOG - The filled online
resources on the network and makes redo log files are archived before
them accessible to users and they are reused. The database can be
applications. The directory services recovered if an instance or a disk
provide a consistent way to name, fails. A “hot” backup can be
describe, locate, access and manage performed only when the database is
resources regardless of the physical running in this mode.
system they reside on.
• NOARCHIVELOG - The filled
AML (EMASS/GRAU specific term) online redo log files are not
Automated Mixed-Media library. archived.

application agent See also online redo log.

A component needed on a client to back
up or restore online database archive logging (Lotus Domino Server
integrations. specific term)
See also Disk Agent. Lotus Domino Server database mode
where transaction log files are
application system (ZDB specific term) overwritten only after they have been
A system the application or database backed up.
runs on. The application or database
data is located on source volumes. ASR Set
See also backup system and source A collection of files stored on several
volume. diskettes, required for proper
reconfiguration of the replacement disk

G-1
Glossary

(disk partitioning and logical volume program via an open interface, which
configuration) and automatic recovery enables them to communicate with Data
of the original system configuration and Protector software. For backup and
user data that was backed up during the restore, SAP R/3 programs issue orders
full client backup. for the Data Protector backint interface.
These files are stored as an ASR archive
file on the Cell Manager (in backup API
<Data_Protector_home>\Config\Serve The Oracle interface between the Oracle
r\dr\asr on a Windows Cell Manager or backup/restore utility and the backup/
in /etc/opt/omni/server/dr/asr/ on a restore media management layer. The
UNIX Cell Manager) as well as on the interface defines a set of routines to
backup medium. The ASR archive file is allow the reading and writing of data to
extracted to three diskettes for 32-bit the backup media, the creation,
Windows systems or four diskettes for searching and removing the backup
64-bit Windows systems after a disaster files.
occurs. You need these diskettes to
perform ASR. backup chain
See restore chain.
autochanger
See library backup device
A device configured for use with Data
autoloader Protector, which can write data to and
See library read data from storage media. This can
be, for example, a standalone DDS/DAT
Automatic Storage Management drive or a library.
(Oracle specific term)
Automatic Storage Management is an backup generation
Oracle 10g integrated filesystem and One backup generation includes one full
volume manager that manages Oracle backup and all incremental backups
database files. It eliminates complexity until the next full backup.
associated with managing data and disk
and provides striping and mirroring backup ID
capabilities to optimize performance. An identifier of an integration object
that equals the session ID of the backup
BACKINT (SAP R/3 specific term) of this object. The backup ID is
SAP R/3 backup programs can call the preserved when an object is copied,
Data Protector backint interface exported, or imported.

G-2
Glossary

backup object specified in a backup specification or an

A backup unit that contains all items interactive session. All clients
backed up from one disk volume configured in one backup specification
(logical disk or mount point). The are backed up together in one backup
backed up items can be any number of session using the same backup type (full
files, directories, or the entire disk or or incremental). The result of a backup
mount point. Additionally, a backup session is a set of media, which was
object can be a database entity or a disk written to, also called the backup or
image (rawdisk). media set.
See also incremental backup and full
A backup object is defined by: backup.

• Client name: hostname of the Data backup set

Protector client where the backup A complete set of integration objects
object resides. associated with a backup.

• Mount point: the access point in a backup set (Oracle specific term)
directory structure (drive on A logical grouping of backed up files
Windows and mount point on that are created using the RMAN
UNIX) on the client where the backup command. A backup set is a
backup object is located. complete set of files associated with a
backup. The files can be multiplexed to
• Description: uniquely defines increase performance. A backup set
backup objects with identical client contains either datafiles or archived
name and mount point. logs, but not both together.

• Type: backup object type (for backup specification

example filesystem or Oracle). A list of objects to be backed up,
together with a set of devices or drives
backup owner to be used, backup options for all
Each backup object in the IDB has an objects in the specification, days and
owner. The default owner of a backup is time that you want backups to be
the user who starts the backup session. performed. The objects are entire disks/
volumes or parts of them such as files,
backup session directories, or even the Windows
A process that creates a copy of data on
storage media. The activities are

G-3
Glossary

Registry for example. File selection lists instant copies of EMC Symmetrix
such as include-lists and exclude-lists standard devices.
can be specified. See also BCV.

backup system (ZDB specific term) BC (HP StorageWorks Disk Array XP

A system connected to target volumes of specific term)
one or multiple application systems. The The Business Copy XP allows to
backup system is typically connected to maintain internal copies of HP
a ZDB disk arraybackup device to StorageWorks Disk Array XP LDEVs
perform the backup of the data in a for purposes such as data backup or data
replica. duplication. The copies (secondary
See also application system, target volumes or S-VOLs) can be separated
volume, and replica. from the primary volumes (P-VOLs)
and connected to a different system for
backup types various purposes, such as backup and
See incremental backup, differential development. For backup purposes, P-
backup, transaction backup, full VOLs should be connected to the
backup and delta backup. application system, and one of the S-
VOL mirror sets to the backup system.
backup view See also HP StorageWorks Disk
Data Protector provides different views Array XP LDEV, CA, Main Control
for backup specifications: By Type - Unit, application system, and backup
according to the type of data available system.
for backups/templates. Default view. By
Group - according to the group to which BC EVA (HP StorageWorks EVA
backup specifications/templates belong. specific term)
By Name - according to the name of Business Copy EVA is a local
backup specifications/templates. By replication software solution enabling
Manager - if you are running MoM, you you to create point-in-time copies
can also set the Backup view according (replicas) of the source volumes using
to the Cell Manager to which backup the snapshot and clone capabilities of
specifications/templates belong. the EVA firmware.
See also replica, source volume,
BC (EMC Symmetrix specific term) snapshot, and CA+BC EVA.
Business Continuance are processes that
allow customers to access and manage

G-4
Glossary

BC Process (EMC Symmetrix specific The BCV devices are used as splittable
term) mirrors of the primary EMC Symmetrix
A protected storage environment SLDs that need to be protected.
solution that has defined specially See also BC and BC Process.
configured EMC Symmetrix devices as
mirrors or Business Continuance Boolean operators
Volumes to protect data on EMC The Boolean operators for the full text
Symmetrix standard devices. search functionality of the online Help
See also BCV. system are AND, OR, NOT, and NEAR.
Used when searching, they enable you
BC VA (HP StorageWorks Virtual Array to define your query precisely by
specific term) creating a relationship between search
Business Copy VA allows you to terms. If no operator is specified in a
maintain internal copies of HP multi-word search, AND is used by
StorageWorks Virtual Array LUNs for default. For example, the query
data backup or data duplication within consistency checkmanual disaster
the same virtual array. The copies (child recovery is equivalent to
or Business Copy LUNs) can be used consistencymanual AND checkdisaster
for various purposes, such as backup, AND recovery.
data analysis or development. When
used for backup purposes, the original boot volume/disk/partition
(parent) LUNs are connected to the A volume/disk/partition with files
application system and the Business required for the initial step of the boot
Copy (child) LUNs are connected to the process. Microsoft terminology defines
backup system. the boot volume/disk/partition as a
See also HP StorageWorks Virtual volume/disk/partition containing the
Array LUN, application system, and operating system files.
backup system.
BRARCHIVE (SAP R/3 specific term)
BCV (EMC Symmetrix specific term) An SAP R/3 backup tool that allows you
Business Continuance Volumes, or BCV to archive redo log files. BRARCHIVE
devices, are dedicated SLDs that are also saves all the logs and profiles of the
pre-configured in the ICDA on which archiving process.
the business continuation operation See also SAPDBA, BRBACKUP and
runs. BCV devices are assigned separate BRRESTORE.
SCSI addresses, differing from the
addresses used by the SLDs they mirror.

G-5
Glossary

BRBACKUP (SAP R/3 specific term) CA (HP StorageWorks Disk Array XP

An SAP R/3 backup tool that allows an specific term)
online or offline backup of the control Continuous Access XP allows you to
file, of individual data files, or of all create and maintain remote copies of HP
tablespaces and, if necessary, of the StorageWorks Disk Array XP LDEVs
online redo log files. for purposes such as data duplication,
See also SAPDBA, BRARCHIVE and backup, and disaster recovery. CA
BRRESTORE. operations involve the main (primary)
disk arrays and the remote (secondary)
BRRESTORE (SAP R/3 specific term) disk arrays. The main disk arrays
An SAP R/3 tool that can be used to contain the CA primary volumes (P-
restore files of the following type: VOLs), which contain the original data
and are connected to the application
• Database data files, control files, and system. The remote disk arrays contain
online redo log files saved with the CA secondary volumes (S-VOLs)
BRBACKUP connected to the backup system.
See also BC (HP StorageWorks Disk
• Redo log files archived with Array XP specific term), Main Control
BRARCHIVE Unit and HP StorageWorks Disk
Array XP LDEV.
• Non-database files saved with
BRBACKUP CA+BC EVA (HP StorageWorks EVA
specific term)
You can specify files, tablespaces, The combination of Continuous Access
complete backups, log sequence (CA) EVA and Business Copy (BC)
numbers of redo log files, or the session EVA enables you to create and maintain
ID of the backup. copies (replicas) of the source volumes
See also SAPDBA, BRBACKUP and on a remote EVA, and then use these
BRARCHIVE. copies as the source for local replication
on this remote array.
BSM See also BC EVA, replica, and source
The Data Protector Backup Session volume.
Manager controls the backup session.
This process always runs on the Cell CAP (StorageTek specific term)
Manager system. Cartridge Access Port is a port built into
the door panel of a library. The purpose
is to enter or eject media.

G-6
Glossary

catalog protection Cell Manager

Defines how long information about The main system in the cell where the
backed up data (such as file names and essential Data Protector software is
file versions) is kept in the IDB. installed and from which all backup and
See also data protection. restore activities are managed. The GUI
used for management tasks can be
CDB located on a different system. Each cell
The Catalog Database is a part of the has one Cell Manager system.
IDB that contains information about
backups, object copies, restores, media centralized licensing
management sessions, and backed up Data Protector allows you to configure
data. Depending on the selected logging centralized licensing for the whole
level, it also contains file names and file enterprise environment consisting of
versions. This part of the database is several cells. All Data Protector licenses
always local to the cell. are installed and kept on the Enterprise
See also MMDB. Cell Manager system. You can then
allocate licenses to specific cells to suit
CDF file (UNIX specific term) your needs.
A Context Dependent File is a file See also MoM.
consisting of several files grouped under
the same pathname. The system Centralized Media Management
ordinarily selects one of the files using Database (CMMDB)
the context of the process. This See CMMDB.
mechanism allows machine dependent
executables, system data, and device channel (Oracle specific term)
files to work correctly from all hosts in a An Oracle Recovery Manager resource
cluster while using the same pathname. allocation. Every allocated channel
starts a new Oracle process, which
cell performs backup, restore, and recovery
A set of systems that are under the actions. The type of channel allocated
control of a Cell Manager. The cell determines the type of media used:
typically represents the systems on a site
or an organizational entity, which are • type 'disk'
connected to the same LAN. Central
control is available to administer the • type ‘sbt_tape’
backup and restore policies and tasks.

G-7
Glossary

If the specified channel is of type client or client system

‘sbt_tape’ and Oracle is integrated with Any system configured with any Data
Data Protector, the server process will Protector functionality and configured
attempt to read backups from or write in a cell.
data files to Data Protector.
cluster-aware application
circular logging (Microsoft Exchange It is an application that supports the
Server and Lotus Domino Server cluster Application Programming
specific term) Interface. Each cluster-aware
Circular logging is a Microsoft application declares its own critical
Exchange Server database and Lotus resources (disk volumes (on Microsoft
Domino Server database mode, in which Cluster Server), volume groups (on MC/
the transaction log file contents are ServiceGuard), application services, IP
periodically overwritten after the names and addresses ...).
corresponding data is committed to the
database. Circular logging reduces disk CMD Script for Informix Server
storage space requirements. (Informix Server specific term)
A Windows CMD script that is created
client backup in INFORMIXDIR when an Informix
A backup of all writers and filesystems Server database is configured. The
mounted on a client. Filesystems CMD script is a set of system
mounted on the client after the backup commands that export environment
specification was created are not variables for Informix Server.
automatically detected.
CMMDB
client backup with disk discovery The Data Protector Centralized Media
A backup of all filesystems mounted on Management Database (CMMDB) is the
a client. When the backup starts, Data result of merging MMDBs from several
Protector discovers the disks on the cells in the MoM environment. It allows
clients. Client backup with disk you to share high-end devices and media
discovery simplifies backup across multiple cells in a MoM
configuration and improves backup environment. One cell can control the
coverage of systems that often mount or robotics, serving the devices that are
dismount disks. connected to systems in other cells.
The CMMDB must reside on the MoM
Manager. A reliable network connection
between the MoM cell and the other

G-8
Glossary

Data Protector cells is highly concurrency

recommended See Disk Agent concurrency.
See also MoM.
control file (Oracle and SAP R/3
COM+ Registration Database specific term)
(Windows specific term) An Oracle data file that contains entries
The COM+ Registration Database and specifying the physical structure of the
the Windows Registry store COM+ database. It provides database
application attributes, class attributes, consistency information used for
and computer-level attributes. This recovery.
guarantees consistency among these
attributes and provides common copy set (HP StorageWorks EVA
operation on top of these attributes. specific term)
A pair that consists of the source
command-line interface volumes on a local EVA and their
A set of DOS and UNIX like commands replica on a remote EVA.
that you can use in shell scripts to See also source volume, replica, and
perform Data Protector configuration, CA+BC EVA.
backup, and restore, and management
tasks. CRS
The Cell Request Server process
Command View (CV) EVA (HP (service) runs on the Data Protector Cell
StorageWorks EVA specific term) Manager. It starts and controls the
The user interface that enables you to backup and restore sessions. The service
configure, manage, and monitor your is started as soon as Data Protector is
HP StorageWorks EVA storage system. installed on the Cell Manager.
It is used to perform various storage CRS runs under the account root on
management tasks, for example, UNIX systems, and under any Windows
creating virtual disk families, managing account. By default, it runs under the
storage system hardware, and creating account of the user, specified at
snapclones and snapshots of virtual installation time.
disks. The Command View EVA
software runs on the HP OpenView CSM
Storage Management Appliance, and is The Data Protector Copy and
accessed by a Web browser. Consolidation Session Manager process
See also HP StorageWorks EVA SMI–
S Agent.

G-9
Glossary

controls the object copy and object which restricts unauthorized access to
consolidation sessions and runs on the Data Protector and to backed up data.
Cell Manager system. Data Protector administrators create this
account specifying a user logon name,
data file (Oracle and SAP R/3 specific the systems from which the user can log
term) on, and a Data Protector user group
A physical file created by Oracle that membership. This is checked whenever
contains data structures such as tables the user starts the Data Protector user
and indexes. A data file can only belong interface or performs specific tasks.
to one Oracle database.
data stream
data protection Sequence of data transferred over the
Defines how long the backed up data on communication channel.
media remains protected, that is, Data
Protector will not overwrite it. When the database library
protection expires, Data Protector will A Data Protector set of routines that
be able to reuse the media in one of the enables data transfer between Data
next backup sessions. Protector and a server of an online
See also catalog protection. database integration, for example,
Oracle Server.
Data Protector Event Log
A central repository of all Data database parallelism
Protector related notifications. By More than one database is backed up at
default, all notifications are sent to the a time if the number of available devices
Event Log. The events are logged in the allows you to perform backups in
<Data_Protector_home>\log\server\Ob parallel.
2EventLog.txt file on the Cell
ManagerThe Event Log is accessible Data Replication (DR) group (HP
only to Data Protector users in the StorageWorks EVA specific term)
Admin group and to Data Protector A logical grouping of EVA virtual disks.
users who are granted the Reporting and It can contain up to eight copy sets
notifications user rights. You can view provided they have common
or delete all events in the Event Log. characteristics and share a common CA
EVA log.
Data Protector user account See also copy set.
You can use Data Protector only if you
have a Data Protector user account,

G-10
Glossary

database server delta backup

A computer with a large database stored A delta backup is a backup containing
on it, such as the SAP R/3 or Microsoft all the changes made to the database
SQL database. A server has a database from the last backup of any type.
that can be accessed by clients. See also backup types

Dbobject (Informix Server specific device

term) A physical unit which contains either
An Informix Server physical database just a drive or a more complex unit such
object. It can be a blobspace, dbspace, as a library.
or logical log file.
device chain
DC directory A device chain consists of several
The Detail Catalog (DC) directory standalone devices configured for
consists of DC binary files, which store sequential use. When a medium in one
information about file versions. It device gets full, the backup
represents the DCBF part of the IDB, automatically continues on a medium in
which occupies approximately 80% of the next device in the device chain.
the IDB. The default DC directory is
called the dcbf directory and is located device group (EMC Symmetrix specific
in the <Data_Protector_home>\db40 term)
directory on a Windows Cell Manager A logical unit representing several EMC
and in the /var/opt/omni/server/db40 Symmetrix devices. A device cannot
directory on a UNIX Cell Manager. You belong to more than a single device
can create more DC directories and group. All devices in a device group
locate them as appropriate to you. Up to must be on the same EMC Symmetrix
10 DC directories are supported per cell. unit. You can use a device group to
The default maximum size of a DC identify and work with a subset of the
directory is 4 GB. available EMC Symmetrix devices.

DCBF device streaming

The Detail Catalog Binary Files (DCBF) A device is streaming if it can feed
part of the IDB stores information about enough data to the medium to keep it
file versions and attributes. It occupies moving forward continuously.
approximately 80% of the IDB. One DC Otherwise, the tape has to be stopped,
binary file is created for each Data the device waits for more data, reverses
Protector medium used for backup. the tape a little and resumes to write to

G-11
Glossary

the tape, and so on. In other words, if the direct backup

data rate written to the tape is less or A SAN-based backup solution in which
equal the data rate which can be data movement directly from disk to
delivered to the device by the computer tape (or to other secondary storage) is
system, then the device is streaming. facilitated by the SCSI Extended Copy
Streaming significantly improves the (Xcopy) command. Direct backup
performance of the device and use of lessens the backup I/O load on systems
space. in a SAN environment. The data
movement is facilitated directly from
DHCP server disk to tape (or to other secondary
A system running the Dynamic Host storage) by the SCSI Extended Copy
Configuration Protocol (DHCP) (XCopy) command. The command is
providing dynamic IP address provided by any element of the
assignment and network configuration infrastructure including bridges,
for DHCP clients. switches, tape libraries, and disk
subsystems.
differential backup See also XCopy engine.
An incremental backup that backs up
changes made since the last full backup. directory junction (Windows specific
To perform this type of backup, specify term)
the Incr1 backup type. Directory junctions use the reparse point
See incremental backup. concept of Windows. An NTFS 5
directory junction allows you to redirect
differential backup (MS SQL specific a directory/file request to another
term) location.
A database backup that records only the
data changes made to the database after disaster recovery
the last full database backup. A process to restore a client’s main
See also backup types. system disk to a state close to the time
when a (full) backup was performed.
differential database backup
A differential database backup records Disk Agent
only those data changes made to the A component needed on a client to back
database after the last full database it up and restore it. The Disk Agent
backup. controls reading from and writing to a
disk. During a backup session, the Disk
Agent reads data from a disk and sends

G-12
Glossary

it to the Media Agent, which then moves images. A disk image (rawdisk) backup
it to the device. During a restore session does not track the files and directory
the Disk Agent receives data from the structure stored on the disk, but stores a
Media Agent and writes it to the disk. disk image structure on byte level. You
can perform a disk image backup of
Disk Agent concurrency either specific disk sections or a
The number of Disk Agents that are complete disk.
allowed to send data to one Media
Agent concurrently. disk quota
A concept to manage disk space
disk discovery consumption for all or a subset of users
The detection of disks during client on a computer system. This concept is
backup with disk discovery. During this used by several operating system
backup, Data Protector discovers platforms.
(detects) the disks that are present on the
client — even though they might not disk staging
have been present on the system when The process of backing up data in
the backup was configured — and backs several phases to improve the
them up. This is particularly useful in performance of backups and restores,
dynamic environments, where reduce costs of storing the backed up
configurations change rapidly. After the data, and increase the data availability
disks are expanded, each inherits all and accessibility for restore. The backup
options from its master client object. stages consist of backing up data to one
Even if pre- and post-exec commands media type first (for example disk) and
are specified once, they are started many later copying it to a different media type
times, once per each object. (for example tape).

disk group (Veritas Volume Manager distributed file media format

specific term) A media format, available with the file
The basic unit of data storage in VxVM library, which supports a space efficient
system. A disk group can consist of one type of synthetic backup called virtual
or more physical volumes. There can be full backup. Using this format is a
more than one disk group on the system. prerequisite for virtual full backup.
See also virtual full backup.
disk image (rawdisk) backup
A high-speed backup where Data
Protector backs up files as bitmap

G-13
Glossary

Distributed File System (DFS) DR OS

A service that connects file shares into a A disaster recovery operating system is
single namespace. The file shares can an operating system environment in
reside on the same or on different which disaster recovery runs. It provides
computers. DFS provides client access Data Protector a basic runtime
to the resources in a location-transparent environment (disk, network, tape, and
manner. filesystem access). The OS has to be
installed and configured before the Data
DMZ Protector disaster recovery can be
The Demilitarized Zone (DMZ) is a performed. DR OS not only hosts the
network inserted as a "neutral zone" Data Protector disaster recovery process
between a company's private network but is also a part of the restored system
(intranet) and the outside public network because it replaces its own configuration
(Internet). It prevents outside users from data with the original configuration data.
getting direct access to company servers
in the intranet. drive
A physical unit that receives data from a
DNS server computer system and can write it onto a
In the DNS client-server model, this is magnetic medium (typically a tape
the server containing information about drive). It can also read the data from the
a portion of the DNS database that medium and send it to the computer
makes computer names available to system.
client resolvers querying for name
resolution across the Internet. drive index
A number that identifies the mechanical
domain controller position of a drive inside a library
A server in a network that is responsible device. This number is used by the
for user security and verifying robotic control to access a drive.
passwords within a group of other
servers. dynamic client
See client backup with disk discovery.
DR image
Data required for temporary disaster EMC Symmetrix Agent (SYMA)
recovery operating system (DR OS)
(EMC Symmetrix specific term)
installation and configuration.
See Symmetrix Agent (SYMA)

G-14
Glossary

emergency boot file (Informix Server services and the logging on and off of
specific term) users. Data Protector can back up
The Informix Server configuration file Windows Event Logs as part of the
ixbar.<server_id> that resides in the Windows configuration backup.
directory <INFORMIXDIR>/etc (on
Windows) or <INFORMIXDIR>\etc (on exchanger
UNIX). <INFORMIXDIR> is the Also referred to as SCSI Exchanger.
Informix Server home directory and See also library.
<server_id> is the value of the
SERVERNUM configuration parameter. exporting media
Each line of the emergency boot file A process that removes all data about
corresponds to one backup object. backup sessions, such as systems,
objects, and file names, which reside on
enhanced incremental backup the media from the IDB. Information
Conventional incremental backup backs about the media and their relation to a
up files that have changed since a pool is also removed from the IDB. The
previous backup, but has certain data on the media remains unchanged.
limitations in detection of changes. See also importing media.
Unlike conventional incremental
backup, enhanced incremental backup Extensible Storage Engine (ESE)
reliably detects and backs up also
(Microsoft Exchange Server specific
renamed and moved files, as well as files
term)
with changes in attributes.
A database technology used as a storage
system for information exchange in
Enterprise Backup Environment
Microsoft Exchange Server.
Several cells can be grouped together
and managed from a central cell. The
failover
enterprise backup environment includes
Transferring of the most important
all clients located in several Data
cluster data, called group (on Windows)
Protector cells which are managed and
or package (on Unix) from one cluster
administered from a central cell using
node to another. A failover can occur
the Manager-of-Managers concept.
mostly because of software or hardware
See also MoM.
failures or maintenance on the primary
node.
Event Logs
Files in which Windows logs all events,
such as the starting or stopping of

G-15
Glossary

failover (HP StorageWorks EVA specific file depot

term) A file containing the data from a backup
An operation that reverses the roles of to a file library device.
source and destination in CA+BC EVA
configurations. file jukebox device
See also CA+BC EVA. A device residing on disk consisting of
multiple slots used to store file media.
FC bridge
See Fibre Channel bridge file library device
A device which resides on a disk
Fibre Channel emulating a library with several media,
An ANSI standard for high-speed hence containing multiple files, referred
computer interconnection. Using either to as file depots.
optical or copper cables, it allows the
high speed bidirectional transmission of File Replication Service (FRS)
large data files and can be deployed A Windows service that replicates the
between sites kilometers apart. domain controller store logon scripts
Fibre Channel connects nodes using and group policies. FRS also enables
three physical topologies: point-to- replication of Distributed File System
point, loop, and switched. (DFS) shares between systems and
allows any server to perform replication
Fibre Channel bridge activity.
A Fibre Channel bridge or multiplexer
provides the ability to migrate existing file version
parallel SCSI devices, like RAID arrays, The same file can be backed up multiple
solid state disks (SSD), and tape times in case of full backups and
libraries to a Fibre Channel incremental backups (if the file
environment. On one side of the bridge changed). If the log level ALL is
or multiplexer there is a Fibre Channel selected for backup, Data Protector
interface while on the other side there retains one entry in the IDB for the
are parallel SCSI ports. The bridge or filename itself and one for each version
multiplexer enables SCSI packets to be (date/time) of the file.
moved between the Fibre Channel and
parallel SCSI devices.

G-16
Glossary

filesystem Data Protector. Information about media

The organization of files on a hard disk. (media ID, description, and location) is
A filesystem is backed up so that the file saved in the IDB as well as on the
attributes and the file contents are stored respective media (media header). Data
on the backup media. Protector media with protected data are
not formatted until the protection
first level mirror (HP StorageWorks expires or the media are unprotected/
Disk Array XP specific term) recycled.
HP StorageWorks Disk Array XP allows
up to three mirror copies of a Primary free pool
Volume and each of these copies can An auxiliary source of media for use by
have additional two copies. The three media pools when they run out of media.
mirror copies are called first level The media pools must be configured to
mirrors. use free pools.
See also Primary Volume, and MU
numbers. full backup
A backup in which all selected objects
flash recovery area (Oracle specific are backed up, whether or not they have
term) been recently modified.
Flash recovery area is an Oracle 10g See also backup types.
managed directory, filesystem, or
Automatic Storage Management disk full database backup
group that serves as a centralized A backup of all data in a database, not
storage area for files related to backup only the data that has been changed after
and recovery (recovery files). the last (full or incremental) backup of
See also recovery files. the database. A full database backup
does not depend on any other backup.
fnames.dat
The fnames.dat files of the IDB contain full mailbox backup
information on the names of the backed A full mailbox backup is a backup of the
up files. Typically, these files occupy entire mailbox content.
about 20% of the IDB, if filenames are
stored. full ZDB
A ZDB to tape or ZDB to disk+tape
formatting session in which all selected objects are
A process that erases any data contained backed upstreamed to tape, even if there
on a medium and prepares it for use with

G-17
Glossary

are no changes from the previous heartbeat

backup. A cluster data set with a time stamp
See also incremental ZDB. carrying information about the
operational status of a particular cluster
global options file node. This data set or packet is
A file that allows you to customize Data distributed among all cluster nodes.
Protector. It explains the global options,
which cover various aspects of Data Hierarchical Storage Management
Protector, typically time-outs and limits, (HSM)
and affect the entire Data Protector cell. A method for optimizing the use of
The file is located in the /etc/opt/omni/ expensive hard disk storage by
server/options directory on HP-UX and migrating less frequently used data to
Solaris systems and in the less expensive optical platters. When
<Data_Protector_home>\Config\Serve needed, the data is migrated back to
r\Options directory on Windows hard disk storage. This balances the
systems. need for fast retrieval from hard disk
with the lower cost of optical platters.
group (Microsoft Cluster Server
specific term) Holidays file
A collection of resources (for example A file that contains information about
disk volumes, application services, IP holidays. You can set different holidays
names and addresses) that are needed to by editing the Holidays file: /etc/opt/
run a specific cluster-aware applications. omni/server/Holidays on the UNIX Cell
Manager and
GUI <Data_Protector_home>\Config\Serve
A cross-platform (HP-UX, Solaris, and r\holidays on the Windows Cell
Windows) graphical user interface, Manager.
provided by Data Protector for easy
access to all configuration, host backup
administration, and operation tasks. See client backup with disk discovery.

hard recovery (Microsoft Exchange hosting system

Server specific term) A working Data Protector client used for
A Microsoft Exchange Server database Disk Delivery Disaster Recovery with a
recovery that is performed after a restore Data Protector Disk Agent installed.
by the database engine, using
transaction log files.

G-18
Glossary

HP ITO HP StorageWorks EVA SMI-S Agent

See OVO. A Data Protector software module that
executes all tasks required for the HP
HP OpC StorageWorks Enterprise Virtual Array
See OVO. integration. With the EVA SMI-S Agent,
the control over the array is established
HP OpenView SMART Plug-In (SPI) through HP StorageWorks SMI-S EVA
A fully integrated, out-of-the-box provider, which directs communication
solution which "plugs into" HP between incoming requests and CV
OpenView Operations, extending the EVA.
managed domain. Through the Data See also Command View (CV) EVA,
Protector integration, which is and HP StorageWorks SMI-S EVA
implemented as an HP OpenView provider.
SMART Plug-In, a user can have an
arbitrary number of Data Protector Cell HP StorageWorks SMI-S EVA
Managers monitored as an extension to provider
HP OpenView Operations (OVO). An interface used for controlling HP
StorageWorks Enterprise Virtual Array.
HP OVO SMI-S EVA provider runs as a separate
See OVO. service on the HP OpenView Storage
Management Appliance system and acts
HP StorageWorks Disk Array XP as a gateway between incoming requests
LDEV and Command View EVA. With the
A logical partition of a physical disk Data Protector HP StorageWorks EVA
within an HP StorageWorks Disk Array integration, SMI-S EVA provider
XP. LDEVs are entities that can be accepts standardized requests from the
replicated in the Continuous Access XP EVA SMI-S Agent, communicates with
(CA) and Business Copy XP (BC) Command View EVA for information or
configurations, or can be used as method invocation, and returns
standalone entities. standardized responses.
See also BC (HP StorageWorks Disk See also HP StorageWorks EVA SMI-
Array XP specific term), CA (HP S Agent and Command View (CV)
StorageWorks Disk Array XP specific EVA.
term), and replica.

G-19
Glossary

HP StorageWorks Virtual Array IDB recovery. It is recommended to

LUN relocate the file, together with IDB
A logical partition of a physical disk transaction logs, to a separate physical
within an HP StorageWorks Virtual disk from other IDB directories, and,
Array. LUNs are entities that can be additionally, to make an additional copy
replicated in the HP StorageWorks of the file.
Business Copy VA configuration, or can
be used as standalone entities. importing media
See also BC VA and replica. A process that re-reads all data about
backup sessions which are on the
HP VPO medium back into the IDB. This then
See OVO. allows for fast and convenient access to
the data on the media.
ICDA (EMC Symmetrix specific term) See also exporting media.
EMC's Symmetrix Integrated Cached
Disk Arrays (ICDA) is a disk array incremental backup
device that combines a set of physical A backup that selects only files that have
disks, a number of FWD SCSI channels, changed since a previous backup.
an internal cache memory, and control Several levels of incremental backup are
and diagnostic software commonly available, which enables detailed control
referred to as the microcode. of restore chain length.
See also backup types.
IDB
The Data Protector Internal Database is incremental backup (Microsoft
an embedded database located on the Exchange Server specific term)
Cell Manager that keeps information A backup of the Microsoft Exchange
regarding which data is backed up, on Server data that has changed since the
which media it is backed up, how last full or incremental backup. With the
backup and restore sessions are run, and incremental backup, only the transaction
so onwhich devices and libraries are log files are backed up.
configured. See also backup types.

IDB recovery file incremental mailbox backup

An IDB file (obrindex.dat) with An incremental mailbox backup backs
information about IDB backups, media, up all the changes made to the mailbox
and devices used for the backup. This after the last backup of any type.
information can significantly simplify

G-20
Glossary

incremental1 mailbox backup incremental restore reassigns a target

An incremental1 mailbox backup backs (R2) device as the next available mirror
up all the changes made to the mailbox of the source (R1) device in the pair.
after the last full backup. However, the source (R1) devices are
updated with only the data that was
incremental (re)-establish (EMC written to the target (R2) device during
Symmetrix specific term) the time of the original pair split, and the
A BCV or SRDF control operation. In data that was written to the source (R1)
BCV control operations, an incremental device during the split is overwritten
establish causes the BCV device to be with data from the target (R2) mirror.
synchronized incrementally and to
function as an EMC Symmetrix incremental ZDB
mirrored medium. The EMC Symmetrix A filesystem ZDB to tape or ZDB to
devices must have been previously disk+tape session in which only changes
paired. from the last protected full or
In SRDF control operations, an incremental backup are streamed to
incremental establish causes the target tape.
(R2) device to be synchronized See also full ZDB.
incrementally and to function as an
EMC Symmetrix mirrored medium. The Inet
EMC Symmetrix devices must have A process that runs on each UNIX
been previously paired. system or service that runs on each
Windows system in the Data Protector
incremental restore (EMC Symmetrix cell. It is responsible for communication
specific term) between systems in the cell and for
A BCV or SRDF control operation. starting other processes needed for
In BCV control operations, an backup and restore. The Inet service is
incremental restore reassigns a BCV started as soon as Data Protector is
device as the next available mirror of the installed on a system. The Inet process
standard device in the pair. However, the is started by the inetd daemon.
standard devices are updated with only
the data that was written to the BCV Information Store (Microsoft
device during the time of the original Exchange Server specific term)
pair split, and the data that was written The Microsoft Exchange Server service
to the standard device during the split is that is responsible for storage
overwritten with data from the BCV management. Information Store in
mirror. In SRDF control operations, an Microsoft Exchange Server manages

G-21
Glossary

two kinds of stores: mailbox stores and steps, such as the application of
public folder stores. A mailbox store transaction log files, may be required for
consists of mailboxes that belong to full recovery.
individual users. A public folder store See also replica, zero downtime
contains public folders and messages backup (ZDB), ZDB to disk, and ZDB
that are shared among several users. to disk+tape.
See also Key Management Service and
Site Replication Service. integrated security (MS SQL specific
term)
Informix Server (Informix Server Integrated security allows the Microsoft
specific term) SQL Server to use Windows
Refers to Informix Dynamic Server. authentication mechanisms to validate
Microsoft SQL Server logins for all
initializing connections. Using integrated security
See formatting. means that users have one password for
both Windows and Microsoft SQL
Installation Server Server. Integrated security should be
A computer system that holds a used in environments where all clients
repository of the Data Protector support trusted connections.
software packages for a specific Connections validated by Windows
architecture. The Installation Server is Server and accepted by Microsoft SQL
used for remote installation of Data Server are referred to as trusted
Protector clients. In mixed environments connections. Only trusted connections
at least two Installation Servers are are allowed.
needed: one for UNIX systems and one
for Windows systems. integration object
A backup object of a Data Protector
instant recovery (ZDB specific term) integration, such as Oracle or SAP DB.
A process in which a replica, produced
by a ZDB-to-disk or a ZDB-to- Internet Information Server (IIS)
disk+tape sessions, is used to restore the
(Windows specific term)
contents of the source volumes to their
Microsoft Internet Information Server is
states at the time at which the replica
a network file and application server that
was created, avoiding the need to
supports multiple protocols. Primarily,
perform a restore from tape. Depending
IIS transmits information in Hypertext
on the application/database concerned,
this may be all that is required, or other

G-22
Glossary

Markup Language (HTML) pages by keychain

using the Hypertext Transport Protocol A tool that eliminates the supply of a
(HTTP). passphrase manually when decrypting
the private key. It needs to be installed
IP address and configured on the Installation Server
Internet Protocol address is a numeric if you perform remote installation using
address of a system used to uniquely secure shell.
identify the system on the network. The
IP address consists of four groups of LBO (EMC Symmetrix specific term)
numbers separated by periods (full A Logical Backup Object (LBO) is an
stops). object of data storage/retrieval in the
EMC Symmetrix environment. It is
ISQL (Sybase specific term) stored/retrieved by EMC Symmetrix as
A Sybase utility used to perform system one entity and can only be restored as a
administration tasks on Sybase SQL whole.
Server.
library
ITO Also called autochanger, jukebox,
See OVO. autoloader, or exchanger. A library
contains media in repository slots. Each
jukebox slot holds one medium (for example,
See library. DDS/DAT). Media are moved between
slots and drives by a robotic mechanism,
jukebox device allowing random access to media. The
A device consisting of multiple slots library can contain multiple drives.
used to store either optical or file media.
When being used to store file media, the lights-out operation or unattended
jukebox device is known as the “file operation
jukebox device”. A backup or restore operation that takes
place outside of normal business hours
Key Management Service (Microsoft without an operator. This implies that no
Exchange Server specific term) operator personnel is present to work
The Microsoft Exchange Server service with the backup application or service
that provides encryption functionality mount requests, for example.
for enhanced security.
See also Information Store and Site
Replication Service.

G-23
Glossary

LISTENER.ORA (Oracle specific lock name

term) You can configure the same physical
An Oracle configuration file that device several times with different
describes one or more Transparent characteristics, by using different device
Network Substrate (TNS) listeners on a names.
server.
The lock name is a user specified string
load balancing that is used for locking all such device
By default, Data Protector automatically configurations to prevent collision if
balances the usage of devices selected several such devices (device names) are
for backup, so that they are used evenly. used concurrently. Use an identical lock
Load balancing optimizes the device name for all device definitions which
usage by balancing the number of use the same physical device.
objects written to each device. Since
load balancing is done automatically log_full shell script (Informix Server
during backup time, you do not need to UNIX specific term)
manage how the data is actually backed A script provided by ON-Bar that you
up. You just specify the devices to be can use to start backing up logical log
used. If you do not want to use load files when Informix Server issues a
balancing, you can select which device logfull event alarm. The Informix Server
will be used for each object in the ALARMPROGRAM configuration
backup specification. Data Protector parameter defaults to the
will access the devices in the specified <INFORMIXDIR>/etc/log_full.sh,
order. where <INFORMIXDIR> is the
Informix Server home directory. If you
local and remote recovery do not want logical logs to be backed up
Remote recovery is performed if all continuously, set the
Media Agent hosts specified in the SRD ALARMPROGRAM configuration
file are accessible. If any of them fails, parameter to <INFORMIXDIR>/etc/
the disaster recovery process fails over no_log.sh.
to the local mode. This means that the
target system is searched for locally logging level
attached devices. If only one device is The logging level determines the
found, it is automatically used. amount of details on files and directories
Otherwise, Data Protector prompts you written to the IDB during backup, object
to select the device, which will be used copying, or object consolidation. You
for restore. can always restore your data, regardless

G-24
Glossary

of the logging level used during backup. have to be entered to connect to an

Data Protector provides four logging Oracle Target Database. This user
levels: Log All, Log Directories, Log must have Oracle SYSDBA or
Files, and No Log. The different logging SYSOPER rights.
level settings influence the IDB growth,
backup speed, and the convenience of • <password> must be the same as the
browsing data for restore. password specified in the Oracle
password file (orapwd), which is
logical-log files used for authentication of users
This applies to online database backup. performing database administration.
Logical-log files are files in which
modified data is first stored before being • <service> is the name used to
flushed to disk. In the event of a failure, identify an SQL*Net server process
these logical-log files are used to roll for the target database.
forward all transactions that have been
committed as well as roll back any login information to the Recovery
transactions that have not been Catalog Database (Oracle specific
committed. term)
The format of the login information to
login ID (MS SQL Server specific term) the Recovery (Oracle) Catalog Database
The name a user uses to log on to is <user_name>/
Microsoft SQL Server. A login ID is <password>@<service>, where the
valid if Microsoft SQL Server has an description of the user name, password,
entry for that user in the system table and service name is the same as in the
syslogin. Oracle SQL*Net V2 login information
to the Oracle target database. In this
login information to the Oracle Target case, <service> is the name of the
Database (Oracle and SAP R/3 specific service to the Recovery Catalog
term) Database, not the Oracle target database.
The format of the login information is
<user_name>/<password>@<service>, Note that the Oracle user specified here
where: must be the owner of the Oracle
Recovery Catalog.
• <user_name> is the name by which
a user is known to Oracle Server and Lotus C API (Lotus Domino Server
to other users. Every user name is specific term)
associated with a password and both An interface for the exchange of backup

G-25
Glossary

and recovery information between Lotus contains the primary volumes for the
Domino Server and a backup solution, Continuous Access configuration and
like Data Protector. acts as a master device.
See also BC (HP StorageWorks Disk
LVM Array XP specific term), CA (HP
A Logical Volume Manager is a StorageWorks Disk Array XP specific
subsystem for structuring and mapping term), and HP StorageWorks Disk
physical disk space to logical volumes Array XP LDEV.
on UNIX systems. An LVM system
consists of several volume groups, Manager-of-Managers (MoM)
where each volume group has several See Enterprise Cell Manager.
volumes.
Media Agent
Magic Packet A process that controls reading from and
See Wake ONLAN. writing to a device, which reads from or
writes to a medium (typically a tape).
mailbox (Microsoft Exchange Server During a backup session, a Media Agent
specific term) receives data from the Disk Agent and
The location to which e-mail is sends it to the device for writing it to the
delivered, which is set up by the medium. During a restore session, a
administrator for each user. If a set of Media Agent locates data on the backup
personal folders is designated as the e- medium and sends it to the Disk Agent.
mail delivery location, e-mail is routed The Disk Agent then writes the data to
from the mailbox to this location. the disk. A Media Agent also manages
the robotics control of a library.
Mailbox Store (Microsoft Exchange
Server specific term) MAPI (Microsoft Exchange specific
A part of the Information Store that term)
maintains information about user The MAPI (Messaging Application
mailboxes. A mailbox store consists of a Programming Interface) is the
binary rich-text .edb file and a streaming programming interface that lets
native internet content .stm file. applications and messaging clients
interact with messaging and information
Main Control Unit (MCU) (HP systems.
StorageWorks Disk Array XP specific
term)
An HP StorageWorks XP disk array that

G-26
Glossary

media allocation policy media management session

Determines in which sequence media A session performing some action on a
are used for backup. The Strict medium, such as initializing, scanning
allocation policy directs Data Protector the content, verifying data on a medium,
to prompt for a specific medium. The or copying a medium.
Loose policy directs Data Protector to
prompt for any suitable medium. The media pool
Formatted First policy directs Data A set of media of the same type (such as
Protector to give preference to unknown DDS) used and tracked as a group.
media, even if unprotected media are Media are formatted and assigned to a
available in the library. media pool.

media condition media set

The quality of a medium as derived from The result of a backup session is data
the media condition factors. Heavy backed up on a group of media called
usage and age result in an increased media set. Depending on the media
number of read and write errors with usage policy, several sessions can share
tape media. Media need to be replaced the same media.
when they are marked as POOR.
media type
media condition factors The physical type of media, such as
The user-assigned age threshold and DDS or DLT.
overwrite threshold used to determine
the state of a medium. media usage policy
The media usage policy controls how
media ID new backups are added to the already
A unique identifier assigned to a used media. It can be Appendable, Non-
medium by Data Protector. Appendable, or Appendable for
incrementals only.
media label
A user-defined identifier used to merging
describe a medium. This defines one mode to resolve file
conflicts during restore. If the file to be
media location restored already exists at the destination,
A user-defined physical location of a the one with the more recent
medium, such as "building 4" or "off-
site storage".

G-27
Glossary

modification date is kept. Files not aware application regardless of its

present on the disk are always restored. specific features. This service
See also overwrite. collaborates with the backup
application, writers, shadow copy
Microsoft Exchange Server providers, and the operating system
A “client-server” messaging and a kernel to implement the management of
workgroup system that offers a volume shadow copies and shadow copy
transparent connection to many different sets.
communication systems. It provides See also shadow copy, shadow copy
users with an electronic mail system, provider, writer.
individual and group scheduling, online
forms, and workflow automation tools. mirror (EMC Symmetrix and HP
It provides a developer with a platform StorageWorks Disk Array XP specific
on which to build custom information- term)
sharing and messaging-service See target volume.
applications.
mirror rotation (HP StorageWorks
Microsoft Management Console Disk Array XP specific term)
(MMC) (Windows specific term) See replica set rotation.
An administration model for Windows-
based environments. It provides a MMD
simple, consistent, and integrated The Media Management Daemon
administration user interface allowing process (service) runs on the Data
management of many applications Protector Cell Manager and controls
through the same GUI, provided that the media management and device
applications adhere to the MMC model. operations. The process is started when
Data Protector is installed on the Cell
Microsoft SQL Server Manager.
A database management system
designed to meet the requirements of MMDB
distributed "client-server" computing. The Media Management Database
(MMDB) is a part of the IDB that
Microsoft Volume Shadow Copy contains information about media,
service (VSS) media pools, devices, libraries, library
A software service that provides a drives, and slots configured in the cell,
unified communication interface to as well as the Data Protector media used
coordinate backup and restore of a VSS- for backup. In an enterprise backup

G-28
Glossary

environment, this part of the database number (0, 1 or 2), used to indicate a
can be common to all cells. first level mirror.
See also CMMDB, CDB. See also first level mirror.

MoM multi-drive server

Several cells can be grouped together A license that allows you to run an
and managed from a central cell. The unlimited number of Media Agents on a
management system of the central cell is single system. This license, which is
the Manager-of-Managers (MoM). The bound to the IP address of the Cell
cells are called MoM clients. The MoM Manager, is no longer available.
enables you to configure and manage
multiple cells from a central point. obdrindex.dat
See IDB recovery file.
mount request
A screen prompt that tells you to insert a OBDR capable device
specific medium into a device. Once you A device that can emulate a CD-ROM
respond to the mount request by drive loaded with a bootable disk and
providing the required medium and can thus be used as a backup or boot
confirm the mount request, the session device for disaster recovery purposes.
continues.
object
mount point See backup object
The access point in a directory structure
for a disk or logical volume, for example object consolidation
/opt or d:. On UNIX, the mount points The process of merging a restore chain
are displayed using the bdf or df of a backup object, consisting of a full
command. backup and at least one incremental
backup, into a new, consolidated version
MSM of this object. The process is a part of
The Data Protector Media Session the synthetic backup procedure. The
Manager, which runs on the Cell result is a synthetic full backup of the
Manager and controls media sessions, specified backup object.
such as copying media.
object consolidation session
MU number (HP StorageWorks Disk A process that merges a restore chain of
Array XP specific term) a backup object, consisting of a full
A Mirror Unit number is an integer

G-29
Glossary

backup and at least one incremental object mirroring

backup, into a new, consolidated version The process of writing the same data to
of this object. several media sets during a backup
session. Data Protector enables you to
object copy mirror all or some backup objects to one
A copy of a specific object version that or more media sets.
is created during an object copy session
or a backup session with object offline backup
mirroring. A backup during which an application
database cannot be used by the
object copy session application.
A process that creates an additional
copy of the backed up data on a different • For simple backup methods (non
media set. During an object copy ZDB), the database is generally put
session, the selected backed up objects into a quiescent state that allows use
are copied from the source to the target by the backup system, but not the
media. application, for the whole backup
period (~minutes/hours). For
object copying instance, for backup to tape, until
The process of copying selected object streaming of data to the tape is
versions to a specific media set. You can finished.
select object versions from one or
several backup sessions to be copied. • For ZDB methods, the database is
also put into the quiescent state, but
Object ID (Windows specific term) for the period of the data replication
The object IDs (OIDs) enable access to process only (~seconds). Normal
NTFS 5 files no matter where in the database operation can then be
system the files reside. Data Protector resumed for the rest of the backup
treats the OIDs as alternate streams of process.
the files.
See also zero downtime backup (ZDB)
object mirror and online backup.
A copy of a backup object created using
object mirroring. Object mirrors are offline recovery
often referred to as object copies. Offline recovery is performed if the Cell
Manager is not accessible, for example,
due to network problems. Only

G-30
Glossary

standalone and SCSI library devices can directory <INFORMIXDIR>\etc (on

be used for offline recovery. Recovery Windows) or <INFORMIXDIR>/etc/
of the Cell Manager is always offline. (on UNIX).

offline redo log online backup

See archived redo log A backup performed while a database
application remains available for use.
On-Bar (Informix Server specific term) The database is placed into a special
A backup and restore system for backup mode of operation for the time
Informix Server. ON-Bar enables you to period that the backup application
create a copy of your Informix Server requires access to the original data
data and later restore the data. The ON- objects. During this period, the database
Bar backup and restore system involves is fully operational, but there may be a
the following components: small performance impact and log files
may grow very quickly.
• the onbar command
• For simple backup methods (non
• Data Protector as the backup ZDB), backup mode is required for
solution the whole backup period (~minutes/
hours). For instance, for backup to
• the XBSA interface tape, until streaming of data to tape
is finished.
• ON-Bar catalog tables, which are
used to back up dbobjects and track • For ZDB methods, backup mode is
instances of dbobjects through required for the short period of the
multiple backups. data replication process only
(~seconds). Normal database
ONCONFIG (Informix Server specific operation can then be resumed for
term) the rest of the backup process.
An environment variable that specifies
the name of the active ONCONFIG In some cases, transaction logs may also
configuration file. If the ONCONFIG have to be backed up to allow a
environment variable is not present, consistent database to be restored.
Informix Server uses the configuration See also zero downtime backup (ZDB)
values from the onconfig file in the and offline backup.

G-31
Glossary

online redo log (Oracle specific term) processing can be moved from the
Redo logs that have not been archived, current primary database to a standby
but are either available to the instance database and back quickly.
for recording database activity or are
filled and waiting to be archived or Oracle instance (Oracle specific term)
reused. Each installation of an Oracle database
See also archived redo log. on one or more systems. One computer
system can have several instances of a
OpC database running.
See OVO.
ORACLE_SID (Oracle specific term)
OpenSSH A unique name for an Oracle Server
A set of network connectivity tools used instance. To switch among Oracle
to access remote machines securely, by Servers, specify the desired
using a variety of authentication and <ORACLE_SID>. The
encryption methods. It needs to be <ORACLE_SID> is included in the
installed and configured on the CONNECT DATA parts of the connect
Installation Server and the client if you descriptor in a TNSNAMES.ORA file
perform remote installation using secure and in the definition of the TNS listener
shell. in the LISTENER.ORA file.

Oracle Data Guard (Oracle specific original system

term) The system configuration backed up by
Oracle Data Guard is Oracle’s primary Data Protector before a computer
disaster recovery solution. Oracle Data disaster hits the system.
Guard is able to maintain up to nine
standby databases, each of which is a overwrite
real-time copy of the production An option that defines one mode to
(primary) database, to protect against resolve file conflicts during restore. All
corruptions, data failures, human errors, files are restored from a backup even if
and disasters. If a failure occurs on the they are older than existing files.
production (primary) database, then a See also merging.
failover to one of the standby databases
which becomes the new primary OVO
database is possible. In addition, HP OpenView Operations for Unix
planned downtime for maintenance can provides powerful capabilities for
be reduced because the production operations management of a large

G-32
Glossary

number of systems and applications on the system during Enhanced Automated

in a network. Data Protector provides an Disaster Recovery (EADR). It is created
integration into this management during full backup and is saved on
product. This integration is implemented backup medium and on Cell Manager
as a SMART Plug-In for OVO into
management servers on HP-UX and <Data_Protector_home>\Config\Se
Solaris. Earlier versions of OVO were ver\dr\p1s directory on a Windows Cell
called IT/Operation, Operations Center Manager or in /etc/opt/omni/server/dr/
and Vantage Point Operations. p1s directory on a UNIX Cell Manager
See also merging. with the filename recovery.p1s.

ownership package (MC/ServiceGuard and Veritas

The ownership of a backup determines Cluster specific term)
who can restore from the backup. The A collection of resources (for example
user who starts an interactive backup is volume groups, application services, IP
the session owner. If a user starts an names and addresses) that are needed to
existing backup specification without run a specific cluster-aware application.
modifying it, the session is not
considered interactive. In that case, if pair status (HP StorageWorks Disk
the backup owner has been defined in Array XP specific term)
the backup specification, they remain A mirrored pair of disks can have
the session owner. Otherwise, the various status values depending on the
session owner becomes the user who action performed on it. The three most
started the backup in question. For the important status values are:
scheduled backups, by default, the
session owner is for the UNIX Cell • COPY - The mirrored pair is
Manager: root.sys@<Cell Manager>, currently resynchronizing. Data is
and for the Windows Cell Manager, the transferred from one disk to the
user that was specified during the other. The disks do not contain the
installation of the Cell Manager. It is same data.
possible to modify the ownership, so
that the specific user becomes the • PAIR - The mirrored pair is
session owner. completely synchronized and both
disks (the primary volume and the
P1S file mirrored volume) contain identical
P1S file contains information on how to data.
format and partition all disks installed in

G-33
Glossary

• SUSPENDED - The link between an object or after the entire session

the mirrored disks is suspended. completes. Post-exec commands are not
That means that both disks are supplied by Data Protector. You need to
accessed and updated independently. create your own. They can be written as
However, the mirror relationship is executables or batch files on Windows
still maintained and the pair can be and as shell scripts on UNIX.
resynchronized without transferring See also pre-exec.
the complete disk.
pre- and post-exec commands
parallel restore Pre- and post-exec commands are used
Restoring backed up data to multiple to perform additional action before and
disks at the same time (that is, in after a backup or restore session. They
parallel) by running multiple Disk are not supplied by Data Protector. You
Agents, that receive data from one need to create your own commands.
Media Agent. For the parallel restore to They can be written as executables or
work, select data that is located on batch files on Windows and as shell
different disks or logical volumes and scripts on UNIX.
during backup, the data from the
different objects must have been sent to prealloc list
the same device using a concurrency of A subset of media in a media pool that
2 or more. During a parallel restore, the specifies the order in which media are
data for multiple objects selected for used for backup.
restore is read from media at the same
time, thereby improving performance. pre-exec
A backup option that executes a
parallelism command or script before the backup of
The concept of reading multiple data an object or before the entire session is
streams from an online database. started. Pre-exec commands are not
supplied by Data Protector. You need to
physical device create your own. They can be written as
A physical unit that contains either a executables or batch files on Windows
drive or a more complex unit such as a and as shell scripts on UNIX.
library. See also post-exec.

post-exec Primary Volume (P-VOL) (HP

A backup option that executes a StorageWorks Disk Array XP specific
command or script after the backup of term)

G-34
Glossary

Standard HP StorageWorks Disk Array RAID Manager Library (HP

XP LDEVs that act as a primary volume StorageWorks Disk Array XP specific
for the CA and BC configurations. The term)
P-VOL is located in the MCU. The RAID Manager Library is used
See also Secondary Volume (S-VOL). internally by Data Protector on Solaris
systems to allow access to HP
protection StorageWorks Disk Array XP
See data protection and also catalog configuration, status, and performance
protection. data and to key HP StorageWorks Disk
Array XP features through the use of
public folder store (Microsoft function calls translated into a sequence
Exchange Server specific term) of low level SCSI commands.
The part of the Information Store that
maintains information in public folders. RAID Manager XP (HP StorageWorks
A public folder store consists of a binary Disk Array XP specific term)
rich-text .edb file and a streaming native The RAID Manager XP application
internet content .stm file. provides an extensive list of commands
to report and control the status of the CA
public/private backed up data and BC applications. The commands
When configuring a backup, you can communicate through a RAID Manager
select whether the backed up data will instance with the HP StorageWorks
be: Disk Array XP Disk Control Unit. This
instance translates the commands into a
• public, that is visible (and accessible sequence of low level SCSI commands.
for restore) to all Data Protector
users rawdisk backup
See disk image backup.
• private, that is, visible (and
accessible for restore) only to the RCU (HP StorageWorks specific term)
owner of the backup and The Remote Control Unit acts as a slave
administrators of an MCU in a CA configuration. In
bidirectional configurations, the RCU
RAID can act as an MCU.
Redundant Array of Inexpensive Disks.
RDBMS
Relational Database Management
System.

G-35
Glossary

RDF1/RDF2 (EMC Symmetrix specific Recovery Catalog Database (Oracle

term) specific term)
A type of SRDF device group. Only An Oracle database that contains a
RDF devices can be assigned to an RDF recovery catalog schema. You should
group. An RDF1 group type contains not store the recovery catalog in your
source (R1) devices and an RDF2 group target database.
type contains target (R2) devices.
recovery files (Oracle specific term)
RDS Recovery files are Oracle 10g specific
The Raima Database Server process files that reside in the flash recovery
(service) runs on the Data Protector Cell area: the current control file, online redo
Manager and manages the IDB. The logs, archived redo logs, flashback logs,
process is started when Data Protector is control file autobackups, datafile copies,
installed on the Cell Manager. and backup pieces.
See also flash recovery area.
Recovery Catalog (Oracle specific
term) RecoveryInfo
A set of Oracle tables and views that are When backing up Windows
used by Recovery Manager to store configuration files, Data Protector
information about Oracle databases. collects the information about the
This information is used by Recovery current system configuration
Manager to manage the backup, restore, (information on disk layout, volume,
and recovery of Oracle databases. The and network configuration). This
recovery catalog contains information information is needed for disaster
about: recovery.

• The physical schema of the Oracle Recovery Manager (RMAN) (Oracle

target database specific term)
An Oracle command-line interface that
• Data file and archived log backup directs an Oracle Server process to back
sets up, restore, or recover the database it is
connected to. RMAN uses either the
• Data file copies recovery catalog or the control file to
store information about backups. This
• Archived Redo Logs information can be used later in restore
sessions.
• Stored scripts

G-36
Glossary

recycle reparse point (Windows specific term)

A process that removes the data A system-controlled attribute that can be
protection from all backed up data on a associated with any directory or file.
medium, allowing Data Protector to The value of a reparse attribute can have
overwrite it during one of the next user-controlled data. The format of the
backups. Data that belongs to the same data is understood by the application
session(s) but resides on other media is that stored the data and a filesystem
also unprotected. Recycling does not filter that was installed to interpret the
actually alter the data on the medium. data and process such files. Whenever
the filesystem encounters a file with a
redo log (Oracle specific term) reparse point, it attempts to find the
Every Oracle database has a set of two filesystem filter associated with the data
or more redo log files. The set of redo format.
log files for the database is known as the
database's redo log. Oracle uses the redo replica (ZDB specific term)
log to record all changes made to data. An image, at a particular point in time,
of the data in source volumes that
Remote Control Unit (HP contain user-specified backup objects.
StorageWorks Disk Array XP specific Depending on the hardware/software
term) with which it is created, the image may
The Remote Control Unit (RCU) acts as be an independent exact duplicate
a slave of an MCU in a CA (clone) of the storage blocks at the
configuration. In bidirectional physical disk level (for example, a split
configurations, the RCU can act as an mirror), or a virtual copy (for example, a
MCU. snapshot). From a host’s perspective, on
a basic UNIX or Windows system, the
Removable Storage Management complete physical disk containing a
Database (Windows specific term) backup object is replicated. However, if
A Windows service used for managing a volume manager is used on UNIX, the
removable media (such as tapes and whole volume/disk group containing a
disks) and storage devices (libraries). backup object is replicated.
Removable Storage allows applications See also snapshot, snapshot creation,
to access and share the same media split mirror, and split mirror creation.
resources.

G-37
Glossary

replica set (ZDB specific term) RSM (Windows specific term)

A group of replicas, all created using the Removable Storage Manager (RSM)
same backup specification. includes a media management service
See also replica and replica set that facilitates communication among
rotation. applications, robotic changers, and
media libraries. It enables multiple
replica set rotation (ZDB specific term) applications to share local robotic media
The use of a replica set for regular libraries and tape or disk drives and to
backup production: Each time the same manage removable media.
backup specification requiring the use of
a replica set is run, a new replica is SAPDBA (SAP R/3 specific term)
created and added to the set, until the An SAP R/3 user interface that
maximum number for the set is reached. integrates the BRBACKUP,
After that, the oldest replica in the set is BRARCHIVE, and BRRESTORE tools.
replaced, maintaining the maximum
number of replicas in the set. scan
See also replica and replica set. A function that identifies the media in a
device. This synchronizes the MMDB
restore chain with the media that are actually present
All backups that are necessary for a at the selected locations (for example,
restore of a backup object to a certain slots in a library).
point in time. A restore chain consists of
a full backup of the object and any scanning
number of related incremental backups. A function which identifies the media in
a device. This synchronizes the MMDB
restore session with the media that are actually present
A process that copies data from backup at the selected locations (for example,
media to a client. slots in a library). It is useful to perform
a scan and check the actual media in the
RMAN (Oracle specific term) device if someone has manually
See Recovery Manager. manipulated media without using Data
Protector to eject or enter, for example.
RSM
The Data Protector Restore Session
Manager controls the restore session.
This process always runs on the Cell
Manager system.

G-38
Glossary

Scheduler it is used for specifying options for the

A function that controls when and how omnimnt, omnistat and omniabort CLI
often automatic backups occur. By commands.
setting up a schedule, you automate the
start of backups. shadow copy (MS VSS specific term)
A volume that represents a duplicate of
Secondary Volume (S-VOL) (HP the original volume at a certain point in
StorageWorks Disk Array XP specific time. The data is then backed up from
term) the shadow copy and not from the
Secondary Volumes, or S-VOLs, are XP original volume. The original volume
LDEVs that act as a secondary CA or continues to changes as the backup
BC mirror of another LDEV (a P-VOL). process continues, but the shadow copy
In the case of CA, S-VOLs can be used of the volume remains constant.
as failover devices in a MetroCluster See also Microsoft Volume Shadow
configuration. The S-VOLs are assigned Copy service.
separate SCSI addresses, different from
the addresses used by the P-VOLs. shadow copy provider (MS VSS
See also Primary Volume (P-VOL). specific term)
An entity that performs the work on
session creating and representing the volume
See backup session, media shadow copies. Providers own the
management session, and restore shadow copy data and expose the
session. shadow copies. Providers can be
software (for example, system
session ID providers) or hardware (local disks, disk
An identifier of a backup, restore, object arrays).
copy, object consolidation, or media See also shadow copy.
management session, consisting of the
date when the session ran and a unique shadow copy set (MS VSS specific
number. term)
A collection of shadow copies created at
session key the same point in time.
This environment variable for the Pre- See also shadow copy.
and Post-exec script is a Data Protector
unique identification of any session, shared disks
including preview sessions. The session A Windows disk on another system that
key is not recorded in the database, and has been made available to other users

G-39
Glossary

on the network. Systems with shared consolidation, and media management

disks can be backed up without a Data sessions. One binary file is created per
Protector Disk Agent installed. session. The files are grouped by year
and month.
SIBF
The Serverless Integrations Binary Files snapshot (HP StorageWorks VA and HP
(SIBF) is a part of the IDB that stores StorageWorks EVA specific term)
raw NDMP meta data. This data is A form of replica produced using
necessary to perform restore of NDMP snapshot creation techniques. A range of
objects. snapshot types is available, with
different characteristics, depending on
Site Replication Service (Microsoft the arrays/techniques used. Such
Exchange Server specific term) replicas are dynamic and may be either
The Microsoft Exchange Server 2000/ virtual copies, still reliant upon the
2003 service that permits compatibility contents of the source volumes, or
with Microsoft Exchange Server 5.5 by independent exact duplicates (clones),
emulating the Exchange Server 5.5 depending on the snapshot type and the
directory service. time since creation.
See also Information Store and Key See also replica and snapshot creation.
Management Service.
snapshot backup (HP StorageWorks
slot VA and HP StorageWorks EVA specific
A mechanical position in a library. Each term)
slot can hold a medium, such as a DLT See ZDB to tape, ZDB to disk, and
tape. Data Protector references each slot ZDB to disk+tape.
with a number. To read a medium, a
robotic mechanism moves the medium snapshot creation (HP StorageWorks
from a slot into the drive. VA and HP StorageWorks EVA specific
term)
SMB A replica creation technique, in which
See split mirror backup. copies of source volumes are created
using storage virtualization techniques.
SMBF The replicas are considered to be created
The Session Messages Binary Files at one particular point in time, without
(SMBF) part of the IDB stores session pre-configuration, and are immediately
messages generated during backup, available for use. However background
restore, object copy, object

G-40
Glossary

copying processes normally continue split mirror backup (EMC Symmetrix

after creation. specific term)
See also snapshot. See ZDB to tape.

source (R1) device (EMC Symmetrix split mirror backup (HP StorageWorks
specific term) Disk Array XP specific term)
An EMC Symmetrix device that See ZDB to tape, ZDB to disk, and
participates in SRDF operations with a ZDB to disk+tape.
target (R2) device. All writes to this
device are mirrored to a target (R2) split mirror creation (EMC Symmetrix
device in a remote EMC Symmetrix and HP StorageWorks Disk Array XP
unit. An R1 device must be assigned to specific term)
an RDF1 group type. A replica creation technique, in which a
See also target (R2) device. pre-configured set of target volumes (a
mirror) is kept synchronized with a set
source volume (ZDB specific term) of source volumes until the time at
A storage volume containing data to be which a replica of the contents of the
replicated. source volumes is required. Then, the
synchronization is stopped (the mirror is
sparse file A file that contains data with split) and a split mirror replica of the
portions of empty blocks. Examples are: source volumes at the time of the split
-A matrix in which some or much of the remains in the target volumes.
data contains zeros -files from image See also split mirror.
applications -high-speed databases If
sparse file processing is not enabled split mirror restore (EMC Symmetrix
during restore, it might be impossible to and HP StorageWorks Disk Array XP
restore this file. specific term)
A process in which data backed up in a
split mirror (EMC Symmetrix and HP ZDB-to-tape or a ZDB-to-disk+tape
StorageWorks Disk Array XP specific session is restored from tape media to a
term) split mirror replica, which is then
A replica created using split mirror synchronized to the source volumes.
techniques. Such a replica provides an Individual backup objects or complete
independent, exact duplicate, or clone, sessions can be restored using this
of the contents of the source volumes. method.
See also replica and split mirror See also ZDB to tape, ZDB to
creation. disk+tape, and replica.

G-41
Glossary

sqlhosts file (Informix Server specific StorageWorks Disk Array XP storing

term) system using the RAID Manager XP
An Informix Server connectivity utility (HP-UX and Windows systems)
information file (on UNIX) or registry or RAID Manager Library (Solaris
(on Windows) that contains the names systems).
of each of the database servers and any
aliases to which the clients on a host sst.conf file
computer can connect. The file /usr/kernel/drv/sst.conf is
required on each Data Protector Sun
SRD file Solaris client to which a multi-drive
The Data Protector System Recovery library device is connected. It must
Data (SRD) file contains system contain an entry for the SCSI address of
information required for installing and the robotic mechanism of each library
configuring the operating system in case device connected to the client.
of a disaster. The SRD file is an ASCII
file, generated when a st.conf file
CONFIGURATION backup is The file /kernel/drv/st.conf is required
performed on a Windows client and on each Data Protector Solaris client
stored on the Cell Manager. with a backup device connected. It must
contain device information and a SCSI
SRDF (EMC Symmetrix specific term) address for each backup drive connected
The EMC Symmetrix Remote Data to that client. A single SCSI entry is
Facility is a business continuation required for a single-drive device and
process that enables effective, real-time multiple SCSI entries are required for a
data replication of SLDs between multi-drive library device.
dislocated processing environments.
These environments could be situated stackers
within the same root computer Devices with multiple slots for media
environment or separated by long storage usually with only one drive. A
distances. stacker selects media from the stack
sequentially. In contrast, a library can
SSE Agent (HP StorageWorks Disk randomly select media from its
Array XP specific term) repository.
A Data Protector software module that
executes all tasks required for a split standalone file device
mirror backup integration. It A file device is a file in a specified
communicates with the HP directory to which you back up data.

G-42
Glossary

standard security (MS SQL specific systems, file systems are built on this
term) storage. Typically, these can be created
Standard security uses the login or exist within a storage system such as
validation process of the Microsoft SQL a disk array.
Server for all connections. Standard
security is useful in network switchover
environments with a variety of clients, See failover
some of which may not support trusted
connections. It also provides backward Sybase Backup Server API (Sybase
compatibility for older versions of the specific term)
Microsoft SQL Server. An industry-standard interface
See also integrated security. developed for the exchange of backup
and recovery information between a
Storage Group Sybase SQL Server and a backup
(Microsoft Exchange Server specific solution like Data Protector.
term)
A collection of databases (stores) that Sybase SQL Server (Sybase specific
share a common set of transaction log term)
files. Exchange manages each storage The server in the Sybase “client-server”
group with a separate server process. architecture. Sybase SQL Server
manages multiple databases and
StorageTek ACS library multiple users, keeps track of the actual
(StorageTek specific term) location of data on disks, maintains
Automated Cartridge System is a library mapping of logical data description to
system (also known as Silo) consisting physical data storage, and maintains
of one Library Management Unit data and procedure caches in memory.
(LMU) and one to 24 Library Storage
Modules (LSM) connected to the unit. Symmetrix Agent (SYMA) (EMC
Symmetrix specific term)
storage volume (ZDB specific term) The Data Protector software module that
A storage volume represents an object prepares the EMC Symmetrix
that may be presented to an operating environment for backup and restore
system or some other entity (for operations.
example, a virtualization mechanism)
upon which volume management synthetic backup
systems, file systems, or other objects A backup solution that produces a
may exist. The volume management synthetic full backup, an equivalent to a

G-43
Glossary

conventional full backup in terms of system disk

data, without putting stress on the A system disk is a disk containing
production servers or the network. A operating system files. Microsoft
synthetic full backup is created from a terminology defines the system disk as a
previous full backup and any number of disk containing the files required for
incremental backups. initial step of boot process.

synthetic full backup system partition

The result of an object consolidation A system partition is a partition
operation, where a restore chain of a containing operating system files.
backup objects is merged into a new, Microsoft terminology defines a system
synthetic full version of this object. A partition as a partition containing the
synthetic full backup is equivalent to a files required for initial step of boot
conventional full backup in terms of process.
restore speed.
System State (Windows specific term)
System Backup to Tape (Oracle The System State data comprises the
specific term) Registry, COM+ Class Registration
An Oracle interface that handles the database, system startup files, and the
actions required to load, label, and Certificate Services database (if the
unload correct backup devices when server is a certificate server). If the
Oracle issues a backup or restore server is a domain controller, Active
request. Directory directory services and the
Sysvol directory are also contained in
system databases (Sybase specific the System State data. If the server is
term) running the Cluster service, the System
The four system databases on a newly State data also includes resource registry
installed Sybase SQL Server are the: checkpoints and the quorum resource
recovery log, which contains the most
• master database (master) recent cluster database information.

• temporary database (tempdb) system volume/disk/partition

A volume/disk/partition containing
• system procedure database operating system files. Microsoft
(sybsystemprocs) terminology defines the system volume/

• model database (model).

G-44
Glossary

disk/partition as the volume/disk/ operations. An R2 device must be

partition containing files required for the assigned to an RDF2 group type.
initial step of the boot process. See also source (R1) device

SysVol (Windows specific term) target system (Disaster Recovery

A shared directory that stores the server specific term)
copy of the domain’s public files, which A system after a computer disaster has
are replicated among all domain occurred. The target system is typically
controllers in the domain. in a non-bootable state and the goal of
disaster recovery is to restore this
tablespace system to the original system
A part of a database structure. Each configuration. The difference between a
database is logically divided into one or crashed system and a target system is
more tablespaces. Each tablespace has that a target system has all faulty
data files or raw volumes exclusively hardware replaced.
associated with it.
target volume (ZDB specific term)
tapeless backup (ZDB specific term) A storage volume to which data is
See ZDB to disk. replicated.

target database (Oracle specific term) Terminal Services (Windows specific

In RMAN, the target database is the term)
database that you are backing up or Windows Terminal Services provide a
restoring. multi-session environment that allows
clients to access a virtual Windows
target (R2) device (EMC Symmetrix desktop session and Windows-based
specific term) programs running on the server.
An EMC Symmetrix device that
participates in SRDF operations with a thread (MS SQL Server specific term)
source (R1) device. It resides in the An executable entity that belongs to
remote EMC Symmetrix unit. It is only one process. It comprises a
paired with a source (R1) device in the program counter, a user-mode stack, a
local EMC Symmetrix unit and receives kernel-mode stack, and a set of register
all write data from its mirrored pair. values. Several threads can run at a time
This device is not accessed by user within one process.
applications during normal I/O

G-45
Glossary

TimeFinder (EMC Symmetrix specific transaction backup (Sybase and SQL

term) specific term)
A business continuation process that A backup of the transaction log
creates an instant copy of single or providing a record of changes made
multiple Symmetrix Logical Devices since the last full or transaction backup.
(SLDs). The instant copy is created on
specially preconfigured SLDs called transaction log backup
BCVs and is accessible via a separate Transaction log backups generally use
device address to the system(s). fewer resources than database backups
so they can be created more frequently
TLU than database backups. By applying
Tape Library Unit. transaction log backups, you can recover
the database to a specific point in time.
TNSNAMES.ORA (Oracle and SAP R/
3 specific term) transaction log files
A network configuration file that Files that record transactions of the
contains connect descriptors mapped to database modifications, and provide
service names. The file may be fault tolerance in case of a database
maintained centrally or locally, for use disaster.
by all or individual clients.
transaction logs (Data Protector
transaction specific term)
A mechanism for ensuring that a set of Keeps track of IDB changes. The
actions is treated as a single unit of archiving of transaction logs should be
work. Databases use transactions to enabled to prevent you from losing the
keep track of database changes. transaction log files that are created after
the last IDB backup and are necessary
transaction backup for IDB recovery.
Transaction backups generally use fewer
resources than database backups, so they transaction log table (Sybase specific
can be created more frequently than term)
database backups. By applying A system table in which all changes to
transaction backups, you can recover the the database are automatically recorded.
database to a specific point in time prior
to when a problem occurred. transportable snapshot (MS VSS
specific term)
A shadow copy that is created on the

G-46
Glossary

application system and can be presented Protector backs up user disk quotas on
to the backup system which performs the whole system and for all configured
the backup. users at a time.
See also Microsoft Volume Shadow
Copy service (VSS). user group
Each Data Protector user is member of a
TSANDS.CFG file (Novell NetWare User Group. Each User Group has a set
specific term) of user rights that are given to every user
A file that allows you to specify the in that User Group. The number of User
names of containers where you want Groups with their associated user rights
backups to begin. It is text file located in can be defined as desired. Data Protector
the SYS:SYSTEM\TSA directory on the provides three default user groups:
server where TSANDS.NLM is loaded. admin, operator, and user.

unattended operation user profile (Windows specific term)

See lights-out operation. Configuration information retained on a
user basis. This information includes
user account desktop settings, screen colors, network
You can use Data Protector only if you connections, and so on. When the user
have a Data Protector user account, logs on, the user profile is loaded and
which restricts unauthorized access to the Windows environment is set
Data Protector and to backed up data. accordingly.
Data Protector administrators create this
account specifying a user logon name, user rights
the systems from which the user can log User rights or access rights are the
on, and a Data Protector user group permissions needed to perform specific
membership. This is checked whenever Data Protector tasks. Configuring a
the user starts the Data Protector user backup, starting a backup session, or
interface or performs specific tasks. starting a restore session are typical user
rights. Users have the access rights of
user disk quotas the user group to which they belong.
NTFS quota-management support
enables an enhanced tracking vaulting media
mechanism and control over disk space The process of storing media to a safe
usage on shared storage volumes. Data and remote place. The media are
brought back to the data center when
they are needed for restore or are ready

G-47
Glossary

for reuse in subsequent backups. The snapshot functionality.

vaulting procedure depends on your See also source volume and target
company's backup strategy and policies volume.
for data protection/reliability.
virtual full backup
verify An efficient type of synthetic backup
A function that lets you check whether where data is consolidated using
the Data Protector data on a specified pointers instead of being copied. It is
medium is readable. Additionally, performed if all the backups (the full
consistency within each block can be backup, incremental backups, and the
checked if the backup was performed resulting virtual full backup) are written
with the cyclic redundancy check (CRC) to a single file library that uses
option ON. distributed file medium format.

Virtual Controller Software (VCS) virtual server

A virtual machine in a cluster
(HP StorageWorks EVA specific term)
environment defined in a domain by a
The firmware that manages all aspects
network IP name and address. Its
of storage system operation, including
address is cached by the cluster software
communication with Command View
and mapped to the cluster node that is
EVA through the HSV controllers.
currently running the virtual server
See also Command View (CV) EVA.
resources. This way all requests for a
particular virtual server are cached by a
Virtual Device Interface (MS SQL
specific cluster node.
Server specific term)
This is a SQL Server programming
volser (ADIC and STK specific term)
interface that allows fast backup and
A VOLume SERial number is a label on
restore of large databases.
the medium to identify the physical tape
used in very large libraries. A volser is a
virtual disk (HP StorageWorks EVA
naming convention specific to ADIC/
specific term)
GRAU and StorageTek devices.
A unit of storage allocated from an HP
StorageWorks Enterprise Virtual Array
volume group
storage pool. Virtual disks are the
A unit of data storage in an LVM
entities that are replicated using the HP
system. A volume group can consist of
StorageWorks Enterprise Virtual Array

G-48
Glossary

one or more physical volumes. There Wake ONLAN

can be more than one volume group on Remote power-up support for systems
the system. running in power-save mode from some
other system on the same LAN.
volume mountpoint (Windows specific
term) Web reporting
An empty directory on a volume that The Data Protector functionality that
can be used to mount another volume. allows you to view reports on backup
The volume mount point acts as a status and Data Protector configuration
gateway to the target volume. Provided using the Web interface.
that the volume is mounted, users and
applications can refer to the data on the wildcard character
mounted volume by the full (merged) A keyboard character that can be used to
filesystem path as if both volumes are represent one or many characters. The
one integral part. asterisk (*), for example, typically
represents one or more characters, and
Volume Shadow Copy service the question mark (?) typically
See Microsoft Volume Shadow Copy represents a single character. Wildcard
service. characters are often used in operating
systems as a means of specifying more
VPO than one file by name.
See OVO.
Windows CONFIGURATION
VSS backup
See Microsoft Volume Shadow Copy Data Protector allows you to back up
service. Windows CONFIGURATION,
including Windows Registry, user
VxFS profiles, Event Logs, and WINS and
Veritas Journal Filesystem. DHCP server data (if configured on a
system) in one step.
VxVM (Veritas Volume Manager)
A Veritas Volume Manager is a system Windows Registry
for managing disk space on Solaris A centralized database used by
platforms. A VxVM system consists of Windows to store configuration
an arbitrary group of one or more information for the operating system
physical volumes organized into logical and the installed applications.
disk groups.

G-49
Glossary

WINS server A system running XCopy. This releases the controlling

Windows Internet Name Service server of reading the data from the
software that resolves Windows storage device into memory and then
networking computer names to IP writing the information to the
addresses. Data Protector can back up destination device.
WINS server data as part of the See also direct backup.
Windows configuration.
ZDB
writer See zero downtime backup (ZDB).
(MS VSS specific term)
A process that initiates change of data ZDB database (ZDB specific term)
on the original volume. Writers are A part of the IDB, storing ZDB related
typically applications or system services information such as source volumes,
that write persistent information on a replicas and security information. The
volume. Writers also participate in the ZDB database is used for ZDB, and
shadow copy synchronization process instant recovery, and split mirror restore.
by assuring data consistency. See also zero downtime backup
(ZDB).
XBSA interface (Informix Server
specific term) ZDB to disk (ZDB specific term)
ON-Bar and Data Protector A form of zero downtime backup where
communicate with each other through the replica produced is kept on the disk
the X/Open Backup Services array as a backup of the source volumes
Application Programmer's Interface at a specific point in time. Multiple
(XBSA). replicas, produced using the same
backup specification at different times,
XCopy engine (direct backup specific can be kept in a replica set. A replica
term) from ZDB to disk can be restored using
A SCSI-3 copy command that allows the instant recovery process.
you to copy data from a storage device See also zero downtime backup
having a SCSI source address to a (ZDB), ZDB to tape, ZDB to
backup device having a SCSI disk+tape, instant recovery, and
destination address, thus enabling direct replica set rotation.
backup. The data flows from a source
device (either block or streaming, that ZDB to disk+tape (ZDB specific term)
is, disk or tape) to the destination device A form of zero downtime backup where
(either block or streaming) through the replica produced is kept on the disk

G-50
Glossary

array as a backup of the source volumes to be backed up is created first. All

at a specific point in time, in the same subsequent backup operations are
way as with ZDB to disk. However, data performed on the replicated data rather
in the replica is also streamed to a than the original data, while the
backup medium, as with ZDB to tape. If application system can be returned to
this backup method is used, data backed normal operation.
up in the same session can be restored See also ZDB to disk, ZDB to tape,
using the instant recovery process, the ZDB to disk+tape, and instant
standard Data Protector restore from recovery.
tape, or on split mirror arrays, split
mirror restore.
See also zero downtime backup
(ZDB), ZDB to disk, ZDB to tape,
instant recovery, replica, and replica
set rotation.

ZDB to tape (ZDB specific term)

A form of zero downtime backup where
data in the replica produced is streamed
to a backup medium, typically tape.
Instant recovery is not possible from
such a backup, so the replica need not be
retained on the disk array after backup
completion. The backed-up data can be
restored using standard Data Protector
restore from tape. On split mirror arrays,
split mirror restore can also be used.
See also zero downtime backup
(ZDB), ZDB to disk, instant recovery,
ZDB to disk+tape, and replica.

zero downtime backup (ZDB)

A backup approach in which data
replication techniques, provided by a
disk array, are used to minimize the
impact of backup operations on an
application system. A replica of the data

G-51
Glossary

G-52
 Index Index

A incremental backups, 80, 93

architecture Notes Storage Facility files, 93
DB2 integration, 47 Notes Template Facility files, 93
Informix integration, 3 previewing backups, 98
Lotus integration, 82 scheduling backups, 97
archived logs backups scheduling backups, example, 97
DB2 integration, 54 starting backups, 99
transaction log files, 93
B backup modes
DB2 integration, 54
backing up DB2, 54–62
Informix integration, 25
archived logs backups, 54
backup options
backup modes, 54 DB2 integration, 58
backup options, 58
Informix integration, 18
backup specification, modifying, 58
Lotus integration, 96
backup specifications, creating, 55
backup specifications, creating
backup templates, 55 DB2 integration, 55
backup types, 46 Informix integration, 14
database objects backups, 54 Lotus integration, 94
full backups, 54 backup specifications, modifying
incremental backups, 54, 61 DB2 integration, 58
incremental delta backups, 61 Informix integration, 18
previewing backups, 59 Lotus integration, 97
scheduling backups, 58 backup templates
scheduling backups, example, 58 DB2 integration, 55
starting backups, 60 backup types
backing up Informix, 13–27 DB2 integration, 46
backup modes, 25 Informix integration, 2, 13
backup options, 18 Lotus integration, 80
backup specification, modifying, 18 BOX files
backup specifications, creating, 14 Lotus integration, 93
backup types, 2, 13
continuous backups, 26 C
full backups, 2, 13
checking configuration
incremental backups, 2, 13 DB2 integration, 52
manual backups, 26 Informix integration, 10
onbar utility, 25 Lotus integration, 91
online mode, 25 complete database restore, Informix
previewing backups, 20 integration, 28
quiescent mode, 25 concepts
scheduling backups, 19 DB2 integration, 47
scheduling backups, example, 19 Informix integration, 3
starting backups, 22 Lotus integration, 82
backing up Lotus, 93–100 configuring DB2, 49–53
backup options, 96 checking configuration, 52
backup specification, modifying, 97 configuring Informix, 5–12
backup specifications, creating, 94 checking configuration, 10
backup types, 80 configuring Lotus, 84–92
BOX files, 93 checking configuration, 91
full backups, 80 , 93 enabling transaction logging, 84

I-1
Index

linking the C API library, 87 E

conventions, ix enabling modification tracking
creating backup specifications DB2 integration, 61
DB2 integration, 55 enabling transaction logging
Informix integration, 14 Lotus integration, 84
Lotus integration, 94 examples
DB2 integration, restore, 68, 70
D DB2 integration, scheduling backups, 58
DB2 backup, 54–62 Informix integration, restore using onbar,
archived logs backups, 54 36
backup modes, 54 Informix integration, scheduling backups,
backup options, 58 19
backup specification, modifying, 58 Informix integration, starting interactive
backup specifications, creating, 55 backups, 24
backup templates, 55 Lotus integration, creating soft links, 88
backup types, 46 Lotus integration, restore, 105
database objects backups, 54 Lotus integration, scheduling backups, 97
delta backups, 54
full backups, 54 F
incremental backups, 54, 61 full backups
incremental delta backups, 61 DB2 integration, 54
modification tracking, enabling, 61 Informix integration, 2, 13
previewing backups, 59 Lotus integration, 80, 93
scheduling backups, 58
scheduling backups, example, 58 I
starting backups, 60
incremental backups
DB2 configuration, 49–53 DB2 integration, 54, 61
checking configuration, 52
Informix integration, 2, 13
DB2 integration
architecture, 47 Lotus integration, 80, 93
backup, 54–62 incremental delta backups
concepts, 47 DB2 integration, 61
Informix backup, 13–27
configuration, 49–53
backup modes, 25
introduction, 46
backup options, 18
monitoring sessions, 74
backup specification, modifying, 18
restore, 63–73
backup specifications, creating, 14
troubleshooting, 75–78 backup types, 2, 13
DB2 restore, 63 –73
continuous backups, 26
examples, 68, 70
full backups, 2, 13
partitioned environment, 71
incremental backups, 2, 13
restore options, 65
manual backups, 26
to a new database, 68
to another DB2 instance, 68 onbar utility, 25
online mode, 25
using CLI, 67
previewing backups, 20
using GUI, 63
quiescent mode, 25
DB2 troubleshooting, 75–78
delta backups scheduling backups, 19
DB2 integration, 54 scheduling backups, example, 19
starting backups, 22

I-2
 Index

Informix configuration, 5–12 starting backups, 99

checking configuration, 10 transaction log files, 93
Informix integration Lotus configuration, 84–92
architecture, 3 checking configuration, 91
backup, 13–27 enabling transaction logging, 84
concepts, 3 linking the C API library, 87
configuration, 5–12 Lotus integration
introduction, 2 architecture, 82
monitoring sessions, 38 backup, 93–100
onbar utility, 3 concepts, 82
restore, 28–37 configuration, 84–92
troubleshooting, 39–44 introduction, 80
Informix restore, 28–37 monitoring sessions, 107
complete database restore, 28 restore, 101–105
finding information for restore, 29 troubleshooting, 108–116
restore options, 34 Lotus restore, 101–105
to another Informix Server, 36 examples, 105
using another device, 37 restore options, 105
using CLI, 35 using GUI, 102
using GUI, 31 Lotus troubleshooting, 108–116
using Informix commands, 35
using Informix commands, examples, 36 M
whole-system restore, 28 modification tracking, enabling
Informix troubleshooting, 39–44 DB2 integration, 61
interactive backups modifying backup specifications
DB2 integration, 60 DB2 integration, 58
Informix integration, 22 Informix integration, 18
Lotus integration, 99 Lotus integration, 97
introduction monitoring sessions
DB2 integration, 46 DB2 integration, 74
Informix integration, 2 Informix integration, 38
Lotus integration, 80 Lotus integration, 107

L N
linking the C API library Notes Storage Facility files
Lotus integration, 87 Lotus integration, 93
Lotus backup, 93–100 Notes Template Facility files
backup options, 96 Lotus integration, 93
backup specification, modifying, 97 NSF See Notes Storage Facility files
backup specifications, creating, 94 NTF See Notes Template Facility files
backup types, 80
BOX files, 93 O
full backups, 80 , 93
onbar utility
incremental backups, 80, 93 Informix integration, 3, 25
Notes Storage Facility files, 93 online backups
Notes Template Facility files, 93 DB2 integration, 46, 54
previewing backups, 98 Informix integration, 2, 25
scheduling backups, 97 Lotus integration, 80
scheduling backups, example, 97

I-3
Index

P DB2 integration, 60
previewing backups Informix integration, 22
DB2 integration, 59 Lotus integration, 99
Informix integration, 20
Lotus integration, 98 T
transaction log files
Q Lotus integration, 93
quiescent backups transaction logging, enabling
Informix integration, 25 Lotus integration, 84
troubleshooting DB2, 75–78
troubleshooting Informix, 39–44
R
troubleshooting Lotus, 108–116
restore methods typographical conventions, ix
Informix integration, 28
restore options W
DB2 integration, 65
Informix integration, 34 whole-system restore
Informix integration, 28
Lotus integration, 105
restoring DB2, 63–73
examples, 68, 70
partitioned environment, 71
restore options, 65
to a new database, 68
to another DB2 instance, 68
using CLI, 67
using GUI, 63
restoring Informix, 28–37
complete database restore, 28
finding information for restore, 29
restore options, 34
to another Informix Server, 36
using another device, 37
using CLI, 35
using GUI, 31
using Informix commands, 35
using Informix commands, examples, 36
whole-system restore, 28
restoring Lotus, 101–105
examples, 105
restore options, 105
using GUI, 102
running backups See starting backups

S
scheduling backups
DB2 integration, 58
Informix integration, 19
Lotus integration, 97
starting backups

I-4