Home

HP 3PAR User's Manual

image

Contents

1. 4 7 Setting Up NetBackup Policies for NBU User Managed Backup 3PAR Recovery Manager supports NetBackup NBU with or without RMAN The following sections describe how to set up NBU policies for NBU backup without RMAN Recovery Manager supports full incremental or cumulative incremental archive log backup backup only archive logs When performing NBU backup without RMAN Recovery Manager supports only full database backup incremental database backup is not possible However you can combine full database backup with archive log backup to simulate incremental database backup Recovery Manager requires that you create an NBU policy for database backup If you wish to perform archive log backup you must create a separate NBU policy for it Setting up Manual Pages on Both Primary and Backup Hosts 4 19 Recovery Manager for Oracle User s Guide Veritas NetBackup NBU For more information on creating a NetBackup policy NOTE This section assumes that you are familiar with the Oracle Database and refer to Veritas NetBackup documentation 4 7 1 Configuring the NetBackup Policy for Database Backup For 3PAR 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 Select the cross mount points option 3 Deselect the Allow multiple
2. 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 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 Select remote shell command r rsh s ssh h help q quit This question is only for Solaris systems SSH is the only connection method supported by Recovery Manager for Linux systems Recovery Manager requires that either RSH Solaris only or SSH is configured to allow remote accesses between the backup host the primary host the InServ Storage Server and Veritas NetBackup server Enter r for RSH or s for SSH Enter ORACLE_HOME on the primary host h help q quit Recovery Manager provides a default value for the ORACLE_HOME of the specified database instance if it can be retrieved from the oratab file Press ENTER to accept default value or enter the ORACLE_HOME location of the specified database instance Enter ORACLE_HOME on the backup host h help s skip q quit Recovery Manager assumes that the ORACLE_HOME on the backup host is the same as the ORACLE_HOME on the primary host for the created clone database and RMAN backup If you don t intend to startup the clone database usin
3. lt ss_name gt is the system name of the InServ Storage Server attached to the backup host lt password gt is the password for the CLI user being created lt public_key gt is the SSH public key of the backup host 4 3 10 Verifying Connections from the Backup Host to the InServ Storage Server From the backup host verify the connection from the backup host to the InServ Storage Server as follows NOTE If you are prompted for a password the setup is incorrect and you must redo the previous setup Setting Up SSH Connections for Recovery Manager 4 15 Recovery Manager for Oracle User s Guide lt backup_host gt ssh lt username gt lt ss_name gt The authenticity of host lt ss_name gt can t be established DSS key fingerprint is xx xK xXK XX XX XX XX XX XK XKIXK IXKIX IXK IXxX Are you sure you want to continue connecting yes no yes Warning Permanently added lt InServ_name gt DSS to the list of known hosts where e lt user_name gt 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 e lt ss_name gt is the system name of the InServ Storage Server attached to the backup host 4 3 11 Setting Connections from the Primary Host to the InServ Storage Server Skip this step if the primary host has the same SSH key pair as the SSH key pair of the backup host see 4 3 4 Generating an SSH Key Pair for the Primary Host on
4. m s lt oracle_sid gt The instance SID of the primary database For an RAC database any instance SID can be specified p lt primary_host gt 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 lt timestamp gt The timestamp of a virtual copy It is also the name of the virtual copy The default behavior is to display all virtual copies EXAMPLES m vcdba_display s TEST920 p pilot Name Create Time Type Status Backup 1 012403154751 Fri Jan 24 15 47 51 2003 Offline Available N 2 012403154650 Fri Jan 24 15 46 50 2003 ArchLog Available N 3 012403153912 Fri Jan 24 15 39 12 2003 Online Available N 4 012303174743 Thu Jan 23 17 47 43 2003 Datafile Available N 5 012303171935 Thu Jan 23 17 19 35 2003 ArchLog Available N vcdba_display s TEST920 p pilot t 012405154751 Name Create Time Type Status Backup 1 012403153912 Fri Jan 24 15 39 12 2003 Online Available N Virtual Copy s Content demo data system01 dbf demo data tools01 dbf demo data rbs01 dbf demo data temp_df dbf demo data users01 dbf demo data users02 dbf demo arch Command 6 19 6 20 Recovery Manager for Oracle User s Guide COMMAND vcdba_export SYNOPSIS vcdba_export s lt oracle_sid gt p lt primary_host gt r alt_host t lt timestamp gt
5. 9 2 Overview 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 After the synchronization process is finished Recovery Manager creates virtual copies for volumes on the secondary remote InServ Storage Server Those virtual copies constitute a consistent point in time backup image for the primary database The primary database related files and information such as init ora the Oracle password file the binary control file compressed format the ASCII control file datafile information and tablespace information are saved in a virtual copy repository on a backup host A virtual copy repository directory is created as etc 3par solutions lt primary_host gt ora lt oracle_sid gt lt timestamp gt For example etc 3par solutions right ora 1SS920 032103170642 Virtual copies exist on the secondary remote InServ Storage Server where they can later be mounted and used to clone the primary database In addition the virtual copies can also be backed up to a tape library or other inexpensive storage devices to keep a consistent point in time image of the primary database 9 2 System Con
6. Command s lt oracle_sid gt The instance SID of the primary database For an RAC database any instance SID can be specified p lt primary_host gt 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 lt timestamp gt The timestamp of a virtual copy to be unmounted The virtual copy name can be obtained using the vcdba_display command f Forcibly unmounts a database virtual copy Without this option the vcdba_umount command does not allow a virtual copy to be unmounted if it is being used Using this option can corrupt the corresponding read write virtual copy However the read only virtual copy remains intact This option is useful in cases where the virtual copy is partially mounted due to mounting failure v Runs the command in verbose mode to display useful messages 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 2 7 1 1 Starting the GUI 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 1 Recovery Manager for Oracle User s Guide
7. EZ R The Veritas NBU master server m NBU_MASTER_SERV m DBFILE_CLASS_NAME The Veritas NBU class policy name for backing up database files m ARCH_CLASS_NAME The Veritas NBU class policy name for backing up archive logs DBFILE_SCHED_FULL The Veritas NBU schedule name for backing up database files ARCH_SCHED_FULL The Veritas NBU schedule name for backing up archive logs full ARCH_SCHED_FULL The Veritas NBU schedule name for backing up archive logs incremental backup RMAN_CONN_STR The RMAN connection string for connecting to the Oracle Recovery Catalog from both the primary host and the backup host RMAN_CHANNEL_TYPE The RMAN channel type is either SBT_TAPE or DISK RMAN_NO_CHANNEL The number of RMAN channels to be allocated during backup and restore m RMAN_BACKUP_DEST The backup destination to store RMAN backup image This option is only required if the specified RMAN channel type is DISK RMVC_AFTER_BACKUP Specifies whether the virtual copy should be removed after a successful backup 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 6 10 command Recovery Manager for Oracle User s Guide Administrator user must exist on the backup host In addition permis
8. 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 2 1 Rollback with Read Only Virtual Copies 1 On the primary host shutdown the database if it is up and running If ASM is being used unmount all involved ASM disk groups On the primary host unmount all file systems where the database volumes are mounted On the InServ Storage Server remove the VLUNs for the data volumes by issuing the removevlun lt vvname gt lt lun gt lt host gt command Example removevlun Oracle_datal 101 pilot Keep the list of the VLUNs which are removed by the command above The VLUNs are used to re export the LUNs with the same disk IDs after rollback operation is completed From the backup host execute the vcdba_rollback s lt oracle_sid gt p lt primary_host gt t lt timestamp gt v command to roll back the read only copy Example vcdba_rollback s TEST920 p pilot t 042903142921 v 6 Onthe InServ Storage Server export all the data volumes to the primary host with the same VLUNs saved in step 4 by issuing the createvlun lt vvname gt lt lun gt lt host gt CLI command vcdba_rollback Usage Recovery Manager for Oracle User s Guide Example createvlun Oracle_datal 101 pilot 7 On the pr
9. m s lt oracle_sid gt The instance SID of the primary database For an RAC database any instance SID can be specified p lt primary_host gt 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 lt timestamp gt The timestamp of a virtual copy It is also the name of the virtual copy The virtual copy name can be obtained using the vcdba_display command Command 6 25 6 26 Recovery Manager for Oracle User s Guide Command m lt mountpoint gt 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 lt primary_host gt ora lt oracle_sid gt lt timestamp gt 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 This option is also helpful where a virtual copy has previously been partially mounted but the virtual copy devices must be scanned manually if the host HBA is Egenera v Runs the command in verbose mode to display useful messages Recovery Manager for Oracle User s Guide COMMAND vcdba_remove SYNOPSIS vcdba_remove s lt oracle_sid gt p lt primary_host gt t lt timestamp gt v DESCRIPTION Rem
10. Command J Tescription j Started Time Status opt Spar vcdbaora bin Periodic Synchronization Wed Aug 27 12 27 48 PIT 2003 started E Connand Log TAPER EEE 7 7 2 Verifying the Periodic Synchronization Process When starting periodic synchronization on a Remote Copy node you may wish to verify that the synchronization process is occurring To verify the periodic synchronization on a Remote Copy node right click the Remote Copy node where synchronization has started and click Periodic Sync Status A window appears displaying the status of the synchronization process 7 7 3 Removing the Recovery Manager Periodic Sync Lock Recovery Manager does not permit more than one periodic synchronization process for the same database at a time Recovery Manager uses the Periodic Sync Lock to prevent simultaneous synchronization processes from occurring on a single database Periodic Database Synchronization 7 11 7 12 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 gt To remove the Periodic Sync Lock right click the Remote Copy node you wish to synchronize and click Remove Periodic Sync Lock 7 7 4 Refreshing Remote Copy Information After performing periodic synchronization on a Remote Copy node you need to refresh the Recov
11. following line 4 10 Setting Up SSH Connections for Recovery Manager 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 lt backup_host ssh keygen b 1024 t rsa Generating public private rsa key pair Enter file in which to save the key ssh id_rsa Enter passphrase empty for no passphrase Enter same passphrase again Your identification has been saved in ssh id_rsa Your public key has been saved in ssh id_rsa pub The key fingerprint is XX XXIXX XXIXXIXXIXXIXXIXXIXXIXXIXXIXX XX XX XX root lt backup_host gt NOTE You can create the SSH key as either dsa or rsa The recommended key length is 1024 the total of the public and private key lengths The ssh keygen utility generates two files id_rsa and id_rsa pub or id_dsa and id_dsa pub The id_rsa or id_dsa file contains the private key and the id_rsa pub or id_dsa pub file contains the public key 4 3 4 Generating an SSH Key Pair for the Primary Host You can either use the same SSH key pai
12. h lt hostname gt The host name to restore to If this option is omitted the virtual copy s backup image is restored to the primary host by default m lt mountpoint gt The mount point to restore to If this option is omitted the virtual copy s backup image is restored to its original location by default c Indicates that the control files are restored If this option is omitted the control files are not restored by default Restoring controlfiles along with datafiles and or tablespaces is not supported v Runs the command in verbose mode to display useful messages Recovery Manager for Oracle User s Guide COMMAND vcdba_rmrep SYNOPSIS vcedba_rmrep s lt oracle_sid gt p lt primary_host gt t lt timestamp gt DESCRIPTION Removes a virtual copy repository The vcdba_rmrep command removes a virtual copy repository specified by the lt timestamp gt parameter If the lt timestamp gt 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 If the virtual copy s status is Y the f option can be used to force the removal of the repository The virtual copy s status and backup status can be obtained using the vcdba_display command If removing a database repository all of the existing virtual copies and their repositories must be removed first You must run this command as a su
13. the InForm OS Command Line Interface CLI must be installed to the opt 3par cli directory prior to installing Recovery Manager If a secure shell SSH connection is to be used see Chapter 4 Configuring Recovery Manager Veritas NetBackup is third party software and 3PAR makes no representations or warranties with respect to such software Preinstallation Requirements 3 3 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 ona Linux system CAUTION When upgrading to a newer version of 3PAR Recovery Manager any previously installed versions of Recovery Manager must be removed Use the rpm e VCDBAora command to remove the previously installed package To install 3PAR Recovery Manager 1 Login asthe root user 2 Insert the 3PAR Recovery Manager CD into a CD ROM drive NOTE If the CD is not mounted automatically you can mount it manually mount t iso9660 r dev cdrom mnt cdrom 3 Change to the CD ROM drive cd mnt cdrom0 4 Issue the rpm command as follows rpm ihv percent nodeps VCDBAora 302 1 1386 rpm 3 4 Installing Recovery Manager on Linux Systems Recovery Manager for Oracle User
14. 1 lt alt_tpdhost gt 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 A virtual copy s repository can be exported to multiple alternate backup hosts which share the same InServ Storage Server as the original backup host A virtual copy can only be mounted on one backup host at a time The first time a virtual copy repository is exported to an alternate backup host the vcdba_export command also copies the Recovery Manager configuration file from the current backup host to the alternate backup host The vcdba_export command also modifies configuration parameters according to the values specified in the arguments for alt_tpdhost alt_tpdpwfile and alt_tpdusername If the vcdba_export command is invoked by an Oracle DBA an identical Oracle user ID and group ID must exist on the alternate backup host If SSH is currently configured for accessing from the current backup host to the primary host and the InServ Storage Server then SSH must also be configured to allow accessing from the current backup host to the alternate backup host as well as from the alternate backup host to the InServ Storage Server SSH is the only supported remote access method on Linux systems by 3PAR Recovery Manager If RSH and CLI are configured to access from the
15. 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 lt primary_host gt showsys 4 2 7 Setting Up a CLI Connection from the Backup Host to the InServ Storage Server Set up a CLI connection from the backup host to the InServ Storage Server as follows 1 On the backup host set the environment variables as follows TPDSYSNAME lt ss_name gt TPDPWFILE lt ss_pwfile gt export TPDSYSNAME TPDPWFILE E where e lt ss_name gt is the system name of the InServ Storage Server attached to the backup host lt ss_pwfile gt is the location for the InServ Storage Server user password file NOTE The following step is optional Perform step 2 if you want 3PAR Recovery p Manager to access the InServ Storage Server from the backup host as a different user than the user created on the primary host 2 On the backup host create a CLI user on the InServ Storage Server as follows lt backup_host gt opt 3par cli bin createuser c lt password gt lt username gt all edit See the InForm OS Command Line Interface Reference for additional information on the createuser
16. 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 If the X11 server is not running enter the following command For Solaris usr openwin bin xhost For Linux usr X11R6 bin xhost 3 Type the following command in an open terminal opt 3par vcdbaora bin vcdbagui 4 Press ENTER NOTE It is a known issue that the mouse events are not captured correctly on the cywin x server for Java6 7 2 Stopping the GUI gt To stop the Recovery Manager GUI click Console and then Exit 7 2 Starting and Stopping the Recovery Manager GUI 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 lt primary_host gt ora lt oracle_sid gt directory on the backup host Refer to 4 9 Recovery Manager Configuration Files on page 4 27 for additional details on creating configuration files with or without
17. CLI Connections for Recovery Manager Recovery Manager for Oracle User s Guide 2 Issue the rsh command for the primary host as follows lt backup_host gt rsh lt primary_host gt 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 To set up an RSH connection from the backup host to the Veritas NetBackup master server 1 Log in to the NetBackup master server as the root or Oracle user 2 Modify or create the rhosts file to contain the following line lt backup_host gt lt root_user gt where lt backup_host gt is the host name of the backup host e lt root_user gt is the root user s name on the backup host 4 2 4 Verifying RSH Connections from the Backup Host to the NetBackup Master Server From the backup host verify the RSH connection to the NetBackup master server as follows 1 On the backup host login in as the root or Oracle user as you logged in during set up 2 Issue the rsh command for the NetBackup master server as follows lt backup_host gt rsh lt nbu_master gt ls Make sure the command completes successfully Setting up RSH CLI Connections for
18. Logon asthe 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 VCDBAora You will be prompted to answer several questions about creating the installation area and the setuid files to be installed NOTE Install the following two patches if applicable e Solaris 5 9 SSH requires patch 114356 05 or higher e Solaris 5 10 requires patch 119130 26 or higher The following commands can be used to verify whether the patches are installed or not e showrev p grep 114356 e showrev p grep 119130 3 5 2 Verifying Installation To verify 3PAR Recovery Manager installation on a Solaris system 1 Login asthe root user Installing Recovery Manager on Solaris Systems 3 7 3 8 Recovery Manager for Oracle User s Guide 2 Use the pkginfo command as follows pkginfo 1 VCDBAora PKGINST VCDBAora NAME 3PAR Recovery Manager for Oracle on Solaris CATEGORY application ARCH Sparc VERSIO 3 0 2 BASEDIR opt 3par vcdbaora VENDOR 3PAR ESC 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 com STATUS comp
19. On the backup host run the vxdct1 enable command and import the disk groups using the same name as when you deported them Example vxdg import orcl920dg_042903142921 vxdg import arch920dg_042903142921 8 6 Database Volumes Under Veritas VxVM Control Recovery Manager for Oracle User s Guide c Onthe 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 The only exception is that no action is needed on the backup host at this time 2 On the backup host execute the Recovery Manager vcdba_rollback s lt oracle_sid gt p lt primary_host gt t lt timestamp gt v command to roll back the specified read only virtual copy Example vcdba_rollback s TEST920 p pilot t 042903142921 v 3 Recover the database on the primary host See step 4 and step 5 on page 8 5 When performing the import no disk group names need to be changed Database Volumes Under Veritas VxVM Control 8 7 Recovery Manager for Oracle User s Guide 8 8 Database Volumes Under Veritas VxVM Control Recovery Manager for Oracle User s Guide 9 Using Remote Copy with Reco
20. Oracle server Introduction 1 1 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 2 Related Documents The following documents also provide information related to the InServ Storage Server For Information About Read the CLI commands and their usage 3PAR InForm OS Command Line Interface Reference Identifying storage server components and 3PAR InForm OS Messages and detailed alert information Operator s Guide Using the Command Line Interface CLI to 3PAR InForm OS CLI Administrator s configure and manage InServ Storage Manual Servers Using the InForm Graphical User Interface 3PAR InForm Management Console GUI to configure and administer InServ Online Help Storage Servers Using 3PAR Remote Copy 3PAR Remote Copy User s Guide 1 2 Audience 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 De
21. Product Properties Cancel if you choose Veritas NetBackup you must create corresponding policies for NetBackup to use Please Enter RMAN Related Parameters RMAN Connection String RMAN Channel Type Disk Master Server Name Datafile Policy Name Archive Log Policy Name Specify No Of Channels SBT Tape Specify Backup Destination C Remove virtual copy from InServ after NBU backup Finish 7 Select the Vendor Backup Product from the menu Recovery Manager Configuration Files Recovery Manager for Oracle User s Guide 8 Enter the requested information under Related Parameters e The NetBackup policies must be pre created e 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 Ifyou do not want to delete the virtual copy after backing it up deselect the Remove virtual copy from InServ after NBU backup option 9 Click Finish Recovery Manager verifies the following Connections between the backup host and the primary host Connections between the backup host and the InServ Storage Server Connections between the primary host and the InServ Storage Server Connections between the backup host and
22. alt_tpdpwfile The location of the 3PAR InServ Storage Server client password file that will be used by Recovery Manager to access the InServ Storage Server from the alternate backup host The password file can be created using InForm CLI setpassword command e alt_tpdusername The 3PAR InServ Storage Server username that will be used by Recovery Manager to connect to the InServ Storage Server from the alternate backup host The InServ Storage Server user can be created using the InForm CLI createuser command The created user must have edit or above privilege Ifthe InForm CLI is configured to allow access from the alternate backup host to the InServ Storage Server then alt_tpdpwfile must be specified If SSH is configured to allow access from the alternate backup host to the InServ Storage Server then alt_tpdusername must be specified v Runs the command in verbose mode to display useful messages Command 6 21 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 Provide help page for the current working menu r Return to the
23. and Veritas NetBackup Client must be installed on the primary host and the backup host Additionally Veritas NetBackup for Oracle Oracle Agent must be installed on the primary host backup host and NetBackup master server if you select to backup to tape Recovery Manager requires that at least one NBU policy must be created per database Optionally a separate NBU policy can be created for archive log backup backup archive log only The NBU policies must be created as standard type or Oracle type for NBU user managed backup restore or Oracle RMAN backup restore respectively see 4 7 Setting Up NetBackup Policies for NBU User Managed Backup on page 4 19 or 4 8 Setting Up NetBackup Policies for Oracle RMAN Backup on page 4 22 for detailed information Interacting with Veritas NetBackup and Oracle RMAN 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 All operations that are available from Recovery Manager require this configuration file After the Recovery Manager configuration file is created for a database instance it
24. 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 0 64bit Production With the Partitioning Real Application Clusters OLAP and Oracle Data Mining options JServer Release 9 2 0 1 0 Production SQL gt archive log list Database log mode Archive Mode Automatic archival Enabled Archive destination vrac9i_db rac9i_arch2 Oldest online log sequence 764 Next log sequence to archive 764 Current log sequence 765 2 4 Interacting with Veritas Volume Manager Due to restrictions on VxVM 3PAR Recovery Manager requires a minimum of two disk groups per database CAUTION The archive log destination must reside on a different Veritas disk group than any of the disk groups that contain data files for backup operations It is also recommended that all database data files be in one VxVM disk group Because of the Veritas VxVM disk group limitation of allowing only one imported VxDG per disk group Recovery Manager allows only one virtual copy per database to be mounted at a time You must unmount the virtual copy for a database after it has been backed up in order to mount another virtual copy Interacting with Veritas Volume Manager 2 5 2 6 Recovery Manager for Oracle User s Guide 2 5
25. command Setting up RSH CLI Connections for Recovery Manager 4 7 4 8 Recovery Manager for Oracle User s Guide 3 On the backup host create a storage server user password file as follows lt backup_host gt opt 3par cli bin setpassword saveonly file STPDPWFILE u lt username gt where lt username gt 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 8 Verifying the CLI Connection from the Backup Host to the InServ Storage Server From the backup host verify the CLI connection to the InServ Storage Server as follows 1 On the backup 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 lt backup_host gt showsys Setting up RSH CLI Connections for Recovery Manager 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 configura
26. 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 Unmounting a database virtual copy involves the following actions For an ASM managed database if the ASM version on the backup host is 10 2 0 5 or 11 1 0 7 unmounting the virtual copy drops the ASM diskgroups that are contained in the virtual copy and cleans up the ASM disks If the ASM version on the backup is lower than those listed in the previous bullet unmounting shuts down the ASM instance and cleans up ASM disks Unmounts all snapshot file systems if the database files reside on file systems Destroys all snapshot VxVM disk groups and their VxVM volumes if the database files reside on VxVM volumes Deports the read write virtual copy from the backup host Removes the read write virtual copy 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 backup host In addition permission on the 3PAR Recovery Manager Installation and Repository directories must be changed appropriately Command 6 39 6 40 Recovery Manager for Oracle User s Guide OPTIONS The following options are supported
27. created if you have sufficient snapshot space 2 9 Database Rollback from a Virtual Copy When a database is corrupted you can restore the database to the most recent database images from the most recently created virtual copy by using the rollback utility 2 9 1 The Database Rollback Utility 3PAR Recovery Manager s database rollback utility vcdoa_rollback promotes a virtual copy s volumes back to its base virtual volumes In other words the base virtual volumes used by the database are rolled back to the virtual copy volumes Once the rollback process completes successfully the base virtual volumes are exactly the same as the virtual copy volumes If the base volume size has been changed since the virtual copy was taken the rollback process will not affect the new size a When rolling back from an online virtual copy both datafile and archive log virtual volumes are rolled back by default Use the o option to rollback only datafile virtual volumes or only archive log virtual volumes m When rolling back from an offline virtual copy only datafile virtual volumes are rolled back a When rolling back from an archive log virtual copy only archive log virtual volumes are rolled back The following restrictions apply when rolling back a virtual copy The online redo logs and control file should not reside on the same virtual volumes used by the datafiles and archive logs Otherwise they will be rolled back along with the dataf
28. data stream and Block level incremental options Backup Selections 1 It is recommended that you enter dummy for the backup selections 2 Recovery Manager generates the backup selection list on the fly to replace the value you entered Backup Schedule 1 Create a schedule for full backup 2 If you wish to perform immediate database backup initiated from Recovery Manager set the backup window to 0 3 If you also wish to perform automatic 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 host as the backup process will actually take place on the backup host 4 20 Setting Up NetBackup Policies for NBU User Managed Backup 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 Select the standard type for the policy 2 Select the cross mount points option Deselect the Allow multiple data stream and Block level incremental options Backup Selections 1 It is recommended that you enter dummy for the backup selections 2 Recovery Manager generates the backup selection list on the fly to replace the value you ent
29. database is an RAC database all RAC instances must be CLOSED For this option only virtual copies of datafile virtual volumes are created 0o coldbkup This option is the same as the o offline option and is deprecated This option will be removed in a future release o datafile Creates a virtual copy for all datafiles of an Oracle database The specified Oracle database instance must be OPEN If the database is an RAC database the other database instances can be either OPEN or CLOSED All tablespaces or database are put into backup mode before virtual copies of the data file virtual volumes are created All tablespaces or database are then taken out of backup mode A log switching is performed before and after the virtual copy is taken o archonly Creates a virtual copy of archive log destination only The specified database instance must be OPEN If the database is an RAC database other RAC instances can be either OPEN or CLOSED A log switching is performed before virtual copies of archive log virtual volumes are created v Runs the command in verbose mode to display useful messages Recovery Manager for Oracle User s Guide COMMAND vcdba_createdb SYNOPSIS vcdba_createdb s lt oracle_sid gt p lt primary_host gt t lt timestamp gt n lt clone_sid gt h lt clone_ora_home gt o ascii binary for_backup recovery norecovery d lt loc gt v DESCRIPTION Creates a new database instance fro
30. database option The cloned database is created on the backup host To clone a database 1 Select a virtual copy that has a status of Mounted 2 Right click the mounted virtual copy and click Create database 3 Provide the new database ID and the Oracle home directory Using Virtual Copies 7 9 7 10 Recovery Manager for Oracle User s Guide 4 6 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 Example If you provide clone_directoryl clone_directory2 CLONE_DATA notice combined ASM diskgroup and file systems are allowed in this operation make sure adequate permissions are granted for the user executing the clone utility If the binary control file is chosen to clone the database the clone operation will use exactly the same structure as that in the primary database The virtual copy must be mounted at before the database creation operation starts in order to ensure the clone database has exactly the same structure for all database files Click Finish After the cloned database operation has completed the Virtual Volume column is changed from Mounted to Database to indicate the cloned database is up and running Click OK 7 6 13 Removing a Cloned Database When a cloned database is no longer needed it can
31. databases any instance ID can be specified p lt primary_host gt The host name of the primary host on which the Oracle database instance is running The value of the primary host name must match the output of the hostname command m t lt timestamp gt The timestamp of a virtual copy to be backed up The virtual copy name can be obtained using the vcdba_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 The offline online datafile and archonly options are mutually exclusive o hotbkup This option is the same as the o online option This option is deprecated and will be removed at a later release o offline Creates an offline virtual copy of a database while it is CLOSED offline prior to backup This option is ignored if a virtual copy is specified The offline online datafile and archonly options are mutually exclusive o coldbkup Same asthe o offline option This option is deprecated and will be removed at a later release COMMAND 6 5 6 6 Recovery Manager for Oracle User s Guide COMMAND 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
32. gt etc 3par solutions lt primary_host gt ora lt oracle_sid gt 3 6 Removing Recovery Manager from Solaris Systems To remove 3PAR Recovery Manager from a Solaris system 1 Log in as the root user 2 Use the pkgrm command as follows pkgrm VCDBAora Removing Recovery Manager from Solaris Systems 3 9 Recovery Manager for Oracle User s Guide 3 10 Removing Recovery Manager from Solaris Systems Recovery Manager for Oracle User s Guide 4 Contiguring Recovery Manager In this chapter 4 1 Setting Up Connections on Recovery Manager 4 2 Setting up RSH CLI Connections for Recovery Manager 4 3 Setting Up SSH Connections for Recovery Manager 4 4 Setting up National Language Host Support 4 5 Setting up Manual Pages on Both Primary and Backup Hosts 4 6 Setting up a Search Path on Both Primary and Backup Hosts 4 7 Setting Up NetBackup Policies for NBU User Managed Backup 4 8 Setting Up NetBackup Policies for Oracle RMAN Backup 4 9 Recovery Manager Configuration Files 4 2 4 3 4 9 4 18 4 19 4 19 4 19 4 22 4 27 Configuring Recovery Manager 4 1 4 2 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 Sola
33. on the Host and Database Properties screen a Check the Remote Copy option b Click Next 4 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 46 Recovery Manager Configuration Files Recovery Manager for Oracle User s Guide e For RSH connection Solaris systems only enter the following information and then click Finish 3PAR InServ Properties This wizard will guide you through the modification of Recovery Manager configuration Please check the new values carefully Primary Local InServ Parameters InServName s537 InServ Password File full path Target 559 Data Group ASM11G_DATA Archive Group Backup Remote InServ Parameters InServ Name 5059 InServ Password File full path Backup Host Name in InServ sei Target 5537 Previous Finish Cancel 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 On the primary local and secondary remote systems use the InForm CLI showrcopy targets command to display the defined target names Data Group the Remote Copy group name for the virtual volumes where the datafiles are located In a single Remote Copy config
34. page 4 11 3PAR Recovery Manager uses the same CLI user to access the InServ Storage Server from either the backup host or primary host If you created a different CLI user for the primary host perform the following to set up an SSH connection from the primary host to the InServ Storage Server 1 Log in to the primary host as root user 2 Make sure the SSH key pair exists as follows lt primary_host gt ls ssh id_rsa id_rsa pub authorized_keys known_hosts 3 Create a CLI user to be used by Recovery Manager to access the InServ Storage Server from the primary host Skip this step if you wish to use an existing user different from the user created for the backup host lt primary_host gt ssh lt adm_user gt lt ss_name gt lt adm_user gt s password lt adm_password gt cli createuser c lt password gt lt username gt all edit 4 16 Setting Up SSH Connections for Recovery Manager Recovery Manager for Oracle User s Guide In the example above e lt adm_user gt is the user name of the InServ Storage Server s administrator e lt ss_name gt is the system name of the InServ Storage Server attached to the primary host e lt adm_password gt is the administrator s password lt password gt is the password for the InForm Storage Server for the CLI user being created e lt username gt is the user being created 4 Copy the public key of the primary host to the InServ Storage Server lt p
35. primary host name must match the output of the hostname command o all Validates all parameters specified in the Recovery Manager configuration file o skipdatabase Validates all non database parameters specified in the Recovery Manager Configuration file o databaseonly Validates all database parameters specified in the Recovery Manager Configuration file v Runs the command in verbose mode to display useful messages COMMAND 6 7 6 8 Recovery Manager for Oracle User s Guide COMMAND vcdba_config SYNOPSIS vcdba_config s lt oracle_sid gt p lt primary_host gt 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 lt primary_host gt ora lt oracle_sid gt config An equivalent environment file is also automatically created for each created configuration file It contains all configuration parameters specified in the configuration file 3PAR Recovery Manager uses the environment file instead The environment file is also stored at the same location as the configuration file vcdba_config is an interactive command The command will prompt for necessary information depending on a user s selection Generally the command
36. s Guide 3 3 2 Verifying Installation To verify 3PAR Recovery Manager installation on a Linux system 1 Login asthe root user 2 Issue the rpm command as follows rpm qi VCDBAora Name VCDBAora Relocations not relocatable Version 302 Vendor 3PAR Inc Release a Build Date Thu 18 Sep 2008 05 28 57 PM PDT Install Date Fri 19 Sep 2008 03 49 59 PM PDT Build Host spinner Group Applications system Source RPM VCDBAora 302 1 src rpm Size 112747698 License 3PAR Inc Signature none Packager John Smith lt johnsmith 3par com gt Summary Recovery Manager for Oracle on Linux Description 3PAR Recovery Manager for Oracle on Linux it provides a set of utilities to perform 3PAR Virtual Copy administration for online backup restore and off host processing 3 After the installation is complete on the primary and backup hosts you can allow Oracle users and Database Administrators group access to the Recovery Manager commands and utilities by changing the owner and permissions of the following directories required for Oracle users opt 3par vcdbaora etc 3par solutions e etc 3par solutions log e etc 3par solutions lock etc 3par solutions lt primary_host gt ora lt oracle_sid gt Installing Recovery Manager on Linux Systems Recovery Manager for Oracle User s Guide a Change the owner of the Recovery Manager utilities and repository as follows where the Database Administrato
37. supported Command s lt oracle_sid gt The instance SID of the primary database For an RAC database any instance SID can be specified p lt primary_host gt 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 lt timestamp gt The timestamp of a virtual copy It is also the name of the virtual copy The virtual copy name can be obtained using the vcdba_display command n lt clone_sid gt The new Oracle SID for the clone database If this option is omitted or is used with the o for_backup option the clone database will have the same ORACLE_SID as the primary database If creating a clone database with the o binary option the new Oracle SID will be ignored h lt clone_oracle_home gt The Oracle home directory on the backup host If specified this value will be used instead of the value of the parameter ORACLE_HOME_BACKUP in the configuration file d lt loc gt A comma separated list of directories or ASM diskgroups for multiplexing to store the new online redologs and controlfiles of the clone database The directories or ASM diskgroups must have enough available space to hold new online redo logs and controlfiles Users who run this command must have write permission to this directory or directories The number of multiplex redo log locations must be equal to or less t
38. system name of the primary local InServ Storage Server which is attached to the primary host You are not prompted for a password if set up correctly 3 Verify the Remote Copy ports cli showport rcip NOTE Ensure the ports are in the ready state 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 0002B3CO03DF2 193 1 1 1 255 255 255 0 1500 1 5 1 ready 0002B3C03H94 194 1 1 1 255 255 255 0 1500 4 Verify the Remote Copy primary local group datafile group and archive log group cli showrcopy groups lt group name gt Verifying Remote Copy Settings 9 5 Recovery Manager for Oracle User s Guide where e lt group name gt is the Remote Copy group name of the virtual volumes where the datafiles of the database reside gt NOTE Ensure the group is in the Start state and in Periodic mode 5 Verify the Remote Copy targets cli showrcopy targets lt target_name gt where lt target_name gt 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 Verifying the Secondary Remote Copy Setting To verify the secondary remote Remote Copy setting 1 Log in to the backup host as the root user 2 Connect to the se
39. the Command Line Interface on the Backup Host 4 27 4 9 1 2 Creating a Recovery Manager Configuration File using the GUI on the Backup Host 4 33 4 9 2 Creating a Recovery Manager Configuration File Using Remote Copy 4 40 4 9 2 1 Creating Configuration Files using the Menu Driven Application or Command Line Interface on the Backup Hos 4 40 4 9 2 2 Creating a Recovery Manager Configuration File using the GUI on the Backup Host 4 44 5 Using Recovery Manager from the Menu Driven Application 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 3 Backing Up Virtual Copies 5 7 5 3 1 Performing Immediate Backups 5 7 5 3 2 Performing Automatic Backups 5 8 5 4 Performing Restores 5 9 5 4 1 Performing Restores 5 9 5 5 Performing Periodic Remote Copy 5 10 6 Using the Recovery Manager Command Line Interface vcdba_backup 6 3 Vi Table of Contents Recovery Manager for Oracle User s Guide vcdba_checkconfig vcdba_config vcdba_create vcdba_createdb vcdba_display vcdba_export vcdba_main vcdba_mount vcdba_remove vcdba_removedb vcdba_restore vcdba_rmrep vcdba_rollback vcdba_rsync vcdba_umount Using the Reco
40. the InForm CLI showhost command on the secondary remote InServ Storage Server The InServ Storage Server s hostname of the backup host may not be the same as the DNS hostname of the backup host Press ENTER to accept the default value otherwise provide the correct hostname defined in the InServ Storage Server Enter Primary Local 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 primary local InServ Storage Server to allow access from the primary host to the primary local InServ Storage Server Enter 3PAR password file on primary host h help q quit You will only be prompted with this question if you previously selected RSH as the remote shell Recovery Manager requires that a 3PAR password file must have been created on the primary host to allow access to the Primary Local InServ Storage Server from the primary host Recovery Manager Configuration Files 4 43 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 Enter 3PAR password file
41. the NetBackup master server if NetBackup is selected If Recovery Manager successfully connects to the database Recovery Manager retrieves the database tablespaces datafiles the archive log destination and the virtual volumes where the database resides After verification is completed Recovery Manager creates a virtual copy repository on the backup host etc 3par solutions lt primary_host gt ora lt oracle_sid gt and two configuration files are generated along with one subdirectory for database files mapping information etc 3par solutions lt primary_host gt ora lt oracle_sid gt config etc 3par solutions lt primary_host gt ora lt oracle_sid gt config_exp sh etc 3par solutions lt primary_host gt ora lt oracle_sid gt gui Recovery Manager Configuration Files 4 39 4 40 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 Create one Remote Copy groups assign all virtual volumes used by datafiles and archive log destinations to the group volumes to Remote Copy groups all volumes in the same Veritas disk group Yy CAUTION If Verit
42. the Remote Copy feature NOTE The configuration file cannot be recreated if it already exists in the repository You can modify the configuration as needed or remove the configuration before a new one can be created 7 4 Modifying Configuration Files Configuration files can only be modified from the host node level Modifications are made in the config and config_exp sh files in the repository 7 5 Removing Configuration Files Configuration files can be removed if there are no virtual copies existing in the repository When configuration files are removed the entire repository is also removed Creating Configuration Files 7 3 7 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 2 3 Select Virtual Copy Management from the navigation view Select Create Virtual Copy from the Virtual Copies pull down menu Select the desired options online backup offline backup backup datafile only or backup archive log dest only from the dialog box Online Hot backup The involved database instance must be up for this operation All tablespac
43. vcedba_rman_dbbackup sh or vcdba_rman_archbackup sh to backup the clone data base The RMAN backup scripts vcdba_rman_dbbackup sh and vcdba_rman_archbackup sh are generated at etc 3par solutions lt primary_host gt ora lt oracle_sid gt during the creation of the Recovery Manager configuration file see vcdba_config Depending on which backup method has been configured for the Recovery Manager the vcdba_backup command performs the following actions COMMAND Creates a virtual copy online offline or datafile for the database or archive log destination if a virtual copy is not specified Mounts the virtual copy on the backup host 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 lt policy_name gt on the NBU client the backup host 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 In addition permission on the 3PAR Recovery Manager Installation and Repository directories must be changed appropriately OPTIONS The following options are supported m s lt oracle_sid gt The instance ID of the primary database For Real Application Cluster RAC
44. 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 You may want to create separate virtual copies using the o archonly options or use another backup method to backup archive log destinations o archonly Creates a virtual copy of the archive log destination prior to backup This option cannot be used if a virtual copy is specified The offline online datafile and archonly options are mutually exclusive o full Performs a full backup of a virtual copy If Veritas NetBackup is selected as the backup method this option can be used with the o archonly option to perform full backup of an archonly virtual copy If Oracle RMAN is selected as the backup method this option can be used to perform full backup of an online or offline virtual copy o incr Performs an incremental backup of a virtual copy If Veritas Netbackup is selected as the backup method this option can be used with the o archonly option to perform incremental backup of an archonly virtual copy If Oracle RMAN is selected as the backup method this option can be used to perform an incremental backup of an online or offline virtual copy o cinc Performs a cumulative incremental backup of a virtual copy If Veritas NetBackup is selected as the backup method this option can be used with the o archonly option to perform a cumulative incremental backup of an archonly virt
45. volumes are involved in a Remote Copy group you must use f to promote the virtual copies back to their base volumes Command 6 35 6 36 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 In addition permission on the 3PAR Recovery Manager Installation and Repository directories must be changed appropriately OPTIONS The following options are supported Command s lt oracle_sid gt The instance SID of the primary database For an RAC database any instance SID can be specified p lt primary_host gt 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 lt timestamp gt The timestamp of a virtual copy form which to promote The virtual copy name can be obtained using the vcdba_display command o data arch data Promotes only the virtual copy s datafile volumes back to their base virtual volumes e arch Promotes only the virtual copy s archive log v
46. 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 For the cloned database on the backup host you should perform log switches to make sure all online redo logs are switched to archive log files and that they are physically on the disk before you shutdown the cloned database Or you can FTP over all online redo log files to the primary host which can be used when performing database recovery b Manually unmount all file systems used by both databases Do not use the vcdba_umount utility in this step which not only unmounts the file systems but also removes the read write virtual copy from the InServ Storage Server If ASM is being used unmount all involved ASM disk groups c Deport the VxVM disk groups used by datafiles and archive log destination Example On the backup host vxdg deport orcl920dg_042903142921 vxdg deport arch920dg_042903142921 On the primary host vxdg deport orcl920dg vxdg deport arch920dg Disk groups with trailing timestamps are created by Recovery Manager when performing a database backup They can be found in the virtual copy repository 2 On the InServ Storage Server remove the VLUNs used by datafiles and archive log destination by issuing the removevlun lt vvname gt lt lun gt lt host gt command 8 4 Database Volumes Under Veritas Vx
47. 2 3 4 3 4 3 5 3 6 3 6 3 7 3 7 3 9 4 2 4 3 4 2 1 4 2 2 4 2 3 4 2 4 4 2 5 4 2 6 4 2 7 4 2 8 Se Veri Se Veri Se Veri Se Veri 3 3 3 3 Recovery Manager for Oracle User s Guide ing Up an RSH Connection from the Backup Host to the Primary Host ying the RSH Connection from the Backup Host to the Primary Host ing Up RSH Connections from ying RSH Connections from th ing Up a CLI Connection from ying the CLI Connection from ing Up a CLI Connection from ying the CLI Connection from he Backup Hos e Backup Host t he Primary Hos the Primary Hos to the NetBackup Master Server o the NetBackup Master Server to the InServ Storage Server t to the InServ Storage Server he Backup Hos to the InServ Storage Server the Backup Host to the InServ Storage Server 4 3 Setting Up SSH Connections for Recovery Man 44 4 5 4 6 47 4 8 4 3 1 4 3 2 4 3 3 4 3 4 4 3 5 4 3 6 4 3 7 4 3 8 4 3 9 SSH Restrictions ager Modifying the SSH Daemon Configuration Generating an SSH Key Pair for the Backup Host Generating an SSH Key Pair for the Primary Host Setting Up Connections from the Backup Host Verifying Connections from the Backup Host to Setting Up Connections from the Backup Host Verifying Connections from the Backup Host to Setting Up Connections from the Backup Host o the o the o the Primary Ho
48. 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 6 Removing Recovery Manager from Solaris Systems 3 9 This chapter describes how to install verify and remove 3PAR Recovery Manager for Oracle on systems running Linux and Solaris Installing and Deinstalling Recovery Manager 3 1 3 2 Recovery Manager for Oracle User s Guide 3 1 Referencing the Support Matrix For information about supported platforms refer to the nForm 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 Prior to the installation of Recovery Manager make sure that the following preinstallation requirements are met The same Oracle owner user and Oracle DBA group on the primary database server must exist on the backup host The Oracle owner user ID and Oracle DBA group ID on the backup host must be the same as on the primary host All Oracle data files and archive logs must reside on separate 3PAR virtual volumes Online redo logs and control files can reside on the same virtual volume However redo l
49. 5 4 26 Recovery Manager for Oracle User s Guide 5 Configure TNS services for the Recovery Catalog database by adding an entry in the SORACLE_HOME network admin tnsnames ora file on the primary host and backup host as follows T lt catdb gt description address protocol TCP host lt cat_host gt port 1521 connect_data server dedicated service_name lt catdb gt where lt cat_host gt is the host name of the host where the catalog is created 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 lt catdb gt ORACLE_HOME lt oracle_home gt SID_NAME lt catdb gt 7 Log in as the Oracle owner user and register the database on the primary host rman target catalog lt rman_user gt lt rman_password gt lt catdb gt RMAN gt register database Setting Up NetBackup Policies for Oracle RMAN Backup 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 m Recovery Manager without
50. 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 lt primary_host gt ora lt oracle_sid gt vcdba_nbu_dbbackup sh Recovery Manager will generate the RMAN backup script at the specified location when you create the configuration file see 4 9 Recovery Manager Configuration Files on page 4 27 below for details Backup Schedule Create two schedules one for full backup and one for incremental backup optional For the incremental backup schedule you can create either a differential incremental or cumulative incremental backup schedule If you wish to perform immediate database backup initiated from Recovery Manager set the backup window to 0 If you also wish to perform automatic 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 host as the backup process will actually take place on the backup host Setting Up NetBackup Policies for Oracle RMAN Backup 4 23 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
51. C11 Backup Server Location Related Parameters Database Home on Backup Server j oracle_base ora product 11 1 0 asm ASM Home on Backup Server oracle_base fora product11 1 Olasm Recovery Manager Configuration Files 4 35 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 Configure Recovery Manager Properties 3PAR InServ Properties Please fill in the field carefully incorrect input values will prevent Recovery Manager from accessing to 3PAR InServ Server R Primary Local InServ Parameters InServName 5537 InServ SSH Username ora Backup Remote InServ Parameters InSeryName 5537 InSery SSH Username ora Backup Host Name in InSery sunt1k 02 Previous Ni Cancel 5 Depending on the connection option you choose perform one of the following e For Solaris systems If you selected the Remote Shell RSH option when configuring the database enter the requested information on the screen and click Next Ifyou selected the Secure Shell SSH option when configuring the database enter the requested information on the configuration screen and click Next 4 36 Recovery Manager Co
52. 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 If the virtual copy is being backed up using NBU the backup key has the format lt oracle_sid gt _ lt primary_host gt _ lt timestamp gt To restore a datafile 1 Right click the desired virtual copy 2 Click Restore A screen appears displaying the virtual copy set information and you are prompted for the host name and mount point for restoring the data files If the mount point is left blank files are restored to their original paths on the primary host 3 Click Finish 7 6 10 Refreshing Database Information Tablespace datafile archive log and virtual volume information can be refreshed in the Recovery Manager GUI by performing the following 1 Click any of Tablespace Datafiles Archive Log or Virtual Volumes in the left hand tree 2 Click Refresh in the tool bar Recovery Manager retrieves all the information from the primary database All mappings are for informational purposes and cannot be modified All mappings reflect the current database and virtual copy information if the primary database is accessible Using Virtual Copie
53. Form CLI showsys command Enter remote copy target name on primary local InServ h help q quit Enter the Remote Copy target name defined on the primary local InServ Storage Server Enter remote copy group name for datafiles on primary local InServ h help q quit Recovery Manager requires that one Remote Copy group must have been created on the primary local InServ Storage Server The Remote Copy group must contain all virtual volumes used by the data files Enter remote copy group name for archive log on primary local InServ h help q quit Recovery Manager Configuration Files 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 Enter remote copy target name on remote secondary InServ h help q quit Enter the Remote Copy target name defined on the secondary remote InServ Storage Server Enter InServ hostname from showhost output of the backup host h help q quit The InServ Storage Server s hostname of the backup host can be retrieved from the output of
54. 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 Instead of a traditional backup where the database is backed up directly on the production server Recovery Manager creates a virtual copy snapshot of the database imports it to a secondary host backup host and then performs the backup of the virtual copy on the backup host Recovery Manager provides two ways to perform backup and restoration NBU user managed and Oracle RMAN NOTE For an ASM managed database Oracle RMAN backup is the only p supported backup method For NBU user managed backup and restoration Recovery Manager interacts directly with NBU to trigger the backup restore process Recovery Manager requires that the NBU client must be installed on the primary database server and the backup host For Oracle RMAN backup Recovery Manager supports backup to tape and backup to disk If Recovery Manager is configured to perform backup to disk Recovery Manager interacts with Oracle RMAN to trigger the backup process If Recovery Manager is configured to perform backup to tape Recovery Manager interacts with Oracle RMAN which in turn interacts with NBU to trigger the backup restore process Recovery Manager requires that Oracle database software Oracle RMAN
55. One contained all data file volumes and one contained archive log volumes In the current release 3PAR also supports one Remote Copy group which contains both datafile volumes and archive log volumes OPTIONS The following options are supported m s lt oracle_sid gt The instance SID of the primary database For an RAC database any instance SID can be specified p lt primary_host gt 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 o online Performs periodic synchronization for datafile and archive log virtual volumes while the database is OPEN m o hotbkup This option is the same asthe o online and is deprecated This option will be removed in a future release Command 6 37 6 38 Recovery Manager for Oracle User s Guide Command 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 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 vcedba_umount s lt oracle_sid gt p lt primary_host gt t lt timestamp gt DESCRIPTION Unmounts a virtual
56. Recovery Manager 4 5 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 Onthe primary host set the environment variables as follows TPDSYSNAME lt ss_name gt TPDPWFILE lt ss_pwfile gt export TPDSYSNAME TPDPWFILE where lt ss_name gt is the system name of the InServ Storage Server attached to the primary host e lt ss_pwfile gt is the location for the InServ Storage Server user password file NOTE Before creating a CLI user refer to the nForm OS CLI Administrator s p Manual for a list of reserved user names 2 Onthe primary host create a CLI user as follows lt primary_host gt opt 3par cli bin createuser c lt password gt lt username gt all edit where lt username gt is the name of the user being created For additional information about the createuser command see the nForm OS Command Line Interface Reference 3 On the primary host create a storage server user password file as follows lt primary_host gt opt 3par cli bin setpassword saveonly file STPDPWFILE u lt username gt where lt username gt is the username you created in step 2 4 6 Setting up RSH CLI Connections for Recovery Manager Recovery Manager for Oracle User s Guide 4 2
57. Remote Copy support For this type of configuration Recovery Manager provides an integrated Veritas NetBackup and Oracle RMAN for backups and restorations m Recovery Manager with Remote Copy For this type of configuration Recovery Manager does not provide tools for media backups and restorations You can choose to create the Recovery Manager configuration file by either using the Command Line Interface CLI menu driven application or a Graphical User Interface GUI NOTE New features are no longer being added to the menu driven application 4 9 1 Creating a Recovery Manager Configuration File without Remote Copy The configuration file can be created in the following ways Menu driven application e CLI a GUI 4 9 1 1 Creating Configuration Files using the Menu Driven Application or the Command Line Interface on the Backup Host To create a Recovery Manager configuration file without Remote Copy support 1 From the backup host start Recovery Manager lt backup host gt opt 3par vcdbaora bin vcdba_main 2 If you are using the CLI from the backup host issue opt 3par vcdbaora bin vcedba_config and then skip to step 4 Recovery Manager Configuration Files 4 27 Recovery Manager for Oracle User s Guide 3 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 4 When prompted press ENTER
58. S to the list of known hosts where e lt username gt is the CLI user created in 4 3 9 Setting Up Connections from the Backup Host to the InServ Storage Server on page 4 14 e lt ss_name gt is the name of the InServ Storage Server attached to the primary host 4 4 Setting up National Language Host Support The 3PAR Recovery Manager message catalog is installed in the opt 3par vcdbaora msg en_US directory and the symbolic link is installed in the usr lib locale en_US directory gt To retrieve the text messages properly you must set the NLSPATH path environment NLSPATH SNLSPATH usr lib locale L N export NLSPATH 4 18 Setting up National Language Host Support 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 To access the manual pages define the environment variable MANPATH as follows MANPATH SMANPATH opt 3par vcdbaora man export MANPATH LC_ALL en_US export LC_ALL 4 6 Setting up a Search Path on Both Primary and Backup Hosts 3PAR Recovery Manager executables are stored in the opt 3par vcdbaora bin directory is provided for main programs gt To add the Recovery Manager executables to the Recovery Manager search path use the following commands PATH SPATH opt 3par vcdbaora bin export PATH
59. Serving Information 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 ar November 2009 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 3PAR reserves the right to make changes in the product design without reservation and without notification to its users Updates to the Documentation at 3PAR Central Any updates to this document or other 3PAR technical documents can be found by logging into 3PAR Central s Document Control System from 3PAR s Support page at http www 3PAR com support index html 3PAR Technical Support and Services Contact your local service provider for technical support and services Sales and Ordering Information For sales and ordering information contact 3PAR Inc 4209 Technology Drive Fremont CA 94538 U S A Telephone 510 413 5999 Fax 510 413 5699 E mail salesinfo 3PAR com Reader Comments and Suggestions E mail your comments and suggestions about this document to Readercomments 3PAR com C
60. Setting Up Connections from the Backup Host to the Primary Host To set up an SSH connection from the backup host to the primary host perform the following gt Copy the public key id_rsa pub of the backup host to the authorized_keys file of the primary host lt backup_host gt scp ssh id_rsa pub lt primary_host gt ssh authorized_keys If the authorized_keys file already exist add the public key to the end of the authorized_keys file 4 3 6 Verifying Connections from the Backup Host to the Primary Host From the backup host verify the connection to the primary host as follows NOTE If you are prompted for a password the setup is incorrect and you must redo the previous setup 4 12 Setting Up SSH Connections for Recovery Manager Recovery Manager for Oracle User s Guide lt backup_host gt ssh root lt primary_host gt The authenticity of host lt primary_host gt can t be established DSS key fingerprint is XX XX XX XXIXXIXXIXXXXIXXIXXIXXIXXXIXXXX Are you sure you want to continue connecting yes no yes Warning Permanently added lt primary_host gt DSS to the list of known hosts where lt primary_host gt is the primary host s hostname 4 3 7 Setting Up Connections from the Backup Host to the NetBackup Master Server To set up an SSH connection from the backup host to the NetBackup NBU master server perform the following gt Copy the public key id_rsa pub of the backu
61. 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 Overview of Recovery Manager Operations 2 1 2 2 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 21 This chapter introduces virtual copy technology and provides instructions for using 3PAR Recovery Manager to back up and restore Oracle databases In this document the following terminology is used primary host A host machine where the Oracle database installation occurs backup host A host machine where Recovery Manager for Oracle operations and backup media installation take place 2 1 Virtual Copies A virtual copy is a point in time image of a virtual volume created using the copy on write technique It is composed of a pointer to the parent virtual volume and a record of all the changes made to the parent since the virtual copy was created These changes can be rolled back to reproduce the parent s earlier state A virtual copy can be exported to or mounted on a server to allow regular operations such as backup o
62. 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 Once the promote rollback process completes successfully the base virtual volumes will be exactly the same as the virtual copy s volumes If the base volume size has been changed since the virtual copy was taken the rollback process will not affect the new size When rolling back from an online virtual copy both datafile and archive log virtual volumes are rolled back by default Use the o option to roll back only datafile virtual volumes or only archive log virtual volumes When rolling back from an offline virtual copy only datafile virtual volumes are rolled back When rolling back from an archive log virtual copy only archive log virtual volumes are rolled back The following restrictions apply when rolling back a virtual copy The online redo logs and control file should not reside on the same virtual volumes used by the datafiles and archive logs Otherwise they will be rolled back along with the datafile and archive log virtual volumes The database instance must be CLOSED for this operation If the database is an RAC database all RAC instances must be CLOSED The base data file and or archive log virtual volumes must not be exported The specified virtual copy must have an Available not mounted status If the base virtual
63. VM Control Recovery Manager for Oracle User s Guide 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 a NOTE If all VLUNs used by the database are removed remember to recreate all 3 Perform rollback on the backup host by executing the Recovery Manager vcdba_rollback s lt oracle_sid gt p lt primary_host gt t lt timestamp gt v w command to roll back the read write copy which is based on point in time read only snapshot when performing a database backup Example vcdba_rollback s TEST920 p pilot t 042903142921 v w 4 On the InServ Storage Server recreate all of the VLUNs which were removed earlier Us the same VLUN information by issuing the createvlun lt vvname gt lt lun gt lt host gt command 5 Onthe primary host run the vxdct1 enable command and import the disk groups with the original names and start all VM volumes Wait until all disks are online Example vxdg fC n orcl920dg import orcl920dg_042903142921 vxdg fC n arch920dg import arch920dg_042903142921 vxvol g orcl920dg startall vxvol g arch920dg startall d Runthe vxdisk list command to see if all volume disks are online and belong to the original names Database Volumes Under Veritas VxVM Control 8 5 Recovery Manager for Oracle User s Guide Example
64. abase Backup Archive Logs 4 Restore Administration Use this menu to perform restore from a virtual copy backup image You can use this menu only if virtual copies are backed up by Veritas NetBackup using the 3PAR Backup Administration menu 5 Remote Copy Administration Use this menu to perform periodic synchronization for virtual volumes used by a database 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 backup host In addition permission on the 3PAR Recovery Manager Installation and Repository directories must be changed appropriately Command 6 23 Recovery Manager for Oracle User s Guide COMMAND vcdba_mount SYNOPSIS vcdba_mount s lt oracle_sid gt p lt primary_host gt t lt timestamp gt m lt mountpoin gt 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 The following restrictions apply when mounting a database virtual copy a The virtual copy must have an Available or Mounted P status in order to be mounted The virtual copy s status can be retrieved using the Recovery Manager display utility The same virtual copy cannot be mount
65. acle User s Guide 1 2 1 2 1 3 1 4 1 5 2 2 2 3 2 4 2 5 2 6 2 7 2 7 2 7 2 9 2 10 2 11 Table of Contents iv Recovery Manager for Oracle User s Guide 3 4 Table of Contents 2 6 6 The Virtual Copy Export Utility 2 6 7 The Database Cloning Utility 2 6 8 The Cloned Database Removal Utility 2 6 9 The Virtual Copy Removal Utility 2 7 The Virtual Copy Repository 2 7 1 The Virtual Copy Repository Removal Utility 2 8 Virtual Copy Policy 2 9 Database Rollback from a Virtual Copy 2 9 1 The Database Rollback Utility 2 10 Recovery Manager and Third Party Backup Tools 2 10 1 The Database Backup Utility 2 10 1 1 Immediate Backup 2 10 1 2 Automatic Backup 2 10 2 The Database Restoration Utility 2 11 Recovery Manager with Remote Copy Installing and Deinstalling Recovery Manager 3 1 Referencing the Support Matrix 3 2 Preinstallation Requirements 3 3 Installing Recovery Manager on Linux Systems 3 3 1 Starting Installation 3 3 2 Verifying Installation 3 4 Removing Recovery Manager from Linux Systems 3 5 Installing Recovery Manager on Solaris Systems 3 5 1 Starting Installation 3 5 2 Verifying Installation 3 6 Removing Recovery Manager from Solaris Systems Configuring Recovery Manager 4 1 Setting Up Connections on Recovery Manager 4 2 Setting up RSH CLI Connections for Recovery Manager 2 12 2 12 2 14 2 14 2 14 2 14 2 15 2 15 2 15 2 16 2 16 2 17 2 18 2 20 2 21 3 2 3
66. allation and Repository directories must be changed appropriately OPTIONS The following options are supported m s lt oracle_sid gt The instance ID of the primary database For an RAC database any instance ID can be specified m p lt primary_host gt 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 m o online Creates an online virtual copy of an Oracle database while it is OPEN online The specified Oracle database instance must be OPEN If the database is an RAC database other database instances can be either OPEN or CLOSED All tablespaces or database will Command 6 13 6 14 Recovery Manager for Oracle User s Guide Command 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 0o hotbkup This option is the same as the o online option and is deprecated This option will be removed in a future release o offline Creates an offline virtual copy of an Oracle database while it is CLOSED offline The specified database instances must be CLOSED If the
67. allowed the next virtual copy creation will fail 5 3 Backing Up Virtual Copies max NOTE Backup is not supported on Remote Copy configuration Read the following sections for information about backing up virtual copies using Recovery Manager 5 3 1 Performing Immediate Backups To perform immediate backups using the menu driven application 1 On the 3PAR Recovery Manager for Oracle main menu select option 3 Backup Administration 2 Select the database to be backed up 3 When prompted to backup the existing virtual copy enter y n or q If you answer n to backup the existing virtual copy the program creates the new virtual copy and the next screen to appear allows you to select either Backup Database or Backup Archive Log Destination Backing Up Virtual Copies 5 7 5 8 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 gt 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 Backup Archive Logs Destination Select this option to create a virtual copy of the archive log destination only You are aske
68. 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 Backup Selections 1 Enter the location of RMAN backup script etc 3par solutions lt primary_host gt ora lt oracle_sid gt vcdba_nbu_archbackup sh 2 Recovery Manager will generate the RMAN backup script at the specified location when you create the configuration file see 4 9 Recovery Manager Configuration Files on page 4 27 below for details Backup Schedule 1 Create a schedule for full backup 2 If you wish to perform immediate archive log backup initiated from Recovery Manager set the backup window to 0 3 If you also wish to perform automatic archive log 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 host as the backup process will actually take place on the backup host 4 8 3 Creating an RMAN Recovery Catalog This section describes how to create and configure an RMAN Recovery Catalog Refer to Oracle documentation for more detailed information 1 Create a database for housing the Recovery Catalog Oracle suggests the following disk space requirements e System tablespace 100 MB Temp tablespace 5 MB Rollback segment 5 MB Online redo log 1 MB each
69. 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 Foran online virtual copy only datafiles are restored Archive logs are not restored to minimize restore time as Oracle RMAN can restore only necessary archive logs during recovery Only datafiles are restored for an offline or datafile virtual copy Restoring from an archive log virtual copy backup image is not supported as Oracle RMAN can restore only necessary archive logs during recovery 2 11 Recovery Manager with Remote Copy If 3PAR Remote Copy is set up for a database 3PAR Recovery Manager s remote synchronization utility vcdba_rsync can perform a periodic synchronization of database virtual volumes Once the synchronization process completes a virtual copy is created automatically for the remote virtual volumes on the secondary InServ Storage Server The virtual copy can then be mounted on a backup host for off host processing purposes Recovery Manager with Remote Copy 2 21 Recovery Manager for Oracle User s Guide 2 22 Recovery Manager with Remote Copy 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
70. as Volume Manager is being used when assigning 3PAR virtual should be assigned to one Remote Copy group whether they are actually being used by the Oracle database or not Otherwise you might not be able to import and mount file systems on the remote backup host Therefore it is strongly suggested that Veritas disk groups only contain files used by one Oracle database Start Remote Copy and verify its setup 4 9 2 1 Creating Configuration Files using the Menu Driven Application or Command Line Interface on the Backup Host To create the Recovery Manager configuration files 1 From the backup host start Recovery Manager lt backup_host gt opt 3par vcdbaora bin vcdba_main If you are using the CLI from the backup host issue opt 3par vcdbaora bin vcedba_config and then skip to step 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 When prompted answer the following questions Recovery Manager Configuration Files 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 cor
71. atafile or Archlog An Online virtual copy indicates that the virtual copy for the database was created while it was OPEN online An Offline virtual copy indicates that the virtual copy for the database was created while it was CLOSED offline A Datafile virtual copy indicates that the virtual copy for the database was created while it was OPEN online and contains only datafiles no archive log destination An Archlog virtual copy indicates that the virtual copy was created for archive log destination only A virtual copy s status can be either Available Removed Mounted Mounted P or Database m Available status indicates that the virtual copy exists and is not currently mounted or cloned Removed status indicates that the virtual copy is removed Mounted status indicates that the virtual copy is currently mounted Mounted P status indicates that the virtual copy is partially mounted Database status indicates that a database has been cloned using the virtual copy A virtual copy s backup status can be either Y or N where Y indicates that the virtual copy has been backed up and N indicates that the virtual copy has not been backed up Recovery Manager Utilities 2 9 2 10 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 v
72. back 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 12 verifying SSHconnection from primary host to InServ 4 17 virtual copies 7 7 backing up 5 7 7 7 creating 5 4 7 4 displaying 5 3 explanation of 2 2 Index exporting 5 5 exporting to alternate hosts 7 9 managing 5 7 mounting 5 5 7 6 refreshing information 7 5 removing 5 4 7 7 rolling back read only 8 2 rolling back read write 8 3 setting up the virtual copy policy 7 5 unmounting 5 5 7 6 virtual copy creating consistent copies 2 4 virtual copy of archive log destination only creating 5 8 virtual copy of database instance creating 5 8 virtual copy policy 2 15 virtual copy policy setup 7 5 virtual copy removal utility 2 14 virtual copy repository 2 14 virtual copy repository removal 5 6 virtual copy repository removal utility 2 14 wW warnings defined 1 5 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 1 Recovery Manager for Oracle User s Guide RH 2 Revision History
73. base 7 9 command line utilities location 6 2 configuration files 4 27 configuration backup host 4 27 4 33 4 44 configuring backup host with GUI 4 44 Recovery Manager for Oracle User s Guide configuring NBU policy for archive log backup 4 21 configuring NBU policy for database backup 4 20 connections 4 2 conventions typographical 1 4 create utility 2 7 actions 2 8 creating a database copy 6 12 creating an RMAN recovery catalog 4 24 creating configuration file with GUI 4 33 creating configuration files 7 3 creating databases 6 15 creating virtual copies 5 4 7 4 D data file restoration 7 8 database backup configuring NBU policy 4 20 database backup utility 2 16 database clone utility 2 12 database configuration utility 2 7 database restoration 5 9 database restore utility 2 20 database rollback 2 15 database rollback utility 2 15 databases cloning 7 9 periodic synchronization 7 10 refreshing information 7 8 deinstalling from Linux systems 3 6 Index IX 1 IX 2 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 immediate backup 2 17 immediate backups performing 5 7 performing using the menu driven application 5 7 installation 3 6 on Linux syst
74. be admitted to the Remote Copy group If ASM is being used all volumes that are in the same ASM disk group as the datafiles or archive log destinations must be admitted to the Remote Copy group Remote copy group must be started and in synchronized status Refer to the 3PAR Remote Copy User s Guide to set Remote Copy targets links and groups After the above has been set up a Recovery Manager configuration file must be created There are three ways to create a configuration file On the backup host gt Run opt 3par vcdbaora bin vcdbagui to start the Recovery Manager Graphical User Interface GUI or Run opt 3par vcdbaora bin vcdba_main to start the Recovery Manager menu driven utility or Run opt 3par vcdbaora bin vcdba_config to start the Command Line Interface CLI Refer to the 4 9 Recovery Manager Configuration Files on page 4 27 to setup the configuration file for Remote Copy System Configuration 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 lt primary_host gt ssh lt username gt lt ss_name gt where e lt username gt is the InServ Storage Server user e lt ss_name gt is the
75. be removed with the following procedure 1 2 Select a virtual copy with a status of Database Right click on the selected virtual copy and click Remove database Click Yes Click OK 7 7 Periodic Database Synchronization The periodic synchronization process is an asynchronous process Synchronization takes minutes to hours for the synchronized process to finish depending on data changes network speed and load on the primary host backup host primary local and secondary remote InServ Storage Servers When the synchronization completes Recovery Manager creates a virtual copy on the remote secondary InServ Storage Server updates the navigation view and sends notification to the user Periodic Database Synchronization 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 2 Depending on the setup of your database select either Online Hot Backup or Offline Cold Backup and then click Finish After the periodic synchronization process is started the command log view of the Recovery Manager GUI displays a status of started avy
76. cdba_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 The virtual copy s status can be retrieved using the Recovery Manager display utility The same virtual copy cannot be mounted concurrently at different mount points If the database files reside on Veritas VxVM Volumes only one virtual copy per database can be mounted at any time on the backup host This is due to the VxVM disk groups from different virtual copies of the same database having the same names and so cannot be imported at the same time If the database files reside on ASM disk groups it is dependent on which ASM database version is installed on the backup host different restrictions apply as follows Ifthe ASM version on the backup host is 10 2 0 5 or 11 1 0 7 one virtual copy per database can be mounted at any time on the backup host However virtual copies from different databases can be mounted concurrently Ifthe ASM version on the backup host is lower than the releases mentioned in the previous bullet only one virtual copy can be mounted at any time on the backup host This restriction prevents an Oracle ASM instance on the backup host from hanging due to some ASM s idle processes still holding a virtual copy s devices even though
77. completion time varies depending on data changes IO and network traffic Performing Periodic Remote Copy Recovery Manager for Oracle User s Guide 6 Using the Recovery Manager Command Line Interface In this chapter vcdba_backup vcdba_checkconfig vcdba_config vcdba_create vcdba_createdb vcdba_display vcdba_export vcdba_main vcdba_mount vcdba_remove vcdba_removedb vcdba_rmrep vcdba_restore vcdba_rollback 6 3 6 7 6 8 6 12 6 15 6 18 6 20 6 22 6 24 6 27 6 28 6 33 6 30 6 35 Using the Recovery Manager Command Line Interface 6 1 6 2 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 Recovery Manager for Oracle User s Guide COMMAND vcdba_backup SYNTAX vcedba_backup s lt oracle_sid gt p lt primary_host gt t lt timestamp gt o fulll incr cinc v or vcdba_backup s lt oracle_sid gt p lt primary_host gt 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 Off host backup can dramatically reduce performance impact on the database primary host as well as minimize
78. condary remote InServ Storage Server from the backup host using either SSH or RSH lt backup_host gt ssh lt username gt lt ss_name gt 9 6 Verifying Remote Copy Settings Recovery Manager for Oracle User s Guide where e lt username gt is the InServ Storage Server CLI user e lt ss_name gt is the system name of the secondary remote InServ Storage Server which is attached to the backup host e You are note prompted for a password if set up correctly 3 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 0002B3CO3DF2 193 1 1 1 255 255 255 0 1500 1 5 1 ready 0002B3C03E94 194 1 1 1 255 255 255 0 1500 4 Verify the Remote Copy secondary remote groups datafile group and archive log group cli showrcopy groups lt group_name gt where lt group name gt is the name of the Remote Copy group which contains all virtual volumes used by database datafiles NOTE Ensure the group is in the Start state and in Periodic mode 5 Verify the Remote Copy targets clits showrcopy targets lt target_name gt Verifying Remote Copy Settings 9 7 9 8 Recovery Manager for Oracle User s Guide where lt target name gt is the name of the remote target that has been created using creatercopytarget NOTE Ensure the target statu
79. 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 For virtual copies from an ASM managed database based on the different ASM database releases on the backup host the operation is different e 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 e For ASM versions lower than the releases mentioned in the previous bullet if an ASM instance is up on the backup host the mount utility checks if there is any mounted diskgroup If none the ASM instance is shut down otherwise the mount utility gives an error and exits After that a new ASM instance is started up and all diskgroups contained in the current virtual copy are mounted Mounts all snapshot file systems if the database files reside on file systems 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 backup host In addition permission on the 3PAR Recovery Manager Installation and Repository directories must be changed appropriately OPTIONS The following options are supported
80. created for archive log destination only Possible values for the virtual copy status are Available the virtual copy is available to be used Removed the virtual copy has been removed from the InServ Storage Server Mounted the virtual copy has been mounted on the backup host Database the virtual copy is currently used for the cloned database on the backup host The cloned database is up and running Mounted P the virtual copy has been partially mounted there are some errors while mounting the virtual copy You need to either unmount it and remount it or call 3PAR support Possible values for the virtual copy backup status are N The virtual copy has not been backed up Y Full The virtual copy has been backed up as a full backup Y Incr The virtual copy has been backed up as a differential incremental backup e Y Cinc The virtual copy has been backed up as a cumulative incremental backup Managing Virtual Copies 5 3 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 p Catalog must have been created and configured prior to creating the virtual copy To create a virtual copy 1 Onthe 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 3 If you choose to cr
81. ctory for the database files mapping information etc 3par solutions lt primary_host gt ora lt oracle_sid gt config etc 3par solutions lt primary_host gt ora lt oracle_sid gt config_exp sh etc 3par solutions lt primary_host gt ora lt oracle_sid gt gui Recovery Manager Configuration Files 4 49 Recovery Manager for Oracle User s Guide 4 50 Recovery Manager Configuration Files 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 3 Backing Up Virtual Copies 5 7 5 3 1 Performing Immediate Backups 5 7 5 3 2 Performing Automatic Backups 5 8 5 4 Performing Restores 5 9 5 5 Performing Periodic Remote Copy 5 10 Using Recovery Manager from the Menu Driven Application 5 1 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 ae NOTE New features will no longer be added into menu driven applications To start the Recovery Manager menu driven app
82. current backup host to the primary host and the InServ Storage Server then RSH and CLI must also be configured to allow access from the current backup host to the alternate backup host as well as from the alternate backup host to the InServ Storage Server You must run this command as a super user from the backup host To allow the Oracle Database Administrator to run this command an identical Oracle Database Administrator user must exist on alternate backup host In addition permission on the opt 3par vcdbaora directory must be changed appropriately Command Recovery Manager for Oracle User s Guide OPTIONS The following options are supported s lt oracle_sid gt The instance ID of the primary database For an RAC database any instance SID can be specified p lt primary_host gt 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 lt timestamp gt The timestamp of a virtual copy It is also the name of the virtual copy The virtual copy name can be obtained using the vcdba_display command r lt alt_host gt The alternate backup host name 1 lt alt_tpd_hostname gt The TPD hostname is the hostname defined on the InServ Storage Server which represents the alternate backup host The showhost command lists all available TPD host names e alt_tpdpwfile alt_tpdusername
83. cy menu from the Virtual Copies pull down menu 3 Enter the maximum number of virtual copies to be kept in the text field 4 If you want to remove the oldest virtual copy select Remove the oldest Virtual Copy If you want to keep the oldest virtual copy select Retain the oldest Virtual Copy option Remove the oldest Virtual Copy If the maximum number of virtual copies is reached the oldest virtual copy is removed before a new virtual copy is created Retain the oldest Virtual Copy If the maximum number of virtual copies is reached the oldest virtual copy is retained and a new virtual copy is created 5 Click Finish mm NOTE The virtual copy policy is effective immediately 7 6 3 Refreshing Virtual Copy Information You can update virtual copy information that includes Backup Type Backup Key Mount point and Virtual Volume State If a new virtual copy is created outside of the Recovery Manager GUI the virtual copy is added to the navigation view 1 Select Virtual Copy Management from the navigation view 2 Select Refresh from the Virtual Copies pull down menu NOTE The refresh process begins immediately It takes a few minutes depending p on the number of virtual copies in the Recovery Manager repository Using Virtual Copies 7 5 7 6 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 i
84. d for a configuration file which you should have already created see 4 9 Recovery Manager Configuration Files on page 4 27 5 3 2 Performing Automatic Backups If you have created a NetBackup policy and a configuration file for a database instance NetBackup triggers a backup automatically NOTE When you configure a NetBackup policy to trigger automatic backups you must specify a backup window for each schedule in each policy NOTE If an Egenera server is used as a backup host Recovery Manager does not support automatic backup Backing Up Virtual Copies 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 a ternate restore NetBackup requires that a file name of usr openv netbackup db altnames lt database_hostname gt exist on the NetBackup master server For example if you want to restore a backup image to a database server named pilot create an empty file named pilot in usr openv netbackup db altnames on the NetBackup master server 5 4 1 Performing Restores NOTE Restore is not supported on Remote Copy configuration To perform a restore using the menu driven application 1 On the 3PAR Recovery Manager for Oracle main menu select option 4 Re
85. database down time or the time database in backup mode during backup The first form of vcdba_backup command initiates an immediate backup of an existing database virtual copy The virtual copy must have Available status not mounted in order to be backed up The vcdba_backup command mounts the virtual copy to the backup host before initiating an immediate backup off host The second form of vcdba_backup command creates a new database virtual copy mounts it to the backup host before initiating an immediate backup off host Recovery Manager supports NBU user managed backup and Oracle RMAN back up methods which can be specified during the Recovery Manager configuration process For the Oracle RMAN backup method you can select the SBT_TAPE or DISK option to backup to tape or disk respectively Regardless of backup method Recovery Manager supports full backup of an Oracle database or archive log destination However incremental differential or cumulative backup of the whole Oracle database is only available for Oracle RMAN backup method Incremental differential or cumulative backup of archive log destination is only available for NBU User managed backup method Backup is not supported on Remote Copy configuration The following are restrictions and automated scripts that are generated when configuring Recovery Manager The automated scripts will be executed while the vcdba_backup command is running COMMAND 6 3 6 4 Recover
86. defined on the storage server d Enter full path of 3PAR InServ password file 1 Provide the 3PAR password file location for the alternate backup host if the current connection method between backup host and the server is using RSH 2 Provide the InServ Storage Server s user name if the current connection method between backup host and the InServ Storage Server is using the SSH method 5 2 7 Removing a Virtual Copy s Repository To remove a virtual copy repository 1 Onthe Virtual Copy Management menu screen select option 7 Remove Virtual Copy Repository 2 Select the virtual copy repository to remove NOTE Only a virtual copy that has Removed status can be specified 5 2 8 Setting Virtual Copy Policy To set the virtual copy policy 1 Onthe Virtual Copy Management menu screen select option 8 Virtual Copy Policy 2 When prompted enter the maximum number of virtual copies to be maintained at any time The maximum allowed virtual copy number is 500 3 The application now asks you if you want to remove the oldest virtual copy when the maximum number of virtual copies is reached Enter y or n 5 6 Managing Virtual Copies 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
87. der to create an online virtual copy datafile only virtual copy or archive log only virtual copy Datafiles and archive logs must reside on separate 3PAR virtual volumes The online redo logs and control files should not reside on the virtual volumes used by the datafiles and archive logs to avoid being rolled back along with datafiles and archive logs virtual volumes However the online redo logs and control files can share the same 3PAR virtual volumes If the database files reside on Veritas VxVM volumes datafiles and archive logs must reside on separate VxVM disk groups The online redo logs and control files should reside on separate VxVM volumes used by the datafiles and archive logs If the Oracle database is an ASM managed database the datafiles and archive logs must reside on separate ASM disk groups The online redo logs and control files should not reside on the same ASM disk groups used by the datafiles and archive logs to avoid being restored when using the Recovery Manager Rollback feature ASM disk groups should not be shared between different databases If the database is an RAC database all RAC instances must share the same archive log destinations same cluster file systems or same ASM disk groups Interacting with Oracle 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
88. e 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 The virtual copy is removed from the virtual copy management list 7 6 7 Backing up a Virtual Copy If a virtual copy is in the Available state it can be backed up If a virtual copy is in the Mounted or Database state the virtual copy needs to be to unmounted prior to being backed up To backup a virtual copy 1 Right click the virtual copy to be backed up to media 2 Click Backup to Media 3 Click Finish 4 Click OK 7 6 8 Removing a Virtual Copy Repository Normally when the virtual copy is removed the repository is deleted However if you have already backed up the repository is not automatically removed It is kept to apply the restore operations when necessary After the virtual copy repository is removed all information related to this virtual copy set is lost 1 Right click the virtual copy name to be removed from the entire repository Using Virtual Copies 7 7 7 8 Recovery Manager for Oracle User s Guide 2 Click Remove Virtual Copy Repository 3
89. e Recovery Catalog 10 MB 4 24 Setting Up NetBackup Policies for Oracle RMAN Backup Recovery Manager for Oracle User s Guide 2 Create a tablespace for the Recovery Catalog as follows S export ORACLE_SID lt catdb gt export ORACLE_HOME lt oracle_home gt sqlplus as sysdba SQL gt create tablespace lt cat_tbs gt datafile lt path filename gt size 10M SQL gt exit where e lt catdb gt is the Oracle Instance ID of the Recovery Catalog e lt cat_tbs gt is the Recovery Catalog tablespace name lt path filename gt is the file path where the datafile is created 3 Create a user for the Recovery Catalog as follows sqlplus as sysdba SQL gt create user lt rman_user gt identified by lt rman_password gt temporary tablespace temp default tablespace lt cat_tbs gt quota unlimited on lt cat_tbs gt SQL gt grant connect resource recovery_catalog_owner to lt rman_user gt where e lt tbs_name gt is the tablespace name of the Recovery Catalog e lt rman_user gt is the user name to be granted access permission to the Recovery Catalog lt rman_password gt is the password for the lt rman_user gt 4 Create the RMAN Recovery Catalog tables as follows rman catalog lt rman_user gt lt rman_password gt lt catdb gt RMAN gt create catalog tablespace lt cat_tbs gt Setting Up NetBackup Policies for Oracle RMAN Backup 4 2
90. e configured to perform either NBU user managed backup or Oracle RMAN backup See 4 9 Recovery Manager Configuration Files on page 4 27 for details 2 10 1 The Database Backup Utility 3PAR Recovery Manager s database backup utility supports full and or incremental backup of an Oracle database or archive log destination Full backup of an Oracle database or archive log destination are always supported regardless of backup method NBU backup or Oracle RMAN backup However incremental differential or cumulative backup of a whole Oracle database is only available using Oracle RMAN backup Incremental differential or cumulative backup of archive log destination is only available for the NBU user managed backup method Recovery Manager and Third Party Backup Tools 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 Atleast 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 Oracle RMAN backup If RMAN sbt_tape backup is chosen the NBU for Oracle client must be installed on the backup host as well as on the primary host If RMAN sbt_tape backup is chosen a
91. e 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 vedba_rman_archbackup sh to backup the cloned database Removes the cloned database Un mounts the virtual copy vcdba_rman_archbackup sh are generated at etc 3par solutions NOTE The RMAN backup scripts vcdba_rman_dbbackup sh and lt primary_host gt ora lt oracle_sid gt during the creation of the Recovery Manager Configuration file 2 10 1 2 Automatic Backup During an automatic backup NBU initiates a backup process on the NBU client the backup host For an NBU user managed backup The NBU client executes the bpstart_notify lt policy_name gt script The bpstart_notify script creates a virtual copy of the database or archive log destination mounts it on the backup host then generates the include list in the usr openv netbackup include_list lt policy_name gt file which contains a list of files on the virtual copy for backup Once the backup process is completed the NBU client executes the bpend_notify lt policy_name gt script to perform virtual copy cleanup Recovery Manager and Third Party Backup Tools 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 defau
92. eate a virtual copy for the database enter o online or f offline to create an online or offline virtual copy creating the virtual copy If you try to create an offline virtual copy with the NOTE If a virtual copy is created offline the database must be shut down prior to database running you will get an error 5 2 3 Removing a Virtual Copy To remove a virtual copy 1 Onthe Virtual Copy Management menu screen select option 3 Remove Virtual Copy 2 Onthe Remove Virtual Copy menu select the virtual copy to remove e The virtual copy removal utility only removes the actual virtual copy It does not remove the repository information for restoration purpose in the case that the virtual copy is not backed up the repository will be removed as well If the repository still remains and the virtual copy is backed up to media before being removed you can still restore to that point in time virtual copy from the backup image e The status of the virtual copy shows Removed after the virtual copy is removed 5 4 Managing Virtual Copies 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 Select the virtual copy to be mounted e 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
93. ed concurrently at different mount points m If the database files reside on Veritas VxVM Volumes only one virtual copy per database can be mounted at any time on the backup host This is due to the VxVM disk groups from different virtual copies of the same database having the same names and so cannot be imported at the same time m If the database files reside on ASM disk groups it is dependent on which ASM database version is installed on the backup host different restrictions apply as follows e Ifthe ASM versoin on the backup host is 10 2 0 5 or 11 1 0 7 one virtual copy per database can be mounted on the backup host Virtual copies from different databases can be mounted concurrently e Ifthe ASM vesrion on the backup host is running versions lower than the releases mentioned in the previous bullet only one virtual copy can be mounted at any time on the backup host This restriction prevents an Oracle ASM instance on the backup host from hanging due to some ASM s idle processes still holding a virtual copy s devices even though the corresponding ASM disk groups are dropped m If the database files reside on OCFS2 file systems only one virtual copy per database can be mounted at any time on the backup host 6 24 Command 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
94. ed for variables in file root lt systemID names paths and screen nodeID gt root Typographical Conventions output and variables in user input To continue Enter your System nance gt lt systemname gt 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 Yv 2 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 WARNING Warnings alert you to actions that can cause injury to people or irreversible damage to data or the operating system Advisories 1 5 Recovery Manager for Oracle User s Guide 1 6 Advisories Recovery Manager for Oracle User s Guide r 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 4 The Virtual Copy Mount Utility 2 10 2 6 5 The Virtual Copy Unmount Utility 2 11 2 6 6
95. ems 3 4 installation of Recovery Manager verifying 3 7 installing 3 2 installing on primary server 3 7 installing Recovery Manager on Solaris systems 3 6 L limitations of space for Recovery Manager 2 5 location of command line utilities 6 2 manual pages setup 4 19 menu driven backup host 4 27 menu driven application performing immediate backups from 5 7 performing restores from 5 9 starting 5 2 modifying configuration files 7 3 mount utility 2 10 mounting virtual copies 5 5 6 24 7 6 Index national language support setup 4 18 NBU parameters setting up 4 21 NBU policies for Oracle RMAN backup 4 22 NBU policy setup 4 19 NetBackup 2 6 4 5 used with Recovery Manager 2 6 NetBackup RSH connection 4 5 notes defined 1 5 0 off host backup 2 16 Oracle RMAN 2 6 used with Recovery Manager 2 6 Oracle interacting with Recovery Manager 2 4 organization of this guide 1 3 P periodic database synchronization 7 10 periodic Remote Copy 5 10 pkgadd command 3 7 pkginfo command 3 8 pkgrm command 3 9 preinstallation requirements 3 2 primary server and InServ RSH connection 4 6 primary server installation 3 7 primary server RSH connection 4 4 Recovery Manager CLI 6 2 configuration files 4 27 deinstallation from Solaris systems 3 9 GUI 7 2 installation on Linux systems 3 4 installation on Solaris systems 3 6 installing preinstallation requirements 3 2 interacting with Veritas NetBackup 2 6 removing from Linux sys
96. er managed restoration the command can also be used to restore an alternate location Oracle RMAN always restores to the primary host If a virtual copy s name is not specified the vcdba_restore command restores from the most recent full back up Restore is not supported on Remote Copy Configuration Restore is not supported on Remote Copy configuration The following restrictions apply when restoring from a virtual copy s backup image m When restoring the database control file using the c option using Oracle RMAN the database must be in STARTED mode startup nomount In addition restoring the database control file along with an individual data file or tablespace is not supported as it is not possible to perform media recovery When restoring a database the database must be in CLOSED or MOUNTED mode for NBU restore or Oracle RMAN restore respectively For an RAC database all RAC instances must be in CLOSED or MOUNTED mode respectively m When restoring individual tablespaces or datafiles the database can be OPEN but the corresponding tablespaces must be offline Restoring controlfiles along with datafiles and or tablespaces is not allowed 6 30 Command 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 lt database_hostname gt must be c
97. ered Backup Schedule 1 Create two schedules one for full backup and one for incremental backup optional For the incremental backup schedule you can create either a differential incremental or cumulative incremental backup schedule 2 If you wish to perform immediate archive log backup initiated from Recovery Manager set the backup window to 0 3 If you also wish to perform automatic archive log 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 host as the backup process will actually take place on the backup host 4 7 3 Setting Up NetBackup Configuration Parameters For Recovery Manager to perform backups correctly the following parameters in the usr openv netbackup bp conf file must be changed on the backup host NBU client If a virtual hostname is used on the primary host for cluster purposes the CLIENT_NAME must be specified inthe bp conf file for the virtual hostname in order for the Recovery Manager restoration utilitiy to function properly em USE_CTIME FOR_INCREMENTAL BPSTART_TIMEOUT 600 BPEND_TIMEOUT 600 CLIENT_NAME lt virtual_hostname gt Setting Up NetBackup Policies for NBU User Managed Backup 4 21 4 22 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 NetBacku
98. ery Manager GUI so that the most current information is displayed gt To refresh Remote Copy information right click the Remote Copy node on which synchronization was performed and click Refresh Periodic Database Synchronization 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 7 Recovery Manager provides a way to rollback a database to a point in time stage with a read only or read write virtual copy The rollback utility requires the data volumes be offline without being exported to any giving host Therefore it is very important to keep the original volume numbers from being reused by other volumes Recovery Manager uses them for creating LUNs and exporting them to the original host with the same set of volume numbers Using the Recovery Manager Rollback Utility 8 1 8 2 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
99. es are put in backup mode before the virtual copy is created After the virtual copy creation is completed tablespaces are taken out of backup mode Offline Cold backup The involved database instance must be down for this operation Backup datafile only The involved database instance must be up for this operation All tablespaces are put in backup mode before the virtual copy is created After the virtual copy creation is completed tablespaces are taken out of backup mode This backup only takes a virtual copy for all datafiles not archive log destination 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 You may want to create separate virtual copies using the o archon1ly option Backup Archive Log Dest Only The involved database instance must be up for this operation The database is forced to switch logs before a virtual copy of archive logs is created 4 Click Finish Using Virtual Copies 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 Poli
100. figuration NOTE Before using this utility ensure that all 3PAR Recovery Manager gt requirements are met the Remote Copy licenses are installed on both the primary local InServ Storage Server and the secondary remote InServ Storage Server and Remote Copy is properly configured on both InServ Storage Servers 9 2 1 Recovery Manager s Remote Copy Requirements Before using the Recovery Manager Remote Copy utility the following must be set up m Primary local and secondary remote InServ Storage Servers must be correctly configured m Links among nodes within two InServ Storage Servers must be set up and targets related to the two InServ Storage Servers must be created System Configuration 9 3 9 4 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 only supports periodic synchronization and requires the period value set to zero for the involved Remote Copy group If volume manager is being used all volumes that are in the same disk group as the datafiles or archive log destinations must
101. for details on how to use Oracle RMAN for 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 backup host In addition permission on the 3PAR Recovery Manager Installation and Repository directories must be changed appropriately Command 6 31 6 32 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 Command s lt oracle_sid gt The instance SID of the primary database For an RAC database any instance SID can be specified p lt primary_host gt 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 lt timestamp gt The timestamp of a virtual copy whose backup image is used for restoration Use the vcdba_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 lt tablespaces gt The tablespace s that need to be restored Use commas to separate multiple tablespace names D lt datafiles gt The datafile s that need to be restored Use commas to separate multiple datafiles
102. g the virtual copy on the backup host you may skip it NOTE RMAN backup requires the cloned database in mounted status Therefore p ORACLE_HOME must be installed on the backup host 4 28 Recovery Manager Configuration Files 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 Enter ORACLE_HOME of ASM instance on the backup server h help q quit Recovery Manager assumes that the ORACLE_HOME of the ASM instance on the backup host is the same as the ORACLE_HOME on the primary host 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 help q quit The Oracle parameter file can be either a pfile or an spfile Recovery Manager recommends that an 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 Press ENTER to accept default value or enter a co
103. g up NBU policies 4 19 setting up RSH CLI connections 4 3 setting up SSH 4 9 Index from backup to InServ server 4 14 from backup to NBU master server 4 13 from backup to primary server 4 12 from primary to InServ server 4 16 space limitations of Recovery Manager 2 5 SQL Plus 2 4 SSH 4 2 generating key pair for the primary server 4 11 modifying daemon configuration 4 10 SSH connection for Remote Copy 4 10 SSH connection relationship 4 9 SSH key pair 4 11 SSH key pair generation 4 11 SSH restrictions 4 10 SSH setup 4 9 SSH setup from the backup to InServ server 4 14 SSH setup from the backup to NBU master server 4 13 SSH setup from the backup to primary server 4 12 SSH setup from the primary to InServ server 4 16 starting the GUI 7 2 starting the menu driven application 5 2 stopping the GUI 7 2 T third party backup tools 2 16 typographical conventions 1 4 U unmount utility 2 11 unmounting virtual copies 5 5 6 39 7 6 utilities 2 7 clone 2 12 cloned database removal 2 14 database backup 2 16 database configuration 2 7 database restore 2 20 database rollback 2 15 display 2 9 export 2 12 mount 2 10 unmount 2 11 virtual copy creation 2 7 virtual copy removal 2 14 virtual copy repository removal 2 14 IX 4 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_roll
104. groups contained in the current virtual copy are mounted 2 6 5 The Virtual Copy Unmount Utility 3PAR Recovery Manager s virtual copy unmount utility vcdba_umount unmounts the file system where a virtual copy is currently mounted The read write virtual copy is removed as well as any components that were created during the mount virtual copy stage The virtual copy must have Mounted or Mounted P status in order to be unmounted The status of a virtual copy can be obtained using a display utility such as the vcdba_display command Unmounting a database virtual copy involves the following actions Foran ASM managed database if the ASM database on the backup host has a version at or above 10 2 0 5 or 11 1 0 7 unmounting the virtual copy drops the ASM diskgroups that are contained in the virtual copy and cleans up the ASM disks m If the ASM database on the backup host has versions lower than those listed in the previous bullet unmounting shuts down the ASM instance and cleans up ASM disks Unmounts all snapshot file systems if the database files reside on file systems Destroys all snapshot VxVM disk groups and their VxVM volumes if the database files reside on VxVM volumes Deports the read write virtual copy from the backup host m Removes the read write virtual copy Recovery Manager Utilities 2 11 2 12 Recovery Manager for Oracle User s Guide 2 6 6 The Virtual Copy Export Utility 3PAR Recovery Manager s vi
105. h 3PAR Remote Copy support Primary Backup Veritas Host Host NetBackup Master Server RSH RSH Root User Root User Root User CLI CLI Connection Connection Recovery Manager User InServ Storage Server Figure 4 1 RSH CLI Connection Relationship Setting up RSH CLI Connections for Recovery Manager 4 3 Recovery Manager for Oracle User s Guide Primary Local Backup Remote Host Host RSH q Root User Root User CLI CLI Connection Connection Recovery Recovery Manager User Manager User Primary Local Secondary Remote InServ Storage InServ Storage Server Server Figure 4 2 RSH CLI Connection Relationship for Remote Copy Support 4 2 1 Setting Up an RSH Connection from the Backup Host to the Primary Host To set up an RSH connection from the backup host to the primary host 1 Log in to the primary host as the root or Oracle user 2 Modify or create the rhosts file to contain the following lines lt backup_host gt lt user gt where lt backup_host gt is the host name of the backup host e lt user gt is the root user name on the backup host 4 2 2 Verifying the RSH Connection from the Backup Host to the Primary Host From the backup host verify the RSH connection to the primary host as follows 1 On the backup host login in as the root or Oracle user as you logged in during set up 4 4 Setting up RSH
106. han the primary database when creating a clone database Otherwise the extra redo log multiplex location will be ignored 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 This option is equivalent to o binary recovery This option is deprecated and will be removed in the future release o recovery Automatically recover the clone database using all available archivelogs that exist on the virtual copy o norecovery Startup the clone database in mounted mode without recovery v Runs the command in verbose mode to display useful messages Command 6 17 6 18 Recovery Manager for Oracle User s Guide COMMAND vcdba_display SYNOPSIS vcdba_display s lt oracle_sid gt p lt primary_host gt t lt timestamp gt 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 m Online
107. have been configured for root user as Veritas NetBackup always initiates a backup as root user If the virtual copy is to be backed up using Oracle RMAN a Recovery Catalog must have been created and configured prior to using the backup utility Recovery Manager and Third Party Backup Tools 2 19 2 20 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 The virtual copy must have a backup status of Y in order to be restored The virtual copy s backup status can be retrieved using the Recovery Manager display utility see 2 6 3 The Virtual Copy Display Utility on page 2 9 The Recovery Manager restore utility can also be used to restore a virtual copy s backup image to an alternate server For an NBU user managed restoration the restore utility can also be used to restore to an alternate location The following restrictions apply when restoring from a virtual copy s backup image m When restoring the database control file using the c option using Oracle RMAN the database must be in STARTED mode startup nomount In addition
108. his question if you previously selected Oracle RMAN as the third party backup tool Enter the number of RMAN channels to be allocated for backup Enter NetBackup master server name h help q quit Recovery Manager Configuration Files 4 31 4 32 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 Enter a schedule name for the policy that is used to perform full database backup Enter NetBackup policy name for archivelog backup h q A separate Veritas NetBackup policy must have been created for archive log back up if you want to perform back up of archive logs only Enter the archive log backup policy or press ENTER if you do not want to perform archive log back up Enter NetBackup full schedule name for archivelog 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 Enter a schedule name of type full for the policy that is used to perform archive log backup Enter NetBackup incremental schedule name for archivel
109. ile and archive log virtual volumes Virtual Copy Policy 2 15 2 16 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 m 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 After a rollback you may need to restore the control file in order to perform database recovery 2 10 Recovery Manager and Third Party Backup Tools 3PAR Recovery Manager integrates 3PAR Virtual Copy with Veritas NetBackup NBU and or Oracle RMAN to perform off host backup Off host backups can dramatically reduce performance impact on the primary host and minimize database down time or database in backup mode during backup Recovery Manager creates a virtual copy snapshot of the database mounts it to the backup host then performs backup of the virtual copy Recovery Manager supports online hot offline cold datafile or archive log backups Online backup A database backup while it is OPEN a Offline backup A database backup while it is CLOSED Datafile backup A backup of datafiles only Archive log backup A backup of archive logs only Recovery Manager can b
110. imary 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 2 Rollback with Read Write Virtual Copies The difference between a read only and a read write virtual copy depends on whether the read write virtual copy has been exported and if any I O operations have been applied on the copy or not For a cloned database on the backup host you need to perform log switches until all online redo logs are switched to archive log files The cloned database must then be shut down All file systems used by the cloned database have to be manually unmounted and remain offline with the umount and removevlun commands NOTE Be sure to manually unmount the file systems used by the cloned database on the backup host Do not use the vcdba_umount utility which not only unmounts the file systems but also removes the read write virtual copy from the InServ system In addition to performing the 8 2 1 Rollback with Read Only Virtual Copies on page 8 2 use the w option to specify read write virtual copy in step 3 in 8 2 7 Rollback with Read Only Virtual Copies on page 8 2 Database Volumes Not Under Veritas VxVM Control 8 3 Recovery Manager for Oracle User s Guide 8 3 Database Volumes Under Veritas VxVM Control If any of the database
111. installing Recovery Manager describes how to install verify and deinstall Recovery Manager for Oracle Chapter 4 Configuring Recovery Manager describes the steps for configuring Recovery Manager Chapter 5 Using Recovery Manager from the Menu Driven Application provides an overview and instructions on using 3PAR Recovery Manager s menu driven application Chapter 6 Using the Recovery Manager Command Line Interface introduces 3PAR Recovery Manager s command line interface and its commands Chapter 7 Using the Recovery Manager Graphical User Interface describes 3PAR Recovery Manager s Graphical User Interface Chapter 8 Using the Recovery Manager Rollback Utility describes how to use 3PAR Recovery Manager s rollback utility Chapter 9 Using Remote Copy with Recovery Manager provides an overview of how to use 3PAR Recovery Manager with 3PAR Remote Copy This guide also contains an index and revision history for reference Organization 1 3 1 4 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 Found lt 12 gt 73G disks and screen output and for Enter cli at the Windows text you are to enter command prompt lt ABCDabcd gt Us
112. irtual Volumes Command Start Time Console Configuration About a Recovery Manager o B oracy Servers g gt Sunti k 02 o amp sunen Ga wow conan ap i Datafiles Archive Log virtual Volumes y Manager sunt1k 01 Name INONRAC11 Command Description Start Time Status Recovery Manager Configuration Files Recovery Manager for Oracle User s Guide The Host and Database Properties screens appear Configure Recovery Manager Properties Host and Database Properties Please fill in the field carefully incorrect values will prevent Recovery Manager from functioning correctly Host Information Primary Local Host Name suntik 02 Backup Remote Host Name suntik 02 Remote Shell options Remote Copy options Remote shell rsh C Remote Copy Secure shell ssh Database Related Parameters Database ID NONRAC11 7 Database Owner asm Configure Recovery Manager Properties Host ind Database Properties Please fill in the field carefully incorrect values will prevent Recovery Manager from functioning correctly Location Related Parameters Database Home jforacle_base ora product 11 1 0 asm ASM Home jforacle_base ora product 11 1 0 asm Parameter File full path NONRAC_DATASnonrac1 1 spfilenanrac11 ora Password File if any full path oracle_base ora product 11 1 O asmidbs orapwNONRA
113. is stored at etc 3par solutions lt primary_host gt ora lt oracle_sid gt config An equivalent environment file is also created for each configuration file It contains all configuration options that are specified in the configuration file Recovery Manager uses the environment file for its operations The environment file is also stored at the same location as the configuration file etc 3par solutions lt primary_host gt ora lt oracle_sid gt config_exp sh If a configuration file of a database instance exists it is overwritten The permission of the configuration file is set to the user that created the file 2 6 2 The Virtual Copy Creation Utility 3PAR Recovery Manager s create utility creates an online offline datafile or archive log virtual copy of an Oracle database vcdba_create command 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 datafile virtual copy A point in time snapshot image of the datafiles of a database while the it is online OPEN A datafile virtual copy alone cannot be used for recovery without the archive logs generated up to the point when the virtual copy is taken It is assumed that the user is responsible for making sure all required archive logs exist Recovery Manager Util
114. ities 2 7 2 8 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 An archive log virtual copy can be used in conjunction with online or offline virtual copy to simulate an incremental backup If Recovery Manager is configured to use Oracle RMAN for backup an RMAN Recovery Catalog must have been created and configured prior to running the create utility The Recovery Manager create utility performs Recovery Catalog synchronization during the virtual copy creation process When creating an online virtual copy the create utility performs the following actions Discovers devices 3PAR virtual volumes used by the datafiles and archive log destination m Puts all tablespaces in backup mode Creates a virtual copy for the datafile virtual volumes Takes all tablespaces out of backup mode Switches online redo logs and archives them to archive log destination 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 An off
115. kup host This parameter is required T if RSH is specified as remote shell VCDBA_MAXVC The maximum number 500 of the database virtual copies allowed at any time VCDBA_RM_OLDVC The flag indicates if an oldest virtual copy should be removed before creating a new virtual copy when the number of virtual copies exceeds the maximum allowed LDATAGROUP The name of the Remote Copy group which contains Oracle datafile volumes on the primary local InServ Storage Server COMMAND 6 9 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 LTARG InForm CLI showrcopy target command to get the target name The target group name on the primary local InServ Storage Server Use the E T RTARGET The target group name on the secondary remote InServ Storage Server Use the InForm CLI showrcopy target command to get the target name BACKTOOL The backup method to be used for backing up a database virtual copy snapshot The two backup methods currently supported by 3PAR Recovery Manager are NBU backup and RMAN backup If the specified database is an ASM managed database the only supported backup method is RMAN backup
116. letely installed FILES 106 installed pathnames 7 shared pathnames 21 directories 50 executables 4 setuid setgid executables 166294 blocks used approx 3 After the installation is complete on the primary and backup hosts you can allow Oracle users and Database Administrators group access to the Recovery Manager commands and utilities by changing the owner and permissions of the following directories required for Oracle users opt 3par vcdbaora etc 3par solutions e etc 3par solutions log e etc 3par solutions lock e etc 3par solutions lt primary_host gt ora lt oracle_sid gt a Change the owner of the Recovery Manager utilities and repository as follows where the Database Administrator user name is lt user gt and the group name is lt group gt chown chown chown chown lt user gt lt user gt lt user gt lt user gt lt group gt opt 3par vcdbaora lt group gt etc 3par solutions lt group gt etc 3par solutions log lt group gt etc 3par solutions lock Installing Recovery Manager on Solaris Systems 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 Ifthe etc 3par solutions lt primary_host gt ora lt oracle_sid gt directory exists you must also change the owner and permission as follows chown R lt user gt lt group
117. lication lt backup_host gt opt 3par vcdbaora bin vcdba_main NOTE Refer to 4 9 1 1 Creating Configuration Files using the Menu Driven Application or the Command Line Interface on the Backup Host on page 4 27 for instructions on creating a configuration file using the menu driven application 5 2 Managing Virtual Copies Recovery Manager for Oracle provides tools to manage the virtual copies The tools allow for creating displaying removing mounting and unmounting virtual copies To manage virtual copies from the menu driven application 1 On the 3PAR Recovery Manager for Oracle main menu select option 2 Virtual Copy Management 2 Select a primary host and database configuration with which you wish to work The Virtual Copy Management menu screen appears 5 2 Starting the Menu Driven Application 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 Select the virtual copy to display Possible values for the virtual copy type are e 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 e Offline virtual copy is created while the database is down It is a cold backup Datafile virtual copy is created for data files only while the database is open Archlog virtual copy is
118. line virtual copy is created while the database is CLOSED The create utility will perform the following actions Starts up the database in MOUNTED mode to retrieve list of datafiles and shuts down the database Discovers devices 3PAR virtual volumes used by the datafiles Creates a virtual copy for the datafile virtual volumes An archive log virtual copy is created while the database is OPEN and performs the following actions Discovers devices 3PAR virtual volumes used by the archive log destination Switches logs and archives online redo logs to archive log destination Recovery Manager Utilities 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 Catalog must have been created and configured prior to running this utility For gt NOTE If the virtual copy is to be backed up using Oracle RMAN a Recovery 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 6 3 The Virtual Copy Display Utility 3PAR Recovery Manager s display utility vcdba_display 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 D
119. lso saved in the Recovery Manager repository along with the backup image information for each virtual copy created The Recovery Manager repository is located in the following directory on the backup host etc 3par solutions lt primary_host gt ora lt oracle_sid gt where lt primary_host gt is the host name of the primary host lt oracle_sid gt is the database ID The following example displays the location of the Recovery Manager repository on the backup host for Oracle database instance test that is running on primary host Host1 etc 3par solutions Hostl ora test If the database is a Real Application Cluster RAC database there will be multiple repositories one for each RAC instance About the Recovery Manager Repository 2 3 2 4 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 In order to create a consistent virtual copy of an Oracle database the database structure must satisfy the following requirements The database must be running in archive log mode and automatic archiving must be enabled in or
120. lt 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 For an Oracle RMAN backup The NBU client executes the backup script vcdba_nbu_dbbackup sh or vcdba_nbu_archbackup sh which must be specified in the Backup Selection List of the NBU policy The backup script creates a virtual copy of the database or archive log destination mounts it on the backup host starts up a cloned database in MOUNTED mode then calls the RMAN backup scripts vcdba_rman_dbbackup sh or vcdba_rman_archbackup sh to backup the cloned database NOTE The backup scripts vcdba_nbu_dbbackup sh and vcdba_nbu_archbackup sh and the RMAN backup scripts vcdba_rman_dbbackup sh and vcdba_rman_archbackup sh are generated at etc 3par solutions lt primary_server gt ora lt oracle_sid gt during the creation of the Recovery Manager Configuration file By default the vcdba_nbu_dbbackup sh 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 put in MOUNTED mode for offline backup NOTE To perform automatic backup RSH or SSH must
121. m 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 The fully functional single instance database can be used for any off host processing purpose The clone database that is started in MOUNTED mode can only be used for RMAN backup The virtual copy used for cloning a database must be either an online or offline virtual copy created using the online or offline option respectively The virtual copy must have been mounted prior to running this command You can create a clone database using an ascii or binary controlfile which was saved in the Recovery Manager repository at the time the virtual copy was created Using an ascii controlfile is more flexible as it allows to change database instance name as well as the structure of the database When using an ascii controlfile the structure of the clone database is not required to be exactly the same as the structure of the primary original database Therefore the virtual copy can be mounted at any mount point However since the virtual copy does not contains online redo logs and control files their locations can be specified using d option can be one or more directories or ASM diskgroups depends on desired multiplexing If the locations of the redologs and controlfiles are not specified they are created at the repository location for the virtual copy etc 3par solutions lt ho
122. mes Command Description Start Time Status fy Command Log fas ate Ss The Host and Database Properties screen appears Host and Database Properties Please fill in the field carefully incorrect values will prevent Recovery Manager from functioning correctly Host Information PrimaryiLocal Host Name _ sunttk 02 Backup Remote Host Name sunttk 02 Remote Shell options Remote Copy options Remote shell rsh Remote Copy Secure shell ssh Database Related Parameters Database ID NONRAC11 x Database Owner lasm Recovery Manager Configuration Files 4 45 Recovery Manager for Oracle User s Guide Host and Database Properties Please fill in the field carefully incorrect values will prevent Recovery Manager from functioning correctly Location Related Parameters Database Home joracle_base ora product 11 1 0 db ASM Home oracle_base ora product 11 1 0 asm Parameter File full path ASM11G_ARCH asm11g spfilenonract1 ora Password File if any full path oracle_base ora product 11 1 Olasm dbs orapwNONRAC11 Backup Server Location Related Parameters Database Home on Backup Server oracle_base ora product 11 1 0 db ASM Home on Backup Server oracle_base oralproduct1 1 0 asm Previous Next Cancel 3 Configure the host information and database related parameters by entering the requested information
123. mmand m t lt timestamp gt The timestamp of a virtual copy that was previously used to create the clone database n lt clone_sid gt The instance ID of the cloned database to be removed If the clone database uses the same lt oracle_sid gt as the primary lt oracle_sid gt this option can be omitted 6 28 Command Recovery Manager for Oracle User s Guide h lt clone_oracle_home gt The Oracle home directory of the cloned database on the backup host If specified this value is used instead of the value of the ORACL E HOM E_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 29 Recovery Manager for Oracle User s Guide COMMAND vcdba_restore SYNOPSIS vcdba_restore s lt oracle_sid gt p lt primary_host gt t lt timestamp gt T lt tablespaces gt D lt datafiles gt 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 The virtual copy s backup status can be retrieved using the vcdba_display command The command can also be used to restore a virtual copy s backup image to an alternate backup host For NBU us
124. nfiguration Files The Recovery Manager Policy screen appears Configure Recovery Manager Properties Recovery Manager Policy Please provide maxium virtual copies you want to keep in inServ Recovery Manager for Oracle User s Guide Maxium virtual copies kept in InServ 500 RAmove the oldest virtual copies if the maxium number is exceeded Remove the oldest virtual copies D Retain the oldest virtual copies Previous Cancel 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 37 4 38 Recovery Manager for Oracle User s Guide The Vendor Backup Product Properties screen appears Configure Vendor Backup Product Properties ifyou choose Veritas NetBackup you must create corresponding policies for NetBackup to use Vendor Backup Product Please Enter NetBackup Related Parameters NBU Binary Location Master Server Name Datafile Policy Name Datafile Policy Full Schedule Name Archive Log Policy Name Archive Log Policy Full Schedule Name Archive Log Policy Incr Schedule Name Jusrfopenvinetbackup C Remove virtual copy from InServ after NBU backup Finish Configure Recovery Manager Properties Vendor Backup
125. nstance on the backup host is the same as the ORACLE_HOME of the ASM instance on the primary host Recovery Manager Configuration Files 4 41 4 42 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 Press ENTER to accept default value or enter a correct value for the Oracle parameter file Enter Oracle password file of the database instance h help s skip q quit Recovery Manager provides a default value for the Oracle password file of the specified database instance Press ENTER to accept the default value or enter the Oracle password file of the specified database instance If no password is being used press s to skip it Do you want to setup configuration for remote copy y n q y Select y if this is this configuration is for Remote Copy Enter Primary Local InServ name h help q quit Enter the system name of the primary local InServ Storage Server that is connected to the primary host The InServ Storage Server name can be retrieved from the output of In
126. obtained from the output of the showhost InForm CLI command and may not be the UNIX hostname of the backup host REMOTE_SHELL The remote shell SSH or RSH to be used by 3PAR Recovery Manager to remotely execute commands on the primary host backup host or InServ Storage Server The remote shell must be configured on the primary host backup host and InServ Storage Server prior to running the vcdoa_config command TPDSYSNAME _PRIMARY The 3PAR InServ Storage Server node name which is connected to the primary host TPDSYSNAME _BACKUP The 3PAR InServ Storage Server node name which is connected to the backup host TPDUSERNAME_PRIMARY The 3PAR InServ Storage Server CLI user name to be used to connect to the InServ Storage Server node from the primary host This parameter is required if SSH is specified as remote shell TPDUSERNAME_BACKUP 3PAR InServ Storage Server CLI user name to be used to connect to the InServ Storage Server node from the backup host This parameter is required if SSH is specified as remote shell T TPDPWFILE_PRIMARY 3PAR InServ Storage Server CLI user password file to be used to connect to the InServ Storage Server node from the primary host This parameter is required if RSH is specified as remote shell TPDPWF ILE_BACKUP 3PAR InServ Storage Server CLI user password file to be used to connect to the InServ Storage Server node from the bac
127. og and configure Oracle TNS Service and Listener to allow connecting to the Recovery Catalog from both the primary and backup hosts The Recovery Catalog can be created on any host 3PAR Recovery Manager recommends that the Recovery Catalog is created on the backup host Refer to Oracle documentation for instructions on how to create a Recovery Catalog as well as how to configure Oracle TNS Service and Listener Virtual volume snapshots used by an Oracle database must be mapped to a Common Provisioning Group CPG Refer to the 3PAR InForm OS CLI Administrator s Manual for details about mapping to CPGs If you are upgrading from an earlier version of Recovery Manager you need to uninstall the earlier version of Recovery Manager first as a root user before installing the newer version Refer to 3PAR Implementation Guides for instructions on setting up connections from hosts to the InServ Storage Server and reserving LUNs with specific Host Bus Adapters HBAs Recovery Manager s Remote Copy feature only supports periodic synchronization with 1 to 1 topology To use the Remote Copy feature you must configure your InServ Storage Servers for Remote Copy The InServ Storage Servers must meet the requirements specified in 9 2 1 Recovery Manager s Remote Copy Requirements on page 9 3 For instructions on configuring storage servers for Remote Copy see the 3PAR Remote Copy User s Guide Solaris only If a trusted host connection RSH is to be used
128. og 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 Enter a schedule name of type differential cumulative incremental for the policy that is used to perform archive log backup Recovery Manager Configuration Files 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 If the X11 server is not running issue the following command lt backup host gt xhost b Ensure the DISPLAY environment variable is set lt backup host gt echo S DISPLAY c Start the Recovery Manager GUI lt backup host gt opt 3par vcdbaora bin vcdbagui Recovery Manager Configuration Files 4 33 4 34 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 Console Configuration About st ery Manager 2 oracle Se a cunt New Configuration sunti G Nonract Us ers Copy Management Tablespaces Datafiles Mi archive Log V
129. ogs and control files must not reside on virtual volumes on which data files and archive logs reside If Veritas Volume Manager is used the Oracle data files and archive logs must reside on separate VxVM disk groups Additionally online redo logs and control files must not reside on VxVM disk groups that are used by Oracle data files and archive logs The online redo logs and control files can reside on the same VxVM disk group The primary and backup host must have the same level of operating system patches Veritas volume manager version and maintenance patch If ASM is used to manage an Oracle database Oracle data files and archive logs must reside on different ASM disk groups Additionally online redo logs and control files must not reside on ASM disk groups used by Oracle data files and archive logs The online redo logs and control files can reside on the same ASM disk group Referencing the Support Matrix Recovery Manager for Oracle User s Guide If you are using Veritas NetBackup 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 Additionally you must create an Oracle RMAN Recovery Catal
130. olumes back to their base virtual volumes v Runs the command in verbose mode to display useful messages w Promotes the read write virtual copy instead of the read only virtual copy back to its base The default is to promote the read only virtual copy f Forces the promote operation to proceed even if the parent base volumes are currently in a Remote Copy group as long as the Remote Copy group has not been started If started the promote will fail Recovery Manager for Oracle User s Guide COMMAND vcdba_rsync SYNOPSIS vcedba_rsyne s lt oracle_sid gt p lt primary_host gt 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 Once the synchronization process completes the vcdba_rsync command automatically creates virtual copies of the corresponding virtual volumes on the secondary remote InServ Storage Server and presents itself to the user as one database virtual copy The vcdba_rsync command can be used to perform periodic synchronization for datafile and archive log virtual volumes or datafile virtual volumes In the previous release 3PAR Recovery Manager required that two Remote Copy groups had to be created
131. on backup host h help q quit You will only be prompted with this question if you previously selected RSH as the remote shell Recovery Manager requires that a 3PAR password file must have been created on the backup host to allow access to the Secondary Remote InServ Storage Server from the backup host 4 9 2 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 with Remote Copy support perform the following 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 If the X11 server is not running enter the following command lt backup_host gt xhost b Ensure the DISPLAY environment variable is set lt backup_host gt echo SDISPLAY c Start the Recovery Manager GUI lt backup_host gt opt 3par vcdbaora bin vcdbagui 4 44 Recovery Manager Configuration Files 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 3PAR Recovery Manager Console Configuration About st al Recovery Manager 2 amp Oracle Servers oun sunti ko 2 G NONRAC11 a Virtual Copy Management Tablespaces Datafiles CA Archive Log 3 Virtual Volu
132. opy The virtual copy name can be obtained using the vcdba_display command v Runs the command in verbose mode to display useful messages Command 6 27 Recovery Manager for Oracle User s Guide COMMAND vcdba_removedb SYNOPSIS vcdba_removedb s lt oracle_sid gt p lt primary_host gt t lt timestamp gt n lt clone_sid gt h lt clone_oracle_home gt 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 The virtual copy remains mounted 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 backup host In addition permission on the 3PAR Recovery Manager Installation and Repository directories must be changed appropriately OPTIONS The following options are supported m s lt oracle_sid gt The instance SID of the primary database For an RAC database any instance SID can be specified p lt primary_host gt 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 co
133. opyright Printed Material Copyright 2009 3PAR Inc All rights reserved No part of this publication may be reproduced stored in a retrieval system or transmitted in any form or by any means electronic mechanical photocopying recording or otherwise without the prior written consent of 3PAR Inc 4209 Technology Drive Fremont CA 94538 By way of exception to the foregoing the user may print one copy of electronic material for personal use only Trademarks 3PAR InServ InForm InSpire and Serving Information are registered trademarks of 3PAR Inc Linux is a registered trademark of Linus Torvalds Oracle Oracle9i Oracle10g and Oracle 11g are registered trademarks of Oracle Corporation All other trademarks and registered trademarks are owned by their respective owners Table of Contents 2 Introduction 1 1 1 2 1 3 1 4 1 5 Audience Related Documents Organization Typographical Conventions Advisories Overview of Recovery Manager Operations 2 1 2 2 23 2 4 2 5 2 6 Virtual Copies About the Recovery Manager Repository Interacting with Oracle Interacting with Veritas Volume Manager Interacting with Veritas NetBackup and Oracle RMAN Recovery Manager Utilities 2 6 1 The Database Configuration Utility 2 6 2 The Virtual Copy Creation Utility 2 6 3 The Virtual Copy Display Utility 2 6 4 The Virtual Copy Mount Utility 2 6 5 The Virtual Copy Unmount Utility Recovery Manager for Or
134. or Offline virtual copy Indicates that the virtual copy was created for the database while it was OPEN online or CLOSED offline respectively Datafile virtual copy Indicates that the virtual copy was created for data files only while the database is open Archlog virtual copy Indicates that the virtual copy was created for the archive log destination only A virtual copy s status can be Available Removed Mounted Mounted P or Database Available status indicates that the virtual copy exists and is not currently mounted or cloned Removed status indicates that the virtual copy is removed Mounted status indicates that the virtual copy is currently mounted Mounted P status indicates that the virtual copy is partially mounted Finally the Database status indicates that a database has been cloned using the virtual copy A virtual copy s backup status can be either Y or N where Y indicates that the virtual copy has been backed up and N indicates that the virtual copy has not been backed up 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 backup host In addition permission on the 3PAR Recovery Manager Installation and Repository directories must be changed appropriately OPTIONS The following options are supported Command Recovery Manager for Oracle User s Guide
135. or to using this utility Once exported the virtual copy on the alternate backup host can be mounted umounted backed up and restored Once the exported virtual copy is no longer needed its repository can be removed from the alternate backup host 2 6 7 The Database Cloning Utility 3PAR Recovery Manager s database cloning utility vcdba_createdb command creates a single instance database or starts up a cloned database in MOUNTED mode for backup RMAN purposes A single instance database can be used for any off host processing purpose A cloned database that is started in MOUNTED mode can be used for RMAN backup Recovery Manager Utilities 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 Using an ascii controlfile is more flexible as it allows you to change database instance name as well as the structure of the database When using an ascii controlfile the structure of the clone database is not required to be exactly the same as the structure of the primary original database Therefore the virtual copy can be mounted at any mo
136. ost Skip this step if you wish to use an existing user lt backup_host gt ssh lt adm_user gt lt ss_name gt lt adm_user gt s password lt adm_password gt cli createuser c lt password gt lt username gt all edit In the example above lt adm_user gt is the user name of the InServ Storage Server s administrator lt ss_name gt is the system name of the InServ Storage Server attached to the backup host lt adm_password gt is the administrator s password lt password gt is the password for the InServ Storage Server for the CLI user being created lt username gt is the user being created 4 14 Setting Up SSH Connections for Recovery Manager 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 lt backup_host gt ssh lt username gt lt ss_name gt lt username gt s password lt password gt cli setsshkey Please enter the SSH puplic key below When finished press enter twice Th 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 lt pass the public key here and press Enter twice gt lt public_key gt SSH public key successfully set In the example above e lt username gt is the user being created
137. overy or o norecovery option If recovery is chosen the clone database is open with a reset log otherwise the clone database is in a mounted status Recovery Manager Utilities 2 13 2 14 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 vcedba_createdb command are removed The virtual copy remains mounted 2 6 9 The Virtual Copy Removal Utility 3PAR Recovery Manager s virtual copy removal utility removes an existing virtual copy from the InServ storage system The virtual copy must have Available status in order to be removed using the vcdba_remove command The status of a virtual copy is obtained by using the display utility vcdba_display This utility only removes the read only virtual copy from the system to free up the snapshot space It does not actually remove the repository information if the virtual copy has been backed up to the media This enables Recovery Manager to restore a virtual copy which has been previously backed up to the media on the original volume as long as the virtual copy repository exists 2 7 The Virtual Copy Repository 3PAR Recovery Manage
138. oves 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 If the specified virtual copy has been backed up the actual database virtual copy is removed but its repository remains for database restoration purposes To remove the virtual copy s repository use the vcdba_rmrep command If the virtual copy s repository is removed Recovery Manager will not be able to perform a database restore operation even if the virtual copy has been backed up 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 backup host In addition permission on the 3PAR Recovery Manager Installation and Repository directories must be changed appropriately OPTIONS The following options are supported m s lt oracle_sid gt The instance SID of the primary database For an RAC database any instance SID can be specified p lt primary_host gt 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 lt timestamp gt The timestamp of a virtual copy It is also the name of the virtual c
139. p 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 In addition you must create an Oracle RMAN Recovery Catalog and configure Oracle TNS Service and Listener to allow connections to the Recovery Catalog from both primary and backup host The Recovery Catalog can be created on any server 3PAR Recovery Manager recommends that the Recovery Catalog is created on the backup host See 4 8 3 Creating an RMAN Recovery Catalog on page 4 24 for instructions When perform NBU backup with RMAN Recovery Manager supports full differential and cumulative incremental database backup Recovery Manager also support full archive log backup backup only archive logs Recovery Manager requires that you create a NBU policy for database backup If you wish to perform archive log backup you must create a separate NBU policy for it NOTE This section assumes that you are familiar with Oracle Database and p Veritas NetBackup NBU For more information on how to create NetBackup policy refer to Veritas NetBackup for Oracle documentation Setting Up NetBackup Policies for Oracle RMAN Backup Recovery Manager for Oracle User s Guide 4 8 1 Configuring the NetBackup Policy for Database
140. p host to the authorized_keys file of the NBU master server lt backup_host scp ssh id_rsa pub lt NBU_server gt ssh authorized_keys If the authorized_keys file already exist add the public key to the end of the authorized_keys file 4 3 8 Verifying Connections from the Backup Host to the NetBackup Master Server From the backup host verify the connection to the NetBackup master server as follows NOTE If you are prompted for a password the setup is incorrect and you must p redo the previous setup Setting Up SSH Connections for Recovery Manager 4 13 Recovery Manager for Oracle User s Guide lt backup_host gt ssh root lt NBU_master gt The authenticity of host lt NBU_master gt can t be established DSS key fingerprint is XX XX XXIXXIXXIXXIXXIXXIXXIXXIXXIXXIXIXXIXX Are you sure you want to continue connecting yes no yes Warning Permanently added lt NBU_master gt DSS to the list of known hosts 4 3 9 Setting Up Connections from the Backup Host to the InServ Storage Server Set up an SSH connection from the backup host to the InServ Storage Server as follows 1 Log in to the backup host as root user 2 Make sure the SSH key pair exists as follows lt backup_host gt ls ssh id_rsa id_rsa pub authorized_keys known_hosts 3 Create a CLI user on the InServ Storage Server to be used by 3PAR Recovery Manager to access the InServ Storage Server from the backup h
141. per 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 backup host In addition permission on the 3PAR Recovery Manager Installation and Repository directories must be changed appropriately OPTIONS The following options are supported m s lt oracle_sid gt The instance SID of the primary database For an RAC database any instance SID can be specified p lt primary_host gt 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 lt timestamp gt The timestamp of a virtual copy whose repository is to be removed The virtual copy name can be obtained using vcdba_display command If the lt timestamp gt is not specified the entire repository will be removed Command 6 33 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 m v Runs the command in verbose mode to display a useful messages 6 34 Command Recovery Manager for Oracle User s Guide COMMAND vcdba_rollback SYNOPSIS vcedba_rollback s lt oracle_sid gt p lt primary_host gt t lt timestamp gt o data arch v w f DESCRIPTION Rolls back database volumes from an online virtual copy
142. pilot vxdisk list DE co G2 c2 c2 c2 ore c2 c2 c2 c2 GZ VICE TYPE DISK GROUP STATUS tO0d0s2 sliced error tO0d0s2 sliced disk01 rootdg online t0d41s2 sliced orcl192001 orcl920dg online t0d42s2 sliced orcl192002 orcl920dg online t0d43s2 sliced orc192003 orcl920dg online t0d44s2 sliced orcl192004 orcl920dg online t0d45s2 sliced orc192005 orcl920dg online tO0d46s2 sliced orcl192006 orcl920dg online t0d47s2 sliced orc192007 orcl920dg online t0d48s2 sliced arch92001 arch920dg online t0d49s2 sliced arch92002 arch920dg online Run the fsck command and mount all the file systems If ASM is being used mount all involved ASM disk groups Recover the database using the new control file generated from the vcdba_rollback command The name of the file is ascii_controlfile for rollback and it is located in the virtual copy repository on the backup host It also shows on the backup host screen when the rollback is done Copy the ascii control file from the backup host to the primary host 6 Optional Recover the cloned database on the backup host as follows backup host up and running the following steps should be performed NOTE After performing the rollback if you still want the cloned database on the Otherwise this section can be skipped a On the InServ Storage Server recreate all VLUNs previously removed by issuing the createvlun lt vvname gt lt lun gt lt host gt command b
143. previous x Exit from the program m The main menu provides following selection 1 Configuration Administration Use this menu to setup a configuration file per database instance Create A Backup Configuration List All Backup Configuration Update A Backup Configuration Remove A Backup Configuration 2 Virtual Copy Management Use this menu to perform all actions of a virtual copy To display create remove mount unmount virtual copy use the remove virtual copy repository menu selection to remove a virtual copy permanently as well as setting up the policy of the virtual copy Display Virtual Copy Create Virtual Copy Remove Virtual Copy 6 22 Command 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 Remove or retain the oldest virtual copy when the maximum number is reached 3 Backup Administration Use this menu to backup the existing virtual copy to tape or disk or perform Virtual Copy creation for off host backup or off host processing Backup Dat
144. r the online redo logs and control files can share the same 3PAR virtual volumes a If the database files reside on Veritas VxVM volumes the datafiles and archive logs must reside on separate VxVM disk groups The online redo logs and control files should reside on separate VxVM volumes used by the datafiles and archive logs m If the Oracle database is an ASM managed database the data files and archive logs must reside on separate ASM disk groups The online redo logs and control files should not reside on the same ASM disk groups used by the datafiles and archive logs to avoid being restored when using the Recovery Manager Rollback feature In addition ASM disk groups should not be shared between different databases m 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 m 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 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 backup host In addition permission on the 3PAR Recovery Manager Inst
145. r generated for the backup host or generate a different SSH key pair for the primary host If you choose to use the same key pair create one InForm CLI user otherwise create two different CLI users to be accessed from the primary host and the backup host respectively If you are generating a different SSH key pair for the Setting Up SSH Connections for Recovery Manager 4 11 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 7 Setting Up Connections from the Backup Host to the NetBackup Master Server on page 4 13 and 4 3 9 Setting Up Connections from the Backup Host to the InServ Storage Server on page 4 14 Then copy the SSH key pair from the backup host to the primary host as follows lt primary_host gt scp lt backup_host gt ssh ssh The authenticity of host pilot 192 168 3 130 can t be established RSA key finger print is XX XX XX XXIXX XX XXIXXIXXIXXIXXIXXIXXXXXXXX Are you sure you want to continue connecting yes no yes Warning Permanently added pilot 192 168 3 130 to the list of known hosts root pilot s password 4 3 5
146. r off host processing Within 3PAR Recovery Manager a virtual copy of a database is a point in time image of the database It consists of virtual copies of the virtual volumes where the data files and or archive logs reside Recovery Manager can be used to create an online offline datafile or archive log virtual copy of an Oracle database An online or offline virtual copy is a point in time image of a database which is taken while the database is OPEN online or CLOSED offline respectively A datafile virtual copy is a point in time image of all database s datafiles which is taken while the database is OPEN online An archive log virtual copy is a point in time image of database s archive log destination which is taken while the database is online OPEN Virtual Copies 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 The information in the repository is used to manage virtual copies and to restore from a virtual copy backup image Some other Oracle related files such as parameter files password files and control files are a
147. r records important information for each virtual copy taken by the Recovery Manager utilities The information is used by Recovery Manager for database restoration The information is stored in the repository at etc 3par solutions lt primary_host gt ora lt oracle_sid gt lt timestamp gt 2 7 1 The Virtual Copy Repository Removal Utility 3PAR Recovery Manager s virtual copy repository removal utility removes a virtual copy s repository that was created using the create utility 2 6 2 The Virtual Copy Creation Utility on page 2 7 The virtual copy that has been removed must have Removed status in order for Recovery Manager to remove the repository The status of a virtual copy can be obtained using the display utility 2 6 3 The Virtual Copy Display Utility on page 2 9 If a virtual copy has been backed up the remove repository utility command fails unless the option is used The Virtual Copy Repository 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 The default and maximum allowed number is 500 meaning that up to 500 read only virtual copies can be
148. r requires that a 3PAR InForm user must have been created on the InServ Storage Server to allow access from the primary host to the InServ Storage Server Enter 3PAR password file on primary host h help q quit You will only be prompted with this question if you previously selected RSH as the remote shell Recovery Manager requires that a 3PAR password file must have been created on the primary host to allow access to the 3PAR InForm CLI from the primary host Enter InServ s user name for the backup host 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 InServ Storage Server to allow access from the backup host to the InServ Storage Server Enter 3PAR password file on backup host h help q quit You will only be prompted with this question if you previously selected RSH as the remote shell Recovery Manager requires that a 3PAR password file must have been created on the backup host to allow access to the 3PAR InForm CLI from the backup host Recovery Manager Configuration Files 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
149. r user name is lt user gt and the group name is lt group gt chown lt user gt lt group gt opt 3par vcdbaora chown lt user gt lt group gt etc 3par solutions chown lt user gt lt group gt etc 3par solutions log chown lt user gt lt group gt etc 3par solutions lock b Change the access permission of the Recovery Manager utilities as follows chmod 550 opt 3par vcdbaora 4 Ifthe etc 3par solutions lt primary_host gt ora lt oracle_sid gt directory exists you must also change the owner and permission as follows chown R lt user gt lt group gt etc 3par solutions lt primary_host gt ora lt oracle_sid gt 3 4 Removing Recovery Manager from Linux Systems To deinstall 3PAR Recovery Manager from a Linux system 1 Log on asthe root user 2 Use the rpm command as follows rpm e VCDBAora 3 5 Installing Recovery Manager on Solaris Systems Use the instructions in this section to install 3PAR Recovery Manager software on both the primary and the backup hosts CAUTION Prior to upgrading to 3PAR Recovery Manager deinstall any previously installed versions of Recovery Manager To remove a previously installed package log on as the root user and use the pkgrm VCDBAora command 3 6 Removing Recovery Manager from Linux Systems Recovery Manager for Oracle User s Guide 3 5 1 Starting Installation To install 3PAR Recovery Manager on a Solaris system 1
150. reated on the NBU master server in order to perform restoration to a host including the primary host that differs from the backup host lt database_hostname gt is the host name of the database server to restore Depending on the type of the virtual copy backup image online offline datafile or archonly corresponding database files are restored appropriately For NBU user manageq restore Control files are not restored by default For an online virtual copy both data files and archive logs are restored unless individual tablespaces or data files are specified In this case only the corresponding data files are restored For an offline virtual copy only data files are restored For a datafile only virtual copy only data files are restored For an archive log virtual copy only archive logs are restored For Oracle RMAN restore Control files are not restored by default For an online virtual copy only data files are restored Archive logs are not restored to minimize restoration time Oracle RMAN can restore necessary archive logs during recovery refer to Oracle documentation for details on how to use Oracle RMAN for recovery For an offline virtual copy only data files are restored For a datafile only virtual copy only data files are restored For an archive log virtual copy archive log restoration is not supported as Oracle RMAN can restore necessary archive logs during recovery refer to Oracle documentation
151. responding database server where the specified database instance is running Select remote shell command r rsh s ssh h help q quit Recovery Manager requires that either RSH Solaris only or SSH is configured to allow remote accesses between the backup host the primary host the InServ Storage Server and the Veritas NetBackup server Enter r for RSH or s for SSH Enter ORACLE_HOME on the primary host h help q quit Recovery Manager 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 ORACLE_HOME on the backup host h help q quit Recovery Manager assumes that the ORACLE_HOME on the backup host is the same as the ORACLE_HOME on the primary host 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 host 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 the ORACLE_HOME of the ASM instance on the primary host Enter ORACLE_HOME of ASM instance on the backup host h q Recovery Manager assumes that the ORACLE_HOME of the ASM i
152. restoring the database control file along with the individual datafile or tablespace is not supported as it is not possible to perform media recovery When restoring a database the database must be in CLOSED or MOUNTED mode for NBU restore or Oracle RMAN restore respectively For an RAC database all RAC instances must be in CLOSED or MOUNTED mode When restoring individual tablespaces or datafiles the database can be OPEN but the corresponding tablespaces must be offline If the database is an ASM managed database all ASM disk groups must be mounted prior to running the restore utility For an NBU user managed restoration the usr openv netbackup db altnames lt database_hostname virtual _hostname gt file must be created on the NBU master server prior to running the restore utility where lt database_hostname virtual_hostname gt is the host name of the database server Depending on the type online offline datafile or archive log of the virtual copy s backup image corresponding database files are restored appropriately For and NBU user managed restoration Control files are not restored by default Recovery Manager and Third Party Backup Tools Recovery Manager for Oracle User s Guide Foran 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
153. rimary_host gt ssh lt username gt lt ss_name gt lt username gt s password lt password gt cli setsshkey Please enter the SSH puplic key below When finished press enter twice Th 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 lt pass the public key here and press Enter twice gt lt public_key gt SSH public key successfully set In the example above e lt username gt is the user being created e lt ss_name gt is the system name of the InServ Storage Server attached to the primary host lt password gt is the password for the CLI user being created lt public_key gt is the SSH public key of the primary host 4 3 12 Verifying Connections from the Primary Host to the InServ Storage Server From the primary host verify the connection from the primary host to the InServ Storage Server as follows Setting Up SSH Connections for Recovery Manager 4 17 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 lt primary_host gt ssh lt username gt lt ss_name gt The authenticity of host lt ss_name gt can t be established DSS key fingerprint is xx xXK XK XX XX XX XX XX XK XKIXK IXKIX IXKIXxX Are you sure you want to continue connecting yes no yes Warning Permanently added lt ss_name gt DS
154. ris systems only Since Recovery Manager can be run by either the root user or Oracle user Oracle owner perform one of the following For Solaris systems configure RSH or SSH for the root or Oracle user For Linux systems configure SSH for the root or Oracle user NOTE RSH or SSH must be set up for the root user in order to use Veritas NetBackup s automatic backup feature a back up initiated from the NetBackup master server as NetBackup always initiates a backup as the root user The following sections describe how to set up RSH and SSH connections Setting Up Connections on Recovery Manager 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 Command Line Interface CLI in the opt 3par cli directory prior to installing 3PAR Recovery Manager Refer to the InForm OS CLI Administrator s Manual for instructions on installing the InForm CLI NOTE If you are setting up an RSH connection you must install the 3PAR InForm Figure 4 1 represents the RSH CLI connections relationship between the primary host the backup host Veritas NetBackup master server and the InServ Storage Server Figure 4 2 represents the RSH CLI connection relationship wit
155. ritas VxVM Control 8 3 1 Rollback with Read Write Virtual Copies 8 3 2 Rollback with Read Only Virtual Copies Using Remote Copy with Recovery Manager 9 1 Overview 9 2 System Configuration 9 2 1 Recovery Manager s Remote Copy Requirements 9 3 Verifying Remote Copy Settings 9 3 1 Verifying the Primary Local Remote Copy Setting 9 3 2 Verifying the Secondary Remote Copy Setting 9 3 2 1 Starting and Synchronizing Remote Copy Groups 9 4 Using Remote Copy 7 7 7 7 7 7 7 8 7 8 7 9 7 9 7 10 7 10 7 11 7 11 7 11 7 12 8 2 8 2 8 2 8 3 8 4 8 4 8 7 9 2 9 3 9 3 9 5 9 5 9 6 9 8 9 9 Recovery Manager for Oracle User s Guide IX Index RH 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 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 enables off host backup of an Oracle database to tape minimizing any impact to the production
156. rrect value for the Oracle parameter file Enter Oracle password file of the database instance h help s skip q quit Recovery Manager provides a default value for the Oracle password file of the specified database instance If the database does not have a password file enter s or S to skip Press ENTER to accept the default value or enter the Oracle password file of the specified database instance Do you want to setup configuration for remote copy y n q n Select n if this configuration is not for 3PAR Remote Copy Enter InServ name h help q quit Recovery Manager Configuration Files 4 29 4 30 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 The InServ Storage Server s host name of the backup host may not be the same as the DNS host name of the backup host Enter InServ s user name for primary host h help q quit You will only be prompted with this question if you previously selected SSH as the remote shell Recovery Manage
157. rrors Eagle IPC transport error EA_PROCESS_DOWN Message canceled becaus of process down 3PAR1170 ERROR Could not perform syncrcopy for specified virtual copy Could not find request handler EAIPC_NOPHANDLE No phandle is available or found 9 4 Using Remote Copy 3PAR Remote Copy can be used to backup the primary database and clone the primary database Cloned databases can be used for testing generating reports or development purpose The primary database can be cloned from the backup host or any other alternate backup host which connects to the secondary remote InServ Storage Server Recovery Manager provides the utility to mount the virtual copies and further clone the primary databases on the backup host Using Remote Copy 9 9 Recovery Manager for Oracle User s Guide 9 10 Using Remote Copy 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 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 5 CLI connection primary to InServ server 4 6 clone utility 2 12 cloned database removal utility 2 14 cloning a data
158. rtual 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 An alternate backup host must have the same operating system file system volume manager and Recovery Manager version as the current backup host Status of a virtual copy can be obtained using a display utility such as the vcdba_display command The following restrictions apply to exporting virtual copies If Veritas Volume Manager is used the alternate backup host must have the same version of Veritas Volume Manager that is currently installed The alternate backup host must be connected to the same InServ Storage Server as the current backup host An identical Oracle Database Administrator user ID and group ID on the backup host must exist on the alternate backup host If the backup host uses SSH as the connection method from the backup host to the primary host then a secure shell connection must be set up between the backup host and the alternate backup host prior to executing this utility This is the only connection method supported in Red Hat Linux Solaris only If the backup host uses RSH as the connection method from the backup host to the primary host then an RSH connection must be set up between the backup host and the alternate backup host pri
159. s 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 Onthe 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 InServ Password File the location of the InServ Storage Server CLI password at the alternate backup host This text field will display if RSH is selected InServ User Name the storage server user name for the alternate backup host This text field will display if RSH is selected Backup Host Name in InServ the alternate backup host name defined in the InServ Storage Server 3 Click Finish to start exporting the virtual copy 7 6 12 Cloning a Database Each online virtual copy created by Recovery Manager represents a point in time database image Recovery Manager can use the virtual copy to help restore the database or to clone the database for testing decision making and report generating purposes The cloning capability takes the workload out of the primary host and reduces performance impact In order to create the cloned database from virtual copies these virtual copies must be created by Recovery Manager with the online or offline
160. s 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 Starting and synchronizing the groups can be achieved by executing the following CLI commands from the primary local InServ Storage Server startrcopygroup lt group_name gt where lt group_name gt is the name of the Remote Copy group which contains all virtual volumes used by database datafiles and archive log destinations NOTE The CLI command showrcopy can be used to check the synchronization status Prior to Recovery Manager release 3 0 0 two Remote Copy groups were required if archive log mode was enabled one for datafiles and one for archive log destinations If you wish to use one group configuration recommended where all datafiles and archive log destinations are within the same Remote Copy group be sure to synchronize the Remote Copy group after you reorganize your Remote Copy group members You can do this by issuing the syncrcopy lt group_name gt command Verifying Remote Copy Settings Recovery Manager for Oracle User s Guide Failure to issue the syncropy lt group_name gt command can result in the subsequently issued vcdba_rsync command failing with the following e
161. s running To mount a virtual copy perform the following procedure 1 2 4 Right click the virtual copy you wish to mount 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 The default mount point is etc 3par solutions lt primary_host gt ora lt oracle_sid gt lt timestamp gt Click Finish Recovery Manager begins mounting all the file systems for you When the mounting of the file systems is complete a screen displays the successful message Click OK In the Virtual Volume State column Mounted should be displayed indicating that the virtual copies are mounted on the backup host The mount point is also displayed indicating the location of the mounted file systems After a virtual copy is in the Mounted state a database instance can be created on the backup host by cloning the database see 7 6 12 Cloning a Database on page 7 9 7 6 5 Unmounting a Virtual Copy After a virtual copy is in the Mounted state an unmount operation can be executed To unmount a virtual copy 1 2 3 Right click the virtual copy you wish to unmount Click Unmount Click Finish A successful message shows on screen after it is finished Click OK The Virtual Volume State column for this virtual copy changes to Available Using Virtual Copies Recovery Manager for Oracle User s Guid
162. sion on the 3PAR Recovery Manager Installation and Repository directories must be changed appropriately OPTIONS The following options are supported m s lt oracle_sid gt The instance SID of the primary database For an RAC database any instance SID can be specified p lt primary_host gt The corresponding hostname of the primary host where the specified Oracle database instance is running COMMAND 6 11 6 12 Recovery Manager for Oracle User s Guide COMMAND vcdba_create SYNOPSIS vcdba_create s lt oracle_sid gt p lt primary_host gt 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 Online or offline virtual copy A consistent point in time snapshot image of the database while it is OPEN online or CLOSED offline respectively Datafile only virtual copy A snapshot image of all datafiles not include archive log destinations of the database while it is OPEN A virtual copy create with the o datafile option is only useful when archive logfiles generated during the creation of the virtual copy are also available You may wish to create separate virtual copies using the o archonly option or use another method to backup archive log destinations Archive log virtual cop
163. st the Primary Host NetBackup Master Server the NetBackup Master Server nServ Storage Server 4 3 10 Verifying Connections from the Backup Host to the InServ Storage Server 4 3 11 Setting Connections from the Primary Host to the InServ Storage Server 4 3 12 Verifying Connections from the Primary Host to the InServ Storage Server Setting up National Language Host Support Setting up Manual Pages on Both Primary and Backup Hosts Setting up a Search Path on Both Primary and Backup Hosts Setting Up Ne 4 7 1 4 7 2 Con 4 7 3 Setti Setting Up Ne 4 8 1 4 8 2 Con Con Con ng Up NetBackup Configuration Parameters Backup Policies for Oracle RMAN Backup Backup Policies for NBU User Managed Backup iguring the NetBackup Policy for Database Backup iguring the NetBackup Policy for Archive Log Backup iguring the NetBackup Policy for Database Backup with RMAN iguring the NetBackup Policy for Archive Log Backup 4 4 4 4 4 5 4 5 4 6 4 7 4 7 4 8 4 9 4 10 4 10 4 11 4 11 4 12 4 12 4 13 4 13 4 14 4 15 4 16 4 17 4 18 4 19 4 19 4 19 4 20 4 21 4 21 4 22 4 23 4 24 Table of Contents V Recovery Manager for Oracle User s Guide 4 8 3 Creating an RMAN Recovery Catalog 4 24 4 9 Recovery Manager Configuration Files 4 27 4 9 1 Creating a Recovery Manager Configuration File without Remote Copy 4 27 4 9 1 1 Creating Configuration Files using the Menu Driven Application or
164. st gt ora lt sid gt lt vc_name gt When using a binary controlfile The structure of the clone database must be exactly the same as the structure of the primary database Therefore the virtual copy must be mounted at if the datafiles and archive logs are on file systems Also since the virtual copy does not contain redologs and archivelogs the same directory structure or same ASM diskgroups for redologs and controlfiles must be pre created on the backup host Command 6 15 6 16 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 A clone database can be created with or without automatic recovery applying archivelogs from the virtual copy using o recovery or o norecovery option if recovery is chosen the clone database is open with reset log otherwise the clone database is in mounted status 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 In addition permission on the 3PAR Recovery Manager Installation and Repository directories must be changed appropriately OPTIONS The following options are
165. store Administration 2 Select a database to restore 3 3PAR Virtual Copy then displays a list of virtual copies Each virtual copy is represented by virtual copy timestamp actual backup timestamp backup type status and a flag to backup to media Choose a virtual copy to restore the database from its associated backup image 4 Choose whether to restore the backup image that is associated with the selected virtual copy to its original location or to a common mount point on the primary or backup host Performing Restores 5 9 5 10 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 Select menu option 1 Periodic Synchronization Select a database to begin synchronization When prompted select o online or offline The periodic synchronization is started You cannot start a new periodic synchronization until the current one finishes If you attempt another synchronization before the current operation completes Recovery Manager returns an error Issue the showrcopy command either from the primary local InServ Storage Server or from the secondary remote InServ Storage Server to check the synchronization status see the InForm OS Command Line Interface Reference for more information about the showrcopy command Synchronization
166. t least one NBU policy of the Oracle type must be created and configured for database backup Optionally a separate NBU policy of the Oracle type can be created and configured for archive log backup See section 4 8 Setting Up NetBackup Policies for Oracle RMAN Backup on page 4 22 for details An RMAN Recovery Catalog database must be created and configured prior to using the backup utility There are two ways to perform backups Immediate backup a backup that is initiated by Recovery Manager through the database backup utility Automatic backup a backup that is initiated by NBU from the NBU master server 2 10 1 1 Immediate Backup During an immediate backup Recovery Manager performs the following Creates an online offline datafile or archonly virtual copy for the database or archive log destination Mounts the virtual copy on the backup host For NBU user managed backup Recovery Manager 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 lt policy_name gt file on the NBU client the backup host Recovery Manager and Third Party Backup Tools 2 17 2 18 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 mod
167. tems 3 6 setting up connections 4 2 utilities 2 7 Recovery Manager repository 2 3 file types 2 3 location 2 3 IX 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 9 performing using the menu driven application 5 9 restoring data files 7 8 restoring databases 5 9 6 30 restrictions with SSH 4 10 revision history RH 1 RMAN recovery catalog creation 4 24 rollback utility requirements 8 1 rolling back read only virtual copies 8 2 rolling back read write virtual copies 8 3 rolling back virtual copies 6 35 RSH 4 2 RSH connection backup to primary server 4 4 RSH connection for NetBackup 4 5 RSH connection for primary server 4 4 RSH connection from backup host to InServ 4 7 RSH connection relationship 4 3 RSH connection relationship for Remote Copy 4 3 RSH connection primary server and InServ 4 6 RSH setup 4 3 S search path setup 4 19 setting up a search path 4 19 setting up manual pages 4 19 setting up national language support 4 18 setting up NBU parameters 4 21 settin
168. the corresponding ASM disk groups are dropped If the database files reside on OCFS2 file systems only one virtual copy per database can be mounted at any time on the backup host Mounting a database virtual copy involves the following actions A read write virtual copy of the original read only virtual copy is created The read write virtual copy is imported to the backup host Snapshots of Veritas VxVM disk groups are imported and all corresponding snapshot VxVM volumes are started if the database files reside on VxVM volumes All snapshot file systems are mounted if the database files reside on file systems Recovery Manager Utilities 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 e 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 e For ASM versions lower than the releases mentioned in the previous bullet if an ASM instance is up on the backup host the mount utility checks if there is any mounted diskgroup If none the ASM instance is shut down otherwise the mount utility gives an error and exits After that a new ASM instance is started up and all disk
169. the oldest virtual copy before creating a new one The default maximum number is 500 read only virtual copies for each volume Select third party backup tool 0 None 1 Veritas NBU 2 Oracle RMAN h q Recovery Manager supports NBU user managed backup and Oracle RMAN backup Enter 0 if you do not want to perform backup If you enter 0 stop here No further information is required If you enter either 1 or 2 you will be prompted for the following information Do you want to remove virtual copy after backup complete y n q Enter n if you do not want to remove the virtual copy after a backup is completed successfully Otherwise enter y Enter Oracle RMAN connection string user password catdb h q You will only be prompted with this question if you previously selected Oracle RMAN as the third party backup tool Enter the Recovery Catalog connection string in user passwd catdb format where catdb is the service name of the Recovery Catalog and user passwd is the user name and password to be used to connect to the Recovery Catalog Enter Oracle RMAN channel type d DISK s SBT_TAPE h q You will only be prompted with this question if you previously selected Oracle RMAN as the third party backup tool Enter dif you want to backup to local disk or s if you want to backup to tape through Veritas NetBackup Media server Enter number of channels to be allocated h help q quit You will only be prompted with t
170. the target InServ Storage Server On the primary local and secondary remote systems use the InForm CLI showrcopy targets command to display the defined target names Data Group the Remote Copy group name for the virtual volumes where the datafiles are located In a single Remote Copy configuration datafiles and archive log destinations virtual volumes are included in the same Remote Copy group 4 48 Recovery Manager Configuration Files 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 verifies the following Connections between the backup host and the primary host Connections between the backup host and the InServ Storage Server Connections between the primary host and the InServ Storage Server Database ID Remote Copy configuration After the verification is complete Recovery Manager creates a virtual copy repository on the backup host etc 3par solutions lt primary_host gt ora lt oracle_sid gt and two configuration files are generated along with one subdire
171. tion Primary Backup Veritas Host Host NetBackup Master Server SSH SSH i _ gt gt Root User Root User Root User SSH SSH Recovery Manager User InServ Storage Server Figure 4 3 SSH Connection Relationship Setting Up SSH Connections for Recovery Manager 4 9 Recovery Manager for Oracle User s Guide Primary Local Backup Remote Host Host SSH iq Root User Root User SSH SSH Recovery Recovery Manager User Manager User Primary Local Secondary Remote InServ Storage InServ Storage Server Server Figure 4 4 SSH Connection Relationship for Remote Copy Support 4 3 1 SSH Restrictions Recovery Manager has the following SSH restrictions m The ssh and scp commands must be located in the usr bin directory Create symbolic links as follows ln s usr local bin ssh usr bin ssh ln s usr local bin scp usr bin scp SSH keys on the primary and backup hosts must be generated with no passphrase Recovery Manager does not support an SSH passphrase or SSH agent 4 3 2 Modifying the SSH Daemon Configuration If SSH needs to be configured for the root user then the SSH daemon on the primary host backup host and NetBackup master server must be configured to allow root access Perform the following on each system 1 Verify that the SSH daemon allows root access by checking the sshd_config file for the
172. ual copy If Oracle RMAN is selected as the backup method this option can be used to perform a cumulative incremental backup of an online or offline virtual copy v Runs the command in verbose mode to display useful messages Recovery Manager for Oracle User s Guide COMMAND vcdba_checkconfig SYNOPSIS vcdba_checkconfig s lt oracle_sid gt p lt primary_host gt 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 One can select to validate only database parameters or non database parameters 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 In addition permission on the 3PAR Recovery Manager Installation and Repository directories must be changed appropriately OPTIONS The following options are supported m s lt oracle_sid gt The instance SID of the primary database For an RAC database any instance SID can be specified p lt primary_host gt The corresponding hostname of the primary database host where the specified Oracle database instance is running The value of the
173. unt point However since the virtual copy does not contains online redo logs and control files their locations can be specified using the 4d option can be one or more directories or ASM diskgroups depending on the desired multiplexing The number of multiplex redo log locations must be equal to or less than the primary database when creating the clone database Otherwise the extra redo log multiplex location will be ignored If the locations of the redologs and controlfiles are not specified they will be created at the repository location for the virtual copy etc 3par solutions lt host gt ora lt sid gt lt vc_name gt When using a binary controlfile the structure of the clone database must be exactly the same as the structure of the primary database Therefore the virtual copy must be mounted at if the datafiles and archive logs are on file systems Also since the virtual copy does not contain redologs and archivelogs the same directory structure or same ASM diskgroups for the redologs and controlfiles must be pre created on the backup host 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 the o for_backup or o binary norecovery option A clone database can be created with or without automatic recovery applying archivelogs from the virtual copy using the o rec
174. uration datafiles and archive log destinations virtual volumes are included in the same Remote Copy group 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 This parameter can be left empty Recovery Manager Configuration Files 4 47 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 e For SSH connection enter the requested information on the configuration screen and click Finish 3PAR InServ Properties Please fill in the field carefully incorrect input values will prevent Recovery Manager from accessing to 3PAR IinServ Server Primary Local InServ Parameters InServName s537 InSery SSH Username ora Target s59 Data Group ASM11G_DATA Archive Group Backup Remote InServ Parameters InServName 3537 InSery SSH Username ora Backup Host Name in InServy sunt1k 02 Target 5537 Previous Finish Cancel 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 Target the name of
175. very Manager In this chapter 9 1 Overview 9 2 System Configuration 9 2 1 Recovery Manager s Remote Copy Requirements 9 3 Verifying Remote Copy Settings 9 3 1 Verifying the Primary Local Remote Copy Setting 9 3 2 Verifying the Secondary Remote Copy Setting 9 4 Using Remote Copy 9 2 9 3 9 3 9 5 9 5 9 6 9 9 Using Remote Copy with Recovery Manager 9 1 Recovery Manager for Oracle User s Guide 9 1 Overview 3PAR Recovery Manager provides three methods to utilize 3PAR Remote Copy for periodic synchronization Graphic User Interface GUI Menu driven application Command Line Interface CLI Each method of Remote Copy is implemented by calling the following utility opt 3par vcdbaora bin vcdba_rsync The following figure illustrates the relationship between the primary and the backup hosts and the primary local and secondary remote InServ Storage Servers Primary Host Backup Host 4 gt Oracle Database 3PAR Recovery Manager 3PAR Recovery Manager Primary Local 4 p gt Secondary Remote InServ Server InServ Server Figure 9 1 Remote Copy and Recovery Manager Relationship The vcdba_rsync command uses the CLI command syncrcopy to periodically push the changed data from the primary local InServ Storage Server to the secondary remote InServ Storage Server The time required for this process depends on the data volume changed in the
176. very Manager Graphical User Interface 7 1 Starting and Stopping the Recovery Manager GUI 7 1 1 Starting the GUI 7 2 Stopping the GUI 7 3 Creating Configuration Files 7 4 Modifying Configuration Files 7 5 Removing Configuration Files 7 6 Using Virtual Copies 7 6 1 Creating a Virtual Copy 7 6 2 Setting up Virtual Copy Policy 7 6 3 Refreshing Virtual Copy Information 7 6 4 Mounting a Virtual Copy 7 6 5 Unmounting a Virtual Copy 6 7 6 8 6 12 6 15 6 18 6 20 6 22 6 24 6 27 6 28 6 30 6 33 6 35 6 37 6 39 7 2 7 2 7 2 7 3 7 3 7 3 7 4 7 4 7 5 7 5 7 6 7 6 Table of Contents V Recovery Manager for Oracle User s Guide 8 9 Table of Contents 7 6 6 Removing a Virtual Copy 7 6 7 Backing up a Virtual Copy 7 6 8 Removing a Virtual Copy Repository 7 6 9 Restoring Datafiles 7 6 10 Refreshing Database Information 7 6 11 Exporting a Virtual Copy to an Alternate Backup Host 7 6 12 Cloning a Database 7 6 13 Removing a Cloned Database 7 7 Periodic Database Synchronization 7 7 1 Starting Periodic Synchronization 7 7 2 Verifying the Periodic Synchronization Process 7 7 3 Removing the Recovery Manager Periodic Sync Lock 7 7 4 Refreshing Remote Copy Information Using the Recovery Manager Rollback Utility 8 1 vcdba_rollback Usage 8 2 Database Volumes Not Under Veritas VxVM Control 8 2 1 Rollback with Read Only Virtual Copies 8 2 2 Rollback with Read Write Virtual Copies 8 3 Database Volumes Under Ve
177. will prompt for the following information ORACLE_SID The Oracle database instance ID For an RAC database ORACLE_SID can be an SID of any instance m ORACLE_HOME The location of Oracle Home on the database server of the specified database instance ORACLE_HOME_BACKUP The location of Oracle Home on the backup host ASM_ORACLE_HOME The location of Oracle Home of the ASM instance on the primary host This parameter is only required if the specified database is using ASM m ASM_ORACLE_HOME_BACKUP The location of Oracle Home of the ASM instance on the backup host This parameter is only required if the specified database is using ASM T m ORACLE_OWN R Oracle database owner of the specified database instance ORACLE_INIT The Oracle database parameter file pfile or server parameter file spfile of the specified database instance 3PAR Recovery Manager recommends that spfile should be used For an RAC database an spfile is required ORACLE_PWDFILE The Oracle password file of the specified database instance if any COMMAND 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
178. write virtual copy will not affect the read only virtual copy e The virtual copy is mounted at a default mount point unless an alternate mount point is specified See section 2 6 4 The Virtual Copy Mount Utility on page 2 10 for instructions on mounting ASM based databases 5 2 5 Unmounting a Virtual Copy To unmount a virtual copy 1 On the Virtual Copy Management menu screen select option 5 Unmount Virtual Copy Select the virtual copy to unmount During unmounting Recovery Manager removes the read write virtual copy as well as any directories that were created during the Mount Virtual Copy operation See section 2 6 5 The Virtual Copy Unmount Utility on page 2 11 for instructions on unmounting ASM based databases 5 2 6 Exporting a Virtual Copy To export a virtual copy 1 On the Virtual Copy Management menu screen select option 6 Export Virtual Copy Select the virtual copy to be exported When prompted answer the following questions a Do you want to export Virtual Copy lt name gt y n q Managing Virtual Copies 5 5 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
179. y A snapshot image of the archive log destination only 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 the Oracle datafiles and or archive log destination depending on which option is specified online offline datafile or archonly An archive log virtual copy can be used in conjunction with online or offline virtual copies to simulate an incremental backup If Recovery Manager is configured to use Oracle RMAN for backup an RMAN Recovery Catalog must have been created and configured prior to running this command The vcdba_create command will initiate an RMAN catalog synchronization during the virtual copy creation process To use the vcdba_create command the Oracle database structure must satisfy the following requirements The database must be running in archive log mode and automatic archival must be enabled in order to create an online datafile or archive log virtual copy Command Recovery Manager for Oracle User s Guide m 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 Howeve
180. y 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 When vcdba_backup is executed it 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 lt policy_name gt on the NBU client the backup host For Oracle RMAN backup to tape or disk To perform RMAN backup to tape the Veritas NetBackup client must be installed on the backup host and primary host In addition Veritas Netbackup for Oracle Oracle Agent must be installed on the backup host primary host and the NBU master server To perform RMAN backup to tape at least one NBU policy of Oracle type must be created and configured for database backup Optionally a separate NBU policy of Oracle type can be created and configured for archive log backup Regardless of tape or disk backup an Oracle RMAN Recovery Catalog database must be created and configured prior to running this command During a backup vcdba_backup starts up a clone database in MOUNTED mode using the mounted virtual copy on the backup host During a backup vcdba_backup executes the RMAN backup script

Download Pdf Manuals

image

Related Search

Related Contents

COOLPIX by Nikon L23 Camcorder User Manual  Radica Games Off Limits Room Blaster 74051 User's Manual  1424 - OneAccess  2008年度の主な取り組み  Fujitsu AMILO Pa 1510  Samsung ML-3750ND Monolaser Drucker (35 / 35 ppm) Benutzerhandbuch  BOT120 PICAXE-20X2 MICROBOT  Minka Lavery 5551-477 Installation Guide  

Copyright © All rights reserved.
Failed to retrieve file