Skip to Content

SAP Database Migration Option (DMO) is a fully functional system for moving a database onto an SAP server. In the case of AWS, this server is one that resides online. While the logistics of the migration are a bit different from simply copying a database across to a secondary physical server, the end result is the same. We already know that AWS offers a lot more flexibility and fluidity in running applications than an on-site SAP server, and now we’ll see how moving databases over from a physical SAP server to an AWS cloud server can be done in a relatively pain-free manner. DMO forms part of a suite of migration tools included in SAP Software Update Manager (SUM) and is leveraged by SAP to move any HANA-compatible database onto an SAP install.

High-Level Migration Tasks

There are multiple ways of taking an on-site system onto AWS completely. Some companies offer solutions that allow for the cloning of an on-site system which can then be moved via DMO to the AWS cloud server and this may be a faster method although it gives less control to the user regarding the details of the migration. If you intend to use this method, AWS offers options that allow a company to test and experiment with their migration, including items like resizing EC2 instances in order to get the most out of the install. These high-level migration tasks allow us to prepare the stage for the migration of our database onto AWS. There are two different ways we can approach this migration and they are discussed below.

Option 1: Manual Database Migration with DMO

The assumptions that are made regarding this migration scenario is that the SAP systems already exist on-site and that the only component that requires access to AWS is the DMO server. The process that follows moves data from the source database onto the SAP HANA database. How we do this is as follows:

STEP 1 – Login to your existing AWS account. If you don’t have an AWS account, then you should create one since it is necessary for the rest of the processes we are going to perform.

STEP 2 – Set up connectivity, either directly via AWS Direct Connect or through a VPN with the AWS Region.

STEP 3 – Create and run the SAP application instance and AWS SAP HANA database instance and on the server in accordance with the SAP HANA Quick Start guide.

STEP 4 – Enable the DMO server. This server can be housed on the same server as the SAP install or can be located separately depending on the demands for processing power and memory space.

STEP 5 – Check the network connectivity between the HANA database located on AWS and the DMO server located on-site. For large database sizes, the amount of data transferred may be immense so this connection should be stable enough so that there is no loss of data.

STEP 6 – Use DMO to carry over the contents of your local SAP HANA database onto AWS in a compatible HANA format.

STEP 7 – Create and deploy new SAP application servers on the AWS server to correspond with the requirements of applications on the SAP HANA install.

Option 2: Using an AWS partner Tool for Migration

If you’re using a partner tool for the migration of your SAP server to the AWS server, you first have to copy the source system that resides on-site onto AWS then migrate that system into SAP HANA. The process is similar to the manual migration of your database using DMO and a few of the steps are unchanged.

STEP 1 – Login to AWS or create an account if you don’t already have one

STEP 2 – Create a direct connection using AWS Direct Connect to bridge the AWS Region and your local data center.

STEP 3 – Clone your system on the AWS server. This creates a distinct version of your system stored on AWS and will be the subject of the SAP HANA migration leaving the original system untouched on the local server.

STEP 4 – Create and run the SAP application instance and SAP HANA database on the AWS server in accordance with the SAP HANA Quick Start guide.

STEP 5 – Enable the DMO server. This can be done on the same server as the SAP install or can be housed on a separate server depending on its demands for processing and memory.

STEP 6 – Using the source system we cloned in Step 3, we will run the DMO migration server to build an SAP HANA database from this cloned server information.

STEP 7 – Create and deploy new SAP application servers on the AWS server to correspond with the requirements of applications on the SAP HANA install.

Migration Planning as a Necessity

Before moving your server online, proper planning is necessary. The installation of application servers won’t be copied along with the database information and must be done separately. Additionally, virtual names need to be assigned to enable the applications on the SAP server to work properly. For any company, if their database is above a certain size, then a few test-runs of the migration should be done before a final migration is commenced. Familiarizing oneself with SAP on AWS can aid in dealing with the more common issues that may arise during a database migration into the cloud.

To report this post you need to login first.

Be the first to leave a comment

You must be Logged on to comment or reply to a post.

Leave a Reply