Hp 3PAR Application Software Suite for Oracle License Bedienungsanleitung

Stöbern Sie online oder laden Sie Bedienungsanleitung nach Computerzubehör Hp 3PAR Application Software Suite for Oracle License herunter. HP 3PAR Application Software Suite for Oracle Licenses User Manual Benutzerhandbuch

  • Herunterladen
  • Zu meinen Handbüchern hinzufügen
  • Drucken
  • Seite
    / 199
  • Inhaltsverzeichnis
  • FEHLERBEHEBUNG
  • LESEZEICHEN
  • Bewertet. / 5. Basierend auf Kundenbewertungen
Seitenansicht 0
HP 3PAR Recovery Manager 4.3.0 Software
for Oracle
User Guide
Abstract
This document provides the information needed to install, configure, and use the HP 3PAR Recovery Manager 4.3.0 Software
for Oracle on Solaris, Red Hat Linux, Oracle Linux, and HP UX. 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 are familiar with the Oracle10g™ and Oracle11g™ Databases.
HP Part Number: QL226-96659
Published: November 2012
Seitenansicht 0
1 2 3 4 5 6 ... 198 199

Inhaltsverzeichnis

Seite 1 - User Guide

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

Seite 2

Oracle is configured to perform backup to tape, Recovery Manager for Oracle interacts withOracle RMAN, which in turn interacts with NBU to trigger the

Seite 3 - Contents

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

Seite 4 - 4 Contents

7. From the backup server, perform a rollback of the database virtual volumes using a databaseread-only Virtual Copy.Example:# rmora_rollback -s TEST9

Seite 5 - Contents 5

NOTE: Use with the -f option if the database virtual volumes are in Remote Copy groups.Also, perform step 8 through step 11 to startup the clone datab

Seite 6 - 6 Contents

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

Seite 7 - Virtual Copies

On the backup server:• Run /opt/3PAR/RMOra/bin/rmoragui to start the Recovery Manager for Oracle GraphicalUser Interface (GUI).or• Run /opt/3PAR/RMOra

Seite 8 - Interacting with Oracle

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

Seite 9

Figure 5 Synchronous Long Distance Remote Copy ConfigurationCreating Virtual CopiesTo create Virtual Copies, use the rmora_sync command or the Recover

Seite 10

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

Seite 11

See:For information about:HP 3PAR Secure Service Custodian Configuration UtilityReferenceConfiguring the Secure Service Custodian server in order tomo

Seite 12

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

Seite 13

Once created, the Virtual Copy can be mounted on the backup server for off-host processingpurposes such as backup and database cloning.A database Virt

Seite 14 - The Database Cloning Utility

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

Seite 15

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

Seite 16 - Virtual Copy Policy

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

Seite 17 - The Database Rollback Utility

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

Seite 18 - Immediate Backup

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

Seite 19 - Automatic Backup

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

Seite 20

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:#

Seite 21

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

Seite 22

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

Seite 23 - Converting Virtual Volumes

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

Seite 24 - Preinstallation Requirements

The Virtual Copy Display UtilityThe Virtual Copy utility (rmora_display) of HP 3PAR Recovery Manager Software for Oracledisplays database Virtual Copi

Seite 25

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

Seite 26 - Installation

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

Seite 27 - Verifying Installation

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

Seite 28

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

Seite 29

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

Seite 30

In the output above, note that the Status and Role of the three Remote Copy groupson S347 are Started and Secondary, respectively.On S256:Name

Seite 31

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

Seite 32 - SSH Restrictions

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

Seite 33

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

Seite 34

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

Seite 35

• If the database files reside on ASM disk groups, it is dependent on which ASM databaseversion is installed on the backup server, different restricti

Seite 36

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

Seite 37

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

Seite 38

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

Seite 39

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

Seite 40

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

Seite 41

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

Seite 42

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

Seite 43

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

Seite 44

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

Seite 45

