HP Data Protector ZDB Solution for Oracle on VMware using the EVA Storage Array Implementation Guide

About this guide .................................................................................................................................. 3 Audience ............................................................................................................................................ 3 Introduction ......................................................................................................................................... 4

Enterprise backup solutions overview.................................................................................................. 4 EBS history .................................................................................................................................. 4

HP StorageWorks Command View EVA overview ................................................................................ 5 Server options .............................................................................................................................. 5

HP StorageWorks SMI-S EVA overview............................................................................................... 6 Zero Downtime Backup topology ....................................................................................................... 7 Planning an HP Data Protector ZDB solution for an Oracle database on VMware .................................... 8

Design consideration factors .......................................................................................................... 8 Prerequisites for the virtual machine running the Oracle database ...................................................... 8 SAN configuration requirements..................................................................................................... 9 Other requirements ....................................................................................................................... 9 HP StorageWorks EVA required components ................................................................................. 10

Implementing an HP Data Protector ZDB solution for an Oracle database on VMware ............................... 10 Solution components....................................................................................................................... 10 Solution execution steps .................................................................................................................. 10 Setting up HP StorageWorks EVA disk array virtual disks.................................................................... 11

Creating the database virtual disks ............................................................................................... 11 Configuring Raw Device Mappings (RDM) VM disks .......................................................................... 14 Configuring NPIV-based LUN access on the VM ................................................................................ 16 Setting up the VM database and backup servers................................................................................ 17

Preparing the hardware on the VM database and backup servers .................................................... 17 Installing HP Data Protector components........................................................................................ 19 Configuring the HP Data Protector Oracle ZDB integration .............................................................. 19 Configuring the integration for the Oracle proxy-copy ZDB method .................................................. 20 Configuring the Data Protector ZDB database (SMISDB).................................................................. 21 Setting the login information for Command View EVA..................................................................... 21

Creating the HP Data Protector backup specifications ......................................................................... 22 Creating the Oracle database ZDB backup specification................................................................. 23 Creating the Oracle archive log backup specification ..................................................................... 29 Creating the Oracle home backup specification ............................................................................. 29

Running the HP Data Protector backup specifications for a ZDB of the database .................................... 30 Running the backup manually .......................................................................................................... 31

Automating the backup ............................................................................................................... 31 Oracle database restore and recovery ................................................................................................. 32

Glossary ........................................................................................................................................... 33 For more information.......................................................................................................................... 34

Related documentation.................................................................................................................... 34 Other HP Websites......................................................................................................................... 35

About this guide This guide is intended to address many of the integration issues when setting up backup and recovery of an Oracle database on a VMware virtual machine (VM) in an HP StorageWorks Enterprise Backup Solutions (EBS) environment. The guide also provides suggestions for the best solution.

Note: This guide does not provide specific documentation for installing and configuring VMware virtual machines, data protection software, or tape library hardware.

This guide addresses special configuration procedures that might not be covered in vendor documentation to help in setting up an efficient HP StorageWorks EBS environment.

IMPORTANT: Oracle has not certified any of its products on VMware virtualized environments. Oracle Support will assist customers running Oracle products on VMware in the following manner: Oracle will support issues that either are known to occur on the native OS, or can be demonstrated not to be as a result of running on VMware. If a problem is a known Oracle issue, Oracle support will recommend the appropriate solution on the native OS. If that solution does not work in the VMware virtualized environment, the customer will be referred to VMware for support. When the customer can demonstrate that the Oracle solution does not work when running on the native OS, Oracle will resume support, including logging a bug with Oracle Development for investigation if required. If the problem is determined not to be a known Oracle issue, HP will refer the customer to VMware for support. When the customer can demonstrate that the issue occurs when running on the native OS, Oracle will resume support, including logging a bug with Oracle Development for investigation if required. Note: Oracle has not certified any of its products on VMware, and use of Oracle products in the RAC environment are also not supported. For more information, see the Oracle Metalink Note 249212.1 at metalink.oracle.com.

Audience This guide is intended for network or database administrators who are implementing the HP StorageWorks Oracle Database on VMware Zero Downtime Backup (ZDB) Solution with HP Data Protector.

3

Introduction The Oracle database on VMware ZDB Solution enables you to back up an Oracle database residing on a VMware virtual machine with minimal impact on the database, virtual machine, and ESX server.

The VMware ZDB Solution uses the following:

• VMware ESX server • Microsoft Windows operating system installed on a VMware virtual machine • HP StorageWorks EVA Disk Array • HP StorageWorks physical or virtual tape libraries • HP StorageWorks Storage Data Protector • HP StorageWorks Business Copy EVA This combination enables snapshot or snapclone. The snapshot or snapclone volumes can then be presented to a backup server where the data can be copied to tape. The backup server offloads processing resources from the ESX server. The Oracle database remains available during the entire process.

