SAP system copy DB-specific methods: - for DB-homogeneous system copies - no Unicode conversion possible! - SAP Basis

Direkt zum Seiteninhalt
DB-specific methods: - for DB-homogeneous system copies - no Unicode conversion possible!
SAP system clone and copy
We will be happy to advise you and work out the most suitable solution for you together with you - so that you profit 100% from Systemcopy as a Service. Contact us.

Such system copies, with their enormous manual effort and SAP checklists that are often hundreds of items long, must be performed before every refresh. Usually, three to four days have to be planned for this, during which the QA system - which in two-tier SAP environments is also the development system - is not available for the actual work. The delay is actually only caused by the meticulous matching of trivial things, such as directory names. Because such SAP system copies have to be created for each SAP application on the QA system and can thus quickly require dozens of system copies, they tie up a lot of resources and staff.
Synonym(s): SAP System Refresh, SAP System Copy, SAP Client Copy, SAP Client Copy, Landscape Copy, Landscape Copy
With Automated System Copy for SAP, an SAP system copy can be scheduled and executed in a parallel mode, which has the advantage of reducing manual intervention to a minimum. In addition, daily work can continue as normal. Rehau had already been using the software provider's Business Automation platform for cross-platform scheduling of complex job chains since 2004. The existing installation was expanded to include the module for creating SAP system copies.

After shutting down the target system, the technical system copy for upgrade 1 can be created at the infrastructure level. To automate the creation of the technical system copy for upgrade, HP System Copy can be used for the following steps.

"Shortcut for SAP Systems" offers the possibility to backup and restore any tables. Not only those that are considered in the PCA tool (Post Copy Automation) but also self-developed tables. Thanks to the simple and clear interface, backup and restore of self-developed tables can be integrated quickly and easily. The command line interface can also be used to automate the process: for example, a simple line command can be used to perform a complete backup of table contents before the system copy, and a simple line command can also be used to restore these tables after the system copy. This means that the complete backup or restore process can be integrated into any automation software.

Large or complex tables with an extremely long runtime can lead to a very long total runtime, even if a separate package has already been defined for the table.

Export and import statistics are created separately, as well as displayed in an overall view.
SAP BASIS
Zurück zum Seiteninhalt