HP 3PAR Recovery Manager Software for Oracle

Transcription

1 HP 3PAR Recovery Manager Software for Oracle User Guide Abstract This document provides the information needed to install, configure, and use the HP 3PAR Recovery Manager Software for Oracle on Solaris, Red Hat Linux, Oracle Linux, HP UX and IBM AIX. This document is for system administrators and database administrators who are responsible for backing up databases and who understand Sun Solaris and/or Linux and/or HP UX and/or IBM AIX, and are familiar with the Oracle10g, Oracle11g, and Oracle12C Databases. HP Part Number: QL Published: October 2014

2 Copyright 2014 Hewlett-Packard Development Company, L.P. Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR and , Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license. 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. Acknowledgements Intel, Itanium, Pentium, Intel Inside, and the Intel Inside logo are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States and other countries. Microsoft, Windows, Windows 2000, and Windows NT are either registered trademarks or trademarks of Microsoft Corporation. Java and Oracle are registered trademarks of Oracle and/or its affiliates. UNIX is a registered trademark of The Open Group. All other trademarks and registered trademarks are owned by their respective owners.

3 Contents 1 Overview of Recovery Manager Operations...7 Virtual Copies...7 About the Recovery Manager for Oracle Repository...7 Interacting with Oracle...8 Interacting with Symantec NetBackup, HP Data Protector and Oracle RMAN...9 Recovery Manager for Oracle Utilities...10 The Database Configuration Utility...10 The Virtual Copy Creation Utility...11 The Virtual Copy Display Utility...12 The Virtual Copy Mount Utility...13 The Virtual Copy Unmount Utility...14 The Virtual Copy Export Utility...14 The Database Cloning Utility...15 The Cloned Database Removal Utility...15 The Virtual Copy Removal Utility...16 Integration with HP 3PAR Virtual Lock Software...16 The Virtual Copy Repository...16 The Virtual Copy Repository Removal Utility...16 Virtual Copy Policy...17 Database Rollback from a Virtual Copy...17 The Database Rollback Utility...17 Recovery Manager for Oracle and Third-Party Backup Tools...18 The Database Backup Utility...18 Client-side Backup...19 Server-side Backup...20 The Database Restoration Utility...21 Recovery Manager for Oracle with Oracle Standby Database...22 Recovery Manager for Oracle and Autonomic Groups...23 Recovery Manager for Oracle and Domain Sets...23 Recovery Manager for Oracle and Host Sets...23 Recovery Manager for Oracle and Virtual Volume Sets...23 Recovery Manager for Oracle with Remote Copy...23 Recovery Manager for Oracle and Peer Motion...24 Preparing Recovery Manager for Oracle for Peer Motion Data Migration...24 Recovery Manager for Oracle and Fat-to-Thin and Thin-to-Fat...24 Converting Virtual Volumes...24 Running Recovery Manager for Oracle on Japanese OS Installing and Uninstalling Recovery Manager...26 Referencing the Support Matrix...26 Preinstallation Requirements...26 Installing Recovery Manager for Oracle on Linux Systems...29 Installation...29 Verifying Installation...31 Removing Recovery Manager from Linux Systems...32 Installing Recovery Manager for Oracle on Solaris Systems...32 Installation...32 Verifying Installation...33 Removing Recovery Manager from Solaris Systems...33 Installing Recovery Manager for Oracle on HP UX Systems...34 Installation...34 Verifying Installation...35 Contents 3

4 Removing Recovery Manager from HP UX Systems...35 Installing Recovery Manager for Oracle on IBM AIX Systems...35 Installation...35 Verifying Installation...37 Removing Recovery Manager from IBM AIX Systems Configuring Recovery Manager for Oracle...40 Setting Up SSH Connections for Recovery Manager...40 SSH Restrictions...41 Modifying the SSH Daemon Configuration...41 Generating an SSH Key Pair for the Backup Server...42 Generating an SSH Key Pair for the Database Server...42 Setting Up Connections from the Backup Server to the Database Server...43 Verifying Connections from the Backup Server to the Database Server...43 Setting Up Connections from the Backup Server to the NetBackup Master Server...44 Verifying Connections from the Backup Server to the NetBackup Master Server...44 Setting Up Connections from the Backup Server to the HP 3PAR StoreServ Storage...44 Verifying Connections from the Backup Server to the HP 3PAR StoreServ Storage...45 Setting Connections from the Database Server to the HP 3PAR StoreServ Storage...46 Verifying Connections from the Database Server to the HP 3PAR StoreServ Storage...47 Setting up National Language Host Support...48 Setting up Manual Pages on Database and Backup Servers...48 Setting up a Search Path on Database and Backup Servers...48 Creating an RMAN Recovery Catalog...53 Setting Up NetBackup Policies for NBU (User-Managed) Backup...50 Configuring the NetBackup Policy for Database Backup...50 Configuring the NetBackup Policy for Archive Log Backup...51 Setting Up NetBackup Configuration Parameters for the Backup Server...51 Setting Up NetBackup Configuration Parameters for the Database Server...51 Setting Up NetBackup Policies for Oracle RMAN Backup...52 Configuring the NetBackup Policy for Database Backup with RMAN...52 Configuring the NetBackup Policy for Archive Log Backup...53 Creating an RMAN Recovery Catalog...53 Configure RMAN Recovery Catalog...55 Setting Up HP Data Protector Backup...55 Enable Recovery Manager for Oracle Feature for HP Data Protector...55 Configuring Oracle Operating System User Account (Oracle Owner Account)...56 Create HP Data Protector Oracle backup specification...56 Modify HP Data Protector RMAN script...58 Configuring TNS Naming Service on Recovery Manager for Oracle Backup Server...59 Recovery Manager for Oracle Configuration Files...60 Creating a Recovery Manager for Oracle Configuration File without Remote Copy...60 Creating Configuration Files Using the Command Line Interface on the Backup Server...60 Creating a Recovery Manager for Oracle Configuration File using the GUI on the backup server...64 Creating a Recovery Manager for Oracle Configuration File for Remote Copy Configuration...65 Creating a Recovery Manager for Oracle Configuration File Using the Command Line Interface...65 Creating a Recovery Manager for Oracle Configuration File using the GUI Using the Recovery Manager Command Line Interface...69 Recovery Manager Commands...69 rmora_backup...69 rmora_checkconfig...74 rmora_chown...74 rmora_config Contents

5 rmora_create...79 rmora_createdb...83 rmora_display...85 rmora_export...87 rmora_mount...89 rmora_remove...91 rmora_removedb...92 rmora_restore...93 rmora_rmrep...96 rmora_rollback...97 rmora_rsync...99 rmora_set rmora_sshagent rmora_sshkeygen rmora_umount Using the Recovery Manager for Oracle Graphical User Interface Starting and Stopping the Recovery Manager for Oracle GUI Starting the GUI Stopping the GUI Creating Configuration Files Modifying Configuration Files Removing Configuration Files Configuring Creating a Virtual Copy Setting up a Time-Based Virtual Copy Policy Setting up a Numeric-Based Virtual Copy Policy Extending Virtual Copy Expiration and Retention Time Refreshing Virtual Copy Information Mounting a Virtual Copy Unmounting a Virtual Copy Rolling Back Using a Virtual Copy Viewing Rollback Status Removing a Virtual Copy Backing up a Virtual Copy Removing a Virtual Copy Repository Restoring Archive Log, Datafiles, and Tablespaces Refreshing Database Information Exporting a Virtual Copy to an Alternate Backup Server Cloning a Database Removing a Cloned Database Database Synchronization Starting Synchronization Verifying the Synchronization Process Refreshing Remote Copy Information Backing Up a Database Using the Task Manager Viewing Event Messages Viewing Online Help Using a Web Browser to Access Online Help and Event Messages Additional Information about the Recovery Manager for Oracle GUI RAC Databases Standby Databases Using the Recovery Manager Rollback Utility rmora_rollback Usage Contents 5

6 Rollback Using a Database Read-Only Virtual Copy Rollback Using a Database Read-Write Virtual Copy Database Recovery after Rollback Using Remote Copy with Recovery Manager Overview Recovery Manager for Oracle s Remote Copy Requirements How Remote Copy Works Creating Virtual Copies Support and Other Resources Contacting HP HP 3PAR documentation Typographic conventions HP 3PAR branding information Documentation feedback A Case Study: Remote Copy with Recovery Manager for Oracle Introduction Systems and Software Configurations Configuration Diagram Preparing for Remote Copy Operation Recovering to the Synchronous Backup System when the Local System is Unavailable Recovering to the Asynchronous Periodic Backup System when the Local and Synchronous Backup Systems are Unavailable B Troubleshooting Index Contents

7 1 Overview of Recovery Manager Operations Recovery Manager for Oracle offers a specific data protection solution that has been enhanced to provide rapid online recovery from space-efficient online point-in-time snapshots of an Oracle database. Further, Recovery Manager for Oracle enables off-host backup of an Oracle database to tape, minimizing any impact to the production Oracle server. This chapter introduces Virtual Copy technology and describes how HP 3PAR Recovery Manager for Oracle backs up and restores Oracle databases. In this document, the following terminology is used: Database server - A host where the Oracle database is running. Backup server - A host where all HP 3PAR Recovery Manager operations are initiated. Virtual Copies A Virtual Copy is a point-in-time image of a virtual volume created using the copy-on-write technique. It is composed of a pointer to the parent virtual volume and a record of all the changes made to the parent since the Virtual Copy was created. These changes can be rolled back to reproduce the parent s earlier state. A Virtual Copy can be exported to or mounted on a server to allow regular operations such as backup or off-host processing. Within HP 3PAR Recovery Manager for Oracle, a Virtual Copy of a database is a point-in-time image of the database. It consists of Virtual Copies of the virtual volumes where the data files and/or archive logs reside. Recovery Manager can be used to create an online, offline, datafile, or archive log Virtual Copy of an Oracle database. An online or offline Virtual Copy is a point-in-time image of a database, which is taken while the database is OPEN (online) or CLOSED (offline), respectively. A datafile Virtual Copy is a point-in-time image of all database's datafiles, which is taken while the database is OPEN (online). An archive log Virtual Copy is a point-in-time image of database's archive log destination, which is taken while the database is online (OPEN). Hereinafter, the term Virtual Copy is used to refer to a Virtual Copy of a database, rather than of a virtual volume. About the Recovery Manager for Oracle Repository Information about Virtual Copies, database structures, and backup images (if backed up via Oracle RMAN and/or Symantec NetBackup or HP Data Protector) are stored in the HP 3PAR Recovery Manager for Oracle repository when a Virtual Copy is created, or when a backup operation is performed. The information in the repository is used to manage Virtual Copies and to restore from a Virtual Copy backup image. Some other Oracle-related files such as parameter files, password files, ASM metadata, and control files are also saved in the Recovery Manager repository, along with the backup image information for each Virtual Copy created. WARNING! Do not modify these repository files. The Recovery Manager for Oracle repository is located in the following directory on the backup server: /etc/3par/solutions/<db_server>.ora.<oracle_sid> Virtual Copies 7

8 where: <db_server> is the host name of the database server. <oracle_sid> is the Oracle SID of the database instance. The following example displays the location of the Recovery Manager for Oracle repository on the backup server for Oracle database instance test that is running on database server Host1. /etc/3par/solutions/host1.ora.test If the database is a Real Application Cluster (RAC) database, there will be multiple repositories, one for each RAC instance. NOTE: For more information about using the utility to manage the repository, refer to The Virtual Copy Repository (page 16). Interacting with Oracle HP 3PAR Recovery Manager for Oracle interacts with Oracle database through the SQL*Plus utility to perform the following: Retrieve database structure information in order to create Virtual Copy for the database. Interact with the Oracle database (putting database in backup mode, stopping redo applied process or performing database log switching), as necessary, to create a consistent Virtual Copy. NOTE: Recovery Manager for Oracle supports only Oracle Enterprise Edition. It does not support Oracle Standard Edition. For more information, refer to Oracle documentation. To create a consistent Virtual Copy of an Oracle database, the database structure must satisfy the following requirements: The database must be running in archive log mode and automatic archiving must be enabled to create an online Virtual Copy, datafile Virtual Copy, or archive log Virtual Copy. Datafiles and archive logs must reside on separate HP 3PAR virtual volumes. The online redo logs and control files should not reside on the virtual volumes used by the datafiles and archive logs to avoid being rolled back along with datafiles and archive logs virtual volumes. However, the online redo logs and control files can share the same HP 3PAR virtual volumes. If the database files reside on Symantec VxVM volumes, datafiles and archive logs must reside on separate VxVM disk groups. The online redo logs and control files should reside on separate VxVM volumes used by the datafiles and archive logs. If the Oracle database is an ASM managed database, the datafiles and archive logs must reside on separate ASM disk groups. The online redo logs and control files should not reside on the same ASM disk groups used by the datafiles and archive logs to avoid being rolled back when using the Recovery Manager Rollback feature. ASM disk groups should not be shared between different databases. If using Logical Volume Manager (LVM) on HP, Linux, or AIX, the Oracle datafiles and archive logs must reside on separate LVM volume groups. In addition, online redo logs and control files must not reside on LVM volume groups that are used by Oracle datafiles and archive logs. However, the online redo logs and control files can reside on the same LVM volume group. If the database is an RAC database, all RAC instances must share the same archive log destinations (same cluster file systems or same ASM disk groups). 8 Overview of Recovery Manager Operations

