Microsoft - Azure LAMA Whitepaper

SAP Landscape Management with Microsoft Azure
November 2017
Whitepaper
Contents
2 Executive Summary ......................................................................................................................... 2

3 Introduction .................................................................................................................................... 3
3.1 SAP Landscape Management ................................................................................................... 3
3.2 SAP HANA Management with LaMa 3.0 .................................................................................... 7
3.3 Microsoft Azure Adapter for LaMa ........................................................................................... 9
3.3.1 SAP and Microsoft Alliance ............................................................................................. 10
3.3.2 SAP on Azure Virtual Machines ....................................................................................... 11
3.3.3 Hybrid Cloud with Azure ................................................................................................. 12
3.3.4 SAP HANA on Microsoft Azure ........................................................................................ 13
3.3.5 Integration with LaMa .................................................................................................... 16
3.3.6 Microsoft Azure Adapter Roadmap* ............................................................................... 17
4 Customer Scenarios ....................................................................................................................... 17
4.1.1 System Copy/Clone/Refresh ........................................................................................... 17
4.1.2 Microsoft Azure Templated Deployment ........................................................................ 18
4.1.3 Relocate ......................................................................................................................... 19
5 Potential Enhancements ................................................................................................................ 20
5.1 SAP HANA Large Instances on Microsoft Azure ....................................................................... 20
5.2 Use Case: Microsoft Azure Adapter for SAP HANA Large Instances ......................................... 23
6 Preparation Requirements ............................................................................................................. 24
7 Conclusion ..................................................................................................................................... 25
8 References..................................................................................................................................... 25
1 Executive Summary
Adoption of cloud computing by SAP customers is on the rise due to the cost reduction and business
agility improvements that this brings. SAP applications are increasingly being run in private, public or
hybrid clouds. An increasing number of SAP customers are opting to use Microsoft Azure for their public
cloud needs. To help customers with deployment and management of applications running in Microsoft
Azure, SAP offers the product SAP Landscape Management (also known as LaMa) and Microsoft has
developed a Microsoft Azure adapter for it.
© 2017 SAP SE or an SAP affiliate company. All rights reserved 2

LaMa 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 configuration, 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 LaMa in the Microsoft Azure Cloud, SAP has partnered with Microsoft to
provide a complete end-to-end management of SAP application landscapes including HANA based
systems. The combined solution provides our customers business and technical benefits that include:
• Greater operational continuity through centralized management, visibility and control of your
entire 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 MS Adapter functionality in Microsoft Azure including:
o Microsoft Azure Template deployment
o Relocate (Linux or Windows operating system as well as Azure storage)
o Support for SAP HANA on Microsoft Azure Virtual Machines
Release 3.0 of LaMa has 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 maintenance) scenarios.
SAP and Microsoft together provide an integrated support where incidents can be reported to SAP
Enterprise Support and can be handled without customer having to determine where the fault lies
(Microsoft support engineers are located at SAP support sites).
2 Introduction
2.1 SAP Landscape Management
SAP Landscape Management (LaMa) is a SAP product which helps customers to deploy, manage and
automate SAP application landscapes in physical and virtualized data centers and cloud infrastructures.
From an administrator's perspective, LaMa is the central tool that communicates with the application
and infrastructure (virtualization layer and storage), and therefore the complexity of the underlying
infrastructure is hidden from SAP application administrators. In addition to creating SAP system copies,
refreshes, and clones, LaMa provides extensive monitoring capabilities and controls for SAP system
interaction (start, stop, relocate, and so on).

SAP Landscape Management*
DEV QAS PRD
SAP Applications
non-SAP Apps
3rd Party Tools

S/4HANA | CRM | ERP | BW | SCM
Operating System and Database

