SAP system copy and the cloud
Tools for SAP test systems
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).
Quasi tick boxes instead of time-consuming handling of programming lines, so that the use is also possible for less experienced experts who have never or only few SAP system copies created. And this after little system training.
To store all the information on the subject of SAP - and others - in a knowledge database, Scribble Papers is suitable.
This is why companies need professional test data management
Suitable tools make it possible to automate and accelerate the necessary creation of true-to-original SAP system copies, for example. This means that you have all production data available on your test system in a short time.
Strategy as of NetWeaver 2007: Prerequisite: in the case of a Unicode conversion, conversion must be performed during export. If the target database can be built with unsorted unloaded data, all packages are automatically unloaded unsorted. R3load ensures that tables that must always be unloaded sorted are unloaded sorted.
With "Shortcut for SAP Systems", tasks in the area of SAP system copying are simplified and can also be automated via the command line interface.
When the cause of an abort with error has been removed, the status in *state.properties can be set from '-' to '0', and the package will be processed again (i.e. exported or imported).
Some useful tips about SAP basis can be found on www.sap-corner.de.
Table splitting reduces the risk of losing a lot of time during export in case of an error.