Creating an SAP HANA Resource

  1. From the LifeKeeper GUI menu, select Edit, then Server. From the drop-down menu, select Create Resource Hierarchy.

A dialog box will appear with a drop-down list with all recognized recovery kits installed within the cluster. Select Generic Application from the drop-down list

Click Next

When the Back button is active in any of the dialog boxes, you can go back to the previous dialog box. This is especially helpful should you encounter an error that might require you to correct previously entered information.

If you click Cancel at any time during the sequence of creating your resource hierarchy, LifeKeeper will cancel the entire creation process.

  1. Select the Switchback Type. This dictates how the primary SAP HANA database will be switched back to this server when it comes back into service after a failover to the backup server. You can choose either intelligent or automatic. Intelligent switchback requires administrative intervention to switch the hierarchy back to the primary/original server. Automatic switchback means the switchback will occur as soon as the original server comes back on line and re-establishes LifeKeeper communication paths.

We recommend to use the Switchback Type intelligent.

The Switchback Type can be changed late from the General tab of the Resource properties dialog box.

Click Next

  1. Select the Server where you want to place the primary SAP HANA database. All servers in your cluster are included in the drop-down list.

Click Next

  1. On the next dialog enter the path to the Restore Script which will be used to start the SAP HANA database and control the replication mode. All the scripts you need for Restore, Remove, QuickCheck and Recover are located in directory /opt/LifeKeeper/HANA2-ARK. Enter the complete path in the dialog box

Click Next

  1. Enter the path to the Remove Script for the SAP HANA database and click Next. This is the script that stops the SAP HANA database.

Click Next

  1. Enter the path to the quickCheck Script for the SAP HANA database. This is the script that monitors the functionality of SAP HANA database and the Replication Mode. Although the quickCheck script is optional for some generic applications it is required for the HANA gen app resource.

Click Next

  1. Enter the path to the Local Recover Script for the SAP HANA database. This is the script that attempts to restore a failed component of SAP HANA database or the database itself. Although the recover script is optional for some generic applications it is required for the HANA gen app resource.

Click Next

  1. Enter the necessary Application Information for the SAP HANA database on this node. The following values are required and must be separated by a space: <SID>˽<Instance number>˽<Replication mode>˽<Site name>˽<Operation mode>

Click Next

  1. Select either Yes or No for Bring Resource in Service, and Click Next. Selecting No will cause the resource state to be set to OSU following the create; selecting Yes will cause the previously provided restore script to be executed. The resource state ISP is required to extend the SAP HANA resource to another cluster member.

Click Next

  1. Enter the Resource Tag, which is a unique name for the SAP HANA resource. This is the label you will see for this resource in the LifeKeeper GUI. The valid characters allowed for the tag are letters, digits and the special characters `-`,`_`,`.` and `/`. The resource name should be meaningful.

Click Next

  1. .Click Create Instance to start the creation process. A window will display a message indicating the status of the instance creation

Click Next

  1. . Select the Target Server on which the SAP HANA resource is to be extended. All remaining cluster member are included in the drop-down list.

Click Next

  1. Select the same Switchback Type as in step 2 selected. Click Next.
  1. Select or enter the Template Priority for the SAP HANA resource. This is the priority for the SAP HANA resource on the server where it is currently in service. Any unused priority from 1 (highest) to 999 (lowest) is valid. The default value is recommended.

Click Next

  1. Select or enter the Target Priority for the SAP HANA resource. This is the priority for the new extended SAP HANA resource relative to the equivalent resource on other servers. The default value is recommended.

Click Next

After receiving the message that the pre-extend checks were successful, click Next.

  1. Check the Resource Tag for the SAP HANA resource. The Resource Tag must be the same on all cluster members. Do not change the default value.

Click Next

  1. Enter the necessary Application Information for the SAP HANA database on this node.

The following values are required and must be separated by a space: <SID>˽<Instance number>˽<Replication mode>˽<Site name>˽<Operation mode>

Click Next

  1. Creating of SAP HANA resource on the selected node is started then the equivalencies between the cluster nodes for the resource are created.

Click Finish

  1. When this is finished, the Done button will be enabled. Click Done to finish.
  1. Next an IP resource should be created and placed in dependency with the SAP HANA resource. Refer to the administration guide “IP Recovery Kit” for these steps.

Feedback

Was this helpful?

Yes No
You indicated this topic was not helpful to you ...
Could you please leave a comment telling us why? Thank you!
Thanks for your feedback.

Post your comment on this topic.

Post Comment