Performing SAP system copies automatically
Consideration of additional QA clients
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.
You should also create a delta list for all transports that have not yet reached the production system. Software contained in open transports is lost during the upgrade, which may seem useful for cleaning up the system, but can have dire consequences for development projects. That's why you should take a close look at delta transport lists before proceeding with the upgrade. UC4 Automated System Copy allows you to automate the above steps. If necessary, you can add additional steps without losing testing capabilities.
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.
Differentiation between homogeneous and heterogeneous SAP system copy
Landscape copies refer to the update of not only one but a whole group of systems. This is the case when dependencies of the source systems are also to be mapped in the target environments. Similar to the simple system copy, the landscape copy also offers potential for automation, but this cannot be implemented by every tool on the market.
An alternative to this is a refresh using a client copy. The test environment will then be missing audit documents, among other things, but the development objects will remain untouched. The client copy only works from a running SAP system, but it burdens the system with database queries and transfers data more slowly than a system copy. The affected client is not available during the copy process. Since there are no options within the client to select what all should be copied, the runtime is often unacceptable.
Of course, time savings also mean money savings. In addition, these processes for system copying can be planned, standardized and always run at a high level of process quality using automation tools of this kind. Especially the latter is of great importance in SAP Basis departments (and of course also for service providers). With "Shortcut for SAP Systems", a number of activities in the context of system copies can be carried out and automated. Your SAP Basis administration is thus significantly relieved. Automation also means that SAP Basis Administrators no longer have to work unreasonable hours. The product can be integrated into almost any automation software.
SAP environments can quickly become time-consuming.
SAP Basis refers to the administration of SAP system that includes activities like installation and configuration, load balancing, and performance of SAP applications running on Java stack and SAP ABAP. This includes the maintenance of different services related to database, operating system, application and web servers in SAP system landscape and stopping and starting the system. Here you can find some useful information about SAP Basis: www.sap-corner.de.
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.