HP OpenView Storage Data Protector

Integration Guide
for Microsoft Applications:
SQL Server 7/2000
Exchange Server 5.x
Exchange Server 2000/2003
Volume Shadow Copy Service

Manual Edition: October 2004

Manufacturing Part Number: B6960-90108

Release A.05.50

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

Legal Notices
©Copyright 2004 Hewlett-Packard Development Company, L.P.
Confidential computer software. Valid license from HP required for
possession, use or copying. Consistent with FAR 12.211 and 12.212,
Commercial Computer Software, Computer Software Documentation,
and Technical Data for Commercial Items are licensed to the U.S.
Government under vendor's standard commercial license.
The information contained herein is subject to change without notice.
The only warranties for HP products and services are set forth in the
express warranty statements accompanying such products and services.
Nothing herein should be construed as constituting an additional
warranty. HP shall not be liable for technical or editorial errors or
omissions contained herein.
UNIX® is a registered trademark of The Open Group.
Microsoft®, 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.
Java™ is a U.S. trademark of Sun Microsystems, Inc.
ARM® is a registered trademark of ARM Limited.

ii
 Contents
1. Integrating Microsoft SQL Server 7.0/2000 and Data Protector
In This Chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Prerequisites and Limitations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Integration Concept . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Advanced Concept - Parallelism . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Data Protector Microsoft SQL Server 7.0/2000 Configuration File . . . . . . . . . . . . . . . 12
Configuring the Integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Configuring Microsoft SQL Server 7.0/2000 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Configuring a Microsoft SQL Server 7.0/2000 Backup. . . . . . . . . . . . . . . . . . . . . . . . 18
Backing Up Microsoft SQL Server 7.0/2000 Databases. . . . . . . . . . . . . . . . . . . . . . . . . 26
Scheduling a Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Running an Interactive Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Restoring a Microsoft SQL Server 7.0/2000 Database . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Restoring Using the Data Protector GUI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Restore Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Restoring Using the Data Protector CLI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Disaster Recovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Performance Tuning. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Monitoring a Microsoft SQL Server 7.0/2000 Backup and Restore. . . . . . . . . . . . . . . . 47
Monitoring Current Sessions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Viewing Previous Sessions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
Before You Begin. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
Configuration Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
Backup Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
Restore Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
Before You Call Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

2. Integrating Microsoft Exchange Server 5.x and Data Protector

In This Chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
Prerequisites and Limitations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
Integration Concept . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
Configuring the Integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
Configuring Microsoft Exchange Server 5.x . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
Configuring a Microsoft Exchange Server 5.x Backup . . . . . . . . . . . . . . . . . . . . . . . 70
Testing the Microsoft Exchange 5.x Backup Configuration . . . . . . . . . . . . . . . . . . . 76

iii
Contents
Backing Up Microsoft Exchange Server 5.x . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
Scheduling a Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
Running an Interactive Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
Restoring a Microsoft Exchange 5.x Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
Restoring from the Latest Online Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
Restore Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
Disaster Recovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
Performance Tuning. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
Monitoring a Microsoft Exchange 5.x Backup and Restore . . . . . . . . . . . . . . . . . . . . . . 91
Monitoring Current Sessions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
Viewing Previous Sessions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
General Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
Backup Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
Restore Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97

3. Integrating Microsoft Exchange Server 2000/2003 and Data Protector

In This Chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
Prerequisites and Limitations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
Integration Concept . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
Configuring the Integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110
Configuring a Microsoft Exchange Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
Backing Up Microsoft Exchange Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118
Scheduling a Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118
Running an Interactive Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119
Restoring a Microsoft Exchange Server Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121
Restore Using the GUI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122
Restore Using the CLI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128
Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130
General Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130
Backup Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131
Restore Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132

4. Integrating Microsoft Exchange Single Mailbox and Data Protector

In This Chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137
Prerequisites and Limitations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139

iv
 Contents
Integration Concept . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141
Configuring the Integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144
Configuring the Single Mailbox Integration Agent . . . . . . . . . . . . . . . . . . . . . . . . . 144
Configuring a Single Mailbox Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148
Backup Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151
Testing the Integration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153
Backing Up a Single Mailbox . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155
Scheduling a Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155
Running an Interactive Backup Using the Data Protector GUI . . . . . . . . . . . . . . . 156
Running an Interactive Backup Using the Data Protector CLI. . . . . . . . . . . . . . . . 157
Restoring a Single Mailbox . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159
Restoring a Single Mailbox Using the Data Protector GUI . . . . . . . . . . . . . . . . . . . 159
Restore Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165
Restoring a Single Mailbox Using the Data Protector CLI . . . . . . . . . . . . . . . . . . . 165
Performance Tuning. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167
Monitoring a Single Mailbox Backup and Restore. . . . . . . . . . . . . . . . . . . . . . . . . . . . 169
Monitoring Current Sessions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169
Viewing Previous Sessions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170
Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172
General Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172
Configuration Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173
Backup Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175
Restore Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176

5. Integrating Microsoft Volume Shadow Copy Service with Data Protector

In This Chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181
Prerequisites and Limitations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185
Integration Concepts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187
Configuring the Integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191
Configuring the Data Protector VSS Cluster-Aware Integration . . . . . . . . . . . . . . 191
Writers Specifics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194
Backing Up Writers Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199
Creating Backup Specification Using GUI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199
Scheduling the Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204
Running an Interactive Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205
Restoring Writers Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207
Restore Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207

v
Contents
MSDE Writer Restore Specifics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209
Microsoft Exchange Server 2003 Writer Restore Specifics . . . . . . . . . . . . . . . . . . . 211
Restore Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214
Monitoring a VSS Backup and Restore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215
Monitoring Current Sessions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215
Viewing Previous Sessions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216
Troubleshooting Integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 218
Restore Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 218

Glossary

Index

vi
 Printing History
The manual printing date and part number indicate its current edition.
The printing date will change when a new edition is printed. Minor
changes may be made at reprint without changing the printing date. The
manual part number will change when extensive changes are made.
Manual updates may be issued between editions to correct errors or
document product changes. To ensure that you receive the updated or
new editions, you should subscribe to the appropriate product support
service. See your HP sales representative for details.
Table 1 Edition History

Part Number Manual Edition Product

B6960-90108 October 2004 Data Protector Release

A.05.50

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 HP OpenView Storage Data Protector
Administrator’s Guide 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://support.openview.hp.com/support.jsp
http://www.hp.com/support
Information about the latest Data Protector patches can be found at
http://support.openview.hp.com/patches/patch_index.jsp
For information on the Data Protector required patches, refer to the HP
OpenView Storage Data Protector Software Release Notes.
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
http://ovweb.external.hp.com/lpe/doc_serv/

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://ovweb.external.hp.com/lpe/doc_serv/
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 HP OpenView Storage Data Protector Administrator’s
Guide.
HP OpenView Storage Data Protector Administrator’s Guide
This manual describes typical configuration and administration tasks
performed by a backup administrator, such as device configuration,
media management, configuring a backup, and restoring data.
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 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 7/2000, Exchange Server 5.x, Exchange
Server 2000/2003, and Volume Shadow Copy Service

xiii
 This manual describes the integrations of Data Protector with the
following Microsoft applications: Microsoft Exchange Server
2000/2003, Microsoft Exchange Server 5.x, Microsoft SQL Server
7/2000, 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, IBM DB2, and Lotus
Notes/Domino.
• 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, and Network Data Management
Protocol.
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, HP
OpenView Service Desk, and HP OpenView Reporter. It is intended for
backup administrators. It discusses how to use the OpenView
applications for Data Protector service management.
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.

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

xv
 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 Software Release Notes
This manual gives a description of new features of HP OpenView Storage
Data Protector A.05.50. 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.openview.hp.com/products/datapro/spec_0001.html.

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

xvi
In This Book
The HP OpenView Storage Data Protector Integration Guide for Microsoft
Applications: SQL Server 7/2000, Exchange Server 5.x, Exchange Server
2000/2003, and Volume Shadow Copy Service describes how to configure
and use Data Protector with Microsoft applications.

Audience
This manual is intended for backup administrators who are responsible
for the planning, setup, and maintenance of network backups. It assumes
that 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.

xvii
Organization
The manual is organized as follows:
Chapter 1 “Integrating Microsoft SQL Server 7.0/2000 and Data
Protector” on page 1.
Chapter 2 “Integrating Microsoft Exchange Server 5.x and Data
Protector” on page 59.
Chapter 3 “Integrating Microsoft Exchange Server 2000/2003 and
Data Protector” on page 101.
Chapter 4 “Integrating Microsoft Exchange Single Mailbox and
Data Protector” on page 135.
Chapter 5 “Integrating Microsoft Volume Shadow Copy Service
with Data Protector” on page 179.
Glossary Definition of terms used in this manual.
The integrations of Data Protector with the following database
applications are described in the HP OpenView Storage Data Protector
Integration Guide for Oracle and SAP:

• Oracle
• SAP R/3
• SAP DB
The integrations of Data Protector with the following database
applications are described in the HP OpenView Storage Data Protector
Integration Guide for IBM Applications: Informix, DB2, and Lotus
Notes/Domino:

• Informix
• IBM DB2 UDB
• Lotus Notes/Domino
The integrations of Data Protector with the following database
applications are described in the HP OpenView Storage Data Protector
Integration Guide for Sybase, Network Node Manager, and Network Data
Management Protocol:

• Sybase
• Network Node Manager

xviii
• Network Data Management Protocol
The integrations of Data Protector ZDB integrations with the following
applications or operating system services are described in the HP
OpenView Storage Data Protector Zero Downtime Backup Integration
Guide:

• Oracle
• SAP R/3
• Microsoft SQL Server 7.0/2000
• Microsoft Volume Shadow Copy Service
• Microsoft Exchange Server 2000/2003

xix
xx
1 Integrating Microsoft SQL
Server 7.0/2000 and Data
Protector

Chapter 1 1
Integrating Microsoft SQL Server 7.0/2000 and Data Protector
In This Chapter

In This Chapter
This chapter explains how to configure and use the Data Protector
Microsoft SQL Server 7.0/2000 integration.
The chapter is organized into the following sections:

“Overview” on page 3
“Prerequisites and Limitations” on page 5
“Integration Concept” on page 6
“Data Protector Microsoft SQL Server 7.0/2000 Configuration File” on
page 12
“Configuring the Integration” on page 14
“Backing Up Microsoft SQL Server 7.0/2000 Databases” on page 26
“Restoring a Microsoft SQL Server 7.0/2000 Database” on page 29
“Performance Tuning” on page 41
“Monitoring a Microsoft SQL Server 7.0/2000 Backup and Restore” on
page 47
“Troubleshooting” on page 50

2 Chapter 1
 Integrating Microsoft SQL Server 7.0/2000 and Data Protector
Overview

Overview
The Data Protector integration with Microsoft SQL Server 7.0/2000
allows you to perform online backups.
Refer to the HP OpenView Storage Data Protector Software Release Notes
for information about platforms and devices that are supported by the
Data Protector Microsoft SQL Server 7.0/2000 integration.
The online backup concept is widely accepted. It addresses the business
requirements for high application availability better than the offline
backup concept.
Data Protector Microsoft SQL 7.0/2000 integration supports the
following backup types:

• Full online database backups

• Transaction log online backups
• Differential online database backups
Data Protector Microsoft SQL 7.0/2000 integration supports the
following restore options:

• Point-in-time restore
• Restore database to another SQL Server
• Recovery completion state
• Force restore over existing database

Advantages Using Data Protector together with Microsoft SQL Server 7.0/2000 offers
several advantages over using Microsoft SQL Server 7.0/2000 alone:

• Central Management for all backup operations

The administrator can manage backup operations from a central
point.
• Media Management
Data Protector has an advanced media management system that
allows users to monitor media usage, set the protection for stored
data, as well as organize and manage devices in media pools.

Chapter 1 3
Integrating Microsoft SQL Server 7.0/2000 and Data Protector
Overview

• Backup Management
Backed up data can be duplicated during or after the backup to
increase fault tolerance of backups, to improve data security and
availability, or for vaulting purposes.
• Scheduling
Data Protector has a built-in scheduler, which allows the
administrator to automate backups to run periodically. With the Data
Protector Scheduler, the backups you configure run unattended at
specified times, provided the devices and media are properly set.
• Device Support
Data Protector supports a wide range of devices: files, standalone
drives, very large multiple drive libraries, etc.
• Reporting
Data Protector has reporting capabilities that allow you to receive
information about your backup environment. You can schedule
reports to be issued at a specific time or attached to a predefined set
of events, such as the end of a backup session or a mount request.
• Monitoring
Data Protector has a feature that allows the administrator to monitor
currently running sessions and view finished sessions from any
system that has the Data Protector GUI installed.
All backup sessions are logged in the IDB, which provides the
administrator with a history of activities that can be queried at a
later time.

4 Chapter 1
 Integrating Microsoft SQL Server 7.0/2000 and Data Protector
Prerequisites and Limitations

Prerequisites and Limitations

Prerequisites • You need a license to use the Data Protector Microsoft SQL Server
7.0/2000 integration. Refer to the HP OpenView Storage Data
Protector Installation and Licensing Guide for information about
licensing.
• Before you begin, make sure that you have correctly installed and
configured the Microsoft SQL Server 7.0/2000 and Data Protector
systems. Refer to the:

— HP OpenView Storage Data Protector Software Release Notes for

an up-to-date list of supported versions, platforms, devices,
limitations, and other information.
— HP OpenView Storage Data Protector Installation and Licensing
Guide for instructions on how to install Data Protector on various
architectures and how to install the Data Protector Microsoft SQL
Server 7.0/2000 integration.
— SQL Server Books Online for online information on Microsoft SQL
Server 7.0/2000.
• Do not use double quotes (" ") in object-specific pre-exec and post-exec
commands.

Limitation Preview is not possible for SQL 7.0/2000 backup and restore sessions.
It is assumed that you are familiar with the Microsoft SQL Server
7.0/2000 database administration and the basic Data Protector
functionality.

Chapter 1 5
 Integrating Microsoft SQL Server 7.0/2000 and Data Protector
Integration Concept

Integration Concept
Virtual Device The Microsoft SQL Server 7.0/2000 introduces a new backup interface
Interface called Virtual Device Interface (VDI). VDI allows much faster backups
and restores than the backup interface used in previous versions of the
Microsoft SQL Server.
The central component of the integration is the Data Protector
sql_bar.exe executable, which is installed on the Microsoft SQL Server
7.0/2000 system. From the perspective of the Microsoft SQL Server
7.0/2000, Data Protector is seen as media management software. The
sql_bar.exe executable implements multiple virtual devices used for
backup and restore, and transforms VDI commands from the Microsoft
SQL Server into Data Protector backup or restore streams.

Fast Direct Mode The VDI architecture allows the Data Protector General Media Agent to
access data directly in the Microsoft SQL Server's memory, provided that
the devices are attached directly to the Microsoft SQL Server system.
Therefore, high backup and restore speeds on large databases can be
achieved.
The high performance Data Protector mode is called Fast direct mode.

Backup Types There are three online backup types of the Microsoft SQL Server
7.0/2000 system that can be performed using the Data Protector
Microsoft SQL 7.0/2000 integration:
Full database backup
Full database backup includes all data in a database regardless of
whether the database has changed after the last backup was created.
This means that the entire database backup does not depend on any
other backup media.
Differential database backup
A differential database backup records only the data changes made to
the database since the last full database backup. A differential database
backup takes less time to complete than a full database backup. By
creating differential database backups more frequently than full
database backups, you can conserve the media used for a backup.

6 Chapter 1
 Integrating Microsoft SQL Server 7.0/2000 and Data Protector
Integration Concept

Transaction log backup

Transaction log backups generally use fewer resources than database
backups, so they can be created more frequently than database backups.
By applying transaction log backups, you can recover the database to a
specific point in time.
A transaction log backup is not possible sometimes. For example, if the
Recovery model option on the Microsoft SQL Server 7.0/2000 is not set
to Bulk-Logged or Full, Data Protector performs a differential or full
backup instead.

Backup Objects When selecting objects for a backup, you can choose to back up the whole
server system or may select particular databases, which are listed below:
Database Description
user databases Contain user data. For example, there is the pubs
database providing learning tools, which is the basis
for most of the examples in Microsoft SQL Server
7.0/2000 manuals.
master Controls the user databases and the operation of
Microsoft SQL Server 7.0/2000 as a whole. It keeps
track of such information as user accounts,
configurable environment variables, and system error
messages.
model Provides a template or prototype for new user
databases.
distribution The distribution database is one of the system
databases used by the replication components of the
Microsoft SQL Server 7.0/2000, such as Distribution
Agent, to store data, including transactions, snapshot
jobs, synchronization status, and replication history
information. This database does not necessarily reside
on a server unless the system is used for remote
distribution or as a combined Publisher/Distributor.
msdb Provides a storage area for scheduling information and
information about backups.

Chapter 1 7
 Integrating Microsoft SQL Server 7.0/2000 and Data Protector
Integration Concept

IMPORTANT Table backup is not supported by the Data Protector Microsoft SQL
Server 7.0/2000 integration.

For a complete description of system databases, refer to the Microsoft

SQL Server 7.0/2000 Books Online.
Full and differential backups, together with regular transaction log
backups, prevent a user from data loss in the event of a disk failure.
Furthermore, transaction log backups are needed to perform a
point-in-time restore. Data Protector restores the databases so that the
last differential backup is applied to the most recent full backup. Then
the transaction log backups are applied according to the specified
point-in-time restore option.
The recovery itself is performed by the Microsoft SQL Server.

Backup Flow A backup session is started by the Data Protector Backup Session
Manager (BSM), which reads the Data Protector backup specification
and invokes sql_bar.exe. The BSM also starts the General Media
Agents. The sql_bar.exe executable connects to the Microsoft SQL
Server 7.0/2000 and receives data from it via VDI. It then passes the
instructions on to Data Protector General Media Agents, which write the
data to the backup devices.
Messages from the backup session are sent to the Backup Session
Manager, which then writes messages and information regarding the
respective session to the IDB.

Restore Flow Using the Data Protector User Interface, the objects and object versions
which are to be restored are defined by the user. A restore session is
started by the Restore Session Manager (RSM), which starts
sql_bar.exe and the Data Protector General Media Agents. The
sql_bar.exe connects to Microsoft SQL Server 7.0/2000 and receives
data from the General Media Agents. The Microsoft SQL Server 7.0/2000
then writes the data restored by Data Protector to the disks.
Messages from the restore session are sent to the Data Protector RSM,
which writes messages and information regarding the respective session
to the IDB.
The concept of a backup and a restore session is shown in the Figure 1-1
on page 9.

8 Chapter 1
 Integrating Microsoft SQL Server 7.0/2000 and Data Protector
Integration Concept

Figure 1-1 Microsoft SQL 7.0/2000 Integration Concept

Legend:
SM A Data Protector Session Manager, which is the Data
Protector Backup Session Manager during backup, or
the Data Protector Restore Session Manager during
restore.
BackupAPI or VDI The Microsoft SQL Server 7.0/2000 Virtual Device
Interface, the Microsoft backup interface introduced
with the Microsoft SQL Server 7.0.
MA The Data Protector General Media Agent.

Advanced Concept - Parallelism

Data Protector can back up more than one Microsoft SQL Server
7.0/2000 database at a time. It can even back up a single database using
multiple streams.
The two parallelism types that are used with Microsoft SQL Server
7.0/2000 are database parallelism and the number of concurrent
streams.

Chapter 1 9
 Integrating Microsoft SQL Server 7.0/2000 and Data Protector
Integration Concept

• Database parallelism
More than one database is backed up at a time if the number of
available devices allows you to perform backups in parallel.
The allocation of streams to devices is done automatically.
Data Protector tries to use all available devices to run the backup in
parallel.
• Number of concurrent streams
The number of concurrent streams is defined as the number of
devices used to back up a particular database or Microsoft SQL
Server 7.0/2000. It can be specified by the user or calculated
automatically.

NOTE Microsoft SQL Server 7.0/2000 does not support the backup of multiple
streams to one device.

Figure 1-2 on page 11 gives an example of a Data Protector backup

session where four Microsoft SQL Server 7.0/2000 databases are being
backed up using a different number of concurrent streams per database.

10 Chapter 1
 Integrating Microsoft SQL Server 7.0/2000 and Data Protector
Integration Concept

Figure 1-2 Database Parallelism = 4, Overall Concurrency = 10

Number of concurrent streams = 1

Db1
Media Agent

Number of concurrent streams = 2

Media Agent
Db3
Media Agent

Number of concurrent streams = 3

Media Agent
Db3 Media Agent
Media Agent
Number of concurrent streams = 4
Media Agent
Media Agent
Db4 Media Agent
Media Agent

Chapter 1 11
 Integrating Microsoft SQL Server 7.0/2000 and Data Protector
Data Protector Microsoft SQL Server 7.0/2000 Configuration File

Data Protector Microsoft SQL Server 7.0/2000

Configuration File
Data Protector stores the Microsoft SQL Server 7.0/2000 integration
parameters for every configured Microsoft SQL Server 7.0/2000 in the
/etc/opt/omni/server/integ/config/MSSQL/<client_name>%<insta
nce_name> file (HP-UX and Solaris systems), or in the
<Data_Protector_home>\Config\Server\Integ\Config\MSSQL\<cl
ient_name>%<instance_name> file (Windows systems) on the Cell
Manager. The parameters stored are the user name and password for the
Microsoft SQL Server 7.0/2000 user, who must have permissions to run
backup and restore within Microsoft SQL Server 7.0/2000 (assuming the
standard security is used during the configuration of the integration).
The configuration parameters are written to the Data Protector
Microsoft SQL Server 7.0/2000 configuration file:

• during the configuration of the integration

• during the creation of a backup specification

Syntax The syntax of the Data Protector Microsoft SQL Server 7.0/2000
configuration file is as follows:
Login='<user>';
Password='<encoded_password>';

IMPORTANT To avoid problems with your backups, take extra care to ensure that the
syntax of your configuration file matches the examples.

Example This is an example of the file:

• if standard security is used:

Login='TROLL\Administrator';
Password='dsjf08m80fh43kdf';

12 Chapter 1
 Integrating Microsoft SQL Server 7.0/2000 and Data Protector
Data Protector Microsoft SQL Server 7.0/2000 Configuration File

• if integrated security is used:

Login='';
Password='dsjf08m80fh43kdf';

Chapter 1 13
 Integrating Microsoft SQL Server 7.0/2000 and Data Protector
Configuring the Integration

Configuring the Integration

The configuration of the Data Protector Microsoft SQL Server 7.0/2000
integration consists of the following:

1. “Configuring Microsoft SQL Server 7.0/2000” on page 14

2. “Configuring a Microsoft SQL Server 7.0/2000 Backup” on page 18

Before You Begin It is recommended that you configure and run some test filesystem
backups using Data Protector.
This includes installing the Disk Agent on the Microsoft SQL Server
7.0/2000 system. Any device can be used for this test. Configure a
standard filesystem backup, which can include one directory only.
Thus, you can check whether the Microsoft SQL Server 7.0/2000 client
system and the Data Protector Cell Manager are communicating
properly.
In case of problems, this type of backup is much easier to troubleshoot
than the integration of Microsoft SQL Server 7.0/2000 with Data
Protector.
Refer to the HP OpenView Storage Data Protector Administrator’s Guide
for instructions. In case of any difficulties with the filesystem backup, do
not continue configuring the integration until you have solved the
problems.

Configuring Microsoft SQL Server 7.0/2000

The configuration is performed during the creation of the first backup
specification for Microsoft SQL Server databases. For creating a backup
specification, see “Configuring a Microsoft SQL Server 7.0/2000 Backup”
on page 18.
However, you can change the configuration any time after you have
created at least one backup specification. For information on changing
the configuration, see “Changing and Checking the Microsoft SQL Server
7.0/2000 Configuration” on page 17.

Prerequisites • Microsoft SQL Server 7.0/2000 must be online during the

configuration procedure.

14 Chapter 1
 Integrating Microsoft SQL Server 7.0/2000 and Data Protector
Configuring the Integration

• Configuration must be performed for every single Microsoft SQL

Server 7.0/2000 system.
The configuration consists of setting the user name and password for the
Data Protector services. Thereafter, the services are able to connect to
the Microsoft SQL Server 7.0/2000 and operate under the specified
account.
The user must have appropriate permissions to run backup and restore
on the respective Microsoft SQL Sever 7.0/2000.
You can check this using the Microsoft SQL Server 7.0/2000 Enterprise
Manager.

Figure 1-3 Microsoft SQL Server 7.0/2000 Users

You need to define the way in which the Data Protector sessions will run
on the Microsoft SQL Server system, using either Data Protector Inet
account (in most cases the system account) or a specified user account
(preferred option).

Chapter 1 15
 Integrating Microsoft SQL Server 7.0/2000 and Data Protector
Configuring the Integration

Configuration To configure the Microsoft SQL 7.0/2000 Server while creating the first
Procedure backup specification or while changing the configuration, proceed as
follows:
In the Configure MS SQL dialog box, select either Integrated
Security or Standard Security. See Figure 1-4.

Figure 1-4 Configuring the Microsoft SQL Server

NOTE It is recommended that the Microsoft SQL Server 7.0/2000 system

administrator configures the Data Protector Microsoft SQL Server
7.0/2000 integration.

• If you use Standard Security, provide a user name in the format

<DOMAIN>\<user_name> and a password for a Microsoft SQL Server
7.0/2000 user, who must have permissions to run backup and restore
of the Microsoft SQL Server 7.0/2000.
• If you use Integrated Security, the Data Protector SQL Server
7.0/2000 integration will use the Data Protector Inet account to
connect to the Microsoft SQL Server 7.0/2000.
See Microsoft SQL Server 7.0/2000 documentation for more detailed
information about security and for a description of the two connection
types.
Click OK to confirm the configuration.

16 Chapter 1
 Integrating Microsoft SQL Server 7.0/2000 and Data Protector
Configuring the Integration

What Happens? The login information is written to the Data Protector Microsoft SQL
Server 7.0/2000 configuration file on the Cell Manager:
<Data_Protector_home>\Config\server\Integ\Config\MSSQL\<ho
stname>%<instance name> (Windows Cell Manager) or
/etc/opt/omni/server/integ/config/MSSQL/<hostname>%<instance
name> (UNIX Cell Manager).

Changing and Checking the Microsoft SQL Server 7.0/2000

Configuration
You can change the configuration of a specific Microsoft SQL Server
7.0/2000 and its instance any time after you have created at least one
backup specification for this Microsoft SQL Server 7.0/2000. To change
the configuration, proceed as follows:

1. In the HP OpenView Storage Data Protector Manager, switch to

the Backup context.
2. In the Scoping Pane, expand Backup, Backup Specifications, and
then MS SQL Server. Click an existing backup specification for the
Microsoft SQL Server 7.0/2000 for which you want to change the
configuration.
3. In the Source property page, right-click the name of the Microsoft
SQL Server 7.0/2000 and select Configure.
4. Configure the Microsoft SQL Server 7.0/2000 as described in
“Configuring Microsoft SQL Server 7.0/2000” on page 14.
5. Right-click the name of the Microsoft SQL Server 7.0/2000 and select
Check Configuration. See Figure 1-5.

Chapter 1 17
 Integrating Microsoft SQL Server 7.0/2000 and Data Protector
Configuring the Integration

Figure 1-5 Checking Configuration

Once you start checking the configuration procedure, the Data

Protector service reads the login information from the configuration
file.

Configuring a Microsoft SQL Server 7.0/2000 Backup

To configure a Microsoft SQL Server 7.0/2000 backup, perform the
following steps:

1. Configure the devices you plan to use for a backup. Refer to the online
Help index keyword “configuring devices” for instructions. See also
“Performance Tuning” on page 41 for advanced options.
2. Configure media pools and media for a backup. Refer to the online
Help index keyword “creating media pools” for instructions.
3. Create a Data Protector Microsoft SQL Server 7.0/2000 backup
specification.

18 Chapter 1
 Integrating Microsoft SQL Server 7.0/2000 and Data Protector
Configuring the Integration

Creating a Backup Specification

To create a Microsoft SQL Server 7.0/2000 backup specification, perform
the following steps:

1. In the HP OpenView Storage Data Protector Manager, switch to

the Backup context.
2. In the Scoping Pane, expand Backup, and then Backup
Specifications. Right-click MS SQL Server and click Add Backup.
3. In the Create New Backup dialog box, select the Blank Microsoft
SQL Server Backup template. See Figure 1-6.

Figure 1-6 Selecting a Blank Template

Click OK.
4. In the Client drop-down list, select the Microsoft SQL Server
7.0/2000 system. If the application is cluster-aware, select the virtual
server of the Microsoft SQL Server 7.0/2000 resource group.
In the Application database drop-down list, leave the instance
name for Microsoft SQL Server 7.0/2000.

Chapter 1 19
 Integrating Microsoft SQL Server 7.0/2000 and Data Protector
Configuring the Integration

Click Next.
5. If the client has not been configured yet, the Configure Microsoft
SQL dialog box appears. See “Configuring Microsoft SQL Server
7.0/2000” on page 14 for detailed steps.
6. Select the Microsoft SQL Server 7.0/2000 databases you want to back
up.

Figure 1-7 Selecting Backup Objects

Click Next.
7. Select the device(s) you want to use for the backup. Click Properties
to set the device concurrency, media pool, and preallocation policy. For
more information on these options, click Help.
You can also specify whether you want to create additional copies
(mirrors) of the backup during the backup session. Specify the desired
number of mirrors by clicking the Add mirror and Remove mirror
buttons. Select separate devices for the backup and for each mirror.

20 Chapter 1
 Integrating Microsoft SQL Server 7.0/2000 and Data Protector
Configuring the Integration

The minimum number of devices required for mirroring Microsoft

SQL Server integration objects equals the number of devices used for
backup.
For detailed information on the object mirror functionality, see HP
OpenView Storage Data Protector Administrator’s Guide.
Click Next.
8. Select the backup options.
For information on Backup Specification Options and Common
Application Options, refer to the online Help.
For information on Application Specific Option, see “Microsoft
SQL Server 7.0/2000 Specific Backup Options” on page 22 or online
Help.
Click Next.
9. Optionally, schedule the backup. For information on scheduler, press
F1.

10. Save the backup specification. It is recommended that you save all
Microsoft SQL Server 7.0/2000 backup specifications in the MSSQL
group. See the following figure.

Figure 1-8 Saving a Backup Specification

11. Once saved, the backup specification can be started by clicking Start
Backup.
See “Backing Up Microsoft SQL Server 7.0/2000 Databases” on
page 26 for information on starting a backup.

Chapter 1 21
 Integrating Microsoft SQL Server 7.0/2000 and Data Protector
Configuring the Integration

Microsoft SQL Server 7.0/2000 Specific Backup Options

The Microsoft SQL Server 7.0/2000 specific backup options are specified
using the Data Protector GUI by clicking the Advanced tab in the
Application Specific Options group box.
The following are the Microsoft SQL Server 7.0/2000 application specific
backup options:

Concurrent streams This option is available only if the whole

Microsoft SQL 7.0/2000 Server is backed up. It sets
the number of user-specified concurrent streams
(devices) used for a backup. To set the number of
concurrent streams for a particular Microsoft SQL
Server 7.0/2000 database (if one or more Microsoft
SQL Server 7.0/2000 databases were selected for a
backup), see “Object Specific Options” on page 23.
Fast Direct Mode This option can only be used with locally
connected devices in order to optimize performance.
This operational mode must be combined with
special device settings. See “Performance Tuning”
on page 41 for details.

NOTE It is recommended that the local devices with special block-size settings
be dedicated to the Microsoft SQL Server 7.0/2000 high performance
backup only.

Check Database Integrity By selecting this option the structure of

the MS SQL data is verified before the backup. In
other words, the MS SQL data integrity validation
is performed.

NOTE If the check fails, the backup session is still completed (with warnings).

Pre-exec Specifies a command with arguments or a script

that will be started on the Microsoft SQL Server
7.0/2000 before the backup starts. The
command/script is started by the Data Protector
sql_bar.exe and must reside in the

22 Chapter 1
 Integrating Microsoft SQL Server 7.0/2000 and Data Protector
Configuring the Integration

<Data_Protector_home>\bin directory of the

Microsoft SQL Server 7.0/2000 system. Only the
filename must be provided in the backup
specification.
Post-exec Specifies a command with arguments or a script
that will be started on the Microsoft SQL 7.0/2000
Server after the backup. The command/script is
started by the Data Protector sql_bar.exe and
must reside in the <Data_Protector_home>\bin
directory of the Microsoft SQL Server 7.0/2000
system. Only the filename must be provided in the
backup specification.

Figure 1-9 Application Specific Options

Object Specific Options

If you have specified one or several databases for a backup, so that the
backup specification is started as a database backup (as opposed to a
whole server backup), you can set the backup options on a single
database level.

Chapter 1 23
 Integrating Microsoft SQL Server 7.0/2000 and Data Protector
Configuring the Integration

NOTE If you selected whole server backup, the same options as in the
Application Specific Options windows are displayed here.

In the Backup Specification Summary property page, double-click an

object to open the Object Properties window, where you can customize
object properties for the respective database.

Figure 1-10 Object Properties

The following backup options can be selected per backup object:

Use default concurrent streams
You may keep this box checked so that the number of
concurrent streams is defined by Data Protector using
all available devices.

24 Chapter 1
 Integrating Microsoft SQL Server 7.0/2000 and Data Protector
Configuring the Integration

Concurrent streams
The number of user-specified concurrent streams
(devices) used for backup. VDI supports up to 32
virtual devices per database.

Chapter 1 25
 Integrating Microsoft SQL Server 7.0/2000 and Data Protector
Backing Up Microsoft SQL Server 7.0/2000 Databases

Backing Up Microsoft SQL Server 7.0/2000

Databases
To run an online backupof a Microsoft SQL Server 7.0/2000 database, use
any of the following methods:

Backup Methods • Schedule a backup of an existing Microsoft SQL Server 7.0/2000

backup specification using the Data Protector Scheduler.
• Start an interactive backup of an existing Microsoft SQL Server
7.0/2000 backup specification using the Data Protector GUI or the
Data Protector CLI.
For information on starting an interactive backup using the Data
Protector CLI, refer to the omnib man page.

Scheduling a Backup
Scheduling a backup specification means setting time, date, and type of a
backup that starts unattended once the scheduling options are defined
and saved in the backup specification.
For more information on scheduling, refer to the online Help index
keyword “scheduled backups”.
To schedule a Microsoft SQL Server 7.0/2000 backup, proceed as follows:

1. In the HP OpenView Storage Data Protector Manager, switch to

the Backup context.
2. In the Scoping Pane, expand Backup, Backup Specifications, and
then MS SQL Server.
3. Double-click the backup specification you want to schedule and click
the Schedule tab.
4. In the Schedule page, select a date in the calendar and click Add to
open the Schedule Backup dialog box.
5. Specify Recurring, Time options, Recurring options, and
Session options. See Figure 1-11.

26 Chapter 1
 Integrating Microsoft SQL Server 7.0/2000 and Data Protector
Backing Up Microsoft SQL Server 7.0/2000 Databases

You can select one of the following backup types: full, differential, or
transaction log backup. See “Integration Concept” on page 6 for a
detailed description of backup types.

Figure 1-11 Scheduling Backups

Click OK and then Apply to save the changes.

Running an Interactive Backup

An interactive backup can be performed any time after a backup
specification has been created and saved.
To start an interactive backup of a Microsoft SQL Server 7.0/2000
database, proceed as follows:

1. In the HP OpenView Storage Data Protector Manager, switch to

the Backup context.
2. In the Scoping Pane, expand Backup, Backup Specifications, and
then MS SQL Server.
3. Right-click the backup specification, and then select Start Backup.

Chapter 1 27
Integrating Microsoft SQL Server 7.0/2000 and Data Protector
Backing Up Microsoft SQL Server 7.0/2000 Databases

In the Start Backup dialog box, select the Backup type and Network
load options. For information on these options, click Help.
Click OK.

28 Chapter 1
 Integrating Microsoft SQL Server 7.0/2000 and Data Protector
Restoring a Microsoft SQL Server 7.0/2000 Database

Restoring a Microsoft SQL Server 7.0/2000

Database
You can restore a Microsoft Exchange 2000/2003 object using the Data
Protector GUI or using the Data Protector CLI.

Prerequisite Before you start a restore session, verify that the database is not being
used by any user.

Restoring Using the Data Protector GUI

