Upload

HP OpenView OmniBack II Administrators Guide
HP Part No. B1957-90036 October 1997
& ! $ " #%# !
Hewlett-Packard makes no warranty of any kind with regard to this material, and specifically disclaims the implied warranties of merchantability and fitness for a particular purpose. Hewlett-Packard shall not be liable for errors contained herein or for any damages, whether direct, indirect consequential, incidental, or special, in connection with the furnishing, performance, or use of this material The specific warranty information for the product as to which this material related is available in Hewlett-Packards purchasing and licensing terms and conditions. Copyright 1997 Hewlett-Packard Company All rights are reserved. No part of this document may be photocopied reproduced, or translated to another language without the prior written consent of Hewlett-Packard Company. The information contained in this document is subject to change without notice. Use, duplication, or disclosure by the Government is subject to restrictions as set forth in subparagraph (c)(1)(ii) of the Rights in Technical Data and Computer Software clause in DFARS 252.227-7013. Rights for non-DOD U.S. Government Departments and Agencies are as set forth in FAR 52.22719(c)(1,2). OSF/Motif is a trademark of the Open Software Foundation in the U.S. and other countries. HP-UX 9.x and 10.x for HP 9000 Series 700 and 800 computers are X/Open Company UNIX 93 branded products. X/Open is a registered trademark, and the X device is a trademark of X/Open Company Ltd. in the UK and other countries. UNIX is a registered trademark in the U.S.A. and other countries, licensed exclusively through X/Open Company Limited.. DOS, Windows, Windows for Workgroups, Windows 95, and Windows NT are 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 Gradient Technologies, Inc.
ii
Conventions
To make the information easier to understand, this manual uses various typographic conventions within the text. The following list explains these conventions:
Computer Font
Computer font is used for the following: Directories and names:

/opt/omni/bin
Screen prompts: Select (highlight) the device with the Mount Request status. Messages displayed by the system: The session is Pending then finally Running. What Bold you type, for example:
Home_Directory
Bold face is used for command names, and the names of windows and elds: Select Object Add Filesystem ..the OmniBack II Editor window appears ..in the Mountpoint field
OK
References to buttons on the display look like this: Click on the Help button Click on the Options button
8 0 650 4 20 ( 11( 73#31)'

iii
In This Book
HP OpenView OmniBack II Administrators Guide describes features and functions of the HP OmniBack II network backup product. Target Audience This manual is intended for administrators who are responsible for the planning, setup, and maintenance of the network backup. The manual is organized as follows: Chapter 1 Chapter 2 Chapter 3 Chapter 4 Chapter 5 Chapter 6 Chapter 7 Chapter 8 Chapter 9 Chapter 10 Glossary Introducing HP OpenView OmniBack II Installation Overview Conguring a Cell Backing Up Your System Restoring data. Monitoring sessions Advanced tasks and concepts. Maintaining the OmniBack II Database. Using Complex Devices and Autochangers. Troubleshooting information. Denitions of terms related to the product.
G ( ( D 6 B @ 11FE8 1CA0 9
iv
Contents
1. Introducing HP OpenView OmniBack II OmniBack II Architecture.......................................................................... 1-3 OmniBack II Components ...................................................................... 1-4 How a Backup Session Works ................................................................ 1-5 How a Restore Session Works ................................................................ 1-6 Using the User Interfaces........................................................................... 1-8 Graphical User Interface......................................................................... 1-8 OmniBack II Online Help....................................................................... 1-9 The 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-6 Importing Hosts with Multi-LAN Cards ................................................ 2-8 Exporting 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. Conguring a Cell
Contents
Planning the Cells .......................................................................................3-3 Planning Your Backup Strategy..................................................................3-5 Choosing the Type of Backup .................................................................3-5 Choosing the Mode of Backup ................................................................3-6 Deciding What to Back up ......................................................................3-9 Choosing a Backup Schedule ................................................................3-10 Protection...............................................................................................3-10 Planning Cell Access and Security........................................................3-11 Using Data Compression.......................................................................3-13 Using Data Encryption ..........................................................................3-13 Media Management ..................................................................................3-14 The Media Pool Approach ....................................................................3-14 Pool Attributes.......................................................................................3-15 Managing Media Compatibility ............................................................3-18 Media Identication ..............................................................................3-20 Conguring and Using Logical Devices...................................................3-21 The Concept of Logical Devices ...........................................................3-21 Device Locking While in Use ...............................................................3-23 Conguring Logical Devices.................................................................3-23 Conguring Typical Devices.................................................................3-25 Media Management Tasks ........................................................................3-27 Creating a Media Pool ...........................................................................3-28 Adding Media to a Pool.........................................................................3-28 Verifying a Medium...............................................................................3-29 Erasing a Medium .................................................................................3-29 Modifying a Medium.............................................................................3-30
ii
Contents
Viewing Information About a Medium ................................................ 3-30 Moving a Medium ................................................................................ 3-31 Recycling Media/Removing Protection................................................ 3-32 Exporting a Medium ............................................................................. 3-32 Importing a Medium ............................................................................. 3-33 Scanning Media .................................................................................... 3-34 Modifying Device and Media Management View................................ 3-35 Conguring User Classes and Users........................................................ 3-36 Conguring User Classes ..................................................................... 3-38 Conguring Users................................................................................. 3-41
4. Backing Up Your System Understanding Datalists and Barlists ......................................................... 4-3 What is a Datalist? .................................................................................. 4-3 What is a Barlist?.................................................................................... 4-4 Generating Datalists................................................................................ 4-5 Creating Datalists.................................................................................... 4-6 Modifying a Datalist ............................................................................... 4-7 Conguring a Filesystem Backup .............................................................. 4-8 Selecting a Filesystem to Back up .......................................................... 4-8 Selecting the Filesystem Backup Options ............................................ 4-11 Conguring a Rawdisk Backup ............................................................... 4-13 Selecting Rawdisk Sections for Backup ............................................... 4-14 Selecting the Rawdisk Backup Options................................................ 4-15 Conguring Host Backup ........................................................................ 4-17
iii
Contents
Selecting a Host to Back up ..................................................................4-18 Running Interactive Backups....................................................................4-20 Starting a Backup of an Existing Datalist .............................................4-20 Status Messages.....................................................................................4-22 Creating a Temporary Datalist...............................................................4-23 Previewing Your Backup.......................................................................4-24 Starting Your Backup ............................................................................4-24 Using Backup Options..............................................................................4-26 Description of Backup Options .............................................................4-29 Device Options ......................................................................................4-33 Transferring Backup Ownership ...........................................................4-34 Load Balancing.........................................................................................4-36 Conguring 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-42 Skipping Backups During Holidays ......................................................4-47 Overriding Scheduled Backup Options .................................................4-48
5. Restoring Data Restore Overview ......................................................................................5-3 Restoring Files from a Filesystem Backup.................................................5-4
iv
Contents
Changing the View of Backup Objects................................................... 5-4 Selecting the Backup Object................................................................... 5-5 Selecting the Files to Restore ................................................................. 5-6 Selecting a File/Directory Version.......................................................... 5-8 Specifying Fileset Restore Options ........................................................ 5-9 Activating and Monitoring the Restore ................................................ 5-15 Searching for a Specic File................................................................. 5-18 Parallel Restore..................................................................................... 5-18 Restoring a Rawdisk Section (Logical Volume) ...................................... 5-20 Choosing the Rawdisk Section to Restore............................................ 5-20 Specifying Rawdisk Restore Options ................................................... 5-21 Starting and Monitoring a Rawdisk Restore......................................... 5-22 Responding to Mount Requests ............................................................ 5-23 Restoring Files from a Rawdisk Backup ................................................. 5-24 Selecting the File from a Rawdisk to Restore ...................................... 5-24 Specifying Rawdisk Restore Options ................................................... 5-26 Starting and Monitoring File Restore from a Rawdisk......................... 5-27 Restoring 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
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 Conguring Pre/Post-Exec Commands for a Datalist/Barlist .................7-6 Pre- and Post- Exec Commands for a Datalist/Barlist ............................7-7 Pre- 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-14 Failed Host Backup ...............................................................................7-15 Restarting 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-19 Improved Backup Performance.............................................................7-20 Limitations.............................................................................................7-20 Restoring ...............................................................................................7-21 Script 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
vi
Contents
Modifying Device and Media Management View................................... 7-28 Disaster Recovery .................................................................................... 7-29 Improved Disaster Recovery ................................................................ 7-29 Preparing For a Disaster ....................................................................... 7-30 Recovering a Client Host...................................................................... 7-30 Recovering a Cell Server ...................................................................... 7-31 Example 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-38 Prerequisites for Conguration............................................................. 7-39 Conguring Primary and Secondary Cell Servers................................ 7-39 Conguring the Cell Server Package.................................................... 7-40 Starting the Cell Server......................................................................... 7-41 Backing up a Secondary Cell Server System ....................................... 7-41 OmniBack II Web Based Reporting......................................................... 7-42 Integrating OmniBack II Reporting with Netscape Fasttrack Server... 7-43 Using 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
vii
Contents
8. Maintaining the OmniBack II Database Installing and Conguring the Database.....................................................8-3 Managing the Growth of the Database .......................................................8-4 Managing the Growth of the Database....................................................8-4 Purging Obsolete Data from the Database ..............................................8-7 Shrinking the Size of the Database File ..................................................8-9 Enlarging 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-3 How OmniBack II Functions with Complex Devices.............................9-4 Conguring a SCSI-II Library....................................................................9-7 Example of a Library Conguration .......................................................9-8 Conguring a Non-Standard Library for Use with OmniBack II.............9-12 How OmniBack II works with non-standard libraries ..........................9-12 Device Conguration ............................................................................9-13
viii
Contents
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
ix
Contents
Introducing HP OpenView OmniBack II
1-1
In This Chapter HP OpenView OmniBack II is the next generation of the OmniBack family of backup and restore utilities. It expands the functionality of OmniBack and OmniBack/Turbo by adding powerful new features that allow you to easily manage large networks. These new features include a comprehensive new media management system that tracks not only your backup media but also the data contained on those media. The exibility provided by OmniBack II enables you to develop customized backup policies while managing from a central point backup operations for each part of your organization. This allows you to create a backup solution that best ts the needs of your organization. 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 les create critical downtime until the les can be located and restored. OmniBack II includes a powerful media management feature that helps you quickly locate and restore lost les or directories, and guides you through the process.
1-2
H s#vt Esqh #ge)b#I #USQI H H w X u Y I r d p Y i I h f d c a ` Y X W V TRP
OmniBack II Architecture
HP OpenView OmniBack II provides a reliable, exible solution for your backup needs by introducing the concept of Cells. Cells allow you to divide your network into independent logical units that correspond to different backup strategies. OmniBack II lets you manage these cells from a central point and initiate backup, restore, and monitor actions on any cell in your network. This exibility provides a scalable backup solution that grows as your network grows. OmniBack II allows you to have many cells in the network, and each of these cells operates as an independent part of the enterprise network. Each cell is installed and congured separately. How the cells are congured determines how backups are handled, which devices are used, and so forth. Dividing the network into separate cells gives network administrators greater exibility in developing a backup policy for each entity of their organization. A cell consists of a set of hosts: a Cell Server and Clients. A host can only belong to one cell. The Cell Server is the main system in the cell and runs the core OmniBack II software and also contains the OmniBack II database. A client can be any host with the supported architecture. Essentially, a client can be a host being backed up, a host with a backup device to which the backup data is stored, or both. The role of the client depends on the software installed. See HP OpenView OmniBack II Installation Guide and Distributing HP OmniBack II to Clients on page 2-4 for installation instructions. OmniBack II has a media management system which allows you to track the backup media and the data contained on those media. The term media refers to the physical media on which the backed-up les are stored. Media exist in several forms: tape refers to DDS (Digital Audio Tape) or similar magnetic tape; disk refers to a hard disk or rewritable optical disk.
4 75 1 F#9 9 )D 1gy 5 4 6 B G 6 0 H st #EsqQ Yh #sxFEI #USI H H w X u Y I r d p i I h f d c a ` Y X W V TRP

1-3
OmniBack II Components
OmniBack II consists of three basic components - User Interfaces, Cell Server software, and Disk and Media Agents. Each of these components can run on a different host in the cell. Figure 1-1 shows this hierarchical architecture. On the rst level, OmniBack II has two types of user interfaces, a Graphical User Interface (GUI) designed for simplicity of use and the Command Line Interface (CLI), designed for efcient use in scripts for experienced UNIX administrators.
ols
ols
ntr
ntr
Co
Co
tus
Sta
Figure 1-1
The second level is the Cell Server software, which runs on the Cell Server host. When a command is entered on any host in the cell (using the GUI or command-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
1-4
4 75 1 )#9 9 #)D 1sy 5 4 6 B G 6 0 H s#vt Esqh #ge)b#I #USQI H H w X u Y I r d p Y i I h f d c a ` Y X W V TRP

User Interface
Commands Visual Cues
Cell Server Software
St atu sC
Co ntr ols
tro ls on
Disk Agent
Data Flow
Media Agent
HP OmniBack II Components
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 for managing the clients needed to execute the command. To perform a backup or restore, the Session Manager determines which devices are needed and how these will be used. Next, it starts the processes needed to control these devices. 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 a disk. The Media Agent reads from and writes to a backup medium. Figure 12 shows how these agents operate during a backup or restore.
Backup Process
Disk Agent Disk Media Agent Media
Restore Process
Media Agent Media Disk Agent Disk
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 this session, OmniBack II performs a backup of requested les and disks to the specied media. 1. When the user initiates the backup, the Cell Server determines the type of session that has been requested (backup) and starts the appropriate Session Manager. 2. The Session Manager reads the specified datalist and determines what needs to be backed up and which devices will be used. 3. The Session Manager then determines how many Media Agents are
1-5
4. The Monitor window is displayed. This window lets you respond to mount prompts and view the progress of a backup session. 5. The Disk Agents and the Media Agent determine whether a local or remote transfer is needed, and the Disk Agents start sending data to the Media Agent. 6. If more than one Disk Agent is used, the Disk Agents send data to the Media Agent concurrently and the Media Agent places the data on the medium. 7. As each block of data is written to the media, the Media Agent sends information to the Session Manager about what was backed up. The Session Manager uses this information to update the catalog of backed-up files in the OmniBack II database.
How a Restore Session Works

A restore session starts when a restore request is initiated. During this session, OmniBack II performs a restore of requested les and disks from the media. 1. When the user initiates the restore, the Cell Server determines the type of session that has been requested (restore), and starts the appropriate Session Manager. 2. The Session Manager then determines which filesystems or directories will be restored, which devices will be used, and what restore options have 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 will be used and a Disk Agent is started for the disk where the data will be restored. 4. The Monitor window is displayed. This window lets you respond to
1-6
4 75 1 )#9 9 #)D 1sy 5 4 6 B G 6 0 H s#vt Esqh #ge)b#I #USQI H H w X u Y I r d p Y i I h f d c a ` Y X W V TRP
needed and starts the Media Agents and the Disk Agents needed for these Media 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 that will be read.
mount prompts and view the progress of a restore session. 5. The Disk Agent and the Media Agent determine whether a local or remote transfer is needed and the Media Agent starts sending data to the Disk Agent. 6. The Session Manager then updates the OmniBack II database and the Disk Agent writes the data to the disk.

1-7
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 Cell Console 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 cues to using OmniBack II features and functionality. It guides you through all the administrative, backup, monitor, and restore tasks. The GUI uses X11/Motif features such as buttons and list boxes to enhance its usability. Whenever possible, list boxes are provided to allow you to select from a list instead of typing in your selection. In addition, a comprehensive online help system provides information about each window and each task. When in Monitor mode, the OmniBack II GUI uses color to alert you to changes in the status of backup and restore sessions. You can monitor all sessions in your cell or focus on a specic session. The following naming convention is used to identify commands for the GUI interface and the command-line interface: commands for the GUI start with a word xomni followed by a word representing the function. For example, the command xomnirestore starts the GUI for restore tasks only.
1-8
8 4 45 9 4 # 30 v 8 1A10 #8 4 B5 6 H s#vt Esqh #ge)b#I #USQI H H w X u Y I r d p Y i I h f d c a ` Y X W V TRP
To use the Graphical User Interface of OmniBack II, enter: xomni xomniadmin xomnibackup xomnicellmon xomnimonitor xomnirestore to start the GUI for the complete OmniBack II functionality to start the GUI for admin (conguration) to start the GUI for backup to start the GUI for monitoring multiple cells to start the GUI for monitoring a single cell to start the GUI for restore
The /usr/lib/X11/app-defaults/xomni command denes the appearance of the Graphical User Interface and can be modied if desired.
OmniBack II Online Help

Information about OmniBack II is available from two sources: this manual and the online help system. This manual contains the information you need to plan and administer your OmniBack II network, and some more commonly used tasks. The online help system contains the information you need to perform all available tasks. The online help system provides four types of help:
On Help On Window
Provides help on using the OmniBack II help system. Displays information on the purpose of each window and how the elds of that window are used. Help on Window is available for each window. Included is information on the menu items, elds, and buttons of the window. Displays information for performing specic tasks, such as scheduling a backup. Displays version and copyright information for OmniBack II
On Tasks On Version
You access the online help by either using the Help pull-down menu or the Help buttons provided on OmniBack II windows.
1-9
8 4 45 9 4 # 30 v 8 1A10 #8 4 B5 6 H st #EsqQ Yh #sxFEI #USI H H w X u Y I r d p i I h f d c a ` Y X W V TRP
Figure 1-4
Within the help text are hyperlinks (cross-references) to related information and denitions. 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 broken underlining.
1-10

OmniBack II Online Help
The Command Line Interface

The command line interface follows the standard UNIX format for commands and options and provides complete OmniBack II functionality. You can use these commands in scripts to speed up your commonly performed tasks. This list provides a short description of each OmniBack II command. For more details refer to the appropriate manpage for the command. omniabort omnib omnicc omnicellinfo Aborts a specied active backup or restore session. Performs a backup of a specied datalist. All backup options are supported. Checks and displays licensing summary for the cell. Displays conguration information of an OmniBack II cell backup objects, media pools, devices, hosts, and the database. Copies data from one OmniBack II medium to another. No information about the copy is recorded in the OmniBack II database Automatically creates a datalist for the cell or the local host. Queries the OmniBack II database for information on backups and restores performed. Checks the consistency of the OmniBack II database. The information about the copy is recorded in the OmniBack II database. Initializes the OmniBack II database. All information on previous backup and restores sessions is lost. A set of OmniBack II database conguration tools, such as extending the database size, write and write the database to/from an ASCII le, and so forth. Creates a copy of an OmniBack II medium.
1-11
omnicp
omnicreatedl omnidb omnidbcheck
omnidbinit omnidbutil
omnimcopy
8 4 45 9 4 # 30 v 8 1A10 #8 4 B5 6 H st #EsqQ Yh #sxFEI #USI H H w X u Y I r d p i I h f d c a ` Y X W V TRP
omniminit omnimlist
omnimm
omnimnt
omnimver
omnir omnistat
omnisv.sh omnitrig omnidownload
omniupload
1-12
Initializes a medium. The medium is assigned to an OmniBack II media pool and added to the database. Displays the content of an OmniBack II medium. It scans the catalog of the medium and shows all objects and sessions on the medium. Manages media and media pools, checks the protection of a medium, maintains the contents of the repository of an library device. Conrms or cancels the mount prompt request issued by a logical device where no media is available for backup. Once you have put the requested medium in the device, you can conrm the mount request. Veries the data on an OmniBack II medium. It reads the data and checks for correct format. Optionally, CRC checking of each block can be specied. Performs a restore of OmniBack II backup. You can restore any objects from the OmniBack II backup. Displays the status of an active backup or restore session. You can display the status of all active sessions or just one specied session. Starts, stops, or displays the status of OmniBack II processes. Triggers scheduled backups. This command is normally executed in the cron script. Displays the conguration of a device as recorded in the OmniBack II database. Use this command to display the conguration or to create an ASCII le containing the device conguration description, which can then be modied and omniuploaded to the database. Uploads the device conguration from a le. Use this command to congure a new device or to change the conguration of an existing device by using the omnidownload command rst.
Installation Overview
2-1
In This Chapter OmniBack II introduces the concept of cells. By dividing a network into cells representing the entities of an organization, the network administrator can dene a unique backup strategy for an organizational entity. How you organize your network determines the backup efciency of your cell. Each cell is installed and congured 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 page 3-1 for more information. Installing the OmniBack II software package on the Cell Server. See HP OpenView OmniBack II Installation Guide for more information. Distributing the OmniBack II modules to the clients in the cell. See
2-2
p Y R h d I YP uP Qh ET S u #SI H
Distributing HP OmniBack II to Clients on page 2-4 for more information. Configuring the devices, users, and media for the cell. See the appropriate sections in Chapter 3, Configuring a Cell, on page 3-1 for more information.
p Y R h d I YP uP h vb#T Q u S#I H
2-3
Distributing HP OmniBack II to Clients

Once you have installed the complete OmniBack II software on the Cell Server, you must distribute the appropriate OmniBack II software modules to all client hosts in the cell using the GUI. The function of a host is determined by the software modules you install. The following list shows these modules: User Interface Disk Agent Media Agent The user interface for OmniBack II. It must be installed on all hosts from which you want to control OmniBack II. Agent that reads and writes from a disk containing data. It must be installed on all hosts which you want to back up. Agent that reads and writes from a device containing a backup medium. It must be installed on all hosts where the backup devices are congured.
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 the Media Agent module, hosts 4,5, and 6 have the Media Agent and the Disk Agent. You install hosts 1,2, and 3 as one group, and hosts 4,5, and 6 as another.
g f @ y e
To perform the installation, you will need either root or admin access or an account with root or admin capabilities access for every host on which you want to install HP OmniBack II modules.
1. In the OmniBack II Main menu, select Install to open the OmniBack II - Cell Administration window. 2. Select EditInstall hosts... to open the Cell Administration - Install window.
2-4
850 d ' ( 73#4 6 )5 9 9 #)D 1se)10 31 6 Q8 6 G 6 0 y 65 5 p Y R h d I YP uP Qh ET S u #SI H
3. Select the Add... button to open the Install - Load Hosts window. The Domain eld of the window shows the IP address for your cell. To change this IP address, click the eld with the address and enter the new IP address. You can select hosts by typing their names in the Filter eld and selecting Add. Short and long hostnames can be used. You can also use wildcards to select several hosts at once. You can select hosts by their names or their IP addresses by entering the exact 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, close the Install- Load Hosts window and return to the Cell Administration - Install window. The hosts you specified now appear in the Installation Target Hosts field. 5. Select which OmniBack II modules you want to install on selected hosts. 6. To confirm this host configuration, click the OK button. Follow instructions and messages in the HP OmniBack II - Install Terminal window.
850 d ' ( 73#4 6 )5 9 9 #)D 1se)10 31 6 Q8 6 G 6 0 y 65 5 p Y R h d I YP uP h vb#T Q u S#I H

2-5
Importing and Exporting Hosts

When you distribute software from the Cell Server to other hosts, they are automatically added to the cell. If you need to modify your cell conguration, move the host from one cell to another, or perform similar tasks without removing the OmniBack II software from the host, you can export and import hosts. The manual importing and exporting of a host is useful, for example, when you want to do one of the following: An emergency fix for problems caused by insufficient licenses. By exporting a host from the cell, its license becomes available to some other host. This is, however, only a temporary solution until you order and get more 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 II Modules are already installed) to the cell. To add a host, follow these steps: 1. In the HP OmniBack II - Cell Administration window, select EditImport from the menu bar to open the Cell Administration - Import Hosts window.
2-6
858 ( 6 ( j f i 0 6 ( h 71F10 75 1h k110 5 1 9 p Y R h d I YP uP Qh ET S u #SI H
2. Select Add... to open the Import - Load Hosts window. The Domain eld of the window shows the IP address for your cell. To change this IP address, click the eld with the address and enter the new IP address. You can select the hosts by typing their names in the Filter eld and selecting Add. Short and long hostnames can be used. You can also use wildcards to select several hosts at once. 3. When you have specified all the hosts that you want to import, close the Import - Load Hosts window and return to the Cell Administration - Import Hosts window. The hosts you specified now appear in the Hosts field. 4. Click the Import button to import the hosts.
Figure 2-2
Import Host window
858 ( 6 ( j f i 0 6 ( h 71)10 75 1h k1ml0 75 1 9 p Y R h d I YP uP h vb#T Q u S#I H

2-7
Importing Hosts with Multi-LAN Cards

Hosts congured with multiple LAN cards or MS/ServiceGuard have multiple network names. To avoid having OmniBack II assign licenses to all the network names of the same host, follow the procedure below. You can only import one hostname at a time using this procedure. 1. Using the method described in the previous section, import the host with its primary hostname to the cell. A primary hostname is the name you get using the UNIX hostname command and will be licensed by OmniBack II. 2. In the Cell Administration - Import Hosts select Add... to open the Import - Load Hosts window. Using any of the methods enter one of the multiple hostnames to the list of hosts. You must only import one hostname at a time. 3. Close the Import - Load Hosts window and return to the Cell Administration - Import Hosts window. The hostname you specified now appears in the Hosts field. 4. Click the Additional Host Name button to import the hostname. OmniBack II will add the hostname to the cell but will not assign an additional 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 without removing the OmniBack II modules installed on it. To export a host, follow these steps: 1. In the HP OmniBack II - Cell Administration window, select the hosts you want to export from the cell.
2-8
858 ( 6 ( j f i 0 6 ( h 71F10 75 1h k110 5 1 9 p Y R h d I YP uP Qh ET S u #SI H
2. Select EditExport from the menu bar. The selected hosts are displayed in the Hosts field. 3. You can remove hosts from the list by selecting them and clicking Delete. 4. Click the Export button to export the hosts in the Hosts list. 5. Remove all appearances of the exported hosts from datalists. See the online help for instructions how to modify datalists.
858 ( 6 ( j f i 0 6 ( h 71)10 75 1h k1ml0 75 1 9 p Y R h d I YP uP h vb#T Q u S#I H

2-9
Updating OmniBack II Clients

If you want to update to a new version of OmniBack II, you can do it easily by installing the new software on the Cell Server and then performing the following procedure to update all hosts in the cell. You can manually select which modules you want to update. OmniBack II automatically checks all the hosts in the cell and updates the selected modules. OmniBack II automatically removes installation packages of the older version 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 the existing ones. The procedure may take some time, depending on your cell conguration. 1. In the HP OmniBack II - Cell Administration window, select EditUpdate All to open the Cell Administration - Update Hosts window. 2. Select the modules you want to update and start the update by clicking OK. 3. Follow instructions and messages in the HP OmniBack II - Update Terminal window. The new version number of the modules you updated now appears for all the hosts in the HP OmniBack II - Cell Administration window.
2-10
850 d 34 6 )' 9 9 #)D 1sml0 711h G 6 0 y 65 i p Y R h d I YP uP Qh ET S u #SI H
Deinstalling OmniBack II from a Host

If your system conguration changes, you may need to deinstall OmniBack II software from a host. Deinstalling OmniBack II from a host removes all the OmniBack II modules from the host and removes all references to this host from the Cell Server. This feature is supported for UNIX systems only.
To Deinstall OmniBack II Modules

1. In the HP OmniBack II - Cell Administration window, select the host you want to deinstall. 2. Select Edit Deinstall from the menu bar to open the Cell Administration - Deinstall window. 3. Select modules you want to deinstall. Only modules currently installed on the host are available for deinstallation. If you deinstall all the available modules, this host is completely removed from the OmniBack II cell. 4. Click OK to begin the deinstallation process. Follow instructions and messages in the HP Cell Administration - Deinstall Terminal window. 5. Remove all references to this host from datalists. See the online help for instructions how to modify the datalists.
58 ( G 6 0 y d 58 6 Q1)En1( Q9 9 #)D 1s10 6 d Q10 #4 p Y R h d I YP uP h vb#T Q u S#I H

2-11
58 ( G 6 0 y d 58 6 Q1)En1( Q9 9 #)D 1s10 6 d Q10 #4 p Y R h d I YP uP Qh ET S u #SI H
2-12
Configuring a Cell
3-1
In This Chapter Conguring a cell involves dening a backup strategy, conguring your logical devices, implementing a media management strategy, and setting up the user access security. The information you need to plan your cell conguration is explained in the following sections. The actual steps for doing the conguration are explained in the online help system. The online help system is divided into task help and window help. The task help provides detailed step-by-step information for conguring a cell. The window help provides detailed information about the elds and buttons in each window.
3-2
h o EI U#Q#T o u ` YR W ` p I
Planning the Cells

A cell can represent an organizational entity (such as a department) or a geographical location (such as a eld ofce). It consists of a set of hosts (server and clients) having a common backup policy, located in the same time zone, and existing on the same LAN. How the network is divided into cells has a major impact on the backup strategy for the network, so careful planning is important. For the best performance, we recommend having a maximum of 50 hosts in a cell. Additional factors that affect performance include the amount of data and the number of les to be backed up.
g f @ y e
A host can belong only to one cell.
HP OmniBack II allows you to manage and monitor backup and restore activities at either the cell or enterprise level. An administrator denes the backup policies, security, logical devices, media pools, and users for each cell. When dening the cells, consider the following factors: Quantity of Data Type of Data Importance of Data The amount of data to be backed up. Files, databases, specic applications (see HP OpenView OmniBack II Integrations Guide) Is data modied often and does it require regular backup, as with users working les, or is it mostly permanent, such as system les? Are unattended backups needed? Availability and characteristics of backup devices User access to backup and restore functions Network infrastructure and speed of the network
Backup Operations Devices Security Performance
8 d #FE1A10 11 v d 4 ' 4 B5 6 0 0 d h o b#I q#Q#T o u ` YR W ` p I

3-3
Time Zones
To install OmniBack II, you will need to dene 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 access OmniBack II (command-line interface and the User Interface).
Once you have planned your cells, you can begin installing the HP OmniBack II on the Cell Server. See HP OpenView OmniBack II Installation Guide for instructions.
3-4
8 d )E17sl0 1l# v d 4 ' 4 B5 6 0 0 d h o EI U#Q#T o u ` YR W ` p I
Calculations of backup start times
Planning Your Backup Strategy

OmniBack II offers great exibility in how you congure and perform your backups. When you plan your backup strategy, you need to make the following decisions: backup type backup mode Filesystem or Rawdisk Full backup or Incremental backup
backup contents Which data to back up backup options Compression, encryption, public/private access to data, report level, le locking, date/time stamps, pre/post execution of commands, and data protection limits backup schedule Specic date/times or time cycle
Each of these is explained in the following sections.
Choosing the Type of Backup

How your data is organized inuences the type of backup you choose. Two types of backup are explained here: Filesystem If you want a complete record of every le and directory that was backed up, a Filesystem backup is best. This type of backup tracks the logical structure of the data on the media. The advantage is easier recovery of data; the disadvantage is that lesystem backups are generally slower than rawdisk backups. This backup type is used for ordinary lesystems such as system and user directories and so forth.
t 45 5 s h G 3Q k1#)D 1A10 11 ( r 6 0 0 d h o b#I q#Q#T o u ` YR W ` p I

3-5
When you congure a lesystem backup, you dene exactly which lesystems are going to be backed up. Host Backup Host backup is essentially the same as lesystem backup, but is dynamic. You specify a host to back up and during backup time OmniBack II checks which lesystems are present on the host and backs them up. This is suitable for hosts with dynamic conguration where disks are often mounted and unmounted. Rawdisk Rawdisk backups are useful for backing up databases located on a disk without a lesystem. This type of backup does not track the logical structure of 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 les are part of the backup when you do a restore. Only the name of the rawdisk device le is recorded in the database. The rawdisk backup backs up a complete disk, including the unused parts, and may therefore take longer than a lesystem backup when a disk is only half full. For limitations, see HP OpenView OmniBack II Software Release Notes.
Choosing the Mode of Backup

How frequently you back up your data affects the security and recoverability of the data. The more frequent the backup, the smaller the potential data loss in the event of a disk failure. There are two types of backup mode: Full and Incremental. Full Backups A full backup includes all the data for the specied objects (directories, lesystems, 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 more media to back up all data.
3-6
t 45 5 s h G v#Q k1#)D 1usl0 1l# v ( r 6 0 0 d h o EI U#Q#T o u ` YR W ` p I
Incremental Backups An incremental backup includes only the data that has been modied since the last full or last incremental backup. Incremental backups are faster and need less media to back up data but make the restore of all data more complicated as you usually need all the media used since the last full backup.
g f @ y e
If a directory is modied, it is backed up during an incremental backup, but previously backed-up les in the directory are not backed up if they have not been modied.
Incremental backups are only valid if the full, protected backup on which they are based exists. See Using Backup Options on page 4-26 for more information. OmniBack II checks if there is a protected full backup before starting an incremental backup. If there is no protected full backup, OmniBack II performs a full backup instead. This can potentially overwrite an unprotected full backup. You can customize this behavior by setting the IncrOnProtected variable in the global options le. See OmniBack II Global Options File on page 7-13 for more information.
g f @ y e
You are advised to use the same backup options with full and incremental backup. Be sure to use one of the options touch and no_touch with both types of backup. If you use the no_touch option with full backup and the touch option with incremental backup, the incremental backup will be the same as a full backup.
Incr Incr (1-9)
Is based on the last backup, either full or incremental. This is the basic incremental backup type. Are based on the previous incremental backup of a lower level. For example, incremental backup level 3 backs up data changed from the last level 2 or lower backup.
Three examples of incremental backups (incremental, single-level, and multiple-level) are described here: Incremental Backups Using incremental backup (Incr) provides an efcient and simple way to congure backups. Each incremental backup is based on the previous backup of any type.

3-7
Single Level Incremental Backups A typical backup strategy involves a combination of full and incremental backups. Each incremental backup is based on the last full backup. For example, a full backup is done once a week during a period of low system usage and incremental backups are done at once each business day in the evening. This type of schedule has the advantage of minimizing the time needed for recovery while at the same time minimizing the effort needed to back up the data on a regular basis. Here is an example of this type of schedule: Friday night Monday night Tuesday night Wednesday night Full Backup includes all data Incr-1 Backup which includes all data modied since the full backup on Friday night Incr-1 Backup which includes all data modied since the full backup on Friday night Incr-1 Backup which includes all data modied since the full backup on Friday night
Thursday night Incr-1 Backup which includes all data modied since the full backup on Friday night In this example, a complete recovery on Wednesday involves restoring the full backup from Friday and the level 1 incremental backup from Tuesday. Everything between the backup of Tuesday night and the time of the system disaster on Wednesday is at risk. Note that each incremental backup makes the previous one obsolete. Multiple Level Incremental Backups Another backup strategy involves the use of multiple-level incremental backups. Here, the incremental backups are based on other incremental backups. By using different incremental levels, you can develop a sophisticated backup strategy. Multiple-level incremental backups have the advantage of reducing the time and the number of media needed to perform the backups even more than the single level incremental backup. The disadvantage is in the increased complexity and length of time needed for data recovery. Here is an example of this type of schedule:
3-8
Friday night Monday night Tuesday night Wednesday night
Full Backup includes all data Incr-1 backup which includes all data modied since the last full backup on Friday night Incr-2 backup which includes all data modied since the Incr-1 backup on Monday night Incr-1 backup which includes all data modied since the full backup on Friday night
Thursday night Incr-2 backup which includes all data modied since the Incr-1 backup on Wednesday night In this example, a complete recovery on Wednesday involves restoring the full backup from Friday, the level 1 incremental backup from Monday, and the level 2 incremental backup from Tuesday. Everything between the backup of Tuesday night and the time of the system disaster on Wednesday is at risk.
Deciding What to Back up

The previous two sections covered choosing a backup type and backup mode. 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 the example of a purchasing department, the vendor information is probably static, while order information is very dynamic. The purchasing department has 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 vendor database remains somewhat static and the order database is updated on an hourly basis. Therefore, the potential data loss is greater for the order database because there are more database updates in the time between the backups. A backup strategy for this scenario might include daily full backups of the order database and daily incremental backups of the vendor database.

3-9
Choosing a Backup Schedule

The previous three sections covered deciding WHAT data to back up and HOW. This section helps you decide WHEN to back it up. For backups to be effective, they must be done on a regular basis. Your data is only as safe as upon backups. The greater the time interval since your last backup, the greater risk to your data. Backup schedules are generally set in one of two ways: by specic date/time or by time cycle. Specic Date/Time The most common form of backup schedule is based on specic dates/times. A backup is performed at the same time and on the same day each week or month. For example, a full backup is done every Friday night at 6:00 and an incremental backup is done every Monday, Tuesday, Wednesday, and Thursday night at 8:00. A schedule like this is easy to plan and remember. OmniBack II can also be congured to check the Unix holiday le to skip backups on holidays. Time Cycle Time cycle backups are done at regular time intervals based on periodic schedules. For example, a full backup is done once every two days at 12:00. Therefore, if the rst backup is Monday at 12:00, subsequent backups will start 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 and for the information about backup stored in the Backup Information Database. This prevents backup data from being overwritten for a specied period. The default value is Permanent. The backup protections are: None Provides no protection. Data will be overwritten if the medium it is stored on is reused.
3-10
Use this option for test backup only. Stored data will be overwritten when the medium is used again since no protection has been chosen.
Until
Data on the medium cannot be overwritten until a specied date. You enter the year, month, and day. Protection for the data will stop at noon of the specied day. Data on the medium cannot be overwritten for the number of days specied. For example, if you set the protection for two days and the current backup starts at 20:00 (8:00 PM) on Wednesday, the data will be protected until Friday at 20:00. Data on the medium cannot be overwritten for the number of weeks specied. For example, if you set the protection for one week and the current backup starts at 10:00 on Wednesday, the data will be protected until 10:00 the following Wednesday. Data is permanently protected from being overwritten. Use the recycle option with media to remove the permanent protection. See Recycling Media/Removing Protection on page 3-32.
Days
Weeks
Permanent
For more information about backup options, see Using Backup Options on page 4-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 from any Cell Server, as long as you have network access. This is particularly useful when you manage more than one cell in your environment, you are running the HP OpenView IT/ Operations, or you have congured an additional Cell Server with a switchover.
t 45 5 s h G 3Q k1#)D 1A10 11 ( r 6 0 0 d h o b#I q#Q#T o u ` YR W ` p I g e y9 @ '

3-11
In smaller environments where you only have one cell, you may want to disable this feature and allow starting backups from the local Cell Server only. The following actions alter the /etc/opt/omni/cell/allow_hosts/ le on all UNIX client hosts and allow_hosts registry entry on all Window NT client hosts.
Limiting Access Once you have congured all the hosts in a cell, you must do the following to limit access to the cell: 1. From the HP OmniBack II Install Window choose Edit Add access limit to cell to open the Cell Administration - Limit Host Access window. The Cell Server eld displays the name of the local Cell Server and cannot be modied. In the OPC host(s) eld, enter hostnames of the HP IT/Operations management system from which you want to access hosts in the OmniBack II cell. In the Alt. cell server(s) eld, enter hostnames of alternate Cell Servers. If you leave this eld empty, only the local Cell Server will have access. 2. Choose OK to limit access to the cell. The Messages field shows the progress. 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 from the HP OpenView OperationsCenter, you must: 1. From the HP OmniBack II Install Window choose Edit Remove access limit from cell to open the Remove access limit window. 2. Choose Remove limit to allow access to the cell from other Cell Servers.
3-12
Using Data Compression

OmniBack II has a compression feature which allows you to reduce the number of media needed for a backup. The standard Unix compression algorithm is used, which provides a compression ratio of approximately 50%. You can substitute a customized compression algorithm by replacing the shared library and integrating this into OmniBack II. Compression can be set for each object or for the whole session. For information on customizing the compression algorithm, see Customizing the Compression Algorithm on page 7-50.
g f @ y e
If you are conguring two logical devices that actually point to one physical device, when one is congured to back up compressed data and the other uncompressed data, you re advised to specify the Lock Name in the advanced options for the two logical devices. Both logical devices must have the same lock name or one logical device must have the name of the other logical device specied as a lock name. A Lock Name is the name which OmniBack II recognizes in order to lock the device before starting backup and restore sessions. Most modern backup devices provide built-in hardware compression that you can congure when adding the device to the host. See your devices manual for instructions. In this case, do NOT use the compress option of OmniBack II, since double compression only decreases performance without giving better compression results.
Using Data Encryption

OmniBack II has a simple encryption feature which provides greater security for the data contained on your backup media. Encryption can be set at the object or session level. You can substitute a customized encryption algorithm by replacing the shared library and integrating this into OmniBack II. For more information on customizing the encryption algorithm, see Customizing the Encryption Algorithm on page 7-45.
t 45 5 s h G 3Q k1#)D 1A10 11 ( r 6 0 0 d h o b#I q#Q#T o u ` YR W ` p I g f @ y e

3-13
Media Management
OmniBack II introduces a complete media management system. It protects your 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 the media. The media management system checks the media management database before writing to a backup medium. This prevents accidental overwrites. The media management system uses a database to record information about the following aspects of a backup or restore:
g f @ y e
The growth and size of the OmniBack II database are determined by the level of detail recorded about each backup and restore session. For more information on maintaining the OmniBack II database, see Managing the Growth of the Database on page 8-4.
The Media Pool Approach

The OmniBack II media management paradigm of handling backup media uses the term media pool to describe a mechanism for managing large numbers of media cartridges.
3-14
50 4 4 0 3#1#l# w 1#4 w 6 i h o EI U#Q#T o u ` YR W ` p I
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
A media pool is an organized collection of media which share common properties. Grouping media into media pools allows OmniBack II to optimize media usage, allocation, and retention policies. Each medium belongs to only one pool at a time. The administrator species a particular allocation and protection policy for media in this pool. OmniBack II also tracks the amount of free space remaining in the pool based on the amount of space specied for each medium when it is added to the pool. OmniBack II sums 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 (Joes DDS media pool)
Pool Attributes
Pool Name A pool name identies a pool. It can consist of up to 32 characters including spaces. We recommend that you assign a name which will help you identify either the logical device or the function of the pool.
Description A description is optional and helps operators identify the pool. The description can contain any characters with a maximum length of 80 characters.
50 4 4 0 3#11 w 14 w 6 i h o b#I q#Q#T o u ` YR W ` p I

3-15
Media Class Media class is the type of media, for example, DDS tapes or optical disks. The Media Class button of the Pool Editor window has a menu of supported media classes. When you select the type of media, OmniBack II calculates available space for that pool based on the media class you have selected. The default value of the available space on a medium is only used in previews. For example, if you specify DDS, a default size of 2.0 GB is assumed when initializing the media. You can overwrite this default with your own value using the Specify option.
Media Allocation Policy The media allocation policy determines the order in which media are accessed within a pool so that media wear out evenly. OmniBack II balances the use of the media in a pool and therefore issues mount prompts based on the status (condition) of the media. Strict directs OmniBack II to require a specic medium. The Medium must be already initialized. This allocation policy is preferrable for use with library devices to prevent accidental overwrite of non-OmniBack II media in the library. directs OmniBack II to accept any suitable medium in the pool (medium must not be in a poor condition or protected). A non-OmniBack II medium is automatically initialized. This policy is preferrable for stacker devices, as they load media in sequential order - a strict policy would require media to be loaded in the same order as they are to be used.
Loose
For libraries containing several media, a strict policy directs OmniBack II to issue mount prompts for the least-used media rst. 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-16
50 4 4 0 3#1#l# w 1#4 w 6 i h o EI U#Q#T o u ` YR W ` p I g f @ y e
often by OmniBack II. To balance the usage, we recommend that you pre-initialize your media before adding them to an existing pool. Initializing a medium also allows you 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 be appended to a medium containing a previous backup. Appendable A backup session writes data to the space remaining on the last medium used in the previous backup session. Subsequent data in the backup set is written to the rst position of the medium. Appending media conserves media space but reduces exibility in manipulating media, because one medium can contain data from several backup sessions. A backup session writes data beginning at the rst position on the rst medium of the backup media set.
NonAppendable Appendable of incrementals only
A backup session appends to a tape only if an incremental backup is performed. This allows having a complete set of full and incremental backupon the same medum if there is enough space.
Media Condition Factors OmniBack II calculates the condition of used media using media condition factors. The condition of the media in a pool determines the condition of the pool. The condition of a pool indicates the reliability of that pool for backups. For example, old or worn media are more likely to have read/write errors. OmniBack II allows you to dene the acceptable thresholds for your media. There are three types of conditions for a medium:
50 4 4 0 3#11 w 14 w 6 i h o b#I q#Q#T o u ` YR W ` p I

3-17
Good Fair Poor
The thresholds used to calculate the status of a medium are described here: Medium valid for The age of a medium is calculated as the number of months that have elapsed since you initialized the medium. For this age to accurately represent the age of your media, we recommend that you use new media when creating a media pool. The default threshold is 36 months. Once a medium is older than 36 months, it is marked as having poor status.
Maximum number of overwrites
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-18
less than 80% of the threshold for age or usage 81 to 100% of the threshold for age or usage exceeds 100% of the threshold for age or usage or if read/write errors have occurred on this medium
The usage of the medium is dened as the number of overwrites to the medium. For OmniBack II to accurately calculate the condition of your media, we recommend using new media when creating a media pool. The default threshold is 250 overwrites. Once a medium has more than 250 overwrites, it is marked as poor.
Since recognition of media types depends on the platform used, we do not recommend that you rely on OmniBack II to recognize other media types. For an upto-date list of detection of media types of various platforms, see HP OpenView OmniBack II Software Release Notes. You may want to set the InitOnLoosePolicy option in the global options le. The medium will not be automatically initialized and data will not be overwritten in case it is not recognized. See OmniBack II Global Options File on page 7-13 for instructions. If you try to read from a medium that was written using hardware compression with a device that does not support compression, OmniBack II will not recognize the DDS and 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 the table below.
Format OmniBack II options irrelevant no-force Overwrite
unknown tar, cpio, OmniStorage, OmniBack I, ANSI label, lesystem tar, cpio, OmniStorage, OmniBack I, ANSI label, lesystem OmniBack II OmniBack II
-force
no-force -force
dependent on the protection set for the backup session
Table 3-1
OmniBack II Overwrite Policy
OmniBack II only writes to media initialized by OmniBack II. You cannot force the overwrite of another backup media format during a backup. This helps avoiding accidental overwrites of other backup media.
50 4 4 0 3#11 w 14 w 6 i h o b#I q#Q#T o u ` YR W ` p I g f @ y e g f @ y e

yes no yes no 3-19
Media Identification
Adding a medium to a media pool consists of initializing the medium. When a medium is initialized, OmniBack II assignes two identiers to the medium: media ID media label A unique ID created by OmniBack II, 32 characters in length. A user-dened label, up to 80 characters in length. If the device supports barcode, the barcode is automatically inserted at the beginning of a media label.
For identication on other systems, an ANSI X3.27 label is also written on the tape. Note that any further modications to the media label are only recorded in the OmniBack II database and not on the medium itself. These labels identify the medium as an OmniBack II medium. When loading a medium for backup or restore, OmniBack II checks the medium for the media ID. When it nds the media ID, it checks the media management system to see what information it has about this medium. This information tells 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, the media management system checks whether the expiration date for the data already contained on this medium has passed. OmniBack II displays the media ID, the media label, and the location when prompting you to mount a medium. OmniBack II knows the media ID of a mounted medium and does not display a mount prompt if the requested medium is already in the device.
3-20
Configuring and Using Logical Devices

OmniBack II introduces the concept of logical devices that represent physical devices with various user dened characteristics such as location or media mount handling. A logical device is associated with a media pool used by OmniBack II to back up and restore data. Since backups and restores are done using logical devices, you must congure your logical devices before you can do a backup or restore. For more information on conguring and using libraries, see Using Complex Devices and Libraries on page 9-1.
The Concept of Logical Devices

A logical device is a group of one or more physical devices of the same type that are treated as one device by OmniBack II. Backups and restores are done using logical devices. For standalone devices, a logical device may consists of linked physical devices that allow you to do unattended backups. When the medium in one physical device is full, the backup automatically continues using the next physical 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 (for example, 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 and Libraries on page 9-1.
8 4 6 2 d 6 ( y 6 # 4 # 11lml0 8 110 6 1C31)' i 0 x0 ( h o b#I q#Q#T o u ` YR W ` p I

3-21
Cleaning Tape Support HP OmniBack II provides automatic cleaning for most backup devices using cleaning tape. For HP SureStore 12000e devices, OmniBack can detect cleaning tape. If the cleaning tape is loaded during backup or restore, OmniBack II recognizes the cleaning tape and logs automatic device cleaning to the log le /var/opt/omni/log/cleaning.log. For SCSI-II libraries it is possible to dene which slots hold cleaning tapes. For devices with barcoded media, OmniBack II recognizes cleaning tape barcodes automatically, if they have the CLN prex. For devices without a cleaning tape, a dirty drive is detected and a cleaning request is displayed on the session monitor window. The device must be cleaned manually. You cannot continue your backup without cleaning the drive, since the backup may fail because data may not be correctly written and stored on the media. OmniBack II detects cleaning tapes in two ways: 1. Hard inventory (during load of cartridge) - only for 48AL 2. Soft inventory (via CLN prex in barcode) - with policies which support barcodes (libraries, Grau ABBA, StorageTek). You can congure a cleaning slot (a slot where OmniBack II can always nd a cleaning tape) only for SCSI II libraries (Grau ABBA and StorageTek ACS have dynamic repository), and only for tape media (not for File and Optical).
g f @ y e
Detection and use of cleaning tapes depends on the platform used. See HP OpenView OmniBack II Software Release Notes for the up-to-date information.
3-22
8 4 2 d 6 ( y 6 # 6 Q4 # 11110 #8 1#10 6 1C31F' i 0 x0 ( h o EI U#Q#T o u ` YR W ` p I
Device Locking While in Use

During backup or restore sessions, OmniBack II locks devices in use in order to prevent use by multiple sessions. Actually, the logical device name is locked. OmniBack II allows you to lock a virtual name and not the real logical device name by specifying this virtual name in the Logical Device Advanced Options, Lock Name option. This feature is useful when you have congured several logical devices for the same physical device, for example, compressed and non-compressed DDS device. To prevent simultaneous usage of the same physical device, you can specify a virtual lockname in both device congurations. This functionality works if devices are specied in different datalists. If more logical devices names of the same physical device are specied in the same datalist, devices are aborted. For example:
DDS_NC is a logical device name for a non-compressed DDS device, DDS_C is a logical device name for a compressed device. In the Lock Name eld of the Logical Device - Advanced Options window for both devices enter DDS_Lock.
Configuring Logical Devices

HP OmniBack II stores information about each logical device in the database. To congure logical devices, follow these steps: 1. In the HP OmniBack II- Main window, select the Devices & Media icon. The HP OmniBack II - Device & Media Management window displays the logical devices and media pools that are currently configured for the cell. 2. In the HP OmniBack II - Device & Media Management window,

3-23
3. In the Logical Device Editor window, select a device type and follow the online help.
Figure 3-1
Configuring a Logical Device
If you are conguring OmniBack II for the rst time, the only media pool shown in the list of media pools is the default pool for this device type (for example "default DDS"). To congure a logical device, you have two choices: You can create an empty pool (a pool without media), and use this pool when configuring the logical device. You can then add media to this pool after you have created the logical device. This is the recommended
3-24
select Edit Create.
method. See The Media Pool Approach on page 3-14 and online help for instructions. You can use the default pool in order to complete the configuration of a logical device. After you have configured the logical device, you can configure an additional pool and assign a device to it. See The Media Pool Approach on page 3-14 and online help for instructions how to create the media pool. Use Edit Modify to assign a device to the pool.
Configuring Typical Devices

This section provides examples about how to congure some typical devices. Be sure to read all relevant sections in order to make full use of this exibility. The following instructions are provided as guidelines only.
Configuring Standalone Devices Standalone devices are, for example, simple one-drive DDS or ExaByte devices. To congure a standalone device, follow these steps: 1. In the HP OmniBack II - Main window, click the Device & Media Management icon to open the HP OmniBack II - Devices & Media Management window. 2. In the HP OmniBack II - Devices & Media Management window, select Edit Create Standalone and follow the online help instructions. If you are conguring OmniBack II for the rst time, the only media pool shown in the list of media pools is the default pool, for example, default ExaByte.

3-25
Configuring SCSI-II Library Devices SCSI-II Library devices are larger libraries, also called autoloaders or jukeboxes. They contain a number of media cartridges and can have multiple drives for backup and restore operations. When conguring a library device, note the following: You must configure a logical device and then add the drives to the library device configuration. For example, drives in a four drive DLT library could be configured as DLT_1, DLT_2, DLT_3 and DLT_4 in a DLT_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 host in a network (multi-host support). You can configure one media pool for all drives or have an independent media pool for each drive.
To congure a SCSI-II Library Device follow these steps: 1. In the HP OmniBack II - Main window, click the Device & Media Management icon to open the HP OmniBack II - Devices & Media Management window. 2. In the HP OmniBack II - Devices & Media Management window, select Edit Create SCSI II-Library and enter the necesarry information. 3. OmniBack II prompts you to configure the drives you want to use in this library. Enter the necessary information for each drive and repeat this step until you have configured all drives.
g f @ y e
Take care when conguring the logical device that you specify the right device le for the right drive index. If you do not, you could set it up so that the library loads media into device 2 and reads from device 1. This is important for a library with two or more drives.
3-26
Media Management Tasks

Media management tasks are accessible using the Edit and View menus in the Device & Media Management window for the pool you select. Most of the media management tasks are also accessible from the Library Management window.
Figure 3-2
The OmniBack II - Device & Media Management Window
8 G 8 @ 50 4 4 0 #z13#l#1 w 14 w 6 i h o b#I q#Q#T o u ` YR W ` p I

3-27
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 media and uses this information to calculate the age and condition of the media. If you add used media to a pool, this information will be incorrect. To create a media pool, follow these steps: 1. In the HP OmniBack II - Main window, click the Device & Media Management icon. 2. In the HP OmniBack II - Device & Media Management window, select Edit Create Media Pool. 3. In the Media Pools - Pool Editor window enter the required information. See online help or Pool Attributes on page 3-15 for more information on specific fields. After you have created a media pool, you can add media to the pool. See the next section for instructions.
Adding Media to a Pool

You must enter a sufcient number of media to a pool to allow unattended backups.
g f @ y e
Once you have initialized a medium, you can only change the Medium Label and Location in the database. To change the label and location on the medium itself, you must reinitialize the medium.
1. In the HP OmniBack II - Main window, click the Devices & Media icon. 2. In the HP OmniBack II - Device & Media Management window, double-click the pool name from the list of media pools. 3. In the Media Management window, choose Edit Init.
3-28
8 G 8 @ 50 4 4 0 ##zl3#1#l# w 1#4 w 6 i h o EI U#Q#T o u ` YR W ` p I
4. In the Media Management - Initialize Medium window, enter the required 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: 1. In the HP OmniBack II - Main window, click the Devices & Media icon. 2. In the HP OmniBack II - Device & Media Management window, double-click a media pool from which you want to verify a medium/media. 3. In the Media Management window, choose a medium/media, select Edit Verify, and follow the online help. OmniBack II displays a message about successful or unsuccessful verication.
Erasing a Medium
The Erase Medium option is only available for magneto-optical platters. The action is used to pre-erase a magneto-optical platter, which signicantly increases the speed of the backup because you need not erase the magnetooptical platters during backup. To pre-erase a medium, follow these steps: 1. In the HP OmniBack II - Main window, click the Devices & Media icon.

3-29
2. In the HP OmniBack II - Device & Media Management window, double-click a pool containing magneto-optical media. 3. In the Media Management window, select a medium/slot, click Edit Erase, and follow the online help instructions.
Modifying a Medium
Modifying a medium lets you change the label or location of the medium in the OmniBack II database. The label is an identier that you have assigned to the medium. Changing the location is useful if you send media to offsite storage. Modifying a medium only changes the information about this medium in the OmniBack II database; the medium itself remains unchanged. To modify a medium, follow these steps: 1. In the HP OmniBack II - Main window, click the Devices & Media icon. 2. In the HP OmniBack II - Device & Media Management window, double-click the pool from which you want to modify a medium. 3. In the Media Management window, choose a medium/slot and select Edit Modify from the menu to open the Pool Editor - Modify Medium window. 4. In the Pool Editor - Modify Medium window enter new information in the Label and Location fields and confirm the modification.
Viewing Information About a Medium

OmniBack II allows you to view information about the usage and condition of a medium. The condition of the medium affects your ability to write to a medium and read the data contained on the medium. This helps you determine when a medium must be replaced.
3-30
To view information about a medium/media, follow these steps: 1. In the HP OmniBack II - Main window, click the Devices & Media icon. 2. In the HP OmniBack II - Device & Media Management window, double-click the pool from which you want to view information about a medium/media. 3. In the Media Management window, choose a medium and select Edit Info to open the Media Management - Medium Info window.
Moving a Medium
OmniBack II lets you move a medium from one pool to another pool. This is useful if you want to use the medium on another device. Note that the new pool must use the same type of media, for example, DDS tapes. 1. In the HP OmniBack II - Main window, click the Devices & Media icon. 2. In the HP OmniBack II - Device & Media Management window, double-click the pool from which you want to move a medium. 3. In the Media Management window, choose a medium/media you want to move and select Edit Move to open the Media Management Move Media window. 4. In the Media Management - Move Media window, select the media pool to which you want to move a medium/media. The name of the selected media pool appears in the Selection field. 5. Click the OK button to confirm the move and return to the Media Management window. Note that the medium that was moved no longer appears in the list of media for this pool.

3-31
Recycling Media/Removing Protection

OmniBack II keeps track of data on every used medium. When conguring backup, you can protect your data from being overwritten by newer backups for a specic time. Recycling removes the data protection from backed-up data, thus allowing OmniBack II to overwrite it during the next backup. The data on the media remains unchanged until the next backup. To recycle a medium, follow these steps: 1. In the HP OmniBack II - Main window, click the Devices & Media icon. 2. In the HP OmniBack II - Device & Media Management window, double-click the pool in which you want to recycle a medium/media. 3. In the Media Management window, select a medium/media. 4. Select Edit Recycle and confirm your decision.
Exporting a Medium
Exporting a medium removes the information about a medium and its contents from the database. OmniBack II no longer knows that this medium exists. The medium and the data it contains remain unchanged. You need to export media when you want to move it to another cell. You must export media in one cell and import them in another cell. Media that hold protected data cannot be exported. You must recycle the media rst.
g f @ y e
If you plan to export media, you must export all the media of a backup session. If a backup session spans several media and you only export one medium of the set, there will be inconsistencies in the OmniBack II database. These inconsistencies will cause problems when you try to restore data from this backup session. These problems
3-32
occur because the backup session is in the database, but the data you want to restore is on media that is no longer available. This generates an error message that the session is not complete.
To export a medium follow these steps: 1. In the HP OmniBack II - Main window, click the Devices & Media icon. 2. In the HP OmniBack II - Device & Media Management window, double-click the pool in which you want to select a medium to export. 3. In the Media Management window, choose the medium you want to export. 4. Choose Edit Export and confirm your action. The medium that you have exported no longer appears in the list of media for this pool.
Importing a Medium
The import of media rereads all data about the backup sessions on the media to the OmniBack II database. If a session spans more than one medium, all media for this session must be imported 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 at restore time. If you select to restore from a partially imported session, you will 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 to another. First you must export media in one cell and then import them in another cell. Note that during import OmniBack II reconstructs the detail catalog of a session. It reads the label, location, and protection information from the medium to the database. Any changes made to this information between the

3-33
initialization and the export will be lost as modications are only made to the database and not to the media. The original initialization information will be imported. Similarly, additional attributes such as object or media size will not be reconstructed during the import. To import a medium, follow these steps: 1. In the HP OmniBack II - Main window, click the Devices & Media icon. 2. In the HP OmniBack II - Device & Media Management window, double-click the media pool to which you want to import a medium. The Media Management window is displayed. 3. From the Media Management window, choose Edit Import to open the Media Management - Import window and follow the online help instructions. 4. During the import process, messages appear in the Messages field. When the import is nished, you return to the Media Management window. The imported medium now appears in the list of media for this pool.
Scanning Media
Scanning media checks the format of media inserted in a logical device and displays information on slots or libraries. To scan media, follow these steps: 1. In the HP OmniBack II - Main window, click the Devices & Media icon. 2. In the HP OmniBack II - Device & Media Management window, double-click a media pool from the list to open the Media Management window. 3. In the Media Management window, choose Edit Scan... and follow the online help instructions.
3-34
When the scanning is nished, the messages about the scanned media are displayed in the Messages field of the Media Management window. To scan a library using barcodes, the Barcode Reader Support device option must be enabled in the device conguration. Use Edit Barcode rescan to scan a library with barcodes.
Modifying Device and Media Management View

You can customize the media view in the Device & Media Mangement window by changing the variables in the global options le. 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 be displayed in the libray or media management view by specifying the corresponding token strings.

3-35
Configuring User Classes and Users

How you congure your user classes and users has a major effect on the security of a cell. Access to backup and restore functions gives a user access to the data stored in that cell. Backing up data and restoring it to a different disk 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 different host. Therefore, it is recommended that you carefully plan what backup and restore 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 access permissions of this user class. A user class is a group of users with specic permissions to perform backup and restore tasks.
3-36
8 8 1#b## )' 8 10 6 1C31F' 4 i 0 8 4 8 8 d 4 x0 ( h o EI U#Q#T o u ` YR W ` p I
The following default classes are provided:

User Class admin Access Rights allowed to congure OmniBack II and do backup, restore, and all other available operations. After installation, only the root user on the Cell Server is congured as the administrator. allowed to do all operations except congure OmniBack II
senioroperator operator end-user
allowed to start backups and respond to mount requests allowed to do restore of their own objects. In addition, users can monitor and respond to mount requests for their own restore sessions. Table 3-2 OmniBack II Default User Classes and their Access Rights
After the initial installation, all default user classes are empty except for the admin class. The Unix root user on the Cell Server is automatically congured as the OmniBack II administrator. All other categories can remain empty if you want to restrict access to OmniBack II. You can add as many additional user classes as you need for your environment. Users are dened by their Unix login name and group. Wildcards (*) may be used for hostname, user name, and the group ID. There is no pattern matching; only the asteriks (*) is a valid wildcard.
g f @ y e
Admin capabilities are very powerful and they basically mean that the administrator has root capabilities on the whole cell. Normally, only the root user on a Cell Server should have Admin capabilities.
You can use HP OmniBack II without modifying the default user conguration. However, for security reasons it is recommended that you verify (and if necessary modify) the default user conguration.
8 #8 l#b## )' 8 10 6 1C31)' 4 i 0 8 4 8 8 d 4 x0 ( h o b#I q#Q#T o u ` YR W ` p I

3-37
Configuring User Classes

OmniBack II user classes are congured using the User Administration - Add Class window. To access this window, follow these steps: 1. In the OmniBack II Main menu, click Users to open the HP OmniBack II - Users Administration window. 2. Select Edit Add Class from the menu bar. The User 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 the Class Name field. The user class name must be alphanumeric and can have a maximum of 16 characters without spaces. 2. Enter a description in the Description field. The description field can contain any characters, is a maximum of 64 characters long, and spaces are 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. See below for a description of the access rights. 4. Click OK to confirm the configuration. Repeat these steps to add additional user classes. For specic information on adding, 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 the user to monitor and abort his/her own session.
3-38
Start datalist backup
allows a user to perform a backup using a datalist. This access right allows the user to start a backup using any datalist and therefore back up the data objects listed in any datalist. allows users to create, schedule, modify, and save their own datalists.
Save datalist
Backup as root allows user to back up any object using the root (superuser) login.
g f @ y e
Note that this is a powerful access right that can affect the security of your system!
Mount prompt Start restore
allows a user to respond to mount prompts for any active session in the cell. allows user to restore only his/her own objects (objects for which he/she is the Unix owner). This access right automatically also allows users to monitor and abort their own session.
Restore to other hosts allows a user to restore objects to a host other than the host where the object was backed up. The user must have login permission on the destination host. Note that this is a powerful access right. Restore from other users allows the user to restore les belonging to another user. Note that this is a powerful access right.
Restore as root allows user to restore objects using root capabilities.

g f @ y e
Note that this is a powerful access right that can affect the security of your system!
Monitor Abort
allows a user to view session information for all sessions in the cell. allows a user to abort any active session in the cell. Note that this is a powerful access right.

3-39
User conguration Device conguration
Media conguration Switch session ownership
MS Exchange
MS SQL
The Edit Class Modify menu selection can be used to both view and modify the access rights of a user class. You cannot modify the Admin class.
3-40
allows a user to add, delete, and modify user classes and users. Note that this is a powerful access right. allows a user to create, delete, modify, and rename logical devices. This includes the ability to add a mount prompt script to a logical device. Note that this is a powerful access right. allows a user to manage media pools and the media in the pools. Note that this is a powerful access right. (Note that this access right is only appropriate if the "Start Datalist Backup" access right is also enabled. The access right "Switch Session Ownership" allows a user to start a backup using a datalist without becoming the owner of the backup session, if an owner has been set for the datalist. You set the owner of a datalist using the File Change Ownership selection in the OmniBack II Backup window. If this access right is OFF, the user who starts the backup becomes the owner of the backup session. allows OmniBack II to run a backup of a Microsoft Exchange server. For instructions how to congure this backup, see HP OpenView OmniBack II Integrations Guide. allows OmniBack II to run backups of a Microsoft SQL database running on PC-based Windows NT systems. For instructions how to congure this backup, see HP OpenView OmniBack II Integrations Guide.
g f @ y e
Configuring Users
Each OmniBack II user is a member of a user class and has the access permissions of this user class. OmniBack II users are congured using the User Administration Add User window. To access this window, follow these steps: 1. In the OmniBack II main menu, click Users to open the HP OmniBack II - Users Administration window. 2. Click the User Class in the User Class list to select the User Class for this user. 3. Select Edit Add User from the menu bar to open the User Administration - Add User window. To add a user, follow these steps: 1. Enter the Unix login (user name) in the Unix Login field. By clicking the ... button you will get a list of users configured in the local /etc/passwd file. 2. Enter the Unix group name in the Unix Group field. 3. Enter the real name (actual name) of the user in the Real Name field. 4. Enter the host name of the user in the Host Name field. 5. Confirm the user class name in the Class field. If you want to use an alternative User Class, click the field to activate it, and enter the alternative User Class name. Note that you can only enter the name of an existing User Class. 6. Click the Add button to confirm the new user. Repeat these steps to add additional users.

3-41
3-42
Backing Up Your System
4-1
In This Chapter This chapter explains the procedures, commands, and options for tasks done during 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 congure a cell with at least one host and a logical device. If the logical device is resident on a separate host, congure that host in the cell as well. See Chapter 3, Conguring a Cell, on page 3-1 for more information. To run a backup you must specify objects you want to back up. This is done using a datalist. A datalist is a list of objects (lesystems or rawdisks) to be backed up. To have the datalist backed up periodically, set up a backup schedule using the Scheduler. Non-routine backups are generally run interactively. The following sections provide you an overview of scheduled and interactive backups.
4-2
r hP ~ } R W T | f { ` Y w X u k1#F)b#I vt
Understanding Datalists and Barlists
What is a Datalist?
A datalist allows you to group and save backup objects. This is especially convenient when these objects are backed up on a regular basis. Instead of dening the objects every time you run a backup, use the settings saved in the datalist. Datalists are ASCII les located in the /etc/opt/omni/datalists directory on the Cell Server. For more details on the syntax of a datalist, see the manpage for omnidatalist. Although it is possible to congure datalists directly with a text editor, we recommend that you use the GUI due to the complexity of the datalist syntax. OmniBack II provides a GUI datalist editor which has been designed to guide you through the process of conguring a datalist. Once your datalist is set up, you only need to change it if your system conguration changes or if you want to change backup options. OmniBack II automatically supplies default values for any options you omit from the datalist. 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 simpler for your case.
85 D i 0 85 d 5 78 6 d )1E78 6 10 l1#78 110 6 i 0 5 4 i r hP ~ } R W T | f { ` Y w X u k1#F)b#I vt

4-3
Generate Datalist
Create Datalist You create the whole datalist from scratch, specifying all backup objects and options.
What is a Barlist?
Similar to a datalist, a barlist allows you to group and save objects for backup of databases. Instead of dening the objects every time you run a backup, use the settings saved in the barlist. Barlists are ASCII les located in the /etc/opt/omni/barlists directory on the Cell Server. For more details on the syntax of a barlist, see the manpage for omnibarlist. Although it is possible to congure barlists directly with a text editor, we recommend that you use the GUI due to the complexity of the barlist syntax. OmniBack II provides a GUI barlist editor which has been designed to guide you through the process of conguring a barlist. Once your barlist is set up, you only need to change it if your system conguration changes or if you want to change backup options. OmniBack II automatically supplies default values for any options you omit from the barlist. For more information on OmniBack II integrations with popular databases, such as Oracle, Informix, Sybase. SAP R/3 and similar, see HP OpenView OmniBack II Integrations Guide.
4-4
85 D i 0 85 d 5 Q8 6 d )1EQ8 6 #Q 10 11Q8 110 6 i 0 5 4 i r hP ~ } R W T | f { ` Y w X u k1#F)b#I vt
This option automatically congures datalists for a complete backup of all lesystems on the local host, selected hosts, or all hosts in the cell. You can later modify the datalists to suit your specic requirements.
Generating Datalists
This option automatically congures datalists for a complete backup of all lesystems on the local host, selected hosts, or all hosts in the cell of the OmniBack II database. You can later modify the datalists to suit your specic requirements. 1. Choose the Backup icon from the main HP OmniBack II window to open the HP OmniBack II - Backup window. 2. Select ActionsGenerate Datalists and choose a host on which the datalist will be generated. The HP OmniBack II - Generate Datalist window is displayed. 3. In the HP OmniBack II - Generate Datalist window, decide whether you want to generate the datalist for a local host only, selected hosts, or all hosts in the cell. You need to select the Host backup or Filesystem backup option for the selected hosts and enter the name of the datalist. Your datalist will be added to the OmniBack II Backup window. 4. If you need to modify this datalist see the online help or Modifying a Datalist on page 4-7 for instructions.

4-5
Figure 4-1
Generating a Datalist
Creating Datalists
You create the datalist from scratch, specifying all options, or create lists for different databases (see HP OpenView OmniBack II Integrations Guide for more information). To create a datalist do the following: 1. Choose the Backup icon from the main HP OmniBack II window to open the HP OmniBack II - Backup window.
4-6
85 D i 0 85 d 5 Q8 6 d )1EQ8 6 #Q 10 11Q8 110 6 i 0 5 4 i r hP ~ } R W T | f { ` Y w X u k1#F)b#I vt
2. Select EditCreateOmniBack II Datalist to open the OmniBack II Backup Editor window. 3. Select ObjectAdd and choose from the menu the type of datalist you want to create and follow the online help. For detailed explanations on these parameters and their options, see the online help and Using Backup Options on page 4-26.
Modifying a Datalist
g f @ y e
If a cell is changed, for example, a host is removed, you need to load and modify the datalist that includes this host. Otherwise, OmniBack II will generate a warning message.
1. Choose the Backup icon from the main HP OmniBack II window to open the HP OmniBack II - Backup window. 2. Highlight the datalist you want to modify. 3. Select EditModify List to open the OmniBack II Backup Editor window and follow the online help instructions. You can add, remove, or modify objects specied in the datalist, and add backup options to each object or to the datalist. See Using Backup Options on page 4-26 for more information.
g f @ y e
If you modify an object description in the datalist, the next backup for that object will be full regardless of your backup mode selection.

4-7
Configuring a Filesystem Backup

A lesystem is an organization of les on a mass memory device. A lesystem is backed up so that the lename, le attributes, and the le contents are stored on backup media. The set of les backed up from a lesystem in a specic session is called a "leset." The leset backed up from one lesystem changes from backup session to backup session depending on user activity on this lesystem (creation of new les, deletion of old les, etc.) and whether a full or incremental backup has been run for the session. OmniBack II keeps track of all backed-up lesystems and knows when and to which media each lesystem has been backed up. OmniBack II uses this information when you request a le or lesystem to be restored. A disk containing a lesystem is identied by its hostname and mountpoint. To get information about HOST backup see Conguring Host Backup on page 4-17. The procedure for running a scheduled lesystem backup involves four main tasks: 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 the Backup icon from the main HP OmniBack II window. The HP OmniBack II - Backup window appears. 2. Select Edit Create OB II Datalist from the menu bar. The OmniBack II Backup Editor appears.
4-8
h G D 458 t8 6 x0 ( 1#)n#7Q#4 d 1E10 6 1C31F' r hP ~ } R W T | f { ` Y w X u k1#F)b#I vt
3. Select ObjectAddFilesystem to open the OmniBack II Filesystem Backup window.
Figure 4-2
Configuring a Filesystem Backup
4. Enter the hostname in the Hostname field or click the ... button to see a list of hosts. 5. Enter the mountpoint (which is the root directory of your mounted filesystem) in the Mount Point field or press the ... button to choose the mountpoint from a list. 6. Enter a description of this filesystem backup in the Description field. It is useful to enter the mountpoint when you back up more than one disk on the same host. This will result in locating files more easily.
h G D 458 t8 6 x0 ( 1#)n#Q4 d lE10 6 1C31)' r hP ~ } R W T | f { ` Y w X u k1#F)b#I vt

4-9
7. Choose Exclude to exclude specific files and directories from the backup. For example, you may want to exclude the /tmp directory. Note that you must enter the full pathname of files. If you do not exclude a particular le or directory, the complete lesystem is congured for backup.
g f @ y e
Use the Exclude option to exclude the conguration 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 be incomplete and you will not be able to restore the database from this backup. We also recommend excluding NFS mounted lesystems to avoid error reports.
8. Click the Options button if you want to activate one of the following options:
Only
9. Click OK to go back to the OmniBack II Filesystem Backup windows. 10. To select additional filesets to back up, enter the full path name and file/directory in the field to the left of the Add button, and click Add. To remove a le from the Files and Directories eld, select the le or directory and click Delete. 11. Enter the name of the logical device to which the fileset will be backed up in the Backup Device field, or click the ... button to select it from a list. After you have congured one lesystem, you may set up the backup options or use the default backup options provided.
4-10
h G D 458 t8 6 x0 ( 1#)n#7Q#4 d 1E10 6 1C31F' r hP ~ } R W T | f { ` Y w X u k1#F)b#I vt g f @ y e
Enter the names of les to be backed up. You can use wildcards when selecting the lename. For example, you may want to back up only *.doc les. Excludes les matching the entered le name criterion. You can use wildcards to the le name. For example, you may want to skip all *.o les in the selected leset.
Skip
Selecting the Filesystem Backup Options

1. In the HP OmniBack II - Main window, select a Cell Server and click the Backup icon. The HP OmniBack II Backup window opens. 2. Select EditCreateOB II Datalist from the menu bar. The OmniBack II Backup Editor appears. 3. Click Object Add Filesystem.
Figure 4-3
Selecting Filesystem Backup Options
4. In the OmniBack II Filesystem Backup window, click the Filesystem Backup Options button to display and set the backup options for this object. These options override the session default options of the
4-11
h G D 458 t8 6 x0 ( 1#)n#Q4 d lE10 6 1C31)' r hP ~ } R W T | f { ` Y w X u k1#F)b#I vt
5. Click on the OK button to set options and return to the Filesystem Backup window. 6. Click on the OK button in theFilesystem Backup window to close this window and return to the OmniBack II Editor window. 7. You can now set the options for the device where the backup will be performed. Select the device in the Devices field in the OmniBack II Backup Editor window and select OptionsFor Selected Device to open the Devices Options window. See Device Options on page 4-33 for more information. 8. Click on the OK button to set options. Now you can save the datalist and run the backup interactively or schedule the datalist. See Starting a Backup of an Existing Datalist on page 4-20 or Setting Up Scheduled Backups on page 4-41 for more information.
4-12
h G D 458 t8 6 x0 ( 1#)n#7Q#4 d 1E10 6 1C31F' r hP ~ } R W T | f { ` Y w X u k1#F)b#I vt
datalist. See Using Backup Options on page 4-26 for more details. Choose Default to set options back to default settings.
Configuring a Rawdisk Backup

A rawdisk backup is a high-speed backup where the system does not track the logical structure of the information stored on the disk. The hostname you enter provides the location of the sections. OmniBack II accesses the sections using the character device lename /dev/rdsk/filename that you congure. Scenarios in which a rawdisk backup is appropriate include:
g f @ y e
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-disk connection is not possible (the two disks must be identical). Backup of a disk that contains databases.
We recommend that you unmount a rawdisk before a rawdisk backup and mount it back later. You can use Pre- and Post- exec commands to do this.
Although a rawdisk backup does not distinguish between lesystem disks and database sections, OmniBack II still allows you to restore individual les from a rawdisk backup if the rawdisk holds an HP-UX HFS lesystem. OmniBack II backs up rawdisk sections locally in the order you have specied them in the Rawdisk Sections list. OmniBack II also allows a network-wide rawdisk backup. However, for maximum performance rawdisk backup is best run locally. The procedure for running a scheduled rawdisk backup involves the same four main tasks you perform for a scheduled lesystem backup: 1. Creating a datalist. 2. Selecting the rawdisk to be backed up. 3. Selecting backup options. 4. Setting up the backup schedule.
h G D G 6 i x0 ( 1#)E8 1m)b10 6 1C31)' r hP ~ } R W T | f { ` Y w X u k1#F)b#I vt

4-13
5. Previewing the backup.
Selecting Rawdisk Sections for Backup

1. Choose the Backup icon from the main HP OmniBack II window. The HP OmniBack II - Backup window appears. 2. Select EditCreateOmniBack II Datalist to open the OmniBack II Backup Editor window. 3. Select ObjectAddRawdisk to open the OmniBack II Rawdisk Backup window.
Figure 4-4
Configuring a Rawdisk Backup
4. In the Hostname field, enter the hostname where the rawdisk is located
4-14
h G D G 6 i x0 ( 1#)b#8 1mQ)E10 6 1C31F' r hP ~ } R W T | f { ` Y w X u k1#F)b#I vt
or click the ... button to see a list of hosts. 5. In the Description field, enter descriptive text for this backup object. Enter up to 80 characters including spaces. Note that you cannot leave this field blank. 6. In the field beside the Add button, enter the disk sections that you want backed up. Enter the section character device name. On HP-UX systems, all character device files are listed in the /dev/rdsk directory.
g f @ y e
7. Click on Add to add the section to the Rawdisk Sections list. To delete a section from the list, highlight a section in the Rawdisk Sections list and click Delete. 8. Enter the name of the logical device to which the rawdisk will be backed up in the Backup Device field, or click the ... button to select from a list.
Selecting the Rawdisk Backup Options

1. Choose the Backup icon from the main HP OmniBack II window. The HP OmniBack II - Backup window appears. 2. Select EditCreateOmniBack II Datalist to open the OmniBack II Backup Editor window. 3. Select ObjectAddRawdisk to open the OmniBack II Rawdisk Backup window. 4. Click on the Rawdisk Backup Options button to display and set the backup options for this object. See Using Backup Options on page 4-26 for more information. Choose Default to reset the options back to the default values. 5. Click on the OK button to set options and return to the Backup Editor window. 6. Next, set the options for the device where the backup will be performed.
h G D G 6 i x0 ( 1#)E8 1m)b10 6 1C31)' r hP ~ } R W T | f { ` Y w X u k1#F)b#I vt

4-15
7. Click on the OK button to set the device options and return to the OmniBack II Backup Editor window. Now you can save the datalist and run the backup interactively or schedule the datalist. See Starting a Backup of an Existing Datalist on page 4-20 or Setting Up Scheduled Backups on page 4-41 for more information.
4-16
h G D G 6 i x0 ( 1#)b#8 1mQ)E10 6 1C31F' r hP ~ } R W T | f { ` Y w X u k1#F)b#I vt
Select the device in the Devices field in the Backup Editor window. Choose OptionsFor Selected Device to open the Devices Options window. See Device Options on page 4-33 for more information.
Configuring Host Backup

Host backup is the dynamic backup of all lesystems congured on a host, as opposed to lesystem backup that includes only the static backup of selected lesystems. See Conguring a Filesystem Backup for more information. This feature simplies datalist conguration and improves backup coverage of hosts that often mount/dismount various disks. Host backup is very useful for dynamic environments with a large number of disks to be backed up.
g f @ y e
The -tree option for a HOST object has inuence only on its mount point, whereas all other lesystems will be fully backed up. Similar functionality for rawdisk backup is not supported.
Occasionally check which disks are congured on a host and decide if you really want to back up all disks congured. If you want to back up a small number of selected lesystems, you are recommended to use the lesystem backup. For example, you add an additional mouintpoint /x to a host that already has mountponts /var, /home, and /tmp congured. If you run a Host Backup, the additional mountpoint /x will automatically be added to the datalist at runtime. The procedure for running a scheduled host backup involves four main tasks: 1. Creating a datalist. 2. Selecting the host to be backed up. 3. Selecting the backup options. 4. Setting up the backup schedule. 5. Previewing the backup.
h G D 58 ( x0 ( 1#)CQ1)10 6 1C31)' r hP ~ } R W T | f { ` Y w X u k1#F)b#I vt g f @ y e

4-17
Selecting a Host to Back up

1. Choose the Backup icon from the main HP OmniBack II window. The HP OmniBack II - Backup window appears. 2. Select EditCreate OB II Datalist from the menu bar. The OmniBack II Backup Editor appears. 3. Select ObjectAddHost to open the OmniBack II Host Backup window.
Figure 4-5
Configuring Host Backup
4. Enter the hostname in the Hostname field or click the ... button to see a list of hosts. 5. Enter a description of this host in the Description field.
4-18
h G D 58 ( x0 ( 1#)CQ1)10 6 1C31F' r hP ~ } R W T | f { ` Y w X u k1#F)b#I vt
6. Click the Browse button to view and select mountpoints, directories, and filesystems for backup. 7. Choose Exclude to exclude specific files and directories from the backup. Note that you must enter the full pathname of files. For example, you may want to exclude the /tmp directory.
g f @ y e
Use the Exclude option to exclude the conguration and database directories /var/opt/omni/db and /etc/opt/omni from your host backups. Because the database is in use during the backup, a backup of the database will be incomplete and you will not be able to restore the database from this backup. We also recommend excluding mounted NFS (Network lesystems) to avoid error reports.
8. Click the Options button if you want to activate one of the following options:
Only
Enter the names of les to be backed up. You can use wildcards when selecting the lename. For example, you may want to back up only *.doc les. In this case, *.doc les from all lesystems congured on the host will be backed up. Enter the names of les to be excluded from backup. You can use wildcards to the le name. For example, you may want to skip all *.o les. In this case, the *.o les from all lesystems congured on the host will be skipped from backup.
Skip
9. To select additional filesets to back up, enter the full path name and file/directory in the field to the left of the Add button, and click Add. 10. To remove a file from the Files and Directories field, select the file or directory, and click Delete. 11. Enter the name of the backup device that will be used to back up the host or click the ... button to see a list of devices. 12. Click the Host Backup Options button if you want to select backup options for the host. 13. Click OK to go back to the OmniBack II Backup Editor window. 14. To add additional hosts to the datalist, repeat the steps 3-11.
h G D 58 ( x0 ( 1#)CQ1)10 6 1C31)' r hP ~ } R W T | f { ` Y w X u k1#F)b#I vt

4-19
Running Interactive Backups

Running an interactive backup means that the backup is performed immediately and interactively. You can run an interactive backup of an existing datalist. See Previewing Your Backup on page 4-24 and "Starting an Interractive Backup of an Existing Datalist" below for instructions. You can create a temporary datalist for one backup only and run the backup of this datalist. See Creating a Temporary Datalist on page 4-23 for instructions.
Starting a Backup of an Existing Datalist

If you want to run an interactive backup of an existing datalist, use the following procedure: 1. Choose the Backup icon from the main HP OmniBack II window. The HP OmniBack II - Backup window appears. 2. In the HP OmniBack II - Backup window, highlight the datalist you want to back up. 3. Choose ActionsBackup Selected... to open the OmniBack II Backup Editor window. 4. Choose ActionsStart Backup.
4-20
8 h G D 65 45 6 0 0 11#)b4 2 Q v0 9 10 111F r hP ~ } R W T | f { ` Y w X u k1#F)b#I vt
Figure 4-6
Running a Backup Session
The message field displays progress messages. The maximum buffer for messages in the Messages eld is limited by the congurable parameter MAXGUIMSG. See OmniBack II Global Options File on page 7-13for more information. If the maximum buffer is exceeded, messages stop appearing in the Message eld and the error message Output disabled appears; however, the backup continues.
g 9 @
By pressing the right mouse button in the message area, you get a pop-up menu where you can print, search for specic messages, clear up the message area and so forth.
8 h G D 65 45 6 0 0 11#)b4 2 7 730 9 10 111F r hP ~ } R W T | f { ` Y w X u k1#F)b#I vt

4-21
Status Messages
The messages elds use colors and status descriptions to help you identify the 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 feld shows how each object in the datalist has been backed up.
Completed
Completed/Errors Some les were not backed up successfully. The eld is
Aborted
Failed
Status of Devices Inactive/waiting. Running. Aborted. Completed.
4-22
All les have been backed up successfully without errors, there may be some warning messages. The eld is green. yellow. The Disk Agent has been aborted for the following reasons: The user has aborted backup. The backup of all files has failed. The Pre- or Post- exec script has failed. Usually les have not been backed up successfully. The eld is red. OmniBack II could not run backup. There may be something wrong with the conguration. No backup exists. The eld is red.
Creating a Temporary Datalist

1. In the HP OmniBack II - Main window, choose the Backup icon. The HP OmniBack II - Backup window appears. 2. From the HP OmniBack II - Backup window, select the datalist you want to back up. 3. Click ActionInteractive Backup to open the OmniBack II Backup Editor window. 4. Use ObjectAdd and select an object you want to add. Enter the required information in the window. Use the ... button to get a list of possible options where available.
g f @ y e
Use the Exclude option to exclude the conguration 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 be incomplete and you will not be able to restore the database from this backup.We also recommend excluding the NFS mounted lesystem to avoid error reports.
For an explanation of backup options available for a specic object, see the online help or Using Backup Options on page 4-27. Repeat this procedure for as many objects as needed. You can modify backup options for each specic object later if desired. If you plan to use this datalist again, use the FileSave to save it.
8 h G D 65 45 6 0 0 11#)b4 2 7 730 9 10 111F r hP ~ } R W T | f { ` Y w X u k1#F)b#I vt

4-23
Previewing Your Backup

You can preview a selected backup session to see if you have properly congured options and if the correct les are being backed up and to get an estimate of how much space will be used for data.
g f @ y e
The Pre- and Post- exec commands set for an object are executed during the preview of a backup. If these commands affect your operations, you may want to preview your backup rst and then add the Pre- and Post- exec commands.
1. Choose Backup from the main HP OmniBack II window. The HP OmniBack II - Backup window appears. 2. In the HP OmniBack II - Backup window, select the desired datalist for the backup you want to preview. 3. In the OmniBack II Backup Editor select ActionsPreview Backup. 4. Choose whether you want to preview a full or incremental backup of selected objects. If this is the first time objects are backed up, the preview will show a full backup.
Starting Your Backup

1. Choose Backup from the main HP OmniBack II window. The HP OmniBack II - Backup window appears. 2. In the HP OmniBack II - Backup window, select the datalist you want to back up. 3. In the OmniBack II Backup Editor, choose ActionsStart Backup. 4. In the Run Omniback II Backup window, choose whether you want to run a full or incremental backup. If selected objects are backed up for the first time, a full backup will be run automatically.
4-24
You are advised to use the same backup optinions with full and incremental backups. At least use the option touch or no_touch with both types of backup. If you use the no_touch option with full backup and the touch option with incremental backup, the incremental backup will be the same as full backup.
The message elds display progress messages. The maximum buffer for messages in the Messages eld is limited with the congurable parameter MAXGUIMSG. If the maximum buffer is exceeded, messages stop appearing in the Messages eld and the error message Output disabled appears. See OmniBack II Global Options File on page 7-13rffor instructions how to change this value.
g 9 @
By pressing the right mouse button in the message area, you get a pop-up menu where you can print, search for specic messages, clear up the messages eld, and so forth.
The Messages eld provides colors and status descriptions to help you identity the progress and status of the session. See the online help or Status Messages on page 4-22 for a description.
8 h G D 65 45 6 0 0 11#)b4 2 7 730 9 10 111F r hP ~ } R W T | f { ` Y w X u k1#F)b#I vt g f @ y e

4-25
Using Backup Options

HP OmniBack II offers a set of comprehensive backup options allowing ne tuning of a backup. All options have default values which are appropriate for most cases.
Figure 4-7
Selecting Backup Options
4-26
8 0 65h y h G D 6 11( 3s1#)10 #8 r hP ~ } R W T | f { ` Y w X u k1#F)b#I vt
For a Datalist Pre- exec commands Post- exec commands load balancing reconnect broken connections protection These options are datalist specic and override session default options. To set these options for a specic datalist, select the datalist and choose Options For Selected Datalist from the OmniBack II Backup Editor window.
Session Defaults for Filesystem Objects compress encrypt private/public report level (warning, minor, major, critical) display statistical information lock files during backup do not preserve time attributes ignore hard links pre- exec command post- exec command protection log files/directories to database backup les of size Default backup options for lesystem objects in a datalist. These options are applied each time a lesystem is being backed up. You could, for example, set the Compress option for all lesystem objects in the datalist. To set these options select Options Session Defaults For Filesystem Objects from the OmniBack II Backup Editor window.
8 0 65h y h G D 6 11( 73g1#)10 8 r hP ~ } R W T | f { ` Y w X u k1#F)b#I vt

4-27
Session Defaults for Rawdisk Objects compress encrypt private/public report level (warning, minor, major, critical) pre- exec command post- exec command protection Default backup options for rawdisk objects in a datalist. These options are applied each time a rawdisk is backed up. You could, for example, set the Compress option for all rawdisk objects in the datalist. To set these options select Options Session Defaults For Rawdisk Objects from the OmniBack II Backup Editor window.
For Selected Objects Backup options for each specific object in a datalist. These options override the session default options and are applied each time a specific object is backed up. You could, for example, specify that one object in a datalist does not use the Compress option because the system is too slow and the object contains only a small amount of data. To set these options select the object in the OmniBack II Backup editor window and choose Options For Selected Object. For Selected Device CRC Check Concurrency Media Pool Prealloc List To set these options, select the device in the OmniBack II Backup editor window and choose Options For Selected Device.
4-28
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 and improves backup performance. By default, the compression option is set to OFF. When software compression is turned on, OmniBack II compresses the data on the host where the Disk Agent is running before it sends it over the network. This reduces data trafc over the network. Depending on the type of data, compression ranges from 30% to 70% and is based on the LempelZiv 4.3 compression algorithm which is completely compatible with the standard Unix compress utility. OmniBack II provides you with the API (Application Programming Interface) which is used by the Disk Agent to interface with the compression module. This allows you to substitute your own special-purpose compression module for even higher rates of compression. OmniBack II also supports devices which allow for hardware data compression.
g f @ y e
In case of conguring two logical devices that actually point to one physical device, one congured to back up compressed data and the other uncompressed data, you are advised to specify the Lock Name in the advanced options for the two logical devices. Both logical devices must have the same lock name. Lock Name is the name which OmniBack II recognizes in order to lock the device before starting backup and restore sessions. Most modern backup devices provide built-in hardware compression that you can congure when adding a device to the host. See your devices manual for instructions. In this case, do not use the compress option of OmniBack II, since double compression only decreases performance without giving better compression results.
Encrypt Open Systems and public networking make data security in large enterprises essential. OmniBack II lets you encrypt le and rawdisk data so that it becomes unreadable. Data is encrypted before it is transferred over the network and before it is written to media. By default, the encrypt option is set to OFF. OmniBack II offers a simple built-in XOR algorithm
8 0 65h y h G D 6 11( 73g1#)10 8 r hP ~ } R W T | f { ` Y w X u k1#F)b#I vt g f @ y e

4-29
implemented in a shared "C" program library. Since OmniBack II provides the API used by the Disk Agent to interface with the encryption module, you can substitute your own internal encryption algorithms for greater security. Do this by writing your own encryption module. Compile the encryption module 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 method of distributing the keys. See Customizing the Encryption Algorithm on page 7-45. Public/Private This option lets you set access rights for restoring the data you back up. If a lesystem is backed up with the Private option, it can be restored only by you or the system administrator. By default, this option is set to Private. Setting the option to Public lets anyone restore your data.
Backup Files of Size

Use this menu button to specify the size of les to be backed up. You can backup les of All Sizes (default), les Bigger than, Smaller than, or within the specied size Range in KB.
Load Balancing
OmniBack II provides a dynamic connection of backup objects to available devices. Devices will be accessed in the order specied in the datalist. Set this option ON and specify the number of logical devices in the two text input boxes; the numbers represent minimum and maximum number of available logical devices. See Load Balancing on page 4-36 for more information. Reconnect Broken Connection In the event of short-term network problems, OmniBack will reconnect Backup Session Manager and Disk or Media Agents. The reconnect functionality works only for network problems during backup. This is, for example, the case when you have the Session Manager on one LAN and the Disk and Media Agents on another LAN and between these two LANs the connection is unreliable (WAN connections).
4-30
See Reconnect of Broken Connections on page 4-40 for more information. Report Level This option denes the level of errors that will be reported during a backup session. Setting a level means errors of this and higher levels are reported. For example, by setting the Minor button ON, all errors graded as minor, major, and critical are reported in the Messages eld. By default the level is set to Warning. Messages keyed as Normal always appear in the Messages eld. See Managing the Growth of the Database on page 8-4for a description how this option inuences the OmniBack II database. Log to Database OmniBack II provides three levels of the amount of details on les and directories stored in the database. Log All This is the default option. All backed up les are logged to the database. This complete information allows you to search for backed up les and allows OmniBack II to quickly position on the tape when restoring a specic le. However, this information may take a lot of space if there are many les.
Log Directories Details on directories only are stored in the database. This disables the search feature during restore and you will only be able to browse directories. However, OmniBack II still performs fast positioning because a le is located on the tape near the directory where it actually resides. This option is suitable for lesystems with many autogenerated les, such as news and mail systems. No Log No details on les or directories are logged in the database. You will not be able to search and browse les and directories. The restore will take longer because OmniBack II cannot fast position on the tape but will read from the start of the backup.
See Managing the Growth of the Database on page 8-4 for a description how this option inuences the OmniBack II database.

4-31
Lock Files During Backup This option denes how les are handled if the les are being used during a backup session. If set to ON, les are locked during the backup session, preventing the les from being modied during the backup. The default setting is OFF. Do Not Preserve Access Time Attributes Whenever a le is opened (read, locked, etc.), the access time of the le is changed. During backup each le in the specied leset is opened, locked, and read. When this option is set to OFF (default), the access time attributes remain 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 the moment of backup. Ignore hard links If this option is ON, OmniBack II will back up the entire le contents for each hard link. Causes OmniBack II to traverse the lesystem tree only once, thus signicantly speeding up the backup process. Use this option when 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 the percentage of the backup nished. The default is OFF. Pre- and Post-Exec The Pre-Exec option allows you to enter a command to be executed before the backup of a datalist or an object is initiated. The Post-Exec option allows you to enter a command to be executed after the backup of a datalist or an object has completed. You can customize the pre- and post-exec commands to your environment. See Using Pre- and Post- Exec Commands on page 7-6 for more information.
4-32
Protection This option enables you to set periods of protection for the data you back up to prevent the backup data from being overwritten for the specied period. The default value is Permanent. The backup protections are: None-Provides no protection. Data can be overwritten if the medium it is stored 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 at noon of the entered day. For example, if you enter in the entry field provided the date 97/8/22, the data will be protected until noon, August 22, 1997. Days-Data on the medium cannot be overwritten for the number of days specified. For example, if you set the protection for 2 days, and the current backup starts at 20:00 (8:00 PM) on Wednesday, the data will be protected until Friday at 20:00. Weeks-Data on the medium cannot be overwritten for the number of weeks specified. For example, if you set the protection for 1 week, and the current backup starts at 10:00 on Wednesday, the data will be protected until 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 backup information about this data in the OmniBack II database. See Managing the Growth of the Database on page 8-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 (cycle redundancy check) when a backup is run. The CRC check is an enhanced checksum function that lets you conrm whether or not data has been
4-33
written correctly to the medium. To verify media written with the CRC option, use the OmniBack II command omniver in the command line interface. Concurrency Concurrency allows more than one Disk Agent (up to ve) to write to one backup device. This helps OmniBack II keep the device streaming when it can accept data faster than a disk agent can send it (for DDS devices, this value 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 not dened, a default pool will be used. Prealloc List The Prealloc list is a subset of media from the media pool that OmniBack II will use for backup. This list also determines the order in which the media will be used. This order is important if you have selected the Strict media allocation policy when you congured the logical device. In this case, OmniBack II expects the sequence of the media in the device to correspond with that specied in the Prealloc list. If the media is not available in this sequence, OmniBack II issues a mount request.
Transferring Backup Ownership

OmniBack II lets you change the owner of a backup session. For example, as system administrator you may create a datalist and back up certain data for other employees. Changing the ownership of a backup session lets another person 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 is changed but not saved, the backup is treated as an interactive backup and the owner is not changed. This could result in a different kind of backup than
4-34
expected. For example, if you interactively start an incremental backup of a datalist and you are not the owner of the full backup, you will get another full backup instead of the incremental. To transfer ownership, follow the steps below: 1. Choose the Backup icon from the main HP OmniBack II window. The HP OmniBack II - Backup window appears. 2. In the HP OmniBack II Backup window, select the datalist the owner of which you want to change. 3. From the menu, select FileChange Ownership to open the Session Ownership window. 4. In the Session Ownership window, enter the user name, group, and host name of the user you want to transfer ownership to. No spaces are allowed between characters.
Figure 4-8
Changing the Owner of a Session
The default ownership of the backup session and objects remains with the original initiator of the backup session. See Conguring User Classes and Users on page 3-36 for more detals.

4-35
Load Balancing
The dynamic datalist/barlist layout in OmniBack II allows a dynamic connection of backup objects to available devices. If you run a backup session with the Load Balancing option, OmniBack II will automatically backup congured backup objects to available devices. Load Balancing Backup Backup performed with the Load Balancing option is suitable in the following 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 the Load Balancing option is recommended in the following cases: When you want to back up a small number of objects. When objects are backed up on simple devices, such as DDS. When you want to manually select the devices on which objects will be backed up. When you want to know on which medium/media objects will be backed up.
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 the Mount Request state. 4. Can not be started at all.
4-36
6 0 d D i ( 10 1# )#l1y r hP ~ } R W T | f { ` Y w X u k1#F)b#I vt
OmniBack does not automatically backup larger backup objects to devices with more capacity. Therefore, if you want to have a large backup object backed up on one medium, perform the backup without the Load 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.
The Load Balancing option redirects backup objects from failed devices to available devices (devices that are not used by another OmniBack II session and have the license to be started). Backup objects that are already partially written to media when a device fails cannot be redirected. The backup of such objects must be repeated. In this case, use the Restart Unsuccessful Backup from the OmniBack II Session Monitor.
g f @ y e
When you run backup with the Load Balancing option, OmniBack II will use devices in the order they are specied in the dynamic datalist. The order of devices specied in the dynamic datalist is of great importance. Make sure you congure faster and more reliable devices in the initial positions of the device list. If devices that are not reliable are congured in initial positions of the device list, backup sessions may more often result in mount requests or even the aborted status.
Configuring Backup with Load Balancing

To back up a datalist/barlist with the Load Balancing option, follow these steps: 1. In the HP OmniBack II - Main window, select the Backup icon. The HP OmniBack II-Backup window is displayed. 2. In HP OmniBack II-Backup window, select EditCreateOB II Datalist. The HP OmniBack II Backup Editor window is displayed. 3. In The OmniBack II Backup Editor select OptionsFor Datalist. 4. The HP OmniBack II-Session Options window is displayed where
6 0 d D i ( 10 #1 #Fm11y r hP ~ } R W T | f { ` Y w X u k1#F)b#I vt g f @ y e g f @ y e

4-37
Figure 4-9
Session Options window
For example, MIN "3" and MAX "4" in a datalist with six logical devices means that session will start when at least three devices are available and that a maximum of four devices can be used at the same time. The remaining 2 devices will be used if the running devices fail.
4-38
6 0 d D i ( 10 1# )#l1y r hP ~ } R W T | f { ` Y w X u k1#F)b#I vt
you can select the Load Balancing option for the datalist and the value of the following dynamic keywords:
MIN represents the required mininum number of available logical
devices (devices that are not being used by another OmniBack II process and have the license to be started) for starting the session. If fewer logical devices are available than specied under the MIN keyword, the session will queue.
MAX represents the maximum number of available logical devices that
can be used at the same time.
If fewer devices are listed in the datalist/barlist than specied in the MIN eld, the value of MIN will be automatically decreased to the number of devices specied in the datalist. The default value of load balancing is MIN 1, MAX 5.
When OmniBack II starts a backup device, it rst backs up local objects (located on the same host as the device). If there are no local objects, the device will back up remote objects (not located on the host where the device is located). In this case, OmniBack II will select remote objects on the host with the fewest running Disk Agents. The main purpose of this function is to prevent excessive use of the network and prevent overloading of hosts.
g f @ y e
If a device goes into a mount request in the middle of a backup, the Disk Agents connected to the device will NOT be reconnected to another running device. They will wait for the mount request conrmation. If a device fails in the middle of a backup, the Disk Agents connected to the device will be aborted. The user will have to manually restart the backup that has failed.
6 0 d D i ( 10 #1 #Fm11y r hP ~ } R W T | f { ` Y w X u k1#F)b#I vt g f @ y e

4-39
Reconnect of Broken Connections

In case of short-term network problems, OmniBack will reconnect the Backup Session Manager and Disk or Media Agents. The reconnect functionality works only for network problems during the backup. This is, for example, the case when you have the Session Manager on one LAN and the Disk and Media Agents on another LAN and between these two LANs the connection is unreliable (WAN connections).
Modifying Reconnect Parameters

The reconnect parameters can be modied by the following two enviroment variables:
OB2RECONNECT_RETRY - how long to try reconnecting after a socket
You must edit the /opt/omni/.omnirc le (on HP-UX 10.x) or /usr/omni/.omnirc le (on HP-UX 9.0x) on the remote client host in order to change reconnect parameters.
4-40
8 0 65 4 0 0 ( ' 0 4 G 11( Q111)#1( D C111#F ( 5 4 0 0 ( 4 r hP ~ } R W T | f { ` Y w X u k1#F)b#I vt
connection has been broke (default is 1200 secs). In other words, the WAN line between BSM and agents cannot be down more than OB2RECONNECT_RETRY secs.
OB2RECONNECT_ACK - how long to wait for the message of
acknowledgement (default 600 secs). In other words, if the agent does not get an acknowledgement in OB2RECONNECT_ACK secs, then it will assume that the socket connection is no longer valid.
Setting Up Scheduled Backups

By setting up a schedule for a datalist, you can automate your backups to run periodically at times of low system usage. With the scheduler, the backups you set up will run on the days and at the times you specify without your attendance as long as the devices and media are properly set. You can also specify the dates (holidays) to be skipped. See Skipping Backups During Holidays on page 4-47 for instructions. When a backup session is started, OmniBack II tries to locate all the resources 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 the resource once a minute until the timeout is reached. When the resources become available, one of queued sessions is randomly selected and started. (Note that the sessions are not 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 global options le. See Managing the Growth of the Database on page 8-4 for more information.
You can set up a schedule using the GUI. As soon as you have created and saved the schedule for a congured datalist, the schedule is activated and OmniBack II will check the schedule. No additional activation step is required. As the backup is running, the OmniBack II Backup Monitor window may issue mount prompts requesting media be mounted. If no one will be present to respond to mount prompts at the times chosen to run a backup, set up mount prompt scripts for automatic mount prompt handling. See the Automating Mount Prompt Handling on page 7-3 for more information.
8 h G D i d i 4 B s 11#)4 111#vh 10 UQvs 655 4 r hP ~ } R W T | f { ` Y w X u k1#F)b#I vt

4-41
When more than 5 sessions are scheduled at the same time, the exceess sessions are queued. You can change this number by modifying the MaxBSessions variable in the global options le.
Setting up Backup Schedules

There are two general methods of setting the start dates and times for a backup: 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 intervals between 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. If the cell is spread over more than one time zone, OmniBack II will use the time from the Cell Server.
4-42
8 h G D i d i 4 B s 11#)4 11#l#vh 10 UQvs 655 4 r hP ~ } R W T | f { ` Y w X u k1#F)b#I vt g f @ y e
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 specic date. 1. In the HP OmniBack II - Main window, select the Backup icon. The HP OmniBack II-Backup window is displayed. 2. In the HP OmniBack II Backup window, highlight a datalist to be scheduled. 3. Select EditChange Schedule from the menu bar. The Scheduler window opens. 4. In the Scheduler window, select the View pulldown menu and choose a month (January-December). 5. Click on the date you want to run the backup on in the Scheduler window to open the Daily Edit window. 6. Choose a Backup Type (Full or Incremental).

4-43
7. Select the starting time for your backup session. You can run a backup as frequently as every fifteen minutes. OmniBack II issues error messages if you select conflicting backup dates or times. The type of backup is indicated by the colors dened in the Legend at the bottom of the Scheduler window.
Figure 4-11
Backup Scheduler for Setting Periodical Backup
For example, to set up an incremental backup on October 4th, at 3:30, follow these steps: 1. Choose October from the View menu. 2. Select day 4. 3. Select Backup Type Incremental. 4. Click on start time 3:30. 5. Click the OK button. The main scheduler window will reappear with the date you set up highlighted in blue and the Legend color for an incremental backup. 6. Select File Save from the menu bar.
4-44
8 h G D i d i 4 B s 11#)4 11#l#vh 10 UQvs 655 4 r hP ~ } R W T | f { ` Y w X u k1#F)b#I vt
Selecting a Predefined Periodic Schedule You can set up a schedule based on the frequency of the backup by choosing a predened or custom schedule (see the next section). You can use the predened schedule as a template to create your own customized schedules. 1. In the HP OmniBack II - Main backup window, click the Backup icon to open the HP OmniBack II-Backup window. 2. In the HP OmniBack II-Backup window, highlight a datalist to be scheduled. 3. Select EditChange Schedule from the menu bar. The Scheduler window opens. 4. In the Scheduler window, select EditPredefined.... 5. Choose one of the predefined schedules. They are as follows: Daily intensive OmniBack II runs a full backup at midnight, and two additional incremental backups at 12:00 and 18:00 every day. This type of backup is intended for database transaction servers and similar environments with intensive backup requirements. Daily full OmniBack II runs a full backup every day at 21:00. This is intended for backups of single workstations or servers. Weekly full OmniBack II runs a full backup every Friday and Incr-1 backups every day at 21:00 from Monday to Friday. This is intended for small workgroup environments. Fortnightly full OmniBack II runs a full backup every second Friday. Between these backups, OmniBack II runs Incr-1 backups every Monday to Thursday, all at 21:00.

4-45
Monthly full OmniBack II runs a full backup on the 1st of every month, Incr-1 backup every week, and an incremental every other day. This is intended for relatively static environments.
Setting up a Custom Periodic Schedule 1. In the HP OmniBack II - Main window, click the Backup icon to open the HP OmniBack II-Backup window. 2. In the HP OmniBack II-Backup window, highlight a datalist to be scheduled. 3. Select Edit Change Schedule from the menu bar. The Scheduler window opens. 4. In the Scheduler window, select Edit Periodic... from the pulldown menu. The Scheduler-Periodic Tagging window opens. 5. In the Scheduler-Periodic Tagging window, select a Backup Type (Full or Incremental 0-9). 6. Choose a Time Cycle (every, every 2nd, etc). 7. Choose a Time Unit (day, month, etc.). 8. Enter the Backup 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 the schedule.
4-46
Editing a Daily or Monthly Backup Schedule Clearing a Schedule To eliminate a schedule that you have already set up, select the Edit
Clear All in the Scheduler window.
Note that when you clear a schedule, you clear all the schedule settings of a specied mode (full, incremental, or all) for the current year. Undoing the Clear To undo the clearing of a schedule, click Edit Undo in the Scheduler window. Changing the Start Date To change the start date, simply follow the procedure for setting up a backup for a specic date. See Setting up a Backup for a Specied Date on page 4-43.
Skipping Backups During Holidays

HP OmniBack II uses the /etc/opt/omni/Holidays le to enable you to set up a holiday backup schedule. This le must be created before you can use this feature. This le uses the same syntax as the standard UNIX holidays le. To skip running a backup during holidays, click the Holiday button in the Scheduler window. This instructs the scheduler to exclude from the current schedule all dates found in the Holidays le. For example, if the date January 1 is registered as a holiday, OmniBack II will not back up on that date. If you have scheduled a full backup for January 1st and an incremental for January 2nd, OmniBack II will skip running the full backup on January 1st but will run the incremental backup scheduled for January 2nd.

4-47
Overriding Scheduled Backup Options

Use the Override option if you want to run backups of certain datalists with different protection policies, for example, if you may want to apply different protection policies to different levels of backup (full, incremental, etc.). The Override option frees you from having to create separate datalists for different data protection schemes. To change the protection, select the datalist you want to modify. 1. In the HP OmniBack II - Main window, click the Backup icon to open the HP OmniBack II-Backup window. 2. In the HP OmniBack II-Backup window, highlight a datalist to be scheduled. 3. Choose Edit Change Schedule. The Scheduler window appears. 4. Choose Options and select a backup type. The Scheduler Option window appears. In our example, we chose Full. 5. Click the Protection button to choose the protection period you want to apply to the scheduled backup. In our example, the full backups of this datalist will be protected for the selected period. 6. In the date entry fields, enter the days, weeks, or date until which you want the data protected and click the OK button to register the settings. The window disappears and returns you to the Scheduler window. To implement a schedule protection override using the command line, enter the omnib command with the -datalist and -protect options and the number of days, weeks, etc. For example, enter: omnib -datalist datalistname -protect weeks 2. For more information, see the manpages for the omnib command.
4-48
To Undo an Override 1. In the HP OmniBack II - Main window, click the Backup icon to open the HP OmniBack II-Backup window. 2. In the HP OmniBack II-Backup window, highlight a datalist to be scheduled. 3. Choose Edit Change Schedule. The Scheduler window appears. 4. Choose Options and select a backup type. In our example, we chose Full. 5. The Scheduler - Full Options window appears where we select the Default option. This will cause OmniBack II to use the protection originally specied in the datalist.

4-49
4-50
Restoring Data
5-1
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 restore les and disks backed up with OmniBack II. It is designed to guide you through the restore process, allowing you to select from lists whenever possible. OmniBack II also offers a command-line interface for restores. For more information on the command-line interface for restores, see the omnir manpage.
5-2
uP u ` YR TP h SQ)EI US#F
Restore Overview
Basically, restoring data consists of providing the following information: FROM WHAT HOW TO From which backup session to restore What les, directories, or disks to restore Which restore options are to be used Where the les, directories, and disks are to be restored
OmniBack II helps you provide this information by guiding you through the restore process. OmniBack II provides three types of restores, depending on how the data was backed up: File restore from a filesystem backup File restore from a rawdisk backup Rawdisk restore from a rawdisk backup
A lesystem backup includes the logical structure of the data. Information about this logical structure as well as the data are written to the media management database. A rawdisk backup does not include information about the structure of the data; therefore, the media management database has no information about the individual les in the backup. Thus, the backup type inuences your ability to locate and restore individual les. For this reason, each of these restore types is explained separately in the following sections.
Q4 6 2 vb4 Q#) 4 2 y (58 4 uP u ` YR TP h SQ)EI US#)

5-3
Restoring Files from a Filesystem Backup

The Media Management database of HP OmniBack II tracks the following information 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 backup media
OmniBack II uses this information to help you locate and restore data. To locate and restore les and directories from a lesystem backup, follow these steps: 1. In the OmniBack II Main window, select a cell server and click the Restore icon to open the OmniBack II Restore window. 2. In the OmniBack II Restore window, double-click the backup object containing your file to open the FileSystem Restore Dialog window. 3. In the FileSystem Restore Dialog window, specify the files or directories for restore. You can optionally specify the fileset restore options (after you have specified the version of a file or directory) and restore 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-4
h G D 45 t8 6 8 6 (58 4 1#)nQ8 Q#4 d 1En1( #4 d 110 6 Q#F uP u ` YR TP h SQ)EI US#F
Browser
Offers a graphical representation of backup objects. This view is suitable for backups with a smaller number of backup objects. Offers a text list of backup objects. This view is suitable for backups with a larger number of backup objects.
List
To change the view, perform the following steps: 1. In the OmniBack II Main window, select a cell server and click the Restore icon to open the OmniBack II Restore window. 2. In the OmniBack II Restore window, choose View from the menu and select an appropriate view.
Selecting the Backup Object

To select objects for restore, follow these steps: 1. In the OmniBack II Main window, select a cell server and click the Restore icon to open the OmniBack II Restore window. 2. A list of backup objects is displayed in the OmniBack II Restore window. Double-click the backup object that contains the files and directories you want to restore to open the FileSystem Restore Dialog window opens. 3. In the FileSystem Restore Dialog window, specify the files and directories for restore. Follow the online help instructions.
h G D 458 t8 6 8 6 (58 4 1#)n#Q4 d lEn1( 4 d 110 6 7) uP u ` YR TP h SQ)EI US#)

5-5
Selecting the Files to Restore
Figure 5-1
Browsing Files
To select the les and directories for restore, follow these steps: 1. In the OmniBack II Main window, select a cell server and click the Restore icon to open the OmniBack II Restore window. 2. In the OmniBack II Restore window, double-click the backup object that contains the files and directories you want to restore. The FileSystem Restore Summary window opens.
5-6
3. In the FileSystem Restore Summary window, specify the files and directories for restore. Follow the online help instructions.
g f @ y e
When you click on a le/directory for restore, you automatically select the last version of the le/directory. With a right mouse button click on a le/directory, you can select a specic version of a le/directory.
Browsing Files to Restore

g f @ y e
If you have chosen the No log backup options (no details on backed-up les and directories are stored in the database) or you have purged detail catalogs from the database, you will not be able to use the browse functionality. Instead, OmniBack II opens the Filesystem Restore Dialog window where you type in the les you want to restore. See Description of Backup Options on page 4-29 and Managing the Growth of the Database on page 8-4 for more information.
OmniBack II allows you to browse the list of les and directories you can restore: Double-click on a directory in the FileSystem Restore Summary window to expand that directory, that is, opens other directories and files on that path. You can perform the same task by simply clicking + button beside directory name. Double-clicking a second time on the directory above contracts the directory, that is, closes directories and files on that path. You can do the same by clicking - button beside directory name. Shaded directories can only be expanded or contracted but not selected for 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 a backup of /users/mike/myfiles.

5-7
Selecting a File/Directory Version

Generally, you have more than one backup containing the les you want to restore, that is, you have several versions of a le or directory to choose to restore from.
To Restore the Last Version of a Lost File If a le has been lost, you will probably want to restore the most recent copy of that le. To restore the most recent copy of a lost le, follow these steps: 1. In the OmniBack II Main window, select a cell server and click on the Restore icon to open the OmniBack II Restore window. 2. In the OmniBack II Restore window, double-click the backup object that contains the les and directories you want to restore. The FileSystem Restore Dialog window opens. 3. In the FileSystem Restore Dialog window, click on the required file/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 le has been corrupted, you may want to restore an older version of the le. In this case, recover the le from a backup containing an uncorrupted version of the le. To select an older backup containing this le, proceed as follows: 1. In the OmniBack II Main window, select a cell server and click on the Restore icon to open the OmniBack II Restore window. 2. In the OmniBack II Restore window, double-click the backup object
5-8
that contains the les and directories you want to restore. The FileSystem Restore Dialog window opens. 3. In the FileSystem Restore Dialog window, click on the required file/directory to display a cascading menu of files and directories. 4. Click the right mouse button on a file/directory whose version you want to select. 5. Click Select Version from the menu and in the Version 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 leset restore options apply to the specic les or directories selected for restore in the FileSystem Restore Dialog window. To specify leset restore options, follow these steps: 1. In the OmniBack II Main window, select a cell server and click on the Restore icon to open the OmniBack II Restore window. 2. In the OmniBack II Restore window, double-click the backup object that contains the les and directories you want to restore. The FileSystem Restore Dialog window opens. 3. After you have selected a version of the file/directory for restore, choose the Restore summary/details window to open theFileSystem Restore Summary window. 4. Highlight the selected version of a file/directory in the FileSystem Restore Summary window and choose Options to open the File Restore Options window. Enter the restore options you want to apply to the selected files or directories. See below for a description of available options.

5-9
Figure 5-2
Restore Options
Repeat the procedure to add options to lesets as needed. Restore As Restores the le or directory as the pathname that you enter in the eld to the right of the button. The destination pathname can be an existing pathname or a new pathname. This enables you to rename objects as you restore them Restores the Fileset into the pathname that you enter in the eld to the right of the button. This appends the leset to the pathname. The destination pathname must be an existing pathname. Restores only les matching the enter le name criterion. You can use wildcards to specify the
Restore Into
Match
5-10
le name. Exclude Excludes the les and directories which you enter in the eld from the restore. Enter the full pathname of the le. Wildcards are not allowed. For example, you may want to exclude the /tmp directory. Excludes les matching the entered le name criterion. You can use wildcards to specify the le name. For example, you may want to skip all *.o les in the selected leset.
Skip

5-11
Selecting Options for the Restore Session These options apply to the whole restore session and all les (directories) restored with one session. 1. In the OmniBack II Main window, select a cell server and click on the Restore icon to open the OmniBack II Restore window. 2. In the OmniBack II Restore window, double-click the backup object that contains the les and directories you want to restore. The FileSystem Restore Dialog window opens. 3. Choose Options in the Restore Dialog window to open the Restore Options window. 4. Enter the restore options you want to apply to the selected files or directories. See below for a description of available options Target Hostname By default, les are restored to their original hosts. You may want to choose some other host in this eld. Merges existing les with les from the backup. If a le on the disk is newer than the backed-up version, the newer le is kept. If a le on the disk is older than the backed-up version, the le is overwritten with the new version from the backup. The default is ON. Replaces the les and directories on the disk with the version of the les and directories on the media. The default is OFF. Preserves the les and directories on the disk, if they exist. The version of these les and directories on the media is not restored. The default is OFF.
Merge
Overwrite
No Overwrite
Restore Protection Attributes
5-12
Preserves the original protection attributes of each restored le. When set to OFF, OmniBack
II applies the protection attributes of the current restore session. The default is ON. Restore Time Attributes Preserves the time attribute values of each restored le. When set to OFF, OmniBack II sets the time attributes of the restored objects to the current date and time. The default is ON. Restores sparse les in their original form. This is important because sparse les can consume additional disk space unless they are restored in their original form. The default is OFF. Denies access to les during the restore. By default the option is set to OFF and the les are not locked. Deletes les that were removed between a full and incremental backup. This option is useful when you restore a complete directory or disk and want to have only those les which were in the directory or disk when the incremental backup was done. The default is OFF. This option is used with the Omit Deleted Files or Overwrite options. If the le is busy during restore, OmniBack II cannot restore the le. This option moves the busy le lename to #lename (with a hash in front of the lename.) When set to ON, OmniBack II displays the names of the les and directories in the Messages section of the Restore Monitor window as the objects are being restored. The default is OFF. When set to ON, OmniBack II displays detailed statistical information about the restore session. The default is OFF.
Restore Sparse Files
Lock Files During Restore
Omit Deleted Files
Move Busy Files
List Restored Files
Display Statistical Information

5-13
Pre- exec command
Post- exec command
5-14
A Pre- exec command is executed as soon as the Disk Agent is started, but before any restore processing has started. See Using Pre- and Post- Exec Commands on page 7-6 for more information. A Post- exec command is executed just before the Disk Agent terminates. See Using Pre- and Post- Exec Commands on page 7-6 for more information.
Activating and Monitoring the Restore

Before you actually run a restore session, you may want to preview it. The Restore Monitor window also allows you to change to a different logical device for restore or to preview a restore session.
Figure 5-3
Monitoring the Restore Session
To activate the restore, follow these steps: 1. In the OmniBack II Main window, select a cell server and click the Restore icon to open the OmniBack II Restore window. 2. In the OmniBack II Restore window, double-click the backup object that contains the les and directories you want to restore. The
5-15
3. After you have entered and selected all the requested information needed for the restore in the Filesystem Restore Dialog window, click the OK button. The Restore Monitor window appears with the device status indicating the Inactive/Waiting status and the session indicating Pending. 4. Choose: Actions Preview Restore to preview the restore session. Actions Start Restore to start the restore session.
5. Select the Network Load. Setting this option to Low reduces the load on the network when running OmniBack II. This prevents the data transmission for restore from blocking the network for other users but increases the time required for the restore. 6. Select Report Level. By default all messages are displayed - the warning level. If you select any other levels, only messages with higher priority are displayed. 7. Click on Start Restore to start running the restore. The Status eld indicates the session is Pending then Running. If OmniBack II requires media, Mount Request appears in the Status eld. To Respond to Mount Requests When prompted by a Mount Prompt message from the Restore Monitor, insert the correct media in the device and conrm the prompt request in the following way: 1. Close the Mount Request dialog. 2. Select (highlight) the device with the Mount Request status. 3. Select Actions Confirm Mount Request from the menu bar.
5-16

FileSystem Restore Dialog window opens.
If 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 specic 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, OmniBack II will automatically use the copy and no mount request will be issued.
The status of the session and device changes to Running. When the session has completed, the status of the session displays Completed and a window appears with the message "Session Completed!" 8. Click OK to close the message window and return to the OmniBack II Restore Monitor window. 9. Select File Close to close the monitor window and return to the OmniBack II Restore window. Viewing the Messages Field While the restore is running, messages appear in the Restore Monitor window Messages eld indicating the status of the lesets, devices, and the progress of the restore. While messages are still displayed in the Messages eld, position the cursor in the Messages eld and click on the RIGHT mouse button. Choose from the following message options in the menu that appears: Search Clear To search for specic string in the message line. To clear all messages from the eld.
Scroll Messages To scroll messages as they are generated. Print Messages To print messages on a printer. The maximum buffer for messages in the Messages eld is limited with the congurable parameter MAXGUIMSG. See OmniBack II Global Options File on page 7-13 for more information. If the maximum buffer is exceeded, messages stop appearing in the Messages eld and the error message Output disabled appears; however the backup continues.
h G D 458 t8 6 8 6 (58 4 1#)n#Q4 d lEn1( 4 d 110 6 7) uP u ` YR TP h SQ)EI US#) g f @ y e

5-17
Searching for a Specific File

From time to time you may forget where a specic le was located on your host, although you remember a part of the le name. OmniBack II gives you a way to easily search for such les. Note that you should normally use the browser to nd your les. The search action may take longer and it will only show the rst 500 les matching the selected criteria. In the event this limit is reached, you must further limit your search criteria. 1. From the OmniBack II Main menu, choose a cell server and click the Restore icon to open the HP OmniBack II Restore window. 2. Choose Actions Search to open the HP OmniBack II Restore - Search window. 3. Enter as much information as possible to speed up the search. Click Search to start searching for the file. Note that this action can take some time, depending on your configuration. 4. If you want to restore all files with the same name, select any object from the File Found In list and click OK to open the FileSystem Restore Dialog window. Continue with the normal restore procedure. 5. If you want to select a specific file, double-click on the host in the File Found In list and select the specific file. Continue with the normal restore procedure.
Parallel Restore
OmniBack II enables parallel restore, meaning that any subset of lesystems and 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 concurrency higher than one.
5-18
Parallel restore improves performance if you restore les to different disks. Otherwise, the les are restored sequentially. To perform a parallel backup follow these steps: 1. In the OmniBack II - Main menu, select the Restore icon to open the HP OmniBack II Restore window. 2. In the HP OmniBack II Restore window, from the menu select ActionsParallel Restore. 3. In the HP OmniBack II Restore window, double-click a host from the list to display a list of its mount points. 4. Select the hosts mountpoints. Selected mountpoints are displayed in the list of objects selected for restore on the right side. 5. Double-click an object from the list to open the Filesystem Restore Dialog window where you specify files and directories of the selected object to be backed up. 6. After you have specified files and directories for a parallel restore, click Restore... to open OmniBack II Restore Monitor window. 7. In the OmniBack II Restore Monitor window, click Actions Start Restore to run a parallel restore.

5-19
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 the OmniBack II Main Menu to open the OmniBack II Restore window. 2. Select the rawdisk backup from which you want to restore. 3. Select Actions Restore Selected to open the Rawdisk Restore Dialog window. 4. In the Backed up On field, choose the version you want to restore. Click ... to get a list of versions. 5. The Sections field shows all disk sections backed up in the selected backup session. To remove a disk section from the list, select the section and click the Remove button. If you need to add it back, type its name in the field below and click Add.
5-20
4 d ( d 6 ( y 0 65 4 s G 6 i (5 8 4 #1 1# 111U1( Qb#8 1mQ)E10 6 Q#F uP u ` YR TP h SQ)EI US#F
Figure 5-4
Restoring a Rawdisk
Specifying Rawdisk Restore Options

OmniBack II provides restore options which allow you to control a rawdisk restore session. To select the restore options, choose Rawdisk Restore Options. The following options are available: Target Hostname Allows you to change the hostname where the rawdisk section should be restored. By default, OmniBack II restores to the original host. A Pre-exec command is executed as soon as the
Pre- exec
4 d ( d 6 ( y 0 65 4 s G 6 i (5 8 4 ml 1# 111U1( Qb#8 1mQ)E10 6 Q) uP u ` YR TP h SQ)EI US#)

5-21
Post- exec
List Restored Objects
Starting and Monitoring a Rawdisk Restore

When you activate a rawdisk restore, you open the OmniBack II Restore Monitor window, enabling you to monitor the progress of your restore. The Monitor window also allows you to respond to mount requests for the restore. To activate the restore, follow these steps: 1. From the Rawdisk Restore Dialog, choose OK to open theRestore Monitor window. 2. Choose:
Actions Preview Restore to preview the restore session.
3. Select the Network Load. Setting this option to Low reduces the load on the network when running OmniBack II. This prevents the data transmission for restore from blocking the network for other users but increases the time required for the restore.
5-22
4 d ( d 6 ( y 0 65 4 s G 6 i (5 8 4 #1 1# 111U1( Qb#8 1mQ)E10 6 Q#F uP u ` YR TP h SQ)EI US#F
Disk Agent is started, but before any restore processing has started. A Post-exec command is executed just before the Disk Agent terminates. For more information, see Using Pre- and Post- Exec Commands on page 7-6. When set to ON, OmniBack II displays the names of the disk sections in the Message section of the Monitor window as the objects are restored. The default is OFF. When set to ON, OmniBack II displays detailed information about the restore session. The default is OFF.
Actions Start Restore to start the restore session.
4. Select the Report Level. By default all messages are displayed - the warning level. If you select any other levels, only messages with higher priority are displayed. 5. Click on Start Restore from the menu bar to start the restore. The Status field indicates the restore session is Inactive/Waiting, then finally Running. Other status messages may appear depending on the progress of the restore. When the session has completed, the status of the session displays Completed 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 read data. 1. Insert the needed medium in the device. 2. Select the device with the Mount Request status. 3. Select Actions Confirm Mount Request from the menu bar. The status of the session and device changes to Running.
4 d ( d 6 ( y 0 65 4 s G 6 i (5 8 4 ml 1# 111U1( Qb#8 1mQ)E10 6 Q) uP u ` YR TP h SQ)EI US#)

5-23
Restoring Files from a Rawdisk Backup

Restoring les from a rawdisk backup is supported on HFS lesystems only. You can restore only "regular" Unix les from a rawdisk backup. Recovery of any other le types is not supported by OmniBack II. You can restore les from any directory except the CDF directory (of cluster environments).
Selecting the File from a Rawdisk to Restore

1. Select a cell server and click Restore in the OmniBack II Main Menu. The OmniBack II Restore window appears. 2. Select the rawdisk backup object which contains the file you want to restore. 3. Select Actions Restore Single File... to open the Single File Restore window. The backup object you selected is displayed in the Rawdisk field.
5-24
h G D G 6 i 8 6 (58 4 l##FE8 1mQ)En1( #4 d 110 6 Q#F uP u ` YR TP h SQ)EI US#F
Figure 5-5
Restoring Single Files from a Rawdisk
4. In the Backed Up On field, choose the version from which you want to restore. Click ... to get a list of versions. 5. In the Restore Files field, enter the path and a file name. 6. Enter the disk section name in the field labeled From Section or click the ... button to select the section from a list.
h G D G 6 i 8 6 (58 4 1#)E8 1m)bl( 7 4 d 110 6 7) uP u ` YR TP h SQ)EI US#)

5-25
Specifying Rawdisk Restore Options

The rawdisk restore options apply to all les to be restored. 1. Choose Single File Restore Options ... to open the Filesystem Restore Options window. The following options are available: Target Hostname Allows you to change the hostname where the rawdisk section should be restored. By default, OmniBack II restores to the original host. Preserves the destination version of les and merges the restore leset into the existing leset on the disk. The default is Merge. Replaces the les and directories on the disk with the version of the les and directories on the media. Preserves the les and directories on the disk, if they exist. The version of these les and directories on the media is not restored. Preserves the time attribute values of the restored le. When set to OFF, OmniBack II sets the time attributes of the restored le to the current date and time. The default is ON. Preserves the original protection attributes of the restored le. When set to OFF, OmniBack II applies the protection attributes of the current restore session. The default is ON. When set to ON, OmniBack II displays the name of the le in the Messages section of the Monitor window while the object is being restored. The default is OFF.
Merge
Overwrite
No Overwrite
Restore Time Attributes
Restore Protection Attributes
List Restored Files
5-26
When set to ON, OmniBack II displays detailed information about the restore session. The default is OFF. A Pre-exec command is executed as soon as the Disk Agent is started, but before any restore processing has started. See Using Pre- and Post- Exec Commands on page 7-6 for more information. A Post-exec command is executed just before the Disk Agent terminates. See Using Pre- and Post- Exec Commands on page 7-6 for more information.
Pre- exec
Post- exec
Starting and Monitoring File Restore from a Rawdisk

After you have provided the information necessary for the restore, you are ready to activate the restore. 1. In the Single File Restore window, choose OK to open the OmniBack II Session Monitor window. 2. Choose:
Actions Preview Restore to preview the restore session.
Actions Start Restore to start the restore session.
3. Select the Network Load. Setting this option to Low reduces the load on the network when running OmniBack II. This prevents the data transmission for restore from blocking the network for other users but increases the time required for the restore. 4. Select the Report Level. By default all messages are displayed - the warning level. If you select any other levels, only messages with higher priority are displayed.
h G D G 6 i 8 6 (58 4 1#)E8 1m)bl( 7 4 d 110 6 7) uP u ` YR TP h SQ)EI US#)

5-27
5. Click on Start Restore from the menu bar to start the restore. The Status field indicates the restore session is Inactive/Waiting, then finally Running. Other status messages may appear depending on the progress of the restore. When the session has completed, the status of the session displays Completed 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 le or directory but do not know the lename, do the following: 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.
5-28
Monitoring Sessions
6-1
In This Chapter OmniBack II allows you to monitor currently running sessions, as well as viewing already nished sessions. You can view messages and status of the sessions, devices used, objects backed up or restored, and so forth. In addition, a Cell Monitor is provided that helps administrators of environments with more cells to have an overview of all their cells.
6-2
I Y h } ` YR T Y I T T #vEI q#SP #b
Monitoring Running Sessions

OmniBack II allows you to connect to any running backup session and monitor the progress of the session, abort the session, or respond to a mount prompt request. For more information on mount prompt requests, see Automating Mount Prompt Handling on page 7-3. The progress and status of running sessions can be monitored using the OmniBack II Session Monitor window. As soon as a session is nished or aborted, it is no longer displayed as the currently running session but as a previous session. 1. From the OmniBack II Main menu, choose Monitor to open the OmniBack II Session Monitor window. The window shows the progress and the status of all currently running sessions in a cell. From the Actions menu you can abort a session. When you run an interactive backup or restore session, a monitor window is opened 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 doubleclicking on the session to open the OmniBack II Backup Monitor or the OmniBack II Restore Monitor window.
8 0 6 8 8 4 s 6 0 0 ( 6 0 11( #v10 111)10 6 5 11( w I Y h } ` YR T Y I T #T b#I U#SP E

6-3
Figure 6-1
Monitoring a Restore Session
In this window you can see all backup or restore objects with their status, the status of devices, and the messages generated in this session. From the Actions menu you can abort the session or cancel a mount prompt request. By clicking the right mouse button in the Messages area, you can scroll, clear, print, or search for specic messages.
6-4
8 0 6 8 8 4 s 6 0 0 ( 6 0 l1( #v10 111)10 6 5 11( w I Y h } ` YR T Y I T T #vEI q#SP #b
Viewing Previous Sessions

As soon as a session is nished or aborted, it is no longer displayed as a currently running session but as a previous session. 1. From the OmniBack II Main menu, choose Monitor to open the OmniBack II Session Monitor window. 2. Choose View 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 the OmniBack II Session Monitor window showing previous sessions: 1. Restarting unsuccessful backups. See Managing Failed Backups on page 7-14 for more information. 2. Removing detailed information from the session. See Managing the Growth of the Database on page 8-4 for more information.
8 0 6 8 8 4 s 8 6 2 6 11( #vE11( 4 10 m4 6 I Y h } ` YR T Y I T #T b#I U#SP E

6-5
Viewing Details of Previous Sessions

You can view detailed information of a previous session by double-clicking on the session to open the OmniBack II Backup Monitor or OmniBack II Restore Monitor window. In this window you can see all backed-up or restored objects with their status, as well as messages generated in the session. Using the View menu you can also nd media used in this session. This functionality is available for backup sessions only. By clicking the right mouse button in the Messages area, you can scroll, clear, print, or search for specic messages. By double-clicking on a specic object, you can see only the messages related to this object.
6-6
8 0 6 8 8 4 s 8 2 6 6 11( ##vb11( 6 Q4 10 mQ4 I Y h } ` YR T Y I T T #vEI q#SP #b
Monitoring Several Cells

For environments with several OmniBack II cells congured, a special monitor is provided giving you an overview of all your cells. To start the Cell 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 the Actions menu you can view different types of backup objects, lists scheduled objects, or list disks not congured for backup.
8 d #F# Q10 6 5 11( w d 4 ' d 4 24 s ( 6 0 I Y h } ` YR T Y I T #T b#I U#SP E

6-7
8 d #F# Q10 6 5 11( w d 4 ' d 4 24 s ( 6 0 I Y h } ` YR T Y I T T #vEI q#SP #b
6-8
OmniBack II Advanced Tasks and Concepts
7-1
In This Chapter This chapter describes customization features and provides instructions for conguring 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-2
Pf h X I SQ#T o #sF#QQH gvt Esd V I u w u V hX I u V H wX u Y I r
Automating Mount Prompt Handling

The Mount Request status on the monitor screen indicates that a device needs 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 conrmed or the session is aborted. If there is no response to the mount prompt within a predened mount prompt delay (30 minutes by default), a mount prompt script is executed on the Cell Server where the session is running that sends an 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 congured using Advanced Options in the Logical Device Configuration window. You can change the default script by modifying the MountScript variable in the global options le. To change the default mount prompt delay, modify the MountDelay variable in the global options le. OmniBack II invokes the mount prompt script and provides the following command line arguments: 1. 2. 3. 4. 5. 6. 7. 8. Unix login of user who started the backup Unix group of user who started the backup host where the backup was started PID of the backup process session key logical device that generated the mount request host of the logical device pathname of the physical device name waiting for new medium (for libraries, the slot number (SCSI Library) or the device file (MO Jukebox)
d i 0 5h 50 10 6 l1#))31( C3l1( w 10 Q13 65 (5 Pf h X I Q#T o gF#QgH s#vt Esd V I u w u V hX I u V H wX u Y I r

7-3
is used instead of the pathname of the physical device) 9. device type number 10. device type name 11. medium id 12. medium label 13. medium location 14. pool name 15. media allocation policy of the pool 16. media type number 17. media type name 18. session key If OmniBack II is unable to dene a medium to mount, empty parameters are sent to the mount prompt script. This can occur if there are no media remaining in the pool or if there is no space remaining on the medium. For more information on adding a script le, see the online help topic "Conguring Advanced Options for a Logical Device" in "Logical Device Conguration Tasks."
Mount Prompt Script Examples

This section provides some typical modications to the mount promt script. An email must be sent to a specic user only: In the Mount.sh script, change the $USER@$HOSTNAME variable to the specic 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/null 1>/dev/null
Enter all commands in one line only.
7-4
d i 0 5h 50 10 6 11)C31( C311( w 10 Q13 65 (5 Pf h X I SQ#T o #sF#QQH gvt Esd V I u w u V hX I u V H wX u Y I r
Automating mount prompt handling OmniBack II can detect that a blank tape has been loaded and continue with a backup session without your conrming the mount request. To automate the mount prompt handling, enter the following lines in Mountscript:
sleep time-period-in-seconds /opt/omni/bin/omnimnt -session $SESSIONKEY -device $DEVNAME.
d i 0 5h 50 10 6 l1#))31( C3l1( w 10 Q13 65 (5 Pf h X I Q#T o gF#QgH s#vt Esd V I u w u V hX I u V H wX u Y I r

7-5
Using Pre- and Post- Exec Commands

Before a backup can begin, additional actions are sometimes necessary. For example, before a backup begins, transaction processing on a database must stop and the users must be notied. Pre- and Post- exec actions are provided on two levels: Before and after the backup of each datalist (session) is started. These actions are executed on any host. Before and after the backup of each object is started. These actions are started on the Disk Agents where the object resides.
Pre- and Post- exec functions are implemented using the Unix pipe mechanism. All processes started in the Pre- or Post- exec functions must nish before processing continues.

Be sure that you follow the instructions provided in the following sections when creating your Pre- and Post- exec scripts.
Configuring Pre/Post-Exec Commands for a Datalist/Barlist

To back up a datalist with the remote Pre-Exec or Post-Exec options follow these steps: 1. In the HP OmniBack II - Main window, select the Backup icon. The HP OmniBack II-Backup window is displayed. 2. In HP OmniBack II-Backup window, select a datalist and click EditModify List. The OmniBack II Backup Editor window is displayed. 3. In the OmniBack II Backup Editor, select OptionsFor Datalist. The HP OmniBack II-Session Options window is displayed where you can specify the Pre-Exec or Post-Exec commands.
7-6
i j f i 6 111)E171v11#4 10 #8 Pf h X I SQ#T o #sF#QQH gvt Esd V I u w u V hX I u V H wX u Y I r
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 and remote hosts. Pre- and Post- exec commands for a datalist are started before and after the backup of a datalist/barlist session. These commands can be executed on any host. The following environment variables are exported and can be used in Preand Post- exec scripts for a datalist/barlist session on any host: SESSIONKEY Is used to identify the running session. You may, for example, abort a backup session before it is started if something is wrong. You can use this variable with Preexec commands only.
7-7
111)b# l11Sv1 # Q#)EgF# g s#v Es
PREVIEW
SESSIONID
SMEXIT
OWNER
Be sure that you check the following before conguring Pre- and Post- exec commands 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 option UsePanScripts to 1 and the host 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 the following 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 have permissions -r-x------ set. If a Pre- exec command fails (returns a non-zero value), the backup status
7-8
111)E 71v11#v1 # SQ#)E#sF# Q gv Es
Set to 1 if preview is running. Set to 0 if backup is running. You can therefore modify your commands to be executed only during a backup and not a preview. Is used to identity a nished session and is recorded in the database. You can only use this variable with the Postexec command. Exit code of the Session Manager and is the same as the exit code of the omnib 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 commands only. Owner of the session (for example, dizdar@emina.hermes).
of the session is set to failed and the session is aborted. If a Post- exec command fails (returns a non-zero value), the backup of the session is set to completed with errors. The Pre- and Post- exec commands for a datalist are by default NOT executed during a preview of a backup. This behavior is defined by the ExecScriptOnPreview variable in the global options file. See OmniBack II Global Options File on page 7-13 for more information. Pre- and Post- exec commands are handled in the same way as commands entered at the shell prompt. 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, you cannot use OmniBack II (GUI or command-line) to stop a session. The only way to stop a session while it is executing a Pre- or Post- exec command is to use the Unix kill command. The Pre- and Post- exec processes operate in background mode. Therefore, do not use any interactive commands for Pre- and Post- exec processing. All commands are started with the UID of the user configured as the session owner. If a user is not configured on the Cell Server, Pre- and Post- exec commands are not executed but the backup continues. The Pre- and Post- exec scripts must send some output at least every 15 minutes by default or the scripts get aborted. You can change this time interval by modifying the ScriptOutputTimeout variable in the global options file. Timeout is provided - if no message is received within the specified timeout in seconds, the script execution is aborted. If the session owner has Backup as Root permission, the script is started as root, otherwise as the session owner. If there is no executable script on the host or if the path of the script is wrong, OmniBack II displays an error message that the script failed and the session is aborted. The executable script can be located on any host. If the pre-exec or

7-9
A pre-/post- exec script may hang because it did not close all le descriptors before forking the new process. This is the case if the new process runs in the background and does not exit (for example, database server process (dbstart), some deamon processes, etc.). In this case, a user can use the detach command. The source of the detach command is provided in the detach.c le. This command is ofcially unsupported. Example: /opt/omni/bin/utilns/detach pre_script [arguments...]
The following features relateto pre/post-exec commands on a local host only: The Pre- and Post- exec commands for a datalist must be located on the Cell Server. By default, Pre- and Post- exec functions can be located in any directory on the Cell Server. If you set the UsePanScripts variable in the global options file, scripts can be started from a specific directory only. See the global 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-10
111)E 71v11#v1 # SQ#)E#sF# Q gv Es

post-exec script fails, the session is aborted.
If a command writes any text to stdout, this text is received by the Disk Agent, sent to the Session Manager, and written to the database. A stderr is redirected to /dev/null. You can redirect it to stdout to get error messages logged to the database.
Pre-/post- Exec Commands on a Local Host
Pre- and Post-Exec Commands for an Object

Pre- and Post- exec commands for an object are executed before the backup of the object is started or nished. You can specify these commands for each object independently. These commands are executed on the host where the Disk Agent is running. For overriding Pre- and Post-exec command scripts for an object, add the following variables:
OB2PREEXEC=full_pathname OB2POSTEXEC=full_pathname
into the le:

/opt/omni/.omnirc
If the Pre-exec or Post-exec script is specied in the datalist for an object, it will be overridden by the scripts specied in the .omnirc le. The following environment variables are exported and can be used in the Pre- and Post- exec scripts for an object on the host where the Disk Agent is running: PREVIEW Set to 1 if preview is running. Set to 0 if backup is running. You can therefore modify your scripts to be executed only during a backup and not during a preview. The Disk Agent sets its exit code (zero is successful) to the BDACC environment variable. This variable can be checked in the Post- exec script thus making the Postexec command dependent on the successful termination of the Disk Agent.
BDACC
Be sure that you check the following before conguring Pre- and Post- exec commands: The Pre- and Post- exec commands for an object are also executed during the preview of a backup. Therefore, you may want to preview your backup first and then add the Pre- and Post- exec commands, or check the

7-11
7-12
11)E v11#v1 F SQ#)E#sF# Q gv Es
PREVIEW environment variable in your scripts. If a Pre- exec command for an object fails (returns a non-zero value), the backup status of the object is set to aborted and the Disk Agent stops processing. Therefore, no backup of the object exists. If a Post- exec command fails (returns a non-zero value), the backup status of the object is set to aborted. However, a backup of the object exists and data can be restored. The Pre- and Post- exec commands should send some output to the Disk Agent at least every 120 minutes by default, or the backup of the object will be aborted. This timeout period can be changed by modifying the SmDaIdleTimeout variable in the global options file. Pre- and Post- exec commands are handled in the same way as commands entered 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, you cannot 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- exec command is to use the Unix kill command. The Pre- and Post- exec processes operate in background mode. Therefore, do not use any interactive commands for Pre- and Post- exec processing. If a command writes any text to stdout, this text is received by the Disk Agent, sent to the Session Manager, and written to the database. A stderr is redirected to /dev/null. You can redirect it to stdout to get error messages logged to the database. The Pre- and Post- exec commands for an object must be located on the host where the Disk Agent is running. The Pre- and Post- exec commands must be executable and must be specified with the full pathname. You can override any Pre- or Post- exec commands specified for objects or datalists by specifying them with the OB2PREEXEC and OB2POSTEXEC variables in the global options file.
OmniBack II Global Options File

OmniBack II uses the Global Options le for advanced conguration settings. Normally you do not need to modify this le, but occasionally you can achieve different functionality if you modify some parameters. The description of all variables is in the le itself. The global options le /etc/opt/omni/options/global is an ASCII le. Using a text editor, you need to uncomment the appropriate option and set the value.

When you update to a new version of OmniBack II, the global options you have are not overridden. The new global options are documented in the newconfig directory tree.
E l 3s 11 s# E) 1 Q#)EgF# g s#v Es

7-13
Managing Failed Backups

Recovering a failed backup is closely related to how OmniBack II runs full and incremental backups. Incremental backups always depend on the last full backup. If there is no full backup, OmniBack II will perform one even if an incremental backup is scheduled - you cannot have an incremental backup without a prior full backup.
Retry Host Backup Procedure

If you choose to back up several hosts and OmniBack II cannot access one of the hosts at runtime, OmniBack II will try to back up the failed host once more after a successful backup of the other hosts. The retry is performed only 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 the connect( ) system call has failed.
OmniBack II will NOT perform the retry backup in the following situations: Either Omniback II inet executable or vbda executable are not installed. Wrong version of OmniBack II (vbda) is installed on the hosts in a cell. All other cases in which the connect( ) system call has succeeded.
7-14
1 #) 1 11# SQ#)E#sF# Q gv Es
Failed Host Backup

During a backup operation, it can happen that a host is down or unavailable due to maintenance or other problems. OmniBack II retries to back up the host once (see the previous section). If this fails, the host will not be backed up. This results in the following: If a full protected backup exists, an incremental backup will be started next time the host is scheduled for backup. If a full protected backup does not exist, a full backup will be started next time the host is scheduled for backup.
This ensures the completeness of the data backed up. Note that if you have congured infrequent scheduled backups, there may be a 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 interactively when hosts are available. See Running Interactive Backups on page 4-20 for instructions.
Restarting Failed Backup Objects

During a backup session it may happen that some backup objects are not backed up successfully. OmniBack II provides a simple way to restart the backup of failed objects.

Sessions with status running or completed or the backup of a barlist cannot be restarted.
Using GUI: 1. From the Monitor window, select View Previous SessionsSelect Sessions/All Sessions . 2. If you select the Select Sessions options, you must select the criteria of
7-15
1 #) # 1 11# Q#)EgF# g s#v Es
3. Select a failed session and choose Actions Restart Unsuccessful Backup. 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 the session ID of the datalist backup session.
$ omnidb -session -datalist MIKI -latest SessionID Type Status User.Group@Host ================================================================== 1996/01/08-12 Backup Completed/Failure root.sys@ik01.rep
7-16
1 #) 1 11# SQ#)E#sF# Q gv Es
datalists you want to view in the Select Previous Sessions window.
2. To list all objects and their status of the backup session:

$ omnidb -session 1996/01/08-12 Object Name Object Type Object Status ================================================================== kpp3.rep:/users1 'REP' FileSystem Completed kpp2.rep:/users/frenk 'REP' FileSystem Completed mdd56.rep:/users 'REP' FileSystem Failed trblexll.rep:/home 'REP' FileSystem Failed waikik.rep:/C 'REP' FileSystem Completed
3. To selectively restart failed objects only:

$ omnib -datalist MIKI -select mdd56:/users 'REP' trblexll:/home 'REP'
1 #) # 1 11# Q#)EgF# g s#v Es

7-17
Detection of CDF Files

OmniBack II can detect CDF (Context Dependent Files) on cluster server systems. Since this often consumes time, you can disable this detection to improve overall backup performance, especially for large lesystems with a number of small les. Detection of CDF les can be selectively enabled/disabled on a per-host basis. HP-UX 10.x no longer supports CDFs so the CDF detection/backup is disabled. HP-UX 9.0x supports the CDF detection/backup. It can be disabled on a specic host by specifying the following line in the /usr/omni/.omnirc le on that host:
OB2NOCDF=1
Note that ALL backup Disk Agents running on that host will receive this option and disable the CDF detection/backup. We recommend disabling the CDF detection/backup on all hosts in a cell EXCEPT on servers of diskless cluster systems or any other hosts that are likely to have CDF les.
7-18
) C31 SQ#)E#sF# Q gv Es
OmniBack II and Veritas File Systems (VxFS) on HP-UX 10.x

OmniBack II supports the VxFS online backup feature. For more information on VxFS functionality, see your system administration manuals.
Concepts
VxFS allows you to back up a lesystem while it is being used by some other application. This is called an online backup and is done by creating a snapshot of a lesystem and backing up this snapshot. A snapshot of a lesystem is created when you mount the VxFS lesystem to a temporary directory. At this point you also specify the lesystem you want to snap. You congure a backup of this temporary directory, which actually is a mount point to the snapshot of the lesystem as it was at the moment of mount. When the backup is nished, you unmount the snapshot lesystem so that it can be used for other purposes. Note that you can perform normal backups without using the VxFS snapshot feature by simply conguring backup as for any other lesystem. If you want to use the VxFS snapshot feature, you must congure a backup as follows. 1. You must have an empty or unused partition created in your host that can be used by VxFS for a snapshot. See your system administrators manual for instructions. 2. Create a temporary directory to which you will mount the snapshot filesystem.
7-19
#l v)11v E kE E #l1# E#) 1 Q#)EgF# g s#v Es
3. Create shell scripts to mount and unmount the snapshot filesystem to the temporary directory. See Script Templates on page 7-21 for templates of these scripts. 4. Configure a backup of the temporary directory. The mount script must be specified as the Pre- exec command, and the unmount script as the Postexec command.
Improved Backup Performance

VxFS on HP-UX provides the specic option -direct I/O - that instructs the Disk Agents to bypass the UNIX buffer cache mechanism and transfer data directly to/from a disk, which improves the I/O performance. You can set the -direct I/O - option by assigning the following environment variable OB2VXDIRECT value <>0.
Limitations
1. It is possible to restore VxFS to HFS and HFS to VxFS, except in the following cases: VxFS does not support ACLs; therefore, on restores from HFS to VxFS this information will be lost. With VxFS it is possible to define different extent attributes and allocation controls for each file. OmniBack II recognizes and stores this information and restores it back during restore. When restoring to an 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 filesystem depends on how busy the snapped filesystem is when the backup is run. The recommended size is up to 15% of the snapped filesystem, if the filesystem is in heavy use during the backup. Normally, the size will be
7-20
#z v)11v b # Q b b S11# b#) 1 SQ#)E#sF#QQ gv Es
around 5%. If the amount of data modied on the snapped lesystem is higher than the space available, OmniBack II produces Cannot stat error messages for all the remaining les to be backed up. You must unmount the snapshot lesystem and repeat the backup procedure.
Restoring
Since you have backed up the temporary directory with the snapshot lesystem mounted and not the original directory, you must restore the les to the original directory using the Restore As option.
Script Templates
Here is a template that can be used to mount the VxFS lesystem.
# # # # # # # # # # # # # # # # # # # # # # # # # # # # # 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.
#l v)11v E kE E #l1# E#) 1 Q#)EgF#Qg s#v Es

7-21
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
7-22
#z v)11v b # Q b b S11# b#) 1 SQ#)E#sF#QQ gv Es

SNAPPED_FS=$1 SNAPSHOT_FS=$2 MOUNT_POINT=$3 mount -F vxfs -e -o snapof=$SNAPPED_FS $SNAPSHOT_FS $MOUNT_POINT # # end SnapMount.sh # exit $? MOUNT_POINT=$1 umount -v $MOUNT_POINT # # end SnapUnmount.sh # exit $?
OmniBack II and HP Enterprise File System on HP-UX 10.x

OmniBack II supports the HP-UX version of the DCE Distributed File System (DFS) called the HP Enterprise File System (EFS). For a list of supported versions, see HP OpenView OmniBack II Software Release Notes. Note the following when conguring backup of an HP EFS or DFS: 1. In the DCE environment, create a special OmniBack II DCE principal (user), by default OmniBackII. This principal must have the rwxcid ACL entries for all the files and directories to back up and a keytab password entry in a local keytab file. If you want to use some other name than OmniBackII, specify the name in the OB2DCEPRINCIPAL variable in the .omnirc file on the DCE host you want to back up. If the principal is user root, no additional ACL settings are needed, but you still need a keytab password. 2. When configuring backup of a DCE host with HP EFS, you must manually enter the mountpoint for the HP EFS as /... since this mountpoint is not visible using the browse button. 3. Manually enter the UNIX and DCE junction point to the Files and Directories list in the Filesystem Backup window. Usually, this junction point is /.../cell_name/fs. This avoids generation of minor errors during 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 detected by OmniBack II.
#l v)1n# kE S )1# E#F lm Q#)EgF#Qg s#v Es

7-23
Deleting a Session
HP OmniBack II keeps track of how long data on a medium is protected (see Using Backup Options on page 4-26 for more information). When the protection expires, the session will be overwritten by the newer backups. OmniBack II provides a way to delete unwanted sessions from the database. 1. From the Monitor window, select View Previous Sessions. 2. Select a session you want to delete and choose Actions Purge Session. The session disappears from the list. The following happens: Protection is removed from the session. This means that the session will be 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 next backup. Therefore, you can still see or restore the session using option List from Media.
7-24
1 vE1 # SQ#)E#sF#QQ gv Es
Copying Media
OmniBack II offers the efcient duplicating of backup sessions to a second set of media. In this way, OmniBack II provides reliable support for vaulting/archiving backup sessions. To copy media follow the these steps: 1. In the HP OmiBack II - Main window, select the Devices&Media icon to open the HP OmiBack II - Device & Media Management window. 2. In the HP OmiBack II - Device & Media Management window, select one of the configured media pools below to open the Media Management window.
Figure 7-3
Copying Media
1 1 ) Q#)EgF#Qg s#v Es

7-25
3. From the menu in the Media Management window, select a medium and click EditCopy to open the Media Management - Medium Copy window 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 media belonging to that particular session, to one target medium or a set of target media. Media can be copied only to another media of the same media class. The copy preserves the media's multiplexed layout, catalogs, and object position information. Target media is checked as for init. You can copy media over the network, and view the copy session in the OmniBack II session monitor. A single copy session operates from a single source device to a single target device. Multiple media can be copied sequentially in a single copy session, but only one medium at a time (no parallelism). The target medium that has OmniBack II format can have different set of medium attributes (medium ID, label, location, protection etc.) from the medium attributes of the source medium. All media which are created as replicas of source OmniBack II media will be visible in the OmniBack II media management GUI as standalone media 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 is marked as full to prevent accidental appending during the lifetime of the copied data. If some other data has been appended to the source medium after it has been copied, the target medium is still regarded as a replica of the source medium, but it is not a 100% match. The target medium cannot be used to append data stored onto the source medium after the copying.
7-26
1 1 F SQ#)E#sF#QQ gv Es
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 target set 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 from a non-target set as a substitute. In the Mount Request of a restore session, the original medium and a list of 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 Specics: 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 two possibilities: Import is denied (default). You are allowed to import a copy with the -force option of omnimm, but if other copies exist, they cannot be imported later.
1 1 ) Q#)EgF#Qg s#v Es

7-27
Modifying Device and Media Management View

You can customize the media view in the Device & Media Management window by changing the variables in the global options le. 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 be displayed in the libray or media management view by specifying the corresponding string variables. See Global Options le for description of variable strings.
7-28
Q #11# 1 1#b# 1 U 11 SQ#)E#sF#QQ gv Es
Disaster Recovery
There are a few simple rules you can follow to be sure that disaster recovery is as smooth and simple as possible: Make a backup of your Cell Server files and the files of other hosts on a regular basis. This ensures that you can always restore up-to-date data and thus allow users to continue their work normally. Make a full disk backup of all important hosts in your cell on a regular basis. This allows quick recovery from a disk disaster. Perform a backup of the OmniBack II databases each night to ensure that you can restore the last state of the databases. If possible, configure the database backup on a separate logical device, for example, a standalone DDS. This simplifies recovery of files in the event of a Cell Server disaster.
Improved Disaster Recovery

OmniBack II provides much faster recovery of all data. For example, if a backup was made with concurrency 4, which means that four backup objects were simultaneously backed up on a single device, OmniBack will also restore objects with concurrency 4. This will result in four times faster recovery. 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.
3)v# Q Q#)EgF#Qg s#v Es

7-29
Preparing For a Disaster

A disk disaster on any host is probably one of the most severe problems that can 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 operating normally. In this case, you only need to restore the corrupted or missing files. You can do this easily using OmniBack II restore. A client host has suffered a major disk disaster and is no longer operating properly. See Recovering a Client Host on page 7-30 for instructions. A Cell Server host has suffered a major disk disaster and is no longer operating properly. See Recovering a Cell Server on page 7-31 for instructions.
Recovering a Client Host

When you need to recover the root disk of your host, you may follow one of these two methods: 1. Install a new disk on another host and restore the complete backup 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. 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-30
#3#)v SQ#)E#sF#QQ gv Es
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 DDS tape. 3. Reinstall the operating system. Refer to your system administrators manual for instructions. 4. Reinstall OmniBack II client modules as they were before the disk disaster. See Chapter 2, Installation Overview on page 2-1 for instructions. 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 page 5-1 for instructions. Your client host should be successfully recovered.
Recovering a Cell Server

Recovering a Cell Server after a major disk disaster includes some additional steps. This procedure is also applicable in case your complete Cell Server is destroyed by some accident. When you need to recover the root disk of your cell server host, you may follow 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-31
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 DDS tape. 3. Reinstall the operating system. Refer to your system administrators manual for instructions. 4. Reinstall the OmniBack II software on the Cell Server. See the HP OpenView OmniBack II Installation Guide for instructions. 5. Restore the latest backup of your database. This simplifies the restore of all other files from media. Note that you cannot restore the database directly. See Restoring the Database on page 8-14 for instructions. 6. Stop running all OmniBack II processes with the omnisv.sh -stop command. 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 previous configuration. 8. Start OmniBack II processes with the omnisv.sh -start command. 9. Start the graphical User Interface and restore all other files from your backup. 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 and recover a mission critical host, such as an OmniBack II Cell Server. This example automates the recovery process.
7-32
This example uses unsupported scripts provided by OmniBack II. An operating system and all mission critical applications (OmniBack II Cell Server) are installed on the same disk (same volume group). The OmniBack II software, including the Cell Server, Disk Agents, and Media Agents is installed on the host. You will need a new disk of the same size and with the same partition configuration 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 one volume group and on the same physical disk, for example, vg00. 2. Print out the information about the volume group configuration. For each logical 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 and Using Logical Devices on page 3-21 for instructions. 4. Initialize and label the medium you will use for backup, for example CRITSYS_OB2. See Media Management Tasks on page 3-27 for instructions. 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 with critical applications). These files must be exluded so that they are not overwritten during restore. See Understanding Datalists and Barlists on page 4-3 for more information. Print out the datalist and save the printout. 6. Run a backup of this datalist and remember the sessionID. 7. Run the /opt/omni/sbin/utilns/omnipfr.ksh sessionID script. This saves all OmniBack II relevant information to the /OB2RECOVERY directory.

7-33
8. Back up this directory to an empty DDS medium and label it using the tar command, for example, OB2RECOVERY_tar. Do NOT run this on the DDS used in previous steps.
cd /OB2RECOVERY tar cvfh device
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 tape and use the printout of the volume groups to reconfigure the logical volumes. 3. Open file /etc/hosts and find the line with the hostname of your system and add its full name. 4. Insert the tar formatted recovery DDS tape (OB2RECOVERY_tar) in the device and run:
cd / tar xvf device
5. Insert the OmniBack II formatted DDS with the backup of the whole
7-34
This creates a recovery tape with the OmniBack II software needed for restore.
This installs back all the OmniBack II software needed for recovery of the system.
system (CRITSYS_OB2) and run:

/omnirecover.ksh device
This restores all les in their places. If a le is busy, it is rst renamed #filename and then the original le is restored. 6. Reboot the system. All les that were backed up are now restored except for the excluded les. Some les, however, still differ: the les that were created during the installation of the operating system but were not on the recovery tape are removed. 7. Restore the OmniBack II database. See Restoring the Database on page 8-14 for instructions. Now you can restore all other les from previous OmniBack II backups.

7-35
Moving a Cell Server

Sometimes you may need to move the Cell Server to another host. This section explains how to move a Cell Server if it is running properly. In case of a system disaster, refer to the Disaster Recovery on page 7-29 section rst. Be sure that you prepare carefully for this task. 1. Decide which host will be the new Cell Server and install it as a Cell Server - see the HP OpenView OmniBack II Installation Guide for instructions. Note that you must request to move your licenses to the new Cell Server. 2. Make a backup of your cell. 3. Make a backup of your database - see Backing Up the Database on page 8-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 the omnistat command to check this. 2. Export all hosts from the cell. See Exporting Hosts from a Cell on page 2-8 for instructions. 3. Exit the Graphical User Interface. 4. Run the omnisv.sh -stop command to stop all OmniBack II processes. On the new Cell Server (which must be already installed), perform the following: 1. Move the/etc/opt/omni/ directory to a target host.
7-36
# #)b1 3 SQ#)E#sF#QQ gv Es
2. Recursively copy the/etc/opt/omni/ directories from the old Cell Server 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 the omnicc command to update the configuration. 5. Run the Graphical User Interface and import all hosts. See Importing Hosts to a Cell on page 2-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 all its appearances from the configured datalists.
##v )bml 3 Q#)EgF#Qg s#v Es

7-37
MC/ServiceGuard and OmniBack II

HP OpenView OmniBack II supports the MC/ServiceGuard software product provided for effective recovery of a particularly valuable host in case of a system disaster. This section provides an explanation of supported functionality, limitations, and instructions for conguration.

Instructions here are given as general guidelines only. We recommend that you rst get familiar with MC/ServiceGuard by creating and testing 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 on how to install OmniBack II. HP OpenView OmniBack II Software Release Notes for last minute information 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 Cell Server, called a Secondary Cell Server, which can be used instead of the Primary Cell Server. In order to do this, the Cell Server software is viewed as a specic application that can be migrated to the Secondary Cell Server in case of a problem with the Primary Cell Server. When MC/ServiceGuard detects problems with the Primary Cell Server, it migrates the whole Cell Server Package to the Secondary Cell Server. Therefore, both Cell Servers must have fully installed and congured versions of OmniBack II. Note, however, that the Secondary Cell Server cannot be used as the Cell Server of some other cell at the same time.
7-38
b#) 1 1#1s# Sl SQ#)E#sF#QQ gv Es
If a failure of the Primary Cell Server occurs while a backup is running, the backup will fail for the currently backed-up host and all others that were scheduled for backup after this host. However, a complete OmniBack II operation is now running on the Secondary Cell Server where you can start an interactive backup of the failed hosts.
Prerequisites for Configuration

Before you start conguring OmniBack II with MC/ServiceGuard, check the following: Decide which hosts are going to be the Primary Cell Server and the Secondary Cell Server. See HP OpenView OmniBack II Installation Guide for more information how to choose an appropriate host. Hosts chosen to be the Primary Cell Server and the Secondary Cell Server must have MC/ServiceGuard installed and must be configured as cluster members. See Managing MC/ServiceGuard for instructions. Hosts chosen to be the Primary Cell Server and the Secondary Cell Server must have HP OpenView OmniBack II Cell Server software installed. See HP OpenView OmniBack II Installation Guide for instructions. Note that a permanent license must be installed on the Primary Cell Server.
Configuring Primary and Secondary Cell Servers

This section provides general guidelines only. For more detailed instructions, refer to the Managing MC/ServiceGuard manual. On the Primary Cell Server: 1. Set up the /dev/vg_ob2cs volume group on a shared disk accessible to both 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.
b#) 1 1#1s# Sl Q#)EgF#Qg s#v Es

7-39
4. Modify the /etc/opt/omni/cell/sg.conf template file. You must change the SHARED_DISK_ROOT variable if you have configured some other shared directory and the CS_SERVICE_HOSTNAME variable. This variable tells OmniBack II the name of the Primary Cell Server. The default name is ob2cs.net.domain. You must change the net.domain to match your network. 5. Run /opt/omni/sbin/install/omniforsg.ksh -primary to configure 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 to configure the Secondary Cell Server. 4. Unmount the /omni_shared directory. 5. Deactivate the /dev/vg_ob2cs volume group.
Configuring the Cell Server Package

This section provides general guidelines only. For more detailed instructions, refer to the Managing MC/ServiceGuard manual. 1. Generate, modify, and distribute the package control script. Be sure that you provide the following information:
/dev/vg_ob2cs/lv_ob2cs must be mounted as /omni_shared
7-40
b#) 1 1#1s# Sl SQ#)E#sF#QQ gv Es
The service command must be

/etc/opt/omni/sg/csfailover.ksh start
The IP address must be the address associated with the relocatable hostname (ob2cs.net.domain)
2. Generate, modify, and distribute the cluster and package configuration scripts.
Starting the Cell Server

This section provides general guidelines only. For more detailed instructions, refer to the Managing MC/ServiceGuard manual. 1. Halt the cluster. 2. Modify and distribute the cluster configuration file. If you are already using MC/ServiceGuard, this file already exists. Otherwise, you must create it. 3. Start the cluster. 4. Hand over control of the volume group /dev/vg_ob2cs to MC/ServiceGuard using the vgchange command. See manpages for details. 5. Be sure that switching of the OB2SG package is enabled. See manpage for the cmmodpkg command for details. 6. When the Primary Cell Server is restarted, proceed with the installation of OmniBack 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 II GUI on it, you must run the following command on the Secondary Cell Server:
mkdir -p /omni_shared/etc_opt_omni/cell
Now you can import the host to your OmniBack II cell conguration, distribute the Disk Agent, and congure the host like any other client.
b#) 1 1#1s# Sl Q#)EgF#Qg s#v Es

7-41
OmniBack II Web Based Reporting

OmniBack II provides full Web reporting integration. You can view reports and congure report criteria using a Web interface.

Web Browsing can be used on a host with the OmniBack II User Interface. Before viewing or conguring reports, you must integrate OmniBack II reporting with Netscape Fasttrack Server. See Integrating OmniBack II Reporting with Netscape Fasttrack Server on page 7-43.
To view or congure reports, perform the following steps: 1. Start WWW browser and point your browser to the following location: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 to save customized reports for later use. For example, display infomration about 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 be used later to create the same report as pure ASCII text usinng the command line interface. OmniBack II provides WWW integration for Netscape Fasttrack Server, but integration with other Web servers that support Common Gateway 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 nights backup.
7-42
1 l ) ) b#) 1 SQ#)E#sF#QQ gv Es
Integrating OmniBack II Reporting with Netscape Fasttrack Server

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 the OmniBack II Installation Guide and online help
Using Provided Reporting Scripts

After you specify and submit the report criteria in the OmniBack II WWW Report Menu, OmniBack II will start a script and compose the WWW output. Scripts enable you to view only essential information, and they point out possible 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 your requirements. Customized (pre-set) report options offer fast access to the most common reports. 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 in the WWW output. Reporting scripts can be scheduled using cron or be used as OmniBack II backup session post-exec scripts to mail or save the
1 1 )# )#Q E#) 1 Q#)EgF#Qg s#v Es

7-43
reports. For example, reports on hosts not used by OmniBack II can be mailed to the administrator every week so that he can take appropriate actions.
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-44
1 l ) ) b#) 1 SQ#)E#sF#QQ gv Es
Customizing the Encryption Algorithm

To increase the security of your backup media, you can enable the encrypt option using the Backup options window. This backup option writes data to the media in an encrypted form. Media encrypted using the HP OmniBack II encryption option can only be read 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 encryption code module, compile the module, and link it to the standard HP OmniBack II encryption library. This library is called libde.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 own encryption module. For detailed information about developing Unix code, please consult the HP-UX Programming Manual.

If you change the encryption algorithm, OmniBack II will no longer be able to deencrypt data from backups performed with the previous algorithm. If this occurs, OmniBack II will restore the data in encrypted form. Therefore, it is recommended that you only change the algorithm after careful planning. Frequent changes to the encryption algorithm increase the risk of data loss! To restore a backup created using a different encryption algorithm, you must rst restore the version of the encryption algorithm that was used to create the backup set you want to restore.
Creating an Encryption Code Module

This section provides an overview of the process for developing your own code module for encryption. For more detailed information, please consult the HP-UX Programming Manual.
11 )1 3 #1 7 1 1 ) Q#)EgF#Qg s#v Es

7-45
Creating and installing a new encryption code module involves the following 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 Disk Agents, 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 DE_XOR 1 no encryption simple XOR encryption
The following list briey explains each function used and its purpose. dene DeInit DeEncrypt DeDecrypt DeExit identies the encryption type initializes the encryption module performs the encryption performs the deencryption exits the encryption module
The encryption module is shown with an explanation of the functions in the module. The module denes unique data encryption type identiers.
#if !defined(UCHAR) #define UCHAR unsigned char #endif #if !defined(ULONG) #define ULONG unsigned long #endif
7-46
11 )1 3 #1 1 1 F SQ#)E#sF#QQ gv Es

#define DE_NONE 0 /* No data encryption */ #define DE_XOR 1 /* Simple XOR encryption */
#define DE_DES
/* DES encryption (not impl.) */
MODULE Data Encryption (De) FUNCTION

extern ULONG DeInit ( #if PROTOTYPES void #endif );
ARGUMENTS void RETURNS DE_NONE DE_XOR DE_xxxx DESCRIPTION This function is called by the Disk Agents initialization procedure at startup. It initializes the data encryption module and retrieves the encryption key from a le or key server. REMARKS The distribution of the encryption key through a network is a complex issue and not within the scope of a backup/restore application. This function can read a key from a predened le or contact a key distribution server (via RPC) to obtain a key. MODULE Data Encryption (De) Initialization failed, encryption disabled Initialization successful, xor encryption Customer-created & implemented encryption type, where nnnn represents a customer-supplied name
11 )1 3 #1 7 1 1 ) Q#)EgF#Qg s#v Es

7-47
FUNCTION
extern int DeEncrypt ( #if PROTOTYPES UCHAR *data, ULONG size #endif );
ARGUMENTS data size RETURNS 0 1 DESCRIPTION The encryption of plain text should be done in-place. OmniBack II expects the size of the data buffer to be maintained and the contents to be overwritten with the encrypted text.

The encryption algorithm must generate encrypted text of the same length as the original text.
MODULE Data Encryption (De) FUNCTION

extern int DeDecrypt ( #if PROTOTYPES UCHAR *data, ULONG size #endif );
ARGUMENTS data size pointer to encrypted text buffer size of encrypted text buffer
7-48
11 )1 3 #1 1 1 F SQ#)E#sF#QQ gv Es
pointer to plain text buffer size of plain text buffer
Error OK
RETURNS 0 1 DESCRIPTION The encryption of the encrypted text should be done in-place. OmniBack II expects that the size of the data buffer will remain the same and that the contents will be overwritten with the encrypted text. MODULE Data Encryption (De) FUNCTION
extern int DeExit ( #if PROTOTYPES void #endif );
Error OK
ARGUMENTS void RETURNS 0 1 DESCRIPTION This function is called to allow the data encryption module to perform a post-processing cleanup. Its return value is ignored. Error OK
11 )1 3 #1 7 1 1 ) Q#)EgF#Qg s#v Es

7-49
Customizing the Compression Algorithm

To reduce the number of media needed to perform a backup, you can enable the compress option using the Backup options window. The compression used by OmniBack II is the Lempel-Ziv 4.3 compression algorithm. This is the same compression algorithm used by the Unix compression utility and provides reasonable compression and speed for most data types. However, you may choose to implement another compression algorithm, customized for your type of data. Customizing the compression algorithm may provide better performance for the backup and restore of specic 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 own compression code module, compile the module, and link it to the standard HP OmniBack II compression library. This library is called libdc.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 own compression module. For detailed information about developing Unix code, consult the HP-UX Programming Manual.

If you change the compression algorithm, OmniBack II will no longer be able to decompress data from backups performed with the previous algorithm. If this occurs, OmniBack II will restore the data in compressed form. Therefore, it is recommended that you only change the algorithm after careful planning. Frequent changes to the compression algorithm increase the risk of data loss. To restore a backup created using a different compression algorithm, you must rst restore the version of the compression algorithm that was used to create the backup set you want to restore.
7-50
11 )1 # 1)E 1 1 F SQ#)E#sF#QQ gv Es
Creating a Compression Code Module

This section provides an overview of the process for developing your own code module for compression. For more detailed information, consult the HP-UX Programming Manual. Creating and installing a new compression code module involves the following 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 Disk Agents, 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 identiers used in the compression module are shown here: No data compression DC_LZ43 0x0b0b0b0b Lempel-Ziv 4.3
DC_NONE 0
The following list briey explains each function used and its purpose. DcInit DcCompress DcDecompress DcExit initializes the compression module and returns the compression type the compression function the stream decompression function performs post-processing cleanup
The following section shows the data compression modules, with an explanation following each function.
11 )1 1FE 1 1 Q ) Q#)EgF#Qg s#v Es

7-51
The module denes unique data encryption type identiers.

#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 ULONG DcInit ( #if PROTOTYPES void #endif );
ARGUMENTS void RETURNS DC_NONE DC_LZ43 DC_xxxx DESCRIPTION This function is called by the Disk Agents initialization procedure at startup. It should initialize the Data Compression module and indicate the compression type. REMARKS Dynamic switching between different compression algorithms depending on the type of input data is not available. Initialization failed, compression disabled Initialization successful, Lempel-Ziv compression a customer-created and implemented compression type, where xxx represents a customer-specied name
7-52
11 )1 # 1)E 1 1 F SQ#)E#sF#QQ gv Es

extern int DcCompress ( #if PROTOTYPES dcCallback dcCallback #endif );
readCallback, writeCallback
ARGUMENTS readCallback writeCallback RETURNS 0 1 DESCRIPTION This is the actual stream compression function. Input is received from the readCallback function and output is written using the writeCallback function. Note the following guidelines when modifying this function: The compression module cannot detect the type of input and output media. Therefore, the input should be treated as a read-only stream and the output should be treated as a write-only stream. The DcCompress function is called once for each file to be compressed. It reads the input until EOF (the input handler returns a value of zero) and makes sure that all the intermediate output buffers are flushed before it sends a return value. Each call to the readCallback is directly translated into a read() system call. Therefore, for better performance, the compression engine should read its input in large chunks and store them in an internal input data buffer. The readCallback function returns the number of bytes read. This number can, under certain circumstances, be less than the number of bytes actually requested. The compression engine should not treat this as an Error OK A pointer to the data input callback A pointer to the data output callback
11 )1 1FE 1 1 Q ) Q#)EgF#Qg s#v Es

7-53
The readCallback return values are: >0 0 Number of bytes read Error or EOF
The writeCallback return values are: >0 0 REMARKS Never call the readCallback to read or write zero bytes, as the return value will be zero which means "Error or EOF." MODULE Data Compression (Dc) FUNCTION
extern int DcDecompress ( #if PROTOTYPES dcCallback dcCallback #endif );
ARGUMENTS readCallback writeCallback A pointer to the data input callback A pointer to the data output callback
The return values are: 0 1 Error OK
7-54
11 )1 # 1)E 1 1 F SQ#)E#sF#QQ gv Es
error but simply issue a second read (this is similar to BSD sockets, reads may succeed partially). The readCallback returns a value of zero when an error occurs or at EOF. The writeCallback function always sends a return value. If an error occurs, the writeCallback return value is zero.
number of bytes written Error
readCallback, writeCallback
DESCRIPTION This is the actual stream decompression function. It receives its input data using the readCallback data input function and writes its output using the writeCallback output function. Note the following guidelines when modifying this function: The nature of the input and output media is unknown to the decompression module. Therefore, the input should be treated as a readonly stream and the output should be treated as a write-only stream. The DcDecompress function is called once for each file to be decompressed. It reads its input until EOF (the input handler returns zero) and checks that all intermediate output buffers are flushed before it sends a return value. Both input and output can be done in byte chunks of arbitrary length. The readCallback function returns data from an internal OmniBack II data buffer. However, for the best performance, it is recommended that output be sent in larger chunks, since calls to the writeCallback function can be directly translated into write() system calls. The readCallback function can partially succeed. A return value of zero denotes either an error or the end of the current file being decompressed. The writeCallback function always succeeds completely and never reports any errors back.
The readCallback return values are: >0 0 Number of bytes read Error or EOF
The writeCallback return values are: >0 0 REMARKS Never instruct the readCallback function to read zero bytes, because this results in a return value of zero, which means "Error or EOF." For the same reason, never attempt to write zero bytes. Number of bytes written Error or EOF
11 )1 1FE 1 1 Q ) Q#)EgF#Qg s#v Es

7-55

extern int DcExit ( #if PROTOTYPES void #endif );
ARGUMENTS void RETURNS 0 1 DESCRIPTION This function allows the data compression module to perform postprocessing cleanup actions. Its return value is ignored. Error OK
7-56
11 )1 # 1)E 1 1 F SQ#)E#sF#QQ gv Es
Maintaining the OmniBack II Database
8-1
In This Chapter This chapter describes how to maintain and back up the OmniBack II database. 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 three tasks: 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-2
#S) s#v EsESF # #SQ #
Installing and Configuring the Database

The OmniBack II database is installed to the /var/opt/omni/db directory on 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 about backup devices and their conguration and media used for backup. Catalog Database: Stores information about data backed up such as les, directories, versions, and so on.
CDB
In an ordinary, single cell environment, both parts of the database are located on the same Cell Server. In a multi-cell environment enabled with the Advanced Backup Manager license, you can congure a common MMDB database for many cells. See HP OpenView OmniBack II Advanced Backup Manager for more information.
l# 1 11C31)11 Q #SF# s#v EsESF #SQ

8-3
Managing the Growth of the Database

The CDB is the largest part of the database and occupies approximately 8085% of the database. The fvers.dat le is the largest le of the CDB and e is located in the /var/opt/omni/db/cdb directory. OmniBack II uses the size of the fvers.dat le to calculate the size of the database. A general estimate for the size of the database is approximately 2% of the data being backed up. Thus, if the data is 100GB, the database will occupy approximately 2GB. It is possible to enlarge the size of the database. See Enlarging the Size of the Database on page 8-10 for more information.

Be sure that you have enough free space on a disk for the database. If the database runs 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 the following 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 the database the protection of backup information about backed-up data in the database the number of backup and restore sessions
8-4
1# v 7 3gb 1 11# #S) s#v EsESF # #SQ #
Estimating the Size of the Database This section provides an example how you can calculate the size of the OmniBack II database based on the number of les and directories you back up. The basis for this calculation is that for each le or directory backed up, the full backup information about each occupies approximately 60 bytes. Let us assume 50 workstations each with approximatelly 40000 les. We do a weekly full backup and daily incrementals and we keep 6 full backups (protection is set to 6 weeks). The estimated size of the incremental backup information 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 = full database size Therefore, the estimated size for the database is 840MB. If this number is too high, check the following sections for information on how to reduce this number. Changing the Number of Logged Messages The level of detail recorded in the database relates to the Report Level and the le logging of the backup options. If you set the Report Level to warning, all screen messages at the warning level and higher are recorded in the database. The number of messages recorded will be higher than if you set the Report Level to critical. See Selecting the Filesystem Backup Options on page 4-11 and Selecting the Rawdisk Backup Options on page 4-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 les and directories stored in the database. Log All This is the default option. All backed-up les are logged to the database. This complete information allows you to search for backed-up les and allows OmniBack II to fast position on the tape when restoring a specic le.
8-5
l# 3 3sE 1 1#1 #SF# s#v EsESF #SQ
Log Directories Details on directories only are stored in the database. This limits the search feature during restore and you will only be able to browse directories. However, OmniBack II still performs fast positioning because a le is located on the tape near the directory where it actually resides. This option is suitable for lesystems with many autogenerated les, such as news and mail systems where you usually do full restores. No Log No details on les or directories are logged in the database. You will not be able to search and browse les and directories. The restore will take longer because OmniBack II cannot fast position on the tape and will read from the start of the backup.
See Selecting the Filesystem Backup Options on page 4-11 and Selecting the Rawdisk Backup Options on page 4-15 for instructions.
Changing the Protection of Backup Information OmniBack II allows you to set protection (see Using Backup Options on page 4-26 for more information) both for data backed up and backup information about data in the CDB. This is also called catalog retention. You can therefore specify that backup information be kept in the database for a limited time only, for example, as long as the data is protected. OmniBack II automatically removes backup information with expired protection from the database, 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 and restore sessions. A schedule with frequent full backups will result in the faster growth of the database.
8-6
1# v 7 3gb 1 11# #S) s#v EsESF # #SQ #
However, this information may take a lot of space if there are many les.
Purging Obsolete Data from the Database

OmniBack II automatically removes obsolete information from the CDB at regular time intervals. Purging removes unneeded information from the database and frees space for new information. Note that by purging the CDB you do not actually shrink the size of the les - you only make space for new information. The following variables in the global options le inuence the behavior of the automatic purge process: DBPurgeSuspension If it is set to 1 (default), purge session manager will suspend its execution while backup/restore sessions are in progress. Species the database purge options; when old aborted sessions and obsolete les may be removed. Species the purge session start times
DBPurgeOptions
DBPurgeStartTime To Purge Manually
The following command purges information relating to restore sessions as well as obsolete (overwritten) backup sessions and sessions without any media such as failed or aborted sessions.
omnidb -purge
OmniBack II records detailed data such as the names of each le being backed up during each session in the CDB. You can create space for new data by removing this data from the CDB. You can remove detailed data for a backed-up object in one specic backup session. The restore of single les will be slower since OmniBack II has to search from the beginning of the media for the le. You can mark detailed data for removing by using the omnidb -strip command with various options. See the omnidb manpage for a complete description of the command options. Example:
8-7
omnidb -strip
marks the details catalog of all objects with expired protection. If you combine this command with -session sessionID, all objects (lesystems) backed up in the specied session are marked. If you combine this command with -session sessionID and filesystem filesystemID, the specied lesystem in the specied session is marked. If you combine this command with days -filesystem filesystemID, all versions of the specied lesystem older than days are marked.

These commands do not actually delete data from the database, but just mark the data for deleting. Data is actually removed from the database when the automatic purging happens or by manually running the omnidbutil -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 page 4-26 for more information). When the protection expires, the session will be overwritten by newer backups. OmniBack II provides a way to delete an unneeded session from the database. 1. From the Monitor window, choose View Previous Sessions. 2. Select the session you want to delete and choose Actions Purge Session. The session disappears from the list. The following happens: Protection is removed from the session. This means that the session will be overwritten during future backups. All detail data (backed-up files and messages) about the session is removed from the database. The session itself remains on the media until it is overwritten by the next backup. Therefore, you can still see or restore the session using the List
8-8
1# v 7 3gb 1 11# #S) s#v EsESF # #SQ #
from Media option.
Shrinking the Size of the Database File

By using the procedures above, you do not really shrink the size of the database; you just remove obsolete or detail data and create more space for new data-. If you really must reduce the size of the database les, the only possible way is to copy the database to an ASCII le and then read it back. To ensure the integrity of the database, be sure that backups, restores, or GUIs are not running before copying the database.
Is it Feasible to Shrink the Database? You can use the omnidbutil -info command to see how many records are actually used and how many are occupied by data. If the numbers vary considerably, it is feasible to shrink the database.
Copying the Database to an ASCII File Before you copy the database to an ASCII le, we recommend running the omnidb -purge command. Use the following command to copy the database to an ASCII le.
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 the omnidbutil command, see the manpage.

For this operation you will need approximately 50% more disk space than the size of your database. This operation may also take considerable time, for example, on an HP Series 800 E35 system, the writeascii of the 500 Mb database may take three hours.

8-9
Reading the Database from an ASCII File Note that by reading the database from the ASCII le you will lose any data written to the database after it was copied to the ASCII le. Make sure that the database is large enough for data in the ASCII le. If needed, use the instuctions in the next section to enlarge the size of the database. Use the following command to read the database from an ASCII le.
omnidbutil -readascii [-mmdb file] [-cdb file] [-no_details]
If you encounter problems with this command, you must rst initialize the database with the omnidbinit command. For more details on the omnidbutil command, see the manpage. If you read the CDB or MMDB individually, you may need to synchronize the content of both databases with the following command:
omnidbutil -cdbsync CDB_hostname
As a result of a database synchronization, protection for some media may change 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 les size limit. If this size is not sufcient for your needs, you can enlarge the size of the database. The procedure creates new, extended fvers.dat les where new data is stored. The maximum size of each new le is 2GB, and the maximum size of the whole database is 8GB. It is important to carefully plan the location of database extension les.
8-10
1# v 7 3gb 1 11# #S) s#v EsESF # #SQ #
Once you dene the extended fvers.dat les, you cannot reduce their size any more.
1. Be sure that no backup, restore, or media management sessions are running in the cell. Be sure that no Graphical User Interfaces are running on the cell. 2. On the Cell Server, run the following command:
omnidbutil -extend pathname -maxsize size
where pathname is the full path to the directory where you want to put the new database les, and size is the size of the database extension le (maximum 2GB). For example:
omnidbutil -extend /var/opt/omni/db/cdb -maxsize 2000
will create an additional database le in the same directory as the original database and extend the size by 2000MB, thus giving a full database size of 4GB. To extend the database even more, repeat the command. OmniBack II creates a new, extended fvers.datN le in the specied directory each time you run the command. The database extension les are backed up as part of the database backup and are restored with database recovery. See Backing up the Database Using a Datalist on page 8-13 and Recovering the Database on page 8-15 for more information.

8-11
Backing Up the Database

The database is an extremely important part of OmniBack II and must be backed up on a regular basis. We recommend the following: Create a separate datalist for the database. This simplifies scheduling and restoring in case of a disk crash. Schedule a database backup every night. This ensures you always have an up-to-date backup of the database. You can set the protection to only a few days. Make the database backup on a separate medium, on a separate device if possible, for example, to a standalone DDS. This greatly simplifies eventual restore, since you know precisely on which medium your database is backed up. Create and use a separate pool for backing up your database. This simplifies the recovery of the database.
The database backup runs online. The database is in use whenever you are using the Graphical User Interface or when a backup or restore session is in progress. OmniBack II provides an automatic action to back up the database that shuts down the database, backs it up, and then restarts it. OmniBack II also maintains the integrity of the database by preventing you from backing up a corrupted database. When you initiate a backup of the database, OmniBack II rst performs a database check. If the database is corrupt, the backup fails. This prevents you from later restoring a corrupted database. The database backup backs up all OmniBack II conguration data, including /etc/opt/omni and /var/opt/omni/db directories and database extension les (see Enlarging the Size of the Database on page 8-10 for more information), not just the database.
8-12
1 7A) 1 ##F #S) s#v EsESF # #SQ #
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 the OmniBack II Backup Editor window, choose Object Add OmniBack II Database to add the database to a new or existing datalist.
Running Backups of the Database Once you have created the datalist for the database, you can schedule the datalist or run an interactive backup. You can use the omnib command with the -datalist option to perform the database backup. See the omnib manpage for details.
l# A) 1 #) #SF# s#v EsESF #SQ

8-13
Restoring the Database

If you have backed up the OmniBack II database using the procedure described in Backing Up the Database on page 8-12, you can recover the database 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:
Graphical User Interface Method To restore the database using this method, you use the normal procedure for restoring single les, except that you use the Fileset Restore Options window to specify an alternative directory for the database. To restore the database, follow these steps: 1. From the OmniBack II Main menu, select Restore to open the OmniBack II Restore window with a list of all the objects which have been backed up. 2. Double-click the OmniDb object to open the Database Restore window.
8-14
1# 1 1 Q F #S) s#v EsESF # #SQ #
You must restore the database from a backup that was created using the method described in the Backing Up the Database on page 8-12. If you try to restore the database from a regular backup, you will corrupt the database! You must restore the database into an alternative directory because the database is in use during any restore session. The -into option is used to specify 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 first shutting down all OmniBack II processes using the omnisv.sh -stop command and then copying all database files to a temporary directory.
3. Choose Actions Restore OmniBack II DB to open the Filesystem Restore window. By default, the database is restored to the /tmp directory. Do not restore the database to the root directory. To select specic restore options, choose Database Restore Options. 4. Choose OK to open the OmniBack II Restore Monitor window where you can start restore. After restore, the complete database directory is restore to /tmp. If you use database extension les, they are also restored to /tmp.
Command-Line Interface Method You can use the -omnidb option to restore the database. The command syntax is shown here:
omnir -omnidb Hostname:Mountpoint [label] -session sessionname -into directory name
If you specied the label when backing up the database, you must specify the 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 use database extension les, they are also restored to /tmp.
Recovering the Database

After you have used the Graphical User Interface method or the commandline method to restore the database, you must copy the restored database from the alternative directory back to the original directory. When the restore of the database is nished, follow these steps: 1. Stop all running OmniBack II sessions. If the Graphical User Interface is
l# 1 1 Q F #SF# s#v EsESF #SQ

8-15
2. Use the omnisv.sh -stop command to stop all OmniBack II processes. 3. Move the existing database directory /var/opt/omni/db to a temporary location so that the directory is empty. This prevents merging of old and new files. 4. Copy the database files from the alternative directory to the original directory /var/opt/omni/db. If you have extension files on some other directory, be sure to copy them to the original position as well. 5. Make sure that the /var/opt/omni/db/syslog directory exists and is empty. If it is not empty, delete all the files from this directory. 6. Use the omnisv.sh -start command to restart the OmniBack II daemons.

With the database backup, all conguration les such as datalists, barlists, scheduling information, cell conguration, were also backed up. You can also recreate these les by copying the complete directory structure.
8-16
1# 1 1 Q F #S) s#v EsESF # #SQ #
in use, exit the interface. This prevents access to the database.
Moving the Database to Another Host

HP OmniBack II provides two ways for you to move the OmniBack II database to another host. You can either move the database direcusing recovery backup or copy the database to ASCII les and then move the ASCII les 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 restore the database to another host using database receovery procedure. For instructions how to back up the database, see Backing Up the Database on page 8-12. For instructions how to recover a database, see Restoring the Database on page 8-14. Copying the Database to an ASCII le and Moving the File Using this method, you copy the database to ASCII les and then move the ASCII les to the new host. To do this, follow these steps: 1. Export the database to ASCII files using the following command. This creates two ASCII files with the data from MMDB adn CDB in the directory 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 using rcp, ftp, or NFS mount. 3. If you have the database extensions files configured, create similar extension files on the new location. 4. Import the database on the other host using the following command:
Q )v# 7 1) 1# 1 3 #SF# s#v EsESF #SQ

8-17
See a manpage for the omnidbutil command for a detailed syntax description.
8-18
Q )v 1) 1 1 3 #S) s#v EsESF # #SQ #

omnidbutil -readascii [-mmdb directory] [-cdb directory] [-no_details]
The -no_details option prevents importing the detail catalogs.
Using Complex Devices and Libraries
9-1
In This Chapter Any device that has more than a single drive and a single cartridge is considered a complex device. For example, libraries provide you access to a large 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. This chapter helps you understand how to: Manage complex devices Configure a SCSI-II library Configure a non-standard library
9-2
# q#q# Eg Q)m #E)b#
Managing Complex Devices with OmniBack II

OmniBack IIs media management services, device support features, and the OmniBack II conguration database work together to control the behavior of complex 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 by OmniBack II. All physical devices in a device chain must belong to the same class. Devices are used sequentially. Device chains do not support parallel backups thus reducing possible performance. Stackers A stacker is a single device usually with only one drive. A stacker takes a medium from a "stack" (its repository) and inserts the medium into its drive. This exchange is always limited to ejecting the medium already in the drive and inserting the next medium from the stack. A stacker cannot randomly pick a medium from its repository. Libraries Libraries, also called exchangers, jukeboxes, or carousels, can randomly pick a medium from its repository and insert the medium in the drive. Libraries differ in repository sizes, exchanging techniques, and number of drives. Some libraries can even read the bar code on the media in the repository.
b#) 1 Q x 1)1 11 # q#q# Eg Q)m #b#)b#

9-3
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 explained below.
Device Chains Backup When OmniBack II detects the end of a medium during a backup session, OmniBack II automatically switches to the next drive congured with the logical device. When all devices in the chain are used, OmniBack II issues a mount request. The user must then replace all the media in each drive. When OmniBack II detects that the mount request has been satised, it starts backing up again from the rst drive. Restore How OmniBack II operates on a device chain during restore is analogous to how it operates during backup. OmniBack II starts scanning the rst drive of the device chain to look for the media it needs for restore. If the needed media is not in the rst drive, OmniBack II automatically starts looking for it in the next drive and so on until OmniBack II nds the drive with the correct medium or until it comes to the last drive of the logical device. If OmniBack II cannot nd the required medium, it issues a mount request for the last
9-4
E) 1 7 m Q 1)1 11# # q#q# Eg Q)m #E)b#
drive. If OmniBack II nds the required medium, but still needs another medium to complete the restore, OmniBack II scans the device chain from the current position to the end of the device chain for the needed medium. Initialize OmniBack II initializes media in the rst device of the device chain only. Verication OmniBack II veries media in the rst device of the device chain only.
Stackers Backup OmniBack II performs backups to a stacker in the same manner as for device chains. The only difference is that instead of changing the drive currently in use, OmniBack II picks the next medium from the repository. If no medium is available, OmniBack II issues a mount request. Restore OmniBack II performs restores from stackers in the same manner as for device chains. The media in the drive is exchanged until the desired medium is 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 can eject the initialized medium to go to the next one. Verication The medium that is at the top of the stack is veried.
b#) 1 Q x 1)1 11 # q#q# Eg Q)m #b#)b#

9-5
Libraries Backup OmniBack II keeps a record of which media are in the repository of a library. This information is updated when a medium is entered or ejected from the repository. OmniBack II always tries to allocate the media it will use for backup from the contents of the repository. If OmniBack II cannot backup using media from the repository or if OmniBack II must use a medium from the top of the Prealloc List, OmniBack II will issue a mount request. If media in the repository is manually removed (you use the Eject button), you must rescan the repository so OmniBack II can update its Media Management database.

We recommend always operating a library via the OmniBack II software. If you circumvent the software and do operations on the library manually, you risk confusing the software which will result in misleading operations messages.
Restore If the media is in the repository, it is automatically inserted into drive in the correct 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 be initialized. Verication Specify slots for all the media in the library repository that are to be veried.
9-6
E) 1 7 m Q 1)1 11# # q#q# Eg Q)m #E)b#
Configuring a SCSI-II Library

A generic tape/optical library is a complex mechanical device containing one or more data drive mechanisms, an internal magazine (repository) of media, and a mechanical picker capable of loading and unloading the media into 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 three SCSI IDs one for each drive and a third for the picker. One exception to this is the HP SureStore 12000e Library which allows both mechanisms, the data drive and the picker, to be accessed through the same SCSI ID but different SCSI Logical Units (lu). Each repository slot of a library holds one cartridge. OmniBack II assigns a numerical ID to each slot within the repository starting from one. You refer to these slots by ID numbers when you congure 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 an ID starting with the number one. A 4-drive library, for example, will have the drive IDs 1, 2, 3, and 4. A single drive library is referred to by the drive ID number 1.

Note that the above slot and drive IDs are NOT the physical element IDs returned by the library in response to a SCSI mode sense command (ioctl). The physical element IDs are determined by the Media Agent based on the above slot and drive IDs 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 have to know the physical element IDs of the library to complete the logical device conguration.
During the conguration of the library, you congure the drives you want to use with OmniBack II.
1 1# U v)vE1 11C31F # q#q# Eg Q)m #b#)b#

9-7
Example of a Library Configuration

The following example will demonstrate how to congure a double-drive DDS library with a repository of 50 slots and connected to an HP9000/S700 system. Conguring a device on other supported systems is similar. Refer to your system administration manuals for instructions how to nd the appropriate device les or the appropriate SCSI-II addresses of devices. The basic steps involved in conguring 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 page 3-14 for more information about media pool and how to create them.
Selecting the Device Files

If you are conguring your library on an HP9000/S800 system, you will have to install the SPT driver which is available in the patch PHKL_5405 (for HP-UX 9.04 or 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 that you follow carefully the instructions provided with the patch. You must install the correct driver for your devices, select the correct SCSI address, and create a device le 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 running ioscan, such as SAM. This could cause the system to reboot.
1. Determine the Unix device files (SCSI-II addresses) that correspond to
9-8
# q )m #E)b# F

6# & # $ 4 1 1 ( ( & 7%5 1 32 )0)' %! $ # "
the library drives. The double-drive DDS library in our example would use the device les /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 the library picker mechanism. In our example, the device les are in the /dev/scsi directory. We will use the device le /dev/scsi/0. The "0" at the end of the device le name 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 picker device but accepts both data drive access commands and picker commands through the same SCSI ID. However, the data drive access commands must be directed to SCSI lu 0 and the picker commands to SCSI lu 1. Therefore, if you are using the HP SureStore 12000e Library, create a new device le that will allow you to address the picker through the same SCSI ID as the data drive (ID number 1) but referring to a different 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 II uma utility verifies that the picker identifies itself correctly 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 le does not refer to a SCSI-II library picker. Double check that the picker is referred to by SCSI ID 0. If you are conguring an HP SureStore 12000e Library, make sure you have created the proper device le. 4. Using the OmniBack II uma utility to force the library to re-initialize itself:
9-9
# q )m #b#)b# )

6# & # $ 4 1 1 ( ( & 7%5 1 32 )0)' %! $ # "
Conguring Drives for the Library Example of conguring a library with 2 drives.
Logical Device DRIVE_1 DRIVE_2 Table 9-1 Drive Device File Control File
1. Once you have determined the correct UNIX device files for the library drives and picker, configure the SCSI-II Library. Choose Devices & Media from the OmniBack II Main menu. 2. Select Edit Create SCSI II Library to open the Logical Device Editor window. Enter the needed information. For detailed field descriptions, refer to the online help. 3. In the SCSI II Control Device eld of the Logical Device Editor window, enter the pathname of the Unix device le that corresponds to the librarys picker mechanism. In our example, the pathname of the UNIX device le is /dev/scsi/0. 4. In the Exchanger Data Device eld of the Logical Device Editor - Drive window, enter the pathname of the Unix device le corresponding to each library drive. For tape libraries, the pathname will be one of the les from the /dev/rmt directory. In our example, the pathname would be /dev/rmt/1m. 5. In the Drive Index eld, enter the ID number of the drive you want OmniBack II to use for the backup or restore. In our example, "1."
9-10
# q )m #E)b# F

6# & # $ 4 1 1 ( ( & 7%5 1 32 )0)' %! $ # "
# 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
1 2
/dev/rmt/1m /dev/rmt/2m
/dev/scsi/0 /dev/scsi/0
Example Device Conguration
Take care when conguring the logical device that you specify the right device le for the right drive index. If you do not, you could set it up so that the library loads media into device 2 and reads from device 1. This is important for a library with two or more drives.
You do not have to set the Advanced Options button. These options are set to default values and normally do not need to be adjusted. This completes the conguration of the rst example logical device, DRIVE_1. To congure the second drive DRIVE_2, follow the same steps. To Verify the Conguration From the Library Management window, select a range of slots and choose Edit Scan...If the device is congured correctly, OmniBack II will be able to load, read, and unload each medium inside the library repository.
# q )m #b#)b# )

6# & # $ 4 1 1 ( ( & 7%5 1 32 )0)' %! $ # "
9-11
Configuring a Non-Standard Library for Use with OmniBack II

In order to control a non-standard library with OmniBack II, you must write a Library Control Script. This script is started whenever the OmniBack II Media Agent needs to load or unload a medium from a repository. To keep the script interface as simple as possible but exible enough to handle a large variety of library devices, the OmniBack II Media Agent denes only two operations: medium load medium unload
Both the load and unload operations are invoked through the same external script which must be capable of parsing our predened options and parameters.
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 from the repository. As soon as the script successfully completes the action, it should return an exit code of zero. If the script terminates unsuccessfully, a positive integer is returned. During the execution of the script, any messages read from its stdout will be picked up by the Media Agent and passed to the controlling Session Manager as error messages at level MINOR. The script is called by OmniBack II using the popen() mechanism.

Note that using an external script interface is a potential security leak since the OmniBack II Media Agents are always executed with root permissions.
To load a medium into the designated library drive, OmniBack II invokes the external script as:
%<script>
9-12
Q 1 0S R A9 I0)AD6 %5 '%8A@38 1 U T & $ P $ H G F E # C # & # $ 4 B # & B & 9 (2
' %! & $ # " # q )m #E)b# F
-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 current medium used is ipped and what its original position was in the library repository slot. When the medium is unloaded, it will be ipped again as it is returned to the repository. The Media Agent assumes that the library is on-line and reset to an operational state before OmniBack II uses it. In a previous section of this chapter we recommended you always operate the library via the OmniBack II software. If someone circumvents the software and does operations on the library manually, the result will be inconsistent software and library states. If the library is left in this inconsistent state, the load or unload action will probably fail and abort the Media Agent. The external script should detect that the library has been used and left in an inconsistent state and rescan the library so that it is reset to its default operational state. However, the Media Agent does not issue a special reset or initialize command for this purpose. Some libraries have removable cartridge magazines (containing media) that can be loaded and unloaded under software control. The OmniBack II Media Agent assumes the magazine is loaded and does not attempt to pre-load it at startup or unload it at shutdown. If a particular library offers the magazine loading function, the external scripts should detect an unloaded magazine and load it automatically without any Media Agent intervention.
Device Configuration
Congure a logical device using the Logical Device Editor window for the type of logical device you are conguring. To access the Logical Device Editor window, follow these steps:
9-13
Q 1 D0S R A9 YXWV7%5 8I%A@3 1 U T & $ P $ H G F E # C 6# & # $ 4 B # & B & 9 (2
# q )m #b#)b# )
& ' %!0 $ # "
1. At the OmniBack II main menu, select Devices to open the HP OmniBack II - Logical Device Administration window appears. This window shows the logical devices that are currently configured for this cell. 2. Select Edit Create Logical Device External Control from the menu bar. The Logical Device Editor External Control window appears. 3. Enter the needed information. The Drive Index must correspond to the Library Data Device. Enter the complete path and filename of the Library Control Script.
9-14
Q 1 0S R A9 I0)AD6 %5 '%8A@38 1 U T & $ P $ H G F E # C # & # $ 4 B # & B & 9 (2
' %! & $ # " # q )m #E)b# F
10
Troubleshooting
10-1
e c b Sfd# Ua`
In this chapter This chapter is divided into sections covering the most common messages and sections covering other OmniBack II messages. Each message is provided with a description or possible cause and recommended actions.
All the troubleshooting messages can be searched from the OmniBack II online help to simplify the access to descriptions and actions.
If you encounter problems that are not documented here, be sure to check the HP OpenView OmniBack II Software Release Notes.
10-2
Common GUI Errors and Warnings

MESSAGE:
Can not access the server host. (inet is not responding) The host that is specified in the /etc/opt/omni/cell/cell_server file is not reachable, it is not turned on and running, or has no OmniBack II software installed and configured on 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 on the network. If not, check the conguration of network services and routing. Check if the OmniBack II software is properly installed on the host. You can use the command: telnet hostname 5555 . After 30 seconds the OmniBack II should respond with the version information to conrm that it is 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.
e c b Sfd# Ua`
F %pi%%%# $ # & h B & F # #
Q 1 E g ' 'Q 0
10-3
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 logical devices. ACTION: Move logical devices to another pool.
MESSAGE:
Device not found.
DESCRIPTION: When adding/modifying an object to the datalist, you tried to specify a logical device that does not exist. ACTION: Use help [] button to get list of congured devices.
MESSAGE:
Host hostname unavailable.
Can not change cong les! DESCRIPTION: When exporting a host from a cell, it was not reachable. The host was properly 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. You must delete the /etc/opt/omni/cell/cell_server le on the host.
10-4
F 8 8qpi%%%# $ # & h B & F # #
e c b Sfd# Ua`
Q 1 E g 0RI8 'Q
MESSAGE:
Host is not in this cell.
DESCRIPTION: When adding/modifying an object to the datalist, you tried to get list of available mountpoints for a host that is not congured in the cell. ACTION: Use the ... button to get the list of congured 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 le contains the information about Cell Server to which this host belongs. If name of Cell Server is different, then remove this le and repeat the procedure.
MESSAGE:
Insufficient disk space on filesystem containing paths pathname and pathname.
DESCRIPTION: There is not enough disk space on volumes with /opt/omni (on HP - UX 10.x) or /tmp/omni_tmp (on HP-UX 9.x) directories.
10-5
e c b Sfd# Ua`
F %pi%%%# $ # & h B & F # #
Q 1 E g ' 'Q 0
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 series sun/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 can not be initialized. ACTION: Check that you do not need the data on the medium, recycle it, and initialize it with the Force initialization option.
10-6
F 8 8qpi%%%# $ # & h B & F # #
e c b Sfd# Ua`
Q 1 E g 0RI8 'Q
MESSAGE:
OmniBack II medium c14d05b9:2fb2f6ff:4a3d:0001 in drive. Medium not found in OmniBack II database. This medium can be initialized only with force option specified. Initialization denied.
DESCRIPTION: If you have an OmniBack II medium and it is not found in the database, the medium can not be initialized. ACTION: Check that you really do not need the data on the medium any more and initialize the medium with the Force Initialization option.
MESSAGE:
The number of configured clients is greater than the number of available client (host) licenses. Possibly the license has expired. Run command omnicc -query to see the licensing summary report.
DESCRIPTION: Not enough licenses. ACTION: Add new licenses or change the conguration.
e c b Sfd# Ua`
F %pi%%%# $ # & h B & F # #
Q 1 E g ' 'Q 0
10-7
Common Message Screen Errors and Warnings

MESSAGE:
[Minor] From: BMA@hostname NJIVA_48L Time: 07/29/95 02:11:53 /dev/dat3 Can 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:13 Can 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, specied in DEV. CONFIG using telnet to port 5555.
10-8
F %sR8Dq8q%# $ # & h B & F # #
Q G G # T ( G & F F G r %WDDI8 'Q
e c b Sfd# Ua`
MESSAGE:
[Critical] From: BDA-NETIO@hostname KALEIDOSKOP backup Time: Sat Jul 29, 1995 01:33:13 Can not connect to Media Agent (IPC Invalid Hostname or IP Address) => aborting Unexpected 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 le on the Disk 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 le from the backup. MESSAGE:
[Warning] From: VBDA@hostname Time: 08/14/95 16:34:32 filename Can not preserve time attributes: (Not owner)
DESCRIPTION: OmniBack II could not reset the access time attribute of the le. ACTION: If this error appears constantly, you may set the Do not preserve access time attributes option, or exclude the le from the backup.
e c b Sfd# Ua`
F %pi%%%# $ # & h B & F # #
Q G G # T ( G & F F G r %)8' 'Q 0
10-9
MESSAGE:
[Minor] From: VBDA@hostname KALEIDOSKOP backup Time: 07/29/95 03:37:25 filename Can 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 le from the backup.
MESSAGE:
[Minor] From: VBDA@hostname KALEIDOSKOP backup Time: 07/29/95 11: 09:50 /users/leon/ Can not stat: (No such file or directory) => not backed up
DESCRIPTION: File has been removed while backup was running. MESSAGE:
[Minor] From: VBDA@hostname KALEIDOSKOP backup Time: 07/28/95 23 :51:51 /nfs/ops Can not stat: (Stale NFS file handle) => not backed up
DESCRIPTION: NFS mount is not valid. ACTION: Umount and mount back the specied NFS mounted volume.
10-10
F %sR8Dq8q%# $ # & h B & F # #
e c b Sfd# Ua`
MESSAGE:
[Major] From: BMA@hostname NJIVA_48L Time: 07/29/95 02:11:53 /dev/dat3 Can 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/95 02:17:10 Got unexpected close from Filesystem backup DA on hostname.
DESCRIPTION: Disk Agent has lost the connection to the Session Manager. The Disk Agent may have been killed or aborted for some reason. ACTION: Restart backup.
MESSAGE:
[Critical] From: VBDA@hostname KALEIDOSKOP backup Time: 07/29/95 03:15:03 Received 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-11
e c b Sfd# Ua`
F %pi%%%# $ # & h B & F # #
Q G G # T ( G & F F G r %)8' 'Q 0
MESSAGE:
[Major] From: BSM@hostname ZLATOROG1 Time: 08/12/95 22:12:06 The Filesystem backup DA reached its inactivity timeout of 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 les, or directories with large number of les and compression or encryption.

The timeout is dened in the Global options le.
MESSAGE:
[Critical] From: BSM@hostname name Time: 05/12/95 15:33:57 There is no license for BDA@hostname. The disk will not be backed up.
DESCRIPTION: This message is displayed if you have exported or deinstalled a host, but the same host is still congured in the datalist. ACTION: Modify the datalist. Reinstall the host or import it.
10-12
F %sR8Dq8q%# $ # & h B & F # #
e c b Sfd# Ua`
MESSAGE:
[Critical] From: INET@hostname name Time: 05/11/95 12:39:19 User username non-existent on this host => aborting
DESCRIPTION: The backup session on the host was aborted because the user is not registered on the host. ACTION: OmniBack II requires that you have the same username on all hosts you back up.
MESSAGE:
[Critical] From: VBDA@hostname name Time: 05/11/95 12:40:07 tree Not valid mount point => aborting
DESCRIPTION: Wrong mountpoint for the hostname was congured, the backup was aborted. ACTION: Modify the object and use the [] button to get list of valid mountpoints for the host. Check available lesystems using the UNIX df or mount command.
MESSAGE:
[Major] From: BSM@hostname name Time: 05/11/95 13:08:05 Could not connect to inet for starting of disk agent on host hostname.
e c b Sfd# Ua`
F %pi%%%# $ # & h B & F # #
Q G G # T ( G & F F G r %)8' 'Q 0
10-13
DESCRIPTION: During the backup session the agent on the host hostname could not be started 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 can use the telnet hostname 5555. After 10 seconds the OmniBack II should respond with the version information to conrm that it is running.
MESSAGE:
[Minor] From: BSM@hostname name Time: 05/11/95 10:58:36 There are not enough media in the pool to complete the backup.
DESCRIPTION: The calculation at the end of the backup preview shows that there are not enough 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 to create more space for new backups.
MESSAGE:
[Minor] From: VBDA@hostname name Time: 05/11/95 10:54:40 tree Can not traverse: (Permission denied) => not backed up
DESCRIPTION: You do not have UNIX permissions to back up the specic tree. The backup of that tree was skipped.
10-14
F %sR8Dq8q%# $ # & h B & F # #
e c b Sfd# Ua`
ACTION: Exclude the tree from the backup as you are not authorized to backup these les.
MESSAGE:
[Warning] From: VBDA@hostname name Time: 05/11/95 10:57:25 tree Object does not reside on current filesystem => not backed up
DESCRIPTION: The tree you have specied is not on the lesytem that is backed up. ACTION: Check on which lesystem the tree resides and modify the datalist accordingly.
MESSAGE:
rexec: Lost connection Problem in obtaining information from host hostname. Possibly wrong password.
DESCRIPTION: Installation to a new host failed- system function rexec between Cell Server and client host can not be executed. ACTION: Resolve why the rexec function can not be executed. See manpages for rexec command.
e c b Sfd# Ua`
F %pi%%%# $ # & h B & F # #
Q G G # T ( G & F F G r %)8' 'Q 0
10-15
Less Common Warning and Error Messages

MESSAGE:
[ERROR] Can not open database/file.
DESCRIPTION: OmniBack II was unable to open the internal database. The database les are either not available or the Unix le permissions to access the database les are incorrect. ACTION: Check the database les ( *.dat, *.ext, *.key) in the /var/opt/omni/db/cdb and /var/opt/omni/db/mmdb directories on the Cell Server. The permissions of these les should be 600 and user root. If there are no les, database has not been initialized yet. In this case, use the omnidbinit command to initialize the database.
MESSAGE:
[ERROR] Cant access the file.
DESCRIPTION: Conguration le can not be accessed. This message means that the Cell Server daemon can not read or write from a certain conguration le. ACTION: Use the /bin/ll - command to check the appropriate les below the directory /etc/opt/omni.
10-16
F G & F F G r # # )%%#
Q B & ' %si 'Q 04 $ # & h F F G
e c b Sfd# Ua`
MESSAGE:
[ERROR] Cant access the file.
DESCRIPTION: The IPC communication ended unexpectedly. ACTION: Check for system resources (memory, swap space). Check if Session Managers are being killed.
MESSAGE:
[MAJOR] FullPathName Can not append to medium (UnixErrorString)
DESCRIPTION: The Backup Media Agent (BMA) process was unable to append to existing data on the medium in use. ACTION: No action is necessary. OmniBack II will attempt to use another medium as this medium has no available space. Simply respond to any mount prompts.
MESSAGE:
[WARNING] FullPathName Can not apply lock: (UnixErrorString)
DESCRIPTION: The specied object could not be locked before backup. The error message indicates 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.
e c b Sfd# Ua`
F G & F F G r # # DW%%#
Q B & I8 %pi 'Q 0D4 $ # & h F F G
10-17
MESSAGE:
[MINOR] FullPathName Can not close: (UnixErrorString)
DESCRIPTION: If the specied object can not be closed after it is backed up, the backup status of this object is unsuccessful. The error message indicates the reason as reported by the operating system. ACTION: Eliminate the problem described by the error message and restart the backup 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 specied host. ACTION: Use the ping command to check the connection to this host and telnet <HOSTNAME> 5555.
MESSAGE:
[ERROR] Can not connect to required session session-id.
DESCRIPTION: You specied the wrong session ID when trying to abort a session. ACTION: Use the omnistat command to get the correct session ID, then try the command.
10-18
F G & F F G r # # )%%#
Q B & ' %si 'Q 04 $ # & h F F G
e c b Sfd# Ua`
MESSAGE:
[ERROR] Can not connect to session with session ID session-id.
DESCRIPTION: You tried to monitor a session that is not a backup or restore session. You can only monitor backup and restore sessions. ACTION: Restart the monitor, specifying backup or restore session.
MESSAGE:
[MAJOR] FullPathName Can not determine disk characteristics (UnixErrorString) => aborting
DESCRIPTION: The optical pre-erase operation failed because OmniBack II was unable to read 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 message indicates the reason as reported by the operating system.
e c b Sfd# Ua`
F G & F F G r # # DW%%#
Q B & I8 %pi 'Q 0D4 $ # & h F F G
10-19
ACTION: Eliminate the problem described by the error message and restart the session. If the pre-erase fails again, you must replace the disk. Check if the drive needs cleaning.
MESSAGE:
[ERROR] Can not execl omnib for datalist datalist_name.
DESCRIPTION: The omnitrig command can not execute the command omnib. ACTION: Check to be sure that the /opt/omni/bin/omnib command exists, and be sure that the Unix le permissions are correctly set. If the omnib command exists and the permissions are correct, the le 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 specied object before starting the restore. The error message indicates the reason as reported by the operating system. ACTION: Restart the operation.
MESSAGE:
[WARNING] FullPathName Can not force lock: (UnixErrorString)
10-20
F G & F F G r # # )%%#
Q B & ' %si 'Q 04 $ # & h F F G
e c b Sfd# Ua`
DESCRIPTION: The specied object could not be locked before backup. The error message indicates 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 open crontab for writing.
DESCRIPTION: You either are not congured for cron or do not have permission to access the cron le. ACTION: Check, and if necessary correct, the cron le conguration and the permission of its conguration les.
MESSAGE:
[MAJOR] Can not load exchanger medium (UnixErrorString)
DESCRIPTION: The library failed to complete SCSI move command. The error message indicates the reason as reported by the operating system. ACTION: Verify that the autochanger device is online and ready. If necessary, perform hardware reset of the autochanger or turn the power off and on. Then restart the failed session.
e c b Sfd# Ua`
F G & F F G r # # DW%%#
Q B & I8 %pi 'Q 0D4 $ # & h F F G
10-21
MESSAGE:
[ERROR] Can not lock database - currently unavailable.
DESCRIPTION: You have a lot of parallel jobs and they want ot access the same part of databse. ACTION: Check to be sure that no other OmniBack II processes are running on the Cell Server (especially Session Managers bsm/rsm/msm/dbsm/psm and the omnidbcheck command.) Stop the Cell Server (using the omnisv.sh -stop command) and then restart the Cell Server (using the omnisv.sh start command). Try rescheduling some backups to run them in sequence (instead of parallel). If PSM (purge session manager) is running you can congure it in the global options le to run when no backups are running.
MESSAGE:
[MAJOR] FullPathName Can not lock exchanger control device (UnixErrorString)
DESCRIPTION: The Media Agent (xMA) could not reserve the library control device for its exclusive use. Exclusive locking is required for multi-drive libraries to prevent mechanical damage. This problem can occur if you are running several Media Agents that concurrently use the same autochanger. The error message indicates the reason as reported by the operating system. ACTION: Check the device and restart the session.
10-22
F G & F F G r # # )%%#
Q B & ' %si 'Q 04 $ # & h F F G
e c b Sfd# Ua`
MESSAGE:
[MAJOR] Can not lock medium mediumID in database. Probably in use by someone else. Skipping reinitialization.
DESCRIPTION: You tried to reinitialize medium which is locked by another process. Possible causes are another user is modifying medium data (label and location) or someone killed the backup/restore Session Manager and the medium 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 for restore as root to restore special les. ACTION: Either add the restore as root access right to this user class or transfer this user to a user class that has the restore as root access right.
MESSAGE:
[ERROR] Can not open database in exclusive mode. Some Session Managers may still be running.
DESCRIPTION: Message is usual at merging mmdb database to central mmdb database. It means that there are session managers running on central host. It might seem that no Session Manager is running, but the message appears. Reason is that there is a lock for cca 30 min after Session Manager is down. In that case restarting crs solves a problem.
10-23
e c b Sfd# Ua`
F G & F F G r # # DW%%#
Q B & I8 %pi 'Q 0D4 $ # & h F F G
ACTION: Wait for the Session Managers to complete, then restart the operation. Check that no Session Managers are running.
MESSAGE:
[ERROR] Can not open database. Somebody is running omnidbcheck or omnidbutil command.
DESCRIPTION: You tried to run a process that opens the database. However, OmniBack II was unable to open the database because either a user was running omnidbcheck or an omnidbutil command. ACTION: Wait for the omnidbcheck or omnidbutil command, then restart the operation.
MESSAGE:
[MAJOR] FullPathName Can not open device (UnixErrorString)
DESCRIPTION: The Media Agent (xMA) detected an error trying to open a device. The error message indicates the reason as reported by the operating system. A "No such device or address" message from media device indicates that there is no medium in the device. ACTION: Verify that medium is loaded and ready. Respond to any pending mount prompts.
10-24
F G & F F G r # # )%%#
Q B & ' %si 'Q 04 $ # & h F F G
e c b Sfd# Ua`
MESSAGE:
[MAJOR] Can not open mount table: (MountTable)
DESCRIPTION: OmniBack II is unable to access the register of mounted lesystems. Probably invalid access rights to the register. ACTION: Verify the cause of this problem described in the error message and notify your system administrator.
MESSAGE:
MAJOR: Can not open mount table: (UnixErrorString)
DESCRIPTION: OmniBack II is unable to access the register of mounted lesystems on the host running the Disk Agent (VBDA). The error message indicates the reason as reported by the operating system. ACTION: Verify that the mount table (le /etc/mnttab on HP-UX systems) exists on the host running the Disk Agent (VBDA) and can be accessed.
MESSAGE:
[WARNING] FullPathName Can not open option file: (UnixErrorString)
DESCRIPTION: The Disk Agent (xBDA) received -read option or an input redirection operator (-trees <lename) and the input le could not be accessed. ACTION: Verify that the input le exists on the appropriate host and can be read by the Disk Agent (xBDA).
e c b Sfd# Ua`
F G & F F G r # # DW%%#
Q B & I8 %pi 'Q 0D4 $ # & h F F G
10-25
MESSAGE:
[WARNING] FullPathName Can not open option file: (UnixErrorString)
DESCRIPTION: The Media Agent (xMA) received -read option or an input redirection operator (-dev <le) but the input le could not be accessed. ACTION: Verify that the input le exists on the appropriate host and can be read by the Media Agent (xMA).
MESSAGE:
[MINOR] FullPathName Can not open: (UnixErrorString) => not backed up
DESCRIPTION: The specied object could not be opened and will not be backed up. The error message indicates the reason as reported by the operating system. ACTION: Eliminate the problem described by the error message and restart the backup session. Exclude the specified object from the backup fileset using the -exclude option.
10-26
F G & F F G r # # )%%#
Q B & ' %si 'Q 04 $ # & h F F G
e c b Sfd# Ua`
MESSAGE:
[WARNING] FullPathName Can not preserve time attributes: (UnixErrorString)
DESCRIPTION: The Disk Agent (VBDA) is unable to preserve the time attributes of the specied object. The error message indicates the reason as reported by the operating system. ACTION: Select option Do not preserve time attributes or back up as root or le owner.
MESSAGE:
[MINOR] FullPathName Can not read ACLs: (UnixErrorString)
DESCRIPTION: The extended ACL attributes belonging to this object can not be read 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 and restart 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.
e c b Sfd# Ua`
F G & F F G r # # DW%%#
Q B & I8 %pi 'Q 0D4 $ # & h F F G
10-27
ACTION: The session fails. You must check the media in the device and restart the session.
MESSAGE:
[MINOR] FullPathName Can not read link: (UnixErrorString) => not backed up
DESCRIPTION: The specied 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 and restart the backup session to complete successful backup.
MESSAGE:
[MINOR] FullPathName Can not read: (UnixErrorString)
DESCRIPTION: The specied object could not be read and will not be backed up. The error message indicates the reason as reported by the operating system. ACTION: Eliminate the problem described by the error message and restart the backup session. Exclude the specified object from the backup fileset using the -exclude option.
10-28
F G & F F G r # # )%%#
Q B & ' %si 'Q 04 $ # & h F F G
e c b Sfd# Ua`
MESSAGE:
[MAJOR] FullPathName Can not seek to requested position (UnixErrorString)
DESCRIPTION: The Media Agent (xMA) detected an error while trying to move the read/write head to certain position. The error message indicates the reason as reported by the operating system. ACTION: A possible cause of this error is corrupted media format. Verify the media format using the OmniBack medium verication utility. The session fails. You must check the media in the device and restart the session.
MESSAGE:
[MINOR] FullPathName Can not stat: (UnixErrorString) => not backed up
DESCRIPTION: The specied object could not be examined and will not be backed up. The error message indicates the reason as reported by the operating system. ACTION: Eliminate the problem described by the error message and restart the backup session. Exclude the specified object from the backup fileset by using the exclude option.
e c b Sfd# Ua`
F G & F F G r # # DW%%#
Q B & I8 %pi 'Q 0D4 $ # & h F F G
10-29
MESSAGE:
[MINOR] FullPathName Can not traverse: (UnixErrorString) => not backed up
DESCRIPTION: The specied directory could not be traversed (probably due to insufcient access rights) and will not be backed up. The error message indicates the reason as reported by the operating system. ACTION: Eliminate the problem described by the error message and restart the backup session. 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 message indicates the reason as reported by the operating system. ACTION: Verify that the autochanger device is online and ready. If necessary, perform a hardware reset of the autochanger or turn the power off and on. Then restart 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 drive Can not be unloaded.
10-30
F G & F F G r # # )%%#
Q B & ' %si 'Q 04 $ # & h F F G
e c b Sfd# Ua`
ACTION: If there is a medium in the source drive, then the internal library status is corrupted and needs to be reset. To x the problem, terminate the OmniBack II session, reset the library, and rescan the library using the OmniBack II rescan feature. NOTE: You can reset the library by either pressing the reset button on the front panel or 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 repository already 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 and needs to be reset. To x the problem, terminate the OmniBack II session, reset the library, and rescan the library using the OmniBack II rescan feature. NOTE: You can reset the library by either pressing the reset button on the front panel or turning the power off and on.
e c b Sfd# Ua`
F G & F F G r # # DW%%#
Q B & I8 %pi 'Q 0D4 $ # & h F F G
10-31
MESSAGE:
[WARNING] FullPathName Can not unlock exchanger control device (UnixErrorString)
DESCRIPTION: The Media Agent (xMA) could not release the library control device. The error message indicates the reason as reported by the operating system. ACTION: No action is necessary. The library control device will be released automatically 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 specied object after the restore and therefore the restore failed. The error message indicates the reason as reported by the operating system. ACTION: Restart the restore.
MESSAGE:
[WARNING] FullPathName Can not unlock: UnixErrorString
DESCRIPTION: The specied object could not be unlocked after backup and its backup status will not be successful. The error message indicates the reason as reported by the operating system. ACTION: No action is necessary. The specied object will be unlocked automatically when the Disk Agent (VBDA) process terminates.
10-32
F G & F F G r # # )%%#
Q B & ' %si 'Q 04 $ # & h F F G
e c b Sfd# Ua`
MESSAGE:
[ERROR] Medium Medium ID in device Logical Device in the pool Pool Name with strict allocation policy can not be used for backup. Medium label is: Medium Label
DESCRIPTION: Library repository was not correct or if you are using pool which has strict Media Allocation Policy, you must mount the exact medium specied by the mount request. ACTION: Mount the medium specied by the mount prompt or use rescan library before backup if you often manually replace media in a library.
MESSAGE:
[MAJOR] FileSystemMountPoint Can not verify filesystem mount point:
DESCRIPTION: OmniBack II is unable to locate the specied mount point in the register of mounted lesystems. ACTION: Verify that the specified mount point exists on the host running the Disk Agent (VBDA) and can be accessed. Ensure that the specified filesystem is mounted at backup time
e c b Sfd# Ua`
F G & F F G r # # DW%%#
Q B & I8 %pi 'Q 0D4 $ # & h F F G
10-33
MESSAGE:
[MAJOR] FullPathName Can not write to device UnixErrorString
DESCRIPTION: The Media Agent (xMA) detected an error while writing to the device. The error message indicates the reason as reported by the operating system. ACTION: The session fails. You must check the media in the device and restart the session.
MESSAGE:
[WARNING] Connection to the peer_type on host peer_host is inactive for over the timeout period and will therefore be closed. Agent identification is peer_version.
DESCRIPTION: Trouble communicating with one of the agents. Agent does not update its status periodically. ACTION: Restart the operation.
MESSAGE:
[MAJOR] Could not connect to Disk Agent agent_host:mountpoint named label.
DESCRIPTION: It is not possible to start Disk Agent on the specied host. There might be a problem with your network setup or there is no OmniBack II inet process properly congured for the target host.
10-34
F G & F F G r # # )%%#
Q B & ' %si 'Q 04 $ # & h F F G
e c b Sfd# Ua`
ACTION: Check your network setup and check that the conguration of the les /etc/services and /etc/inetd.conf on the target host is correct for the inet entry. Use telnet <host> 555 for checking. MESSAGE:
[MAJOR] Could not connect to Media Agent agent_host:mountpoint named label.
DESCRIPTION: It is not possible to start the Media Agent on the specied host. There might be problem with your network setup or there is no OmniBack II inet process properly congured for the target host. ACTION: Check your network setup and check that the conguration of the les /etc/services and /etc/inetd.conf on the target host is correct for the inet entry. Use telnet <host> 555 for checking.
MESSAGE:
[MAJOR] Could not connect to OmniBack II inet process on host agent_host.
DESCRIPTION: Media management Session Manager can not connect to OmniBack II inet process 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:
e c b Sfd# Ua`
F G & F F G r # # DW%%#
Q B & I8 %pi 'Q 0D4 $ # & h F F G
10-35
Be sure that the OmniBack II entries are contained in the /etc/inetd.conf and/etc/services les. Then trigger the /etc/inetd daemon to reread the conguration with /etc/inetd -. Use telnet <host> 555.
MESSAGE:
[MAJOR] Could not start Media Agent. Session is aborted.
DESCRIPTION: Could not start the Media Agent for Media Management Operation. The Media Agent did not respond to the Session Manager. ACTION: Check the message from OmniBack II [inet] process. Be sure that the OmniBack II Media Agent software is installed on host where this device is located. Use telnet <host> 555.
MESSAGE:
[ERROR] Database is probably corrupt. Please run omnidbcheck!
DESCRIPTION: OmniBack II database is probably corrupt. ACTION: Terminate all running sessions and GUIs so that no process is accessing the database. Next, login to Cell Server as root and run the omnidbcheck fix command. If you get error message "Database is corrupted!", the database is unxable and you must recover the database from backup.
MESSAGE:
[ERROR] Database key files have been corrupted. Please run omnidbcheck -fix!
10-36
F G & F F G r # # )%%#
Q B & ' %si 'Q 04 $ # & h F F G
e c b Sfd# Ua`
DESCRIPTION: The OmniBack II database index le has been corrupted. ACTION: Use the omnidbcheck -fix command to x the index le.
MESSAGE:
[ERROR] Database network communication error.
DESCRIPTION: The OmniBack II database has problems communicating with the Velosis Daemon (RDS). It is very likely that rds was restarted, and GUI was not. ACTION: Check to be sure that the Velosis Daemon (RDS) is running. Stop the Cell Server (using the omnisv.sh -stop command) and restart the Cell Server (using the omnisv.sh -start command). Start the GUI.
MESSAGE:
[ERROR] Database record limit per file reached.
DESCRIPTION: The limit for OmniBack II database records has been reached. ACTION: Stop all Session Managers and terminate all GUIs, then use the omnidb strip and omnidbcheck -purge command to delete obsolete data from the database. Restart the operation.
e c b Sfd# Ua`
F G & F F G r # # DW%%#
Q B & I8 %pi 'Q 0D4 $ # & h F F G
10-37
MESSAGE:
[MAJOR] Default pool pool_name of specified device is invalid.
DESCRIPTION: The pool you selected for this device is invalid because it uses an incompatible media class or does not exist. ACTION: Congure different pool for this device.
MESSAGE:
[MAJOR] Device device_name and pool pool_name media classes do not match. Aborting
DESCRIPTION: The media class of the specied device is different than the media class of the specied pool. ACTION: Select pool which has the same media class as the device.
MESSAGE:
[MAJOR] Error accessing the database, in line code_line, file 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-38
F G & F F G r # # )%%#
Q B & ' %si 'Q 04 $ # & h F F G
e c b Sfd# Ua`
MESSAGE:
[ERROR] File containing Cell Server host not found.
DESCRIPTION: The conguration le /etc/opt/omni/cell/cell_server which holds the name of the Cell Server host is missing. ACTION: Create the conguration le /etc/opt/omni/cell/cell_server and add the name of the local Cell Server.
MESSAGE:
[ERROR] File containing Cell Server host not found.
DESCRIPTION: The le /etc/opt/omni/cell/cell_server is missing. This le contains information about the User Interface and the Cell Server. ACTION: Create this le 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 x the problem, follow these steps: 1. Umount the filesystem 2. Remount the filesystem as read/write filesystem 3. Restart the restore
e c b Sfd# Ua`
F G & F F G r # # DW%%#
Q B & I8 %pi 'Q 0D4 $ # & h F F G
10-39
MESSAGE:
[WARNING] FilesystemMountPoint Filesystem is mounted read-only => locking disabled
DESCRIPTION: The lesystem being backed up is mounted as read-only or is read-only by nature (CDROM) and does not support mandatory locking. The Disk Agent (VBDA) will disable the locking feature automatically to prevent wrong error 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 its recursive lesystem traversal. This indicates that your directory structure is too deep. ACTION: Try to reconfigure the filesystem backup object to contain several trees starting 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 Cell Server do not match.
DESCRIPTION: Internal compatibility check reported that the running GUI or command is not compatible with the running Cell Server daemon.
10-40
F G & F F G r # # )%%#
Q B & ' %si 'Q 04 $ # & h F F G
e c b Sfd# Ua`
ACTION: Check the OmniBack II release on the hosts and update the software.
MESSAGE:
[ERROR] Instance of OmniBack II Maintenance control script already running or terminated abnormally; semaphore file inst.lock will be ignored if no other instance running
DESCRIPTION: The lock le inst.lock already existed when the installation was started. ACTION: If you are sure that only you are running the installation script, you can proceed with the installation.
MESSAGE:
[MAJOR] Interprocess communication error on Session Manager connection. The connection was to peer_type on host peer_host. Agent identification is peer_version. Ipc library reports "detailed_error_description."
DESCRIPTION: Unexpected error for interprocess communication on connection to an agent or monitor. The connection is closed. If the connection was to monitor, you can ignore this message. ACTION: Restart the operation.
e c b Sfd# Ua`
F G & F F G r # # DW%%#
Q B & I8 %pi 'Q 0D4 $ # & h F F G
10-41
MESSAGE:
[MAJOR] Invalid slot slotID specified.
DESCRIPTION: You specied a slot which is not congured for this device. ACTION: Check the device conguration and specify the correct slot.
MESSAGE:
[MAJOR] Invalid device device_name specified.
DESCRIPTION: This cell does not contain the device you specied. ACTION: Check the spelling of the device name and the conguration of the device.
MESSAGE:
[MAJOR] Invalid format of the message from peer_type on host peer_host. Agent identification is peer_version.
DESCRIPTION: One of the agents received a recognized message with an invalid format. ACTION: Restart the session.
10-42
F G & F F G r # # )%%#
Q B & ' %si 'Q 04 $ # & h F F G
e c b Sfd# Ua`
MESSAGE:
[WARNING] Invalid option OptionString => ignored
DESCRIPTION: The Disk Agent or Media Agent received an invalid option from the Session Manager. It is possible that the user specied an option argument starting with 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, version peer_version.
DESCRIPTION: Reported peer (Media Agent or command/GUI) is not compatible with this version of the Session Manager. ACTION: Check the software version of your cell and update the peer to the same release as the Session Manager.
MESSAGE:
[ERROR] Velocis daemon error - the daemon is probably not running.Use omnisv.sh start to restart OB2 daemons.
DESCRIPTION: Velocis Daemon (RDS) is not running.
e c b Sfd# Ua`
F G & F F G r # # DW%%#
Q B & I8 %pi 'Q 0D4 $ # & h F F G
10-43
ACTION: Check to be sure that the Velocis Daemon (RDS) is running. Stop the Cell Server (using the omnisv.sh -stop command) and restart the Cell Server (using the omnisv.sh -start command).
MESSAGE:
[ERROR] Maximum number of Session Managers allowed are currently running.
DESCRIPTION: Too many concurrent sessions running. ACTION: Use the monitor GUI or the omnistat command to check the number of currently executing sessions. Abort any unnecessary sessions. Stop the Cell Server (using the omnisv.sh -stop command) and restart the Cell Server (using the omnisv.sh -start command). This will terminate all active GUIs and command-line interfaces.
MESSAGE:
[WARNING] Medium already in database. You must export medium first.
DESCRIPTION: The medium you tried to import already belongs to this cell. ACTION: To put the medium in different cell, use the Move Medium feature. Otherwise, rst export and then import the medium.
10-44
F G & F F G r # # )%%#
Q B & ' %si 'Q 04 $ # & h F F G
e c b Sfd# Ua`
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 a process that terminated unsuccessfully. ACTION: If other Session Managers are running, you can not use this medium until the other Session Managers nish (or are terminated).
MESSAGE:
[WARNING] Medium is still under protection => recycle medium.
DESCRIPTION: You tried to initialize or erase medium that contains protected sessions. ACTION: Use the OmniBack II Recycle feature to remove the protection for the medium, 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 not be veried by OmniBack II. ACTION: Mount valid OmniBack II medium and restart the verication.
e c b Sfd# Ua`
F G & F F G r # # DW%%#
Q B & I8 %pi 'Q 0D4 $ # & h F F G
10-45
MESSAGE:
[WARNING] tar meidum in device ...... The medium will not be used for backup.
DESCRIPTION: OmniBack II checks the format of the medium before writing to the medium. OmniBack II recognizes media of types such as tar, cpio, and HP-UX lesystem but will not write to these media formats. ACTION: To use media of these formats, you must rst initialize the medium by using the -force option. An alternative is to use UNIX commands to overwrite the rst block on the medium.
MESSAGE:
[ERROR] Monitoring is not supported for this session type.
DESCRIPTION: You tried to monitor a session that is not a backup or restore session. You can only monitor backup and restore sessions. ACTION: Restart the monitor, specifying backup or restore session.
MESSAGE:
[ERROR] Neither /etc/hosts nor Name Service can resolve/verify system hostname.
DESCRIPTION: Installation failed because the host name was not in the /etc/hosts le. ACTION: Enter the hostname again, making sure that you spell the name correctly.
10-46
F G & F F G r # # )%%#
Q B & ' %si 'Q 04 $ # & h F F G
e c b Sfd# Ua`
MESSAGE:
[ERROR] No details for this session type.
DESCRIPTION You tried to view status information for a session which is not a backup or restore session. You can only view status information for backup and restore sessions. ACTION: Retry the operation, specifying backup or restore session.
MESSAGE:
[ERROR] No Session Manager with that session ID is currently 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 device specified.
DESCRIPTION: You selected a device which uses double-sided media but you did not specify which side of the medium to use. ACTION: Specify the side of the medium to use.
e c b Sfd# Ua`
F G & F F G r # # DW%%#
Q B & I8 %pi 'Q 0D4 $ # & h F F G
10-47
MESSAGE:
[MAJOR] No slot ID for exchanger device specified.
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 les from the disk where the OmniBack II database is located (/var/opt/omni/db) and then restart the operation. All disks where OmniBack II les 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 its rst treewalk building its internal hard link catalog. The object will be backed up as regular le and can not be restored as hard link reference but only as a separate le. ACTION: If you are concerned about the consistency of your backup data, restart the backup session.
10-48
F G & F F G r # # )%%#
Q B & ' %si 'Q 04 $ # & h F F G
e c b Sfd# Ua`
MESSAGE:
[ERROR] Nothing to browse or database was closed during browse due to inactivity.
DESCRIPTION: There are two possible causes: You tried to use the Browse feature to search the OmniBack II database for files. OmniBack II is unable to display this information because the OmniBack II lacks detailed information about the backup session you selected. Possible causes are the backup session was performed without the Log files 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. If the cause was lack of detailed information in the OmniBack II database, you will need to using another method (for example, read the media) to locate the le(). MESSAGE:
[WARNING] FullPathName Object does not reside on current filesystem => not backed up
DESCRIPTION: The specied object (le/directory) does not belong to the physical lesystem being backed up. Probably it is an NFS mount point. ACTION: No action is necessary. To suppress this error message, exclude the specied object from the backup leset by using the -exclude option.
e c b Sfd# Ua`
F G & F F G r # # DW%%#
Q B & I8 %pi 'Q 0D4 $ # & h F F G
10-49
MESSAGE:
[WARNING] FullPathName Object is mounted filesystem
DESCRIPTION: You have specied a rawdisk section pathname that refers to a disk device containing a lesystem currently mounted. ACTION: No action is necessary. If you are concerned about the consistency of your backup data, you must use the pre/post-exec feature to unmount the lesystem before the backup and remount it after the backup has completed.
MESSAGE:
[MAJOR] deviceFileName Object is mounted filesystem
DESCRIPTION: The rawdisk has a mounted lesystem. ACTION: Unmount the lesystem and start the restore again.
MESSAGE:
[MAJOR] FullPathName Object not character device => not backed up
DESCRIPTION: You have specied a rawdisk section pathname which does not refer to character device le. ACTION: Verify the conguration of the backup object and the rawdisk section les on the host running the Disk Agent (RBDA).
10-50
F G & F F G r # # )%%#
Q B & ' %si 'Q 04 $ # & h F F G
e c b Sfd# Ua`
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 the limit. Split the command into several commands in order to use less resources.
MESSAGE:
[ERROR] Problems in transfer of package packet-name to system hostname via service-name service. Check service manually for user username before continuing.
DESCRIPTION: FTP failed while transferring an OmniBack II software packet to the selected host. The FTP failed because user used the su command instead of su -. ACTION: Run su - 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 the medium belongs to a pool that is not appendable or because this medium is not the rst medium of the backup. ACTION: Be sure that the pool is appendable. Then load the rst medium of that backup set.
10-51
e c b Sfd# Ua`
F G & F F G r # # DW%%#
Q B & I8 %pi 'Q 0D4 $ # & h F F G
MESSAGE:
[WARNING] Can not start script .... tSystem reports error descr
or
tScript .... on cell server host has invalid permissions and will not be executed by Session Manager.
DESCRIPTION: Unable to locate this mount prompt script. Note: Script must be owned by root. The script can only be executed if no other user has write permission for the script. ACTION: Check the script and, if necessary, change the write permissions.
MESSAGE:
[MAJOR] Session Manager received close from the peer_type on host peer_host The agent did not respond in time. Connection will be closed. Agent identification is peer_version.
DESCRIPTION: The connection to the Disk Agent, Media Agent, or Monitor was closed unexpectedly. This is probably due to abnormal agent termination or agent host shutdown. ACTION: Restart the operation.
10-52
F G & F F G r # # )%%#
Q B & ' %si 'Q 04 $ # & h F F G
e c b Sfd# Ua`
MESSAGE:
[MAJOR] Specified device for the object not found.
DESCRIPTION: OmniBack II can not nd the specied device. ACTION: Check the spelling of the device name and the device conguration. If a device does not exist any more, you must specify a different device to be used for restore.
MESSAGE:
[MAJOR] Specified pool pool_name is invalid.
DESCRIPTION: You specied 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-name installation with Cell Server cell-server-name instead of cell-server-name.
DESCRIPTION: The distribution of OmniBack II modules to this host failed because the host already belongs to another OmniBack II cell. The installation script checks the cell-server le located in the full pathname directory on the host where you wanted to install the OmniBack II modules.
e c b Sfd# Ua`
F G & F F G r # # DW%%#
Q B & I8 %pi 'Q 0D4 $ # & h F F G
10-53
ACTION: If you want to import the selected host into your cell, you must rst export it from the cell it belongs to now. Then you will be able to include it into your cell.
MESSAGE:
[WARNING] This medium can be initialized only with force option specified.
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: Restart the operation.
MESSAGE:
[MAJOR] Unknown event on Session Manager from peer_type on host peer_host. Agent identification is peer_version.
DESCRIPTION: Unknown event received from one of the agents.
10-54
F G & F F G r # # )%%#
Q B & ' %si 'Q 04 $ # & h F F G
e c b Sfd# Ua`
ACTION: Restart the session.
MESSAGE:
[WARNING] FullPathName Unknown object type => not backed up
DESCRIPTION: The stat() system call identies a lesystem object not recognized and/or supported by OmniBack II. ACTION: No actions are necessary. To suppress this error message, exclude the specied object from the backup leset by using the -exclude option.
MESSAGE:
[WARNING] Unknown type of compression : UniqueDataCompressionType
DESCRIPTION: There is an error in the shared library libdc.sl. There is difference between the compression used for the backup and the compression used for the restore. Since OmniBack II was unable to decompress the le, it restored the le in compressed form. ACTION: Be sure that the shared library contains the original compression used for the backup. Then restart the restore.
e c b Sfd# Ua`
F G & F F G r # # DW%%#
Q B & I8 %pi 'Q 0D4 $ # & h F F G
10-55
MESSAGE:
[WARNING] Unknown type of encryption !
DESCRIPTION: There is an error in shared library libde.sl. There is difference between the encryption used for the backup and the encryption used for the restore. Since OmniBack II was unable to deencrypt the le, it restored the le in encrypted form. ACTION: Be sure that the shared library contains the original encryption used for the backup. Restart the restore. MESSAGE:
[WARNING] Unrecognized option "OptionString" => ignored
DESCRIPTION: The Media Agent (xMA) received an invalid option from the Session Manager. It is possible that the user specied an option argument starting with 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-56
F G & F F G r # # )%%#
Q B & ' %si 'Q 04 $ # & h F F G
e c b Sfd# Ua`
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 can only 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 the session. If user belongs to an OmniBack II class that has the Abort ACL disabled, 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 monitor this session. If user belongs to an OmniBack II class that has the Monitor ACL disabled he will not be able to monitor sessions belonging to other users. ACTION: Set the Monitor ACL in the appropriate class.
e c b Sfd# Ua`
F G & F F G r # # DW%%#
Q B & I8 %pi 'Q 0D4 $ # & h F F G
10-57
MESSAGE:
[ERROR] You do not have permission to reply to mount request.
DESCRIPTION: OmniBack II security has reported that you have no permission to respond to the specied mount request. This occurs when you try to respond to mount request from a session that was not initiated by yourself and you belong to group 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 specied position is not in OmniBack II format. This can occur if an existing OmniBack II medium has been partly overwritten by another application. ACTION: In order to use this medium for OmniBack II, you must rst re-initialize the medium. To discard the medium, rst 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 specied position contains an invalid record header which indicates that the block might be corrupted.
10-58
F G & F F G r # # )%%#
Q B & ' %si 'Q 04 $ # & h F F G
e c b Sfd# Ua`
ACTION: No recovery actions are possible. Use a different medium.
MESSAGE:
[MAJOR] [BlockSegment:BlockOffset] Stored/Computed CRC mismatch => block corrupted
DESCRIPTION: The CRC checksum that was computed at backup time does not match the CRC computed during the verify session. The block at the specied position is probably corrupted. ACTION: It is rare that random bit errors can produce this message. Therefore, you must export this medium from the OmniBack II database and discard the medium.
MESSAGE:
[COMMAND ERROR] Can not access the server host.
DESCRIPTION: The le /etc/opt/omni/cell/cell_server is missing. ACTION: Create the Cell Server le and enter in the name of the local Cell Server.
MESSAGE:
[COMMAND ERROR] You do not have permission to start restore.
DESCRIPTION: You tried to perform restore but you have no permission to perform restore.
e c b Sfd# Ua`
F G & F F G r # # DW%%#
Q B & I8 %pi 'Q 0D4 $ # & h F F G
10-59
ACTION: Either add the start restore access right to this user class or transfer this user to a user class that has the start restore access right.
MESSAGE:
[COMMAND ERROR] You do not have permission to start backup.
DESCRIPTION: You tried to start backup but you have no permission to do this. ACTION: Either add the start backup access right to this user class or transfer this user to a user class that has the start backup access right.
MESSAGE:
[COMMAND ERROR] You do not have permission to start datalist backup.
DESCRIPTION: You tried to start datalist backup but you have no permission to do this. ACTION: Either add the start datalist backup access right to this user class or transfer this user to a user class that has the start datalist backup access right.
10-60
F G & F F G r # # )%%#
Q B & ' %si 'Q 04 $ # & h F F G
e c b Sfd# Ua`
MESSAGE:
[COMMAND] Can not start media management Session Manager on host hostname.
DESCRIPTION: You tried to perform a media management operation, but you lack the Media configuration access right. ACTION: Either add the Media configuration access right to this user class or transfer this user to a user class that has the Media configuration access right.
MESSAGE:
[COMMAND] Could not fork process command
DESCRIPTION: The command you specied 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 the omnisv.sh -status command to be sure that the Cell Server is running. 2. Check the /opt/omni/bin directory to be sure that the command is in the directory. 3. Use the ps -ef command to be sure that the process limit of the system has not been reached.
e c b Sfd# Ua`
F G & F F G r # # DW%%#
Q B & I8 %pi 'Q 0D4 $ # & h F F G
10-61
MESSAGE:
[COMMAND] You do not have permission to get logical device information.
DESCRIPTION: You tried to view logical device information, but you lack the Device configuration access right. ACTION: Either add the Device configuration access right to this user class or transfer this user to a user class that has the Device configuration access right.
MESSAGE:
[COMMAND] You do not have permission to get media management information.
DESCRIPTION: You tried to view media management information, but you lack the Media
configuration access right.
ACTION: Either add the Media configuration access right to this user class or transfer this user to a user class that has the Media configuration access right.
MESSAGE:
[COMMAND] You do not have permission to initialize medium.
DESCRIPTION: You tried to initialize medium, but you lack the Media configuration access right.
10-62
F G & F F G r # # )%%#
Q B & ' %si 'Q 04 $ # & h F F G
e c b Sfd# Ua`
ACTION: Either add the Media configuration access right to this user class or transfer this user to a user class that has the Media configuration access right.
MESSAGE:
[CRITICAL] No physical device() specified => aborting
DESCRIPTION: No physical devices have been specied for this logical device. Each logical device must have at least one physical device. ACTION: Verify the conguration of the logical device, and if necessary, modify the logical device.
MESSAGE:
[CRITICAL] Incorrect type of backup - backup must be done with: typeOfBackup
DESCRIPTION: You tried to restore a le using the wrong menu selection. ACTION: To restore a le from a rawdisk backup, use the Restore Single File from Rawdisk menu selection.
e c b Sfd# Ua`
F G & F F G r # # DW%%#
Q B & I8 %pi 'Q 0D4 $ # & h F F G
10-63
MESSAGE:
[CRITICAL] FilesystemMountPoint Not valid mount point => aborting
DESCRIPTION: The lesystem mount point specied by the user is not real mount point on the host running the Disk Agent (VBDA). ACTION: Verify the conguration of the backup object and the table of mounted lesystems on the host running the Disk Agent (VBDA).
MESSAGE:
[CRITICAL] FullPathName Can not open exchanger control device (UnixErrorString)
DESCRIPTION: The Media Agent (xMA) could not open the specied library control device. The error message indicates the reason as reported by the operating system. ACTION: Verify that the control device le exists on the appropriate host and can be accessed by the Media Agent (xMA) process.
MESSAGE:
[CRITICAL] FullPathName Can not preerase (invalid physical device type) => aborting
DESCRIPTION: You can only pre-erase magneto-optical media. The device you selected is not the correct device type. ACTION: Attempt pre-erase operation on magneto-optical media only. Note that not all HP optical drives are capable of pre-erasing an optical platter.
10-64
F G & F F G r # # )%%#
Q B & ' %si 'Q 04 $ # & h F F G
e c b Sfd# Ua`
MESSAGE:
[CRITICAL] FullPathName can not preerase (unknown medium capacity) => aborting
DESCRIPTION: The optical preerase operation failed because the capacity of the medium could not be determined. ACTION: Do not use the pre-erase feature on this optical disk. OmniBack II generally requires that the capacity of a disk is known in order to use and handle it properly. 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 replace the defective disks.
MESSAGE:
[CRITICAL] FullPathName Invalid exchanger control device => aborting
DESCRIPTION: The library control device accessed a device that is not a SCSI-II compliant library. ACTION: Verify the conguration of the logical device. The library control device le probably does not refer to an autochanger picker device.
e c b Sfd# Ua`
F G & F F G r # # DW%%#
Q B & I8 %pi 'Q 0D4 $ # & h F F G
10-65
MESSAGE:
[CRITICAL] FullPathName Invalid physical device type => aborting
DESCRIPTION: The physical device type does not match the device type of the logical device as congured. ACTION: Verify the device type of the physical device in the logical device conguration.
MESSAGE:
[CRITICAL] ShellCommandLine Can not popen() script: (UnixErrorString)
DESCRIPTION: The Media Agent (xMA) could not invoke a subshell script using the popen() system call. The error message indicates the reason as reported by the operating system. ACTION: Verify that the shell command line has the correct syntax and does not contain any inaccessible or non-executable commands. Verify that the host running the Media Agent (xMA) has sufcient resources for the necessary processes.
10-66
F G & F F G r # # )%%#
Q B & ' %si 'Q 04 $ # & h F F G
e c b Sfd# Ua`
MESSAGE:
[CRITICAL] ShellCommandLine Error reading script output (UnixErrorString)
DESCRIPTION: The Disk Agent (xBDA) process detected an error while reading from the pipe through which it is connected with its pre-/post-exec process. The error is probably caused by an ungraceful termination of the script. The error message indicates the reason as reported by the operating system. ACTION: Verify that the shell command line is syntactically correct and does not contain inaccessible or non-executable command invocations. Verify that the executed programs behave as expected and do not produce unexpected results. Test the shell command line manually for possible bugs.
MESSAGE:
[CRITICAL] ShellCommandLine Error reading script output (UnixErrorString)
DESCRIPTION: The Media Agent (xMA) process detected an error while reading from the pipe through which it is connected with its subshell process. The cause is probably an ungraceful termination of the subshell. The error message indicates the reason as reported by the operating system. ACTION: Verify that the shell command line has the correct syntax and does not contain any inaccessible or non-executable commands. Verify that the executed programs work as expected and do not produce unexpected results. Test the shell command line manually for possible bugs.
e c b Sfd# Ua`
F G & F F G r # # DW%%#
Q B & I8 %pi 'Q 0D4 $ # & h F F G
10-67
F G & F F G r # # )%%#
Q B & ' %si 'Q 04 $ # & h F F G
e c b Sfd# Ua`
10-68
MESSAGE:
[CRITICAL] UserName Not Super-User => can not restore raw
DESCRIPTION: You must have the restore as root access right to restore a rawdisk or les from rawdisk. ACTION: Toggle on the access right for restore as root
MESSAGE:
[CRITICAL] Can not determine control device type (FullPathName)
DESCRIPTION: The device accessed by the specied library control device does not respond correctly to the SCSI inquiry command. The error message indicates the reason as reported by the operating system. ACTION: Verify the conguration of the logical device. The library control device le probably 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 message indicates 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-69
e c b Sfd# Ua`
F G & F F G r # # DW%%#
Q B & I8 %pi 'Q 0D4 $ # & h F F G
host.
MESSAGE:
[CRITICAL] Can not fork NETIO process (UnixErrorString) => aborting
DESCRIPTION: The Disk Agent (xBDA) main process is not able to fork its NETIO subprocess. This is possibly due to insufcient system resources on the host running the Disk Agent (xBDA). The error message indicates the reason as reported by the operating system. The most probable cause is insufcient memory or process table full. ACTION: Verify that the host running the Disk Agent (xBDA) has sufcient resources to 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 NETIO subprocess. A possible cause is insufcient system resources on the host running the Media Agent (xMA). The error message indicates the reason as reported by the operating system. The most probable cause is insufcient memory or process table full. ACTION: Verify that the host running the Media Agent (xMA) has sufcient resources to fork and execute another process.
10-70
F G & F F G r # # )%%#
Q B & ' %si 'Q 04 $ # & h F F G
e c b Sfd# Ua`
MESSAGE:
[CRITICAL] Can not initialize pipe connection (UnixErrorString) => aborting
DESCRIPTION: The Disk Agent (xBDA) parent process is not able to open a pipe connection and fork its NETIO process. This is possibly due to insufcient system resources on the host running the Disk Agent (xBDA). The error message indicates the reason as reported by the operating system. ACTION: Verify that the host running the Disk Agent (xBDA) has sufcient resources to 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 pipe connection and fork its NETIO process. A possible cause is insufcient system resources on the host running the Media Agent (xMA). The error message indicates the reason as reported by the operating system. ACTION: Verify that the host running the Media Agent (xMA) has sufcient resources to open the pipe and establish an IPC connection.
e c b Sfd# Ua`
F G & F F G r # # DW%%#
Q B & I8 %pi 'Q 0D4 $ # & h F F G
10-71
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 can not 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 OmniBack II. If the drive is empty, then the internal library status is corrupted and needs to be reset. To x the problem, terminate the OmniBack II session, reset the library, and rescan the library using the OmniBack II rescan feature. NOTE: You can reset the library by either pressing the reset button on the front panel or turning the power off and on.
MESSAGE:
[CRITICAL] Database layer reports [line: code_line, file: code_file]: error_message
DESCRIPTION: The backup session tries to update the database with information, but the information is not accepted. The probable cause is an invalid transaction. In rare cases, this error could indicate a corrupted database. ACTION: Restart the backup. If the error reoccurs, use the omnidbcheck command to check the database.
10-72
F G & F F G r # # )%%#
Q B & ' %si 'Q 04 $ # & h F F G
e c b Sfd# Ua`
MESSAGE:
[CRITICAL] Final BMA acknowledgement missing => backup INCOMPLETE
DESCRIPTION: The Disk Agent (xBDA) was disconnected from the Media Agent before the last pending data block was acknowledged. This indicates that the backup record stream is not complete and the backup can not be regarded as successful. ACTION: The backup will not be completed successfully. You must restart the backup session.
MESSAGE:
[CRITICAL] IPC failure reading NETIO message (UnixErrorString) => aborting
DESCRIPTION: The Media Agent (xMA) main process detected an IPC error reading an incoming NETIO message. The error message indicates the reason as reported 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 reading an incoming Session Manager (SM) message. The error message indicates the reason as reported by the operating system.
e c b Sfd# Ua`
F G & F F G r # # DW%%#
Q B & I8 %pi 'Q 0D4 $ # & h F F G
10-73
ACTION: The session fails. You must restart the session.
MESSAGE:
[CRITICAL] Incorrect type of backup - backup must be done with: TypeOfBackup
DESCRIPTION: You selected "Restore File from Rawdisk" but the backup object you selected was not a rawdisk. ACTION: To restore from a rawdisk, you must select a "rawdisk" backup object. Either select a rawdisk object or select "Restore File from Filesystem."
MESSAGE:
[CRITICAL] Invalid device type specified (LogicalDeviceTypeID) => aborting
DESCRIPTION: The device type congured for this logical device is invalid. ACTION: Verify the conguration of the logical device, and if necessary, modify the logical device.
MESSAGE:
[CRITICAL] Invalid exec code (AgentExecCode) => aborting
DESCRIPTION: Internal Error: The Session Manager tried to execute an invalid or nonexistent agent.
10-74
F G & F F G r # # )%%#
Q B & ' %si 'Q 04 $ # & h F F G
e c b Sfd# Ua`
ACTION: Verify that the inet and Session Manager versions are compatible.
MESSAGE:
[CRITICAL] Invalid storage element requested => aborting. Please verify logical device configuration
DESCRIPTION: The set of repository identiers contains invalid items that do not match the actual repository elements located inside the library. The error was detected while attempting to access an invalid element. ACTION: Verify the layout of the library repository and the conguration of the library.
MESSAGE:
[CRITICAL] MA/NETIO protocol error => aborting
DESCRIPTION: The Media Agent (xMA) main process received an unexpected message type on its NETIO IPC channel. ACTION: The session fails. You must restart the session.
MESSAGE:
[CRITICAL] No datalist in Session Manager command line options or no such datalist exists.
DESCRIPTION: Either an invalid datalist or no datalist was specied.
e c b Sfd# Ua`
F G & F F G r # # DW%%#
Q B & I8 %pi 'Q 0D4 $ # & h F F G
10-75
ACTION: Specify valid datalist and restart the backup.
MESSAGE:
[CRITICAL] No exchanger control device specified => aborting
DESCRIPTION: No SCSI-II library control device has been specied for this logical device. SCSI-II library must have control device to handle medium move commands. ACTION: Verify the conguration of the logical device and, if necessary, modify the logical device.
MESSAGE:
[CRITICAL] Protocol error, can not parse options => aborting
DESCRIPTION: Internal Error: The startup handshake protocol between the OmniBack inet agent and the invoking Session Manager is unsuccessful. ACTION: Verify that the inet and Session Manager versions are compatible.
MESSAGE:
[CRITICAL] SM/MA protocol error => aborting
DESCRIPTION: The Media Agent (xMA) main process received an unexpected message type on its Session Manager (SM) IPC channel.
10-76
F G & F F G r # # )%%#
Q B & ' %si 'Q 04 $ # & h F F G
e c b Sfd# Ua`
ACTION: Verify that the Media Agent (xMA) and Session Manager (xSM) versions are compatible. The session fails. You must restart the session.
MESSAGE:
[CRITICAL] Security violation: Can not switch to uid= in user mode
DESCRIPTION: The user root can be the only member of the user class Admin. This is to prevent network security problems. The error was detected by the inet agent enforcing the security. ACTION: Verify that user root is the only member of the Admin user class.
MESSAGE:
[CRITICAL] The peer_type on host peer_host did not identify itself on startup. Connection will be closed.
DESCRIPTION: An agent must rst identify itself to the Session Manager in order to check compatibility. The problem is probably due to the inet process on the target host being unable to execute the proper agent. ACTION: Check the availability of OmniBack II executables on the target host, their permissions, and the availability of shared libraries.
e c b Sfd# Ua`
F G & F F G r # # DW%%#
Q B & I8 %pi 'Q 0D4 $ # & h F F G
10-77
MESSAGE:
[CRITICAL] Unexpected close reading NETIO message (UnixErrorString) => aborting
DESCRIPTION: The Media Agent (xMA) main process detected loss of connection while reading an incoming NETIO message. The error message indicates the reason as reported by the operating system. ACTION: The session fails. You must restart the session.
MESSAGE:
[CRITICAL] Unexpected close reading SM message (UnixErrorString) => aborting
DESCRIPTION: The Media Agent (xMA) main process detected connection loss while reading an incoming Session Manager (SM) message. The error message indicates the reason as reported by the operating system. ACTION: The session fails. You must restart the session.
MESSAGE:
[CRITICAL] Unexpected error parsing NETIO message (UnixErrorString) => aborting
DESCRIPTION: The Media Agent (xMA) main process detected parsing error while reading an incoming NETIO message. This indicates that the received message was incorrectly formatted. ACTION: The session fails. You must restart the session.
10-78
F G & F F G r # # )%%#
Q B & ' %si 'Q 04 $ # & h F F G
e c b Sfd# Ua`
MESSAGE:
[CRITICAL] Unexpected error parsing SM message (UnixErrorString) => aborting
DESCRIPTION: The Media Agent (xMA) main process detected parsing error while reading an incoming Session Manager (SM) message. This indicates that the received message was incorrectly formatted. ACTION: The session fails. You must restart the session.
MESSAGE:
[CRITICAL] Unknown type of encryption !
DESCRIPTION: There is an error in shared library libde.sl. There is difference between the encryption used for the backup and the encryption used for the restore. Since OmniBack II was unable to deencrypt the le, it restored the le in encrypted form. ACTION: Be sure that the shared library contains the original encryption used for the backup. Then restart the restore.
MESSAGE:
[CRITICAL] Unrecognized option "option" !
DESCRIPTION:
e c b Sfd# Ua`
F G & F F G r # # DW%%#
Q B & I8 %pi 'Q 0D4 $ # & h F F G
10-79
The Session Manager sent an invalid option to the Disk Agent (xRDA). This reason could be that the user specied 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 this host=> aborting
DESCRIPTION: HP OmniBack II requires a user to have a valid Unix "user:group" account in order to start an agent on a host. The error was detected by the inet agent enforcing the security. ACTION: Either create a Unix account for the user on the host, or run the agents in root mode.
MESSAGE:
[CRITICAL] Agent peer_id, version peer_version, is not compatible 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 installed agents on all the hosts in a cell, use the Update All feature of the OmniBack II Install feature.
10-80
F G & F F G r # # )%%#
Q B & ' %si 'Q 04 $ # & h F F G
e c b Sfd# Ua`
MESSAGE:
[CRITICAL] FullPathName Can not compute disk capacity (UnixErrorString) => not backed up
DESCRIPTION: OmniBack II is unable to determine the capacity of the specied rawdisk section. 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 be backed up. ACTION: Run the omnidbcheck -fix command to check the consistency of the database and rebuild index les. If this does not solve the problem, you must restore the database from the latest backup.
MESSAGE:
[CRITICAL] Group "UnixGroupName" non-existent on this host=> aborting
DESCRIPTION: HP OmniBack II does not permit user "user:group" to start an agent on a host where his Unix group does not exist. The error was detected by the inet agent enforcing the security.
10-81
e c b Sfd# Ua`
F G & F F G r # # DW%%#
Q B & I8 %pi 'Q 0D4 $ # & h F F G
ACTION: Either create a Unix group for the user on the host or change the conguration 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 agent on host where he is not member of the specied Unix group. The error was detected by the inet agent enforcing the security. ACTION: Either create Unix group for the user on the host or change the conguration of 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 the popen() system call. The error message indicates the reason as reported by the operating system. ACTION: Verify that the shell command line is syntactically correct and does not contain inaccessible or non-executable command invocations. Verify that the host running the Disk Agent (xBDA) has sufficient resources to execute another process.
10-82
F G & F F G r # # )%%#
Q B & ' %si 'Q 04 $ # & h F F G
e c b Sfd# Ua`
MESSAGE:
[ERROR GUI] Table allocation error. (No more free entries!).
DESCRIPTION: Table allocation error. ACTION: Internal program static tables are used due to several error recovery procedures. Restart the GUI.
MESSAGE:
[Can not get value of the environment variable DISPLAY.
DESCRIPTION: You tried to get the status of a specied cell, but OmniBack II was unable to display 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). To allow access to the client, use the xhost + clientname command.
MESSAGE:
[No valid host running Cell Server daemon located.
DESCRIPTION: You selected a host that is not dened as a Cell Server. ACTION: Dene a host as a Cell Server using the procedures described in the chapter "OmniBack II and IT/OperationsCenter Integration."
e c b Sfd# Ua`
F G & F F G r # # DW%%#
Q B & I8 %pi 'Q 0D4 $ # & h F F G
10-83
MESSAGE:
[NORMAL] No reply from peer_type on host peer_host. Agent identification is peer_version. The connection to the agent will be closed.
DESCRIPTION: The Session Manager was waiting for a reply from Disk Agent or Media Agent. The reply did not arrive before the timeout. ACTION: Restart the operation.
MESSAGE:
[ERROR] sh: /opt/omni/sbin/omnitrig: not found
DESCRIPTION:
omnitrig is missing and crontab has not been updated. This can happen if OmniBack II was removed instead of deinstalled.
ACTION: Manually remove the omnitrig line from the crontab le.
MESSAGE:
[CRITICAL] device name Can not get device file status (error string) =>abborting
DESCRIPTION: Can not get the status of a device le. The device le name is specied at a location where no le can be created. ACTION: Change the specied device le.
10-84
F G & F F G r # # )%%#
Q B & ' %si 'Q 04 $ # & h F F G
e c b Sfd# Ua`
MESSAGE:
[CRITICAL] device name Not a character device or a regular file => aborting
DESCRIPTION: You tried to work with a device that is a block device or the le name specied is not a regular le. ACTION: Change the device le name into a character (raw) device or into a regular le.
MESSAGE:
[MAJOR] device name No access permission for device file => 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 of supported devices.
e c b Sfd# Ua`
F G & F F G r # # DW%%#
Q B & I8 %pi 'Q 0D4 $ # & h F F G
10-85
MESSAGE:
[CRITICAL] Not a BSD device => aborting
DESCRIPTION: You have used a device that is not dened as a Berkley Style Device. ACTION: In the Logical Device Editor change the logical device le name to a BSD device. For more information on creating device le names, see also the Operating 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 le name into a device lename 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 the Logical Device editor, change the device le name appropriately to a device le name with a dened variable block size.
10-86
F G & F F G r # # )%%#
Q B & ' %si 'Q 04 $ # & h F F G
e c b Sfd# Ua`
MESSAGE:
[MAJOR] Can not access blocks after early warning EOT (error string
DESCRIPTION: The medium is at a position after early warning End Of Tape, but blocks are 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 the tape Alert diagnostics) and respond accordingly. 2. The medium can be damaged, so replace it with a new one and restart the operation.
MESSAGE:
[MAJOR] Can not switch to exclusive access
DESCRIPTION: Operating system can not switch to access for just one process. Probably access is already excluded with some other process. ACTION: Wait for other procces to nish, and then restart the operation.
MESSAGE:
[MAJOR] Medium has no capacity.
DESCRIPTION: You tried to backup to medium with no capacity.
e c b Sfd# Ua`
F G & F F G r # # DW%%#
Q B & I8 %pi 'Q 0D4 $ # & h F F G
10-87
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 nished on the specied 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. (error string)
DESCRIPTION: For some reason, the medium position can not be determined. ACTION: Check the disk or magnet-optical device you are using.
10-88
F G & F F G r # # )%%#
Q B & ' %si 'Q 04 $ # & h F F G
e c b Sfd# Ua`
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 whole block. ACTION: You can still use this medium for restore but the data will be successfully read only up to the point where the warning occured.
MESSAGE: [CRITICAL] Attempted read after logical EOD. (error

string)
DESCRIPTION: Position of medium was positioned after the End Of Data where no data block resides. Possibly the medium format is not in the OmniBack II valid format or OmniBack II data is not written properly because of the hardware failure.
e c b Sfd# Ua`
F G & F F G r # # DW%%#
Q B & I8 %pi 'Q 0D4 $ # & h F F G
10-89
ACTION: You can use the medium only for restore because backup information can not 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 to any 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 unable to write on this part of medium.
10-90
F G & F F G r # # )%%#
Q B & ' %si 'Q 04 $ # & h F F G
e c b Sfd# Ua`
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 data written to the end of medium will be lost.
MESSAGE:
[CRITICAL] Can not write to device. Position at physical EOT.
DESCRIPTION: 1. This message occurs when copying a source medium to a target medium with not enough space. 2. OmniBack II can not write catalog data after the early warning end of tape. The size of catalog data to be written between the early warning end of tape and the physical end of tape is too large. ACTION: The catalog data is written to the OmniBack II database, and it can be restored as long as the medium is not exported. If you export the medium, full restore is impossible and some data written to the 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 the error occured.
e c b Sfd# Ua`
F G & F F G r # # DW%%#
Q B & I8 %pi 'Q 0D4 $ # & h F F G
10-91
MESSAGE:
[MAJOR] Can not close after write problem. (error string)
DESCRIPTION: There was situation where OB2 was forced to close a current medium. But there was a problem closing the medium. ACTION: Check the device. If the device functions properly, there is probably a problem 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: Check the device. If the device functions properly, there is probably a problem with a medium. Try to perform backup to another medium.
MESSAGE:
[MAJOR] device name Rewindable device.
DESCRIPTION: There was situation where OB2 was forced to close and reopen a medium. But device was opened as rewindable device which rewinds the medium after close. ACTION: Device must be opened as non-rewindable.
10-92
F G & F F G r # # )%%#
Q B & ' %si 'Q 04 $ # & h F F G
e c b Sfd# Ua`
MESSAGE:
[MAJOR] Skiping write of filemark. (Apparently SCSI bus reset).
DESCRIPTION: A SCSI bus reset has been detected and the medium can be repositioned to any 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 filemark. (error string) DESCRIPTION: For some reason the lemark can not be written. ACTION: Check the device. If the device functions properly, there is probably a problem with a medium. Try to perform backup to another medium.
MESSAGE:
[MINOR] INQUIRY call failed. (error string)
DESCRIPTION: When the INQUIRY call fails, we are unable to nd out what device we are dealing with. ACTION: Check if the device is correctly connected to and recognized by the system.
e c b Sfd# Ua`
F G & F F G r # # DW%%#
Q B & I8 %pi 'Q 0D4 $ # & h F F G
10-93
MESSAGE:
MINOR] REQUEST SENSE call failed. (error string)
DESCRIPTION: When the REQUEST SENSE call fails we are unable to get special information from a device such as the cleanme signal. ACTION: If this occurs at the beginning of a session, check if the device is correctly connected to and recognized by the system. Otherwise, check if there is a device 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: Check the device. If the device functions properly, there is probably a problem with a medium. Try to perform backup to another medium.
MESSAGE:
[MAJOR] Can not backspace segment. (error string)
DESCRIPTION: Device driver can not position medium back for specic number of segments. ACTION: Check the device. If the device functions properly, there is probably a problem with a medium. Try to perform backup to another medium.
10-94
F G & F F G r # # )%%#
Q B & ' %si 'Q 04 $ # & h F F G
e c b Sfd# Ua`
MESSAGE: [MAJOR] Can not forward segment. (error string) DESCRIPTION: Device driver can not position medium forward for specic number of segments. ACTION: Check the device. If the device functions properly, there is probably a problem with a medium. Try to perform backup to another medium.
MESSAGE:
[MAJOR] Can not backspace block. (error string)
DESCRIPTION: Device driver can not position medium back for specic number of blocks. ACTION: Check the device. If the device functions properly, there is probably a problem with a medium. Try to perform backup to another medium.
MESSAGE:
[MAJOR] Can not forward block. (error string)
DESCRIPTION: Device driver can not position medium forward for specic number of blocks. ACTION: Check the device. If the device functions properly, there is probably a problem with a medium. Try to perform backup to another medium.
e c b Sfd# Ua`
F G & F F G r # # DW%%#
Q B & I8 %pi 'Q 0D4 $ # & h F F G
10-95
MESSAGE:
[CRITICAL] Lost position. (error string)
DESCRIPTION: After positionig the medium, a real block position is different. OmniBack II detected that a block of data has been corrupted or not written to the medium. 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: Check the device. If the device functions properly, there is probably a problem with a medium. Try to perform backup to another medium.
10-96
F G & F F G r # # )%%#
Q B & ' %si 'Q 04 $ # & h F F G
e c b Sfd# Ua`
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 II medium.
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 valid format version.
MESSAGE:
[MAJOR] Invalid position specified. (error string)
DESCRIPTION: Medium was positioned to the invalid position. ACTION: Try with segment and/or block specication that do not exceed a maximum number of segments and/or blocks.
e c b Sfd# Ua`
F G & F F G r # # DW%%#
Q B & I8 %pi 'Q 0D4 $ # & h F F G
10-97
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 (error string) => aborting
DESCRIPTION: Can not get important data from BMA like number of buffers, block size and medium header size. ACTION: Restart operation.
10-98
F G & F F G r # # )%%#
Q B & ' %si 'Q 04 $ # & h F F G
e c b Sfd# Ua`
MESSAGE:
[CRITICAL] Device formats are not equal => aborting
DESCRIPTION: You tried to replicate medium BMA and CMA that have not the same format. They are different in block size or number of blocks or size of a medium header. ACTION: Congure both sides of devices for BMA and CMA that have the same formats such as a block size or the number of buffers.
MESSAGE: [CRITICAL] Grau DAS error in function_name(): error

code=#
DESCRIPTION: The API call function_name() failed. Real cause is explained with error codes: 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-99
e c b Sfd# Ua`
F G & F F G r # # DW%%#
Q B & I8 %pi 'Q 0D4 $ # & h F F G
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 by aci_cancel(). ACTION: According to the error code number check the condition of Grau library and restart operation.
MESSAGE:
[MAJOR] Grau DAS error in function_name(): error code=#
DESCRIPTION: The API call function_name() failed. Real cause is explained with error codes: Explanations of error codes:
10-100
F G & F F G r # # )%%#
Q B & ' %si 'Q 04 $ # & h F F G
e c b Sfd# Ua`
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. 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 by aci_cancel().
10-101
e c b Sfd# Ua`
F G & F F G r # # DW%%#
Q B & I8 %pi 'Q 0D4 $ # & h F F G
ACTION: According to the error code number check the condition of Grau library and restart operation.
MESSAGE:
[MINOR] Grau DAS error in function_name(): error code=#
DESCRIPTION: The API call function_name() failed. Real cause is explained with error codes: 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. 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.
10-102
F G & F F G r # # )%%#
Q B & ' %si 'Q 04 $ # & h F F G
e c b Sfd# Ua`
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 by aci_cancel(). ACTION: Current session will not be aborted because of this problem.
MESSAGE:
[CRITICAL] Can not determine element addresses: (error string).
DESCRIPTION: Unable to get element addresses that are neccessary to manipulate with SCSI-II libraries. ACTION: Check the library. If the library still does not respond, try turning it off and on. If this does not help, reboot the system.
e c b Sfd# Ua`
F G & F F G r # # DW%%#
Q B & I8 %pi 'Q 0D4 $ # & h F F G
10-103
MESSAGE:
[CRITICAL] Can not EJECT repository element(s): (no mailslot defined).
DESCRIPTION: SCSI-II Library can not eject the specied medium because Library has no mailslots. ACTION: You can not use the eject operation.
MESSAGE:
[CRITICAL] Can not ENTER repository element(s): (no mailslot defined).
DESCRIPTION: SCSI-II Library can not enter the specied medium because Library has no mailslots. ACTION: You can not use the enter operation.
MESSAGE:
[WARNING] Can not EJECT repository element # into mailslot #: (mailslot is full).
DESCRIPTION: SCSI-II Library can not eject the specied medium into mailslot because it is full. ACTION: Mailslot(s) must be emptied manually.
10-104
F G & F F G r # # )%%#
Q B & ' %si 'Q 04 $ # & h F F G
e c b Sfd# Ua`
MESSAGE:
[WARNING] Can not ENTER repository element # from mailslot #: (slot is full).
DESCRIPTION: SCSI-II Library can not enter a specied medium from a mailslot because all slots are full. ACTION: Eject some media from slots rst and remove them from the Library. Then try with the ENTER operation again.
MESSAGE:
[WARNING] Can not EJECT repository element # into mailslot #: (slot is empty).
DESCRIPTION: SCSI-II Library can not eject the specied medium into mailslot because all slots are empty. ACTION: Enter some media into slots rst. Then you can perform the EJECT operation.
MESSAGE:
[WARNING] Can not ENTER repository element # from mailslot #: (mailslot is empty).
DESCRIPTION: SCSI-II Library can not enter the specied medium from a mailslot because the mailslot is empty. ACTION: Mailslot(s) must be lled manualy.
e c b Sfd# Ua`
F G & F F G r # # DW%%#
Q B & I8 %pi 'Q 0D4 $ # & h F F G
10-105
MESSAGE:
[MAJOR] Can not EJECT repository element # into mailslot #: (error string).
DESCRIPTION: For some reason SCSI-II Library can not eject medium. ACTION: Check the library. If the library still does not respond, try turning it off and on. If this does not help, reboot the system.
MESSAGE:
[CRITICAL] Can not read mailslot status => aborting.
DESCRIPTION: SCSI-II Library does not return any information about the specied mailslot. ACTION: Check the library. If the library still does not respond, try turning it off and on. If this does not help, reboot the system.
MESSAGE:
[CRITICAL] ENTER aborted due to operator inactivity timeout (# secs).
DESCRIPTION: Operator did not ll the specied mailslot with a medium. ACTION: Try the operation again and this time ll the specied mailslot with a medium.
10-106
F G & F F G r # # )%%#
Q B & ' %si 'Q 04 $ # & h F F G
e c b Sfd# Ua`
MESSAGE:
[CRITICAL] EJECT aborted due to operator inactivity timeout (# secs).
DESCRIPTION: Operator did not empty the specied 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 function function_name() did not reply with a correct sequence number. This is a problem in API protocol. ACTION: Check if StorageTek library and the server system are congured correctly.
MESSAGE:
[CRITICAL] StorageTek ACS error in function_name(): primary status : secundary status.
DESCRIPTION: When working with StorageTek Library the API function function_name() returned primary status instead of secundary status. ACTION: According to the returned status, check the StorageTek library and restart operation.
e c b Sfd# Ua`
F G & F F G r # # DW%%#
Q B & I8 %pi 'Q 0D4 $ # & h F F G
10-107
MESSAGE:
[WARNING] OB2CLEANME setting is obsolete. You must configure dirty drive detection in logical device configuration.
DESCRIPTION: In le .omnirc the OB2CLEANME variable that is obsolete is dened. ACTION: For detection of a dirty drive you must congure the dirty drive in the logical device conguration.
MESSAGE:
[WARNING] OB2BLKSIZE setting is obsolete. You must configure block size in logical device configuration.
DESCRIPTION: In le .omnirc the OB2BLKSIZE variable that is obsolete is dened. ACTION: For dening a block size you must congure the block size in the logical device conguration.
MESSAGE:
[WARNING] OB2BARCODE setting is obsolete. You must configure barcode reader support in logical device configuration.
DESCRIPTION: In le .omnirc is dened variable OB2BARCODE that is obsolete.
10-108
F G & F F G r # # )%%#
Q B & ' %si 'Q 04 $ # & h F F G
e c b Sfd# Ua`
ACTION: To scan a library with barcodes you must congure a barcode reader support in the logical device conguration.
MESSAGE:
[WARNING] Block size setting of #KB is too big. Maximum allowed block size for this device type is #KB.
DESCRIPTION: The block size you set in the device conguration is too big. ACTION: Change the device conguration with a smaller block size. A maxium block 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 already mounted but OmniBack did not succeed to dismount the busy drive. ACTION: You must congure a drive busy hadling to eject a medium or eject medium to a mailslot in the logical device conguration. If that does not succeed you must dismount a drive manualy.
MESSAGE:
[NORMAL] Successfuly dismounted busy drive #.
DESCRIPTION: OmniBack mounted a medium into a drive that was already mounted and successfuly dismounted
e c b Sfd# Ua`
F G & F F G r # # DW%%#
Q B & I8 %pi 'Q 0D4 $ # & h F F G
10-109
MESSAGE:
StorageTek ACS error in acs_mount:STATUS_UNREADABLE_LABEL
DESCRIPTION: The medium sticker label somehow fell of the medium. This causes the ACS software to report an error, and OmniBack II session is aborted after the error message is displayed. ACTION: Open the autochagner device and x the medium sticker label. After that, rescan the autochanger from the OmniBack II GUI.
10-110
F G & F F G r # # )%%#
Q B & ' %si 'Q 04 $ # & h F F G
e c b Sfd# Ua`
Glossary
This glossary contains definitions and additional information about words and phrases used in HP OpenView OmniBack II.
access permissions Unix File name characteristics (such as read, write, and execute) that determine whether a user can perform an operation on a file (such as opening a file for writing). This is different from access rights that control which tasks an OmniBack II user can perform. access rights The permission to perform specific backup and restore tasks, such as handling mount prompts. Users have the access rights of the user class to which they belong. ACS pool Used to optimally manage and control StorageTek Library systems. CDF file Context Dependent File. A context dependent file consists of several files grouped under the same pathname. The system ordinarily selects one of the files using the context of the process. This mechanism allows machine dependent executable, system data, and device files to work correctly from all hosts in a cluster while using the same path name. cell A local part of the network. The system administrator groups several workstations, hosts, devices, and other items necessary for backup into a cell to more easily manage backup and restore operations. A cell typically represents a location or organizational structure. Backup and restore policies and
schedules are defined on the cell level. This lets system administrators customize the backup and restore functions for each cell. By default, a cell does not cross LAN boundaries. Also known as "domain." cell configuration Setting up hosts, pools, and devices for a cell and defining the services and policies for the cell. Once configured, a cell can be controlled from a single workstation, the Cell Server. Cell Server This is the workstation from which a cell is managed. It includes a User Interface, several session managers, all configuration files, and the OmniBack II log database. client A computer on a network that receives service from another computer (server). For example, a communication server connects clients to other communications networks such as local area networks (LANs). (See server.) complex device See Device Chains, Libraries, or Stackers. concurrency Media multiplexing. This device option allows more than one Disk Agent (up to five) to write to one backup device. This helps OmniBack II keep the media streaming when the device can accept data faster than a disk can send it. OmniBack II provides defaults for each device type supported condition The quality and reliability of a medium. Heavy usage and age result in increased read and write errors. Media should be replaced when the condition
Glossary-i
Glossary
field indicates POOR. control device The device file used to control the robotic arm which moves the media between the repository slots and the read-write mechanism of an library. DAS pool Is used to optimally manage and control GRAU systems. daemon A memory resident program that is constantly running. The OmniBack II daemon facilitates communications in the network so that OmniBack II can access different parts of the network at any time. database server A computer with a large database stored on it. A server has a database that can be accessed by client workstations. (See also Client). datalist A list of objects to be backed up. These objects can be files or directories. OmniBack II backs up the objects in the datalist. default entry A datalist entry that establishes default values for a group of objects. default selection An object or action that is used when no other selection is specified. device A unit that contains stored data for backup or recovery. See also Complex Device and Source Device. detail catalog A catalog in the OmniBack II database containing the detail information from backup and
restore sessions. You can delete this catalog if you run out of disk space and you will still be able to restore all files backed up, but it will take longer. Disk Agent The OmniBack II software module that controls reading from and writing to a disk. During a backup session, the Disk Agent sends data from the disk to the Media Agent which then stores the data to the media. During a restore session, the Disk Agent takes data received from the Media Agent and writes it to the disk. OmniBack II only backs up those systems which have the Disk Agent module installed. JFS Journaled File System that allows you to back up a file system while it is being backed up by some other application. This is called an online backup and is done by creating a snapshot of the file system and backing up that snapshot. export host To remove a host from the Cell Configuration without deinstalling the OmniBack II modules that are on this host. This action allows you to move a host from one cell to another without deinstalling and reinstalling the OmniBack II modules. You export the host from one cell and import the host to another cell. export medium To remove all information about a backup medium and its contents from the OmniBack II database of a cell. Once a medium is exported, OmniBack II no longer has information about either the medium itself (for example, its location) or what
Glossary-ii
Glossary
backup sessions (and files) are contained on this medium. Use this option when the medium is no longer to be used for backup in a cell. Data on the medium remains unchanged. See also import medium. filter Criteria which let you selectively display information in OmniBack II windows. Use filters to define a view of session activities based on a specific session owner or type of media session (backup, restore). If you use a filter to display names, OmniBack II generally allows you to use wildcards to view a particular pattern. force initialization To erase any data contained on a medium and format the medium as an OmniBack II medium. full backup A backup in which all selected objects on all selected hosts are backed up whether or not they have been modified recently. This contrasts with incremental backup. host A server with workstations including the disks and disk drives of the workstations. hostname The name of a system on the network. host backup A dynamic backup of all filesystems configured in a host. Host backup simplies datalist
export host. import medium Returns all information about a backup and its contents medium to the OmniBack II database of a cell. See also export medium. IP Address The numeric address of a host. The IP address consists of 4 groups of numbers: the first three groups of numbers represent the number of the internet network and the last group of numbers represents the local network address. IPC address See IP Address.
incremental backup A backup in which only objects changed since a recent full backup are copied. Related to full backup. label A user-defined identifier used to describe a backup medium. LAN An acronym for Local Area Network. The hosts and/or clusters which share data, hardware, and software resources via Networking Services software. libraries Also called autochangers, jukeboxes, etc. Standalone storage devices. A library contains a library system of media which are held in repository slots. Each slot holds one medium (for example, DAT tape or magneto-optical platter). The library provides access to a vast library of data within a few seconds without operator intervention. To read a medium, an electro-mechanical arm guided by the
conguration and improves backup coverage of systems that often mount/dismount various disks.
import host Adds an already installed host to an OmniBack II cell. See also
Glossary-iii
Glossary
host computer selects, moves, rotates, and inserts tape or optical cartridges into the drive mechanism(s) mounted inside the cabinet. library data device A data storage device. This device includes repository slots, a read mechanism, and a robotic arm which moves media between the repository slots and the read mechanism. libraries pool Used to optimally manage and control large SCSI II libraries. library repository slots Make up a library repository. Each slot holds one storage medium, for example, DAT tape or magneto-optical platter. OmniBack II references each slot by a number. To read a medium, a control arm removes the medium from a slot and inserts it in the read mechanism. load balancing Dynamic allocation of devices. If you select this option, OmniBack II will automatically connect backup objects to available devices. location The physical location of the backup media (for example, "building 4" or "offsite storage"). logical device A set of physical devices treated and accessed as if they are one device. A logical device consists of devices of the same type (such as DAT, optical, or Exabyte) and usage policy. magazine pool Used to optimally manage and control small library devices
such as HP SureStore 12000e. A magazine pool also supports the use of cleaning tapes. media Physical objects upon which data is recorded such as DAT tapes or optical disks. You save or back up data to media. The plural of medium. Media Agent The OmniBack II software module that controls reading from and writing to a media drive. During a backup session, the Media Agent writes to media the data it has received from the Disk Agent. During a restore session, the Media Agent locates data on the backup media and sends the data to the Disk Agent. The Disk Agent then writes the data to the disk. media allocation policy Determines in which order media are accessed within a pool. Strict allocation policy directs OmniBack II to prompt for a specific medium. Loose directs OmniBack II to prompt for any suitable medium. media capacity See medium capacity media class The format of the media (for example, DAT) media condition factors The userassigned age threshold and usage threshold used to calculate the probable condition of the medium. The following terms describe the condition: Good = indicates less than 80% of thresholds for age or usage
Glossary-iv
Glossary
Fair = indicates 81-100% of the thresholds for age or usage Poor = indicates more than 100% of the thresholds for age or usage Default values for the thresholds are provided by OmniBack II. media ID A unique identifier assigned by OmniBack II to a medium. media label See label.
restored to a destination. If files exist in the destination path, those with the newer date are kept. Not existing files are always restored to the destination path. See also overwrite. mount To add an auxiliary (removable) file system to an active existing file system. mount prompt A screen prompt that tells the user to put media online. This prompt appears in the status field of the monitor windows. When a mount prompt has been answered, the status field changes to in progress. mount point The access point to the data in the directory structure. object An entity such as a directory, file, filesystem, or database that is used in a backup. overwrite Defines how files are restored to a destination. All files are restored from the backup even if they are older than existing files. See also merge. permissions Unix file characteristics (such as read, write, or execute) that determine whether you can perform a certain operation on the file (such as writing to a file). pool (See media pool) pool attributes Attributes that define the characteristics and use of a pool. Different pool types have different attributes.
media management A tool that allows you to track your backup media and backup/restore history. Media management also protects your data by helping to prevent accidental overwriting of data. media pool A set of similar media (DATs, Exabytes, etc.) used and tracked as a group. Media in a pool must be the same media class (for example, DAT). Media are initialized and assigned to a media pool. See also standard pool, magazine pool, library pool, ACS pool, and DAS pool. medium (See media.) medium capacity The space available on a medium before any data is written to the medium. If determine is selected, OmniBack II determines the media capacity for that media type (for example, DAT). If specify is selected, OmniBack II uses the capacity that you specify when you initialize the medium. merge Defines how the files are
Glossary-v
Glossary
pre-exec An option that instructs OmniBack II to process a command or script before it backs up an object or a session is started. post-exec An option that instructs OmniBack II to process a command after the backup of an object or a session is completed. recycle OmniBack II keeps track of data on every used medium. Recycling removes data protection from the data backed up, thus allowing OmniBack II to overwrite data in the next backup. The data on the media remains unchanged until the next backup. remote pre-exec An option that instructs OmniBack II to process a command or script on a remote host before it backs up an object or a session is started. remote post-exec An option that instructs OmniBack II to process a command on a remote host after the backup of an object or a session is completed. repository slots See library repository slots. rescan A logical device function that checks each slot of a library to identify the media and update the media management database with this information. If someone has manually removed or switched media, do a rescan. Rescanning lets OmniBack scan all the slots in the library, confirm what medium is present in each slot, and update and correct any inconsistencies
within the media management database. scheduler The function that controls how often and when backups occur. By setting up a schedule for a datalist, you can automate your backups to run periodically at times of low system usage. With the scheduler, the backups you set up will run on the days and at the times you specify without your attendance as long as the devices and media are properly set. server A computer on a network that provides service to terminals on the network (clients) by managing an expensive shared resource. For example, a file server manages a set of disks and provides storage services to computers (clients) on the network that may not have their own disks. Sometimes a server is a dedicated computer. (See also client.) session A major operation of OmniBack II such as backup or restore. Each session is monitored and controlled by a Session Manager. source device The mass storage unit from which OmniBack II is to be installed or updated, for example, a cartridge tape, a DDS, or a CD-ROM. standard pool Used to manage standalone devices, such as DATs, jukeboxes, or small external libraries. User Interface The user interface of OmniBack II. It usually runs on the Cell Server but can also be installed on any system in the cell.
Glossary-vi
Glossary
verify A function that lets you check whether or not the data on a specified medium is consistent or valid. This function reads all blocks, checks the headers, parses all Media Agent blocks, and checks every record within the block.
Glossary-vii
Glossary
Glossary-viii
Index
A access rights for OmniBack II users, 3-38 ACL for OmniBack II users, 3-38 adding media to pool, 3-28 allocation policy, 3-16 ANSI media format compatibility, 3-18 architecture cell, 1-3 Disk Agent, 1-4 layers, 1-4 Media Agent, 1-4 OmniBack II, 1-3 automating mount prompt handling, 7-3 auxiliary devices, 3-21 B backing up a host, 3-6, 4-18 a rawdisk, 3-6, 4-13 existing datalist, 4-20 in incremental mode, 3-7 OmniBack II network, 1-2 selected filesystem, 4-8 the secondary Cell Server (MC/ServiceGuard), 7-41 backing up your system, 4-1 backup changing ownership, 4-34 choosing mode of backup, 3-6 configuring a filesystem backup, 4-8 dynamic host backup, 4-17 incremental, 3-7 interactive, 4-20 load balancing datalists, 4-36 monitoring sessions, 6-3
periodic schedule, 4-45 planning backup strategy, 3-5 post-exec commands, 7-6 pre-exec commands, 7-6 previewing, 4-24 recovering failed backup, 7-14 reporting through WWW server, 7-42 restarting failed backup, 7-15 scheduling, 4-41 scheduling on a specific date, 4-43 selecting a type, 3-5 selecting rawdisk backup options, 4-15 selecting rawdisk sections, 4-14 skipping on holidays, 4-47 starting, 4-24 with load balancing, 4-37 backup devices configuring and using, 3-21 backup mode, 3-6 choosing, 3-6 full, 3-6 incremental, 3-7 backup objects changing the view at restore, 5-4 selecting, 3-9 selecting at restore, 5-5 backup options, 4-26 compressing data, 4-29 description, 4-29 encryption, 4-29 for device, 4-33 for filesystems, 4-11 ignoring hard links, 4-32 load balancing, 4-30 locking files during backup, 4-32 loging files to database, 4-31 pre/post-exec commands, 4-32, 7-6 preserving access time attributes, 4-32 private data, 4-30
Index-i
Index
protecting data, 4-33 protection, 3-10 public data, 4-30 reconnecting broken connections, 4-30 report level, 4-31 backup ownership changing, 4-34 backup protection, 3-10 backup reporting through WWW server, 7-42 backup schedule changing date, 4-47 clearing, 4-47 editing a daily or monthly backup schedule, 447 example, 3-8 types of, 3-10 backup session deleting from a database, 7-24 display of status, 4-22 how does it work, 1-5 operating, 1-5 previewing, 4-24 backup sessions status, 4-22 backup strategy planning, 3-5 backup type filesystem, 3-5 host, 3-6 rawdisk, 3-6 selecting, 3-5 barcodes quick scan using barcodes, 3-34 barlist understanding, 4-4 what is a barlist, 4-4 BIDB protection of backup information, 8-6 broken connections
reconnecting, 4-40 browsing directories for restore, 5-7 files for restore, 5-7 C catalogue retention, 8-6 CDB synchronizing with MMDB, 8-10 CDF files detection, 7-18 cell, 2-2 access planning, 3-11 Cell Server and clients, 1-3 configuring, 3-1 deinstalling OmniBack II from hosts, 2-11 exporting hosts, 2-8 importing hosts, 2-6 importing hosts wirh multi-LAN cards, 2-8 planning, 3-3 planning backup strategy, 3-5 upgrading OmniBack II software, 2-10 what is a cell, 1-3 cell access planning, 3-11 Cell Server, 1-4 moving, 7-36 recovering, 7-31 starting with MC/ServiceGuard, 7-41 what is a Cell Server, 1-3 Cell Server Package configuring with MC/ServiceGuard, 7-40 changing backup ownership, 4-34 datalist, 4-7 max. number of running session, 4-42 the view of backup objects, 5-4 choosing backup mode, 3-6
Index-ii
Index
cleaning tape, 3-22 client recovering after disaster, 7-30 updating, 2-10 what is a client, 1-3 client hosts importing to the cell, 2-6 clients installing Omniback II software, 2-4 Command Line Interface, 1-11 using, 1-11 commands, 1-11 completed sessions viewing details, 6-6 complex device types device chains, 9-3 functions, 9-4 libraries, 9-3 OmniBack II operating on complex devices, 9-4 stackers, 9-3 complex devices managing, 9-3 complex devices and libraries, 9-1 what are they, 9-2 components of OmniBack II, 1-4 compressing data, 3-13, 4-29 compression algorithm customizing, 7-50 compression module customizing, 7-50 concept of OmniBack II, 1-3 concurrency, 4-34 configuring a cell, 3-1 appearance of GUI, 1-9 data compression, 3-13
data encryption, 3-13 drives for the SCSI-II library, 9-10 dynamic host backup, 4-17 logical devices, 3-21, 3-23 media management, 3-14 non-standard libraries, 9-12 pre/post-exec commands for a datalist/barlist, 7-6 SCSI II library device, 3-26 SCSI-II library, 9-7 standalone devices, 3-25 user classes, 3-36 users, 3-36, 3-41 configuring a cell, 3-1 overview, 3-1 configuring devices non-standard libraries, 9-13 congiguring backup with load balancing, 4-37 constraints with copying media, 7-27 copied media exporting, 7-27 importing, 7-27 copying media of backup sessions, 7-26 media of restore sessions, 7-27 copying media general constraints, 7-27 corrupted files restoring older versions, 5-8 cpio format compatibility, 3-18 crash recovering a Cell Server, 7-31 CRC Check, 4-33 creating datalist for interactive backup, 4-23 datalist from scratch, 4-6 encryption code module, 7-45, 7-51
Index-iii
Index
media pools, 3-28 critical system example of recovering, 7-32 recovering, 7-32 currently running sessions viewing details, 6-3 customizing compression module, 7-50 device and media management view, 7-28 encryption module, 7-45 OmniBack II, 7-1 periodic schedule, 4-46 D data compressing, 3-13, 4-29 encrypting, 3-13, 4-29 protecting, 4-33 database adding to datalist, 8-13 backing up, 8-13 copying to an ASCII file, 8-9 deleting a session, 7-24 enlarging the size, 8-10 managing growth, 8-4 protection of backup information, 8-6 reading database from ASCII file, 8-9 restoring, 8-14 shrinking the file, 8-9 synchronizing MMDB and CDB, 8-10 datalist automatical configuring, 4-5 automatical generating, 4-5 changing, 4-7 changing backup ownership, 4-34 creating, 4-6 for interactive backup, 4-23 load balancing, 4-36 modifying, 4-7
previewing backup, 4-24 scheduling backup on a specific date, 4-43 scheduling periodic backup, 4-45 skipping backup during holidays, 4-47 starting interactive backup, 4-20 understanding, 4-3 DCE Enterprise File System with OmniBack II, 7-23 deinstalling OmniBack II from hosts, 2-11 OmniBack II Modules, 2-11 deleting a session from a database, 7-24 a session from media, 7-24 description of backup options, 4-29 detecting CDF files, 7-18 device backup options, 4-33 device and media management view customizing, 7-28 modifying, 7-28 device chains operating, 9-4 device configuration non-standard libraries, 9-13 device options concurrency, 4-34 CRC check, 4-33 media pool, 4-34 prealloc list, 4-34 devices about logical devices, 3-21 auxiliary devices, 3-21 cleaning tape support, 3-22 configuring, 3-21 configuring logical devices, 3-23 configuring SCSI II library, 3-26
Index-iv
Index
configuring standalone devices, 3-25 device chains, 9-3 libraries, 9-3 locking when in use, 3-23 managing complex devices, 9-3 modifying the view, 3-35 primary devices, 3-21 stackers, 9-3 devices and libraries complex, 9-1 directory version selecting for restore, 5-8 dirty drives cleaning tape support, 3-22 disabling CDF files detection, 7-18 disaster preparing for a disaster, 7-30 recovering a Cell Server, 7-31 recovering a client, 7-30 recovering from a disaster, 7-34 disaster recovery, 7-29 Disk Agent, 1-4 display statistical information restore options, 5-13 distributing OmniBack II software to clients, 2-4 E enabling CDF files detection, 7-18 encrypting data, 3-13, 4-29 encryption algorithm customizing, 7-45 encryption code module configuring, 7-45, 7-51 creating, 7-45, 7-51 encryption module
customizing, 7-45 Enterprise File System with OmniBack II, 7-23 erasing a medium from a media pool, 3-29 error messages, 10-2 exclude restore options, 5-11 excluding OmniBack II database directories, 4-10 exporting copied media, 7-27 hosts from the cell, 2-8 media from pool, 3-32 exporting hosts from the cell why, 2-6 F failed backup, 7-15 recovering, 7-14 restarting, 7-15 failed host backup, 7-15 file restore specifying options restoring from a rawdisk, 526 file restore from a radisk selecting files, 5-24 file restore from a rawdisk starting and monitoring, 5-27 file version selecting for restore, 5-8 files browsing for restore, 5-7 configuring backup, 4-8 locking during backup, 4-32 lost, 5-8 selecting for restore, 5-6 fileset restore options specifying, 5-9
Index-v
Index
filesystem configuring backup, 4-8 excluding OmniBack II database directories, 4-10 selecting backup options, 4-11 selecting for backup, 4-8 filesystem backup, 3-5 configuring, 4-8 restoring, 5-4 filesystem backup options, 4-11 full backup mode, 3-6 schedule example, 3-8 functionality MC/ServiceGuard, 7-38 G generating datalists, 4-5 global options modifying, 7-13 global options file InitOnLoosePolicy, 3-19 MaxBSessions option, 4-42 MAXGUIMSG, 4-21 Graphical User Interface, 1-8 modifying the appearance, 1-9 starting, 1-9 using, 1-8 GUI, 1-8 H help online help, 1-9 holidays skipping backup, 4-47 host backing up, 4-18 host backup, 3-6, 4-18
configuring, 4-17 failed, 7-15 retrying, 7-14 selecting, 4-18 hosts deinstalling, 2-11 deinstalling OmniBack II, 2-11 exporting from the cell, 2-8 importing, 2-6 importing hosts with MC/ServiceGuard, 2-8 importing hosts with multi-LAN cards, 2-8 importing to the cell, 2-6 moving between cells, 2-6 updating modules, 2-10 HP-UX 10.x Journaled File System (JFS,VxFS), 7-19 HP-UX filesystem format compatility, 3-18 I ID media, 3-20 ignoring hard links, 4-32 importing copied media, 7-27 hosts to the cell, 2-6 hosts with MC/ServiceGuard, 2-8 hosts with Multi-LAN cards, 2-8 media to media pool, 3-33 importing hosts to the cell why, 2-6 improved backup performance VxFS, 7-20 improved disaster recovery, 7-29 incremental backup, 3-7 levels of, 3-7 mode, 3-7 scheduling example, 3-8 what to back up, 3-9 indentifying
Index-vi
Index
media, 3-20 information about media viewing, 3-30 initializing media in pool, 3-28 InitOnLoosePolicy, 3-19 installing deinstalling OmniBack II from hosts, 2-11 new OmniBack II version, 2-10 OmniBack II software to clients, 2-4 installing OmniBack II overview, 2-2 integrating OmniBack II reporting with Netscape Communication Server, 7-43 interactive backup, 4-20 creating a temporary datalist, 4-23 of existing datalist, 4-20 running, 4-20 J JFS, 7-19 concepts, 7-19 limitations, 7-20 restoring, 7-21 script templates, 7-21 Journaled File System concepts, 7-19 limitations, 7-20 L label media, 3-20 LAN cards importing hosts with Multi-LAN cards, 2-8 last version of a file restoring, 5-8 libraries operating, 9-6
library devices configuring, 3-26 list restored objects restore option, 5-13 load balancing, 4-30 configuring, 4-40 configuring backup, 4-37 configuring broken connections, 4-40 periodical backup, 4-44 what is, 4-36 locating files, 5-7 lock files restore option, 5-13 locking devices in use, 3-23 files during backup, 4-32 logging files to databse, 4-31 logical devices, 3-21 about logical devices, 3-21 auxiliary devices, 3-21 concept, 3-21 configuring, 3-21, 3-23 configuring SCSI II library device, 3-26 configuring standalone device, 3-25 device locking when in use, 3-23 locking devices when in use, 3-23 primary devices, 3-21 using, 3-21 lost files restoring, 5-8 M managing complex devices, 9-3 media, 3-14 MaxBSessions global option, 4-42 MAXGUIMSG global option, 4-21 MC/ServiceGuard, 7-38 backing up the secondary Cell Server, 7-41
Index-vii
Index
configuring, 7-38 configuring Cell Server Package, 7-40 configuring primary Cell Server, 7-39 configuring secondary Cell Server, 7-39 functionality, 7-38 importing hosts with MC/Service, 2-10 importing hosts with MC/ServiceGuard, 2-8 prerequisites for configuration, 7-39 starting a Cell Server, 7-41 media adding to pool, 3-28 compatibility, 3-18 compatibility with other formats, 3-18 copying, 7-25 creating media pool, 3-28 erasing, 3-29 exporting from media pool, 3-32 ID, 3-20 identification, 3-20 importing to a media pool, 3-33 initializing media in pool, 3-28 label, 3-20 media management tasks, 3-27 media pools, 3-14 modifying, 3-30 modifying the view, 3-35 moving, 3-31 recycling, 3-32 removing protection, 3-32 scanning, 3-34 verifying, 3-29 viewing information about media, 3-30 Media Agent, 1-4 media allocation policy, 3-16 media class, 3-16 media compatibility managing, 3-18 media condition factors, 3-17 media information
viewing, 3-30 media management, 3-14 media of backup sessions copying, 7-26 media of restore sessions copying, 7-27 media pool, 3-14, 4-34 exporting media, 3-32 initializing media, 3-28 media pool attributes, 3-17 media allocation policy, 3-16 media class, 3-16 media pools adding media, 3-28 creating, 3-28 description, 3-15 erasing media, 3-29 importing media, 3-33 modifying media, 3-30 moving media, 3-31 pool name, 3-15 scanning media, 3-34 verifying media, 3-29 what are, 3-14 media protection removing, 3-32 media usage policy, 3-17 merge restore option, 5-12 messages, 10-2 about errors, 10-2 messages field backup status description, 4-22 viewing messages at restore, 5-17 MMDB synchronizing with CDB, 8-10 mode of backup, 3-6 full, 3-6 incremental, 3-7
Index-viii
Index
modifying appearance of GUI, 1-9 backup ownership, 4-34 datalist, 4-7 Device & Media Management view, 3-35 global options, 7-13 media, 3-30 number of running sessions, 4-42 reconnect parameters, 4-40 monitoring a rawdisk restore, 5-22 completed sessions, 6-5 multiple cells, 6-7 running sessions, 6-3 several cells, 6-7 viewing details of a running session, 6-3 mount prompt automatic handling, 7-3 responding, 5-23 mount prompt handling automating, 7-3 mount prompt scripts examples, 7-4 mount request, 7-3 responding, 5-23 move busy files restore option, 5-13 moving Cell Server, 7-36 media, 3-31 multi-LAN cards importing hosts to a cell, 2-8 multiple cells monitoring, 6-7 N Netscape Communication Server integrating with OmniBack II reporting, 7-43 network load, 5-16
no overwrite restore option, 5-12 non-standard libraries configuring, 9-12 device configuration, 9-13 operating, 9-12 non-standard OmniBack II tasks and concepts, 7-1 O OB2RECONNECT_ACK option, 4-40 omit deleted files restore options, 5-13 OmniBack II architecture, 1-3 backing up a database, 8-13 backup session, 1-5 catalogue retention, 8-6 CDF files, 7-18 Cell Server, 1-3 clients, 1-3 commands, 1-11 components, 1-4 copying database to ASCII file, 8-9 customizing, 7-1 data compression, 3-13 deinstalling hosts, 2-11 deleting a session from database, 7-24 distributing to clients, 2-4 error messages, 10-2 exporting hosts, 2-8 filesystem backup, 4-8 global options file, 7-13 Graphical User Interface, 1-8 graphical user interface, 1-8 HP OperationsCenter configuring, 3-11 importing hosts, 2-6 installation overview, 2-2 logical devices, 3-21
Index-ix
Index
online help, 1-9 planning backup strategy, 3-5 reading database from ASCII file, 8-9 restore session, 1-6 restoring database, 8-14 shrinking the database, 8-9 starting GUI, 1-9 supporting HP EFS, 7-23 supporting MC/ServiceGuard, 7-38 updating modules, 2-10 what is a cell, 1-3 with JFS (VxFS) on HP-UX 10.0, 7-19 OmniBack II database enlarging the size, 8-10 excluding from ordinary backup, 4-10 managing the growth, 8-4 moving to another system, 8-17 OmniBack II Modules deinstalling, 2-11 OmniBack II network backing up, 1-2 omnirc file OB2RECONNECT_ACK option, 4-40 OB2RECONNECT_RETRY option, 4-40 OmniStorage format compatibility, 3-18 online help using, 1-9 operating device chains, 9-4 libraries, 9-6 non-standard libraries, 9-12 stackers, 9-5 operation backup session, 1-5 Graphical User Interface, 1-8 restore session, 1-6 options for running backup, 4-26 pre-and post-exec commands, 7-6
protection of data, 3-10 restore, 5-9 overriding scheduled backup options, 4-48 overriding of scheduled backup options undoing, 4-49 overview of restores, 5-3 overwrite restore option, 5-12 ownership changing, 4-34 P parallel restore, 5-18 performing full backup, 3-6 periodic schedule customizing, 4-46 periodical backup setting, 4-44 planning backup strategy, 3-5 cell, 3-3 cell access, 3-11 OmniBack II cell, 3-3 pool attributes description, 3-15 media allocation policy, 3-16 media class, 3-16 media condition factors, 3-17 media usage policy, 3-17 pool name, 3-15 pools creating, 3-28 exporting media, 3-32 importing media, 3-33 what is a media pool, 3-14 post- exec
Index-x
Index
restore option, 5-14 post-exec commands, 4-32, 7-6 pre/post-exec commands for an object, 7-11 on a local host, 7-10 on a remote host, 7-10 pre/post-exec commands for a datalist/barlist configuring, 7-6 prealloc list, 4-34 predefined periodic schedule selecting, 4-45 pre-exec commands, 4-32, 7-6 restore option, 5-14 preparing for a disaster, 7-30 prerequisites configuring MC/ServiceGuard, 7-39 preserving access time attributes, 4-32 previewing backups, 4-24 previous sessions viewing, 6-5 primary logical devices, 3-21 primary Cell Server configuring with MC/Service Guard, 7-39 private data, 4-30 protection of backed up data, 3-10 of backup information, 8-6 protection attributes restore option, 5-12 protection of media removing, 3-32 public data, 4-30 R rawdisk configuring backup, 4-13 selecting rawdisk backup options, 4-15
selecting rawdisk sections for backup, 4-14 rawdisk backup, 3-6 configuring, 4-13 rawdisk restore restoring files from a rawdisk backup, 5-24 selecting files from a rawdisk restore, 5-24 specifying options for file restore, 5-26 starting and monitoring, 5-22, 5-24 rawdisk restore options specifying, 5-21 rawdisk section choosing for restore, 5-20 restoring, 5-20 selecting for restore, 5-20 reconnect parameters modifying, 4-40 reconnecting broken connections, 4-40 reconnecting broken connections, 4-30 recovering a Cell Server, 7-31 a client system, 7-30 a critical system, 7-32 a failed backup, 7-14 data after disaster, 7-29 from a disaster, 7-34 recovering Celll Server Package configuring with MC/ServiceGuard, 7-40 recurring backups, 3-10 recycling media, 3-32 removing protection of media, 3-32 report level, 4-31 reporting about backups through WWW server, 7-42 reporting scripts using, 7-43 responding to mount prompt request, 5-23
Index-xi
Index
to mount request, 5-23 restarting failed backup, 7-15 restore monitoring sessions, 6-3 network load, 5-16 options for file restore from rawdisk, 5-26 restore as option, 5-10 running, 5-15 searching for files, 5-18 selecting files, 5-6 starting, 5-15 starting and monitoring, 5-15 target hostname option, 5-12 restore into restore option, 5-10 restore options display statistical information, 5-13 exclude, 5-11 for fileset, 5-9 list restored objects, 5-13 lock files, 5-13 match entire filename, 5-10 merge, 5-12 move busy files, 5-13 no overwrite, 5-12 omit deleted files, 5-13 overwrite, 5-12 post- exec, 5-14 pre- exec, 5-14 protection attributes, 5-12 restore as, 5-10 skip, 5-11 sparse files, 5-13 specifying for a rawdisk, 5-21 specifying for filesets, 5-9 target hostname, 5-12 time attributes, 5-13 restore session
how does it work, 1-6 selecting options, 5-12 restoring a file with unknown filename, 5-28 changing the view of backup objects, 5-4 files from a filesystem backup, 5-4 files from a rawdisk backup, 5-24 JFS (VxFS), 7-21 lost files, 5-8 older versions of corrupted files, 5-8 overview, 5-3 parallel restore, 5-18 rawdisk section, 5-20 responding to mount request, 5-23 selectig version of a backup object, 5-8 selecting a rawdisk section, 5-20 specifying rawdisk restore options, 5-21 starting and monitoring with rawdisk, 5-22 the last version of a lost file, 5-8 viewing the messages field, 5-17 restoring data, 5-1 restoring files from a rawdisk starting and monitoring, 5-27 retrying host backup, 7-14 running incremental backup, 3-7 restore, 5-15 S scan quick scan using barcodes, 3-34 scanning media, 3-34 schedule types of backup schedules, 3-10 scheduled backup options overriding, 4-48 scheduling
Index-xii
Index
backups, 4-41 on a specific backup date, 4-43 periodic backup, 4-45 skipping backup during holidays, 4-47 SCSI-II library configuring, 9-7 example of configuration, 9-8 what is it, 9-7 SCSI-II library configuration example, 9-8 SCSI-II library drives configuring, 9-10 searching for files restore, 5-18 secondary Cell Server configuring with MC/Service Guard, 7-39 selecting a filesystem for backup, 4-8 a rawdisk section for restore, 5-20 backup mode, 3-6 backup objects at restore, 5-5 directory version for restore, 5-8 file version for restore, 5-8 files from a rawdisk restore, 5-24 files to restore, 5-6 host backup, 4-18 options for restore, 5-12 rawdisk backup options, 4-15 rawdisk sections for backup, 4-14 selecting backup objects, 5-5 session changing ownership, 4-34 changing the number of sessions, 4-42 deleting from a database, 7-24 scheduling on a specific date, 4-43 scheduling periodic backup, 4-45 skipping backup during holidays, 4-47 Session Manager, 1-4 sessions
monitoring, 6-3 viewing completed sessions, 6-5 viewing details, 6-3 viewing details of completed sessions, 6-6 setting periodical backup, 4-44 several cells monitoring, 6-7 skip restore option, 5-11 sparse files restore option, 5-13 specific files searching at restore, 5-18 specifying fileset restore options, 5-9 stackers operating, 9-5 standalone devices configuring, 3-25 starting a rawdisk restore, 5-22, 5-24 backup, 4-24 failed backup, 7-15 Graphical User Interface, 1-9 restore, 5-15 starting a Cell Server with MC/ServiceGuard, 7-41 starting and monitoring file restore from a rawdisk, 5-27, 5-28 status descriptions of backup session, 4-22 status of backup sessions messages description, 4-22 synchronizing OmniBack II database, 8-10 T tar format compatility, 3-18
Index-xiii
Index
tasks media management, 3-27 temporary datalist creating, 4-23 time attributes restore option, 5-13 troubleshooting, 10-2 type of backup choosing, 3-5 host backup, 3-6 rawdisk, 3-6 selecting, 3-5 types of backup filesystem, 3-5 types of WWW reports, 7-44 U unattended backups, 3-10 understanding datalist, 4-3 updating OmniBack II clients, 2-10 OmniBack II software, 2-10 upgrading OmniBack II software, 2-10 usage policy, 3-17 media, 3-17 user class description of access rights, 3-38 user classes configuring, 3-36 description of, 3-37 users configuring, 3-41 configuring user classes, 3-36 description of access rights, 3-38 using backup devices, 3-21 logical devices, 3-21
media management, 3-27 V verifying media, 3-29 media in pool, 3-29 Veritas File System concepts, 7-19 limitations, 7-20 script templates, 7-21 version installing new OmniBack II version, 2-10 viewing devices and media, 3-35 information about media, 3-30 messages field at restore, 5-17 VxFcopying media, 7-25 VxFS concepts, 7-19 improved backup performance, 7-20 limitations, 7-20 mounting, 7-21 restoring, 7-21 script templates, 7-21 with OmniBack II, 7-19 W WWW reporting, 7-42 types, 7-44
Index-xiv

Upload

Încărcat de

Informații document

Descriere originală:

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

Upload

Încărcat de

Drepturi de autor:

Formate disponibile

HP OpenView OmniBack II Administrators Guide

HP Part No. B1957-90036 October 1997

 & ! $  "     #%# !  

Computer font is used for the following: Directories and names:

8 0 650 4 20 ( 11( 73#31)'

Introducing HP OpenView OmniBack II

H s#vt Esqh #ge)b#I #USQI H H w X u Y I r d p Y i I h f d c a ` Y X W V TRP

4 75 1 F#9 9 )D 1gy 5 4 6 B G 6 0 H st #EsqQ Yh #sxFEI #USI H H w X u Y I r d p i I h f d c a ` Y X W V TRP

4 75 1 )#9 9 #)D 1sy 5 4 6 B G 6 0 H s#vt Esqh #ge)b#I #USQI H H w X u Y I r d p Y i I h f d c a ` Y X W V TRP

Cell Server Software

The Role of Disk Agents and Media Agents

How a Backup Session Works

4 75 1 F#9 9 )D 1gy 5 4 6 B G 6 0 H st #EsqQ Yh #sxFEI #USI H H w X u Y I r d p i I h f d c a ` Y X W V TRP

How a Restore Session Works

4 75 1 )#9 9 #)D 1sy 5 4 6 B G 6 0 H s#vt Esqh #ge)b#I #USQI H H w X u Y I r d p Y i I h f d c a ` Y X W V TRP

4 75 1 F#9 9 )D 1gy 5 4 6 B G 6 0 H st #EsqQ Yh #sxFEI #USI H H w X u Y I r d p i I h f d c a ` Y X W V TRP

Using the User Interfaces

HP OmniBack II Main Menu (xomni)

Graphical User Interface

8 4 45 9 4 #  30 v 8 1A10 #8 4 B5 6 H s#vt Esqh #ge)b#I #USQI H H w X u Y I r d p Y i I h f d c a ` Y X W V TRP

OmniBack II Online Help

8 4 45 9 4 #  30 v 8 1A10 #8 4 B5 6 H st #EsqQ Yh #sxFEI #USI H H w X u Y I r d p i I h f d c a ` Y X W V TRP

8 4 45 9 4 #  30 v 8 1A10 #8 4 B5 6 H s#vt Esqh #ge)b#I #USQI H H w X u Y I r d p Y i I h f d c a ` Y X W V TRP

The Command Line Interface

omnicreatedl omnidb omnidbcheck

8 4 45 9 4 #  30 v 8 1A10 #8 4 B5 6 H st #EsqQ Yh #sxFEI #USI H H w X u Y I r d p i I h f d c a ` Y X W V TRP

omnisv.sh omnitrig omnidownload

8 4 45 9 4 #  30 v 8 1A10 #8 4 B5 6 H s#vt Esqh #ge)b#I #USQI H H w X u Y I r d p Y i I h f d c a ` Y X W V TRP

OmniBack II - Cell Administrator

Distributing HP OmniBack II to Clients

850 d ' ( 73#4 6 )5 9 9 #)D 1se)10 31 6 Q8 6 G 6 0 y 65 5 p Y R h d I YP uP Qh  ET S u #SI H

850 d ' ( 73#4 6 )5 9 9 #)D 1se)10 31 6 Q8 6 G 6 0 y 65 5 p Y R h d I YP uP h  vb#T Q u S#I H

Importing and Exporting Hosts

Importing Hosts to a Cell

858 ( 6 ( j f i 0 6 ( h 71F10 75 1h k110 5 1 9 p Y R h d I YP uP Qh  ET S u #SI H

Import Host window

858 ( 6 ( j f i 0 6 ( h 71)10 75 1h k1ml0 75 1 9 p Y R h d I YP uP h  vb#T Q u S#I H

Importing Hosts with Multi-LAN Cards

Exporting Hosts from a Cell

858 ( 6 ( j f i 0 6 ( h 71F10 75 1h k110 5 1 9 p Y R h d I YP uP Qh  ET S u #SI H

858 ( 6 ( j f i 0 6 ( h 71)10 75 1h k1ml0 75 1 9 p Y R h d I YP uP h  vb#T Q u S#I H

Updating OmniBack II Clients

To Update OmniBack II Clients

850 d 34 6 )' 9 9 #)D 1sml0 711h G 6 0 y 65 i p Y R h d I YP uP Qh  ET S u #SI H

Deinstalling OmniBack II from a Host

To Deinstall OmniBack II Modules

58 ( G 6 0 y d 58 6 Q1)En1( Q9 9 #)D 1s10 6 d Q10 #4 p Y R h d I YP uP h  vb#T Q u S#I H

58 ( G 6 0 y d 58 6 Q1)En1( Q9 9 #)D 1s10 6 d Q10 #4 p Y R h d I YP uP Qh  ET S u #SI H

Planning the Cells

Backup Operations Devices Security Performance

8 d #FE1A10 11 v d 4 ' 4 B5 6 0 0 d h o b#I q#Q#T o u ` YR W ` p I

8 d )E17sl0 1l# v d 4 ' 4 B5 6 0 0 d h o EI U#Q#T o u ` YR W ` p I

Calculations of backup start times

Planning Your Backup Strategy

Each of these is explained in the following sections.

Choosing the Type of Backup

t 45 5 s h G 3Q k1#)D 1A10 11 ( r 6 0 0 d h o b#I q#Q#T o u ` YR W ` p I

Choosing the Mode of Backup

t 45 5 s h G v#Q k1#)D 1usl0 1l# v ( r 6 0 0 d h o EI U#Q#T o u ` YR W ` p I

Incr Incr (1-9)

t 45 5 s h G 3Q k1#)D 1A10 11 ( r 6 0 0 d h o b#I q#Q#T o u ` YR W ` p I

t 45 5 s h G v#Q k1#)D 1usl0 1l# v ( r 6 0 0 d h o EI U#Q#T o u ` YR W ` p I

Friday night Monday night Tuesday night Wednesday night

& ! $ " #%# !

H s#vt Esqh #ge)b#I #USQI H H w X u Y I r d p Y i I h f d c a ` Y X W V TRP

4 75 1 F#9 9 )D 1gy 5 4 6 B G 6 0 H st #EsqQ Yh #sxFEI #USI H H w X u Y I r d p i I h f d c a ` Y X W V TRP

4 75 1 )#9 9 #)D 1sy 5 4 6 B G 6 0 H s#vt Esqh #ge)b#I #USQI H H w X u Y I r d p Y i I h f d c a ` Y X W V TRP

4 75 1 F#9 9 )D 1gy 5 4 6 B G 6 0 H st #EsqQ Yh #sxFEI #USI H H w X u Y I r d p i I h f d c a ` Y X W V TRP

4 75 1 )#9 9 #)D 1sy 5 4 6 B G 6 0 H s#vt Esqh #ge)b#I #USQI H H w X u Y I r d p Y i I h f d c a ` Y X W V TRP

4 75 1 F#9 9 )D 1gy 5 4 6 B G 6 0 H st #EsqQ Yh #sxFEI #USI H H w X u Y I r d p i I h f d c a ` Y X W V TRP

8 4 45 9 4 # 30 v 8 1A10 #8 4 B5 6 H s#vt Esqh #ge)b#I #USQI H H w X u Y I r d p Y i I h f d c a ` Y X W V TRP

8 4 45 9 4 # 30 v 8 1A10 #8 4 B5 6 H st #EsqQ Yh #sxFEI #USI H H w X u Y I r d p i I h f d c a ` Y X W V TRP

8 4 45 9 4 # 30 v 8 1A10 #8 4 B5 6 H s#vt Esqh #ge)b#I #USQI H H w X u Y I r d p Y i I h f d c a ` Y X W V TRP

8 4 45 9 4 # 30 v 8 1A10 #8 4 B5 6 H st #EsqQ Yh #sxFEI #USI H H w X u Y I r d p i I h f d c a ` Y X W V TRP

8 4 45 9 4 # 30 v 8 1A10 #8 4 B5 6 H s#vt Esqh #ge)b#I #USQI H H w X u Y I r d p Y i I h f d c a ` Y X W V TRP

850 d ' ( 73#4 6 )5 9 9 #)D 1se)10 31 6 Q8 6 G 6 0 y 65 5 p Y R h d I YP uP Qh ET S u #SI H

850 d ' ( 73#4 6 )5 9 9 #)D 1se)10 31 6 Q8 6 G 6 0 y 65 5 p Y R h d I YP uP h vb#T Q u S#I H

858 ( 6 ( j f i 0 6 ( h 71F10 75 1h k110 5 1 9 p Y R h d I YP uP Qh ET S u #SI H

858 ( 6 ( j f i 0 6 ( h 71)10 75 1h k1ml0 75 1 9 p Y R h d I YP uP h vb#T Q u S#I H

858 ( 6 ( j f i 0 6 ( h 71F10 75 1h k110 5 1 9 p Y R h d I YP uP Qh ET S u #SI H

858 ( 6 ( j f i 0 6 ( h 71)10 75 1h k1ml0 75 1 9 p Y R h d I YP uP h vb#T Q u S#I H

850 d 34 6 )' 9 9 #)D 1sml0 711h G 6 0 y 65 i p Y R h d I YP uP Qh ET S u #SI H

58 ( G 6 0 y d 58 6 Q1)En1( Q9 9 #)D 1s10 6 d Q10 #4 p Y R h d I YP uP h vb#T Q u S#I H

58 ( G 6 0 y d 58 6 Q1)En1( Q9 9 #)D 1s10 6 d Q10 #4 p Y R h d I YP uP Qh ET S u #SI H

8 d #FE1A10 11 v d 4 ' 4 B5 6 0 0 d h o b#I q#Q#T o u ` YR W ` p I

8 d )E17sl0 1l# v d 4 ' 4 B5 6 0 0 d h o EI U#Q#T o u ` YR W ` p I

t 45 5 s h G 3Q k1#)D 1A10 11 ( r 6 0 0 d h o b#I q#Q#T o u ` YR W ` p I

t 45 5 s h G v#Q k1#)D 1usl0 1l# v ( r 6 0 0 d h o EI U#Q#T o u ` YR W ` p I

t 45 5 s h G 3Q k1#)D 1A10 11 ( r 6 0 0 d h o b#I q#Q#T o u ` YR W ` p I

t 45 5 s h G v#Q k1#)D 1usl0 1l# v ( r 6 0 0 d h o EI U#Q#T o u ` YR W ` p I

t 45 5 s h G 3Q k1#)D 1A10 11 ( r 6 0 0 d h o b#I q#Q#T o u ` YR W ` p I

t 45 5 s h G v#Q k1#)D 1usl0 1l# v ( r 6 0 0 d h o EI U#Q#T o u ` YR W ` p I

t 45 5 s h G 3Q k1#)D 1A10 11 ( r 6 0 0 d h o b#I q#Q#T o u ` YR W ` p I g e y9 @ '

t 45 5 s h G v#Q k1#)D 1usl0 1l# v ( r 6 0 0 d h o EI U#Q#T o u ` YR W ` p I

t 45 5 s h G 3Q k1#)D 1A10 11 ( r 6 0 0 d h o b#I q#Q#T o u ` YR W ` p I g f @ y e

50 4 4 0 3#1#l# w 1#4 w 6 i h o EI U#Q#T o u ` YR W ` p I

50 4 4 0 3#11 w 14 w 6 i h o b#I q#Q#T o u ` YR W ` p I

50 4 4 0 3#1#l# w 1#4 w 6 i h o EI U#Q#T o u ` YR W ` p I g f @ y e

50 4 4 0 3#11 w 14 w 6 i h o b#I q#Q#T o u ` YR W ` p I

50 4 4 0 3#1#l# w 1#4 w 6 i h o EI U#Q#T o u ` YR W ` p I

50 4 4 0 3#11 w 14 w 6 i h o b#I q#Q#T o u ` YR W ` p I g f @ y e g f @ y e

50 4 4 0 3#1#l# w 1#4 w 6 i h o EI U#Q#T o u ` YR W ` p I

8 4 6 2 d 6 ( y 6 # 4 # 11lml0 8 110 6 1C31)' i 0 x0 ( h o b#I q#Q#T o u ` YR W ` p I

8 4 2 d 6 ( y 6 # 6 Q4 # 11110 #8 1#10 6 1C31F' i 0 x0 ( h o EI U#Q#T o u ` YR W ` p I

8 4 6 2 d 6 ( y 6 # 4 # 11lml0 8 110 6 1C31)' i 0 x0 ( h o b#I q#Q#T o u ` YR W ` p I

8 4 2 d 6 ( y 6 # 6 Q4 # 11110 #8 1#10 6 1C31F' i 0 x0 ( h o EI U#Q#T o u ` YR W ` p I

8 4 6 2 d 6 ( y 6 # 4 # 11lml0 8 110 6 1C31)' i 0 x0 ( h o b#I q#Q#T o u ` YR W ` p I

8 4 2 d 6 ( y 6 # 6 Q4 # 11110 #8 1#10 6 1C31F' i 0 x0 ( h o EI U#Q#T o u ` YR W ` p I

8 G 8 @ 50 4 4 0 #z13#l#1 w 14 w 6 i h o b#I q#Q#T o u ` YR W ` p I

8 G 8 @ 50 4 4 0 ##zl3#1#l# w 1#4 w 6 i h o EI U#Q#T o u ` YR W ` p I

8 G 8 @ 50 4 4 0 #z13#l#1 w 14 w 6 i h o b#I q#Q#T o u ` YR W ` p I

8 G 8 @ 50 4 4 0 ##zl3#1#l# w 1#4 w 6 i h o EI U#Q#T o u ` YR W ` p I

8 G 8 @ 50 4 4 0 #z13#l#1 w 14 w 6 i h o b#I q#Q#T o u ` YR W ` p I

8 G 8 @ 50 4 4 0 ##zl3#1#l# w 1#4 w 6 i h o EI U#Q#T o u ` YR W ` p I

8 G 8 @ 50 4 4 0 #z13#l#1 w 14 w 6 i h o b#I q#Q#T o u ` YR W ` p I

8 G 8 @ 50 4 4 0 ##zl3#1#l# w 1#4 w 6 i h o EI U#Q#T o u ` YR W ` p I

8 G 8 @ 50 4 4 0 #z13#l#1 w 14 w 6 i h o b#I q#Q#T o u ` YR W ` p I

8 8 1#b## )' 8 10 6 1C31F' 4 i 0 8 4 8 8 d 4 x0 ( h o EI U#Q#T o u ` YR W ` p I

8 #8 l#b## )' 8 10 6 1C31)' 4 i 0 8 4 8 8 d 4 x0 ( h o b#I q#Q#T o u ` YR W ` p I

8 8 1#b## )' 8 10 6 1C31F' 4 i 0 8 4 8 8 d 4 x0 ( h o EI U#Q#T o u ` YR W ` p I

8 #8 l#b## )' 8 10 6 1C31)' 4 i 0 8 4 8 8 d 4 x0 ( h o b#I q#Q#T o u ` YR W ` p I

8 8 1#b## )' 8 10 6 1C31F' 4 i 0 8 4 8 8 d 4 x0 ( h o EI U#Q#T o u ` YR W ` p I

8 #8 l#b## )' 8 10 6 1C31)' 4 i 0 8 4 8 8 d 4 x0 ( h o b#I q#Q#T o u ` YR W ` p I

8 8 1#b## )' 8 10 6 1C31F' 4 i 0 8 4 8 8 d 4 x0 ( h o EI U#Q#T o u ` YR W ` p I