VMware Zero Downtime Backup solutions are one of many different data protection solutions offered by HP. VMware Zero Downtime Backup solutions are unique in that they tie many software and hardware products together.

Note: The examples in this document use HP StorageWorks Business Copy snapshot data volumes. Snapclone and Vsnap can also be used for a ZDB solution but is not the focus of this document.

Enterprise backup solutions overview VMware ZDB solutions require storage components such as tape libraries, disk arrays, and servers, all on a Fibre Channel SAN. HP StorageWorks EBS is the HP StorageWorks SAN backup solution in which the servers are in the data path from the source to the target.

Setting up a Fibre Channel SAN backup solution can be challenging. Components are typically purchased at different times and arrive separately, or they are purchased from different vendors. Each piece of hardware ships with documentation for setup and deployment. These challenges might require additional time and money.

HP is committed to keeping these challenges to a minimum by providing the HP StorageWorks Enterprise Backup Solution design guide and this document. See the Related documentation section at the end of this document for other reference sources.

EBS history HP engineering teams have developed a comprehensive approach to ensure that hardware, firmware, and software components are properly fitted into an HP StorageWorks Enterprise Backup Solution. HP engineers

4

test the supported configurations and develop best practices to follow when setting up an EBS environment. The teams also test backup solution software and provide best practices to ensure that the EBS environment runs smoothly.

HP StorageWorks Command View EVA overview HP StorageWorks Command View EVA provides a Web interface to the EVA configuration and monitoring functions. The appliance manages the EVA in-band over the SAN. The Web interface served by the appliance is accessible over the LAN with a Web browser. The leftmost frame of the Command View EVA Web GUI contains five folders for each EVA. The EVA called EVARack48_4 with the five folders Virtual Disks, Hosts, Disk Groups, Data Replication, and Hardware is shown in Figure 1.

Server options EVA Device Management Server Options include:

• HP OpenView Storage Management Appliance (SMA) • HP ProLiant Storage Server (NAS) • Dedicated Management server • General purpose server

Note: See the HP StorageWorks Command View EVA Installation Guide for additional server requirements.

Note: This document does not give details on installing the HP StorageWorks EVA or Command View EVA components. This document does list the required components. For details on installing the EVA components please refer to EVA documentation.

5

Figure 1: HP StorageWorks Command View EVA window

• Virtual Disks – The unit of disk space that is seen by hosts on the SAN is called a virtual disk. Virtual

disks are simulated disk drives within a physical disk group. Properties of a virtual disk include the size of the logical unit number (LUN) that will be presented to the SAN, The RAID level of the LUN, the world wide LUN number of the LUN, and the hosts that can see it.

• Hosts—The Hosts folder contains definitions of the servers that can have virtual disks presented to them. A host definition includes the HBA WWN, the network name and IP address of the host, and the OS that is running on the host.

• Disk Groups—Physical disks are allocated into pools with common protection levels. These pools are called Disk Groups.

HP StorageWorks SMI-S EVA overview A key feature of the EVA is the ability to create snapshots of data stored on the disk arrays. These snapshots can be used to back up the data using a different server (backup system), and thus reduce the backup load from the production server (application system), allowing the production applications to run uninterrupted.

6

HP StorageWorks Storage Management Initiative Specification for Enterprise Virtual Array (SMIS-EVA) is the tool utilized by Data Protector to initiate creation of EVA virtual disk snapshots. Data Protector 6.0 supports the Vsnap, snapclone and standard snapshots provided by the EVA array.

Note: SMI-S EVA is part of the standard Command View EVA 8.0.2 installation; however there are prerequisites that must be met prior to installing SMI-S EVA. Please see the HP StorageWorks Command View EVA installation guide for details.

Zero Downtime Backup topology Figure 2 shows the physical and logical connectivity of the test environment. The test environment uses an HP StorageWorks EVA disk array, from which a copy of the Oracle Database can be taken using HP StorageWorks Business Copy. This copy can then be mounted on a backup server for backup.

Figure 2: Physical and logical connectivity of the test environment

S A N S w itc h 2 /1 6

7

Planning an HP Data Protector ZDB solution for an Oracle database on VMware When designing a ZDB solution for an Oracle database residing on a virtual machine, several factors should be considered. These factors include:

