HP DATA PROTECTOR V5.0 User Manual

Download

Page 1

HP OpenView Storage Data Protector

Administrator’s Guide

Manual Edition: August 2002

Manufacturing Part Number: B6960-90057

Release A.05.00

Page 2

Legal Notices

Hewlett-Packard makes no warranty of any kind with regard to this manual, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose. Hewlett-Packard

shall not be held liable for errors contained herein or direct, indirect, special, incidental or consequential damages in connection with the furnishing, performance, or use of this material.

Warranty. A copy of the specific warranty terms applicable to your Hewlett-Packard product and replacement parts can be obtained from your local Sales and Service Office.

Restricted Rights Legend. All rights are reserved. No part of this document may be photocopied, reproduced, or translated to another language without the prior written consent of Hewlett-Packard Company Company. The information contained in this document is subject to change without notice.

Use, duplication or disclosure by the U.S. Government is subject to restrictions as set forth in subparagraph (c) (1) (ii) of the Rights in Technical Data and Computer Software clause at DFARS 252.227-7013 for DOD agencies, and subparagraphs (c) (1) and (c) (2) of the Commercial Computer Software Restricted Rights clause at FAR 52.22719 for other agencies.

Hewlett-Packard Company United States of America

Reproduction, adaptation, or translation of this document without prior written permission is prohibited, except as allowed under the copyright laws.

This software is based in part on the Fourth Berkeley Software Distribution under license from the Regents of the University of California.

Page 3

©Copyright 1985-86, 1988 Massachusetts Institute of Technology ©Copyright 1989-93 The Open Software Foundation, Inc. ©Copyright 1986-1997 FTP Software, Inc. All rights reserved ©Copyright 1986 Digital Equipment Corporation ©Copyright 1990 Motorola, Inc. ©Copyright 1990, 1991, 1992 Cornell University ©Copyright 1989-1991 The University of Maryland ©Copyright 1988 Carnegie Mellon University ©Copyright 1991-1995 by Stichting Mathematisch Centrum,

States and other countries, licensed exclusively through X/Open Company Limited.

X Window System is a trademark of the Massachusetts Institute of Technology.

Motif is a trademark of the Open Software Foundation, Inc. in the U.S. and other countries.

Windows NT™ is a U.S. trademark of Microsoft Corporation. Microsoft®, MS-DOS®, Windows® and MS Windows® are U.S. registered trademarks of Microsoft Corporation.

Oracle®, SQL*Net®, and Net8® are registered U.S. trademarks of Oracle Corporation, Redwood City, California. Oracle Reports™, Oracle7™, Oracle7 Server™, Oracle7 Backup Utility™, Oracle8™, Oracle8 Server Manager™ and Oracle8 Recovery Manager™ are trademarks of Oracle Corporation, Redwood City, California.

Java™ is a U.S. trademark of Sun Microsystems, Inc. Adobe® and Acrobat® are trademarks of Adobe Systems Incorporated. ARM® is a registered trademark of ARM Limited. X/Open® is a registered trademark, and the X device is a trademark of X/

Open Company Ltd. in the UK and other countries. VisiCalc® is a U.S. registered trademark of Lotus Development Corp.

iii

Page 4

HP-UX Release 10.20, HP-UX Release 11.00 and later (in both 32 and 64-bit configurations) on all HP 9000 computers are Open Group UNIX 95 branded products.

Netscape and Netscape Navigator are U.S. trademarks of Netscape Communications Corporation.

OpenView® is a registered U.S. trademark of Hewlett-Packard Company.

Other reserved names are trademarks of the respective companies.

Page 5

Contents

1. Introducing Data Protector

In This Chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

The Data Protector Cell Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

How a Backup Session Works . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

How a Restore Session Works . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

Using the Data Protector User Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

Graphical User Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

The Command-Line Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Data Protector Online Resources. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Using Microsoft Management Console (MMC) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Overview of the Tasks to Set Up Data Protector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

2. Configuring and Using Backup Devices

In This Chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Configuring Backup Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Configuring Standalone Devices. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

Configuring File Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

Configuring Library Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

Configuring Libraries with Multiple Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

Configuring Magazine Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

Configuring Stacker Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

Configuring a Library for Mixed Media . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

Configuring Devices for Direct Backup. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

Configuration Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

Support of New Devices. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

Using Several Drive Types in a Library. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

Shared Devices in the SAN Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

Locking Devices Used Exclusively by Data Protector . . . . . . . . . . . . . . . . . . . . . . . . 44

Locking Devices Used by Multiple Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

Direct Library Access Concept. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

Indirect Library Access Concept . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

Configuration Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

Shared Devices and MC/ServiceGuard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

Drive Cleaning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

Configuring Automatic Drive Cleaning. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

Testing the Drive Cleaning Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

Busy Drive Handling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

Activating Barcode Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

Page 6

Contents

Activating Cartridge Memory Support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

Disabling a Backup Device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

Removing a Backup Device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66

Renaming a Backup Device. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

Device Locking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68

Device Concurrency, Segment and Block Size . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70

3. Configuring Users and User Groups

In This Chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76

Data Protector User Rights. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77

Predefined Data Protector User Groups. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80

Adding a New User Group. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82

Adding a New User . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83

Changing User Group Rights . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85

Example User Configurations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86

Users Restoring Their Own Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86

Enabling Users to Back Up Their Systems. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86

4. Managing Media

In This Chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90

Overview of Data Protector Media Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91

Media Life Cycle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92

Creating a Media Pool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94

Properties of a Media Pool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95

Adding Media to a Media Pool. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98

Formatting Media . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99

Formatting Media in a Magazine. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101

Recognizing Other Data Formats . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102

Importing Media . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104

Importing the Catalog from Media . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105

Importing Media in a Magazine Device. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106

Appending Backups to Media . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108

Using a Pre-Allocation List of Media for Backup. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110

Selecting Media for Backup. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111

Media Selection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112

Setting Data Protection for Media . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114

Recycling Media . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115

Moving Media to Another Pool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116

Page 7

Contents

Exporting Media from Data Protector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117

Modifying Media Locations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118

Modifying Media Descriptions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119

Verifying Data on a Medium . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120

Scanning Media in a Device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121

Checking the Condition of a Medium . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123

Factors Influencing the Condition of Media . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124

Changing How Media Condition Is Calculated. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126

Searching for and Selecting a Medium. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127

Entering a Medium into a Device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128

Ejecting a Medium from a Device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129

Scheduled Eject of Media . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130

Vaulting Media. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131

Configuring Vaults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132

Moving Media to a Vault . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132

Restoring from Media in a Vault . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132

Copying Media . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134

Detection of Write-Protected Media . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136

Using Different Media Format Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137

Modifying Views in the Media Management Window . . . . . . . . . . . . . . . . . . . . . . . . . 138

5. Backup

In This Chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140

Configuring a Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141

Creating a Backup Specification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142

Backing Up UNIX Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148

Backing Up UNIX Filesystems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148

Backing Up Clients Using Disk Discovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150

Backing Up Disks Using NFS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151

Backing Up UNIX Disks as Disk Image Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . 153

Backing Up Windows Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155

Backing Up Filesystems (Logical Disk Drives). . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155

Backing Up CONFIGURATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159

Backing Up Windows Clients Using Disk Discovery . . . . . . . . . . . . . . . . . . . . . . . . 168

Backing Up Windows Shared Disks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170

Backing Up Windows Disks as Disk Image Objects . . . . . . . . . . . . . . . . . . . . . . . . . 174

Backing Up Novell NetWare Systems. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176

Backing Up Novell NetWare Filesystems (Volumes) . . . . . . . . . . . . . . . . . . . . . . . . 176

vii

Page 8

Contents

Client Backup with Disk Discovery. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180

