SAP system copy Import of delta statuses after SAP system copy / restore - NW Admin

Direkt zum Seiteninhalt
Import of delta statuses after SAP system copy / restore
Copying needs to be done skillfully
To meet ever-changing business requirements, a production system must be continuously developed and adapted after the initial installation. To do this, you need development, consolidation, and quality assurance (QA) systems that can provide the appropriate updates to the production system as SAP transports.

Security-conscious companies usually keep their mission-critical IT infrastructures redundant anyway. Storage systems are usually secured in disk arrays by multi-level raid, spatially separated from each other and networked by a storage area network (SAN). Connected to this are at least two computers, also spatially separated. One of these acts as a backup system.
Shutting Down the Target System
RFC data transfer was completed within 1 day. Effort decreases from 1st test to 2nd test to final copy.

So much information... how can you keep it so that you can find it again when you need it? That's what Scribble Papers is great for.


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.

With "Shortcut for SAP Systems" you get additional functions for the SAP system copy.

For in-house developments and third-party software, check whether there are system-specific tables for the programs that should be backed up.

SAP Basis is the foundation of any SAP system. You can find a lot of useful information about it on this page: www.sap-corner.de.

Such system copies, with their enormous manual effort and SAP checklists that are often hundreds of items long, must be performed before every refresh.
NW BASIS
Zurück zum Seiteninhalt