Create SAP HANA system replication levels
Automatic determination of delta states after SAP system copy/recovery
For a long time, manual procedures dominated, supported by SAP (guidelines), in particular by predefined procedures and a large number of checklists. In many places, this was supplemented by scripts created in-house, which, however, only automated partial tasks/processes of an SAP system copy.
The steps to be taken before shutting down the target SAP system can be summarized as follows: Well before performing the upgrade, inform the target system users - especially project managers, developers, and testers - about the planned maintenance work via e-mail, SAP system messages, and/or a message at the system logon. Using the SAP transport system requires careful preparation so that software development projects can be completed as far as possible. Shortly before the start of the update, inform users again that maintenance work on the system is imminent and that they should log off from the target system. After logging users off and locking them out, download system-specific content from the target system database for customization (including security settings, Remote Function Call (RFC) targets, and operating modes).
Food for thought for another productive system: until when must the system be identical, keyword: transaction log
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).
The freeware Scribble Papers puts an end to the confusing paper chaos. The tool is also suitable for storing, structuring and quickly finding text documents and text snippets of all kinds in addition to notes.
As a rule, the SAP basis has to fulfill: to provide SAP system copies as quickly as possible for the increased usage purposes. The performance of modern tools has developed rapidly. An assessment of the current situation.
If you have used "Shortcut for SAP Systems" to save system-specific tables before the system refresh, several manual steps can be omitted - the data can be restored by restoring the data saved before the system copy.
This is done with SAP tools (SUM).
The website www.sap-corner.de offers many useful information about SAP basis.
Even companies that offer the setup of test systems as a service rarely do this for any SAP dataset.