9 To ensure that the database is running in automatic archive log mode, use SQL*Plus utility to ensure the Database log mode is Archive Mode and that Automatic archival is Enabled, as in the following example: $ sqlplus "/as sysdba" SQL*Plus: Release Production on Wed Nov 14 13:59: Copyright (c) 1982, 2002, Oracle Corporation. All rights reserved. Connected to: Oracle9i Enterprise Edition Release bit Production With the Partitioning, Real Application Clusters, OLAP and Oracle Data Mining options JServer Release Production SQL> archive log list Database log mode Archive Mode Automatic archival Enabled Archive destination /rac9i_db/rac9i_arch2 Oldest online log sequence 764 Next log sequence to archive 764 Current log sequence 765 Oracle standby databases are supported. An Oracle standby database is a synchronized copy of the production database. To support Oracle standby databases, you need the following: Oracle 10g or 11g is supported. A standby database must be a physical database. Logical or snapshot standby databases are not supported. If using RMAN backup, the primary database (not standby) must be registered with Oracle Recovery Catalog. A snapshot of a standby database can be used to promote standby database volumes, but cannot be used to promote primary database volumes (even though a backup of the snapshot can be used to restore the primary database). Oracle parameter and control files are not compatible between the standby and primary databases. They cannot be used to restore the primary database unless Oracle RMAN (11g) is used. The Oracle parameter and control files of the primary database must be backed up manually outside of Recovery Manager for Oracle. Interacting with Symantec NetBackup, HP Data Protector and Oracle RMAN HP 3PAR Recovery Manager for Oracle integrates HP 3PAR Virtual Copy with Symantec NetBackup (NBU) or HP Data Protector and Oracle RMAN to dramatically reduce the performance impact on the database server, as well as to minimize database down time during backup. Instead of a traditional backup where the database is backed up directly on the production server, Recovery Manager for Oracle creates a Virtual Copy (snapshot) of the database, imports it to a secondary host (backup server), and then performs the backup of the Virtual Copy on the backup server. Recovery Manager for Oracle provides four ways to perform backup and restoration: Symantec NetBackup (NBU), Oracle RMAN (to local disk), Oracle RMAN With Symantec NetBackup, and Oracle RMAN with HP Data Protector. NOTE: For an ASM managed database, Oracle RMAN with or without Symantec NetBackup or HP Data Protector are supported backup methods. NOTE: Recovery Manager for Oracle supports only Symantec NetBackup master server on UNIX (or linux) platforms. Recovery Manager for Oracle does not support the master server on Windows platforms. Interacting with Symantec NetBackup, HP Data Protector and Oracle RMAN 9

10 For NBU backup and restoration, Recovery Manager for Oracle interacts directly with NBU to trigger the backup or restore process. Recovery Manager for Oracle requires that the NBU client must be installed on the database server and the backup server. For HP Data Protector backup and restoration, Recovery Manager for Oracle interacts directly with HP Data Protector to trigger the backup or restore process. HP Data Protector client with Oracle Integration Agent and User Interface components must be installed on the database servers and backup server. For Oracle RMAN backup, Recovery Manager for Oracle supports backup to tape and backup to local disk. If Recovery Manager is configured to perform backup to local disk, Recovery Manager for Oracle interacts with Oracle RMAN to trigger the backup process. If Recovery Manager for Oracle is configured to perform backup to tape, Recovery Manager for Oracle interacts with Oracle RMAN, which in turn interacts with either NBU or HP Data Protector to trigger the backup or restore process. Recovery Manager for Oracle requires that Oracle database software (Oracle RMAN) and Symantec NetBackup Client or HP Data Protector Client must be installed on the database server and the backup server. Additionally, Symantec NetBackup for Oracle (Oracle Agent) or HP Data Protector Oracle Integration component must be installed on the database server, backup server, and NetBackup master server, if you select to backup to tape. Recovery Manager for Oracle requires that at least one NBU policy or HP Data Protector backup specification must be created per database. Optionally, a separate NBU policy or HP Data Protector backup specification can be created for archive log backup (backup archive log only). The NBU policies must be created as "standard" type or "Oracle" type for NBU (user-managed) backup/restore or Oracle RMAN backup/restore, respectively. The HP Data Protector backup specifications must be created as an Oracle backup specification. See, Setting Up NetBackup Policies for NBU (User-Managed) Backup (page 50) or Setting Up NetBackup Policies for Oracle RMAN Backup (page 52) or Create HP Data Protector Oracle backup specification (page 56) for detail information). Recovery Manager for Oracle Utilities Read this section for general information regarding HP 3PAR Recovery Manager for Oracle utilities available through the Recovery Manager for Oracle command line interface and graphical user interface. The Database Configuration Utility The database configuration utility (rmora_config) of HP 3PAR Recovery Manager for Oracle creates a Recovery Manager for Oracle configuration file for each database. All operations that are available from Recovery Manager for Oracle require this configuration file. After the Recovery Manager for Oracle configuration file is created for a database, it is stored at: /etc/3par/solutions/<db_server>.ora.<oracle_sid>/config An equivalent environment file is also created for each configuration file. It contains all configuration options that are specified in the configuration file. Recovery Manager for Oracle uses the environment file for its operations. The environment file is also stored at the same location as the configuration file. /etc/3par/solutions/<db_server>.ora.<oracle_sid>/config_exp.sh If a configuration file of a database instance exists, it is overwritten. The permission of the configuration file is set to the user that created the file. To check the configuration on a specific database, use the rmora_checkconfig command. Resolve any issues before you create Virtual Copies. 10 Overview of Recovery Manager Operations

11 The Virtual Copy Creation Utility The Virtual Copy creation utility (rmora_create command) of HP 3PAR Recovery Manager Software for Oracle creates an online, offline, datafile, or archive log Virtual Copy of an Oracle database. Online or offline Virtual Copy - A point-in-time snapshot image of a database while it is OPEN (online) or CLOSED (offline). Archive log Virtual Copy - A snapshot image of the archive log destination of a database while it is online (OPEN). Datafile Virtual Copy - A point-in-time snapshot image of the datafiles of a database while it is online (OPEN). A datafile Virtual Copy alone cannot be used for recovery without the archive logs generated up to the point when the Virtual Copy is taken. Ensure that all required archive logs exist. After creating the Virtual Copy, it can be mounted on the backup server for off-host processing purposes such as backup and database cloning. A database Virtual Copy consists of multiple Virtual Copies of underlying HP 3PAR virtual volumes used by Oracle datafiles, archive log destination, or both, depending on which option is specified (online, offline, datafile, or archlog). An archive log Virtual Copy can be used in conjunction with online or offline Virtual Copy to simulate an incremental backup. If Recovery Manager for Oracle is configured to use Oracle RMAN for backup, an RMAN Recovery Catalog must be created and configured prior to running the create utility. The Recovery Manager create utility performs Recovery Catalog synchronization during the Virtual Copy creation process. When creating an online Virtual Copy, the create utility performs the following actions: Discovers devices (HP 3PAR virtual volumes) used by the datafiles and archive log destination. Puts the database in backup mode. Creates a Virtual Copy for the datafile virtual volumes. Takes the database out of backup mode. Switches online redo logs and archives them to archive log destination. Re-synchronizes the Recovery Catalog to update with newly generated archive logs if the Virtual Copy is to be backed up using Oracle RMAN. Creates a Virtual Copy for the archive log destination virtual volumes. A datafile Virtual Copy is created while the database is OPEN. The create utility performs the following actions: Discovers devices (HP 3PAR virtual volumes) used by the datafiles. Puts the database in backup mode. Creates a Virtual Copy for the datafile virtual volumes. Takes the database out of backup mode. An offline Virtual Copy is created while the database is CLOSED. The create utility performs the following actions: Starts up the database in MOUNTED mode to retrieve a list of datafiles and shuts down the database. Discovers devices (HP 3PAR virtual volumes) used by the datafiles. Creates a Virtual Copy for the datafile virtual volumes. Recovery Manager for Oracle Utilities 11

12 An archive log Virtual Copy is created while the database is OPEN and performs the following actions: Discovers devices (HP 3PAR virtual volumes) used by the archive log destination. Switches logs and archives online redo logs to archive log destination. Re-synchronizes the Recovery Catalog to update with newly generated archive logs if the Virtual Copy is to be backed up using Oracle RMAN. Creates a Virtual Copy for the archive log destination virtual volumes. NOTE: If the Virtual Copy is to be backed up using Oracle RMAN, a Recovery Catalog must be created and configured prior to running this utility. For an RAC database, archive log destinations of all RAC instances must be on shared storage (same cluster file systems or same ASM disk groups). The Virtual Copy Display Utility The Virtual Copy utility (rmora_display) of HP 3PAR Recovery Manager Software for Oracle displays database Virtual Copies along with other information including creation time, type, status, and backup status. For systems running HP 3PAR OS and later, the rmora_display utility also provides the option to display the retention times and expiration times of the Virtual Copy. A type of Virtual Copy can be either Online, Offline, Datafile, or Archlog. An Online Virtual Copy indicates that the Virtual Copy for the database is created while it is OPEN (online). An Offline Virtual Copy indicates that the Virtual Copy for the database is created while it is CLOSED (offline). A Datafile Virtual Copy indicates that the Virtual Copy for the database is created while it is OPEN (online) and contains only datafiles (no archive log destination). An Archlog Virtual Copy indicates that the Virtual Copy is created for archive log destination only. The status of a Virtual Copy can be either Available, Available(P), Orphaned, Removed, Mounted, Mounted(P), Database, or Stale. Available status indicates that the Virtual Copy exists and is not currently mounted or cloned. Available(P) status indicates that one or more virtual volumes of the Virtual Copy are missing. Removed status indicates that the Virtual Copy is removed. Mounted status indicates that the Virtual Copy is currently mounted. Mounted(P) status indicates that the Virtual Copy is partially mounted. NOTE: To remount the Virtual Copy, use the rmora_mount command with the r option. To change the Virtual Copy status to Available, use the rmora_umount command. Database status indicates that a database is cloned using the Virtual Copy. An Orphaned status indicates the current database volumes are no longer the parents of the Virtual Copy volumes. A Stale status indicates that one or more virtual volumes of the database Virtual Copy are stale. The backup status of a Virtual Copy can be either Y or N, where Y indicates that the Virtual Copy is backed up and N indicates that the Virtual Copy is not backed up. 12 Overview of Recovery Manager Operations

13 The Virtual Copy Mount Utility The Virtual Copy mount utility of HP 3PAR Recovery Manager Software for Oracle mounts an existing database Virtual Copy that is created using the create utility on the backup server using the rmora_mount command. The mounted Virtual Copy can be used for off-host processing purposes such as backup or database cloning. The following restrictions apply when mounting a database Virtual Copy: The Virtual Copy must have an Available or Mounted(P) status in order to be mounted. The Virtual Copy's status can be retrieved using the Recovery Manager for Oracle display utility. The same Virtual Copy cannot be mounted concurrently at different mount points. If the database files reside on Symantec VxVM Volumes, only one Virtual Copy per database can be mounted at any time on the backup server. This is due to the VxVM disk groups from different Virtual Copies of the same database having the same names and so cannot be imported at the same time. If Oracle datafiles and archive logs reside on LVM logical volumes, HP 3PAR Recovery Manager for Oracle allows only one Virtual Copy of the same database to be mounted. You must unmount a mounted Virtual Copy before mounting a different Virtual Copy. If the database files reside on ASM disk groups, it is dependent on which ASM database version is installed on the backup server, different restrictions apply as follows: If the ASM version on the backup server is or and later, one Virtual Copy per database can be mounted at any time on the backup server. However, Virtual Copies from different databases can be mounted concurrently. If the ASM version on the backup server is earlier than the or , only one Virtual Copy can be mounted at any time on the backup server. This restriction prevents an Oracle ASM instance on the backup server from hanging due to some ASM's idle processes still holding a Virtual Copy's devices, even though the corresponding ASM disk groups are dropped. NOTE: The ASM version on the backup server must be equal or higher than the ASM version on the database server. On Linux systems, if the database files reside on OCFS or above file systems, Recovery Manager for Oracle supports multiple Virtual Copies per database being mounted at the same time. For versions lower than OCFS , only one Virtual Copy per database can be mounted at any time on the backup server. Mounting a database Virtual Copy involves the following actions: A read-write Virtual Copy of the original (read-only) Virtual Copy is created. The read-write Virtual Copy is imported to the backup server. Snapshots of Symantec VxVM disk groups are imported and all corresponding snapshot VxVM volumes are started if the database files reside on VxVM volumes. Snapshots of LVM volume groups are imported and all corresponding LVM snapshot volumes are activated if the database files reside on LVM logical volumes. All snapshot file systems are mounted if the database files reside on file systems. For Virtual Copies from an ASM-managed database, based on the different ASM database releases on the backup server, the operation is different. For ASM versions or and later, if an ASM instance exists and is up on the backup server, then all diskgroups from the Virtual Copy are mounted in this ASM Recovery Manager for Oracle Utilities 13