In Microsoft SQL Server 2000, there is no need to create an empty
database prior to restoring database, since the database and its files are
generated automatically by the Microsoft SQL Server 2000.
If the database already exists and has a different structure, the restore
will fail unless you select the Force restore over existing database
option.
See “Restore Options” on page 33 for a detailed description.
General restore options that apply to all objects within a restore session,
such as Restore database to another Microsoft SQL Server and
Restore using a different device can be combined with the
object-specific restore options, which are the following:

• Point-in-time restore
• Recovery completion state
• Force restore over existing database
In this way, you can choose among several restore scenarios.

Restore Procedure To restore the Microsoft SQL Server 7.0/2000 databases using the Data
Protector GUI, proceed as follows:

1. In the HP OpenView Storage Data Protector Manager, switch to

the Restore context.
2. In the Scoping Pane, expand Restore Objects, MS SQL Server, and
then select the MS SQL Server from which you want to restore. A list
of backed up objects is displayed in the Results Area.

Chapter 1 29
 Integrating Microsoft SQL Server 7.0/2000 and Data Protector
Restoring a Microsoft SQL Server 7.0/2000 Database

3. Select the backed up Microsoft SQL Server 7.0/2000 databases you

want to restore. See Figure 1-12.

Figure 1-12 Restore Objects

To select the backup object specific options, right-click the object and
select Properties.

30 Chapter 1
 Integrating Microsoft SQL Server 7.0/2000 and Data Protector
Restoring a Microsoft SQL Server 7.0/2000 Database

Figure 1-13 Selecting the Object Specific Options

Here you can select the version (date of a backup) from which you
want to restore and choose the Microsoft SQL Server 7.0/2000 specific
restore options. See “Restore Options” on page 33 for details about
these options. Click OK.
4. In the Options property page, specify whether you want to restore
your data to another client or instance. In this case, you have to
specify new locations for the databases you want to restore. See
“Restore Options” on page 33.

NOTE When you click the Options tab, Data Protector browses the cell for the
running Microsoft SQL Server 2000 instances that can be selected as
target instances for restore. If no instances are found, the Restore to
another instance option is automatically disabled and the message
There are no instances on this client system is displayed.

Chapter 1 31
 Integrating Microsoft SQL Server 7.0/2000 and Data Protector
Restoring a Microsoft SQL Server 7.0/2000 Database

Select one of the following Restore actions:

• Restore data (default). Select this action to restore the whole

database.
• Restore and display file list only. Use this action if you do
not know the original file names. In this case, the list of files
backed up in a particular backup session is displayed.
• Restore and display headers only. Select this action if you
need specific details about the database backup. The SQL Server’s
header information is displayed.

Figure 1-14 Restore Options

5. Click Devices and then Media to select the devices and media to be
used for the restore.
Note that you can use a different device for the restore than the one
used for the backup. Refer to the “Restoring Under Another Device”
section in the HP OpenView Storage Data Protector Administrator’s
Guide for more information on how to perform a restore using
another device.

32 Chapter 1
 Integrating Microsoft SQL Server 7.0/2000 and Data Protector
Restoring a Microsoft SQL Server 7.0/2000 Database

IMPORTANT If the devices used for the restore are not those used for the backup,
select the same number of devices in the Devices property page as you
used when you backed up the databases.

6. Click Restore MS SQL Server and then Next to select the Report
level and Network load.
Click Finish to start the restore session.

Restore Options
See also “Before You Call Support” on page 56 for restore options
available from the command line only.
Backup Version
Specify the backup session from which the selected
objects will be restored.
Point-in-Time Restore
Point-in-time restore means that a user can specify a
point in time to which the database state must be
restored. After recovery, the database is recovered in
the state it was at the specified date and time.
Only transaction log records written before the
specified date and time are applied to the database.
Point-in-time restore is specified by selecting a backup
version and by setting the Stop at option.
Stop at
The Stop at option specifies the exact time when the
rollforward of transactions will be stopped. Therefore,
the backup you restore from must include transaction
log backups so that the Microsoft SQL Server can
recover the database to a particular point in time.
This option cannot be used with NORECOVERY or
STANDBY. If you specify a Stop at time that is after the
end of the RESTORE LOG operation, the database is left
in a non-recovered state, just as if RESTORE LOG had
been run with NORECOVERY.

Chapter 1 33
Integrating Microsoft SQL Server 7.0/2000 and Data Protector
Restoring a Microsoft SQL Server 7.0/2000 Database

Restore only this backup

If you have restored a version of the database and left
it in a non-operational or standby state, then you can
subsequently restore differential or transaction log
backups one by one, leaving each version
non-operational to restore additional backups.
Full restore of the database
All necessary versions are restored, including the latest
full backup, the latest differential backup (if one
exists), and all transaction log backups from the last
differential up to the selected version.
Force restore over the existing database
The existing database residing on the target restore
server system will be overwritten.
If a database with the same name as the one that you
want to restore already exists on the server, and it has
a different internal structure, then the Microsoft SQL
Server 7.0/2000 does not let you rewrite the database
without the Force Restore over existing
database option turned on.
Recovery Completion State
These options let you select the state of the database
after the recovery. You may select among the following:

• Leave the database operational. Once the last

transaction log has been restored and the recovery
has completed, the database is already operational.
• Leave the database non-operational after the last
transaction log has been restored. You may further
restore additional transaction logs one by one.
• Leave the database as read-only. You may further
restore transaction logs before the database is set to
read-write mode.

34 Chapter 1
 Integrating Microsoft SQL Server 7.0/2000 and Data Protector
Restoring a Microsoft SQL Server 7.0/2000 Database

Restore database with a new name

This option lets you restore your database under a
different name. You have to specify the database’s
logical file name and the destination file name
(suboptions of the Restore files to new locations
option) when selecting this option.
Restore files to new locations
This option allows you to restore files to a new location.
You need to specify the database’s logical file name, and
a destination target file name for the specified logical
file name. Use this option if you are restoring data to
another server, instance or making a copy of the
database on the same server.

Restoring to Another Microsoft SQL Server 2000 Instance or

(and) to Another Microsoft SQL Server 7.0/2000
To restore databases to a different Microsoft SQL Server 7.0/2000 system
or (and) to a different Microsoft SQL Server 2000 instance, check the
prerequisites below:

Prerequisites • Both Microsoft SQL Servers 7.0/2000 must have the same local
settings, such as code page and sort order. This information is
displayed in the session monitor for each backup.
• The Target Microsoft SQL Server 7.0/2000 must be in the same Data
Protector cell as the original Microsoft SQL Server 7.0/2000 and it
must be configured.
Proceed as follows:

1. If the target Microsoft SQL Server 7.0/2000 is not yet configured,

create a backup specification and configure the server.
See “Configuring a Microsoft SQL Server 7.0/2000 Backup” on
page 18.
2. Select the databases you want to restore and their versions.

Chapter 1 35
 Integrating Microsoft SQL Server 7.0/2000 and Data Protector
Restoring a Microsoft SQL Server 7.0/2000 Database

3. Select whether you want to restore the data to another Microsoft SQL
Server 7.0/2000 client or (and) to another Microsoft SQL Server 2000
instance:

• To restore the data to another Microsoft SQL Server 7.0/2000

client, select the Restore to another client option and then
select the target client from the drop-down list.
• To restore the data to another Microsoft SQL Server 2000
instance, select the Restore to another instance option. If you
do not see the list of instances in the drop-down list, enter the
instance name by yourself.
• To restore the data to another Microsoft SQL Server 2000 client
and to another Microsoft SQL Server 2000 instance, make sure
you entered the name of the instance that exists on the target
client. Otherwise, the restore will fail.
Also, specify the new locations for the databases you want to restore.
4. Start restore.
See “Restoring a Microsoft SQL Server 7.0/2000 Database” on page 29

Restoring Using the Data Protector CLI

A restore session can also be started from the command line. Switch to
the <Data_Protector_home>\bin directory on any client system
within the Data Protector cell that has the Data Protector User Interface
installed, and run the following command:
omnir -MSSQL -barhost <MSSQL_Server_Name> [-destination
<Target_MSSQL_Server>]-base <dbname>[-session <Session
_ID>][-nochain][-replace][-recovery rec|norec][-standby
<File>] [-instance <instance name>]
Provide the Session_ID of the backup session. In case of object copies, do
not use the copy session ID, but the object's backup ID, which equals the
object's backup session ID.

Example To start a restore of the database RONA that was running on the Microsoft
SQL Server 7.0/2000 called Alma, execute the following command to
restore the latest backup session to the same destination:
omnir -MSSQL -barhost Alma -base RONA

36 Chapter 1
 Integrating Microsoft SQL Server 7.0/2000 and Data Protector
Restoring a Microsoft SQL Server 7.0/2000 Database

Disaster Recovery
Disaster recovery is a very complex process that involves products from
several vendors. As such, a successful disaster recovery depends on all
the vendors involved. The information provided here is intended to be
used as a guideline.
Check the instructions from the database/application vendor on how to
prepare for a disaster recovery. See also the “Disaster Recovery” chapter
in the HP OpenView Storage Data Protector Administrator’s Guide for
instructions on how to approach system disaster recovery using Data
Protector.
This is a general procedure for recovering an application:

1. Complete the recovery of the operating system.

2. Install, configure, and initialize the database/application so that data
on the Data Protector media can be loaded back to the system.
Consult the documentation from the database/application vendor for
a detailed procedure and the steps needed to prepare the database.
3. Ensure that the database/application server has the required Data
Protector client software installed and is configured for the
database/application. Follow the procedures in this chapter and in the
troubleshooting section.
4. Start the restore. When the restore is complete, follow the
instructions from the database/application vendor for any additional
steps required to bring the database back online.
In case of a disk failure, you need to recover the operating system prior to
any other recovery tasks. Data Protector disaster recovery is used to
bring the operating system back up on the damaged system.
Refer to the HP OpenView Storage Data Protector Administrator’s Guide
for more information about the Data Protector disaster recovery.
The next step is restoring the Microsoft SQL Server 7.0/2000 database.

IMPORTANT If you need to reinstall SQL Server 7.0/2000, ensure that you use the
original local settings. Before you perform a restore to another client,
ensure that the local settings on the restore target system match the
original.

Chapter 1 37
 Integrating Microsoft SQL Server 7.0/2000 and Data Protector
Restoring a Microsoft SQL Server 7.0/2000 Database

You need to recover the master database first. See the following section
for the procedure on how to do this.

Recovering the Master Database

The master database holds the vital information about the Microsoft
SQL Server 7.0/2000 as a whole. If you lose the master database, you
cannot access any other databases and all of them are therefore
unavailable.
If the master database gets corrupted or lost, recover the master
database first to make the Microsoft SQL Server 7.0/2000 operational.
Next, restore all other databases or reattach them, as described in the
section “Recovering User Databases” on page 40.
To recover the master database, proceed as follows:

1. Rebuild the master database

Create the basic master database in order to make the Microsoft SQL
Server 7.0/2000 operational, since some databases might be corrupted
or might contain inconsistent data:

a. Shut down the Microsoft SQL Server 7.0/2000 if it is running.

b. Start the Rebuild Master utility
<SQL7.0/2000>\bin\rebuildm.exe
c. Select an appropriate character set and sort order to match the
backed up data. You can check this in the latest backup session
report.
d. Rebuild the database.
For more information, refer to the Microsoft SQL Server Books
Online.
2. Set user rights or reconfigure the integration
At this stage, either reconfigure the integration or set user rights.

Setting User After the master database is rebuilt, proceed as follows to set user
Rights rights using the Microsoft SQL Server 7.0/2000 Enterprise Manager:

a. From the server’s desktop, click Start, Programs, Microsoft

SQL Server 7/Microsoft SQL Server, Enterprise Manager to
start the utility.

38 Chapter 1
 Integrating Microsoft SQL Server 7.0/2000 and Data Protector
Restoring a Microsoft SQL Server 7.0/2000 Database

b. Right-click the server in question, and then select Register

Server. Configure the Microsoft SQL Server 7.0/2000 to use
trusted connections.
c. Close the dialog box and go to Security, Logins.
Select the user rights you want to use (such as sa,<password>).
d. Then return to the server in question, right-click its name, and
then select Register Server.
Enter the account you have just selected in Manage, Logins.

Perform any additional administration tasks that are required to

run the SQL Server at this point.

Reconfiguring the Reconfigure the Microsoft SQL Server 7.0/2000 Integration.

Microsoft SQL
See “Configuring a Microsoft SQL Server 7.0/2000 Backup” on
Server 7.0/2000
page 18 for instructions.
Integration
3. Stop all Microsoft SQL Server 7.0/2000 services
You can do this using the Windows desktop:
Start, Programs, Microsoft SQL Server 7.
Start the SQL Service Manager and stop the services.
4. Start the Microsoft SQL Server 7.0/2000 service in single-user
mode
This can be done from the Windows desktop:

a. In the Control Panel, go to Administrative Tools, Services.

b. Select the MSSQL Server Service.
c. Enter -m as a start-up parameter and start the services.
5. Restore the master database using the Data Protector
Manager
6. Restart the Microsoft SQL Server 7.0/2000 services in normal
mode
After the recovery of the master database, the Microsoft SQL Server
7.0/2000 service is automatically shut down. Start the Microsoft SQL
Server 7.0/2000 Service Manager and restart SQL services.

Chapter 1 39
 Integrating Microsoft SQL Server 7.0/2000 and Data Protector
Restoring a Microsoft SQL Server 7.0/2000 Database

Remember that you must restore all other databases if you perform
disaster recovery.
If you restored selected databases only, you need to reattach
databases (if they exist on disks) to the newly-rebuilt master
database. See the next section for details.

Recovering User Databases

To restore a user database, proceed as described in “Restoring a
Microsoft SQL Server 7.0/2000 Database” on page 29.
Note that restoring a database to a certain state often requires a
multiphase restore. This means that multiple versions need to be
restored to retrieve data. The latest full backup, the latest differential
backup and all transaction log backups after the last full or differential
backup must be restored.
Suppose you have the following backup sequence:
FD T TDTTTTT
and you want to restore the version marked T, then all the backup
versions in <italic> will be restored.
Restore is performed and automated by sql_bar.exe.

TIP It is also possible to restore versions one by one to have more control over
the restore process. Use the options Restore only this backup and
Recovery completion state to do this.

For more information about restoring the master database, see

“Recovering the Master Database” on page 38.
For more information on disaster recovery, refer to the HP OpenView
Storage Data Protector Administrator’s Guide and Microsoft SQL Server
Books Online.

40 Chapter 1
 Integrating Microsoft SQL Server 7.0/2000 and Data Protector
Performance Tuning

Performance Tuning
Performance tuning means customizing your Microsoft SQL Server
7.0/2000 and Data Protector in a way that enables them to achieve better
backup and restore results. You can improve the backup or restore
performance of your Microsoft SQL Server 7.0/2000 by following these
guidelines:

1. Ensure that your Microsoft SQL Server 7.0/2000 database files are on
separate disks.
2. Calculate the number of devices to be used in parallel. The main
consideration is to select a number of devices to match the bandwidth
of the incoming data stream and to identify the bottleneck. This can
be either the network, if devices are connected to remote systems, or
the Microsoft SQL Server 7.0/2000 itself, if the devices are connected
locally.
As the bandwidths of networks are most often either ~1 MB/s (10
Mbit Ethernet), or ~10 MB/s (100 Mbit Ethernet), though the actual
throughput is usually lower, you will not need more than one fast
device, such as a DLT 7000 for a remote backup.
There are two possibilities when you have devices connected locally:

a. Devices are dedicated to local backups of the Microsoft SQL Server

7.0/2000 and it is very likely that backup/restore performance is
important. Fast direct mode should be used.
b. Devices are shared within the Data Protector cell and
backup/restore performance is not very important. Fast direct
mode should be disabled.
Determine the maximum backup speed by performing a backup to a
few null file devices on a local server, and select the number of devices
that fit best with the measured performance.

TIP Create separate backup specifications for local and remote devices. It is
not recommended to use both in one backup specification.

Chapter 1 41
Integrating Microsoft SQL Server 7.0/2000 and Data Protector
Performance Tuning

3. Adjust the block size for local backup devices.

• Enable/Disable the Fast direct mode option.

Fast direct mode is an application-specific option per backup
specification, which enables Data Protector to read data directly
from the SQL Server’s shared memory, and can therefore increase
the backup/restore speed to/from local devices. See Figure 1-9 on
page 23.
This option should be used only if the highest performance is
required. Due to the specific device settings, these device
definitions should not be shared with conventional (filesystem)
backups. Therefore, it is not recommended to use this option in
general.
You should disable the Fast direct mode option (as well as the
special local device settings) if backup performance is not very
critical and/or other data is also backed up to devices connected to
the Microsoft SQL Server system.
The Fast direct mode option can only be used for local devices.
This mode is ignored for remote devices.
• Set the block size.
Before you activate the Fast direct mode option, a special block
size has to be set for the devices, as referenced in the backup
specification. The adjusted block sizes can be calculated as follows:
block size (kB) = 64*N + 4 (N=1,...64)
block size (kB) = 68, 132, .....4100 kB
All selected devices must have the same block size.
Some performance improvement can be gained by specifying a
block size larger than 68 KB. You can increase the block size step
by step and compare the performance achieved for each step.
Note that it is recommended to set the block size to 68 KB.
If you keep the Fast direct mode inactive, you do not need to
adjust the local device settings; otherwise, adjust the block size for
all selected local devices, where the block size must meet the above
requirements.

42 Chapter 1
 Integrating Microsoft SQL Server 7.0/2000 and Data Protector
Performance Tuning

You can adjust the block size during the initial device definition
for local devices by checking the attached check box and selecting
the block size. See Figure 1-15 on page 44.
You can also modify the block size later, however you will have to
first calculate the block size by using the formula above and then
insert the value as shown in Figure 1-16 on page 45.
• Modify the registry.
To use a block size larger than 56 KB, some SCSI interface cards
require you to adjust related values in the registry of the system
where the device is connected.
Refer to the HP OpenView Storage Data Protector Administrator’s
Guide for information on how to adjust registry values for block
sizes larger than 56 KB.

Chapter 1 43
 Integrating Microsoft SQL Server 7.0/2000 and Data Protector
Performance Tuning

Figure 1-15 Creating an Adjusted Local Device

To modify the block sizes of an existing device, proceed as follows:

a. In the HP OpenView Storage Data Protector Manager,

switch to the Devices & Media context.
In the Scoping Pane, expand Devices and click the
locally-connected device that you want to modify. In the Results
Area, select Settings, and then click Advanced.
b. In the Advanced Options window, click Sizes, where you can
modify block sizes.

44 Chapter 1
 Integrating Microsoft SQL Server 7.0/2000 and Data Protector
Performance Tuning

Figure 1-16 Advanced Options

If the Fast direct mode option has been activated and not all
selected local devices in a backup specification are adjusted
accordingly, you will get the following warning message when
saving the backup specification:

Figure 1-17 Device Block Sizes Are Not Adjusted

Chapter 1 45
Integrating Microsoft SQL Server 7.0/2000 and Data Protector
Performance Tuning

4. Scheduling
The backup schedule depends on how many transactions are done on
the server. Generally, it is not wise to let the transaction log files grow
over a certain limit, which depends on the certain production
database and the size of its transaction log files. These are some
general rules on how to schedule backups for production databases:

• Weekly full backup

• Differential backup daily
• Transaction log backups as needed
You should schedule full and differential backups when the server is
not heavily loaded (nights and weekends), while transaction log
backups should be done several times during the day.
The final decision on scheduling backups must be made according to
the actual database configuration.
For more information, refer to the Microsoft SQL Server Books Online
and HP OpenView Storage Data Protector Administrator’s Guide.

46 Chapter 1
 Integrating Microsoft SQL Server 7.0/2000 and Data Protector
Monitoring a Microsoft SQL Server 7.0/2000 Backup and Restore

Monitoring a Microsoft SQL Server 7.0/2000

Backup and Restore
The Data Protector GUI enables you to monitor current or view previous
backup and restore sessions.
Monitoring is automatically activated when you start a backup or restore
interactively.
See “Running an Interactive Backup” on page 27 and “Before You Call
Support” on page 56 for information about how to use the command line.

Monitoring Current Sessions

To monitor a currently running session using the Data Protector GUI,
proceed as follows:

1. In the Context List, click Monitor.

In the Results Area, all currently running sessions are listed. See
Figure 1-18.
2. Double-click the session you want to monitor.

Figure 1-18 Monitoring a Current Session

Clearing Sessions To remove all completed or aborted sessions from the Results Area of the
Monitor context, proceed as follows:

1. In the Scoping Pane, click Current Sessions.

2. In the Actions menu, select Clear Sessions. Or click the Clear
Sessions icon on the toolbar.

Chapter 1 47
 Integrating Microsoft SQL Server 7.0/2000 and Data Protector
Monitoring a Microsoft SQL Server 7.0/2000 Backup and Restore

To remove a particular completed or aborted session from the current

sessions list, right-click the session and select Remove From List.

NOTE All completed or aborted sessions are automatically removed from the
Results Area of the Monitor context if you restart the Data Protector
GUI.

For detailed information on a completed or aborted session, see “Viewing

Previous Sessions”.

Viewing Previous Sessions

To view a previous session using the Data Protector GUI, proceed as
follows:

1. In the Context List, click Internal Database.

2. In the Scoping Pane, expand Sessions to display all the sessions
stored in the IDB.
The sessions are sorted by date. Each session is identified by a session
ID consisting of a date in the YY/MM/DD format and a unique
number.
3. Right-click the session and select Properties to view details on the
session.
4. Click the General, Messages or Media tab to display general
information on the session, session messages, or information on the
media used for this session, respectively. See Figure 1-19.

48 Chapter 1
 Integrating Microsoft SQL Server 7.0/2000 and Data Protector
Monitoring a Microsoft SQL Server 7.0/2000 Backup and Restore

Figure 1-19 Viewing Previous Sessions

Chapter 1 49
Integrating Microsoft SQL Server 7.0/2000 and Data Protector
Troubleshooting

Troubleshooting
This section is divided into the following subsections:

• “Before You Begin” on page 50

• “Configuration Problems” on page 51
• “Backup Problems” on page 53
• “Restore Problems” on page 54
• “Before You Call Support” on page 56

Before You Begin

• Ensure that the latest official Data Protector patches are installed.
Refer to the “Verifying Which Data Protector Patches Are Installed”
section in the HP OpenView Storage Data Protector Installation and
Licensing Guide.
Refer to the HP OpenView Storage Data Protector Software Release
Notes or
http://www.openview.hp.com/products/datapro/spec_0001.html for an
up-to-date list of supported versions, platforms, and other
information.
• Refer to the HP OpenView Storage Data Protector Software Release
Notes for a description of general Data Protector limitations,
problems and workarounds, as well as a list of available Data
Protector patches.
Follow the given procedures to troubleshoot your configuration, backup,
or restore problems. The Data Protector agent displays troubleshooting
messages when a problem occurs. These can be then used to find a
workaround.

50 Chapter 1
 Integrating Microsoft SQL Server 7.0/2000 and Data Protector
Troubleshooting

Configuration Problems
1. If a configuration procedure does not work:

• Check that the Microsoft SQL Server 7.0/2000 services are

running.
• Examine system errors reported in
<Data_Protector_home>\log\debug.log on the Microsoft SQL
Server 7.0/2000, functioning as a Data Protector client.
• Connect to the Microsoft SQL Server 7.0/2000 via Microsoft SQL
Server 7.0/2000 Enterprise Manager using the same login ID as
the one specified in the Data Protector Configuration dialog box.
• Perform a backup of Microsoft SQL Server 7.0/2000 databases
using the Microsoft SQL Server 7.0/2000 Enterprise Manager.
If the backup fails, fix any Microsoft SQL Server 7.0/2000
problems, and then perform a backup using Data Protector.

Using the Data Protector Command Line to Check Configuration

The configuration can also be performed from the command line. Enter
the following string at the <Data_Protector_home>\bin directory on
the Microsoft SQL Server 7.0/2000 system:
sql_bar config -dbuser:<dbuser> -password:<password>
-appsrv:<appsrv> [-instance:<instance name>]
Enter the same information as if using the Data Protector GUI:

• The username and password of the SQL Server 7.0/2000 user who has
permissions to back up and restore the SQL Server backup objects.
• The name of the SQL Server system.
To check configuration using the command line, enter the following
string from the <Data_Protector_home>\bin directory on the
Microsoft SQL Server 7.0/2000 computer:
sql_bar chkconf [-instance:<instance_name>]
If the optional parameter -instance:<instance_name> is not specified,
the default instance is checked.

Chapter 1 51
 Integrating Microsoft SQL Server 7.0/2000 and Data Protector
Troubleshooting

If the integration is not properly configured, the command returns the

following output:
*RETVAL*8523
If you want the information about the existing configuration, enter the
following string:
sql_bar getconf [-instance:<instance_name>]
If the optional parameter -instance:<instance_name> is not specified,
the configuration for the default instance is returned.

What Happens? Once you start the configuration from the command line, the login
information will be written in the <hostname>%<instance name> file in
the <Data_Protector_home>\Config\Server\Integ\Config\MSSQL
directory.
Once you start checking the configuration procedure, the Data Protector
service reads login information from the <hostname>%<instance name>
file on the Data Protector Cell Manager and tries to connect to the server
using this account.

Miscellaneous Problems

Problems • The integration is properly configured and the backup of all

databases fails after a timeout, with an error message similar to the
following:
[Warning] From: [email protected] "MSSQL70" Time:
3/14/2000 8:19:22 PM
Error has occurred while executing SQL statement.
Error message: '<Microsoft SQL-DMO (ODBC SQLState: 42000)> Error
number: bc5
[Microsoft][ODBC SQL Server Driver][SQL Server]Backup or restore
operation terminating abnormally.'
[Critical] From: [email protected] "MSSQL70" Time:
3/14/00 8:19:24 PM
Received ABORT request from SM => aborting.
• The SQL Server's error log contains an entry similar to the following:
2000-03-14 20:19:21.62 kernel
BackupVirtualDeviceSet::Initialize: Open failure on backup
device 'Data_Protector_master'. Operating system error
-2147024891(Access is denied.).

52 Chapter 1
 Integrating Microsoft SQL Server 7.0/2000 and Data Protector
Troubleshooting

• The SQL Server's VDI.LOG file contains an entry similar to the

following:
2000/03/15 13:19:31 pid(2112)
Error at BuildSecurityAttributes: SetSecurityDescriptorDacl
Status Code: 1338, x53A Explanation: The security descriptor
structure is invalid.

Cause The SQL Server service and the Data Protector Inet service are
running under different accounts. The SQL Server 7.0/2000 integration
cannot access the SQL Server's data for backup due to security problems.

Solution Restart the Data Protector Inet service under the same account as
the SQL Server service is running.

Backup Problems
1. If a backup does not work:

• Verify the configuration file to check if the Cell Manager is

correctly set on the Microsoft SQL Server 7.0/2000 that is
functioning as a Data Protector client.

• Check that the Microsoft SQL Server 7.0/2000 services are

running.
• Check that sql_bar.exe is installed on the system.
• Examine system errors reported in
<Data_Protector_home>\log\debug.log on the Microsoft SQL
Server 7.0/2000 system.
Check also the errorlog and VDI.log files in the
<MSSQL7.0/2000>\log directory on the server system.
• Perform a backup of Microsoft SQL Server 7.0/2000 databases
using the Microsoft SQL Server 7.0/2000 Enterprise Manager.
If the backup fails, fix the Microsoft SQL Server 7.0/2000 problems
and perform a backup using Data Protector.
2. If during the creation of a backup specification you do not see the
instance of the Microsoft SQL Server 2000 as the application
database, enter the instance name by yourself. When the “not-named
instance” is not displayed, the DEFAULT string must be inserted as an
application database.

Chapter 1 53
 Integrating Microsoft SQL Server 7.0/2000 and Data Protector
Troubleshooting

3. When performing a backup, Microsoft SQL Server 7.0/2000 reports

that the database backup cannot take place because of inappropriate
user rights.
If the Data Protector Manager (and sql_bar.exe) reports that the
integration is properly configured, verify that the Microsoft SQL
Server 7.0/2000 user has appropriate rights to access the databases
that cannot be backed up.
It is recommended that the Microsoft SQL Server 7.0/2000 system
administrator (sa) configure the Data Protector Microsoft SQL Server
7.0/2000 integration.

Backup Hangs if Concurrency Is Set to More Than One and One

of the Devices Fails

Problem Backup of a Microsoft SQL Server can hang if Disk Agent concurrency is
set to more than one and one of the devices fails during backup or is not
started at all, for example because of a medium error.

Action Set the device concurrency to one or replace the invalid media.

Restore Problems
• If a restore does not work:

— Check whether a filesystem backup of the problematic client

works. It is much easier to troubleshoot a filesystem backup.
— Check that the Microsoft SQL Server 7.0/2000 services are
running.
— Check that sql_bar.exe is installed on the system.
— Examine the system errors reported in
<Data_Protector_home>\log\debug.log on the Microsoft SQL
Server 7.0/2000 that is functioning as a Data Protector client.
Check also the errorlog and VDI.log files in the
<MSSQL7.0/2000>\log directory on the same system.

54 Chapter 1
 Integrating Microsoft SQL Server 7.0/2000 and Data Protector
Troubleshooting

• The following error has occurred when executing an SQL statement:

Error message: “Microsoft SQL-DMO (ODBC SQLState:
01000)?15[152:5] 1646 [Microsoft][ODBC SQL Serevr Driver][SQL
Server]The master database has been successfully restored.
Shutting down SQL Server.[Microsoft][ODBC SQL Server Driver][SQL
Server]SQL Server is terminating this process.”
It is an expected behavior when the master database is restored in a
single user mode, so this message should not be treated as an error.

A Restore from an Object Copy Hangs.

Problem A 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, perform the
following steps:

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

search for all objects belonging to the same 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.

Database is Left in Unrecovered State After the “Invalid value

specified for STOPAT parameter” Message is Reported in the
Data Protector Monitor

Problem If the Invalid value specified for STOPAT parameter Message is

Reported in the Data Protector Monitor, the database remains in the
unrecovered state as if the RESTORE LOG operation was run with the
Leave the database non-operational option.

Chapter 1 55
 Integrating Microsoft SQL Server 7.0/2000 and Data Protector
Troubleshooting

Action The database can be recovered to the latest point in time by using the
Microsoft SQL Query Analyzer. To recover the database, run the
following T-SQL command:
RESTORE DATABASE <database_name> WITH RECOVERY
After the database is recovered, additional transaction logs cannot be
applied.

Restoring to Another Client

Problem You want to perform a restore of the Microsoft SQL Server 7.0/2000
database to another client in the Data Protector cell not configured to use
with the Microsoft SQL Server 7.0/2000, but the restore does not work.

Action Create the configuration file by configuring the Microsoft SQL 7.0/2000
integration on this client. See “Configuring the Integration” on page 14.

Database Left in Unrecovered State After the Restore Session

Completed Successfully

Problem If you set the time for the Stop at restore option beyond the end of the
RESTORE LOG operation, the database remains in the unrecovered state
as if the RESTORE LOG operation was run with the Leave the database
non-operational option.

Action The database can be recovered to the latest point in time by using the
Microsoft SQL Query Analyzer. To recover the database, run the
following T-SQL command:
RESTORE DATABASE <database_name> WITH RECOVERY
After the database is recovered, additional transaction logs cannot be
applied.

Before You Call Support

If you have performed all the troubleshooting procedures without solving
your problem, you should gather the following information for Data
Protector support before you make a call:

1. Provide details about your hardware and software configuration,

including the official patches you use, the Microsoft SQL Server
version, the SP, the Windows version and the SP.

56 Chapter 1
 Integrating Microsoft SQL Server 7.0/2000 and Data Protector
Troubleshooting

2. Provide a detailed description of the action you failed to perform. If

you had backup problems, attach the backup specification.
3. Provide the information from the following files:

• <Data_Protector_home>\log\debug.log
• <MSSQL7.0/2000>\log\errorlog
• <MSSQL7.0/2000>\log\vdi.log
Copy the session output into a file.

Chapter 1 57
Integrating Microsoft SQL Server 7.0/2000 and Data Protector
Troubleshooting

58 Chapter 1
2 Integrating Microsoft Exchange
Server 5.x and Data Protector

Chapter 2 59
Integrating Microsoft Exchange Server 5.x and Data Protector
In This Chapter

In This Chapter
This chapter explains how to configure and use the Data Protector
Microsoft Exchange 5.x integration.
The chapter is organized into the following sections:

“Overview” on page 61
“Prerequisites and Limitations” on page 63
“Integration Concept” on page 64
“Configuring the Integration” on page 68
“Backing Up Microsoft Exchange Server 5.x” on page 78
“Restoring a Microsoft Exchange 5.x Object” on page 81
“Performance Tuning” on page 90
“Monitoring a Microsoft Exchange 5.x Backup and Restore” on
page 91
“Troubleshooting” on page 94

60 Chapter 2
 Integrating Microsoft Exchange Server 5.x and Data Protector
Overview

Overview
Data Protector offers online backup of your Microsoft Exchange Server
5.x. The online backup concept is widely accepted. It addresses the
business requirements for high application availability better than the
offline backup concept.
An offline filesystem backup can also be performed. This can be
implemented by configuring pre-exec commands to shut down the
database before the backup, and post-exec commands to start up the
database after the backup.
Using the Data Protector Microsoft Exchange Server integration, you
can perform online backups and restores of single mailboxes located on a
MS Exchange Server system. For more information on configuring,
backing up, and restoring single mailboxes, see Chapter 4, “Integrating
Microsoft Exchange Single Mailbox and Data Protector,” on page 135.

Advantages Using Data Protector together with the Microsoft Exchange Server 5.x
offers several advantages over using the Microsoft Exchange Server 5.x
alone:

• Central Management for all backup operations

The administrator can manage backup operations from a central
point.
• Media Management
Data Protector has an advanced media management system, which
allows users to monitor media usage and set protection for stored
data, as well as organize and manage devices in media pools.
• Backup Management
Backed up data can be duplicated during or after the backup to
increase fault tolerance of backups, to improve data security and
availability, or for vaulting purposes.
• Scheduling
Data Protector has a scheduler that allows the administrator to
automate backups to run periodically. Using the Data Protector
Scheduler, one can configure the backups to run unattended, at
specified times, as long as the devices and media are properly set.

Chapter 2 61
Integrating Microsoft Exchange Server 5.x and Data Protector
Overview

• Device Support
Data Protector supports a wide range of devices: files, standalone
drives, very large multiple drive libraries, etc.
• Reporting
Data Protector has reporting capabilities that allow you to receive
information about your backup environment. You can schedule
reports to be issued at a specific time or attached to a predefined set
of events, such as the end of a backup session or a mount request.
• Monitoring
Data Protector has a feature that allows the administrator to monitor
currently running sessions and view finished sessions from any
system that has the Data Protector Manager installed.
All backup sessions are logged in the IDB, which provides the
administrator with the history of activities that can be queried at a
later time.
Refer to the HP OpenView Storage Data Protector Software Release Notes
for more information about the platforms and devices that are supported
by the Data Protector Microsoft Exchange 5.x integration.

62 Chapter 2
 Integrating Microsoft Exchange Server 5.x and Data Protector
Prerequisites and Limitations

Prerequisites and Limitations

Prerequisites • You need a license to use the Data Protector Microsoft Exchange 5.x
integration. Refer to the HP OpenView Storage Data Protector
Installation and Licensing Guide for information about licensing.
• Before you begin, ensure that you have correctly installed and
configured the Microsoft Exchange 5.x and Data Protector systems.
Refer to the:

— HP OpenView Storage Data Protector Software Release Notes for

an up-to-date list of supported versions, platforms, devices,
limitations, and other information.
— HP OpenView Storage Data Protector Installation and Licensing
Guide for instructions on how to install Data Protector on various
architectures and how to install the Data Protector Microsoft
Exchange 5.x integration.
— Microsoft Exchange Server 5.x Books Online for online information
on Microsoft Exchange Server 5.x.

Limitations • On a single node, only one Data Protector Microsoft Exchange 5.x
Agent may run at a certain point of time. You cannot run two or more
backup sessions, two or more restore sessions, or a backup and a
restore session simultaneously. In the Data Protector cell, however,
you can run multiple Exchange 5.x backups (backup of different
Microsoft Exchange Servers 5.x) simultaneously.
• Do not use double quotes (" ") in object-specific pre-exec and post-exec
commands.
It is assumed that you are familiar with the Microsoft Exchange 5.x
database administration and the basic Data Protector functionality.