• Impact of the solution on the VMware ESX server • Impact of the solution on Virtual machine database server • Cost (mirrored primary storage, off-host backup server, and so on) • Backup and restore performance • Array integration • Ease of configuration and use • Complexity • Availability • Deployment • Backup options Design consideration factors Although cost is a major factor, many administrators are even more concerned with the impact of the ZDB solution on the VMware ESX and virtual machine running the Oracle database and the availability of the database. Using an off-host server removes the heavy demands of backups from the VMware ESX server and virtual machine running the Oracle database; however, database availability is also a noted benefit of ZDB solutions. Good performance can be achieved by using a capable backup server or multiple backup servers.

Restores are also a very important part of the solution, but they are often overshadowed by the benefits of the backups. Restores are accomplished by retrieving data from the backup device and restoring directly to the virtual machine running the Oracle database.

Array integration has a big impact on how the ZDB solution behaves. Zero Downtime Backup solutions require a hardware mirror or snapshot of the primary data volume. Cost, performance, and implementation are contributing factors in this decision. This white paper focuses on HP StorageWorks EVA storage arrays that use BC volumes. In a ZDB off-host backup scenario, the time required to complete a backup is not as critical as a scenario in which the VMware ESX server or virtual machine running the Oracle database performs the backup.

Prerequisites for the virtual machine running the Oracle database • The Oracle data volumes must reside on a mapped raw LUN using the physical compatibility raw device

mapping (RDM) feature of VMware in order to take advantage of HP StorageWorks Business Copy EVA. • The Oracle database must be running in archivelog mode.

8

Note: VMware N_Port ID Virtualization (NPIV) LUN access for the virtual machine running the Oracle database is recommended for this solution but not required. See Configuring NPIV-based LUN access on the VM for details on setting up NPIV.

SAN configuration requirements Use the following Fibre Channel configuration guidelines to ensure that the mirrored or snapshot data can be copied to the tape library or virtual library system by the backup server, and that it can also be retrieved from the library by the database server:

• When configuring the SAN, the HP StorageWorks EVA disk array must be presented to the VMware ESX server, the virtual machine running the Oracle database (if NPIV-based LUN access is configured), and the backup server.

• When configuring the SAN, the tape libraries must be presented to the backup server. • The data to be backed up must be located on an HP StorageWorks EVA disk array.

Other requirements The following six steps must be completed before an Oracle Database on VMware ZDB solution can be performed:

1. Place the database in hot backup mode (online backup), or shut down the database (offline backup). 2. Prepare (create snapshot or snapclone) and mount the BC volumes on the backup server. 3. Take the database out of backup mode (online backup), or start the database up (offline backup). 4. Back up the database. 5. Unmount the BC volumes from the backup server. 6. Destroy the snapshot or snapclone.

Note: Snapshots and snapclones can be used for fast database recovery if desired. In this scenario the snapshot or snapclone should not be destroyed until just prior to the next backup.

Note: When planning the ZDB solution, make sure that the components of the solution can accomplish these six steps. Integration with HP Data Protector greatly simplifies the implementation of these steps.

9

HP StorageWorks EVA required components • HP StorageWorks Virtual Controller Software (VCS) • HP StorageWorks Command View EVA software suite (includes CV EVA, CV EVAPerf, SSSU, and SMI-S

EVA). • HP StorageWorks Business Copy EVA license key.

Implementing an HP Data Protector ZDB solution for an Oracle database on VMware Certain configuration limitations apply and are noted where applicable. This white paper can serve as a template for similar solutions where there may be minor changes in design, such as the operating system version or HBAs used.

Solution components VMware HP StorageWorks

Hardware HP StorageWorks Software HP ProLiant Servers and

HBAs Oracle Software

VMware ESX 3.5 EVA disk array Command View EVA 8.0.2 software suite

HP ProLiant DL380G5 virtual machine host running VMware ESX 3.5

Oracle 10g/11g

Virtual machine running Windows 2003

MSL2024 tape library BC EVA license key FC2243 – 4G PCI-to-Fibre Channel host bus adapter for the VMware ESX 3.5 server

Raw Device Mapping (RDM)

VLS6100 virtual tape library

Data Protector 6.0 HP ProLiant DL380G4 backup server running Windows 2003

NPIV-based LUN access

Data Protector agents & integrations:

• Disk agent

• Media agent

• HP StorageWorks EVA SMI-S agent

• Oracle integration

AB379A – 4G PCI-to-Fibre Channel host bus adapter for the Windows 2003 backup server

Solution execution steps This solution uses the following steps, which are initiated by the HP Data Protector backup specification for the Oracle database:

1. Obtain a list of database data files and tablespaces. 2. Obtain a list of the HP StorageWorks EVA disk array source volumes on which the database data files

reside. 3. Place the database in hot backup mode (online backup) or shut down the database (offline backup). 4. Create database snapshot: Hardware snapshot the EVA virtual disks on which the database data files

