Oraasfsa

Features - Oracle iDataAgent
Table of Contents
Overview
System Requirements - Oracle iDataAgent
Installation
Install the Oracle iDataAgent - Windows
Install the Oracle iDataAgent - Windows - Clustered Environment - Virtual Server
Install the Oracle iDataAgent - Unix
Install the Oracle iDataAgent - Unix - Clustered Environment
Backup Data - Oracle iDataAgent
Restore Data - Oracle iDataAgent
Configuration
Instances - Oracle iDataAgent
Subclients - Oracle iDataAgent
Management
Backup Job History
Restore Job History
Troubleshooting
Backup - Oracle or Oracle RAC Troubleshooting
Restore Data - Oracle or Oracle RAC Troubleshooting
Page 1 of 199
Overview - Oracle iDataAgent
Choose from the following topics:
Introduction
Supported Data Types
Tree Levels in the Oracle iDataAgent
License Requirement
Databases, Instances and Subclients
Securing Oracle Application Data Using the File System iDataAgent
Third-Party Command Line
Performance Tuning
Ensuring Successful Oracle Data Protection and Recovery Operations
Disaster Recovery Considerations
Related Topics:
Running RMAN Scripts using the Command Line Interface
Introduction
The Oracle database is comprised of several objects. These objects can be backed up by the Oracle
iDataAgent. For more information on the Oracle objects, refer to your Oracle documentation.
Back to Top
Supported Data Types
Data Protection Operations for the following data types are supported by the Oracle iDataAgent:
Oracle database files, which include data files (*.dbf) and control files (*.ctl)
Archived redo logs
Data Protection Operations for all other data types not mentioned in the above list are not supported by
the Oracle iDataAgent, including:
Oracle application files (can be secured by the appropriate File System iDataAgent)
Back to Top
Tree Levels in the Oracle iDataAgent
When the Oracle iDataAgent is installed, the following levels are automatically created in the CommCell
Browser.
Page 2 of 199
Back to Top
License Requirement
To perform a data protection operation using this Agent a specific Product License must be available in
the CommServe
Server.

Review general license requirements included in License Administration. Also, View All Licenses provides
step-by-step instructions on how to view the license information.
Back to Top
Databases, Instances and Subclients
During installation, the Oracle iDataAgent software establishes the Oracle iDataAgent. Before you backup
data, you must however, define the data that you want to back up, and how this data should be backed
up. Consider the following:
Databases and Instances are similar for the Oracle iDataAgent. This means that for each database that
you want to back up, you must create an Instance for it.
Initially, the system creates a default subclient for each Oracle Instance that you create. You can
create one or more subclients for each instance, depending on the backup strategy that you devise to
meet the backup needs of your system.
To determine the best strategy, you should ask the following questions:
What is the available backup window?
Should the database be accessible while the backup is running?
What are the time constraints for recovering the database?
If your Oracle database is in the NOARCHIVELOG mode, you must backup the database offline. For an
online backup of the database, it must be in ARCHIVELOG mode. If the database must be accessible, and
you have a small backup window, you may want to run a series of online backups in which different
portions of the database are backed up at different times. You may also want to combine all of these
bootes: Client
Oracle: Agent
<user_defined_instance>: Instance

In order to run the first backup, instances must be added. Each instance
creates a default subclient.
Page 3 of 199
backup types in your backup strategy. Once you have determined your backup needs you can define your
backup strategy by creating one or more subclients for the database. To perform this task effectively, you
need to understand the key aspects of the CommCell architecture, most notably:
Instances
Subclients
Storage Policies
If at some later time you decide to change the way a client computer is backed up, you can always
change the CommCell configuration, in whole or in part. You may also add new databases to be secured
by the system, or remove databases currently secured.
See also: Establishing Parallel Data Protection Operations Using Subclients
Moving Instances
Oracle instances can be moved from one client computer to another within a CommCell. See Moving an
Oracle Instance for more information.
Back to Top
Securing Oracle Application Data Using the File System iDataAgent
In addition to the Oracle database, there may be Oracle application files stored on the computer (that is,
the Oracle client). Such data is not backed up by the Oracle iDataAgent. To secure such data from an
Oracle client, you must back it up using the appropriate iDataAgent for the computers file system.
Back to Top
Third-Party Command Line
The Oracle iDataAgent supports the ability to perform backups and restores across clients from the RMAN
Command Line. For more information, see Third-Party Command Line Operations.
Back to Top
Performance Tuning
Performance tuning parameters are a valuable tool for the recovery administrator to increase efficiency of
backup and restore operations by avoiding throughput bottlenecks. The performance of Oracle backup
and restore operations can be optimized through the appropriate configuration of RMAN parameter
options provided in the Subclient Properties dialog box. A brief description of certain key performance
tuning parameters and their recommended uses is provided below.
Data Files per BFS
The Data Files per BFS parameter defines the number of datafiles to be bundled in each RMAN backupset,
for datafile backups. It is often used in conjunction with the Max Open Files parameter to establish the
proper RMAN multiplexing factor for disk buffer allocation. For example, assume that you are backing up
six datafiles with one RMAN channel. If FILESPERSET=6 and MAXOPENFILES=1, then the channel
includes 6 datafiles in a backupset but does not multiplex the files because RMAN is not reading from
more than one file simultaneously. The channel reads one file at a time and writes to the backup piece. In
this case, the level of multiplexing is 1 and would result in relatively slower backups because of the
throughput bottleneck. Ideally, the MAXOPENFILES parameter should be set in such a way that the
number of files read simultaneously is just enough to utilize the output device fully. In this example, if
FILESPERSET=6 and MAXOPENFILES=3, the level of multiplexing is 2 and would result in a quicker more
efficient backup, especially when the output device is tape, by allowing RMAN to provide the proper disk
buffer allocation. However, keep in mind that multiplexing too many files can decrease restore
performance depending on the hardware configuration.
Page 4 of 199
Archive Files per BFS
The Archive Files per BFS parameter defines the number of archive files to be bundled in each RMAN
backupset, for archive log backups. Its use is similar to the Data Files per BFS parameter discussed
above.
Max Backupset Size (KB)
The Max Backupset Size parameter defines the maximum allowable size for an RMAN backupset. It can
be used to adjust performance for either partial restore or whole database restores. The proper setting
depends on whether faster whole database restores or partial restores are required. A smaller
MAXBACKUPSETSIZE will result in faster partial restores, however, whole database restores will be
slower. A larger MAXBACKUPSETSIZE will result in faster whole database restores, but may not be
optimal for partial restores. It is generally recommended that you avoid entering too small a value for
this setting, which should be at least 2000 KB. The exception is the default value of 0, which means
unlimited.
Max Open Files
The Max Open Files parameter defines the maximum number of concurrent open datafiles that RMAN can
read from simultaneously during a backup operation. A smaller MAXOPENFILES setting results in faster
performance on most systems. However, it should be used in conjunction with the Data Files per BFS or
Archive Files per BFS parameters to achieve the most efficient RMAN multiplexing level for optimizing disk
buffer allocation. The goal is to set the number of files read simultaneously to fully utilize the output
device. See Data Files per BFS above for a discussion of how these parameters work together. Keep in
mind that the default value for this parameter is 8.
See Configure Backup Arguments for step-by-step instructions. See also publications from Oracle
Corporation on the topic of RMAN performance tuning for a more complete understanding of this subject.
Disk Ratio
Disk ratio enables RMAN to read data files across disks and group them in a backup set. For example,
consider data files distributed across 10 disks that supply data at 10 bytes/second and a tape drive that
needs 40 bytes/second to keep streaming. In this case, you can set the disk ratio value to 4, which will
direct RMAN to include data files from 4 disks in each backup set. Disk ratio groups the data files into
backup sets and distributes the backup load across disks. Even though disk ratio facilitates backup
performance, you should keep in mind that more the number of disks from which data files are grouped,
slower will be the restore performance. Hence, make sure that a minimum possible value is set for disk
ratio.

Back to Top
The Oracle iDataAgent provides the ability to preview backup and restore scripts as well as validate the
database, prior to actually running a data protection or recovery operation, to help ensure that Oracle
backups and restores will run smoothly. Descriptions of these features are provided below.
Script Preview
You can preview the backup and restore scripts that will be submitted to RMAN to back up or restore data
on a client. Previewing the script before running a backup or restore is useful for identifying whether the
selected backup or restore options will yield the desired result in the script. The script text can be
previewed from the Backup Options and Restore Options dialogs, and provides the capability for you to
copy the text from the display window for manual submission in RMAN, if desired.
See Preview a Script for step-by-step instructions.
Validate
Page 5 of 199
You can run a validate job to ensure the integrity of the data and availability of the media before actually
running a backup or restore job. When the validate option is selected on the Subclient Properties (Backup
Arguments) tab or Advanced Restore Options (Options) tab, this will cause the system to simulate either
a backup or restore job without using any media or over-writing the Oracle database. After the validate
job completes, you can view the log file for the job to identify and correct any validation issues prior to
running the backup or restore.
For step-by-step instructions, see Validate a Backup or Restore.
Back to Top
Before you use your agent, be sure to review and understand the associated full system restore (or
disaster recovery) procedure. The procedure for some agents may require that you plan specific
actions or consider certain items before an emergency occurs. See Disaster Recovery for more
information regarding your agent.
Consider the following when you are planning for a full system restore of the Oracle database in the
event of a destroyed or damaged client:
For Oracle on any platforms, we recommend that you perform the following configuration steps in the
Oracle client:
1. Exclude the Oracle database files from your file system backup. You can do this by establishing a
backup filter for .dbf files in the appropriate file system subclient(s).
2. Ensure that the recovery catalog is available on a separate machine. If the recovery catalog is on
the same machine, we recommend that you take the following actions:
a. Export the user, who is the owner of the recovery catalog using the Oracle export command
to an external flat file.
b. Ensure that this external flat file is included in your file system backup.
c. Ensure that your file system data is backed up regularly.
3. Select the Resync Catalog option in the Subclient Properties (Backup Arguments) tab of the
subclient used for backing up the entire database.
Back to Top
Page 6 of 199
System Requirements - Oracle iDataAgent
The following requirements are for the Oracle iDataAgent:
Application/Operating System Processor
Oracle 9.2.x Database 32-bit (Enterprise or Standard Edition) on:
Linux Red Flag Linux
Red Flag Linux 4.x with glibc 2.3.x
Red Hat Enterprise Linux/CentOS
Red Hat Enterprise Linux/CentOS 3.x with glibc
2.3.x
2.3.x
SuSE Linux
SuSE Linux 9.x with glibc 2.3.x

Intel Pentium or compatible processors
Solaris
Solaris 8 with a minimum of Service Packs 108528-
13
02
Solaris 10.x
Sun Sparc5 or higher recommended
Windows Windows 2003
Microsoft Windows Server 2003 32-bit Editions with
a minimum of Service Pack 1
Microsoft Windows Server 2003 R2 Editions

All Windows-compatible processors
supported
Oracle 9.2.x Database 64-bit (Enterprise or Standard Edition) on:
AIX
AIX 5.2 with maintenance level 10 (or higher) and
runtime library xlC.rte 8.0.0.0 or higher
AIX 5.3 with technology level 6 (or higher) and
Power PC (Includes IBM System p)
HP-UX
HP-UX 11i v1 (11.11) with a minimum of OS patch
PHCO29328 (contact Hewlett Packard to obtain the
patch)
HP-UX 11i v2 (11.23)
HP-UX 11i v3 (11.31)
PA-RISC
HP-UX 11i v2 (11.23)
HP-UX 11i v3 (11.31)
Intel Itanium
Linux Red Hat Enterprise Linux/CentOS
2.3.x

Intel Itanium, x64 or compatible
processors
Page 7 of 199
2.3.x
SuSE Linux
Solaris
13
02
Solaris 10.x
Tru64
Tru64 OSF1 Release 5.1B-3 or higher Compaq (DEC) AlphaServer DS Series
computer or higher recommended
Microsoft Windows Server 2003 x64 Editions with a
minimum of Service Pack 1

supported
Oracle 10g (10.1.x) Database 32-bit (Enterprise or Standard Edition) on:
Linux Red Flag Linux
Red Flag Linux 4.x with glibc 2.3.x
2.3.x
2.3.x
SuSE Linux


supported
Oracle 10g (10.1.x) Database 64-bit (Enterprise or Standard Edition) on:
AIX
HP-UX
patch)
HP-UX 11i v2 (11.23)
HP-UX 11i v3 (11.31)
PA-RISC
HP-UX 11i v2 (11.23)
HP-UX 11i v3 (11.31)
Intel Itanium
Page 8 of 199
Linux Red Hat Enterprise Linux/CentOS
2.3.x

Intel Itanium
2.3.x
Intel Itanium, x64 or compatible
processors
SuSE Linux

x64
Solaris
13
02
Solaris 10.x
Solaris 10.x (Flying Zones supported)
Tru64
Windows
supported
Oracle 10g R2 (10.2.x) Database 32-bit (Enterprise or Standard Edition) on:
Linux Oracle
Oracle Enterprise Linux 4 with glibc 2.3.x
2.3.x
2.3.x
2.5.x
SuSE Linux

Solaris
Solaris 10.x Intel Pentium or compatible processors
Windows 2008
Microsoft Windows Server 2008 32-bit Editions*
*Core and R2 Editions not supported

supported
Page 9 of 199
AIX
AIX 6.1
HP-UX
patch)
HP-UX 11i v2 (11.23)
HP-UX 11i v3 (11.31)
PA-RISC
HP-UX 11i v2 (11.23)
HP-UX 11i v3 (11.31)
Intel Itanium
Linux Oracle

x64
2.3.x
Intel Itanium
2.3.x
2.5.x
Intel Itanium, x64, Power PC (Includes
IBM System p) or compatible processors
SuSE Linux

Intel Itanium, x64, Power PC (Includes
IBM System p) or compatible processors
SuSE Linux 11.x with glibc 2.9.x x64

Solaris
13
02
Solaris 10.x
Solaris 10.x (Flying Zones supported)
Solaris 10.x x64
Tru64
Page 10 of 199
Windows 2008
Microsoft Windows Server 2008 x64 Editions*
*Core Editions not supported
Microsoft Windows Server 2008 R2 x64 Editions
supported
Oracle 11g Database 32-bit (Enterprise or Standard Edition) on:
Linux Oracle
2.3.x
2.5.x
SuSE Linux

Windows 2008
supported
Oracle 11g Database 64-bit (Enterprise or Standard Edition) on:
AIX
AIX 5.3
AIX 6.1
HP-UX
HP-UX 11i v2 (11.23)
HP-UX 11i v3 (11.31)
PA-RISC
HP-UX 11i v2 (11.23)
HP-UX 11i v3 (11.31)
Intel Itanium
Linux Oracle

x64
Page 11 of 199
2.3.x
2.5.x
SuSE Linux
Solaris
Solaris 9
Solaris 10.x
Windows 2008
supported
Linux
Oracle
2.3.x
2.5.x
SuSE Linux

Windows 2008
supported
AIX
AIX 5.3
AIX 6.1
Page 12 of 199
HP-UX
HP-UX 11i v3 (11.31) Intel Itanium
HP-UX 11i v3 (11.31) PA-RISC
Linux
Oracle
2.3.x
2.5.x
SuSE Linux
x64

Solaris
Solaris 10.x Sun Sparc5 or higher recommended
Solaris 10.x x64
Windows 2008
Microsoft Windows Server 2008 R2 Editions*
supported
Cluster Support
See Clustering - Support
Memory
Windows
32 MB RAM per stream/drive minimum required beyond the requirements of the operating system and
running applications
AIX, HP-UX Linux, Solaris and Tru64
64 MB RAM per stream/drive minimum required beyond the requirements of the operating system and
running applications
Swap space = 2*RAM size
Hard Disk
Windows
112 MB minimum of hard disk space for software/ 498 MB recommended
50 MB of additional hard disk space for log file growth
Page 13 of 199
80 MB of temp space required for install or upgrade (where the temp folder resides)
Unix
230 MB minimum of hard disk space for software
Peripherals
DVD-ROM drive
Network Interface Card
Miscellaneous
TCP/IP Services configured on the computer.
The File System iDataAgent will be automatically installed during installation of the Oracle iDataAgent, if
it is not already installed. For System Requirements and install information specific to the File System
iDataAgents, refer to:
System Requirements - Microsoft Windows File System iDataAgent
System Requirements - Unix File System iDataAgent
On Solaris computers, the operating system must have been installed with at least the user level
software option selected
Microsoft Visual C++ 2008 Redistributable Package is automatically installed. Note that Visual C++ 2008
Redistributable Package can co-exist with other versions of this software.
If you have SELinux enabled on the client computer, create the SELinux policy module as a root user
before performing a backup. The SELinux Development package must be installed on the client.
To create SELinux policy module, perform the following steps as user "root":
1. Create the following files in the /usr/share/selinux/devel directory:
File Name Content of the file
<directory>/<file_name>.te
where:
<directory> is /usr/share/selinux/devel
<file_name> is the name of the Unix file, created to
save the policy module statement. It is a good idea to
use the same name for policy module and the file.
For example: When you are creating a policy module
for backup_IDA application, you can use the following
file name: backup_IDA.te

The content of the file should be as follows:
policy_module(<name>,<version>)
##############################
where:
<name> is the name of the policy module. You can
give any unique name to the policy module, such
as a process or application name.
<version> is the version of the policy module. It
can be any number, such as 1.0.0.
For Example: While creating a policy module for
the backup_IDA application, you can use the
following content.
policy_module(backup_IDA,1.0.0)
<directory>/<file_name>.fc
where:
<directory> is /usr/share/selinux/devel
<file_name> is the name of the Unix file, created to
save the policy module statement. It is a good idea to
The content of the file should be as follows:
Note that the following list of files is not
exhaustive. If the process fails to launch,
check /var/log/messages. Also, if required, add
it to the following list of files.
/opt/<software installation
Page 14 of 199
2. Create the policy file from command line. Use the following command. Ensure that you give the
following commands in the /usr/share/selinux/devel directory.
[root]# make backup_IDA.pp
Compiling targeted backup_IDA module
/usr/bin/checkmodule: loading policy configuration from tmp/backup_IDA.tmp
/usr/bin/checkmodule: policy configuration loaded
/usr/bin/checkmodule: writing binary representation (version 6) to
tmp/backup_IDA.mod
Creating targeted backup_IDA.pp policy package
rm tmp/backup_IDA.mod tmp/backup_IDA.mod.fc
[root]# semodule -i backup_IDA.pp
[root]#
use the same name for policy module and the file.
For example: When you are creating a policy module
for backup_IDA application, you can use the following
file name: backup_IDA.fc

directory>/Base/libCTreeWrapper.so --
gen_context
(system_u:object_r:texrel_shlib_t,s0)
directory>/Base/libCVMAGuiImplgso --
gen_context
directory>/Base/libdb2locale.so.1 --
gen_context
directory>/Base/libdb2osse.so.1 --
gen_context
directory>/Base/libDb2Sbt.so --
gen_context
directory>/Base/libdb2trcapi.so.1 --
gen_context
directory>/Base/libDrDatabase.so --
gen_context
directory>/Base/libIndexing.so --
gen_context
directory>/Base/libSnooper.so --
gen_context

Page 15 of 199
DISCLAIMER
Minor revisions and/or service packs that are released by application and operating system vendors may, in some cases, affect the working of our
software. Although we may list such revisions and/or service packs as supported in our System Requirements, changes to the behavior of our
software resulting from an application or operating system revision/service pack may be beyond our control. However, we will make every effort to
correct such disruption as quickly as possible. When in doubt, please contact your software provider to ensure support for a specific application or
operating system.
Additional considerations regarding minimum requirements and End of Life policies from application and operating system vendors are also
applicable.
3. Execute the policy module. Use the following command:
[root]# restorecon -R /opt/<software installation directory>
SELinux is now configured to work with this application.
Page 16 of 199
Install the Oracle iDataAgent - Windows
Click on a link below to go to a specific section of the software installation:
Install Requirements
Install Checklist
Before You Begin
Install Procedure
Getting Started
Select Components for Installation
Firewall Configuration
Configuration of Other Installation Options
Storage Policy Selection
Client Group Selection
Configure Oracle Specific Information
Verify Summary of Install Options
Schedule Automatic Update
Install Remaining Cluster Nodes
Setup Complete
Post-Install Considerations
The Oracle iDataAgent is installed on the computer on which the Oracle Database application resides.
(This computer is referred to as the Client computer in this install procedure.)
Verify that the computer in which you wish to install the software satisfies the minimum requirements
specified in System Requirements - Oracle iDataAgent and in System Requirements - Microsoft Windows
File System iDataAgent.
The following procedure describes the steps involved in installing the Windows File System and the
Oracle iDataAgent. If you choose to install multiple components simultaneously, refer to the appropriate
procedures for installation requirements and steps specific to the component. Note that when you install
multiple components, the sequence of the install steps may vary.
Review the following Install Requirements before installing the software:
General
Agents should be installed only after the CommServe and at least one MediaAgent have been. Also,
keep in mind that the CommServe
software and MediaAgent must be installed and running (but not

necessarily on the same computer), before you can install the Agent.
This software should be installed in a CommCell component with current versions of the CommServe
Server and MediaAgent software.
Close all applications and disable any programs that run automatically, including anti-virus, screen
savers and operating system utilities. Some of the programs, including many anti-virus programs,
may be running as a service. Stop and disable such services before you begin. You can re-enable
them after the installation.
Ensure there is an available license on the CommServe software for the Agent.
Verify that you have the software installation disc that is appropriate to the destination computers
operating system.
Make sure that you have the latest software installation disc before you start to install the software.
If you are not sure, contact your software provider.
Page 17 of 199
Firewall
If the CommServe
Server, MediaAgent and/or Clients communicate across two-way firewall(s):

Ensure port 8400 is allowed connections through the firewall.
In addition a range of bi-directional ports (consecutive or discrete) must also be allowed
connections through the firewall.
For information on configuring the range of ports, see Port Requirements for Two-way Firewall.
If the CommServe Server, MediaAgent and/or Clients communicate across one-way firewall(s):
Identify a range of outbound ports (consecutive or discrete) for use by the software.
For information on configuring the range of ports, see Port Requirements for One-way Firewall.
If the MediaAgent/Client communicates with the CommServe Server across a one-way firewall, you
must add the MediaAgent/Client host name (or the IP address) in the CommServe computer before
installing the necessary software on the MediaAgent/Client computer.
Reboot Required
A reboot will be required after installation, before you can use this Agent.
Agent Specific
The Oracle Database application has been installed on the client.
For a database Agent, you may be required or be given the option to shut down the
instances/databases for the agent before or during the following procedure. See Shut Down
Instances for more information.
Although the File System iDataAgent is a prerequisite, you do not have to install it separately. The
Oracle iDataAgent installation program checks for the File System iDataAgent and installs it
automatically if it is not installed.
A reboot will be required after install/upgrade to initialize the QSnap driver, before you can use this
Agent.
Install Checklist
Collect the following information before installing the software. Use the space provided to record the
information, and retain this information in your Disaster Recovery binder.
1. Install folder
location:________________________________________________________________
See Select Components for Installation for more information.
2. If the CommServe Server and the client computer communicate across a firewall:
Firewall ports:
______________________________________________________________________
Hostnames and/or IP Addresses and corresponding GxCVD port numbers of computers on the
other side of the firewall:______________
Keep Alive Interval
minutes:____________________________________________________________
Hostname for outgoing tunnel
connections:_________________________________________________
Tunnel Initialization Interval
seconds:_____________________________________________________
See Firewall Configuration for more information.
Page 18 of 199
3. CommServe Host Name or the CommServe IP
address:______________________________________
See Configuration of Other Installation Options for more information.
4. Client computer's Host name (NetBIOS name) or IP
address____________________________________
5. Job result folder
location:________________________________________________________________
If necessary, Name and Password for the specified
folder:_______________________________________
6. Storage Policy used by the default
subclient:________________________________________________
See Storage Policy Selection for more information.
7. Client Group to which this Client will be
associated:_____________________________________________
See Client Group Selection for more information.
8. Time and frequency for Install of Automatic
Updates:_________________________________________
See Schedule Automatic Update for more information.
Before You Begin
Log on to the client as local Administrator or as a member of the Administrators group on that
computer.
Install Procedure
Getting Started
1. Place the software installation disc for the Windows
platform into the disc drive.
After a few seconds, the installation program is
launched.
If the installation program does not launch
automatically:
Click the Start button on the Windows task bar, and
then click Run.
Browse to the installation disc drive, select
Setup.exe, click Open, then click OK.
NOTES
If you are installing on a x64 version of Windows
2008 Server Core R2, go to the AMD64 folder and
run Setup.exe.

2. In this screen, you choose the language you want to use
Page 19 of 199
during installation. Click the down arrow, select the
desired language from the pull-down list, and click Next
to continue.
3. Select the option to install software.
NOTES
This screen will only appear when the
bAllow32BitInstallOn64Bit registry key has been
created and enabled on this computer.

4. Select the option to install software on this computer.
NOTES
The options that appear on this screen depend on the
computer in which the software is being installed.

5. Read the Welcome screen.
Click Next to continue, if no other applications are
running.

6. Read the virus scanning software warning.
Click OK to continue, if virus scanning software is
disabled.

7. Read the license agreement, then select I accept the
terms in the license agreement.
Click Next to continue.

8. Select the component(s) to install.
NOTES
Your screen may look different from the example
shown.
Components that either have already been
installed, or which cannot be installed, will be
dimmed. Hover over the component for
additional details.
The Special Registry Keys In Use field will be
enabled when GalaxyInstallerFlags registry
keys have been enabled on this computer. Hover
over the field to see which keys have been set,
as well as their values. For more information, see
Registry Keys.
To install the Oracle iDataAgent expand the Client
Modules folder, the iDataAgents folder, and the
Database Agents folder then select the following:
iDA for Oracle
When you select the Oracle iDataAgent for install,
the appropriate Windows File System iDataAgent is
automatically selected for install.
Page 20 of 199
9. Specify the location where you want to install the
software.
NOTES
Do not install the software to a mapped network
drive.
Do not use the following characters when
specifying the destination path:
/ : * ? " < > |
It is recommended that you use alphanumeric
characters only.
If you intend to install other components on this
computer, the selected installation directory will
be automatically used for that software as well.
If a component has already been installed, this
screen may not be displayed if the installer can
use the same install location as previously used.
If you intend to use the SnapProtect
feature
for Windows File System iDataAgent, the agent
should be installed on a non-system drive and
not a filer volume.
Click Browse to change directories.
10. Select from the following:
If this Client communicates with the CommServe
Server and/or MediaAgent across a firewall,
select Yes, configure firewall services, and
then click Next to continue. Proceed to the next
Step.
If firewall configuration is not required, click No,
do not configure firewall services and then
click Next to continue. Proceed to the next
section.
NOTES
Operating systems, such as Windows 2008 and
Windows Vista, may have more than one profile
present. When you select No to configure
firewall services, verify that firewall settings are
not enabled in the profile(s).
If the system detects firewall settings are
present in the profile(s), you must select from
the following:
Disable firewall for ALL profiles: Employ
caution when choosing this option; firewall
settings will be disabled in all profiles. This
requires a system reboot; installation
automatically resumes after reboot.
No, Firewall is not enabled: Select this
option if your firewall settings allow
communication with the CommServe
Page 21 of 199
computer.
Click Back to configure firewall services.
11. Click the Specify list of machine across the
firewall option and then specify the list of hosts
separated from this computer by a firewall. Make
sure you correctly describe whether the firewall
allows two-way communication (but on a limited
range of ports), or one-way communication (with
either only remote host being able to make
connections to this computer, or vice versa).
For all one-way firewalls allowing incoming
connections and those one-way firewalls allowing
outgoing connections without additional port
filtering, skip this step.
NOTES
Consider the following:
On the CommServe Server, this list should
include all the MediaAgents and Clients that
are on the other side of the firewall.
On the MediaAgents/Clients this should
include the CommServe computer, and any
other Clients/MediaAgents on the other side of
the firewall with which communications will be
established.
For each machine on the other side of the
firewall that you want to configure, choose the
type of firewall configuration based on the
firewall setup in your environment. Choose from
the following options:
Click on 2-way firewall if you can open
certain ports as bi-directional ports.
Click 1-way firewall; host is reachable
from this machine on the machine that is on
the secure side of the firewall.
Click 1-way firewall; host is NOT
reachable from this machine on the
machine that is on the public / DMZ side of
the firewall.
If you wish to communicate with computers in a
clustered environment, ensure that you add the
Host Name/IP Address of all physical nodes in
the cluster (even if no CommCell components
are installed) and all the virtual nodes in which
CommCell components are installed.
Type the host name or the IP address and the
GxCVD port number of the host name, and click
Add to place it in the Host Name/IP Address List.
12. Click the Specify list of restricted open ports
option and then specify the port range. Add the
starting and ending port range and then click Add
to place it in the Open Port List. Repeat as
needed.
Page 22 of 199
If firewall separating this computer from others
allows incoming connections, but these connections
can be made only on a limited set of ports, then
configure the appropriate port range here. For all
other scenarios, skip this step.
Note that if you do not specify hostname(s) as well
as port number(s), then the firewall services will not
be configured.
NOTES
Typically in a two-way firewall, the open ports
must be indicated for all computers. In a one-
way firewall, the ports must be specified on
computers in the open side, if they are open in a
restricted way. Note that the port ranges are not
required for computers that are fully closed in
the one-way firewall. For example, laptops which
are configured as clients in the Workstation
Backup Agent.
In a clustered environment, make sure the
firewall ports specified here are open for
communication on all the physical nodes as well
as the virtual nodes.
13. If desired, modify the Keep Alive interval.
14. Optionally, select Advanced Firewall
Configuration and specify a local host name
interface to use for outgoing tunnel connections
through the firewall. Otherwise, the interface and
port is automatically selected for you by the OS.
15. If desired, modify the Tunnel Initialization interval.
Page 23 of 199
16. Enter the fully qualified domain name of the
CommServe computer. (TCP/IP network name. e.g.,
computer.company.com)
NOTES
Do not use spaces when specifying a new name
for the CommServe Host Name.
screen will not be displayed; instead, the
installer will use the same Server Name as
previously specified.
17. Enter the username and password information for
an external domain user account or a CommCell
user account. This authorizes the installation of an
agent on the CommCell.
NOTES
This window is only displayed when the Require
Authentication for Agent Installation option
is selected in the CommCell Properties. Users
must belong to a User Group with Administrative
Management capabilities to enable this feature.
For more information, see Authentication for
Agent Installs.
18. Enter the following:
The local (NetBIOS) name of the client
computer.
The TCP/IP IP host name of the NIC that the
client computer must use to communicate with
the CommServe Server.
NOTES
Do not use spaces when specifying a new name
for the Client.
Page 24 of 199
The default network interface name of the client
computer is displayed if the computer has only
one network interface. If the computer has
multiple network interfaces, enter the interface
name that is preferred for communication with
screen will not be displayed; instead, the install
program will use the same name as previously
specified.
19. Specify the following and click Next to continue:
Type the location of the client's job results
directory, or click Browse.
NOTES
The Agent uses the job results directory to store
the client's backup and restore job results.
20. Select the storage policy through which you want to
back up/archive the indicated component (subclient,
instance, etc.)
NOTES
A storage policy directs backup data to a media
library. Each library has a default storage policy.
When you install an Agent, the install program
creates a default subclient for most Agents.
If desired, you can change your storage policy
selection at any time after you have installed the
client software.
If applicable, enable Global Filters for the default
subclient.
If this screen appears more than once, it is
because you have selected multiple agents for
installation and are configuring storage policy
association for each of the installed agents.
21. Select a Client Group from the list.
Page 25 of 199
NOTES
This screen will be displayed only if Client Groups
are configured in the CommCell Console. For
more information, see Client Computer Groups.
22. Make sure that all Oracle Instances are shut down
before continuing. If necessary, click Service
Control Manager to stop the Oracle services. After
all Oracle Instances have been shut down, click
Next to continue.
23. Click Search ORASBT.DLL to search all locations
specified in the SYSTEM PATH environment variable
to find any occurrences of the ORASBT.DLL file. For
all occurrences that are found, you need to either
rename or delete these occurrences so that the
Oracle Database iDataAgent can use the correct
ORASBT.DLL. After renaming or deleting all
occurrences of this DLL, click Next to continue.
24. Select Download Pack(s) and Install to
download and install the latest service packs and
post packs from the software provider.
NOTES
Internet connectivity is required to download
updates.
This step is applicable when installing on the first
instance.
Updates are downloaded to the following
Page 26 of 199
directory:
<software
installation>/Base/Temp/DownloadedPacks.
They are launched silently and installed
automatically for the first instance.

25. Verify the summary of selected options.
NOTES
The Summary on your screen should reflect the
components you selected for install, and may
look different from the example shown.
Click Next to continue or Back to change any of
the options.
The install program now starts copying the software
to the computer. This step may take several
minutes to complete.
26. The System Reboot message may be displayed. If
so, select one of the following:
Skip Reboot
This option will be displayed if the install
program finds any files belonging to other
applications, that need to be replaced. As these
files are not critical for this installation, you may
skip the reboot and continue the installation and
reboot the computer at a later time.
Reboot Now
If this option is displayed without the Skip
Reboot option, the install program has found
files required by the software that are in use and
need to be replaced. If Reboot Now is displayed
without the Skip Reboot option, reboot the
computer at this point. The install program will
automatically continue after the reboot.
Exit Setup
If you want to exit the install program, click Exit
Setup.
27. If necessary, select this option to schedule an
automatic installation of software updates.
Page 27 of 199
NOTES
Install Updates Schedule allows automatic
installation of the necessary software updates on
the computer on a single or weekly basis. If you
do not select this option, you can schedule these
updates later from the CommCell Console.
To avoid conflict, do not schedule the automatic
installation of software updates to occur at the
same time as the automatic FTP downloading of
software updates.
You may be prompted to reboot the computer
before restarting services.
installer will use the same option as previously
specified.
28. Setup reminds you that the computer must be
restarted, after the installation completes, before
you can use this Agent.
Click OK to continue.
29. If you are installing/upgrading the software on the
physical node in a clustered environment, use this
option to install/upgrade the software on the
remaining physical nodes of the cluster.
To install/upgrade the software on the remaining
nodes of the cluster, click Yes.
To complete the install/upgrade for this node
only, click No.
See Install/Upgrade Remaining Cluster Nodes for
step-by-step instructions.
Setup Complete
30. Click Next to continue.
NOTES
Schedules help ensure that the data protection
operations for the Agent are automatically
performed on a regular basis without user
intervention. For more information, see
Scheduling.
Page 28 of 199
If the Reboot Now button is displayed, a reboot
is required before you can use the software. You
can click this button to restart the computer
now, or choose to perform the restart at another
time. If the Reboot Now button is not
displayed, it will not be necessary to restart the
computer.
Click Finish to exit the program.
NOTES
The Setup Complete message displayed on
your screen will reflect the components you
installed/upgraded, and may look different from
the example shown.
If you install an Agent with the CommCell
Console open, you need to refresh the CommCell
Console (F5) to see the new Agents.
This procedure is now complete.
General
Install post-release updates or Service Packs that may have been released after the release of the
software. If you are installing a Service Pack, verify and ensure that it is the same version as the one
installed in the CommServe Server. Alternatively, you can enable Automatic Updates for quick and
easy installation of updates in the CommCell component.
After installing the Agent, you may want to configure the Agent before running a data protection
operation. The following list includes some of the most common features that can be configured:
Configure your subclients - see Subclients for more information.
Schedule your data protection operations - see Scheduling for more information.
Configure Alerts - See Alerts and Monitoring for more information.
Schedule Reports - See Reports for more information.
The software provides many more features that you will find useful. See the Index for a complete list of
supported features.
Agent Specific
Before you can begin using the Oracle iDataAgent for data protection operations, you must Create an
Instance.
To plan for a full system restore of the Oracle database in the event of a destroyed or damaged
client, we recommend that you configure the client for disaster recovery by including the Oracle
database files in your file system backups. Refer to Disaster Recovery Considerations for more
information and procedures.
Page 29 of 199
Install the Oracle iDataAgent - Windows - Clustered
Environment - Virtual Server
Install Checklist
Before You Begin
Install Procedure
Getting Started
Cluster Selection
Setup Complete
The Windows File System iDataAgent must be first installed onto all of the physical nodes of the cluster.
See Install the Microsoft Windows File System iDataAgent if you have not installed it on all of the
physical nodes. Once it has been installed onto the physical nodes, the Oracle iDataAgent and the
Windows File System iDataAgent can be installed from the active node to the virtual server using the
following procedure. The software can also be automatically installed on all available passive nodes
when the software is installed onto the virtual server, or you can choose to install any passive node(s)
separately.
For an overview of deploying the software components in a clustered environment, see Clustering
Support.
Verify that all of the computers to which software will be installed satisfy the minimum requirements
specified in System Requirements - Oracle iDataAgent and in System Requirements - Microsoft Windows
File System iDataAgent.
The following procedure describes the steps involved in installing the Oracle iDataAgent and the
Windows File System iDataAgent. If you choose to install additional components simultaneously, refer to
the appropriate procedures for installation requirements and steps specific to the component. Note that
when you install multiple components, the sequence of the install steps may vary.
General
Agents should be installed only after the CommServe and at least one MediaAgent have been. Also,
keep in mind that the CommServe
software and MediaAgent must be installed and running (but not

necessarily on the same computer), before you can install the Agent.
This software should be installed in a CommCell component with current versions of the CommServe
Server and MediaAgent software.
Page 30 of 199
Close all applications and disable any programs that run automatically, including anti-virus, screen
savers and operating system utilities. Some of the programs, including many anti-virus programs,
may be running as a service. Stop and disable such services before you begin. You can re-enable
them after the installation.
Ensure there is an available license on the CommServe software for the Agent.
operating system.
Firewall
If the CommServe

