XSA Service Instances Migration from On-premise to Cloud Foundry

[apoorva_nagaraju]

In the last blog, you learned migration from an on-premise SAP HANA database to an SAP HANA Cloud database instance using the Self-Service Migration for SAP HANA Cloud. Now, will see on how to migrate the XS advanced service instances from on-premise to Cloud Foundry.

Figure: Migration Landscape

Pre-requisites

• Connectivity Service Entitlement with the service plan “connectivity_proxy” must be enabled for your subaccount using the SAP BTP cockpit.
• Supported for SAP HANA Database Revision 53 or greater.
• Source and Tenant databases has XS advanced installed.
• Migration user in the XSA tenant database of source system with necessary privileges.
• Establish a connection to the XSA tenant database of source system using Cloud Connector.

Note: Services Instances in default SAP space is not supported for migration.

Procedure

1. Open SAP HANA Cloud Central, navigate to “Migrations”.
2. Choose “Create Migration”, specify the migration information and then “Create”.
3. In the PLAN phase,

• Enter the virtual host and port that you specified in the cloud connector configuration.
• Enable Cloud Connector and specify the Cloud Connector Location ID.
• Enter the credentials of the migration user that was created in the XSA tenant database of the source system.
• Check Compatibility with SAP HANA Cloud.

• Tool runs a series of database and application compatibility checks. Once the Self-Service Migration tool finishes checking your database, it lists any incompatibilities found. 
• Only checks with the severity 'CRITICAL' and 'UNKNOWN' will forbid the migration. Checks with the severity 'ERROR' or below will allow the migration; however, it is possible that some functionality may not work as expected in the target database.
• Review and resolve the incompatibilities where possible. Choose Proceed to Preparation Phase.

    4. In the PREPARATION phase, provide the following information:

       Migrate XS advanced service instances (SAP HANA Schemas and HDI containers) to Cloud Foundry.

     As the source database has XS advanced installed and the tenant database selected for migration is enabled for XS advanced, the connection to the XS advanced database is configured through the SAP Cloud Connector.

• Provide the login credentials of the XS advanced administrator user.
• Configure the connection to the XS advanced runtime through Cloud Connector.
• Choose Configure Endpoint to generate a configuration file that you  have to upload to SAP Cloud Connector in a later step.

• Download the Configuration file and upload the same in Cloud Connector. Refer to point 9 in the link for more details.

• Click on Save and Proceed.

• Specify the credentials of the SAP BTP technical user.

• Map the source and target spaces which contain the service instances to be migrated.

• Specify the credentials of the migration user and Choose Save and Proceed to Select Target.

• Choose the target database for the migration and enter the credentials of the DBADMIN user on the target database.

• Confirm all the migration choices and Choose Continue to Execution Phase to proceed to the next phase of the migration.

     5. In the EXECUTION phase, choose “Start Migration” to start the migration process and monitor progress in the status bars. After the migration, a summary is displayed, and you can proceed to the VALIDATION phase.

    6. In the VALIDATION phase, the metadata and data of the migrated content are checked for consistency, also the record count of the tables to be migrated can be checked. Choose “Proceed to Finalization Phase”.

    7. In the FINALIZATION phase, the finalization process removes all artifacts that were temporarily stored by the migration service.Choose “Deactivate the migration user” and “Finalize Migration” to complete the migration and start the post-migration clean-up.

   8. The XS service instances is migrated to Cloud Foundry. A summary screen is displayed, containing information about the completed migration, including statistics about the migrated database, migration step durations, and validation statuses.

   9. “Clean Up Process” will archive the completed migration. Once the migration is archived, it serves as a reference and cannot be altered. Up to 20 migrations can be archived.

Hope this blog has helped! For more information refer SAP documentation SAP HANA Cloud Migration Guide.