prepares the environment to start the restore, and issues the RMAN restore command.
RMAN checks the recovery catalog (if one is used) or the control file to gather the
information about the Oracle backup objects. It also contacts the Oracle Server
processes, which initialize the restore through MML. MML establishes a connection
with the Restore Session Manager and passes along the information about which
objects and object versions are needed.
The Restore Session Manager checks the IDB to find the appropriate devices and
media, starts the General Media Agent, establishes a connection between MML and
the General Media Agent, and then monitors the restore and writes messages and
information regarding the restore to the IDB.
The General Media Agent reads the data from the backup devices and sends it to
the Oracle Server processes through MML. The Oracle Server Processes write the
data to the disks.
The concept of Oracle integration, data and the control flow are shown in
Figure
2
on page 38, and the related terms are explained in the following table.
Figure 2 Data Protector Oracle integration concept
Oracle 10g/11g database files can also be part of ASM configuration.
Data Protector Oracle ZDB integration
38
Summary of Contents for Data Protector A.06.11
Page 18: ...Publication history 18 ...
Page 83: ...Figure 21 EVA backup options Click Next Zero downtime backup integration guide 83 ...
Page 197: ...Figure 49 XP backup options Zero downtime backup integration guide 197 ...
Page 198: ...Figure 50 VA backup options Data Protector SAP R 3 ZDB integration 198 ...
Page 199: ...Figure 51 EVA backup options Click Next Zero downtime backup integration guide 199 ...
Page 242: ...Data Protector SAP R 3 ZDB integration 242 ...
Page 315: ...1 In the Context List select Restore Zero downtime backup integration guide 315 ...
Page 328: ...Data Protector Microsoft Exchange Server ZDB integration 328 ...
Page 432: ...Appendix 432 ...
Page 490: ...Glossary 490 ...