If a MediaAgent or Client on a Microsoft Windows MSCS virtual server needs to communicate with
other CommCell components across a firewall, you must:
Install File System iDataAgent or MediaAgent on all the physical nodes of the cluster. During the
installation, use the firewall related prompts to establish the firewall settings required by the
software to communicate across the firewall.
Then install the software components on the virtual nodes. (It is not necessary to configure the
firewall settings again in the virtual nodes.)
If the cluster communicates with the CommServe across a one-way firewall, you must add both the
physical and virtual nodes' host names (or the IP addresses) in the CommServe computer before
installing the software.
Cluster
Check the following on the cluster computer in which you wish to install the software:
Cluster software is installed and running.
Active and passive nodes are available.
Disk array devices configured with access to the shared array.
Public Network Interface Card is bound first, before the private Network Interface Card. (Does not
apply to NetWare Cluster.)
Prior to installing the Oracle iDataAgent on a virtual server that does not have the required cluster
resource type (i.e., Oracle Failsafe) in Windows Cluster Administrator, you must use the
bAllowOracleOnVmWithoutFailsafe registry key to bypass this requirement and enable the Oracle
iDataAgent option on the platform selection screen for this configuration.
Reboot Required
A reboot will be required after installation, before you can use this Agent.
Agent Specific
Page 31 of 199
Although the File System iDataAgent is a prerequisite, you do not have to install it separately. The
Oracle iDataAgent installation program checks for the File System iDataAgent and installs it
automatically if it is not installed.
A reboot will be required after install/upgrade to initialize the QSnap driver, before you can use this
Agent.
Install Checklist
1. Name of the disk group in which the virtual server resides
____________________________________
See Cluster Selection for more information.
2. Install folder
location:________________________________________________________________
See Select Components for Installation for more information.
Firewall ports:
______________________________________________________________________
Keep Alive Interval
minutes:____________________________________________________________
connections:_________________________________________________
seconds:_____________________________________________________
4. Client computer's Host name (NetBIOS name) or IP
address____________________________________
5. CommServe Host Name or the CommServe IP
address:______________________________________
6. Job result folder
location:________________________________________________________________
If necessary, Name and Password for the specified
folder:_______________________________________
subclient:________________________________________________
Page 32 of 199
associated:_____________________________________________
9. Time and frequency for Install of Automatic
Updates:_________________________________________
See Schedule Automatic Update for more information.
Before You Begin
Log on to the active node as the Domain User with administrative privileges to all nodes on the
cluster.
Install Procedure
Getting Started
1. Place the software installation disc for the Windows
After a few seconds, the installation program is
launched.
If the installation program does not launch
automatically:
Click the Start button on the Windows task bar, and
then click Run.
Browse to the installation disc drive, select
Setup.exe, click Open, then click OK.
NOTES
If remotely installing to other physical nodes of the
cluster, ensure you mount the software installation
disc on a UNC path or a shared location (e.g.,
\\machine_name\shared_directory_name).

2. In this screen, you choose the language you want to use
during installation. Click the down arrow, select the
desired language from the pull-down list, and click Next
to continue.

3. Select the option to install software.
NOTES
This screen will only appear when the
bAllow32BitInstallOn64Bit registry key has been
created and enabled on this computer.

4. Select the option to install software on this computer.
NOTES
The options that appear on this screen depend on the
computer in which the software is being installed.

5. Read the Welcome screen.
Click Next to continue, if no other applications are

Page 33 of 199
running.
6. Read the virus scanning software warning.
Click OK to continue, if virus scanning software is
disabled.

7. Read the license agreement, then select I accept the
terms in the license agreement.

Cluster Selection
8. Select Configure a Virtual Server.
9. Select the disk group in which the virtual server resides.
10. Select the component(s) to install.
NOTES
Your screen may look different from the
example shown.
Components that either have already been
installed, or which cannot be installed, will be
dimmed. Hover over the component for
additional details.
The Special Registry Keys In Use field will
be enabled when GalaxyInstallerFlags
registry keys have been enabled on this
Page 34 of 199
computer. Hover over the field to see which
keys have been set, as well as their values.
For more information, see Registry Keys.
To install the Oracle iDataAgent expand the
Client Modules folder, the iDataAgents folder,
and the Database Agents folder then select the
following:
iDA for Oracle
When you select the Oracle iDataAgent for install,
the appropriate Windows File System iDataAgent
is automatically selected for install.
11. Specify the location where you want to install the
software.
NOTES
Do not install the software to a mapped
network drive.
Do not use the following characters when
specifying the destination path:
/ : * ? " < > |
It is recommended that you use alphanumeric
characters only.
If you intend to install other components on
this computer, the selected installation
directory will be automatically used for that
software as well.
screen may not be displayed if the installer can
use the same install location as previously
used.
If you intend to use the SnapProtect
feature
for Windows File System iDataAgent, the agent
should be installed on a non-system drive and
not a filer volume.
Click Browse to change directories.
Proprietary disk resources will not appear in the browse window. To install to a proprietary disk
resource, manually enter the path.
After installing to a proprietary disk resource, the error message CVD failed to set
dependency may be generated. To set the dependency, open the Cluster Administrator and
select the CVD that has just been installed. Click on the Properties Dependencies tab, and
click Modify. Select the proprietary disk resource and click OK.
Do not select the same destination drive in which the MSCS resides.
If this Client communicates with the
CommServe Server and/or MediaAgent across
Page 35 of 199
a firewall, select Yes, configure firewall
services, and then click Next to continue.
Proceed to the next Step.
If firewall configuration is not required, click
No, do not configure firewall services and
then click Next to continue. Proceed to the
next section.
NOTES
Operating systems, such as Windows 2008 and
Windows Vista, may have more than one
profile present. When you select No to
configure firewall services, verify that firewall
settings are not enabled in the profile(s).
If the system detects firewall settings are
present in the profile(s), you must select from
the following:
Disable firewall for ALL profiles: Employ
caution when choosing this option; firewall
settings will be disabled in all profiles. This
requires a system reboot; installation
automatically resumes after reboot.
No, Firewall is not enabled: Select this
option if your firewall settings allow
communication with the CommServe
computer.
Click Back to configure firewall services.
13. Click the Specify list of machine across the
firewall option and then specify the list of hosts
separated from this computer by a firewall. Make
sure you correctly describe whether the firewall
allows two-way communication (but on a limited
range of ports), or one-way communication (with
either only remote host being able to make
connections to this computer, or vice versa).
For all one-way firewalls allowing incoming
connections and those one-way firewalls allowing
outgoing connections without additional port
filtering, skip this step.
NOTES
Consider the following:
On the CommServe Server, this list should
include all the MediaAgents and Clients that
are on the other side of the firewall.
On the MediaAgents/Clients this should
include the CommServe computer, and any
other Clients/MediaAgents on the other side
of the firewall with which communications
will be established.
For each machine on the other side of the
firewall that you want to configure, choose the
type of firewall configuration based on the
firewall setup in your environment. Choose
Page 36 of 199
from the following options:
Click on 2-way firewall if you can open
certain ports as bi-directional ports.
Click 1-way firewall; host is reachable
from this machine on the machine that is
on the secure side of the firewall.
Click 1-way firewall; host is NOT
reachable from this machine on the
machine that is on the public / DMZ side of
the firewall.
If you wish to communicate with computers in
a clustered environment, ensure that you add
the Host Name/IP Address of all physical nodes
in the cluster (even if no CommCell
components are installed) and all the virtual
nodes in which CommCell components are
installed.
Type the host name or the IP address and the
GxCVD port number of the host name, and
click Add to place it in the Host Name/IP
Address List.
14. Click the Specify list of restricted open ports
option and then specify the port range. Add the
starting and ending port range and then click Add
to place it in the Open Port List. Repeat as
needed.
If firewall separating this computer from others
allows incoming connections, but these
connections can be made only on a limited set of
ports, then configure the appropriate port range
here. For all other scenarios, skip this step.
Note that if you do not specify hostname(s) as
well as port number(s), then the firewall services
will not be configured.
NOTES
Typically in a two-way firewall, the open ports
must be indicated for all computers. In a one-
way firewall, the ports must be specified on
computers in the open side, if they are open in
a restricted way. Note that the port ranges are
not required for computers that are fully closed
in the one-way firewall. For example, laptops
which are configured as clients in the
Workstation Backup Agent.
In a clustered environment, make sure the
firewall ports specified here are open for
communication on all the physical nodes as
well as the virtual nodes.
15. If desired, modify the Keep Alive interval.
Page 37 of 199
16. Optionally, select Advanced Firewall
Configuration and specify a local host name
interface to use for outgoing tunnel connections
through the firewall. Otherwise, the interface and
port is automatically selected for you by the OS.
17. If desired, modify the Tunnel Initialization
interval.

If any of the above prompts for firewall configuration is not displayed, you must configure
communication across firewall(s) using the Firewall Configuration Wizard before running
any operations on this computer. (See Configure or Modify Firewall Settings on Windows
Computers for step-by-step instructions on using the Firewall Configuration Wizard.)
18. Enter the fully qualified domain name of the
CommServe computer. (TCP/IP network name.
e.g., computer.company.com)
NOTES
Page 38 of 199
Do not use spaces when specifying a new
name for the CommServe Host Name.
installer will use the same Server Name as
19. Enter the username and password information
for an external domain user account or a
CommCell user account. This authorizes the
installation of an agent on the CommCell.
NOTES
This window is only displayed when the
Require Authentication for Agent
Installation option is selected in the
CommCell Properties. Users must belong to a
User Group with Administrative Management
capabilities to enable this feature. For more
information, see Authentication for Agent
Installs.
20. Enter the following:
The local (NetBIOS) name of the client
computer.
The TCP/IP IP host name of the NIC that the
client computer must use to communicate with
NOTES
Do not use spaces when specifying a new
name for the Client.
The default network interface name of the
client computer is displayed if the computer
has only one network interface. If the
computer has multiple network interfaces,
enter the interface name that is preferred for
communication with the CommServe Server.
install program will use the same name as
21. Specify the following and click Next to continue:
Type the location of the client's job results
directory, or click Browse.
Page 39 of 199
NOTES
The Agent uses the job results directory to
store the client's backup and restore job
results.
22. Select the storage policy through which you want
to back up/archive the indicated component
(subclient, instance, etc.)
NOTES
A storage policy directs backup data to a
media library. Each library has a default
storage policy.
When you install an Agent, the install program
creates a default subclient for most Agents.
If desired, you can change your storage policy
selection at any time after you have installed
the client software.
If applicable, enable Global Filters for the
default subclient.
If this screen appears more than once, it is
because you have selected multiple agents for
installation and are configuring storage policy
association for each of the installed agents.
23. Select a Client Group from the list.
NOTES
This screen will be displayed only if Client
Groups are configured in the CommCell
Console. For more information, see Client
Computer Groups.
Page 40 of 199
24. If you have Oracle FailSafe configured for your
clustered environment, then use Oracle FailSafe
Manager to shut down the instance before
continuing with the install. If your site is not
configured for Oracle FailSafe, then you can
disregard this message.
25. Make sure that all Oracle Instances are shut down
before continuing. If necessary, click Service
Control Manager to stop the Oracle services.
After all Oracle Instances have been shut down,
click Next to continue.
26. Click Search ORASBT.DLL to search all locations
specified in the SYSTEM PATH environment
variable to find any occurrences of the
ORASBT.DLL file. For all occurrences that are
found, you need to either rename or delete these
occurrences so that the Oracle Database
iDataAgent can use the correct ORASBT.DLL.
After renaming or deleting all occurrences of this
DLL, click Next to continue.
27. Select Download Pack(s) and Install to
download and install the latest service packs and
post packs from the software provider.
NOTES
Internet connectivity is required to download
updates.
This step is applicable when installing on the
first instance.
Updates are downloaded to the following
directory:
<software
installation>/Base/Temp/DownloadedPacks.

They are launched silently and installed
automatically for the first instance.
Page 41 of 199

28. Verify the summary of selected options.
NOTES
The Summary on your screen should reflect
the components you selected for install, and
may look different from the example shown.
Click Next to continue or Back to change any of
the options.
The install program now starts copying the
software to the computer. This step may take
several minutes to complete.
29. The System Reboot message may be displayed. If
so, select one of the following:
Skip Reboot
This option will be displayed if the install
program finds any files belonging to other
applications, that need to be replaced. As
these files are not critical for this installation,
you may skip the reboot and continue the
installation and reboot the computer at a later
time.
Reboot Now
If this option is displayed without the Skip
Reboot option, the install program has found
files required by the software that are in use
and need to be replaced. If Reboot Now is
displayed without the Skip Reboot option,
reboot the computer at this point. The install
program will automatically continue after the
reboot.
Exit Setup
If you want to exit the install program, click
Exit Setup.
30. If necessary, select this option to schedule an
automatic installation of software updates.
NOTES
Install Updates Schedule allows automatic
installation of the necessary software updates
on the computer on a single or weekly basis. If
you do not select this option, you can schedule
these updates later from the CommCell
Console.
To avoid conflict, do not schedule the
Page 42 of 199
automatic installation of software updates to
occur at the same time as the automatic FTP
downloading of software updates.
You may be prompted to reboot the computer
before restarting services.
installer will use the same option as previously
specified.
31. Setup reminds you that the computer must be
restarted, after the installation completes, before
you can use this Agent.
32. To install/upgrade the software on the remaining
nodes of the cluster, click Yes.
To complete the install for this node only, click
No.
33. Select cluster nodes from the Preferred Nodes
list and click the arrow button to move them to
the Selected Nodes list.
NOTES
The list of Preferred Nodes displays all the
nodes found in the cluster; from this list you
should only select cluster nodes configured to
host this virtual server.
Do not select nodes that already have multiple
instances installed. For more information, see
Multi Instancing.
When you have completed your selections, click
Next to continue.
34. Type the User Name and Password for the
Domain Administrator account, so that the
installer can perform the remote install/upgrade
of the cluster nodes you selected in the previous
step.
Page 43 of 199
35. The progress of the remote install for the cluster
nodes is displayed; the install can be interrupted
if necessary.
Click Stop to prevent installation to any nodes
after the current ones complete.
Click Advanced Settings to specify any of the
following:
Maximum number of nodes on which Setup
can run simultaneously.
Time allocated for Setup to begin executing on
each node, after which the install attempt will
fail.
Time allocated for Setup to complete on each
node, after which the install attempt will fail.
NOTES
If, during the remote install of a cluster node,
setup fails to complete or is interrupted, you
must perform a local install on that node.
When you do, the install begins from where it
left off, or from the beginning if necessary. For
procedures, see Manually Installing the
Software on a Passive Node.
36. Read the summary for remote installation to
verify that all selected nodes were installed
successfully.
NOTES
If any node installation fails, you must
manually install the software on that node
once the current installation is complete. (See
Manually Installing the Software on a Passive
Node for step-by-step instructions.)
The message displayed on your screen will
reflect the status of the selected nodes, and
may look different from the example.
Setup Complete
Page 44 of 199
37. Click Next to continue.
NOTES
Schedules help ensure that the data protection
operations for the Agent are automatically
performed on a regular basis without user
intervention. For more information, see
Scheduling.
If the Reboot Now button is displayed, a
reboot is required before you can use the
software. You can click this button to restart
the computer now, or choose to perform the
restart at another time. If the Reboot Now
button is not displayed, it will not be necessary
to restart the computer.
Click Finish to exit the program.
NOTES
The Setup Complete message displayed on
your screen will reflect the components you
installed/upgraded, and may look different
from the example shown.
If you install an Agent with the CommCell
Console open, you need to refresh the
CommCell Console (F5) to see the new Agents.
This procedure is now complete.
General
supported features.
Agent Specific
Page 45 of 199
Instance.
Cluster
If the passive node was not available while installing the software, you must manually install the
software on the passive node now. (See Manually Installing the Software on a Passive Node for step-
by-step instructions.)
By default, a failure of MediaAgent or Agent software on the active node in a Windows, Veritas, or HP
Scalable NAS/PolyServe Cluster will not cause a failover to be initiated. For information on how to
change this default behavior, see Clustering Support - Failovers.

Page 46 of 199
Install the Oracle iDataAgent - Unix
Install Checklist
Before You Begin
Install Procedure
Getting Started
Base Software Installation
Base Software Installation (continued)
Kernel Parameters
Enable Global Filters
Setup Complete
The Oracle iDataAgent is installed on the computer on which the Oracle Database application resides.
(This computer is referred to as the Client computer in this install procedure.)
Verify that the computer in which you wish to install the software satisfies the minimum requirements
specified in System Requirements - Oracle iDataAgent and System Requirements - Unix File System
iDataAgent.
The following procedure describes the steps involved in installing the Oracle iDataAgent and the Unix
File System iDataAgent. If you choose to install multiple components simultaneously, refer to the
appropriate procedures for installation requirements and steps specific to the component. Note that
when you install multiple components, the sequence of the install steps may vary.
General
Agents should be installed only after the CommServe and at least one MediaAgent have been
installed in the CommCell. Also, keep in mind that the CommServe and MediaAgent must be installed
and running (but not necessarily on the same computer), before you can install the Agent.
This software should be installed in a CommCell with current versions of the CommServe and
MediaAgent software.
Ensure there is an available license on the CommServe for the Agent.
operating system.
Firewall
If the CommServe

Page 47 of 199
Package Management Systems
You can use the Red Hat Package Manager (RPM) package management system to install all Linux
versions of the agent. Also, you can use the Advanced Packaging Tool (APT) package management
system to install all Debian Linux versions of the agent. For step-by-step instructions, see Use the
Package Management System for Installs.
Red Hat Linux
Red Hat Linux will create an entry in the /etc/hosts file when it is first installed, in the following
format:
<ip_address> <host name> localhost
For example, if the host name of your computer is bluesky, the entry will look something like this:
192.168.1.111 bluesky localhost
If you have not already done so, edit the /etc/hosts file. The edited entry should look like this:
127.0.0.1 localhost
Depending upon your environment, and using the above example again, you may also need an entry
similar to this:
192.168.1.111 bluesky
Agent Specific
HP-UX
If you are installing on a HP-UX computer, you must manually mount the installation disc as
described in Mount the Software Installation Disc.
Install Checklist
1. Network host name:____________________________________
Client name:____________________________________
For example, green.domainname.com and green.
See Step 5 for more information.
2. Install directory
location:________________________________________________________________
Page 48 of 199
The default is /opt, but you may designate any location you want.
See Base Software Installation for more information.
3. Log files directory
location:________________________________________________________________
The default is /var/log, but you may designate any location you want.
4. Network TCP port number for the Communications Service
(CVD):_____________________________
Network TCP port number for the Client Event Manager Service
(EvMgrC):___________________________
Firewall ports:
______________________________________________________________________
Keep Alive Interval
minutes:____________________________________________________________
connections:_________________________________________________
seconds:_____________________________________________________
6. CommServe Name and the CommServe Host
Name:______________________________________
For example, orange and orange.domainname.com.
See Base Software Installation (continued) for more information.
7. Job result directory
location:________________________________________________________________
8. Number of Streams___________________________________________________
See Kernel Parameters for more information.
subclient:________________________________________________
associated:_____________________________________________
Before You Begin
Page 49 of 199
Log on to the client as root.
The install package requires super-user permissions to execute.
Install Procedure
Getting Started
1. Place the software installation disc for the Unix platform
into the disc drive.
You can also install the product using a disc drive
mounted on another computer on the network.
On Solaris, double-click the cvpkgadd program
from the File Manager window.
On other Unix platforms, open the Terminal window,
navigate to the software installation disc and then
enter cvpkgadd.

2. The product banner and other information is displayed.
Press Enter to continue.

3. Read the license agreement. Type y and press Enter to
continue.

4. This prompt is displayed only when you are installing
on HP-UX, Linux, or Solaris computers.
Press Enter to continue
NOTES
When you install on non-clustered computer, you
must select the number associated with the option
Install on a physical machine.
Certain Data Protection Suite
packages can be associated with a
virtual IP, or in other words,
installed on a "virtual machine"
belonging to some cluster. At any
given time the virtual machine's
services and IP address are active
on only one of the cluster's
servers. The virtual machine can
"fail-over" from one server to
another, which includes stopping
services and deactivating IP
address on the first server and
activating the IP address/services
on the other server.
You now have a choice of performing
a regular Data Protection Suite
install on the physical host or
installing Data Protection Suite on
a virtual machine for operation
within a cluster.
Most users should select "Install
on a physical machine" here.
1) Install on a physical machine
2) Install on a virtual machine
3) Exit
Your choice: [1]
5. If you have only one network interface, press Enter to
accept the default network interface name and
Network interface with the
following IPs have been found
Page 50 of 199
continue.
If you have multiple network interfaces, enter the
number corresponding to the network interface that
you wish to use as default, and then press Enter to
continue.
NOTES
The interface name and IP addresses depend on the
computer in which the software is installed and may
be different from the example shown.
available on your system. One of
these interfaces should be
associated with the physical
machine being installed. It will
also be used by the CommServe to
initiate connections to the
physical machine. Note that you
will be able to additionally
customize Datapipe Interface Pairs
used for the backup data traffic
later in the Data Protection Suite
Java GUI.
Please select the correct network
interface below.
1) client (201.42.33.598)
2) hk97::489:9glg:hk8d:9490
3) client.company.com
(hr90:8842:2:78:013:8ghh:hg8k:9x54)
Interface number: [1]
If you have multiple network interfaces, enter the
number corresponding to the network interface that
you wish to use as default, and then press Enter to
continue.
NOTES
The interface name and IP addresses depend on the
computer in which the software is installed and may
be different from the example shown.
When configuring an Oracle RAC iDataAgent, make
sure that the network interface or host name you
choose is same as the one configured in the
database, or else the RAC configuration will fail.
Network interfaces with the
following IPs have been found
configured on your system. Please
select one to be used by the
CommServe to contact the client.
1) dunk.company.com (480.19.65.333)
2) 480.19.66.326
Verify the default network interface name.
Press Enter to accept the default network interface
name and continue, or
Type the default network interface name, and then
press Enter to continue.
NOTES
This prompt will be displayed only when you have
multiple network interfaces for the computer.
Please verify the physical machine
interface name below. Make it as
complete (with fully qualified
domain name) as possible:
Physical Machine Host Name:
[angel.company.com]
6. Specify the client name for the computer.
Press Enter to accept the default name and continue,
or
Enter a new client name for the computer and then
Please specify the client name for
this machine. It does not have to
be the network host name: you can
enter any word here without spaces.
The only requirement is that it
must be unique on the CommServe.
Client name: [angel]
7. Enter the number
corresponding to the
CVGxOrIDA module.
Install Data Protection Suite on physical machine
client.company.com
Select the Data Protection Suite module that you would
Page 51 of 199
NOTES
Your screen may look
different from the
example shown.
Components that either
have already been
installed, or which cannot
be installed, will not be
shown.
In addition, the list of
modules that appear
depends on the specific
Unix File System in which
the package is installed.
(e.g., CVGxWA will
appear only when the
installation package is
run on a Solaris
computer.)
like to install
1) Media Agent <= CVGxMA
2) FileSystem iDataAgent <= CVGxIDA
3) Exit this menu
Module number: [1]
If this is the first package
to be installed on the
computer, press Enter to
continue.
If this is NOT the first
package to be installed
on the computer, this
screen will not be
displayed. Skip to
Storage Policy Selection.
Here is a list and status of the dependent modules:
1) Data Protection Suite Base0
Module NOT installed
2) Data Protection Suite Base
If there are any modules listed as NOT
installed/upgraded, they will be installed/upgraded
first.
Press <ENTER> to proceed ...
9. Specify the location where
you want to install the
software.
NOTES
The amount of free space
required depends on the
components selected for
install, and may look
different from the
example shown.
Press Enter to accept the
default path and continue,
or
Enter a path and then press
Enter to continue.
Press Enter again to
confirm the path.
Please specify where you want us to install Data
Protection Suite binaries.
It must be a local directory and there should be at least
209MB of free space available. All files will be
installed in a "hds" subdirectory, so if you enter
"/opt", the files will actually be placed into
"/opt/hds".
Installation Directory: [/opt]
..
Data Protection Suite will be installed in /opt/hds.
Press ENTER to continue ...
10. Specify the location for the
Please specify where you want to keep Data Protection
Page 52 of 199
log files.
NOTES
All the modules installed
on the computer will
store the log files in this
directory.
different from the
example shown.
or
Enter to continue.
confirm the path.
Suite log files.
100MB of free space available. All log files will be
created in a "hds/Log_Files" subdirectory, so if you
enter "/var/log", the logs will actually be placed into
"/var/log/hds/Log_Files".
Log Directory: [/var/log]
..
Data Protection Suite log files will be created
in /var/log/hds/Log_Files.
11. Indicate whether you would
like to launch processes with
inherent database access
rights.
Press Enter to assign a new
group, or
Type No and then press
Enter to continue.
Most of Data Protection Suite processes run with root
privileges, but some are launched by databases and
inherit database access rights. To make sure that
registry and log files can be written to by both kinds of
processes we can either make such files world-writeable
or we can grant write access only to processes belonging
to a particular group, e.g. a "hds" or a "dba" group.
We highly recommend now that you create a new user group
and enter its name in the next setup screen. If you
choose not to assign a dedicated group to Data Protection
Suite processes, all temporary and configuration files
will be created with -rw-rw-rw permissions.
If you're planning to backup Oracle DB you should use
"dba" group.
Would you like to assign a specific group to Data
Protection Suite? [yes]
12. If you indicated Yes in the
previous step, you will be
prompted for the group
name that must be used to
launch processes.
Enter the group name and
then press Enter to
continue.
continue.
For installs on a Solaris
computer, proceed to the
next step. Otherwise, skip to
Please enter the name of the group which will be assigned
to all Data Protection Suite files and on behalf of which
all Data Protection Suite processes will run.
In most of the cases it's a good idea to create a
dedicated "hds" group. However, if you're planning to use
Oracle iDataAgent or SAP Agent, you should enter Oracle's
"dba" group here.
Group name: dba
REMINDER
If you are planning to install Data Protection Suite
Informix, DB2, Sybase or Lotus Notes iDataAgent, please
make sure to include Informix, DB2, etc. users into group
"dba".
Press <ENTER> to continue ...
13. Type a network TCP port
number for the
Every instance of Data Protection Suite should use a
unique set of network ports to avoid interfering with
Page 53 of 199
Communications Service
(CVD) and press Enter.
Type a network TCP port
number for the Client Event
Manager Service (EvMgrC)
and press Enter.
NOTES
For more information
about Network TCP Ports,
see Network TCP Port
Requirements.
about these services, see
Services.
other instances running on the same machine.
The port numbers selected must be from the reserved port
number range and have not been registered by another
application on this machine.

Please enter the port numbers.

Port Number for CVD : [8400]

Port Number for EvMgrC: [8402]
14. If this computer
communicates with the
CommServe, MediaAgent
and/or other clients across a
firewall, type Yes, and then
Press Enter, if you do not
wish to configure the firewall
services. Proceed to the
next section.
Various Data Protection Suite components need to
communicate with each other: iDataAgents and MediaAgents
establish connections to CommServe and talk to each other
as well. If any of the involved parties are situated on
the opposite sides of a firewall, Data Protection Suite
should be made aware of it so that it could bind its
pipeline sockets to open ports and could establish
tunnels for control traffic.

You must configure Data Protection Suite firewall
services if there are other Data Protection Suite
machines, which are expected to communicate with this
one.

Do you want to configure Data Protection Suite firewall
services? [no]
15. Enter the port range(s), and
then press Enter to
continue.
NOTES
Specify the range of
ports that must be used
for communication
between the Client and
CommServe and/or
MediaAgent computers.
For more information on
the port requirements,
see Port Requirements
for Two-way Firewall or
Port Requirements for
One-way Firewall, as
applicable.
Data Protection Suite needs to know which TCP ports of
this machine are available for connections initiated by
machines on the other side of the firewall.
If this machine is not reachable from the other side of
the firewall at all (because the FW is one-way and allows
only outgoing connections), enter any unused port number
here (e.g. 8600).
Otherwise please consult your FW configuration for the
list of open incoming ports and enter all of them here
(with the exception of port 8400).
Currently there are no ports configured. Please enter a
single port number or a port range (like 8600-8620) to be
added to the FW configuration:
Port range: [8600-8620]
16. Enter the number
corresponding to the option
you wish to perform.
NOTES
What would you like to do:
1) Add another open port or a range of ports
2) Delete an existing port or a range of ports
Page 54 of 199
If you choose option 1,
refer the previous step.
proceed to the next step.
3) Continue with the firewalled host setup
Your choice: [3]
17. Enter the host name(s) of
the computers that will need
to be contacted through a
firewall, and then press
Enter to continue.
We need to know which Data Protection Suite hosts are
located on the other side of the firewall, and whether
the firewall will allow direct or reverse connections
to/from those hosts.
You can specify hosts by either entering their names, IP
addresses or name/IP wildcards. The wildcards are
available only if the firewall is symmetrical, i.e.
allows to open connections to certain ports both ways.
Currently there are no firewall hosts configured.
Please enter the name or IP address of a host on the
other side of the firewall. If the firewall is
symmetrical, you are allowed to use wildcards, i.e.
things like 192.168.* or *.firewall.company.com:
Firewalled Host: lavender.company.com
18. Choose the option
associated with type of
firewall configuration based
on the firewall setup in your
environment.
NOTES
Choose Two-way
(symmetrical) firewall
if you can open certain
ports as bi-directional
ports.
Choose One-way
firewall; <port> is
reachable from here if
this computer
communicates with
MediaAgent/Client on the
other side of the firewall.
Choose One-way
firewall; this machine
is reachable from
<port> when the
CommServe and any
Clients/MediaAgents)
communicates with this
computer.
Please specify the type of the firewall separating this
machine from 172.19.61.89.
1) Two-way (symmetrical) firewall
2) One-way firewall, 172.19.61.89 is reachable from
here
3) One-way firewall, this machine is reachable from
172.19.61.89
Your choice: [1]
NOTES
refer the previous two
steps.
1) Configure another host
2) Delete an existing host
3) Continue with the firewall keep-alive setup
Your choice: [3] 1
Page 55 of 199
20. If desired, modify the Keep
Alive interval, and then
press Enter to continue, or
default.
Please specify Keep Alive interval for Data Protection
Suite firewall services.
Many firewalls disconnect idle Network connections after
some period of time. Some of the Data Protection Suite
Services need continuous connections. Data Protection
Suite keeps such connections active by sending periodic
"keep-alive" packets.
Consult your firewall documentation, or contact your
Network Administrator, for the exact value after which
idle connections will be closed (snip time). Then enter a
value, which is at least one minute less than the snip
time.
Keep-alive interval, minutes [5]
21. To configure advanced
firewall settings, type Yes,
and then press Enter.
If you do not want to
configure advanced firewall
settings, type No, and then
press Enter. Proceed to the
next section.
The Generic part of the Data Protection Suite Firewall
Config has been completed successfully. There are some
additional advanced settings that you may want to review
now. All of them can be customized later by editing
the .properties file
under /etc/CommVaultRegistry/Galaxy/Instance003/Firewall.
Would you like to review the advanced settings now? [no]
22. To bind the local end of
tunnel connections to a
specified interface, type
Yes, and then press Enter.
If you do not want to bind
the local end of tunnel
connections to a specified
interface, type No, and then
press Enter. Skip the next
Step.
Normally Data Protection Suite Firewall code doesn't bind
local end of TCP/IP sockets when establishing outgoing
tunnel connections relying on the OS to pick correct
interface and arbitrary port automatically. Usually this
doesn't cause connectivity problems because we require
that the firewall must allow connections for as long as
1meither source or destination socket end is bound to one
of the ports in the open range.
Sometimes, however, on hosts with several NICs it's
important to force the OS to bind the local socket end to
a specific network interface. There is a Data Protection
Suite setting called 1mnBIND_BEFORE_CONNECT_IFACEm, which
enables this behavior. If present, Data Protection Suite
will bind the local end of tunnel connections to the
specified interface.
Would you like to configure nBIND_BEFORE_CONNECT_IFACE?
[no]
23. Type a number
corresponding to one of the
listed network interfaces, to
use for outgoing tunnel
connections through the
firewall.
Please select network interface that should be used for
all outgoing tunnel connections:
1) <ip_address>
24. If desired, modify the
Tunnel Initialization interval
by typing a number.
When tunnel to a destination machine cannot be
established because the machine is down or is not
accepting connections, Data Protection Suite will retry
the connection after some time. Tunnels piercing one-way
firewalls are 1mPERSISTENTm meaning that Data Protection
Page 56 of 199
Suite will keep on trying to initialize them until
success. These attempts can generate a lot of network
traffic if a central machine (e.g. CommServe) suddenly
goes down.
Here you can adjust the interval (called
1mnTUNNEL_INIT_INTERVALm in registry) between tunnel init
attempts.
Tunnel Init Interval, seconds, [5]
25. Type the name of the
CommServe computer and
NOTES
Ensure that the
CommServe is accessible
before typing the name;
otherwise the installation
will fail.
If you enter a short name
which resolves to the
same IP address as the
fully qualified
CommServe name, you
will be asked if you would
prefer to use the fully
qualified name.
Please enter the hostname of the Data Protection Suite
CommServe. It can be either short or long; the only
requirement is that it must be resolvable by the name
services configured on this machine.
CommServe Name:
26. Enter the username and
password information for
an external domain user
account or a CommCell user
account. This authorizes the
installation of an agent on
the CommCell.
NOTES
This is only displayed
when the
Authentication for
Agent feature is enabled
in the CommCell
Properties. Users must
belong to a User Group
with Agent Management
capabilities to enable this
feature. For more
information, see
Authentication for Agent
Installs.
Click Enter to continue.
Enter your CommCell user name and password:
User Name :
Password :
27. Specify the location of the
job results directory.
Please specify the name for the JobResults directory.
Page 57 of 199
NOTES
All the agent modules
installed on the computer
uses the job results
directory to store the
backup and restore job
results.
different from the
example shown.
or
Enter to continue.
20MB of free space available. It will be used to store
intermediate data that should be passed from one backup
phase to another.
JobResults Directory: [/test1]
Kernel Parameters
28. Enter the appropriate
number of streams, and
then press Enter to
continue, or
default number of streams
and continue.
NOTES
The number of streams
specified ensures that
concurrent
backup/restore streams
would have sufficient
system resources. For
more information on the
subject, see Configuring
Kernel Parameters
(Unix/Macintosh).
This prompt is relevant only
when you install/upgrade on
a Macintosh or Solaris
computer as appropriate.
Please enter the total number of streams that you plan to
run at the same time. We need to make sure that you have
enough semaphores and shared memory segments configured
in /etc/system.
Number of streams: [10]
like modifications to be
made to the /etc/system
configuration file.
Type Yes, and then press
Enter to automatically
update the file and continue,
or
default No and continue (if
you do not want to
We now need to modify the /etc/system configuration file
on this computer. It is done to make sure that there will
be enough shared memory and semaphores available for Data
Protection Suite programs.
Please review the changes below and answer "yes" if you
want us to apply them to the /etc/system file. Otherwise,
the installation will proceed, the changes will be saved
to some other file, and you will have to apply them
manually.
set shmsys:shminfo_shmmni=8570 (was 7930)
Page 58 of 199
automatically update the
file).
This prompt is displayed
only when you
install/upgrade on a Solaris
or Macintosh computer.
set shmsys:shminfo_shmseg=8420 (was 7780)
set semsys:seminfo_semmns=10320 (was 9680)
set semsys:seminfo_semmni=8570 (was 7930)
set semsys:seminfo_semmsl=8570(was 7930)
Do you want us to apply these changes now? [no]
Changes saved into /etc/system.gal.1744
Press <ENTER> to continue.
30. If you indicated No in the
previous step, the file to
which the changes have
been saved is displayed.
Make sure that these values
are established later to
ensure that all the
requirements for this setup
is satisfied.
NOTES
The settings that are
displayed are the
maximum or minimum
required settings. Value
640, which is provided
for various shared
memory segment or
semaphore requirements,
is a maximum value
based on 10 streams.
only when you
computer, in cases where
the install detects that the
computer does not have the
maximum or minimum
required shared memory
settings.
Although a no answer can be selected to this question
during install, the user should make sure the min
requirements (below) for shared memory are met, otherwise
the backups may fail (the message in logs is could not
start the pipeline).
set shmsys:shminfo_shmmax=4199304
set shmsys:shminfo_shmmin=1
set semsys:shminfo_shmmni=640
set semsys:shminfo_shmseg=640
set semsys:seminfo_semmns=640
set semsys:seminfo_semmni=640
set semsys:seminfo_semmsl=640
set maxusers=256
corresponding to the storage
policy through which you
want to back up the File
System iDataAgent and then
NOTES
A storage policy directs
backup data to a media
library. Each library has a
default storage policy.
When you install an
Agent, the install
Please select one storage policy for this IDA from the
list below:
1) SP_StandAloneLibrary2_2
2) SP_Library3_3
3) SP_MagLibrary4_4
4) fornax_fornax_HWCmp
5) ranger_ranger_HWCmp
6) fornax_fornax_ClntCmp
7) fornax_fornax_MACmp
8) fornax_fornax_NoCmp
Storage Policy: [3]
Page 59 of 199
program creates a
default subclient for most
Agents.
If desired, you can
change your storage
policy selection at any
time after you have
installed the client
software.
If this screen appears
more than once, it is
because you have
selected multiple agents
for installation and are
configuring storage policy
association for each of
the installed agents.
32. Type the appropriate
number for configuring
Global Filters for the default
subclient and press Enter to
continue.
NOTES
Select Use Cell level
Policy to inherit the
global filter policy
configuration set for the
CommCell, i.e., if the
Use Global Filters on
All Subclients option is
selected in the Global
Filters dialog box (from
the CommCell Consoles
Control Panel), then this
policy will be applied to
the default subclient as
well. If is not selected,
then the global filters will
not be applied to the
default subclient.
Select Always use
Global filters to always
apply the global filters
policy to the default
subclient regardless of
the policy set for the
CommCell.
Select Do not use
Global filters to
disregard applying the
global filters to the
default subclient
regardless of the policy
set for the CommCell.
Commcell Level Global Filters are set through Data
Protection Suite GUI's Control Panel in order to filter
out certain directories or files from backup Commcell-
widely. If you turn on the Global filters, they will be
effective to the default subclient. There are three
options you can choose to set the filters.
1) Use Cell level policy
2) Always use Global filters
3) Do not use Global filters
Please select how to set the Global Filters for the
default subclient? [1]
Page 60 of 199
33. Type the number of a Client
Group and press Enter.
A confirmation screen will
mark your choice with an
"X". Type the number for
Done with the Selection,
and press Enter to
continue.
NOTES
This screen will be
displayed only if Client
Groups are configured for
the CommCell. For more
information, see Client
Computer Groups.
Client Group(s) is currently configured on CommServe
cs.company.com. Please choose the group(s) that you want
to add this client client.company.com to. The selected
group(s) will be marked (X) and can be deselected if you
enter the same number again. After you are finished with
the selection, select "Done with the Selection".

