Skip to main content
NetApp Solutions SAP

SAP LaMa provisioning workflow - clone system

Contributors kevin-hoke
PDFs

The following figure highlights the main steps executed with the system clone workflow.

Workflow diagram containing the steps Storage Cloning, Prepare System, Activate Isolation, and Start System.

In this section, we go through the complete SAP LaMa system cloning workflow based on the source SAP system HN9 with HANA database H09. The following picture gives an overview of the steps executed during the workflow.

This image depicts the steps executed during the workflow, including Create Cloned System Configuration, Create Storage Snapshot and Clone, Create Mount Point Configuration, Set Custom Properties, and Prepare and start system.

  1. To start the cloning workflow, open Provisioning in the menu tree and select the source system (in our example HN9). Then start the Clone System wizard.

    This screenshot depicts the Provisioning System View. It contains two Systems.

  2. Enter the requested values. Screen 1 of the wizard asks for the pool name for the cloned system. This step specifies the instances (virtual or physical) on which the cloned system will be started. The default is to clone the system into the same pool as the target system.

    Clone System Wizard Screen 1 for providing basic data of target system.

  3. Screen 2 of the wizard asks for the target hosts that the new SAP instances are started on. The target hosts for this instance(s) can be selected out of the host pool specified in the previous screen. Each instance or service can be started on a different host. In our example, all three services run on the same host.

    Clone System Wizard Screen 2 provides host selection of the target system.

  4. Provide the information requested in screen 3, which asks for virtual host names and networks. Typically, the host names are maintained in DNS, so the IP addresses are prepopulated accordingly.

    Clone System Wizard Screen 3 enables to you provide Virtual Host Names and Networks.

  5. In screen 4, the custom clone operations are listed. A clone and a SnapPostfix name are provided, which are used during the storage clone operation for the FlexClone volume and Snapshot name, respectively. If you leave these fields empty, the default value configured in the variable section of the provider script netapp_clone.sh is used.

    In Clone System Wizard Screen 4, custom clone options are listed as are the operation parameters.

  6. In screen 5, the database consistency option is selected. In our example, we selected Online: Clone running DB.

    In Clone System Wizard Screen 5, Database consistency options are listed with Online: Clone running DB selected.

  7. In screen 6, input is only required if you perform a tenant clone.

    In Clone System Wizard Screen 6, you can provide username and password if you are performing a tenant clone.

  8. In screen 7, system isolation can be configured.

    In Clone System Wizard Screen 7, you can define allowed outgoing connections for system isolation.

  9. In screen 8, a summary page contains all the settings for final confirmation before the workflow is started. Click Execute to start the workflow.

    Clone System Wizard Screen 8 provides a summary of entered information.

    SAP LaMa now performs all the actions indicated in the configuration. These actions include creating the storage volume clones and exports, mounting them to the target host, adding the firewall rules for isolation, and starting the HANA database and SAP services.

  10. You can monitor the progress of the clone workflow under the Monitoring menu.

    T"his screenshot depicts the Monitoring screen for the System clone process."

    Within the detailed log, the operations Clone Volume and Modify Mountpoints and add Custom Properties are executed at the Ansible node, the sap-jump host. These steps are executed for each service, the HANA database, the SAP central services, and the SAP AS service.

    This screenshot depicts the System clone screen showing various operations depicted in the detailed log.

  11. By selecting the Clone Volumes task the detailed log for that step is displayed and the execution of the Ansible Playbook is shown here. You can see, that the Ansible playbook netapp_lama_CloneVolumes.yml is executed for each HANA database volume, data, log, and shared.

    This screen depicts the logs detailing volume clone.

  12. In the details view of the step Modify Mountpoints and add Custom Properties, you can find information about the mount points and the custom properties handed over by the execution script.

    More log information

After the workflow has been completed, the cloned SAP system is prepared, started, and ready for use.