Consideration of additional QA clients
Types of SAP system copy
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.
In SAP, the admin must be happy to build new landscapes so that testing, development and enhancement can take place. In a system copy, the approaches are as colorful and varied as the philosophies of the administrators. The important thing is to think about the target system before building it. After all, after the database is removed and the system is rebuilt, there will be two identical systems on the network.
Automatic determination of delta states after SAP system copy/recovery
Administrators and SAP maintainers in the x86 world under Windows and various Unix derivatives can nowadays choose from a wealth of software solutions for system support. In contrast, administrators in the System i world and SAP support staff in this environment are often left to their own devices. Nevertheless, the special system architecture and the peculiarities of the DB2 database integrated in the operating system, as well as the specific applications, also pose challenges for system tool developers.
The freeware Scribble Papers is a "note box" in which all kinds of data can be stored. It takes in typed texts as well as graphics and entire documents. The data is then organised in folders and pages.
The solution described in this document can be summarized as follows: The goal is to create a homogeneous copy of an SAP system. The source of the system copy is a production system. The target of the system copy is an existing non-production system. The focus is on a specific use case, a system copy created for updates. Backup and restore are performed at the SAN device level and supported by HP System Copy software. Pre- and post-processing is automated using the UC4 Automated System Copy for SAP solution. Thus, the proposed solution allows you to optimize the automation and acceleration of SAP system copies generated for upgrades and reduce IT administration costs. Automated, fast and powerful upgrade capabilities enable shorter and more flexible SAP software lifecycles, enabling more agile business processes.
With "Shortcut for SAP Systems" any tables can be saved and restored. This is especially useful in the context of an SAP system copy - quite a few tables are system-specific and must exist unchanged in the system after a system copy.Shortcut for SAP Systems uses R3trans - a utility from SAP that is essentially used in the Transport Management System (TMS) environment. With "Shortcut for SAP Systems" it is now also available outside the TMS and enables completely new and diverse application possibilities. Among others in the environment of a system copy. R3trans works database independent. I.e. even in the case of a system refresh from an SAP system with an Oracle DB to a system with HANA, the backup and restore process works!
This means that basic functions for monitoring, starting/stopping and administering SAP systems will be possible directly from the familiar interface.
Almost 4,000 employees worldwide access our SAP systems directly.