Description of the new and enhanced RMAN functions in Oracle Database 11g
• Configure an archiving log deletion policy • Use the Oracle network to copy active databases (No backups) • backing up large files in multiple parts • Creating archive backups for long-term storage • Managing and restoring directories, such as merging multiple directory versions • describing the usage of Virtual Private Directories
• The following improvements have improved performance:-fast Incremental backup on physical backup databases-improved Block Media recovery of new features of RMAN backup and recovery operations is a key part, it can ensure the availability of information to the Organization even if there are various levels of potential faults and errors. With Oracle Database 11 GB, the Recovery Manager (RMAN) Enhancement provides the following advantages: fast Incremental backup on the physical standby DATABASE enables block change tracking on the physical standby DATABASE (using the existing alter database enable/disable block change trackingsql Statement ). Then RMAN tracks the changed Blocks During the standby managed recovery. In this way, the block tracking of the standby database can be uninstalled, and the same fast Incremental Backup can use the change tracking files available on the primary database. This feature allows you to perform Incremental backup at a faster speed than the previous version in a physical backup database. You can use the RECOVER command (previous BLOCKRECOVER command) to restore a single data block for improved Block Media recovery performance. 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 All Rights Reserved©2007, Oracle. All rights reserved. 10-4
• Use the zlib algorithm to accelerate the COMPRESSION speed configure compression algorithm to zlib; • Enhance the block damage detection function, therefore, the protection function is enhanced to retain the backup space while accelerating the compression speed. You can use the CONFIGURE command to select the BZIP2 or ZLIB Compression Algorithm for the 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 these two algorithms: the compression ratio is 2.0: 1 when the BZIP2 algorithm is used, and the compression ratio is 1.68 when the ZLIB algorithm is used: 1. Use the following command to configure the backup compression algorithm (replace alg_name with BZIP2 or ZLIB): configure compression algorithm to 'Alg _ name '; enhanced the block damage detection function. In addition to the block Damage detected by RMAN, the Oracle Database 11g also records the active block damage in the V $ database_block_partition uption view. Oracle DB automatically updates this view after blocks are detected or repaired. The VALIDATE command is enhanced with many new options (such as VALIDATE... BLOCK and validate database.
• Optimized Backup recovery automatically reduces backup time and storage space • flexible use of VSS-allows databases to participate in snapshots coordinated by VSS-compliant Backup management tools and storage products-using RMAN automatic Restoration Based on Snapshot recovery database-optimized restoration backup restores unnecessary data for transaction processing recovery (for example, for committed transactions), do not back up. 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. Integrated with applications that support VSS, the Volume Shadow replication service (VSS) is an infrastructure on Windows. The Oracle VSS write process is integrated with applications that support VSS. Therefore, you can use the software and storage system supporting VSS to back up and restore Oracle DB. The primary advantage is that you can create a Shadow Copy of the opened database. You can also use the backup incremental level 1... from scn command in RMAN to generate an incremental backup of the VSS Shadow Copy.
• Simplified archive log management in a multi-component environment • Improved availability by transferring backup failures to optional targets simplifies archive log management in a multi-component environment this feature simplifies archiving logs in a multi-component Environment management. It also improves the availability of archiving logs when archive logs are lost or cannot be accessed in the quick recovery area. Enhanced deletion policy configuration can be deleted only when any necessary components (such as Data Guard, stream, and Flash back database) do not need to archive and redo logs. 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. Like the quick recovery area, BACKUP... delete input and DELETE... ARCHIVELOG both use this configuration. During backup and recovery, if the archived redo logs in the quick recovery area are inaccessible or damaged, RMAN may fail over to other archived redo log targets.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
