Installation process overview SAP Landscape Virtualization Management (SAP LVM)
In this document i will give you an overview of the installation process, the requirements and
initial configuration of SAP LVM.
You can find additional detailed information in the Configuration and Deployment section of
You can click on any of the pictures below to get a larger view !
Lets start with an overview of the main components:
SAP LVM is a Java based add-on that is installed on a Java Application Server
We use the SAP Host Agent to connect and control SAP Instances
We use adapters for storage and virtualization to connect to the infrastructure and enable copy processes
This picture gives you an overview of the steps that are required to complete the whole process
The initial system setup and basic configuration are always required and will enable you to do basic
management functions like start/stop ,system overview , scheduling and so on.
If you want to use the system provisioning features you also need to complete the infrastructure config
In the extended configuration section i will show you how to adapt LVM to your environment
Lets get started, the next steps are all done on the System where you install SAP LVM
Now we move to the hosts where your SAP Systems are running
SAP LVM requires the SAP Host Agent to connect to the SAP systems in your landscape and to control them
Please make sure that your SAP Host Agent is on the latest patch level to avoid problems
Now we are moving to the SAP LVM management GUI. The default URL for logging in, should look like this
We start with the configuration of a pool. Pools is a way to group systems. Since it is possible
to run functions like start/stop both on system and pool level you should group systems in a way that allow
you to manage them in an easy way. E.g. productive vs. test systems
In the next step you add your hosts and systems to LVM. This is done via the "Discover" button under the
"Hosts" and "Systems" section of the "Configuration" tab.There are a couple of ways to discover your
hosts and systems:
Detect using host and instance agent: Here you can give a host name or ip address or a range of ip-addresses
and LVM will try to connect and use the SAP Host Agent to discover which instances are installed.
Virtualization Manager: LVM will connect to the virtualization management software and retrieve the list of
hosts and will connect to SAP Host Agents to discover which instances are installed.
Landscape scanner: The Landscape Scanner is a background process that continuously scans the known
Network for new systems and will notify you if it finds something. You can then decide if you want to add the
found systems to SAP LVM.
System Landscape Directory: LVM will connect to the SLD and get the configuration information from there
This will only work if your SLD accurately represents your current Landscape.
For system discover you use the same procedure.
During System configuration, LVM will show you the configured filesystems.
It is very important to make sure that this information is accurate. LVM uses
this information to determine which filesystems to copy.
At this stage you have a configured SAP LVM and can start to use it for basic management functions.
Next we will look into the Infrastructure Configuration needed for an End to End system copy process
Networks are a way to group your different Network segments. You have to configure some parameters
like ip range, broadcast address and so on. Each system needs to be configured for one of your networks
The storage manager is needed if you want to use a "storage based cloning" procedure. The storage
adapter connects to the storage management Software and controls the replication of the data volumes
needed for a clone/copy/refresh process. If you are using virtualization and your data resides on virtual disks
you configure the virtualization adapter under "Virtualization Managers"
During a copy process, LVM is able to create the users needed for the copied system. For this to work
you need to configure the user management service. We support LDAP,NIS,Active Directory. It is possible
to leave this out, but you then need to manually pre-configure the users needed in your user managment
Similar to the user management , LVM can handle the assignment of virtual hostnames/ip addresses
automatically and you can configure the DNS servers here. Here it is also possible to leave it out, but
you need to manually manage the relationship between hostnames and ip addresses.
System rename is needed as part of the overall process and requires a so called release configuration. This
is a SWPM specifically for a release/platform combination.You can download SWPM as part of the
SL Toolset.Software Logistics Toolset (SL Toolset) – SAP Help Portal Page You should create a shared
filesystem that can be mounted on all of your hosts. LVM will automatically mount this filesystem on the
target host to execute the system rename. In this configuration you point LVM to the shared filesystem.
The JAVA Post Copy Automation is required to rename a JAVA based instance. This is a standalone tool
that you install on a Linux or Windows based server in your Landscape. It runs a web service that LVM uses
to make the necessary changes on the JAVA stack
The ABAP Post Copy Automation is installed inside your ABAP source system. Depending on the release
level of your source system most of the content will already be installed. Please check the SAP notes to see
what you need to do to get it to the most current version.
You will find more details here: https://scn.sap.com/docs/DOC-43270
For customizing SAP LVM to your requirements and environment please go to:
At this point you should have a fully configured SAP LVM.
SAP LVM installation guide: Guide
SAP LVM provisioning Best Practices: Guide
SAP LVM online help : http://help.sap.com/nwlvm
SAP LVM customization: SAP Landscape Virtualization Management (LVM) Overview of Customization Options