Skip to main content
NetApp Solutions SAP

SAP LaMa provisioning workflow - system refresh

Contributors kevin-hoke
PDFs

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

This image depicts a timeline of the steps in the system refresh workflow. It contains Export configuration, stop system, unprepare system, delete storage clone, storage cloning, prepare system, activate isolation, system rename, start system, import configuration, post copy automation, and deactivate isolation.

During the refresh workflow, the storage clone must be deleted. You can use the same Ansible playbook as for the system destroy workflow. However, the custom hook is defined to a different step, so the playbook is named accordingly. The process step for the clone doesn´t differ.

This image shows an architectural diagram that includes the steps contained within this workflow.

The refresh workflow can be triggered through the provisioning screen for a copied system.

This screenshot shows the Provisioning system view with the Refresh system dropdown highlighted.

Again, nothing differs in the input screens from the standard, and the workflow execution can be started from the summary screen.

This screenshot shows the Refresh System screen, including Basic Data of System to be refreshed and the host selection of the target system.