Oracle11gNew enhanced features using RMAN

Backup and recovery operations are a key part. Even if there are various levels of potential faults and errors, they can ensure the availability of information to the Organization. Use OracleDatabas

Backup and recovery operations are a key part. Even if there are various levels of potential faults and errors, they can ensure the availability of information to the Organization. Use Oracle Databas

Description of the new and enhanced RMAN functions in Oracle Database 11g

• Configure an archiving log deletion policy

• Use Oracle to copy active databases (No backups)

• Backing up large files in the form of multiple parts

• Create an archive backup for long-term storage

• Manage and restore directories, such as merging multiple directory versions

• Describe the usage of Virtual Private Directories

RMAN: New Feature

• The following improvements improve performance:

-Fast Incremental backup on the physical backup database

-Improved Block Media recovery

New Features of RMAN

Backup and recovery operations are a key part. Even if there are various levels of potential faults and errors, they can ensure the availability of information to the Organization. With Oracle Database 11 GB, the Recovery Manager (RMAN) Enhancement provides the following advantages:

Fast Incremental backup on physical backup database

You can enable block change tracking on a physical standby DATABASE (using an existing alter database enable/disable block change trackingsql Statement ). Then RMAN will be in standby

Tracks changed blocks during managed recovery. In this way, you can unmount the block tracking of the standby database, and use the change tracking files available on the primary database for the same fast Incremental backup. This feature allows you to perform Incremental backup at a faster speed than the previous version in a physical backup database.

Improved Block Media recovery performance

You can use the RECOVER command (previous BLOCKRECOVER command) to restore a single data block. If flash back event records are enabled and the event records contain old and intact blocks, RMAN can use these blocks to speed up Block Media recovery.

Oracle Database 11g: Administrator-oriented New features 10-4

Copyright©2007, Oracle. All rights reserved. 10-4

Optimized backup

• Use the ZLIB algorithm to accelerate Compression

Configure compression algorithm to zlib;

• Enhanced block Damage Detection and enhanced protection

Saves backup space while accelerating Compression

You can use the CONFIGURE command to select the BZIP2 or ZLIB Compression Algorithm for RMAN backup. The new ZLIB backup compression algorithm is 40% faster than the previous BZIP2 algorithm. The actual data warehouse database of a large pharmaceutical company uses this

The compression ratio is 2.0: 1 when the BZIP2 algorithm is used, and the compression ratio is 1.68: 1 when the ZLIB algorithm is used. Use the following command to configure the backup compression algorithm (replace alg_name with BZIP2 or ZLIB ):

Configure compression algorithm to 'Alg _ name ';

Enhanced block Damage Detection

In addition to the block corruption detected by RMAN, the Oracle Database 11g also records the block corruption of the activity in the V $ database_block_partition uption view. After detecting or repairing block damage,

Oracle DB automatically updates this view. The VALIDATE command is enhanced with many new options (such as VALIDATE... BLOCK and validate database.

Optimized backup

• Optimized Backup recovery automatically reduces backup time and storage space

• Flexible use of VSS-supported software

-Allows databases to participate in snapshots coordinated by VSS-compliant Backup management tools and storage products.

-Restore the database automatically by using RMAN Based on the snapshot

Optimized Backup Recovery

No backup is required for restoring data that is not required by transaction processing (for example, for processing committed transactions. The advantage is that the backup time and storage space are reduced in general because it does not back up the restored data applied to committed transactions. This optimization is automatically enabled.

Integration with applications supporting VSS

Volume copying service (VSS) is an infrastructure on Windows. Oracle VSS write process and support for VSS

Optimized backup

• Simplified archive log management in Multi-Component Environments

• Availability is improved by transferring backup failures to optional targets

Simplified archive log management in a multi-component Environment

This feature simplifies the management of archive logs in a multi-component environment. It also improves the availability of archiving logs when archive logs are lost or cannot be accessed in the quick recovery area.

Enhanced configuration of deletion policies

Only when necessary components (such as Data Guard, stream, and flash back to database) do not need to archive and redo logs can they be deleted.

In the Data Guard environment, all standby targets need to be considered before the archived logs are identified as deleted (not just required targets ). This configuration is specified using the configure archivelog deletion policy to applied on standby command.

After the archive log deletion policy is configured, this configuration will be applied to all archiving targets, including the quick recovery area. Fast Recovery

For more details, please continue to read the highlights on the next page:

Recommended reading:

Basic Oracle tutorial-copying a database through RMAN

Reference for RMAN backup policy formulation

RMAN backup learning notes

Oracle Database Backup encryption RMAN Encryption