Book Image

SAP on Azure Implementation Guide

By : Nick Morgan, Bartosz Jarkowski
Book Image

SAP on Azure Implementation Guide

By: Nick Morgan, Bartosz Jarkowski

Overview of this book

Cloud technologies have now reached a level where even the most critical business systems can run on them. For most organizations SAP is the key business system. If SAP is unavailable for any reason then potentially your business stops. Because of this, it is understandable that you will be concerned whether such a critical system can run in the public cloud. However, the days when you truly ran your IT system on-premises have long since gone. Most organizations have been getting rid of their own data centers and increasingly moving to co-location facilities. In this context the public cloud is nothing more than an additional virtual data center connected to your existing network. There are typically two main reasons why you may consider migrating SAP to Azure: You need to replace the infrastructure that is currently running SAP, or you want to migrate SAP to a new database. Depending on your goal SAP offers different migration paths. You can decide either to migrate the current workload to Azure as-is, or to combine it with changing the database and execute both activities as a single step. SAP on Azure Implementation Guide covers the main migration options to lead you through migrating your SAP data to Azure simply and successfully.
Table of Contents (5 chapters)

Landscape review

As part of the migration, you should consider reviewing your landscape. As well as the minimum Development (DEV), Quality Assurance System (QAS), and Production (PRD), it is quite likely that you have multiple additional non-production environments. These may include Sandbox, Training, Integration Testing, User Acceptance Testing, Project DEV, Project QAS and Pre-Production. Should all of these be migrated to Azure, or should only the key environments be migrated, and the rest created as required once the move to Azure is complete?

Once you have decided which environments need to be migrated, you will also need to decide whether to migrate each individual environment, or simply migrate production and copy back the production data into the other environments. This will depend to some extent on your current practices. You may already copy back production into QAS on a regular basis for testing purposes, but equally your development environment may contain...