1) Unix
2) DR
3) DKS
4) Done with the selection

Please enter a number to select/deselect: [1]
34. If you have multiple
instances of the database,
ensure that the items listed
are satisfied. Press Enter.
IMPORTANT

If you are planning to use Data Protection Suite
<package> with several instances of the database, each
running on behalf of different UNIX users, you must make
sure that:

1) All database users have been added to each of the
database groups involved. For example, if there is a
"db2inst1" user from group "dba1" and "db2inst2" user
from group "dba2", then both "db2inst1" and "db2inst2"
should be included into "dba1" and "dba2" groups. On most
UNIXes this can be accomplished by editing the /etc/group
file.

2) The .profile of each database user must contains a
"umask 002" command at the end, which will guarantee that
all files created by one database user can be open for
writing by other database users.

3) All database users should be added to the "dba" group
that you have chosen for Data Protection Suite at the
time of CVGxBase install.

If all of the above requirements are not fulfilled, Data
Protection Suite will run into various "Permission
denied" errors, and backups will not work.

Setup Complete
35. Press Enter to continue.
NOTES
Schedules help ensure
that the data protection
operations for the Agent
are automatically
performed on a regular
+---------------------+
IMPORTANT:
In addition to installing Data Protection Suite on this
computer, you will also need to create a Job Schedule for
each iDataAgent that has been installed on this client
computer.
Job Schedules are required to allow the Data Protection
Page 61 of 199
basis without user
intervention. For more
information, see
Scheduling.
Suite iDataAgents to perform automated backup and restore
operations.
Job Schedule creation can be accomplished through the
Data Protection Suite CommCell Console administration
interface.
+---------------------+
Successfully installed CVGxIDA.
36. If this is the last package
that you wish to
install/upgrade, enter the
number corresponding to
the Return option and then
NOTES
Only modules that are
not installed/upgraded
appear in the list.
Your screen may appear
different from the
example shown.
If you are installing on
AIX, FreeBSD, IRIX or
Tru64 computers, if this
module was the last
possible module to
install, you are
automatically exited from
the program. Otherwise,
type the number for the
Exit option and then
press Enter. The
installation is completed.
like to install.
1) Proxy FileSystem iDataAgent <= CVGxProxyIDA
2) Oracle iDataAgent <= CVGxOrIDA
3) DB2 iDataAgent <= CVGxDB2
4) Return
Module number: [1]
37. Enter Yes to download and
install the latest service
packs and post packs from
the software provider.
NOTES
Internet connectivity is
required to download
updates.
This step is applicable for
multi instancing.
Download and Install Latest Service Pack
If you choose to download the latest service pack from
the software provider website now, please make sure you
have internet connectivity at this time. This process may
take some time depending on the internet connectivity.
Do you want to download the latest service pack now ?
[no]
38. This prompt is displayed
only when you are installing
on HP-UX, Linux, or Solaris
computers. Enter the
the Exit option and then
Certain Data Protection Suite packages can be associated
with a virtual IP, or in other words, installed on a
"virtual machine" belonging to some cluster. At any given
time the virtual machine's services and IP address are
active on only one of the cluster's servers. The virtual
machine can "fail-over" from one server to another, which
includes stopping services and deactivating IP address on
the first server and activating the IP address/services
Page 62 of 199
The installation is now
complete.
Currently you have Data Protection Suite installed on
physical node stone.company.com.
Now you have a choice of either adding another package to
the existing installation or configure Data Protection
Suite on a virtual machine for use in a cluster.
1) Add another package to stone.company.com
2) Install Data Protection Suite on a virtual machine
3) Exit
Your choice: [1]
General
supported features.
Agent Specific
Instance.
If you installed the Oracle iDataAgent for Oracle 9i on any supported version of Solaris, AND if you
have previously set (or are planning to set) SQLNET_EXPIRETIME in sqlnet.ora (which restricts system
access through sqlnet), then follow these post-install steps to prevent potential backup failures:
1. Shut down the Oracle database and the listener.
2. Edit the sysliblist file under the $ORACLE_HOME/lib directory.
3. Add -lthread and -lpthread at the beginning of the sysliblist file. An example of what it
should look like is as follows:
-lthread -lpthread -lnsl -lsocket -lgen -ldl -lsched
4. After performing the above steps, start up the Oracle database and the listener, then run a
backup. If you have not already created/configured an instance and subclient from the
CommCell Console, then you need to do that first before running the backup.
For the AIX, FreeBSD, HP-UX, IRIX, Linux, Solaris, and Tru64 File System iDataAgents, a registry
key is available to allow you to define where core files will be generated in the unlikely event of an
Page 63 of 199
application process crash. Generating core files in filesystems other than root will help maintain
system integrity. Refer to dCOREDIR for information about implementing this registry key.
After installing or upgrading the Oracle 9i or 10g iDataAgent on a Red Hat Linux AS 3.0 32-bit
platform, if you want to include the Oracle iDataAgent instance in an Oracle RAC node, follow the
procedure to Create a RAC Client.
Page 64 of 199
Install the Oracle iDataAgent - Unix - Clustered Environment
Install Checklist
Before You Begin
Install Procedure
Getting Started
Cluster Selection
Kernel Parameters
Oracle Specific Information
Setup Complete
The Oracle iDataAgent in a Unix cluster can be installed from the active node to the virtual server using
the following procedure. The software can also be automatically installed on all available passive nodes
when the software is installed onto the virtual server, or you can choose to install any passive node(s)
separately.
For an overview of deploying the software components in a clustered environment, see Clustering
Support.
The following procedure provides step-by-step instructions for installing the Oracle iDataAgent on a Unix
cluster. If you choose to install multiple components simultaneously, the sequence of the install steps
may vary.
Review the following Install Requirements before installing software on a Unix cluster:
General
Agents should be installed only after the CommServe and at least one MediaAgent have been
installed in the CommCell. Also, keep in mind that the CommServe and MediaAgent must be installed
and running (but not necessarily on the same computer), before you can install the Agent.
This software should be installed in a CommCell with current versions of the CommServe and
MediaAgent software.
Ensure there is an available license on the CommServe for the Agent.
operating system.
Firewall
If the CommServe

Page 65 of 199
Package Management Systems
You can use the Red Hat Package Manager (RPM) package management system to install all Linux
versions of the agent. Also, you can use the Advanced Packaging Tool (APT) package management
system to install all Debian Linux versions of the agent. For step-by-step instructions, see Use the
Package Management System for Installs.
Cluster
Refer to Supported UNIX Cluster Installations for important overview information about installing
MediaAgent or Agent software in a Unix clustered environment.
Check the following on the cluster computer in which you wish to install the software:
Cluster software is installed and running.
Active and passive nodes are available.
Agent Specific
Complete the following steps:
1. Ensure that the affected database is installed only on the virtual machine.
2. If both the database and its application files are installed on the virtual machine, install the Base
software and the required agents only on the virtual machine.
3. If the database application files are installed on the physical machine, install the Base software and
the required agents only on all the affected physical nodes; you do not need to install these items
on the virtual machine in this case. See Installation for more information.
4. Be sure to install your software to the appropriate directories per the directives in UNIX Clusters.
5. Verify that all of the computers to which software will be installed satisfy the minimum
requirements specified in the appropriate System Requirements.
6. Ensure that services are up and running on the remote hosts.
instances/databases for the agent before or during the following procedure. See Shut Down Instances
for more information.
Ensure that the Base software is installed in the same base directory on all physical nodes in the cluster.
Otherwise, the Oracle configuration for the passive nodes will be corrupted and will need to be relinked.
HP-UX
If you are installing on a HP-UX computer, you must manually mount the installation disc as
described in Mount the Software Installation Disc.
Install Checklist
Page 66 of 199
The spaces for the client name and the various directories are intended to contain information regarding
the virtual machine. Note that you may want to include multiple entries in these spaces if you are
installing more than one virtual machine on the current host machine.
General Information
1. Virtual client name:_____________________________
2. Network interface name associated with the physical machine:_____________________________
3. Node name for the physical machine:_____________________________
4. Install directory
location:________________________________________________________________
5. Log files directory
location:________________________________________________________________
The default is /var/log, but you may designate any location you want.
6. Network TCP port number for the Communications Service
(CVD):_____________________________
Network TCP port number for the Client Event Manager Service
(EvMgrC):___________________________
Firewall ports:
______________________________________________________________________
Keep Alive Interval
minutes:____________________________________________________________
connections:_________________________________________________
seconds:_____________________________________________________
8. CommServe Name and the CommServe Host
Name:______________________________________
For example, orange and orange.domainname.com.
Page 67 of 199
9. Job result directory
location:________________________________________________________________
subclient:________________________________________________
associated:_____________________________________________
Before You Begin
Log on to the client as root.
The install package requires super-user permissions to execute.
Install Procedure
Getting Started
1. Place the software
installation disc for the Unix
You can also install the
product using a disc drive
mounted on another
computer on the network.
On Solaris, double-click
the cvpkgadd program
from the File Manager
window.
On other Unix platforms,
open the Terminal
window, navigate to the
software installation disc
and then enter
cvpkgadd.

2. The product banner and
other information is
displayed.

3. Read the license agreement.
Type y and press Enter to
continue.

Cluster Selection
4. Type 2 and press Enter to
install on a virtual machine.
Certain Data Protection Suite packages can be associated
with a virtual IP, or in other words, installed on a
Page 68 of 199
"virtual machine" belonging to some cluster. At any given
time the virtual machine's services and IP address are
active on only one of the cluster's servers. The virtual
machine can "fail-over" from one server to another, which
includes stopping services and deactivating IP address on
the first server and activating the IP address/services
You now have a choice of performing a regular Data
Protection Suite install on the physical host or
installing Data Protection Suite on a virtual machine for
operation within a cluster.
Most users should select "Install on a physical machine"
here.
1) Install on a physical machine
2) Install on a virtual machine
3) Exit
Your choice: [1]
5. Type the name of the virtual
machine that you want to
configure or its
corresponding IP address
and press Enter.
Please enter the hostname or IP address of the virtual
machine being installed. It can be either short or long;
the only requirement is that it must be resolvable by the
name services configured on this machine
WARNING: You should follow this path ONLY if this host
participates in a cluster and you really want to install
Data Protection Suite on the virtual machine. This is NOT
how most people will use Data Protection Suite.
If you got into this screen by mistake, hit ^C and
restart cvpkgadd.
Virtual Machine Host Name:
6. This prompt appears if you
entered the short form of
the virtual machine host
name in the previous step.
If you want to use the long
form of the host name,
accept the yes default; if
not, type no. Then press
Enter.
It looks like name "example.company.com" resolves to the
same IP as "example". Generally, it's better to use
longer name to address a host: less chances for name-to-
IP resolution problems on CommServe or other IDA/MA.
Would you like to use fully qualified
"example.company.com" instead of "example"?
Use longer "example.company.com" name? [yes]
7. If you have already installed
the software on the virtual
machine for the active node,
accept the yes default to
install for the passive node,
press Enter, and go to the
next step.
If you still must install for
the active node, type no,
press Enter, and perform
the install for the virtual
machine for the active node.
NOTES
This prompt appears only
When installing new Data Protection Suite packages on a
virtual machine, you should start with the active node,
that is the host where the virtual machine is currently
running.

This node appears to be passive, so we will assume that
you have already installed Data Protection Suite for
example.company.com on the active node.

Is this correct? [yes]
Page 69 of 199
when installing on a
passive node.
8. Type the name of the virtual
client and press Enter.
Please specify the client name for this machine.
It does not have to be the network host name: you can
enter any word here without spaces. The only requirement
is that it must be unique on the CommServe.
Virtual Machine Client Name: [hpuxmc1]
9. Specify the network
interface that you want to
associate with the physical
machine and press Enter.
NOTES
This prompt appears only
when the UNIX File
System iDataAgent is not
installed on the physical
node.
Even though it is a virtual machine that you are
installing now, we still have to ask you to provide
hostname and client name for the physical node.
Network interfaces with the following IPs are available
on your system. Please select the one that you want to be
associated with Data Protection Suite physical machine.
The interface should be static, and should not get
disabled in case of cluster failover.
1) mackrel71
2) mackrel
3) mackrel1
Interface number: [1] 2
10. Verify the name of the
physical interface and make
any required changes. Then
press Enter.
Please verify the physical interface name below. Make it
as complete (with fully qualified domain name) as
possible.
Physical Hostname: [mackrel]
11. Enter a node name for the
physical machine and press
Enter.
Even though you are installing Data Protection Suite on a
machine, we still need to ask you to provide a node name
for the physical machine.
It does not have to be the network host name: you can
enter any word here without spaces. The only requirement
is that it must be unique on the CommServe.
Physical Machine Node Name: [mackrel]
corresponding to the
CVGxOrIDA module.
NOTES
Your screen may look
different from the
example shown.
Components that either
have already been
installed, or which cannot
be installed, will not be
shown.
In addition, the list of
modules that appear
depends on the specific
Unix File System in which
the package is installed.
(e.g., CVGxWA will
Install Data Protection Suite on physical machine
client.company.com
like to install
1) Media Agent <= CVGxMA
2) FileSystem iDataAgent <= CVGxIDA
3) Exit this menu
Module number: [1]
Page 70 of 199
appear only when the
installation package is
run on a Solaris
computer.)
If this is the first package
to be installed on the
computer, press Enter to
continue.
If this is NOT the first
package to be installed
on the computer, this
screen will not be
displayed. Skip to
Here is a list and status of the dependent modules:
1) Data Protection Suite Base0
2) Data Protection Suite Base
If there are any modules listed as NOT
installed/upgraded, they will be installed/upgraded
first.
Press <ENTER> to proceed ...
14. Specify the location where
you want to install the
software.
NOTES
different from the
example shown.
or
Enter to continue.
confirm the path.
Please specify where you want us to install Data
Protection Suite binaries.
170MB of free space available. All files will be
installed in a "hds" subdirectory, so if you enter
"/opt", the files will actually be placed into
"/opt/hds".
Installation Directory: [/opt]
..
Data Protection Suite will be installed in /opt/hds.
15. Specify the location for the
log files.
NOTES
All the modules installed
on the computer will
store the log files in this
directory.
different from the
example shown.
or
Please specify where you want to keep Data Protection
Suite log files.
100MB of free space available. All log files will be
created in a "hds/Log_Files" subdirectory, so if you
enter "/var/log", the logs will actually be placed into
"/var/log/hds/Log_Files".
Log Directory: [/var/log]
..
Data Protection Suite log files will be created
in /var/log/hds/Log_Files.
Page 71 of 199
Enter to continue.
confirm the path.
like to launch processes with
inherent database access
rights.
Press Enter to assign a new
group, or
Type No and then press
Enter to continue.
Most of Data Protection Suite processes run with root
privileges, but some are launched by databases and
inherit database access rights. To make sure that
registry and log files can be written to by both kinds of
processes we can either make such files world-writeable
or we can grant write access only to processes belonging
to a particular group, e.g. a "hds" or a "dba" group.
We highly recommend now that you create a new user group
and enter its name in the next setup screen. If you
choose not to assign a dedicated group to Data Protection
Suite processes, all temporary and configuration files
will be created with -rw-rw-rw permissions.
If you're planning to backup Oracle DB you should use
"dba" group.
Would you like to assign a specific group to Data
Protection Suite? [yes]
17. If you indicated Yes in the
previous step, you will be
prompted for the group
name that must be used to
launch processes.
Enter the group name and
then press Enter to
continue.
continue.
For installs on a Solaris
computer, proceed to the
next step. Otherwise, skip to
Please enter the name of the group which will be assigned
to all Data Protection Suite files and on behalf of which
all Data Protection Suite processes will run.
In most of the cases it's a good idea to create a
dedicated "hds" group. However, if you're planning to use
Oracle iDataAgent or SAP Agent, you should enter Oracle's
"dba" group here.
Group name: dba
REMINDER
If you are planning to install Data Protection Suite
Informix, DB2, Sybase or Lotus Notes iDataAgent, please
make sure to include Informix, DB2, etc. users into group
"dba".
18. Type a network TCP port
number for the
Communications Service
(CVD) and press Enter.
Type a network TCP port
number for the Client Event
Manager Service (EvMgrC)
and press Enter.
NOTES
about Network TCP Ports,
see Network TCP Port
Requirements.
about these services, see
Services.
Every instance of Data Protection Suite should use a
unique set of network ports to avoid interfering with
other instances running on the same machine.
The port numbers selected must be from the reserved port
number range and have not been registered by another
application on this machine.

Please enter the port numbers.

Port Number for CVD : [8400]

Port Number for EvMgrC: [8402]
Page 72 of 199
19. If this computer
communicates with the
CommServe, MediaAgent
and/or other clients across a
firewall, type Yes, and then
Press Enter, if you do not
wish to configure the firewall
services. Proceed to the
next section.
Various Data Protection Suite components need to
communicate with each other: iDataAgents and MediaAgents
establish connections to CommServe and talk to each other
as well. If any of the involved parties are situated on
the opposite sides of a firewall, Data Protection Suite
should be made aware of it so that it could bind its
pipeline sockets to open ports and could establish
tunnels for control traffic.

You must configure Data Protection Suite firewall
services if there are other Data Protection Suite
machines, which are expected to communicate with this
one.

Do you want to configure Data Protection Suite firewall
services? [no]
20. Enter the port range(s), and
then press Enter to
continue.
NOTES
Specify the range of
ports that must be used
for communication
between the Client and
CommServe and/or
MediaAgent computers.
For more information on
the port requirements,
see Port Requirements
for Two-way Firewall or
Port Requirements for
One-way Firewall, as
applicable.
Data Protection Suite needs to know which TCP ports of
this machine are available for connections initiated by
machines on the other side of the firewall.
If this machine is not reachable from the other side of
the firewall at all (because the FW is one-way and allows
only outgoing connections), enter any unused port number
here (e.g. 8600).
Otherwise please consult your FW configuration for the
list of open incoming ports and enter all of them here
(with the exception of port 8400).
Currently there are no ports configured. Please enter a
single port number or a port range (like 8600-8620) to be
added to the FW configuration:
Port range: [8600-8620]
NOTES
refer the previous step.
1) Add another open port or a range of ports
2) Delete an existing port or a range of ports
3) Continue with the firewalled host setup
Your choice: [3]
22. Enter the host name(s) of
the computers that will need
to be contacted through a
firewall, and then press
Enter to continue.
We need to know which Data Protection Suite hosts are
located on the other side of the firewall, and whether
the firewall will allow direct or reverse connections
to/from those hosts.
You can specify hosts by either entering their names, IP
addresses or name/IP wildcards. The wildcards are
available only if the firewall is symmetrical, i.e.
allows to open connections to certain ports both ways.
Currently there are no firewall hosts configured.
Please enter the name or IP address of a host on the
Page 73 of 199
other side of the firewall. If the firewall is
symmetrical, you are allowed to use wildcards, i.e.
things like 192.168.* or *.firewall.company.com:
Firewalled Host: lavender.company.com
23. Choose the option
associated with type of
firewall configuration based
on the firewall setup in your
environment.
NOTES
Choose Two-way
(symmetrical) firewall
if you can open certain
ports as bi-directional
ports.
Choose One-way
firewall; <port> is
reachable from here if
this computer
communicates with
MediaAgent/Client on the
other side of the firewall.
Choose One-way
firewall; this machine
is reachable from
<port> when the
CommServe and any
Clients/MediaAgents)
communicates with this
computer.
Please specify the type of the firewall separating this
machine from 172.19.61.89.
1) Two-way (symmetrical) firewall
2) One-way firewall, 172.19.61.89 is reachable from
here
3) One-way firewall, this machine is reachable from
172.19.61.89
Your choice: [1]
NOTES
refer the previous two
steps.
1) Configure another host
2) Delete an existing host
3) Continue with the firewall keep-alive setup
Your choice: [3] 1
25. If desired, modify the Keep
Alive interval, and then
press Enter to continue, or
default.
Please specify Keep Alive interval for Data Protection
Suite firewall services.
Many firewalls disconnect idle Network connections after
some period of time. Some of the Data Protection Suite
Services need continuous connections. Data Protection
Suite keeps such connections active by sending periodic
"keep-alive" packets.
Consult your firewall documentation, or contact your
Network Administrator, for the exact value after which
idle connections will be closed (snip time). Then enter a
value, which is at least one minute less than the snip
time.
Keep-alive interval, minutes [5]
Page 74 of 199
26. To configure advanced
firewall settings, type Yes,
and then press Enter.
If you do not want to
configure advanced firewall
settings, type No, and then
press Enter. Proceed to the
next section.
The Generic part of the Data Protection Suite Firewall
Config has been completed successfully. There are some
additional advanced settings that you may want to review
now. All of them can be customized later by editing
the .properties file
under /etc/CommVaultRegistry/Galaxy/Instance003/Firewall.
Would you like to review the advanced settings now? [no]
27. To bind the local end of
tunnel connections to a
specified interface, type
Yes, and then press Enter.
If you do not want to bind
the local end of tunnel
connections to a specified
interface, type No, and then
press Enter. Skip the next
Step.
Normally Data Protection Suite Firewall code doesn't bind
local end of TCP/IP sockets when establishing outgoing
tunnel connections relying on the OS to pick correct
interface and arbitrary port automatically. Usually this
doesn't cause connectivity problems because we require
that the firewall must allow connections for as long as
1meither source or destination socket end is bound to one
of the ports in the open range.
Sometimes, however, on hosts with several NICs it's
important to force the OS to bind the local socket end to
a specific network interface. There is a Data Protection
Suite setting called 1mnBIND_BEFORE_CONNECT_IFACEm, which
enables this behavior. If present, Data Protection Suite
will bind the local end of tunnel connections to the
specified interface.
Would you like to configure nBIND_BEFORE_CONNECT_IFACE?
[no]
28. Type a number
corresponding to one of the
listed network interfaces, to
use for outgoing tunnel
connections through the
firewall.
Please select network interface that should be used for
all outgoing tunnel connections:
1) <ip_address>
29. If desired, modify the
Tunnel Initialization interval
by typing a number.
When tunnel to a destination machine cannot be
established because the machine is down or is not
accepting connections, Data Protection Suite will retry
the connection after some time. Tunnels piercing one-way
firewalls are 1mPERSISTENTm meaning that Data Protection
Suite will keep on trying to initialize them until
success. These attempts can generate a lot of network
traffic if a central machine (e.g. CommServe) suddenly
goes down.
Here you can adjust the interval (called
1mnTUNNEL_INIT_INTERVALm in registry) between tunnel init
attempts.
Tunnel Init Interval, seconds, [5]
30. Type the name of the
CommServe computer and
NOTES
Please enter the hostname of the Data Protection Suite
CommServe. It can be either short or long; the only
requirement is that it must be resolvable by the name
services configured on this machine.
CommServe Name:
Page 75 of 199
Ensure that the
CommServe is accessible
before typing the name;
otherwise the installation
will fail.
If you enter a short name
which resolves to the
same IP address as the
fully qualified
CommServe name, you
will be asked if you would
prefer to use the fully
qualified name.
31. Enter the username and
password information for
an external domain user
account or a CommCell user
account. This authorizes the
installation of an agent on
the CommCell.
NOTES
This is only displayed
when the
Authentication for
Agent feature is enabled
in the CommCell
Properties. Users must
belong to a User Group
with Agent Management
capabilities to enable this
feature. For more
information, see
Authentication for Agent
Installs.
Click Enter to continue.
Enter your CommCell user name and password:
User Name :
Password :
32. Specify the location of the
job results directory.
NOTES
All the agent modules
installed on the computer
uses the job results
directory to store the
backup and restore job
results.
different from the
example shown.
or
Please specify the name for the JobResults directory.
Since you are installing Data Protection Suite on a
virtual machine, the JobResults directory must reside on
a shared disk and should have at least 20MB of free space
available. The directory will be used to store
intermediate data that should be passed from one backup
phase to another.
JobResults Directory: [/swtitchover/]
Page 76 of 199
Enter to continue.
Kernel Parameters
33. Enter the appropriate
number of streams, and
then press Enter to
continue, or
default number of streams
and continue.
NOTES
The number of streams
specified ensures that
concurrent
backup/restore streams
would have sufficient
system resources. For
more information on the
subject, see Configuring
Kernel Parameters
(Unix/Macintosh).
This prompt is relevant only
when you install/upgrade on
a Macintosh or Solaris
computer as appropriate.
Please enter the total number of streams that you plan to
run at the same time. We need to make sure that you have
enough semaphores and shared memory segments configured
in /etc/system.
Number of streams: [10]
like modifications to be
made to the /etc/system
configuration file.
Type Yes, and then press
Enter to automatically
update the file and continue,
or
default No and continue (if
you do not want to
automatically update the
file).
only when you
or Macintosh computer.
We now need to modify the /etc/system configuration file
on this computer. It is done to make sure that there will
be enough shared memory and semaphores available for Data
Protection Suite programs.
Please review the changes below and answer "yes" if you
want us to apply them to the /etc/system file. Otherwise,
the installation will proceed, the changes will be saved
to some other file, and you will have to apply them
manually.
set shmsys:shminfo_shmmni=8570 (was 7930)
set shmsys:shminfo_shmseg=8420 (was 7780)
set semsys:seminfo_semmns=10320 (was 9680)
set semsys:seminfo_semmni=8570 (was 7930)
set semsys:seminfo_semmsl=8570(was 7930)
Do you want us to apply these changes now? [no]
Changes saved into /etc/system.gal.1744
Press <ENTER> to continue.
35. If you indicated No in the
previous step, the file to
which the changes have
been saved is displayed.
Make sure that these values
are established later to
ensure that all the
requirements for this setup
is satisfied.
Although a no answer can be selected to this question
during install, the user should make sure the min
requirements (below) for shared memory are met, otherwise
the backups may fail (the message in logs is could not
start the pipeline).
set shmsys:shminfo_shmmax=4199304
set shmsys:shminfo_shmmin=1
set semsys:shminfo_shmmni=640
set semsys:shminfo_shmseg=640
Page 77 of 199
NOTES
The settings that are
displayed are the
maximum or minimum
required settings. Value
640, which is provided
for various shared
memory segment or
semaphore requirements,
is a maximum value
based on 10 streams.
only when you
computer, in cases where
the install detects that the
computer does not have the
maximum or minimum
required shared memory
settings.
set semsys:seminfo_semmns=640
set semsys:seminfo_semmni=640
set semsys:seminfo_semmsl=640
set maxusers=256
corresponding to the storage
policy through which you
want to back up the File
System iDataAgent and then
NOTES
A storage policy directs
backup data to a media
library. Each library has a
default storage policy.
When you install an
Agent, the install
program creates a
default subclient for most
Agents.
If desired, you can
change your storage
policy selection at any
time after you have
installed the client
software.
If this screen appears
more than once, it is
because you have
selected multiple agents
for installation and are
configuring storage policy
association for each of
the installed agents.
Please select one storage policy for this IDA from the
list below:
1) SP_StandAloneLibrary2_2
2) SP_Library3_3
3) SP_MagLibrary4_4
4) fornax_fornax_HWCmp
5) ranger_ranger_HWCmp
6) fornax_fornax_ClntCmp
7) fornax_fornax_MACmp
8) fornax_fornax_NoCmp
Storage Policy: [3]
Page 78 of 199
37. Type the appropriate
number for configuring
Global Filters for the default
subclient and press Enter to
continue.
NOTES
Select Use Cell level
Policy to inherit the
global filter policy
configuration set for the
CommCell, i.e., if the
Use Global Filters on
All Subclients option is
selected in the Global
Filters dialog box (from
the CommCell Consoles
Control Panel), then this
policy will be applied to
the default subclient as
well. If is not selected,
then the global filters will
not be applied to the
default subclient.
Select Always use
Global filters to always
apply the global filters
policy to the default
subclient regardless of
the policy set for the
CommCell.
Select Do not use
Global filters to
disregard applying the
global filters to the
default subclient
regardless of the policy
set for the CommCell.
Commcell Level Global Filters are set through Data
Protection Suite GUI's Control Panel in order to filter
out certain directories or files from backup Commcell-
widely. If you turn on the Global filters, they will be
effective to the default subclient. There are three
options you can choose to set the filters.
1) Use Cell level policy
2) Always use Global filters
3) Do not use Global filters
Please select how to set the Global Filters for the
default subclient? [1]
38. Type the number of a Client
Group and press Enter.
A confirmation screen will
mark your choice with an
"X". Type the number for
Done with the Selection,
and press Enter to
continue.
NOTES
This screen will be
displayed only if Client
Groups are configured for
the CommCell. For more
Client Group(s) is currently configured on CommServe
cs.company.com. Please choose the group(s) that you want
to add this client client.company.com to. The selected
group(s) will be marked (X) and can be deselected if you
enter the same number again. After you are finished with
the selection, select "Done with the Selection".

1) Unix
2) DR
3) DKS
4) Done with the selection

Please enter a number to select/deselect: [1]
Page 79 of 199
information, see Client
Computer Groups.
Oracle Specific Information
39. The install program now
starts copying the software
to the computer. The
progress of the operation is
displayed.
.....
.....
.....
.....
Successfully copied xx files
40. If you have multiple
instances of the database,
ensure that the items listed
are satisfied. Press Enter.
IMPORTANT

If you are planning to use Data Protection Suite
<package> with several instances of the database, each
running on behalf of different UNIX users, you must make
sure that:

1) All database users have been added to each of the
database groups involved. For example, if there is a
"db2inst1" user from group "dba1" and "db2inst2" user
from group "dba2", then both "db2inst1" and "db2inst2"
should be included into "dba1" and "dba2" groups. On most
UNIXes this can be accomplished by editing the /etc/group
file.

2) The .profile of each database user must contains a
"umask 002" command at the end, which will guarantee that
all files created by one database user can be open for
writing by other database users.

3) All database users should be added to the "dba" group
that you have chosen for Data Protection Suite at the
time of CVGxBase install.

If all of the above requirements are not fulfilled, Data
Protection Suite will run into various "Permission
denied" errors, and backups will not work.

.....
.....
.....
Successfully installed CVGxOrIDA.
42. Enter Yes to download and
install the latest service
packs and post packs from
the software provider.
NOTES
Internet connectivity is
required to download
updates.
This step is applicable for
multi instancing.
Download and Install Latest Service Pack
If you choose to download the latest service pack from
the software provider website now, please make sure you
have internet connectivity at this time. This process may
take some time depending on the internet connectivity.
Do you want to download the latest service pack now ?
[no]
Page 80 of 199
Setup Complete
NOTES
Schedules help ensure
that the data protection
operations for the Agent
are automatically
performed on a regular
basis without user
intervention. For more
information, see
Scheduling.
+---------------------+
IMPORTANT:
In addition to installing Data Protection Suite on this
computer, you will also need to create a Job Schedule for
each iDataAgent that has been installed on this client
computer.
Job Schedules are required to allow the Data Protection
Suite iDataAgents to perform automated backup and restore
operations.
Job Schedule creation can be accomplished through the
Data Protection Suite CommCell Console administration
interface.
+---------------------+
Successfully installed CVGxIDA.
44. If this is the last package
that you wish to
install/upgrade, enter the
the Return option and then
NOTES
Only modules that are
not installed/upgraded
appear in the list.
Your screen may appear
different from the
example shown.
If you are installing on
AIX, FreeBSD, IRIX or
Tru64 computers, if this
module was the last
possible module to
install, you are
automatically exited from
the program. Otherwise,
type the number for the
Exit option and then
press Enter. The
installation is completed.
like to install.
1) Proxy FileSystem iDataAgent <= CVGxProxyIDA
2) Oracle iDataAgent <= CVGxOrIDA
3) DB2 iDataAgent <= CVGxDB2
4) Return
Module number: [1]
45. This prompt is displayed
only when you are installing
on HP-UX, Linux, or Solaris
computers. Enter the
the Exit option and then
The installation is now
complete.
Data Protection Suite is currently configured on virtual
machine hpuxmc1.company.com.
Now you have an option of installing Data Protection
Suite on physical machine, another virtual machine or you
can add a new package to hpuxmc1.company.com.
1) Add a new package to hpuxmc1.company.com
2) Install Data Protection Suite on the physical machine
3) Install Data Protection Suite on another virtual
machine
Page 81 of 199
4) Exit
Your choice: [1]
General
supported features.
Cluster
The cvclusternotify.sh script should be added as part of the normal cluster startup/shutdown
procedure. The script is provided as a generic template, and it must be run whenever the current
node shuts down during failover and as the new active node comes online. In both cases, data
protection services must be up and running. The script works as follows:
During node shutdown, the script notifies File Archiver for Unix and the CommServe that the listed
file systems will no longer be monitored on this node.
During node startup, the script notifies File Archiver for Unix and the CommServe that the listed
file systems will now be monitored on this node.
Usage:
cvclusternotify - Program to notify Data Protection Suite of cluster failovers
cvclusternotify -inst <Instance> -cn <Client Name> -start|-shutdown \[-fs <dir1>]
[-fs <dir2>] ...
This command notifies Data Protection Suite that the specified client from the specified instance is
going up or down because of a cluster failover. The optional "-fs <dir>" parameters can be provided
to notify File Archiver for Unix that certain file systems are disappearing or becoming available during
the failover. For each of these file systems, the CDR/File Archiver for UNIX driver will be instructed to
stop or begin file system monitoring.
Example:
Suppose you have a two-node cluster where the virtual machine client name is "virtual". (Physical
node names are not needed.) Suppose that the application instance in this case is "Instance001" and
that the archived data currently exists on two shared file system directories as follows:
/share1/filesystem1
/share2/filesystem2
For the node shutdown, the following command is issued:
cvclusternotify -inst Instance001 -cn "virtual" -shutdown -fs /share1/filesystem1 -
fs /share2/filesystem2
This will stop File Archiver for Unix from monitoring the indicated file systems on the node that is
Page 82 of 199
shutting down.
For the node (active) startup, the following command is issued:
cvclusternotify -inst Instance001 -cn "virtual" -start -fs /share1/filesystem1 -
fs /share2/filesystem2
This will enable File Archiver for Unix to start monitoring the indicated file systems on the node that
is starting up.
On failover of a Linux cluster, Services may be killed by cluster services during a virtual machine
failover. To insure that the Services are re-started on the passive node, add commands in failover
scripts to start Services.
Page 83 of 199
Backup - Oracle
Topics | How To | Troubleshoot | Related Topics
Overview
Supported Backup Types
Oracle Backup Jobs
Oracle Selective Online Full Backups
Optional Configuration for Oracle Backups
Backup Arguments
Table Backup
Backup Considerations
Advanced Backup Options
Overview
Plan your backup jobs for this agent by reviewing the following information:
For an overview of backup jobs, see Backup Data.
For a list of supported data types for this agent, see Supported Data Types.
For information on subclients, see Subclients
For information on configuring subclients for this agent, see Subclients - Oracle.
For information on running backups from the RMAN command line, see Third-Party Command Line
Operations.
Supported Backup Types
This agent supports the following backup types:
Full Backups
Incremental Backups - The Oracle iDataAgent supports Levels 1 to 4 backups. For more information
on incremental backups, refer to incremental backups in the Oracle Backup and Recovery Guide from
Oracle Corporation. (The Oracle Incremental backups work as described in Differential backups. See
Differential Backups for information on Oracle Incremental Backup.)
Archive Log Backups
SnapProtect
For Oracle On Demand backup jobs, in cases where multiple instances
are backed up that are not all in the same mode, Job Manager will
report the backup type as either Full (when the first instance in the
backup script is in OPEN mode) or as Offline Full (when the first
instance in the backup script is in MOUNTED mode).
Oracle Table Browse and Table Restore are not supported for data
backed up using Oracle SnapProtect.
Always ensure that the archive logs are backed up prior to deleting them.
Page 84 of 199
Oracle Backup Jobs
This agent has the following unique functionality.
Backup Arguments
Table Backup
This is a special type of backup where a full backup is taken of the Oracle database while it is online, and
the backup data can be copied to a selective copy (during an auxiliary copy operation) from which it can
be restored.
The advantage of this type of backup is that both data and logs use the same storage policy, which
means that they reside together on the same media, and are completely self-contained for restore and
long term archiving purposes. This is especially useful in disaster recovery situations by alleviating the
need to locate different offsite media from various jobs to gather the necessary data and logs to recover
the database. Also, the data aging rules for selective online full backups are different from regular full
backups, as both data and logs are aged together under the same storage policy.
There are certain rules that pertain to this type of backup that you should keep in mind:
A selective online full backup job will wait for other Oracle backup jobs currently running on the same
instance to complete, before it begins.
For this type of backup, both data and archive logs will use the same storage policy as defined for data
in the subclient, and will ignore the storage policy setting for archive logs (which is defined at the
instance level).
During selective online full backups, if the data streams (defined at the subclient level) is less than the
archive log streams (defined at the instance level), then both the data phase and the archive log
phase will use the same number of streams defined for the data in the subclient, and will ignore the
number of streams set for the archive logs.
While the data backup phase of a selective online full backup is running, the only other Oracle backup
jobs that are allowed to run on the same instance are archive log backups. During the log backup
phase of a selective online full backup, no other Oracle backups are allowed to run (neither logs nor
data) on the same instance.
If other Oracle archive log backup jobs are run at the same time as the selective online full backup,
they will be forced to use the same storage policy used by the selective online full backup during the
time-frame in which the selective online full backup job is running, and will be included in the same
auxiliary copy operation. Refer to Oracle and Oracle RAC for more information on special data aging
rules for selective online full backups.

