Types of SAP system copy
Before shutting down the target system
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.
A SAN enables a system copy during dialog operation. In this way, virtual copies of a logical volume, so-called snapshots, can be created. Data is only copied if it is changed in the original data volume (copy-on-write procedure). When copying from a snapshot to file level, the affected systems remain available. However, this procedure puts a strain on the storage network. If this takes several days, the response times of the productive system deteriorate.
Planning Guide for the Connector for SAP Landscape Management
Database: For some databases (MS SQL Server) there is the possibility to copy the database files and reattach them on the target system. For the following SAP installation you only have to specify that no SAP loads should be used, but that the database is already there!
The freeware Scribble Papers puts an end to the confusing paper chaos. The tool is also suitable for storing, structuring and quickly finding text documents and text snippets of all kinds in addition to notes.
Advantage of the system copy: Users receive one hundred percent consistent test data. A disadvantage, however, is the high storage space requirement of such a test system, which corresponds to that of the productive system. In addition, an authorization concept for the system copy is required to protect the authentic data it contains. Otherwise, company secrets are at risk, and there is a violation of regulations such as the Federal Data Protection Act and the Sarbanes-Oxley Act.
With "Shortcut for SAP Systems", tasks in the area of SAP system copy are simplified and made possible.
The SAP system copies required for this are quite time-consuming and complex, but also offer very great automation potential.
So Windows remains Windows and Linux remains Linux.