Conclusion
Solution infrastructure
Basically, a distinction is made between the initial setup and refresh of a non-productive SAP system. In the past, the cost of a refresh, i.e., updating the environment with new data, often corresponded to the cost of the initial setup. This also restricted the availability of the productive system, which is hardly tolerable for companies that operate internationally and in different time zones.
The maturity and performance of automation tools for SAP system copying have evolved over a period of more than 15 years. The first tools for SAP system copy creation came from the mainframe environment.
Scope of the SAP system copy
After shutting down the target system, the technical system copy for upgrade 1 can be created at the infrastructure level. To automate the creation of the technical system copy for upgrade, HP System Copy can be used for the following steps.
Until now, there has been no functional tool for System i to automate and optimize this task. The enormous resource requirements that arise during a refresh of the SAP QA system really cry out for an optimizing software tool. System Copy from Libelle (LSC) reduces the effort required for these work steps. Although a one-time effort is still required, the system landscape is examined so well that the system copy and any subsequent ones are performed literally at the push of a button. The work that is automated by LSC is in the preparation and post-processing of the files as well as the actual system copy.
With "Shortcut for SAP Systems" you can sustainably relieve your administrators of time-consuming routine activities of an SAP system copy.
SAP Basis is the foundation of any SAP system. You can find a lot of useful information about it on this page: www.sap-corner.de.
Test and development system: After a new productive system has been set up, at least one identical development system or even one test system is still needed.
If necessary, the system is copied incrementally, table by table, on weekends and at night.