reside. 5. Take the database out of hot backup mode (online backup) or startup the database (offline backup).

10

6. Mount the database snapshot on the backup server. 6. Mount the database snapshot on the backup server.

7. Use the RMAN utility to perform a backup of the database and the control files in backup set mode from the mirror or clone mounted on the backup server.

7. Use the RMAN utility to perform a backup of the database and the control files in backup set mode from the mirror or clone mounted on the backup server.

8. Back up the recovery catalog database. 8. Back up the recovery catalog database. 9. Unmount the snapshot from the backup server: Destroy the snapshot. 9. Unmount the snapshot from the backup server: Destroy the snapshot. The remainder of this section is a guide for installing and configuring the solution components so that the above steps can execute. The remainder of this section is a guide for installing and configuring the solution components so that the above steps can execute.

Setting up HP StorageWorks EVA disk array virtual disks Setting up HP StorageWorks EVA disk array virtual disks Use the following instructions if using the HP StorageWorks EVA disk array as the database storage for the ZDB solution. Use the following instructions if using the HP StorageWorks EVA disk array as the database storage for the ZDB solution.

Creating the database virtual disks Creating the database virtual disks 1. Start the HP StorageWorks Command View EVA Web-based GUI from the Command View EVA server

(for example, 1. Start the HP StorageWorks Command View EVA Web-based GUI from the Command View EVA server

(for example, ). ). 2. In the Command View EVA Storage Systems navigation tree select the proper storage system, then select

Virtual Disks and click on Create Vdisk. 2. In the Command View EVA Storage Systems navigation tree select the proper storage system, then select

Virtual Disks and click on Create Vdisk.

Note: Note: If the VMware ESX, virtual machine database, and backup servers have not been added as hosts in the HP StorageWorks Command View EVA for the associated disk array, see the HP StorageWorks Command View EVA user guide for adding new hosts.

11

Figure 3: HP StorageWorks Command View EVA: Virtual Disks

3. Enter the desired properties for the new Vdisk and then click on Create Vdisk.

Name (Unique Vdisk name)

Size (Desired size in GB of the Vdisk)

Redundancy (RAID level)

Present to host (ESX server)

Other properties as desired

12

Figure 4: HP StorageWorks Command View EVA: Create a Vdisk

Note: Additional storage can be added by repeating steps 2-3.

Note: Prior to completing step 4 the virtual machine NPIV WWNs must be created and presented to the EVA disk array. See the section Configuring NPIV-based LUN Access on the VM in this document.

4. Repeat steps 2-3 for the VM Oracle server host presenting the same Vdisks to the VM Oracle server host that were presented to the ESX server host.

13

Configuring Raw Device Mappings (RDM) VM disks 1. Start the VMware Infrastructure client GUI on the Windows server on which the VMware Infrastructure

client has been installed (see the VMware Website for detailed documentation). 2. Select the virtual machine from the left pane in the Hosts & Clusters navigation tree, and click Edit

virtual machine settings (see Figure 5).

Figure 5: VMware Infrastructure Client

3. In the Virtual Machine Properties window, select the Hardware tab, and click Add. 4. In the Add Hardware Wizard window, select Hard Disk as the device type, and click Next. 5. In the next window, select Raw Device Mappings as the disk to use, and click Next (see Figure 6).

14

Figure 6: Add Hardware Wizard

6. Select the LUN presented from the EVA disk array to the ESX server as the LUN to use for the raw disk,

and click Next. 7. Next, select the datastore on which to store the device mapping, and click Next. 8. Select Physical as the compatibility mode, and click Next. 9. Accept the pre-selected Virtual Device Node, and click Next. 10. When the Ready to Complete window displays, click Finish (see Figure 7).

15

Figure 7: Ready to Complete window

11. In the Virtual Machine Properties window, click OK to create the RDM.

Configuring NPIV-based LUN access on the VM

Note: NPIV-based LUN access on the VM is recommended but not required for this solution

Note: Prior to configuring NPIV on the VM, see the Fibre Channel SAN Configuration Guide ESX Server 3.5 for detailed instructions and requirements for NPIV.

1. Start the VMware Infrastructure client GUI on the Windows server on which the VMware Infrastructure client has been installed (see the VMware Website for detailed documentation).

2. Select the virtual machine in the Hosts & Clusters navigation tree, and click Edit virtual machine settings.

3. In the Virtual Machine Properties window, select the Options tab, and select Fibre Channel NPIV. 4. In the Fibre Channel Virtual WWNs box, select Generate new WWNs, and click OK (see Figure 8).

16

Figure 8: Configuring NVIP-based LUN access