RHEL | Windows | AIX | HANA | Any DB
IT Infrastructure
Virtualization | Storage | Network | Server
On-Premise | Cloud | Hybrid
Figure 1: SAP Landscape Management (LaMa) – *Formerly SAP Landscape Virtualization Management
Some of the business challenges that LaMa solves include improved flexibility to relocate applications
across servers or cloud environments and reduction of excessive coordination between SAP application
administrators and other infrastructure domains.
Key features of LaMa:
· Provisioning SAP Systems:

o Automate SAP system provisioning activities such as system clone/copy/refresh
o Provision SAP systems with one-click through templates
· Landscape Management:
o Landscape-wide visibility and control
o Centralize landscape operations
· Design & Extensibility:
o Tailor it to your specific needs
o Integrate your own procedures
o Custom Processes

* Near Zero Downtime (nZDM)
** Rolling Kernel Switch (RKS)
Figure 2: SAP Landscape Management (LaMa)
Some new capabilities introduced with LaMa 3.0 cover support of SAP HANA environments as below:
· Simplified provisioning and management of SAP HANA Multi-Tenant Database Container (MDC)
setups
· Fully automated SAP system refresh procedure for SAP HANA using backup and restore
· Fully automated procedure to setup and monitor SAP HANA System Replication
· Fully automated procedure for nZDM Takeover and Failback for SAP HANA
· Near Zero Downtime (nZDM) maintenance for SAP HANA (e.g. facilitating OS updates, SAP HANA
upgrades, Hardware maintenance)

Figure 3: Managing SAP Landscape Powered by HANA -- *Near Zero Downtime (nZDM)
When an SAP system copy is performed, a series of manual tasks (inside the SAP system pertaining to
NetWeaver and Application components) need to be performed that can take several days to complete.
With LaMa Post Copy Automation (PCA) the manual tasks are fully automated and can reduce the time
needed significantly (depending on size) and correspondingly reducing the labor intensive manual
efforts. Moreover, this results in standardized operations ensuring that SAP system refreshes are done
consistently unlike the manual methods that tend to be different each time and error prone.
Figure 4: SAP system clone, copy & refresh

The table below outlines common use cases for LaMa.
Use Case Benefits

SAP System clone, copy, and · Reduced administrative time
refresh · Greater agility
· Standardized - fewer errors, greater efficiency
· Personnel released for other tasks
Landscape Visualization · Improved availability
· Improved incident response
· Reduced management time
· Easier system optimization
Operation Automation · Reduced management time
· Reduced management cost
Third-party support and · Administrative flexibility and efficiency
extensibility (e.g. integration
with MS Azure)
Other benefits · Ease of deployment
· Faster time to value
· Less training required
2.2 SAP HANA Management with LaMa 3.0
LaMa 3.0 introduced many new capabilities focused on management of SAP HANA. A key feature in this
area is around SAP HANA High Availability and Disaster Recovery management. Diagrams below
illustrate how LaMa can help a Basis Administrator to takeover or failback a HANA based environment.
Figure 5: SAP HANA Replication Setup with LaMa

Figure 6: SAP HANA Takeover
Figure 7: SAP HANA nZDM Takeover

Figure 8: SAP HANA Failback
Figure 9: SAP HANA nZDM Maintenance
2.3 Microsoft Azure Adapter for LaMa
To support customers on their journey into a cloud model (hybrid or entirely public cloud), SAP and
Microsoft partnered to create an adapter that integrates the SAP management capabilities of LaMa with
the IaaS advantages of Microsoft Azure.

Many SAP customers are running their applications on Microsoft Azure infrastructure and some are
already using LaMa to manage such landscapes. However, they do not get the full infrastructure
automation capabilities that Microsoft Azure provides. To make available the powerful infrastructure
automation capabilities of Microsoft Azure within LaMa, an adapter was built by Microsoft and is
shipped with LaMa. This adapter can be leveraged by the administrator via the LaMa dashboard and
allows a real end to end automation covering the entire stack of SAP application and the infrastructure.
Before getting into the details of the adapter we will first cover some basics of running SAP applications
in Microsoft Azure regardless of using LaMa.
2.3.1 SAP and Microsoft Alliance
Microsoft and SAP have a strong partnership going back several years. It helps organizations use the
cloud to drive innovation, agility and enable new ways to work. By aligning and integrating solutions, the
alliance empowers businesses to reason over vast quantities of data and create systems of intelligence
that they can use to dramatically improve their customer engagement, employee productivity, business
operations and product development to give the end user unprecedented insight, convenience and
agility.
Figure 10: SAP and Microsoft

