Database Administrator (DBA) GUIDE Oracle iDataAgentsupport-q.bull.com/ols/product/storage/backup/calypso/release_10_0...Oracle DBA Guide Overview System Requirements Getting Started

Database Administrator (DBA) GUIDE

Oracle iDataAgent

Published On: 11/19/2013 V10 Service Pack 4A Page 1 of 100

Oracle DBA Guide

Overview

System Requirements

Getting Started - Backup Administrator

Deployment On unix

Configuration

Getting Started - Database Administrator

Prerequisites

Configuration

Backup

Restore

data Retention

Table of Contents


Overview - Oracle DBA

Introduction

Key Features

Terminology

The Oracle iDataAgent enables you to use Oracle Recovery Manager (RMAN) to back up Oracle databases to media directly. The Oracle iDataAgent provides a unique, simplified end-to-end backup and recovery solution for Oracle databases. It also provides more granular backup and recovery of specific data files and logs. The product can be used to create duplicate databases and perform out of place restores of Oracle databases. The backups are kept based on the retention policy set by the database administrators.

The Oracle iDataAgent offers the following key features for database administrators:

Seamless integration with RMAN.

DBAs can run RMAN scripts like they used to do it always.

Use existing RMAN scripts for backups and restores without any changes.

Schedule backup and restores operations using Oracle Enterprise Manager OEM or Control M or Cron.

Client side Deduplication

Deduplication on the source (client) identifies and eliminates redundant data at the source client, thereby shrinking the storage space as well as the network bandwidth required for backups.

The following diagram illustrates Data Protection Suite Oracle backups.

The Oracle iDataAgent documentation uses the following terminology:

Overview Deployment - Windows Deployment - Windows Cluster Deployment - Unix Deployment - Unix Cluster Configuration

Table of Contents

Introduction

Key Features

Terminology

ClientThe computer in which the iDataAgent is installed and contains the data to be secured.

InstanceThe Oracle database to be used for the backup and restore operations.

SubclientThe Oracle data to be backed up.

Back to top


System Requirements - Oracle iDataAgent

The following requirements are for the Oracle iDataAgent:

System Requirements Supported Features License Requirements

Application/Operating System Architecture

Oracle 12c Database (Enterprise or Standard Edition) on:

Linux Oracle Linux

Oracle Linux 6.x with glibc 2.12.x x64

Oracle Linux 5.x with glibc 2.5.x x64

Red Hat Enterprise Linux/CentOS

Red Hat Enterprise Linux/CentOS 6.x with glibc 2.12.x x64, Power PC or compatible processors

Red Hat Enterprise Linux/CentOS 5.x with glibc 2.5.x x64, Power PC or compatible processors

Solaris Solaris 11.x x64, Sparc T/M series

Solaris 10.x x64, Sparc T/M series

Windows Windows 2008

Microsoft Windows Server 2008 Editions with a minimum of Service Pack 1*

*Core Editions not supported

Oracle 10g/11g (R1, R2 or higher) Databases (Enterprise or Standard Edition) on:

AIX AIX 5.3, 6.1, 7.1 Power PC

HP-UX HP-UX 11i v3 (11.31) Itanium

HP-UX 11i v2 (11.23) Itanium

Linux Oracle Linux

Oracle Linux 6.x with glibc 2.12.x x86, x64 or compatible processors

Oracle Linux 5.x with glibc 2.5.x x86, x64 or compatible processors

Oracle Linux 4.x with a minimum of glibc 2.3.4 x86, x64 or compatible processors

Red Hat Enterprise Linux/CentOS

Red Hat Enterprise Linux/CentOS 6.x with glibc 2.12.x x86, x64, Power PC or compatible processors

Red Hat Enterprise Linux/CentOS 5.x with glibc 2.5.x x86, x64, Power PC or compatible processors

Red Hat Enterprise Linux/CentOS 4.x with a minimum of glibc 2.3.4 x86, x64, Power PC or compatible processors

SuSE Linux (SLES)

SuSE Linux 11.x with glibc 2.9.x and above x86, x64, Power PC, Itanium or compatible processors

SuSE Linux 10.x with glibc 2.4.x x86, x64, Power PC or compatible processors

Z-Linux Red Hat Enterprise Linux

Red Hat Enterprise Linux 6.x s390x 64-bit



SuSE Linux (SLES)

SuSE Linux 11.x Enterprise Server s390x 64-bit

SuSE Linux 10.x Enterprise Server s390x 64-bit

Solaris Solaris 11.x x64, Sparc T/M series

Solaris 10.x x64, Sparc T/M series

Windows Microsoft Windows Server 2003 Editions with a minimum of Service Pack 2


The software can be installed on a Cluster if clustering is supported by the above-mentioned operating systems.

For information on supported cluster types, see Clustering - Support.

1 GB of minimum disk space is required for installing the software.

256 MB of free disk space is required for job result directory.

256 MB of free disk space is required for log directory.

Express Editions of Oracle 10g/11g (R2) Databases are supported on all operating systems supported by the Oracle application server.

Oracle Exadata Database Machine is supported on the following Oracle Database versions:

Oracle 11g (11.1.0.7)

Oracle 11g R2 (11.2.0.1 or higher)

Data Protection of data residing on global and non-global zones is supported.

For a comprehensive list of supported components, see Unix Virtualization.

Data protection on Logical Partitioning (LPAR) and Workload Partitioning (WPAR) is supported.

The File System iDataAgent will be automatically installed during installation of this software, 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 - AIX File System iDataAgent

System Requirements - HP-UX File System iDataAgent

System Requirements - Linux File System iDataAgent

System Requirements - Solaris File System iDataAgent

The operating system must have been installed with at least the user level software option selected.

SELinux

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 an SELinux policy module, perform the following steps as user "root":

1. Create the following files in the /usr/share/selinux/devel directory:

Server 2003

Windows Windows 2008

Microsoft Windows Server 2008 Editions with a minimum of Service Pack 1*

*Core Editions not supported

Cluster - Support

Hard Drive

Express Database Edition Support

Oracle Exadata Database Machine Support

Solaris Zones/Containers Support

AIX LPAR/WPAR Support

Miscellaneous

File Name Content of the File<directory>/<file_name>.tewhere:

<directory> is /usr/share/selinux/devel

The content of the file should be as follows:

policy_module(<name>,<version>)

##############################


2. Create the policy file from command line. Use the following command. Ensure that you give the following commands in the /usr/share/selinux/develdirectory.

[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]#

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.

.NET Framework

.NET Framework 4.0 is automatically installed. Note that .NET Framework 4.0 can co-exist with other versions of this software.

Microsoft Visual C++

Microsoft Visual C++ 2010 and 2008 Redistributable Packages are automatically installed. Note that these Visual C++ Redistributable Packages can co-exist with other versions of this software.

DISCLAIMER

Minor revisions and/or service packs that are released by application and operating system vendors are supported by our software but may not be individually listed in our System Requirements. We will provide information on any known caveat for the revisions and/or service packs. In some cases, these revisions and/or service packs affect the working of our software. Changes to the behavior of our software resulting from an application or operating system revision/service pack may be beyond our control. The older releases of our software may not support the platforms supported in the current release. However, we will make every effort to correct the behavior in the current or future

<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

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>.fcwhere:

<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.fc

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 directory>/Base/libCTreeWrapper.so --gen_context(system_u:object_r:texrel_shlib_t,s0)/opt/<software installation directory>/Base/libCVMAGuiImplgso --gen_context(system_u:object_r:texrel_shlib_t,s0)/opt/<software installation directory>/Base/libdb2locale.so.1 --gen_context(system_u:object_r:texrel_shlib_t,s0)/opt/<software installation directory>/Base/libdb2osse.so.1 --gen_context(system_u:object_r:texrel_shlib_t,s0)/opt/<software installation directory>/Base/libDb2Sbt.so -- gen_context(system_u:object_r:texrel_shlib_t,s0)/opt/<software installation directory>/Base/libdb2trcapi.so.1 --gen_context(system_u:object_r:texrel_shlib_t,s0)/opt/<software installation directory>/Base/libDrDatabase.so --gen_context(system_u:object_r:texrel_shlib_t,s0)/opt/<software installation directory>/Base/libIndexing.so --gen_context(system_u:object_r:texrel_shlib_t,s0)/opt/<software installation directory>/Base/libSnooper.so -- gen_context(system_u:object_r:texrel_shlib_t,s0)


releases when necessary. Please contact your Software Provider for any problem with 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


Supported Features - Oracle iDataAgent

The following table lists the features that are supported by this Agent.

System Requirements Supported Features License Requirements

Feature Sub-Feature Support Comments

Advanced Backup/Archive OptionsData tab - Catalog

Data tab - Verify Synthetic FullJob Retry tab

Media tab - Allow other Schedule to use Media SetMedia tab - Mark Media Full on Success

Media tab - Reserve Resources Before ScanMedia tab - Start New Media

Startup tab

VaultTracking tab

Comments Includes several additional options in the Backup Archive Logs, Delete Archive Logs, Custom RMAN Script, and Oracle Options tabs.

Advanced File System iDataAgent Options

Automatic File System Multi-Streaming

On Demand Data Protection Operation

Restore by JobsRestore Data Using a Map FileComments For On Demand Data Protection Operations, see On Demand

Instances.

Alerts and Monitoring Global Alerts

Job-Based Alerts*

Comments

Automatic Updates Automatic Updates

Comments

Backup/Archive OptionsDifferential Backup

Full Backup

Incremental Backup

Other Backup TypesSynthetic Full BackupComments

Backward Compatibility Version 8

Version 9

Comments

BrowseBrowse from Copy Precedence

Browse the Latest Data

Browse Using FiltersExclude Data BeforeFindFull Backup Transparent BrowseImage Browse

No Image Browse


Page Size

Specify Browse PathSpecify Browse Time

Subclient Browse

Use MediaAgent

View All VersionsComments

Additionally, Browse Database Tables is supported.

Clustering Unix Cluster

Windows - Microsoft Cluster (MSCS)

Windows - Non-Microsoft ClusterComments

Command Line InterfaceCommand Line Interface

Comments

CommCell Migration CommCell Migration

Comments CommCell Migration is not supported with IntelliSnap backup when using Data Replicator snapshot engine.

Content Indexing Offline Content Indexing

Comments

Data Aging Basic Retention Rules

Deleting a Job

Extended Retention Rules

Retaining a Job

Unique Data Aging Rules

Comments Extended Retention Rules are supported for offline/selective online fulls.

Data Compression Client Compression

Hardware Compression

MediaAgent Compression

Comments

Data Encryption Data Encryption Support

Third-party Command Line Encryption SupportComments

Data MultiplexingMultiplexing

Comments

Deduplication MediaAgent Deduplication

Source Deduplication

Comments

Erase Backup/Archived Data Erase Data by Browsing

Erase StubsComments

Global Filters Global Filters

Comments

Installation Custom Package

Decoupled Install

Remote Install

Restore Only Agents


Silent Install

CommentsDecoupled Install is supported on Unix; not supported on Windows.

To install this agent as restore only, see Installing Restore only Agents

Installing 32-bit Components on a Microsoft Windows x64 Platform

Install 32-bit On x64

Comments

Job Restart - Data ProtectionNot Restartable

Restarts from the BeginningRestarts from the Beginning of the DatabaseRestarts from the Point-of-Failure

Comments Third-party command line operations and selective online full backup jobs are Not Restartable.

Offline backup jobs Restart from the Beginning.

Job Restart - Data RecoveryNot Restartable

Restarts from the BeginningRestarts from the Beginning of the DatabaseRestarts from the Point-of-Failure

Comments Third-party command line operations are Not Restartable.

List Media List Media Associated with a Specific Backup Set or InstanceList Media Associated with IndexList Media Associated with Specific Files and/or FoldersList Media Associated with Specific JobsComments

Multi Instancing Multi Instance

Comments Supported on Unix; not supported on Windows.

Multi Instancing is not supported for SnapProtect Backup.

Optimized ScanOptimized Scan

Comments

Pre/Post Processes Pre/Post Process with Data Protection and RecoveryComments

Restore/Recover/Retrieve DestinationsCross-Application Restores (Different Application version)Cross-Platform Restores - Different Operating SystemCross-Platform Restores - Same Operating System - Different VersionIn-place Restore - Same path/ destination - Same ClientOut-of-place Restore - Different path/ destinationOut-of-place Restore - Same path/ destination - Different ClientRestore Data Using a Map FileRestore to Network Drive /NFS-Mounted File SystemComments See Advanced Restore - Oracle iDataAgent for this iDataAgent.

Restore/Recover/Retrieve Options Automatic Detection of Regular ExpressionsFilter Data From Recover OperationsRename/ Redirect Files on Restore

Restore Data Using Wildcard ExpressionsRestore Data with Pre/Post Processes

Restore from Copies

Skip Errors and ContinueUse Exact Index


Additional features are listed below:

Use MediaAgent

Comments

Restore/Recover/Retrieve Overwrite Options

Overwrite Files

Overwrite if file on media is newerRestore only if target existsUnconditional OverwriteUnconditionally overwrite only if target is a DataArchiver stubComments

Schedule Policy Agent Specific Data Protection Schedule PolicyAll Agent Types Schedule Policy

Comments

Storage Policies Incremental Storage Policy*

Standard Storage Policies

Comments Incremental Storage Policy does not support Transaction Log backups for this agent.

Subclient Policies SubClient Policy

Comments

Upgrade Netware - Local

Unix - Remote (Push)Unix/Linux - LocalUnix/Linux - SilentUnix/Linux/Macintosh - Local

Unix/Linux/Macintosh - SilentUpgrade from CommCell Console

Windows - Local

Windows - Remote (Push)

Windows - Silent

Comments

User Administration and Security Backup Set/Archive Set

InstanceSubclientComments

Activity Control Deconfigure/Reconfigure Components Auxiliary Copy LanguagesCommCell Console MediaAgentGridStor Scheduling Log Files Snapshot EnginesOperation window VaultTracker IntelliSnap Backup Restore/Recover/Retrieve - Other Options VaultTracker Enterprise Job Restart - Data Collection Cloud Storage



Install the software on a Windows computer on which the Oracle server resides.

The computer will be added as a client in the CommCell as soon as the installation completes successfully.

The software installation may require a system reboot if a pending rename operation from a previously installed application is found in the operating system, hence, plan your installation at a convenient time.

System Requirements

Verify that the computer in which you wish to install the software satisfies the minimum requirements specified in System Requirements.

Download Software Packages

Download the latest software package to perform the install.

1. Log on to the client computer as an Administrator or as a member of the Administrator group on that computer.

2. Run SetupAll.exe from the Software Installation Discs.

3. Click I accept the terms in the license agreement.

Click Next.

4. Click Standard.

Click Next.


Where to Install

Planning Your Installation

Before You Begin