5. Go back to the Options tab, and select Fibre Channel NPIV to see the WWNs that were created

for the virtual machine. 6. The virtual machine WWNs should be added to the Fibre Channel SAN configuration. If SAN zoning is

being used, add the WWNs to the proper zone with the HP StorageWorks EVA disk array. 7. The EVA database volumes should be presented to the virtual machine WWNs as already shown in the

Setting up HP StorageWorks EVA disk array virtual disks section of this document.

Setting up the VM database and backup servers The setup of the database and backup servers includes preparing the tape library and VLS, and installing and configuring Data Protector. This document assumes that Oracle is already installed, that a database instance is up and running, and that the database data files and control files are located on EVA disk array virtual disks that have been presented as VMware RDMs to the VMware Oracle database server.

Preparing the hardware on the VM database and backup servers A shared tape library or virtual library system (VLS) is part of the EVA Oracle ZDB solution.

17

Note: This document does not present the details of installing a tape library or VLS on the SAN. See the HP StorageWorks Enterprise Backup Solution design guide at http://www.hp.com/go/ebs for detailed information on installing a tape library or VLS.

The tape library or VLS robot and tape devices should be presented to the backup server. Windows Computer Management utility will show the robot and tape devices (see Figure 9).

Figure 9: Computer Management Utility

After the tape library and VLS robot and tape devices are presented to the backup server, HP Data Protector can be installed and configured.

18

Installing HP Data Protector components

Note: Prior to installing HP Data Protector components on the VM database and backup servers, all required HP Data Protector patches must be installed on the HP Data Protector installation server. The following Data Protector 6.0 patches are required for this solution:

- DPWIN_00378 (HP StorageWorks EVA SMI-S Agent)

- DPWIN_00379 (Media Agent)

- DPWIN_00402 (Core Component & Core of Integrations Component)

The following HP Data Protector components are required for this solution:

• HP Data Protector Disk Agent • HP Data Protector Media Agent • HP Data Protector EVA SMI-S Agent • HP Data Protector Oracle Integration

1. Run the HP Data Protector Manager GUI from the installation server to install the required components and license keys.

Note: Refer to the HP OpenView Storage Data Protector installation and licensing guide for instructions on installing HP Data Protector.

2. After HP Data Protector has been installed, run the Autoconfigure Devices wizard to properly configure the tape library or VLS for use by HP Data Protector

Configuring the HP Data Protector Oracle ZDB integration The following list gives an overview of the global tasks for configuring the HP Data Protector Oracle ZDB integration:

Note: See the HP OpenView Storage Data Protector ZDB integration guide for details on configuring the integration.

1. Configure the integration for the Oracle proxy-copy ZDB method. See Configuring the integration for the Oracle proxy-copy ZDB method.

2. Create the HP Data Protector backup specifications using the HP Data Protector Administration GUI. See Creating the HP Data Protector backup specifications.

19

Configuring the integration for the Oracle proxy-copy ZDB method Before starting the integration, ensure the following:

• A recovery catalog database is recommended for this solution and should be configured and running on the Oracle server. See the Oracle documentation for configuring a recovery catalog database.

• The Oracle network software must be correctly configured and running on the Oracle server.

Note: The Oracle network software is needed because during a backup, the HP Data Protector process, which is running on the backup system, has to be connected to the Oracle database on the Oracle server through Oracle TNS. See the detailed instructions in the HP OpenView Storage Data Protector ZDB integration guide for configuring Oracle TNS.

For online backup of the Oracle database, the database must be put into archivelog mode.

Oracle must be installed on the backup server and configured as follows:

1. Ensure that the Oracle software on the backup server and Oracle server have the same directory structure. ORACLE_HOME for both Oracle installations must be identical.

2. The database on the Oracle server must be accessible from the backup server. To enable this, verify that the following files are the same on the application system and the backup system. This can be accomplished by copying the files from the Oracle server to the backup server.

File Description

tnsnames.ora The default path is <ORACLE_HOME>\network\admin\tnsnames.ora

init<ORACLE_SID>.ora The default path is <ORACLE_HOME>\dbs\init<ORACLE_SID>.ora

SPFILE<ORACLE_SID>.ora The default path is <ORACLE_HOME>\dbs\SPFILE<ORACLE_SID>.ora

PWD<ORACLE_SID>.ora This is the Oracle password file.

The default path is <ORACLE_HOME>\database\PWD<ORACLE_SID>.ora

admin\<ORACLE_SID> This is a directory, containing all Oracle configuration files.

The default path is <ORACLE_BASE>\..\admin\<ORACLE_SID>

3. Verify that the Windows administrator user can connect to the target database and the recovery catalog database using the RMAN command on the backup system.

For example:

