Skip to main content
SnapManager for SAP

Restore backups by using Single File SnapRestore


You can restore the backups by using the Single File SnapRestore (SFSR) method.

  1. Create a profile from the SnapManager graphical user interface (GUI).

  2. Back up the database by using the GUI.

  3. Unlink the Oracle and Network File System (NFS) service groups from the cluster service groups and freeze them.

  4. Ensure that Secure Shell (SSH) is configured between the hosts and SnapDrive for UNIX by setting #secure-communication-among-cluster-nodes to on in the snapdrive.conf file.

  5. From the SnapManager GUI, perform full backup restore and recovery by using --alllogs.

  6. Unfreeze the service groups and link them back to the cluster service group.

    Note This configuration is applicable only when you use SnapDrive 4.1.1 D2 for UNIX and SnapDrive 4.2 for UNIX.

    If one restore operation is followed by another restore operation, then there is a possibility that the creation of the backup Snapshot copy fails. If you run successive restore operations within the specified time in which the SFSR can complete, then SnapManager for SAP will encounter Snapshot copy creation errors.

    To prevent Snapshot copy creation errors, ensure that restore operations are performed after the time period during which SFSR is in progress.

    To achieve this, check the LUN clone split process status by entering the following command from the storage system command-line interface (CLI):

    rsh filernname lun clone split status lun-name

    Sample Output:
    /vol/delaware_760gb/lun700gb (64% complete)..
    Note Volume-based SnapRestore (VBSR) is not supported on Solaris hosts running Veritas stack with SFRAC and VCS environment.