SAP Landscape Management With Microsoft Azure
SAP Landscape Management With Microsoft Azure
1 /24
Table of Contents
4 EXECUTIVE SUMMARY
5 INTRODUCTION
5 SAP Landscape Management
8 SAP HANA Management with SAP Landscape Management 3.0
9 Key components of SAP Landscape Management
10 Deployment Models
10 Adaptive Design Principles
11 SAP Landscape Management Cloud
14 Microsoft Azure Adapter for SAP Landscape Management
14 SAP and Microsoft Alliance
15 SAP on Azure Virtual Machines
16 Hybrid Cloud with Azure
17 SAP HANA on Microsoft Azure
19 Integration with SAP Landscape Management
20 Microsoft Azure Adapter Roadmap
21 CUSTOMER SCENARIOS
21 System copy/clone/refresh
22 Microsoft Azure Templated Deployment
22 Relocate
23 PREPARATION REQUIREMENTS
24 CONCLUSION
24 REFERENCES
2 /24
3 /24
Executive Summary
SAP Landscape Management allows administrators to get a single pane of glass view of the status
of their entire SAP application landscape as well as the underlying infrastructure. It acts as a central
point of control and provides extensive automation capabilities intended to simplify the configura-
tion, provisioning, monitoring, and management of SAP applications/systems and associated
non-SAP applications and services. The managed environments can be either physical or cloud
based – private, public or hybrid cloud. However, this paper focuses on SAP application landscapes
running in Microsoft Azure cloud.
To extend the capabilities of SAP Landscape Management in the Microsoft Azure Cloud, SAP has
partnered with Microsoft to provide a complete end-to-end management of SAP application land-
scapes including HANA based systems. The combined solution provides our customers, busi-
ness and technical benefits that include:
• Greater operational continuity through centralized management, visibility and control of your en-
tire SAP landscape residing in Microsoft Azure Cloud using a single console.
• Reduced time, effort, and cost to manage and operate your SAP systems through automation
of time-consuming SAP Basis administration tasks.
• Increased operational agility through acceleration of application lifecycle management operations
and fast response to workload fluctuations.
• Additional Cloud Manager functionality in Microsoft Azure including:
- Deployment of VMs with Azure ARM templates by SAP Landscape Management
- Termination of VMs by SAP Landscape Management
- Copy across regions for managed disks
- Setup HSR across regions for managed disks
- Switch of managed disk types from Ultra/Premium to Standard and vice versa
- Relocate (Linux or Windows operating system as well as Azure storage)
- Support for SAP HANA on Microsoft Azure Virtual Machines
4 /24
Release 3.0 of SAP Landscape Management introduced SAP HANA management capabilities that
include provisioning and orchestration of SAP system and landscapes powered by SAP HANA, with
one-click operation of SAP HANA Takeover/ Failback and nZDM (near zero downtime mainte-
nance) scenarios.
SAP and Microsoft together provide an integrated support where incidents can be reported to SAP
Enterprise Support and can be handled without customers having to determine where the fault lies
(Microsoft support engineers are located at SAP support sites).
INTRODUCTION
SAP Landscape Management
SAP Landscape Management is an SAP product which helps customers to deploy, manage and au-
tomate SAP application landscapes in physical and virtualized data centers and cloud infrastruc-
tures.
From an administrator's perspective, SAP Landscape Management is the central tool that commu-
nicates with the application and infrastructure (virtualization layer and storage), and therefore the
complexity of the underlying infrastructure is hidden from SAP application administrators. In addi-
tion to creating SAP system copies, refreshes, and clones, SAP Landscape Management provides
extensive monitoring capabilities and controls for SAP system interaction (start, stop, relocate, and
so on).
5 /24
Some of the business challenges that SAP Landscape Management solves include improved flexi-
bility to relocate applications across servers and reduction of excessive coordination between
SAP application administrators and other infrastructure domains.
6 /24
The key use cases are shown in figure 3 and below are more details:
7 /24
SAP Landscape Management 3.0 introduced many new capabilities focused on management of
SAP HANA.
· Basic Operations
· Tenant Database Operations
· Setting up SAP HANA System Replication
· Create SAP HANA System Replication Tiers
· Manage SAP HANA System Replication
· Changing Replication Modes
· Enabling Column Table Preload
· Disable System Replication
· Assign Replication Status Repository (HA/DR Hooks)
· Update Replication Status Configuration
· Remove Replication Status Configuration
· Takeover & Near Zero Downtime Takeover
· Failback for SAP HANA System Replication
· Register Primary Tier as new Secondary Tier
· Near Zero Downtime Maintenance on (Non-)Primary Tier
· Near Zero Downtime SAP HANA Update on Primary Tier
· SAP HANA Update
· SAP HANA Client Update
· Move Tenant (optionally with Near Zero Downtime)
· Access SAP HANA Cockpit from SAP Landscape Management
· Destroy SAP HANA System Replication Tiers
· Provision Tenant Databases
· Copy a Tenant Database
· Refresh a Tenant Database
· Rename a Tenant Database
· System Provisioning
· Restore based refresh for SAP HANA
· Backint
· File-Based Backup
8 /24
The main involved components of SAP Landscape Management are shown in figure 4.
The SAP Host Agent needs to be installed on every managed host and includes the elements for
centrally managing and monitoring various aspects of the operating system. Through this SAP
Landscape Management can perform various operations such as discover, monitor, and provision
SAP systems in addition to several other operation tasks.
The SAP Adaptive Extensions compliment the SAP Host Agent and allow functions such as reex-
port NFS filesystems, manage virtual hostnames and Azure storage.
9 /24
Deployment Models
A prerequisite to using the Azure Connector with SAP Landscape Management is to ensure that
the managed systems are set up using the Adaptive Design Principles.
The mandatory principles are #1 and #2. Central User Management is recommended but it is
possible to operate without it for example in a test environment.
10 /24
In addition to the above described SAP Landscape Management solution, SAP launched an-
other product in the family called SAP Landscape Management Cloud (LaMa Cloud). These
two products complement each other and can operate either stand-alone or together in an in-
tegrated way.
11 /24
It is important to understand that SAP Landscape Management Cloud does not equate to the cloud
version of SAP Landscape Management. The table below highlights the key use cases for each
product to help customers decide which product to use.
When to use On-premise or hybrid SAP landscapes IaaS based SAP landscape and the need
and the need for SAP basis operations to reduce the TCO as well as getting an
automation SAP system centric view on the IaaS
costs of the SAP systems
12 /24
Figure 6: SAP Landscape Management, enterprise edition and SAP Landscape Management Cloud working together
Note that if customer does not have SAP Landscape Management, enterprise edition
managing the SAP landscapes in Azure, then a component known as “Execution Engine”
needs to run in Azure in lieu of SAP Landscape Management, enterprise edition. In this sce-
nario only the features of SAP Landscape Management Cloud are available.
13 /24
14 /24
The Microsoft Azure platform is a hyper-scale cloud services platform hosted and operated in Mi-
crosoft data centers. The platform includes the Microsoft Azure Virtual Machine Services (Infra-
structure as a Service, or IaaS) and a set of rich Platform as a Service (PaaS) capabilities.
The Azure platform reduces the need for upfront technology and infrastructure purchases. It simpli-
fies maintaining and operating applications by providing on-demand compute and storage to host,
scale and manage web application and connected applications. Infrastructure management is auto-
mated with a platform that is designed for high availability and dynamic scaling to match usage
needs with the option of a pay-as-you-go pricing model.
By choosing Microsoft Azure as your SAP certified cloud partner, you can reliably run your mission
critical SAP workloads on a scalable, compliant, cost-effective and enterprise-proven platform. With
the expanded partnership between Microsoft and SAP, you can run SAP applications across dev/
test and production scenarios in Microsoft Azure - and be fully supported.
On Microsoft Azure, customers have the option of running their SAP applications on Linux and/ or
Windows operating systems. The SAP Product Availability Matrix (PAM) should be consulted to find
out what operating systems are supported in Microsoft Azure for their SAP application and what
SAP Note is needed. SAP applications have been officially supported on Microsoft Azure Windows
VMs since 2014. As of May, 19 2016, SAP NetWeaver is officially supported on SUSE Linux VMs on
Azure. It should be noted that not all Operating Systems & Database combination listed in PAM is
supported on Microsoft Azure and therefore Microsoft websites listed in the reference section
should also be consulted.
Deployment of SAP application in Microsoft Azure can either be as new VMs provisioned or existing
VMs migrated from on premise to Azure cloud. Microsoft has multiple guides and tools to assist
with migration of existing VMs.
15 /24
Customers have the option of running their SAP landscapes in a hybrid cloud environment. This
gives the customer flexibility in placing applications in Azure or on-premise. The base assumption
is that SAP systems within one SAP landscape need to communicate with each other and with
many other software components deployed in the company, independent of their deployment
form.
There also should be no differences introduced by the deployment form for the end user
connecting with SAP GUI or other interfaces. These conditions can only be met when we have the
on-premises Active Directory/OpenLDAP and DNS services extended to the Microsoft Azure
instances through site-to-site/multi-site connectivity or private connections like Microsoft Azure
ExpressRoute.
16 /24
SAP HANA and Microsoft Azure are key components for the digital transformation of the over
200,000 organizations that run their line of business applications on SAP. The Cloud and SAP HANA
are inextricably related and the challenges, (as shown in below diagram) of the journey can be han-
dled by the power of Microsoft Azure and SAP HANA.
Figure 10: Meeting the need of cloud and HANA with Microsoft Azure
An up to date list of currently SAP certified machines can be found in SAP Note 1928533.
1928533 - SAP Applications on Azure: Supported Products and Azure VM types - SAP ONE Support Launchpad
A dedicated list of servers explicitly certified for running SAP HANA can be found here:
Certified and Supported SAP HANA® Hardware Directory
Microsoft Azure VMs are certified by SAP for SAP HANA scale-up and scale-out configurations. The
following operating systems are supported to deploy SAP HANA on Microsoft Azure:
- SUSE Linux Enterprise Server 12.x/15.x
- Red Hat Enterprise Linux 7/8
SAP Landscape Management on Azure also supports mixed installations where SAP HANA is running
on Linux and the application servers are running on Windows.
For NetWeaver based systems, Windows is also supported as OI for databases like MS SQL Server or
Oracle.
17 /24
The scenario of running SAP HANA on a Microsoft Azure VM as well as other components of the SAP
landscape are typically for the below cases:
a. Production systems
b. Development systems
c. Testing systems
d. Prototype systems
e. Learning / Demonstration systems
Deployments of SAP HANA can be Cloud-Only or Cross-Premises. The former refers to where
the Microsoft Azure subscription is not connected via a site-to-site or Expressroute connection to
the on-premises network infrastructure. On the other hand, the latter is a hybrid type environ-
ment as described in an earlier section. In short it refers to the scenario where VMs are de-
ployed to an Azure subscription that has site-to-site, multisite or Expressroute connectivity be-
tween the onpremises datacenter(s) and Microsoft Azure.
18 /24
The Microsoft Azure Adapter for SAP Landscape Management was developed by Microsoft to bring
the capabilities of standardized SAP application management to the Microsoft Azure Cloud. All the
functionality that is available in SAP Landscape Management and described earlier in this paper be-
comes available to be used on SAP landscapes including SAP HANA running in Microsoft Azure.
The adapter is built as a Java library and is bundled into the SAP Landscape Management applica-
tion. Once activated, actions that require interaction with the Microsoft Azure infrastructure can
now be handled by the adapter by making the necessary Microsoft Azure API calls. For example, an
SAP Basis administrator may choose a clone of an SAP system based on Microsoft Azure cloning
technology, SAP Landscape Management will do this via the Adapter.
The diagram below conceptually illustrates the solution and what can be accomplished with it.
Figure 12: The complete solution: SAP Landscape Management + Microsoft Azure Adapter/Connector
19 /24
The Azure Adapter for SAP Landscape Management at the time of publishing this whitepaper
is at SP19 and has the following capabilities:
* Microsoft Azure Adapter for SAP Landscape Management roadmap is owned by Microsoft
** There is no guaranty from Microsoft or SAP that these features will be delivered by the dates mentioned
*** This functionality is not GA yet. For more information refer to SAP Note 2815988 (only visible to preview customers). Open
an SAP incident on component BC-VCM-LVM-HYPERV and request to join the SAP Landscape Management storage adapter
for Azure NetApp Files preview
‡ Refer to SAP Note 2343511
20 /24
CUSTOMER SCENARIOS
Some sample customer scenarios that benefit from the combined SAP Landscape Management
and Microsoft Azure Adapter solution are described in the sections below. Note that there are
many use cases for SAP Landscape Management itself that do not depend on the Microsoft Azure
Adapter and are therefore not listed. All the scenarios below can be handled from the SAP Land-
scape Management interface.
System Copy/Clone/Refresh
Before we get into how the Microsoft Azure Adapter is leveraged for SAP system copy, clone or re-
fresh operations, it is important to understand the differences. The diagram shown below illus-
trates this.
Figure 13: SAP Landscape Management - SAP system clone, copy and refresh
As can be seen in the diagram for each of the above 3 options, the “Clone SAP system” (which is a
clone of the data representing the SAP system) is a step that is common. For any of the 3 options,
Microsoft Azure based cloning can be selected and SAP Landscape Management takes care of the
remaining steps that differentiate the procedures.
A Microsoft Azure based clone is done as a full clone, meaning there is a one to one copy of the
data – for example a 20GB data volume will be cloned to a new 20GB data volume.
21 /24
The Microsoft Azure adapter can deploy a template (existing customer created template in JSON
format) that defines the infrastructure and configuration of the Microsoft Azure based SAP land-
scape. By using a template, you can repeatedly deploy your solution throughout its lifecycle and
have confidence your resources are deployed in a consistent state.
A customer may have a need to provision and teardown SAP landscapes for training purposes. In
this scenario, Microsoft Azure templates would be created (by the customer) from a running envi-
ronment and then used to deploy additional environments. All the above would be done from the
SAP Landscape Management interface.
Relocate
SAP Landscape Management has a relocate feature that allows SAP instances to easily move be-
tween different hosts and different versions of operating system (refer to SAP Note 2427183). Cou-
pled with the Microsoft Azure Adapter it can perform this task more easily by leveraging Microsoft
Azure automation features. This capability can be applied when moving from one Azure instance to
another with same or different version of OS.
22 /24
PREPARATION REQUIREMENTS
The pre-requisites for SAP Landscape Management and Microsoft Azure Adapter to work together
are as below.
1. Dependencies
a. Recommendation is to have the latest SP
2. System Requirements for SAP Landscape Management (can be physical server or virtual ma-
chine)
a. Dependent on size of landscape to be managed
b. NetWeaver version – refer to SAP Product Availability Matrix
c. Refer to the sizing guide listed in reference section
d. Sample sizing table:
Category for Database
CPU Requirements Memory Requirements Disk Requirements
Enterprises Requirements
Small 3.200 SAPS 10 GB RAM 32 GB Disk 15 GB Database
(0-40 systems)
Medium 6.400 SAPS 20 GB RAM 64 GB Disk 32 GB Database
(40~80 systems)
Large 9.600 SAPS 30 GB RAM 96 GB Disk 50 GB Database
(80~120 systems)
X-Large Please contact SAP or your hardware partner
23 / 24
CONCLUSION
SAP Landscape Management is a powerful tool for Basis Administrators that give them ability to
efficiently manage application landscapes in a standardized way. Whether small or large SAP land-
scapes, tedious manual tasks are automated and significantly reduce errors and the time to complete.
SAP Landscape Management is positioned as a single pane of glass for the administrator allowing for
complete end to end operations in a standardized and SAP supported way.
With SAP applications running on Microsoft Azure Cloud, the power of SAP Landscape Management
is extended even further as Microsoft Azure infrastructure automation capabilities can be leveraged.
This allows real end-to-end management capabilities as many more automation tasks can be per-
formed at the infrastructure level. Azure Adapter for SAP Landscape Management 3.0 is the solution
to get deeper into the infrastructure layers and automate tasks that were not possible before.
Together, SAP Landscape Management and Microsoft Azure Adapter allow SAP Application Adminis-
trators to perform activities that would have traditionally required a team of different disciplines and
skill sets such as Microsoft Azure, SAP system, storage, OS and network administrators. Automation
is key to having an agile and robust application environment and this is achievable with the complete
end-to-end automation that SAP and Microsoft Azure provide.
REFERENCES
1. SAP Landscape Management – Product Page: https://www.sap.com/lama
2. SAP Landscape Management – Community Page: www.sap.com/lama-community
3. SAP Landscape Management – SAP Help Portal:https://help.sap.com/viewer/product/lama
4. SAP Landscape Management – Provisioning and Adaptive Design Principles
5. SAP Product Availability Matrix: https://apps.support.sap.com/sap/support/pam
6. Microsoft Azure Documentation: https://docs.microsoft.com/en-us/azure/
7. SAP on Microsoft Azure: https://azure.microsoft.com/en-us/solutions/sap/
8. SAP on Microsoft Azure (SAP Wiki):
https://wiki.scn.sap.com/wiki/display/VIRTUALIZATION/SAP+on+Microsoft+Azure
9. SAP HANA on Microsoft Azure:
https://docs.microsoft.com/en-us/azure/virtual-machines/workloads/sap/get-started
10. Certified IaaS Platforms for SAP HANA:
https://www.sap.com/dmc/exp/2014-09-02-hana-hardware/enEN/iaas.html#recordid=1819
24 / 24
www.sap.com/contactsap
(2021/07)
SAP and other SAP products and services mentioned herein as well as
their respective logos are trademarks or registered trademarks of
SAP SE (or an SAP affiliate company) in Germany and other countries.
All other product and service names mentioned are the trademarks of
their respective companies.