> rman target sys/manager@vmrdm catalog rman/rman@rcvcat

4. Configure the HP Data Protector Oracle ZDB integration-specific parameters on the backup server using

the command line interface:

perl util_oracle8.pl -CONFIG_SMB_PROXY <ORACLE_SID> <ORACLE_HOME> <TARGET_DATBASE_LOGIN> <RECOVERY_CATALOG_LOGIN> <CONTROL_FILE_LOCATION>

20

For example, with the following database information:

Parameter Data

Oracle SID vmrdm

OracleHome: O:\oracle\product\10.2.0\db_1

Database login: sys/manager

Recovery catalog database SID

rcvcat

Recovery catalog login rman/rman

Control file location O:\oracle\oradata\vmrdm

The util_oracle8.pl utility would be used as follows:

>cd C:\program files\omniback\bin >perl util_oracle8.pl -CONFIG_SMB_PROXY vmrdm \ O:\oracle\product\10.2.0\db_1 sys/manager@vmrdm \ rman/rman@rcvcat o:\oracle\oradata\vmrdm

5. Run the following command to check the configuration:

perl util_oracle8.pl -CHKCONF_SMB <ORACLE_SID>

Configuring the Data Protector ZDB database (SMISDB)

Note: For details on the Data Protector ZDB database please refer to the HP OpenView Storage Data Protector V6.0 Zero Downtime Backup Administrator’s Guide.

The ZDB database for EVA integration is referred to as SMISDB. It keeps the information about: • Management Appliance systems on which Command View EVA runs configured in the Data Protector

cell. For each system, the following is stored: • Hostname as recognized in the IP network. • Port number through which SMI-S Agent communicates (default - 5988 SMI-S provider accepts the

SSL-based connection, the default port number is 5989). • User name and encoded password for SMI-S EVA provider login.

• Disk groups for snapclone destination. • Information about the home (CA+BC configurations). • Replicas kept on the array.

Setting the login information for Command View EVA Before starting ZDB sessions, login information for CV EVA running on the Management Appliance system must be provided. To set, delete or list the login information, use the omnidbsmis utility.

21

1. To list the current CV EVA login information enter the following at the command line on the Data

Protector Cell manager: > cd C:\program files\omniback\bin > omnidbsmis –ompasswd

2. To set the CV EVA Management Appliance login information enter the following at the command line:

> omnidbsmis –ompasswd –add <CVEVA_Server_Hostname> -port <CVEVA_SMI-S_Port>\ –namespace root/eva –user <CVEVA_Server_Unsername>

3. The omnidbsmis utility will prompt for the login password. For example, with the following CV EVA login information:

• CVEVA_Server_Hostname: sanapp02 • CVEVA_Server_Username: cvevaadmin • CVEVA_SMI-S_Port: 5988 The omnidbsmis utility would be used as follows: > omnidbsmis –ompasswd –add sanapp02 –port 5988 –namespace root/eva\ -user cvevaadmin

Creating the HP Data Protector backup specifications The next step creates the HP Data Protector backup specifications for the Oracle database backup. The following backup specifications should be created for this solution:

Specification Description

Oracle database ZDB backup specification This is the Oracle server SMB proxy-copy backup specification, which controls the flow of the entire database backup process.

Oracle archive log backup specification This is the Oracle server Archive Log backup specification, which controls the database archive log backup process.

Oracle home backup specification This is a file system backup specification, which controls the Oracle file system backup process. This backup specification should back up all files that are not part of the database and archive log backup specifications that are required for a complete disaster recovery scenario. For example, the database password and parameter files should be part of this backup. The backup can be a VMware VCB file-level backup, if desired.

22

Creating the Oracle database ZDB backup specification 1. Start the HP Data Protector Manager on the cell manager. 2. Select Backup in the navigation window, right-click Oracle Server under Backup Specifications,

and click Add Backup… (see Figure 10).

Figure 10: ZDB backup specifications

23

Create a new backup 1. In the Create New Backup window, select SMB_Proxy_Database as the Oracle Server backup

template. Select Snapshot backup for Backup type, and select HP StorageWorks EVA SMI-S for Sub type, as shown in Figure 11.

Figure 11: Create New Backup window

2. Click OK.

24

Enter the application and backup system 1. Select the Application system and Backup system. The application system is the Oracle server, and the

backup system is the server performing the offhost database backup (see Figure 12).

Figure 12: Application and backup system

2. Click Next.

25

Enter the Oracle database SID 1. Select the Oracle database SID in the Application database box (see Figure 13).

Figure 13: Select the Oracle database ID

2. Click Next.

Select database and control files 1. Select the database and control files to be backed up.

2. Click Next.

