Configuring an Oracle RMAN Incremental Backup Copy

You can perform Oracle RMAN incremental backup copy operations on a proxy server.

Before You Begin

Verify the following:

The database physical schema is the same in both the snapshot and the current backup. This means no addition or deletion of tablespaces and datafiles has occurred between the time of the snapshot and the current time. If the physical schema has changed, you can configure an additional setting to prevent backup copies from failing. For more information, see Preventing RMAN Backup Copy Failures due to Schema Changes.
The Oracle user ID/group ID on the source and the proxy client must be the same. Otherwise, the RMAN backup copy will fail due to permission issues.

Copy the Oracle parameter file (pfile) and password file from the source to the proxy computer's $ORACLE_HOME/dbs/ directory.
Create the bdump, udump, adump, cdump and diagnostic_dest directories. Ensure that the directories are in the same location as the source.
Create the DB_CREATE_FILE_DEST and LOG_ARCHIVE_DEST directories. If there are multiple archive destinations, then create the directories for each of the archivelog destinations.
Copy the catalog connection information from the source to the proxy in the tnsnames.ora file.
Start up the proxy instance in NOMOUNT mode.
Configure the proxy Oracle instance on the CommCell Console.
From the CommCell Browser, navigate to Client Computers > client > Oracle > instance.
Right-click the subclient and click Properties.

The Subclient Properties dialog box appears.
On the IntelliSnap Operations tab, select IntelliSnap.
From the Available Snap Engines list, select the storage array.
From the Use Proxy list, select the configured proxy.
Select Use RMAN for Backup Copy, and then click OK.

The Incremental option is now available for backup.
You can configure an additional setting to prevent backup copies from failing if the physical schema changes. For more information, see Preventing RMAN Backup Copy Failures due to Schema Changes.