Need recommendation on Migration approach for MII(Java stack) systems

[former_member609950]

Hi Experts,

I would need your expertise advise on the following scope and approach for MII system's version upgrade and migration project as I’ve listed different approaches to migrate data from source to target and need your recommendation on which one we should opt for considering all different factors and dependencies.

Scope:

• Upgrade the SAP JAVA stack of MII landscape from Net weaver 7.31 SPS 17 to Net weaver 7.50 SPS 13
• Upgrade of SAP MII from 15.0 SP06 to 15.2 SP03
• Upgrade of OS from Windows Server 2012 to 2016 & DB from SQL Server 2012 to 2017 respectively

Upgrade/Migration Approach:

Windows team builds new servers with requested configuration and latest OS Windows 2016. Subsequently, following is the approach to upgrade and migrate respective system.

• Install SQL DB 2017 on new target server
• Install SAP Netweaver 7.50 Java stack on target system
• Upgrade Netweaver SPS to level 13 along with SAP MII 15.2 SP03 on target system
• Creation of MII users with a generic password in new target system
• Bring Source & Target systems down as part of cut-over(Downtime window starts)
• Migration Approaches

1. Perform detach of source SQL DB and attach it to target system: The caveat with this approach is that we can’t rollback to the source system in case we encounter issues on target system and doesn’t get sign-off.
2. Select backup & restore method during SWPM process : Does this method works seamlessly for a JAVA stack system?
3. SAP Export & Import : This is usually a recommended method for a JAVA stack system but in case of MII, we’ve an additional database schemas created, thus, not sure whether all the database schemas gets exported or not?

• Perform post copy steps

Regards,

Dheeraj

[patelyogesh]

Hello Dheeraj Kadiyala,

I have gone through your question and this is what I can think of in your case...

Perform detach of source SQL DB and attach it to target system: The caveat with this approach is that we can’t rollback to the source system in case we encounter issues on target system and doesn’t get sign-off.

You are correct on this case... you need to stop using your existing system and perform full testing on your migrated system. Once sign-off completed you can stop the existing system and start using new system. This is the safe way to do migration.

If this is java system this method will not work.

Select backup & restore method during SWPM process : Does this method works seamlessly for a JAVA stack system?

For Java I do not recommend you this method.

SAP Export & Import : This is usually a recommended method for a JAVA stack system but in case of MII, we’ve an additional database schemas created, thus, not sure whether all the database schemas gets exported or not?

This method will work for java system. Actually this is the recommend method.

[Sriram2009]

Hi Dheeraj.

Since you are using an MS SQL server, in the target system you can perform either backup /restore or MS DB detach. attach method. and then start the SWPM on the target system, I am not sure about the SAP MII

Regards

Sriram

[vmg011185]

Hi yogesh.patel3

Why export/import is recommended method for java, Please eloborate?

Regards,

Vaibhav