SAP system copy Automation tool reduces time required to create test environments

Direkt zum Seiteninhalt
Automation tool reduces time required to create test environments
SAP system clone and copy
Another method of creating an SAP system copy is to use external tools such as Oracle RMAN or Microsoft SQL Server Backup. These tools allow you to create a complete copy of the database as well as a copy of the file system. However, it is important to note that special knowledge is required when using these tools to ensure that the backup is created correctly.

Fact: BDLS is a kind of "time eater" for system copies (except when using Hana). An important first step is to integrate the BDLS run into the system copy. Once the copy is effectively through, the BDLS is automatically started.
Solution Description
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.

The number of R3load processes to be started in parallel is specified in the {ex|im}port_monitor_cmd.properties configuration file. The Migration Monitor stores the state of the export or import process in the {ex|im}port_state.properties file. For each package being processed, there is a = line.

With "Shortcut for SAP Systems", a mature and yet very cost-effective product is available that offers useful functions for system copies. For example, SAP system users can be backed up and restored. Likewise, system-specific tables can be backed up before the system copy and restored after the system copy. And all this can also be automated.

And last, but not least, such tools must allow for extensibility or enable customer-specific extensions/requirements, such as integration into a scheduler or consideration of SAP double-stack systems.

After shutting down the target system, the technical system copy for upgrade 1 can be created at the infrastructure level.
SAP Corner
Zurück zum Seiteninhalt