Performing Provisioning

The features of system provisioning are as follows:

• All possible system provisioning options are available via Provisioning → System and AS.

• Virtual Host provisioning is possible via Provisioning → Virtual Host.

• Provisioning options for system provisioning have to be enabled explicitly in the system configuration, as outlined in the previous figure.

• No validation issues in SAP Landscape Management with the hosts, systems, and instances that you want to use

• No alerts on the instances that you want to use

• You can log on to the source system

• Comply with all prerequisites described in SAP Note 1709155 - System Provisioning with SAP Landscape Virtualization Management

• The system can be used for cloning — the initial entities and provisioning setup procedure are configured

• Configured repository

• The source system must be installed on a shared storage system.

• The target resource must match all prerequisites for a relocation of adaptively installed systems.

• The corresponding storage manager is configured.

• The system to be cloned must be installed into a VM that is managed by a virtualization provider.

• The VM itself must be registered with SAP Landscape Management.

• The corresponding virtualization provider is registered with SAP Landscape Management and supports VM cloning.

• The SAP HANA systems and ABAP on SAP HANA systems are adaptively installed and configured.

• You can use a compatible version of the SAP HANA lifecycle management tool (hdblcm) with used revision.

• The version of the ABAP kernel is compatible with the SAP HANA version.

• A compatible SAP HANA 1.0 (or higher) client with the SAP HANA system is installed on the host where the SAP ABAP application servers are running.

• For SAP HANA single-node standalone systems and ABAP based application systems on SAP HANA single-node, you need at least SAP Host Agent 7.20 SP 191 or above.

• For SAP HANA multi-node systems, you need the latest SAP Host Agent 7.21.

• Comply with all prerequisites described in SAP Note 2050537 - Support for SAP HANA in SAP Landscape Management.

• The SAP Host Agent must be able to write to the operations.d subfolder.

  If this is not possible, because it is a mounted NFS share, extract the latest patch of the SAPACEXT.SAR as per SAP Note 1759181 – Information into this share.

You can create an identical clone of the source system with the following features:

• Same SID.

• Isolated from the rest of landscape.

The following approaches are available for cloning:

• Storage-based cloning.

• Virtualization-based cloning.

• Custom cloning.

The figure, Copy System, shows some of the required screens in the system, required for the system copy.

You can create a copy of an existing source system with the following features:

• Different SID.

• Different hostname.

• Clone source system.

• Rename cloned system.

• Post-copy automation.

• With a refresh, you can overwrite an existing target system with the latest data from a source system while maintaining the configuration.

• For ABAP systems, the following occurs:

  • SAP Landscape Management exports the target system tables that contain configuration information before starting the system refresh. This prevents it from overwriting the target system configuration.

  • After the system refresh has finished, SAP Landscape Management imports the configuration information into the target system.

• For Java systems, the following occurs:

  • Use the Java post-copy configuration wizard to export target system tables that contain configuration information before starting the system refresh. This prevents it from overwriting the target system configuration.

  • After the system refresh has finished, you can use the Java post-copy wizard to import the configuration information into the target system.

Refresh your system with current data of your Prod system, for example.

The system refresh consists of the following:

• Export configuration data of target system.

• Refresh of target system.

• Import of configuration data.

• You can refresh a database to keep the configuration settings of your application instances, such as central instance (CI), dialog instance (DI), and so on.

• For storage based systems, the following occurs:

  • Mount points containing the database logs, data, and software are only configured for the database instance and must not be shared with any other instances of the system.

  • Install the database client software on a separate volume if it is needed by the SAP application servers.

• For virtualization based systems, the database is installed on a separate virtual machine.

Refresh a database to keep the configuration settings of your application instances such as central instance (CI) and dialog instance (DI).

A system refresh consists of the following:

• Export configuration data of target system.

• Refresh of target system.

• Import of configuration data.

The following are examples for refreshing a database:

• Storage-based.

• Custom provisioning.

The figure, Performing Provisioning: Refresh Database (Storage Based), shows an example of a system provisioning, following the formula: Refresh database (storage based) = export + system copy + import

Note that for a storage-based refresh database, the functionality can vary according to SAP partner integration.

• You can perform a restore-based refresh for a system with SAP HANA databases using a complete database backup from the source system.

• For storage based systems, the following applies:

  • Mount points containing the database logs, data, and software are only configured for the database instance and must not be shared with any other instances of the system.

  • Install the database client software on a separate volume if it is needed by the SAP application servers

• For virtualization-based systems, the database is installed on a separate virtual machine.

• You can refresh the SAP HANA database of the system but keep the configuration settings of your application instances such as central instance (CI), dialog instance (DI), and so on.

Refresh the SAP HANA database of the system, but keep the configuration settings of your application instances such as central instance (CI), dialog instance (DI), and so on.

The prerequisite is a backup share. For example, an NFS share is configured on the source system, and you can mount it on the target system.

To replace or add additional custom provider implementation definitions to the storage or rename step during system provisioning, you can configure custom provisioning processes.

You can replace the following operations for storage cloning on the source or target system:

You can perform the following:

• Create a provider implementation definition, for example, a script registered with host agent.

• Create a custom provisioning process and replace the corresponding step.

You can rename a system to change the system ID, host names, instance numbers, and mount points from the source system to the target system. The following applies:

• You can rename cloned or copied systems only.

• After renaming, your source system is no longer available.

• It manages the renaming of mount points.

SAP Landscape Management enables you to install or uninstall application servers via predefined roadmap steps.

SAP Landscape Management automatically adds the new installed application server to the corresponding system.

The Diagnostics Agent is a central component of the SAP Solution Manager system landscape and the remote component of end-to-end root cause analysis.

SAP Landscape Management enables you to install or uninstall Diagnostic Agents via predefined roadmap steps.

You can execute post-copy automation (PCA) standalone to carry out several configuration steps on a system, which was not provisioned by SAP Landscape Management.

You can use post-copy automation for the use cases shown in the previous figure.

SAP Landscape Management supports several SAP HANA-specific operations. System replication is a mechanism for ensuring the high availability of your SAP HANA system, as follows:

• The continuous replication of data from a primary to a secondary system, including in-memory loading, system replication, facilitates rapid failover in the event of a disaster.

• Productive operations can be resumed with minimal downtime.

• SAP HANA system replication is a prerequisite for SAP HANA operations such as nZDM or takeovers.

The figure, Provisioning Blueprints, shows the use of provisioning blueprints in UI5.