In this article I will cover:<\/p>\n
- \n
- Multisection Backup Improvements<\/li>\n
- Restoring and Recovering Files Over Network<\/li>\n
- Storage Snapshot Optimization<\/li>\n
- Active Database Duplication Improvements<\/li>\n<\/ul>\n
Multisection Backup Improvements<\/h2>\n
The multisection backup functionality was introduced in Oracle 11g to handle large data file backups. Using this functionality RMAN can break up a large file into sections during the backup and recovery, which can improve the performance of large datafiles backup. You can select the size using the SECTION SIZE keyword and each channel will create separate files within the backup set, and backup the database in parallel. This functionality supports only backup sets in 11g.<\/p>\n
In Oracle 12c, the multisection backup supports incremental backups and image copies, including backup sets (introduced in 11g). \u00a0This functionality can only be used for data files, you cannot use this to backup control files.<\/p>\n
If the SECTION SIZE that you selected is larger than the actual file then RMAN does not use multisection backup. If you specify a small SECTION SIZE that produces more than 256 sections then RMAN increases the SECTION SIZE to a value that results 256 sections.<\/p>\n
The following example creates a multisection backup of the database using image copies.
\nRMAN> BACKUP AS COPY SECTION SIZE 1024M DATABASE;<\/code><\/p>\nThe following example creates multisection incremental level1 backup
\nRMAN> BACKUP INCREMENTAL LEVEL 1 SECTION SIZE 1024M DATABASE;<\/code><\/p>\nTo improve the backup performance, use unused block compression and block change tracking in conjunction with multisection incremental backups.<\/p>\n
Restoring and Recovering Files over Network<\/h2>\n
Using RMAN you can restore and recover a database, datafile, controlfile, tablespace or spfile over the network from a physical standby database. To restore the database over the network, use the
RESTORE\u2026 FROM SERVICE<\/code> command and use theRECOVER\u2026FROM SERVICE<\/code> command to recover the database over the network. TheFROM SERVICE<\/code> clause specifies the service name of the physical standby.<\/p>\nYou can also use multisection, compression and encryption to improve backup and restore performance.<\/p>\n
- \n
- Use
SECTION SIZE<\/code> withRESTORE <\/code>command to perform multisection restore<\/li>\n- Use
SET ENCRYPTION<\/code> clause before theRESTORE<\/code> command to specify the encryption<\/li>\n- Use
USING COMPRESSED BACKUPSET<\/code> clause to compress backup sets<\/li>\n<\/ul>\nThis feature is useful to synchronize primary and standby database.\u00a0 Here are the few scenarios<\/p>\n
- \n
- Roll-forward a physical standby database to sync with the primary database<\/li>\n
- Restore the primary database using physical standby database.<\/li>\n
- Restore physical standby database using the primary database.<\/li>\n<\/ul>\n
In the following example restoring data file over the network from physical standby to primary database<\/p>\n
Connected to primary database implicitly
\nRMAN> CONNECT TARGET \/<\/code><\/p>\nBackup sets encrypted using AES128 encryption algorithm
\nRMAN> SET ENCRYPTION ALGORITHM 'AES128';<\/code><\/p>\nRestoring the datafile on the primary using datafile on physical database with service \u201cstandby_db\u201d
\nRMAN> RESTORE DATAFILE '\/db1\/oradata\/users.dbf' FROM SERVICE standby_db SECTION SIZE 1024M;<\/code><\/p>\nStorage Snapshot Optimization<\/h2>\n
This new feature enables you to take a storage snapshot of your database using third-party technologies without keeping the database in BACKUP mode. When you need to recover, you can use point in time of the snapshot. You can roll forward by using the database archive logs, and use this snapshot feature to recover part or all of the database.<\/p>\n
The best practice is to use different storage location to keep snapshot than the one where the database currently running.<\/p>\n
In order to backup your Oracle database using storage snapshot optimization, the third-party snapshot technologies must meet the following requirements:<\/p>\n
- \n
- The snapshot preserves the write order for each file.<\/li>\n
- The database is crash consistent during the snapshot.<\/li>\n
- The snapshot technology stores the time at which the snapshot is completed.<\/li>\n<\/ul>\n
If third-party snapshot technology vendor cannot guarantee compliance with above requirements then you must keep the database in BACKUP mode to take the snapshot.<\/p>\n
Follow these steps to keep the database in BACKUP mode and take snapshot<\/p>\n
- \n
SQL> ALTER DATABASE BEGIN BACKUP<\/code><\/li>\n- Take Snapshot using third-part technologies<\/li>\n
SQL> ALTER DATABASE END BACKUP<\/code><\/li>\n<\/ol>\nUse
RECOVER\u2026SNAPSHOT TIME<\/code> command to recover the database in one step from RMAN or SQL*Plus. You can recover the database to a point-in-time or current time after the snapshot was taken. When performing point-in-time make sure that the recovery time cannot be earlier than the snapshot time.<\/p>\nTo recover database completely use below command
\nRECOVER DATABASE;<\/code><\/p>\nTo recover database using particular snapshot use below command
\nRECOVER DATABASE UNTIL TIME \u201810\/10\/2014 10:00:00\u2019 SNAPSHOT TIME \u201810\/10\/2014 09:00:00\u2019<\/code><\/p>\nIn this example database will be recovered until \u201810\/10\/2014 10:00:00\u2019 using snapshot taken on \u201810\/10\/2014 09:00:00\u2019<\/p>\n
To perform partial recovery using archived redo logs use below command
\nRECOVER DATABASE UNTIL CANCEL SNAPSHOT TIME \u201810\/10\/2014 09:00:00\u2019<\/code><\/p>\nNote that
UNTIL CANCEL<\/code> clause is valid only in SQL*Plus<\/p>\nIf there are any structural changes during the snapshot then the snapshots are unusable.\u00a0 Do not perform the operations such as O
NLINE, OFFLINE, DROP, RENAME, ADD, READONLY<\/code> andSHRINK<\/code> on data files and table spaces.<\/p>\nActive Database Duplication Improvements<\/h2>\n
Active Database duplication was introduced in Oracle Database 11g. Using this feature you can create clone or standby database by copying the data files and archive logs using the TARGET (Source) database channels over the network to clone AUXILIARY database. As you are using the TARGET database channels you will see processing load on the TARGET instance. In this method no backups of the TARGET database are required.<\/p>\n
![\"rman2pic1\"](\"https:\/\/www.red-gate.com\/simple-talk\/wp-content\/uploads\/oracle\/2014\/12\/rman2pic1.png\")
<\/p>\nIn Oracle 11g, Performance typically gated by network bandwidth<\/p>\n<\/div>\n
In Oracle 12c, you can perform Active Database duplication using the backup sets. You can allocate sufficient AUXILIARY channels to connect TARGET database and retrieve the backup\u2019s sets over the network, this reduced the load on the TARGET (source) database. You can use unused block compression to reduce the size of the backups transported over the network.<\/p>\n
While performing the Active database duplication you can also encrypt backups and multisection backups.<\/p>\n
![\"rman2pic2\"](\"https:\/\/www.red-gate.com\/simple-talk\/wp-content\/uploads\/oracle\/2014\/12\/rman2pic2.png\")
<\/p>\nIn Oracle 12c, it helps to reduce network consumption and improve performance<\/p>\n<\/div>\n
As you see in below duplication example, it is using AUXILIARY channel.<\/p>\n
oracle@gc12c ~]$ rman target sys\/password@TESTDB auxiliary sys\/password@DUPDB \r\nRecovery Manager: Release 12.1.0.1.0 - Production on Wed Oct 15 10:26:58 2014 \r\nCopyright (c) 1982, 2013, Oracle and\/or its affiliates.\u00a0 All rights reserved. \r\n\r\nconnected to target database: TESTDB (DBID=488428308732) \r\nconnected to auxiliary database: DUPDB (not mounted) \r\n\r\nRMAN> run { \r\n2> duplicate target database to DUPDB from active database \r\n3>\u00a0\u00a0 db_file_name_convert('TESTDB','DUPDB'); \r\n4> } \r\n\r\nStarting Duplicate Db at 15-OCT-2014 10:27:11 \r\nusing target database control file instead of recovery catalog \r\nallocated channel: ORA_AUX_DISK_1 \r\nchannel ORA_AUX_DISK_1: SID=20 device type=DISK<\/b> \r\ncurrent log archived \u2026\u2026\u2026\u2026\u2026\u2026.<\/pre>\nNote that if the numbers of AUXILIARY channels allocated are less than target channels, or no auxiliary channels are allocated, then RMAN uses image copies to perform active database duplication. In order to RMAN use backup sets you need to establish connection to target database using a net service name and one of the following conditions must be satisfied.<\/p>\n
- \n
- The number of AUXILIARY channels should be equal or greater than TARGET channels<\/li>\n
- The DUPLICATION \u2026FROM ACTIVE DATABASE should contain either USING BACKUPSET, USING COMPRESSED BACKUPSET or SECTION SIZE clause<\/li>\n<\/ul>\n
Conclusion<\/h2>\n
Oracle Database 12c offers new enhancements and additions in Recovery Manager (RMAN). The above listed features will help user to backup the database in parallel, improve the backup performance, reduce the load on the source database during the active duplication, quickly create point-in-time copies using storage snapshot and easily synchronize primary and standby databases over the network. Take the advantage of new features for efficient backup and recovery.<\/p>\n
<\/p>\n","protected":false},"excerpt":{"rendered":"
Oracle Database 12c has new enhancements and additions to Recovery Manager (RMAN).\u00a0 The Recovery Manager continues to enhance and extend the reliability, efficiency, and availability of Oracle Database Backup and Recovery. In this article series, I will be explaining the new features and how it will help the Oracle community. See new features covered in Part 1 \u2013 Oracle Databas…<\/p>\n","protected":false},"author":316203,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[143533],"tags":[5564,4598,48492],"coauthors":[],"class_list":["post-73180","post","type-post","status-publish","format-standard","hentry","category-oracle-databases","tag-backups","tag-recovery","tag-rman"],"acf":[],"_links":{"self":[{"href":"https:\/\/www.red-gate.com\/simple-talk\/wp-json\/wp\/v2\/posts\/73180","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.red-gate.com\/simple-talk\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.red-gate.com\/simple-talk\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.red-gate.com\/simple-talk\/wp-json\/wp\/v2\/users\/316203"}],"replies":[{"embeddable":true,"href":"https:\/\/www.red-gate.com\/simple-talk\/wp-json\/wp\/v2\/comments?post=73180"}],"version-history":[{"count":1,"href":"https:\/\/www.red-gate.com\/simple-talk\/wp-json\/wp\/v2\/posts\/73180\/revisions"}],"predecessor-version":[{"id":91669,"href":"https:\/\/www.red-gate.com\/simple-talk\/wp-json\/wp\/v2\/posts\/73180\/revisions\/91669"}],"wp:attachment":[{"href":"https:\/\/www.red-gate.com\/simple-talk\/wp-json\/wp\/v2\/media?parent=73180"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.red-gate.com\/simple-talk\/wp-json\/wp\/v2\/categories?post=73180"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.red-gate.com\/simple-talk\/wp-json\/wp\/v2\/tags?post=73180"},{"taxonomy":"author","embeddable":true,"href":"https:\/\/www.red-gate.com\/simple-talk\/wp-json\/wp\/v2\/coauthors?post=73180"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}
- Use
- Use