SnapProtect - Advanced Snapshots - SAP Oracle

Table of Contents

Managing Snapshots

The snapshots of the data created by the SnapProtect backup are also available for various other operations like list, mount, unmount, delete, or revert.

List Snapshots

The browse operation provides the capability to see the snapshots created for an agent, job, or a snapshot copy. The list of the snapshots displayed is corresponding to the entity selected for the browse operation, for e.g., browsing the snapshots for an agent will display all the snapshots created for the selected agent. You can view volume or disk related information for the snapshots. Follow the steps given below to browse snapshots.
  1. From the CommCell Console, navigate to Client Computers | <Client> | SAP for Oracle | <Instance>.
  2. Right-click the <Subclient> and click List Snaps.

    The Snaps created during SnapProtect operation dialog box appears.

  1. The Snaps created during SnapProtect operation dialog box displays a list of all the snapshots created for the selected subclient. It also displays important information about each snapshot, including the source mount path, snap mount path, the storage array, and the source client.
    • Right-click the snapshot and click Details to view the snapshot properties.
    • Click the Disk View tab to display the snapshot name, e.g. SP_2_79_1286222629.

You can also browse snapshots at the instance level of the SAP Oracle Agent.

Mount Snapshots

You can mount any available snapshot to access the data included in the snapshot. Follow the steps below to mount snapshots:

When mounting multiple snapshots, note the following:

  • You can mount snapshots from different jobs
  • The snapshots selected for mounting should belong to the same agent (such as Windows file system, UNIX file system, or VMware).
  • Snapshots should be mounted on a MediaAgent with the same operating system as the snapshot volumes. For example, Windows volumes should be mounted on a Windows MediaAgent, and Linux volumes should be mounted on a Linux MediaAgent.
  • There are no limits on the number of snapshots to be mounted. However, increasing the number of snapshots that are selected also increases the time for mounting the snapshots.
  • For Virtual Server Agent (VSA), mount snapshots from the backup set or subclient level. Mounting snapshots from the storage policy is not supported.
  • For VMware, mounting multiple snapshots of the same volume at the same time is not supported.
  1. From the CommCell Browser, navigate to Client Computers | <Client> | <Agent>| <Instance>.
  2. Right-click the subclient and click List Snaps.

    The Snaps created during SnapProtect operation dialog box appears.

  1. Right-click the snapshot that you wish to mount and click Mount.

    To select multiple snapshots, hold <Shift> key and select the snapshots to be mounted.

  2. Click Yes.
  3. In the Mount Path dialog box, specify the destination client and the path on the client in the Destination Client and Destination Path fields.
  4. If you do not wish to save any changes made to the mounted snapshot after the snapshot is unmounted, select Protect Snapshot during mount.
  5. Click OK.

If you do not select Protect Snapshot during mount, the changes made to snapshot when it is mounted will be retained after the snapshot is unmounted and the snapshot can no longer be used for restore.

Mount Snapshots on a MediaAgent

You can mount any available snapshot on a MediaAgent to access the data included in the snapshot. It is recommended that you select the option to protect a snapshot when it is mounted, as this ensures the changes made to the snapshot when it is mounted are not retained when you unmount the snapshot and the snapshot is usable for data protection operations. Follow the steps given below to mount snapshots on a MediaAgent:

When mounting multiple snapshots, note the following:

  • You can mount snapshots from different jobs
  • The snapshots selected for mounting should belong to the same iDataAgent, such as Windows file system, Unix file system, VMware etc,.
  • The snapshots should be mounted on the corresponding OS MediaAgent. Linux volumes should be mounted on a Linux MediaAgent etc,.
  • There are no limits on the number of snapshots to be mounted. However, if there are more number of snapshots selected, the time taken for mounting the snapshots also will increase.
  • When mounting Oracle ASM snapshots, the destination client must have a +ASM instance configured in addition to having the Oracle iDataAgent and MediaAgent installed.
  1. From the CommCell Browser, navigate to Client Computers | <Client> | <Agent>| <Instance>.
  2. Right-click the subclient and click List Snaps.

    The Snaps created during SnapProtect operation dialog box appears.

  1. Right-click the snapshot to mount and click Mount.

    To select multiple snapshots, hold the <Shift> key and select the snapshots to be mounted.

  2. Click Yes.
  3. For Oracle ASM snapshots, specify the ASM diskgroup name to be used for the snapshot, e.g. "+ASMSNAP", in the Destination Path field..

    On a Windows platform, enter a CIFS Share Name for the Agent.

  4. If you do not wish to save any changes made to the mounted snapshot after the snapshot is unmounted, select Protect Snapshot during mount.
  5. Click OK.

