upload

HP OpenView OmniBack IIAdministrator ’s Guide

HP Part No. B1957-90036October 1997

ii

�� Hewlett-Packard makes no warranty of any kind with regard to this material,and specifically disclaims the implied warranties of merchantability andfitness for a particular purpose. Hewlett-Packard shall not be liable for errorscontained herein or for any damages, whether direct, indirect consequential,incidental, or special, in connection with the furnishing, performance, or useof this material

The specific warranty information for the product as to which this materialrelated is available in Hewlett-Packard’s purchasing and licensing terms andconditions.

© Copyright 1997 Hewlett-Packard Company

All rights are reserved. No part of this document may be photocopiedreproduced, or translated to another language without the prior writtenconsent of Hewlett-Packard Company. The information contained in thisdocument is subject to change without notice.

�� Use, duplication, or disclosure by the Government is subject to restrictions asset forth in subparagraph (c)(1)(ii) of the Rights in Technical Data andComputer Software clause in DFARS 252.227-7013. Rights for non-DODU.S. Government Departments and Agencies are as set forth in FAR 52.227-19(c)(1,2).

OSF/Motif is a trademark of the Open Software Foundation in the U.S. andother countries.

HP-UX 9.x and 10.x for HP 9000 Series 700 and 800 computers are X/OpenCompany UNIX 93 branded products.

X/Open is a registered trademark, and the X device is a trademark of X/OpenCompany Ltd. in the UK and other countries.

UNIX® is a registered trademark in the U.S.A. and other countries, licensedexclusively through X/Open Company Limited..

DOS, Windows, Windows for Workgroups, Windows 95, and Windows NTare registered trademarks of Microsoft Corporation.

IRIX is a registered trademark of Silicon Graphics, Inc.

iFOR/LS is a trademark and Gradient is a registered trademark of GradientTechnologies, Inc.

iii

��! �"��!#%$ ��&

Conventions

To make the information easier to understand, this manual uses varioustypographic conventions within the text. The following list explains theseconventions:

Computer Font Computer font is used for the following:

• Directories and names:/opt/omni/bin

• Screen prompts: Select (highlight) the devicewith the Mount Request status.

• Messages displayed by the system: Thesession isPending then finallyRunning.

• What you type, for example:Home_Directory

Bold Bold face is used for command names, and thenames of windows and fields:

• Select Object → Add → Filesystem

• ..theOmniBack II Editor window appears

• ..in theMountpoint field

OK References to buttons on the display look likethis:

• Click on theHelp button

• Click on theOptions button

iv

' �)(+*�$ &-,.��/

In This Book

HP OpenView OmniBack II Administrator’s Guide describes features andfunctions of the HP OmniBack II network backup product.

Target AudienceThis manual is intended for administrators who are responsible for theplanning, setup, and maintenance of the network backup.

The manual is organized as follows:

Chapter 1 Introducing HP OpenView OmniBack II

Chapter 2 Installation Overview

Chapter 3 Configuring a Cell

Chapter 4 Backing Up Your System

Chapter 5 Restoring data.

Chapter 6 Monitoring sessions

Chapter 7 Advanced tasks and concepts.

Chapter 8 Maintaining the OmniBack II Database.

Chapter 9 Using Complex Devices and Autochangers.

Chapter 10 Troubleshooting information.

Glossary Definitions of terms related to the product.

Contents

i

1. Intr oducing HP OpenView OmniBack II

OmniBack II Architecture..........................................................................1-3

OmniBack II Components......................................................................1-4How a Backup Session Works................................................................1-5How a Restore Session Works................................................................1-6

Using the User Interfaces...........................................................................1-8

Graphical User Interface.........................................................................1-8OmniBack II Online Help.......................................................................1-9The Command Line Interface...............................................................1-11

2. Installation Overview

Distributing HP OmniBack II to Clients....................................................2-4

Importing and Exporting Hosts..................................................................2-6

Importing Hosts to a Cell........................................................................2-6Importing Hosts with Multi-LAN Cards................................................2-8Exporting Hosts from a Cell...................................................................2-8

Updating OmniBack II Clients................................................................2-10

To Update OmniBack II Clients...........................................................2-10

Deinstalling OmniBack II from a Host....................................................2-11

To Deinstall OmniBack II Modules......................................................2-11

3. Configuring a Cell

ii

Contents

Planning the Cells.......................................................................................3-3

Planning Your Backup Strategy..................................................................3-5

Choosing the Type of Backup.................................................................3-5Choosing the Mode of Backup................................................................3-6Deciding What to Back up......................................................................3-9Choosing a Backup Schedule................................................................3-10Protection...............................................................................................3-10Planning Cell Access and Security........................................................3-11Using Data Compression.......................................................................3-13Using Data Encryption..........................................................................3-13

Media Management..................................................................................3-14

The Media Pool Approach....................................................................3-14Pool Attributes.......................................................................................3-15Managing Media Compatibility............................................................3-18Media Identification..............................................................................3-20

Configuring and Using Logical Devices...................................................3-21

The Concept of Logical Devices...........................................................3-21Device Locking While in Use...............................................................3-23Configuring Logical Devices.................................................................3-23Configuring Typical Devices.................................................................3-25

Media Management Tasks........................................................................3-27

Creating a Media Pool...........................................................................3-28Adding Media to a Pool.........................................................................3-28Verifying a Medium...............................................................................3-29Erasing a Medium.................................................................................3-29Modifying a Medium.............................................................................3-30

Contents

iii

Viewing Information About a Medium................................................3-30Moving a Medium................................................................................3-31Recycling Media/Removing Protection................................................3-32Exporting a Medium.............................................................................3-32Importing a Medium.............................................................................3-33Scanning Media....................................................................................3-34Modifying Device and Media Management View................................3-35

Configuring User Classes and Users........................................................3-36

Configuring User Classes.....................................................................3-38Configuring Users.................................................................................3-41

4. Backing Up Your System

Understanding Datalists and Barlists.........................................................4-3

What is a Datalist?..................................................................................4-3What is a Barlist?....................................................................................4-4Generating Datalists................................................................................4-5Creating Datalists....................................................................................4-6Modifying a Datalist...............................................................................4-7

Configuring a Filesystem Backup..............................................................4-8

Selecting a Filesystem to Back up..........................................................4-8Selecting the Filesystem Backup Options............................................4-11

Configuring a Rawdisk Backup...............................................................4-13

Selecting Rawdisk Sections for Backup...............................................4-14Selecting the Rawdisk Backup Options................................................4-15

Configuring Host Backup........................................................................4-17

iv

Contents

Selecting a Host to Back up..................................................................4-18

Running Interactive Backups....................................................................4-20

Starting a Backup of an Existing Datalist.............................................4-20Status Messages.....................................................................................4-22Creating a Temporary Datalist...............................................................4-23Previewing Your Backup.......................................................................4-24Starting Your Backup............................................................................4-24

Using Backup Options..............................................................................4-26

Description of Backup Options.............................................................4-29Device Options......................................................................................4-33Transferring Backup Ownership...........................................................4-34

Load Balancing.........................................................................................4-36

Configuring Backup with Load Balancing............................................4-37

Reconnect of Broken Connections...........................................................4-40

Modifying Reconnect Parameters.........................................................4-40

Setting Up Scheduled Backups.................................................................4-41

Setting up Backup Schedules................................................................4-42Skipping Backups During Holidays......................................................4-47Overriding Scheduled Backup Options.................................................4-48

5. Restoring Data

Restore Overview......................................................................................5-3

Restoring Files from a Filesystem Backup.................................................5-4

Contents

v

Changing the View of Backup Objects...................................................5-4Selecting the Backup Object...................................................................5-5Selecting the Files to Restore.................................................................5-6Selecting a File/Directory Version..........................................................5-8Specifying Fileset Restore Options........................................................5-9Activating and Monitoring the Restore................................................5-15Searching for a Specific File.................................................................5-18Parallel Restore.....................................................................................5-18

Restoring a Rawdisk Section (Logical Volume)......................................5-20

Choosing the Rawdisk Section to Restore............................................5-20Specifying Rawdisk Restore Options...................................................5-21Starting and Monitoring a Rawdisk Restore.........................................5-22Responding to Mount Requests............................................................5-23

Restoring Files from a Rawdisk Backup.................................................5-24

Selecting the File from a Rawdisk to Restore......................................5-24Specifying Rawdisk Restore Options...................................................5-26Starting and Monitoring File Restore from a Rawdisk.........................5-27Restoring a File When You do not Know the Filename.......................5-28

6. Monitoring Sessions

Monitoring Running Sessions....................................................................6-3

Viewing Details of a Currently Running Session...................................6-3

Viewing Previous Sessions........................................................................6-5

Viewing Details of Previous Sessions....................................................6-6

Monitoring Several Cells...........................................................................6-7

vi

Contents

7. OmniBack II Advanced Tasks and Concepts

Automating Mount Prompt Handling.........................................................7-3

Mount Prompt Script Examples..............................................................7-4

Using Pre- and Post- Exec Commands.......................................................7-6

Configuring Pre/Post-Exec Commands for a Datalist/Barlist.................7-6Pre- and Post- Exec Commands for a Datalist/Barlist............................7-7Pre- and Post-Exec Commands for an Object.......................................7-11

OmniBack II Global Options File.............................................................7-13

Managing Failed Backups........................................................................7-14

Retry Host Backup Procedure...............................................................7-14Failed Host Backup...............................................................................7-15Restarting Failed Backup Objects.........................................................7-15

Detection of CDF Files.............................................................................7-18

OmniBack II and Veritas File Systems (VxFS) on HP-UX 10.x..............7-19

Concepts................................................................................................7-19Improved Backup Performance.............................................................7-20Limitations.............................................................................................7-20Restoring...............................................................................................7-21Script Templates....................................................................................7-21

OmniBack II and HP Enterprise File System on HP-UX 10.x.................7-23

Deleting a Session.....................................................................................7-24

Copying Media.........................................................................................7-25

Contents

vii

Modifying Device and Media Management View...................................7-28

Disaster Recovery....................................................................................7-29

Improved Disaster Recovery................................................................7-29Preparing For a Disaster.......................................................................7-30Recovering a Client Host......................................................................7-30Recovering a Cell Server......................................................................7-31Example of Mission Critical System Recovery....................................7-32

Moving a Cell Server...............................................................................7-36

Moving a Cell Server............................................................................7-36

MC/ServiceGuard and OmniBack II.......................................................7-38

Functionality and Behavior...................................................................7-38Prerequisites for Configuration.............................................................7-39Configuring Primary and Secondary Cell Servers................................7-39Configuring the Cell Server Package....................................................7-40Starting the Cell Server.........................................................................7-41Backing up a Secondary Cell Server System.......................................7-41

OmniBack II Web Based Reporting.........................................................7-42

Integrating OmniBack II Reporting with Netscape Fasttrack Server...7-43Using Provided Reporting Scripts........................................................7-43

Customizing the Encryption Algorithm...................................................7-45

Creating an Encryption Code Module..................................................7-45

Customizing the Compression Algorithm...............................................7-50

Creating a Compression Code Module.................................................7-51

viii

Contents

8. Maintaining the OmniBack II Database

Installing and Configuring the Database.....................................................8-3

Managing the Growth of the Database.......................................................8-4

Managing the Growth of the Database....................................................8-4Purging Obsolete Data from the Database..............................................8-7Shrinking the Size of the Database File..................................................8-9Enlarging the Size of the Database........................................................8-10

Backing Up the Database..........................................................................8-12

Backing up the Database Using a Datalist............................................8-13

Restoring the Database.............................................................................8-14

Recovering the Database.......................................................................8-15

Moving the Database to Another Host.....................................................8-17

9. Using Complex Devices and Libraries

Managing Complex Devices with OmniBack II........................................9-3

Complex Device Types............................................................................9-3How OmniBack II Functions with Complex Devices.............................9-4

Configuring a SCSI-II Library....................................................................9-7

Example of a Library Configuration.......................................................9-8

Configuring a Non-Standard Library for Use with OmniBack II.............9-12

How OmniBack II works with non-standard libraries..........................9-12Device Configuration............................................................................9-13

Contents

ix

10. Troubleshooting

Common GUI Errors and Warnings........................................................10-3

Common Message Screen Errors and Warnings.....................................10-8

Less Common Warning and Error Messages........................................10-16

x

Contents

1-1

1

Introducing HP OpenView OmniBack II

1-2

0 1325476�8�9�: ; 1�<>=�?A@CB�D�1�E�; D�FG@IH-1�; JLK�: MI0 0

In This Chapter

HP OpenView OmniBack II is the next generation of the OmniBack familyof backup and restore utilities. It expands the functionality of OmniBack andOmniBack/Turbo by adding powerful new features that allow you to easilymanage large networks. These new features include a comprehensive newmedia management system that tracks not only your backup media but alsothe data contained on those media. The flexibility provided by OmniBack IIenables you to develop customized backup policies while managing from acentral point backup operations for each part of your organization. Thisallows you to create a backup solution that best fits the needs of yourorganization.

OmniBack II also enables the administrator to create a true "lights-out"environment by automating the backup process using media management,logical devices, and pre/post-processing functionality.

Lost or corrupted files create critical downtime until the files can be locatedand restored. OmniBack II includes a powerful media management featurethat helps you quickly locate and restore lost files or directories, and guidesyou through the process.

1-3

0 1�25476�8�9�: ; 1�<-=.?N@IB�D�1�E�; D3FG@IH-1�; J�K�: MI0 0OCPQ��$ ,�R�S�/ ' '�T.U S�*�$ #V"�S�#%W U "

OmniBack II Architecture

HP OpenView OmniBack II provides a reliable, flexible solution for yourbackup needs by introducing the concept ofCells. Cells allow you to divideyour network into independent logical units that correspond to differentbackup strategies. OmniBack II lets you manage these cells from a centralpoint and initiate backup, restore, and monitor actions on any cell in yournetwork. This flexibility provides a scalable backup solution that grows asyour network grows. OmniBack II allows you to have many cells in thenetwork, and each of these cells operates as an independent part of theenterprise network. Each cell is installed and configured separately. How thecells are configured determines how backups are handled, which devices areused, and so forth. Dividing the network into separate cells gives networkadministrators greater flexibility in developing a backup policy for eachentity of their organization.

A cell consists of a set of hosts: aCell Server andClients. A host can onlybelong to one cell. The Cell Server is the main system in the cell and runsthe core OmniBack II software and also contains the OmniBack II database.A client can be any host with the supported architecture. Essentially, a clientcan be a host being backed up, a host with a backup device to which thebackup data is stored, or both. The role of the client depends on the softwareinstalled. SeeHP OpenView OmniBack II Installation Guide and“Distributing HP OmniBack II to Clients” on page2-4 for installationinstructions.

OmniBack II has a media management system which allows you to track thebackup media and the data contained on those media. The termmedia refersto the physical media on which the backed-up files are stored. Media exist inseveral forms:tape refers to DDS (Digital Audio Tape) or similar magnetictape;disk refers to a hard disk or rewritable optical disk.

1-4

0 1325476�8�9�: ; 1�<>=�?A@CB�D�1�E�; D�FG@IH-1�; JLK�: MI0 0OIPQ��$ ,�R�S�/ ' '�T�U S�*�$ #V"�S�#%W U "

OmniBack II Components

OmniBack II consists of three basic components - User Interfaces, CellServer software, and Disk and Media Agents. Each of these components canrun on a different host in the cell. Figure 1-1 shows this hierarchicalarchitecture.

On the first level, OmniBack II has two types of user interfaces, a GraphicalUser Interface (GUI) designed for simplicity of use and the Command LineInterface (CLI), designed for efficient use in scripts for experienced UNIXadministrators.

Figure 1-1 HP OmniBack II Components

The second level is the Cell Server software, which runs on the Cell Serverhost. When a command is entered on any host in the cell (using the GUI orcommand-line), the following actions occur:

1. A connection (local or remote) to the Cell Server is established.2. The Cell Server determines the type of command (backup, restore, or

status).3. The Cell Server starts the Session Manager (SM) needed to execute the

command.4. As the session progresses, the Session Manager writes information to the

OmniBack II database about the session and the data stored to the media

Disk Agent

Cell Server Software

User Interface

Data Flow

Commands Visual Cues

Con

trols

Media Agent

Controls

Stat

us C

ontro

ls Status Controls

1-5


during backup.

The third level is the Client component which runs on the individual host.The Session Manager (started in the second level) is responsible formanaging the clients needed to execute the command. To perform a backupor restore, the Session Manager determines which devices are needed andhow these will be used. Next, it starts the processes needed to control thesedevices. These processes are called Agents, and are either a Disk Agent(DA) or a Media Agent (MA). The Disk Agent reads and writes data to adisk. The Media Agent reads from and writes to a backup medium. Figure 1-2 shows how these agents operate during a backup or restore.

Figure 1-2 The Role of Disk Agents and Media Agents

How a Backup Session Works

A backup session starts when a backup request is initiated. During thissession, OmniBack II performs a backup of requested files and disks to thespecified media.

1. When the user initiates the backup, the Cell Server determines the type ofsession that has been requested (backup) and starts the appropriateSession Manager.

2. The Session Manager reads the specified datalist and determines whatneeds to be backed up and which devices will be used.

3. The Session Manager then determines how many Media Agents are

Disk

Disk Agent Media Agent

Media

Backup Process

Disk

Media Agent Disk Agent

Media

Restore Process

1-6

0 1325476�8�9�: ; 1�<>=�?A@CB�D�1�E�; D�FG@IH-1�; JLK�: MI0 0OIPQ��$ ,�R�S�/ ' '�T�U S�*�$ #V"�S�#%W U "

needed and starts the Media Agents and the Disk Agents needed for theseMedia Agents. For example, a Media Agent is started for each media(tape) drive that will be used and a Disk Agent is started for each disk thatwill be read.

4. The Monitor window is displayed. This window lets you respond tomount prompts and view the progress of a backup session.

5. The Disk Agents and the Media Agent determine whether a local orremote transfer is needed, and the Disk Agents start sending data to theMedia Agent.

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

7. As each block of data is written to the media, the Media Agent sendsinformation to the Session Manager about what was backed up. TheSession Manager uses this information to update the catalog of backed-upfiles in the OmniBack II database.

How a Restore Session Works

A restore session starts when a restore request is initiated. During thissession, OmniBack II performs a restore of requested files and disks fromthe media.

1. When the user initiates the restore, the Cell Server determines the type ofsession that has been requested (restore), and starts the appropriateSession Manager.

2. The Session Manager then determines which filesystems or directorieswill be restored, which devices will be used, and what restore optionshave been specified.

3. The Session Manager starts the necessary Disk Agent and Media Agent.For example, a Media Agent is started for the media (tape) drive that willbe used and a Disk Agent is started for the disk where the data will berestored.

4. The Monitor window is displayed. This window lets you respond to

1-7


mount prompts and view the progress of a restore session.

5. The Disk Agent and the Media Agent determine whether a local or remotetransfer is needed and the Media Agent starts sending data to the DiskAgent.

6. The Session Manager then updates the OmniBack II database and theDisk Agent writes the data to the disk.

1-8

0 1325476�8�9�: ; 1�<>=�?A@CB�D�1�E�; D�FG@IH-1�; JLK�: MI0 0X &�$ ��Y)#V*�" X &�" UL' �!#V" U�Z R�S�"�&

Using the User Interfaces

There are two user interfaces to OmniBack II: a Graphical User Interface(GUI) and a command-line interface. Both can be accessed on the CellConsole hosts, from where you can perform all OmniBack II tasks.

Figure 1-3 HP OmniBack II Main Menu (xomni)

Graphical User Interface

The Graphical User Interface uses colors and graphics to provide visual cuesto using OmniBack II features and functionality. It guides you through allthe administrative, backup, monitor, and restore tasks.

The GUI uses X11/Motif features such as buttons and list boxes to enhanceits usability. Whenever possible, list boxes are provided to allow you toselect from a list instead of typing in your selection. In addition, acomprehensive online help system provides information about each windowand each task.

When in Monitor mode, the OmniBack II GUI uses color to alert you tochanges in the status of backup and restore sessions. You can monitor allsessions in your cell or focus on a specific session.

The following naming convention is used to identify commands for the GUIinterface and the command-line interface: commands for the GUI start witha wordxomni followed by a word representing the function. For example,the commandxomnirestore starts the GUI for restore tasks only.

1-9

0 1�25476�8�9�: ; 1�<-=.?N@IB�D�1�E�; D3FG@IH-1�; J�K�: MI0 0X &�$ ��Y)#V*�" X &�" UL' �!#V" U�Z R�S�"�&

To use the Graphical User Interface of OmniBack II, enter:

xomni to start the GUI for the complete OmniBack IIfunctionality

xomniadmin to start the GUI for admin (configuration)

xomnibackup to start the GUI for backup

xomnicellmon to start the GUI for monitoring multiple cells

xomnimonitor to start the GUI for monitoring a single cell

xomnirestore to start the GUI for restore

The /usr/lib/X11/app-defaults/xomni command defines theappearance of the Graphical User Interface and can be modified if desired.

OmniBack II Online Help

Information about OmniBack II is available from two sources: this manualand the online help system. This manual contains the information you needto plan and administer your OmniBack II network, and some morecommonly used tasks. The online help system contains the information youneed to perform all available tasks.

The online help system provides four types of help:

On Help Provides help on using the OmniBack II help system.

On Window Displays information on the purpose of each window andhow the fields of that window are used. Help on Windowis available for each window. Included is information onthe menu items, fields, and buttons of the window.

On Tasks Displays information for performing specific tasks, suchas scheduling a backup.

On Version Displays version and copyright information forOmniBack II

You access the online help by either using theHelp pull-down menu or theHelp buttons provided on OmniBack II windows.

1-10


Figure 1-4 OmniBack II Online Help

Within the help text are hyperlinks (cross-references) to related informationand definitions. These hyperlinks help you navigate through the online help.You click the hyperlinked word or phrase to "jump" to the new topic.Hyperlinked words and phrases are marked with either solid or brokenunderlining.

1-11

0 1�25476�8�9�: ; 1�<-=.?N@IB�D�1�E�; D3FG@IH-1�; J�K�: MI0 0X &�$ ��Y)#V*�" X &�" UL' �!#V" U�Z R�S�"�&

The Command Line Interface

The command line interface follows the standard UNIX format forcommands and options and provides complete OmniBack II functionality.You can use these commands in scripts to speed up your commonlyperformed tasks.

This list provides a short description of each OmniBack II command. Formore details refer to the appropriate manpage for the command.

omniabort Aborts a specified active backup or restore session.

omnib Performs a backup of a specified datalist. All backupoptions are supported.

omnicc Checks and displays licensing summary for the cell.

omnicellinfo Displays configuration information of an OmniBack IIcell backup objects, media pools, devices, hosts, and thedatabase.

omnicp Copies data from one OmniBack II medium to another.No information about the copy is recorded in theOmniBack II database

omnicreatedl Automatically creates a datalist for the cell or the localhost.

omnidb Queries the OmniBack II database for information onbackups and restores performed.

omnidbcheck Checks the consistency of the OmniBack II database. Theinformation about the copy is recorded in the OmniBackII database.

omnidbinit Initializes the OmniBack II database. All information onprevious backup and restores sessions is lost.

omnidbutil A set of OmniBack II database configuration tools, suchas extending the database size, write and write thedatabase to/from an ASCII file, and so forth.

omnimcopy Creates a copy of an OmniBack II medium.

1-12


omniminit Initializes a medium. The medium is assigned to anOmniBack II media pool and added to the database.

omnimlist Displays the content of an OmniBack II medium. It scansthe catalog of the medium and shows all objects andsessions on the medium.

omnimm Manages media and media pools, checks the protection ofa medium, maintains the contents of the repository of anlibrary device.

omnimnt Confirms or cancels the mount prompt request issued by alogical device where no media is available for backup.Once you have put the requested medium in the device,you can confirm the mount request.

omnimver Verifies the data on an OmniBack II medium. It reads thedata and checks for correct format. Optionally, CRCchecking of each block can be specified.

omnir Performs a restore of OmniBack II backup. You canrestore any objects from the OmniBack II backup.

omnistat Displays the status of an active backup or restore session.You can display the status of all active sessions or just onespecified session.

omnisv.sh Starts, stops, or displays the status of OmniBack IIprocesses.

omnitrig Triggers scheduled backups. This command is normallyexecuted in thecron script.

omnidownload Displays the configuration of a device as recorded in theOmniBack II database. Use this command to display theconfiguration or to create an ASCII file containing thedevice configuration description, which can then bemodified andomniuploaded to the database.

omniupload Uploads the device configuration from a file. Use thiscommand to configure a new device or to change theconfiguration of an existing device by using theomnidownload command first.

2-1

2

Installation Overview

2-2

0 1�[25K�\ \ K�25; 6�1-@^]�D�4 ]�; D3F

In This Chapter

OmniBack II introduces the concept ofcells. By dividing a network intocells representing the entities of an organization, the network administratorcan define a unique backup strategy for an organizational entity. How youorganize your network determines the backup efficiency of your cell. Eachcell is installed and configured separately.

Figure 2-1 OmniBack II - Cell Administrator

Installing OmniBack II consists of the following tasks:

• Planning the cells. See Chapter 3, “Configuring a Cell,” on page3-1 formore information.

• Installing the OmniBack II software package on the Cell Server. SeeHPOpenView OmniBack II Installation Guide for more information.

• Distributing the OmniBack II modules to the clients in the cell. See

2-3

0 1�[25K�\ \ K32_; 6�1>@L]�D�4 ]�; D�F

“Distributing HP OmniBack II to Clients” on page2-4 for moreinformation.

• Configuring the devices, users, and media for the cell. See the appropriatesections in Chapter 3, “Configuring a Cell,” on page3-1 for moreinformation.

2-4

0 1�[25K�\ \ K�25; 6�1-@^]�D�4 ]�; D3F` $ &3# U $ a�W!#V$ ��YQb�cAOIPQ��$ ,�R�S�/ ' ' #V�Q��d $ "��!#%&

Distributing HP OmniBack II to Clients

Once you have installed the complete OmniBack II software on the CellServer, you must distribute the appropriate OmniBack II software modulesto all client hosts in the cell using the GUI. The function of a host isdetermined by the software modules you install. The following list showsthese modules:

User Interface The user interface for OmniBack II. It must be installedon all hosts from which you want to control OmniBack II.

Disk Agent Agent that reads and writes from a disk containing data. Itmust be installed on all hosts which you want to back up.

Media Agent Agent that reads and writes from a device containing abackup medium. It must be installed on all hosts wherethe backup devices are configured.

To simplify installation, your installation plans should include a list of hosts,grouped by modules to be installed. For example, hosts 1,2, and 3 have theMedia Agent module, hosts 4,5, and 6 have the Media Agent and the DiskAgent. You install hosts 1,2, and 3 as one group, and hosts 4,5, and 6 asanother.

e O ( f gTo perform the installation, you will need eitherroot or admin access or anaccount withroot or admin capabilities access for every host on which you wantto install HP OmniBack II modules.

1. In theOmniBack II Main menu, selectInstall to open theOmniBackII - Cell Administration window.

2. SelectEdit →Install hosts... to open theCellAdministration - Install window.

2-5

0 1�[25K�\ \ K32_; 6�1>@L]�D�4 ]�; D�F` $ &3# U $ a�W!#V$ ��YQb�cAOIPQ��$ ,�R�S�/ ' ' #V�Q��d $ "��!#%&

3. Select theAdd... button to open theInstall - Load Hosts window.

TheDomain field of the window shows the IP address for your cell. Tochange this IP address, click the field with the address and enter the newIP address.

You can select hosts by typing their names in theFilter field andselectingAdd. Short and long hostnames can be used. You can also usewildcards to select several hosts at once.

You can select hosts by their names or their IP addresses by entering theexact host IP address or a range of addresses to add several hosts at once.

4. When you have specified all hosts that will have the same modules, closethe Install- Load Hosts window and return to theCellAdministration - Install window. The hosts you specified nowappear in theInstallation Target Hosts field.

5. Select which OmniBack II modules you want to install on selected hosts.

6. To confirm this host configuration, click theOK button. Followinstructions and messages in theHP OmniBack II - InstallTerminal window.

2-6

0 1�[25K�\ \ K�25; 6�1-@^]�D�4 ]�; D3F' PQh�� U #V$ ��YQR��iQfkj�h�� U #%$ ��YQb.��&�#%&

Importing and Exporting Hosts

When you distribute software from the Cell Server to other hosts, they areautomatically added to the cell. If you need to modify your cellconfiguration, move the host from one cell to another, or perform similartasks without removing the OmniBack II software from the host, you canexport and import hosts.

The manual importing and exporting of a host is useful, for example, whenyou want to do one of the following:

• An emergency fix for problems caused by insufficient licenses. Byexporting a host from the cell, its license becomes available to some otherhost. This is, however, only a temporary solution until you order and getmore licenses.

• Add a pre-installed host to the cell.• Move the host from one cell to another. You do not need to de-install

software from the host before moving it to another cell.• Remove from the configuration any hosts which are no longer a part of the

network.• Needed to integrate Novell, Windows NT, and Windows 95 clients. See

HP OpenView OmniBack II Integrations Guide for instructions.

Importing Hosts to a Cell

Importing a host tells the Cell Server to add the host (where OmniBack IIModules are already installed) to the cell.

To add a host, follow these steps:

1. In theHP OmniBack II - Cell Administration window, selectEdit →Import… from the menu bar to open theCellAdministration - Import Hosts window.

2-7

0 1�[25K�\ \ K32_; 6�1>@L]�D�4 ]�; D�F' PQh�� U #%$ �lYmR��iQfkj�h�� U #%$ ��YQb��&�#%&

2. SelectAdd... to open theImport - Load Hosts window.

TheDomain field of the window shows the IP address for your cell. Tochange this IP address, click the field with the address and enter the newIP address.

You can select the hosts by typing their names in theFilter field andselectingAdd. Short and long hostnames can be used. You can also usewildcards to select several hosts at once.

3. When you have specified all the hosts that you want to import, close theImport - Load Hosts window and return to theCellAdministration - Import Hosts window. The hosts you specifiednow appear in theHosts field.

4. Click theImport button to import the hosts.

Figure 2-2 Import Host window

2-8

0 1�[25K�\ \ K�25; 6�1-@^]�D�4 ]�; D3F' PQh�� U #V$ ��YQR��iQfkj�h�� U #%$ ��YQb.��&�#%&

Importing Hosts with Multi-LAN Cards

Hosts configured with multiple LAN cards or MS/ServiceGuard havemultiple network names.

To avoid having OmniBack II assign licenses to all the network names of thesame host, follow the procedure below. You can only import one hostnameat a time using this procedure.

1. Using the method described in the previous section, import the host withits primary hostname to the cell. A primary hostname is the name you getusing the UNIXhostname command and will be licensed by OmniBackII.

2. In theCell Administration - Import Hosts selectAdd... to openthe Import - Load Hosts window.

Using any of the methods enter one of the multiple hostnames to the listof hosts. You must only import one hostname at a time.

3. Close theImport - Load Hosts window and return to theCellAdministration - Import Hosts window. The hostname youspecified now appears in theHosts field.

4. Click theAdditional Host Name button to import the hostname.

OmniBack II will add the hostname to the cell but will not assign anadditional licence for this hostname.

Repeat steps 2, 3, and 4 for all the multiple hostnames of the host.

Exporting Hosts from a Cell

Exporting a host tells the Cell Server to remove a host from the cell withoutremoving the OmniBack II modules installed on it.

To export a host, follow these steps:

1. In theHP OmniBack II - Cell Administration window, select thehosts you want to export from the cell.

2-9

0 1�[25K�\ \ K32_; 6�1>@L]�D�4 ]�; D�F' PQh�� U #%$ �lYmR��iQfkj�h�� U #%$ ��YQb��&�#%&

2. SelectEdit →Export from the menu bar. The selected hosts aredisplayed in theHosts field.

3. You can remove hosts from the list by selecting them and clickingDelete .

4. Click theExport button to export the hosts in theHosts list.

5. Remove all appearances of the exported hosts from datalists. See theonline help for instructions how to modify datalists.

2-10

0 1�[25K�\ \ K�25; 6�1-@^]�D�4 ]�; D3FX h�i�R�#%$ �lYmOIPQ��$ ,�R�S�/ ' ' ��d $ "��!#V&

Updating OmniBack II Clients

If you want to update to a new version of OmniBack II, you can do it easilyby installing the new software on the Cell Server and then performing thefollowing procedure to update all hosts in the cell. You can manually selectwhich modules you want to update. OmniBack II automatically checks allthe hosts in the cell and updates the selected modules.

OmniBack II automatically removes installation packages of the olderversion thus freeing more disk space.

This feature is supported for UNIX systems only.

To Update OmniBack II Clients

This procedure does not install any new modules; it only updates theexisting ones.

The procedure may take some time, depending on your cell configuration.

1. In theHP OmniBack II - Cell Administration window, selectEdit →Update All to open theCell Administration - UpdateHosts window.

2. Select the modules you want to update and start the update by clickingOK.

3. Follow instructions and messages in theHP OmniBack II - UpdateTerminal window.

The new version number of the modules you updated now appears for all thehosts in theHP OmniBack II - Cell Administration window.

2-11

0 1�[25K�\ \ K32_; 6�1>@L]�D�4 ]�; D�F` "�$ ��&3#VR�d d $ ��YQOIPQ��$ ,�R�S�/ ' '3ZVU ��PnR-b��&3#

Deinstalling OmniBack II from a Host

If your system configuration changes, you may need to deinstall OmniBackII software from a host. Deinstalling OmniBack II from a host removes allthe OmniBack II modules from the host and removes all references to thishost from the Cell Server.

This feature is supported for UNIX systems only.

To Deinstall OmniBack II Modules

1. In theHP OmniBack II - Cell Administration window, select thehost you want to deinstall.

2. SelectEdit → Deinstall from the menu bar to open theCellAdministration - Deinstall window.

3. Select modules you want to deinstall. Only modules currently installed onthe host are available for deinstallation. If you deinstall all the availablemodules, this host is completely removed from the OmniBack II cell.

4. Click OK to begin the deinstallation process. Follow instructions andmessages in the HP Cell Administration - DeinstallTerminal window.

5. Remove all references to this host from datalists. See the online help forinstructions how to modify the datalists.

2-12

0 1�[25K�\ \ K�25; 6�1-@^]�D�4 ]�; D3F` "�$ ��&3#VR�d d $ ��YQOIPQ��$ ,�R�S�/ ' '3ZVU ��PnR-b��&3#

3-1

3

Configuring a Cell

3-2

o 6�13p�<�9�47; 1�<-K o D�\ \

In This Chapter

Configuring a cell involves defining a backup strategy, configuring yourlogical devices, implementing a media management strategy, and setting upthe user access security. The information you need to plan your cellconfiguration is explained in the following sections. The actual steps fordoing the configuration are explained in the online help system. The onlinehelp system is divided into task help and window help. The task helpprovides detailed step-by-step information for configuring a cell. Thewindow help provides detailed information about the fields and buttons ineach window.

3-3

o 6�13p�<�9�4q; 1�<>K o D�\ \cLd R��$ ��Y)#V*�"-�."�d d &

Planning the Cells

A cell can represent an organizational entity (such as a department) or ageographical location (such as a field office). It consists of a set of hosts(server and clients) having a common backup policy, located in the sametime zone, and existing on the same LAN. How the network is divided intocells has a major impact on the backup strategy for the network, so carefulplanning is important. For the best performance, we recommend having amaximum of 50 hosts in a cell. Additional factors that affect performanceinclude the amount of data and the number of files to be backed up.

e O ( f gA host can belong only to one cell.

HP OmniBack II allows you to manage and monitor backup and restoreactivities at either the cell or enterprise level. An administrator defines thebackup policies, security, logical devices, media pools, and users for eachcell.

When defining the cells, consider the following factors:

Quantity ofData The amount of data to be backed up.

Type of Data Files, databases, specific applications (seeHP OpenViewOmniBack II Integration’s Guide)

Importance ofData Is data modified often and does it require regular backup,

as with user’s working files, or is it mostly permanent,such as system files?

BackupOperations Are unattended backups needed?

Devices Availability and characteristics of backup devices

Security User access to backup and restore functions

Performance Network infrastructure and speed of the network

3-4

o 6�13p�<�9�47; 1�<-K o D�\ \cLd R��l��$ �lYI#%*�"-��"�d d &

Time Zones Calculations of backup start times

To install OmniBack II, you will need to define the following for each cell:

• Which host will be the Cell Server (Note: once the Cell Server is selected,it is difficult to change it)

• Which hosts have disks to be backed up (Disk Agent clients)

• Which hosts have backup devices that will be used (Media Agent clients)

• Which hosts (in addition to the Cell Server host) will be used to accessOmniBack II (command-line interface and the User Interface).

Once you have planned your cells, you can begin installing the HPOmniBack II on the Cell Server. SeeHP OpenView OmniBack II InstallationGuide for instructions.

3-5

o 6�13p�<�9�4q; 1�<>K o D�\ \c�d R��$ ��Y)r^��W U ,�R�S�/�W�hQsk# U R3#V"�Y!t

Planning Your Backup Strategy

OmniBack II offers great flexibility in how you configure and perform yourbackups. When you plan your backup strategy, you need to make thefollowing decisions:

backup type Filesystem or Rawdisk

backup mode Full backup or Incremental backup

backup contentsWhich data to back up

backup options Compression, encryption, public/private access to data,report level, file locking, date/time stamps, pre/postexecution of commands, and data protection limits

backupschedule Specific date/times or time cycle

Each of these is explained in the following sections.

Choosing the Type of Backup

How your data is organized influences the type of backup you choose. Twotypes of backup are explained here:

Filesystem

If you want a complete record of every file and directory that was backed up,aFilesystem backup is best. This type of backup tracks the logical structureof the data on the media. The advantage is easier recovery of data; thedisadvantage is that filesystem backups are generally slower than rawdiskbackups. This backup type is used for ordinary filesystems such as systemand user directories and so forth.

3-6

o 6�13p�<�9�47; 1�<-K o D�\ \cLd R��l��$ �lYIru��W U ,�R�S�/�W�hQsk# U R3#V"�Yvt

When you configure a filesystem backup, you define exactly whichfilesystems are going to be backed up.

Host Backup

Host backup is essentially the same as filesystem backup, but is dynamic.You specify a host to back up and during backup time OmniBack II checkswhich filesystems are present on the host and backs them up. This is suitablefor hosts with dynamic configuration where disks are often mounted andunmounted.

Rawdisk

Rawdisk backups are useful for backing up databases located on a diskwithout a filesystem. This type of backup does not track the logical structureof the data on the media. The advantage is faster backup of a complete disk.The disadvantage is that the OmniBack II does not know which files are partof the backup when you do a restore. Only the name of the rawdisk devicefile is recorded in the database. The rawdisk backup backs up a completedisk, including the unused parts, and may therefore take longer than afilesystem backup when a disk is only half full.

For limitations, seeHP OpenView OmniBack II Software Release Notes.

Choosing the Mode of Backup

How frequently you back up your data affects the security and recoverabilityof the data. The more frequent the backup, the smaller the potential data lossin the event of a disk failure. There are two types of backup mode: Full andIncremental.

Full Backups

A full backup includes all the data for the specified objects (directories,filesystems, or databases). It is a "snapshot" of the data as it currently exists.In the event of data loss, all data can be recovered using this one backup.The advantage of a full backup is security (the complete object is backed up)and faster, easier recovery (only one set of backup media must be restored).The disadvantage is that a backup may take a long time and needs moremedia to back up all data.

3-7


Incr emental Backups

An incremental backup includes only the data that has been modified sincethe last full or last incremental backup. Incremental backups are faster andneed less media to back up data but make the restore of all data morecomplicated as you usually need all the media used since the last fullbackup.

e O ( f g If a directory is modified, it is backed up during an incremental backup, butpreviously backed-up files in the directory are not backed up if they have not beenmodified.

Incremental backups are only valid if the full, protected backup on whichthey are based exists. See “Using Backup Options” on page4-26 for moreinformation. OmniBack II checks if there is a protected full backup beforestarting an incremental backup. If there is no protected full backup,OmniBack II performs a full backup instead. This can potentially overwritean unprotected full backup. You can customize this behavior by setting theIncrOnProtected variable in the global options file. See “OmniBack IIGlobal Options File” on page7-13 for more information.

e O ( f gYou are advised to use the same backup options with full and incremental backup. Besure to use one of the optionstouch andno_touch with both types of backup. Ifyou use theno_touch option with full backup and thetouch option withincremental backup, the incremental backup will be the same as a full backup.

Incr Is based on the last backup, either full or incremental.This is the basic incremental backup type.

Incr (1-9) Are based on the previous incremental backup of a lowerlevel. For example, incremental backup level 3 backs updata changed from the last level 2 or lower backup.

Three examples of incremental backups (incremental, single-level, andmultiple-level) are described here:

Incr emental Backups

Using incremental backup (Incr) provides an efficient and simple way toconfigure backups. Each incremental backup is based on the previousbackup of any type.

3-8


Single Level Incremental Backups

A typical backup strategy involves a combination of full and incrementalbackups. Each incremental backup is based on the last full backup. Forexample, a full backup is done once a week during a period of low systemusage and incremental backups are done at once each business day in theevening. This type of schedule has the advantage of minimizing the timeneeded for recovery while at the same time minimizing the effort needed toback up the data on a regular basis. Here is an example of this type ofschedule:

Friday night Full Backup includes all data

Monday night Incr-1 Backup which includes all data modified since thefull backup on Friday night

Tuesday night Incr-1 Backup which includes all data modified since thefull backup on Friday night

Wednesdaynight Incr-1 Backup which includes all data modified since the

full backup on Friday night

Thursday night Incr-1 Backup which includes all data modified since thefull backup on Friday night

In this example, a complete recovery on Wednesday involves restoring thefull backup from Friday and the level 1 incremental backup from Tuesday.Everything between the backup of Tuesday night and the time of the systemdisaster on Wednesday is at risk. Note that each incremental backup makesthe previous one obsolete.

Multiple Level Incr emental Backups

Another backup strategy involves the use of multiple-level incrementalbackups. Here, the incremental backups are based on other incrementalbackups. By using different incremental levels, you can develop asophisticated backup strategy. Multiple-level incremental backups have theadvantage of reducing the time and the number of media needed to performthe backups even more than the single level incremental backup. Thedisadvantage is in the increased complexity and length of time needed fordata recovery.

Here is an example of this type of schedule:

3-9


Friday night Full Backup includes all data

Monday night Incr-1 backup which includes all data modified since thelast full backup on Friday night

Tuesday night Incr-2 backup which includes all data modified since theIncr-1 backup on Monday night

Wednesdaynight Incr-1 backup which includes all data modified since the

full backup on Friday night

Thursday night Incr-2 backup which includes all data modified since theIncr-1 backup on Wednesday night

In this example, a complete recovery on Wednesday involves restoring thefull backup from Friday, the level 1 incremental backup from Monday, andthe level 2 incremental backup from Tuesday. Everything between thebackup of Tuesday night and the time of the system disaster on Wednesdayis at risk.

Deciding What to Back up

The previous two sections covered choosing a backup type and backupmode. A third factor affects the security and recoverability of your data:deciding WHAT to back up. Your system probably has a mixture of data,some of which is very dynamic and some of which is static. Using theexample of a purchasing department, the vendor information is probablystatic, while order information is very dynamic. The purchasing departmenthas a group of vendors from whom orders are placed on a continuous basis.Assuming that there is a vendor database and an order database, the vendordatabase remains somewhat static and the order database is updated on anhourly basis. Therefore, the potential data loss is greater for the orderdatabase because there are more database updates in the time between thebackups. A backup strategy for this scenario might include daily fullbackups of the order database and daily incremental backups of the vendordatabase.

3-10


Choosing a Backup Schedule

The previous three sections covered deciding WHAT data to back up andHOW. This section helps you decide WHEN to back it up. For backups to beeffective, they must be done on a regular basis. Your data is only as safe asupon backups. The greater the time interval since your last backup, thegreater risk to your data. Backup schedules are generally set in one of twoways: by specific date/time or by time cycle.

Specific Date/Time

The most common form of backup schedule is based on specific dates/times.A backup is performed at the same time and on the same day each week ormonth. For example, a full backup is done every Friday night at 6:00 and anincremental backup is done every Monday, Tuesday, Wednesday, andThursday night at 8:00. A schedule like this is easy to plan and remember.OmniBack II can also be configured to check the Unix holiday file to skipbackups on holidays.

Time Cycle

Time cycle backups are done at regular time intervals based on periodicschedules. For example, a full backup is done once every two days at 12:00.Therefore, if the first backup is Monday at 12:00, subsequent backups willstart at 12:00 on Wednesday, Friday, Sunday, Tuesday, Thursday, etc.

Protection

This option enables you to set periods of protection for data you back up andfor the information about backup stored in the Backup InformationDatabase. This prevents backup data from being overwritten for a specifiedperiod. The default value isPermanent.

The backup protections are:

None Provides no protection. Data will be overwritten if themedium it is stored on is reused.

3-11


� T X ( ' O e gUse this option for test backup only. Stored data will be overwritten when themedium is used again since no protection has been chosen.

Until Data on the medium cannot be overwritten until aspecified date. You enter the year, month, and day.Protection for the data will stop at noon of the specifiedday.

Days Data on the medium cannot be overwritten for the numberof days specified. For example, if you set the protectionfor two days and the current backup starts at 20:00 (8:00PM) on Wednesday, the data will be protected until Fridayat 20:00.

Weeks Data on the medium cannot be overwritten for the numberof weeks specified. For example, if you set the protectionfor one week and the current backup starts at 10:00 onWednesday, the data will be protected until 10:00 thefollowing Wednesday.

Permanent Data is permanently protected from being overwritten.Use therecycle option with media to remove thepermanent protection. See “Recycling Media/RemovingProtection” on page3-32.

For more information about backup options, see “Using Backup Options” onpage4-26.

For more information about the OmniBack II Database, see .

Planning Cell Access and Security

OmniBack II allows you to run backup and restore sessions on a cell fromany Cell Server, as long as you have network access. This is particularlyuseful when you manage more than one cell in your environment, you arerunning the HP OpenView IT/ Operations, or you have configured anadditional Cell Server with a switchover.

3-12


In smaller environments where you only have one cell, you may want todisable this feature and allow starting backups from the local Cell Serveronly.

The following actions alter the/etc/opt/omni/cell/allow_hosts/file on all UNIX client hosts andallow_hosts registry entry on allWindow NT client hosts.

Limiting Access

Once you have configured all the hosts in a cell, you must do the followingto limit access to the cell:

1. From theHP OmniBack II Install Window chooseEdit → Addaccess limit to cell to open theCell Administration - Limit HostAccess window.

TheCell Server field displays the name of the local Cell Server andcannot be modified.

In theOPC host(s) field, enter hostnames of the HP IT/Operationsmanagement system from which you want to access hosts in theOmniBack II cell.

In theAlt. cell server(s) field, enter hostnames of alternate CellServers. If you leave this field empty, only the local Cell Server will haveaccess.

2. ChooseOK to limit access to the cell. TheMessages field shows theprogress.

If you wish to add a new host later, you must repeat the procedure.

Allowing Access to the Cell

If you want to allow access to the cell from any other Cell Servers or fromthe HP OpenView OperationsCenter, you must:

1. From theHP OmniBack II Install Window chooseEdit → Removeaccess limit from cell to open theRemove access limit window.

2. ChooseRemove limit to allow access to the cell from other Cell Servers.

3-13


Using Data Compression

OmniBack II has a compression feature which allows you to reduce thenumber of media needed for a backup. The standard Unix compressionalgorithm is used, which provides a compression ratio of approximately50%. You can substitute a customized compression algorithm by replacingthe shared library and integrating this into OmniBack II. Compression canbe set for each object or for the whole session. For information oncustomizing the compression algorithm, see “Customizing the CompressionAlgorithm” on page7-50.

e O ( f gIf you are configuring two logical devices that actually point to one physical device,when one is configured to back up compressed data and the other uncompressed data,you re advised to specify theLock Name in the advanced options for the two logicaldevices. Both logical devices must have the same lock name or one logical devicemust have the name of the other logical device specified as a lock name. A LockName is the name which OmniBack II recognizes in order to lock the device beforestarting backup and restore sessions.

e O ( f gMost modern backup devices provide built-in hardware compression that you canconfigure when adding the device to the host. See your device’s manual forinstructions. In this case, do NOT use the compress option of OmniBack II, sincedouble compression only decreases performance without giving better compressionresults.

Using Data Encryption

OmniBack II has a simple encryption feature which provides greatersecurity for the data contained on your backup media. Encryption can be setat the object or session level. You can substitute a customized encryptionalgorithm by replacing the shared library and integrating this into OmniBackII. For more information on customizing the encryption algorithm, see“Customizing the Encryption Algorithm” on page7-45.

3-14

o 6�13p�<�9�47; 1�<-K o D�\ \w "�i�$ R w R��lR�Y�"�PQ"��!#

Media Management

OmniBack II introduces a complete media management system. It protectsyour data by providing the following features:

• protection against accidental overwrite• notification of bad or worn media• optimization of the space available in libraries• tracking and managing media

OmniBack II provides protection by tracking and protecting the data on themedia. The media management system checks the media managementdatabase before writing to a backup medium. This prevents accidentaloverwrites.

The media management system uses adatabase to record information aboutthe following aspects of a backup or restore:

• date and time the backup was started• type of backup• directories, files, and disks that were backed up• file positions on the media• usage and condition of the media in the pools• protection expiration date for the data contained on the backup media• copying media

e O ( f gThe growth and size of the OmniBack II database are determined by the level ofdetail recorded about each backup and restore session. For more information onmaintaining the OmniBack II database, see “Managing the Growth of the Database”on page8-4.

The Media Pool Approach

The OmniBack II media management paradigm of handling backup mediauses the term “media pool” to describe a mechanismfor managing largenumbers of media cartridges.

3-15

o 6�13p�<�9�4q; 1�<>K o D�\ \w "�i�$ R w R��R�Y�"�PQ"��!#

A media pool is an organized collection of mediawhich share commonproperties. Grouping media into media poolsallows OmniBack II tooptimize media usage, allocation, and retentionpolicies. Each mediumbelongsto only one pool at a time. The administrator specifies a particularallocation and protection policy for media in this pool. OmniBack II alsotracks the amount of free space remaining in the pool based on the amount ofspace specified for each medium when it is added to the pool. OmniBack IIsums up the space on each medium to calculate the space for one pool.

For example, in a typical environment you may want to create:

• a media pool for a company wide backup• a media pool for archiving purposes• media pools for backup of specific teams• media pools for private backups (Joe’s DDS media pool)

Pool Attributes

Pool Name

A pool name identifies a pool. It can consist of up to 32 characters includingspaces. We recommend that you assign a name which will help you identifyeither the logical device or the function of the pool.

Description

A description is optional and helps operators identify the pool. Thedescription can contain any characters with a maximum length of 80characters.

3-16


Media Class

Media class is the type of media, for example, DDS tapes or optical disks.TheMedia Class button of thePool Editor window has a menu ofsupported media classes.

When you select the type of media, OmniBack II calculates available spacefor that pool based on the media class you have selected. The default valueof the available space on a medium is only used in previews. For example, ifyou specify DDS, a default size of 2.0 GB is assumed when initializing themedia. You can overwrite this default with your own value using theSpecify option.

Media Allocation Policy

The media allocation policy determines the order in which media areaccessed within a pool so that media wear out evenly. OmniBack II balancesthe use of the media in a pool and therefore issues mount prompts based onthe status (condition) of the media.

Strict directs OmniBack II to require a specific medium. TheMedium must be already initialized. This allocationpolicy is preferrable for use with library devices toprevent accidental overwrite of non-OmniBack II mediain the library.

Loose directs OmniBack II to accept any suitable medium in thepool (medium must not be in apoor condition orprotected). A non-OmniBack II medium is automaticallyinitialized. This policy is preferrable for stacker devices,as they load media in sequential order - a strict policywould require media to be loaded in the same order asthey are to be used.

e O ( f gFor libraries containing several media, a strict policy directs OmniBack II to issuemount prompts for the least-used media first. It continues to request these "newer"media until the usage of these media equals the usage of the other media in the pool.Therefore, if you add a new (unused) medium to this pool, it will be requested more

3-17


often by OmniBack II. To balance the usage, we recommend that you pre-initializeyour media before adding them to an existing pool. Initializing a medium also allowsyou to add a label to the medium, helping you to identify it.

Media Usage Policy

The media usage policy determines whether or not a new backup can beappended to a medium containing a previous backup.

Appendable A backup session writes data to the space remaining onthe last medium used in the previous backup session.Subsequent data in the backup set is written to the firstposition of the medium. Appending media conservesmedia space but reduces flexibility in manipulatingmedia, because one medium can contain data from severalbackup sessions.

Non-Appendable A backup session writes data beginning at the first

position on the first medium of the backup media set.

Appendable ofincrementalsonly A backup session appends to a tape only if an incremental

backup is performed. This allows having a complete set offull and incremental backupon the same medum if there isenough space.

Media Condition Factors

OmniBack II calculates the condition of used media usingmedia conditionfactors. The condition of the media in a pool determines the condition of thepool. The condition of a pool indicates the reliability of that pool forbackups. For example, old or worn media are more likely to have read/writeerrors. OmniBack II allows you to define the acceptable thresholds for yourmedia. There are three types of conditions for a medium:

3-18


Good less than 80% of the threshold for age or usage

Fair 81 to 100% of the threshold for age or usage

Poor exceeds 100% of the threshold for age or usage or ifread/write errors have occurred on this medium

The thresholds used to calculate the status of a medium are described here:

Medium validfor The age of a medium is calculated as the number of

months that have elapsed since you initialized themedium. For this age to accurately represent the age ofyour media, we recommend that you use new media whencreating a media pool. The default threshold is 36 months.Once a medium is older than 36 months, it is marked ashavingpoor status.

Maximumnumber ofoverwrites The usage of the medium is defined as the number of

overwrites to the medium. For OmniBack II to accuratelycalculate the condition of your media, we recommendusing new media when creating a media pool. The defaultthreshold is 250 overwrites. Once a medium has morethan 250 overwrites, it is marked aspoor .

Managing Media Compatibility

OmniBack II recognizes the following media types:

• tar• cpio• OmniStorage• OmniBack and OmniBack/Turbo• HP-UX filesystem• OmniBack II• ANSI labeled tapes

3-19


e O ( f gSince recognition of media types depends on the platform used, we do notrecommend that you rely on OmniBack II to recognize other media types. For an up-to-date list of detection of media types of various platforms, seeHP OpenViewOmniBack II Software Release Notes.You may want to set theInitOnLoosePolicy option in the global options file.The medium will not be automatically initialized and data will not be overwritten incase it is not recognized. See “OmniBack II Global Options File” on page7-13 forinstructions.

e O ( f gIf you try to read from a medium that was written using hardware compression witha device that does not support compression, OmniBack II will not recognize the DDSand cannot read its data, but will initialize and overwrite it with the next backup.

The initialization policy for these backup media formats is shown in thetable below.

OmniBack II only writes to media initialized by OmniBack II. You cannotforce the overwrite of another backup media format during a backup. Thishelps avoiding accidental overwrites of other backup media.

Format OmniBack IIoptions

Overwrite

unknown irrelevant yes

tar, cpio, OmniStorage, OmniBack I,ANSI label, filesystem

no-force no

tar, cpio, OmniStorage, OmniBack I,ANSI label, filesystem

-force yes

OmniBack II no-force no

OmniBack II -force dependent on theprotection set for the

backup session

Table 3-1 OmniBack II Overwrite Policy

3-20


Media Identification

Adding a medium to a media pool consists of initializing the medium. Whena medium is initialized, OmniBack II assignes two identifiers to the medium:

media ID A unique ID created by OmniBack II, 32 characters inlength.

media label A user-defined label, up to 80 characters in length. If thedevice supports barcode, the barcode is automaticallyinserted at the beginning of a media label.

For identification on other systems, an ANSI X3.27 label is also written onthe tape. Note that any further modifications to the media label are onlyrecorded in the OmniBack II database and not on the medium itself.

These labels identify the medium as an OmniBack II medium. When loadinga medium for backup or restore, OmniBack II checks the medium for themedia ID. When it finds the media ID, it checks the media managementsystem to see what information it has about this medium. This informationtells OmniBack II whether the requested action is allowed for this medium.For example, if you are trying to write a new backup to this medium, themedia management system checks whether the expiration date for the dataalready contained on this medium has passed.

OmniBack II displays the media ID, the media label, and the location whenprompting you to mount a medium. OmniBack II knows the media ID of amounted medium and does not display a mount prompt if the requestedmedium is already in the device.

3-21

o 6�13p�<�9�4q; 1�<>K o D�\ \��!x+Y�W U $ ��YQR��i X &�$ �lYmyl��Y�$ S�R�d ` "� �$ S�"�&

Configuring and Using Logical Devices

OmniBack II introduces the concept of logical devices that representphysical devices with various user defined characteristics such as location ormedia mount handling. A logical device is associated with a media poolused by OmniBack II to back up and restore data. Since backups andrestores are done using logical devices, you must configure your logicaldevices before you can do a backup or restore.

For more information on configuring and using libraries, see “UsingComplex Devices and Libraries” on page9-1.

The Concept of Logical Devices

A logical device is a group of one or more physical devices of the same typethat are treated as one device by OmniBack II. Backups and restores aredone using logical devices.

For standalone devices, a logical device may consists of linked physicaldevices that allow you to do unattended backups. When the medium in onephysical device is full, the backup automatically continues using the nextphysical device in the logical device.

Note the following requirements for logical devices:

• All the physical devices in a logical device must be of the same type (forexample, DDS)

• All the physical devices in a logical device must exist on the same host.

• A physical device can only belong to ONE logical device.

For more information on using libraries, see “Using Complex Devices andLibraries” on page9-1.

3-22

o 6�13p�<�9�47; 1�<-K o D�\ \�.��!x+Y�W U $ ��YQR��i X &�$ ��YQy��Y�$ S�R�d ` "3 �$ S�"�&

Cleaning Tape Support

HP OmniBack II provides automatic cleaning for most backup devices usingcleaning tape.

For HP SureStore 12000e devices, OmniBack can detect cleaning tape. Ifthe cleaning tape is loaded during backup or restore, OmniBack IIrecognizes the cleaning tape and logs automatic device cleaning to the logfile /var/opt/omni/log/cleaning.log .

For SCSI-II libraries it is possible to define which slots hold cleaning tapes.

For devices with barcoded media, OmniBack II recognizes cleaning tapebarcodes automatically, if they have the “CLN” prefix.

For devices without a cleaning tape, a dirty drive is detected and a cleaningrequest is displayed on the session monitor window. The device must becleaned manually.

You cannot continue your backup without cleaning the drive, since thebackup may fail because data may not be correctly written and stored on themedia.

OmniBack II detects cleaning tapes in two ways:

1. Hard inventory (during load of cartridge) - only for 48AL

2. Soft inventory (via CLN prefix in barcode) - with policies which supportbarcodes (libraries, Grau ABBA, StorageTek).

You can configure a cleaning slot (a slot where OmniBack II can always finda cleaning tape) only for SCSI II libraries (Grau ABBA and StorageTekACS have dynamic repository), and only for “tape” media (not for File andOptical).

e O ( f gDetection and use of cleaning tapes depends on the platform used. SeeHPOpenView OmniBack II Software Release Notes for the up-to-dateinformation.

3-23


Device Locking While in Use

During backup or restore sessions, OmniBack II locks devices in use inorder to prevent use by multiple sessions. Actually, the logical device nameis locked.

OmniBack II allows you to lock a virtual name and not the real logicaldevice name by specifying this virtual name in theLogical Device -Advanced Options , Lock Name option.

This feature is useful when you have configured several logical devices forthe same physical device, for example, compressed and non-compressedDDS device. To prevent simultaneous usage of the same physical device,you can specify a virtual lockname in both device configurations. Thisfunctionality works if devices are specified in different datalists. If morelogical devices names of the same physical device are specified in the samedatalist, devices are aborted.

For example:

DDS_NC is a logical device name for a non-compressed DDS device,DDS_Cis a logical device name for a compressed device. In theLock Name field oftheLogical Device - Advanced Options window for both devicesenterDDS_Lock.

Configuring Logical Devices

HP OmniBack II stores information about each logical device in thedatabase.

To configure logical devices, follow these steps:

1. In theHP OmniBack II- Main window, select theDevices & Mediaicon. TheHP OmniBack II - Device & Media Managementwindow displays the logical devices and media pools that are currentlyconfigured for the cell.

2. In theHP OmniBack II - Device & Media Management window,

3-24


selectEdit → Create .

3. In theLogical Device Editor window, select a device type andfollow the online help.

Figure 3-1 Configuring a Logical Device

If you are configuring OmniBack II for the first time, the only media poolshown in the list of media pools is the default pool for this device type (forexample "default DDS"). To configure a logical device, you have twochoices:

• You can create an empty pool (a pool without media), and use this poolwhen configuring the logical device. You can then add media to this poolafter you have created the logical device. This is the recommended

3-25


method. See “The Media Pool Approach” on page3-14 and online helpfor instructions.

• You can use the default pool in order to complete the configuration of alogical device. After you have configured the logical device, you canconfigure an additional pool and assign a device to it. See “The MediaPool Approach” on page3-14 and online help for instructions how tocreate the media pool. UseEdit → Modify… to assign a device to thepool.

Configuring Typical Devices

This section provides examples about how to configure some typicaldevices. Be sure to read all relevant sections in order to make full use of thisflexibility.

The following instructions are provided as guidelines only.

Configuring Standalone Devices

Standalone devices are, for example, simple one-drive DDS or ExaBytedevices.

To configure a standalone device, follow these steps:

1. In theHP OmniBack II - Main window, click theDevice & MediaManagement icon to open theHP OmniBack II - Devices & MediaManagement window.

2. In theHP OmniBack II - Devices & Media Management window,selectEdit → Create → Standalone and follow the online helpinstructions.

If you are configuring OmniBack II for the first time, the only media poolshown in the list of media pools is the default pool, for example, defaultExaByte.

3-26


Configuring SCSI-II Library Devices

SCSI-II Library devices are larger libraries, also called autoloaders orjukeboxes. They contain a number of media cartridges and can havemultiple drives for backup and restore operations.

When configuring a library device, note the following:

• You must configure a logical device and then add the drives to the librarydevice configuration. For example, drives in a four drive DLT librarycould be configured as DLT_1, DLT_2, DLT_3 and DLT_4 in aDLT_library OmniBack II device.

• It is not necessary to configure all drives for use with OmniBack II.

• You can configure a Media Agent for each drive to run on a different hostin a network (multi-host support).

• You can configure one media pool for all drives or have an independentmedia pool for each drive.

To configure aSCSI-II Library Device follow these steps:

1. In theHP OmniBack II - Main window, click theDevice & MediaManagement icon to open theHP OmniBack II - Devices & MediaManagement window.

2. In theHP OmniBack II - Devices & Media Management window,selectEdit → Create→ SCSI II-Library and enter the necesarryinformation.

3. OmniBack II prompts you to configure the drives you want to use in thislibrary. Enter the necessary information for each drive and repeat this stepuntil you have configured all drives.

e O ( f gTake care when configuring the logical device that you specify the right device filefor the right drive index. If you do not, you could set it up so that the library loadsmedia into device 2 and reads from device 1. This is important for a library with twoor more drives.

3-27

o 6�13p�<�9�4q; 1�<>K o D�\ \w "�i�$ R w R��R�Yl"�PQ"��!#�(zR�&�/�&

Media Management Tasks

Media management tasks are accessible using theEdit andView menus intheDevice & Media Management window for the pool you select.

Most of the media management tasks are also accessible from theLibraryManagement window.

Figure 3-2 The OmniBack II - Device & Media Management Window

3-28

o 6�13p�<�9�47; 1�<-K o D�\ \w "�i�$ R w R��lR�Y�"�PQ"��!#l(zR�&�/�&

Creating a Media Pool

When adding media to pools, we recommend using new (unused) media.This is because OmniBack II records the number of reads/writes to mediaand uses this information to calculate the age and condition of the media. Ifyou add used media to a pool, this information will be incorrect.

To create a media pool, follow these steps:

1. In theHP OmniBack II - Main window, click theDevice & MediaManagement icon.

2. In theHP OmniBack II - Device & Media Management window,selectEdit → Create → Media Pool .

3. In theMedia Pools - Pool Editor window enter the requiredinformation. See online help or “Pool Attributes” on page3-15 for moreinformation on specific fields.

After you have created a media pool, you can add media to the pool. See thenext section for instructions.

Adding Media to a Pool

You must enter a sufficient number of media to a pool to allow unattendedbackups.

e O ( f gOnce you have initialized a medium, you can only change theMedium Label andLocation in the database. To change the label and location on the medium itself,you must reinitialize the medium.

1. In theHP OmniBack II - Main window, click theDevices & Mediaicon.

2. In theHP OmniBack II - Device & Media Management window,double-click the pool name from the list of media pools.

3. In theMedia Management window, chooseEdit → Init .

3-29


4. In theMedia Management - Initialize Medium window, enter therequired information in the fields. See online help for more information.

Verifying a Medium

Verifying a medium checks whether the data on the medium is valid.OmniBack II performs the following:

• Checks the OmniBack II tape format headers.• If the CRC [Cycle Redundancy Check] option is used, OmniBack II

recalculates the CRC and compares it to the one stored on the medium.

To verify a medium, follow these steps:


2. In theHP OmniBack II - Device & Media Management window,double-click a media pool from which you want to verify amedium/media.

3. In theMedia Management window, choose a medium/media, selectEdit → Verify , and follow the online help.

OmniBack II displays a message about successful or unsuccessfulverification.

Erasing a Medium

TheErase Medium option is only available for magneto-optical platters.The action is used to pre-erase a magneto-optical platter, which significantlyincreases the speed of the backup because you need not erase the magneto-optical platters during backup.

To pre-erase a medium, follow these steps:


3-30


2. In theHP OmniBack II - Device & Media Management window,double-clicka pool containing magneto-optical media.

3. In theMedia Management window, select a medium/slot, clickEdit →Erase, and follow the online help instructions.

Modifying a Medium

Modifying a medium lets you change the label or location of the medium inthe OmniBack II database. The label is an identifier that you have assignedto the medium. Changing the location is useful if you send media to offsitestorage.

Modifying a medium only changes the information about this medium in theOmniBack II database; the medium itself remains unchanged.

To modify a medium, follow these steps:


2. In theHP OmniBack II - Device & Media Management window,double-clickthe pool from which you want to modify a medium.

3. In theMedia Management window, choose a medium/slot and selectEdit → Modify from the menu to open thePool Editor - ModifyMedium window.

4. In thePool Editor - Modify Medium window enter new informationin theLabel andLocation fields and confirm the modification.

Viewing Information About a Medium

OmniBack II allows you to view information about the usage and conditionof a medium. The condition of the medium affects your ability to write to amedium and read the data contained on the medium. This helps youdetermine when a medium must be replaced.

3-31


To view information about a medium/media, follow these steps:


2. In theHP OmniBack II - Device & Media Management window,double-clickthe pool from which you want to view information about amedium/media.

3. In theMedia Management window, choose a medium and selectEdit→ Info to open theMedia Management - Medium Info window.

Moving a Medium

OmniBack II lets you move a medium from one pool to another pool. This isuseful if you want to use the medium on another device. Note that the newpool must use the same type of media, for example, DDS tapes.


2. In theHP OmniBack II - Device & Media Management window,double-clickthe pool from which you want to move a medium.

3. In theMedia Management window, choose a medium/media you wantto move and selectEdit → Move to open theMedia Management -Move Media window.

4. In theMedia Management - Move Media window, select the mediapool to which you want to move a medium/media. The name of theselected media pool appears in theSelection field.

5. Click theOK button to confirm the move and return to theMediaManagement window. Note that the medium that was moved no longerappears in the list of media for this pool.

3-32


Recycling Media/Removing Protection

OmniBack II keeps track of data on every used medium. When configuringbackup, you can protect your data from being overwritten by newer backupsfor a specific time. Recycling removes the data protection from backed-updata, thus allowing OmniBack II to overwrite it during the next backup. Thedata on the media remains unchanged until the next backup.

To recycle a medium, follow these steps:


2. In theHP OmniBack II - Device & Media Management window,double-clickthe pool in which you want to recycle a medium/media.

3. In theMedia Management window, select a medium/media.

4. SelectEdit → Recycle and confirm your decision.

Exporting a Medium

Exporting a medium removes the information about a medium and itscontents from the database. OmniBack II no longer knows that this mediumexists. The medium and the data it contains remain unchanged.

You need to export media when you want to move it to another cell. Youmust export media in one cell and import them in another cell.

Media that hold protected data cannot be exported. You must recycle themedia first.

e O ( f gIf you plan to export media, you must export all the media of a backup session. If abackup session spans several media and you only export one medium of the set, therewill be inconsistencies in the OmniBack II database. These inconsistencies will causeproblems when you try to restore data from this backup session. These problems

3-33


occur because the backup session is in the database, but the data you want to restoreis on media that is no longer available. This generates an error message that thesession is not complete.

To export a medium follow these steps:


2. In theHP OmniBack II - Device & Media Management window,double-clickthe pool in which you want to select a medium to export.

3. In theMedia Management window, choose the medium you want toexport.

4. ChooseEdit → Export and confirm your action.

The medium that you have exported no longer appears in the list of mediafor this pool.

Importing a Medium

The import of media rereads all data about the backup sessions on the mediato the OmniBack II database.

If a session spans more than one medium, all media for this session must beimported to the database. If you do not import all the media of the session,the session will be only partially imported. This could cause problems atrestore time. If you select to restore from a partially imported session, youwill get the following message:

Full restore chain is broken or media needed for restore missing

You need to import media when you want to move media from one cell toanother. First you must export media in one cell and then import them inanother cell.

Note that during import OmniBack II reconstructs the detail catalog of asession. It reads the label, location, and protection information from themedium to the database. Any changes made to this information between the

3-34


initialization and the export will be lost as modifications are only made tothe database and not to the media. The original initialization informationwill be imported. Similarly, additional attributes such as object or media sizewill not be reconstructed during the import.

To import a medium, follow these steps:


2. In theHP OmniBack II - Device & Media Management window,double-clickthe media pool to which you want to import a medium.TheMedia Management window is displayed.

3. From theMedia Management window, chooseEdit → Import… toopen theMedia Management - Import window and follow the onlinehelp instructions.

4. During the import process, messages appear in theMessages field.

When the import is finished, you return to theMedia Managementwindow. The imported medium now appears in the list of media for thispool.

Scanning Media

Scanning media checks the format of media inserted in a logical device anddisplays information on slots or libraries.

To scan media, follow these steps:


2. In theHP OmniBack II - Device & Media Management window,double-clicka media pool from the list to opentheMedia Managementwindow.

3. In theMedia Management window, chooseEdit → Scan... and followthe online help instructions.

3-35


When the scanning is finished, the messages about the scanned media aredisplayed in theMessages field of theMedia Management window.

To scan a library using barcodes, theBarcode Reader Support deviceoption must be enabled in the device configuration. UseEdit → Barcoderescan to scan a library with barcodes.

Modifying Device and Media Management View

You can customize the media view in theDevice & Media Mangementwindow by changing the variables in the global options file.

To modify the default media view, follow these steps:

1. Open the global options file/etc/opt/omni/options/global .

2. Customize the attributes that will bedisplayed in the libray or mediamanagement viewby specifying the corresponding token strings.

3-36

o 6�13p�<�9�47; 1�<-K o D�\ \�.��!x+Y�W U $ ��Y X &�" U ��d R�&�&�"�&>R��i X &�" U &

Configuring User Classes and Users

How you configure your user classes and users has a major effect on thesecurity of a cell. Access to backup and restore functions gives a user accessto the data stored in that cell. Backing up data and restoring it to a differentdisk is essentially the same as copying the data from one disk to another.Data that can be backed up can also be removed and reloaded on a differenthost. Therefore, it is recommended that you carefully plan what backup andrestore functions you give to your OmniBack II users.

Figure 3-3 OmniBack II Users Administration Window

Each OmniBack II user is a member of a user class and has the accesspermissions of this user class. Auser class is a group of users with specificpermissions to perform backup and restore tasks.

3-37

o 6�13p�<�9�4q; 1�<>K o D�\ \��!x+Y�W U $ ��Y X &�" U ��d R�&�&�"�&>R��li X &�" U &

The following default classes are provided:

After the initial installation, all default user classes are empty except for theadmin class. The Unix root user on the Cell Server is automaticallyconfigured as the OmniBack II administrator. All other categories canremain empty if you want to restrict access to OmniBack II. You can add asmany additional user classes as you need for your environment.

Users are defined by their Unix login name and group. Wildcards (*) may beused for hostname, user name, and the group ID. There is no patternmatching; only the asteriks (*) is a valid wildcard.

e O ( f gAdmin capabilities are very powerful and they basically mean that the administratorhasroot capabilities on the whole cell. Normally, only the root user on a Cell Servershould have Admin capabilities.

You can use HP OmniBack II without modifying the default userconfiguration. However, for security reasons it is recommended that youverify (and if necessary modify) the default user configuration.

User Class Access Rights

admin allowed to configure OmniBack II and do backup, restore, andall other available operations. After installation, only therootuser on the Cell Server is configured as the administrator.

senior-operator

allowed to do all operations except configure OmniBack II

operator allowed to start backups and respond to mount requests

end-user allowed to do restore of their own objects. In addition, users canmonitor and respond to mount requests for their own restoresessions.

Table 3-2 OmniBack II Default User Classes and theirAccess Rights

3-38


Configuring User Classes

OmniBack II user classes are configured using theUser Administration - Add Class window. To access this window,follow these steps:

1. In theOmniBack II Main menu, clickUsers to open theHP OmniBack II - Users Administration window.

2. SelectEdit → Add → Class from the menu bar. TheUser Administration - Add Class window appears.

Creating a user class consists of the following steps:

1. Defining a user class name

2. Defining a description

3. Selecting the access rights

4. Confirming the configuration of this user class

1. Enter a user class name in theClass Name field. The user class namemust be alphanumeric and can have a maximum of 16 characters withoutspaces.

2. Enter a description in theDescription field. The description field cancontain any characters, is a maximum of 64 characters long, and spacesare allowed.

3. Select the access rights by clicking on the buttons to the left of the text.You can scroll up and down to view the complete list of access rights. Seebelow for a description of the access rights.

4. Click OK to confirm the configuration.

Repeat these steps to add additional user classes. For specific information onadding, modifying, and deleting user classes, see the online help system.

The access rights are described below:

Start backup allows users to perform backups of only their own data.Note that this access right automatically also allows theuser to monitor and abort his/her own session.

3-39


Start datalistbackup allows a user to perform a backup using adatalist. This

access right allows the user to start a backup using anydatalist and therefore back up the data objects listed inany datalist.

Save datalist allows users to create, schedule, modify, and save theirown datalists.

Backup as root allows user to back up any object using the root(superuser) login.

e O ( f gNote that this is a powerful access right that can affect the security of your system!

Mount pr ompt allows a user to respond to mount prompts for any activesession in the cell.

Start restore allows user to restore only his/her own objects (objectsfor which he/she is the Unix owner). This access rightautomatically also allows users to monitor and abort theirown session.

Restore to otherhosts allows a user to restore objects to a host other than the

host where the object was backed up. The user must havelogin permission on the destination host. Note that this isa powerful access right.

Restore fromother users allows the user to restore files belonging to another user.

Note that this is a powerful access right.

Restore as root allows user to restore objects usingroot capabilities.

e O ( f gNote that this is a powerful access right that can affect the security of your system!

Monitor allows a user to view session information for all sessionsin the cell.

Abort allows a user to abort any active session in the cell. Notethat this is a powerful access right.

3-40


Userconfiguration allows a user to add, delete, and modify user classes and

users. Note that this is a powerful access right.

Deviceconfiguration allows a user to create, delete, modify, and rename logical

devices. This includes the ability to add a mount promptscript to a logical device. Note that this is a powerfulaccess right.

Mediaconfiguration allows a user to manage media pools and the media in the

pools. Note that this is a powerful access right.

Switch sessionownership (Note that this access right is only appropriate if the "Start

Datalist Backup" access right is also enabled. The accessright "Switch Session Ownership" allows a user to start abackup using a datalist without becoming the owner ofthe backup session, if an owner has been set for thedatalist. You set the owner of a datalist using theFile →Change Ownership selection in theOmniBack II -Backup window. If this access right isOFF, the user whostarts the backup becomes the owner of the backupsession.

MS Exchange allows OmniBack II to run a backup of a MicrosoftExchange server. For instructions how to configure thisbackup, seeHP OpenView OmniBack II IntegrationsGuide.

MS SQL allows OmniBack II to run backups of a Microsoft SQLdatabase running on PC-based Windows NT systems. Forinstructions how to configure this backup, seeHPOpenView OmniBack II Integrations Guide.

e O ( f gTheEdit → Class → Modify menu selection can be used to both view and modifythe access rights of a user class. You cannot modify theAdmin class.

3-41


Configuring Users

Each OmniBack II user is a member of a user class and has the accesspermissions of this user class.

OmniBack II users are configured using theUser Administration -Add User window. To access this window, follow these steps:

1. In the OmniBack II main menu, clickUsers to open theHP OmniBackII - Users Administration window.

2. Click theUser Class in theUser Class list to select the User Classfor this user.

3. SelectEdit → Add → User from the menu bar to open theUserAdministration - Add User window.

To add a user, follow these steps:

1. Enter the Unix login (user name) in theUnix Login field. By clickingthe ... button you will get a list of users configured in the local/etc/passwd file.

2. Enter the Unix group name in theUnix Group field.

3. Enter the real name (actual name) of the user in theReal Name field.

4. Enter the host name of the user in theHost Name field.

5. Confirm the user class name in theClass field. If you want to use analternative User Class, click the field to activate it, and enter thealternative User Class name. Note that you can only enter the name of anexisting User Class.

6. Click theAdd button to confirm the new user.

Repeat these steps to add additional users.

3-42


4-1

4

Backing Up Your System

4-2

JLK�: M ; 1�<>{�B.|^6�9�4�}k~�[2_D�H

In This Chapter

This chapter explains the procedures, commands, and options for tasks doneduring most backup sessions. It explains how to do the following:

• Create and use datalists.

• Back up filesystems, hosts, and rawdisks.

• Configure the scheduler for scheduled backups.

• Using backup options.

• Change backup ownership.

OmniBack II provides two ways of backing up data:

• Scheduled or interactive.

• Full or incremental.

Before you run a backup, you must configure a cell with at least one host anda logical device. If the logical device is resident on a separate host, configurethat host in the cell as well. See Chapter 3, “Configuring a Cell,” on page3-1for more information.

To run a backup you must specify objects you want to back up. This is doneusing a datalist. A datalist is a list of objects (filesystems or rawdisks) to bebacked up. To have the datalist backed up periodically, set up a backupschedule using theScheduler.

Non-routine backups are generally run interactively.

The following sections provide you an overview of scheduled andinteractive backups.

4-3

JLK�: M ; 1�<>{�B.|^6�9�4�}k~�[2_D�HX ��i�" U &�#%R��il$ ��Y ` R�#VR�d $ &�#%&-R��iQ,�R U d $ &�#%&

Understanding Datalists and Barlists

What is a Datalist?

A datalist allows you to group and save backup objects. This is especiallyconvenient when these objects are backed up on a regular basis. Instead ofdefining the objects every time you run a backup, use the settings saved inthe datalist.

Datalists are ASCII files located in the/etc/opt/omni/datalistsdirectory on the Cell Server. For more details on the syntax of a datalist, seethe manpage foromnidatalist . Although it is possible to configuredatalists directly with a text editor, we recommend that you use the GUI dueto the complexity of the datalist syntax. OmniBack II provides a GUIdatalist editor which has been designed to guide you through the process ofconfiguring a datalist.

Once your datalist is set up, you only need to change it if your systemconfiguration changes or if you want to change backup options. OmniBackII automatically supplies default values for any options you omit from thedatalist.

When you create a datalist, the minimum information required is:

• What to back up.

• Where to back up (to which logical device).

You can create a datalist using two methods; choose the one that is simplerfor your case.

4-4

JLK�: M ; 1�<>{�B.|^6�9�4�}k~�[2_D�HX ��i�" U &3#VR��i�$ ��Y ` R3#VR�d $ &3#V&-R��iQ,�R U d $ &3#V&

GenerateDatalist This option automatically configures datalists for a

complete backup of all filesystems on the local host,selected hosts, or all hosts in the cell. You can latermodify the datalists to suit your specific requirements.

Create Datalist You create the whole datalist from scratch, specifying allbackup objects and options.

What is a Barlist?

Similar to a datalist, a barlist allows you to group and save objects forbackup of databases. Instead of defining the objects every time you run abackup, use the settings saved in the barlist.

Barlists are ASCII files located in the/etc/opt/omni/barlistsdirectory on the Cell Server. For more details on the syntax of a barlist, seethe manpage foromnibarlist . Although it is possible to configure barlistsdirectly with a text editor, we recommend that you use the GUI due to thecomplexity of the barlist syntax. OmniBack II provides a GUI barlist editorwhich has been designed to guide you through the process of configuring abarlist.

Once your barlist is set up, you only need to change it if your systemconfiguration changes or if you want to change backup options. OmniBackII automatically supplies default values for any options you omit from thebarlist.

For more information on OmniBack II integrations with popular databases,such as Oracle, Informix, Sybase. SAP R/3 and similar, seeHP OpenViewOmniBack II Integrations Guide.

4-5


Generating Datalists

This option automatically configures datalists for a complete backup of allfilesystems on the local host, selected hosts, or all hosts in the cell of theOmniBack II database. You can later modify the datalists to suit yourspecific requirements.

1. Choose theBackup icon from the mainHP OmniBack II window toopen theHP OmniBack II - Backup window.

2. SelectActions →Generate Datalists and choose a host on whichthe datalist will be generated. TheHP OmniBack II - GenerateDatalist window is displayed.

3. In theHP OmniBack II - Generate Datalist window, decidewhether you want to generate the datalist for a local host only, selectedhosts, or all hosts in the cell. You need to select theHost backup orFilesystem backup option for the selected hosts and enter the name ofthe datalist. Your datalist will be added to theOmniBack II Backupwindow.

4. If you need to modify this datalist see the online help or “Modifying aDatalist” on page4-7 for instructions.

4-6

JLK�: M ; 1�<>{�B.|^6�9�4�}k~�[2_D�HX ��i�" U &3#VR��i�$ ��Y ` R3#VR�d $ &3#V&-R��iQ,�R U d $ &3#V&

Figure 4-1 Generating a Datalist

Creating Datalists

You create the datalist from scratch, specifying all options, or create lists fordifferent databases (seeHP OpenView OmniBack II Integrations Guide formore information).

To create a datalist do the following:

1. Choose theBackup icon from the mainHP OmniBack II window toopentheHP OmniBack II - Backup window.

4-7


2. SelectEdit →Create →OmniBack II Datalist to open theOmniBack II Backup Editor window.

3. SelectObject →Add and choose from the menu the type of datalist youwant to create and follow the online help.

For detailed explanations on these parameters and their options, see theonline help and “Using Backup Options” on page4-26.

Modifying a Datalist

e O ( f gIf a cell is changed, for example, a host is removed, you need to load and modify thedatalist that includes this host. Otherwise, OmniBack II will generate a warningmessage.

1. Choose theBackup icon from the mainHP OmniBack II window toopen theHP OmniBack II - Backup window.

2. Highlight the datalist you want to modify.

3. SelectEdit →Modify List to open theOmniBack II BackupEditor window and follow the online help instructions.

You can add, remove, or modify objects specified in the datalist, and addbackup options to each object or to the datalist. See “Using BackupOptions” on page4-26 for more information.

e O ( f gIf you modify an object description in the datalist, the next backup for that object willbefull regardless of your backup mode selection.

4-8

JLK�: M ; 1�<>{�B.|^6�9�4�}k~�[2_D�H�.��!x+Y�W U $ ��YQR-��$ d "�&3t�&�#%"�Pn,�R�S�/�W�h

Configuring a Filesystem Backup

A filesystem is an organization of files on a mass memory device. Afilesystem is backed up so that the filename, file attributes, and the filecontents are stored on backup media. The set of files backed up from afilesystem in a specific session is called a "fileset." The fileset backed upfrom one filesystem changes from backup session to backup sessiondepending on user activity on this filesystem (creation of new files, deletionof old files, etc.) and whether a full or incremental backup has been run forthe session. OmniBack II keeps track of all backed-up filesystems andknows when and to which media each filesystem has been backed up.OmniBack II uses this information when you request a file or filesystem tobe restored. A disk containing a filesystem is identified by its hostname andmountpoint.

To get information about HOST backup see “Configuring Host Backup” onpage4-17.

The procedure for running a scheduled filesystem backup involves four maintasks:

1. Creating a datalist.

2. Selecting the filesystem to be backed up.

3. Selecting the backup options.

4. Setting up the backup schedule.

5. Previewing the backup.

Selecting a Filesystem to Back up

1. Choose theBackup icon from the mainHP OmniBack II window. TheHP OmniBack II - Backup window appears.

2. SelectEdit →Create → OB II Datalist from the menu bar. TheOmniBack II Backup Editor appears.

4-9

JLK�: M ; 1�<>{�B.|^6�9�4�}k~�[2_D�H��!x+Y�W U $ ��YQR-�l$ d "�&�t�&3#V"�Pn,�R�S�/�W�h

3. SelectObject →Add→Filesystem to open theOmniBack IIFilesystem Backup window.

Figure 4-2 Configuring a Filesystem Backup

4. Enter the hostname in theHostname field or click the... button to see alist of hosts.

5. Enter the mountpoint (which is the root directory of your mountedfilesystem) in theMount Point field or press the... button to choose themountpoint from a list.

6. Enter a description of this filesystem backup in theDescription field. It isuseful to enter the mountpoint when you back up more than one disk onthe same host. This will result in locating files more easily.

4-10


e O ( f gIf you modify an object description in the datalist, the next backup for that objectwill be full regardless of your backup mode selection.

7. ChooseExclude to exclude specific files and directories from the backup.For example, you may want to exclude the/tmp directory. Note that youmust enter the full pathname of files.

If you do not exclude a particular file or directory, the completefilesystem is configured for backup.

e O ( f gUse theExclude option to exclude the configuration and database directories/var/opt/omni/db and/etc/opt/omni from your Full Filesystem backups.Because the database is in use during the backup, a backup of the database will beincomplete and you will not be able to restore the database from this backup.We also recommend excluding NFS mounted filesystems to avoid error reports.

8. Click theOptions button if you want to activate one of the followingoptions:

Only Enter the names of files to be backed up. You can usewildcards when selecting the filename. For example, youmay want to back up only*.doc files.

Skip Excludes files matching the entered file name criterion.You can use wildcards to the file name. For example, youmay want to skip all*.o files in the selected fileset.

9. Click OK to go back to theOmniBack II Filesystem Backupwindows.

10.To select additional filesets to back up, enter the full path name andfile/directory in the field to the left of theAdd button, and clickAdd.

To remove a file from theFiles and Directories field, select the file ordirectory and clickDelete.

11.Enter the name of the logical device to which the fileset will be backed upin theBackup Device field, or click the... button to select it from a list.

After you have configured one filesystem, you may set up the backupoptions or use the default backup options provided.

4-11

JLK�: M ; 1�<>{�B.|^6�9�4�}k~�[2_D�H��!x+Y�W U $ ��YQR-�l$ d "�&�t�&3#V"�Pn,�R�S�/�W�h

Selecting the Filesystem Backup Options

1. In theHP OmniBack II - Main window, select a Cell Server and clicktheBackup icon. TheHP OmniBack II Backup window opens.

2. SelectEdit →Create →OB II Datalist from the menu bar. TheOmniBack II Backup Editor appears.

3. Click Object →Add →Filesystem .

Figure 4-3 Selecting Filesystem Backup Options

4. In theOmniBack II Filesystem Backup window, click theFilesystem Backup Options button to display and set the backup optionsfor this object. These options override the session default options of the

4-12


datalist. See “Using Backup Options” on page4-26 for more details.ChooseDefault to set options back to default settings.

5. Click on theOK button to set options and return to theFilesystemBackup window.

6. Click on theOK button in theFilesystem Backup window to close thiswindow and return to theOmniBack II Editor window.

7. You can now set the options for the device where the backup will beperformed. Select the device in theDevices field in theOmniBack IIBackup Editor window and selectOptions →For SelectedDevice… to open theDevices Options window. See “Device Options”on page4-33 for more information.

8. Click on theOK button to set options.

Now you can save the datalist and run the backup interactively or schedulethe datalist. See “Starting a Backup of an Existing Datalist” on page4-20 or“Setting Up Scheduled Backups” on page4-41 for more information.

4-13

JLK�: M ; 1�<>{�B.|^6�9�4�}k~�[2_D�H��!x+Y�W U $ ��YQR>��R��mi�$ &�/-,�R�S�/�W�h

Configuring a Rawdisk Backup

A rawdisk backup is a high-speed backup where the system does not trackthe logical structure of the information stored on the disk. The hostname youenter provides the location of the sections. OmniBack II accesses thesections using the character device filename/dev/rdsk/ filename thatyou configure.

Scenarios in which a rawdisk backup is appropriate include:

• Full host backup intended for disaster recovery (full host restore).

• Host backup before a major software update.

• Duplication of a filesystem on another disk, if a direct disk-to-diskconnection is not possible (the two disks must be identical).

• Backup of a disk that contains databases.

e O ( f gWe recommend that you unmount a rawdisk before a rawdisk backup and mount itback later. You can use Pre- and Post- exec commands to do this.

Although a rawdisk backup does not distinguish between filesystem disksand database sections, OmniBack II still allows you to restore individualfiles from a rawdisk backup if the rawdisk holds an HP-UX HFS filesystem.

OmniBack II backs up rawdisk sections locally in the order you havespecified them in theRawdisk Sections list. OmniBack II also allows anetwork-wide rawdisk backup. However, for maximum performancerawdisk backup is best run locally.

The procedure for running a scheduled rawdisk backup involves the samefour main tasks you perform for a scheduled filesystem backup:


2. Selecting the rawdisk to be backed up.

3. Selecting backup options.


4-14

JLK�: M ; 1�<>{�B.|^6�9�4�}k~�[2_D�H�.��!x+Y�W U $ ��YQR-��R3�mi�$ &�/>,�R�S�/�W�h


Selecting Rawdisk Sections for Backup



3. SelectObject →Add→Rawdisk to open theOmniBack II RawdiskBackup window.

Figure 4-4 Configuring a Rawdisk Backup

4. In theHostname field, enter the hostname where the rawdisk is located

4-15

JLK�: M ; 1�<>{�B.|^6�9�4�}k~�[2_D�H��!x+Y�W U $ ��YQR>��R��mi�$ &�/-,�R�S�/�W�h

or click the... button to see a list of hosts.

5. In theDescription field, enter descriptive text for this backup object.Enter up to 80 characters including spaces. Note that you cannot leave thisfield blank.

6. In the field beside theAdd button, enter the disk sections that you wantbacked up. Enter the section character device name. On HP-UX systems,all character device files are listed in the/dev/rdsk directory.

e O ( f gIf you modify an object description in the datalist, the next backup for that object willbefull regardless of your backup mode selection.

7. Click onAdd to add the section to theRawdisk Sections list.

To delete a section from the list, highlight a section in the RawdiskSections list and clickDelete.

8. Enter the name of the logical device to which the rawdisk will be backedup in theBackup Device field, or click the... button to select from a list.

Selecting the Rawdisk Backup Options



3. SelectObject →Add→Rawdisk to open theOmniBack II RawdiskBackup window.

4. Click on theRawdisk Backup Options button to display and set thebackup options for this object. See “Using Backup Options” on page4-26for more information.

ChooseDefault to reset the options back to the default values.

5. Click on theOK button to set options and return to theBackup Editorwindow.

6. Next, set the options for the device where the backup will be performed.

4-16

JLK�: M ; 1�<>{�B.|^6�9�4�}k~�[2_D�H�.��!x+Y�W U $ ��YQR-��R3�mi�$ &�/>,�R�S�/�W�h

Select the device in theDevices field in theBackup Editor window.ChooseOptions →For Selected Device to open theDevicesOptions window.

See “Device Options” on page4-33 for more information.

7. Click on theOK button to set the device options and return to theOmniBack II Backup Editor window.

Now you can save the datalist and run the backup interactively or schedulethe datalist. See “Starting a Backup of an Existing Datalist” on page4-20 or“Setting Up Scheduled Backups” on page4-41 for more information.

4-17

JLK�: M ; 1�<>{�B.|^6�9�4�}k~�[2_D�H��!x+Y�W U $ ��YQb��&3#+,�R�S�/�W�h

Configuring Host Backup

Host backup is the dynamic backup of all filesystems configured on a host,as opposed to filesystem backup that includes only the static backup ofselected filesystems. See “Configuring a Filesystem Backup” for moreinformation.

This feature simplifies datalist configuration and improves backup coverageof hosts that often mount/dismount various disks. Host backup is very usefulfor dynamic environments with a large number of disks to be backed up.

e O ( f gThe -tree option for a HOST object has influence only on its mount point, whereasall other filesystems will be fully backed up.

e O ( f gSimilar functionality for rawdisk backup is not supported.

Occasionally check which disks are configured on a host and decide if youreally want to back up all disks configured. If you want to back up a smallnumber of selected filesystems, you are recommended to use the filesystembackup. For example, you add an additional mouintpoint/x to a host thatalready has mountponts/var, /home , and/tmp configured. If you run aHost Backup , the additional mountpoint/x will automatically be added tothe datalist at runtime.

The procedure for running a scheduled host backup involves four maintasks:


2. Selecting the host to be backed up.

3. Selecting the backup options.



4-18

JLK�: M ; 1�<>{�B.|^6�9�4�}k~�[2_D�H�.��!x+Y�W U $ ��YQb��&3#+,�R�S�/�W�h

Selecting a Host to Back up


2. SelectEdit →Create → OB II Datalist from the menu bar. TheOmniBack II Backup Editor appears.

3. SelectObject →Add→Host to open theOmniBack II Host Backupwindow.

Figure 4-5 Configuring Host Backup

4. Enter the hostname in theHostname field or click the... button to see alist of hosts.

5. Enter a description of this host in theDescription field.

4-19

JLK�: M ; 1�<>{�B.|^6�9�4�}k~�[2_D�H��!x+Y�W U $ ��YQb��&3#+,�R�S�/�W�h

6. Click theBrowse button to view and select mountpoints, directories, andfilesystems for backup.

7. ChooseExclude to exclude specific files and directories from the backup.Note that you must enter the full pathname of files. For example, you maywant to exclude the/tmp directory.

e O ( f gUse theExclude option to exclude the configuration and database directories/var/opt/omni/db and /etc/opt/omni from your host backups. Becausethe database is in use during the backup, a backup of the database will be incompleteand you will not be able to restore the database from this backup.We also recommend excluding mounted NFS (Network filesystems) to avoid errorreports.

8. Click theOptions button if you want to activate one of the followingoptions:

Only Enter the names of files to be backed up. You can usewildcards when selecting the filename. For example, youmay want to back up only*.doc files. In this case,*.doc files from all filesystems configured on the hostwill be backed up.

Skip Enter the names of files to be excluded from backup. Youcan use wildcards to the file name. For example, you maywant to skip all*.o files. In this case, the*.o files fromall filesystems configured on the host will be skippedfrom backup.

9. To select additional filesets to back up, enter the full path name andfile/directory in the field to the left of theAdd button, and clickAdd.

10.To remove a file from theFiles and Directories field, select the file ordirectory, and clickDelete.

11.Enter the name of the backup device that will be used to back up the hostor click the... button to see a list of devices.

12.Click theHost Backup Options button if you want to select backupoptions for the host.

13.Click OK to go back to theOmniBack II Backup Editor window.

14.To add additional hosts to the datalist, repeat the steps 3-11.

4-20

JLK�: M ; 1�<>{�B.|^6�9�4�}k~�[2_D�H�.W��$ ��Y ' �v#V" U R�S3#V$ �">,�R�S�/�W�h�&

Running Interactive Backups

Running an interactive backup means that the backup is performedimmediately and interactively.

• You can run an interactive backup of an existing datalist. See “PreviewingYour Backup” on page4-24 and "Starting an Interractive Backup of anExisting Datalist" below for instructions.

• You can create a temporary datalist for one backup only and run thebackup of this datalist. See “Creating a Temporary Datalist” on page4-23for instructions.

Starting a Backup of an Existing Datalist

If you want to run an interactive backup of an existing datalist, use thefollowing procedure:


2. In theHP OmniBack II - Backup window, highlight the datalist youwant to back up.

3. ChooseActions →Backup Selected... to open theOmniBack IIBackup Editor window.

4. ChooseActions →Start Backup .

4-21

JLK�: M ; 1�<>{�B.|^6�9�4�}k~�[2_D�H�.W��$ ��Y ' �!#%" U R�S�#%$ �">,�R�S�/�W�h�&

Figure 4-6 Running a Backup Session

The message field displays progress messages.

The maximum buffer for messages in theMessages field is limited bythe configurable parameterMAXGUIMSG. See “OmniBack II GlobalOptions File” on page7-13for more information. If the maximum bufferis exceeded, messages stop appearing in theMessage field and the errormessage “Output disabled” appears; however, the backup continues.

( ' c gBy pressing the right mouse button in the message area, you get a pop-upmenu where you can print, search for specific messages, clear up themessage area and so forth.

4-22


Status Messages

The messages fields use colors and status descriptions to help you identifythe progress and status of a backup.

The status is displayed for each object and datalist (session) separately.

Status of backup objects

The status of backup objects fifeld shows how each object in the datalist hasbeen backed up.

Completed All files have been backed up successfully without errors,there may be some warning messages. The field is green.

Completed/Errors Some files were not backed up successfully. The field isyellow.

Aborted The Disk Agent has been aborted for the followingreasons:

• The user has aborted backup.• The backup of all files has failed.• The Pre- or Post- exec script has failed.Usually files have not been backed up successfully. Thefield is red.

Failed OmniBack II could not run backup. There may besomething wrong with the configuration. No backupexists. The field is red.

Status of Devices

• Inactive/waiting.

• Running.

• Aborted.

• Completed.

4-23


Creating a Temporary Datalist

1. In theHP OmniBack II - Main window, choose theBackup icon. TheHP OmniBack II - Backup window appears.

2. From theHP OmniBack II - Backup window, select the datalist youwant to back up.

3. Click Action →Interactive Backup to open theOmniBack IIBackup Editor window.

4. UseObject →Add and select an object you want to add. Enter therequired information in the window.

Use the... button to get a list of possible options where available.

e O ( f gUse the Exclude option to exclude the configuration and database directories/var/opt/omni/db and/etc/opt/omni from your Full Filesystem backups.Because the database is in use during the backup, a backup of the database will beincomplete and you will not be able to restore the database from this backup.We alsorecommend excluding the NFS mounted filesystem to avoid error reports.

For an explanation of backup options available for a specific object, seethe online help or “Using Backup Options” on page4-27.

Repeat this procedure for as many objects as needed. You can modifybackup options for each specific object later if desired.

If you plan to use this datalist again, use theFile →Save to save it.

4-24


Previewing Your Backup

You can preview a selected backup session to see if you have properlyconfigured options and if the correct files are being backed up and to get anestimate of how much space will be used for data.

e O ( f gThe Pre- and Post- exec commands set for an object are executed during the previewof a backup. If these commands affect your operations, you may want to preview yourbackup first and then add the Pre- and Post- exec commands.

1. ChooseBackup from the mainHP OmniBack II window. TheHPOmniBack II - Backup window appears.

2. In theHP OmniBack II - Backup window, select the desired datalistfor the backup you want to preview.

3. In theOmniBack II Backup Editor selectActions →PreviewBackup .

4. Choose whether you want to preview a full or incremental backup ofselected objects. If this is the first time objects are backed up, the previewwill show a full backup.

Starting Your Backup

1. ChooseBackup from the mainHP OmniBack II window. TheHPOmniBack II - Backup window appears.

2. In theHP OmniBack II - Backup window, select the datalist you wantto back up.

3. In theOmniBack II Backup Editor , chooseActions →StartBackup .

4. In theRun Omniback II Backup window, choose whether you wantto run a full or incremental backup. If selected objects are backed up forthe first time, a full backup will be run automatically.

4-25


e O ( f gYou are advised to use the same backup optinions with full and incremental backups.At least use the optiontouch or no_touch with both types of backup. If you usethe no_touch option with full backup and thetouch option with incrementalbackup, the incremental backup will be the same as full backup.

The message fields display progress messages. The maximum buffer formessages in theMessages field is limited with the configurable parameterMAXGUIMSG. If the maximum buffer is exceeded, messages stop appearingin theMessages field and the error message “Output disabled” appears. See“OmniBack II Global Options File” on page7-13rffor instructions how tochange this value.

( ' c gBy pressing the right mouse button in the message area, you get a pop-upmenu where you can print, search for specific messages, clear up themessages field, and so forth.

TheMessages field provides colors and status descriptions to help youidentity the progress and status of the session. See the online help or “StatusMessages” on page4-22 for a description.

4-26

JLK�: M ; 1�<>{�B.|^6�9�4�}k~�[2_D�HX &�$ ��YQ,�R�S�/�W�hQOIh!#V$ ��&

Using Backup Options

HP OmniBack II offers a set of comprehensive backup options allowing finetuning of a backup. All options have default values which are appropriate formost cases.

Figure 4-7 Selecting Backup Options

4-27

JLK�: M ; 1�<>{�B.|^6�9�4�}k~�[2_D�HX &�$ ��YQ,�R�S�/�W�hQOCh!#%$ ��&

For a Datalist

Pre- exec commandsPost- exec commands

load balancing

reconnect broken connections

protection

These options are datalist specific and override session default options.

To set these options for a specific datalist, select the datalist and chooseOptions → For Selected Datalist from theOmniBack II BackupEditor window.

Session Defaults for Filesystem Objects

compressencryptprivate/publicreport level (warning, minor, major, critical)display statistical informationlock files during backupdo not preserve time attributesignore hard linkspre- exec commandpost- exec commandprotectionlog files/directories to database

backup files of size

Default backup options for filesystem objects in a datalist. These optionsare applied each time a filesystem is being backed up. You could, forexample, set theCompress option for all filesystem objects in thedatalist.

To set these options selectOptions → Session Defaults→ ForFilesystem Objects from theOmniBack II Backup Editor window.

4-28


Session Defaults for Rawdisk Objects

compressencryptprivate/publicreport level (warning, minor, major, critical)pre- exec commandpost- exec commandprotection

Default backup options for rawdisk objects in a datalist. These optionsare applied each time a rawdisk is backed up. You could, for example, settheCompress option for all rawdisk objects in the datalist.

To set these options selectOptions → Session Defaults→ For RawdiskObjects from theOmniBack II Backup Editor window.

For Selected Objects

Backup options for each specific object in a datalist. These optionsoverride the session default options and are applied each time a specificobject is backed up. You could, for example, specify that one object in adatalist does not use theCompress option because the system is too slowand the object contains only a small amount of data.

To set these options select the object in theOmniBack II Backupeditor window and chooseOptions → For Selected Object….

For Selected Device…

CRC CheckConcurrencyMedia PoolPrealloc List

To set these options, select the device in theOmniBack II Backupeditor window and chooseOptions → For Selected Device….

4-29


Description of Backup Options

Compress

Data compression lets you write data to the media in a compressed format.Compression reduces the number of media required for a backup andimproves backup performance. By default, the compression option is set toOFF. When software compression is turned on, OmniBack II compresses thedata on the host where the Disk Agent is running before it sends it over thenetwork. This reduces data traffic over the network. Depending on the typeof data, compression ranges from 30% to 70% and is based on the Lempel-Ziv 4.3 compression algorithm which is completely compatible with thestandard Unixcompress utility. OmniBack II provides you with the API(Application Programming Interface) which is used by the Disk Agent tointerface with the compression module. This allows you to substitute yourown special-purpose compression module for even higher rates ofcompression. OmniBack II also supports devices which allow for hardwaredata compression.

e O ( f gIn case of configuring two logical devices that actually point to one physical device,one configured to back up compressed data and the other uncompressed data, you areadvised to specify theLock Name in the advanced options for the two logicaldevices. Both logical devices must have the same lock name. Lock Name is the namewhich OmniBack II recognizes in order to lock the device before starting backup andrestore sessions.

e O ( f gMost modern backup devices provide built-in hardware compression that you canconfigure when adding a device to the host. See your device’s manual forinstructions. In this case, do not use the compress option of OmniBack II, sincedouble compression only decreases performance without giving better compressionresults.

Encrypt

Open Systems and public networking make data security in large enterprisesessential. OmniBack II lets you encrypt file and rawdisk data so that itbecomes unreadable. Data is encrypted before it is transferred over thenetwork and before it is written to media. By default, the encrypt option isset to OFF. OmniBack II offers a simple built-in XOR algorithm

4-30


implemented in a shared "C" program library. Since OmniBack II providesthe API used by the Disk Agent to interface with the encryption module, youcan substitute your own internal encryption algorithms for greater security.Do this by writing your own encryption module. Compile the encryptionmodule into a library and substitute it for the default OmniBack II library.

You must generate your own encryption module and key as well as a methodof distributing the keys. See “Customizing the Encryption Algorithm” onpage7-45.

Public/Private

This option lets you set access rights for restoring the data you back up. If afilesystem is backed up with thePrivate option, it can be restored only byyou or the system administrator.

By default, this option is set toPrivate. Setting the option toPublic letsanyone restore your data.

Backup Files of Size

Use this menu button to specify the size of files to be backed up. You canbackup files of All Sizes (default), files Bigger than, Smaller than, or withinthe specified size Range in KB.

Load Balancing

OmniBack II provides a dynamic connection of backup objects to availabledevices. Devices will be accessed in the order specified in the datalist. Setthis option ON and specify the number of logical devices in the two textinput boxes; the numbers represent minimum and maximum number ofavailable logical devices.

See “Load Balancing” on page4-36 for more information.

Reconnect Broken Connection

In the event of short-term network problems, OmniBack will reconnectBackup Session Manager and Disk or Media Agents. The reconnectfunctionality works only for network problemsduring backup.

This is, for example, the case when you have the Session Manager on oneLAN and the Disk and Media Agents on another LAN and between thesetwo LANs the connection is unreliable (WAN connections).

4-31


See “Reconnect of Broken Connections” on page4-40 for more information.

Report Level

This option defines the level of errors that will be reported during a backupsession. Setting a level means errors of this and higher levels are reported.For example, by setting theMinor button ON, all errors graded asminor ,major , andcritical are reported in theMessages field. By default the levelis set toWarning. Messages keyed asNormal always appear in theMessages field. See “Managing the Growth of the Database” onpage8-4for a description how this option influences the OmniBack IIdatabase.

Log to Database

OmniBack II provides three levels of the amount of details on files anddirectories stored in the database.

Log All This is the default option. All backed up files are loggedto the database. This complete information allows you tosearch for backed up files and allows OmniBack II toquickly position on the tape when restoring a specific file.However, this information may take a lot of space if thereare many files.

Log Directories Details on directories only are stored in the database. Thisdisables the search feature during restore and you willonly be able to browse directories. However, OmniBackII still performs fast positioning because a file is locatedon the tape near the directory where it actually resides.This option is suitable for filesystems with many auto-generated files, such as news and mail systems.

No Log No details on files or directories are logged in thedatabase. You will not be able to search and browse filesand directories. The restore will take longer becauseOmniBack II cannot fast position on the tape but will readfrom the start of the backup.

See “Managing the Growth of the Database” on page8-4 for a descriptionhow this option influences the OmniBack II database.

4-32


Lock Files During Backup

This option defines how files are handled if the files are being used during abackup session. If set to ON, files are locked during the backup session,preventing the files from being modified during the backup. The defaultsetting is OFF.

Do Not Preserve Access Time Attributes

Whenever a file is opened (read, locked, etc.), the access time of the file ischanged. During backup each file in the specified fileset is opened, locked,and read. When this option is set to OFF (default), the access time attributesremain as they were before backup (they are reset to their original values).When you set this option to ON, the access time values are changed to themoment of backup.

Ignore hard links

If this option is ON, OmniBack II will back up the entire file contents foreach hard link. Causes OmniBack II to traverse the filesystem tree onlyonce, thus significantly speeding up the backup process. Use this optionwhen there are no hard links in your directory. When this option is set to ON,OmniBack II cannot estimate the size of the backup or display thepercentage of the backup finished. The default is OFF.

Pre- and Post-Exec

The Pre-Exec option allows you to enter a command to be executed beforethe backup of a datalist or an object is initiated.

The Post-Exec option allows you to enter a command to be executed afterthe backup of a datalist or an object has completed. You can customize thepre- and post-exec commands to your environment.

See “Using Pre- and Post- Exec Commands” on page7-6 for moreinformation.

4-33


Protection

This option enables you to set periods of protection for the data you back upto prevent the backup data from being overwritten for the specified period.The default value isPermanent.

The backup protections are:

• None-Provides no protection. Data can be overwritten if the medium it isstored on is reused.

• Until -Data on the medium cannot be overwritten until a specified date.You enter the year, month, and day. Protection for the data will stop atnoon of the entered day. For example, if you enter in the entry fieldprovided the date 97/8/22, the data will be protected until noon, August22, 1997.

• Days-Data on the medium cannot be overwritten for the number of daysspecified. For example, if you set the protection for 2 days, and the currentbackup starts at 20:00 (8:00 PM) on Wednesday, the data will be protecteduntil Friday at 20:00.

• Weeks-Data on the medium cannot be overwritten for the number ofweeks specified. For example, if you set the protection for 1 week, and thecurrent backup starts at 10:00 on Wednesday, the data will be protecteduntil 10:00 the following Wednesday.

• Permanent-the data is permanently protected from being overwritten.

You can set the protection independently for backed up data and for backupinformation about this data in the OmniBack II database. See “Managing theGrowth of the Database” on page8-4 for more information.

Device Options

Set these options for the selected backup destination device.

CRC Check

Set this option ON to have OmniBack II calculate the CRC (cycleredundancy check) when a backup is run. The CRC check is an enhancedchecksum function that lets you confirm whether or not data has been

4-34


written correctly to the medium. To verify media written with the CRCoption, use the OmniBack II commandomniver in the command lineinterface.

Concurrency

Concurrency allows more than one Disk Agent (up to five) to write to onebackup device. This helps OmniBack II keep the device streaming when itcan accept data faster than a disk agent can send it (for DDS devices, thisvalue is 2). OmniBack II provides default values for all supported devices.

Media Pool

This option selects the media pool where the backup will be done. If notdefined, a default pool will be used.

Prealloc List

The Prealloc list is a subset of media from the media pool that OmniBack IIwill use for backup. This list also determines the order in which the mediawill be used. This order is important if you have selected theStrict mediaallocation policy when you configured the logical device. In this case,OmniBack II expects the sequence of the media in the device to correspondwith that specified in thePrealloc list . If the media is not available inthis sequence, OmniBack II issues a mount request.

Transferring Backup Ownership

OmniBack II lets you change the owner of a backup session. For example, assystem administrator you may create a datalist and back up certain data forother employees. Changing the ownership of a backup session lets anotherperson start a backup session for objects he or she does not own.

Changing the owner works only if the datalist is saved. If the datalist ischanged but not saved, the backup is treated as an interactive backup and theowner is not changed. This could result in a different kind of backup than

4-35


expected. For example, if you interactively start an incremental backup of adatalist and you are not the owner of the full backup, you will get anotherfull backup instead of the incremental.

To transfer ownership, follow the steps below:


2. In theHP OmniBack II Backup window, select the datalist the ownerof which you want to change.

3. From the menu, selectFile →Change Ownership to open theSessionOwnership window.

4. In theSession Ownership window, enter the user name, group, andhost name of the user you want to transfer ownership to. No spaces areallowed between characters.

Figure 4-8 Changing the Owner of a Session

The default ownership of the backup session and objects remains with theoriginal initiator of the backup session. See “Configuring User Classes andUsers” on page3-36 for more detals.

4-36

JLK�: M ; 1�<>{�B.|^6�9�4�}k~�[2_D�Hy��lR�iQ,�R�d R��S�$ ��Y

Load Balancing

The dynamic datalist/barlist layout in OmniBack II allows a dynamicconnection of backup objects to available devices. If you run a backupsession with theLoad Balancing option, OmniBack II will automaticallybackup configured backup objects to available devices.

Load Balancing Backup

Backup performed with theLoad Balancing option is suitable in thefollowing cases:

• When you want to back up a large number of objects.

• When objects are backed up on large library (exchanger) devices.

• When you do not need to know on which media objects will be backed up.

File System Backup - No Load Balancing

Backup without theLoad Balancing option is recommended in thefollowing cases:

• When you want to back up a small number ofobjects.

• When objects are backed up on simple devices, such as DDS.

• When you want to manually select the devices on which objects will bebacked up.

• When you want to know on which medium/media objects will be backedup.

OmniBack II will not backup objects to devices that:

1. Failed during a backup of another object.

2. Stopped during a backup of another object.

3. Are in theMount Request state.

4. Can not be started at all.

4-37

JLK�: M ; 1�<>{�B.|^6�9�4�}k~�[2_D�Hy��R�im,.R�d R��S�$ ��Y

e O ( f gOmniBack does not automatically backup larger backup objects to devices with morecapacity. Therefore, if you want to have a large backup object backed up on onemedium, perform the backup without theLoad Balancing option. In this case,you must manually select the device on which a large object is backed up. In this way,you can easily locate and restore the backup object.

TheLoad Balancing option redirects backup objects from failed devicesto available devices (devices that are not used by another OmniBack IIsession and have the license to be started). Backup objects that are alreadypartially written to media when a device fails cannot be redirected. Thebackup of such objects must be repeated. In this case, use theRestartUnsuccessful Backup from theOmniBack II Session Monitor .

e O ( f gWhen you run backup with the Load Balancing option, OmniBack IIwill use devices in the order they are specified in the dynamic datalist. Theorder of devices specified in the dynamic datalist is of great importance.Make sure you configure faster and more reliable devices in the initialpositions of the device list.

e O ( f gIf devices that are not reliable are configured in initial positions of the device list,backup sessions may more often result in mount requests or even theabortedstatus.

Configuring Backup with Load Balancing

To back up a datalist/barlist with theLoad Balancing option, follow thesesteps:

1. In theHP OmniBack II - Main window, select theBackup icon. TheHP OmniBack II-Backup window is displayed.

2. In HP OmniBack II-Backup window, selectEdit →Create →OB IIDatalist. TheHP OmniBack II Backup Editor window isdisplayed.

3. In TheOmniBack II Backup Editor selectOptions →ForDatalist .

4. TheHP OmniBack II-Session Options window is displayed where

4-38

JLK�: M ; 1�<>{�B.|^6�9�4�}k~�[2_D�Hy��lR�iQ,�R�d R��S�$ ��Y

you can select theLoad Balancing option for the datalistand the valueof the following dynamic keywords:

• MIN represents the required mininum number of available logicaldevices (devices that are not being used by another OmniBack IIprocess and have the license to be started) for starting the session. Iffewer logical devices are available than specified under theMINkeyword, the session will queue.

• MAX represents the maximum number of available logical devices thatcan be used at the same time.

Figure 4-9 Session Options window

For example,MIN "3" andMAX "4" in a datalist with six logical devicesmeans that session will start when at least three devices are available andthat a maximum of four devices can be used at the same time. The remaining2 devices will be used if the running devices fail.

4-39

JLK�: M ; 1�<>{�B.|^6�9�4�}k~�[2_D�Hy��R�im,.R�d R��S�$ ��Y

e O ( f gIf fewer devices are listed in the datalist/barlist than specified in theMIN field, thevalue ofMIN will be automatically decreased to the number of devices specified inthe datalist.The default value of load balancing isMIN 1 , MAX 5.

When OmniBack II starts a backup device, it first backs up local objects(located on the same host as the device). If there are no local objects, thedevice will back up remote objects (not located on the host where the deviceis located). In this case, OmniBack II will select remote objects on the hostwith the fewest running Disk Agents. The main purpose of this function is toprevent excessive use of the network and prevent overloading of hosts.

e O ( f gIf a device goes into a mount request in the middle of a backup, the Disk Agentsconnected to the device will NOT be reconnected to another running device. Theywill wait for the mount request confirmation.If a device fails in the middle of a backup, the Disk Agents connected to the devicewill be aborted. The user will have to manually restart the backup that has failed.

4-40

JLK�: M ; 1�<>{�B.|^6�9�4�}k~�[2_D�H�."�S��"�S�#+� Z , U ��/�"��Q��"�S3#V$ ��&

Reconnect of Broken Connections

In case of short-term network problems, OmniBack will reconnect theBackup Session Manager and Disk or Media Agents. The reconnectfunctionality works only for network problemsduring the backup.

This is, for example, the case when you have the Session Manager on oneLAN and the Disk and Media Agents on another LAN and between thesetwo LANs the connection is unreliable (WAN connections).

Modifying Reconnect Parameters

The reconnect parameters can be modified by the following two enviromentvariables:

• OB2RECONNECT_RETRY - how long to try reconnecting after a socketconnection has been broke (default is 1200 secs). In other words, theWAN line between BSM and agents cannot be down more thanOB2RECONNECT_RETRY secs.

• OB2RECONNECT_ACK - how long to wait for the message ofacknowledgement (default 600 secs). In other words, if the agent does notget an acknowledgement inOB2RECONNECT_ACK secs, then it willassume that the socket connection is no longer valid.

You must edit the/opt/omni/.omnirc file (on HP-UX 10.x) or/usr/omni/.omnirc file (on HP-UX 9.0x) on the remote client host inorder to change reconnect parameters.

4-41

JLK�: M ; 1�<>{�B.|^6�9�4�}k~�[2_D�HsL"3#7#V$ ��Y X hQsLS�*�"�i�W�d "�iQ,�R�S�/�W�h�&

Setting Up Scheduled Backups

By setting up a schedule for a datalist, you can automate your backups to runperiodically at times of low system usage. With the scheduler, the backupsyou set up will run on the days and at the times you specify without yourattendance as long as the devices and media are properly set. You can alsospecify the dates (holidays) to be skipped. See “Skipping Backups DuringHolidays” on page4-47 for instructions.

When a backup session is started, OmniBack II tries to locate all theresources needed (for example, the correct number of licenses, the devices,and access rights to the database). If any of these resources are unavailable,the session is marked as "queued." OmniBack II then tries again to get theresource once a minute until the timeout is reached. When the resourcesbecome available, one of queued sessions is randomly selected and started.(Note that the sessions arenot started in sequential order).

If OmniBack II cannot get the necessary resources within the allotted time,the session fails. The timeout is controlled by two parameters in the globaloptions file. See “Managing the Growth of the Database” on page8-4 formore information.

You can set up a schedule using the GUI.

As soon as you have created and saved the schedule for a configured datalist,the schedule is activated and OmniBack II will check the schedule. Noadditional activation step is required.

As the backup is running, theOmniBack II Backup Monitor windowmay issue mount prompts requesting media be mounted. If no one will bepresent to respond to mount prompts at the times chosen to run a backup, setup mount prompt scripts for automatic mount prompt handling. See the“Automating Mount Prompt Handling” on page7-3 for more information.

4-42

JLK�: M ; 1�<>{�B.|^6�9�4�}k~�[2_D�HsL"3#7#V$ ��Y X hQsLS�*l"�i�W�d "�iQ,�R�S�/�W�h�&

e O ( f gWhen more than 5 sessions are scheduled at the same time, the exceess sessions arequeued. You can change this number by modifying theMaxBSessions variable inthe global options file.

Setting up Backup Schedules

There are two general methods of setting the start dates and times for abackup:

• Method 1: By specifying the exact start date(s) and time(s).

• Method 2: By using regular intervals.

In Method 2, OmniBack II offers you two ways to specify the intervalsbetween backups.

• Predefined intervals.

• Custom intervals.

In all cases, you can schedule backups for up to a year in advance.

Make sure the cell you are setting the schedule for is within one time zone. Ifthe cell is spread over more than one time zone, OmniBack II will use thetime from the Cell Server.

4-43


Setting up a Backup for a Specified Date

Figure 4-10 Backup Scheduler for Setting Specific Dates

The following section explains how to do a backup on a specific date.


2. In theHP OmniBack II Backup window, highlight a datalist to bescheduled.

3. SelectEdit →Change Schedule from the menu bar. TheSchedulerwindow opens.

4. In theScheduler window, select theView pulldown menu and choosea month (January-December).

5. Click on the date you want to run the backup on in theSchedulerwindow to open theDaily Edit window.

6. Choose a Backup Type (Full or Incremental).

4-44


7. Select the starting time for your backup session. You can run a backup asfrequently as every fifteen minutes. OmniBack II issues error messages ifyou select conflicting backup dates or times.

The type of backup is indicated by the colors defined in theLegend at thebottom of theScheduler window.

Figure 4-11 Backup Scheduler for Setting Periodical Backup

For example, to set up an incremental backup on October 4th, at 3:30, followthese steps:

1. ChooseOctober from theView menu.

2. Select day4.

3. Select Backup TypeIncremental.

4. Click on start time3:30.

5. Click theOK button. The main scheduler window will reappear with thedate you set up highlighted in blue and theLegend color for anincremental backup.

6. SelectFile → Save from the menu bar.

4-45


Selecting a Predefined Periodic Schedule

You can set up a schedule based on the frequency of the backup by choosinga predefined or custom schedule (see the next section). You can use thepredefined schedule as a template to create your own customized schedules.

1. In theHP OmniBack II - Main backup window, click theBackup iconto open theHP OmniBack II-Backup window.

2. In theHP OmniBack II-Backup window, highlight a datalist to bescheduled.

3. SelectEdit →Change Schedule from the menu bar. TheSchedulerwindow opens.

4. In theScheduler window, selectEdit →Predef ined... .

5. Choose one of the predefined schedules. They are as follows:

Daily intensive

OmniBack II runs a full backup at midnight, and two additional incrementalbackups at 12:00 and 18:00 every day. This type of backup is intended fordatabase transaction servers and similar environments with intensive backuprequirements.

Daily full

OmniBack II runs a full backup every day at 21:00. This is intended forbackups of single workstations or servers.

Weekly full

OmniBack II runs a full backup every Friday and Incr-1 backups every dayat 21:00 from Monday to Friday. This is intended for small workgroupenvironments.

Fortnightly full

OmniBack II runs a full backup every second Friday. Between thesebackups, OmniBack II runs Incr-1 backups every Monday to Thursday, all at21:00.

4-46


Monthly full

OmniBack II runs a full backup on the 1st of every month, Incr-1 backupevery week, and an incremental every other day. This is intended forrelatively static environments.

Setting up a Custom Periodic Schedule

1. In theHP OmniBack II - Main window, click theBackup icon to opentheHP OmniBack II-Backup window.


3. SelectEdit → Change Schedule from the menu bar. TheSchedulerwindow opens.

4. In theScheduler window, selectEdit → Periodic... from the pull-down menu. TheScheduler-Periodic Tagging window opens.

5. In theScheduler-Periodic Tagging window, select a Backup Type(Full or Incremental 0-9).

6. Choose aTime Cycle (every, every 2nd, etc).

7. Choose aTime Unit (day, month, etc.).

8. Enter theBackup Time using the 24-hour clock system.

9. Click Apply to apply the schedule. If there are scheduling conflicts,OmniBack II will notify you with a message so you can modify theschedule.

4-47


Editing a Daily or Monthly Backup Schedule

Clearing a Schedule

To eliminate a schedule that you have already set up, select theEdit →Clear → All in theScheduler window.

Note that when you clear a schedule, you clear all the schedule settings of aspecified mode (full, incremental, or all) for the current year.

Undoing the Clear

To undo the clearing of a schedule, clickEdit → Undo in theSchedulerwindow.

Changing the Start Date

To change the start date, simply follow the procedure for setting up a backupfor a specific date. See “Setting up a Backup for a Specified Date” onpage4-43.

Skipping Backups During Holidays

HP OmniBack II uses the/etc/opt/omni/Holidays file to enable you toset up a holiday backup schedule. This file must be created before you canuse this feature. This file uses the same syntax as the standard UNIXholidays file.

To skip running a backup during holidays, click theHoliday button in theScheduler window. This instructs the scheduler to exclude from thecurrent schedule all dates found in theHolidays file. For example, if thedate January 1 is registered as a holiday, OmniBack II will not back up onthat date. If you have scheduled a full backup for January 1st and anincremental for January 2nd, OmniBack II will skip running the full backupon January 1st but will run the incremental backup scheduled for January2nd.

4-48


Overriding Scheduled Backup Options

Use theOverride option if you want to run backups of certain datalists withdifferent protection policies, for example, if you may want to apply differentprotection policies to different levels of backup (full, incremental, etc.). TheOverride option frees you from having to create separate datalists fordifferent data protection schemes. To change the protection, select thedatalist you want to modify.



3. ChooseEdit → Change Schedule . TheScheduler window appears.

4. ChooseOptions and select a backup type. TheScheduler Optionwindow appears. In our example, we choseFull .

5. Click theProtection button to choose the protection period you want toapply to the scheduled backup. In our example, the full backups of thisdatalist will be protected for the selected period.

6. In the date entry fields, enter the days, weeks, or date until which you wantthe data protected and click theOK button to register the settings. Thewindow disappears and returns you to theScheduler window.

To implement a schedule protection override using the command line, entertheomnib command with the -datalist and-protect options and thenumber of days, weeks, etc.

For example, enter:omnib -datalist datalistname -protectweeks 2 . For more information, see the manpages for theomnib command.

4-49


To Undo an Override



3. ChooseEdit → Change Schedule . TheScheduler window appears.

4. ChooseOptions and select a backup type. In our example, we choseFull .

5. TheScheduler - Full Options window appears where we select theDefault option.This will cause OmniBack II to use the protectionoriginally specified in the datalist.

4-50


5-1

5

Restoring Data

5-2

�.D�[256�47; 1�<-��K325K

In This Chapter

This chapter describes how to use the Graphical User Interface (GUI) to:

• restore single files and directories from a filesystem backup

• restore and search for files using the new simple restore GUI

• restore single files from a rawdisk backup

• restore disk sections from a rawdisk backup

The HP OmniBack II GUI is designed to make it easy to locate and restorefiles and disks backed up with OmniBack II. It is designed to guide youthrough the restore process, allowing you to select from lists wheneverpossible. OmniBack II also offers a command-line interface for restores. Formore information on the command-line interface for restores, see theomnirmanpage.

5-3

��D�[256�47; 1�<-��K325K��"�&3#V� U ">OL �" U �$ "3�

Restore Overview

Basically, restoring data consists of providing the following information:

FROM From which backup session to restore

WHAT What files, directories, or disks to restore

HOW Which restore options are to be used

TO Where the files, directories, and disks are to be restored

OmniBack II helps you provide this information by guiding you through therestore process.

OmniBack II provides three types of restores, depending on how the datawas backed up:

• File restore from a filesystem backup

• File restore from a rawdisk backup

• Rawdisk restore from a rawdisk backup

A filesystem backup includes the logical structure of the data. Informationabout this logical structure as well as the data are written to the mediamanagement database. A rawdisk backup does not include informationabout the structure of the data; therefore, the media management databasehas no information about the individual files in the backup. Thus, the backuptype influences your ability to locate and restore individual files. For thisreason, each of these restore types is explained separately in the followingsections.

5-4

�.D�[256�47; 1�<-��K325K�."�&3#V� U $ ��YQ��$ d "�& ZVU ��PnR-��$ d "�&3t�&3#V"�Pn,�R�S�/�W�h

Restoring Files from a Filesystem Backup

The Media Management database of HP OmniBack II tracks the followinginformation about each backup performed using OmniBack II:

• date and time of each backup

• type of backup

• directories, files, and disks that were backed up

• file positions on the media

• messages resulting from a backup or restore session

• expiration date for the protection of the data contained on the backupmedia

OmniBack II uses this information to help you locate and restore data. Tolocate and restore files and directories from a filesystem backup, followthese steps:

1. In theOmniBack II Main window, select a cell server and click theRestore icon to open theOmniBack II Restore window.

2. In theOmniBack II Restore window, double-click the backup objectcontaining your file to open theFileSystem Restore Dialogwindow.

3. In theFileSystem Restore Dialog window, specify the files ordirectories for restore. You can optionally specify the fileset restoreoptions (after you have specified the version of a file or directory) andrestore session options.

4. Activate and monitor the restore process.

Changing the View of Backup Objects

OmniBack II offers two types of views of backup objects:

5-5

��D�[256�47; 1�<-��K325K��"�&�#%� U $ ��YQ��$ d "�& ZVU ��PnR-�l$ d "�&�t�&3#V"�Pn,�R�S�/�W�h

Browser Offers a graphical representation of backup objects. Thisview is suitable for backups with a smaller number ofbackup objects.

List Offers a text list of backup objects. This view is suitablefor backups with a larger number of backup objects.

To change the view, perform the following steps:


2. In theOmniBack II Restore window, chooseView from the menu andselect an appropriate view.

Selecting the Backup Object

To select objects for restore, follow these steps:


2. A list of backup objects is displayed in theOmniBack II Restorewindow. Double-click the backup object that contains the files anddirectories you want to restore to open theFileSystem RestoreDialog window opens.

3. In theFileSystem Restore Dialog window, specify the files anddirectories for restore. Follow the online help instructions.

5-6


Selecting the Files to Restore

Figure 5-1 Browsing Files

To select the files and directories for restore, follow these steps:


2. In theOmniBack II Restore window, double-click the backup objectthat contains the files and directories you want to restore. TheFileSystem Restore Summary window opens.

5-7


3. In theFileSystem Restore Summary window, specify the files anddirectories for restore. Follow the online help instructions.

e O ( f gWhen you click on a file/directory for restore, you automatically select the lastversion of the file/directory. With a right mouse button click on a file/directory, youcan select a specific version of a file/directory.

Browsing Files to Restore

e O ( f gIf you have chosen theNo log backup options (no details on backed-up files anddirectories are stored in the database) or you have purged detail catalogs from thedatabase, you will not be able to use the browse functionality. Instead, OmniBack IIopens theFilesystem Restore Dialog window where you type in the filesyou want to restore.See “Description of Backup Options” on page4-29 and “Managing the Growth of theDatabase” on page8-4 for more information.

OmniBack II allows you to browse the list of files and directories you canrestore:

• Double-click on a directory in theFileSystem Restore Summarywindow to expand that directory, that is, opens other directories and fileson that path. You can perform the same task by simply clicking + buttonbeside directory name.

• Double-clicking a second time on the directory above contracts thedirectory, that is, closes directories and files on that path. You can do thesame by clicking - button beside directory name.

Shaded directories can only be expanded or contracted but not selectedfor restore; this is because only a subtree of the directory was backed up,for example, the/users directory will be shaded if you only did abackup of/users/mike/myf iles .

5-8


Selecting a File/Directory Version

Generally, you have more than one backup containing the files you want torestore, that is, you have several versions of a file or directory to choose torestore from.

To Restore the Last Version of a Lost File

If a file has been lost, you will probably want to restore the most recent copyof that file. To restore the most recent copy of a lost file, follow these steps:

1. In theOmniBack II Main window, select a cell server and click on theRestore icon to open theOmniBack II Restore window.

2. In theOmniBack II Restore window, double-click the backup objectthat contains the files and directories you want to restore. TheFileSystem Restore Dialog window opens.

3. In theFileSystem Restore Dialog window, click on the requiredfile/directory to display a cascading menu of files and directories.

4. Click a file/directory to select its last version for restore.

5. Repeat the process to select further files or directories.

6. To deselect a file/directory, click it once again.

To Restore an Older Version of a File

If a file has been corrupted, you may want to restore an older version of thefile. In this case, recover the file from a backup containing an uncorruptedversion of the file. To select an older backup containing this file, proceed asfollows:


2. In theOmniBack II Restore window, double-click the backup object

5-9


that contains the files and directories you want to restore. TheFileSystem Restore Dialog window opens.

3. In theFileSystem Restore Dialog window, click on the requiredfile/directory to display a cascading menu of files and directories.

4. Click the right mouse button on a file/directory whose version you wantto select.

5. Click Select Version from the menu and in theVersion of window,select the desired version.

6. Repeat the process to select additional files or directories.

7. To deselect a file/directory, click the file/directory once again.

Specifying Fileset Restore Options

The fileset restore options apply to the specific files or directories selectedfor restore in theFileSystem Restore Dialog window.

To specify fileset restore options, follow these steps:



3. After you have selected a version of the file/directory for restore, choosetheRestore summary/details window to open theFileSystem RestoreSummary window.

4. Highlight the selected version of a file/directory in theFileSystemRestore Summary window and chooseOptions to open theFileRestore Options window. Enter the restore options you want to applyto the selected files or directories. See below for a description of availableoptions.

5-10


Figure 5-2 Restore Options

Repeat the procedure to add options to filesets as needed.

Restore As Restores the file or directory as the pathnamethat you enter in the field to the right of thebutton. The destination pathname can be anexisting pathname or a new pathname. Thisenables you to rename objects as you restorethem

Restore Into Restores the Fileset into the pathname that youenter in the field to the right of the button. Thisappends the fileset to the pathname. Thedestination pathname must be an existingpathname.

Match Restores only files matching the enter file namecriterion. You can use wildcards to specify the

5-11


file name.

Exclude Excludes the files and directories which youenter in the field from the restore. Enter the fullpathname of the file. Wildcards are not allowed.For example, you may want to exclude the/tmp directory.

Skip Excludes files matching the entered file namecriterion. You can use wildcards to specify thefile name. For example, you may want to skipall *.o files in the selected fileset.

5-12


Selecting Options for the Restore Session

These options apply to the whole restore session and all files (directories)restored with one session.



3. ChooseOptions in theRestore Dialog window to open theRestoreOptions window.

4. Enter the restore options you want to apply to the selected files ordirectories. See below for a description of available options

Target Hostname By default, files are restored to their originalhosts. You may want to choose some other hostin this field.

Merge Merges existing files with files from thebackup. If a file on the disk is newer than thebacked-up version, the newer file is kept. If afile on the disk is older than the backed-upversion, the file is overwritten with the newversion from the backup. The default is ON.

Overwrite Replaces the files and directories on the diskwith the version of the files and directories onthe media. The default is OFF.

No Overwrite Preserves the files and directories on the disk, ifthey exist. The version of these files anddirectories on the media is not restored. Thedefault is OFF.

Restore ProtectionAttributes Preserves the original protection attributes of

each restored file. When set to OFF, OmniBack

5-13


II applies the protection attributes of the currentrestore session. The default is ON.

Restore Time Attributes Preserves the time attribute values of eachrestored file. When set to OFF, OmniBack IIsets the time attributes of the restored objects tothe current date and time. The default is ON.

Restore Sparse Files Restores sparse files in their original form. Thisis important because sparse files can consumeadditional disk space unless they are restored intheir original form. The default is OFF.

Lock Files DuringRestore Denies access to files during the restore. By

default the option is set to OFF and the files arenot locked.

Omit Deleted Files Deletes files that were removed between a fulland incremental backup. This option is usefulwhen you restore a complete directory or diskand want to have only those files which were inthe directory or disk when the incrementalbackup was done. The default is OFF.

Move Busy Files This option is used with the Omit Deleted Filesor Overwrite options. If the file is busy duringrestore, OmniBack II cannot restore the file.This option moves the busy filefilename to#filename (with a hash in front of the filename.)

List Restored Files When set to ON, OmniBack II displays thenames of the files and directories in theMessages section of theRestore Monitorwindow as the objects are being restored. Thedefault is OFF.

Display StatisticalInformation When set to ON, OmniBack II displays detailed

statistical information about the restore session.The default is OFF.

5-14


Pre- exec command A Pre- exec command is executed as soon asthe Disk Agent is started, but before any restoreprocessing has started. See “Using Pre- andPost- Exec Commands” on page7-6 for moreinformation.

Post- exec command A Post- exec command is executed just beforethe Disk Agent terminates. See “Using Pre- andPost- Exec Commands” on page7-6 for moreinformation.

5-15


Activating and Monitoring the Restore

Before you actually run a restore session, you may want to preview it.

TheRestore Monitor window also allows you to change to a differentlogical device for restore or to preview a restore session.

Figure 5-3 Monitoring the Restore Session

To activate the restore, follow these steps:


2. In theOmniBack II Restore window, double-click the backup objectthat contains the files and directories you want to restore. The

5-16


FileSystem Restore Dialog window opens.

3. After you have entered and selected all the requested information neededfor the restore in theFilesystem Restore Dialog window, click theOK button. TheRestore Monitor window appears with the devicestatus indicating theInactive/Waiting status and the session indicatingPending.

4. Choose:

• Actions → Preview Restore to preview the restore session.

• Actions → Start Restore to start the restore session.

5. Select theNetwork Load .

Setting this option toLow reduces the load on the network when runningOmniBack II. This prevents the data transmission for restore fromblocking the network for other users but increases the time required forthe restore.

6. SelectReport Level .

By default all messages are displayed - thewarning level. If you selectany other levels, only messages with higher priority are displayed.

7. Click onStart Restore to start running the restore.

The Status field indicates the session isPending thenRunning. IfOmniBack II requires media,Mount Request appears in theStatusfield.

To Respond to Mount Requests

When prompted by a Mount Prompt message from the Restore Monitor,insert the correct media in the device and confirm the prompt request inthe following way:

1. Close theMount Request dialog.

2. Select (highlight) the device with theMount Request status.

3. SelectActions → Confirm Mount Request from the menu bar.

5-17


e O ( f gIf a medium has copies in case of restore mount request, the messsage states:'Available copies...' In the message there is a list of all copies of a specific medium.You can load any of the copies or the original to continue restore.If there is no original in the backup device but there is at least one copy, OmniBackII will automatically use the copy and no mount request will be issued.

The status of the session and device changes toRunning . When thesession has completed, the status of the session displaysCompleted anda window appears with the message "Session Completed!"

8. Click OK to close the message window and return to theOmniBack IIRestore Monitor window.

9. SelectFile → Close to close the monitor window and return to theOmniBack II Restore window.

Viewing the Messages Field

While the restore is running, messages appear in theRestore MonitorwindowMessages field indicating the status of the filesets, devices, and theprogress of the restore.

While messages are still displayed in theMessages field, position thecursor in theMessages field and click on the RIGHT mouse button. Choosefrom the following message options in the menu that appears:

Search To search for specific string in the message line.

Clear To clear all messages from the field.

Scroll MessagesTo scroll messages as they are generated.

Print Messages To print messages on a printer.

The maximum buffer for messages in theMessages field is limited with theconfigurable parameterMAXGUIMSG. See “OmniBack II Global OptionsFile” on page7-13 for more information. If the maximum buffer isexceeded, messages stop appearing in theMessages field and the errormessage “Output disabled” appears; however the backup continues.

5-18


Searching for a Specific File

From time to time you may forget where a specific file was located on yourhost, although you remember a part of the file name. OmniBack II gives youa way to easily search for such files.

Note that you should normally use the browser to find your files. The searchaction may take longer and it will only show the first 500 files matching theselected criteria. In the event this limit is reached, you must further limityour search criteria.

1. From theOmniBack II Main menu, choose a cell server and click theRestore icon to open theHP OmniBack II Restore window.

2. ChooseActions → Search… to open theHP OmniBack II Restore- Search window.

3. Enter as much information as possible to speed up the search. ClickSearch to start searching for the file. Note that this action can take sometime, depending on your configuration.

4. If you want to restore all files with the same name, select any object fromtheFile Found In list and clickOK to open theFileSystemRestore Dialog window. Continue with the normal restore procedure.

5. If you want to select a specific file, double-click on the host in theFileFound In list and select the specific file. Continue with the normalrestore procedure.

Parallel Restore

OmniBack II enables parallel restore, meaning that any subset of filesystemsand rawdisks from one host can be restored in a single restore session,demultiplexed if required.

In order for parallel restore to run, a backup must be done using concurrencyhigher than one.

5-19


Parallel restore improves performance if you restore files to different disks.Otherwise, the files are restored sequentially.

To perform a parallel backup follow these steps:

1. In theOmniBack II - Main menu, select theRestore icon to open theHP OmniBack II Restore window.

2. In theHP OmniBack II Restore window, from the menu selectActions →Parallel Restore .

3. In theHP OmniBack II Restore window, double-click a host from thelist to display a list of its mount points.

4. Select the host’s mountpoints. Selected mountpoints are displayed in thelist of objects selected for restore on the right side.

5. Double-click an object from the list to open theFilesystem RestoreDialog window where you specify files and directories of the selectedobject to be backed up.

6. After you have specified files and directories for a parallel restore, clickRestore... to openOmniBack II Restore Monitor window.

7. In theOmniBack II Restore Monitor window, clickActions→Start Restore to run a parallel restore.

5-20

�.D�[256�47; 1�<-��K325K�."�&3#V� U $ ��YQR-��R3�mi�$ &�/>s�"�S3#V$ ��Q�7y��Y�$ S�R�d��d W�PQ"��

Restoring a Rawdisk Section (Logical Volume)

Restoring a disk section (logical volume) includes the following tasks:

1. Selecting from which backup session you want to restore.

2. Selecting a version of backup.

3. Selecting a section to restore.

4. Selecting restore options.

5. Previewing, starting, and monitoring the restore.

Choosing the Rawdisk Section to Restore

To choose a rawdisk section for restore, follow these steps:

1. Click Restore at theOmniBack II Main Menu to open theOmniBackII Restore window.

2. Select the rawdisk backup from which you want to restore.

3. SelectActions → Restore Selected… to open theRawdisk RestoreDialog window.

4. In theBacked up On field, choose the version you want to restore. Click... to get a list of versions.

5. TheSections field shows all disk sections backed up in the selectedbackup session. To remove a disk section from the list, select the sectionand click theRemove button. If you need to add it back, type its name inthe field below and clickAdd.

5-21

��D�[256�47; 1�<-��K325K��"�&3#V� U $ ��YQR-��R3�mi�$ &�/>s�"�S3#V$ ��Q�7y��Y�$ S�R�d��d WlPm"��

Figure 5-4 Restoring a Rawdisk

Specifying Rawdisk Restore Options

OmniBack II provides restore options which allow you to control a rawdiskrestore session.

To select the restore options, chooseRawdisk Restore Options.

The following options are available:

Target Hostname Allows you to change the hostname where therawdisk section should be restored. By default,OmniBack II restores to the original host.

Pre- exec A Pre-exec command is executed as soon as the

5-22

�.D�[256�47; 1�<-��K325K�."�&3#V� U $ ��YQR-��R3�mi�$ &�/>s�"�S3#V$ ��Q�7y��Y�$ S�R�d��d W�PQ"��

Disk Agent is started, but before any restoreprocessing has started.

Post- exec A Post-exec command is executed just beforethe Disk Agent terminates.

For more information, see “Using Pre- andPost- Exec Commands” on page7-6.

List Restored Objects When set to ON, OmniBack II displays thenames of the disk sections in theMessagesection of theMonitor window as the objectsare restored. The default is OFF.


information about the restore session. Thedefault is OFF.

Starting and Monitoring a Rawdisk Restore

When you activate a rawdisk restore, you open theOmniBack II RestoreMonitor window, enabling you to monitor the progress of your restore. TheMonitor window also allows you to respond to mount requests for therestore. To activate the restore, follow these steps:

1. From theRawdisk Restore Dialog , chooseOK to open theRestoreMonitor window.

2. Choose:





5-23

��D�[256�47; 1�<-��K325K��"�&3#V� U $ ��YQR-��R3�mi�$ &�/>s�"�S3#V$ ��Q�7y��Y�$ S�R�d��d WlPm"��

4. Select theReport Level .


5. Click onStart Restore from the menu bar to start the restore. TheStatusfield indicates the restore session isInactive/Waiting , then finallyRunning . Other status messages may appear depending on the progressof the restore.

When the session has completed, the status of the session displaysCompleted and a window with the message "Session Completed!"appears.

Responding to Mount Requests

A mount prompt is issued when OmniBack II needs a new medium to readdata.

1. Insert the needed medium in the device.

2. Select the device with theMount Request status.

3. SelectActions → Confirm Mount Request from the menu bar. Thestatus of the session and device changes toRunning .

5-24

�.D�[256�47; 1�<-��K325K�."�&3#V� U $ ��YQ��$ d "�& ZVU ��PnR-��R3�mi�$ &�/-,.R�S�/�Wlh

Restoring Files from a Rawdisk Backup

Restoring files from a rawdisk backup is supported on HFS filesystems only.

You can restore only "regular" Unix files from a rawdisk backup. Recoveryof any other file types is not supported by OmniBack II.

You can restore files from any directoryexcept the CDF directory (of clusterenvironments).

Selecting the File from a Rawdisk to Restore

1. Select a cell server and clickRestore in theOmniBack II Main Menu .TheOmniBack II Restore window appears.

2. Select the rawdisk backup object which contains the file you want torestore.

3. SelectActions → Restore Single File... to open theSingle FileRestore window. The backup object you selected is displayed in theRawdisk field.

5-25

��D�[256�47; 1�<-��K325K��"�&�#%� U $ ��YQ��$ d "�& Z%U �lP�R>��R��mi�$ &�/-,�R�S�/�W�h

Figure 5-5 Restoring Single Files from a Rawdisk

4. In theBacked Up On field, choose the version from which you want torestore. Click... to get a list of versions.

5. In theRestore Files field, enter the path and a file name.

6. Enter the disk section name in the field labeledFrom Section or clickthe... button to select the section from a list.

5-26


Specifying Rawdisk Restore Options

The rawdisk restore options apply to all files to be restored.

1. ChooseSingle File Restore Options ... to open theFilesystemRestore Options window.

The following options are available:

Target Hostname Allows you to change the hostname where therawdisk section should be restored. By default,OmniBack II restores to the original host.

Merge Preserves the destination version of files andmerges the restore fileset into the existingfileset on the disk. The default is Merge.

Overwrite Replaces the files and directories on the diskwith the version of the files and directories onthe media.

No Overwrite Preserves the files and directories on the disk, ifthey exist. The version of these files anddirectories on the media is not restored.

Restore Time Attributes Preserves the time attribute values of therestored file. When set to OFF, OmniBack IIsets the time attributes of the restored file to thecurrent date and time. The default is ON.

Restore ProtectionAttributes Preserves the original protection attributes of

the restored file. When set to OFF, OmniBack IIapplies the protection attributes of the currentrestore session. The default is ON.

List Restored Files When set to ON, OmniBack II displays thename of the file in theMessages section of theMonitor window while the object is beingrestored. The default is OFF.

5-27

��D�[256�47; 1�<-��K325K��"�&�#%� U $ ��YQ��$ d "�& Z%U �lP�R>��R��mi�$ &�/-,�R�S�/�W�h


information about the restore session. Thedefault is OFF.

Pre- exec A Pre-exec command is executed as soon as theDisk Agent is started, but before any restoreprocessing has started. See “Using Pre- andPost- Exec Commands” on page7-6 for moreinformation.

Post- exec A Post-exec command is executed just beforethe Disk Agent terminates. See “Using Pre- andPost- Exec Commands” on page7-6 for moreinformation.

Starting and Monitoring File Restore from a Rawdisk

After you have provided the information necessary for the restore, you areready to activate the restore.

1. In theSingle File Restore window, chooseOK to open theOmniBack II Session Monitor window.

2. Choose:





4. Select theReport Level .


5-28


5. Click onStart Restore from the menu bar to start the restore. TheStatusfield indicates the restore session isInactive/Waiting , then finallyRunning . Other status messages may appear depending on the progressof the restore.

When the session has completed, the status of the session displaysCompleted and a window with the message "Session Completed!"appears.

Restoring a File When You do not Know the Filename

If you need to restore a file or directory but do not know the filename, do thefollowing:

1. Restore the entire rawdisk to an empty section.

2. Mount this empty section as a filesystem.

3. Find the file you are looking for using filesystem file restore.

4. Copy the file back to its original location.

5. Umount the empty section.

6-1

6

Monitoring Sessions

6-2

�>6�1�; 256�4q; 1�<-}LD�[ [ ; 6�1�[

In This Chapter

OmniBack II allows you to monitor currently running sessions, as well asviewing already finished sessions. You can view messages and status of thesessions, devices used, objects backed up or restored, and so forth.

In addition, a Cell Monitor is provided that helps administrators ofenvironments with more cells to have an overview of all their cells.

6-3

�-6�1�; 256�47; 1�<>}�D�[ [ ; 6�1�[w ��$ #V� U $ ��YQ��W��$ ��YQsL"�&�&�$ ��&

Monitoring Running Sessions

OmniBack II allows you to connect to any running backup session andmonitor the progress of the session, abort the session, or respond to a mountprompt request. For more information on mount prompt requests, see“Automating Mount Prompt Handling” on page7-3.

The progress and status of running sessions can be monitored using theOmniBack II Session Monitor window. As soon as a session isfinished or aborted, it is no longer displayed as the currently running sessionbut as a previous session.

1. From theOmniBack II Main menu, chooseMonitor to open theOmniBack II Session Monitor window.

The window shows the progress and the status of all currently runningsessions in a cell.

From theActions menu you can abort a session.

When you run an interactive backup or restore session, a monitor window isopened showing objects, devices, and messages generated in the session.Even if the GUI is closed, the sessions continue.

Viewing Details of a Currently Running Session

You can view detailed information of a currently running session by double-clicking on the session to open theOmniBack II Backup Monitor or theOmniBack II Restore Monitor window.

6-4

�>6�1�; 256�4q; 1�<-}LD�[ [ ; 6�1�[w ��$ #V� U $ ��YQ��W��$ ��YQsL"�&�&�$ ��l&

Figure 6-1 Monitoring a Restore Session

In this window you can see all backup or restore objects with their status, thestatus of devices, and the messages generated in this session.

From theActions menu you can abort the session or cancel a mountprompt request.

By clicking the right mouse button in theMessages area, you can scroll,clear, print, or search for specific messages.

6-5

�-6�1�; 256�47; 1�<>}�D�[ [ ; 6�1�[��$ "��m$ ��YQc U "� �$ ��W�&-sL"�&�&�$ ��&

Viewing Previous Sessions

As soon as a session is finished or aborted, it is no longer displayed as acurrently running session but as a previous session.

1. From theOmniBack II Main menu, chooseMonitor to open theOmniBack II Session Monitor window.

2. ChooseView → Previous Sessions and choose all or selected sessions.

The window shows all completed and currently running sessions.

Figure 6-2 Viewing Completed Sessions

The following actions are available from theOmniBack II SessionMonitor window showing previous sessions:

1. Restarting unsuccessful backups. See “Managing Failed Backups” onpage7-14 for more information.

2. Removing detailed information from the session. See “Managing theGrowth of the Database” on page8-4 for more information.

6-6

�>6�1�; 256�4q; 1�<-}LD�[ [ ; 6�1�[��$ "3�m$ ��YQc U "3 �$ ��W�&>sL"�&�&�$ ��&

Viewing Details of Previous Sessions

You can view detailed information of a previous session by double-clickingon the session to open theOmniBack II Backup Monitor or OmniBackII Restore Monitor window.

In this window you can see all backed-up or restored objects with theirstatus, as well as messages generated in the session. Using theView menuyou can also find media used in this session. This functionality is availablefor backup sessions only.

By clicking the right mouse button in theMessages area, you can scroll,clear, print, or search for specific messages.

By double-clicking on a specific object, you can see only the messagesrelated to this object.

6-7

�-6�1�; 256�47; 1�<>}�D�[ [ ; 6�1�[w ��$ #V� U $ ��YQs�"3 �" U R�d��."�d d &

Monitoring Several Cells

For environments with several OmniBack II cells configured, a specialmonitor is provided giving you an overview of all your cells.

To start theCell Monitor , type:

xomnicellmon -cell Cell_Server1 Cell_Server2 ...

You must specify a list of Cell Servers of the cells you want to monitor.

Figure 6-3 Monitoring OmniBack II Cells

From theActions menu you can view different types of backup objects,lists scheduled objects, or list disks not configured for backup.

6-8

�>6�1�; 256�4q; 1�<-}LD�[ [ ; 6�1�[w ��$ #V� U $ ��YQs�"3 �" U R�d��."�d d &

7-1

7

OmniBack II Advanced Tasks and Concepts

7-2

@IH-1�; JLK�: MC0 03��83]�K�1�: D�8.��K�[ M [IK�1�8 o 6�1�: D�B325[

In This Chapter

This chapter describes customization features and provides instructions forconfiguring these features.

The following customization features are described in this chapter:

• Automating Mount Prompt Handling

• Pre- and Post-Exec Processing of Commands

• Customizing the Encryption Algorithm

• Customizing the Compression Algorithm

• Customizing the OmniBack II Global Options

• Recovery after a Disaster

• Moving a Cell Server

• Recovery of Failed Backups

7-3

@IH-1�; JLK�: MI0 0��C83]�K�1�: D�8.��K�[ M [CK�1�8 o 6�1�: D�B32_[T W!#V��PQR3#V$ ��Y w ��Wl�!#+c U ��PQh!#�b�R��ild $ ��Y

Automating Mount Prompt Handling

TheMount Request status on the monitor screen indicates that a deviceneeds a new medium and is waiting for a user response to the mount request.OmniBack II remains in this state until the mount request is confirmed or thesession is aborted. If there is no response to the mount prompt within apredefined mount prompt delay (30 minutes by default), a mount promptscript is executed on the Cell Server where the session is running that sendsan email to the user who started the session.

The default script that sends email to the user is:

/opt/omni/lbin/Mount.sh

The Mount Prompt Delay and the Mount Prompt Script can be configuredusingAdvanced Options in theLogical Device Conf igurationwindow.

You can change the default script by modifying theMountScript variablein the global options file. To change the default mount prompt delay, modifytheMountDelay variable in the global options file.

OmniBack II invokes the mount prompt script and provides the followingcommand line arguments:

1. Unix login of user who started the backup2. Unix group of user who started the backup3. host where the backup was started4. PID of the backup process5. session key6. logical device that generated the mount request7. host of the logical device8. pathname of the physical device name waiting for new medium (for

libraries, the slot number (SCSI Library) or the device file (MO Jukebox)

7-4

@IH-1�; JLK�: MC0 03��83]�K�1�: D�8.��K�[ M [IK�1�8 o 6�1�: D�B325[T W!#V��PQR3#V$ ��Y w ��W��!#+c U ��PQh!#+b�R��i�d $ ��Y

is used instead of the pathname of the physical device)9. device type number10.device type name11.medium id12.medium label13.medium location14.pool name15.media allocation policy of the pool16.media type number17.media type name18.session key

If OmniBack II is unable to define a medium to mount, empty parametersare sent to the mount prompt script. This can occur if there are no mediaremaining in the pool or if there is no space remaining on the medium.

For more information on adding a script file, see the online help topic"Configuring Advanced Options for a Logical Device" in "Logical DeviceConfiguration Tasks."

Mount Prompt Script Examples

This section provides some typical modifications to the mount promt script.

An email must be sent to a specific user only:

In theMount.sh script, change the$USER@$HOSTNAME variable to thespecific user.

Aborting sessions with the mount prompt script:

Specify the following command in the mount prompt script.

/opt/omni/bin/omniabort -session $SESSIONKEY 2>/dev/null1>/dev/null

Enter all commands in one line only.

7-5

@IH-1�; JLK�: MI0 0��C83]�K�1�: D�8.��K�[ M [CK�1�8 o 6�1�: D�B32_[T W!#V��PQR3#V$ ��Y w ��Wl�!#+c U ��PQh!#�b�R��ild $ ��Y

Automating mount prompt handling

OmniBack II can detect that a blank tape has been loaded and continue witha backup session without your confirming the mount request.

To automate the mount prompt handling, enter the following lines inMountscript :

sleep time-period-in-seconds

/opt/omni/bin/omnimnt -session $SESSIONKEY -device$DEVNAME.

7-6

@IH-1�; JLK�: MC0 03��83]�K�1�: D�8.��K�[ M [IK�1�8 o 6�1�: D�B325[X &�$ ��YQc U "��R��iQcL��%��f�j��-��Q�Q��i��

Using Pre- and Post- Exec Commands

Before a backup can begin, additional actions are sometimes necessary. Forexample, before a backup begins, transaction processing on a database muststop and the users must be notified.

Pre- and Post- exec actions are provided on two levels:

• Before and after the backup of each datalist (session) is started. Theseactions are executed on any host.

• Before and after the backup of each object is started. These actions arestarted on the Disk Agents where the object resides.

Pre- and Post- exec functions are implemented using the Unix pipemechanism. All processes started in the Pre- or Post- exec functions mustfinish before processing continues.

� � � � �Be sure that you follow the instructions provided in the following sections whencreating your Pre- and Post- exec scripts.

Configuring Pre/Post-Exec Commands for a Datalist/Barlist

To back up a datalist with the remotePre-Exec or Post-Exec optionsfollow these steps:


2. In HP OmniBack II-Backup window, select a datalist and clickEdit →Modify List. TheOmniBack II Backup Editor windowis displayed.

3. In theOmniBack II Backup Editor , selectOptions →ForDatalist . TheHP OmniBack II-Session Options window isdisplayed where you can specify thePre-Exec or Post-Execcommands.

7-7

�I�-�� L �¡ ¢I£ £�¤C¥ ] ��¡ ¦�¥.§� �¨ ¢ ¨C ��¥-©�ª��¡ ¦�«3¬_¨ ��® ¯�°Q±L²5��³��¯�´Q±�µl��V³ ��¶ ��>��µ��Q�Q��¯�´��

Figure 7-1 Configuring Pre/Post-Exec Commands located on a Cell Server

Pre- and Post- Exec Commands for a Datalist/Barlist

The following features pertain to Pre/Post-exec commands on local andremote hosts.

Pre- and Post- exec commands for a datalist are started before and after thebackup of a datalist/barlist session. These commands can be executed on anyhost.

The following environment variables are exported and can be used in Pre-and Post- exec scripts for a datalist/barlist session on any host:

SESSIONKEY Is used to identify the running session. You may, forexample, abort a backup session before it is started ifsomething is wrong. You can use this variable with Pre-exec commands only.

7-8

�I�-�� L �¡ ¢C£ £3¤�¥ ] ��¡ ¦�¥.§� �¨ ¢ ¨I ��¥-©�ª��¡ ¦�«3¬5¨ ��® ¯�°Q±L²��³��¯�´Q±Lµ��%³ ��¶ ��-��µ��Q�Q��¯�´��

PREVIEW Set to 1 if preview is running. Set to 0 if backup isrunning. You can therefore modify your commands to beexecuted only during a backup and not a preview.

SESSIONID Is used to identity a finished session and is recorded in thedatabase. You can only use this variable with the Post-exec command.

SMEXIT Exit code of the Session Manager and is the same as theexit code of theomnib command:

• 0 Completed• 10 Completed with file errors• 11 One or more Disk Agents failed• 12 All Disk Agents failed• 13 Session was aborted

You can use this variable with the Post-exec commandsonly.

OWNER Owner of the session (for example,[email protected]).

Be sure that you check the following before configuring Pre- and Post- execcommands for a datalist on a local or remote host:

• You must specify the full path name for the pre/post-exec commands.

• If you set the global optionUsePanScripts to 1 and thehost on which you want to start a pre/post-exec command is a Cell Server,the Session Manager will search for the scipts in the/opt/omni/lbin/scripts directory on the Cell Server.

• On the client hosts, the pre/post-exec command must be located in thefollowing directories:/opt/omni/lbin/ on HP-UX 10.x,/usr/omni/bin/ on other UNIX hosts,$OMNIBACKHOME$\BIN on Windows NT hosts.

• The scripts must be owned by the superuser (root) and must havepermissions-r-x------ set.

• If a Pre- exec command fails (returns a non-zero value), the backup status

7-9


of the session is set tofailed and the session is aborted.

• If a Post- exec command fails (returns a non-zero value), the backup ofthe session is set tocompleted with errors .

• The Pre- and Post- exec commands for a datalist are by default NOTexecuted during a preview of a backup. This behavior is defined by theExecScriptOnPreview variable in the global options file. See“OmniBack II Global Options File” on page7-13 for more information.

• Pre- and Post- exec commands are handled in the same way as commandsentered at the shell prompt. Special shell characters such as the pipe| andthe redirect symbols> and< are allowed.

• The Unix shell controls the Pre- and Post- exec processing. Therefore, youcannot use OmniBack II (GUI or command-line) to stop a session. Theonly way to stop a session while it is executing a Pre- or Post- execcommand is to use the Unixkill command.

• The Pre- and Post- exec processes operate in background mode.Therefore, do not use any interactive commands for Pre- and Post- execprocessing.

• All commands are started with the UID of the user configured as thesession owner. If a user is not configured on the Cell Server, Pre- andPost- exec commands are not executed but the backup continues.

• The Pre- and Post- exec scripts must send some output at least every 15minutes by default or the scripts get aborted. You can change this timeinterval by modifying theScriptOutputTimeout variable in the globaloptions file.

• Timeout is provided - if no message is received within the specifiedtimeout in seconds, the script execution is aborted.

• If the session owner hasBackup as Root permission, the script isstarted as root, otherwise as the session owner.

• If there is no executable script on the host or if the path of the script iswrong, OmniBack II displays an error message that the script failed andthe session is aborted.

• The executable script can be located on any host. If thepre-exec or

7-10

�I�-�� L �¡ ¢C£ £3¤�¥ ] ��¡ ¦�¥.§� �¨ ¢ ¨I ��¥-©�ª��¡ ¦�«3¬5¨ ��® ¯�°Q±L²��³��¯�´Q±Lµ��%³ ��¶ ��-��µ��Q�Q��¯�´��

post-exec script fails, the session is aborted.

• If a command writes any text tostdout , this text is received by the DiskAgent, sent to the Session Manager, and written to the database. Astderr is redirected to/dev/null . You can redirect it tostdout to geterror messages logged to the database.

� � � � �A pre-/post- exec script may hang because it did not close all file descriptorsbefore forking the new process. This is the case if the new process runs in thebackground and does not exit (for example, database server process (dbstart ),some deamon processes, etc.). In this case, a user can use thedetach command.The source of thedetach command is provided in thedetach.c file. Thiscommand is officially unsupported. Example:/opt/omni/bin/utilns/detach pre_script [arguments...]

Pre-/post- Exec Commands on a Local Host

The following features relateto pre/post-exec commands on a local hostonly:

• The Pre- and Post- exec commands for a datalist must be located on theCell Server.

• By default, Pre- and Post- exec functions can be located in any directoryon the Cell Server. If you set theUsePanScripts variable in the globaloptions file, scripts can be started from a specific directory only. See theglobal options file for details.

Pre-/post- Exec Commands on a Remote Host

The following pertains to pre/post-exec commands on a remote host only:

You must specify the remote pre/post-exec command in/opt/omni/lbin .

7-11


Pre- and Post-Exec Commands for an Object

Pre- and Post- exec commands for an object are executed before the backupof the object is started or finished. You can specify these commands for eachobject independently. These commands are executed on the host where theDisk Agent is running.

For overriding Pre- and Post-exec command scripts for an object, add thefollowing variables:

OB2PREEXEC=full_pathname

OB2POSTEXEC=full_pathname

into the file:

/opt/omni/.omnirc

If the Pre-exec or Post-exec script is specified in the datalist for an object, itwill be overridden by the scripts specified in the.omnirc file.

The following environment variables are exported and can be used in thePre- and Post- exec scripts for an object on the host where the Disk Agent isrunning:

PREVIEW Set to 1 if preview is running. Set to 0 if backup isrunning. You can therefore modify your scripts to beexecuted only during a backup and not during a preview.

BDACC The Disk Agent sets its exit code (zero is successful) tothe BDACC environment variable. This variable can bechecked in the Post- exec script thus making the Post-exec command dependent on the successful terminationof the Disk Agent.

Be sure that you check the following before configuring Pre- and Post- execcommands:

• The Pre- and Post- exec commands for an object are also executed duringthe preview of a backup. Therefore, you may want to preview yourbackup first and then add the Pre- and Post- exec commands, or check the

7-12

�I�-�� L �¡ ¢C£ £3¤�¥ ] ��¡ ¦�¥.§� �¨ ¢ ¨I ��¥-©�ª��¡ ¦�«3¬5¨.· ® ¯�°Q±L²�¸�³�¹�¯�´Q±Lµ ·�º ³ ��¶ ¸�»-¼�µ�½Q½Q¹�¯�´ ·

PREVIEW environment variable in your scripts.

• If a Pre- exec command for an object fails (returns a non-zero value), thebackup status of the object is set to aborted and the Disk Agent stopsprocessing. Therefore, no backup of the object exists.

• If a Post- exec command fails (returns a non-zero value), the backup statusof the object is set to aborted. However, a backup of the object exists anddata can be restored.

• The Pre- and Post- exec commands should send some output to the DiskAgent at least every 120 minutes by default, or the backup of the objectwill be aborted. This timeout period can be changed by modifying theSmDaIdleTimeout variable in the global options file.

• Pre- and Post- exec commands are handled in the same way as commandsentered at the shell prompt. So, special shell characters such as the pipe|and the redirect symbols> and< are allowed.

• The Unix shell controls the Pre- and Post- exec processing. Therefore, youcannot use OmniBack II (GUI or command-line) to stop the Disk Agent.The only way to stop a session while it is executing a Pre- or Post- execcommand is to use the Unixkill command.

• The Pre- and Post- exec processes operate in background mode.Therefore, do not use any interactive commands for Pre- and Post- execprocessing.

• If a command writes any text tostdout , this text is received by the DiskAgent, sent to the Session Manager, and written to the database. Astderr is redirected to/dev/null . You can redirect it tostdout to geterror messages logged to the database.

• The Pre- and Post- exec commands for an object must be located on thehost where the Disk Agent is running.

• The Pre- and Post- exec commands must be executable and must bespecified with the full pathname.

• You can override any Pre- or Post- exec commands specified for objectsor datalists by specifying them with the OB2PREEXEC andOB2POSTEXEC variables in the global options file.

7-13

�I�-�� L �¡ ¢I£ £�¤C¥ ] ��¡ ¦�¥.§� �¨ ¢ ¨C ��¥-©�ª��¡ ¦�«3¬_¨� ½Q¯�® ¾�¹�»�¿-À À�ÁIÂ µ�a�¹�Â �IÃ!º ® µl¯ ·-Ä ® Â ¸

OmniBack II Global Options File

OmniBack II uses theGlobal Options file for advanced configurationsettings. Normally you do not need to modify this file, but occasionally youcan achieve different functionality if you modify some parameters. Thedescription of all variables is in the file itself.

The global options file/etc/opt/omni/options/global is an ASCIIfile. Using a text editor, you need to uncomment the appropriate option andset the value.

� � � � �When you update to a new version of OmniBack II, the global options you have arenot overridden. The new global options are documented in thenewconf igdirectory tree.

7-14

�I�-�� L �¡ ¢C£ £3¤�¥ ] ��¡ ¦�¥.§� �¨ ¢ ¨I ��¥-©�ª��¡ ¦�«3¬5¨Å ¹�¯�¹�°�® ¯�° Ä ¹�® Â ¸�´Q¾�¹�»�¿�Æ Ã�·

Managing Failed Backups

Recovering a failed backup is closely related to how OmniBack II runs fulland incremental backups.

Incremental backups always depend on the last full backup. If there is no fullbackup, OmniBack II will perform one even if an incremental backup isscheduled - you cannot have an incremental backup without a prior fullbackup.

Retry Host Backup Procedure

If you choose to back up several hosts and OmniBack II cannot access oneof the hosts at runtime, OmniBack II will try to back up the failed host oncemore after a successful backup of the other hosts. The retry is performedonly once.

OmniBack II will perform the retry backup in the following situations:

• "Inet" process is not running on the host.

• A host is not currrently connected to the network.

• All other cases in which theconnect( ) system call has failed.

OmniBack II will NOT perform the retry backup in the following situations:

• Either Omniback IIinet executable orvbda executable are not installed.

• Wrong version of OmniBack II (vbda ) is installed on the hosts in a cell.

• All other cases in which theconnect( ) system call has succeeded.

7-15

�I�-�� L �¡ ¢I£ £�¤C¥ ] ��¡ ¦�¥.§� �¨ ¢ ¨C ��¥-©�ª��¡ ¦�«3¬_¨Å ¹�¯�¹�°�® ¯�° Ä ¹�® Â ¸�´Q¾�¹�»�¿�Æ Ã�·

Failed Host Backup

During a backup operation, it can happen that a host is down or unavailabledue to maintenance or other problems. OmniBack II retries to back up thehost once (see the previous section). If this fails, the host will not be backedup.

This results in the following:

• If a full protected backup exists, an incremental backup will be startednext time the host is scheduled for backup.

• If a full protected backup does not exist, a full backup will be started nexttime the host is scheduled for backup.

This ensures the completeness of the data backed up.

Note that if you have configured infrequent scheduled backups, there may bea period of time when a recent backup for a host does not exist.

You can avoid this situation by running a backup for the host interactivelywhen hosts are available. See “Running Interactive Backups” on page4-20for instructions.

Restarting Failed Backup Objects

During a backup session it may happen that some backup objects are notbacked up successfully. OmniBack II provides a simple way to restart thebackup of failed objects.

� � � � �Sessions with statusrunning or completed or the backup of a barlist cannot berestarted.

Using GUI:

1. From theMonitor window, selectView → Previous Sessions→SelectSessions/All Sessions .

2. If you select theSelect Sessions options, you must select the criteria of

7-16

�I�-�� L �¡ ¢C£ £3¤�¥ ] ��¡ ¦�¥.§� �¨ ¢ ¨I ��¥-©�ª��¡ ¦�«3¬5¨Å ¹�¯�¹�°�® ¯�° Ä ¹�® Â ¸�´Q¾�¹�»�¿�Æ Ã�·

datalists you want to view in theSelect Previous Sessions window.

3. Select a failed session and chooseActions → Restart UnsuccessfulBackup.

This starts the backup of all failed objects.

Figure 7-2 Restarting Unsuccessful Backups

Using commands:

For example, you want to restart failed objects from the datalist MIKI.

1. To get a list of all the objects in the backup session, you must first find thesession ID of the datalist backup session.

$ omnidb -session -datalist MIKI -latestSessionID Type Status User.Group@Host==================================================================1996/01/08-12 Backup Completed/Failure [email protected]

7-17

�I�-�� L �¡ ¢I£ £�¤C¥ ] ��¡ ¦�¥.§� �¨ ¢ ¨C ��¥-©�ª��¡ ¦�«3¬_¨Å ¹�¯�¹�°�® ¯�° Ä ¹�® Â ¸�´Q¾�¹�»�¿�Æ Ã�·

2. To list all objects and their status of the backup session:

$ omnidb -session 1996/01/08-12Object Name Object Type ObjectStatus==================================================================kpp3.rep:/users1 'REP' FileSystem Completedkpp2.rep:/users/frenk 'REP' FileSystem Completedmdd56.rep:/users 'REP' FileSystem Failedtrblexll.rep:/home 'REP' FileSystem Failedwaikik.rep:/C 'REP' FileSystem Completed

3. To selectively restart failed objects only:

$ omnib -datalist MIKI -select mdd56:/users 'REP' trblexll:/home'REP'

7-18

�I�-�� L �¡ ¢C£ £3¤�¥ ] ��¡ ¦�¥.§� �¨ ¢ ¨I ��¥-©�ª��¡ ¦�«3¬5¨` ¸ º ¸�» º ® µ�¯Qµ!Ç+¼ `�ÄQÄ ® Â ¸ ·

Detection of CDF Files

OmniBack II can detect CDF (Context Dependent Files) on cluster serversystems. Since this often consumes time, you can disable this detection toimprove overall backup performance, especially for large filesystems with anumber of small files.

Detection of CDF files can be selectively enabled/disabled on a per-hostbasis.

HP-UX 10.x no longer supports CDFs so the CDF detection/backup isdisabled.

HP-UX 9.0x supports the CDF detection/backup. It can be disabled on aspecific host by specifying the following line in the/usr/omni/.omnircfile on that host:

OB2NOCDF=1

Note that ALL backup Disk Agents running on that host will receive thisoption and disable the CDF detection/backup.

We recommend disabling the CDF detection/backup on all hosts in a cellEXCEPT on servers of diskless cluster systems or any other hosts that arelikely to have CDF files.

7-19

�I�-�� L �¡ ¢I£ £�¤C¥ ] ��¡ ¦�¥.§� �¨ ¢ ¨C ��¥-©�ª��¡ ¦�«3¬_¨� ½Q¯�® ¾�¹�»�¿-À À�¹�¯�´QÈl¸�²�® º ¹ ·-Ä ® Â ¸-ÉkÊ ·�º ¸�½ ·-Ë È ¶�Ä ÉLÌ�µ�¯Qb�±L³ lÍÏÎ�Ð�Ñ ¶

OmniBack II and Veritas File Systems (VxFS) onHP-UX 10.x

OmniBack II supports the VxFS online backup feature.

For more information on VxFS functionality, see your system administrationmanuals.

Concepts

VxFS allows you to back up a filesystem while it is being used by someother application. This is called an online backup and is done by creating asnapshot of a filesystem and backing up this snapshot.

A snapshot of a filesystem is created when you mount the VxFS filesystemto a temporary directory. At this point you also specify the filesystem youwant to snap.

You configure a backup of this temporary directory, which actually is amount point to the snapshot of the filesystem as it was at the moment ofmount.

When the backup is finished, you unmount the snapshot filesystem so that itcan be used for other purposes.

Note that you can perform normal backups without using the VxFS snapshotfeature by simply configuring backup as for any other filesystem.

If you want to use the VxFS snapshot feature, you must configure a backupas follows.

1. You must have an empty or unused partition created in your host that canbe used by VxFS for a snapshot. See your system administrator’s manualfor instructions.

2. Create a temporary directory to which you will mount the snapshotfilesystem.

7-20

�I�-�� L �¡ ¢C£ £3¤�¥3Ò� ��¡ ¦�¥.§� �¨ ¢ ¨I ��¥-©�ª��¡ ¦�«3¬5¨� ½Q¯�® ¾�¹�»�¿>À À�¹�¯�´QÈ�¸�²5® º ¹ ·>Ä ® Â ¸>É�Ê ·3º ¸�½ ·>Ë È ¶�Ä ÉLÌ�µ�¯QÓ�±L³ zÍÔÎ�Ð�Ñ ¶

3. Create shell scripts to mount and unmount the snapshot filesystem to thetemporary directory. See “Script Templates” on page7-21 for templatesof these scripts.

4. Configure a backup of the temporary directory. The mount script must bespecified as the Pre- exec command, and the unmount script as the Post-exec command.

Improved Backup Performance

VxFS on HP-UX provides the specific option -direct I/O - that instructs theDisk Agents to bypass the UNIX buffer cache mechanism and transfer datadirectly to/from a disk, which improves the I/O performance. You can set the-direct I/O - option by assigning the following environment variableOB2VXDIRECT value <>0 .

Limitations

1. It is possible to restore VxFS to HFS and HFS to VxFS, except in thefollowing cases:

• VxFS does not support ACLs; therefore, on restores from HFS toVxFS this information will be lost.

• With VxFS it is possible to define different extent attributes andallocation controls for each file. OmniBack II recognizes and storesthis information and restores it back during restore. When restoring toan HFS, this information is lost.

2. You cannot use the VxFS snapshot feature on ordinary UNIX filesystems.

3. The amount of disk space necessary for the snapshot of a filesystemdepends on how busy the snapped filesystem is when the backup is run.The recommended size is up to 15% of the snapped filesystem, if thefilesystem is in heavy use during the backup. Normally, the size will be

7-21

�I�-�� L �¡ ¢I£ £�¤C¥3Ò� ��¡ ¦�¥.§� �¨ ¢ ¨C ��¥-©�ª��¡ ¦�«3¬_¨� ½Q¯�® ¾�¹�»�¿-À À�¹�¯�´QÈl¸�²�® º ¹ ·-Ä ® Â ¸-ÉkÊ ·�º ¸�½ ·-Ë È ¶�Ä ÉLÌ�µ�¯QÓ�±L³ lÍÏÎ�Ð�Ñ ¶

around 5%.

If the amount of data modified on the snapped filesystem is higher thanthe space available, OmniBack II producesCannot stat errormessages for all the remaining files to be backed up. You must unmountthe snapshot filesystem and repeat the backup procedure.

Restoring

Since you have backed up the temporary directory with the snapshotfilesystem mounted and not the original directory, you must restore the filesto the original directory using theRestore As option.

Script Templates

Here is a template that can be used to mount the VxFS filesystem.

# SnapMount.sh## Mounting snapshot filesystem (pre-exec script)## A script requires 3 parameters:# 1. a block special file of the snapped FS# or# a mount point directory of the snapped FS# 2. a block special file of the snapshot FS# 3. a mount point of the snapshot FS## NOTE:## In case of multiple Disk Agents reading from the same snapshot FS,# the pre-exec script should contain a kind of synchronization# mechanism for following reasons:## 1) an attempt to mount an already mounted snapshot FS,# snapping the same FS# will cause the pre-exec script to fail and a DA to abort## 2) an attempt to mount an already mounted snapshot FS,# snapping some other FS will cause a warning to be generated,# script to fail and a DA to abort## 3) a synchronization with the post-exec script should be also# provided because the snapshot FS must not be unmounted while there# is other DA reading from the FS.#

7-22

�I�-�� L �¡ ¢C£ £3¤�¥3Ò� ��¡ ¦�¥.§� �¨ ¢ ¨I ��¥-©�ª��¡ ¦�«3¬5¨� ½Q¯�® ¾�¹�»�¿>À À�¹�¯�´QÈ�¸�²5® º ¹ ·>Ä ® Â ¸>É�Ê ·3º ¸�½ ·>Ë È ¶�Ä ÉLÌ�µ�¯QÓ�±L³ zÍÔÎ�Ð�Ñ ¶

SNAPPED_FS=$1SNAPSHOT_FS=$2MOUNT_POINT=$3

mount -F vxfs -e -o snapof=$SNAPPED_FS $SNAPSHOT_FS $MOUNT_POINT

## end SnapMount.sh#

exit $?

Here is a template that can be used to unmount a VxFS system.

# SnapUnmount.sh## Unmounting snapshot filesystem (post-exec shell script)## Script requires 1 parameter:# - a mount point directory of the snapshot FS# or# - a block special file of the snapshot FS## NOTE# In case of multiple Disk Agents reading from the same snapshot FS,# a kind of synchronization mechanism has to be added for# the following reasons:## 1) post-exec script should unmount snapshot FS only if there# is no other DA reading from the snapshot FS## Success/failure of the DA can be checked by examining# the BDACC environment variable#

MOUNT_POINT=$1

umount -v $MOUNT_POINT

## end SnapUnmount.sh#

exit $?

7-23

�I�-�� L �¡ ¢I£ £�¤C¥3Ò� ��¡ ¦�¥.§� �¨ ¢ ¨C ��¥-©�ª��¡ ¦�«3¬_¨� ½m¯l® ¾.¹�»�¿-À À�¹�¯�´QÓ�± � ¯ º ¸�² Ã ²5® · ¸ Ä ® Â ¸-ÉkÊ ·�º ¸�½nµ�¯QÓ�±L³ lÍÏÎ�Ð�Ñ ¶

OmniBack II and HP Enterprise File System onHP-UX 10.x

OmniBack II supports the HP-UX version of the DCE Distributed FileSystem (DFS) called the HP Enterprise File System (EFS). For a list ofsupported versions, seeHP OpenView OmniBack II Software Release Notes.

Note the following when configuring backup of an HP EFS or DFS:

1. In the DCE environment, create a special OmniBack II DCE principal(user), by defaultOmniBackII. This principal must have therwxcid ACLentries for all the files and directories to back up and a keytab passwordentry in a local keytab file. If you want to use some other name thanOmniBackII, specify the name in theOB2DCEPRINCIPAL variable in the.omnirc file on the DCE host you want to back up. If the principal is userroot, no additional ACL settings are needed, but you still need a keytabpassword.

2. When configuring backup of a DCE host with HP EFS, you mustmanually enter the mountpoint for the HP EFS as/... since thismountpoint is not visible using the browse button.

3. Manually enter the UNIX and DCE junction point to the Files andDirectories list in the Filesystem Backup window. Usually, this junctionpoint is/.../cell_name/fs . This avoids generation of minor errorsduring backup.

4. A backup session can only be run as user root.

5. The HP EFS cannot be backed up using Host backup, as it is not detectedby OmniBack II.

7-24

�I�-�� L �¡ ¢C£ £3¤�¥3Ò� ��¡ ¦�¥.§� �¨ ¢ ¨I ��¥-©�ª��¡ ¦�«3¬5¨Õ ¸�Â ¸ º ® ¯�°Q¹-ÉL¸ ·�· ® µ�¯

Deleting a Session

HP OmniBack II keeps track of how long data on a medium is protected (see“Using Backup Options” on page4-26 for more information). When theprotection expires, the session will be overwritten by the newer backups.

OmniBack II provides a way to delete unwanted sessions from the database.

1. From theMonitor window, selectView → Previous Sessions.

2. Select a session you want to delete and chooseActions → Purge Session.

The session disappears from the list.

The following happens:

• Protection is removed from the session. This means that the session willbe overwritten.

• All detail information about the session is removed from the database.

• The session itself remains on the media until it is overwritten by the nextbackup. Therefore, you can still see or restore the session using optionList from Media .

7-25

�I�-�� L �¡ ¢I£ £�¤C¥3Ò� ��¡ ¦�¥.§� �¨ ¢ ¨C ��¥-©�ª��¡ ¦�«3¬_¨¼�µ Ã Ê�® ¯�° Å ¸�´�® ¹

Copying Media

OmniBack II offers the efficient duplicating of backup sessions to a secondset of media. In this way, OmniBack II provides reliable support forvaulting/archiving backup sessions.

To copy media follow the these steps:

1. In theHP OmiBack II - Main window, select theDevices&Mediaicon to open theHP OmiBack II - Device & Media Managementwindow.

2. In theHP OmiBack II - Device & Media Management window,select one of the configured media pools below to open theMediaManagement window.

Figure 7-3 Copying Media

7-26

�I�-�� L �¡ ¢C£ £3¤�¥3Ò� ��¡ ¦�¥.§� �¨ ¢ ¨I ��¥-©�ª��¡ ¦�«3¬5¨¼.µ Ã Ê�® ¯�° Å ¸�´�® ¹

3. From the menu in theMedia Management window, select a medium andclick Edit →Copy to open theMedia Management - Medium Copywindow and follow the online help instructions.

� � � � �The target media is by default assigned to the default media pool for that media type.

Copying Media of Backup Sessions

Copying media of backup sessions includes the following features:

• Duplicating a complete session is based on copying one or more mediabelonging to that particular session, to one target medium or a set of targetmedia.

• Media can be copied only to another media of the same media class. Thecopy preserves the media's multiplexed layout, catalogs, and objectposition information. Target media is checked as forinit .

• You can copy media over the network, and view the copy session in theOmniBack II session monitor.

• A single copy session operates from a single source device to a singletarget device. Multiple media can be copied sequentially in a single copysession, but only one medium at a time (no parallelism).

• The target medium that has OmniBack II format can have different set ofmedium attributes (medium ID, label, location, protection etc.) from themedium attributes of the source medium.

• All media which are created as replicas of source OmniBack II media willbe visible in the OmniBack II media management GUI as standalonemedia and are normally tracked by the OmniBack II media management.They are marked as a non-source set of media.

• After a source medium is copied to a target medium, the target medium ismarked asfull to prevent accidental appending during the lifetime of thecopied data.

• If some other data has been appended to the source medium after it hasbeen copied, the target medium is still regarded as a replica of the sourcemedium, but it is not a 100% match. The target medium cannot be used toappend data stored onto the source medium after the copying.

7-27

�I�-�� L �¡ ¢I£ £�¤C¥3Ò� ��¡ ¦�¥.§� �¨ ¢ ¨C ��¥-©�ª��¡ ¦�«3¬_¨¼�µ Ã Ê�® ¯�° Å ¸�´�® ¹

Copying media of Restore Session

Copying media of restore sessions includes the following features:

• If more than one copy of the required medium set is available at restore,OmniBack II will by default attempt to use the target set. Only if the targetset is not fully available (one or more of the required media is not present),or if explicitly mounted by the operator, OmniBack II will use media froma non-target set as a substitute.

• In the Mount Request of a restore session, the original medium and a listof copies you can choose from are displayed.

General constraints:

• Magazine medium cannot be used as a destination medium.

• Copy cannot be appended.

• Original cannot be appended.

• Copy cannot be copied.

Import/Export Specifics:

• If the original is in a database, copies can be freelyimported and exported.

• If the original is exported, one of the copies becomes the original.

• If you want to import a copy and its original is not found, there are twopossibilities:

• Import is denied (default).• You are allowed to import a copy with the-force option ofomnimm,

but if other copies exist, they cannot be imported later.

7-28

�I�-�� L �¡ ¢C£ £3¤�¥3Ò� ��¡ ¦�¥.§� �¨ ¢ ¨I ��¥-©�ª��¡ ¦�«3¬5¨Å µ�´�® Ç7Ê�® ¯�° Õ ¸�Ö�® »�¸>¹�¯�´ Å ¸�´�® ¹ Å ¹�¯�¹�°�¸�½Q¸�¯ º È�® ¸3×

Modifying Device and Media Management View

You can customize the media view in theDevice & Media Managementwindow by changing the variables in the global options file.

To modify the default media view, follow these steps:

1. Open the global options file on HP-UX 10.X:/etc/opt/omni/options/global .

2. Customize the attributes that will bedisplayed in the libray or mediamanagement viewby specifying the corresponding string variables.

See Global Options file for description of variable strings.

7-29

�I�-�� L �¡ ¢I£ £�¤C¥3Ò� ��¡ ¦�¥.§� �¨ ¢ ¨C ��¥-©�ª��¡ ¦�«3¬_¨Õ ® · ¹ ·3º ¸�²LØ�¸�»�µ!Ö�¸�²�Ê

Disaster Recovery

There are a few simple rules you can follow to be sure that disaster recoveryis as smooth and simple as possible:

• Make a backup of your Cell Server files and the files of other hosts on aregular basis. This ensures that you can always restore up-to-date data andthus allow users to continue their work normally.

• Make a full disk backup of all important hosts in your cell on a regularbasis. This allows quick recovery from a disk disaster.

• Perform a backup of the OmniBack II databases each night to ensure thatyou can restore the last state of the databases. If possible, configure thedatabase backup on a separate logical device, for example, a standaloneDDS. This simplifies recovery of files in the event of a Cell Serverdisaster.

Improved Disaster Recovery

OmniBack II provides much faster recovery of all data. For example, if abackup was made with concurrency4, which means that four backup objectswere simultaneously backed up on a single device, OmniBack will alsorestore objects with concurrency4. This will result in four times fasterrecovery.

Recovery of lost data includes:

1. Host disk recovery.

2. Recovery of OmniBack II installation and minimal configuration.

3. OmniBack II database restore.

4. Recovery of all data.

7-30

�I�-�� L �¡ ¢C£ £3¤�¥3Ò� ��¡ ¦�¥.§� �¨ ¢ ¨I ��¥-©�ª��¡ ¦�«3¬5¨Õ ® · ¹ ·�º ¸�²LØ�¸�»�µ!Ö�¸�²�Ê

Preparing For a Disaster

A disk disaster on any host is probably one of the most severe problems thatcan happen; therefore, it is good to plan a recovery procedure for all hosts.Basically, there are three different disaster cases:

• Some files have been corrupted or deleted, but the host is still operatingnormally. In this case, you only need to restore the corrupted or missingfiles. You can do this easily using OmniBack II restore.

• A client host has suffered a major disk disaster and is no longer operatingproperly. See “Recovering a Client Host” on page7-30 for instructions.

• A Cell Server host has suffered a major disk disaster and is no longeroperating properly. See “Recovering a Cell Server” on page7-31 forinstructions.

Recovering a Client Host

When you need to recover the root disk of yourhost, you may follow one ofthese two methods:

1. Install a new disk on another host and restore the complete backup on thedisk. This is the preferred solution.

2. Install a new disk on the crashed host and restore files on the disk.

Both methods are explained below.

Recovery on Another Host

1. Install a new disk on another host.

2. Make the disk bootable.

3. Restore your full disk backup on the new disk.

4. Move the disk to the crashed host and reboot the host.

7-31

�I�-�� L �¡ ¢I£ £�¤C¥3Ò� ��¡ ¦�¥.§� �¨ ¢ ¨C ��¥-©�ª��¡ ¦�«3¬_¨Õ ® · ¹ ·3º ¸�²LØ�¸�»�µ!Ö�¸�²�Ê

Recovery on the Same Host

1. Replace the crashed disk with a new one.

2. Boot your host from the installation media for your host, such as a DDStape.

3. Reinstall the operating system. Refer to your system administrator’smanual for instructions.

4. Reinstall OmniBack II client modules as they were before the diskdisaster. See Chapter 2, “Installation Overview” on page2-1 forinstructions.

5. Reinstall other applications using installation media.

6. Make a restore of the latest full backup of the host. See Chapter 5,“Restoring Data” on page5-1 for instructions.

Your clienthost should be successfully recovered.

Recovering a Cell Server

Recovering a Cell Server after a major disk disaster includes someadditional steps. This procedure is also applicable in case your completeCell Server is destroyed by some accident.

When you need to recover the root disk of your cell serverhost, you mayfollow one of these two methods:

1. Install a new disk on another host and restore the required files on the disk.This is the preferred solution.

2. Install a new disk on the crashed host and restore files on the disk.

Both methods are explained below.

Recover on Another Host

1. Install a new disk on another host.

2. Make the disk bootable.

3. Restore your full disk backup of the Cell Server on the new disk.

7-32

�I�-�� L �¡ ¢C£ £3¤�¥3Ò� ��¡ ¦�¥.§� �¨ ¢ ¨I ��¥-©�ª��¡ ¦�«3¬5¨Õ ® · ¹ ·�º ¸�²LØ�¸�»�µ!Ö�¸�²�Ê

4. Restore the latest database backup.

5. Move the disk to the crashed Cell Server host and reboot the host.

Recover on the Same Host

1. Replace the crashed disk.

2. Boot your host from the installation media for your host, such as DDStape.

3. Reinstall the operating system. Refer to your system administrator’smanual for instructions.

4. Reinstall the OmniBack II software on the Cell Server. See theHPOpenView OmniBack II Installation Guide for instructions.

5. Restore the latest backup of your database. This simplifies the restore ofall other files from media. Note that you cannot restore the databasedirectly. See “Restoring the Database” on page8-14 for instructions.

6. Stop running all OmniBack II processes with theomnisv.sh -stopcommand. This ensures that no files will be in use.

7. Move the/etc/opt/omni/ directory and recursively copy to it the files,previously restored to a temporary directory. This recreates the previousconfiguration.

8. Start OmniBack II processes with theomnisv.sh -start command.

9. Start the graphical User Interface and restore all other files from yourbackup.

Your Cell Server should be successfully recovered.

Example of Mission Critical System Recovery

This section provides an example of how you can prepare for a disaster andrecover a mission criticalhost, such as an OmniBack II Cell Server.

This example automates the recovery process.

7-33

�I�-�� L �¡ ¢I£ £�¤C¥3Ò� ��¡ ¦�¥.§� �¨ ¢ ¨C ��¥-©�ª��¡ ¦�«3¬_¨Õ ® · ¹ ·3º ¸�²LØ�¸�»�µ!Ö�¸�²�Ê

This example uses unsupported scripts provided by OmniBack II.

❒ An operating system and all mission critical applications (OmniBack IICell Server) are installed on the same disk (same volume group).

❒ The OmniBack II software, including the Cell Server, Disk Agents, andMedia Agents is installed on the host.

❒ You will need a new disk of the same size and with the same partitionconfiguration as the original disk.

❒ You will need a standalone DDS drive connected directly to the host.

Preparing for a Disaster

1. Be sure that all the filesystems or volumes of the critical disk are in onevolume group and on the same physical disk, for example,vg00.

2. Print out the information about the volume group configuration. For eachlogical volume you need to know where it is mounted (or the swap type)and its size. You must save this information!

3. Configure the standalone DDS in OmniBack II. See “Configuring andUsing Logical Devices” on page3-21 for instructions.

4. Initialize and label the medium you will use for backup, for exampleCRITSYS_OB2. See “Media Management Tasks” on page3-27 forinstructions.

5. Create a datalist with all filesystems on the critical disk. Exclude the/var/opt/omni directory and/dev/ vg00 (a device file for a disk withcritical applications). These files must be exluded so that they are notoverwritten during restore. See “Understanding Datalists and Barlists” onpage4-3 for more information.

Print out the datalist and save the printout.

6. Run a backup of this datalist and remember thesessionID .

7. Run the /opt/omni/sbin/utilns/omnipfr.ksh sessionIDscript. This saves all OmniBack II relevant information to the/OB2RECOVERY directory.

7-34

�I�-�� L �¡ ¢C£ £3¤�¥3Ò� ��¡ ¦�¥.§� �¨ ¢ ¨I ��¥-©�ª��¡ ¦�«3¬5¨Õ ® · ¹ ·�º ¸�²LØ�¸�»�µ!Ö�¸�²�Ê

8. Back up this directory to an empty DDS medium and label it using thetar command, for example,OB2RECOVERY_tar. Do NOT run this onthe DDS used in previous steps.

cd /OB2RECOVERY

tar cvfh device

This creates a recovery tape with the OmniBack II software needed forrestore.

At the end of these steps you have the following:

❒ A printout of the volume group information.

❒ A printout of the datalist used for backup of the host.

❒ A OmniBack II DDS tape with a backup of the host.

❒ A tar DDS tape with all the OmniBack II software needed for recovery.

You should save all this in a safe place.

Recovering From a Disaster

1. Replace a crashed disk with a new disk of the same size.

2. Install the HP-UX operating system from your system installation tapeand use the printout of the volume groups to reconfigure the logicalvolumes.

3. Open file/etc/hosts and find the line with the hostname of yoursystem and add its full name.

4. Insert the tar formatted recovery DDS tape (OB2RECOVERY_tar) in thedevice and run:

cd /

tar xvf device

This installs back all the OmniBack II software needed for recovery ofthe system.

5. Insert the OmniBack II formatted DDS with the backup of the whole

7-35

�I�-�� L �¡ ¢I£ £�¤C¥3Ò� ��¡ ¦�¥.§� �¨ ¢ ¨C ��¥-©�ª��¡ ¦�«3¬_¨Õ ® · ¹ ·3º ¸�²LØ�¸�»�µ!Ö�¸�²�Ê

system (CRITSYS_OB2) and run:

/omnirecover.ksh device

This restores all files in their places. If a file is busy, it is first renamed#filename and then the original file is restored.

6. Reboot the system.

All files that were backed up are now restored except for the excludedfiles. Some files, however, still differ: the files that were created duringthe installation of the operating system but were not on the recovery tapeare removed.

7. Restore the OmniBack II database. See “Restoring the Database” onpage8-14 for instructions.

Now you can restore all other files from previous OmniBack II backups.

7-36

�I�-�� L �¡ ¢C£ £3¤�¥3Ò� ��¡ ¦�¥.§� �¨ ¢ ¨I ��¥-©�ª��¡ ¦�«3¬5¨Å µ!Ö�® ¯�°Q¹>¼�¸�Â Â�É�¸�²�Ö�¸�²

Moving a Cell Server

Sometimes you may need to move the Cell Server to another host. Thissection explains how to move a Cell Server if it is running properly. In caseof a system disaster, refer to the “Disaster Recovery” on page7-29 sectionfirst.

Be sure that you prepare carefully for this task.

1. Decide whichhost will be the new Cell Server and install it as a CellServer - see theHP OpenView OmniBack II Installation Guide forinstructions. Note that you must request to move your licenses to the newCell Server.

2. Make a backup of your cell.

3. Make a backup of your database - see “Backing Up the Database” onpage8-12 for instructions.

Moving a Cell Server

On the old Cell Server, perform the following:

1. No backup or restore session should be running. Run theomnistatcommand to check this.

2. Export all hosts from the cell. See “Exporting Hosts from a Cell” onpage2-8 for instructions.

3. Exit the Graphical User Interface.

4. Run theomnisv.sh -stop command to stop all OmniBack II processes.

On the new Cell Server (which must be already installed), perform thefollowing:

1. Move the/etc/opt/omni/ directory to a target host.

7-37

�I�-�� L �¡ ¢I£ £�¤C¥3Ò� ��¡ ¦�¥.§� �¨ ¢ ¨C ��¥-©�ª��¡ ¦�«3¬_¨Å µ!Ö�® ¯l°m¹>¼�¸�Â Â�ÉL¸�²�Ö�¸�²

2. Recursively copy the/etc/opt/omni/ directories from the old CellServer to the new one.

3. Edit appearances of the old Cell Server name in the following new files.

/etc/opt/omni/cell/cell_server/etc/opt/omni/cell/cell_info/etc/opt/omni/users/UserList

You can use the following script to do this for you:

/opt/omni/sbin/install/omnichhost.ksh [-preview]old_name new_name

4. Run theomnicc command to update the configuration.

5. Run the Graphical User Interface and import all hosts. See “ImportingHosts to a Cell” on page2-6 for instructions.

6. Restore or copy the database to the new Cell Server.

7. Check if users are still correctly configured for the new cell.

8. Check if logical devices are still correctly configured for the new cell.

9. If you have removed the old Cell Server from your cell, also remove allits appearances from the configured datalists.

7-38

�I�-�� L �¡ ¢C£ £3¤�¥3Ò� ��¡ ¦�¥.§� �¨ ¢ ¨I ��¥-©�ª��¡ ¦�«3¬5¨Å ¼lÙ5É�¸�²�Ö�® »�¸�ÁIÆ�¹�²�´Q¹�¯�´ � ½Q¯�® ¾�¹�»�¿>À À

MC/ServiceGuard and OmniBack II

HP OpenView OmniBack II supports the MC/ServiceGuard softwareproduct provided for effective recovery of a particularly valuable host incase of a system disaster.

This section provides an explanation of supported functionality, limitations,and instructions for configuration.

� � � � �Instructions here are given as general guidelines only.We recommend that you first get familiar with MC/ServiceGuard by creating andtesting the example applications in the MC/ServiceGuard manuals.

Refer to the following manuals for more information:

• Managing MC/ServiceGuard for more information on MC/ServiceGuard.

• HP OpenView OmniBack II Installation Guide for more information onhow to install OmniBack II.

• HP OpenView OmniBack II Software Release Notes for last minuteinformation on the current OmniBack II release.

Functionality and Behavior

For OmniBack II, the really critical component is the Cell Server.MC/ServiceGuard integration provides a way to have an additional CellServer, called a Secondary Cell Server, which can be used instead of thePrimary Cell Server. In order to do this, the Cell Server software is viewedas a specific application that can be migrated to the Secondary Cell Server incase of a problem with the Primary Cell Server.

When MC/ServiceGuard detects problems with the Primary Cell Server, itmigrates the whole Cell Server Package to the Secondary Cell Server.Therefore, both Cell Servers must have fully installed and configuredversions of OmniBack II. Note, however, that the Secondary Cell Servercannot be used as the Cell Server of some other cell at the same time.

7-39

�I�-�� L �¡ ¢I£ £�¤C¥3Ò� ��¡ ¦�¥.§� �¨ ¢ ¨C ��¥-©�ª��¡ ¦�«3¬_¨Å ¼lÙ5É�¸�²�Ö�® »�¸�ÁIÆ�¹�²�´Q¹�¯�´ � ½Q¯�® ¾�¹�»�¿>À À

If a failure of the Primary Cell Server occurs while a backup is running, thebackup will fail for the currently backed-up host and all others that werescheduled for backup after this host. However, a complete OmniBack IIoperation is now running on the Secondary Cell Server where you can startan interactive backup of the failed hosts.

Prerequisites for Configuration

Before you start configuring OmniBack II with MC/ServiceGuard, check thefollowing:

❒ Decide which hosts are going to be the Primary Cell Server and theSecondary Cell Server. SeeHP OpenView OmniBack II InstallationGuide for more information how to choose an appropriatehost.

❒ Hosts chosen to be the Primary Cell Server and the Secondary Cell Servermust have MC/ServiceGuard installed and must be configured as clustermembers. SeeManaging MC/ServiceGuard for instructions.

❒ Hosts chosen to be the Primary Cell Server and the Secondary Cell Servermust have HP OpenView OmniBack II Cell Server software installed. SeeHP OpenView OmniBack II Installation Guide for instructions. Note thata permanent license must be installed on the Primary Cell Server.

Configuring Primary and Secondary Cell Servers

This section provides general guidelines only. For more detailedinstructions, refer to theManaging MC/ServiceGuard manual.

On the Primary Cell Server:

1. Set up the/dev/vg_ob2cs volume group on a shared disk accessible toboth Cell Servers.

2. Create the logical volume/dev/vg_ob2cs/lv_ob2cs for that group.

3. Mount the logical volume to the/omni_shared directory.

7-40

�I�-�� L �¡ ¢C£ £3¤�¥3Ò� ��¡ ¦�¥.§� �¨ ¢ ¨I ��¥-©�ª��¡ ¦�«3¬5¨Å ¼lÙ5É�¸�²�Ö�® »�¸�ÁIÆ�¹�²�´Q¹�¯�´ � ½Q¯�® ¾�¹�»�¿>À À

4. Modify the /etc/opt/omni/cell/sg.conf template file. You mustchange theSHARED_DISK_ROOT variable if you have configured someother shared directory and theCS_SERVICE_HOSTNAME variable. Thisvariable tells OmniBack II the name of the Primary Cell Server. Thedefault name isob2cs. net.domain. You must change thenet.domain to match your network.

5. Run/opt/omni/sbin/install/omniforsg.ksh -primary toconfigure the Primary Cell Server.

6. Unmount the/omni_shared directory.

7. Deactivate the/dev/vg_ob2cs volume group.

On the Secondary Cell Server:

1. Import the/dev/vg_ob2cs volume group.

2. Mount the logical volume to the/omni_shared directory.

3. Run/opt/omni/sbin/install/omniforsg.ksh -secondary toconfigure the Secondary Cell Server.

4. Unmount the/omni_shared directory.

5. Deactivate the/dev/vg_ob2cs volume group.

Configuring the Cell Server Package


1. Generate, modify, and distribute the package control script. Be sure thatyou provide the following information:

• /dev/vg_ob2cs/lv_ob2cs must be mounted as/omni_shared

• The service command must be/etc/opt/omni/sg/csfailover.ksh start

• The IP address must be the address associated with the relocatablehostname (ob2cs. net.domain)

7-41

�I�-�� L �¡ ¢I£ £�¤C¥3Ò� ��¡ ¦�¥.§� �¨ ¢ ¨C ��¥-©�ª��¡ ¦�«3¬_¨Å ¼lÙ5É�¸�²�Ö�® »�¸�ÁIÆ�¹�²�´Q¹�¯�´ � ½Q¯�® ¾�¹�»�¿>À À

2. Generate, modify, and distribute the cluster and package configurationscripts.

Starting the Cell Server


1. Halt the cluster.

2. Modify and distribute the cluster configuration file. If you are alreadyusing MC/ServiceGuard, this file already exists. Otherwise, you mustcreate it.

3. Start the cluster.

4. Hand over control of the volume group/dev/vg_ob2cs toMC/ServiceGuard using thevgchange command. See manpages fordetails.

5. Be sure that switching of the OB2SG package is enabled. See manpagefor thecmmodpkg command for details.

6. When the Primary Cell Server is restarted, proceed with the installation ofOmniBack II client hosts. See

Backing up a Secondary Cell Server System

If you want to back up the Secondary Cell Server or run the OmniBack IIGUI on it, you must run the following command on the Secondary CellServer:

mkdir -p /omni_shared/etc_opt_omni/cell

Now you can import the host to your OmniBack II cell configuration,distribute the Disk Agent, and configure the host like any other client.

7-42

�I�-�� L �¡ ¢C£ £3¤�¥3Ò� ��¡ ¦�¥.§� �¨ ¢ ¨I ��¥-©�ª��¡ ¦�«3¬5¨� ½Q¯�® ¾�¹�»�¿>À À�ÚÛ¸�ÜQ¾�¹ · ¸�´QØ�¸ Ã µl² º ® ¯�°

OmniBack II Web Based Reporting

OmniBack II provides full Web reporting integration. You can view reportsand configure report criteria using a Web interface.

� � � � �Web Browsing can be used on a host with the OmniBack II User Interface.

� � � � �Before viewing or configuring reports, you must integrate OmniBack II reportingwith Netscape Fasttrack Server. See “Integrating OmniBack II Reporting withNetscape Fasttrack Server” on page7-43.

To view or configure reports, perform the following steps:

1. Start WWW browser and point your browser to the followinglocation:http://hostname/OB2-cgi/main.pl

2. Select a Cell Server from the list to display further options.

3. Select a desired option to get detailed reports. OmniBack II allows you tosave customized reports for later use. For example, display infomrationabout all backup sessions that have run in the last 48 hours.

For more information, refer to online help available from the Web Browser.

You can access most of the reports through the command line interface.When you save a customized report, a command is displayed that can beused later to create the same report as pure ASCII text usinng the commandline interface.

OmniBack II provides WWW integration forNetscape FasttrackServer , but integration with other Web servers that support CommonGateway Interface (CGI) and directory mapping should also work.

Here are some examples of reports you can access using the WWW server:

• List of devices used in a datalist.

• Post- exec commands, status of their configuration and schedules.

• Filesystems that are not configured for backup.

• The status of the previous night’s backup.

7-43

�I�-�� L �¡ ¢I£ £�¤C¥3Ò� ��¡ ¦�¥.§� �¨ ¢ ¨C ��¥-©�ª��¡ ¦�«3¬_¨� ½Q¯�® ¾�¹�»�¿-À À3ÚÛ¸�ÜQ¾�¹ · ¸�´QØ�¸ Ã µ�² º ® ¯�°

Integrating OmniBack II Reporting with Netscape FasttrackServer

In order to integrate OmniBack II reporting with Netscape Fasttrack Server,you must perform the following tasks:

1. Install Netscape Fasttrack Server (NFS) on HP-UX 10.x

2. Configure the NFS to use OmniBack II reporting features.

� � � � �The host on which you install NFS must have OmniBack II Cell Server installed.

For more information about integration tasks, follow the instructions in theOmniBack II Installation Guide and online help

Using Provided Reporting Scripts

After you specify and submit the report criteria in theOmniBack II WWWReport Menu , OmniBack II will start a script and compose the WWWoutput.

Scripts enable you to view only essential information, and they point outpossible failures in everyday operations.

Scripts that OmniBack II creates have the following key features:

• Scripts produce WWW as well as ASCII output (for most reports).

• Full range of options enables you to configure reports to yourrequirements.

• Customized (pre-set) report options offer fast access to the most commonreports.

• Most of the reports are available for single and multi-cell enviroments.

You can use scripts created in an ASCII format to get the same reports as inthe WWW output. Reporting scripts can be scheduled usingcron or be usedas OmniBack II backup sessionpost-exec scripts to mail or save the

7-44

�I�-�� L �¡ ¢C£ £3¤�¥3Ò� ��¡ ¦�¥.§� �¨ ¢ ¨I ��¥-©�ª��¡ ¦�«3¬5¨� ½Q¯�® ¾�¹�»�¿>À À�ÚÛ¸�ÜQ¾�¹ · ¸�´QØ�¸ Ã µl² º ® ¯�°

reports. For example, reports on hosts not used by OmniBack II can bemailed to the administrator every week so that he can take appropriateactions.

Types of Reports

Four sets of reports are available:

• Backup sessions

• Datalist

• Configuration

• Pools and Media

For more information, refer to WWW online help.

7-45

�I�-�� L �¡ ¢I£ £�¤C¥3Ò� ��¡ ¦�¥.§� �¨ ¢ ¨C ��¥-©�ª��¡ ¦�«3¬_¨¼�Æ ·�º µ�½Q® Ý ® ¯�° º%Þ ¸ � ¯�»�²�Ê Ã!º ® µ�¯Qß�Â °�µ�²�® ºVÞ ½

Customizing the Encryption Algorithm

To increase the security of your backup media, you can enable theencryptoption using theBackup options window. This backup option writes datato the media in an encrypted form.

Media encrypted using the HP OmniBack II encryption option can only beread by an OmniBack II Media Agent using the same encryption key.

� � � � �Customizing of the encryption algorithm is supported on HP-UX only.

To customize the encryption algorithm, you can write your own encryptioncode module, compile the module, and link it to the standard HP OmniBackII encryption library. This library is calledlibde.sl and is located in the/usr/omni/lib (on HP-UX 9.0x) or/opt/omni/lib (on HP-UX 10.x)directories. The following section describes how to create your ownencryption module. For detailed information about developing Unix code,please consult theHP-UX Programming Manual.

¼ ß � À � � �If you change the encryption algorithm, OmniBack II will no longer be able todeencrypt data from backups performed with the previous algorithm. If this occurs,OmniBack II will restore the data in encrypted form. Therefore, it is recommendedthat you only change the algorithm after careful planning. Frequent changes to theencryption algorithm increase the risk of data loss!

¼ ß � À � � �To restore a backup created using a different encryption algorithm, you must firstrestore the version of the encryption algorithm that was used to create the backup setyou want to restore.

Creating an Encryption Code Module

This section provides an overview of the process for developing your owncode module for encryption. For more detailed information, please consulttheHP-UX Programming Manual.

7-46

�I�-�� L �¡ ¢C£ £3¤�¥3Ò� ��¡ ¦�¥.§� �¨ ¢ ¨I ��¥-©�ª��¡ ¦�«3¬5¨¼.Æ ·�º µ�½Q® Ý ® ¯�° ºVÞ ¸ � ¯�»�²�Ê Ã!º ® µ�¯Qß�Â °�µ�²�® ºVÞ ½

Creating and installing a new encryption code module involves thefollowing tasks:

1. rename the original shared library (libde.sl )

2. write the new code module

3. compile the new code module

4. link the new code module to the original shared library

5. rename the new shared library to the name of the original shared library(libde.sl )

� � � � �Since the encryption shared library is accessed by the backup and restore DiskAgents, the shared libraries must be replaced on all hosts where the Disk Agents run,not just on the Cell Server host.

The constants used in the encryption module are shown here:

DE_NONE 0 no encryption

DE_XOR 1 simple XOR encryption

The following list briefly explains each function used and its purpose.

define identifies the encryption type

DeInit initializes the encryption module

DeEncrypt performs the encryption

DeDecrypt performs the deencryption

DeExit exits the encryption module

The encryption module is shown with an explanation of the functions in themodule. The module defines unique data encryption type identifiers.

#if !defined(UCHAR)#define UCHAR unsigned char#endif

#if !defined(ULONG)#define ULONG unsigned long#endif

#define DE_NONE 0 /* No data encryption */#define DE_XOR 1 /* Simple XOR encryption */

7-47


#define DE_DES 2 /* DES encryption (not impl.) */

MODULE

Data Encryption (De)

FUNCTION

extern ULONGDeInit (#if PROTOTYPES void#endif);

ARGUMENTS

void

RETURNS

DE_NONE Initialization failed, encryption disabled

DE_XOR Initialization successful, xor encryption

DE_xxxx Customer-created & implemented encryption type, wherennnn represents a customer-supplied name

DESCRIPTION

This function is called by the Disk Agent’s initialization procedure atstartup. It initializes the data encryption module and retrieves the encryptionkey from a file or key server.

REMARKS

The distribution of the encryption key through a network is a complex issueand not within the scope of a backup/restore application. This function canread a key from a predefined file or contact a key distribution server (viaRPC) to obtain a key.

MODULE


7-48

�I�-�� L �¡ ¢C£ £3¤�¥3Ò� ��¡ ¦�¥.§� �¨ ¢ ¨I ��¥-©�ª��¡ ¦�«3¬5¨¼.Æ ·�º µ�½Q® Ý ® ¯�° ºVÞ ¸ � ¯�»�²�Ê Ã!º ® µ�¯Qß�Â °�µ�²�® ºVÞ ½

FUNCTION

extern intDeEncrypt (#if PROTOTYPES UCHAR *data, ULONG size#endif);

ARGUMENTS

data pointer to plain text buffer

size size of plain text buffer

RETURNS

0 Error

1 OK

DESCRIPTION

The encryption of plain text should be done in-place. OmniBack II expectsthe size of the data buffer to be maintained and the contents to beoverwritten with the encrypted text.

� � � � �The encryption algorithm must generate encrypted text of the samelength as the original text.

MODULE


FUNCTION

extern intDeDecrypt (#if PROTOTYPES UCHAR *data, ULONG size#endif);

ARGUMENTS

data pointer to encrypted text buffer

size size of encrypted text buffer

7-49


RETURNS

0 Error

1 OK

DESCRIPTION

The encryption of the encrypted text should be done in-place. OmniBack IIexpects that the size of the data buffer will remain the same and that thecontents will be overwritten with the encrypted text.

MODULE


FUNCTION

extern intDeExit (#if PROTOTYPES void#endif);

ARGUMENTS

void

RETURNS

0 Error

1 OK

DESCRIPTION

This function is called to allow the data encryption module to perform apost-processing cleanup. Its return value is ignored.

7-50

�I�-�� L �¡ ¢C£ £3¤�¥3Ò� ��¡ ¦�¥.§� �¨ ¢ ¨I ��¥-©�ª��¡ ¦�«3¬5¨¼.Æ ·�º µ�½Q® Ý ® ¯�° ºVÞ ¸-¼�µ�½ Ã ²�¸ ·�· ® µ�¯Qß�Â °�µ�²�® ºVÞ ½

Customizing the Compression Algorithm

To reduce the number of media needed to perform a backup, you can enablethecompress option using theBackup options window. Thecompression used by OmniBack II is the Lempel-Ziv 4.3 compressionalgorithm. This is the same compression algorithm used by the Unixcompression utility and provides reasonable compression and speed for mostdata types. However, you may choose to implement another compressionalgorithm, customized for your type of data. Customizing the compressionalgorithm may provide better performance for the backup and restore ofspecific types of data (for example, graphics-oriented applications).

� � � � �Customizing of the encryption algorithm is supported on HP-UX only.

To customize the compression algorithm, you can write your owncompression code module, compile the module, and link it to the standardHP OmniBack II compression library. This library is calledlibdc.sl andis located in the/usr/omni/lib (on HP-UX 9.0x) or/opt/omni/lib(on HP-UX 10.x) directories. The following section describes how to createyour own compression module. For detailed information about developingUnix code, consult theHP-UX Programming Manual.

¼ ß � À � � �If you change the compression algorithm, OmniBack II will no longer be able todecompress data from backups performed with the previous algorithm. If this occurs,OmniBack II will restore the data in compressed form. Therefore, it is recommendedthat you only change the algorithm after careful planning. Frequent changes to thecompression algorithm increase the risk of data loss.

¼ ß � À � � �To restore a backup created using a different compression algorithm, you must firstrestore the version of the compression algorithm that was used to create the backupset you want to restore.

7-51

�I�-�� L �¡ ¢I£ £�¤C¥3Ò� ��¡ ¦�¥.§� �¨ ¢ ¨C ��¥-©�ª��¡ ¦�«3¬_¨¼�Æ ·3º µ�½Q® Ý ® ¯�° ºVÞ ¸-¼.µ�½ Ã ²�¸ ·�· ® µ�¯Qß�Â °�µ�²�® ºVÞ ½

Creating a Compression Code Module

This section provides an overview of the process for developing your owncode module for compression. For more detailed information, consult theHP-UX Programming Manual.

Creating and installing a new compression code module involves thefollowing tasks:

1. rename the original shared library (libdc.sl )

2. write the new code module

3. compile the new code module

4. link the new code module to the original shared library

5. rename the new shared library to the original shared library (libdc.sl )

� � � � �Since the compression shared library is accessed by the backup and restore DiskAgents, the shared libraries must be replaced on all hosts where the Disk Agents run,not just on the Cell Server host.

The data compression type identifiers used in the compression module areshown here:

DC_NONE 0 No data compression

DC_LZ43 0x0b0b0b0bLempel-Ziv 4.3

The following list briefly explains each function used and its purpose.

DcInit initializes the compression module and returns thecompression type

DcCompress the compression function

DcDecompress the stream decompression function

DcExit performs post-processing cleanup

The following section shows the data compression modules, with anexplanation following each function.

7-52


The module defines unique data encryption type identifiers.

#if !defined(UCHAR)#define UCHAR unsigned char#endif

#if !defined(ULONG)#define ULONG unsigned long#endif#define DC_NONE 0 /* No data compression */#define DC_LZ43 0x0b0b0b0b /* Lempel-Ziv 4.3 */

typedef int (*dcCallback)(UCHAR *, ULONG);

MODULE

Data Compression (Dc)

FUNCTION

extern ULONGDcInit (#if PROTOTYPES void#endif);

ARGUMENTS

void

RETURNS

DC_NONE Initialization failed, compression disabled

DC_LZ43 Initialization successful, Lempel-Ziv compression

DC_xxxx a customer-created and implemented compression type,wherexxx represents a customer-specified name

DESCRIPTION

This function is called by the Disk Agent’s initialization procedure atstartup. It should initialize the Data Compression module and indicate thecompression type.

REMARKS

Dynamic switching between different compression algorithms depending onthe type of input data is not available.

7-53


MODULE


FUNCTION

extern intDcCompress (#if PROTOTYPES dcCallback readCallback, dcCallback writeCallback#endif);

ARGUMENTS

readCallback A pointer to the data input callback

writeCallback A pointer to the data output callback

RETURNS

0 Error

1 OK

DESCRIPTION

This is the actual stream compression function. Input is received from thereadCallback function and output is written using thewriteCallbackfunction. Note the following guidelines when modifying this function:

• The compression module cannot detect the type of input and outputmedia. Therefore, the input should be treated as a read-only stream andthe output should be treated as a write-only stream.

• TheDcCompress function is called once for each file to be compressed.It reads the input until EOF (the input handler returns a value of zero) andmakes sure that all the intermediate output buffers are flushed before itsends a return value.

• Each call to thereadCallback is directly translated into aread()system call. Therefore, for better performance, the compression engineshould read its input in large chunks and store them in an internal inputdata buffer.

• ThereadCallback function returns the number of bytes read. Thisnumber can, under certain circumstances, be less than the number of bytesactually requested. The compression engine should not treat this as an

7-54


error but simply issue a second read (this is similar to BSD sockets, readsmay succeed partially). ThereadCallback returns a value of zero whenan error occurs or at EOF.

• ThewriteCallback function always sends a return value. If an erroroccurs, thewriteCallback return value is zero.

ThereadCallback return values are:

>0 Number of bytes read

0 Error or EOF

ThewriteCallback return values are:

>0 number of bytes written

0 Error

REMARKS

Never call thereadCallback to read or write zero bytes, as the returnvalue will be zero which means "Error or EOF."

MODULE


FUNCTION

extern intDcDecompress (#if PROTOTYPES dcCallback readCallback, dcCallback writeCallback#endif);

ARGUMENTS

readCallback A pointer to the data input callback

writeCallback A pointer to the data output callback

The return values are:

0 Error

1 OK

7-55


DESCRIPTION

This is the actual stream decompression function. It receives its input datausing thereadCallback data input function and writes its output using thewriteCallback output function. Note the following guidelines whenmodifying this function:

• The nature of the input and output media is unknown to thedecompression module. Therefore, the input should be treated as a read-only stream and the output should be treated as a write-only stream.

• The DcDecompress function is called once for each file to bedecompressed. It reads its input until EOF (the input handler returns zero)and checks that all intermediate output buffers are flushed before it sendsa return value.

• Both input and output can be done in byte chunks of arbitrary length. ThereadCallback function returns data from an internal OmniBack II databuffer. However, for the best performance, it is recommended that outputbe sent in larger chunks, since calls to thewriteCallback function canbe directly translated intowrite() system calls.

• ThereadCallback function can partially succeed. A return value ofzero denotes either an error or the end of the current file beingdecompressed. ThewriteCallback function always succeedscompletely and never reports any errors back.

ThereadCallback return values are:

>0 Number of bytes read

0 Error or EOF

ThewriteCallback return values are:

>0 Number of bytes written

0 Error or EOF

REMARKS

Never instruct thereadCallback function to read zero bytes, because thisresults in a return value of zero, which means "Error or EOF." For the samereason, never attempt to write zero bytes.

7-56


MODULE


FUNCTION

extern intDcExit (#if PROTOTYPES void#endif);

ARGUMENTS

void

RETURNS

0 Error

1 OK

DESCRIPTION

This function allows the data compression module to perform post-processing cleanup actions. Its return value is ignored.

8-1

8

Maintaining the OmniBack II Database

8-2

à �� 3¬5 �� á.¬5â�¦-�I�-�� L �¡ ¢I£ £�ã� �¬5 �ä� �¨ ¦

In This Chapter

This chapter describes how to maintain and back up the OmniBack IIdatabase. This database is used to record the following information:

• configured devices, media, and pools• usage and condition of the media in the pools• date and time backups are started• type of backups• directories, files, and disks that were backed up• file positions on the media• messages resulting from a backup or restore session• protection status of the data contained on the backup media

Maintaining the database used to store this information consists of threetasks:

• managing the growth of the database• backing up the database for recoverability• maintaining the integrity of the database

Each of these tasks is explained in detail in this chapter.

8-3

à �� 3¬5 �� á.¬5â�¦-�I�-�� L �¡ ¢I£ £�ã. �¬5 �ä� �¨ ¦À ¯ ·3º ¹�Â Â ® ¯�°Q¹�¯�´Q¼�µ�¯!å+°�Æ�²�® ¯�° ºVÞ ¸ Õ ¹ º ¹�Ül¹ · ¸

Installing and Configuring the Database

The OmniBack II database is installed to the/var/opt/omni/db directoryon a local disk of the Cell Server.

� � � � �The database must be located on local disks and not on NFS mounted disks.

The OmniBack II database consists of two parts:

MMDB Media Management Database: Stores information aboutbackup devices and their configuration and media usedfor backup.

CDB Catalog Database: Stores information about data backedup such as files, directories, versions, and so on.

In an ordinary, single cell environment, both parts of the database are locatedon the same Cell Server. In a multi-cell environment enabled with theAdvanced Backup Manager license, you can configure a common MMDBdatabase for many cells. SeeHP OpenView OmniBack II Advanced BackupManager for more information.

8-4

à �� 3¬5 �� á.¬5â�¦-�I�-�� L �¡ ¢I£ £�ã� �¬5 �ä� �¨ ¦Å ¹�¯�¹�°�® ¯�° ºVÞ ¸>ÁC²�µ!× º%Þ µvÇ ºVÞ ¸ Õ ¹ º ¹�Ü�¹ · ¸

Managing the Growth of the Database

The CDB is the largest part of the database and occupies approximately 80-85% of thee database. Thefvers.dat file is the largest file of the CDB and

is located in the/var/opt/omni/db/cdb directory. OmniBack II uses thesize of thefvers.dat file to calculate the size of the database.

A general estimate for the size of the database is approximately 2% of thedata being backed up. Thus, if the data is 100GB, the database will occupyapproximately 2GB.

It is possible to enlarge the size of the database. See “Enlarging the Size ofthe Database” on page8-10 for more information.

� � � � �Be sure that you have enough free space on a disk for the database. If the databaseruns out of disk space during a backup, the database will become incomplete.

Managing the Growth of the Database

The growth and size of the OmniBack II database are determined by thefollowing factors:

• the number of files and directories backed up

• the number of logged messages

• the amount of details on backed-up files and directories stored in thedatabase

• the protection of backup information about backed-up data in the database

• the number of backup and restore sessions

8-5

à �� 3¬5 �� á.¬5â�¦-�I�-�� L �¡ ¢I£ £�ã. �¬5 �ä� �¨ ¦Å ¹�¯�¹�°�® ¯�° ºVÞ ¸-ÁI²�µ!× ºVÞ µ!Ç ºVÞ ¸ Õ ¹ º ¹�Ül¹ · ¸

Estimating the Size of the Database

This section provides an example how you can calculate the size of theOmniBack II database based on the number of files and directories you backup. The basis for this calculation is that for each file or directory backed up,the full backup information about each occupies approximately 60 bytes.

Let us assume 50 workstations each with approximatelly 40000 files. We doa weekly full backup and daily incrementals and we keep 6 full backups(protection is set to 6 weeks). The estimated size of the incremental backupinformation is 20% of the full.

50 x 40000 x 60B = 120MB for one full backup

120MB x 20% x 5 = 120MB for all incrementals between two full backups

120MB x 6 + 120MB = 840MB six full backups and incrementals = fulldatabase size

Therefore, the estimated size for the database is 840MB. If this number istoo high, check the following sections for information on how to reduce thisnumber.

Changing the Number of Logged Messages

The level of detail recorded in the database relates to theReport Level andthe file logging of the backup options. If you set the Report Level towarning , all screen messages at thewarning level and higher are recordedin the database. The number of messages recorded will be higher than if youset the Report Level tocritical .

See “Selecting the Filesystem Backup Options” on page4-11 and “Selectingthe Rawdisk Backup Options” on page4-15 for instructions.

Changing the Amount of Details on Files Stored in the Database

OmniBack II provides three levels of the amount of details on files anddirectories stored in the database.

Log All This is the default option. All backed-up files are loggedto the database. This complete information allows you tosearch for backed-up files and allows OmniBack II to fastposition on the tape when restoring a specific file.

8-6


However, this information may take a lot of space if thereare many files.

Log Directories Details on directories only are stored in the database. Thislimits the search feature during restore and you will onlybe able to browse directories. However, OmniBack II stillperforms fast positioning because a file is located on thetape near the directory where it actually resides. Thisoption is suitable for filesystems with many auto-generated files, such as news and mail systems where youusually do full restores.

No Log No details on files or directories are logged in thedatabase. You will not be able to search and browse filesand directories. The restore will take longer becauseOmniBack II cannot fast position on the tape and willread from the start of the backup.

See “Selecting the Filesystem Backup Options” on page4-11 and “Selectingthe Rawdisk Backup Options” on page4-15 for instructions.

Changing the Protection of Backup Information

OmniBack II allows you to set protection (see “Using Backup Options” onpage4-26 for more information) both for data backed up and backupinformation about data in the CDB. This is also called catalog retention. Youcan therefore specify that backup information be kept in the database for alimited time only, for example, as long as the data is protected. OmniBack IIautomatically removes backup information with expired protection from thedatabase, thus keeping the database up-to-date.

Changing the Number of Backup and Restore Sessions

The other factor in estimating database growth is the number of backup andrestore sessions. A schedule with frequent full backups will result in thefaster growth of the database.

8-7


Purging Obsolete Data from the Database

OmniBack II automatically removes obsolete information from the CDB atregular time intervals. Purging removes unneeded information from thedatabase and frees space for new information. Note that by purging the CDByou do not actually shrink the size of the files - you only make space for newinformation.

The following variables in the global options file influence the behavior ofthe automatic purge process:

DBPurgeSuspension If it is set to 1 (default), purge sessionmanager will suspend its executionwhile backup/restore sessions are inprogress.

DBPurgeOptions Specifies the database purge options;when old aborted sessions and obsoletefiles may be removed.

DBPurgeStartTime Specifies the purge session start times

To Purge Manually

The following command purges information relating to restore sessions aswell as obsolete (overwritten) backup sessions and sessions without anymedia such as failed or aborted sessions.

omnidb -purge

OmniBack II records detailed data such as the names of each file beingbacked up during each session in the CDB. You can create space for newdata by removing this data from the CDB. You can remove detailed data fora backed-up object in one specific backup session. The restore of single fileswill be slower since OmniBack II has to search from the beginning of themedia for the file.

You can mark detailed data for removing by using theomnidb -stripcommand with various options. See theomnidb manpage for a completedescription of the command options.

Example:

8-8


omnidb -strip

marks the details catalog of all objects with expired protection.

If you combine this command with-session sessionID, all objects(filesystems) backed up in the specified session are marked.

If you combine this command with-session sessionID and-f ilesystem filesystemID, the specified filesystem in the specifiedsession is marked.

If you combine this command withdays -f ilesystem filesystemID,all versions of the specified filesystem older thandays are marked.

� � � � �These commands do not actually delete data from the database, but just mark the datafor deleting. Data is actually removed from the database when the automatic purginghappens or by manually running theomnidbutil -purge command afterwards.

To Delete an Unneeded Session from the Database

OmniBack II keeps track of how long data on a medium is protected (see“Using Backup Options” on page4-26 for more information). When theprotection expires, the session will be overwritten by newer backups.

OmniBack II provides a way to delete an unneeded session from thedatabase.

1. From theMonitor window, chooseView → Previous Sessions.

2. Select the session you want to delete and chooseActions → PurgeSession.

The session disappears from the list.

The following happens:

• Protection is removed from the session. This means that the session willbe overwritten during future backups.

• All detail data (backed-up files and messages) about the session isremoved from the database.

• The session itself remains on the media until it is overwritten by the nextbackup. Therefore, you can still see or restore the session using theList

8-9


from Media option.

Shrinking the Size of the Database File

By using the procedures above, you do not really shrink the size of thedatabase; you just remove obsolete or detail data and create more space fornew data-. If you really must reduce the size of the database files, the onlypossible way is to copy the database to an ASCII file and then read it back.

To ensure the integrity of the database, be sure that backups, restores, orGUIs are not running before copying the database.

Is it Feasible to Shrink the Database?

You can use theomnidbutil -info command to see how many recordsare actually used and how many are occupied by data. If the numbers varyconsiderably, it is feasible to shrink the database.

Copying the Database to an ASCII File

Before you copy the database to an ASCII file, we recommend running theomnidb -purge command.

Use the following command to copy the database to an ASCII file.

omnidbutil -writeascii [-mmdb directory] [-cdb directory][-no_details]

You must specify which part of the database you want to copy, MMDB,CDB, or both.

For more details on theomnidbutil command, see the manpage.

� � � � �For this operation you will need approximately 50% more disk space than the size ofyour database.This operation may also take considerable time, for example, on an HP Series 800E35 system, the writeascii of the 500 Mb database may take three hours.

8-10


Reading the Database from an ASCII File

Note that by reading the database from the ASCII file you will lose any datawritten to the database after it was copied to the ASCII file. Make sure thatthe database is large enough for data in the ASCII file. If needed, use theinstuctions in the next section to enlarge the size of the database.

Use the following command to read the database from an ASCII file.

omnidbutil -readascii [-mmdb file] [-cdb file] [-no_details]

If you encounter problems with this command, you must first initialize thedatabase with theomnidbinit command.

For more details on theomnidbutil command, see the manpage.

If you read the CDB or MMDB individually, you may need to synchronizethe content of both databases with the following command:

omnidbutil -cdbsync CDB_hostname

As a result of a database synchronization, protection for some media maychange and some backed up objects may dissapear from the CDB.

Enlarging the Size of the Database

The size of the OmniBack II database is limited to 2GB by the UNIX filessize limit. If this size is not sufficient for your needs, you can enlarge the sizeof the database.

The procedure creates new, extendedfvers.dat files where new data isstored. The maximum size of each new file is 2GB, and the maximum size ofthe whole database is 8GB. It is important to carefully plan the location ofdatabase extension files.

8-11


� � � � �Once you define the extendedfvers.dat files, you cannot reduce their size anymore.

1. Be sure that no backup, restore, or media management sessions arerunning in the cell. Be sure that no Graphical User Interfaces are runningon the cell.

2. On the Cell Server, run the following command:

omnidbutil -extend pathname -maxsize size

wherepathname is the full path to the directory where you want to putthe new database files, andsize is the size of the database extension file(maximum 2GB).

For example:

omnidbutil -extend /var/opt/omni/db/cdb -maxsize 2000

will create an additional database file in the same directory as the originaldatabase and extend the size by 2000MB, thus giving a full database sizeof 4GB. To extend the database even more, repeat the command.

OmniBack II creates a new, extendedfvers.dat N file in the specifieddirectory each time you run the command. The database extension files arebacked up as part of the database backup and are restored with databaserecovery. See “Backing up the Database Using a Datalist” on page8-13 and“Recovering the Database” on page8-15 for more information.

8-12

à �� 3¬5 �� á.¬5â�¦-�I�-�� L �¡ ¢I£ £�ã� �¬5 �ä� �¨ ¦¾.¹�»�¿�® ¯�° �Ã)º%Þ ¸ Õ ¹ º ¹�Ü�¹ · ¸

Backing Up the Database

The database is an extremely important part of OmniBack II and must bebacked up on a regular basis. We recommend the following:

• Create a separate datalist for the database. This simplifies scheduling andrestoring in case of a disk crash.

• Schedule a database backup every night. This ensures you always have anup-to-date backup of the database. You can set the protection to only a fewdays.

• Make the database backup on a separate medium, on a separate device ifpossible, for example, to a standalone DDS. This greatly simplifieseventual restore, since you know precisely on which medium yourdatabase is backed up.

• Create and use a separate pool for backing up your database. Thissimplifies the recovery of the database.

The database backup runs online. The database is in use whenever you areusing the Graphical User Interface or when a backup or restore session is inprogress. OmniBack II provides an automatic action to back up the databasethat shuts down the database, backs it up, and then restarts it.

OmniBack II also maintains the integrity of the database by preventing youfrom backing up a corrupted database. When you initiate a backup of thedatabase, OmniBack II first performs a database check. If the database iscorrupt, the backup fails. This prevents you from later restoring a corrupteddatabase.

The database backup backs up all OmniBack II configuration data, including/etc/opt/omni and/var/opt/omni/db directories and databaseextension files (see “Enlarging the Size of the Database” on page8-10 formore information), not just the database.

8-13

à �� 3¬5 �� á.¬5â�¦-�I�-�� L �¡ ¢I£ £�ã. �¬5 �ä� �¨ ¦¾�¹�»�¿�® ¯�° �Ã)ºVÞ ¸ Õ ¹ º ¹�Ül¹ · ¸

Backing up the Database Using a Datalist

Backing up the database consists of two steps:

• Adding the object (OmniBack II Database) to a datalist• Performing a backup using this datalist

Creating a Datalist to Back up the Database

1. From theOmniBack II Backup Editor window, chooseObject →Add → OmniBack II Database to add the database to a new or existingdatalist.

Running Backups of the Database

Once you have created the datalist for the database, you can schedule thedatalist or run an interactive backup.

You can use theomnib command with the-datalist option to performthe database backup. See theomnib manpage for details.

8-14

à �� 3¬5 �� á.¬5â�¦-�I�-�� L �¡ ¢I£ £�ã� �¬5 �ä� �¨ ¦Ø.¸ ·3º µ�²�® ¯�° ºVÞ ¸ Õ ¹ º ¹�Ü�¹ · ¸

Restoring the Database

If you have backed up the OmniBack II database using the proceduredescribed in “Backing Up the Database” on page8-12, you can recover thedatabase after restoring it to a different directory.

Restoring the Database consists of two basic steps:

1. Restoring the database to an alternative directory

2. Recovering the database

¼ ß � À � � �Please note the following precautions for the recovery of the database:

• You must restore the database from a backup that was created using themethod described in the “Backing Up the Database” on page8-12. If youtry to restore the database from a regular backup, you will corrupt thedatabase!

• You must restore the database into an alternative directory because thedatabase is in use during any restore session. The-into option is used tospecify the alternative directory for the database. If you do not use the-into option, you will get an error message.

• It is recommended that you create a copy of all database files by firstshutting down all OmniBack II processes using theomnisv.sh -stopcommand and then copying all database files to a temporary directory.

Graphical User Interface Method

To restore the database using this method, you use the normal procedure forrestoring single files, except that you use theFileset Restore Optionswindow to specify an alternative directory for the database. To restore thedatabase, follow these steps:

1. From theOmniBack II Main menu, selectRestore to open theOmniBack II Restore window with a list of all the objects which havebeen backed up.

2. Double-click theOmniDb object to open theDatabase Restorewindow.

8-15

à �� 3¬5 �� á.¬5â�¦-�I�-�� L �¡ ¢I£ £�ã. �¬5 �ä� �¨ ¦Ø.¸ ·3º µ�²�® ¯�° ºVÞ ¸ Õ ¹ º ¹�Ül¹ · ¸

3. ChooseActions → Restore OmniBack II DB… to open theFilesystem Restore window.

By default, the database is restored to the/tmp directory. Do not restorethe database to the root directory.

To select specific restore options, chooseDatabase Restore Options.

4. ChooseOK to open theOmniBack II Restore Monitor windowwhere you can start restore.

After restore, the complete database directory is restore to/tmp . If you usedatabase extension files, they are also restored to/tmp .

Command-Line Interface Method

You can use the-omnidb option to restore the database. The commandsyntax is shown here:

omnir -omnidb Hostname:Mountpoint [label] -session sessionname-into directory name

If you specified thelabel when backing up the database, you must specifythe label when restoring the database.

The-into option is required when restoring the database.

Do not restore the database to the root directory.

After restore, the complete database directory is restore to/tmp . If you usedatabase extension files, they are also restored to/tmp .

Recovering the Database

After you have used the Graphical User Interface method or the command-line method to restore the database, you must copy the restored databasefrom the alternative directory back to the original directory. When therestore of the database is finished, follow these steps:

1. Stop all running OmniBack II sessions. If the Graphical User Interface is

8-16

à �� 3¬5 �� á.¬5â�¦-�I�-�� L �¡ ¢I£ £�ã� �¬5 �ä� �¨ ¦Ø.¸ ·3º µ�²�® ¯�° ºVÞ ¸ Õ ¹ º ¹�Ü�¹ · ¸

in use, exit the interface. This prevents access to the database.

2. Use theomnisv.sh -stop command to stop all OmniBack II processes.

3. Move the existing database directory/var/opt/omni/db to atemporary location so that the directory is empty. This prevents mergingof old and new files.

4. Copy the database files from the alternative directory to the originaldirectory/var/opt/omni/db . If you have extension files on some otherdirectory, be sure to copy them to the original position as well.

5. Make sure that the/var/opt/omni/db/syslog directory exists and isempty. If it is not empty, delete all the files from this directory.

6. Use theomnisv.sh -start command to restart the OmniBack IIdaemons.

� � � � �With the database backup, all configuration files such as datalists, barlists, schedulinginformation, cell configuration, were also backed up.You can also recreate these files by copying the complete directory structure.

8-17

à �� 3¬5 �� á.¬5â�¦-�I�-�� L �¡ ¢I£ £�ã. �¬5 �ä� �¨ ¦Å µ!Ö�® ¯�° ºVÞ ¸ Õ ¹ º ¹�Ü�¹ · ¸ º µQß�¯�µ º%Þ ¸�²LÓ�µ ·3º

Moving the Database to Another Host

HP OmniBack II provides two ways for you to move the OmniBack IIdatabase to another host. You can either move the database direcusingrecovery backup or copy the database to ASCII files and then move theASCII files to the other host. Use the one that is simpler for your situation.Both methods are described below.

Moving the database using recovery backup

If you have a backup of the OmniBack II database, you can simply restorethe database to another host using database receovery procedure.

For instructions how to back up the database, see “Backing Up theDatabase” on page8-12.

For instructions how to recover a database, see “Restoring the Database” onpage8-14.

Copying the Database to an ASCII file and Moving the File

Using this method, you copy the database to ASCII files and then move theASCII files to the new host. To do this, follow these steps:

1. Export the database to ASCII files using the following command. Thiscreates two ASCII files with the data from MMDB adn CDB in thedirectory you specify:

omnidbutil -writeascii [-mmdb directory] [-cdb directory][-no_details]

The-no_details option prevents exporting of the detail catalogs.

2. Move the files to the other host usingrcp , ftp , or NFS mount .

3. If you have the database extensions files configured, create similarextension files on the new location.

4. Import the database on the otherhost using the following command:

8-18

à �� 3¬5 �� á.¬5â�¦-�I�-�� L �¡ ¢I£ £�ã� �¬5 �ä� �¨ ¦Å µ!Ö�® ¯�° ºVÞ ¸ Õ ¹ º ¹�Ü�¹ · ¸ º µQß�¯�µ ºVÞ ¸�²LÓ�µ ·3º

omnidbutil -readascii [-mmdb directory] [-cdb directory][-no_details]

The-no_details option prevents importing the detail catalogs.

See a manpage for theomnidbutil command for a detailed syntaxdescription.

9-1

9

Using Complex Devices and Libraries

9-2

æ ¨ � ��á>©�ª��-«�ç ¦�èmã�¦3Ò�� ¡ ¦�¨C ��¥-é�� ä�êq �êq� ¦�¨

In This Chapter

Any device that has more than a single drive and a single cartridge isconsidered a complex device. For example, libraries provide you access to alarge volume of data within a few seconds, without operator intervention.Allowing convenient access to a library of tape and magneto-optical platters,these devices can offer capacities of up to several 100 gigabytes. Thischapter helps you understand how to:

• Manage complex devices

• Configure a SCSI-II library

• Configure a non-standard library

9-3

æ ¨ � ��á>©�ª��>«�ç ¦�èmã�¦3Ò�� ¡ ¦�¨C ��¥-é�� ä�êq �êq� ¦�¨Å ¹�¯�¹�°�® ¯�°Q¼�µ�½ Ã Â ¸ ¶NÕ ¸3Ö�® »�¸ · ×ë® ºVÞQ� ½Q¯�® ¾�¹�»�¿>À À

Managing Complex Devices with OmniBack II

OmniBack II’s media management services, device support features, and theOmniBack II configuration database work together to control the behavior ofcomplex devices as described in this chapter.

Complex Device Types

OmniBack II supports three types of complex devices:

Device Chains

A device chain is a set of standalone devices treated as one device byOmniBack II. All physical devices in a device chainmust belong to thesame class. Devices are used sequentially. Device chains do not supportparallel backups thus reducing possible performance.

Stackers

A stacker is a single device usually with only one drive. A stacker takes amedium from a "stack" (its repository) and inserts the medium into its drive.This exchange is always limited to ejecting the medium already in the driveand inserting the next medium from the stack. A stacker cannot randomlypick a medium from its repository.

Libraries

Libraries, also called exchangers, jukeboxes, or carousels, can randomlypick a medium from its repository and insert the medium in the drive.Libraries differ in repository sizes, exchanging techniques, and number ofdrives. Some libraries can even read the bar code on the media in therepository.

9-4

æ ¨ � ��á>©�ª��-«�ç ¦�èmã�¦3Ò�� ¡ ¦�¨C ��¥-é�� ä�êq �êq� ¦�¨Å ¹�¯�¹�°�® ¯�°Q¼�µ�½ Ã Â ¸ ¶ìÕ ¸3Ö�® »�¸ · ×m® º%ÞQ� ½Q¯�® ¾�¹�»�¿-À À

How OmniBack II Functions with Complex Devices

OmniBack II performs the following operations on complex devices:

• backing up data• restoring data• initializing media to be used for backup• verifying data off-line• list cataloging• importing

How OmniBack II operates on different complex device types is explainedbelow.

Device Chains

Backup

When OmniBack II detects the end of a medium during a backup session,OmniBack II automatically switches to the next drive configured with thelogical device. When all devices in the chain are used, OmniBack II issues amount request. The user must then replace all the media in each drive. WhenOmniBack II detects that the mount request has been satisfied, it startsbacking up again from the first drive.

Restore

How OmniBack II operates on a device chain during restore is analogous tohow it operates during backup. OmniBack II starts scanning the first drive ofthe device chain to look for the media it needs for restore. If the neededmedia is not in the first drive, OmniBack II automatically starts looking for itin the next drive and so on until OmniBack II finds the drive with the correctmedium or until it comes to the last drive of the logical device. If OmniBackII cannot find the required medium, it issues a mount request for the last

9-5

æ ¨ � ��á>©�ª��>«�ç ¦�èmã�¦3Ò�� ¡ ¦�¨C ��¥-é�� ä�êq �êq� ¦�¨Å ¹�¯�¹�°�® ¯�°Q¼�µ�½ Ã Â ¸ ¶NÕ ¸3Ö�® »�¸ · ×ë® ºVÞQ� ½Q¯�® ¾�¹�»�¿>À À

drive. If OmniBack II finds the required medium, but still needs anothermedium to complete the restore, OmniBack II scans the device chain fromthe current position to the end of the device chain for the needed medium.

Initialize

OmniBack II initializes media in the first device of the device chain only.

Verification

OmniBack II verifies media in the first device of the device chain only.

Stackers

Backup

OmniBack II performs backups to a stacker in the same manner as for devicechains. The only difference is that instead of changing the drive currently inuse, OmniBack II picks the next medium from the repository. If no mediumis available, OmniBack II issues a mount request.

Restore

OmniBack II performs restores from stackers in the same manner as fordevice chains. The media in the drive is exchanged until the desired mediumis reached. If OmniBack II needs another medium to complete the restore,OmniBack II inserts media from the stack until the needed medium is found.If no media is available, OmniBack II issues a mount request.

Initialize

OmniBack II initializes the medium that is at the top of the stack.You caneject the initialized medium to go to the next one.

Verification

The medium that is at the top of the stack is verified.

9-6

æ ¨ � ��á>©�ª��-«�ç ¦�èmã�¦3Ò�� ¡ ¦�¨C ��¥-é�� ä�êq �êq� ¦�¨Å ¹�¯�¹�°�® ¯�°Q¼�µ�½ Ã Â ¸ ¶ìÕ ¸3Ö�® »�¸ · ×m® º%ÞQ� ½Q¯�® ¾�¹�»�¿-À À

Libraries

Backup

OmniBack II keeps a record of which media are in the repository of alibrary. This information is updated when a medium is entered or ejectedfrom the repository. OmniBack II always tries to allocate the media it willuse for backup from the contents of the repository. If OmniBack II cannotbackup using media from the repository or if OmniBack II must use amedium from the top of the Prealloc List, OmniBack II will issue a mountrequest.

If media in the repository is manually removed (you use the Eject button),you must rescan the repository so OmniBack II can update its MediaManagement database.

� � � � �We recommend always operating a library via the OmniBack II software. If youcircumvent the software and do operations on the library manually, you riskconfusing the software which will result in misleading operations messages.

Restore

If the media is in the repository, it is automatically inserted into drive in thecorrect sequence and OmniBack II proceeds with the restore. Otherwise,OmniBack II issues a mount request.

Initialization

Specify slots for all the media in the library repository that are to beinitialized.

Verification

Specify slots for all the media in the library repository that are to be verified.

9-7

æ ¨ � ��á>©�ª��>«�ç ¦�èmã�¦3Ò�� ¡ ¦�¨C ��¥-é�� ä�êq �êq� ¦�¨¼.µ�¯!å+°�Æ�²�® ¯�°Q¹-ÉL¼�ÉLÀ ³7À À�í�® Ü�²�¹�²�Ê

Configuring a SCSI-II Library

A generic tape/optical library is a complex mechanical device containingone or more data drive mechanisms, an internal magazine (repository) ofmedia, and a mechanical picker capable of loading and unloading the mediainto the drives under software control.

The generic library has a SCSI ID for each data drive and one for the picker.For instance, an HP optical jukebox containing two optical drives has threeSCSI IDs — one for each drive and a third for the picker. One exception tothis is the HP SureStore 12000e Library which allows both mechanisms, thedata drive and the picker, to be accessed through the same SCSI ID butdifferent SCSI Logical Units (lu).

Each repository slot of a library holds one cartridge. OmniBack II assigns anumerical ID to each slot within the repository starting from one. You referto these slots by ID numbers when you configure the logical device.

For example, a library with 6 repository slots will have the slot IDs 1, 2, 3, 4,5, and 6. If the library has multiple drives, each drive is also referred to by anID starting with the number one. A 4-drive library, for example, will havethe drive IDs 1, 2, 3, and 4. A single drive library is referred to by the driveID number “1.”

î ï ð ñ òNote that the above slot and drive IDs are NOT the physical element IDs returned bythe library in response to a SCSI mode sense command (ioctl ). The physicalelement IDs are determined by the Media Agent based on the above slot and driveIDs and the mode sense information returned by the library when a backup is run.OmniBack II has provided you with this numbering scheme so that you do not haveto know the physical element IDs of the library to complete the logical deviceconfiguration.

During the configuration of the library, you configure the drives you want touse with OmniBack II.

9-8

ó.ô õ ö�÷>ø�ù�ú-û�ü ý�þmÿ�ý��õ � ý�ô��ö��õ ��qõ ý�ô �� !� ��"�� #��%$

Example of a Library Configuration

The following example will demonstrate how to configure a double-driveDDS library with a repository of 50 slots and connected to an HP9000/S700system. Configuring a device on other supported systems is similar. Refer toyour system administration manuals for instructions how to find theappropriate device files or the appropriate SCSI-II addresses of devices.

The basic steps involved in configuring the library are:

1. Creating a Media Pool for media in the library.

2. Selecting the device files.

3. Configuring the drives.

Creating a media pool

See “The Media Pool Approach” on page3-14 for more information aboutmedia pool and how to create them.

Selecting the Device Files

î ï ð ñ òIf you are configuring your library on an HP9000/S800 system, you will have toinstall theSPT driver which is available in the patch PHKL_5405 (for HP-UX 9.04or later), PHKL_5406 (for HP-UX 10.x.), PHKL_10356 (for HP-UX 10.01),PHKL_10507 (for HP-UX 10.10), or PHKL_10443 (for HP-UX 10.20). Be sure thatyou follow carefully the instructions provided with the patch. You must install thecorrect driver for your devices, select the correct SCSI address, and create a devicefile for the device you will use with OmniBack II.When this driver is installed and OmniBack II performs backup or restore sessions,we do not recommend the use of applications runningioscan , such asSAM. Thiscould cause the system to reboot.

1. Determine the Unix device files (SCSI-II addresses) that correspond to

9-9

ó�ô õ ö�÷>ø�ù�ú>û�ü ý�þmÿ�ý��õ � ý�ô��ö��õ ��qõ ý�ô �� !� ��"�� #��%$

the library drives.

The double-drive DDS library in our example would use the device files/dev/rmt/1m and/dev/rmt/2m to address the library drives(assuming the data drive SCSI IDs are 1 and 2).

2. Determine the UNIX device file (SCSI-II address) that corresponds to thelibrary picker mechanism.

In our example, the device files are in the/dev/scsi directory. We willuse the device file/dev/scsi/0 . The "0" at the end of the device filename indicates that SCSI ID for the library picker device is 0.

î ï ð ñ òThe HP SureStore 12000e Library does not have a dedicated SCSI ID for the pickerdevice but accepts both data drive access commands and picker commands throughthe same SCSI ID. However, the data drive access commands must be directed toSCSI lu 0 and the picker commands to SCSI lu 1. Therefore, if you are using the HPSureStore 12000e Library, create a new device file that will allow you to address thepicker through the same SCSI ID as the data drive (ID number 1) but referring to adifferent SCSI lu (ID number 1):

mknod /dev/scsi/1.lu1 c 105 0x201110--- --

| ||| |---- Picker SCSI lu (1)| ----- Picker SCSI ID| (the same as data| drive SCSI ID = 1)---------- scsi_pt driver major

3. Using the OmniBack IIuma utility verifies that the picker identifies itselfcorrectly as a SCSI-II Library:

# echo “inq” | /opt/omni/lbin/uma -ioctl /dev/scsi/0 /dev/scsi/0> inq

----------- | Note: Use /dev/scsi/1.lu1 for the HP SureStore 12000e

If the picker does not identify itself correctly, then the selected device filedoes not refer to a SCSI-II library picker. Double check that the picker isreferred to by SCSI ID 0. If you are configuring an HP SureStore 12000eLibrary, make sure you have created the proper device file.

4. Using the OmniBack IIuma utility to force the library to re-initializeitself:

9-10

ó.ô õ ö�÷>ø�ù�ú-û�ü ý�þmÿ�ý��õ � ý�ô��ö��õ ��qõ ý�ô �� !� ��"�� #��%$

# echo "init" | /opt/omni/lbin/uma -ioctl /dev/scsi/0/dev/scsi/0> init ----------- | Note: Use /dev/scsi/1.lu1 for the HP SureStore 12000e

Configuring Drives for the Library

Example of configuring a library with 2 drives.

1. Once you have determined the correct UNIX device files for the librarydrives and picker, configure the SCSI-II Library. ChooseDevices &Media from theOmniBack II Main menu.

2. SelectEdit → Create → SCSI II Library to open theLogicalDevice Editor window. Enter the needed information. For detailedfield descriptions, refer to the online help.

3. In theSCSI II Control Device field of theLogical DeviceEditor window, enter the pathname of the Unix device file thatcorresponds to the library’s picker mechanism. In our example, thepathname of the UNIX device file is/dev/scsi/0 .

4. In theExchanger Data Device field of theLogical DeviceEditor - Drive window, enter the pathname of the Unix device filecorresponding to each library drive. For tape libraries, the pathname willbe one of the files from the/dev/rmt directory. In our example, thepathname would be/dev/rmt/1m .

5. In theDrive Index field, enter the ID number of the drive you wantOmniBack II to use for the backup or restore. In our example, "1."

LogicalDevice

Drive Device File Control File

DRIVE_1 1 /dev/rmt/1m /dev/scsi/0

DRIVE_2 2 /dev/rmt/2m /dev/scsi/0

Table 9-1 Example Device Configuration

9-11

ó�ô õ ö�÷>ø�ù�ú>û�ü ý�þmÿ�ý��õ � ý�ô��ö��õ ��qõ ý�ô �� !� ��"�� #��%$

î ï ð ñ òTake care when configuring the logical device that you specify the right device filefor the right drive index. If you do not, you could set it up so that the library loadsmedia into device 2 and reads from device 1. This is important for a library with twoor more drives.

You do not have to set theAdvanced Options button. These options are set todefault values and normally do not need to be adjusted.

This completes the configuration of the first example logical device,DRIVE_1. To configure the second driveDRIVE_2, follow the same steps.

To Verify the Configuration

From theLibrary Management window, select a range of slots andchooseEdit → Scan...If the device is configured correctly, OmniBack II willbe able to load, read, and unload each medium inside the library repository.

9-12

ó.ô õ ö�÷>ø�ù�ú-û�ü ý�þmÿ�ý��õ � ý�ô��ö��õ ��qõ ý�ô �� î ��& !�(')��&*��*�"�� #�� $,+)��-�.�/�01� ')2 ï43 �� 5��6�7��

Configuring a Non-Standard Library for Usewith OmniBack II

In order to control a non-standard library with OmniBack II, you must writea Library Control Script. This script is started whenever the OmniBack IIMedia Agent needs to load or unload a medium from a repository. To keepthe script interface as simple as possible but flexible enough to handle alarge variety of library devices, the OmniBack II Media Agent defines onlytwo operations:

• medium load

• medium unload

Both the load and unload operations are invoked through the same externalscript which must be capable of parsing our predefined options andparameters.

How OmniBack II works with non-standard libraries

At runtime, the OmniBack II Media Agent will call the external script,passing to the script all information necessary to load or unload media fromthe repository. As soon as the script successfully completes the action, itshould return an exit code of zero. If the script terminates unsuccessfully, apositive integer is returned. During the execution of the script, any messagesread from itsstdout will be picked up by the Media Agent and passed tothe controlling Session Manager as error messages at level MINOR. Thescript is called by OmniBack II using thepopen() mechanism.

î ï ð ñ òNote that using an external script interface is a potential security leak since theOmniBack II Media Agents are always executed with root permissions.

To load a medium into the designated library drive, OmniBack II invokes theexternal script as:

%<script>

9-13

ó�ô õ ö�÷>ø�ù�ú>û�ü ý�þmÿ�ý��õ � ý�ô��ö��õ ��qõ ý�ô �� î �� !�(')��*��*1"&� #��%$�+8��9-�.�/:0;� ')2 ï43 �� 5��6�7,� �

-drive %<data drive index> -slot %<one from the list of slot addresses> [-flip] %<if medium should be flipped during transport> -load

Similarly, to unload a medium from a drive into its original position,OmniBack II invokes the script as:

%<script> -drive %<data drive index> -slot %<one from the list of slot addresses> [-flip] %<if medium should be flipped during transport> -unload

Note that the OmniBack II Media Agent keeps track of whether the currentmedium used is flipped and what its original position was in the libraryrepository slot. When the medium is unloaded, it will be flipped again as it isreturned to the repository.

The Media Agent assumes that the library is on-line and reset to anoperational state before OmniBack II uses it. In a previous section of thischapter we recommended you always operate the library via the OmniBackII software. If someone circumvents the software and does operations on thelibrary manually, the result will be inconsistent software and library states. Ifthe library is left in this inconsistent state, the load or unload action willprobably fail and abort the Media Agent. The external script should detectthat the library has been used and left in an inconsistent state and rescan thelibrary so that it is reset to its default operational state. However, the MediaAgent does not issue a special reset or initialize command for this purpose.

Some libraries have removable cartridge magazines (containing media) thatcan be loaded and unloaded under software control. The OmniBack II MediaAgent assumes the magazine is loaded and does not attempt to pre-load it atstartup or unload it at shutdown. If a particular library offers the magazineloading function, the external scripts should detect an unloaded magazineand load it automatically without any Media Agent intervention.

Device Configuration

Configure a logical device using theLogical Device Editor windowfor the type of logical device you are configuring.

To access theLogical Device Editor window, follow these steps:

9-14

ó.ô õ ö�÷>ø�ù�ú-û�ü ý�þmÿ�ý��õ � ý�ô��ö��õ ��qõ ý�ô �� î ��& !�(')��&*��*�"�� #�� $,+)��-�.�/�01� ')2 ï43 �� 5��6�7��

1. At the OmniBack II main menu, selectDevices to open theHPOmniBack II - Logical Device Administration windowappears. This window shows the logical devices that are currentlyconfigured for this cell.

2. SelectEdit → Create Logical Device→ External Control from themenu bar. TheLogical Device Editor External Controlwindow appears.

3. Enter the needed information. TheDrive Index must correspond to theLibrary Data Device. Enter the complete path and filename of the LibraryControl Script.

10-1

10

Troubleshooting

10-2

<=7ù�>��ü ý�ô@?�ù�ùBA5õ ö�÷

In this chapter

This chapter is divided into sections covering the most common messagesand sections covering other OmniBack II messages. Each message isprovided with a description or possible cause and recommended actions.

î ï ð ñ òAll the troubleshooting messages can be searched from the OmniBack II online helpto simplify the access to descriptions and actions.

If you encounter problems that are not documented here, be sure to checkthe HP OpenView OmniBack II Software Release Notes.

10-3

<=7ù�>��ü ý�ô@?�ù�ùBA5õ ö�÷ �� 3�3 ��C�-�� ñ ��.��*EDF�� .

Common GUI Errors and Warnings

MESSAGE:

Can not access the server host. (inet is not responding)

The host that is specif ied in the /etc/opt/omni/cell/cell_serverf ile is not reachable, it is not turned on and running,or has no OmniBack II software installed and conf iguredon it.

DESCRIPTION:

The xomni GUI tried to connect to the Cell Server but the connection failed.

ACTION:

Check if the cell server host is up and running. Check if it is accessible onthe network. If not, check the configuration of network services and routing.

Check if the OmniBack II software is properly installed on the host. You canuse the command: telnet hostname 5555 . After 30 seconds theOmniBack II should respond with the version information to confirm that itis ready.

MESSAGE:

Can not export medium medium_label.

Medium is protected.

DESCRIPTION:

You can not export medium with protected data.

ACTIONS:

Recycle medium and then export it.

10-4

<=7ù�>��ü ý�ô@?�ù�ùBA5õ ö�÷ �� 3�3 �&�1C4-�� ñ ��.��*EDF��G�&� ��&.

MESSAGE:

Can not remove pool.

Pool is used as default pool for device().

DESCRIPTION:

You can not remove a pool that is used as the default pool for logicaldevices.

ACTION:

Move logical devices to another pool.

MESSAGE:

Device not found.

DESCRIPTION:

When adding/modifying an object to the datalist, you tried to specify alogical device that does not exist.

ACTION:

Use help […] button to get list of configured devices.

MESSAGE:

Host hostname unavailable.

Can not change config files!

DESCRIPTION:

When exporting a host from a cell, it was not reachable. The host wasproperly exported only on the Cell Server side.

ACTION:

Check if the host is connected to the network and reachable.

Problem will occur when you will try to import this host to another cell. Youmust delete the/etc/opt/omni/cell/cell_server file on the host.

10-5


MESSAGE:

Host is not in this cell.

DESCRIPTION:

When adding/modifying an object to the datalist, you tried to get list ofavailable mountpoints for a host that is not configured in the cell.

ACTION:

Use the... button to get the list of configured hosts.

Check if the Disk Agent software is installed on the host.

MESSAGE:

Importing host hostname…

Can not import host hostname.

Command import failed.

DESCRIPTION:

You wanted to import a host to your cell, but the command failed.

ACTION:

Check the/etc/opt/omni/cell/cell_server located on this host.This file contains the information about Cell Server to which this hostbelongs. If name of Cell Server is different, then remove this file and repeatthe procedure.

MESSAGE:

Insuff icient disk space on f ilesystem containing pathspathname and pathname.

DESCRIPTION:

There is not enough disk space on volumes with/opt/omni (on HP - UX10.x) or/tmp/omni_tmp (on HP-UX 9.x) directories.

10-6

<=7ù�>��ü ý�ô@?�ù�ùBA5õ ö�÷ �� 3�3 �&�1C4-�� ñ ��.��*EDF��G�&� ��&.

ACTIONS:

Free up more disk space and start the installation again.

MESSAGE:

MediaAgent for series sun/sparc/sunos is not supported.

DESCRIPTION:

This version of OmniBack II does not support Media Agent for seriessun/sparc/sunos. Check which architectures are supported.

MESSAGE:

Node hostname unknown or not responding.

DESCRIPTION:

Installation on the selected host failed because the host was not reachable.

ACTION:

Check if the host you want to install is reachable on the network.

MESSAGE:

OmniBack II medium “Default File_1” in drive.Medium is still under protection => recycle medium.Initialization denied.

DESCRIPTION:

If you have an OmniBack II medium and it is still under protection, it cannot be initialized.

ACTION:

Check that you do not need the data on the medium, recycle it, and initializeit with theForce initialization option.

10-7


MESSAGE:

OmniBack II medium “c14d05b9:2fb2f6ff:4a3d:0001” indrive.Medium not found in OmniBack II database.This medium can be initialized only with force optionspecif ied.

Initialization denied.

DESCRIPTION:

If you have an OmniBack II medium and it is not found in the database, themedium can not be initialized.

ACTION:

Check that you really do not need the data on the medium any more andinitialize the medium with theForce Initialization option.

MESSAGE:

The number of conf igured clients is greater than thenumber of available client (host) licenses. Possibly thelicense has expired.Run command omnicc -query to see the licensing summaryreport.

DESCRIPTION:

Not enough licenses.

ACTION:

Add new licenses or change the configuration.

10-8

<=7ù�>��ü ý�ô@?�ù�ùBA5õ ö�÷ �� 3�3 �&�1H,/�.�.��/,�96��/�/�� ñ ��G�&�G.,��&*4DI�� .

Common Message Screen Errors and Warnings

MESSAGE:

[Minor] From: BMA@ hostname “NJIVA_48L” Time: 07/29/9502:11:53 /dev/dat3Can not close device (I/O error)

DESCRIPTION:

Something is wrong with the device.

ACTION:

Check if the medium is bad or the device needs cleaning.

MESSAGE:

[Critical] From: BDA-NETIO@ hostname “KALEIDOSKOP backup”Time: Sat Jul 29, 1995 01:33:13Can not connect to Media Agent (IPC Can not Connect) =>aborting

DESCRIPTION:

Connection to Media Agent failed and can not be reestablished.

ACTION:

Check the displayed Media Agent messages for some errors.

Try to connect from Disk Agent host to the Media Agent host, specified inDEV. CONFIG usingtelnet to port 5555.

10-9

<=7ù�>��ü ý�ô@?�ù�ùBA5õ ö�÷ �� 3�3 ��H�/�.�.��&/��6��/�/�� ñ ��.��*EDF�� .

MESSAGE:

[Critical] From: BDA-NETIO@ hostname “KALEIDOSKOP backup”Time: Sat Jul 29, 1995 01:33:13Can not connect to Media Agent (IPC Invalid Hostname orIP Address) => abortingUnexpected close reading NET message => aborting

DESCRIPTION:

Media Agent host not known on the Disk Agent.

ACTION:

Add Media Agent host to the name server or the/etc/hosts file on theDisk Agent host.

MESSAGE:

Can not open: (unknown error) => not backed up

DESCRIPTION:

File could not be opened and it was not backed up.

ACTION:

If this error appears constantly, exclude the file from the backup.

MESSAGE:

[Warning] From: VBDA@ hostname Time: 08/14/95 16:34:32filenameCan not preserve time attributes: (Not owner)

DESCRIPTION:

OmniBack II could not reset the access time attribute of the file.

ACTION:

If this error appears constantly, you may set theDo not preserveaccess time attributes option, or exclude the file from the backup.

10-10


MESSAGE:

[Minor] From: VBDA@ hostname “KALEIDOSKOP backup” Time:07/29/95 03:37:25filenameCan not read: (Lockf deadlock detection)

DESCRIPTION:

File is locked by some other process and can not be backed up with OB-II

ACTION:

If this error appears constantly, exclude the file from the backup.

MESSAGE:

[Minor] From: VBDA@ hostname “KALEIDOSKOP backup” Time:07/29/95 11: 09:50/users/leon/Can not stat: (No such f ile or directory) => not backedup

DESCRIPTION:

File has been removed while backup was running.

MESSAGE:

[Minor] From: VBDA@ hostname “KALEIDOSKOP backup” Time:07/28/95 23 :51:51/nfs/opsCan not stat: (Stale NFS f ile handle) => not backed up

DESCRIPTION:

NFS mount is not valid.

ACTION:

Umount and mount back the specified NFS mounted volume.

10-11


MESSAGE:

[Major] From: BMA@ hostname “NJIVA_48L” Time: 07/29/9502:11:53/dev/dat3Can not write to device (I/O error)

DESCRIPTION:

Error on the device.

ACTION:

Check if the medium is bad or the device needs cleaning.

MESSAGE:

[Major] From: BSM@ hostname “KALEIDOSKOP” Time: 07/29/9502:17:10Got unexpected close from Filesystem backup DA onhostname.

DESCRIPTION:

Disk Agent has lost the connection to the Session Manager. The Disk Agentmay have been killed or aborted for some reason.

ACTION:

Restart backup.

MESSAGE:

[Critical] From: VBDA@ hostname “KALEIDOSKOP backup”Time: 07/29/95 03:15:03Received ABORT request from NET => aborting

DESCRIPTION:

Media Agent was aborted and the Disk Agent must be aborted, too.

ACTION:

Check messages for Media Agent errors.

10-12


MESSAGE:

[Major] From: BSM@ hostname “ZLATOROG1” Time: 08/12/9522:12:06The Filesystem backup DA reached its inactivity timeoutof 7200 seconds.The agent on host hostname will be shut down.

DESCRIPTION:

Disk Agent was not active for more than two hours.

ACTION:

Check for mount problems (bdf), big sparse files, or directories with largenumber of files and compression or encryption.

î ï ð ñ òThe timeout is defined in the Global options file.

MESSAGE:

[Critical] From: BSM@ hostname “ name” Time: 05/12/9515:33:57There is no license for BDA@hostname. The disk will notbe backed up.

DESCRIPTION:

This message is displayed if you have exported or deinstalled a host, but thesame host is still configured in the datalist.

ACTION:

Modify the datalist.

Reinstall the host or import it.

10-13


MESSAGE:

[Critical] From: INET@ hostname “ name” Time: 05/11/9512:39:19User “ username” non-existent on this host => aborting

DESCRIPTION:

The backup session on the host was aborted because the user is notregistered on the host.

ACTION:

OmniBack II requires that you have the same username on all hosts youback up.

MESSAGE:

[Critical] From: VBDA@ hostname “ name” Time: 05/11/9512:40:07 treeNot valid mount point => aborting

DESCRIPTION:

Wrong mountpoint for the hostname was configured, the backup wasaborted.

ACTION:

Modify the object and use the […] button to get list of valid mountpoints forthe host.

Check available filesystems using the UNIXdf or mount command.

MESSAGE:

[Major] From: BSM@ hostname “ name” Time: 05/11/9513:08:05Could not connect to inet for starting of disk agent onhost “ hostname”.

10-14


DESCRIPTION:

During the backup session the agent on the hosthostname could not bestarted and the host was not backed up.

ACTION:

Check if the host is up and running. Check if it is accessible on the network.

Check if the OmniBack II software is properly installed on the host. You canuse thetelnet hostname 5555. After 10 seconds the OmniBack II shouldrespond with the version information to confirm that it is running.

MESSAGE:

[Minor] From: BSM@ hostname “ name” Time: 05/11/9510:58:36There are not enough media in the pool to complete thebackup.

DESCRIPTION:

The calculation at the end of the backup preview shows that there are notenough free media in the media pool.

ACTION:

Add new media to the pool.

If some backups are no longer needed, you may want to recycle media tocreate more space for new backups.

MESSAGE:

[Minor] From: VBDA@ hostname “ name” Time: 05/11/9510:54:40 treeCan not traverse: (Permission denied) => not backed up

DESCRIPTION:

You do not have UNIX permissions to back up the specifictree. The backupof thattree was skipped.

10-15


ACTION:

Exclude the tree from the backup as you are not authorized to backup thesefiles.

MESSAGE:

[Warning] From: VBDA@ hostname “ name” Time: 05/11/9510:57:25treeObject does not reside on current f ilesystem => notbacked up

DESCRIPTION:

Thetree you have specified is not on the filesytem that is backed up.

ACTION:

Check on which filesystem thetree resides and modify the datalistaccordingly.

MESSAGE:

rexec: Lost connectionProblem in obtaining information from host hostname.Possibly wrong password.

DESCRIPTION:

Installation to a new host failed- system function rexec between Cell Serverand client host can not be executed.

ACTION:

Resolve why the rexec function can not be executed. See manpages forrexec command.

10-16

<=7ù�>��ü ý�ô@?�ù�ùBA5õ ö�÷"�/�.�.� �� 3�3 ��EDI�� * ñ ��H�/�.�.��/�.

Less Common Warning and Error Messages

MESSAGE:

[ERROR] Can not open database/f ile.

DESCRIPTION:

OmniBack II was unable to open the internal database. The database files areeither not available or the Unix file permissions to access the database filesare incorrect.

ACTION:

Check the database files (*.dat , *.ext , *.key ) in the/var/opt/omni/db/cdb and/var/opt/omni/db/mmdb directories onthe Cell Server. The permissions of these files should be600 and userroot .If there are no files, database has not been initialized yet. In this case, use theomnidbinit command to initialize the database.

MESSAGE:

[ERROR] Can’t access the f ile.

DESCRIPTION:

Configuration file can not be accessed. This message means that the CellServer daemon can not read or write from a certain configuration file.

ACTION:

Use the/bin/ll - command to check the appropriate files below thedirectory/etc/opt/omni .

10-17

<=7ù�>��ü ý�ô@?�ù�ùBA5õ ö�÷"�/�.�., �� 3�3 ��EDF�� &�1��* ñ ��9H,/�.�.��/�.

MESSAGE:

[ERROR] Can’t access the f ile.

DESCRIPTION:

The IPC communication ended unexpectedly.

ACTION:

Check for system resources (memory, swap space). Check if SessionManagers are being killed.

MESSAGE:

[MAJOR] FullPathName Can not append to medium( UnixErrorString)

DESCRIPTION:

The Backup Media Agent (BMA) process was unable to append to existingdata on the medium in use.

ACTION:

No action is necessary. OmniBack II will attempt to use another medium asthis medium has no available space. Simply respond to any mount prompts.

MESSAGE:

[WARNING] FullPathName Can not apply lock:( UnixErrorString)

DESCRIPTION:

The specified object could not be locked before backup. The error messageindicates the reason as reported by the operating system.

ACTION:

• Eliminate the problem described by the error message.• Unset the "Lock Files During Backup" option in the configuration of the

backup object.

10-18


MESSAGE:

[MINOR] FullPathName Can not close: ( UnixErrorString)

DESCRIPTION:

If the specified object can not be closed after it is backed up, the backupstatus of this object is unsuccessful. The error message indicates the reasonas reported by the operating system.

ACTION:

• Eliminate the problem described by the error message and restart thebackup session.

• Exclude the specified object from the backup fileset by using the-exclude option.

MESSAGE:

[ERROR] Can not connect to host hostname.

DESCRIPTION:

OmniBack II could not connect to the specified host.

ACTION:

Use theping command to check the connection to this host and telnet<HOSTNAME> 5555.

MESSAGE:

[ERROR] Can not connect to required session session-id.

DESCRIPTION:

You specified the wrong session ID when trying to abort a session.

ACTION:

Use theomnistat command to get the correct session ID, then try thecommand.

10-19


MESSAGE:

[ERROR] Can not connect to session with session IDsession-id.

DESCRIPTION:

You tried to monitor a session that is not a backup or restore session. Youcan only monitor backup and restore sessions.

ACTION:

Restart the monitor, specifying backup or restore session.

MESSAGE:

[MAJOR] FullPathName Can not determine diskcharacteristics ( UnixErrorString) => aborting

DESCRIPTION:

The optical pre-erase operation failed because OmniBack II was unable toread the disk.

ACTION:

• Verify that the disk drive model is supported by OmniBack II.• Verify that the disk is not damaged. Replace any damaged disks.

MESSAGE:

[MAJOR] FullPathName Can not erase disk surface( UnixErrorString) => aborting

DESCRIPTION:

The pre-erase operation failed due to system error. The error messageindicates the reason as reported by the operating system.

10-20


ACTION:

Eliminate the problem described by the error message and restart thesession. If the pre-erase fails again, you must replace the disk. Check if thedrive needs cleaning.

MESSAGE:

[ERROR] Can not execl omnib for datalist’ datalist_name’.

DESCRIPTION:

Theomnitrig command can not execute the commandomnib .

ACTION:

Check to be sure that the/opt/omni/bin/omnib command exists, and besure that the Unix file permissions are correctly set. If theomnib commandexists and the permissions are correct, the file may be corrupt. In this case,reinstall the User Interface on the Cell Server.

MESSAGE:

[WARNING] FileName Can not force lock: Unix Error Code

DESCRIPTION:

The restore operation could not lock the specified object before starting therestore. The error message indicates the reason as reported by the operatingsystem.

ACTION:

Restart the operation.

MESSAGE:

[WARNING] FullPathName Can not force lock:( UnixErrorString)

10-21


DESCRIPTION:

The specified object could not be locked before backup. The error messageindicates the reason as reported by the operating system.

ACTION:

• Eliminate the problem described by the error message.• Toggle off the "Lock Files During Backup" option of the backup.

MESSAGE:

[ERROR] Can not install trigger in cron. Can not opencrontab for writing.

DESCRIPTION:

You either are not configured forcron or do not have permission to accessthecron file.

ACTION:

Check, and if necessary correct, thecron file configuration and thepermission of its configuration files.

MESSAGE:

[MAJOR] Can not load exchanger medium ( UnixErrorString)

DESCRIPTION:

The library failed to complete SCSI move command. The error messageindicates the reason as reported by the operating system.

ACTION:

Verify that the autochanger device is online and ready. If necessary, performhardware reset of the autochanger or turn the power off and on. Then restartthe failed session.

10-22


MESSAGE:

[ERROR] Can not lock database - currently unavailable.

DESCRIPTION:

You have a lot of parallel jobs and they want ot access the same part ofdatabse.

ACTION:

Check to be sure that no other OmniBack II processes are running on theCell Server (especially Session Managersbsm/rsm/msm/dbsm/psm andtheomnidbcheck command.) Stop the Cell Server (using theomnisv.sh-stop command) and then restart the Cell Server (using theomnisv.sh -start command).

Try rescheduling some backups to run them in sequence (instead of parallel).

If PSM (purge session manager) is running you can configure it in theglobal options file to run when no backups are running.

MESSAGE:

[MAJOR] FullPathName Can not lock exchanger controldevice ( UnixErrorString)

DESCRIPTION:

The Media Agent (xMA) could not reserve the library control device for itsexclusive use. Exclusive locking is required for multi-drive libraries toprevent mechanical damage. This problem can occur if you are runningseveral Media Agents that concurrently use the same autochanger. The errormessage indicates the reason as reported by the operating system.

ACTION:

Check the device and restart the session.

10-23


MESSAGE:

[MAJOR] Can not lock medium mediumID in database.Probably in use by someone else. Skipping re-initialization.

DESCRIPTION:

You tried to reinitialize medium which is locked by another process.Possible causes are another user is modifying medium data (label andlocation) or someone killed the backup/restore Session Manager and themedium stayed locked.

ACTION:

Wait until the medium is free and try again.

MESSAGE:

[MINOR] FileName Can not mknod : Unix Error Code

DESCRIPTION:

You must have the access right forrestore as root to restore specialfiles.

ACTION:

Either add therestore as root access right to this user class or transferthis user to a user class that has therestore as root access right.

MESSAGE:

[ERROR] Can not open database in exclusive mode. SomeSession Managers may still be running.

DESCRIPTION:

Message is usual at merging mmdb database to centralmmdb database. Itmeans that there are session managers running on central host. It might seemthat no Session Manager is running, but the message appears. Reason is thatthere is a lock for cca 30 min after Session Manager is down. In that caserestartingcrs solves a problem.

10-24


ACTION:

Wait for the Session Managers to complete, then restart the operation. Checkthat no Session Managers are running.

MESSAGE:

[ERROR] Can not open database. Somebody is runningomnidbcheck or omnidbutil command.

DESCRIPTION:

You tried to run a process that opens the database. However, OmniBack IIwas unable to open the database because either a user was runningomnidbcheck or anomnidbutil command.

ACTION:

Wait for theomnidbcheck or omnidbutil command, then restart theoperation.

MESSAGE:

[MAJOR] FullPathName Can not open device( UnixErrorString)

DESCRIPTION:

The Media Agent (xMA) detected an error trying to open a device. The errormessage indicates the reason as reported by the operating system. A "Nosuch device or address" message from media device indicates that there is nomedium in the device.

ACTION:

Verify that medium is loaded and ready. Respond to any pending mountprompts.

10-25


MESSAGE:

[MAJOR] Can not open mount table: ( MountTable)

DESCRIPTION:

OmniBack II is unable to access the register of mounted filesystems.Probably invalid access rights to the register.

ACTION:

Verify the cause of this problem described in the error message and notifyyour system administrator.

MESSAGE:

MAJOR: Can not open mount table: ( UnixErrorString)

DESCRIPTION:

OmniBack II is unable to access the register of mounted filesystems on thehost running the Disk Agent (VBDA). The error message indicates thereason as reported by the operating system.

ACTION:

Verify that the mount table (file/etc/mnttab on HP-UX systems) existson the host running the Disk Agent (VBDA) and can be accessed.

MESSAGE:

[WARNING] FullPathName Can not open option f ile:( UnixErrorString)

DESCRIPTION:

The Disk Agent (xBDA) received-read option or an input redirectionoperator (-trees < filename) and the input file could not be accessed.

ACTION:

Verify that the input file exists on the appropriate host and can be read by theDisk Agent (xBDA).

10-26


MESSAGE:

[WARNING] FullPathName Can not open option f ile:( UnixErrorString)

DESCRIPTION:

The Media Agent (xMA) received-read option or an input redirectionoperator (-dev < file) but the input file could not be accessed.

ACTION:

Verify that the input file exists on the appropriate host and can be read by theMedia Agent (xMA).

MESSAGE:

[MINOR] FullPathName Can not open: ( UnixErrorString) =>not backed up

DESCRIPTION:

The specified object could not be opened and will not be backed up. Theerror message indicates the reason as reported by the operating system.

ACTION:


• Exclude the specified object from the backup fileset using the-excludeoption.

10-27


MESSAGE:

[WARNING] FullPathName Can not preserve time attributes:( UnixErrorString)

DESCRIPTION:

The Disk Agent (VBDA) is unable to preserve the time attributes of thespecified object. The error message indicates the reason as reported by theoperating system.

ACTION:

Select optionDo not preserve time attributes or back up asrootor file owner.

MESSAGE:

[MINOR] FullPathName Can not read ACLs:( UnixErrorString)

DESCRIPTION:

The extended ACL attributes belonging to this object can not be read andwill not be backed up. The error message indicates the reason as reported bythe operating system.

ACTION:

Eliminate the cause of the problem described by the error message andrestart the backup session to complete successful backup.

MESSAGE:

[MAJOR] FullPathName Can not read from device( UnixErrorString)

DESCRIPTION:

The Media Agent (xMA) detected an error while reading from the device.The error message indicates the reason as reported by the operating system.

10-28


ACTION:

The session fails. You must check the media in the device and restart thesession.

MESSAGE:

[MINOR] FullPathName Can not read link:( UnixErrorString) => not backed up

DESCRIPTION:

The specified symbolic link can not be resolved and will not be backed up.The error message indicates the reason as reported by the operating system.

ACTION:

Eliminate the cause of the problem described by the error message andrestart the backup session to complete successful backup.

MESSAGE:

[MINOR] FullPathName Can not read: ( UnixErrorString)

DESCRIPTION:

The specified object could not be read and will not be backed up. The errormessage indicates the reason as reported by the operating system.

ACTION:


• Exclude the specified object from the backup fileset using the-excludeoption.

10-29


MESSAGE:

[MAJOR] FullPathName Can not seek to requested position( UnixErrorString)

DESCRIPTION:

The Media Agent (xMA) detected an error while trying to move theread/write head to certain position. The error message indicates the reason asreported by the operating system.

ACTION:

A possible cause of this error is corrupted media format. Verify the mediaformat using the OmniBack medium verification utility.


MESSAGE:

[MINOR] FullPathName Can not stat: ( UnixErrorString) =>not backed up

DESCRIPTION:

The specified object could not be examined and will not be backed up. Theerror message indicates the reason as reported by the operating system.

ACTION:


• Exclude the specified object from the backup fileset by using the-exclude option.

10-30


MESSAGE:

[MINOR] FullPathName Can not traverse: ( UnixErrorString)=> not backed up

DESCRIPTION:

The specified directory could not be traversed (probably due to insufficientaccess rights) and will not be backed up. The error message indicates thereason as reported by the operating system.

ACTION:


• Exclude the specified directory from the backup fileset using the-exclude option.

MESSAGE:

[MAJOR] Can not unload exchanger medium( UnixErrorString)

DESCRIPTION:

The library failed to complete a SCSI move command. The error messageindicates the reason as reported by the operating system.

ACTION:

Verify that the autochanger device is online and ready. If necessary, performa hardware reset of the autochanger or turn the power off and on. Thenrestart the failed session.

MESSAGE:

[MINOR] Can not unload medium, source drive( DriveSlotID) appears to be empty

DESCRIPTION:

The library status indicates that the source drive is empty. An empty driveCan not be unloaded.

10-31


ACTION:

If there is a medium in the source drive, then the internal library status iscorrupted and needs to be reset. To fix the problem, terminate the OmniBackII session, reset the library, and rescan the library using the OmniBack IIrescan feature.

NOTE:

You can reset the library by either pressing thereset button on the front panelor turning the power off and on.

MESSAGE:

[MINOR] Can not unload medium, target slot( RepositorySlotID) appears to be occupied

DESCRIPTION:

The library status indicates that the target slot in the library repositoryalready contains medium. The unload operation fails and the Media Agent(xMA) terminates.

ACTION:

If the source drive is empty, then the internal library status is corrupted andneeds to be reset. To fix the problem, terminate the OmniBack II session,reset the library, and rescan the library using the OmniBack II rescan feature.

NOTE:


10-32


MESSAGE:

[WARNING] FullPathName Can not unlock exchanger controldevice ( UnixErrorString)

DESCRIPTION:

The Media Agent (xMA) could not release the library control device. Theerror message indicates the reason as reported by the operating system.

ACTION:

No action is necessary. The library control device will be releasedautomatically as soon as the Media Agent (xMA) process terminates.

MESSAGE:

[WARNING] FileName Can not unlock: Unix Error Code

DESCRIPTION:

The restore operation could not unlock the specified object after the restoreand therefore the restore failed. The error message indicates the reason asreported by the operating system.

ACTION:

Restart the restore.

MESSAGE:

[WARNING] FullPathName Can not unlock: UnixErrorString

DESCRIPTION:

The specified object could not be unlocked after backup and its backupstatus will not be successful. The error message indicates the reason asreported by the operating system.

ACTION:

No action is necessary. The specified object will be unlocked automaticallywhen the Disk Agent (VBDA) process terminates.

10-33


MESSAGE:

[ERROR] Medium “Medium ID” in device “Logical Device” inthe pool “Pool Name” with strict allocation policy cannot be used for backup. Medium label is: “Medium Label”

DESCRIPTION:

Library repository was not correct or if you are using pool which hasstrict Media Allocation Policy, you must mount the exact mediumspecified by the mount request.

ACTION:

Mount the medium specified by the mount prompt or userescan librarybefore backup if you often manually replace media in a library.

MESSAGE:

[MAJOR] FileSystemMountPoint Can not verify f ilesystemmount point:

DESCRIPTION:

OmniBack II is unable to locate the specified mount point in the register ofmounted filesystems.

ACTION:

• Verify that the specified mount point exists on the host running the DiskAgent (VBDA) and can be accessed.

• Ensure that the specified filesystem is mounted at backup time

10-34


MESSAGE:

[MAJOR] FullPathName Can not write to deviceUnixErrorString

DESCRIPTION:

The Media Agent (xMA) detected an error while writing to the device. Theerror message indicates the reason as reported by the operating system.

ACTION:


MESSAGE:

[WARNING] Connection to the peer_type on host peer_hostis inactive for over the timeout period and willtherefore be closed. Agent identif ication ispeer_version.

DESCRIPTION:

Trouble communicating with one of the agents. Agent does not update itsstatus periodically.

ACTION:


MESSAGE:

[MAJOR] Could not connect to Disk Agentagent_host: mountpoint named label.

DESCRIPTION:

It is not possible to start Disk Agent on the specified host. There might be aproblem with your network setup or there is no OmniBack IIinet processproperly configured for the target host.

10-35


ACTION:

Check your network setup and check that the configuration of the files/etc/services and/etc/inetd.conf on the target host is correct forthe inet entry. Use telnet<host> 555 for checking.

MESSAGE:

[MAJOR] Could not connect to Media Agentagent_host: mountpoint named label.

DESCRIPTION:

It is not possible to start the Media Agent on the specified host. There mightbe problem with your network setup or there is no OmniBack IIinetprocess properly configured for the target host.

ACTION:

Check your network setup and check that the configuration of the files/etc/services and/etc/inetd.conf on the target host is correct forthe inet entry. Use telnet<host> 555 for checking.

MESSAGE:

[MAJOR] Could not connect to OmniBack II inet process onhost agent_host.

DESCRIPTION:

Media management Session Manager can not connect to OmniBack IIinetprocess on reported host.

Possible reasons are:

• OmniBack II is not installed on that host• The /etc/inetd is not running• The inetd configuration is incorrect

ACTION:

10-36


Be sure that the OmniBack II entries are contained in the/etc/inetd.conf and/etc/services files. Then trigger the/etc/inetd daemon to reread the configuration with/etc/inetd - . Usetelnet<host> 555 .

MESSAGE:

[MAJOR] Could not start Media Agent. Session is aborted.

DESCRIPTION:

Could not start the Media Agent for Media Management Operation. TheMedia Agent did not respond to the Session Manager.

ACTION:

Check the message from OmniBack II [inet] process. Be sure that theOmniBack II Media Agent software is installed on host where this device islocated. Use telnet<host> 555 .

MESSAGE:

[ERROR] Database is probably corrupt. Please runomnidbcheck!

DESCRIPTION:

OmniBack II database is probably corrupt.

ACTION:

Terminate all running sessions and GUIs so that no process is accessing thedatabase. Next, login to Cell Server asroot and run theomnidbcheck -f ix command. If you get error message "Database is corrupted!", thedatabase is unfixable and you must recover the database from backup.

MESSAGE:

[ERROR] Database key f iles have been corrupted. Pleaserun omnidbcheck -f ix!

10-37


DESCRIPTION:

The OmniBack II database index file has been corrupted.

ACTION:

Use theomnidbcheck -f ix command to fix the index file.

MESSAGE:

[ERROR] Database network communication error.

DESCRIPTION:

The OmniBack II database has problems communicating with the VelosisDaemon (RDS).

It is very likely thatrds was restarted, and GUI was not.

ACTION:

Check to be sure that the Velosis Daemon (RDS) is running. Stop the CellServer (using theomnisv.sh -stop command) and restart the Cell Server(using theomnisv.sh -start command). Start the GUI.

MESSAGE:

[ERROR] Database record limit per f ile reached.

DESCRIPTION:

The limit for OmniBack II database records has been reached.

ACTION:

Stop all Session Managers and terminate all GUIs, then use theomnidb -strip andomnidbcheck -purge command to delete obsolete data fromthe database. Restart the operation.

10-38


MESSAGE:

[MAJOR] Default pool pool_name of specif ied device isinvalid.

DESCRIPTION:

The pool you selected for this device is invalid because it uses anincompatible media class or does not exist.

ACTION:

Configure different pool for this device.

MESSAGE:

[MAJOR] Device device_name and pool pool_name mediaclasses do not match. Aborting…

DESCRIPTION:

The media class of the specified device is different than the media class ofthe specified pool.

ACTION:

Select pool which has the same media class as the device.

MESSAGE:

[MAJOR] Error accessing the database, in line code_line,f ile code_file. Database layer reports:" error_description."

DESCRIPTION:

Problems with the OmniBack II database.

ACTION:

Check message in error description and try to resolve the prior

10-39


MESSAGE:

[ERROR] File containing Cell Server host not found.

DESCRIPTION:

The configuration file/etc/opt/omni/cell/cell_server which holdsthe name of the Cell Server host is missing.

ACTION:

Create the configuration file/etc/opt/omni/cell/cell_server andadd the name of the local Cell Server.

MESSAGE:

[ERROR] File containing Cell Server host not found.

DESCRIPTION:

The file/etc/opt/omni/cell/cell_server is missing. This filecontains information about the User Interface and the Cell Server.

ACTION:

Create this file and add the name of the local Cell Server.

MESSAGE:

[WARNING] Filesystem ( FileSystem) is READ ONLY !

DESCRIPTION:

FileSystem on which you want to restore data is mounted as read-only.

ACTION:

To fix the problem, follow these steps:

1. Umount the filesystem2. Remount the filesystem as read/write filesystem3. Restart the restore

10-40


MESSAGE:

[WARNING] FilesystemMountPoint Filesystem is mountedread-only => locking disabled

DESCRIPTION:

The filesystem being backed up is mounted as read-only or is read-only bynature (CDROM) and does not support mandatory locking. The Disk Agent(VBDA) will disable the locking feature automatically to prevent wrongerror messages.

ACTION:

Toggle off the "Lock Files During Backup" option of the backup.

MESSAGE:

[MAJOR] Filesystem too deep: ( FilesystemRecursionDepth)levels

DESCRIPTION:

The Filesystem Backup Disk Agent has reached the maximum depth of itsrecursive filesystem traversal. This indicates that your directory structure istoo deep.

ACTION:

• Try to reconfigure the filesystem backup object to contain several treesstarting at lower level in the directory hierarchy.

• Decrease the depth of the directory structure to less than 100 levels.

MESSAGE:

[ERROR] Handshaking error. Versions of client and CellServer do not match.

DESCRIPTION:

Internal compatibility check reported that the running GUI or command isnot compatible with the running Cell Server daemon.

10-41


ACTION:

Check the OmniBack II release on the hosts and update the software.

MESSAGE:

[ERROR] Instance of OmniBack II Maintenance controlscript already running or terminated abnormally;semaphore f ile inst.lock will be ignored if no otherinstance running…

DESCRIPTION:

The lock fileinst.lock already existed when the installation was started.

ACTION:

If you are sure that only you are running the installation script, you canproceed with the installation.

MESSAGE:

[MAJOR] Interprocess communication error on SessionManager connection. The connection was to peer_type onhost peer_host. Agent identif ication is “ peer_version”.Ipc library reports " detailed_error_description."

DESCRIPTION:

Unexpected error for interprocess communication on connection to an agentor monitor. The connection is closed. If the connection was to monitor, youcan ignore this message.

ACTION:


10-42


MESSAGE:

[MAJOR] Invalid slot slotID specif ied.

DESCRIPTION:

You specified a slot which is not configured for this device.

ACTION:

Check the device configuration and specify the correct slot.

MESSAGE:

[MAJOR] Invalid device device_name specif ied.

DESCRIPTION:

This cell does not contain the device you specified.

ACTION:

Check the spelling of the device name and the configuration of the device.

MESSAGE:

[MAJOR] Invalid format of the message from peer_type onhost peer_host. Agent identif ication is “ peer_version”.

DESCRIPTION:

One of the agents received a recognized message with an invalid format.

ACTION:

Restart the session.

10-43


MESSAGE:

[WARNING] Invalid option “ OptionString” => ignored

DESCRIPTION:

The Disk Agent or Media Agent received an invalid option from the SessionManager. It is possible that the user specified an option argument startingwith a dash (-).

ACTION:

• Check that option arguments do not have a leading dash.• Verify that the Disk Agent (xBDA) and backup Session Manager (BSM)

versions are compatible.

MESSAGE:

[MAJOR] Invalid version of peer peer_id, versionpeer_version.

DESCRIPTION:

Reported peer (Media Agent or command/GUI) is not compatible with thisversion of the Session Manager.

ACTION:

Check the software version of your cell and update the peer to the samerelease as the Session Manager.

MESSAGE:

[ERROR] Velocis daemon error - the daemon is probablynot running.Use omnisv.sh start to restart OB2 daemons.

DESCRIPTION:

Velocis Daemon (RDS) is not running.

10-44


ACTION:

Check to be sure that the Velocis Daemon (RDS) is running. Stop the CellServer (using theomnisv.sh -stop command) and restart the Cell Server(using theomnisv.sh -start command).

MESSAGE:

[ERROR] Maximum number of Session Managers allowed arecurrently running.

DESCRIPTION:

Too many concurrent sessions running.

ACTION:

Use the monitor GUI or theomnistat command to check the number ofcurrently executing sessions. Abort any unnecessary sessions. Stop the CellServer (using theomnisv.sh -stop command) and restart the Cell Server(using theomnisv.sh -start command). This will terminate all activeGUIs and command-line interfaces.

MESSAGE:

[WARNING] Medium already in database. You must exportmedium f irst.

DESCRIPTION:

The medium you tried to import already belongs to this cell.

ACTION:

To put the medium in different cell, use theMove Medium feature.Otherwise, first export and then import the medium.

10-45


MESSAGE:

[ERROR] Medium currently in use by someone else.

DESCRIPTION:

You tried to use a medium that is locked by either an executing process or aprocess that terminated unsuccessfully.

ACTION:

If other Session Managers are running, you can not use this medium until theother Session Managers finish (or are terminated).

MESSAGE:

[WARNING] Medium is still under protection => recyclemedium.

DESCRIPTION:

You tried to initialize or erase medium that contains protected sessions.

ACTION:

Use the OmniBack IIRecycle feature to remove the protection for themedium, then restart the operation.

MESSAGE:

[MAJOR] FullPathName Medium not in OmniBack II format =>aborting

DESCRIPTION:

The medium examined is not in OmniBack II format and therefore can notbe verified by OmniBack II.

ACTION:

Mount valid OmniBack II medium and restart the verification.

10-46


MESSAGE:

[WARNING] “tar” meidum in device “.....”. The mediumwill not be used for backup.

DESCRIPTION:

OmniBack II checks the format of the medium before writing to themedium. OmniBack II recognizes media of types such astar , cpio , andHP-UX filesystem but will not write to these media formats.

ACTION:

To use media of these formats, you must first initialize the medium by usingthe-force option. An alternative is to use UNIX commands to overwritethe first block on the medium.

MESSAGE:

[ERROR] Monitoring is not supported for this sessiontype.

DESCRIPTION:

You tried to monitor a session that is not a backup or restore session. Youcan only monitor backup and restore sessions.

ACTION:

Restart the monitor, specifying backup or restore session.

MESSAGE:

[ERROR] Neither /etc/hosts nor Name Service canresolve/verify system hostname.

DESCRIPTION:

Installation failed because the host name was not in the/etc/hosts file.

ACTION:

Enter the hostname again, making sure that you spell the name correctly.

10-47


MESSAGE:

[ERROR] No details for this session type.

DESCRIPTION

You tried to view status information for a session which is not a backup orrestore session. You can only view status information for backup and restoresessions.

ACTION:

Retry the operation, specifying backup or restore session.

MESSAGE:

[ERROR] No Session Manager with that session ID iscurrently running.

DESCRIPTION:

There is no session with that session ID currently running.

ACTION:

Use omnistat to display all currently running sessions.

MESSAGE:

[MAJOR] No side of cartridge for double-sided devicespecif ied.

DESCRIPTION:

You selected a device which uses double-sided media but you did notspecify which side of the medium to use.

ACTION:

Specify the side of the medium to use.

10-48


MESSAGE:

[MAJOR] No slot ID for exchanger device specif ied.

DESCRIPTION:

You have selected an autochanger device and must therefore specify slot ID.

ACTION:

Specify slot ID for the operation (Init/erase/list/import/verify operations).

MESSAGE:

[ERROR] Not enough disk space for database.

DESCRIPTION:

OmniBack II does not have enough disk space to use the database.

ACTION:

Delete or move files from the disk where the OmniBack II database islocated (/var/opt/omni/db ) and then restart the operation.

All disks where OmniBack II files reside (/opt/omni , /var/opt/omni )must have at least 2 MB free space.

MESSAGE:

[WARNING] FullPathName Not in hard link catalog =>backed up regularly

DESCRIPTION:

Hard link reference was created after the Disk Agent (xBDA) completed itsfirst treewalk building its internal hard link catalog. The object will bebacked up as regular file and can not be restored as hard link reference butonly as a separate file.

ACTION:

If you are concerned about the consistency of your backup data, restart thebackup session.

10-49


MESSAGE:

[ERROR] Nothing to browse or database was closed duringbrowse due to inactivity.

DESCRIPTION:

There are two possible causes:

• You tried to use theBrowse feature to search the OmniBack II databasefor files. OmniBack II is unable to display this information because theOmniBack II lacks detailed information about the backup session youselected. Possible causes are the backup session was performed withouttheLog f iles to database option or the backup session failed.

• The browser window has been inactive for more than 30 minutes.

ACTION:

Try the browser again. If the cause was inactivity, the browser will work. Ifthe cause was lack of detailed information in the OmniBack II database, youwill need to using another method (for example, read the media) to locatethe file() .

MESSAGE:

[WARNING] FullPathName Object does not reside on currentf ilesystem => not backed up

DESCRIPTION:

The specified object (file/directory) does not belong to the physicalfilesystem being backed up. Probably it is an NFS mount point.

ACTION:

No action is necessary. To suppress this error message, exclude the specifiedobject from the backup fileset by using the-exclude option.

10-50


MESSAGE:

[WARNING] FullPathName Object is mounted f ilesystem

DESCRIPTION:

You have specified a rawdisk section pathname that refers to a disk devicecontaining a filesystem currently mounted.

ACTION:

No action is necessary. If you are concerned about the consistency of yourbackup data, you must use the pre/post-exec feature to unmount thefilesystem before the backup and remount it after the backup has completed.

MESSAGE:

[MAJOR] deviceFileName Object is mounted f ilesystem

DESCRIPTION:

The rawdisk has a mounted filesystem.

ACTION:

Unmount the filesystem and start the restore again.

MESSAGE:

[MAJOR] FullPathName Object not character device => notbacked up

DESCRIPTION:

You have specified a rawdisk section pathname which does not refer tocharacter device file.

ACTION:

Verify the configuration of the backup object and the rawdisk section files onthe host running the Disk Agent (RBDA).

10-51


MESSAGE:

[ERROR] Parameter string is too long.

DESCRIPTION:

Action response is too long (exceeds the internal limits)

ACTION:

This message means that the output of low level query is bigger than thelimit. Split the command into several commands in order to use lessresources.

MESSAGE:

[ERROR] Problems in transfer of package packet-name tosystem hostname via service-name service. Check servicemanually for user username before continuing.

DESCRIPTION:

FTP failed while transferring an OmniBack II software packet to theselected host. The FTP failed because user used thesu command instead ofsu - .

ACTION:

Runsu - before you start the installation.

MESSAGE:

[ERROR] Protected medium and can not append.

DESCRIPTION:

You tried to append to a medium that is unappendable either because themedium belongs to a pool that is not appendable or because this medium isnot the first medium of the backup.

ACTION:

Be sure that the pool is appendable. Then load the first medium of thatbackup set.

10-52


MESSAGE:

[WARNING] Can not start script “....” tSystem reports “error descr”

or

tScript “....” on cell server host has invalidpermissions and will not be executed by Session Manager.

DESCRIPTION:

Unable to locate this mount prompt script. Note: Script must be owned byroot . The script can only be executed if no other user has write permissionfor the script.

ACTION:

Check the script and, if necessary, change the write permissions.

MESSAGE:

[MAJOR] Session Manager received close from thepeer_type on host peer_host The agent did not respond intime. Connection will be closed. Agent identif ication is“ peer_version”.

DESCRIPTION:

The connection to the Disk Agent, Media Agent, or Monitor was closedunexpectedly. This is probably due to abnormal agent termination or agenthost shutdown.

ACTION:


10-53


MESSAGE:

[MAJOR] Specif ied device for the object not found.

DESCRIPTION:

OmniBack II can not find the specified device.

ACTION:

Check the spelling of the device name and the device configuration.

If a device does not exist any more, you must specify a different device to beused for restore.

MESSAGE:

[MAJOR] Specif ied pool pool_name is invalid.

DESCRIPTION:

You specified a nonexistent pool.

ACTION:

Select one of the media pools with the correct media class for this device.

MESSAGE:

[ERROR] System belongs to different packet-nameinstallation with Cell Server cell-server-name insteadof cell-server-name.

DESCRIPTION:

The distribution of OmniBack II modules to this host failed because the hostalready belongs to another OmniBack II cell. The installation script checksthe cell-server file located in the full pathname directory on the host whereyou wanted to install the OmniBack II modules.

10-54


ACTION:

If you want to import the selected host into your cell, you must first export itfrom the cell it belongs to now. Then you will be able to include it into yourcell.

MESSAGE:

[WARNING] This medium can be initialized only with forceoption specif ied.

DESCRIPTION:

You tried to initialize a medium that is of known format ( OB1, OB2, TAR,CPIO).

ACTION:

Restart the initialization, using the-force option.

MESSAGE:

[ERROR] Unknown event event received.

DESCRIPTION:

This problem is caused by an internal error.

ACTION:


MESSAGE:

[MAJOR] Unknown event on Session Manager from peer_typeon host peer_host. Agent identif ication is“ peer_version”.

DESCRIPTION:

Unknown event received from one of the agents.

10-55


ACTION:

Restart the session.

MESSAGE:

[WARNING] FullPathName Unknown object type => not backedup

DESCRIPTION:

The stat() system call identifies a filesystem object not recognized and/orsupported by OmniBack II.

ACTION:

No actions are necessary. To suppress this error message, exclude thespecified object from the backup fileset by using the-exclude option.

MESSAGE:

[WARNING] Unknown type of compression :UniqueDataCompressionType

DESCRIPTION:

There is an error in the shared librarylibdc.sl . There is differencebetween the compression used for the backup and the compression used forthe restore. Since OmniBack II was unable to decompress the file, it restoredthe file in compressed form.

ACTION:

Be sure that the shared library contains the original compression used for thebackup. Then restart the restore.

10-56


MESSAGE:

[WARNING] Unknown type of encryption !

DESCRIPTION:

There is an error in shared librarylibde.sl . There is difference betweenthe encryption used for the backup and the encryption used for the restore.Since OmniBack II was unable to deencrypt the file, it restored the file inencrypted form.

ACTION:

Be sure that the shared library contains the original encryption used for thebackup. Restart the restore.

MESSAGE:

[WARNING] Unrecognized option " OptionString" => ignored

DESCRIPTION:

The Media Agent (xMA) received an invalid option from the SessionManager. It is possible that the user specified an option argument startingwith a dash - .

ACTION:

• Check that option arguments do not have a leading dash- .• Verify that the Media Agent (xMA) and Session Manager (xSM) versions

are compatible.

MESSAGE:

[WARNING] Wrong medium loaded.

DESCRIPTION:

You loaded a non-OmniBack II medium into the drive.

ACTION:

Either load an OmniBack II medium or initialize the medium and then use it.

10-57


MESSAGE:

[ERROR] You Can not abort session of this type.

DESCRIPTION:

You tried to abort a session that is not a backup or restore session. You canonly abort backup and restore sessions.

ACTION:

Wait for the session to end or abort the session in GUI where you started it.

MESSAGE:

[ERROR] You do not have permission to abort session.

DESCRIPTION:

OmniBack II security has reported that you have no permission to abort thesession. If user belongs to an OmniBack II class that has the Abort ACLdisabled, he will not be able to abort sessions belonging to other users.

ACTION:

Set the Abort ACL in the appropriate class.

MESSAGE:

[ERROR] You do not have permission to monitor session.

DESCRIPTION:

OmniBack II security has reported that you have no permission to monitorthis session. If user belongs to an OmniBack II class that has the MonitorACL disabled he will not be able to monitor sessions belonging to otherusers.

ACTION:

Set the Monitor ACL in the appropriate class.

10-58


MESSAGE:

[ERROR] You do not have permission to reply to mountrequest.

DESCRIPTION:

OmniBack II security has reported that you have no permission to respond tothe specified mount request. This occurs when you try to respond to mountrequest from a session that was not initiated by yourself and you belong togroup that has the ACL Mount Prompt disabled.

ACTION:

Set the Mount Prompt ACL in the appropriate class.

MESSAGE:

[MAJOR] [ BlockSegment: BlockOffset] Invalid block header=> not in OmniBack II format

DESCRIPTION:

The block at the specified position is not in OmniBack II format. This canoccur if an existing OmniBack II medium has been partly overwritten byanother application.

ACTION:

In order to use this medium for OmniBack II, you must first re-initialize themedium. To discard the medium, first export it from the OmniBack II pool.

MESSAGE:

[MAJOR] [ BlockSegment: BlockOffset] Invalid record header=> block corrupted

DESCRIPTION:

The block of the OmniBack II media format at the specified positioncontains an invalid record header which indicates that the block might becorrupted.

10-59


ACTION:

No recovery actions are possible. Use a different medium.

MESSAGE:

[MAJOR] [ BlockSegment: BlockOffset] Stored/Computed CRCmismatch => block corrupted

DESCRIPTION:

The CRC checksum that was computed at backup time does not match theCRC computed during the verify session. The block at the specified positionis probably corrupted.

ACTION:

It is rare that random bit errors can produce this message. Therefore, youmust export this medium from the OmniBack II database and discard themedium.

MESSAGE:

[COMMAND ERROR] Can not access the server host.

DESCRIPTION:

The file/etc/opt/omni/cell/cell_server is missing.

ACTION:

Create the Cell Server file and enter in the name of the local Cell Server.

MESSAGE:

[COMMAND ERROR] You do not have permission to startrestore.

DESCRIPTION:

You tried to perform restore but you have no permission to perform restore.

10-60


ACTION:

Either add thestart restore access right to this user class or transfer thisuser to a user class that has thestart restore access right.

MESSAGE:

[COMMAND ERROR] You do not have permission to startbackup.

DESCRIPTION:

You tried to start backup but you have no permission to do this.

ACTION:

Either add thestart backup access right to this user class or transfer thisuser to a user class that has thestart backup access right.

MESSAGE:

[COMMAND ERROR] You do not have permission to startdatalist backup.

DESCRIPTION:

You tried to start datalist backup but you have no permission to do this.

ACTION:

Either add thestart datalist backup access right to this user class ortransfer this user to a user class that has thestart datalist backupaccess right.

10-61


MESSAGE:

[COMMAND] Can not start media management Session Manageron host hostname.

DESCRIPTION:

You tried to perform a media management operation, but you lack theMedia conf iguration access right.

ACTION:

Either add theMedia conf iguration access right to this user class ortransfer this user to a user class that has theMedia conf iguration accessright.

MESSAGE:

[COMMAND] Could not fork processcommand

DESCRIPTION:

The command you specified could not execute for one of several reasons:

• the command was not able to connect to the selected Cell Server• the command is not contained in the/opt/omni/bin directory• there are too many processes are already running

ACTION:

Check the following items to correct the problem:

1. Use theomnisv.sh -status command to be sure that the Cell Serveris running.

2. Check the/opt/omni/bin directory to be sure that the command is inthe directory.

3. Use theps -ef command to be sure that the process limit of the systemhas not been reached.

10-62


MESSAGE:

[COMMAND] You do not have permission to get logicaldevice information.

DESCRIPTION: You tried to view logical device information, but you lacktheDevice conf iguration access right.

ACTION:

Either add theDevice conf iguration access right to this user class ortransfer this user to a user class that has theDevice conf igurationaccess right.

MESSAGE:

[COMMAND] You do not have permission to get mediamanagement information.

DESCRIPTION:

You tried to view media management information, but you lack theMediaconf iguration access right.

ACTION:


MESSAGE:

[COMMAND] You do not have permission to initializemedium.

DESCRIPTION:

You tried to initialize medium, but you lack theMedia conf igurationaccess right.

10-63


ACTION:


MESSAGE:

[CRITICAL] No physical device() specif ied => aborting

DESCRIPTION:

No physical devices have been specified for this logical device. Each logicaldevice must have at least one physical device.

ACTION:

Verify the configuration of the logical device, and if necessary, modify thelogical device.

MESSAGE:

[CRITICAL] Incorrect type of backup - backup must bedone with: typeOfBackup

DESCRIPTION:

You tried to restore a file using the wrong menu selection.

ACTION:

To restore a file from a rawdisk backup, use theRestore Single Filefrom Rawdisk menu selection.

10-64


MESSAGE:

[CRITICAL] FilesystemMountPoint Not valid mount point =>aborting

DESCRIPTION:

The filesystem mount point specified by the user is not real mount point onthe host running the Disk Agent (VBDA).

ACTION:

Verify the configuration of the backup object and the table of mountedfilesystems on the host running the Disk Agent (VBDA).

MESSAGE:

[CRITICAL] FullPathName Can not open exchanger controldevice ( UnixErrorString)

DESCRIPTION:

The Media Agent (xMA) could not open the specified library control device.The error message indicates the reason as reported by the operating system.

ACTION:

Verify that the control device file exists on the appropriate host and can beaccessed by the Media Agent (xMA) process.

MESSAGE:

[CRITICAL] FullPathName Can not preerase (invalidphysical device type) => aborting

DESCRIPTION:

You can only pre-erase magneto-optical media. The device you selected isnot the correct device type.

ACTION:

Attempt pre-erase operation on magneto-optical media only. Note that notall HP optical drives are capable of pre-erasing an optical platter.

10-65


MESSAGE:

[CRITICAL] FullPathName can not preerase (unknown mediumcapacity) => aborting

DESCRIPTION:

The optical preerase operation failed because the capacity of the mediumcould not be determined.

ACTION:

Do not use the pre-erase feature on this optical disk. OmniBack II generallyrequires that the capacity of a disk is known in order to use and handle itproperly.

NOTE:

If only some of the optical disks in your autochanger refuse to be preerased,this may be an indication that their surfaces are damaged. You must replacethe defective disks.

MESSAGE:

[CRITICAL] FullPathName Invalid exchanger control device=> aborting

DESCRIPTION:

The library control device accessed a device that is not a SCSI-II compliantlibrary.

ACTION:

Verify the configuration of the logical device. The library control device fileprobably does not refer to an autochanger picker device.

10-66


MESSAGE:

[CRITICAL] FullPathName Invalid physical device type =>aborting

DESCRIPTION:

The physical device type does not match the device type of the logicaldevice as configured.

ACTION:

Verify the device type of the physical device in the logical deviceconfiguration.

MESSAGE:

[CRITICAL] ShellCommandLine Can not popen() script:( UnixErrorString)

DESCRIPTION:

The Media Agent (xMA) could not invoke a subshell script using thepopen() system call. The error message indicates the reason as reported bythe operating system.

ACTION:

Verify that the shell command line has the correct syntax and does notcontain any inaccessible or non-executable commands.

Verify that the host running the Media Agent (xMA) has sufficient resourcesfor the necessary processes.

10-67


MESSAGE:

[CRITICAL] ShellCommandLine Error reading script output( UnixErrorString)

DESCRIPTION:

The Disk Agent (xBDA) process detected an error while reading from thepipe through which it is connected with its pre-/post-exec process. The erroris probably caused by an ungraceful termination of the script. The errormessage indicates the reason as reported by the operating system.

ACTION:

• Verify that the shell command line is syntactically correct and does notcontain inaccessible or non-executable command invocations.

• Verify that the executed programs behave as expected and do not produceunexpected results. Test the shell command line manually for possiblebugs.

MESSAGE:

[CRITICAL] ShellCommandLine Error reading script output( UnixErrorString)

DESCRIPTION:

The Media Agent (xMA) process detected an error while reading from thepipe through which it is connected with its subshell process. The cause isprobably an ungraceful termination of the subshell. The error messageindicates the reason as reported by the operating system.

ACTION:

Verify that the shell command line has the correct syntax and does notcontain any inaccessible or non-executable commands.

Verify that the executed programs work as expected and do not produceunexpected results. Test the shell command line manually for possible bugs.

10-68


10-69


MESSAGE:

[CRITICAL] UserName Not Super-User => can not restoreraw

DESCRIPTION:

You must have therestore as root access right to restore a rawdisk orfiles from rawdisk.

ACTION:

Toggle on the access right forrestore as root

MESSAGE:

[CRITICAL] Can not determine control device type( FullPathName)

DESCRIPTION:

The device accessed by the specified library control device does not respondcorrectly to the SCSI inquiry command. The error message indicates thereason as reported by the operating system.

ACTION:

Verify the configuration of the logical device. The library control device fileprobably does not refer to the valid SCSI device.

MESSAGE:

[CRITICAL] Can not execute ’ FullPathName’( UnixErrorString) => aborting

DESCRIPTION:

The inet agent is unable to execute the requested agent. The error messageindicates the reason as reported by the operating system.

ACTION:

• Verify that HP OmniBack II is installed correctly on the host.• Verify that the specified agent binary can be accessed and executed on the

10-70


host.

MESSAGE:

[CRITICAL] Can not fork NETIO process ( UnixErrorString)=> aborting

DESCRIPTION:

The Disk Agent (xBDA) main process is not able to fork its NETIOsubprocess. This is possibly due to insufficient system resources on the hostrunning the Disk Agent (xBDA). The error message indicates the reason asreported by the operating system. The most probable cause is “insufficientmemory” or “process table full”.

ACTION:

Verify that the host running the Disk Agent (xBDA) has sufficient resourcesto fork and execute another process.

MESSAGE:

[CRITICAL] Can not fork NETIO process ( UnixErrorString)=> aborting

DESCRIPTION:

The Media Agent (xMA) main process is not able to fork its NETIOsubprocess. A possible cause is insufficient system resources on the hostrunning the Media Agent (xMA). The error message indicates the reason asreported by the operating system. The most probable cause is “insufficientmemory” or “process table full”.

ACTION:

Verify that the host running the Media Agent (xMA) has sufficient resourcesto fork and execute another process.

10-71


MESSAGE:

[CRITICAL] Can not initialize pipe connection( UnixErrorString) => aborting

DESCRIPTION:

The Disk Agent (xBDA) parent process is not able to open a pipe connectionand fork its NETIO process. This is possibly due to insufficient systemresources on the host running the Disk Agent (xBDA). The error messageindicates the reason as reported by the operating system.

ACTION:

Verify that the host running the Disk Agent (xBDA) has sufficient resourcesto open the pipe and establish an IPC connection.

MESSAGE:

[CRITICAL] Can not initialize pipe connection( UnixErrorString) => aborting

DESCRIPTION:

The Media Agent (xMA) parent process is not able to open a pipeconnection and fork its NETIO process. A possible cause is insufficientsystem resources on the host running the Media Agent (xMA). The errormessage indicates the reason as reported by the operating system.

ACTION:

Verify that the host running the Media Agent (xMA) has sufficient resourcesto open the pipe and establish an IPC connection.

10-72


MESSAGE:

[CRITICAL] Can not load medium, target drive( DriveSlotID) appears to be busy

DESCRIPTION:

The library status indicates that the target drive is not empty. A medium cannot be loaded into an occupied drive and therefore the Media Agent (xMA)terminates.

ACTION:

Verify that the drive of the logical device is empty before starting OmniBackII. If the drive is empty, then the internal library status is corrupted and needsto be reset. To fix the problem, terminate the OmniBack II session, reset thelibrary, and rescan the library using the OmniBack II rescan feature.

NOTE:


MESSAGE:

[CRITICAL] Database layer reports [line: code_line,f ile: code_file]: ” error_message”

DESCRIPTION:

The backup session tries to update the database with information, but theinformation is not accepted. The probable cause is an invalid transaction. Inrare cases, this error could indicate a corrupted database.

ACTION:

Restart the backup. If the error reoccurs, use theomnidbcheck command tocheck the database.

10-73


MESSAGE:

[CRITICAL] Final BMA acknowledgement missing => backupINCOMPLETE

DESCRIPTION:

The Disk Agent (xBDA) was disconnected from the Media Agent before thelast pending data block was acknowledged. This indicates that the backuprecord stream is not complete and the backup can not be regarded assuccessful.

ACTION:

The backup will not be completed successfully. You must restart the backupsession.

MESSAGE:

[CRITICAL] IPC failure reading NETIO message( UnixErrorString) => aborting

DESCRIPTION:

The Media Agent (xMA) main process detected an IPC error reading anincoming NETIO message. The error message indicates the reason asreported by the operating system.

ACTION:

The session will fail. You must restart the session.

MESSAGE:

[CRITICAL] IPC failure reading SM message( UnixErrorString) => aborting

DESCRIPTION:

The Media Agent (xMA) main process detected an IPC error while readingan incoming Session Manager (SM) message. The error message indicatesthe reason as reported by the operating system.

10-74


ACTION:

The session fails. You must restart the session.

MESSAGE:

[CRITICAL] Incorrect type of backup - backup must bedone with: TypeOfBackup

DESCRIPTION:

You selected "Restore File from Rawdisk" but the backup object youselected was not a rawdisk.

ACTION:

To restore from a rawdisk, you must select a "rawdisk" backup object. Eitherselect a rawdisk object or select "Restore File from Filesystem."

MESSAGE:

[CRITICAL] Invalid device type specif ied( LogicalDeviceTypeID) => aborting

DESCRIPTION:

The device type configured for this logical device is invalid.

ACTION:

Verify the configuration of the logical device, and if necessary, modify thelogical device.

MESSAGE:

[CRITICAL] Invalid exec code ( AgentExecCode) => aborting

DESCRIPTION:

Internal Error: The Session Manager tried to execute an invalid ornonexistent agent.

10-75


ACTION:

Verify that theinet and Session Manager versions are compatible.

MESSAGE:

[CRITICAL] Invalid storage element requested =>aborting. Please verify logical device conf iguration

DESCRIPTION:

The set of repository identifiers contains invalid items that do not match theactual repository elements located inside the library. The error was detectedwhile attempting to access an invalid element.

ACTION:

Verify the layout of the library repository and the configuration of thelibrary.

MESSAGE:

[CRITICAL] MA/NETIO protocol error => aborting

DESCRIPTION:

The Media Agent (xMA) main process received an unexpected messagetype on its NETIO IPC channel.

ACTION:


MESSAGE:

[CRITICAL] No datalist in Session Manager command lineoptions or no such datalist exists.

DESCRIPTION:

Either an invalid datalist or no datalist was specified.

10-76


ACTION:

Specify valid datalist and restart the backup.

MESSAGE:

[CRITICAL] No exchanger control device specif ied =>aborting

DESCRIPTION:

No SCSI-II library control device has been specified for this logical device.SCSI-II library must have control device to handle medium movecommands.

ACTION:

Verify the configuration of the logical device and, if necessary, modify thelogical device.

MESSAGE:

[CRITICAL] Protocol error, can not parse options =>aborting

DESCRIPTION:

Internal Error: The startup handshake protocol between the OmniBackinetagent and the invoking Session Manager is unsuccessful.

ACTION:

Verify that theinet and Session Manager versions are compatible.

MESSAGE:

[CRITICAL] SM/MA protocol error => aborting

DESCRIPTION:

The Media Agent (xMA) main process received an unexpected messagetype on its Session Manager (SM) IPC channel.

10-77


ACTION:

Verify that the Media Agent (xMA) and Session Manager (xSM) versionsare compatible.


MESSAGE:

[CRITICAL] Security violation: Can not switch to uid= inuser mode

DESCRIPTION:

The userroot can be the only member of the user classAdmin . This is toprevent network security problems. The error was detected by theinetagent enforcing the security.

ACTION:

Verify that userroot is the only member of theAdmin user class.

MESSAGE:

[CRITICAL] The peer_type on host peer_host did notidentify itself on startup. Connection will be closed.

DESCRIPTION:

An agent must first identify itself to the Session Manager in order to checkcompatibility. The problem is probably due to theinet process on the targethost being unable to execute the proper agent.

ACTION:

Check the availability of OmniBack II executables on the target host, theirpermissions, and the availability of shared libraries.

10-78


MESSAGE:

[CRITICAL] Unexpected close reading NETIO message( UnixErrorString) => aborting

DESCRIPTION:

The Media Agent (xMA) main process detected loss of connection whilereading an incoming NETIO message. The error message indicates thereason as reported by the operating system.

ACTION:


MESSAGE:

[CRITICAL] Unexpected close reading SM message( UnixErrorString) => aborting

DESCRIPTION:

The Media Agent (xMA) main process detected connection loss whilereading an incoming Session Manager (SM) message. The error messageindicates the reason as reported by the operating system.

ACTION:


MESSAGE:

[CRITICAL] Unexpected error parsing NETIO message( UnixErrorString) => aborting

DESCRIPTION:

The Media Agent (xMA) main process detected parsing error while readingan incoming NETIO message. This indicates that the received message wasincorrectly formatted.

ACTION:


10-79


MESSAGE:

[CRITICAL] Unexpected error parsing SM message( UnixErrorString) => aborting

DESCRIPTION:

The Media Agent (xMA) main process detected parsing error while readingan incoming Session Manager (SM) message. This indicates that thereceived message was incorrectly formatted.

ACTION:


MESSAGE:

[CRITICAL] Unknown type of encryption !

DESCRIPTION:

There is an error in shared librarylibde.sl . There is difference betweenthe encryption used for the backup and the encryption used for the restore.Since OmniBack II was unable to deencrypt the file, it restored the file inencrypted form.

ACTION:

Be sure that the shared library contains the original encryption used for thebackup. Then restart the restore.

MESSAGE:

[CRITICAL] Unrecognized option " option" !

DESCRIPTION:

10-80


The Session Manager sent an invalid option to the Disk Agent (xRDA). Thisreason could be that the user specified a tree (or similar) with a leading dash"-".

ACTION:

Check that there are no leading dashes"-". Also, check that the Disk Agent(xRDA) version corresponds to the Session Manager.

MESSAGE:

[CRITICAL] User " UnixUserName" non-existent on thishost=> aborting

DESCRIPTION:

HP OmniBack II requires a user to have a valid Unix "user:group" accountin order to start an agent on a host. The error was detected by theinet agentenforcing the security.

ACTION:

Either create a Unix account for the user on the host, or run the agents inroot mode.

MESSAGE:

[CRITICAL] Agent peer_id, version peer_version, is notcompatible with current version of Session Manager.Connection will be closed.

DESCRIPTION:

The agent is not compatible with the current version of the Session Manager.

ACTION:

Install the new version of the agent on the hosts. To update all the installedagents on all the hosts in a cell, use theUpdate All feature of theOmniBack IIInstall feature.

10-81


MESSAGE:

[CRITICAL] FullPathName Can not compute disk capacity( UnixErrorString) => not backed up

DESCRIPTION:

OmniBack II is unable to determine the capacity of the specified rawdisksection. The section can not be backed up.

ACTION:

The disk is not supported by HP OmniBack II.

MESSAGE:

[CRITICAL] Media Management Database corrupted ==>backup aborted!

or

Catalog Database corrupted ==> backup aborted!

DESCRIPTION:

OmniBack II internal database is not in a consistent state, so it will not bebacked up.

ACTION:

Run theomnidbcheck -f ix command to check the consistency of thedatabase and rebuild index files. If this does not solve the problem, you mustrestore the database from the latest backup.

MESSAGE:

[CRITICAL] Group " UnixGroupName" non-existent on thishost=> aborting

DESCRIPTION:

HP OmniBack II does not permit user "user:group" to start an agent on ahost where his Unix group does not exist. The error was detected by theinet agent enforcing the security.

10-82


ACTION:

Either create a Unix group for the user on the host or change theconfiguration of this user to a valid Unix group.

MESSAGE:

[CRITICAL] User " UnixUserName" is not a member of group" UnixGroupName" => aborting

DESCRIPTION:

HP OmniBack II does not permit a Unix user ("user:group") to start an agenton host where he is not member of the specified Unix group. The error wasdetected by theinet agent enforcing the security.

ACTION:

Either create Unix group for the user on the host or change the configurationof this user to a valid Unix group.

MESSAGE:

[CRITICAL] ShellCommandLine Can not popen() script:( UnixErrorString)

DESCRIPTION:

The Disk Agent (xBDA) can not invoke pre-/post-exec script using thepopen() system call. The error message indicates the reason as reported bythe operating system.

ACTION:

• Verify that the shell command line is syntactically correct and does notcontain inaccessible or non-executable command invocations.

• Verify that the host running the Disk Agent (xBDA) has sufficientresources to execute another process.

10-83


MESSAGE:

[ERROR GUI] Table allocation error. (No more freeentries!).

DESCRIPTION:

Table allocation error.

ACTION:

Internal program static tables are used due to several error recoveryprocedures. Restart the GUI.

MESSAGE:

[Can not get value of the environment variable DISPLAY.

DESCRIPTION:

You tried to get the status of a specified cell, but OmniBack II was unable todisplay this information.

ACTION:

• Be sure that the DISPLAY environment variable is set• Be sure that the ITO/OpC management station allows the Cell Server host

to display an hpterm (you must allow access to the appropriate client). Toallow access to the client, use thexhost + clientname command.

MESSAGE:

[No valid host running Cell Server daemon located.

DESCRIPTION:

You selected a host that is not defined as a Cell Server.

ACTION:

Define a host as a Cell Server using the procedures described in the chapter"OmniBack II and IT/OperationsCenter Integration."

10-84


MESSAGE:

[NORMAL] No reply from peer_type on host peer_host.Agent identif ication is peer_version. The connection tothe agent will be closed.

DESCRIPTION:

The Session Manager was waiting for a reply from Disk Agent or MediaAgent. The reply did not arrive before the timeout.

ACTION:


MESSAGE:

[ERROR] sh: /opt/omni/sbin/omnitrig: not found

DESCRIPTION:

omnitrig is missing andcrontab has not been updated. This can happenif OmniBack II was removed instead of deinstalled.

ACTION:

Manually remove theomnitrig line from thecrontab file.

MESSAGE:

[CRITICAL] ‘device name’ Can not get device f ile status(error string) =>abborting

DESCRIPTION:

Can not get the status of a device file. The device file name is specified at alocation where no file can be created.

ACTION: Change the specified device file.

10-85


MESSAGE:

[CRITICAL] ‘device name’ Not a character device or aregular f ile => aborting

DESCRIPTION:

You tried to work with a device that is a block device or the file namespecified is not a regular file.

ACTION:

Change the device file name into a character (raw) device or into a regularfile.

MESSAGE:

[MAJOR] ‘device name’ No access permission for devicef ile => aborting

DESCRIPTION:

You have no permission to access the logical device.

ACTION:

Check your permissions and change them appropriately.

MESSAGE:

[CRITICAL] 'device name' Unsupported device => aborting

DESCRIPTION:

The device you wanted to use is not supported by OmniBack II.

ACTION:

Use only devices that are supported by OmniBack II.

Refer to the HP OpenView OmniBack II Release Notes for a list ofsupported devices.

10-86


MESSAGE:

[CRITICAL] Not a BSD device => aborting

DESCRIPTION:

You have used a device that is not defined as a Berkley Style Device.

ACTION:

In the Logical Device Editor change the logical device file name to a BSDdevice. For more information on creating device file names, see also theOperating System Manual.

MESSAGE:

[CRITICAL] Limited block size of 64K => aborting

DESCRIPTION:

You have used a device that has a limited block size of 64K.

ACTION:

In the Logical Device Editor, change a logical device file name into a devicefilename with unlimited block size.

MESSAGE:

[CRITICAL] Not a variable block size => aborting

DESCRIPTION:

You have used a device that has a non-variable block size.

ACTION:

In theLogical Device editor, change the device file name appropriately to adevice file name with a defined variable block size.

10-87


MESSAGE:

[MAJOR] Can not access blocks after early warning EOT(error string

DESCRIPTION:

The medium is at a position after early warningEnd Of Tape , but blocksare not accessible. It is possible that medium is damaged.

ACTION:

The following actions are possible:

1. Check the error string and the Tape Alert Flag (if the device supports thetape Alert diagnostics) and respond accordingly.

2. The medium can be damaged, so replace it with a new one and restart theoperation.

MESSAGE:

[MAJOR] Can not switch to exclusive access

DESCRIPTION:

Operating system can not switch to access for just one process. Probablyaccess is already excluded with some other process.

ACTION:

Wait for other procces to finish, and then restart the operation.

MESSAGE:

[MAJOR] Medium has no capacity.

DESCRIPTION:

You tried to backup to medium with no capacity.

10-88


ACTION:

Replace the medium with a medium that has enough capacity.

MESSAGE:

[MAJOR] Can not open. Device busy.

DESCRIPTION:

Device is busy (occupied by another process).

ACTION:

Wait until the other process is finished on the specified device.

MESSAGE:

[MAJOR] Can not eject medium. (error string)

DESCRIPTION:

For some reason a medium can not be ejected from a drive.

ACTION:

Eject the medium manually.

MESSAGE:

[MAJOR] Can not get current medium position. (errorstring)

DESCRIPTION:

For some reason, the medium position can not be determined.

ACTION:

Check the disk or magnet-optical device you are using.

10-89


MESSAGE:

[MAJOR] Unexpected status of medium. (devFlags=#)

DESCRIPTION:

Medium is in position that is not expected for OmniBack II.

ACTION:

Check the exchanger (library device).

MESSAGE:

[WARNING] Partial read of a block.

DESCRIPTION:

From the medium just a part of that block was read instead of the wholeblock.

ACTION:

You can still use this medium for restore but the data will be successfullyread only up to the point where the warning occured.

MESSAGE:

[CRITICAL] Attempted read after logical EOD. (errorstring)

DESCRIPTION:

Position of medium was positioned after the End Of Data where no datablock resides. Possibly the medium format is not in the OmniBack II validformat or OmniBack II data is not written properly because of the hardwarefailure.

10-90


ACTION:

You can use the medium only for restore because backup information cannot be appended to the medium.

MESSAGE:

[MAJOR] Skipping write. (Apparently SCSI bus reset).

DESCRIPTION:

A SCSI bus reset has been detected and the medium can be repositioned toany position of data on tape. In order to protect data from being overwritten,Omniback II stops writing data to the medium.

ACTION:

Media Agent will abort a current process.

MESSAGE:

[MAJOR] Apparently SCSI bus reset.

DESCRIPTION:

A SCSI bus reset has been detected.

ACTION:

Media Agent will abort current process.

MESSAGE:

[MAJOR] Can not write to device after early warning EOT.(error string)

DESCRIPTION:

Position of medium is after early warning EOT and OmniBack II is unableto write on this part of medium.

10-91


ACTION:

Complete restore is still possible as long as the medium is not exported.

If you export the medium, a complete restore is not possible. Some datawritten to the end of medium will be lost.

MESSAGE:

[CRITICAL] Can not write to device. Position at physicalEOT.

DESCRIPTION:

1. This message occurs when copying a source medium to a target mediumwith not enough space.

2. OmniBack II can not write catalog data after the early warning end oftape. The size of catalog data to be written between the early warning endof tape and the physical end of tape is too large.

ACTION:

The catalog data is written to the OmniBack II database, and it can berestored as long as the medium is not exported.

If you export the medium, full restore is impossible and some data written tothe end of tape will be lost.

MESSAGE:

[CRITICAL] Partial write of a block.

DESCRIPTION:

For some reason there was just a part of block written to medium.

ACTION:

You can use this medium for restore only, but just up to the point where theerror occured.

10-92


MESSAGE:

[MAJOR] Can not close after write problem. (errorstring)

DESCRIPTION:

There was situation where OB2 was forced to close a current medium. Butthere was a problem closing the medium.

ACTION:

Check the device. If the device functions properly, there is probably aproblem with a medium. Try to perform backup to another medium.

MESSAGE:

[MAJOR] Can not open after write problem. (error string)

DESCRIPTION:

There was situation where OB2 was forced to close and reopen a medium.But there was problem with reopening.

ACTION:


MESSAGE:

[MAJOR] ‘device name’ Rewindable device.

DESCRIPTION:

There was situation where OB2 was forced to close and reopen amedium.But device was opened as rewindable device which rewinds the mediumafter close.

ACTION:

Device must be opened as non-rewindable.

10-93


MESSAGE:

[MAJOR] Skiping write of f ilemark. (Apparently SCSI busreset).

DESCRIPTION:

A SCSI bus reset has been detected and the medium can be repositioned toany position of data on tape. In order to protect data from being overwritten,Omniback II stops writing data to the medium.

ACTION:

Media Agent will terminate the current process.

MESSAGE:

[MAJOR] Can not write f ilemark. (error string)

DESCRIPTION:

For some reason the filemark can not be written.

ACTION:


MESSAGE:

[MINOR] INQUIRY call failed. (error string)

DESCRIPTION:

When the INQUIRY call fails, we are unable to find out what device we aredealing with.

ACTION:

Check if the device is correctly connected to and recognized by the system.

10-94


MESSAGE:

MINOR] REQUEST SENSE call failed. (error string)

DESCRIPTION:

When the REQUEST SENSE call fails we are unable to get specialinformation from a device such as thecleanme signal.

ACTION:

If this occurs at the beginning of a session, check if the device is correctlyconnected to and recognized by the system. Otherwise, check if there is adevice error (needs cleaning).

MESSAGE:

[MAJOR] Can not rewind medium. (error string)

DESCRIPTION:

Device driver can not rewind medium to the begining of a medium.

ACTION:


MESSAGE:

[MAJOR] Can not backspace segment. (error string)

DESCRIPTION:

Device driver can not position medium back for specific number ofsegments.

ACTION:


10-95


MESSAGE:

[MAJOR] Can not forward segment. (error string)

DESCRIPTION:

Device driver can not position medium forward for specific numberof segments.

ACTION:


MESSAGE:

[MAJOR] Can not backspace block. (error string)

DESCRIPTION:

Device driver can not position medium back for specific number ofblocks.

ACTION:


MESSAGE:

[MAJOR] Can not forward block. (error string)

DESCRIPTION:

Device driver can not position medium forward for specific numberof blocks.

ACTION:


10-96


MESSAGE:

[CRITICAL] Lost position. (error string)

DESCRIPTION:

After positionig the medium, a real block position is different. OmniBack IIdetected that a block of data has been corrupted or not written to themedium.

ACTION:

You can use the medium for restore up to the point where the error occured.

MESSAGE:

[CRITICAL] Medium full. Can not append (error string)

DESCRIPTION:

Can not append to a full medium.

ACTION:

Use another medium that is not full.

MESSAGE:

[MAJOR] Can not position to end of data. (error string)

DESCRIPTION:

For some reason device driver can not position a medium to the end of data.

ACTION:


10-97


MESSAGE:

[MINOR] Invalid format version of OmniBack II medium.

DESCRIPTION:

Format version on the medium is not a valid OmniBack II version.

ACTION:

Replace the medium with another one that has a valid OmniBack II version.

MESSAGE:

40. [CRITICAL] Invalid format version of OmniBack IImedium.

DESCRIPTION:

It is not allowed to accept medium with older format version.

ACTION:

You must replace a medium with another OmniBack II medium with a validformat version.

MESSAGE:

[MAJOR] Invalid position specif ied. (error string)

DESCRIPTION:

Medium was positioned to the invalid position.

ACTION:

Try with segment and/or block specification that do not exceeda maximumnumber of segments and/or blocks.

10-98


MESSAGE:

[MAJOR] Can not position to the requested position.(error string)

DESCRIPTION:

For some reason medium can not be positioned to the requested position.

ACTION:

Check whether medium is a valid OmniBack II medium.

MESSAGE:

[CRITICAL] Can not connect to Media Agent (error string)=> aborting

DESCRIPTION:

CMA process can not connect with BMA process.

ACTION:

Check if CMA is connecting to the BMA with a correct port number.

MESSAGE:

[CRITICAL] Can not handshake with Media Agent (errorstring) => aborting

DESCRIPTION:

Can not get important data from BMA like number of buffers, blocksize and medium header size.

ACTION:

Restart operation.

10-99


MESSAGE:

[CRITICAL] Device formats are not equal => aborting

DESCRIPTION:

You tried to replicate medium BMA and CMA that have not the sameformat. They are different in block size or number of blocks or sizeofa medium header.

ACTION:

Configure both sides of devices for BMA and CMA that have the sameformats such as a block size or the number of buffers.

MESSAGE:

[CRITICAL] Grau DAS error in “function_name()”: errorcode=#

DESCRIPTION:

The API callfunction_name() failed. Real cause is explained with errorcodes:

Explanations of error codes:

1. RPC failure.

2. ACI parameter invalid.

3. Volume not found of this type.

4. Drive not in Grau ATL.

5. The requested drive is in use.

6. The robot has a physical problem with the volume.

7. An internal error in the AMU.

8. The DAS was unable to communicate with the AMU.

9. The robotic system is not functioning.

10.The AMU was unable to communicate with the robot.

11.The DAS system is not active.

10-100


12.The drive did not contain an unloaded volume.

13.Invalid registration.

14.Invalid hostname or ip address.

15.The area name does not exist.

16.The client is not authorized to make this request.

17.The dynamic area became full, insertion stopped.

18.The drive is currently available to another client.

19.The client does not exist.

20.The dynamic area does not exist.

21.No request exists with this number.

22.Retry attempts exceeded.

23.Requested volser is not mounted.

24.Requested volser is in use.

25.No space availble to add range.

26.The range or object was not found.

27.The request was cancelled byaci_cancel() .

ACTION:

According to the error code number check the condition of Grau library andrestart operation.

MESSAGE:

[MAJOR] Grau DAS error in “function_name()”: errorcode=#

DESCRIPTION:



10-101


1. RPC failure.



























10-102


ACTION:

According to the error code number check the condition of Grau library andrestart operation.

MESSAGE:

[MINOR] Grau DAS error in “function_name()”: errorcode=#

DESCRIPTION:



1. RPC failure.
















10-103













ACTION:

Current session will not be aborted because of this problem.

MESSAGE:

[CRITICAL] Can not determine element addresses: (errorstring) .

DESCRIPTION:

Unable to get element addresses that are neccessary to manipulatewith SCSI-II libraries.

ACTION:

Check the library. If the library still does not respond, try turning it off andon. If this does not help, reboot the system.

10-104


MESSAGE:

[CRITICAL] Can not EJECT repository element(s): (nomailslot def ined) .

DESCRIPTION:

SCSI-II Library can not eject the specified medium because Library hasnomailslots.

ACTION:

You can not use theeject operation.

MESSAGE:

[CRITICAL] Can not ENTER repository element(s): (nomailslot def ined).

DESCRIPTION:

SCSI-II Library can not enter the specified medium because Library hasno mailslots.

ACTION:

You can not use theenter operation.

MESSAGE:

[WARNING] Can not EJECT repository element # intomailslot #: (mailslot is full).

DESCRIPTION:

SCSI-II Library can not eject the specified medium into mailslot becauseit is full.

ACTION:

Mailslot(s) must be emptied manually.

10-105


MESSAGE:

[WARNING] Can not ENTER repository element # frommailslot #: (slot is full).

DESCRIPTION:

SCSI-II Library can not enter a specified medium from a mailslotbecause all slots are full.

ACTION:

Eject some media from slots first and remove them from the Library. Thentry with the ENTER operation again.

MESSAGE:

[WARNING] Can not EJECT repository element # intomailslot #: (slot is empty).

DESCRIPTION:

SCSI-II Library can not eject the specified medium into mailslot becauseall slots are empty.

ACTION:

Enter some media into slots first. Then you can perform the EJECToperation.

MESSAGE:

[WARNING] Can not ENTER repository element # frommailslot #: (mailslot is empty).

DESCRIPTION:

SCSI-II Library can not enter the specified medium from a mailslot becausethe mailslot is empty.

ACTION:

Mailslot(s) must be filled manualy.

10-106


MESSAGE:

[MAJOR] Can not EJECT repository element # into mailslot#: (error string).

DESCRIPTION:

For some reason SCSI-II Library can not eject medium.

ACTION:


MESSAGE:

[CRITICAL] Can not read mailslot status => aborting.

DESCRIPTION:

SCSI-II Library does not return any information about the specifiedmailslot.

ACTION:


MESSAGE:

[CRITICAL] ENTER aborted due to operator inactivitytimeout (# secs).

DESCRIPTION:

Operator did not fill the specified mailslot with a medium.

ACTION:

Try the operation again and this time fill the specified mailslot witha medium.

10-107


MESSAGE:

[CRITICAL] EJECT aborted due to operator inactivitytimeout (# secs) .

DESCRIPTION:

Operator did not empty the specified mailslot.

ACTION:

Try the operation again and this time empty the specied mailslot.

MESSAGE:

[CRITICAL] “function_name()”: ACS reply out of sequence:#(expected #).

DESCRIPTION:

When working with StorageTek Library the API functionfunction_name() did not reply with a correct sequence number. This is aproblem in API protocol.

ACTION:

Check if StorageTek library and the server system are configured correctly.

MESSAGE:

[CRITICAL] StorageTek ACS error in “function_name()”:‘primary status’ : ‘secundary status’.

DESCRIPTION:

When working with StorageTek Library the API functionfunction_name() returnedprimary status instead ofsecundarystatus .

ACTION:

According to the returned status, check the StorageTek library and restartoperation.

10-108


MESSAGE:

[WARNING] OB2CLEANME setting is obsolete. You mustconf igure dirty drive detection in logical deviceconf iguration.

DESCRIPTION:

In file .omnirc the OB2CLEANME variable that is obsolete is defined.

ACTION:

For detection of a dirty drive you must configure the dirty drive in the logicaldevice configuration.

MESSAGE:

[WARNING] OB2BLKSIZE setting is obsolete. You mustconf igure block size in logical device conf iguration.

DESCRIPTION:

In file .omnirc the OB2BLKSIZE variable that is obsolete is defined.

ACTION:

For defining a block size you must configure the block size in the logicaldevice configuration.

MESSAGE:

[WARNING] OB2BARCODE setting is obsolete. You mustconf igure barcode reader support in logical deviceconf iguration.

DESCRIPTION:

In file .omnirc is defined variable OB2BARCODE that is obsolete.

10-109


ACTION:

To scan a library with barcodes you must configure a barcode readersupport in the logical device configuration.

MESSAGE:

[WARNING] Block size setting of #KB is too big. Maximumallowed block size for this device type is #KB.

DESCRIPTION:

The block size you set in the device configuration is too big.

ACTION:

Change the device configuration with a smaller block size. A maxiumblock size allowed is printed out.

MESSAGE:

[MAJOR] Can not dismount busy drive #. (error string).

DESCRIPTION:

OmniBack tried to mount a medium into a drive that is alreadymounted butOmniBack did not succeed to dismount the busy drive.

ACTION:

You must configure a drive busy hadling to eject a medium or ejectmedium to a mailslot in the logical device configuration. If that does notsucceed you must dismount a drive manualy.

MESSAGE:

[NORMAL] Successfuly dismounted busy drive #.

DESCRIPTION:

OmniBack mounted a medium into a drive that was already mountedandsuccessfuly dismounted

10-110


MESSAGE:

StorageTek ACS error in‘acs_mount’:STATUS_UNREADABLE_LABEL

DESCRIPTION:

The medium sticker label somehow fell of the medium. This causes the ACSsoftware to report an error, and OmniBack II session is aborted after theerror message is displayed.

ACTION:

Open the autochagner device and fix the medium sticker label. After that,rescan the autochanger from the OmniBack II GUI.

Glossary-i

Glossary

This glossary contains definitionsand additional information aboutwords and phrases used in HPOpenView OmniBack II.

access permissionsUnix File namecharacteristics (such as read, write, andexecute) that determine whether a usercan perform an operation on a file (suchas opening a file for writing). This isdifferent fromaccess rights that controlwhich tasks an OmniBack II user canperform.

access rights The permission toperform specific backup and restoretasks, such as handling mount prompts.Users have the access rights of the userclass to which they belong.

ACS pool Used to optimally manageand control StorageTek Library systems.

CDF file Context Dependent File. Acontext dependent file consists of severalfiles grouped under the same pathname.The system ordinarily selects one of thefiles using the context of the process.This mechanism allows machinedependent executable, system data, anddevice files to work correctly from allhosts in a cluster while using the samepath name.

cell A local part of the network. Thesystem administrator groups severalworkstations, hosts, devices, and otheritems necessary for backup into a cell tomore easily manage backup and restoreoperations. A cell typically represents alocation or organizational structure.Backup and restore policies and

schedules are defined on the cell level.This lets system administratorscustomize the backup and restorefunctions for each cell. By default, a celldoes not cross LAN boundaries. Alsoknown as "domain."

cell configuration Setting up hosts,pools, and devices for a cell and definingthe services and policies for the cell.Once configured, a cell can be controlledfrom a single workstation, the CellServer.

Cell Server This is the workstationfrom which a cell is managed. It includesa User Interface, several sessionmanagers, all configuration files, and theOmniBack II log database.

client A computer on a network thatreceives service from another computer(server). For example, a communicationserver connects clients to othercommunications networks such as localarea networks (LANs). (Seeserver.)

complex device SeeDevice Chains,Libraries , orStackers.

concurrency Media multiplexing.This device option allows more than oneDisk Agent (up to five) to write to onebackup device. This helps OmniBack IIkeep the media streaming when thedevice can accept data faster than a diskcan send it. OmniBack II providesdefaults for each device type supported

condition The quality and reliabilityof a medium. Heavy usage and age resultin increased read and write errors. Mediashould be replaced when the condition

Glossary-ii

Glossary

field indicatesPOOR.

control device The device file used tocontrol the robotic arm which moves themedia between the repository slots andthe read-write mechanism of an library.

DAS pool Is used to optimally manageand control GRAU systems.

daemon A memory resident programthat is constantly running. TheOmniBack II daemon facilitatescommunications in the network so thatOmniBack II can access different partsof the network at any time.

database server A computer with alarge database stored on it. A server hasa database that can be accessed by clientworkstations. (See alsoClient).

datalist A list of objects to be backedup. These objects can be files ordirectories. OmniBack II backs up theobjects in the datalist.

default entry A datalist entry thatestablishes default values for a group ofobjects.

default selection An object or actionthat is used when no other selection isspecified.

device A unit that contains stored datafor backup or recovery. See alsoComplex Device andSource Device.

detail catalog A catalog in theOmniBack II database containing thedetail information from backup and

restore sessions. You can delete thiscatalog if you run out of disk space andyou will still be able to restore all filesbacked up, but it will take longer.

Disk Agent The OmniBack IIsoftware module that controls readingfrom and writing to a disk. During abackup session, the Disk Agent sendsdata from the disk to theMedia Agentwhich then stores the data to the media.During a restore session, the Disk Agenttakes data received from the MediaAgent and writes it to the disk.OmniBack II only backs up thosesystems which have the Disk Agentmodule installed.

JFS Journaled File System that allowsyou to back up a file system while it isbeing backed up by some otherapplication. This is called an onlinebackup and is done by creating asnapshot of the file system and backingup that snapshot.

export host To remove a host from theCell Configuration without deinstallingthe OmniBack II modules that are on thishost. This action allows you to move ahost from one cell to another withoutdeinstalling and reinstalling theOmniBack II modules. You export thehost from one cell and import the host toanother cell.

export medium To remove allinformation about a backup medium andits contents from the OmniBack IIdatabase of a cell. Once a medium isexported, OmniBack II no longer hasinformation about either the mediumitself (for example, its location) or what

Glossary-iii

Glossary

backup sessions (and files) are containedon this medium. Use this option whenthe medium is no longer to be used forbackup in a cell. Data on the mediumremains unchanged. See also importmedium.

filter Criteria which let you selectivelydisplay information in OmniBack IIwindows. Use filters to define a view ofsession activities based on a specificsession owner or type of media session(backup, restore). If you use a filter todisplay names, OmniBack II generallyallows you to use wildcards to view aparticular pattern.

force initialization To erase any datacontained on a medium and format themedium as an OmniBack II medium.

full backup A backup in which allselected objects on all selected hosts arebacked up whether or not they have beenmodified recently. This contrasts withincremental backup.

host A server with workstationsincluding the disks and disk drives of theworkstations.

hostname The name of a system on thenetwork.

host backup A dynamic backup of allfilesystems configured in a host. Hostbackupsimplifies datalistconfiguration and improves backupcoverage of systems that oftenmount/dismount various disks.

import host Adds an already installedhost to an OmniBack II cell. See also

export host.

import medium Returns allinformation about a backup and itscontents medium to the OmniBack IIdatabase of a cell. See alsoexportmedium.

IP Address The numeric address of ahost. The IP address consists of 4 groupsof numbers: the first three groups ofnumbers represent the number of theinternet network and the last group ofnumbers represents the local networkaddress.

IPC address SeeIP Address.

incremental backup A backup inwhich only objects changed since arecent full backup are copied. Related tofull backup.

label A user-defined identifier used todescribe a backup medium.

LAN An acronym for Local AreaNetwork. The hosts and/or clusterswhich share data, hardware, andsoftware resources via NetworkingServices software.

libraries Also called autochangers,jukeboxes, etc. Standalone storagedevices. A library contains a librarysystem of media which are held inrepository slots. Each slot holds onemedium (for example, DAT tape ormagneto-optical platter). The libraryprovides access to a vast library of datawithin a few seconds without operatorintervention. To read a medium, anelectro-mechanical arm guided by the

Glossary-iv

Glossary

host computer selects, moves, rotates,and inserts tape or optical cartridges intothe drive mechanism(s) mounted insidethe cabinet.

library data device A data storagedevice. This device includes repositoryslots, a read mechanism, and a roboticarm which moves media between therepository slots and the read mechanism.

libraries pool Used to optimallymanage and control large SCSI IIlibraries.

library repository slots Make up alibrary repository. Each slot holds onestorage medium, for example, DAT tapeor magneto-optical platter. OmniBack IIreferences each slot by a number. Toread a medium, a control arm removesthe medium from a slot and inserts it inthe read mechanism.

load balancing Dynamic allocation ofdevices. If you select this option,OmniBack II will automatically connectbackup objects to available devices.

location The physical location of thebackup media (for example, "building 4"or "offsite storage").

logical device A set of physicaldevices treated and accessed as if theyare one device. A logical device consistsof devices of the same type (such asDAT, optical, or Exabyte) and usagepolicy.

magazine pool Used to optimallymanage and control small library devices

such as HP SureStore 12000e. Amagazine pool also supports the use ofcleaning tapes.

media Physical objects upon whichdata is recorded such as DAT tapes oroptical disks. You save or back up data tomedia. The plural of medium.

Media Agent The OmniBack IIsoftware module that controls readingfrom and writing to a media drive.During a backup session, the MediaAgent writes to media the data it hasreceived from theDisk Agent. During arestore session, the Media Agent locatesdata on the backup media and sends thedata to the Disk Agent. The Disk Agentthen writes the data to the disk.

media allocation policy Determines inwhich order media are accessed within apool.Strict allocation policy directsOmniBack II to prompt for a specificmedium.Loose directs OmniBack II toprompt for any suitable medium.

media capacity Seemedium capacity

media class The format of the media(for example, DAT)

media condition factors The user-assigned age threshold and usagethreshold used to calculate the probablecondition of the medium. The followingterms describe the condition:

Good = indicates less than 80% ofthresholds for age or usage

Glossary-v

Glossary

Fair = indicates 81-100% of thethresholds for age or usage

Poor = indicates more than 100% of thethresholds for age or usage

Default values for the thresholds areprovided by OmniBack II.

media ID A unique identifier assignedby OmniBack II to a medium.

media label Seelabel.

media management A tool thatallows you to track your backup mediaand backup/restore history. Mediamanagement also protects your data byhelping to prevent accidentaloverwriting of data.

media pool A set of similar media(DATs, Exabytes, etc.) used and trackedas a group. Media in a pool must be thesame media class (for example, DAT).Media are initialized and assigned to amedia pool. See alsostandard pool,magazine pool, library pool , ACSpool, andDAS pool .

medium (Seemedia.)

medium capacity The space availableon a medium before any data is written tothe medium. Ifdetermine is selected,OmniBack II determines the mediacapacity for that media type (forexample, DAT). Ifspecify is selected,OmniBack II uses the capacity that youspecify when you initialize the medium.

merge Defines how the files are

restored to a destination. If files exist inthe destination path, those with thenewer date are kept. Not existing filesare always restored to the destinationpath. See alsooverwrite.

mount To add an auxiliary(removable) file system to an activeexisting file system.

mount prompt A screen prompt thattells the user to put media online. Thisprompt appears in thestatus field of themonitor windows. When a mountprompt has been answered, the statusfield changes toin progress.

mount point The access point to thedata in the directory structure.

object An entity such as a directory,file, filesystem, or database that is usedin a backup.

overwrite Defines how files arerestored to a destination. All files arerestored from the backup even if they areolder than existing files. See alsomerge.

permissions Unix file characteristics(such as read, write, or execute) thatdetermine whether you can perform acertain operation on the file (such aswriting to a file).

pool (Seemedia pool)

pool attributes Attributes that definethe characteristics and use of a pool.Different pool types have differentattributes.

Glossary-vi

Glossary

pre-exec An option that instructsOmniBack II to process a command orscript before it backs up an object or asession is started.

post-exec An option that instructsOmniBack II to process a command afterthe backup of an object or a session iscompleted.

recycle OmniBack II keeps track ofdata on every used medium. Recyclingremoves data protection from the databacked up, thus allowing OmniBack II tooverwrite data in the next backup. Thedata on the media remains unchangeduntil the next backup.

remote pre-exec An option thatinstructs OmniBack II to process acommand or script on a remote hostbefore it backs up an object or a sessionis started.

remote post-exec An option thatinstructs OmniBack II to process acommand on a remote host after thebackup of an object or a session iscompleted.

repository slots Seelibraryrepository slots.

rescan A logical device function thatchecks each slot of a library to identifythe media and update the mediamanagement database with thisinformation. If someone has manuallyremoved or switched media, do a rescan.Rescanning lets OmniBack scan all theslots in the library, confirm whatmedium is present in each slot, andupdate and correct any inconsistencies

within the media management database.

scheduler The function that controlshow often and when backups occur. Bysetting up a schedule for a datalist, youcan automate your backups to runperiodically at times of low systemusage. With the scheduler, the backupsyou set up will run on the days and at thetimes you specify without yourattendance as long as the devices andmedia are properly set.

server A computer on a network thatprovides service to terminals on thenetwork (clients) by managing anexpensive shared resource. For example,a file server manages a set of disks andprovides storage services to computers(clients) on the network that may nothave their own disks. Sometimes aserver is a dedicated computer. (See alsoclient.)

session A major operation ofOmniBack II such as backup or restore.Each session is monitored and controlledby aSession Manager.

source device The mass storage unitfrom which OmniBack II is to beinstalled or updated, for example, acartridge tape, a DDS, or a CD-ROM.

standard pool Used to managestandalone devices, such as DATs,jukeboxes, or small external libraries.

User Interface The user interface ofOmniBack II. It usually runs on the CellServer but can also be installed on anysystem in the cell.

Glossary-vii

Glossary

verify A function that lets you checkwhether or not the data on a specifiedmedium is consistent or valid. Thisfunction reads all blocks, checks theheaders, parses all Media Agent blocks,and checks every record within theblock.

Glossary-viii

Glossary

Index

Index-i

Aaccess rights

for OmniBack II users, 3-38ACL

for OmniBack II users, 3-38adding

media to pool, 3-28allocation policy, 3-16ANSI media format compatibility, 3-18architecture

cell, 1-3Disk Agent, 1-4layers, 1-4Media Agent, 1-4OmniBack II, 1-3

automatingmount prompt handling, 7-3

auxiliary devices, 3-21

Bbacking up

a host, 3-6, 4-18a rawdisk, 3-6, 4-13existing datalist, 4-20in incremental mode, 3-7OmniBack II network, 1-2selected filesystem, 4-8the secondary Cell Server (MC/ServiceGuard),

7-41backing up your system, 4-1backup

changing ownership, 4-34choosing mode of backup, 3-6configuring a filesystem backup, 4-8dynamic host backup, 4-17incremental, 3-7interactive, 4-20load balancing datalists, 4-36monitoring sessions, 6-3

periodic schedule, 4-45planning backup strategy, 3-5post-exec commands, 7-6pre-exec commands, 7-6previewing, 4-24recovering failed backup, 7-14reporting through WWW server, 7-42restarting failed backup, 7-15scheduling, 4-41scheduling on a specific date, 4-43selecting a type, 3-5selecting rawdisk backup options, 4-15selecting rawdisk sections, 4-14skipping on holidays, 4-47starting, 4-24with load balancing, 4-37

backup devicesconfiguring and using, 3-21

backup mode, 3-6choosing, 3-6full, 3-6incremental, 3-7

backup objectschanging the view at restore, 5-4selecting, 3-9selecting at restore, 5-5

backup options, 4-26compressing data, 4-29description, 4-29encryption, 4-29for device, 4-33for filesystems, 4-11ignoring hard links, 4-32load balancing, 4-30locking files during backup, 4-32loging files to database, 4-31pre/post-exec commands, 4-32, 7-6preserving access time attributes, 4-32private data, 4-30

Index-ii

Index

protecting data, 4-33protection, 3-10public data, 4-30reconnecting broken connections, 4-30report level, 4-31

backup ownershipchanging, 4-34

backup protection, 3-10backup reporting through WWW server, 7-42backup schedule

changing date, 4-47clearing, 4-47editing a daily or monthly backup schedule, 4-

47example, 3-8types of, 3-10

backup sessiondeleting from a database, 7-24display of status, 4-22how does it work, 1-5operating, 1-5previewing, 4-24

backup sessionsstatus, 4-22

backup strategyplanning, 3-5

backup typefilesystem, 3-5host, 3-6rawdisk, 3-6selecting, 3-5

barcodesquick scan using barcodes, 3-34

barlistunderstanding, 4-4what is a barlist, 4-4

BIDBprotection of backup information, 8-6

broken connections

reconnecting, 4-40browsing

directories for restore, 5-7files for restore, 5-7

Ccatalogue retention, 8-6CDB

synchronizing with MMDB, 8-10CDF files

detection, 7-18cell, 2-2

access planning, 3-11Cell Server and clients, 1-3configuring, 3-1deinstalling OmniBack II from hosts, 2-11exporting hosts, 2-8importing hosts, 2-6importing hosts wirh multi-LAN cards, 2-8planning, 3-3planning backup strategy, 3-5upgrading OmniBack II software, 2-10what is a cell, 1-3

cell accessplanning, 3-11

Cell Server, 1-4moving, 7-36recovering, 7-31starting with MC/ServiceGuard, 7-41what is a Cell Server, 1-3

Cell Server Packageconfiguring with MC/ServiceGuard, 7-40

changingbackup ownership, 4-34datalist, 4-7max. number of running session, 4-42the view of backup objects, 5-4

choosingbackup mode, 3-6

Index

Index-iii

cleaning tape, 3-22client

recovering after disaster, 7-30updating, 2-10what is a client, 1-3

client hostsimporting to the cell, 2-6

clientsinstalling Omniback II software, 2-4

Command Line Interface, 1-11using, 1-11

commands, 1-11completed sessions

viewing details, 6-6complex device types

device chains, 9-3functions, 9-4libraries, 9-3OmniBack II operating on complex devices, 9-4stackers, 9-3

complex devicesmanaging, 9-3

complex devices and libraries, 9-1what are they, 9-2

componentsof OmniBack II, 1-4

compressingdata, 3-13, 4-29

compression algorithmcustomizing, 7-50

compression modulecustomizing, 7-50

conceptof OmniBack II, 1-3

concurrency, 4-34configuring

a cell, 3-1appearance of GUI, 1-9data compression, 3-13

data encryption, 3-13drives for the SCSI-II library, 9-10dynamic host backup, 4-17logical devices, 3-21, 3-23media management, 3-14non-standard libraries, 9-12pre/post-exec commands for a datalist/barlist,

7-6SCSI II library device, 3-26SCSI-II library, 9-7standalone devices, 3-25user classes, 3-36users, 3-36, 3-41

configuring a cell, 3-1overview, 3-1

configuring devicesnon-standard libraries, 9-13

congiguring backupwith load balancing, 4-37

constraintswith copying media, 7-27

copied mediaexporting, 7-27importing, 7-27

copyingmedia of backup sessions, 7-26media of restore sessions, 7-27

copying mediageneral constraints, 7-27

corrupted filesrestoring older versions, 5-8

cpio format compatibility, 3-18crash

recovering a Cell Server, 7-31CRC Check, 4-33creating

datalist for interactive backup, 4-23datalist from scratch, 4-6encryption code module, 7-45, 7-51

Index-iv

Index

media pools, 3-28critical system

example of recovering, 7-32recovering, 7-32

currently running sessionsviewing details, 6-3

customizingcompression module, 7-50device and media management view, 7-28encryption module, 7-45OmniBack II, 7-1periodic schedule, 4-46

Ddata

compressing, 3-13, 4-29encrypting, 3-13, 4-29protecting, 4-33

databaseadding to datalist, 8-13backing up, 8-13copying to an ASCII file, 8-9deleting a session, 7-24enlarging the size, 8-10managing growth, 8-4protection of backup information, 8-6reading database from ASCII file, 8-9restoring, 8-14shrinking the file, 8-9synchronizing MMDB and CDB, 8-10

datalistautomatical configuring, 4-5automatical generating, 4-5changing, 4-7changing backup ownership, 4-34creating, 4-6for interactive backup, 4-23load balancing, 4-36modifying, 4-7

previewing backup, 4-24scheduling backup on a specific date, 4-43scheduling periodic backup, 4-45skipping backup during holidays, 4-47starting interactive backup, 4-20understanding, 4-3

DCE Enterprise File Systemwith OmniBack II, 7-23

deinstallingOmniBack II from hosts, 2-11OmniBack II Modules, 2-11

deletinga session from a database, 7-24a session from media, 7-24

descriptionof backup options, 4-29

detectingCDF files, 7-18

devicebackup options, 4-33

device and media management viewcustomizing, 7-28modifying, 7-28

device chainsoperating, 9-4

device configurationnon-standard libraries, 9-13

device optionsconcurrency, 4-34CRC check, 4-33media pool, 4-34prealloc list, 4-34

devicesabout logical devices, 3-21auxiliary devices, 3-21cleaning tape support, 3-22configuring, 3-21configuring logical devices, 3-23configuring SCSI II library, 3-26

Index

Index-v

configuring standalone devices, 3-25device chains, 9-3libraries, 9-3locking when in use, 3-23managing complex devices, 9-3modifying the view, 3-35primary devices, 3-21stackers, 9-3

devices and librariescomplex, 9-1

directory versionselecting for restore, 5-8

dirty drivescleaning tape support, 3-22

disablingCDF files detection, 7-18

disasterpreparing for a disaster, 7-30recovering a Cell Server, 7-31recovering a client, 7-30recovering from a disaster, 7-34

disaster recovery, 7-29Disk Agent, 1-4display statistical information

restore options, 5-13distributing

OmniBack II software to clients, 2-4

Eenabling

CDF files detection, 7-18encrypting

data, 3-13, 4-29encryption algorithm

customizing, 7-45encryption code module

configuring, 7-45, 7-51creating, 7-45, 7-51

encryption module

customizing, 7-45Enterprise File System

with OmniBack II, 7-23erasing

a medium from a media pool, 3-29error messages, 10-2exclude

restore options, 5-11excluding

OmniBack II database directories, 4-10exporting

copied media, 7-27hosts from the cell, 2-8media from pool, 3-32

exporting hosts from the cellwhy, 2-6

Ffailed backup, 7-15

recovering, 7-14restarting, 7-15

failed host backup, 7-15file restore

specifying options restoring from a rawdisk, 5-26

file restore from a radiskselecting files, 5-24

file restore from a rawdiskstarting and monitoring, 5-27

file versionselecting for restore, 5-8

filesbrowsing for restore, 5-7configuring backup, 4-8locking during backup, 4-32lost, 5-8selecting for restore, 5-6

fileset restore optionsspecifying, 5-9

Index-vi

Index

filesystemconfiguring backup, 4-8excluding OmniBack II database directories,

4-10selecting backup options, 4-11selecting for backup, 4-8

filesystem backup, 3-5configuring, 4-8restoring, 5-4

filesystem backup options, 4-11full backup

mode, 3-6schedule example, 3-8

functionalityMC/ServiceGuard, 7-38

Ggenerating

datalists, 4-5global options

modifying, 7-13global options file

InitOnLoosePolicy, 3-19MaxBSessions option, 4-42MAXGUIMSG, 4-21

Graphical User Interface, 1-8modifying the appearance, 1-9starting, 1-9using, 1-8

GUI, 1-8

Hhelp

online help, 1-9holidays

skipping backup, 4-47host

backing up, 4-18host backup, 3-6, 4-18

configuring, 4-17failed, 7-15retrying, 7-14selecting, 4-18

hostsdeinstalling, 2-11deinstalling OmniBack II, 2-11exporting from the cell, 2-8importing, 2-6importing hosts with MC/ServiceGuard, 2-8importing hosts with multi-LAN cards, 2-8importing to the cell, 2-6moving between cells, 2-6updating modules, 2-10

HP-UX 10.xJournaled File System (JFS,VxFS), 7-19

HP-UX filesystem format compatility, 3-18

IID

media, 3-20ignoring hard links, 4-32importing

copied media, 7-27hosts to the cell, 2-6hosts with MC/ServiceGuard, 2-8hosts with Multi-LAN cards, 2-8media to media pool, 3-33

importing hosts to the cellwhy, 2-6

improved backup performanceVxFS, 7-20

improved disaster recovery, 7-29incremental backup, 3-7

levels of, 3-7mode, 3-7scheduling example, 3-8what to back up, 3-9

indentifying

Index

Index-vii

media, 3-20information about media

viewing, 3-30initializing

media in pool, 3-28InitOnLoosePolicy, 3-19installing

deinstalling OmniBack II from hosts, 2-11new OmniBack II version, 2-10OmniBack II software to clients, 2-4

installing OmniBack IIoverview, 2-2

integratingOmniBack II reporting with Netscape Commu-

nication Server, 7-43interactive backup, 4-20

creating a temporary datalist, 4-23of existing datalist, 4-20running, 4-20

JJFS, 7-19

concepts, 7-19limitations, 7-20restoring, 7-21script templates, 7-21

Journaled File Systemconcepts, 7-19limitations, 7-20

Llabel

media, 3-20LAN cards

importing hosts with Multi-LAN cards, 2-8last version of a file

restoring, 5-8libraries

operating, 9-6

library devicesconfiguring, 3-26

list restored objectsrestore option, 5-13

load balancing, 4-30configuring, 4-40configuring backup, 4-37configuring broken connections, 4-40periodical backup, 4-44what is, 4-36

locating files, 5-7lock files

restore option, 5-13locking

devices in use, 3-23files during backup, 4-32

logging files to databse, 4-31logical devices, 3-21

about logical devices, 3-21auxiliary devices, 3-21concept, 3-21configuring, 3-21, 3-23configuring SCSI II library device, 3-26configuring standalone device, 3-25device locking when in use, 3-23locking devices when in use, 3-23primary devices, 3-21using, 3-21

lost filesrestoring, 5-8

Mmanaging

complex devices, 9-3media, 3-14

MaxBSessions global option, 4-42MAXGUIMSG global option, 4-21MC/ServiceGuard, 7-38

backing up the secondary Cell Server, 7-41

Index-viii

Index

configuring, 7-38configuring Cell Server Package, 7-40configuring primary Cell Server, 7-39configuring secondary Cell Server, 7-39functionality, 7-38importing hosts with MC/Service, 2-10importing hosts with MC/ServiceGuard, 2-8prerequisites for configuration, 7-39starting a Cell Server, 7-41

mediaadding to pool, 3-28compatibility, 3-18compatibility with other formats, 3-18copying, 7-25creating media pool, 3-28erasing, 3-29exporting from media pool, 3-32ID, 3-20identification, 3-20importing to a media pool, 3-33initializing media in pool, 3-28label, 3-20media management tasks, 3-27media pools, 3-14modifying, 3-30modifying the view, 3-35moving, 3-31recycling, 3-32removing protection, 3-32scanning, 3-34verifying, 3-29viewing information about media, 3-30

Media Agent, 1-4media allocation policy, 3-16media class, 3-16media compatibility

managing, 3-18media condition factors, 3-17media information

viewing, 3-30media management, 3-14media of backup sessions

copying, 7-26media of restore sessions

copying, 7-27media pool, 3-14, 4-34

exporting media, 3-32initializing media, 3-28

media pool attributes, 3-17media allocation policy, 3-16media class, 3-16

media poolsadding media, 3-28creating, 3-28description, 3-15erasing media, 3-29importing media, 3-33modifying media, 3-30moving media, 3-31pool name, 3-15scanning media, 3-34verifying media, 3-29what are, 3-14

media protectionremoving, 3-32

media usage policy, 3-17merge

restore option, 5-12messages, 10-2

about errors, 10-2messages field

backup status description, 4-22viewing messages at restore, 5-17

MMDBsynchronizing with CDB, 8-10

mode of backup, 3-6full, 3-6incremental, 3-7

Index

Index-ix

modifyingappearance of GUI, 1-9backup ownership, 4-34datalist, 4-7Device & Media Management view, 3-35global options, 7-13media, 3-30number of running sessions, 4-42reconnect parameters, 4-40

monitoringa rawdisk restore, 5-22completed sessions, 6-5multiple cells, 6-7running sessions, 6-3several cells, 6-7viewing details of a running session, 6-3

mount promptautomatic handling, 7-3responding, 5-23

mount prompt handlingautomating, 7-3

mount prompt scriptsexamples, 7-4

mount request, 7-3responding, 5-23

move busy filesrestore option, 5-13

movingCell Server, 7-36media, 3-31

multi-LAN cardsimporting hosts to a cell, 2-8

multiple cellsmonitoring, 6-7

NNetscape Communication Server

integrating with OmniBack II reporting, 7-43network load, 5-16

no overwriterestore option, 5-12

non-standard librariesconfiguring, 9-12device configuration, 9-13operating, 9-12

non-standard OmniBack II tasks and concepts,7-1

OOB2RECONNECT_ACK option, 4-40omit deleted files

restore options, 5-13OmniBack II

architecture, 1-3backing up a database, 8-13backup session, 1-5catalogue retention, 8-6CDF files, 7-18Cell Server, 1-3clients, 1-3commands, 1-11components, 1-4copying database to ASCII file, 8-9customizing, 7-1data compression, 3-13deinstalling hosts, 2-11deleting a session from database, 7-24distributing to clients, 2-4error messages, 10-2exporting hosts, 2-8filesystem backup, 4-8global options file, 7-13Graphical User Interface, 1-8graphical user interface, 1-8HP OperationsCenter configuring, 3-11importing hosts, 2-6installation overview, 2-2logical devices, 3-21

Index-x

Index

online help, 1-9planning backup strategy, 3-5reading database from ASCII file, 8-9restore session, 1-6restoring database, 8-14shrinking the database, 8-9starting GUI, 1-9supporting HP EFS, 7-23supporting MC/ServiceGuard, 7-38updating modules, 2-10what is a cell, 1-3with JFS (VxFS) on HP-UX 10.0, 7-19

OmniBack II databaseenlarging the size, 8-10excluding from ordinary backup, 4-10managing the growth, 8-4moving to another system, 8-17

OmniBack II Modulesdeinstalling, 2-11

OmniBack II networkbacking up, 1-2

omnirc fileOB2RECONNECT_ACK option, 4-40OB2RECONNECT_RETRY option, 4-40

OmniStorage format compatibility, 3-18online help

using, 1-9operating

device chains, 9-4libraries, 9-6non-standard libraries, 9-12stackers, 9-5

operationbackup session, 1-5Graphical User Interface, 1-8restore session, 1-6

optionsfor running backup, 4-26pre-and post-exec commands, 7-6

protection of data, 3-10restore, 5-9

overridingscheduled backup options, 4-48

overriding of scheduled backup optionsundoing, 4-49

overviewof restores, 5-3

overwriterestore option, 5-12

ownershipchanging, 4-34

Pparallel restore, 5-18performing

full backup, 3-6periodic schedule

customizing, 4-46periodical backup

setting, 4-44planning

backup strategy, 3-5cell, 3-3cell access, 3-11OmniBack II cell, 3-3

pool attributesdescription, 3-15media allocation policy, 3-16media class, 3-16media condition factors, 3-17media usage policy, 3-17pool name, 3-15

poolscreating, 3-28exporting media, 3-32importing media, 3-33what is a media pool, 3-14

post- exec

Index

Index-xi

restore option, 5-14post-exec commands, 4-32, 7-6pre/post-exec commands

for an object, 7-11on a local host, 7-10on a remote host, 7-10

pre/post-exec commands for a datalist/barlistconfiguring, 7-6

prealloc list, 4-34predefined periodic schedule

selecting, 4-45pre-exec commands, 4-32, 7-6

restore option, 5-14preparing

for a disaster, 7-30prerequisites

configuring MC/ServiceGuard, 7-39preserving access time attributes, 4-32previewing backups, 4-24previous sessions

viewing, 6-5primary

logical devices, 3-21primary Cell Server

configuring with MC/Service Guard, 7-39private data, 4-30protection

of backed up data, 3-10of backup information, 8-6

protection attributesrestore option, 5-12

protection of mediaremoving, 3-32

public data, 4-30

Rrawdisk

configuring backup, 4-13selecting rawdisk backup options, 4-15

selecting rawdisk sections for backup, 4-14rawdisk backup, 3-6

configuring, 4-13rawdisk restore

restoring files from a rawdisk backup, 5-24selecting files from a rawdisk restore, 5-24specifying options for file restore, 5-26starting and monitoring, 5-22, 5-24

rawdisk restore optionsspecifying, 5-21

rawdisk sectionchoosing for restore, 5-20restoring, 5-20selecting for restore, 5-20

reconnect parametersmodifying, 4-40

reconnectingbroken connections, 4-40

reconnecting broken connections, 4-30recovering

a Cell Server, 7-31a client system, 7-30a critical system, 7-32a failed backup, 7-14data after disaster, 7-29from a disaster, 7-34

recovering Celll Server Packageconfiguring with MC/ServiceGuard, 7-40

recurring backups, 3-10recycling media, 3-32removing

protection of media, 3-32report level, 4-31reporting

about backups through WWW server, 7-42reporting scripts

using, 7-43responding

to mount prompt request, 5-23

Index-xii

Index

to mount request, 5-23restarting

failed backup, 7-15restore

monitoring sessions, 6-3network load, 5-16options for file restore from rawdisk, 5-26restore as option, 5-10running, 5-15searching for files, 5-18selecting files, 5-6starting, 5-15starting and monitoring, 5-15target hostname option, 5-12

restore intorestore option, 5-10

restore optionsdisplay statistical information, 5-13exclude, 5-11for fileset, 5-9list restored objects, 5-13lock files, 5-13match entire filename, 5-10merge, 5-12move busy files, 5-13no overwrite, 5-12omit deleted files, 5-13overwrite, 5-12post- exec, 5-14pre- exec, 5-14protection attributes, 5-12restore as, 5-10skip, 5-11sparse files, 5-13specifying for a rawdisk, 5-21specifying for filesets, 5-9target hostname, 5-12time attributes, 5-13

restore session

how does it work, 1-6selecting options, 5-12

restoringa file with unknown filename, 5-28changing the view of backup objects, 5-4files from a filesystem backup, 5-4files from a rawdisk backup, 5-24JFS (VxFS), 7-21lost files, 5-8older versions of corrupted files, 5-8overview, 5-3parallel restore, 5-18rawdisk section, 5-20responding to mount request, 5-23selectig version of a backup object, 5-8selecting a rawdisk section, 5-20specifying rawdisk restore options, 5-21starting and monitoring with rawdisk, 5-22the last version of a lost file, 5-8viewing the messages field, 5-17

restoring data, 5-1restoring files from a rawdisk

starting and monitoring, 5-27retrying

host backup, 7-14running

incremental backup, 3-7restore, 5-15

Sscan

quick scan using barcodes, 3-34scanning

media, 3-34schedule

types of backup schedules, 3-10scheduled backup options

overriding, 4-48scheduling

Index

Index-xiii

backups, 4-41on a specific backup date, 4-43periodic backup, 4-45skipping backup during holidays, 4-47

SCSI-II libraryconfiguring, 9-7example of configuration, 9-8what is it, 9-7

SCSI-II library configurationexample, 9-8

SCSI-II library drivesconfiguring, 9-10

searching for filesrestore, 5-18

secondary Cell Serverconfiguring with MC/Service Guard, 7-39

selectinga filesystem for backup, 4-8a rawdisk section for restore, 5-20backup mode, 3-6backup objects at restore, 5-5directory version for restore, 5-8file version for restore, 5-8files from a rawdisk restore, 5-24files to restore, 5-6host backup, 4-18options for restore, 5-12rawdisk backup options, 4-15rawdisk sections for backup, 4-14

selecting backup objects, 5-5session

changing ownership, 4-34changing the number of sessions, 4-42deleting from a database, 7-24scheduling on a specific date, 4-43scheduling periodic backup, 4-45skipping backup during holidays, 4-47

Session Manager, 1-4sessions

monitoring, 6-3viewing completed sessions, 6-5viewing details, 6-3viewing details of completed sessions, 6-6

settingperiodical backup, 4-44

several cellsmonitoring, 6-7

skiprestore option, 5-11

sparse filesrestore option, 5-13

specific filessearching at restore, 5-18

specifyingfileset restore options, 5-9

stackersoperating, 9-5

standalone devicesconfiguring, 3-25

startinga rawdisk restore, 5-22, 5-24backup, 4-24failed backup, 7-15Graphical User Interface, 1-9restore, 5-15

starting a Cell Serverwith MC/ServiceGuard, 7-41

starting and monitoringfile restore from a rawdisk, 5-27, 5-28

status descriptionsof backup session, 4-22

status of backup sessionsmessages description, 4-22

synchronizingOmniBack II database, 8-10

Ttar format compatility, 3-18

Index-xiv

Index

tasksmedia management, 3-27

temporary datalistcreating, 4-23

time attributesrestore option, 5-13

troubleshooting, 10-2type of backup

choosing, 3-5host backup, 3-6rawdisk, 3-6selecting, 3-5

types of backupfilesystem, 3-5

types of WWW reports, 7-44

Uunattended backups, 3-10understanding

datalist, 4-3updating

OmniBack II clients, 2-10OmniBack II software, 2-10

upgradingOmniBack II software, 2-10

usage policy, 3-17media, 3-17

user classdescription of access rights, 3-38

user classesconfiguring, 3-36description of, 3-37

usersconfiguring, 3-41configuring user classes, 3-36description of access rights, 3-38

usingbackup devices, 3-21logical devices, 3-21

media management, 3-27

Vverifying

media, 3-29media in pool, 3-29

Veritas File Systemconcepts, 7-19limitations, 7-20script templates, 7-21

versioninstalling new OmniBack II version, 2-10

viewingdevices and media, 3-35information about media, 3-30messages field at restore, 5-17

VxFcopyingmedia, 7-25

VxFSconcepts, 7-19improved backup performance, 7-20limitations, 7-20mounting, 7-21restoring, 7-21script templates, 7-21with OmniBack II, 7-19

WWWW reporting, 7-42

types, 7-44

upload

Documents

sf qqh gvt esd

sf qq gv es

ioctl dev scsi 0 dev scsi 0

bma hostname njiva 48l time

prototypes void endif

vt esqh ge

congurable parameter maxguimsg

netscape fasttrack server