Re-import backup transports (exports), set up locally in 000 client for isolated systems (sandbox)
Possibility of manual intervention in case of delta import
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.
Packages that have not been explicitly assigned a special DDLORA file receive the DDL file specified via the "ddlFile=" parameter. The default is DDLORA.TPL.
Scope of the SAP system copy
Even if the target system is not used for production in an update scenario based on a system copy, it is of central importance for developers and thus also the software lifecycle of the production system. That's why you should avoid upgrade downtime in both the production source system and the non-production target system. Production system downtime depends primarily on the method you use to create the image of the production data to be used in the target system. This image must be a transferable database image - for example, a database export, a backup copy, or an array-based reconciliation. To eliminate downtime in the production system and minimize the impact on application performance-regardless of the size of the production data reconciliation-you can use, for example, HP StorageWorks System Copy for SAP (HP System Copy), which has a disk array-based replication capability. Downtime in the target system depends on the following factors, among others: The time required to restore production data reconciliation in the target system The amount of pre- and post-processing in the target system With HP System Copy, images of production data can be created in minutes, with each step between shutdown and reboot of the target system occurring automatically. However, after the reboot, the target system is not immediately ready for use, as additional steps must first be performed (see description below).
Individual steps know exactly where they have to restart the actual copy run in the event of an error. In general, this means that error situations can be handled as needed and with pinpoint accuracy.
"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.
This is the case when dependencies of the source systems are also to be mapped in the target environments.
SAP Basis refers to the administration of SAP system that includes activities like installation and configuration, load balancing, and performance of SAP applications running on Java stack and SAP ABAP. This includes the maintenance of different services related to database, operating system, application and web servers in SAP system landscape and stopping and starting the system. Here you can find some useful information about SAP Basis: www.sap-corner.de.
If users have to shut down the productive system during the copy, the runtime of the operation or the unavailability of the productive system becomes a critical factor.