SAP Data Services Upgrade to 4.3 SP3 on Azure cloud - help

[kiranpileti]

Hello,
We need a help Migrating SAP DS 4.2 SP14 to Data Service 4.3 SP3 and IPS 4.3 SP4 on Azure cloud.  We need help with documents , videos or blogs how to migrate the SAP Data Services on Azure Cloud. Currently we are running a Data Services environment with the following software and versions:

SAP Data Services 4.2 SP14
SAP Information Platform Services 4.2 Support Pack 8

Application server OS: Windows Server 2019 Datacenter
Database: DB2 11.5 running on Linux server

Web Application: Tomcat

Migration tools: SAP Data Services Repository Manager

Thank You
Kiran

[JoyD]

For the DS repo migration, please refer below
https://me.sap.com/notes/2768127
https://me.sap.com/notes/1481432

Best Regards,
Joy

[DayaJha]

Hi Kiran,

There are 03 scenario's is up to you which one to pick as per your landscape.

Scenario I: - If network connectivity or network latency is not an issue, then better to move current H/W from on-prem to cloud using Azure Tool in this case only you have to make sure that after migration below configuration are in SYNC

• O.S H/W configuration (CPU, RAM & Virtual Memory) status before and after migration
• Drive space status before and after migration
• Data store connectivity status before and after migration
• Source file (Network Path) connectivity status before and after migration
• Assuming machine name is same, so that no impact to current configuration only changes of IP address which will be taken care with th ehelp of network team (firewall security)

Once On-Prem to cloud migration is done, you are done with the post validation take a break for 1-2 weeks and then go for upgrade in this scenario you will not face any issue related to credentials and connectivity.

Scenario II: - Build new environment with same IPS & BODS version, assuming database is pointing to same repositories (CMS, Audit, Local repository, Secure Central repository & Profile repository)

• Perform installation with dummy database and then switch it to current CMS & Audit database so that you will get the same configuration
• Activate Local repository, Secure Central repository & Profile repository via CMC console
• Update Job Server configuration.

Once on-prem IPS & BODS version setup is done, with the post validation take a break for 1-2 weeks and then go for upgrade in this scenario you need ODBC to be setup in new server, also you need credential for all data store where credential is required, also you have to make sure Source file (Network Path) connectivity will work as expected or else coordinate with network team and get it sorted.

Scenario III: - Build new environment with updated IPS & BODS version, using promotion manager copy the content from on-prem landscape.

• Perform installation with new CMS & Audit database
• Using Promotion manager migrate the content
• Create new Local repository, Secure Central repository & Profile repository via DSMC
• Activate Local repository, Secure Central repository & Profile repository via CMC console
• Import ATL in new Local repository
• Delete Job server details from Local repository via DB's.
• Map new Local repository to Job Server
• Validate the data store, changes of failing where ever network path and credential is required, please make sure you have credential for all DB's also network connectivity should be in SYNC with new Azure server

I hope this will help!!!

Regards,

Daya Jha