Planning Guide for the Connector for SAP Landscape Management
Easy integration also in the system copy of systems of older releases possible!
Until now, it has been common practice to create test systems as a client or system copy of the production system on a specific date. In these cases, a single client or the entire SAP system is duplicated. The corresponding instances of the SAP system have to be reinstalled. In addition, a copy of the source database must be created. These are standard procedures, but they can be disproportionately expensive for productive data sets of several terabytes. SAP and third-party tools for selective data extraction can significantly reduce the cost of deploying non-production SAP systems.
What is the purpose of copying a complete SAP system? - Well, there are several reasons. Test and development system: After a new productive system has been set up, at least one identical development system or even one test system is still needed. To avoid having to repeat the customizing (settings and configurations of the SAP modules and business processes) on these systems, it makes sense to make a copy. This is clearly the faster way to achieve the goal!
Create SAP HANA system replication levels
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.
"Shortcut for SAP Systems" provides an automated solution for many of the tasks involved in copying SAP systems by enabling the backup and restore of any table.
For information on installing and configuring SAP Landscape Management, see the latest SAP documentation on the SAP Help Portal.