Installation

The software can be installed using one of the following methods:

Method 1: Interactive Install - Standard

Use this procedure to install the software using the standard installation options.

Method 2: Interactive Install - Custom

Use this procedure to install the software by specifying installation settings and options.

Method 1: Interactive Install - Standard


5. Click Join an Existing CommCell.

Click Next.

6. Click Oracle.

Click Next.

7. Verify the default location for software installation.

Click Next.

If necessary, click Browse... to change the default location.

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

8. Click Install.

9. Click Yes.

10. Click Next.

The Summary on your screen should reflect the components you selected for install, and may look different from the example shown.


11. Select one of the following:

If firewall configuration is not required, click Next.

If this computer and the CommServe is separated by a firewall, click Configure firewall services.

For firewall options and configuration instructions, see Firewall Configuration and continue with the installation.

12. Enter the fully qualified domain name of the CommServe in the CommServe Host Name box.

Do not use space and the following characters when specifying the CommServe Host Name:

\|`~!@#$%^&*()+=<>/?,[]{}:;'"

Click Next.


13. Enter the following:

The local (NetBIOS) name of the client computer is displayed in the Select a Client name list.

If necessary you can also type a new (friendly) name for the client in this box. This name will be used in the CommCell and will also be displayed in the CommCell Console.

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 (NIC card).

If the computer has multiple network interfaces, select the interface name that is preferred for communication with the CommServe.

Click Next.

14. Select one of the following options:

If you do not want to disable Windows Firewall, click Next.

If you want to disable Windows Firewall for all profiles, click Yes, disable Windows Firewall for all profiles and then click Next.

15. Select a storage policy from the Storage Policy list.

Click Next.

If a component is already installed on this computer, this screen will not be displayed; instead, the install program will use the same name as previously specified.

You will get this screen if you did not configure the firewall settings in step 11.

If you do not have a Storage Policy, the list will not be displayed. You can create the Storage Policy later in step 20.


16. Click Next.

17. Click OK.

18. Click Reboot Now.

Stop the Oracle services by clicking Service Control Manager.

This screen will reflect the components you selected for install, and may look different from the example shown.


19. To create a storage policy, you must have configured a library in the CommCell.

If you do not already have a library configured, go to Disk Library Creation.

If you have a library configured, go to Storage Policy Creation.

DISK LIBRARY CREATION:

1. From the CommCell Browser, navigate to Storage Resources, right-click the Libraries, point to Add and then click Disk Library...

Alternatively, you can also navigate to MediaAgents, right-click <MediaAgent>, point to All Tasks | Create Library and then click Disk Library...

2. From the Add Disk Library dialog box, specify the following:

In the Name box, specify name of the disk library.

From the MediaAgent list, select the MediaAgent.

Perform one of the following:

Select Local Path if you wish to specify a local path in the MediaAgent computer.

In the Disk Device box, type the name of the folder in which the disk library must located or click button to select the folder.

Select Network Path, if you wish to specify a network path as the target share.

In the Connect As box, type the user name.

In the Password and Verify Password box, type the password to access the network share.

In the Folder box, type the mount path or click button to select a mount path.

Click OK.

3. The newly created disk library will be displayed under Libraries node.

This will create a library and Storage Policy. Click to proceed to the Configuration section.

Storage Policy Creation

1. From the CommCell Browser, navigate to Policies.

2. Right-click the Storage Policies and then click New Storage Policy.

3. Follow the prompts displayed in the Storage Policy Wizard. The required options are mentioned below:

Select the Storage Policy type as Data Protection and Archiving and click Next.

Enter the name in the Storage Policy Name box and click Next.

From the Library list, click the name of a disk library to which the primary copy should be associated and then click Next.

Ensure that you select a library attached to a MediaAgent operating in the current release.

From the MediaAgent list, click the name of a MediaAgent that will be used to create the primary copy and then click Next.

For the device streams and the retention criteria information, click Next to accept default values.

Select Yes to enable deduplication for the primary copy.

From the MediaAgent list, click the name of the MediaAgent that will be used to host the Deduplication Database (DDB).

In the Location box, type the name of the folder in which the DDB must be located or click the Browse button to select the folder and then click Next.

Review the details and click Finish to create the Storage Policy.

This will create a storage policy. Click to proceed to the Configuration section.

If you already have a storage policy selected in step 16, click to proceed to the Configuration section.

If you do not have Storage Policy created, continue with the following step.


Default Options Selected During Standard Install

Listed below are the default options that are automatically selected while performing the Standard Install.

Components installed by default during Standard Install

Listed below are the components that are installed by default while performing the Standard Install:

1. Log on to the client computer as an Administrator or as a member of the Administrator group on that computer.



Click Next.

OPTION ENABLED / DISABLED DESCRIPTION

Add programs to the Windows Firewall Exclusion List Disabled This option allows you to add Data Protection Suite programs to the Windows Firewall exclusion list.

This option is not selected.Global Filter Options Enabled This option is used to filter out specific directories or files from the

backups within the CommCell. The filters are set using the Control Panel in the CommCell Console and, if enabled, they will be effective for the default subclient.

Cell level policy is automatically selected.

SELECTED PACKAGE COMPONENTS INSTALLED

Oracle Agent Oracle iDataAgent File System Core Windows File System

Method 2: Interactive install - Custom


4. Click Custom.

Click Next.

5. Click Select components to install on this computer and click Next.

6. Expand Database, and then click Oracle.

Click Next.



Click Next.





8. Click Install.



9. Click Yes.

10. Click Next.








\|`~!@#$%^&*()+=<>/?,[]{}:;'"

Click Next.







Click Next.

14. The default port numbers used for CommCell communication is displayed. If necessary, you can modify the port numbers.

Click Next.


This screen will not appear if the default port numbers are not used for CommCell communication.





16. Select Add programs to the Windows Firewall Exclusion List, to add CommCell programs and services to the Windows Firewall Exclusion List.

Click Next.


This option enables CommCell operations across Windows firewall by adding CommCell programs and services to Windows firewall exclusion list.

It is recommended to select this option even if Windows firewall is disabled. This will allow the CommCell programs and services to function if the Windows firewall is enabled at a later time.


17. Select a Client Group.Click Next.


Click Use Cell level Policy to inherit the global filter policy configuration set for the CommCell.

Click Always use Global Filters to apply the global filters policy to the default subclient regardless of the policy set for the CommCell.

Select Do not use Global Filters if you plan to define specific filters for the Agent.

Click Next.

This screen will not be displayed if Client Groups are not configured in the CommCell Console. For more information, see Client Computer Groups.



Click Next.

20. Click Next.

21. Click OK.

22. Click Reboot Now.

If you do not have a Storage Policy, the list will not be displayed. You can create the Storage Policy later in step 24.


This screen will reflect the components you selected for install, and may look different from the example shown.


















Click OK.





















Custom Package

Create a compact software package for quick deployment to multiple clients.

Decoupled Install

Install the software first and later register the client in the CommCell.

Remote Install

Deploy the software from CommCell Console on multiple clients.

Installing Restore only Agents

Setup a client in the CommCell for restore purposes.

Silent Install

Deploy the software silently on multiple clients.

Additional Installation Methods



SKIP THIS PAGE IF YOU ARE NOT INSTALLING THIS AGENT ON A MICROSOFT CLUSTER. Steps involved in installing the Oracle iDataAgent in a Clustered environment:

1. Install the software on physical Nodes

2. Configure the Cluster Group Client

System Requirements


Network TCP Port Requirements

Review the Network TCP Port requirements specified in Network TCP Port Requirements.

License Requirements

Review the license requirements specified in License Requirements.



Several additional options are available for remotely installing the software from CommCell Console, refer to Install Software from the CommCell Console (Remote Install) for more information.

1. From the active node of the cluster group, log on to the physical computer as an Administrator or as a member of the Administrator group on that computer.



Click Next.

4. Click Custom.


Before You Begin

Install the software on physical Nodes

If you do not wish to protect physical nodes with a specific agent, you can install that agent in 'restore only' mode, doing so will prevent the consumption of additional license per node. See Installing Restore Only Agentsfor more information. Alternatively, you can release license from the CommCell Console for a specific agent after installing it on the physical nodes. Refer to Releasing a License section to see the procedure for releasing a license.

The software can be installed on the Physical nodes using one of the following methods:

Method : Interactive Install

Use this procedure to Install the software on the physical nodes from the active node of a cluster group.

Method : Interactive install


Click Next.

5. Click Select components to install on this computer and click Next.

6. Expand Database, and then click Oracle.

Click Next.


Click Next.






8. Click Install.

9. Click Yes.

10. Click Next.









