SAP Landscape Copies
Multicloud: the systems involved with different hyperscalers
A system copy can be created either with SAP transactions (R3trans, from R4.6C SAPinst) or at file and database level. Costs and effort increase with the size of the system and the requirements for availability and data protection. In addition, administrative rework is often necessary, starting with the system name and extending to printers and interfaces.
The term "system copy" describes the process of creating a copy of an SAP system on a new server. There are two types to be distinguished: homogeneous and heterogeneous system copy and one can get to the system copy in different ways.
Applicability of Systemcopy as a Service
For virtually all customers using SAP Business Suite (including All-in-One solutions), the creation of SAP system copies is in and of itself a firmly established task area. In concrete terms, the doing usually has to be performed by the SAP Basis within IT, in addition to many other activities.
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.
With "Shortcut for SAP Systems" a tool is available that simplifies the SAP system copy and offers additional possibilities.
To build a target system that can be used for testing, development and training purposes, there are two different approaches: Users can reinstall an SAP system and import all transports and support packages that have also made it into the production system to date.
Renaming and restoring the target system database - adjusting file system permissions.