Mount an SAP HANA scale-out backup as a standard mount

You can mount images of an SAP HANA database as a standard mount or as a virtual database—application aware mount. This is the procedure for a standard mount. To make a virtual database—application aware mount—see the procedure in SAP HANA database virtual copy.

About standard mounts

A standard mount provides the backup image disk of data, active log and archive log volume to the specified target. You can mount snapshot backup images of an SAP HANA database as a standard mount for the following:

  • Any manual operation.
  • To run the SNAPSHOT DATA INTEGRITY CHECK: This tool runs the SAP HANA persistence checking tool, hdbpersdiag with the 'check all' option to verify the healthy state of data volumes from the mounted snapshot image. Mount jobs fail if there is any corruption during these checks.

Pre checks during mount

  • Connector connectivity status: The Backup and DR agent is installed and a secret is applied for host connectivity between the backup/recovery appliance and the Backup and DR agent.
  • Mount locations specified are available for mount operation.
  • HANA binary is installed.
  • Verify that the HANA sid same as source is not up and running on the target.
  • The HANA instance version is greater than 2.0SP05.
  • Permission check on source and target project for the cloud service.

Use these instructions to mount the database image as a standard mount:

  1. Right-click the protected database from the App Manager Applications list, and select Access.

  2. Select a snapshot image and choose Mount.

  3. Click Target on the Mount page and select the target SAP HANA server from the drop-down.

  4. Optionally, enter a unique name associated with the mount in the Label field.

  5. Under Application Options, disable Create New Virtual Application.

  6. Enter a Mount Location in Mapping Options.

    IBM Db2

    • TARGET INSTANCE NAME. From the drop-down, select a target Db2 instance to attach the selected database as a virtual copy.

    MariaDB

    • MARIADB TARGET SERVER PORT. Enter the port number on the target server where a new MySQL instance will get created for the new child databases.
    • MARIADB TARGET OS USER NAME. Enter the name of the operating system user on the target server where a new MySQL instance will get created.
    • MARIADB TARGET SERVER BASE DIRECTORY. Enter the path to the base directory where the configuration files for MySQL instance on the target server are stored. resource profile to protect the database.

INCLUDED TENANT DATABASES is informational only showing the list of tenant databases under backup image. Under Mapping Options DEVICE PATH: is pre-populated with the source DEVICE PATH. Provide the path that is not in use at the selected target and that you want to use to mount the snapshot image of DATA VOLUME, LOG VOLUME and LOG BACKUP VOLUME on the target server. Note: special character - (ex: data-1) is not supported in the device mount location DISK TYPE: is pre-populated with the source DISK TYPE value. You can change the disk type by selecting the different type from the drop-down value. SNAPSHOT DATA INTEGRITY CHECK: By default the value is set to true. Set it to false by clicking the toggle button if you don't want to run the check. This tool will run the SAP HANA persistence checking tool, hdbpersdiag API with 'check all' option. This will verify the healthy state of data and active log volumes from the mounted snapshot image. Mount jobs will fail with error for any corruption during these checks otherwise it will show success.

The result of the Integrity check will be available under /var/act/log/(HANA sid)_dataintegrity_check.log and /usr/sap/GC1/HDB00/hana-scaleup-3/trace/localclient.*.trc./.

Click Pre-Flight check. This will validate the required options on the target server for a successful mount. Upon a successful Pre-Flight the Submit button will be enabled. Upon failure Pre-Flight will show the failed check to correct and rerun the Pre-Flight.

  1. If you plan to run pre- or post- scripts with the mounted image, then enter the path and relative filenames in the Pre-Script and Post-Script fields.
  2. Click Submit. You can go to the Job Monitor to view the progress and details of the job. The mounted image is available in the Active Mounts.

Management of the active mounts

Once you have created a mount, you can track the image from the Backup and DR Service management console App Manager > Active Mounts. Ideally, don't leave any image mounted indefinitely. This is because the backup image that the mount was created from, cannot expire until all its mounts have been deleted. When you have finished using the mounted image then either:

  • Unmount the image. You can remount it if needed. You can then delete the image later when you are certain it is no longer needed.
  • Unmount and delete the image. This deletes the mounted image, not the backup that the mount is based on.

Backup and DR Service documentation for SAP HANA scale-out

This page is one in a series of pages specific to protecting and recovering SAP HANA scale-out instances with Backup and DR Service. You can find additional information in the following pages: