DB-specific methods: - for DB-homogeneous system copies - no Unicode conversion possible!
Critical factor: Availability
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.
To build a target system that can be used for testing, development and training purposes, there are two different approaches: Users can reinstall an SAP system and import all transports and support packages that have also made it into the production system to date. However, when their number reaches the hundreds and thousands, the effort becomes disproportionately high. In addition, the data still has to be imported from the production system, for example via a client copy.
Automatic determination of delta states after SAP system copy/recovery
The initial screen will then, for example, already show an overview of the - in some cases automatically - integrated systems and their status, as well as system information such as release, patch level and the like. The use of a comprehensive dashboard will then also be included.
Creating a consistent storage replica - splitting a clone or creating a snapshot on the disk array. Regardless of the storage size, this process takes only a few seconds.
With "Shortcut for SAP Systems" you get additional functions for the SAP system copy.
Larger productive systems, on the other hand, are not so easy to virtualize.
If you want to get more information about SAP basis, visit the website www.sap-corner.de.
The following applies to all systems: new licenses, set up Securestore, IP address management, convert original system, no two identical SIDs possible in the network.