3PAR Recovery Manager 3.0.2 for Oracle on Solaris and Red Hat Linux User’s Guide 3PAR Inc. 4209 Technology Drive Fremont, CA 94538 U.S.A. Part No.
Revision Notice This is the first release of this manual. A complete revision history is provided at the end of this manual. Changes The material in this document is for information only and is subject to change without notice. While reasonable efforts have been made in the preparation of this document to assure its accuracy, 3PAR Inc. assumes no liability resulting from errors or omissions in this document or from the use of the information contained herein.
Recovery Manager for Oracle User’s Guide Table of Contents 1 Introduction 1.1 Audience 1.2 1.2 Related Documents 1.2 1.3 Organization 1.3 1.4 Typographical Conventions 1.4 1.5 Advisories 1.5 2 Overview of Recovery Manager Operations 2.1 Virtual Copies 2.2 2.2 About the Recovery Manager Repository 2.3 2.3 Interacting with Oracle 2.4 2.4 Interacting with Veritas Volume Manager 2.5 2.5 Interacting with Veritas NetBackup and Oracle RMAN 2.6 2.6 Recovery Manager Utilities 2.7 2.6.
Recovery Manager for Oracle User’s Guide 2.6.6 The Virtual Copy Export Utility 2.12 2.6.7 The Database Cloning Utility 2.12 2.6.8 The Cloned Database Removal Utility 2.14 2.6.9 The Virtual Copy Removal Utility 2.14 2.7 The Virtual Copy Repository 2.7.1 The Virtual Copy Repository Removal Utility 2.14 2.14 2.8 Virtual Copy Policy 2.15 2.9 Database Rollback from a Virtual Copy 2.15 2.9.1 The Database Rollback Utility 2.10 Recovery Manager and Third-Party Backup Tools 2.10.1 2.10.2 2.
Recovery Manager for Oracle User’s Guide 4.2.1 Setting Up an RSH Connection from the Backup Host to the Primary Host 4.4 4.2.2 Verifying the RSH Connection from the Backup Host to the Primary Host 4.4 4.2.3 Setting Up RSH Connections from the Backup Host to the NetBackup Master Server 4.5 4.2.4 Verifying RSH Connections from the Backup Host to the NetBackup Master Server 4.5 4.2.5 Setting Up a CLI Connection from the Primary Host to the InServ Storage Server 4.6 4.2.
Recovery Manager for Oracle User’s Guide 4.8.3 Creating an RMAN Recovery Catalog 4.9 Recovery Manager Configuration Files 4.9.1 Creating a Recovery Manager Configuration File without Remote Copy 4.9.1.1 4.9.1.2 4.9.2 4.24 4.27 4.27 Creating Configuration Files using the Menu-Driven Application or the Command Line Interface on the Backup Host 4.27 Creating a Recovery Manager Configuration File using the GUI on the Backup Host 4.
Recovery Manager for Oracle User’s Guide vcdba_checkconfig 6.7 vcdba_config 6.8 vcdba_create 6.12 vcdba_createdb 6.15 vcdba_display 6.18 vcdba_export 6.20 vcdba_main 6.22 vcdba_mount 6.24 vcdba_remove 6.27 vcdba_removedb 6.28 vcdba_restore 6.30 vcdba_rmrep 6.33 vcdba_rollback 6.35 vcdba_rsync 6.37 vcdba_umount 6.39 7 Using the Recovery Manager Graphical User Interface 7.1 Starting and Stopping the Recovery Manager GUI 7.1.1 Starting the GUI 7.2 7.2 7.2 Stopping the GUI 7.
Recovery Manager for Oracle User’s Guide 7.6.6 Removing a Virtual Copy 7.7 7.6.7 Backing up a Virtual Copy 7.7 7.6.8 Removing a Virtual Copy Repository 7.7 7.6.9 Restoring Datafiles 7.8 7.6.10 Refreshing Database Information 7.8 7.6.11 Exporting a Virtual Copy to an Alternate Backup Host 7.9 7.6.12 Cloning a Database 7.9 7.6.13 Removing a Cloned Database 7.7 Periodic Database Synchronization 7.10 7.10 7.7.1 Starting Periodic Synchronization 7.11 7.7.
Recovery Manager for Oracle User’s Guide IX RH Index Revision History Table of Contents ix
Recovery Manager for Oracle User’s Guide x Table of Contents
Recovery Manager for Oracle User’s Guide 1 Introduction In this chapter 1.1 Audience 1.2 1.2 Related Documents 1.2 1.3 Organization 1.3 1.4 Typographical Conventions 1.4 1.5 Advisories 1.5 This user’s guide provides the information needed to install, configure, and use the 3PAR Recovery Manager 3.0.2 for Oracle on Solaris and Red Hat Linux®.
Recovery Manager for Oracle User’s Guide 1.1 Audience This is an installation and configuration guide for system administrators and database administrators who are responsible for backing up databases and who understand Sun™ Solaris™ and/or Linux, and are familiar with the Oracle10g™ and Oracle11g™ Databases. 1.
Recovery Manager for Oracle User’s Guide 1.3 Organization This guide is organized as follows: ■ This chapter provides an overview of this guide, including intended audience, related documentation, typographical conventions, and advisories. ■ Chapter 2, Overview of Recovery Manager Operations, provides an overview of 3PAR Recovery Manager and its utilities. ■ Chapter 3, Installing and Deinstalling Recovery Manager, describes how to install, verify, and deinstall Recovery Manager for Oracle.
Recovery Manager for Oracle User’s Guide 1.4 Typographical Conventions The following typographical conventions are used in this guide: Typeface Meaning Example ABCDabcd Used for dialog box elements Enter your system name in the such as titles and button Value box and click OK. labels. ABCDabcd Used for file names, paths, and screen output, and for Found < 12 > 73G disks. Enter cli at the Windows text you are to enter. command prompt.
Recovery Manager for Oracle User’s Guide 1.5 Advisories To avoid injury to people or damage to data and equipment, be sure to observe the cautions and warnings in this guide. Always be careful when handling any electrical equipment. NOTE: Notes are reminders, tips, or suggestions that supplement the procedures included in this guide. CAUTION: Cautions alert you to actions that can cause damage to equipment, software, or data.
Recovery Manager for Oracle User’s Guide 1.
Recovery Manager for Oracle User’s Guide 2 Overview of Recovery Manager Operations In this chapter 2.1 Virtual Copies 2.2 2.2 About the Recovery Manager Repository 2.3 2.3 Interacting with Oracle 2.4 2.4 Interacting with Veritas Volume Manager 2.5 2.5 Interacting with Veritas NetBackup and Oracle RMAN 2.6 2.6 Recovery Manager Utilities 2.7 2.6.1 The Database Configuration Utility 2.7 2.6.2 The Virtual Copy Creation Utility 2.7 2.6.3 The Virtual Copy Display Utility 2.9 2.6.
Recovery Manager for Oracle User’s Guide 2.7 The Virtual Copy Repository 2.14 2.7.1 The Virtual Copy Repository Removal Utility 2.14 2.8 Virtual Copy Policy 2.15 2.9 Database Rollback from a Virtual Copy 2.15 2.10 Recovery Manager and Third-Party Backup Tools 2.16 2.10.1 The Database Backup Utility 2.16 2.10.2 The Database Restoration Utility 2.20 2.11 Recovery Manager with Remote Copy 2.
Recovery Manager for Oracle User’s Guide Hereinafter, the term virtual copy is used to refer to a virtual copy of a database, rather than of a virtual volume. 2.2 About the Recovery Manager Repository Information about virtual copies, database structures, and backup images (if backed up via Oracle RMAN and/or Veritas NetBackup) are stored in the 3PAR Recovery Manager repository when a virtual copy is created, or when a backup operation is performed.
Recovery Manager for Oracle User’s Guide 2.3 Interacting with Oracle 3PAR Recovery Manager interacts with Oracle database through the SQL Plus utility to perform the following: ■ Retrieve database structure information in order to create virtual copy for the database. ■ Interact with the Oracle database (put tablespaces (or the whole database) in and out of backup mode, switch logfiles) as necessary to create a consistent virtual copy.
Recovery Manager for Oracle User’s Guide To ensure that the database is running in automatic archive log mode, use SQL Plus to ensure that 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.
Recovery Manager for Oracle User’s Guide 2.5 Interacting with Veritas NetBackup and Oracle RMAN 3PAR Recovery Manager integrates 3PAR Virtual Copy with Veritas NetBackup (NBU) and Oracle RMAN to dramatically reduce the performance impact on the database host, as well as to minimize database down time during backup.
Recovery Manager for Oracle User’s Guide 2.6 Recovery Manager Utilities Read this section for general information regarding 3PAR Recovery Manager utilities available through the Recovery Manager command line interface, menu driven application, and graphical user interface. 2.6.1 The Database Configuration Utility 3PAR Recovery Manager’s database configuration utility (vcdba_config) creates a Recovery Manager configuration file for each database instance.
Recovery Manager for Oracle User’s Guide Once created, the virtual copy can be mounted on the backup host for off-host processing purposes such as backup and database cloning. A database virtual copy consists of multiple virtual copies of underlying 3PAR virtual volumes used by Oracle datafiles, archive log destination, or both, depending on which option is specified (online, offline, datafile, or archonly).
Recovery Manager for Oracle User’s Guide ■ Resynchronizes 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. NOTE: If the virtual copy is to be backed up using Oracle RMAN, a Recovery Catalog must have been created and configured prior to running this utility.
Recovery Manager for Oracle User’s Guide 2.6.4 The Virtual Copy Mount Utility 3PAR Recovery Manager’s mount utility mounts an existing database virtual copy that was created using the create utility on the backup host using the vcdba_mount command. The mounted virtual copy can be used for off-host processing purposes such as backup or database cloning.
Recovery Manager for Oracle User’s Guide ■ For virtual copies from an ASM-managed database, based on the different ASM database releases on the backup host, the operation is different. ◆ For ASM versions 10.2.0.5 or 11.0.1.7, if an ASM instance exists and is up on the backup host, then all diskgroups from the virtual copy are mounted in this ASM instance. Otherwise, an ASM instance is started up on the backup host, and all ASM disk groups in the virtual copy are mounted.
Recovery Manager for Oracle User’s Guide 2.6.6 The Virtual Copy Export Utility 3PAR Recovery Manager’s virtual copy export utility exports an existing virtual copy to an alternate backup host. The exported virtual copy (vcdba_export command) can then be mounted, backed up or cloned at the alternate backup host. The virtual copy must have Available status in order to be exported.
Recovery Manager for Oracle User’s Guide The virtual copy used for cloning a database must be either an online or offline virtual copy (created using the vcdba_create or vcdba_sync command). The virtual copy must have been mounted using the vcdba_mount command prior to running this command. A clone database can be created using an ascii or binary controlfile which was saved in the Recovery Manager repository at the time the virtual copy was created.
Recovery Manager for Oracle User’s Guide 2.6.8 The Cloned Database Removal Utility 3PAR Recovery Manager’s cloned database removal utility (vcdba_removedb command) removes a cloned database, which was created using the vcdba_createdb command. The cloned database is shutdown with the shutdown immediate option. All files (Oracle parameter file, control files, and redo logs), which were previously created by the vcdba_createdb command, are removed. The virtual copy remains mounted. 2.6.
Recovery Manager for Oracle User’s Guide 2.8 Virtual Copy Policy 3PAR Recovery Manager provides the capability to limit the maximum number of virtual copies allowed per database instance at any time. For example, a policy can be set to only allow twelve virtual copies at any time for a database. Recovery Manager always maintains the twelve latest virtual copies by removing the oldest virtual copy before creating a new copy.
Recovery Manager for Oracle User’s Guide ■ The database instance must be CLOSED for this operation. If the database is an RAC database, all RAC instances must be CLOSED. ■ The base (datafile and/or archive log) virtual volumes must be temporarily removed from the primary (database) server. ■ The specified virtual copy must have an Available status (not mounted). Recovery Manager saves an ASCII control file and a binary control file for each created virtual copy in its repository.
Recovery Manager for Oracle User’s Guide The following restrictions apply when backing up a database using the Recovery Manager database backup utility. ■ For NBU (user-managed) backup: ◆ The NBU client must be installed on the backup host, as well as on the primary host. ◆ 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.
Recovery Manager for Oracle User’s Guide ■ Calls the bpbackup command from the NBU master server to backup files listed in the include list. For Oracle RMAN backup, Recovery Manager: ■ Starts up a clone database in mounted mode using the mounted virtual copy on the backup host, assuming ORACLE_HOME is installed and configured in the Recovery Manager repository. ■ Calls an RMAN backup script (vcdba_rman_dbbackup.sh or vcdba_rman_archbackup.sh) to backup the cloned database.
Recovery Manager for Oracle User’s Guide 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) will perform 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.
Recovery Manager for Oracle User’s Guide For an RAC database, archive log destinations of all RAC instances must be on shared storage (same cluster file systems or same ASM disk groups). 2.10.2 The Database Restoration Utility 3PAR Recovery Manager’s database restoration utility restores databases, tablespaces, datafiles, or archive logs from a virtual copy's backup image. The virtual copy must have been previously backed up using the vcdba_backup command.
Recovery Manager for Oracle User’s Guide ■ For an online virtual copy, both datafiles and archive logs are restored unless individual tablespaces or datafiles are being specified. In this case, only the corresponding datafiles are restored. ■ Only datafiles are restored for an offline or datafile virtual copy. ■ Only archive logs are restored for an archive log virtual copy. For an Oracle RMAN restoration: ■ Control files are not restored by default.
Recovery Manager for Oracle User’s Guide 2.
Recovery Manager for Oracle User’s Guide 3 Installing and Deinstalling Recovery Manager In this chapter 3.1 Referencing the Support Matrix 3.2 3.2 Preinstallation Requirements 3.2 3.3 Installing Recovery Manager on Linux Systems 3.4 3.3.1 Starting Installation 3.4 3.3.2 Verifying Installation 3.5 3.4 Removing Recovery Manager from Linux Systems 3.6 3.5 Installing Recovery Manager on Solaris Systems 3.6 3.5.1 Starting Installation 3.7 3.5.2 Verifying Installation 3.7 3.
Recovery Manager for Oracle User’s Guide 3.1 Referencing the Support Matrix For information about supported platforms, refer to the InForm OS Configuration Matrix (part number 320-200099) available from 3PAR’s Document Control System. 3.2 Preinstallation Requirements Recovery Manager must be installed on a primary host and a backup host. The primary host must be running an Oracle10g or above database. Database backups take place on the backup host that runs Recovery Manager.
Recovery Manager for Oracle User’s Guide ■ If you are using Veritas® NetBackup1, it is recommended that you use the backup host as the NetBackup master server. The Veritas NetBackup client must be installed on the primary and backup hosts. If you are using Veritas NetBackup in conjunction with Oracle RMAN, the NetBackup for Oracle client must be installed on the primary and backup hosts. Refer to Veritas NetBackup for Oracle for installation and configuration instructions.
Recovery Manager for Oracle User’s Guide 3.3 Installing Recovery Manager on Linux Systems Use the instructions in this section to install 3PAR Recovery Manager software on both the primary and backup hosts. 3.3.1 Starting Installation The following section describes the steps necessary for installing 3PAR Recovery Manager on a Linux system: CAUTION: When upgrading to a newer version of 3PAR Recovery Manager, any previously installed versions of Recovery Manager must be removed.
Recovery Manager for Oracle User’s Guide 3.3.2 Verifying Installation To verify 3PAR Recovery Manager installation on a Linux system: 1 Log in as the root user. 2 Issue the rpm command as follows: # rpm -qi VCDBAora Name : VCDBAora Relocations: (not relocatable) Version : 302 Vendor: 3PAR, Inc.
Recovery Manager for Oracle User’s Guide a Change the owner of the Recovery Manager utilities and repository as follows, where the Database Administrator user name is and the group name is : #chown #chown #chown #chown b : : : : /opt/3par/vcdbaora /etc/3par/solutions /etc/3par/solutions/log /etc/3par/solutions/lock Change the access permission of the Recovery Manager utilities as follows: #chmod 550 /opt/3par/vcdbaora 4 If the /etc/
Recovery Manager for Oracle User’s Guide 3.5.1 Starting Installation To install 3PAR Recovery Manager on a Solaris system: 1 Log on as the root user. 2 Insert the 3PAR Recovery Manager CD into a CD-ROM drive. If the CD is not mounted automatically, you will need to mount it manually. # mount -F hsfs -o ro /dev/dsk/c0t6d0s2/cdrom 3 Change to the CD-ROM drive. # cd /cdrom/cdrom0 4 Use the pkgadd command as follows: # pkgadd -d .
Recovery Manager for Oracle User’s Guide 2 Use the pkginfo command as follows: # pkginfo -l VCDBAora PKGINST: VCDBAora NAME: 3PAR Recovery Manager for Oracle on Solaris CATEGORY: application ARCH: Sparc VERSION: 3.0.2 BASEDIR: /opt/3par/vcdbaora VENDOR: 3PAR DESC: 3PAR Recovery Manager for Oracle on Solaris PSTAMP: vcdbaora-3.0.2: 01-19-2007 15:07:30 INSTDATE: Jan 19 2007 15:21 HOTLINE: 1-510-413-5999 EMAIL: salesinfo@3pardata.
Recovery Manager for Oracle User’s Guide b Change the access permission of the Recovery Manager utilities as follows: #chmod 550 /opt/3par/vcdbaora 4 If the /etc/3par/solutions/.ora. directory exists, you must also change the owner and permission as follows: # chown -R : /etc/3par/solutions/ .ora. 3.6 Removing Recovery Manager from Solaris Systems To remove 3PAR Recovery Manager from a Solaris system: 1 Log in as the root user.
Recovery Manager for Oracle User’s Guide 3.
Recovery Manager for Oracle User’s Guide 4 Configuring Recovery Manager In this chapter 4.1 Setting Up Connections on Recovery Manager 4.2 4.2 Setting up RSH/CLI Connections for Recovery Manager 4.3 4.3 Setting Up SSH Connections for Recovery Manager 4.9 4.4 Setting up National Language Host Support 4.18 4.5 Setting up Manual Pages on Both Primary and Backup Hosts 4.19 4.6 Setting up a Search Path on Both Primary and Backup Hosts 4.19 4.
Recovery Manager for Oracle User’s Guide 4.1 Setting Up Connections on Recovery Manager 3PAR Recovery Manager requires that either an RSH/CLI or SSH connection be configured for the backup host, the primary host, the Veritas NetBackup master server, and the InServ Storage Server. NOTE: RSH connection is available for Solaris systems only.
Recovery Manager for Oracle User’s Guide 4.2 Setting up RSH/CLI Connections for Recovery Manager NOTE: RSH connections are available for Solaris systems only. This section describes how to set up RSH/CLI for a root user on the primary host, backup host, Veritas NetBackup master server, and the InServ Storage Server. NOTE: If you are setting up an RSH connection, you must install the 3PAR InForm Command Line Interface (CLI) in the /opt/3par/cli directory prior to installing 3PAR Recovery Manager.
Recovery Manager for Oracle User’s Guide Primary/Local Host Backup/Remote Host RSH Root User Root User CLI Connection Recovery Manager User Primary/Local InServ Storage Server CLI Connection Recovery Manager User Secondary/Remote InServ Storage Server Figure 4-2. RSH/CLI Connection Relationship for Remote Copy Support 4.2.
Recovery Manager for Oracle User’s Guide 2 Issue the rsh command for the primary host as follows: # rsh ls / 3 Make sure the command completes successfully. 4.2.3 Setting Up RSH Connections from the Backup Host to the NetBackup Master Server If the Veritas NetBackup master server and the Recovery Manager backup host are not the same, you must set up the RSH connection to the NetBackup master server as described in the following steps. Otherwise, skip this section.
Recovery Manager for Oracle User’s Guide 4.2.5 Setting Up a CLI Connection from the Primary Host to the InServ Storage Server Set up a CLI connection from the primary host to the InServ Storage Server as follows: 1 On the primary host, set the environment variables as follows: #TPDSYSNAME= #TPDPWFILE= #export TPDSYSNAME TPDPWFILE where: ◆ is the system name of the InServ Storage Server attached to the primary host.
Recovery Manager for Oracle User’s Guide 4.2.6 Verifying the CLI Connection from the Primary Host to the InServ Storage Server From the primary host, verify the CLI connection to the InServ Storage Server as follows: 1 On the primary host, log in as the root or Oracle user (as you logged in during set up). 2 Issue any CLI command (such as showsys) and ensure that the command completes successfully. # showsys 4.2.
Recovery Manager for Oracle User’s Guide 3 On the backup host, create a storage server user password file as follows: # /opt/3par/cli/bin/setpassword -saveonly -file \ $TPDPWFILE -u where is the name of the user you created in step 2 in this section or in 4.2.2 Verifying the RSH Connection from the Backup Host to the Primary Host on page 4.4. 4.2.
Recovery Manager for Oracle User’s Guide 4.3 Setting Up SSH Connections for Recovery Manager This section provides instructions on how to configure a Secure Shell (SSH) connection for the root user on the primary host, backup host, NetBackup (NBU) master server, and the InServ Storage Server. Figure 4-3 represents the SSH connection relationship between the primary host, the backup host, and the InServ Storage Server. Figure 4-4 represents the SSH connection relationship in a Remote Copy configuration.
Recovery Manager for Oracle User’s Guide Primary/Local Host Backup/Remote Host SSH Root User Root User SSH SSH Recovery Manager User Primary/Local InServ Storage Server Recovery Manager User Secondary/Remote InServ Storage Server Figure 4-4. SSH Connection Relationship for Remote Copy Support 4.3.1 SSH Restrictions Recovery Manager has the following SSH restrictions: ■ The ssh and scp commands must be located in the /usr/bin/ directory.
Recovery Manager for Oracle User’s Guide PermitRootLogin yes NOTE: If you are using native SSH, the sshd_config file is located in /etc/ssh/sshd_config. 2 If the line reads PermitRootLogin no, change the line to read yes. 4.3.3 Generating an SSH Key Pair for the Backup Host To generate an SSH key pair for the backup host: 1 Log on to the backup host as the root user. 2 Create a key pair with no passphrase using the ssh-keygen command. If a key-pair already exists, skip this section.
Recovery Manager for Oracle User’s Guide primary host, perform the procedure described in 4.3.3 Generating an SSH Key Pair for the Backup Host on page 4.11 on the primary host. NOTE: In an RAC environment, all the nodes in the cluster must have the same SSH key pair in order to run Recovery Manager utilities against any RAC instance on any node. If you choose to use the same SSH key pair, create one InForm CLI user (see 4.3.
Recovery Manager for Oracle User’s Guide # ssh root@ The authenticity of host '' can't be established. DSS key fingerprint is xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:x:xx:xx. Are you sure you want to continue connecting (yes/no)? yes Warning: Permanently added '' (DSS) to the list of known hosts. where is the primary host’s hostname. 4.3.
Recovery Manager for Oracle User’s Guide # ssh root@ The authenticity of host '' can't be established. DSS key fingerprint is xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:x:xx:xx. Are you sure you want to continue connecting (yes/no)? yes Warning: Permanently added '' (DSS) to the list of known hosts. 4.3.
Recovery Manager for Oracle User’s Guide For details about the createuser command, refer to the InForm OS Command Line Interface Reference. 4 Copy the public key of the backup host to the InServ Storage Server. # ssh @ 's password: cli% setsshkey Please enter the SSH puplic key below. When finished, press enter twice. The key is usually long. It's better to copy it from inside and editor and paste it here. (Please make sure there are no extra blanks.
Recovery Manager for Oracle User’s Guide # ssh @ The authenticity of host '' can't be established. DSS key fingerprint is xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:x:xx:xx. Are you sure you want to continue connecting (yes/no)? yes Warning: Permanently added '' (DSS) to the list of known hosts. where: ◆ is the CLI user created in 4.3.7 Setting Up Connections from the Backup Host to the NetBackup Master Server on page 4.13.
Recovery Manager for Oracle User’s Guide In the example above: ◆ is the user name of the InServ Storage Server’s administrator. ◆ is the system name of the InServ Storage Server attached to the primary host. ◆ is the administrator's password. ◆ is the password (for the InForm Storage Server) for the CLI user being created. ◆ 4 is the user being created. Copy the public key of the primary host to the InServ Storage Server.
Recovery Manager for Oracle User’s Guide NOTE: If you are prompted for a password, the setup is incorrect and you must redo the previous setup. # ssh @ The authenticity of host '' can't be established. DSS key fingerprint is xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:x:xx:xx. Are you sure you want to continue connecting (yes/no)? yes Warning: Permanently added '' (DSS) to the list of known hosts. where: ◆ is the CLI user created in 4.3.
Recovery Manager for Oracle User’s Guide 4.5 Setting up Manual Pages on Both Primary and Backup Hosts 3PAR Recovery Manager provides manual pages in the /opt/3par/vcdbaora/man directory. X To access the manual pages, define the environment variable MANPATH as follows: # MANPATH=$MANPATH:/opt/3par/vcdbaora/man # export MANPATH # LC_ALL=en_US #export LC_ALL 4.
Recovery Manager for Oracle User’s Guide NOTE: This section assumes that you are familiar with the Oracle Database and Veritas NetBackup (NBU). For more information on creating a NetBackup policy, refer to Veritas NetBackup documentation. 4.7.
Recovery Manager for Oracle User’s Guide 4.7.2 Configuring the NetBackup Policy for Archive Log Backup Perform this step only if you want to only backup the archive logs. For Recovery Manager to perform backup and restoration correctly, you must use the following guidelines in conjunction with Veritas NetBackup documentation when configuring a NBU policy: Backup Attribute 1 Select the standard type for the policy. 2 Select the cross mount points option.
Recovery Manager for Oracle User’s Guide 4.8 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 Veritas NetBackup for Oracle installed on the NBU master server, VERTIAS NetBackup client for Oracle installed on the primary host and the backup host. Refer to Veritas NetBackup for Oracle for installation and configuration instructions.
Recovery Manager for Oracle User’s Guide 4.8.1 Configuring the NetBackup Policy for Database Backup with RMAN For Recovery Manager to perform backup and restoration correctly, you must use the following guidelines in conjunction with Veritas NetBackup documentation when configuring a NBU policy: Backup Attribute Select the Oracle type for the policy. Backup Selections 1 Enter the location of RMAN backup script (/etc/3par/solutions/ .ora./vcdba_nbu_dbbackup.sh).
Recovery Manager for Oracle User’s Guide 4.8.2 Configuring the NetBackup Policy for Archive Log Backup Perform this step only if you wish to backup only archive logs. For Recovery Manager to perform backup and restoration correctly, you must use the following guidelines in conjunction with Veritas NetBackup documentation when configuring a NBU policy: Backup Attribute Select the Oracle type for the policy.
Recovery Manager for Oracle User’s Guide 2 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 ◆ is the Oracle Instance ID of the Recovery Catalog. ◆ is the Recovery Catalog tablespace name. ◆ is the file path where the datafile is created.
Recovery Manager for Oracle User’s Guide 5 Configure TNS services for the Recovery Catalog database by adding an entry in the $ORACLE_HOME/network/admin/tnsnames.ora file on the primary host and backup host as follows: = (description = (address = (protocol = TCP) (host = ) (port = 1521)) (connect_data = (server = dedicated) (service_name = )) ) where is the host name of the host where the catalog is created.
Recovery Manager for Oracle User’s Guide 4.9 Recovery Manager Configuration Files The following section provides instructions on creating Recovery Manager configuration files. There are two types of configuration files for Recovery Manager: ■ Recovery Manager without Remote Copy support. For this type of configuration, Recovery Manager provides an integrated Veritas NetBackup and Oracle RMAN for backups and restorations. ■ Recovery Manager with Remote Copy.
Recovery Manager for Oracle User’s Guide 3 4 If you are using the menu-driven application, from the backup host: a Select option 1, Configuration Administration. b Select option 1, Create a backup Configuration. When prompted, press ENTER. ◆ Enter ORACLE_SID of the database instance [h=help,q=quit]? Enter ORACLE_SID of the database instance that you want to configure. If the database is an RAC database, enter ORACLE_SID of any RAC instance.
Recovery Manager for Oracle User’s Guide Press ENTER to accept default value or enter the ORACLE_HOME location on the backup host. ◆ Enter ORACLE_HOME of ASM instance on the primary server [h=help,q=quit]? Recovery Manager provides a default value for the ORACLE_HOME of the ASM instance on the primary host 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 primary host.
Recovery Manager for Oracle User’s Guide Enter the system name of the InServ Storage Server that is connected to both the primary and the backup hosts. The InServ Storage Server’s name can be retrieved from the output of the showsys InForm CLI command. ◆ Enter InServ hostname (from showhost output) of the backup server [h=help,q=quit]? The hostname defined in the InServ Storage Server for the backup host can be retrieved from the output of the 3PAR InForm CLI showhost command on the InServ Storage Server.
Recovery Manager for Oracle User’s Guide ◆ Enter maximum number of virtual copies allowed [h=help,q=quit]? Enter the maximum number of virtual copies that can be created for the specified database. Once the maximum number of virtual copies for the database is reached, Recovery Manager removes the oldest virtual copy before creating a new one. The default maximum number is 500 read-only virtual copies for each volume.
Recovery Manager for Oracle User’s Guide Enter the DNS host name of the Veritas Netbackup master server. ◆ Enter NetBackup policy name for database backup [h=help,q=quit]? Recovery Manager requires that an NBU backup policy must have been created for database backup. ◆ Enter NetBackup full schedule name for database policy [h=help,q=quit]? You will only be prompted with this question if you previously selected Veritas NBU as the third-party backup tool.
Recovery Manager for Oracle User’s Guide 4.9.1.2 Creating a Recovery Manager Configuration File using the GUI on the Backup Host To use the Recovery Manager GUI to create a Recovery Manager configuration file without Remote Copy support: 1 Start the Recovery Manager GUI on the backup host. a Ensure the X11 server is running on the destination host where the GUI is displayed.
Recovery Manager for Oracle User’s Guide 2 From the navigation window, right-click either the Oracle Servers node or a host node, and then select New Configuration as shown in the following figures. 4.
Recovery Manager for Oracle User’s Guide The Host and Database Properties screens appear. Recovery Manager Configuration Files 4.
Recovery Manager for Oracle User’s Guide 3 Configure the host and database by entering the requested information on the configuration screen and click Next. The Modify Recovery Manager Configuration Properties screen appears. 4 The 3PAR InServ Properties screen appears.
Recovery Manager for Oracle User’s Guide The Recovery Manager Policy screen appears. 6 Specify the maximum number of virtual copies allowed in the InServ Storage Server. You can select to retain or remove the oldest virtual copy if the maximum number of virtual copies is reached. Click Next. Recovery Manager Configuration Files 4.
Recovery Manager for Oracle User’s Guide The Vendor Backup Product Properties screen appears. 7 4.38 Select the Vendor Backup Product from the menu.
Recovery Manager for Oracle User’s Guide 8 Enter the requested information under Related Parameters. ◆ The NetBackup policies must be pre-created. ◆ One policy is used for backing up the entire database. This may or may not include an archive log destination, depending on the type of backup (online or offline), and requires one full schedule. ◆ The other policy is used only for backing up the main archive log destination. This requires both a full and differential schedule.
Recovery Manager for Oracle User’s Guide 4.9.2 Creating a Recovery Manager Configuration File Using Remote Copy Before creating the configuration files for Recovery Manager to use, you must do the following: ■ Set up physical links between the local and remote InServ systems. Refer to the 3PAR Remote Copy User’s Guide for instructions on setting up links. ■ Set up Remote Copy targets for the local and remote InServ systems.
Recovery Manager for Oracle User’s Guide ◆ Enter ORACLE_SID of the database instance [h,q]? Enter ORACLE_SID of the database instance that you want to configure. If the database is an RAC database, enter ORACLE_SID of any RAC instance. ◆ Enter hostname of the primary (database) server [h=help,q=quit]? Enter the host name of the corresponding database server where the specified database instance is running.
Recovery Manager for Oracle User’s Guide Press enter to accept the default value, or enter ORACLE_HOME of the ASM instance on the backup host. ◆ Enter Oracle parameter file of the database instance [h,q]? Oracle parameter file can be either a pfile or a spfile. Recovery Manager recommends that spfile is used, especially if the database is an RAC database. Recovery Manager provides a default value for the Oracle parameter file if it can be retrieved from the specified database itself.
Recovery Manager for Oracle User’s Guide This question is for backwards compatibility. Provide the Remote Copy group name for the archive log destinations if it is being used. Press ‘s’ to skip it if there is no such group. ◆ Enter Secondary/Remote InServ name [h=help,q=quit]? Enter the system name of the Secondary/Remote InServ Storage Server that is connected to the backup host. The InServ Storage Server name can be retrieved from the output of the InForm CLI showsys command.
Recovery Manager for Oracle User’s Guide ◆ Enter Secondary/Remote InServ's user name [h=help,q=quit]? You will only be prompted with this question if you previously selected SSH as the remote shell. Recovery Manager requires that a 3PAR InForm user must have been created on the Secondary/Remote InServ Storage Server to allow access from the backup host.
Recovery Manager for Oracle User’s Guide 2 From the navigation window, right-click either the Oracle Servers node or the host node, and then select New Configuration as shown in the following figures. The Host and Database Properties screen appears. Recovery Manager Configuration Files 4.
Recovery Manager for Oracle User’s Guide 3 Configure the host information and database related parameters by entering the requested information on the Host and Database Properties screen. 4 a Check the Remote Copy option. b Click Next. Depending on the connection type you chose in step 3 on page 4.46, provide the following information in the 3PAR InServ Properties screen that appears: 4.
Recovery Manager for Oracle User’s Guide ◆ For RSH connection (Solaris systems only), enter the following information and then click Finish. In the example above: ◆ InServ Name: name of the primary/local or secondary/remote InServ Storage Server. ◆ InServ Password File: location of the storage server client password file. ◆ Target: the name of the target InServ Storage Server.
Recovery Manager for Oracle User’s Guide ◆ Backup Host Name in InServ: the backup host hostname defined in the InServ Storage Server. Use the InForm CLI showhost command to see a list of defined hosts. ◆ For SSH connection, enter the requested information on the configuration screen and click Finish. In the example above: ◆ InServ Name: name of the primary/local or secondary/remote InServ Storage Server. ◆ InServ SSH username: InServ Storage Server username (login).
Recovery Manager for Oracle User’s Guide ◆ Archive Group: the Remote Copy group name of the virtual volumes where the database archive logs are located. In a single Remote Copy configuration, datafiles and archive log destinations virtual volumes are included in the same Remote Copy group. ◆ Backup Host Name in InServ: the backup host hostname defined in the InServ storage system. Use the InForm CLI showhost command to see a list of defined hosts. The Verification screen appears.
Recovery Manager for Oracle User’s Guide 4.
Recovery Manager for Oracle User’s Guide 5 Using Recovery Manager from the Menu-Driven Application In this chapter 5.1 Starting the Menu-Driven Application 5.2 5.2 Managing Virtual Copies 5.2 5.2.1 Displaying Virtual Copies 5.3 5.2.2 Creating a Virtual Copy 5.4 5.2.3 Removing a Virtual Copy 5.4 5.2.4 Mounting a Virtual Copy 5.5 5.2.5 Unmounting a Virtual Copy 5.5 5.2.6 Exporting a Virtual Copy 5.5 5.2.7 Removing a Virtual Copy’s Repository 5.6 5.2.8 Setting Virtual Copy Policy 5.6 5.
Recovery Manager for Oracle User’s Guide Read this chapter for instructions on using Recovery Manager for Oracle from the menu-driven application. 5.1 Starting the Menu-Driven Application NOTE: New features will no longer be added into menu-driven applications. To start the Recovery Manager menu-driven application: # /opt/3par/vcdbaora/bin/vcdba_main NOTE: Refer to 4.9.1.
Recovery Manager for Oracle User’s Guide 5.2.1 Displaying Virtual Copies To display virtual copies: 1 On the Virtual Copy Management menu screen, select option 1, Display Virtual Copy. 2 Select the virtual copy to display. Possible values for the virtual copy type are: ◆ Online - virtual copy is created while the database is up and running, the virtual copy contains datafiles and archive log files; it is a hot backup. ◆ Offline - virtual copy is created while the database is down.
Recovery Manager for Oracle User’s Guide 5.2.2 Creating a Virtual Copy NOTE: If Recovery Manager is configured to use RMAN backup, a Recovery Catalog must have been created and configured prior to creating the virtual copy. To create a virtual copy: 1 On the Virtual Copy Management menu screen, select menu option 2, Create Virtual Copy. 2 When prompted, choose to create a virtual copy for the database (d) or archive log destination only(a).
Recovery Manager for Oracle User’s Guide 5.2.4 Mounting a Virtual Copy To mount a virtual copy: 1 On the Virtual Copy Management menu screen, select option 4, Mount Virtual Copy. 2 Select the virtual copy to be mounted. ◆ Recovery Manager creates a read/write virtual copy from the read-only (original) virtual copy and then mounts the read-write virtual copy. Any changes to the read-write virtual copy will not affect the read-only virtual copy.
Recovery Manager for Oracle User’s Guide Answer y (yes). b Enter alternate backup host Provide the name of the host where the virtual copy is exported. c Enter InServ internal host name for alternate backup host? Provide the 3PAR InServ Storage Server internal host name that represents the backup host on the InServ Storage Server (the showhost command displays the list of hosts defined on the storage server). d Enter full path of 3PAR InServ password file...
Recovery Manager for Oracle User’s Guide 4 Finally, you are asked if you want to save this new policy. Enter y, n, or q. NOTE: If you do not wish to remove the oldest virtual copy while creating the new virtual copy, and the InServ Storage Server contains the maximum number of virtual copies allowed, the next virtual copy creation will fail. 5.3 Backing Up Virtual Copies NOTE: Backup is not supported on Remote Copy configuration.
Recovery Manager for Oracle User’s Guide 3PAR Recovery Manager for Oracle Backup Administration: Perfom backup operation from backup host 1. Backup Database 2. Backup Archive Log Destination ?. Help For Current Menu r. Return To The Previous Menu x. Exit From Utility Enter Selection -> ◆ Backup Database Select this option to perform database backup. You are asked to confirm for a configuration file, which you should have already created (see 4.9 Recovery Manager Configuration Files on page 4.27).
Recovery Manager for Oracle User’s Guide 5.4 Performing Restores You can automatically restore a backup of a database instance only if the backup was created using NetBackup. The backup operation actually occurs on the backup host. Restoring a backup image from the backup host to the primary host is called alternate restore. NetBackup requires that a file name of /usr/openv/netbackup/db/altnames/ exist on the NetBackup master server.
Recovery Manager for Oracle User’s Guide 5.5 Performing Periodic Remote Copy To perform periodic Remote Copy from the menu-driven application: 1 On the 3PAR Recovery Manager for Oracle main menu, select option 5, Remote Copy Administration. 2 Select menu option 1, Periodic Synchronization. 3 Select a database to begin synchronization. 4 When prompted, select o (online) or f (offline). The periodic synchronization is started.
Recovery Manager for Oracle User’s Guide 6 Using the Recovery Manager Command Line Interface In this chapter vcdba_backup 6.3 vcdba_checkconfig 6.7 vcdba_config 6.8 vcdba_create 6.12 vcdba_createdb 6.15 vcdba_display 6.18 vcdba_export 6.20 vcdba_main 6.22 vcdba_mount 6.24 vcdba_remove 6.27 vcdba_removedb 6.28 vcdba_rmrep 6.33 vcdba_restore 6.30 vcdba_rollback 6.35 Using the Recovery Manager Command Line Interface 6.
Recovery Manager for Oracle User’s Guide vcdba_rsync 6.37 vcdba_umount 6.39 This chapter describes the Recovery Manager command line utilities. NOTE: The command line utilities are located in /opt/3par/vcdbaora/bin. Listed below are commands that can be run from the command line. 6.
Recovery Manager for Oracle User’s Guide COMMAND vcdba_backup SYNTAX vcdba_backup -s -p [-t ] [-o full|incr|cinc] [-v] or vcdba_backup -s -p [-o online|offline|datafile|archonly [,full|incr|cinc] [-v] DESCRIPTION Recovery Manager integrates 3PAR Virtual Copy feature with Veritas NetBackup(NBU) and Oracle RMAN to perform off-host backup.
Recovery Manager for Oracle User’s Guide For NBU (user-managed) backup: ■ The Veritas NetBackup client must be installed on the backup host and primary host. ■ 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 backup.
Recovery Manager for Oracle User’s Guide ■ For NBU (user-managed) backups, 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 /usr/ openv/netbackup/include_list. on the NBU client (the backup host). You must run this command as a super user from the backup host.
Recovery Manager for Oracle User’s Guide ■ -o datafile - Creates an virtual copy for all datafiles (not including the archive log destinations) of a database while it is OPEN (online) prior to backup. This option is ignored if a virtual copy is specified. The online, offline, datafile, and archonly options are mutually exclusive. A virtual copy created with the -o datafile option is only useful when archive logfiles generated during the creation of the virtual copy are also available.
Recovery Manager for Oracle User’s Guide COMMAND vcdba_checkconfig SYNOPSIS vcdba_checkconfig [-s -p ] [-o all|skipdatabase|databaseonly] [-v] DESCRIPTION The vcdba_checkconfig command validates a Recovery Manager 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.
Recovery Manager for Oracle User’s Guide COMMAND vcdba_config SYNOPSIS vcdba_config [-s -p ] DESCRIPTION The vcdba_config command creates or modifies the 3PAR Recovery Manager 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 3PAR Recovery Manager. The configuration file will be created at /etc/3par/solutions/ .ora./config.
Recovery Manager for Oracle User’s Guide ■ PRIMARYHOST - The hostname of the primary (database) server where the Oracle database instance is running. The value of the primary host name must match the output of the hostname command. ■ TPDHOST - The backup hostname defined in the InServ Storage Server. The hostname can be obtained from the output of the showhost InForm CLI command, and may not be the UNIX hostname of the backup host.
Recovery Manager for Oracle User’s Guide ■ LARCHGROUP - The name of the Remote Copy group, which contains Oracle archive log volumes, on the primary (local) InServ Storage Server. In a Remote Copy configuration, Oracle datafile volumes and archive log volumes are in the same Remote Copy group. Therefore, this parameter can be left empty. ■ LTARGET - The target group name on the primary (local) InServ Storage Server. Use the InForm CLI showrcopy target command to get the target name.
Recovery Manager for Oracle User’s Guide Administrator user must exist on the backup host. In addition, permission on the 3PAR Recovery Manager Installation and Repository directories must be changed appropriately. OPTIONS The following options are supported: ■ -s - The instance SID of the primary database. For an RAC database, any instance SID can be specified. ■ -p - The corresponding hostname of the primary host where the specified Oracle database instance is running.
Recovery Manager for Oracle User’s Guide COMMAND vcdba_create SYNOPSIS vcdba_create -s -p [-o online|offline|datafile|archonly] [-v] DESCRIPTION Creates a virtual copy of a database instance. The vcdba_create command can be used to create an online or offline virtual copy of an Oracle database, a datafile only virtual copy, or an archive log virtual copy.
Recovery Manager for Oracle User’s Guide ■ If archive log mode is enabled, the data files and archive logs must reside on separate 3PAR virtual volumes. ■ The online redo logs and control files should not reside on the same 3PAR virtual volumes used by the data files and archive logs to avoid being restored when using Recovery Manager Rollback feature. However, the online redo logs and control files can share the same 3PAR virtual volumes.
Recovery Manager for Oracle User’s Guide be put into backup mode before virtual copies of the data file virtual volumes are created. All tablespaces (or database) will then be taken out of backup mode. A log switching will be performed before virtual copies of archive log virtual volumes are created. If the online, offline, datafile, or archonly options are not specified, an online virtual copy will be created by default. ■ -o hotbkup - This option is the same as the -o online option and is deprecated.
Recovery Manager for Oracle User’s Guide COMMAND vcdba_createdb SYNOPSIS vcdba_createdb -s -p -t [-n ] [-h ] [-o ascii|binary|for_backup[,recovery|norecovery]] [-d ] [-v] DESCRIPTION Creates a new database instance from a virtual copy. The vcdba_createdb command creates a fully functional single-instance database or starts up a clone database in MOUNTED mode for RMAN backup purposes.
Recovery Manager for Oracle User’s Guide When creating a clone database for backup (RMAN) purposes, the database is started in MOUNTED mode using the binary controlfile from the repository without recovering the database. This can be achieved by using -o for_backup or -o binary,norecovery option.
Recovery Manager for Oracle User’s Guide ■ -o ascii - Use an ascii controlfile which was saved in the Recovery Manager repository to create a clone database. ■ -o binary - Use a binary controlfile which was saved in the Recovery Manager repository to create a clone database. ■ -o for_backup - Use an binary controlfile which was saved in the Recovery Manager repository to create a clone database. The clone database is started in MOUNTED mode without recovery for backup (RMAN) purpose.
Recovery Manager for Oracle User’s Guide COMMAND vcdba_display SYNOPSIS vcdba_display -s -p [-t ] DESCRIPTION Displays virtual copies. The vcdba_display command displays database virtual copies, along with other information including creation time, type, status and backup status. A virtual copy's type can be either Online, Offline, Datafile, or Archlog.
Recovery Manager for Oracle User’s Guide ■ -s - The instance SID of the primary database. For an RAC database, any instance SID can be specified. ■ -p - The corresponding host name of the primary host where the specified Oracle database instance is running. The value of the primary host 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.
Recovery Manager for Oracle User’s Guide COMMAND vcdba_export SYNOPSIS vcdba_export -s -p -r alt_host -t [-l ] -e alt_tpdpwfile|alt_tpdusername [-v] DESCRIPTION The vcdba_export command exports a virtual copy's repository from the current backup host to an alternate backup host. The exported virtual copy can then be mounted or cloned at the alternate backup host.
Recovery Manager for Oracle User’s Guide OPTIONS The following options are supported: ■ -s - The instance ID of the primary database. For an RAC database, any instance SID can be specified. ■ -p - The corresponding host name of the primary host where the specified Oracle database instance is running. The value of the primary host 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.
Recovery Manager for Oracle User’s Guide COMMAND vcdba_main SYNOPSIS vcdba_main DESCRIPTION The vcdba_main command provides a menu-driven interface to perform 3PAR Virtual Copy administration for off-host backup and off-host processing. Each menu contains the necessary steps to guide you through the process to perform the corresponding task. Each step may require user's interaction. ■ Each menu page contains a standard menu selection.
Recovery Manager for Oracle User’s Guide - Mount Virtual Copy - Unmount Virtual Copy - Export Virtual Copy - Remove Virtual Copy Repository Each virtual copy created by Recovery Manager will keep information in the repository to allow restore from tape or disk successfully even the associate virtual copy has been removed. Once the virtual copy is no longer needed, use this selection to free up repository space. - Virtual Copy Policy Allow the maximum number of virtual copy setting per database instance.
Recovery Manager for Oracle User’s Guide COMMAND vcdba_mount SYNOPSIS vcdba_mount -s -p -t [-m t] [-r] [-v] DESCRIPTION Mounts a virtual copy. The vcdba_mount command mounts an existing virtual copy created by the vcdba_create command on the backup host. The mounted virtual copy can be used for off-host processing purposes such as backup or database cloning.
Recovery Manager for Oracle User’s Guide Mounting a database virtual copy involves the following actions: ■ Creates a read-write virtual copy the original read-only virtual copy. ■ Imports the read-write virtual copy to the backup host. ■ Imports snapshot VERTIAS VxVM disk groups and starts up all corresponding snapshot VxVM volumes if the database files reside on VxVM volumes.
Recovery Manager for Oracle User’s Guide ■ -m - The destination location where the virtual copy is mounted. The current user must have permission to write to this location. By default, the virtual copy will be mounted at /etc/3par/solutions/.ora./ . If ASM is used on the backup host, this option will be ingnored. ■ -r - Re-mounts a virtual copy that has previously been mounted, but has been un-mounted due to system reboot.
Recovery Manager for Oracle User’s Guide COMMAND vcdba_remove SYNOPSIS vcdba_remove -s -p -t [-v] DESCRIPTION Removes a virtual copy. The vcdba_remove command removes a virtual copy created by the vcdba_create command. The virtual copy must have Available status in order to be removed. The status of the virtual copy can be retrieved using the vcdba_display command.
Recovery Manager for Oracle User’s Guide COMMAND vcdba_removedb SYNOPSIS vcdba_removedb -s -p -t [-n ] [-h ] [-f] [-v] DESCRIPTION The vcdba_removedb command removes a clone database that was created using the vcdba_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 vcdba_createdb command are removed.
Recovery Manager for Oracle User’s Guide ■ -h - The Oracle home directory of the cloned database on the backup host. If specified, this value is used instead of the value of the ORACLE_HOME_BACKUP parameter in the configuration file. ■ -f - Forces the removal of the clone database. ■ -v - Runs the command in verbose mode to display useful messages. Command 6.
Recovery Manager for Oracle User’s Guide COMMAND vcdba_restore SYNOPSIS vcdba_restore -s -p [-t ] [-T |-D ] [-h hostname] [-m alt_mountpoint] [-c] [-v] DESCRIPTION Restores database files from a virtual copy backup image. The vcdba_restore command restores databases, tablespaces, data files, and/or archive logs from a virtual copy backup image. The virtual copy must have a status of Y in order to be restored.
Recovery Manager for Oracle User’s Guide ■ If the database is an ASM managed database, all ASM disk groups must be mounted prior to running this command. ■ For NBU (user-managed) restore, a file named /usr/openv/netbackup/db/altnames/ must be created on the NBU master server in order to perform restoration to a host (including the primary host) that differs from the backup host. is the host name of the database server to restore.
Recovery Manager for Oracle User’s Guide Only the super user or the owner of the virtual copy can restore the specified virtual copy. OPTIONS The following options are supported: ■ -s - The instance SID of the primary database. For an RAC database, any instance SID can be specified. ■ -p - The corresponding host name of the primary host where the specified Oracle database instance is running. The value of the primary host name must match the output of the hostname command.
Recovery Manager for Oracle User’s Guide COMMAND vcdba_rmrep SYNOPSIS vcdba_rmrep -s -p [-t ] [-f] [-v] DESCRIPTION Removes a virtual copy repository. The vcdba_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 virtual copy's status must be Removed and its backup status must be N.
Recovery Manager for Oracle User’s Guide ■ -f - Forces the removal of the virtual copy repository even if the virtual copy has been previously backed up. ■ 6.34 Command -v - Runs the command in verbose mode to display a useful messages.
Recovery Manager for Oracle User’s Guide COMMAND vcdba_rollback SYNOPSIS vcdba_rollback -s -p -t [-o data|arch] [-v] [-w] [-f] DESCRIPTION Rolls back database volumes from an online virtual copy. The vcdba_rollback command promotes a virtual copy’s volumes back to their base virtual volumes. The base virtual volumes used by the database are rolled back to the virtual copy’s volumes.
Recovery Manager for Oracle User’s Guide Recovery Manager saves an ACII 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. You must run this command as a super user from the backup host. To allow the Oracle Database Administrator (Oracle Owner) to run this command, an identical Oracle Database Administrator user must exist on the backup host.
Recovery Manager for Oracle User’s Guide COMMAND vcdba_rsync SYNOPSIS vcdba_rsync -s -p [-o online|offline|checkonly] [-v] DESCRIPTION The vcdba_rsync command performs a periodic synchronization for database virtual volumes. During synchronization, changed data from the virtual volumes on the primary/local InServ Storage Server is pushed over to the corresponding remote virtual volumes on the secondary/remote InServ Storage Server.
Recovery Manager for Oracle User’s Guide ■ -o offline- Performs periodic synchronization for datafile virtual volumes while the database is CLOSED. ■ -o coldbkup - This option is the same as the -o offline and is deprecated. This option will be removed in a future release. 6.38 ■ -o checkonly - Verifies the Remote Copy configuration. ■ -v - Runs the command in verbose mode to display useful messages.
Recovery Manager for Oracle User’s Guide COMMAND vcdba_umount SYNOPSIS vcdba_umount -s -p -t [-f ] [-v] DESCRIPTION Unmounts a virtual copy. The vcdba_umount command unmounts a mounted database virtual copy. 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.
Recovery Manager for Oracle User’s Guide OPTIONS The following options are supported: ■ -s - The instance SID of the primary database. For an RAC database, any instance SID can be specified. ■ -p - The corresponding host name of the primary host where the specified Oracle database instance is running. The value of the primary host name must match the output of the hostname command. ■ -t - The timestamp of a virtual copy to be unmounted.
Recovery Manager for Oracle User’s Guide 7 Using the Recovery Manager Graphical User Interface In this chapter 7.1 Starting and Stopping the Recovery Manager GUI 7.1.1 Starting the GUI 7.2 7.2 7.2 Stopping the GUI 7.2 7.3 Creating Configuration Files 7.3 7.4 Modifying Configuration Files 7.3 7.5 Removing Configuration Files 7.3 7.6 Using Virtual Copies 7.4 7.7 Periodic Database Synchronization 7.10 Using the Recovery Manager Graphical User Interface 7.
Recovery Manager for Oracle User’s Guide 7.1 Starting and Stopping the Recovery Manager GUI The 3PAR Recovery Manager Graphical User Interface (GUI) is installed when the VCDBAora package is installed. 7.1.1 Starting the GUI To start the Recovery Manager GUI: 1 Ensure that the DISPLAY environment variable is set. 2 Verify that the X11 server is running on the destination host where the GUI is displayed.
Recovery Manager for Oracle User’s Guide 7.3 Creating Configuration Files 3PAR Recovery Manager relies on configuration files for most of its operations. There are two types of configuration files, Recovery Manager with Remote Copy and Recovery Manager without Remote Copy. The Recovery Manager repository is located in the /etc/3par/solutions/.ora. directory on the backup host. Refer to 4.9 Recovery Manager Configuration Files on page 4.
Recovery Manager for Oracle User’s Guide 7.6 Using Virtual Copies 7.6.1 Creating a Virtual Copy This feature supports hot (online) and cold (offline) backup of a database instance or backup of archive log destinations only. Creating a virtual copy requires the primary host Oracle SID. Perform this function through the menu, tool bar, and popup menu. To create a virtual copy, perform the following procedure: 1 Select Virtual Copy Management from the navigation view.
Recovery Manager for Oracle User’s Guide 7.6.2 Setting up Virtual Copy Policy This feature allows the control of the number of virtual copies on an InServ Storage Server. When the maximum number of virtual copies is reached, the oldest copy can either be removed or retained. To create a virtual copy policy, perform the following procedure: 1 Select Virtual Copy Management from the navigation view. 2 Select the Virtual Copy Policy menu from the Virtual Copies pull-down menu.
Recovery Manager for Oracle User’s Guide 7.6.4 Mounting a Virtual Copy After a virtual copy is created, it can be mounted on the backup host where the Recovery Manager 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 being mounted on the backup host.
Recovery Manager for Oracle User’s Guide 7.6.6 Removing a Virtual Copy After the Virtual Volume State column displays Available, the virtual copy can be deleted. CAUTION: Removing a virtual copy permanently removes the virtual copy from the system. To remove a virtual copy: 1 Right-click the virtual copy you wish to remove. 2 Click Remove Virtual Copy. 3 Click Yes when prompted for confirmation to remove the virtual copy. A successful message shows on screen after it is finished. 4 Click OK.
Recovery Manager for Oracle User’s Guide 2 Click Remove Virtual Copy Repository. 3 Click Yes when prompted for confirmation to remove the repository. The removed repository is no longer displayed on the virtual copy management screen. 7.6.9 Restoring Datafiles If Veritas NetBackup (NBU) is used to back up datafiles, NBU can be used to restore datafiles to the primary host, backup host, or any other hosts where the NBU clients for the same NBU master server are configured.
Recovery Manager for Oracle User’s Guide 7.6.11 Exporting a Virtual Copy to an Alternate Backup Host After a virtual copy is created, it can be exported to an alternate backup host. Export a virtual copy as follows: 1 Right-click the virtual copy you wish to export and click Export. The Export Virtual Copy screen appears. 2 On the Export Virtual Copy screen, provide the following information: ◆ Alternate Backup Host Name - the name of the backup host to which the virtual copy is exported.
Recovery Manager for Oracle User’s Guide 4 If an ascii control file is chosen to clone the database (this is default option), provide one or more mount points on the backup host for the control files and the redo log files (control files and redo log files are multiplexed across the mount points).
Recovery Manager for Oracle User’s Guide 7.7.1 Starting Periodic Synchronization To start periodic synchronization on a Remote Copy node: 1 Right-click a Remote Copy node on the navigation tree and click Periodic Sync Virtual Volumes. The Periodic Synchronization Virtual Volumes screen appears. NOTE: Recovery Manager does not allow more than one periodic synchronization process for the same database at the same time.
Recovery Manager for Oracle User’s Guide If Recovery Manager prevents you from performing a periodic synchronization of your Remote Copy group when no other synchronization processes are occurring, the Periodic Sync Lock can be removed. X To remove the Periodic Sync Lock, right-click the Remote Copy node you wish to synchronize and click Remove Periodic Sync Lock. 7.7.
Recovery Manager for Oracle User’s Guide 8 Using the Recovery Manager Rollback Utility In this chapter 8.1 vcdba_rollback Usage 8.2 8.2 Database Volumes Not Under Veritas VxVM Control 8.2 8.2.1 Rollback with Read-Only Virtual Copies 8.2 8.2.2 Rollback with Read-Write Virtual Copies 8.3 8.3 Database Volumes Under Veritas VxVM Control 8.4 8.3.1 Rollback with Read-Write Virtual Copies 8.4 8.3.2 Rollback with Read-Only Virtual Copies 8.
Recovery Manager for Oracle User’s Guide 8.1 vcdba_rollback Usage Refer to vcdba_rollback on page 6.35 for the syntax and available options for the vcdba_rollback command. The procedure to rollback the data volumes depends on the data type of the datafile. If the datafiles are composed from Veritas VxVM then special VxVM procedures apply. 8.2 Database Volumes Not Under Veritas VxVM Control If none of the disk volumes used by a database are under Veritas VxVM control, perform the following procedures. 8.
Recovery Manager for Oracle User’s Guide Example: createvlun Oracle_data1 101 pilot 7 On the primary host, run the fsck command on all mount points, and then mount each disk to its original mount point. If ASM is being used, mount all involved ASM disk groups. 8 On the primary host, follow Oracle documentation to perform media recovery to recover the database. 8.2.
Recovery Manager for Oracle User’s Guide 8.3 Database Volumes Under Veritas VxVM Control If any of the database volumes are under Veritas VxVM control, perform the following procedures. 8.3.1 Rollback with Read-Write Virtual Copies 1 On both the backup host and the primary host: a Shutdown both databases.
Recovery Manager for Oracle User’s Guide NOTE: If all VLUNs used by the database are removed, remember to recreate all of them after the rollback. Rollback only overrides virtual volumes used by datafiles and/or archive log destination (depending on which backup option the user performed for the specific timestamp).
Recovery Manager for Oracle User’s Guide Example: pilot:# vxdisk list DEVICE TYPE c0t0d0s2 sliced c2t0d0s2 sliced c2t0d41s2 sliced c2t0d42s2 sliced c2t0d43s2 sliced c2t0d44s2 sliced c2t0d45s2 sliced c2t0d46s2 sliced c2t0d47s2 sliced c2t0d48s2 sliced c2t0d49s2 sliced e DISK disk01 orcl92001 orcl92002 orcl92003 orcl92004 orcl92005 orcl92006 orcl92007 arch92001 arch92002 GROUP rootdg orcl920dg orcl920dg orcl920dg orcl920dg orcl920dg orcl920dg orcl920dg arch920dg arch920dg STATUS error online online online
Recovery Manager for Oracle User’s Guide c On the backup host, run the vxdisk list command to make sure all volume disks are online and belong to the correct disk groups. d On the backup host, mount all file systems previously used by the cloned database. e On the backup host, start up the database. 8.3.2 Rollback with Read-Only Virtual Copies To rollback read-only virtual copies, perform the following: 1 On the primary host, perform step 1 and step 2 on page 8.2.
Recovery Manager for Oracle User’s Guide 8.
Recovery Manager for Oracle User’s Guide 9 Using Remote Copy with Recovery Manager In this chapter 9.1 Overview 9.2 9.2 System Configuration 9.3 9.2.1 Recovery Manager’s Remote Copy Requirements 9.3 Verifying Remote Copy Settings 9.3 9.5 9.3.1 Verifying the Primary/Local Remote Copy Setting 9.5 9.3.2 Verifying the Secondary/Remote Copy Setting 9.6 9.4 Using Remote Copy 9.9 Using Remote Copy with Recovery Manager 9.
Recovery Manager for Oracle User’s Guide 9.
Recovery Manager for Oracle User’s Guide primary database from the last synchronization, I/O load on both InServ Storage Servers, and the network speed. Each time vcdba_rsync is executed, with either the online or offline option, Recovery Manager synchronizes the volumes on the secondary/remote InServ Storage Server with changes from the database on the primary/local InServ Storage Server.
Recovery Manager for Oracle User’s Guide ■ Either one or two Remote Copy group(s) must be created, which contain all virtual volumes used by datafiles and archive log destinations. The one group option requires that datafiles and archive log destinations are in the same group. The two group option rqeuires that the archive log destination(s) is in a different group from datafiles. ■ Recovery Manager only supports the mirror_config policy (default) for the involved Remote Copy target.
Recovery Manager for Oracle User’s Guide 9.3 Verifying Remote Copy Settings 9.3.1 Verifying the Primary/Local Remote Copy Setting To verify the primary/local Remote Copy setting: 1 Log in to the primary host as root user. 2 Connect to the primary/local InServ Storage Server from the primary host using either SSH or RSH: # ssh @ where: ◆ is the InServ Storage Server user.
Recovery Manager for Oracle User’s Guide where: ◆ is the Remote Copy group name of the virtual volumes where the datafiles of the database reside. NOTE: Ensure the group is in the Start state and in Periodic mode. 5 Verify the Remote Copy targets. cli% showrcopy targets where is the name of the remote target that has been created using creatercopytarget. NOTE: Ensure the target status is Ready. 6 Verify the Remote Copy links.
Recovery Manager for Oracle User’s Guide where: ◆ is the InServ Storage Server CLI user. ◆ is the system name of the secondary/remote InServ Storage Server, which is attached to the backup host. ◆ 3 You are note prompted for a password if set up correctly. Verify the Remote Copy ports. cli% showport -rcip The following is sample output from the showport -rcip command: N:S:P State HW Address IP Address Netmask Gateway MTU 0:5:1 ready 0002B3C03DF2 193.1.1.1 255.255.255.
Recovery Manager for Oracle User’s Guide where is the name of the remote target that has been created using creatercopytarget. NOTE: Ensure the target status is Ready. 6 Verify the Remote Copy links. cli% showrcopy links NOTE: Ensure the link status is Up. 9.3.2.1 Starting and Synchronizing Remote Copy Groups Before using Recovery Manager with Remote Copy, groups in both the primary/local and secondary/remote InServ Storage Servers should be started and in a synchronized state.
Recovery Manager for Oracle User’s Guide Failure to issue the syncropy command can result in the subsequently issued vcdba_rsync command failing with the following errors: Eagle IPC transport error: EA_PROCESS_DOWN of process down -- Message canceled because 3PAR1170: ERROR: Could not perform syncrcopy for specified virtual copy. Could not find request handler: EAIPC_NOPHANDLE -- No phandle is available or found 9.
Recovery Manager for Oracle User’s Guide 9.
Recovery Manager for Oracle User’s Guide Index A advisories 1.5 archive log backup configuring NBU policy 4.21 audience for this guide 1.2 automatic backup 2.18, 5.8 automatic backups performing 5.8 B backing up virtual copies 5.7, 7.7 backup server to InServ RSH connection 4.7 backup server to InServ SSH connection 4.15 backup to NBU verification for SSH 4.13 backup to primary host verification 4.12 backups, automatic, performing 5.8 backups, immediate, performing 5.7 C cautions, defined 1.
Recovery Manager for Oracle User’s Guide deinstalling Recovery Manager from Solaris systems 3.9 display utility 2.9 displaying virtual copies 5.3, 6.18 documents, related 1.2 E export utility 2.12 exporting virtual copies 5.5 G generating an SSH key pair 4.11 GUI configuration, backup host 4.33, 4.44 I immediate backup 2.17 immediate backups performing 5.7 performing using the menu-driven application 5.7 installation 3.6 on Linux systems 3.4 installation of Recovery Manager, verifying 3.7 installing 3.
Recovery Manager for Oracle User’s Guide Recovery Manager with Remote Copy 2.21 refreshing database information 7.8 refreshing virtual copy information 7.5 related documents 1.2 Remote Copy 2.21 overview 9.2 uses 9.9 removing a virtual copy repository 5.6, 7.7 removing cloned databases 6.28 removing configuration files 7.3 removing the repository 7.7 removing virtual copies 5.4, 6.27, 7.7 removing virtual copy repositories 6.33 repository for Recovery Manager, about 2.3 restores performing 5.
Recovery Manager for Oracle User’s Guide V vcdba_create 6.12 vcdba_createdb 6.15 vcdba_display 6.18 vcdba_mount 6.24 vcdba_remove 6.27 vcdba_removedb 6.28 vcdba_restore 6.30 vcdba_rmrep 6.33 vcdba_rollback 6.35 vcdba_unmount 6.39 verifying installation of Recovery Manager 3.7 verifying installation on primary host 3.7 verifying SSH connection from backup host to InServ 4.15 verifying SSH connection from backup to NBU 4.13 verifying SSH connection from backup to primary host 4.
Recovery Manager for Oracle User’s Guide Revision History .............. Release level Revision summary 320-200190 Rev A First release of this manual to support product release 3.0.2. November 2009 Revision History RH.
Recovery Manager for Oracle User’s Guide RH.
