Differentiation between homogeneous and heterogeneous SAP system copy
Renaming and restoring the target system database - adjusting file system permissions. Renaming, recovery and startup of the target system database.
The guideline that integrated job logic is preferable to customizing has also proven its worth. The key point here is that each step of a copy job knows the overall context, including the steps that preceded and follow it.
SAP system update and database update
Regular updating reduces operational risk and improves the quality of the multi-level system landscape. To update the non-productive systems of an SAP landscape, the data must be cloned from the productive system. This is time-consuming and requires very complex rework.
We will be happy to advise you and work out the most suitable solution for you together with you - so that you profit 100% from Systemcopy as a Service. Contact us.
With "Shortcut for SAP Systems" any tables can be saved and restored. This is especially useful in the context of an SAP system copy - quite a few tables are system-specific and must exist unchanged in the system after a system copy.Shortcut for SAP Systems uses R3trans - a utility from SAP that is essentially used in the Transport Management System (TMS) environment. With "Shortcut for SAP Systems" it is now also available outside the TMS and enables completely new and diverse application possibilities. Among others in the environment of a system copy. R3trans works database independent. I.e. even in the case of a system refresh from an SAP system with an Oracle DB to a system with HANA, the backup and restore process works!
To eliminate downtime in the production system and minimize the impact on application performance-regardless of the size of the production data reconciliation-you can use, for example, HP StorageWorks System Copy for SAP (HP System Copy), which has a disk array-based replication capability.
Of these, TM-TMS covers two areas.