Create the ASCS Resource Hierarchy
- In the LifeKeeper GUI, click the icon to open the Create Resource Wizard. Select the “SAP” Recovery Kit.
- Enter the following values to create and extend a LifeKeeper resource (SAP-SPS_ASCS10) to protect the ASCS10 instance on node-a and node-b. Notice that the resource is being created on node-a and extended to node-b. Also note that the resulting resource should not be extended to node-c, the witness node. The icon indicates that the default option is chosen.
Create Resource Wizard | |
---|---|
Switchback Type | intelligent |
Server | node-a |
SAP SID | SPS |
SAP Instance for SPS | ASCS10 |
IP child resource | none |
Automate dependent filesystem creation | no |
Dependent filesystem resource | none |
SAP Tag | SAP-SPS_ASCS10 |
Pre-Extend Wizard | |
Target Server | node-b |
Switchback Type | intelligent |
Template Priority | 1 |
Target Priority | 10 |
Extend gen/app Resource Hierarchy Wizard | |
Root Tag | SAP-SPS_ASCS10 |
Once the SAP-SPS_ASCS10 resource has been successfully created and extended to node-b, the LifeKeeper resource panel should look similar to the following. Note that the names of the resources providing failover functionality for the ASCS and ERS virtual IP’s/hostnames may differ according to your chosen cloud platform depending on which subsection of Create ASCS and ERS Virtual IPs was followed.
- Right-click on the SAP-SPS_ASCS10 resource and select Create Dependency… from the drop-down menu.
For Child Resource Tag, specify the root resource of the resource hierarchy being used to failover the ASCS virtual IP/hostname. The precise resource name used in this step will depend on resources created in the subsection of Create ASCS and ERS Virtual IPs corresponding to your chosen cloud platform.
Click Next> to continue, then click Create Dependency to create the dependency.
The resulting hierarchy will look similar to the following:
Create the ERS Resource Hierarchy
- In the LifeKeeper GUI, click the icon to open the Create Resource Wizard. Select the “SAP” Recovery Kit.
- Enter the following values to create and extend a LifeKeeper resource (SAP-SPS_ERS20) to protect the ERS20 instance on node-a and node-b. Notice that this resource is being created on node-b and extended to node-a. Also note that the resulting resource should not be extended to node-c, the witness node. The icon indicates that the default option is chosen.
Create Resource Wizard | |
---|---|
Switchback Type | intelligent |
Server | node-b |
SAP SID | SPS |
SAP Instance for SPS | ERS20 |
IP child resource | none |
Automate dependent filesystem creation | no |
Dependent filesystem resource | none |
SAP Tag | SAP-SPS_ERS20 |
Pre-Extend Wizard | |
Target Server | node-a |
Switchback Type | intelligent |
Template Priority | 1 |
Target Priority | 10 |
Extend gen/app Resource Hierarchy Wizard | |
Root Tag | SAP-SPS_ERS20 |
Once the SAP-SPS_ERS20 resource has been successfully created and extended to node-a, the LifeKeeper resource panel should look similar to the following. Note that the names of the resources providing failover functionality for the ASCS and ERS virtual IP’s/hostnames may differ according to your chosen cloud platform depending on which subsection of Create ASCS and ERS Virtual IPs was followed.
- Right-click on the SAP-SPS_ERS20 resource and select Create Dependency… from the drop-down menu.
For Child Resource Tag, specify the root resource of the resource hierarchy being used to failover the ERS virtual IP/hostname. The precise resource name used in this step will depend on resources created in the subsection of Create ASCS and ERS Virtual IPs corresponding to your chosen cloud platform.
Click Next> to continue, then click Create Dependency to create the dependency.
The resulting hierarchy will look similar to the following:
The ASCS10 and ERS20 instances have now been successfully protected by LifeKeeper.
このトピックへフィードバック