Backing Up NetWare Directory Services (NDS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181

Backing Up in Direct Backup Environment. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183

Backup Specification Configuration Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184

Starting Direct Backup using the CLI. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185

Scheduling Unattended Backups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186

Starting Backups on Specific Dates. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187

Starting Periodic Backups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188

Editing Your Backup Schedule. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189

Skipping Backups During Holidays. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190

Configuring Backup Options When Scheduling Backups . . . . . . . . . . . . . . . . . . . . 191

Running Consecutive Backups. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191

Selecting a Backup Type: Full or Incremental. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192

Using Backup Templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195

Data Protector Default Backup Templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195

Options Offered by Templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195

Using a Backup Template When Creating a New Backup Specification. . . . . . . . . 197

Applying a Backup Template . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197

Creating a New Template. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198

Modifying an Existing Template . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199

Groups of Backup Specifications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200

Using Backup Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203

Most Frequently Used Backup Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204

List of Data Protector Backup Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212

Device Backup Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225

Pre- and Post-Exec Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 226

Pre- and Post- Exec Commands on Windows Systems . . . . . . . . . . . . . . . . . . . . . . . 227

Pre- and Post- Exec Commands on UNIX Systems . . . . . . . . . . . . . . . . . . . . . . . . . 232

Managing Failed Backups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 238

Warnings When Backing Up System Disks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 238

Preventing Backup Failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239

Restarting Failed Backups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 241

6. Restore

In This Chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 244

Restoring Your Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245

Standard Restore Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245

Restoring Disk Images . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249

viii

Page 9

Contents

Restoring Your Data to a Shared Disk . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 251

Restoring UNIX Systems. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 252

Restoring Windows Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 254

Restoring the Windows CONFIGURATION. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 256

Restoring the Windows 2000/XP System State. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 258

Restoring the Windows Registry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 259

Restoring Windows 2000/XP Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 260

Restoring DFS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 261

Restoring Windows User Profiles and Event Logs . . . . . . . . . . . . . . . . . . . . . . . . . . 261

Restoring Windows TCP/ IP Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 262

Restoring Novell Netware Filesystems. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 263

Restoring Namespace Information and Volume Space Restrictions . . . . . . . . . . . . 263

Restoring File Ownerships and Trustees . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 264

Restoring the Novell NetWare Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 264

Restoring Novell NDS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 265

Restore Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 267

List of Restore Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 267

Restore Techniques . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 271

Restoring Files to Different Paths . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 271

Restoring Files in Parallel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 272

Viewing Files Not in the IDB. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 273

Restoring Files in Use . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 274

Restoring by Query. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 274

Skipping Files for Restore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 276

Selecting Only Specific Files (Matching) for Restore . . . . . . . . . . . . . . . . . . . . . . . . 276

Restoring Files and Directories Manually. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 277

7. Monitoring, Reporting, Notifications and the Event Log

In This Chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 280

Monitoring Sessions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 281

Viewing Currently Running Sessions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 281

Viewing Finished Sessions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 282

Responding to Mount Requests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 282

Restarting Failed Backups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 283

Aborting Running Sessions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 284

Changing the Amount of Messages Shown . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 284

Monitoring Several Cells Simultaneously . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 285

Data Protector Reporting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 286

Page 10

Contents

Reports Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 287

Reports Formats . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 298

Report Send Methods. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 300

Email Send Method . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 300

Broadcast Send Method . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 301

Log to File Send Method. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 301

SNMP Send Method . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 301

External Send Method . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 303

Configuring Reports Using the Data Protector GUI . . . . . . . . . . . . . . . . . . . . . . . . . . 304

Configuring Report Groups and Adding Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . 304

Running Reports and Report Groups Using the Data Protector GUI. . . . . . . . . . . . . 307

Running Individual Reports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 307

Running Report Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 307

Running Reports and Report Groups Using the Command-Line Interface . . . . . . . . 308

Data Protector Notifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 311

Notification Types. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 311

Notification Send Methods. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 316

Configuring Notifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 320

Configuring Reports and Notifications on the Web . . . . . . . . . . . . . . . . . . . . . . . . . . . 321

Copying Data Protector Java Programs to the Web Server . . . . . . . . . . . . . . . . . . . 322

Restricting Access to Web Reporting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 322

Generating the Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 323

Configuring Notifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 323

Configuring Report Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 323

Data Protector Event Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 324

8. Manager-of-Managers Environment

In This Chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 328

Manager-of-Managers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 329

Configuring the Data Protector Manager-of-Managers. . . . . . . . . . . . . . . . . . . . . . . . 330

Setting Up MoM Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 331

Importing Data Protector Cells . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 331

Adding a MoM Administrator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 332

Restarting Data Protector Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 332

Centralized Media Management Database (CMMDB) . . . . . . . . . . . . . . . . . . . . . . . . 334

Configuring a Centralized Media Management Database . . . . . . . . . . . . . . . . . . . . . 336

Configuring the CMMDB on the MoM Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . 337

Configuring the CMMDB on the Client Cell. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 338

Page 11

Contents

Centralized Licensing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 340

Setting Up Centralized Licensing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 340

Moving Licenses in the MoM Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 343

Deactivating Centralized Licensing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 344

Working with a MoM Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 345

Importing and Exporting Data Protector Cells. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 345

Moving Client Systems Among Cells. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 346

Distributing the MoM Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 346

Configuring Data Protector Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 347

Managing Devices and Media for a Specific Cell . . . . . . . . . . . . . . . . . . . . . . . . . . . 347

Restoring, Monitoring, and Reporting in an Enterprise Environment. . . . . . . . . . . . 348

9. Managing the Data Protector Internal Database

In This Chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 350

About the Data Protector Internal Database. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 351

The IDB Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 352

Configuring the IDB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 356

Allocating Disk Space for Future Use . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 356

Preparing for the Database Recovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 358

Configuring the Database Reports and Notifications. . . . . . . . . . . . . . . . . . . . . . . . 368

Maintaining the IDB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 370

Reducing the Database Growth . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 373

Reducing the Database Current Size . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 374

Purging Obsolete Filenames . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 376

Extending the Database Size . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 376

Checking the Database Size . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 378

Checking the Consistency of the Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 379

Moving the Database to a Different Cell Manager . . . . . . . . . . . . . . . . . . . . . . . . . . 380

Restoring the IDB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 382

Restoring the IDB to a Temporary Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 382

Moving the IDB to the Original Location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 383

Recovering the IDB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 385

Overview of Database Recovery Methods . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 385

Identifying the Level of Database Corruption . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 387

Performing Guided Autorecovery. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 389

Handling Minor Database Corruption in the DCBF Part . . . . . . . . . . . . . . . . . . . . 390

Handling Major Database Corruption in the Filenames Part . . . . . . . . . . . . . . . . . 391

Recovering the Database Using IDB Recovery File and Changed Device. . . . . . . . 392

Page 12

Contents

Recovering the Database Without IDB Recovery File . . . . . . . . . . . . . . . . . . . . . . . 394

Recovering the Database from a Specific IDB Session. . . . . . . . . . . . . . . . . . . . . . . 396

Replaying IDB Transaction Logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 398

Recovering the Database to a Different Disk Layout. . . . . . . . . . . . . . . . . . . . . . . . 399

Updating the Database by Importing Media . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 401

10. Disaster Recovery

In This Chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 404

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 405

Preparing for a Disaster Recovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 410

Planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 410

Consistent and Relevant Backup. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 411

Updating the System Recovery Data (SRD) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 412

Assisted Manual Disaster Recovery of a Windows System . . . . . . . . . . . . . . . . . . . . . 416

Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 417

Limitation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 417

Preparation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 417

Recovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 422

Disk Delivery Disaster Recovery of a Windows Client . . . . . . . . . . . . . . . . . . . . . . . . 425

Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 425

Limitations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 426

Preparation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 426

Recovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 427

Enhanced Automated Disaster Recovery of a Windows NT/2000 System . . . . . . . . . 429

Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 430

Limitations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 431

Preparation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 432

Recovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 435

One Button Disaster Recovery of a Windows NT/2000 System . . . . . . . . . . . . . . . . . 438

Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 439

Limitations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 440

Preparation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 442

Recovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 444

Restoring the Data Protector Cell Manager Specifics . . . . . . . . . . . . . . . . . . . . . . . . 447

Making IDB consistent (all methods) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 447

Enhanced Automated Disaster Recovery Specifics. . . . . . . . . . . . . . . . . . . . . . . . . . 447

One Button Disaster Recovery Specifics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 448

Advanced Recovery Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 449

xii

Page 13

Contents

Restoring the Microsoft Cluster Server Specifics . . . . . . . . . . . . . . . . . . . . . . . . . . . 449

Restoring Internet Information Server (IIS) Specifics . . . . . . . . . . . . . . . . . . . . . . . 455

Manual Disaster Recovery of an HP-UX Client. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 457

Limitation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 457

Concept . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 457

Using Custom Installation Medium . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 458

Using System Recovery Tools. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 462

Disk Delivery Disaster Recovery of an HP-UX and Solaris Client . . . . . . . . . . . . . . 466

Limitations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 466

Preparation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 466

Recovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 469

Manual Disaster Recovery of an Unix Cell Manager . . . . . . . . . . . . . . . . . . . . . . . . . 471

Limitation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 471

Preparation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 471

Recovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 471

Troubleshooting Disaster Recovery on Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 473

General Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 473

Troubleshooting Assisted Manual Disaster Recovery . . . . . . . . . . . . . . . . . . . . . . . 474

Troubleshooting EADR and OBDR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 475

Troubleshooting Disk Delivery Disaster Recovery . . . . . . . . . . . . . . . . . . . . . . . . . . 477

Disk Delivery Disaster Recovery of a Media Agent Client. . . . . . . . . . . . . . . . . . . . 478

11. Customizing the Data Protector Environment

In This Chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 480

Global Options File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 481

Most Often Used Variables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 481

Using Omnirc Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 482

Firewall Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 485

Limiting the Range of Port Numbers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 485

Port Usage in Data Protector. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 488

Examples of Configuring Data Protector in Firewall Environments. . . . . . . . . . . . 492

12. Troubleshooting

In This Chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 506

Before Calling Your Support Representative . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 507

Data Protector Log Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 508

Location of Data Protector Log Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 508

Format of Data Protector Log Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 508

xiii

Page 14

Contents

Log Files and Their Contents. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 509

Debugging. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 511

Debugging Using the Data Protector GUI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 511

Debug Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 511

Trace File Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 512

INET Debug on UNIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 512

INET Debug on Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 513

CRS Debug on Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 513

CRS Debug in MS Cluster Environment. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 513

Sample Debugging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 514

Browsing Troubleshooting Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 516

When You Cannot Access Online Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . 517

Description of Common Problems. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 519

Troubleshooting Networking and Communication . . . . . . . . . . . . . . . . . . . . . . . . . . . 520

Hostname Resolution Problems. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 520

Client Fails with “Connection Reset by Peer” . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 523

Troubleshooting Data Protector Services and Daemons . . . . . . . . . . . . . . . . . . . . . . . 524

Problems Starting Data Protector Services on Windows . . . . . . . . . . . . . . . . . . . . . 524

Problems Starting Data Protector Daemons on UNIX. . . . . . . . . . . . . . . . . . . . . . . 526

Data Protector Processes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 527

Troubleshooting Devices and Media . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 529

Cannot Access Exchanger Control Device on Windows 2000/XP. . . . . . . . . . . . . . . 529

Device Open Problem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 529

Using Unsupported SCSI Adapters on Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . 530

Medium Quality Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 530

Medium Header Sanity Check. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 531

Other Common Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 531

Troubleshooting Backup and Restore Sessions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 533

Filenames Are Not Displayed Correctly in GUI . . . . . . . . . . . . . . . . . . . . . . . . . . . . 533

Full Backups Are Performed Instead of Incrementals . . . . . . . . . . . . . . . . . . . . . . . 533

Unexpected Mount Request for a Standalone Device. . . . . . . . . . . . . . . . . . . . . . . . 534

Unexpected Mount Request for a Library Device. . . . . . . . . . . . . . . . . . . . . . . . . . . 535

Unexpected Mounted Filesystems Detected . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 536

Data Protector Fails to Start a Scheduled Session . . . . . . . . . . . . . . . . . . . . . . . . . . 537

Data Protector Fails to Start an Interactive Session . . . . . . . . . . . . . . . . . . . . . . . . 538

Backup Protection Expiration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 538

Troubleshooting Application Database Restores . . . . . . . . . . . . . . . . . . . . . . . . . . . 539

Problems with non-ASCII Characters in Filenames . . . . . . . . . . . . . . . . . . . . . . . . 539

xiv

Page 15

Contents

HP-UX 11.X Shared Memory Problems. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 539

Troubleshooting Data Protector Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 540

Problems with Remote Installation of Windows Clients . . . . . . . . . . . . . . . . . . . . . 540

Name Resolution Problems when Installing the Windows Cell Manager. . . . . . . . 541

Troubleshooting User Interface Startup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 542

Inet Is Not Responding on the Cell Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 542

No Permissions to Access the Cell Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 542

Connection to a Remote System Refused on Windows or Novell NetWare . . . . . . . 543

Connection to Windows 95/98 Clients Fails . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 543

Troubleshooting the IDB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 544

Problems During the Upgrade of the IDB on Solaris . . . . . . . . . . . . . . . . . . . . . . . . 544

Problems While Running the User Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 547

Libraries (Executables) Missing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 547

Data Files (Directories) Missing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 548

Temporary Directory Missing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 549

Problems During Backup and Import . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 550

Performance Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 551

MMDB and CDB Are Not Synchronized . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 552

Troubleshooting Reporting and Notifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 554

Troubleshooting Data Protector Online Help. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 555

Troubleshooting Online Help on Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 555

Troubleshooting Online Help on UNIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 555

Check Whether Data Protector Functions Properly . . . . . . . . . . . . . . . . . . . . . . . . . . 557

Data Protector Checking and Maintenance Mechanism . . . . . . . . . . . . . . . . . . . . . 557

The User Check Failed Notification. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 558

Overview of Items to Be Checked . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 559

13. Integrations with Other Applications

In This Chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 564

Cluster Integrations with Data Protector. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 565

Cluster Concepts and Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 565

Cluster-Aware Databases and Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 568

Microsoft Cluster Server Integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 569

Cell Manager on Microsoft Cluster Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 570

Clients on Microsoft Cluster Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 570

Backing Up Data in a Cluster (MSCS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 571

Managing Cluster-Aware Backups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 572

MC/ServiceGuard Integration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 578

Page 16

Contents

Cell Manager on MC/ServiceGuard. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 578

Clients on MC/ServiceGuard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 587

Backing Up Data in a Cluster (MC/SG) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 588

Veritas Cluster Integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 590

Clients on Veritas Cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 590

Data Source Integration (DSI) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 592

Application Response Measurement (ARM) Integration. . . . . . . . . . . . . . . . . . . . . . . 594

ManageX Integration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 596

Access Points for System and Management Applications . . . . . . . . . . . . . . . . . . . . . . 597

Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 597

Data Protector Access Points . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 597

Examples. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 601

14. ADIC/GRAU DAS and STK ACS Libraries

In This Chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 604

ADIC/GRAU DAS and STK ACS Integrations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 605

Configuration Basics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 607

Media Management Basics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 607

The ADIC/GRAU DAS Library Device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 610

Direct Access to the Library: Installation and Configuration . . . . . . . . . . . . . . . . . 610

Connecting Library Drives. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 610

Preparing for Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 611

Installing the DAS Media Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 612

Using the Data Protector GUI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 618

Indirect Access to the DAS Library: Installation and Configuration . . . . . . . . . . . 619

Using Data Protector to Access the ADIC/GRAU Library . . . . . . . . . . . . . . . . . . . . 619

The STK ACS Library Device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 628

Direct Access to the Library: Installation and Configuration . . . . . . . . . . . . . . . . . 628

Media Management Basics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 628

Connecting Library Drives. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 629

Installing the ACS Media Agent to Use the StorageTek Library . . . . . . . . . . . . . . 629

Using Data Protector to Configure the STK ACS Library . . . . . . . . . . . . . . . . . . . . 634

Indirect Access to the Library: Installation and Configuration. . . . . . . . . . . . . . . . 634

Using Data Protector to Access the STK ACS Library. . . . . . . . . . . . . . . . . . . . . . . 635

Troubleshooting Library Installation and Configuration . . . . . . . . . . . . . . . . . . . . . . 645

A. Further Information

In This Appendix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .A-2

xvi

Page 17

Contents

Backing Up and Restoring UNIX Specifics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .A-3

VxFS Snapshot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .A-3

Enterprise File System (EFS) on HP-UX 10.x . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .A-6

Data Protector Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .A-8

Performance Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .A-10

The Infrastructure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .A-10

Configuring Backups and Restores . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .A-12

Example of Scheduled Eject of Media. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .A-16

Schedule the Report Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .A-16

Add the Report to the Report Group and Configure It . . . . . . . . . . . . . . . . . . . . . . .A-16

Copy the Script to the Specified Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .A-17

Examples of Pre-Exec and Post-Exec Commands for UNIX . . . . . . . . . . . . . . . . . . . .A-22

Disaster Recovery:

Move Kill Links on HP-UX 10.x . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .A-27

Creating a libaci.o on AIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .A-28

Example of the Package Configuration File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .A-30

Example of the Package Control File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .A-41

Example of the Package Configuration Script . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .A-48

Data Protector Log Files Example Entries. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .A-53

debug.log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .A-53

sm.log. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .A-55

inet.log. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .A-55

media.log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .A-56

upgrade.log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .A-56

Windows NT and Windows 2000 Manual Disaster Recovery Preparation Template A-59

Changing Block Size on Windows Media Agent. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .A-61

Glossary

Index

xvii

Page 18

Contents

xviii

Page 19

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-90149 November 2001 OmniBack II Release A.04.10

B6960-90057 August 2002 Data Protector Release

A.05.00

xix

Page 20

Page 21

Table 2

Conventions

The following typographical conventions are used in this manual.

Convention Meaning Example

Italic Book or manual

titles, and manual page names

Provides emphasis You must follow these steps.

Specifies a variable that you must supply when entering a command

Bold New terms The Data Protector Cell

Computer Text and items on the

computer screen

Command names Use the grep command ...

File and directory names

Process names Check to see if Data

Refer to the HP OpenView

Storage Data Protector Integration Guide for more

information.

At the prompt type: rlogin your_name where you supply your login name.

Manager is the main ...

The system replies: Press

Enter

/usr/bin/X11

Protector Inet is

running.

Window/dialog box names

Computer Bold

Keycap Keyboard keys Press Return.

xxi

Text that you must enter

In the Backup Options dialog box...

At the prompt, type: ls -l

Page 22

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

xxii

Page 23

Contact Information

General Information

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

Documentation Feedback

Training Information

General information about Data Protector can be found at http://www.openview.hp.com/products/data_protector/

Centers at http://support.openview.hp.com/support.jsp 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, see the HP

OpenView Storage Data Protector Software Release Notes

HP does not support third-party hardware and software. Contact the respective vendor for support.

Your comments on the documentation help us to understand and meet your needs. You can provide feedback at

http://ovweb.external.hp.com/lpe/doc_serv/

For information on currently available HP OpenView training, see the 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.

xxiii

Page 24

xxiv

Page 25

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 on 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 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. There are two versions of this manual:

• HP OpenView Storage Data Protector Windows Integration Guide This manual describes integrations running the Windows operating

systems, such as Microsoft Exchange, Microsoft SQL, Oracle, SAP R/3, Informix, Sybase, NetApp Filer, HP OpenView Network Node Manager and Lotus Domino R5 Server.

• HP OpenView Storage Data Protector UNIX Integration Guide This manual describes integrations running on the UNIX operating

system, such as: Oracle, SAP R/3, Informix, Sybase, NetApp Filer, HP OpenView Network Node Manager and Lotus Domino R5 Server.

xxv

Page 26

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 EMC Symmetrix/Fastrax Integration Guide

This manual describes how to install, configure, and use the EMC Symmetrix and EMC Fastrax integrations. It is intended for backup administrators or operators.

• The first part describes the integration of Data Protector with the EMC Symmetrix Remote Data Facility and TimeFinder features for Symmetrix Integrated Cached Disk Arrays. It covers the backup and restore of filesystems and disk images as well as online databases, such as Oracle and SAP R/3.

• The second part describes the integration of Data Protector with the EMC Fastrax. It covers the backup and restore of disk images as well as Oracle8i and SAP R/3 systems, using direct disk to tape technology.

HP OpenView Storage Data Protector HP SureStore Disk Array XP Integration Guide

This manual describes how to install, configure, and use the integration of Data Protector with HP SureStore Disk Array XP. It is intended for backup administrators or operators. It covers the backup and restore of Oracle, SAP R/3, Microsoft Exchange, and Microsoft SQL.

HP OpenView Storage Data Protector HP SureStore Virtual Array Integration Guide

This manual describes how to install, configure, and use the integration of Data Protector with HP SureStore Virtual Array. It is intended for backup administrators or operators. It covers the backup and restore of Oracle, SAP R/3 and Microsoft Exchange.

xxvi

Page 27

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 MPE/iX System User Guide

This document describes how to install and configure MPE/iX clients, and how to back up and restore MPE/iX data.

HP OpenView Storage Data Protector Integration Guide for HP OpenView Operations

This document 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).

HP OpenView Storage Data Protector Software Release Notes

This document gives a description of new features of HP OpenView Storage Data Protector A.05.00. It also provides information on supported configurations (devices, platforms and online database integrations, SAN configurations, EMC split mirror configurations, and HP SureStore XP configurations), required patches, limitations, as well as known problems and workarounds. An updated version of the supported configurations is available at http://www.openview.hp.com/products/data_protector/specifications/inde x.asp.

Online Help Data Protector provides online Help for Windows and UNIX platforms.

xxvii

Page 28

xxviii

Page 29

In This Book

The HP OpenView Storage Data Protector Administrator’s Guide describes how to configure and use the Data Protector network backup product. You must properly install Data Protector before you can start to configure it.

NOTE This manual describes Data Protector functionality without specific

information on particular licensing requirements. Some Data Protector functionality is subject to specific licenses. The related information is covered in the HP OpenView Storage Data Protector Installation and Licensing Guide.

Audience

This manual is intended for network administrators responsible for maintaining and backing up systems on the network.

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

xxix

Page 30

Organization

The manual is organized as follows:

Chapter 1 “Introducing Data Protector” on page 1. Chapter 2 “Configuring and Using Backup Devices” on page 17. Chapter 3 “Configuring Users and User Groups” on page 75. Chapter 4 “Managing Media” on page 89. Chapter 5 “Backup” on page 139. Chapter 6 “Restore” on page 243. Chapter 7 “Monitoring, Reporting, Notifications and the Event

Log” on page 279.

Chapter 8 “Manager-of-Managers Environment” on page 327. Chapter 9 “Managing the Data Protector Internal Database” on

page 349.

Chapter 10 “Disaster Recovery” on page 403. Chapter 11 “Customizing the Data Protector Environment” on

page 479.

Chapter 12 “Troubleshooting” on page 505. Chapter 13 “Integrations with Other Applications” on page 563. Chapter 14 “ADIC/GRAU DAS and STK ACS Libraries” on page

603.

Appendix A “Further Information” on page A-1. Glossary Definition of terms used in this manual.

xxx

Page 31

1 Introducing Data Protector

Chapter 1 1

Page 32

Introducing Data Protector

In This Chapter

This chapter contains some general principles on how Data Protector works, covered in these sections:

“The Data Protector Cell Environment” on page 3 “Using the Data Protector User Interface” on page 6 “Overview of the Tasks to Set Up Data Protector” on page 14

Chapter 12

Page 33

Introducing Data Protector

The Data Protector Cell Environment

The Data Protector cell is a network environment containing a Cell Manager, clients, and backup devices. The Cell Manager has the

main Data Protector control software installed and is the central point, from which the cell is administered and backup and restore operations are controlled. Systems that are to be backed up can be added to the cell and set up as Data Protector clients. When Data Protector performs a backup of data from these clients, it saves the data to media (such as magnetic tapes, or hard disks) contained within backup devices.

The Data Protector internal database (IDB) keeps track of the files backed up making it is easy to browse and restore them, ether singly or collectively.

The Cell Manager is the main control center for the cell and contains the IDB. It runs the core Data Protector software and the Session Manager, which starts and stops backup and restore sessions and writes session information to the IDB.

Any system within a chosen cell environment can be set up as a Data Protector client. Essentially, a client is a system that can be backed up, a system connected to a backup device with which the backup data can be saved, or both. The role of the client depends on whether it has a Disk Agent or a Media Agent installed.

A client that will be backed up using Data Protector must have a Disk Agent installed. Data Protector controls the access to the disk. The Disk Agent lets you back up information from, or restore information to, the client disk.

A client system that will control a for Data Protector must have a Media Agent installed. This software controls the access to the backup device. The Media Agent controls reading from and writing to a backup device’s media drive.

A Backup Device performs the actual recording of back-up data to, and retrieval of restore data from, a recording medium.

The physical object upon which the data is recorded, such as a DAT tape or a hard disk, is called the backup medium.

Chapter 1 3

Page 34

Introducing Data Protector

The Data Protector Cell Environment

NOTE For further information on these terms or on the principles of Data

Protector operation, see the HP OpenView Storage Data Protector Concepts Guide.

How a Backup Session Works

A backup session starts either when a backup is requested through the user interface, or when a scheduled backup is initiated. During this session, Data Protector backs up the requested filesystems and disks to the specified media.

1. The Cell Manager determines the type of session that has been requested (backup) and starts the appropriate Session Manager.

2. The Session Manager reads the backup specification and determines what needs to be backed up and which devices to use.

3. The Session Manager then starts a Media Agent for each media drive that will be used and a Disk Agent for each disk that will be read.

4. The Monitor window appears. This window lets you respond to mount requests and view the progress of a backup session.

5. The Disk Agents start sending data to the Media Agent.

6. If more than one Disk Agent is used, the Disk Agents send data to the Media Agent concurrently and the Media Agent places the data on the medium.

7. As each block of data is written to the medium, the Media Agent sends information to the Session Manager about what has been backed up. The Session Manager uses this information to update the catalog of backed-up files in the IDB.

How a Restore Session Works

A restore session starts when a restore is requested. During this session, Data Protector performs a restore of requested files and disks from the media.

1. You specify which filesystems to restore and how to restore them using the Data Protector user interface.

Chapter 14

Page 35

Introducing Data Protector

The Data Protector Cell Environment

2. The Cell Manager determines the type of session that has been requested (restore), and starts the appropriate Session Manager.

3. The Session Manager then determines which filesystems or directories to restore, which devices to use, and what restore options have been specified.

4. The Session Manager starts the appropriate Disk Agent and Media Agent. For example, a Media Agent is started for the media (tape) drive that will be used and a Disk Agent is started for the disk to which the data will be restored.

5. The Monitor window appears. This window lets you respond to mount requests and view the progress of a restore session.

6. The Media Agent starts sending data to the Disk Agent.

7. The Session Manager then updates the IDB and the Disk Agent writes the data to the disk.

Chapter 1 5

Page 36

Introducing Data Protector

Using the Data Protector User Interface

There is one Data Protector user interface, available on Windows and UNIX platforms. It consists of the Data Protector graphical user interface (GUI) and the command-line interface.

Using the Data Protector user interface, you can perform all Data Protector tasks.

Figure 1-1 HP OpenView Storage Data Protector Graphical User Interface

Chapter 16

Page 37

Introducing Data Protector

Using the Data Protector User Interface

Graphical User Interface

The Data Protector graphical user interface (GUI) uses features such as buttons and text boxes to enhance usability. Whenever possible, drop-down lists are provided to allow you to select from a list instead of typing in your selection. In addition, a comprehensive online Help system provides information about each window and each task.

Depending on the user rights, you can either use the GUI to access the complete Data Protector functionality or to access only specific contexts.

For more information on user rights, refer to “Data Protector User Rights” on page 77.

For more information on Data Protector contexts, refer to “Context List” on page 8.

Starting GUI on Windows Platforms

Starting GUI on UNIX Platforms

To start the Data Protector GUI on Windows platforms, do one of the following:

•Click Start button on the Windows desktop and click Data

Protector Manager from the HP OpenView Storage Data Protector program group to start the GUI for the complete Data

Protector functionality.

•Use the manager command to start the GUI for the complete Data Protector functionality. Context specific options for this command enable you to start one or more Data Protector contexts. For example, the command

manager -backup -restore starts Data Protector Backup and Restore contexts.

To specify the Cell Manager you want to connect to, use the following command: manager -server <Cell Manager_name>. For more information, use the manager -help command.

For more information on this commands, refer to the <Data_Protector_home>/docs/man/omnigui.wri man page.

To use the Data Protector GUI on UNIX platforms, enter: xomni to start the GUI with the complete Data Protector

functionality

xomniadmin to start the administration (configuration) of clients,

users, reports and IDB GUI

xomnibackup to start the backup GUI

Chapter 1 7

Page 38

Introducing Data Protector

Using the Data Protector User Interface

xomnicellmon to start the MoM cell monitoring GUI xomnimm to start the media and devices management GUI xomnimonitor to start the monitoring a single cell GUI xomnirestore to start the restore GUI xomniinstrec To start the instant recovery GUI. A special license is

needed to start this GUI. Refer to the HP OpenView Storage Data Protector HP SureStore Disk Array XP Integration Guide for more information on the instant recovery functionality and to the HP OpenView Storage Data Protector Installation and Licensing Guide for

more information on Data Protector licenses. xomnimom to start the Manager-of-Managers GUI For more information on these commands, refer to the omnigui man

page.

Elements of the Data Protector Graphical User Interface

For the visual representation of the GUI elements, refer to Figure 1-1 on page 6.

Context List The Context List is a drop-down list, from which you can select the

management contexts described below: Clients Controls all of the client systems in

the current Data Protector cell. You can add, delete, and monitor any client within the cell.

Users Adds and removes users, user groups

and their rights.

Devices & Media Controls device and media

maintenance and access to media which stores the data.

Backup Controls which, how, and where data

is backed up.

Restore Controls which, how, and where data

is restored.

Chapter 18

Page 39

Introducing Data Protector

Using the Data Protector User Interface

Instant Recovery Controls the split mirror instant

recovery processes. A special license is needed to display this context. Refer to the HP OpenView Storage

Data Protector HP SureStore Disk Array XP Integration Guide for more

information on the instant recovery functionality and to the HP

OpenView Storage Data Protector Installation and Licensing Guide for

more information on Data Protector licenses.

Reporting Allows you to get information on your

cell configuration, backup specifications, media and media pools, as well as get information on specific sessions and objects.

Internal Database Allows you to get information on the

IDB storage capacity, database objects, and sessions.

Monitor Allows you to monitor sessions that

are in progress.

Scoping Pane The Scoping Pane provides a tree of items that can be selected to open

a view. Selecting an item in the Scoping Pane displays information in the Results Area.

Results Area Selecting an item in the Scoping Pane displays corresponding

information in the Results Area. If you click Clients in the Scoping Pane, the Results Area displays a list of all the clients within your cell.

Navigation Tabs Navigation Tabs appear at the bottom of the Scoping Pane. These tabs

allow you to switch between the two possible item list views in the Scoping Pane: Objects and Tasks. Not every Scoping Pane has these views. Clicking on a Navigation Tab changes the items displayed in the Scoping Pane.

Tab N ame What the Tab Displays in the Scoping Pane

Chapter 1 9

Page 40

Introducing Data Protector

Using the Data Protector User Interface

Objects A hierarchical presentation of data, similar to the

directory tree in Windows Explorer. For example, in the

Devices & Media context, the Scoping Pane will display

the list of devices and media configured with Data

Protector. Tasks A list of tasks that you can perform. Clicking a task

displays a wizard that will walk you through an entire

task, such as backing up a file.

Results Tab The name on the Results Tab corresponds to the name of the item

currently selected in the Scoping Pane. You click the Pin icon from the toolbar to make this view "stick" and keep it available for the future. In case you need to use the GUI to look up some other information but want to continue with the previous view later, you can access this view by selecting the "pinned" tab. You can remove one or more tabs by right-clicking the area and selecting Remove Tab or Remove Other Tabs.

The Command-Line Interface

The command-line interface (CLI) follows the standard UNIX format for commands and options and provides complete Data Protector functionality. You can use these commands in scripts to speed up your commonly performed tasks.

The omniintro man page lists all supported Data Protector commands, as well as eventual differences between commands on UNIX and Windows platforms.

See also “Data Protector Commands” on page A-8.

Chapter 110

Page 41

Introducing Data Protector

Using the Data Protector User Interface

Data Protector Online Resources

Information about Data Protector is available from this manual and online Help system. This manual contains the information you need to plan and administer your Data Protector network, and information on some more commonly performed tasks. The online Help system contains the information you need to perform all available tasks.

The following Data Protector online resources are available: Help Topics Online Help with task instructions

and reference information. Selection of topics can be performed using contents list, index or search facility.

Help Navigator Context-sensitive Help that provides

detailed help on the current task.

Online Documentation Online manuals in PDF format that

can be read with the Adobe Acrobat Reader.

Data Protector on the Web Opens your Web browser to Data

Protector homepage, where more information about Data Protector can be found.

Online Support This option invokes your Internet

browser so that you can find information on the HP OpenView interactive Online Support service.

About Displays version and copyright

information for Data Protector as well as licensing information.

You can access the online resources by either using the Help drop-down menu or the Help buttons provided on the Data Protector windows.

Hyperlinks (cross-references) to additional information and definitions help you navigate through online Help. You click the hyperlinked word or phrase to jump to the new topic. Hyperlinked words and phrases are marked with either solid underlining or different color.

Chapter 1 11

Page 42

Introducing Data Protector

Using the Data Protector User Interface

Starting and Using the Help Navigator

The Help Navigator provides context-sensitive online Help, which can be used to find information about the current GUI panel or task.

If the GUI concerned is running on Windows, the Help Navigator is dynamic: Once it is started, its contents automatically change as the user proceeds to the next page of the wizard or to another view in the Data Protector user interface.

To start the Help Navigator, either:

•Press F1

• Click Help Navigator from the pull-down the Help menu, or

• Click the Help Navigator icon (the Question Mark) on the button bar

Using the Online Manuals

Data Protector provides online manuals in PDF format that can be read using the Adobe Acrobat Reader software. Once installed, the online manuals reside in the <Data_Protector_home>\docs directory (Windows) or the /opt/omni/doc/C directory (HP-UX or Solaris) on the Cell Manager system.

Using Microsoft Management Console (MMC)

On Windows systems, it is possible to integrate the Data Protector GUI with the Microsoft Management Console.

The Microsoft Management Console (MMC) is a Graphical User Interface (GUI) that lets you manage and run your administrative tools within a common interface environment. You can add already installed software, hardware, or network management applications to the console, where the primary type of tool that can be added to the console is called a snap-in.

Data Protector snap-in, known as OB2_Snap, provides a basic integration of Data Protector and MMC which leads you to the Data Protector home page, to the Data Protector Web/Java Reporting, and lets you start the Data Protector GUI on Windows from MMC. Proceed as follows to add OB2_Snap to MMC.

1. Download the MMC software from

ttp://www.microsoft.com/downloads/.

Chapter 112

Page 43

Introducing Data Protector

Using the Data Protector User Interface

2. From the Windows desktop, click Start, and then select Run.

3. In the Open text box, enter mmc to open the Microsoft Management

Console window.

4. From the Console menu, select Add/Remove Snap-in. In the

Standalone property page of the Add/Remove Snap-in window, click Add.

5. In the Add Standalone Snap-in window, select HP OpenView

Storage Data Protector. Click Close to exit the window, then click OK to get back to the Microsoft Management Console window.

The HP OpenView Storage Data Protector item will be displayed under Console Root. Once you have added the applications to MMC, save the file as <Console_Name>.msc.

Chapter 1 13

Page 44

Introducing Data Protector

Overview of the Tasks to Set Up Data Protector

Although configuring Data Protector is easy, some advanced planning will help you configure the environment and optimize your backups. This section provides an overview of the global tasks to set up a backup environment.

Depending on the size and complexity of your environment, you may not need to go through all these steps.

1. Analyze your network and organizational structure. Decide which

systems need to be backed up. For more information refer to the HP OpenView Storage Data

Protector Concepts Guide.

2. Check whether there are any special applications and databases

which you want to back up, such as Microsoft Exchange, Microsoft SQL, Oracle, SAP R/3, or others. Data Protector provides specific integrations with these products.

Refer to the HP OpenView Storage Data Protector Integration Guide for instructions on how to configure the integrations.

3. Decide on the configuration of your Data Protector cell, such as the

• system to be your Cell Manager

• the systems on which you want to install the user interface

• type of backup - local backup versus network backup

• systems to control backup devices

4. Purchase the required Data Protector licenses for your setup. This

way you obtain the passwords you need to have installed. Alternatively, you can operate Data Protector using an instant-on password. However, this is valid only for 60 days from the date of installation. Refer to the HP OpenView Storage Data Protector Installation and Licensing Guide for details.

5. Decide how you want to structure your backups:

• Which media pools would you like to have and how will they be used?

Chapter 114

Page 45

Introducing Data Protector

Overview of the Tasks to Set Up Data Protector

• Which devices will be used and how?

• Which user groups do you want to have and what will they do?

• How many backup specifications do you want to have and how should they be grouped?

6. Install the Data Protector Cell Manager and Installation Server(s). Then use the Data Protector GUI to distribute Data Protector agents to other systems. Also connect the devices (tape drives) to the systems that will control them. See the HP OpenView Storage Data Protector Installation and Licensing Guide for detailed instructions.

7. Configure the device(s). See Chapter 2, “Configuring and Using Backup Devices,” on page 17.

8. Configure the pools and optionally prepare the media. See Chapter 4, “Managing Media,” on page 89.

9. Setup the backup specifications, including scheduling. See Chapter 5, “Backup,” on page 139.

10.Configure the IDB. See Chapter 9, “Managing the Data Protector Internal Database,” on page 349.

11.Configure reports, if required. See Chapter 7, “Monitoring, Reporting, Notifications and the Event Log,” on page 279.

12.Consider preparing for disaster recovery if your disk fails. See Chapter 10, “Disaster Recovery,” on page 403.

13.Become familiar with tasks such as:

• How to work with failed backups

• Performing restores

• Testing disaster recovery

• IDB maintenance

Chapter 1 15

Page 46

Introducing Data Protector

Overview of the Tasks to Set Up Data Protector

Chapter 116

Page 47

2 Configuring and Using Backup

Devices

Chapter 2 17

Page 48

Configuring and Using Backup Devices

In This Chapter

This chapter includes information on the following topics:

“Configuring Backup Devices” on page 19 “Configuring Standalone Devices” on page 22 “Configuring File Devices” on page 24 “Configuring Library Devices” on page 26 “Configuring Libraries with Multiple Systems” on page 29 “Configuring Magazine Devices” on page 31 “Configuring Stacker Devices” on page 33 “Configuring a Library for Mixed Media” on page 35 “Configuring Devices for Direct Backup” on page 36 “Support of New Devices” on page 39 “Using Several Drive Types in a Library” on page 40 “Configuring Magazine Devices” on page 31 “Shared Devices in the SAN Environment” on page 42 “Drive Cleaning” on page 57 “Busy Drive Handling” on page 61 “Activating Barcode Support” on page 62 “Disabling a Backup Device” on page 65 “Removing a Backup Device” on page 66 “Device Locking” on page 68 “Device Concurrency, Segment and Block Size” on page 70

NOTE Backup devices (like tape drives) are subject to specific Data Protector

licenses. See the HP OpenView Storage Data Protector Installation and Licensing Guide for details.

Chapter 218

Page 49

Table 2-1

Configuring and Using Backup Devices

Configuring Backup Devices

Preparation of a backup device consists of connecting the device to the system and knowing which of the (working) associated device files (SCSI address) is to be used:

1. Connect the device to a computer. Refer to the documentation that comes with the device.

2. Make sure that you have done the following:

UNIX systems

Windows systems

Create or find the device filename for a device connected to a UNIX system. For detailed steps, refer to the online Help index keyword “creating device filenames” or “finding device filenames”. For further information, refer to “Appendix B” of the HP

OpenView Storage Data Protector Installation and Licensing Guide.

Provide a SCSI II address and load the driver that will be used with a device connected to a Windows system. Tape drives can have:

• the Windows native tape driver unloaded (preferred).

• the Windows native tape driver loaded. The device filename depends on whether a

Windows native tape driver is used with a particular tape drive.

For detailed steps, refer to the online Help index keyword “creating SCSI addresses”. For further information, refer to “Appendix B” of the HP

OpenView Storage Data Protector Installation and Licensing Guide.

Chapter 2 19

Page 50

Table 2-1

Configuring and Using Backup Devices

Configuring Backup Devices

Windows 2000 robotics drivers

On Windows 2000, disable the Windows 2000 medium changer (robotics) driver before you configure the robotics device with Data Protector. For detailed steps, refer to the index keyword “robotics drivers, Windows 2000”. For further information, refer to “Appendix B” of the HP OpenView Storage Data Protector Installation and Licensing Guide.

Cartridge Memory

If your backup device is connected to a Windows NT or a Windows 2000 system and uses media with Cartridge Memory, make sure that your SCSI II card supports execution of 16-byte CDB SCSI II commands. On the UNIX and Novell platform, you need a tape driver which supports the respective SCSII II commands.

3. Boot the system to have the device recognized by the system.

4. Configure the device, as described in the following sections, so that you can use it with Data Protector.

5. Prepare the media that you want to use with your backups. See “Formatting Media” on page 99 to learn how to format your media.

A default media pool is used with each device so that you do not have to create one. If you want to create your own media pool, refer to “Creating a Media Pool” on page 94.

Figure 2-1 shows the relationship between the backup specification, devices, and media pools. The devices are referred to in the backup specification, while each device is linked to a default media pool. This media pool can be changed in the backup specification.

Chapter 220

Page 51

Configuring and Using Backup Devices

Configuring Backup Devices

Figure 2-1 How Backup Specifications, Devices, and Media Pools Relate

Chapter 2 21

Page 52

Configuring and Using Backup Devices

Configuring Standalone Devices

What Are Standalone Devices?

How to Configure a Standalone Device?

TIP You can also let Data Protector automatically configure most common

Standalone devices are simple backup devices with one drive that reads from or writes to one medium at a time. They are used for small-scale backups. When a medium is full, the operator has to manually replace it with a new medium so that the backup can proceed. Standalone devices are not appropriate for large, unattended backups.

Data Protector provides simple configuration and management of media used in standalone backup devices.

Once you have prepared the device for configuration as described in “Configuring Backup Devices” on page 19, configure a standalone device so that you can use it with Data Protector. In the Add Device wizard, specify the Standalone device type. Refer to Figure 2-2. For detailed steps and examples, refer to the online Help index keyword “configuring standalone devices”.

Data Protector supports a specific set of backup devices. Refer to the HP OpenView Storage Data Protector Software Release Notes for a detailed list of supported devices and their corresponding media types.

In case you want to use a device that is not in the list of supported devices, refer to “Support of New Devices” on page 39.

devices. You still need to prepare the media for a backup session, but Data Protector determines the name, policy, media type, media policy, and the device’s SCSI II address or device file. For detailed steps, refer to the online Help index keyword “autoconfiguring backup devices”.

Chapter 222

Page 53

Figure 2-2 Specifying Device Type and Name

Configuring and Using Backup Devices

Configuring Standalone Devices

Configuring Device Chains

Data Protector allows you to configure standalone devices of the same type into device chains. When a medium in one device becomes full, the backup automatically continues on the medium in the next device in the device chain. Device chains are possible for only one Media Agent, that is, you can connect a device chain to only one system.

The configuration is the same as for a standalone device, except that you enter multiple SCSI addresses (on Windows) or device filenames (on UNIX).

NOTE The order in which the devices are added determines the order in which

Data Protector uses them.

When all of the media in a device chain are full, Data Protector issues a mount request. The operator must replace the medium in the first device with a new medium, format it, and then confirm the mount request. Data Protector can immediately use media that are recognized and unprotected. Data Protector can also use blank media, so that you do not have to format them.

Chapter 2 23

Page 54

Configuring and Using Backup Devices

Configuring File Devices

What Are File Devices?

Handling Mount Requests

A file device is a file in a specified directory to which you back up data instead of writing it to a tape. File devices are intended for test purposes. It is not recommended that you use file devices as your principle device type due to the burden on media management. File devices are available for standalone devices and Jukebox devices simulation.

The default capacity of a file device is 100 MB. Data Protector never measures the amount of free space on the filesystem; it takes either the default or the specified capacity as the file size limit. The largest capacity specified for a file is 4 GB. Data Protector does not support using compressed files for file devices. You can change the default file size by changing the FileMediaCapacity parameter in the <Data_Protector_home>\Config\Options\global file on the Windows Cell Manager or in the /etc/opt/omni/options/global file on the HP-UX or Solaris Cell Manager. You specify the capacity of a file device when you first format the medium. When you reformat the medium, you can specify a new size; however, the originally specified size will be used. You can change the capacity of a file device only by deleting the file from the system.

The path to a file device can be anywhere, whether it is an internal drive or an external portable hard drive.

Media are handled differently from physical devices. When a standalone file device (medium) becomes full, Data Protector tries to write to the same file again. Data Protector does not recognize that any other file exists, so it issues a mount request. When the mount request occurs, the existing file has to be moved or renamed (for example, by exchanging the ZIP media). The original file should no longer exist after the move. You then need to confirm the mount request. Data Protector will recreate the original file with the default file capacity. After the backup is finished, the file created by Data Protector contains the last part of the backup.

For Jukebox file devices, Data Protector issues a mount request when all media (files) are full.

Chapter 224

Page 55

Configuring and Using Backup Devices

Configuring File Devices

Prerequisite Before you configure a file device on a Windows system, disable the file

compression option. This can be done using Windows Explorer. Right-click the file, select Properties and deselect Compress under Attributes. If Compress is selected, Data Protector will not be able to write to the file device.

IMPORTANT It is recommended that you do not use the name of an existing file for

configuring a file device since the existing file will be overwritten. It is also recommended that you do not use the same filename for

configuring several file devices because every time that a file device will access the file, it will be overwritten.

How to Configure File Devices?

To create a standalone file device, specify the Standalone device type in the Add Device wizard. Refer to Figure 2-2. As a device address, specify a pathname for the file device, for example, b:\My_Backup. Refer to Figure 2-3. For detailed steps, refer to the online Help index keyword “configuring file devices”.

To create a jukebox file device, specify the Jukebox device type in the Add Device wizard. As device addresses, specify different pathnames that will simulate jukebox slots. For detailed steps, refer to the online Help index keyword “configuring file devices”.

Figure 2-3 Specifying a Pathname for a File Device

Chapter 2 25

Page 56

Configuring and Using Backup Devices

Configuring Library Devices

What Are Library Devices?

Slot Number Each slot in the device’s repository holds one medium. Data Protector

Drive Index The drive index identifies the mechanical position of the drive in the

SCSI-II library devices, also called autoloaders, are large backup devices. They contain a number of media cartridges in a device’s repository and can have multiple drives handling multiple media at the same time. Most library devices also allow you to configure automatic drive cleaning, which is performed by Data Protector when the drive gets dirty. Refer to “Drive Cleaning” on page 57.

A library device has a SCSI ID for each drive in the device and one for the library robotic mechanism. This mechanism moves media from slots to drives and back again. For example, a library with four drives has five SCSI IDs, four for the drives and one for the robotic mechanism.

assigns a number to each slot, starting from one. When managing a library, you refer to the slots using their numbers. For example, a library with 48 repository slots has slot numbers 1, 2, 3, 4, 5, 6...47, 48.

library. Refer to Figure 2-4. The index number is relevant for the robotics control. The robot knows

only index numbers and has no information about the SCSI address of the drive. The drive index is a sequential integer (starting from 1) which has to be coupled with the SCSI address of this drive. For example, for a four drive library, the drive indexes are 1,2,3,4.

Drive SCSI Address

If you have only one drive in the library, the drive index is 1.

The drive index must match the corresponding SCSI address. This means that you need to configure the pairs as follows:

SCSI address_A for index one, SCSI address_B for index two, and so on.

Chapter 226

Page 57

Configuring and Using Backup Devices

Configuring Library Devices

NOTE It is not necessary to configure all drives for use with Data Protector. You

can configure one media pool for all drives, or have an independent media pool for each drive. It is recommended that you use the default media pool when configuring a device.

Figure 2-4 Drive Index to SCSI Address Mapping

How to Configure a Library Device?

Once you have prepared the device for configuration as described in “Configuring Backup Devices” on page 19, configure a library device, including its drive(s). The Add Device wizard guides you through both configurations. For detailed steps and examples, refer to the online Help index keyword “configuring SCSI libraries”.

TIP You can also have Data Protector automatically configure the library

devices for you. You still need to prepare the media for a backup session, but Data Protector determines the name, policy, media type, media

Chapter 2 27

Page 58

Configuring and Using Backup Devices

Configuring Library Devices

policy, and the device file or SCSI address of the device, as well as configures the drive and slots. For detailed steps, refer to the online Help index keyword “autoconfiguring backup devices”.

To verify the device configuration, right-click the created drive, and choose Scan Medium. If the device is configured correctly, Data Protector will be able to load, read, and unload media in the slots.

What’s Next? If you have configured all the backup devices you want to use with Data

Protector, then do the following:

• Add media to the media pools that you will use with the newly configured device. See “Adding Media to a Media Pool” on page 98.

• If you want to configure a cleaning tape, see “Drive Cleaning” on page 57.

• If your device uses barcodes, see “Activating Barcode Support” on page 62 for more information.

• Configure a backup for your data. See Chapter 5, “Backup,” on page 139.

Chapter 228

Page 59

Configuring and Using Backup Devices

Configuring Libraries with Multiple Systems

You can configure a library so that each drive receives data from a different system running a Data Protector Media Agent. The library robotics control is still performed by one system. This improves performance in high-end environments by allowing local backup, instead of having to move the data over the network.

Prerequisites • Each client system that you want to use with the drives in the library

must have the Data Protector Media Agent component installed.

• You need to have connected the backup device to the system and a working device file (SCSI address) must exist before you can configure the device for use with Data Protector.

For more information on multi-drive support, see the HP OpenView Storage Data Protector Concepts Guide.

How to Configure Libraries with Multiple Systems?

TIP To verify the device configuration, select a range of slots from the library

What’s Next? If you have configured all the backup devices you want to use with Data

Configure a library as described in “Configuring Library Devices” on page 26. When you are prompted to configure drives in the library, specify the client system that you want to use with each drive. For detailed steps, refer to the online Help index keyword “configuring libraries for multiple systems”.

and then click Scan from the Actions menu. If the device is configured correctly, Data Protector will be able to load, read, and unload media back into the slots.

Protector, then do the following:

• Add media to the media pools that you will use with the newly configured device. See “Adding Media to a Media Pool” on page 98.

• If you want to configure a cleaning tape, see “Drive Cleaning” on page 57.

• If your device uses barcodes, see “Activating Barcode Support” on page 62.

Chapter 2 29

Page 60

Configuring and Using Backup Devices

Configuring Libraries with Multiple Systems

• Configure a backup. See Chapter 5, “Backup,” on page 139.

Chapter 230

Page 61

Configuring and Using Backup Devices

Configuring Magazine Devices

What Are Magazine Devices?

Prerequisite Create at least one media pool with the Magazine Support option set.

How to Configure a Magazine Device?

TIP You can also let Data Protector automatically configure your device for

Magazine devices group a number of media into a single unit called a magazine. Therefore, a magazine allows you to handle large amounts of data more easily than when using many individual media.

This allows you to perform media management tasks on magazines as sets or on single media.

You can also configure automatic cleaning of a dirty drive using a cleaning tape. See “Drive Cleaning” on page 57 for detailed instructions.

See “Adding Media to a Media Pool” on page 98.

Magazines must be configured as libraries. Select the SCSI-II Library device type in the Add Device wizard. The media pool to which magazines belong needs to have the Magazine Support option selected. For detailed steps, refer to the online Help index keyword “configuring SCSI libraries”.

you. You still need to prepare the media for a backup session, but Data Protector determines the name, policy, media type, media policy, and the device file or SCSI address of the device, as well as configures the drive and slots. For detailed steps, refer to the online Help index keyword “autoconfiguring backup devices”.

To verify the device configuration, right-click the created drive, and then choose Scan. If the device is configured correctly, Data Protector will be able to load, read, and unload media in the slots.

What’s Next? If you have configured all the backup devices you want to use with Data

Protector, then do the following:

• If you want to configure a cleaning tape, see “Drive Cleaning” on page 57.

• If your device uses barcodes, see “Activating Barcode Support” on page 62 for more information.

Chapter 2 31

Page 62

Configuring and Using Backup Devices

Configuring Magazine Devices

• Configure a backup for your data. See Chapter 5, “Backup,” on page 139.

Chapter 232

Page 63

Configuring and Using Backup Devices

Configuring Stacker Devices

What Are Stacker Devices?

How to Configure a Stacker Device?

Stacker Device Media Management

Example 1. Manually load the first media.

A stacker is a single device with one drive and sequentially accessed media. Using stacker devices requires more human media management than for using a small library. Data Protector provides simple configuration and management of media used in stacker backup devices.

To create a stacker device, specify the Stacker device type in the Add Device wizard. For detailed steps, refer to the online Help index keyword “configuring stacker devices”.

The operations scan, verify, or format have to be run separately on each medium in a stacker device. When performing these operations, use the Eject medium after operation option, in order to have each medium loaded automatically (only the first medium should be loaded manually). When all the tapes in the stacker magazine are used, the magazine must be unmounted manually and the next one inserted.

Stackers load media in sequential order, therefore a Loose media allocation policy is recommended. A Strict policy would require media to be loaded in the same order as they are to be used.

2. Run format/verify/scan (with Eject after operation enabled) -- (next tape will be loaded automatically).

3. Repeat step 2 until all tapes are finished.

4. When all the tapes in the stacker magazine are used, unmount the magazine manually and insert the next one.

NOTE If a medium is not properly loaded, then Data Protector will abort the

medium session.

Chapter 2 33

Page 64

Configuring and Using Backup Devices

Configuring Stacker Devices

Backup and Restore with Stacker Devices

Only the first medium has to be manually loaded. When a tape is full, it is ejected and the next tape is loaded automatically. When all the tapes are used in a stacker magazine, the magazine has to be unmounted manually and the next one has to be inserted. Again the first tape has to be loaded manually into the drive.

NOTE A backup or restore session will not be aborted if media are not present,

but a mount request will be issued instead. The whole session will not be aborted if a user does not change stacker magazines within a time out period.

Chapter 234

Page 65

Configuring and Using Backup Devices

Configuring a Library for Mixed Media

A mixed media library contains media of several types, such as DLT and magneto-optical. It uses identical robotics to move all the media (regardless of media type) between slots and drives.

In order to use this library functionality, configure several (sub)libraries; one library definition per media type.

To take full advantage of this feature supported by Data Protector, perform the following steps:

• Configure at least one media pool (or use the default pool) per media type.

• Configure the library robotics once per media type, including the slot range for that media type. Make sure the robotics control (SCSI path on Windows systems or device file on UNIX systems) for each of the library robotic definitions resides on the same host and that they are identical.

• Configure all the drives for a media type and link them to the related library robotic and media pool. Make sure the drive index is unique for each physical device, regardless of media type.

Chapter 2 35

Page 66

Configuring and Using Backup Devices

Configuring Devices for Direct Backup

This section provides the configuration steps for backup devices used in a direct backup environment. Refer to the HP OpenView Storage Data Protector Concepts Guide for a more detailed information on direct backup concepts.

Direct backup is a Data Protector backup solution in a SAN environment. Please read the section “Shared Devices in the SAN Environment” on page 42 for general information on SAN environments. Note that the direct backup device configuration steps differ from the configuration steps described in the mentioned section, and are given in this section.

A direct backup environment consists of the following:

• a SAN network

• internal or external Fibre Channel bridge(s) (FC bridge)

• backup device(s) connected to FC bridge(s) (standalone or SCSI-II library)

• physical XCopy engine(s) (present on an FC Bridge)

• disk array(s) assuring point-in-time stability of data (HP SureStore Disk Array XP or HP SureStore Virtual Array)

• application system(s) connected to the disk array original disk(s)

• backup system(s) connected to the disk array mirror disk(s) and controlling the SCSI-II library robotics and SCSI-II library/standalone device drives

An internal FC bridge is embedded in the backup device, whereas an external FC bridge resides at any point in the SAN.

A backup device used in the direct backup environment is identified by the World Wide Name (WWN) of the Fibre Channel bridge that it is connected to or is embedded in the backup device, and by the device (standalone device) or drive (SCSI-II library) Logical Unit Number (LUN) as seen on the SAN. If SCSI-II library is used, its robotics does not have to be connected to a FC bridge.

Chapter 236

Page 67

Configuring and Using Backup Devices

Configuring Devices for Direct Backup

Backup Device Auto-detection

XCopy Engine There can be more than one physical XCopy engine in a direct backup

The XCopy engine must reside on the FC bridge to which the backup device or drive is connected (external FC bridge), or on the internal FC bridge. A backup device is, using direct backup functionality, auto-detected, meaning that WWN and LUN for the device are detected anew whenever a direct backup session is started. If auto-detection is not used, the WWN and the LUN parameters must be entered manually; the LUN must be reconfigured every time the LUN changes.

environment. Each of these physical XCopy engines can have more logical XCopy engines configured and assigned. Which of these logical XCopy engines will be used in a direct backup session is specified in the direct backup specification by specifying the backup device(s) to be used in the direct backup session and assigning them a logical XCopy engine. The physical XCopy engine behind the logical XCopy engine specified in the backup specification must be configured for the backup system specified in the backup specification.

The following types of backup devices are supported for a Data Protector direct backup:

•standalone devices

• SCSI-II libraries

Configuration Procedure

Refer to the following online Help index keywords and perform any necessary steps before configuring backup devices as described later on in this section:

• online Help index keyword “preparing backup devices”

• online Help index keyword “configuring direct backup environment”

Configuring a backup device for direct backup consists of the following:

1. configuring a standalone device or SCSI-II library.

2. configuring XCopy engines.

3. if direct library access will be used, configuring the libtab file.

Chapter 2 37

Page 68

Configuring and Using Backup Devices

Configuring Devices for Direct Backup

Configuring Standalone Devices

Refer to the online Help index keyword “configuring standalone devices for direct backup” for detailed information on how to configure a standalone device for a direct backup.

Configuring SCSI-II Libraries

Refer to the online Help index keyword “configuring SCSI-II libraries for direct backup” for detailed information on how to configure a SCSI-II library for a direct backup.

Configuring XCopy Engines

Refer to the online Help index keyword “configuring XCopy engine” for detailed information on how to configure an XCopy engine.

Configuring the libtab File

Configuration of the libtab file is necessary only if direct library access is to be used.

Refer to the “Manually Configuring the libtab Files” on page 52 for detailed information on how to configure the libtab file.

Chapter 238

Page 69

Configuring and Using Backup Devices

Support of New Devices

To use a device that is not listed as supported in the HP OpenView Storage Data Protector Software Release Notes, download the latest

software package for the scsitab file from the HP OpenView World Wide Web site at http://www.openview.hp.com/products/data_protector/

IMPORTANT Modifying the scsitab file is not supported.

After you have downloaded the scsitab software package, follow the installation procedure provided with the software package.

The scsitab file is located on the system to which the device is connected, on the following location:

• <Data_Protector_home>\scsitab on Windows platforms

• /opt/omni/scsitab on HP-UX and Solaris platforms

Support of New Devices

• /usr/omni/scsitab on other UNIX platforms

If you still receive the same error while configuring your device, please contact HP Support to get information about when the device will be supported.

Chapter 2 39

Page 70

Configuring and Using Backup Devices

Using Several Drive Types in a Library

Using several drive types of a similar technology like DLT 4000/7000/8000 (the same is true within the DDS family) in the same library can lead to problems when you use the media in any drive, but do not ensure a common format on all media.

For example, at restore time, a DLT 4000 cannot read a tape that has been written with a DLT 8000 (highest density). Compressed and non-compressed media cannot be used interchangeably.

To avoid these kind of problems, you can either use a common density setting for all your media, or you can separate your media pools. Both of these solutions are described in the following sections.

Same Density Setting

Different Media Pools (on UNIX and Windows)

This method uses a common format on all media, which allows you to use all media interchangeably in any drive.

For devices used on Windows systems, you need to consult the drive documentation for information about using a specific write density.

On UNIX systems, you can set the density for drives by selecting the related device filenames and using them in the device definitions. The density must be set at the same value. For example, in case of DLT 4000 and DLT 7000 drives, the DLT 4000 drive density should be set.

Make sure the block size setting of the devices used is the same. This setting in the device definition must already be used at the time the media is formatted.

The free-pool concept can be used as desired. During restore, any drive can be used with any media. On HP-UX, you can set the density of a drive when creating the device

filename. See Appendix B, “Creating the Device Files on HP-UX”, in the HP OpenView Storage Data Protector Installation and Licensing Guide for more information.

This method clearly separates the media used by one group of drives from the media used by another group of drives, allowing you to better optimize drive and media usage.

Chapter 240

Page 71

Configuring and Using Backup Devices

Using Several Drive Types in a Library

On Windows and UNIX systems, you can configure separate media pools for different groups of drives. This allows you to use different density settings for different drive types. For example, you could create a DLT 4000 pool and a DLT 8000 pool.

The related setting in the device definition must be used at the time the media is formatted. For example, the media in the pool for the DLT 8000 highest density must be formatted by a DLT 8000 in highest density setting.

The free-pool concept cannot be used across such pools. This would not identify media from the other pool to the devices correctly, they would be seen as “foreign” media. The free pool concept can at most be used only with one of such pools (like the DLT 8000 pool), in case the same media type (DLT) is written in an incompatible way.

Care must be taken during restore, since media from a certain pool can only be used with related devices.

To configure new media pools, refer to the online Help index keyword “configuring media pools”.

To modify media pool settings for a drive, modify the drive properties. For detailed steps, refer to the online Help index keyword “modifying, media pools”.

Chapter 2 41

Page 72

Configuring and Using Backup Devices

Shared Devices in the SAN Environment

This section describes some of the basic concepts of Storage Area Networks (SANs). For further conceptual information, see the HP OpenView Storage Data Protector Concepts Guide.

The concepts and instructions provided here are the following:

• Device locking when the library is accessed exclusively by Data Protector

• Using the Data Protector user interface to configure the library robotics and drives

• Locking library robotics and drives

• Direct versus indirect library access

What Is SAN? Storage Area Network (SAN), a network dedicated to data storage, is

based on high-speed Fibre Channel technology. SAN lets you offload storage operations from application servers to a separate network. Data Protector supports this technology by enabling multiple hosts to share storage devices connected over a SAN, which allows multiple-system <—> multiple-device connectivity. This is done by defining the same physical device multiple times, for example, once on every system that needs access to the device.

Key Concepts There are some key concepts to consider when using Data Protector in a

SAN environment:

• Each system can have its (pseudo-)local device, although the devices are typically shared among several systems. This applies to individual drives as well as the robotics in libraries.

• Take care to prevent several systems from writing to the same device at the same time. Access to the devices needs to be synchronized between all systems. This is done using locking mechanisms.

• SAN technology provides an excellent way of managing library robotics from multiple systems. It creates the ability to manage the robotics directly, as long as the requests sent to the robotics are synchronized among all the systems involved.

Chapter 242

Page 73

Configuring and Using Backup Devices

Shared Devices in the SAN Environment

Figure 2-5 Multiple System to Multiple Device Connectivity in SAN

Chapter 2 43

Page 74

Configuring and Using Backup Devices

Shared Devices in the SAN Environment

FC-AL SAN and LIP

Using tape devices in Fibre Channel Arbitrated Loops (FC-AL) may cause certain anomalies that could abort a backup session. This problem arises because the FC-AL performs a Loop Initialization Protocol (LIP) whenever a new FC link is connected or disconnected, or whenever a system connected to the FC-AL is rebooted. This re-initialization of the FC-AL causes running backups to be aborted. Such terminated jobs should be restarted.

When a LIP occurs on the FC-AL Loop, any utility with an active I/O process shows an I/O error. For backup utilities attempting to use a shared tape, an I/O error causes failure of the current backup session, causing active tapes to be rewound and unloaded, and the backup session to abort.

To avoid these problems, take the following precautions:

• Do not add new devices or remove devices from the Arbitrated Loop while backup sessions are running.

• Do not touch FC components while backup sessions are running, the static charge can cause a LIP.

• Do not use discovery on Windows or ioscan on HP-UX system since these also cause a LIP.

Locking Devices Used Exclusively by Data Protector

If Data Protector is the only application that uses a drive, but that same drive needs to be used by several systems, Device Locking has to be used.

If Data Protector is the only application that uses a robotics control from several systems, Data Protector handles this internally, provided the library control is in the same cell as all the systems that need to control it. In such a case, all synchronization of access to the device is managed by Data Protector internal control.

Locking Devices Used by Multiple Applications

If Data Protector and at least one other application want to use the same device from several systems, the same (generic) device locking mechanism has to be used by each application. This mechanism needs to work across several applications. This mode is not currently supported by Data Protector. Should this be required, operational rules must ensure exclusive access to all devices from only one application at a time.

Chapter 244

Page 75

Configuring and Using Backup Devices

Shared Devices in the SAN Environment

Direct Library Access Concept

With direct library access, every system sends control commands directly to the library robotics. Therefore, a system does not depend on any other system in order to function.

With direct library access and multiple systems sending commands to the same library, the sequence of such communication has to be coordinated. Therefore, every library definition is associated by default with a host controlling the library robotics. If another host requests that a medium is moved, Data Protector will first access the system specified in the library definition for performing the media move. If the system is not available, direct access from the local host to the library robotics is used if the libtab file is set. All of this is done in a transparent manner within Data Protector.

Indirect Library Access Concept

With indirect library access, only one system (the default robotics control system) sends robotic control commands that are initiated from Data Protector. Any other system that requests a robotics function forwards the request to the robotics control system, which then sends the actual command to the robotics. This is the default setting, and is done in a transparent manner within Data Protector for all requests from Data Protector.

Configuration Overview

This section provides an overview of the steps involved in configuring your system.

• Configuration goals This section specifies the mixed SAN environment to be configured.

• Configuration methods This section outlines the configuration methods that need to be

performed for UNIX, Windows, and mixed SAN environments.

• Manually configuring the robotics This section describes how you can manually configure the library

robotics so that they can be used in a SAN environment.

• Manually configuring the devices

Chapter 2 45

Page 76

Configuring and Using Backup Devices

Shared Devices in the SAN Environment

This section describes the steps that need to be performed to configure the drives. It also explains when Lock Names and direct access should be used.

• Manually configuring the libtab file This section describes the purpose and usage of the libtab file.

Examples of libtab files are also provided.

• Simplified configuration using the SANconf tool This section refers to SANconf tool which simplifies configuration on

Windows, HP-UX, and Solaris system in SAN environment.

Configuration Goals

The SAN environment can range from one host using a library to several hosts using several libraries. The hosts can run on several operating systems platforms. In this example, the SAN environment is made up of Windows 2000, Windows NT, HP-UX, and Solaris systems as follows:

• one Windows NT,

• one Windows 2000,

• one HP-UX 11.11,

• one Solaris 8,

•one bridge,

• one switch,

• library with 4 DLT 7000 drives and 174 slots,

• default library robotics control, which is performed by the Windows NT system with the hostname dupin.

Chapter 246

Page 77

Figure 2-6 SAN Environment Configuration

Configuring and Using Backup Devices

Shared Devices in the SAN Environment

As the library is attached to several systems that can access its drives directly, you need to configure as many drives on each host as you want to use from that host. In this case, all 4 physical drives are to be used from each host.

From a Data Protector perspective, the goal is as follows.

• On each host that is to share the library robotics:

✓ Create a library robotics definition for each host. If there is only

one host that is controlling the robotics, the library definition is created only for the default robotics control host.

• On each host that is to participate in sharing the same (tape) drives in the library:

Chapter 2 47

Page 78

Configuring and Using Backup Devices

Shared Devices in the SAN Environment

✓ Create a device definition for each device to be used. ✓ Use a Lock Name if the (physical) device will be used by another

host as well (shared device).

✓ Optionally, select direct access if you want to use this

functionality. If you use it, ensure that the libtab file is set up on that host.

Configuration Methods

Two configuration methods that depend on the platforms that participate in the SAN configuration exist:

• If your environment consists only of Windows, HP-UX, and Solaris systems, use the simplified configuration. For more information, refer to “Simplified Configuration using the SANconf tool” on page 54.

• If your environment consists of other UNIX systems, use the manual configuration. For more information, refer to “Manually Configuring the Library Robotics” on page 48.

Manually Configuring the Library Robotics

You first need to configure the library robotics control on a host, which acts as the default robotics control system. This host will be used to manage media movements, regardless of which other host requests the media move.

This is done in order to prevent conflicts in the robotics if several hosts request a media move at the same time. Only if the hosts fail and direct access is enabled is the robotics control performed by the local host requesting the media move.

Prerequisites Before configuring Data Protector device sharing in a SAN environment,

the Data Protector Media Agent must be installed on each host that needs to communicate with the shared library. See the HP OpenView Storage Data Protector Installation and Licensing Guide for more information on installing a Media Agent.

Configuring the Library Robotics

To create the library itself, refer to “Configuring Library Devices” on page 26 or online Help topic “Creating Devices in a SAN Environment”. For the robotics control, you can use any host within the SAN; here the

Chapter 248

Page 79

Configuring and Using Backup Devices

Shared Devices in the SAN Environment

system dupin.company.com is used. The library robotics will be controlled by that host, unless the host is unavailable and direct access is enabled as explained in detail in “Enabling Direct Access” on page 51.

Configuring the Library Robotics in a Cluster

If you want the robotic control to be managed by a cluster, you need to make sure that:

• The robotics control exists on each cluster node.

• The virtual cluster name is used in the library robotics configuration.

• The common robotics and device filenames are installed either using the mksf command or using the libtab file.

After you have configured the library robotics, create the drives.

Manually Configuring the Devices (Drives)

You need to configure each device (tape drive) on each host from which you want to use the device.

Lock Names have to be used to prevent the same device from being used by several hosts at the same time. Optionally, the “direct access” mode can be selected.

Configuring Drives As will be seen shortly, it helps to follow a drive naming convention

similar to the following:

LibraryLogicalName_DriveIndex_Hostname, for example SAN_LIB_2_computer_1.

The drive naming convention shows its benefits during backup specification creation. Whenever you configure a backup on any host, all you have to do now is to use the drive that is configured on that host, since the drive includes the host name in its name.

Table 2-2 Device Locking for Drives

Environment Conditions Required Action

The drive is used by only one system and Data Protector only

Chapter 2 49

No locking is necessary, leave the fields blank, for example, Lock Name = blank

Page 80

Configuring and Using Backup Devices

Shared Devices in the SAN Environment

Table 2-2 Device Locking for Drives

Environment Conditions Required Action

Defining Lock Names

The drive is used by several systems (SAN), Data Protector is the only application accessing the drive

Use device locking (define a Lock Name) as described in Device Locking Names section

The drive is used by several systems and several applications (not only by Data Protector)

Use device locking (define a Lock Name) and ensure that operational rules provide exclusive access to all devices from only one application at a time

Using Lock Names is necessary in a SAN environment. This is the way to prevent collisions on the device caused by several systems talking to it at the same time. It is recommended that the following convention is used for Lock Names:

LibraryLogicalName_DdriveIndex, for example SAN_LIB_D1.

Chapter 250

Page 81

Figure 2-7 Setting Advanced Options

Configuring and Using Backup Devices

Shared Devices in the SAN Environment

When you are setting the locking name of a drive, use the same lock name for the same physical drive when using it in the device definition on another host.

Figure 2-8 Summary of Device Definitions Using Lock Names

Enabling Direct Access

The Direct Access mechanism always uses the default robotics control host first for media movements, but if this fails, Data Protector uses direct access, if enabled.

Chapter 2 51

Page 82

Configuring and Using Backup Devices

Shared Devices in the SAN Environment

To enable direct access, check the Use direct library access check box and configure the libtab file on every host on which you want to use direct access.

Figure 2-9 Selecting Direct Access

Manually Configuring the libtab Files

The purpose of the libtab files is to map the library robotic control access so that it also works on the “direct access requesting system”, since here the local control path is likely to be different from the one used on the default library robotic control system.

You need to create a libtab file for every Windows and UNIX system client host that needs “direct access” to the library robotic, and is not identical to the system configured as the default library robotics control system.

On each system requesting direct access, a plain text file with the following format must be provided:

• <FullyQualifiedHostname> is the name of the client host

Chapter 252

Page 83

Configuring and Using Backup Devices

Shared Devices in the SAN Environment

demanding direct access control for the library robotics. If the host is part of a cluster, the node name should be used.

• <DeviceFile | SCSIPath> is the control path to the library robotic driver on this client host.

• <DeviceName> is the name of the device definition used on this client host.

You need one line per device for which you request direct access. The libtab file is located on:

• <Data_Protector_home>\libtab on Windows systems

• /opt/omni/.libtab on HP-UX and Solaris systems

• /usr/omni/.libtab on other UNIX systems

Example files follow for all systems involved. Definitions are separated by lines, and empty lines are ignored. Since the default library robotics are defined on the host dupin.company.com, no libtab file is needed on this system.

TIP There can be only one libtab file that includes definitions for all

systems involved and is distributed to all such systems. In this case, when a specific system needs “direct access” to the library robotic, the definitions for other systems are ignored and only the definitions for the system are used.

Example libtab file on zala

Example of the libtab file on host zala.company.com (Windows): zala.company.com scsi:2:0:2:0 SAN_LIB_1_zala zala.company.com scsi:2:0:2:0 SAN_LIB_2_zala zala.company.com scsi:2:0:2:0 SAN_LIB_3_zala zala.company.com scsi:2:0:2:0 SAN_LIB_4_zala

Example libtab file on oda

Example of the libtab file on host oda.company.com (HP-UX): oda.company.com /dev/spt/lib SAN_LIB_1_computer_2 oda.company.com /dev/spt/lib SAN_LIB_2_computer_2 oda.company.com /dev/spt/lib SAN_LIB_3_computer_2

Chapter 2 53

Page 84

Configuring and Using Backup Devices

Shared Devices in the SAN Environment

oda.company.com /dev/spt/lib SAN_LIB_4_computer_2

Example libtab file on donat

NOTE If the host is part of a cluster, <FullyQualifiedHostname> must be the

Example of the libtab file on host donat.company.com (Solaris): donat.company.com /dev/rsst6 SAN_LIB_1_sample donat.company.com /dev/rsst6 SAN_LIB_2_sample donat.company.com /dev/rsst6 SAN_LIB_3_sample donat.company.com /dev/rsst6 SAN_LIB_4_sample

virtual host name, and <DeviceFile | SCSIPath> must refer to the local node.

Simplified Configuration using the SANconf tool

For the Windows, HP-UX, and Solaris environments, the configuration task is simplified significantly by using the SANconf tool via the command line.

The tool performs:

• configuration of the default robotic control host

• configuration of the devices (tape drives) on all hosts by simply providing a list of hosts. This includes configuration of Lock Names and libtab files.

For details about how to use the SANconf tool, refer to the SANconf tool Readme File, which can be found on the Data Protector Windows installation CD (\Product_Information\Whitepapers & Service Deployment\SANconf_tool_readme.pdf).

Shared Devices and MC/ServiceGuard

If you are using Data Protector with MC/ServiceGuard for clustering, you can implement the integration in a SAN environment. Since clustering is based on sharing resources such as network names, disks, and tapes among nodes, Fibre Channel and SAN are well suited as enabling technologies for storage device sharing. ATS (Advanced Tape

Chapter 254

Page 85

Configuring and Using Backup Devices

Shared Devices in the SAN Environment

Services) is an integrated part of HP MC/ServiceGuard 11.05 that manages tape resources and enables the use of Data Protector in a SAN environment.

This section explains how to create the necessary device files, how to configure the virtual host, how to configure static and floating drives, and how to use the Data Protector GUI to configure the integration for use in a SAN environment.

Configuration Basics

Nodes in a cluster can share SAN connected devices in order to perform a "LAN-free" backup of an application running in a cluster. Cluster-aware applications can, at any time, run on any node in a cluster since they run on the virtual host. In order to perform a LAN-free local backup of such an application, you need to configure the logical device with a virtual hostname instead of a real node name. You can configure as many logical devices for a single physical device as you need, but you have to use the same Lock Name for all devices.

In order to share a device among multiple systems, configure one logical device for each system on which you want to use the device locally.

NOTE Before the ATS component can be configured, the MC/ServiceGuard

configuration has to be completed and a cluster has to exist.

Refer to the following documents for detailed information:

• B3936-90032 Using Advanced Tape Services (MC/ServiceGuard documentation)

• B3935-90015 MC/ServiceGuard Version A.11.05 Release Notes

• B3936-90026 Managing MC/ServiceGuard, Sixth Edition

Creating the ATS Configuration Files

Run the stquerycl command to gather the configuration of all attached tape devices and robotic control. This will create the configuration file. The configuration file includes the following new device file names and a usage policy for all devices:

• dev/rmt/st#m

Chapter 2 55

Page 86

Configuring and Using Backup Devices

Shared Devices in the SAN Environment

for tape device files

• dev/rac/sac# for robotic control devices

The configuration files should be the same on all nodes for the same physical device. Both the robotics and drive files should be included.

Configuring Drives

Floating Drives Drives that should be accessible from both hosts, depending on which

host the package is running, have to be configured based on the virtual host.

Table 2-3 How to Configure a Floating Drive

Hostname node_Appl

Device Control Path /dev/rmt/st3m

Lock Name Libl_Drive_1

Static Drives The drives can still be used in the standard way using the static

hostname and the local device file. (You can use the local HP-UX or ATS device file.) The local drives should be configured on the node. For example:

Table 2-4 How to Configure a Static Drive

Hostname Host_A

Device Control Path /dev/rmt/0m

Lock Name Lib1_Drive_1

The previous examples for floating and static drives show the device identified by /dev/rmt/0m and /dev/rmt/st3m. Both device files refer to the same physical devices and therefore the lock name (Lib1_Drive_1) is identical.

Chapter 256

Page 87

Configuring and Using Backup Devices

Drive Cleaning

There are several methods for cleaning dirty drives:

• Library built-in cleaning mechanism Some tape libraries have a functionality for cleaning drives

automatically when a drive requests head cleaning. When the library detects a dirty drive, it automatically loads a cleaning tape, and Data Protector is not notified of this action. This interrupts any active session, causing it to fail. This specific hardware-managed cleaning procedure is not recommended, since it is not compatible with Data Protector. Use automatic drive cleaning managed by Data Protector instead.

• Automatic drive cleaning managed by Data Protector Data Protector provides automatic cleaning for most devices using

cleaning tapes. For SCSI-II libraries and magazine devices, you can define which slots contain cleaning tapes. A dirty drive sends the cleaning request, and Data Protector uses the cleaning tape to clean the drive. This method prevents failed sessions due to dirty drives, provided that suitable media are available for backup. Refer to “Configuring Automatic Drive Cleaning” on page 58.

• Manual cleaning If automatic drive cleaning is not configured, you need to clean the

dirty drive manually. If Data Protector detects a dirty drive, a cleaning request appears in the session monitor window. You then have to manually insert a cleaning tape into the drive.

A special tape-cleaning cartridge with slightly abrasive tape is used to clean the head. Once loaded, the drive recognizes this special tape cartridge and starts cleaning the head.

Limitations • Data Protector does not support the diagnostic vendor unique SCSI

command for performing drive cleaning with cleaning-tapes stored in one of the special cleaning tape storage slots. These special cleaning tape storage slots are not accessible using the normal SCSI commands, and therefore cannot be used with automatic drive cleaning managed by Data Protector. Configure the standard slot(s) to store cleaning tape(s).

Chapter 2 57

Page 88

Configuring and Using Backup Devices

Drive Cleaning

• Detection and use of cleaning tapes depends on the system platform where the Media Agent is running. See the HP OpenView Storage Data Protector Software Release Notes for further information.

• You should not use another kind of device management application if you configure automatic drive cleaning managed by Data Protector, as this may cause unexpected results. This is due to the “cleanme” request being cleared as it is read, depending on the specific device type and vendor.

• Automatic drive cleaning for logical libraries with a shared cleaning tape is not supported. Each logical library needs to have its specific cleaning tape configured.

Conditions for Automatic Cleaning

Automatic drive cleaning is supported for libraries with barcode support as well as for those without barcode support. The following conditions must be met for automatic cleaning:

• In a library without barcode support, a cleaning-tape slot has been configured in the Data Protector device definition and contains a cleaning-tape cartridge. The cleaning-tape slot must be configured together with the other library slots.

• In a library with barcode support, the cleaning tape has a barcode label with “CLN” as its prefix. Further, barcode support must be enabled. Refer to “Activating Barcode Support” on page 62.

• The configured drive has the Detect Dirty Drive option enabled.

When Data Protector receives notification that the drive needs cleaning, it automatically loads the cleaning tape, cleans the drive and then resumes the session. All cleaning activities are logged in the following file:

• on Windows: <Data_Protector_home>\log\cleaning.log

• on UNIX: /var/opt/omni/log/cleaning.log

Configuring Automatic Drive Cleaning

The configuration of automatic drive cleaning is performed in two steps:

1. Enable dirty drive detection. This needs to be done for all device types (standalone and libraries). This enables Data Protector to recognize the event issued by the drive.

Chapter 258

Page 89

Configuring and Using Backup Devices

Drive Cleaning

2. Configure a slot for the cleaning tape in the library or magazine device.

Enabling Dirty Drive Detection

Configuring a Slot for Cleaning Tape

To enable dirty drive detection, select the Detect dirty drive advanced option in the Settings property page for the drive. For detailed steps, refer to the online Help index keyword “configuring drive cleaning”.

To configure a slot for cleaning tape in a SCSI-II library, click the Cleaning Slot option and select an existing slot in the drop-down list in the Repository property page for the device. For detailed steps, refer to the online Help index keyword “configuring drive cleaning”.

Testing the Drive Cleaning Configuration

You can test if drive cleaning has been successfully configured.

Preparation 1. Log on to the system where the Media Agent for the drive is installed.

2. Change to the Data Protector tmp directory:

• on HP-UX and Solaris systems: /var/opt/omni/tmp/

• on other UNIX systems: /usr/omni/tmp/

• on Windows systems: <Data_Protector_home>\tmp\

• on Novell NetWare systems: \usr\omni\tmp\

3. Create an ASCII file named simtab on Windows systems or .simtab on UNIX systems with the following content:

Testing the Configuration

CLEANME <file_name> <drive_name>

Where <file_name> is the name of the file you will use to simulate a dirty drive, and <drive_name> is the name of the drive you want to test.

You can add multiple entries for various drives. Do not add any directories in front of the name of the file.

In order to test your configuration, do the following:

1. In the Data Protector tmp directory, create an empty file that will be used to simulate a dirty drive. Use the same name as in the simtab or .simtab file.

Chapter 2 59

Page 90

Configuring and Using Backup Devices

Drive Cleaning

2. Start a backup using the drive you are testing.

Data Protector behaves as though the selected drive were dirty and performs the cleaning action.

To stop simulating dirty drive behavior for the specific drive, delete the file used for simulation.

Chapter 260

Page 91

Configuring and Using Backup Devices

Busy Drive Handling

Data Protector expects drives to be empty, i.e., there should not be a medium in the drive unless a restore or backup is currently active. Several factors can cause a medium to still be in a drive, for instance, if the medium was used with a different application and not removed, or if the system writing the data to the tape (Media Agent) failed during the backup. The next backup using this drive has to deal with this situation. Data Protector can respond automatically in several ways. The response is configurable via the library option Busy Drive Handling. The following options are available:

Abort The backup will be aborted (default). Eject Data Protector will eject the medium from the drive

and put it in any empty slot.

Eject to mail slot Data Protector will eject the medium from the drive

and put it in the library mailslot (CAP).

If the backup continues automatically, select Eject. Because the tape is moved to an unknown slot, the library should be scanned before the next backup.

Chapter 2 61

Page 92

Configuring and Using Backup Devices

Activating Barcode Support

If a SCSI library device uses media with barcodes, Data Protector can use barcodes by providing the following barcode support:

• Recognition of cleaning tapes with a CLN prefix.

• Reference to media by their barcodes. Data Protector adds the media barcode to the Data Protector media label.

• Quickly scanning the media in the slots of the library repository using media barcodes. This is considerably faster than scanning a repository without the barcode functionality. In the Action menu, click Barcode Scan to scan the library repository for media.

Activate barcode support by selecting the Barcode reader support option from the Control property page of the device. Refer to Figure 2-10. For detailed steps, refer to the online Help index keyword “activating barcode reader support”.

NOTE All barcodes in a cell should be unique, regardless of the type of media or

the fact that there are multiple libraries.

Figure 2-10 Activating Barcode Reader Support

Chapter 262

Page 93

Configuring and Using Backup Devices

Activating Cartridge Memory Support

Cartridge memory support can be activated for drives with the LTO-Ultrium media type providing the following:

• Updating or changing media management information such as medium label, medium location and pool name, and media usage information such as date of last access, date of last write and number of writes.

• Importing of media that include information stored in Cartridge Memory.

• Listing all Cartridge Memory contents for the specific medium.

• Reformatting Cartridge Memory of a specific medium from GUI and CLI in cases where medium header information in Cartridge Memory is not synchronized with the medium header on the medium.

• Recognizing media used by other applications.

Limitation On Novell NetWare, Cartridge Memory operations on LTO devices are

not supported.

Activate Cartridge Memory support for a drive by setting the Advanced options from the Settings property page of the drive. Refer to Figure 2-11.

Chapter 2 63

Page 94

Configuring and Using Backup Devices

Activating Cartridge Memory Support

Figure 2-11 Cartridge Memory Support Activation for a Drive

Chapter 264

Page 95

Configuring and Using Backup Devices

Disabling a Backup Device

If you disable a backup device, all subsequent backups skip this device. The next available device defined in the list of devices for the backup specification is used, provided that load balancing has been selected. All devices using the same lock name as the disabled device are also disabled.

This lets you avoid backups that fail due to a device needing service, while keeping other devices available (and configured) for backup.

Disabling a backup device is useful when the device is damaged or in maintenance mode.

How to Disable a Device?

How to Restart the Device?

Figure 2-12 Disable Device

Disable a backup device by selecting the Disable device option in the Settings property page of your device or drive. Refer to Figure 2-12. For

detailed steps, refer to the online Help index keyword “disabling backup devices”.

To resume using the device for backups, you need to deselect this option.

Chapter 2 65

Page 96

Configuring and Using Backup Devices

Removing a Backup Device

By removing a backup device from the Data Protector configuration, you stop using this device for backup or restore. Make sure that you remove the device from all backup specifications that use the device. Otherwise the backup or restore will fail.

TIP Also, if you are not using a certain backup device with Data Protector

anymore, you may want to delete the Data Protector Media Agent software from the system. This can be done using the Client context.

How to Remove a Backup Device?

To remove a backup device, delete it from the Devices & Media context. For detailed steps, refer to the online Help index keyword “deleting backup devices”.

Chapter 266

Page 97

Configuring and Using Backup Devices

Renaming a Backup Device

When you rename a backup device, the device is no longer used under its old name for backup or restore.

IMPORTANT Make sure that you remove the device's old name from all backup

specifications that use the device. Otherwise, Data Protector tries to back up to or restore from a device that does not exist, and the session fails.

How to Rename a Backup Device?

Rename a backup device in the General property page of the device. For detailed steps, refer to the online Help index keyword “renaming backup devices”.

Chapter 2 67

Page 98

Configuring and Using Backup Devices

Device Locking

Internal Locking The internal locking of backup devices prevents two Data Protector

sessions from accessing the same physical device at the same time. For example, if one backup session is using a particular device, all other backup/restore sessions must wait for this device to become free before starting to use it. When a backup or restore session starts, the Data Protector locks the device, the drive, and the slot used for that session.

Media sessions performing media operations such as initialization, scanning, verifying, copying, or importing also lock devices. During that time, no other operations can lock and use the device. If a media session cannot obtain a lock, the operation fails, and you have to retry the operation at a later time.

Locking when a Mount Request is issued

Locking with Data Protector

During a mount request of a backup or restore session, Data Protector allows the device to be used for media management operations, such as formatting a new medium.

When the mount request is confirmed, the backup or restore session locks the device again and continues with the session.

You can configure the same physical device many times with different characteristics, simply by configuring devices with different device names.

Since the internal locking operates on logical devices rather than on physical devices, a collision can occur, if you specify one device name in one backup specification and another device name for the same physical device in another backup specification. Depending on the backup schedule, this may result in Data Protector trying to use the same physical device in several backup sessions at the same time. This can also happen when two device names are used in other operations such as backup and restore, backup and scan, and so on.

To prevent this collision, you can specify a virtual lock name in both device configurations. Data Protector then uses this lock name to check if the device is available, thus preventing collisions.

If you configure two Data Protector backup devices that actually point to the same physical device, you are advised to specify the Lock Name in the advanced options for the two logical devices. Both logical devices need to

Chapter 268

Page 99

Configuring and Using Backup Devices

Device Locking

have the same lock name. Lock Name is the name that Data Protector recognizes in order to lock the device before starting backup and restore sessions. Refer to the “Shared Devices in the SAN Environment” on page 42 for example on how to use Lock Name.

How to Lock a Device?

Lock a backup device by selecting the Use Lock Name advanced option from the Settings property page for the device, and then entering the lock name of your choice. For detailed steps, refer to the online Help index keyword “locking backup devices”.

Chapter 2 69

Page 100

Configuring and Using Backup Devices

Device Concurrency, Segment and Block Size

Streaming To maximize a device’s performance, it has to be kept streaming. A device

is streaming if it can feed enough data to the medium to keep it moving forward continuously. Otherwise, the tape has to be stopped, the device waits for more data, reverses the tape a little and resumes writing to the tape, and so on. In other words, if the data rate written to the tape is less than or equal to the data rate which can be delivered to the device by the computer system, then the device is streaming. Device streaming is also dependent on other factors such as network load and the block size of the data written to the backup device in one operation.

For additional information on device concurrency, segment and block sizes, see the Media Management chapter in the HP OpenView Storage Data Protector Concepts Guide.

Changing Concurrency

Data Protector provides a default number of Disk Agents that are started for each device. Increasing the number of Disk Agents sending data to a Media Agent at the same time improves device streaming.

In the Advanced Options dialog box of a specific device, set the Concurrency to the maximum number of Disk Agents allowed to feed data to each Media Agent. See Figure 2-13 on page 71. For detailed steps, refer to the online Help index keyword “concurrency”.

Concurrency can also be set in the backup specification. The concurrency set in the backup specification will take precedence over the concurrency set in the device definition. See Figure 2-14 on page 72. For detailed steps, refer to the online Help index keyword “concurrency”.

Chapter 270