Key solution steps
SAP system startup and shutdown, including virtual hosts
Third-party tools sometimes have a different focus than TDMS. The tools each offer a more or less generally understandable user guidance and are thus "out-of-the-box" products that do not require external consulting on implementation or application.
Even if the target system is not used for production in an update scenario based on a system copy, it is of central importance for developers and thus also the software lifecycle of the production system. That's why you should avoid upgrade downtime in both the production source system and the non-production target system. Production system downtime depends primarily on the method you use to create the image of the production data to be used in the target system. This image must be a transferable database image - for example, a database export, a backup copy, or an array-based reconciliation. 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. Downtime in the target system depends on the following factors, among others: The time required to restore production data reconciliation in the target system The amount of pre- and post-processing in the target system With HP System Copy, images of production data can be created in minutes, with each step between shutdown and reboot of the target system occurring automatically. However, after the reboot, the target system is not immediately ready for use, as additional steps must first be performed (see description below).
What is System Copy as a Service?
Without interrupting operations, we copy your systems using established methods and products. We guarantee consistent quality and reliable reproducibility through standardized processes and a high degree of automation. Due to the SAP system copy, the test and development systems are up to date and tests can be performed reliably and trustworthily on the non-production systems.
While homogeneous SAP system copy expects identical combinations of operating/database systems on the source and target systems, there is also a requirement for different combinations of operating/database systems on the source and target systems in the project environment (eg, during migrations). This is referred to as a "heterogeneous SAP system copy". Technically, it is quite possible to build up a degree of automation here as well, but officially certified consultants ("migration consultants") are required to perform the heterogeneous system copy.
There is a useful product for SAP system copy - "Shortcut for SAP Systems".
However, after the reboot, the target system is not immediately ready for use, as additional steps must first be performed (see description below).
Increasingly, ad hoc requests are coming from IT or SAP Basis to provide an SAP system copy as quickly as possible, for example of an SAP ERP, BW or HCM system.