> CommCell Console > Backup and Restore Agents > Snapshot Management > Supported Agents > Oracle RAC

IntelliSnap - FAQ - Oracle RAC

Can I use the Oracle agent to perform an IntelliSnap backup of an Oracle RAC client?

Yes, you can perform IntelliSnap operations for a single node Oracle RAC setup. The following configurations are required:

  • When configuring the Oracle RAC components for the first IntelliSnap backup, ensure that:

    • The Oracle instance is configured on one of the physical nodes for the Oracle RAC agent.

    • If the data and archive logs do not reside on a shared location, create a user-defined subclient for the archive logs and run a backup using RMAN. The original subclient should only include the data volume in order to perform a IntelliSnap backup.

    • The Use RMAN for Tape Movement option is selected during the subclient configuration if you plan to backup the archive logs.

  • The ASM Oracle Database should be located on a ASM disk group, and the underlying disks should be snap-able.

  • If you plan to use RMAN for copying the data to the media on the proxy computer, copy the Oracle parameter file (pfile) from the client to the proxy computer's $ORACLE_HOME/dbs/ directory, and remove any parameter containing Oracle RAC related entries. For example:

    • cluster_database_instances

    • cluster_database

    • <RAC Instance name>.thread

    • <RAC Instance name>.local_listener

    • <RAC Instance name>.instance_number

Can I delete the FRA content using the Archive Delete option when the backup does not include archive logs?

No. The flash recovery area (FRA) content is deleted based on the RMAN retention rules for FRA content, therefore it is not required to delete the FRA content manually.

Set the retention rules for the FRA content using the following command from the RMAN prompt with "n" representing the number of days 

CONFIGURE ARCHIVELOG DELETION POLICY TO RECOVERY WINDOW of n days

Can I prevent the single volume revert when the database is spanned across the multiple volumes?

No. You cannot prevent a single volume revert when the database is spanned across multiple volumes. When you perform a hard revert, the database will not be restored as the reversion happens at LUN level and the other source paths related to this database are not reverted. Hence, we recommend Restore by Revert which is application aware instead of regular revert using the CommCell Console (GUI).

The following steps explain the current process of reversion for a single volume when the database is spanned across multiple volumes:

  1. Create two Logical Unit Numbers (LUNs) from the same volume and another LUN from a different Volume.

  2. Create host volume from each LUN or two LUNs from the same volume. Create two LUNs from a different Volume and host volumes (partitioned disks) from each LUN.

  3. Create multiple mount points and mount the File System created from above LUNs.

  4. Create a database on these mount points and create table spaces spanned across these locations.

  5. Perform a IntelliSnap backup for the database.

  6. Perform a IntelliSnap backup after adding data and tables.

  7. Select all source paths related to LUN at previous Job ID and perform the hardware revert.

Yes, they are supported if you use a UNIX environment. The destination volumes referenced by Symbolic/Soft links are automatically included in the IntelliSnap backups. Soft link directory structure is supported on both NFS and SAN volume.

Why do I see more application size than the actual one for IntelliSnap?

If the subclient content has both the database and archived log selected for snap, then the size determined is cumulative of the database usage size and the archive log size. If archive logs are deleted manually without using RMAN, the database still thinks that those logs are available until a crosscheck runs and gives more size for the archive log location.

×

Loading...