[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

Seite 46

Unmounting a database Virtual Copy involves the following actions:• For an ASM-managed database, if the ASM database on the backup server has a versio

Seite 47

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

Seite 48

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

Seite 49 - Configuration

MESSAGE ID1012SYMBOLIC NAMERMO_ERROR_MULTIPLE_PARTITIONMESSAGE3PAR1012: ERROR: Disk <disk ID> has multiple partitions.REASONIn Linux, the specif

Seite 50

REASONFailed to retrieve the hostname defined in the HP 3PAR StoreServ Storage system for the backupsystem.SOLUTIONExecute InForm CLI command showhost

Seite 51

3PAR1021: ERROR: Backup tag not specified.REASONUsing RMAN to backup the Virtual Copy to media with NetBackup, Recovery Manager for Oraclecould not fi

Seite 52

RMO_ERROR_UNSUPPORTED_FILETYPEMESSAGE3PAR1031: ERROR: <file name> is neither a regular file, directory, block nor character device.REASONWhen di

Seite 53

MESSAGE ID1048SYMBOLIC NAMERMO_ERROR_ARCHDEST_ERRORMESSAGE3PAR1048: ERROR: One or more archivelog destinations have error status.REASONWhen trying to

Seite 54 - Recovery Manager Commands

Change to use a different host as the alternate host.MESSAGE ID1054SYMBOLIC NAMERMO_ERROR_INVALID_ARGUMENTMESSAGE3PAR1054: ERROR: Invalid argument.REA

Seite 55 - Recovery Manager Commands 55

MESSAGE3PAR1061: ERROR: Could not find file system for file <file name>.REASONThe specified file or directory is a regular file or qio file, but

Seite 56

MESSAGE ID1066SYMBOLIC NAMERMO_ERROR_SHARED_ASMDGMESSAGE3PAR1066: ERROR: Archive logs and datafiles are on the same ASM disk group.REASONRecover Manag

Seite 57 - Recovery Manager Commands 57

When using an ascii control file:• The structure of the clone database is not required to be exactly the same as the structure ofthe original database

Seite 58 - DESCRIPTION

During configuration, the retention or expiration value provided exceeds the maximum systemallowed value, which is in the range of 1 to 43800 hours (1

Seite 59 - Recovery Manager Commands 59

3PAR1080: ERROR: Failed to retrieve the retention/expiration time for Virtual Copy <name>.REASONFailed to retrieve the retention and/or expirati

Seite 60

MESSAGE ID1097SYMBOLIC NAMERMO_ERROR_SNAPDEV_NOTFOUNDMESSAGE3PAR1097: ERROR: Could not find Virtual Copy device for <Virtual Copy name>.REASONTh

Seite 61 - Recovery Manager Commands 61

MESSAGE ID1101SYMBOLIC NAMERMO_ERROR_REMOVE_ORAASMDISKMESSAGE3PAR1101: ERROR: Could not delete oracleasm disk <disk ID>.REASONFailed to use the

Seite 62

MESSAGE3PAR1104: ERROR: The number of Virtual Copies has exceeded the maximum of <value>.REASONThe maximum number of Virtual Copies specified in

Seite 63

Check if device is valid. Ignore the error message for non-3PAR devices. Check log files for moreinformation. Contact customer support for further inv

Seite 64

Try the operation at a later time. If you are certain that there are no similar operations going on,remove the lock file specified on the screen as it

Seite 65 - Recovery Manager Commands 65

SYMBOLIC NAMERMO_ERROR_RETRIEVE_LDVVMESSAGE3PAR1116: ERROR: Could not retrieve logical disks for volume <name>.REASONThe InForm CLI command show

Seite 66

MESSAGE ID1128SYMBOLIC NAMERMO_ERROR_RETRIEVE_CTRLFILEMESSAGE3PAR1128: ERROR: Could not retrieve location of the control files from <database name&

Seite 67 - Recovery Manager Commands 67

REASONBefore using the rmore_rsync command, all of the volumes within the Remote Copy groups thatare used by the Oracle database should be in Synced s

Seite 68

Integration with HP 3PAR Virtual Lock SoftwareHP 3PAR Virtual Lock Software allows administrators to apply a configurable retention period tovirtual v

Seite 69 - EXAMPLES

MESSAGE ID1135SYMBOLIC NAMERMO_ERROR_CONFIG_PARAM_NOTFOUNDMESSAGE3PAR1135: ERROR: Parameter <value not found from the configuration file.REASONAn e

Seite 70

Contact customer support for further investigation.MESSAGE ID1139SYMBOLIC NAMERMO_ERROR_ORA_VERSIONMESSAGE3PAR1139: ERROR: Could not determine Oracle

Seite 71 - Recovery Manager Commands 71

When running rmora_createdb to clone the database on the backup server using the binarycontrol file, and if the original datafiles/archive log destina

Seite 72

RMO_ERROR_VC_NOTMOUNTED_AT_ROOTMESSAGE3PAR1145: ERROR: The Virtual Copy <Virtual Copy name> is not currently mounted at <location>.REASONT

Seite 73 - Recovery Manager Commands 73

MESSAGE ID1149SYMBOLIC NAMERMO_ERROR_RESTOREMESSAGE3PAR1149: ERROR: Could not restore backup to host <name>.REASONThe operation rmora_restore fa

Seite 74

When Recovery Manager for Oracle tries to execute the command createvlun, it has to makesure there is no other identical operation going on to take th

Seite 75

Make sure the HP 3PAR StoreServ Storage system is working properly. Retry the operation. If thesame error persists, contact customer support for furth

Seite 76

MESSAGE ID1164SYMBOLIC NAMERMO_ERROR_SET_RETENTEXPMESSAGE3PAR1164: ERROR: Could not set retention/expiration for Virtual Copy <Virtual Copy name>

Seite 77 - Recovery Manager Commands 77

3PAR1168: ERROR: One or more Virtual Copy's repository exist.REASONTrying to execute rmora_rmrep to remove the backup repository for a database c

Seite 78

RMO_ERROR_SET_PROTECTION_MODEMESSAGE3PAR1173: ERROR: Could not set the database protection mode to maximum performance.REASONAfter using the binary co

Seite 79 - SYNOPSIS

For a time-based policy example, if the expiration time is one month (specified in the configurationfile), then the Virtual Copy that reaches the expi

Seite 80

SOLUTIONCheck the alert log and Recovery Manager for Oracle log file for more details. Manually querythe cloned the database to see if there are any p

Seite 81 - Recovery Manager Commands 81

SYMBOLIC NAMERMO_ERROR_PHYSDEV_NOTFOUNDMESSAGE3PAR1182: ERROR: Could not find device '%s'.REASONFailed to retrieve the OS device used by the

Seite 82

SOLUTIONCheck the log file for more details. Contact customer support for further investigation.MESSAGE ID1192SYMBOLIC NAMERMO_ERROR_DB_NOTIN_STANDBYM

Seite 83 - Recovery Manager Commands 83

SOLUTIONMake sure that the –d <loc> argument entered under rmora_createdb is entered and enclosedwithin double quotes (“), and make sure that th

Seite 84

SYMBOLIC NAMERMO_ERROR_ARCHLOG_GAPMESSAGE3PAR1208 ERROR: Archive log gap exists between the primary and standby database.REASONRecovery Manager for Or

Seite 85 - Description

MESSAGE ID1216SYMBOLIC NAMERMO_ERROR_SETVVMESSAGE3PAR1216: ERROR: Could not set retention time <time> for Virtual Copy <Virtual Copy name>

Seite 86

SOLUTIONTry to upgrade the InForm OS, or do not use this feature.MESSAGE ID1220SYMBOLIC NAMERMO_ERROR_INVALID_RETENTEXPMESSAGE3PAR1220: ERROR: Invalid

Seite 87

3PAR1224: ERROR: Oracle ASMLib has not been installed.REASONIn Linux, the required file /etc/sysconfig/oracleasm or/etc/sysconfig/Oracleasm-_dev_oracl

Seite 88 - Interface

SOLUTIONMake sure the TPDSYSNAME and TPDUSERNAME have correct values in the configuration file.Make sure the volumes were not removed, which can cause

Seite 89 - Creating a Virtual Copy

MESSAGE ID1231SYMBOLIC NAMERMO_ERROR_RETRIEVE_VVMESSAGE3PAR1231: ERROR: Could not retrieve virtual volume information from the HP 3PAR StoreServStorag

Seite 90

• Datafile backup - A backup of datafiles only.• Archive log backup - A backup of archive logs only.Recovery Manager for Oracle can be configured to p

Seite 91

SOLUTIONCheck the log file for more information. Make sure the OS is a valid supported version and thatthe OS is functioning correctly. Contact custom

Seite 92

SYMBOLIC NAMERMO_ERROR_SHUTDOWN_ASMMESSAGE3PAR1238: ERROR: Could not shutdown ASM instance on host <host name>.REASONCould not shutdown the ASM

Seite 93 - Unmounting a Virtual Copy

MESSAGE ID1242SYMBOLIC NAMERMO_ERROR_RETRIEVE_ASMDISKMESSAGE3PAR1242: ERROR: Could not retrieve ASM disks for database '%s'.REASONFailed to

Seite 94 - Backing up a Virtual Copy

If during database cloning time, check the saved init.ora file to see if there are any unusualcharacters or wrong syntax. Make sure the primary databa

Seite 95 - Cloning a Database

Make sure the archive log destinations are in valid state and have enough space. Make sure theprimary database is running normally.MESSAGE ID1250SYMBO

Seite 96 - Removing a Cloned Database

REASONFailed to remount the specified file system.SOLUTIONMake sure the OS is in valid state on the database server. Manually remount the file system.

Seite 97 - Backing Up a Database

MESSAGE3PAR1258: ERROR: Could not startup all VxVM volumes in disk group <name>.REASONUsing the command vxvol -g dgname to start up all VxVM vol

Seite 98 - Viewing Online Help

SYMBOLIC NAMERMO_ERROR_DROP_ASMDGMESSAGE3PAR1262: ERROR: Could not drop one or more ASM snapshot disk groups.REASONThe SQL command to drop one or more

Seite 99 - Standby Databases

MESSAGE ID1266SYMBOLIC NAMERMO_ERROR_BACKUP_NOT_CONFIGUREMESSAGE3PAR1266: ERROR: Recovery Manager has not been configured for backup/restore.REASONThe

Seite 100 - # umount /oradata

The operation to use Oracle RMAN and a NetBackup policy with Oracle type to backup a databasefailed.SOLUTIONCheck NetBackup log files and the Recovery

Seite 101

For Oracle RMAN backup, Recovery Manager for Oracle:• Starts up a clone database in mounted mode using the mounted Virtual Copy on the backupserver, a

Seite 102

MESSAGE ID1273SYMBOLIC NAMERMO_ERROR_RETRIEVE_DBNAMEMESSAGE3PAR1273: ERROR: Could not retrieve the current database name.REASONDuring rmora_restore, R

Seite 103 - Overview

SYMBOLIC NAMERMO_ERROR_ARCHLOG_RESTOREMESSAGE3PAR1276: ERROR: Archive logs will be restored automatically during media recovery usingOracle RMAN.REASO

Seite 104 - How Remote Copy Works

MESSAGE3PAR1279: ERROR: The host <host name> is neither the backup server or the original host.Use '-H' option to specify the Oracle H

Seite 105 - How Remote Copy Works 105

Make sure TPDSYSNAME and TPDUSERNAME to access the specified HP 3PAR StoreServ Storagesystem are correct. Make sure the Remote Copy and Remote copy gr

Seite 106 - Creating Virtual Copies

3PAR1304: ERROR: Control file ASM disk group <name> not found.REASONDuring rmora_createdb process, the error occurs when:• A non-default clone l

Seite 107 - 8 Support and Other Resources

Make sure that the alternate backup server is connected to the HP 3PAR StoreServ Storage systemand is set up correctly, so that a showhostcommand on t

Seite 108

MESSAGE ID1315MESSAGE3PAR1315: ERROR: Could not import volume group <group>.REASONThe LVM vgimport command, which is used to import the snapshot

Seite 109

See the preceding error message to determine the cause of failure.MESSAGE ID1320MESSAGE3PAR1320: ERROR: Could not remove LVM volume group <group>

Seite 110 - HP 3PAR branding information

IndexAarchive log backupconfiguring NBU policy, 40automatic backup, 19Bbackup server to HP 3PAR StoreServ Storage system SSHconnection, 36backup to NB

Seite 111 - 9 Documentation feedback

removing Virtual Copy repositories, 79requirementsstandby databases, 9restrictions with SSH, 32RMAN recovery catalog creation, 42rmora_create, 63rmora

Seite 112 - Introduction

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

Seite 113 - Configuration Diagram

NOTE: The backup scripts (rmora_nbu_dbbackup.sh and rmora_nbu_archbackup.sh)and the RMAN backup scripts (rmora_rman_dbbackup.sh andrmora_rman_archback

Seite 114

For an NBU (user-managed) restoration:• Control files are not restored by default.• For an online Virtual Copy, both datafiles and archive logs are re

Seite 115 - Unavailable

The following configuration requirements must be met:• The HP 3PAR StoreServ Storage system must be running HP 3PAR OS 2.3.1 or higher.• The backup se

Seite 116

Recovery Manager for Oracle and Fat-to-Thin and Thin-to-FatTo improve the existing RMO setup environment, an unlimited bidirectional conversion of vol

Seite 117

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

Seite 118 - Primary-Rev

◦ If you install the NetBackup for Oracle client, you must link the Oracle libok.so libraryon the database and backup servers to point to the Symantec

Seite 119

If you are not using the backup server as the NetBackup master server, be sure to install RecoveryManager for Oracle on the NetBackup master server.In

Seite 120

5. After the installation is complete on all the required servers, you can allow Oracle users andDatabase Administrators group access to the Recovery

Seite 121

If you are not using the backup server as the NetBackup master server, be sure to install RecoveryManager for Oracle on the NetBackup master server.In

Seite 122

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, you will need to moun

Seite 123

Contents1 Overview of Recovery Manager Operations...7Virtual Copies...

Seite 124

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

Seite 125

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

Seite 126

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

Seite 127

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

Seite 128

Setting Up Connections from the Backup Server to the Database ServerTo set up an SSH connection from the backup server to the database server, perform

Seite 129

NOTE: If you are prompted for a password, the setup is incorrect and you must redo the previoussetup.<backup_server># ssh <user>@<NBU_m

Seite 130

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

Seite 131

Setting Connections from the Database Server to the HP 3PAR Storage SystemSkip this step if the database server has the same SSH key pair as the SSH k

Seite 132

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

Seite 133

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

Seite 134

3 Configuring Recovery Manager for Oracle...31Setting Up SSH Connections for Recovery Manager...

Seite 135 - Secondary-Rev

NOTE: This section assumes that you are familiar with the Oracle Database and SymantecNetBackup (NBU). For more information on creating a NetBackup po

Seite 136

be set to at least 600 seconds (10 minutes) to allow enough time for Recovery Manager to performall necessary operations prior to the actual backup.Fo

Seite 137

For Recovery Manager for Oracle to perform backup and restoration correctly, you must use thefollowing guidelines in conjunction with Symantec NetBack

Seite 138

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

Seite 139

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

Seite 140 - B Troubleshooting

2. When prompted, press ENTER.• ORACLE_SID of the database instance [h=help,q=quit]?Enter ORACLE_SID of the database instance that you want to configu

Seite 141 - MESSAGE ID

• HP 3PAR Storage system user name for the database server[h=help,q=quit]?Recovery Manager for Oracle requires that a HP 3PAR OS Software user must ha

Seite 142

reached, Recovery Manager for Oracle removes the oldest Virtual Copy before creating anew one.The default maximum number is 500 read-only Virtual Copi

Seite 143

• NetBackup full schedule name for policy 'your policyname'[h=help,s=skip,q=quit]?You will only be prompted with this question if you previo

Seite 144

4. In the Recovery Manager Policy wizard screen, set either a numeric or time-based policy. ClickNext.5. In the Vendor Backup Product Properties wizar

Seite 145

5 Using the Recovery Manager for Oracle Graphical User Interface...88Starting and Stopping the Recovery Manager for Oracle GUI...

Seite 146

3. When prompted, answer the following questions:• ORACLE_SID of the database instance [h=help,q=quit]?Enter ORACLE_SID of the database instance that

Seite 147

• Primary/Local storage system user name [h=help,q=quit]?Recovery Manager for Oracle requires that a HP 3PAR Operating System Software user musthave b

Seite 148

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

Seite 149

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

Seite 150

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

Seite 151

The following list describes the restrictions and automated scripts that are generated whenconfiguring Recovery Manager. The automated scripts will be

Seite 152

server is separate from the Recovery Manager for Oracle backup server, the Oracle DatabaseAdministrator user and group must exist on the NetBackup mas

Seite 153

differential incremental or cumulative incremental backup, which is predefined in the NBU schedule.If Oracle RMAN is selected as the backup method, th

Seite 154

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

Seite 155

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

Seite 156

9 Documentation feedback...111A Case Study: Remote Copy with Recovery Manager fo

Seite 157

rmora_configSYNTAXrmora_config [-s <oracle_sid> -p <db_server>]DESCRIPTIONThe rmora_config command creates or modifies the Recovery Manage

Seite 158

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

Seite 159

• RMAN_BACKUP_DEST - The backup destination to store RMAN backup image. This option isonly required if the specified RMAN channel type is DISK.• RMVC_

Seite 160

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

Seite 161

will be then taken out of backup mode. An archive log switch will be performed before VirtualCopies of archive log virtual volumes are created.• If th

Seite 162

-s <oracle_sid>The Oracle SID of the database instance. For Real Application Cluster (RAC) database, an OracleSID of any RAC instance can be spe

Seite 163

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

Seite 164

-s <oracle_sid>The Oracle SID of the database instance. For Real Application Cluster (RAC) database, an OracleSID of any RAC instance can be spe

Seite 165

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

Seite 166

EXAMPLES• rmora_display -s TEST920 -p pilot. # Name Create Time Type Status Backup?============ ======================== =

Seite 167

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

Seite 168

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

Seite 169

Software CLI createuser command. The created user must be assigned the edit role (privilege)or 3PAR_RM role.-vRuns the command in verbose mode.Recover

Seite 170

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

Seite 171

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

Seite 172

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

Seite 173

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

Seite 174

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

Seite 175

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

Seite 176

-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

Seite 177

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

Seite 178

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

Seite 179

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

Seite 180

-t <timestamp>The timestamp of a Virtual Copy from which to promote. The Virtual Copy name can be obtainedusing the rmora_display command.-o [da

Seite 181

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

Seite 182

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

Seite 183

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

Seite 184

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

Seite 185

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

Seite 186

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

Seite 187

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

Seite 188

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

Seite 189

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

Seite 190

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

Seite 191

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

Seite 192

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

Seite 193

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

Seite 194

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

Seite 195

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

Seite 196

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

Seite 197

4. (Optional) Select Retention time and enter a numeric value from 1 to 1,825 (Days) or 1 to43,800 (Hours) in the adjacent field.5. Click Finish.After

Seite 198 - 198 Index

3. Select the Backup Type.NOTE: Incremental backup of archive log using RMAN is not supported.a. Full backup - Performs a full backup of a Virtual Cop

Seite 199

Recovery Manager for Oracle Online Help appears in a web browser.Using a Web Browser to Access Online Help and Event MessagesRecovery Manager for Orac

Kommentare zu diesen Handbüchern

Keine Kommentare