Depending upon how your Oracle server and databases are set up, you may need to perform the
following addition configuration.
Allocate Command Syntax for Oracle Command Line Backups on a Unix Cluster
In order to perform Oracle Command Line backups on a Unix cluster, you need to use the following
syntax for the allocate command within the RMAN script:
allocate channel ChannelName type 'sbt_tape' PARMS="ENV=
(CVOraVMName=VirtualMachineName)";
where ChannelName can be chN (N is a stream number: 1, 2, ...) and VirtualMachineName should be the
name of the virtual machine.
Page 85 of 199
Configuring Autobackup of Control Files
The control file contains metadata about the physical structure of the database including the location of
all files, the current database state and system change number (SCN), as well as information about
backups performed in RMAN. Oracle 9.2 and 10g provide the capability to configure autobackup of control
files in RMAN so that they are automatically backed up along with the server parameter file during
backup operations. The purpose of the control file autobackup is to provide a way to restore the backup
repository contained in the control file when the control file is lost and the recovery catalog is either lost
or was never used. You do not need a recovery catalog or target control file to restore the control file
from autobackup. If you dont use the catalog database for Oracle backups, and the entire database and
control file are lost, then a restore of the entire database with control files will fail unless you have
enabled autobackup of control files in RMAN.
See Configure Autobackup of Control Files for step-by-step instructions.
Configuring the Lights Out Script to Shut Down the Database for Offline Backups
In order to perform offline backups of the Oracle database, all users must be logged out of the database
and it must be completely shut down. Certain options are available in the Subclient Properties (Backup
Arguments) tab that allow you to automate the graceful shutdown of the Oracle database to perform
offline backups. A brief description of these options, and their role in the shutdown sequence are provided
below.
1. For Oracle on Unix, a warning message is issued to the physical node to notify users that the
database will be shut down in a specified number of minutes and request that they log out of the
database. This message is issued when the Warning option is enabled. Note that the Warning
option is not supported for Oracle on Windows platforms.
2. For Oracle on Unix, after the warning message has been issued to the physical node, the lights out
process will wait for the period of time specified in the Delay Time (min) option while users log
out, before an attempt is made to shut down the database. After waiting the specified Delay Time,
the SHUTDOWN IMMEDIATE statement is issued to the server.
3. The status of the database will be then checked to determine whether it is shutdown. If it is not
shutdown, the system will retry issuing the SHUTDOWN IMMEDIATE statement, based on the
following sequence of settings:
a. Sleep Time (sec) - The lights out process will wait (i.e., sleep) for the specified number of
seconds before retrying the SHUTDOWN IMMEDIATE statement and checking the status again.
Because the goal is to shut down the database as quickly as possible, the Sleep Time in
seconds is tried first, and must exhaust all the number of tries in the Tries Number setting
located below the Sleep Time (sec) option, before switching over to the Sleep Time (min)
option.
b. Sleep Time (min) - If the number of tries limit has been reached for the Sleep Time (sec)
option and the database has not been shut down yet, the lights out process will then begin
waiting for the number of minutes specified in the Sleep Time (min) option before retrying the
SHUTDOWN IMMEDIATE statement and rechecking the status again. The reasoning behind this
approach is that once it becomes apparent to the system that it can't shut down the database
quickly, it probably means that someone must be still logged in to the database in order to
complete their work, and the system will retry at less frequent intervals, in this case minutes
not seconds, in order to give the user time to complete and save the work. The system will
keep retrying to shut down the database until it exhausts the number of tries in the Tries
Number setting located below the Sleep Time (min) option. If the database is successfully
shutdown, the backup will begin, otherwise the sequence continues to the next step.
4. Once the Tries Number limit is reached for the Sleep Time (min) option, then a SHUTDOWN ABORT
statement will be issued to the server. If the SHUTDOWN IMMEDIATE statement has already
completed within the specified time, this has no effect. Otherwise the SHUTDOWN ABORT overrides
the SHUTDOWN IMMEDIATE statement and shuts down the database.
See Configure the Lights Out Script to Shut Down the Database for Offline Backups for step-by-step
instructions.
Page 86 of 199
Configuring the Oracle Tag for Backups
You can configure the Oracle Tag for backups on a subclient to uniquely identify a particular backup copy.
The Oracle Tag specified for a backup can be used during a restore operation to tell the system which
particular backup to restore the data from. Use of the Oracle Tag backup argument provides an
alternative to point-in-time restores.
See Configure Backup Arguments for step-by-step instructions.
Backup Arguments
Some database iDataAgents run backups using a system-generated script that is run behind the scenes
from a command line. The CommCell Console serves as a front-end user interface for specifying various
backup arguments and parameters that are passed to the backup script that is run. Depending on your
agent, you can specify, for example, the application-specific Backup Level, whether the backups will be
online or offline, as well as buffer and bundle sizes, among other settings. Although the backup
arguments/parameters vary among iDataAgents, they all function in a similar manner. These arguments
are set at the subclient level from the respective iDataAgent's Subclient Properties dialog box tab.
For step-by-step instructions, see Configure Backup Arguments.
Table Backup
You can restore and recover individual database tables from non-system tablespaces to the same
database or to another database. In order to restore individual Oracle or Oracle RAC database tables, you
need to select the Enable Table Browse option in the Subclient Properties dialog box for the subclient
prior to a backup. Note that this option can be enabled on only one subclient. Also, ensure that this
option is not enabled on the LOGS-only subclient. When this option is enabled, information such as Oracle
tablespace, user ID and table name mappings are stored in the CommServe during the backup operation.
For step-by-step instructions on running a table restore, see Restore and Recover One or More Database
Table(s).
Backup Considerations
Before performing any backup procedures for this agent, review the following information:
For online database backups the database must be in ARCHIVELOG mode.
Oracle selective online full backup jobs will immediately fail if there are any job-related failures.
It is recommended that users do not kill Oracle backup jobs, since it may cause RMAN and/or
Cloragent exception errors.
Users should not run several console-initiated RMAN jobs for the same instance at the same time for
Oracle clients running on Windows platforms. Limit RMAN jobs to run one at a time in the CommCell
Console and scheduler.
Different SID and database names for Oracle instances are supported for Oracle command line
backups.
When the Data Files per BFS parameter is set to a value greater than 32 on the Subclient Properties
(Backup Arguments) dialog, in order to back up more than 32 files per bundle at a time, the following
parameter line is added inside the RMAN script: set limit channel ch1 maxopenfiles = nn
Increasing the bundle size may improve the backup performance on large enterprise servers, but may
hinder performance on smaller systems with limited resources.
The incremental backup type is not supported by the Oracle Database application for Oracle 9.2
Standard Edition, and therefore is not supported by the Oracle iDataAgent. If you are using the
Standard Edition of Oracle, you will need to run full backups.
Oracle recommends that it is mandatory to do a Incremental Level 0 backup (which equates to a Full
backup) after adding new tablespaces and datafiles to the database. If this is not done, the next
Incremental backup would fail, because the Oracle Recovery Manager will not be able to find the
parent files for the new tablespaces and datafiles.
Page 87 of 199
If you perform a backup of the default subclient, without changing its default properties, the backup
would include all the objects in the database, including any new objects that may have been created.
If you have created subclients for either online or offline databases, and have included the archived
log files and control files in these subclients, you can create a complete backup of the database by
backing up these subclients. If you have created a group of online subset subclients for the database,
you must backup all of these subclients to create a complete backup. If you have created separate
subclients for archive logs and control files, and if they are not included with the subclients defined for
online databases, offline databases or subsets, then the subclients for archive logs and control files
must also be backed up to create a complete backup.
You can preview the backup and restore scripts that will be submitted to RMAN to back up or restore
data on a client. Previewing the script before running a backup or restore is useful for identifying
whether the selected backup or restore options will yield the desired result in the script. The script text
can be previewed from the Backup Options and Restore Options dialogs, and provides the capability
for you to copy the text from the display window for manual submission in RMAN, if desired.
You can run a validate job to ensure the integrity of the data and availability of the media before
actually running a backup or restore job. When the validate option is selected on the Subclient
Properties (Backup Arguments) tab or Advanced Restore Options (Options) tab, this will cause the
system to simulate either a backup or restore job without using any media or over-writing the Oracle
database. After the validate job completes, you can view the log file for the job to identify and correct
any validation issues prior to running the backup or restore.
Review Performance Tuning - Oracle or Performance Tuning - Oracle RAC for details on setting
configuration parameters to optimize backup and restore operations for your site.
For Oracle on Linux platforms, review Avoiding Intermittent Backup Failures for Oracle on Linux
Platforms for additional configuration steps that may be needed for your site.
Multiple streams are supported for data protection and recovery operations with this agent; however,
before utilizing multiple streams, you should understand how their use affects operations. For more
information, see Streams.
When creating/modifying an instance for Oracle or Oracle RAC iDataAgent, make sure that you do not
enter a / at the end of the string for Oracle Home path. Due to limitations in the Oracle application,
having a / at the end of the string for Oracle Home path can cause backups to fail occasionally.
For Oracle and Oracle RAC iDataAgent, when you resume a backup job, if the subclient content
includes the SP file, the backup job gets restarted from the beginning and all the data that was backed
up previously gets backed up again. This causes an incorrect display of data transferred count in job
details.
If the Oracle offline backup with lights out option fails when you use the default value for Tries
Number in the Subclient Properties (Backup Arguments) window, then increase the value to a number
greater than or equal to 5.
An Oracle offline backup will start up from the beginning (and not from the point of failure) if the
backup fails and is then resumed.
When you configure the Oracle database using RMAN, determine how long you need to retain the
backup and recovery records in the control file and set the retention value using the database
parameter CONTROL_FILE_RECORD_KEEP_TIME. By default, the value for this parameter is set to
7. This means that Oracle will maintain the backup and recovery information in the control file for a
period of 7 days. Now, if you perform a point in time recovery to a period greater than 7 days, the
restore operation fails. You can view the current setting of the CONTROL_FILE_RECORD_KEEP_TIME
parameter as follows:
SQL> show parameter CONTROL_FILE_RECORD_KEEP_TIME;
It is always recommended that you set the CONTROL_FILE_RECORD_KEEP_TIME parameter to a value
Page 88 of 199
greater than the RMAN retention period. Otherwise, you will have backups available in the backup
media without any related backup information in the control file. For more information, refer Oracle
documentation.
For Oracle and Oracle RAC iDataAgents, if the Oracle Instance (SID) name is different from the
database name or if the Oracle Instance (SID) name configured in the CommCell is different from the
actual instance name (case sensitive), then Oracle offline backups with lights out script may fail. In
such cases, you need to select the Use SQL Connect option in the Subclient Properties (Backup
Arguments) tab in order to connect to the database using the Connect String value configured for
the instance in the Instance Properties (Details) tab. Also, make sure that the Connect String value
does not include "/" when used with the Use SQL Connect option.
When Oracle and DB2 iDataAgents are installed on the same client, make sure that both Oracle and
DB2 users are part of the primary user groups.
For Oracle and Oracle RAC iDataAgents, selective online full backup jobs are not preemptable nor
restartable. Similarly, oracle log backup jobs that are submitted during selective online full backups
(data phase) also cannot be preempted nor restarted.
When restarting Oracle offline backup jobs, note that the job is restarted from the beginning rather
than from the point of failure.

Back to Top
Backup - Oracle - How To
Start a Backup
Schedule Backups
Start a Backup in the Suspended State
Start a Backup on New Media
Start a Backup that Marks Media Full on Completion
Start a Backup with a Set Job Priority
Start a Backup with Vault Tracking enabled
Start an Archive Log Backup
Enable (Disable) SnapProtect for a Subclient
Delete Archive Logs
Configure Autobackup of Control Files
Configure the Lights Out Script to Shut Down the Database for Offline Backups
Preview a Script
Validate a Backup or Restore
Start a Backup
Before You Begin
You can perform the following types of backup operations: Full, Incremental, Differential or
Synthetic Full.
Page 89 of 199
Read Full Backups before performing a Full Backup.
Read Incremental Backups before performing a Incremental Backup.
Read Differential Backups before performing a Differential Backup.
Read Synthetic Full Backups before performing a Synthetic Full Backup.
Required Capability: See Capabilities and Permitted Actions
To start an immediate backup job:
1. From the CommCell Browser, expand Client Computers by double-clicking Client Computers |
iDA File System | defaultBackupSet. The default and other subclients (if available) are displayed
on the right-hand windowpane.
2. To back up the default subclient, right-click the subclient, and click Backup.
3. From the Backup Options dialog box, select Run Immediately.
4. Select Full, Incremental, Differential or Synthetic Full backup.
In certain circumstances a non-full backup may automatically be converted to a full backup. For a
listing of these circumstances, see When a Non-Full Backup is Automatically Converted to a Full
Backup.
5. Click OK. You can track the progress of the backup job from the Job Controller window. If you are
using a stand-alone drive, you are prompted to load a specific cartridge into the drive. If you are
using a library, you will not receive this prompt. The system loads the tapes automatically. Your
cartridges should be appropriately labeled. This will enable you to locate the correct cartridge for a
restore job, if necessary.
6. When the backup has completed, the Job Controller displays Completed.
After running a backup, you may want to verify the backup data. You can do this by viewing the
Backup History. For more information, see Backup Job History.
Schedule Backups
You can also run backups of the following:
For a user-defined backup set or instance, right-click the backup set
you want to back up, click All Tasks, and click Backup All
Subclients.
For the Lotus Notes Document iDataAgent, to back up a partition,
right-click the partition you want to back up, click All Tasks, and
click Backup Default Backup Set.
For the Lotus Notes Database iDataAgent, to back up a partition,
right-click the partition you want to back up, click All Tasks, and
click Backup All Subclients.
For Agents that do not have backup set or instance levels, to back
up all subclients, right-click the agent icon, click All Tasks, and click
Backup All Subclients.
If you chose a level higher than subclient (i.e., backup set, etc.),
you are prompted to confirm that you want to back up all the
subclients below that level/node. Click Yes.
Starting a data protection operation on a backup set, instance or
agent level causes the system to start individual data protection
operations for each subclient contained therein. If the subclients
are associated with the same storage policy, then their operations
will run sequentially unless that storage policy is configured to
accommodate multiple data streams.
Page 90 of 199
You can schedule backups to occur with the following procedure. You will be prompted to create a
schedule for the data protection operation after selecting your data protection options.
Before You Begin
All Agents
Be sure all of the subclients are backed up, or scheduled to be backed up as needed, in order to
secure all of the data for the agent. Note this does not apply to archive operations.
To schedule a backup operation:
1. From the CommCell Browser, select one of the following:
To back up a subclient, right-click the subclient and click Backup.
To back up a backup set or instance, right-click the backup set or instance, click All Tasks, and
click Backup All Subclients.
To back up the default backup set, right-click the agent or instance node, click All Tasks, and
For the Lotus Notes Document iDataAgent, to back up a partition, right-click the partition you
want to back up, click All Tasks, and click Backup Default Backup Set.
For the Lotus Notes Database iDataAgent, to back up a partition, right-click the partition you
want to back up, click All Tasks, and click Backup All Subclients.
For Agents that do not have backup set or instance levels, to back up all subclients, right-click the
agent icon, click All Tasks, and click Backup All Subclients.
2. If you chose a level higher than subclient (i.e., backup set, etc.), you are prompted to confirm that
you want to back up all the subclients below that level/node. Click Yes.
3. From the Backup Options dialog box, select the type of backup that you want to initiate. In certain
circumstances a non-full backup may automatically be converted to a full backup. For a listing of
these circumstances, see When a Non-Full Backup is Automatically Converted to a Full Backup.
4. Click Schedule. Click OK to continue.
5. From the Schedule Details (Schedule Details) dialog box, create a schedule for this operation. For
step-by-step instructions, see Create a Job Schedule. Click OK to continue.
6. Your backup operation will execute according to the specified schedule.
Start a Backup in the Suspended State
Use the following procedure to start a backup in the suspended state.
Before You Begin
To start an immediate backup job with advanced backup options:
To backup a subclient, right-click the subclient to want to backup and click Backup.
Starting a data protection operation on a backup set, instance or agent
level causes the system to start individual data protection operations for
each subclient contained therein. If the subclients are associated with the
same storage policy, then their operations will run sequentially unless that
storage policy is configured to accommodate multiple data streams.
Page 91 of 199
To backup a user-defined backup set or instance, right-click the backup set you want to backup,
click All Tasks, and click Backup All Subclients.
To backup the default backup set, right-click the agent or instance node, click All Tasks, and
For Lotus Notes iDataAgent, to backup a partition, right-click the partition you want to backup,
click All Tasks, and click Backup Default Backup Set.
For Agents that do not have backup set or instance levels, to backup all subclients, right-click the
4. Select the type of backup that you want to initiate.
Backup.
5. Click the Advanced button to open the Advanced Backup Options dialog box.
6. Click on the Advanced Backup Options (Startup) tab, and select Startup in suspended state and
click OK.
7. From the Backup Options dialog box, click OK. You can track the progress of the backup job from
the Job Controller window.
8. If you are using a stand-alone drive, you are prompted to load a specific cartridge into the drive. If
you are using a library, you will not receive this prompt. The system loads the tapes automatically.
9. When the backup has completed, Job Controller displays Completed.
Start a Backup on New Media
Use the following procedure to start a backup on new media.
Before You Begin
Your cartridges should be appropriately labeled. This will enable you to
locate the correct cartridge for a restore job, if necessary.
Page 92 of 199
Backup.
6. Click on the Advanced Backup Options (Media) tab, and select Start new media and click OK.
If you would like jobs with other Job IDs to use this new media, also select the Allow other
schedule to use media set option.
Start a Backup that Marks Media Full on Completion
Use the following procedure to start a backup that marks media full on completion.
Before You Begin
Page 93 of 199
Backup.
6. Click on the Advanced Backup Options (Media) tab, and select Mark media full after successful
operation and click OK.
Start a Backup with a Set Job Priority
This option allows you to manually set a job priority. This is useful if you have jobs that are very
important and must complete, and/or jobs that can be moved to a lower priority. For more information,
see Job Priorities and Priority Precedence.
Before You Begin
Page 94 of 199
Backup.
6. Click on the Advanced Backup Options (Startup) tab, and select Change Priority and then enter a
value. Click OK to continue.
Start a Backup with Vault Tracking enabled
Use the following procedure to start a backup with Vault Tracking enabled.
For additional information, see the following:
VaultTracker
VaultTracker Enterprise
Before You Begin
secure all of the data for the agent.
1. select one of the following:
Page 95 of 199
Backup.
6. Click on the Vault Tracking tab, and select the vault tracking options you want to use and click
OK.
Start an Archive Log Backup
Use this procedure to backup archive logs.
Oracle and Oracle RAC iDataAgents provide the facility to backup archive log files based on certain
criteria.
Before You Begin
Oracle archives online redo log files once they become full. These logs can be used to recover
database transactions that have been lost due to an operating system or disk failure, by applying
them to an online backup in order to recover a database. Because of their importance in recovering
data, it is recommended that you create separate subclients for backing up archived redo log files.
Archived redo log files are always backed up as a full backup even if incremental is selected.
To start an archive log backup:
3. From the Backup Options dialog box, select the type of backup that you want to schedule.
4. Click Advanced.
5. From the Advanced Backup Options dialog box, click Backup Archive Logs tab, and select the
Page 96 of 199
criteria based on which the archive logs will be backed up.
6. Click OK. You can track the progress of the backup job from the Job Controller window.
Enable (or Disable) SnapProtect for a Subclient
Before you Begin
When you enable SnapProtect for a subclient, all the backups performed for the selected subclient will
be using the SnapProtect feature. Review SnapProtect, for more information.
To switch from SnapProtect to a traditional backup for this subclient, you must disable SnapProtect for
the subclient.
To enable (or disable) SnapProtect for a subclient:
1. From the CommCell Browser, right-click the subclient for which you wish to perform a SnapProtect
operation and click Properties.
2. From the Snap Backups tab, select (or clear) the Snap backup option to enable (or disable)
SnapProtect for the selected subclient.
3. Select the relevant snap engine from the Available Snap Engines.
4. Click OK.
Delete Archive Logs
Use this procedure to delete archive logs.
Oracle and Oracle RAC iDataAgents provide the facility to delete archive log files based on certain
criterion.
To delete archive logs:
You should select the snapshot engine applicable to your environment.
Page 97 of 199
4. Click Advanced.
5. From the Advanced Backup Options dialog box, click Delete Archive Logs tab, and select the
criteria based on which the archive logs will be deleted.
6. Click OK.
Configure Autobackup of Control Files
Related Topics
Oracle iDataAgent: Configuring Autobackup of Control Files
Oracle RAC iDataAgent: Configuring Autobackup of Control Files
To configure autobackup of the control file from the CommCell Console:
1. From the CommCell Browser, right-click the Oracle instance then click Properties.
2. From the Details tab of the Instance Properties dialog box, select one of the following options from
the selection list for the Ctl File Autobackup field:
Not Configure - Disables autobackup of the control file.
Configure On - If the backup includes a datafile, then RMAN will not automatically include the
current control file in the datafile backupset, but will write the control file and server parameter
file to a separate autobackup piece. If the backup does not include a datafile, the control file and
server parameter file will be written to their own autobackup piece.
Configure Off - If the backup includes a datafile, then RMAN automatically includes the current
control file and server parameter file in the datafile backupset. RMAN will not create a separate
autobackup piece containing the control file and server parameter file.
3. Click OK to save your settings.
4. After autobackup has been enabled in the CommCell Console, the control file will be automatically
backed up every time you perform a backup from either the CommCell Console or command line.
To configure autobackup of the control file from RMAN:
1. Enter the following commands/parameters at the RMAN prompt (the catalog connect string is
optional):
$rman target <connect string for target> catalog <connect string for catalog>
RMAN>configure controlfile autobackup on;
For Example:
$rman target systemuser/systempass@rman92 RMAN>configure controlfile autobackup on;
2. After autobackup has been enabled in RMAN, the control file will be automatically backed up every
time you perform a backup from either the CommCell Console or command line.
Configure the Lights Out Script to Shut Down the Database for Offline
Backups
Related Topics
Page 98 of 199
Backup - Oracle iDataAgent
Backup - Oracle RAC
Subclients - Oracle RAC
Before You Begin
Do not change the backup arguments of a subclient that is being backed up.
Oracle iDataAgent: Review Configuring the Lights Out Script to Shut Down the Database for Offline
Backups for an overview of this feature.
Oracle RAC: Review Configuring the Lights Out Script to Shut Down the Database for Offline Backups
for an overview of this feature.
To configure the lights out script to shut down the database for offline backups on a subclient:
1. From the CommCell Browser, right-click the subclient whose lights out script you want to configure,
then click Properties from the shortcut menu.
2. Click the Subclient Properties Subclient Properties (Backup Arguments) tab, then configure the
following options as appropriate:
Select the Lights Out Script option to enable automatic execution of this script before backing
up the database.
For Oracle on Unix, select the Warning option to enable a warning message that will be
displayed on the physical node for users logged into the database, that the database will be shut
down.
For Oracle on Unix, in the Delay Time (min) field, enter the number of minutes that you want
the script to wait after sending out the warning message to the physical node before the system
attempts to shut down the database.
If you are configuring Oracle RAC, then skip to step 3, as the remaining options in this step apply
only to the Oracle iDataAgent.
In the Sleep Time (sec) field, enter the number of seconds that you want the script to wait
between retry attempts to shut down the database and check the status. This field is used by the
lights out script in the event that the first attempt to shut down the database was unsuccessful
after the Delay Time has expired.
In the Tries Number field below the Sleep Time (sec) field, enter the number of times that you
want the script to retry attempts to shut down the database when the Sleep Time (sec) field is
activated.
In the Sleep Time (min) field, enter the number of minutes that you want the script to wait
lights out script in the event that the Tries Number limit has been reached for the Sleep Time
(sec) field.
In the Tries Number field below the Sleep Time (min) field, enter the number of times that you
want the script to retry attempts to shut down the database when the Sleep Time (min) field is
activated.
Select the Use SQL Connect option to connect to the database using the SQL command
connect <connect string> as sysdba. The Connect String entry is configured in the
Instance Properties (Details) tab. Note that if this option is not selected, the CommServer sets
the service name using set oracle_sid=<Instance name> and connects to the database using
the connect /as sysdba command. The Instance name is displayed in the Instance Properties
(General) tab.
On AIX 64 bit platform, you should always use the SQL_CONNECT option to
shutdown and start the database in mount mode. This is required because
of the limitation in SQL Plus to connect using / when the EXTSHM variable is
set.
Page 99 of 199
3. Select any other options as appropriate, then click OK to save the changes.
Preview a Script
Related Topics
To preview a backup script:
1. From the CommCell Browser, right-click the subclient containing the data whose backup script you
want to preview, then click Backup.
2. From the Backup Options dialog, click Script Preview.
3. To change the script, click OK to close the preview window, then enter the desired changes on the
Backup Options and Advanced Backup Options dialogs, and click Script Preview again to see if
the script now reflects the configuration you want. Repeat this if necessary to achieve the desired
result.
4. Once you are satisfied with the script, perform one of the following actions:
To have the system run the script in RMAN, click OK to close the preview windows, then click OK
on the Backup Options dialog to save the current settings. This script will be executed the next
time that a backup is run for this subclient.
To run the script yourself in RMAN, you can copy and paste the script from the preview window
into a text file for that purpose (or select the Save as Script option on the Backup Options
dialog). Click OK to close the preview window. Click OK to save the subclient configuration
changes.
To preview a restore script:
1. From the CommCell Browser, right-click the instance containing the data whose restore script you
want to preview, select All Tasks, then click Restore (or click Browse Backup Data).
2. From the Oracle Restore Options (General) dialog, click Script Preview.
Restore Options and Advanced Restore Options dialogs, and click Script Preview again to see
if the script now reflects the restore settings you want. Repeat this if necessary to achieve the
desired result.
To have the system run the script in RMAN, click OK to close the preview window, then click OK
on the Restore Options dialog to save the current settings. This script will be executed the next
time that a restore is run for this instance.
into a text file for that purpose (or select the Save as Script option on the Restore Options
(Job Initiation) tab). Click OK to close the preview window. Click OK to save the restore
settings.
NOTES:
Copying the script from the preview window can be accomplished by pressing <CTRL><C> from the
CommCell Console.
Page 100 of 199
Related Topics
Oracle iDataAgent: Ensuring Successful Oracle Data Protection and Recovery Operations
Oracle RAC iDataAgent: Ensuring Successful Oracle Data Protection and Recovery Operations
See Also:
Backup - Oracle or Oracle RAC - Troubleshoot
Restore Data - Oracle or Oracle RAC - Troubleshoot
To validate a backup:
1. From the CommCell Browser, right-click the subclient containing the backup data you want to
validate, then click Properties.
2. Click the Backup Arguments tab, then select Validate and click OK.
3. Start a Backup for the subclient. A Validate job will run, which will cause RMAN to examine the
database and scan all of the backup pieces to verify that the backup can be successfully restored.
4. Once the Validate job completes you can view the log file for the job to determine whether there
were any errors in the validation. To view the log file:
From the CommCell Browser, right-click the subclient, click View and then click Backup History.
Click OK on the History Filter dialog.
On the Job History window, right-click the Validate job, then select View Log File. The RMAN
Output Log will display for the job.
If you determine that there are any errors in the validation, take the appropriate corrective action
before running the actual backup.
To validate a restore:
1. From the CommCell Browser, right-click the instance whose restore you want to validate, select All
Tasks, then click Restore.
2. From the Restore Options dialog, click Advanced.
3. Click the Options tab, then select Validate and click OK.
NOTE: For the Oracle iDataAgent, keep in mind that the Options tab is unavailable when the
Duplicate DB option is selected on the Restore Options (General) tab.
4. Start a Basic Restore for the Instance. A Validate job will run, which will cause RMAN to decide which
database pieces need to be restored and then scans them to verify their contents, but no output will
be created and no data will be over-written.
From the CommCell Browser, right-click the instance, click View and then click Restore History.
before running the actual restore.
Back To Top
Page 101 of 199
Restore Data - Oracle
Topics | How To | Full System Restore | Troubleshoot | Related Topics
Overview
Duplicate Database
Standby Database
No Re-Do Logs Option
Allocate Command Syntax for Oracle Command Line Restores on a Unix Cluster
Restoring the Recovery Catalog
Automatic Mode Switching
Multiplex Restores
Reset Database Incarnation
Disable Oracle Channel Restore Failover
Table Restores
Restoring Archive Logs
Restore Considerations for this Agent
Restore Destinations
In-Place Restore
Out-of-Place Restore
Cross-Platform Restores
Overview
The following page describes the agent-specific restore options. Additional restore options are accessible
from the Related Topics menu.
The Oracle iDataAgent supports the following types of restores:
Restoring and recovering individual datafiles
Restoring and recovering individual tablespaces
Restoring and recovering individual tables
Restoring and recovering whole databases
Restoring and recovering archive log files
Recovery involves two processes: restoring the physical datafiles, and then recovering the database.
After the necessary files are restored, the database will be recovered.
Additionally, the Oracle iDataAgent supports:
Restores from the Latest Full Backup
Point in Time Restores - recovers the database to a consistent state at a point-in-time by applying any
incremental database backups and Archive logs that have occurred between the time of the full
backup used for the restore and the restore itself.
Rename/redirect data during restore (See Redirect/Rename Data During Restore for more information)
Creation of a Duplicate Database or a Standby Database (See Duplicate Database for more
information)
Restores from a third-party command line (i.e., RMAN)
Restoring control files from autobackup (see Restore Control Files from Autobackup for step-by-step
instructions)
Page 102 of 199
All restores can be performed in-place, out-of-place or cross-platform. (See Restore Destinations below
for comprehensive information.)
For the Oracle iDataAgent restore operations can be performed from the client, iDataAgent, and instance
levels in the CommCell Browser.
When there is a problem with the Oracle database server or the operating system of the client computer
full system restores may be required. See Restore Data - Oracle or Oracle RAC - Full System Restore for
more information.
See Also:
Restoring Data from a Secondary Copy using a Third-Party Command Line
Running RMAN Scripts using the Command Line Interface
Duplicate Database
The duplicate database feature allows you use backups of the target database to create either of the
following:
Duplicate Database - This is a copy or subset of the target database and has a unique DBID. It is
independent of the primary database and can be registered in the same recovery catalog as the
primary database. Duplicate databases are typically created for testing or demo purposes.
Prior to creating a duplicate database, you need to perform the Prerequisite Setup Steps for Creating a
Duplicate Database.
Standby Database - This is a special copy of the primary database that does not have a unique
DBID, and is updated by applying archived redo logs from the primary database. Backups from the
standby database are interchangeable with backups of the primary database. For this reason, standby
databases can be especially useful when the primary database experiences a disaster such as a
hardware related failure or data corruption and it is not configured for a cluster failover. This feature is
supported for Oracle 9i and 10g.
The creation of a non-standby duplicate database or standby database can be in-place on the same
physical computer, or out-of-place on another computer. Furthermore, you have the choice of whether or
not to configure the Oracle SID in the CommCell Console as part of this operation. See the How To page
for step-by-step procedures on creating a duplicate database or a standby database.
No Re-Do Logs Option
The No Re-do Logs option, available from the Options tab in the Oracle Advanced Restore Options
dialog, allows you to perform a point-in-time restore of a database that was backed up in NOARCHIVELOG
mode. When enabled, RMAN suppresses the application of archived re-do logs so that only data from
incremental backups are applied. If you do not specify noredo, RMAN will search for archived re-do logs
after applying incremental backup data, and will issue an error message when it does not find them.
Allocate Command Syntax for Oracle Command Line Restores on a Unix Cluster
In order to perform Oracle command line restores on a Unix cluster, you need to use the following syntax
for the allocate command within the RMAN script:
allocate channel ChannelName type 'sbt_tape' PARMS="ENV=
(CVOraVMName=VirtualMachineName)";
where ChannelName can be chN (N is a stream number: 1, 2, ...) and VirtualMachineName
should be the name of the virtual machine.
Restoring the Recovery Catalog
The method that you use to restore the Recovery Catalog depends on the method that you have used to
back up the Recovery Catalog.
If you have exported the Recovery Catalog using the exp command, you must import the Recovery
Catalog into a new database using the imp command.
Page 103 of 199
If you have backed up the Recovery Catalog using the Oracle iDataAgent, you must use an appropriate
restore procedure provided in the How To page to restore the Recovery Catalog.
Automatic Mode Switching
When an Oracle restore job is submitted from the CommCell Console, the system will automatically check
to ensure that the database is in a valid mode for the type of restore you are performing. If the database
is not in the correct mode, the system will display a pop-up message informing you of this issue, at which
point you can choose to either allow the system to automatically switch the database to the correct mode
for the restore, or cancel the restore request and set the mode manually.
Automatic mode switching during Oracle restores is supported under the following conditions:
1. The database is OPEN for the entire database restore, and the system will put the database in
MOUNTED mode.
2. The database is OPEN for restoring tablespaces, and the system will put the tablespaces in OFFLINE
mode.
Also note that this feature is only supported when the CommServe and Oracle client are both at the
current software release version. For mixed mode environments, if a restore is attempted while the
database is OPEN, the system will still issue a pop-up message indicating it will automatically switch the
database into MOUNTED mode. However, since it is not supported in this scenario, you will need to
manually switch the database into MOUNTED mode.
Multiplex Restores
The Oracle iDataAgent on Unix can detect whether multiplexing was used during backups from which
data is being restored and then multiplex the data streams during restore. This allows restore jobs to
maximize the throughput of available data channels by multiplexing multiple data streams, which speeds
up the process of restoring data. In order to fully optimize the multiplex restore capability, we
recommend setting the number of restore streams to the same number of streams used by the backup
job. By default, multiplexing is disabled if the sEnableMultiplexRestore registry key is not applied. To
enable the automatic multiplexing of restores, create the sEnableMultiplexRestore registry key with a
value of Y.
For more information, see Data Multiplexing.
Reset Database Incarnation
Whenever you perform a point in time recovery of an Oracle or Oracle RAC database (10g or higher) with
RESETLOGS, a new incarnation of the database is created. All archive log files generated after the reset
logs will be associated to the new incarnation. However, in order to perform a point in time recovery from
a backup of a previous incarnation, you need to reset the current incarnation to the previous incarnation
value using the Set DB Incarnation option in Advanced Restore Options (Options) dialog box. For step-
by-step instructions on restoring a database to a previous point-in-time, see Restore and Recover an
Entire Database in ARCHIVELOG Mode to a Previous Point-In-Time.
You can retrieve the database incarnation value using the RMAN command LIST INCARNATION.
Disable Oracle Channel Restore Failover
In Oracle 10g or higher version, you can prevent a restore failover operation using the Disable Oracle
Channel Restore Failover option in the Oracle Advanced Restore Options (Options) dialog box.
If this option is de-selected (default) for a restore job, and if either a backup piece is inaccessible
(because it has been deleted from the database or the MediaAgent is offline) or a block in the backup is
Multiplexed restores for Oracle work best on the Oracle 9i platform.
Multiplexed restores for Oracle are always from the primary copy.
You can recover an Oracle 9i database to a previous incarnation when
using the recovery catalog.
Page 104 of 199
corrupted within the latest full backup, RMAN automatically searches for another usable copy of this
backup piece in the same library or another library. If no usable copies are available, RMAN starts
searching all prior backups for the most recent available backup that is usable for the current job until it
has exhausted all possibilities.
If this option is selected for a restore job, this will prevent job delays caused by RMAN trying to locate
another copy of the backup data to complete the restore operation.
Table Restores
You can restore and recover individual database tables from non-system tablespaces to the same
database or to another database. During a table restore, Data Protection Suite identifies the list of
tablespaces that contain the actual data, and it restores the data and the system tablespaces to a staging
path in an auxiliary Oracle instance, which either you or Data Protection Suite must create. You can use
the CommCell Console to export the data from the auxiliary instance and import it to a destination that
you choose, or you can leave the data in the staging path and import the data manually by using Oracle
import utilities.
In order to restore individual Oracle or Oracle RAC database tables, you need to select the Enable Table
Browse option in the Subclient Properties dialog for the subclient prior to a backup. Note that this option
can be enabled on only one subclient. Also, ensure that this option is not enabled on the LOGS-only
subclient. When this option is enabled, information such as Oracle tablespace, user ID and table name
mappings are stored in the CommServe during the backup operation. When you browse for backup data,
you can select the Table View option in the Browse Options dialog to view the list of database tables
of each user in a tree view and select multiple tables to restore them to a destination location.
If you want to create the auxiliary instance for the restore, you must select the Auxiliary Instance
option from the Oracle Restore Options (Table Restore) tab, and you must specify the auxiliary database
name and PFile location along with the staging path information by populating the appropriate fields. If
you create the auxiliary instance, you can specify the location of the instance either on the same client or
on a different client by providing the appropriate information in the Database Client field. The auxiliary
instance should be started in the NOMOUNT mode. See Prerequisite Setup Steps for Creating a Duplicate
Database for information on creating the auxiliary database on the destination host.
On the other hand, to allow the system to create the auxiliary instance, do not select the Auxiliary
Instance option. In such a case, Data Protection Suite will create the auxiliary instance with
tsrst<jobid>, where jobid is the ID number for the restore job. If Data Protection Suite creates the
auxiliary instance, the instance is by default included on your local computer. Since Data Protection Suite
will connect to the auxiliary instance using "/", ensure that the source instance does not include "/".
For step-by-step instructions on running a table restore, see Restore and Recover One or More Database
Table(s).
Restoring Archive Logs
Oracle and Oracle RAC iDataAgents enable you to restore archive logs using the Restore Archive Logs
option in the Advanced Restore Options (Restore) tab from the CommCell Console. You can restore all the
archive logs or logs based on log time or Log Serial Number (LSN).For step-by-step instruction on
restoring archive log files, see Restore Archive Log Files.
Restore Considerations for this Agent
Before performing any restore procedures for this agent, review the following information.
Before recovering the Oracle database to a point-in-time, read Caution on the Use of RESETLOGS.
You can preview the backup and restore scripts that will be submitted to RMAN to back up or restore
data on a client. Previewing the script before running a backup or restore is useful for identifying
Oracle Table Browse and Table Restore are not supported for data
backed up using Oracle SnapProtect.
Page 105 of 199
whether the selected backup or restore options will yield the desired result in the script. The script text
can be previewed from the Backup Options and Restore Options dialogs, and provides the capability
for you to copy the text from the display window for manual submission in RMAN, if desired.
In the event that you need to restore the backup repository contained in the control file when the
control file is lost and the recovery catalog is either lost or was never used, and you have previously
configured autobackup of control files, then follow the procedure to Restore Control Files from
Autobackup.
For Oracle 10g, if the instance is configured for autobackup with flash recovery, then restoring the
SPFile from the CommCell Console will not work. See Troubleshooting - Oracle and Oracle RAC
iDataAgents for available work-arounds.
After performing an Oracle restore operation from the CommCell Console where options were selected
for Redirect, Rename and Recover at the same time, you must click the Refresh button on the
Subclient Properties (Content) tab or run a backup after the restore operation has completed before
proceeding with another restore. This is necessary to ensure that the CommCell Console recognizes
the changes that were made to the Oracle database and control file, so that it reflects the current
structure of the database to be restored, otherwise the restore will fail.
When restoring an Oracle 10g database, if the backup data is not available due to a service failure or
an offline library, RMAN will automatically failover to the previous backup. However, if the backup data
becomes inaccessible during the restore operation, then the failover does not work. A bug has been
raised by Oracle regarding this issue. For more information, refer Oracle documentation.
When restoring an Oracle SP file from Autobackup, make sure that the database is in NOMOUNT
mode. To start the database in NOMOUNT mode you need to do the following:
Shut down the database
Start the database in NOMOUNT mode using the following command:
Startup force nomount
This command can be used only if you have the initSID.ora file in the below location:
$ORACLE_HOME/dbs for Unix (can be copied from
$ORACLE_HOME/admin/<instancename>/spfile folder)
$ORACLE_HOME/database for Windows (can be copied from
$ORACLE_BASE/admin/<instancename>/spfile folder)
Restore the SP file from the CommCell Console. Once the SP file is restored, make sure that you do
a database shutdown and startup once again.
You can restore multiplexed data only from a primary copy.
If the database is upgraded, the next backup that is run detects the new version. The version is
refreshed and displayed in the instance Properties dialog box and for the SQL Server iDataAgent, it is
displayed during a browse operation. For more information, see Browse Databases.
When recovering an Oracle or Oracle RAC database with flashback enabled, make sure to disable the
flashback option prior to recovery of the database, or else the recovery operation may fail. To disable
Page 106 of 199
the flashback, do the following:
1. Restore the control file and the database using the CommCell Console.
2. Start the database in MOUNT mode and disable the flashback option using the command:
alter database flashback off
3. Continue the recovery of the database from the CommCell Console.
Consider the following when performing a table restore operation:
During a table restore operation, if the restore job fails when the table is getting restored to the
auxiliary database using RMAN scripts, the job is kept in a pending state.
If the restore job fails when the table is getting imported from the auxiliary instance, the job is
shown as completed with errors and the user is advised to export table from the auxiliary instance
using exp or expdp command line interface. If the auxiliary instance option is not selected during
the restore, use the ORACLE_SID name to connect to the auxiliary instance. However, in this case,
the auxiliary database will not be cleaned up and user is expected to shutdown the auxiliary
instance after importing the tables manually. If both the restore and import operations completes
successfully, the auxiliary database will be cleaned up.
When restoring tables to a cross-machine, if the auxiliary instance option is selected for the restore,
you need to recover the database to a specified point-in-time or SCN number. The SCN number can
be retrieved from the Job Details (general) tab of the backup job.
You can restore a table to a specific failure point when you use an auxiliary instance during the
table restore operation.
Before you restore and recover tablespaces (partial database) out of place for this agent, be sure to
take the tablespaces offline if they are not already offline.
If you are trying to restore (only) tablespaces in place for this agent, and if an error message
indicating that you have to reset the logs is displayed, simply ignore the message and click Yes to
continue.
If you are trying to recover an entire database, tablespaces, or data files for this agent, and if an error
message advising you how to administer the Open DB option from the CommCell Console is
displayed, simply ignore the message. However, ensure that the database is in mount mode.
You can restore Oracle duplicate databases cross-platform only by using a point-in-time value or a
System Change Number (SCN). You can retrieve the SCN from the Jobs Details (General) tab for the
backup job.
When restoring backups with recovery catalog, the connect string details provided in the Instance
Properties (Details) tab will be automatically displayed in the Restore Options (General) tab.
During an On Demand restore or a regular restore operation from the CommCell Console, if the data
restore phase encounters problems, the restore job goes to pending and resumes from the beginning.
However, if the recovery phase of the operation encounters issue in opening database or incorrect
catalog, the job is completed with errors.
Restore Destinations
By default, the Oracle iDataAgent restores data to the client computer from which it originated; this is
referred to as an in-place restore. You can also restore the data to another Client computer in the
CommCell. Keep in mind the following considerations when performing such restores:
The destination client must reside in the same CommCell as the client whose data was backed up.
Note that when you perform restores other than in-place restores, the restored data assumes the
rights (i.e., permissions) of the parent directory.
The following section enumerates the types of restore destinations that are supported by the Oracle
iDataAgent. See Support Information - Restore Options - Restore Destinations for a list of Agents
supporting each restore destination type.
Page 107 of 199
In-Place Restore
Same path/destination
Out-of-Place Restore
Same path/destination
Different path/destination
Redirect/Rename Data During Restore
For the Oracle and Oracle RAC iDataAgents, one of the options available during a restore operation is
the ability to redirect datafiles and tablespaces to be restored to a new location. Additionally, datafiles
and tablespaces can be renamed during restore. Both of these operations can be performed from the
Redirect tab in the Oracle Advanced Restore Options dialog box. Redirecting and/or renaming datafiles
and tablespaces as they are restored allows them to be restored without overwriting existing datafiles
and tablespaces. This is also useful when restoring and recovering an Oracle database to a new host
with a different directory structure. While redirecting the tablespaces/datafiles, it is always
recommended that you redirect all of the restored tablespaces/datafiles. In other words, restore only
the tablespaces/datafiles that need to be redirected.
Cross-Platform Restores
Same Operating System - Different Version
Back to Top
Restore Data - Oracle or Oracle RAC - How To
Oracle iDataAgent or Oracle RAC iDataAgent
Redirect/Rename Data During Oracle Restore
Restore and Recover One or More Tablespace(s) in ARCHIVELOG Mode to the Current Time
Restore and Recover One or More Datafile(s) in ARCHIVELOG Mode to the Current Time
Restore Archive Log Files
Restore and Recover One or More Database Table(s)
Restore and Recover a Database to a New Host with the Same Directory Structure
Restore and Recover a Database to a New Host with a Different Directory Structure
Restore and Recover an Entire Database in ARCHIVELOG Mode to a Previous Point-In-Time
Restore and Recover an Entire Database in ARCHIVELOG Mode to the Current Time
Restore and Recover an Entire Database in NOARCHIVELOG Mode to the Latest Backup
Restore and Recover an Entire Database in NOARCHIVELOG Mode to a Point-In-Time
Restore and Recover One Control File from an Existing Control File
Restore and Recover All Control Files
Restore Control Files from Autobackup
Create a Duplicate Database on a Different Host without the Instance Configured
Page 108 of 199
Create a Duplicate Database on a Different Host with the Instance Configured
Create a Duplicate Database on the Same Host without the Instance Configured
Create a Duplicate Database on the Same Host with the Instance Configured
Preview a Script
Oracle iDataAgent
Create a Standby Database on a Different Host without the Instance Configured
Create a Standby Database on a Different Host with the Instance Configured
Create a Standby Database on the Same Host without the Instance Configured
Create a Standby Database on the Same Host with the Instance Configured
Redirect/Rename Data During Oracle Restore
Before You Begin
Review the general and agent-specific restore requirements accessed from Restore Backup Data prior
to performing any restore.
To redirect tablespaces and/or rename datafiles during an Oracle restore:
1. From the CommCell Browser, right-click the Oracle agent or instance that contains the datafiles you
want to rename/redirect on restore, click All Tasks and then click the available Browse command
(command names vary by agent).
2. Run a browse operation. See Browsing Data for a list of customized browse operations and their
step-by-step instructions. If you accept all defaults, you will be browsing the latest backups for the
selected data.
3. From the Browse window, Select Objects From the Browse Window for Restore.
4. From the General tab of the Oracle Restore Options dialog box, and the Job Initiation tab of the
Restore Options dialog box, select the options that you want to use.
5. Click Advanced.
6. From the Redirect tab of the Advanced Restore Options dialog box, redirect tablespaces and/or
rename datafiles for the restore operation. Specifically, do one of the following:
If you want to redirect all the tablespaces selected for restore to a new location, then select the
Redirect All Table Spaces to: checkbox and either type in a new location in the corresponding
entry field or click Browse to display the Browse for Restore Redirect Path window and
navigate to the new location.
If you want to redirect only certain tablespace(s) or datafile(s) to a new location, then select the
Redirect checkbox, click the desired object(s) in the Object column to highlight them, and either
type in a new location in the New Path entry field or click the Browse button to the right of the
New Path field to display the Browse for Restore Redirect Path window and navigate to the
new location. After specifying the New Path, click Apply. The specified location will now display in
the New Path column next to the selected object(s).
If you want to redirect all datafiles for a tablespace, select the Redirect checkbox, select the
desired tablespace from the Object column, and type in a new path in the New Path entry field.
After specifying the new path, click Apply. The new path for the datafiles will now display in the
New Path column next to the selected tablespace.
If you want to rename one datafile for a tablespace, select the Redirect checkbox, expand the
desired tablespace then select the desired datafile, and type in the full path with a new name in
the New Path entry field. After specifying the new name, click Apply. The new name for the
Page 109 of 199
datafile will now display in the New Path column next to the selected datafile.
7. Click OK to save your entries. This closes the Redirect tab.
8. Select any additional restore options from the tabs for the Advanced Restore Options dialog box and
then click OK.
9. If you want to schedule the job, select the Job Initiation tab from the Restore Options dialog box,
click Schedule, schedule the job, and then click OK. If you want to run the job now, accept or click
Run Immediately in the same tab and then click OK.
10. The progress of the restore job can be monitored using the Job Controller.
11. After the data has been restored, you will see a job completion message in the Job Controller and
Event Viewer.
Restore and Recover One or More Tablespace(s) in ARCHIVELOG Mode to
the Current Time
The following procedure describes the steps involved in restoring one or more lost tablespaces, without
the control file for a database running in ARCHIVELOG mode. This procedure restores and recovers the
tablespace(s) as follows:
From an online backup
Without the control file(s) (since it exists)
To the current time and to the original host
Using the Recovery Catalog
Before You Begin:
To restore and recover one or more tablespace(s) in ARCHIVELOG mode to the current time:
1. From the CommCell Browser, right-click the instance that contains the tablespace(s) you want to
restore and recover, click All Tasks and then click Restore.
2. From the Oracle Restore Options (General) dialog box, select the following options:
Click the name of the client computer with the tablespace(s) you want to restore in the
Destination Client box (if it is not already selected).
Select the Restore Data and Recover options.
Select the tablespace(s) you want to restore in The Latest Database View pane.
3. Click on the Advanced button and verify the following options are selected:
Restore Data - From the Latest Backup Advanced Restore Options (Restore)
Recover - Current Time Advanced Restore Options (Recover)
4. Click OK in the Oracle Advanced Restore Options window.
5. When restoring encrypted data, refer to Data Encryption.
Before the restore job is run, the system will check whether the database
is in the correct mode for this type of restore. If it is not, a message dialog
will inform you of this and offer to automatically switch the database into
the valid mode. When this happens, either click Yes on the message
dialog to have the system automatically switch the database to the valid
mode and continue the restore, or click No to manually switch the
database to the valid mode before proceeding.
Page 110 of 199
6. Optionally for Oracle RAC, from the Oracle Restore Options (Stream) dialog box, set the instance
restore order per stream allotment.
7. Begin or schedule the restore.
8. While the job is running you can right-click the job in the Job Controller and select Details to view
information on the job. After the data has been restored, you will see a job completion message in
the Job Controller and Event Viewer.
Restore and Recover One or More Datafile(s) in ARCHIVELOG Mode to
the Current Time
The following procedure describes the steps involved in restoring one or more lost datafile(s), from an
existing control file. The database containing these datafile(s) is running in ARCHIVELOG mode. This
procedure restores and recovers the datafile(s) as follows:
Before You Begin:
To restore and recover one or more datafile(s) in ARCHIVELOG mode to the current time:
1. From the CommCell Browser, right-click the instance that contains the datafile(s) you want to
restore and recover, click All Tasks and then click Restore.
Click the name of the client computer with the datafile(s) you want to restore in the Destination
Client box (if it is not already selected).
Open the database tree and select the datafile(s) you want to restore in The Latest Database
View pane.
3. Click the Advanced button and verify the following options are selected in the identified tab for the
Oracle Advanced Restore Options dialog box:
Restore Data - From the Latest Backup in Restore
Recover - Current Time in Recover
During the partial restore job, the system checks whether the selected
tablespaces are in the OFFLINE state. If they are not, the system will
automatically switch the tablespaces to the OFFLINE state.
Page 111 of 199
Before You Begin:
Make sure that the DBID value for the particular database is displayed in the Instance properties
dialog box. If you have not yet created an instance for the database, refer to Create/Modify an
Instance for more information.
To restore archive log files using the CommCell Console:
1. From the CommCell Browser, right-click the instance, select All Tasks then click Restore.
2. From the Oracle Restore Options (General) tab, select Restore Archive Log. You can also select
Restore Data and Recover options if required.
3. Click Advanced.
4. From the Advanced Restore Options (Restore) tab, select Restore Archive Logs.
5. Select any of the following criteria to restore the archive log files:
Select By Log Time to restore archive log with start time (mm/dd/yy:hh/mm/ss) and End time
(mm/dd/yy:hh/mm/ss).
Select By Log Serial Number (LSN) to restore archive logs based on the specified Log
Sequence Numbers (LSNs) that you specify. Specify the Start number (enter log sequence
number) and End number (enter log sequence number) to restore archive logs.
6. If you want to save the archive logs in a different location, enter the path in Target Directory field
or click Browse to select a new location.
7. Click OK to save the settings.
Restore and Recover One or More Database Table(s)
The following procedure describes the steps involved in restoring one or more database tables. This
procedure restores and recovers the tables as follows:
From an online backup with the Enable Table Browse option set on the Subclient Properties (Backup
Arguments: Options) tab
From the current time (by default) backup data or either the point-in-time (PIT) or System Change
Numbers (SCN) backup data
To the original host (by default) or to a cross-host client that is installed on the same CommServe and
to the Oracle instance that is configured in the CommCell
Using the Recovery Catalog (optional)
Before You Begin:
Ensure that the destination host has the same version of the operating system and Oracle version as
the source host.
Make sure that the backup was performed after enabling the table browse for the subclient. For step-
by-step instructions, see Enable Table Browse for the Subclient.
Perform the Prerequisite Setup Steps for Creating a Duplicate Database to create an auxiliary
database on the destination host.
Page 112 of 199
Ensure that all dependent tables are selected for restore by running the following Oracle command:
select constraint_name, constraint_type, table_name, R_constraint_name from
dba_constraints;
To restore and recover one or more database tables:
1. From the CommCell Browser, right-click the instance that contains the tables you want to restore
and recover, click All Tasks and then click Browse Backup Data.
2. From the Browse Options dialog box, select Table View.
3. Click OK.
4. In the Browse window, select the tables to be restored and click Recover All Selected.
5. From the Oracle Restore Options (General) tab, select, enter, or consider the following:
The Destination Client field will display the name of the client computer to which you want to
restore the Auxiliary Instance if you select the Auxiliary Instance option on the Oracle Restore
Options (Table Restore) tab (discussed in a later step) and enter a client name in the Database
Client list on this tab. The source client is the default computer.
Use the Catalog Connect fields to enter the connect string for the catalog database of the
source machine, or select the NO CATALOG option to disable the Catalog Connect fields.
6. Click Advanced and then the Recover tab, and choose a time for the restore. Current Time is the
default option. The point in time value will be displayed automatically in the Point In Time fields if
the PIT time has already been entered in the Specify Browse Time field in the Browse Options
dialog box.
7. From the Oracle Restore Options (Table Restore), select the required parameters.
The Paths Selected For Restore box will show the selected users and selected tables
If the Auxiliary Instance option is selected, this instance must be in NOMOUNT mode, the pfile
should be provided, and you will need to select a client name from the Database Client list. The
Auxiliary Instance should be configured on the CommCell. The source client is the default client.
The existing Auxiliary Instance will be overwritten by restoring tables.
When you provide an auxiliary instance, make sure that the temp.dbf file is removed from the
operating system in the specified auxiliary instance datafile location.
Ensure that the staging path that you specify has enough space. To determine space
requirements, preview the RMAN script before you run the restore by clicking Script Preview
from the Oracle Restore Options (General) tab. This script will show the system tablespaces and
the user tablespaces (containing tables) to be restored; however, it will not show the temporary
tablespaces used for the restore. Therefore, be sure to check the size of all these tablespaces
from your computer before you run the restore.
The Import Options option allows you to select any options that you want to restore tables.
Do Not Import option will export the tables and leave them in the staging area. You can import
the tables to the destination database later or at any time by using the appropriate import
utility.
Import to Source Database option will import tables to the source database.
Import to a Different Database option allows you to import selected tables to a different
database whose name must be entered in the Select Import Database field. This database
must be configured on CommCell of the same CommServe. The cross-machine can be selected
from the Select a Client list also.
Drop Table option will drop all selected tables if they have not been dropped manually from the
destination database.
8. For Oracle RAC only, from the Streams tab, select only one node with only one stream to submit the
job.
Page 113 of 199
9. Click OK.
Restore and Recover a Database to a New Host with the Same Directory
Structure (Oracle and Oracle RAC)
The following procedure describes the steps involved in restoring and recovering a database (either in
ARCHIVELOG or NOARCHIVELOG) mode to a new host, with the same directory structure.
Before You Begin:
When you perform a database restore to a new host the source and destination machines must have
the following features:
The same operating systems
The same Oracle version
The same database datafile directory structures
The same ORACLE_SID
Must be either a 32-bit or 64-bit system
In the destination machine
Install the Oracle iDataAgent or create the Oracle RAC client and configure as client in the same
CommServe in which the source machine resides
Create and configure a new Oracle instance, similar to the one existing in the source machine
In addition the destination machine must have sufficient disk space to accommodate the restored
database.
To restore and recover a database to a new host with the same directory structure:
1. Verify that the destination machine's init <SID>.ora file is the same as the source machine's file.
2. Configure the destination machine's $TNS_ADMIN/tnsnames.ora file to include the Recovery Catalog
database's service entry. The easiest way to configure this file is to copy the Recovery Catalog
database's service entry from the source machine's tnsnames.ora file and append it to the
destination machine's tnsnames.ora file. The Recovery Catalog database's service entry should look
similar to the following:
<service_name> =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = <protocol>)(HOST = <host>) (PORT = <##>))
(CONNECT_DATA = (SID = <Recovery Catalog database>)))
3. Make sure that ORACLE_SID is set to the database that you are restoring and that ORACLE_HOME is
set appropriately. Note the following example for Solaris:
#export ORACLE_SID= <target database SID>
#export ORACLE_HOME= <Oracle home directory>