Chapter 2 63
 Integrating Microsoft Exchange Server 5.x and Data Protector
Integration Concept

Integration Concept
Data Protector integration with the Microsoft Exchange 5.x allows you to
perform online backups of the Microsoft Exchange Server 5.x.
The integration also provides you with such features as library support,
parallel backups, and media management for the backup and restore.
Data Protector backs up online the Microsoft Exchange Server 5.x
Directory Store (DS) and the Information Store (MDB), which are also
referred to as the Microsoft Exchange 5.x backup objects.
The central component of the integration is the Data Protector
exbar.exe executable, which is installed on the Microsoft Exchange
Server 5.x computer and which controls the activities between the
Microsoft Exchange Server 5.x and Data Protector backup and restore
processes.
From the perspective of the Microsoft Exchange Server 5.x, Data
Protector is seen as a media management software. On the other hand,
the Microsoft Exchange Server 5.x is a Data Protector client from Data
Protector Cell Manager’s point of view.

Backup Flow A Data Protector backup session can be started only from the Data
Protector side.
The Data Protector Backup Session Manager reads the backup
specification and starts the exbar.exe on the Microsoft Exchange Server
5.x system.
The exbar.exe reads data from the Microsoft Exchange Server 5.x and
passes it to the Data Protector General Media Agents.
Data Protector can back up a single database using multiple streams.
This is known as the concurrent streaming.
Microsoft Exchange 5.x objects are backed up sequentially one after
another. Each object can be backed up to more than one stream. So you
can back up to 4 devices, for example.

64 Chapter 2
 Integrating Microsoft Exchange Server 5.x and Data Protector
Integration Concept

The concurrency value per backup session equals the number of the
streams started by the exbar.exe, that is the sum of all concurrencies
per individual device defined in the backup specification. The
configuration of streams is designed to optimize the performance of a
backup.
Two backup types supported by Data Protector Microsoft Exchange 5.x
integration are full and incremental. There is only one level of
incremental which refers to the previous full or incremental, whichever
was performed last.
The full backup includes all backup objects specified in the backup
specification regardless of whether they have changed since the last
backup. The incremental backup performs a backup of the objects that
have changed since the last backup.
Backup session messages are sent to the Backup Session Manager,
which then writes the messages and information regarding the
respective session to the IDB.

Restore Flow Using the Data Protector User Interface, you define which objects and
object versions to restore. The Data Protector Restore Session Manager
is invoked, which then starts the exbar.exe and passes the information
about the objects and the backup versions to the backup API. The
General Media Agents are started by the exbar.exe and the data flows
from the media to the target Microsoft Exchange Server 5.x (see Figure
2-1). For optimal performance, use the same number of devices as for a
backup.
Messages from the restore session are sent to the Data Protector Restore
Session Manager, which writes the messages and information regarding
the respective session to the IDB.

Chapter 2 65
 Integrating Microsoft Exchange Server 5.x and Data Protector
Integration Concept

Figure 2-1 Data Protector Microsoft Exchange 5.x Integration Concept

Media Agent Clients

MA
Device
Media Agent Clients
Directory Store exbar.exe
Microsoft Exchange
Server MA
+ Device
Backup API
Cell Manager

Data Protector
Backup
Specification

Information Store
Microsoft Exchange Server SM IDB

control Data Protector

Data Protector
data Microsoft Exchange Server User Interface

Table 2-1 Legend:

SM A Data Protector Session Manager, that can be the Data

Protector Backup Session Manager during backup or the
Data Protector Restore Session Manager during restore.

MA The Data Protector General Media Agent

Information The default message store provider for Microsoft Exchange

Store (MDB) Server 5.x.

Directory A part of the Microsoft Exchange Server 5.x directory, which

Store (DS) contains objects that are the principal means for applications
to find and access services, mailboxes, recipients, public
folders, and other addressable objects within the messaging
system.
The directory consists of two components:

• Directory database
• Directory service agent

66 Chapter 2
 Integrating Microsoft Exchange Server 5.x and Data Protector
Integration Concept

Table 2-1 Legend:

Backup API The Microsoft defined interface that enables data transfer
between Data Protector and Microsoft Exchange Server 5.x.

Chapter 2 67
 Integrating Microsoft Exchange Server 5.x and Data Protector
Configuring the Integration

Configuring the Integration

The configuration of the Data Protector Microsoft Exchange 5.x
integration consists of the following:

1. “Configuring Microsoft Exchange Server 5.x” on page 68

2. “Configuring a Microsoft Exchange Server 5.x Backup” on page 70

Configuring Microsoft Exchange Server 5.x

To configure Microsoft Exchange Server 5.x, you have to switch off the
circular logging in order to enable incremental backups.
Circular logging is a default Microsoft Exchange Server 5.x database
mode, where transaction log files are automatically overwritten, as soon
as the data they contain gets committed to the database.
If turned on, this option reduces disk storage space requirements, but
does not allow you to perform incremental backups.
Proceed as follows to turn the circular logging off:

Cluster-Aware If the application is cluster-aware, switch off the circular logging on all
Clients cluster nodes.

Switching Off the 1. From the Windows desktop on the Microsoft Exchange 5.x computer,
Circular Logging start the Exchange Administrator.

2. Log on to the Microsoft Exchange Server 5.x, open the site, move to
Configuration, Servers, <Server_Name>.

68 Chapter 2
 Integrating Microsoft Exchange Server 5.x and Data Protector
Configuring the Integration

Figure 2-2 Browsing Exchange Server 5.x

3. Right-click the server name to open the advanced tab of the

properties and clear the circular logging for Information Store and
Directory. See Figure 2-3 on page 69.

Figure 2-3 Disabling Circular Logging

Chapter 2 69
 Integrating Microsoft Exchange Server 5.x and Data Protector
Configuring the Integration

Configuring a Microsoft Exchange Server 5.x Backup

Before You Begin It is recommended that you configure and run a test filesystem backup
using Data Protector.
This includes installing a Disk Agent on the Microsoft Exchange Server
5.x. Any device can be used for this test. Configure a standard filesystem
backup which may include one directory only.
By doing this, you will check whether the Microsoft Exchange Server 5.x
client system and the Data Protector Cell Manager can communicate
properly.
In case of problems, this type of backup is much easier to troubleshoot
than the Data Protector Microsoft Exchange Server 5.x integration.
Refer to the HP OpenView Storage Data Protector Administrator’s Guide
for instructions. In case of any difficulties with the filesystem backup, do
not proceed with configuring the integration until you solve them.
To configure a Microsoft Exchange Server 5.x backup, perform the
following steps:

1. Configure the devices you plan to use for a backup. Refer to the online
Help index keyword “configuring devices” for instructions.
2. Configure media pools and media for a backup. Refer to the online
Help index keyword “creating media pools” for instructions.
3. Create a Data Protector Microsoft Exchange Server 5.x backup
specification.

Creating a Backup Specification

To create a Microsoft Exchange Server 5.x backup specification, perform
the following steps:

1. In the HP OpenView Storage Data Protector Manager, switch to

the Backup context.
2. In the Scoping Pane, expand Backup, and then Backup
Specifications. Right-click MS Exchange 5.x Server and click Add
Backup.
3. In the Create New Backup dialog box, select the Blank Microsoft
Exchange Server Backup template. See Figure 2-4.

70 Chapter 2
 Integrating Microsoft Exchange Server 5.x and Data Protector
Configuring the Integration

Figure 2-4 Selecting a Blank Template

Click OK.
4. In the Client drop-down list, select the Microsoft Exchange Server
5.x system. If the application is cluster-aware, select the virtual
server of the Microsoft Exchange Server 5.x resource group.
In the Application database drop-down list, leave the instance
name for Microsoft Exchange Server 5.x that is MSExchange.
Click Next.
5. Select the Microsoft Exchange Server 5.x objects you want to back up.
You can select the Information Store (MDB) and the Directory
Store (DS) object.
The public information store (PUB.EDB), and the private information
store(PRIV.EDB)are backed up if the Information Store (MDB) has
been selected for a backup.

Chapter 2 71
 Integrating Microsoft Exchange Server 5.x and Data Protector
Configuring the Integration

Figure 2-5 Selecting Backup Objects

Click Next.
6. Select the device(s) you want to use for the backup. Click Properties
to set the device concurrency, media pool, and preallocation policy.
For more information on these options, click Help.
You can also specify whether you want to create additional copies
(mirrors) of the backup during the backup session. Specify the desired
number of mirrors by clicking the Add mirror and Remove mirror
buttons. Select separate devices for the backup and for each mirror.
For detailed information on the object mirror functionality, see HP
OpenView Storage Data Protector Administrator’s Guide.

NOTE The recommended maximum backup device concurrency is two for

devices connected directly to the server and one for those connected
remotely to the server.

Click Next.

72 Chapter 2
 Integrating Microsoft Exchange Server 5.x and Data Protector
Configuring the Integration

7. Select the backup options.

For information on Backup Specification Options and Common
Application Options, refer to the online Help.
For information on Application Specific Option, see “The
Microsoft Exchange Server 5.x Specific Backup Options” on page 74
or online Help.
Click Next.
8. Optionally, schedule the backup. For information on scheduler, press
F1.

When scheduling, starting or previewing the backup specification,

select Full or Incr backup type:

• Full: Backs up all selected Microsoft Exchange Server 5.x

databases and Microsoft Exchange Server 5.x transaction logs
even if there are no changes from the previous backup. The
advantage of a full backup is faster and simpler restore (you only
need media from the latest full backup). The disadvantage is that
a full backup takes longer to complete and occupies more space on
media and in the IDB since the same version of a file can be
backed up several times.
• Incr: Backs up only the changes to the selected Microsoft
Exchange Server 5.x databases. If there is no full Microsoft
Exchange Server 5.x backup in the IDB, Data Protector starts a
full backup instead. The advantage of this type of backup is that it
takes less time to complete (it backs up smaller quantities of data)
and occupies less space on media and in the IDB. The
disadvantage is more complicated restore as you usually need all
the media used since the last full backup.
9. Save the backup specification. It is recommended that you save all
Microsoft Exchange Server 5.x backup specifications in the
MSExchange group. See Figure 2-6.

Chapter 2 73
 Integrating Microsoft Exchange Server 5.x and Data Protector
Configuring the Integration

Figure 2-6 Saving a Backup Specification

10. Once saved, the backup specification can be tested by clicking Start
Preview, or started by clicking Start Backup.
See “Testing the Microsoft Exchange 5.x Backup Configuration” on
page 76 for information on testing a backup configuration.
See “Backing Up Microsoft Exchange Server 5.x” on page 78 for
information on starting a backup.

The Microsoft Exchange Server 5.x Specific Backup Options

This section describes the Data Protector Microsoft Exchange Server 5.x
integration specific backup options, which are also known as the
application specific options.
You can access them from the Options property page of a backup
specification. Click the Advanced tab in the Application Specific
Options group box. See Figure 2-7.

74 Chapter 2
 Integrating Microsoft Exchange Server 5.x and Data Protector
Configuring the Integration

Figure 2-7 Application Specific Options

The following options can be selected from this window:

Pre-exec Specifies a command with arguments or script that will
be started on the Microsoft Exchange 5.x client before
the backup starts. The command/script is started by
the Data Protector exbar.exe and must reside in the
<Data_Protector_home>\bin directory. Only the
filename must be provided in the backup specification.
Post-exec Specifies a command with arguments or script that will
be started on the Microsoft Exchange 5.x client after
the backup. The command/script is started by the Data
Protector exbar.exe and must reside in the
<Data_Protector_home>\bin directory. Only the
filename must be provided in the backup specification.
Buffer Size This is the size of the Microsoft Exchange 5.x buffer,
which is used to transfer data to Data Protector. The
default value is equal to number of backup streams
multiplied by 16kB.

Chapter 2 75
 Integrating Microsoft Exchange Server 5.x and Data Protector
Configuring the Integration

For example, if you have two DLT devices defined in a

backup specification, each with a concurrency of two,
then the Default Buffer Size is:
BUFF_SIZE=2*2*16=64kB.

NOTE Note that the Pre-exec and the Post-exec commands have to reside in
the <Data_Protector_home>\bin directory on the Microsoft Exchange
Server 5.x computer.

The application specific options are applied to all backup objects that
have been selected in the backup specification.

Testing the Microsoft Exchange 5.x Backup

Configuration
To check whether a backup specification has been properly configured,
perform the following steps:

1. In the HP OpenView Storage Data Protector Manager, switch to

the Backup context.
2. In the Scoping Pane, expand Backup, and then Backup
Specifications.
Expand MS Exchange 5.x Server and then right-click the backup
specification you want to preview.
3. Click Preview Backup and select the backup type and the network
load. Click OK.
The “Session completed successfully” message is displayed at the
end of the preview session if the test finishes successfully.

What Happens? The given procedure actually tests the backup by performing the
following actions:

1. The Data Protector exbar.exe is started on the Microsoft Exchange

Server 5.x to test all Microsoft Exchange 5.x backup interface calls
needed for a backup. It also checks whether all needed Microsoft
Exchange 5.x services are running.

76 Chapter 2
 Integrating Microsoft Exchange Server 5.x and Data Protector
Configuring the Integration

2. Starting a backup simulation (without data transfers) of the backup

objects in order to:

• Check the communication between the client and the Data

Protector Cell Manager.
• Check if the specified devices are available.
• Check if there are media available in the devices, where backup
data can be written to.

Chapter 2 77
 Integrating Microsoft Exchange Server 5.x and Data Protector
Backing Up Microsoft Exchange Server 5.x

Backing Up Microsoft Exchange Server 5.x

To run an online backup of a Microsoft Exchange 5.x database, use any of
the following methods:

Backup Methods • Schedule the backup of an existing Microsoft Exchange 5.x backup
specification using the Data Protector Scheduler.
• Start an interactive backup of an existing Microsoft Exchange 5.x
backup specification using the Data Protector GUI or the Data
Protector command-line interface.
For information on starting an interactive backup using the Data
Protector command-line interface, refer to the omnib man page.

Scheduling a Backup
Scheduling a backup specification means setting time, date and type of a
backup that will be started unattended once the scheduling options are
defined and saved in the backup specification.
For more information on scheduling, refer to the online Help index
keyword “scheduled backups”.
To schedule a Microsoft Exchange 5.x backup, proceed as follows:

1. In the HP OpenView Storage Data Protector Manager, switch to

the Backup context.
2. In the Scoping Pane, expand Backup, Backup Specifications, and
then MS Exchange 5.x Server.
3. Double-click the backup specification you want to schedule and click
the Schedule tab.
4. In the Schedule page, select a date in the calendar and click Add to
open the Schedule Backup dialog box.
5. Specify Recurring, Time options, Recurring options, and
Session options. See Figure 2-8.
The Incremental backup performs a backup of the transaction log
files that record changes to the database.

78 Chapter 2
 Integrating Microsoft Exchange Server 5.x and Data Protector
Backing Up Microsoft Exchange Server 5.x

The Microsoft Exchange Server 5.x automatically deletes transaction

log files after they have been backed up.

Figure 2-8 Scheduling Backups

Click OK and then Apply to save the changes.

Running an Interactive Backup

An interactive backup can be performed any time after a backup
specification has been created and saved.
To start an interactive backup of a Microsoft Exchange 5.x database,
proceed as follows:

1. In the HP OpenView Storage Data Protector Manager, switch to

the Backup context.
2. In the Scoping Pane, expand Backup, Backup Specifications, and
then MS Exchange 5.x Server.
3. Right-click the backup specification, and then select Start Backup.

Chapter 2 79
Integrating Microsoft Exchange Server 5.x and Data Protector
Backing Up Microsoft Exchange Server 5.x

In the Start Backup dialog box, select the Backup type and Network
load. For information on these options, click Help.
Click OK.

80 Chapter 2
 Integrating Microsoft Exchange Server 5.x and Data Protector
Restoring a Microsoft Exchange 5.x Object

Restoring a Microsoft Exchange 5.x Object

NOTE A Microsoft Exchange 5.x object can only be restored offline.

You can restore a Microsoft Exchange 5.x object using the Data Protector
GUI. The following is a description of the Microsoft Exchange 5.x restore
flow:

Restore Flow • The Data Protector Restore Session Manager starts the exbar.exe
command on the Microsoft Exchange Server 5.x and General Media
Agents on the systems where the backup devices are configured.
• The Data Protector exbar.exe command stops all Microsoft
Exchange 5.x services except the Exchange System Attendant if the
Stop services before restore option is selected in the Data
Protector Manager.
Otherwise, you have to stop the services manually:
Use the Windows desktop to open the Services window. Select all
the Microsoft Exchange 5.x services with the exception of the
Exchange System Attendant, and then click the Stop button. See
Figure 2-9 on page 82.
• General Media Agents read data from the backup devices, and after
send it to exbar.exe which writes the data to disks.
• If the Start services after restore option was selected,
exbar.exe restarts all Microsoft Exchange 5.x services that were
stopped at the beginning of the restore session.
• During the services start-up, the Microsoft Exchange Server 5.x
performs its internal restore procedure, which can be monitored using
the Windows EventLog Viewer.

NOTE Microsoft Exchange 5.x objects are restored offline. Steps two and four
are performed by the Data Protector integration, provided that the above
mentioned options are selected.

Chapter 2 81
 Integrating Microsoft Exchange Server 5.x and Data Protector
Restoring a Microsoft Exchange 5.x Object

Figure 2-9 Stopping the Microsoft Exchange Server 5.x Services:

Once you have taken the Microsoft Exchange Server 5.x offline
(manually or by selecting the corresponding option), proceed as follows to
restore the Microsoft Exchange 5.x backup objects using the Data
Protector GUI:

Restore Procedure 1. In the HP OpenView Storage Data Protector Manager, switch to

the Restore context.
2. In the Scoping Pane, expand Restore Objects, MS Exchange 5.x
Server, and then the name of the client from which you want to
restore.
3. Double-click MS Exchange 5.x Server. In the Source property page,
select either DS or MDB database. Parallel restore of both objects is not
supported.

82 Chapter 2
 Integrating Microsoft Exchange Server 5.x and Data Protector
Restoring a Microsoft Exchange 5.x Object

Figure 2-10 Restore Objects

4. To select a backup version to be restored right-click the object and

select Properties.

Chapter 2 83
 Integrating Microsoft Exchange Server 5.x and Data Protector
Restoring a Microsoft Exchange 5.x Object

Figure 2-11 Selecting a Backup Version

In the Properties for DS or Properties for MDB dialog box, select

the restore version.
Data Protector restores the backup chain. You have to select the
latest version that has to be restored. The latest full and all required
incremental backups will be restored automatically. Do not restore
versions one by one.
5. In the Options property page, select the restore options. See “Restore
Options” on page 88 for details about these options.
6. Click Devices and then Media to select the devices and media to be
used for the restore.
Note that you can use a different device for the restore than the one
used for the backup. Refer to the “Restoring Under Another Device”
section in the HP OpenView Storage Data Protector Administrator’s
Guide for more information on how to perform a restore using
another device.

84 Chapter 2
 Integrating Microsoft Exchange Server 5.x and Data Protector
Restoring a Microsoft Exchange 5.x Object

IMPORTANT If the devices used for the restore are not those used for the backup,
select the same number of devices in the Devices property page as you
used when you backed up the object.

7. Click Restore MS Exchange and then Next to select the Report

level and Network load.
Click Finish to start the restore session.

Restoring from the Latest Online Backup

This procedure allows the restore of the Microsoft Exchange 5.x database
to the point of failure using existing log files.

Prerequisites • You have an online backup with databases and log files from number
M to N (for example, edb000110.log to edb000120.log)
• You have log files at the time of the crash from number N+1 to K and
the edb.log file (for example, edb000121.log to edb000135.log).

Procedure 1. Restore from an online backup without deleting existing logs so that
you get databases from the time of the backup, logs from number M to
N, and existing logs. You should have the following files in the
directory:

• edbM.log to edbK.log (edb000110.log to edb000135.log in our

example) without any missing log file
• edb.log file from the time of failure
2. Start the Microsoft Exchange Server 5.x Information Store.

Restore Options
The following restore options are specific to the Data Protector Microsoft
Exchange 5.x integration (See also Figure “Restore Options” on page 88):
Restore to another client (supported for the Information Store
only)
By default, the target Data Protector Microsoft
Exchange 5.x client is the Microsoft Exchange Server
5.x from which the application data was backed up.

Chapter 2 85
 Integrating Microsoft Exchange Server 5.x and Data Protector
Restoring a Microsoft Exchange 5.x Object

Nevertheless, the Information Store can be restored to

a Microsoft Exchange Server 5.x other than the one the
backup was made from. The new target Microsoft
Exchange Server 5.x has to be also in the Data
Protector cell. This provides a method to recover
individual items (messages or folders) from the backup
without restoring them over Microsoft Exchange
Server 5.x items that are in use. You may use this
option as a last-resort method for retrieving items such
as mailboxes.

NOTE It is recommended that this option is used with the Delete existing
log files option (see below for a description).

Follow the steps below to restore the Information Store to another client:

1. Install the Microsoft Exchange Server 5.x on a separate system, and

create the same structure and site names as on the Microsoft
Exchange Server 5.x the backup of which is to be restored.
The new system name can be different.
2. Install the Data Protector Microsoft Exchange 5.x integration on this
system.
3. Restore the Information Store to the new Microsoft Exchange Server
5.x. See “Restoring a Microsoft Exchange 5.x Object” on page 81 for
details.
Delete existing log files
Erases all existing log files pertaining to the directory
or the Information Store that is being restored. Use
this option when the data is being restored to a
different system or when you want your restore to be
consistent to a point-in-time.
It is recommend that you do not delete log files when
you restore the latest backup on the system from which
the backup was made.
Stop services before restore
Data Protector stops all Microsoft Exchange 5.x
services except the Exchange System Attendant.

86 Chapter 2
 Integrating Microsoft Exchange Server 5.x and Data Protector
Restoring a Microsoft Exchange 5.x Object

If you do not use this option, you have to stop the

services manually before the restore.
Start services after restore
Data Protector starts the Microsoft Exchange 5.x
services that were stopped using the Stop services
before restore option.
If you do not use this option, you have to start these
services manually after the restore. The exbar.exe
starts only the services that were stopped before the
restore session using the Data Protector Manager Stop
services before restore option.
Restore actions (supported for the Information Store only)
The Restore both databases option restores both the
public and the private parts of the Information Store.
The Restore private database only option restores
only the private part of the Information Store.
The Restore public database only option restores
only the public part of the Information Store.

Chapter 2 87
 Integrating Microsoft Exchange Server 5.x and Data Protector
Restoring a Microsoft Exchange 5.x Object

Figure 2-12 Restore Options

Disaster Recovery
Disaster recovery is a very complex process where the following products
from several vendors participate:

• main system hardware

• special disk subsystem (such as raid arrays)

• interface cards

• drivers for various hardware components

• operating system

• backup/restore application

• online database application

This implies that disaster recovery is a shared responsibility among ALL
vendors involved.

88 Chapter 2
 Integrating Microsoft Exchange Server 5.x and Data Protector
Restoring a Microsoft Exchange 5.x Object

Disclaimer The information provided here is to be seen as guidelines. By no means

does the presented information imply that Data Protector guarantees the
overall recovery to a running application like database.
Refer to the HP OpenView Storage Data Protector Administrator’s Guide
for details on Data Protector disaster recovery.
To recover your Microsoft Exchange Server 5.x, follow the steps below:

1. Use the Data Protector disaster recovery to recover the Microsoft

Exchange Server 5.x.
2. If your Microsoft Exchange Server 5.x cannot be restored from a
filesystem backup, proceed as follows:

a. Install the Microsoft Exchange Server 5.x and create the same
structure for the new Microsoft Exchange Server 5.x and name it
the same as the original.
b. Install the Microsoft Exchange Service Pack.
3. Restore the Directory from the last backup of this Microsoft Exchange
Server 5.x.
4. Restore the Information Store from the last backup.
5. Run the Microsoft Exchange DS/MDB consistency adjustment tool.
Refer to the Microsoft Exchange Server 5.x Books Online for more
information.

Chapter 2 89
Integrating Microsoft Exchange Server 5.x and Data Protector
Performance Tuning

Performance Tuning
Performance tuning means customizing your Microsoft Exchange Server
5.x and Data Protector in the way that they achieve better backup and
restore results. You can improve the backup or restore performance of
your Microsoft Exchange Server 5.x by following these guidelines:

• Increase the Microsoft Exchange Server 5.x buffer size on the high
performance systems. The recommended values range from 512 KB to
2 MB. See “The Microsoft Exchange Server 5.x Specific Backup
Options” on page 74 for information on how to modify the buffer size.
• Calculate the number of devices to use in parallel.
The main consideration is to set the number of devices to match the
bandwidth of the incoming data stream and to identify the bottleneck.
This can be either the network, if the devices are connected to remote
computers, or the server computer itself, if the devices are connected
locally.
As the bandwidths of networks usually vary between ~1 MB/s (10
Mbit Ethernet), ~10 MB/s (100 Mbit Ethernet) and the actual
throughput is usually lower, you will not need more than one fast
device, such as a DLT 7000 for a remote backup.
Otherwise, determine the maximum backup capabilities of the
Microsoft Exchange Server 5.x machine by performing a backup to a
few null file devices on the local server and select the number of
devices that best fit the measured performance.

90 Chapter 2
 Integrating Microsoft Exchange Server 5.x and Data Protector
Monitoring a Microsoft Exchange 5.x Backup and Restore

Monitoring a Microsoft Exchange 5.x Backup

and Restore
The Data Protector Manager enables you to monitor the current or view
previous backup and restore sessions.
Monitoring is automatically activated when you start a backup or restore
session interactively.

Monitoring Current Sessions

To monitor a currently running session using the Data Protector GUI,
proceed as follows:

1. In the Context List, click Monitor.

In the Results Area, all currently running sessions are listed.
2. Double-click the session you want to monitor. See Figure 2-13.

Figure 2-13 Monitoring a Current Session

Clearing Sessions To remove all completed or aborted sessions from the Results Area of the
Monitor context, proceed as follows:

1. In the Scoping Pane, click Current Sessions.

2. In the Actions menu, select Clear Sessions. Or click the Clear
Sessions icon on the toolbar.
To remove a particular completed or aborted session from the current
sessions list, right-click the session and select Remove From List.

Chapter 2 91
 Integrating Microsoft Exchange Server 5.x and Data Protector
Monitoring a Microsoft Exchange 5.x Backup and Restore

NOTE All completed or aborted sessions are automatically removed from the
Results Area of the Monitor context if you restart the Data Protector
GUI.

For detailed information on a completed or aborted session, see “Viewing

Previous Sessions”.

Viewing Previous Sessions

To view a previous session using the Data Protector GUI, proceed as
follows:

1. In the Context List, click Internal Database.

2. In the Scoping Pane, expand Sessions to display all the sessions
stored in the IDB.
The sessions are sorted by date. Each session is identified by a
session ID consisting of a date in the YY/MM/DD format and a unique
number.
3. Right-click the session and select Properties to view details on the
session.
4. Click the General, Messages or Media tab to display general
information on the session, session messages, or information on the
media used for this session, respectively. See Figure 2-14.

92 Chapter 2
 Integrating Microsoft Exchange Server 5.x and Data Protector
Monitoring a Microsoft Exchange 5.x Backup and Restore

Figure 2-14 Viewing a Previous Session

Chapter 2 93
Integrating Microsoft Exchange Server 5.x and Data Protector
Troubleshooting

Troubleshooting
This section is divided into the following subsections:

• General troubleshooting
• Backup problems
• Restore problems

General Troubleshooting
• Ensure that the latest official Data Protector patches are installed.
Refer to the “Verifying Which Data Protector Patches Are Installed”
section in the HP OpenView Storage Data Protector Installation and
Licensing Guide.
Refer to the HP OpenView Storage Data Protector Software Release
Notes or
http://www.openview.hp.com/products/datapro/spec_0001.html for an
up-to-date list of supported versions, platforms, and other
information.
• Refer to the HP OpenView Storage Data Protector Software Release
Notes for a description of general Data Protector limitations,
problems and workarounds, as well as the list of related Data
Protector patches.

Backup Problems
1. Backup does not work:

• To perform backup of the Directory Store, you have to check if the

following services are running:

✓ Microsoft Exchange Directory

✓ Microsoft Exchange System Attendant
• To perform backup of the Information Store, you have to check if
the following services are running:

✓ Microsoft Exchange Directory

94 Chapter 2
 Integrating Microsoft Exchange Server 5.x and Data Protector
Troubleshooting

✓ Microsoft Exchange System Attendant

✓ Microsoft Exchange Information Store
• To check if the Cell Manager is correctly set on the Microsoft
Exchange 5.x client, check the Windows registry entry
(\HKEY_LOCAL_MACHINE\Software\Hewlett-Packard\OpenView
\OmniBack II\Site).
• Provided that the Microsoft Exchange Server 5.x is running, but
you cannot connect it, proceed as follows:

a. Edit the following registry key on the Microsoft Exchange 5.x

client:
HKEY_LOCAL_MACHINE\Software\Hewlett-Packard\OpenVie
w\OmniBack II\Agents\Exchange\
b. Edit the ServerName value and enter the Microsoft Exchange
Server 5.x’s NetBIOS computer name.
• Check if the filesystem backup of the problematic client works.
• Start the Data Protector test backup utility. See “Testing the
Microsoft Exchange 5.x Backup Configuration” on page 76 for
instructions.

— If Microsoft Exchange Server 5.x part of the test fails, proceed

as follows:
Check the Microsoft Exchange Server 5.x log error messages
using the Event Viewer utility.
Examine system errors reported in
<Data_Protector_home>\log\debug.log on the Data
Protector Microsoft Exchange 5.x client system
— If the Data Protector part of the test backup utility fails,
proceed as follows:
Examine system errors reported in
<Data_Protector_home>\log\debug.log on the Data
Protector Microsoft Exchange 5.x client system.
— If the test succeeds, start a backup of the Data Protector
Microsoft Exchange 5.x client system using the Windows
backup utility.

Chapter 2 95
 Integrating Microsoft Exchange Server 5.x and Data Protector
Troubleshooting

If this backup succeeds, the problem is probably insufficient

amount of memory, disk space, or other OS resources of the
client running the Data Protector User Interface.
• To test the Data Protector internal data transfer, restart the Data
Protector Inet service as an administrator and start the test
backup utility as follows:
<Data_Protector_home>\utilns\testbar -type:MSExchange
-bar:<backup_specification_name> -perform:backup
2. Backup hangs because of a large buffer.
Stop the running exbar.exe tasks, reduce the buffer size and start
the backup.
3. The Data Protector Manager displays misleading error messages.
In case of system or the Microsoft Exchange Server 5.x errors,
exbar.exe displays messages generated by the Microsoft Exchange
Server 5.x or the Windows operating system. Some of these messages
are erroneous.

Command Line A backup session can be tested using the Data Protector CLI, where the
backup options have to be specified as the exbar.exe command-line
options.
The command has to be started from the
<Data_Protector_home>\bin directory on a Data Protector Microsoft
Exchange 5.x client system:
exbar [-appsrv:<Microsoft_Exchange_Server>]-perform:backup
-base:<Microsoft_Exchange_backup_object>
[-type:<backup_type>]-bar:<backup_specification_name> -n
<concurrency> [-buffer:
<buffer_size>][-pre:<Pre_exec_command>][-post:<Post_exec_comm
and>]
The <Microsoft_Exchange_backup_object> can be MDB or DS and
the <backup type> can be full or incremental. The [-start][-stop]
options are related to the Microsoft Exchange 5.x services that have to be
stopped before or started after a restore session.

96 Chapter 2
 Integrating Microsoft Exchange Server 5.x and Data Protector
Troubleshooting

NOTE The -bar option is mandatory since exbar.exe reads the device options
from the backup specification as opposed to other options in the
respective backup specification, which are ignored. The command-line
options are used instead.

An interactive backup of a Microsoft Exchange 5.x backup object can also

be started using the omnib command on any client in the Data Protector
cell, provided that the respective client has the Data Protector User
Interface installed. The command has to be started from the
<Data_Protector_home>\bin directory:
omnib -msexchange_list <backup_specification_name> [-barmode
Exchangemode] [list_options]
List_options can be one of the following:

-protect {none | weeks n | days n | until date | permanent}

-load {low | medium| high}
-crc
-no_monitor
date = YYYY/MM/DD
Exchangemode options can be one of the following:

• full, for a full backup

• incr, for an incremental backup

Example The following is an example of an incremental backup using the omnib

command of a backup specification RONA
omnib -msexchange_list RONA -barmode incr

Restore Problems
1. Restore does not work:

• Check whether the filesystem restore of the problematic client

works. It is much easier to troubleshoot a filesystem restore.
• Check that the Microsoft Exchange System Attendant Service is
running.

Chapter 2 97
Integrating Microsoft Exchange Server 5.x and Data Protector
Troubleshooting

• Check whether the Data Protector Microsoft Exchange Agent

ExBAR is installed on the system.
• To restore to another system, ensure that the Microsoft Exchange
Server 5.x is installed and that it has the same organization and
site names as the Server the backup of which is to be restored.
• Examine system errors reported in
<Data_Protector_home>\log\debug.log on the Microsoft
Exchange Server 5.x client.
2. The Start Services After Restore option is used and a timeout
error message is returned as services are being started.
It is very likely that the default timeout is too small.
You have to manually restart the services that were not started and
increase the timeout (in seconds) in the registry:
HKEY_LOCAL_MACHINE\SOFTWARE\Hewlett-Packard\OpenView\
OmniBackII\Agents\Exchange\SvcStartTimeout.
This timeout will be used from this on.
3. You cannot start the Microsoft Exchange Directory and/or
Information Service after the restore.
Perform the following steps and restart the services after each step:

a. Check the messages in the Event Viewer to see if any log file has
failed. Delete the first failed log file and all subsequent log files.
b. Delete the tmp.edb file in Directory Database directory and/or
temp.edb file in the Information Store directory.
c. Delete *.chk files and all old *.log files in the Directory
Transaction Logs directory or the Information Store Transaction
Logs directory. Refer to the Microsoft Exchange Administrator for
the locations of the files.
d. Delete all data in the directories and perform the restore once
again.
4. Data Protector Manager displays misleading error messages.
In case of the system or the Microsoft Exchange Server 5.x errors,
exbar.exe displays messages generated by the Microsoft Exchange
Server 5.x or the Windows operating system. Some of these messages
are erroneous.

98 Chapter 2
 Integrating Microsoft Exchange Server 5.x and Data Protector
Troubleshooting

Command Line A restore session can be tested using the Data Protector exbar
command. The command has to be started from the
<Data_Protector_home>\bin directory on a Data Protector
Microsoft Exchange Server 5.x system:
exbar [-appsrv:<Microsoft_Exchange_Server>]-perform:restore
-base:<Microsoft_Exchange_backup_object>
[-versionmdb:<version_string>][-versionds:<version_string>]
[-start][-stop][-restorefrom:<Original_Microsoft_Exchange_Serve
r>]
The <Microsoft_Exchange_backup_object> can be MDB or DS and
the <version string> has to be specified as it is recorded in the IDB,
otherwise the last version will be restored. The [-start] [-stop]
options are related to the Microsoft Exchange 5.x services that have
to be stopped before or started after a restore session.

Example To restore the Information Store that was backed up on ‘1999/09/23’,

on the Microsoft Exchange 5.x client named my.exchange.server to
the computer where you are running this command, and stop the
Microsoft Exchange 5.x services on the target computer before the
restore, type the following string at the command line:
exbar -perform:restore -base:MDB -versionmdb:1999/09/23-0001
-stop -restorefrom:my.exchange.server
An interactive backup of a Microsoft Exchange 5.x backup object can
also be started from the command line, using the omnir command
from any client in the Data Protector cell, provided that the
respective client has the Data Protector User Interface installed.
The command is started from the <Data_Protector_home>\bin
directory on a Data Protector client system configured in the same
cell as the original and the target Microsoft Exchange 5.x client
system.
omnir -exchange -barhost <Microsoft_Exchange_Server>
[-destination <Other_Microsoft_Exchange_Server>] -base
{MDB|DS}[-session <Session_ID>][-start][-stop]

Before You Call If you have performed the troubleshooting procedures without solving
Support your problem, you should gather the following information for the
Data Protector support before you make a call.

a. Provide details about your hardware and software configuration,

including official patches you use.

Chapter 2 99
Integrating Microsoft Exchange Server 5.x and Data Protector
Troubleshooting

b. Provide a detailed description about the action you failed to

