Reference Architecture for HP Data Protector and

Oracle 11gR2 RAC on Linux

Technical white paper
Table of contents
Executive summary .......................................................................................................................2
Data Protector and Oracle 11gR2 Database integration ...................................................................2
Integration components ..............................................................................................................2
Business case for backup and recovery solution ...............................................................................4
Solution overview .........................................................................................................................5
Solution components .................................................................................................................5
Solution environment .....................................................................................................................5
Hardware components ................................................................................................................12
Oracle ZDB backup configuration for filesystem based database .....................................................13
Oracle ZDB backup configuration for ASM based database ............................................................17
Oracle 11gR2 installation tips for Red Hat Linux 5 .........................................................................18
Summary ...................................................................................................................................18
For more information...................................................................................................................19

Executive summary
A variety of backup strategies exist to best meet your business priorities. If the Oracle database availability is the
highest priority, for instance, the backup strategy should include online backups that are performed frequently to
minimize recovery time. The HP Data Protector zero downtime backup functionality offers online backup capabilities
with minimal degradation of the application system performance.
HP Data Protector zero downtime backup (ZDB) is designed to improve backup strategies for high-availability systems
and non HA systems. ZDB delivers best-in-class backup and recovery solutions for Oracle 11gR2 database in Linux
environment. Zero downtime backup and recovery have two great advantages over other backup and restore
techniques.

Minimal downtime or impact on the application during backup

Short restore times (minutes instead of hours)
The HP Data Protector 6.20 Oracle integration links the Oracle database management software with Data Protector.
From the Oracle point of view, Data Protector represents media management software. On the other hand, the
Oracle database management system can be seen as a data source for backup, using backup media and devices
controlled by Data Protector.
Target audience: This document is for IT managers, database and system administrators, and experienced users who
wish to learn more about the capabilities of HP Data Protector 6.20 and how it can be used to integrate Oracle
11gR2 with ZDB backup. Knowledge of the underlying storage and server components will be helpful when reading
this white paper. You should also have a good understanding of Oracle Real Application Clusters (RAC). Please see
the for more information section at the end of this paper for links to additional information on these topics.
This white paper describes testing performed in December 2011.

Data Protector and Oracle 11gR2 Database integration

Integration components
The software components involved in backup and restore processes are:

The Oracle Recovery Manager (RMAN)

The Data Protector Oracle integration software
The Data Protector Oracle Integration agent (ob2rman.pl) executes RMAN, which directs the Oracle server
processes on the target database to perform backup, restore and recovery. RMAN maintains the required information
about the target databases in the recovery catalog, the Oracle central repository of information, and in the control file
of a particular target database.
The main information which ob2rman.pl provides to RMAN is:

Number of allocated RMAN channels

RMAN channel environment parameters
Information on the database objects to be backed up or restored
The Data Protector Oracle Integration agent (ob2rman.pl) works with RMAN to manage all aspects of the
following operations on the Oracle target database:
Backups (backup and copy)
Recovery (restore, recovery, and duplication)
For backup, ob2rman.pl uses the Oracle target database views to get information on which logical (tablespaces) and
physical (datafiles) target database objects are available for backup. For restore, ob2rman.pl uses current control file
or recovery catalog (if used) to get information on which objects are available for restore. Using the Data Protector
integration with RMAN, you can back up and restore the Oracle control files, datafiles, and Archived Redo Logs.

The interface from the Oracle server processes to Data Protector is provided by the Data Protector Oracle integration
Media Management Library (MML), which is a set of routines that allows the reading and writing of data to General
Media Agents. Besides handling direct interaction with the media devices, Data Protector provides scheduling, media
management, network backups, monitoring, and interactive backup. Figure 1 illustrates concept of Oracle
integration, data and the control flow.

Figure 1. Concept of Oracle integration, data and the control flow

