HP 3PAR Application Software Suite for Oracle Licenses - Manual (Page 9)

To ensure that the database is running in automatic archive log mode, use SQL*Plus utility to ensure
the Database log mode is Archive Mode and that Automatic archival is Enabled, as
in the following example:
$ sqlplus "/as sysdba"
SQL*Plus: Release 9.2.0.1.0 - Production on Wed Nov 14 13:59:13 2007
Copyright (c) 1982, 2002, Oracle Corporation. All rights reserved.
Connected to:
Oracle9i Enterprise Edition Release 9.2.0.1.0 - 64bit Production
With the Partitioning, Real Application Clusters, OLAP and Oracle Data Mining options
JServer Release 9.2.0.1.0 - Production
SQL> archive log list
Database log mode Archive Mode
Automatic archival Enabled
Archive destination /rac9i_db/rac9i_arch2
Oldest online log sequence 764
Next log sequence to archive 764
Current log sequence 765
Oracle standby databases are supported. An Oracle standby database is a synchronized copy
of the production database. The following are required for standby database support:
•
Only Oracle 10g and 11g are supported.
•
A standby database must be a physical database. Logical or snapshot standby databases
are not supported.
•
If using RMAN backup, the primary database (not standby) must be registered with Oracle
Recovery Catalog.
•
A snapshot of a standby database can be used to promote standby database volumes, but
cannot be used to promote primary database volumes (even though a backup of the snapshot
can be used to restore the primary database).
•
Oracle parameter and control files are not compatible between the standby and primary
databases. They cannot be used to restore the primary database unless Oracle RMAN (11g)
is used. The Oracle parameter and control files of the primary database must be backed up
manually outside of Recovery Manager for Oracle.
Interacting with Symantec NetBackup and Oracle RMAN
HP 3PAR Recovery Manager for Oracle integrates HP 3PAR Virtual Copy with Symantec NetBackup
(NBU) and Oracle RMAN to dramatically reduce the performance impact on the database server,
as well as to minimize database down time during backup. Instead of a traditional backup where
the database is backed up directly on the production server, Recovery Manager for Oracle creates
a Virtual Copy (snapshot) of the database, imports it to a secondary host (backup server), and
then performs the backup of the Virtual Copy on the backup server.
Recovery Manager for Oracle provides two ways to perform backup and restoration: NBU
(user-managed) and Oracle RMAN.
NOTE: For an ASM managed database, Oracle RMAN backup is the only supported backup
method.
For NBU (user-managed) backup and restoration, Recovery Manager for Oracle interacts directly
with NBU to trigger the backup/restore process. Recovery Manager for Oracle requires that the
NBU client must be installed on the primary host and the backup server.
For Oracle RMAN backup, Recovery Manager for Oracle supports backup to tape and backup
to local disk. If Recovery Manager is configured to perform backup to local disk, Recovery Manager
for Oracle interacts with Oracle RMAN to trigger the backup process. If Recovery Manager for
Interacting with Symantec NetBackup and Oracle RMAN 9