14 instance. If no ASM instance is up on the backup server, an ASM instance is started up on the backup server, and all ASM disk groups in the Virtual Copy are mounted. For ASM versions earlier than or , if an ASM instance is up on the backup server, the mount utility checks if there is any mounted diskgroup. If there is no mounted diskgroup, the ASM instance is shut down, otherwise, the mount utility gives an error and exits. If there are no errors, a new ASM instance is started up and all diskgroups contained in the current Virtual Copy are mounted. The Virtual Copy Unmount Utility The Virtual Copy unmount utility (rmora_umount) of HP 3PAR Recovery Manager Software for Oracle unmounts the file system where a Virtual Copy is currently mounted, or drops ASM disk groups if ASM is used. The read-write Virtual Copy is removed, as well as any components that are created during the mount Virtual Copy stage. The Virtual Copy must have Mounted or Mounted(P) status in order to be unmounted. The status of a Virtual Copy can be obtained using a display utility such as the rmora_display command. Unmounting a database Virtual Copy involves the following actions: For an ASM-managed database, if the ASM database on the backup server has a version at or above or , unmounting the Virtual Copy drops the ASM diskgroups that are contained in the Virtual Copy and cleans up the ASM disks. If the ASM database on the backup server has versions earlier than or , unmounting shuts down the ASM instance and cleans up ASM disks. Unmounts all snapshot file systems if the database files reside on file systems. Destroys all snapshot VxVM disk groups and their VxVM volumes if the database files reside on VxVM volumes. Destroys all snapshot LVM volume groups and their logical volumes if the database files reside on LVM logical volumes. Deports the read-write Virtual Copy from the backup server. Removes the read-write Virtual Copy. NOTE: rmora_umount will remove all the changes in the cloned database. The Virtual Copy Export Utility The Virtual Copy export utility of HP 3PAR Recovery Manager Software for Oracle exports an existing Virtual Copy to an alternate backup server (rmora_export command). The exported Virtual Copy can then be mounted, backed up or cloned at the alternate backup server. The Virtual Copy must have Available status in order to be exported. An alternate backup server must have the same operating system, file system, volume manager, and Recovery Manager for Oracle version as the current backup server. Status of a Virtual Copy can be obtained using a display utility such as the rmora_display command. The following restrictions apply to exporting Virtual Copies: If Symantec Volume Manager is used, the alternate backup server must have the same version of Symantec Volume Manager that is currently installed. The alternate backup server must be connected to the same HP 3PAR StoreServ Storage system as the current backup server. SSH must be configured to access the alternate backup server, the NetBackup master server, and any other related servers, from the current backup server without prompting for a pass phrase. For more information, see Setting Up SSH Connections for Recovery Manager (page 40). 14 Overview of Recovery Manager Operations

15 Once exported, the Virtual Copy on the alternate backup server can be mounted, unmounted, backed up, and restored. Once the exported Virtual Copy is no longer needed, its repository can be removed from the alternate backup server. The Database Cloning Utility The database cloning utility (rmora_createdb command) of HP 3PAR Recovery Manager Software for Oracle creates a single-instance database, or starts up a cloned database in MOUNTED mode for backup (RMAN) purposes. A single-instance database can be used for any off-host processing purpose. A cloned database that is started in MOUNTED mode, can be used for RMAN backup. The Virtual Copy used for cloning a database must be either an online or offline Virtual Copy (created using the rmora_create or rmora_rsync command). The Virtual Copy must have been mounted using the rmora_mount command prior to running this command. A clone database can be created using an ASCII or binary control file which was saved in the Recovery Manager for Oracle repository at the time the Virtual Copy was created. Using an ASCII control file is more flexible as it allows you to change database instance name as well as the structure of the database. When using an ASCII control file: The structure of the clone database is not required to be exactly the same as the structure of the original database. Therefore the Virtual Copy can be mounted at any mount point. Because the Virtual Copy does not contain online redo logs and control files, their locations can be specified using the -d option (can be one or more directories or ASM diskgroups, depending on the desired multiplexing). The number of multiplex redo log locations must be equal to, or less than, the original database when creating the clone database. Otherwise, the extra redo log multiplex location will be ignored. If the locations of the redo logs and control files are not specified, they will be created at the repository location for the Virtual Copy (/etc/3par/solutions/<host>.ora.<sid>/<vc_name>). When using a binary control file: The structure of the clone database must be exactly the same as the structure of the original database. Therefore, the Virtual Copy must be mounted at '/' if the datafiles and archive logs are on file systems. Because the Virtual Copy does not contain redo logs and control files, the same directory structure or same ASM diskgroups for the redo logs and control files must be pre-created on the backup server. When creating a clone database for backup (RMAN) purposes, the database is started in MOUNTED mode using the binary control file from the repository without recovering the database. This can be achieved by using the -o for_backup or -o binary,norecovery option. A clone database can be created with or without automatic recovery (applying archivelogs from the Virtual Copy) using the o recovery or -o norecovery option. If recovery is chosen, the clone database is open with a resetlogs. If no recovery is chosen, the clone database is mounted and archive logs from the Virtual Copy are not applied. The Cloned Database Removal Utility HP 3PAR Recovery Manager Software for Oracle s cloned database removal utility (rmora_removedb command) removes a cloned database, which was created using the rmora_createdb command. Recovery Manager for Oracle Utilities 15

16 The cloned database is shutdown with the shutdown immediate option. The database related files (Oracle parameter file, control files and redo logs), which are previously created by the rmora_createdb command, are removed. The read-write Virtual Copy remains mounted. The Virtual Copy Removal Utility HP 3PAR Recovery Manager for Oracle s Virtual Copy removal utility removes an existing Virtual Copy from the HP 3PAR StoreServ Storage system. The Virtual Copy must have Available or Available(P) status in order to be removed using the rmora_remove command. The status of a Virtual Copy is obtained by using the display utility rmora_display. This utility only removes the read-only Virtual Copy from the system to free up the snapshot space. It does not actually remove the repository information if the Virtual Copy has been backed up to the media. This enables Recovery Manager for Oracle to restore a Virtual Copy, which has been previously backed-up to the media on the original volumes, as long as the Virtual Copy repository exists. Integration with HP 3PAR Virtual Lock Software HP 3PAR Virtual Lock Software allows administrators to apply a configurable retention period to virtual volumes - including thin volumes created with HP 3PAR Thin Provisioning Software and virtual volume copies such as those created with HP 3PAR Recovery Manager for Oracle. The Virtual Lock utilities prevent read-only Virtual Copies from being accidentally or intentionally removed. This is achieved by enforcing a predefined retention time for the read-only Virtual Copy. Be cautious that once the retention time is set, it cannot be removed or reduced. It can only be removed after the retention time ends. This feature is only available for HP 3PAR OS or later and requires an HP 3PAR Virtual Lock Software license. There are a few ways to enforce the retention time for read-only Virtual Copies. During configuration, the retention value specified will be the default value for new read-only Virtual Copies created via rmora_create, rmora_rsync, and rmora_backup (without the -t option). Use rmora_create -r or rmora_rsync -r to override the default value specified during configuration. Use the rmora_set command for the specified Virtual Copy to extend its retention time. Retention time can be displayed by using rmora_display with the -r option. The Virtual Copy Repository HP 3PAR Recovery Manager Software for Oracle records important information for each Virtual Copy taken by the Recovery Manager for Oracle utilities. The information is used by Recovery Manager for Oracle, especially for database restoration. The information is stored in the repository at: /etc/3par/solutions/<db_server>.ora.<oracle_sid>/<timestamp> To avoid unpredictable errors, do not manually modify the directories and files in this repository. The Virtual Copy Repository Removal Utility HP 3PAR Recovery Manager Software for Oracle s Virtual Copy repository removal utility removes a Virtual Copy s repository created using the create utility ( The Virtual Copy Creation Utility (page 11)). The Virtual Copy that has been removed must have Removed status in order for Recovery Manager for Oracle to remove the repository. The status of a Virtual Copy can be obtained using the display utility ( The Virtual Copy Display Utility (page 12)). 16 Overview of Recovery Manager Operations

17 If a Virtual Copy has been backed up, the remove repository utility command fails unless the -f option is used. Virtual Copy Policy HP 3PAR Recovery Manager Software for Oracle provides the capability to limit the number of Virtual Copies per database at any time. This can be achieved in two ways. One way is to use a time-based policy, which is based on the expiration time (the Virtual Copy is removed automatically by an internal scheduler once the expiration time is reached) of the Virtual Copy. The second way is to use a numeric-based policy, which is based on the maximum number of Virtual Copies specified in the configuration file (the maximum allowed value is 500). For a numeric-based policy example, a policy can be set to only allow twelve Virtual Copies at any time for a database. Recovery Manager for Oracle always maintains the twelve latest Virtual Copies by removing the oldest Virtual Copy before creating a new copy. If a Virtual Copy is protected by retention time, it can only be removed after the retention time ends. The default and maximum allowed number is 500, meaning that up to 500 read-only Virtual Copies can be created if you have sufficient snapshot space. For a time-based policy example, if the expiration time is one month (specified in the configuration file), then the Virtual Copy that reaches the expiration time will be removed from the HP 3PAR StoreServ Storage system automatically. The system has all the Virtual Copies for last month. Expiration time can be changed using the rmora_set command. Database Rollback from a Virtual Copy When a database is inconsistent, you can restore the database to the most recent database images from the most recently created Virtual Copy by using the rollback utility. The Database Rollback Utility The database rollback utility (rmora_rollback) of HP 3PAR Recovery Manager Software for Oracle promotes the volume of a Virtual Copy back to its base virtual volumes. In other words, the base virtual volumes used by the database are rolled back to the Virtual Copy volumes. Once the rollback process completes successfully, the base virtual volumes are exactly the same as the Virtual Copy volumes. If the base volume size has been changed since the Virtual Copy was taken, the rollback process will not affect the new size. When rolling back from an online Virtual Copy, both datafile and archive log virtual volumes are rolled back by default. Use the -o option to rollback only datafile virtual volumes or only archive log virtual volumes. When rolling back from an offline or datafile Virtual Copy, only datafile virtual volumes are rolled back. When rolling back from an archive log Virtual Copy, only archive log virtual volumes are rolled back. The following restrictions apply when rolling back a Virtual Copy: The online redo logs and control file should not reside on the same virtual volumes used by the datafiles and archive logs. Otherwise, they will be rolled back along with the datafile and archive log virtual volumes. The database instance must be CLOSED for this operation. If the database is an RAC database, all RAC instances must be CLOSED. The base (datafile and/or archive log) virtual volumes must be temporarily removed from the original database server. NOTE: For detailed instructions and examples for using the rollback utility, see Using the Recovery Manager Rollback Utility (page 119). Virtual Copy Policy 17

18 Recovery Manager for Oracle saves an ASCII control file and a binary control file for each created Virtual Copy in its repository. After a rollback, you may need to restore the control file in order to perform database recovery. Recovery Manager for Oracle and Third-Party Backup Tools HP 3PAR Recovery Manager Software for Oracle integrates HP 3PAR Virtual Copy Software with Symantec NetBackup (NBU), HP Data Protector and/or Oracle RMAN to perform off-host backup. Off-host backups can dramatically reduce performance impact on the database server and minimize database down time or database in backup mode during backup. Recovery Manager for Oracle creates a Virtual Copy (snapshot) of the database, mounts it to the backup server, then performs backup of the Virtual Copy. Recovery Manager for Oracle supports online (hot), offline (cold), datafile, or archive log backups. Online backup - A database backup while it is OPEN. Offline backup - A database backup while it is CLOSED. Datafile backup - A backup of datafiles only. Archive log backup - A backup of archive logs only. Recovery Manager for Oracle can be configured to perform Symantec NetBackup (user-managed) backup, Oracle RMAN, Oracle RMAN with Symantec NetBackup or Oracle RMAN with HP Data Protector backup.. The Database Backup Utility HP 3PAR Recovery Manager Software for Oracle s database backup utility supports full and/or incremental backup of an Oracle database or archive log destination. Full backup of an Oracle database or archive log destination are always supported regardless of backup method (Symantec NetBackup, Oracle RMAN, Oracle RMAN with Symantec NetBackup, or Oracle RMAN with HP Data Protector backup). However, incremental (differential or cumulative) backup of a whole Oracle database is only available using Oracle RMAN, Oracle RMAN with Symantec NetBackup, or Oracle RMAN with HP Data Protector backup. Incremental (differential or cumulative) backup of archive log destination is only available for the Symantec NetBackup (user-managed) backup method. 18 Overview of Recovery Manager Operations

19 The following restrictions apply when backing up a database using the Recovery Manager for Oracle database backup utility. For NBU (user-managed) backup: The NBU client must be installed on the backup server, as well as on the database server. At least one NBU policy of standard type must be created and configured for database backup. Optionally, a separate NBU policy of standard type can be created and configured for archive log destination backup. For Oracle RMAN, Oracle RMAN with Symantec NetBackup, or Oracle RMAN with HP Data Protector backup: An RMAN Recovery Catalog database must be created and configured prior to using the backup utility. For Oracle RMAN with Symantec NetBackup backup: The NBU for Oracle client must be installed on the backup server, as well as on the database server. At least one NBU policy of standard type must be created and configured for database backup. Optionally, a separate NBU policy of standard type can be created and configured for archive log destination backup. For Oracle RMAN with HP Data Protector backup: HP Data Protector client with Oracle Integration Agent and User Interface components must be installed on the Recovery Manager for Oracle database server and backup servers. HP recommends that HP Data Protector Cell Manager with Oracle Integration Agent and User Interface components be installed on the Recovery Manager for Oracle backup server. The Transparent Network Substrate (TNS) service name must be pre-configured for the database instance on the database server. The same Transparent Network Substrate (TNS) net service name must be pre-configured for the cloned database instance on the backup server. Oracle Home must be the same between the Recovery Manager for Oracle database server and backup server. At least one HP Data Protector Oracle backup specification must be created and configured for database backup. Optionally, a separate HP Data Protector Oracle backup specification can be created and configured for archive log backup. There are two ways to perform backups: Client-side backup - A backup that is initiated by using Recovery Manager for Oracle User Interface. Server-side backup - A backup that is initiated by using Symantec NetBackup or HP Data Protector User Interface from the Symantec NetBackup master server or HP Data Protector cell manager respectively. Client-side Backup During client-side backup, Recovery Manager for Oracle performs the following: Creates an online, offline, datafile, or archonly Virtual Copy for the database or archive log destination. Mounts the Virtual Copy on the backup server. Recovery Manager for Oracle and Third-Party Backup Tools 19