\|`~!@#$%^&*()+=<>/?,[]{}:;'"

Click Next.








Click Next.


Click Next.





This screen will not appear if the default port numbers are not used for CommCell communication.



16. Select Add programs to the Windows Firewall Exclusion List, to add CommCell programs and services to the Windows Firewall Exclusion List.

Click Next.

17. Select a Client Group.Click Next.

This option enables CommCell operations across Windows firewall by adding CommCell programs and services to Windows firewall exclusion list.

It is recommended to select this option even if Windows firewall is disabled. This will allow the CommCell programs and services to function if the Windows firewall is enabled at a later time.

This screen will not be displayed if Client Groups are not configured in the CommCell Console. For more information, see Client Computer Groups.



Click Use Cell level Policy to inherit the global filter policy configuration set for the CommCell.

Click Always use Global Filters to apply the global filters policy to the default subclient regardless of the policy set for the CommCell.

Select Do not use Global Filters if you plan to define specific filters for the Agent.

Click Next.


Click Next.

20. Click Next.

If you do not have a Storage Policy, the list will not be displayed. You can create a Storage Policy later using the steps described in the Configuring Storage Policy section.



21. Click Yes.

When you click Yes, the software automatically retrieves the list of nodes to which the current active node can failover.

22. Select cluster nodes from the Preferred Nodes list and click the arrow button to move them to the Selected Nodes list.

Once you complete your selections, click Next.

The list of Preferred Nodes displays all the nodes found in the cluster; from this list, you are required to select the cluster nodes configured to host this cluster group server.

23. Specify User Name and Password of the Domain Administrator account to perform the remote install on the cluster nodes you selected in the previous step.

Click Next.

The Domain Administrator user account that you specify here must have Administrator rights on all the cluster nodes that you selected in the previous step.


The Installer tries to install the software on all the nodes (physical computers) that you have selected.

The progress of the remote install for the cluster nodes is displayed on the Remote Install Progress screen.

24. Click Finish.

25. Click Finish.

If the software is not installed successfully on any of the passive nodes that you selected, or if any passive node is not available during the installation, a separate installation from the CommCell Console needs to be performed on that node in order to prepare it for a failover protection.

For remote install instructions, see Remote Install.


After installing the software successfully on all the physical computers that host the Cluster Group, you must configure the Cluster Group Client from the CommCell Console. Use the steps described in the Configure the Cluster Group Client section fro configuring the Cluster Group Client.

1. From the CommCell Browser, right-click the Client Computers node, point to New Client | Clustered Server and then click Windows Cluster.

2. In the Client Name box, type a name for the cluster group. The Client name can be any unique name.

In the Host Name box, type the fully qualified domain name of the cluster group.

Host Name is the fully qualified domain name of the cluster group. See the screenshot below for reference.

Configure the Cluster Group Client

The Host name of the cluster group client should not be used by any existing client in your CommCell.


3. Review the cluster group information and click Finish.

Advanced Client Properties window is displayed now.

4. On the Advanced Client Properties dialog box, click the Cluster Group Configuration tab. All the Windows clients that are available in the CommCell will be listed in the Available list. Select the physical computers (nodes) where you installed the necessary Agents from the Available list, and then click Add > to move the client to the Selected list.

5. Click the Agents tab.

If the client computer properties dialog box is not displayed automatically, then you need to open it manually: Right-click the <Cluster Group Client>, and then click Properties. Click Advanced on the Client Computer Properties dialog box. Click the Cluster Group Configuration tab on the Advanced Client Properties dialog box.


Select the Agents you want to use in the cluster group client from the Available list and click Add > to move the Agent to the Selected list.

6. Click the Job Configuration tab.

Type or click Browse to specify the path for the Job Results Directory in the cluster group client.

Click OK.

If you do not have a Storage Policy created, use the following steps to create a storage policy:

To create a storage policy, you must have configured a library in the CommCell.














In order to configure a Cluster Group Client, the agents should be installed on all the clustered nodes for proper failover. If an Agent is not installed on all the nodes, then the Agents selection tab on the Advanced Client Properties window will display the Agent name in plain text (not in bold). However, you can still configure the Cluster Group Client even when the Agents are not installed on a particular node; installation can be done later using Remote install procedure.

Ensure that the Job Results Directory resides on a shared clustered drive. In the case of MediaAgent and ContinuousDataReplicator, the Job Result directory path will be used for the Index Cache and CDR Log directories respectively if no directory location is provided.

Configuring Storage Policy




Click OK.
















Remote Install





SKIP THIS PAGE IF YOU ARE NOT INSTALLING ON UNIX CLIENT.

Install the software on a computer on which the Oracle server resides.

On AIX, it is recommended to grant read permissions for others (chmod o+r) on shared libraries and executables so that the services are started without any issues.

For Solaris, software can be installed on one of the following:

Unix computer hosting the global zone on which Oracle Database application resides.

Unix computer in a non-global zone on which Oracle Database application resides.

Follow the steps given below to install the Oracle iDataAgent.

The computer will be added as a client in the CommCell as soon as the installation completes successfully.

System Requirements




1. Logon to the client computer as root.

If you do not have root access, acquire the root access credentials from the system administrator.

2. Use the following options depending upon your environment:

3. Run the following command from the Software Installation Package or mount point:


Where to Install

Before You Begin

Installation

The software can be installed using one of the following methods:

Method 1: Interactive Install

Use this procedure to install the software using the custom installation options.

Method 2: Custom Package

Create a compact software package for quick deployment to multiple clients.

Method 1: Interactive Install

Mount the Software Installation Discs on a global zone or a Unix machine using the following command:

Mount the Software Installation Discs on the non-global zone using the following commands:

Connect to the non-global zone terminal.

mount -t iso9660,udf /dev/cdrom /mnt/cdrom

mkdir <Non-Global Zone root location>/<Non-Global Zone local directory>

mount –F lofs <Global zone software Install Disc mount point> <Non-Global Zone root location>/<Non-Global Zone local directory>

./cvpkgadd


4. The product banner and other information is displayed.

Press Enter.

5. Read the license agreement. Type y and press Enter.

6. Press Enter.

7. If your computer is 32-bit, or if you want to install 32-bit binaries on 64-bit computer, press Enter.

If your computer is 64-bit, and want to install 64-bit binaries, type 2, and then press Enter.

8. The default network interface name of the client computer is displayed if the computer has only one network interface (NIC card), press Enter to accept.

If the computer has multiple network interfaces, enter the interface name that is preferred for communication with the CommServe, and then press Enter.

9. The local name of the client computer is displayed, press Enter to accept.

If necessary you can also enter a new (friendly) name for the client, and then press Enter. This name will be used in the CommCell and will also be displayed in the CommCell Console.


10. Type the number associated with the Oracle iDataAgent and press Enter.

Selecting Unix Setup TaskPlease select a setup task you want to perform from the list below:Advanced options provide extra setup features such as creating custom package, recording/replaying user selections and installing External Data Connector software.1) Install data protection agents on this computer2) Advanced options3) Exit this menuYour choice: [1]

This prompt is displayed only when you are installing on AIX, HP-UX, or Solaris computers. You can determine this by verifying whether all the components that you wish to install in this computer are supported in 64-bit in System RequirementsNote that when the first component is installed using 64-bit binaries, you cannot subsequently install another component using 32-bit. (Or vice-versa.)

32 or 64?This machine supports both 32 bit and 64 bit binaries. By default, we will install 32 bit binary set that has full support for all the modules included in this package. Please note that 64 bit binary set currently only support limited modules.1) All platforms(32 bit)2) FS and MA only(64 bit)Your choice: [1]

The interface names and IP addresses depend on the computer in which the software is installed and may be different from the example shown.

Setting Client/Physical Machine Host NameWe found one network interface available on your machine. We will associate it with the client being installed, and it will also be used by the CommServe to connect to the client. 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 check the interface name below, and make corrections if necessary:Client/Physical Machine Host Name: [myclient.company.com]

Setting Client NamePlease 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.Physical Machine Client name: [myclient]

Selecting Modules to Install.[ ] 1) UNIX File System iDataAgent [1101] [CVGxIDA][ ] 2) MediaAgent [1301] [CVGxMA]


11. Type d for Done, and press Enter.

12. Press Enter.

13. Press Enter.

14. Verify the default path for software installation.

Press Enter.

If necessary, enter a path to modify the default path and press Enter.


Do not use the following characters when specifying the path:

!@#$%^&*():/?\


15. Verify the default path for log files.

Press Enter.

[ ] 3) ProxyHost iDataAgent [1102] [CVGxProxyIDA][ ] 4) Documentum iDataAgent [1126] [CVGxDctmIDA][ ] 5) Oracle iDataAgent [1204] [CVGxOrIDA][ ] 6) SAP for Oracle [1205] [CVGxOrSAP][ ] 7) SAP for MaxDB [1206] [CVGxSAPMAXDB][ ] 8) Informix iDataAgent [1201] [CVGxIfIDA][ ] 9) Sybase iDataAgent [1202] [CVGxSybIDA][ ] 10) DB2 iDataAgent [1207] [CVGxDB2][ ] 11) MySQL iDataAgent [1208] [CVGxMySQL][ ] 12) PostGres iDataAgent [1209] [CVGxPostGres][ ] 13) Lotus Notes Database iDataAgent [1051] [CVGxLndbIDA]>) >>>>>>>>>>>> NEXT PAGE >>>>>>>>>>>>[a=all n=none r=reverse q=quit d=done >=next <=previous ?=help]Enter number(s)/one of "a,n,r,q,d,>,<,?" here: 5

Selecting Modules to Install.[ ] 1) UNIX File System iDataAgent [1101] [CVGxIDA][ ] 2) MediaAgent [1301] [CVGxMA][ ] 3) ProxyHost iDataAgent [1102] [CVGxProxyIDA][ ] 4) Documentum iDataAgent [1126] [CVGxDctmIDA][X] 5) Oracle iDataAgent [1204] [CVGxOrIDA][ ] 6) SAP for Oracle [1205] [CVGxOrSAP][ ] 7) SAP for MaxDB [1206] [CVGxSAPMAXDB][ ] 8) Informix iDataAgent [1201] [CVGxIfIDA][ ] 9) Sybase iDataAgent [1202] [CVGxSybIDA][ ] 10) DB2 iDataAgent [1207] [CVGxDB2][ ] 11) MySQL iDataAgent [1208] [CVGxMySQL][ ] 12) PostGres iDataAgent [1209] [CVGxPostGres][ ] 13) Lotus Notes Database iDataAgent [1051] [CVGxLndbIDA]>) >>>>>>>>>>>> NEXT PAGE >>>>>>>>>>>>[a=all n=none r=reverse q=quit d=done >=next <=previous ?=help]Enter number(s)/one of "a,n,r,q,d,>,<,?" here: d

Deciding if to Config for Laptop or Desktop BackupsDo you want to configure the iDataAgent for laptop or desktop backups?Config for Laptop or Desktop Backups? [no]

Deciding if to Install Agents for Restore OnlyDo you want to install the agents for restore only without consuming licenses?Install Agents for Restore Only? [no]

Preparing Installation DirectoryPlease specify where you want us to install Data Protection Suite binaries.It must be a local directory or NFS and there should be at least 281MB 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]




!@#$%^&*():/?\


All the modules installed on the computer will store the log files in this directory.

16. Press Enter.

17. Type the Group name and press Enter.

Press Enter again.

18. Type d for done with the selection and press Enter.

Preparing Log DirectoryPlease specify where you want to keep Data Protection Suite log files.It must be a local directory or NFS share and there should be at least 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]

Deciding If to Use a Unix GroupMost 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, you will need to specify the access permissions later.If you're planning to backup Oracle DB you should use "dba" group.Would you like to assign a specific group to Software? [yes]

Setting Unix GroupPlease 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: testgrp1REMINDERIf 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 "testgrp1"..Press <ENTER> to continue...

This screen is displayed if you do not assign any group to the software and type no in step 13.

Setting Access Permissions for Group and Other UsersInstaller will assign full access rights to root user for all installed Data Protection Suite files and its processes.For group and any other users, you can specify the access permissions now.If you did not assign a dedicated group in previous step, make sure you specify sufficient access rights for other users if you are also planning to install Data Protection Suite agents involving third party software protection.[X] 1) Allow read permission to group users[X] 2) Allow write permission to group users[X] 3) Allow execute permission to group users[X] 4) Allow read permission to other users[ ] 5) Allow write permission to other users[X] 6) Allow execute permission to other users[a=all n=none r=reverse q=quit d=done >=next <=previous ?=help]



Press Enter.

20. Press Enter.

21. Do one of the following:

If firewall configuration is not required, press Enter.

If this computer and the CommServe is separated by a firewall, type Yes and then press Enter.

For firewall options and configuration instructions, see Firewall Configuration.

22. Type the fully qualified domain of the CommServe host name and press Enter.


\|`~!@#$%^&*()+=<>/?,[]{}:;'"

23. If you have enabled per-client certificate on CommServe, type y and press Enter.

Else, press Enter.

24. Choose one of the following:

1 - To inherit global filter policy configuration set for the CommCell.

2 - To apply the global filters policy to the default subclient regardless of the policy set for the CommCell.

Enter number(s)/one of "a,n,r,q,d,>,<,?" here: d

Setting Instance Port Number of cvdEvery 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]

Setting Instance Port Number of EvMgrCEvery 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: 8400Port Number for EvMgrC: [8402]

Deciding If to Configure FirewallYou need to configure firewall settings if there is a firewall between this client and the CommServe.Is there a firewall between this client and the CommServe? [no]

Setting CommServe Host NamePlease specify hostname of the CommServe below. Make sure the hostname is fully qualified, resolvable by the name services configured on this machine.CommServe Host Name: mycommserve.company.com

Specifying If CommServe Per-Client Certificate is EnabledIf you have checked "Force per-client certificate authentication on CommServe" on the CommServe or Proxy, you need to provide installer with a Temp Certificate.This Temp Certificate can be obtained by opening "Certificate Administration Applet" from the Java GUI's Control Panel, clicking "Temp Certificate" button, selecting newly created client in the popped up window and copying/pasting generated certificate to a local file accessible from this installer.Have you enabled per-client certificate authentication on CommServe? [no]


3 - If you plan to define specific filters for the Agent.

Press Enter.

25. Type the appropriate number to select the Client Group and press Enter.


27. Press Enter.

If you do not have Storage Policy created, this message will be displayed. You may not be prompted for user input. You can create the Storage Policy later in step 27.




Disk Library Creation:




Selecting How to Set Commcell Level Global FiltersCommcell 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. Please select how to set the Global Filters for the default subclient?1) Use Cell level policy2) Always use Global filters3) Do not use Global filtersYour Choice: [1]

This screen will be displayed only if Client Groups are configured for the CommCell.

Selecting Client Computer GroupsClient Group(s) is currently configured on CommServe mycommserve.company.com. Please choose the group(s) that you want to add this client myclient.company.com to.[ ] 1) Client Grp1[a=all n=none r=reverse q=quit d=done >=next <=previous ?=help]Enter number(s)/one of "a,n,r,q,d,>,<,?" here: 1

Selecting Client Computer GroupsClient Group(s) is currently configured on CommServe mycommserve.company.com. Please choose the group(s) that you want to add this client myclient.company.com to.[X] 1) Client Grp1[a=all n=none r=reverse q=quit d=done >=next <=previous ?=help]Enter number(s)/one of "a,n,r,q,d,>,<,?" here: d

Deciding if to Configure Storage PolicyWould you like to configure Storage Policy on this client?Configure? [no]

Adjusting modes and permissions of files...done.Starting Data Protection Suite services...done.Thank you for choosing Data Protection Suite.

There seem to be no Storage Policies configured on the CommServe. Before you can run any backups of this IDA, you will need to install a MediaAgent, create a Storage Policy and assign it to all subclients..













Click OK.



















Create a Custom Package

Use the following steps to create a custom package for Unix components.


2. If you are installing the software from the Software Installation Discs, run the following command to mount the CD:

Run the following command from the Software Installation Package or mount point:


Press Enter.


5. Type 2 and press Enter.

6. Press Enter to create a Custom install package.

7. Press Enter.

8. Type the number associated with the platform for which you want to create the custom package, and press Enter.

Method 2: Custom Package


./cvpkgadd

You can also run this command as a SUDO user with root privileges:

For steps to add a SUDO user to /etc/sudoers, see Frequently Asked Questions - Install.

./sudo cvpkgadd

Selecting Unix Setup TaskPlease select a setup task you want to perform from the list below:Advanced options provide extra setup features such as creating custom package,recording/replaying user selections and installing External Data Connector software.1) Install data protection agents on this computer2) Advanced options3) Exit this menuYour Choice: [1] 2

Selecting Unix Setup Advanced OptionsPlease select a setup task you want to perform from the list below:[Custom Package Creator]1) Create a custom install package[ De-coupled Installer ]2) Pre-install software Components (De-coupled Mode)3) Exit this menu

Your Choice: [1]

Selecting Package TypeBesides general package, you may choose to create one additional native package from the list below.Please make sure to allow write permission to /opt if you choose to create native package(except Mac package)1) General package only2) Please also create RPM3) Please also create solaris native package4) Please also create hpux native package5) Please also create Mac package using PackageMaker6) Please also create APT7) ExitYour Choice: [1]

Do not select more than one platform.


9. Type d for done, and then press Enter.

10. Type the number associated with component (s) that you want to include in the custom package, and press Enter.

11. Type d for done and then press Enter.

Selecting PlatformPlease choose one or more platforms to package from the list below.[ ] 1) Linux X86[ ] 2) Linux X86_64[ ] 3) Linux PPC64[ ] 4) Linux S390[ ] 5) Solaris10 SPARC[ ] 6) Solaris10 X86_64[ ] 7) Aix PPC[ ] 8) HP-UX IA64[ ] 9) Darwin X86[ ] 10) FreeBSD7 X86[ ] 11) FreeBSD7 X86_64[a=all n=none r=reverse q=quit d=done >=next <=previous ?=help]Enter number(s)/one of "a,n,r,q,d,>,<,?" here: 2

Selecting PlatformPlease choose one or more platforms to package from the list below.[ ] 1) Linux X86[X] 2) Linux X86_64[ ] 3) Linux PPC64[ ] 4) Linux S390[ ] 5) Solaris10 SPARC[ ] 6) Solaris10 X86_64[ ] 7) Aix PPC[ ] 8) HP-UX IA64[ ] 9) Darwin X86[ ] 10) FreeBSD7 X86[ ] 11) FreeBSD7 X86_64

[a=all n=none r=reverse q=quit d=done >=next <=previous ?=help]Enter number(s)/one of "a,n,r,q,d,>,<,?" here: d

Selecting Subsystem

Please choose one or more subsystems to package from the list below.

[ ] 1) File System Core [1002] [CVGxBase][ ] 2) File System [1101] [CVGxIDA][ ] 3) MediaAgent [1301] [CVGxMA][ ] 4) Documentum iDataAgent [1126] [CVGxDctmIDA][ ] 5) Oracle iDataAgent [1204] [CVGxOrIDA][ ] 6) SAP for Oracle [1205] [CVGxOrSAP][ ] 7) SAP for MaxDB [1206] [CVGxSAPMAXDB][ ] 8) Informix iDataAgent [1201] [CVGxIfIDA][ ] 9) Sybase iDataAgent [1202] [CVGxSybIDA][ ] 10) DB2 iDataAgent [1207] [CVGxDB2][ ] 11) MySQL iDataAgent [1208] [CVGxMySQL][ ] 12) PostgreSQL iDataAgent [1209] [CVGxPostGres][ ] 13) Lotus Notes Database iDataAgent [1051] [CVGxLndbIDA]>) >>>>>>>>>>>> NEXT PAGE >>>>>>>>>>>>

[a=all n=none r=reverse q=quit d=done >=next <=previous ?=help]Enter number(s)/one of "a,n,r,q,d,>,<,?" here: 5

Selecting Subsystem

Please choose one or more subsystems to package from the list below.

[ ] 1) File System Core [CVGxBase][ ] 2) File System [1101] [CVGxIDA][ ] 3) MediaAgent [1301] [CVGxMA][ ] 4) Documentum iDataAgent [1126] [CVGxDctmIDA][x] 5) Oracle iDataAgent [1204] [CVGxOrIDA][ ] 6) SAP for Oracle [1205] [CVGxOrSAP][ ] 7) SAP for MaxDB [1206] [CVGxSAPMAXDB]


12. Press Enter to save the Custom Package to the default path. If you want to specify a different location, type the path and then press Enter.

13. Type Yes and press Enter.

14. Press Enter.

Press Enter to hide the above option during install.

15. Verify the default path for software installation. Custom Package will be installed to this location.

Press Enter.




!@#$%^&*():/?\


