Automate SAP system copies
Downtime
Nowadays, companies are required more than ever to react agilely and flexibly to the demands of the global market. It is not unusual for them to have to introduce new processes and projects particularly quickly and securely for the benefit of their own competitiveness. At the same time, their system landscapes are becoming increasingly complex due to mergers and acquisitions and the use of new technologies.
In this context, generated jobs adapt to changes, even if, for example, a DB change, a release change or other changes have taken place. Nevertheless, once created copy jobs can be reused, which minimizes the maintenance effort and a certain susceptibility to errors. This is also the case when switching from one Any DB to another or when moving from an Any DB to Hana.
Import of delta statuses after SAP system copy / restore
Individual steps know exactly where they have to restart the actual copy run in the event of an error. In general, this means that error situations can be handled as needed and with pinpoint accuracy.
SAP system copy can be done easier and faster with "Shortcut for SAP Systems".
Ideally, a tool for creating SAP system copies should take the following core copy processes into account: Check and pre-processing, restore, actual execution, and post-processing.