perform. If you have backup problems, attach the backup
specification.
c. Provide the information from the
<Data_Protector_home>\log\debug.log.
Describe what happened after the failure.
d. Copy the session output to a file.

100 Chapter 2
3 Integrating Microsoft Exchange
Server 2000/2003 and Data
Protector

Chapter 3 101
Integrating Microsoft Exchange Server 2000/2003 and Data Protector
In This Chapter

In This Chapter
This chapter explains how to configure and use the Data Protector
Microsoft Exchange integration.
The chapter is organized into the following sections:

“Overview” on page 103

“Prerequisites and Limitations” on page 106
“Integration Concept” on page 107
“Configuring the Integration” on page 110
“Backing Up Microsoft Exchange Server” on page 118
“Restoring a Microsoft Exchange Server Database” on page 121
“Troubleshooting” on page 130

102 Chapter 3
 Integrating Microsoft Exchange Server 2000/2003 and Data Protector
Overview

Overview
The Data Protector integration with Microsoft Exchange enables you to
perform online backup of Microsoft Exchange Server.

Extensible Storage Microsoft Exchange Server uses a database technology called

Engine (ESE 98) Extensible Storage Engine (ESE 98) as a storage system for
information exchange.
Microsoft Exchange Server uses a common Application Programming
Interface (API) that provides a unified interface to back up and restore
all data that is written to any instance of the ESE database present on
the system.
Using new functionality of Exchange Server, you can configure multiple
databases for each server. Databases are grouped into storage groups.
For each storage group a database server instance is running. Up to 4
storage groups and 5 databases per storage group are supported, so that
up to 20 databases for each server or cluster can be configured. Each
storage group can only run one backup at a time, so that databases
within a storage group can only be backed up sequentially. Storage
groups can be backed up in parallel.
There are two kinds of databases: mailbox stores and public folder stores.
The service that is responsible for storage management is called the
Information Store. The database that permits compatibility with
Exchange 5.5 by emulating an Exchange 5.5 directory service is called
the Site Replication Service. The database that provides security
encryption services is called the Key Management Service.
For other information about Microsoft Exchange Server, refer to the
Microsoft Exchange Server 2000/2003 Books Online.
Using the Data Protector Microsoft Exchange Server integration, you
can perform online backups and restores of single mailboxes located on a
Microsoft Exchange Server system. For more information on configuring,
backing up, and restoring single mailboxes, see Chapter 4, “Integrating
Microsoft Exchange Single Mailbox and Data Protector,” on page 135.

Chapter 3 103
 Integrating Microsoft Exchange Server 2000/2003 and Data Protector
Overview

Advantages Integrating Data Protector with Microsoft Exchange Server offers

several advantages over using the Windows backup utility with support
for Exchange Server:

• Central Management for all backup operations

The administrator can manage backup operations from a central
point.
• Backup Management
Backed up data can be duplicated during or after the backup to
increase fault tolerance of backups, to improve data security and
availability, or for vaulting purposes.
• Media Management
Data Protector has an advanced media management system, which
allows users to monitor media usage and set protection for stored
data, as well as organize and manage devices in media pools.
• Scheduling
Data Protector has a scheduler that allows the administrator to
automate backups to run periodically. Using the Data Protector
Scheduler, you can configure the backups to run unattended, at
specified times, if the devices and media are set properly.
• Device Support
Data Protector supports a wide range of devices: files, standalone
drives, very large multiple drive libraries, etc.
• Reporting
Data Protector has reporting capabilities that allow you to receive
information about your backup environment. You can schedule
reports to be issued at a specific time or attached to a predefined set
of events, such as the end of a backup session or a mount request.
• Monitoring
Data Protector has a feature that allows the administrator to monitor
currently running sessions and view finished sessions from any
system that has the Data Protector User Interface installed.
All backup sessions are logged in the IDB, which provides the
administrator with a history of activities that can be queried later.

104 Chapter 3
 Integrating Microsoft Exchange Server 2000/2003 and Data Protector
Overview

Refer to the HP OpenView Storage Data Protector Software Release Notes

for more information about supported platforms and devices.

Chapter 3 105
Integrating Microsoft Exchange Server 2000/2003 and Data Protector
Prerequisites and Limitations

Prerequisites and Limitations

• You need a license to use the Data Protector Microsoft Exchange
integration. Refer to the HP OpenView Storage Data Protector
Installation and Licensing Guide for information about licensing.
• Before you begin, make sure that you have correctly installed and
configured the Microsoft Exchange and Data Protector systems. Refer
to the:

— HP OpenView Storage Data Protector Software Release Notes for

an up-to-date list of supported versions, platforms, devices,
limitations, and other information.
— HP OpenView Storage Data Protector Installation and Licensing
Guide for instructions on how to install Data Protector on various
architectures and how to install the Data Protector Microsoft
Exchange Server 2000/2003 integration.
— Microsoft Exchange Server 2000/2003 Books Online for online
information on Microsoft Exchange Server.
• Do not use double quotes (" ") in object-specific pre-exec and post-exec
commands.

• Preview is not possible for Exchange Server backup and restore

sessions.
It is assumed that you are familiar with the Microsoft Exchange
database administration and the basic Data Protector functionality.

106 Chapter 3
 Integrating Microsoft Exchange Server 2000/2003 and Data Protector
Integration Concept

Integration Concept
The central component of the Data Protector Microsoft Exchange
integration is the Data Protector ese_bar.exe executable, which is
installed on the Microsoft Exchange Server system and which controls
the activities between Microsoft Exchange Server and Data Protector
backup and restore processes.
From the perspective of Microsoft Exchange Server, Data Protector is
seen as media management software. On the other hand, Microsoft
Exchange Server is a Data Protector client from the Data Protector Cell
Manager’s point of view.

Backup Flow A Data Protector backup session can be started only from the Data
Protector GUI.
The Data Protector Backup Session Manager reads the backup
specification and starts the ese_bar.exe command on the Microsoft
Exchange Server system.
The ese_bar.exe command reads the data from Microsoft Exchange
Server and passes it to the Data Protector General Media Agents.
Multiple storage groups are backed up in parallel. Multiple databases
within a storage group are backed up sequentially. The maximum
number of devices used in a backup session equals the number of storage
groups you want to back up.
The two types of backup supported by the Data Protector Microsoft
Exchange integration are Full and Incremental.
A full backup selects for a backup the whole database and all log files of a
storage group regardless of whether they have been changed since the
last backup. Incremental backup selects only log files. After a full or
incremental backup, the log files are deleted.
There is only one level of incremental backup, which refers to the
previous full or incremental backup, whichever was performed last.

Restore Flow Using the Data Protector User Interface, you define which objects and
object versions to restore. The Data Protector Restore Session Manager
is invoked, which then starts ese_bar.exe and passes the information

Chapter 3 107
 Integrating Microsoft Exchange Server 2000/2003 and Data Protector
Integration Concept

about the objects and backup versions on to the backup API. General
Media Agents are started by ese_bar.exe, and the data flows from the
media to the target Microsoft Exchange Server. See Figure 3-1.
Messages from the restore session are sent to the Data Protector Restore
Session Manager, which writes the messages and the information
regarding the respective session to the IDB.

Figure 3-1 Data Protector Microsoft Exchange Integration Concept

Table 3-1 Legend:

SM Data Protector Session Manager, which is a Data

Protector Backup Session Manager during a backup,
or Data Protector Restore Session Manager during a
restore.

MA Data Protector General Media Agent

Backup API The Microsoft defined interface that enables the data
transfer between Data Protector and Microsoft
Exchange Server.

108 Chapter 3
 Integrating Microsoft Exchange Server 2000/2003 and Data Protector
Integration Concept

Table 3-1 Legend:

Storage A collection of mailbox stores and public folder stores

group that share a set of transaction log files. Exchange
manages each storage group using a separate server
process.

Chapter 3 109
 Integrating Microsoft Exchange Server 2000/2003 and Data Protector
Configuring the Integration

Configuring the Integration

Switching Off the Before performing an incremental backup of Microsoft Exchange Server,
Circular Logging make sure that circular logging for storage groups is switched off.
Circular logging is a Microsoft Exchange mode where transaction log
files are automatically overwritten as soon as the data they contain is
transferred to the database(s).
If turned on, this option reduces disk storage space requirements, but
does not allow you to perform incremental backups.

Cluster-Aware If the application is cluster-aware, switch off the circular logging on all
Clients cluster nodes.

Extending the Path The <Exchange_home>\bin directory must be added to the Windows
Environment Path environment variable before any operation is performed.
Variable
To add this directory, proceed as follows:

1. In the Microsoft Windows Explorer, right-click My Computer and

click Properties.
2. In the Properties dialog box, click Advanced and then Environment
Variables.
3. In the Environment Variables dialog box, select Path in the System
Variables list and click Edit.
4. Add <Exchange_home>\bin in the Variable Value text box and click
OK.
See Figure 3-2 on page 111.

Cluster-Aware If the Microsoft Exchange integration is cluster-aware, add this directory

Clients to the Windows Path environment variable on all cluster nodes.

110 Chapter 3
 Integrating Microsoft Exchange Server 2000/2003 and Data Protector
Configuring the Integration

Figure 3-2 Path System Variable

Configuring a Microsoft Exchange Backup

To configure a Microsoft Exchange backup, perform the following three
steps:

1. Configure the devices which you plan to use for a backup. Refer to the
online Help index keyword “configuring devices” for instructions.
2. Configure media pools and media for a backup. Refer to the online
Help index keyword “creating media pools” for instructions.
3. Create a Data Protector Microsoft Exchange Server backup
specification.
See the following section for the procedure on creating a backup
specification.
See the following section for the procedure on how to create a backup
specification.

Chapter 3 111
 Integrating Microsoft Exchange Server 2000/2003 and Data Protector
Configuring the Integration

Creating a Backup Specification

To create a Microsoft Exchange backup specification, perform the
following steps:

1. In the HP OpenView Storage Data Protector Manager, switch to

the Backup context.
2. In the Scoping Pane, expand Backup, and then Backup
Specifications.
3. Right-click MS Exchange 2000/2003 Server and click Add Backup.
4. In the Create New Backup dialog box, select the Blank Microsoft
Exchange 2000/2003 Server Backup template, and click OK.

Figure 3-3 Selecting a Blank Template

5. In the Client drop-down list, select the Microsoft Exchange Server

system. If the application is cluster-aware, select the virtual server of
the Microsoft Exchange Server resource group.

112 Chapter 3
 Integrating Microsoft Exchange Server 2000/2003 and Data Protector
Configuring the Integration

In the Application database drop-down list, select one of the

following:

• Microsoft Exchange Server (Microsoft Information Store)

Select this item to back up the Information Store.
• Microsoft Exchange Server (Microsoft Key Management
Service) (if installed)
Select this item to back up the Key Management Service.
• Microsoft Exchange Server (Microsoft Site Replication
Service) (if installed)
Select this item to back up the Site Replication Service.
Click Next.

Figure 3-4 Specifying a Client Name and Selecting an Application Database

6. Select the Microsoft Exchange Server databases you want to back up.

Chapter 3 113
 Integrating Microsoft Exchange Server 2000/2003 and Data Protector
Configuring the Integration

Figure 3-5 Selecting Backup Objects

Click Next.
7. Select the device(s) you want to use for the backup. Click Properties
to set the device concurrency, media pool, and preallocation policy. For
more information on these options, click Help.
You can also specify whether you want to create additional copies
(mirrors) of the backup during the backup session. Specify the desired
number of mirrors by clicking the Add mirror and Remove mirror
buttons. Select separate devices for the backup and for each mirror.
For detailed information on the object mirror functionality, see HP
OpenView Storage Data Protector Administrator’s Guide.

NOTE The recommended maximum device concurrency is two for devices

connected directly to the server, and one for those connected remotely.

114 Chapter 3
 Integrating Microsoft Exchange Server 2000/2003 and Data Protector
Configuring the Integration

Figure 3-6 Selecting Backup Devices

Click Next to proceed.

8. Select the backup options.
For information on Backup Specification Options and Common
Application Options, refer to the online Help.
For information on Application Specific Option, see “Microsoft
Exchange Specific Backup Options” on page 116 or online Help.
Click Next.
9. Optionally, schedule the backup. For information on scheduler, press
F1.

10. Save the backup specification.

Once saved, the backup specification can be started by clicking Start
Backup.
See “Backing Up Microsoft Exchange Server” on page 118 for
information on starting a backup.

Chapter 3 115
 Integrating Microsoft Exchange Server 2000/2003 and Data Protector
Configuring the Integration

Microsoft Exchange Specific Backup Options

This section describes backup options specific to the Data Protector
Microsoft Exchange integration.
You can access these options from the Options property page of a backup
specification. Click the Advanced button next to the Application
Specific Options. See Figure 3-7.

Figure 3-7 Application Specific Options

The following options can be selected from this window:

Pre-exec Specifies a command with arguments
or a script that will be started on the
Microsoft Exchange client before the
backup starts. The command/script is
started by Data Protector
ese_bar.exe and must reside in
<Data_Protector_home>\bin
directory. Only the filename must be
provided in the backup specification.

116 Chapter 3
 Integrating Microsoft Exchange Server 2000/2003 and Data Protector
Configuring the Integration

Post-exec Specifies a command with arguments

or a script that will be started on the
Microsoft Exchange client after the
backup. The command/script is
started by Data Protector
ese_bar.exe and must reside in
<Data_Protector_home>\bin
directory. Only the filename must be
provided in the backup specification.
Backup buffer size This is the size of the Microsoft
Exchange buffer, which is used for
transferring data to Data Protector.

NOTE Note that the pre-exec and post-exec commands/scripts must reside in
the <Data_Protector_home>\bin directory on the Microsoft Exchange
Server system.

Chapter 3 117
 Integrating Microsoft Exchange Server 2000/2003 and Data Protector
Backing Up Microsoft Exchange Server

Backing Up Microsoft Exchange Server

To run an online backup of a Microsoft Exchange database, use any of
the following methods:

Backup Methods • Schedule the backup of an existing Microsoft Exchange backup

specification using the Data Protector Scheduler.
• Start an interactive backup of an existing Microsoft Exchange backup
specification using the Data Protector GUI or the Data Protector
command-line interface.
For information on starting an interactive backup using the Data
Protector command-line interface, refer to the omnib man page.

Scheduling a Backup
Scheduling a backup specification means setting time, date, and type of a
backup that starts unattended once the scheduling options are defined
and saved in the backup specification.
For more information on scheduling, refer to the online Help index
keyword “scheduled backups”.
To schedule a Microsoft Exchange backup, proceed as follows:

1. In the HP OpenView Storage Data Protector Manager, switch to

the Backup context.
2. In the Scoping Pane, expand Backup, Backup Specifications, and
then Filesystem.
3. Double-click the backup specification you want to schedule and click
the Schedule tab.
4. In the Schedule page, select a date in the calendar and click Add to
open the Schedule Backup dialog box.
5. Specify Recurring, Time options, Recurring options, and
Session options. See Figure 3-8.
The incremental backup performs a backup of the transaction log files
that record changes to the database.

118 Chapter 3
 Integrating Microsoft Exchange Server 2000/2003 and Data Protector
Backing Up Microsoft Exchange Server

Microsoft Exchange Server automatically deletes transaction log files

after they have been backed up.

Figure 3-8 Scheduling Backups

Click OK and then Apply to save the changes.

Running an Interactive Backup

An interactive backup can be performed any time after a backup
specification has been created and saved.
To start an interactive backup of a Microsoft Exchange database, proceed
as follows:

1. In the HP OpenView Storage Data Protector Manager, switch to

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

Chapter 3 119
Integrating Microsoft Exchange Server 2000/2003 and Data Protector
Backing Up Microsoft Exchange Server

3. Right-click the backup specification, and then select Start Backup.

In the Start Backup dialog box, select the Backup type and Network
load. For information on these options, click Help.
Click OK.

120 Chapter 3
 Integrating Microsoft Exchange Server 2000/2003 and Data Protector
Restoring a Microsoft Exchange Server Database

Restoring a Microsoft Exchange Server

Database
You can restore a Microsoft Exchange Server database using the Data
Protector GUI or using the Data Protector CLI.

IMPORTANT The database (store) must be dismounted to perform a restore.

To unmount the database (store), perform the following steps using the
Exchange Administration GUI:

1. In the Exchange System Manager window, right-click the object that

you have backed up (Mailbox Store or Public Folder Store), and
select Dismount Store from the pop-up menu.

Figure 3-9 Unmounting the Database (Store)

2. A warning message appears. Click Yes to continue unmounting.

When the dismounting is completed, you may start a restore session.

Chapter 3 121
 Integrating Microsoft Exchange Server 2000/2003 and Data Protector
Restoring a Microsoft Exchange Server Database

After a hard recovery, databases can be mounted automatically. See

“Restore Options” on page 125 for details.

NOTE Log files for storage groups are saved in the subdirectory of the specified
log directory. See “Restore Options” on page 125 for details.

Restore Using the GUI

Restore Procedure Use the following procedure to restore a Microsoft Exchange Server
database:

1. In the HP OpenView Storage Data Protector Manager, switch to

the Restore context.
2. In the Scoping Pane, expand Restore Objects, MS Exchange
2000/2003 Server, and then the name of the client to which you
want to restore.
3. Select the backed up Microsoft Exchange Server databases you want
to restore.

122 Chapter 3
 Integrating Microsoft Exchange Server 2000/2003 and Data Protector
Restoring a Microsoft Exchange Server Database

Figure 3-10 Restore Objects

To select a backup version to be restored, right-click the object and

select Properties.

IMPORTANT If you are restoring several databases from the same storage group,
make sure that their backup versions are the same. Otherwise, you need
to restore them in separate restore sessions.

Chapter 3 123
 Integrating Microsoft Exchange Server 2000/2003 and Data Protector
Restoring a Microsoft Exchange Server Database

Figure 3-11 Selecting a Backup Version

4. In the Options property page, select the restore options. See “Restore
Options” on page 125 for details about these options.
5. Click Devices and then Media to select the devices, verify device
information, and set priorities of media to be used for the restore.
Note that you can use a different device for the restore than the one
used for the backup. Refer to the “Restoring Under Another Device”
section in the HP OpenView Storage Data Protector Administrator’s
Guide for more information on how to perform a restore using
another device.

IMPORTANT If the devices used for the restore are not those used for the backup,
select the same number of devices in the Devices property page as you
used when you backed up the object.

6. Click Restore MS Exchange 2000/2003 Server. Review your

selection, and then click Finish to start the restore session.

124 Chapter 3
 Integrating Microsoft Exchange Server 2000/2003 and Data Protector
Restoring a Microsoft Exchange Server Database

If the Mount databases after recovery option was not specified for
the restore, mount the dismounted Information Stores using the
Exchange System Manager after the restore has finished.

Restore Options
The following restore options are specific to the Data Protector Microsoft
Exchange integration:
Restore to another client
By default, the target Data Protector Microsoft
Exchange client is the Microsoft Exchange Server from
which the application data was backed up.
Nevertheless, the databases can be restored to a
Microsoft Exchange Server other than the one the
backup was made from. The new target Microsoft
Exchange Server must be a part of the Data Protector
cell and have the MS Exchange Integration software
component installed.
Follow the steps below to restore a database to another client:

1. Install the same version of Microsoft Exchange Server on a separate

system.

NOTE The new system name can be different.

2. On the newly installed Microsoft Exchange Server , install the same

Microsoft Exchange Server Service Pack version(s).
3. On the newly installed Microsoft Exchange Server, create all the
storage groups that existed on the Microsoft Exchange Server that
was backed up. For every storage group, use the same name, the same
location and the same parameters as on the Microsoft Exchange
Server that was backed up.
4. For every newly created storage group, create all the Stores
(databases) that existed in this particular storage group on the
Microsoft Exchange Server that was backed up. When creating a
Store (database), use the same name, the same location and the same
parameters as used for this particular Store (database) on the
Microsoft Exchange Server that was backed up.

Chapter 3 125
Integrating Microsoft Exchange Server 2000/2003 and Data Protector
Restoring a Microsoft Exchange Server Database

5. Install the Data Protector Microsoft Exchange integration on this

system.
6. Restore the database to the new Microsoft Exchange Server.
Directory for temporary log files
Specifying this option, you set the temporary directory
for log files. Data Protector restores the log files to this
directory. Using this directory, Microsoft Exchange
Server then recovers the database - this operation is
referred to as hard recovery.
Last restore set (start recovery)
If this option is set, a hard recovery is performed after
the restore. Use this option if you are restoring the last
set of files. If you do not set this option, you need to
start the recovery manually by running the eseutil
/cc /t utility from the appropriate subdirectory of the
directory for temporary log files.
Mount databases after recovery
If you specify this option, the restored databases will be
automatically mounted after the hard recovery.
Last consistent state
If this option is set, the database will be restored to its
last consistent state. The latest log files, created after
the backup, will be applied to the restored database
during the recovery process.

126 Chapter 3
 Integrating Microsoft Exchange Server 2000/2003 and Data Protector
Restoring a Microsoft Exchange Server Database

Figure 3-12 Restore Options

Recovering an Note that restoring a database to a certain state often requires a

Exchange multiphase restore. This means that multiple versions need to be
Database (Store) restored to retrieve data. The full backup and the transaction log
backups after the full backup have to be restored.

IMPORTANT When you restore from a full database (store) backup, make sure you
selected the database files and the transaction log files from the same
version.

Example Suppose you have the following backup sequence:

F T TFTTTT

Chapter 3 127
 Integrating Microsoft Exchange Server 2000/2003 and Data Protector
Restoring a Microsoft Exchange Server Database

and you want to restore the version marked T, restore all the versions in
<italic>: the first full and transaction log backup, the second
transaction log backup, and the last transaction log backup. The last
transaction log backup has to be restored with the Last restore set (start
recovery) option selected.

Restore Using the CLI

Use the omnir command to restore a Microsoft Exchange Server
database. Refer also to “Restore Options” on page 125 for additional
description of the parameters, limitations and prerequisites. This is the
syntax of the omnir command when used to restore a Microsoft Exchange
Server database:

Syntax omnir -msese

-barhost <ClientName> [-destination <ClientName>]
-appname <full_application_name> -base <DBName>
-session <SessionID>...
-logpath <Path> [-mount] [-last]

Options where:
-msese specifies a Microsoft Exchange Server database for restore
-barhost <ClientName> specifies the system where the Data Protector
Microsoft Exchange client that was backed up is installed
-destination <ClientName> specifies the target client for restore
-appname <full_application_name> Specifies a Microsoft Exchange
Information Store, Site Replication Service or Key Management Service
for the restore. The name of the Store/Service
(<full_application_name>) must be provided in double quotes as
follows:

• for the Information Store: Microsoft Exchange Server(Microsoft

Information Store)
• for the Site Replication Service: Microsoft Exchange Server
(Microsoft Site Replication Service)
• for the Key Management Service: Microsoft Exchange Server
(Microsoft Key Management Service)

128 Chapter 3
 Integrating Microsoft Exchange Server 2000/2003 and Data Protector
Restoring a Microsoft Exchange Server Database

-base <DBName> specifies the Microsoft Exchange store or logs for

restore
-session <SessionID> Specifies the session to be used for restore.
Provide the SessionID of the backup session. In case of object copies, do
not use the copy session ID, but the object's backup ID, which equals the
object's backup session ID.
This option must be set for every -base option specified.
-logpath <Path> By specifying this option, you set the temporary
directory for the Microsoft Exchange log files. Data Protector restores the
log files to this directory. Using this directory, the Microsoft Exchange
then recovers the database - this operation is referred to as hard
recovery.
-mount the restored Microsoft Exchange databases will be automatically
mounted after the soft or hard recovery
-last Hard recovery is performed after the restore of the Microsoft
Exchange Server databases. Use this option if you are restoring the last
set of files. If you do not set this option, start the recovery manually by
running the eseutil /cc /t utility from the directory for temporary
log files. If this option is not specified, soft recovery is performed after the
restore.

Example The Microsoft Information Store with the /First Storage

Group/STORE/Public Folder Store store and /First Storage
Group/LOGS/Logs logs is to be restored to the system called
computer.company.com (where it was backed up), using the Data
Protector session with the session ID 2003/07/07-13. The Microsoft
Exchange log files are to be restored to c:\temp directory, the hard
recovery is to be performed after the restore has finished. The database
is to be mounted after the hard recovery. Run the following command:
omnir -msese -barhost computer.company.com -appname
"Microsoft Exchange Server (Microsoft Information Store)"
-base "/First Storage Group/LOGS/Logs" -session
"2003/07/07-13" -base "/First Storage Group/STORE/Public
Folder Store" -session "2003/07/07-13" -logpath c:\temp
-mount -last
Refer to the omnir man page for more information on usage of the
command.

Chapter 3 129
Integrating Microsoft Exchange Server 2000/2003 and Data Protector
Troubleshooting

Troubleshooting
This section is divided into the following subsections:

• General troubleshooting
• Backup problems
• Restore problems

General Troubleshooting
• Ensure that the latest official Data Protector patches are installed.
Refer to the “Verifying Which Data Protector Patches Are Installed”
section in the HP OpenView Storage Data Protector Installation and
Licensing Guide.
Refer to the HP OpenView Storage Data Protector Software Release
Notes or
http://www.openview.hp.com/products/datapro/spec_0001.html for an
up-to-date list of supported versions, platforms, and other
information.
• Refer to the HP OpenView Storage Data Protector Software Release
Notes for a description of general Data Protector limitations,
problems and workarounds, as well as for a list of related Data
Protector patches.
• Try to run a backup and restore without using Data Protector. Use
Windows Backup to back up and restore the Microsoft Exchange
Server Information Store.
• Check if the following directories exist on the Data Protector Cell
Manager:
<Data_Protector_home>\config\server\barlists\msese
<Data_Protector_home>\config\server\barschedules\msese
• If you perform an incremental backup, ensure that the Enable
circular logging option on the Microsoft Exchange Server is
disabled. You can check this option by starting the Exchange System
manager and selecting Properties from the storage group you are
backing up.

130 Chapter 3
 Integrating Microsoft Exchange Server 2000/2003 and Data Protector
Troubleshooting

• Check if the environment variable Path also includes the

<Exchange_home>\bin directory. For instructions, see “Prerequisites
and Limitations” on page 106.

Backup Problems

Backup Fails

1. Check if the Microsoft Exchange Server services are running. To

perform any kind of backup (MailBox Store, Public Folder Store or
both), the following services must be running:

✓ Microsoft Exchange System Attendant

✓ Microsoft Exchange Information Store
2. Check on the Microsoft Exchange System manager if all the stores
that need to be backed up are mounted.
3. Check if the Cell Manager is correctly set on the Microsoft Exchange
Server client by checking the following registry entry:
HKEY_LOCAL_MACHINE\SOFTWARE\Hewlett-Packard\OpenView\Omni
Back II\Site
Its name and value must be CellServer and "<Cell Manager
hostname>", respectively.
4. Create a Microsoft Exchange Server backup specification to back up
to a null or file device and run the backup. If the backup succeeds, the
problem may be related to the backup devices. Refer to the HP
OpenView Storage Data Protector Administrator’s Guide for
instructions on troubleshooting devices.
5. Check if the filesystem backup of the problematic client works. It is
much easier to troubleshoot a filesystem backup.
6. Examine the errors reported in
<Data_Protector_home>\log\debug.log on the Microsoft
Exchange Server.
7. Examine the errors logged in the Windows Event log.
8. Try to restart the Microsoft Exchange Server and start the backup
again.

Chapter 3 131
Integrating Microsoft Exchange Server 2000/2003 and Data Protector
Troubleshooting

Restore Problems
• Check if the following Microsoft Exchange Server services are
running:

1. Microsoft Exchange System Attendant

2. Microsoft Exchange Information Store
• Using the Exchange System Manager, check whether all the stores
that need to be restored are dismounted.
• If you cannot mount the storage after a successful restore, check if the
LOGS storage on the same storage group has also been restored.
• To restore, for example a Second Storage Group, the
<MS_Exchange_Server_home>\Second Storage Group directory
must exist on your drive.
• Define a directory for temporary log files in the restore context. Check
whether the directory you have specified exists. If it does not, create it
or specify another existing directory.
• Check if the Cell Manager is correctly set on the Microsoft Exchange
Server client by checking the following registry entry:
HKEY_LOCAL_MACHINE\SOFTWARE\Hewlett-Packard\OpenView\Omni
Back II\Site
Its name and value should be CellServer and "<Cell Manager
hostname>", respectively.
• To restore to another system, make sure that the Microsoft Exchange
Server is installed on that system and has the same organization and
site names as the restored server.
• Ensure that the filesystem restore of the problematic client works. It
is much easier to troubleshoot a filesystem restore. Refer to the HP
OpenView Storage Data Protector Administrator’s Guide for
information on troubleshooting filesystem restores.
• Examine the errors reported in
<Data_Protector_home>\log\debug.log on the Microsoft
Exchange Server.
• Examine the errors logged in the Windows Event log.

132 Chapter 3
 Integrating Microsoft Exchange Server 2000/2003 and Data Protector
Troubleshooting

• The restore session fails.

Message [Critical]
Target Instance, specified for restore, is not found or log
files do not match the backup set logs.

Description This problem occurs when there is a gap in the sequence of the
restored and the current log files

Action At the command prompt, run the eseutil tool from the directory
with temporary log files of the corresponding storage group:

— If the storage group name consists only of the ASCII characters

A-Z, a-z, 0-9, and space, run the following command from the
<Storage_group_name> subdirectory:
eseutil /cc /t
— If the storage group name consists of Unicode characters, proceed
as follows:

1. One of the subdirectories in the temporary log file directory

contains an empty file whose filename equals the name of the
storage group you are restoring. Identify the subdirectory
where the file is located. The subdirectory name conforms to
the following template:
Storage Group <Number>
2. Run the following commands:
<Drive_letter>:
cd "\<Temporary_log_files_directory_path>\Storage
Group <Number>"
eseutil /cc /t

Chapter 3 133
Integrating Microsoft Exchange Server 2000/2003 and Data Protector
Troubleshooting

134 Chapter 3
4 Integrating Microsoft Exchange
Single Mailbox and Data
Protector

Chapter 4 135
Integrating Microsoft Exchange Single Mailbox and Data Protector
In This Chapter

In This Chapter
This chapter explains how to configure and use the Data Protector MS
Exchange Single Mailbox integration.
The chapter is organized into the following sections:

“Overview” on page 137

“Prerequisites and Limitations” on page 139
“Integration Concept” on page 141
“Configuring the Integration” on page 144
“Backing Up a Single Mailbox” on page 155
“Restoring a Single Mailbox” on page 159
“Performance Tuning” on page 167
“Monitoring a Single Mailbox Backup and Restore” on page 169
“Troubleshooting” on page 172

136 Chapter 4
 Integrating Microsoft Exchange Single Mailbox and Data Protector
Overview

Overview
The Data Protector MS Exchange Single Mailbox integration enables
performing online backups and restores of single mailboxes located on
the MS Exchange Server system. The entire mailbox content including
e-mail messages, task assignments, calendar schedules, contacts, etc., is
backed up and restored by Data Protector.
You can perform full, incremental1, and incremental backups of single
mailboxes using the Data Protector MS Exchange Single Mailbox
integration.
You can restore your data into the original mailbox, into a new mailbox
on the same MS Exchange Server system, or into the mailbox located on
an other MS Exchange Server.

Advantages The following are the advantages of integrating Data Protector with MS
Exchange Single Mailbox:

• Central Management for all backup operations

The MS Exchange administrator can manage backup operations from
a central point.
• Media Management
Data Protector has an advanced media management system that
allows you to monitor media usage and set protection for stored data,
as well as to organize and manage devices in media pools.
• Backup Management
Backed up data can be duplicated during or after the backup to
increase fault tolerance of backups, to improve data security and
availability, or for vaulting purposes.
• Scheduling
Data Protector has a scheduler that allows you to automate backups
to run periodically. Using the Data Protector Scheduler, you can
configure the backups to run unattended at specified times if the
devices and media are set properly.

Chapter 4 137
Integrating Microsoft Exchange Single Mailbox and Data Protector
Overview

• Device Support
Data Protector supports a wide range of devices: files, standalone
drives, very large multiple drive libraries, etc.
• Reporting
Data Protector has reporting capabilities that allow you to receive
information about your backup environment. You can schedule
reports to be issued at a specific time or attached to a predefined set
of events, such as the end of a backup session or a mount request.
• Monitoring
Data Protector has a feature that allows you to monitor currently
running sessions and view finished sessions from any system that has
the Data Protector User Interface installed.
All backup sessions are logged in the Data Protector internal
database (IDB), which provides the administrator with a history of
activities that can be queried later.

138 Chapter 4
 Integrating Microsoft Exchange Single Mailbox and Data Protector
Prerequisites and Limitations

Prerequisites and Limitations

This is a list of prerequisites and limitations for the Data Protector MS
Exchange Single Mailbox integration:

Prerequisites • It is assumed that you are familiar with the MS Exchange

administration and basic Data Protector functionality.
• Before you begin, make sure that you have correctly installed and
configured the MS Exchange Server and Data Protector systems.
Refer to the following documentation:

— HP OpenView Storage Data Protector Software Release Notes or

http://www.openview.hp.com/products/datapro/spec_0001.html for
an up-to-date list of supported versions, platforms, devices, and
other information.
— Microsoft Exchange Server Documentation for information about
MS Exchange Server.
— HP OpenView Storage Data Protector Installation and Licensing
Guide for instructions on how to install Data Protector on various
architectures and how to install the Data Protector MS Exchange
5.x or the Data Protector MS Exchange 2000/2003 integration.
— HP OpenView Storage Data Protector Administrator’s Guide for
general information on how to configure and run backups.
• Before performing a restore into a different mailbox, make sure that
the destination mailbox exists on the target MS Exchange Server.
• Before restoring mailbox content to another MS Exchange Server
system, the MS Exchange Single Mailbox integration must be
installed and configured on the target MS Exchange Server.

Limitations • A single mailbox backup is slower and requires more media space
than a regular MS Exchange Server backup. The reason is that only
one copy of a message addressed to more than one recipient is saved
on the MS Exchange Server system and linked to all recipients. The
entire message is backed up for each mailbox when performing single
mailbox backups.

Chapter 4 139
 Integrating Microsoft Exchange Single Mailbox and Data Protector
Prerequisites and Limitations

• Only the messages, located on MS Exchange Server, can be backed up

and restored. It means that if you have messages stored locally on
client machines, they will not be backed up.

IMPORTANT Single mailbox backups should not be used as a replacement of regular

MS Exchange Server backups. Server backups are still needed to
successfully recover a crashed system. For the information on how to
back up MS Exchange Server, see “Backing Up Microsoft Exchange
Server 5.x” on page 78 and “Backing Up Microsoft Exchange Server” on
page 118.

140 Chapter 4
 Integrating Microsoft Exchange Single Mailbox and Data Protector
Integration Concept

Integration Concept
The following MS Exchange concepts are important from the single
mailbox backup and restore perspective:

• MAPI (Messaging Application Programming Interface), a

programming interface that lets applications and messaging clients
interact with messaging and information systems through the use of
a single interface.
• MAPI profile, a group of settings that define how a MAPI client is
set up for a particular user. It contains information services, that is
settings that enable sending, storing, and receiving messages. The
profile is created during the configuration process.
• MAPI session, a connection with a MAPI subsystem (for example,
MS Exchange Server) that must be established before a client
application can call the underlying messaging system.
• Message Store, a MAPI object that contains messages and folders
organized hierarchically.
• Message, a MAPI object containing the information that can be sent
to one or more recipients by means of a messaging system.

Integration The central component of the Data Protector MS Exchange Single

Overview Mailbox integration is the Data Protector mbx_bar.exe agent, which is
installed on the MS Exchange Server system. It communicates with MS
Exchange Server through MAPI thus controlling the activities between
MS Exchange Server and the Data Protector backup and restore
processes. The mbx_bar.exe agent transfers data directly from the MS
Exchange Server to Data Protector General Media Agents.
From the perspective of MS Exchange Server, Data Protector is seen as
media management software. On the other hand, MS Exchange Server is
a Data Protector client from the Data Protector Cell Manager’s point of
view.

Backup Flow A backup session is started by the Data Protector Backup Session
Manager (BSM). The BSM reads a backup specification and starts the
mbx_bar.exe agent installed on the MS Exchange Server system. The
mbx_bar.exe agent logs in through the MAPI profile to the Exchange
administrator’s mailbox, which has privileges to access users’ mailboxes.

Chapter 4 141
 Integrating Microsoft Exchange Single Mailbox and Data Protector
