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

Direkt zum Seiteninhalt
DB-specific methods: - for DB-homogeneous system copies - no Unicode conversion possible!
Solution Description
Creating a consistent storage replica - splitting a clone or creating a snapshot on the disk array. Regardless of the storage size, this process takes only a few seconds.

Checklist for preliminary work: Comparison of database sizes (target system must be the same or larger), comparison of database versions, kernel, host agent (ideally the same software version), dump of kernel files (export via SAPINST), saves download via SWDC, compile RFC connection passwords, inform third-party system administrators, provide memory, hard disk on the system for database and software import. Perform database dump, if necessary with transaction log, if possible with downtime, then without jobs or stop running jobs with report BTCTRNS1. Adminsitration passwords (DDIC, DB-Admin, Winadmin), create system snapshots (recovery), perform database import.

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.
Types of SAP system copy
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.

The solution does not use software agents. The use of standard protocols for the interaction of tool (client/server) and source system and tool with target system has proven itself, exclusively for the purpose of system copy creation. Whereby the use of a single point of management and control has also proven its worth.

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.

Another method of creating an SAP system copy is to use external tools such as Oracle RMAN or Microsoft SQL Server Backup.

Some useful tips about SAP basis can be found on www.sap-corner.de.


To ensure that SAP solutions are nevertheless used optimally, decision-makers are well advised to regularly subject IT landscapes and applications to intensive testing.
Zurück zum Seiteninhalt