20 For NBU (user-managed) backup, Recovery Manager for Oracle: Generates an include list file that contains a list of datafiles and/or archive log destination on the mounted Virtual Copy and stores it in the /usr/openv/netbackup/include_list.<policy_name> file on the NBU client (the backup server). Calls the bpbackup command from the NBU master server to backup files listed in the include list. For Oracle RMAN with HP Data Protector, Recovery Manager for Oracle: Starts up a clone database in mounted mode using the mounted Virtual Copy on the Recovery Manager for Oracle backup server Calls HP Data Protector CLI (omnib) to initiate a backup of the clone database. Removes the cloned database. Unmounts the Virtual Copy. For Oracle RMAN and Oracle RMAN with Symantec NetBackup, Recovery Manager for Oracle: Starts up a clone database in mounted mode using the mounted Virtual Copy on the Recovery Manager for Oracle backup server. Calls an RMAN backup script (rmora_rman_dbbackup.sh or rmora_rman_archbackup.sh) to backup the cloned database. Removes the cloned database. Unmounts the Virtual Copy. NOTE: The RMAN backup scripts (rmora_rman_dbbackup.sh and rmora_rman_archbackup.sh) are generated at /etc/3par/solutions/<db_server>.ora.<oracle_sid> during the creation of the Recovery Manager Configuration file. Server-side Backup NOTE: NBU server-side backup can be used when Recovery Manager for Oracle is configured to run as either a root user or an Oracle owner. NOTE: If Recovery Manager for Oracle is configured to be run as an Oracle user and this is an upgrade from previous Recovery Manager release, the rmora_config command must be run again for each database that is configured for server-side backup. During server-side backup, Symantec NetBackup or HP Data Protector initiates a backup process on the Symantec NetBackup or HP Data Protector client (the backup server). For an NBU (user-managed) backup: The NBU client executes the bpstart_notify.<policy_name> script. The bpstart_notify script creates a Virtual Copy of the database or archive log destination, mounts it on the backup server, then generates the include list in the /usr/openv/netbackup/include_list.<policy_name> file, which contains a list of files on the Virtual Copy for backup. Once the backup process is completed, the NBU client executes the bpend_notify.<policy_name> script to perform Virtual Copy cleanup. 20 Overview of Recovery Manager Operations

21 NOTE: The bpstart_notify and bpend_notify scripts are generated at /usr/openv/netbackup/bin during the creation of the Recovery Manager Configuration file. By default, the bpstart_notify script (for database backup policy) performs an online backup. If an offline or datafile backup is desired, edit this file to set the value of BACKUP_MODE to 'offline' or 'datafile' respectively. In addition, the database must be manually shutdown for offline backup. For Oracle RMAN with HP Data Protector: HP Data Protector Cell Manager executes the DP_pre.<backup_specification> on the RMO backup server. The DP_pre.<backup_specification> script creates an online, offline, datafile or archlog virtual copy; mounts it on the RMO backup server; starts up a cloned database in MOUNTED mode; then return control to HP Data Protector. HP Data Protector executes RMAN script (defined in the HP Data Protector backup specification) to back up the cloned database. HP Data Protector executes the DP_post.<backup_specification> on the RMO backup server to clean up the cloned database and the virtual copy. NOTE: The DP_pre.<backup_specification> and DP_post.<backup_specification> are generated at /usr/omni/bin (AIX) or /opt/omni/lbin (other UNIX platforms) on the backup server during the Recovery Manager for Oracle configuration process. By default, the DP_pre.<backup_specification> creates an online Virtual Copy. If an offline or datafile Virtual Copy is desired, edit this file to set the value of BACKUP_MODE to offline or datafile respectively. For offline virtual copy, the database must be manually shutdown. For Oracle RMAN and Oracle RMAN with Symantec NetBackup: The NBU client executes the backup script rmora_nbu_dbbackup.sh or rmora_nbu_archbackup.sh, which must be specified in the Backup Selection List of the NBU policy. The backup script creates a Virtual Copy of the database or archive log destination, mounts it on the backup server, starts up a cloned database in MOUNTED mode, then calls the RMAN backup scripts (rmora_rman_dbbackup.sh or rmora_rman_archbackup.sh) to backup the cloned database. NOTE: The backup scripts (rmora_nbu_dbbackup.sh and rmora_nbu_archbackup.sh) and the RMAN backup scripts (rmora_rman_dbbackup.sh and rmora_rman_archbackup.sh) are generated at /etc/3par/solutions/<db_server>.ora.<oracle_sid> during the creation of the Recovery Manager Configuration file. By default, the rmora_nbu_dbbackup.sh script (for database backup policy) will perform an online backup. If an offline or datafile backup is desired, edit this file to set the value of BACKUP_MODE to 'offline' or 'datafile' respectively. For offline Virtual Copy, the database must be manually shutdown. If the Virtual Copy is to be backed up using Oracle RMAN, a Recovery Catalog must be created and configured prior to using the backup utility. For an RAC database, archive log destinations of all RAC instances must be on shared storage (same cluster file systems or same ASM disk groups). The Database Restoration Utility The database restoration utility of HP 3PAR Recovery Manager Software for Oracle restores databases, tablespaces, datafiles, or archive logs from a backup image of a Virtual Copy. The Virtual Copy must be previously backed up using the rmora_backup command. The Virtual Copy must have a backup status of Y in order to be restored. The backup status of a Virtual Copy can Recovery Manager for Oracle and Third-Party Backup Tools 21

22 be retrieved using the Recovery Manager display utility (see The Virtual Copy Display Utility (page 12)). For an NetBackup (user-managed) restoration, the database restoration utility can be used to restore a backup image of a Virtual Copy to the backup server, and it can also be used to restore to an alternate server on an alternate mount point. For an Oracle RMAN restoration, the backup image is always restored to the database server. The following restrictions apply when restoring from a backup image of a Virtual Copy: When restoring the database control file (using the -c option) using Oracle RMAN, the database must be in STARTED mode (startup nomount). In addition, restoring the database control file along with the individual datafile or tablespace is not supported as it is not possible to perform media recovery. When restoring a database, the database must be in CLOSED or MOUNTED mode for NBU restore or Oracle RMAN restore, respectively. For an RAC database, all RAC instances must be in CLOSED or MOUNTED mode, respectively. When restoring individual tablespaces or datafiles, the database can be OPEN, but the corresponding tablespaces must be offline. If the database is an ASM managed database, all ASM disk groups must be mounted prior to running the restore utility. For an NBU (user-managed) restoration, the /usr/openv/netbackup/db/altnames/<database_hostname virtual _hostname> file must be created on the NBU master server prior to running the restore utility, where <database_hostname virtual_hostname> is the host name of the database server. Depending on the type (online, offline, datafile, or archive log) of backup image of the Virtual Copy, corresponding database files are restored appropriately. For an NBU (user-managed) restoration: Control files are not restored by default. For an online Virtual Copy, both datafiles and archive logs are restored unless individual tablespaces or datafiles are being specified. In this case, only the corresponding datafiles are restored. Only datafiles are restored for an offline or datafile Virtual Copy. Only archive logs are restored for an archive log Virtual Copy. For an Oracle RMAN restoration: Control files are not restored by default. For an online Virtual Copy, only datafiles are restored. Archive logs are not restored to minimize restore time as Oracle RMAN can restore only necessary archive logs during recovery. Only datafiles are restored for an offline or datafile Virtual Copy. Restoring from an archive log Virtual Copy backup image is not supported as Oracle RMAN can restore necessary archive logs during recovery. Recovery Manager for Oracle with Oracle Standby Database All HP 3PAR Recovery Manager Software for Oracle s utilities can be run against an Oracle physical standby database instead of the production database. This completely eliminates the performance impact on the production database. 22 Overview of Recovery Manager Operations

23 In addition to the current Recovery Manager for Oracle s limitations and restrictions when running against an Oracle primary database, the following limitations and restrictions apply when running against an Oracle physical standby database: Only Oracle 10g and 11g are supported. A standby database must be a physical standby database. Logical and snapshot standby databases are not supported. If using Oracle RMAN for backup, the primary database, and not the standby database, must be registered with Oracle Recovery Catalog. A snapshot of a standby database can be used to promote back to the standby database volumes, but it cannot be used to promote back to the primary database volumes. Oracle parameter file and control file are not compatible between the standby database and the primary database. They cannot be used to restore to the primary database unless Oracle RMAN (11g) is used for restoring. This means that the Oracle parameter file and control file of the primary database must be backed up manually outside of the Recovery Manager for Oracle. Recovery Manager for Oracle and Autonomic Groups HP 3PAR Autonomic Groups allow domains, hosts, and virtual volumes to be grouped into a set that is managed as a single object. HP 3PAR Recovery Manager Software for Oracle supports domain sets, and can coexist with host sets and volume sets. Refer to the HP 3PAR OS Concepts Guide for additional information about 3PAR Autonomic Groups. Recovery Manager for Oracle and Domain Sets HP 3PAR Recovery Manager Software for Oracle allows the management of multiple database servers belonging to different virtual domains from a single backup server. The following configuration requirements must be met: The backup server must belong to a domain set, which contains all database servers virtual domains to be managed by the backup server. The HP 3PAR OS user used by Recovery Manager for Oracle to access the HP 3PAR StoreServ Storage system from the backup server must belong to the virtual domains of all the database servers. Recovery Manager for Oracle and Host Sets Database servers (nodes) within the same Real Application Cluster (RAC) can be grouped into a set, which can then be managed as a single object. If the backup server also belongs to a host set, Recovery Manager for Oracle continues to export/deport database Virtual Copies to the backup server, rather than the host set that contains the backup server. Recovery Manager for Oracle and Virtual Volume Sets Database virtual volumes can be grouped into a set on the database server, which can be managed as a single object. Recovery Manager for Oracle works with the volume sets, but from the backup server, it does not make use of them as database virtual volumes must still be discovered to ensure that all database volumes are included in the volume set. Recovery Manager for Oracle with Remote Copy Recovery Manager for Oracle integrates with HP 3PAR Remote Copy Software to copy database virtual volumes from one HP 3PAR StoreServ Storage system (local or primary) to another (remote or secondary). Once copied, database Virtual Copies (application consistent snapshots) are created on the remote storage system or secondary storage system. The Virtual Copies can be used for disaster recovery or other off-host processing purposes. Recovery Manager for Oracle supports Recovery Manager for Oracle and Autonomic Groups 23

24 synchronous, asynchronous periodic mode, and Synchronous Long Distance Remote Copy. See the HP 3PAR Remote Copy Software User's Guide for additional information. Recovery Manager for Oracle and Peer Motion You need not uninstall and then reinstall Recovery Manager for Oracle when you migrate data with HP 3PAR Peer Motion. Preparing Recovery Manager for Oracle for Peer Motion Data Migration 1. Before you use Peer Motion to migrate data, remove all existing Recovery Manager for Oracle Virtual Copies in the following order: a. Remove all clone databases; to do so, use the GUI or the rmora_removedb command. b. Unmount all currently mounted Virtual Copies; to do so, use the GUI or the rmora_umount command. c. Remove all existing Virtual Copies; to do so, use the GUI or the rmora_remove command. 2. Start the data migration. While Peer Motion is migrating data, do not use Recovery Manager for Oracle. 3. Finish host configuration for the new HP 3PAR StoreServ Storage system. 4. Remove the old system from the storage system setup. 5. After Peer Motion migration is complete, reconfigure SSH to allow the database server and backup servers to access the new HP 3PAR StoreServ Storage system. 6. Modify the Recovery Manager for Oracle configuration file to reflect the new HP 3PAR StoreServ Storage system; to do so, use the GUI or rmora_config command. 7. Begin Recovery Manager for Oracle operations. Recovery Manager for Oracle and Fat-to-Thin and Thin-to-Fat To improve the existing RMO setup environment, an unlimited bidirectional conversion of volumes from Fat-to-Thin and Thin-to-Fat is featured with HP 3PAR Operating System Software. The user may better balance between performance and spacial optimization. Converting Virtual Volumes CAUTION: Due to the limitations of HP 3PAR OS, RMO is unable to retain repository information after online Fat-to-Thin or online Thin-to-Fat conversion process. As a result, all existing Virtual Copies, including the mounted ones, must be unmounted and removed prior to performing any online Fat-to-Thin or Thin-to-Fat conversion. Use either the GUI or CLI (rmora_remove) to remove all Virtual Copies. Do not use the RMO creation process during conversion. Only use the RMO creation process when the conversion process is complete. RMO can only detect conversion on specified volume. For example, you can still create a Virtual Copy on a datafile while a conversion is in progress on archive log volume. To convert database Virtual Volumes: 1. On HP 3PAR Backup system, use the Recovery Manager GUI or command line interface to remove all Virtual Copies of the database before converting the volumes. 2. On HP 3PAR StoreServ Storage system, enter tunevv to convert the virtual volumes. NOTE: For more details about using the tunevv command, see the HP 3PAR Operating System Software User Guide. 3. On HP 3PAR StoreServ Storage system, enter showtask to monitor the Virtual Volume conversion completion. 24 Overview of Recovery Manager Operations

25 Running Recovery Manager for Oracle on Japanese OS CAUTION: For full compatibility with Recovery Manager for Oracle, you must use English-language naming conventions in your Recovery Manager for Oracle setup (for example: Oracle SID/instance, Hostnames of database and backup servers, RMAN catalog db name, and NBU policies). RHEL 6.x Japanese OS Oracle 11g R2 HP 3PAR StoreServ Storage System NBU (Refer SPOCK for detail) Running Recovery Manager for Oracle on Japanese OS 25