Integration Concept

The MAPI session is therefore established, and after that the

mbx_bar.exe agent logs to each mailbox that was selected for backup.
The content of these mailboxes is then passed to Data Protector General
Media Agents, which write it to media.
Messages from the backup session are sent to the BSM, which writes
them and the information regarding the respective backup session to the
IDB.

Backup Types The Data Protector MS Exchange Single Mailbox integration supports
three backup types: Full, Incremental1, and Incremental. A full
backup is a backup of the entire mailbox content. An incremental1
backup backs up all the changes made to the mailbox after the last full
backup. An incremental backup backs up all the changes after the last
backup of any type.
Each mailbox is represented as one Data Protector backup object and is
backed up in one stream. Multiple mailboxes can be backed up in
parallel streams to one device. See “Performance Tuning” on page 167.

Restore Flow A restore session is started by the Data Protector Restore Session
Manager (RSM). The RSM starts the mbx_bar.exe agent on the target
MS Exchange Server and invokes Data Protector General Media Agents,
which read the data from backup devices and send it to the MS Exchange
Server. The MS Exchange Server processes write the data to disks.
The mbx_bar.exe agent logs in to each mailbox that was selected for
restore, and creates there a new Data Protector <backup date>
<backup time> folder to which the selected data is restored.
Messages from the restore session are sent to the RSM, which writes
them and the information regarding the respective restore session to the
IDB.
The architecture of the Data Protector MS Exchange Single Mailbox
integration is presented in Figure 4-1 on page 143.

142 Chapter 4
 Integrating Microsoft Exchange Single Mailbox and Data Protector
Integration Concept

Figure 4-1 MS Exchange Single Mailbox Integration Concept

Table 4-1 Legend:

MAPI The Messaging Application Programming Interface, which lets

applications and messaging clients interact with messaging and
information systems through the use of a single interface.

SM The Data Protector Session Manager, which is the Data Protector

Backup Session Manager during a backup session, and the Data
Protector Restore Session Manager during a restore session.

MA The Data Protector General Media Agent, which reads and writes
data from and to media devices.

IDB The Data Protector internal database where all the information
about Data Protector sessions, including session messages, objects,
data, used devices and media is written.

Chapter 4 143
 Integrating Microsoft Exchange Single Mailbox and Data Protector
Configuring the Integration

Configuring the Integration

It is assumed that the installation of the Data Protector software
components on the MS Exchange Server system was successful.

Prerequisite Ensure that you have an account with MS Exchange administrative

permissions. In particular, check that Act as part of the operating
system and Log on as a service user rights are assigned to the MS
Exchange administrator account. See “Configuration Problems” on
page 173 for more details about these user rights.

Configuration The following list gives an overview of the global tasks for configuring
Overview the MS Exchange Single Mailbox integration:

1. “Configuring the Single Mailbox Integration Agent” on page 144.

2. “Configuring a Single Mailbox Backup” on page 148.

Cluster-Aware In a cluster environment, the MS Exchange Single Mailbox integration

Clients must be configured on all cluster nodes.
Once you have finished the configuration on one node, switch the virtual
server to the other node and repeat the configuration procedure.

Configuring the Single Mailbox Integration Agent

In order to perform single mailbox backup and restore-related
operations, the account, under which the mbx_bar.exe agent is started,
must have permissions to access the mailboxes residing on the MS
Exchange Server (these are the permissions of the MS Exchange
administrator). Therefore, the account you have to provide during the
configuration of the Single Mailbox integration agent must be the user
account, to which the permission to administer MS Exchange was
granted at the time of the MS Exchange Server installation.
This user account must also be added to the Data Protector Operator
user group, or to the user group with the same or higher privileges.
The parameters that need to be specified during the configuration
process are the username, the password, and the domain of the MS
Exchange administrator.

144 Chapter 4
 Integrating Microsoft Exchange Single Mailbox and Data Protector
Configuring the Integration

IMPORTANT The integration must be reconfigured any time the MS Exchange

administrator’s password changes.

The configuration is performed during the creation of a new backup

specification, and can be modified when a backup specification already
exists.
The procedure below describes the single mailbox integration
configuration at the time of creating a new backup specification:

1. In the HP OpenView Storage Data Protector Manager, switch to

the Backup context.
2. In the Scoping Pane, expand Backup, then Backup Specifications,
and right-click MS Exchange Single Mailboxes. Select Add Backup.
3. In the Create New Backup window, double-click Blank Single
Mailbox Backup.
4. In the next page of the wizard, select the client on which MS
Exchange is running. Data Protector lists all the clients that have the
MS Exchange 5.x or the MS Exchange 2000/2003 integration
installed. If the application is cluster-aware, select the virtual server
of the MS Exchange resource group.
The name of the application database is set to Single Mailbox, and
you cannot change it.
Click Next.
5. If the MS Exchange Single Mailbox integration was not configured for
the client you have selected, the Configure Single Mailbox window
is displayed.
In the Configure Single Mailbox window, provide the username,
the password, and the domain of the MS Exchange administrator.

Chapter 4 145
 Integrating Microsoft Exchange Single Mailbox and Data Protector
Configuring the Integration

Figure 4-2 Single Mailbox Configuration

Click OK to confirm the configuration.

Once the integration is configured for a particular client, the Configure
Single Mailbox window is not displayed any more during creating of
backup specifications for backing up data from this client. However, you
can modify the configuration when a backup specification already exists
following the procedure described below:

1. In the HP OpenView Storage Data Protector Manager, switch to

the Backup context.
2. In the Scoping Pane, expand Backup, Backup Specifications, and
then MS Exchange Single Mailboxes. Click an existing backup
specification.
3. Right-click the name of the MS Exchange Server listed in the Source
property page, and then select Configure from the pop-up window.
4. In the Configure Single Mailbox window, provide the required
information. Click OK to confirm the configuration.

What Happens? The login information and the encrypted password are written to the
configuration file on the Cell Manager:

• <Data_Protector_home>\Config\server\Integ\Config\Mailbox\
<hostname>%SingleMailbox - Windows Cell Manager
• /etc/opt/omni/server/integ/config/Mailbox/<hostname>%
SingleMailbox - HP-UX Cell Manager
If the integration is configured properly, Data Protector is allowed to
back up and restore single mailboxes.

146 Chapter 4
 Integrating Microsoft Exchange Single Mailbox and Data Protector
Configuring the Integration

Refer to the Microsoft Exchange documentation for further information

on different types of connections, roles and permissions of MS Exchange
database administrators, and security issues that need to be considered.

Checking the If you confirmed the configuration by clicking OK in the Configure

Configuration Single Mailbox window, the next page in the wizard allows you to
check the configuration.
Data Protector verifies the configuration by trying to connect to the MS
Exchange Server system on which the Single Mailbox integration is
configured using the information specified and saved during the
configuration procedure.

Figure 4-3 Checking the Configuration

Proceed as follows to check the configuration:

1. Right-click the MS Exchange Server system.

2. Click Check Configuration.
The configuration can also be checked if you have already created and
saved a backup specification for backing up a single mailbox. Follow the
steps described below:

1. In the HP OpenView Storage Data Protector Manager, switch to

the Backup context. In the Scoping Pane, expand Backup, Backup
Specifications, and then MS Exchange Single Mailboxes.
2. In the Results Area, right-click the backup specification.
3. In the Source property page, right-click the name of the client
system, and then click Check Configuration.

Chapter 4 147
Integrating Microsoft Exchange Single Mailbox and Data Protector
Configuring the Integration

If the configuration was successful, you receive a message confirming

that the integration was properly configured. If it was not, you receive a
message explaining the reasons for the unsuccessful configuration.

Configuring a Single Mailbox Backup

To configure a single mailbox backup, perform the following steps:

1. Configure the backup devices, media, and media pools.

Refer to the HP OpenView Storage Data Protector Administrator’s
Guide or online Help for instructions.
2. Create a backup specification.
Once the backup specification is created and saved, it can be
scheduled so that unattended backups can be performed.

Creating a Backup Specification

To create a backup specification for backing up single mailboxes, proceed
as follows:

1. In the HP OpenView Storage Data Protector Manager, switch to

the Backup context.
2. In the Scoping Pane, expand Backup, then Backup Specifications,
and right-click MS Exchange Single Mailboxes. Select Add Backup.
3. In the Create New Backup window, select the template you want to
use.

148 Chapter 4
 Integrating Microsoft Exchange Single Mailbox and Data Protector
Configuring the Integration

Figure 4-4 Selecting a Template

4. In the Client drop-down list, select the client on which MS Exchange

is running. Data Protector lists all the clients that have the MS
Exchange 5.x or the MS Exchange 2000/2003 integration installed. If
the application is cluster-aware, select the virtual server of the MS
Exchange resource group.
In the Application database drop-down list, leave the name of the
application database. It is set to Single Mailbox, and you cannot
change it.
Click Next.

NOTE If the integration had not been configured for the selected client, the
configuration window appears. See “Configuring the Single Mailbox
Integration Agent” on page 144 for the information on how to configure
the MS Exchange Single Mailbox integration.

Chapter 4 149
 Integrating Microsoft Exchange Single Mailbox and Data Protector
Configuring the Integration

5. In the next step of the wizard, select the data you want to back up. All
the mailboxes residing on the selected client are displayed in
alphabetical order. For example, all mailboxes with the first letter S
are collected under the S item in the Data Protector GUI.
You can specify a full server backup by selecting a top-level backup
object, or a single mailbox backup by selecting lower-level objects.

Figure 4-5 Selecting Backup Objects

Click Next to proceed.

6. Follow the wizard to select the devices to be used for backup, to define
backup options, and to schedule your backup specification.
Select the device(s) you want to use for the backup. Click Properties
to set the device concurrency, media pool, and preallocation policy.
For more information on these options, click Help.

150 Chapter 4
 Integrating Microsoft Exchange Single Mailbox and Data Protector
Configuring the Integration

You can also specify whether you want to create additional copies
(mirrors) of the backup during the backup session. Specify the desired
number of mirrors by clicking the Add mirror and Remove mirror
buttons. Select separate devices for the backup and for each mirror.
For detailed information on the object mirror functionality, refer to
the HP OpenView Storage Data Protector Administrator’s Guide.
Refer to the Data Protector online Help and the HP OpenView
Storage Data Protector Administrator’s Guide for a description of the
backup options common to all backup objects.
See “Backup Options” on page 151 for details about backup options,
specific to the Data Protector MS Exchange Single Mailbox
integration.
7. Name and save your MS Exchange Single Mailbox backup
specification.
After the backup specification is saved, it can be started either from
the Data Protector GUI or the Data Protector CLI, or can be
scheduled to run automatically using the Data Protector Scheduler.
See “Backing Up a Single Mailbox” on page 155 for information on
how to perform a backup using the Data Protector GUI or the Data
Protector CLI and on how to schedule a backup specification.
You can examine the newly created and saved backup specification in
the Backup context. The backup specification itself is stored in the
<Data_Protector_home>\Config\server\barlists\Mailbox\<b
ackup_specification_name> file on Windows Cell Manager
systems and in the /etc/opt/omni/server/barlists/Mailbox/
<backup_specification_name> file on HP-UX Cell Manager.
You can start an interactive backup that includes data transfer by
clicking the Start Backup button.

Backup Options
The MS Exchange Single Mailbox integration specific backup options are
specified using the Data Protector GUI by clicking the Advanced button
next to Application Specific Options.

Chapter 4 151
 Integrating Microsoft Exchange Single Mailbox and Data Protector
Configuring the Integration

Figure 4-6 Backup Options

The following backup options are specific to the Data Protector MS

Exchange Single Mailbox integration:
Pre-exec Specifies a command with arguments or a script that
will be started on MS Exchange Server before the
backup. This command/script, started by Data
Protector mbx_bar.exe, must reside in the
<Data_Protector_home>\bin directory on the MS
Exchange Server system. Only the filename, relative to
the directory named above, must be provided in the
backup specification. For more information on the
pre-exec commands, refer to the HP OpenView Storage
Data Protector Administrator’s Guide.
Post-exec Specifies a command with arguments or a script that
will be started on MS Exchange Server after the
backup. This command/script, started by Data
Protector mbx_bar.exe, must reside in the
<Data_Protector_home>\bin directory on the MS
Exchange Server system. Only the filename, relative to
the directory named above, must be provided in the

152 Chapter 4
 Integrating Microsoft Exchange Single Mailbox and Data Protector
Configuring the Integration

backup specification. For more information on the

post-exec commands, refer to the HP OpenView Storage
Data Protector Administrator’s Guide.

Testing the Integration

Once you have created and saved a backup specification, you should test
it before running a backup.

Testing Using the Data Protector GUI

Testing Procedure The testing procedure consists of checking the MS Exchange and the
Data Protector parts of the integration to ensure the communication
within MS Exchange and Data Protector is established and the data
transfer works properly. Proceed as follows to test the integration:

1. In the HP OpenView Storage Data Protector Manager, switch to

the Backup context.
2. In the Scoping Pane, expand Backup, then Backup Specifications,
MS Exchange Single Mailboxes, and right-click the backup
specification you want to preview.
3. Click Preview Backup to open the Start Preview dialog box. Select
the type of backup you want to run as well as the network load. For a
description of these options, press F1.

Figure 4-7 Previewing a Backup

Chapter 4 153
 Integrating Microsoft Exchange Single Mailbox and Data Protector
Configuring the Integration

Testing Using the Data Protector CLI

A test can be executed from the CLI on the MS Exchange Server system
or on any other Data Protector client system within the same cell,
provided that the systems have the Data Protector User Interface
installed.
To test a backup specification, run the omnib command with the
-test_bar option:
<Data_Protector_home>\bin\omnib -mbx_list
<backup_specification_name> -test_bar

What Happens? The session messages are displayed on the screen during the command
execution.
The mbx_bar.exe program is started, which then starts the Data
Protector testbar2 command. This command checks the following:

• if the communication within Data Protector works properly.

• if the syntax of the MS Exchange Single Mailbox backup specification
is correct.
• if the devices are correctly specified.
• if the required media reside in the devices.
After that, the MS Exchange part of the preview is started, which checks
if all the backup objects are present and are in a correct state for a
backup.

154 Chapter 4
 Integrating Microsoft Exchange Single Mailbox and Data Protector
Backing Up a Single Mailbox

Backing Up a Single Mailbox

Each mailbox is one Data Protector backup object, which is backed up in
one stream. However, if you perform a backup of several mailboxes, it is
recommended that you back them up in parallel streams to one device.
Backing up mailboxes this way enables constant data transfer to tape
and thus improves backup performance. See “Performance Tuning” on
page 167 for details.
To run a single mailbox backup, use any of the following methods:

• Schedule a backup of an existing MS Exchange Single Mailbox

backup specification using the Data Protector Scheduler.
• Start an interactive backup using the Data Protector GUI or the Data
Protector CLI.

Scheduling a Backup
Scheduling a backup specification means setting the time, date, and type
of a backup that will be started unattended once the scheduling options
are defined and saved in the backup specification.
To schedule an MS Exchange Single Mailbox backup specification,
perform the following steps:

1. In the HP OpenView Storage Data Protector Manager, switch to

the Backup context.
2. In the Scoping Pane, expand Backup, and then Backup
Specifications.
Expand the MS Exchange Single Mailboxes item to get a list of
backup specifications.
3. Double-click the backup specification you want to schedule, and then
click the Schedule tab to open the Schedule property page.
4. In the Schedule property page, select a date in the calendar, and
click Add to open the Schedule Backup dialog box.
5. Specify Recurring, Time options, Recurring options, and
Session options. See Figure 4-8 on page 156.

Chapter 4 155
 Integrating Microsoft Exchange Single Mailbox and Data Protector
Backing Up a Single Mailbox

You can select one of the following backup types: full, incremental1,
or incremental. See “Integration Concept” on page 141 for a detailed
description of backup types.
6. Click OK to return to the Schedule property page.
7. Click Apply to save the changes.

Figure 4-8 Scheduling a Backup

Running an Interactive Backup Using the Data

Protector GUI
An interactive backup can be run any time after the backup specification
has been created and saved.

Backup Procedure To start an interactive single mailbox backup using the Data Protector
GUI, perform the following steps:

1. In the HP OpenView Storage Data Protector Manager, switch to

the Backup context.

156 Chapter 4
 Integrating Microsoft Exchange Single Mailbox and Data Protector
Backing Up a Single Mailbox

2. In the Scoping Pane, expand the Backup, and then the Backup
Specifications items.
Expand MS Exchange Single Mailboxes. A list of backup
specifications appears.
3. Right-click the backup specification you want to back up, and then
select Start Backup from the pop-up menu.
The Start Backup dialog box appears.
Select the backup type and network load, and click OK. For a
description of these options, press F1.

Running an Interactive Backup Using the Data

Protector CLI
You can start an interactive backup from the Data Protector CLI. Switch
to the <Data_Protector_home>\bin directory on the MS Exchange
Server system, and run the following command:
omnib
-mbx_list <ListName>
[-barmode <MSMailboxMode>]
[<List_options>]
The <ListName> parameter is the name of a backup specification.
You can select among the following <MSMailboxMode>:
{full | incr | incr1}
You can select among the following <List_options>:
-barcmnd <Command>
-protect {none | weeks n | days n | until Date | permanent}
-keepcatalog {weeks n | days n | until Date | permanent}
-load {low | medium | high}
-disk_only
-crc
-no_monitor
-test_bar
Refer to the HP OpenView Storage Data Protector Command Line
Interface Reference for a description of <List_options>.

Chapter 4 157
 Integrating Microsoft Exchange Single Mailbox and Data Protector
Backing Up a Single Mailbox

Example To start an incremental backup using an existing MS Exchange Single

Mailbox backup specification called FIRST, and to set data protection to 5
days, execute the following command:
omnib -mbx_list FIRST -barmode incr -protect days 5

158 Chapter 4
 Integrating Microsoft Exchange Single Mailbox and Data Protector
Restoring a Single Mailbox

Restoring a Single Mailbox

You can restore a single mailbox using either the Data Protector GUI or
the Data Protector CLI.

Prerequisites • If you want to perform a restore into a different mailbox, make sure
that the destination mailbox exists on the target MS Exchange
Server.
• If you want to restore mailbox content to another MS Exchange
Server, configure the MS Exchange Single Mailbox integration on the
target MS Exchange Server.

Restoring a Single Mailbox Using the Data Protector

GUI
Use the following procedure to restore a single mailbox using the Data
Protector GUI:

1. In the HP OpenView Storage Data Protector Manager, switch to

the Restore context.
2. In the Scoping Pane, expand MS Exchange Single Mailboxes, and
then the name of the client system from which the data you want to
restore was backed up.
3. In the Source property page, browse for and select the backed up
objects you want to restore. These objects are displayed in
alphabetical order. For example, all the backed up mailboxes with the
first letter S are collected under the S item in the Data Protector GUI.
By selecting a top-level object (a letter) you restore all the mailboxes
with the first letter you specified, while by selecting lower-level
objects you perform a restore of single mailboxes.

Chapter 4 159
 Integrating Microsoft Exchange Single Mailbox and Data Protector
Restoring a Single Mailbox

Figure 4-9 Restore Objects

You may check the properties of each object by right-clicking the

object name.
Under the Version tab in the Properties window, select the version
you want to restore. The version is identified by the date and time of a
backup and the backup type.

NOTE By default, the latest version of the object is selected. If you want to
restore some other version, select it from the Backup version drop-down
list.

160 Chapter 4
 Integrating Microsoft Exchange Single Mailbox and Data Protector
Restoring a Single Mailbox

Figure 4-10 Version Properties

Under the Advanced tab in the Properties window, specify if you

want to restore your data into a different mailbox. To restore to
another mailbox, enter its name into the Restore into mailbox
text box.

IMPORTANT The destination mailbox must exist on the target MS Exchange Server.

You can choose between Restore only this backup and Full
restore of mailbox options. The last option is selected by default.

Chapter 4 161
 Integrating Microsoft Exchange Single Mailbox and Data Protector
Restoring a Single Mailbox

Figure 4-11 Advanced Properties

See “Restore Options” on page 165 for details about these options.
4. In the Options property page, specify whether you want to restore
the data to another MS Exchange Server system. See “Restore
Options” on page 165 for a description of this option.

IMPORTANT The MS Exchange Single Mailbox integration must be configured on the

target MS Exchange Server. Otherwise, the Configuration window will
appear at the beginning of a restore session.

162 Chapter 4
 Integrating Microsoft Exchange Single Mailbox and Data Protector
Restoring a Single Mailbox

Figure 4-12 Selecting a Destination

5. In the Devices property page, the names of devices used for backup
are displayed. If you want to restore from a device different from the
one used for backup, select the device you want to change, and click
Change. The list of all configured devices is displayed. From this list,
select the device you want to use for restore, and then click OK.
Refer to the HP OpenView Storage Data Protector Administrator’s
Guide for more information on how to perform a restore using
another device.
6. Click Restore MS Exchange to start the restore session.

After the Restore Data Protector creates a Data Protector <backup date> <backup
time> folder on each mailbox selected for restore, and restores the data
into it. If the same backup version was restored several times, folders
with restored data look as follows: Data Protector <backup date>
<backup time> (1) (this folder contains the backup version, which was
restored first), Data Protector <backup date> <backup time> (2)

Chapter 4 163
 Integrating Microsoft Exchange Single Mailbox and Data Protector
Restoring a Single Mailbox

(this folder contains the backup version, which was restored second), etc.,
depending on the number of restore sessions performed. See Figure 4-13
on page 164.

Figure 4-13 Restored Mailbox Content

Mailbox users can start transferring restored data to .pst files by

performing the following:

1. Creating a .pst file on their client system.

2. Connecting to MS Exchange Server.
3. Moving the restored data from the Data Protector <backup date>
<backup time> folder to the previously created .pst file.

164 Chapter 4
 Integrating Microsoft Exchange Single Mailbox and Data Protector
Restoring a Single Mailbox

Restore Options
The following restore options are specific to the Data Protector MS
Exchange Single Mailbox integration:
Restore into mailbox By default, the data is restored into the original
mailbox. Nevertheless, you may restore your data into
a different mailbox. In this case, enter the name of this
mailbox in the Restore into mailbox text box. The
destination mailbox must exist on the target MS
Exchange Server. Note that you can specify the same
destination mailbox for more than one mailbox you
want to restore.
Full restore of mailbox This option is selected by default. The latest
full, the latest incremental1 (if exists), and all
incremental backups from the last incremental1 up to
the selected version are restored within one restore
session.
Restore only this backup If you specify this option, only a selected
backup session, regardless of the backup type, will be
restored.
Restore to another host By default, the target Data Protector MS
Exchange client is the MS Exchange Server from which
the data was backed up. Nevertheless, mailboxes can
be restored to an MS Exchange Server other than the
one the backup was made from. The new target MS
Exchange Server must be a part of the Data Protector
cell and have the MS Exchange 5.x Integration or
the MS Exchange 2000/2003 Integration software
component installed and configured.

Restoring a Single Mailbox Using the Data Protector

CLI
You can also start a restore session from the Data Protector CLI. Switch
to the <Data_Protector_home>\bin directory on the MS Exchange
Server system, and run the following command:
omnir -mbx
-barhost <HostName>
[-destination <HostName>]

Chapter 4 165
 Integrating Microsoft Exchange Single Mailbox and Data Protector
Restoring a Single Mailbox

-mailbox <MailboxName>
-session <SessionID>
[<MAILBOX_OPTIONS>]...
You can select among the following <MAILBOX_OPTIONS>:
-destMailbox <destMailboxName>
-chain
The -barhost <HostName> parameter is the name of the MS Exchange
Server system from which you are restoring, while the -destination
<HostName> parameter is the name of the target MS Exchange Server.
<MailboxName> is the name of the mailbox you want to restore, and
<SessionID> is the ID of the backup session. In case of object copies, do
not use the copy session ID, but the object's backup ID, which equals the
object's backup session ID.
The <destMailboxName> parameter is the name of a destination mailbox
into which the data will be restored (in case of a restore into the mailbox
other than the original). By specifying the chain parameter, you select
full restore of a mailbox meaning that the latest full, the latest
incremental1 (if exists), and all incremental backups from the last
incremental1 up to the selected version are restored within one restore
session; otherwise, only a selected backup session, regardless of the
backup type, will be restored.

Example To restore the contents of a mailbox called FIRST residing on the MS

Exchange Server system called infinity.ipr.hermes, with the backup
session ID 2003/01/10-1, into a new mailbox called TEMP, execute the
following command:
omnir -mbx -barhost infinity.ipr.hermes -mailbox FIRST
-session 2003/01/10-1 -destMailbox TEMP

166 Chapter 4
 Integrating Microsoft Exchange Single Mailbox and Data Protector
Performance Tuning

Performance Tuning
Performance tuning means customizing MS Exchange Server and Data
Protector to achieve better backup and restore results.
When backing up single mailboxes, one backup object is created for each
mailbox selected for backup. The Single Mailbox integration agent
mbx_bar.exe spends a significant amount of time on creating/finishing
Data Protector backup objects and logging mailboxes on/off before it
starts the actual data transfer to tape. This influences backup
performance, especially if the mailbox store contains a lot of mailboxes.
In this case, data transfer stops when mbx_bar.exe finishes a backup of
one mailbox and starts a backup of the next one. This has an impact on
the backup device, which stops a tape when the mbx_bar.exe agent
finishes with one mailbox and starts running a tape when the agent
restarts data transfer.
Figure 4-14 on page 167 shows how a single-streamed backup of
mailboxes affects backup performance.

Figure 4-14 An Example of a Single-Streamed Backup (Concurrency = 1)

This problem can be solved by backing up mailboxes in parallel streams.

Performance tests show that the best performance is achieved by backing
up mailboxes in 2 parallel streams to one device or by backing up
mailboxes in 2 concurrent streams to 2 devices. The second stream takes
over the entire backup load while the first stream deals with
creating/finishing the object process and the mailbox logon/logoff.

Chapter 4 167
 Integrating Microsoft Exchange Single Mailbox and Data Protector
Performance Tuning

Backing up mailboxes this way enables constant data transfer to tape

and thus improves backup performance. See Figure 4-15 on page 168.

Figure 4-15 An Example of a Multiple-Streamed Backup (Concurrency = 2)

NOTE The backup of one mailbox using multiple streams is not supported.

168 Chapter 4
 Integrating Microsoft Exchange Single Mailbox and Data Protector
Monitoring a Single Mailbox Backup and Restore

Monitoring a Single Mailbox Backup and

Restore
The Data Protector GUI enables you to monitor current or view previous
backup and restore sessions.
Monitoring is automatically activated when you start a restore or backup
interactively.

Monitoring Current Sessions

To monitor a currently running session using the Data Protector GUI,
proceed as follows:

1. In the Context List, click Monitor.

In the Results Area, all currently running sessions are listed.
2. Double-click the session you want to monitor. See Figure 4-16.

Figure 4-16 Monitoring Current Sessions

Clearing Sessions To remove all completed or aborted sessions from the Results Area of the
Monitor context, proceed as follows:

1. In the Scoping Pane, click Current Sessions.

2. In the Actions menu, select Clear Sessions. Or click the Clear
Sessions icon on the toolbar.
To remove a particular completed or aborted session from the current
sessions list, right-click the session and select Remove From List.

Chapter 4 169
 Integrating Microsoft Exchange Single Mailbox and Data Protector
Monitoring a Single Mailbox Backup and Restore

NOTE All completed or aborted sessions are automatically removed from the
Results Area of the Monitor context if you restart the Data Protector
GUI.

For detailed information on a completed or aborted session, see “Viewing

Previous Sessions”.

Viewing Previous Sessions

To view a previous session using the Data Protector GUI, proceed as
follows:

1. In the Context List, click Internal Database.

2. In the Scoping Pane, expand Sessions to display all the sessions
stored in the IDB.
The sessions are sorted by date. Each session is identified by a
session ID consisting of a date in the YY/MM/DD format and a unique
number.
3. Right-click the session and select Properties to view details on the
session.
4. Click the General, Messages or Media tab to display general
information on the session, session messages, or information on the
media used for this session, respectively. See Figure 4-17.

170 Chapter 4
 Integrating Microsoft Exchange Single Mailbox and Data Protector
Monitoring a Single Mailbox Backup and Restore

Figure 4-17 Viewing a Previous Session

Chapter 4 171
Integrating Microsoft Exchange Single Mailbox and Data Protector
Troubleshooting

Troubleshooting
The following section provides some testing procedures you should
perform before calling the Data Protector support. Following these
guidelines, you may either resolve the problem yourself or identify the
area where the problems occur.
Should you fail when performing a troubleshooting procedure, actions
are proposed to help you work around the problem.
The section is divided into the following subsections:

• General troubleshooting
• Configuration problems
• Backup problems
• Restore problems

General Troubleshooting
1. Ensure that the latest official Data Protector patches are installed.
Refer to the “Verifying Which Data Protector Patches Are Installed”
in the HP OpenView Storage Data Protector Installation and
Licensing Guide.
Refer to the HP OpenView Storage Data Protector Software Release
Notes or
http://www.openview.hp.com/products/datapro/spec_0001.html for an
up-to-date list of supported versions, platforms, and other
information.
2. Refer to the HP OpenView Storage Data Protector Software Release
Notes for a description of general Data Protector limitations,
problems, and workarounds.
3. Check if the following directories exist on the Data Protector Cell
Manager:
<Data_Protector_home>\config\server\barlists\Mailbox
<Data_Protector_home>\config\server\barschedules\Mailbox

172 Chapter 4
 Integrating Microsoft Exchange Single Mailbox and Data Protector
Troubleshooting

Configuration Problems

Problem You do not have necessary permissions to log on to the system

The <Data_Protector_home>\log\debug.log file on the MS
Exchange 2000/2003 Server contains one of the following error messages:
Error = 596
Logon failure: the user has not been granted the requested logon
type to this computer.

or:
[MBX_ImpersonateUser] A required privilege is not held by the
client.

Action Check on the Domain Controller system if the domain-level policy

settings are defined.
To do this, go to Start->Settings->Control Panel->Administrative
Tools->Domain Security Policy->Local Policies->User Rights
Assignment, and check in the Computer Setting column if the Log on
as a service and Act as part of the operating system user
rights are set to Defined.

Domain-Level If the domain-level policy settings are defined, proceed as follows:

Policy Settings
Are Defined 1. Go to Start->Settings->Control Panel->Administrative
Tools->Domain Security Policy->Local Policies->User Rights
Assignment on the Domain Controller System.
2. Set Log on as a service and Act as part of the operating
system user rights for the MS Exchange administrator.
3. Run the secedit command:
secedit /refreshpolicy machine_policy /enforce
4. Perform the following steps on the MS Exchange 2000/2003 Server
system:

a. Log off the currently logged on user, and then log this user on
again.

Chapter 4 173
 Integrating Microsoft Exchange Single Mailbox and Data Protector
Troubleshooting

b. Start the Local Security Policy console application:

Start->Settings->Control Panel->Administrative
Tools->Local Security Policy->Local Policies->User
Rights Assignment.
c. Make sure that Act as part of the operating system and
Log on as a service user rights are set to MS Exchange
administrator in both the Local Setting and Effective
Setting columns.

Domain-Level If the domain-level policy settings are not defined, perform the following
Policy Settings steps on the MS Exchange 2000/2003 Server system:
Are Not Defined
1. Start the Local Security Policy console application:
Start->Settings->Control Panel->Administrative
Tools->Local Security Policy->Local Policies->User Rights
Assignment.
2. Set the Act as part of the operating system and Log on as a
service user rights for the MS Exchange administrator account.
3. Log off the currently logged on user, and then log this user on again.

IMPORTANT After performing any of the above-mentioned procedures, restart the

Data Protector Inet service on the MS Exchange 2000/2003 Server
system.

Problem Configuration of the Single Mailbox integration is not successful

The <Data_Protector_home>\log\debug.log file on the MS
Exchange Server contains the following error message:
An error has occurred while creating a profile administration
object.

Action Proceed as follows to solve this problem:

1. Connect to the client machine where MS Exchange Server is

installed.
2. Run the <Data_Protector_home>\bin\mbx_bar.exe delete
command to delete the incorrect administrator’s profile.

174 Chapter 4
 Integrating Microsoft Exchange Single Mailbox and Data Protector
Troubleshooting

3. Run the <Data_Protector_home>\bin\mbx_bar.exe create

command to manually create a profile:

a. In the Choose Profile window, click New to create a new profile.

b. Following the profile setup wizard, specify the $$$Data
Protector as a profile name, provide the name of the MS
Exchange Server containing the administrator’s mailbox, and
enter the name of the MS Exchange administrator’s mailbox. See
Figure 4-18 on page 175.

Figure 4-18 The Setup Wizard

Backup Problems

Problem Backup does not work

Actions To solve this kind of problem, try one of the actions described below:

• Start a preview of the Data Protector MS Exchange backup

specification:

— If the MS Exchange Server part of the preview fails, check if the

MS Exchange databases are running.
— If the Data Protector part of the preview fails, proceed as follows:

1. Make sure that the Cell Manager is correctly set on the

Microsoft Exchange 2000/2003 Server client by checking the
following registry entry:

Chapter 4 175
 Integrating Microsoft Exchange Single Mailbox and Data Protector
Troubleshooting

HKEY_LOCAL_MACHINE\SOFTWARE\Hewlett-Packard\OpenVie
w\OmniBack II\Site
Its name and value must be CellServer and “<Cell Manager
hostname>”, respectively.
2. Check if the integration was properly configured. The
procedure how to check configuration is described on page 147.
3. Create an MS Exchange Single Mailbox backup specification to
back up to a null or file device, and run the backup. If the
backup succeeds, the problem may be related to backup
devices. Refer to the HP OpenView Storage Data Protector
Administrator’s Guide for instructions on troubleshooting
devices.
— If the preview succeeds, proceed as follows:

1. Examine the errors reported in the

<Data_Protector_home>\log\debug.log file on the MS
Exchange Server.
2. Examine the errors logged in the Windows Event log.
3. Try to restart the MS Exchange Server and start the backup
again.

Restore Problems

Problem Restore does not work

Actions To solve this kind of problem, try one of the actions described below:

• Make sure that the Cell Manager is correctly set on the MS Exchange
Server client by checking the following registry entry:
HKEY_LOCAL_MACHINE\SOFTWARE\Hewlett-Packard\OpenView\Omni
Back II\Site
Its name and value should be CellServer and “<Cell Manager
hostname>”, respectively.
• Examine the errors reported in the
<Data_Protector_home>\log\debug.log file on the MS Exchange
Server.
• Examine the errors logged in the Windows Event log.

176 Chapter 4
 Integrating Microsoft Exchange Single Mailbox and Data Protector
Troubleshooting

Problem Restore to another client fails

Action Check if the MS Exchange Server is installed and the Data Protector MS
Exchange Single Mailbox integration is installed and configured on the
system to which you will perform a restore.

Problem Restore into another mailbox fails

Action Make sure that the destination mailbox exists on the target MS
Exchange Server.

Chapter 4 177
Integrating Microsoft Exchange Single Mailbox and Data Protector
Troubleshooting

178 Chapter 4
5 Integrating Microsoft Volume
Shadow Copy Service with Data
Protector

Chapter 5 179
Integrating Microsoft Volume Shadow Copy Service with Data Protector
In This Chapter

In This Chapter
This chapter explains how to configure and use the Data Protector
Microsoft Volume Shadow Copy integration.
The chapter is organized into the following chapters:

“Overview” on page 181

“Prerequisites and Limitations” on page 185
“Integration Concepts” on page 187
“Configuring the Integration” on page 191
“Writers Specifics” on page 194
“Backing Up Writers Data” on page 199
“Restoring Writers Data” on page 207
“Monitoring a VSS Backup and Restore” on page 215
“Troubleshooting Integration” on page 218

180 Chapter 5
 Integrating Microsoft Volume Shadow Copy Service with Data Protector
Overview

Overview
A traditional backup process is based on the direct communication
between the backup application and the application to be backed up. This
backup method requires from the backup application an individual
interface for each application it backs up.
The number of applications on the market is constantly increasing. The
necessity of handling application specific features can cause difficulties
in backup, restore, and storage activities. An effective solution to this
problem is introducing a coordinator among the actors of the backup and
restore process.

