Оценок - 0, средний балл: 0
(
)
)
|
К этому устройству также есть другие инструкции:
Фрагмент инструкции
Introduction
This document describes how to perform Oracle Backup Set ZDB tracked for Instant Recovery, and
how to perform Instant Recovery of Automatic Storage Management (ASM)-based databases.
Automatic Storage Management (ASM)
Automatic Storage Management is an integrated file system and volume manager built to handle
Oracle database files. It is not a general purpose file system or clustered file system, so it cannot be
used for binaries, trace files and other non-Oracle files. The primary function of ASM is to eliminate
the complexity associated with managing data and disks, while also providing striping and mirroring
capabilities to optimize performance.
Instant Recovery support for databases that use Oracle
ASM
Instant Recovery of ASM-based databases is now supported in HP Data Protector A.06.00 through
the Site Specific Patch SSPUX600_074. This feature requires replicas created by Oracle Backup Set
ZDB that is tracked for Instant Recovery.
The procedure for creating backup specifications and running restore sessions is the same for ASM-
based databases and for the Oracle databases that do not use ASM.
Oracle Backup Set ZDB, tracked for Instant Recovery for ASM-based databases, requires atomic
split to be enabled during the backup session.
NOTE: Atomic split must be enabled during both disk and disk+tape sessions. Restore or Instant
Recovery sessions do not need atomic split.
For more details on Oracle Backup Set ZDB, See the HP Data Protector 6.0 ZDB
Integration Guide.
See Enabling Atomic Split section for details on omnirc variable required to enable atomic split
and the Instant Recovery procedures for ASM-based databases section for Instant Recovery
procedure of ASM-based databases in this document.
Guidelines for creating ASM disk groups and ASM-based
databases
Oracle Backup Set ZDB, tracked for Instant Recovery for ASM-based databases, requires an atomic
split of the disks that comprise ASM disk groups. Hence al the XP disks that are required to be split
atomical y must be configured with same CT group IDs. For the atomic split to work properly, each
XP disk (LUN ) used for ASM disk groups, must consist of a single LDEV from the array, which
means that the LUN must be of the type OPEN-3, OPEN-9 or OPEN-V, but not of the type OPEN-
x*n.
A CT group ID of 0 is currently not supported.
An ASM disk group must only be configured for a single database.
All ASM disk groups must be configured with external redundancy mirroring.
The autoextend feature must not be enabled for tablespaces and datafiles of an ASM-based
database during backup that is tracked for Instant Recovery and Instant Recovery of that database.
...