Note the following example for Windows 2000 machines:
C:\set ORACLE_SID= <target database SID>
C:\set ORACLE_HOME= <Oracle home directory>
4. From Server Manager or SQL Plus on the source machine, create a new user account within the
Recovery Catalog for the destination machine by executing the commands in the following display:
SVRMGR>create user <username> identified by <password>
When you are restoring data from a database in NOARCHIVELOG mode,
you must always restore and recover the entire database.
Page 114 of 199
2>temporary tablespace <temp_tablespace_name>
3>default tablespace <default_tablespace_name>
4>quota unlimited on <default_tablespace_name>;
Statement processed.
SVRMGR>grant connect, resource, recovery_catalog_owner to <username>;
5. Transfer the Oracle password file "orapw<Oracle SID name>" from the source machine to the
destination machine. Usually this file resides in ORACLE_HOME/dbs.
6. From the source machine, use the Oracle exp command to export the Recovery Catalog data. You
are exporting the data by user. For example, if the user ID for the Recovery Catalog owner is rman,
you would export the database backup information for the user rman.
7. From the source machine, use the Oracle imp command to import the contents of the file you
created in the previous step into the new user account for the destination machine. Depending on
the version of Oracle that you are running, you may receive the following error when you run the
imp command:
IMP-00044: unable to allocate enough memory for statement
8. Perform these steps if you receive an error while running the imp command:
Drop the user.
Recreate the user.
Rerun the imp command.
When you rerun the imp command, enter 1000000 when prompted for the insert buffer file.
If you receive the error message again, repeat the preceding steps and increase the buffer by a
million each time you run imp until the error message is no longer displayed.
9. Ensure that the database in NOMOUNT mode in the destination machine.
10. If you want to perform the cross-machine restore from the CommCell Console then continue on with
this procedure. Otherwise, if you want to perform the cross-machine restore from the RMAN
command line using your own custom script, then exit this help and run the script now (refer to
Oracle's Recovery Manager documentation for more information).
11. From the CommCell Browser, right-click the instance that contains the database you want to restore
and recover to a new host, click All Tasks and then click Restore.
12. From the Oracle Restore Options (General) dialog box, select or enter the following:
Click the name of the client computer to which you want to restore in the Destination Client
box.
destination machine.
Select the Restore Control File option.
Make sure that the <username>you supply for the destination machine is
different than the username for the source machine.
When you are granting the user database permissions, make sure to
include the recovery_catalog_owner option shown above.
If your destination client is not listed, check and ensure that all the
requirements stated in the Before you Begin section is satisfied.
It is critical that the Recover option is selected, as Recover applies any
incremental backups that are needed to bring the database back to a
consistent state.
Page 115 of 199
Select the entire database in The Latest Database View pane (if it is not already selected).
Restore Control File - To Point in Time in Ctrl & SP Files
Restore Data in Restore
Recover - Point In Time in Recover
14. Click OK in the Oracle Advanced Restore Options dialog box.
18. View the progress of the restore in the Job Controller window.
In ARCHIVELOG mode - When the data is restored, click OK on the confirmation window. If
desired, click Detail to review information on the restore operation.
In NOARCHIVELOG mode - The job will report the restore as failed. This is because no archive
redo log files exist. RMAN will report the following message, in reference to this error:

RMAN-03022: compiling command: recover(4)
RMAN-03026: error recovery releasing channel resources
RMAN-08031: released channel: ch1
RMAN-00571:
======================================================
RMAN-00569:====== ERROR MESSAGE STACK FOLLOWS=========
RMAN-00571:
======================================================
RMAN-03002: failure during compilation of command
RMAN-03013: command type: recover
RMAN-06054: media recovery requesting unknown log: thread 1 scn 72077
RMAN>
Recovery Manager Complete.
Perform the following steps if your database is in the NOARCHIVELOG mode.
19. Manually recover and open the database using the following steps.
20. From the Server Manager window, execute the command displayed in the following example:
SVRMGR>recover database using backup control file until cancel;
The Control file must be restored to a point in time that is later than or
equal to time set for the Restore Data option in the Restore tab.
The Restore Data option must be earlier than or equal to the point in time
that you specified for the Restore Control File option in the Ctrl & SP
Files tab.
The point in time for the recover option must be later than or equal to the
point in time specified for the Control file in the Ctrl & SP Files tab.
Page 116 of 199

Server Manager displays several messages, including the following:
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
21. Type cancel

The following message is displayed:
Media recovery cancelled.
22. Execute the commands displayed in the following example:
SVRMGR>alter database open resetlogs;
SVRMGR>exit
23. Reset the Recovery Catalog by executing the commands displayed in the following example:
#rman rcvcat <catalog connect string>
Recovery Manager: Release 8.1.5.00 - Production
RMAN-06008: connected to recovery catalog database
RMAN>connect target;
RMAN-06005: connected to target database: <database_name> DBID=<##>)
RMAN> reset database;
RMAN-03022: compiling command: reset
RMAN-03023: executing command: reset
RMAN-08006: database registered in recovery catalog
RMAN-03023: executing command: full resync
RMAN-08002: starting full resync of recovery catalog
RMAN-08004: full resync complete
RMAN>exit

Resetting the Recovery Catalog creates a new incarnation of the database. Before you can restore
and recover the database to the current time, you must perform another full backup and wait for it
to complete successfully.
24. Perform an immediate offline full backup.
Restore and Recover a Database to a New Host with a Different
Directory Structure (Oracle and Oracle RAC)
The following procedure describes the steps involved in restoring and recovering a database (either in
ARCHIVELOG or NOARCHIVELOG) mode to a new host, with a different directory structure.
Before You Begin:
When you perform a database restore to a new host the source and destination machines must have
The same operating systems
The same Oracle version
Different database datafile directory structures
The same ORACLE_SID
Must be either a 32-bit or 64-bit system
In the destination machine
Install the Oracle iDataAgent or create the Oracle RAC client and configure as client in the same
CommServe in which the source machine resides
Page 117 of 199
Create and configure a new Oracle instance, similar to the one existing in the source machine
In addition the destination machine must have sufficient disk space to accommodate the restored
database.
To restore and recover a database to a new host with a different directory structure:
1. Copy the init<SID>.ora from the old host to the new host.
2. Edit the init<SID>.ora file on the new host to reflect all the directory structure changes (i.e., change
the path for control files, archivelog destination and *dump destinations).
3. Create the directory structures as defined in init<SID>.ora file for all paths.
4. Configure the destination machine's $TNS_ADMIN/tnsnames.ora file to include the Recovery Catalog
database's service entry. The easiest way to configure this file is to copy the Recovery Catalog
database's service entry from the source machine's tnsnames.ora file and append it to the
destination machine's tnsnames.ora file. The Recovery Catalog database's service entry should look
similar to the following:
<service_name> =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = <protocol>)(HOST = <host>) (PORT = <##>))
(CONNECT_DATA = (SID = <Recovery Catalog database>)))
5. Make sure that ORACLE_SID is set to the database that you are restoring and that ORACLE_HOME is
set appropriately. Note the following example for Solaris:

Note the following example for Windows 2000 machines:
C:\set ORACLE_SID= <target database SID>
C:\set ORACLE_HOME= <Oracle home directory>
6. From Server Manager or SQL Plus on the source machine, create a new user account within the
Recovery Catalog for the destination machine by executing the commands in the following display:
SVRMGR>create user <username> identified by <password>
2>temporary tablespace <temp_tablespace_name>
3>default tablespace <default_tablespace_name>
4>quota unlimited on <default_tablespace_name>;
SVRMGR>grant connect, resource, recovery_catalog_owner to <username>;
7. Transfer the Oracle password file "orapw<Oracle SID name>" from the source machine to the
destination machine. Usually this file resides in ORACLE_HOME/dbs.
8. From the source machine, use the Oracle exp command to export the Recovery Catalog data. You
are exporting the data by user. For example, if the user ID for the Recovery Catalog owner is rman,
you would export the database backup information for the user rman.
9. From the source machine, use the Oracle imp command to import the contents of the file you
created in the previous step into the new user account for the destination machine. Depending on
the version of Oracle that you are running, you may receive the following error when you run the
imp command:
IMP-00044: unable to allocate enough memory for statement
Make sure that the <username>you supply for the destination machine is
different than the username for the source machine.
When you are granting the user database permissions, make sure to
include the recovery_catalog_owner option shown above.
Page 118 of 199
10. Perform these steps if you receive an error while running the imp command:
Drop the user.
Recreate the user.
Rerun the imp command.
When you rerun the imp command, enter 1000000 when prompted for the insert buffer file.
If you receive the error message again, repeat the preceding steps and increase the buffer by a
million each time you run imp until the error message is no longer displayed.
11. Ensure that the database in NOMOUNT mode in the destination machine.
12. If you want to perform the cross-machine restore from the CommCell Console then continue on with
this procedure. Otherwise, if you want to perform the cross-machine restore from the RMAN
command line using your own custom script, then exit this help and run the script now (refer to
Oracle's Recovery Manager documentation for more information).
When performing cross-machine restore, do the following:
Restore the control file and put the database in MOUNT mode.
Login to SQL database in the destination computer and provide the following syntax:
SQL> alter database rename file '/oracle/oradata/rman10g1/redo01.log' to
'/space/oracle/oracle10g2/oradata/redo01.log';
Here, '/oracle/oradata/rman10g1/ is the source redo log location and
'/space/oracle/oracle10g2/oradata/ is the destination redo log location.
and recover to a new host, click All Tasks and then click Restore.
14. From the Oracle Restore Options (General) dialog box, select or enter the following:
Click the name of the client computer to which you want to restore in the Destination Client
box.
destination machine.
If your destination client is not listed, check and ensure that all the
requirements stated in the Before you Begin section is satisfied.
consistent state.
Page 119 of 199
Redirect All Table Spaces to, along with the path, in Redirect
16. Click OK on the Oracle Advanced Restore Options dialog box.
In ARCHIVELOG mode - When the data is restored, click OK on the confirmation window. If
desired, click Detail to review information on the restore operation.
In NOARCHIVELOG mode - The job will report the restore as failed. This is because no archive
redo log files exist. RMAN will report the following message, in reference to this error:

RMAN-03022: compiling command: recover(4)
RMAN-03026: error recovery releasing channel resources
RMAN-08031: released channel: ch1
RMAN-00571:
======================================================
RMAN-00569:====== ERROR MESSAGE STACK FOLLOWS=========
RMAN-00571:
======================================================
RMAN-06054: media recovery requesting unknown log: thread 1 scn 72077
RMAN>
Recovery Manager Complete.
Perform the following steps if your database is in the NOARCHIVELOG mode.
21. Manually recover and open the database using the following steps.

Files tab.
point in time specified for the Control file in the Ctrl & SP Files tab.
The path for datafiles should be created manually because Oracle or Oracle
iDataAgent will not create that path.
Page 120 of 199
23. Type cancel

SVRMGR>exit
#rman rcvcat <catalog connect string>
RMAN>exit

Restore and Recover an Entire Database in ARCHIVELOG Mode to a
Previous Point-In-Time
The following procedure describes the steps involved in restoring and recovering a database to a previous
point-in-time. This procedure restores and recovers the database as follows:
With or without the control file(s) (since it must have a timestamp that is later than or equal to the
datafiles)
To a point-in-time and to the original host
Before You Begin:
To restore and recover an entire database in ARCHIVELOG mode to a previous point-in-time:
and recover, click All Tasks and then click Restore.
Click the name of the client computer with the database you want to restore in the Destination
Select the Restore Control File option, if you want to restore the control files.
Page 121 of 199
Verify that the Status of the database is displayed as STARTED; if necessary click on the
Refresh button to refresh the status.
3. Click on the Advanced button.
4. From the Ctrl & SP Files tab in the Oracle Advanced Restore Options dialog box, select the To Point
in Time in the Restore Control File pane and enter the date and time to which you want the
Control File(s) restored.
5. From the Restore tab, select the To Point in Time in the Restore Data pane and enter the date
and time to which you want the datafiles restored.
6. From the Recover tab, select the To Point in Time in the Recover pane and enter the date and
time to which you want the database recovered.
7. From the Options tab, type or select the database incarnation value in the Set DB Incarnation box,
if you want to perform the restore from a backup of a previous incarnation.
Restore and Recover an Entire Database in ARCHIVELOG Mode to the
Current Time
The following procedure describes the steps involved in restoring and recovering a database running in
ARCHIVELOG mode, with lost data files and control files.
The control file(s) must be restored to a point-in-time that is later than or
equal to the point-in-time set for the Restore Data option in the Restore
tab.
The data must be restored to a point-in-time that is earlier than or equal
to the point-in-time set for the Restore Control File option in the Ctrl &
SP Files tab.
The point in time that you specify for the Recover option must be later
than or equal to the point in time that you specified for the CONTROL FILE
in the Ctrl & SP Files tab.
If you recover the database to a previous point in time, or restore the
control file, then you have to perform a full database backup. This is
because a previous point in time recovery or restoring the control file will
destroy all previous backups.
Page 122 of 199
This procedure restores and recovers the database as follows:
With the control file(s) (since they no longer exist)
Before You Begin:
To restore and recover Restore an entire database in ARCHIVELOG mode to the current time:
Select the name of the client computer with the database you want to restore in the Destination
Verify that the Status of the database is displayed as STARTED; if necessary click on the Refresh
button to refresh the status.
Restore Control File (if you do not have one) in Ctrl & SP Files
The system automatically resets the logs and the database. Before you can restore and recover the
database to the current time, it is good practice to perform another full backup and wait for it to
complete successfully.
NOTES
If you restore the control file, then you have to perform a full database backup. This is because
Page 123 of 199
restoring the control file will destroy all previous backups.
Restore and Recover an Entire Database in NOARCHIVELOG Mode to the
Latest Backup
The following procedure describes the steps involved in restoring and recovering an entire database when
all datafiles and control files are lost. This procedure restores and recovers an entire database as follows:
From an offline backup
With the control files (since they no longer exist)
To the latest backup and to the original host
Before You Begin:
To restore and recover an entire database in NOARCHIVELOG mode to the latest backup:
Restore Control File in Ctrl & SP Files
you must always restore and recover the entire database
consistent state.
Page 124 of 199
Restore and Recover an Entire Database in NOARCHIVELOG Mode to a
Point-In-Time
The following procedure describes the steps involved in restoring and recovering an entire database when
all data files and control files are lost. This procedure restores and recovers an entire database as follows:
From an offline backup
With the control files (since they no longer exist)
To the latest backup and to the original host
Before You Begin:
To restore and recover an entire database in NOARCHIVELOG mode to a point-in-time:
If you restore the control file, then you have to perform a full database
backup. This is because restoring the control file will destroy all previous
backups.
consistent state.
Page 125 of 199
9. The job will report the restore as failed. This is because no archive redo log files exist. RMAN will
report the following message, in reference to this error:
RMAN-00569: =========error message stack follows============
RMAN-06038: recovery catalog package detected an error
RMAN-03013: command type: recover(4)
RMAN-20242: specification does not match any archivelog in the recovery catalog
Manually recover and open the database using the following steps.
10. Make sure that ORACLE_SID is set to the database you are restoring and that ORACLE_HOME is set
appropriately. Note the following example:
12. Type cancel
Files tab.
point in time specified for the Restore Control File in the Ctrl & SP Files
tab.
If you recover the database to a previous point in time and restore the
control file, then you have to perform a full database backup. This is
because a previous point in time recovery and restoring the control file will
destroy all previous backups.
Page 126 of 199
SVRMGR>exit
rman rcvcat <catalog connect string>
RMAN>exit
Restore and Recover One Control File from an Existing Control File
The following procedure describes the steps involved in restoring one lost control file from other control
files that exist.
Before You Begin:
To restore and recover one control file from an existing control file:
1. Shutdown the database.
2. Copy one of the existing control files to the missing control file.
3. Verify that new control file has the same owner, group, and file permissions as the original control
file.
4. Startup the database.
Restore and Recover All Control Files
Before You Begin:
If all control files have been lost and datafiles have been lost, restore and recover the control files
using the Restore and Recover an Entire Database in ARCHIVELOG Mode to the Current time
procedure.
Page 127 of 199
To restore and recover all control files:
1. Create a new control file using the Oracle create control file command.
For instructions, refer to your Oracle documentation.
2. Recover the database.
NOTES
After you restore the control file successfully, perform a full database backup. This is because
restoring the control file will destroy all previous backups.
Before You Begin:
To restore archive log files using the CommCell Console:
2. From the Oracle Restore Options (General) tab, select Restore Archive Log. You can also select
Restore Data and Recover options if required.
3. Click Advanced.
4. From the Advanced Restore Options (Restore) tab, select Restore Archive Logs.
5. Select any of the following criteria to restore the archive log files:
Select By Log Time to restore archive log with start time (mm/dd/yy:hh/mm/ss) and End time
(mm/dd/yy:hh/mm/ss).
Select By Log Serial Number (LSN) to restore archive logs based on the specified Log
Sequence Numbers (LSNs) that you specify. Specify the Start number (enter log sequence
number) and End number (enter log sequence number) to restore archive logs.
6. If you want to save the archive logs in a different location, enter the path in Target Directory field
or click Browse to select a new location.
Restore Control Files from Autobackup
Before You Begin:
Autobackup is only available in Oracle 9i and 10g. If you have not yet configured autobackup of
control files, refer to Configuring Autobackup of Control Files for more information.
Page 128 of 199
To restore control files from autobackup using the CommCell Console:
2. From the Oracle Restore Options (General) tab, click Advanced.
3. Click the Control and SP Files tab of the Oracle Advanced Restore Options dialog box, then select the
options for Restore Control File and From Autobackup.
4. Click the Options tab in the Oracle Advanced Restore Options dialog box, and select Set DBID. This
option will distinguish the target database from the rest of the databases that have the same name
in the recovery catalog.
5. Enter or select any other desired options on this tab, then click OK to save the settings.
To restore control files from autobackup using RMAN:
1. Start up the target instance in NOMOUNT mode.
2. Start RMAN, but do not issue any connect statements.
3. At the RMAN prompt, set the dbid (if you do not know the dbid, you can get it from the RMAN log of
the control file autobackup):
RMAN> set dbid=<your_DBID>;
4. After setting the dbid, connect to the target instance that has been started in NOMOUNT mode:
RMAN> connect target;
5. Enter the following commands/parameters from the RMAN prompt:
RMAN> run {
2> allocate channel ch1 type 'sbt_tape';
3> restore controlfile from autobackup;
4> }
6. Mount the database from the restored control file:
RMAN> alter database mount;
7. Restore and recover the database:
RMAN> run {
2> allocate channel ch1 type 'sbt_tape';
3> restore database;
4> recover database;
5> alter database open resetlogs;
6> }
RMAN> exit
Related Topics
Oracle iDataAgent: Ensuring Successful Oracle Data Protection and Recovery Operations
Oracle RAC iDataAgent: Ensuring Successful Oracle Data Protection and Recovery Operations
See Also:
Page 129 of 199
To validate a backup:
1. From the CommCell Browser, right-click the subclient containing the backup data you want to
validate, then click Properties.
2. Click the Backup Arguments tab, then select Validate and click OK.
3. Start a Backup for the subclient. A Validate job will run, which will cause RMAN to examine the
database and scan all of the backup pieces to verify that the backup can be successfully restored.
From the CommCell Browser, right-click the subclient, click View and then click Backup History.
before running the actual backup.
To validate a restore:
1. From the CommCell Browser, right-click the instance whose restore you want to validate, select All
Tasks, then click Restore.
2. From the Restore Options dialog, click Advanced.
3. Click the Options tab, then select Validate and click OK.
NOTE: For the Oracle iDataAgent, keep in mind that the Options tab is unavailable when the
Duplicate DB option is selected on the Restore Options (General) tab.
4. Start a Basic Restore for the Instance. A Validate job will run, which will cause RMAN to decide which
database pieces need to be restored and then scans them to verify their contents, but no output will
be created and no data will be over-written.
From the CommCell Browser, right-click the instance, click View and then click Restore History.
before running the actual restore.
Create a Duplicate Database on a Different Host without the Instance
Configured
The following procedure describes the steps involved in creating a duplicate database on a different host
without the instance configured.
Before You Begin:
Review information on the Duplicate Database feature before beginning this procedure.
Perform the Prerequisite Setup Steps for Creating a Duplicate Database.
Page 130 of 199
To create a duplicate database on a different host without the instance configured:
1. From the CommCell Console, right-click the source host instance then select All Tasks -> Restore.
2. From the Oracle Restore Options (General) dialog box, select the Duplicate DB checkbox and click
Advanced.
3. From the Duplicate tab in the Oracle Duplicate Options dialog box, select the Duplicate To
checkbox and enter the name for the duplicate database in the Database Name field. Click OK.
4. From the Oracle Restore Options (General) dialog box, select the Destination Client from the list
(when the instance is not configured, the destination client must be the source host) then enter the
Catalog Connect string and click Advanced.
5. From the Duplicate tab in the Oracle Duplicate Options dialog box, configure the following fields:
Pfile - For Oracle 10g and 9i, type in or Browse to the location of the Startup Pfile.
Open Restricted - For Oracle 10g, you can select this option if you want to open the database in
restricted mode.
Log File - Select this option, then specify Group or File and click the appropriate Add button to
enter specifications for the redo log group/file.
6. From the Recover tab in the Advanced Restore Options dialog box, select the appropriate recover
option.
7. Select any other desired options, then click Redirect in the Advanced Restore Options dialog box.
8. From the Redirect tab, choose one of the following then click OK:
To redirect all tablespaces to the same location, select the Redirect All Table Spaces to:
checkbox then type in or Browse to the new path.
To redirect tablespaces/datafiles to different locations, select the Redirect checkbox then click
the desired objects in the Object column to highlight them, and either type in or Browse to the
new path. Click Apply. Repeat this process until all tablespaces/datafiles have been redirected.
9. From the Duplicate DB Options tab in the Oracle Duplicate Options dialog box, configure the
following options as desired:
Time Zone - Select a time zone for a point-in-time recovery.
No Filename Check - Select this option to prevent RMAN from performing a check for target
datafiles sharing the same names as the duplicated files to see if they are in use. This option is
required when you are using the same path (i.e., the standby and primary datafiles and logs have
identical filenames).
10. Click OK on the Advanced Restore Options dialog box.
11. Begin or schedule the restore. Once the job begins, if you see a pop-up message about the database
state, ensure that the duplicate database is in NOMOUNT mode then click Yes to continue.
12. Verify that the restore completed successfully and that the database is restored to the destination
host. If you selected the Recover option verify that the database is consistent.
Create a Duplicate Database on a Different Host with the Instance
To redirect the database temp file, use the DB_FILE_NAME_CONVERT
parameter in the initial file for the new database instance. Similarly, to
redirect the log files, you can either use the LOG_FILE_NAME_CONVERT
parameter in the initial file or use the Log File option in the Advanced
Restore Options (Duplicate) dialog box. For more information on setting
the parameters in the initial file, see Prerequisite Setup Steps for Creating
a Duplicate Database.
Page 131 of 199
Configured
The following procedure describes the steps involved in creating a duplicate database on a different host
with the instance configured.
Before You Begin:
To create a duplicate database on a different host with the instance configured:
2. From the Oracle Restore Options (General) dialog box, select the Duplicate DB checkbox and click
Advanced.
3. From the Duplicate tab in the Oracle Duplicate Options dialog box, select the Duplicate To
checkbox and enter the name for the duplicate database in the Database Name field. Click OK.
then enter the Catalog Connect string and click Advanced.
restricted mode.
option.
Page 132 of 199
Create a Duplicate Database on the Same Host without the Instance
Configured
The following procedure describes the steps involved in creating a duplicate database on the same host
Before You Begin:
To create a duplicate database on the same host without the instance configured:
2. From the Oracle Restore Options (General) dialog box, select the Duplicate DB checkbox then enter
the Catalog Connect string and click Advanced.
Duplicate To - Select this option then enter the name for the duplicate database in the
Database Name field.
restricted mode.
option.
Page 133 of 199
Create a Duplicate Database on the Same Host with the Instance
Configured
The following procedure describes the steps involved in creating a duplicate database on the same host
To create a duplicate database on the same host with the instance configured:
2. From the Oracle Restore Options (General) dialog box, select the Duplicate DB checkbox then enter
the Catalog Connect string and click Advanced.
Duplicate To - Select this option then enter the name for the duplicate database in the
Database Name field.
restricted mode.
option.
Page 134 of 199
Preview a Script
Related Topics
To preview a backup script:
1. From the CommCell Browser, right-click the subclient containing the data whose backup script you
want to preview, then click Backup.
2. From the Backup Options dialog, click Script Preview.
Backup Options and Advanced Backup Options dialogs, and click Script Preview again to see if
the script now reflects the configuration you want. Repeat this if necessary to achieve the desired
result.
To have the system run the script in RMAN, click OK to close the preview windows, then click OK
on the Backup Options dialog to save the current settings. This script will be executed the next
time that a backup is run for this subclient.
into a text file for that purpose (or select the Save as Script option on the Backup Options
dialog). Click OK to close the preview window. Click OK to save the subclient configuration
changes.
To preview a restore script:
1. From the CommCell Browser, right-click the instance containing the data whose restore script you
want to preview, select All Tasks, then click Restore (or click Browse Backup Data).
2. From the Oracle Restore Options (General) dialog, click Script Preview.
Restore Options and Advanced Restore Options dialogs, and click Script Preview again to see
if the script now reflects the restore settings you want. Repeat this if necessary to achieve the
desired result.
To have the system run the script in RMAN, click OK to close the preview window, then click OK
on the Restore Options dialog to save the current settings. This script will be executed the next
time that a restore is run for this instance.
into a text file for that purpose (or select the Save as Script option on the Restore Options
(Job Initiation) tab). Click OK to close the preview window. Click OK to save the restore
Page 135 of 199
settings.
NOTES:
Copying the script from the preview window can be accomplished by pressing <CTRL><C> from the
CommCell Console.
Create a Standby Database on a Different Host without the Instance
Configured
The following procedure describes the steps involved in creating a standby database on a different host
Before You Begin
Review the general restore requirements accessed from Restore Backup Data, and the agent-specific
restore requirements accessed from Restore Data - Oracle prior to performing any restore.
Prerequisite Setup Steps:
From the RMAN command line, run an online full backup with CURRENT CONTROLFILE FOR
STANDBY of the primary database on the source host. This backup will be used to create the
standby database and standby control file.
Standby Database Preparation (We strongly recommend that you consult the Oracle9i or Oracle10g
Data Guard Concepts and Administration guide for more detailed information on this process):
Create the standby control file from the backup of the primary control file.
Choose filenames for the standby datafiles.
Choose filenames for the standby database online redo logs.
Set the necessary initialization parameters in the primary initialization parameter file (i.e.,
Startup PFile).
Create an initialization parameter file for the standby database and configure the necessary
parameters. Ensure that the Startup Pfile init<SID>.ora is copied from the destination host to
the target host with the same path as it is in the target host.
Perform any Oracle Net setup and configuration required to connect to the standby database.
For example, set up the listener and configure the destination computer's
$TNS_ADMIN/tnsnames.ora file for the standby database.
Start the standby database in NOMOUNT mode.
You must create a new instance on the same host before performing this procedure. The new
instance should be in NOMOUNT mode. There should be a valid connect string for the auxiliary
channel (used to duplicate the database). The system assumes and uses sys/change_on_install
for the auxiliary channel. However, you must use this connect string to connect to the auxiliary
database when the instance is not configured. Once the instance is configured, ensure that you set
the same password for the SYS user account for every primary and standby databases, for the redo
data transmission to succeed.
Do not create a new instance for the destination host in the CommCell Console.
Ensure that the Oracle iDataAgent is installed on the Destination host.
For Oracle 10g, ensure that you set the Standby Role Initialization
parameter, DB_FILE_NAME_CONVERT,to add all the temp data files from the
primary database location to the standby database location, as follows:
DB_FILE_NAME_CONVERT='<primary_database_temp_datafile_old
_location>','<standby_database_temp_datafile_new_location>'
If this parameter is not set, restore will fail with the following error
message:
temporary file TEMP01.DBF conflicts with file used by target
Page 136 of 199
To create a standby database on a different host without the instance configured:
2. From the Oracle Restore Options (General) dialog box, select the Duplicate DB checkbox and enter
the Catalog Connect string, then click Advanced.
3. Click the Duplicate DB Options tab, select the Duplicate For Standby option then enter the Oracle
System Identifier for the standby database in the Oracle SID field. Optionally, you may configure
any of the following options as desired:
Do Recover - Select this option to recover the standby database after it has been created.
4. Click the Recover tab, then select the appropriate recover option.
5. Click the Redirect tab, then choose one of the following and click OK:
6. Select any other applicable options in the Oracle Duplicate Options dialog box, then click OK.
(when the instance is not configured, the destination client must be the source host).
state, ensure that the standby database is in NOMOUNT mode then click Yes to continue.
Create a Standby Database on a Different Host with the Instance
Configured
The following procedure describes the steps involved in creating a standby database on a different host
Before You Begin
database
Page 137 of 199
Startup PFile).
parameters. Ensure that the Startup Pfile init<SID>.ora is copied from the destination host to
the target host with the same path as it is in the target host.
Configure the Oracle instance in the CommCell Console.
Ensure that the instances are saved properly in the CommCell Console, then open the instance
properties and verify that the Oracle instance status of the standby database is NOMOUNT.
To create a standby database on a different host with the instance configured:
message:
database
Page 138 of 199
Create a Standby Database on the Same Host without the Instance
Configured
The following procedure describes the steps involved in creating a standby database on the same host
Before You Begin
Startup PFile).
parameters.
Do not create a new instance for the destination host in the CommCell Console.
Page 139 of 199
To create a standby database on the same host without the instance configured:
Create a Standby Database on the Same Host with the Instance
Configured
The following procedure describes the steps involved in creating a standby database on the same host
Before You Begin
message:
database
Page 140 of 199
Startup PFile).
parameters.
Configure the Oracle instance in the CommCell Console.
Ensure that the instances are saved properly in the CommCell Console, then open the instance
properties and verify that the Oracle instance status of the standby database is NOMOUNT.
To create a standby database on the same host with the instance configured:
message:
database
Page 141 of 199
Back to Top
Basic Restore
Topics | How To | Related Topics
Overview
Time Range Options
Overview
There are two functions that help you retrieve backed up data from the backup media: Browse and
Restore. Browse operations allow you to view the data that has been backed up for a client computer
without actually restoring the data. Restore operations retrieve the data from the backup media and
restore it to the desired location.
In the CommCell Browser, the Browse and various Restore commands appear in the right-click menus at
the agent, instance and/or backup set levels, depending on agent.
Using the Restore commands, i.e., restoring without browsing, is most appropriate when you want to
restore the latest backup job for an agent, instance or backup set and want to retain the current file
structure.
In certain situations and for supported agents, Restore operations can run without utilizing the Browse
feature. For example, if you know the path/name of the volume of the data that you want to restore, you
can restore it without browsing. In these agents, this procedure is most appropriate when the number of
paths for the data that you want to restore is small or when the data that you want to restore is at a
single volume. If you want to restore data from many different paths or volumes, you should probably
select the data from the Browse window.
Time Range Options
In a Basic Restore, point-in-time data can be restored by specifying time range options in the Advanced
Restore Options (Time Range) dialog box. See Time Range Options for Basic Restore for step-by-step
instructions. When a time range is specified for a Basic Restore, the latest version of the backup job
within the given time range will be restored.
Basic Restore - How To
Basic Restore
Advanced Restore Options
Time Range Options for Basic Restore
Page 142 of 199
Basic Restore
Before You Begin:
to performing any restore operation.
To restore data without using browse:
1. From the CommCell Browser, right-click the agent, instance or backup set that contains the data you
want to restore, click All Tasks and then click the available Restore command (command names
vary by agent).
2. In the Restore dialog box, type the starting path of the data you want to restore.
3. From the Restore Options and Advanced Restore Options dialog boxes, select the restore
options that you want to use. When you accept all the default settings, you will be restoring the
selected data to its original location. See Restore Backup Data for complete information on the
agent-specific restore options.
4. After completing your selections, you can either start an immediate restore or schedule the restore.
If you want to schedule the job, click the Job Initiation tab from the Restore Options dialog box,
click Schedule, and enter your selections in the Schedule Details (Schedule Details) dialog box.
Clicking OK from this dialog box saves your schedule. See Scheduled Data Recovery Operations
If you want to run the job now, accept or click Run Immediately in the same tab and then click
OK.
You can monitor the progress of the restore job in the Job Controller. While the job is running, you can
right-click the job in the Job Controller and select Detail to view information on the job.
After the data has been restored, you will see a job completion message in the Job Controller and Event
Viewer.
Time Range Options for Basic Restore
Before You Begin:
To provide time range options for basic restore:
1. From the CommCell Browser, right-click the agent, instance or backup set that contains the data you
want to restore, click All Tasks and then click the available Restore command (command names
vary by agent).
2. In the Restore dialog box, type the starting path of the data you want to restore.
3. From the Restore Options and Advanced Restore Options dialog boxes, select the Time Range
tab.
4. In the Advanced Restore Options (Time Range) dialog box select Image Browsing option, if
required.
In the Specify Restore Time area select the Time Zone for the time range options. Select the
Exclude Data Before option and select the start date and time from which you wish to restore
data, and select the Browse Data Before option and select the end date and time until which you
wish to restore data.
Page 143 of 199
5. Click OK in the Advanced Restore Options dialog box.
6. Click OK in the Restore Options dialog box to execute the restore.
Back To Top
Browse and Restore
Overview
There are two functions that help you retrieve backed up data from the backup media: browse and
restore. In the CommCell Browser, the browse and variously-named restore commands appear,
depending on agent, in the right-click menus at the agent, instance and/or backup set levels.
Browse operations allow you to view data that has been backed up by the agent on the client computer
and select all or some of that data. Depending on the agent, there are several options available to
customize your browse. See Browse Data for comprehensive information on Browse operations.
Restore operations allow you to retrieve data from backup media and restore it to the desired location.
Restoring without browsing is most appropriate when you want to restore the latest backup job for an
agent, instance or backup set and want to retain the current file structure. See Basic Restore for more
information on restoring without using browse.
Browse and Restore
The Browse and Restore procedure is a sequential procedure that combines the two procedures. When
you select a Browse command from the CommCell Browser, you can define and run one of many
potential browse sequences. At the end of the browse, when you are looking at the resulting information
presented in the Browse window, you can continue with a restore procedure simply by selecting data and
clicking the Recover All Data button. As with the browse, depending on the agent, there are several
options available to customize your restore.
Perform a browse and restore operation when you want to:
restore from an earlier backup
restore only select files/objects
restore deleted files/objects
when you don't want or don't need to retain the current file structure
to utilize browse options
Browse and Restore - How To
Browse and Restore
Browse and Restore
Before You Begin:
Page 144 of 199
To browse and restore data:
1. From the CommCell Browser, right-click the agent, instance, backup set, or Legal hold set (for Legal
Hold data) that contains the data you want to restore, click All Tasks and then click the available
Browse command (command names vary by agent).
2. Run a browse operation. See Browse Data for a list of customized browse operations and their step-
by-step instructions. If you accept all defaults, you will be browsing the latest backups for the
selected data.
3. From the Browse window, Select Objects From the Browse Window for Restore.
4. From the agent's Restore Options and Advanced Restore Options dialog boxes, select the
restore options that you want to use. For agents with multiple tabs, do not click OK until you have
used all of the desired tabs. When you accept all the default settings, you will be restoring the
selected data to its original location. See Restore Backup Data for access to complete information on
the agent-specific Restore Destination options and procedures available.
5. When restoring encrypted data, refer to Data Encryption for comprehensive feature information and
procedures for using the Encryption tab of the Advanced Restore Options dialog box.
6. After completing your selections, you can either start an immediate restore or schedule the restore.
If you want to schedule the job, click the Job Initiation tab from the Restore Options dialog box,
click Schedule, schedule the job, and then click OK.
If you want to run the job now, accept or click Run Immediately in the same tab and then click
OK.
While the job is running, you can right-click the job in the Job Controller and select Detail to view
Back To Top
Page 145 of 199
Instances - Oracle
Overview
Configurable Properties
Overview
As Oracle instances reference a database, you must create an Oracle instance for each of the databases
that you want to back up.
See Instances for an overview of Instances. Given below is a list of what you need to provide before
creating an Oracle instance.
The Oracle User should have DBA and SYSDBA privileges
A name for the instance which should be the same name as the name of the database for which the
instance is created
The Windows user account or Unix Oracle User account which will be used to perform all system
operations
The path to the Oracle home directory
Storage policy to be used by the default subclient for data
Storage policies to be used by the instance for user command backups and archive log backups
The database connect string
The catalog connect string for the catalog database
The path to the TNS Admin directory (optional)
The block size for backup and restore operations (optional)
The pass-phrase to enable data encryption for RMAN command line backups (optional)
Software compression for Oracle Command Line Backups can be enabled or disabled at the instance level.
Software compression for Oracle Archive Logs Backups and data are managed through the subclient
level. When you change the compression scheme for Archive Logs you change it for data as well, and vice
versa.
You can also disable data compression by turning off both software and hardware compression.
Moving Instances
Oracle instances can be moved from one client computer to another within a CommCell. See Moving an
Oracle Instance for more information.
Once installed, the agent is configured and is therefore able to manage the data or volumes on the client
computer. However, you can change certain aspects of the instance configuration to manage the data in
the manner that best suits your needs.
You can view or change the instance configuration from the Instance Properties dialog box. The following
information can be configured.
Change the Designated Home Directory
For the Oracle, Oracle RAC, and SAP for Oracle iDataAgents, you can change the Oracle Home directory.
Similarly, you can change the Informix (Home) directory for the Informix iDataAgent, the Sybase Home
directory for the Sybase iDataAgent, the MySQL Home directory for the MySQL iDataAgent, and the
Instance Home directory for the DB2 DPF pseudo-client.
Page 146 of 199
See Change the Home Directory for step-by-step instructions.
Change Connect Details
For the Oracle and Oracle RAC iDataAgents along with the Quick Recovery Agent with Oracle, you can
view or change various settings of the selected instance (e.g., connect string, TNS Admin, block size for
backups and restores, use of the Recovery Catalog database for backups, configure control file for
autobackup). Some of these settings are also available for the SAP for Oracle iDataAgent. For Oracle,
Oracle RAC and SAP for Oracle, see Change Instance Details for step-by-step instructions. For Quick
Recovery Agent with Oracle, see Change Connect Details for step-by-step instructions.
Disabling RMAN Cross Check
For the Oracle and Oracle RAC iDataAgents, you can disable the synchronization of CommServe database
entries with the RMAN catalog during a data aging operation. For more information, see Data Aging.
For step-by- step instructions on disabling the RMAN cross check, see Disable RMAN Cross Check.
Use Encryption for Third-party Command Line Operations
When accessing the Encryption tab from the instance level, you are selecting either Network and/or
Media-side encryption for third-party Command Line operations. When accessing this same tab from the
subclient level, the settings selected apply only to the selected subclient content for operations run from
the CommCell Console. (See Data Encryption for an overview.) See the configuration section for your
agent for more information on this feature.
View and Change Instance-level Storage Policies
From the Storage Device tab, you can view or change the storage policy used to back up data via the
command line for the selected instance, select a storage policy for backing up logs on the selected
instance, or view or select a default storage policy for the selected instance. By defining a storage policy
for command line backups, you can view and track the status of those same jobs in the Job Controller. If
you redefine (i.e., select a new) storage policy for command line backups at the instance level, the
storage policy will apply only to any new command line backup jobs (i.e., those backup jobs that you
subsequently start). (See Storage Policies for an overview.) See the configuration section for your agent
for more information on this feature.
User Accounts
You can change the Windows or Unix user accounts that are used by the system to access the application
and in effect perform all data protection and recovery operations for the iDataAgent.
See Oracle iDataAgent section in User Accounts and Passwords for more information.
The following pertains to Oracle on Windows:
User Security
You can perform the following functions:
Identify the user groups to which this CommCell object is associated.
Associate this object with a user group.
Disassociate this object from a user group.
For more information, see User Administration and Security.
Back to Top
Instances - Oracle - How To
One or more of the agents of this type use one or more accounts that are
configured from a non-Properties dialog box. See the appropriate section
for your agent(s) in User Accounts and Passwords for more information.
Page 147 of 199
Create/Modify an Instance
Create an On Demand Instance
Delete an Instance
Change the User Account
Select a Storage Policy for Third Party User Commands
Configure Third-party Command Line Operations for Encryption
Change Account for Accessing Databases/Applications (Oracle on Windows)
Change Account for Executing Pre/Post Commands for Data Recovery (Oracle on Windows)
Disable RMAN Cross Check
Change Instance Details
Change the Home Directory
Create/Modify an Instance
Before You Begin
For the Oracle, Oracle RAC or SAP for Oracle iDataAgent, if you have custom SQL settings, you must
turn off these settings to ensure that the instance browse works correctly and that the instance status
is correctly fetched. To do this, create and edit the cvlogin.sql file with the appropriate contents at
ORACLE_HOME/sqlplus/admin. For example, run the following command:
edit file $ORACLE_HOME/sqlplus/admin/cvlogin.sql
Then include the following contents in the cvlogin.sql file:
set heading on;
set pause off;
Required Capability: See Capabilities and Required Actions
To create/modify an Instance
1. To create an instance, from the CommCell Browser, locate the correct client computer node, and
right-click the agent node for which you want the new instance created, click All Tasks, and then
click New Instance from the shortcut menu.
To modify an existing instance, from the CommCell Browser, right-click the instance you want to
modify, and then click Properties from the shortcut menu.
2. From the General tab, enter the name (up to 32 characters) for the instance. In addition, provide
the required access information for this instance.
For various iDataAgents, you can add/modify an application/database user account. See the
appropriate section as follows in User Accounts and Passwords for more information:
DB2 iDataAgent
Informix iDataAgent
Microsoft SQL Server iDataAgent
Oracle iDataAgents (Oracle, Oracle RAC, SAP for Oracle)
Page 148 of 199
Sybase iDataAgent
MySQL iDataAgent
3. If your agent uses the Details tab, enter the required database connect string and other optional
parameters.
For the Oracle, Oracle RAC and SAP for Oracle iDataAgents, see the Oracle iDataAgents section in
User Accounts and Passwords for more information.
4. From the Storage Device tab, select storage policy copies to be used for, as applicable, data
backups, command line data backups and log backups. Within these tabs you can click Data Paths to
display the details of the data paths associated with the primary storage policy copy of the selected
storage policy.
5. If your agent uses the Software Compression tab, and you want to enable software compression for
the selected backups, click the tab and select the option appropriate to your environment.
6. If you want to enable data encryption, from the Encryption tab select encryption settings for third-
party or RMAN command line backups.
7. Click OK to save the instance.
8. A message advises you to schedule backups for your new instance. It is recommended you elect to
set a schedule now. You can also associate this instance with an All Agent Types schedule policy
(which is automatically created by the system, or can be a user defined Data Protection schedule
policy). If you have already associated a schedule policy at a previous level (Agent, Client, or Client
Computer Group) the schedules defined in the Schedule Policy will be automatically applied to the
new instance. See Schedule Policy for more information.
For agents that offer an OK option, click OK to acknowledge the message. This procedure is now
complete.
For agents that offer Yes and No options to this message, click No if you don't want to create a
backup schedule at this time, and this procedure is complete. If you click Yes, a dialog box
prompts you to back up all subclients of this instance.
9. Click Yes. The Backup Options dialog box appears, which allows you to create the necessary
schedules.
11. If you want to access Advanced Backup Options, click Advanced.
12. After selecting the backup type and any advanced options, click OK. The Schedule Details dialog
box appears.
13. From the Schedule Details tab of the Schedule Details dialog box, select the scheduling options
that you want to apply, then click OK.
NOTES
A default subclient is created for the Oracle instance, which includes all the objects in the instance.
When you are done with this procedure, open the Subclient Properties dialog box for the default
subclient and verify that the Resync Catalog option available in the Backup Arguments tab is
selected. This would help you to successfully perform a full system restore in the event of destroyed or
damaged client.
After creating the instance for DB2, you can now create one or more Backup Sets for this instance.
Create an On Demand Instance
Related Topics
Running an RMAN Script using the Command Line Interface
Page 149 of 199
To create an On Demand Instance:
1. From the CommCell Browser, locate the correct client computer node, right-click the Agent for which
you want the On Demand Instance created, click All Tasks and then click New On Demand
Instance.
2. The On Demand Instance will display in the CommCell Browser, and its associated default Subclient
will appear in the right-hand pane.
3. If you wish to configure security for the On Demand Instance, right-click the On Demand Instance
then click Properties. Click the Security tab, enter the desired security settings then click OK.
4. Right-click the default Subclient of the On Demand Instance you just created, then click Properties.
You can configure any of the following properties for this subclient:
From the General tab, you can rename the subclient to another name of your choice, instead of
using default.
From the Pre/Post Process tab, you can establish processes to be run before or after certain
phases of the backup job.
From the Data Transfer Option tab, you can configure software compression, specify the number
of network agents, and set the throughput for network bandwidth throttling.
From the Activity Control tab, you can enable/disable jobs from running on the subclient.
Once you have finished configuring the subclient, click OK to save the changes.
NOTES
Once an On Demand Instance has been created, it cannot be changed into a traditional Instance.
Delete an Instance
Before You Begin
For most agents except Oracle and SQL Server, you cannot delete an instance if there is only one
instance present for an agent. To delete the final instance for most agents except the ones identified,
you must first remove the agent software from the client computer. For Oracle RAC, which does not
involve agent software, you can delete the instance under the RAC pseudo-client.
When you delete a specific instance positioned in the level below the corresponding agent or pseudo-
client in the CommCell Console, the following actions occur:
The corresponding backup data for that instance becomes immediately unavailable, thus making it
inaccessible for restore purposes. In effect, the backup data is deleted.
All child levels contained within the level are deleted in the CommCell Browser.
All job schedules and job histories that pertain to any of the levels within the deleted instance are
deleted.
If you delete an Oracle iDataAgent instance included within an Oracle RAC instance (node), the backup
data is not deleted, and it is available for restore by another eligible client.
You cannot delete an instance if it is being backed up. Attempts to delete an instance under such
conditions cause the deletion to fail. If a backup is in progress, either wait for the backup to complete
or kill the backup job using the Job Manager. Once the backup is no longer in progress, you can delete
the instance level.
To delete an instance positioned in the level below the corresponding agent or pseudo-client
1. From the CommCell Browser, right-click the instance that you want to delete, click All Tasks and
then click Delete.
2. Click Yes to confirm the deletion. (Clicking No cancels the deletion and retains the node.)
3. Type the requested phrase in the Enter Confirmation Text dialog box and click OK. This should
Page 150 of 199
delete the instance.
To delete an Oracle iDataAgent instance included within an Oracle RAC instance (node)
1. Right-click the Oracle RAC instance, click Properties, and click Details.
2. Click the instance that you want to delete within Client/Instance/Status and click Delete.
3. Repeat the previous step for each Oracle iDataAgent instance (except the last one remaining) within
the Oracle RAC instance that you want to delete.
4. Click OK. This should delete the Oracle iDataAgent instance(s).
Change the User Account
Before You Begin
Review Instances
Review Subclients
Required Capability Administrative Management
To change the user account
1. From the CommCell Browser, expand the agent tree, right-click the desired instance, and then click
Properties.
2. From the General dialog box, click the Change button associated with the User Account
information.
3. From the Impersonate NT User dialog box, enter the requested information.
Select a Storage Policy for Third-Party User Commands
When backing up data through third-party command line functions rather than the CommCell Console,
the specific storage policy for the backups of the affected non-Oracle RAC agents is established and
maintained through the Creating New Instance screen for the appropriate iDataAgent. For the Oracle
RAC iDataAgent, the storage policy is established when you create the associated pseudo-client or when
you modify the pseudo-client instance.
To select a storage policy for third-party user commands for non-Oracle RAC agents:
1. From the CommCell Browser, right-click the supported server/instance icon, click All Tasks, and
then click New Instance.
2. Within the Creating New Instance dialog box, click the Storage Device tab on server/instance
properties.
3. From the Command Line Backup tab, select from the list of existing storage policies
To select a storage policy for third-party user commands for the Oracle RAC iDataAgent:
1. From the CommCell Browser, if you are creating a RAC pseudo-client, right-click Client Computers,
click New Client, click RAC Client in the Add New Client dialog box, and then click OK. If you are
modifying the pseudo-client instance, right-click the instance and then click Properties.
With the exceptions noted above, you can no longer access the
corresponding backup data for restore purposes.
Page 151 of 199
2. Click Storage Device.
3. From the Command Line Backup tab, select from the list of existing storage policies.
4. Use the other tabs as appropriate to configure the subclient and then click OK to save your settings.
Configure Third-party Command Line Operations for Encryption
Encryption settings made at the instance level for third-party Command Line operations are not related in
any way to settings made at the subclient level. Subclient encryption settings are only for data protection
and recovery operations run from the CommCell Console.
See Data Encryption - Support for a list of supported products.
Before You Begin
Encryption must be enabled at the client level prior to configuring any instances residing on that client.
See Configure the Client for Data Encryption.
Required Capability: Capabilities and Permitted Actions
To configure the instance for encryption of third-party command line operations:
1. From the CommCell Console, right-click the instance and click Properties.
2. From the respective Encryption tab, select an option based on the criteria described in the
Encryption tab help.
3. Click OK to save your settings and close the properties dialog box.

Change Account for Accessing Databases/Applications
To change a user account for accessing DB2 databases:
1. From the CommCell Browser, expand the tree if necessary to view the desired level icon.
From the agent level, right-click the agent icon, click All Tasks from the short-cut menu, click
New Instance, and go to the next step.
From the instance level, right-click the instance icon, click Properties from the short-cut menu,
and go to Step 3.
From the backup set level, right-click the backup set icon, click Properties from the short-cut
menu, and go to Step 4.
2. Use the Creating New Instance dialog box to create and configure the instance. Thereafter, from
the General tab, click the Change button associated with the User Account information. Then go to
Step 5.
3. From the General tab of the Instance Properties dialog box, click the Change button associated
with the User Account information. Then go to Step 5.
4. From the General tab of the Backup Set Properties dialog box, ensure that the Connect as a
Different User option is selected. Then click the Change button associated with the User Account
information.
5. Enter the required information in the Set DB2 User Account dialog box.
For third-party Command Line data recovery operations to succeed when
using pass-phrase security, you must export the pass-phrase to the
destination client.
Page 152 of 199
To change a user account for accessing Oracle or SAP for Oracle applications on Windows not
associated with QR Agent:
1. From the CommCell Browser, expand the tree if necessary to view the desired level icon.
From the agent level, right-click the agent icon, click All Tasks from the short-cut menu, and
click New Instance (Oracle SID).
From the instance level, right-click the instance icon and click Properties from the short-cut
menu.
2. From the General tab, click the Change button associated with the User Account information.
3. Enter the required information in the Impersonate NT User dialog box.
To change a user account for accessing Oracle applications for QR Agent:
1. From the CommCell Browser, expand the tree if necessary to view the QR agent icon. Then right-
click the icon and click Properties.
2. From the Authentication tab, click the Oracle sub-tab.
3. From the Oracle sub-tab, either click Add Instance or select an Oracle instance to edit and then
click Edit Instance.
4. From the Add Oracle Instance to QR Agent dialog box, click Change.
5. Enter the required information in the Impersonate NT User dialog box.
To change a user account for accessing Informix, Oracle, or SAP for Oracle applications on Unix:
1. From the CommCell Browser, expand the tree if necessary to view the desired level icon. From the
agent level, right-click the agent icon, click All Tasks from the short-cut menu, click New
Instance, and go to the next step. From the instance level, right-click the instance icon, click
Properties from the short-cut menu, and go to Step 3.
2. Use the New Instance dialog box to create and configure the instance.
3. From the General tab of the Instance Properties dialog box, do one of the following, as appropriate.
For Informix, type the name of the user account in the INFORMIX USER field.
For Oracle or SAP for Oracle, type the name of the user account in the ORACLE USER field.
Change Account for Executing Pre/Post Commands (Data Recovery)
To change a user account for executing pre/post commands for Data Recovery jobs:
1. From the CommCell Browser, expand the tree to view the appropriate level icon for the affected
agent. Then right-click the icon and click All Tasks from the short-cut menu.
2. Click the appropriate Browse or Restore option. Then populate, select, and click as appropriate to
access the Restore Options dialog box.
3. From the Restore Options dialog box, click Advanced.
4. From the Advanced Restore Options, click the Pre/Post tab.
5. From the Pre/Post tab, select one of the account options in the Pre/Post Impersonation area. If
Page 153 of 199
you select Impersonate User, type the appropriate user name and password.
To change the connect details for the Oracle instance:
1. From the CommCell Browser, right-click the QR Agent and then click Properties.
2. Click the Authentication tab and then click the Oracle sub-tab. Click the Add (or Edit) Instance
button.
3. From the Details tab of the Properties dialog box, enter the target database connect string in the
Connect String box.
4. Establish or modify the path to the directory containing the listener.ora and tnsnames.ora files in
the TNS_ADMIN box by entering the path in the box or use Browse to establish the designated
Oracle Home directory.
Disable RMAN Cross Check
To disable the RMAN cross check for the Oracle instance:
1. From the CommCell Browser, right-click the instance and then click Properties.
2. From the Details tab of the Properties dialog box, select Disable RMAN Cross Check.
3. A warning message is displayed to inform that the RMAN Catalog will not be synched with the
CommServe. Click OK.
Change Instance Details
To change the instance details for Oracle or SAP for Oracle:
1. From the CommCell Browser, right-click the icon for any supported instance and then click
Properties.
2. From the Details tab of the Properties dialog box, to modify the Connect String information:
in the first box, enter the database ID
in the second box, enter the password for the user ID
in the third box, enter the Oracle service name
3. To modify the Use Catalog Connect information:
in the first box, enter the Recovery Catalog database user ID
See the Details tab help for user rights information.
Page 154 of 199
in the third box, enter the Recovery Catalog service name
4. To establish or modify the path to the TNS Administration path information, enter the path in the
box or use Browse.
5. To modify the block size used for backup and restore operations, enter a new value in the Block
Size field.
6. To configure autobackup of control files, select the desired option from the Ctrl File Autobackup
list.
7. For SAP for Oracle, to change the path to the SAP EXE folder, type the path to the SAP EXE folder in
the SAP EXE Folder (Required) field or use Browse to locate the path.
To change the instance details for Oracle RAC:
Properties.
2. From the Details tab of the Properties dialog box, to modify the Use Catalog Connect information:
in the first box, enter the Recovery Catalog database user ID
in the third box, enter the Recovery Catalog service name
3. From the same tab, to modify the block size used for backup and restore operations, enter a new
value in the Block Size field.
4. From the same tab, to configure autobackup of control files, select the desired option from the Ctrl
File Autobackup list.
5. From the same tab, click the appropriate Oracle client/instance/status and then click Modify.
6. From the Update Instance dialog box, to modify the Connect String information:
in the first box, enter the database ID
in the third box, enter the Oracle service name
7. To establish or modify the path to the TNS Administration path information, enter the path in the
box or use Browse.
8. Click OK to save your settings in the Update Instance dialog box.
9. Repeat Steps 5 through 7 for each Oracle client/instance/status that you want to modify.
10. Continue making settings as appropriate.
Change the Home Directory
To change the Home Directory:
Properties.
2. For agents other than Oracle RAC, from the General tab of the Properties dialog box, type the path
in the Home or Dir (Directory) box or use Browse to locate the path. Then go to Step 6.
See the Details tab help for user rights information.
Page 155 of 199
3. For the MySQL iDataAgent, from the General tab of the Properties dialog box, type the path in the
Binary Directory box or use Browse to locate the path. Also, type the path to the MySQL data
directory in the Data Directory box or use Browse to locate the path. Then go to Step 6.
4. For Oracle RAC, from the Details tab of the Properties dialog box, click the appropriate
client/instance/status and then click Modify.
5. In the Update Instance dialog box, enter the path in the Home box or use Browse to locate the
path.
7. Continue to make additional settings as desired.
Back to Top
Page 156 of 199
Subclients - Oracle
Overview
Subclient Content
Things to Consider when Creating and Configuring Oracle Subclients
Overview
The following table shows subclient creation and configuration details specific to the Oracle iDataAgent.
Before you back up data, you must define the data that you want to back up, and how this data should
be backed up. This is done by creating one or more subclients for the database you are backing up. For
the Oracle iDataAgent, a subclient defines:
Whether a backup will be offline or online
Whether the entire database will be backed up as a whole, or only a subset of objects within the
database
Whether the control files should be included in the database backup
Depending on your needs, you can create multiple subclients for one or all of the following:
Online Databases, with or without archive logs and control files
Online Subsets, with or without archive logs and control files
Offline Databases, with or without the control files
Selective Online Full Backups
Subclient Content
The Oracle iDataAgent is designed to back up and restore Oracle data files (*.dbf) along with control files
Agent
Type of
Data
Default
Subclient
created
during
install of
the
Agent
Supports
Default
Subclient
Supports
User
Defined
Subclient
Contents
of the
default
subclient
when
user-
defined
subclient
is present
Other
Types of
subclients
supported
by the
Agent
Notes
Oracle
Database
iDataAgent
Oracle
databases/
datafiles/
tablespaces
No Yes Yes database
objects not
assigned to
other
subclients,
unless
otherwise
configured*
None
Default
subclient is
created when
the instance is
configured
*See Caution
Against Re-
configuring
Default
Subclient
Content.
Page 157 of 199
(*.ctl) and archived redo log files. After you install an Oracle iDataAgent, a default subclient is created by
the system only after you first configure an Oracle database instance from the CommCell Console. Since
an Oracle instance references a database, the default subclient includes the entire database associated
with that instance. However, you can use the CommCell Console to create user-defined subclients to
include only some of the database content by configuring the Subclient Properties (Content) tab. Any
content that is not included in the user-defined subclients will remain in the default subclient.
When you configure subclient content, you click the Subclient Properties (Content) tab for the
subclient to view the eligible data for inclusion in the subclient content. You then select an option to
include one of the following in the subclient content: online database, offline database, one or more
online subsets of the database, archive log files, control files, Flash Recovery Area (for Oracle 10g or
higher), or the SP file. You can also choose to include selective online full backups for the subclient.
If you opt to include just online subsets in the subclient content, you click the appropriate option and
then select the desired table spaces and data files to configure the content for the subclient. Once you do
this, the subclient content may be displayed as follows:

