Download HPE Recovery Manager Central 4.0.0 for Oracle User

HPE Recovery Manager Central 4.0.0 for
Oracle User Guide
Abstract
This guide is intended for Oracle database administrators to create, schedule, and manage
snapshots on HPE 3PAR StoreServ Storage systems.
Part Number: 869346-002
Published: April 2017
Edition: 1
©
2016, 2017 Hewlett Packard Enterprise Development, L.P.
Notices
The information contained herein is subject to change without notice. The only warranties for Hewlett Packard
Enterprise products and services are set forth in the express warranty statements accompanying such
products and services. Nothing herein should be construed as constituting an additional warranty. Hewlett
Packard Enterprise shall not be liable for technical or editorial errors or omissions contained herein.
Confidential computer software. Valid license from Hewlett Packard Enterprise required for possession, use,
or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software
Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under
vendor's standard commercial license.
Links to third-party websites take you outside the Hewlett Packard Enterprise website. Hewlett Packard
Enterprise has no control over and is not responsible for information outside the Hewlett Packard Enterprise
website.
Acknowledgments
Microsoft® and Windows® are either registered trademarks or trademarks of Microsoft Corporation in the
United States and/or other countries.
VMware®, VMware® vCenter Server®, and VMware vSphere® Web Client are registered trademarks or
trademarks of VMware, Inc. in the United States and/or other jurisdictions.
Adobe® and Acrobat® are trademarks of Adobe Systems Incorporated.
Java and Oracle are registered trademarks of Oracle and/or its affiliates.
Contents
Overview.......................................................................................................9
Recovery Manager Central for Oracle.................................................................................................9
Features.............................................................................................................................................. 9
RMC-O deployment model....................................................................................................... 9
Licensing.................................................................................................... 11
License models supported by RMC-O...............................................................................................11
Licensing scenarios................................................................................................................ 12
RMC-O installation.....................................................................................14
Deploying RMC................................................................................................................................. 14
RMC-O client installation................................................................................................................... 14
Prerequisites...........................................................................................................................14
Installing RMC-O client........................................................................................................... 16
Uninstalling RMC-O client.......................................................................................................16
RMC-O configuration.................................................................................17
Prerequisites......................................................................................................................................17
First-time RMC-O setup.....................................................................................................................17
Configuring remote copy environment...............................................................................................17
Prerequisites...........................................................................................................................17
Configuring remote copy environment using single RMC VM................................................ 17
Configuring remote copy environment using multiple RMC VMs........................................... 19
Navigating the graphical user interface.................................................. 22
About the graphical user interface.....................................................................................................22
Activity sidebar.................................................................................................................................. 23
Activity sidebar details....................................................................................................................... 23
Banner and main menu..................................................................................................................... 23
Browsers............................................................................................................................................24
Commonly used browser features and settings......................................................................24
Button functions.................................................................................................................................24
Filters sidebar.................................................................................................................................... 25
Help sidebar...................................................................................................................................... 26
View the End-User License agreement.................................................................................. 27
RMC icon descriptions.......................................................................................................................27
Status and severity icons........................................................................................................27
User control icons................................................................................................................... 28
Informational icons..................................................................................................................29
Log out of RMC................................................................................................................................. 29
Search help topics............................................................................................................................. 29
Help search features and limitations.......................................................................................30
Search resources.............................................................................................................................. 31
View resources according to their health status................................................................................ 32
Contents
3
Oracle servers............................................................................................34
About Oracle servers.........................................................................................................................34
Oracle servers screen details............................................................................................................ 34
Overview.................................................................................................................................34
Register server.................................................................................................................................. 35
Edit server......................................................................................................................................... 36
Unregister server............................................................................................................................... 36
Migrate legacy RMO catalog............................................................................................................. 36
RMO to RMC-O migration...................................................................................................... 39
Migrate RMO catalog..............................................................................................................39
Migrating remote copy RMO catalogs.................................................................................... 40
Oracle databases....................................................................................... 42
About Oracle databases.................................................................................................................... 42
Oracle database screen details......................................................................................................... 42
Overview.................................................................................................................................43
Protection View.......................................................................................................................44
Register Oracle database..................................................................................................................44
Edit database.....................................................................................................................................45
Unregister database.......................................................................................................................... 46
Refresh database.............................................................................................................................. 46
Protection policies.....................................................................................47
About protection policies................................................................................................................... 47
Protection policy screen details......................................................................................................... 47
Creating a protection policy............................................................................................................... 49
Edit protection policy......................................................................................................................... 49
Remove protection policy.................................................................................................................. 49
Snapshots.................................................................................................. 50
About snapshots................................................................................................................................50
Snapshot screen details.................................................................................................................... 51
Create local snapshot........................................................................................................................52
About snapshot meta data.................................................................................................................54
Edit snapshot.....................................................................................................................................54
About mount snapshot.......................................................................................................................54
Mount snapshot................................................................................................................................. 54
Remount snapshot............................................................................................................................ 56
Unmount snapshot............................................................................................................................ 56
Remove snapshot..............................................................................................................................56
Restore using a database read-only snapshot.................................................................................. 57
Restore using a database read-write snapshot................................................................................. 59
Performing manual recovery of Oracle database post restore operation.......................................... 61
About cloning databases................................................................................................................... 61
Clone database................................................................................................................................. 62
Remove cloned database..................................................................................................................63
Snapshots with remote copy....................................................................64
About remote copy............................................................................................................................ 64
Remote Copy Requirements for RMC-O...........................................................................................64
4
Contents
Remote copy configuration................................................................................................................65
Set up remote copy........................................................................................................................... 70
Set up remote appliance....................................................................................................................70
Set up remote copy volume groups in HPE 3PAR StoreServ........................................................... 71
Database configuration in failover scenarios.....................................................................................71
Configuring a cloned database............................................................................................... 71
Configuring base volumes on a failover site........................................................................... 71
Create remote snapshot.................................................................................................................... 72
Protect........................................................................................................ 75
About protect..................................................................................................................................... 75
Protect screen details........................................................................................................................ 77
Create protect....................................................................................................................................78
Edit protect........................................................................................................................................ 79
Remove protect................................................................................................................................. 79
Restore protect.................................................................................................................................. 79
Abort protect...................................................................................................................................... 81
Catalyst Copy.............................................................................................82
Catalyst Copy.................................................................................................................................... 82
Catalyst Copy topology......................................................................................................................82
Creating a Catalyst Copy...................................................................................................................82
Creating a Catalyst Copy from an existing snapshot.........................................................................83
Creating a Catalyst Copy from an existing protect............................................................................ 83
Editing a Catalyst Copy..................................................................................................................... 83
Removing a Catalyst Copy................................................................................................................ 84
Restoring a Catalyst Copy.................................................................................................................84
Aborting a Catalyst Copy...................................................................................................................84
NetBackup policy configuration...............................................................85
About NetBackup policies for NBU (user-managed) backup.............................................................85
Configure a Netbackup policy for database and archive log backup......................................85
About NetBackup policies for Oracle RMAN backup.........................................................................86
Configure a NetBackup policy with RMAN............................................................................. 86
About database backup.....................................................................................................................87
Client-side backup.................................................................................................................. 87
Server-side backup.................................................................................................................88
RMAN Recovery Catalog configuration...................................................89
About RMAN Recovery Catalog configuration.................................................................................. 89
Create RMAN Recovery Catalog.......................................................................................................89
Prerequisites...........................................................................................................................89
Creating an RMAN Recovery Catalog.................................................................................... 89
Configure RMAN Recovery Catalog..................................................................................................90
Prerequisites...........................................................................................................................90
Configuring an RMAN Recovery Catalog............................................................................... 90
HPE Data Protector configuration............................................................92
About Data Protector configuration................................................................................................... 92
Prerequisites for database backup.................................................................................................... 92
About database backup.....................................................................................................................92
Contents
5
Client-side backup.................................................................................................................. 92
Server-side backup.................................................................................................................93
Setting up Data Protector.................................................................................................................. 93
Enable RMC-O for Data Protector.......................................................................................... 93
Configure Oracle Operating System User Account (Oracle Owner Account) ........................94
Create Data Protector Oracle backup specification................................................................94
Modify Data Protector RMAN script........................................................................................95
Configure TNS naming service on the RMC-O backup server............................................... 96
Backup and database schema changes.................................................................................96
Media backups........................................................................................... 97
About media backup operations........................................................................................................ 97
Protecting snapshots on media using ISVs....................................................................................... 98
About restore media backup..............................................................................................................99
Restoring media backup..................................................................................................................101
Recovery processes........................................................................................................................ 101
Deleting media backup.................................................................................................................... 104
RMC-O commands...................................................................................105
About RMC-O commands............................................................................................................... 105
Verify the CLI requirements............................................................................................................. 105
rmc_config.py ............................................................................................................................105
rmco_display ..............................................................................................................................106
rmco_create ................................................................................................................................107
rmco_backup ................................................................................................................................108
rmco_remove ................................................................................................................................ 111
rmco_mount .................................................................................................................................. 112
rmco_umount ................................................................................................................................ 113
rmco_createdb ............................................................................................................................114
rmco_removedb ............................................................................................................................115
rmco_rsync .................................................................................................................................. 116
Support ticket...........................................................................................118
Troubleshooting.......................................................................................119
Abort operation of an Express Protect Restore causes the database to go to an error state..........119
Unable to perform a restore of cumulative RMAN backup ............................................................. 119
Failure of media backups.................................................................................................................119
ORA-00845: MEMORY_TARGET not supported on this system .....................................................120
Snapshot mount fails with error pertaining to volume manager...................................................... 120
Media backup completion status not reflecting in Activity page...................................................... 120
New schedule created in RMO post partial successful migration does not get migrated on
reattempt......................................................................................................................................... 122
Update or create recovery set failed — log_archive_dest_n not set error ..............................122
Auto-update all RAC cluster nodes feature causes few RAC nodes to be added with an error
status............................................................................................................................................... 122
Mounted or cloned snapshots do not get migrated with appropriate status in Remote Copy
environment.....................................................................................................................................123
Database startup encounters errors related to SPFILE post a successful snapshot or Express
Protect restore................................................................................................................................. 123
Mounting of snapshot fails with An Unknown error occurred ............................................... 123
6
Contents
Clone operation fails with error MEMORY_TARGET unsupported .....................................................124
Cannot determine archive log mode for database <name>............................................................ 124
SCSI inquiry failed for device devicename. ..................................................................................125
Unable to resolve the file path for <file name>................................................................................ 125
Automatic log archiving is disabled................................................................................................. 125
Unable to determine status of database instance <name>............................................................. 126
<file name> is neither a regular file, directory, block nor a character device...................................126
One or more archivelog destinations of the database have error status ...................................126
Unable to find file system for file <file name>..................................................................................127
Unable to convert oracleasm disks ..............................................................................................127
Unsupported file system type of <file type>.....................................................................................127
Unable to decide the OCFS2 version.............................................................................................. 128
Unable to discover devices used by database <name>.................................................................. 128
Unable to open device <device ID>.................................................................................................128
Snapshot <snapshot name> is not currently mounted at <location>...............................................129
Unable to query for ASM disk groups from the ASM instance........................................................ 129
ORA-15063: ASM discovered an insufficient number of disks for diskgroup ................................129
Unable to determine if ASM rebalancing is in progress...................................................................130
ASM rebalancing operation is in progress.......................................................................................130
Unable to query the clone database for the control file's location................................................... 130
Unable to find device %s .................................................................................................................131
Database is not in managed recovery mode................................................................................... 131
Database instances are still not closed........................................................................................... 131
Unable to generate ASCII control file for database......................................................................... 132
Unable to change asm_diskstring to %s ...................................................................................132
Database is neither a primary nor physical standby database........................................................ 132
Existence of archive log gap between the primary and standby databases....................................133
Unable to stop redo apply process for database %s .......................................................................133
Unable to restart a redo apply process for a database....................................................................133
Unable to determine Oracle ASM version....................................................................................... 134
Incorrect configuration of Oracle ASMLib........................................................................................134
Oracle ASMlib has not been installed..............................................................................................134
ORACLEASM_SCANORDER from <file> does not include <entity>.............................................. 135
Unable to retrieve ASM instance SID for database <database name>........................................... 135
Unable to retrieve ASM clients for the ASM instance <instance name>......................................... 135
One or more ASM disk groups are shared between databases......................................................136
Unable to retrieve ASM disks for database %s ...............................................................................136
Unable to find ASM disk group <name>..........................................................................................136
Unable to shut down (%) database instance <name>.....................................................................137
Unable to parse file %s ................................................................................................................... 137
Unable to create spfile <file name> from pfile <file name> ........................................................137
Unable to retrieve database files..................................................................................................... 138
An error to set value for log_archive_dest_n parameter is displayed ..................................... 138
Unable to sync file system <file system name> on host <host name>............................................138
Unable to remount file system <file system name> on host <host name> ............................. 139
Unable to drop one or more ASM snapshot disk groups.................................................................139
Database <name> may be still running on snapshot...................................................................... 139
Unable to recover clone database...................................................................................................140
Failed to scan snapshot OS devices............................................................................................... 140
The virtual volumes of snapshot %s no longer belong to the current database virtual volumes .....140
Header validation error is encountered from RMAN during media backups................................... 141
An error Invalid clone instance... occurs during clone or backup operation ...................142
Mount operation displays an error about duplicate volume groups or ASM diskgroups..................142
Snapshot creation failed with Recovery Set Snapshot status must be available
or error ...................................................................................................................................... 142
Contents
7
Snapshot operation creates a new snapshot in warning state........................................................ 143
rmco_display -r commands for migrated snapshots having retention set displays an error ... 143
Scheduled backup operation fails post migration without any proper Activity status...................... 143
Pre-check fails due to policy conflict where user specifies Max-Snap-Count in RMO and
Expiration/Retention time in RMC-O or vice versa ......................................................................144
Pre-check fails due to policy conflict where user specifies True for Remove-Oldest-Snapshot
in RMO and False in RMC-O or vice versa .................................................................................. 144
Failed to retrieve OS devices during snapshot mount or unmount operation..................................144
ASCII AND Binary clone with automatic recovery fails on dataguard setup....................................145
While initiating Catalyst Copy Protect operation, RMC IE browser crashes....................................146
Cloning a database with the automatic recovery option fails when ORACLE_HOME is
configured as a symbolic link...........................................................................................................146
Websites................................................................................................... 147
Support and other resources................................................................. 148
Accessing Hewlett Packard Enterprise Support.............................................................................. 148
Accessing updates.......................................................................................................................... 148
Customer self repair........................................................................................................................ 148
Remote support............................................................................................................................... 149
Warranty information....................................................................................................................... 149
Regulatory information.................................................................................................................... 150
Documentation feedback.................................................................................................................150
Creating an RMAN Recovery Catalog....................................................151
Setting Up NetBackup Policies for NBU (User-Managed) Backup......153
Configuring the NetBackup Policy for Database Backup................................................................ 153
Configuring the NetBackup Policy for Archive Log Backup.............................................................153
Setting Up NetBackup Configuration Parameters for the Backup Server....................................... 154
Setting Up NetBackup Configuration Parameters for the Database Server.................................... 154
Setting Up NetBackup Policies for Oracle RMAN Backup...................155
Configuring the NetBackup Policy for Database Backup with RMAN............................................. 155
Configuring the NetBackup Policy for Archive Log Backup.............................................................156
Creating an RMAN Recovery Catalog.............................................................................................156
Configure RMAN Recovery Catalog..................................................................................... 158
Setting Up HPE Data Protector Backup.................................................160
Enable RMC-O Feature for HPE Data Protector............................................................................. 160
Configuring Oracle Operating System User Account (Oracle Owner Account) ..............................160
Create HPE Data Protector Oracle backup specification................................................................ 161
Modify HPE Data Protector RMAN script........................................................................................ 163
Configuring TNS Naming Service on RMC-O Backup Server.........................................................164
8
Contents
Overview
Recovery Manager Central for Oracle
HPE Recovery Manager Central for Oracle (RMC-O) is a data protection solution that provides rapid recovery
from point-in-time snapshots of an Oracle database. RMC-O allows Oracle database administrators to create,
schedule, and manage snapshots on HPE 3PAR StoreServ Storage systems.
The RMC-O Express Protect feature provides a second-tier of data protection with backup of Oracle database
volumes from HPE 3PAR StoreServ to HPE StoreOnce. Backups to HPE StoreOnce are self-contained
volumes, de-duplicated to save space, and can be used to recover to the original or a different 3PAR
StoreServ array. You can use RMC-O with either HPE StoreOnce, HPE Data Protector, Symantec NetBackup,
or Oracle Recovery Manager (RMAN) to protect and restore snapshots created by RMC-O.
NOTE:
RMC-O supports Oracle Enterprise and Oracle Standard Editions. For more information on the
supported versions, see SPOCK for HPE Storage products.
Features
The major features of RMC-O include:
•
•
•
•
•
•
•
•
•
Web based GUI and Command-Line functionality
Schedule snapshot and backup jobs
Create time-based and numeric-based protection policies
Snapshot multiple Oracle databases simultaneously
Migrate legacy HPE 3PAR Recovery Manager Software for Oracle (RMO) snapshot and backup catalogs
to RMC-O database
Space optimized and fast snapshot-based clones of a database to a backup server
Integration with RMC Express Protect for StoreOnce backups
Integration with HPE Data Protector or Symantec NetBackup and Oracle RMAN for media backups
Restore from protects using HPE StoreOnce or Oracle RMAN or HPE Data Protector or Symantec
NetBackup
RMC-O deployment model
The subsequent diagram illustrates the components that are involved in performing a snapshot or a backup
operation. The SAN and management network connections are depicted separately. The tertiary media is a
representation of the different backup targets that can be used.
Overview
9
Recovery Manager Central for Oracle orchestrates the data movement from the HPE StoreServ volumes onto
the HPE StoreOnce Backup appliance. If you have a backup server, you may mount snapshots and clone
databases on it. If you intend to perform a media backup, RMC-O facilitates ISV backup software integration
too.
10
Overview
Licensing
Licensing is used to enable Recovery Manager for Oracle product functionality. You do not have to purchase
a new license if you are an existing RMO customer.
License models supported by RMC-O
HPE 3PAR StoreServ licensing
HPE 3PAR StoreServ arrays are delivered with an All Inclusive license that includes license to use RMC-O.
You need to purchase the RMC Application Suite License if you are using HPE 3PAR 7000 storage and HPE
3PAR 10000 storage arrays.
RMC license must be installed on the HPE 3PAR StoreServ Storage Systems. The RMC instance checks the
licenses on the storage array that is in use. For older HPE 3PAR StoreServ 7000 storage and HPE 3PAR
StoreServ 10000 storage arrays, you have to purchase the RMC Application Suite license. The RMC
Application Suite license covers licensing of RMC and all the RMC application plug-ins. This license has to be
installed on HPE 3PAR StoreServ Storage Systems.
If you do no have the RMC Application Suite license, you can purchase individual application plug-in licenses.
HPE StoreVirtual licensing
All HPE StoreVirtual storage systems are shipped with preinstalled RMC license.
NOTE:
RMC does not allow users to install or delete RMC licenses. These licenses are directly installed on the
HPE 3PAR StoreServ and HPE StoreVirtual Systems. For information on installing these licenses, see
the HPE 3PAR StoreServ Storage and HPE StoreVirtual Storage documentation.
HPE StoreOnce licensing
StoreOnce Catalyst license must be installed on HPE StoreOnce Backup systems.
NOTE:
HPE RMC does not allow users to install or delete StoreOnce Catalyst license. This license is directly
installed on the HPE StoreOnce Backup system. For information on installing this license, see the HPE
StoreOnce documentation.
The following types of licenses are available for RMC-O:
Licensing
11
RMC Application Suite license
Licenses required for RMC appliance to
communicate with HPE 3PAR StoreServ and HPE
StoreVirtual.
HPE StoreOnce Catalyst licenses
Mandatory licenses required for the RMC-O
appliance to communicate with HPE StoreOnce.
•
•
•
•
Virtual Copy is a mandatory license required to
create a snapshot of a volume.
Virtual Copy License
Virtual Lock License
Remote Copy
Thin provisioning
Virtual Lock license is required to enforce the
retention period for a snapshot. Locking a volume,
prevents the volume from being deleted intentionally
or unintentionally before the retention period elapses.
Remote Copy license is required for Remote Copy
operations.
Thin provisioning license is required for creating
thin-provisioned volumes.
NOTE:
For more information on licenses, see Single Point of Connectivity Knowledge (SPOCK) website for
HPE Storage products.
Licensing scenarios
Licensing scenarios table describes how the appliance handles licensing for different user actions:
Table 1: Licensing scenarios
User action
License policy or type
Result
Notes
•
•
•
If a valid license exists,
you can create a
snapshot
The license required is
either Permanent or valid
Temporary license. You
can also use RMC suite
license instead of RMO
license.
Create snapshot
Create snapshot
•
Create snapshot with
retention time
•
•
•
Create HPE StoreOnce
backup
RMO license, RMC
Application Suite
license
Virtual Copy license
RMC Application Suite If a valid license exists,
license
you can create a
snapshot.
Virtual Copy license
Virtual Lock
StoreOnce Catalyst
license
If a valid license exists,
you can backup the
required snapshots.
The license required is
either Permanent or valid
Instant-On license.
Table Continued
12
Licensing scenarios
User action
License policy or type
Result
Mount, unmount, delete,
and restore snapshots
•
These operations
functions without licenses
if a valid license exists
when a snapshot is
created.
•
•
Restore and delete all
StoreOnce backups
RMC Application Suite
license
RMO license
Virtual Copy license
StoreOnce Catalyst
license
Notes
These operations
functions with licenses if
a valid license exists
when a backup is
created.
Licensing
13
RMC-O installation
This chapter provides information on the Recovery Manager Central (RMC) deployment and RMC-O
installation process. Before starting the installation, ensure that the system and license requirements are met.
For more information on the supported environment, hardware, and software platforms, see SPOCK for HPE
Storage products.
Deploying RMC
RMC is available as an OVF package for deployment. The RMC OVF template can be deployed using the
following methods:
•
•
VMware vSphere Client 5.5 or later
VMware vSphere Web Client 5.5 or later
NOTE:
To deploy the RMC OVF template, you must have the vCenter Server. For instructions on downloading
and deploying the RMC OVF package, see the HPE Recovery Manager Central User Guide.
RMC-O client installation
Prerequisites
Procedure
1. Ensure that RMC-O client binaries are installed on application and backup servers.
2. RMC-O client binaries can be installed only on Red Hat Enterprise Linux (RHEL) or Oracle Enterprise
Linux (OEL) 64–bit (x86_64) platforms.
3. Ensure that SSH is enabled on the Oracle server
•
•
For a RAC database, all nodes must have RMC-O client installed.
The database and backup servers must be running either Oracle 12c or 11g software.
Before the installation of RMC-O client, ensure that the following preinstallation requirements are met:
•
•
•
•
•
•
•
•
14
The same Oracle owner user and Oracle DBA group on the database server must exist on the backup
server.
The backup server must use the same operating system as the database server, and must be the same
major version number.
RMC-O client requires Korn shell to be installed and available from the location /usr/bin/ksh
and /bin/ksh, which normally are the default locations for all supported platforms. If not, symbolic links
must be created.
If ASM is used to manage an Oracle database, the same ASM binary owner and group on the database
server must exist on the backup server.
Oracle datafiles 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 logs and control
files must not reside on virtual volumes on which data files and archive logs reside.
If LVM Volume Manager is used, the Oracle datafiles and archive logs must reside on separate LVM
volume groups. In addition, online redo logs and control files must not reside on LVM volume groups that
are used by Oracle datafiles and archive logs. However, the online redo logs and control files can reside
on the same LVM volume group.
If ASM is used to manage an Oracle database, Oracle datafiles 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
RMC-O installation
•
by Oracle datafiles and archive logs. The online redo logs and control files can reside on the same ASM
disk group.
If you are using Symantec NetBackup 1
◦
◦
◦
•
HPE recommends that you use the backup server as the NetBackup master server.
The Symantec NetBackup client must be installed on the database and backup servers.
If you are using Symantec NetBackup in conjunction with Oracle RMAN, the NetBackup for Oracle
client must be installed on the database and backup servers. See Symantec NetBackup for Oracle for
installation and configuration instructions.
◦ If you install the NetBackup for Oracle client, you must link the Oracle libobk.so library on the
database and backup servers to point to the Symantec NetBackup Media Management Library. For
more information, see Symantec NetBackup for Oracle documentation.
◦ If you separate the NetBackup master server from the backup server, RMC-O client installation is
optional on NetBackup master server. Also, no Oracle binary is required.
If you are using HPE Data Protector:
◦
•
•
HPE Data Protector client with Oracle Integration Agent and User Interface components must be
installed on the RMC-O application and backup servers.
◦ The Transparent Network Substrate (TNS) net service name must be preconfigured for the database
instance on the database server.
◦ The same TNS net service name must be preconfigured for the clone database instance on the backup
server. During the backup process, a clone database will be brought up on the backup server.
◦ Oracle Home (including ASM) must be the same between the RMC-O application server and backup
server.
If you select Oracle RMAN for the backup method, you must create an Oracle RMAN Recovery Catalog
and configure Oracle TNS Service and Listener to allow connecting to the Recovery Catalog from both the
application and backup servers. The Recovery Catalog can be created on any host. RMC-O recommends
that the Recovery Catalog is created on the backup server. See Oracle documentation for instructions on
how to create a Recovery Catalog, as well as how to configure Oracle TNS Service and Listener.
In Linux:
◦
•
•
•
1
If you are using the device mapper multipath, the supported disk formats on the database server are:
– /dev/mapper/diskname
– /dev/mapper/aliasname
– /dev/mapper/mpathn
– /dev/dm-n
– /dev/mpath/diskname
◦ Raw disks (/dev/raw/raw) are not supported.
◦ Hard links to the actual devices are not supported.
◦ Each OS disk can only have maximum one partition.
◦ For ext3/ext4 file systems, the journal devices must be within the same file systems
Virtual volume snapshots used by an Oracle database must be mapped to a Common Provisioning Group
(CPG). Refer to the HPE 3PAR Administrator Manual for details about mapping to CPGs.
See the HPE 3PAR Implementation Guides for instructions on setting up connections from hosts to the
HPE 3PAR StoreServ Storage systems and reserving LUNs with specific Host Bus Adapters (HBAs) and
Multipath configurations. The supported HBAs are QLogic and Emulex.
To use the Remote Copy feature, you must configure your HPE 3PAR StoreServ Storage systems for
Remote Copy Software. For instructions on configuring storage systems for Remote Copy Software, see
the HPE 3PAR Remote Copy Software User Guide.
Symantec NetBackup is third-party software, and HPE 3PAR StoreServ makes no representations or warranties
with respect to such software.
RMC-O installation
15
Installing RMC-O client
The procedure details the steps to perform an installation or upgrade of the RMC-O client.
Procedure
1. To download the installation file, perform one of the following steps:
•
Open an internet browser and type the following in the address bar:
•
https://<RMC_IP>/files/rmoracle/client/rmco_installer_linux.tar.gz
Open the command-line interface and type the following command:
wget https://<RMC_IP>/files/rmoracle/client/rmco_installer_linux.tar.gz
NOTE:
If you encounter any certificate errors, use --no-check-certificate option for wget
command.
2. Extract the rmco_installer_linux.tar.gz file using tar command with -xvf option.
3. To install the client and CLI binaries, run the sh ./rmco_install.sh command in the current directory.
For upgrade, the RMC-O client installer automatically prompts for upgrade confirmation.
NOTE:
This process does not uninstall RMO from the servers. However, the RMO schedules are
permanently disabled before a migration activity. HPE recommends uninstalling RMO post
successful migration activity of all the configured databases.
Uninstalling RMC-O client
Procedure
1. To uninstall the RMC-O client binaries, enter /opt/hpe/rmc/oracle/rmco_unistall.sh command
on the intended server.
NOTE:
User generated media backup related utility scripts (as part of protection policy creation) and default
RMC configurations performed using the CLI are not deleted.
16
Installing RMC-O client
RMC-O configuration
This chapter describes the prerequisites for successfully setting up RMC-O environment for taking snapshots
and backups. This chapter also describes the way to configure RMC-O in a Remote Copy environment.
Prerequisites
Ensure that you perform the following steps before you configure RMC-O:
1. RMC availability — RMC appliance must be deployed.
2. Storage system registration (mandatory) — Register the storage systems on which, the Oracle databases
reside.
3. Backup system and backup policy creation (mandatory for express protect backups) — Register the
backup system and create backup policy for creating Express Protect backups of Oracle databases.
4. Notification policy (optional) — You can add, edit, and delete email notifications.
5. Remote appliances (mandatory for remote copy configuration) — Specify the IP address or host name of
the remote appliance that will be used to create Remote Copy snapshots for recovery purposes.
For more information, see HPE Recovery Central Manager 4.0.0 User Guide.
First-time RMC-O setup
Perform the following steps for a first time set up of RMC-O software:
1.
2.
3.
4.
Install RMC-O client binaries on Application and Backup servers.
Registering Server
Creating Protection Policies
Registering databases
On the Oracle databases page, for the configured database, click Actions > Create Snapshot to create the
first snapshot.
Configuring remote copy environment
Prerequisites
Procedure
1. The RMC (remote or target RMC appliance) appliance must be registered for performing remote copy
operations. You can register up to eight appliances and also register the same appliance as remote. The
appliance user credentials can also be edited. For information on registering an appliance, see
Set up remote appliance on page 70.
2. For synchronous long distance (SLD) configurations, Hewlett-Packard Enterprise recommends you to
have two target RMC VMs.
3. Ensure that the names of all the virtual volumes in a Synchronous Remote Copy group does not exceed
20 characters.
Configuring remote copy environment using single RMC VM
For remote copy operations, HPE recommends that you use NIC 0 of RMC VM-I IP address.
RMC-O configuration
17
NOTE:
HPE recommends that you use only time based policy (expiration or retention or both) if you are using
single RMC VM to manage source and target snapshots. If you use numeric policy, the results might
vary. The numeric policy is applicable for the source and target snapshots.
Remote copy environment (Non Synchronous long distance)
Procedure
1. Install the RMC-O 4.0.0 client on Oracle application servers. For information on client installation, see
RMC-O client installation on page 14.
2. Deploy RMC VM as shown in Figure 1: Non synchronous long-distance remote copy environment on
page 18.
Figure 1: Non synchronous long-distance remote copy environment
3. Add a source and target storage system to RMC VM-I.
4. Add the source RMC VM-I IP address as remote appliance, that is, add the RMC VM-I IP address from
RMC VM-I RMC GUI. For information on registering a remote appliance, Set up remote appliance on
page 70.
5. Register the Oracle application server on RMC VM-I. For information on registering an Oracle server, see
Register server on page 35.
Remote copy environment (Synchronous long distance)
•
•
18
Install the RMC-O 4.0.0 client on Oracle application servers. For information on client installation, see
RMC-O client installation on page 14.
Deploy RMC VM-I as shown in Figure 2: Synchronous long-distance remote copy environment on
page 19.
RMC-O configuration
•
•
•
•
Figure 2: Synchronous long-distance remote copy environment
Add the source and target HPE 3PAR Storage systems as per the existing configuration. Use RMC VM-I
RMC GUI to add storage systems. For information on adding a storage system, see the HPE Recovery
Manager Central User Guide.
Add the target synchronous or periodic storage systems as per the RMC configuration. Use RMC VM-I
and RMC GUI to add target-1 and target-2 storage systems respectively.
Add the source RMC VM-I IP address as remote appliance using source RMC VM-I GUI. For information
on registering a remote appliance, see the Set up remote appliance on page 70.
Register the Oracle application server on RMC VM-I. For information on registering an Oracle server, see
Register server on page 35.
Configuring remote copy environment using multiple RMC VMs
This option is recommended for managing remote copy snapshots in RMC-O. For remote copy operations,
HPE recommends that you use NIC 0 of the RMC appliance used as a remote appliance.
Remote copy environment (Non Synchronous long distance)
Procedure
1. Install the RMC-O 4.0.0 client on Oracle application servers. For information on client installation, see
RMC-O client installation.
2. Deploy RMC VM-I and RMC VM-II as shown in Non synchronous long-distance remote copy
environment diagram.
Configuring remote copy environment using multiple RMC VMs
19
Figure 3: Non synchronous long-distance remote copy environment
3. Add the source storage system to RMC VM-I.
4. Add the target storage system to RMC VM-II.
5. Add the remote appliance, that is, add RMC VM-II IP address to RMC VM-I as remote appliance. For
information on registering a remote appliance, see Set up remote appliance on page 70.
6. Register the Oracle application server on RMC VM-I. For information on registering an Oracle server, see
Register server on page 35.
7. Register the Oracle application server on RMC VM-II. This step is optional.
8. RMC-O internally registers the Oracle application server on RMC VM-II when you create the first remote
copy snapshot. HPE recommends that you register the Oracle application server to define the policy on
the target system in advance.
Remote copy environment (Synchronous long distance)
For remote copy operations, HPE recommends you to use NIC 0 of RMC VM-I, RMC VM-II, and RMC VMIII IP address.
•
•
20
Install the RMC-O 4.0.0 client on Oracle application servers. For information on client installation, see
RMC-O client installation on page 14.
Deploy RMC VM-I, RMC VM-II, and RMC VM-III as shown in Figure 4: Synchronous long-distance
remote copy environment on page 21.
RMC-O configuration
•
•
•
•
•
Figure 4: Synchronous long-distance remote copy environment
Add all source HPE 3PAR StoreServe storage systems as per the existing configuration. Use the source
RMC VM-I RMC GUI to add storage systems. For information on adding a storage system, see the HPE
Recovery Manager Central User Guide.
Add remote appliance RMC VM-II and RMC VM-III as remote appliances in the source RMC GUI. Use
the RMC VM-I GUI to add the RMC VM-II and RMC VM-III remote appliance.
Add target synchronous or periodic storage systems as per the configuration. Use RMC VM-II and RMC
VM-III RMC GUI to add target-1 and target-2 storage systems respectively.
Register the Oracle application server on RMC VM-I. For information on registering an Oracle server, see
Register server on page 35.
Register the Oracle application server on RMC VM-II and RMC VM-III. This step is optional on RMC
VM-II and RMC VM-III.
RMC-O internally registers the Oracle application servers RMC VM-II and RMC VM-III when you create the
first remote copy snapshot using RMC VM-II or RMC VM-III. HPE recommends that you register the Oracle
application server to define the policy on the target system in advance.
RMC-O configuration
21
Navigating the graphical user interface
I want to ...
•
•
•
•
•
View the End-User License agreement on
page 27
Log out of RMC on page 29
Search help topics on page 29
Search resources on page 31
View resources according to their health
status on page 32
Learn more
•
•
•
•
•
•
•
•
About the graphical user interface on page 22
Activity sidebar on page 23
Banner and main menu on page 23
Browsers on page 24
Button functions on page 24
Filters sidebar on page 25
Help sidebar on page 26
Help search features and limitations on page 30
About the graphical user interface
To learn the names of common areas, icons, and controls on a UI screen, see the numbered descriptions that
appear after the image.
1. Main menu — The primary navigation menu. To expand the menu, click the .
2. View selector — Controls the information displayed about a resource to focus on specific information.
3. Activity control — Expands (or hides) a sidebar of recent appliance, resource, or user activity (from the
current login session and browser window).
4. Session control — Tracks who is logged in to the appliance and the duration of each login session. Also
enables you to log out of the appliance and edit some user account information, depending on your user
credentials.
22
Navigating the graphical user interface
5. Help control — Expands (or hides) a sidebar which provides access to UI help, License, and the EULA
and Written Offer.
6. Actions menu — Provides actions available on the current resource. Actions include, but are not limited
to: adding, creating, deleting, removing, and editing a resource instance. If you do not have the appropriate
permissions to perform an action, the action does not appear on the Actions menu.
7. Details pane — Provides all information known about a selected resource instance. To see details about a
particular resource instance, click its name in the master pane.
8. Master pane — Lists all resource instances configured on the appliance. In some cases, a status icon
indicates general health of the resource.
Along with the screen components, every UI screen has a notification area to alert you when an event or
activity requires your attention.
Some screens also have a filters sidebar to control the type of information displayed in the master pane.
Activity sidebar
The Activity sidebar shows task activities generated during your current login session. The most recent task
is displayed first.
Task notifications provide information (including in-progress, error, and completion messages) about tasks
that were launched.
Activity sidebar details
The Activity sidebar shows task activities generated during your current login session.
Component
Description
Shows recent task activity generated during your login session.
When the Activity sidebar is closed, the number of alert or task notifications that
have not yet been viewed appears next to the Activity icon.
Activity
Describes the alert or task and the affected resource.
A health status icon indicates the status of the resource associated with the activity.
Banner and main menu
The main menu is the primary method for navigating to resources and performing actions.
To expand the main menu, click anywhere in the banner.
Activity sidebar
23
The main menu provides access to resources; each resource screen contains an Actions menu.
Browsers
For information about the web browsers that are supported for use with RMC, see Single Point of
Connectivity Knowledge (SPOCK) website.
Commonly used browser features and settings
Feature
Description
Screen resolution
For optimum performance, the minimum screen size is 1280 × 1024 pixels for
desktop monitors and 1280 × 800 for laptop displays. The minimum supported
screen size is 1024 × 768 pixels.
Language
US English, Japanese, and Simplified Chinese are the supported languages.
Close window
You can close browser windows at any time. Closing the window while you are
logged in invalidates your session after 24 hours.
Copy and paste
You can select and copy most text, with the exception of text in images. You can
paste text into text entry boxes.
Search in a screen
To search for text in the current screen, press Ctrl+F.
Local history
To view the history of the active tab, right-click the browser back button. Use
this feature to determine how you arrived at the current screen.
Back and forward buttons
You can use the browser back and forward buttons to navigate the UI.
NOTE:
Pop-up dialog boxes are not considered screens. If you click the back
button while a pop-up dialog box is displayed, you return to the previous
screen.
If you click the forward button to go to a pop-up dialog box, you go
instead to the screen with the link to the pop-up dialog box.
The exceptions are screens that you access directly from the Actions
menu. If you use the browser navigation buttons with these screens, you
lose any unsaved changes you made on the screens.
Browser refresh
If you click the browser refresh button to refresh a screen on which you have
added but not saved information, you lose the information.
Zoom in/zoom out
To increase or decrease the text size, use the zoom in or zoom out feature.
Button functions
UI buttons have the same function, whether they appear on screens or dialog boxes.
24
Browsers
Table 2: Standard UI buttons
Button
Description
Add
Adds items from your data center environment.
and
•
Add
•
adds a single item and closes the screen or dialog box.
Add +
Add +
enables you to add another item in the same dialog box.
Remove
Removes items from your data center environment.
and
•
Remove
•
removes a single item and closes the screen or dialog box.
Remove +
Remove +
enables you to remove another item in the same dialog box.
Close
Closes a screen or dialog box and returns you to the previous screen.
Cancel
Discards unsaved changes on a screen or dialog box and then closes the screen
or dialog box.
OK
Confirms and saves your entries and then closes the screen or dialog box.
Filters sidebar
Some resource screens have a Filters sidebar that enables you to control the amount and type of information
displayed in the details pane.
Filters sidebar
25
1. Pin control — Switches between the Filters sidebar and Filters banner bar when clicked. When the filter
banner is in view, the filter headings display across the screen below the resource title. To access the filter
options when in the banner bar view, click the filter name.
2. Filtering criteria enables you to refine the information displayed for a resource in the master pane.
Help sidebar
To open the help sidebar, click
26
Help sidebar
1. Opens context-sensitive help for the current screen in a new browser window or tab.
2. Opens the top of the help contents in a new browser window, which enables you to navigate to the entire
table of contents for the UI help.
3. Displays the End-User License agreement (EULA).
View the End-User License agreement
Procedure
1. To open the Help sidebar, click the
2. Click End-User License agreement
RMC icon descriptions
RMC uses icons to represent the status of resources and to control the display.
•
•
•
Status and severity icons
User control icons
Informational icons
Status and severity icons
Large icon
Small icon
Resource
Activity
Task
Critical
Critical
Failed/Interrupted
Warning
Warning
Warning
Table Continued
View the End-User License agreement
27
Large icon
Small icon
Resource
Activity
Task
OK
Informational
Success
Disabled
Canceled
Unknown
An In progress rotating icon indicates that a change is applied
or a task is running.
This icon can appear in combination with any of the resource
states.
User control icons
Icon
Name
Action
Expand menu
Expands a menu to show all options.
View details
Identifies a title that has additional information. Clicking the title
changes the view to display details.
Expand
Expands a collapsed list item.
Collapse
Collapses an expanded list item.
Delete or remove
Deletes the current entry.
Search
Searches for the text you enter in the Search box; especially useful for
finding types of resources or specific resources by name.
Search is context specific to a particular page. It does not perform a
search across multiple pages.
28
User control icons
Pin
•
•
The left pin expands or collapses the Filters sidebar.
The right pin expands or collapses the Activity sidebar or Help
sidebar.
Sort
Determines whether items are displayed in ascending or descending
order.
Informational icons
Icon
Name
Description
Activity control
Provides a history of user and appliance initiated tasks performed
in the current session.
Session control
Displays username and logged in time; and provides the log out
option.
The RMC GUI session times—out one hour after you log in. If the
GUI is active (performing actions) after one hour, you are prompted
to renew the session.
Help control
•
•
At the top of a dialog box, this icon opens context-sensitive help
for that topic in another window or tab.
In the banner, this icon expands or collapses the Help sidebar,
where you can browse the help documentation or find help on
the page currently displayed. The help sidebar provides the
following:
◦
◦
◦
A Help on this page hyperlink to access context-sensitive
help for the current screen.
A Browse help hyperlink to access the entire help system.
Link that displays the EULA.
Log out of RMC
Procedure
1. Click the Session control icon in the banner.
2. Select Logout.
Search help topics
Procedure
1.
2.
3.
4.
On any screen, click the
In the Help sidebar, select Help on this page.
Context-specific help appears in a separate browser window.
In the new browser window where the help is displayed, click Search at the top of the left navigation pane,
next to the Contents and Index links.
Informational icons
29
5.
6.
7.
8.
Figure 5: UI help search box
Enter a search term in the Search box.
Press Enter or click List Topics to start the search process.
Search results are presented as links to the sections in which the search term appears.
Scan the search results for the section title or titles that best match what you are looking for, and click the
link to view the content. Each instance of your search term is highlighted in yellow for easy identification.
Help search features and limitations
Features
Case sensitivity
By default, searches are case-insensitive. The case-sensitive check box enables you to search matching
the case of the word or phrase you enter.
Full word and phrase matches
You can search for full or hyphenated words.
Phrase search enables you to search for documents containing an exact sentence or phrase by entering
the search text in double quotes (“).
Do not include special characters in the search text of a phrase search.
Wildcard characters
The wildcard feature enables you to replace individual letters, or sequences of letters, within the search
word.
Use a question mark (?) to replace a single character.
Use an asterisk (*) to represent several (or zero) characters.
Keyboard pasted characters
When entering a search keyword, you may find it useful to copy it from another window, right-click in the
text box, and select Paste.
Boolean operators
This feature lets you combine keywords with the Boolean operators to produce more relevant results:
Use a space character for Boolean AND.
Use either OR or or for Boolean OR.
30
Help search features and limitations
Use a hyphen character (-) for NOT.
Auto complete
Auto-complete monitors what you are typing and, after typing the first few characters, displays a list of
suggested words. If one of those words matches what you intended to type, you can select it from the list.
Highlighting
Search highlighting, highlights the searched key words or phrase in the resulting documents.
Fuzzy search
Like a spelling corrector, a fuzzy search tries to correct misspelled search text and suggests corrected
text.
Proximity search
Proximity search looks for documents where two or more word occurrences are at most 10 words apart.
The proximity search operators are NEAR and FBY (meaning “followed by”). These operators can be
entered in upper or lower case.
Synonym search
This feature suggests links to synonyms of the keyword.
Limitations
Special characters
Special characters are not allowed in word search.
The search function does not return topics or index entries that contain special characters, such as the
copyright symbol.
The backslash character (\) is not allowed inside a phrase.
Common words
The search feature does not return common words such as a, an, and the.
Initials
The search function does not return topics or index entries that contain initials, such L.P..
Boolean searches
Boolean operator names must be entered in English.
The AND and OR Boolean operators cannot be combined in a search text.
NOT operators must be at the end of the search string.
Proximity searches
The proximity operators must be entered in English.
Search resources
The banner of every screen includes the Smart Search feature, which enables you to find resource-specific
information such as specific instances of Oracle server name, snapshot names, and IP addresses.
The banner of every screen includes the Smart Search feature, which enables you to find resource-specific
information such as specific instances of host name, snapshot names, and IP addresses.
1. Click in the Smart Search box.
Search resources
31
Search
Smart Search box
2. Enter your search text and press Enter.
The search results are focused in your current location in the UI.
When you start typing, search suggestions are provided based on pattern matching and previously entered
search criteria.
•
•
You can either select a suggestion (the screen displays data containing that selection) or click Enter.
If your search term is a resource, then the list of resources in a master pane is filtered to match your
search input.
TIP:
•
•
•
Enter complete words or names as your search criteria. Partial words or names might not return the
expected results.
If you enter a multiword search term, results show matches for all words you enter.
Enclose a search term in double quotes (”) if the search term contains spaces.
View resources according to their health status
On most screens, you can filter the view of resource instances based on their health status, which might be
useful for troubleshooting or maintenance purposes.
The default filtering is All statuses, which means that all resource members are shown, regardless of their
health status.
To filter that view based on a specific health status, select the health status you are interested in viewing from
the Status menu.
For more information about health status icons and what they mean, see Status and severity icons on page
27.
32
View resources according to their health status
Navigating the graphical user interface
33
Oracle servers
I want to ...
•
•
•
•
Register server on page 35
Edit server on page 36
Unregister server on page 36
Migrate legacy RMO catalog on page 36
Learn More...
•
•
•
About Oracle servers on page 34
Oracle servers screen details on page 34
Migrate legacy RMO catalog on page 36
About Oracle servers
The Oracle Servers Overview screen displays the registered servers and enables you to register production
and backup servers to the RMC appliance. There are the following types of Oracle servers:
•
•
•
•
Application — This type of server is where the production database is hosted.
Backup — This type of server is where the mounting or cloning of a snapshot or ISV supported backup
takes place.
NBU Master Server — This type of server is where the NBU Master server is configured. NBU Master
server must be running on a*nix platform. RMC-O client binaries installation is not mandatory for this
server type.
Backup+NBU Master — It is a combination of the Backup and NBU Master Server. RMC-O client
binaries installation is mandatory.
Oracle servers screen details
The master pane of the Oracle Servers screen displays the IP address/host name and the server type of a
registered Oracle server. The details pane displays the general details related to the server selected on the
master pane and the details of the database configured on the server. You can also use the Actions menu to
Register server, Edit server, Unregister server, and Migrate legacy RMO catalog.
Overview
Server details
Host name
Host name of the server.
IP address
IP address of the server.
Operating system type
Operating system installed on the server.
Operating system version
Version of the operating system.
Kernel version
Kernel version of the operating system.
Hardware architecture
Architecture of the processor.
34
Oracle servers
RMC-O client version
Version of the RMC-O client installed on the system.
Registration time
Server registration time stamp.
Updated time
Server modification time stamp.
Description
Description that you might have added while registering the server.
Associated databases
NOTE:
This section is populated if there is a database associated with the registered server.
Name
Name of the associated database.
Description
Description of the database.
Role
Displays the role of the HPE 3PAR StoreServ.
Type
Type of database.
Version
Oracle version number of the database.
Created at
Database creation time stamp.
Register server
Prerequisites
•
•
•
•
•
Ensure that you have root user privileges for the server you intend to register and that root has SSH
access.
Ensure that you have RMC-O client installed on the server that you intend to register.
You can register a server that is running RHEL and OEL versions 6.x and 7 (U1 and U2).
Only the 64–bit (x86_64) platform is supported for server registration. The 32–bit (i386, i686, and so
on) platforms are not supported.
You cannot use virtual entities of RAC like SCAN, VIPs for registration.
Registering a server
Procedure
1. Click the HPE Recovery Manager Central main menu and then click Servers.
2. Perform one of the following:
Register server
35
• On the master pane of the Servers screen, click + Register Oracle Server.
• Select Register Server from the Actions menu.
3. Select the Server type. For example Application, Backup, NBU Master server, or Backup + NBU
master server.
NOTE:
The backup server can also be legacy RMO backup server having catalog repository information.
You can migrate this repository to RMC-O.
4. Provide the following details:
a. IP Address or Host Name — IP address or host name of the server to be configured for backup.
NOTE:
If you intend to use the hostname for registration purpose, configure the DNS appropriately.
b. Username — User name of the server. The user must be the root user or have user ID of 0.
c. Password — User password.
d. Description — Description or additional comments about the server.
5. Click OK.
Edit server
Procedure
1.
2.
3.
4.
Click the HPE Recovery Manager Central main menu and then click Servers.
On the master pane of the Servers screen, select a server.
Select Edit from the Actions menu.
Perform the following actions:
•
•
•
Edit the IP Address or Host Name.
Edit the username or description.
Re-enter the password.
NOTE:
Remember to update the password whenever the root password on the server changes.
5. Click OK.
Unregister server
Procedure
1.
2.
3.
4.
Click the HPE Recovery Manager Central main menu and then click Servers.
On the master pane of the Servers screen, select a server.
Select Unregister Server from the Actions menu.
Click Yes, Unregister.
Migrate legacy RMO catalog
Migrate legacy RMO catalog section describes the prerequisites and the process of migrating the existing
catalog information from HPE 3PAR Recovery Manager Software for Oracle (RMO) version 4.6 or 4.7 to
RMC-O. The migration process migrates all local and remote snapshots, policies, schedules, and backups
from the selected backup server to the RMC-O appliance. When the migration completes, RMC-O triggers the
backup and snapshot creation tasks as per the schedules created in RMO.
36
Edit server
Time and numeric policies set in RMC-O can be overridden with the policies of RMO during migration
process. This override is achieved by selecting the Enforce RMO policies option in the Migrate Server
window. When you click Yes, migrate in the Migrate Server window, the system validates all prerequisites.
You can monitor the validation progress in the Activity feed. If the validation fails, a recommended action is
provided for the failed task so that you can rectify the issue and initiate migration again. If the validation is
successful, the system proceeds with the migration and displays the migration summary and report on
completion. You can view the reports at https://<RMC_IP>/RMC-O/migration and get the details.
When you select a backup server for migration, there are prechecks that are performed on all configured
databases before the start of the actual migration process. If any database encounters an error, the migration
process ignores that particular database and continues with the migration activity for other databases. After
you rectify the errors that a particular database encountered, you can restart the migration process for them.
CAUTION:
Ensure that you continue to with RMCO after successful migration. If you have encountered unexpected
errors while migration activity, and want to continue working with RMO, perform the following steps:
1. Locate and login to the backup server where the migration activity was initiated.
2. Navigate to /etc/3par/solutions location.
3. Rename rmco_tasks/ folder as tasks/.
For a database, the sequence in which, various entities undergo migration is as follows:
1.
2.
3.
4.
5.
RMO Policies (Snapshots and backups) to RMC-O Protection Policies
Snapshots
Backups
Schedules
RMO email notification to RMC-O Notification policies
Sr.
No.
Precheck
Behavior when
Enforce RMO Policy
option is not selected
1
Backup server registration with RMC
If not registered, migration is not possible.
2
Supported version check
Only RMO 4.6 and 4.7 supported.
3
Production server registration with RMC
If not registered, migration fails for all the databases on
the server.
4
Array registration with RMC
If not registered, snapshot migration is skipped and any
schedules, backups, policies are migrated.
Table Continued
Oracle servers
37
Sr.
No.
Precheck
Behavior when
Enforce RMO Policy
option is not selected
5
Policy conflict check
This check is about max snap count and expiration/
retention time which are mutually exclusive parameters.
Following is the migration behavior:
•
•
6
Snap count check
If max snap count is set in RMO and expiration/
retention time is set on database in RMC-O or
conversely, precheck fails.
If both max snap count and expiration/retention time is
set in legacy configuration file, then the latter takes
the precedence and gets considered for policy conflict
check.
This check is to ensure that max snap count value on
RMC-O database is set to a higher value than the total
number of snapshots on RMC-O, had the migration been
successfully complete. Following is the migration
behavior:
•
•
If max snap count in legacy is set to some nonzero
value and it is unspecified on database in RMC-O,
precheck fails. In this case, you must set max snap
count value on RMC-O database to something
accommodate the number of snapshots on RMO and
RMC-O.
If max snap count in legacy and RMC-O database
both is set to some nonzero value, then a check is
made on
remove oldest snapshot
•
38
flag to see if they have the same value set for both
legacy and RMC-O database. If not, precheck reports
the issue and moves onto the next database.
If max snap count in legacy and RMC-O database
both is set to some nonzero value, then a check is
performed on max snap count set on RMC-O
database that it is larger than the total number of
unmigrated snapshots and the ones already present
on the appliance for the corresponding database. If
precheck fails, it reports the issue and moves onto the
next database.
8
Snapshot state check
This check reports whether a snapshot is in migrate-able
state or not. This check is performed on all the potential
snapshot candidates for migration.
9
NBU registration with RMC
If NBU is configured on legacy setup, this check is
performed to ensure that NBU server is registered with
RMC. If not, precheck fails and does not allow migration
for the corresponding database.
Oracle servers
NOTE:
•
•
•
•
•
HPE recommends to use Enforce RMO Policy option to overcome conflicts during migration
process.
HPE recommends you to use RMC-O to create schedules for snapshots, backups, and so on, after a
successful migration of the database.
If there are no schedules for a particular database, the email configurations created from legacy
RMO are not migrated. In such cases, you must create Notification Policies (Application type as
RMC-O) from the RMC user interface and associate it with corresponding databases if you have to
subscribe to email notifications.
If there are more than one notification policies (local and remote) configured for the database, all of
them are migrated to the local appliance. One among all gets associated with the database. Review
the Notification Policy association and perform any changes.
Any time based policies (expiry or retention) configured in days in RMO is converted to appropriate
hours. This conversion happens as part of protection policy creation in RMC-O.
RMO to RMC-O migration
The following list details the rules for a typical RMO to RMC-O migration:
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
Unregistered databases are skipped.
Databases for which array is unavailable are skipped.
Databases for which any database specific pre-check fails are skipped.
Local protection policy gets migrated to local appliance.
Remote protection policy gets migrated to remote appliance.
Local snapshots get migrated to local appliance.
Remote snapshots get migrated to remote appliance.
Backups of existing snapshots get migrated to local appliance.
Backups of removed snapshots get migrated to local appliance.
Both local and remote schedules get migrated to local appliance.
Both local and remote email notification policy get migrated to local appliance.
Removed and stale snapshots are be migrated.
Mounted snapshots get migrated in mounted state.
Cloned snapshots get migrated in cloned state.
Mounted(P) snapshots get migrated in mounted state.
Orphaned snapshots get migrated in available state.
For remote snapshots migration, servers and databases are auto registered on the remote appliance if it is
different from local appliance.
Remote backup server are registered on the remote appliance if there is at least one of mounted or cloned
snapshot to be migrated on the backup server selected for migration.
Post-migration, newly created schedules in RMO do not get migrated during retry migration operation.
Instead, you need to create new schedules from RMC-O user interface.
Migrate RMO catalog
Prerequisites
•
•
•
•
Ensure that the HPE 3PAR StoreServ systems are registered.
All the related servers that are applicable (Application, Backup, NBU master) must be registered in RMCO.
For migrating remote snapshots from RMO to RMC-O, the prerequisites for creating remote snapshots in
RMC-O must be met. For more information on the prerequisites, see Create remote snapshot .
The maximum snapshot count in the RMC-O database must be greater than or equal to the snapshots
present together in RMO and RMC-O.
RMO to RMC-O migration
39
Migrating legacy RMO catalogs
Procedure
1. Click the HPE Recovery Manager Central main menu and then click Servers .
2. On the master pane of the Servers screen, select the backup server from which you want to migrate the
data.
3. Select Migrate legacy RMO catalog from the Actions menu.
4. Click Yes, migrate .
•
•
If the migration is successful, click HPE Recovery Manager Central > Activity to view the migrated
entities.
If the migration is unsuccessful or partially successful, click HPE Recovery Manager Central >
Activity to view the details. You can view the migration report, rectify the issues, and then initiate
migration again.
NOTE:
•
•
•
Snapshots with Mounted or Database states in RMO are also migrated with the same states to
RMC-O. Snapshots with Mounted(P) state are migrated to Mounted state.
HPE recommends performing a remount operation on the Mounted(P) state snapshots in legacy
RMO before attempting to perform a migration operation. However, if you fail to do so, you can
also perform the remount operation in RMC-O post migration operation.
Snapshots with Orphaned states in RMO are migrated as Available to RMC-O. Operations on
such snapshots will fail. HPE recommends removing any Orphaned snapshots in RMO before
migrating to RMC-O.
Migrating remote copy RMO catalogs
Prerequisites
•
•
•
•
•
•
•
Ensure that the remote backup server is registered with the local appliance.
Ensure that the local backup server (if configured) is registered with the local appliance.
Ensure that the source HPE 3PAR StoreServ systems are registered on the primary RMC appliance and
the secondary HPE 3PAR StoreServ systems are registered on the secondary RMC appliance, and so on.
All the related servers that are applicable (Application, Local Backup, Remote Backup, NBU master) must
be registered in RMC-O (primary appliance). On remote appliance, registration of servers is optional.
Register the secondary RMC appliances in the Remote Appliances page on the RMC user interface.
Ensure that you register the databases that you intent to migrate on a primary appliance and optionally on
a secondary appliance.
The maximum snapshot count in the RMC-O database must be greater than the snapshots present
together in RMO and RMC-O.
Procedure
Procedure
1. Click the HPE Recovery Manager Central main menu and then click Servers.
2. On the master pane of the Servers screen, select the remote backup server from which you want to
migrate the data.
3. Select Migrate legacy RMO catalog from the Actions menu.
4. Select Remote Copy and then select the Local Backup Server from the list.
5. Select the Remote RMC Appliance and then click Yes, Migrate.
40
Migrating remote copy RMO catalogs
NOTE:
•
•
•
•
•
When using a single RMC-O appliance and a single backup server in RMO, the local and the
remote backup servers and the local and Remote RMC appliances are the same.
If the database is not registered on the secondary (remote) appliance, the protection policy of the
secondary appliance does not get attached to the migrated database of the secondary appliance
after a successful migration operation.
Post successful migration, refrain from using RMO for migrated snapshots. Before starting
operations using RMC-O, review the protection policy that is associated with the database.
During migration, some of the local snapshots of remote backup server get updated on local
appliance temporarily. It gets removed from the local appliance and gets updated on remote
appliance after migration process completion.
Wait for the first migration process to complete before you initiate a second migration process.
6. Select the Enforce RMO Policy option. If not selected, all pre-checks are performed stringently.
Oracle servers
41
Oracle databases
I want to ...
•
•
•
•
Register Oracle database on page 44
Edit database on page 45
Unregister database on page 46
Refresh database on page 46
Learn More...
•
•
About Oracle databases on page 42
Oracle database screen details on page 42
About Oracle databases
You can register your application database that you want to protect. You can either specify an Oracle SID and
then register or allow RMC to register all the databases running on the selected server.
The Oracle Databases Overview screen displays the registered databases. You can use this screen to
Register Oracle Database, Edit Database, Unregister Database, Refresh Database, Create Snapshots,
Protect, and Catalyst Copy.
In the Protection View page, the information about Snapshots and Express Protects is displayed. You can
remove one or more Snapshots or Express Protects using the Bulk Remove option.
About Oracle standby database
An Oracle standby database is a synchronized copy of the production database. You can use the snapshot of
a standby database to promote standby database volumes. However, you cannot use the snapshot to
promote primary database volumes (even though a backup of the snapshot can be used to restore the
primary database). The Oracle standby databases are supported if:
•
•
•
The Oracle Database version is 11g or 12c.
The standby database is a physical database. Logical or snapshot standby databases are not supported.
The primary database (not standby) is registered with Oracle Recovery Catalog while using RMAN
backup.
About Production database configuration
This section describes the storage configuration that the database must fulfill to take snapshots and perform
backup operations. All the datafiles and archive logs must reside on the same HPE 3PAR StoreServ storage.
However, the datafiles and archive logs cannot coexist on the same volumes. CONTROLFILE, SPFILE and
redo logs cannot be present on datafile volumes or archive log volumes. The same condition is applicable for
ASM diskgroups.
For Remote copy configuration, see Remote Copy Requirements for RMC-O on page 64.
IMPORTANT:
The Oracle parameter and control files are not compatible with the standby and primary databases. You
cannot use these files to restore the primary database unless Oracle RMAN is used. The Oracle
parameter and control files of the primary database must be backed up manually outside of RMC-O.
Oracle database screen details
The master pane of the screen displays the name and type of database. The details pane displays the details
pertaining to the database selected in the master pane.
•
•
42
Overview
Protection View
Oracle databases
Overview
Database details
Name
Name of the Oracle database.
Description
Description of the Oracle database.
Oracle version
Oracle version of the database.
Type
Type of the Oracle server, for example, Standalone, Real Application Clusters, and Dataguard .
Role
Role of the source and target HPE 3PAR StoreServ. The role of the source HPE 3PAR StoreServ is
always Primary. The role of the target HPE 3PAR StoreServ is always Secondary.
Oracle Home
The directory path where Oracle is installed.
Protection policy
Protection policy associated with the database.
Notification Policy
Notification policy associated with the database.
Maximum Snapshot count
Maximum number of database snapshots that can be taken.
Delete Oldest snapshot
Indicates if the oldest snapshot is deleted when the maximum snapshot count is reached. The value can
be either True or False.
Maximum Express Protects count
Maximum number of express protects that can be taken.
Delete Oldest Express Protects
Indicates if the oldest express protect is deleted when the maximum express protect count is reached.
The value can be either True or False.
Maximum Copy count
Maximum number of catalyst copy that can be taken.
Delete Oldest Copy
Indicates if the oldest catalyst copy is deleted when the maximum catalyst copy is reached. The value can
be either True or False.
State
Current state of the database related to the RMC-O operations. For example, Available, Error, Errorrestoring, Restoring, Migrating, Updating.
Registered at
Database registration timestamp.
Overview
43
Database instances
Name
Name of the Oracle database.
ASM ID
Displays the SID of the ASM instance corresponding to the database instance.
Server
IP-host name of the Oracle server.
Protection View
Snapshots
Name
Name of the snapshot.
Timestamp
Timestamp indicting the snapshot creation time.
Snapshot type
Type of snapshot, for example, online, offline, datafile, or archlog.
Mounted
Indicates if the snapshot is mounted. The value can be either Yes or No.
Cloned
Indicates if the snapshot is cloned. The value can be either Yes or No.
Protects
Name
Name of the express protect backup.
Timestamp
Timestamp indicting the express protect creation time.
Snapshot type
Type of snapshot, for example, online, offline, datafile, or archlog.
Backup type
Type of backup, for example, full, incr, or cinc.
Backup vendor
The backup vendor.
Catalyst Copy
Indicates if there is a copy of an Express Protect on another HPE StoreOnce Catalyst Store.
Register Oracle database
Prerequisites
•
44
To update Real Application Cluster (RAC) cluster nodes, ensure that the following prerequisites are met:
Protection View
◦
◦
The appropriate cluster node is registered using the Oracle Servers screen.
DNS is configured correctly so that it communicates with other cluster nodes from the RMC appliance
using the hostname. If DNS is not configured correctly and you select the Auto update all RAC
cluster nodes check box, RMC-O does not update all RAC cluster nodes. In such case, you must
manually register other RAC nodes using SID option and add RAC nodes host entries in /etc/hosts
of RMC.
Registering an Oracle database
Procedure
1. Click the HPE Recovery Manager Central main menu and then click Databases.
2. Do one of the following:
• On the master pane of the Databases screen, click + Oracle Databases.
• Select Register from theActions menu.
3. In Server properties, enter the name of the Oracle server or click Select to select a server from the list.
4. In Database properties, provide the following details:
•
•
SID — Oracle SID of the database to be added.
Oracle Home — The ORACLE_HOME directory where the database instance with the specified SID is
running.
NOTE:
You can specify ORACLE_HOME that are configured as symbolic links.
•
•
Description — Description of the Oracle database.
Protection policy — Protection policy that you want to associate with the database. For information on
protection policies, see Protection policies. To select a policy from the list, clickSelect.
• Notification Policy — Notification policy to be associated with the database.
• Maximum snapshots — Maximum number of snapshots that you can create. The maximum limit is
2048.
• Maximum express protects — Maximum number of express protect backups that you can create. The
maximum limit is 2048.
• Remove the oldest snapshot — Select to delete the oldest snapshot when the maximum snapshot
limit is reached.
• Remove the oldest express protects— Select to delete the oldest express protect when the
maximum express protect limit is reached.
• Auto update all RAC cluster nodes— Select to auto update the RAC nodes. This option is enabled if
SID is entered.
5. Click OK.
NOTE:
If an Application Server hosts any catalog databases, often the catalog databases get registered.
Unregister catalog databases that you do not intend to protect.
Edit database
Procedure
1.
2.
3.
4.
5.
Click the HPE Recovery Manager Central main menu and then click Databases.
On the master pane of the Databases screen, select a database.
Select Edit from the Actions menu.
In Database properties, edit the protection policy or notification policy associated with the database.
In Numeric, do the following:
Edit database
45
•
•
Edit the Maximum snapshots, Maximum express protects, Maximum Copy Protects or all.
Select or clear the Remove the oldest snapshot, Remove the oldest express protect, Remove the
oldest Copy Protects, or all.
6. Click OK.
NOTE:
•
•
If you associate a new protection policy with the database, the older protection policy cannot be used
for a backup until it is associated again. Similarly, you can associate and disassociate a notification
policy. If you intend to clear the current policies set with the database, you may use the
Disassociate option.
If you use RMAN_DP, at first, temporarily disassociate the protection policy before you update any
attributes. Reassociate the protection policy after you successfully update the attributes.
Unregister database
Procedure
1.
2.
3.
4.
Click the HPE Recovery Manager Central main menu and then click Databases.
On the master pane of the Databases screen, select a database.
Select Unregister from the Actions menu.
Click Unregister.
Refresh database
Refresh database operation for a database analyzes all the snapshots and Express Protect backups residing
in RMC-O catalog. Any snapshots and Express Protect backups that have expired (due to numeric or timebased policies set) are removed from the RMC-O catalog after a refresh operation. Refresh database
operation is a time consuming activity as it depends on the number of snapshots or Express Protect backups
that are present in a database.
Procedure
1.
2.
3.
4.
46
Click the HPE Recovery Manager Central main menu and then click Databases.
On the master pane of the Databases screen, select a database.
Select Refresh from the Actions menu.
To refresh the snapshots and express protects on the selected database, click Refresh.
Unregister database
Protection policies
I want to ...
•
•
•
Creating a protection policy on page 49
Edit protection policy on page 49
Remove protection policy on page 49
Learn More...
•
•
About protection policies on page 47
Protection policy screen details on page 47
About protection policies
Protection policy is used to abstract various attributes related to snapshots and protects. If you do not intend
to perform backups of your databases, you can use protection policy to specify the properties common to all
snapshots (expiration and retention times) and associate it with more than one database.
If you intend to perform Express Protect backups, you may create a single protection policy and associate it
with many databases.
If you intend to perform media backups, ensure that there is at least one dedicated protection policy per
database created and associated. However, you may create one or more database-specific protection policies
based on your back-up strategy and specify them in the Create Protect dialog. For client-side backups
triggered from the ISV interface, the associated protection policy is always used.
Protection policy screen details
The Protection Policy Overview screen displays the protection policies and enables you to add, edit, or
remove protection policies. The master pane of the Protection policies screen displays the configured
policies and the details pane displays the details associated with the policy, such as policy ID, backup policy
associated with the protection policy, snapshot retention, and snapshot expiration details.
ID
Internal ID of the protection policy that can be used with rmco_backup command.
Policy name
Name of the protection policy.
Description
Description of the protection policy.
Expiration time
Time when the storage system removes the snapshot automatically once the expiration time is reached.
To specify an expiration time, specify a value between 0 to 43,800 hours (1825 days).
Retention time
Time until when the snapshot is retained. To specify a retention time, specify a value between 0 to 366
hours (0 to 14 days).
Backup vendor
Back up vendor to be used for backing up a database snapshot. The supported backup methods are HPE
StoreOnce, RMAN, RMAN NBU, RMAN DP, and NBU.
Backup policy
Back up policy that you want to associate with the backup system. For information on creating a backup
policy, see the HPE Recovery Manager Central User Guide.
Protection policies
47
NOTE:
This field is available only if you select HPE StoreOnce as the backup system.
Copy policy
Copy policy that you want to associate with the backup system.
NOTE:
This field is available only if you select HPE StoreOnce as the backup system.
Backup server
Backup server to which you want to associate the backup policy.
Channel count
Number of RMAN channels to be allocated during backup and restore. The valid channel count is
between 1 to 99.
Catalog Username
Database user name configured for the catalog database. For example, rman.
Catalog Password
Database password configured for the catalog database.
Catalog Service Name
Database service name configured for the catalog database. For example, catdb.
NOTE:
RMAN uses the Catalog Username, Catalog Password, and Catalog Service Name attributes for
connecting to catalog database. For example, rman/rman@catdb.
Master server
Host name of the Symantec NetBackup master server.
Datafile policy
Policy created on the NBU master server for datafile backup.
Data policy schedule full
Symantec NetBackup schedule name for database backup.
Archivelog policy
Policy created on the NBU master server for archive log backup.
Archivelog policy schedule full
Symantec NetBackup schedule name for archive log back-up (full).
Archivelog policy incremental schedule
Symantec NetBackup schedule name for archive log back-up (incremental).
48
Protection policies
Creating a protection policy
Procedure
1. Click the HPE Recovery Manager Central main menu and then click Protection Policies.
2. Perform one of the following:
• On the master pane of the Protection Policies screen, click+ Protection Policy.
• Select Add from the Actions menu.
3. Enter the policy name, description, expiration time, and retention time.
4. Select the backup vendor from the list and specify values for the related attributes.
•
HPE StoreOnce — Select and specify the Backup policy and the Copy Policy. Copy policy, also
known as catalyst copy creates a copy of an Express Protect on another HPE StoreOnce Catalyst
Store. For information on creating a backup policy and catalyst copy, see the HPE Recovery Manager
Central User Guide.
• RMAN — Specify the Backup server, Channel count, Catalog Username, Catalog Password,
Catalog Service Name, Backup destination, and Use Large Pages. For more information, see
Appendix A, Creating an RMAN Recovery Catalog.
• RMAN NBU — Specify the Backup server, Channel count, Catalog Username, Catalog Password,
Catalog Service Name, NBU master server, Datafile policy, Data policy schedule full, Archivelog
policy, Archivelog policy schedule full, Archivelog policy incremental schedule, and Use Large
Pages. For more information, see Appendix B, Setting Up NetBackup Policies for NBU (UserManaged) Backup.
• RMAN DP — Specify the Backup server, Channel count, Catalog Username, Catalog Password,
Catalog Service Name, Datafile Backup Specification, Archivelog Backup Specification, Use
Large Pages, and for the backup system. For more information, seeAppendix C, Setting Up
NetBackup Policies for Oracle RMAN Backup.
• NBU — Specify the Backup server, NBU Master server, Datafile policy, Data policy schedule full,
Archivelog policy, Archivelog policy schedule full, and Archivelog policy incremental schedule.
For more information, seeAppendix D, Setting Up HPE Data Protector Backup.
5. To create the protection policy, click OK.
Edit protection policy
Procedure
1.
2.
3.
4.
Click the HPE Recovery Manager Central main menu and then click Protection Policies.
On the master pane of the Protection Policies screen, select a policy.
Select Edit from the Actions menu.
Make required changes and click OK.
Remove protection policy
Procedure
1.
2.
3.
4.
Click the HPE Recovery Manager Central main menu and then click Protection Policies.
On the master pane of the Protection Policies screen, select a policy.
Select Remove from the Actions menu.
Click Yes, Remove.
Creating a protection policy
49
Snapshots
I want to ...
•
•
•
•
•
•
•
•
•
•
•
Create local snapshot on page 52
Edit snapshot on page 54
Mount snapshot on page 54
Remount snapshot on page 56
Unmount snapshot on page 56
Remove snapshot on page 56
Restore using a database read-only snapshot
on page 57
Restore using a database read-write
snapshot on page 59
Performing manual recovery of Oracle
database post restore operation on page 61
Clone database on page 62
Remove cloned database on page 63
Learn More...
•
•
•
•
•
About snapshots on page 50
About mount snapshot on page 54
Snapshot screen details on page 51
About snapshot meta data on page 54
About cloning databases on page 61
About snapshots
RMC-O allows Oracle database administrators to create, schedule, and manage application consistent
snapshots on HPE 3PAR StoreServ. A database snapshot consists of multiple snapshots of underlying 3PAR
virtual volumes used by Oracle datafiles, archive log destination, or both, depending on the option that you
specify. RMC-O enables you to create the following type of snapshots:
•
•
•
•
Online — A point-in-time image of a database, which is taken while the database is open or online. The
database is put in backup mode before the snapshot is created. After the snapshot is complete, the
database is taken out of backup mode.
Offline — A point-in-time image of a database, which is taken while the database is closed or offline.
Datafile — A point-in-time image of the datafiles of all databases, which is taken while the database is
open or online. The database is put in backup mode before the snapshot is created. This backup only
takes a snapshot of only the datafiles and not archives log destination. A snapshot created with this option
is only useful when archive log files generated during the creation of the snapshot are also available.
Archive log — A point-in-time image of archive log destination of the database, which is taken while the
database is open or online.
After creating a snapshot, you can perform the following actions using the Action menu on the Oracle
Databases > Protection View screen:
•
•
•
•
•
•
50
Edit snapshot — Edit details like snapshot name, description, and schedule.
Mount snapshot — Mount a snapshot on the backup server for off-host processing purposes, such as
backup and database cloning.
Unmount snapshot — Unmount the file system where a snapshot is mounted or drops ASM disk groups if
ASM is used. The read-write snapshot is removed along with any components that are created during the
mount snapshot stage.
Remove snapshot — Remove an existing snapshot from the HPE 3PAR StoreServ Storage system.
Restore snapshot — Restore the database with the previous snapshot. The meta data (CONTROLFILE,
PFILE, password files, and so on) is also restored.
Protect snapshot — Protects an existing snapshot.
Snapshots
•
•
Clone database — Create a single-instance database or starts up a cloned database in Mounted mode for
backup (RMAN) purposes. You can use a single-instance database for any off-host processing purpose.
Remove cloned database — Remove a cloned database. The database-related files (Oracle parameter
file, control files and redo logs) are removed. The read-write snapshot remains mounted.
If you know RMC Recovery Set concepts, the first database snapshot creates two recovery sets. One for
datafile (RMCO_<dbname>_datafile ) and the other for archivelogs (RMCO_<dbname>_archlog ).
IMPORTANT:
Perform all the operations from the RMC-O user interface only. Do not attempt to modify or delete RMCO entities from Recovery Sets or Snapshots Sets. Exercise this caution as this operation may lead to
backups or snapshots becoming unusable.
Snapshot screen details
Type
Create snapshot
Creates a local or remote snapshot.
General
Oracle database name
Displays the name of the database on which you want to create the snapshot.
Snapshot name
Name of the snapshot.
Snapshot description
Description of the snapshot.
Backup method
Online (Hot)
Creates a point-in-time image of the database while the database is open.
Archive logs only
Creates a point-in-time image of the database’s archive log destination while the database is open.
Offline (Cold) backup
Takes a point-in-time snapshot image of the database while the database is closed.
Datafile only
Takes a point-in-time snapshot image of the datafiles of a database while it is open.
Time constraints
Expiration time
A time-based policy in which an internal scheduler automatically removes a snapshot by once the
expiration time is reached. You can enter a value between 1 to 43,800 hours (1–1825 days). For example,
if the expiration time is one month, then the snapshot that reaches the expiration time is removed from the
HPE 3PAR StoreServ Storage system automatically. The system has all snapshots for last month. To
update the status of such snapshots in RMC-O catalog, you have to perform a database Refresh.
Retention time
To specify a retention time, specify a value between 1 to 336 hours (1–14 days). If a snapshot is protected
by retention time, you can remove it only after the retention time ends.
Snapshot screen details
51
NOTE:
If you want to override the Expiration time or Retention time values that are already assigned in the
protection policy, you must specify them in the user interface dialog while creating a snapshot. The
values that you specify in the Create Snapshot dialog are applicable to the particular snapshot and
take the highest precedence.
Remote Copy
NOTE:
This section is available only for remote snapshots.
Retain local snapshot
Select to create a local and remote snapshot as per the selected source target HPE 3PAR Remote Copy
configuration. If you select the check box, you can perform all operations on local snapshots and limited
operations, except restore on target snapshots. If you clear the check box, RMC-O creates a target
snapshot only. No local snapshot is created.
Target RMC appliance IP address/host name
IP address or host name of the remote RMC appliance. This operation fetches all valid target systems
using the IP address of the RMC appliance. If HPE 3PAR StoreServ is not configured on the RMC
appliance, you must add an HPE 3PAR StoreServ on the RMC appliance.
Target storage system
List of all storage systems currently registered with target RMC appliance.
Schedule
Schedule
Schedules a backup task.
Scheduler name
Name of the schedule.
Scheduler description
Description for the schedule.
Frequency
Select the schedule frequency, for example, Weekly, Daily, Hourly, Minutes, Monthly, Yearly, or One
off.
Start time
Time for the scheduled snapshot to start.
Create local snapshot
Prerequisites
•
•
•
•
52
An Oracle server and database must be registered.
The database must be running in archive log mode and automatic archiving must be enabled to create an
online, datafile, or archive log snapshots.
Datafiles and archive logs must reside on separate HPE 3PAR virtual volumes, not on the local file system.
The online redo logs and control files must 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 HPE 3PAR virtual volumes.
Create local snapshot
•
•
•
•
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 must not reside on the same ASM disk
groups used by the datafiles and archive logs to avoid being rolled back when the snapshot is rolled back.
Also, the ASM instance must not share the datafile and archive disk log group for storing the server
parameter file (SPFILE)
Do not share ASM disk groups between different databases.
If using Logical Volume Manager (LVM) on Linux, the Oracle datafiles and archive logs must reside on
separate LVM volume groups. In addition, online redo logs and control files must not reside on LVM
volume groups that are used by Oracle datafiles and archive logs. However, the online redo logs and
control files can reside on the same LVM volume group.
If the database is an RAC database, all RAC instances must share archive log destinations (same cluster
file systems or same ASM disk groups). To ensure that the database is running in automatic archive log
mode, use SQL*Plus utility to ensure the Database log mode is Archive Mode and that Automatic archival
is Enabled, as in the following example:
Connected to:
Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production
WWith the Partitioning, OLAP, Data Mining and Real Application Testing
options
SQL> archive log list
Database log mode
Automatic archival
Archive destination
Oldest online log sequence
Next log sequence to archive
Current log sequence
Archive Mode
Enabled
/nonrc_arch
196
198
198
Creating a local snapshot
Procedure
1.
2.
3.
4.
5.
On the master pane of the Databases screen, select a database.
Select Create Snapshot from the Actions menu.
Select Local in Create Snapshot.
Enter the snapshot name and description.
Select the backup method for the database, for example Online (Hot) backup, Archive log only, Offline
(Cold) backup, or Datafile only.
6. Enter the policy expiration time and retention time.
7. To set the frequency of the snapshot, select Schedule and perform the following steps:
a. Enter the schedule name and description.
b. Set the schedule frequency. For example, Daily, Minutes, Weekly, Monthly, Yearly, or OneOff.
c. Enter the start time.
d. Enter the Recurrence.
NOTE:
The minimum recommended interval between two subsequent snapshots is 15 minutes.
8. Click OK.
9. To view the snapshot creation progress, navigate to the Activity pane.
Snapshots
53
About snapshot meta data
As part of snapshot creation process, CONTROLFILE, pfile, and password files (if applicable) are
captured. These files can be used during the snapshot or express restore operation. A snapshot is in
state if meta data collection fails. Ensure that you rectify the errors so that the future snapshots are not
created in the
state.
Edit snapshot
Procedure
1.
2.
3.
4.
5.
6.
On the master pane of the Oracle Databases screen, select a database.
Select Protection View from the View selector menu.
Select the snapshot that you want to edit and click Action > Edit.
In General, edit either Name or description, or both.
In Time Constraints, edit either Expiration time or Retention time, or both.
Click OK.
About mount snapshot
The operation mounts an existing snapshot created by RMC-O on the backup server. The mounted snapshot
can be used for off-host processing purposes such as backup or database cloning.
The following restrictions apply when mounting a database snapshot:
•
•
•
The snapshot must be Available.
The same snapshot cannot be mounted concurrently on different backup servers or on different mount
points within a backup server.
If the database files reside on ASM disk groups, restrictions apply as follows:
◦
•
•
Ensure that the backup host has +ASM instance created and configured properly for RMC- O mount or
unmount operations being able to use the existing +ASM instance.
◦ One snapshot per database can be mounted on the backup server. Snapshots from different databases
can be mounted concurrently.
Only one snapshot per database can be mounted at any time on the backup server.
For online backup and archlog backup, all MANDATORY archive log destinations are mounted. If no
MANDATORY archive log destinations are found, all OPTIONAL archive log destinations are mounted.
Mounting a snapshot involves the following actions:
•
•
•
•
•
Creates a read-write snapshot of the original read-only snapshot.
Imports the read-write snapshots to the backup server.
Imports snapshot LVM volume groups and activates all corresponding LVM snapshot volumes if the
database files reside on LVM volumes.
For snapshots from an ASM-managed database, if an ASM instance exists and is up on the backup
server, then all diskgroups from the snapshots are mounted in this ASM instance.
Mounts all snapshot file systems if the database files reside on file systems.
Mount snapshot
Prerequisites
•
•
54
The snapshot must be in the Available status to be mounted.
The same snapshot cannot be mounted concurrently at different mount points.
About snapshot meta data
•
•
If Oracle datafiles and archive logs reside on LVM logical volumes, RMC-O allows only one snapshot of
the same database to be mounted. Unmount a mounted snapshot before mounting a different snapshot.
If the database files reside on ASM disk groups, then depending on the ASM database version installed on
the backup server, one snapshot per database can be mounted at any time on the backup server.
However, snapshots from different databases can be mounted concurrently. This process prevents an
Oracle ASM instance on the backup server from hanging due to some ASM's idle processes still holding a
snapshot’s devices, even though the corresponding ASM disk groups are dropped.
NOTE:
The ASM version on the backup server must be equal or higher than the ASM version on the
database server.
•
•
On Linux systems, if the database files reside on OCFS2 1.4.1 or above file systems, RMC-O supports
multiple snapshots per database being mounted at the same time. For versions lower than OCFS2 1.4.1,
only one snapshot per database can be mounted at any time on the backup server.
If device mapper multipath is used, the Oracle asmlib
/etc/sysconfig/oracleasm
file must contain the following lines so that
asmlib
scans only device mapper devices (dm devices) and not SD devices:
•
◦ ORACLEASM_SCANORDER="dm"
◦ ORACLEASM_SCANEXCLUDE="sd"
In Linux, if you are using the device mapper multipath, the supported disk formats on the database server
are:◦
–
–
–
–
–
/dev/mapper/diskname
/dev/mapper/aliasname
/dev/mapper/mpathn
/dev/dm-n
/dev/mpath/diskname
◦
◦
◦
Raw disks (/dev/raw/raw) are not supported.
Each OS disk can only have maximum one partition.
For
ext3/ext4 file systems, the journal devices must be within the same file systems.
IMPORTANT:
These prerequisites are applicable only if you are mounting a snapshot using command-line interface.
Mounting a snapshot
Procedure
1.
2.
3.
4.
5.
6.
On the master pane of the Oracle Databases screen, select a database.
Select Protection View from the View selector menu.
Select the snapshot that you want to mount and click Action > Mount.
To select the backup server from the list, click Select.
Enter the mount point where you want to mount the snapshot on the backup server.
Click Mount.
Snapshots
55
Remount snapshot
Prerequisites
•
•
Ensure that the snapshot is either mounted or cloned to a database before performing a remount
operation.
Ensure that the snapshot volumes on the HPE 3PAR StoreServ systems are still exported.
Remounting a snapshot
A remount operation is performed when the backup server undergoes a restart along with mounted
snapshots.
Procedure
1.
2.
3.
4.
5.
On the master pane of the Oracle Databases screen, select a database.
Select Protection View from the View selector menu.
Select the snapshot that you want to remount and click Action > Remount.
Click Remount on the Remount Snapshot dialog.
Click Yes, Remount and monitor the activity pane for the task status.
NOTE:
If the remounted snapshot was cloned to a database, post remount operation manually STARTUP the
database.
Unmount snapshot
Prerequisites
The snapshot must be in the Mounted status to be unmounted.
IMPORTANT:
This prerequisite is applicable only if you are unmounting a snapshot using command-line interface.
Unmounting a snapshot
Procedure
1.
2.
3.
4.
On the master pane of the Oracle Databases screen, select a database.
Select Protection View from the View selector menu.
Select the snapshot that you want to unmount and click Action > Unmount.
Select Force unmount if the database contains partially mounted virtual copies or if the cloned database
is not functioning properly.
5. Click Unmount.
Remove snapshot
Prerequisites
The snapshot must be in the Available status to be removed.
IMPORTANT:
This prerequisite is applicable only if you are removing a snapshot using command-line interface.
56
Remount snapshot
Removing a snapshot
WARNING:
Removing a snapshot permanently removes the snapshot from the system.
Procedure
1.
2.
3.
4.
On the master pane of the Oracle Databases screen, select a database.
Select Protection View from the View selector menu.
Select the snapshot that you want to remove and click Action > Remove.
Click Yes, Remove.
Restore using a database read-only snapshot
Prerequisites
The database instance must be closed for this operation. If the database is an RAC database, all RAC
instances must be closed.
Procedure
1.
2.
3.
From the database server, shut down the database. If the database is a Real Application Clusters (RAC)
database, all RAC instances must be shut down.
From the database server, unmount all database file systems if they are on file systems.
Example:
# umount /oradata
4.
5.
From the database server, drop the database ASM disk groups if ASM is in use.
Example:
SQL>drop diskgroup <disk_group> including contents;
6.
7.
From the database server, deport/export the database volume groups if volume groups are in use.
Depends on volume groups involved, the deport/export volume group commands are slightly different,
the following are some of examples:
- For Linux logical volume groups, use the following command to deactivate
logical volumes and export volume groups:
# lvchange -an /dev/ <vgname>/<lvname>
# vgexport <vgname>
Example:
# lvchange -an /dev/rh6lvm-data/lvol0
# lvchange -an /dev/rh6lvm-data/lvol1
# vgexport rh6lvm-datavg
8. On the master pane of the Oracle Databases screen, select a database.
9. Select Protection View from the View selector menu.
10. Select the snapshot that you want to restore on the database and click Action > Restore.
Restore using a database read-only snapshot
57
CAUTION:
The online redo logs and control file must not reside on the same virtual volumes used by the
datafiles and archive logs. Otherwise, they are rolled back along with the datafile and archive log
virtual volumes.
11. Select the database restore type, clear the Read/Write flag if it is selected and click Yes, Restore and
wait for the operation to finish.
12. Perform a rescan of the devices on the Application Server.
a. You may use
rescan-scsi-bus.sh
from
sg3_utils
package.
Or,
b. For iSCSI connections, use appropriate
iscsiadm
commands.
13. Post rescan operation, execute oracleasm scandisks if you use ASMLib. You may validate the ASM
disks with the command oracleasm querydisk <diskname> .
NOTE:
You can select to restart the Application Server if you do not want to perform a manual rescan or
where rescan operation fails.
14. From the database server, activate logical volumes and import/start volume groups.
15. Example:
#
#
#
#
For Linux logical volumes:
vgscan
vgimport rh6lvm-datavg
lvchange -ay /dev/rh6lvm-datavg/lvol0
lvchange -ay /dev/rh6lvm-datavg/lvol1
16. From the database server, perform file system check, and then mount the database file systems if
database files are on file systems.
17. Example:
# fsck -y /dev/maper/mpathc
# mount /dev/mapper/mpathc /oradata
18. From the database server, mount database ASM disk groups if ASM is in use.
19. Example:
SQL>alter diskgroup <disk_group> mount
20. From the database server, follow Oracle documentation to perform media recovery to recover the
database.
58
Snapshots
NOTE: If both datafile and archive log volumes are rolled back, then an incomplete recovery must
be performed to recover the database on the database server. The binary or ASCII control file is
present in the meta data folder of the target server as part of the restore operation.
Restore using a database read-write snapshot
First, perform step 1 to 4 from the section Restore using a database read-only snapshot on the database
server for the primary database. Then perform the following steps:
Procedure
1.
2.
3.
4.
5.
6.
7.
8.
From the backup server, if a clone database is created, shutdown the database. If the clone instance is
part of a Real Application Clusters (RAC) database, all RAC instances must be shut down.
From the backup server, unmount all file systems which are mounted using the read-write snapshot
volumes.
Example:
# umount /oradata
From the backup server, unmount the ASM diskgroups contained in the read-write snapshot volumes if
ASM is in use.
Example:
SQL> alter diskgroup dgname dismount;
From the backup server, depends on volume groups involved, the deport/export volume group
commands are slightly different, the following are some examples:
For Linux logical volume groups, use the following command to deactivate
logical volumes and export volume groups:
# lvchange -an /dev/rh6lvm-data/lvol0
# lvchange -an /dev/rh6lvm-data/lvol1
# vgexport rh6lvm-datavg
9. On the master pane of the Oracle Databases screen, select a database.
10. Select Protection View from the View selector menu.
11. Select the snapshot that you want to restore on the database and click Action > Restore.
CAUTION:
The online redo logs and control file must not reside on the same virtual volumes used by the
datafiles and archive logs. Otherwise, they are rolled back along with the datafile and archive log
virtual volumes.
12. Select the database restore type, select the Read/Write flag, and click Yes, Restore and wait for the
task to finish.
13. Copy the CONTROLFILE and any other meta data from the cloned database manually to the Application
server before attempting a database recovery. The meta data restored along with the snapshot pertains
to the snapshot’s point in time and does not contain the changes of the cloned database. However, for
snapshots that were mounted and not cloned to a database, use the snapshot meta data provided by
RMC-O.
14. Remount the snapshot and startup the cloned database.
IMPORTANT:
If the cloned database failed to start, perform step 11 to step 15 on the backup server.
15. From the HPE 3PAR StoreServ Storage system, if needed, export the read-write snapshot volumes back
to the backup servers.
Restore using a database read-write snapshot
59
16. Example:
17. cli>createvlun rmc-0014832-rw-160311062003366 auto pilot
18. Select the database restore type, clear the Read/Write flag if it is selected and click Yes, Restore and
wait for the operation to finish.
19. Perform a rescan of the devices on the backup server.
20. You may use rescan-scsi-bus.sh from sg3_utils package.
a. Or,
b. For iSCSI connections, use appropriate
iscsiadm
commands.
21. Post rescan operation, execute oracleasm scandisks if you use ASMLib. You may validate the ASM
disks with the command oracleasm querydisk <diskname> .
NOTE:
You can select to restart the backup server if you do not want to perform a manual rescan or where
rescan operation fails.
22. From the backup server, if needed, import disk groups contained in the read-write snapshot volumes and
activate logical volumes and import/start volume groups:
For Linux
# vgscan
# vgimport
# lvchange
Example:
# vgscan
# vgimport
# lvchange
# lvchange
logical volumes:
<vgname>
-ay /dev/ <vgname>/<lvname>
rh6lvm-datavg
-ay /dev/rh6lvm-datavg/lvol0
-ay /dev/rh6lvm-datavg/lvol1
23. From the backup server, if needed, mount the file systems if the read-write snapshot contains file
systems.
24. Example:
25. # mount /dev/mapper/mpathc /oradata
26. From the backup server, if needed, mount database ASM disk groups if ASM is in use and contained in
the read-write snapshot volumes
27. Example:
28. SQL>alter diskgroup <disk_group> mount;
29. From the backup server, bring up the clone database if needed.
NOTE:
Remote copy groups must be stopped before initiating a snapshot restore operation.
30. Perform step 13 to step 18 on an application server instead of a backup server. Use the base volumes
wherever read-write snapshot volumes are mentioned in the steps.
31. Perform a database recovery using the CONTROLFILE of the clone database or using the snapshot meta
data contents.
60
Snapshots
Performing manual recovery of Oracle database post restore
operation
Prerequisites
Ensure that you have a successful Snapshot or Express Protect restore operation before performing a
manual recovery.
Procedure
1. Extract the CONTROLFILE the meta data file path specified in RMC-O Restore user interface dialog using
the following commands:cd <meta data file path> tar -xvf <sid>.gz gunzip
controlfile.gzThe backed up binary CONTROLFILE is unzipped to <meta data file path>/
controlfile.
IMPORTANT:
Change the ownership of the extracted CONTROLFILE to an oracle user.
2. Connect to RMAN (rman target /) to restore the binary CONTROLFILE and run the recover database
commands as follows:RMAN> startup nomount RMAN> restore controlfile from '<meta
data file path>/controlfile'; RMAN> shutdown immediate RMAN> exit
3. Connect to the SQL prompt to run the following set of commands:SQL> startup mount SQL>
recover database using backup controlfile until cancel; SQL> alter database
open resetlogs; SQL> exit
4. You may use UNTIL TIME or UNTIL SCN or UNTIL SEQUENCE clauses in the commands described in
this procedure for point-in-time recovery. When prompted for archive logs, you may use the AUTO or
CANCEL option, based on your recovery needs. If there is any mismatch in the path of prompted archive
logs, specify the paths to the actual archive logs explicitly in the prompt so that recovery succeeds. Once
the recovery completes, a new form of your database is started.
NOTE:
Restoring CONTROLFILE is not mandatory if the new form of your database has not changed.
About cloning databases
The clone procedure 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 snapshot, used for cloning a database, must be either an online or offline snapshot (created using online
or offline option respectively). The snapshot must have been mounted before running this command.
You can create a clone database using an ASCII or binary control file which was saved as meta data at the
time the snapshot was created. Using an ASCII control file is more flexible as it allows you to change
database instance name as well as the structure of the database.
When using an ASCII control file, the structure of the clone database is not required to be the same as the
structure of the original database. Therefore the snapshot can be mounted at any mount point. However,
because the snapshot does not contain online redo logs and control files, their locations can be specified
using the user interface (can be one or more directories or ASM diskgroups, depends on desired
multiplexing). If the locations of the redologs and control files are not specified, they are created at the
repository location for the snapshot (/opt/hpe/rmc/oracle/data/<host>.ora.<sid>/<snap_id>).
Performing manual recovery of Oracle database post restore operation
61
When using a binary control file, the structure of the clone database must be the same as the structure of the
original database. Therefore, the snapshot must be mounted at '/' if the datafiles and archive logs are on file
systems. Also, because the snapshot does not contain redologs and control files, the same directory structure
or same ASM diskgroups for redologs and control files must be precreated on the backup server.
When you use an offline snapshot to clone a database, either with a binary control file or an ASCII control file,
the cloned database uses the same archive log destination as that of the primary database. If archive log
mode is enabled, you must precreate the archive log destination. The offline snapshot does not contain the
archive log destination.
When creating a clone database for backup (RMAN) purposes, the database is started in MOUNTED mode
using the binary control file from the repository without recovering the database. This can be achieved by
clearing the Automatically Recover the database option.
A clone database can be created with or without automatic recovery (applying archivelogs from the snapshot).
If recovery is selected, the clone database is open with reset log, otherwise, the clone database is in mounted
status. The primary database and the standby database cannot coexist on the same backup server.
RMC-O does not create snapshots for virtual volumes used by Oracle database temporary files, to be
consistent with Oracle's backup procedure.
NOTE:
The minimum memory requirement on the backup server must be equal to the memory present on the
application server. The cloned database uses the same set of memory-related parameters (SGA, PGA,
and so on) configured on the application database.
Clone database
Prerequisites
•
•
The snapshot used for cloning a database must be either an online or offline snapshot.
The snapshot must be in the Mounted state. If the snapshot is not mounted, the
Clone Database
option on the GUI is unavailable.
Cloning a database
Procedure
1.
2.
3.
4.
On the master pane of the Oracle Databases screen, select a database.
Select Protection View from the View selector menu.
Select the snapshot that you want to use for cloning the database and click Action > Clone Database.
Provide the following details:
•
•
•
Clone database SID — Oracle SID of the cloned database. The maximum character limit for SID is 12.
HPE recommends limiting the SID character length to 8 to avoid truncation of other parameters like
NAME (V$DATABASE).
Clone database home — ORACLE_HOME on the backup server used for cloning.
Control file — ASCII or binary control file that you want to use for cloning the database.
TIP:
Using an ASCII control file is more flexible as it allows you to change database instance name as
well as the structure of the database.
62
Clone database
•
Redo log destinations — A comma-separated list of directories or ASM diskgroups (for multiplexing)
to store the new online redologs and control files of the clone database. The directories or ASM
diskgroups must have enough available space to hold new online redo logs and control files. 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 than the original database when creating a clone
database. Otherwise, the extra redo log multiplex location will be ignored.
• Automatically recover the clone database — Automatically recover the cloned database using all
available archivelogs that exists with the snapshot.
• Use Large Pages — Override mechanism used to indicate whether the USE_LARGE_PAGES
initialization parameter from the application database has to be used during the cloning process.
5. Click OK.
NOTE:
If any of the optional parameters are not specified, the default values configured on the application
database is used.
Remove cloned database
Procedure
1.
2.
3.
4.
5.
On the master pane of the Oracle Databases screen, select a database.
Select Protection View from the View selector menu.
Select the snapshot that was used to clone the database and click Action > Remove cloned database.
To shut down the cloned database (if it is running), select Force Remove .
Click Remove.
Remove cloned database
63
Snapshots with remote copy
I want to ...
•
•
•
•
Create remote snapshot on page 72
Set up remote copy on page 70
Set up remote appliance on page 70
Set up remote copy volume groups in HPE
3PAR StoreServ on page 71
Learn More...
•
•
•
•
About remote copy on page 64
Remote copy configuration on page 65
Remote Copy Requirements for RMC-O on page
64
Configuring remote copy environment on page
17
About remote copy
HPE 3PAR Remote Copy Software helps you safeguard against disasters by keeping copies of data on a
separate server, which can be placed at a remote location. For example, you can recover the data stored on a
server at a location impacted by a disaster from a server at another location not impacted by the disaster.
RMC-O protects Oracle databases by copying Oracle datafiles and archive log virtual volumes from one HPE
3PAR StoreServ Storage system (local or primary) to another (remote or secondary). It then creates a
consistent snapshot image of an Oracle database on the local and remote HPE 3PAR StoreServ Storage
systems. For more information on HPE 3PAR Remote Copy Software, see the HPE 3PAR Remote Copy
Software User Guide.
IMPORTANT:
•
•
Ensure that the source and target RMC VSAs Network Interface -1 (NIC 0) is configured with valid IP
address for remote copy to function with RMC-O. For more information on how to configure multi
NIC, see the HPE Recovery Manager Central User Guide.
Ensure you refer Configuring RMC for Remote Copy section in HPE Recovery Manager Central User
Guide before working on remote copy operations.
RMC-O supports remote copy in synchronous, asynchronous, and asynchronous periodic mode. If you are
using synchronous, asynchronous, or asynchronous periodic remote copy, you can create RMC-O snapshots
even if the policies on the source and target RMC-O servers do not match. If the policies do not match, the
snapshots use the policies on the source side RMC-O server. If there is a primary site disaster, the remote
snapshots created at the secondary site before disaster can be used to restore the data through restore
operations. To achieve this, ensure that the Oracle server instance or database is online using the secondary
site LUNs.
Remote Copy Requirements for RMC-O
Before using the RMC-O Remote Copy utility, the following must be set up:
•
•
Primary or local and secondary or remote RMC-O servers must be correctly configured.
Remote Copy links among nodes within the servers must be set up and Remote Copy targets related to
the servers must be created. RMC-O only supports the
mirror_config
•
•
•
64
policy (default) for the involved Remote Copy targets.
If LVM is used, all volumes that are in the same disk group as the datafiles or archive log destinations must
be admitted to the same Remote Copy group.
The Remote Copy groups must be started and in synchronized status. For asynchronous streaming,
datafile and archive log volume must be in different Remote Copy (RC) group.
For Synchronous Long-Distance Remote Copy setups:
Snapshots with remote copy
◦
•
The Oracle datafile and archive log virtual volumes can be on the same or separate Remote Copy
groups.
◦ Each Remote Copy group must have two targets. The same set of database volumes must belong to
two Remote Copy groups (with the same name). One group is for the asynchronous periodic target,
and the other group is for the synchronous target.
◦ The Oracle online redo log volumes must be included in one of the database Remote Copy groups,
excluding the Oracle datafile and archive log Remote Copy groups. This approach allows a successful
failover if needed. If the Oracle online redo log volumes are included in either the Oracle datafile
Remote Copy group or the archive log Remote Copy group, RMC-O will fail.
To set Remote Copy targets, links, and groups, see the HPE 3PAR Remote Copy Software User Guide.
After Remote Copy targets, links, and groups are set up, an RMC-O configuration file must be created. There
are two ways to create a configuration file.
On the backup server:
•
To start the RMC-O Graphical User Interface (GUI), open browser, type
https://RMC_IPaddress/
Or
•
To start the Command Line Interface (CLI), run
/opt/hpe/rmc/oracle/rmco_cli/scripts/rmc_config.py.
Remote copy configuration
A remote copy configuration typically involves two HPE 3PAR StoreServ Storage systems; a local or primary
system and a remote or secondary system. For all modes that include synchronous, asynchronous, and
asynchronous periodic streaming, snapshots are not created for redo log volumes. The synchronization
between the local and remote systems can be in the following modes.
•
Synchronous — In this mode, Oracle database virtual volumes between the local and remote HPE 3PAR
StoreServ Storage systems are always in synchronization. However, the copy of the Oracle database on
the remote server is considered inconsistent and can be only used for crash recovery. RMC-O can be
used to create a consistent snapshot image of the database virtual volumes on the local and remote HPE
3PAR StoreServ Storage systems. The database is placed in backup mode before the snapshot being
taken. RMC-O leverages the Oracle backup mode to freeze the I/O at the application level and to take
point in time snapshots.
Remote copy configuration
65
•
66
Figure 6: Synchronous remote copy configuration (Use one of the following diagrams)
Asynchronous periodic — In this mode, RMC-O initiates synchronization between the database virtual
volumes between two HPE 3PAR StoreServ Storage systems and creates a consistent database snapshot
on the local and remote systems. RMC-O leverages the Oracle backup mode to freeze the I/O at the
application level and to take point in time snapshots.
Snapshots with remote copy
•
Figure 7: Asynchronous periodic remote copy configuration (Use one of the following diagrams)
Asynchronous periodic streaming— This mode eliminates the compromise between performance and
the level of data protection. HPE 3PAR Remote Copy asynchronous periodic streaming helps you to
execute a data protection plan that includes a minimal RPO and protect data for replication distances up to
10ms round-trip latency.
Snapshots with remote copy
67
•
68
Figure 8: Asynchronous periodic streaming remote copy configuration (Use one of the following diagrams)
Synchronous long distance— In this mode, database virtual volumes are synchronized from one system
to the two other systems. This configuration involves three HPE 3PAR StoreServ Storage systems. One is
synchronized using synchronous mode. The other is synchronized using asynchronous periodic mode.
RMC-O leverages the Oracle backup mode to freeze the I/O at the application level and to take point in
time snapshots. For synchronous long-distance remote copy groups, RMC-O does not create Remote
virtual copies for the synchronous, asynchronous, and periodic target LUNs simultaneously. Remote
snapshot creation for the target LUN depends on the type of remote copy, for example synchronous,
asynchronous, or periodic configured for Oracle instance or database.
Snapshots with remote copy
Figure 9: Synchronous long-distance remote copy configuration (Use one of the following diagrams)
When you synchronize data between a production system (the remote copy primary system) on one site and
the remote copy backup system at another site, the systems involved perform the following steps:
•
•
For synchronous or asynchronous remote copy groups, HPE RMC-O leverages the coordinate snapshot
technology provided by the HPE 3PAR StoreServ to create remote virtual copies (Internally uses RMC to
connect with StoreServ). The local RMC-O VM server saves the time stamp record of the snapshots of a
source LUN and remote RMC-O RMC VM server saves the same time stamp record of a remote snapshot
in their respective repositories.
For periodic remote copy groups, after the remote snapshots are created for the target LUNs, the remote
RMC-O interface server repository is updated with the time stamp of the remote snapshot created. The
local RMC-O RMC VM server does not retain any record of the snapshot time stamp for the source LUNs
of the remote copy group in its repository.
Snapshots with remote copy
69
NOTE: You can use the Expiration policy settings of RMC-O. In this case, HPE 3PAR StoreServ
removes the retained snapshots after the expiration period elapses.
•
For synchronous long-distance remote copy groups, snapshot creation and timestamp retention in local
and remote RMC-O RMC VM servers depends on the target HPE 3PAR StoreServ during RMC-O
snapshot creation. If you select the target HPE 3PAR StoreServ that has synchronous relationship with the
source, the behavior is same as that of synchronous or asynchronous remote copy groups. If you select
the target HPE 3PAR StoreServ that has periodic relationship with the source, the behavior is same as that
of periodic remote copy group.
Set up remote copy
Procedure
1. Install and configure remote copy. For information on installation and configuration, see the HPE 3PAR
Remote Copy Software User Guide.
2. Create a remote copy volume group for testing after you have set up remote copy on two HPE 3PAR
StoreServ Storage systems.
3. Configure the remote copy volume group for synchronization in synchronous, asynchronous, or
asynchronous periodic mode with appropriate periodic value as supported by HPE 3PAR StoreServ.
4. Set up a remote appliance. For information setting up a remote appliance, see Set up remote appliance
on page 70.
5. In the source RMC-O GUI, register the Oracle production server and remote copy instances or database.
6. In the target RMC-O GUI, register the Oracle remote copy instances or database. This step is mandatory if
you are setting the target policy in advance. Otherwise, the default policy is used on the target RMC-O for
given instance or database.
7. For synchronous long-distance remote copy configuration, repeat Step 6 on both target RMC-O GUI.
NOTE:
•
•
There is no separate configuration for synchronous long-distance remote copy configuration. If the
Oracle server instance or database is configured for synchronous long-distance remote copy, you
must select the required target interface server to create a synchronous or periodic snapshot.
You can also create a local or remote copy snapshot from the remote site RMC-O RMC VM server
configured from RMC-O GUI. However, HPE does not recommend you to do so. Manage or create a
remote copy snapshot from the source RMC-O GUI.
Set up remote appliance
Prerequisites
Registering the target interface server is mandatory for setting up remote copy configuration.
Setting up remote appliance
Procedure
1. From the main menu, select Remote Appliance.
2. Click Register Appliance on the master pane or select Register from the Actions menu.
3. Perform the following steps:
a. Enter the IP address or the host name of the appliance.
b. In Remote, enter the remote user name and password to register with the appliance.
70
Set up remote copy
c. In Local, enter the local user name and password to register with the appliance.
d. To register the local appliance as a remote appliance, select Use Local Appliance to Manage Remote
Array.
4. Click Add.
Set up remote copy volume groups in HPE 3PAR StoreServ
RMC-O supports single remote copy group for datafile and archlog files. It also supports separate remote
copy groups for datafile or archlog files.
Procedure
1. Identify the virtual volumes that contain the datafile and archlog files to be copied.
2. Add virtual volumes belonging to the datafile and archlog log files to the primary remote copy volume
group.
CAUTION:
Do not disperse files from one datafile or archlog files over multiple primary remote copy volume
groups. RMC-O does not support database and log files from one database existing in any location
other than the one primary remote copy volume group created for that instance or database.
3. Synchronize the remote copy primary and secondary volume groups.
Database configuration in failover scenarios
This section describes the Remote Copy groups and application server configurations to be performed on the
remote site to support HPE 3PAR StoreServ failover. This feature can be used to start an Oracle database on
an alternate Application server registered with a remote appliance.
NOTE:
•
•
The CONTROLFILE must be available on the remote site during a failover. Configure the
CONTROLFILE inside a remote copy group (other than datafile, archivelog) or perform a manual
backup periodically.
If the primary database is a RAC, HPE recommends you to follow the steps described in Configuring
a cloned database procedure. This approach is recommended as the CONTROLFILE may not be
interoperable among the servers configured on these sites.
Configuring a cloned database
Configuring base volumes on a failover site
Procedure
1.
2.
3.
4.
5.
Configure the Remote Copy groups (datafile, archivelogs, CONTROLFILE and REDO logs) preferably
on a sync mode according to the steps described in the section Remote Copy Configuration.
Register the alternate server as an application server on the remote RMC appliance.
Export the base volumes containing the database to the alternate application server registered in step 2
once the arrays have failed over.
Restart the application server so that the exported volumes are discovered.
Perform a rescan of the devices on the Application Server.
a. You may use rescan-scsi-bus.sh from sg3_utils package. Or,
b. For iSCSI connections, use appropriate iscsiadm commands.
Set up remote copy volume groups in HPE 3PAR StoreServ
71
6.
Post rescan operation, execute oracleasm scandisks if you use ASMLib. You may validate the ASM
disks with the command oracleasm querydisk <diskname> .
NOTE:
You can select to restart the Application Server if you do not want to perform a manual rescan or
where rescan operation fails.
7.
8.
Mount the ASM disk groups or file systems (including the volume groups and LVMs, if configured) and
start the database.
Register the database that is now hosted on the alternate application server.
TIP:
You can consider to protect the newly registered database by creating and associating appropriate
protection policies.
9.
If desired, perform a failback operation on the HPE 3PAR StoreServ systems when the primary site is
available.
10. Export the base volumes on the primary site to the original application server and restart the server or
perform a manual rescan operation, so that the exported volumes are discovered and the databases are
restarted.
Create remote snapshot
Prerequisites
•
•
•
•
•
•
•
•
RMC-O license and Remote Copy license must be available on all registered HPE 3PAR StoreServ
Storage systems.
The remote copy group volumes must be in Synced and Started state.
All RMC appliances and Oracle production servers (Primary and Target) must communicate with each
other. It is optional to have network connectivity between target RMC VM and Oracle production server to
create remote copy snapshot on the target RMC VM.
Use RMC appliance NIC 0 IP address for creating a remote copy snapshot. If you have configured other
NICs, use NIC 0 IP address and ensure that it is configured properly.
The IP address of the RMC appliance must be added using the Remote Appliances feature in RMC. If
the remote copy group is configured for synchronous long-distance configuration, add both RMC-O
appliances. For more information, see Set up remote appliance. If you are using single RMC instance for
all remote copy group modes, add the IP address of the local RMC appliance using the Remote
Appliances feature.
The source and target HPE 3PAR StoreServ must be added using the Storage Systems feature in RMC.
This addition must be done for the local RMC-O appliance. If you are using single RMC instance, you must
add source and target storage systems using the local Storage Systems feature in RMC.
Primary or local and secondary or remote RMC-O servers must be correctly configured.
Remote copy links among nodes within the servers must be set up and remote copy targets related to the
servers must be created. RMC-O supports only the
mirror_config
•
72
policy (default) for the involved remote copy targets.
For synchronous long-distance remote copy setups:
Create remote snapshot
◦
•
•
•
•
•
•
•
•
•
The Oracle datafile and archive log virtual volumes can be on the same or separate remote copy
groups.
◦ Each remote copy group must have two targets. The same set of database volumes must belong to two
Remote Copy groups (with the same name). One group is for the asynchronous periodic target, and the
other group is for the synchronous target.
◦ The Oracle online redo log volumes must be included in one of the database remote copy groups,
excluding the Oracle datafile and archive log remote copy groups. This process allows for a successful
failover if needed. If the Oracle online redo log volumes are included in either the Oracle datafile
Remote Copy group or the archive log remote copy group, RMC-O fails.
RMC-O must be preconfigured for the database on the local backup server. The local RMC-O server can
be used to manage all database snapshots that are created on the local or primary 3PAR StoreServ
Storage system.
The database instance must be offline or online when creating an offline snapshot or when creating online
or datafile snapshot respectively. The database instance is considered to be offline if it is in closed mode. If
the database is an RAC database, all RAC instances must be offline. The database instance is considered
to be online if it is in Open mode (for primary database) or in managed recovery mode (for physical
standby databases). If the database is a RAC database, the specified database instance must be online,
all other RAC instances can be either online or offline.
If the database being snapshot is a physical standby database and Oracle release is not 11g, the Oracle
parameter file and control file of the production database must be backedup manually and the snapshot.
This is because the parameter file and control file are not compatible between the standby and production
database.
Each database instance must be started up using either a parameter file (pfile) or server parameter file
(spfile) from the default location ($ORACLE_HOME/dbs).
The database must be running in archive log mode and automatic archival must be enabled to create an
online snapshot.
If archive log mode is enabled, the datafiles and archive logs must reside on separate 3PAR virtual
volumes.
The online redo logs and control files must not reside on the same 3PAR virtual volumes used by the
datafiles and archive logs to avoid being restored when using the Snapshot Restore feature. However, the
online redologs and control files can share 3PAR virtual volumes.
If you use LVM Volume Manager, the Oracle datafiles and archive logs must reside on separate LVM
volume groups. In addition, online redo logs and control files must not reside on LVM volume groups that
are used by Oracle datafiles and archive logs. However, the online redo logs and control files can reside
on the same LVM volume group.
Datafile and archive log volumes can be in the same remote copy group or separate remote copy groups
for periodic or synchronous mode.
Datafile and archive log volume must be in different remote copy group for asynchronous streaming mode.
•
In SLD configuration, if datafile and archive log volumes are in the same remote copy group, when a
failover occurs, a full synchronization of the remote copy group between the periodic secondary system
and the new primary system is required. Redo log volumes are not required to be in a remote copy group
for periodic mode. Redo log volumes must not belong to the datafile or archive log remote copy groups for
synchronous mode, asynchronous streaming mode, or SLD configuration.
The remote copy group resynchronization frequency must be disabled to avoid interfering with RMC-O
operations.
Creating a remote snapshot
Procedure
1.
2.
3.
4.
On the master pane of the Oracle Databases screen, select a database.
Select Create snapshot from the Actions menu.
Select Remote in Create snapshot.
Enter the snapshot name and description.
Snapshots with remote copy
73
5.
Select the backup method for the database, for example Online (Hot) backup, Archive log only,
Offline (Cold) backup, or Datafile only.
6. Enter the snapshot expiration time or retention time.
7. Perform the following steps:
8. To set the frequency of the snapshot, select Schedule and perform the following steps:
9. Click OK.
10. To view the snapshot creation progress, navigate to the Activity pane.
NOTE:
•
•
74
Once the remote snapshot operation is complete, you can use the secondary RMC appliance to
protect these snapshots by using appropriate protection policies on the remote site.
The naming format of the snapshots created during remote snapshot is Remote_Copy_<snapname> on the remote appliance.
Snapshots with remote copy
Protect
I want to ...
•
•
•
•
•
Create protect on page 78
Edit protect on page 79
Remove protect on page 79
Restore protect on page 79
Abort protect on page 81
Learn More...
•
•
About protect on page 75
Protect screen details on page 77
About protect
Protect enables you to schedule snapshots and backups. It also provides the capability to take quick and
immediate backup and restore from historical snapshots and backups.
RMC-O integrates RMC snapshot feature with HPE StoreOnce, Symantec NetBackup with RMAN (RMAN
NBU), Symantec NetBackup (NBU), HPE Data Protector, and Oracle RMAN to perform snapshot off-host
backup. Snapshot off-host backup can dramatically reduce performance impact on the database server as
well as minimize database down time or the time database in backup mode during backup.
For an HPE StoreOnce backup, selecting Protect from Actions creates a database snapshot and performs a
volume level backup of datafiles and archivelogs to HPE StoreOnce target. The database meta data
CONTROLFILE, password file, PFILE, and so on) is also backed up. The Express Protect backups are
faster and de-duplicated compared to traditional backups. See Recovery Manager Central User Guide for
details on Express Protect feature.
For a media backup, selecting Protect from Actions creates a database snapshot, mounts (presents) it to the
backup server before initiating an immediate backup (off-host).
If you intend to perform a media backup of an existing snapshot, the snapshot must have Available status
(not mounted or cloned to a database) to be backed up. The backup process mounts the snapshot to the
backup server before initiating a client-side media backup (off-host). However, this limitation does not apply
for HPE StoreOnce backup types.
RMC-O supports Symantec NetBackup, HPE Data Protector (RMAN DP), and Oracle RMAN backup
methods. The backup method can be specified during Recovery Manager configuration process. Symantec
NetBackup backup method can be used to perform backup of a database whose database files are on file
systems. Oracle RMAN backup method can be used to perform backup of a database whose database files
are either on file systems or ASM disk group. For Oracle RMAN backup method, a database can be backed
up to a local disk (Symantec NetBackup or HPE Data Protector is not required) or to a tape using Symantec
NetBackup or HPE Data Protector.
If Oracle RMAN (with or without Symantec NetBackup or HPE Data Protector) is selected, the primary (not
standby) database must be registered with an Oracle Recovery Catalog. Starting with Oracle 11g, an RMAN
backup image of a standby database to local disk cannot be seen from the Recovery Catalog from the
production database. Therefore, the backup image cannot be restored to the production database using the
RMC-O interface.
For Symantec NetBackup, a database backup must be a full backup. An incremental database backup is not
possible. An archive log backup can be used to simulate an incremental backup. An archive log backup can
be a full, a differential incremental (incr), or a cumulative incremental backup.
For Oracle RMAN or Oracle RMAN with Symantec NetBackup, a database backup can be a full, a differential
incremental (incr), or a cumulative incremental (cinc) backup. Archive log backup must be a full backup.
Incremental backup of archive log is not supported.
For Oracle RMAN with HPE Data Protector, a database backup can be a full, or an incremental level 1 (incr1)
to level 4 (incr4) backup. By default, an incremental backup is differential. To perform cumulative incremental
Protect
75
backup, user must modify the RMAN script in the backup specification of HPE Data Protector. Archive log
backup must be a full backup. Incremental backup of archive log is not supported.
Backup operations are supported on Remote Copy configuration. To back up the snapshot created on the
remote site, configure the Protection Policies appropriately on the remote appliance.
The following list describes the restrictions and automated scripts that are generated when configuring
Recovery Manager. The automated scripts will be executed during the backup process.
For NBU (user-managed) backup:
•
•
The Symantec NetBackup client must be installed on the backup server and database server.
At least one NBU policy of standard type must be created and configured for database backup. Optionally,
a separate NBU policy of standard type can be created and configured for archive log backup.
For Oracle RMAN, Oracle RMAN with Symantec NetBackup and Oracle RMAN with Data Protector back up:
•
•
•
•
The backup server and the recovery catalog database server must have same or higher Oracle major
release version than the Oracle major release version on the database server.
An Oracle RMAN Recovery Catalog database is required. Refer to RMC-O User Guide for detail on how to
create and configure RMAN Recovery Catalog database.
For Oracle RMAN with Symantec NetBackup backup, the Symantec NetBackup Client with Oracle
Integration Agent must be installed on the backup server and database servers. The Symantec NetBackup
master server can be installed on any servers. A Symantec NetBackup Policy of Oracle type must be
precreated for database backup (online, offline, or datafile). Optionally, a separate Symantec NetBackup
policy of Oracle type can be created and configured for archive log backup (archlog). See Configuring
Symantec NetBackup Policy section to create Symantec NetBackup Policy.
For Oracle RMAN with HPE Data Protector backup, the HPE Data Protector Client with Oracle Integration
Agent and user interface components must be installed on the backup server and database servers. The
HPE Data Protector Cell Manager can be installed on any servers. The HPE Data Protector User Interface
Component must be installed on a Windows server to access the HPE Data Protector Cell Manager. An
HPE Data Protector Oracle backup specification must be created before database backup (online, offline,
or datafile). Optionally, a separate HPE Data Protector Oracle backup specification can be created and
configured for archive log backup (archlog). See Configuring HPE Data Protector Backup section for more
details.
Depending on which backup method is configured for media backups, the backup process performs the
following actions:
•
•
•
Creates a snapshot (online, offline, datafile, or archlog) for the database or archive log destination if a
snapshot is not specified.
Mounts the snapshot on the backup server.
For NetBackup (user-managed) backups:
◦
•
Generates an include list file, which contains a list of datafiles or the archive log destination or both on
the mounted snapshot and stores it in /usr/openv/netbackup/include_list.<policy_name>
on the NetBackup client (the backup server).
◦ Initiates an immediate backup of the snapshot by calling the NetBackup bpbackup command on the
NetBackup master server.
For Oracle RMAN or Oracle RMAN with Symantec NetBackup back up:
◦
◦
76
Protect
Starts up a clone database in MOUNTED mode using the mounted snapshot on the backup server.
Executes the RMAN backup scripts rmco_rman_dbbackup.sh or rmco_rman_archbackup.sh or
to back up the clone database.
NOTE:
The RMAN backup scripts (rmco_rman_dbbackup.sh and rmco_rman_archbackup.sh) are
generated at /opt/hpe/rmc/oracle/data/<db_server>.ora.<oracle_sid> on the backup server when
associating a database with a Protection Policy.
•
For Oracle RMAN with HPE Data Protector back up:
◦
◦
Starts up a clone database in MOUNTED mode using the mounted snapshot on the backup server.
Executes HPE Data Protector backup CLI (omnib) on the backup server to initiate the backup.
Protect screen details
Database
Displays the database selected for the backup.
Backup vendor
Supported backup storage system vendor.
Name
Name of the express protect.
Description
Description of the express protect.
Protection policy name
Protection policy applied to the express protect.
Backup type
Displays the backup type, for example, Full, Incremental, Cumulative incremental. If the backup vendor
is HPE StoreOnce, the Backup type could be either Full Backup or Auto.
Snapshot Configuration
Snapshot name
Name of the snapshot.
Expiration time
Time when the snapshot expires.
Retention time
Minimum time after which a snapshot can be removed either manually or automatically.
Retain snapshot
Retains the snapshot after a backup is taken.
Backup Method
Online (hot) backup
Schedules an online backup. The involved database instance must be open for this operation.
Archive logs only
Creates a point-in-time image of database's archive log destination while the database is open.
Offline (hot) backup
Schedules an offline backup. The involved database instance must be shut down normally for this
operation.
Protect screen details
77
Datafile only
Takes a point-in-time snapshot image of the datafiles of a database while it is open.
Schedule
Schedule
Select to schedule a backup task.
Scheduler name
Name of the schedule.
Scheduler description
Description for the schedule.
Frequency
Select the schedule frequency, for example, Weekly, Daily, Hourly, Monthly, Yearly, or One off.
Start time
Time for the scheduled snapshot to start.
Create protect
Procedure
1.
2.
3.
4.
5.
6.
7.
8.
On the master pane of the Oracle Databases screen, select a database.
Select Protect from the Actions menu
Select the backup vendor. For example, HPE StoreOnce, Oracle Recovery Manager, RMAN NBU,
RMAN DP, or NBU.
Enter the name and description of the backup set.
Select the policy that you want to associate with the express protect.
Perform one of the following steps:
a. If the backup vendor is HPE StoreOnce, select Auto or Full backup as the backup type. Auto type
is preferred as it automatically detects whether to perform a full or incremental backup.
b. If the backup vendor is anything other than HPE StoreOnce, select Full, Incr, or Cinc as the backup
type.
c. For RMAN, RMAN DP, and RMAN NBU, the default value of Use Large Pages specified in the
Protection Policy is applicable. However, you can modify the value for the current protect.
Enter the snapshot name, expiration time, and retention time.
To retain the snapshot after the backup is taken, select Retain snapshot.
NOTE: To retain the newly created snapshot after protect, ensure that the Retain snapshot check
box is not selected.
9.
Select the backup method, for example, Online (Hot) Backup, Archive logs only, Offline (Cold)
Backup, or Datafile only.
10. To schedule the snapshots and backups, select Schedule and enter the required schedule details.
NOTE:
The minimum permissible interval between two subsequent backups is 1 hour.
11. Click OK.
78
Create protect
Edit protect
Procedure
1.
2.
3.
4.
5.
On the master pane of the Oracle Databases screen, select a database.
Select Protection View from the View selector menu.
Select the express protect backup that you want to edit and click Action > Edit.
Edit the Name or Description, or both.
Click OK.
Remove protect
Procedure
1.
2.
3.
4.
On the master pane of the Oracle Databases screen, select a database.
Select Protection View from the View selector menu.
Select the backup that you want to remove and click Action > Remove.
Click Remove.
NOTE:
For media backups, this procedure clears the selected backup from the RMC-O catalog. However, the
entries in the backup software catalog continue to exist. See Media Backups chapter for details on
clearing the backup software catalog and erasing the physical media corresponding to this backup.
Restore protect
Restoring protect to parent volume
Procedure
1.
2.
3.
From the database server, shut down the database. If the database is a Real Application Clusters (RAC)
database, all RAC instances must be shut down.
From the database server, unmount all database file systems if they are on file systems.
Example:
# umount /oradata
4.
5.
From the database server, drop the database ASM disk groups if ASM is in use.
Example:
SQL>drop diskgroup <disk_group> including contents;
6.
7.
From the database server, deport/export the database volume groups if volume groups are in use.
Depends on volume groups involved, the deport/export volume group commands are slightly different,
the following are some of examples:
Edit protect
79
For Linux logical volume groups, use the following command to deactivate
logical volumes and export volume groups:
# lvchange -an /dev/ <vgname>/<lvname>
# vgexport <vgname>
Example:
# lvchange -an /dev/rh6lvm-data/lvol0
# lvchange -an /dev/rh6lvm-data/lvol1
# vgexport rh6lvm-datavg
8.
9.
10.
11.
On the master pane of the Oracle Databases screen, select a database.
Select Protection View from the View selector menu.
Select the express protect backup that you want to restore and click Action > Restore.
In General, perform the following steps:
a. Select Restore express protect to parent volume or any alternate volumes as the restore
operation.
b. Select the application server on which you want to restore the express protect backup.
c. Enter the meta data file path and select the restore type.
12. Click Restore.
13. From the database server, activate logical volumes and import/start volume groups.
14. Example:
For Linux
vgscan
vgimport
lvchange
lvchange
#
#
#
#
logical volumes:
rh6lvm-datavg
-ay /dev/rh6lvm-datavg/lvol0
-ay /dev/rh6lvm-datavg/lvol1
15. From the database server, perform file system check, and then mount the database file systems if
database files are on file systems.
16. Example:
fsck -y /dev/maper/mpathc
# mount /dev/mapper/mpathc /oradata
17. From the database server, mount database ASM disk groups if ASM is in use.
18. Example:
SQL>alter diskgroup <disk_group> mount
19. From the database server, follow Oracle documentation to perform media recovery to recover the
database.
NOTE:
If both datafile and archive log volumes are rolled back, then an incomplete recovery must be
performed to recover the database on the database server. The binary or ASCII control file from the
restored meta data file can be used if necessary.
Restoring protect to another volume
80
Protect
•
•
•
•
•
•
•
On the master pane of the Oracle Databases screen, select a database.
Select Protection View from the View selector menu.
Select the express protect backup that you want to restore and click Action > Restore.
In General, perform the following steps:
Select the storage system on which you want to restore the backup.
Select the data volume and archive volume.
Click Restore.
Abort protect
Procedure
1.
2.
3.
4.
5.
From the master pane of the Oracle Databases screen, select a database.
From the details pane, select a backup which is either in running or restoring state.
Click Action from the backup list.
Select Abort from the Action menu.
Click Abort.
NOTE:
•
•
•
To abort an express protect, the Backup Vendor must be HPE STOREONCE.
The backup state must either be in running or restoring state.
The database goes to an error state after aborting restore operation. Retry Restore operation or
Unregister Database.
Abort protect
81
Catalyst Copy
Catalyst Copy
Creates a copy of an Express Protect or snapshot or database on another HPE StoreOnce Catalyst Store or
on a different Catalyst Store of the same HPE StoreOnce.
Catalyst Copy topology
Displays a graphical representation of Catalyst Copy and the associated resources. To view the topology,
click
in the Catalyst Copy page.
Figure 10: Catalyst copy topology
Creating a Catalyst Copy
Procedure
1. Click the HPE Recovery Manager Central main menu and click Databases.
Databases overview screen appears.
2. Click Actions > Catalyst Copy.
One click Catalyst copy creation dialog appears.
3. Perform the following in the Create Copy dialog:
a. Enter the Name and Description of the Catalyst Copy.
b. Enter the Name and Description of the Express Protect.
c. Click Select to search and select a Protection Policy name.
d. Select the Backup Type as either Auto or Full Backup.
e. Enter the Snapshot Name, Expiration Time, and Retention Time in hours or days.
f. Click Retain Snapshot to retain the snapshot after a backup is taken.
g. Select a Backup Method from Online (Hot) Backup, Archive logs only, Offline (Cold) Backup,
Datafile only.
h. Specify the Scheduler Name and Scheduler Description.
i. Set the Frequency, Start time, and Recurrence in hours for the scheduler.
4. Click Ok to create the Catalyst Copy.
82
Catalyst Copy
Creating a Catalyst Copy from an existing snapshot
Procedure
1. Click the HPE Recovery Manager Central main menu and click Databases.
Databases overview screen appears.
2. Select Protection View from the view selector in the overview screen.
Snapshots and Protects option appear in the Protection View screen.
3. Click Snapshots and select a snapshot from the list.
4. Click Action and select Catalyst Copy.
5. Perform the following in the Create Copy dialog:
a. Enter Name and Description for the catalyst copy.
b. Enter the Name and Description of the Express Protect.
c. Click Select to search and select a protection policy.
d. Select Backup Type as Auto or Full Backup.
6. Click Ok.
Creating a Catalyst Copy from an existing protect
Procedure
1. Click the HPE Recovery Manager Central main menu and click Databases.
2.
3.
4.
5.
6.
Databases overview screen appears.
Select Protection View from the view selector in the overview screen.
Snapshots and Protects option appear in the Protection View screen.
Click Protects and select a protect from the list.
Click Action and select Catalyst Copy.
Enter a Description (optional) in the Create Copy dialog.
Click Ok to create a catalyst copy from an existing protect.
Editing a Catalyst Copy
Prerequisites
Ensure you have a Catalyst Copy associated with the selected Protect.
Procedure
1. Click the HPE Recovery Central main menu and click Databases.
The databases overview screen appears.
2. Click Protection View > Protects.
List of Protects appears with the corresponding details appears.
3. Select a Protect from the list where the value of Catalyst Copy is Yes.
4. Click Action > Edit.
5. Perform the following in the Edit dialog:
a. Edit the Name of the Catalyst Copy.
b. Edit the Description of the Catalyst Copy.
c. Enter the Expiration Time (Hours) and Retention Time (Hours).
6. Click Ok.
Creating a Catalyst Copy from an existing snapshot
83
Removing a Catalyst Copy
Prerequisites
Ensure you have a Catalyst Copy associated with the selected Protect.
Procedure
1. Click the HPE Recovery Central main menu and click Databases.
The databases overview screen appears.
2. Click Protection View > Protects.
List of Protects appears with the corresponding details appears.
3. Select a Protect from the list where the value of Catalyst Copy is Yes.
4. Click Action > Remove.
5. Click Remove in the Remove dialog.
The associated Catalyst Copy is removed.
Restoring a Catalyst Copy
Prerequisites
Ensure you have a Catalyst Copy associated with the selected Protect.
Procedure
1. Click the HPE Recovery Central main menu and click Databases.
The databases overview screen appears.
2. Click Protection View > Protects.
List of Protects appears with the corresponding details appears.
3. Select a Protect from the list where the value of Catalyst Copy is Yes.
4. Click Action > Restore.
5. Perform the following in the Restore dialog:
a. Select either Restore Express Protect to parent volume or Restore Express Protect to another
volume from the Restore Operation option.
b. Click Select to search and select a host name for the Application Server.
c. Specify or edit Meta Data File Path.
d. Specify the Restore Type from Both, Archive logs, or Data.
6. Click Restore.
Aborting a Catalyst Copy
Prerequisites
Ensure that the Protect is in a running state.
Procedure
1. Click the HPE Recovery Central main menu and click Databases.
The databases overview screen appears.
2. Click Protection View > Protects.
List of Protects appears with the corresponding details appears.
3. Select a Protect from the list where the value of Catalyst Copy is Yes and the task is in running status.
4. Click Action > Abort.
5. Click Abort.
84
Removing a Catalyst Copy
NetBackup policy configuration
This chapter describes the NetBackup policies and the procedure to configure the policies to perform
Symantec NetBackup (user-managed) and Oracle Recovery Manager (RMAN) with Symantec NetBackup.
RMC-O integrates HPE 3PAR Virtual Copy Software with Symantec NetBackup (NBU) to reduce the
performance impact on the database server and to minimize database down time during backup. For NBU
backup and restore, RMC-O interacts directly with NBU to trigger the backup or restore process.
About NetBackup policies for NBU (user-managed) backup
RMC-O supports Symantec NetBackup with or without RMAN. It also supports full, incremental, or cumulative
incremental archive log backup. When performing NBU backup without RMAN, RMC-O supports only full
database backup (incremental database backup is not supported). However, you can combine full database
backup with archive log backup to create an incremental database backup. For more information on creating
a NetBackup policy, see the Symantec NetBackup documentation.
Configure a Netbackup policy for database and archive log backup
Prerequisites
Procedure
1. HPE recommends that you use the backup server as the NetBackup master server.
2. The Symantec NetBackup client must be installed on the backup server and the database server.
3. At least one standard Symantec NetBackup policy must be created and configured for database backup.
Optionally, you can create and configure a separate standard NBU policy for archive log destination
backup.
4. The Backup and RMC-O application server must have the same OS version as RMC-O and Oracle
database.
Configuring a Netbackup policy for database and archive log backup
Procedure
1. On the Attributes tab, perform the following steps:
• Set the Policy Type as Standard.
• Select the Cross mount points check box.
• Clear the Allow multiple data stream and Block level incremental check boxes.
2. On the Schedules tab, perform the following steps:
a. For Database backup
•
•
Select the Type of backup as Full Backup.
Perform one of the following:
◦
◦
Set the backup start window to 0 to perform client-side database backup (initiated from RMC).
Set the backup window to meet your requirement to perform automatic archive log backup
(initiated from NBU).
b. For Archive log backup
NetBackup policy configuration
85
•
Create two schedules, one for full backup and one for incremental backup (optional). For the
incremental backup schedule, you must either create a differential incremental or a cumulative
incremental backup schedule.
NOTE:
◦
◦
•
Incremental backup of archive log using RMAN is not supported.
Backup server and NBU master server can be the same.
Perform one of the following steps:
◦
◦
Set the backup start window to 0 to perform client-side database backup (initiated from RMC).
Set the backup window to meet your requirement to perform server-side database backup
(initiated from NBU).
3. On the Clients tab, set the backup client to the host name of the backup server so that the backup
process takes place on the backup server.
4. On the Backup Selections tab, type /dummy for the backup selections.
5. RMC generates the backup selection list to replace the value you entered.
About NetBackup policies for Oracle RMAN backup
RMC-O supports full, differential, cumulative incremental, and full archive log (backup only archive logs)
database backup when performing an NBU backup with RMAN. For more information on creating a policy,
see the Symantec NetBackup for Oracle documentation.
NOTE:
Run the script /usr/openv/netbackup/bin/oracle_link for Oracle to connect to the Oracle
library on the database and backup servers to point to the Symantec NetBackup Media Library.
Configure a NetBackup policy with RMAN
Prerequisites
Procedure
1. An RMAN Recovery Catalog database must be created and configured before database backup.
2. Symantec NetBackup client for Oracle must be installed on the backup server and the database server.
3. At least one standard NBU policy must be created and configured for database backup. Optionally, you
can create and configure a separate standard NBU policy for archive log destination backup.
4. Symantec NetBackup for Oracle (NBU Agent for Oracle) must be installed on the NBU master server.
5. An Oracle RMAN Recovery Catalog must be created and Oracle TNS service and Listener must be
configured to allow connections to the Recovery Catalog from the database server and backup servers.
NOTE:
You can create the Recovery Catalog on any server. However, HPE recommends that you create the
Recovery Catalog on the backup server.
Configuring a NetBackup policy for database and archive log backup with RMAN
Procedure
1. On the Attributes tab, select the Policy Type as Oracle.
2. On the Schedules tab, perform the following steps:
86
About NetBackup policies for Oracle RMAN backup
•
For Database backup
◦
◦
•
Create two schedules, one for full backup and one for incremental backup (optional). For the
incremental backup schedule, you must create either a differential incremental or cumulative
incremental backup schedule.
Perform one of the following steps:
– Set the backup start window to 0 to perform client-side database backup (initiated from RMC).
– Set the backup window to meet your requirement to perform automatic database backup
(initiated from NBU),
For Archive log backup
◦
◦
Create a schedule for full backup.
Perform one of the following steps:
– Set the backup start window to 0 to perform client-side archive log backup (initiated from RMC).
– Set the backup window to meet your requirement to perform automatic archive log backup
(initiated from NBU).
3. On the Clients tab, set the backup client to the host name of the backup server so that the backup
process takes place on the backup server.
4. On the Backup Selections tab, type /opt/hpe/rmc/oracle/data/
<db_server>.ora.<oracle_sid>/rmco_nbu_archbackup.sh.
About database backup
RMC-O performs the backup in the following ways:
•
•
Client-side backup — A backup that is initiated from the RMC-O user interface.
Server-side backup — A backup that is initiated from the Symantec NetBackup user interface using the
Symantec NetBackup master server.
Client-side backup
RMC-O performs the following tasks during client-side backup:
•
For NBU (user-managed) backup
◦
◦
◦
•
Creates an online, offline, datafile, or archive logs snapshot for the database or archive log destination.
Mounts the snapshot on the backup server.
Generates an include list file that contains a list of datafiles and archive logs destination on the
mounted snapshot. The file is stored at /usr/openv/netbackup/include_list.
<policy_name> on the NBU client (the backup server).
◦ Calls the bpbackup command from the NBU master server to back up files listed in the include list.
For Oracle RMAN and Oracle RMAN with Symantec NetBackup:
◦
◦
◦
◦
◦
◦
Creates an online, offline, datafile, or archive logs only snapshot for the database or archive log
destination.
Mounts the snapshot on the backup server.
Starts up a clone database in mounted mode using the mounted snapshot on the RMC-O backup
server.
Calls an RMAN backup script (rmco_rman_dbbackup.sh or rmco_rman_archbackup.sh) to back
up the cloned database.
Removes the cloned database.
Unmounts the snapshot.
About database backup
87
Server-side backup
During server-side backup, Symantec NetBackup initiates a backup process on the Symantec NetBackup
client. The NBU server-side backup can be used when RMC-O is configured to run as a root user. RMC-O
performs the following tasks during server-side backup:
•
For NBU (user-managed) backup
◦
◦
◦
•
The NBU client executes the bpstart_notify.<policy_name> script.
The bpstart_notify script creates a snapshot of the database or archive log destination, mounts it
on the backup server, and then generates the include list in the /usr/openv/netbackup/
include_list.<policy_name> file, which contains a list of files on the snapshot for backup.
Once the backup process is completed, the NBU client executes the
bpend_notify.<policy_name> script to perform snapshot cleanup.
For Oracle RMAN with Symantec NetBackup
◦
The NBU client executes the backup script rmco_dbbackup.sh
or
◦
rmco_archbackup.sh, which must be specified in the Backup Selection List of the NBU policy.
The backup script creates a snapshot of the database or archive log destination, mounts it on the
backup server, starts up a cloned database in Mounted mode, then calls the RMAN backup scripts
(rmco_rman_dbbackup.sh)
or
rmco_rman_archbackup.sh to back up the cloned database.
NOTE:
•
•
88
By default, the rmco_dbbackup.sh script (for database backup policy) performs an online backup.
If an offline or datafile backup is desired, edit this file to set the value of BACKUP_MODE, to offline,
or datafile. For offline snapshots, you must manually shut down the database.
If ORACLE_HOME is different on production and backup servers, create symbolic links on backup
server to match the value of the production server.
Server-side backup
RMAN Recovery Catalog configuration
About RMAN Recovery Catalog configuration
This chapter explains how to create and configure a Recovery Catalog. If you want to back up a snapshot
using Oracle RMAN, a Recovery Catalog must be created and configured before backing up the database.
For detailed information on creating a Recovery Catalog and configuring Oracle TNS Service and Listener,
see the Oracle documentation.
Create RMAN Recovery Catalog
Prerequisites
Procedure
1. The following are the disk space requirements for creating a Recovery Catalog:
a. System tablespace must be 100 MB
b. Temp tablespace must be 5 MB
c. Rollback segment must be 5 MB
d. Online redo log must be 1 MB each
e. Recovery Catalog must be 10 MB
Creating an RMAN Recovery Catalog
Procedure
1. Create a database for the Recovery Catalog.
2. Create a tablespace for the Recovery Catalog as follows:
$ export ORACLE_SID=<catdb>
$ export ORACLE_HOME=<oracle_home>
$ sqlplus "/as sysdba"
SQL> create tablespace <cat_tbs> datafile '<path/filename>' size 10M;
SQL> exit
Where,
• <catdb> is the Oracle Instance ID of the Recovery Catalog.
• <cat_tbs> is the Recovery Catalog tablespace name.
• <path/filename> is the file path where the datafile is created.
3. Create a user for the Recovery Catalog as follows:
$ sqlplus "/as sysdba"
SQL> create user <rman_user> identified by <rman_password>
temporary tablespace temp
default tablespace <cat_tbs>
quota unlimited on <cat_tbs>;
SQL> grant connect, resource, recovery_catalog_owner to <rman_user>;
Where,
RMAN Recovery Catalog configuration
89
• <tbs_name> is the tablespace name of the Recovery Catalog.
• <rman_user> is the user name to be granted access permission to the Recovery Catalog.
• <rman_password> is the password for the <rman_user>.
4. Create the RMAN Recovery Catalog tables as follows:
$ rman catalog <rman_user>/<rman_password>@<catdb>
RMAN> create catalog tablespace <cat_tbs>;
5. Configure TNS services for the Recovery Catalog database by adding an entry in the $ORACLE_HOME/
network/admin/tnsnames.ora file on the database server and backup server as follows:
<catdb> =
(description =
(address = (protocol = TCP) (host = <cat_host>) (port = 1521))
(connect_data = (server = dedicated) (service_name = <catdb>))
)
Where,
<cat_host> is the host name of the host where the catalog is created.
6. Configure 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 = <catdb>)
(ORACLE_HOME = <oracle_home>)
(SID_NAME = <catdb>)
)
)
7. Log in as the Oracle owner user and register the database on the database server.
NOTE:
If RMC-O is used to run against an Oracle standby database, you must register the primary database
on the primary database server instead of the standby database.
$ rman target / catalog <rman_user>/<rman_password>@<catdb>
RMAN> register database;
Configure RMAN Recovery Catalog
Prerequisites
Procedure
1. RMC-O requires an Oracle RMAN recovery catalog database when using RMAN backup. To create RMAN
Recovery Catalog, see Create RMAN Recovery Catalog on page 89.
Configuring an RMAN Recovery Catalog
When using RMAN backup with Data Protector, if the Oracle release of the recovery catalog database is 11g
R2 or later:
90
Configure RMAN Recovery Catalog
Procedure
1. Grant CREATE ANY DIRECTORY and DROP ANY DIRECTORY system privileges to the owner of the
Recovery Catalog.
SQL> grant CREATE ANY DIRECTORY to <recovery_catalog_user> ;
SQL> grant DROP ANY DIRECTORY to <recovery_catalog_user>
2. Grant SELECT permissions on v_$instance view to the owner of the Recovery Catalog.
SQL> grant select on v_$instance to <recovery_catalog_user> ;
RMAN Recovery Catalog configuration
91
HPE Data Protector configuration
About Data Protector configuration
RMC-O interacts directly with Data Protector to trigger the backup or restore process. RMC-O supports full
and incremental level 1 to level 4 backup when performing Oracle RMAN with Data Protector backup of a
database. You can also perform a full archive log backup (backup only archive logs) of the database.
However, to perform archive log and database backup, you must create a Data Protector Oracle backup
specification. For information on how to create Data Protector Oracle backup specification, see the Data
Protector documentation.
NOTE:
•
•
•
•
With Data Protector, RMC-O supports only Oracle RMAN backup. File system backup using Data
Protector is not supported. For detailed information on the installation and configuration of Data
Protector, see the HPE Data Protector documentation.
The integration options for RMC-O are not available on the Data Protector Java graphical user
interface on the UNIX Cell Manager.
The database must be in the Mounted or Started mode before the restore process.
If a backup of archive logs is not performed, datafile backup is not useful. Perform backup of archive
logs separately.
Prerequisites for database backup
•
•
•
•
•
•
•
•
An RMAN Recovery Catalog database must be created and configured before backing up the database.
Oracle RMAN Recovery Catalog and Oracle TNS Service and Listener must be configured to allow
connections to the Recovery Catalog from the database server and backup servers.
HPE Data Protector client with Oracle Integration Agent and User Interface components must be installed
on the RMC-O database server and backup servers.
HPE Data Protector Cell Manager with Oracle Integration Agent and User Interface components installed
on any supported Data Protector server. HPE recommends that you install Data Protector Cell Manager on
the backup server.
The TNS service name must be preconfigured for the database instance on the database server.
The same TNS net service name must be preconfigured for the cloned database instance on the backup
server.
Oracle Home must be the same between the RMC-O database server and backup server.
At least one Data Protector Oracle backup specification must be created and configured for database
backup. Optionally, you can create and configure a separate Data Protector Oracle backup specification
for archive log backup.
About database backup
RMC-O performs the backup in the following ways:
•
•
Client-side backup — A backup that is initiated from the RMC-O user interface.
Server-side backup — A backup that is initiated from the HPE Data Protector user interface using the Data
Protector Cell Manager.
Client-side backup
For Oracle RMAN with Data Protector, RMC-O performs the following tasks during client-side backup:
92
HPE Data Protector configuration
•
•
•
•
Creates an online, offline, datafile, or archonly snapshot for the database or archive log destination.
Mounts the snapshot on the backup server.
Starts up a clone database in mounted mode using the mounted snapshot on the RMC-O backup server.
Calls Data Protector CLI (
omnib
•
•
) to initiate a backup of the clone database.
Removes the cloned database.
Unmounts the snapshot.
Server-side backup
For Oracle RMAN with Data Protector, RMC-O performs the following tasks during server-side backup:
•
Data Protector Cell Manager executes the
DP_pre.<backup_specification>
•
on the RMC-O backup server.
The
DP_pre.<backup_specification>
•
•
script creates an online, offline, datafile, or archlog snapshot, mounts it on the RMC-O backup server,
starts up a cloned database in MOUNTED mode, and then returns control to Data Protector.
Data Protector executes RMAN script (defined in the Data Protector backup specification) to back up the
cloned database.
Data Protector executes
DP_pre.<backup_specification>
on the RMC-O backup serve to clean up the cloned database and snapshot.
NOTE:
By default, DP_pre.<backup_specification> creates an online snapshot. To create an offline or
datafile snapshot, use RMC-O to schedule one.
Setting up Data Protector
Process overview:
Procedure
1.
2.
3.
4.
5.
Enable RMC-O for Data Protector on page 93
Configure Oracle Operating System User Account (Oracle Owner Account) on page 94
Create Data Protector Oracle backup specification on page 94
Modify Data Protector RMAN script on page 95
Configure TNS naming service on the RMC-O backup server on page 96
Enable RMC-O for Data Protector
Procedure
1. In Data Protector Cell Manager, add the following parameter to the /etc/opt/omni/server/options/
global file:
Server-side backup
93
Enable3ParBackupToTapeForOracle=1
2. Restart Data Protector service for the change to take effect. Use the following commands to restart the
service:
•
•
# /opt/omni/sbin/omnisv stop
# /opt/omni/sbin/omnisv start
Configure Oracle Operating System User Account (Oracle Owner Account)
The Oracle operating system user is the owner of the Oracle Home.
Procedure
1. Add the Oracle operating system user account to the Data Protector admin group.
2. Specify the following parameters when adding a user to the Data Protector admin group:
•
•
•
•
•
Group — admin
Type —UNIX
Name — User name of the Oracle owner on the database server, for example Oracle
Group/Domain — <Any>
Client — <Any>
Create Data Protector Oracle backup specification
Prerequisites
Data Protector user interface must be used from Windows machine to connect to the Cell Manager when
creating a backup specification.
Creating Data Protector Oracle backup specification
Procedure
1. Select the 3PAR_RMO_Online, 3PAR_RMO_Offline, or 3PAR_RMO_Data template for database backup
or 3PAR_RMO_Archive template for archive log backup.
2. Select the control file object.
3. In Application, perform the following steps:
• Client — Select the host name of the database server to be configured for backup.
• Application database — Select the database to be configured for backup.
4. In User and group/domain, perform the following steps:
a. User name — Specify the user name of the Oracle owner. This user must be added to Data Protector
admin group. For information on adding users, see Configure Oracle Operating System User
Account (Oracle Owner Account) .
b. Group/Domain name — Specify the corresponding group name of the Oracle owner.
5. In General Information, specify the Oracle Home of the database.
6. In Primary Database, perform the following steps:
a. User name — Specify an Oracle user that has SYSDBA privilege.
b. Password — Specify the password of the Oracle user.
c. Services — Specify the TNS service name of the Oracle database. For an RAC database, specify all
TNS service names of the database instances separated by comma.
IMPORTANT:
The TNS service names must be preconfigured for the database instances on the RMC-O
application server. The same TNS service names must be preconfigured for the clone database
on the backup server.
94
Configure Oracle Operating System User Account (Oracle Owner Account)
7. In Recovery Catalog, perform the following steps:
a. User name — Specify the RMAN catalog user name.
b. Password — Specify the password for the RMAN catalog user.
c. Services — Specify the service name of the catalog database. The TNS service name must be
configured on the RMC-O application server and the backup server.
8. In Backup Specification Option, perform the following steps:
a. Pre-exec
•
•
Pre-exec — Specify DP_pre.<backup_specification_name>.
On client — Specify the host name of the RMC-O backup server where the pre-exec script will be
executed.
b. Post-exec
•
•
Post-exec — Specify DP_post.<backup_specification_name>..
On client — Specify the host name of the RMC-O backup server where the post-exec script will be
executed.
c. Ownership
•
•
•
User — Specify the user name of the Oracle owner.
Group — Specify the group name of the Oracle owner.
System — Specify the host name of the RMC-O backup server.
IMPORTANT:
Specify the name of the backup specification at the end. The name that you enter must match the
specified <backup_specification_name>.
9. In Application Specific Options, specify the host name of the backup server where the RMAN backup
will take place.
IMPORTANT:
Use Data Protector User Interface from a Windows system to access the Cell Manager when creating a
backup specification and to specify the backup server name for the Application Specific Options. Failure
to specify the backup server name in the Application Specific Options results in the backup of
production database instead of clone database.
Modify Data Protector RMAN script
Procedure
1. Change the following lines if you are using the 3PAR_RMO_Online or 3PAR_RMO_Archive template:
backup
format 'backup_specification <app_name_%s:%t:%p>.dbf
archivelog all;
2. Change to following lines to:
backup
format 'backup_specification <app_name_%s:%t:%p>.dbf
archivelog all skip inaccessible;
Modify Data Protector RMAN script
95
Or,
backup
format 'backup_specification <app_name_%s:%t:%p>.dbf
archivelog all not backed up 1 times skip inaccessible;
3. If the control file object is selected, change the following lines:
backup
format 'backup_specification <app_name_%s:%t:%p>.dbf
current controlfile;
Change the following lines to:
catalog controlfilecopy '$ORACLE_HOME/dbs/backup_ctrl$ORACLE_SID';
backup
format 'backup_specification <app_name_%s:%t:%p>.dbf
controlfilecopy '$ORACLE_HOME/dbs/backup_ctrl$ORACLE_SID';
NOTE:
The <backup_specification>, <app_name>, $ORACLE_HOME, and $ORACLE_SID must be replaced
with actual values.
Configure TNS naming service on the RMC-O backup server
Procedure
1. In
$ORACLE_HOME/network/admin/tnsnames.ora
on the RMC-O backup server, check an entry as follows:
<Network Service Name>=
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = TCP)(HOST = <RMO Backup Server Name
(and NOT the db server name)>)(PORT = 1521))
)
(CONNECT_DATA =
(SERVICE_NAME = <Service Name>)
)
)
Backup and database schema changes
If tablespaces are added or deleted from the database, the backup specification must be modified in the Data
Protector GUI to reflect the schema changes. This activity is mandatory to retain the created tablespaces in
the backup.
96
Configure TNS naming service on the RMC-O backup server
Media backups
RMC-O can be used with either HPE StoreOnce, HPE Data Protector, Symantec NetBackup, and Oracle
RMAN to protect and restore the snapshots created by RMC-O.
About media backup operations
RMC from which the backup operation is initiated must be configured for performing ISV media backups on
the backup server.
RMC-O integrates HPE 3PAR StoreServ Snapshot Software feature with Symantec NetBackup (NBU), HPE
Data Protector, and Oracle RMAN to perform snapshot off-host backup. Snapshot off-host backup can
dramatically reduce performance impact on the database server as well as minimize database down time or
the time database in backup mode during backup.
RMC-O supports Symantec NetBackup and Oracle RMAN backup methods. The backup method can be
specified during Recovery Manager configuration process. Symantec NetBackup backup method can be used
to perform backup of a database whose database files are on file systems. Oracle RMAN backup method can
be used to perform backup of a database whose database files are either on file systems or ASM disk group.
For Oracle RMAN backup method, a database can be backed up to a local disk (Symantec NetBackup or
HPE Data Protector is not required) or to a tape using Symantec NetBackup or HPE Data Protector.
If Oracle RMAN (with or without Symantec NetBackup or HPE Data Protector) is selected, the primary (not
standby) database must be registered with an Oracle Recovery Catalog. Starting with Oracle 11g, an RMAN
backup image of a standby database to local disk cannot be seen from the Recovery Catalog from the
production database. Therefore, the backup image cannot be restored to the production database.
For Symantec NetBackup, a database backup must be a full backup. An incremental database backup is not
possible. An archive log backup can be used to simulate an incremental backup. An archive log backup can
be a full, a differential incremental (incr), or a cumulative incremental backup. This backup method is
supported for databases residing on filesystem. For ASM managed databases, this procedure performs a
backup of any meta data residing on filesystems. Always use NetBackup with Oracle RMAN to back up ASM
managed databases.
For Oracle RMAN or Oracle RMAN with Symantec NetBackup, a database backup can be a full, a differential
incremental (incr), or a cumulative incremental (cinc) backup. An archive log backup must always be a full
backup since incremental backups of archive logs are not supported. A restore from any incremental or
cumulative backup is not allowed unless a previous full backup exists and is already restored.
To recover to the point of failure, perform a restore from the last full backup and then use Oracle RMAN to
perform any media recovery so that the archive logs can be applied automatically to the restored datafiles.
For Oracle RMAN with HPE Data Protector, a database backup can be a full, or an incremental level 1 (incr1)
to level 4 (incr4) backup. By default, an incremental backup is differential. To perform cummulative
incremental backup, user must modify the RMAN script in the backup specification of HPE Data Protector.
Archive log backup must be a full backup. Incremental backup of archive log is not supported.
One-Click backup is not supported on Remote Copy configuration. However, you can trigger a backup from
the remote appliance, once the snapshot is available.
The following list describes the restrictions and automated scripts that are generated when configuring
Recovery Manager.
For NBU (user-managed) backup:
•
•
The Symantec NetBackup client must be installed on the backup server and database server.
At least one NBU policy of standard type must be created and configured for database backup. Optionally,
a separate NBU policy of standard type can be created and configured for archive log backup.
For Oracle RMAN, Oracle RMAN with Symantec NetBackup and Oracle RMAN with Data Protector back up:
Media backups
97
•
•
•
•
The backup server must have same or higher Oracle major release version than the Oracle major release
version on the database server.
An Oracle RMAN Recovery Catalog database is required. Refer to RMC-O User's Guide for detail on how
to create and configure RMAN Recovery Catalog database.
For Oracle RMAN with Symantec NetBackup backup, the Symantec NetBackup Client with Oracle
Integration Agent must be installed on the backup server and RMC-O application server. The Symantec
NetBackup master server can be installed on any servers. A Symantec NetBackup Policy of Oracle type
must be precreated for database backup (online, offline, or datafile). Optionally, a separate Symantec
NetBackup policy of Oracle type can be created and configured for archive log backup (archlog). Refer to
Recovery Manager User's Guide for detail on how to create Symantec NetBackup Policy.
For Oracle RMAN with HPE Data Protector backup, the HPE Data Protector Client with Oracle Integration
Agent and User Interface Components must be installed on the backup server and RMC-O application
server. The HPE Data Protector Cell Manager can be installed on any servers. The HPE Data Protector
User Interface Component must be installed on a Windows server to access the HPE Data Protector Cell
Manager. An HPE Data Protector Oracle backup specification must be created before database backup
(online, offline, or datafile). Optionally, a separate HPE Data Protector Oracle backup specification can be
created and configured for archive log backup (archlog). Refer to Recovery Manager User's Guide for
detail on how to create HPE Data Protector Backup Specification.
NOTE:
Simultaneous media backups of the same database on the same backup server cannot be performed.
However, Express Protects and a media backup can run simultaneously.
Protecting snapshots on media using ISVs
Procedure
1.
2.
Click the HPE Recovery Manager Central main menu and then click Servers.
Perform one of the following:
3.
• On the master pane of the Servers screen, click + Register Oracle Server.
• Select Register Server from the Actions menu.
Select the Server type as Backup.
NOTE:
The backup server can also be legacy RMO backup server having catalog repository information.
You can migrate this repository to RMC-O.
4.
5.
6.
7.
98
Provide the following details:
a. IP-Host name— IP address or host name of the server to be configured for backup.
b. Username — User name of the server. The user must have root privileges.
c. Password — Password of the server.
d. Description — Description or additional comments about the server.
Click OK.
Create a Protection policy.
To configure the default RMC appliance to be used with media backup, enter the following command in
the CLI:opt/hpe/rmc/oracle/rmco_cli/scripts/rmc_config.py -i <IP Address> -u
<username> -p <password> -f Do you want to use this appliance for RMC Oracle
media backups triggered from ISV backup software? Enter Y/Yes or N/No: Y
INFO: RMC <IP Address> will be used as default ONLY for media backups
triggered from ISV backup software. RMC appliance with IP <IP Address> is
already configured. Updating the existing configuration. Successfully
registered RMC appliance <IP Address> .
Protecting snapshots on media using ISVs
NOTE:
Whenever RMC credentials are changed, always execute the command in step 7 to update the
RMC credentials on the backup server.
8.
9.
10.
11.
Click the HPE Recovery Manager Central main menu and then click Databases.
Select a database from the master pane.
From the Actions menu, select Protect.
On the Create Protect window, perform the following:
•
Backup Vendor
Select one of the following backup vendors:
•
•
•
◦ RMAN
◦ RMAN NBU
◦ RMAN DP
◦ NBU
Provide a Name and a Description for the protect.
To search and select a Protection Policy Name from the list of available protection policies, click
Select.
Specify the Backup Type as Full, Incr, Cinc
For RMAN, RMAN_NBU, and NBU, you can select the backup type as Full, Incr, or Cinc.
•
For RMAN DP, you can select among Full, Incr1, Incr2, Incr3, and Incr4.
Specify the following optional fields:
◦
◦
◦
Snapshot Name
Expiration Time
Retention Time
NOTE:
If you want to override the Expiration time or Retention time values of the snapshot
associated with this backup for the values present in the protection policy, you must specify
them in the
Create Protect
dialog. The values that you specify in the Create Protect dialog are applicable to the
particular snapshot and take the highest precedence.
•
•
•
Select or clear the Retain Snapshot option.
Specify the Backup Method by selecting one of the options for backup from Online (Hot) Backup,
Archive logs only, Offline (Cold) Backup, and Datafile Only.
Select or clear Schedule. If you select the Select option, then enter the following details:
◦ Specify a Scheduler Name.
◦ Specify a Scheduler Description.
◦ Specify the schedule Frequency..
◦ Specify the Start time.
12. To protect a snapshot on media using ISV, click Ok.
About restore media backup
The restore media operation restores databases, tablespaces, data files, and archive logs from a media
backup.
About restore media backup
99
For NBU (User-managed) restore, we can restore to an alternate server on an alternate mount point. For
Oracle RMAN restore, it is always restored to the database server.
If Symantec NetBackup is used and if a restore is performed to an alternate host, ensure that backup images
created from the backup server are available to the alternate host. For example, if the system date on the
alternate host is earlier than from the RMC-O backup server, backup images may not be available to be
restored to the alternate host. Ensure that a valid database instance is running on the alternate host and all
the required parameters like SPFILE, CONTROLFILE, and so on are set correctly.
Restore is not supported on Remote Copy configuration.
The following restrictions apply when restoring a media back up:
•
•
•
•
•
•
•
•
When restoring the database control file (Restore database control files option), the current database
instance must be in STARTED mode (startup nomount). If the database is a Real Application Cluster
(RAC) database, all other RAC instances must be in CLOSED mode. Restoring the database control file
along with individual datafile or tablespace is not supported as it is not possible to perform media recovery.
If the original database is a physical standby database, the backup control file generally cannot be used to
restore to the primary (production) database. This occurs as they are not compatible unless Oracle 11g is
in use and Oracle RMAN is used to restore.
When restoring a database instance without restoring control file, the database instance must be in
MOUNTED mode. If the database is a Real Application Cluster (RAC) database, all other RAC instances
must be in CLOSED mode.
When restoring individual tablespaces or datafiles, the database can be in OPEN or MOUNTED mode. If
the database is in OPEN mode, the corresponding tablespaces must be offline.
Restoring control files along with datafiles and/or tablespaces is not allowed.
If the database is an ASM managed database, all ASM disk groups must be mounted before running this
command.
For NBU (user-managed) restore, a file named /usr/openv/netbackup/db/altnames/
<alt_server> or /usr/openv/netbackup/db/altnames/No.Restrictions must be created on
the NBU master server to perform restoration to a host (including the original database server) that differs
from the backup server. <alt_server> s the host name of the database server to restore.
If the backup tool was chosen to be RMAN backup to local disk, then the backup images must be
accessible to the restore host.
Starting with Oracle 11g, an RMAN backup image of a standby database, which was backup to local disk,
cannot be restored since, the backup image cannot be seen from the Recovery Catalog from the primary
(production) database. To restore, the following steps must be performed manually:
◦
◦
◦
The backup image (pieces) must be manually copied from the backup server to the primary
(production) server.
The backup pieces must be then cataloged manually with the Recovery Catalog from the primary
(production) server.
Perform restore manually using Oracle RMAN.
Depending on the Snapshot type of backup image (online, offline, datafile, or archlog), corresponding
database files are restored appropriately.
For NBU (user-managed) restore:
•
•
•
•
•
Control files are not restored by default.
For an online Snapshot, both datafiles 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 Snapshot, only datafiles are restored.
For a datafile only Snapshot, only datafiles are restored.
For an archive log Snapshot, only archive logs are restored.
For Oracle RMAN restore:
100
Media backups
•
•
•
•
•
Control files are not restored by default.
For an online Snapshot, 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 Snapshot, only data files are restored.
For a datafile-only Snapshot, only data files are restored.
For an archive log Snapshot, archive log restoration is not supported as Oracle RMAN can restore
necessary archive logs during recovery (refer to Oracle documentation for details on how to use Oracle
RMAN for recovery).
Restoring media backup
This procedure completes the physical restore operation. However, to get the database back to a consistent
state, logical recovery operation has to be performed. The process of logical recovery of the database is
described in the subsequent section.
Procedure
1.
2.
3.
4.
5.
Click the HPE Recovery Manager Central main menu and then click Databases.
On the databases details pane, select Protection View from the view selector.
Click Protects and select a protect from the list of Protects.
Click Action and select Restore.
Specify the following details in the Restore dialog:
a. For RMAN NBU and RMAN types of backup systems,
•
Select either Full Restore, Restore TableSpace, or Restore Datafile type of database objects.
◦
For Restore TableSpace, search and select the table spaces from the Select Table Spaces
dialog. Click Change Selection to change the selected table space.
NOTE: For a backup created using an offline mode snapshot containing tablespaces that
span across files, duplicate entries might be displayed. However, the selection of any entry
restores the entire tablespace.
◦
For Restore Datafile, search and select data files from the Select Data File dialog. Click
Change Selection dialog. Click Change Selection to change the selected data file.
b. For RMAN DP type of backup system,
Select either Full Restore, Restore Datafile, or type of database objects.
6. Select or clear the Restore database control files.
7. Search and select an oracle server to specify the Alternate Host.
8. Specify the optional Alternate SID and Alternate Home optional fields.
IMPORTANT:
For restore that involves RMAN, the DBID of the source and target databases have to be identical.
9. Click Restore.
NOTE: If the very first RMAN backup is an inc or cinc backup, then it can be selected for restore
since, they are treated as level-0 (level zero) RMAN backups internally. However, a non level-0
RMAN backup cannot be selected for restore.
Recovery processes
RMAN DP
Restoring media backup
101
Logical recovery can be performed using RMAN. Connect to RMAN on the application server (or alternate
server, if specified) as described in the following snippet:
rman target / catalog <rman_user>/<password>@<catalog_db>
In the RMAN command prompt, run the following snippet:
RUN {
ALLOCATE CHANNEL c1 TYPE SBT_TAPE
PARMS 'SBT_LIBRARY=/opt/omni/lib/libob2oracle8_64bit.so,ENV=
(OB2BARTYPE=Oracle8,OB2BARLIST=<backup_specification>)';
ALLOCATE CHANNEL c2 TYPE SBT_TAPE
PARMS 'SBT_LIBRARY=/opt/omni/lib/
libob2oracle8_64bit.so,ENV=(OB2BARTYPE=Oracle8,OB2BARLIST=<backup_specification>
)';
RECOVER DATABASE;
RELEASE CHANNEL C1;
RELEASE CHANNEL C2;
}
NOTE:
•
Replace the argument of
RECOVER
command with either
TABLESPACE
or
DATAFILE
•
along with the corresponding names in the snippet to perform recovery of tablespaces or datafiles.
Use
SET UNTIL TIME
,
SET UNTIL SCN
,
SET UNTIL SEQUENCE
•
clauses in the snippet to perform a point in time recovery.
The backup images must be accessible to the restore host.
RMAN NBU
Logical recovery can be performed using RMAN. Connect to RMAN on the application server (or alternate
server, if specified) as described in the following snippet:
rman target / catalog <rman_user>/<password>@<catalog_db>
In the RMAN command prompt, run the following snippet:
RUN {
ALLOCATE CHANNEL c1 TYPE SBT_TAPE;
ALLOCATE CHANNEL c2 TYPE SBT_TAPE;
SEND 'NB_ORA_CLIENT=<RMC-O backup server>';
102
Media backups
RECOVER DATABASE;
RELEASE CHANNEL C1;
RELEASE CHANNEL C2;
}
NOTE:
•
Replace the argument of
RECOVER
command with either
TABLESPACE
or
DATAFILE
•
along with the corresponding names in the snippet to perform recovery of tablespaces or datafiles.
Use
SET UNTIL TIME
,
SET UNTIL SCN
,
SET UNTIL SEQUENCE
•
clauses in the snippet to perform a point in time recovery.
Replace the
RMC-O backup server
with the client name as specified in NetBackup.
RMAN
Logical recovery can be performed using RMAN. Connect to RMAN on the application server (or alternate
server, if specified) as described in the following snippet:
rman target / catalog <rman_user>/<password>@<catalog_db>
In the RMAN command prompt, run the following snippet:
RUN {
ALLOCATE CHANNEL c1 TYPE DISK;
ALLOCATE CHANNEL c2 TYPE DISK;
RECOVER DATABASE;
RELEASE CHANNEL C1;
RELEASE CHANNEL C2;
}
Media backups
103
NOTE:
•
Replace the argument of
RECOVER
command with either
TABLESPACE
or
DATAFILE
•
along with the corresponding names in the snippet to perform recovery of tablespaces or datafiles.
Use
SET UNTIL TIME
,
SET UNTIL SCN
,
SET UNTIL SEQUENCE
clauses in the snippet to perform a point in time recovery.
NBU
Logical recovery process is similar to that of a snapshot and express protect.
Deleting media backup
To delete a backup from the ISV backup software, perform these procedures:
Procedure
1. Deleting RMAN DP backup using Data Protector user interface or Deleting RMAN DP backup using
commands.
2. Deleting RMAN NBU backup.
3. Deleting RMAN backup.
4. Deleting NBU backup
104
Deleting media backup
RMC-O commands
This chapter describes the following commands:
About RMC-O commands
This chapter describes the RMC-O command-line utilities. Use the RMC-O Command Line Interface (CLI) to
manage RMC-O functionality using commands. Before using the CLI commands, you must first log in to the
appliance with a valid username and password. The command-line utilities are located in /opt/hpe/rmc/
oracle/rmco_cli/scripts.
To run RMC-O CLI commands, you must configure the RMC appliance using rmc_config.py.
rmc_config.py allows you to configure one or more RMC appliances. To use one of the configured RMCs,
either set RMC_IP environment variable to any configured RMC address or pass configured RMC address in
CLI command. RMC address passed in CLI command takes priority over RMC_IP environment variable.
Verify the CLI requirements
Procedure
1. Python 2.6 or 2.7 package must be available for the CLI to operate.
2. RHEL/OEL (6.x or 7.x) 64–bit machine can be used to run the CLI.
3. argparse
Python module must be available.
rmc_config.py
Syntax
•
•
rmc_config.py -i <RMC_appliance_address> -u <appliance_username> -p
<appliance_password> [-a <remote_RMC_address>] [-r -f] [-h] help
rmc_config.py -l <list_RMC>
Description
The rmc_config.py command manages the RMC credentials.
Options
The following options are required:
-i
Specifies the IP address or hostname of the RMC appliance.
-u
Specifies the user name of the RMC appliance.
-p
Specifies the password of the RMC appliance.
-l
Displays the list of configured RMC appliances, address, username, and associated remote RMC (if
configured). This argument is mutually exclusive with other arguments.
RMC-O commands
105
NOTE:
The following are optional:
-a
The corresponding IP address, FQDN, or hostname of target (remote) RMC appliance to be used as
remote RMC appliance in remote copy configuration. Accepts the name what the appliance was
registered with in RMC as a remote appliance. This address is displayed in RMC GUI Remote
Appliance screen against "IP Address" label.
-r
Deconfigures the RMC appliance.
-f
Force to deconfigure the RMC appliance or to register RMC appliance that you want to use for RMC
Oracle media backups triggered from ISV backup software.
-h
Displays a help message
rmco_display
Syntax
•
rmco_display -s <oracle_sid> -p <db_server> [-i RMC_appliance_address] [-r]
•
or
rmco_display -t <snapshot_id> [-s <oracle_sid>] [-p <db_server>] [-i
RMC_appliance_address] [-r]
•
or
rmco_display -s <oracle_sid> -p <db_server> [-i RMC_appliance_address] [-b]
Description
The rmco_display command displays the database snapshots and the snapshot creation time, type, status,
and backup status.
Options
The following options are required:
-s
Specifies the Oracle SID of the database instance.
-p
The corresponding IP address, FQDN, or hostname of database server where the specified Oracle database
instance is running. Provide the name that is provided during the Oracle server registration. The IP/
Hostname field on the Oracle Servers screen lists the server name.
106
rmco_display
NOTE:
The following are optional:
-b
Displays the list of database backups. This flag is mutually exclusive with -t and -r options.
-i
Specifies the RMC appliance IP address or hostname. This appliance must be configured in advance
using rmc_config.py.
-h
Displays a help message.
-t
Specifies the snapshot ID. If this argument is passed, -s and -p become optional and their values are
not processed.
-r
Displays the snapshot retention and expiration time.
rmco_create
Syntax
rmco_create -s <oracle_sid> -p <db_server> [-i RMC_appliance_address] [-o
{online|offline|datafile|archlog}] [-r <retention_time>{d|D|h|H} -f] [-e
<expiration_time>{d|D|h|H}] [-v]
Description
The rmco_create command creates an online, offline, datafile, or an archive log snapshot of the specified
Oracle database instance.
Options
The following options are required:
-s
Specifies the Oracle SID of the database instance.
-p
Specifies the IP address, FQDN, or hostname of database server on which the specified Oracle database
instance is running. Enter the address that was provided during Oracle server registration. The IP/Host name
field on the Oracle Servers screen lists the server name.
rmco_create
107
NOTE:
The following are optional:
-e
The relative time from the current time that the volume will expire.
-f
Forces to create a database snapshot with a retention time.
-h
Displays a help message.
-i
Specifies the IP address or hostname of the appliance. The appliance must be configured in advance
using the rmc_config.py command.
-o
Specifies the snapshot type.
-r
Specifies the amount of time, relative to the current time, that the snapshot will be retained.
-v
Runs the command in verbose mode. This option is ignored and it is useful for backward compatibility
with the RMO CLI command.
rmco_backup
Syntax
•
•
rmco_backup -s <oracle_sid> -p <db_server>[-i RMC_appliance_address] [-o
online|offline|datafile|archlog[,<backup_type>]] [-l <protection_policy_id>] [r <retention_time>{d|D|h|H}] [-e <expiration_time>{d|D|h|H}] [-c clone_home] [d] [-v] [-f]
rmco_backup -t <snapshot_id> [-s <oracle_sid>] [-p <db_server>][-i
RMC_appliance_address] [-o backup_type] [-l <protection_policy_id>] [-c
clone_home] [-v] [-f]
•
For Symantec NetBackup, Oracle RMAN or Oracle RMAN with Symantec NetBackup,
•
<backup_type> = {full | incr | cinc}
For Oracle RMAN with HPE Data Protector,
•
<backup_type> = {full | incr1 | incr2 | incr3 | incr4}
For StoreOnce Backup,
<backup_type> = {fullExpressProtect}
Description
The rmco_backup command initiates a client-side backup of an existing database snapshot or creates a
snapshot of the database and mounts it to the backup server before initiating an immediate backup.
Options
The following options are supported:
-d
108
rmco_backup
Specifies the snapshot to be deleted after an one click backup operation.
-s
Specifies the Oracle SID of the database instance.
-p
Specifies the IP address, FQDN, or hostname of database server on which the specified Oracle database
instance is running. You can enter the name that is provided during Oracle server registration. The IP/Host
name field on the Oracle Servers screen lists the server name.
-t
Specifies the snapshot ID to be backed up.
•
NOTE:
The offline, online, datafile, and archlog options are mutually exclusive.
•
-o online
•
— Creates an online snapshot of a database while it is OPEN (online) before backup. This option is
ignored if a snapshot is specified.
-o offline
•
— Creates an offline snapshot of a database while it is CLOSED (offline) before backup. This option is
ignored if a snapshot is specified.
-o datafile
— Creates a snapshot for all datafiles (not including the archive log destinations and temporary datafile) of
a database while it is OPEN (online) before backup. This option is ignored if a snapshot is specified. A
snapshot created with the
-o datafile
option is only useful when archive log files generated during snapshot creation are also available. You can
create separate snapshots using the
-o archlog
•
options, or use another backup method to back up archive log destinations.
-o archlog
•
— Creates a snapshot of the archive log destination before backup. This option cannot be used if a
snapshot is specified.
-o full
— Performs a full backup of a snapshot. If Symantec NetBackup is selected as the backup method, this
option can be used with the
-o archlog
option to perform full backup of an
archlog
snapshot. RMC-O uses one incremental schedule name for either differential incremental or cumulative
incremental backup, which is predefined in the NBU schedule. If Oracle RMAN is selected as the backup
method, you can use this option to perform full backup of an online, offline,
or datafile
•
snapshot.
-o incr
— Performs an incremental backup of a snapshot.
RMC-O commands
109
This option is not applicable for Oracle RMAN with Data Protector backup.
If Symantec NetBackup is selected as the backup method, you can use this option with the
-o archlog
option to perform incremental backup of an
archlog
•
snapshot. If Oracle RMAN is selected as the backup method, you can use this option to perform an
incremental backup of an online or offline snapshot.
-o cinc
— Performs a cumulative incremental backup of a snapshot.
This option is not applicable for Oracle RMAN with Data Protector backup.
If Symantec NetBackup is selected as the backup method, you can use this option with the
-o archlog
option to perform a cumulative incremental backup of an
archlog
•
snapshot. RMC-O uses only one incremental schedule name for either differential incremental or
cumulative incremental backup, which is predefined in the NBU schedule. If Oracle RMAN is selected as
the backup method, you can use this option to perform a cumulative incremental backup of an online or
offline snapshot.
-o incr1|incr2|incr3|incr4
— Performs an incremental backup of a snapshot. The incr1, incr2, incr3, and incr4 correspond to
incremental backup level 1, 2, 3 and 4 respectively. This option is only applicable for Oracle RMAN with
Data Protector backup. You can use this option with the
-o online|offline|datafile
option to perform incremental backup of a database virtual copy. By default, the incremental backup is
differential. To perform cumulative incremental backup, the RMAN script from the Data Protector Backup
Specification must be changed manually.
110
RMC-O commands
NOTE:
The following are optional:
-c
Specifies the Oracle home directory on the backup server to be used for clone operation. If not
specified, the ORACLE_HOME of the production database is used.
-e
The relative time from the current time that the volume will expire.
-f
Runs the backup task when the flag is passed and waits until the task completes.
-h
Displays a help message.
-i
Specifies the RMC appliance IP address or hostname. This appliance must be configured in advance
using the rmc_config.py command.
-o
Specifies the backup_type. For StoreOnce backup, if backup_type is not passed, default
backup_type is Auto. For Auto backup, first backup will be full and other backups will be incremental.
-l
Specifies the RMC-O protection policy ID. Ensure that you specify this option if no protection policy is
associated with the database.
-r
Specifies the amount of time, relative to the current time, that the snapshot will be retained.
-v
Runs the command in verbose mode. This flag is ignored and thus, does not provide additional logs.
rmco_remove
Syntax
rmco_remove -t <snapshot_id> [-i RMC_appliance_address] [-s <oracle_sid>] [-p
<db_server>] [-v]
Description
The rmco_remove command removes a database snapshot.
Options
The following option is required:
-t
Specifies the snapshot ID.
rmco_remove
111
NOTE:
The following are optional:
-h
Displays a help message.
-i
Specifies the RMC appliance IP address or hostname. The appliance must be configured in advance
using the rmc_config.py command.
-p
Specifies the IP address, FQDN, or hostname of database server on which the specified Oracle
database instance is running. Enter the address that was provided during Oracle server registration.
The IP/Host name field on the Oracle Servers screen lists the server name. This option is ignored and
is useful for backward compatibility with the RMO CLI command.
-s
This option is ignored and is useful for backward compatibility with the RMO CLI command.
-v
Runs the command in verbose mode.
rmco_mount
Syntax
rmco_mount -t<snapshot_id> [-i RMC_appliance_address] [-b <backup_server>] [-m
<mountpoint>] [-s <oracle_sid>] [-p <db_server>] [-r] [-v]
Description
The rmco_mount command mounts an existing snapshot created by the rmco_create command or
rmco_rsync command on the backup server.
Options
The following option is required:
-t
Specifies snapshot ID.
112
rmco_mount
NOTE:
The following are optional:
-i
Specifies the IP address or hostname of the appliance. This appliance must be configured in advance
using rmc_config.py command.
-b
Specifies the IP address, FQDN, or hostname of database server on which the specified Oracle
database instance is running. Enter the address that was provided during Oracle server registration.
The IP/Host name field on the Oracle Servers screen lists the server name. If this argument is not
passed, then mounts the snapshot on the server where the command is being run, provided the server
is registered in RMC-O.
-m
Specifies the location where the snapshot is mounted. The current user must have permission to write
to this location.
By default, the snapshot is mounted at /opt/hpe/rmc/oracle/data/
<db_server>.ora.<oracle_sid>/<snapshot_id>. If the snapshot is for an ASM-managed
database, this option is ignored.
-r
Remounts a snapshot that was mounted previously but unmounted due to system reboot.
-s
This option is ignored and is useful for backward compatibility with the RMO CLI command.
-p
This option is ignored and is useful for backward compatibility with the RMO CLI command.
-v
Runs the command in verbose mode
-h
Displays a help message
rmco_umount
Syntax
rmco_umount -t<snapshot_id> [-i RMC_appliance_address] [-s <oracle_sid>] [-p
<db_server>] [-f] [-v]
Description
The rmco_umount command unmounts a snapshot that was mounted using the rmco_mount command.
Options
The following option is required:
-t
Specifies the snapshot ID.
rmco_umount
113
NOTE:
-i
Specifies the IP address or the hostname of the RMC appliance. The appliance must be configured in
advance using the rmc_config.py command.
The following are optional:
-s
This option is ignored and is useful for backward compatibility with the RMO CLI command.
-p
This option is ignored and is useful for backward compatibility with the RMO CLI command.
-f
Forcibly unmounts a database snapshot. Using this option can corrupt the corresponding read-write
snapshot. However, the read-only snapshot remains intact.
-v
Runs the command in verbose mode.
-h
Displays a help message.
rmco_createdb
IMPORTANT:
In the rmco_createdb command, the option -h is used for cloned Oracle home directory and not for
help as in other CLI commands. This is for the backward compatibility with the RMO CLI commands.
For help message, use --h or -–help.
Syntax
rmco_createdb -t <timestamp> [-n <clone_sid>] [-i RMC_appliance_address]
[-h <clone_ora_home>] [-o ascii|binary|recovery|norecovery] [-d <loc>]
[-s <oracle_sid>] [-p <db_server>] [-v]
Description
The rmco_createdb command creates a fully functional single instance database or starts up the cloned
database in the Mounted mode for RMAN backup.
Options
The following option is required:
-t
Specifies the snapshot ID.
114
rmco_createdb
NOTE:
The following are optional:
-i
Specifies the RMC appliance IP address or hostname. This appliance must be configured using
rmc_config.py.
-n
Specifies the Oracle SID of the clone database. If no value is specified, the clone database has the
same Oracle SID as the original database.
-h
Specifies the Oracle home directory on the backup server. If no value is specified, the ORACLE_HOME
directory of the production database is used.
-d
A comma-separated list of directories or ASM diskgroups (for multiplexing) to store the new online redo
logs and control files of the clone database. If no value is specified, the redo logs are created
at /opt/hpe/rmc/oracle/data/<db_server>.ora.<oracle_sid>/<snapshot_id> on the
backup server.
-o ascii|binary|recovery|norecovery]
Use the following control files for creating a cloned database.
•
-o ascii
•
— Uses an ASCII control file that was saved in the RMC-O repository for creating a clone database.
-o binary
•
— Uses a binary control file that was saved in the RMC-O repository for creating a clone database.
-o recovery
•
— Automatically recovers the clone database using all available archivelogs that exist on the snapshot.
-o norecovery
— Starts the clone database in mounted mode without recovery.
-s
This option is ignored and is useful for backward compatibility with the RMO CLI command.
-p
This option is ignored and is useful for backward compatibility with the RMO CLI command.
-v
Runs the command in verbose mode.
-h
Displays a help message.
rmco_removedb
IMPORTANT:
In the rmco_removedb command, the option -h is used for cloned Oracle home directory and not for
help as in other CLI commands. This is for the backward compatibility with the RMO CLI commands.
For help message, use —h or –help.
rmco_removedb
115
Syntax
rmco_removedb -t <snapshot_id> [-i RMC_appliance_address] [-s <oracle_sid>] [-p
<db_server>] [-n <clone_sid>] [-h <clone_ora_home>] [-f] [-v]
Description
The rmco_removedb command removes a cloned database that was created using the rmco_createdb
command.
Options
The following option is required:
-t
Specifies the snapshot ID.
NOTE:
The following are optional:
-f
Forces the removal of the cloned database.
-h
This option is ignored and is useful for backward compatibility with the RMO CLI command.
-i
Specifies the RMC appliance IP address or hostname. This appliance must be configured in advance
using the rmc_config.py command.
-s
This option is ignored and is useful for backward compatibility with the RMO CLI command.
-p
This option is ignored and is useful for backward compatibility with the RMO CLI command.
-n
This option is ignored and is useful for backward compatibility with the RMO CLI command.
-v
Runs the command in verbose mode.
--help
Displays a help message.
rmco_rsync
Syntax
rmco_rsync -s <oracle_sid> -p <db_server> [-i RMC_appliance_address][-o {online|
offline|datafile|archlog}] [-r <retention_time>{d|D|h|H} -f] [-e
<expiration_time>{d|D|h|H}] [-l <local_backup_server>] [-a
<target_rmc_appliance>] [-k] [-t <target_storage_serial_number>] [-v]
Description
The rmco_rsync command creates an online, offline, datafile, or archlog type snapshot on the remote or
secondary and local or primary HPE 3PAR StoreServ Storage system in a remote copy or synchronous longdistance remote copy configuration.
116
rmco_rsync
Options
-s
Specifies the Oracle SID of the database instance.
-p
Specifies the IP address, FQDN, or hostname of database server on which the specified Oracle database
instance is running. Enter the address that was provided during Oracle server registration. The IP/Host name
field on the Oracle Servers screen lists the server name
NOTE:
The following are optional:
-i
Specifies the name of the RMC appliance’s IP address or hostname. This appliance must be configured
in advance using the rmc_config.py command.
-r
Specifies the amount of time, relative to the current time, that the snapshot will be retained.
-e
Specifies the relative time from the current time that volume will expire.
-l
This option is ignored and it is useful for backward compatibility with the RMO CLI command.
-k
If this flag is passed, then source and target snapshot is retained otherwise only target snapshot is
retained.
-a
Specifies the corresponding IP address, FQDN, or hostname of the target (remote) RMC appliance. If
no value is provided for this option, RMC-O reads the data from the configuration file to determine if a
remote RMC appliance IP is configured.
-t
Specifies the serial number of the target (remote) storage array. For synchronous long-distance
configurations, if the same RMC appliance manages both the target StoreServ arrays, this value must
be passed. In other remote copy configurations, RMC-O internally determines the target array.
-o
Specifies the type of snapshot.
-f
Specifies the force to create a database snapshot with a retention time.
-v
Runs the command in verbose mode. This option is ignored and it is useful for backward compatibility
with the RMO CLI command.
-h
Displays a help message.
RMC-O commands
117
Support ticket
Support ticket option is available from Settings in the RMC user interface.
Figure 11: Support ticket dialog
Selecting a Database automatically includes the list of all RAC nodes from where RMC-O client logs must be
collected. You may also select other servers from Oracle Servers from where RMC-O client logs have to be
captured. For example, if you face any issue with snapshot mount operation, select the database from
Database drop-down menu and the backup server from Oracle Servers dialog, where mount operation was
attempted.
In most of the cases Activity pane provides a hint of the reason for failure and the required actions. If that
does not suffice, you may try to analyze the RMC-O client-side log file /var/log/rmc/oracle/
RMCOLogger located in application and backup servers for some of the common errors and then see the
Troubleshooting chapter of this document.
For RMC-related errors, once you have collected the support ticket, you may look into the rmoracleapp.log and rmoracle-api.log located in <support_ticket>/logs/var/log/rmoracle folder.
For troubleshooting ORA- errors resulting from SQL executions, there will be
<operation>_spool.<db_name>.<shell id> files present in /tmp on failures. These files provide the
details of the errors reported by the database. Based on the operation, look for these files in the Application or
Backup server.
For example, failure of a clone database operation places spool files as follows:
[root@asmbkp1 tmp]# ls —ls /tmp/*spool*
-rw-r—-r—-1 root root 1.1K Aug 9 03:47 /tmp/createdb_spool.asmlibdb.26662
118
Support ticket
Troubleshooting
Cause
This chapter lists the troubleshooting topics for the problems that you may encounter in RMC-O. It lists the
cause and corrective action for a symptom. You need to perform the corrective action to troubleshoot your
problem.
Abort operation of an Express Protect Restore causes the
database to go to an error state
Symptom
Post the successful abort of Restore operation, the database is marked as an error and the operations that
can be performed are limited.
Cause
Tried performing an abort of Restore operation when the volumes were being populated with data.
Action
Procedure
•
Perform a Restore operation from Snapshot or an Express Protect and recover the database (OPEN state)
for the subsequent snapshots and backups to succeed.
Unable to perform a restore of cumulative RMAN backup
Symptom
Restore operation of a cumulative incremental backup encounters an error.
Cause
There was an attempt to perform a Restore of an incremental cumulative backup.
Action
Procedure
•
If the very first RMAN backup is an inc or cinc backup, then it can be selected for restore since, they are
treated as level-0 (level zero) RMAN backups internally. This is described in media backups section.
Failure of media backups
Symptom
The GUI activity displays an RMAN failed for backup error message. On further inspecting the
rmco_rmanbackup.log in /var/log/rmc/oracle on the backup server, displays the errors from
recovery catalog database.
Cause
Incorrect recovery catalog database service name or credentials specified within the Protection Policy.
Troubleshooting
119
Action
Procedure
•
To rectify the catalog database details, edit the corresponding Protection Policy.
ORA-00845: MEMORY_TARGET not supported on this system
Symptom
Backup or clone fails with the error message of memory target while cloning or taking backup on a backup
server.
Cause
Memory size is low on backup server.
Action
Procedure
1. Increase the size of memory of backup server. To increase the /tmpfs size, execute the following
commands:
1. mount -t tmpfs shmfs -o size=5g /dev/shm
2. Edit your /etc/fstab file to include the option you specified above
3. Mount -a
Snapshot mount fails with error pertaining to volume
manager
Symptom
Snapshot mount fails with CheckLvmVgExistence error.
Cause
Volume manager present on the backup server is unresponsive due to stale device entries.
Action
Procedure
•
Restart the backup server and retry the mount operation.
Media backup completion status not reflecting in Activity
page
Symptom
ISV backup software (Data Protector or NBU) displays the job status as Complete or Error. Whereas the
activity page, displays the job is in progress.
120
ORA-00845: MEMORY_TARGET not supported on this system
Solution 1
Cause
RMC credentials are not updated in the backup server.
Action
Procedure
1. To reregister an RMC for media backups, execute rmc_config.py command with the updated password
on the backup server .
2. Before starting the next backup operation, restart the RMC appliance and remove any cloned database
and unmount any snapshots of this database.
Solution 2
Cause
RMC appliance is not reachable from the backup server.
Action
Procedure
1. Ensure that RMC is reachable from the backup server.
2. Before starting the next backup operation, restart the RMC appliance and remove any cloned database
and unmount any snapshots of this database.
Solution 3
Cause
Incorrect backup server registered with either the policy created on the backup software interface or the
protection policy of RMC-O.
Action
Procedure
1. Edit the policy and provide the correct backup server details.
2. Restart the RMC appliance and remove any cloned database and unmount any snapshots of this
database.
Solution 4
Cause
HPE Data Protector cell manager experiences connectivity issues or failed during a backup operation.
Action
Procedure
1. Ensure that HPE Data Protector cell manager is reachable from the backup server.
2. Before starting the next backup operation, restart the RMC appliance and remove any cloned database
and unmount any snapshots of this database.
Troubleshooting
121
New schedule created in RMO post partial successful
migration does not get migrated on reattempt
Symptom
New schedule created in RMO post partial successful migration does not get migrated on reattempt.
Cause
The migration activity does not revert the schedules that were disabled before migration.
Action
Procedure
•
Create schedules in RMC-O for the migrated database.
Update or create recovery set failed —
log_archive_dest_n not set error
Symptom
Snapshot creation failed.
Cause
The parameter value for log_archive_dest_n not specified.
Action
Procedure
•
Verify that the database is running in ARCHIVELOG mode and specify a value for the parameter
log_archive_dest_n.
Auto-update all RAC cluster nodes feature causes few RAC
nodes to be added with an error status
Symptom
Auto-update all RAC cluster nodes feature causes few RAC nodes to be added with an error status.
Cause
DNS is improperly configured with the information about the erroneous RAC nodes.
122
New schedule created in RMO post partial successful migration does not get migrated on reattempt
Action
Procedure
•
Rectify the DNS configuration and edit the server properties in RMC-O user interface.
Mounted or cloned snapshots do not get migrated with
appropriate status in Remote Copy environment
Symptom
The mounted or cloned snapshot in RMO does not appear mounted or cloned in the remote appliance post
migration.
Cause
Registration of a remote backup server is not performed on remote appliance.
Action
Procedure
1.
2.
3.
4.
Shut down the cloned database manually using SQL commands.
Unmount the file systems or ASM diskgroups.
Detach the RW snapshot volumes corresponding to the mounted snapshot.
Reboot the remote backup server.
Database startup encounters errors related to SPFILE post a
successful snapshot or Express Protect restore
Symptom
Attempt to start a database displays Failed to open file <SPFILE>.
Cause
During database startup, the default SPFILE is not present in the specified location.
Action
Procedure
•
Use a different pfile to start the database and create an SPFILE when required. Alternatively for a
pfile, you can use the init.ora present in the meta data as part of the restore operation.
Mounting of snapshot fails with An Unknown error
occurred
Symptom
Mounting of a snapshot fails with the display of An Unknown error occured error on the activity page.
Cause
Snapshot has expired and hence removed from the array.
Mounted or cloned snapshots do not get migrated with appropriate status in Remote Copy environment
123
Action
Procedure
•
Perform a database Refresh that removes any expired snapshots of the database from the RMC-O
catalog.
Clone operation fails with error MEMORY_TARGET
unsupported
Symptom
Clone operation triggered individually or as part of a media backup, fails with an error message
MEMORY_TARGET unsupported.
Solution 1
Cause
Memory requirements for the backup server are not met.
Action
Procedure
•
Ensure that the RAM size on the backup server is equal or greater than the application server.
Solution 2
Cause
There are many cloned databases running simultaneously on the backup server.
Action
Procedure
•
To free up memory space for the new cloned databases, remove a few cloned databases . Also, ensure
not to trigger many simultaneous media backups.
Cannot determine archive log mode for database <name>
Symptom
Unable to determine the archive log mode for database <name>
Cause
Failed to retrieve the archive log mode for the specified database.
124
Clone operation fails with error MEMORY_TARGET unsupported
Action
Procedure
•
Manually log on to the database and check if the database is running normally. Most likely, either the
database is not open or the archive log destination is full, which could cause the database to hang.
SCSI inquiry failed for device devicename.
Symptom
Unable to determine the archive log mode for database <name>.
Cause
When performing a SCSI inquiry, the specified device found is not an HPE 3PAR device.
Action
Procedure
•
Normally this error can be ignored if it only appears in the RMC-O log file, as RMC-O performs a SCSI
inquiry for all disks to search for HPE 3PAR disks. For RMC-O to work, datafiles and archive log files must
reside on HPE 3PAR volumes.
Unable to resolve the file path for <file name>
Symptom
Unable to resolve the file path for <file name>.
Cause
RMC-O fails to retrieve the real path for the specified file or directory.
Action
Procedure
•
Check if the file or directory is valid.
Automatic log archiving is disabled
Symptom
Automatic log archiving is disabled.
Cause
Archive log mode in the primary Oracle database is disabled. Certain backup types (online, archonly, datafile)
require archive log mode to be enabled.
SCSI inquiry failed for device devicename.
125
Action
Procedure
•
Enable the archive log mode from the primary database and try the operation again.
Unable to determine status of database instance <name>
Symptom
Unable to determine status of database instance <name>.
Cause
Failed to retrieve the database instance status.
Action
Procedure
•
Verify if the database is healthy. Make sure that the parameters in the configuration files are up to date.
<file name> is neither a regular file, directory, block nor a
character device
Symptom
An error <file name> is neither a regular file, directory, block nor a character device is displayed.
Cause
When discovering devices used by the Oracle database, RMC-O failed to determine the type of the specified
device.
Action
Procedure
•
Make sure that the device is a supported device type.
One or more archivelog destinations of the database have
error status
Symptom
An error message One or more archivelog destinations of the database have error status is displayed.
Cause
When trying to retrieve archive log destinations, one or more archive log destinations were found with ERROR
status.
126
Unable to determine status of database instance <name>
Action
Procedure
•
Ensure all archive log destinations have enough space and have no errors.
Unable to find file system for file <file name>
Symptom
An error message Could not find file system for file <file name> is displayed.
Cause
The specified file or directory is a regular file or qio file, but the operation could not retrieve its file system
type.
Action
Procedure
•
Make sure the mnttab contains the file system for the specified file or directory. Contact customer support
for further investigation.
Unable to convert oracleasm disks
Symptom
An error message Could not convert oracleasm disks is displayed.
Cause
Failed to retrieve the OS device for Oracle asmlib devices, which are labeled as ORCL:.
Action
Procedure
•
RMC-O checks the major and minor number for Oracle asmlib devices using the oracleasmquerydisk
command, and tries to find the same OS device with the same major and minor number. Make sure that
the Oracle asmlib version is within the configuration matrix. Contact customer support for further
investigation.
Unsupported file system type of <file type>
Symptom
An error message Unsupported file system type of <file type> is displayed.
Cause
RMC-O cannot recognize the specified file system.
Unable to find file system for file <file name>
127
Action
Procedure
•
Check HPE 3PAR configuration matrix for supported file system types
Unable to decide the OCFS2 version.
Symptom
An error message Could not decide OCFS2 version is displayed.
Cause
During rmco_mount, if RMC-O discovers that a snapshot file system is an OCFS2 file system, RMC-O will try
to reset the volume's UUID, using the OCFS2 command tune.ocfs2, and only supporting OCFS2 1.4.1 or
later release. If the OCFS2 version cannot be determined, the error occurs.
Action
Procedure
•
Make sure that OCFS2 is installed and configured on the backup server.
Unable to discover devices used by database <name>
Symptom
An error Could not discover devices used by database <name> is displayed.
Cause
RMC-O failed to retrieve the devices used by datafiles or archive log destinations.
Action
Procedure
•
Ensure datafiles and archive log destinations are on separate HPE 3PAR volumes and ensure that the file
system type is supported by RMC-O (refer to the HPE 3PAR configuration matrix). Check log files from
both the database server and the backup system. The immediate preceding error message may indicate
the reason for the failure. If none of the reveals the failure reason, contact customer support for further
investigation.
Unable to open device <device ID>
Symptom
An error Could not open device <device ID> is displayed.
Cause
System call open() failed for the specified device.
128
Unable to decide the OCFS2 version.
Action
Procedure
•
Check if the device exists and has correct permissions. Contact customer support for further investigation.
Snapshot <snapshot name> is not currently mounted at
<location>
Symptom
An error The snapshot <snapshot name> is not currently mounted at <location> .
Cause
Trying to clone a database with the specified snapshot using the binary control file option failed. The snapshot
must be mounted at the file system to be able to use the binary control file to clone.
Action
Procedure
•
Use the RMC-O user interface to unmount the snapshot and mount it on a desired location.
Unable to query for ASM disk groups from the ASM instance
Symptom
An error message Could not query for ASM disk groups from the ASM instance is displayed.
Cause
Failed to run an SQL query against the +ASM instance on the backup server.
Action
Procedure
•
Check the Oracle alert log (ASM instance) and RMC-O activity page log for more details.
ORA-15063: ASM discovered an insufficient number of
disks for diskgroup
Symptom
An error message ORA-15063: ASM discovered an insufficient number of disks for diskgroup during
mount or unmount operation is displayed.
Cause
Failed to retrieve the ASM disks forming the diskgroup (for example, duplicate disks found).
Snapshot <snapshot name> is not currently mounted at <location>
129
Action
Procedure
•
Check the Oracle alert log (ASM instance) and rectify the errors mentioned there before attempting next
mount or unmount operation.
Unable to determine if ASM rebalancing is in progress
Symptom
An error Could not determine if ASM rebalancing is in progress is displayed.
Cause
Before RMC-O creates a snapshot either using rmco_create or rmco_rsync, if datafiles or archive log files
are in ASM disk groups, RMC-O will check to make sure that there is no ASM disk rebalance is in progress.
The error occurs when the SQL query fails.
Action
Procedure
•
Check the ASM instance from the primary database and make sure the database and the ASM instance
are in normal running mode.
ASM rebalancing operation is in progress
Symptom
An error ASM rebalancing operation is in progress is displayed.
Cause
Before RMC-O creates a snapshot for the datafile volumes or archivelog destination volumes that reside on
ASM disk groups, RMC-O discovers an ASM rebalance operation is in progress.
Action
Procedure
•
Wait until the rebalance operation finishes, or stop the rebalance temporarily.
Unable to query the clone database for the control file's
location
Symptom
An error Could not query the clone database for the control file's location is displayed.
Cause
During the process of rmco_createdb, the Oracle database is found to use OMF format. After the database
is mounted (using binary control file to clone) or created (using ascii control file to clone), RMC-O has to
retrieve the current control file location and put them into the init.ora file. During this process, the SQL
command failed.
130
Unable to determine if ASM rebalancing is in progress
Action
Procedure
•
Check the alert log and RMC-O activity page for more details. Manually query the cloned the database to
see if there are any problems.
Unable to find device %s
Symptom
An error Unable to find device %s is displayed.
Cause
Failed to retrieve the OS device used by the database while executing rmco_create or rmco_rsync.
Action
Procedure
•
Check the log file from both the RMC-O application server and the backup system to find out more
information. Contact customer support for further investigation.
Database is not in managed recovery mode
Symptom
An error The database is not in managed recovery mode is displayed.
Cause
The database, RMC-O runs against, is a physical standby database. However, the database is not in
managed recovery mode and there is no MRP process in the database.
Action
Procedure
•
Check the physical standby database and make sure it is working in managed recovery mode.
Database instances are still not closed
Symptom
An error The following database instances are still not closed: <database instance name> is displayed.
Cause
Creating an offline snapshot for an RAC database requires all instances in this RAC database to be offline.
Unable to find device %s
131
Action
Procedure
•
Shut down all instances in this RAC database and run the command again.
Unable to generate ASCII control file for database
Symptom
An error Could not generate ascii control file for database <database name> is displayed.
Cause
Trying to run SQL command alter database backup control file to trace failed.
Action
Procedure
•
Check the Oracle alert.log file. Check if the database is in valid status and check if there is enough
space.
Unable to change asm_diskstring to %s
Symptom
An error Could not change asm_diskstring to '%s' is displayed.
Cause
When trying to mount a snapshot which contains ASM devices, the SQL command failed to change the
asm_diskstring parameter in the +ASM instance on the backup server.
Action
Procedure
•
Check the context from screen or log file and try to do it manually in +ASM instance on the backup server.
Database is neither a primary nor physical standby database
Symptom
An error The database is neither a primary nor physical standby database is displayed.
Cause
RMC-O currently only supports creating snapshots for a database that is either a primary database or a
physical standby database.
132
Unable to generate ASCII control file for database
Action
Procedure
•
Run RMC-O against a supported database
Existence of archive log gap between the primary and
standby databases
Symptom
An error Archive log gap exists between the primary and standby database is displayed.
Cause
RMC-O runs against a physical standby database. Trying to create an online or archive log only snapshot fails
because there is a gap for archive log files.
Action
Procedure
•
Transfer the archive log files from the RMC-O application server to the physical standby database.
Unable to stop redo apply process for database %s
Symptom
An error Could not stop redo apply process for database '%s' is displayed.
Cause
Trying to stop the managed recovery process for the physical standby database failed. The SQL command
used is ALTER DATABASE RECOVER MANAGED STANDBY DATABASE CANCEL.
Action
Procedure
•
Check the alert.log file and make sure that the physical standby database is valid.
Unable to restart a redo apply process for a database
Symptom
An error Could not restart redo apply process for database <database name> is displayed.
Cause
The SQL command ALTER DATABASE RECOVER MANAGED STANDBY DATABASE DISCONNECT FROM
SESSION failed.
Existence of archive log gap between the primary and standby databases
133
Action
Procedure
•
Check the alert.log file for the physical standby database and make sure it is in the valid state.
Unable to determine Oracle ASM version
Symptom
An error Could not determine Oracle ASM version is displayed.
Cause
Failed to determine the ASM software version.
Action
Procedure
•
Make sure the Oracle binary for ASM is installed correctly. Make sure that the values in the configuration
files are valid.
Incorrect configuration of Oracle ASMLib
Symptom
An error Oracle ASMLib has not been configured correctly is displayed.
Cause
In Linux, if the datafiles and archive log destinations use asmlib managed devices, on the backup server,
asmlib must also be configured. This error occurs when rmco_mount finds the asmlib status wrong.
Action
Procedure
•
Ensure that the supported asmlib packages are installed, configured, and oracle asmlib is in correct status.
Oracle ASMlib has not been installed
Symptom
An error Oracle ASMLib has not been installed is displayed.
Cause
In Linux, the required file /etc/sysconfig/oracleasm or /etc/sysconfig/Oracleasm_dev_oracleasm which contains the oracleasm configurations is missing.
134
Unable to determine Oracle ASM version
Action
Procedure
•
Install asmlib and configure oracleasm correctly.
ORACLEASM_SCANORDER from <file> does not include
<entity>
Symptom
An error The ORACLEASM_SCANORDER from <file> does not include <entity> is displayed.
Cause
In Linux, during snapshot mount process, RMC-O discovered that asmlib is used from the database server
and on the backup server with the multipath daemon running. RMC-O will look for devices with device mapper
multipath configured and used from the backup server. In this case, the ORACLEASM_SCANORDER
parameter in /etc/sysconfig/oracleasm must contain the value dm to instruct oracleasm to scan device
mapper devices.
Action
Procedure
•
Reconfigure oracleasm to contain dm for ORACLEASM_SCANORDER. Restart oracleasm to put the
changes in effect.
Unable to retrieve ASM instance SID for database <database
name>
Symptom
An error 3PAR1239: ERROR: Could not retrieve ASM instance SID for database <database name> is
displayed.
Cause
Failed to retrieve the ASM instance SID from the specified database.
Action
Procedure
•
Check the alert.log file for more details, and make sure that the parameters in configuration files are
up to date.
Unable to retrieve ASM clients for the ASM instance
<instance name>
Symptom
An error 3PAR1240: ERROR: Could not retrieve ASM clients for the ASM instance <instance name> is
displayed.
ORACLEASM_SCANORDER from <file> does not include <entity>
135
Cause
Failed to retrieve the ASM client names from the ASM instance on the primary database server.
Action
Procedure
•
Check the alert.log file for more details. Make sure that the parameters in configuration files are up-todate and that the ASM instance is in healthy state.
One or more ASM disk groups are shared between
databases
Symptom
An error 3PAR1241: ERROR: One or more ASM disk groups are shared between databases is displayed.
Cause
RMC-O requires that an ASM disk group be exclusively used by one database. This is to avoid the potential
rollback (promote) operations destroying data from other databases or applications.
Action
Procedure
1. Do not share disk groups between different databases.
Unable to retrieve ASM disks for database %s
Symptom
An error 3PAR1242: ERROR: Could not retrieve ASM disks for database %s is displayed.
Cause
Failed to retrieve ASM disks used by the specified database from ASM instance.
Action
Procedure
•
Check the alert log for more details. Make sure that the parameters in configuration files are up-to-date
and that the ASM instance is in healthy state.
Unable to find ASM disk group <name>
Symptom
An error 3PAR1243: ERROR: Could not find ASM disk group <name> is displayed.
Cause
Unable to find the specified ASM disk group in ASM instance from the primary RMC-O application server.
136
One or more ASM disk groups are shared between databases
Action
Procedure
•
Check the log file to find more information. Contact customer for further investigation.
Unable to shut down (%) database instance <name>
Symptom
An error 3PAR1244: ERROR: Could not shutdown (%) database instance <name> is displayed.
Cause
Unable to shut down the specified database instance during the rmco_removedb process.
Action
Procedure
•
Check the alert log and RMC-O log file for more details. Use the -f option to remove the cloned database.
Unable to parse file %s
Symptom
An error 3PAR1245: ERROR: Could not parse file %s is displayed.
Cause
An error occurred either during the creation of snapshot time or cloning database time.
Action
Procedure
•
If during database cloning time, check the saved init.ora file to see if there are any unusual characters
or wrong syntax. Make sure that the primary database has the correct parameter file. Check the log file for
more details. Contact customer support for further investigation.
Unable to create spfile <file name> from pfile <file name>
Symptom
An error 3PAR1247: ERROR: Could not create spfile <file name> from pfile <file name> is displayed.
Cause
Failed to run the SQL command to create a spfile from a specified pfile.
Unable to shut down (%) database instance <name>
137
Action
Procedure
•
Check the alert log file or RMC-O log file for more details.
Unable to retrieve database files
Symptom
An error 3PAR1248: ERROR: Could not retrieve database files is displayed.
Cause
Failed to run the SQL command to retrieve the physical location of the archive log destinations.
Action
Procedure
•
Make sure the archive log destinations are in valid state and have enough space. Make sure that the
primary database is running normally.
An error to set value for log_archive_dest_n parameter is
displayed
Symptom
An error 3PAR1250: ERROR: Please explicitly set value for parameter log_archive_dest_n is
displayed.
Cause
The detail can be found in bug 41996. If there is no explicit value set for this parameter, it could cause
rmco_createdb tasks to fail.
Action
Procedure
•
Set this parameter value explicitly.
Unable to sync file system <file system name> on host <host
name>
Symptom
An error 3PAR1252: ERROR: Could not sync file system <file system name> on host <host name> is
displayed.
Cause
The system calling fsync() for the specified file system failed.
138
Unable to retrieve database files
Action
Procedure
•
Make sure that the OS is in valid state on the RMC-O application server.
Unable to remount file system <file system name> on
host <host name>
Symptom
An error 3PAR1253: ERROR: Could not re-mount file system <file system name> on host <host
name> is displayed.
Cause
Failed to remount the specified file system.
Action
Procedure
•
Make sure that the OS is in valid state on the RMC-O application server. Manually remount the file system.
Contact customer for further investigation.
Unable to drop one or more ASM snapshot disk groups
Symptom
An error 3PAR1262: ERROR: Could not drop one or more ASM snapshot disk groups is displayed.
Cause
The SQL command to drop one or more ASM snapshot disk groups on the backup server fails.
Action
Procedure
•
Check the log file for more details. Contact customer support for further investigation.
Database <name> may be still running on snapshot
Symptom
An error 3PAR1262: ERROR: Database <name> may be still running on this snapshot is displayed.
Cause
Trying to unmount a snapshot failed as the snapshot is used by a running database.
Unable to remount file system <file system name> on host <host name>
139
Action
Procedure
1. If the cloned database with the same snapshot is no longer used, remove the database using
rmco_removedb before using the rmco_umount command.
Unable to recover clone database
Symptom
An error 3PAR1271: ERROR: Could not recover the clone database is displayed.
Cause
The operation trying to clone a database failed. Normally detailed error messages come before this message.
Action
Procedure
•
Check the error message before this message and check the log file for more details. The snapshot used
for the clone may be corrupted. Try to create a snapshot and clone with the new snapshot. If this problem
persists, contact customer support for further investigation. For dataguard setup, at times,
log_archive_dest_1 of the cloned database needs to be set manually after cloning. And recovery has
to be re-attempted on the cloned database after setting this parameter.
Failed to scan snapshot OS devices
Symptom
An error 3PAR1306: ERROR: Failed to scan snapshot OS devices is displayed.
Cause
During rmco_mount or rmco_umount, the operation trying to find the devices included in a snapshot failed.
Action
Procedure
1. It can be caused by previous failed snapshot rmco_mount or rmco_umount operations, try the command
again, if it still fails, try to reboot the backup server to clean up the stale devices.
The virtual volumes of snapshot %s no longer belong to the
current database virtual volumes
Symptom
An error 3PAR1331: ERROR: The virtual volumes of Virtual Copy %s no longer belong to the current
database virtual volumes is displayed.
Cause
The Virtual Copy is orphaned because its parent volumes have been converted to THIN volumes or FAT
volumes.
140
Unable to recover clone database
Action
Procedure
•
A database snapshot can only be used to promote to its original parent virtual volumes. Since, one or
more virtual volumes of the specified snapshot no longer belong to the current database virtual volumes,
possibly because of FAT-to-THIN or THIN-to-FAT conversion, they cannot be used to promote to the
current database virtual volumes.
Header validation error is encountered from RMAN during
media backups
Symptom
The ISV interfaces display error related to RMAN that contains header validation failures.
Cause
RMAN catalog contains inconsistencies.
Action
Procedure
1. CROSSCHECK and DELETE any expired backups or archivelogs through RMAN.
1. rman target / catalog <rman_user>/<rman_password>@<catalog_service> .
NOTE:
•
•
•
If you have configured RMAN_NBU, use SBT_TAPE channel type and release it once complete.
For example,
ALLOCATE CHANNEL c1 TYPE SBT_TAPE;
SEND 'NB_ORA_CLIENT=<RMC-O backup server>';
If you have configured RMAN_DP, use SBT_TAPE channel type and release it once complete.
For example,
ALLOCATE CHANNEL 'dev_0' TYPE 'sbt_tape'
PARMS 'SBT_LIBRARY=/opt/omni/lib/
libob2oracle8_64bit.so,ENV=(OB2BARTYPE=Oracle8,OB2APPNAME=<DB
NAME>,OB2BARLIST=<Backup Specification Name>)';
Ensure that you perform these steps on the Application server before attempting the next backup
after you notice the failure. If you use only RMAN (not RMAN_DP or RMAN_NBU), ensure that
the RMAN backup pieces are available at the same location on the Application server (to which it
was initially backed up on the backup server). Otherwise, RMAN marks the backup pieces as
expired.
2. RMAN> crosscheck archivelog all; RMAN> delete expired archivelog all; RMAN>
crosscheck backup; RMAN> delete expired backup;
Header validation error is encountered from RMAN during media backups
141
An error Invalid clone instance... occurs during
clone or backup operation
Symptom
An error occurs either during a clone or a backup operation.
Cause
On the backup server, there is a duplicate running instance of the selected database.
Action
Procedure
•
On the backup server, check and shutdown the duplicate instances on all configured ORACLE_HOME
folders.
Mount operation displays an error about duplicate volume
groups or ASM diskgroups
Symptom
Mount operation displays an error about duplicate volume groups or ASM diskgroups.
Cause
On the backup server, there are conflicting volume groups and ASM diskgroups because of their same names
as on the application server.
Action
Procedure
•
Use a different backup server with no name conflicts. Alternatively, remove the conflicting ASM diskgroups
or volume groups temporarily, before attempting a mount operation.
Snapshot creation failed with Recovery Set Snapshot
status must be available or error
Symptom
Count based snapshot policy set on a database attempts to delete the oldest snapshot that is in warning
state.
Cause
The oldest snapshot that is supposed to be automatically deleted is in warning state.
142
An error Invalid clone instance... occurs during clone or backup operation
Action
Procedure
•
Temporarily decrease the snapshot count using Actions > Edit on a selected database from the RMC-O
user interface such that the oldest snapshot is not in
state.
Snapshot operation creates a new snapshot in warning state
Symptom
The Snapshot list displays
for the corresponding snapshot.
Cause
One of the snapshot meta data (CONTROLFILE, PFILE) item retrieval failed.
Action
Procedure
•
Search the client logs on the Application Server to understand the exact Oracle error and perform
necessary actions on the database to rectify the error.
rmco_display -r commands for migrated snapshots
having retention set displays an error
Symptom
CLI displays ValueError for migrated snapshots that have retention or expiration time set.
Cause
RMC-O runtime error.
Action
Procedure
•
See the retention details for the migrated snapshots from the RMC-O user interface.
Scheduled backup operation fails post migration without
any proper Activity status
Symptom
Failure of a scheduled backup post migration.
Cause
The migrated protection policy does not have a valid backup vendor.
Snapshot operation creates a new snapshot in warning state
143
Action
Procedure
•
Verify that the schedule for the backup has an appropriate backup vendor (HPE StoreOnce) and a valid
protection policy assigned to the backup.
Pre-check fails due to policy conflict where user specifies
Max-Snap-Count in RMO and Expiration/Retention time in
RMC-O or vice versa
Symptom
Pre-check fails due to policy conflict when user specifies Max-Snap-Count in RMO and Expiration/
Retention time in RMC-O or vice versa.
Cause
Numeric and time based policies cannot coexist in RMC-O.
Action
Procedure
•
Set same type of policy for RMO and RMC-O or use Enforce RMO Policy option.
Pre-check fails due to policy conflict where user specifies
True for Remove-Oldest-Snapshot in RMO and False in
RMC-O or vice versa
Symptom
Pre-check fails due to policy conflict when user specifies True for Remove-Oldest-Snapshot in RMO and
False in RMC-O or vice versa.
Cause
Precedence to remove a snapshot has to be set explicitly when count based policy is in use.
Action
Procedure
•
Set same value for Remote-Oldest-Snapshot flag both in RMO and RMC-O or use Enforce RMO
Policy option.
Failed to retrieve OS devices during snapshot mount or
unmount operation
Symptom
Mount or unmount operation fails. The GUI activity displays Failed to retrieve OS devices.
144 Pre-check fails due to policy conflict where user specifies Max-Snap-Count in RMO and Expiration/
Retention time in RMC-O or vice versa
Solution 1
Cause
For fibre channel connections, zoning is not properly configured.
Action
Procedure
•
Rectify the zoning issue in the fibre channel switch and verify.
Solution 2
Cause
Device mapper multipath is either improperly configured or the service is not running.
Action
Procedure
•
Rectify and reload the device mapper configuration else restart the device mapper multipath daemon.
Solution 3
Cause
iSCSI daemon is in error state.
Action
Procedure
•
Restart the iSCSI daemon and ensure array connectivity.
Solution 4
Cause
Unmount attempts to remove all the corresponding devices of a mounted snapshot. However, there might be
cases where some old devices are be left out in the /dev/mapper/ folder.
Action
Procedure
1. Run the command multipath -ll and check for devices with faulty status.
2. Remove the devices with faulty status manually before you attempt the next mount operation.
ASCII AND Binary clone with automatic recovery fails on
dataguard setup
Symptom
Clone operation is successful with warnings around automatic recovery. Hence, the clone database remains
in mounted state.
ASCII AND Binary clone with automatic recovery fails on dataguard setup
145
Cause
Unable to set the log_archive_dest_1 parameter on the cloned database.
Action
Procedure
1. Connect to the cloned database and set the log_archive_dest_1 parameter manually based on the
archive log mount point.
2. Perform a recovery on the cloned database to open the database for transactions.
While initiating Catalyst Copy Protect operation, RMC IE
browser crashes
Symptom
Internet Explorer version 11 crashes when trying to perform a Catalyst Copy Protect operation. App Crash
error dialog pops up during the operation.
Cause
Internet Explorer version 11 is used to perform operations in RMC.
Action
Procedure
•
Update Internet Explorer to the latest 11.0 version.
Cloning a database with the automatic recovery option fails
when ORACLE_HOME is configured as a symbolic link
Symptom
Cloning a database with the automatic recovery option fails when ORACLE_HOME is configured as a symbolic
link on a backup server.
Action
Procedure
•
146
Provide a non symbolic link for ORACLE_HOME in the Clone Database dialog.
While initiating Catalyst Copy Protect operation, RMC IE browser crashes
Websites
Website
Link
Contact Hewlett Packard Enterprise Worldwide
www.hpe.com/assistance
Subscription Service/Support Alerts
www.hpe.com/support/e-updates
Software Depot
www.hpe.com/storage/rmc/swdepot/
Customer Self Repair
www.hpe.com/support/selfrepair
Documentation
Hewlett Packard Enterprise Information Library
www.hpe.com/info/enterprise/docs
RMC Documentation on Hewlett Packard
Enterprise Information Library
www.hpe.com/storage/rmc/docs
Hewlett Packard Enterprise Support Center
www.hpe.com/support/hpesc
Single Point of Connectivity Knowledge (SPOCK)
Storage Compatibility Matrix
www.hpe.com/storage/spock/
Storage White Papers
www.hpe.com/storage/whitepapers
Websites
147
Support and other resources
Accessing Hewlett Packard Enterprise Support
•
For live assistance, go to the Contact Hewlett Packard Enterprise Worldwide website:
•
http://www.hpe.com/assistance
To access documentation and support services, go to the Hewlett Packard Enterprise Support Center
website:
http://www.hpe.com/support/hpesc
Information to collect
•
•
•
•
•
•
•
•
Technical support registration number (if applicable)
Product name, model or version, and serial number
Operating system name and version
Firmware version
Error messages
Product-specific reports and logs
Add-on products or components
Third-party products or components
Accessing updates
•
•
Some software products provide a mechanism for accessing software updates through the product
interface. Review your product documentation to identify the recommended software update method.
To download product updates:
Hewlett Packard Enterprise Support Center
•
•
www.hpe.com/support/hpesc
Hewlett Packard Enterprise Support Center: Software downloads
www.hpe.com/support/downloads
Software Depot
www.hpe.com/support/softwaredepot
To subscribe to eNewsletters and alerts:
www.hpe.com/support/e-updates
To view and update your entitlements, and to link your contracts and warranties with your profile, go to the
Hewlett Packard Enterprise Support Center More Information on Access to Support Materials page:
www.hpe.com/support/AccessToSupportMaterials
IMPORTANT:
Access to some updates might require product entitlement when accessed through the Hewlett Packard
Enterprise Support Center. You must have an HPE Passport set up with relevant entitlements.
Customer self repair
Hewlett Packard Enterprise customer self repair (CSR) programs allow you to repair your product. If a CSR
part needs to be replaced, it will be shipped directly to you so that you can install it at your convenience.
148
Support and other resources
Some parts do not qualify for CSR. Your Hewlett Packard Enterprise authorized service provider will
determine whether a repair can be accomplished by CSR.
For more information about CSR, contact your local service provider or go to the CSR website:
http://www.hpe.com/support/selfrepair
Remote support
Remote support is available with supported devices as part of your warranty or contractual support
agreement. It provides intelligent event diagnosis, and automatic, secure submission of hardware event
notifications to Hewlett Packard Enterprise, which will initiate a fast and accurate resolution based on your
product's service level. Hewlett Packard Enterprise strongly recommends that you register your device for
remote support.
If your product includes additional remote support details, use search to locate that information.
Remote support and Proactive Care information
HPE Get Connected
www.hpe.com/services/getconnected
HPE Proactive Care services
www.hpe.com/services/proactivecare
HPE Proactive Care service: Supported products list
www.hpe.com/services/proactivecaresupportedproducts
HPE Proactive Care advanced service: Supported products list
www.hpe.com/services/proactivecareadvancedsupportedproducts
Proactive Care customer information
Proactive Care central
www.hpe.com/services/proactivecarecentral
Proactive Care service activation
www.hpe.com/services/proactivecarecentralgetstarted
Warranty information
To view the warranty for your product, see the Safety and Compliance Information for Server, Storage, Power,
Networking, and Rack Products document, available at the Hewlett Packard Enterprise Support Center:
www.hpe.com/support/Safety-Compliance-EnterpriseProducts
Additional warranty information
HPE ProLiant and x86 Servers and Options
www.hpe.com/support/ProLiantServers-Warranties
HPE Enterprise Servers
www.hpe.com/support/EnterpriseServers-Warranties
HPE Storage Products
www.hpe.com/support/Storage-Warranties
HPE Networking Products
www.hpe.com/support/Networking-Warranties
Remote support
149
Regulatory information
To view the regulatory information for your product, view the Safety and Compliance Information for Server,
Storage, Power, Networking, and Rack Products, available at the Hewlett Packard Enterprise Support Center:
www.hpe.com/support/Safety-Compliance-EnterpriseProducts
Additional regulatory information
Hewlett Packard Enterprise is committed to providing our customers with information about the chemical
substances in our products as needed to comply with legal requirements such as REACH (Regulation EC No
1907/2006 of the European Parliament and the Council). A chemical information report for this product can be
found at:
www.hpe.com/info/reach
For Hewlett Packard Enterprise product environmental and safety information and compliance data, including
RoHS and REACH, see:
www.hpe.com/info/ecodata
For Hewlett Packard Enterprise environmental information, including company programs, product recycling,
and energy efficiency, see:
www.hpe.com/info/environment
Documentation feedback
Hewlett Packard Enterprise is committed to providing documentation that meets your needs. To help us
improve the documentation, send any errors, suggestions, or comments to Documentation Feedback
([email protected]). When submitting your feedback, include the document title, part number, edition,
and publication date located on the front cover of the document. For online help content, include the product
name, product version, help edition, and publication date located on the legal notices page.
150
Regulatory information
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.
Procedure
1.
Create a database for housing the Recovery Catalog. Oracle suggests the following disk space
requirements:
a. System tablespace: 100 MB
b. Temp tablespace: 5 MB
c. Rollback segment: 5 MB
d. Online redo log: 1 MB (each)
e. Recovery Catalog: 10 MB
2.
Create a tablespace for the Recovery Catalog as follows:
$ export ORACLE_SID=<catdb>
$ export ORACLE_HOME=<oracle_home>
$ sqlplus "/as sysdba"
SQL> create tablespace <cat_tbs> datafile '<path/filename>' size 10M;
SQL> exit
3.
Where:
a. <catdb>
is the Oracle Instance ID of the Recovery Catalog.
b. <cat_tbs>
is the Recovery Catalog tablespace name.
c. <path/filename>
4.
is the file path where the datafile is created.
Create a user for the Recovery Catalog as follows:
$ sqlplus "/as sysdba"
SQL> create user <rman_user> identified by <rman_password>
temporary tablespace temp
default tablespace <cat_tbs>
quota unlimited on <cat_tbs>;
SQL> grant connect, resource, recovery_catalog_owner to <rman_user>;
5.
Where:
a. <tbs_name>
is the tablespace name of the Recovery Catalog.
b. <rman_user>
is the user name to be granted access permission to the Recovery Catalog.
c. <rman_password>
is the password for the
Creating an RMAN Recovery Catalog
151
<rman_user>
6.
.
Create the RMAN Recovery Catalog tables as follows:
$ rman catalog <rman_user>/<rman_password>@<catdb>
RMAN> create catalog tablespace <cat_tbs>;
7.
Configure TNS services for the Recovery Catalog database by adding an entry in the $ORACLE_HOME/
network/admin/tnsnames.ora file on the database server and backup server as follows:
<catdb> =
(description =
(address = (protocol = TCP) (host = <cat_host>) (port = 1521))
(connect_data = (server = dedicated) (service_name = <catdb>))
)
8.
9.
Where <cat_host> is the host name of the host where the catalog is created.
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 = <catdb>)
(ORACLE_HOME = <oracle_home>)
(SID_NAME = <catdb>)
)
)
10. Log in as the Oracle owner user and register the database on the database server.
NOTE:
If RMC-O is used to run against an Oracle standby database, you must register the primary
database on the primary database server instead of the standby database.
$ rman target / catalog <rman_user>/<rman_password>@<catdb>
RMAN> register database;
152
Creating an RMAN Recovery Catalog
Setting Up NetBackup Policies for NBU (UserManaged) Backup
RMC-O supports NetBackup (NBU) with or without RMAN. The following sections describe how to set up
NBU policies for NBU backup without RMAN.
RMC-O 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.
RMC-O 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.
NOTE:
This section is intended for the users who are familiar with the Oracle Database and Symantec
NetBackup (NBU). For more information on creating a NetBackup policy, refer to Symantec NetBackup
documentation.
Configuring the NetBackup Policy for Database Backup
For RMC-O to perform backup and restoration correctly, you must use the following guidelines in conjunction
with Symantec NetBackup documentation when configuring an NBU policy:
Backup
Attribute
1. Select the standard type for the policy.
2. Select the cross mount points option.
3. 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 instantly to replace the value
you entered.
Backup
Schedule
1. Create a schedule for full backup.
2. If you wish to perform client-side database backup (initiated from Recovery Manager),
set the backup window to 0.
3. If you also wish to perform server-side database backup (initiated from NBU), specify
the backup window to fit your needs.
Backup Clients
Set the backup client to the host name of the backup server, as the backup process will
actually take place on the backup server.
Configuring the NetBackup Policy for Archive Log Backup
This procedure is to back up the archive logs only. For RMC-O to perform backup and restoration correctly,
you must use the following guidelines in conjunction with Symantec NetBackup documentation when
configuring an NBU policy:
Setting Up NetBackup Policies for NBU (User-Managed) Backup
153
Backup
Attribute
1. Select the standard type for the policy.
2. Select the cross mount points option.
3. 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 instantly to replace the value
you entered.
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.
NOTE:
Incremental backup of archive log using RMAN is not supported.
2. If you wish to perform client-side archive log backup (initiated from Recovery Manager),
set the backup window to 0.
3. If you also wish to perform server-side 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 server, as the backup process will
actually take place on the backup server.
Setting Up NetBackup Configuration Parameters for the
Backup Server
Recovery Manager uses bpstart and bpend scripts as a hook to NetBackup to create snapshot of a
database, then present the database snapshot to the backup server for backup, and to clean up the snapshot
after backup process completes respectively. The BPSTART_TIMEOUT and BPEND_TIMEOUT in the /usr/
openv/netbackup/bp.conf on the backup server must be set to at least 600 seconds (10 minutes) to
allow enough time for Recovery Manager to perform all necessary operations before the actual backup.
For example, to set the BPSTART_TIMEOUT and BPEND_TIMEOUT parameters to 600 seconds (10
minutes), modify the corresponding parameters in /usr/openv/netbackup/bp.conf on the backup
server as follows:
BPSTART_TIMEOUT = 600
BPEND_TIMEOUT = 600
Setting Up NetBackup Configuration Parameters for the
Database Server
If a database is set up for High Availability (HA), then the CLIENT_NAME parameter in the /usr/openv/
netbackup/bp.conf on the database server must be set to the virtual host name of the database server
instead of the physical host name. This allows a backup image to be restored to the actual database server
even if the database has fail-overed to another database server.
For example, to set the CLIENT_NAME parameter to a virtual host name, modify the corresponding
parameter in the /usr/openv/netbackup/bp.conf on the database server as follows:
CLIENT_NAME = <virtual_hostname>
154
Setting Up NetBackup Configuration Parameters for the Backup Server
Setting Up NetBackup Policies for Oracle RMAN
Backup
The following sections describe how to set up NetBackup (NBU) policies for NBU backup with RMAN.
To perform NBU backup with RMAN, you must have Symantec NetBackup for Oracle (NBU Agent for Oracle)
installed on the NBU master server, Symantec NetBackup client for Oracle installed on the database server
and the backup server. Refer to Symantec NetBackup for Oracle for installation and configuration instructions.
In addition, you must create an Oracle RMAN Recovery Catalog and configure Oracle TNS Service and
Listener to allow connections to the Recovery Catalog from the database server and backup servers. The
Recovery Catalog can be created on any server. RMC-O recommends that the Recovery Catalog be created
on the backup server. See Creating an RMAN Recovery Catalog on page 156 for instructions.
When performing NBU backup with RMAN, Recovery Manager supports full, differential, and cumulative
incremental database backup. Recovery Manager also supports full archive log backup (backup only archive
logs).
RMC-O 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.
NOTE:
This section assumes that you are familiar with Oracle Database and Symantec NetBackup (NBU). For
more information on how to create NetBackup policy, refer to Symantec NetBackup for Oracle
documentation.
Configuring the NetBackup Policy for Database Backup with
RMAN
NOTE:
•
•
•
NBU server-side backup (initiated by the NBU scheduler) can now be used when RMC-O is
configured to run as either the root user or Oracle owner. Previously, NBU server-side backup was
only available if RMC-O was configured for the root user.
If RMC-O is configured to be run as an Oracle user and this is an upgrade from previous Recovery
Manager release, the rmora_config command must be run again for each database that is
configured for server-side backup.
Run the script /usr/openv/netbackup/bin/oracle_link for Oracle to connect to the Oracle
library on the database and backup servers to point to the Symantec NetBackup Media Library.
For RMC-O to perform backup and restoration correctly, you must use the following guidelines in conjunction
with Symantec NetBackup documentation when configuring an NBU policy:
Backup Attribute
Select the Oracle type for the policy.
Backup Selections RMC-O will generate the RMAN backup script at the specified location when you create
the configuration file.
Table Continued
Setting Up NetBackup Policies for Oracle RMAN Backup
155
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 client-side 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 server, as the backup process will
actually take place on the backup server.
Configuring the NetBackup Policy for Archive Log Backup
NOTE:
•
•
NBU server-side backup can be used when RMC-O is configured to run as both root user and Oracle
owner.
If RMC-O is configured to run as an Oracle user and this is an upgrade from previous Recovery
Manager for Oracle release, the rmora_config command must be run again for each database
that is configured for server-side backup.
This procedure is to back up archive logs only. For RMC-O to perform backup and restoration correctly, you
must use the following guidelines in conjunction with Symantec NetBackup documentation when configuring
an NBU policy:
Backup Attribute
Select the Oracle type for the policy.
Backup Selections 1. Enter the location of RMAN backup script (//opt/hpe/rmc/oracle/data/
<db_server>.ora.<oracle_sid>/rmora_nbu_archbackup.sh).
2. Recovery Manager will generate the RMAN backup script at the specified location
when you create the configuration file (see below for details).
Recovery Manager will generate the RMAN backup script at the specified location
when you create the configuration file (see RMC-O configuration Files for details).
Backup Schedule
1. Create a schedule for full backup.
2. If you wish to perform client-side archive log backup (initiated from RMC-O), 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 server, as the backup process will
actually take place on the backup server.
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.
Procedure
1.
156
Create a database for housing the Recovery Catalog. Oracle suggests the following disk space
requirements:
a. System tablespace: 100 MB
Configuring the NetBackup Policy for Archive Log Backup
b. Temp tablespace: 5 MB
c. Rollback segment: 5 MB
d. Online redo log: 1 MB (each)
e. Recovery Catalog: 10 MB
2.
Create a tablespace for the Recovery Catalog as follows:
$ export ORACLE_SID=<catdb>
$ export ORACLE_HOME=<oracle_home>
$ sqlplus "/as sysdba"
SQL> create tablespace <cat_tbs> datafile '<path/filename>' size 10M;
SQL> exit
3.
Where:
a. <catdb>
is the Oracle Instance ID of the Recovery Catalog.
b. <cat_tbs>
is the Recovery Catalog tablespace name.
c. <path/filename>
4.
is the file path where the datafile is created.
Create a user for the Recovery Catalog as follows:
$ sqlplus "/as sysdba"
SQL> create user <rman_user> identified by <rman_password>
temporary tablespace temp
default tablespace <cat_tbs>
quota unlimited on <cat_tbs>;
SQL> grant connect, resource, recovery_catalog_owner to <rman_user>;
5.
Where:
a. <tbs_name>
is the tablespace name of the Recovery Catalog.
b. <rman_user>
is the user name to be granted access permission to the Recovery Catalog.
c. <rman_password>
is the password for the
<rman_user>
6.
.
Create the RMAN Recovery Catalog tables as follows:
$ rman catalog <rman_user>/<rman_password>@<catdb>
RMAN> create catalog tablespace <cat_tbs>;
7.
Configure TNS services for the Recovery Catalog database by adding an entry in the $ORACLE_HOME/
network/admin/tnsnames.ora file on the database server and backup server as follows:
Setting Up NetBackup Policies for Oracle RMAN Backup
157
<catdb> =
(description =
(address = (protocol = TCP) (host = <cat_host>) (port = 1521))
(connect_data = (server = dedicated) (service_name = <catdb>))
)
8.
9.
Where <cat_host> is the host name of the host where the catalog is created.
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 = <catdb>)
(ORACLE_HOME = <oracle_home>)
(SID_NAME = <catdb>)
)
)
10. Log in as the Oracle owner user and register the database on the database server.
NOTE:
If RMC-O is used to run against an Oracle standby database, you must register the primary
database on the primary database server instead of the standby database.
$ rman target / catalog <rman_user>/<rman_password>@<catdb>
RMAN> register database;
Configure RMAN Recovery Catalog
RMC-O requires an Oracle RMAN recovery catalog database when using RMAN backup. To create RMAN
Recovery catalog, see Creating an RMAN Recovery Catalog on page 156
When using RMAN backup with HPE Data Protector, if the Oracle release of the recovery catalog database is
11g R2 or later:
•
Ensure that the owner of the recovery catalog is granted the CREATE ANY DIRECTORY and the DROP
ANY DIRECTORY system priviledges.
SQL> grant CREATE ANY DIRECTORY to <recovery_catalog_user> ;
SQL> grant DROP ANY DIRECTORY to <recovery_catalog_user>
•
158
Ensure that the owner of the recovery catalog has SELECT permissions on v_$instance view.
Configure RMAN Recovery Catalog
SQL> grant select on v_$instance to <recovery_catalog_user> ;
Setting Up NetBackup Policies for Oracle RMAN Backup
159
Setting Up HPE Data Protector Backup
The following sections describe how to configure HPE Data Protector to work with RMC-O.
To perform Oracle RMAN with HPE Data Protector backup, you must have HPE Data Protector Oracle Agent
component installed on the Cell Manager, HPE Data Protector client with User Interface and Oracle
Integration components installed on the RMC-O application server and backup server. Refer to HPE Data
Protector document 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 the database server and backup servers. The Recovery Catalog can be created on
any server. RMC-O recommends that the Recovery Catalog be created on the backup server. For more
details, see Creating an RMAN Recovery Catalog on page 156.
When performing Oracle RMAN with HPE Data Protector backup of a database, Recovery Manager supports
full, differential, and cumulative incremental level 1 to level 4 backup. Recovery Manager also supports full
archive log backup (backup only archive logs).
RMC-O requires that you create an HPE Data Protector Oracle backup specification for database backup. If
you wish to perform archive log backup, you must create a separate HPE Data Protector Oracle backup
specification for it.
NOTE:
This section is intended for users familiar with Oracle Database and HPE Data Protector. For more
information on how to create HPE Data Protector Oracle backup specification, refer to HPE Data
Protector documentation.
NOTE:
With HPE Data Protector, RMC-O only supports Oracle RMAN backup. File system backup using HPE
Data Protector is not supported.
Enable RMC-O Feature for HPE Data Protector
To enable RMC-O feature for HPE Data Protector:
1. On HPE Data Protector Cell Manager, add the following parameter to the file /etc/opt/omni/server/
options/global:
Enable3ParBackupToTapeForOracle=1
2. For the change to take effect, restart HPE Data Protector service. To restart the service:
# /opt/omni/sbin/omnisv stop
# /opt/omni/sbin/omnisv start
Configuring Oracle Operating System User Account (Oracle
Owner Account)
The Oracle operating system user is the owner of the Oracle Home. Add the Oracle operating system user
account to the HPE Data Protector admin group. Following is the list of parameters that you must specify
when adding the user to the HPE Data Protector admin group:
•
•
•
160
Group - Admin
Type- UNIX
Name - The user name of the Oracle owner on the database server (for example, Oracle)
Setting Up HPE Data Protector Backup
•
•
Group/Domain - <Any>
Client - <Any>
Figure 12: HPE Data Protector User Configuration
Create HPE Data Protector Oracle backup specification
To create an HPE Data Protector Oracle backup specification, you must use the HPE Data Protector user
interface from Windows machine to connect to the Cell Manager.
NOTE:
The integration options for RMC-O are not available on the HPE Data Protector Java graphical user
interface on the UNIX Cell Manager.
You can create an Oracle backup specification using online, offline, or datafile template.
For online or datafile backup, the database must be online (OPEN) when the backup occurs. For offline
backup, the database must be offline (CLOSED) when the backup occurs.
NOTE:
RMC-O will not automatically shut down the database before performing the backup.
If backup of archive logs is not done, datafile backup is not useful. Perform backup of archive logs
separately.
Create HPE Data Protector Oracle backup specification
161
An HPE Data Protector Oracle backup specification must be created as follows:
•
•
•
•
A backup specification must be an Oracle backup specification, not a file system backup specification.
Select 3PAR_RMO_Online, 3PAR_RMO_Offline, or 3PAR_RMO_Data template for database backup or
3PAR_RMO_Archive template for archive log backup.
Select control file object.
Application:
•
◦ Client: Select the host name of the database server to be configured for backup.
◦ Application database: Select the database to be configured for backup.
User and group/domain:
◦
•
User name: The user name of the Oracle owner (for example, Oracle) of the Oracle Home. This user
must be added to HPE Data Protector admin group. (See Configure Oracle Operating System User
Account (Oracle Owner Account) )
◦ Group/Domain name: The corresponding group name of the Oracle owner.
General Information:
•
◦ Oracle Server home directory: Specify the Oracle Home of the database.
Primary Database:
◦
•
User name: Specify an Oracle user that has SYSDBA priviledge.
– Password: Specify the password of the Oracle user.
– Services: Specify the TNS service name of the Oracle database. For a RAC database, specify all
TNS service names for all database instances separated by comma. The TNS service names must
be preconfigured for the database instances on the RMC-O application server. The same TNS
service names must be preconfigured for the clone database on the backup server.
Recovery Catalog:
◦
◦
◦
•
User name: The RMAN catalog user name.
Password: The password for the RMAN catalog user.
Services: The TNS service name of the catalog database. The TNS service name must be configured
on the RMC-O application server and the backup server.
Backup Specification Option:
◦
Pre-exec:
◦
– Pre-exec: Specifiy DP_pre.<backup_specification_name>.
– On client: The host name of the RMC-O backup server where the pre-exec script will be executed.
Post-exec:
◦
– Post-exec: Specifiy DP_post.<backup_specification_name>.
– On client: The host name of the RMC-O backup server where the post-exec script will be executed.
Ownership:
– User: The user name of the Oracle owner.
– Group: The group name of the Oracle owner.
– System: The host name of the RMC-O backup server.
NOTE:
Specify the name of the backup specification at the end and the name of the backup specification
must match the specified <backup_specification_name>.
•
Application Specific Options:
◦
Backup client: The host name of the backup server where the RMAN backup will actually take place.
Use HPE Data Protector User Interface from a Windows system to access the Cell Manager when creating a
backup specification and to specify the backup server name for the Application Specific Options. Failure to
162
Setting Up HPE Data Protector Backup
specify the backup server name in the Application Specific Options will result in the backup of production
database instead of clone database.
Modify HPE Data Protector RMAN script
After the HPE Data Protector backup specification is saved, modify the RMAN script in the Application
Specific Options as follows:
•
If the
3PAR_RMO_Online
or
3PAR_RMO_Archive
template is selected earlier, change the following lines.
backup
format 'backup_specification <app_name_%s:%t:%p>.dbf
archivelog all;
Change these lines to:
backup
format 'backup_specification <app_name_%s:%t:%p>.dbf
archivelog all skip inaccessible;
OR
backup
format 'backup_specification <app_name_%s:%t:%p>.dbf
archivelog all not backed up 1 times skip inaccessible;
•
If control file object is selected, change the following lines:
backup
format 'backup_specification <app_name_%s:%t:%p>.dbf
current controlfile;
Change these lines to:
Modify HPE Data Protector RMAN script
163
backup
format 'backup_specification <app_name_%s:%t:%p>.dbf
controlfilecopy '$ORACLE_HOME/dbs/backup_ctrl$ORACLE_SID';
NOTE:
The <backup_specification >, <app_name >, $ORACLE_HOME, and $ORACLE_SID must be
replaced with actual values.
Configuring TNS Naming Service on RMC-O Backup Server
To configure TNS naming service on RMC-O Backup Server:
In $ORACLE_HOME/network/admin/tnsnames.ora on the RMC-O Backup Server, check an entry as
follows:
<Network Service Name>=
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = TCP)(HOST = <RMO Backup Server Name
(and NOT the db server name)>)(PORT = 1521))
)
(CONNECT_DATA =
(SERVICE_NAME = <Service Name>)
)
)
164
Configuring TNS Naming Service on RMC-O Backup Server