Oracle Incremental Merge protection with Oracle RMAN agent
Oracle Incremental Merge backups enable you to create a full image copy backup of a database every day for the cost of an incremental backup, resulting in faster backups with better deduplication and faster restores.
Oracle Incremental Merge protection is implemented through the
PowerProtect Data Manager UI and the integrated Oracle RMAN agent workflows.
PowerProtect Data Manager 19.13 and later supports the Oracle Incremental Merge backups and restores on Linux for both stand-alone and Oracle RAC systems.
PowerProtect Data Manager 19.14 and later supports the Data Guard federated mode with the Oracle Incremental Merge operations.
The first Oracle Incremental Merge backup of a database to a DD storage unit is a full image copy backup, which begins the cycle of incremental updates. Each subsequent backup is a level 1 incremental backup of the database. The changed blocks are applied to the full backup to create an up-to-date synthetic full backup. The synthetic full backup is easier to restore as an image copy than a traditional RMAN backup. Oracle Incremental Merge enables "forever incremental" functionality through the creation of the synthetic full backups.
The Oracle Incremental Merge operations support both DD BoostFS mount-based backups and restores and NFS mount-based backups and restores. The BoostFS mount-based operations require the installation of DD BoostFS on the application host, to provide a standard file system mount point to the application. With direct access to the BoostFS mount point, the application can leverage the storage and network efficiencies of the DD Boost protocol for backups and restores.
NOTE:In the Oracle Incremental Merge configuration in
PowerProtect Data Manager, you can use the
Set Protocol option to set the BoostFS or NFS protocol for the Oracle Incremental Merge backups. If you change the protocol setting from NFS to BoostFS, you must run a
Set Lockbox operation for the applicable self-service protection policy.
You can perform Oracle Incremental Merge backups of both pfile-based and spfile-based Oracle databases. Oracle Incremental Merge supports scheduled backups through the BoostFS or NSF protocol. You can perform both centralized and self-service Oracle Incremental Merge backups, based on the Oracle Incremental backup policy that you configure in the
PowerProtect Data Manager UI.
NOTE:You can use the
ddutil command with appropriate options to list the Oracle Incremental Merge backups. In the latest version of the
PowerProtect Oracle RMAN Agent Administration Guide (for the stand-alone Oracle RMAN agent), refer to the "Oracle Incremental Merge operations" section and the topic about using the
ddutil command to list the backups.
Oracle Incremental Merge supports the following operations:
Full backups—A full backup creates a full copy of the database plus archive logs. The full copy is used with an incremental backup to create a synthetic full backup. Backups are protected by a DD retention lock
Synthetic full backups—An incremental backup backs up the changed data blocks, which are applied to the previous full backup to create a new synthetic full backup. This synthetic full backup is stored in a new location and then cataloged and protected by a DD retention lock.
NOTE:When the synthetic full backups are part of an Oracle Incremental Merge protection policy, ensure that you run a manual full backup in the following cases:
You move an asset from one policy to a second policy, where the second policy has only a
Synthetic Full schedule.
The backups fail continuously at the catalog merge steps.
Archive log backups—The Oracle database archive logs are backed up during the full and incremental backups. Oracle Incremental Merge provides an option to back up only the archive logs. The archive log backups are protected by a DD retention lock.
Restore operations—You can perform centralized restores and live mount or instant access recovery of Oracle Incremental Merge backups from the
PowerProtect Data Manager UI. A live mount operation is a live migration of the database by using the image-based backup copies. The instant access recovery provides access to the database files directly from the protection storage without restoring the database to the client.
Mount operations—An Oracle Incremental Merge backup performs open and write operations to a local disk or NFS mount. For BoostFS mount-based operations, the storage unit is mounted by using a DD BoostFS FUSE mount operation and the operations are performed on the mounted storage unit. The latest
PowerProtect Oracle RMAN Agent Administration Guide provides details about the
ddbmoim command that you use to perform a mount operation.
Unmount operations—An Oracle Incremental Merge operation unmounts the storage unit from the local mount path. A BoostFS mount-based operation uses a DD BoostFS FUSE mount. The latest
PowerProtect Oracle RMAN Agent Administration Guide provides details about the
ddbmoim command that you use to perform an unmount operation.
MTree replication operations—You can perform the MTree replication of an Oracle Incremental Merge backup on a primary system to a secondary system.
Cloud tier operations—You can perform the Oracle Incremental Merge backups and restores by using the cloud tier. For example, you can perform instant access recovery after recalling the required files from the cloud tier to the active tier on DD.
PowerProtect Data Manager obtains the metadata from all Oracle Incremental Merge backups during copy discovery. All the fast copies of Oracle Incremental Merge backups can be used later for the Oracle Incremental Merge restores, disaster recovery, or instant access recovery.
Before you perform any Oracle Incremental Merge operations, you must complete the procedures in
Installation requirements for Oracle Incremental Merge. You must configure an Oracle Incremental Merge protection policy in the
PowerProtect Data Manager UI for all the assets to be protected by Oracle Incremental Merge backups.
Enable centralized Oracle Incremental Merge backups in a non-RAC environment
In a non-RAC environment, you must enable the centralized Oracle Incremental Merge backups by specifying the TNS alias name in the
Net Service Name field in the
PowerProtect Data Manager UI.
For example, ORCL is the TNS alias name in the
tnsnames.ora file as follows:
To enable the centralized Oracle Incremental Merge backups, specify ORCL as the net service name in the
PowerProtect Data Manager UI:
Select
Infrastructure > Assets, and then click the
Oracle tab.
Select the assets by clicking the check box next to each required asset name.
Select
More Actions > Set Credential.
In the
Set Credential dialog box, specify the required values for
Database Credentials:
Select
Database User or
Wallet, and select the credentials from the menu.
Type
ORCL in the
Net Service Name text box.
Limitations of Oracle Incremental Merge
The following limitations apply to the Oracle Incremental Merge operations:
Oracle Incremental Merge operations are not supported on AIX.
PowerProtect Data Manager cannot discover any Oracle Incremental Merge backups that were performed using a stand-alone Oracle RMAN agent, which was not integrated with
PowerProtect Data Manager.
Installation of the DD BoostFS software in a non-default location is not supported.
IPv6 is not supported with the DD BoostFS protocol.
Encryption in-flight and
Smart Scale are not supported with the NFS protocol.
When any of the following changes occur in an NFS protection policy, outdated NFS entries in the
/etc/fstab file are not changed automatically. The outdated NFS entries must be changed manually:
Storage unit is changed.
DD is changed.
Asset is removed from the protection policy.
Asset is moved to a different Oracle Incremental Merge protection policy.
Data Guard heterogeneous deployment with nodes on more than one type of operating system is not supported.
Oracle Incremental Merge backups on multiple nodes (load balancing) are not supported.
Cloud tiering of incremental delta backup copies is not supported.
The dry run option is not supported for instant access recovery.
Data is not available for the Topic
Please provide ratings (1-5 stars).
Please provide ratings (1-5 stars).
Please provide ratings (1-5 stars).
Please select whether the article was helpful or not.
Comments cannot contain these special characters: <>()\