SAP SYSTEM COPY - A BEFORE AND AFTER GUIDE
Consistency of database disk blocks - stopping I/O activities or executing DATABASE BEGIN ONLINE BACKUP command, flushing cache, etc.
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.
The Migration Monitor: is a standalone tool implemented in Java, takes over the management and control of the R3load processes, is downward compatible. Use the latest Migration Monitor version of the highest release!
What is System Copy as a Service?
Over 30 productive systems at more than 9 customers successfully copied using IMIG. For the Unicode conversion of a 4.5 TB system (2.7 TB data) a downtime of 16 hours was achieved (including the follow-up work such as reconfiguration, updating DB statistics, generating reports, creating backups, testing the system).
After restarting the target system The SAP target instance has been started with a database that has been updated with content copied from the production database using fast and scalable disk array replication. The status of the target system now allows it to run without severe internal errors and disruption to the SAP landscape. However, the system does not have the same identity in the SAP landscape as it had before the update. That's why post-processing is required. UC4 Automated System Copy can handle most of the post-processing by restoring specific database content customizations (such as security settings, RFC targets, and operating modes) that were downloaded before the upgrade. Another goal in post-processing is to change the production system's logical system names to those used by the target system. Since these names usually need to be passed to numerous tables in a given system that have not yet been customized, SAP has the BDLS transaction that can be used to safely analyze and change logical system names. UC4 Automated System Copy can automate and accelerate this transaction by analyzing the underlying processes and executing them in parallel. It can also automate tasks such as reorganizing spools and instructing transport managers to process the delta transport list.
A solution such as "Shortcut for SAP Systems" offers an automatable solution for many of the activities involved in an SAP system copy.
These tools allow you to create a complete copy of the database as well as a copy of the file system.
On www.sap-corner.de you will also find useful information about SAP basis.
So much information... how can you keep it so that you can find it again when you need it? Scribble Papers is a "note box" that makes this very easy.
To avoid having to repeat the customizing (settings and configurations of the SAP modules and business processes) on these systems, it makes sense to make a copy.