26 2 Installing and Uninstalling Recovery Manager This chapter describes how to install, verify, and remove HP 3PAR Recovery Manager Software for Oracle on systems running Linux, Solaris, HP UX, and AIX. Referencing the Support Matrix For information about supported hardware and software platforms, refer to the Single Point of Connectivity Knowledge for HP Storage Products (SPOCK) website: Preinstallation Requirements Recovery Manager for Oracle must be installed on a database server and a backup server. The database server must be running an Oracle 10g or 11g database. NOTE: This feature requires the HP 3PAR Recovery Manager for Oracle Software license. NOTE: This version of HP 3PAR Recovery Manager for Oracle supports only English and limited Japanese. For Japanese language environment, see Running Recovery Manager for Oracle on Japanese OS (page 25) Prior to the installation of Recovery Manager for Oracle, make sure the following preinstallation requirements are met: The same Oracle owner user and Oracle DBA group on the database server must exist on the backup server. Recovery Manager for Oracle requires Korn shell to be installed and available from the location /usr/bin/ksh and /bin/ksh, which normally are the default locations for all supported platforms. If not, symbolic links should be created. If ASM is used to manage an Oracle database, the same ASM binary owner and group on the database server must exist on the bacup server. Oracle datafiles and archive logs must reside on separate 3PAR virtual volumes. Online redo logs and control files can reside on the same virtual volume. However, redo logs and control files must not reside on virtual volumes on which data files and archive logs reside. If Symantec Volume Manager is used, the Oracle datafiles and archive logs must reside on separate VxVM disk groups. Additionally, online redo logs and control files must not reside on VxVM disk groups that are used by Oracle datafiles and archive logs. The online redo logs and control files can reside on the same VxVM disk group. The database and backup server must have the same level of operating system patches, Symantec Volume Manager version, and maintenance patch. If HP, Linux, or AIX LVM Volume Manager is used, the Oracle datafiles and archive logs must reside on separate LVM volume groups. In addition, online redo logs and control files must not reside on LVM volume groups that are used by Oracle datafiles and archive logs. However, the online redo logs and control files can reside on the same LVM volume group. If ASM is used to manage an Oracle database, Oracle datafiles and archive logs must reside on different ASM disk groups. Additionally, online redo logs and control files must not reside on ASM disk groups used by Oracle datafiles and archive logs. The online redo logs and control files can reside on the same ASM disk group. 26 Installing and Uninstalling Recovery Manager

27 If you are using Symantec NetBackup 1 : HP recommends that you use the backup server as the NetBackup master server. The Symantec NetBackup client must be installed on the database and backup servers. If you are using Symantec NetBackup in conjunction with Oracle RMAN, the NetBackup for Oracle client must be installed on the database and backup servers. Refer to Symantec NetBackup for Oracle for installation and configuration instructions. The Backup and Database servers must have the same OS version as that of RMO and Oracle database. If you install the NetBackup for Oracle client, you must link the Oracle libobk.so library on the database and backup servers to point to the Symantec NetBackup Media Library. For more information, refer to Symantec s NetBackup for Oracle documentation. If you separate the NetBackup master server from the backup server, you must also install Recovery Manager for Oracle on the NetBackup master server. If you use the Oracle owner user to perform Recovery Manager for Oracle operations, the same Oracle owner user and Oracle owner group must exist on the NetBackup master server. No Oracle binary is required. If you are using HP Data Protector: HP Data Protector client with Oracle Integration Agent and User Interface components must be installed on the Recovery Manager for Oracle database server and backup servers. The Transparent Network Substrate (TNS) net service name must be pre-configured for the database instance on the database server. The same TNS net service name must be pre-configured for the clone database instance on the backup server. During the backup process, a clone database will be brought up on the backup server. Oracle Home must be the same between the Recovery Manager for Oracle database server and backup server. If you choose Oracle RMAN for the backup method, you must create an Oracle RMAN Recovery Catalog and configure Oracle TNS Service and Listener to allow connecting to the Recovery Catalog from both the database and backup servers. The Recovery Catalog can be created on any host. Recovery Manager for Oracle recommends that the Recovery Catalog is created on the backup server. Refer to Oracle documentation for instructions on how to create a Recovery Catalog, as well as how to configure Oracle TNS Service and Listener. In Linux: If you are using the device mapper multi-path, the supported disk formats on the database server are: /dev/mapper/diskname /dev/mapper/aliasname /dev/mapper/mpathn /dev/dm-n /dev/mpath/diskname Raw disks (/dev/raw/raw) are not supported. 1. Symantec NetBackup is third-party software, and HP 3PAR makes no representations or warranties with respect to such software. Preinstallation Requirements 27

28 Each OS disk can only have maximum one partition. For ext3/ext4 file systems, the journal devices should be within the same file systems Virtual volume snapshots used by an Oracle database must be mapped to a Common Provisioning Group (CPG). Refer to the HP 3PAR Command Line Interface Administrator s Manual for details about mapping to CPGs. For SSH private key protection expect utility must be pre-installed on Linux OS versions 5.9 and above. If you are upgrading from an earlier version of Recovery Manager for Oracle, do not use any upgrade utilities provided by the system. Instead, use rmora_install.sh to perform the upgrade. Refer to the HP 3PAR Implementation Guides for instructions on setting up connections from hosts to the HP 3PAR StoreServ Storage systems and reserving LUNs with specific Host Bus Adapters (HBAs) and Multipath configurations. To use the Remote Copy feature, you must configure your HP 3PAR StoreServ Storage systems for Remote Copy Software. The HP 3PAR StoreServ Storage systems must meet the requirements specified in Recovery Manager for Oracle s Remote Copy Requirements (page 125). For instructions on configuring storage systems for Remote Copy Software, see the HP 3PAR Remote Copy Software User s Guide. To support Recovery Manager for Oracle on AIX virtualization environment (VIOS), AIX VIO clients (LPAR/DLPAR) must be configured with N-Port ID Virtualization (NPIV) to provide direct Fibre Channel connections from VIO clients to SAN Storage Server. SAN Storage Server can be either direct attach or zoned using the switch for physical hosts. For VIO clients (LPAR's or DLPAR's) storage, switch and Host Bus Adaptor (HBA) of the server must support NPIV feature to be zoned. In AIX, 32-bit applications can access only one segment (256 MB) of program data memory, by default. Increase the amount of memory to 1.25 GB or an appropriate value: export LDR_CNTRL=MAXDATA=0x which is 1.25 GB of memory per process (5 segments of 256 MB). To make this setting permanent, add LDR_CNTRL=MAXDATA=0x at the end of the /etc/environment file. NOTE: There is a maximum of 2 GB of memory per process for 32-bit applications (0x ). Consult IBM's AIX documentation for more information. In the following example, a VIO client is added on a VIO Server and a virtual FC adapter is created and assigned to the client. ibm710-vm1 / :-> lsdev -c adapter ent0 Available Virtual I/O Ethernet Adapter (l-lan) ent1 Available Virtual I/O Ethernet Adapter (l-lan) fcs0 Available C3-T1 Virtual Fibre Channel Client Adapter vscsi0 Available Virtual SCSI Client Adapter ibm710-vm1 / :-> lscfg -vl fcs0 grep Address Network Address...C C << WWN of virtual adapter The Storage array is zoned to the WWN's of virtual adapter on clients. # showhost IBM710_01_VM1 Id Name Persona -WWN/iSCSI_Name- Port 31 IBM710_01_VM1 Generic C C :2:4 C C :2:4 28 Installing and Uninstalling Recovery Manager

29 NOTE: To get more information on how to configure NPIV for AIX VIOS, see IBM website: Installing Recovery Manager for Oracle on Linux Systems Installation Use the instructions in this section to install or upgrade Recovery Manager for Oracle on the database and backup servers. If you are not using the backup server as the NetBackup master server, be sure to install Recovery Manager for Oracle on the NetBackup master server. The following section describes the steps necessary for installing or upgrading Recovery Manager for Oracle on a Linux system. To install or upgrade HP 3PAR Recovery Manager: 1. Log in as the root user. 2. Insert the HP 3PAR Recovery Manager CD into a CD-ROM drive. NOTE: If you are using HP-UX older than version, then it is mandatory to update to the patch level. If the CD is not mounted automatically, mount it manually. # mount -t iso9660 -r /dev/cdrom /mnt/cdrom 3. Change to the CD-ROM drive. # cd /mnt/cdrom0/ Installing Recovery Manager for Oracle on Linux Systems 29

30 4. Installation without SSH private key protection Enter./rmora_install.sh. Read the following information before continuing the installation: By default, only user root is allowed to run RMO if the second question is answered no. Enter the user and group name of the Oracle owner previously used to install your Oracle database if different from the names shown in the sample output below. The sample output describes a clean installation. The output and first prompt when doing an upgrade or a re-installation will indicate that an upgrade or re-installation is being initiated. Answer the following prompts. #./rmora_install.sh Welcome to HP 3PAR Recovery Manager for Oracle Checking for existing Recovery Manager installation... Recovery Manager is not found on the system. Do you want to install Recovery Manager for Oracle v4.6.0? (y/n) y Installing Recovery Manager for Oracle v Preparing packages for installation... RMOra Would you like to run RMOra as an Oracle owner? (y/n) y Enter the user name of the Oracle owner[q]: oracle Enter the group name of the Oracle owner[q]: oinstall WARN: Ownership and permission will be changed for all database repositories. Refer to the Recovery Manager for Oracle User's Guide or the rmora_chown(1m) man page for details. Allow RMOra to be run with 'oracle:oinstall' (y/n)? y Installation completed. Installation with SSH private key protection Answer the following prompts. #./rmora_install.sh Welcome to HP 3PAR Recovery Manager for Oracle! Checking for existing Recovery Manager installation... Recovery Manager is not found on the system. Do you want to install Recovery Manager for Oracle v4.6.0? (y/n) y Installing Recovery Manager for Oracle v Preparing packages for installation... RMOra WARN: By default, only root user can run RMOra. You can allow Oracle user to run RMOra by answering yes to the question below. If you answer no, all existing configuration(s) will be changed to be owned by root user on this server. Would you like to run RMOra as an Oracle owner? (y/n) n All existing configuration(s) will be changed to be owned by root user. Do you want to continue? (y/n) y WARN: Ownership and permission will be changed for all database repositories. Refer to the Recovery Manager for Oracle User's Guide or the rmora_chown(1m) man page for details. Would you like to protect ssh private key with passphrase? (y/n) y Enter the number of bits in the key to create (default:1024): Enter the keytype rsa/dsa (default:rsa): Enter the location of private/public key pair (default: rsa -> ~/.ssh/id_rsa ; 30 Installing and Uninstalling Recovery Manager

31 dsa -> ~/.ssh/id_dsa): Enter the passphrase of the private key (mandatory): fjalfjalf Generating public/private rsa key pair. /root/.ssh/id_rsa already exists. Overwrite (y/n)? y Your identification has been saved in /root/.ssh/id_rsa. Your public key has been saved in /root/.ssh/id_rsa.pub. The key fingerprint is: b3:12:63:1a:9b:da:32:6f:e1:d1:e3:fd:3c:6b:2c:c2 root@rhel5bk successfully created the ssh private/public keypair successfully configured ssh-agent Installation completed. NOTE: If you opts not to generate the keys here and wants to protect the keys later, then you must run the following commands in the same sequence: /opt/3par/rmora/bin/rmora_sshkeygen /opt/3par/rmora/bin/rmora_sshagent 5. After the installation is complete on all the required servers, you can allow Oracle users and Database Administrators group access to the Recovery Manager commands and utilities by running the rmora_chown utility if you did not specify during step 4. You can use the utility command to allow only root or both root and a single non-root user to manage all RMO database configurations. #/opt/3par/rmora/bin/rmora_chown -u <user> -g <group> NOTE: You will be prompted to generate the ssh-keys, and if you opt for the passphrase protection, the above command rmora_chown should be run on all backup/database server. For more information about allowing types of users to manage all RMO database configurations, refer to rmora_chown (page 74). 6. You are required to add the SSH public key resides in the user specified location during the installation from the backup server to the database server(s), HP 3par Storeserv and other servers used for oracle backup using RMO. 7. Since SSH keys are generated, you are not required to regenerate the keys. verifying the SSH connectivity between the hosts: # ssh rhel5db The authenticity of host 'rhel5db ( )' can't be established. RSA key fingerprint is 45:00:39:96:3e:62:ad:cf:aa:38:ae:7b:4f:48:2b:f3. Are you sure you want to continue connecting (yes/no)? yes Warning: Permanently added 'rhel5db, ' (RSA) to the list of known ho Enter passphrase for key '/root/.ssh/id_rsa': Last login: Thu Sep 18 08:10: from rhel5bk Verifying Installation NOTE: You will be prompted to enter the passphrase which was provided during SSH keys generation at the time of installation. To verify HP 3PAR Recovery Manager installation on a Linux system: 1. Log in as the root user. Installing Recovery Manager for Oracle on Linux Systems 31

32 2. Issue the rpm -qi RMOra command and verify: RMOra is the displayed package name under the Name field is the version displayed under the Version field. Removing Recovery Manager from Linux Systems To uninstall HP 3PAR Recovery Manager from a Linux system: 1. Log in as the root user. 2. Insert the HP 3PAR Recovery Manager CD into a CD-ROM drive. NOTE: If the CD is not mounted automatically, mount it manually. # mount -t iso9660 -r /dev/cdrom /mnt/cdrom 3. Change to the CD-ROM drive. # cd /mnt/cdrom0/ 4. Enter./rmora_uninstall.sh. Confirm you want to uninstall RMO when prompted. #./rmora_uninstall.sh Welcome to HP 3PAR Recovery Manager for Oracle Checking for existing Recovery Manager installation... The following version of RMOra has been found: Currently Installed version: Do you want to remove the existing RMOra? (y/n)y Removing existing RMOra... Recovery Manager removed Installing Recovery Manager for Oracle on Solaris Systems Installation Use the instructions in this section to install or upgrade Recovery Manager for Oracle on the database and the backup servers. If you are not using the backup server as the NetBackup master server, be sure to install Recovery Manager for Oracle on the NetBackup master server. To install or upgrade HP 3PAR Recovery Manager on a Solaris system: 1. Log on as the root user. 2. Insert the HP 3PAR Recovery Manager CD into a CD-ROM drive. If the CD is not mounted automatically, mount it manually. # mount -F hsfs -o ro /dev/dsk/c0t6d0s2/cdrom 3. Change to the CD-ROM drive. # cd /cdrom/cdrom0/ 32 Installing and Uninstalling Recovery Manager

