SAP system copy SAP system startup and shutdown, including virtual hosts

Direkt zum Seiteninhalt
SAP system startup and shutdown, including virtual hosts
Easy integration also in the system copy of systems of older releases possible!
We will be happy to advise you and work out the most suitable solution for you together with you - so that you profit 100% from Systemcopy as a Service. Contact us.

After shutting down the target system, the technical system copy for upgrade 1 can be created at the infrastructure level. To automate the creation of the technical system copy for upgrade, HP System Copy can be used for the following steps.

To store all the information on the subject of SAP - and others - in a knowledge database, Scribble Papers is suitable.
Purpose of the SAP system copy
Checklist for preliminary work: Comparison of database sizes (target system must be the same or larger), comparison of database versions, kernel, host agent (ideally the same software version), dump of kernel files (export via SAPINST), saves download via SWDC, compile RFC connection passwords, inform third-party system administrators, provide memory, hard disk on the system for database and software import. Perform database dump, if necessary with transaction log, if possible with downtime, then without jobs or stop running jobs with report BTCTRNS1. Adminsitration passwords (DDIC, DB-Admin, Winadmin), create system snapshots (recovery), perform database import.

In order to check whether the usable settings are correctly adjusted, especially in the case of large databases, the runtimes are automatically logged during the BDLS. Based on these results, it is possible to analyze how the runtime can be further optimized. By the way, BDLS reports and optimization options are displayed in the BSC GUI, including modification options.

"Shortcut for SAP Systems" offers the possibility to backup and restore any tables. Not only those that are considered in the PCA tool (Post Copy Automation) but also self-developed tables. Thanks to the simple and clear interface, backup and restore of self-developed tables can be integrated quickly and easily. The command line interface can also be used to automate the process: for example, a simple line command can be used to perform a complete backup of table contents before the system copy, and a simple line command can also be used to restore these tables after the system copy. This means that the complete backup or restore process can be integrated into any automation software.

The maturity and performance of automation tools for SAP system copying have evolved over a period of more than 15 years.

Some useful tips about SAP basis can be found on www.sap-corner.de.


Storage systems are usually secured in disk arrays by multi-level raid, spatially separated from each other and networked by a storage area network (SAN).
Zurück zum Seiteninhalt