In this example, suse11GR1 is the name of the instance, and this instance includes a single database. The
database includes six table spaces out of which two of the table spaces have been included in the
subclient content.
When creating user-defined subclients, it is recommended that you create a separate user-defined
subclient for the archive log files. Also, make sure to use separate storage policies for data backup, which
is set at the subclient level, and for log backup, which is set at the instance level.
A useful way to distribute subclient content for this iDataAgent is to create separate user-defined
sublients for frequently used table spaces and also for log files. For example, if the EXAMPLE and USERS
dbspaces shown above undergo frequent changes, you can create a separate subclient for each table
space. For example:
User-defined subclient: Test1
Content:
EXAMPLE
User-defined subclient: Test2
Content:
USERS
It is recommended that you create a separate user-defined subclient for the log files on the client. For
example:
User-defined subclient: Logs
Content:
(all the archive log files)
Distributing the client data using subclients in this way can help improve backup performance by
organizing the workload on the client into logical groupings.
Filtering
Page 158 of 199
Data protection filtering is not applicable for this agent.
Wildcards and Regular Expressions
Wildcards and regular expressions are not supported for this agent when defining subclient content.
Considerations
For more information, see Things to Consider when Creating and Configuring Oracle Subclients.
Once installed, the agent is configured and is therefore able to manage the data or volumes on the client
computer. However, you can change certain aspects of the subclient configuration to manage the data in
the manner that best suits your needs.
You can view or change the subclient configuration from the Subclient Properties dialog box. The
following information can be configured.
Activity Control
You can enable or disable all operations for this CommCell object and all objects below it. For more
information, see Activity Control.
Archive Log Destinations for Backup and Deletion
You can specify the location from where the archive logs will be backed up. You can also specify the
location from where archive files will be deleted. Either option allows you to create more than one
schedule with different log destinations on the same subclient.
See Select Archive Log Destinations for Backup or Deletion for a step-by-step procedure.
Archive Logs Backup and Deletion
You can backup and delete archive logs of an Oracle instance based on specific criteria. For detailed
information, see Advanced Backup/Archive Options. In the case of Oracle RAC, you can specify archive
redo log backups and deletions for one or more Oracle iDataAgent instances within an Oracle RAC node.
If the archive log is stored on a shared medium (e.g., NFS, CFS), all the archive logs for all the instances
can be backed up. On the other hand, if the archive log is on a local drive (i.e., not shared), only the
archived logs of the selected instances can be backed up.
See Configure the Subclient to Back up and Delete Archive Logs for step-by-step instructions.
Backup Arguments
Some database iDataAgents run backups using a system-generated script that is run behind the scenes
from a command line. The CommCell Console serves as a front-end user interface for specifying various
backup arguments and parameters that are passed to the backup script that is run. Depending on your
agent, you can specify, for example, the application-specific Backup Level, whether the backups will be
online or offline, as well as buffer and bundle sizes, among other settings. Although the backup
arguments/parameters vary among iDataAgents, they all function in a similar manner. These arguments
are set at the subclient level from the respective iDataAgent's Subclient Properties dialog box tab.
For step-by-step instructions, see Configure Backup Arguments.
From this tab for the Oracle iDataAgent, you can establish the maximum number of concurrent open
datafiles and the maximum allowable size for an RMAN backupset as well as other Performance Tuning
parameters. You can also Enable Table Browse for the Subclient to view and restore Oracle database
tables and Configure the Lights Out Script to Shut Down the Database for Offline Backups.
Always ensure that the archive logs are backed up prior to deleting them.
Page 159 of 199
Content/Databases
You can define the content of the subclient. Most agents include a configure button that displays a dialog
where you can add or modify the data included as subclient content. For step-by-step instructions, see
Configure Subclient Content.
Data Transfer Options
Several configurable options to efficiently use available resources for transferring data secured by data
protection operations are provided in the subclient. This includes the following:
Enable or disable Data Compression either on the client or the MediaAgent.
Configure the transfer of data in the network using the options for Network Bandwidth Throttling and
Network Agents.
Data Encryption
You can enable or disable the encryption of data for transmission over unsecure networks and for storage
on media. For more information, see Data Encryption.
Data Paths
You can view the data paths associated with the primary storage policy copy of the selected storage
policy or incremental storage policy. You can also modify the data paths for the subclient including their
priority. For additional information, see Configuring Alternate Data Paths for Subclients.
Pre/Post Processes
You can add, modify or view Pre/Post processes for the subclient. These are batch files or shell scripts
that you can run before or after certain job phases. For more information, see Pre/Post Processes.
You can also change the user account for running Pre/Post processes for data protection operations of
agents residing on Windows platforms. These agents include Active Directory, DataArchiver, DB2 on
Windows, Exchange, Image Level on Windows, Lotus Notes, NAS, Oracle on Windows, Image Level
ProxyHost on Windows, ProxyHost, Quick Recovery Agent, SAP for Oracle on Windows, SharePoint, SQL
Server, and Windows File System. For more information, see User Accounts and Passwords.
Storage Policies
You can associate the subclient to a storage policy. For more information, see Storage Policies.
Subclient Name
You can rename a subclient. For step-by-step instructions, see Rename a Subclient.
User Accounts
The following pertains to Oracle on Windows:
You can define an account with permissions to execute Pre/Post commands for the agent's archive,
backup, or volume creation jobs.
See Oracle iDataAgents: Other User Accounts in User Accounts and Passwords for more information.
Flash Recovery Area Backup
Flash Recovery Area is a specific area in the disk storage that exclusively holds a copy of all backup-
related components, such as image copies, redo logs, and control file auto backups. The Flash Recovery
Area facilitates faster restores of backup data and minimizes restores from tapes during data recovery
operations. This feature is available only in Oracle 10g. You can set up a Flash Recovery Area by
specifying the area size and location using RMAN parameters. You can also create a retention policy that
will specify when the backups can be deleted from the Flash Recovery Area. For more information, refer
to Oracle documentation. The Oracle and Oracle RAC iDataAgents allow you to enable backups of the
Flash Recovery Area.
For more information, see Enabling Backup of Flash Recovery Area.
Page 160 of 199
Things to Consider when Creating and Configuring Oracle Subclients
When creating and configuring subclients for the Oracle iDataAgent, keep in mind the following
considerations:
If you will be using Recovery Manager or Oracle Enterprise Manager to create backup and restore
scripts, you do not need to create subclients.
When scheduling backups of multiple subclients simultaneously for the Oracle iDataAgent, ensure that
you dont include the same datafile or table space in both subclients.
If you are running in NOARCHIVELOG mode, you must back up the database offline. If you are running
in ARCHIVELOG mode and database accessibility is a priority, an online backup of the database may
be appropriate. If the database must be accessible and you have a small backup window, you may
want to run a series of online backups in which different portions of the database are backed up at
different times. You may also want to combine all of these backup types in your backup strategy. Once
you have determined your backup needs, you can define your backup strategy by creating one or
more subclients for the database.
It is recommended that you include the control files with the appropriate database backups.
Oracle Automatic Subclient Updates:
When new objects are added to databases, the system automatically adds these objects to subclients;
you do not have to add them to subclients to ensure that they get backed up. This section explains
how the system determines which subclients are assigned new objects.
If a new datafile is added to a tablespace, it is assigned to the subclient that contains the
tablespace. For example, assume that you have created the following subclients for the accounts
database:
Then assume that the datafile users05.dbf is added to the user tablespace. This datafile will be
automatically added to the on_accounts and on_user subclients, but not to the on_sys subclient.
This is because the on_accounts and on_user subclients contain the user tablespace, but the
on_sys subclient does not.
If a new datafile is added to the database, and if none of the online subset subclients contain the
tablespace for the datafile, the datafile is assigned to the default subclient.
on_accounts An online database subclient that backs up the entire database.
on_user An online subset subclient that backs up the user tablespace.
on_sys An online subset subclient that backs up the system tablespace.

Subclients must contain the entire contents of a tablespace if you want
the system to automatically add a new datafile to the subclient. For
example, the on_user subclient must contain the files users01.dbf
through users04.dbf if you want the system to automatically add the
users05.dbf file. If the on_user subclient contains only the files
users01.dbf and users02.dbf, the system will not automatically add
users05.dbf to this subclient.
Page 161 of 199
Caution Against Re-configuring Default Subclient Content
We recommend that you do not re-configure the content of a default subclient because this would
disable its capability to serve as "catch-all" entity for client data. As a result, the likelihood that some
data will not get backed up or scanned for archiving would increase.
Back to Top
Subclients - Oracle - How To
Associate a Subclient to a Storage Policy
Change Account for Executing Pre/Post Commands (Data Protection) (Oracle on Windows)
Configure a Subclient for Pre/Post Processing of Data Protection Operations
Configure Backup Arguments
Configure Subclient Content
Configure the Lights Out Script to Shut Down the Database for Offline Backups
Configure the Subclient for Data Encryption
Create a New Subclient
Create Subclient for Backing Up Archived Redo Log Files
Create Subclient for Backing Up Offline Databases
Create Subclient for Backing Up Online Databases
Create Subclient for Backing Up Online Subsets
Create Subclient for Performing Selective Online Full Backups
Delete a User-Defined Subclient
Enable or Disable Operations
Enable Software Compression for a Subclient
Remove a Process from Pre/Post Processing of Data Protection Operations
Rename a Subclient
Set the Network Bandwidth and Network Agents for a Data Protection Operation
View Data Paths Associated with a Subclient
View Subclient Content
Select ArchiveLog Destinations for Backup or Deletion
Enable Backup of Flash Recovery Area
Enable Table Browse for the Subclient

Oracle recommends performing a mandatory Incremental Level 0
backup (i.e., Full backup) after adding new tablespaces and datafiles to
the database. If this is not done, the next Incremental backup will fail
because Recovery Manager will not be able to find the parent files for
the new tablespaces and datafiles.
Page 162 of 199
Associate a Subclient to a Storage Policy
To associate a subclient to a storage policy:
1. From the CommCell Browser, right-click the subclient whose associated storage policy you want to
change, then click Properties from the shortcut menu.
2. Click the Storage Device tab of the Subclient Properties dialog box.
3. From the Storage Policy list of the Data Storage Policy tab, select a data storage policy to
associate with this subclient. If necessary, click the Create Storage Policy button to create a new
storage policy to which the subclient can then be associated.
4. From the Changing a Storage Policy window select the next type of backup operation. Click OK.
5. If applicable for your agent, you can change the number of data streams from the Number of
Data/Database Backup Streams field.
6. If applicable for your agent, click the Log Storage Policy tab and select a storage policy to
associate with this transaction log subclient from the Transaction Log Storage Policy list. Also,
you can set the Number of Transaction Log Backup Streams from this tab.
7. Click OK to save your changes and close the Subclient Properties Storage Device tab.
Change Account for Executing Pre/Post Commands (Data Protection)
To change a user account for executing pre/post commands for Data Protection jobs:
1. From the CommCell Browser, expand the tree to view the appropriate level icon for the affected
agent.
From the agent, instance/partition, or backup set/archive set level, right-click the appropriate
icon, click All Tasks, and click New Subclient from the short-cut menu.
From the subclient level, right-click the subclient icon and click Properties from the short-cut
menu.
2. From the Subclient Properties dialog box, create and/or configure the subclient as appropriate. Then
click the Pre/Post Process tab.
3. From the Pre/Post Process tab, click Change.
4. From the User Account dialog box, select one of the account options. If you select Impersonate
User, type the appropriate user name and password.
Configure a Subclient for Pre/Post Processing of Data
Protection/Archive Operations
Before You Begin
We recommend not configuring a pre/post process for a subclient that is currently running a data
protection or archive operation.
Verify that there are no pre/post processes already assigned for the subclient.
Review the Overview and Agent-Specific Guidelines for your agent before configuring pre/post
processes for data protection/archive operations.
Pre-process commands for the iDataAgents will be executed only when the necessary resources (e.g.,
Page 163 of 199
media, library, drive, etc.) are available.
To configure a subclient for Pre/Post processing of data protection/archive operations:
1. From the CommCell Browser, right-click the subclient for which you want to configure a pre/post
process, and then click Properties from the shortcut menu.
2. Click the Pre/Post Process tab of the Properties dialog box.
3. For an agent other than the Oracle RAC iDataAgent, click inside the space that corresponds to one of
the following phases and type the full path of the process that you want executed during that phase.
Alternatively, click Browse to locate the process (applicable only for paths that do not contain any
spaces). For the Oracle RAC iDataAgent, click Browse for the corresponding process, click the name
of the control node client in the Select Client for Browse dialog box, and click OK. Then browse for
and click the process.
PreBackup
PreScan
PreArchive
PreCopy
PreSnap
PostBackup
PostScan
PostArchive
PostCopy
PostSnap
Click OK.
4. If you want to run a Post Process for all attempts to run that job phase, then select the
corresponding checkbox.
5. For subclients on Windows platforms, if Run As displays Not Selected, or if you want to change the
account that has permission to run these commands, click Change.
a. In the User Account dialog box, select Use Local System Account, or select Impersonate
User and enter a user name and password. Click OK.
b. If you selected Local System Account, click OK to the message advising you that commands
using this account have rights to access all data on the client computer.
6. Click OK to save your changes and close the Pre/Post Process tab of the Properties dialog box.
Configure Backup Arguments
Related Topics
Subclients - DB2
Subclients - DB2 DPF
Subclients - Informix
Subclients - Oracle
Before You Begin
For the DB2 and DB2 DPF iDataAgents, you will need to indicate whether the database should be
online or offline during backups.
Page 164 of 199
To configure backup arguments for a subclient:
1. From the CommCell Browser, right-click the subclient whose backup arguments you want to
configure, then click Properties from the shortcut menu.
2. Click the appropriate tab of the Subclient Properties dialog box for your iDataAgent:
DB2, DP2 DPF - (Backup Arguments)
Oracle, Oracle RAC - (Backup Arguments)
Informix (Content)
3. Select the desired backup argument settings that you want configured for this subclient.
4. Click OK to save your changes.
Configure Subclient Content
Before You Begin
Review Subclients.
Do not configure the content of a subclient while the parent node or any sibling subclient has a data
protection or archive operation currently running on it.
Exchange Mailbox iDataAgents and Exchange Mailbox/Public Folder Archiver Agents: If you change the
contents of the default backup set or archive set then the auto-discover feature will be disabled. If you
disable the auto-discovery feature, newly created mailboxes will not be backed up/archived unless
they are manually discovered and assigned to a subclient.
NAS NDMP iDataAgents: You must ensure there is no overlap in content between all subclients.
Overlap in subclient content will result in loss of data. An existing subclient's contents are not
automatically changed when another subclient is added with overlapping contents.
SharePoint Server iDataAgent: The Site Content Database, the Site Collection Database, the Site
Database, and the Site Index for the virtual server must all be assigned to the same subclient.
Lotus Notes Document iDataAgent: Review Assigning Restore View Names to Newly-discovered
Databases
QR Agent: Follow these guidelines when adding a volume to a QR Agent subclient:
The volume must correspond to a physical disk or RAID array.
A volume created by volume management software other than VxVM is not valid subclient content.
Subclients may have overlapping content; however, if two or more subclients overlap, they all must
use the same snapshot engine. If the QR policies associated with the subclients are configured to
use different snap engines, they must be reconfigured to use the same snap engine in this scenario.
Caution Against Re-configuring Default Subclient Content
We recommend that you do not re-configure the content of a default subclient because this would
disable its capability to serve as "catch-all" entity for client data. As a result, the likelihood that some
data will not get backed up or scanned for archiving would increase.
To configure subclient content:
1. From the CommCell Browser, right-click the subclient for which you want to configure content, click
All Tasks (if applicable) and then click Properties.
2. Follow the procedure below that is applicable for your agent:
For File System, Active Directory, File Archiver, Exchange Public/Web Folder iDataAgents, NDS,
Page 165 of 199
and SharePoint Server iDataAgents click the Subclient Properties (Content) tab and configure
content for the subclient as described below for your agent:
For File System, Active Directory, File Archiver, NDS, and SharePoint Server iDataAgents:
Type the full path of the data that you want to include as subclient content in the Enter New
Content field, then click Add. Optionally, click Browse to enter the content. When browsing
content while configuring SharePoint subclients, you can add content via multiple selections
with the CTRL or SHIFT keys. For Windows, when specifying a UNC Path, click As User, and
enter the user account information for the domain user with permissions for that path. For
NetWare/DNS, see the Notes section below for content path examples. For Unix File Systems,
you can enter the mount point of an NFS-mounted file system, see the Notes section below for
examples.
For Exchange Public/Web Folder iDataAgents: Click Browse, select folders to include as
content, then click Add.
For NAS NDMP iDataAgents, configure the Backup Content Path field(s) as described below,
then click Add:
Click the drop-down list arrow to display the root volumes on the file server. To change the
root volume, click one in the list. If you want to refine the content path further, use the space
to the right of (or below) the root volume list to enter additional path information. Note the
following:
For NetApp, the root volume is the mount path of each volume.
Example: for volume FS1 the root volume will be /vol/FS1.
For EMC Celerra, the root volume is the mount point created for a volume.
Example: for volume FS1 with mount point /FS1 the root volume will be /FS1.
For Hitachi, no root volumes are shown in the drop down list. Type the full path of the root
volume.
Example: for volume FS1 with mount point /mnt/FS1 the root volume will be /mnt/FS1.
For BlueArc, the root volume is a combination of a descriptor of the path and the volume
name.
Example: for volume FS1 with a mount point of / the root volume will be /__VOLUME__/FS1.
Optionally, for NetApp NAS NDMP, click Browse to enter the content.
For Exchange Mailbox and Exchange Mailbox/Public Folder Archiver Agents follow the procedure
to Discover and Assign New Mailboxes or Assign Mailboxes to Another Subclient.
For DataArchiver for Exchange Agents follow the procedure to Discover and Assign New Journal
Mailboxes or Assign Journal Mailboxes to Another Subclient.
For Lotus Notes Database and Document iDataAgents follow the procedure to Discover and Assign
New Databases or Assign Databases to a Subclient.
For DB2, DB2 DPF, Exchange Database, Novell GroupWise, SharePoint Server, SQL Server 2000
Database, Sybase, and MySQL iDataAgents, click the Subclient Properties (Content) tab and
configure content for the subclient as described below for your agent:
For the DB2 iDataAgent, specify whether you want to include the entire database or a subset
of this data as content for the subclient. For the DB2 DPF iDataAgent, specify whether you
want to include all the affected database partitions or a subset of this data as content for the
subclient.
For Exchange and GroupWise iDataAgents: Click Configure. From the Add/Modify Subclients
dialog box click the subclient entry for the database element/Storage Group that you want to
add to the new subclient and select the name of the destination subclient from the list that
appears. Alternatively, you can select and assign a range of databases/storage groups using
the Change all selected databases/storage groups to list. Note that you must have at
least one database element/Storage Group assigned to this subclient in order to save the
configuration.
A database/Storage Group that is not configured for a subclient does not appear in the list.
This can be the case if the subclient containing the database/Storage Group was deleted. If
this happens, click Discover to display all databases/Storage Groups.
Page 166 of 199
For the SharePoint Server iDataAgent, follow the procedure to Discover and Assign New Data
Types.
For the SQL Server 2000 Database iDataAgent, follow the procedure to Configure SQL Server
2000/2005 Databases or Configure SQL Server 2000/2005 Files and File Groups.
For the Sybase iDataAgent, follow the procedure to Configure Sybase Databases.
For the MySQL iDataAgent, follow the procedure to Configure MySQL Databases.
For the Informix iDataAgent, click the Subclient Properties (Content) tab and define the contents
of the subclient. Specifically, establish the backup mode for the data to be backed up, set the
backup level, and decide whether to back up the emergency boot file and/or the ONCONFIG file.
For the Oracle, SAP for Oracle, or Oracle RAC iDataAgent, click the Subclient Properties (Content)
tab and define the contents of the subclient. To configure this subclient for specialized types of
backups, follow the appropriate procedure below:
For SAN iDataAgents, click the Subclient Properties (Content) tab and configure content for the
subclient as described below for your agent:
Image Level on Unix iDataAgent: Click Add. From the Add Content Path dialog box, select the
volume(s) that you want to back up (use CTRL + click to select multiple volumes). Click OK.
The selected volumes are added to the Contents of subclient list. These volumes are
automatically configured to be CXBF devices. Alternatively, use Volume Explorer per specific
scenarios to configure CXBF devices.
To configure an unmounted block device or raw device as content, first use Volume Explorer to
configure the device as a CXBF device. Then select the configured CXBF device as subclient
content. You can ignore the warning that is displayed.
For more information, see When to Use Volume Explorer. For a step-by-step procedure, see
Configure a CXBF Device in Volume Explorer.
Image Level and Image Level ProxyHost on Windows iDataAgents: Click Add. Then in the Add
Content dialog box, type the full path of the volume or mount point that you want to include
as subclient content, then click Add. Optionally, click Browse to select the content. Click OK.
The volume or mount point is added to the Contents of subclient list. Add additional content
by repeating this step.
ProxyHost iDataAgent: Select a backup host from the Backup Host list. This is the computer
to which the BCV is connected. Click Add. In the Content field of the Add/Edit Content for
Subclient dialog box, type the primary host path of the content that you want to back up, or
click Browse to find and select this data. In the Backup Host BCV Path field of the Add/Edit
Content for Subclient dialog box, type the path through which the backup host accesses this
data on the BCV, or click Browse to find and select this path. Click OK. The primary host data
path and corresponding backup host BCV path are added as a single entry in the Contents of
subclient list. To add additional entries, repeat these steps. Refer to Notes below for more
information.
For Quick Recovery Agents, click the Subclient Properties (Content) tab and configure the
following options:
Click Add Volume. From the Adding Volume dialog box, select volume(s) that you want to
add to the subclient content (use CTRL + click to select multiple volumes). You can add/edit
additional advanced options for the selected volume by select Advanced on the Adding
Volume dialog box. Click OK.
Click Add App to select an application and associated volumes. Click OK.
Any instances you intend to protect and recover with the QR Agent must be configured in the
QR Agent properties Authentication tab. They will not appear in the Add App dialog box if they
Page 167 of 199
are not configured. Only volumes containing datafiles and archive log files will be detected by
Add App. Volumes containing control files and redo log files will not be detected.
For a clustered Exchange Server, if you are not using VSS to perform an online quiesce,
sufficient permissions are required in order to be able to perform an offline quiesce; in such
cases, ensure that the User Name specified has Exchange Administrator rights.
See also Configure Subclients for Overlapping Content.
3. Click OK to save your content configuration.
NOTES
Content examples for NetWare are OU=prospects.O=engineering.[Root], (for NDS content), and
SYS:\public (for File System content).
Content examples for adding an NFS-mounted file system to subclient content of a Unix File System
iDataAgent:
/mountpointA to include the entire file system at mountpointA
/mountpointA/projects for only the projects directory within the file system at mountpointA.
Informix subclients include one or more dbspaces. As databases are added to the dbspaces, the
subclients are updated automatically.
SQL Server 2000 Database iDataAgents: The logical and physical names are available to assist in
identifying the correct content. Files and file groups that are configured as content of other subclients
are unavailable for selection.
Exchange Mailbox iDataAgents and Exchange Mailbox/Public Folder Archiver Agents: Initially, all
unconfigured mailboxes are assigned to the default subclient. You can create a new subclient and
reassign mailboxes to this new subclient (within the same backup set/archive set). Once assigned, the
mailboxes become part of the content of the new subclient.
SharePoint Server iDataAgent: Initially, all unconfigured data types are assigned to the default
subclient. You can create a new subclient and reassign data types to this new subclient. Once
assigned, they become part of the content of the new subclient.
ProxyHost iDataAgent: The primary host data path is backed up by the subclient and is the path
through which the backup host accesses this data on the BCV. A primary host path and its
corresponding backup host path are listed in the following format:
<primary_host_path> --> <backup_host_path>
For example, assume that you want to back up the D:\data directory from your primary host and D:\
is mirrored by a BCV, which is mapped to the backup host as F:\. Consequently, the path to this data
on the backup host is F:\data. When you add this directory to a subclient, it is listed in the Contents
of subclient pane as D:\data --> F:\data.
Configure the Lights Out Script to Shut Down the Database for Offline
Backups
Related Topics
The primary host path in the Content field is used for browse and restore
purposes. However, it is the data in the Backup Host BCV Path which is
actually backed up. If these two paths do not accurately correspond, the
path that appears when data is browsed for restore does not accurately
reflect the data that will be restored. In the example given above, assume
that D:\data is entered in the Content field, while F:\data1 is
accidentally entered in the Backup Host BCV Path. If you browse and
select D:\data to be restored, it is actually D:\data1 that is restored.
(Remember, F:\Data1 is the path on the backup host that corresponds to
D:\data1 on the primary host.)
Page 168 of 199
Backup - Oracle iDataAgent
Backup - Oracle RAC
Before You Begin
Oracle iDataAgent: Review Configuring the Lights Out Script to Shut Down the Database for Offline
Backups for an overview of this feature.
Oracle RAC: Review Configuring the Lights Out Script to Shut Down the Database for Offline Backups
To configure the lights out script to shut down the database for offline backups on a subclient:
1. From the CommCell Browser, right-click the subclient whose lights out script you want to configure,
then click Properties from the shortcut menu.
2. Click the Subclient Properties Subclient Properties (Backup Arguments) tab, then configure the
following options as appropriate:
Select the Lights Out Script option to enable automatic execution of this script before backing
up the database.
For Oracle on Unix, select the Warning option to enable a warning message that will be
displayed on the physical node for users logged into the database, that the database will be shut
down.
For Oracle on Unix, in the Delay Time (min) field, enter the number of minutes that you want
the script to wait after sending out the warning message to the physical node before the system
attempts to shut down the database.
If you are configuring Oracle RAC, then skip to step 3, as the remaining options in this step apply
only to the Oracle iDataAgent.
In the Sleep Time (sec) field, enter the number of seconds that you want the script to wait
lights out script in the event that the first attempt to shut down the database was unsuccessful
after the Delay Time has expired.
In the Tries Number field below the Sleep Time (sec) field, enter the number of times that you
want the script to retry attempts to shut down the database when the Sleep Time (sec) field is
activated.
In the Sleep Time (min) field, enter the number of minutes that you want the script to wait
lights out script in the event that the Tries Number limit has been reached for the Sleep Time
(sec) field.
In the Tries Number field below the Sleep Time (min) field, enter the number of times that you
want the script to retry attempts to shut down the database when the Sleep Time (min) field is
activated.
Select the Use SQL Connect option to connect to the database using the SQL command
connect <connect string> as sysdba. The Connect String entry is configured in the
Instance Properties (Details) tab. Note that if this option is not selected, the CommServer sets
the service name using set oracle_sid=<Instance name> and connects to the database using
the connect /as sysdba command. The Instance name is displayed in the Instance Properties
(General) tab.
On AIX 64 bit platform, you should always use the SQL_CONNECT option to
shutdown and start the database in mount mode. This is required because
of the limitation in SQL Plus to connect using / when the EXTSHM variable is
set.
Page 169 of 199
3. Select any other options as appropriate, then click OK to save the changes.
Configure the Subclient for Data Encryption
Encryption settings made at the subclient level are for data protection and recovery operations run from
the CommCell Console and are not related in any way to settings made at the instance level which is for
third-party Command Line operations only.
See Data Encryption - Support for a list of supported products.
Before You Begin
Encryption must be enabled at the client level prior to configuring any subclients residing on that
client. See Configure the Client for Data Encryption.
If you are attempting to configure for third-party Command Line operations, do not use this
procedure. See Configure Third-party Command Line Operations for Encryption.
To configure the subclient for data encryption:
1. From the CommCell Console, right-click the subclient and click Properties.
2. From the Subclient Properties (Encryption) tab, select an option based on the criteria described in
the Encryption tab help.
3. Click OK to save your settings and close subclient properties.
Create a New Subclient
Before You Begin
Review Subclients.
Do not create a subclient while the parent node or any sibling subclient has a data protection or
archive operation currently running on it.
In cases where a new subclient is created with the same name as a deleted subclient, the system will
append a Unix time stamp to the deleted subclient's name in data protection job history reports and
views to distinguish the two subclients. For example, subclientname_1104257351.
Informix iDataAgents: If you will be using the Informix ONBAR utility to create backup and restore
scripts, you need not create subclients. Otherwise, if you will be using the CommCell Console to back
up and restore Informix database objects (subsets/dbspaces), then you will need to create a subclient.
ProxyHost iDataAgents: If you are using a BCV, you must prepare a batch file or a shell script file on
the backup host containing commands to synchronize and split the BCV. The Resource Pack includes
information on configurations for these batch files or shell scripts, as well as examples that apply to
specific applications and hardware (e.g., Exchange databases in an EMC Symmetrix environment). See
Tools and Utilities for more information on the Resource Pack.
The ProxyHost iDataAgent also requires that you set permissions for the batch/shell script file on the
backup host.
SQL Server 2000/2005 Database iDataAgents: When running on Windows Server 2003 and VSS is
enabled, the New Subclient command is not available.
To create a new subclient:
1. From the CommCell Browser, right-click the node (agent/backup set/archive set/instance) for which
you want to create a new subclient, click All Tasks (if applicable), and then simply click New
Subclient for most agents.
Page 170 of 199
For the SQL Server iDataAgent, expand New Subclient and click either Database to include
individual databases or File/File Group to include database elements.
For the File Archiver Agent for Windows with Data Classification, right-click the DataClassSet,
expand All Tasks, and then click Create DataClassSet (subclient).
2. Click the General tab or General (Quick Recovery Agent) tab of the Subclient Properties dialog box
and type the name (up to 32 characters) of the subclient that you want to create.
For supported agents identified in Support Information - Snapshot Engines, you can select a
QSnap option to snap data and then perform a data protection operation on the data.
For QR Agents, you must also select a QR Policy from the QR Policy list.
For the Windows iDataAgents that support VSS, you can optionally Enable VSS on a Subclient.
3. Select other options from the General tab as appropriate for the agent.
4. Click the Content or Databases tab of the Subclient Properties dialog box and Configure Subclient
Content as appropriate for your agent.
5. For all agents (except QR), click the Storage Device (Data Storage Policy) tab of the Subclient
Properties dialog box, then select a data storage policy to associate with this subclient from the
storage policy list.
For the DB2 and DB2 DPF iDataAgents, you can also change the number of data backup streams.
For the DB2 DPF iDataAgent, the default stream threshold should be equal to the total number of
database partitions for the subclient.
For SQL Server iDataAgents, you can also click the Storage Device (Log Storage Policy) tab of the
Subclient Properties dialog box, then select a log storage policy to associate with this subclient
from the storage policy list and select the number of backup streams for transaction log backup
jobs.
For 1-Touch for Unix, it is strongly recommended that the storage policy that you select for the
subclient configured for 1-Touch use a MediaAgent on a different computer. If you do this, and if
the system crashes, the media will not have to be exported to another MediaAgent in order to
recover the system.
6. For Oracle and DB2 iDataAgents, click the Backup Arguments (Oracle) or Backup Arguments (DB2,
DB2 DPF) tab of the Subclient Properties dialog box and Configure Backup Arguments as appropriate
for your agent. Note that the backup arguments for Informix are located on the Content tab.
7. For Migration Archiver Agents, click the Archiving Rules or Rules tab of the Subclient Properties
dialog box and configure archiving rules as appropriate for your agent. In order to perform rules-
based migration archiving operations, the Disable All Rules checkbox must be cleared.
If the File Archiver for Windows supports Data Classification, several filter-like configuration fields
are defined as archiving rules and are available from the Subclient Properties (Rules) tab. If you
want to define content and archiving rules based on file attributes other than volumes, size, and
modified time (i.e., if you want to customize your rules), click the Advanced tab and configure as
appropriate. Also, stub management options can be configured from the Stub Rule tab. See
Configure Archiving Rules - File Archiver Agents for step-by-step instructions.
8. For ProxyHost and Image Level ProxyHost iDataAgents, click the Pre/Post Process tab of the
Subclient Properties dialog box. In the PreScan field, type the path to the batch file/shell script file
that contains those commands that are to run before each backup of the subclient, or click Browse
to locate and select this file. For ProxyHost and Image Level ProxyHost, the file must reside on the
backup host or primary host.
9. Optionally (if supported for your agent) you can:
Add a Data Protection or Discovery Filter for a Subclient on the Filters tab.
Configure a Subclient for Pre/Post Processing of Data Protection/Archive Operations on the
Pre/Post Process tab.
Enable Software Compression for a Subclient on the Software Compression tab of the Storage
Device tab.
Page 171 of 199
Configure the Subclient for Data Encryption on the Encryption tab.
Enable or Disable Operations for this subclient on the Activity Control tab.
Configure Mailbox Stores for Auto-Discovery on the Auto-discovery tab.
Configure the Subclient for 1-Touch on the 1-Touch Recovery tab.
View or change the user group security associations for this subclient from the Security tab.
Determine location from where archive logs will be backed up or deleted from the Log
Destinations tab.
Enable backups using a snap engine from the Snap Backups tab.
10. Click OK to save the subclient configuration. For QR Agents, this procedure is now complete. For all
other agents, continue on to the next step.
11. The Backup Schedule dialog box advises you to schedule data protection operations for your new
subclient. It is recommended you elect to set a schedule now. You can also associate this subclient
with an All Agent Types schedule policy (which is automatically created by the system, or can be a
user defined Data Protection schedule policy). If you have already associated a schedule policy at a
previous level (Backup Set/Instance, Agent, Client, or Client Computer Group) the schedules defined
in the Schedule Policy will be automatically applied to the new subclient. See Schedule Policy for
more information.
If you want to associate this subclient with an All Agent Types schedule policy, click Associate
with Generic Schedule Policy, and then select that schedule policy from the drop-down list
box. Click OK.
If you want to associate this subclient with a specific schedule policy, click Associate to
schedule policy, and then select the schedule policy from the drop-down list box. Click OK.
If you have selected to define a schedule for this subclient:
Click Schedule.
From the Backup/Archive Options dialog box, select the type of data protection operation that
you want to schedule.
If you want to set Advanced Backup/Archive Options, click Advanced.
After selecting the data protection type and any advanced options, click OK. The Schedule
Details dialog box appears.
From the Schedule Details tab, select the scheduling options that you want to apply, then click
OK.
If you don't want to create a data protection schedule at this time, click Do Not Schedule, and
then click OK.
This task is now complete.
Related Topics:
Subclients - Oracle
Subclients - SAP for Oracle
The following procedure demonstrates how to create a subclient for backing up archived redo log files
with the following features:
Includes only archived redo log files.
Deletes the archived redo log files once they are backed up.
Re-synchronizes the contents of the Recovery Catalog with the contents of the Control File.
Before You Begin
Page 172 of 199
Review Things to Consider when Creating and Configuring Oracle Subclients, Things to Consider when
Creating and Configuring Oracle RAC Subclients, or Things to Consider when Creating and Configuring
SAP for Oracle Subclients.
Oracle archives online redo log files once they become full. These logs can be used to recover
database transactions that have been lost due to an operating system or disk failure, by applying
them to an online backup in order to recover a database. Because of their importance in recovering
data, it is recommended that you create separate subclients for backing up archived redo log files.
Archived redo log files are always backed up as a full backup even if incremental is selected.
To create a subclient for backing up archived redo log files:
1. From the CommCell Browser, right-click the instance for which you want to create a new subclient,
click All Tasks then click New Subclient.
2. Click the General tab of the Subclient Properties dialog box and type the name (up to 32 characters)
of the subclient that you want to create.
3. For Oracle or SAP for Oracle, click the Content tab. For Oracle RAC, click the Logs Backup tab and
select the following option:
Backup Archive Log - Specifies that archived redo log files will be backed up. These logs can be
applied to the database in order to recover it to a point-in-time.
Archive Delete - Specifies that archived redo log files are deleted once they are backed up. Note
that any archived redo log files that do not match the format indicated by the
LOG_ARCHIVE_FORMAT environment variable are not deleted.
Optionally, for Oracle RAC, use the directional arrows to reset the client/instance backup order.
4. Click the Backup Arguments tab and select the following options:
Archive Files per BFS - Establishes the number of archive files to be bundled in each backup set
(Default is 32).
Resync Catalog - Specifies that the contents of the Recovery Catalog will be synchronized with
the contents of the Control File (This option is automatically enabled by default when the Backup
Archive Log option is selected on the Content tab in Step 3 above).
5. Click the Storage Device tab of the Subclient Properties dialog box, then select a storage policy to
associate with this subclient from the storage policy list.
6. Optionally, you can:
Establish Pre/Post processes using the Pre/Post Process tab.
Enable a software compression scheme for the subclient from the Software Compression tab on
the Storage Device tab.
Enable De-Duplication for the subclient from the De-Duplication tab on the Storage Device tab.
Enable data encryption for backups on the Encryption tab.
Enable/disable backups for this subclient on the Activity Control tab.
Select archive log destinations for backup and deletion on the Log Destinations tab.
7. Click OK to save the subclient configuration.
8. You will be prompted to create a backup schedule for the newly created item. Select Schedule if
you want to create a backup schedule for this subclient, otherwise select Do Not Schedule if you
don't want to create a backup schedule for this subclient, then click OK.
9. If you selected Do Not Schedule in the previous step, then this procedure is now complete. If you
selected Schedule, the Backup Options dialog box appears.
10. From the Backup Options dialog box, select the type of backup that you want to schedule. If you
want to access Advanced Backup Options, click Advanced.
11. Click Backup Archive Logs tab, if available, and select the criteria based on which the archive logs
Page 173 of 199
will be backed up. For more information, see Backup Archive Log Options.
12. Click OK. The Schedule Details dialog box appears.
13. From the Schedule Details (Schedule Details) tab, select the scheduling options that you want to
apply, and then click OK.
Related Topics:
Subclients - Oracle
The following procedure demonstrates how to create a subclient for backing up an offline database with
Includes Control Files (where applicable).
Incremental backup level set to 1, 2, 3 or 4. By default the system performs an incremental level 1
backup. The first time you back up the subclient the system performs a full backup for the subclient
before performing a level 1, 2, 3, or 4 incremental backup.
Database is taken OFFLINE and available in the MOUNT mode for the backup.
Before You Begin
SAP for Oracle Subclients..
Make sure that the database used for creating the subclient is up and running. This ensures that the
system accesses the most recent configuration of the database.
To create a subclient for backing up offline databases:
click All Tasks and then click New Subclient.
3. Click the Content tab and select the following options where available:
Data - Specifies that data files will be backed up.
Offline Database - Establishes the backup as an offline database backup.
Backup Control File - Specifies that the backup control files will be included in the subclient
backup.
4. Click the Backup Arguments tab where available and select the following options:
Lights Out Script - Specifies that the Lights Out Script will be automatically executed before
backing up offline databases. This script shuts down the database and by default uses the SPFile
to start up the database in MOUNT mode. Once the backup is completed, the script opens the
database.
STARTUP PFILE location - Specifies the location of the PFile to be used for starting up the
database. You need to select this option only if you want to start up the database using the PFile.
By default, the system uses the SPFile available in $ORACLE_HOME/dba directory (for Unix) or
$ORACLE_HOME/database directory (for Windows) to start up the database.
Do not select the Offline Arguments option if you would like to manually start the database in
MOUNT mode before you back up the subclient.
Page 174 of 199
For Oracle RAC, enable archive log backups and use the directional arrows to reset the
client/instance backup order on the Logs Backup tab.
want to access Advanced Backup Options, click Advanced. After selecting the backup type and
any advanced options, click OK. The Schedule Details dialog box appears.
Related Topics:
Subclients - Oracle
The following procedure demonstrates how to create a subclient for backing up an online database with
Includes control files (where applicable).
Data Files bundled in each backup set is set to 32 (default is 64).
Excludes Archived Redo Log files. It is recommended that you create separate subclients for archive
redo logs.
Before You Begin
Page 175 of 199
To create a subclient for backing up online databases:
3. Click the Content tab and select the following options where available:
Online Database - Establishes the backup as an online database backup.
Backup Control File - Specifies that the backup control files will be included in the subclient
backup.
4. Click the Backup Arguments tab where available and select the following option:
Data Files per BFS - Establishes the number of datafiles to be bundled in each backup set - set
this to 32.
Related Topics:
Subclients - Oracle
The following procedure demonstrates how to create a subclient for backing up an online subsets that
include tablespaces/datafiles with the following features:
Excludes Control Files.
Page 176 of 199
Excludes Archived Redo Log Files. It is recommended that you create separate subclients for archive
redo logs.
Before You Begin
To create a subclient for backing up online subsets:
3. Click the Content tab and select the following options:
Online Subset - Establishes the backup of a subset of database objects. The database tree
displays the subsets that are available in the database. Click the objects in the tree to include the
subset objects for the subclient.
4. Click the Backup Arguments tab where available and select the desired options.
Page 177 of 199
Related Topics:
Subclients - Oracle
Before You Begin
To create a subclient for performing Selective online full backups:
3. Click the Content tab to define the contents of the subclient. Click the Selective Online Full
checkbox to enable selective online full backups for this subclient.
4. Click the Backup Arguments tab where available to define backup arguments for the subclient.
For Oracle RAC, enable archive log backups and use the directional arrows to reset the
client/instance backup order on the Logs Backup tab.
Delete a User-Defined Subclient
Related Topics:
Command Line Interface - qdelete subclient
Page 178 of 199
Subclients
To delete a user-defined subclient:
1. From the CommCell Browser, right-click the user-defined subclient that you want to delete, and then
click Delete from the shortcut menu.
2. A confirmation message is displayed, asking if you want to delete the subclient.
Click No to cancel the deletion and retain the subclient, or click Yes to continue the deletion. If you
click Yes:
the subclient, and any data that may have been protected/archived by the subclient are logically
deleted, and you can no longer access the corresponding data for recovery/retrieve purposes.
However, the data remains valid for the length of time specified by the associated retention
period. Some agents allow you to browse data from a deleted subclient provided that the Browse
Data Before date and time precedes the time that the user-defined subclient was deleted.
for agents that support a default subclient, once the user-defined subclient is deleted its contents
are automatically reallocated to the default subclient the next time a data
protection/archive/discovery operation is run on the default subclient to ensure data protection
coverage.
the system deletes the selected subclient node and removes it from the CommCell Browser.
the system deletes any data protection/archive and recovery/retrieve job schedules that are
associated with the subclient.
Enable or Disable Operations
To enable or disable activity control at the CommCell, client computer group, client, agent, or subclient
levels:
1. From the CommCell Browser, right-click the CommServe, client computer group, client computer,
agent, or subclient, and then click Properties from the short-cut menu.
2. From the Activity Control tab of the associated Properties dialog box, select or clear option(s), as
desired.
3. Click OK.
Enable or Disable Software Compression for a Subclient
Before you Begin
Level Capability
CommCell Administrative Management with CommCell level association
Client Computer
Group
Administrative Management with Client Computer Group level association
Client Agent Management with Client level association
Agent Agent Management with Agent level association
Subclient Agent Management with Subclient level association
Disabled data management and/or data recovery operations are displayed
with client and/or agent icon changes in the CommCell Browser. For a
comprehensive list of all icons in the CommCell Console, see CommCell
Console Icons.
Page 179 of 199
Do not enable/disable software compression for a subclient that is being backed up/archived.
To enable software compression for a subclient:
1. From the CommCell Browser, right-click the subclient for which you wish to enable software
compression and then click Properties.
2. Click the Storage Device tab and from the Data Storage Policy tab, select the storage policy from
the Storage Policy list.
If applicable for the selected agent, click the Log Storage Policy tab and select a storage policy from
the Transaction Log Storage Policy list.
3. Then click the Storage Device (Data Transfer Option) tab and choose the appropriate compression
option for this subclient.
4. Click OK to save your changes.
Remove a Process from Pre/Post Processing of Data Protection/Archive
Operations
Before You Begin
We recommend not removing a pre/post process for a subclient that is currently running a data
protection or archive operation.
Review the Overview and Agent-Specific Guidelines for your agent before removing pre/post processes
for data protection/archive operations.
To remove a process from Pre/Post processing of data protection/archive operations:
1. From the CommCell Browser, right-click the subclient for which you want to remove a pre/post
process, and then click Properties from the shortcut menu.
2. Click the Pre/Post Process tab of the Subclient Properties dialog box.
3. Click the text inside the space that corresponds to one of the following phases for which you want a
pre/post process removed, then press the Delete key:
PreScan
PreArchive
PreCopy
PreSnap
PostBackup
PostScan
PostArchive
PostCopy
PostSnap
4. Repeat Step 3 for any additional processes that you want to remove.
5. Click OK.
Rename a Subclient
Page 180 of 199
Before You Begin
You can rename a subclient at any time. However, we recommend that you don't rename a subclient
while a data protection or archive operation is running on that subclient.
In cases where a subclient is renamed using the same name as a deleted subclient, the system will
append a Unix time stamp to the deleted subclient's name in data protection job history reports and
views to distinguish the two subclients. For example, subclientname_1104257351.
To rename a subclient:
1. From the CommCell Browser, right-click the subclient that you want to rename, and then click
Properties from the shortcut menu.
2. From the Subclient Properties (General) tab, or the QR Agent Subclient Properties (General) tab,
type the new name in the Subclient Name field, and then click OK.
The CommCell Browser updates the subclient with its new name. The new name will also be reflected in
any associated schedules and reports.
Set the Network Bandwidth and Network Agents for a Data Protection
Operation
Before you Begin
Do not modify the network bandwidth and network agents for a subclient or instance that is being
backed up.
To Set the Network Bandwidth and Network Agents for a Data Protection Operation:
1. From the CommCell Browser, right-click a subclient and then click Properties.
For the DB2, DB2 DPF, Informix, Oracle, Oracle RAC, SAP, or Sybase iDataAgent, right-click an
instance and then click Properties.
2. Click the Storage Device Data Transfer Option tab.
For the QR Agent:
To control network bandwidth settings, use the Throttle Network Bandwidth section in the
General tab of the Subclient Properties dialog box.
To control the number of network agents, you must create a nQRNetworkAgents registry key.
3. Enter a number of Network Agents that must be used to perform data protection operations on the
subclient/instance.
4. Click the Throttle Network Bandwidth (MB/HR) option and then enter the throughput as
needed. Note that throttling is done on a per Network Agent basis.
5. Click OK to save the changes.
View Data Paths Associated with a Subclient
To view data paths:
1. From the CommCell Browser, right-click the subclient whose data paths you want to view, then click
Page 181 of 199
Properties from the shortcut menu.
2. Click the Storage Device tab of the Subclient Properties dialog box.
3. From the Data [or Logs] Storage Policy tab, click Show Data Paths to view the data paths used
by the subclient to access the storage media for data protection operations. Click Close to exit the
Data Paths dialog box.
4. Click OK to exit the Subclient Properties Storage Device tab.
View Subclient Content
To view content of a subclient:
1. From the CommCell Browser, right-click the subclient whose content you want to view, then click
Properties.
2. From the Subclient Properties dialog box, click the Content tab (or Databases tab for Lotus Notes)
to view the contents of the subclient.
3. Click OK to close the dialog box.
Select Archive Log Destinations for Backup or Deletion
Related Topics:
Subclients - Oracle
Before You Begin
To select Archive Log destinations for backup or deletion:
1. From the CommCell Browser, right-click the appropriate subclient, click Properties from the
shortcut menu, and then click the Log Destinations tab.
2. Do either or both of the following:
Click Select ArchiveLog Destinations for Backup, click Add, click the desired ArchiveLog
backup location, and then click OK. Repeat this step for each location that you want to include.
Click Select ArchiveLog Destinations for Delete, click Add, click the desired ArchiveLog
deletion location, and then click OK. Repeat this step for each location that you want to include.
3. Click OK.
Enable Backup of Flash Recovery Area
Related Topics:
Subclients - Oracle
Before You Begin
Page 182 of 199
Make sure that a Flash Recovery Area is set for the Oracle database and all related parameters, such
as size, location, and retention policy are configured.
Note that the Flash Recovery Area is an Oracle 10g feature. Therefore, backup of the Flash Recovery
Area is possible only with agents that use Oracle 10g.
Note that you can backup the Flash Recovery Area only when the database is online.
To enable backup of Flash Recovery Area:
1. From the CommCell Browser, right-click the subclient that you want to back up, and choose
Properties.
2. Click SubClient Properties of data (Content) tab.
3. Select Protect backup recovery area checkbox.
4. Click OK. The Flash Recovery Area backup is now enabled.
Enable Table Browse for the Subclient
Related Topics:
Subclients - Oracle
Before You Begin
Review Things to Consider when Creating and Configuring Oracle Subclients or Things to Consider
when Creating and Configuring Oracle RAC Subclients.
Note that you can enable the table browse for only one subclient.
To enable table browse for the subclient:
1. From the CommCell Browser, right-click the subclient for which you want to enable table browse,
and then click Properties.
2. From the Subclient Properties (Backup Arguments) tab, select Enable Table Browse.
3. Click OK.
Back To Top
Page 183 of 199
Backup Job History
Overview
Items That Were Backed Up
Items That Failed
Pruning Backup History Information
Supported Features
Content Indexing History Information
Overview
You can view the backup and restore history of iDataAgents, BackupSets/Instances, and subclients.
The Backup Job History Filter dialog box allows you view detailed, historical information about backup
jobs. Once you have chosen your filter options, they are displayed in the Backup Job History window.
For information on Job Details displayed in the Job History, see Viewing Job Information.
From this window, you can right-click a backup job to:
Browse the data backed up by the backup set or instance from the Backup Job History window. This
is provided as right-click option for each job. (This menu option, when selected, initiates the Browse
Options dialog box preset with the values needed to browse the data.)
Browse the snapshots created during SnapProtect
View items that failed during the backup job
View details of the backup job
View files that were not indexed during a backup job that performed content indexing
View associated media
View events of the backup job
View a list of items that were backed up
View a list of items that were moved to media for a SnapProtect job
View the log files of the backup job.
View the RMAN log of an Oracle backup job.
Items That Were Backed Up
The View backup file list option allows you to view a list of the files that were backed up during a
backup job, along with the data sizes of each backed up file. The View backed up messages option
allows you to view a list of messages that were backed up by using, along with the alias name, display
name, email address, sender name, and recipient of each message.
From these windows you can conduct searches based on a particular string, allowing to find particular
files quickly and easily.
It is not recommended that this option is used to view a very large list of
items that were backed up (such as lists that total over 100,000 items). It
is suggested that the Browse option is used to find a list of backed up
items in such cases.
Page 184 of 199
See View the Items That Were Protected During a Data Protection Operation for step-by-step
instructions.
Items That Failed
The items that failed for a data protection operation include individual files that may fail the job even
though a particular job completed successfully. You can determine the degree of success for these jobs
using this window.
Filters can be used in conjunction with the "Items That Failed" list on the data protection Job History
Report to eliminate backup or archive failures by excluding items which consistently fail that are not
integral to the operation of the system or applications. Some items fail because they are locked by the
operating system or application and cannot be opened at the time of the data protection operation. This
often occurs with certain system-related files and database application files.
Also, keep in mind that you will need to run a full backup after adding failed files to the filter in order to
remove them.
See View the Items That Failed For a Data Protection Operation for step-by-step instructions.
Pruning Backup History Information
You can prune backup history information based on the number of days established in the Days to keep
the backup job histories option from the Media Management Configuration (Service
Configuration) dialog box available in the Control Panel.
Supported Features
The NAS NDMP iDataAgents do not support the ability to view items that failed.
The Image Level and Image Level ProxyHost iDataAgents do not support the ability to Browse the data
of a selected backup job in Backup Job History.
Content Indexing History Information
Content Indexing history can also be viewed of iDataAgents, BackupSets/Instances, and subclients. The
following information is displayed:
Items that were Successfully Content Indexed
A listing of files and folders that failed is not available for the Quick
Recovery Agent, or the Image Level and Image Level ProxyHost
iDataAgents. These agents do not perform a file level backup/copy.
Certain application related files can never be backed up by the File System
iDataAgent due to the nature of the data. For example, Microsoft SQL
Server database files cannot be backed up by the File System iDataAgent.
In this and other similar circumstances, consider entering files such as
these as exclusions in the corresponding subclient filter.
If you have installed the SQL Server iDataAgent, do not use the stored
procedure sp_delete_backuphistory,
sp_delete_database_backuphistory and
sp_delete_backup_and_restore_history provided by Microsoft clean
up backup history. By default backup history is automatically pruned from
the CommServe database and the Microsoft SQL Server, as necessary.
Page 185 of 199
You can view the list of items that were successfully content indexed during a Content Indexing operation
for a particular job. for step-by-step instructions, see View the Items that Were Successfully Content
Indexed.
Content Indexing Failures
Content Indexing failures allows you to look at the messages, files and documents that could not be
indexed during a content indexing operation. Content Indexing looks at each file (of the supported data
types) and indexes its contents allowing advanced searches of backed up/archived/migrated data.
Files that were not indexed, (perhaps because the files content could not be read) are added to the
Content Indexing Failures list, and are viewable from the View Content Index (Failed Items) option in the
Job History window. For step-by-step instruction, see View the Items that Failed to Content Index.
Back to Top
Backup Job History - How To
View Backup Job History
View the Items That Were Protected During a Data Protection Operation
View the Items That Failed For a Data Protection Operation
View Job History Details
View the Media or Mount Paths of a Job History
View the Events of a Job History
View the Items that were Moved to Media during SnapProtect
View the Log Files of a Job History
View the Items that Were Not Indexed During Content Indexing
View the Items that Were Successfully Content Indexed
View Backup Job History
To view backup history:
1. From the CommCell Browser, right-click the entity (client computer, iDataAgent, backup set or
subclient) whose backup history you want to view, click View, and then click View Backup
History.
2. From the Backup History filter window select the filter options, if any, that you want to apply, and
then click OK. The system displays the Backup Job History window.
3. Click OK.
View the Items That Were Protected During a Data Protection Operation
Required Capability: none required
This option is available for File System-like agents.
Page 186 of 199
To view the list of items that were protected during a data protection operation.
1. From the CommCell Browser, right-click the entity whose history of data protection operations you
want to view, click View, and then click the necessary options to view a job history.
2. From the Job History Filter dialog box, select the filter options, if any, that you want to apply, and
then click OK.
3. From the Job History window, right-click the operation whose list of protected items you want to
view, and then select View backup file list/View Backed Up Messages. The Backup file List
window displays a list of the backed up files/messages that were included in the backup job. You can
use the Search option to find items in the window.
4. Click File -> Exit.
5. Click Close from the Job History window.
View the Items That Failed For a Data Protection Operation
To view the list of items that failed for a data protection operation:
want to view, click View, and then click to view a job history.
then click OK.
3. From the Job History window, right-click the operation whose list of failed items you want to view,
and then select View Failed Items. The Unsuccessful Backup Files window (for DataArchiver
Agents, Items On Which Archive Failed) displays those items that failed. If no items failed, a
message to that effect is displayed.
4. Click Close.
View Job History Details
To view the details of a job history:
1. From the CommCell Browser, right-click the entity (e.g., subclient, client computer, etc.) whose job
history you want to view, click View, and then click job history.
2. From the Job History Filter dialog box, select the filter options that you want to apply and click OK.
3. From the Data Management Job History window, right-click the job whose job details you want to
view, and then click View Job Details.
4. The Job Details dialog box appears, displaying detailed job history in General, Details, Phase Details
and Attempts tabs for the selected job.
5. Click OK.
A listing of files and folders that failed is not available for the Quick
Recovery Agent, nor the Image Level and Image Level ProxyHost
iDataAgents. These agents do not perform a file level backup/copy.
If viewing the details of a job with a pending or failed status, the Reason
for Job Delay field will contain an Error Code, which, if clicked, will launch
the customer support website displaying troubleshooting article(s) related
to the specific issue.
Page 187 of 199
To view media or mount paths associated with a job history:
history you want to view, click View, and then select the appropriate history.
2. From the Job History window select the filter options, if any, that you want to apply, and then click
OK.
3. From the job history widow, right-click the backup whose media or mount paths you want to view,
and then click View Media.
4. The Media Used By Job ID window displays a list of media or mount paths used by the operation.
5. Click OK.
To view the events associated with a job:
history you want to view, click View, and then click Job History.
view, and then click View Events.
4. The All Found Events window gets displayed. If no events where found for the back up, a message is
displayed to that effect.
5. Click Close.
View the Items that were Moved to Media during SnapProtect
To view the list of items that were moved to tape during SnapProtect backup.
want to view, click View, and then click the necessary options to view a job history.
then click OK.
3. From the Job History window, right-click the operation whose list of items moved to media you want
to view, and then select View Backup Copy file listing. The Backup file List window displays a
list of the backed up files that were included in the backup copy job. You can use the Search option
to find items in the window.
4. Click File -> Exit.
This option is available for the SnapProtect feature.
To view the files moved to media for a backup copy job, right-click the
SnapProtect backup job corresponding to the Backup Copy job and
select View Backup Copy file listing.
View backup items will not display anything for a Backup Copy job.
Page 188 of 199
To view the log files of a Job History:
1. From the CommCell Browser, right-click the entity whose job history you want to view, and then
click to view a job history.
2. From the job history filter window select the filter options, if any, that you want to apply, and then
click OK.
3. From the job history window, right-click the job whose log files you want to view, and then click
View Logs.
4. The contents of the log file related to the selected job history are displayed in the Log File for Job
n window.
View the Items that Were Successfully Content Indexed
To view the list items that were not indexed during content indexing:
1. From the CommCell Browser, right-click the entity whose operations you want to view, click View,
and then click the necessary options to view a job history.
then click OK.
3. From the Job History window, right-click the job for which you want to view the successfully content
indexed items, select View Content Index, and click Successful Items.
4. Click Close.
View the Items that Failed to Content Index
To view the list of items that failed to content index:
1. From the CommCell Browser, right-click the entity whose operations you want to view, click View,
and then click the necessary options to view a job history.
then click OK.
3. From the Job History window, right-click the job for which you want to view the list of items failed to
content index, select View Content Index, and click Failed Items.
4. Click Close.
This option is available for operations that performed content indexing.
This option is available for operations that performed content indexing.
Page 189 of 199