Volume Shadow Volume Shadow Copy service (VSS) is a software service introduced by
Copy Service Microsoft on Windows operating systems. This service collaborates with
the backup application, applications to be backed up, shadow copy
providers, and the operating system kernel to implement the
management of volume shadow copies and shadow copy sets.
HP OpenView Storage Data Protector supports the integration with the
Microsoft Volume Shadow Copy service (VSS).
The Data Protector Volume Shadow Copy integration provides a unified
communication interface that can coordinate backup and restore of any
application regardless of their specific features. With this approach,
backup application does not need to handle each application to be backed
up specifically. However, the production application as well as the backup
application must conform to the VSS specification.
Figure 5-1 and Figure 5-2 show the differences between the traditional
backup model and the model with the Data Protector MS Volume
Shadow Copy integration.

Chapter 5 181
 Integrating Microsoft Volume Shadow Copy Service with Data Protector
Overview

Figure 5-1 Actors of the Traditional Backup Model

Figure 5-2 Actors of the Data Protector VSS Integration Backup Model

182 Chapter 5
 Integrating Microsoft Volume Shadow Copy Service with Data Protector
Overview

Without using the Volume Shadow Copy service, Data Protector has to
communicate with each application to be backed up individually. The
Data Protector VSS integration introduces a unified backup and restore
interface and provides the coordination among the participants of the
backup and restore process.

Advantages The advantages of using the Data Protector MS Volume Shadow Copy
integration are the following:

• Central Management for all backup operations

The administrator can manage backup operations from a central
point.
• Media Management
Data Protector has an advanced media management system that
allows users to monitor media usage and set protection for stored
data, as well as to organize and manage devices in media pools.
• Backup Management
Backed up data can be duplicated during or after the backup to
increase fault tolerance of backups, to improve data security and
availability, or for vaulting purposes.
• Scheduling
Data Protector has a built-in scheduler that allows the administrator
to automate backups to run periodically. Using the Data Protector
Scheduler, the backups you configure run unattended at specified
times, as long as the devices and media are properly set.
• Device Support
Data Protector supports a wide range of devices: files, standalone
drives, very large multiple drive libraries, etc.
• Reporting
Data Protector has reporting capabilities that allow you to get
information on your backup environment. You can schedule reports to
be issued at a specific time or to be attached to a predefined set of
events, such as the end of a backup session or a mount request.

Chapter 5 183
Integrating Microsoft Volume Shadow Copy Service with Data Protector
Overview

• Monitoring
Data Protector has a feature that allows the administrator to monitor
currently running sessions and view finished sessions from any
system that has the Data Protector GUI installed.
All backup sessions are logged in the IDB, which provides the
administrator with a history of activities that can be queried later.

184 Chapter 5
 Integrating Microsoft Volume Shadow Copy Service with Data Protector
Prerequisites and Limitations

Prerequisites and Limitations

This is a list of prerequisites and limitations for the Data Protector MS
Volume Shadow Copy integration:

Prerequisites • MS Volume Shadow Copy integration is supported only on the

Windows Server 2003 operating systems.
• Before you begin, ensure that you have correctly installed and
configured Data Protector, writers and shadow copy providers. Refer
to the:

— HP OpenView Storage Data Protector Software Release Notes for

an up-to-date list of supported versions, platforms, devices,
limitations, and other information.
— HP OpenView Storage Data Protector Installation and Licensing
Guide for instructions on how to install Data Protector on various
architectures and how to install the Data Protector MS Volume
Shadow Copy integration.
— Writers and shadow copy providers documentation for
instructions on how to install and configure writers and providers
on your system.

Limitations Refer to the HP OpenView Storage Data Protector Software Release Notes
for a list of general Data Protector limitations. The integration-specific
limitations are the following:

• Maximum 64 volumes in a single volume shadow copy set is allowed.

The number of shadow copy sets per volume is limited by system
resources.
• To run a VSS integration backup, your system must have at least one
NTFS filesystem.
• The VSS integration backup of writers which store their data on
network shared volumes is not supported.
• The Data Protector MS VSS integration does not provide any restore
method for writers requesting a custom restore method. These
writers are by default not presented by Data Protector.

Chapter 5 185
Integrating Microsoft Volume Shadow Copy Service with Data Protector
Prerequisites and Limitations

If a writer specifies a custom restore method, it is only possible to

restore the writer's data as plain files using the Data Protector
functionality. You can perform the custom restore manually. Refer to
the writers documentation for additional information on the restore
methods.
• Only Full backup is supported.
• Preview is only possible for VSS filesystem backup sessions.

186 Chapter 5
 Integrating Microsoft Volume Shadow Copy Service with Data Protector
Integration Concepts

Integration Concepts
The Data Protector integration with the MS Volume Shadow Copy
service provides full support for certified VSS-aware writers. This
includes automatic detection of the VSS-aware writers and backup and
restore functionality.
If the writers are not aware of the VSS mechanism, the VSS filesystem
backup is provided. For information on the VSS filesystem backup, refer
to the HP OpenView Storage Data Protector Administrator’s Guide.
For a complete list of supported VSS writers and providers refer to the
HP OpenView Storage Data Protector Software Release Notes.

Benefits of Using The advantages of using the Data Protector VSS integration are the
the Integration following:

• Unified backup interface is provided for all writers.

• Data integrity is provided on application level, because it is provided
by the writers. No interference is needed from the backup application.

VSSBAR Agent The central part of the integration is the VSSBAR agent, which links
Data Protector with the MS Volume Shadow Copy service. Data
Protector MS Volume Shadow Copy integration uses the VSSBAR agent
for automatic browsing of VSS-aware writers, coordinating backup and
restore. VSSBAR agent is responsible for the following actions:

• detecting VSS-aware writers

• examining and analyzing Writer Metadata Document (WMD)

NOTE A Writer Metadata Document (WMD) is metadata provided by each

writer. Writers identify themselves by the metadata and instruct the
backup application what to back up and how to restore the data. Thus,
Data Protector follows the requirements provided by the writer when
selecting the volumes to be backed up and the restore method.

• requesting shadow copy creation

• backing up writers’ data to media

Chapter 5 187
 Integrating Microsoft Volume Shadow Copy Service with Data Protector
Integration Concepts

• coordinating restore session start

• restoring the Writer Metadata Document
• restoring writer’s data from media

Backup Flow During the Data Protector VSS integration backup, Data Protector does
not interact directly with each writer, but through the VSS interface. It
uses the VSSBAR agent to coordinate the backup process. The
consistency of data is provided on the level of writer and not dependent
on Data Protector functionality. The backup process of the VSS-aware
writers consists of the following phases:

1. When you selected writers and components you want to back up and
started a VSS integration backup, Data Protector communicates with
the Volume Shadow Copy service (backup coordinator) to notify that
the backup is about to start.
2. The coordinator identifies all writers that support the VSS feature
and passes the list of available writers and their characteristics
(Writer Metadata Document) back to Data Protector.
3. Data Protector examines Writer Metadata and identifies the volumes
that contain the data to be backed up. Then the VSS informs
available writers about selected components.
4. Data Protector prepares a list of volumes (shadow copy set) that must
be put into consistent state, and passes the list back to the
coordinator for preparing a shadow copy.
5. The VSSBAR agent notifies the writers about the shadow copy
creation. The VSS mechanism ensures that there are no writes on the
volume while the shadow copy is being created.

NOTE When the VSSBAR agent creates a shadow copy of the volume, this
volume is marked in order to avoid attempts to simultaneously create
another shadow copy of the same volume. In order to prevent any
deadlocks arising from volume locking, only a single VSSBAR agent at a
time is allowed to define a shadow copy set.

6. When the writers are fully prepared for the consistent shadow copy
backup, the VSSBAR agent passes shadow copy creation requests to
VSS.

188 Chapter 5
 Integrating Microsoft Volume Shadow Copy Service with Data Protector
Integration Concepts

7. After a shadow copy is created, the VSS service returns the related
information to the Data Protector.
8. Data Protector backs up the data from the shadow copy to media and
then notifies the VSS service that the shadow copy can be released.
VSS issues a command to the shadow copy provider to destroy the
shadow copy that has been already backed up. Figure 5-3 shows the
relations between the actors of a local or network VSS backup.

Figure 5-3 Local or Network VSS Backup

Restore Flow During the restore procedure, the Data Protector VSS integration
coordinates communication between Data Protector and the writers. In
general, the restore flow consists of the following phases: preparing for
restore, restoring components, and notifying the application writers that
a restore has been completed. The restore procedure of the VSS-aware
writers consists of the following phases.

1. Data Protector first restores the metadata, which was collected

during the backup. Then it examines the metadata to identify the
backup components and determine the restore method. It also checks
if restore to specific volumes is possible.

Chapter 5 189
Integrating Microsoft Volume Shadow Copy Service with Data Protector
Integration Concepts

2. Data Protector connects to the coordinator (VSS service) to notify that

the restore is about to start, which in turn communicates with the
writer. Data Protector restores the data from the backup media to the
locations specified in the backup metadata. During the restore, Data
Protector follows the writers' instructions regarding any additional
checking or processing specified in the WMD.
3. After the data are successfully restored from the backup media, Data
Protector informs the coordinator that the restore is completed and
the writers can now access the newly-restored data and start the
internal processing, for example recovery.

190 Chapter 5
 Integrating Microsoft Volume Shadow Copy Service with Data Protector
Configuring the Integration

Configuring the Integration

The Data Protector MS Volume Shadow Copy integration does not
require any configuration steps neither on the Data Protector nor on the
application side, unless you are configuring a cluster-aware Data
Protector VSS integration.
VSS writers are either a part of Windows operating system or delivered
with applications. Data Protector automatically detects writers when the
VSS backup specification is created and registers them.
You may check which writers and shadow copy providers are installed
and registered on your system using the following Windows operating
system command:

• For a list of writers: VSSadmin list writers

• For a list of providers: VSSadmin list providers

Configuring the Data Protector VSS Cluster-Aware

Integration
The configuration of the Data Protector VSS cluster-aware integration
consists of:

1. Configuring an VSS cluster-aware client. Refer to “Configuring a VSS

Cluster-Aware Client” on page 191.
2. Configuring a cluster-aware VSS integration backup. Refer to
“Configuring Backups for a Cluster-Aware VSS Client” on page 192
Find below an overview of global configuration tasks with cluster-specific
steps.

Configuring a VSS Cluster-Aware Client

The client configuration must be performed on one cluster node per one
VSS client, since the Data Protector VSS configuration file resides on the
Cell Manager.

Chapter 5 191
 Integrating Microsoft Volume Shadow Copy Service with Data Protector
Configuring the Integration

Configuring Backups for a Cluster-Aware VSS Client

To configure backups for a cluster-aware VSS client, create a Data
Protector VSS backup specification, as explained in “Creating Backup
Specification Using GUI” on page 199 taking into account the VSS
infrastructure specifics described below.
The MS VSS infrastructure does not identify writers that run as cluster
resources (for example, cluster-aware writers). Therefore, the MS VSS
integration agent cannot distinguish between the cluster-aware and
non-cluster-aware writers when creating a backup specification. This
means you need to configure different backup specifications for
cluster-aware and non-cluster-aware writers.
When backing up cluster-aware writers (such as SQL Server via the
MSDE Writer), specify the name of the VSS client system as the virtual
server name given in the particular writer resource group.
When backing up writers that are not cluster-aware (such as System
Writer or Event Log Writer), specify the name of the VSS client system
as the physical node.

Example 5-1 VSS Cluster Specifics

The example below shows why it is necessary to create different backup
specifications for cluster-aware and non-cluster-aware writers.
You have node_A and node_B, and MS Exchange Server 2003 running on
a virtual host exchsvr. When creating a backup specification, you can
select, among others, MS Exchange Writer and Event Log Writer.
Suppose, at the time of a backup, Exchange is running on node_A. If you
create just one backup specification for both writers, the following
problems will occur:

• If you select node_A as your source host, you have Event Log Writer
and Exchange Server 2003 associated with node_A. While it is true,
that Event Log Writer is a property of the physical node, it is wrong to
associate Exchange Server with it, as it is a property of the virtual
server.
Suppose that after a failover, MS Exchange Server 2003 is running on
node_B. When you try to restore the data to node_A, the restore will
fail because Exchange disks are now owned by node_B and you
cannot write to them. However, the restore of Event Log Writer will
succeed.

192 Chapter 5
 Integrating Microsoft Volume Shadow Copy Service with Data Protector
Configuring the Integration

• If you select exchsvr as your source host, you have Event Log Writer
and Exchange Server associated with a virtual server exchsvr. While
it is true, that Exchange Server 2003 is a property of the virtual
server, it is wrong to associate Event Log Writer with it, as it is a
property of the physical node.
Suppose that after a failover, MS Exchange Server 2003 is running on
node_B. When you try to restore Event Log Writer data to exchsvr, it
will overwrite (or try to overwrite) the data in the Event Log of
node_B with the data from the Event Log of node_A. The restore of
Event Log Writer will fail, while Exchange Server will be restored
successfully.

Chapter 5 193
 Integrating Microsoft Volume Shadow Copy Service with Data Protector
Writers Specifics

Writers Specifics
This section describes specific information about VSS writers, that you
need to take into account before backing up or restoring the writers.
VSS writers either come with the Windows operating system or with
applications. Please refer to the support matrix in the HP OpenView
Storage Data Protector Software Release Notes for a list of supported
writers.
The Data Protector MS VSS integration does not provide any restore
method for writers requesting a custom restore. If a writer specifies a
custom restore method, it is only possible to restore the writer's data as
plain files using the Data Protector functionality. You can perform the
custom restore manually. Refer to the writers documentation for
additional information on the restore methods.

NOTE Writers requiring custom restore methods are by default not shown by
Data Protector. The omnirc variable OB2_SHOWALLWRITERS must be set
to 1 for all writers to be displayed.

Table 5-1 provides a description of VSS writers.

Table 5-1 Writer description

Writer Description Restore

Name Method

Certificate This is a system writer, used to back Files are

Authority up and restore Certificate Authority restored
Writer (CA) Service database. This service after a
issues, revokes, and manages reboot.
certificates employed in public
key-based cryptography technologies.

194 Chapter 5
 Integrating Microsoft Volume Shadow Copy Service with Data Protector
Writers Specifics

Table 5-1 Writer description

Writer Description Restore

Name Method

Cluster This VSS writer using a custom API, Custom

Service is used to back up and restore Cluster restore
Writer Service on Microsoft Cluster Server method
(MSCS). The Cluster Service is a
component on Windows servers used
to control server cluster activities on
cluster nodes. It is fundamental to the
operation of the cluster.

COM+ This VSS writer using a custom API, Custom

REGDB is used to back up and restore COM+ restore
Writer Database Service. This service method
provides automatic distribution of
events to subscribing COM+
components.

DHCP Jet This is a system writer, used to back Files are

Writer up and restore DHCP Service restored
database. DHCP Service provides after a
dynamic IP address assignment and reboot.
network configuration for Dynamic
Host Configuration Protocol (DHCP)
clients.

Event Log This is a system writer, used to back Files are

Writer up and restore Event Logs. Event Logs restored
are files where the Windows operating after a
system saves information about reboot.
events, such as starting and stopping
services or the logging on and logging
off of a user.

Chapter 5 195
 Integrating Microsoft Volume Shadow Copy Service with Data Protector
Writers Specifics

Table 5-1 Writer description

Writer Description Restore

Name Method

FRS Writer This VSS writer using a custom API, Custom

is used to back up and restore File restore
Replication Service data. File method
Replication Service is a multithreaded
replication engine that replicates
system policies and logon scripts
stored in System Volume (SYSVOL).
FRS can also replicate data for
Distributed File System (Dfs), copy
and maintain shared files and folders
on multiple servers simultaneously.

IIS This is a system writer, used to back Files are

Metabase up and restore Microsoft Internet restored
Writer Information Server (IIS). IIS is a after a
network file and application server reboot.
that supports multiple protocols.
Primarily, IIS transmits information
in Hypertext Markup Language
(HTML) pages by using the Hypertext
Transport Protocol (HTTP).

MSDE This is a writer used to back up and Refer to

Writer restore Microsoft SQL Server. SQL “MSDE
Server is a database management Writer
system that can respond to queries Restore
from client machines formatted in the Specifics” on
SQL language. page 209.

Microsoft This is a writer used to back up and Refer to

Exchange restore Microsoft Exchange Server “Microsoft
2003 Server 2003. Microsoft Exchange Server 2003 Exchange
Writer is a mail and groupware server. Server 2003
Writer
Restore
Specifics” on
page 211.

196 Chapter 5
 Integrating Microsoft Volume Shadow Copy Service with Data Protector
Writers Specifics

Table 5-1 Writer description

Writer Description Restore

Name Method

NTDS This is a system writer used to back up To restore

Writer and restore Microsoft Active Directory Active
on Windows servers. Active Directory Directory,
Service is a Windows server directory boot into
service that enables you to manage Directory
data structures distributed over a restore
network. For example, Active mode. Files
Directory Service stores information will be
about user accounts, passwords, phone restored if
numbers, profiles, and installed they can be
services. It provides methods for overwritten.
storing directory data and making this
data available to network users and
administrators.

Registry This VSS writer using a custom API, Custom

Writer is used to back up and restore restore
Windows Registry. Windows Registry method
is a database repository of information
containing the Windows system
configuration.

Remote This is a system writer used to back up Files are

Storage and restore Remote Storage Service restored
Writer (RSS). RSS is used to automatically after a
move infrequently accessed files from reboot.
local to remote storage. Remote files
are recalled automatically when the
file is opened.

Removable This is a system writer used to back up Files are

Storage and restore Removable Storage restored
Manager Manager Service. This service after a
Writer manages removable media, drives, and reboot.
libraries.

Chapter 5 197
 Integrating Microsoft Volume Shadow Copy Service with Data Protector
Writers Specifics

Table 5-1 Writer description

Writer Description Restore

Name Method

System This is a system writer that backs up a Files are

Writer specific set of Windows dynamic link restored
libraries (DLL). after a
reboot.

TermServLic This is a system writer that backs up Files are

encing Windows Terminal Services. These restored
Writer services provide a multi-session after a
environment that allows client reboot.
systems to access a virtual Windows
desktop session and Windows-based
programs running on the server.

WINS Jet This is a system writer, used to back Files are

Writer up and restore Windows Internet restored
Name Service (WINS). WINS is a after a
dynamic replicated database service reboot.
that can register and resolve NetBIOS
names to IP addresses used on a
TCP/IP network.

WMI Writer This is a system writer, used to back Files are

up and restore Windows Management restored
Instrumentation (WMI). WMI is a after a
unified management infrastructure in reboot.
Windows for monitoring system
resources.

198 Chapter 5
 Integrating Microsoft Volume Shadow Copy Service with Data Protector
Backing Up Writers Data

Backing Up Writers Data

To run backups and restores of the VSS-aware writers, you need to
configure the Data Protector MS Volume Shadow Copy integration
backup specifications.
To configure the backup using the VSS integration, perform the following
steps:

Configuration 1. Configure devices, media and media pools needed for the backup. See
Steps the HP OpenView Storage Data Protector Administrator’s Guide for
instructions.
2. Create a Data Protector VSS backup specification specifying the data
that you want to back up, the media and devices to which you want
your data to be backed up, as well as the Data Protector backup
options that define the behavior of your backup or restore session.

Creating Backup Specification Using GUI

The procedure below shows how to back up MS VSS objects using the
Data Protector GUI. Some writers have specific limitations. For writers
specific limitations, refer to the appropriate sections:

• For Microsoft Exchange Server 2003 specifics, refer to “Microsoft

Exchange Server 2003 Writer Specifics” on page 203.
You need to configure different backup specifications for cluster-aware
and non-cluster-aware writers. Refer to “Configuring the Data Protector
VSS Cluster-Aware Integration” on page 191.
To create a new backup specification for the VSS integration, proceed as
follows:

1. In the HP OpenView Storage Data Protector Manager, switch to

the Backup context.
2. In the Scoping Pane, expand Backup, and then Backup
Specifications.
3. Right-click MS Volume Shadow Copy Writers and then click Add
Backup. The Create New Backup dialog box is displayed.

Chapter 5 199
 Integrating Microsoft Volume Shadow Copy Service with Data Protector
Backing Up Writers Data

4. In the Create New Backup dialog box, click Blank Microsoft

Volume Shadow Copy Backup to select a template.

Figure 5-4 Selecting a Blank Template and Local or Network backup

Select Local or network backup for the backup type.

5. Specify the name of the client that has the VSSBAR agent installed.
When backing up cluster-aware writers (such as SQL Server via the
MSDE Writer), specify the name of the VSS client system as the
virtual server name given in the particular writer resource group.
Click Next.

200 Chapter 5
 Integrating Microsoft Volume Shadow Copy Service with Data Protector
Backing Up Writers Data

6. Select the backup objects you want to back up.

Figure 5-5 Selecting Backup Objects

You can specify a full client backup by selecting the top-level item (the
name of the client), a single writer or a writer’s component backup by
selecting a lower-level item.

NOTE In case a writer requires all of its components to be backed up, it is not
allowed to select lower-level items. To prevent from accidental selecting,
these items are not displayed in the GUI. If you select such a writer for
backup, all its components will be backed up.

If full client is selected, Data Protector checks which writers exist on

the client and backs up all of them at backup time.

Chapter 5 201
 Integrating Microsoft Volume Shadow Copy Service with Data Protector
Backing Up Writers Data

NOTE If a writer has no components to be backed up, it is not displayed in the

list of writers, and is not backed up when the full client is selected.

7. Following the wizard, select the devices, backup options, and schedule
your backup.
Select the device(s) you want to use for the backup. Click Properties
to set the device concurrency, media pool, and preallocation policy. For
more information on these options, click Help.
You can also specify whether you want to create additional copies
(mirrors) of the backup during the backup session. Specify the desired
number of mirrors by clicking the Add mirror and Remove mirror
buttons. Select separate devices for the backup and for each mirror.
For detailed information on the object mirror functionality, see HP
OpenView Storage Data Protector Administrator’s Guide.

TIP If you are not sure about selecting the backup options, keep the default
values.

Refer to online Help and the HP OpenView Storage Data Protector

Administrator’s Guide for details about the options common to all
Data Protector backup specifications.
8. Once you have defined all backup options and the schedule, you need
to name and save the newly-created backup specification.
You have now completed the creation of a MS Volume Shadow Copy
Writers backup specification.
9. You can review the newly-created and saved backup specification in
the Backup context, under the specified group of backup
specifications.
10. You can run backup using one of the following methods:

• Schedule the backup of an existing MS Volume Shadow Copy

Writers backup specification using the Data Protector Scheduler.
• Start an interactive backup of an existing MS Volume Shadow
Copy Writers backup specification.

202 Chapter 5
 Integrating Microsoft Volume Shadow Copy Service with Data Protector
Backing Up Writers Data

Microsoft Exchange Server 2003 Writer Specifics

Microsoft The following are Microsoft Exchange Server 2003 writer limitations:
Exchange 2003
Writer Limitations • A combination of VSS snapshot backups and incremental stream
backups is not possible.
• You can back up only the whole server or full storage groups. Single
stores cannot be backed up.
• Circular logging must be disabled; otherwise, only full backup
recovery is possible.
• Only one VSS backup session of the Microsoft Exchange Server 2003
Writer can be running at once on the application client.

Consistency The database can be successfully backed up only if the consistency check
Check of the replicated datafiles succeeded.
To disable consistency checking, set the
OB2VSS_EXCHANGE_DISABLE_CONSISTENCY_CHECK omnirc variable to 1.

Chapter 5 203
 Integrating Microsoft Volume Shadow Copy Service with Data Protector
Backing Up Writers Data

Figure 5-6 Selecting Microsoft Exchange Server 2003 Storage Groups

Scheduling the Backup

For more detailed information on scheduling, refer to the online Help
index keyword “scheduled backups”.
To schedule a MS Volume Shadow Copy Writers backup specification,
perform the following steps in the Data Protector GUI:

1. In the HP OpenView Storage Data Protector Manager, switch to

the Backup context.
2. In the Scoping Pane, expand Backup, then Backup Specifications.
Click MS Volume Shadow Copy Writers.
A list of available backup specifications is displayed in the Results
Area.
3. Double-click the backup specification you want to schedule and click
the Schedule tab to open the Schedule property page.

204 Chapter 5
 Integrating Microsoft Volume Shadow Copy Service with Data Protector
Backing Up Writers Data

4. In the Schedule property page, select a date in the calendar and click
Add to open the Schedule Backup dialog box.
5. Specify Recurring, Time options, Recurring options, and
Session options.
See Figure 5-7 on page 205.
6. Click OK to return to the Schedule property page.
7. Click Apply to save the changes.

Figure 5-7 Scheduling a Backup

Running an Interactive Backup

An interactive backup can be started using the Data Protector GUI by
following these steps:

1. In the HP OpenView Storage Data Protector Manager, switch to

the Backup context.
2. In the Scoping Pane, expand Backup; then expand the Backup
Specifications and the MS Volume Shadow Copy Writers items.

Chapter 5 205
Integrating Microsoft Volume Shadow Copy Service with Data Protector
Backing Up Writers Data

3. Right-click the backup specification you want to run, and then select
Start Backup from the pop-up menu.
The Start Backup dialog box appears.
Select the Full backup type and the network load
{High|Medium|Low}.
Refer to online Help for a description of network load.
4. Click OK. Upon successful completion of the backup session, a
Session Completed Successfully message appears.

206 Chapter 5
 Integrating Microsoft Volume Shadow Copy Service with Data Protector
Restoring Writers Data

Restoring Writers Data

You can restore the Data Protector MS Volume Shadow Copy integration
objects using the Data Protector GUI.

NOTE Data Protector first restores the Writer Metadata collected during the
backup time. This metadata contains the information about the backup
components and the restore method. Data Protector performs restore
according to the restore method specified by the writers.

Limitations for • Data Protector MS VSS integration does not automatically provide
Custom Restore any restore method for writers requesting custom restore. If a writer
specifies custom restore method, it is only possible to restore the
writer's data as plain files using the Data Protector restore
functionality. To do so, use the Restore Into option to specify the
restore path of these plain files. You can then perform the custom
restore from these plain files manually. For information on writer’s
custom restore, refer to the writers documentation.

NOTE Writers requiring custom restore methods are by default not shown by
Data Protector. The omnirc variable OB2_SHOWALLWRITERS must be set
to 1 for all writers to be displayed.

Restore Procedure
The procedure below shows how to restore MS VSS objects using the
Data Protector GUI. Some writers require custom restore procedures
and/or have specific limitations. Refer to the appropriate sections:

• For Microsoft Exchange 2003 Writer specifics refer to “Microsoft

Exchange Server 2003 Writer Restore Specifics” on page 211.
• For MSDE Writer specifics refer to “MSDE Writer Restore Specifics”
on page 209.

Chapter 5 207
 Integrating Microsoft Volume Shadow Copy Service with Data Protector
Restoring Writers Data

To restore MS VSS objects using the Data Protector GUI, proceed as

follows:

1. In the HP OpenView Storage Data Protector Manager, switch to

the Restore context.
2. Expand Restore and Microsoft Volume Shadow Copy Writers and
select the client from which you want to restore the data. In the
Results Area, a list of writers, which were backed up on this client, is
displayed.
3. In the Results Area, check the writers or writers’ components that
you want to restore.

Figure 5-8 Restore Objects

You can select the top-level item (full writer restore) or only specific
components. If you select a full writer restore, but some components
of this writer were not backed up in the same session, you cannot
select them (unavailable components are shaded).

208 Chapter 5
 Integrating Microsoft Volume Shadow Copy Service with Data Protector
Restoring Writers Data

To select the version (the date of a backup) from which you want to
restore, right-click the object name and click Properties. The last
backup version is selected by default, however, you can select a
different version from the drop-down list.
4. In the Options property page, select the MS Volume Shadow Copy
specific restore options. Refer to “Restore Options” on page 214.
5. In the Devices and Media property pages, the devices and media for
restore are automatically selected.
Note that you can change the device used for the restore. Therefore,
you have the possibility of using a different device for a restore than
the one that was used for the backup. Refer to the “Restoring Under
Another Device” section of the HP OpenView Storage Data Protector
Administrator’s Guide for more information on how to perform a
restore using another device.
6. Click the Restore MS Volume... button. Review your selection, and
then click Finish to start a restore session.
The restore session messages are displayed in the Results Area.
7. If you are restoring a VSS writer that requires a custom restore, the
restored files will be saved in a temporary location specified by the
Restore Into option. You can then restore them manually using
the writers specific methods, if it is provided by a writer. Refer to the
writers’ documentation.

MSDE Writer Restore Specifics

MSDE writer is used to back up and restore Microsoft SQL database.

IMPORTANT Before restoring the SQL system databases (master, model, msdb and
pub), you have to stop the SQL service.

Chapter 5 209
 Integrating Microsoft Volume Shadow Copy Service with Data Protector
Restoring Writers Data

Figure 5-9 MSDE writer

When you expand the MSDE Writer item in the Results Area, all
Microsoft SQL Server instances are displayed. Each instance contains all
databases it includes. System databases (master, model, msdb and pub)
are always listed there.

IMPORTANT If system databases are restored, the whole internal database structure
will be changed.

210 Chapter 5
 Integrating Microsoft Volume Shadow Copy Service with Data Protector
Restoring Writers Data

NOTE Only point-in-time restore is possible. Rollforward restore is not

supported.

User databases will be restored only if it is possible to overwrite the files.

MSDE writer will unlock user databases before the restore, while SQL
service will have to be stopped manually in order to restore the system
databases.

Microsoft Exchange Server 2003 Writer Restore

Specifics
Microsoft Exchange Server 2003 Writer is used to restore Microsoft
Exchange Server 2003 database files.
When restoring from a Microsoft Exchange 2003 backup, the following
two scenarios are possible:

• One or more databases are corrupted, but the log files are not
damaged. In this case the database is restored and transaction logs
are applied.
• The log files are corrupted or missing. In this case all databases and
log files need to be restored. A rollforward recovery of the database is
not possible.

Limitations The following limitations apply when restoring Microsoft Exchange

Server 2003:

• Shadow copies cannot be restored to alternate locations on the backup

client.
• You cannot restore the shadow copy to the Restore Storage Group.

Rollforward Recovery from the Loss of One or More Databases

For a rollforward recovery, perform the following steps:

1. Dismount all stores from the storage group in which the target store
resides using Microsoft Exchange System Manager.

Chapter 5 211
 Integrating Microsoft Volume Shadow Copy Service with Data Protector
Restoring Writers Data

2. Select the stores you want to recover. Make sure that the Logs
component is not selected. If this component is selected, a
point-in-time restore will be performed instead of a rollforward
recovery of the store(s).
3. Start the restore session.
4. Mount all stores from the storage group in which they reside using
Exchange System Manager. The selected stores are recovered.

Figure 5-10 Selecting Microsoft Exchange Server 2003 Stores for Rollforward
Recovery

Point-in-Time Restore After Loss of a Log File

To perform a point-in-time restore, perform the following steps:

1. Start Exchange System Manager and check if the storage group is

already unmounted. If not, unmount the whole group.

212 Chapter 5
 Integrating Microsoft Volume Shadow Copy Service with Data Protector
Restoring Writers Data

2. Select all stores including log files.

3. Start the restore session.
4. Mount the stores from the storage group in which the target stores
reside using Exchange System Manager. All stores are mounted and
put in the state as they were at the last full backup.

Figure 5-11 Selecting Microsoft Exchange Server 2003 Stores for

Point-in-Time Restore

Chapter 5 213
Integrating Microsoft Volume Shadow Copy Service with Data Protector
Restoring Writers Data

Restore Options
The following restore options are specific to the Data Protector MS
Volume Shadow Copy integration.
Restore to another client
By default, the target Data Protector MS Volume
Shadow Copy client is the client from which the
application data was backed up. However, you may
restore the data to another VSS client if you specify the
Restore to another client option. The new target
MS VSS client must be a part of the Data Protector
cell, it must run on the same platform and have the MS
Volume Shadow Copy Integration software component
installed.
Restore into the following directory
By default, you restore the data to the same directory
from which it was backed up (it can be on the original
client or on some other client which you selected).
However, if you specify the Restore into the
following directory option, your data will be
restored to another directory. When defining the
restore location, you can specify the path to the
directory where you want to restore your data.

214 Chapter 5
 Integrating Microsoft Volume Shadow Copy Service with Data Protector
Monitoring a VSS Backup and Restore

Monitoring a VSS Backup and Restore

The Data Protector GUI enables you to monitor current or view previous
backup and restore sessions.
Monitoring is automatically activated when you start a restore or a
backup interactively.

Monitoring Current Sessions

To monitor a currently running session using the Data Protector GUI,
proceed as follows:

1. In the Context List, click Monitor.

In the Results Area, all currently running sessions are listed. See
Figure 5-12.
2. Double-click the session you want to monitor.

Figure 5-12 Monitoring a Current Session

Clearing Sessions To remove all completed or aborted sessions from the Results Area of the
Monitor context, proceed as follows:

1. In the Scoping Pane, click Current Sessions.

2. In the Actions menu, select Clear Sessions. Or click the Clear
Sessions icon on the toolbar.
To remove a particular completed or aborted session from the current
sessions list, right-click the session and select Remove From List.

Chapter 5 215
 Integrating Microsoft Volume Shadow Copy Service with Data Protector
Monitoring a VSS Backup and Restore

NOTE All completed or aborted sessions are automatically removed from the
Results Area of the Monitor context if you restart the Data Protector
GUI.

For detailed information on a completed or aborted session, see “Viewing

Previous Sessions”.

Viewing Previous Sessions

To view a previous session using the Data Protector GUI, proceed as
follows:

1. In the Context List, click Internal Database.

2. In the Scoping Pane, expand Sessions to display all the sessions
stored in the IDB.
The sessions are sorted by date. Each session is identified by a session
ID consisting of a date in the YY/MM/DD format and a unique
number.
3. Right-click the session and select Properties to view details on the
session.
4. Click the General, Messages or Media tab to display general
information on the session, session messages, or information on the
media used for this session, respectively. See Figure 5-13.

216 Chapter 5
 Integrating Microsoft Volume Shadow Copy Service with Data Protector
Monitoring a VSS Backup and Restore

Figure 5-13 Viewing a Previous Session

Chapter 5 217
 Integrating Microsoft Volume Shadow Copy Service with Data Protector
Troubleshooting Integration

Troubleshooting Integration
This section describes the procedures you should follow to troubleshoot
the integration.

Before You Begin 1. Ensure that the latest official Data Protector patches are installed.
Refer to “Verifying Which Data Protector Patches Are Installed” in
the HP OpenView Storage Data Protector Installation and Licensing
Guide.
Refer to the HP OpenView Storage Data Protector Software Release
Notes or
http://www.openview.hp.com/products/datapro/spec_0001.html for an
up-to-date list of supported versions, platforms, and other
information.
2. Refer to the HP OpenView Storage Data Protector Software Release
Notes for general Data Protector limitations as well as known
problems and workarounds.

Restore Problems

Problem After the restore of system writers was aborted, the Windows
operating system is corrupted when you restart it.
If the restore of some system writers (for example, System Writer) is
aborted for any reason (hardware or software failure, manually aborted,
etc.), the Windows operating system may be corrupted after the restart
(for example, the GUI or some system services cannot be started, etc.).

Action Depending on the nature of the corruption, repair or re-install the

operating system from the Windows installation CD-ROM.

Problem Some components are not restored during the restore session.
If a component cannot be restored to the location specified in Writer
Metadata Document (for example, if this location is locked or it is not
possible to perform regular restore), this component will be skipped
during the restore procedure.

218 Chapter 5
 Integrating Microsoft Volume Shadow Copy Service with Data Protector
Troubleshooting Integration

Action Specify a location, where skipped files will be redirected in case of

failure, by setting the OB2VSS_DUMPTO environmental variable in the
<Data_Protector_home>\omnirc file. Restart the Data Protector
services to apply the changes in the omnirc file.

Example If you want the files that are skipped during the restore to be copied to
the F:\Restore directory, set OB2VSS_DUMPTO=F:\Restore in the
omnirc file. In case the SQL component Company was skipped during the
restore, it will be copied to the specified directory as follows:
F:\Restore\2002-12-09-23\G\SQL\Log\Company.ldf
F:\Restore\2002-12-09-23\G\SQL\Log\Company.mdf
The pathname includes the backup session ID and the pathname to the
original location.

Chapter 5 219
Integrating Microsoft Volume Shadow Copy Service with Data Protector
Troubleshooting Integration

220 Chapter 5
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 one (or
manages the Automated Cartridge more) archived log destination(s). This
System (ACS). copy is the Archived Redo Log. The
presence or absence of an Archived
Active Directory (Windows specific Redo Log is determined by the mode
term) that the database is 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 from an instance and disk
provide a consistent way to name, failure. The “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 interface defines a set of routines to

