SAP system startup and shutdown, including virtual hosts
SAP system deployment scenarios
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.
Fact: BDLS is a kind of "time eater" for system copies (except when using Hana). An important first step is to integrate the BDLS run into the system copy. Once the copy is effectively through, the BDLS is automatically started.
Before shutting down the target system
Test data is important for companies to eliminate risks in ongoing operations and to optimize systems or processes. But collecting this data can be challenging in times of Big Data and increased data protection, as well as due to complex IT structures.
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.
With "Shortcut for SAP Systems", tasks in the area of SAP system copy are simplified and made possible.
The number of R3load processes to be started in parallel is specified in the {ex|im}port_monitor_cmd.properties configuration file.
Some useful tips about SAP basis can be found on www.sap-corner.de.
In addition to making the target systems unavailable to operations and project teams, system and landscape copies also block SAP Basis administrators.