If you do not select Protect Snapshot during mount, the changes made to snapshot when it is mounted will be retained after the snapshot is unmounted and the snapshot can no longer be used for restore.

Unmount Snapshots

Follow the steps given below to unmount snapshots:

  1. From the CommCell Browser, navigate to Client Computers | <Client> | <Agent>| <Instance>.
  2. Right-click the subclient and click List Snaps.

    The Snaps created during SnapProtect operation dialog box appears.

  1. Right-click the snapshot you wish to unmount and click Unmount.

    To select multiple snapshots, hold <Shift> key and select the snapshots to be mounted.

  2. Click Yes when prompted if you want to continue.

If the snapshot does not get unmounted, select the Force Unmount option to mark the snapshot as unmounted.

Delete Snapshots

Snapshots can either be deleted using job-based pruning or from the list of displayed snapshots when browsing snapshots. Data Aging can also be used to define the retention rules and pruning of snapshots. Follow the steps given below to delete snapshots:

  • Manual deletion of snapshots is not recommended. When a snapshot is deleted, it is no longer possible to perform data recovery operations from the snapshot copy. However, if a backup copy was created from the snapshot, data recovery operations can be performed from the backup copy.
  • Ensure that the snapshot to be deleted is not mounted.
  • For NetApp E-series PiT engine, the order to delete snapshots should be the oldest snapshot first.

  1. From the CommCell Console, navigate to Client Computers | <Client> | SAP for Oracle | <Instance>.
  2. Right-click the <Subclient> and click List Snaps.

    The Snaps created during SnapProtect operation dialog box appears.

  1. Right-click the snapshot you wish to delete.

    Ensure all snapshots with the same Job ID are selected for a successful deletion operation.

  2. Click Delete.
  3. Enter the confirmation text string, erase snapshots.
  4. Click OK.

Force Delete

The force delete operation is useful when a client, subclient, or a storage policy copy has been deleted or when a source MediaAgent computer is unavailable and you want to delete snapshots from the CommCell database. The force-deleted snapshots are not moved to tape and are not deleted on the array.

  1. From the CommCell Console, navigate to Client Computers | <Client> | SAP for Oracle | <Instance>.
  2. Right-click the <Subclient> and click List Snaps.

    The Snaps created during SnapProtect operation dialog box appears.

  1. Right-click the snapshot to select it to force delete.
  2. Click Force Delete.
  3. Enter the confirmation text string, force erase snapshots.
  4. Click OK.

Revert a Snapshot

You can use the revert operation to bring the data back to the point-in-time when the snapshot was taken. This operation overwrites any modifications to the data since the time when the snapshot was created. This option is available if the storage arrays that you are using supports revert. Revert operations are supported on NetApp File Servers but not from SnapVault or SnapMirror snapshots. You can either perform an application aware revert or a hardware specific revert.

