Skip to main content
NetApp Solutions SAP

Overview of SAP system clone workflow with SnapCenter

Contributors netapp-nbauer kevin-hoke
PDFs

As discussed in the previous section, SnapCenter can manage clones of data sets from any existing Snapshot backup and can rapidly provision these data sets to any target system. The flexible and agile provisioning of production data to a repair system to address logical corruption is critical, since it is often necessary to reset the repair system and to choose a different production data set. FlexClone technology enables a rapid provisioning process, and provides significant capacity savings, since the repair system is typically only used for a short time.

The figure below summarizes the required steps for an SAP system clone operation using SnapCenter.

  1. Prepare the target host.

  2. SnapCenter clone create workflow for the SAP HANA shared volume.

  3. Start SAP HANA services.

  4. SnapCenter clone create workflow for the SAP HANA data volume including database recovery.

  5. The SAP HANA system can now be used as a repair system.

If the system is not needed anymore, the clean-up process is performed with the following steps.

  1. SnapCenter clone delete workflow for the SAP HANA data volume including database shutdown (when using the automation script).

  2. Stop SAP HANA services.

  3. SnapCenter clone delete workflow for the SAP HANA shared volume.

Note If you must reset the system to a different Snapshot backup, then step 6 and step 4 are sufficient. A refresh of the SAP HANA shared volume is not required.

Figure showing input/output dialog or representing written content

The section “SAP system clone with SnapCenter” provides a detailed step-by-step description of the system clone workflow.