Hp 3PAR Application Software Suite for Oracle Bedienungsanleitung

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

  • Herunterladen
  • Zu meinen Handbüchern hinzufügen
  • Drucken
  • Seite
    / 194
  • Inhaltsverzeichnis
  • FEHLERBEHEBUNG
  • LESEZEICHEN
  • Bewertet. / 5. Basierend auf Kundenbewertungen
Seitenansicht 0
HP 3PAR Recovery Manager 4.2.0 Software
for Oracle
User’s Guide
Abstract
This document provides the information needed to install, configure, and use the HP 3PAR Recovery Manager 4.2.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-96279
Published: May 2012
Seitenansicht 0
1 2 3 4 5 6 ... 193 194

Inhaltsverzeichnis

Seite 1 - User’s Guide

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

Seite 2

NetBackup Policies for NBU (User-Managed) Backup” (page 39) or “Setting Up NetBackup Policiesfor Oracle RMAN Backup” (page 41) for detailed informatio

Seite 3 - 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 4 - 4 Contents

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

Seite 5 - Contents 5

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

Seite 6 - 6 Contents

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 7 - Virtual Copies

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

Seite 8 - Interacting with Oracle

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

Seite 9

8 Support and Other ResourcesRelated DocumentsThe following documents also provide information related to the HP 3PAR Storage Server:Read the…For Info

Seite 10

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

Seite 11

The database ASM11GR2 uses SPFILE, which is located on one of the ASM disk groups.$cat initASM11GR21.oraSPFILE='+ASM11GR2_DATADG/ASM11GR2/spfileA

Seite 12

NOTE: Recovery Manager for Oracle requires online redo logs and control files to be in aRemote Copy group separate from datafiles and archive log dest

Seite 13

When creating an online virtual copy, the create utility performs the following actions:• Discovers devices (3PAR virtual volumes) used by the datafil

Seite 14 - The Database Cloning Utility

Taking the database out of backup mode ...Archiving online redo logs ...Initiating synchronization for archive log volumes ...Synchronization request

Seite 15

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 16 - Virtual Copy Policy

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

Seite 17 - The Database Backup Utility

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

Seite 18 - Immediate Backup

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 19 - Automatic Backup

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

Seite 20

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

Seite 21

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 22

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

Seite 23 - Preinstallation Requirements

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

Seite 24