Back to Top
Page 190 of 199
Restore Job History
Overview
Items That Restored
Supported Features
Overview
The Restore History Filter dialog box allows you to view detailed, historical information about restore
jobs.
For information on Job Details displayed in the Job History, see Viewing Job Information.
Once you have chosen your filter options, they are displayed in the Restore Job History window. From
this window you can right-click a restore job to:
View Restore Items; items in the job that were Successful, Failed, Skipped or All. These items, if
any, will be listed in the Restored Files window.
View Job Details of the restore job. The job details will be listed in the Job Details window.
View Events of the restore job. The job events will be listed in the All Found Events window.
View Log files of the restore job. The job log files will be listed in the Log File window.
View the RMAN Log of an Oracle restore job. The RMAN Log will be listed in the Oracle Restore Log
window.
Items That are Restored
When viewing files that are restored in the Restored Files window, each of the files is listed with the
restore status level appended at the end of the file path. The possible status levels are: RESTORED,
FAILED and OLDER.
Successfully restored files will be listed with RESTORED appended to the file path. If files are not
restored/recovered due to errors, the file paths will be appended with FAILED. Under some
circumstances, the system may not restore/recover certain files because they are older versions of the
same files already present in the files system; these files are appended with the word OLDER.
Supported Features
Consider the following.
The NAS NDMP iDataAgents do not support the ability to view failed/successful item lists.
Restore Job History will not display Oracle rman_util jobs at the instance level.
Back to Top
Restore History - How To
View Restore Job History
Page 191 of 199
View the Media of a Job History
View Restore Job History
To view the restored items associated with a job:
restore history you want to view, click View, and then click Restore History.
2. From the Job History filter window, select the filter options, if any, that you want to apply, and then
click OK.
3. From the Job History window, right-click the job whose restored items you want to view; click View
Restore Items, and select from the type of items to view: Successful, Failed, Skipped or All.
4. The Restored Files window will display the selected type of restored items for the job.
5. Click OK.
To view the events associated with a job:
history you want to view, click View, and then click Job History.
view, and then click View Events.
4. The All Found Events window gets displayed. If no events where found for the back up, a message is
displayed to that effect.
5. Click Close.
To view media or mount paths associated with a job history:
history you want to view, click View, and then select the appropriate history.
2. From the Job History window select the filter options, if any, that you want to apply, and then click
OK.
3. From the job history widow, right-click the backup whose media or mount paths you want to view,
and then click View Media.
4. The Media Used By Job ID window displays a list of media or mount paths used by the operation.
5. Click OK.
Page 192 of 199
To view the log files of a Job History:
1. From the CommCell Browser, right-click the entity whose job history you want to view, and then
click to view a job history.
2. From the job history filter window select the filter options, if any, that you want to apply, and then
click OK.
3. From the job history window, right-click the job whose log files you want to view, and then click
View Logs.
4. The contents of the log file related to the selected job history are displayed in the Log File for Job
n window.
Back to Top
Page 193 of 199
Backup Failure Due to Database Block Corruption
Avoiding Intermittent Backup Failures for Oracle on Linux Platforms
Offline Backup with Lights Out Option Fails When Using Default Tries Number
Oracle Backup Fails if the Oracle Instance has the NAS_LANG set to a non American_America.US7ASCII
character
File spfile.ora or init<SID>.ora Must be Populated Correctly Before you Select Log Destinations
Backup Failure Due to Database Block Corruption
If an Oracle database backup operation fails due to corrupted database blocks, an error message will be
displayed. For example:
LISTING 2: r_20030520213618.log
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of backup command on d1 channel at 05/20/2003 21:36:26
ORA-19566: exceeded limit of 0 corrupt blocks for file
/u01/app/Oracle/oradata/MRP/sales_data_01.dbf
In such cases, you should make sure that the Enter the maximum database block corruptions value
is set in the Advanced Backup Options (Oracle Options) tab. It is recommended that you set this value to
match the number of corrupted database blocks identified by RMAN for the database file being backed up.
To identify the number of corrupted database blocks in a data file, refer Oracle documentation.
Avoiding Intermittent Backup Failures for Oracle on Linux Platforms
In order to avoid intermittent backup failures for Oracle on Linux platforms, some additional configuration
steps may be needed. Specifically, if the library libobk.so fails to load, then the backup may fail.
Provided below are steps to take to ensure that this essential library is loaded in the system
configuration.
1. Log in to the Oracle client computer as root.
2. From the system prompt, enter the following command:
ldconfig /<Base_directory_name>
For example: # ldconfig <software installation path>/Base
3. This configuration step will ensure that the libobk.so library is loaded so that backups for Oracle on
Linux can run successfully.
Oracle Backup Fails if the Oracle Instance has the NLS_LANG set to a non
American_America.US7ASCII character
If the Oracle instance has the NLS_LANG set to a non American_America.US7ASCII character, the Oracle
Page 194 of 199
backup operations fail with the following error:
Character conversion not supported
To solve this problem, you need to set the NLS_LANG environment variable on the client computer using
the <oracle_SID>_NLS _LANG registry key, where oracle_SID is the Oracle instance name. For example,
rman10g_NLS_LANG <non American_America.US7ASCII character>
If the registry key is not set, the NLS_LANG variable will be set to American_America.US7ASCII character
by default.
In the case of Oracle RAC iDataAgent, the registry key need to be set in all the RAC instance nodes.
Offline Backup with Lights Out Option Fails When Using Default Tries Number
If the Oracle offline backup with lights out option fails when you use the default value for Tries Number
in the Subclient Properties (Backup Arguments) window, then increase the value to a number greater
than or equal to 5.
File spfile.ora or init<SID>.ora Must be Populated Correctly Before you Select Log
Destinations
Oracle Log Destinations are set up in the spfile.ora or init<SID>.ora file, and they are displayed in
the Add list for the following: Select ArchiveLog Destinations for Backup/Delete fields in the
Subclient Properties (Log Destinations) tab and the Select ArchiveLog Destinations field in both the
Advanced Backup Options (Back up Archive Logs) tab and the Advanced Backup Archive Options (Delete
Archive Logs) tab. However, if the spfile.ora or init<SID>.ora file does not include any log
destinations, the lists will show USE_DB_RECOVERY_FILE_DEST by default, and the backup job will fail if
you select this parameter. Therefore, either do not select log destinations if none are defined in the
spfile.ora or init<SID>.ora file or include the log destinations in either file and then refresh the
database from the Subclient Properties (Contents) tab.
Back to Top
Page 195 of 199
Troubleshooting Oracle Errors
Troubleshooting RMAN Errors
Troubleshooting CommCell Console Errors
Troubleshooting Point-In-Time Recoveries
Caution on the Use of RESETLOGS
Sample Script for Resetting a Database After RESETLOGS
Sample Script for Resetting the Database to an Old Incarnation
Troubleshooting Oracle Errors
If you receive an Oracle error during a backup or restore operation, we recommend that you follow
procedures published by Oracle Corporation on resolving the specific error. We also advise you to
consult with your on-site Oracle database administrator, as needed.
If a duplicate database restore fails with error PLS-00553: character set name is not
recognized; then make sure the character sets are the same between the locations of where you are
running RMAN from and the location of the target database. Because this is an Oracle related issue,
please contact Oracle support for more information.
When using Oracle 10g, a table level restore operation may fail intermittently due to an error in the
Oracle's DataPump utility and the following error message will be displayed:
UDE-00008: operation generated ORACLE error 31623
ORA-31623: a job is not attached to this session via the specified handle
In such cases, set the sNODATAPUMPEXPORT registry key to Y on the client and re-submit the job.
Sometimes, Oracle backup and restore jobs fail due to the large size of the sbtio.log file in the
$UDUMP directory. To resolve this, set the size of the sbtio.log file using the
sMAXORASBTIOLOGFILESIZE registry key. Once the specified size limit is reached, the sbtio.log file
gets pruned automatically.
Troubleshooting RMAN Errors
If the system notifies you that there was an "RMAN error" during a backup or restore operation, we
advise you to view the RMAN Output Log to identify which error was encountered. To view the RMAN
Output Log, do the following:
1. From the CommCell Browser, right-click the desired instance, click All Tasks, click View and
then click either Backup History or Restore History.
2. Click OK on the History Filter dialog.
3. On the Job History window, right-click the desired job, then select View Log File. The RMAN
Once you have identified the specific RMAN error, consult one of the following publications from Oracle
Corporation for information on resolving the specific error, in conjunction with your on-site Oracle
database administrator:
Oracle8i - Backup and Recovery Guide
Oracle8i - Recovery Manager Users Guide and Reference
Page 196 of 199
Oracle9i - Recovery Manager Users Guide
Any RMAN command line operation can fail if the required media resource is unavailable due to a
conflicting resource reservation by another data protection/recovery process or when the resource is
unavailable offline. If this happens, we recommend that you establish or verify the availability of the
required resource then rerun the RMAN command line operation.
If an RMAN command line backup for Oracle fails because it has exceeded the timeout limit while
waiting for a resource to allocate streams, you can increase the timeout limit by adding (or modifying
the value currently entered for) the sALLOCATESTREAMSECS registry key to wait beyond the default
of 86400 seconds (i.e., 24 hours) before failing the backup job.
If an RMAN command line backup fails with the error "Unable to open lock
file /opt/hds/Base/Temp/locks/.dir_lock: Permission denied", it may be because the
"unmask" is set as "022" in .profile for instances on Oracle. If this occurs, change the "unmask" to
"000" or "002" and try the backup again. Also, ensure that the users for Oracle are in the group "dba".
From Oracle release 10g and later, Oracle stopped adding a database reference to the listener.ora
file because it uses dynamic transparent network substrate (TNS) registration, and this can sometimes
cause problems while running Offline Lights Out backups. If an Oracle 10g or 10g R2 backup fails with
the RMAN error "ORA-12528 TNS listener - all appropriate instances are blocking new
connections", then add a reference to the database in the listener.ora file as shown in the example
below, to work around this issue:
SID_LIST_LISTENER =
(SID_LIST =
(SID_DESC =
(SID_NAME = PLSExtProc)
(ORACLE_HOME = C:\oracle\product\10.1.0\db_1)
(PROGRAM = extproc)
)
(SID_DESC =
(SID_NAME = rman10g)
(ORACLE_HOME = C:\oracle\product\10.1.0\db_1)
(SID = rman10g)
)
)
When creating standby databases using Oracle 10g, you need to set the Standby Role Initialization
parameter, DB_FILE_NAME_CONVERT, to add all the temp data files from the primary database
location to the standby database location, as follows:
DB_FILE_NAME_CONVERT='<primary_database_temp_datafile_old_location>','<standby_database
If this parameter is not set, restore will fail with the following error message:
temporary file TEMP01.DBF conflicts with file used by target database
Troubleshooting CommCell Console Errors
If only command line backups have been performed, and a Browse Restore operation is subsequently
attempted from the CommCell Console without first opening and closing the subclient properties, then
the system will display a message indicating that no data was backed up. If this happens, ensure that
you open and then close the subclient properties of the Oracle iDataAgent you are trying to restore,
then try the Browse Restore operation again.
For Oracle 10g, if the instance is configured for autobackup with flash recovery, then restoring the
SPFile from the CommCell Console will not work. The following work-arounds are available in this
situation:
Work-around 1:
Comment out the option "db_recovery_file_dest" from the PFile, then re-create the SPFile using
the new PFile. Afterwards, restoring the SPFile from the CommCell Console should work.
Page 197 of 199
Work-around 2:
Restore the SPFile manually using RMAN with the script below:
RMAN> run {
2> ALLOCATE CHANNEL c1 DEVICE TYPE DISK;
3> restore spfile from autobackup;
4> }
If the line "set linesize 80" is present in the file $ORACLE_HOME/sqlplus/admin/glogin.sql, it may
cause the SrvOraAgent server process on the CommServe to fail when browsing database contents or
executing a backup. To avoid such failures, comment out that line from the file and re-try the browse
or backup operation.
Troubleshooting Point-In-Time Recoveries
Caution should be used when recovering an Oracle database to a point-in-time using the Point In Time
option in the Recover tab of the Oracle Advanced Restore Options dialog box. The reasoning is that this
action executes a powerful RMAN statement called "ALTER DATABASE OPEN RESETLOGS" which will reset
the SCN (System Change Number) and time stamp on every object of the database (i.e., datafiles and
control files).
Archived redo logs have these two values (SCN and time stamp) in their headers, and Oracle will not
apply an archived redo log to a datafile unless the RESETLOGS SCN and time stamps match, to prevent
you from corrupting your datafiles with old archived logs.
Execution of the "ALTER DATABASE OPEN RESETLOGS" statement has the effect of recovering the database
to a time that is not current, hence being reset with old data (i.e., an old incarnation). This is a very
useful operation if the point-in-time to which you are trying to recover is certain and known, but can be
counterproductive if you are guessing at the point-in-time.
If the point-in-time is in question, it is recommended that you select the Restore Data option in the
Advanced Restore Options (Restore) tab and/or the Restore Control File option in the Advanced
Restore Options (Ctrl & SP Files) tab instead of the Point In Time option in the Recover tab. These
options can either be used separately or together, depending on the situation (if used together with
point-in-time, both must use the same point-in-time). This method will allow you to restore the database
to a state that you can make the determination whether or not you have achieved the correct point-in-
time, without invoking the "ALTER DATABASE OPEN RESETLOGS" statement that would reset SCNs and
time stamps on the database objects.
After determining the correct point-in-time through this method, the Point In Time option in the
Recover tab can be safely applied to reset your Oracle database to the desired incarnation.
Sample scripts are provided below for your Oracle database administrator to use as reference for
developing custom scripts that you can run from the RMAN command line, to perform special operations
apart from the CommCell Console.
The following example resets a database after performing an incomplete media recovery:
run {
allocate channel dev1 type disk;
set until logseq 1234 thread 1;
Page 198 of 199
restore database skip tablespace readonly;
recover database;
sql "ALTER DATABASE OPEN RESETLOGS";
release channel dev1;
}
reset database;
The following command makes an old incarnation of database PROD1 current again:
# obtain primary key of old incarnation
list incarnation of database prod1;
shutdown immediate;
# reset database to old incarnation
reset database to incarnation 2;
# recover it
run {
allocate channel dev1 type disk;
restore controlfile;
startup mount;
restore database;
recover database;
sql "ALTER DATABASE OPEN RESETLOGS";
release channel dev1;
}

Back to Top

List of Database Incarnations
DB Key
------
Inc
Key
------
-
DB
Name
------
-
DB ID
-----
CUR
---
Reset SCN
---------
Reset Time
----------
1 2 PROD1 1224038686 NO 1 02-JUL-98
1 582 PROD1 1224038686 YES 59727 10-JUL-98
Page 199 of 199

Oraasfsa

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Oraasfsa

Uploaded by

Copyright:

Available Formats

Features - Oracle iDataAgent

software and MediaAgent must be installed and running (but not

Server, MediaAgent and/or Clients communicate across two-way firewall(s):

software and MediaAgent must be installed and running (but not

Server, MediaAgent and/or Clients communicate across two-way firewall(s):

Server, MediaAgent and/or Clients communicate across two-way firewall(s):

Server, MediaAgent and/or Clients communicate across two-way firewall(s):

You might also like