Configuring the Snap Creator Framework and SAP HANA database backup

Contributors Download PDF of this page

You must configure the Snap Creator Framework and the SAP HANA database backup.

  1. Connect to the Snap Creator graphical user interface (GUI): https://host:8443/ui/.

  2. Log in using the user name and password that were configured during the installation. Click Sign in.

    Shows the Snap Creator GUI login
  3. Enter a profile name and click OK.

    sap hana user profile

    For example, “ANA” is the SID of the database.

  4. Enter the configuration name, and click Next.

    Shows the configuration name entered in the field
  5. Select Application plug-in as the plug-in type, and click Next.

    shows select application plug-in
  6. Select SAP HANA as the application plug-in, and click Next.

    sap hana select application plug in
  7. Enter the following configuration details:

    1. Select Yes from the drop-down menu to use the configuration with a multitenant database. For a single container database select No.

    2. If Multitenant Database Container is set to No, you must provide the database SID.

    3. If Multitenant Database Container is set to Yes, you must add the hdbuserstore keys for each SAP HANA node.

    4. Add the name of the tenant database.

    5. Add the HANA nodes on which the hdbsql statement must be executed.

    6. Enter the HANA node instance number.

    7. Provide the path to the hdbsql executable file.

    8. Add the OSDB user.

    9. Select Yes from the drop-down list to Enable LOG Cleanup.

      NOTE:

      • Parameter HANA_SID is available only if the value for parameter HANA_MULTITENANT_DATABASE is set to N

      • For multitenant database containers (MDC) with a “Single Tenant” resource type, the SAP HANA Snapshot copies work with UserStore Key based authentication. If the HANA_MULTITENANT_DATABASE parameter is set to Y, then the HANA_USERSTORE_KEYS parameter must be set to the appropriate value.

      • Similar to non-multitenant database containers, the file-based backup and integrity check feature is supported

    10. Click Next.

    file based backup configuration
  8. Enable the File-Based Backup operation:

    1. Set the File-Backup Location.

    2. Specify the file-backup prefix.

    3. Select the Enable File-Backup checkbox.

    4. Click Next.

      enable file based backup
  9. Enable the Database Integrity Check operation:

    1. Set the temporary File-Backup location.

    2. Select the Enable DB Integrity Check checkbox.

    3. Click Next.

    Database Integrity Check
  10. Enter the details for the agent configuration parameter, and click Next.

    This image is explained by the surrounding text.
  11. Enter the storage connection settings, and click Next.

    This image is explained by the surrounding text.
  12. Enter the storage login credentials, and click Next.

    This image is explained by the surrounding text.
  13. Select the data volumes that are stored on this storage controller, and click Save.

    This image is explained by the surrounding text.
  14. Click Add to add another storage controller.

    This image is explained by the surrounding text.
  15. Enter the storage login credentials, and click Next.

    This image is explained by the surrounding text.
  16. Select the data volumes that are stored on the second storage controller that you created, and click Save.

    This image is explained by the surrounding text.
  17. The Controller/Vserver Credentials window displays the storage controllers and volumes that you added. Click Next.

    This image is explained by the surrounding text.
  18. Enter the Snapshot policy and retention configuration.

    The retention of three daily and eight hourly Snapshot copies is just an example and could be configured differently depending on the customer requirements.

    Note Select Timestamp as the naming convention. The use of the naming convention Recent is not supported with the SAP HANA plug-in, because the timestamp of the Snapshot copy is also used for the SAP HANA backup catalog entries.
    This image is explained by the surrounding text.
  19. No changes required. Click Next.

    This image is explained by the surrounding text.
  20. Select SnapVault, and configure the SnapVault retention policies and the SnapVault wait time.

    This image is explained by the surrounding text.
  21. Click Add.

    This image is explained by the surrounding text.
  22. Select a source storage controller from the list, and click Next.

    This image is explained by the surrounding text.
  23. Select all the volumes that are stored on the source storage controller, and click Save.

    This image is explained by the surrounding text.
  24. Click Add, and select the second source storage controller from the list, and then click Next.

    This image is explained by the surrounding text.
  25. Select all the volumes that are stored on the second source storage controller, and click Save.

    This image is explained by the surrounding text.
  26. The Data Protection Volumes window displays all the volumes that should be protected in the configuration that you created. Click Next.

    This image is explained by the surrounding text.
  27. Enter the credentials for the target storage controllers, and click Next. In this example, the “root” user credentials are used to access the storage system. Typically, a dedicated backup user is configured on the storage system and is then used with Snap Creator.

    This image is explained by the surrounding text.
  28. Click Next.

    DFM/OnCommand Setting GUI. This image is explained by the surrounding text.
  29. Click Finish to complete the configuration.

    This image is explained by the surrounding text.
  30. Click the SnapVault settings tab.

  31. Select Yes from the drop-down list of the SnapVault Restore Wait option, and click Save.

    This image is explained by the surrounding text.

    It is recommended that you use a dedicated network for replication traffic. If you decide to do so, you should include this interface in the Snap Creator configuration file as a secondary interface.

    You can also configure dedicated management interfaces so that Snap Creator can access the source or the target storage system by using a network interface that is not bound to the storage controller’s host name.

    mgmtsrv01:/opt/NetApp/Snap_Creator_Framework_411/scServer4.1.1c/engine/configs/HANA_profile_ANA
    # vi ANA_database_backup.conf
    
    #####################################################################
    ########################
    #     Connection Options                                            #
    #####################################################################
    ########################
    PORT=443
    SECONDARY_INTERFACES=hana1a:hana1a-rep/hana2b;hana1b:hana1b-rep/hana2b
    MANAGEMENT_INTERFACES=hana2b:hana2b-mgmt