Loading...

IntelliSnap - Troubleshooting - SAP Oracle

Table of Contents

SAPOR0001: Restore operation fails on selecting the copy precedence as 1 if the logs were backed up traditionally

SAPOR0002: Data and Log Restore Operation Fails when Trying to Restore from Data Only Jobs

SAPOR0003: An IntelliSnap Backup Copy Fails When You Have an ext3 or ext4 LVM Volume for the Hardware Array

Completed with One or More Errors

Jobs Completed with Warnings

Revert Fails on Zpool Volume

SAPOR0001: Restore operation fails on selecting the copy precedence as 1 if the logs were backed up traditionally

If you back up the data after selecting the Use Traditional Backup for Logs check box and then try to restore it by selecting the copy precedence as 1, the restore job will fail.

Symptom

When you run a backup after selecting the Use Traditional Backup for Logs check box,

  • Snap backup is run on the data and the copy precedence of the data is set to 1
  • Logs are backed up traditionally and the copy precedence of the logs is set to 2

Because of this difference in the copy precedence, if you run a restore by selecting the copy precedence as 1, the restore operation fails.

Resolution

Run a restore without selecting any copy precedence.

Alternatively, you can perform a backup copy operation to copy snapshot of the backed up data to any media and then run a restore by selecting the copy precedence as 2. For step-by-step instructions to run a backup copy, see Backup Copy for IntelliSnap Backup.

SAPOR0002: Data and Log Restore Operation Fails when Trying to Restore from Data Only Jobs

The restore operation fails with the following error message while using the Restore by Job feature to restore data and log.

Failing restore as the log summary file information could not be found.

Symptom

For restoring both data and log, if you try to restore from the data only job, the restore operation will fail.

Resolution

Run a restore by selecting the job type as Log Incremental.

SAPOR0003: An IntelliSnap Backup Copy Fails When You Have an ext3 or ext4 LVM Volume for the Hardware Array

Issue

An IntelliSnap backup copy fails on the following agents when you have ext3, or ext4, or XFS LVM volume for the hardware engine:

  • MySQL
  • PostgreSQL
  • SAP HANA
  • SAP on Oracle

Resolution

If you use Red Hat 7.x or CentOS 7.x for the backup copy proxy, perform the following operations:

  1. Disable and stop the lvm2-lvmetad. On the command line, type the following commands:

    systemctl disable lvm2-lvmetad
    systemctl stop lvm2-lvmetad

  2. Disable the lvmetad parameter in the LVM config file. Edit the /etc/lvm/lvm.conf file, and add the following line to the file:

    use_lvmetad = 0

Completed with One or More Errors

A job is marked as Completed with Errors [CWE] if some data is backed up or restored and then the job is killed or fails.

Jobs Completed with Warnings

A job is marked as Completed with Warnings [CWW], if Brbackup/Brarchive returns warnings during backups or restores or the database restore succeeds, however the database could not be opened or recovered successfully.

Revert Fails on Zpool Volume

Sometimes, on Solaris Zpool volumes, revert can fail after the zpool gets exported. In such cases, $SAPDATA_HOME might get deleted as well.

To resolve this issue, we recommend to run a FS DataAgent Snapshot level revert of the Data Volume, then restore Control File and Archive Logs using SAP Oracle DataAgent. A FS DataAgent Snapshot revert has to be done in this case, as BRRESTORE process cannot invoke the Commvault Backint to run revert, if $SAPDATA_HOME is missing.

Windows 2003 Clusters -To do a Volume Level Revert on Windows 2003 cluster running SAP Oracle DataAgent, do not put the cluster volumes in Extended Maintenance Mode, as this will mark the volume offline.

We recommend using a FS DataAgent for Volume Level revert of Data volumes, before restoring the Control Files and Archive logs using the SAP Oracle DataAgent.

Windows 2008 and Windows 2012 Clusters -  These Operating System versions allow cluster volumes to be put in Maintenance mode, allowing for SAP Oracle DataAgent level revert to succeed.

Last modified: 1/10/2018 3:47:39 PM