Differentiation between homogeneous and heterogeneous SAP system copy
SAP Landscape Copies
SAP offers its own solution for this: With the Test Data Migration Server (TDMS), individual tables can be selected and written indirectly, via a third SAP system, from the source to the target system via Remote Function Call (RFC). However, the selection of business objects is not possible in the standard system. The tables to be copied can only be determined on the basis of the date. The content restriction applies from a certain point in time. At least the SAP tool can be used to reduce the runtime of an extraction of test data compared to the system copy or client copy.
Security-conscious companies usually keep their mission-critical IT infrastructures redundant anyway. Storage systems are usually secured in disk arrays by multi-level raid, spatially separated from each other and networked by a storage area network (SAN). Connected to this are at least two computers, also spatially separated. One of these acts as a backup system.
Before shutting down the target system
Basically, a distinction is made between the initial setup and refresh of a non-productive SAP system. In the past, the cost of a refresh, i.e., updating the environment with new data, often corresponded to the cost of the initial setup. This also restricted the availability of the productive system, which is hardly tolerable for companies that operate internationally and in different time zones.
Test data is important for companies to eliminate risks in ongoing operations and to optimize systems or processes. But collecting this data can be challenging in times of Big Data and increased data protection, as well as due to complex IT structures.
Tools such as "Shortcut for SAP Systems" are extremely useful in SAP system copy.
This is also the case when switching from one Any DB to another or when moving from an Any DB to Hana.
The groups are defined in the same file where the order of the packages is defined.