A backup that includes all datafiles and current control file that belong to an Oracle Server instance is known as a
whole database backup. Data Protector ZDB can be used for online or offline backup of the Oracle target database.
However, you must ensure that the backup objects (such as tablespaces) are switched into the appropriate state
before and after a backup session. For online backup, the database instance must operate in the ARCHIVELOG
mode; whereas for offline backup, objects need to be prepared for backup using the Pre-exec and Post-exec options
in the backup specification. The Data Protector backup specification contains information about backup options,
commands for RMAN, Pre- and Post-exec commands, media, and devices.
Data Protector provides broad coverage for storage systems. In this white paper Data Protector 6.20 is tested with HP
6400 Enterprise Virtual Array (EVA6400) snapshot types:

Snapshot with pre-allocation of disk space (standard snapshot).

Snapshot without pre-allocation of disk space (virtually capacity-free snapshot or vsnap).
Complete copy of the source volume (the virtual disk containing original data), which is independent of the source
volume (snapclone).Using the EVA6400 Array integration, the backup can be performed on disk, tape and
disk+tape media.

 ZDB to disk: The replica produced is kept on a disk array until reused. This replica becomes part of the replica set
and can be used for instant recovery. ZDB to disk is performed if the option Track the replica for instant recovery
is selected in a ZDB backup specification and to disk is selected when running/scheduling a backup.

ZDB to tape: The replica produced is streamed to backup media, typically tape, according to the tape backup type
you have selected. This replica is deleted after backup if the option keep the replica after the backup is cleared
for the backup specification. If this option is selected, the replica remains on a disk array until reused and becomes
part of the replica set. However, it cannot be used for recovery.

ZDB to disk+tape: The replica produced is kept on a disk array until reused and is also streamed to backup media
according to the tape backup type you have selected. This replica becomes part of the replica set and can be used
for instant recovery. ZDB to disk+tape is performed if the option Track the replica for recovery is selected in a
ZDB backup specification, and to disk+tape is selected when running/scheduling a backup.

Business case for backup and recovery solution

The growing requirement for data security for mission critical applications, together with the increasing sophistication
of Storage Area Network (SAN) environments, has resulted in a rapid expansion in the use of large disk arrays
containing RAID technology. These can hold large application databases, containing vast amounts of data. By using
storage virtualization techniques, disk arrays can be divided into many virtual disks. These can easily be copied
within a disk array, perhaps many times dependent on disk array technology and the available storage space. This
makes it possible to perform operations on copies of data without any risk to the original data. In particular, it
enables effective backup solutions for applications in high-availability and mission-critical areas. Conventional tape
backup and restore techniques are not fast enough to handle the enormous amounts of data involved in a world of
terabyte databases where information is expected to be available 24 hours a day.
The key benefits of ZDB and recovery include:

ZDB Backup set method: The Oracle backup set ZDB method, the entire data to be backed up is provided to Data
Protector through the Oracle APIthe data is streamed through the Data Protector Oracle integration MML.
Depending on the location of the Oracle control file, online redo log files, and SPFILE, the following two options
are possible:

Oracle control file, online redo log files, and SPFILE reside on a different volume group (if LVM is used) or
source volume than Oracle datafiles. By default, instant recovery for such a configuration is enabled.

Oracle control file, online redo log files, SPFILE reside on the same volume group (If LVM is used) or source
volume as Oracle datafiles

Online backup: The database is placed in hot-backup mode while a replica of sections to be backed up is created.
In this mode, any changes to the database are written to transaction logs, not the database itself. When the
database is fully functional again, it is updated from the transaction logs. This allows the database to be operated
on without stopping the application. A separate backup server can be used for backup application database to
save the production server bandwidth.

Offline backup: Database operation is simply stopped while a replica is created. No transactions are possible
during this time.

Solution overview
The solution described in this paper will create an Oracle backup and recovery sample architecture to integrate Data
Protector in an Oracle Database environment. Backup and recovery strategies will be considered in context to an
Oracle Real Application Clusters (RAC) environment. This project is a base Data Protector (DP) solution which resides
in an HP BladeSystem environment; it provides for a scale-out environment with respect to DP cell servers and
installation servers.

Solution components
HP Data Protector 6.20 ZDB environment has the following key components:

Hardware
HP BladeSystem c7000 enclosure
BL460c G7 servers
HP Virtual Connect Flex Fabric 10Gb/24 port modules
EVA6400 storage
HP SAN Switch and 4/16 SAN Switch
HP MSL2024 G3 series tape library
HP NC553i FCOE (Fiber Channel over Ethernet)