2.3.2 SAP on Azure Virtual Machines
The Microsoft Azure platform is a hyper-scale cloud services platform hosted and operated in Microsoft
data centers. The platform includes the Microsoft Azure Virtual Machine Services (Infrastructure as a
Service, or IaaS) and a set of rich Platform as a Service (PaaS) capabilities.
The Azure platform reduces the need for up-front technology and infrastructure purchases. It simplifies
maintaining and operating applications by providing on-demand compute and storage to host, scale and
manage web application and connected applications. Infrastructure management is automated 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 Windows or Linux
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.

Figure 11: Sample of Azure Virtual Machine based SAP Landscape
2.3.3 Hybrid Cloud with Azure
Customers have the option of running their SAP applications in a hybrid cloud environment where you
divide the deployment between bare-metal for high-end DBMS servers, on-premises virtualized
environments for application layers and smaller 2-Tier configured SAP systems and Microsoft Azure IaaS.
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.

Figure 12: SAP Landscape in Hybrid Cloud Environment
2.3.4 SAP HANA on Microsoft Azure
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 handled by
the power of Microsoft Azure and SAP HANA.

Figure 13: Meeting the need of Cloud & HANA with Microsoft Azure
At this time, Microsoft Azure VMs are certified by SAP for SAP HANA scale-up configurations only. Scale-
out configurations with SAP HANA workloads are not yet supported. The following operating systems
are supported to deploy SAP HANA on Microsoft Azure:
· SUSE Linux Enterprise Server 12.x

· Red Hat Enterprise Linux 7.2
Configurations of SAP HANA on Microsoft Azure are certified for up to 448GB memory and Microsoft
Azure instance type of GS5. Please refer to “Certified IaaS Platforms for SAP HANA”

Figure 14: SAP HANA on Microsoft Azure
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. Medium sized 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 environment as
described in an earlier section (3.3.3). In short it refers to the scenario where VMs are deployed to an
Azure subscription that has site-to-site, multi-site or ExpressRoute connectivity between the on-
premises datacenter(s) and Microsoft Azure.

2.3.5 Integration with LaMa
The Microsoft Azure Adapter for LaMa 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 LaMa and described earlier in this paper becomes available to be used on SAP landscapes
including SAP HANA running in Microsoft Azure.
The adapter is built as a Java library and is installed directly into the LaMa application. Once in place,
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, LaMa will do this via the
Adapter.
The diagram below conceptually illustrates the solution and what can be accomplished with it.
Figure 15: The complete solution: LaMa + Microsoft Azure Adapter/Connector

2.3.6 Microsoft Azure Adapter Roadmap*
The Azure Adapter for LaMa currently is at SP04 and has the following capabilities:
· Start/Stop Virtual Machine

· Virtual Machine Discovery
· Relocate (Linux OS)
· Azure Template Deployment
Features that are still in development and expected to be available by end of 2017** as part of SP05‡:
· Virtual Machine Activate/Deactivate (Power Off)