[ ] 8) Informix iDataAgent [1201] [CVGxIfIDA][ ] 9) Sybase iDataAgent [1202] [CVGxSybIDA][ ] 10) DB2 iDataAgent [1207] [CVGxDB2][ ] 11) MySQL iDataAgent [1208] [CVGxMySQL][ ] 12) PostgreSQL iDataAgent [1209] [CVGxPostGres][ ] 13) Lotus Notes Database iDataAgent [1051] [CVGxLndbIDA]>) >>>>>>>>>>>> NEXT PAGE >>>>>>>>>>>>


Setting Custom Package Directory

Please enter the directory name for saving the custom package to.

Save custom package to: [/opt]

Deciding If to Record the Install

Optionally, you may choose to record install to an xml parameter file now so that you can play it later. The recorded xml will be encapsulated into thecustom package and can be used as an answer file in two ways:(1) from the custom package run "cvpkgadd" or "silent_install -p default";(2) from the native package run native installer(rpm/pkgadd/swinstall...)

You can still perform the above two tasks without custom recording if you choose to use all default parameters.

Do you want to record the install now? [no] yes

Deciding If to Install Agents for Restore Only

Do you want to install the agents for restore only without consuming licenses?

Install Agents for Restore Only? [no]

Hide this screen? [yes]

Please specify where you want us to install binaries.

It must be a local directory and there should be at least 680MB of free spaceavailable. All files will be installed in a "hds" subdirectory, so if youenter "/opt", the files will actually be placed into "/opt/hds".

Installation Directory: /opt


Press Enter to hide the above option during custom package install.

16. Verify the default path for log files. While installing the Custom Package, the log files will be saved to this location.

Press Enter.



!@#$%^&*():/?\




17. Verify the default path for JobResults Directory and press Enter.



Press Enter again.


Preparing Log Directory

Please specify where you want to keep Data Protection Suite log files.

It must be a local directory and there should be at least 100MB of free spaceavailable. All log files will be created in a "hds/Log_Files"subdirectory, so if you enter "/var/log", the logs will actually be placedinto "/var/log/hds/Log_Files".

Log Directory: /Log_Files


Preparing Job Results Directory

Please specify the name for the JobResults directory.

It must be a local directory and there should be at least 20MB of free spaceavailable. It will be used to store intermediate data that should be passedfrom one backup phase to another.

JobResults Directory: /opt/jbrdir


Deciding If to Use a Unix Group

Most of Data Protection Suite processes run with root privileges, but some are launched bydatabases and inherit database access rights. To make sure that registry andlog files can be written to by both kinds of processes we can either make suchfiles world-writeable or we can grant write access only to processes belongingto 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 inthe next setup screen. If you choose not to assign a dedicated group toData Protection Suite processes, you will need to specify the access permissions later.


If you do not want the above screen to be displayed at the time of installation of this Custom Package, press Enter.

19. Type the UNIX group and press Enter.

Make sure that the group you specified above exists on the computer on which you would install this custom package.


20. Press Enter.

21. Press Enter.

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]


Setting Unix GroupPlease 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 "Data Protection Suite" group.However, if you're planning to use Oracle iDataAgent or SAP Agent, you should enter Oracle's "dba" group here.Group name: dba


Setting Unix GroupPlease 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 "Data Protection Suite" group.However, if you're planning to use Oracle iDataAgent or SAP Agent, you should enter Oracle's "dba" group here.Group name: galaxyREMINDERIf you are planning to install Data Protection Suite Informix, DB2, Sybase or LotusNotes iDataAgent, please make sure to include informix, db2, etc. users into group "galaxy"..Press <ENTER> to continue...

Setting Access Permissions for Group and Other Users

Installer will assign full access rights to root user for all installedData Protection Suite files and its processes.

For group and any other users, you can specify the access permissions now.

If you did not assign a dedicated group in previous step, make sure youspecify sufficient access rights here if you are also planning to installData Protection Suite agents involving third party software protection.

[X] 1) Allow read permission to group users[X] 2) Allow write permission to group users[X] 3) Allow execute permission to group users[X] 4) Allow read permission to other users[X] 5) Allow write permission to other users[X] 6) Allow execute permission to other users





Press Enter.


23. Press Enter.









\|`~!@#$%^&*()+=<>/?,[]{}:;'"


Setting Instance Port Number of cvd

Every instance of Data Protection Suite should use a unique set of network ports to avoidinterfering with other instances running on the same machine.The port numbers selected must be from the reserved port number range and havenot been registered by another application on this machine.

Please enter the port numbers.

Port Number for CVD : 8400


Setting Instance Port Number of EvMgrC

Every instance of Data Protection Suite should use a unique set of network ports to avoidinterfering with other instances running on the same machine.The port numbers selected must be from the reserved port number range and havenot been registered by another application on this machine.

Please enter the port numbers.

Port Number for CVD : 8400

Port Number for EvMgrC: 8402


Deciding If to Configure Firewall

You need to configure firewall settings if there is a firewall between thisclient and the CommServe.

Is there a firewall between this client and the CommServe? [no]




26. Press Enter.

If you want to record the install as decupled install, type yes and then press Enter.


27. Press Enter.

If CommCell authentication is enabled, you might need to provide the CommCell credentials in order to continue with the installation.

To specify the CommCell credentials, type y, press Enter and then specify the CommCell credentials.




29. Press Enter.

Setting CommServe Host Name

Please specify hostname of the CommServe below. Make sure the hostname isfully qualified, resolvable by the name services configured on this machine.

CommServe Host Name: cserve.idclab.loc


Deciding If to Record as Decoupled Install

You may choose to create a package that will not register to CommServe duringinstall.

Do you want to record the install as decoupled install? [no]


Deciding If to Use CommCell Authentication

If CommCell client authentication is enabled, you must enter a valid usernameand password in order to register this client to the CommCell.

Do you want to enter CommCell username and password? [no]



Setting Client Computer Group

Please enter one Client Computer Group name for this client to join.

Client Computer Group Name: CCGroup_01


Setting Storage Policy

Please enter a storage policy name for this IDA.

Storage Policy Name: Storage_policy_01



30. Type 11 and then press Enter.

If you want to install the components to a different instance, type the number associated with the instance and then press Enter.


31. Type yes and press Enter.


32. Press Enter

Make a note of the locations at which the Packages are created.

Install Using the Custom Package

Use the following procedure to install using the custom package self extracting file.


If you do not have root access, acquire the root access credentials from the system administrator.

2. Navigate to the location specified during Custom Package creation.

For example:


Please select which instance you want to install/replay for this recording:

1) Always install to Instance0012) Always install to Instance0023) Always install to Instance0034) Always install to Instance0045) Always install to Instance0056) Always install to Instance0067) Always install to Instance0078) Always install to Instance0089) Always install to Instance00910) Always install to Instance01011) Always install to a new instance12) I want to specify another instance

Your Choice: [11]


ArchivingOptionally, you may choose to tar the custom package in a tar file now.Do you want to create the tar file now? [no] yes


***IMPORTANT*** You were using default tar on this machine to make thearchiving. Make sure you use the same/compatible tar to unzip the archive onthe target machine.Press <ENTER> to continue ...

[Custom Regular Package Summary] General package created at/opt/UnixCustomPackage/pkg[Custom Native Package Summary] Tar package created at/opt/UnixCustomPackage/tar

/opt/UnixCustomPackage/pkg


3. Run ./silent_install -p default. For example:

Decoupled Install

Install the software first and later register the client in the CommCell.

Remote Install


Installing Restore Only Agents

Setup a client in the CommCell for restore purposes.

Silent Install

Deploy the software silently on multiple clients.

<client_computer>/opt/UnixCustomPackage# ./silent_install -p default

Performing non-interactive Install of the following modules...* Base Client [1002] [CVGxBase]* Base0 Client [1003] [CVGxBase0]* UNIX File System iDataAgent [1101] [CVGxIDA]* Oracle iDataAgent [1204] [CVGxOrIDA]Install of the above modules completed successfully.




SKIP THIS PAGE IF YOU ARE NOT INSTALLING THIS AGENT ON A VERITAS CLUSTER. Steps involved in installing the Oracle Agent in a Clustered environment:

1. Install the Software on Physical Nodes

2. Configure the Cluster Group Client

System Requirements


Network TCP Port Requirements

Review the Network TCP Port requirements specified in Network TCP Port Requirements.

License Requirements

Review the license requirements specified in License Requirements.



The Oracle agent must be installed on all the physical nodes that host the Cluster Group.


2. Use the following options depending upon your environment:

3. Run the following command from the Software Installation Package or mount point:


Before You Begin

Install the Software on Physical Nodes

If you do not wish to protect physical nodes with a specific agent, you can install that agent in 'restore only' mode, doing so will prevent the consumption of additional license per node. See Installing Restore Only Agentsfor more information. Alternatively, you can release license from the CommCell Console for a specific agent after installing it on the physical nodes. Refer to Releasing a License section to see the procedure for releasing a license.

The software can be installed on the Physical nodes using one of the following methods:


Use this procedure to Install the software on the physical nodes from the active node of a cluster group.


Repeat the following steps on each of the physical nodes that host the Cluster Group.

Mount the Software Installation Discs on a global zone or a Unix machine using the following command:

Mount the Software Installation Discs on the non-global zone using the following commands:

Connect to the non-global zone terminal.


mkdir <Non-Global Zone root location>/<Non-Global Zone local directory>

mount –F lofs <Global zone software Install Disc mount point> <Non-Global Zone root location>/<Non-Global Zone local directory>



Press Enter.


6. Press Enter.

7. If your computer is 32-bit, or if you want to install 32-bit binaries on 64-bit computer, press Enter.

If your computer is 64-bit, and want to install 64-bit binaries, type 2, and then press Enter.

8. The default network interface name of the client computer is displayed if the computer has only one network interface (NIC card), press Enter to accept.

If the computer has multiple network interfaces, enter the interface name that is preferred for communication with the CommServe, and then press Enter.

9. The local name of the client computer is displayed, press Enter to accept.

If necessary you can also enter a new (friendly) name for the client, and then press Enter. This name will be used in the CommCell and will also be displayed in the CommCell Console.


10. Type the number associated with the Oracle iDataAgent and press Enter.

./cvpkgadd

Selecting Unix Setup TaskPlease select a setup task you want to perform from the list below:Advanced options provide extra setup features such as creating custom package, recording/replaying user selections and installing External Data Connector software.1) Install data protection agents on this computer2) Advanced options3) Exit this menuYour choice: [1]

This prompt is displayed only when you are installing on AIX, HP-UX, or Solaris computers. You can determine this by verifying whether all the components that you wish to install in this computer are supported in 64-bit in System RequirementsNote that when the first component is installed using 64-bit binaries, you cannot subsequently install another component using 32-bit. (Or vice-versa.)

32 or 64?This machine supports both 32 bit and 64 bit binaries. By default, we will install 32 bit binary set that has full support for all the modules included in this package. Please note that 64 bit binary set currently only support limited modules.1) All platforms(32 bit)2) FS and MA only(64 bit)Your choice: [1]

The interface names and IP addresses depend on the computer in which the software is installed and may be different from the example shown.

Setting Client/Physical Machine Host NameWe found one network interface available on your machine. We will associate it with the client being installed, and it will also be used by the CommServe to connect to the client. 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 check the interface name below, and make corrections if necessary:Client/Physical Machine Host Name: [myclient.company.com]

Setting Client NamePlease 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.Physical Machine Client name: [myclient]



12. Press Enter.

13. Press Enter.

14. Verify the default path for software installation.

Press Enter.




!@#$%^&*():/?\


Selecting Modules to Install.[ ] 1) UNIX File System iDataAgent [1101] [CVGxIDA][ ] 2) MediaAgent [1301] [CVGxMA][ ] 3) ProxyHost iDataAgent [1102] [CVGxProxyIDA][ ] 4) Documentum iDataAgent [1126] [CVGxDctmIDA][ ] 5) Oracle iDataAgent [1204] [CVGxOrIDA][ ] 6) SAP for Oracle [1205] [CVGxOrSAP][ ] 7) SAP for MaxDB [1206] [CVGxSAPMAXDB][ ] 8) Informix iDataAgent [1201] [CVGxIfIDA][ ] 9) Sybase iDataAgent [1202] [CVGxSybIDA][ ] 10) DB2 iDataAgent [1207] [CVGxDB2][ ] 11) MySQL iDataAgent [1208] [CVGxMySQL][ ] 12) PostGres iDataAgent [1209] [CVGxPostGres][ ] 13) Lotus Notes Database iDataAgent [1051] [CVGxLndbIDA]>) >>>>>>>>>>>> NEXT PAGE >>>>>>>>>>>>[a=all n=none r=reverse q=quit d=done >=next <=previous ?=help]Enter number(s)/one of "a,n,r,q,d,>,<,?" here: 5

Selecting Modules to Install.[ ] 1) UNIX File System iDataAgent [1101] [CVGxIDA][ ] 2) MediaAgent [1301] [CVGxMA][ ] 3) ProxyHost iDataAgent [1102] [CVGxProxyIDA][ ] 4) Documentum iDataAgent [1126] [CVGxDctmIDA][X] 5) Oracle iDataAgent [1204] [CVGxOrIDA][ ] 6) SAP for Oracle [1205] [CVGxOrSAP][ ] 7) SAP for MaxDB [1206] [CVGxSAPMAXDB][ ] 8) Informix iDataAgent [1201] [CVGxIfIDA][ ] 9) Sybase iDataAgent [1202] [CVGxSybIDA][ ] 10) DB2 iDataAgent [1207] [CVGxDB2][ ] 11) MySQL iDataAgent [1208] [CVGxMySQL][ ] 12) PostGres iDataAgent [1209] [CVGxPostGres][ ] 13) Lotus Notes Database iDataAgent [1051] [CVGxLndbIDA]>) >>>>>>>>>>>> NEXT PAGE >>>>>>>>>>>>[a=all n=none r=reverse q=quit d=done >=next <=previous ?=help]Enter number(s)/one of "a,n,r,q,d,>,<,?" here: d

Deciding if to Config for Laptop or Desktop BackupsDo you want to configure the iDataAgent for laptop or desktop backups?Config for Laptop or Desktop Backups? [no]

Deciding if to Install Agents for Restore OnlyDo you want to install the agents for restore only without consuming licenses?Install Agents for Restore Only? [no]

Preparing Installation DirectoryPlease specify where you want us to install Data Protection Suite binaries.It must be a local directory or NFS and there should be at least 281MB 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]


15. Verify the default path for log files.

Press Enter.



!@#$%^&*():/?\



16. Press Enter.


Press Enter again.

18. Type d for done with the selection and press Enter.

Preparing Log DirectoryPlease specify where you want to keep Data Protection Suite log files.It must be a local directory or NFS share and there should be at least 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]

Deciding If to Use a Unix GroupMost 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, you will need to specify the access permissions later.If you're planning to backup Oracle DB you should use "dba" group.Would you like to assign a specific group to Software? [yes]

Setting Unix GroupPlease 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: testgrp1REMINDERIf 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 "testgrp1"..Press <ENTER> to continue...

This screen is displayed if you do not assign any group to the software and type no in step 13.

Setting Access Permissions for Group and Other UsersInstaller will assign full access rights to root user for all installed Data Protection Suite files and its processes.For group and any other users, you can specify the access permissions now.If you did not assign a dedicated group in previous step, make sure you specify sufficient access rights for other users if you are also planning to install Data Protection Suite agents involving third party software protection.[X] 1) Allow read permission to group users[X] 2) Allow write permission to group users[X] 3) Allow execute permission to group users[X] 4) Allow read permission to other users



Press Enter.

20. Press Enter.







\|`~!@#$%^&*()+=<>/?,[]{}:;'"

