Monday, February 14, 2011

RMAN and hp-Data Protector Integration


RMAN and hp-Data Protector Integration

Data Protector Basics:


HP OpenView Storage Data Protector is a backup solution that provides reliable data protection and high accessibility for your fast growing business data. Data Protector offers comprehensive backup and restore functionality specifically tailored for enterprise-wide and distributed environments.



HP OpenView Storage Data Protector is a backup solution that provides reliable data protection and high accessibility for your fast growing business data. Data Protector offers comprehensive backup and restore functionality specifically tailored for enterprise-wide and distributed environments.

Scalable and Highly Flexible Architecture
Easy Central Administration
High Performance Backup
Supporting Mixed Environments
Easy Installation for Mixed Environments
High Availability Support
Monitoring, Reporting and Notification
Integration with Online Database Applications
Integration with Other Products



The Data Protector cell, is a network environment that has a Cell Manager, client systems, and devices.
The Cell Manager is the central control point where Data Protector software is installed.
After installing Data Protector software, you can add systems to be backed up.
These systems become Data Protector client systems that are part of the cell.
When Data Protector backs up files, it saves them to media in backup devices.

The Data Protector internal database (IDB) keeps track of the files you back up so that you can browse and easily recover the entire system or single files.

Client systems with connected backup devices must have a Data Protector Media Agent (MA) installed. Such client systems are also called Drive Servers.
A backup device can be connected to any system and not only to the Cell Manager.
A Media Agent reads or writes data from or to media in the device and sends or receives data from the Disk Agent.
 Manager-of-Managers
Data Protector provides the MoM for management of large environments with multiple cells. The MoM allows you to group multiple cells into a larger unit, which can be managed from a single point.
New cells can be added, or existing cells can be split. MoM provides:
Centralized licensing repository—This optional feature enables simplified licensing
management.
Centralized Media Management Database (CMMDB)—The CMMDB allows you to share
devices and media across several cells in a MoM environment. Using CMMDB, devices in one cell are accessible to other cells that use the CMMDB.
• With the CMMDB, you can share high-end devices between cells in the multi-cell environment. One cell can control the robotics, serving several devices that are connected to systems in different cells.
Even the Disk Agent to Media Agent data path can go across cell boundaries.
Enterprise Backup Solution with HP Data Protector implementation guide 11
Enterprise reporting—The MoM can generate reports on a single-cell basis as well as for the entire enterprise environment.


DP and RMAN Integration:

The interface from the Oracle server processes to Data Protector is provided by the Data Protector Oracle integration Media Management Library (MML), which is a set of routines that allows the reading and writing of data to General Media Agents.
Besides handling direct interaction with the media devices, Data Protector provides scheduling, media management, network backups,monitoring, and interactive backup.
Using this integration, you can perform the Oracle full and incremental (up to incremental level 4) backup types.
With Oracle full and incremental level 0 backups all data blocks per datafile are backed up. With Oracle incremental backup (level 1 or higher), only the data blocks that have changed since a previous backup are backed up.
The difference between a full backup and an incremental level 0 backup is that the incremental 0 is a base for subsequent incremental backups.
Therefore, Data Protector always performs Oracle incremental 0 when you select the full backup type in a backup specification.
The full backup type is not related to the number of datafiles included in the backup, and can therefore be performed per single datafile. The data being backed up, regardless of the backup type (full or incremental), is selected and controlled by Oracle.
Oracle incremental backups can be differential or cumulative. By default, Data Protector performs Oracle differential incremental backups. By changing the default RMAN script created by Data
Protector, you can specify also a cumulative backup.
NOTE Regardless of the Oracle backup type specified, Data Protector always marks the Oracle backups as full in the Data Protector database, since the Data Protector incremental backup concept is different from the Oracle incremental backup concept.
A backup that includes all datafiles and current control file that belong to an Oracle Server instance is known as a whole database backup.


Backup Flow:
1. A Data Protector scheduled or interactive backup is triggered by the Data Protector Backup Session Manager, which reads the backup specification and starts the ob2rman.pl command on the Oracle Server under a specific user.
This user must be defined as the owner of the Data Protector Oracle backup specification.
2. Further on, ob2rman.pl prepares the environment to start the backup, and issues the RMAN backup command. RMAN instructs the Oracle Server processes to perform the specified command.
3. The Oracle Server processes initialize the backup through MML, which establishes a connection to the Data Protector Backup Session Manager.
4. The Backup Session Manager starts the General Media Agent, sets up a connection between MML and the General Media Agent, and then monitors the backup process.
5. The Oracle Server processes read the data from the disks and send it to the backup devices through MML and the General Media Agent.
6. RMAN writes information regarding the backup either to the recovery catalog (if one is used) or to the control file of the Oracle target database.
 7. Messages from the backup session are sent to the Backup Session Manager, which writes messages and information regarding the backup session to the IDB.
8. The Data Protector General Media Agent writes data to the backup devices

Restore Flow:

A restore session can be started using:
• Data Protector GUI
• RMAN CLI
• Oracle Enterprise Manager GUI
You must specify which objects are to be restored.
  1. A restore from the Data Protector user interface is triggered by the Data Protector Restore Session Manager, which starts the ob2rman.pl command. Ob2rman.pl prepares the environment to start the restore, and issues the RMAN restore command.
  2. 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.
  3. MML establishes a connection with the Restore Session Manager and passes along the information about which objects and object versions are needed.
4.   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.



No comments:

Post a Comment