SAP system startup and shutdown, including virtual hosts
On-premises: all involved source/target systems in the company's own data centers
Internationally active companies that operate systems with several terabytes of data and hundreds of users in different time zones depend on high system availability. If necessary, the system is copied incrementally, table by table, on weekends and at night. Complete shutdown of the production system is best avoided altogether.
Until now, it has been common practice to create test systems as a client or system copy of the production system on a specific date. In these cases, a single client or the entire SAP system is duplicated. The corresponding instances of the SAP system have to be reinstalled. In addition, a copy of the source database must be created. These are standard procedures, but they can be disproportionately expensive for productive data sets of several terabytes. SAP and third-party tools for selective data extraction can significantly reduce the cost of deploying non-production SAP systems.
One to two pre-tests are required, one of which should be performed on the production system. The additional load on the production system caused by the IMIG has been negligible. Split/mirror techniques allow many actions to be moved from the production machine to another machine.
In terms of its architectural approach, BSC takes standards into account wherever possible. As a result, the automation tool can be installed with minimal effort, fits very well into the respective system landscape and offers a fast ROI.
SAP system copy is made much easier by the "Shortcut for SAP Systems" application.
We support you in the execution of SAP system copies and, within the framework of our partnership with Libelle, we can also set up automation mechanisms for you if you have the need for regular system copies.
For each group, the software used for automation is shown, where "UC4" stands for UC4 Automated System Copy and "HP" stands for HP System Copy.