Docu91844

Dell EMC Avamar for Oracle
Version 18.2
User Guide
302-005-115
REV 02
November 2019

Copyright © 2001-2019 Dell Inc. or its subsidiaries. All rights reserved.
Dell believes the information in this publication is accurate as of its publication date. The information is subject to change without notice.
THE INFORMATION IN THIS PUBLICATION IS PROVIDED “AS-IS.” DELL MAKES NO REPRESENTATIONS OR WARRANTIES OF ANY KIND
WITH RESPECT TO THE INFORMATION IN THIS PUBLICATION, AND SPECIFICALLY DISCLAIMS IMPLIED WARRANTIES OF
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. USE, COPYING, AND DISTRIBUTION OF ANY DELL SOFTWARE DESCRIBED
IN THIS PUBLICATION REQUIRES AN APPLICABLE SOFTWARE LICENSE.
Dell Technologies, Dell, EMC, Dell EMC and other trademarks are trademarks of Dell Inc. or its subsidiaries. Other trademarks may be the property
of their respective owners. Published in the USA.
Dell EMC
Hopkinton, Massachusetts 01748-9103
1-508-435-1000 In North America 1-866-464-7381
www.DellEMC.com
2 Dell EMC Avamar for Oracle User Guide

7
9
11
Introduction 15
Architecture...................................................................................................... 16
Stand-alone configuration.................................................................... 16
High-availability configuration...............................................................17
Data Domain system support................................................................18
Log files................................................................................................18
Backup and restore operations.......................................................................... 18
Backups and restores in Avamar Administrator or the AUI....................19
Backup..............................................................................................................20
Backup types....................................................................................... 20
Archive log backups............................................................................. 22
Automatic Storage Management and raw file structure support.......... 22
Oracle offline backup........................................................................... 22
RMAN tuning options...........................................................................22
RMAN backup optimization..................................................................23
RMAN multisection backups................................................................ 23
Restore and recovery........................................................................................24
Corrupt block recovery........................................................................ 24
Flashback Database recovery...............................................................24
Roll forward recovery...........................................................................24
Restore and recovery from the Cloud.................................................. 24
Concurrent backups and restores..................................................................... 25
Multiple databases............................................................................................25
Multi-streaming................................................................................................ 25
Oracle Exadata..................................................................................................26
Oracle recovery catalog....................................................................................26
Preprocessing and postprocessing backup and restore scripts......................... 26
Installation 29
Preparing to install the Avamar Plug-in for Oracle............................................ 30
System requirements...........................................................................30
Oracle requirements.............................................................................30
VCS configurations...............................................................................31
Downloading the software.................................................................... 31
Installing the Avamar file system client.................................................31
Installing, upgrading, and uninstalling the software on HP-UX.......................... 32
Installing the Avamar Plug-in for Oracle on HP-UX.............................. 32
Upgrading the Avamar Plug-in for Oracle on HP-UX............................33
Uninstalling the Avamar Plug-in for Oracle on HP-UX..........................33
Installing, upgrading, and uninstalling the software on IBM AIX........................ 33
Tables
Figures
Preface
Chapter 1
Chapter 2
CONTENTS
Dell EMC Avamar for Oracle User Guide 3

Installing the Avamar Plug-in for Oracle on IBM AIX............................ 33
Upgrading the Avamar Plug-in for Oracle on IBM AIX.......................... 34
Uninstalling the Avamar Plug-in for Oracle on IBM AIX........................ 35
Installing, upgrading, and uninstalling the software on Linux.............................36
Installing the Avamar Plug-in for Oracle on Linux.................................36
Upgrading the Avamar Plug-in for Oracle on Linux...............................37
Uninstalling the Avamar Plug-in for Oracle on Linux.............................38
Installing, upgrading, and uninstalling the software on Solaris...........................39
Installing the Avamar Plug-in for Oracle on a stand-alone Solaris.........39
Installing the Avamar Plug-in for Oracle on a Solaris cluster................ 40
Upgrading the Avamar Plug-in for Oracle on Solaris............................ 43
Uninstalling the Avamar plug-in on a stand-alone Solaris..................... 43
Uninstalling the Avamar Cluster Client for Solaris................................ 44
Installing, upgrading, and uninstalling the software on Windows.......................44
Installing the Avamar Plug-in for Oracle on Windows .......................... 44
Configuring the Avamar cluster client on Windows.............................. 45
Upgrading the Avamar Plug-in for Oracle on Windows.........................47
Uninstalling the Avamar Plug-in for Oracle on Windows.......................48
Excluding Oracle directories from file system backups..................................... 49
Oracle RAC Configuration 51
Managing Oracle RAC on Linux or UNIX........................................................... 52
Running the rac_config script..............................................................52
Changing the listening port for RAC avagent....................................... 53
Registering the Avamar client.............................................................. 54
Changing the active node.................................................................... 55
Removing the Oracle RAC configuration..............................................55
Managing Oracle RAC on Windows Server 2008.............................................. 55
Running AvamarRACConfiguration.exe................................................56
Starting the EMCagent clusterware resource...................................... 57
Verifying the Oracle RAC configuration............................................... 57
Stopping the Oracle EMCagent........................................................... 57
Adding a new node to an Oracle RAC configuration............................. 58
Re-registering a node with a different Avamar server..........................59
Resetting the Oracle RAC configuration.............................................. 59
High Availability Oracle Single-Instance Database Configuration 61
Highly available Oracle single-instance databases.............................................62
Configuring highly available single-instance databases on Linux or UNIX
............................................................................................................ 62
Configuring highly available single-instance databases on Windows.... 64
Backup 71
Creating the Oracle user account......................................................................72
Enabling Block Change Tracking....................................................................... 72
Preparing the database for backup .................................................................. 72
Performing an on-demand backup.................................................................... 73
Scheduling backups...........................................................................................77
Creating a dataset................................................................................77
Creating a backup policy...................................................................... 79
Enabling a scheduled backup for a backup policy................................. 79
Monitoring backups.......................................................................................... 80
Cancel backups.................................................................................................80
Oracle RAC backup failures............................................................................... 81
Chapter 3
Chapter 4
Chapter 5
Contents

Restarting the backup after the active node’s instance goes down...... 81
Restarting the backup after a node goes down.....................................81
Enforcement of backups to Data Domain.......................................................... 81
Restore and Recovery 83
Preparing the database for recovery.................................................................84
Configuring Flashback Database recovery........................................... 84
Configuring the database for corrupt block recovery...........................84
Preparing the database for restore................................................................... 84
Restore types................................................................................................... 86
Restoring a database to the original client........................................................ 86
Restoring a database to a different client......................................................... 90
Monitor restores...............................................................................................93
Cancel restores.................................................................................................94
Performing a disaster recovery.........................................................................94
Backup and Restore with Oracle RMAN 97
Preparing the system for RMAN backups and restores.....................................98
Creating an avtar flag file.....................................................................98
Creating a taskflag file......................................................................... 99
Specifying the SBT_LIBRARY parameter........................................... 100
Specifying the library path settings.................................................... 100
Specifying the SECTION SIZE parameter for multisection backups.... 101
RMAN substitution variables %d and %U............................................101
Specifying RMAN parameters to improve performance................................... 101
Specifying the maxopenfiles parameter..............................................102
Specifying the filesperset parameter.................................................. 102
Enabling RMAN backup optimization..................................................102
Specifying before, after, and nobackuptag flags to increase index
lookup speed.......................................................................................103
Backing up Oracle data with RMAN.................................................................105
Backing up a database........................................................................105
Backing up a tablespace..................................................................... 105
Backing up a datafile...........................................................................106
Restoring Oracle data with RMAN...................................................................107
Restoring a database.......................................................................... 107
Restoring a tablespace....................................................................... 109
Restoring datafiles.............................................................................. 110
Using advanced restore commands.................................................................. 111
Using the catalog for backup and restores...........................................111
Performing a redirected restore.......................................................... 112
Managing backup retention..............................................................................112
Configuring retention policies..............................................................113
Crosschecking backups.......................................................................114
Deleting backups.................................................................................114
Mixing RMAN and Avamar Administrator backups.............................. 115
Synchronizing the RMAN catalog........................................................115
Allocating multiple channels............................................................................. 116
Managing RMAN backups and restores through Avamar Administrator........... 117
Plug-in Options 119
How to set plug-in options...............................................................................120
Backup options................................................................................................120
Specifying the channel_maxopenfiles option as normal text...............123
Chapter 6
Chapter 7
Appendix A
Contents

The sbtio_trace_level option.............................................................. 123
The libobk_timeout option.................................................................. 124
Restore options............................................................................................... 125
Recovery modes and values................................................................127
Timestamp order of precedence rules.................................................129
Preprocessing and postprocessing scripts and attributes................................129
Preprocessing and postprocessing usage examples............................132
Troubleshooting 137
Backup and restore problems and solutions.....................................................138
Avamar Administrator shows a completed RMAN backup or restore as
still running......................................................................................... 138
avoracle Error <7936>: No valid targets found................................... 138
Activity monitor of RMAN backup shows an incorrect status of still
running............................................................................................... 138
Backups fail when backup copies is set to more than 1....................... 139
Log files for RMAN operations cannot be viewed from the Avamar
Administrator if a custom var directory is used...................................139
Backups unavailable after registering secondary RAC node................139
Cannot open file f_cache.dat error.....................................................139
Cannot Sync error.............................................................................. 140
Failed RMAN restore of control file is reported as completed in Avamar
Administrator......................................................................................140
Hot backup fails with Oracle not available error..................................140
Level-1 backup of a large database fails with a snapview timeout........141
ORA-19870: error while restoring backup piece...................................141
ORA-25153: Temporary Tablespace is Empty.....................................142
ORA-27211: Failed to load Media Management Library....................... 142
Restore fails to complete successfully................................................142
RMAN backup script fails with media management errors.................. 143
RMAN backup script fails with ORA-19511..........................................143
RMAN-06056: could not access datafile n error on AIX......................144
RMAN script fails with WriteFile failed error.......................................144
Time-out errors when using multiple RMAN channels.........................145
Unable to process snapview workorder.............................................. 145
Unable to send CTL message..............................................................145
The no_of_channels parameter no longer supported..........................145
Hidden backups.................................................................................. 146
Configuration problems and solutions..............................................................146
Avamar client and Avamar Plug-in for Oracle registration...................146
Bitwidth of Avamar Plug-in for Oracle and Oracle...............................147
Cluster Configuration Tool fails to start..............................................148
Determining the version of Oracle...................................................... 148
Disk space for the /var/avamar directory...........................................148
Oracle RAC database failover............................................................. 148
Requirements for libobk_avamar.so and libobk_avamar.dll.................149
RMAN executable file and Oracle versions......................................... 149
Stopping Avamar Administrator processes......................................... 150
Unable to browse Oracle databases with Avamar Administrator.........150
Verifying the client and plug-in versions..............................................151
153
Appendix B
Glossary
Contents

Typographical conventions................................................................................................ 12
Hardware requirements ....................................................................................................30
Environment variables for libobk......................................................................................100
Backup plug-in options.................................................................................................... 120
Restore plug-in options................................................................................................... 125
Recovery mode options................................................................................................... 127
Preprocessing and postprocessing attributes.................................................................. 130
Attribute flags................................................................................................................. 130
Avamar client installation verification...............................................................................151
1
2
3
4
5
6
7
8
9
TABLES

Tables

Avamar Plug-in for Oracle in a stand-alone configuration..................................................16
Avamar client and Avamar server process flow diagram.................................................... 19
Level 1 differential backups................................................................................................21
Level 1 cumulative backups................................................................................................21
RMAN multiplexing........................................................................................................... 23
Setup Avamar for Oracle Single-Instance Database dialog................................................65
Backup Command Line Options window.......................................................................... 133
Backup Command Line Options window.......................................................................... 135
1
2
3
4
5
6
7
8
9
10
11
FIGURES

Figures