• A Datafile virtual copy indicates that the virtual copy for the database was created while itwas OPEN (online) and contains only datafiles (no archi

Seite 25 - Verifying Installation

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 26

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 27

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

Seite 28

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 29

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

Seite 30

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 31

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 32 - SSH Restrictions

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 33

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

Seite 34

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

Seite 35

NOTE: The ASM major release version on the backup server must be higher than the ASMmajor release version on the database server.• On Linux systems, i

Seite 36

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

Seite 37

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

Seite 38

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

Seite 39

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 40

[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 41

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

Seite 42

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

Seite 43

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

Seite 44

REASONFailed to retrieve the hostname defined in the HP 3PAR storage system for the backup system.SOLUTIONExecute InForm CLI command showhost to verif

Seite 45

REASONUsing RMAN to backup the virtual copy to media with NetBackup, Recovery Manager for Oraclecould not find the backup tag parameter, which should

Seite 46

• Deports the read-write virtual copy from the backup server.• Removes the read-write virtual copy.The Virtual Copy Export UtilityHP 3PAR Recovery Man

Seite 47

MESSAGE3PAR1031: ERROR: <file name> is neither a regular file, directory, block nor character device.REASONWhen discovering devices used by the

Seite 48

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

Seite 49 - Configuration

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

Seite 50

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 51

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

Seite 52

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 53 - Recovery Manager Commands

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

Seite 54 - DESCRIPTION

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

Seite 55 - Recovery Manager Commands 55

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

Seite 56

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

Seite 57 - Recovery Manager Commands 57

• The number of multiplex redo log locations must be equal to, or less than, the original databasewhen creating the clone database. Otherwise, the ext

Seite 58

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 59

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 60

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

Seite 61 - Recovery Manager Commands 61

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

Seite 62

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 63 - Recovery Manager Commands 63

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

Seite 64

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

Seite 65 - Recovery Manager Commands 65

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 66

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

Seite 67 - Recovery Manager Commands 67

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

Seite 68 - EXAMPLES

There are a few ways to enforce the retention time for read-only virtual copies.• During configuration, the retention value specified will be the defa

Seite 69

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 70

Make sure the HP 3PAR storage system is working properly. Retry the operation. If the same errorpersists, contact customer support for further investi

Seite 71 - Recovery Manager Commands 71

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

Seite 72

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 73 - Recovery Manager Commands 73

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

Seite 74

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 75

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

Seite 76

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

Seite 77 - Recovery Manager Commands 77

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

Seite 78

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

Seite 79 - SYNOPSIS

The Database Rollback UtilityHP 3PAR Recovery Manager Software for Oracle’s database rollback utility (rmora_rollback)promotes a virtual copy's v

Seite 80

MESSAGE ID1216SYMBOLIC NAMERMO_ERROR_SETVVMESSAGE3PAR1216: ERROR: Could not set retention time <time> for virtual copy <virtual copy name>

Seite 81 - Recovery Manager Commands 81

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

Seite 82

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

Seite 83 - Recovery Manager Commands 83

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

Seite 84

SYMBOLIC NAMERMO_ERROR_RETRIEVE_VVMESSAGE3PAR1231: ERROR: Could not retrieve virtual volume information from the HP 3PAR storage system.REASONFailed t

Seite 85 - Description

MESSAGE ID1235SYMBOLIC NAMERMO_ERROR_SV_NOTFOUNDMESSAGE3PAR1235: ERROR: virtual copy volume <volume name> not found from the HP 3PAR storagesyst

Seite 86

3PAR1238: ERROR: Could not shutdown ASM instance on host <host name>.REASONCould not shutdown the ASM instance on the backup server.SOLUTIONMake

Seite 87

RMO_ERROR_RETRIEVE_ASMDISKMESSAGE3PAR1242: ERROR: Could not retrieve ASM disks for database '%s'.REASONFailed to retrieve ASM disks used by

Seite 88 - Interface

MESSAGE ID1246SYMBOLIC NAMERMO_ERROR_BACKUP_ASM_METADATAMESSAGE3PAR1246: ERROR: Could not backup ASM metadata.REASONFailed to execute the ASM command

Seite 89 - Creating a Virtual Copy

MESSAGE ID1250SYMBOLIC NAMERMO_ERROR_SET_ARCHLOGMESSAGE3PAR1250: ERROR: Please explicitly set value for parameter log_archive_dest_n.REASONThe detail

Seite 90

backup or Oracle RMAN backup). However, incremental (differential or cumulative) backup of awhole Oracle database is only available using Oracle RMAN

Seite 91

SOLUTIONMake sure the OS is in valid state on the database server. Manually remount the file system. Contactcustomer for further investigation.MESSAGE

Seite 92 - Unmounting a Virtual Copy

REASONUsing the command vxvol -g dgname to start up all VxVM volumes failed.SOLUTIONCheck the log file to get more details. Make sure VxVM is in a val

Seite 93 - Backing up a Virtual Copy

MESSAGE3PAR1262: ERROR: Could not drop one or more ASM snapshot disk groups.REASONThe SQL command to drop one or more ASM snapshot disk groups on the

Seite 94

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

Seite 95 - Cloning a Database

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 96 - Backing Up a Database

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

Seite 97 - Viewing Event Messages

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

Seite 98 - Viewing Online Help

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

Seite 99 - # umount /oradata

MESSAGE ID1301SYMBOLIC NAMERMO_ERROR_CLONEDB_UPMESSAGE3PAR1301: ERROR: The clone database instance <name> is currently running.REASONTrying to c

Seite 100

During rmora_createdb process, the error occurs when:• A non-default clone location (option -d) was specified to clone the database, and• At least one

Seite 101

NOTE: The RMAN backup scripts (rmora_rman_dbbackup.sh andrmora_rman_archbackup.sh) are generated at/etc/3par/solutions/<db_server>.ora.<oracl

Seite 102 - Overview

Make sure that the alternate backup server is connected to the HP 3PAR storage system and is setup correctly, so that a showhostcommand on the storage

Seite 103 - How Remote Copy Works

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

Seite 104

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

Seite 105 - Creating Virtual Copies

IndexAarchive log backupconfiguring NBU policy, 40automatic backup, 19Bbackup server to HP 3PAR storage system SSH connection,36backup to NBU verifica

Seite 106 - 8 Support and Other Resources

removing virtual copy repositories, 79requirementsstandby databases, 9restrictions with SSH, 32RMAN recovery catalog creation, 42rmora_create, 62rmora

Seite 107 - Introduction

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

Seite 108 - Configuration Diagram

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 Da

Seite 109

Recovery Manager for Oracle with Oracle Standby DatabaseAll HP 3PAR Recovery Manager Software for Oracle’s utilities can be run against an Oraclephysi

Seite 110 - Unavailable

Recovery Manager for Oracle with Remote CopyRecovery Manager for Oracle integrates with HP 3PAR Remote Copy Software to copy databasevirtual volumes f

Seite 111

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

Seite 112

user and Oracle owner group must exist on the NetBackup master server. No Oraclebinary is required.• If you choose Oracle RMAN for the backup method,

Seite 113 - Primary-Rev

Starting InstallationThe following section describes the steps necessary for installing Recovery Manager for Oracle ona Linux system:CAUTION: When upg

Seite 114

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

Seite 115

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.CA

Seite 116

INSTDATE: Jan 18 2000 05:40 HOTLINE: 1-800-786-7967 EMAIL: www.hp.com STATUS: completely installed FILES: 386 installed pathna

Seite 117

2. Use the pkgrm command as follows:# pkgrm <package_name>For versions prior to, or equal to, 3.0.4, the package name is VCDBAora. Starting with

Seite 118

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

Seite 119

• /etc/3par/solutions/log• /etc/3par/solutions/lock• /etc/3par/solutions/<db_server>.ora.<oracle_sid>a. Change the owner of the Recovery M

Seite 120

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

Seite 121

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

Seite 122

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 123

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 124

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 125

4. Copy the public key of the backup server to the HP 3PAR storage system. You can find thepublic key in the location specified when generating an SSH

Seite 126

for Oracle uses the same CLI user to access the HP 3PAR storage system from either the backupserver or database server.If you created a different CLI

Seite 127

4. Copy the public key of the database server to the HP 3PAR storage system.<db_server># ssh <username>@<ss_name><username>&ap

Seite 128

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

Seite 129

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

Seite 130 - 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 131

For example, to set the BPSTART_TIMEOUT and BPEND_TIMEOUT parameters to 600 seconds (5minutes), modify the corresponding parameters in /usr/openv/netb

Seite 132

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

Seite 133

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

Seite 134

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 135 - 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 136 - MESSAGE ID

• HP 3PAR storage system user name for the database server[h=help,q=quit]?Recovery Manager for Oracle requires that a 3PAR InForm user must have been

Seite 137

The default maximum number is 500 read-only virtual copies for each volume.• Do you want to remove oldest virtual copy when the maximum numberof virtu

Seite 138

Enter a schedule name for the policy provided for the previous question that is used to performfull database backup.• NetBackup policy name for archiv

Seite 139

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

Seite 140

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

Seite 141

• 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

Seite 142

• 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

Seite 143

1. Start the Recovery Manager for Oracle GUI on the backup server.a. Ensure the X11 server is running on the destination host where the GUI is display

Seite 144

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

Seite 145

rmora_backupSYNTAXrmora_backup -s <oracle_sid> -p <db_server> [-t <timestamp>] [-ofull|incr|cinc] [-v]orrmora_backup -s <oracle_s

Seite 146

For Oracle RMAN backup (to tape or local disk):• The backup server must have an equal or higher Oracle major release version than the Oraclemajor rele

Seite 147

The Oracle SID of the database instance. For Real Application Cluster (RAC) database, an OracleSID of any RAC instance can be specified.-p <db_serv

Seite 148

-o cincPerforms a cumulative incremental backup of a virtual copy. If Symantec NetBackup is selected asthe backup method, this option can be used with

Seite 149

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

Seite 150

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

Seite 151

Systems and Software Configurations...107Configuration Diagram...

Seite 152

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 153

• 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 154

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

Seite 155

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 156

The Oracle SID of the database instance. For Real Application Cluster (RAC) database, an OracleSID of any RAC instance can be specified.-p <db_serv

Seite 157

NOTE: If the database volumes do not belong to any domain, then the read-only virtual copy'sretention time cannot exceed the value of the system&

Seite 158

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

Seite 159

Database Administrator user must exist on the backup server. In addition, permission on the RecoveryManager for Oracle Installation and Repository dir

Seite 160

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

Seite 161

============ ======================== ======= ========= ========1. 012403154751 Fri Jan 24 15:47:51 2003 Offline Available N2. 012403154650 Fri Ja

Seite 162

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

Seite 163

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

Seite 164

system user can be created using the InForm CLI createuser command. The created user mustbe assigned the edit role (privilege) or 3PAR_RM role.-vRuns

Seite 165

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

Seite 166

• For virtual copies from an ASM-managed database, based on the different ASM databasereleases on the backup server, the operation is different.◦ For

Seite 167

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

Seite 168

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

Seite 169

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

Seite 170

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

Seite 171

-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 172

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

Seite 173

The following example displays the location of the Recovery Manager for Oracle repository onthe backup server for Oracle database instance test that i

Seite 174

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

Seite 175

-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 176

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

Seite 177

• The online redo logs and control files should not reside on the same 3PAR virtual volumesused by the datafiles and archive logs to avoid being resto

Seite 178

-o coldbkupThis option is the same as the -o offline and is deprecated.-o validateValidates the Remote Copy configuration.-o checkonlySame as the -o v

Seite 179

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 180

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

Seite 181

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

Seite 182

5 Using the Recovery Manager for Oracle Graphical UserInterfaceStarting and Stopping the Recovery Manager for Oracle GUIThe Recovery Manager for Oracl

Seite 183

For additional details on creating configuration files with or without the Remote Copy feature, see“Recovery Manager for Oracle Configuration Files” (

Seite 184

Database log mode Archive ModeAutomatic archival EnabledArchive destination /rac9i_db/rac9i_arch2

Seite 185

43,800 (hours). Deselecting the checkbox indicates there is no expiration and/or retentiontime.5. Click Next.6. (Optional) If you wish to schedule a t

Seite 186

5. Click Finish.NOTE: The virtual copy policy is effective immediately.Setting up a Numeric-Based Virtual Copy PolicyThis feature allows you to contro

Seite 187

3. Select the unit of measure for the Expiration time and/or the Retention Time as Days or Hours.4. Enter a numeric value from 0 to 1,825 (Days) or 0

Seite 188

Rolling Back Using a Virtual CopyTo roll back the primary database to a virtual copy’s point-in-time image, perform the following:1. Right-click the v

Seite 189

when necessary. After the virtual copy repository is removed, the virtual copies have a status ofRemoved and all information related to this virtual c

Seite 190

2. On the Export Virtual Copy screen, provide the following information:• Alternate backup host name - the name of the backup server to which the virt

Seite 191

copy on the remote (secondary) HP 3PAR storage system, updates the navigation view, and sendsnotification to the user.Starting Periodic Synchronizatio

Seite 192

Log Destination Only option. After the virtual copy creation is completed, the databaseis taken out of backup mode.• Archive Log Destination Only - Th

Seite 193

Viewing Online HelpTo view online help for Recovery Manager for Oracle, select Help→Online Help.Recovery Manager for Oracle Online Help appears in a w

Seite 194 - 194 Index

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

Kommentare zu diesen Handbüchern

Keine Kommentare