HP 3PAR Recovery Manager 4.5.0 Software for Oracle User Guide Abstract This document provides the information needed to install, configure, and use the HP 3PAR Recovery Manager 4.5.0 Software for Oracle on Solaris, Red Hat Linux, Oracle Linux, HP UX and IBM AIX.
© Copyright 2014 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 Online Help for HP 3PAR Recovery Manager Software for Oracle.......................7 1 Overview of Recovery Manager Operations..................................................8 Virtual Copies..........................................................................................................................8 About the Recovery Manager for Oracle Repository......................................................................8 Interacting with Oracle............................................
Installation........................................................................................................................33 Verifying Installation...........................................................................................................34 Removing Recovery Manager from HP UX Systems......................................................................34 Installing Recovery Manager for Oracle on IBM AIX Systems........................................................
rmora_chown....................................................................................................................73 rmora_config.....................................................................................................................75 rmora_create.....................................................................................................................78 rmora_createdb .......................................................................................................
Rollback Using a Database Read-Only Virtual Copy.............................................................117 Rollback Using a Database Read-Write Virtual Copy............................................................119 Database Recovery after Rollback......................................................................................121 7 Using Remote Copy with Recovery Manager..............................................123 Overview................................................................
Online Help for HP 3PAR Recovery Manager Software for Oracle Welcome to the online help for HP 3PAR Recovery Manager Software for Oracle. Searching the Online Help To search the online help, click Search in the navigation pane on the left. The Search feature supports: • Case-insensitivity If you search for host, the search displays topics containing host, Host, HOST, and so on.
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.
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. file on the NBU client (the backup server). • Calls the bpbackup command from the NBU master server to backup files listed in the include list.
NOTE: The bpstart_notify and bpend_notify scripts are generated at /usr/openv/netbackup/bin during the creation of the Recovery Manager Configuration file. By default, the bpstart_notify script (for database backup policy) performs an online backup. If an offline or datafile backup is desired, edit this file to set the value of BACKUP_MODE to 'offline' or 'datafile' respectively. In addition, the database must be manually shutdown for offline backup.
be retrieved using the Recovery Manager display utility (see “The Virtual Copy Display Utility” (page 13)). For an NetBackup (user-managed) restoration, the database restoration utility can be used to restore a backup image of a Virtual Copy to the backup server, and it can also be used to restore to an alternate server on an alternate mount point. For an Oracle RMAN restoration, the backup image is always restored to the database server.
In addition to the current Recovery Manager for Oracle’s limitations and restrictions when running against an Oracle primary database, the following limitations and restrictions apply when running against an Oracle physical standby database: • Only Oracle 10g and 11g are supported. • A standby database must be a physical standby database. Logical and snapshot standby databases are not supported.
synchronous, asynchronous periodic mode, and Synchronous Long Distance Remote Copy. See the HP 3PAR Remote Copy Software User's Guide for additional information. Recovery Manager for Oracle and Peer Motion You need not uninstall and then reinstall Recovery Manager for Oracle when you migrate data with HP 3PAR Peer Motion. Preparing Recovery Manager for Oracle for Peer Motion Data Migration 1.
Running Recovery Manager for Oracle on Japanese OS CAUTION: For full compatibility with Recovery Manager for Oracle, you must use English-language naming conventions in your Recovery Manager for Oracle setup (for example: Oracle SID/instance, Hostnames of database and backup servers, RMAN catalog db name, and NBU policies). 26 • RHEL 6.
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 are using Symantec NetBackup1: ◦ HP recommends that you use the backup server as the NetBackup master server. ◦ The Symantec NetBackup client must be installed on the database and backup servers. ◦ If you are using Symantec NetBackup in conjunction with Oracle RMAN, the NetBackup for Oracle client must be installed on the database and backup servers. Refer to Symantec NetBackup for Oracle for installation and configuration instructions.
◦ Each OS disk can only have maximum one partition. ◦ For ext3/ext4 file systems, the journal devices should be within the same file systems • Virtual volume snapshots used by an Oracle database must be mapped to a Common Provisioning Group (CPG). Refer to the HP 3PAR Command Line Interface Administrator’s Manual for details about mapping to CPGs. • If you are upgrading from an earlier version of Recovery Manager for Oracle, do not use any upgrade utilities provided by the system.
Installing Recovery Manager for Oracle on Linux Systems Use the instructions in this section to install or upgrade Recovery Manager for Oracle on the database and backup servers. If you are not using the backup server as the NetBackup master server, be sure to install Recovery Manager for Oracle on the NetBackup master server. Installation The following section describes the steps necessary for installing or upgrading Recovery Manager for Oracle on a Linux system.
Allow RMOra to be run with 'oracle:oinstall' (y/n)? y Installation completed. 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.
Installing Recovery Manager for Oracle on Solaris Systems Use the instructions in this section to install or upgrade Recovery Manager for Oracle on the database and the backup servers. If you are not using the backup server as the NetBackup master server, be sure to install Recovery Manager for Oracle on the NetBackup master server. 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.
Removing Recovery Manager from Solaris Systems To remove HP 3PAR Recovery Manager from a Solaris system: 1. Log on as the root user. 2. Insert the HP 3PAR Recovery Manager CD into a CD-ROM drive. If the CD is not mounted automatically, mount it manually. # mount -F hsfs -o ro /dev/dsk/c0t6d0s2/cdrom 3. Change to the CD-ROM drive. # cd /cdrom/cdrom0/ 4. Enter ./rmora_uninstall.sh. Confirm you want to uninstall RMO when prompted. # ./rmora_uninstall.
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 30). 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.5.0 # 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.5.0. 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.5.0 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 41). # 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 41)). 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
1. 2. Create a database for housing the Recovery Catalog. Oracle suggests the following disk space requirements: • System tablespace: 100 MB • Temp tablespace: 5 MB • Rollback segment: 5 MB • Online redo log: 1 MB (each) • Recovery Catalog: 10 MB Create a tablespace for the Recovery Catalog as follows: $ export ORACLE_SID= $ export ORACLE_HOME= $ sqlplus "/as sysdba" SQL> create tablespace datafile '' size 10M; SQL> exit where: 3.
6. Configure the Oracle listener for the Recovery Catalog database by adding an entry in the $ORACLE_HOME/network/admin/listener.ora file on the host where the Recover Catalog is created as follows: SID_LIST_LISTENER = (SID_LIST = (SID_DESC = (GLOBAL_DBNAME = ) (ORACLE_HOME = ) (SID_NAME = ) ) ) 7. Log in as the Oracle owner user and register the database on the database server.
Backup Schedule 1. Create a schedule for full backup. 2. If you wish to perform client-side database backup (initiated from Recovery Manager), set the backup window to 0. 3. If you also wish to perform server-side database backup (initiated from NBU), specify the backup window to fit your needs. Backup Clients Set the backup client to the host name of the backup server, as the backup process will actually take place on the backup server.
Setting Up NetBackup Policies for Oracle RMAN Backup The following sections describe how to set up NetBackup (NBU) policies for NBU backup with RMAN. To perform NBU backup with RMAN, you must have Symantec NetBackup for Oracle (NBU Agent for Oracle) installed on the NBU master server, Symantec NetBackup client for Oracle installed on the database server and the backup server. Refer to Symantec NetBackup for Oracle for installation and configuration instructions.
Configuring the NetBackup Policy for Archive Log Backup NOTE: NBU server-side backup can be used when Recovery Manager for Oracle is configured to run as both root user and Oracle owner. NOTE: If Recovery Manager for Oracle is configured to run as an Oracle user and this is an upgrade from previous Recovery Manager for Oracle release, the rmora_config command must be run again for each database that is configured for server-side backup. This procedure is to backup archive logs only.
3. Create a user for the Recovery Catalog as follows: $ sqlplus "/as sysdba" SQL> create user identified by temporary tablespace temp default tablespace quota unlimited on ; SQL> grant connect, resource, recovery_catalog_owner to ; 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 .
Configure RMAN Recovery Catalog Recovery Manager for Oracle requires an Oracle RMAN recovery catalog database when using RMAN backup. To create RMAN Recovery catalog, see “Creating an RMAN Recovery Catalog” (page 52) 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.
1. On HP Data Protector Cell Manager, add the following parameter to the file /etc/opt/ omni/server/options/global: Enable3ParBackupToTapeForOracle=1 2. For the change to take effect, restart HP Data Protector service. To restart the service: # /opt/omni/sbin/omnisv stop # /opt/omni/sbin/omnisv start Configuring Oracle Operating System User Account (Oracle Owner Account) The Oracle operating system user is the owner of the Oracle Home.
NOTE: Recovery Manager for Oracle will not automatically shutdown the database before performing the backup. Datafile backup is not useful if backup of archive logs is not done. You must perform backup of archive logs separately. 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.
• 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 .
Recovery Manager for Oracle Configuration Files For each database to be managed by Recovery Manager for Oracle, a configuration file must be created first. There are two types of configuration files for Recovery Manager for Oracle: • Recovery Manager for Oracle without Remote Copy support. For this type of configuration, Recovery Manager for Oracle provides an integrated Symantec NetBackup, HP Data Protector, and Oracle RMAN for backups and restorations. • Recovery Manager for Oracle with Remote Copy.
• Oracle Home of ASM instance on the database server [h=help,q=quit]? Recovery Manager for Oracle detects if the specified Oracle instance is managed by ASM. If it is, Recovery Manager for Oracle prompts this question and provides a default value for the ORACLE_HOME of the ASM instance on the database server if it can be retrieved from the oratab file. Press ENTER to accept the default value or enter ORACLE_HOME of the ASM instance on the database server.
NOTE: If the database volumes do not belong to any domain, then the retention time of the read-only Virtual Copy cannot exceed the VVRetentionTimeMax value of the system. The VVRetentionTimeMax default value for the system is 14 days. If the database volumes belong to a domain, then the retention time of the read-only Virtual Copy cannot exceed the VVRetentionTimeMax value of the domain, if set. The retention time cannot be removed or reduced once it is set.
• Remove Virtual Copy after backup complete? [y=yes,n=no,q=quit]? Enter n if you do not want to remove the Virtual Copy after a backup is completed successfully. Otherwise, enter y. • Oracle RMAN Recovery Catalog connection string [user/password@catdb,h=help,q=quit]? You will be prompted with this question only if you previously selected Oracle RMAN as the third-party backup tool.
You will be prompted with this question only if you previously selected Oracle RMAN with HP Data Protector as the third-party backup tool. • 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 of type full for the policy that is used to perform archive log backup.
6. Click Finish. If Recovery Manager for Oracle successfully connects to the database, it retrieves the database tablespaces, datafiles, the archive log destination, and the virtual volumes where the database resides. After verification is completed, Recovery Manager for Oracle creates a Virtual Copy repository on the backup server (/etc/3par/solutions/.ora.) and two configuration files are generated along with one subdirectory for database files mapping information.
• 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 ORACLE_HOME location of the specified database instance.
• 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. Input value should be a positive integer and in the range of 1 hour to 43800 hours (1825 days). d/D means days. h/H means hours. A value of 0 specifies that there is no retention time set for read-only Virtual Copies. This question is only prompted for HP 3PAR Operating System Software 2.3.1 or later.
Creating a Recovery Manager for Oracle Configuration File using the GUI To use the Recovery Manager for Oracle GUI to create a configuration file with Remote Copy support, perform the following: 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.
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 160).
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.
• If the Oracle database is an RAC database, all RAC instances must share the same archive log destinations (i.e., the same cluster file system or the same ASM disk groups). • If the database files are symbolic links pointing to actual files and the links do not reside on the same file systems as the actual files, only the actual files are backed up. Otherwise, only the first links and the actual files are backed up; intermediate links will not be backed up.
NOTE: If the database volumes do not belong to any domain, then the retention time of the read-only Virtual Copy cannot exceed the VVRetentionTimeMax value of the system. The VVRetentionTimeMaxdefault value for the system is 14 days. If the database volumes belong to a domain, then the retention time of the read-only Virtual Copy cannot exceed the VVRetentionTimeMax value of the domain, if set. The retention time cannot be removed or reduced once it is set.
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.
The timestamp of a Virtual Copy. It is also the name of the Virtual Copy. The default behavior is to display all Virtual Copies. -r Displays the Virtual Copy’s retention and expiration time. This option is only available for HP 3PAR Operating System Software 2.3.1 or higher, otherwise, this option is ignored. EXAMPLES • rmora_display -s TEST920 -p pilot. # Name Create Time Type Status Backup? ============ ======================== ======= ========= ======== • 1.
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.
NOTE: Recovery Manager for Oracle must be pre-configured on the local backup server prior to executing rmora_rsync with the -l option.
-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 68). 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.
Starting Synchronization To start synchronization on a Remote Copy node: 1. Right-click a Remote Copy node on the navigation tree and click Create Virtual Copy. The Virtual Copy Creation screen appears. 2. 3. 4. 5. Depending on the setup of your database, select either Online (Hot) Backup or Offline (Cold) Backup. (Optional) Select Expiration time and enter a numeric value from 1 to 1,825 (Days) or 1 to 43,800 (Hours) in the adjacent field.
Destination Only option. After the Virtual Copy creation is completed, the database is taken out of backup mode. • 3. Archive Log Destination Only - The involved database instance must be open for this operation. The database is forced to switch logs before a Virtual Copy of archive logs is created. 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.
The event messages for Recovery Manager for Oracle appear in a web browser. For more information about event messages, see “Troubleshooting” (page 160). Viewing Online Help To view online help for Recovery Manager for Oracle, select Help→Online Help. 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.
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.
4. From the database server, deport/export the database volume groups if volume groups are in use.
9. From the database server, activate logical volumes and import/start volume groups. Example: - For Symantec VxVM volume groups: # vxdg import # vxvol -g startall Example: # vxdg import myvxvmdb_datadg # vxvol -g myvxvmdb_datadg startall - For HP-UX logical volume groups, using the tmpfile generated during vgexport. # vgimport -m pvname1, pvname2, ... # vgchange -a y Example: # vgimport -m /tmp/lvmtest_datadg.
3. From the backup server, unmount the ASM diskgroups contained in the read-write virtual copy volumes if ASM is in use. Example: SQL> alter diskgroup dgname dismount; 4.
# vxvol -g myvxvmdb_datadg startall - For HP-UX logical volume groups, using the tmpfile generated during vgexport: # vgimport -m pvname1, pvname2, ... # vgchange -a y Example: # vgimport -m /tmp/lvmtest_datadg.
Option:2 Using ascii control file Modify the backed up ascii control file, and the format is as follows: STARTUP NOMOUNT CREATE CONTROLFILE REUSE DATABASE "EXT2TEST" NORESETLOGS ARCHIVELOG MAXLOGFILES 16 MAXLOGMEMBERS 3 MAXDATAFILES 100 MAXINSTANCES 8 MAXLOGHISTORY 292 LOGFILE GROUP 1 '/EXT2TEST/redo/EXT2TEST/redo01.log' SIZE 50M BLOCKSIZE 512, GROUP 2 '/EXT2TEST/redo/EXT2TEST/redo02.log' SIZE 50M BLOCKSIZE 512, GROUP 3 '/EXT2TEST/redo/EXT2TEST/redo03.
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.
How Remote Copy Works A Remote Copy configuration typically involves two HP 3PAR StoreServ Storage systems: a local or primary system and a remote or secondary system. The synchronization between the local and remote systems can be either synchronous or asynchronous mode. In synchronous mode, Oracle database virtual volumes between the local and remote HP 3PAR StoreServ Storage systems are always in synchronization.
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 126).
Figure 6 Synchronous Long Distance Remote Copy Configuration Creating Virtual Copies To create Virtual Copies, use the rmora_rsync command or the Recovery Manager for Oracle GUI. Refer to “rmora_rsync” (page 98).
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 128 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 comp
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, 7400, and 7450 storage systems HP 3PAR StoreServ 7000 Storage Site Planning Manual HP 3PAR StoreServ 7450 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 Physic
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. 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 136 • 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.
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 .
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.
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 . REASON Failed to retrieve the database instance status.
RMO_ERROR_ENVVAR_NOTFOUND MESSAGE 3PAR1026: ERROR: Environment variable is not set. REASON To access the HP 3PAR StoreServ Storage system, the environment variables TPDSYSNAME, or TPDUSERNAME, or both must be set. SOLUTION Check the configuration file and make sure the TPDSYSNAME, or TPDUSERNAME, or both are up to date. MESSAGE ID 1028 SYMBOLIC NAME RMO_ERROR_INVALID_CONFIG_PARAM MESSAGE 3PAR1028: ERROR: Configuration parameter 'parametername' is not set or is invalid.
MESSAGE ID 1032 SYMBOLIC NAME RMO_ERROR_OSDEVS_NOTFOUND MESSAGE 3PAR1032: ERROR: Could not find OS devices for virtual volumes REASON The command rmora_mount or rmora_umount failed to find the OS device associated with the specified read-write virtual volume. SOLUTION Make sure the configuration on the backup server is supported, such as a multipath configuration, and make sure related daemons are up.
When trying to retrieve archive log destinations, one or more archive log destination were found with "ERROR" status. SOLUTION Make sure all archive log destinations have enough space and have no errors. MESSAGE ID 1049 SYMBOLIC NAME RMO_ERROR_BKUP_TYPE_NOT_SPECIFIED MESSAGE 3PAR1049: ERROR: Backup type (full, incr, or cinc) not specified. REASON When using RMAN to backup the Virtual Copy to media via NetBackup, RMAN related functions could not find the backup type parameter.
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. Contact customer support for further investigation. MESSAGE ID 1055 SYMBOLIC NAME RMO_ERROR_RMAN_SCRIPT MESSAGE 3PAR1055: ERROR: RMAN script not found. Please run rmora_config first.
Make sure the mnttab contains the file system for the specified file or directory. Contact customer support for further investigation. MESSAGE ID 1062 SYMBOLIC NAME RMO_ERROR_CONVERT_ORAASM_DISK MESSAGE 3PAR1062: ERROR: Could not convert oracleasm disks. REASON Failed to retrieve the OS device for Oracle asmlib devices, which are labeled as "ORCL:".
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. The Virtual Copy for datafiles volumes and archive log destination volumes are taken at different times in order to recover the database to a point-in-time image. SOLUTION Put datafiles and archive log destinations on separate ASM disk groups.
MESSAGE ID 1072 SYMBOLIC NAME RMO_ERROR_DB_NOT_RUNNING MESSAGE 3PAR1072: ERROR: Oracle instance is not currently running. Use -f option to force to remove the cloned database. REASON The operation trying to execute rmora_removedb to remove a cloned database failed. The clone database is not currently running. SOLUTION If the clone database is no longer used, use the -f option to force to the removal of the related files in the repository.
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. MESSAGE ID 1087 SYMBOLIC NAME RMO_ERROR_WRONG_VC_CLONE MESSAGE 3PAR1087: ERROR: Database '%s' was not started using the Virtual Copy . REASON Executing rmora_removedb failed as the file indicating the Virtual Copy is being used for cloning the database does not exist.
MESSAGE 3PAR1097: ERROR: Could not find Virtual Copy device for . REASON The command rmora_mount failed to find the OS device for the specified Virtual Copy. SOLUTION Make sure the configuration on the backup server is supported, such as a multipath configuration, and make sure related daemons are up. If the host HBA card is not QLogic, Emulex, or iSCSI (refer to the HP 3PAR configuration matrix), manually add or remove devices from the OS is needed.
REASON Failed to use the command oracleasm deletedisk to delete the specified Oracle asmlib disk. SOLUTION Most likely the disk is still busy. Check the /var/log/oracleasm logfile for more information. Make sure there are no other processes accessing this disk. Normally the +ASM instance could still hold the resource. Shutting down or starting up the +ASM instance could resolve the issue.
Either remove one or more Virtual Copies, or increase the number in the configuration file by running rmora_config or the GUI to modify the configuration. If you choose the option to remove the oldest Virtual Copy when maximum number is reached during configuration, Recovery Manager for Oracle will automatically remove the oldest Virtual Copy. MESSAGE ID 1105 SYMBOLIC NAME RMO_ERROR_DISCOVER_DEV MESSAGE 3PAR1105: ERROR: Could not discover devices used by database .
RMO_ERROR_NONE_RCVV_FOUND MESSAGE 3PAR1109: ERROR: There is no Remote Copy volumes found on HP 3PAR StoreServ Storage system . REASON Could not find any volumes used by Remote Copy from the specified HP 3PAR StoreServ Storage system. SOLUTION Check if Remote Copy is configured correctly. Make sure all parameters from the configuration file are up to date. Check if volumes used by datafiles and archive log files are within Remote Copy groups.
RMO_ERROR_UNKNOWN_BACKUP_MODE MESSAGE 3PAR1112: ERROR: Unknown backup mode . REASON The error occurs when NetBackup calls the bpstart_notify.policy_name script. The script finds out the backup mode is not recognized. The recognized mode are: online, offline, datafile, or archlog. SOLUTION Check the bpstart_notify.policy_name file (policy name can be found from configuration file; there is one for database, and an optional one for archive log only). Check the log file to see if there are any errors.
SOLUTION Check the log file for more information. Make sure TPDSYSNAME and TPDUSERNAME are set correctly from the configuration file. Make sure the HP 3PAR StoreServ Storage system is working properly. MESSAGE ID 1118 SYMBOLIC NAME RMO_ERROR_REMOVE_DMDEV MESSAGE 3PAR1118: ERROR: Could not remove device mapper device . REASON Failed to remove the specified device mapper device. SOLUTION Make sure the device is not being used by other processes.
REASON The specified Remote Copy group must be started in order to run the rmora_rsync command. SOLUTION Start the Remote Copy group. Refer to the HP 3PAR Remote Copy Software User's Guide for the command syntax and usage. MESSAGE ID 1130 SYMBOLIC NAME RMO_ERROR_2ORMORE_ARCH_RCGROUPS MESSAGE 3PAR1130: ERROR: Archive log volumes belong to more than one Remote Copy groups.
MESSAGE ID 1133 SYMBOLIC NAME RMO_ERROR_CREATE_GROUPSV MESSAGE 3PAR1133: ERROR: Could not create group of snapshot volumes. REASON Recovery Manager for Oracle calls HP 3PAR CLI command creategroupsv to create a Virtual Copy for a group of volumes failed. SOLUTION Check the log file to see more details. Check the HP 3PAR StoreServ Storage system to see if there is enough space for Virtual Copy creation. Make sure all parameters from the configuration file are up to date.
Cannot determine the HP 3PAR OS version. SOLUTION Run the showversion command against the HP 3PAR StoreServ Storage system to see what the error is. Make sure the configuration contains valid parameter values. Run rmora_checkconfig to verify the values. MESSAGE ID 1137 SYMBOLIC NAME RMO_ERROR_SNAPSHOT_DEV_NOTFOUND MESSAGE 3PAR1137: ERROR: Could not find snapshot devices for . REASON The command rmora_mount failed to retrieve the snapshot device from the OS for the specified virtual volume.
REASON The command rmora_umount failed to unmount the specified file system. SOLUTION Manually unmount the file system and rerun rmora_umount with the -f option. MESSAGE ID 1141 SYMBOLIC NAME RMO_ERROR_RCGROUP_NOTFOUND MESSAGE 3PAR1141: ERROR: Remote Copy group(s) not found. REASON Failed to retrieve Remote Copy information. SOLUTION Make sure the TPDSYSNAME and TPDUSERNAME are set correctly from the configuration file. Make sure the Remote Copy configuration is set up correctly.
REASON The volume used by the Oracle database, which belongs to either datafiles or archive log destinations, could not be found in any Remote Copy groups. SOLUTION Add the volume to the appropriate Remote Copy group. MESSAGE ID 1144 SYMBOLIC NAME RMO_ERROR_2ORMORE_DATA_RCGROUPS MESSAGE 3PAR1144: ERROR: Datafile volumes belong to more than one Remote Copy groups.
Make sure the backup type (online/offline/archlog/datafile) contains the specified file. Contact customer support for further investigation. MESSAGE ID 1147 SYMBOLIC NAME RMO_ERROR_UNSUPPORTED_INFORM_OSVER MESSAGE 3PAR1147: ERROR: Unsupported HP 3PAR OS Version. REASON Recover Manager detects that HP 3PAR OS version is earlier than 2.2.3. SOLUTION Upgrade the HP 3PAR OS to version 2.2.4 or later.
REASON In Linux, Recovery Manager for Oracle failed to bind a raw device in file /etc/sysconfig/rawdevices. SOLUTION Check the log file. Contact customer support for further investigation. MESSAGE ID 1153 SYMBOLIC NAME RMO_ERROR_UNKNOWN_VCTYPE MESSAGE 3PAR1153: ERROR: Unknown Virtual Copy's type '. REASON When using NetBackup to backup a Virtual Copy, Recovery Manager for Oracle could not decide the Virtual Copy type, which is in the file vc_info in timestamp repository.
MESSAGE ID 1158 SYMBOLIC NAME RMO_ERROR_ROLLBACK_TASK_NOTFOUND MESSAGE 3PAR1158: ERROR: Could not find rollback task with task ID . REASON During the process of rmora_rollback, Recovery Manager for Oracle checks the status of the promotesv tasks periodically. The error occurs when Recovery Manager for Oracle fails to find the specified task. SOLUTION Make sure the HP 3PAR StoreServ Storage system is working properly. Contact customer support for further investigation.
MESSAGE 3PAR1162: ERROR: ASM rebalancing operation is in progress. REASON Before Recovery Manager for Oracle creates a Virtual Copy for the datafile volumes and/or archivelog destination volumes that reside on ASM disk groups, Recovery Manager for Oracle discovers an ASM rebalance operation is in progress. SOLUTION Wait until the rebalance operation finishes, or stop the rebalance temporarily.
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 the all of the Virtual Copies before running rmora_rmrep. Make sure the Virtual Copies are no longer being used. MESSAGE ID 1167 SYMBOLIC NAME RMO_ERROR_ASMOWNER_NOTMATCH MESSAGE 3PAR1167: ERROR: Oracle ASM owner's uid/gid does not match between the primary and the backup server.
RMO_ERROR_SYNCRCOPY MESSAGE 3PAR1170: ERROR: Could not perform synchronization for RC group . REASON Synchronization for the specified Remote Copy group failed. SOLUTION Check the log file to see the error message. Make sure the Remote Copy group is configured properly and make sure the Remote Copy group contains the correct volumes. MESSAGE ID 1172 SYMBOLIC NAME RMO_ERROR_MAXVC_EXCEED MESSAGE 3PAR1172: ERROR: The maximum number of Virtual Copy must be between 1 and 500 (inclusive).
Check the mapping file in the repository to see if it contains the specified datafile, and check if the file system for this datafile is mounted. MESSAGE ID 1176 SYMBOLIC NAME RMO_ERROR_RESTORE_CLONE_CFILE MESSAGE 3PAR1176: ERROR: Could not restore control files for the clone database. REASON During the process of rmora_createdb, RMAN failed to restore the control file to the correct location. SOLUTION Check the log file for more details.
MESSAGE 3PAR1179: ERROR: Oracle user '%s' not found on the backup server. REASON Even Oracle home on the backup server is not specified, the same Oracle user as the database server should exist on the backup server. SOLUTION Create the same user if not exist. MESSAGE ID 1180 SYMBOLIC NAME RMO_ERROR_ORAOWNER_NOTMATCH MESSAGE 3PAR1180: ERROR: The owners of Oracle Home between the backup and database server do not match. REASON This error occurs when creating or checking a configuration file.
Follow the instructions in the HP 3PAR Recovery Manager for Oracle User Guide to configure the SSH connection. MESSAGE ID 1186 SYMBOLIC NAME RMO_ERROR_CONNECT_TO_RMANCAT MESSAGE 3PAR1186: ERROR: Could not verify RMAN Catalog configuration from host . REASON rmora_checkconfig failed to use the credentials provided during configuration to connect to the ORACLE RMAN catalog from the database server or the backup system. SOLUTION Verify if the credential provided during configuration is valid.
REASON During the process of rmora_createdb, Recovery Manager for Oracle failed to generate init.ora to clone the database. 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.
MESSAGE 3PAR1201: ERROR: Could not parse location entered. REASON Recovery Manager for Oracle has trouble understanding and parsing the argument supplied when user ran the rmora_createdb command. 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.
SOLUTION Check the primary database and make sure the two parameters are set correctly. You can manually correct the problem in the init.ora file saved in the timestamp directory and perform rmora_createdb again. MESSAGE ID 1208 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.
3PAR1215 ERROR: Unrecognized UUID format: %s. REASON In Linux, the output from the command dmsetup info devicename contains unrecognized UUID. SOLUTION Check the log file to find more information. Contact customer for further investigation. MESSAGE ID 1216 SYMBOLIC NAME RMO_ERROR_SETVV MESSAGE 3PAR1216: ERROR: Could not set retention time
RMO_ERROR_UNSUPPORTED_RETENTEXP MESSAGE 3PAR1219: ERROR: Current HP 3PAR OS version does not support volume retention/expiration. REASON Recovery Manager for Oracle only supports volume retention and/or expiration for HP 3PAR OS versions 2.3.1 or later. 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 .
MESSAGE ID 1224 SYMBOLIC NAME RMO_ERROR_ASMLIB_NOT_INSTALL MESSAGE 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 .
3PAR1227: ERROR: Virtual volume with WWN not found from the HP 3PAR StoreServ Storage system. REASON The process to discover virtual volumes used by Oracle database failed. The file basevv or archvv contains extra volumes’ WWN information, which cannot be found on the HP 3PAR StoreServ Storage system. 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.
REASON Failed to run the HP 3PAR CLI command showport. SOLUTION Make sure the SSH connection from the current server to the specified HP 3PAR StoreServ Storage system is valid, the parameters in configuration file are up to date, and permissions are correct for the user to execute commands. Contact customer support for further investigation. 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.
SYMBOLIC NAME RMO_ERROR_RETRIEVE_CONTROLLER MESSAGE 3PAR1234: ERROR: Could not retrieve FC controller information. REASON Failed to run the OS command cfgadm -al. 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.
instance on the backup server, all disk groups that are not used by the cloned database should be dismounted. SOLUTION Dismount all diskgroups that are currently mounted in the ASM instance on the backup server and try the operation again. MESSAGE ID 1238 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.
3PAR1241: ERROR: One or more ASM disk groups are shared between databases. REASON Recovery Manager for Oracle requires that an ASM disk group be exclusively used by one database. This is to avoid the potential rollback (promote) operations destroying data from other databases or applications. SOLUTION Do not share disk groups between different databases. MESSAGE ID 1242 SYMBOLIC NAME RMO_ERROR_RETRIEVE_ASMDISK MESSAGE 3PAR1242: ERROR: Could not retrieve ASM disks for database '%s'.
RMO_ERROR_PARSE_FILE MESSAGE 3PAR1245: ERROR: Could not parse file '%s'. REASON An error occurred either during the creation of Virtual Copy time or cloning database time. SOLUTION 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.
RMO_ERROR_RETRIEVE_ARCHDEST MESSAGE 3PAR1249: ERROR: Could not retrieve archive log destination. REASON Failed to run the SQL command to retrieve the physical location of the archive log destinations. SOLUTION 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.
MESSAGE ID 1253 SYMBOLIC NAME RMO_ERROR_REMOUNT_FS MESSAGE 3PAR1253: ERROR: Could not re-mount file system on host . 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.
Check the log file to get more details. Make sure VxVM is in a valid state. Contact customer support for further investigation. MESSAGE ID 1258 SYMBOLIC NAME RMO_ERROR_STARTUP_VXVMVOL 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.
If the host adapter type is not within the supported types (see the HP 3PAR configuration matrix), Recovery Manager for Oracle will not be able to rescan the volumes to the backup server. SOLUTION Manually scan the devices following the specific HBA driver's requirements. Then run rmora_mount -r. MESSAGE ID 1262 SYMBOLIC NAME RMO_ERROR_DROP_ASMDG MESSAGE 3PAR1262: ERROR: Could not drop one or more ASM snapshot disk groups.
MESSAGE 3PAR1265: ERROR: Could not query for the Flash Recovery Area (FRA) location. REASON The command rmora_restore failed to retrieve the value from the destination database for the parameter db_recovery_file_dest. SOLUTION Check the log file for more information. Make sure the database that will be restored is started and the v$parameter view is accessible. MESSAGE ID 1266 SYMBOLIC NAME RMO_ERROR_BACKUP_NOT_CONFIGURE MESSAGE 3PAR1266: ERROR: Recovery Manager has not been configured for backup/restore.
MESSAGE ID 1269 SYMBOLIC NAME RMO_ERROR_BACKUP_FAILURE MESSAGE 3PAR1269: ERROR: Backup process for database completed with failure. REASON 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 Trying to clone a database using the specific Virtual Copy fails as it only contains datafiles. A Virtual Copy created with the datafile type occurs when the database is open and in archive log mode. Archive log files are required to create a consistent point-in-time database image. SOLUTION Use online/offline Virtual Copies to clone a database. Manually copy over all necessary archive log files. Modify the init.ora file on the backup server.
1. 2. 3. Cloning database is only available to online or offline Virtual Copies. Restore files which requires later recovery operations cannot be a archive log only Virtual Copy, should be one of the online or offline types. There is no need to restore archive log files using RMAN as RMAN recovery will automatically restore necessary archive log files.
3PAR1278: ERROR: The database unique name is different from the Virtual Copy. The control file from the backup is not compatible with the current database. REASON Trying to execute rmora_restore -c failed with this error if the db_unique_name from the Virtual Copy and the current database is different (For example, the Virtual Copy is from the standby database), and the backup method is not RMAN, or the Oracle version is earlier than 11g.
SOLUTION Make sure TPDSYSNAME and TPDUSERNAME to access the specified HP 3PAR StoreServ Storage system are correct. Make sure the Remote Copy is set up properly. MESSAGE ID 1295 SYMBOLIC NAME RMO_ERROR_RETRIEVE_RCVV MESSAGE 3PAR1295: ERROR: Could not retrieve Remote Copy volumes from HP 3PAR StoreServ Storage system . REASON The HP 3PAR CLI command showrcopy failed to retrieve the Remote Copy volumes information.
RMO_ERROR_OPEN_DB MESSAGE 3PAR1303: ERROR: Could not open database instance . REASON The operation to clone a database failed. A cloned database using the same Virtual Copy already exists, Recovery Manager for Oracle failed to open the existing clone database. SOLUTION Check alert.log to find more details. MESSAGE ID 1304 SYMBOLIC NAME RMO_ERROR_CFILEDG_NOTFOUND MESSAGE 3PAR1304: ERROR: Control file ASM disk group not found.
On the backup server, Oracle asmlib configuration file (/etc/sysconfig/oracleasm, which links to /etc/sysconfig/oracleasm-_dev_oracleasm) has “dm” specified for ORACLEASM_SCANORDER, which means Oracle will scan the device mapper devices. However, Recovery Manager for Oracle checks and finds out that there is no multipathd daemon running, hence the error displayed. SOLUTION Start the multipathd daemon using the command /sbin/service multipathd start or /etc/init.d/multipathd start.
SOLUTION • Make sure the current user has write permission to the repository directory /etc/3par/ solutions/_ora_ on the database server. • See the preceding error message to determine the cause of the failure. MESSAGE ID 1313 SYMBOLIC NAME RMO_ERROR_CHANGE_VGID MESSAGE 3PAR1313: ERROR: Could not change ID for volume group . REASON The LVM vgchgid command, which is used to change the ID of a snapshot volume group, has failed.
MESSAGE 3PAR1316: ERROR: Could not activate volume group . REASON The LVM vgchange command, which is used to activate the snapshot volume group, has failed. SOLUTION See the preceding error message to determine the cause of failure. MESSAGE ID 1317 SYMBOLIC NAME RMO_ERROR_VG_NOTFOUND MESSAGE 3PAR1317: ERROR: Could not retrieve information for volume group . REASON The LVM vgdisplay command, which is used to retrieve the snapshot volume group information, has failed.
RMO_ERROR_REMOVE_VG 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 ID 1331 SYMBOLIC NAME RMO_ERROR_ORPHANED_VC MESSAGE 3PAR1331: ERROR: The virtual volumes of Virtual Copy '%s' no longer belong to the current database virtual volumes.
Make sure the NetBackup master server specified in Recovery Manager for Oracle configuration file is reachable. The specified NetBackup policy can be queried by using bppllist command from the NetBackup master server, and a client name is assigned to the policy appropriately. MESSAGE ID 1342 SYMBOLIC NAME RMO_ERROR_LARGER_RETENTION MESSAGE 3PAR1342: ERROR: The desired retention time '%s' is larger than the system's VVRetentionTimeMax value (%s hours) in HP 3PAR StoreServ Storage '%s'.
RMO_ERROR_SYNCMODE_NOTSAME MESSAGE 3PAR1351: ERROR: Synchronization mode modename for datafile group is different from the mode modename for archive log group. One database should have same synchronization modes. REASON Volumes used by the Oracle database belong to two Remote Copy groups, and the synchronization modes are different. SOLUTION Make the two modes same.
Index A I archive log backup configuring NBU policy, 50 installation on Linux systems, 30 installing, 27 installing on primary server, 32 installing Recovery Manager on Solaris systems, 32 B backup server to database server verification, 42 backup server to HP 3PAR StoreServ Storage system SSH connection, 44 backup server to NBU verification for SSH, 42 L location of command line utilities, 68 C M client side backup, 20 clone utility, 16 cloned database removal utility, 16 cloning a database, 112 co
requirements standby databases, 10 restrictions with SSH, 40 RMAN recovery catalog creation, 47, 52 rmora_create, 78 rmora_createdb, 82 rmora_display, 84 rmora_mount, 88 rmora_remove, 90 rmora_removedb, 91 rmora_restore, 92 rmora_rmrep, 95 rmora_rollback, 96 rmora_set, 102 rmora_unmount, 104 rolling back Virtual Copies, 96 S server side backup, 21 setting retention time for a Virtual Copy, 102 setting up national language support, 47 setting up SSH from backup server to HP 3PAR StoreServ Storage system, 43
