Skip to Content

Depending on the  selected copy scenario, the production systems must be put back to their  original state so productive operations can be resumed. This phase may be  delayed until after phase six to reduce any possible risks to an absolute  minimum.

Generic

5.1 – Startup  production

5.2 – Re-enable  communication between source systems

Reversing the  steps taken at Phase 3: Preparations on Source Environment section 3.3 to 3.5

5.3 – Perform  follow-up activities from [System Copy Guide]

Reversing the  steps taken at Phase  3: Preparations on Source Environment section 3.3 to 3.5

5.4 – Restart  productive operation in source systems

BW  Specific

Phase 5: Final  Activities in Source (Original) Environment

Step 5.4: Restart  productive operation in the original BW system

SAP NetWeaver 7.0:  Restart daemons for real-time data acquisition in transaction RSRDA.

SAP NetWeaver 7.2:  Execute report RS_SYSTEM_SHUTDOWN to restart process chains and real-time  data acquisition.

This has to be  done after unlocking the RFC users but it should be done before restarting  and enabling the other background jobs, e.g. by executing report BTCTRNS2.

CRM  Specific

On the source  environment, no special final activities have to take place after the copy.

APO  Specific

5.1 – Start-up  production

When using an external  liveCache: Start the source SCM database and the source liveCache. When starting the liveCache via transaction LC10, choose the button “Start liveCache”. Do NOT initialize the liveCache.

Notes:

To further  minimize the risk of the target systems interfering with the production  environment, restart of production could be delayed until the most critical  activities on the target environment (steps 6.1 – 6.6) are completed.

This  additional protection prolongs downtime for production.

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