HP 3PAR Recovery Manager 4.4.0 Software for Oracle User Guide Abstract This document provides the information needed to install, configure, and use the HP 3PAR Recovery Manager 4.4.0 Software for Oracle on Solaris, Red Hat Linux, Oracle Linux, HP UX and IBM AIX.
© Copyright 2013 Hewlett-Packard Development Company, L.P. Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license. The information contained herein is subject to change without notice.
Contents 1 Overview of Recovery Manager Operations..................................................7 Virtual Copies..........................................................................................................................7 About the Recovery Manager for Oracle Repository......................................................................7 Interacting with Oracle..............................................................................................................
Installing Recovery Manager for Oracle on IBM AIX Systems........................................................34 Installation........................................................................................................................34 Verifying Installation...........................................................................................................35 Removing Recovery Manager from IBM AIX Systems....................................................................
rmora_display...................................................................................................................82 rmora_export....................................................................................................................84 rmora_mount.....................................................................................................................86 rmora_remove...........................................................................................................
7 Using Remote Copy with Recovery Manager..............................................118 Overview............................................................................................................................118 Recovery Manager for Oracle’s Remote Copy Requirements..................................................118 How Remote Copy Works......................................................................................................119 Creating Virtual Copies...........................
1 Overview of Recovery Manager Operations Recovery Manager for Oracle offers a specific data protection solution that has been enhanced to provide rapid online recovery from space-efficient online point-in-time snapshots of an Oracle database. Further, Recovery Manager for Oracle enables off-host backup of an Oracle database to tape, minimizing any impact to the production Oracle server.
where: • is the host name of the database server. • is the Oracle SID of the database instance. The following example displays the location of the Recovery Manager for Oracle repository on the backup server for Oracle database instance test that is running on database server Host1. /etc/3par/solutions/Host1.ora.test If the database is a Real Application Cluster (RAC) database, there will be multiple repositories, one for each RAC instance.
To ensure that the database is running in automatic archive log mode, use SQL*Plus utility to ensure the Database log mode is Archive Mode and that Automatic archival is Enabled, as in the following example: $ sqlplus "/as sysdba" SQL*Plus: Release 9.2.0.1.0 - Production on Wed Nov 14 13:59:13 2007 Copyright (c) 1982, 2002, Oracle Corporation. All rights reserved. Connected to: Oracle9i Enterprise Edition Release 9.2.0.1.
For NBU backup and restoration, Recovery Manager for Oracle interacts directly with NBU to trigger the backup or restore process. Recovery Manager for Oracle requires that the NBU client must be installed on the database server and the backup server. For HP Data Protector backup and restoration, Recovery Manager for Oracle interacts directly with HP Data Protector to trigger the backup or restore process.
The Virtual Copy Creation Utility The Virtual Copy creation utility (rmora_create command) of HP 3PAR Recovery Manager Software for Oracle creates an online, offline, datafile, or archive log Virtual Copy of an Oracle database. • Online or offline Virtual Copy - A point-in-time snapshot image of a database while it is OPEN (online) or CLOSED (offline). • Archive log Virtual Copy - A snapshot image of the archive log destination of a database while it is online (OPEN).
An archive log Virtual Copy is created while the database is OPEN and performs the following actions: • Discovers devices (HP 3PAR virtual volumes) used by the archive log destination. • Switches logs and archives online redo logs to archive log destination. • Re-synchronizes the Recovery Catalog to update with newly generated archive logs if the Virtual Copy is to be backed up using Oracle RMAN. • Creates a Virtual Copy for the archive log destination virtual volumes.
The Virtual Copy Mount Utility The Virtual Copy mount utility of HP 3PAR Recovery Manager Software for Oracle mounts an existing database Virtual Copy that is created using the create utility on the backup server using the rmora_mount command. The mounted Virtual Copy can be used for off-host processing purposes such as backup or database cloning. The following restrictions apply when mounting a database Virtual Copy: • The Virtual Copy must have an Available or Mounted(P) status in order to be mounted.
instance. If no ASM instance is up on the backup server, an ASM instance is started up on the backup server, and all ASM disk groups in the Virtual Copy are mounted. ◦ For ASM versions earlier than 10.2.0.5 or 11.0.1.7, if an ASM instance is up on the backup server, the mount utility checks if there is any mounted diskgroup. If there is no mounted diskgroup, the ASM instance is shut down, otherwise, the mount utility gives an error and exits.
• Once exported, the Virtual Copy on the alternate backup server can be mounted, unmounted, backed up, and restored. • Once the exported Virtual Copy is no longer needed, its repository can be removed from the alternate backup server. The Database Cloning Utility The database cloning utility (rmora_createdb command) of HP 3PAR Recovery Manager Software for Oracle creates a single-instance database, or starts up a cloned database in MOUNTED mode for backup (RMAN) purposes.
The cloned database is shutdown with the shutdown immediate option. The database related files (Oracle parameter file, control files and redo logs), which are previously created by the rmora_createdb command, are removed. The read-write Virtual Copy remains mounted. The Virtual Copy Removal Utility HP 3PAR Recovery Manager for Oracle’s Virtual Copy removal utility removes an existing Virtual Copy from the HP 3PAR StoreServ Storage system.
If a Virtual Copy has been backed up, the remove repository utility command fails unless the -f option is used. Virtual Copy Policy HP 3PAR Recovery Manager Software for Oracle provides the capability to limit the number of Virtual Copies per database at any time. This can be achieved in two ways. One way is to use a time-based policy, which is based on the expiration time (the Virtual Copy is removed automatically by an internal scheduler once the expiration time is reached) of the Virtual Copy .
Recovery Manager for Oracle saves an ASCII control file and a binary control file for each created Virtual Copy in its repository. After a rollback, you may need to restore the control file in order to perform database recovery. Recovery Manager for Oracle and Third-Party Backup Tools HP 3PAR Recovery Manager Software for Oracle integrates HP 3PAR Virtual Copy Software with Symantec NetBackup (NBU), HP Data Protector and/or Oracle RMAN to perform off-host backup.
The following restrictions apply when backing up a database using the Recovery Manager for Oracle database backup utility. • • For NBU (user-managed) backup: ◦ The NBU client must be installed on the backup server, as well as on the database server. ◦ At least one NBU policy of standard type must be created and configured for database backup. Optionally, a separate NBU policy of standard type can be created and configured for archive log destination backup.
Client-side Backup During client-side backup, Recovery Manager for Oracle performs the following: • Creates an online, offline, datafile, or archonly Virtual Copy for the database or archive log destination. • Mounts the Virtual Copy on the backup server. For NBU (user-managed) backup, Recovery Manager for Oracle: • Generates an include list file that contains a list of datafiles and/or archive log destination on the mounted Virtual Copy and stores it in the /usr/openv/netbackup/include_list.
/usr/openv/netbackup/include_list. file, which contains a list of files on the Virtual Copy for backup. • Once the backup process is completed, the NBU client executes the bpend_notify. script to perform Virtual Copy cleanup. NOTE: The bpstart_notify and bpend_notify scripts are generated at /usr/openv/netbackup/bin during the creation of the Recovery Manager Configuration file. By default, the bpstart_notify script (for database backup policy) performs an online backup.
The Database Restoration Utility The database restoration utility of HP 3PAR Recovery Manager Software for Oracle restores databases, tablespaces, datafiles, or archive logs from a backup image of a Virtual Copy. The Virtual Copy must be previously backed up using the rmora_backup command. The Virtual Copy must have a backup status of Y in order to be restored. The backup status of a Virtual Copy can be retrieved using the Recovery Manager display utility (see “The Virtual Copy Display Utility” (page 12)).
Recovery Manager for Oracle with Oracle Standby Database All HP 3PAR Recovery Manager Software for Oracle’s utilities can be run against an Oracle physical standby database instead of the production database. This completely eliminates the performance impact on the production database.
Recovery Manager for Oracle with Remote Copy Recovery Manager for Oracle integrates with HP 3PAR Remote Copy Software to copy database virtual volumes from one HP 3PAR StoreServ Storage system (local or primary) to another (remote or secondary). Once copied, database Virtual Copies (application consistent snapshots) are created on the remote storage system or secondary storage system. The Virtual Copies can be used for disaster recovery or other off-host processing purposes.
NOTE: For more details about using the tunevv command, see the HP 3PAR Operating System Software User Guide. 3. On HP 3PAR StoreServ Storage system, enter showtask to monitor the Virtual Volume conversion completion.
2 Installing and Uninstalling Recovery Manager This chapter describes how to install, verify, and remove HP 3PAR Recovery Manager Software for Oracle on systems running Linux, Solaris, HP UX, and AIX. Referencing the Support Matrix For information about supported hardware and software platforms, refer to the Single Point of Connectivity Knowledge for HP Storage Products (SPOCK) website: http://h20272.www2.hp.com/.
• ◦ If you install the NetBackup for Oracle client, you must link the Oracle libobk.so library on the database and backup servers to point to the Symantec NetBackup Media Library. For more information, refer to Symantec’s NetBackup for Oracle documentation. ◦ If you separate the NetBackup master server from the backup server, you must also install Recovery Manager for Oracle on the NetBackup master server.
• Refer to the HP 3PAR Implementation Guides for instructions on setting up connections from hosts to the HP 3PAR StoreServ Storage systems and reserving LUNs with specific Host Bus Adapters (HBAs) and Multipath configurations. • To use the Remote Copy feature, you must configure your HP 3PAR StoreServ Storage systems for Remote Copy Software. The HP 3PAR StoreServ Storage systems must meet the requirements specified in “Recovery Manager for Oracle’s Remote Copy Requirements” (page 118).
Installation The following section describes the steps necessary for installing or upgrading Recovery Manager for Oracle on a Linux system. To install or upgrade HP 3PAR Recovery Manager: 1. Log in as the root user. 2. Insert the HP 3PAR Recovery Manager CD into a CD-ROM drive. NOTE: If the CD is not mounted automatically, mount it manually. # mount -t iso9660 -r /dev/cdrom /mnt/cdrom 3. Change to the CD-ROM drive. # cd /mnt/cdrom0/ 4. Enter ./rmora_install.sh.
5. After the installation is complete on all the required servers, you can allow Oracle users and Database Administrators group access to the Recovery Manager commands and utilities by running the rmora_chown utility if you did not specify during step 4. You can use the utility command to allow only root or both root and a single non-root user to manage all RMO database configurations.
If you are not using the backup server as the NetBackup master server, be sure to install Recovery Manager for Oracle on the NetBackup master server. Installation To install or upgrade HP 3PAR Recovery Manager on a Solaris system: 1. Log on as the root user. 2. Insert the HP 3PAR Recovery Manager CD into a CD-ROM drive. If the CD is not mounted automatically, mount it manually. # mount -F hsfs -o ro /dev/dsk/c0t6d0s2/cdrom 3. Change to the CD-ROM drive. # cd /cdrom/cdrom0/ 4. Enter ./rmora_install.sh.
2. Insert the HP 3PAR Recovery Manager CD into a CD-ROM drive. If the CD is not mounted automatically, mount it manually. # mount -F hsfs -o ro /dev/dsk/c0t6d0s2/cdrom 3. Change to the CD-ROM drive. # cd /cdrom/cdrom0/ 4. Enter ./rmora_uninstall.sh. Confirm you want to uninstall RMO when prompted. # ./rmora_uninstall.sh Welcome to HP 3PAR Recovery Manager for Oracle Checking for existing Recovery Manager installation... The following version of RMOra has been found: Currently Installed version: 4.4.0.
4. Enter ./rmora_install.sh. The prompts and output from running rmora_install.sh are similar to those when running rmora_install.sh on Linux. If necessary, refer to “Installation” (page 29). 5. After the installation is complete on all the required servers, you can allow Oracle users and the Database Administrators group access to the Recovery Manager commands and utilities by running the rmora_chown utility if you did not specify during step 4.
Installing Recovery Manager for Oracle on IBM AIX Systems Use the instructions in this section to install Recovery Manager for Oracle on the database and backup servers. If you are not using the backup server as the NetBackup master server, be sure to install Recovery Manager for Oracle on the NetBackup master server. Installation The following section describes the steps necessary for installing Recovery Manager for Oracle on IBM AIX system. To install HP 3PAR Recovery Manager on IBM AIX system: 1.
SUCCESSES --------Filesets listed in this section passed pre-installation verification and will be installed. Selected Filesets ----------------RMOra.rte 4.4.0.1 # Recover Manager for Oracle o... << End of Success Section >> +-----------------------------------------------------------------------------+ BUILDDATE Verification ... +-----------------------------------------------------------------------------+ Verifying build dates...
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 4.4.0.1. Removing Recovery Manager from IBM AIX Systems To remove 3PAR Recovery Manager from IBM AIX system: 1. Log in as the root user. 2. Insert the HP 3PAR Recovery Manager CD into a CD-ROM drive. NOTE: If the CD is not mounted automatically, mount it manually.
4. Enter ./rmora_uninstall.sh. Confirm you want to uninstall Recovery Manager for Oracle when prompted. Welcome to HP 3PAR Recovery Manager for Oracle Checking for existing Recovery Manager installation... The following version of RMOra has been found: Currently Installed version: 4.4.0.1 Do you want to remove the existing RMOra? (y/n) y Removing existing RMOra... +-----------------------------------------------------------------------------+ Pre-deinstall Verification...
3 Configuring Recovery Manager for Oracle Recovery Manager for Oracle requires that an SSH connection be configured for the backup server, the database server, the Symantec NetBackup master server, and the HP 3PAR StoreServ Storage system. Since Recovery Manager for Oracle can be run by either the root user or an Oracle user (Oracle owner), configure SSH for the root or an Oracle user. NOTE: Recovery Manager for Oracle supports Symantec NetBackup and HP Data Protector as the root user or an Oracle user.
Figure 2 SSH Connection Relationship for Remote Copy Support SSH Restrictions Recovery Manager for Oracle has the following SSH restrictions: • The ssh and scp commands must be located in the /usr/bin/ directory. Create symbolic links, if necessary.
3. If you are using HP UX, verify that the SSH daemon has strict mode disabled: a. Check the sshd_config file for the following line: StrictModes no b. If StrictModes is set to yes, change the entry to no. Generating an SSH Key Pair for the Backup Server To generate an SSH key pair for the backup server: 1. Log on to the backup server as the root or Oracle owner user. 2. Create a key pair with no passphrase using the ssh-keygen command. If a key-pair already exists, skip this section.
Setting Up Connections from the Backup Server to the Database Server To set up an SSH connection from the backup server to the database server: • Copy the public key (id_rsa.pub) of the backup server to the authorized_keys file of the database server. # scp ~/.ssh/id_rsa.pub :~/.ssh/authorized_keys If the authorized_keys file already exist, add the public key (from ~/.ssh/id_rsa.pub on the backup server) to the end of the authorized_keys file on the database server.
yes Warning: Permanently added '' (DSS) to the list of known hosts. where is either the root or the Oracle owner user and is the name of the NBU master server. NOTE: If you are prompted for a password, the setup is incorrect and you must perform the previous setup again. Setting Up Connections from the Backup Server to the HP 3PAR StoreServ Storage To set up an SSH connection from the backup server to the HP 3PAR StoreServ Storage system: 1.
4. Copy the public key of the backup server to the HP 3PAR StoreServ Storage system. You can find the public key in the location specified when generating an SSH key pair; for more information, see “Generating an SSH Key Pair for the Backup Server” (page 40). # ssh @ 's password: cli% setsshkey Please enter the SSH public key below. When finished, press enter twice. The key is usually long.
Setting Connections from the Database Server to the HP 3PAR StoreServ Storage Skip this step if the database server has the same SSH key pair as the SSH key pair of the backup server (see “Generating an SSH Key Pair for the Database Server” (page 40)). Recovery Manager for Oracle uses the same CLI user to access the HP 3PAR StoreServ Storage system from either the backup server or the database server.
4. Copy the public key of the database server to the HP 3PAR StoreServ Storage system. # ssh @ 's password: cli% setsshkey Please enter the SSH public key below. When finished, press enter twice. The key is usually long. It's better to copy it from inside an editor and paste it here. (Please make sure there are no extra blanks.
Setting up National Language Host Support The Recovery Manager for Oracle message catalog and the symbolic link are installed in the following locations: OS Recovery Manager for Oracle Message Catalog Location Symbolic Link Location Solaris /opt/3PAR/msg/en_US /usr/lib/locale/en_US Linux /opt/3PAR/RMOra/msg/en_US /usr/lib/locale/en_US HP UX /opt/3PAR/msg/en_US /usr/lib/nls/msg/C AIX /opt/3PAR/msg/en_US /usr/lib/nls/msg/en_US • To retrieve the text messages properly, you must set the NLSPATH
NOTE: This section is intended for the users who are familiar with the Oracle Database and Symantec NetBackup (NBU). For more information on creating a NetBackup policy, refer to Symantec NetBackup documentation. Configuring the NetBackup Policy for Database Backup For Recovery Manager for Oracle to perform backup and restoration correctly, you must use the following guidelines in conjunction with Symantec NetBackup documentation when configuring a NBU policy: Backup Attribute 1.
be set to at least 600 seconds (10 minutes) to allow enough time for Recovery Manager to perform all necessary operations prior to the actual backup. For example, to set the BPSTART_TIMEOUT and BPEND_TIMEOUT parameters to 600 seconds (10 minutes), modify the corresponding parameters in /usr/openv/netbackup/bp.
# /opt/omni/sbin/omnisv start Configuring Oracle Operating System User Account (Oracle Owner Account) The Oracle operating system user is the owner of the Oracle Home. Add the Oracle operating system user account to the HP Data Protector admin group.
An HP Data Protector Oracle backup specification must be created as follows: • A backup specification must be an Oracle backup specification, not a file system backup specification. • Select 3PAR_RMO_Online, 3PAR_RMO_Offline, or 3PAR_RMO_Data template for database backup or 3PAR_RMO_Archive template for archive log backup. • Select control file object. • Application: • • ◦ Client: Select the host name of the database server to be configured for backup.
• Backup Specification Option: ◦ ◦ ◦ Pre-exec: – Pre-exec: Specifiy DP_pre.. – On client: The host name of the Recovery Manager for Oracle backup server where the pre-exec script will be executed. Post-exec: – Post-exec: Specifiy DP_post.. – On client: The host name of the Recovery Manager for Oracle backup server where the post-exec script will be executed. Ownership: – User: The user name of the Oracle owner.
OR backup format 'backup_specification .dbf archivelog all not backed up 1 times skip inaccessible; • If control file object is selected, change the following lines: backup format 'backup_specification .dbf current controlfile; Change these lines to: backup format 'backup_specification .
In addition, you must create an Oracle RMAN Recovery Catalog and configure Oracle TNS Service and Listener to allow connections to the Recovery Catalog from the database server and backup servers. The Recovery Catalog can be created on any server. Recovery Manager for Oracle recommends that the Recovery Catalog be created on the backup server. See “Creating an RMAN Recovery Catalog” (page 54) for instructions.
This procedure is to backup archive logs only. For Recovery Manager for Oracle to perform backup and restoration correctly, you must use the following guidelines in conjunction with Symantec NetBackup documentation when configuring a NBU policy: Backup Attribute Select the Oracle type for the policy. Backup Selections 1. Enter the location of RMAN backup script (/etc/3par/solutions/.ora./rmora_nbu_archbackup.sh). 2.
where: 4. • is the tablespace name of the Recovery Catalog. • is the user name to be granted access permission to the Recovery Catalog. • is the password for the . Create the RMAN Recovery Catalog tables as follows: $ rman catalog /@ RMAN> create catalog tablespace ; 5. Configure TNS services for the Recovery Catalog database by adding an entry in the $ORACLE_HOME/network/admin/tnsnames.
When using RMAN backup with HP Data Protector, if the Oracle release of the recovery catalog database is 11g R2 or later: • Ensure that the owner of the recovery catalog is granted the CREATE ANY DIRECTORY and the DROP ANY DIRECTORY system priviledges. SQL> grant CREATE ANY DIRECTORY to ; SQL> grant DROP ANY DIRECTORY to • Ensure that the owner of the recovery catalog has SELECT permissions on v_$instance view.
• 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 of the specified database instance if it can be retrieved from the oratab file. Press ENTER to accept default value or enter the ORACLE_HOME location of the specified database instance.
• HP 3PAR StoreServ Storage user name for the backup server [h=help,q=quit]? Recovery Manager for Oracle requires that a HP 3PAR OS Software user must be created on the HP 3PAR StoreServ Storage to allow access from the backup server to the HP 3PAR StoreServ Storage. • 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 the Virtual Copy will be retained.
• Do you want to remove oldest Virtual Copy when the maximum number of Virtual Copy is reached [y=yes,n=no,q=quit]? You will be prompted with this question if you set the maximum number of Virtual Copies in the previous question. Enter n if you do not want to remove the oldest Virtual Copy when maximum number of Virtual Copy is reached. Otherwise, enter y.
• NetBackup full schedule name for policy 'your policy name'[h=help,s=skip,q=quit]? You will be prompted with this question only if you previously selected Symantec NetBackup as the third-party backup tool. Enter a schedule name for the policy provided for the previous question that is used to perform full database backup.
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 displayed. If the X11 server is not running, issue the following command: # xhost + b. Ensure the DISPLAY environment variable is set. # echo $DISPLAY c. Start the Recovery Manager GUI.
• Create one or two Remote Copy groups, assign all virtual volumes used by datafiles and archive log destinations to one group if only one group is created, or two separate groups if two groups are created. CAUTION: Symantec Volume Manager VxVM: If Symantec Volume Manager VxVM is being used when assigning HP 3PAR virtual volumes to Remote Copy groups, all volumes in the same VxVM disk group should be assigned to a Remote Copy group, whether they are actually being used by the Oracle database or not.
Press ENTER to accept the default value, or enter the ORACLE_HOME of the ASM instance on the database server. • Oracle Home of ASM instance on the backup server [h,q]? Recovery Manager for Oracle assumes that the ORACLE_HOME of the ASM instance on the backup server is the same as the ORACLE_HOME of the ASM instance on the database server. Press ENTER to accept the default value, or enter ORACLE_HOME of the ASM instance on the backup server.
day, or 'h' or 'H' for hours after the amount of time. The default value, '0d', means the Virtual Copy has no expiration time. ◦ Count-based or numeric-based policy: Either skip this question or use the default value '0' for the expiration date. You will be prompted for the maximum Virtual Copies you want the system to keep. NOTE: • The numeric-based policy is deprecated and will be removed in a future release.
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 displayed. If the X11 server is not running, issue the following command: # xhost + b. Ensure the DISPLAY environment variable is set. # echo $DISPLAY c. Start the Recovery Manager for Oracle GUI.
4 Using the Recovery Manager Command Line Interface This chapter describes the Recovery Manager for Oracle command line utilities. NOTE: The command line utilities are located in /opt/3PAR/RMOra/bin. To view error messages, their explanations, and appropriate troubleshooting actions in a web browser, select Help→Event Messages from the menu bar. Alternatively, see “Troubleshooting” (page 155).
method, a database can be backed up to a local disk (Symantec NetBackup or HP Data Protector is not required) or to a tape using Symantec NetBackup or HP Data Protector. If Oracle RMAN (with or without Symantec NetBackup or HP Data Protector) is selected, the primary (not standby) database must be registered with an Oracle Recovery Catalog. Starting with Oracle 11g, an RMAN backup image of a standby database to local disk cannot be seen from the Recovery Catalog from the production database.
backup (archlog). Refer to Recovery Manager User's Guide for detail on how to create HP Data Protector Backup Specification. Depending on which backup method has been configured for the Recovery Manager, the rmora_backup command performs the following actions: • Creates a Virtual Copy (online, offline, datafile, or archlog) for the database or archive log destination if a Virtual Copy is not specified.
The host name of the database server, on which the Oracle database instance is running. The value of the database server name must match the output of the hostname command. -t The timestamp of a Virtual Copy to be backed up. The Virtual Copy name can be obtained using the rmora_display command. -o online Creates an online Virtual Copy of a database while it is OPEN (online) prior to backup. This option is ignored if a Virtual Copy is specified.
This option is only applicable for Oracle RMAN with HP Data Protector backup. This option can be used with the -o online|offline|datafile option to perform incremental backup of a database virtual copy. By default, the incremental backup is differential. To perform cumulative incremental backup, the RMAN script from the HP Data Protector Backup Specification must be changed manually. -v Runs the command in verbose mode.
rmora_checkconfig SYNTAX rmora_checkconfig -s -p [-o all|skipdatabase|databaseonly] [-v] DESCRIPTION The rmora_checkconfig command validates a Recovery Manager for Oracle configuration file for a specified database. A configuration file must have been created prior to using this command. By default, all configured parameters in the specified configuration file will be validated. One can select to validate only database parameters or non-database parameters.
changes the permissions and owners of the necessary files and directories in order to enable an Oracle binary owner to operate Recovery Manager for Oracle. Each Recovery Manager for Oracle repository (under /etc/3par/solutions/) should be owned by either the super user or the Oracle binary owner. Different repositories could be owned by different Oracle binary owners.
rmora_config SYNTAX rmora_config [-s -p [-l]] DESCRIPTION The rmora_config command creates or modifies the Recovery Manager for Oracle configuration file for a database. A configuration file for each database must be created prior to using any database snapshot (Virtual Copy) utilities provided by Recovery Manager for Oracle. The configuration file will be created at /etc/3par/solutions/.ora./config. An equivalent environment file (config_exp.
the current time, that the volume will be retained. To specify a retention time, specify a value between 1 to 43,800 hours (1825 days). Retention time considerations: ◦ This feature requires a separate HP 3PAR Virtual Lock license. ◦ The maximum retention time (VVRetentionTimeMax) is either the system's VVRetentionTimeMax (1825 days) or the virtual domain's VVRetentionTimeMax. – If the volume belongs to a domain, then its retention time cannot exceed the VVRetentionTimeMax value of the domain (if set).
• DBFILE_SCHED_FULL - The Symantec NetBackup schedule name for database backup. This parameter is applicable only to the Symantec NetBackup backup method. • ARCH_SCHED_FULL - The Symantec NetBackup schedule name for archive log backup (full). This parameter is applicable only to the Symantec NetBackup backup method. • ARCH_SCHED_INCR - The Symantec NetBackup schedule name for archive log backup (incremental). This parameter is applicable only to the Sysmantec NetBackup backup method.
rmora_create SYNTAX rmora_create -s -p [ -o online|offline|datafile|archlog] [ -r {d|D|h|H} -f] [ -e {d|D|h|H}] [-v] DESCRIPTION The rmora_create command can be used to create an online, offline, datafile, or archive log Virtual Copy of a specified Oracle database instance. The Oracle database instance can be either a regular database or a physical standby database.
When creating an online or datafile Virtual Copy: • If the specified database instance is a regular database, the database will be temporarily put into backup mode before the Virtual Copy of datafile virtual volumes is created. The database will be then taken out of backup mode. An archive log switch will be performed before Virtual Copies of archive log virtual volumes are created.
OPTIONS The following options are supported: -s The Oracle SID of the database instance. For Real Application Cluster (RAC) database, an Oracle SID of any RAC instance can be specified. -p The corresponding host name of the database server where the specified Oracle database instance is running. The value of the database server name must match the output of the hostname command.
NOTE: HP 3PAR Operating System Software CLI command showsys -param and showdomain -d can be used to check the value of VVRetentionTimeMax for value system and domain respectively. For online backup, because the Virtual Copy for datafile volumes and the Virtual Copy for archive log destinations are taken at different times, their retention time are slightly different.
rmora_createdb SYNTAX rmora_createdb -s -p -t [-n ] [-h ] [-o ascii|binary|for_backup[,recovery|norecovery]] [-d ] [-v] DESCRIPTION The rmora_createdb command creates a fully functional single-instance database or starts up a clone database in MOUNTED mode for RMAN backup purposes. The fully functional single-instance database can be used for any off-host processing purpose.
OPTIONS The following options are supported: -s The Oracle SID of the database instance. For Real Application Cluster (RAC) database, an Oracle SID of any RAC instance can be specified. -p The corresponding host name of the database server where the specified Oracle database instance is running. The value of the database server name must match the output of the hostname command. -t The timestamp of a Virtual Copy. It is also the name of the Virtual Copy.
rmora_display SYNTAX rmora_display -s -p [-t ] [-r] DESCRIPTION The rmora_display command displays database Virtual Copies, along with other information including creation time, type, status and backup status. A type of Virtual Copy can be either Online, Offline, Datafile, or Archlog. • Online or Offline Virtual Copy - Indicates that the Virtual Copy was created for the database while it was OPEN (online) or CLOSED (offline), respectively.
Displays the Virtual Copy’s retention and expiration time. This option is only available for HP 3PAR Operating System Software 2.3.1 or , otherwise, this option is ignored. EXAMPLES • rmora_display -s TEST920 -p pilot. # Name Create Time Type Status Backup? ============ ======================== ======= ========= ======== • 1. 012403154751 Fri Jan 24 15:47:51 2003 Offline Available N 2. 012403154650 Fri Jan 24 15:46:50 2003 ArchLog Available N 3.
rmora_export SYNTAX rmora_export -s -p -t -r -e [-l ] [-v] DESCRIPTION The rmora_export command exports a Virtual Copy's repository from the current backup server to an alternate backup server. The exported Virtual Copy can then be mounted or cloned at the alternate backup server.
HP 3PAR StoreServ Storage system user can be created using the HP 3PAR Operating System Software CLI createuser command. The created user must be assigned the edit role (privilege) or 3PAR_RM role. -v Runs the command in verbose mode.
rmora_mount SYNTAX rmora_mount -s -p -t [-m ] [-r] [-v] DESCRIPTION The rmora_mount command mounts an existing Virtual Copy created by the rmora_create command or rmora_rsync command on the backup server. The mounted Virtual Copy can be used for off-host processing purposes such as backup or database cloning.
• Imports snapshot LVM volume groups and activates all corresponding LVM snapshot volumes if the database files reside on LVM volumes. • For Virtual Copies from an ASM-managed database, based on the different ASM database releases on the backup server, the operation is different. • ◦ For ASM versions 10.2.0.5, 11.0.1.7 or , if an ASM instance exists and is up on the backup server, then all diskgroups from the Virtual Copy are mounted in this ASM instance.
rmora_remove SYNTAX rmora_remove -s -p -t [-v] DESCRIPTION The rmora_remove command removes a database Virtual Copy that was created using the rmora_create command. The Virtual Copy must have a status of Available to be removed. (To view the status of the Virtual Copy, use the rmora_display command.
rmora_removedb SYNTAX rmora_removedb -s -p -t [-n ] [-h ] [-f] [-v] DESCRIPTION The rmora_removedb command removes a clone database that was created using the rmora_createdb command. The clone database is shutdown with the shutdown immediate option. All files (Oracle parameter file, control files, and redo logs), previously created with the rmora_createdb command are removed. The Virtual Copy remains mounted.
rmora_restore SYNTAX rmora_restore -s -p [-t ] [-T ] [-D ] [-m ] [-h ] [-S ] [-H ] [-c] [-v] DESCRIPTION Restores database files from a Virtual Copy backup image. The rmora_restore command restores databases, tablespaces, data files, and/or archive logs from a Virtual Copy backup image. The Virtual Copy must have been previously backed up using the rmora_backup command.
image cannot be seen from the Recovery Catalog from the primary (production) database. To restore, the following steps must be performed manually: ◦ The backup image (pieces) must be manually copied from the backup server to the primary (production) server. ◦ The backup pieces must be then cataloged manually with the Recovery Catalog from the primary (production) server. ◦ Perform restore manually using Oracle RMAN.
-t The timestamp of a Virtual Copy whose backup image is used for restoration. Use the rmora_display command to retrieve a list of the Virtual Copy names. If a name is not specified, the most recent Virtual Copy’s backup (full) image is used for the restoration. -T The tablespace(s) that need to be restored. Use commas to separate multiple tablespace names (no space between the tablespace names). -D The datafile(s) that need to be restored.
rmora_rmrep SYNOPSIS rmora_rmrep -s -p [-t ] [-f] [-v] DESCRIPTION The rmora_rmrep command removes a Virtual Copy repository, specified by the parameter. If the is not specified, the entire database repository will be removed. If removing a Virtual Copy repository, the status of a Virtual Copy must be Removed and its backup status must be N. If the status of a Virtual Copy is Y, the -f option can be used to force the removal of the repository.
rmora_rollback SYNOPSIS rmora_rollback -s -p -t [-o data|arch] [-v] [-w] [-f] DESCRIPTION The rmora_rollback command promotes the volumes of a database Virtual Copy back to their base virtual volumes. Once promoted, the database virtual volumes will be exactly the same as the volumes of the database Virtual Copy. If the Virtual Copy is the snapshot image of a standby database, it can only be used to promote back to the standby database virtual volumes.
The corresponding host name of the database server where the specified Oracle database instance is running. The value of the database server name must match the output of the hostname command. -t The timestamp of a Virtual Copy from which to promote. The Virtual Copy name can be obtained using the rmora_display command. -o [data|arch] • data Promotes only the Virtual Copy’s datafile volumes back to their base virtual volumes.
rmora_rsync SYNTAX rmora_rsync -s -p [-l ] [ -o online|offline|validate] [ -r {d|D|h|H} -f] [ -e {d|D|h|H}] [-v] DESCRIPTION The rmora_rsync command can be used to create an online of offline database Virtual Copy on the remote/secondary and local/primary HP 3PAR StoreServ Storage system in a Remote Copy or Synchronous Long Distance Remote Copy configuration. NOTE: This feature requires the HP 3PAR Remote Copy Software license.
To use the rmora_rsync command, the following requirements must be satisfied: • Each database instance must be started up using either a parameter file (pfile) or server parameter file (spfile) from default location ($ORACLE_HOME/dbs). • The database must be running in archive log mode and automatic archival must be enabled in order to create an online Virtual Copy. • If archive log mode is enabled, the datafiles and archive logs must reside on separate HP 3PAR virtual volumes.
-o online Create an online database Virtual Copy in Remote Copy or Synchronous Long Distance configuration. The specified database instance must be online. -o offline Create an offline database Virtual Copy in Remote Copy or Synchronous Long Distance configuration. The specified database instance must be offline. -o validate Validates the Remote Copy configuration. -v Runs the command in verbose mode. -f Force to create a database Virtual Copy with a retention time.
rmora_set SYNTAX rmora_set -s -p -t [-r
• The retention time set during configuration time serves as the default value all Virtual Copies created thereafter. • The retention time can be specified during a Virtual Copy creation to overwrite the retention value set during the Recovery Manager for Oracle configuration. • The retention time can be modified but it can not be lower than the original setting. • The retention time can be specified in hours or days.
rmora_umount SYNTAX rmora_umount -s -p -t [-f] [-v] DESCRIPTION The rmora_umount command unmounts a mounted database Virtual Copy, which was previously mounted using the rmora_mount command. The Virtual Copy must have Mounted or Mounted(P) status in order to be unmounted. The Virtual Copy unmounting process only removes the read-write Virtual Copy; the read-only Virtual Copy remains intact.
5 Using the Recovery Manager for Oracle Graphical User Interface The following section describes how to use the GUI to perform specific operations relating to the maintenance of existing databases. For more information about using the CLI utilities, see “Using the Recovery Manager Command Line Interface” (page 66). Starting and Stopping the Recovery Manager for Oracle GUI The Recovery Manager for Oracle Graphical User Interface (GUI) is installed when the RMOra package is installed.
4. Press ENTER. NOTE: It is a known issue that the mouse events are not captured correctly on the cygwin x-server for Java6. Stopping the GUI To stop the Recovery Manager for Oracle GUI, select either Exit in the top left hand corner of the console window, or select the Exit menu item under the Console drop-down menu. Creating Configuration Files Recovery Manager for Oracle relies on configuration files for most of its operations.
3. 4. 5. 6. Select the desired options from the Backup Method group box. • Online (Hot) backup - The involved database instance must be open for this operation. The database is put in backup mode before the Virtual Copy is created. After the Virtual Copy creation is completed, the database is taken out of backup mode. • Offline (Cold) backup - The involved database instance must be shut down normally for this operation.
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 numeric-based policy. The numeric-based policy will not be supported in a future release. To create a time-based Virtual Copy policy: 1. Right-click the database on which you will create the Virtual Copy policy from the navigation tree and select Modify Configuration. The Modify Recovery Manager Configuration Properties wizard appears. 2. 3. 4. 5. 6.
6. 7. (Optional) Select Default retention time and enter a numeric value from 1 to 1,825 (Days) or 1 to 43,800 (Hours) in the adjacent field to set the number of days or hours that a newly created Virtual Copy must be retained before it becomes a candidate for removal. Click Next and then Finish. To update a numeric-based Virtual Copy policy: 1. Right-click Virtual Copy Management under the database on which you wish to create the Virtual Copy policy from the navigation tree and select Policy.
Mounting a Virtual Copy After a Virtual Copy is created, it can be mounted on the backup server where the Recovery Manager for Oracle GUI is running. To mount a Virtual Copy, perform the following procedure: 1. Right-click the Virtual Copy you wish to mount. 2. Click Mount. A screen appears showing the Virtual Copy name, and creation time. You are prompted for the mount point where you want the Virtual Copy to be mounted on the backup server. The default mount point is: /etc/3par/solutions/.ora.
Viewing Rollback Status It may take several minutes to rollback a Virtual Copy depending on its size. To view a Virtual Copy’s rollback status: 1. Right-click the Virtual Copy you rolled back and select Rollback Status. The Information dialog box appears displaying the status of the rollback operation. 2. Click OK to close the dialog box. Removing a Virtual Copy If the Virtual Volume State column displays Available, the Virtual Copy can be deleted.
Restoring Archive Log, Datafiles, and Tablespaces NOTE: If Symantec NetBackup (NBU) is used to back up datafiles, NBU can be used to restore datafiles to the database server, backup server, or any other hosts where the NBU clients for the same NBU master server are configured. If the Virtual Copy is being backed up using NBU, the backup key has the format: __. To restore a datafile or tablespace: 1. Select Virtual Copy Management in the navigation tree. 2.
database, or to clone the database for testing, decision making, and report generating purposes. The cloning capability takes the workload out of the database server and reduces performance impact. In order to create the cloned database from Virtual Copies, these Virtual Copies must be created by Recovery Manager for Oracle with the online or offline database option. The cloned database is created on the backup server. To clone a database: 1. Select a Virtual Copy that has a status of Mounted. 2.
4. 5. (Optional) Select Retention time and enter a numeric value from 1 to 1,825 (Days) or 1 to 43,800 (Hours) in the adjacent field. Click Finish. After the periodic synchronization process is started, the command log view of the Recovery Manager for Oracle GUI displays a status of started and then changes to Success when the Virtual Copy is created.
3. Select the Backup Type. NOTE: a. b. c. 4. 5. Incremental backup of archive log using RMAN is not supported. Full backup - Performs a full backup of a Virtual Copy. If Symantec NetBackup is selected as the backup method, this option can be used with the -o archonly option to perform full backup of an archonly Virtual Copy. If Oracle RMAN is selected as the backup method, this option can be used to perform full backup of an online or offline Virtual Copy.
Recovery Manager for Oracle Online Help appears in a web browser. Using a Web Browser to Access Online Help and Event Messages Recovery Manager for Oracle supports the latest versions of Firefox. If the Recovery Manager for Oracle GUI is unable to launch online help or event messages in Firefox, it attempts to launch your system’s default browser. If the Recovery Manager for Oracle GUI is unable to launch a browser, it prompts you to install Firefox as follows: OS Firefox Version Linux 3.6.
6 Using the Recovery Manager Rollback Utility Recovery Manager for Oracle provides a way to rollback a database to a point-in-time image by promoting a read-only or read-write Virtual Copy back to the base (database) virtual volumes. The base (database) virtual volume must not be exported to any host during the rollback process. In other words, the database LUNs of the corresponding database virtual volumes must be removed from the database server prior to the rollback process.
5. On the HP 3PAR StoreServ Storage system, remove the VLUNs for the database virtual volumes. Example: cli>removevlun Oracle_data1 101 pilot 6. 7. Keep the list of the VLUNs, which are removed by the command . The database virtual volumes need to be exported to the same VLUNs. From the backup server, perform a rollback of the database virtual volumes using a database read-only Virtual Copy. Example: # rmora_rollback -s TEST920 -p pilot -t 042903142921 -v NOTE: 8.
Rollback Using a Database Read-Write Virtual Copy The steps to rollback from a read-write Virtual Copy are the similar to rollback from a read-only Virtual Copy. First, perform step 1 to 6 from the section “Rollback Using a Database Read-Only Virtual Copy” (page 114) on the database server for the primary database. Then perform the following steps: 1. On the backup server, if a clone database is created, shutdown the database.
10. On the backup server, if needed, mount the file systems if the read-write virtual copy contains file systems. Example: # mount -F vxfs /dev/vx/dsk/datadg/datavol/oradata 11. On the backup server, if needed, mount database ASM disk groups if ASM is in use and contained in the read-write virtual copy volumes Example: SQL>alter diskgroup mount; 12. On the backup server, bring up the clone database if needed.
7 Using Remote Copy with Recovery Manager Overview HP 3PAR Remote Copy Software helps you safeguard against disasters by copying (synchronizing) virtual volumes from one HP 3PAR StoreServ Storage system to another.
On the backup server: • Run /opt/3PAR/RMOra/bin/rmoragui to start the Recovery Manager for Oracle Graphical User Interface (GUI). or • Run /opt/3PAR/RMOra/bin/rmora_config to start the Command Line Interface (CLI). To set up the configuration file for Remote Copy, see “Creating a Recovery Manager for Oracle Configuration File for Remote Copy Configuration” (page 61).
Figure 5 Asynchronous Periodic Remote Copy Configuration A Remote Copy configuration can also be configured as a Synchronous Long Distance configuration. Typically, a synchronous long distance Remote Copy configuration involves three HP 3PAR StoreServ Storage systems. Database virtual volumes are synchronized from one system to the two other systems. One is synchronized using synchronous mode. The other is synchronized using asynchronous periodic mode. See Figure 6 (page 121).
Figure 6 Synchronous Long Distance Remote Copy Configuration Creating Virtual Copies To create Virtual Copies, use the rmora_sync command or the Recovery Manager for Oracle GUI. Refer to “rmora_rsync” (page 96).
8 Support and Other Resources Contacting HP For worldwide technical support information, see the HP support website: http://www.hp.
For information about: See: Migrating data from one HP 3PAR storage system to another HP 3PAR-to-3PAR Storage Peer Motion Guide Configuring the Secure Service Custodian server in order to monitor and control HP 3PAR storage systems HP 3PAR Secure Service Custodian Configuration Utility Reference Using the CLI to configure and manage HP 3PAR Remote Copy HP 3PAR Remote Copy Software User’s Guide Updating HP 3PAR operating systems HP 3PAR Upgrade Pre-Planning Guide Identifying storage system components
For information about: See: Planning for HP 3PAR storage system setup Hardware specifications, installation considerations, power requirements, networking options, and cabling information for HP 3PAR storage systems HP 3PAR 7200 and 7400 storage systems HP 3PAR StoreServ 7000 Storage Site Planning Manual HP 3PAR 10000 storage systems HP 3PAR StoreServ 10000 Storage Physical Planning Manual HP 3PAR StoreServ 10000 Storage Third-Party Rack Physical Planning Manual Installing and maintaining HP 3PAR 7200
Typographic conventions Table 1 Document conventions Convention Element Bold text • Keys that you press • Text you typed into a GUI element, such as a text box • GUI elements that you click or select, such as menu items, buttons, and so on Monospace text • File and directory names • System output • Code • Commands, their arguments, and argument values • Code variables • Command variables Bold monospace text • Commands you enter into a command line interface • System
9 Documentation feedback HP is committed to providing documentation that meets your needs. To help us improve the documentation, send any errors, suggestions, or comments to Documentation Feedback (docsfeedback@hp.com). Include the document title and part number, version number, or the URL when submitting your feedback.
A Case Study: Remote Copy with Recovery Manager for Oracle Introduction HP 3PAR Recover Manager Software for Oracle provides a utility, rmora_rsync, which can be used to support one-to-one synchronous or asynchronous periodic HP 3PAR Remote Copy configurations or Synchronous Long Distance configurations, and provides a quick restore and recovery for Oracle databases when failures occur.
oracleasm-support-2.1.4-1.el5 oracleasmlib-2.0.4-1.el5 The database ASM11GR2 uses SPFILE, which is located on one of the ASM disk groups. $cat initASM11GR21.ora SPFILE='+ASM11GR2_DATADG/ASM11GR2/spfileASM11GR2.ora' Configuration Diagram Preparing for Remote Copy Operation 1. 128 Refer to the HP 3PAR Remote Copy Software User’s Guide for instructions on setting up a Remote Copy environment.
2. Create Remote Copy groups on the local storage system S256: # creatercopygroup linux_asm11gr2_data S347:sync S336:periodic # creatercopygroup linux_asm11gr2_arch S347:sync S336:periodic # creatercopygroup linux_asm11gr2_redo S347:sync NOTE: Recovery Manager for Oracle requires online redo logs and control files to be in a Remote Copy group separate from datafiles and archive log destinations on the local storage system and remote synchronous storage system.
Checking database status ... Discovering database devices ... Retrieving database Remote Copy group(s) ... Archiving online redo logs ... Putting the database in backup mode ... Initiating synchronization for datafile volumes ... Synchronization request issued for group linux_asm11gr2_data task ID = 9789 9790 9791 9792 Taking the database out of backup mode ... Archiving online redo logs ... Initiating synchronization for archive log volumes ...
1. Failover to the synchronous storage system S347. If the Remote Copy groups have not been stopped, stop the groups on S256 by issuing the following: # stoprcopygroup -f linux_asm11gr2_data # stoprcopygroup -f linux_asm11gr2_arch # stoprcopygroup -f linux_asm11gr2_redo • The failover operation changes the role of the secondary groups on the remote synchronous storage system from Secondary to Primary-Rev.
Name Target Status Role Mode Options linux_asm11gr2_arch.r256 S256 Stopped Secondary Sync LocalVV ID RemoteVV ID SyncStatus LastSyncTime lux_asm11gr2_arch1_347 4447 lux_asm11gr2_arch1 6517 Stopped 2011-06-08 15:12:11 PDT lux_asm11gr2_arch2_347 4448 lux_asm11gr2_arch2 6518 Stopped 2011-06-08 15:12:11 PDT lux_asm11gr2_arch3_347 4449 lux_asm11gr2_arch3 6519 Stopped 2011-06-08 15:12:11 PDT Name Target Status Role Mode Options linux_asm11gr2_arch.
a. From the remote synchronous system S347, issue the following commands to failover the database ASM11GR21 related Remote Copy groups to S347: # setrcopygroup failover -f -t S256 linux_asm11gr2_data.r256 # setrcopygroup failover -f -t S256 linux_asm11gr2_arch.r256 # setrcopygroup failover -f -t S256 linux_asm11gr2_redo.r256 b. After the failover operation completes, issue the showrcopy command on S347. Name Target Status Role Mode Options linux_asm11gr2_arch.
c. After failover, any LUNs associated with volumes on storage system S347 will become writable by the connected host panther. If VLUNs have not yet been created for the database volumes, issue the createvlun command from storage system S347 to create VLUNs for the corresponding database volumes on the synchronous storage system. # # # # # # # # # d.
2. Recover the Remote Copy groups from the synchronous storage system S347. • The recover operation initiates reverse replication and synchronizes the changes from the backup system to the primary system for the Remote Copy groups. Once executed, the role of the Remote Copy groups on the source system becomes Secondary-Rev. Any LUNs associated with volumes in the groups become non-writable on the source system.
On S347: Name Target Status Role Mode Options linux_asm11gr2_arch.r256 S256 Started Primary-Rev Sync LocalVV ID RemoteVV ID SyncStatus LastSyncTime lux_asm11gr2_arch1_347 4447 lux_asm11gr2_arch1 6517 Synced NA lux_asm11gr2_arch2_347 4448 lux_asm11gr2_arch2 6518 Synced NA lux_asm11gr2_arch3_347 4449 lux_asm11gr2_arch3 6519 Synced NA Name Target Status Role Mode Options linux_asm11gr2_arch.
From this output, note that the Status and Role of the three Remote Copy groups with target S356 are Started and Primary-Rev, respectively.
3. Restore the Remote Copy groups from the synchronous storage system S347. • The restore operation restores the replication for the Remote Copy groups to a pre-failover state. Once the restore operation is executed, the role of the Remote Copy groups on the source system will become Primary, and the Remote Copy groups on the backup system will become Secondary, which are the original settings.
On S347: Name Target Status Role Mode Options linux_asm11gr2_arch.r256 S256 Started Secondary Sync LocalVV ID RemoteVV ID SyncStatus LastSyncTime lux_asm11gr2_arch1_347 4447 lux_asm11gr2_arch1 6517 Synced NA lux_asm11gr2_arch2_347 4448 lux_asm11gr2_arch2 6518 Synced NA lux_asm11gr2_arch3_347 4449 lux_asm11gr2_arch3 6519 Synced NA Name Target Status Role Mode Options linux_asm11gr2_arch.
In the output , note that the Status and Role of the three Remote Copy groups on S347 are Started and Secondary, respectively.
4. Recover the RAC database ASM11GR2. Assume the Oracle binary is available and CRS is up. Mount all necessary file systems if the file systems are used. In this case, asmlib is used, so scan the oracleasm disks and then mount all database diskgroups. a. Scan oracleasm devices. dl160g6-13:# oracleasm scandisks b. Mount ASM diskgroups. alter alter alter alter alter c.
The best recovery option is recovering from the asynchronous periodic backup system S336. To recover, perform the following sequence of actions: • Perform the failover operation on the asynchronous periodic backup system S336.
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 the following: # stoprcopygroup -f linux_asm11gr2_data # stoprcopygroup -f linux_asm11gr2_arch The failover operation changes the role of secondary groups on the backup system from Secondary to Primary-Rev. Any LUNs associated with the volumes in the Remote Copy group become writable by hosts connected to the backup system.
Name Target Status Role Mode Options linux_asm11gr2_arch.r256 S256 Stopped Primary-Rev Periodic over_per_alert LocalVV ID RemoteVV ID SyncStatus LastSyncTime lux_asm11gr2_arch1_336 1651 lux_asm11gr2_arch1 6517 Stopped 2011-06-08 17:49:41 PDT lux_asm11gr2_arch2_336 1652 lux_asm11gr2_arch2 6518 Stopped 2011-06-08 17:49:41 PDT lux_asm11gr2_arch3_336 1653 lux_asm11gr2_arch3 6519 Stopped 2011-06-08 17:49:41 PDT Name Target Status Role Mode Options linux_asm11gr2_arch.
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. pe2950-24:# rmora_mount -s ASM11GR21 -p dl160g6-13 -t 060311173319 -v Verifying ssh between the backup server and the HP 3PAR Storage system ... Creating database read-write Virtual Copy ... Exporting database read-write Virtual Copy to host 'pe2950-24.3pardata.com' ... Mounting ASM disk groups ... The Virtual Copy '060311173319' is mounted successfully.
3. Back up the binary control file from the cloned database and prepare to rollback the Virtual Copy. a. Issue the RMAN command to backup the control file in the cloned database while the database is in the Mounted state. RMAN> backup current controlfile format '/tmp/clone_control'; RMAN> shutdown immediate; b. Connect to the +ASM instance on the remote backup server pe2950-24 and then unmount the related ASM diskgroups used by the cloned database.
4. Rollback the read-write Virtual Copy to the base volumes from the remote system S336. Promote the read-write Virtual Copy to its base volume by issuing the rmora_rollback -w command. a. The rmora_rollback command with the -w option requires LUNs to be removed for the base volumes. In this example, the Virtual Copy used to clone the database is 060311173319.
5. Recover the Remote Copy groups from the asynchronous periodic backup system S336 to the local system S256. The recover operation initiates reverse replication and synchronizes the changes from the backup system to the primary system for the Remote Copy groups. Once executed, the role of the Remote Copy groups on the source system becomes Secondary-Rev. Any LUNs associated with volumes in the groups become nonwritable on the source system.
On S336 Name Target Status Role Mode Options linux_asm11gr2_arch.r256 S256 Started Primary-Rev Periodic Last-Sync 2011-06-09 17:07:17 PDT , over_per_alert LocalVV ID RemoteVV ID SyncStatus LastSyncTime lux_asm11gr2_arch1_336 1651 lux_asm11gr2_arch1 6517 Synced 2011-06-09 17:15:07 PDT lux_asm11gr2_arch2_336 1652 lux_asm11gr2_arch2 6518 Synced 2011-06-09 17:15:04 PDT lux_asm11gr2_arch3_336 1653 lux_asm11gr2_arch3 6519 Synced 2011-06-09 17:14:51 PDT Name Target Status Role Mode Options linux_asm11gr2_arch.
From this output, note that the role of the Remote Copy groups from S336 are Primary-Rev.
6. Restore the Remote Copy groups from the asynchronous periodic system S336. The restore operation restores the replication for the remote copy groups to a pre-failover state. Once the restore operation is executed, the role of the Remote Copy groups on the source system will become Primary, and the Remote Copy groups on the backup system will become Secondary, which are the original settings.
From this output, note that the Status and Role of the Remote Copy groups on S336 are Started and Secondary, respectively.
7. Bring up the primary database from the database server. a. Bring up the +ASM1 instance from the node dl160g6-13, mount all diskgroups, and create a new disk group for redo files and control files. If the same name of the disk group for redo logs exists, drop it and recreate it.
[vcdba@dl160g6-13 ~]$ sqlplus '/as sysdba' SQL*Plus: Release 11.2.0.1.0 Production on Thu Jun 9 21:59:32 2011 Copyright (c) 1982, 2009, Oracle. All rights reserved. Connected to: Oracle Database 11g Enterprise Edition Release 11.2.0.1.
B Troubleshooting This appendix provides Recovery Manager for Oracle error messages, their explanations, and appropriate actions. MESSAGE ID 1003 SYMBOLIC NAME RMO_ERROR_USER_NOTFOUND MESSAGE 3PAR1003: ERROR: Could not retrieve user id and group id for username . REASON Failed to retrieve the user information for a given username. SOLUTION Review the configuration file and make sure all parameters have up-to-date values.
3PAR1007: ERROR: Cannot determine archive log mode for database . REASON Failed to retrieve the archive log mode for the specified database. SOLUTION Manually log onto the database and check if the database is running normally. Most likely, either the database is not open or the archive log destination is full, which could cause the database to hang. MESSAGE ID 1008 SYMBOLIC NAME SymbolicName = RMO_ERROR_ORAHOME_BACKUP MESSAGE 3PAR1008: ERROR: Oracle binary location on the backup server is required.
MESSAGE ID 1012 SYMBOLIC NAME RMO_ERROR_MULTIPLE_PARTITION MESSAGE 3PAR1012: ERROR: Disk has multiple partitions. REASON In Linux, the specified disk has multiple partitions defined. SOLUTION Multiple partitions are not supported by Recovery Manager for Oracle. This is to avoid the possible rollback overwriting the data on other partitions. MESSAGE ID 1013 SYMBOLIC NAME RMO_ERROR_TARGET_PWWN_NOTFOUND MESSAGE 3PAR1013: ERROR: Could not find target port WWN for port .
REASON Failed to retrieve the hostname defined in the HP 3PAR StoreServ Storage system for the backup system. SOLUTION An attempt to retrieve the host definition for the backup server on the HP 3PAR Storage system fails because the HBA host port WWNs does not match any port WWNs of the existing host definitions on the HP 3PAR Storage system. Either a host definition for the backup server has not been created or the backup server is not currently connect to the HP 3PAR Storage system.
SYMBOLIC NAME RMO_ERROR_BKUP_TAG_NOT_SPECIFIED MESSAGE 3PAR1021: ERROR: Backup tag not specified. REASON Using RMAN to backup the Virtual Copy to media with NetBackup, Recovery Manager for Oracle could not find the backup tag parameter, which should be passed from NetBackup. SOLUTION Contact customer support for further investigation. MESSAGE ID 1022 SYMBOLIC NAME RMO_ERROR_DB_STATUS MESSAGE 3PAR1022: ERROR: Could not determine status of database instance .
MESSAGE ID 1031 SYMBOLIC NAME RMO_ERROR_UNSUPPORTED_FILETYPE MESSAGE 3PAR1031: ERROR: is neither a regular file, directory, block nor a character device. REASON When discovering devices used by the Oracle database, Recovery Manager for Oracle failed to determine the type of the specified device. SOLUTION Make sure the device is a supported device type.
The HP 3PAR CLI command promotesv failed. SOLUTION Make sure the HP 3PAR StoreServ Storage system is functioning correctly. Contact customer support for further investigation. MESSAGE ID 1048 SYMBOLIC NAME RMO_ERROR_ARCHDEST_ERROR MESSAGE 3PAR1048: ERROR: One or more archivelog destinations have error status. REASON When trying to retrieve archive log destinations, one or more archive log destination were found with "ERROR" status.
3PAR1050: ERROR: The alternate host is the same as the backup system. REASON When running the rmora_export command, the alternate host cannot be the same as the backup server. SOLUTION Change to use a different host as the alternate host. MESSAGE ID 1054 SYMBOLIC NAME RMO_ERROR_INVALID_ARGUMENT MESSAGE 3PAR1054: ERROR: Invalid argument. REASON rmora_exec or tpdcli_exec received an invalid argument. SOLUTION Verify the configuration file contains all parameters up to date.
MESSAGE ID 1061 SYMBOLIC NAME RMO_ERROR_FS_NOTFOUND MESSAGE 3PAR1061: ERROR: Could not find file system for file . REASON The specified file or directory is a regular file or qio file, but the operation could not retrieve its file system type. SOLUTION Make sure the mnttab contains the file system for the specified file or directory. Contact customer support for further investigation.
REASON Recovery Manager requires datafiles and archive log destinations reside on different HP 3PAR volumes. SOLUTION Put datafiles and archive log destinations on separate HP 3PAR volumes. MESSAGE ID 1066 SYMBOLIC NAME RMO_ERROR_SHARED_ASMDG MESSAGE 3PAR1066: ERROR: Archive logs and datafiles are on the same ASM disk group. REASON Recovery Manager requires datafiles and archive log destinations reside on different ASM disk groups.
RMO_ERROR_MAXVC_RETENTEXP MESSAGE 3PAR1071: ERROR: '%s' exceeds maximum Virtual Copy retention or expiration value. REASON During configuration, the retention or expiration value provided exceeds the maximum system allowed value, which is in the range of 1 to 43800 hours (1825 days). SOLUTION Specify a value within system allowed range. MESSAGE ID 1072 SYMBOLIC NAME RMO_ERROR_DB_NOT_RUNNING MESSAGE 3PAR1072: ERROR: Oracle instance is not currently running.
MESSAGE ID 1080 SYMBOLIC NAME RMO_ERROR_RETRIEVE_RETENTEXP MESSAGE 3PAR1080: ERROR: Failed to retrieve the retention/expiration time for Virtual Copy . REASON Failed to retrieve the retention time and/or expiration time from the HP 3PAR StoreServ Storage system for the specified Virtual Copy. SOLUTION Make sure all parameters in the configuration file are up to date. Make sure the HP 3PAR StoreServ Storage system is functioning properly. Contact customer support for further investigation.
Trying to clone a database failed because the redo log information cannot be found in the ascii control file. SOLUTION Check the original database and manually create an ascii control file to make sure it contains correct redo log information. The Virtual Copy, which will be used for clone, may be corrupted, or there could be some strange characters which prevent the parser from parsing the ascii control file correctly.
ORACLEASM_SCANEXCLUDE="sd" This is to direct asmlib to only scan device mapper devices (dm devices), and not to scan sd format of devices. This will avoid Oracle asmlib seeing the same disk twice and which can cause unforeseen problem. SOLUTION Modify the specified file and reload the Oracle asmlib. MESSAGE ID 1101 SYMBOLIC NAME RMO_ERROR_REMOVE_ORAASMDISK MESSAGE 3PAR1101: ERROR: Could not delete oracleasm disk .
Run rmora_config or the GUI application to modify the configuration file to set VCDBA_MAXVC to a positive number, which cannot exceed 500. Also make sure the VCEXPIRATION parameter is not enabled (it should be set to 0d or 0h), otherwise the time-based policy will be in effect. MESSAGE ID 1104 Symbolic Name RMO_ERROR_MAXVC_ALLOWED MESSAGE 3PAR1104: ERROR: The number of Virtual Copies has exceeded the maximum of . REASON The maximum number of Virtual Copies specified in configuration file is reached.
SYMBOLIC NAME RMO_ERROR_IOCTL MESSAGE 3PAR1107: ERROR: Could not perform SCSI inquiry to device . REASON The system call ioctl failed for the specified device. SOLUTION Check if device is valid. Ignore the error message for non-HP 3PAR devices. Check log files for more information. Contact customer support for further investigation. MESSAGE ID 1109 SYMBOLIC NAME RMO_ERROR_NONE_RCVV_FOUND MESSAGE 3PAR1109: ERROR: There is no Remote Copy volumes found on HP 3PAR StoreServ Storage system .
If there is no other backup process for this database running, remove the lock file and try again. REASON Some Recovery Manager for Oracle commands (create, backup, or rsync) are designed to be executed sequentially. The command has to wait until the previous similar command finishes to obtain a lock for its exclusive time. SOLUTION Try the operation at a later time.
rmora_checkconfig is called at the end of creating or modifying a configuration file. It can also be executed separately. If it finds any check has an unexpected result, the error message will be displayed. SOLUTION Resolve the error, otherwise Recovery Manager for Oracle may not work properly. MESSAGE ID 1116 SYMBOLIC NAME RMO_ERROR_RETRIEVE_LDVV MESSAGE 3PAR1116: ERROR: Could not retrieve logical disks for volume . REASON The HP 3PAR CLI command showld failed.
RMO_ERROR_BACKUP_IMAGE_NOTFOUND MESSAGE 3PAR1127: ERROR: There is no Virtual Copy backup image (full). REASON rmora_restore could not find a Virtual Copy that has been backed up. SOLUTION Specify a Virtual Copy that has been backed up. MESSAGE ID 1128 SYMBOLIC NAME RMO_ERROR_RETRIEVE_CTRLFILE MESSAGE 3PAR1128: ERROR: Could not retrieve location of the control files from . REASON rmora_createdb failed to retrieve the control file location from the saved init.ora file.
Rearrange the Remote Copy groups used by the database accordingly. MESSAGE ID 1131 SYMBOLIC NAME RMO_ERROR_RCVV_NOTSYNCED MESSAGE 3PAR1131: ERROR: Remote Copy volume is not currently synced. REASON Before using the rmore_rsync command, all of the volumes within the Remote Copy groups that are used by the Oracle database should be in Synced status. SOLUTION Wait until the specified volume finishes syncing.
REASON Failed to find next available VLUN number to create a VLUN. The HP 3PAR CLI command createvlun will fail if the error is not corrected. SOLUTION Check if the LUN being used exceeds the maximum value. If necessary, delete some unused VLUNs to make the VLUN available. MESSAGE ID 1135 SYMBOLIC NAME RMO_ERROR_CONFIG_PARAM_NOTFOUND MESSAGE 3PAR1135: ERROR: Parameter value not found from the configuration file. REASON An expected parameter does not exist in the configuration file.
RMO_ERROR_INVALID_TSTMP MESSAGE 3PAR1138: ERROR: Invalid timestamp format . REASON Failed to receive a timestamp for next current Virtual Copy to be created. SOLUTION Contact customer support for further investigation. MESSAGE ID 1139 SYMBOLIC NAME RMO_ERROR_ORA_VERSION MESSAGE 3PAR1139: ERROR: Could not determine Oracle release version. REASON During rmora_restore, Recover Manager failed to retrieve the Oracle software release.
RMO_ERROR_CREATE_VC_SYMLINK MESSAGE 3PAR1142: ERROR: Could not create symbolic links for Virtual Copy . REASON When running rmora_createdb to clone the database on the backup server using the binary control file, if the original datafiles or archive log destinations are symbolic links rmora_createdb will try to create the links to point to the Virtual Copy. Hence, the operation fails.
MESSAGE ID 1145 SYMBOLIC NAME RMO_ERROR_VC_NOTMOUNTED_AT_ROOT MESSAGE 3PAR1145: ERROR: The Virtual Copy is not currently mounted at . REASON Trying to clone a database with the specified Virtual Copy using the binary control file option failed. The Virtual Copy must be mounted at the file system to be able to use the binary control file to clone. SOLUTION Use rmora_umount to unmount the Virtual Copy and use rmora_mount with the -m option to mount the Virtual Copy.
SOLUTION Make sure the previous rmora_mount was successful. Check the alert log and Recovery Manager for Oracle log for more details. MESSAGE ID 1149 SYMBOLIC NAME RMO_ERROR_RESTORE MESSAGE 3PAR1149: ERROR: Could not restore backup to host . REASON The operation rmora_restore failed to use NetBackup to restore a backup image to the specified host. SOLUTION Check the NetBackup log file and Recovery Manager for Oracle log file for more detail information.
REASON When Recovery Manager for Oracle tries to execute the command createvlun, it has to make sure there is no other identical operation going on to take the next available LUN away. This is an exclusive operation. The lock file is in /etc/3par/solutions/lock/.vlun. SOLUTION Make sure there is no other createvlun process running. If the lock file is not cleaned up by previous failed operation, manually remove it.
SOLUTION Make sure the HP 3PAR StoreServ Storage system is working properly. Retry the operation. If the same error persists, contact customer support for further investigation. MESSAGE ID 1161 SYMBOLIC NAME RMO_ERROR_QUERY_ASM_REBALANCE MESSAGE 3PAR1161: ERROR: Could not determine if ASM rebalancing is in progress.
MESSAGE ID 1164 SYMBOLIC NAME RMO_ERROR_SET_RETENTEXP MESSAGE 3PAR1164: ERROR: Could not set retention/expiration for Virtual Copy . REASON Using rmora_set to set the retention time and/or expiration time for the specified Virtual Copy failed. SOLUTION Check the screen output and log files for more information. Check the system by issuing showsys -param and the maximum domain limit by issuing showdomain -d for the maximum allowed retention time.
3PAR1168: ERROR: One or more Virtual Copy's repository exist. REASON Trying to execute rmora_rmrep to remove the backup repository for a database configuration failed as one or more Virtual Copy repositories still exist. SOLUTION Run rmora_remove to remove all of the Virtual Copies before running rmora_rmrep. Make sure the Virtual Copies are no longer being used. MESSAGE ID 1169 SYMBOLIC NAME RMO_ERROR_UNSUPPORTED_DEVFMT MESSAGE 3PAR1169: ERROR: Unsupported device format: %s.
RMO_ERROR_SET_PROTECTION_MODE MESSAGE 3PAR1173: ERROR: Could not set the database protection mode to maximum performance. REASON After using the binary control file to clone a database, trying to set the protection mode to the default maximum performance failed. SOLUTION Check the alert.log for detailed information. MESSAGE ID 1174 SYMBOLIC NAME RMO_ERROR_RETRIEVE_EQUIVALENT_FPATH MESSAGE 3PAR1174: ERROR: Could not retrieve the equivalent file path for on the backup server.
SOLUTION Check the alert log and Recovery Manager for Oracle log file for more details. Manually query the cloned the database to see if there are any problems. MESSAGE ID 1178 SYMBOLIC NAME RMO_ERROR_NBUMASTER_NOTFOUND MESSAGE 3PAR1178: ERROR: Could not retrieve NBU master server. REASON During configuration, retrieval of the NetBackup master server from the file /usr/openv/netbackup/bp.conf failed. SOLUTION Make sure NetBackup is installed and configured correctly on the backup server.
SYMBOLIC NAME RMO_ERROR_PHYSDEV_NOTFOUND MESSAGE 3PAR1182: ERROR: Could not find device '%s'. REASON Failed to retrieve the OS device used by the database while executing rmora_create or rmora_rsync. SOLUTION Check the log file from both the database server and the backup system to find out more information. Contact customer support for further investigation. MESSAGE ID 1183 SYMBOLIC NAME RMO_ERROR_CONNECT_TO_HOST MESSAGE 3PAR1183: ERROR: Could not connect (ssh) to host .
SOLUTION Check the log file for more details. Contact customer support for further investigation. MESSAGE ID 1192 SYMBOLIC NAME RMO_ERROR_DB_NOTIN_STANDBY MESSAGE 3PAR1192 ERROR: The database is not in managed recovery mode. REASON The database, Recovery Manager for Oracle runs against, is a physical standby database. However, the database is not in managed recovery mode and there is no MRP process in the database.
SOLUTION Make sure that the –d argument entered under rmora_createdb is entered and enclosed within double quotes (“), and make sure that the shell’s environment variable Internal Field Separator (IFS) is not set to a comma. MESSAGE ID 1202 SYMBOLIC NAME RMO_ERROR_UDUMP_NOTFOUND MESSAGE 3PAR1202 ERROR: Could not retrieve udump location for database . REASON Failed to retrieve the user_dump_dest value from the specified database. SOLUTION Check the alert.log file.
SYMBOLIC NAME RMO_ERROR_ARCHLOG_GAP MESSAGE 3PAR1208 ERROR: Archive log gap exists between the primary and standby database. REASON Recovery Manager for Oracle runs against a physical standby database. Trying to create an online or archive log only Virtual Copy fails because there is a gap for archive log files. SOLUTION Transfer the archive log files from the database server to the physical standby database.
MESSAGE ID 1216 SYMBOLIC NAME RMO_ERROR_SETVV MESSAGE 3PAR1216: ERROR: Could not set retention time
SOLUTION Try to upgrade HP 3PAR OS, or do not use this feature. MESSAGE ID 1220 SYMBOLIC NAME RMO_ERROR_INVALID_RETENTEXP MESSAGE 3PAR1220: ERROR: Invalid Virtual Copy retention or expiration value . REASON The retention or expiration value for a Virtual Copy should be a positive number and in the range of 1 to 43800 hours (1825 days). d/D means days. h/H means hours. A value of 0 indicates that the Virtual Copy will have no retention or expiration time.
3PAR1224: ERROR: Oracle ASMLib has not been installed. REASON In Linux, the required file /etc/sysconfig/oracleasm or /etc/sysconfig/Oracleasm-_dev_oracleasm which contains the oracleasm configurations is missing. SOLUTION Install asmlib and configure oracleasm correctly. MESSAGE ID 1225 SYMBOLIC NAME RMO_ERROR_DM_SCANORDER MESSAGE 3PAR1225: ERROR: The ORACLEASM_SCANORDER from does not include .
SOLUTION Make sure the TPDSYSNAME and TPDUSERNAME have correct values in the configuration file. Make sure the volumes were not removed, which can cause the error. Contact customer support for further investigation. MESSAGE ID 1228 SYMBOLIC NAME RMO_ERROR_VXVM_ASM_MOUNT_LOCK MESSAGE 3PAR1228: ERROR: Another database Virtual Copy is currently mounted. Only one Virtual Copy per database can be mounted at any time when ASM or VxVM is in use.
MESSAGE ID 1231 SYMBOLIC NAME RMO_ERROR_RETRIEVE_VV MESSAGE 3PAR1231: ERROR: Could not retrieve virtual volume information from the HP 3PAR StoreServ Storage system. REASON Failed to run the HP 3PAR CLI command showvv -d. SOLUTION Make sure the SSH connection from the current server to the specified HP 3PAR StoreServ Storage system is valid, all parameters in configuration files are up to date, and permissions are correct for the user to execute commands. Contact customer support for further investigation.
SOLUTION Check the log file for more information. Make sure the OS is a valid supported version and that the OS is functioning correctly. Contact customer support for further investigation. MESSAGE ID 1235 SYMBOLIC NAME RMO_ERROR_SV_NOTFOUND MESSAGE 3PAR1235: ERROR: Virtual Copy volume not found from the HP 3PAR StoreServ Storage system. REASON Could not find the specified Virtual Copy volume from the HP 3PAR StoreServ Storage system.
SYMBOLIC NAME RMO_ERROR_SHUTDOWN_ASM MESSAGE 3PAR1238: ERROR: Could not shutdown ASM instance on host . REASON Could not shutdown the ASM instance on the backup server. SOLUTION Make sure the parameter values in configuration files are up to date, and check the alert.log file for more information. MESSAGE ID 1239 SYMBOLIC NAME RMO_ERROR_RETRIEVE_ASMSID MESSAGE 3PAR1239: ERROR: Could not retrieve ASM instance SID for database .
MESSAGE ID 1242 SYMBOLIC NAME RMO_ERROR_RETRIEVE_ASMDISK MESSAGE 3PAR1242: ERROR: Could not retrieve ASM disks for database '%s'. REASON Failed to retrieve ASM disks used by the specified database from ASM instance. SOLUTION Check the alert log for more details. Make sure the parameters in configuration files are up-to-date and that the ASM instance is in healthy state. MESSAGE ID 1243 SYMBOLIC NAME RMO_ERROR_ASMDG_NOTFOUND MESSAGE 3PAR1243: ERROR: Could not find ASM disk group .
If during database cloning time, check the saved init.ora file to see if there are any unusual characters or wrong syntax. Make sure the primary database has the correct parameter file. Check the log file for more details. Contact customer support for further investigation. MESSAGE ID 1246 SYMBOLIC NAME RMO_ERROR_BACKUP_ASM_METADATA MESSAGE 3PAR1246: ERROR: Could not backup ASM metadata. REASON Failed to execute the ASM command md_backup.
Make sure the archive log destinations are in valid state and have enough space. Make sure the primary database is running normally. MESSAGE ID 1250 SYMBOLIC NAME RMO_ERROR_SET_ARCHLOG MESSAGE 3PAR1250: ERROR: Please explicitly set value for parameter log_archive_dest_n. REASON The detail can be found in bug 41996. If there is no explicit value set for this parameter, it could cause rmora_createdb tasks to fail. SOLUTION Set this parameter value explicitly.
REASON Failed to remount the specified file system. SOLUTION Make sure the OS is in valid state on the database server. Manually remount the file system. Contact customer for further investigation. MESSAGE ID 1254 SYMBOLIC NAME RMO_ERROR_CREATE_ROVC MESSAGE 3PAR1254: ERROR: Could not create read-only Virtual Copy. REASON The HP 3PAR CLI command creategroupsv failed to create a read-only Virtual Copy. SOLUTION Check the log file for more details. Make sure parameters have up to date values.
MESSAGE 3PAR1258: ERROR: Could not startup all VxVM volumes in disk group . REASON Using the command vxvol -g dgname to start up all VxVM volumes failed. SOLUTION Check the log file to get more details. Make sure VxVM is in a valid state. Contact customer support for further investigation. MESSAGE ID 1259 SYMBOLIC NAME RMO_ERROR_MOUNT_ASM MESSAGE 3PAR1259: ERROR: Could not start up the ASM instance or mount the ASM snapshot disk groups.
SYMBOLIC NAME RMO_ERROR_DROP_ASMDG MESSAGE 3PAR1262: ERROR: Could not drop one or more ASM snapshot disk groups. REASON The SQL command to drop one or more ASM snapshot disk groups on the backup server fails. SOLUTION Check the log file for more details. Contact customer support for further investigation. MESSAGE ID 1263 SYMBOLIC NAME RMO_ERROR_RETRIEVE_DMPNODE MESSAGE 3PAR1262: ERROR: Could not retrieve VxVM DMP node for disk .
MESSAGE ID 1266 SYMBOLIC NAME RMO_ERROR_BACKUP_NOT_CONFIGURE MESSAGE 3PAR1266: ERROR: Recovery Manager has not been configured for backup/restore. REASON The operation to backup or restore failed as the configuration file does not contain the backup information. SOLUTION Run rmora_config to add the backup configuration portion. MESSAGE ID 1267 SYMBOLIC NAME RMO_ERROR_NBU_INCBACKUP_UNSUPPORTED MESSAGE 3PAR1267: ERROR: Incremental backup using Symantec NetBackup is not supported.
The operation to use Oracle RMAN and a NetBackup policy with Oracle type to backup a database failed. SOLUTION Check NetBackup log files and the Recovery Manager for Oracle log file for more details. MESSAGE ID 1270 SYMBOLIC NAME RMO_ERROR_RETRIEVE_VCTSTMP MESSAGE 3PAR1270: ERROR: Could not retrieve the created Virtual Copy's timestamp. REASON This error occurs when using NetBackup to backup a Virtual Copy.
MESSAGE ID 1273 SYMBOLIC NAME RMO_ERROR_RETRIEVE_DBNAME MESSAGE 3PAR1273: ERROR: Could not retrieve the current database name. REASON During rmora_restore, Recovery Manager for Oracle failed to retrieve the name of the database to be restored. SOLUTION Make sure the database to be restored to is started in started mode to be able to query the v$instance view. MESSAGE ID 1274 SYMBOLIC NAME RMO_ERROR_VC_NOT_BACKUP MESSAGE 3PAR1274: ERROR: The Virtual Copy has no backup image.
SYMBOLIC NAME RMO_ERROR_ARCHLOG_RESTORE MESSAGE 3PAR1276: ERROR: Archive logs will be restored automatically during media recovery using Oracle RMAN. REASON Trying to restore archive log files using RMAN fails. SOLUTION There is no need to restore archive log files alone. RMAN will automatically restore necessary archive log files during media recovery. MESSAGE ID 1277 SYMBOLIC NAME RMO_ERROR_RESTORE_DIFFERENT_DB MESSAGE 3PAR1277: ERROR: Restoring to a different database is not supported.
MESSAGE 3PAR1279: ERROR: The host is neither the backup server or the original host. Use '-H' option to specify the Oracle Home on the host. REASON Trying to restore a backup image to a host that is different from the original database server and the backup server, but no Oracle Home parameter is specified in the command line results in this error. SOLUTION rmora_restore needs to know the host name and Oracle home on this alternate host to be able to continue.
Make sure TPDSYSNAME and TPDUSERNAME to access the specified HP 3PAR StoreServ Storage system are correct. Make sure the Remote Copy and Remote copy groups are set up properly. MESSAGE ID 1301 SYMBOLIC NAME RMO_ERROR_CLONEDB_UP MESSAGE 3PAR1301: ERROR: The clone database instance is currently running. REASON Trying to clone a database with the specified name failed, as a database with same instance name is already up and running.
3PAR1304: ERROR: Control file ASM disk group not found. REASON 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 of the clone locations is an ASM disk group, which means the control file will reside on one of the ASM disk groups on the backup server, and • The ASM instance on the backup server does not contain the disk group for the control file.
SOLUTION User specified a non-existing host definition for the backup server on the HP 3PAR Storage system. Use the showhost command on the HP 3PAR Storage system to find out the correct host definition and update the HP 3PAR Recovery Manager configuration with the correct value. MESSAGE ID 1311 MESSAGE 3PAR1311: ERROR: TPD Host does not match specified host . REASON The TPD Host name that the user entered does not correspond to any valid host that Recovery Manager for Oracle can discover.
Make sure the current user has read-write permission to the repository directory /etc/3par/ solutions/.ora./ on the backup server. MESSAGE ID 1315 MESSAGE 3PAR1315: ERROR: Could not import volume group . REASON The LVM vgimport command, which is used to import the snapshot volume group, has failed. SOLUTION See preceding error message to determine the cause of failure. MESSAGE ID 1316 MESSAGE 3PAR1316: ERROR: Could not activate volume group .
The LVM pvremove command, which is used to remove LVM physical volumes from a snapshot volume group, has failed. SOLUTION See the preceding error message to determine the cause of failure. MESSAGE ID 1320 MESSAGE 3PAR1320: ERROR: Could not remove LVM volume group . REASON The LVM vgremove command, which is used to remove a snapshot volume group, has failed. SOLUTION See the preceding error message to determine the cause of failure.
MESSAGE 3PAR1341: ERROR: Failed to retrieve the client name for NetBackup policy '%s'. REASON The client name of a NetBackup policy cannot be retrieved using NetBackup command bppllist. See the error message that comes before this error to determine the reason. SOLUTION Make sure the NetBackup master server specified in Recovery Manager for Oracle configuration file is reachable.
Index A I archive log backup configuring NBU policy, 47 installation on Linux systems, 28 installing, 26 installing on primary server, 31 installing Recovery Manager on Solaris systems, 30 B backup server to HP 3PAR StoreServ Storage system SSH connection, 43 backup to database server verification, 41 backup to NBU verification for SSH, 41 L location of command line utilities, 66 C M client side backup, 20 clone utility, 15 cloned database removal utility, 15 cloning a database, 109 command line uti
requirements standby databases, 9 restrictions with SSH, 39 RMAN recovery catalog creation, 54 rmora_create, 76 rmora_createdb, 80 rmora_display, 82 rmora_mount, 86 rmora_remove, 88 rmora_removedb, 89 rmora_restore, 90 rmora_rmrep, 93 rmora_rollback, 94 rmora_set, 99 rmora_unmount, 101 rolling back Virtual Copies, 94 S server side backup, 20 setting retention time for a Virtual Copy, 99 setting up national language support, 46 setting up SSH from backup to HP 3PAR StoreServ Storage system, 42 from backup t