PREFACE
As part of an effort to improve the product lines, revisions of the software and hardware are
periodically released. Therefore, some functions that are described in this document might not be
supported by all versions of the software or hardware currently in use. The product release notes
provide the most up-to-date information on product features.
Contact the technical support professional when a product does not function correctly or does not
function as described in this document.
Note: This document was accurate at publication time. To find the latest version of this
document, go to Online Support (https://support.EMC.com).
Purpose
This guide describes how to install, configure, administer, and use the Avamar Plug-in for Oracle.
Audience
This document is intended for:
l System administrators who are responsible for installing software and maintaining servers and
clients on a network
l Oracle Database Administrators (DBAs) who are responsible for backing up and maintaining
Oracle databases
Revision history
The following table presents the revision history of this document.
Revision Date Description
02 November 15, 2019 This revision includes the
following updates:
l Updated "Creating an
avtar flag file" to add a
command parameter.
l Hardware requirements
updates
01 December 14, 2018 GA release of Avamar 18.2
Related documentation
The following publications provide additional information:
l Avamar Administration Guide
l Avamar Backup Clients User Guide
l Avamar for Windows Server User Guide
l Avamar Operational Best Practices Guide
l E-lab Navigator at https://elabnavigator.emc.com/eln/elnhome
l Avamar Release Notes
l Avamar and Data Domain System Integration Guide

Special notice conventions used in this document
These conventions are used for special notices.
DANGER Indicates a hazardous situation which, if not avoided, results in death or serious
injury.
WARNING Indicates a hazardous situation which, if not avoided, could result in death or
serious injury.
CAUTION Indicates a hazardous situation which, if not avoided, could result in minor or
moderate injury.
NOTICE Addresses practices that are not related to personal injury.
Note: Presents information that is important, but not hazard-related.
Typographical conventions
These type style conventions are used in this document.
Table 1 Typographical conventions
Bold Used for names of interface elements, such as names of windows,
dialog boxes, buttons, fields, tab names, key names, and menu paths
(what the user specifically selects or clicks)
Italic Used for full titles of publications that are referenced in text
Monospace Used for:
l System code
l System output, such as an error message or script
l Pathnames, filenames, prompts, and syntax
l Commands and options
Monospace italic Used for variables
Monospace bold Used for user input
[ ] Square brackets enclose optional values
| Vertical bar indicates alternate selections - the bar means “or”
{ } Braces enclose content that the user must specify, such as x or y or
z
... Ellipses indicate nonessential information that is omitted from the
example
Where to get help
The Avamar support page provides access to licensing information, product documentation,
advisories, and downloads, as well as how-to and troubleshooting information. This information
may resolve a product issue before contacting Customer Support.
To access the Avamar support page:
1. Go to https://www.dell.com/support/home/us/en/19.
2. Type a product name in the Enter a Service Tag, Serial Number, Service Request, Model,
or Keyword search box.
3. Select the product from the list that appears. When you select a product, the Product
Support page loads automatically.
PREFACE

4. (Optional) Add the product to the My Products list by clicking Add to My Saved Products in
the upper right corner of the Product Support page.
Documentation
The Avamar product documentation provides a comprehensive set of feature overview, operational
task, and technical reference information. To supplement the information in product administration
and user guides, review the following documents:
l Release notes provide an overview of new features and known limitations for a release.
l Technical notes provide technical details about specific product features, including step-by-
step tasks, where necessary.
l White papers provide an in-depth technical perspective of a product or products as applied to
critical business issues or requirements.
Knowledgebase
The Knowledgebase contains applicable solutions that you can search for either by solution
number (for example, KB000xxxxxx) or by keyword.
To search the Knowledgebase:
1. Go to https://www.dell.com/support/home/us/en/19.
2. Under the Support tab, click Knowledge Base.
3. Type either the solution number or keywords in the search box. Optionally, you can limit the
search to specific products by typing a product name in the search box and then selecting the
product from the list that appears.
Online communities
Go to Community Network at http://community.EMC.com for peer contacts, conversations, and
content on product support and solutions. Interactively engage online with customers, partners,
and certified professionals for all products.
Live chat
To engage Customer Support by using live interactive chat, click Join Live Chat on the Service
Center panel of the Avamar support page.
Service Requests
For in-depth help from Customer Support, submit a service request by clicking Create Service
Requests on the Service Center panel of the Avamar support page.
Note: To open a service request, you must have a valid support agreement. Contact a sales
representative for details about obtaining a valid support agreement or with questions about an
account.
To review an open service request, click the Service Center link on the Service Center panel, and
then click View and manage service requests.
Enhancing support
It is recommended to enable ConnectEMC and Email Home on all Avamar systems:
l ConnectEMC automatically generates service requests for high priority events.
l Email Home sends configuration, capacity, and general system information to Customer
Support.
Comments and suggestions
Comments and suggestions help to continue to improve the accuracy, organization, and overall
quality of the user publications. Send comments and suggestions about this document to
DPAD.Doc.Feedback@emc.com.
PREFACE

Please include the following information:
l Product name and version
l Document name, part number, and revision (for example, 01)
l Page numbers
l Other details to help address documentation issues
PREFACE

CHAPTER 1
Introduction
This chapter includes the following topics:
l Architecture...........................................................................................................................16
l Backup and restore operations...............................................................................................18
l Backup.................................................................................................................................. 20
l Restore and recovery............................................................................................................ 24
l Concurrent backups and restores..........................................................................................25
l Multiple databases................................................................................................................ 25
l Multi-streaming.....................................................................................................................25
l Oracle Exadata......................................................................................................................26
l Oracle recovery catalog........................................................................................................ 26
l Preprocessing and postprocessing backup and restore scripts..............................................26

Architecture
The Avamar
®
Plug-in for Oracle works with Oracle and Oracle Recovery Manager (RMAN) to back
up Oracle databases, tablespaces, or datafiles to an Avamar server or a Data Domain
®
system. The
Avamar Plug-in for Oracle serves as a backup module and the Avamar server or Data Domain
system as a storage device. You can perform backups and restores from Avamar Administrator or
from the RMAN command line interface.
From the RMAN command line interface, RMAN uses the Avamar Plug-in for Oracle as a data
mover to perform backup and recovery. From Avamar Administrator, the Avamar Plug-in for
Oracle creates an RMAN script to perform the backup or restore operation and spawns an RMAN
process to run the script. RMAN then uses the Avamar Plug-in for Oracle as a data mover to
perform a backup or a restore operation.
Stand-alone configuration
You can deploy the Avamar Plug-in for Oracle in stand-alone configurations for all supported
platforms.
The following figure shows a stand-alone configuration that uses the Avamar Plug-in for Oracle to
back up or restore Oracle data to or from an Avamar server or a Data Domain system.
Figure 1 Avamar Plug-in for Oracle in a stand-alone configuration
The E-lab Navigator provides more information about supported platforms.
Introduction

High-availability configuration
You can also deploy the Avamar Plug-in for Oracle in high-availability (HA) configurations such as
Microsoft Cluster Server (MSCS), Solaris Cluster Server (VCS), and Oracle Real Application
Clusters (RAC).
MSCS configurations
The Avamar Plug-in for Oracle supports two-node MSCS configuration. You can use the Avamar
Plug-in for Oracle to back up Oracle database files from Windows Server 2008 and MSCS for both
32-bit and 64-bit platforms.
VCS configurations
The Avamar Plug-in for Oracle supports both two-node active/active and two-node active/passive
VCS configurations. You can use the Avamar Plug-in for Oracle to back up Oracle database files
from Solaris platforms that run VCS.
In an active/active cluster configuration, each node runs an instance of the Avamar Plug-in for
Oracle as an application in separate service groups. This functionality provides application
redundancy. When a failure occurs on one active node, the other active node hosts both service
groups.
In an active/passive cluster configuration, the service group is online on the active node until a
failover occurs. Then the service group comes online on the passive node.
You can run backups and restores from both nodes.
RAC configurations
RAC is an option for an Oracle database that enables multiple nodes to have shared access to a
single database. The Avamar Plug-in for Oracle supports backups of RAC configuration on HP-UX,
IBM AIX, Linux, Solaris, or Windows platforms, and requires that Oracle RAC installation is in the
English language.
The Avamar Plug-in for Oracle installation packages for the HP-UX, IBM AIX, Linux, and Solaris
platforms include three configuration scripts for Oracle RAC:
l rac_config—Configures the Avamar Plug-in for Oracle to back up and restore RAC
databases.
l rac_deconfig—Deletes the RAC configuration from the Avamar Plug-in for Oracle.
l rac_stop—Removes the Avamar agent (EMCagent) from the Oracle Clusterware resource
list.
The Avamar Plug-in for Oracle installation package for Microsoft Windows includes
AvamarRACConfiguration.exe.
Use Avamar Administrator to back up and restore Oracle RAC databases just as you would for non-
RAC databases. In an Oracle RAC configuration, each cluster node runs a local instance of the
Oracle database and maintains a local copy of online logs. The instance name differs from the
database unique name.
To back up an Oracle RAC database, the Avamar Plug-in for Oracle connects to the instance of the
database that is running on the current active node. To restore an Oracle RAC database, you must
first shut down all database instances, and then start the instance on the registered node in a “no
mount” state.
When one cluster node fails or is taken offline, the other cluster nodes continue operating. The
Oracle RAC database remains available to users without interruption. The Avamar Plug-in for
Introduction

Oracle backs up and restores Oracle RAC databases by connecting to the instance that runs on
the cluster node. This node is the one registered with the Avamar server.
Because each node runs an instance of the Oracle database in a RAC configuration, when a
failover occurs, users access the database on the failover node. The failover process is transparent
to the users.
Data Domain system support
The Avamar Plug-in for Oracle supports backups to and restore from Data Domain systems. You
can back up Oracle data to a Data Domain system by using Avamar Administrator or by using
RMAN backup scripts. The Avamar Plug-in for Oracle stores the metadata for the backup on the
Avamar server.
Before you can store backups on a Data Domain system, you must add the Data Domain system to
the Avamar configuration by using Avamar Administrator. After you configure the Data Domain
system, you can back up Oracle database files to the Data Domain system by performing the
following actions:
l Selecting the appropriate plug-in option from Avamar Administrator.
l Specifying the Data Domain system as the target system for RMAN backup scripts.
You can also specify a Data Domain system when you create a dataset for a scheduled backup.
You must store the full backup for a client and all subsequent incremental backups on either the
Avamar server or a single Data Domain system. The Avamar Plug-in for Oracle does not support
backups that are stored partly on Avamar and partly on a Data Domain system. For example, the
Avamar Plug-in for Oracle does not support the following types of backups:
l Full backup on a Data Domain system and incremental backups on the Avamar server
l Full backup on the Avamar server and incremental backups on a Data Domain system
l Full backup on one Data Domain system and incremental backups on another Data Domain
system
If you change the device on which backups for a client are stored, you must then perform a full
backup before you perform any further incremental backups.
The steps to restore backups are the same whether you restore backups from the Avamar server
or from a Data Domain system. The restore process determines the location of the backup.
The Avamar and Data Domain System Integration Guide provides more information about configuring
Data Domain systems for use with Avamar systems.
Log files
The Avamar Plug-in for Oracle creates log files during backup and restore operations. The log files
are for debugging purposes. Backup and restore operations from Avamar Administrator create the
avoracle.log file in the install-directory/var/clientlogs directory.
Backup and restore operations
You can perform backup and restores by using Avamar Administrator, the AUI, or by running
RMAN scripts from the command line.
Note: The Avamar AUI is only supported in stand-alone environments.
Introduction

Backups and restores in Avamar Administrator or the AUI
During backups or restores in Avamar Administrator, or the AUI, the Avamar Plug-in for Oracle
generates an RMAN script that performs the backup or restore of the specified database. The
Avamar client agent runs RMAN with this script. The script directs Oracle to open a connection
with an Avamar Media Management library, which invokes an avtar session to connect to the
Avamar server.
The following figure shows the process flow between the Avamar client and Avamar server.
Figure 2 Avamar client and Avamar server process flow diagram
The Oracle backup process generates an RMAN script similar to the following script:
configure controlfile autobackup on;
run {
allocate channel c1 type sbt;
send 'connect information for avtar to connect to the Avamar server';
backup database;
}
During the backup or restore operation, RMAN creates a log file that you can view from Avamar
Administrator, or the AUI:
Recovery Manager: Release 11.1.0.7.0 - Production
Copyright (c) 1995, 2004, Oracle. All rights reserved.
connected to target database: ORACLE (DBID=1420649215) using target database
controlfile instead of recovery catalog
RMAN> configure controlfile autobackup on;
2> run {
3> allocate channel c1 type sbt;
4> send '... ';
6> backup database;
7> }
8>
old RMAN configuration parameters:
CONFIGURE CONTROLFILE AUTOBACKUP OFF;
new RMAN configuration parameters:
CONFIGURE CONTROLFILE AUTOBACKUP OFF;
new RMAN configuration parameters are successfully stored
allocated channel: c1
channel c1: sid=142 devtype=SBT_TAPE
channel c1: AVTAR/Avamar backup
sent command to channel: c1
Introduction

Starting backup at 23-NOV-12
channel c1: starting full datafile backupset
channel c1: specifying datafile(s) in backupset
input datafile fno=00001 name=D:ORACLEPRODUCT10.1.0ORADATAORACLEORACLE
SYSTEM01.DBF
SYSAUX01.DBF
UNDOTBS01.DBF
USERS01.DBF
channel c1: starting piece 1 at 23-NOV-12
channel c1: finished piece 1 at 23-NOV-12
piece handle=15gfs32k_1_1 comment=API Version 2.0,MMS Version 2.2.0.108
channel c1: backup set complete, elapsed time: 00:00:45 channel c1: starting
full datafile backupset channel c1: specifying datafile(s) in backupset
including current controlfile in backupset including current SPFILE in
backupset channel c1: starting piece 1 at 23-NOV-12 channel c1: finished
piece 1 at 23-NOV-12 piece handle=16gfs341_1_1 comment=API Version 2.0,MMS
Version 2.2.0.108 channel c1: backup set complete, elapsed time: 00:00:17
Finished backup at 21-MAR-11 released channel: c1
Recovery Manager complete.
Backup
The Avamar Plug-in for Oracle enables you to back up Oracle database files and archive logs by
using Avamar Administrator, the AUI, or RMAN backup scripts. When you use an RMAN script, you
can back up an Oracle database, a tablespace, or a single datafile.
Backup types
The Avamar Plug-in for Oracle supports the following types of backups:
l Backups of Oracle database files and archive logs.
l Cold (offline) backups of the Oracle file system.
l Four backup levels:
n Full—Backs up all data files. You can optionally choose to backup the archive logs during a
Level 0 (incremental) backup or at a later time.
Level full, the default backup level, is not part of the incremental backup strategy.
n Level 0 (incremental)—Backs up all data files.
You must run a Level 0 backup before you run a Level 1 backup.
n Differential (incremental)—Backs up all database blocks that have changed since the most
recent incremental (differential or cumulative) or level 0 backup. The following figure shows
daily level 1 differential backups during a two-week period.
Introduction

Figure 3 Level 1 differential backups
n Cumulative (incremental)—Backs up all database blocks that have changed since the most
recent level 0 backup.
Restoring a backup from a cumulative backup is faster than restoring a backup from a
differential backup. Cumulative backups, however, require more disk space and take longer
to complete than differential backups.
Perform cumulative level backups when recovery time is more important than disk space.
The following figure shows daily level 1 cumulative backups during a two-week period.
Figure 4 Level 1 cumulative backups
l On-demand or scheduled backups—You can perform on-demand backups or schedule backups
to run automatically.
Introduction

Archive log backups
The Backup Command Line Options dialog box includes the following backup options: Back up
database, Back up archive logs, and Delete archive log after backup.
You must select at least one of the backup options, otherwise the backup fails. The Avamar Plug-in
for Oracle does not validate these options. When you select the Back up archive logs option, the
Avamar Plug-in for Oracle ignores the incremental backup options and performs a full backup.
Avamar Administrator does not support restores of only archive logs. To restore only archive logs,
you must use an RMAN script.
Automatic Storage Management and raw file structure support
The Avamar Plug-in for Oracle supports backups of databases that use Automated Storage
Management (ASM) for storage management and raw file structure.
Oracle offline backup
The Avamar Plug-in for Oracle supports Oracle’s offline backup feature, which enables you to back
up a database that is in a mount state. This type of backup is equivalent to a hot backup of a
database. A restore of an offline backup uses the same procedure that a restore of a hot backup
uses.
RMAN tuning options
Backups that you perform with the Avamar Plug-in for Oracle in Avamar Administrator use RMAN.
RMAN reads the individual data files, bundles the files into backup sets, and then sends the backup
set to avtar.
To create the backup set, RMAN simultaneously reads multiple files from the disk, and then writes
the blocks of file data into the same backup set. The combination of blocks from multiple files is
called backup multiplexing. The following figure shows the multiplexing of three files into a backup
piece.
Introduction

Figure 5 RMAN multiplexing
In Figure 5 on page 23, RMAN simultaneously reads three files and writes them to the backup set
intermingled. The RMAN multiplexing feature intermingles the backup files, and does not provide
the data stream in a similar format for subsequent reads.
Because of how the RMAN multiplexing feature intermingles files, backups by the Avamar Plug-in
for Oracle to the Avamar server can contain the duplicate data even if no changes were made to
the database since the last backup. The RMAN multiplexing feature can negatively affect the data
deduplication ratio of the Avamar Plug-in for Oracle.
The Avamar Plug-in for Oracle improves data deduplication performance by enabling you to use
the Filesperset option in Avamar Administrator.
The Filesperset option specifies the number of files to include in each backup set. The default
value of the Filesperset option is 1. When you specify a value for the Filesperset option, RMAN
uses the value as a limit for the number of files RMAN includes in a backup set.
RMAN backup optimization
The Avamar Plug-in for Oracle supports the RMAN backup optimization feature through the
RMAN CLI only. By enabling the backup optimization feature, the RMAN backup command skips
the backup of a file if an identical file is already backed up to the allocated device type.
Enable backup optimization with the configure backup optimization on RMAN command.
Enabling backup optimization reduces backup time. The Oracle documentation provides more
information about backup optimization.
Enabling RMAN backup optimization on page 102 provides more information about performing
backups that use the backup optimization feature.
RMAN multisection backups
The Avamar Plug-in for Oracle supports the Oracle multisection backup feature through the RMAN
CLI only. To use this feature, perform backups with the SECTION SIZE parameter to divide data
Introduction

files into subsections. Each subsection is then backed up in parallel across multiple channels. The
Oracle documentation provides more information about the multisection backup feature.
Restore and recovery
The Avamar Plug-in for Oracle supports the restore of a database backup from one system to
another system or to a directory on the same system. During a restore you can recover corrupt
blocks or recover data blocks from the flash recovery area (FRA).
Corrupt block recovery
The Avamar Plug-in for Oracle includes the Corrupt blocks option, which enables you to recover
corrupt data blocks only and not the entire database. The Corrupt blocks option is an advanced
option in the Restore Command Line Options dialog box.
To use the Corrupt blocks option, you must first configure the database to use checksums to
verify data blocks. To enable this feature, set the initialization parameter, DB_BLOCK_CHECKSUM, to
TYPICAL for the Oracle database. This setting enables RMAN to detect both physical and logical
corruption:
l Physical corruption can occur because of defective memory boards, defective controllers, or
broken sectors on a hard disk.
l Logical corruption can occur if the contents of a data block are logically inconsistent. Examples
of logical corruption include corruption of a row piece or an index entry.
You can use the Corrupt blocks option while the database is open.
Flashback Database recovery
The Avamar Plug-in for Oracle supports Oracle Flashback Database recovery. The Flashback
Database feature enables you to rewind the database to a target time, system change numbers
(SCN), or a log sequence number. The Avamar Plug-in for Oracle provides a new option in the
Restore Command Line Options dialog box that enables you to perform a recovery from
Flashback Database logs.
Plug-in Options on page 119 provides more information about Flashback Recovery options.
Roll forward recovery
The Avamar Plug-in for Oracle supports roll-forward recovery by providing the Open the
database with resetlogs after recovery advanced option in Avamar Administrator. The
installation of the Avamar Plug-in for Oracle enables this advanced option by default.
The Open the database with resetlogs after recovery option instructs the restore operation to
open the database with resetlogs after the restore completes. The opening of the database with
resetlogs initializes the logs, resets the log sequence number, truncates the available changes in
the redo logs, and starts a new incarnation of the database.
To roll forward a database after a restore operation completes, you must clear the Open the
database with resetlogs after recovery option in the Restore Command Line Options dialog
box. When you clear this option, the restore operation does not open the database with resetlogs.
You can apply archive logs to recover the database to the most current point-in-time that is
available.
Restore and recovery from the Cloud
For Elastic Cloud Storage (ECS), when backups are in the Cloud and absent on Active tier, direct
read from ECS for Oracle enables common restore scenarios by using the plugin restore operations
Introduction

with DD 6.1 and later. When the user performs restores of backups in the ECS, Avamar Plug-in for
Oracle transparently restores data from ECS without performing a recall operation first.
For other Cloud providers, a two step process is in place for restoring and recovering data:
l Recall data from the Cloud
l Restore and recover data
Refer to Restore operations for cloud tier in the Avamar Data Domain System Integration Guide for
more information.
Concurrent backups and restores
The Avamar Plug-in for Oracle supports concurrent backups, restore, or both types of operations
from Avamar Administrator. You can select multiple databases for a backup or restore operation
and the Avamar Plug-in for Oracle runs the backup or restore operations concurrently.
When the operation completes, the Avamar Plug-in for Oracle creates a snapview with all of the
files that are backed up or restored. For differential, cumulative, and archive log only backups, the
snapview also contains the backup files from the previous backups.
You can perform concurrent backups on Oracle 10g and later. You cannot run concurrent backups
of the same database from Avamar Administrator and the RMAN CLI simultaneously.
Avamar Plug-in for Oracle backups from Avamar Administrator use the same page cache files per
database. Concurrent backups to a Data Domain system do not use cache files.
Multiple databases
The Avamar Plug-in for Oracle supports the selection of multiple databases for both backup and
restore operations.
When multiple databases are backed up on the same workorder, they are logically grouped so that
Avamar Administrator can present a hierarchical view of the databases during subsequent restore
operations. This grouping is accomplished by prefixing a path that comprises the ORACLE-
INSTANCE and ORACLE-SID to each database within the backup. For example, an Oracle 11g
database with ORACLE-SID set to orcl is prefixed with /11g/orcl/.
Multi-streaming
Multi-streaming is a feature that enables a backup or a restore to use multiple RMAN channels to
the Avamar server or the Data Domain system. A backup or restore that uses multiple RMAN
channels runs multiple instances of avtar in parallel.
RMAN might not use all the RMAN channels that you specify. For example, if you specify 4 RMAN
channels for a backup, RMAN might use only 2 channels. The backup ignores the other 2 channels.
The default number of RMAN channels is 1 and the maximum is 10.
Allocating multiple RMAN channels for backups and restores can improve performance.
Performance improvements for backups and restores, however, depend on the Oracle server
configuration.
You can specify multiple RMAN channels for backups and restores by using the Number of RMAN
Channels option in Avamar Administrator or by specifying allocate channel commands in an
RMAN script.
Introduction

Oracle Exadata
Oracle Exadata is a product that combines hardware and software to run Oracle. The Avamar
Plug-in for Oracle supports Oracle Exadata for Oracle Database Machine and Exadata Storage
Server (attached to an external database server) configurations.
The Avamar Plug-in for Oracle supports the same environment for Oracle Exadata (including the
Oracle database versions, operating system versions, and Avamar versions) as the environment
that the Avamar Plug-in for Oracle supports for Oracle RAC. The E-lab Navigator provides more
information about supported environments for the Avamar Plug-in for Oracle.
Install and configure the Avamar Plug-in for Oracle on the Exadata database server the same way
you install and configure the Avamar Plug-in for Oracle in Oracle RAC configurations. Use Avamar
Administrator to back up and restore the Exadata database server just as you would for non-
Exadata database servers. Backup on page 71 and Restore and Recovery on page 83 provide
more information.
Oracle recovery catalog
The Avamar Plug-in for Oracle supports the Oracle recovery catalog feature during backups and
restores.
When you select the Use recovery catalog option for a backup, the backup updates the recovery
catalog. All backups include the database control file so that future restore operations do not
depend on the recovery catalog.
When Avamar Administrator cannot use the recovery catalog for a restore, the restore must use
the database control file. You can, however, restore a database from an Avamar backup by using
the recovery catalog from RMAN. Using the catalog for backup and restores on page 111 provides
more information.
Preprocessing and postprocessing backup and restore scripts
The Avamar Plug-in for Oracle supports preprocessing and postprocessing scripts for both backup
and restore operations that you perform in Avamar Administrator.
Preprocessing and postprocessing scripts are user-written shell scripts (.sh) on Linux or UNIX.
On Windows, scripts are batch scripts (.bat), vb Scripts (.vbs), and JScripts (.js). The
Avamar Plug-in for Oracle runs preprocessing and postprocessing scripts as root on Linux or UNIX,
and as an administrator on Windows.
You can use preprocessing and postprocessing scripts for various tasks, such as the following
tasks:
l Copying logs from the var directory to different directory before a backup.
l Preparing the databases for a backup or restore.
l Running SQL queries to get database information.
l Setting environment parameters.
All preprocessing and postprocessing scripts must be in the /avamar/etc/scripts directory
on the client. The preprocessing and postprocessing feature is an advanced option in Avamar
Administrator. Preprocessing and postprocessing scripts and attributes on page 129 provides
more information.
In addition to using preprocessing and postprocessing scripts, the Avamar Plug-in for Oracle
supports the use of preprocessing and postprocessing attributes. Specify preprocessing and
Introduction

postprocessing attributes and attribute values in the Enter Attribute and Enter Attribute Value
fields.
Introduction

Introduction

CHAPTER 2
Installation
l Preparing to install the Avamar Plug-in for Oracle.................................................................30
l Installing, upgrading, and uninstalling the software on HP-UX...............................................32
l Installing, upgrading, and uninstalling the software on IBM AIX.............................................33
l Installing, upgrading, and uninstalling the software on Linux................................................. 36
l Installing, upgrading, and uninstalling the software on Solaris............................................... 39
l Installing, upgrading, and uninstalling the software on Windows........................................... 44
l Excluding Oracle directories from file system backups..........................................................49

Preparing to install the Avamar Plug-in for Oracle
Review the system requirements for the Avamar Plug-in for Oracle to ensure that the environment
meets these requirements before you perform the installation. You must download the Avamar file
system client and Avamar Plug-in for Oracle installation packages from the Avamar server.
System requirements
The environment must meet client compatibility requirements before you install the Avamar Plug-
in for Oracle.
Client compatibility requirements are available in the E-lab Navigator. The requirements in the E-lab
Navigator include supported operating systems and application versions. The Avamar file system
client and the Avamar Plug-in for Oracle that you install on the host must be the same version.
If Oracle RAC is being used, the Avamar Plug-in for Oracle requires that Oracle RAC be installed in
the English language.
Hardware requirements
The following table lists hardware requirements for the Avamar Plug-in for Oracle.
Table 2 Hardware requirements
Resource Requirement
RAM 64 MB
Hard drive space 130 MB permanent hard drive space for
software installation. The Avamar client
software also requires an additional 12 MB of
permanent hard drive space for each 64 MB
of physical RAM. The local cache files use this
space. The maximum required disk space for a
cache file is 2 GB.
Network interface 10BaseT minimum. 100BaseT or higher
recommended, configured with the latest
drivers for the platform.
Software requirements
To install the Avamar Plug-in for Oracle in a Windows cluster requires the Microsoft .NET
Framework 4 software.
You can download and install the .NET Framework 4 from the Microsoft Download Center.
Oracle requirements
Ensure that you meet Oracle requirements before you install the Avamar Plug-in for Oracle.
1. Ensure that you have operating system root privileges on the Oracle server.
2. Ensure that Oracle and RMAN are installed and functioning properly.
3. Ensure that the Avamar server is operational and present on the same network as the Oracle
server by opening a command shell on the Oracle server and typing the following command:
Installation

ping Avamar-server
where Avamar-server is the network hostname (as defined in DNS) or IP address of the
Avamar server.
4. Note the network hostname (which is a DNS entry) for the Avamar server and the utility node.
The installation and configuration of the Avamar system adds these entries to DNS.
VCS configurations
The Avamar Plug-in for Oracle supports both two-node active/active and two-node active/passive
VCS configurations. You can use the Avamar Plug-in for Oracle to back up Oracle database files
from Solaris platforms that run VCS.
In an active/active cluster configuration, each node runs an instance of the Avamar Plug-in for
Oracle as an application in separate service groups. This functionality provides application
redundancy. When a failure occurs on one active node, the other active node hosts both service
groups.
In an active/passive cluster configuration, the service group is online on the active node until a
failover occurs. Then the service group comes online on the passive node.
You can run backups and restores from both nodes.
Downloading the software
Download the installation package for the Avamar Plug-in for Oracle from the Avamar server, and
then save the package to a temporary directory.
About this task
Note: For a Solaris cluster (VCS) configuration, download the Avamar Cluster Client for
Solaris. The Avamar Cluster Client for Solaris includes the Avamar Plug-in for Oracle.
Procedure
1. Log in to the Oracle server with the necessary privileges to perform an installation.
2. Open a web browser and type the following URL:
https://Avamar_server/dtlt/home.html
where Avamar_server is the DNS name or IP address of the Avamar server.
The Avamar Web Restore page appears.
3. Click Downloads.
The Downloads list appears.
4. Click + next to the platform heading for the Oracle server.
5. Click + next to the operating system heading for the Oracle server.
6. Click the link for the Avamar Plug-in for Oracle installation package.
7. Save the Avamar Plug-in for Oracle installation package to a temporary directory.
Installing the Avamar file system client
You install the appropriate Avamar file system client before you install the Avamar Plug-in for
Oracle.
About this task
Install and register the Avamar file system client.
Installation

Procedure
l For HP-UX, IBM AIX, Linux, and Solaris systems, follow the instructions in the Avamar Backup
Clients User Guide.
l For Windows systems, follow the instructions in the Avamar for Windows Server User Guide.
Installing, upgrading, and uninstalling the software on HP-UX
You can install, upgrade, and uninstall the Avamar Plug-in for Oracle on HP-UX.
Installing the Avamar Plug-in for Oracle on HP-UX
You can use the swinstall command to install the Avamar Plug-in for Oracle in the default var
directory or in a new location. You use the -x ask=true option with the swinstall command
to specify a new location for the var directory during the Avamar Client for HP-UX installation.
About this task
When you install the Avamar Plug-in for Oracle after you install the Avamar Client for HP-UX, the
plug-in installation does not automatically use the same location for the var directory that you
specified during the Avamar Client for HP-UX installation. Install the Avamar Plug-in for Oracle by
using the -x ask=true option with the swinstall command.
Ensure that you install the Avamar Plug-in for Oracle in the same directory as the Avamar Client
for HP-UX.
Procedure
1. Log in to the Oracle server as root.
2. Change the directory to the temporary directory by typing the following command:
cd /tmp
where tmp is the temporary directory.
3. To install the Avamar Plug-in for Oracle in the default directory, type the following
command:
swinstall -s AvamarRMAN-platform-version.depot *
where:
l platform is the HP-UX platform type.
l version is the Avamar version number.
4. To install the Avamar Plug-in for Oracle in an alternate directory:
a. Type the following command:
swinstall -x ask=true -s /tmp/AvamarRMAN-platform-version.depot
hpuxrman,l=/install_path
where:
l platform is the HP-UX platform type.
l install_path is the installation directory.
b. Type the name of the directory to use for the installation.
The following appears in the command shell:
Installation

Confirm ‘/install_path/’ is the desired location. [n]
c. Type y to confirm the location.
Upgrading the Avamar Plug-in for Oracle on HP-UX
The version of the Avamar Client for HP-UX and Avamar Plug-in for Oracle must be the same
version.
Procedure
1. Uninstall the Avamar Plug-in for Oracle. Uninstalling the Avamar Plug-in for Oracle on HP-
UX on page 33 provides instructions.
2. Uninstall the Avamar Client for HP-UX. The Avamar Backup Clients User Guide provides
instructions.
3. Download and install the new version of the Avamar Client for HP-UX. The Avamar Backup
Clients User Guide provides instructions.
4. Download the Avamar Plug-in for Oracle installation package. Downloading the software on
page 31 provides instructions.
5. Install the new version of the Avamar Plug-in for Oracle. Installing the Avamar Plug-in for
Oracle on HP-UX on page 32 provides instructions.
Uninstalling the Avamar Plug-in for Oracle on HP-UX
You can uninstall the Avamar Plug-in for Oracle from an HP-UX system by using the swremove
command.
About this task
When you uninstall the Avamar Plug-in for Oracle and the Avamar Client for HP-UX from the host
system, scheduled backups no longer occur for the client. You cannot restore backups to the client
after you uninstall the software.
You can retire or delete a client either before or after you uninstall the Avamar Plug-in for Oracle:
l To keep the backups for the client so that you can restore the backups to a different client,
retire the client by using Avamar Administrator.
l To delete the backups for the client, delete the client by using Avamar Administrator.
The Avamar Administration Guide provides more information.
Procedure
2. Uninstall the Avamar Plug-in for Oracle by typing the following command:
swremove hpuxrman
Installing, upgrading, and uninstalling the software on IBM
AIX
You can install, upgrade, and uninstall the Avamar Plug-in for Oracle on IBM AIX.
Installing the Avamar Plug-in for Oracle on IBM AIX
You can install the Avamar Client for AIX software in either the default installation directory or an
alternate directory. Use the geninstall command to install the Avamar Plug-in for Oracle in the
Installation

default var directory or use the installp command to install the Avamar Plug-in for Oracle in a
new location.
About this task
for AIX. The installation returns an error if you install the Avamar Plug-in for Oracle in the default
directory after you install the Avamar Client for AIX in an alternate directory.
Procedure
cd /tmp
command:
geninstall -d AvamarRMAN-aix6-ppc-version.bff all
where version is the version of the Avamar software.
4. To install the Avamar Plug-in for Oracle in an alternate directory, type the following
command:
installp -R /install_path -d AvamarRMAN-aix6-ppc-version.bff all
where:
l install_path is the directory for the installation files.
l version is the Avamar software version.
Upgrading the Avamar Plug-in for Oracle on IBM AIX
Upgrade the Avamar Plug-in for Oracle before you upgrade the Avamar Client for AIX. The
versions of the Avamar Client for AIX and Avamar Plug-in for Oracle must be the same.
Procedure
1. Download the Avamar Plug-in for Oracle installation packages. Downloading the software on
cd /tmp
where tmp is the temporary install directory.
4. To upgrade the Avamar Plug-in for Oracle in the default installation directory, type the
following command:
geninstall -d AvamarRMAN-platform-version.bff all
where:
l platform is the AIX system type.
Installation

5. To upgrade the Avamar Plug-in for Oracle in an alternate installation directory, type the
following command:
installp -R /install_path -d AvamarRMAN-platform-version.bff all
where:
l install_path is the alternate installation directory.
6. Download the Avamar Client for AIX. The Avamar Backup Clients User Guide provides
instructions.
7. To upgrade the Avamar Client for AIX in the default installation directory, type the following
command:
geninstall -d AvamarClient-platform-version.bff all
where:
8. To upgrade the Avamar Client for AIX in an alternate installation directory, type the
following command:
installp -R /install_path -d AvamarClient-platform-version.bff all
where:
l install_path is the alternate installation directory.
Uninstalling the Avamar Plug-in for Oracle on IBM AIX
You can uninstall the Avamar Plug-in for Oracle from an IBM AIX system by using the
geninstall -u command.
About this task
When you uninstall the Avamar Plug-in for Oracle and the Avamar Client for AIX from the host
Procedure
2. To list Avamar packages installed in the default directory, type the following command:
Installation

lslpp -l | grep Avamar
The following appears in the command shell:
AvamarClient-aix6-ppc VERSION COMMITTED Avamar client VERSION
AvamarRMAN-aix6-ppc VERSION COMMITTED Avamar client VERSION
3. To list Avamar packages installed in an alternate installation directory, type the following
command:
lslpp -la -R /install_path | grep Avamar
where install_path is the alternate installation directory.
4. To uninstall the Avamar Plug-in for Oracle software, type the following command:
geninstall -u AvamarRMAN-aix6-ppc-version.bff
where version is the Avamar version number.
Installing, upgrading, and uninstalling the software on Linux
You can install, upgrade, and uninstall the Avamar Plug-in for Oracle on Linux.
Installing the Avamar Plug-in for Oracle on Linux
You can install the Avamar Plug-in for Oracle software in either the default installation directory or
an alternate directory.
About this task
for Linux.
Procedure
cd /tmp
command:
rpm -ivh AvamarRMAN-linux-platform-version.rpm
where:
l platform is the Linux system type.
4. To change base directory for the installation, type the following command:
rpm --relocate /usr/local/avamar=/install_path -i AvamarRMAN-linux-
platform-version.rpm
where:
l install_path is the new directory.
Installation

5. To change the base directory and var directory locations during the installation, type the
following command:
rpm -ivh --relocate /usr/local/avamar=install_path --relocate /var/
avamar=var_path AvamarRMAN-linux-platform-version.rpm
where:
l install_path is the new directory.
l var_path is the new var directory.
Upgrading the Avamar Plug-in for Oracle on Linux
You upgrade the Avamar Plug-in for Oracle by using the rpm -Uvh command. You can use the --
relocate option to specify the alternate installation or var directory that you specified when
you installed the initial version. The versions of the Avamar Client for Linux and Avamar Plug-in for
Oracle must be the same.
Procedure
1. Upgrade the Avamar Client for Linux by using the instructions in the Avamar Backup Clients
User Guide.
cd /tmp
3. To upgrade the software in the default directory, type the following command:
rpm -Uvh AvamarRMAN-linux-platform-version.rpm
where:
l platform is the Linux platform type.
4. To upgrade the software in a nondefault installation directory, type the following command:
rpm -Uvh --relocate /usr/local/avamar=install_path AvamarRMAN-linux-
platform-version.rpm
where:
l install_path is the installation directory that you specified when you installed the earlier
version of the Avamar Plug-in for Oracle software.
5. To upgrade the software and use a nondefault var directory, type the following command:
rpm -Uvh --relocate /var/avamar=var_path AvamarRMAN-linux-platform-
version.rpm
Installation

where:
l var_path is the var directory that you specified when you installed the earlier version of
the Avamar Plug-in for Oracle software.
The rpm -Uvh command automatically uninstalls the earlier version of the Avamar Plug-in
for Oracle, and then installs the new version.
Uninstalling the Avamar Plug-in for Oracle on Linux
You can uninstall the Avamar Plug-in for Oracle from a Linux system by using the rpm -e
command.
About this task
When you uninstall the Avamar Plug-in for Oracle and the Avamar Client for Linux from the host
Procedure
2. To view all Avamar packages installed on the system, type the following command:
rpm -qa | grep Av
A list of Avamar software appears in the command shell:
download-AvamarRMAN-version
download-AvamarClient-version
where version is the Avamar software version.
3. To uninstall the Avamar Plug-in for Oracle, type the following command:
rpm -e AvamarRMAN-version
where version is the version of the Avamar Plug-in for Oracle.
4. To uninstall the Avamar Client for Linux, type the following command:
rpm -e AvamarClient-version
where version is the version of Avamar Client for Linux.
The following output appears in the command shell:
avagent.d Info: Stopping Avamar Client Agent (avagent)...
avagent.d Info: Client Agent stopped.
Installation

Installing, upgrading, and uninstalling the software on Solaris
You can install, upgrade, and uninstall the Avamar Plug-in for Oracle on a stand-alone Solaris
system or on a Solaris cluster (VCS).
Installing the Avamar Plug-in for Oracle on a stand-alone Solaris
You can install the Avamar Plug-in for Oracle on a stand-alone system or on a Solaris cluster
(VCS).
About this task
Note: To install the Avamar Plug-in for Oracle on a Solaris cluster (VCS), skip this procedure
and continue with Installing the Avamar Plug-in for Oracle on a Solaris cluster on page 40.
Procedure
cd /tmp
3. Install the Avamar Plug-in for Oracle by typing the following commands:
pkgadd -d AvamarRMAN-solaris10-platform-version.pkg
where:
l platform is the Solaris platform type.
The following packages are available:
1 AVMRrman Avamar Client Plugin for Oracle RMAN
(sparc) 7.2.100-nnn
Select package(s) you wish to process (or 'all' to process
all packages). (default: all) [?,??,q]:
4. Type 1 and press Enter.
Processing package instance <AVMRrman> from
</AvamarRMAN-solaris10-sparc-7.2.100-nnn.pkg>
Avamar Client Plugin for Oracle RMAN(sparc) 7.2.100-nnn
## Executing checkinstall script.
Using as the package base directory.
## Processing package information.
## Processing system information.
4 package pathnames are already properly installed.
## Verifying package dependencies.
## Verifying disk space requirements.
## Checking for conflicts with packages already installed.
## Checking for setuid/setgid programs.
This package contains scripts which will be executed with
super-user permission during the process of installing this
Installation

package.
Do you want to continue with the installation of <AVMRrman> [y,n,?]
5. Type y and press Enter.
The installation runs to completion.
Installing the Avamar Plug-in for Oracle on a Solaris cluster
In a VCS configuration, install the Avamar Cluster Client for Solaris on both nodes in the cluster.
The Avamar Cluster Client for Solaris includes the Avamar Plug-in for Oracle.
About this task
Note: To install the Avamar Plug-in for Oracle on a stand-alone Solaris system, skip this
procedure and complete Installing the Avamar Plug-in for Oracle on a stand-alone Solaris on
page 39.
Procedure
1. Log in to the active VCS node as root.
cd /tmp
3. Install the software by typing the following commands:
pkgadd -d AvamarClusterClient-solaris10-platform-version.pkg
where:
l platform is the Solaris platform type.
The following packages are available:
1 AVMRclusclnt Avamar Cluster Client
(sparc) 7.2.100-nnn
Select package(s) you wish to process (or 'all' to process all
packages). (default: all) [?,??,q]:
Processing package instance <AVMRclusclnt> from
</home/source/fresh/installers/solpkgs/PKGS/AvamarClusterClient-
solaris10-sparc-7.0.100-nnn.pkg>
Avamar Cluster Client(sparc) 7.2.100-nnn
This software is copyright EMC Corporation, 2001-2014
Please read and agree to the End User License Agreement
which will be placed in the base directory of the install
as a file named AvamarClient-License.txt.
## Executing checkinstall script.
Using as the package base directory.
## Processing package information.
## Processing system information.
## Verifying package dependencies.
## Verifying disk space requirements.
## Checking for conflicts with packages already installed.
## Checking for setuid/setvtgid programs.
Installation

This package contains scripts which will be executed with
super-user permission during the process of installing this
package.
Do you want to continue with the installation of <AVMRclusclnt>
[y,n,?] y
The installation runs to completion.
6. Run avclustinstall by typing the following commands:
cd /opt/AVMRclusclnt/bin/
./avclusinstall
Setting PATH set for Veritas Cluster Server commands
Available service groups for configuration
1. oraclegrp
Select an option:
Selected service group: oraclegrp
Group State
oraclegrp PARTIAL
Enter the resource name of Avamar application for selected
service group (Default: avagent_oraclegrp):
Note: The state of oraclegrp can be either ONLINE or PARTIAL. Usually the state is
ONLINE.
8. Type the resource name of the Avamar application and press Enter.
Available mount Resources:
1. oramnt (Mount point: /fsclus01)
Selected mount resource: oramnt
Do you want to install Avamar Client Plugin for Oracle RMAN? (y/n)
[y]:
Enter the hostname or dns alias associated with virtual-ip
(15.16.140.13):
10. Type the hostname or DNS alias and press Enter.
Active node detected
=== Client Registration and Activation
This script will register and activate the client with the
Administrator server.
Using /opt/AVMRclusclnt/cluster/oraclegrp/var as the var dir
for the group oraclegrp avagent
Enter the Administrator server address (DNS text name or
numeric IP address, DNS name preferred):
Installation

Note: The hostname or DNS alias must match the hostname specified by the HOST
parameter in the tnsnames.ora and listener.ora files.
11. Type the hostname (defined in DNS) or IP address for the Administrator server and press
Enter.
Enter the Avamar server domain [clients]:
12. Type the domain name and press Enter.
avagent.d Info: Client Agent not running.
avagent Info <5241>: Logging to /opt/AVMRclusclnt/cluster/
oraclegrp/var/avagent.log
avagent Info <5174>: - Reading /opt/AVMRclusclnt/cluster/
oraclegrp/var/avagent.cmd
avagent.d Info: Client activated successfully.
avagent Info <5241>: Logging to /opt/AVMRclusclnt/cluster/
oraclegrp/var/avagent.log
avagent Info <5174>: - Reading /opt/AVMRclusclnt/cluster/
oraclegrp/var/avagent.cmd
avagent Info <5417>: daemonized as process id 7154
avagent.d Info: Client Agent started.
avagent.d Info: Stopping Avamar Client Agent (avagent)...
avagent.d Info: Client Agent stopped.
Registration Complete.
Avamar Client has been installed for service group 'oraclegrp'
successfully.
Do you want to install Avamar in another service group? (y/n) [n]:
13. Type n and press Enter.
14. Log in to the passive node as root and type the following commands:
cd /opt/AVMRclusclnt/bin
./avclusinstall
Setting PATH set for Veritas Cluster Server commands
Available service groups for configuration
1. oraclegrp
Select an option:
Selected service group: oraclegrp
Group State
oraclegrp OFFLINE
Do you want to install Avamar Client Plugin for Oracle RMAN? (y/n)
[y]:
Passive node detected.
Avamar Client has been installed for service group
Installation

'oraclegrp' successfully.
Do you want to install Avamar in another service group? (y/n) [n]:
17. Type n and press Enter.
18. Bring VCS resources online by typing the following command:
hares -online avagent_servicegroup -sys hostname
where:
l avagent_servicegroup is the default name of the Avamar VCS cluster agent. If you did
not select the default name in Upgrading the Avamar Plug-in for Oracle on HP-UX on
page 33, use the name you specified in Upgrading the Avamar Plug-in for Oracle on HP-
UX on page 33.
l hostname is the system where the VCS service group is in PARTIAL state.
Upgrading the Avamar Plug-in for Oracle on Solaris
The versions of the Avamar Client for Solaris and Avamar Plug-in for Oracle must be the same.
Procedure
1. Uninstall the Avamar Plug-in for Oracle. Uninstalling the Avamar plug-in on a stand-alone
Solaris on page 43 provides instructions.
2. Uninstall the Avamar Client for Solaris. The Avamar Backup Clients User Guide provides
instructions.
3. Download the Avamar Plug-in for Oracle installation package. Downloading the software on
4. Download and install the new version of the Avamar Client for Solaris. The Avamar Backup
Clients User Guide provides instructions.
5. Install the new version of the Avamar Plug-in for Oracle:
l Installing the Avamar Plug-in for Oracle on a stand-alone Solaris on page 39 provides
instructions for installations on a stand-lone system.
l Installing the Avamar Plug-in for Oracle on a Solaris cluster on page 40 on a Solaris
cluster.
Uninstalling the Avamar plug-in on a stand-alone Solaris
When you uninstall the Avamar Plug-in for Oracle and the Avamar Client for Solaris from the host
About this task
Procedure
1. Log in to the Oracle server host as root.
Installation

2. To view all Avamar packages installed on the system, type the following command:
pkginfo | grep AVMR
Information similar to the following appears in the command shell:
The following packages are currently installed:
1 AVMRclnt Avamar Client
(sparc) 7.2.100-nnn
2 AVMRrman Avamar Client Plugin for Oracle RMAN
(sparc) 7.2.100-nnn
3. To uninstall the software, type the following command:
pkgrm package_name
where package_name is the Avamar plug-in package displayed in step 2.
The following package is currently installed:
package_name
Do you want to remove this package?
Removal of package_name was successful.
Uninstalling the Avamar Cluster Client for Solaris
The Avamar Cluster Client for Solaris includes the Avamar Plug-in for Oracle. To uninstall the
Avamar Plug-in for Oracle on a Solaris cluster, you uninstall the Avamar Cluster Client for Solaris.
About this task
The Avamar Backup Clients User Guide provides instructions for uninstalling the Avamar Cluster
Client for Solaris software.
Installing, upgrading, and uninstalling the software on
Windows
You can install, upgrade, and uninstall the Avamar Plug-in for Oracle on a stand-alone Windows
system or on a Windows cluster.
Installing the Avamar Plug-in for Oracle on Windows
Install the Avamar Plug-in for Oracle on both Windows stand-alone systems and MSCS two-node
clusters. In a cluster, install the Avamar Plug-in for Oracle on both nodes and in the same directory
on each node.
Before you begin
l The Avamar Plug-in for Oracle is automatically installed in the same folder as the Avamar Client
for Windows.
l If the Oracle software is installed with the New Windows User, ensure that the Avamar Plug-in
for Oracle software is installed outside of the default path. For example, C:Program Files
avs.
Installation

l If UAC is enabled on the client computer, you must start the setup wizard by using
administrator privileges. Otherwise, the software does not install correctly. This procedure
provides one method to bypass UAC. The Microsoft documentation provides other methods
and additional information.
Procedure
1. Log in to the Oracle server as an administrator.
2. Go to the temporary directory that contains the installation files that you downloaded in
Downloading the software on page 31.
3. Start the Avamar Plug-in for Oracle installation:
l If UAC is disabled, double-click the installation package to open it.
l If UAC is enabled, open a command prompt as an administrator, change directory to the
location of the installation package, and then type the following command:
msiexec /i AvamarRMAN-windows-platform-version.msi
where:
n platform is the Windows platform type.
n version is the Avamar software version.
The welcome page appears.
4. Click Next.
The Ready to install Avamar Backup Plug-in for Oracle page appears.
5. Click Install.
The Installing Avamar Backup Plug-in for Oracle page appears. A status bar shows the
installation’s progress. After the installation completes, the Completed the Avamar Backup
Plug-in for Oracle Setup Wizard page appears.
6. Click Finish.
7. In a cluster, repeat this installation procedure on each node.
Configuring the Avamar cluster client on Windows
The Avamar cluster client enables you to back up and restore Oracle data on shared storage in a
cluster, regardless of which node is managing the data at the time of the backup or restore. Use
the Cluster Configuration Tool to configure the Avamar cluster client on the active node in an
active/passive configuration or on both active nodes in an active/active configuration.
Before you begin
Before you run the Cluster Configuration Tool, ensure that the Avamar Client for Windows and the
Avamar Plug-in for Oracle are installed on each node in the cluster and each node is registered to
the Avamar server.
Procedure
1. Log in to the active node in the cluster as a domain administrator. The account must be a
member of the local Administrators group on each cluster node.
2. Start the Cluster Configuration Tool:
l On Windows Server 2012, open the Start screen and select Cluster Configuration Tool.
l On Windows Server 2008, open the Start menu and select Program Files > Avamar >
Cluster Configuration Tool.
Installation

3. Click Next.
The Plug-Ins page appears.
4. Select Avamar Backup Plug-in for Oracle from the Avamar Backup Plug-ins list, and then
click Next.
The Cluster Nodes page appears with a list of nodes and their status.
5. Ensure that the status of all nodes is Up, and then click Next.
The Operations page appears.
6. Select the Configure new Oracle Virtual Client for cluster option, and then click Next.
Note: Select the Use existing configuration to configure new nodes for Oracle
Virtual Clients on cluster option to add a node to an existing configuration. The Avamar
for Windows Server User Guide provides more information.
The Prerequisites page appears. A check mark next to a prerequisite indicates that the
prerequisite is met.
7. Ensure that the environment meets all prerequisites on the Prerequisites page.
If a prerequisite is not met, exit the wizard, resolve the issue, and restart the wizard.
8. Select the Internet Protocol version that the environment uses, and then click Next.
The Attach to Service page appears.
9. Select the cluster service for the plug-in, and then click Next.
The Server Settings page appears.
10. Specify the settings for the Avamar server:
a. Type either the DNS name of the Avamar server in the Name box or the IP address in the
IPv4/IPv6 address box.
b. Type the name of the Avamar domain for the cluster client in the Client domain for
cluster box.
To specify a domain at the root level, type /domain, where domain is the domain name.
To specify a subdomain, type /domain/subdomain, where domain is the domain name
and subdomain is the subdomain name.
c. Type the data port for Avamar client/server communication in the Port number box.
Note: Port 28001 is the default port that the Avamar client uses to communicate
with the Avamar server.
d. Type the name of the shared network directory or volume in the Cluster client’s var
directory box or click Browse to select a shared network directory or volume.
The shared network directory or volume stores the cluster client configuration and the
log files. All nodes in the cluster must have write access to this directory or volume.
Note: Select a volume that the cluster owns instead of a remote pathname on the
network.
e. Click Next.
The Summary page appears.
11. Review the configuration settings, and then click Configure.
The Progress page provides the status of the configuration. When the configuration
process completes, the Results page appears.
Installation

12. Click Close.
Upgrading the Avamar Plug-in for Oracle on Windows
The steps to upgrade the Avamar Plug-in for Oracle on Windows depend on whether the
installation is on a stand-alone server or in a cluster.
Upgrading on a stand-alone Windows server
When you upgrade the Avamar Plug-in for Oracle on a stand-alone server, you do not need to
uninstall earlier versions before you install a new version. The installation determines that an earlier
version is installed, and then prompts you to upgrade to the new version or remove the current
version.
Procedure
1. Ensure that you meet all system requirements for the new version. Preparing to install the
Avamar Plug-in for Oracle on page 30 provides more information.
2. Upgrade the Avamar Client for Windows by running the Windows client installation wizard
for the new version on the client computer. The Avamar for Windows Server User Guide
provides instructions.
3. Upgrade the Avamar Plug-in for Oracle by running the plug-in installation wizard for the new
version on the client computer. Installing the Avamar Plug-in for Oracle on Windows on page
44 provides instructions.
Upgrading in a Windows cluster
When you upgrade the Avamar Client for Windows and Avamar Plug-in for Oracle software in a
cluster, you must uninstall the earlier version of the Avamar client and plug-in from each node, and
then install the new version.
Procedure
1. Uninstall the current version of the Avamar Client for Windows and Avamar Plug-in for
Oracle:
a. Use the earlier version of the Cluster Configuration Tool to uninstall the Avamar cluster
client. Uninstalling the cluster client on page 48 provides instructions.
b. Uninstall the earlier version of the Avamar Plug-in for Oracle on each node in the cluster.
c. Uninstall the earlier version of the Avamar Client for Windows on each node in the
cluster.
The plug-in guide for the earlier versions provides instructions.
2. Install the new version of the Avamar Client for Windows and Avamar Plug-in for Oracle:
a. Install the Avamar Client for Windows in the same directory on each node in the cluster.
The Avamar for Windows Server User Guide provides instructions.
Note: If the Oracle software is installed with the New Windows User, ensure that the
Avamar Plug-in for Oracle software is installed outside of the default path. For
example, C:Program Filesavs.
b. Install the Avamar Plug-in for Oracle in the same directory on each node in the cluster.
Installing the Avamar Plug-in for Oracle on Windows on page 44 provides instructions.
c. Register each node in the cluster with the Avamar server. The Avamar for Windows Server
User Guide provides instructions.
Installation

d. Use the Cluster Configuration Tool to install the Avamar cluster client on an active node.
Configuring the Avamar cluster client on Windows on page 45 provides instructions.
Uninstalling the Avamar Plug-in for Oracle on Windows
When you uninstall the Avamar Plug-in for Oracle and the Avamar Client for Windows from the
host system, scheduled backups no longer occur for the client. You cannot restore backups to the
client after you uninstall the software.
About this task
The steps to uninstall the Avamar Plug-in for Oracle on Windows depend on whether the
installation is on a stand-alone server or in a cluster.
Uninstalling on a stand-alone Windows server
Use the Windows uninstall feature to uninstall the Avamar Client for Windows and Avamar Plug-in
for Oracle software.
Procedure
1. Uninstall the Avamar Plug-in for Oracle by using Programs and Features.
2. Uninstall the Avamar Client for Windows by using Programs and Features.
Uninstalling the cluster client
In a Windows cluster, use the Cluster Configuration Tool to uninstall the Avamar cluster client.
Then use the Windows uninstall feature to uninstall the Avamar Client for Windows and Avamar
Plug-in for Oracle software from each node.
Procedure
1. Log in to the active node in the cluster as a domain administrator. The account must be a
member of the local Administrators group on each cluster node.
2. Start the Cluster Configuration Tool:
l On Windows Server 2012, open the Start screen and select Cluster Configuration Tool.
l On Windows Server 2008, open the Start menu and select Program Files > Avamar >
Cluster Configuration Tool.
3. Click Next.
The Plug-Ins page appears.
4. Select Avamar Backup Plug-in for Oracle and click Next.
The Cluster Nodes page appears with a list of nodes and each node’s status.
5. Ensure that the status of all nodes is Up, and then click Next.
The Operations page appears.
6. Select Remove the Oracle Virtual Client from all nodes in cluster and click Next.
The Prerequisites page appears. A check mark next to a prerequisite indicates that the
prerequisite has been met.
Installation

7. Ensure that the environment meets all prerequisites on the page, and then click Next.
The Summary page appears.
8. Review the configuration settings and click Uninstall.
The Progress page provides the status of the uninstall operation. When the uninstall
completes, the Results page appears.
9. Click Close.
10. Uninstall the Avamar Plug-in for Oracle from each node by using Programs and Features.
11. Uninstall the Avamar Client for Windows from each node by using Programs and Features.
Excluding Oracle directories from file system backups
You can optimize Oracle database backups and save storage space by creating a dataset that
excludes the platform-specific file system from the Avamar Plug-in for Oracle backup.
About this task
Note: Including Oracle database files with the file system backup consumes storage space in
the Avamar system and increases network traffic during the nightly backup window.
Create a dataset that excludes the entire root directory branch for each Oracle instance, and then
assign the dataset to the Avamar client. For example, if the full pathname of a database instance
is /space/local/oracle/ora901, exclude this directory in the Avamar dataset.
Procedure
1. Open the oratab file in a text editor and note the home directory for all Oracle database
instances.
2. In Avamar Administrator, select Tools > Manage Dataset.
The Manage All Datasets window appears.
3. Click New.
The New Dataset dialog box appears.
4. In the Name box, type a name for the dataset.
The name can include alphanumeric characters (A-Z, a-z, 0-9) and the following special
characters: period (.), hyphen (-), and underscore (_). Do not use Unicode characters or
the following special characters: ` ~ ! @ # $ % ^ & * ( ) = + [ ] { } | / ; : ' " < > , ?
5. Click the Source Data tab.
The Source Data tab is where you define a list of source data plug-ins that contribute data
to this dataset.
a. Select Enter Explicitly and select the plug-in from the Select Plug-In Type list.
b. To remove a plug-in from the dataset, select the plug-in from the list in the bottom
portion of the New Dataset dialog box, and then click -. Repeat this step as necessary.
Note: The Avamar Plug-in for Oracle does not support include or exclude lists in
datasets.
6. Click the Options tab and select the plug-in from the Select Plug-In Type list.
The windows expands to display plug-in options.
7. Complete the following fields:
Installation

a. Leave the Oracle instance name field blank. The Oracle instance name is filled in when
the Oracle server is assigned to a group.
b. (Optional) For Oracle 12c and later, if the Oracle user has SYSBACKUP privileges (instead
of SYSDBA), select SYSBACKUP privilege.
c. Type the username to use to authenticate the Oracle database in the Username field. If
you leave the Username field blank, RMAN tries to log in with the same username and
password that the Avamar client agent uses, and attempts to assume SYSDBA (or
SYSBACKUP) privileges.
d. Type the password for the account in the Password field.
e. Click OK.
The New Dataset dialog box closes. The new dataset appears in the left pane of the
Manage All Datasets window.
8. Click OK.
The Manage All Datasets window closes.
9. In Avamar Administrator, click the Policy launcher link button.
The Policy window appears.
10. Click the Policy Management tab.
11. Click the Clients tab.
The left pane contains a list of domains.
12. Click the domain that contains the Oracle server.
A list of Avamar clients appears in a table to the right of the domains list.
13. Click the client that runs the Oracle server.
14. Select Actions > Client > Edit Client.
The Edit Client dialog box appears.
15. In the Edit Client dialog box, complete the following setting:
a. Click the Dataset tab.
b. From the Select An Existing Dataset list, select the dataset you created in step 4 on
page 49.
c. Select Override group dataset.
d. Click OK.
Installation

CHAPTER 3
Oracle RAC Configuration
l Managing Oracle RAC on Linux or UNIX................................................................................52
l Managing Oracle RAC on Windows Server 2008...................................................................55

Managing Oracle RAC on Linux or UNIX
The Avamar Plug-in for Oracle supports Oracle RAC configurations on HP-UX, IBM AIX, Linux, and
Solaris systems. Before you can back up Oracle RAC configurations, you must run the
rac_config script and register the client with the Avamar server.
About this task
Note: We recommend that you configure a shared var directory. The Avamar Plug-in for
Oracle supports automatic failover for the Avamar agent if the active node goes down,
regardless of whether the var directory is a shared. However, if there be configurations with
non-shared var directories, the Avamar logs are saved only on local node.
Running the rac_config script
To configure Oracle RAC on HP-UX, IBM AIX, Linux, or Solaris, run the rac_config script on
each RAC node. Specify the same shared Avamar var directory for each node that you configure.
Procedure
1. Log in to one of the Oracle RAC nodes as root.
2. Change the directory to /usr/local/avamar/bin by typing the following command:
cd /usr/local/avamar/bin
3. Start the script by typing the following command:
./rac_config
Enter the path of Oracle Clusterware Home : /u01/app/11.2.0/grid
Using ORACLE_HOME : /u01/app/11.2.0/grid
Setting PATH set for Oracle commands
Oracle cluster version 11 R2
Do you want to configure on a cluster shared filesystem? [y/n] [y]:
y
Enter the full path of var directory location[]:
Enter y if var is a shared directory. Enter n if var is a non-
shared directory: [y] y
4. Type the directory path, and then press Enter.
Enter the virtual hostname [vlrac1]:
where vlrac1 is the scan name for Oracle grid 11g R2.
5. Press Enter to accept the default virtual hostname.
Using vlrac1 as hostname
6. Repeat steps 2 through 5 on the other nodes.
After you finish
To ensure that backups using the RMAN CLI backups are viewable in the Avamar Administrator
Activity window, copy the avoracle.cmd file from ../ora_rac/var/ to ../ora_rac/var/
clientlogs/. The following options must be present in avoracle.cmd:

l --rac_cluster
l --hostname = cluster scan name
Changing the listening port for RAC avagent
The rac_config script configures the system to use a fixed listening port number, 28003, for
communication. Some RAC configurations might have firewall limitations that do not allow the use
of the default listening port, 28003. In these instances, you can manually change the listening port
to be a random port number by changing the value of the --acport option or by replacing the --
acport option in the avagent.cmd file.
Changing the value of the acport option in the avagent.cmd file
Procedure
1. Log in to the Oracle RAC system as root.
2. Add the Oracle Clusterware Home directory to the PATH environment variable.
3. Stop the avagent process for RAC by typing the following command:
crsctl stop resource EMCagent
4. Navigate to the var directory for RAC.
This directory contains the avagent.cmd file.
5. Open the avagent.cmd file in an editor.
6. Change the value for the --acport option to a number between 28003 and 28008.
7. Save and close the avagent.cmd file.
8. If the var directory is not shared, repeat steps 4 on page 53 through 7 on page 53 on all
nodes.
9. Restart the avagent process for RAC by typing the following command:
crsctl start resource EMCagent
Replacing the acport option in the avagent.cmd file
Procedure
1. Log in to the Oracle RAC system as root.
2. Stop the avagent process for RAC by typing the following command:
3. Navigate to the var directory for RAC.
This directory contains the avagent.cmd file.
4. Open the avagent.cmd file in an editor.
5. Replace the --acport line with the following two lines:
--disable_nonlocal_listenport
--disablegui
6. If the var directory is not shared, repeat steps 4 on page 53 and 5 on page 53 for all nodes.
7. Restart the avagent process for RAC by typing the following command:

Registering the Avamar client
After you run the rac_config script on each RAC node, you run the avregister command on
one cluster node. The avregister command registers and activates the Avamar client with the
Avamar server.
Procedure
1. Log in to one of the Oracle RAC nodes as root.
Note: Run avregister on one RAC node only.
2. Change the directory to /usr/local/avamar/ora_rac/bin by typing the following
command:
cd /usr/local/avamar/ora_rac/bin
3. Start the registration script by typing the following command:
./avregister
4. Type the DNS hostname or IP address of the Administrator server, and then press Enter.
5. Press Enter to accept the default domain (clients).
avagent.d Info: Server stopped. [ OK ]
avagent Info <5241>: Logging to /usr/local/avamar/ora_rac/var/
avagent.log
avagent.d Info: Client activated successfully. [ OK ]
avagent.log
avagent.d Info: Server started. [ OK ]
6. If the var directory is not being shared, copy the files /usr/local/avamar/
ora_rac/var/cid.bin and /usr/local/avamar/ora_rac/var/avagent.cfg from
this node into the same directory on all the other nodes. You do not need to do this step if
the var directory is being shared.
Results
Once you register the Avamar client with the Avamar server, start.sh runs and starts
EMCagent as an Oracle Clusterware resource on the current node. Backups and restores connect
to the RAC database instance on the active node. If the active node goes down, EMCagent

automatically restarts on one of the other RAC nodes. The new node then automatically notifies
Avamar server of the address change for the active node.
Changing the active node
You can make the inactive node the active node by restarting the EMCagent on the inactive node.
Procedure
1. Log in to the inactive cluster node as root.
2. Change the directory to the shared installation_path/ora_rac/etc directory.
3. Restart EMCagent by typing the following command:
./start.sh
Removing the Oracle RAC configuration
You can use rac_deconfig to remove the Oracle RAC configuration from one node only or both
nodes. If the EMCagent resource is online, you must first move it to a different node before
running rac_deconfig.
Procedure
1. Log in to the registered node as root.
3. Stop EMCagent and remove it from the Oracle Clusterware resources by typing the
following command:
./rac_stop
/usr/local/avamar/bin/rac_stop
Enter the path of Oracle Clusterware Home:
4. Run the rac_deconfig script by typing the following command:
./rac_deconfig
avagent.d Info: Client Agent not running.
[PASSED]
Results
The rac_deconfig script deletes the Avamar_install_dir/ora_rac directory.
Managing Oracle RAC on Windows Server 2008
The Avamar Plug-in for Oracle supports Oracle RAC configurations on Windows Server 2008
systems. Before you can back up Oracle RAC configurations on Windows Server 2008 systems,
you must run AvamarRACConfiguration.exe on one Oracle cluster node.
About this task
Note: We recommend that you configure a shared var directory. The Avamar Plug-in for
Oracle supports automatic failover for the Avamar agent if the active node goes down,

regardless of whether the var directory is a shared. However, if there be configurations with
non-shared var directories, the Avamar logs are saved only on local node.
Running AvamarRACConfiguration.exe
AvamarRACConfiguration.exe is installed as part of the Avamar Plug-in for Oracle installation
and is located in C:Program Filesavsbin. To configure Oracle RAC on Windows Server
2008, run AvamarRACConfiguration.exe on one Oracle cluster node.
Procedure
1. Log in to one of the Oracle cluster nodes as an administrator.
2. Double-click C:Program FilesavsbinAvamarRACConfiguration.exe.
The Setup Avamar RAC Configuration for Windows dialog box appears.
3. Select the correct name from the Choose Oracle RAC Scan Name/Virtual list:
l For Oracle 11g R1, select the virtual hostname.
l For Oracle 11g R2, select the scan name.
4. Type the full pathname and folder name for the var folder in the Var folder field.
To browse the file system for the var folder, click Browse and select the var folder from
the File Open dialog box.
5. Select the Shared checkbox if the var folder is a shared folder or disk.
Note: The Change Avamar Server Registration option is disabled if the Avamar server
is not configured.
6. Type the DNS hostname or IP address for the Avamar server in the Administrator server
hostname or IP field.
7. Type the port for the Avamar server in the Administrative server listen port field. The
default value is 28001.

8. Type the domain name in the Backup domain for this client field. The default value is
clients.
9. Select one or more nodes from the Available Nodes box.
To select multiple entries, press and hold the Ctrl key while you select entries with the
mouse.
10. Click Configure.
After you finish
To ensure that backups using the RMAN CLI backups are viewable in the Avamar Administrator
Activity window, copy the avoracle.cmd file from ../ora_rac/var/ to ../ora_rac/var/
clientlogs/. The following options must be present in avoracle.cmd:
l --rac_cluster
l --hostname = cluster scan name
Starting the EMCagent clusterware resource
You start the EMCagent on one node only.
Procedure
1. Log in to one of the Oracle cluster nodes as an administrator.
2. Start EMCagent from the Command Prompt by typing one of the following commands:
l For Oracle 11g R1, type the following command:
crs_start EMCagent
l For Oracle 11g R2, type following command:
Verifying the Oracle RAC configuration
After running AvamarRACConfiguration.exe and starting the EMCagent, verify the Oracle
RAC configuration.
Procedure
1. Log in to the Oracle cluster node as an administrator.
2. Ensure that the Avamar Oracle RAC Backup Agent appears in the Windows Services list.
3. Verify that the EMCagent resource was added to Oracle Clusterware by typing one of the
following commands:
crs_stat EMCagent
crsctl status resource EMCagent
Stopping the Oracle EMCagent
Stop the EMCagent from the Oracle cluster node.
Procedure
1. Log in to the Oracle cluster node where EMCagent is running as an administrator.
2. Stop EMCagent from the Command Prompt by typing one of the following commands:

crs_stop EMCagent
Adding a new node to an Oracle RAC configuration
Add a node to an Oracle RAC configuration by running AvamarRACConfiguration.exe on any
one node.
Procedure
crs_stop EMCagent
2. Use Avamar Administrator to deactivate the registered Oracle RAC client:
a. In Avamar Administrator, click the Policy launcher link button.
The Policy window appears.
b. Click the Policy Management tab.
c. Click the Clients tab.
d. Select the client from the table.
e. Select Actions > Client > Edit Client.
The Edit Client dialog box appears.
f. Click the Properties tab.
g. Clear the Activated checkbox.
3. Run AvamarRACConfiguration.exe on any one node.
The Cluster Configured Node section displays all configured nodes.
The Oracle RAC Parameters, Logs/ Var Folder, and Registration group boxes are
disabled when you add a new node to a cluster configuration.
4. Select a node from the Available Nodes group box.
To select multiple entries, press and hold the Ctrl key while you select entries with the
mouse.
5. After you add the node to the configuration, start the EMCagent on any Clusterware node:
crs_start EMCagent

Re-registering a node with a different Avamar server
Run to AvamarRACConfiguration.exe to re-register a RAC node with a different Avamar
server.
Procedure
crs_stop EMCagent
2. Run AvamarRACConfiguration.exe.
The Cluster Configured Nodes group box display all configured nodes.
3. Select the Change Avamar Server Registration checkbox.
The Setup Avamar Oracle RAC Configuration for Windows dialog box appears.
Selecting the Change Avamar Server Registration option clears the nodes in the Available
Nodes group box.
4. Type the DNS hostname or IP address for the Avamar server in the Administrator server
hostname or IP field.
5. Type the port for the Avamar server in the Administrative server listen port field. The
default value is 28001.
6. Type the domain name in the Backup domain for this client field. The default value is
clients.
7. Click Register.
8. After the registration completes, start the EMCagent on any of the Clusterware nodes by
typing one of the following commands:
crs_start EMCagent
Resetting the Oracle RAC configuration
You cannot perform a reset operation on a node that is not a member of the cluster configuration.
Procedure
1. Log in to the Oracle cluster node as an administrator.
2. On any cluster node, run AvamarRACConfiguration.exe.
The Setup Avamar RAC Configuration for Windows dialog box appears.
3. Click Reset.
All the nodes in Cluster Configured Nodes group box are deleted and unregistered from
the Avamar server.

CHAPTER 4
High Availability Oracle Single-Instance Database
Configuration
l Highly available Oracle single-instance databases................................................................. 62

Highly available Oracle single-instance databases
The Avamar Plug-in for Oracle supports the backup of Oracle single-instance databases that are
configured as high availability with failover support.
As part of the Avamar Plug-in for Oracle support for high availability Oracle single-instance
databases, there must be one resource which controls the failover of the single-instance
databases. The Avamar service relies on this resource to initiate a failover of the Avamar client. A
shared Avamar var directory must be used by all nodes.
Configuring highly available single-instance databases on Linux or UNIX
Before you can back up high availability Oracle single-instance database configurations, you must
run the si_config script and register a corresponding virtual client with the Avamar server.
Procedure
1. Log in as root to any of the Oracle cluster nodes where the single-instance database has
been configured.
2. Change to the /usr/local/avamar/bin:
3. Run the si_config command:
./si_config -d database_name -r resource -p 28004 -h /u01/app/11.2.0/
grid -v shared_directory -n "node_names"
where:
l database_name is the name of the single-instance database.
l resource is the resource which controls the failover of the single-instance database (for
example, ora.dbsi1.db).
l shared_directory is a shared directory (for example, /cluster_share/).
l node_names is a space-separated list of the names of the nodes on which the single-
instance database is configured.
Example command line:
./si_config -d DBSI1 -r ora.dbsi1.db -p 28004 -h /u01/app/11.2.0/grid -
v /cluster_share/dbsi1 -n "bu-lin-earth bu-lin-mars"
Note: Run the si_config command on one node only.
The script will prompt you for the client name.
4. Enter the client name or press Enter to accept the default selection:
Enter the client name for database_name [Client_name]
High Availability Oracle Single-Instance Database Configuration

5. If ssh autologin is not set up for the root user, you will be prompted to enter the root
password for each remote node:
root@node_name's password:
Enter the root password for each node when prompted.
This will allow configuration on all other nodes.
Registering the highly available single-instance database client
After you run the si_config script, run the avregister command on any node where the
single-instance database is configured. The avregister command registers and activates the
Avamar client with the Avamar server.
Procedure
1. Log in as root to one of the cluster nodes where the single-instance database is configured.
Note: Run avregister on one node only.
2. Change the directory to /usr/local/avamar/ora_database_name/bin by typing the
following command:
cd /usr/local/avamar/ora_database_name/bin
where database_name is the name of the single-instance database.
3. Start the registration script by typing the following command:
./avregister
4. Type the DNS hostname or IP address of the Administrator server, and then press Enter.
5. Press Enter to accept the default domain (clients).
avagent.d Info: Server stopped. [ OK ]
avagent.log
avagent.d Info: Client activated successfully. [ OK ]
avagent.log
avagent.d Info: Server started. [ OK ]
Results
Once you register the Avamar client with the Avamar server, start.sh runs and starts
EMCagent as an Oracle cluster resource.

Note: If the database instance is running on another node, EMCagent_database_name will
automatically fail over to the node on which the instance is running.
Management Console-initiated backups and restores are sent to the node where the
EMCagent_database_name is running. If the database instance fails over to another node, the
EMCagent_database_name resource is failed over to that node as well. The new node then
automatically notifies the Avamar server of the address change for the active node.
Removing the highly available single-instance database configuration
You can use si_deconfig to remove the configuration for Oracle Single Instance from all nodes.
Procedure
1. Log in as root to one of the cluster nodes where the single-instance database is configured.
3. Run the si_deconfig script by typing the following command:
./si_deconfig -d database_name
where database_name is the name of the single-instance database.
4. If ssh autologin is not set up for the root user, you will be prompted to enter the root
password for each remote node:
root@node_name's password:
Enter the root password for each node when prompted.
This step allows deconfiguration on all other nodes.
Results
The si_deconfig script removes the related EMCagent cluster resource
(EMCagent_database_name) for the database from the Oracle Clusterware resources and deletes
the avamar_install_dir/ora_database_name directory.
Configuring highly available single-instance databases on Windows
Before you can back up high availability Oracle single-instance database configurations, you must
run the AvamarSDConfiguration.exe program as Administrator, which registers a
corresponding virtual client with the Avamar server.
Before you begin
Each node to be configured must register and activate to the same Avamar server before this
configuration, otherwise you may get certification issues when performing browse, backup, and
restore operations. There must be one resource which controls the failover of the single-instance
database. The Avamar service relies on this resource to a following failover of the Avamar client
Procedure
1. Log in to any of the Oracle cluster nodes where the single-instance database has been
configured.
2. Right-click the file C:Program Filesavsbin AvamarSDConfiguration.exe
and select Run as Administrator.
The Setup Avamar for Oracle Single-Instance Database dialog box opens.

Figure 6 Setup Avamar for Oracle Single-Instance Database dialog
3. Type the name of the single-instance database and click Lookup.
After a successful lookup, if the database has not been configured before, nodes are listed
under Available Nodes.
a. For Var Folder, type a var directory or click Browse to select one.
Note: The var directory all nodes being configured.
b. For Administrator Server Hostname or IP, type the hostname or IP address of the
Avamar server.
c. For Administrator Server Listen Port, type the port number of the Avamar server listen
port.
d. For Backup Domain for this Client, type the client's backup domain on the Avamar
server.
e. For Connection Port (acport), type the port number of the connection port.
f. Select the nodes to be configured in the Available Nodes list.
g. Click Configure.
Note: All fields must be completed before beginning the configuration.

A message indicates that the configuration was successful. Click OK clear the message.
You can start another single-instance database configuration by clicking Next Config.
After the configuration is complete, EMCagent_database_name is available and ready for
failover.
4. Start the EMCagent_database_name by typing the following at the command line:
crsctl start res EMCagent_database_name
EMCagent_database_name then runs on the node on which the single-instance database
instance is running.
Results
Management Console-initiated backups and restores are sent to the node where the EMCagent
cluster resource (EMCagent_database_name) is running. If the database instance fails over to
another node, the EMCagent_database_name resource is failed over to that node as well. The
new node then automatically notifies the Avamar server of the address change for the active node.
Adding additional nodes to a single-instance database configuration
To add additional nodes to a single-instance database configuration, stop the
EMCagent_database_name and run the AvamarSDConfiguration.exe program as
Administrator.
Procedure
configured.
2. Stop the EMCagent cluster resource by typing the following at the command line:
crsctl stop resource EMCagent_database_name

4. Type the name of the single-instance database and click Lookup.
After a successful lookup, already-configured nodes are listed under Cluster Configuration
Nodes and any additional nodes that are available to be configured are listed under
Available Nodes.
5. In Available Nodes, select the nodes to be configured.
6. Click Configure.
7. Restart the EMCagent cluster resource by typing the following at the command line:
crsctl start res EMCagent_database_name
Re-registering a single-instance database with a different Avamar server
To register a current single-instance database to another Avamar server, run the
AvamarSDConfiguration.exe program as Administrator.
Before you begin
Each node to be configured must register and activate to the same Avamar server before this
configuration, otherwise you may get certification issues when performing browse, backup, and
restore operations.

Procedure
configured.
3. Enter the name of the single-instance database and click Lookup.
4. Select the Change Avamar Server Configuration checkbox and complete the following
information:
a. For Administrator Server Hostname or IP, enter the hostname or IP address of the
new Avamar server.
b. For Administrator Server Listen Port, enter the port number of the new Avamar server
listen port.
c. For Backup Domain for this Client, enter the client's backup domain on the new
Avamar server.
d. Click Register.

Removing a single-instance database configuration on Windows platforms
To remove a single-instance database configuration, run the AvamarSDConfiguration.exe
program as Administrator.
Procedure
configured.
3. Enter the name of the single-instance database and click Lookup.
4. Click Reset to remove the configuration.
Results
The EMCagent cluster resource (EMCagent_database_name) for the database is removed from
the Oracle Clusterware resources and the corresponding service Avamar Oracle database_name
Backup Agent is deleted from all the configured nodes.

CHAPTER 5
Backup
l Creating the Oracle user account.......................................................................................... 72
l Enabling Block Change Tracking............................................................................................72
l Preparing the database for backup .......................................................................................72
l Performing an on-demand backup.........................................................................................73
l Scheduling backups............................................................................................................... 77
l Monitoring backups...............................................................................................................80
l Cancel backups..................................................................................................................... 80
l Oracle RAC backup failures....................................................................................................81
l Enforcement of backups to Data Domain...............................................................................81

Creating the Oracle user account
If an Oracle user account with SYSDBA (or SYSBACKUP) privileges does not exist, you must create
one. The Avamar software uses the Oracle account to perform database backups and restores.
Procedure
l Specify the username and password in the Backup Command Line Options, Restore
Command Line Options, and New Dataset dialog boxes.
Oracle documentation provides instruction for creating an Oracle user account.
Note: To use an RMAN catalog, you must configure the catalog.
Enabling Block Change Tracking
The Block Change Tracking feature can improve level 1 (differential and cumulative) backup
performance by recording changed blocks in each datafile in a block change tracking file.
Procedure
1. Determine whether Block Change Tracking is enabled by typing the following
command from an SQL prompt:
select status from v$block_change_tracking;
The STATUS column shows whether Block Change Tracking is enabled. The
FILENAME column contains the file name of the block change tracking file. Oracle
documentation provides more information about v$block_change_tracking.
2. Enable Block Change Tracking by typing the following command from an SQL prompt:
alter database enable block change tracking using file 'filename';
where filename is the absolute pathname of the file to be used for Block Change
Tracking. Oracle uses this file to track datafile changes. Oracle documentation provides
more information about Block Change Tracking.
Note: To schedule level 0, level 1 differential, and level 1 cumulative backups, create
three backup schedules: one for level 0 backups, one for level 1 differential backups, and
one for level 1 cumulative backups. Scheduling backups on page 77 provides more
information.
Preparing the database for backup
Before you back up an Oracle database, you must prepare the database. You must determine
whether the database is in ARCHIVELOG mode. If the database is not in ARCHIVELOG mode, you
must use the alter database archivelog command to set it.
Procedure
1. Connect to the database by typing the following command:
sqlplus "/ as sysdba"
The command prompt changes to the SQL prompt.
2. Determine if the Oracle database is in ARCHIVELOG mode by typing the following command:
Backup

select log_mode from v$database;
If archiving is not set for the database, screen output similar to the following output
appears:
LOG_MODE
----------
NOARCHIVELOG
3. Shut down the database by typing the following command:
shutdown immediate;
The following information appears in the command shell:
Database closed.
Database dismounted.
ORACLE instance shut down.
4. Start the database by typing the following command:
startup mount;
ORACLE instance started.
Total System Global Area 171966464 bytes
Fixed Size 787988 bytes
Variable Size 144964076 bytes
Database Buffers 25165824 bytes
Redo Buffers 1048576 bytes
Database mounted.
5. Change the database archiving mode by typing the following command:
alter database archivelog;
Database altered.
6. Open the database for normal operations by typing the following command:
alter database open;
Database altered.
7. Disconnect from the database by typing the following command:
exit
8. Back up the database by following the instructions in Performing an on-demand backup on
page 73.
Performing an on-demand backup
An on-demand backup is a user-initiated backup of Oracle data on a client. You can perform an on-
demand backup for the first backup of the client immediately after you install the Avamar client
Backup

software. Perform an on-demand backup before system maintenance, software installations, or
software upgrades.
Procedure
1. In the AUI navigation pane on the left, click , and then click Asset Management.
The Asset Management window is displayed.
2. In the domain tree, select the domain that contains the Oracle server.
A list of Avamar clients is displayed in the pane below the domains list.
3. In the list of clients, select the client that runs the Oracle server.
You can only view clients in the domain for the login account. To view all clients, log in to the
root domain.
4. Click BACKUP.
The Backup wizard is displayed. In the Plugin pane, a list of plug-ins that are installed on the
Oracle server is displayed.
5. In the Plugins pane, perform the following steps:
a. Select the Oracle RMAN plug-in for the platform.
b. Browse to and select one or more databases for the backup.
c. Click NEXT.
The Basic Configuration pane is displayed.
6. In the Basic Configuration pane, complete the following fields:
a. Select the backup retention policy settings:
l To automatically delete this backup from the Avamar server after a specific amount
of time, select Retention period. Specify the number of days, weeks, months, or
years for the retention period.
l To automatically delete this backup from the Avamar server on a specific calendar
date, select End date and browse to that date on the calendar.
l To keep this backup for as long as this client remains active in the Avamar server,
select No end date.
b. In the Avamar encryption method list, select the encryption method to use for data
transfer between the client and the Avamar server during the backup.
The encryption technology and bit strength for a client/server connection depends on
several factors, including the client operating system and Avamar server version. The
Avamar Product Security Guide provides additional information.
c. In the Optionally select a proxy to perform backup list, select the proxy.
The default setting is Automatic, which enables the Avamar server to choose the best
proxy for this operation.
d. Click NEXT.
The More Options window is displayed.
7. In the More Options pane, set the plug-in options:
a. To view advanced options, select Show Advanced Options.
b. Leave the Oracle Instance Name field blank. The Avamar Plug-in for Oracle determines
the Oracle instance name when you browse and select a target to back up.
Backup

c. (Optional) For Oracle 12c and later, if the Oracle user has SYSBACKUP privileges (instead
a. Type the username to use to authenticate the Oracle database. This is the user with
SYSDBA (or SYSBACKUP) privileges.
b. Type the password for the account.
c. Select the number of channels to allocate during the backup from the Number of
RMAN Channels list. The maximum number is 10.
Backup options on page 120 provides more information about the Number of RMAN
Channels option.
8. Select one or more backup options:
a. To back up the entire Oracle database, select Back up database.
b. To back up only the archive logs, select Back up archive logs. Archive backups are
always full backups no matter which backup level you choose.
c. To automatically delete archive logs after a successful database backup, select Delete
archive logs after backup
Note: The selection of multiple options is cumulative. To back up the entire database
and the archive logs, select Back up database and Back up archive logs.
d. (Linux and UNIX only) If the application bitness and operating system bitness are not the
same, select the appropriate setting from the Media Management Library Bitwidth list.
If the application bitness and operating system bitness are the same, leave the Media
Management Library Bitwidth set to Automatic, the default setting.
Note: The Management Library Bitwidth option does not apply to Windows
platforms.
e. To prevent a multiple target backup from continuing after one of the backups fails, select
Exit a multiple target backup when any one backup fails.
f. Type the number of files that RMAN can open concurrently per channel in the
Filesperset field. The default value is 1.
g. (Advanced option) Do not select the Enable debugging message option. This option is
for troubleshooting backup problems. When you select the Enable debugging messages
option, the Avamar Plug-in for Oracle creates large log files.
h. (Advanced option) Leave the NLS_DATE_FORMAT field blank.
i. (Advanced option) Select the appropriate option from the Enhanced Data
Deduplication list:
l To use the global enhanced data deduplication setting already set on the server,
select Default. This is the default setting.
l To back up the data files without using enhanced data deduplication, select Disabled.
l To use enhanced data deduplication for the backup, select Enabled.
9. Select a backup level:
l Full backup backs up all the data in the database data files when you select the Back up
database option.
l Level 0 backup backs up all data files.
Perform a level 0 backup before you perform a level 1 (differential or cumulative) backup.
Backup

l Level 1 differential backup backs up only changed blocks of the database.
l Level 1 cumulative backup backs up all database blocks that have changed since the
most recent level 0 backup.
Note: The Avamar Plug-in for Oracle supports incremental (level 0 and level 1) backups
for Oracle 11g and later. To improve level 1 (differential or cumulative) backup
performance, enable the Block Change Tracking feature. Enabling Block Change
Tracking on page 72 provides more information.
10. (Optional) If you use a recovery catalog, select the Use recovery catalog check box, and
then complete the following steps:
a. In the Recovery Catalog Server Name field, type the recovery catalog service entry.
b. In the Recovery Catalog User Name field, type the recovery catalog username.
c. In the Recovery Catalog Password field, type the recovery catalog password.
Note: The Use recovery catalog option uses the values in the Recovery Catalog
Server Name, Recovery Catalog User Name, and Recovery Catalog Password fields
to form a recovery catalog server connection string for RMAN.
11. (Advanced option) Complete options in the Preprocessing Script group box:
a. In the Run user-defined script at beginning of backup field, type the name of a
preprocessing script.
The preprocessing script must be in the /avamar/etc/scripts directory on the
client.
b. To stop processing the script when the script returns a nonzero status code, select Exit
backup if script fails.
Preprocessing and postprocessing scripts and attributes on page 129 provides more
information about using scripts.
12. (Advanced option) Complete the Postprocessing Script options:
a. In the Run user-defined script at end of backup field, type the name of a
postprocessing script.
The postprocessing script must be in the /avamar/etc/scripts directory on the
client.
b. To exit the script with an exit code from the script rather than with the standard
avoracle exit code, select the Exit process with if script failure exitcode check box.
information about using scripts.
c. To store the backup on a Data Domain system instead of the Avamar server, select Store
backup on Data Domain system, and then select the Data Domain system from the list.
d. From the Encryption method to Data Domain system list, select the encryption
method to use for data transfer between the client and the Data Domain system during
the backup.
13. Click FINISH.
The following status message is displayed:
Backup initiated.
Backup

Scheduling backups
Scheduled backups run automatically to ensure that backups of the Oracle data occur on an
ongoing basis. You can schedule backups to run daily, weekly, or monthly. The scheduled backup
can include multiple clients or a single server.
About this task
You can schedule backups by using the Policy wizard to create a policy for a backup.
Perform the following steps within the Policy wizard. The Avamar Administration Guide provides
more information about groups, group policy, datasets, schedules, and retention settings.
Procedure
1. Assign members to the new backup policy.
2. Assign a dataset to the new backup policy.
To create a dataset, use the Policy wizard or select Settings > Dataset > Add.
3. Assign a schedule to the new backup policy.
To create a schedule, use the Policy wizard or select Settings > Schedule > Add.
4. Assign a retention policy to the new backup policy.
To create a retention policy, use the Policy wizard or select Settings > Retention > Add.
5. Enable scheduling for the backup policy.
Creating a dataset
A dataset specifies the data to include in a scheduled backup and the options to use for the
backup. Create at least one dataset for scheduled backups on a client or group of clients. Create
multiple datasets to segregate client data.
Procedure
1. In the AUI navigation pane on the left, click , and then click Settings.
The Setting pane is displayed.
2. Click the Dataset tab.
3. Click ADD.
The Create Dataset window is displayed.
4. In the Dataset Name field, type a name for the dataset.
The name can include alphanumeric characters (A-Z, a-z, 0–9) and the following special
characters: period (.), hyphen (-), and underscore (_). Do not use Unicode characters or
the following special characters: ` ~ ! @ # $ % ^ & * ( ) = + [ ] { } | / ; : ' " < > , ?
5. From the Plugins list, select the Oracle RMAN plug-in for the platform.
The Oracle RMAN plug-in options are displayed.
6. Click the Options tab, and then set the plug-in options:
b. Leave the Oracle Instance Name field blank.
The Avamar Plug-in for Oracle determines the Oracle instance name when you browse
and select a target to back up.
Backup

a. In the Username field, type the username to use to authenticate the Oracle database.
This feature is the user with SYSDBA (or SYSBACKUP) privileges.
b. In the Password field, type the password for the username account.
c. In the Number of RMAN Channels list, select the number of channels to allocate
during the backup. The maximum number is 10.
Backup options on page 120 provides more information about the Number of RMAN
Channels option.
d. Select one or more backup options:
l To back up the entire Oracle database, select Back up database.
l To back up only the archive logs, select Back up archive logs.
Archive backups are always full backups no matter what the backup level you choose.
l To automatically delete archive logs following a successful database backup, select
Delete archive logs after backup.
Note: The selection of multiple options is cumulative. To back up the entire database
and the archive logs, for example, select Back up database and Back up archive
logs.
e. (Linux and UNIX only) If the application bitness and operating system bitness are not the
same, select the appropriate setting from the Media Management Library Bitwidth list.
Management Library Bitwidth set to the Automatic, the default setting.
Note: The Media Management Library Bitwidth option does not apply to Windows
platforms.
f. (Optional) Select Exit a multiple target backup when any one backup fails to prevent
a multiple target backup from continuing after one of the backups fails.
g. In the Filesperset field, type the number of files that RMAN can open concurrently per
channel. The default value is 1.
h. Select a backup level from the Incremental Backup group box:
l Full backup backs up all the data in the database data files when you select the Back
up database option.
l Level 0 backup backs up all data files.
Perform a level 0 backup before you perform a level 1 (differential or cumulative)
backup.
l Level 1 differential backup backs up only changed blocks of the database.
l Level 1 cumulative backup backs up all database blocks that have changed since the
Note: The Avamar Plug-in for Oracle supports incremental (level 0 and level 1)
backups for Oracle 11g and later. To improve level 1 (differential or cumulative)
backup performance, enable the Block Change Tracking feature. Enabling
Block Change Tracking on page 72 provides more information.
i. (Optional) If you use a recovery catalog, select Use recovery catalog, and complete the
following fields:
Backup

l In the Recovery Catalog Server Name field, type the recovery catalog service entry.
l In the Recovery Catalog User Name field, type the recovery catalog username.
l In the Recovery Catalog Password field, type the recovery catalog password.
Note: If you select the Use recovery catalog option, the Recovery Catalog Server
Name, Recovery Catalog User Name, and Recovery Catalog Password settings
are used to specify a recovery catalog server connection string for RMAN.
j. To store the backup on a Data Domain system instead of the Avamar server, select Store
backup on Data Domain system, and then select the Data Domain system from the list.
Note: Plug-in Options on page 119 provides more information about the Avamar
Plug-in for Oracle plug-in options, including information about advanced options.
k. In the Encryption method to Data Domain system list, select the encryption method to
use for data transfer between the client and the Data Domain system during the backup.
7. Click the Source Data tab and set the following plug-in options:
a. In the File/Folder Path, type the file path.
b. Click ADD.
8. Click SUBMIT.
Creating a backup policy
A backup policy is a collection of Avamar clients that use the same dataset, schedule, and
retention settings to implement scheduled backups.
About this task
Member clients must all be in the same Avamar domain. When you create a backup policy, you
define the dataset, schedule, and retention settings that apply for scheduled backups. These
settings comprise the backup policy, which controls backup behavior for all members of the
backup policy unless you override these settings at the client level.
The Avamar Administration Guide provides information about creating and editing backup policies,
schedules, or retention settings.
Enabling a scheduled backup for a backup policy
Scheduled backups occur only for enabled backup policies. Backup policies are disabled by default
unless you select the Enabled check box on the first page of the New Policy wizard. If you did not
enable the backup policy when you created it, use the menu options in the Policy window to
enable backups.
Procedure
1. In the AUI navigation pane on the left, click , and then click Backup Policy.
The Policy page is displayed.
2. In the domain tree, select a domain or subdomain for the backup policy.
To select a subdomain for the backup policy, toggle the Include Sub-domain switch to on.
3. Select a backup policy from the list.
4. To enable a backup policy, click MORE ACTIONS > Enable Policy.
5. To disable a backup policy, click MORE ACTIONS > Disable Policy.
Backup

Monitoring backups
You can monitor and view status information for backup and restore operations by using the
Activity Monitor.
About this task
To access the Activity Monitor, open the navigation pane, and then click Activity. The Activity
Monitor appears with a list of all activities.
Note: The AUI Activity Monitor window has been optimized for at least 1366 pixels-wide
screens. Display issues might occur for smaller screens. To properly display the AUI, ensure
that your display is at least 1366 pixels wide.
The Activity Monitor provides you with options to filter the information that appears:
l Filter activities by duration—By default, the Activity Monitor displays the most recent 5,000
client activities. To select a different duration, in the Filter activities by duration drop-down
list, select Last 24 hours or Last 72 hours.
l Filter activities by domain—By default, the Activity Monitor displays all activities regardless
of domain. To display only the activities for a specific domain, in the Filter activities by
domain drop-down list, select a domain or subdomain.
l Filter activities by status—By default, the Activity Monitor displays all activities regardless of
status.
To display only activities with a specific status, at the top of the Activity Monitor, select one
of the following options:
n Canceled
n Completed
n Completed with Exceptions
n Failed
n Running
n Waiting
To filter activities by client, start time, plug-in, or type, click in their respective column.
The Activity Monitor displays the date and time that an activity began, and the total number of
bytes examined during an activity.
To view activity details, expand the Details pane, by clicking .
Cancel backups
You can cancel a backup any time before it completes. The cancellation might take 5 minutes or
longer. The backup might complete before the cancellation finishes.
Procedure
1. In the AUI navigation pane on the left, click , and then click Activity.
The Activity Monitor appears with a list of activities.
2. Select the backup from the list.
3. Click CANCEL.
A confirmation dialog box is displayed.
Backup

4. Click YES.
Oracle RAC backup failures
An Oracle RAC backup fails when the Oracle instance on the active node goes down or when a
node goes down. For each type of failure, you must restart the backup.
Restarting the backup after the active node’s instance goes down
Procedure
1. Establish the active node by taking the appropriate action:
l Restarting the instance on the active node.
l Shutting down the current active node to enable one of the other nodes as the active
node.
2. Start a new backup.
Restarting the backup after a node goes down
Procedure
l If the var directory is located on a shared file system, another node automatically takes over
as the active node. You can then restart the backup.
Note: In this scenario, EMCagent is configured as an Oracle Clusterware resource.
l If EMCagent is not configured as an Oracle Clusterware resource and the var directory is not
shared across all nodes:
a. Activate the Avamar agent on one of the available nodes.
b. Restart the backup.
Enforcement of backups to Data Domain
If the Avamar server is configured to enforce backups to a Data Domain system, the server rejects
backups that are not destined for the Data Domain. This enforcement covers backups that you
configure through the Avamar Administrator and the AUI, as well as from command-line interfaces
and other tools.
These backups must have additional flags that indicate the storage target. The Avamar and Data
Domain System Integration Guide provides more information about backup enforcement and the
related client version requirements. Backup enforcement is disabled by default.
Backup

Backup

CHAPTER 6
Restore and Recovery
l Preparing the database for recovery..................................................................................... 84
l Preparing the database for restore........................................................................................84
l Restore types........................................................................................................................86
l Restoring a database to the original client.............................................................................86
l Restoring a database to a different client..............................................................................90
l Monitor restores................................................................................................................... 93
l Cancel restores..................................................................................................................... 94
l Performing a disaster recovery............................................................................................. 94

Preparing the database for recovery
Before you can use Avamar Plug-in for Oracle to recover data blocks from the flash recovery area
or recover corrupt data blocks, you must configure the Oracle database.
Configuring Flashback Database recovery
Procedure
1. Set the database to ARCHIVELOG mode.
2. Enable the flash recovery area.
The Oracle documentation provides instructions.
3. (For RAC configurations only) Configure the flash recovery area in a clustered file system or
in ASM.
4. Start the database in mount state by using the STARTUP command with the MOUNT option.
After the restore completes successfully, Avamar issues the command to open the
database.
Configuring the database for corrupt block recovery
To configure the database for corrupt block recovery, set the DB_BLOCK_CHECKSUM initialization
parameter to TYPICAL for the Oracle database. This parameter setting enables RMAN to detect
both physical and logical corruption.
Preparing the database for restore
Before you restore an Oracle database, you must prepare the database depending on the types of
activities you plan to perform.
About this task
Procedure
1. (VCS clusters only) To restore the Oracle database to a Solaris VCS cluster, stop the
listener and other dependent processes. Otherwise, skip this step and go to step 3.
2. (Raw devices only) Before you restore datafiles on a raw device, back up the files in the
flash recovery area. Otherwise, skip this step and go to step 3.
Note: For configurations in which you store the database on a raw file structure, Oracle
recommends that you use a normal file system as the flash recovery area.
3. Ensure that ORACLE_SID is set correctly by typing the following command:
echo $ORACLE_SID
$ORACLE-SID must point to the correct system identifier to restore the Oracle database.
4. To restore an Oracle Real Application Clusters (RAC) database, complete the following
steps:
a. Shut down all database instances on all nodes by typing the following commands:

sqlplus “/ as sysdba”
shutdown immediate;
exit
b. Start an instance without mounting the database on the registered node by typing the
following commands:
startup nomount;
exit
c. Skip step 5 and go to step 6.
5. To restore a nonclustered Oracle database, close the database and start an instance without
mounting the database:
a. Connect to the database by typing the following command:
The command prompt changes to the SQL prompt.
b. Shut down the database by typing the following command:
shutdown immediate;
The following information is displayed in the command shell:
Database closed.
Database dismounted.
ORACLE instance shut down.
c. Start the database by typing the following command:
startup nomount;
Total System Global Area 171966464 bytes
Database mounted.
d. Disconnect from the database by typing the following command:
exit
Disconnected from Oracle Database 11g Enterprise Edition Release
11.1.0.7.0
6. Move the existing datafiles (*.dbf), control files (*.ctl), redo log files (*.log), archive
log files (*.arc), and autobackup files (*.bkp). The following commands move the
existing database files to a convenient location:
mkdir $ORACLE_HOME/oradata/DB_NAME.saved
mv $ORACLE_HOME/oradata/DB_NAME/*
$ORACLE_HOME/oradata/DB_NAME.saved
mkdir $ORACLE_HOME/flash_recovery_area/DB_NAME.saved

mv $ORACLE_HOME/flash_recovery_area/DB_NAME/*
$ORACLE_HOME/flash_recovery_area/DB_NAME.saved
where DB_NAME is the database name in uppercase.
Note: The Oracle files can be in the default location or in a nondefault location. The
default location of Oracle files varies depending on the version of Oracle. The previous
commands use the default values for the directories.
For Oracle 11g R2, type the following additional commands:
mkdir $ORACLE_HOME/flash_recovery_area/db_name.saved
mv $ORACLE_HOME/flash_recovery_area/db_name/*
$ORACLE_HOME/flash_recovery_area/db_name.saved
where db_name is the database name in lowercase.
Note: Starting with Oracle 11g R2, flash_recovery_area is referred to as
fast_recovery_area.
The following directories are the default directories of the datafiles (*.dbf), control files
(*.ctl), redo log files (*.log), archive log files (*.arc), and autobackup files (*.bkp):
l $ORACLE_HOME/oradata/DB_NAME
l $ORACLE_HOME/flash_recovery_area/DB_NAME
7. Restore the database to the $ORACLE_HOME/oradata/DB_NAME directory.
Note: If the Oracle directories have been deleted or do not exist, create the directory
structure before restoring the database.
Restore types
Avamar Administrator supports the restore of a database backup from one system to another
system or directory on the same system. The restore uses the same Oracle system identifier (SID)
and database identification number (DBID) of the original database for the restored database.
Note: To perform a restore to a different client, prepare the target system by completing the
instructions in Preparing the database for restore on page 84.
After preparing the database, you can restore database files to the original client or to a different
client.
Restoring a database to the original client
You can restore Oracle databases to the original directory on the original client.
Procedure
You cannot view clients outside the domain for the login account. To view all clients, log in
to the root domain.

3. From the list of clients, select the client that runs the Oracle server.
4. (Optional) To locate backups by date:
a. In the right pane, click VIEW MORE.
b. Click SEARCH.
c. In the From and To fields, specify the date range.
d. Click RETRIEVE.
e. In the list of backups, select a backup.
The list of backups for the date range is displayed.
5. Click the Restore tab.
The Restore wizard is displayed and the Destination Client pane is displayed on the right.
6. In the Destination Client pane, perform the following steps:
a. Select Restore to original client.
b. Click NEXT.
The Backup Content pane is displayed.
7. In the Backup Content pane, perform the following steps:
a. In the left pane, select the folder from the tree.
The Backup Content pane displays a list of databases within the backup.
b. In the right pane, select the databases that you want to restore.
c. Click NEXT.
The Destination Location pane is displayed.
8. In the Destination Location pane, perform the following steps:
a. Select Restore everything to its original location.
b. Click Next.
The More Options pane is displayed.
the Oracle instance name when you browse and select a database to restore.
a. In the User Name field, type the username to use to authenticate the Oracle
database. This is the user with SYSDBA (or SYSBACKUP) privileges.
b. In the Password field, type the password for the account.
c. (Linux and UNIX only) If the application bitness and operating system bitness are not
the same, select the appropriate setting from the Media Management Library
Bitwidth list.
Management Library Bitwidth set to the Automatic (default).
The Management Library Bitwidth option does not apply to Windows platforms.

d. In the Number of RMAN Channels list, select the number of channels to allocate
during the restore. The maximum number is 10.
d. (Optional) To prevent a multiple target restore from continuing after one of the restore
operations fails, select Exit a multiple target restore when any one restore fails .
e. (Advanced option) Do not select the Enable debugging message option. This option is
for troubleshooting restore problems. When you select the Enable debugging messages
f. (Advanced option) In the NLS_DATE_FORMAT field, type a timestamp format for the
target database.
g. In the Encryption method from Data Domain system list, select the encryption method
to use for data transfer between the Data Domain system and the client during the
restore.
h. (Advanced option) If you selected Corrupt blocks from the Recovery Type group box,
select Validate database.
The Validate database option is optional when you perform a corrupt block recovery.
The restore operation is slower when you use the Validate database option.
i. Select an option from the Recovery mode list for the selected recovery type.
Recovery modes and values on page 127 provides more information about the Recovery
mode options.
j. In the Recovery value field, type the SCN, log sequence number, or timestamp. This
value depends on the option you select from the Recovery mode list.
k. To open the database after the recovery finishes, select Open the database with
resetlogs after recovery.
This option is selected by default.
l. Clear the Open the database with resetlogs after recovery option. When you clear this
option, the restore operation does not open the database with resetlogs. You can apply
archive logs to recover the database to the most current point-in-time that is available.
10. Select a Recovery Type:
a. To recover the database to the present time or to a point-in-time in the past, select
Point-in-Time (PIT).
Do not select multiple databases for a point-in-time recovery. Select only one database
for the restore.
b. To recover data blocks from the flash recovery area, select Flashback Database (FRA).
Configure flash recovery area before you can use the Flashback Recovery (FRA)
recovery type. Configuring Flashback Database recovery on page 84 provides more
information.
c. (Advanced option) To restore corrupt blocks only, and not the entire database, select
Corrupt blocks.
To use the Corrupt blocks recovery option, you must set the DB_BLOCK_CHECKSUM
initialization parameter to TYPICAL for the Oracle database. The database must be in a
mounted or open state.
d. From the Encryption method from Data Domain system list, select the encryption
method to use for data transfer between the Data Domain system and the client during
the restore.

e. (Advanced option) If you selected Corrupt blocks from the Recovery Type group box,
11. Specify Point-in-Time/Flashback Recovery options: :
a. Select an option from the Recovery mode list for the selected recovery type.
mode options.
b. Specify the SCN, log sequence number, or timestamp in the Recovery value field. This
c. To open the database after the recovery finishes, select Open the database with
To disable this option, clear the Open the database with resetlogs after recovery
check box. When you clear this option, the restore operation does not open the database
with resetlogs. You can apply archive logs to recover the database to the most current
point-in-time that is available.
12. Specify Preprocessing Script options:
a. To run a user-defined script at the beginning of the restore, type the script name in the
Run user-defined script at beginning of restore field.
The script must be in the avamaretcscripts directory on the client.
b. To stop the script from processing when the script returns a nonzero status code, select
Exit restore if script fails.
information about using scripts and specifying attributes.
13. Specify Postprocessing Script options:
a. To run a user-defined script at the end of the restore, type the script name in the Run
user-defined script at end of restore field.
b. To exit the script when it fails with an exitcode from the script rather than an exitcode
from the Avamar Plug-in for Oracle, select Exit process with script failure exitcode.
14. Click NEXT.
The Summary pane is displayed.
15. Review the provided information, and then click FINISH.

Restoring a database to a different client
You can restore Oracle databases to a different client.
Before you begin
Before you restore the Oracle database, ensure that the following items on the target client match
the source client:
l ORACLE_HOME
l oradata
l flash_recovery_area pathnames
l Database SID
Prepare the target client by following the instructions in Preparing the database for restore on
page 84.
Procedure
You cannot view clients outside the domain for the login account. To view all clients, log in
to the root domain.
3. From the list of clients, select the client that runs the Oracle server.
4. (Optional) To locate backups by date:
a. In the right pane, click VIEW MORE.
b. Click SEARCH.
c. In the From and To fields, specify the date range.
d. Click RETRIEVE.
e. In the list of backups, select a backup.
The list of backups for the date range is displayed.
5. Click the Restore tab.
The Restore wizard is displayed and the Destination Client pane is displayed on the right.
6. In the Destination Client pane, perform the following steps:
a. Select Restore everything to a different client.
b. In the domain tree, select the domain for the client.
c. In the list of clients, select the destination client.
The client is displayed in the Destination Client field.
d. Click NEXT.
The Backup Content pane is displayed.
7. In the Backup Content pane, perform the following steps:
a. In the left pane, select the folder from the tree.

The Backup Content pane displays a list of databases within the backup.
b. In the right pane, select the databases that you want to restore.
c. Click NEXT.
The Destination Location pane is displayed.
8. In the Destination Location pane, perform the following steps:
a. Select Restore everything to a different location.
b. In the Restore Location field, type the file path of the target location where you want to
restore the data.
For example: E:/dbrestore_dir/
c. Click NEXT.
The More Options pane is displayed.
the Oracle instance name when you browse and select a database to restore.
a. In the User Name field, type the username to use to authenticate the Oracle
database. This is the user with SYSDBA (or SYSBACKUP) privileges.
b. In the Password field, type the password for the account.
c. (Linux and UNIX only) If the application bitness and operating system bitness are not
the same, select the appropriate setting from the Media Management Library
Bitwidth list.
Management Library Bitwidth set to the Automatic (default).
The Management Library Bitwidth option does not apply to Windows platforms.
d. In the Number of RMAN Channels list, select the number of channels to allocate
during the restore. The maximum number is 10.
d. (Optional) To prevent a multiple target restore from continuing after one of the restore
operations fails, select Exit a multiple target restore when any one restore fails .
e. (Advanced option) Do not select the Enable debugging message option. This option is
for troubleshooting restore problems. When you select the Enable debugging messages
f. (Advanced option) In the NLS_DATE_FORMAT field, type a timestamp format for the
target database.
g. In the Encryption method from Data Domain system list, select the encryption method
to use for data transfer between the Data Domain system and the client during the
restore.
h. (Advanced option) If you selected Corrupt blocks from the Recovery Type group box,

i. Select an option from the Recovery mode list for the selected recovery type.
mode options.
j. In the Recovery value field, type the SCN, log sequence number, or timestamp. This
k. To open the database after the recovery finishes, select Open the database with
l. Clear the Open the database with resetlogs after recovery option. When you clear this
option, the restore operation does not open the database with resetlogs. You can apply
archive logs to recover the database to the most current point-in-time that is available.
10. Select a Recovery Type:
a. To recover the database to the present time or to a point-in-time in the past, select
Point-in-Time (PIT).
Do not select multiple databases for a point-in-time recovery. Select only one database
for the restore.
b. To recover data blocks from the flash recovery area, select Flashback Database (FRA).
Configure flash recovery area before you can use the Flashback Recovery (FRA)
recovery type. Configuring Flashback Database recovery on page 84 provides more
information.
c. (Advanced option) To restore corrupt blocks only, and not the entire database, select
Corrupt blocks.
To use the Corrupt blocks recovery option, you must set the DB_BLOCK_CHECKSUM
initialization parameter to TYPICAL for the Oracle database. The database must be in a
mounted or open state.
d. From the Encryption method from Data Domain system list, select the encryption
method to use for data transfer between the Data Domain system and the client during
the restore.
e. (Advanced option) If you selected Corrupt blocks from the Recovery Type group box,
11. Specify Point-in-Time/Flashback Recovery options: :
a. Select an option from the Recovery mode list for the selected recovery type.
mode options.
b. Specify the SCN, log sequence number, or timestamp in the Recovery value field. This
c. To open the database after the recovery finishes, select Open the database with
To disable this option, clear the Open the database with resetlogs after recovery
check box. When you clear this option, the restore operation does not open the database

with resetlogs. You can apply archive logs to recover the database to the most current
point-in-time that is available.
12. Specify Preprocessing Script options:
a. To run a user-defined script at the beginning of the restore, type the script name in the
Run user-defined script at beginning of restore field.
b. To stop the script from processing when the script returns a nonzero status code, select
Exit restore if script fails.
13. Specify Postprocessing Script options:
a. To run a user-defined script at the end of the restore, type the script name in the Run
user-defined script at end of restore field.
b. To exit the script when it fails with an exitcode from the script rather than an exitcode
from the Avamar Plug-in for Oracle, select Exit process with script failure exitcode.
14. Click NEXT.
The Summary pane is displayed.
15. Review the provided information, and then click FINISH.
Monitor restores
You can monitor and view status information for backup and restore operations in the Activity
Monitor.
About this task
To access the Activity Monitor, open the navigation pane, and then click Activity. The Activity
Monitor appears with a list of all activities.
Note: The AUI Activity Monitor window has been optimized for at least 1366 pixels-wide
screens. Display issues might occur for smaller screens. To properly display the AUI, ensure
that your display is at least 1366 pixels wide.
The Activity Monitor provides you with options to filter the information that appears:
l Filter activities by duration—By default, the Activity Monitor displays the most recent 5,000
client activities. To select a different duration, in the Filter activities by duration drop-down
list, select Last 24 hours or Last 72 hours.
l Filter activities by domain—By default, the Activity Monitor displays all activities regardless
of domain. To display only the activities for a specific domain, in the Filter activities by
domain drop-down list, select a domain or subdomain.
l Filter activities by status—By default, the Activity Monitor displays all activities regardless of
status.

To display only activities with a specific status, at the top of the Activity Monitor, select one
of the following options:
n Canceled
n Completed
n Completed with Exceptions
n Failed
n Running
n Waiting
To filter activities by client, start time, plug-in, or type, click in their respective column.
The Activity Monitor displays the date and time that an activity began, and the total number of
bytes examined during an activity.
To view activity details, expand the Details pane, by clicking .
Cancel restores
You can cancel a restore any time before it completes. The cancellation might take 5 minutes or
longer. The restore might complete before the cancellation finishes.
Procedure
1. In the AUI navigation pane on the left, click , and then click Activity.
The Activity Monitor appears with a list of activities.
2. Select the restore from the list.
3. Click CANCEL.
A confirmation dialog box is displayed.
4. Click YES.
Performing a disaster recovery
With an effective data backup plan in place, you can successfully recover an Oracle server from a
complete loss.
Procedure
1. Replace hardware if required.
The hostname and IP address must be same as that of the original server.
2. Install the same version of the Avamar file system client and Avamar Plug-in for Oracle.
Installation on page 29 provides instructions.
3. Register and activate the client with the same Avamar server.
Note: To resolve registration problems, retire the client and reregister it with the
Avamar server.
The Avamar Administration Guide provides instructions for registering, retiring, and activating
clients.
4. Install the same version of the Oracle software that was previously installed.
5. Set up the Oracle database:

a. Ensure that you set the ORACLE_HOME to the same location as it was set to previously.
b. Create the Oracle database with the same SID name that was used previously.
Ensure that the ORACLE_SID, oradata, and flash_recovery_area pathnames are
exactly the same as in the previous configuration.
6. Start the database in the nomount mode by typing the following command:
startup nomount
7. Restore the server parameter file (spfile) by using the following RMAN script:
connect target "/";
set dbid=DBID;
run{
restore spfile to '/HOME/ORACLE/spfiletestdb.ora' from autobackup
MAXSEQ=SEQ
until time = "TO_DATE('DATE','YYYYMMDD')";
}
where:
l DBID is the database ID.
l /HOME/ORACLE is the path for the spfile file.
l SEQ is the highest sequence number for the control file autobackup search.
l DATE, YYYYMMDD is the backup date.
8. Restore the Oracle database by completing the steps in Restoring a database to a different
client on page 90.

CHAPTER 7
Backup and Restore with Oracle RMAN
l Preparing the system for RMAN backups and restores......................................................... 98
l Specifying RMAN parameters to improve performance........................................................101
l Backing up Oracle data with RMAN.....................................................................................105
l Restoring Oracle data with RMAN....................................................................................... 107
l Using advanced restore commands.......................................................................................111
l Managing backup retention.................................................................................................. 112
l Allocating multiple channels..................................................................................................116
l Managing RMAN backups and restores through Avamar Administrator................................117

Preparing the system for RMAN backups and restores
Before you use RMAN scripts to back up and restore Oracle data, you must prepare the system.
This preparation includes creating an avtar flag file, defining backup channels, and specifying
library path settings.
Before you begin
All RMAN backup and restore scripts in this chapter require an avtar flag file. When you use
RMAN to back up or restore Oracle data, you must pass specific avtar options by using the send
command. You include these avtar options in the avtar flag file, which is a text file.
With Avamar version 7.3 and greater, information about command line backups and restores for
Oracle appears in the Avamar Administrator activity window in the same way as when these
operations are started within the Administrator. This step requires some modifications in the
avtar flag file, and creation of a taskflag file.
Creating an avtar flag file
When you use RMAN to back up Oracle rather than Avamar Administrator, you must specify the
backup expiration time. Otherwise, backups that are stored on the Avamar server never expire.
Specify the backup expiration by including the --expires option for the avtar command in the
avtar flag file. The avtar process reads the avtar flag file during RMAN backups and restores.
About this task
Note: Do not include the avtar -c and -x options in the avtar flag file. The -c and -x options
might conflict with other avtar options that are specified for backup or restore operations
that Avamar Administrator runs.
Procedure
1. Create a plain text file with a text editor.
The remaining steps use my-avtar-flags.txt file as an example flag file.
2. Add the following entries to the text file:
--pidname=Oracle
--pidnum=pidnum
--logfile=install-dir/var/clientlogs/avtar.log
--vardir=install-dir/var/clientlogs
--id=user
--ap=password
--path=/clients/my-db-client
--expires={num-days |timestamp}
--server=Avamar_server_name
where:
l pidnum is the correct PID number for the operating system:
n For Linux, use PID 1002.
n For Solaris, use 2002.
n For Windows, use 3002.
n For HP-UX, use 4002.
n For AIX, use 5002.

l install-dir is the base installation directory for the platform. For example, specify /usr/
local/avamar on Linux, /opt/AVMRclnt on Solaris, C:Progra~1avsbin on
Windows, and so forth.
l user is an Avamar administrative user account.
l password is the Avamar administrative password.
l my-db-client is the Oracle database hostname.
l {num-days |timestamp} specifies backup expiration as the number of days from today
(num-days) or an absolute timestamp.
l Avamar_server_name is the Avamar server hostname.
3. To use an RMAN script to back up Oracle to Data Domain systems, add the following Data
Domain-specific entries:
--ddr=true
--ddr-index=ddr-index
where ddr-index is the index number (1, 2, 3, and so forth) that you assign to the Data
Domain system when you add it to the Avamar server configuration.
Note:
If the backup is not to a Data Domain System, then add the following entry:
--ddr=false
4. Save the file to /oracle or another convenient place in the search path.
Creating a taskflag file
With Avamar version 7.3 and greater, information about command line backups and restores for
Oracle appears in the Avamar Administrator activity window in the same way as when these
operations are started within the Administrator. This action requires the creation of a taskflag
file. The taskflag file must then be invoked by the RMAN script using the --taskfile
parameter.
Procedure
1. Create a plain text file with a text editor called taskflag.txt.
2. Add the following entries to the text file:
--no of channels=num
--operation=operation
where:
l num is the number of multiple channels that are run in parallel.
l operation is either backup or restore.
3. Save the file to /oracle or another convenient place in the search path.
Note: With a taskflag file, for most avtar processes the logfile name is generated
using the workorder ID from Management Console, and the --logfile parameter in
the avtar flag file is ignored.

Specifying the SBT_LIBRARY parameter
To use RMAN backup and restore scripts with the Avamar software requires you to define backup
channels by using the allocate channel command. The allocate channel command must
include a PARMS clause, which specifies the SBT_LIBRARY parameter.
Procedure
1. Set the SBT_LIBRARY parameter to point to the directory that contains the
libobk_avamar.so file for 32-bit installations or the libobk_avamar64.so file for 64-
bit installations:
SBT_LIBRARY=install-dir/lib/libobk_avamar.so
where install-dir is the base installation directory for the platform. For example,
specify /usr/local/avamar on Linux, /opt/AVMRclnt on Solaris, C:Progra~1avs
bin on Windows.
For 64-bit Oracle installations, use libobk_avamar64.so in place of
libobk_avamar.so. On Windows, the equivalent libraries are libobk_avamar64.dll
and libobk_avamar.dll.
2. Use the appropriate allocate channel command to define backup channels:
l For IBM AIX, type the following command:
allocate channel c1 type sbt
PARMS="SBT_LIBRARY=/usr/local/avamar/lib/libobk_avamar.so";
l For 64-bit HP-UX, type the following command
PARMS="SBT_LIBRARY=/opt/AVMRclnt/lib/libobk_avamar64.so";
Specifying the library path settings
When RMAN loads libobk_avamar.so or libobk_avamar64.so, the path to the RMAN-
dependent libraries must be communicated to the dynamic loader. The dynamic loader exits with a
failure when it is unable to locate the libraries that libobk_avamar.so or
libobk_avamar64.so requires. RMAN channel allocation fails.
About this task
Use an environment variable to specify the location of the libraries. Set the correct environment
variable before an Avamar backup or restore operation runs an RMAN script. The location and the
environment variable vary with each operating system. The following table lists the operating
systems and the environment variables.
Table 3 Environment variables for libobk
Operating system Environment variable
AIX LIBPATH
HP-UX SHLIB_PATH
Linux, Solaris LD_LIBRARY_PATH
The library path is typically install-dir/lib, where install-dir is the base installation directory
for the system. For example:
l On Linux, the path is /usr/local/avamar.

l On Solaris, the path is /opt/AVMRclnt.
l On Windows, the path is C:Progra~1avsbin.
Procedure
1. Use the set and export commands (for the sh, ksh, or bash shell) or the setenv
command (for the csh or bash shell) to set the library path variable.
2. Set the appropriate environment variable on the system. For example, to set the
LD_LIBRARY_PATH variable on Solaris, use one of the following methods depending on the
operating system shell:
l For the sh, ksh, or bash shell, type the following command:
set LD_LIBRARY_PATH=/opt/AVMRclnt/lib export LD_LIBRARY_PATH
l For the csh or bash shell, type the following command:
setenv LD_LIBRARY_PATH /opt/AVMRclnt/lib
Specifying the SECTION SIZE parameter for multisection backups
The SECTION SIZE parameter enables RMAN to create a multisection backup.
Procedure
l To set the SECTION SIZE parameter, add the following command to the RMAN backup
script:
backup section size sizespec database;
where sizespec specifies the size of each backup section. For example: 250M.
The following example command creates a multisection backup of the database where
each backup piece is 250M:
backup section size 250M database;
RMAN substitution variables %d and %U
You can use RMAN substitution variables %d and %U in an RMAN backup or restore script to
ensure that the name of each backup piece is a unique name.
The name of a backup piece can be any name, as long as each backup piece has a unique name on
the Avamar server.
l %d specifies the name of the database.
l %U specifies a unique Oracle system-generated file name.
Specify both the %d and %U together to obtain a unique name. For example: format '%d_%U'.
Specifying RMAN parameters to improve performance
To improve performance, you can set RMAN parameters, such as maxopenfiles and
filesperset, configure the database to skip certain file types, and use the --before and --
after flags.

Specifying the maxopenfiles parameter
The maxopenfile parameter specifies the number of files that RMAN can open concurrently per
channel.
Procedure
l To set the maxopenfiles parameter in an RMAN backup script, use the allocate
channel or configure channel command. The following example uses the allocate
channel command:
allocate channel c0 maxopenfiles = 1 device type sbt;
RMAN compares the value of the maxopenfiles parameter with the number of files in each
backup set and uses the level of multiplexing as a minimum of two.
Set the maxopenfiles parameter to 1 to disable multiplexing, which increases data
deduplication performance. Disabling RMAN multiplexing results in more time to back up
Oracle data because RMAN reads a single file instead of multiple files simultaneously.
Specifying the filesperset parameter
The filesperset parameter specifies the number of files that RMAN can include in each backup
set.
Procedure
l To set the filesperset parameter in an RMAN backup script, use the backup command.
The following example uses the backup database command:
backup filesperset = n database ...;
where n is the number of files RMAN includes in a backup set. The default value is 8.
Results
RMAN compares the value of the filesperset parameter with number of files to be backed up
divided by the number of allocated channels, and then uses the lower of the two values. For
example, if the total number of files to be backed up is 8, the number of channels is 1, and
filesperset is 4, RMAN creates two backup sets each with four files.
Enabling RMAN backup optimization
Backups that use RMAN backup optimization skip any file that has not changed and has already
been backed up to the allocated device type. A file can be a dbf file, an archived redo log, or an
RMAN backup set.
Procedure
l Set the CONFIGURE RETENTION POLICY option:
CONFIGURE RETENTION POLICY TO REDUNDANCY r
where r is the redundancy setting.
Results
RMAN skips backups of offline or read-only datafiles only when there are r +1 backups of the files
to SBT.

Setting backup optimization
To reduce backup time, enable the RMAN backup optimization feature.
Procedure
1. Open a command shell.
2. Log in to Oracle RMAN by using the Oracle user ID and password.
The command prompt changes to an RMAN prompt.
3. Connect to the Oracle database to back up.
4. Type the following command:
configure backup optimization on;
Guidelines for using RMAN backup optimization
About this task
The following guidelines apply to backups that use RMAN backup optimization:
Procedure
l Allocate only one type of channel. Do not mix disk and SBT channels in the same RMAN
backup command.
l Run the crosscheck command periodically to synchronize the RMAN backup catalog with
Avamar backups.
Running the crosscheck command also ensures that RMAN does not skip a backup that has
already expired in Avamar.
l Override RMAN backup optimization by specifying the force option with the RMAN backup
command.
The Oracle documents provide more information about the RMAN backup optimization feature.
Specifying before, after, and nobackuptag flags to increase index lookup speed
The Avamar Plug-in for Oracle uses the avtar --history command to perform index lookups.
This command can sometimes run slowly. To increase the index lookup speed, you can specify the
--before, --after, and --nobackuptag flags with the send command.
About this task
The Avamar Plug-in for Oracle runs the avtar --history command for each CLI backup and
for each backup a restore retrieves. When a backup or restore includes hundreds of backups, the
avtar --history command might take hours to run.
The avtar --history command supports two time-range CLI flags, as well as the --
nobackuptag flag:
l The --before flag instructs the avtar process to search only for backups that were created
before the time specified by the --before flag.
l The --after flag instructs the avtar process to search only for backups that were created
after the time specified by the --after flag.
l The --nobackuptag flag can improve performance because the Avamar Plug-in for Oracle
library, libobk_avamar.x, automatically sets the --backuptag flag to search backups.
This may cause slow restore performance due to avtar --history failing and retrying. The
--nobackuptag flag can be used to avoid failing history searches.

The Avamar Plug-in for Oracle library, libobk_avamar.x, enables you to set the --before, --
after, and --nobackuptag flags for operations that perform an index lookup. The
libobk_avamar.x uses these flags to increase index lookup performance.
Procedure
l Do not set the --before or --after flags for backups. The libobk_avamar.x
automatically sets these flags to the backup start time, which enables the backup index lookup
to search only for backups that are created after the backup began.
l Set the --before, --after, or --nobackuptag flags for restores with the send command
in an RMAN script. The following RMAN script shows how to set these flags:
connect target user/password@SID;
run {
PARMS="SBT_LIBRARY=install-dir/lib/libobk_avamar.so";
send '"--after=2014-11-07 00:30:00" "--before=2014-11-11 01:00:00"
"--bindir=install-dir/avamar/bin" "--flagfile=my-avtar-flags.txt" "--
taskfile=/oracle/taskfile.txt" "--nobackuptag"';
restore datafile 4;
release channel c1;
Use the following time format for the --before and --after flags:
YYYY-MM-DD HH:MM:SS
Note: The smaller the time range between the --before and --after flags, the faster
the searches.
l In addition to the --before and --after flags, use the --nohist flag to disable all index
lookups for all operations. Set the --nohist flag with the send command in an RMAN script:
send '"--nohist" "--bindir=install-dir/avamar/bin"
"--flagfile=my-avtar-flags.txt"';
The --nohist flag does not require a value.
l Use the –noduplicatecheck flag, to disable index lookups only for backups to disable
duplicate name checks. Set the --noduplicatecheck flag with the send command in an
RMAN script:
send '"--noduplicatecheck" "--bindir=install-dir/avamar/bin" "--flagfile=my-
avtar-flags.txt"'
The --noduplicatecheck flag does not require a value and is only relevant for backups
that are performed from RMAN CLI without a taskfile. Because use of the --
noduplicatecheck flag disables the check for duplicate names in the Avamar server, best
practices are to name backup pieces in the RMAN script, for example: %d_%U, to that ensure
that each backup piece is unique.
Results
When a backup or restore specifies all four flags, the --nohist flag takes precedence. The --
before and --after flags are ignored.

Backing up Oracle data with RMAN
You can use RMAN scripts to back up an Oracle database, a tablespace, or a single datafile. You
can specify an Avamar server or a Data Domain system as the target system for RMAN backup
scripts.
Before you begin
All RMAN backup scripts in the following topics require an avtar flag file. Creating an avtar flag
file on page 98 provides more information.
About this task
All Windows paths that you specify with the RMAN send command must use the 8.3 format.
Note: Avamar uses the RMAN interface to perform hot and cold backups. RMAN requires the
Oracle database to be running to perform a hot backup.
Backing up a database
Procedure
Note: To back up the database by using a database control file instead of a recovery
catalog, start RMAN by using the nocatalog option.
4. Back up the Oracle database by typing RMAN commands similar to the following commands:
run {
PARMS="SBT_LIBRARY=install-dir/lib/libobk_avamar.so"
format '%d_%U';
set controlfile autobackup format for device type sbt
to "CONTROLFILE.%F";
send '"--flagfile=/oracle/my-avtar-flags.txt"
"--bindir=install-dir/bin"' "--taskfile=/oracle/taskfile.txt";
backup database plus archivelog;
release channel c1;
}
bin on Windows.
Backing up a tablespace
About this task
The following procedure uses an RMAN script to back up a tablespace to an Avamar server or a
Data Domain system.

An avtar flag file for the RMAN script that is specified in this procedure contains the following
entries:
--debug
--pidname=Oracle
--pidnum=3002
--logfile=install-dir/var/clientlogs/backupdb.log
--vardir=install-dir/var
--id=testuser@/clients/oraw2k864-mc2.bgl-avamar.emc
--password=testuser
--path=/clients/oraw2k864-mc2.bgl-avamar.emc
--server=avamar-1.emc.com
Note: To view the contents of a tablespace backup, use the list backup command. The
list backup command lists all the datafiles and the control file that are part of the
tablespace backup.
Procedure
4. Back up the Oracle tablespace by typing commands similar to the following RMAN
commands:
run {
set controlfile autobackup format for device type sbt to
'CONTROLFILE.ANT.%F';
PARMS="SBT_LIBRARY=c:PROGRA~1avsbinorasbt64.dll"
format '%d_%U';
send '"--prefix=11g/ANT/"
"--flagfile=c:rmanavtar-flags.txt"
"--taskfile=c:rmantaskfile.txt"
"--bindir=c:PROGRA~1avsbin"';
backup tablespace ant_ts;
release channel c0;
}
In the sample script, the database name is ANT and the tablespace name is ant_ts. The
script backs up the tablespace and the database control file by using the autobackup
option.
Backing up a datafile
Procedure

4. Back up the Oracle datafile by typing RMAN commands similar to the following commands:
run {
format '%d_%U';
"--taskfile=/oracle/taskfile.txt"
"--bindir=install-dir/bin"';
backup datafile "MyFile.dbf";
release channel c1;
}
where:
local/avamar on Linux,/opt/AVMRclnt on Solaris, C:Progra~1avsbin on
l MyFile.dbf is the Oracle datafile to back up.
Restoring Oracle data with RMAN
You can use RMAN scripts to restore an Oracle database, a tablespace, or a single datafile.
Before you begin
All RMAN backup scripts in the following topics require an avtar flag file. Creating an avtar flag
About this task
The Oracle database that you select to restore must be offline.
Note: RMAN command line backups can only be restored through command line restores.
Restore of command line backups from the Avamar Administrator are not supported.
Restoring a database
To restore a database backup, you must specify a value from the control file name. Backups you
perform from RMAN use the format, c.DBID-DATE-SEQ, for the control file name. Backups you
perform with Avamar Administrator add a prefix to the control file name.
About this task
You can modify the default RMAN format of the control file by passing directives to RMAN scripts.
Avamar Administrator generates scripts that contain the RMAN directive, %F:
The %F directive combines the DBID, date, and sequence to form the following control file name:
CONTROLFILE.c.DBID-DATE-SEQ
The sample scripts in this guide assume this format for the control file name.
The control file name contains a prefix when you use a backup that you created with Avamar
Administrator for the restore. You must then add the prefix to the send command. The prefix

must be the first directive. The following send command specifies “11g/orcl” as the prefix for an
Oracle 11g database with a SID of orcl:
send '"--prefix=11g/orcl/" "--flagfile=/oracle/my-avtar-flags.txt"
"--taskfile=/oracle/taskfile.txt" "--bindir=install-dir/bin"';
The path that you specify by the --prefix option must contain a trailing slash (/). The direction
of the slash does not change on Windows platforms.
The following procedure uses an RMAN script to restore an Oracle control file and database.
Procedure
3. Connect to the Oracle database to restore.
4. List all available backups by typing the list backup command:
list backup;
5. From the backup to be restored, retrieve the following information from the control file:
a. Examine the database backup control file name.
b. Note the values for the following variables:
l DATE
l DBID
l SEQ
Use the values of the DATE, DBID, and SEQ variables in the RMAN restore script.
6. Restore the Oracle control file by typing the following RMAN commands:
set dbid=DBID;
set controlfile autobackup format for device type sbt to
'CONTROLFILE.%F';
run {
format '%d_%U';
restore controlfile from autobackup MAXSEQ=SEQ
until time = "TO_DATE('DATE','YYYYMMDD')";
startup mount;
release channel c1;
list backup;
}
where:
l DBID is the database ID.
Windows.

l YYYYMMDD is a date.
The restore process copies the control file and puts the database in a mount state. A list of
available database backups and corresponding system change numbers (SCN) appears in
the command shell
7. Locate and note the SCN that corresponds to the backup to use for the recover process:
l To recover an archive log backup, locate and note the next SCN for the archive log.
l To recover from a database backup, locate and note the SCN for the database.
Note: In general, database control files are small and it is highly recommended a single
channel is used for restoring the control file for achieving better performance.
8. Log out of the RMAN session by typing the following command:
exit
11. Restore the Oracle database by typing the following RMAN commands:
run {
allocate channel c1 type sbt PARMS="SBT_LIBRARY=install-dir
/lib/libobk_avamar.so" format '%d_%U';
set until scn scn;
restore database;
recover database;
release channel c1;
}
alter database open resetlogs;
where:
l scn is the next SCN value (noted in step 7) for the archive log recovery or the SCN value
for the database.
Windows.
Note: If the restore process fails, you might need to perform manual recovery steps.
ORA-19870: error while restoring backup piece on page 141 provides more information.
Restoring a tablespace
You can use an RMAN script to restore a tablespace from an Avamar server or a Data Domain
system.
Procedure

4. Restore the Oracle tablespace by typing the following RMAN commands:
run {
format '%d_%U';
restore tablespace "USERS";
recover tablespace "USERS";
release channel c1;
}
where:
l USERS is the tablespace to restore.
Restoring datafiles
Procedure
4. Restore the Oracle datafile by typing the following RMAN commands:
run {
format '%d_%U';
"--bindir=install-dir/bin" "--labelnum=num"';
restore datafile "MyFile.dbf";
recover datafile "MyFile.dbf";
release channel c1;
}
where:

Windows.
l num is the backup number from which you want to restore.
l MyFile.dbf is the Oracle datafile you want to restore.
Using advanced restore commands
You can restore a database by using the recovery catalog. Restore the database to the original
location or to a different client system.
Before you begin
All RMAN restore scripts in the following topics require an avtar flag file. Creating an avtar flag
Using the catalog for backup and restores
Before you begin
To use a catalog for restore, add the connect catalog string after the connect target string. For
example, you can specify the following commands:
connect target user/password@mydb;
connect catalog catuser/catpassword@catalog;
Procedure
3. Restore the Oracle database by typing the following RMAN commands:
Connect catalog user/passwd@CATALOG;
run {
format '%d_%U';
restore database;
recover database;
release channel c1;
}
where:
l user and passwd are the credentials for the recovery catalog (CATALOG).

Performing a redirected restore
You can use RMAN to restore Oracle to a different client system. This type of restore is known as
a directed restore.
Before you begin
The system environment must meet the following requirements to restore Oracle to a different
client system:
l Both the source and target platforms must be similar types with the same configuration.
l The version of RMAN on the target platform must be compatible with the version of RMAN
that was used to create the backup.
Procedure
2. On the target system, create an avtar flag file.
This file is the same as the one described in Creating an avtar flag file on page 98, except for
the --id, --ap, and --path entries, which refer to the original client system (where the
backup was originally performed), not the target system.
3. Save the changes.
5. Create an empty database on the target system with the same SID as the original database.
6. Shut down the database and delete all control files, datafiles, logs, and FRA contents
corresponding to the database.
7. Restart the database with the nomount option.
8. Restore the database by using the flag file. Restoring a database on page 107 provides
instructions.
Managing backup retention
RMAN supports two types of retention policies: recovery window and redundancy.
About this task
The recovery window policy specifies a period of time that begins with the current time and
extends backward in time to the point of recoverability. For example, a recovery window policy can
be seven days. The redundancy policy specifies the number of backups that are kept for the
database. The default retention policy keeps one backup.
As backups accumulate, older backups become obsolete according to the retention policy. RMAN
uses crosscheck and delete operations to manage backups that are stored on the Avamar
server:
l Crosscheck operations verify that backups on the Avamar server exist. Crosscheck operations
also work for backups that are created by Avamar Administrator.

l Delete operations remove expired backups from the Avamar server if the backups are marked
as obsolete. Delete operations do not work for backups that are created by Avamar
Administrator.
Configuring retention policies
To use the crosscheck command to verify backups performed by Avamar Administrator, you
must configure an Avamar retention policy and an RMAN retention policy.
Configuring an Avamar retention policy
Procedure
1. In Avamar Administrator, select Tools > Manage Retention Policies.
The Manage All Retention Policies window appears.
2. Click New.
The New Retention Policy dialog box appears.
3. Type a name in the Name field for the retention policy.
Do not use any of the following characters in the retention policy name: ~!@$^%(){}[]|,`;#
/:*?<>'"&.
4. To configure a basic retention policy, select the appropriate option from the Basic
Retention Policy group box:
l To automatically delete backups after a specific number of days, weeks, months, or
years, select Retention period and specify the number of days, weeks, months, or years.
l To automatically delete backups on a specific calendar date, select End date and browse
to that date on the calendar.
l To keep backups for as long as a client remains active, select No end date.
5. To configure advanced retention settings:
a. Select Override basic retention policy for scheduled backups.
b. Click Advanced.
The Edit Advanced Retention Policy dialog box appears.
c. Specify the maximum number of daily, weekly, monthly, and yearly backups to retain.
d. Click OK.
The Edit Advanced Retention Policy dialog box closes.
6. Click OK.
The new retention policy appears in the Manage All Retention Policies dialog box.
Configuring an RMAN retention policy
Procedure
3. Connect to the Oracle database.

4. Create a retention policy by using the appropriate command. The following commands are
examples:
CONFIGURE RETENTION POLICY TO REDUNDANCY 2;
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 3 DAYS;
Ensure that the RMAN retention period and the Avamar retention policy are as close as
possible to the same length of time.
Crosschecking backups
The crosscheck command verifies that backups on the Avamar server exist. RMAN marks the
backup as available or expired upon successful completion of this command. When the
crosscheck command is unable to connect to the Avamar server, the operation fails.
About this task
When you back up a database from Avamar Administrator, the Avamar Plug-in for Oracle adds a
prefix to the name of the backup file. To crosscheck this type of a backup, ensure that you add the
prefix to the avtar flag file. The prefix that you specify by the avtar flag file must match the
prefix of the Avamar Administrator backup.
Note: The --taskflag option is not supported when crosschecking backups.
Procedure
The command prompt changes to and RMAN prompt.
4. Verify a backup by typing the following RMAN commands:
allocate channel for maintenance type sbt
PARMS="SBT_LIBRARY=install-dir/lib/libobk_avamar.so";
"--bindir=/usr/local/avamar/bin"';
crosscheck backup device type sbt;
bin on Windows, and so forth.
Deleting backups
To delete backups, the Avamar user account must have the delete privilege. This user account is
the account that corresponds to the --id value in the avtar flag file. When you run the delete
command from an account that does not have the delete privilege, the avtar program issues a
warning, not an error.
Before you begin
Note: The --taskflag option is not supported when crosschecking backups.
The following procedure requires an avtar flag file. Creating an avtar flag file on page 98 provides
more information.
About this task
To add the delete privilege to the Avamar user account, use the avmgr command:

avmgr chgv --u=name --pv=delete
where name is the name of the user account.
Note: The delete command deletes expired backups from the Avamar server if the backups
are marked as obsolete. Use the delete command only to manage RMAN backups. The use of
the delete command to manage backups that are originally created by Avamar Administrator
can cause unpredictable system behavior.
Procedure
4. Delete an expired backup by typing the following RMAN commands:
run {
PARMS="SBT_LIBRARY=/install-dir/lib/libobk_avamar.so";
"--bindir=/usr/local/avamar/bin"';
delete expired backupset;
}
bin on Windows, and so forth.
Mixing RMAN and Avamar Administrator backups
Do not back up Oracle by using both RMAN and Avamar Administrator. You can, however, recover
backups you create with Avamar Administrator by using RMAN.
Synchronizing the RMAN catalog
You can synchronize the RMAN catalog by using the report obsolete command or the
crosscheck command.
About this task
To keep the RMAN catalog synchronized with the Avamar server, use either of the following
methods.
Procedure
l Use the report obsolete command followed by the delete obsolete command.
RMAN determines which backups have fallen outside of the retention policy, and then deletes
them from its catalog and the Avamar server.
l Use the crosscheck command followed by the delete expired command.
RMAN determines which backups are available on the Avamar server, and then updates its
catalog accordingly.

Allocating multiple channels
An RMAN backup script that specifies multiple channels runs multiple instances of the avtar
program in parallel. The maximum number of channels is 10.
About this task
To avoid cache file collisions, specify a separate cache file for each channel including cases where
you only use one channel. The cacheprefix directive determines the name of the cache file. Use
a separate set of cache files for each database.
You might lock out processes by allocating too many channels, which can result in a time-out error.
If a time-out error occurs, retry the operation by using fewer channels.
Create an RMAN script to use multiple channels.
Procedure
1. Disable the file cache by adding the following entry to the avtar flag file:
--enable-filecache=false
2. Create an RMAN script that includes allocate channel commands similar to the
following commands:
PARMS="SBT_LIBRARY=/usr/local/avamar/lib/libobk_avamar64.so"
format '%d_%U';
format '%d_%U';
format '%d_%U'
3. Repeat the allocate channel command to allocate more channels, if required.
4. Add a send command to the RMAN script for each channel. For example, the following
send commands correspond to the channels specified in step 2.
send channel='c0' '"--flagfile=/oracle/my-avtar-flags.txt"
"--bindir=install-dir/bin" "--cacheprefix=orcl-c0"';
The script specifies a cacheprefix directive for each channel. If the send command is
split into multiple instances, specify the cacheprefix directive only once for each channel.
5. Before running an RMAN script that allocates multiple channels, ensure that the user
account has permissions to create files in the install-dir/var directory or the cache
files exists and has the correct permissions.

Managing RMAN backups and restores through Avamar
Administrator
To enable Avamar Administrator to monitor or cancel a backup or restore with RMAN, you must
create a taskfile and modify the sent statements in the RMAN script.
About this task
Follow the required steps to enable Avamar Administrator to monitor or cancel a backup or restore
with RMAN.
Procedure
1. Create a text file called a taskfile with the following entries:
--no_of_channels=<number of channels to be used in current operation>
--operation={backup | restore}
An example of a taskfile is as follows:
--no_of_channels=2
--operation=backup
2. Modify the send statements in the RMAN script by adding a taskfile parameter.
For example:
send channel='c1' '"--prefix=11g/MAYONE/" "--cacheprefix=MAYONE1" "--
bindir=/usr/local/avamar/bin" "--taskfile=/software/taskflag.txt" "--
flagfile=/software/my_avtar_flags.txt"';
allocate channel c2 type sbt PARMS="SBT_LIBRARY=/usr/local/avamar/lib/
libobk_avamar64.so" format '%d_%U';
3. Run the RMAN script according to the appropriate instructions in this chapter.
4. Locate the new entry for the current RMAN operation in the Activity window in Avamar
Administrator.

APPENDIX A
Plug-in Options
This appendix includes the following topics:
l How to set plug-in options................................................................................................... 120
l Backup options.................................................................................................................... 120
l Restore options....................................................................................................................125
l Preprocessing and postprocessing scripts and attributes.................................................... 129

How to set plug-in options
Plug-in options enable you to control specific actions for on-demand backups, restores, and
scheduled backups. The plug-in options that are available depend on the operation type and client
plug-in type.
Specify plug-in options in Avamar Administrator for on-demand backup or restore operations, or
when you create a dataset for a scheduled backup. Set plug-in options with the graphical user
interface (GUI) controls (text boxes, checkboxes, and radio buttons, and so forth). In addition to
using the GUI controls for the options, you can type an option and its value in the Enter Attribute
and Enter Attribute Value fields.
NOTICE The Avamar software does not check or validate the information that is typed in the
Show Free Form section of the More Options pane. The values in the Key and Value fields
override settings that are specified with the GUI controls for the options.
Detailed instructions on how to access and set plug-in options during a backup or restore are
available in Backup on page 71 and Restore and Recovery on page 83.
Backup options
Backup plug-in options enable you to control backup functionality that is specific to the Avamar
Plug-in for Oracle. You can specify plug-in options for on-demand and scheduled backups.
The following table lists options that are available for the Avamar Plug-in for Oracle when you
perform an on-demand backup or when you configure dataset for scheduled backups.
Table 4 Backup plug-in options
Option Description
Oracle Instance Name Leave this field blank. The Avamar Plug-in for Oracle
determines the Oracle instance name when you browse
and select a target to back up.
Username Specifies the username that is used to authenticate the
Oracle database. Username and password comprise a
connection string to Oracle. The connection string must
specify a user that has backup privileges for the
database.
If left blank, RMAN tries to log in with the same
username and password that the Avamar client agent
uses and attempts to assume SYSDBA (or SYSBACKUP)
privileges.
Typically, this field should contain the special account
name (backupuser). Creating the Oracle user account on
page 72 provides more information.
Password Specifies the password for the username account.
Number of RMAN Channels Specifies the number of channels to allocate during a
backup or restore. The maximum number is 10. The
default is 1. This option impacts the number of streams
that Data Domain systems use. The formula that
determines the number of streams is:
Plug-in Options

Table 4 Backup plug-in options (continued)
Option Description
NUMBER OF RMAN CHANNELS x NUMBER OF DATA
DOMAIN STREAMS.
Note: The number of Data Domain streams is set
when you add a Data Domain system to the Avamar
configuration.
Note: Allocating multiple channels for backups and
restores can improve performance. Performance
improvements for backups and restores, however,
depend on the Oracle server configuration.
In some instances, allocating too many channels can lock
out processes, which can result in a time-out error. This
problem does not occur when using RMAN scripts.
Back up database Backs up the Oracle database. You can use this option by
itself or with the Backup archive logs option.
Back up archive logs Backs up Oracle archive logs. You can use this option by
itself or with the Back up database option.
Note: The backup process does not use Incremental
Backup options if you select only the Back up
archive logs option.
Delete archive logs after backup Automatically deletes Oracle archive logs after a
successful database backup.
Media Management Library Bitwidth Specifies Media Management Library (MML) bitwidth.
Select an option:
l Automatic (default)
l 32-bit
l 64-bit
If the application bitness and OS bitness are not the
same, select the appropriate setting from the Media
Management Library Bitwidth list. If the application
bitness and OS bitness are the same, leave the Media
Management Library Bitwidth set to Automatic.
Note: The Media Management Library Bitwidth
option is available for Linux and UNIX Oracle RMAN
plug-ins. This option does not apply to Windows
platforms.
Exit a multiple target backup when any one backup fails Prevents a multiple target backup from continuing after
one of the backups fails.
Enable debugging messages (advanced option) Writes maximum information to log files. Use with
caution.
NLS_DATE_FORMAT (advanced option) Specifies a valid timestamp format for the target
machine. For example: mm/dd/yyyy.
Enhanced Data Deduplication (advanced option) Enables or disables data compression. During backups,
enhanced data deduplication can reduce the amount of
Plug-in Options

Option Description
client data that is sent to the server, but might require
additional client CPU resources. Select an option:
l To back up the data files without using compression,
select Default.
l To use the global data compression setting that is
already set on the server, select Default. This is the
default setting.
l To use enhanced data deduplication for the backup,
select Enabled.
Full backup Backs up all data files. You can optionally choose to
backup the archive logs during a Level 0 (incremental)
backup or at a later time. Full backups do not use the
Block Change Tracking option. This option is the
default.
Level 0 backup Performs a level 0 backup. Level 0 backups back up all
data files. You must perform a level 0 backup before you
perform a level 1 backup.
Level 1 differential backup Backs up all database blocks that have changed since the
most recent level 1 or level 0 backup. You must perform a
level 0 backup before you perform a level 1 backup.
Selecting the Level 1 backup option before you create a
level 0 backup results in a level 0 backup.
Level 1 cumulative backup Backs up all database blocks that have changed since the
Use recovery catalog Select this option to use the values in the Recovery
Catalog Server Name, Recovery Catalog Username,
and Recovery Catalog Password fields to form a
recovery catalog server connection string for RMAN.
Using a recovery catalog server enables you to use
specialized features of RMAN. A thorough discussion of
these features is beyond the scope of this guide. The
Oracle documentation provides more information.
Recovery Catalog Server Name Specifies the recovery catalog server name.
Recovery Catalog Username Specifies the recovery catalog username.
Recovery Catalog Password Specifies the recovery catalog password.
Run user-defined script at beginning of backup
(advanced option)
Specifies the name of a script that runs at the beginning
of the backup. The preprocessing script must be in the /
avamar/etc/scripts directory on the client.
Exit backup if script fails (advanced option) Stops processing the script when the script returns a
non-zero status code.
Run user-defined script at end of backup (advanced
option)
Specifies the name of a script that runs at the end the
backup. The postprocessing script must be in the /
Plug-in Options

Option Description
Exit process with script failure exitcode (advanced
option)
Exits the script with an exitcode from the script rather
than with the standard avoracle exitcode.
Filesperset Specifies the number of files that RMAN can include in
each backup set. The default is 1.
Store backup on Data Domain system Backs up the data to the Data Domain system rather
than to the Avamar server. Select the checkbox, and
then choose a Data Domain system from the list.
Encryption method to Data Domain system Specifies the encryption method for data transfer
between the client and the Data Domain system during
the backup.
Show Advanced Options Displays advanced options.
Specifying the channel_maxopenfiles option as normal text
The MAXOPENFILES parameter defines the number of files that RMAN can read and write
simultaneously in each backup piece per channel. You can specify RMAN parameters for backups
in Avamar Administrator by using avoracle flags in the avoracle.cmd file.
About this task
To modify the MAXOPENFILES value, specify the --channel_maxopenfiles flag in the
avoracle.cmd file:
--channel_maxopenfiles=value
Tune the MAXOPENFILES value appropriately for the databases and hardware configuration.
Specify the MAXOPENFILES value in the Backup Command Line Options dialog box.
Procedure
1. From the Backup Command Line Options dialog box, click More.
The dialog box expands to display the Enter Attribute and Enter Attribute Value fields.
2. Type the [avoracle]channel_maxopenfiles option in the Enter Attribute field.
3. Type the number of files in the Enter Attribute Value field.
4. Click +.
The option and value appear in the box below the + and - buttons.
The sbtio_trace_level option
The trace parameter in RMAN defines the logging level for sbtio logs. You can specify RMAN
parameters for backups and restore by using avoracle flags in the avoracle.cmd file or in the
Avamar Administrator via the Backup Command Line Options dialog box or the Restore
Command Line Options dialog box.
To modify the trace level, specify the --sbtio_trace_level option in the avoracle.cmd
file by using the format:
--sbtio_trace_level=value
Plug-in Options

The acceptable values for --sbtio_trace_level are 0 or any integer greater than 0. A 0
indicates minimal logging and reports only error conditions. Any value greater than 0 logs all
messages.
By default, the trace level is set to 2, which logs all messages. You can minimize logging by setting
--sbtio_trace_level to 0.
Specifying the sbtio_trace_level option in the Avamar Administrator.
To set the --sbtio_trace_level option in the Avamar Administrator:
Procedure
1. From the Backup Command Line Options dialog box or the Restore Command Line
Options dialog box, click More.
2. Type the [avoracle]channel_sbtio_trace_level option in the Enter Attribute field.
3. Type the trace level in the Enter Attribute Value field.
The acceptable values for the trace level are 0 or any integer greater than 0. A 0 indicates
minimal logging and reports only error conditions. Any value greater than 0 logs all
messages.
By default, the trace level is set to 2, which logs all messages. You can minimize logging by
setting --sbtio_trace_level to 0.
4. Click +.
The libobk_timeout option
The libobk_timeout parameter defines the timeout interval for communication between
avoracle and MML. You can specify RMAN parameters for backups and restore by using
avoracle flags in the avoracle.cmd file or in the Avamar Administrator via the Backup
Command Line Options dialog box or the Restore Command Line Options dialog box.
To modify the timeout, specify the --libobk_timeout flag in the avoracle.cmd file by using
the format:
--libobk_timeout=value
The libobk_timeout parameter accepts values in minutes. The acceptable values for --
libobk_timeout are between 1 and 35791. An input of 1 indicates timeout of 1 minute. If the
flag is not set or is set outside the range, a default input of 1 minute is set.
Specifying the libobk_timeout option in the Avamar Administrator
To set the --libobk_timeout option in the Avamar Administrator:
Procedure
1. From the Backup Command Line Options dialog box or the Restore Command Line
Options dialog box, click More.
2. Type the [avoracle]libobk_timeout option in the Enter Attribute field.
Plug-in Options

3. Type the value in minutes in the Enter Attribute Value field.
The acceptable values are 1 or any integer greater than 1. A 1 indicates a timeout of 1
minute. A value of 0 or negative integer will automatically set the timeout to 1 minute.
By default, the timeout is set to 1.
4. Click +.
Restore options
Restore plug-in options enable you to control restore functionality that is specific to the Avamar
Plug-in for Oracle. You set restore options from the Restore Command Line Options dialog box.
The following table lists options for restore operations with the Avamar Plug-in for Oracle.
Table 5 Restore plug-in options
Option Description
Oracle Instance Name Leave this field blank. The Avamar Plug-in for Oracle
determines the Oracle instance name when you browse
and select a target to restore.
Username Specifies the username that is used to authenticate the
Oracle database. Username and password comprise a
connection string to Oracle. The connection string must
specify a user that has backup privileges for the
database.
If left blank, RMAN tries to log in with the same
username and password that the Avamar client agent is
running under, and attempts to assume SYSDBA (or
SYSBACKUP) privileges.
Typically, this field should contain the special account
name (backupuser), Creating the Oracle user account on
page 72 provides more information.
Password Specifies the password for the username account.
Media Management Library Bitwidth Specifies Media Management Library (MML) bitwidth.
Choices are:
l Automatic (default)
l 32-bit
l 64-bit
If the application bitness and OS bitness are not the
same, select the appropriate setting from the Media
Management Library Bitwidth list. If the application
bitness and OS bitness are the same, leave the Media
Management Library Bitwidth set to the Automatic.
Note: The Media Management Library Bitwidth
option is available for Linux and UNIX Oracle RMAN
plug-ins. This option does not apply to Windows
platforms.
Plug-in Options

Table 5 Restore plug-in options (continued)
Option Description
Number of RMAN Channels Specifies the number of channels to allocate during a
backup or restore. The maximum number is 10. The
default is 1. This option impacts the number of streams
that Data Domain systems use. The formula that
determines the number of streams is: NUMBER OF
RMAN CHANNELS x NUMBER OF DATA DOMAIN
STREAMS.
Note: The number of Data Domain streams is set
when you add a Data Domain system to the Avamar
configuration.
Note: Allocating multiple channels for backups and
restores can improve performance. Performance
improvements for backups and restores, however,
depend on the Oracle server configuration.
In some instances, allocating too many channels might
lock out processes, which can result in a time-out error.
This problem does not occur when using RMAN scripts.
Exit a multiple target restore when any one restore fails Prevents a multiple target restore from continuing after
one of the backups fails.
Enable debugging messages (advanced option) Writes maximum information to log files. Use with
caution.
NLS_DATE_FORMAT (advanced option) Specifies a valid timestamp format for the target
machine. For example: mm/dd/yyyy.
Encryption method from Data Domain system Specifies the encryption method for data transfer
between the Data Domain system and the client during
the restore.
Point-in-Time (PIT) Enables a point-in-time recovery. Do not specify a point-
in-time option if you selected multiple databases for the
restore. Before using a point-in-time recovery option,
ensure that relevant backups are available on the Avamar
server. The recovery operation fails if a backup has
expired or has been deleted from the Avamar server.
Flashback Database (FRA) Enables a flashback restore.
Corrupt blocks (advanced option) Recovers corrupt blocks only, and not the entire
database. To use the Corrupt blocks only option, you
must set the DB_BLOCK_CHECKSUM initialization
parameter to TYPICAL for the Oracle database. The
database must be in a mounted or open state.
Validate database (advanced option) Validates the database only if the option is selected
during a corrupt blocks recovery
Recovery mode Lists recovery modes for the Point-in-Time (PIT) and
Flashback Database (FRA) recovery types. Select an
option from the Recovery mode list. Recovery modes
and values on page 127 provides more information.
Plug-in Options

Table 5 Restore plug-in options (continued)
Option Description
Recovery value Specifies the SCN, log sequence number, or timestamp,
depending on which recovery mode is selected.
Open the database with resetlogs after recovery Select this option to open the database after the
recovery. Clear this option to enable a roll-forward
operation to recover the database with archive log
transactions.
Run user-defined script at beginning of restore
(advanced option)
Specifies the name of a script that runs at the beginning
of the restore. The preprocessing script must be in the /
Exit restore if script fails (advanced option) Stops processing the script when the script returns a
non-zero status code.
Run user-defined script at end of restore (advanced
option)
Specifies the name of a script that runs at the end of the
restore. The postprocessing script must be in the /
Exit process with script failure exitcode (advanced
option)
Exits the script with an exitcode from the script rather
than with the standard avoracle exitcode.
Show Advanced Options Displays advanced options.
Recovery modes and values
The Point-in-Time (PIT) and Flashback Database (FRA) recovery types share recovery mode
options.
The following table describes the recovery mode options and shows the relation that each option
has to each recovery type.
Table 6 Recovery mode options
Recovery mode options Recovery value Point-in-Time (PIT) Flashback Database
(FRA)
Backup Time (PIT only) Recovers the database to
the most recent SCN. The
Avamar Plug-in for Oracle
automatically determines
the SCN from the control
file.
X
SCN Recovers the database to
the specified SCN:
l To recover an archive
log backup, type the
next SCN for the
archive log.
l To recover only from a
database backup, type
X X
Plug-in Options

Table 6 Recovery mode options (continued)
(FRA)
the SCN for the
database.
Type the SCN in the
Recovery value field.
Log Sequence Recovers the database to
the specified log sequence
number. Specify the log
sequence number in the
Recovery value field.
X X
Time Stamp Recovers the database to
the specified timestamp.
The timestamp format
must conform to the
localization settings on the
target host and locale
configuration setting for
the Oracle server.
X X
Restore Point Recovers the database to
the SCN associated with
the specified restore point.
The restore point can be an
ordinary restore point or a
guaranteed restore point.
X X
Before SCN (FRA only) Recovers the database to
its state just before the
specified SCN. Any
changes at an SCN lower
than the specified SCN are
applied. If there is a change
that is associated with the
specified SCN, it is not
applied.
X
Before Log Sequence (FRA
only)
Specifies a redo log
sequence number and
thread as an upper limit.
RMAN applies changes up
to (but not including) the
last change in the log with
the specified sequence and
thread number.
X
Before Resetlogs (FRA
only)
Recovers the database to
its state including all
changes up to the SCN of
the most recent OPEN
RESETLOGS.
X
Plug-in Options

Table 6 Recovery mode options (continued)
(FRA)
Before Time Stamp (FRA
only)
Recovers the database to
its state including all
changes up to but not
including changes at the
specified time.
X
Timestamp order of precedence rules
The timestamp order of precedence rules from highest to lowest are:
l Highest—A timestamp format that is specified by the NLS_DATE_FORMAT field (advanced
option).
l Lower—A timestamp format that is specified by the NLS_DATE_FORMAT variable in
environment settings.
l Lowest—The built-in default timestamp format uses american_america.us7asci.
The format is MM DD YYYY HH24:MI:SS:
l MM is a two-digit month.
l DD is a two-digit day of the month.
l YYYY is a four-digit year.
l HH24 is the hour using a 24-hour format.
l MI is minutes.
l SS is seconds.
Preprocessing and postprocessing scripts and attributes
Preprocessing and postprocessing scripts are user-written shell scripts that you can run from
Avamar Administrator when you perform backup and restore operations. Specify preprocessing or
postprocessing scripts and attributes in the Backup Command Line Options dialog box or the
Restore Command Line Options dialog box.
To specify preprocessing or postprocessing scripts, select Show Advanced Options in either of
the two dialog boxes.
1. From the Backup Command Line Options or Restore Command Line Options dialog box,
select Show Advanced Options.
2. Click More.
The Enter Attribute and Enter Attribute Value fields appear.
The following table describes the attributes that you specify in the Enter Attribute and Enter
Attributes Value fields.
Plug-in Options

Table 7 Preprocessing and postprocessing attributes
Attribute Description
run_at_start=script_name Specifies a script to run before a backup or restore
operation. The user interface includes the Run user-
defined script at beginning of backup and Run user-
defined script at beginning of restore fields for this
attribute.
run_at_start_clause=flags Specifies flags to use with the run_at_start script.
run_at_end=script_name Specifies a script to run after a backup or restore
operation. The user interface includes the Run user-
defined script at end of backup and Run user-defined
script at end of restore fields for this attribute.
run_at_end_clause=flags Specifies flags to use with the run_at_end script.
run_before_database=script_name Specifies a script to run before a database backup or
restore operation. When you specify multiple targets, the
script runs for each database operation.
run_before_database_clause=flags Specifies flags to use with the run_before_database
script.
run_after_database=script_name Specifies a script to run after a database backup or
restore operation. When you specify multiple targets, the
script runs for each database operation.
run_after_database_clause=flags Specifies flags to use with the run_after_database
script.
The following table describes flags that you specify for run_at_start_clause,
run_at_end_clause, run_before_database_clause, and
run_after_database_clause attributes.
Table 8 Attribute flags
Flag Description Usage Default value
desc Specifies a description
for the script.
desc=text string Type of script being
executed.
env Specifies an environment
variable to use.
env=variable_name=value None
exit_on_error Set to true to exit the
process if the
preprocessing or
postprocessing script
fails.
exit_on_error=true False
skip_on_error Set to true to skip the
next backup or restore
component. The
skip_on_error flag
clause is valid only with
the
skip_on_error=true False
Plug-in Options

Table 8 Attribute flags (continued)
run_before_databas
e attribute.
use_cscript
(Windows only)
Set to true to run the
script with Microsoft
cscript.exe.
use_cscript=true False
use_cscript_raw
(Windows only)
Set to true to run the
script with Microsoft
cscript.exe/nologo.
use_cscript_raw=true False
timeout_seconds Specifies the number of
seconds a script has to
complete before the
plug-in considers the
script as failed. The plug-
in then terminates the
script.
timeout_seconds=num 1 hour (60 * 60
seconds)
create_stdout_pipe Creates a stdout pipe
for the script and sends
output to the avoracle
log file.
create_stdout_pipe=true True
create_stderr_pipe Creates a stderr pipe
for the script and sends
output to the avoracle
log file.
create_stderr_pipe=true True
stringlist_args Set to false (default
value) to split the
specified argument’s
string into separate
arguments. Set to true
to use each argument’s
string as a separate
argument to the script.
Example of
stringlist_args=fa
lse:
[avoracle]run_at_s
tart=script.bat
First Second Third
The plug-in passes
First, Second, and
Third as three command
line parameters to
script.bat.
Example of
stringlist_args=tr
ue:
stringlist_args=true False
Plug-in Options

Table 8 Attribute flags (continued)
[avoracle]run_at_s
tart=script.bat
First Second Third
The plug-in considers the
script as a single file
name. The arguments are
not split. To pass
arguments the correct
way, use commas:
[avoracle]run_at_s
tart=script.bat,Fi
rst,Second,Third
Preprocessing and postprocessing usage examples
The following examples show how to specify preprocessing and postprocessing attributes in
Avamar Administrator.
Running a preprocessing script before the backup
The Run user-defined script at beginning of backup field specifies a script that runs before the
backup. Specifying a script in this field is equivalent to specifying a script with the run_at_start
attribute.
About this task
To pass flags to a preprocessing script requires you to type attributes and values in the Enter
Attribute and Enter Attribute Value fields. For example, the following procedure specifies
attributes and flags that provide a description for the preprocessing script and a time-out of 60
seconds.
Procedure
1. From the Backup Command Line Options dialog box, select Show Advanced Options.
2. Type the name of the script in the Run user-defined script at beginning of backup field.
This example uses Avamar.bat for the script:
Avamar.bat
3. Type the following text after the name of the script:
First Second
First and Second correspond to the attributes and flags you pass to the script.
The field now contains the following text:
Avamar.bat First Second
Note: To pass a third attribute and flag, you append Third to the text string.
4. Click More.
Plug-in Options

5. Type the run_at_start_clause attribute in the Enter Attribute field:
[avoracle]run_at_start_clause
You precede all attributes with [avoracle].
6. Type the desc flag and value in the Enter Attribute Value field:
desc=”Avamar Pre Script”
Enclose the text string in quotation marks.
7. Click +.
8. Type the run_at_start_clause attribute in the Enter Attribute field:
[avoracle]run_at_start_clause
9. Type the timeout_seconds flag and value in the Enter Attribute Value field:
timeout_seconds=60
10. Click +.
The run_at_start_clause attributes and flags appear in the box below the + and -
buttons.
Figure 10 Backup Command Line Options window
11. Clear the Exit backup if script fails option to enable the backup to proceed if the script
fails.
Plug-in Options

Running a postprocessing script after the backup
The Run user-defined script at end of backup field specifies a script that runs after the backup.
Specifying a script in this field is equivalent to specifying a script with the run_at_end attribute.
About this task
The instructions for running a run_at_end script are the same as Running a preprocessing script
before the backup on page 132.
Running a postprocessing script after each database backup
To run a postprocessing script after each backup requires you to type attributes and values in the
Enter Attribute and Enter Attribute Value fields. For this type of operation leave the Run user-
defined script at end of backup field blank.
About this task
This procedure adds attributes and flags that run the dbpostscript.bat script after a database
backup, sets the time-out to 200 seconds, specifies a description, and prevents the script’s output
from being written to the log file.
Procedure
1. From the Backup Command Line Options dialog box, select Show Advanced Options.
2. Click More.
3. Type the run_after_database attribute in the Enter Attribute field:
[avoracle]run_after_database
4. Type the script name, first, second, and third in the Enter Attribute Value field:
dbpostscript.bat first second third
5. Click +.
6. Type the run_after_database_clause attribute in the Enter Attribute field:
[avoracle]run_after_database_clause
7. Type the desc flag and value in the Enter Attribute Value field:
desc=”Avamar post script after database”
8. Click +.
10. Type the timeout_seconds flag and value in the Enter Attribute Value field:
timeout_seconds=200
11. Click +.
13. Type the create_stdout_pipe flag and value in the Enter Attribute Value field:
create_stdout_pipe=false
14. Click +.
Plug-in Options

The attributes and flags appear in the box below the + and - buttons.
Figure 11 Backup Command Line Options window
Note: You do not need to specify the exit_on_error flag, because it is set to false
by default.
Plug-in Options

Plug-in Options

APPENDIX B
Troubleshooting
This appendix includes the following topics:
l Backup and restore problems and solutions......................................................................... 138
l Configuration problems and solutions.................................................................................. 146

Backup and restore problems and solutions
You can resolve common backup and restore problems with the following troubleshooting
information.
Avamar Administrator shows a completed RMAN backup or restore as still
running
When you enable Avamar Administrator to monitor or cancel an RMAN backup or restore and then
run the RMAN operation, Avamar Administrator displays an incorrect status when the operation
completes.
When the RMAN backup or restore completes, the Activity window in Avamar Administrator
shows the operation as still running. This issue occurs because the v$rman_status does not report
status. For example, the following sql query becomes suspended:
select status from v$rman_status;
Contact Oracle for details about the solution to this issue.
avoracle Error <7936>: No valid targets found
A database restore fails with the following error:
avoracle Error <7936>: No valid targets found. Aborting the operation
To work around this problem, increase the snapupbrowsetimeoutsecs option in Avamar
Administrator:
1. From the Restore Command Line Options dialog box, click the More button.
2. Type the [avoracle]snapupbrowsetimeoutsecs option in the Enter Attribute field.
3. Type the number of seconds in the Enter Attribute Value field.
4. Click +.
5. Restart the restore.
Activity monitor of RMAN backup shows an incorrect status of still running.
Because of an issue with the Oracle database, the Activity monitor in the Avamar Administrator
may incorrectly show RMAN backups as still running.
To workaround this problem, run the follow in sqlplus when logged in as sysdba:
1. SQL> exec dbms_stats.DELETE_TABLE_STATS('SYS','X$KCCRSR');
The PL/SQL procedure will be successfully completed
2. SQL> exec dbms_stats.LOCK_TABLE_STATS('SYS','X$KCCRSR');
The PL/SQL procedure will be successfully completed
3. SQL> set autotrace on
4. SQL> select * from x$kccrsr;
Troubleshooting

5. exit sqlplus and relogin sqlplus
6. select status from v$rman_status;
Backups fail when backup copies is set to more than 1
You can use the BACKUP ... COPIES command to make identical copies of backups in RMAN.
Making copies is also known as backup duplexing.
If you configure backup copies to be more than 1 in RMAN, the backups that you perform with the
Avamar Plug-in for Oracle fail. For example, the following RMAN command sets backup copies to
3:
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE SBT_TAPE TO 3;
Backups that you run from Avamar Administrator or RMAN scripts that you run from the command
line fail after setting backup copies to 3:
l For backups from Avamar Administrator, an error message similar to the following error
appears in the sbtio.log:
error 7501: Could not connect to avoracle
l For backups from the RMAN command line, an error message similar to the following error
appears in the avtar log file:
avtar Error <5064>: Cannot open file cache_filename
The Avamar Plug-in for Oracle does not support the RMAN backup copies feature.
To prevent this backup failure, do not configure backup copies to be more than 1. The Oracle
RMAN documentation provides more information about the backup copies feature.
Note: To further protect the Oracle data beyond performing regular backups, consider using
Avamar replication. The Avamar Administration Guide provides more information about the
Avamar replication feature.
Log files for RMAN operations cannot be viewed from the Avamar Administrator
if a custom var directory is used.
When you use a custom var directory for RMAN backups, all CLI operations complete normally and
the log files can be viewed from the custom directory. However, the log files cannot be viewed
from the Avamar Administrator.
Backups unavailable after registering secondary RAC node
Backups are unavailable after the following occurs:
l The Avamar var directory is accidentally deleted.
l You registered the secondary RAC node with a virtual hostname other than the original virtual
hostname.
This problem applies only to Oracle 11g R1.
To prevent this problem, register the secondary node by using the original virtual hostname.
Cannot open file f_cache.dat error
The Avamar activity.log file contains avtar errors similar to the following:
avtar Info <8650>: Opening cache file /usr/local/avamar/var/f_cache2.dat
avtar Error <5064>: Cannot open file "/usr/local/avamar/var/
Troubleshooting

f_cache2.dat"
avtar Error <0000>: Invalid cache file header for /usr/local/avamar/var/
f_cache2.dat, clearing the cache
avtar Info <5065>: Creating new paging cache file /usr/local/avamar/var/
f_cache2.dat
avtar Error <5803>: Error writing 32-byte header to cache file /usr/
local/avamar/var/f_cache2.dat.
These errors occur if the specified var directory does not have sufficient permissions for the
Oracle user. The Oracle user requires read, write, and execute permissions for the var directory.
Specify the /var/avamar/clientlogs directory for backups that you perform from the RMAN
CLI.
Backups with Avamar Administrator automatically access the cache files from the /var/
clientlogs directory.
Cannot Sync error
If an RMAN session stops responding and a Cannot Sync message appears, try restarting RMAN
by using svrmgr.
Failed RMAN restore of control file is reported as completed in Avamar
Administrator
An RMAN restore of an Oracle control file fails when the taskfile parameter is used and invalid
client credentials are used in Avamar Administrator. However, the Avamar Administrator displays
the restore status as completed.
When you run an RMAN script with the taskfile parameter to restore an Oracle control file and the
client username and password have been deleted in Avamar Administrator, the restore fails with
the following type of error message:
RMAN-00571: =======================================
RMAN-00569: ===== ERROR MESSAGE STACK FOLLOWS =====
RMAN-00571: =======================================
RMAN-03002: failure of restore command at 01/22/2016 02:48:16
ORA-19870: error while restoring backup piece
CONTROLFILE.testdb.c-2652908924-20160122-00
ORA-19608: CONTROLFILE.testdb.c-2652908924-20160122-00 is not a backup
piece
However, the Activity window in Avamar Administrator incorrectly displays the restore status as
completed.
In this case, you can examine the activity logs to determine the cause of the restore failure.
Hot backup fails with Oracle not available error
The Avamar Plug-in for Oracle uses Oracle RMAN for a hot backup. Oracle RMAN requires the
Oracle database to be running for a hot backup.
If the database is not running, a hot backup will fail. Oracle RMAN then returns the following error:
Oracle not available
To start the Oracle database before a hot backup, use SQL*Plus:
Troubleshooting

1. Connect to the Oracle database by typing the following command:
sqlplus "/as sysdba"
2. Start the Oracle database by typing the following command:
startup;
The startup process displays status information about the Oracle instance.
Total System Global Area1 023410176 bytes
Database mounted
Level-1 backup of a large database fails with a snapview timeout
A level-1 backup of a large (300 GB) database that you perform from Avamar Administrator fails
with a snapview timeout. This issue is specific to Windows.
The log file contains the following error messages:
2014-04-03 16:04:26 avoracle Error <7011>: Unable to
successfully process snapview workorder because of timeout on
wait for snapview workorder MOD-1364973477725#0 (pid:3002-Oracle).
Please increase subprocess timeout using
--[avoracle]subprocesstimeoutsecs option and try again.
2014-04-03 16:04:26 avoracle Info <7271>: Final summary
generated subwork 1, cancelled/aborted 0, snapview 24,
exitcode 0
To work around this issue, set the --[avoracle]subprocesstimeoutsecs option to 350:
1. In the Backup Command Line Options dialog box, click More.
2. Type --[avoracle]subprocesstimeoutsecs in the Enter Attribute field.
3. Type 350 in the Enter Attribute Value field.
4. Click +.
5. Click OK.
ORA-19870: error while restoring backup piece
The restore of a database that contains datafiles that uses the UTF-8 character set fails with the
following error messages:
channel c0: ORA-19870: error while restoring backup piece
ORCL_0vnahoeh_1_1ORA-19504: failed to create file
"/home/oracle/app/oracle/oradata/orcl/home/oracle/app/oracle/product/
11.2.0/dbhome_1/home/oracle/app/oracle/product/11.2.0/dbhome_1/home/
oracle/app/oracle/product/11.2.0/dbhome_1.dbf"
ORA-27040: file create error, unable to create file
Solaris-AMD64 Error: 2: No such file or directory failover to previous
Troubleshooting

backup released channel: c0
RMAN-00571: =======================================
RMAN-00569: ===== ERROR MESSAGE STACK FOLLOWS =====
RMAN-00571: =======================================
RMAN-03002: failure of restore command at 05/09/2014 10:01:35
RMAN-06026: some targets not found - aborting restore
RMAN-06023: no backup or copy of datafile 3 found to restore
Oracle requires you to set the NLS_LANG environment variable to the correct language, territory,
and character set when the following configuration settings are true:
l The operating system is in a locale other than English.
l The database contains datafiles that use the UTF-8 character set.
ORA-25153: Temporary Tablespace is Empty
If you encounter a ORA-25153 Temporary Tablespace is Empty message, you must
manually re-create the temporary tablespace.
The Oracle Database Backup and Recovery Advanced User's Guide provides more information about
creating tablespaces.
ORA-27211: Failed to load Media Management Library
While backing up or restoring from either Avamar Administrator or the command line, RMAN fails
to load the Media Management Library. In both cases, RMAN writes output similar to the following
in the log file:
RMAN-00571: ==================================================
RMAN-00569: ========== ERROR MESSAGE STACK FOLLOWS ===========
RMAN-00571: ==================================================
RMAN-03009: failure of allocate command on c1 channel at 2014-9-4
20:27:34
ORA-19554: error allocating device, device type: SBT_TAPE, device name:
ORA-27211: Failed to load Media Management Library
Additional information: 25
Recovery Manager complete.
Restore fails to complete successfully
In rare situations, the restore process for a full database fails to complete successfully because of
the internal state of the database when the backup occurred. When this happens, additional
manual recovery steps can be necessary.
To restore a database after an unsuccessful restore attempt:
1. Restore the control file. Restoring Oracle data with RMAN on page 107 provides more
information.
2. Note the system change number (SCN) that corresponds to the backups that you need to
restore.
Troubleshooting

5. Type the following commands:
allocate channel c1 type sbt PARMS="SBT_LIBRARY=install-dir
/lib/libobk_avamar.so" format '%d_%U';
restore database;
restore archivelog until scn scn;
release channel c1;
}
where:
l install-dir is the base installation directory for the platform (for example, /usr/local/
avamar on Linux, /opt/AVMRclnt on Solaris, and C:Program Filesavsbin on
Windows).
l scn is an SCN value noted in step 2 on page 142.
6. Use Oracle documentation to perform other necessary recovery steps.
RMAN backup script fails with media management errors
An RMAN script that you create from the Schedule Backup page in the Oracle Enterprise
Manager does not include the RMAN send command. For example, the following script was
generated by using the Oracle Enterprise Manager user interface:
run {
allocate channel oem_sbt_bkup1 type 'SBT_TAPE' format '%U' parms
'"SBT_LIBRARY=/usr/local/avamar/lib/libobk_avamar64.so"';
backup incremental level 1 cumulative database;
backup archivelog all not backed up;
}
allocate channel for maintenance device type 'SBT_TAPE' parms
'"SBT_LIBRARY=/usr/local/avamar/lib/libobk_avamar64.so"';
delete noprompt obsolete recovery window of 31 days device type
'SBT_TAPE';
The script is missing the RMAN send command.
To solve this issue, use the Edit RMAN Script button from the Oracle Enterprise Manager to add
the appropriate RMAN send command. Backup and Restore with Oracle RMAN on page 97
provides more information about creating RMAN scripts.
RMAN backup script fails with ORA-19511
An RMAN script that backs up Oracle fails with ORA-19511. RMAN writes output similar to the
following to the log file:
RMAN-00571: ===================================================
RMAN-00569: =========== ERROR MESSAGE STACK FOLLOWS ===========
RMAN-00571: ===================================================
RMAN-03009: failure of backup command on ORA_SBT_TAPE_1 channel
at 2014-9-4 16:02:37
ORA-19506: failed to create sequential file,
name="06jtv7ks_1_1", parms=""
ORA-27028: skgfqcre: sbtbackup returned error
ORA-19511: Error received from media manager layer, error text:
sbtbackup: avtar exited, trying to create 06jtv7ks_1_1
Troubleshooting

The following problems might cause the RMAN backup script to fail with the ORA-19511 error:
l The /var/avamar directory does not have correct permissions to start a backup.
Use the /var/avamar/clientlogs directory instead of the /var/avamar directory.
l Either RMAN or libobk cannot locate avtar.
The allocate channel command in the RMAN backup or restore script must include
Avamar-home/bin as the PATH variable or include bindir="/usr/local/avamar/bin".
l An Oracle instance is running as a nonstandard user or group.
To determine if Oracle is installed as a nonstandard user or group, check the file permissions
for the Oracle home directory. For example, use the following commands:
cd /home/oracle/oracle/product/10.2.0/db_1/oradata
ls -l
total 28
drwxr-x--- 2 oracle oinstall 4096 Aug 26 2014 cataloged
drwxr-x--- 2 oracle oinstall 4096 Mar 9 18:05 db2
drwxr-xr-x 2 oracle oinstall 4096 Mar 30 17:21 orcl
drwxr-xr-x 2 oracle oinstall 4096 Mar 30 16:26 orcl.w
drwxr-xr-x 2 oracle oinstall 4096 Mar 10 15:50 plargedb
drwxr-xr-x 2 oracle oinstall 4096 Feb 6 16:20 plargedb.w
-rw-r--r-- 1 oracle oinstall 696 Dec 28 16:58 sqlnet.log
In the example, oracle is the user and oinstall is the group.
If a user other than oracle installs the Oracle database, the avoracle program must use the --
storageapp_username=username option. For example, if the user named test installs the Oracle
database, username is test.
RMAN-06056: could not access datafile n error on AIX
The avoracle program runs as root. If you encounter an RMAN-06056: could not access
datafile n error, it means avoracle was unable to open the file for processing.
This error on IBM AIX systems occurs when the default ulimit is set to 2097151. This default
setting limits the maximum file size that the root user can read to 1 GB.
To resolve this issue, change the ulimit setting for the root user to unlimited. This unlimited
setting allows avoracle to process large files.
RMAN script fails with WriteFile failed error
When you specify C:Program Filesavsbin for the --bindir variable in an RMAN script,
the script fails with the following errors:
RMAN-03009: failure of backup command on c1 channel at 10/20/2014
13:56:49
ORA-19502: write error on file "sample_1_1", blockno 1 (blocksize=512)
ORA-27030: skgfwrt: sbtwrite2 returned error
ORA-19511: Error received from media manager layer, error text:
stream->WriteFile failed
To resolve this issue, ensure that all variables in the RMAN script that specify the Windows
installation directory use Progra~1, the short name for the Program Files folder. The parser
cannot process spaces in folder names.
Troubleshooting

For example, the correct syntax for the --bindir variable is --bindir=C:Progra~1avsbin.
Time-out errors when using multiple RMAN channels
Allocating too many channels from Avamar Administrator might lock out processes. The backup or
restore can then fail with a time-out error. If a time-out error occurs, retry the operation by using
fewer channels.
This problem does not occur when using RMAN scripts.
Unable to process snapview workorder
The Avamar Plug-in for Oracle is unable to process the snapview workorder because the wait time
for the snapview workorder times out.
To work around this problem, increase the [avoracle]subprocesstimeoutsecs option in
Avamar Administrator:
1. From the Backup Command Line Options dialog box, click the More button.
2. Type the [avoracle]subprocesstimeoutsecs option in the Enter Attribute field.
3. Type the number of seconds in the Enter Attribute Value field.
4. Click +.
5. Restart the backup.
Unable to send CTL message
A backup or restore fails with one of the following error messages:
avoracle Error <6629>: INTERNAL: Unable to send CTL message
(n=-1, retcode=1, errno=0)
avoracle Error <6629>: INTERNAL: Unable to send CTL message
(n=-1, retcode=3, errno=0)
These errors can occur when you allocate too many channels for a backup or restore from Avamar
Administrator.
To resolve this issue, it is recommended to set the number of channels to no more than two times
the number of processors. If the problem still persists, reduce the number of channels.
The Number of RMAN Channels option is available from the Backup Command Line Options,
Restore Command Line Options, and New Dataset dialog boxes.
This problem does not apply to backups or restores started by an RMAN script.
The no_of_channels parameter no longer supported
When upgrading to the Avamar Plug-in for Oracle release 7.3 or greater from earlier versions, the
no_of_channels parameter is no longer supported.
After upgrading to release 7.3, Oracle datasets must be manually modified to use new max-
streams parameter to take effect.
Troubleshooting

Hidden backups
At the end of each database backup, the Avamar Plug-in for Oracle performs a final step to group
backup pieces into a consolidated backup.
If a backup fails in the final consolidation step, the backup becomes a hidden backup, which cannot
be searched for and restored from Avamar Administrator. At the moment of this backup failure,
the Avamar Plug-in for Oracle displays the following error message:
Failed to create the snapview. However, the database data has been
successfully backed up and is marked as a hidden backup. Restore is
available through CLI only. See the plug-in documentation for
information about restoring hidden backups.
It is recommended that you perform an immediate full database backup after the backup failure.
Although the backup label does not display in the Avamar Administrator window, the Avamar Plug-
in for Oracle performs a proper backup of the database data. To view information on hidden
backups, you must use the following command:
avtar --backups --server=Avamar_server_name --id=Avamar_server_username --
password=Avamar_server_password --account=Avamar_domain
The following example shows the output from the command. Records that are associated with the
Hidden Oracle RMAN backup are the hidden backup pieces.
Date Time Seq Label Size Plugin Working
directory Targets
---------- -------- ----- ----------------- ---------- --------
--------------------- -------------------
2017-09-12 09:25:11 106 CONTROLFILE.ORCL.c-1463025941-20170912-00
12033K Hidden Oracle RMAN backup C:appAdministratorproduct
11.2.0dbhome_2DATABASE 11g/ORCL/CONTROLFILE.ORCL.c-1463025941-20170912-00
2017-09-12 09:24:57 105 ORCL_2gse8rmv_1_1 257K Hidden Oracle RMAN
backup C:appAdministratorproduct11.2.0dbhome_2DATABASE 11g/ORCL/
ORCL_2gse8rmv_1_1
2017-09-12 09:24:39 104 ORCL_2fse8rmf_1_1 3329K Hidden Oracle RMAN
ORCL_2fse8rmf_1_1
2017-09-12 09:24:28 103 ORCL_2ese8rm0_1_1 84993K Hidden Oracle RMAN
ORCL_2ese8rm0_1_1
Completing a database recovery of a hidden backup
In the output from the avtar --backups command, the lines that have "Hidden Oracle RMAN
backup" indicate the hidden backups.
To perform a database recovery that involves the restore of a hidden backup, use the procedure
described in Restoring Oracle data with RMAN.
Note: You cannot restore the backup pieces from Avamar Administrator.
Configuration problems and solutions
You can resolve common configuration problems with the following troubleshooting information.
Avamar client and Avamar Plug-in for Oracle registration
To back up or restore Oracle by using the Avamar Plug-in for Oracle, you must register the Avamar
client with the Avamar server. The registration process can fail for either of the following
conditions:
Troubleshooting

l The Avamar plug-in_catalog.xml does not support the Avamar Plug-in for Oracle version.
l An administrator disabled the Avamar Plug-in for Oracle.
After you register the Avamar client, Avamar Administrator lists the client in the Oracle databases.
In addition, the avagent.log file (in the /var/avamar directory, by default) contains
information that verifies a successful registration:
****** Current MCS name 'avamar-1.example.com' ******
2014-1-1 15:08:37 avagent Info <7452>: Registration of client
/clients/Oracle-client.example.com with MCS
avamar-1.example.com:28001 successful.
2014-1-1 15:08:37 avagent Info <5928>: Registration of plugin
1002 Oracle successful.
2014-1-1 15:08:37 avagent Info <5928>: Registration of plugin
1001 Unix successful.
2014-1-1 15:08:37 avagent Info <5619>: Registration of client
and plugins complete.
2014-1-1 15:08:37 avagent Info <7150>: first work request
delayed for 180 seconds.
2014-1-1 15:11:37 avagent Info <7151>: first work request delay
finished.
Bitwidth of Avamar Plug-in for Oracle and Oracle
The bitwidth of the Oracle software, the Avamar Plug-in for Oracle, and the platform must match.
Ensure that you download the correct software packages for the platform and version of Oracle.
System requirements on page 30 provides more information.
Note: 64-bit operating systems do not support the 32-bit versions of Oracle 10g and later
versions. You can find additional information about Oracle on the Oracle website.
To check the bitwidth of Oracle, change to the $ORACLE_HOME/bin directory and type the
following command:
file ~/oracle/product/version/db-name/bin/rman
where:
l version is the version of Oracle.
l db-name is the name of the Oracle database.
/home/oracle/oracle/product/10.2.0/db_1/bin/rman: ELF 64-bit
LSB executable, AMD x86-64, version 1 (SYSV), for
GNU/Linux 2.4.0, dynamically linked (uses shared libs),
not stripped
To check the bitwidth of RMAN, change to the $ORACLE_HOME/bin directory and type the
following command:
file ~/oracle/product/version/db-name/bin/sqlplus
where:
l version is the version of Oracle.
l db-name is the name of the Oracle database.
/home/oracle/oracle/product/10.2.0/db_1/bin/sqlplus: ELF 64-bit
LSB executable, AMD x86-64, version 1 (SYSV), for
Troubleshooting

GNU/Linux 2.4.0, dynamically linked (uses shared libs),
not stripped
The text string ELF 64-bit LSB executable in the command output confirms that both
Oracle and RMAN are 64-bit.
Cluster Configuration Tool fails to start
Starting the Cluster Configuration Tool fails with the following error if the Windows system does
not have Microsoft . NET Framework 4 installed:
To run this application, you must install one of the following
versions of the .NET Framework: v4.0.30319 Contact your
application publisher for instructions about obtaining the
appropriate version of the .NET Framework
The Cluster Configuration Tool requires Microsoft .NET Framework 4. You can download and
install the .NET Framework 4 from the Microsoft Download Center.
Determining the version of Oracle
Use SQL*Plus to determine the version of Oracle:
1. Log in to the Oracle server.
2. Start SQL*Plus:
3. View version information by typing the following command:
select * from v$version;
Content similar to the following appears in the command shell:
Oracle Database 11g Enterprise Edition Release 11.1.0.7.0 -
Prod PL/SQL Release 11.1.0.7.0 - Production CORE 11.1.0.7.0
Production TNS for Linux: Version 11.1.0.7.0 - Production
NLSRTL Version 11.1.0.7.0 - Production
Disk space for the /var/avamar directory
The /var/avamar directory must have sufficient disk space for RMAN scripts and log files.
Backups and restores fail if the /var/avamar directory does not have enough space.
Check the /var/avamar directory for free space by using the applicable method for the system.
The following example shows output from the df -h command on a Red Hat Enterprise Linux
system:
Filesystem Size Used Avail Use% Mounted on
/dev/mapper/VolGroup00-LogVol00 985G 310G 625G 34% /
The RMAN scripts, RMAN log files, and the avoracle log files require a minimum of 100 MB of
disk space.
Oracle RAC database failover
If the registered Oracle RAC node fails over to another node, you must manually start the
avagent program on the other cluster nodes.
Run avagent.d restart to start the avagent program:
Troubleshooting

1. Log in to the failover node as root.
2. Change the directory by typing the following command:
cd /usr/local/avamar/ora_rac/etc
3. Start avagent by typing the following command:
./avagent.d restart
The following information appears in the command shell.
avagent Info <5241>: Logging to
/usr/local/avamar/ora_rac/var/avagent.log
avagent Info <5174>: - Reading /usr/local/avamar/ora_rac/var/
avagent.cmd
avagent.d Info: Client Agent started.
[OK]
Requirements for libobk_avamar.so and libobk_avamar.dll
The libobk_avamar.so file (on UNIX) and libobk_avamar.dll file (on Windows)
implement the Oracle SBT interface specification, which Avamar Plug-in for Lotus Domino and
RMAN requires for successful backup and restore operations.
The following requirements apply to both files:
l They must provide read and execute access to the Oracle user.
l They must be in the Avamar-home/lib directory.
l They must be the same bitwidth as Oracle.
To verify that the correct libobk_avamar file is installed in the Avamar-home/lib directory on
a UNIX platform, type the following commands:
cd Avamar-home/lib
file *
The text strings ELF 64-bit LSB shared object and ELF 32-bit LSB shared object
in the following command output confirm that both 64-bit and 32-bit libraries are present:
libobk_avamar64.so: ELF 64-bit LSB shared object, AMD x86-64,
version 1 (SYSV), not stripped
libobk_avamar.so: ELF 32-bit LSB shared object, Intel 80386,
version 1 (SYSV), not stripped
RMAN executable file and Oracle versions
The RMAN executable file version must match the Oracle database version. For example, the
ORACLE_HOME/bin directory contains the RMAN executable file. Linux systems use the default
RMAN file in the /usr/X11R6/bin directory. An RMAN backup or restore script that uses the
default RMAN executable file causes the backup or restore operation to fail.
For multiple versions of Oracle, RMAN executables must point to the correct ORACLE_HOME/bin
directory.
To determine whether the default RMAN executable points to the correct RMAN executable in the
ORACLE_HOME/bin directory, type the following commands:
which rman
/usr/X11R6/bin/rman
rpm -qf /usr/X11R6/bin/rman
Troubleshooting

xorg-x11-devel-6.8.2-1.EL.33
xorg-x11-devel-6.8.2-1.EL.33
more oratab
catalogdb:/home/oracle/oracle/product/10.2.0/db_1:N
largedb:/home/oracle/OraHome:N
orcl:/home/oracle/oracle/product/10.2.0/db_1:N
The sample output from the oratab file includes a database that is named largedb. This database
has both Oracle 9i and Oracle 10g homes. Because largedb is an Oracle 9i instance, the correct
RMAN executable is in /home/oracle/OraHome/bin/rman.
Set the PATH variable to the ORACLE_HOME/bin directory to ensure that RMAN uses the correct
executable file. Before running RMAN scripts, run /usr/local/bin/oraenv.
Stopping Avamar Administrator processes
Note: Only administrators, who understand the consequences of stopping Avamar
Administrator processes, should perform the following procedure. Use this procedure for
emergencies only.
The following procedure runs the UNIX kill command to stop avoracle processes, which were
started by the Avamar Administrator interface. The Avamar Administrator automatically starts the
avoracle processes for browse, backup, and restore operations. Stop these avoracle
processes only when you determine that an issue occurs with a browse, backup, or restore
operation.
1. Log in to the Oracle server.
2. Show all Avamar processes by typing the following command:
ps -ef|grep avoracle
The command shell displays a list of active processes. Some of them are avoracle processes
for the Avamar Plug-in for Oracle.
3. Locate the avoracle processes in the list and note the process ID numbers (PIDs).
4. Terminate the process by typing the following command:
kill pid
where pid is a process ID displayed in step 2.
5. Repeat step 4 until all avoracle processes are stopped.
Unable to browse Oracle databases with Avamar Administrator
The Browse for Files, Folder, or Directories option in Avamar Administrator does not display any
Oracle databases. To verify the issue with the browse option, use the following command:
./avoracle --browse
When the browse problem exists, the output from the avoracle program contains the following
message:
avoracle Info <7908>: browse returning with 0 items
The following circumstances can prevent you from browsing the Oracle databases:
l The Avamar client and Oracle databases use two separate NIC cards, each with different IP
addresses and hostnames.
Troubleshooting

l The oratab file contains invalid entries.
Verifying the client and plug-in versions
For all supported platforms, install the Avamar client before installing the Avamar Plug-in for
Oracle. The versions of the Avamar client and Avamar Plug-in for Oracle must be the same.
The following table includes methods to verify the installation of the Avamar client.
Table 9 Avamar client installation verification
Platform Method
Microsoft Windows Use the Windows Explorer to verify that the
C:Program filesavs folder exists and
contains libobk_avamar.dll.
Oracle Linux, Red Hat Linux, or SUSE Linux Use the rpm command:
rpm -qa |grep -i avamar
HP-UX Use the swinstall command:
swinstall -list
IBM AIX Use the smitty command to list all software
or to search for the Avamar client software
package.
Solaris Use the pkginfo command:
pkginfo|grep -i AVMRclnt
Troubleshooting

Troubleshooting

GLOSSARY
A
activation The process of passing the client ID (CID) back to the client, where it is stored in an
encrypted file on the client file system.
See also client activation
administrator Person who normally installs, configures, and maintains software on network
computers, and who adds users and defines user privileges.
archive logs Log files that contain a copy of one of the filled members of an online redo log group.
The archiving process requires that the database be set to ARCHIVELOG mode. Oracle
terminology refers to archive logs as archive redo logs.
Avamar Administrator A graphical management console software application that is used to remotely
administer an Avamar system from a supported Windows or Linux client computer.
Avamar client A computer or workstation that runs Avamar software and accesses the Avamar server
over a network connection. Avamar client software comprises a client agent and one or
more plug-ins.
Avamar server The server component of the Avamar client/server system. Avamar server is a fault-
tolerant, high-availability system that efficiently stores the backups from all protected
clients. It also provides essential processes and services required for data restores,
client access, and remote system administration. Avamar server runs as a distributed
application across multiple networked storage nodes.
avtar The Avamar process that performs backups and restores.
B
backup A point-in-time copy of client data that can be restored as individual files, selected
data, or as an entire backup.
backup policy In the AUI, a backup policy specifies a dataset, schedule, and retention settings that
are applied to a client or a group of clients. A backup policy must contain at least one
Avamar client. If the backup policy contains two or more clients, the clients must
belong to the same Avamar domain. You can override backup policy settings at the
client level.
browse The process of viewing data that is available for backup on a client computer or restore
from the Avamar server.

C
client activation The process of passing the client ID (CID) back to the client, where it is stored in an
encrypted file on the client file system.
See also activation
client agent A platform-specific software process that runs on the client and communicates with
the Management Console Server (MCS) and with any plug-ins installed on that client.
client registration The process of establishing an identity with the Avamar server. When Avamar
recognizes the client, it assigns a unique client ID (CID), which it passes back to the
client during client activation.
See also registration
cluster Two or more independent network servers, usually with exact copies of the same
software and data, that operate and appear to clients as if they are a single unit. A
cluster configuration enables work to be shifted from one server to another, providing
high availability, which allows application services to continue despite most hardware
or software failures.
Cluster Configuration
Tool
Avamar configuration wizard to configure the cluster client.
cold backup A backup of database objects that you perform while the corresponding database or
instance is shut down and unavailable to users. Also known as an offline backup.
D
database A collection of data arranged for ease and speed of update, search, and retrieval by
computer software.
database files Oracle database files include datafiles, control files, and online redo logs.
Data Domain system Disk-based deduplication appliances and gateways that provide data protection and
disaster recovery (DR) in the enterprise environment.
dataset A policy that defines a set of files, directories, and file systems for each supported
platform that are included or excluded in backups across a group of clients. A dataset
is a persistent and reusable Avamar policy that can be named and attached to multiple
groups.
DD Boost The API that Avamar clients use to access a Data Domain system. The DD Boost API is
installed automatically on the client computer when you install the Avamar client. It is
also installed automatically on the Avamar server when you install Avamar.
disaster recovery Recovery from any disruptive situation, such as hardware failure or software
corruption, in which ordinary data recovery procedures are not sufficient to restore a
system and its data to normal day-to-day operations. A disaster recovery can be a bare
metal recovery.
Glossary

DNS Domain Name Server. A dynamic and distributed directory service for assigning domain
names to specific IP addresses.
domain A feature in Avamar Administrator that is used to organize large numbers of clients into
named areas of control and management.
F
file system Software interface used to save, retrieve, and manage files on storage media by
providing directory structures, data transfer methods, and file association.
G
group A level of organization in Avamar Administrator for one or more Avamar clients. All
clients in an Avamar group use the same group policies, which include the dataset,
schedule, and retention policy.
group policy In Avamar Administration, a group policy is defined as a dataset, schedule, and
retention policy for all clients in an Avamar group.
L
LAN Local Area Network.
M
MCS Management console server. The server subsystem that provides centralized
administration (scheduling, monitoring, and management) for the Avamar server. The
MCS also runs the server-side processes used by Avamar Administrator.
Media Management
Library (MML)
A software library used by RMAN to back up data to tertiary storage. The MML for the
Avamar Plug-in for Oracle is libobk_avamar.
Media Manager (MM) A third-party networked backup system. MM works with Recovery Manager so that
database backups can be written directly to tertiary storage.
metadata Data about the backup, including information about the original database files, the
backup types, the date and time of the backup, and other information necessary for
restore.
O
Oracle instance A memory structure and a group of Oracle Server processes running on a node.
oratab file A text file that contains the system identifier and home directory of the Oracle
database. A typical oratab entry is similar to the following: ora91:/space/local/
oracle/ora901. The default location for the oratab file is /var/opt/oracle on
Solaris and /etc on other systems.
Glossary

P
plug-in Avamar client software that recognizes a particular kind of data resident on that client.
point-in-time restore Restore of a backup to a specific point in time.
policy A set of rules for client backups that can be named and applied to multiple groups.
Groups have dataset, schedule, and retention policies.
R
Recovery Manager
(RMAN)
A software application that provides a command line interface for hot and cold
backups, as well as cold recovery of a supported Oracle database.
redirected restore The process of restoring a backup to a different location than the original location
where the backup occurred.
registration The process of establishing an identity with the Avamar server. When Avamar
recognizes the client, it assigns a unique client ID (CID), which it passes back to the
client during client activation.
See also client registration
restore An operation that retrieves one or more file systems, directories, files, or data objects
from a backup and writes the data to a designated location.
retention The time setting to automatically delete backups on an Avamar server. Retention can
be set to permanent for backups that should not be deleted from an Avamar server.
Retention is a persistent and reusable Avamar policy that can be named and attached
to multiple groups.
S
schedule The ability to control the frequency and the start and end time each day for backups of
clients in a group. A schedule is a persistent and reusable Avamar policy that can be
named and attached to multiple groups.
System Backup to Tape An Oracle architecture that supports directly writing backups to tape (and reading
them) by using the Media Management Library.
T
tablespace A logical storage unit in a database, which groups related logical structures together.
transaction logs A record of database transactions or list of changed files in a database, stored in a log
file to execute quick restore and rollback transactions.
Glossary

U
User Account Control
(UAC)
A Windows feature available in Windows 7, Windows Server 2008, Windows Server
2008 R2, Windows Vista. UAC helps prevent unauthorized changes to your computer.
When functions that could potentially affect a computer's operation are made, UAC
prompts the user for permission or for an administrator's password before continuing
with the task.
Glossary

Glossary

Docu91844

More Related Content

Similar to Docu91844 (20)

Recently uploaded (20)

Docu91844