Hello experts, require your help with a Solution Manager 7.2 ABAP/JAVA Migration to new server

[Privete_member__1051866]

I am an SAP Basis Admin and I was required by my company to carry out a Solution Manager 7.2 ABAP & JAVA stack migration from (OS) Windows Server 2012 to Windows Server 2019 - (DB) Microsoft SQL Server 2016 - stays consistent. Now I thought SWPM was the best way to do this as this sounds like a Homogenous System Copy as we are just switching servers and plan to keep everything else the same (including SID, instance etc), do correct me if I am wrong. 

New server is up and running and database changes were made as I went through the process to maintain consistency. 

Application sits on its own server which also remained the same. Database went from old windows server to new windows server

After a few different failed attempts via SWPM different options. I was able to carry this out as a JAVA export/import first & then ABAP export/import which was completed successfully.

Initially the JAVA was up and running without an issue. However, after the ABAP - now the JAVA instance shows "some processes started" and the ABAP instance - disp+work goes from "request handling without progress" to "server shutdown". The info on the instances has updated to the new server and I have done server restarts as well but the instance is showing these errors and just not coming back up. 

From SWPM I had chosen the option below for the ABAP export (Source System) - 

SAP Solution Manager 7.2 Support Release 2 > SAP Solution Manager 7.2 ABAP Support Release 2 > MS SQL Server > System Copy > Source System > Bases on AS ABAP > Database Instance Export 

Option below for the ABAP import (Target System) - 

SAP Solution Manager 7.2 Support Release 2 > SAP Solution Manager 7.2 ABAP Support Release 2 > MS SQL Server > System Copy > Target System > Distributed System > Based on AS ABAP > Database Instance

These were the respective options, unless I have selected something wrong ?

 Now From SWPM I had chosen the option below for the JAVA export (Source System) - 

I did not see a similar option as of the ABAP under SAP Solution Manager 7.2 Support Release 2 for JAVA, hence, I had to select -

SAP NetWeaver 7.5 > MS SQL Server > System Copy > Source System > Based on AS Java > Database Instance Export 

Option below for the JAVA import (Target System) - 

SAP NetWeaver 7.5 > MS SQL Server > System Copy > Target System > Distributed System > Based on AS Java > Database Instance 

Perhaps the different options were the inconsistencies ? I had no other option that made sense though and initially this was how my manager had installed Solman 7.2 via the SAP Netweaver 7.5 (I did select the Solution Manager 7.2 option during the ABAP instead of SAP Netweaver 7.5 though but I did not think that would be a problem ? 

OR it can just be other post export/import steps that I am missing ?

Require your insights on this and I can provide more information if needed. 

Thank You !

[Vera_Jiang]

We helped you to accept the answer, since there were no updates after 7 days. You can unaccept it anytime if the answer provided was not helpful enough and you have further questions.

[mamartins]

On the HOMOGENEOUS COPY method, you don't need to use SWPM to export the DB. 

Please follow the official documentation: System Copy - Target Databases Other than SAP HANA | SAP Help Portal.

Although your description of the problem is a little bit messy, I think that you are doing a "Single Instance Copy" option of the manual mentioned above.

[Privete_member__1051866]

Also, yes I have followed the guides for Windows - ABAP & Windows - JAVA for Solution Manager 7.2 SR2.

[Privete_member__1051866]

Hello, thank you for your response. Can you elaborate more on what you mean ? If not SWPM, then what do you recommend ? You are saying I did as Single Instance rather Dual Stack ?
Also, I can clarify more on the issue if needed. The main problem is the system not coming up after the system copy which was done without issue. 

[mamartins]

SOLMAN 7.2 is no longer dual stack. They are 2 separated instances (even if they depend on each other).

The migration process is simpler if the destination server keeps the same hostname from the older one. If not, the JAVA stack migration is bit more complex.

on SOLMAN the JAVA stack uses the ABAP one to do USER authentication. Perhaps you have conflicts with instance numbers?!

[Privete_member__1051866]

Hello, everything is consistent but going from Windows Server 2012 to 2019 and host changes from XXXSAPXXX1 to XXXSAPXXX01. Instance numbers are also the same.

[Sriram2009]

Hi yes, you have to change the windows server host name you can keep the all instance numbers same as you have in the windows 2012 server. Regards SS