23. If you have enabled per-client certificate on CommServe, type y and press Enter.

Else, press Enter.

24. Choose one of the following:

[ ] 5) Allow write permission to other users[X] 6) Allow execute permission to other users[a=all n=none r=reverse q=quit d=done >=next <=previous ?=help]Enter number(s)/one of "a,n,r,q,d,>,<,?" here: d

Setting Instance Port Number of cvdEvery 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]

Setting Instance Port Number of EvMgrCEvery 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: 8400Port Number for EvMgrC: [8402]

Deciding If to Configure FirewallYou need to configure firewall settings if there is a firewall between this client and the CommServe.Is there a firewall between this client and the CommServe? [no]

Setting CommServe Host NamePlease specify hostname of the CommServe below. Make sure the hostname is fully qualified, resolvable by the name services configured on this machine.CommServe Host Name: mycommserve.company.com

Specifying If CommServe Per-Client Certificate is EnabledIf you have checked "Force per-client certificate authentication on CommServe" on the CommServe or Proxy, you need to provide installer with a Temp Certificate.This Temp Certificate can be obtained by opening "Certificate Administration Applet" from the Java GUI's Control Panel, clicking "Temp Certificate" button, selecting newly created client in the popped up window and copying/pasting generated certificate to a local file accessible from this installer.Have you enabled per-client certificate authentication on CommServe? [no]


1 - To inherit global filter policy configuration set for the CommCell.

2 - To apply the global filters policy to the default subclient regardless of the policy set for the CommCell.

3 - If you plan to define specific filters for the Agent.

Press Enter.



27. Press Enter.

If you do not have a Storage Policy, the list will not be displayed. You can create a Storage Policy later using the steps described in the Configuring storage Policysection.

After installing the software successfully on all the physical computers that host the Cluster Group, you must configure the Cluster Group Client from the CommCell Console. Use the following steps to configure the Cluster Group Client.

1. From the CommCell Browser, right-click the Client Computers node, point to New Client | Clustered Server and then click Unix Cluster.

Selecting How to Set Commcell Level Global FiltersCommcell 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. Please select how to set the Global Filters for the default subclient?1) Use Cell level policy2) Always use Global filters3) Do not use Global filtersYour Choice: [1]


Selecting Client Computer GroupsClient Group(s) is currently configured on CommServe mycommserve.company.com. Please choose the group(s) that you want to add this client myclient.company.com to.[ ] 1) Client Grp1[a=all n=none r=reverse q=quit d=done >=next <=previous ?=help]Enter number(s)/one of "a,n,r,q,d,>,<,?" here: 1

Selecting Client Computer GroupsClient Group(s) is currently configured on CommServe mycommserve.company.com. Please choose the group(s) that you want to add this client myclient.company.com to.[X] 1) Client Grp1[a=all n=none r=reverse q=quit d=done >=next <=previous ?=help]Enter number(s)/one of "a,n,r,q,d,>,<,?" here: d

Deciding if to Configure Storage PolicyWould you like to configure Storage Policy on this client?Configure? [no]

Adjusting modes and permissions of files...done.Starting Data Protection Suite services...done.Thank you for choosing Data Protection Suite.

There seem to be no Storage Policies configured on the CommServe. Before you can run any backups of this IDA, you will need to install a MediaAgent, create a Storage Policy and assign it to all subclients..

Configure the Cluster Group Client


2. In the Client Name box, type a name for the cluster group. The Client name can be any unique name.

In the Host Name box, you can type either the fully qualified domain name of the Cluster Group or the IP address of the Cluster Group.

3. Review the cluster group information and click Finish.

Advanced Client Properties window is displayed now.

4. On the Advanced Client Properties dialog box, click the Cluster Group Configuration tab. All the Linux clients that are available in the CommCell will be listed in the Available list. Select the physical computers (nodes) where you installed the necessary Agents from the Available list, and then click Add > to move the client to the Selected list.

The Host name of the Cluster Group client should not be used by any existing client in your CommCell. If you want to specify the IP address of the Cluster Group, ensure that the IP address is static.

If the client computer properties dialog box is not displayed automatically, then you need to open it manually: Right-click the <Cluster Group Client>, and then click Properties. Click Advanced on the Client Computer Properties dialog box. Click the Cluster Group Configuration tab on the Advanced Client Properties dialog box.


5. Click the Agents tab.

Select the Agents you want to use in the cluster group client from the Available list and click Add > to move the Agent to the Selected list.

6. Click the Job Configuration tab.

Type or click Browse to specify the path for the Job Results Directory in the cluster group client.

Click OK.

In order to configure a Cluster Group Client, the agents should be installed on all the clustered nodes for proper failover. If an Agent is not installed on all the nodes, then the Agents selection tab on the Advanced Client Properties window will display the Agent name in plain text (not in bold). However, you can still configure the Cluster Group Client even when the Agents are not installed on a particular node; installation can be done later using Remote install procedure.

Ensure that the Job Results Directory resides on a shared clustered drive. In the case of MediaAgent and ContinuousDataReplicator, the Job Result directory path will be used for the Index Cache and CDR Log directories respectively if no directory location is provided.


7. Click OK.

The cluster group client is successfully created.

If you do not have a Storage Policy created, use the following steps to create a storage policy:

To create a storage policy, you must have configured a library in the CommCell.
















Configuring Storage Policy


Click OK.
















Remote Install





Once the Oracle iDataAgent is installed, do the following:

1. From the CommCell Browser, navigate to Security.

2. Right-click CommCell Users and click New User.

3. In the User Name box, enter the name of the new user account.

In the Password box, enter the new password for the user account. Re-enter the password in the Confirm Password box.

In the Full Name box, enter the full name of the user.

In the E-Mail box, enter the email of the user.

Click OK.

4. From the CommCell Browser, navigate to Security.

5. Right-click the CommCell User Groups and select New User Group.

6. Type the user group name in Name box.

Type a description on the user group in Description box.


Setup Permissions for Oracle Database Administrator


7. Click the Capabilities tab.

Select Agent Management, Data Protection/Management Operations, In Place Recover, and Out of Place Recover capabilities.

Click > to move the selected capabilities to the Assigned Capabilities list box.

8. Click the Users tab.

Select the user from Available Users list and move to Member Users.


9. Click the Associated Entities tab.

Expand the Client Computers node and select the client computers that you want to associate to this user group.

Click OK.


Right-click Storage Policies and click New Storage Policy.

Create Storage Policy with Infinite Retention


2. Click Next.

3. Type the Storage Policy name in the Storage Policy Name box and click Next.

4. From the Library list, select the name of a library and click Next.


5. From the MediaAgent list, select the name of a MediaAgent that will be used to create the primary copy.

Click Next.

6. Click Next to accept default values.

If necessary these values can be modified later.

7. By default, Yes check box is selected, which enables (MediaAgent side) deduplication on primary copy.

Clear Enable Client Side Deduplication option and then click Next.


8. By default, name for deduplication database is displayed in Name box.

Under DDB Location, perform the following:

From the MediaAgent list, click the name of the MediaAgent that will be used to host the deduplication database.

In the Location box, type the name of the folder or Browse to the folder in which the deduplication database must be located.

Click OK.

9. Click Finish.

10. From the CommCell Browser, navigate to Policies | Storage Policies | <Storage Policy>

The deduplication database must be located in a folder and not directly under the root of a disk volume.


Right-click the storage policy copy, and click Properties.

Click the Retention tab.

Click Infinite.

By default, retention is set to 15 days and 2 cycles for all backups.

Click OK.



Prior to performing backup and restore operations, do the following:

1. Ensure that the Oracle iDataAgent is installed on the client computer with Oracle group permissions.

2. Acquire the following from the backup administrator:

CommCell login credentials

Storage Policy name for database backups

3. Review the following RMAN parameters and verify if they are required in your environment.

SBT_LIBRARY

Specify the SBT_LIBRARY parameter to direct to the Oracle iDataAgent's SBT library during channel allocation and configuration.

CvClientName

This parameter is optional if Oracle instance is running on a physical machine. This parameter is mandatory when Oracle Instance is running on a virtual machine in clustered environment.

RMAN Retention

Make sure retention rules set for the Storage Policy copy and RMAN retention policy setting are in sync. If you want to retain the data using RMAN retention policy settings, it is recommended to configure the retention rules to infinite. So, the data will be obsoleted and aged using RMAN retention policy.

Number of channels in RMAN script

Each allocate channel command in RMAN script gets translated into backup stream in media manager. Allocate optimum number of channels for resource usage and to meet the backup window requirements.

RMAN block size

Specify the block size for backup and restore to be used in allocate channel PARMS. If this parameter is not passed, RMAN will use the default block size value for backup and restores.

Oracle database administrator can use Oracle RMAN scripts to backup their data using multi-stream backups. RMAN scripts can contain FILESPERSET and BLOCK SIZE parameters to optimize their backup usage. It is recommended to use FILESPERSET as 4 so that the Oracle backups will create identical backup images across the backups, resulting in greater Deduplication ratio. We also recommend to set the block size to 512K for better performance.

Prerequisites Configuration Backup Restore

Planning your Backup and Restore

If you do not wish to pass the SBT_LIBRARY parameter in RMAN script, create a symbolic link $ORACLE_HOME/lib/libobk.so to point to the Oracle iDataAgent's SBT library. You can run <software_install_path>/iDataAgent/Ora_install.sh script to create the libobk.so link under $ORACLE_HOME/lib directory. For instructions to run the Ora_install.sh script, see Relinking SBT Library.



Configuring an Instance

Relinking SBT Library

Enabling Backups From Oracle Enterprise Manager

Viewing Job Details

Viewing Job Summary Report

Viewing RMAN Backup Pieces

Use the qcreate instance qcommand to create a new instance for the Oracle iDataAgent.

Description

This command creates a new instance under the given agent.

Creating an On Demand instance does not require additional options as all options specified for the Oracle iDataAgent are accepted per their default value. If you need to create an Oracle instance for a Unix client, you must use the qcreate instance command with an input file. This is because "/" is an argument separator in Windows and hence cannot be used for paths.

Upon successful completion, this command displays the message "Created instance successfully" on the command prompt. In case of an error, an error code and description are displayed as: "Instance: Error errorcode: errordescription".

Usage

Options

Argument Files


Table of Contents

Configuring an Instance

qcreate instance -c client -a iDataAgent -n instance -dsp defaultstoragepolicy -csp cmdlinestoragepolicy -lsp logstoragepolicy [-hu Host User Windows|Unix)] [-ntu ntuser] [-ntp ntpas sword] [-oh oracleHome] [-ocu connectUser] [-ocp connectPassword] [-ocs connectService] [-ct usecatalog] [-ctu catalogUser] [-ctp catalogPassword] [-cts catalogService] [-tf tokenfile] [-tk token] [-af argsfile] [-h]

-c Client computer name -a Agent type installed on client computer (see Argument Values - Agent Types)-n Name of the instance to be created -dsp Default storage policy name-csp Command line storage policy name-lsp Log storage policy name-ntu NT User Name-hu Host User Name-ntp NT Password (in plain text)-oh Oracle Home path-ocu Connect User-ocp Connect Password-ocs Connect Service-ct Use Catalog (yes | no)-ctu Catalog User-ctp Catalog Password-cts Catalog Service-tf Reads token from a file-tk Token string-af Reads arguments from a file -h Displays help

client Client computer namedataagent Agent type installed on client computer (see Argument Values - Agent Types)instance Instance name as reflected in the agentdefaultsp Default storage policy namelogsp Log storage policy namecmdlinesp Command line storage policy namentuser NT - User Name


Diagnostics

Possible exit status values are:

0 - Successful completion.

1 - CLI usage failures, due to the use of an unsupported option or missing argument.

2 - Any other failure.

Example

Create an instance with name ins1 under client client1 and Agent Q_ORACLE.

Use the following steps to synchronize the Oracle iDataAgent SBT library with the Oracle library:

1. Navigate to the software install folder/iDataAgent directory and run the Ora_install.sh file as root user.

2. Type the Oracle user ID and press Enter.

3. Type the user group and press Enter.

4. Type the Oracle home directory and press Enter.

5. Type the home directory of Oracle user and press Enter.

6. Type n and press Enter.

7. Verify the SBT library under specified Oracle_HOME/lib directory.

ntpassword NT - Passwordoraclehome Oracle Homeoracleconnectuser Oracle Connect Useroracleconnectpassword Oracle Connect Passwordoracleconnectservice Oracle Connect Serviceusecatalog Use Catalog (yes | no)cataloguser Catalog connect string, user namecatalogpassword Catalog connect string, passwordcatalogservice Catalog connect string, service nametns TNS Admin Folderblocksize Block size (>0)logstreamcount Log Stream Count (>0)compressionat Compression at (CLIENT | MA)networkbandwidth Network Bandwidth

qcreate instance -c client1 -a Q_ORACLE -n ins1 -dsp ora_data -csp ora_test -lsp ora_test -hu oracle -oh /oracle/oracle10g -ocu sys -ocp sys -ocs dctmdb -ct yes -ctu snap -ctp snap -cts test

Relinking SBT Library

[root@dbserve22 iDataAgent]# ./Ora_install.sh

Please enter ORACLE_USER ID: oracle

Please enter user group for oracle [dba]: oinstall

Please enter ORACLE_HOME directory: /home/oracle/app/oracle/product/11.2.0/dbhome_1

Please enter the home directory of user oracle [~oracle]: /home/oracle

Would you like to relink Simpana with different ORACLE_HOME now(y/[n])?n

ls -l /home/oracle/app/oracle/product/11.2.0/dbhome_1/lib/libobk.solrwxrwxrwx 1 root root 27 May 29 13:02 libobk.so -


If you are using the Oracle Enterprise Manager to schedule the backups and restore operations, set the iDataAgent's SBT library in the Oracle Enterprise Manager (OEM) using the following steps:

Oracle recommends doing periodic full, regular incremental and logs backup operations. The command line backup and restore operations can be scheduled using third-party tools like Control-M or cron.

1. Login to Oracle Enterprise Manager.

2. Click the Availability tab.

