Forum Discussion

ShaswatC's avatar
ShaswatC
Copper Contributor
Oct 13, 2020

Horizontal strategy for SAP Migration

Dear All ,

 

I have a query regarding Horizontal strategy for migrating SAP Landscapes . In this we migrate all the Development systems together, then Quality and then finally Production . While this migration is on , how do we maintain the transport landscape ?

 

For example , if DEV is migrated to Azure and QAS is on premise , they need to share a common transport directory . So how will it be achieved ? Does anyone have a real use case where they faced this . As taking a transport "freeze" for the entire duration of the migration is not an option for us .

 

Thanks in advance !

 

SAPonAzure

1 Reply

  • PSJENA's avatar
    PSJENA
    Copper Contributor
    Feb 17, 2021

    ShaswatC The approach would be as follows :

    There are many scenarios :

    like-to-like migration and no version /patch upgrade then follow below options.[code freeze during the Dev,QA & Production environments few days before to the migration till live]

     

    1.You should go for a Parallel landscape for Dev & QA environments in On-premise if customer has money to spent and this is the recommended approach.Parallel landscapes can be build by the system copy from existing Dev & QA. In this case no need of code freeze for the entire migration period. Only code freeze during the Dev,QA & Production environments few days before to the cutover. Shared Transport directory will migrate during production cutover. Dual maintenance in Dev is require till production live. 

     

    2.Only parallel landscape for Dev environment , Only code freeze during the Dev,QA & Production environments few days before to the cutover. But post QA migration to Cloud transports will move from Dev on-prem to Prod on-prem during emergency change. Shared Transport directory will migrate during production cutover. Dual maintenance is require in Dev till production live. 

     

    3.No parallel landscape & no Dual Maintenance - Move/migrate the Dev systems along with trans directory to cloud , then mount the cloud Trans directory mount point with on-prem QA & Prod and establish the transport route. In respective environment migration phase reconfigure the STMS route/ reconfigure is not required if you are have having same virtual host used for on-prem & Cloud.

     

    Version /patch upgrade then follow below options.[code freeze during the Dev,QA & Production environments few days before to the migration till live]

    1.Parallel landscape for Dev & QA environments in On-premise is mandatory. Trans directory migrate during production cutover. Dual maintenance between on-prem Dev & Cloud Dev is mandatory.

     

    2.Parallel landscape for only for Dev environments in On-premise is mandatory. Trans directory migrate during production cutover. Dual maintenance between on-prem Dev & Cloud Dev is mandatory.ut post QA migration to Cloud transports will move from Dev on-prem to Prod on-prem during emergency change. 

     

    Thanks

    Partha

Resources