configuration) and automatic recovery allow the reading and writing of data to
of the original system configuration and the backup media, the creation,
user data that was backed up during the searching and removing the backup
full client backup. files.
These files are stored as an ASR archive
file on the Cell Manager (in backup chain
<Data_Protector_home>\Config\Serve This relates to a situation where full and
r\dr\asr on a Windows Cell Manager or incremental backups are performed.
in /etc/opt/omni/server/dr/asr/ on a Based on the level of the incremental
UNIX Cell Manager) as well as on the backups used (Incr, Incr 1, Incr 2, and so
backup medium. The ASR archive file is on), simple or rather complex
extracted to three diskettes for 32-bit dependencies of incrementals to
Windows systems or four diskettes for previous incrementals can exist. The
64-bit Windows systems after a disaster backup chain are all backups, starting
occurs. You need these diskettes to from the full backup plus all the
perform ASR. dependent incrementals up to the
desired point in time.
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
BACKINT (SAP R/3 specific term) drive or a library.
SAP R/3 backup programs can call the
Data Protector backint interface backup generation
program via an open interface, which One backup generation includes one full
enables them to communicate with Data backup and all incremental backups
Protector software. For backup and until the next full backup.
restore, SAP R/3 programs issue orders
for the Data Protector backint interface. backup ID
An identifier of an integration object
backup API that equals the session ID of the backup
The Oracle interface between the Oracle of this object. The backup ID is
backup/restore utility and the backup/ preserved when an object is copied,
restore media management layer. The 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 backup device to perform the backup StorageWorks Disk Array XP LDEVs
of the data in a replica. for purposes such as data backup or data
See also application system, target duplication. The copies (secondary
volume, and replica. volumes or S-VOLs) can be separated
from the primary volumes (P-VOLs)
backup types and connected to a different system for
See incremental backup, differential various purposes, such as backup and
backup, transaction backup, full development. For backup purposes, P-
backup and delta backup. VOLs should be connected to the
application system, and one of the S-
backup view VOL mirror sets to the backup system.
Data Protector provides different views See also HP StorageWorks Disk
for backup specifications: By Type - Array XP LDEV, CA, Main Control
according to the type of data available Unit, application system, and backup
for backups/templates. Default view. By system.
Group - according to the group to which
backup specifications/templates belong. BC Process (EMC Symmetrix specific
By Name - according to the name of term)
backup specifications/templates. By A protected storage environment
Manager - if you are running MoM, you solution that has defined specially
can also set the Backup view according configured EMC Symmetrix devices as
to the Cell Manager to which backup mirrors or Business Continuance
specifications/templates belong. Volumes to protect data on EMC
Symmetrix standard devices.
BC (EMC Symmetrix specific term) See also BCV.
Business Continuance are processes that
allow customers to access and manage BC VA (HP StorageWorks Virtual Array
specific term)
Business Copy VA allows you to

G-4
Glossary

maintain internal copies of HP multi-word search, AND is used by

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

G-5
Glossary

• 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 CAP (StorageTek specific term)
Cartridge Access Port is a port built into
You can specify files, tablespaces, the door panel of a library. The purpose
complete backups, log sequence is to enter or eject media.
numbers of redo log files, or the session
ID of the backup. catalog protection
See also SAPDBA, BRBACKUP and Defines how long information about
BRARCHIVE. backed up data (such as file names and
file versions) is kept in the IDB.
BSM See also data protection.
The Data Protector Backup Session
Manager controls the backup session. CDB
This process always runs on the Cell The Catalog Database is a part of the
Manager system. IDB that contains information about
backups, object copies, restores, media
CA (HP StorageWorks Disk Array XP management sessions, and backed up
specific term) data. Depending on the selected logging
Continuous Access XP allows you to level, it also contains file names and file
create and maintain remote copies of HP versions. This part of the database is
StorageWorks Disk Array XP LDEVs always local to the cell.
for purposes such as data duplication, See also MMDB.
backup, and disaster recovery. CA
operations involve the main (primary) CDF file (UNIX specific term)
disk arrays and the remote (secondary) A Context Dependent File is a file
disk arrays. The main disk arrays consisting of several files grouped under
contain the CA primary volumes (P- the same pathname. The system
VOLs), which contain the original data ordinarily selects one of the files using
and are connected to the application the context of the process. This
system. The remote disk arrays contain mechanism allows machine dependent
the CA secondary volumes (S-VOLs) executables, system data, and device
connected to the backup system. files to work correctly from all hosts in a
See also BC (HP StorageWorks Disk cluster while using the same pathname.

G-6
Glossary

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.
If the specified channel is type
Cell Manager ‘SBT_TAPE’ and Oracle is integrated
The main system in the cell where the with Data Protector, the server process
essential Data Protector software is will attempt to read backups from or
installed and from which all backup and write data files to Data Protector.
restore activities are managed. The GUI
used for management tasks can be circular logging (Microsoft Exchange
located on a different system. Each cell Server and Lotus Domino Server
has one Cell Manager system. specific term)
Circular logging is a Microsoft
centralized licensing Exchange Server database and Lotus
Data Protector allows you to configure Domino Server database mode, in which
centralized licensing for the whole the transaction log file contents are
enterprise environment consisting of periodically overwritten after the
several cells. All Data Protector licenses corresponding data is committed to the
are installed and kept on the Enterprise database. Circular logging reduces disk
Cell Manager system. You can then storage space requirements.
allocate licenses to specific cells to suit
your needs. client backup
See also MoM. A backup of all filesystems mounted on
a client. Filesystems mounted on the
Centralized Media Management client after the backup specification was
Database (CMMDB) created are not automatically detected.
See CMMDB.
client backup with disk discovery
channel (Oracle specific term) A backup of all filesystems mounted on
An Oracle Recovery Manager resource a client. When the backup starts, Data
allocation. Every allocated channel Protector discovers the disks on the
starts a new Oracle process, which clients. Client backup with disk

G-7
Glossary

discovery simplifies backup robotics, serving the devices that are

configuration and improves backup connected to systems in other cells.
coverage of systems that often mount or The CMMDB must reside on the MoM
dismount disks. Manager. A reliable network connection
between the MoM cell and the other
client or client system Data Protector cells is highly
Any system configured with any Data recommended
Protector functionality and configured See also MoM.
in a cell.
COM+ Registration Database
cluster-aware application (Windows specific term)
It is an application that supports the The COM+ Registration Database and
cluster Application Programming the Windows Registry store COM+
Interface. Each cluster-aware application attributes, class attributes,
application declares its own critical and computer-level attributes. This
resources (disk volumes (on Microsoft guarantees consistency among these
Cluster Server), volume groups (on MC/ attributes and provides common
ServiceGuard), application services, IP operation on top of these attributes.
names and addresses ...).
command-line interface
CMD Script for OnLine Server A set of DOS and UNIX like commands
(Informix specific term) that you can use in shell scripts to
Windows CMD script that is created in perform Data Protector configuration,
INFORMIXDIR when Informix OnLine backup, restore, and management tasks.
Server is configured. The CMD script is
a set of system commands that export Command View (CV) EVA (HP
environment variables for OnLine StorageWorks EVA specific term)
Server. The user interface that allows you to
configure, manage, and monitor your
CMMDB HP StorageWorks EVA storage system.
The Data Protector Centralized Media It is used to perform various storage
Management Database (CMMDB) is the management tasks, for example,
result of merging MMDBs from several creating virtual disk families, managing
cells in the MoM environment. It allows storage system hardware, creating
you to share high-end devices and media snapclones and snapshots of virtual
across multiple cells in a MoM disks. The Command View EVA
environment. One cell can control the software runs on the HP OpenView

G-8
Glossary

Storage Management Appliance, and is data file (Oracle and SAP R/3 specific
accessed by a Web browser. term)
See also HP StorageWorks EVA Agent A physical file created by Oracle that
(legacy) and HP StorageWorks EVA contains data structures such as tables
SMI-S Agent. and indexes. A data file can only belong
to one Oracle database.
concurrency
See Disk Agent concurrency. data protection
Defines how long the backed up data on
control file (Oracle and SAP R/3 media remains protected, that is, Data
specific term) Protector will not overwrite it. When the
An Oracle data file that contains entries protection expires, Data Protector will
specifying the physical structure of the be able to reuse the media in one of the
database. It provides database next backup sessions.
consistency information used for See also catalog protection.
recovery.
Data Protector Event Log
CRS A central repository of all Data
The Cell Request Server process Protector related notifications. By
(service) runs on the Data Protector Cell default, all notifications are sent to the
Manager. It starts and controls the Event Log. The Event Log is accessible
backup and restore sessions. The service only to Data Protector users in the
is started as soon as Data Protector is Admin group and to Data Protector
installed on the Cell Manager. users who are granted the Reporting and
CRS runs under the account root on notifications user rights. You can view
UNIX systems, and under any Windows or delete all events in the Event Log.
account. By default, it runs under the
account of the user, specified at Data Protector user account
installation time. You can use Data Protector only if you
have a Data Protector user account,
CSM which restricts unauthorized access to
The Data Protector Copy Session Data Protector and to backed up data.
Manager process controls the object Data Protector administrators create this
copy session and runs on the Cell account specifying a user logon name,
Manager system. the systems from which the user can log
on, and a Data Protector user group

G-9
Glossary

membership. This is checked whenever which occupies approximately 80% of

the user starts the Data Protector user the IDB. The default DC directory is
interface or performs specific tasks. called the dcbf directory and is located
in the <Data_Protector_home>\db40
data stream directory on a Windows Cell Manager
Sequence of data transferred over the and in the /var/opt/omni/server/db40
communication channel. directory on a UNIX Cell Manager. You
can create more DC directories and
database library locate them as appropriate to you. Up to
A Data Protector set of routines that 10 DC directories are supported per cell.
enables data transfer between Data The default maximum size of a DC
Protector and a server of an online directory is 4 GB.
database integration, for example, the
Oracle Server. DCBF
The Detail Catalog Binary Files (DCBF)
database parallelism part of the IDB stores information about
More than one database is backed up at file versions and attributes. It occupies
a time if the number of available devices approximately 80% of the IDB. One DC
allows you to perform backups in binary file is created for each Data
parallel. Protector medium used for backup.

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 specific term) device

An Informix physical database object. It A physical unit which contains either
can be a blobspace, dbspace, or logical- just a drive or a more complex unit such
log file. as a library.

DC directory device chain

The Detail Catalog (DC) directory A device chain consists of several
consists of DC binary files, which store standalone devices configured for
information about file versions. It sequential use. When a medium in one
represents the DCBF part of the IDB,

G-10
Glossary

device gets full, the backup differential backup

automatically continues on a medium in An incremental backup (incr) based on
the next device in the device chain. any previous Data Protector backup (full
or any incremental), which must still be
device group (EMC Symmetrix specific protected.
term) See incremental backup.
A logical unit representing several EMC
Symmetrix devices. A device cannot differential backup (MS SQL specific
belong to more than a single device term)
group. All devices in a device group A database backup that records only the
must be on the same EMC Symmetrix data changes made to the database after
unit. You can use a device group to the last full database backup.
identify and work with a subset of the See also backup types.
available EMC Symmetrix devices.
differential database backup
device streaming A differential database backup records
A device is streaming if it can feed only those data changes made to the
enough data to the medium to keep it database after the last full database
moving forward continuously. backup.
Otherwise, the tape has to be stopped,
the device waits for more data, reverses direct backup
the tape a little and resumes to write to A SAN-based backup solution in which
the tape, and so on. In other words, if the data movement directly from disk to
data rate written to the tape is less or tape (or to other secondary storage) is
equal the data rate which can be facilitated by the SCSI Extended Copy
delivered to the device by the computer (Xcopy) command. Direct backup
system, then the device is streaming. lessens the backup I/O load on systems
Streaming significantly improves the in a SAN environment. The data
performance of the device and use of movement is facilitated directly from
space. disk to tape (or to other secondary
storage) by the SCSI Extended Copy
DHCP server (XCopy) command. The command is
A system running the Dynamic Host provided by any element of the
Configuration Protocol (DHCP) infrastructure including bridges,
providing dynamic configuration of IP switches, tape libraries, and disk
addresses and related information. subsystems.
See also XCopy engine.

G-11
Glossary

directory junction (Windows specific Disk Agent concurrency

term) The number of Disk Agents that are
Directory junctions use the reparse point allowed to send data to one Media
concept of Windows. An NTFS 5 Agent concurrently.
directory junction allows you to redirect
a directory/file request to another disk discovery
location. The detection of disks during client
backup with disk discovery. During this
Directory Store (DS) (Microsoft backup, Data Protector discovers
Exchange specific term) (detects) the disks that are present on the
A part of the Microsoft Exchange Server client — even though they might not
directory. The Microsoft Exchange have been present on the system when
Server directory contains objects used the backup was configured — and backs
by Microsoft Exchange applications in them up. This is particularly useful in
order to find and access services, dynamic environments, where
mailboxes, recipients, public folders, configurations change rapidly. After the
and other addressable objects within the disks are expanded, each inherits all
messaging system. options from its master client object.
See also Information Store (MDB). Even if pre- and post-exec commands
are specified once, they are started many
disaster recovery times, once per each object.
A process to restore a client’s main
system disk to a state close to the time disk group (Veritas Volume Manager
when a (full) backup was performed. specific term)
The basic unit of data storage in VxVM
Disk Agent system. A disk group can consist of one
A component needed on a client to back or more physical volumes. There can be
it up and restore it. The Disk Agent more than one disk group on the system.
controls reading from and writing to a
disk. During a backup session, the Disk disk image (rawdisk) backup
Agent reads data from a disk and sends A high-speed backup where Data
it to the Media Agent, which then moves Protector backs up files as bitmap
it to the device. During a restore session images. A disk image (rawdisk) backup
the Disk Agent receives data from the does not track the files and directory
Media Agent and writes it to the disk. structure stored on the disk, but stores a
disk image structure on byte level. You

G-12
Glossary

can perform a disk image backup of (Internet). It prevents outside users from
either specific disk sections or a getting direct access to company servers
complete disk. in the intranet.

disk quota DNS server

A concept to manage disk space In the DNS client-server model, this is
consumption for all or a subset of users the server containing information about
on a computer system. This concept is a portion of the DNS database that
used by several operating system makes computer names available to
platforms. client resolvers querying for name
resolution across the Internet.
disk staging
The process of backing up data in domain controller
several phases to improve the A server in a network that is responsible
performance of backups and restores, for user security and verifying
reduce costs of storing the backed up passwords within a group of other
data, and increase the data availability servers.
and accessibility for restore. The backup
stages consist of backing up data to one DR image
media type first (for example disk) and Data required for temporary disaster
later copying it to a different media type recovery operating system (DR OS)
(for example tape). installation and configuration.

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
data with the original configuration data.

G-13
Glossary

drive Enterprise Backup Environment

A physical unit that receives data from a Several cells can be grouped together
computer system and can write it onto a and managed from a central cell. The
magnetic medium (typically a tape enterprise backup environment includes
drive). It can also read the data from the all clients located in several Data
medium and send it to the computer Protector cells which are managed and
system. administered from a central cell using
the Manager-of-Managers concept.
drive index See also MoM.
A number that identifies the mechanical
position of a drive inside a library Event Logs
device. This number is used by the Files in which Windows logs all events,
robotic control to access a drive. such as the starting or stopping of
services and the logging on and off of
dynamic client users. Data Protector can back up
See client backup with disk discovery. Windows Event Logs as part of the
Windows configuration backup.
EMC Symmetrix Agent (SYMA)
exchanger
(EMC Symmetrix specific term)
Also referred to as SCSI Exchanger.
See Symmetrix Agent (SYMA)
See also library.
emergency boot file (Informix specific
exporting media
term)
A process that removes all data about
An Informix configuration file that
backup sessions, such as systems,
resides in the <INFORMIXDIR>\etc
objects, and file names, which reside on
directory (on HP-UX) or
the media from the IDB. Information
<INFORMIXDIR>/etc directory (on
about the media and their relation to a
Windows) and is called
pool is also removed from the IDB. The
ixbar.<server_id>, where
data on the media remains unchanged.
<INFORMIXDIR> is the OnLine Server
See also importing media.
home directory and <server_id> is the
value of the SERVERNUM
configuration parameter. Each line of
the emergency boot file corresponds to
one backup object.

G-14
Glossary

Extensible Storage Engine (ESE) environment. On one side of the bridge

or multiplexer there is a Fibre Channel
(Microsoft Exchange Server 2000/2003
interface while on the other side there
specific term)
are parallel SCSI ports. The bridge or
A database technology used as a storage
multiplexer enables SCSI packets to be
system for information exchange in
moved between the Fibre Channel and
Microsoft Exchange Server 2000/2003.
parallel SCSI devices.
failover
file depot
Transferring of the most important
A file containing the data from a backup
cluster data, called group (on Windows)
to a file library device.
or package (on Unix) from one cluster
node to another. A failover can occur
file jukebox device
mostly because of software or hardware
A device residing on disk consisting of
failures or maintenance on the primary
multiple slots used to store file media.
node.
file library device
FC bridge
A device which resides on a disk
See Fibre Channel bridge
emulating a library with several media,
hence containing multiple files, referred
Fibre Channel
to as file depots.
An ANSI standard for high-speed
computer interconnection. Using either
File Replication Service (FRS)
optical or copper cables, it allows the
A Windows service that replicates the
high speed bidirectional transmission of
domain controller store logon scripts
large data files and can be deployed
and group policies. FRS also enables
between sites kilometers apart.
replication of Distributed File System
Fibre Channel connects nodes using
(DFS) shares between systems and
three physical topologies: point-to-
allows any server to perform replication
point, loop, and switched.
activity.
Fibre Channel bridge
file version
A Fibre Channel bridge or multiplexer
The same file can be backed up multiple
provides the ability to migrate existing
times in case of full backups and
parallel SCSI devices, like RAID arrays,
incremental backups (if the file
solid state disks (SSD), and tape
changed). If the log level ALL is
libraries to a Fibre Channel
selected for backup, Data Protector

G-15
Glossary

retains one entry in the IDB for the not formatted until the protection
filename itself and one for each version expires or the media are unprotected/
(date/time) of the file. recycled.

filesystem free pool

The organization of files on a hard disk. An auxiliary source of media for use by
A filesystem is backed up so that the file media pools when they run out of media.
attributes and the file contents are stored The media pools must be configured to
on the backup media. use free pools.

first level mirror (HP StorageWorks full backup

Disk Array XP specific term) A backup in which all selected objects
HP StorageWorks Disk Array XP allows are backed up, whether or not they have
up to three mirror copies of a Primary been recently modified.
Volume and each of these copies can See also backup types.
have additional two copies. The three
mirror copies are called first level full database backup
mirrors. A backup of all data in a database, not
See also Primary Volume, and MU only the data that has been changed after
numbers. the last (full or incremental) backup of
the database. A full database backup
fnames.dat does not depend on any other backup.
The fnames.dat files of the IDB contain
information on the names of the backed full mailbox backup
up files. Typically, these files occupy A full mailbox backup is a backup of the
about 20% of the IDB, if filenames are entire mailbox content.
stored.
global options file
formatting A file that allows you to customize Data
A process that erases any data contained Protector. It explains the global options,
on a medium and prepares it for use with which cover various aspects of Data
Data Protector. Information about media Protector, typically time-outs and limits,
(media ID, description, and location) is and affect the entire Data Protector cell.
saved in the IDB as well as on the The file is located in the /etc/opt/omni/
respective media (media header). Data server/options directory on HP-UX and
Protector media with protected data are Solaris systems and in the

G-16
Glossary

<Data_Protector_home>\Config\Serve less expensive optical platters. When

r\Options directory on Windows needed, the data is migrated back to
systems. hard disk storage. This balances the
need for fast retrieval from hard disk
group (Microsoft Cluster Server with the lower cost of optical platters.
specific term)
A collection of resources (for example Holidays file
disk volumes, application services, IP A file that contains information about
names and addresses) that are needed to holidays. You can set different holidays
run a specific cluster-aware applications. by editing the Holidays file: /etc/opt/
omni/server/Holidays on the UNIX Cell
GUI Manager and
A cross-platform (HP-UX, Solaris, and <Data_Protector_home>\Config\Serve
Windows) graphical user interface, r\holidays on the Windows Cell
provided by Data Protector for easy Manager.
access to all configuration,
administration, and operation tasks. host backup
See client backup with disk discovery.
hard recovery (Microsoft Exchange
Server specific term) hosting system
A Microsoft Exchange Server database A working Data Protector client used for
recovery that is performed after a restore Disk Delivery Disaster Recovery with a
by the database engine, using Data Protector Disk Agent installed.
transaction log files.
HP ITO
heartbeat See OVO.
A cluster data set with a time stamp
carrying information about the HP OpC
operational status of a particular cluster See OVO.
node. This data set or packet is
distributed among all cluster nodes. HP OpenView SMART Plug-In (SPI)
A fully integrated, out-of-the-box
Hierarchical Storage Management solution which "plugs into" HP
(HSM) OpenView Operations, extending the
A method for optimizing the use of managed domain. Through the Data
expensive hard disk storage by Protector integration, which is
migrating less frequently used data to implemented as an HP OpenView

G-17
Glossary

SMART Plug-In, a user can have an HP StorageWorks EVA SMI-S Agent

arbitrary number of Data Protector Cell A Data Protector software module that
Managers monitored as an extension to executes all tasks required for the HP
HP OpenView Operations (OVO). StorageWorks Enterprise Virtual Array
integration operating on HP
HP OVO StorageWorks EVA with Command
See OVO. View (CV) EVA software starting with
v3.2. With the EVA SMI-S Agent, the
HP StorageWorks Disk Array XP control over the array is established
LDEV through HP StorageWorks SMI-S EVA
A logical partition of a physical disk provider, which directs communication
within an HP StorageWorks Disk Array between incoming requests and CV
XP. LDEVs are entities that can be EVA.
replicated in the Continuous Access XP See also Command View (CV) EVA,
(CA) and Business Copy XP (BC) HP StorageWorks SMI-S EVA
configurations, or can be used as provider, and HP StorageWorks EVA
standalone entities. Agent (legacy).
See also BC (HP StorageWorks Disk
Array XP specific term), CA (HP HP StorageWorks SMI-S EVA
StorageWorks Disk Array XP specific provider
term), and replica. An interface used for controlling HP
StorageWorks Enterprise Virtual Array.
HP StorageWorks EVA Agent SMI-S EVA provider runs as a separate
(legacy) service on the HP OpenView Storage
A Data Protector software module that Management Appliance system and acts
executes all tasks required for the HP as a gateway between incoming requests
StorageWorks Enterprise Virtual Array and Command View EVA. With the
integration operating on HP Data Protector HP StorageWorks EVA
StorageWorks EVA with Command integration, SMI-S EVA provider
View (CV) EVA software v3.1 or lower, accepts standardized requests from the
and the EVA VCS firmware v3.01x or EVA SMI-S Agent, communicates with
lower. Command View EVA for information or
See also Command View (CV) EVA method invocation, and returns
and HP StorageWorks EVA SMI-S standardized responses.
Agent. See also HP StorageWorks EVA SMI-

G-18
Glossary

S Agent and Command View (CV) importing media

EVA. A process that re-reads all data about
backup sessions which are on the
medium back into the IDB. This then
HP StorageWorks Virtual Array allows for fast and convenient access to
LUN the data on the media.
A logical partition of a physical disk See also exporting media.
within an HP StorageWorks Virtual
Array. LUNs are entities that can be incremental backup
replicated in the HP StorageWorks A backup that selects only files that have
Business Copy VA configuration, or can changed since a previous backup.
be used as standalone entities. Several levels of incremental backup are
See also BC VA and replica. available, allowing selective backup of
only files that have changed since the
HP VPO last incremental backup.
See OVO. See also backup types.

ICDA (EMC Symmetrix specific term) incremental backup (Microsoft

EMC's Symmetrix Integrated Cached Exchange Server specific term)
Disk Arrays (ICDA) is a disk array A backup of the Microsoft Exchange
device that combines a set of physical Server data that has changed since the
disks, a number of FWD SCSI channels, last full or incremental backup. With the
an internal cache memory, and control incremental backup, only the transaction
and diagnostic software commonly log files are backed up.
referred to as the microcode. See also backup types.

IDB incremental mailbox backup

The Data Protector Internal Database is An incremental mailbox backup backs
an embedded database located on the up all the changes made to the mailbox
Cell Manager that keeps information after the last backup of any type.
regarding which data is backed up, on
which media it is backed up, how incremental1 mailbox backup
backup and restore sessions are run, and An incremental1 mailbox backup backs
which devices and libraries are up all the changes made to the mailbox
configured. after the last full backup.

G-19
Glossary

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 Inet
mirrored medium. The EMC Symmetrix A process that runs on each UNIX
devices must have been previously system or service that runs on each
paired. Windows system in the Data Protector
In SRDF control operations, an cell. It is responsible for communication
incremental establish causes the target between systems in the cell and for
(R2) device to be synchronized starting other processes needed for
incrementally and to function as an backup and restore. The Inet service is
EMC Symmetrix mirrored medium. The started as soon as Data Protector is
EMC Symmetrix devices must have installed on a system. The Inet process
been previously paired. is started by the inetd daemon.

incremental restore (EMC Symmetrix Information Store (Microsoft

specific term) Exchange Server 2000/2003 specific
A BCV or SRDF control operation. term)
In BCV control operations, an The Microsoft Exchange Server 2000/
incremental restore reassigns a BCV 2003 service that is responsible for
device as the next available mirror of the storage management. Information Store
standard device in the pair. However, the in Microsoft Exchange Server 2000/
standard devices are updated with only 2003 manages two kinds of stores:
the data that was written to the BCV mailbox stores and public folder stores.
device during the time of the original A mailbox store consists of mailboxes
pair split, and the data that was written that belong to individual users. A public
to the standard device during the split is folder store contains public folders and
overwritten with data from the BCV messages that are shared among several
mirror. In SRDF control operations, an users.
incremental restore reassigns a target See also Key Management Service and
(R2) device as the next available mirror Site Replication Service.
of the source (R1) device in the pair.
However, the source (R1) devices are
updated with only the data that was

G-20
Glossary

Information Store (Microsoft used for remote installation of Data

Exchange Server 5.5 specific term) Protector clients. In mixed environments
This is the default message store at least two Installation Servers are
provider for the Microsoft Exchange needed: one for UNIX systems and one
Server 5.5. Information Store consists of for Windows systems.
the following stores:
instant recovery (ZDB specific term)
• public information store A process in which a replica, produced
by a ZDB-to-disk or a ZDB-to-
• private information store disk+tape sessions, is used to restore the
contents of the source volumes to their
• personal folder store states at the time at which the replica
was created, avoiding the need to
• offline information store. perform a restore from tape. Depending
on the application/database concerned,
The public information store contains this may be all that is required, or other
public folders and messages that can be steps, such as the application of
shared among multiple users and transaction log files, may be required for
applications. A single public store is full recovery.
shared by all users within an Exchange See also replica, zero downtime
Server 5.5 organization, even if multiple backup (ZDB), ZDB to disk, and ZDB
Exchange Servers are used. The private to disk+tape.
information store consists of mail boxes
that can belong to users or to integrated security (MS SQL specific
applications. The mail boxes reside on term)
the server running the Exchange Server Integrated security allows the Microsoft
5.5. SQL Server to use Windows
See also Directory Store (DS). 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

G-21
Glossary

Server are referred to as trusted jukebox device

connections. Only trusted connections A device consisting of multiple slots
are allowed. used to store either optical or file media.
When being used to store file media, the
integration object jukebox device is known as the “file
A backup object of a Data Protector jukebox device”.
integration, such as Oracle or SAP DB.
Key Management Service (Microsoft
Internet Information Server (IIS) Exchange Server 2000/2003 specific
term)
(Windows specific term)
The Microsoft Exchange Server 2000/
Microsoft Internet Information Server is
2003 service that provides encryption
a network file and application server that
functionality for enhanced security.
supports multiple protocols. Primarily,
See also Information Store and Site
IIS transmits information in Hypertext
Replication Service.
Markup Language (HTML) pages by
using the Hypertext Transport Protocol
LBO (EMC Symmetrix specific term)
(HTTP).
A Logical Backup Object (LBO) is an
object of data storage/retrieval in the
IP address
EMC Symmetrix environment. It is
Internet Protocol address is a numeric
stored/retrieved by EMC Symmetrix as
address of a system used to uniquely
one entity and can only be restored as a
identify the system on the network. The
whole.
IP address consists of four groups of
numbers separated by periods (full
library
stops).
Also called autochanger, jukebox,
autoloader, or exchanger. A library
ISQL (Sybase specific term)
contains media in repository slots. Each
A Sybase utility used to perform system
slot holds one medium (for example,
administration tasks on Sybase SQL
DDS/DAT). Media are moved between
Server.
slots and drives by a robotic mechanism,
allowing random access to media. The
ITO
library can contain multiple drives.
See OVO.
lights-out operation or unattended
jukebox
operation
See library.
A backup or restore operation that takes

G-22
Glossary

place outside of normal business hours target system is searched for locally
without an operator. This implies that no attached devices. If only one device is
operator personnel is present to work found, it is automatically used.
with the backup application or service Otherwise, Data Protector prompts you
mount requests, for example. to select the device, which will be used
for restore.
LISTENER.ORA (Oracle specific
term) lock name
An Oracle configuration file that You can configure the same physical
describes one or more Transparent device several times with different
Network Substrate (TNS) listeners on a characteristics, by using different device
server. names.

load balancing The lock name is a user specified string

By default, Data Protector automatically that is used for locking all such device
balances the usage of devices selected configurations to prevent collision if
for backup, so that they are used evenly. several such devices (device names) are
Load balancing optimizes the device used concurrently. Use an identical lock
usage by balancing the number of name for all device definitions which
objects written to each device. Since use the same physical device.
load balancing is done automatically
during backup time, you do not need to log_full shell script (Informix UNIX
manage how the data is actually backed specific term)
up. You just specify the devices to be A script provided by ON-Bar that you
used. If you do not want to use load can use to start backing up logical-log
balancing, you can select which device files when OnLine Server issues a log-
will be used for each object in the full event alarm. The Informix
backup specification. Data Protector ALARMPROGRAM configuration
will access the devices in the specified parameter defaults to the
order. <INFORMIXDIR>/etc/log_full.sh,
where <INFORMIXDIR> is the OnLine
local and remote recovery Server home directory. If you do not
Remote recovery is performed if all want logical logs to be backed up
Media Agent hosts specified in the SRD continuously, set the
file are accessible. If any of them fails, ALARMPROGRAM configuration
the disaster recovery process fails over parameter to <INFORMIXDIR>/etc/
to the local mode. This means that the no_log.sh.

G-23
Glossary

logging level login information to the Oracle

The logging level determines the Target Database (Oracle and SAP R/3
amount of details on files and directories specific term)
written to the IDB during backup or The format of the login information is
object copying. You can always restore <user_name>/<password>@<service>,
your data, regardless of the logging level where:
used during backup. Data Protector
provides four logging levels: Log All, • <user_name> is the name by which
Log Directories, Log Files, and No Log. a user is known to Oracle Server and
The different logging level settings to other users. Every user name is
influence the IDB growth, backup associated with a password and both
speed, and the convenience of browsing have to be entered to connect to an
data for restore. Oracle Target Database. This user
must have been granted Oracle
logical-log files SYSDBA or SYSOPER rights.
This applies to online database backup.
Logical-log files are files in which • <password> is a string used for data
modified data is first stored before being security and known only to its
flushed to disk. In the event of a failure, owner. Passwords are entered to
these logical-log files are used to roll connect to an operating system or
forward all transactions that have been software application. The password
committed as well as roll back any has to be the same as the password
transactions that have not been specified in the Oracle password file
committed. (orapwd), which is used for
authentication of users performing
login ID (MS SQL Server specific term) database administration.
The name a user uses to log on to
Microsoft SQL Server. A login ID is • <service> is the name used to
valid if Microsoft SQL Server has an identify an SQL*Net server process
entry for that user in the system table for the target database.
syslogin.
login information to the Recovery
Catalog Database (Oracle specific
term)
The format of the login information to
the Recovery (Oracle) Catalog Database
is <user_name>/

G-24
Glossary

<password>@<service>, where the personal folders is designated as the e-

description of the user name, password, mail delivery location, e-mail is routed
and service name is the same as in the from the mailbox to this location.
Oracle SQL*Net V2 login information
to the Oracle target database. In this Mailbox Store (Microsoft Exchange
case, <service> is the name of the Server 2000/2003 specific term)
service to the Recovery Catalog A part of the Information Store that
Database, not the Oracle target database. maintains information about user
mailboxes. A mailbox store consists of a
Note that the Oracle user specified here binary rich-text .edb file and a streaming
has to be the owner of the Oracle native internet content .stm file.
Recovery (Oracle) Catalog.
Main Control Unit (MCU) (HP
Lotus C API (Lotus Domino Server StorageWorks Disk Array XP specific
specific term) term)
An interface for the exchange of backup An HP StorageWorks XP disk array that
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

G-25
Glossary

medium and sends it to the Disk Agent. media condition factors

The Disk Agent then writes the data to The user-assigned age threshold and
the disk. A Media Agent also manages overwrite threshold used to determine
the robotics control of a library. the state of a medium.

MAPI (Microsoft Exchange specific media ID

term) A unique identifier assigned to a
The MAPI (Messaging Application medium by Data Protector.
Programming Interface) is the
programming interface that lets media label
applications and messaging clients A user-defined identifier used to
interact with messaging and information describe a medium.
systems.
media location
media allocation policy A user-defined physical location of a
Determines in which sequence media medium, such as "building 4" or "off-
are used for backup. The Strict site storage".
allocation policy directs Data Protector
to prompt for a specific medium. The media management session
Loose policy directs Data Protector to A session performing some action on a
prompt for any suitable medium. The medium, such as initializing, scanning
Formatted First policy directs Data the content, verifying data on a medium,
Protector to give preference to unknown or copying a medium.
media, even if unprotected media are
available in the library. media pool
A set of media of the same type (such as
media condition DDS) used and tracked as a group.
The quality of a medium as derived from Media are formatted and assigned to a
the media condition factors. Heavy media pool.
usage and age result in an increased
number of read and write errors with media set
tape media. Media need to be replaced The result of a backup session is data
when they are marked as POOR. backed up on a group of media called
media set. Depending on the media
usage policy, several sessions can share
the same media.

G-26
Glossary

media type transparent connection to many different

The physical type of media, such as communication systems. It provides
DDS or DLT. users with an electronic mail system,
individual and group scheduling, online
media usage policy forms, and workflow automation tools.
The media usage policy controls how It provides a developer with a platform
new backups are added to the already on which to build custom information-
used media. It can be Appendable, Non- sharing and messaging-service
Appendable, or Appendable for applications.
incrementals only.
Microsoft Management Console
merging (MMC) (Windows specific term)
This defines one mode to resolve file An administration model for Windows-
conflicts during restore. If the file to be based environments. It provides a
restored already exists at the destination, simple, consistent, and integrated
the one with the more recent administration user interface allowing
modification date is kept. Files not management of many applications
present on the disk are always restored. through the same GUI, provided that the
See also overwrite. applications adhere to the MMC model.

MFS Microsoft SQL Server 7.0/2000

The Migrating File System enables a A database management system
standard JFS filesystem with migration designed to meet the requirements of
capabilities (on HP-UX 11.00). The distributed "client-server" computing.
MFS is accessed via a standard
filesystem interface (DMAPI), it is Microsoft Volume Shadow Copy
mounted to a directory the same way as service (VSS)
any HP-UX filesystem. In an MFS, only A software service that provides a
the superblock, the inode and the unified communication interface to
'extended attribute' information remain coordinate backup and restore of a VSS-
permanently on the hard disk and are aware application regardless of its
never migrated. specific features. This service
See also VBFS. 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

G-27
Glossary

sets. management system of the central cell is

See also shadow copy, shadow copy the Manager-of-Managers (MoM). The
provider, writer. MoM allows you to configure and
manage multiple cells from a central
mirror (EMC Symmetrix and HP point.
StorageWorks Disk Array XP specific
term) mount request
See target volume. A screen prompt that tells you to insert a
specific medium into a device. Once you
mirror rotation (HP StorageWorks respond to the mount request by
Disk Array XP specific term) providing the required medium and
See replica set rotation. confirm the mount request, the session
continues.
MMD
The Media Management Daemon mount point
process (service) runs on the Data The access point in a directory structure
Protector Cell Manager and controls for a disk or logical volume, for example
media management and device /opt or d:. On UNIX, the mount points
operations. The process is started when are displayed using the bdf or df
Data Protector is installed on the Cell command.
Manager.
MSM
MMDB The Data Protector Media Session
The Media Management Database Manager, which runs on the Cell
(MMDB) is a part of the IDB that Manager and controls media sessions,
contains information about media, such as copying media.
media pools, devices, libraries, library
drives, and slots configured in the cell, MU number (HP StorageWorks Disk
as well as the Data Protector media used Array XP specific term)
for backup. In an enterprise backup A Mirror Unit number is an integer
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

G-28
Glossary

single system. This license, which is session, the selected backed up objects
bound to the IP address of the Cell are copied from the source to the target
Manager, is no longer available. media.

obdrindex.dat object copying

An IDB file with information about IDB The process of copying selected object
backups, media, and devices used for versions to a specific media set. You can
the backup. This information can select object versions from one or
significantly simplify IDB recovery. It is several backup sessions to be copied.
recommended to relocate the file,
together with IDB transaction logs, on a Object ID (Windows specific term)
separate physical disk from other IDB The object IDs (OIDs) enable access to
directories, and, additionally, to make a NTFS 5 files no matter where in the
copy of the file and locate it where you system the files reside. Data Protector
want. treats the OIDs as alternate streams of
the files.
OBDR capable device
A device that can emulate a CD-ROM object mirror
drive loaded with a bootable disk and A copy of a backup object created using
can thus be used as a backup or boot object mirroring. Object mirrors are
device for disaster recovery purposes. often referred to as object copies.

object object mirroring

See backup object The process of writing the same data to
several media sets during a backup
object copy session. Data Protector enables you to
A copy of a specific object version that mirror all or some backup objects to one
is created during an object copy session or more media sets.
or a backup session with object
mirroring. offline backup
A backup during which an application
object copy session database cannot be used by the
A process that creates an additional application.
copy of the backed up data on a different
media set. During an object copy • For simple backup methods (non
ZDB), the database is generally put
into a quiescent state that allows use

G-29
Glossary

by the backup system, but not the On-Bar (Informix specific term)
application, for the whole backup A backup and restore system for OnLine
period (~minutes/hours). For Server. ON-Bar enables you to create a
instance, for backup to tape, until copy of your OnLine Server data and
streaming of data to the tape is later restore the data. The ON-Bar
finished. backup and restore system involves the
following components:
• For ZDB methods, the database is
also put into the quiescent state, but • onbar utility
for the period of the data replication
process only (~seconds). Normal • Data Protector, as the backup
database operation can then be solution
resumed for the rest of the backup
process. • XBSA interface

See also zero downtime backup (ZDB) • ON-Bar catalog tables, which are
and online backup. used to back up dbobjects and track
instances of dbobjects through
offline recovery multiple backups.
Offline recovery is performed if the Cell
Manager is not accessible, for example, onbar utility (Informix specific term)
due to network problems. Only The Informix utility that communicates
standalone and SCSI library devices can backup and restore requests to OnLine
be used for offline recovery. Recovery Server. The utility uses XBSA to
of the Cell Manager is always offline. exchange control data and back up and
restore data with Data Protector.
offline redo log
See archived redo log ONCONFIG (Informix specific term)
An environment variable that specifies
OmniStorage the name of the active ONCONFIG
Software providing transparent configuration file. If the ONCONFIG
migration of less frequently used data to environment variable is not present,
the optical library while keeping more OnLine uses the configuration values
frequently used data on the hard disk. from the file <INFORMIXDIR>/etc/
HP OmniStorage runs on HP-UX onconfig (on HP-UX) or
systems. <INFORMIXDIR>\etc\onconfig (on
Windows).

G-30
Glossary

online backup filled and waiting to be archived or

A backup performed while a database reused.
application remains available for use. See also archived redo log.
The database is placed into a special
backup mode of operation for the time OnLine Server (Informix specific term)
period that the backup application Refers to INFORMIX-OnLine Dynamic
requires access to the original data Server.
objects. During this period, the database
is fully operational, but there may be a OpC
small performance impact and log files See OVO.
may grow very quickly.
Oracle instance (Oracle specific term)
• For simple backup methods (non Each installation of an Oracle database
ZDB), backup mode is required for on one or more systems. One computer
the whole backup period (~minutes/ system can have several instances of a
hours). For instance, for backup to database running.
tape, until streaming of data to tape
is finished. ORACLE_SID (Oracle specific term)
A unique name for an Oracle Server
• For ZDB methods, backup mode is instance. To switch among Oracle
required for the short period of the Servers, specify the desired
data replication process only <ORACLE_SID>. The
(~seconds). Normal database <ORACLE_SID> is included in the
operation can then be resumed for CONNECT DATA parts of the connect
the rest of the backup process. descriptor in a TNSNAMES.ORA file
and in the definition of the TNS listener
In some cases, transaction logs may also in the LISTENER.ORA file.
have to be backed up to allow a
consistent database to be restored. original system
See also zero downtime backup (ZDB) The system configuration backed up by
and offline backup. Data Protector before a computer
disaster hits the system.
online redo log (Oracle specific term)
Redo logs that have not been archived, overwrite
but are either available to the instance An option that defines one mode to
for recording database activity or are resolve file conflicts during restore. All

G-31
Glossary

files are restored from a backup even if installation of the Cell Manager. It is
they are older than existing files. possible to modify the ownership, so
See also merging. that the specific user becomes the
session owner.
OVO
HP OpenView Operations for Unix P1S file
provides powerful capabilities for P1S file contains information on how to
operations management of a large format and partition all disks installed in
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
Manager: root.sys@<Cell Manager>,
and for the Windows Cell Manager, the
user that was specified during the

G-32
Glossary

• COPY - The mirrored pair is parallelism

currently resynchronizing. Data is The concept of reading multiple data
transferred from one disk to the streams from an online database.
other. The disks do not contain the
same data. physical device
A physical unit that contains either a
• PAIR - The mirrored pair is drive or a more complex unit such as a
completely synchronized and both library.
disks (the primary volume and the
mirrored volume) contain identical post-exec
data. A backup option that executes a
command or script after the backup of
• 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.

G-33
Glossary

pre-exec A public folder store consists of a binary

A backup option that executes a rich-text .edb file and a streaming native
command or script before the backup of internet content .stm file.
an object or before the entire session is
started. Pre-exec commands are not public/private backed up data
supplied by Data Protector. You need to When configuring a backup, you can
create your own. They can be written as select whether the backed up data will
executables or batch files on Windows be:
and as shell scripts on UNIX.
See also post-exec. • public, that is visible (and accessible
for restore) to all Data Protector
Primary Volume (P-VOL) (HP users
StorageWorks Disk Array XP specific
term) • private, that is, visible (and
Standard HP StorageWorks Disk Array accessible for restore) only to the
XP LDEVs that act as a primary volume owner of the backup and
for the CA and BC configurations. The administrators
P-VOL is located in the MCU.
See also Secondary Volume (S-VOL). RAID
Redundant Array of Inexpensive Disks.
Private Information Store (Microsoft
Exchange Server 5.5 specific term) RAID Manager Library (HP
A part of the Information Store that StorageWorks Disk Array XP specific
maintains information in user term)
mailboxes. A mailbox store consists of a The RAID Manager Library is used
binary rich-text .edb file. 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 2000/2003 specific of low level SCSI commands.
term)
The part of the Information Store that RAID Manager XP (HP StorageWorks
maintains information in public folders. Disk Array XP specific term)
The RAID Manager XP application