Select storage device 1. Select the devices or tape drives to be used for the backup. 2. Specify the load balance. The load balance determines how many drives can be active for a single

backup session. 3. For each device selected, go to the Device Properties window and set the backup concurrency, media

pool, and preferred host. The backup server should be the preferred host for the backup. 4. Click OK to close the properties window and save the settings (see Figure 14).

26

Figure 14: Select a storage device

5. After the backup device configuration and properties have been completed, click Next.

Set backup data protection 1. Click Advanced in the Common Application Options section, and set the desired protection for the

backup data. This setting determines how long HP Data Protector will protect the database backup from being overwritten on the backup media.

2. Click OK.

Oracle RMAN Integration: 1. Click Advanced in the Application Specific Options section, and view the Oracle RMAN script that will

be used to perform the backup. Offline backup might also be selected in this window, if desired. An offline backup will shut down the database prior to backup. Otherwise, the database is placed into backup mode prior to splitting the mirrored volumes, and then put back into normal mode after the split has completed (see Figure 15).

27

Figure 15: Application Specific Options

2. Click OK to save the settings and close the window. 3. Click Next.

28

Note: It is important to observe the OB2DMAP setting of the RMAN script. For a proxy-copy backup, the OB2DMAP setting controls the number of concurrent streams to be sent from Oracle to backup devices. The value of OB2DMAP should be equal to the number of drives being used for backup, multiplied by the concurrency.

For example, if two drives are used for backup and each drive has a concurrency of two, then OB2DMAP should be set to four. The RMAN script cannot be edited while creating the backup specification. To edit the RMAN script, after saving the backup specification, go to the backup specification properties and click the Options tab. From there, click Advanced in the Application Specific Options section, and edit the RMAN script.

Set schedule and save the backup specification 1. In the next window, a schedule can be set to automate when backups are performed. Set the schedule

as desired, and click Next. 2. In the next window, the backup specification should be saved. Enter a meaningful name, and save the

specification. The Oracle database ZDB backup specification is now complete and can be used to back up the database.

Creating the Oracle archive log backup specification Each Oracle database environment has unique requirements for archive logs and archive log backups. These steps are an example of setting up archive log backups.

1. In the HP Data Protector Manger Backup window, right-click Oracle Server under the Backup Specifications section, and select Add Backup.

2. In the Create New Backup window, select Archive as the Oracle Server backup template. Select Local or network backup as the backup type.

3. Click OK. 4. Select the Application system (Oracle server), the Oracle database SID, and then click Next. 5. In the backup source selection window, select ARCHIVELOGS, and then click Next to continue. 6. Select the tape devices to be used for backup. The properties of the tape devices can be configured as

they were in the Oracle database ZDB backup specification.

7. Click Next. 8. In the backup options window, set the desired protection for the backup data, as was done in the

Oracle database ZDB backup specification, and then click Next to continue.

9. Set the desired backup schedule, and then click Next to continue. 10. Save the backup specification with a meaningful name.

Creating the Oracle home backup specification The Oracle home backup specification is created the same as any file system backup specification.

29

Note: If VMware VCB is used for the Oracle home backup specification, follow the HP Data Protector documentation for creating a VCB backup specification.

Create the backup specification as follows:

1. In the HP Data Protector Manger Backup window, right-click Filesystem under the Backup Specifications section, and click Add Backup….

2. In the Create New Backup window, select Blank Filesystem Backup as the backup template. The backup type should be Local or network backup.

3. Click OK. 4. Select the desired file system or files for backup. This should include all Oracle files that will be needed

for recovery that are not part of the database and archive log backups. 5. Click Next. 6. Select the tape devices to be used for backup. The properties of the tape devices can be configured as

they were in the Oracle database ZDB backup specification. 7. Click Next. 8. In the backup options window set the desired protection for the backup data as was done in the Oracle

database ZDB backup specification, then click Next. 9. Set the desired backup schedule, and click Next. 10. Save the backup specification with a meaningful name.

Running the HP Data Protector backup specifications for a ZDB of the database A backup can be initiated manually or through the backup specification schedules. HP recommends testing the backup manually prior to using the automated schedules.

30

Running the backup manually 1. To activate the database backup manually, right-click one of the backup specifications that has already

been created, and select Start Backup (see Figure 16).

Figure 16: Starting a backup manually

2. The backup specifications can be run simultaneously; however, there could be contention for tape

devices, file systems, database, and so on, so it is recommended to run the backup specifications one at a time.

3. To follow the backup progress, use the HP Data Protector Manager GUI. When backups are initiated, the progress is sent to the Backup window. The Monitor window can also be used by selecting the current session associated with the backup.

