SAP Landscape Copies
The 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.
The tools we use can be easily operated either in the cloud or on premise. For this, the SAP systems to be copied must allow access at operating system level. The typical cloud infrastructures, such as AWS or Azure, are not a hurdle for this service.
Applicability of Systemcopy as a Service
Today, thanks to tools for creating SAP system copies, it is possible to create such system duplications practically at the push of a button, and that too in a very short time. Even several at once.
The maturity and performance of automation tools for SAP system copying have evolved over a period of more than 15 years. The first tools for SAP system copy creation came from the mainframe environment.
If you have used "Shortcut for SAP Systems" to save system-specific tables before the system refresh, several manual steps can be omitted - the data can be restored by restoring the data saved before the system copy.
For example, it is possible to automate quality assurance processes and successfully introduce new business functions without a costly and time-consuming SAP system copy.
The IT team must regularly copy the SAP productive environment in order to be able to carry out testing and development work on the "real" system without manipulating the productive systems.