You can set up the SAP Recovery Kit through the use of the LKCLI (Command Line Interface).
Terminology
- Switchback Type – This dictates how the SAP instance 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 instance back to the primary/original server. Automatic switchback means the switchback will occur as soon as the primary server comes back on line and re-establishes LifeKeeper communication paths.
- IP Tag – This represents the IP resource that will become a dependent of the SAP resource hierarchy.
- Protection Level – The Protection Level represents the actions that are allowed for each resource.
- Recovery Level – The Recovery Level provides instruction for the resource in the event of a failure.
- Additional SAP Dependents – This value represents the LifeKeeper SAP resource tag that will become a dependent of the current SAP resource being created.
You can set up the SAP Recovery Kit through the use of the LKCLI (Command Line Interface).
Creating/Extending the SAP resource from the Command Line
create sap
EXAMPLE: #lkcli resource create sap --tag <tag> --sid <SAP SID> --instance <SAP instance> --switchback <switchback type> --protection_level <FULL | STANDARD | BASIC | MINIMUM> --recovery_level <FULL | REMOTE | LOCAL | OFF> --ip <IP tag> --dependent_cs <SAP central service tag> --dependent_fs <FS tags> --automate_fs_creation
| Option | Default | Description |
|---|---|---|
| --sid <str> | SID for the SAP installation. | |
| --instance <str> | SAP instance (e.g., ASCS10). | |
| [--protection_level <FULL|STANDARD|BASIC|MINIMUM>] | FULL | Protection Level for the protected SAP resource. |
| [--recovery_level <FULL|REMOTE|LOCAL|OFF>] | FULL | Recovery Level for the protected SAP resource. |
| [--ip <str>] | LifeKeeper IP resource tag protecting the virtual IP for the given SAP instance. The IP resource must be in-service on the server where the SAP resource is being created. A comma-separated list of IP resource tags is allowed for this parameter. The IP resources specified by this argument will become child resources of the SAP resource. | |
| [--dependent_fs <str>] | A comma-separated list of LifeKeeper resource tag(s) for the file system (gen:filesys) or NFS (gen:nfs) resource(s) protecting the file system(s) associated to the given SAP instance. (e.g., /sapmnt,/usr/sap/SID/ASCS10). All given resources must be in-service on the server where the SAP resource is being created. The file system and/or NFS resources specified by this argument will become child resources of the SAP resource. Note: This parameter cannot be used in conjunction with the --automate_fs_creation parameter. | |
| [--dependent_cs <str>] | LifeKeeper SAP resource tag for a central services resource (e.g., ASCS10) to be added as a child of the SAP resource being created. The given central services resource must be in-service on the server where the SAP resource is being created. Note: This parameter may be applicable when creating a resource to protect a PAS instance. See the “Create the Primary Application Server Resource” section of Creating an SAP Resource Hierarchy for more information. | |
| [--automate_fs_creation] | During SAP resource creation, LifeKeeper will scan the existing SAP directory structures and attempt to automatically create appropriate LifeKeeper resources to protect any shared file system mounts that it finds. Any resources that are created during this process will become children of the SAP resource. Inspect the resulting hierarchy for accuracy once the process completes. Notes: Replicated file system hierarchies cannot be created automatically by this process. This parameter cannot be used in conjunction with the --dependent_fs parameter. |
extend sap
EXAMPLE: #lkcli resource extend sap --tag <tag> --dest <backup node> --switchback <switchback type> --template_priority <priority> --target_priority <priority>
config sap
EXAMPLE: #lkcli resource config sap --tag <tag> --sshcc_action <start | stop | migrate [:<node>] | maintenance:<enable | disable | check> --protection_level <FULL | STANDARD | BASIC | MINIMUM> --recovery_level <FULL | REMOTE | LOCAL | OFF>
| Option | Default | Description |
|---|---|---|
| [--protection_level <FULL|STANDARD|BASIC|MINIMUM>] | Update the Protection Level for the protected SAP resource. This command must be run on the server where the SAP resource is currently in-service. | |
| [--recovery_level <FULL|REMOTE|LOCAL|OFF>] | Update the Recovery Level for the protected SAP resource. This command must be run on the server where the SAP resource is currently in-service. | |
| [--sshcc_action <start|stop|migrate[:<node>]|maintenance:<enable|disable|check>>] | Perform an SAP SIOS HA Cluster Connector (SSHCC) action. This command must be run on the server where the SAP resource is currently in-service. The possible values of this parameter are: start – Bring the SAP resource in-service via the HA cluster connector. stop – Take the SAP resource out-of-service via the HA cluster connector. migrate[:<node>] – Migrate the SAP resource to a different server. Optionally, a target migration server may be provided by adding “:<hostname>” to the migrate parameter (e.g., lkcli resource config sap --tag SAP-SID_ASCS10 --sshcc_action migrate:node2). If no target migration server is explicitly provided, the HA cluster connector will attempt to determine the best target server based on current cluster conditions. maintenance:<enable|disable|check> – Enable, disable, or check the status of SAP Maintenance Mode for the hierarchy containing the given SAP resource. |
Post your comment on this topic.