Differentiation between homogeneous and heterogeneous SAP system copy
SAP system startup and shutdown, including virtual hosts
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.
Of course, time savings also mean money savings. In addition, these processes for system copying using such automation tools can be planned, standardized and always run at a high level of process quality. Especially the latter is of great importance in SAP Basis departments (and of course also for service providers).
SAP system update and database update
Unicode conversion: A Unicode target system is built from a non-Unicode source system. Unicode conversion can only be performed using procedures based on R3load.
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.
With "Shortcut for SAP Systems" the effort for many work steps is reduced. The work done by "Shortcut for SAP Systems" lies in the preparation and post-processing of the data - by backing up the system-specific data before the system copy and restoring it after the system copy. Efforts for preparation and post-processing are thus reduced to a minimum.
Internationally active companies that operate systems with several terabytes of data and hundreds of users in different time zones depend on high system availability.
So Windows remains Windows and Linux remains Linux.