· Virtual Machine Discovery (Disk Type: Managed Disks)
· SAP System Relocate (Windows OS)
· SAP System Copy (Source VM: Linux/Windows; Target VM: Pre-existing VM or Azure Template
Deployment)
· SAP System Clone (Source VM: Linux/Windows; Target VM: Pre-existing VM or Azure Template
Deployment)
· SAP System Refresh (Linux/Windows)
* Microsoft Azure Adapter for LaMa roadmap is owned by Microsoft
** There is no guaranty from Microsoft or SAP that these features will be delivered by the dates mentioned
‡ Refer to SAP Note 2343511
3 Customer Scenarios
Some sample customer scenarios that benefit from the combined LaMa and Microsoft Azure Adapter
solution are described in the sections below. Note that there are many use cases for LaMa itself that do
not dependent on the Microsoft Azure Adapter and are therefore not listed. All the scenarios below can
be handled from the LaMa interface.
3.1.1 System Copy/Clone/Refresh
Before we get into how the Microsoft Azure Adapter is leveraged for SAP system copy, clone or refresh
operations, it is important to understand the differences. The diagram shown below illustrates this.

Figure 16: LaMa – SAP system clone, copy and refresh
As can be seen in the above 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 LaMa 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.
3.1.2 Microsoft Azure Templated Deployment
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 landscape. 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 environment
and then used to deploy additional environments.
All the above would be done from the LaMa interface.

Figure 17: Azure Virtual Machine defined via JSON template
3.1.3 Relocate
LaMa has a relocate feature that allows SAP instances to easily move between different hosts and
different versions of operating system. Coupled 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.
The sequence needed to perform this task may look like:
1. Stop – The SAP application is shut down by LaMa directly.

2. Unprepare – The underlying infrastructure changes are made with Microsoft Azure Adapter. This
includes shutdown of virtual IP address and detaching the storage where data for the SAP
application is located
3. Prepare – Microsoft Azure Adapter is leveraged again to assign the needed network settings.
Storage previously detached is attached to new system.
4. Start – LaMa verifies the SAP application and starts it up

Figure 18: SAP Instance Relocate in Microsoft Azure
4 Potential Enhancements
Microsoft Azure Adapter could be extended to cover additional scenarios that are currently not
supported. This section covers such potential enhancements although there is no timeline or guaranty
for delivery.
4.1 SAP HANA Large Instances on Microsoft Azure
SAP HANA Large Instance is where the memory footprint is over 500GB. This type of deployment in
Microsoft Azure has the SAP application layer residing in Microsoft Azure VMs and the database layer
residing on SAP HANA Tailored Datacenter Integration (TDI) configured hardware located in a Large
Instance stamp in the same Microsoft Azure Region that is connected to Microsoft Azure IaaS. Large
Instance stamp refers to hardware infrastructure stack that is SAP HANA TDI certified and dedicated to
run SAP HANA instances within Microsoft Azure.
As of writing this paper, the sizes supported are as below:
o SAP HANA on Microsoft Azure S72 (2 x Intel® Xeon® Processor E7-8890 v3, 768GB)
o SAP HANA on Microsoft Azure S72m (2 x Intel® Xeon® Processor E7-8890 v3, 1.5TB)
o SAP HANA on Microsoft Azure S192 (4 x Intel® Xeon® Processor E7-8890 v4, 2.0TB)

o SAP HANA on Microsoft Azure S384xm (8 x Intel® Xeon® Processor E7-8890 v4, 8.0TB)
In this kind of setup, bare metal servers are used to run SAP HANA database. The application servers and
other components of the SAP landscape are hosted on Microsoft Azure virtual machines. The physical
servers are in close vicinity of the Microsoft Azure VMs. To the customer, this would appear as both
being in the same datacenter (where as they may or may not be in the same datacenter).

Figure 19: SAP HANA Large Instances
The diagram above illustrates a scenario where SAP HANA is running on physical servers while other SAP
application layers are on virtual machines all located in the same Microsoft Azure region.
Within the multi-tenant infrastructure of the Large Instance stamp, customer landscapes are deployed
as isolated tenants. These tenants have a 1:1 relationship to the Microsoft Azure subscription. This
means you cannot access the same instance of SAP HANA on Microsoft Azure (Large Instances) that runs
in a Microsoft Azure Large Instance stamp out of two different Microsoft Azure subscriptions.
As with Microsoft Azure VMs, SAP HANA on Microsoft Azure (Large Instances) is offered in multiple
Microsoft Azure regions. For Disaster Recovery capabilities, you can choose to opt in for this service.
Different Large Instance stamps in the various Microsoft Azure regions are connected to each other.