Management software
HP Command View EVA (CV EVA)
HP Data Protector 6.20
Red Hat Enterprise Linux device-mapper multipath
Oracle database management software (dbca, asmca, etc.)

HP NC553i FCOE driver version

This configuration is tested with Linux FCOE driver 8.2.0.78.7p.

Solution environment
This section outlines the setup used in Data Protector 6.20 ZDB solution for Oracle using:

ZDB Backup/Restore
ZDB snapshot Oracle Integration.
Figure 2 illustrates the functional diagram of ZDB backup.

Figure 2. Functional diagram of ZDB setup

Abbreviations:

SMISA Storage Management Initiative Specification Agent

MA Media Agent
DA Disk Agent
RHEL 5.5 - Red hat Enterprise Linux 5 Update 5
RAC Real Application Clusters

Table 1. Tested configuration

Host name

Host name description

Cluster name

EVACMDVIEW_Server

Windows Management Server

N/A

BKUP_Server

Data Protector Cell Server (Backup

Server)

N/A

APP_Server1

Application Server1

raccluster

APP_Server2

Application Server 2

raccluster

Microsoft Windows Server 2008 R2 Management server:

It is a centralized server which manages all the resources.

It is a management station for CV EVA.
It is a management station for DP GUI. It manages adding clients, auto configure devices and initiating backup
and restore tasks. It integrates disk agents, media agents and Oracle/DP integration, etc.

EVA6400 SMISA agent is configured.

To verify your setup you can use several tools as shown in the notes below.

Note: omnidbsmis.exe executes administrative tasks on the ZDB database (SMISDB)

and on a disk array of the HP EVA Disk Array Family.
C:\Program Files\OmniBack\bin>omnidbsmis.exe -ompasswd -add
EVACMDVIEW_Server
Please enter P6000 EVA SMI-S provider password: ********
Please repeat P6000 EVA SMI-S provider password: ********
P6000 EVA SMI-S provider authentication data updated for user administrator at host
EVACMDVIEW_Server

Note
C:\Program Files\OmniBack\bin>omnidbsmis.exe -ompasswd list
User
Host
Port
Ssl
----------------+--------------------+-----+-------------Administrator
BKUP_Server
5988
No
Administrator
EVACMDVIEW_Server
5988
No

Note:
C:\Program Files\OmniBack\bin>omnidbsmis.exe -ompasswd check
This command checks the communication to configured SMI-A providers.

RHEL 5.5 DP Cell server:

DP Cell server is configured as a backup server.

The backup server should have the same Oracle directory structure (such as ORACLE_HOME and CRS_HOME) as
application servers.

Oracle 11gR2 Grid installed as a standalone server. Grid infrastructure is important for ZDB backup process.
RMAN Catalog database is configured on this server. Each application database should be registered under
catalog database for ZDB backup.