G-34
Glossary

provides an extensive list of commands Recovery Catalog (Oracle specific

to report and control the status of the CA term)
and BC applications. The commands A set of Oracle tables and views that are
communicate through a RAID Manager used by Recovery Manager to store
instance with the HP StorageWorks information about Oracle databases.
Disk Array XP Disk Control Unit. This This information is used by Recovery
instance translates the commands into a Manager to manage the backup, restore,
sequence of low level SCSI commands. and recovery of Oracle databases. The
recovery catalog contains information
rawdisk backup about:
See disk image backup.
• The physical schema of the Oracle
RCU (HP StorageWorks specific term) target database
The Remote Control Unit acts as a slave
of an MCU in a CA configuration. In • Data file and archived log backup
bidirectional configurations, the RCU sets
can act as an MCU.
• Data file copies
RDBMS
Relational Database Management • Archived Redo Logs
System.
• Stored scripts.
RDF1/RDF2 (EMC Symmetrix specific
term) Recovery Catalog Database (Oracle
A type of SRDF device group. Only specific term)
RDF devices can be assigned to an RDF An Oracle database that contains a
group. An RDF1 group type contains recovery catalog schema. You should
source (R1) devices and an RDF2 group not store the recovery catalog in your
type contains target (R2) devices. target database.

RDS RecoveryInfo
The Raima Database Server process When backing up Windows
(service) runs on the Data Protector Cell configuration files, Data Protector
Manager and manages the IDB. The collects the information about the
process is started when Data Protector is current system configuration
installed on the Cell Manager. (information on disk layout, volume,

G-35
Glossary

and network configuration). This configuration. In bidirectional

information is needed for disaster configurations, the RCU can act as an
recovery. MCU.

Recovery Manager (RMAN) (Oracle Removable Storage Management

specific term) Database (Windows specific term)
An Oracle command-line interface that A Windows service used for managing
directs an Oracle Server process to back removable media (such as tapes and
up, restore, or recover the database it is disks) and storage devices (libraries).
connected to. RMAN uses either the Removable Storage allows applications
recovery catalog or the control file to to access and share the same media
store information about backups. This resources.
information can be used later in restore
sessions. reparse point (Windows specific term)
A system-controlled attribute that can be
recycle associated with any directory or file.
A process that removes the data The value of a reparse attribute can have
protection from all backed up data on a user-controlled data. The format of the
medium, allowing Data Protector to data is understood by the application
overwrite it during one of the next that stored the data and a filesystem
backups. Data that belongs to the same filter that was installed to interpret the
session(s) but resides on other media is data and process such files. Whenever
also unprotected. Recycling does not the filesystem encounters a file with a
actually alter the data on the medium. reparse point, it attempts to find the
filesystem filter associated with the data
redo log (Oracle specific term) format.
Every Oracle database has a set of two
or more redo log files. The set of redo replica (ZDB specific term)
log files for the database is known as the An image, at a particular point in time,
database's redo log. Oracle uses the redo of the data in source volumes that
log to record all changes made to data. contain user-specified backup objects.
Depending on the hardware/software
Remote Control Unit (HP with which it is created, the image may
StorageWorks Disk Array XP specific be an independent exact duplicate
term) (clone) of the storage blocks at the
The Remote Control Unit (RCU) acts as physical disk level (for example, a split
a slave of an MCU in a CA mirror), or a virtual copy (for example, a

G-36
Glossary

snapshot). From a host’s perspective, on RSM

a basic UNIX or Windows system, the The Data Protector Restore Session
complete physical disk containing a Manager controls the restore session.
backup object is replicated. However, if This process always runs on the Cell
a volume manager is used on UNIX, the Manager system.
whole volume/disk group containing a
backup object is replicated. RSM (Windows specific term)
See also snapshot, snapshot creation, Removable Storage Manager (RSM)
split mirror, and split mirror creation. includes a media management service
that facilitates communication among
replica set (ZDB specific term) applications, robotic changers, and
A group of replicas, all created using the media libraries. It enables multiple
same backup specification. applications to share local robotic media
See also replica and replica set libraries and tape or disk drives and to
rotation. manage removable media.

replica set rotation (ZDB specific term) SAPDBA (SAP R/3 specific term)
The use of a replica set for regular An SAP R/3 user interface that
backup production: Each time the same integrates the BRBACKUP,
backup specification requiring the use of BRARCHIVE, and BRRESTORE tools.
a replica set is run, a new replica is
created and added to the set, until the scan
maximum number for the set is reached. A function that identifies the media in a
After that, the oldest replica in the set is device. This synchronizes the MMDB
replaced, maintaining the maximum with the media that are actually present
number of replicas in the set. at the selected locations (for example,
See also replica and replica set. slots in a library).

restore session scanning

A process that copies data from backup A function which identifies the media in
media to a client. a device. This synchronizes the MMDB
with the media that are actually present
RMAN (Oracle specific term) at the selected locations (for example,
See Recovery Manager. slots in a library). It is useful to perform
a scan and check the actual media in the

G-37
Glossary

device if someone has manually unique identification of any session,

manipulated media without using Data including preview sessions. The session
Protector to eject or enter, for example. key is not recorded in the database, and
it is used for specifying options for the
Scheduler omnimnt, omnistat and omniabort CLI
A function that controls when and how commands.
often automatic backups occur. By
setting up a schedule, you automate the shadow copy (MS VSS specific term)
start of backups. A volume that represents a duplicate of
the original volume at a certain point in
Secondary Volume (S-VOL) (HP time. The data is then backed up from
StorageWorks Disk Array XP specific the shadow copy and not from the
term) original volume. The original volume
Secondary Volumes, or S-VOLs, are XP continues to changes as the backup
LDEVs that act as a secondary CA or process continues, but the shadow copy
BC mirror of another LDEV (a P-VOL). of the volume remains constant.
In the case of CA, S-VOLs can be used See also Microsoft Volume Shadow
as failover devices in a MetroCluster Copy service.
configuration. The S-VOLs are assigned
separate SCSI addresses, different from shadow copy provider (MS VSS
the addresses used by the P-VOLs. specific term)
See also Primary Volume (P-VOL). An entity that performs the work on
creating and representing the volume
session shadow copies. Providers own the
See backup session, media shadow copy data and expose the
management session, and restore shadow copies. Providers can be
session. software (for example, system
providers) or hardware (local disks, disk
session ID arrays).
An identifier of a backup, restore, object See also shadow copy.
copy, or media management session,
consisting of the date when the session shadow copy set (MS VSS specific
ran and a unique 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

G-38
Glossary

shared disks SMBF

A Windows disk on another system that The Session Messages Binary Files
has been made available to other users (SMBF) part of the IDB stores session
on the network. Systems with shared messages generated during backup,
disks can be backed up without a Data object copy, restore, and media
Protector Disk Agent installed. management sessions. One binary file is
created per session. The files are
SIBF grouped by year and month.
The Serverless Integrations Binary Files
(SIBF) is a part of the IDB that stores snapshot (HP StorageWorks VA and HP
raw NDMP meta data. This data is StorageWorks EVA specific term)
necessary to perform restore of NDMP A form of replica produced using
objects. snapshot creation techniques. A range of
snapshot types is available, with
Site Replication Service (Microsoft different characteristics, depending on
Exchange Server 2000/2003 specific the arrays/techniques used. Such
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.
The replicas are considered to be created

G-39
Glossary

at one particular point-in-time, without of the contents of the source volumes.

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

G-40
Glossary

sessions can be restored using this executes all tasks required for a split
method. mirror backup integration. It
See also ZDB to tape, ZDB to communicates with the HP
disk+tape, and replica. StorageWorks Disk Array XP storing
system using the RAID Manager XP
sqlhosts file (Informix specific term) utility (HP-UX and Windows systems)
An Informix connectivity-information or RAID Manager Library (Solaris
file that contains the names of each of systems).
the database servers and any aliases to
which the clients on a host computer can sst.conf file
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

G-41
Glossary

standalone file device example, a virtualization mechanism)

A file device is a file in a specified upon which volume management
directory to which you back up data. systems, file systems, or other objects
may exist. The volume management
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 2000/2003 solution like Data Protector.
specific 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.

G-42
Glossary

System Backup to Tape (Oracle System State (Windows specific term)

specific term) The System State data comprises the
An Oracle interface that handles the Registry, COM+ Class Registration
actions required to load, label, and database, system startup files, and the
unload correct backup devices when Certificate Services database (if the
Oracle issues a backup or restore server is a certificate server). If the
request. server is a domain controller, Active
Directory directory services and the
system databases (Sybase specific Sysvol directory are also contained in
term) the System State data. If the server is
The four system databases on a newly running the Cluster service, the System
installed Sybase SQL Server are the: State data also includes resource registry
checkpoints and the quorum resource
• master database (master) recovery log, which contains the most
recent cluster database information.
• temporary database (tempdb)
system volume/disk/partition
• system procedure database A volume/disk/partition containing
(sybsystemprocs) operating system files. Microsoft
terminology defines the system volume/
• model database (model). disk/partition as the volume/disk/
partition containing files required for the
system disk initial step of the boot process.
A system disk is a disk containing
operating system files. Microsoft SysVol (Windows specific term)
terminology defines the system disk as a A shared directory that stores the server
disk containing the files required for copy of the domain’s public files, which
initial step of boot process. are replicated among all domain
controllers in the domain.
system partition
A system partition is a partition tablespace
containing operating system files. A part of a database structure. Each
Microsoft terminology defines a system database is logically divided into one or
partition as a partition containing the more tablespaces. Each tablespace has
files required for initial step of boot data files or raw volumes exclusively
process. associated with it.

G-43
Glossary

tapeless backup (ZDB specific term) target volume (ZDB specific term)
See ZDB to disk. A storage volume to which data is
replicated.
target database (Oracle specific term)
In RMAN, the target database is the Terminal Services (Windows specific
database that you are backing up or term)
restoring. Windows Terminal Services provide a
multi-session environment that allows
target (R2) device (EMC Symmetrix clients to access a virtual Windows
specific term) desktop session and Windows-based
An EMC Symmetrix device that programs running on the server.
participates in SRDF operations with a
source (R1) device. It resides in the thread (MS SQL Server 7.0/2000
remote EMC Symmetrix unit. It is specific term)
paired with a source (R1) device in the An executable entity that belongs to
local EMC Symmetrix unit and receives only one process. It comprises a
all write data from its mirrored pair. program counter, a user-mode stack, a
This device is not accessed by user kernel-mode stack, and a set of register
applications during normal I/O values. Several threads can run at a time
operations. An R2 device must be within one process.
assigned to an RDF2 group type.
See also source (R1) device TimeFinder (EMC Symmetrix specific
term)
target system (Disaster Recovery A business continuation process that
specific term) creates an instant copy of single or
A system after a computer disaster has multiple Symmetrix Logical Devices
occurred. The target system is typically (SLDs). The instant copy is created on
in a non-bootable state and the goal of specially preconfigured SLDs called
disaster recovery is to restore this BCVs and is accessible via a separate
system to the original system device address to the system(s).
configuration. The difference between a
crashed system and a target system is TLU
that a target system has all faulty Tape Library Unit.
hardware replaced.
TNSNAMES.ORA (Oracle and SAP R/
3 specific term)
A network configuration file that

G-44
Glossary

contains connect descriptors mapped to transaction log files

service names. The file may be Files that record transactions of the
maintained centrally or locally, for use database modifications, and provide
by all or individual clients. fault tolerance in case of a database
disaster.
transaction
A mechanism for ensuring that a set of transaction logs (Data Protector
actions is treated as a single unit of specific term)
work. Databases use transactions to Keeps track of IDB changes. The
keep track of database changes. archiving of transaction logs should be
enabled to prevent you from losing the
transaction backup transaction log files that are created after
Transaction backups generally use fewer the last IDB backup and are necessary
resources than database backups, so they for IDB recovery.
can be created more frequently than
database backups. By applying transaction log table (Sybase specific
transaction backups, you can recover the term)
database to a specific point in time prior A system table in which all changes to
to when a problem occurred. the database are automatically recorded.

transaction backup (Sybase and SQL transportable snapshot (MS VSS

specific term) specific term)
A backup of the transaction log A shadow copy that is created on the
providing a record of changes made application system and can be presented
since the last full or transaction backup. to the backup system which performs
the backup.
transaction log backup See also Microsoft Volume Shadow
Transaction log backups generally use Copy service (VSS).
fewer resources than database backups
so they can be created more frequently TSANDS.CFG file (Novell NetWare
than database backups. By applying specific term)
transaction log backups, you can recover A file that allows you to specify the
the database to a specific point in time. names of containers where you want
backups to begin. It is text file located in
the SYS:SYSTEM\TSA directory on the
server where TSANDS.NLM is loaded.

G-45
Glossary

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
Protector backs up user disk quotas on brought back to the data center when
the whole system and for all configured they are needed for restore or are ready
users at a time. for reuse in subsequent backups. The
vaulting procedure depends on your
user group company's backup strategy and policies
Each Data Protector user is member of a for data protection/reliability.
User Group. Each User Group has a set
of user rights that are given to every user VBFS (OmniStorage specific term)
in that User Group. The number of User A Very Big File System is an extension
Groups with their associated user rights of the standard HP-UX file system on
can be defined as desired. Data Protector HP-UX 9.x. It is mounted to a directory
provides three default user groups: the same way as any HP-UX file system.
admin, operator, and user. In a VBFS, only the superblock, the
inode and the 'extended attribute'

G-46
Glossary

information remain permanently on the snapshot functionality.

hard disk and are never migrated. See also source volume and target
See also MFS. volume.

verify virtual server

A function that lets you check whether A virtual machine in a cluster
the Data Protector data on a specified environment defined in a domain by a
medium is readable. Additionally, network IP name and address. Its
consistency within each block can be address is cached by the cluster software
checked if the backup was performed and mapped to the cluster node that is
with the cyclic redundancy check (CRC) currently running the virtual server
option ON. resources. This way all requests for a
particular virtual server are cached by a
Virtual Controller Software (VCS) specific cluster node.
(HP StorageWorks EVA specific term)
volser (ADIC and STK specific term)
The firmware that manages all aspects
A VOLume SERial number is a label on
of storage system operation, including
the medium to identify the physical tape
communication with Command View
used in very large libraries. A volser is a
EVA through the HSV controllers.
naming convention specific to ADIC/
See also Command View (CV) EVA.
GRAU and StorageTek devices.
Virtual Device Interface (MS SQL
volume group
Server 7.0/2000 specific term)
A unit of data storage in an LVM
This is a SQL Server 7.0/2000
system. A volume group can consist of
programming interface that allows fast
one or more physical volumes. There
backup and restore of large databases.
can be more than one volume group on
the system.
virtual disk (HP StorageWorks EVA
specific term)
volume mountpoint (Windows specific
A unit of storage allocated from an HP
term)
StorageWorks Enterprise Virtual Array
An empty directory on a volume that
storage pool. Virtual disks are the
can be used to mount another volume.
entities that are replicated using the HP
The volume mount point acts as a
StorageWorks Enterprise Virtual Array
gateway to the target volume. Provided
that the volume is mounted, users and
applications can refer to the data on the

G-47
Glossary

mounted volume by the full (merged) wildcard character

filesystem path as if both volumes are A keyboard character that can be used to
one integral part. represent one or many characters. The
asterisk (*), for example, typically
Volume Shadow Copy service represents one or more characters, and
See Microsoft Volume Shadow Copy the question mark (?) typically
service. represents a single character. Wildcard
characters are often used in operating
VPO systems as a means of specifying more
See OVO. than one file by name.

VSS Windows CONFIGURATION

See Microsoft Volume Shadow Copy backup
service. Data Protector allows you to back up
Windows CONFIGURATION,
VxFS including Windows Registry, user
Veritas Journal Filesystem. profiles, Event Logs, and WINS and
DHCP server data (if configured on a
VxVM (Veritas Volume Manager) system) in one step.
A Veritas Volume Manager is a system
for managing disk space on Solaris Windows Registry
platforms. A VxVM system consists of A centralized database used by
an arbitrary group of one or more Windows to store configuration
physical volumes organized into logical information for the operating system
disk groups. and the installed applications.

Wake ONLAN WINS server A system running

Remote power-up support for systems Windows Internet Name Service
running in power-save mode from some software that resolves Windows
other system on the same LAN. networking computer names to IP
addresses. Data Protector can back up
Web reporting WINS server data as part of the
The Data Protector functionality that Windows configuration.
allows you to view reports on backup
status and Data Protector configuration
using the Web interface.

G-48
Glossary

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

G-49
Glossary

using the instant recovery process, the See also ZDB to disk, ZDB to tape,
standard Data Protector restore from ZDB to disk+tape, and instant
tape, or on split mirror arrays, split recovery.
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
to be backed up is created first. All
subsequent backup operations are
performed on the replicated data rather
than the original data, while the
application system can be returned to
normal operation.

G-50
 Index Index

A performance tuning, 167

advantages scheduling, 155
MS Exchange 2000/2003 integration, 104 backing up VSS , 199–206
MS Exchange 5.x, 61 backup concepts, scheme, 182
MS SQL integration, 3 backup flow, 188
VSS integration, 183, 187 starting interactive backup, using Data
architecture Protector GUI, 205
MS Exchange 5.x integration, 66 backup concepts
MS Exchange 2000/2003 integration, 108
B MS SQL integration, 9
MS SQL integration, parallelism, 9
backing up MS Exchange 2000/2003, 118–120 VSS integration, 182
backup concepts, scheme, 108 backup flow
backup flow, 107 MS Exchange 2000/2003 integration, 107
backup options, GUI, 116 MS Exchange 5.x integration, 64
backup problems, 131 MS Exchange Single Mailbox, 141
scheduled backup, 118 MS SQL integration, 8
starting interactive backup, using Data VSS integration, 188
Protector GUI, 119 backup methods
backing up MS Exchange 5.x, 78–80 MS Exchange 5.x integration, 78
backup flow, 64 MS SQL integration, 26
backup methods, 78 backup options
backup options, 74 MS Exchange 2000/2003 integration, GUI,
backup problems, 94 116
backup specification, creating, 70 MS Exchange 5.x integration, 74
full backup, 65 MS Exchange Single Mailbox, 151
incremental backup, 65 MS SQL integration, GUI, 22
interactive backup, 79 backup problems
scheduling backups, 78 MS Exchange 2000/2003 integration, 131
backing up MS SQL, 26–28 MS Exchange 5.x integration, 94
backup concepts, scheme, 9 MS Exchange Single Mailbox, 175
backup flow, 8 MS SQL integration, 53
backup methods, 26 backup specification
backup options, GUI, 22 MS Exchange 2000/2003 integration,
backup problems, 53 creating, 112
backup types, 3, 6 MS Exchange 2000/2003 integration,
concepts, parallelism, 9 scheduling, 118
scheduled backup, 26 MS Exchange 5.x integration, creating, 70
starting interactive backup, using Data MS Exchange 5.x integration, scheduling,
Protector GUI, 27 78
backing up single mailboxes MS Exchange Single Mailbox, 148
backup flow, 141 MS SQL integration, creating, 19
backup specification, creating, 148 MS SQL integration, scheduling, 26
full backup, 142 VSS integration, creating, 199
in parallel, 167 backup templates
incremental backup, 142 MS Exchange 5.x integration, 70
incremental1 backup , 142 backup types
interactively using CLI, 157 MS Exchange Single Mailbox, 142
interactively using GUI, 156 MS SQL integration, 3, 6
monitoring sessions, 169

I-1
Index

C disaster recovery
checking MS Exchange 5.x, 88
MS SQL configuration, 17 MS SQL integration, 37
concepts DS See Directory Store
MS Exchange 2000/2003 integration,
107–108 F
MS Exchange 5.x, 64 full backup
MS SQL integration, 6–11 MS Exchange 5.x integration, 65
VSS integration, 187–190 MS Exchange Single Mailbox, 142
concurrent streams
MS Exchange 5.x, 64 I
configuration file
improving performance
MS SQL integration, 12–13 MS SQL integration, 41
configuration problems
incremental backup
MS Exchange Single Mailbox, 173
MS Exchange 5.x integration, 65
MS SQL integration, 51
MS Exchange Single Mailbox, 142
configuring
MS Exchange Single Mailbox integration, Information Store (MDB), 71
integration concepts
144 MS Exchange Single Mailbox, 141
MS Exchange Single Mailbox integration interactive backup
agent, 144 MS Exchange 2000/2003 integration,
Single Mailbox backup, 148 starting, 119
configuring MS Exchange 2000/2003, MS Exchange 5.x integration, 79
110–117 MS SQL integration, starting, 27
backup specification, 112
configuring MS Exchange 5.x, 68–77
backup, 70 L
backup specification, 70 limitations
backup templates, 70 MS Exchange 5.x, 63
improving performance, 90 MS Exchange Single Mailbox, 139
performance tuning, 90 MS SQL integration, 5
configuring MS SQL, 14–25 VSS integration, 185
backup specification, 19
checking configuration, 17 M
configuration problems, 51 MAPI , 141
configuring VSS, 191–193 MAPI profile, 141
backup specification, 199 MAPI session, 141
conventions, ix MDB See Information Store
creating monitoring
MS Exchange 2000/2003 backup MS Exchange 5.x sessions, 91
specification, 112 MS Exchange Single Mailbox sessions, 169
MS Exchange 5.x backup specification, 70 MS SQL sessions, 47
MS Exchange Single Mailbox backup VSS sessions, 215
specification, 148 MS Exchange 2000/2003 backup, 118–120
MS SQL backup specification, 19 backup concepts, scheme, 108
VSS backup specification, 199 backup flow, 107
backup options, GUI, 116
D backup problems, 131
Directory Store (DS), 71 scheduling backup, 118

I-2
 Index

starting interactive backup, using Data incremental backup, 65

Protector GUI, 119 interactive backup, 79
MS Exchange 2000/2003 configuration, scheduling backups, 78
110–117 MS Exchange 5.x configuration, 68–77
backup specification, 112 backup, 70
MS Exchange 2000/2003 integration backup specification, 70
advantages, 104 backup templates, 70
backing up, 118–120 improving performance, 90
concepts, 107–108 performance tuning, 90
configuring, 110–117 MS Exchange 5.x integration
overview, 103 viewing sessions, 92
prerequisites, 106 MS Exchange 5.x restore, 81–89
restoring, 121–129 disaster recovery, 88
troubleshooting, 130–133 from the latest online backup, 85
MS Exchange 2000/2003 restore, 121–129 restore flow, 81
restore flow, 107 restore options, 85
restore options, CLI, 128 restore problems, 97
restore options, GUI , 125 restore procedure, 82
restore problems, 132 restoring from the latest online backup, 85
MS Exchange 2000/2003 troubleshooting, MS Exchange 5.x troubleshooting, 94–100
130–133 backup problems, 94
backup problems, 131 restore problems, 97
restore problems, 132 MS Exchange Single Mailbox integration
MS Exchange 5.x backup flow, 141
advantages, 61 backup options, 151
architecture, 66 backup problems, 175
backing up MS Exchange 5.x, 78–80 backup specification, 148
basic component, 61 checking configuration, 147
concepts, 64 concepts, 141
concurrent streams, 64 configuration problems, 173
configuring MS Exchange 5.x, 68–77 configuring, 144
disaster recovery, 88 configuring backup, 148
improving performance, 90 limitations, 139
limitations, 63 MAPI, 141
monitoring sessions, 91 MAPI profile, 141
overview, 61 MAPI session, 141
performance tuning, 90 overview, 137
prerequisites, 63 prerequisites, 139
restoring MS Exchange 5.x, 81–89 restore flow, 142
scheduling backup, 78 restore options, 165
testing, using GUI, 76 restore problems, 176
troubleshooting MS Exchange 5.x, 94–100 restoring, 159
MS Exchange 5.x backup, 78–80 testing, 153
backup flow, 64 troubleshooting, 172
backup methods, 78 MS SQL backup, 26–28
backup options, 74 backup concepts, scheme, 9
backup problems, 94 backup flow, 8
backup specification, creating, 70 backup methods, 26
full backup, 65 backup options, GUI, 22

I-3
Index

backup problems, 53 P
backup types, 3, 6 performance tuning
concepts, parallelism, 9 MS Exchange Single Mailbox, 167
scheduling backup, 26 MS SQL integration, 41
starting interactive backup, using Data prerequisites
Protector GUI, 27 MS Exchange 2000/2003 integration, 106
MS SQL configuration, 14–25 MS Exchange 5.x, 63
backup specification, 19 MS Exchange Single Mailbox, 139
checking, 17 MS SQL integration, 5
configuration problems, 51 VSS integration, 185
MS SQL configuration file, 12–13
MS SQL integration R
advantages, 3
backing up, 26–28 restore flow
backup types, 3, 6 MS Exchange 2000/2003 integration, 107
concepts, 6–11 MS Exchange 5.x, 65, 81
configuration file, 12–13 MS Exchange Single Mailbox, 142
configuring, 14–25 MS SQL integration, 8
disaster recovery, 37 VSS integration, 189
improving performance, 41 restore options
MS Exchange 2000/2003 integration, CLI,
limitations, 5
128
monitoring sessions, 47
MS Exchange 2000/2003 integration, GUI,
overview, 3
125
performance tuning, 41
MS Exchange 5.x integration, 85
prerequisites, 5
MS Exchange Single Mailbox, 165
restoring, 29–40
MS SQL integration, 3
troubleshooting, 50–57
MS SQL integration, GUI, 33
viewing sessions, 48
VSS integration, 214
MS SQL restore, 29–40
disaster recovery, 37 restore problems
MS Exchange 2000/2003 integration, 132
restore flow, 8
MS Exchange 5.x integration, 97
restore options, 3
MS Exchange Single Mailbox, 176
restore options, GUI , 33
MS SQL integration, 54
restore problems, 54
using CLI, 36 VSS integration, 218
restore procedure
using GUI, 29
MS Exchange Single Mailbox, 159
MS SQL troubleshooting, 50–57
restoring
backup problems, 53
MS Exchange single mailboxes, 159
configuration problems, 51 restoring MS Exchange 2000/2003, 121–129
restore problems, 54 restore flow, 107
restore options, CLI, 128
O restore options, GUI, 125
overview restore problems, 132
MS Exchange 2000/2003 integration, 103 restoring MS Exchange 5.x, 81–89
MS Exchange 5.x, 61 disaster recovery, 88
MS Exchange Single Mailbox integration, from the latest online backup, 85
137 restore flow, 65, 81
MS SQL integration, 3 restore options, 85
VSS integration, 181 restore problems, 97

I-4
 Index

restore procedure, 82 MS Exchange Single Mailbox, 172

restoring from the latest online backup, 85 troubleshooting MS Exchange 2000/2003,
restoring MS SQL, 29–40 130–133
disaster recovery, 37 backup problems, 131
restore flow, 8 restore problems, 132
restore options, 3 troubleshooting MS Exchange 5.x, 94–100
restore options, GUI , 33 backup problems, 94
restore problems, 54 restore problems, 97
using CLI, 36 troubleshooting MS SQL, 50–57
using GUI, 29 backup problems, 53
restoring single mailboxes configuration problems, 51
monitoring sessions, 169 restore problems, 54
restore flow, 142 troubleshooting VSS, 218–219
restore procedure, 159 restore problems, 218
using CLI, 165 typographical conventions, ix
using GUI, 159
restoring VSS, 207–214 V
restore flow, 189 viewing
restore options, GUI , 214 MS Exchange 5.x sessions, 92
restore problems, 218 MS SQL sessions, 48
running VSS sessions, 216
Single Mailbox interactive backup, 156 Volume Shadow Copy service (VSS), 181
VSS backup, 199–206
S backup concepts, scheme, 182
backup flow, 188
scheduling
Single Mailbox backup specification, 155 starting interactive backup, using Data
scheduling backup Protector GUI, 205
MS Exchange 2000/2003 integration, 118 VSS configuration, 191–193
MS Exchange 5.x, 78 backup specification, 199
MS Exchange 5.x integration, 78 VSS integration
MS SQL integration, 26 advantages, 183, 187
backing up, 199–206
starting backup
MS Exchange 2000/2003 integration, concepts, 187–190
interactive, 119 configuring, 191–193
MS Exchange 2000/2003 integration, using limitations, 185
Data Protector GUI, 119 monitoring sessions, 215
MS Exchange 5.x integration, 79 overview, 181
MS SQL integration, interactive, 27 prerequisites, 185
MS SQL integration, using Data Protector restoring, 207–214
GUI, 27 troubleshooting, 218–219
VSS integration, using Data Protector GUI, viewing sessions, 216
205 writers specifics, 194–198
writers specifics, Microsoft Exchange
Server 2003, 203, 211
T
writers specifics, MSDE, 209
testing VSS restore, 207–214
MS Exchange 5.x integration, using GUI, restore flow, 189
76 restore options, GUI, 214
MS Exchange Single Mailbox, 153 restore problems, 218
troubleshooting

I-5
Index

VSS troubleshooting, 218–219

restore problems, 218
VSS writers specifics, 194–198
Microsoft Exchange Server 2003, 203, 211
MSDE, 209

I-6