Just as you can choose between different VM types with Microsoft Azure Virtual Machines, you can
choose from different SKUs of HANA Large Instances that are tailored for different workload types of
SAP HANA.
4.2 Use Case: Microsoft Azure Adapter for SAP HANA Large Instances
The use case of giving customers the ability to manage SAP HANA Large Instances hosted in Microsoft
Azure is the vision for extending the Microsoft Azure Adapter. With many new SAP HANA management
capabilities in the LaMa 3.0 release and coupled with the Microsoft Azure Adapter, it would make it
much easier to manage SAP landscapes based on SAP HANA.
Leveraging Microsoft Azure multi-region setups, SAP HANA HA/DR features and LaMa/Microsoft Azure
Adapter capabilities, customers will have true enterprise class production applications running in the
cloud. This also includes LaMa orchestrating HANA MDC (Multitenant Database Containers) moves for
relocating tenants from on premise to MS Azure and back again.
Figure 20: SAP HANA HA/DR in Microsoft Azure Multi-Region Setup

The relocate capabilities that currently apply to Azure VMs (see section 4.1.3) would also apply to Azure
bare-metal servers used for SAP HANA large instances.
5 Preparation Requirements
The pre-requisites for LaMa and Microsoft Azure Adapter to work together are as below.
1. Dependencies
a. LaMa 3.0 Support Pack 1 (GA version)
2. System Requirements for LaMa (can be physical server or virtual machine)

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 refence section
d. Sample sizing table:
3. System Requirements for Microsoft Azure Adapter

As the adapter is a software package deployed directly on LaMa, there are no additional
requirements. Please refer to SAP Note 2343511
4. Platforms Supported (managed landscapes with the combined solution: LaMa + Microsoft Azure
Adapter)
a. SuSE Linux Enterprise Server 12.1 with SAP HANA SP12 or higher
b. Microsoft Windows Server 2008 R2 up to Windows Server 2016 with SQL Server 2016

6 Conclusion
SAP Landscape Management (LaMa) 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 landscapes,
tedious manual tasks are automated and significantly reduce errors and the time to complete. LaMa 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 as well as the HANA automation tool.
With SAP applications running on Microsoft Azure Cloud, the power of LaMa 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 performed at the infrastructure level.
Azure Adapter for LaMa 3.0 is the solution to get deeper into the infrastructure layers and automate
tasks that were not possible before. This becomes even more compelling for customers running or
planning to run SAP HANA Large Instances in Microsoft Azure Cloud as the power of LaMa and Microsoft
Azure Adapter allow for an efficient management of highly available SAP landscapes.
Together, LaMa and Microsoft Azure Adapter allow Basis Administrators to perform activities that would
have traditionally required a team of different disciplines and skill sets such as Microsoft Azure Cloud,
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.
7 References
1. SAP Landscape Management – Product Page: https://www.sap.com/lama
2. SAP Landscape Management – Community Page:
https://www.sap.com/community/topic/landscape-management.html
3. SAP Landscape Management – SAP Help Portal: https://help.sap.com/viewer/product/lama
4. SAP Product Availability Matrix: https://apps.support.sap.com/sap/support/pam
5. Microsoft Azure Documentation: https://docs.microsoft.com/en-us/azure/
6. SAP on Microsoft Azure: https://azure.microsoft.com/en-us/solutions/sap/
7. SAP on Microsoft Azure (SAP Wiki):
https://wiki.scn.sap.com/wiki/display/VIRTUALIZATION/SAP+on+Microsoft+Azure
8. SAP HANA on Microsoft Azure: https://docs.microsoft.com/en-us/azure/virtual-
machines/workloads/sap/get-started
9. Certified IaaS Platforms for SAP HANA: https://www.sap.com/dmc/exp/2014-09-02-hana-
hardware/enEN/iaas.html#recordid=1819