Application database should be able to login to the backup host using sqlplus sys/sys@DBSID as sysdba
credentials. Make sure the application database is accessible by the backup host. Make sure the tnsnames.ora
and listener.ora files are same in both application servers and backup server.
Sample listener.ora file:
SID_LIST_LISTENER =
(SID_LIST =
(SID_DESC =
(SID_NAME = PLSExtProc)
(ORACLE_HOME = /u01/app/11.2.0/dbhome_1)
(PROGRAM = extproc)
)
(SID_DESC =
(GLOBAL_DBNAME = RCBB)
(ORACLE_HOME = /u01/app/11.2.0/dbhome_1)
(SID_NAME = RCBB)
)
(SID_DESC =
(GLOBAL_DBNAME = RCBB)
(ORACLE_HOME = /u01/app/11.2.0/dbhome_1)
(SID_NAME = RCBB1)
)
(SID_DESC =

RAC database name

RAC database instance name 1

(GLOBAL_DBNAME = RCBB)
(ORACLE_HOME = /u01/app/11.2.0/dbhome_1)
(SID_NAME = RCBB2)
)
(SID_DESC =
(GLOBAL_DBNAME = RCAA)
(ORACLE_HOME = /u01/app/11.2.0/dbhome_1)
(SID_NAME = RCAA)
)
(SID_DESC =
(GLOBAL_DBNAME = +ASM1)
(ORACLE_HOME = /u01/app/11.2.0/grid)
(SID_NAME = +ASM1)
)
(SID_DESC =
(GLOBAL_DBNAME = +ASM2)
(ORACLE_HOME = /u01/app/11.2.0/grid)
(SID_NAME = +ASM2)
)

RAC database instance name 2

Single instance database

ASM instance 1

ASM instance 2

Note
ASM information is also required in listener.ora files. For Real Application
Clusters (RAC) environment, mention all ASM instance names e.g. +ASM1,
+ASM2 in listener.ora file.

Sample tnsnames.ora file:

RCBB =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = raccluster)(PORT = 1521)) RAC cluster name
(ADDRESS = (PROTOCOL = TCP)(HOST = APP_Server1-vip(PORT = 1521))
RAC database
(ADDRESS = (PROTOCOL = TCP)(HOST = APP_Server2-vip)(PORT = 1521))
(CONNECT_DATA =
(SERVER = DEDICATED)
(SERVICE_NAME = RCBB)
)
)
RCBB1 =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = raccluster)(PORT = 1521))
(ADDRESS = (PROTOCOL = TCP)(HOST = APP_Server1-vip)(PORT = 1521)) RAC database
instance 1
(ADDRESS = (PROTOCOL = TCP)(HOST = APP_Server1)(PORT = 1521))
(CONNECT_DATA =
(SERVER = DEDICATED)
(SERVICE_NAME = RCBB)
(INSTANCE_NAME = RCBB1)
)
)
RCBB2 =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = raccluster)(PORT = 1521))
(ADDRESS = (PROTOCOL = TCP)(HOST = APP_Server2-vip)(PORT = 1521)) RAC database
instance 2
(ADDRESS = (PROTOCOL = TCP)(HOST = APP_Server2)(PORT = 1521))
(CONNECT_DATA =
(SERVER = DEDICATED)
(SERVICE_NAME = RCBB)
(INSTANCE_NAME = RCBB2)
)
)
RCAA =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = APP_Server2)(PORT = 1521))
database
(CONNECT_DATA =

Single instance

(SERVER = DEDICATED)
(SERVICE_NAME = RCAA)
)
)
+ASM1 =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = raccluster)(PORT = 1521))
(ADDRESS = (PROTOCOL = TCP)(HOST = APP_Server1-vip)(PORT = 1521)) ASM instance 1
(ADDRESS = (PROTOCOL = TCP)(HOST = APP_Server1)(PORT = 1521))
(CONNECT_DATA =
(SERVER = DEDICATED)
(SERVICE_NAME = +ASM1)
)
)
+ASM2 =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = raccluster)(PORT = 1521))
(ADDRESS = (PROTOCOL = TCP)(HOST = APP_Server2-vip)(PORT = 1521)) ASM instance 2
(ADDRESS = (PROTOCOL = TCP)(HOST = APP_Server2)(PORT = 1521))
(CONNECT_DATA =
(SERVER = DEDICATED)
(SERVICE_NAME = +ASM2)
)
)

Note
ASM instances are required in tnsnames.ora files. For RAC, mention all ASM
instance names +ASM1, +ASM2 in tnsnames.ora file

After configuring ZDB backup configuration using command line CLI in Application server, the configuration files
will get created in Cell Servers /etc/opt/omni/server/integ/config/Oracle8 location. These files have the details
about database ID and its credentials, ASM instance details, catalog database details and credentials.
During the backup process the DP GUI will fetch the details from this location:
/etc/opt/omni/server/integ/config/Oracle8.
cat /etc/opt/omni/server/integ/config/Oracle8
-rw------- 1 root root 341 Nov 28 00:12 2108799478
-rw------- 1 root root 870 Nov 28 00:12 BKUP_Server%initVASS_bckp.ora
-rw------- 1 root root 24 Nov 28 00:12 BKUP_Server%_OB2_GLOBAL
-rw------- 1 root root 258 Nov 28 00:12 BKUP_Server%VASS
-rw------- 1 root root 61 Nov 28 00:13 APP_Server1%_OB2_GLOBAL
-rw------- 1 root root 282 Nov 28 00:13 APP_Server1%VASS
-rw------- 1 root root 241 Nov 28 01:55 ob2_dpmctl_backup_18899_bfef.dma

