Enabling Instant Recovery In An Asm Configuration For The Xp Array; Cluster-Aware Clients; Linking Oracle Server With The Data Protector Mml - HP Data Protector A.06.11 Integration Manual

RMAN> exit
Recovery Manager completed.

Enabling instant recovery in an ASM configuration for the XP array

On UNIX systems, the ASM configuration on XP array can be supported for instant
recovery, provided that support for the atomic split configuration on XP array is
enabled. To support ASM for instant recovery, the following prerequisites must be
met:
• The ASM files you will use for backup must be located on raw disks. They should
not reside on raw logical volumes.
• The XP array which you will use for backing up the ASM files must support the
atomic split configuration.
• The XP mirror groups must be created in the group mode with a specific CT number
assigned. Note that the CT number 0 is not supported.
• The Data Protector omnirc variable SSEA_ATOMIC_SPLIT must be enabled
(set to 1). Note that by default the variable is disabled (set to 0).

Cluster-aware clients

In cluster environment, if you intend to use the Data Protector CLI, set the Data Protector
environment variable OB2BARHOSTNAME to the virtual server name. Set the variable
on the Oracle Server system as follows:
Windows: set OB2BARHOSTNAME=virtual_server_name
UNIX: export OB2BARHOSTNAME=virtual_server_name
HP-UX with RAC: To enable instant recovery, create an MC/ServiceGuard package
containing only the virtual IP and the virtual hostname parameters and distribute it
among the RAC nodes.

Linking Oracle Server with the Data Protector MML

To use the Data Protector Oracle integration, the Oracle Server software needs to
be linked with the Data Protector Oracle integration Media Management Library
(MML) on every client on which an Oracle instance is running.
You do not need to link Oracle Server with the Data Protector MML manually. When
you start backups or restores using the Data Protector GUI or CLI, Data Protector
automatically links Oracle Server with the correct platform–specific Data Protector
MML. However, for testing purposes, you can override this automatic selection. You
can manually specify which platform–specific Data Protector MML should be used
56 Data Protector Oracle ZDB integration