Synonym(s): SAP System Refresh, SAP System Copy, SAP Client Copy, SAP Client Copy, Landscape Copy, Landscape Copy
SAP Landscape Copies
Administrators and SAP maintainers in the x86 world under Windows and various Unix derivatives can nowadays choose from a wealth of software solutions for system support. In contrast, administrators in the System i world and SAP support staff in this environment are often left to their own devices. Nevertheless, the special system architecture and the peculiarities of the DB2 database integrated in the operating system, as well as the specific applications, also pose challenges for system tool developers.
Preparation before system copy - All information about transport requests that should be re-imported on the target system of the system copy is evaluated and collected: Already released transport requests that have not yet landed on production. Open transport requests that should survive the system copy (maintain development status). The respective owners of the transports have the possibility to discard an obsolete development.
Challenges reduced!
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.
Typically, the "homogeneous SAP system copy" process involves a large number of manual activities. A certain skill level is required for this, which leads to the fact that usually the employees of the SAP Basis department or external service providers realize the system copy. Depending on the structure and size of the systems, this process can take anywhere from hours to several days. In addition to making the target systems unavailable to operations and project teams, system and landscape copies also block SAP Basis administrators. Other challenges include the varying duration and quality (completeness) of the results depending on the processor, time dependency on the employees performing the work, etc..
Use "Shortcut for SAP Systems" to make a required SAP system copy easier and faster.
Backup / Restore: If the source system must not fail, eg to copy the database files, one can create an online backup of the database, copy the backup files to the new server and perform a restore before performing the SAP installation over the existing database.
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.