Summary of SAP Partner integrations with SAP Landscape Management 2.x/3.x

SAP Landscape Management (LaMa, formerly known as LVM) provides three main integration points for SAP Partner Technologies:

  1. Virtualization and Cloud

    • What: Integration into Virtual Machine (VM) or Cloud management infrastructure
    • Purpose: To manage, migrate, visualize and perform “VM-based clone”.
    • Note: A “VM-based clone” replicates data via the virtualization technology; Prerequisite is that all data is on virtual disks, e.g. “vmdk” 
  2. Storage

    • What: Integration into shared/centralized storage management infrastructure
    • Purpose: To relocate adaptively installed SAP Systems and perform “Storage-based clone”.
    • Note I: A “Storage-based clone” replicates data directly via Storage based cloning and/or snapshot technologies
    • Note II: LVM 2.x also offers a “custom clone/provisioning” interface to easily integrate scripts which can perform the data replication step within the LVM End-to-End process. This can be used for technologies not listed below, e.g. different storage, OS, use of backup/restore infrastructure.
  3. Management/Orchestration (“External Interfaces”)

    • What: Integration with generic higher-level Management/Orchestration Software
    • Purpose: To allow generic Management/Orchestration Software tools to control LVM operations

Below is a high-level summary of what SAP Partners are supporting with SAP NetWeaver Landscape Virtualization Management 2.x/3.x For the official, detailed documentation of these SAP Partner integrations, please see the sections below and follow the links.


  1. Microsoft Azure

    • Further/detailed information
  2. Amazon AWS

    • Further/detailed information
      • There are two adapters, one virtualization adapter and one storage adapter
      • SAP Notes 2251474 and 1861561
      • Supported functions : Start/Stop/Monitoring/Clone/Copy
      • Provisioning is supported since LVM 2.1 SP5 with the new Storage Adapter for AWS EBS Storage


  1. Microsoft Hyper-V

    • Further/detailed information:
    • Supported OS’s
      • Windows
  2. VMware vSphere
  3. IBM PowerVM


  1. EMC (NFS)

  2. EMC (SAN/Fiber Channel)

  3. Hitachi/HDS

    • Further/detailed information:
    • Supported OS’s
      • AIX [supported on a per project basis]
      • RHEL (Physical and VMware) [supported on a per project basis]
      • SLES (Physical and VMware) [supported on a per project basis]
      • Windows (Physical and Hyper-V) [supported on a per project basis]
  4. HPE

    • Further/detailed information:
      • HP 3Par , HP XP7 and HP XP P9500 storage
      • P2P, P2V, V2P and V2V operations
      • SAP SCN Page: HP
    • Supported OS’s
      • Windows (Physical and VMware)
      • RHEL
      • SLES
      • HP-UX
  5. IBM

  6. NetApp (NFS)

  7. NetApp (SAN/iSCSI)

  8. NetApp (SAN/Fiber Channel)


P2P = Physical-to-Physical

P2V = Physical-to-Virtual

V2P = Virtual-to-Physical

V2V = Virtual-to-Virtual (i.e. relocate from VM to another VM, not the same as “migrate”)