SAP system copy Re-import backup transports (exports), set up locally in 000 client for isolated systems (sandbox) - SAP Basis

Direkt zum Seiteninhalt
Re-import backup transports (exports), set up locally in 000 client for isolated systems (sandbox)
This is why companies need professional test data management
Database: For some databases (MS SQL Server) there is the possibility to copy the database files and reattach them on the target system. For the following SAP installation you only have to specify that no SAP loads should be used, but that the database is already there!

The guideline that integrated job logic is preferable to customizing has also proven its worth. The key point here is that each step of a copy job knows the overall context, including the steps that preceded and follow it.
SAP system clone and copy
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.

While homogeneous SAP system copy expects identical combinations of operating/database systems on the source and target systems, there is also a requirement for different combinations of operating/database systems on the source and target systems in the project environment (eg, during migrations). This is referred to as a "heterogeneous SAP system copy". Technically, it is quite possible to build up a degree of automation here as well, but officially certified consultants ("migration consultants") are required to perform the heterogeneous system copy.

With "Shortcut for SAP Systems", tasks in the area of SAP system copying are simplified and can also be automated via the command line interface.

To do this, however, the tools must contain the object dependencies for SAP's complex data model.

Often one is held up by troubleshooting.
SAP BASIS
Zurück zum Seiteninhalt