Hp 3PAR Application Software Suite for Oracle Instrukcja Użytkownika

Przeglądaj online lub pobierz Instrukcja Użytkownika dla Przechowywanie Hp 3PAR Application Software Suite for Oracle. HP 3PAR Application Software Suite for Oracle User Manual Instrukcja obsługi

  • Pobierz
  • Dodaj do moich podręczników
  • Drukuj
Przeglądanie stron 0
HP 3PAR Recovery Manager 4.5.0 Software
for Oracle
User Guide
Abstract
This document provides the information needed to install, configure, and use the HP 3PAR Recovery Manager 4.5.0 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™ and Oracle11g™ Databases.
HP Part Number: QL226-97705
Published: February 2014
Przeglądanie stron 0
1 2 3 4 5 6 ... 222 223

Podsumowanie treści

Strona 1 - User Guide

HP 3PAR Recovery Manager 4.5.0 Softwarefor OracleUser GuideAbstractThis document provides the information needed to install, configure, and use the HP

Strona 2

To ensure that the database is running in automatic archive log mode, use SQL*Plus utility to ensurethe Database log mode is Archive Mode and that Aut

Strona 3 - Contents

NOTE: Recovery Manager for Oracle must be pre-configured on the local backup server priorto executing rmora_rsync with the -l option.100 Using the Rec

Strona 4 - 4 Contents

-o onlineCreate an online database Virtual Copy in Remote Copy or Synchronous Long Distanceconfiguration. The specified database instance must be onli

Strona 5 - Contents 5