33 4. Enter./rmora_install.sh. The prompts and output from running rmora_install.sh are similar to those when running rmora_install.sh on Linux. If necessary, refer to Installation (page 29). However, the output on Solaris will include a listing of all RMO package files being installed and you will also be prompted to confirm the installation of setuid root executables. NOTE: Install the following patch if applicable: Solaris 5.10 requires patch or later. Use the following command to verify whether the patches are installed or not: showrev -p grep After the installation is complete on the required servers, you can allow Oracle users and Database Administrators group access to the Recovery Manager commands and utilities by running the rmora_chown utility if you did not specify during step 4. You can use the utility command to allow only root or both root and a single non-root user to manage all RMO database configurations. # /opt/3par/rmora/bin/rmora_chown -u <user> -g <group> Verifying Installation For more information about allowing types of users to manage all RMO database configurations, refer to rmora_chown (page 74). To verify HP 3PAR Recovery Manager installation on a Solaris system: 1. Log in as the root user. 2. Enter the pkginfo -l RMOra command and verify: RMOra is the package name displayed under the PKGINST field is the version displayed under the Version field. Removing Recovery Manager from Solaris Systems To remove HP 3PAR Recovery Manager from a Solaris system: 1. Log on as the root user. 2. Insert the HP 3PAR Recovery Manager CD into a CD-ROM drive. If the CD is not mounted automatically, mount it manually. # mount -F hsfs -o ro /dev/dsk/c0t6d0s2/cdrom 3. Change to the CD-ROM drive. # cd /cdrom/cdrom0/ Removing Recovery Manager from Solaris Systems 33

34 4. Enter./rmora_uninstall.sh. Confirm you want to uninstall RMO when prompted. #./rmora_uninstall.sh Welcome to HP 3PAR Recovery Manager for Oracle Checking for existing Recovery Manager installation... The following version of RMOra has been found: Currently Installed version: Do you want to remove the existing RMOra? (y/n)y Removing existing RMOra... Recovery Manager removed Installing Recovery Manager for Oracle on HP UX Systems Installation Use the instructions in this section to install or upgrade Recovery Manager for Oracle on the database and backup servers. If you are not using the backup server as the NetBackup master server, be sure to install Recovery Manager for Oracle on the NetBackup master server. The following section describes the steps necessary for installing or upgrading Recovery Manager for Oracle on an HP UX system: 1. Log in as the root user. 2. Insert the HP 3PAR Recovery Manager CD into a CD-ROM drive. NOTE: If the CD is not mounted automatically, mount it manually. # mount -t iso9660 -r /dev/cdrom /mnt/cdrom 3. Change to the CD-ROM drive. # cd /mnt/cdrom0/ 4. Enter./rmora_install.sh. The prompts and output from running rmora_install.sh are similar to those when running rmora_install.sh on Linux. If necessary, refer to Installation (page 29). 5. After the installation is complete on all the required servers, you can allow Oracle users and the Database Administrators group access to the Recovery Manager commands and utilities by running the rmora_chown utility if you did not specify during step 4. You can use the utility command to allow only root or both root and a single non-root user to manage all RMO database configurations. /opt/3par/rmora/bin/rmora_chown -u <user> -g <group> For more information about allowing types of users to manage all RMO database configurations, refer to rmora_chown (page 74). 34 Installing and Uninstalling Recovery Manager

35 Verifying Installation 1. Log in as the root user. 2. Enter the swlist RMOra command and verify: The product name RMOra and the fileset RMOra.RUN are displayed. The Version displayed is To enable a user to schedule tasks (for example, to create a Virtual Copy creation schedule), add the user name to the /usr/lib/cron/cron.allow file. Removing Recovery Manager from HP UX Systems 1. Log in as the root user. 2. Insert the HP 3PAR Recovery Manager CD into a CD-ROM drive. NOTE: If the CD is not mounted automatically, mount it manually. # mount -t iso9660 -r /dev/cdrom /mnt/cdrom 3. Change to the CD-ROM drive. # cd /mnt/cdrom0/ 4. Enter./rmora_uninstall.sh. Confirm you want to uninstall RMO when prompted. #./rmora_uninstall.sh Welcome to HP 3PAR Recovery Manager for Oracle Checking for existing Recovery Manager installation... The following version of RMOra has been found: Currently Installed version: Do you want to remove the existing RMOra? (y/n)y Removing existing RMOra... Recovery Manager removed Installing Recovery Manager for Oracle on IBM AIX Systems Installation Use the instructions in this section to install Recovery Manager for Oracle on the database and backup servers. If you are not using the backup server as the NetBackup master server, be sure to install Recovery Manager for Oracle on the NetBackup master server. The following section describes the steps necessary for installing Recovery Manager for Oracle on IBM AIX system. To install HP 3PAR Recovery Manager on IBM AIX system: 1. Log in as the root user. 2. Insert the HP 3PAR Recovery Manager CD into a CD-ROM drive. Removing Recovery Manager from HP UX Systems 35

36 NOTE: If the CD is not mounted automatically, mount it manually. To mount the CD on physical server, enter the following: # /usr/sbin/mount -rv cdrfs /dev/cd0 /mnt/cdrom To mount a CD on VIO clients: 1. Create a Virtual SCSI Adapter or use existing one on the VIO server. 2. To create a Virtual Device cd0 and to map it to Virtual Adapter, enter the following: # mkvdev -vdev cd0 -vadapter vhost0 vtopt0 Available 3. The CD is available to the same client, where vhost0 is mapped. 4. To find out to which client the CD is mapped to, enter lsmap -all on VIO Server. 5. On VIO Client, use mount command to mount a CD. # /usr/sbin/mount -rv cdrfs /dev/cd0 /mnt/cdrom 3. Change to the CD-ROM drive. # cd /mnt/cdrom/ 4. Enter./rmora_install.sh. Welcome to HP 3PAR Recovery Manager 4.6.0for Oracle Checking for existing Recovery Manager installation... Recovery Manager is not found on the system. Do you want to install Recovery Manager for Oracle v4.6.0? (y/n) y Installing Recovery Manager for Oracle v aix_install=installp -a -X -d /share/engineering/solutions/release/oracle/4.6.0/aix RMOra.rte Pre-installation Verification Verifying selections...done Verifying requisites...done Results... SUCCESSES Filesets listed in this section passed pre-installation verification and will be installed. Selected Filesets RMOra.rte # Recover Manager for Oracle o... << End of Success Section >> BUILDDATE Verification Verifying build dates...done FILESET STATISTICS Selected to be installed, of which: 1 Passed pre-installation verification Installing and Uninstalling Recovery Manager

37 1 Total to be installed Installing Software installp: APPLYING software for: RMOra.rte Finished processing all filesets. (Total time: 35 secs) Summaries: Installation Summary Name Level Part Event Result RMOra.rte USR APPLY SUCCESS Would you like to run RMOra as an Oracle owner? (y/n) y Enter the user name of the Oracle owner[q]: ora Enter the group name of the Oracle owner[q]: oinstall WARN: Ownership and permission will be changed for all database repositories. Refer to the Recovery Manager for Oracle User's Guide or the rmora_chown(1m) man page for details. Allow RMOra to be run with 'ora:oinstall' (y/n)? y Installation completed. 5. After the installation is complete on all the required servers, you can allow Oracle users and the Database Administrators group access to the Recovery Manager commands and utilities by running the rmora_chown utility if you did not specify during step 4. You can use the utility command to allow only root or both root and a single non-root user to manage all RMO database configurations. /opt/3par/rmora/bin/rmora_chown -u <user> -g <group> Verifying Installation For more information about allowing types of users to manage all RMO database configurations, refer to rmora_chown (page 74). To verify HP 3PAR Recovery Manager installation on IBM AIX system: 1. Log in as the root user. 2. Enter the lslpp -l RMOra.rte command and verify: The Product Fileset name RMOra.rte, State and Description are displayed. The level displayed is Removing Recovery Manager from IBM AIX Systems To remove 3PAR Recovery Manager from IBM AIX system: 1. Log in as the root user. 2. Insert the HP 3PAR Recovery Manager CD into a CD-ROM drive. Removing Recovery Manager from IBM AIX Systems 37

38 NOTE: If the CD is not mounted automatically, mount it manually. To mount the CD on physical server, enter the following: # /usr/sbin/mount -rv cdrfs /dev/cd0 /mnt/cdrom To mount a CD on VIO clients: 1. Create a Virtual SCSI Adapter or use existing one on the VIO server. 2. To create a Virtual Device cd0 and to map it to Virtual Adapter, enter the following: # mkvdev -vdev cd0 -vadapter vhost0 vtopt0 Available 3. The CD is available to the same client, where vhost0 is mapped. 4. To find out to which client the CD is mapped to, enter lsmap -all on VIO Server. 5. On VIO Client, use mount command to mount a CD. # /usr/sbin/mount -rv cdrfs /dev/cd0 /mnt/cdrom 3. Change to the CD-ROM drive. # cd /mnt/cdrom/ 38 Installing and Uninstalling Recovery Manager

39 4. Enter./rmora_uninstall.sh. Confirm you want to uninstall Recovery Manager for Oracle when prompted. Welcome to HP 3PAR Recovery Manager for Oracle Checking for existing Recovery Manager installation... The following version of RMOra has been found: Currently Installed version: Do you want to remove the existing RMOra? (y/n) y Removing existing RMOra Pre-deinstall Verification Verifying selections...done Verifying requisites...done Results... SUCCESSES Filesets listed in this section passed pre-deinstall verification and will be removed. Selected Filesets RMOra.rte # Recover Manager for Oracle o... << End of Success Section >> FILESET STATISTICS Selected to be deinstalled, of which: 1 Passed pre-deinstall verification Total to be deinstalled Deinstalling Software installp: DEINSTALLING software for: RMOra.rte Finished processing all filesets. (Total time: 10 secs) Summaries: Installation Summary Name Level Part Event Result RMOra.rte USR DEINSTALL SUCCESS Recovery Manager removed Removing Recovery Manager from IBM AIX Systems 39

40 3 Configuring Recovery Manager for Oracle Recovery Manager for Oracle requires that an SSH connection be configured for the backup server, the database server, the Symantec NetBackup master server, and the HP 3PAR StoreServ Storage system. Since Recovery Manager for Oracle can be run by either the root user or an Oracle user (Oracle owner), configure SSH for the root or an Oracle user. NOTE: Recovery Manager for Oracle supports Symantec NetBackup and HP Data Protector as the root user or an Oracle user. Setting Up SSH Connections for Recovery Manager This section provides instructions on how to configure a Secure Shell (SSH) on the database server, backup server, NetBackup (NBU) master server, and the HP 3PAR StoreServ Storage system. Recovery Manager for Oracle commands can be run as either a root user or an Oracle user. SSH must be configured for the root user or the Oracle user. Figure 1 (page 40) represents the SSH connection relationship between the database server, the backup server, NBU master server, and the HP 3PAR StoreServ Storage system. Figure 2 (page 41) represents the SSH connection relationship in a Remote Copy configuration. Figure 1 SSH Connection Relationship 40 Configuring Recovery Manager for Oracle

41 Figure 2 SSH Connection Relationship for Remote Copy Support SSH Restrictions Recovery Manager for Oracle has the following SSH restrictions: The ssh and scp commands must be located in the /usr/bin/ directory. Create symbolic links, if necessary. For example, if SSH and SCP are located at /usr/local/bin, create symbolic links as follows: #ln -s /usr/local/bin/ssh /usr/bin/ssh #ln -s /usr/local/bin/scp /usr/bin/scp SSH keys on the database server and backup servers must be generated with no passphrase. Recovery Manager for Oracle does not support an SSH passphrase or SSH agent. Modifying the SSH Daemon Configuration If SSH needs to be configured for the root user, then the SSH daemon on the database server, backup server, and NetBackup master server must be configured to allow root access. Perform the following on each system: 1. Verify that the SSH daemon allows root access by checking the sshd_config file for the following line: PermitRootLogin yes NOTE: If you are using native SSH, the sshd_config file is located in /etc/ssh/sshd_config. If you are using HP UX, the sshd_config file is located in /opt/ssh/etc/sshd_config. 2. If the line is PermitRootLogin no, change the line to PermitRootLogin yes. Setting Up SSH Connections for Recovery Manager 41

42 3. If you are using HP UX, verify that the SSH daemon has strict mode disabled: a. Check the sshd_config file for the following line: StrictModes no b. If StrictModes is set to yes, change the entry to no. Generating an SSH Key Pair for the Backup Server IMPORTANT: For manual generation of SSH keys with passpharse protection for Linux 5.9 and above, see: /opt/3par/rmora/bin/rmora_sshkeygen /opt/3par/rmora/bin/rmora_sshagent For generating SSH keys without passpharse protection for Linux and other supported OS, perform the following task: To generate an SSH key pair for the backup server: 1. Log on to the backup server as the root or Oracle owner user. 2. Create a key pair with no passphrase using the ssh-keygen command. If a key-pair already exists, skip this section. <backup_server>:# ssh-keygen -b t rsa Generating public/private rsa key pair. Enter file in which to save the key (//.ssh/id_rsa): Enter passphrase (empty for no passphrase): Enter same passphrase again: Your identification has been saved in //.ssh/id_rsa. Your public key has been saved in //.ssh/id_rsa.pub. The key fingerprint is: xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx root@<backup_server> NOTE: You can create the SSH key as either dsa or rsa. The recommended key length is 1024 (the total of the public and private key lengths). The ssh-keygen utility generates two files, id_rsa and id_rsa.pub (or id_dsa and id_dsa.pub). The id_rsa (or id_dsa) file contains the private key and the id_rsa.pub (or id_dsa.pub) file contains the public key. Generating an SSH Key Pair for the Database Server You can either use the same SSH key pair generated for the backup server or generate a different SSH key pair for the database server. If you choose to use the same key pair, create one HP 3PAR CLI user, otherwise, create two different HP 3PAR CLI users to be accessed from the database server and the backup server, respectively. If you are generating a different SSH key pair for the database server, perform the procedure described in Setting Connections from the Database Server to the HP 3PAR StoreServ Storage (page 46) on the database server. NOTE: In a Real Application Cluster (RAC) environment, all the nodes in the RAC cluster must have the same SSH key pair to run Recovery Manager for Oracle utilities against any RAC instance on any node. 42 Configuring Recovery Manager for Oracle

