The scope of work:

• Prepare the current applications for readiness
• Prepare the AWS environment for SAP Landscape
• Upgrade the OS/DB on On-Premise datacenter with required versions compatible for AWS
• Migrate the SAP Applications to AWS
• Configure and follow-up activities
• Troubleshoot the issues and handover the environment

Approach in migration of SAP landscape to AWS

• CloudEndure replication
• Reconfigure customer landscape integration with third party vendors

Preparation

• Architect and plan the migration
• Prepare the current environment for optimal migration, such as applying the pre-requisites notes, follow the SAP guidelines, cleanup the large basis tables, check the network performance and adequate local diskspace for backups to be transferred to AWS instances
• Check the minimum kernel patch level requirements on source systems, cancelled or pending update requests, released jobs to scheduled, Adapt the Operation modes timetable and other required steps before shutting down the SAP for offline backups
• Get the Superdba, SAP<SCHEMA> and DDIC passwords from the source system
• Prepare the AWS accounts with required services with VPC Public subnet and Private subnets.
• Prepare the connections from On-premise to AWS cloud with direct connect or storage gateway if required and internet connection for moving the files to S3 bucket
• Estimate the timings of backup transfers through S3, Storage gateway and Direct connect
• Launch the Windows 2008 R2 Server EC2 instances with correct instance type and diskspace.
• Configure the instance for deploying SAP ERP and PI Dual stack systems as equal to the current systems.
• Prepare the Server hosts for local installations of SAP Applications
• Download required SAP software from SAP Marketplace
• Download the SAP Maxdb for ECC systems on these instances and configure as per the SAP installation guides
• Download correct SWPM versions for SAP ERP and NetWeaver for the installation.

Migration Process

• Stop SAP instance and take complete offline backups in the local disks for the automatic restore (It requires to take a backup in single file as backup medium for the whole backup)
• Transfer the backups to AWS EC2 Instance through Direct Connect/Storage Gateway/S3 explorer whichever is efficient
• Run the installer with SWPM for System copy -> Target System -> Standard System and choose Homogeneous System copy
• Complete the System copy

Post migration activities

• • Backup the total system with Snapshots of volumes in AWS
  • Complete the AWS VPC post steps such as NAT configuration and Security aspects
  • Start the AS Java instance manually as it doesn’t start after system copy
  • Install the SAP License key
  • On PI system migrate the entries in secure storage
  • Perform OS Windows Server level specific follow-up activities
  • Perform SAP MaxDB Specific follow-up activities
  • Perform the activities that are SAP System level as per the system copy guides
  • Check the consistency of Target system for handover

• Perform the Follow-up activities that is specific to Java
• SAP PI specific Follow-up activities such as SLD, Integration Server and connection checks
• Database Backup configuration and scheduling