Verification of source system status and infrastructure - analysis of software versions, database disk layout, system status, etc.
Critical factor: Availability
An SAP system copy is a process in which an exact copy of an existing SAP system is created. This copy can be used to run tests, perform development, or back up the system.
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.
Import of delta statuses after SAP system copy / restore
Another method of creating an SAP system copy is to use external tools such as Oracle RMAN or Microsoft SQL Server Backup. These tools allow you to create a complete copy of the database as well as a copy of the file system. However, it is important to note that special knowledge is required when using these tools to ensure that the backup is created correctly.
SAP production system copies are created for a variety of reasons, including: - Generating a new non-production system for short- or long-term use - Updating an existing non-production system An SAP system copy is called homogeneous if the source and target operating and database systems are identical. If this is not the case, the system copy is considered heterogeneous. Heterogeneous system copies or platform migrations are not supported by the HP StorageWorks System Copy software for SAP and are therefore not discussed further in this document. In addition, this document deals exclusively with system copies for non-production target systems. Overview of a homogeneous system copy Figure 1 shows copies of an SAP production system that are created for non-production systems. Some copies are short-term (ad hoc) in nature, while others are intended for long-term use. Note that when a long-term system is created from a system copy, a system copy may be needed for updates later in the system's life cycle. This adds the latest transactional data from the original production system. Given their particular importance, this document focuses on scenarios with system copies created for updates. Figure 1: Overview of scenarios with homogeneous SAP system copies Scenario with system copies for updates In order to meet constantly 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 production system with the appropriate updates as SAP transports.
For some time now, SAP customers have been supported in system copying by very powerful automation tools that can be used as needed, such as "Shortcut for SAP Systems". Nothing has to be installed in your SAP systems for this - no transport requests, no AddOns!
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.
Rework, a transaction checklist: SU01 Adjust DDIC PW, SM66 Check server instance distribution, SE38 BTCTRNS1 (schedule all jobs out), SM38 Suspend jobs, SICK SAP Consistency check, SM28 Installation rework, SE06 Installastion check, SLICENSE License check, RZ10 Delete profiles, create and import OS level, RZ04, SM63 Create operation modes (optional), SMLG Delete SAP logon groups, SE14 Delete table contents: from system specific tables (emails, monitoring), SE38 RSBTCDEL (delete background jobs), SE16N Match table entries (optional), RZ12 Maintain server groups, SM61 Job server groups, create servers, SM59 Delete RFC connections, , SCC4 / SE03 Edit system: Assign system type, create and name SALE logical system, SCC4 client setting, rename to current SYSNAME, convert BDLS original system, generate SGEN ABAP Load, set up SA36 standard jobs, regenerate STRUST certificates, set/adjust SE61 logon screen, DB02 database connection, maintain PW.
In addition, testing is complicated by the growing complexity of applications and IT architecture.