rmora_setSYNTAXrmora_set -s <oracle_sid> -p <db_server> -t <timestamp>[-r <time> d|D|h|H] [-f] [-e <time> d|D|h|H>] [

Strona 6 - 6 Contents

• The retention time set during configuration time serves as the default value all Virtual Copiescreated thereafter.• The retention time can be specif

Strona 7 - Searching the Online Help

rmora_umountSYNTAXrmora_umount -s <oracle_sid> -p <db_server> -t <timestamp> [-f] [-v]DESCRIPTIONThe rmora_umount command unmounts a

Strona 8 - Virtual Copies

5 Using the Recovery Manager for Oracle Graphical UserInterfaceThe following section describes how to use the GUI to perform specific operations relat

Strona 9 - Interacting with Oracle

4. Press ENTER.NOTE: It is a known issue that the mouse events are not captured correctly on the cygwinx-server for Java6.Stopping the GUITo stop the

Strona 10

3. Select the desired options from the Backup Method group box.• Online (Hot) backup - The involved database instance must be open for this operation.

Strona 11

NOTE: You can configure the Virtual Copy policy by using either a time or numeric-based policy.HP recommends using a time-based policy instead of a nu

Strona 12

6. (Optional) Select Default retention time and enter a numeric value from 1 to 1,825 (Days) or1 to 43,800 (Hours) in the adjacent field to set the nu

Strona 13

For NBU backup and restoration, Recovery Manager for Oracle interacts directly with NBU totrigger the backup or restore process. Recovery Manager for

Strona 14

Mounting a Virtual CopyAfter a Virtual Copy is created, it can be mounted on the backup server where the RecoveryManager for Oracle GUI is running.To

Strona 15

Viewing Rollback StatusIt may take several minutes to rollback a Virtual Copy depending on its size.To view a Virtual Copy’s rollback status:1. Right-

Strona 16 - The Database Cloning Utility

Restoring Archive Log, Datafiles, and TablespacesNOTE: If Symantec NetBackup (NBU) is used to back up datafiles, NBU can be used to restoredatafiles t

Strona 17 - The Virtual Copy Repository

database, or to clone the database for testing, decision making, and report generating purposes.The cloning capability takes the workload out of the d

Strona 18 - Virtual Copy Policy

Starting SynchronizationTo start synchronization on a Remote Copy node:1. Right-click a Remote Copy node on the navigation tree and click Create Virtu

Strona 19 - The Database Backup Utility

Destination Only option. After the Virtual Copy creation is completed, the database istaken out of backup mode.• Archive Log Destination Only - The in

Strona 20 - Client-side Backup

The event messages for Recovery Manager for Oracle appear in a web browser.For more information about event messages, see “Troubleshooting” (page 160)

Strona 21 - Server-side Backup

6 Using the Recovery Manager Rollback UtilityRecovery Manager for Oracle provides a way to rollback a database to a point-in-time image bypromoting a

Strona 22

4. From the database server, deport/export the database volume groups if volume groups arein use.Depends on volume groups involved, the deport/export

Strona 23

9. From the database server, activate logical volumes and import/start volume groups.Example:- For Symantec VxVM volume groups:# vxdg import <diskg

Strona 24

The Virtual Copy Creation UtilityThe Virtual Copy creation utility (rmora_create command) of HP 3PAR Recovery ManagerSoftware for Oracle creates an on

Strona 25 - Converting Virtual Volumes

3. From the backup server, unmount the ASM diskgroups contained in the read-write virtual copyvolumes if ASM is in use.Example:SQL> alter diskgroup

Strona 26

# vxvol -g myvxvmdb_datadg startall- For HP-UX logical volume groups, using the tmpfile generated during vgexport:# vgimport -m <tmpfile> <

Strona 27 - Preinstallation Requirements

Option:2 Using ascii control fileModify the backed up ascii control file, and the format is as follows:STARTUP NOMOUNTCREATE CONTROLFILE REUSE DATABAS

Strona 28

7 Using Remote Copy with Recovery ManagerOverviewHP 3PAR Remote Copy Software helps you safeguard against disasters by copying (synchronizing)virtual

Strona 29

How Remote Copy WorksA Remote Copy configuration typically involves two HP 3PAR StoreServ Storage systems: a localor primary system and a remote or se

Strona 30 - Installation

Figure 5 Asynchronous Periodic Remote Copy ConfigurationA Remote Copy configuration can also be configured as a Synchronous Long Distance configuratio

Strona 31 - Verifying Installation

Figure 6 Synchronous Long Distance Remote Copy ConfigurationCreating Virtual CopiesTo create Virtual Copies, use the rmora_rsync command or the Recove

Strona 32

8 Support and Other ResourcesContacting HPFor worldwide technical support information, see the HP support website:http://www.hp.com/supportBefore cont

Strona 33

See:For information about:HP 3PAR-to-3PAR Storage Peer Motion GuideMigrating data from one HP 3PAR storage system to anotherHP 3PAR Secure Service Cus

Strona 34

See:For information about:Planning for HP 3PAR storage system setupHardware specifications, installation considerations, power requirements, networkin

Strona 35

An archive log Virtual Copy is created while the database is OPEN and performs the followingactions:• Discovers devices (HP 3PAR virtual volumes) used

Strona 36

Typographic conventionsTable 1 Document conventionsElementConventionBold text• Keys that you press• Text you typed into a GUI element, such as a text

Strona 37

9 Documentation feedbackHP is committed to providing documentation that meets your needs. To help us improve thedocumentation, send any errors, sugges

Strona 38

A Case Study: Remote Copy with Recovery Manager forOracleIntroductionHP 3PAR Recover Manager Software for Oracle provides a utility, rmora_rsync, whic

Strona 39

oracleasm-support-2.1.4-1.el5oracleasmlib-2.0.4-1.el5The database ASM11GR2 uses SPFILE, which is located on one of the ASM disk groups.$cat initASM11G

Strona 40 - SSH Restrictions

2. Create Remote Copy groups on the local storage system S256:# creatercopygroup linux_asm11gr2_data S347:sync S336:periodic# creatercopygroup linux_a

Strona 41

Checking database status ...Discovering database devices ...Retrieving database Remote Copy group(s) ...Archiving online redo logs ...Putting the data

Strona 42

1. Failover to the synchronous storage system S347.If the Remote Copy groups have not been stopped, stop the groups on S256 by issuing thefollowing:#

Strona 43

Name Target Status Role Mode Optionslinux_asm11gr2_arch.r256 S256 Stopped Secondary SyncLocalVV

Strona 44

a. From the remote synchronous system S347, issue the following commands to failover thedatabase ASM11GR21 related Remote Copy groups to S347:# setrco

Strona 45

c. After failover, any LUNs associated with volumes on storage system S347 will becomewritable by the connected host panther. If VLUNs have not yet be

Strona 46

The Virtual Copy Mount UtilityThe Virtual Copy mount utility of HP 3PAR Recovery Manager Software for Oracle mounts anexisting database Virtual Copy t

Strona 47

2. Recover the Remote Copy groups from the synchronous storage system S347.• The recover operation initiates reverse replication and synchronizes the

Strona 48

On S347:Name Target Status Role Mode Optionslinux_asm11gr2_arch.r256 S256 Started Primary-Rev SyncLocalVV

Strona 49

From this output, note that the Status and Role of the three Remote Copy groups withtarget S356 are Started and Primary-Rev, respectively.On S256:Name

Strona 50

3. Restore the Remote Copy groups from the synchronous storage system S347.• The restore operation restores the replication for the Remote Copy groups

Strona 51

On S347:Name Target Status Role Mode Optionslinux_asm11gr2_arch.r256 S256 Started Secondary SyncLocalVV

Strona 52

In the output , note that the Status and Role of the three Remote Copy groups on S347are Started and Secondary, respectively.On S256:Name

Strona 53

4. Recover the RAC database ASM11GR2.Assume the Oracle binary is available and CRS is up. Mount all necessary file systems if thefile systems are used

Strona 54

The best recovery option is recovering from the asynchronous periodic backup system S336. Torecover, perform the following sequence of actions:• Perfo

Strona 55

1. Failover to the asynchronous periodic backup system S336.If the Remote Copy groups have not been stopped, stop the groups on S256 by issuing thefol

Strona 56

Name Target Status Role Mode Optionslinux_asm11gr2_arch.r256 S256 Stopped Primary-Rev Periodic over_per_al

Strona 57 - ◦ Ownership:

instance. If no ASM instance is up on the backup server, an ASM instance is started upon the backup server, and all ASM disk groups in the Virtual Cop

Strona 58

2. Clone the database on the remote backup server using the desired Virtual Copy.a. Mount the Virtual Copy; in this example, Virtual Copy 060311173319

Strona 59

3. Back up the binary control file from the cloned database and prepare to rollback the VirtualCopy.a. Issue the RMAN command to backup the control fi

Strona 60

4. Rollback the read-write Virtual Copy to the base volumes from the remote system S336. Promotethe read-write Virtual Copy to its base volume by issu

Strona 61

5. Recover the Remote Copy groups from the asynchronous periodic backup system S336 to thelocal system S256.The recover operation initiates reverse re

Strona 62

On S336Name Target Status Role Mode Optionslinux_asm11gr2_arch.r256 S256 Started Primary-Rev Periodic Last-Sync 20

Strona 63

From this output, note that the role of the Remote Copy groups from S336 arePrimary-Rev.S256:Name Target Status Role Mod

Strona 64 - Configuration

6. Restore the Remote Copy groups from the asynchronous periodic system S336.The restore operation restores the replication for the remote copy groups

Strona 65

From this output, note that the Status and Role of the Remote Copy groups on S336are Started and Secondary, respectively.S256:Name Targ

Strona 66

7. Bring up the primary database from the database server.a. Bring up the +ASM1 instance from the node dl160g6-13, mount all diskgroups, andcreate a n

Strona 67

[vcdba@dl160g6-13 ~]$ sqlplus '/as sysdba'SQL*Plus: Release 11.2.0.1.0 Production on Thu Jun 9 21:59:32 2011Copyright (c) 1982, 2009, Oracle

Strona 68 - Recovery Manager Commands

• Once exported, the Virtual Copy on the alternate backup server can be mounted, unmounted,backed up, and restored.• Once the exported Virtual Copy is

Strona 69 - Recovery Manager Commands 69

B TroubleshootingThis appendix provides Recovery Manager for Oracle error messages, their explanations, andappropriate actions.MESSAGE ID1003SYMBOLIC

Strona 70

3PAR1007: ERROR: Cannot determine archive log mode for database <name>.REASONFailed to retrieve the archive log mode for the specified database.

Strona 71 - Recovery Manager Commands 71

SYMBOLIC NAMERMO_ERROR_MULTIPLE_PARTITIONMESSAGE3PAR1012: ERROR: Disk <disk ID> has multiple partitions.REASONIn Linux, the specified disk has m

Strona 72

Failed to retrieve the hostname defined in the HP 3PAR StoreServ Storage system for the backupsystem.SOLUTIONAn attempt to retrieve the host definitio

Strona 73

RMO_ERROR_BKUP_TAG_NOT_SPECIFIEDMESSAGE3PAR1021: ERROR: Backup tag not specified.REASONUsing RMAN to backup the Virtual Copy to media with NetBackup,

Strona 74

RMO_ERROR_ENVVAR_NOTFOUNDMESSAGE3PAR1026: ERROR: Environment variable <environment variable name> is not set.REASONTo access the HP 3PAR StoreSe

Strona 75

MESSAGE ID1032SYMBOLIC NAMERMO_ERROR_OSDEVS_NOTFOUNDMESSAGE3PAR1032: ERROR: Could not find OS devices for virtual volumes <names>REASONThe comma

Strona 76

When trying to retrieve archive log destinations, one or more archive log destination were foundwith "ERROR" status.SOLUTIONMake sure all ar

Strona 77 - Recovery Manager Commands 77

3PAR1054: ERROR: Invalid argument.REASONrmora_exec or tpdcli_exec received an invalid argument.SOLUTIONVerify the configuration file contains all para

Strona 78

Make sure the mnttab contains the file system for the specified file or directory. Contact customersupport for further investigation.MESSAGE ID1062SYM

Strona 79 - Recovery Manager Commands 79

The cloned database is shutdown with the shutdown immediate option. The database relatedfiles (Oracle parameter file, control files and redo logs), wh

Strona 80

MESSAGE3PAR1066: ERROR: Archive logs and datafiles are on the same ASM disk group.REASONRecovery Manager requires datafiles and archive log destinatio

Strona 81 - Recovery Manager Commands 81

MESSAGE ID1072SYMBOLIC NAMERMO_ERROR_DB_NOT_RUNNINGMESSAGE3PAR1072: ERROR: Oracle instance <name> is not currently running.Use -f option to forc

Strona 82

Make sure all parameters in the configuration file are up to date. Make sure the HP 3PAR StoreServStorage system is functioning properly. Contact cust

Strona 83 - Recovery Manager Commands 83

MESSAGE3PAR1097: ERROR: Could not find Virtual Copy device for <Virtual Copy name>.REASONThe command rmora_mount failed to find the OS device fo

Strona 84

REASONFailed to use the command oracleasm deletedisk to delete the specified Oracle asmlib disk.SOLUTIONMost likely the disk is still busy. Check the

Strona 85 - EXAMPLES

Either remove one or more Virtual Copies, or increase the number in the configuration file byrunning rmora_config or the GUI to modify the configurati

Strona 86

RMO_ERROR_NONE_RCVV_FOUNDMESSAGE3PAR1109: ERROR: There is no Remote Copy volumes found on HP 3PAR StoreServ Storage system<name>.REASONCould not

Strona 87 - Recovery Manager Commands 87

RMO_ERROR_UNKNOWN_BACKUP_MODEMESSAGE3PAR1112: ERROR: Unknown backup mode <mode>.REASONThe error occurs when NetBackup calls the bpstart_notify.p

Strona 88

SOLUTIONCheck the log file for more information. Make sure TPDSYSNAME and TPDUSERNAME are setcorrectly from the configuration file. Make sure the HP 3

Strona 89 - Recovery Manager Commands 89

REASONThe specified Remote Copy group must be started in order to run the rmora_rsync command.SOLUTIONStart the Remote Copy group. Refer to the HP 3PA

Strona 90

If a Virtual Copy has been backed up, the remove repository utility command fails unless the -foption is used.Virtual Copy PolicyHP 3PAR Recovery Mana

Strona 91

MESSAGE ID1133SYMBOLIC NAMERMO_ERROR_CREATE_GROUPSVMESSAGE3PAR1133: ERROR: Could not create group of snapshot volumes.REASONRecovery Manager for Oracl

Strona 92

Cannot determine the HP 3PAR OS version.SOLUTIONRun the showversion command against the HP 3PAR StoreServ Storage system to see what theerror is. Make

Strona 93 - Recovery Manager Commands 93

REASONThe command rmora_umount failed to unmount the specified file system.SOLUTIONManually unmount the file system and rerun rmora_umount with the -f

Strona 94

REASONThe volume used by the Oracle database, which belongs to either datafiles or archive logdestinations, could not be found in any Remote Copy grou

Strona 95 - SYNOPSIS

Make sure the backup type (online/offline/archlog/datafile) contains the specified file. Contactcustomer support for further investigation.MESSAGE ID1

Strona 96

REASONIn Linux, Recovery Manager for Oracle failed to bind a raw device in file/etc/sysconfig/rawdevices.SOLUTIONCheck the log file. Contact customer

Strona 97 - Recovery Manager Commands 97

MESSAGE ID1158SYMBOLIC NAMERMO_ERROR_ROLLBACK_TASK_NOTFOUNDMESSAGE3PAR1158: ERROR: Could not find rollback task with task ID <task ID>.REASONDur

Strona 98

MESSAGE3PAR1162: ERROR: ASM rebalancing operation is in progress.REASONBefore Recovery Manager for Oracle creates a Virtual Copy for the datafile volu

Strona 99 - Recovery Manager Commands 99

Trying to execute rmora_rmrep to remove the backup repository for a database configurationfailed as one or more Virtual Copy repositories still exist.

Strona 100

RMO_ERROR_SYNCRCOPYMESSAGE3PAR1170: ERROR: Could not perform synchronization for RC group <Remote Copy group name>.REASONSynchronization for the

Strona 101 - Recovery Manager Commands 101

Recovery Manager for Oracle saves an ASCII control file and a binary control file for each createdVirtual Copy in its repository. After a rollback, yo

Strona 102 - Description

Check the mapping file in the repository to see if it contains the specified datafile, and check ifthe file system for this datafile is mounted.MESSAG

Strona 103 - Recovery Manager Commands 103

MESSAGE3PAR1179: ERROR: Oracle user '%s' not found on the backup server.REASONEven Oracle home on the backup server is not specified, the sa

Strona 104 - DESCRIPTION

Follow the instructions in the HP 3PAR Recovery Manager for Oracle User Guide to configure theSSH connection.MESSAGE ID1186SYMBOLIC NAMERMO_ERROR_CONN

Strona 105 - Interface

REASONDuring the process of rmora_createdb, Recovery Manager for Oracle failed to generateinit.ora to clone the database.SOLUTIONCheck the log file fo

Strona 106 - Removing Configuration Files

MESSAGE3PAR1201: ERROR: Could not parse location entered.REASONRecovery Manager for Oracle has trouble understanding and parsing the <loc> argum

Strona 107

SOLUTIONCheck the primary database and make sure the two parameters are set correctly. You can manuallycorrect the problem in the init.ora file saved

Strona 108

3PAR1215 ERROR: Unrecognized UUID format: %s.REASONIn Linux, the output from the command dmsetup info devicename contains unrecognizedUUID.SOLUTIONChe

Strona 109

RMO_ERROR_UNSUPPORTED_RETENTEXPMESSAGE3PAR1219: ERROR: Current HP 3PAR OS version does not support volume retention/expiration.REASONRecovery Manager

Strona 110 - Unmounting a Virtual Copy

MESSAGE ID1224SYMBOLIC NAMERMO_ERROR_ASMLIB_NOT_INSTALLMESSAGE3PAR1224: ERROR: Oracle ASMLib has not been installed.REASONIn Linux, the required file

Strona 111 - Backing up a Virtual Copy

3PAR1227: ERROR: Virtual volume with WWN <WWN> not found from the HP 3PAR StoreServStorage system.REASONThe process to discover virtual volumes

Strona 112 - Cloning a Database

© Copyright 2014 Hewlett-Packard Development Company, L.P.Confidential computer software. Valid license from HP required for possession, use or copyin

Strona 113 - Database Synchronization

The following restrictions apply when backing up a database using the Recovery Manager forOracle database backup utility.• For NBU (user-managed) back

Strona 114 - Backing Up a Database

REASONFailed to run the HP 3PAR CLI command showport.SOLUTIONMake sure the SSH connection from the current server to the specified HP 3PAR StoreServ S

Strona 115 - Viewing Event Messages

SYMBOLIC NAMERMO_ERROR_RETRIEVE_CONTROLLERMESSAGE3PAR1234: ERROR: Could not retrieve FC controller information.REASONFailed to run the OS command cfga

Strona 116 - Viewing Online Help

instance on the backup server, all disk groups that are not used by the cloned database shouldbe dismounted.SOLUTIONDismount all diskgroups that are c

Strona 117 - # umount /oradata

3PAR1241: ERROR: One or more ASM disk groups are shared between databases.REASONRecovery Manager for Oracle requires that an ASM disk group be exclusi

Strona 118

RMO_ERROR_PARSE_FILEMESSAGE3PAR1245: ERROR: Could not parse file '%s'.REASONAn error occurred either during the creation of Virtual Copy tim

Strona 119

RMO_ERROR_RETRIEVE_ARCHDESTMESSAGE3PAR1249: ERROR: Could not retrieve archive log destination.REASONFailed to run the SQL command to retrieve the phys

Strona 120

MESSAGE ID1253SYMBOLIC NAMERMO_ERROR_REMOUNT_FSMESSAGE3PAR1253: ERROR: Could not re-mount file system <file system name> on host <host name&g

Strona 121

Check the log file to get more details. Make sure VxVM is in a valid state. Contact customer supportfor further investigation.MESSAGE ID1258SYMBOLIC N

Strona 122

If the host adapter type is not within the supported types (see the HP 3PAR configuration matrix),Recovery Manager for Oracle will not be able to resc

Strona 123 - Overview

MESSAGE3PAR1265: ERROR: Could not query for the Flash Recovery Area (FRA) location.REASONThe command rmora_restore failed to retrieve the value from t

Strona 124 - How Remote Copy Works

For NBU (user-managed) backup, Recovery Manager for Oracle:• Generates an include list file that contains a list of datafiles and/or archive log desti

Strona 125 - How Remote Copy Works 125

MESSAGE ID1269SYMBOLIC NAMERMO_ERROR_BACKUP_FAILUREMESSAGE3PAR1269: ERROR: Backup process <process name> for database <database name> comp

Strona 126 - Creating Virtual Copies

REASONTrying to clone a database using the specific Virtual Copy fails as it only contains datafiles. AVirtual Copy created with the datafile type occ

Strona 127 - 8 Support and Other Resources

1. Cloning database is only available to online or offline Virtual Copies.2. Restore files which requires later recovery operations cannot be a archiv

Strona 128

3PAR1278: ERROR: The database unique name is different from the Virtual Copy.The control file from the backup is not compatible with the current datab

Strona 129

SOLUTIONMake sure TPDSYSNAME and TPDUSERNAME to access the specified HP 3PAR StoreServ Storagesystem are correct. Make sure the Remote Copy is set up

Strona 130 - HP 3PAR branding information

RMO_ERROR_OPEN_DBMESSAGE3PAR1303: ERROR: Could not open database instance <name>.REASONThe operation to clone a database failed. A cloned databa

Strona 131 - 9 Documentation feedback

On the backup server, Oracle asmlib configuration file (/etc/sysconfig/oracleasm, whichlinks to /etc/sysconfig/oracleasm-_dev_oracleasm) has “dm” spec

Strona 132 - Introduction

SOLUTION• Make sure the current user has write permission to the repository directory /etc/3par/solutions/<db_server>_ora_<oracle_sid> on

Strona 133 - Configuration Diagram

MESSAGE3PAR1316: ERROR: Could not activate volume group <group>.REASONThe LVM vgchange command, which is used to activate the snapshot volume gr

Strona 134

RMO_ERROR_REMOVE_VGMESSAGE3PAR1320: ERROR: Could not remove LVM volume group <group>.REASONThe LVM vgremove command, which is used to remove a s

Strona 135 - Unavailable

NOTE: The bpstart_notify and bpend_notify scripts are generated at/usr/openv/netbackup/bin during the creation of the Recovery Manager Configuration f

Strona 136

Make sure the NetBackup master server specified in Recovery Manager for Oracle configurationfile is reachable. The specified NetBackup policy can be q

Strona 137

RMO_ERROR_SYNCMODE_NOTSAMEMESSAGE3PAR1351: ERROR: Synchronization mode modename for datafile group is different from themode modename for archive log

Strona 138 - Primary-Rev

IndexAarchive log backupconfiguring NBU policy, 50Bbackup server to database server verification, 42backup server to HP 3PAR StoreServ Storage system

Strona 139

requirementsstandby databases, 10restrictions with SSH, 40RMAN recovery catalog creation, 47, 52rmora_create, 78rmora_createdb, 82rmora_display, 84rmo

Strona 140

be retrieved using the Recovery Manager display utility (see “The Virtual Copy Display Utility”(page 13)).For an NetBackup (user-managed) restoration,

Strona 141

In addition to the current Recovery Manager for Oracle’s limitations and restrictions when runningagainst an Oracle primary database, the following li

Strona 142

synchronous, asynchronous periodic mode, and Synchronous Long Distance Remote Copy. Seethe HP 3PAR Remote Copy Software User's Guide for addition

Strona 143

Running Recovery Manager for Oracle on Japanese OSCAUTION: For full compatibility with Recovery Manager for Oracle, you must use English-languagenamin

Strona 144

2 Installing and Uninstalling Recovery ManagerThis chapter describes how to install, verify, and remove HP 3PAR Recovery Manager Softwarefor Oracle on

Strona 145

• If you are using Symantec NetBackup1:HP recommends that you use the backup server as the NetBackup master server.◦◦ The Symantec NetBackup client mu

Strona 146

◦ 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 v

Strona 147

ContentsOnline Help for HP 3PAR Recovery Manager Software for Oracle...71 Overview of Recovery Manager Operations...

Strona 148

Installing Recovery Manager for Oracle on Linux SystemsUse the instructions in this section to install or upgrade Recovery Manager for Oracle on theda

Strona 149

Allow RMOra to be run with 'oracle:oinstall' (y/n)?yInstallation completed.5. After the installation is complete on all the required servers

Strona 150

Installing Recovery Manager for Oracle on Solaris SystemsUse the instructions in this section to install or upgrade Recovery Manager for Oracle on the

Strona 151

Removing Recovery Manager from Solaris SystemsTo remove HP 3PAR Recovery Manager from a Solaris system:1. Log on as the root user.2. Insert the HP 3PA

Strona 152

4. Enter ./rmora_install.sh.The prompts and output from running rmora_install.sh are similar to those when runningrmora_install.sh on Linux. If necess

Strona 153

Installing Recovery Manager for Oracle on IBM AIX SystemsUse the instructions in this section to install Recovery Manager for Oracle on the database a

Strona 154

SUCCESSES--------- Filesets listed in this section passed pre-installation verification and will be installed. Selected Filesets -----------------

Strona 155 - Secondary-Rev

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

Strona 156

4. Enter ./rmora_uninstall.sh.Confirm you want to uninstall Recovery Manager for Oracle when prompted.Welcome to HP 3PAR Recovery Manager for OracleCh

Strona 157

3 Configuring Recovery Manager for OracleRecovery Manager for Oracle requires that an SSH connection be configured for the backup server,the database

Strona 158

Installation...33Verifying Instal

Strona 159

Figure 2 SSH Connection Relationship for Remote Copy SupportSSH RestrictionsRecovery Manager for Oracle has the following SSH restrictions:• The ssh a

Strona 160 - B Troubleshooting

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 nob. I

Strona 161 - MESSAGE ID

Setting Up Connections from the Backup Server to the Database ServerTo set up an SSH connection from the backup server to the database server:• Copy t

Strona 162

yes Warning: Permanently added '<NBU_master>' (DSS) to the list of known hosts.where <user> is either the root or the Oracle ow

Strona 163

4. Copy the public key of the backup server to the HP 3PAR StoreServ Storage system. You canfind the public key in the location specified when generat

Strona 164

Setting Connections from the Database Server to the HP 3PAR StoreServ StorageSkip this step if the database server has the same SSH key pair as the SS

Strona 165

4. Copy the public key of the database server to the HP 3PAR StoreServ Storage system.<db_server># ssh <username>@<ss_name><usern

Strona 166

Setting up National Language Host SupportThe Recovery Manager for Oracle message catalog and the symbolic link are installed in thefollowing locations

Strona 167

1. Create a database for housing the Recovery Catalog. Oracle suggests the following diskspace requirements:• System tablespace: 100 MB• Temp tablespa

Strona 168

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 w

Strona 169

rmora_chown...73rmora_config...

Strona 170

Backup Schedule 1. Create a schedule for full backup.2. If you wish to perform client-side database backup (initiated from Recovery Manager), set theb

Strona 171

Setting Up NetBackup Policies for Oracle RMAN BackupThe following sections describe how to set up NetBackup (NBU) policies for NBU backup withRMAN.To

Strona 172

Configuring the NetBackup Policy for Archive Log BackupNOTE: NBU server-side backup can be used when Recovery Manager for Oracle is configuredto run a

Strona 173

3. Create a user for the Recovery Catalog as follows:$ sqlplus "/as sysdba"SQL> create user <rman_user> identified by <rman_pass

Strona 174

Configure RMAN Recovery CatalogRecovery Manager for Oracle requires an Oracle RMAN recovery catalog database when usingRMAN backup. To create RMAN Rec

Strona 175

1. On HP Data Protector Cell Manager, add the following parameter to the file /etc/opt/omni/server/options/global:Enable3ParBackupToTapeForOracle=12.

Strona 176

NOTE: Recovery Manager for Oracle will not automatically shutdown the database beforeperforming the backup.Datafile backup is not useful if backup of

Strona 177

• Backup Specification Option:Pre-exec:◦– Pre-exec: Specifiy DP_pre.<backup_specification_name>.– On client: The host name of the Recovery Manag

Strona 178

ORbackup format 'backup_specification <app_name_%s:%t:%p>.dbf archivelog all not backed up 1 times skip inaccessible;• If control file ob

Strona 179

Recovery Manager for Oracle Configuration FilesFor each database to be managed by Recovery Manager for Oracle, a configuration file must becreated fir

Strona 180

Rollback Using a Database Read-Only Virtual Copy...117Rollback Using a Database Read-Write V

Strona 181

• Oracle Home of ASM instance on the database server [h=help,q=quit]?Recovery Manager for Oracle detects if the specified Oracle instance is managed b

Strona 182

NOTE: If the database volumes do not belong to any domain, then the retention time of theread-only Virtual Copy cannot exceed the VVRetentionTimeMax v

Strona 183

• Remove Virtual Copy after backup complete? [y=yes,n=no,q=quit]?Enter n if you do not want to remove the Virtual Copy after a backup is completed suc

Strona 184

You will be prompted with this question only if you previously selected Oracle RMAN withHP Data Protector as the third-party backup tool.• NetBackup f

Strona 185

6. Click Finish.If Recovery Manager for Oracle successfully connects to the database, it retrieves the databasetablespaces, datafiles, the archive log

Strona 186

• Oracle Home of the database instance on the database server[h=help,q=quit]?Recovery Manager for Oracle provides a default value for the ORACLE_HOME

Strona 187

• Enter Virtual Copy retention time in days(d|D) or hours(h|H)[h=help,s=skip,q=quit]?Specifies the amount of time relative to the creation time that t

Strona 188

Creating a Recovery Manager for Oracle Configuration File using the GUITo use the Recovery Manager for Oracle GUI to create a configuration file with

Strona 189

4 Using the Recovery Manager Command Line InterfaceThis chapter describes the Recovery Manager for Oracle command line utilities.NOTE: The command lin

Strona 190

method, a database can be backed up to a local disk (Symantec NetBackup or HP Data Protectoris not required) or to a tape using Symantec NetBackup or

Strona 191

Online Help for HP 3PAR Recovery Manager Software forOracleWelcome to the online help for HP 3PAR Recovery Manager Software for Oracle.Searching the O

Strona 192

backup (archlog). Refer to Recovery Manager User's Guide for detail on how to create HPData Protector Backup Specification.Depending on which bac

Strona 193

The host name of the database server, on which the Oracle database instance is running. Thevalue of the database server name must match the output of

Strona 194

This option is only applicable for Oracle RMAN with HP Data Protector backup. This option canbe used with the -o online|offline|datafile option to per

Strona 195

rmora_checkconfigSYNTAXrmora_checkconfig -s <oracle_sid> -p <db_server>[-o all|skipdatabase|databaseonly] [-v]DESCRIPTIONThe rmora_checkco

Strona 196

changes the permissions and owners of the necessary files and directories in order to enable anOracle binary owner to operate Recovery Manager for Ora

Strona 197

rmora_configSYNTAXrmora_config [-s <oracle> -p <db_server> [-l]]DESCRIPTIONThe rmora_config command creates or modifies the Recovery Manag

Strona 198

the current time, that the volume will be retained. To specify a retention time, specify a valuebetween 1 to 43,800 hours (1825 days).Retention time c

Strona 199

• DBFILE_SCHED_FULL - The Symantec NetBackup schedule name for database backup. Thisparameter is applicable only to the Symantec NetBackup backup meth

Strona 200

rmora_createSYNTAXrmora_create -s <oracle_sid> -p <db_server>[ -o online|offline|datafile|archlog][ -r <retention_time>{d|D|h|H} -f]

Strona 201

When creating an online or datafile Virtual Copy:• If the specified database instance is a regular database, the database will be temporarily putinto

Strona 202

1 Overview of Recovery Manager OperationsRecovery Manager for Oracle offers a specific data protection solution that has been enhancedto provide rapid

Strona 203

• If the Oracle database is an RAC database, all RAC instances must share the same archivelog destinations (i.e., the same cluster file system or the

Strona 204

NOTE: If the database volumes do not belong to any domain, then the retention time of theread-only Virtual Copy cannot exceed the VVRetentionTimeMax v

Strona 205

rmora_createdbSYNTAXrmora_createdb -s <oracle_sid> -p <db_server> -t <timestamp>[-n <clone_sid>] [-h <clone_ora_home>][-

Strona 206

OPTIONSThe following options are supported:-s <oracle_sid>The Oracle SID of the database instance. For Real Application Cluster (RAC) database,

Strona 207

rmora_displaySYNTAXrmora_display -s <oracle_sid> -p <db_server> [-t <timestamp>] [-r]DESCRIPTIONThe rmora_display command displays d

Strona 208

The timestamp of a Virtual Copy. It is also the name of the Virtual Copy. The default behavior isto display all Virtual Copies.-rDisplays the Virtual

Strona 209

rmora_exportSYNTAXrmora_export -s <oracle_sid> -p <db_server> -t <timestamp>-r <alt_backup_server> -e <alt_tpdusername>[

Strona 210

HP 3PAR StoreServ Storage system user can be created using the HP 3PAR Operating SystemSoftware CLI createuser command. The created user must be assig

Strona 211

rmora_mountSYNTAXrmora_mount -s <oracle_sid> -p <db_server> -t <timestamp>[-m <mountpoint>] [-r] [-v]DESCRIPTIONThe rmora_moun

Strona 212

• Imports snapshot LVM volume groups and activates all corresponding LVM snapshot volumesif the database files reside on LVM volumes.• For Virtual Cop

Strona 213

where:• <db_server> is the host name of the database server.• <oracle_sid> is the Oracle SID of the database instance.The following exampl

Strona 214

rmora_removeSYNTAXrmora_remove -s <oracle_sid> -p <db_server> -t <timestamp> [-v]DESCRIPTIONThe rmora_remove command removes a datab

Strona 215

rmora_removedbSYNTAXrmora_removedb -s <oracle_sid> -p <db_server> -t <timestamp>[-n <clone_sid>] [-h <clone_ora_home>] [

Strona 216

rmora_restoreSYNTAXrmora_restore -s <oracle_sid> -p <db_server> [-t <timestamp>][-T <tablespaces>] [-D <dbf1,dbf2,...>]

Strona 217

image cannot be seen from the Recovery Catalog from the primary (production) database.To restore, the following steps must be performed manually:◦ The

Strona 218

-t <timestamp>The timestamp of a Virtual Copy whose backup image is used for restoration. Use thermora_display command to retrieve a list of the

Strona 219

rmora_rmrepSYNOPSISrmora_rmrep -s <oracle_sid> -p <db_server> [-t <timestamp>] [-f] [-v]DESCRIPTIONThe rmora_rmrep command removes a

Strona 220

rmora_rollbackSYNOPSISrmora_rollback -s <oracle_sid> -p <db_server> -t <timestamp>[-o data|arch] [-v] [-w] [-f]DESCRIPTIONThe rmora_

Strona 221

The corresponding host name of the database server where the specified Oracle database instanceis running. The value of the database server name must

Strona 222 - 222 Index

rmora_rsyncSYNTAXrmora_rsync -s <oracle_sid> -p <db_server> [-l <local_backup_server>][ -o online|offline|validate] [ -r <retenti

Strona 223

To use the rmora_rsync command, the following requirements must be satisfied:• Each database instance must be started up using either a parameter file

Komentarze do niniejszej Instrukcji

Brak uwag