Additional Blogs by Members
Showing results for 
Search instead for 
Did you mean: 
Lot of SAP users are planning to move their SAP instances into Rise with SAP offering. The client who want to move there existing S/4HANA system under Rise my blog will help them to plan their activity in more organized way.

As you all know, RISE with SAP is offers One SAP contract covering all components, in addition to secondary contracts with Partners for services or add-on packages if applicable.

RISE with SAP is not a product. RISE with SAP offering is centred around SAP S/4HANA and this package aims to accelerate, streamline, and motivate organisations with their journey to a cloud centric intelligent enterprise.

Following figure describes how S/4HANA services are managed:

SAP S/4HANA : On-Premise vs Rise with SAP

If the client wants to move it existing S/4HANA system (as-is) into Rise with SAP environment, SAP has given a five step Brownfield approach which uses the System copy – Backup/Restore method using the migration server. Following are the steps

Step 1: Take the backup of existing S/4HANA system.

Step 2: Move the backup to Object Storage provided by SAP

Step 3: SAP team will move the backup from Object Storage to Storage attached to the HANA Database of the S/4HANA server.

Step 4: Run the SWPM on Migration Server.

Step 5: Restore the backup on the S/4HANA system hosted into Rise with SAP environment.

Since SAP has regulations in place and they do not provide OS/root access on SAP Cloud deployed application and database servers.

Instead of, SAP provided additional VM with full OS/root access and they call it as Migration server. The VM have 128GB RAM, 32vCPUs and 100GB storage which /sapmnt of 20GB and /usr/sap of 80GB.

Steps to provision copy of client system into Rise which is also called as Partner Led Migration

Following details are require from client to start the migration:

  • Hostname of the migration server, database server

  • DB ports to be opened so that it can be accessed from migration server

  • Location of Backup files and backup prefix

  • SID and instance number of the database

  • Passwords for SYSTEMDB/SYSTEM user, sidadm, Tenant DB/SYSTEM user

  • S-user ID for software download on migration server

Once the migration is complete, partner will shutdown the application running on the migration server and will provide password of DDIC in 000, 100, 200, 300, TenantDB / SYSTEM, Schema user password which came with the backup.

Kindly provide feedback about my blog and also if I have missed any thing do let me know.