3. Under Media Management Setting group, type the following command in the Media Management Vendor Library Parameters box.

The SBT_LIBRARY path for the various platforms are listed below:

AIX with 64 bit Oracle - <Client Agent Install Path>/Base64/libobk.a(shr.o)HP UX PA RISC 64 bit Oracle - <Client Agent Install Path>/Base64/libobk.slSolaris with 64 bit Oracle -<Client Agent Install Path>/Base64/libobk.soLinux on System Z with 64 bit Oracle - <Client Agent Install Path>/Base64/libobk.soAll Other Unix platforms -<Client Agent Install Path>/Base/libobk.so

4. Click OK.

Use the qlist job qcommand to view job details.

Description

This command displays the job details of a given job ID, or of all the active jobs under a client, agent, instance backup set or subclient. The command displays job details such as job ID, type, phase, status, failure reason, and user-defined description.

When a job ID is specified, its details are displayed irrespective of the job status. When no option is specified in the command, it displays all active jobs in the CommServe. Only active jobs are displayed when you query jobs based on client, agent, instance, backup set, or subclient.

Additionally, you can filter the jobs based on the job type or status. Only those jobs with the specified type/status are displayed in the command prompt. When more than one job is found, the jobs are listed one job per line, and are displayed in the command prompt. The system displays a message "No jobs to display" when there are no jobs.

In case of an error, an error code and the error description are displayed in the following format: "job: Error errorcode: errordescription"

Usage

> /opt/hds/Base/libobk.so

Enabling Backups From Oracle Enterprise Manager

SBT_LIBRARY=<software_install_path>/Base/libobk.so,BLKSIZE=262144, ENV=(CvClientName=<client_name>, CvInstanceName=<instance_name>)"

[CvClientName] [CvClientName]

<Client_Name>

Example:

[CvClientName]=client_name

Name of the client defined in the CommCell Console.

[CvInstanceName] [CvInstanceName]

<Instance_Name>

Example:

[CvInstanceName]=instance_name

Name of the Data Protection Suite instance installed

This parameter is optional.

In cases of multiple instances of the software, the first installeinstance would be 'Instance001')

Viewing Job Details

qlist job [-co <i|o|s|p|r|d|c>] [-j <jobid>] [-jt <jobtype>] [-js <Running|Suspended|Waiting|Pending>] [-c <client>] [-a <iDataAgent Type>] [-i <instance>] [-b <backupset>] [-s <subclient>] [-tf <tokenfile>] [-tk <token>] [-h]

Use the [-jt <jobtype>] option to specify the job operation that you want to display. This will prevent


Column Codes

The column codes represent the job details that you want to display for a job. These columns can be specified using the -co option to filter the columns displayed by the qlist job command. The following are the available column codes:

By default, all column codes are enabled, except the r column.

Options

Diagnostics





Example

Use the qoperation report qcommand to view the job summary report.

Description

This command generates a job summary report. Reports can be saved as a file in HTML/text formats.

The qoperation report command also allows you to filter the report output by job type, backup type, job status, client, agent, start times, and end times. When no filters are specified, the report is generated for all job types (backup, restore, and administration) for the last 24 hours.

This command provides several options worth noting:

You can run a backup report for a specific job by using the [-j jobid] option. Whenever you issue the command with this option, a job report will be generated only for the specified job.

You can run a report that includes jobs that were not run by setting the -js (job status) parameter to norun.

displaying other job operations, such as administration jobs.

i Job IDo Job Types Job Statusp Job Phaser Failure/Pending Reasond Job Descriptionc Job Progress (percentage of completion)

-co Columns to display. See the Column Codes table above.-j Job ID-jt Filters the jobs by type. Valid values are:

Backup Restore

-js Filters the jobs by status. Valid values are: Running Suspended Waiting Pending

-c Client computer name-a iDataAgent type installed on client computer (see Argument Values - Agent Types).-i Instance name-b Backup set name-s Subclient name-tf Reads token from a file-tk Token string-h Displays help

When you run the qlist job command with no options specified (to display all the active jobs), any description that the user specified for the job is partially displayed. Similarly, a partial description is displayed if you run the command for a specific job along with the -co option (including the d value), for example qlist job -j jobid -co iod.

To display the entire user-defined description for a specific job, you must run the following command: qlist job -j jobid -co d.

qlist job -c dbserve41 -a Q_ORACLE

Viewing Job Summary Report


Upon successful completion, the command displays the message "Report generated successfully" on the command prompt. In case of an error, an error code and description are displayed as: Error errorcode: errordescription

Usage

Options

Argument File

qoperation report -rt reporttype [-jt jobtype] [-t backuptype] [-c client] [-cg clientgroup][-a iDataAgent] [-js job status] [-st Start time] [-et endtime] [-lh lasthours] [-dpath destinationpath] [-opfrmt reportformat] [-j jobid] [-af argsfile] [-tf tokenfile] [-tk token] [-h]

-rt [string] Type of Report to be generated (jobsummary)-jt [string] Type of job. Valid values are:

backup restore admin

-t [string] Type of backup. Valid values are: Q_FULL Q_INC Q_DIFF Q_SYNTH

-c [list] Client computer name(s)-cg [list] Client computer group name(s)-a [list] Agent type installed on client computer (see Argument Values - Agent Types)-js [string] Job status. Valid job states are:

completed failed killed partsuc unning delayed nobackup norun

-st [time] Start time. The time must be entered in the following format: mm/dd/yyyy hh:mm[:ss] or yyyy/mm/dd hh:mm[:ss]. -et [time] End time. The time must be entered in the following format: mm/dd/yyyy hh:mm[:ss] or yyyy/mm/dd hh:mm[:ss]. -lh [int] Last hours-dpath [string] Destination path where the report needs to be saved (supports both local paths, and UNC paths)-opfrmt [string] Format of report to be saved. Valid formats are .html and .text files.-af [string] Reads arguments from a file-j [int] Job ID-tf Reads token from a file-tk Token string-h [nil] Displays help

client [list] Client computer name(s) clientgroup [list] Client computer group name(s)jobtype [string] Type of job. Valid values are:

backup restore admin

backuptype [string] Type of backup. Valid values are: Q_FULL Q_INC Q_DIFF Q_SYNTH

dataagent [list] Agent type installed on client computer (see Argument Values - Agent Types)diagtype [list] Type of diagnostic for the job. Valid values are:

freason jobattempts assoevents

contenttype [string] Content type. Valid values are: scf protobj failobj cifail

storagetype [string] Type of storage. Valid values are: media


Diagnostics





Example

Generate a job summary report and save it to e:\targetdir.

We have a getbackuplist utility which lists the RMAN backup pieces for a backup job. You can execute the following commands to query the backup job history and find the list of all the RMAN backup pieces from any client where the iDataAgent is installed:

1. Execute the following command to query the backup job history and identify the job id :

2. Execute the following command to view the list of all the RMAN backup pieces from the backup job ID:

Example:

drive sp ma

jobinfo [string] Job information (jobopts|user)jobstatus [string]

Valid job states are:

completed failed killed partsuc unning delayed nobackup norun

starttime [list] Start time. The time must be entered in the following format: mm/dd/yyyy hh:mm[:ss] or yyyy/mm/dd hh:mm[:ss]. endtime [string] End time. The time must be entered in the following format: mm/dd/yyyy hh:mm[:ss] or yyyy/mm/dd hh:mm[:ss]. lasthours [int] Last hoursdestinationpath [string] Destination path where the report needs to be saved (supports only local paths, not UNC paths)outputformat [string] Format of report to be saved. Valid formats are .html and .text files.jobid [number] Backup job IDdescription [list<string> | multiline] User-defined comments regarding the job

Note the following when using [description] parameter. [description] provided with no value shows description of all the jobs based on other conditions. [description] provided with filtered value shows description for filtered job reports. If parameter is absent, description is not displayed.

qoperation report -rt jobsummary -dpath e:\targetdir -jt backup -j 10Report generated successfully

Viewing RMAN Backup Pieces

./qlist jobhistory -c <client name> -a <iDataAgent> -i <Data Protection Suite_instance> -s <subclient>

./getbackupList -jobid <job ID> -outfile <ex: /tmp/xxxx.out> -dbjob <db job>

[root@dbserve Base]# ./qlist jobhistory -c dbserve -a Q_ORACLE -i RDMDB -s defaultJOBID STATUS STORAGE POLICY SUBCLIENT INSTANCE----- ------ -------------- --------- --------6394 Completed sh default RDMDB5686 Completed sh default RDMDB

[root@dbserve Base]# ./getbackupList -jobid 6394 -outfile /tmp/oracle.out -dbjob


getBackupList succeeded[root@dbserve Base]# cat /tmp/oracle.out

DATA ----------------------------------- Archive Files List For Db Job ----------------------------------------------------------

--archFileName | fileType | createTime | archFileId| archGroupId | jobIdDATA ----------------------------------- Archive Files List For Db Job ----------------------------------------------------------

--42o3p5nh_1_1 | 1 | 1362509187 | 23055 | 35 | 639443o3p5nh_1_1 | 1 | 1362509207 | 23056 | 35 | 639444o3p5qi_1_1 | 1 | 1362509279 | 23057 | 35 | 6394c-1814427393-20130305-00 | 1 | 1362509290 | 23058 | 35 | 6394

LOGS ----------------------------------- Archive Files List For Db Job ----------------------------------------------------------

--archFileName | fileType | createTime | archFileId| archGroupId | jobIdLOGS ----------------------------------- Archive Files List For Db Job ----------------------------------------------------------

--46o3p5su_1_1 | 4 | 1362509359 | 23059 | 35 | 639447o3p5su_1_1 | 4 | 1362509380 | 23060 | 35 | 639448o3p5uc_1_1 | 4 | 1362509399 | 23061 | 35 | 6394c-1814427393-20130305-01 | 4 | 1362509408 | 23062 | 35 | 6394



Full Backups

Incremental Backups

Archive Log Backups

Backup Flash Recovery Area

Full backups provide the most comprehensive protection of data.

Backups for any client start with a full backup. The full backup becomes a baseline to which subsequent backup types are applied. For example, a full backup must be performed before an archive log backup can be initiated.

You can perform a full backup of an online or offline database. If the database is in NOARCHIVELOG mode, you should perform offline backup only.

Use the following RMAN sample script to perform full backups. You can schedule a FULL Backup using the sample RMAN script using 4 streams

Incremental backups can be performed when the database is online.

An incremental backup contains only data that is new or has changed since the last backup, regardless of the type. On average, incremental backups consume less media and use less resources than full backups.

Use the following RMAN sample script to perform incremental backups. You can schedule an Incremental backup using the sample RMAN script using 4 streams.

An archive log backup captures the archive redo logs generated during database transactions.

Archive log backups are useful when you want to recover database transactions that have been lost due to an operating system or disk failure. You can apply these archive logs to an online backup in order to recover a database. It is recommended to schedule Oracle Archive Log backup every 20 minutes on busy databases.

By default full backups include both data and archive logs. However, you can also perform separate archive log backups.

In order to perform a backup of the archive logs, the database has to be in ARCHIVELOG mode.

Use the following RMAN sample script to perform archive log backups:


Table of Contents

Full Backups

run {allocate channel ch1 type 'sbt_tape'; allocate channel ch2 type 'sbt_tape';allocate channel ch3 type 'sbt_tape'; allocate channel ch4 type 'sbt_tape'; setlimit channel ch1 maxopenfiles 8; setlimit channel ch2 maxopenfiles 8; setlimit channel ch3 maxopenfiles 8;setlimit channel ch2 maxopenfiles 8;backup incremental level = 0 filesperset = 4 database include current controlfile; }

Incremental Backups

run {allocate channel ch1 type 'sbt_tape'; allocate channel ch2 type 'sbt_tape'; setlimit channel ch1 maxopenfiles 8; setlimit channel ch2 maxopenfiles 8; backup incremental level = 1 filesperset = 4 database include current controlfile; }

Archive Log Backups

run { allocate channel ch1 type 'sbt_tape';


Use the following RMAN sample script to backup the flash recovery area. You can schedule a Flash Recovery Area backups using the sample RMAN script using 2 streams.

allocate channel ch2 type 'sbt_tape'; backup (archivelog all delete input); }

Backup Flash Recovery Area

run{allocate channel ch1 type 'sbt_tape';allocate channel ch2 type 'sbt_tape' ;backup filesperset = 32recovery area;}



Restoring the Database

Restoring the Control File

Creating a Duplicate Database

When the database is corrupted or lost, you can restore the database using the following RMAN sample script:

Use the following RMAN sample script to restore the controlfile from Auto Backup.

Use the following steps to duplicate the production database to qa2:

1. Specify DB_FILE_NAME_CONVERT init parameter to redirect data files.

2. Run the RMAN sample script:


Table of Contents

Restoring the Database

SET DBID dbid; run { allocate channel ch1 type 'sbt_tape'; allocate channel ch2 type 'sbt_tape'; restore database ;recover database; }

Restoring the Control File

SET DBID dbid; run { allocate channel ch1 type 'sbt_tape'; restore controlfile from autobackup ; }

Creating a Duplicate Database

run { allocate auxiliary channel ch1 type 'sbt_tape';allocate auxiliary channel ch2 type 'sbt_tape';DUPLICATE TARGET DATABASE TO dupdb;PFILE = /dup/oracle/dbs/initDUPDB.oraNOFILENAMECHECK; }


Data Retention - Oracle DBA

Use the following command to configure retention policy in RMAN:

where, 'n' is the number of full cycles to be retained. The older cycles will be obsoleted.

You can also generate a report of the obsolete backups using the following command.

Configuring the Retention Policy

RMAN> CONFIGURE RETENTION POLICY TO REDUNDANCY n;

RMAN> report obsolete;


Troubleshooting Backup - Oracle iDataAgent

The following section provides information on troubleshooting backups.

Backup Restore

Backup Failures

Increase in sbtio.log file size Sometimes, jobs fail due to increase in the size of sbtio.log file in the $UDUMP directory.

To resolve this, set the size limit for the sbtio.log file using the sMAXORASBTIOLOGFILESIZE registry key. Once the specified size limit is reached, the sbtio.log file gets pruned automatically.

Command Line Backup Failures Make sure if the required media resource is available and then run the backups once again. For on demand backups, you can run more than one script for an instance. However, backup jobs will fail if there are more than one instance in the argument file. For Oracle on Windows, it is recommended to avoid using a space after a comma in the argument file. A backup job will fail if you leave a space after a comma in the argument file. RMAN command line backup fails with the following error

"Unable to open lock file /opt/hds/Base/Temp/locks/.dir_lock: Permission denied"

This may occur if the unmask parameter is set as 022 in the .profile file for the Oracle instance. As a workaround, change the unmask to 000 or 002 and try the backup again.

Sometimes, the third party command line jobs may hang when you perform large backups and restores.