Review the following before performing a revert operation:

  • As only the data volumes can be reverted, ensure that the data volumes are not stored in the online log, sap backup, and saparch directories
  • Ensure that the volumes being reverted/restored are not accessed by any user/application during the Revert/Restore process.
  • Ensure that the database and other SAP data volumes reside on separate LUNs or drives. For example, sapdata(1-#) volumes and other volumes like sapbackup, saparch, sapreorg, dbs should reside on separate LUNs or drives.
  • The revert operation is not supported on Windows clusters.
  • On Windows clients, disable automount using the following command:

    diskpart> automount disable

  • On Unix clusters, use pre/post scripts to freeze and unfreeze the cluster for revert operations. For example, on Red Hat Linux cluster, use the following command in the pre/post scripts:

    clusvcadm -Z <group> to freeze the cluster

    clusvcadm -U <group> to unfreeze the cluster

    This is required because during revert the application is shut down and corresponding volumes are unmounted. In that case, the cluster will automatically failover to another node thus preventing the revert operation.

Perform a SAP Oracle Revert Restore Operation Using the Command Line Interface

Review the following before performing a revert operation:

  • Set RevertSnapVolume to 1 at the following location:

    $ORACLE_HOME/dbs/init<SID>.utl

  • Ensure that the archived redo log files and their mirror log files reside on the same array as data.
  • Run the following to perform Revert Restore of Database:

    ./brrestore –d util_file –m all –b last

  • After a successful revert restore operation, you must also run the following command to restore control files:

    ./brrestore –d util_file –b last –m 0

  • After the data and Cntrl File restore, perform recover as “recover database using backup controlfile until cancel” or recover using brrecover tool.
  • When using HP EVA Clone or Data Replicator for SnapProtect backup, the revert operation is not supported.

It is recommended to verify the contents of the backup and ensure that you want to perform a revert operation as it is an irreversible operation.

Perform an Application Aware Revert

  1. From the CommCell Browser, right-click the entity that contains the data you want to restore, and click All Tasks | Browse Backup Data.
  2. From the Browse and Restore dialog box, click OK.
  3. Select the data you want to revert and click Recover All Selected.
  4. From the Restore Options dialog box, click Advanced.
  5. Select the Use hardware revert capability if available option.
  6. Click OK to confirm the revert operation.
  7. Click OK from the Advanced Restore Options dialog box.
  8. Click OK to start the revert.

    An application aware revert operation reverts back all the volumes included in the backup.

Perform a Hardware Specific Revert

  1. From the CommCell Console, navigate to Client Computers | <Client>.
  2. Right-click the subclient and click List Snaps.

    The Snaps created during SnapProtect operation dialog box appears.

  3. Right-click the snapshot that you wish to delete and click Use hardware revert capability if available.
  4. Enter the confirmation text string, confirm.
  5. Click OK.

A hardware specific revert operation reverts back the volume included in the snapshot. If the volume being reverted is the source of vault/mirror relation and if the protection topology is Primary-Vault, Primary-Mirror, or Primary-Vault-Mirror, then the baseline snapshot on primary volume will be shifted to the snapshot of the reverted volume. In case of Primary-Mirror-Vault or Primary-Mirror1-Mirror2 topologies, the baseline snapshot for Mirror-Vault relationship and Mirror1-Mirror2 relationship, respectively, is not shifted, which may lead to auxcopy job failures.

The revert operation might delete some snapshots. To avoid failures, when selecting SnapProtect jobs for auxcopy or backup copy operations, unpick all SnapProtect jobs that have deleted snapshots as a result of a revert operation. Running auxcopy or backup copy operations with SnapProtect jobs from deleted snapshots might produce failures.

Snap Reconciliation

Snapshots may be deleted from the array due to factors like low disk space on the array, number of snapshots exceeds the threshold etc., and the jobs corresponding to these deleted snapshots can no longer be used for any data recovery or backup copy operations. You can use the nRunSnapRecon additional setting to start snap reconciliation to check for missing snapshots once in every 24 hours and marks jobs corresponding to the missing snapshots as invalid.

Snap Cleanup

If an SnapProtect operation is in pending/suspended states or is killed, a prune request will be sent immediately and delete the snaps which were taken in that SnapProtect operation on the storage array. For example, if an SnapProtect operation is in pending state after taking snaps for data volume, then it will remove the snap for that data volume. Once the job resumes, it will take a snap again from data phase. As clean-up is performed immediately, you need not wait for the data aging job to remove un-useful snaps.

View Snapshot Details

You can view the details of a snapshot for an agent, job, or a snapshot copy. When you right-click any of these entities, you will be able to browse all the snapshots corresponding to the selected entity.
  1. From the CommCell Browser, right-click the entity that contains the snapshots you want to browse, and click All Tasks | List Snaps.
  2. The Snaps created during SnapProtect operation dialog box displays a list of all the snapshots created for the selected entity and displays important information about each snapshot, including the source mount path, snap mount path, the storage array, and the source client.
  3. Right-click the snapshot and click Details to view the snapshot properties.

Select a Job for Backup Copy

You can select a specific job for creating backup copy. Once selected, the Move Snap to Tape field for the specific job will be changed to Picked (i.e., the next backup copy operation will move this job to media).
  1. Right-click a storage policy containing SnapProtect backup jobs, and then click View Jobs.
  2. Right-click the job and then click Pick for Backup Copy.

Disable a Job for Backup Copy

You can prevent a job from being moved to media. You can apply this option to those jobs that were previously selected for moving to media. On selecting this option, the Move Snap to Tape field for the specific job will be changed to Not Picked (i.e., the next backup copy operation will not move this job to media).
  1. Right-click a storage policy containing SnapProtect backup jobs and then click View Jobs.
  2. Right-click the job and then click Do not Backup Copy.

SCSI Reservation

SCSI reservation can be enabled for SnapProtect backup for all the agents. Enabling SCSI Reservation prevents other applications (SCSI3 compliant) from using the reserved SCSI Device (i.e. the mounted snapshot).

If this option is enabled and the hardware does not support this type of operation, subsequent backup jobs may fail.

Use the following steps to enable SCSI reservation:

  1. From the CommCell Browser, navigate to Client Computers.
  2. Right-click the <Client>, and then click Properties.
  3. Click Advanced.
  4. Click the Additional Settings tab.
  5. Click Add.
  6. In the Name box, type nSCSIReserveForSnap.
  7. In the Category box, select iDataAgent.
  8. In the Type box, select Integer.
  9. In the Value box, type 1.