Migrating AnyDB to SAP HANA on AWS
Migrating from anyDB to HANA typically involves changes to the database platform and sometimes includes operating system changes. However, migration might also involve additional technical changes and impacts, such as the following:
-
SAP ABAP code changes. For example, you might have custom code that has database or operating system dependencies, such as database hints coded for the anyDB platform. You might also need to change custom ABAP code so it performs optimally on SAP HANA. See SAP’s recommendations and guidance for these SAP HANA-specific optimizations. For details and guidance, see Get started with the ABAP custom code migration process
and SAP Notes 1885926 – ABAP SQL monitor and 1912445 – ABAP custom code migration for SAP HANA on the SAP website. -
Operating system-specific dependencies such as custom file shares and scripts that would need to be re-created or moved to a different solution.
-
Operating system tunings (for example, kernel parameters) that would need to be accounted for. Note that the AWS Launch Wizard for SAP incorporates best practices from operating system partners like SUSE and Red Hat for SAP HANA.
-
Technology expertise such as Linux administration and support, if your organization doesn’t already have experience with Linux.
SAP provides tools and methodologies such as classical migration and SUM DMO to help its customers with the migration process for this scenario. (For more information, see the section Migration Tools and Methodologies.) AWS customers can use the SAP SUM DMO tool to migrate their database to SAP HANA on AWS. Some considerations for the SAP SUM DMO method are network bandwidth, amount of data to be transferred, and the amount of time available for the data to be transferred.
You can use the SUM DMO memory pipe option – DMO Move to SAP S/4HANA (DMOVE2S4) to
accelerate your move to SAP S/4HANA. In a single step, you can migrate the database over
network while converting to SAP S/4HANA. For more information, see SAP Documentation –
DMO Move to SAP S/4HANA (on Hyperscaler)
-
low latency – less than 20 ms
-
high bandwidth – more than 400 Mbps
For more information, see the following SAP resources.
-
SAP Note 3296427 - Database Migration Option (DMO) of SUM 2.0 SP17
(requires SAP portal access)
Implementing SAP HANA on AWS enables quick provisioning of scale-up and scale-out SAP HANA configurations and enables you to have your SAP HANA system available in minutes. In addition to fast provisioning, AWS lets you quickly scale up by changing your EC2 instance type. With this capability, you can react to changing requirements promptly and focus less on getting your sizing absolutely perfect. This means that you can spend less time sizing (that is, you can move through your project’s planning and sizing phase faster) knowing that you can scale up later, if needed.