SAP Landscape Management 3.0, Enterprise Edition

System Provisioning Concepts

This section provides an overview of the system provisioning concepts, such as clone, copy, refresh, or rename.



System Provisioning Concepts

System Clone

A system clone is a duplicate of an existing system with an identical system ID. To avoid conflicts with the original system, the cloned system is isolated from the rest of the landscape.

Cloned systems provide a way to test your systems safely and without interrupting user access to your existing systems.

System cloning is storage and/or virtualization integration dependent.
  • Storage based:

    You clone system and database at storage volume level.

    All SAP components including the database files are installed on shared filesystems. SAP Landscape Management connects to the storage system and initiates a storage based copy of the data. SAP Landscape Management mounts the copy to a new compute node, including isolation on operating system level.

  • Virtualization based:

    You clone the entire virtual machines the system is running on.

    All SAP components including the database files are installed inside a virtual machine using virtual disks. SAP Landscape Management connects to the hypervisor manager and initiates a full virtual machine clone including isolation on operating system level.

  • Custom:

    You use any technology to clone your source system or a standby database.

    You create new, or use an existing set of scripts to clone the source system or a standby database.

System Copy

A system copy is a duplicate of an existing system with a different host name and a unique system ID. SAP Landscape Management creates a copy of an existing system and renames the copy.

System Refresh

You refresh a system to overwrite an existing target system with the latest data from a source system while maintaining the configuration.

System Rename

You change system ID, host names, instance numbers, and mount points from the source system to the target system.