This happens since ClDBControlAgent updates the job manager for every 100MB data transfer and this causes the thread failure for large backups/ restores after transferring some of the data.

The following exception will be seen in the ClDBControlAgent.log:

You can set sBYTESDIFFMBS registry key <value> in MBs in OracleAgent/.properties.

This will update the job manager at every <value> in MBs specified in the key.

5710030 304 02/22 03:47:23 608119 OraAgentBase::NotifyCommServeJobContinue() -m_jobObject->setUnCompBytesToAdd(105119744) ...5710030 304 02/22 03:47:24 608119 CvThread::start_func() - Unhandled exception.5710030 405 02/22 03:47:37 608119 ClOraControlAgent::OnClientTimeout() - Got timed out while waiting for msg from client 0

Offline Backup fails when using Lights Out Script

Offline backup using lights out script fails with the following error:

RMAN error "ORA-12528 TNS listener - all appropriate instances are blocking new connectionsAs a workaround, add a reference to the database in the listener.ora file as shown in the example below:

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)))Oracle offline backup with lights out option fails when you use the default value for retry attempts for the subclient. As a workaround, increase the retry attempts by setting the Tries number value greater than or equal to 5. See Configuring Lights Out Script for Offline Backups for more details.

Time Out Failures The default time for resources to allocate streams during RMAN command line backups is 86400 seconds (i.e., 24 hours). If a backup fails due to a timeout being reached, you can configure the sALLOCATESTREAMSECS registry key to increase the waiting time period.

Backup Failures If the following line is present in the $ORACLE_HOME/sqlplus/admin/glogin.sql file, it may cause the SrvOraAgent server process on the CommServe to fail when browsing database contents or executing a backup.

set linesize 80To avoid such failures, comment out that line from the file and re-try the browse or backup operation.

Backup fails with following error:


Character conversion not supportedBy default, the iDataAgent sets the NLS_LANG environment variable to American_America.US7ASCII character set. However, if the Oracle database on the client uses a different NLS character set (eg., WE8MSWIN1252), theiDataAgent’s backup operations may fail.

In such cases, use the <oracle_SID>_NLS _LANG additional setting to set the NLS_LANG environment variable to American_America.<database_character_set> on the client computer.

Database block corruption Oracle backups fail with the following error:

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.dbfMake sure that the maximum value for database block corruptions is set for the backup. 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.

Backups fail intermittently on Linux clients

On Linux clients, if the libobk.so library fails to load, the backups may fail.

As a workaround, do the following steps:

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

This will ensure that the libobk.so library is loaded so that backups for Oracle on Linux can run successfully.Backup fails on Windows Clients Make sure that the Oracle user is part of administrator group. If the user is not part of administrator group, assign group

permissions for the user as follows:

1. From Windows Explorer, right-click Backup and Recovery folder and then select Properties.

2. Click the Security tab.

3. Select the user and click Edit.

4. Click the Allow checkbox for Full Control permission for the user, and then click OK.

5. From the Registry Editor, navigate to HKEY_LOCAL_MACHINE | SOFTWARE.

6. Right click CommVault Systems and select Permissions...

7. Select the user and click Allow checkbox for Full Control permission. Backup Fails on Red Hat Enterprise Linux 4 with oracle version 10.1.0.5 32Bit

Issue:

The backup may fail with the following error on Red Hat Enterprise Linux 4 with oracle version 10.1.0.5 32Bit as there is a known oracle issue with libunwind.so.3 file:

channel ch1: starting piece 1 at Jul 12 2013 16:46:08PID 30152, signal 6 (Aborted), address 0x75c8[bt]: (1) /lib/tls/libpthread.so.0 [0x622890][bt]: (2) /lib/ld-linux.so.2 [0x3b07a2][bt]: (3) /lib/tls/libc.so.6(gsignal+0x55) [0x3f57a5][bt]: (4) /lib/tls/libc.so.6(abort+0xe9) [0x3f7209][bt]: (5) /soft/oracle/product/db/10.1.0.5/lib/libunwind.so.3(GetCurrentFrame32+0xdc) [0xb7ffd0ce][bt]: (6) /soft/oracle/product/db/10.1.0.5/lib/libunwind.so.3(_Unwind_RaiseException+0x5b) [0xb7ffc86b][bt]: (7) ./libstdc++.so.6(__cxa_throw+0x5d) [0xb60a126d][bt]: (8) ./libCvLib.so(_ZN10CvFwDaemonC1EPKcbii+0x2ee) [0xb6207c00][bt]: (9) ./libCvLib.so(_ZN10CvFwClient7connectEPKcS1_iiiiPFvR9CQiSocketPvES4_b+0xf6f) [0xb6211acb][bt]: (10) ./libCvSession.so(_ZN9CVSession16socketConnectionEPKcS1_+0x261) [0xb72cd4f1][bt]: (11) ./libCvSession.so(_ZN9CVSession9getSocketEPKcS1_+0x135) [0xb72cddd5][bt]: (12) ./libCvSession.so(_ZN9CVSession13getConnectionEPKvPKc+0x11b) [0xb72cdf1b][bt]: (51) oracleHWRHDEV(main+0xbb) [0x82816bf]


If you are experiencing performance issues during backup, you can troubleshoot them by enabling logging of performance details in the log files. These performance counters contain information that help in resolving the performance related issues during backups.

1. Perform a client backup to determine the performance statistics. To perform a backup, see Getting Started Backup - Oracle iDataAgent for step-by-step instructions.

You can track the progress of the job from the Job Controller window of the CommCell Console.

Right-click the backup job and click Details and verify the Data Transferred on Network.

If the backup transfer rate is very slow, then kill the job by right-clicking the backup job and then click Kill.

2. View log files of backup job to verify performance counters. See View the Log Files of a Job History for step-by-step instructions.

The following are the performance counters that need to be verified in the log files:

Resolution:

Upgrade your oracle version from 10.1.x to 10.2 to avoid the backup failure on Red Hat Enterprise Linux 4.

[bt]: (52) /lib/tls/libc.so.6(__libc_start_main+0xd3) [0x3e2de3][bt]: (53) oracleHWRHDEV(ldxsto+0x1d1) [0x828157d]RMAN-00571: ===========================================================RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============RMAN-00571: ===========================================================RMAN-03009: failure of backup command on ch1 channel at 07/12/2013 16:46:33RMAN-10038: database session for channel ch1 terminated unexpectedlyRMAN> Recovery Manager complete.]3 16:46:33RMAN-10038: database session for channel ch1 terminated unexpectedlyRMAN> Recovery Manager complete.]

Log backups failure If the Oracle database is configured to save the archive logs in the Flash recovery area, and Oracle subclients having both Protect backup recovery area and Archive Delete enabled at the same time then the backup will fail.

To resolve this, there should be two different subclients, one for Protect backup recovery area and the other for Archive Delete.

Log backup fails if you select the default USE_DB_RECOVERY_FILE_DEST entry as a log destination for the backup.

To resolve this, make sure that the log destinations are included in the PFile(init<SID>.ora) or SPFile (spfile.ora) file. Also ensure that the correct log destination is selected for the backup.

Backup fails on Linux clients because of UNKNOWN Instance Status

Backups may fail on Linux clients if the Oracle instance status is shown as UNKNOWN on CommCell Console.

To resolve this issue, make sure the nproc value in /etc/security/limits.d/90-nproc.conf file is greater than 1024.

Shared Memory Error Issue:

The backup failed because the shared memory on the HP-UX PA-RISC client has not been configured per operational guidelines.

Resolution:

Add the DisableIPC_GLOBAL file in the /apps/simpana/Base directory on the client where the backup failed.

1. Stop the Data Protection Suite software.

2. Create an empty file called DisableIPC_GLOBAL in the /apps/simpana/Base directory. From the command line, enter the following:

touch /apps/simpana/Base/DisableIPC_Global3. Restart the Data Protection Suite software.

Troubleshooting Performance Issues

For example, if backup job is using 10 streams, make sure to backup atleast 200 GB of data. If you are performing backups using 5 streams, make sure to backup atleast 100 GB of data.

Total Oracle I/O TimeTime spent per SBT thread for reading the data from disk.

Total MA I/O TimeTime spent during data transfer to MediaAgent i.e., data read from the network buffer and written to the disk.


3. In the log file verify the above performance counters.

If the Total Oracle I/O Time value is more than the Total MA I/O Time value then perform the following to improve performance:

Verify Oracle application compression. If it is ON turn OFF the compression.

Verify HDPS compression. If it is ON turn OFF the compression from instance and storage policy copy level. See Setting Up Data Compression for step-by-step instructions.

Depending upon your environment, modify Data Files per BFS (value to 4 or 8) and Max Open Files. See Enhancing Backup Performance for step-by-step instructions.

If the Total Oracle I/O Time value is lesser than the Total MA I/O Time value then perform the following to improve performance:

If the write throughput of the disk is slow, run CvDiskPerf tool to measure the throughput for the disk. See Measure the Deduplication Disk Performance for more information.

If the data transfer on the network is slow or you have a low bandwidth network environment, then verify Network Throughput by running CvNetworkTestTool tool. If network throughput is low then enable nNumPipelineBuffers registry key to increase the data transfer throughput from the client. See Increasing Data Transfer Throughput From Client for more information.

Backup jobs from Oracle iDataAgent will be displayed as "Completed w/ one or more errors" in the Job History in the following cases:

When RMAN Script execution for the backup job completes with warnings.

When job is killed after backing up some data.

During offline backups, if the database cannot be opened after a backup.

If you receive an Oracle error during an Oracle backup 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.

Symptom

Offline backups are failing on Windows servers with the following error message:

Resolution

This problem can happen if the TNS configuration for this database does not have a "static" listener. Most Oracle databases since the release of 9i are now using dynamic listeners, and there could be a delay in the listener between the lights-out script starting the database, and the database finishes registering in the dynamic listener, before the CommServe tries to connect back to the database to get its status. If the database does not register quickly enough, the CommServe will fail to connect to the database using the TNS connection resulting in an unknown status and this error.

To resolve this issue, scan the ClOraAgent.log on the client for a connection error to Oracle where TNS is blocking connections.

If this is indeed the error, a directive can be added to the tnsnames.ora file which will prevent the connection from getting blocked when using a dynamic listener.

Go to the %ORACLE_HOME%\NETWORK\admin folder in the oracle server and add (UR = A) to the connect_data directive.

Completed with One or More Errors

Oracle Errors

ORA0001: Error 18:18 Oracle database is not available. The database may be down or in an unknown state

ORACLE database is not available. The database may be down or in an unknown state


Once this parameter is added, the connection should no longer be blocked, and the backup should run with no errors.

Symptom

When data aging Oracle backup jobs, by default, the RMAN Oracle crosscheck operation is initiated. During this process, a check is done to see what Oracle backup objects can be aged off the backup media, according to the CommCell Data Retention rules. A remote Oracle crosscheck operation is run on the Oracle Server against the objects identified by the CommCell's Storage Policy retention criteria as ready to be aged (marked as available to over-write).

When an Oracle backup piece is aged (marked as available to over-write) in the CommServe database, by default a RMAN command is issued to make the same backup piece 'unavailable' in the RMAN Control File (Catalog). This way the RMAN Control File is kept synchronized, so that Oracle knows which backup pieces are not available in the CommServe database.

This crosscheck operation may fail with any of the following errors:

This may be due to various issues, but the most common is that the crosscheck operation runs out of time, taking longer than the default 600 seconds (10 Minutes) set.

Often there are too many objects that need to be processed by RMAN, to get this done within this default time allotted. Sometimes network issues trigger the problem. When the crosscheck fails, the unprocessed objects that are trying to age, build up a large list in the CommServe Database, making the time required during next data aging operation even longer.

Resolution

To resolve this issue, set the cross check timeout to 1800 seconds instead of the default timeout period of 600 seconds.

1. From the CommCell Browser, navigate to Client Computers | <Client> | Oracle .

2. Right-click the <Instance>, and then click Properties.

3. Click the Details tab.

4. In the Cross Check Timeout box, set the time interval to 1800 seconds.

5. Click OK.

ORA0002: Data aging jobs complete with errors during Oracle crosscheck

Error Code 32:321: Failed to clean up database after Oracle Cross-Check.

Error Code 13:93: Failed to clean up database after Oracle cross-check due to database problem.


Symptom

Oracle backup fails with the following error message:

When you view the RMAN log file, the following entry is shown:

Resolution

When the error message indicates an error from the Media Manager Layer, it could be a media error or network error. Make sure to fix this and perform the RMAN job once again.

If you still encounter the same issue, open a case with the contracted support center and upload the following logs for troubleshooting:

All logs from the CommServe

All logs from the MediaAgent

All logs from the Client

Any running RMAN script or backup script

When sending the logs, make sure the following logs are included:

JobManger.log from CommServe (log file is normally included with a send logs job for CS)

ORASBT.log from Client (log file is normally included with a send logs job for CL)

cvd.log from MediaAgent (log file is normally included with a send logs job for MA)

Additional Information

To review the RMAN logs use the following link to review usual log locations.

Locating the RMAN logs on an Oracle iDataAgent

For RMAN script recommendations and information please review the following KB.

ORA0003: Error 18:40 RMAN Script execution failed for this job. Please check RMAN log file for job failure reason.

RMAN Script execution failed for this job. Please check RMAN log file for job failure reason.

ORA-19511: Error received from media manager layer, error text:


Running RMAN from Command Line

Oracle has released a patch titled "High SCN growth rate from ALTER DATABASE BEGIN BACKUP in 11g" under patch number 12371955.

This information is relevant to Data Protection Suite conventional Oracle backups and for IntelliSnap Oracle Online backups as the command ALTER DATABASE BEGIN BACKUP is issued when putting tablespaces into hot backup mode.

Please review the issue and apply the patch to the CommCell Oracle clients.

The Oracle link requires Support Account to access:

"Bug 12371955 Hot Backup can cause increased SCN growth rate leading to ORA-600 [2252] errors" (Modified 16-FEB-2012 Type PATCH Status PUBLISHED)

https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&doctype=PATCH&id=12371955.8

When you encounter errors during backup/restore, make sure to view the following logs for troubleshooting:

SrvOraAgent.log on the CommServe

CIOraAgent.log on the client

ORASBT.log on the client.

This log file is required if you encounter errors during data transfer from/to the MediaAgent.

<job_results_directory>/2/0/<jobid>/<backup|restore>.out for RMAN specific errors on the client.

If the information in the log files is not sufficient enough to determine the failure reason, increase the debugging level in the EventManager/.properties file and re-run thejob.

In addition, you can also view the RMAN logs from the Oracle iDataAgent. From the Job Controller window or Job History window, right click the specific job and click View RMAN Log.

