In the case of BSC, sophisticated mechanisms make it possible to exclude configuration errors, since relevant parameter settings are made automatically and according to predefined rules. For example, it is automatically recognized whether the system is an Abap, Java or double-stack system.
Shutting down and copying virtualized systems, such as VMware instances, requires just a few mouse clicks. VMware is suitable for running multiple training, development and test environments on one physical system. Larger productive systems, on the other hand, are not so easy to virtualize. If users have to shut down the productive system during the copy, the runtime of the operation or the unavailability of the productive system becomes a critical factor.
DB-specific methods: - for DB-homogeneous system copies - no Unicode conversion possible!
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.
One of the most common methods of creating an SAP system copy is to use SAP's own tool "BR*Tools". This tool provides the ability to create a backup of the database, which can then be used to restore the system. It can also be used to export certain data from the database and import it into another system.
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.
Disadvantages: - Potential load on the production system during IMIG - Additional resource requirements in the source system - Two systems running in parallel are needed (source and target system).
This requires time and resources in the source system.