SAP system deployment scenarios
Performing SAP system copies automatically
The process of creating system copies for updates can be broken down into different activities, as shown in Table 1. For each group, the software used for automation is shown, where "UC4" stands for UC4 Automated System Copy and "HP" stands for HP System Copy. All these activity groups are described individually below.
SAP environments can quickly become time-consuming. For example, when it comes to creating system copies of a production environment on the test and quality assurance (QA) system. Because of the time required, some QA systems turn out to be outdated and thus even ticking time bombs. A software tool from Libelle now makes it easier to update QA systems in SAP architectures on System i as well.
Create SAP HANA system replication levels
An SAP system copy is not done in an hour. Due to the large amount of data in an SAP system, the individual steps can take a long time to complete. The export and the import do not always run without errors. Often one is held up by troubleshooting. Of course, the target system must be prepared before the actual copy can be performed: Setting up the server, installing the operating system and database software, downloading and copying the installation media. During the export, the source system cannot be used. Therefore, this task must be planned well and in advance.
Installation continues until the 'Load Data' phase. Here the program waits for successfully exported packages and starts the import as soon as a package has been exported.
Tools such as "Shortcut for SAP Systems" supplement missing functions in the area of SAP system copy.
Here the program waits for successfully exported packages and starts the import as soon as a package has been exported.
For information from SAP about configuring and supporting the Connector for LaMa, see SAP Note 3078321.