Tape library is configured as a backup device on this server.

Cell file library is configured as a local device/repository (LVM device).
EVA6400 SMISA agent is configured. SMI-S password has to be provided. In our test it is same as Administrator
password.

Verify the SMISA agent configuration on the backup server:

[root@BKUP_Server bin]#. /omnidbsmis -ompasswd -add EVACMDVIEW_Server
Please enter P6000 EVA SMI-S provider password: ********
Please repeat P6000 EVA SMI-S provider password: ********
P6000 EVA SMI-S provider authentication data updated for
user administrator at host EVACMDVIEW_Server.

Verify the SMI-S configuration:

[root@BKUP_Server bin]#. /omnidbsmis -ompasswd -check -host BKUP_Server
[Normal] From: SMISA@BKUP_Server "SMISA" Time: 12/01/2011 09:46:17 PM
Checking the P6000 EVA SMI-S provider using this
connection data:
Host:
EVACMDVIEW_Server

User:
Namespace:
Port:
SSL mode:

Administrator
root/eva
5988
FALSE

[Normal] From: SMISA@BKUP_Server "SMISA" Time: 12/01/2011 09:46:17 PM

This P6000 EVA SMI-S provider has access to the following P6000 EVA Family unit:
Array Name:
EVA6400-C7
Array WWN:
50001FE1501D2050
Array Status:
OK
Status Description:
initialized_ok
Firmware Version:
09501200
Comment Field:
Configuration checking finished.

RHEL 5.5 Oracle 11gR2 RAC Application servers (1 and 2):

The application servers have Oracle 11gR2 Grid installed.

ASM disk groups are created.

To list the ASM disk groups:

$ export ORACLE_SID=+ASM1
$ export ORACLE_HOME=/u01/app/11.2.0/grid
$ asmcmd
State
Type
MOUNTED EXTERN N
MOUNTED EXTERN N
MOUNTED EXTERN N

Rebal
512
512
512

Sector Block
4096 1048576
4096 1048576
4096 1048576

AU
204800
10240
20480

Total_MB
201361
7567
20385

Free_MB

Req_mir_free_MB
0
0
0

Usable_file_MB
201361
7567
20385

Offline_disks
0
0
0

Voting_files
N
N
N

Name
DATA
RAC
SIDB

RAC database and single instance database is configured on ASM disk groups.
ZDB backup should be configured on Application server using following command.
For RAC database:
$/opt/omni/lbin/util_oracle8.pl -config -dbname RCBB -orahome /u01/app/11.2.0/dbhome_1 prmuser sys -prmpasswd sys -prmservice RCBB1,RCBB2 -rcuser rman -rcpasswd rman -rcservice
CATDB -zdb_method BACKUP_SET -bkphost BKUP_Server -client raccluster -asmhome
/u01/app/11.2.0/grid -asmuser sys -asmpasswd sys -asmservice +ASM1,+ASM2

Note
The client name should be the cluster name.

For Single instance database:

$/opt/omni/lbin/util_oracle8.pl -config -dbname SIDB -orahome /u01/app/11.2.0/dbhome_1 prmuser sys -prmpasswd sys -prmservice SIDB -rcuser rman -rcpasswd rman -rcservice CATDB zdb_method BACKUP_SET -bkphost BKUP_Server -client APP_Server2 -asmhome /u01/app/11.2.0/grid
-asmuser sys -asmpasswd sys -asmservice +ASM1

Note:
The ZDB GUI based database backup configuration is not supported for ASM
based databases. All the ASM options can be used only in command line
mode.

ZDB backup and restore solutions are tested on filesystem, ASM and non-ASM configurations on Red Hat Linux
environment. Oracle ASM disks are managed using Linux device-mapper multipath.