Microsoft - Azure LAMA Whitepaper

Uploaded by

Copyright:

Available Formats

You might also like

Microsoft - Azure LAMA Whitepaper

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Microsoft - Azure LAMA Whitepaper

Uploaded by

Copyright:

Available Formats

SAP Landscape Management with Microsoft Azure

2 Executive Summary ......................................................................................................................... 2

© 2017 SAP SE or an SAP affiliate company. All rights reserved 2

© 2017 SAP SE or an SAP affiliate company. All rights reserved 3

DEV QAS PRD

3rd Party Tools

Operating System and Database

On-Premise | Cloud | Hybrid

Key features of LaMa:

· Provisioning SAP Systems:

© 2017 SAP SE or an SAP affiliate company. All rights reserved 4

Figure 2: SAP Landscape Management (LaMa)

© 2017 SAP SE or an SAP affiliate company. All rights reserved 5

Figure 4: SAP system clone, copy & refresh

© 2017 SAP SE or an SAP affiliate company. All rights reserved 6

Use Case Benefits

2.2 SAP HANA Management with LaMa 3.0

Figure 5: SAP HANA Replication Setup with LaMa

© 2017 SAP SE or an SAP affiliate company. All rights reserved 7

Figure 7: SAP HANA nZDM Takeover

© 2017 SAP SE or an SAP affiliate company. All rights reserved 8

Figure 9: SAP HANA nZDM Maintenance

2.3 Microsoft Azure Adapter for LaMa

© 2017 SAP SE or an SAP affiliate company. All rights reserved 9

2.3.1 SAP and Microsoft Alliance

Figure 10: SAP and Microsoft

© 2017 SAP SE or an SAP affiliate company. All rights reserved 10

© 2017 SAP SE or an SAP affiliate company. All rights reserved 11

2.3.3 Hybrid Cloud with Azure

© 2017 SAP SE or an SAP affiliate company. All rights reserved 12

2.3.4 SAP HANA on Microsoft Azure

© 2017 SAP SE or an SAP affiliate company. All rights reserved 13

· SUSE Linux Enterprise Server 12.x

© 2017 SAP SE or an SAP affiliate company. All rights reserved 14

a. Medium sized production systems

© 2017 SAP SE or an SAP affiliate company. All rights reserved 15

Figure 15: The complete solution: LaMa + Microsoft Azure Adapter/Connector

© 2017 SAP SE or an SAP affiliate company. All rights reserved 16

· Start/Stop Virtual Machine

· Virtual Machine Activate/Deactivate (Power Off)

* Microsoft Azure Adapter for LaMa roadmap is owned by Microsoft

‡ Refer to SAP Note 2343511

3.1.1 System Copy/Clone/Refresh

© 2017 SAP SE or an SAP affiliate company. All rights reserved 17

3.1.2 Microsoft Azure Templated Deployment

All the above would be done from the LaMa interface.

© 2017 SAP SE or an SAP affiliate company. All rights reserved 18

The sequence needed to perform this task may look like:

1. Stop – The SAP application is shut down by LaMa directly.

© 2017 SAP SE or an SAP affiliate company. All rights reserved 19

4.1 SAP HANA Large Instances on Microsoft Azure

As of writing this paper, the sizes supported are as below:

© 2017 SAP SE or an SAP affiliate company. All rights reserved 20

© 2017 SAP SE or an SAP affiliate company. All rights reserved 21

© 2017 SAP SE or an SAP affiliate company. All rights reserved 22

Figure 20: SAP HANA HA/DR in Microsoft Azure Multi-Region Setup

© 2017 SAP SE or an SAP affiliate company. All rights reserved 23

2. System Requirements for LaMa (can be physical server or virtual machine)