Automating the backup The HP Data Protector backup specification schedules should be created when backup specifications are created (see Creating the Oracle database ZDB backup specification). Using the schedules, backups are set to run at a specific time on a recurring basis, depending on business requirements.

31

Oracle database restore and recovery The process of recovering the database consists of:

• Identifying and preparing resources—prior to recovery, know the recovery location. Ensure that all the required tape drives and media are available for recovery.

• Preparing the database for recovery—the database must be put into the proper mode for recovery. The proper mode depends on the nature of the failure.

• Restoring needed files: • All data files that belong to the tablespaces being restored • Any archived redo logs needed to make restored files current • One copy of the control file, if it was damaged • The parameter file, if different than the current file • The Oracle password file, if it was damaged

• Recovering the database and applying redo logs—this step depends on the nature of the failure and whether the database needs to be online during recovery. Oracle provides methods for performing data file recovery, tablespace recovery, and database recovery. Consult the Oracle documentation for more information on these functions.

Note: VMware does not support SAN tape devices. For this solution, when restoring the Oracle database directly to the Oracle database server the restores will occur over the LAN using the backup server as the HP Data Protector media host.

Note: See the HP OpenView Storage Data Protector ZDB integration guide for detailed instructions on restoring the database data files, control file and archive logs from a backup.

32

Glossary

application server The Oracle database server.

backup server The offhost that does data backups from the BC volumes to tape.

disk group Physical disks in an EVA are allocated into pools with common protection levels. These pools are called Disk Groups.

NPIV N_Port ID Virtualization. A Fibre Channel facility allowing multiple N_Port IDs to share a single physical N_Port.

RDM Raw device mappings. A process used to map a raw device to a virtual machine.

snapclone An independent, point-in-time copy of an EVA virtual disk. All data on the virtual disk is copied to the snapclone.

snapshot A dependent, point-in-time copy of an EVA virtual disk. Data is not actually copied to the snapshot until it is overwritten on the source.

Vdisk Another name for virtual disk.

virtual disk Simulated disk drives within an EVA physical disk group created as storage accessible by selected hosts.

VMware Oracle server The Oracle database server.

vsnap A snapshot for which no storage space is pre-allocated.

33

For more information HP StorageWorks Enterprise Backup Solutions (EBS) are fully certified and supported data protection solutions—from entry-level workgroups to enterprise-level datacenters. To learn more about HP StorageWorks EBS, go to http://www.hp.com/go/ebs.

Related documentation For proper disk array setup and configuration, the following HP StorageWorks EVA disk array documents are available at http://www.hp.com/bizsupport (click on Manuals->Storage Software and then select your product):

• HP StorageWorks Command View EVA User Guide • HP StorageWorks Command View EVA 8.0.2 release notes • HP StorageWorks Command View EVA installation guide

For proper installation and configuration of HP OpenView Storage Data Protector, the following documents are available at http://www.hp.com/go/dataprotector:

• HP OpenView Storage Data Protector V6.0 Installation and Licensing Guide • HP OpenView Storage Data Protector V6.0 Zero Downtime Backup Administrator’s Guide • HP OpenView Storage Data Protector V6.0 Integration Guide for Oracle and SAP • HP OpenView Storage Data Protector V6.0 Zero Downtime Backup Integration Guide for Oracle, SAP

R/3, Microsoft SQL Server, Microsoft Exchange Server, and Microsoft Volume Shadow Copy Service

For information about compatibility and implementation, the following documents are available on the EBS Website: http://www.hp.com/go/ebs:

• HP StorageWorks Enterprise Backup Solution Hardware/Software Compatibility Matrix • HP StorageWorks Enterprise Backup Solution Design Guide • HP StorageWorks EBS with Data Protector Implementation Guide • HP StorageWorks Enterprise Backup Solution Example Configurations

For VMware Infrastructure and virtual machine administration documentation, see the VMware Website: http://www.vmware.com/support/pubs/vi_pubs.html.

To read the entire Oracle Metalink Note 249212.1, see metalink.oracle.com.

34

Other HP Websites Other HP Websites For additional information, see the following HP Websites: For additional information, see the following HP Websites:

http://www.hp.com

http://www.hp.com

http://www.hp.com/go/storage

http://www.hp.com/service_locator

http://www.docs.hp.com

http://www.hp.com/go/vmware

http://www.hp.com/go/hpcft

Technology for better business outcomes

© Copyright 2009 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 Corporation and/or its affiliates. Linux is a U.S. registered trademark of Linus Torvalds. Microsoft and Windows are U.S. registered trademarks of Microsoft Corporation. UNIX is a registered trademark of The Open Group.

4AA2-4706ENW, Version 1.2, June 2009

35