10

Table 2. Tested configuration

Database/Filesystem

Backup

Restore

RAC based ASM database

Tape Library

Tape Library

Single Instance database

Tape Library

Tape Library

Linux LVM based filesystem

Tape Library/CellFileLibrary

Tape Library/CellFileLibrary

Linux filesystem

Tape Library/CellFileLibrary

Tape Library/CellFileLibrary

Note
Instant recovery is not supported for ASM based disks.
Oracle catalog database is required in the backup server and all the

application database should be registered in the catalog database.

Resync catalog database will be automatically taken care by the Data

Protector during the backup process if there any changes done in the
application database.
Verify the list of database names registered under RMAN catalog database:

RMAN> list DB_UNIQUE_NAME all;

List of Databases
DB Key DB Name
DB ID
Database Role
Db_unique_name
------- ------- ----------------- --------------- -----------------2091
RCAA
104569537
PRIMARY
RCAA
299
RCBB
1151267082
PRIMARY
RCBB
ZDB configuration is supported using CLI commands only. Non ASM setups

can be configured using Data Protector GUI.

ASM based ZDB backup is supported using BACKUP_SET method.
ASM based inputs can be only given using CLI based command set.
All application databases should accessible by backup server.
All device-mapper devices should have same oracle user and DB group

permissions.

EVA6400 storage array:

Make sure the storage has enough of space to handle snapshot.
MSL2024 G3 Tape Library:
Make sure the tape library is accessible by the backup host, perform barcode scanning and make the device
available during the ZDB backup process.
Fiber Channel switch:
Make sure all the devices are zoned respectively to access the storage LUNs.

11

Hardware components
This section outlines the hardware components used in Data Protector ZDB environment described in this white paper.
Figure 3 illustrates the front and rear views of hardware used in this configuration.

Figure 3. Front and rear views

12

Oracle ZDB backup configuration for filesystem based

database
1.

Install the database on the filesystem.

2.

Register the database under RMAN catalog database.

3.

Start the DP GUI.

4.

Create a new backup by selecting the filesystem.

5.

Select the backup method and select the subtype as HP EVA6400 SMI-S.

Figure 4 illustrates the Create New Backup for filesystem in the DP GUI.

Figure 4. Creating New Backup

6.

Select the application system and the backup system.

7.

Select he snapshot management options as Original volume and snapshot type as Standard snapshot.

8.

Enable Backup system options as shown below.

Figure 5 illustrates the backup specifications such as snapshot type and backup system options, etc.

13

Figure 5. Backup snapshot specifications

9.

14

Choose the filesystem which needs to be backed up.

Figure 6 illustrates the list of filesystems available for backup.

Figure 6. Select the available filesystem for backup

Figure 7 illustrates the list of vdisk created in the EVA6400 array.

Figure 7. List of created vdisk in EVA6400 array

15

Figure 8 illustrates the list of destination backup devices available for backup.

Figure 8. List of available destination device s for backup

10. Review the selected filesystem and proceed further.

16

Figure 9 illustrates the selected filesystem for backup.

Figure 9. Selected filesystem for backup

11. Save the ZDB backup and start the backup process.

Oracle ZDB backup configuration for ASM based database

1. Install the database on ASM diskgroup.
Register the database in backup servers catalog database.
Configure the ZDB backup using CLI commands on application server as oracle user. Make sure RETURN
value is 0 i.e. successful configuration without errors.
ZDB configuration for RAC database:
$/opt/omni/lbin/util_oracle8.pl -config -dbname RCBB -orahome /u01/app/11.2.0/dbhome_1
-prmuser sys -prmpasswd sys -prmservice RCBB1,RCBB2 -rcuser rman -rcpasswd rman rcservice CATDB -zdb_method BACKUP_SET -bkphost BKUP_Server -client raccluster asmhome /u01/app/11.2.0/grid -asmuser sys -asmpasswd sys -asmservice +ASM1,+ASM2
*RETVAL*0

ZDB configuration for Single instance database:

