Import of delta statuses after SAP system copy / restore
Copying needs to be done skillfully
A SAN enables a system copy during dialog operation. In this way, virtual copies of a logical volume, so-called snapshots, can be created. Data is only copied if it is changed in the original data volume (copy-on-write procedure). When copying from a snapshot to file level, the affected systems remain available. However, this procedure puts a strain on the storage network. If this takes several days, the response times of the productive system deteriorate.
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.
To store all the information on the subject of SAP - and others - in a knowledge database, Scribble Papers is suitable.
Scenario with system copies for updating
RFC data transfer was completed within 1 day. Effort decreases from 1st test to 2nd test to final copy.
Acceleration/table export: up to 4 times faster. The larger the table and the higher the effort for sorting, the greater the time gain during export.
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.
Specific SAP transactions are used to customize the system.
On www.sap-corner.de you will also find useful information about SAP basis.
A relatively comfortable way.