SAP system copy Re-import backup transports (exports), set up locally in 000 client for isolated systems (sandbox) - SAP Basis

Direkt zum Seiteninhalt
Re-import backup transports (exports), set up locally in 000 client for isolated systems (sandbox)
Shutting Down the Target System
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.

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.
SAP Landscape Copies
Installing the Connector for LaMa enables a Cloud Manager feature for Google Cloud in SAP Landscape Management. This guide does not provide instructions for installing, configuring, or operating SAP Landscape Management. For information on installing and configuring SAP Landscape Management, see the latest SAP documentation on the SAP Help Portal. For information from SAP about configuring and supporting the Connector for LaMa, see SAP Note 3078321.

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.

"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.

This solution can reduce the total cost of ownership (TCO) and the length of the SAP software lifecycle.

It can also automate tasks such as reorganizing spools and instructing transport managers to process the delta transport list.
SAP BASIS
Zurück zum Seiteninhalt