The RMAN logs are stored in the job results directory as backup.out (for backup jobs) and restore.out (for restore jobs). If there is an issue with data aging, the file in the job results directory will be called crosscheck.out.

The Oracle iDataAgent logs the performance statistics in the ORASBT.log file with the following throughput information:

Backup

Restore

Use the following steps to troubleshoot allocate failure errors on Unix clients:

Install/Permission issues

Oracle user should belong to the hds group entered during the iDataAgent install. Otherwise, Oracle will not able to write to the ORASBT.log and will not be able to access the CommVault registry /etc/CommVaultRegistry. More often, customers select 'sys' group (oracle does not belong to this group and fails) at the time of iDataAgent install. Please follow the installation instructions to create hds group and reinstall the software packages on the client.

Library loading errors

Oracle backup library loading errors get logged into the temporary hook file libcvobk.log generated under /tmp folder. If this file does not exist, the Oracle user (not the root user) should create this file and run the backup again. Check this file for any library loading errors.

Create trace files:

ORA0004: Oracle bug with available patch - backup and recovery impacted

ORA0005: Log files required to troubleshoot Oracle iDataAgent related errors

ORA0006: Performance statistics for Oracle backup and restore

Oracle I/O Throughput : Amount of data read by Oracle from disk in GB /HourMediaAgent I/O Throughput : Amount of data written by the MediaAgent in GB / Hour I/O Throughput Net amount of data read from Oracle and written to the MediaAgent (i.e. amount of

data backed up) in GB / Hour

(This value includes time taken by Oracle as well as the MediaAgent.)

Oracle I/O Throughput : Amount of data written by Oracle to disk in GB / HourMediaAgent I/O Throughput : Amount of data read from the MediaAgent in GB / Hour I/O Throughput: Effective amount of data read from the MediaAgent and written by Oracle (i.e.

amount of data restored) in GB / Hour.

(This value includes time taken by Oracle as well as the MediaAgent.)

ORA0007: Debugging allocate channel failures on Unix clients


Execute the following rman command and get the latest trace files udump directory of this oracle instance. Also get the iDataAgent client logs as well.

If the issue still exist, escalate to customer support with output of above steps.

If using a Windows 32bit client, make sure to check if /3GB switch is set in the boot.ini file.

rman target userid/passwrod@instance nocatalog run { allocate channel ch1 type 'sbt_tape' trace=2 debug=2; } exit;

Back to top


Troubleshooting Restore - Oracle iDataAgent

The following section provides information on troubleshooting restores.

Backup Restore

Browse Failures

Point in time Table Browse Failures

When you have encryption enabled for the client, point in time table browse operation fails with the following error message:

Pass-phrase protection is on for client [80], but pass-phrase was not specified.Make sure that the pass phrase is exported to the MediaAgent when encryption is enabled for the client.

1. From the CommCell Browser, right-click the client and select Properties.

2. Click the Encryption tab.

3. Click Via Pass-Phrase.

4. Click Export.

5. In the Destination Computer box, select the MediaAgent.

6. In the Pass-Phrase box, type the pass-phrase used for encryption.

7. In the Re-enter Pass-Phrase box, re-type the pass-phrase to confirm.

8. Click Export.

9. Click OK.

Restore Failures

Table Restore Failures For Windows, make sure that the Oracle Services are running as Local System.

The table restores may fail with the following error message:

RMAN-05502: the target database must be mounted when issuing a DUPLICATE command.

Make sure to use connect string instead of ‘/’ when you configure an instance. For example, sys/[email protected] Restore Failures 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.

Unable to create Duplicate Database

When you create a duplicate database make sure that one of the instances use a proper connect string instead of ‘/’. For example, sys/pwd12@orcl4. This is required when you perform a duplicate database restore operation since we need to connect two instances in the same RMAN operation.If a duplicate database restore fails with error PLS-00553: character set name is not recognized; then make sure that the character sets are the same between the location from where you are running RMAN, and the location of the target database. As this is an Oracle related issue, please contact Oracle support for more information.

Unable to restart a duplicate database restore job

The Auxiliary database is remaining in mount state when a suspended restore job is resumed. As a result, the restore job is failing with the following error:

RMAN-00571: ===========================================================RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============RMAN-00571: ===========================================================RMAN-03002: failure of Duplicate Db command at XX/XX/XXXX 16:28:20RMAN-05500: the auxiliary database must be not mounted when issuing a DUPLICATE commandRMAN>

This issue may occur due to the wrong syntax value (extra Slash (/) value) after oracle home. You will receive a different status when connected to a database instance. Hence, the duplicate database restore is failing.

Make sure to remove the (extra Slash (/) value) after oracle home in the syntax under instance properties.

For example:

If the Oracle Home was set to the following under instance properties.

You must update the syntax as following:

/u01/app/oracle/product/11.2.0/dbhome/

/u01/app/oracle/product/11.2.0/dbhome

Increase in sbtio.log file size Sometimes, jobs fail due to increase in the size of sbtio.log file in the $UDUMP directory.

To resolve this, set the size limit for the sbtio.log file using the sMAXORASBTIOLOGFILESIZE registry key. Once the specified size limit is reached, the sbtio.log file gets pruned automatically.

Table Level Restore Intermittent Failures

The 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


When restoring Oracle database on Windows clients, if the Switch database mode for restore option is selected to keep database in correct mode during restore, the database may not restart after switching the database mode. Also, the restore operation may fail with the following error message.

This issue occurs if the oracle user has a higher ulimit configuration than the root user. To resolve this issue, apply the ulimit value of Oracle user for the restore using the following steps:

1. From the CommCell Browser, navigate to Client Computers.

2. Right-click the <Client>, and then click Properties.

3. Click Advanced.

4. Click the Additional Settings tab.

5. Click Add.

6. In the Additional Settings dialog:

In the Name box, type OracleUser.

In the Category box, select or type OracleAgent from the list.In the Type box, select String.

In the Value box, type the Oracle user name (eg., oracle).

7. Click OK.

8. Restart Data Protection Suite Services on the client.

ORA-31623: a job is not attached to this session via the specified handleIn such cases, set the sNODATAPUMPEXPORT registry key to Y on the client and re-submit the job.

Command Line Restore Failures Verify the availability of the required resource then rerun the RMAN command line operationSometimes, the third party command line jobs may hang when you perform large backups and restores.This happens since ClOraControlAgent updates the job manager for every 100MB data transfer and this causes the thread failure for large backups/ restores after transferring some of the data.The following exception will be seen in the clOraControlAgent.log:

You can set sBYTESDIFFMBS registry key <value> in MBs in OracleAgent/.properties.This will update the job manager at every <value> in MBs specified in the key.

5710030 304 02/22 03:47:23 608119 OraAgentBase::NotifyCommServeJobContinue() -m_jobObject->setUnCompBytesToAdd(105119744) ...5710030 304 02/22 03:47:24 608119 CvThread::start_func() - Unhandled exception.5710030 405 02/22 03:47:37 608119 ClOraControlAgent::OnClientTimeout() - Got timed out while waiting for msg from client 0

Unable to create a Standby Database

Standby database fails with the following error message:

temporary file TEMP01.DBF conflicts with file used by target databaseMake sure that the Standby Role Initialization parameter, DB_FILE_NAME_CONVERT, is set to add all the temp datafiles 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>

The Block Size during the backup and restore are different.

Error Code: [19:1336]

Description: Oracle Restore [Job[xxxxx] thread[xxxxxxxx]: Did not read correct number of bytes, expected: xxxxxx, read: yyyyyy.]

The Block Size during the backup and restore are different.

While performing a restore, It is recommended to use the same block size that you have used during the backup. For example, if you have used 128 KB as the block size during the backup, make sure to use the same 128 KB as the block size during the restore of that backup. An increase in the block size during the restore may cause the restores to fail.

Restore Error When Switch Database Mode is Enabled

RMAN Script execution failed with error [RMAN-04014: startup failed: ORA-27137: unable to allocate large pages to create a shared memory segment]. Please check the Logs for more details.

Recovering data associated with deleted clients and storage policies


Symptom

In a disaster recovery scenario, use the following procedure to recover data associated with the following entities:

Deleted storage policy

Deleted client, agent, backup set or instance

Before You Begin

This procedure can be performed when the following are available:

You have a Disaster Recovery Backup that contains information on the entity that you are trying to restore. For example, if you wish to recover a storage policy (and the data associated with the storage policy) that was accidentally deleted, you must have a copy of the disaster recovery backup that was performed before deleting the storage policy.

Media containing the data you wish to recover is available and not overwritten.

If a CommCell Migration license was available in the CommServe when the disaster recovery backup was performed, no additional licenses are required. If not, obtain the following licenses:

IP Address Change license

CommCell Migration license

See License Administration for more details.

A standby computer, which is used temporarily to build a CommServe.

Resolution

Recovering Deleted Data

1. Locate the latest Disaster Recovery Backup that contains the information on the entity (storage policy, client, agent, backup set or instance) you are trying to restore.

Check the Phase 1 destination for the DR Set or use Restore by Jobs for CommServe DR Data to restore the data.

If the job was pruned and you know the media containing the Disaster Recovery Backup, you can move the media in the Overwrite Protect Media Pool. See Accessing Aged Data for more information. You can then restore the appropriate DR Set associated with the job as described in Restore by Jobs for CommServe DR Data.

If the job is pruned and you do not know the media containing the Disaster Recovery Backup, you can do one of the following:

If you regularly run and have copies of the Data on Media and Aging Forecast report, you can check them to see if the appropriate media is available.

If you do not have an appropriate report, and know the media that contains the DR Backup, catalog the media using Media Explorer. Once the cataloging process is completed, details of the data available in the media are displayed.

2. On a standby computer, install the CommServe software. For more information on installing the CommServe, see Install the CommServe.

3. Restore the CommServe database using the CommServe Disaster Recovery Tool from the Disaster Recovery Backup described in Step 1. (See CommServe Disaster Recovery Tool - Getting Started for step-by-step instructions.)

4. Verify and ensure that the HDPS Client Event Manager HDPS Communications Service (EvMgrS) is running.

5. If you did not have a CommCell Migration license available in the CommServe when the disaster recovery backup was performed, apply the IP Address Change license and the CommCell Migration license on the standby CommServe. See Activate Licenses for step-by-step instructions.

6. Export the data associated with the affected clients from the standby CommServe as described in Export Data from the Source CommCell.

7. Import the exported data to the main CommServe as described in Import Data on the Destination CommCell.

This brings back the entity in the CommServe database and the entity is visible in the CommCell Browser. (Press F5 to refresh the CommCell Browser if the entity is not displayed after a successful merge.)

8. If you have additional data that was backed up after the disaster recovery backup and before the deletion of the entity, use the procedure described in Import Metadata from a Tape Media to obtain the necessary information.

9. You can now browse and restore the data from the appropriate entity.

When restoring large tables, the restore operation may fail if there is insufficient memory allocation for creating the auxiliary instance.

When you start the Command Line Interface to capture data, use the name of the standby CommServe in the -commcell argument.

As a precaution, mark media (tape media) associated with the source CommCell as READ ONLY before performing a data recovery operation in the destination CommCell.

Optimizing Memory Allocation for Table Restores


Use the following steps to optimize the memory allocation for the auxiliary instance:

Allocating Memory for Auxiliary Instance

By default, 16MB pool size is allocated for the auxiliary instance. Use the following steps to increate this size limit:



3. Click Advanced.


5. Click Add.

6. On the Add Additional Settings dialog:

In the Name box, type sLARGEPOOLSIZE.


In the Value box, type the memory for the auxiliary instance (for example, 32M).

7. Click OK.

Allocating Memory for Oracle Streams

By default, the system allocates 48 MB for the Oracle streams. You can modify this value using the following steps:



3. Click Advanced.


5. Click Add.


In the Name box, type sSTREAMSPOOLSIZE.


In the Value box, type the memory for oracle streams (for example, 96M).

7. Click OK.

Setting the UNDO Retention Period

Whenever a transaction is committed, the old undo information is retained by default for a period of 1800 seconds. You can modify this value, using the following steps:



3. Click Advanced.


5. Click Add.


In the Name box, type sUNDORETENTIONSIZE.


In the Value box, type the retention period (for example 2200 seconds).

7. Click OK.

Viewing 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 <Instance>, point to View, and then click either Backup History or Restore History.

2. Click OK.

3. On the Job History window, right-click the job, and then select View Log File.The RMAN Output Log will display for the job.

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:

Oracle - Backup and Recovery Guide

Oracle - Recovery Manager User’s Guide and Reference

Oracle - Recovery Manager User’s Guide

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.

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.

For Oracle 10g and higher, 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.

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> }

When you recover a database to a point in time, the RMAN command ALTER DATABASE OPEN RESETLOGS is executed which will reset the SCN (System Change Number) and time stamp on every object of the database (i.e., datafiles and control files). Also, only the archived redo logs that match the RESETLOGS SCN and timestamp value will be applied to the database, thus recovering the database to a time that is not current. 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 you are not sure about the point-in-time for the recovery, it is recommended to restore the data and the control files to a point in time without recovery. 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, you can recover the database to the point in time 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.

Sample Script for Resetting a Database After RESETLOGS

The following example resets a database after performing an incomplete media recovery:

run {allocate channel dev1 type disk;set until logseq 1234 thread 1;restore database skip tablespace readonly;recover database;sql "ALTER DATABASE OPEN RESETLOGS";release channel dev1;}

reset database;

CommCell Console Errors

Point-in-Time Recovery


Sample Script for Resetting the Database to an Old Incarnation

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 itrun {allocate channel dev1 type disk;restore controlfile;startup mount;restore database;recover database;sql "ALTER DATABASE OPEN RESETLOGS";release channel dev1;}

Restore jobs from Oracle iDataAgent will be displayed as "Completed w/ one or more errors" in the Job History in the following cases:

During a table restore, if the export or import of table fails.

RMAN recovery is completed, but an incorrect open mode is selected for restore.

Restore jobs from Oracle for Oracle iDataAgent will be displayed as "Completed with Warnings" in the Job History in the following case:

When the database restore succeeds but it fails when recovering the database or opening the database.

If you receive an Oracle error during an Oracle 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.

© 1997-2013 CommVault Systems Inc. All rights reserved.This document may not be copied or further distributed, in whole or in part, without written permission from CommVault Systems Inc.

List of Database IncarnationsDB Key------

Inc Key-------

DB Name-------

DB ID-----

CUR---

Reset SCN---------

Reset Time----------

1 2 PROD1 1224038686 NO 1 02-JUL-981 582 PROD1 1224038686 YES 59727 10-JUL-98

Completed with One or More Errors

Restore Completed with Warnings

Oracle Errors


Documents

Database Administrator (DBA) GUIDE Oracle iDataAgentsupport-q.bull.com/ols/product/storage/backup/calypso/release_10_0...Oracle DBA Guide Overview System Requirements Getting Started