43 If you choose to use the same SSH key pair, create one HP 3PAR CLI user. Then copy the SSH key pair from the backup server to the database server as follows: <db_server> # scp <backup_server>:~/.ssh/* ~/.ssh The authenticity of host 'pilot ( )' can't be established. RSA key finger print is xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx. Are you sure you want to continue connecting (yes/no)? yes Warning: Permanently added 'pilot ( )' to the list of known hosts. root@pilot's password: Setting Up Connections from the Backup Server to the Database Server To set up an SSH connection from the backup server to the database server: Copy the public key (id_rsa.pub) of the backup server to the authorized_keys file of the database server. <backup_server> # scp ~/.ssh/id_rsa.pub <db_server>:~/.ssh/authorized_keys If the authorized_keys file already exist, add the public key (from ~/.ssh/id_rsa.pub on the backup server) to the end of the authorized_keys file on the database server. Verifying Connections from the Backup Server to the Database Server From the backup server, verify the connection to the database server as follows: <backup_server># ssh <user>@<db_server> The authenticity of host '<db_server>' can't be established. DSS key fingerprint is xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:x:xx:xx. Are you sure you want to continue connecting (yes/no)? yes Warning: Permanently added '<db_server>' (DSS) to the list of known hosts. where <user> is either the root or the Oracle owner user and <db_server> is the database server s hostname. NOTE: If you are prompted for a password, the connection was not set up correctly. To resolve the issue: Redo the connection setup. Verify that the.ssh directory and the files within the.ssh directory have the correct permissions. Setting Up SSH Connections for Recovery Manager 43

44 Setting Up Connections from the Backup Server to the NetBackup Master Server To set up an SSH connection from the backup server to the NetBackup (NBU) master server: Copy the public key (id_rsa.pub) of the backup server to the authorized_keys file of the NBU master server. <backup_server # scp ~/.ssh/id_rsa.pub <NBU_server>:~/.ssh/authorized_keys If the authorized_keys file already exist, add the public key (from ~/.ssh/id_rsa.pub on the backup server) to the end of the authorized_keys file on the NetBackup master server. Verifying Connections from the Backup Server to the NetBackup Master Server From the backup server, verify the connection to the NetBackup master server as follows: <backup_server># ssh <user>@<nbu_master> The authenticity of host '<NBU_master>' can't be established. DSS key fingerprint is xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:x:xx:xx. Are you sure you want to continue connecting (yes/no)? yes Warning: Permanently added '<NBU_master>' (DSS) to the list of known hosts. where <user> is either the root or the Oracle owner user and <NBU_master> is the name of the NBU master server. NOTE: If you are prompted for a password, the setup is incorrect and you must perform the previous setup again. Setting Up Connections from the Backup Server to the HP 3PAR StoreServ Storage To set up an SSH connection from the backup server to the HP 3PAR StoreServ Storage system: 1. SSH to the backup server and log in as the root or Oracle owner user. 2. Make sure the SSH key pair exists as follows: <backup_server> # ls ~/.ssh id_rsa id_rsa.pub authorized_keys known_hosts 3. Create a CLI user on the HP 3PAR StoreServ Storage system to be used by Recovery Manager for Oracle to access the system from the backup server. Skip this step if you choose to use an existing user. <backup_server># ssh <adm_user>@<ss_name> <adm_user>'s password: <adm_password> cli% createuser -c <password> <username> <domainname> <role> 44 Configuring Recovery Manager for Oracle

45 In the example : <adm_user> is the user name of the HP 3PAR StoreServ Storage system s administrator (for example, 3paradm). For more information, see the HP 3PAR Command Line Interface Administrator s Manual. <ss_name> is the system name of the HP 3PAR StoreServ Storage system attached to the backup server. <adm_password> is the administrator password. <password> is the password (for the HP 3PAR StoreServ Storage system) for the CLI user being created. <username> is the user being created. <domainname> is the domain to which the user will belong (for example, all). <role> specifies the authority level of the user (for example, 3PAR_RM). For details about the createuser command, refer to the HP 3PAR Command Line Interface Reference. 4. Copy the public key of the backup server to the HP 3PAR StoreServ Storage system. You can find the public key in the location specified when generating an SSH key pair; for more information, see Generating an SSH Key Pair for the Backup Server (page 42). <backup_server># ssh <username>@<ss_name> <username>'s password: <password> cli% setsshkey Please enter the SSH public key below. When finished, press enter twice. The key is usually long. It's better to copy it from inside an editor and paste it here. (Please make sure there are no extra blanks.) The maximum number of characters used to represent the SSH key (including the "from" option, key type, and additional comments) is <paste the public key here and press Enter twice> <public_key> SSH public key successfully set! In the example : <username> is the user you created. <ss_name> is the system name of the HP 3PAR StoreServ Storage system attached to the backup server. <password> is the password for the CLI user you created. <public_key> is the SSH public key of the backup server. You can also use the command setsshkey with the option -add to specify that the given key should be added to the list of authorized keys instead of replacing existing ones. Verifying Connections from the Backup Server to the HP 3PAR StoreServ Storage From the backup server, verify the connection from the backup server to the HP 3PAR StoreServ Storage system as follows: <backup_server># ssh <username>@<ss_name> Setting Up SSH Connections for Recovery Manager 45

46 The authenticity of host '<ss_name>' can't be established. DSS key fingerprint is xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:x:xx:xx. Are you sure you want to continue connecting (yes/no)? yes Warning: Permanently added '<HP 3PAR StoreServ Storage>' (DSS) to the list of known hosts. where: <user_name> is the CLI user created in Setting Up Connections from the Backup Server to the HP 3PAR StoreServ Storage (page 44). <ss_name> is the system name of the HP 3PAR StoreServ Storage system attached to the backup server. NOTE: If you are prompted for a password, the setup is incorrect and you must perform the previous setup again. Setting Connections from the Database Server to the HP 3PAR StoreServ Storage Skip this step if the database server has the same SSH key pair as the SSH key pair of the backup server (see Generating an SSH Key Pair for the Database Server (page 42)). Recovery Manager for Oracle uses the same CLI user to access the HP 3PAR StoreServ Storage system from either the backup server or the database server. If you created a different CLI user for the database server, then to set up an SSH connection from the database server to the HP 3PAR StoreServ Storage system: 1. SSH to the database server and log in as the root or Oracle owner user. 2. Make sure the SSH key pair exists as follows: <db_server> # ls ~/.ssh id_rsa id_rsa.pub authorized_keys known_hosts 3. Create a CLI user to be used by Recovery Manager for Oracle to access the HP 3PAR StoreServ Storage system from the database server. Skip this step if you wish to use an existing user (different from the user created for the backup server). <db_server># ssh <adm_user>@<ss_name> <adm_user>'s password: <adm_password> cli% createuser -c <password> <username> <domainname> <role> In the example : <adm_user> is the user name of the HP 3PAR StoreServ Storage system s administrator (for example, 3paradm). <ss_name> is the system name of the HP 3PAR StoreServ Storage system attached to the database server. <adm_password> is the administrator password. <password> is the password (for the HP 3PAR StoreServ Storage system) for the CLI user being created. <username> is the user being created. <domainname> is the domain to which the user will belong (for example, all) <role> specifies the authority level of the user (for example, 3PAR_RM) 46 Configuring Recovery Manager for Oracle

47 4. Copy the public key of the database server to the HP 3PAR StoreServ Storage system. <db_server># ssh <username>'s password: <password> cli% setsshkey Please enter the SSH public key below. When finished, press enter twice. The key is usually long. It's better to copy it from inside an editor and paste it here. (Please make sure there are no extra blanks.) The maximum number of characters used to represent the SSH key (including the "from" option, key type, and additional comments) is <pass the public key here and press Enter twice> <public_key> SSH public key successfully set! In the example : <username> is the user being created. <ss_name> is the system name of the HP 3PAR StoreServ Storage system attached to the database server. <password> is the password for the CLI user being created. <public_key> is the SSH public key of the database server. You can also use the command setsshkey with the option -add to specify that the given key should be added to the list of authorized keys instead of replacing existing ones. Verifying Connections from the Database Server to the HP 3PAR StoreServ Storage From the database server, verify the connection from the database server to the HP 3PAR StoreServ Storage system as follows: <db_server># ssh <username>@<ss_name> The authenticity of host '<ss_name>' can't be established. DSS key fingerprint is xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:x:xx:xx. Are you sure you want to continue connecting (yes/no)? yes Warning: Permanently added '<ss_name>' (DSS) to the list of known hosts. where: <username> is the CLI user created in Setting Up Connections from the Backup Server to the HP 3PAR StoreServ Storage (page 44). <ss_name> is the name of the HP 3PAR StoreServ Storage system attached to the database server. NOTE: If you are prompted for a password, the setup is incorrect and you must perform the previous setup again. Setting Up SSH Connections for Recovery Manager 47

48 Setting up National Language Host Support The Recovery Manager for Oracle message catalog and the symbolic link are installed in the following locations: OS Solaris Linux HP UX AIX Recovery Manager for Oracle Message Catalog Location /opt/3par/msg/en_us /opt/3par/rmora/msg/en_us /opt/3par/msg/en_us /opt/3par/msg/en_us Symbolic Link Location /usr/lib/locale/en_us /usr/lib/locale/en_us /usr/lib/nls/msg/c /usr/lib/nls/msg/en_us To retrieve the text messages properly, you must set the NLSPATH path environment; for example: # NLSPATH=$NLSPATH:/usr/lib/locale/%L/%N # export NLSPATH Setting up Manual Pages on Database and Backup Servers Recovery Manager for Oracle provides manual pages in the /opt/3par/man directory for Solaris, HP UX, and IBM AIX systems, and in the /opt/3par/rmora/man directory for Linux systems. To access the manual pages, define the environment variable MANPATH as follows: # MANPATH=$MANPATH:/opt/3PAR/man # export MANPATH # LC_ALL=en_US # export LC_ALL For Linux systems, change the manual page directory to /opt/3par/rmora/man. Setting up a Search Path on Database and Backup Servers Recovery Manager for Oracle executables are stored in the /opt/3par/rmora/bin directory. To add the Recovery Manager executables to the Recovery Manager search path, use the following commands: # PATH=$PATH:/opt/3PAR/RMOra/bin # export PATH Creating an RMAN Recovery Catalog This section describes how to create and configure an RMAN Recovery Catalog. Refer to Oracle documentation for more detailed information. 48 Configuring Recovery Manager for Oracle

49 1. Create a database for housing the Recovery Catalog. Oracle suggests the following disk space requirements: System tablespace: 100 MB Temp tablespace: 5 MB Rollback segment: 5 MB Online redo log: 1 MB (each) Recovery Catalog: 10 MB 2. Create a tablespace for the Recovery Catalog as follows: $ export ORACLE_SID=<catdb> $ export ORACLE_HOME=<oracle_home> $ sqlplus "/as sysdba" SQL> create tablespace <cat_tbs> datafile '<path/filename>' size 10M; SQL> exit where: <catdb> is the Oracle Instance ID of the Recovery Catalog. <cat_tbs> is the Recovery Catalog tablespace name. <path/filename> is the file path where the datafile is created. 3. Create a user for the Recovery Catalog as follows: $ sqlplus "/as sysdba" SQL> create user <rman_user> identified by <rman_password> temporary tablespace temp default tablespace <cat_tbs> quota unlimited on <cat_tbs>; SQL> grant connect, resource, recovery_catalog_owner to <rman_user>; where: <tbs_name> is the tablespace name of the Recovery Catalog. <rman_user> is the user name to be granted access permission to the Recovery Catalog. <rman_password> is the password for the <rman_user>. 4. Create the RMAN Recovery Catalog tables as follows: $ rman catalog <rman_user>/<rman_password>@<catdb> RMAN> create catalog tablespace <cat_tbs>; 5. Configure TNS services for the Recovery Catalog database by adding an entry in the $ORACLE_HOME/network/admin/tnsnames.ora file on the database server and backup server as follows: <catdb> = (description = (address = (protocol = TCP) (host = <cat_host>) (port = 1521)) (connect_data = (server = dedicated) (service_name = <catdb>)) ) where <cat_host> is the host name of the host where the catalog is created. Creating an RMAN Recovery Catalog 49

50 6. Configure the Oracle listener for the Recovery Catalog database by adding an entry in the $ORACLE_HOME/network/admin/listener.ora file on the host where the Recover Catalog is created as follows: SID_LIST_LISTENER = (SID_LIST = (SID_DESC = (GLOBAL_DBNAME = <catdb>) (ORACLE_HOME = <oracle_home>) (SID_NAME = <catdb>) ) ) 7. Log in as the Oracle owner user and register the database on the database server. NOTE: If Recovery Manager for Oracle is used to run against an Oracle standby database, you must register the primary database on the primary database server instead of the standby database. $ rman target / catalog <rman_user>/<rman_password>@<catdb> RMAN> register database; Setting Up NetBackup Policies for NBU (User-Managed) Backup Recovery Manager for Oracle supports NetBackup (NBU) with or without RMAN. The following sections describe how to set up NBU policies for NBU backup without RMAN. Recovery Manager for Oracle supports full, incremental, or cumulative incremental archive log backup (backup only archive logs). When performing NBU backup without RMAN, Recovery Manager supports only full database backup (incremental database backup is not possible). However, you can combine full database backup with archive log backup to simulate incremental database backup. Recovery Manager for Oracle requires that you create an NBU policy for database backup. If you wish to perform archive log backup, you must create a separate NBU policy for it. NOTE: This section is intended for the users who are familiar with the Oracle Database and Symantec NetBackup (NBU). For more information on creating a NetBackup policy, refer to Symantec NetBackup documentation. Configuring the NetBackup Policy for Database Backup For Recovery Manager for Oracle to perform backup and restoration correctly, you must use the following guidelines in conjunction with Symantec NetBackup documentation when configuring a NBU policy: Backup Attribute Backup Selections 1. Select the standard type for the policy. 2. Select the cross mount points option. 3. Deselect the Allow multiple data stream and Block level incremental options. 1. It is recommended that you enter /dummy for the backup selections. 2. Recovery Manager generates the backup selection list on the fly to replace the value you entered. 50 Configuring Recovery Manager for Oracle

