Oracle IntelliSnap General FAQs

Can I perform IntelliSnap backups for Oracle databases that use ASM disks on VxDMP devices?

No. You cannot perform IntelliSnap backups for Oracle databases that use ASM disks on VxDMP devices.

Can I perform an IntelliSnap backup for ASM Oracle databases on Windows?

No. You cannot perform IntelliSnap backups for ASM Oracle databases on Windows computers.

Can I use a separate proxy to perform a backup copy?

No. The Use Separate Proxy for Snap to Tape option in Subclient Properties is not supported for the Oracle iDataAgent.

Can I perform an incremental backup copy?

Yes. You can perform an incremental backup copy using RMAN.

Can I perform a log restore from an IntelliSnap backup using RMAN?

No. Currently, log restore from an IntelliSnap backup using RMAN is not supported.

Are partial snaps supported for VSS backup?

No. Currently, Partial Snaps are not supported for VSS backup.

Can I perform RMAN restore from VSS IntelliSnap backup?

No. Currently, RMAN restores from VSS IntelliSnap backups are not supported.

Can I revert partial tablespaces?

No. Revert operation is not supported for partial tablespaces.

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. Use 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.

Can I configure the Oracle database to include the root volume of a file server?

No, data that resides on the root volume cannot be part of the Oracle database content.

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.

Can I perform an IntelliSnap backup without a valid Archive Log Destination directory?

No. You cannot perform an IntelliSnap backup without a valid archive log destination directory. IntelliSnap will not work if you configure the archive log destination with a pattern such as the following example:

Example:

log_Archive_dest_1='location=/archivelog/db_'

Can I mount snapshots on its own member nodes in a windows cluster and perform IntelliSnap operations?

Mount is not possible on its own member nodes in a Windows cluster environment. Consider the following to perform IntelliSnap operations in a Windows clustered environment:

  • Disable the data verification on Windows cluster to successfully perform IntelliSnap operations. See Disabling Verification of Datafiles During Backup for more information.

  • Use a proxy computer to perform restore operations.

  • Revert operations are currently not supported on Windows clusters.

Can I use a separate proxy to perform a backup copy?

No. The Use Separate Proxy for Snap to Tape option in Subclient Properties is not supported for the Oracle iDataAgent.

Can I restore a point in time IntelliSnap backup, if copy precedence is not selected?

Generally, we can set copy precedence for storage policy. The copy that is set to a copy precedence of 1 will be restored. However, if a IntelliSnap backup job is available, then it won't consider the copy precedence and restores only from the IntelliSnap backup.

If the database and instance name are different, can i perform a table level restore?

No. The table level restores will not work, if the database and instance names are different.

Can I perform a Log Only restore for ASM database?

No. Log Only restore is not supported for ASM database.

How do I determine the supported IntelliSnap operations based on the location of the Oracle application, data and log volumes on the client?

The following table displays the supported IntelliSnap operations based on the location of the Oracle Application, data and log volumes on the client :

Operation

Oracle Application/data/log are on the same physical disk/volume group

Oracle Application is on different device/volume group but Oracle data and log on same physical disk/volume group

Oracle Application, data and log are on different physical disks/volume groups (Recommended Configuration)

Notes

IntelliSnap Backup

Supported

Supported

Supported

Backup Copy

Supported

Supported

Supported

IntelliSnap Restore

Supported

Supported

Supported

Volume level Revert

Not Supported

Supported (based on Array Support)

Supported

For a NetApp array, if the data and logs are on the same volume, the log snap will be automatically deleted after the data volume revert.

File Level Revert (NetApp NFS only)

Supported

Supported

Supported

If data and logs are on same volume/disk, multiple snaps will be taken in data phase and log phase separately.

The following table displays the ASM, proxy and LUN support.

Physical server that uses ASM Storage

Proxy
Information

Proxy
Support

iSCSI
Lun

FC
Lun

Notes

<IntelliSnap Backup>

Use a physical proxy server with Oracle and an ASM instance used for the backup copy

Yes

Yes

Yes

IntelliSnap Restore

Use a physical proxy server with Oracle and an ASM instance to mount the ASM storage for snap restore

No

No

No

All mounts must be local.

The destination host must have access to the snap.

Restore from Backup Copy

Use a physical server with Oracle and ASM instance to restore from a backup copy

Yes

Yes

Yes

Virtual server using ASM (with physical RDMS)

<IntelliSnap Backup>

Use a physical proxy server with Oracle and an ASM instance used for the backup copy

Yes

Yes

Yes

The backup copy is on the physical proxy server.

The CvDeviceTree test must pass for the ASM disk.

IntelliSnap Restore

Use a physical proxy server with Oracle and an ASM instance to mount the ASM storage for snap restore

No

No

No

The following conditions must be met in order to perform an in-place revert operation.:

  • The mount must be local to the destination.

  • The destination must have direct access to the storage array.

  • If the virtual server has iscsi enabled and the filer is accessible.

Restore from Backup Copy

Use a physical server with Oracle and ASM instance to restore from a backup copy

Yes

Yes

Yes

Virtual server using ASM (with virtual RDMS)

<IntelliSnap Backup>

Use a physical proxy server with Oracle and an ASM instance used for the backup copy

No

No

No

There is no access to the filer.

IntelliSnap Restore

Use a physical proxy server with Oracle and an ASM instance to mount the ASM storage for snap restore

No

No

No

There is no access to the filer.

Restore from Backup Copy

Use a physical server with Oracle and ASM instance to restore from a backup copy

Yes

Yes

Yes

Why do I see a difference in the application size of IntelliSnap backup job after a backup copy operation?

The application size of the IntelliSnap backup job is determined by querying the database. If subclient content has both database and archived log selected for snap, then the size determined is cumulative of database usage size and archive log size. Once the backup copy operation is executed, the actual application size is displayed for the IntelliSnap backup job.

In addition, file system backup copy operation will display a greater application size than RMAN backup copy. This is because file system backup copy will backup the entire datafile whereas RMAN backup copy will backup only the used blocks in the datafile.

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 RETENTION POLICY TO RECOVERY WINDOW OF n DAYS

Why do I see a difference in the 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 additional size for the archive log location.

What considerations are required if the SP file is not included in a backup that uses RMAN backup copy?

If you did not include the SP file in the subclient content (Subclient Properties dialog box, Content tab, Back up SP file check box), the software does not back up the SP file in a backup copy operation and the proxy server instance starts by using the SP file that is located in the $ORACLE_HOME/dbs directory (UNIX) or %ORACLE_HOME%\database folder (Windows).

Page contents

×

Loading...