$/opt/omni/lbin/util_oracle8.pl -config -dbname SIDB -orahome /u01/app/11.2.0/dbhome_1
prmuser sys -prmpasswd sys -prmservice SIDB -rcuser rman -rcpasswd rman rcservice CATDB -zdb_method BACKUP_SET -bkphost BKUP_Server -client APP_Server1 asmhome /u01/app/11.2.0/grid -asmuser sys -asmpasswd sys -asmservice +ASM1
*RETVAL*0

2. Start the DP GUI.

Create a new backup by selecting the Oracle.

Select the SMB_backup_set method and select the subtype as HP EVA6400 EVA SMI-S.

Select the application system and the backup system.

Select he snapshot management options as Original volume and snapshot type as Standard snapshot
and proceed further.

Verify the database name, RMAN credentials and backup method is BACKUP_SET method. Proceed
further.

Select the target device as Tape library and proceed further.

Save the ZDB backup by giving name and start the backup.

Monitor the backup process from DP GUI.

17

Figure 10 illustrates the DP monitoring window which shows the current backup progress.

Figure 10: DP monitoring Window

Oracle 11gR2 installation tips for Red Hat Linux 5

Refer to Oracle 11gR2 installation guide for Red Hat Linux 5. There are few changes that need to be done to invoke
the device-mapper multipathing device name persistency after reboots.
1. Download and install oracle ASM library rpm (for appropriate Linux version).
Append the following to the /etc/sysconfig/oraclesasm file:
# ORACLEASM_SCANORDER: Matching patterns to order disk scanning
ORACLEASM_SCANORDER="mpath sd"

Save the file.

2. Create the following entries in /etc/rc.d/rc.local:
chown oracle:oinstall /dev/mapper/mpath*
chown oracle:oinstall /dev/dm-*
chown oracle:oinstall /tgt

Save the file. This will avoid the device-mapper device permission changes after the reboot. This is mandatory.
Make an entry if LVM based disk is used:
chown oracle:oinstall /dev/mapper/targt-lvol0

Summary
With HP Data Protector 6.20 you can create zero downtime backup (ZDB) for filesystem and ASM based Oracle
databases. This white paper details how to use the HP Data protector 6.20 to perform zero downtime backup for
Oracle 11gR2 RAC and single instance databases. It includes steps to configure the ZDB backup for Oracle 11gR2
RAC.

18

For more information

Data Protector guides:
After successful installation of Data protector 6.20 Manager, the guides can be obtained from DP Manager GUI.
Refer to the documents before ZDB configuration.

HP Data Protector Manager Help guides

Zero Downtime Backup Concepts Guide
Zero Downtime Backup Administrators Guide
Zero Downtime Backup Integration Guide
For more information on the HP BladeSystem c7000 enclosure, refer to:
http://h18004.www1.hp.com/products/blades/components/enclosures/c-class/c7000/
For more information on the HP 6400 Enterprise Virtual Array, refer to
http://h10010.www1.hp.com/wwpc/us/en/sm/WF04a/12169-304616-304648-304648-304648.html
For detailed information on HP Data Protector support matrices please visit:
http://www.hp.com/go/dataprotector
For more information on the Onboard Administrator, refer to:
http://h18004.www1.hp.com/products/blades/components/onboard/.
For more information on Virtual Connect, refer to:
http://h18000.www1.hp.com/products/blades/virtualconnect/infrastructure.html.
For more information on Flex-10, refer to:
http://h20000.www2.hp.com/bc/docs/support/SupportManual/c01608922/c01608922.pdf.
For more information on the BL460c G7 server blade, refer to http://www.hp.com/servers/bl460c.
To help us improve our documents, please provide feedback at
http://h71019.www7.hp.com/ActiveAnswers/us/en/solutions/technical_tools_feedback.html.

Copyright 2012 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice. The
only warranties for HP products and services are set forth in the express warranty statements accompanying such products and services.
Nothing herein should be construed as constituting an additional warranty. HP shall not be liable for technical or editorial errors or
omissions contained herein.
Oracle is a registered trademark of Oracle and/or its affiliates. Microsoft and Windows are U.S. registered trademarks of Microsoft
Corporation.
4AA3-9092ENW, Created January 2012