SAP is a set of tools and solutions for analytics and databasing. It is a key component for many business processes and is used by 80% of Fortune 500 companies. SAP is also used by Microsoft; the two companies have been partners for over 25 years. A recent development in this partnership was the announcement that SAP is now fully supported on Microsoft Azure.
Azure support for SAP is a significant opportunity for organizations that are already using or are planning to migrate to the cloud. However, migrating SAP to Azure can be a complex process that requires significant expertise and effort.
The following guide provides a high-level overview of this process to give you a basic understanding of the requirements of migration. For a more in depth guideline, you can refer to Azure’s SAP Deployment Checklist.
The preparation phase of a migration can be the longest. It requires research, negotiation, budgeting, and communication. When preparing, you need to perform the following steps.
1) Create an Inventory
When preparing for migration, you need to start with an inventory of your SAP components. This inventory includes applications that you want to move and any SAP interfaces you are using.
2) Decide on an Architecture
Next, you need to determine your desired architecture. Three-tier designs are recommended for greater flexibility and easier maintenance. Three-tier designs include a database, application, and presentation layer.
Part of architecture planning is choosing a deployment method.
3) Determine Your Network and Regions
Once you know what architecture you want to use, you need to decide which regions you plan to deploy to. You also need to determine how you will connect to these regions across your deployment and from your on-premise resources.
4) Choose a Migration Method
Finally, once you understand what resources you need to move and what sort of architecture you’re moving to, you can select your migration method. The method you choose depends on how your current resources are hosted, what applications you’re using, and how your data is stored.
Your migration method has a significant impact on the timing and success of your migration. It is important to make sure you fully understand the implications of whatever method you choose.
There are four areas to focus on when deciding the details of your architecture—security, scalability and performance, availability and recoverability, and efficiency.
To determine the proper security settings for your future deployment, you need to first understand what parts of security you are responsible for. The table below shows the breakdown of security responsibility you need to follow.
|Your Responsibilities||Shared Responsibility||Provider Responsibilities|
|Self deployment||Data governance and rights management, endpoints, account and access management, identity and directory infrastructure, applications, network controls, and OS||Physical hosts, data centers, and networks|
|SAP CP deployment||Data governance and rights management, endpoints, and account and access management||Identity and directory infrastructure, applications, and network controls||OS, physical hosts, data centers, and networks|
When configuring for security, you should include the following services:
2) Scalability and Performance
During configuration, you need to right-size your resources for optimal performance. This includes compute, storage, and network resources. If you undersize you will have bottlenecks and if you oversize you will pay for unused resources.
Keep in mind that you can scale up resources when needed. You can scale by either increasing compute capacity or by adding additional servers. However, this isn’t instantaneous. Scaling is most efficient when you know that you’ll have temporarily higher demands.
You should consider using ExpressRoute for a private, dedicated connection. This connection service provides more reliability, lower latency, faster speed, and better security than a standard connection. It is also a good idea to enable Accelerated Networking. Accelerated Networking further decreases the latency and increases the speed of your network transfers.
3) Availability and Recoverability
Use multiple small application servers instead of one large server to provide resiliency and protect against unplanned downtime.
There are multiple ways to ensure availability and data duplication:
Regardless of your data duplication, ensure that you have backups of both your database and your applications. You can use built-in HANA System Replication for your database and Azure Site-to-Site Recovery for your applications. You can also create manual backups although this is a more laborious process.
Make sure you are only moving the data and applications you need. Moving unnecessary data or applications wastes time, bandwidth, and storage space. Using a hybrid storage solution that integrates with Azure can help ease this process. Hybrid storage makes it easier to transfer data between on-premise and cloud locations. It can enable you to easily move additional files later if you find you need them.
If you need to run SAP applications 24/7, consider using Azure Reserved Instances. These instances are cheaper but require that you prepay for services.
Try to automate your deployment wherever possible to reduce configuration errors and ensure consistency. There are templates available that you can use for automation. These templates use Terraform modules to deploy components and Ansible playbooks to install and configure your database and applications.
A test deployment enables you to make adjustments and refine your configurations before going to production. During this deployment, you should verify VM types, storage, networking, availability and disaster recovery, and communication timeout settings.
Test your availability and disaster recovery procedures by shutting off select VMs and running backup and restore sequences.
Test your security to ensure that users are only able to take the actions you expect. Ensure that databases can’t be accessed publicly and that data is encrypted. In this deployment, it is best practice to use simulated data whenever possible. Simulated data reduces your risk of private data being breached if your set-up is not secure.
Compare your test deployment performance to your current implementation. When comparing, make sure to evaluate multiple jobs and workloads. You should include your highest anticipated and average levels.
During your testing, it helps to create documentation of your configurations and processes. You can use this document as guidance when maintaining your production system.
Migrating SAP to Azure enables you to take advantage of the benefits of the cloud, including flexibility and scalability. SAP in Azure can also provide significant cost savings, particularly if your current infrastructure needs an upgrade.
Hopefully, this article helped you understand some of what a migration entails. Using the guidelines here and the resources provided, you can begin planning a successful migration of your SAP workloads.