Skip to Content

Environment Group – System Copy

This notebook details generic and product specific phases, which are in line with the SAP System Landscape Copy Guide (2008).  The notebook has been enhanced to include SAP notes for specific products and whilst this is a good template it should be refined for each customer with detailed site information and screenshots if necessary. Please refer to the SAP System Landscape Copy Guide and SAP Note 885343 as starting points for reference documentation.

Phase 1: Preliminary Tasks

Phase 2: Preparations on Target Environment

Phase 3: Preparations on Source Environment

Phase 4: Copy Process

Phase 5: Final Activities on Source Environment

Phase 6: Final Activities on Target Environment

Risks

Risks 1 Avoidance of interactions with Production Systems

Disable all interfaces

Adapt Transport Settings

Adapt NFS mounts

Check Batch input

Adapt Printers and Spool Settings

Modify Users and Authorisations

Adapt Logon Groups

Check External Commands

⚠  All these actions should be done before or immediately after starting a target system.

If you cannot make absolutely sure that the production environment will be unaffected, we recommend separating the network environments of source and target systems.

Risk 2 Online Copy

Prevent  automatic start of batch jobs

Disable  unintentional user logon

Disable  system connections (RFC ‘s)

Risk 3 Changing the Logical System Name

In any system landscape where data is distributed and exchanged between different systems, there is a potential risk when changing the configuration parameters responsible for data exchange. These parameters include:

RFC Destinations

Hostname

Logical  system names

Risk 4 System Copy with Non empty Message Queues

If the queues are not empty when doing the copy, they will contain valid data in  the target systems after the copy. Processing these queues will be important  for application data consistency in the target landscape (also see the  discussion of data consistency in “Risk 5”).

Risk 5 Data Inconsistency in the target landscape

Data consistency in this context means that the application data exchanged between systems has a matching state regarding data modifications transferred by messages.

Notes:

⚠ The phases 2 to 6 must be done in parallel for all components of the landscape that are to be copied together.

As a generalisation ERP is completed first with the other systems being completed before the next phase commences.

To report this post you need to login first.

Be the first to leave a comment

You must be Logged on to comment or reply to a post.

Leave a Reply