51 Backup Schedule 1. Create a schedule for full backup. 2. If you wish to perform client-side database backup (initiated from Recovery Manager), set the backup window to If you also wish to perform server-side database backup (initiated from NBU), specify the backup window to fit your needs. Backup Clients Set the backup client to the host name of the backup server, as the backup process will actually take place on the backup server. Configuring the NetBackup Policy for Archive Log Backup This procedure is to backup the archive logs only. For Recovery Manager for Oracle to perform backup and restoration correctly, you must use the following guidelines in conjunction with Symantec NetBackup documentation when configuring a NBU policy: Backup Attribute Backup Selections Backup Schedule 1. Select the standard type for the policy. 2. Select the cross mount points option. 3. Deselect the Allow multiple data stream and Block level incremental options. 1. It is recommended that you enter /dummy for the backup selections. 2. Recovery Manager generates the backup selection list on the fly to replace the value you entered. 1. Create two schedules, one for full backup and one for incremental backup (optional). For the incremental backup schedule, you can create either a differential incremental or cumulative incremental backup schedule. NOTE: Incremental backup of archive log using RMAN is not supported. 2. If you wish to perform client-side archive log backup (initiated from Recovery Manager), set the backup window to If you also wish to perform server-side archive log backup (initiated from NBU), specify the backup window to fit your needs. Backup Clients Set the backup client to the host name of the backup server, as the backup process will actually take place on the backup server. Setting Up NetBackup Configuration Parameters for the Backup Server Recovery Manager uses bpstart and bpend scripts as a hook to NetBackup to create Virtual Copy of a database, then present the database Virtual Copy to the backup server for backup, and to cleanup the Virtual Copy after backup process completes respectively. The BPSTART_TIMEOUT and BPEND_TIMEOUT in the /usr/openv/netbackup/bp.conf on the backup server should be set to at least 600 seconds (10 minutes) to allow enough time for Recovery Manager to perform all necessary operations prior to the actual backup. For example, to set the BPSTART_TIMEOUT and BPEND_TIMEOUT parameters to 600 seconds (10 minutes), modify the corresponding parameters in /usr/openv/netbackup/bp.conf on the backup server as follows: BPSTART_TIMEOUT = 600 BPEND_TIMEOUT = 600 Setting Up NetBackup Configuration Parameters for the Database Server If a database is setup for High Availability (HA), then the CLIENT_NAME parameter in the /usr/ openv/netbackup/bp.conf on the database server should be set to the virtual host name of the database server instead of the physical host name. This allows a backup image to be restored to the actual database server even if the database has fail-overed to another database server. For example, to set the CLIENT_NAME parameter to a virtual host name, modify the corresponding parameter in the /usr/openv/netbackup/bp.conf on the database server as follows: CLIENT_NAME = <virtual_hostname> Setting Up NetBackup Policies for NBU (User-Managed) Backup 51

52 Setting Up NetBackup Policies for Oracle RMAN Backup The following sections describe how to set up NetBackup (NBU) policies for NBU backup with RMAN. To perform NBU backup with RMAN, you must have Symantec NetBackup for Oracle (NBU Agent for Oracle) installed on the NBU master server, Symantec NetBackup client for Oracle installed on the database server and the backup server. Refer to Symantec NetBackup for Oracle for installation and configuration instructions. In addition, you must create an Oracle RMAN Recovery Catalog and configure Oracle TNS Service and Listener to allow connections to the Recovery Catalog from the database server and backup servers. The Recovery Catalog can be created on any server. Recovery Manager for Oracle recommends that the Recovery Catalog be created on the backup server. See Creating an RMAN Recovery Catalog (page 53) for instructions. When performing NBU backup with RMAN, Recovery Manager supports full, differential, and cumulative incremental database backup. Recovery Manager also support full archive log backup (backup only archive logs). Recovery Manager for Oracle requires that you create a NBU policy for database backup. If you wish to perform archive log backup, you must create a separate NBU policy for it. NOTE: This section assumes that you are familiar with Oracle Database and Symantec NetBackup (NBU). For more information on how to create NetBackup policy, refer to Symantec NetBackup for Oracle documentation. Configuring the NetBackup Policy for Database Backup with RMAN NOTE: NBU server-side backup (initiated by the NBU scheduler) can now be used when Recovery Manager for Oracle is configured to run as either the root user or Oracle owner. Previously, NBU server-side backup was only available if Recovery Manager for Oracle was configured for the root user. NOTE: If Recovery Manager for Oracle is configured to be run as an Oracle user and this is an upgrade from previous Recovery Manager release, the rmora_config command must be run again for each database that is configured for server-side backup. NOTE: Run the script /usr/openv/netbackup/bin/oracle_link for Oracle to connect to the Oracle library on the database and backup servers to point to the Symantec NetBackup Media Library. For Recovery Manager for Oracle to perform backup and restoration correctly, you must use the following guidelines in conjunction with Symantec NetBackup documentation when configuring a NBU policy: Backup Attribute Backup Selections Backup Schedule Backup Clients Select the Oracle type for the policy. 1. Recovery Manager for Oracle will generate the RMAN backup script at the specified location when you create the configuration file. 1. Create two schedules, one for full backup and one for incremental backup (optional). For the incremental backup schedule, you can create either a differential incremental or cumulative incremental backup schedule. 2. If you wish to perform client-side database backup (initiated from Recovery Manager), set the backup window to If you also wish to perform automatic database backup (initiated from NBU), specify the backup window to fit your needs. Set the backup client to the host name of the backup server, as the backup process will actually take place on the backup server. 52 Configuring Recovery Manager for Oracle

53 Configuring the NetBackup Policy for Archive Log Backup NOTE: NBU server-side backup can be used when Recovery Manager for Oracle is configured to run as both root user and Oracle owner. NOTE: If Recovery Manager for Oracle is configured to run as an Oracle user and this is an upgrade from previous Recovery Manager for Oracle release, the rmora_config command must be run again for each database that is configured for server-side backup. This procedure is to backup archive logs only. For Recovery Manager for Oracle to perform backup and restoration correctly, you must use the following guidelines in conjunction with Symantec NetBackup documentation when configuring a NBU policy: Backup Attribute Backup Selections Backup Schedule Backup Clients Select the Oracle type for the policy. 1. Enter the location of RMAN backup script (/etc/3par/solutions/<db_server>.ora.<oracle_sid>/rmora_nbu_archbackup.sh). 2. Recovery Manager will generate the RMAN backup script at the specified location when you create the configuration file (see below for details). Recovery Manager will generate the RMAN backup script at the specified location when you create the configuration file (see Recovery Manager for Oracle Configuration Files for details). 1. Create a schedule for full backup. 2. If you wish to perform client-side archive log backup (initiated from Recovery Manager for Oracle), set the backup window to If you also wish to perform automatic archive log backup (initiated from NBU), specify the backup window to fit your needs. Set the backup client to the host name of the backup server, as the backup process will actually take place on the backup server. Creating an RMAN Recovery Catalog This section describes how to create and configure an RMAN Recovery Catalog. Refer to Oracle documentation for more detailed information. 1. Create a database for housing the Recovery Catalog. Oracle suggests the following disk space requirements: System tablespace: 100 MB Temp tablespace: 5 MB Rollback segment: 5 MB Online redo log: 1 MB (each) Recovery Catalog: 10 MB 2. Create a tablespace for the Recovery Catalog as follows: $ export ORACLE_SID=<catdb> $ export ORACLE_HOME=<oracle_home> $ sqlplus "/as sysdba" SQL> create tablespace <cat_tbs> datafile '<path/filename>' size 10M; SQL> exit where: <catdb> is the Oracle Instance ID of the Recovery Catalog. <cat_tbs> is the Recovery Catalog tablespace name. <path/filename> is the file path where the datafile is created. Setting Up NetBackup Policies for Oracle RMAN Backup 53

54 3. Create a user for the Recovery Catalog as follows: $ sqlplus "/as sysdba" SQL> create user <rman_user> identified by <rman_password> temporary tablespace temp default tablespace <cat_tbs> quota unlimited on <cat_tbs>; SQL> grant connect, resource, recovery_catalog_owner to <rman_user>; where: <tbs_name> is the tablespace name of the Recovery Catalog. <rman_user> is the user name to be granted access permission to the Recovery Catalog. <rman_password> is the password for the <rman_user>. 4. Create the RMAN Recovery Catalog tables as follows: $ rman catalog <rman_user>/<rman_password>@<catdb> RMAN> create catalog tablespace <cat_tbs>; 5. Configure TNS services for the Recovery Catalog database by adding an entry in the $ORACLE_HOME/network/admin/tnsnames.ora file on the database server and backup server as follows: <catdb> = (description = (address = (protocol = TCP) (host = <cat_host>) (port = 1521)) (connect_data = (server = dedicated) (service_name = <catdb>)) ) where <cat_host> is the host name of the host where the catalog is created. 6. Configure the Oracle listener for the Recovery Catalog database by adding an entry in the $ORACLE_HOME/network/admin/listener.ora file on the host where the Recover Catalog is created as follows: SID_LIST_LISTENER = (SID_LIST = (SID_DESC = (GLOBAL_DBNAME = <catdb>) (ORACLE_HOME = <oracle_home>) (SID_NAME = <catdb>) ) ) 7. Log in as the Oracle owner user and register the database on the database server. NOTE: If Recovery Manager for Oracle is used to run against an Oracle standby database, you must register the primary database on the primary database server instead of the standby database. $ rman target / catalog <rman_user>/<rman_password>@<catdb> RMAN> register database; 54 Configuring Recovery Manager for Oracle

55 Configure RMAN Recovery Catalog Recovery Manager for Oracle requires an Oracle RMAN recovery catalog database when using RMAN backup. To create RMAN Recovery catalog, see Creating an RMAN Recovery Catalog (page 53) When using RMAN backup with HP Data Protector, if the Oracle release of the recovery catalog database is 11g R2 or later: Ensure that the owner of the recovery catalog is granted the CREATE ANY DIRECTORY and the DROP ANY DIRECTORY system priviledges. SQL> grant CREATE ANY DIRECTORY to <recovery_catalog_user> ; SQL> grant DROP ANY DIRECTORY to <recovery_catalog_user> Ensure that the owner of the recovery catalog has SELECT permissions on v_$instance view. SQL> grant select on v_$instance to <recovery_catalog_user> ; Setting Up HP Data Protector Backup The following sections describe how to configure HP Data Protector to work with Recovery Manager for Oracle. To perform Oracle RMAN with HP Data Protector backup, you must have HP Data Protector Oracle Agent component installed on the Cell Manager, HP Data Protector client with User Interface and Oracle Integration components installed on the database servers and backup server. Refer to HP Data Protector document for installation and configuration instructions. In addition, you must create an Oracle RMAN Recovery Catalog and configure Oracle TNS Service and Listener to allow connections to the Recovery Catalog from the database server and backup servers. The Recovery Catalog can be created on any server. Recovery Manager for Oracle recommends that the Recovery Catalog be created on the backup server. For more details, see Creating an RMAN Recovery Catalog (page 53). When performing Oracle RMAN with HP Data Protector backup of a database, Recovery Manager supports full, differential, and cumulative incremental level 1 to level 4 backup. Recovery Manager also support full archive log backup (backup only archive logs). Recovery Manager for Oracle requires that you create an HP Data Protector Oracle backup specification for database backup. If you wish to perform archive log backup, you must create a separate HP Data Protector Oracle backup specification for it. NOTE: This section is intended for users familiar with Oracle Database and HP Data Protector. For more information on how to create HP Data Protector Oracle backup specification, refer to HP Data Protector documentation. NOTE: With HP Data Protector, Recovery Manager for Oracle only supports Oracle RMAN backup. File system backup using HP Data Protector is not supported. Enable Recovery Manager for Oracle Feature for HP Data Protector To enable Recovery Manager for Oracle feature for HP Data Protector: Setting Up HP Data Protector Backup 55

56 1. On HP Data Protector Cell Manager, add the following parameter to the file /etc/opt/ omni/server/options/global: Enable3ParBackupToTapeForOracle=1 2. For the change to take effect, restart HP Data Protector service. To restart the service: # /opt/omni/sbin/omnisv stop # /opt/omni/sbin/omnisv start Configuring Oracle Operating System User Account (Oracle Owner Account) The Oracle operating system user is the owner of the Oracle Home. Add the Oracle operating system user account to the HP Data Protector admin group. Following is the list of parameters that you must specify when adding the user to the HP Data Protector admin group: Group: admin Type: UNIX Name: The user name of the Oracle owner on the database server (for example: oracle) Group/Domain: <Any> Client: <Any> Figure 3 HP Data Protector User Configuration Create HP Data Protector Oracle backup specification To create an HP Data Protector Oracle backup specification, you must use the HP Data Protector user interface from Windows machine to connect to the Cell Manager. NOTE: The integration options for Recovery Manager for Oracle are not available on the HP Data Protector Java graphical user interface on the UNIX Cell Manager. You can create an Oracle backup specification using online, offline or datafile template. For online or datafile backup, the database must be online (OPEN) when the backup occurs. For offline backup, the database must be offline (CLOSED) when the backup occurs. 56 Configuring Recovery Manager for Oracle