Create SAP HANA system replication levels
We take over your SAP system copies as a service
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!
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 system/instance move
Unsorted unloading: - By default, R3load sorts table data by primary key before export. This requires time and resources in the source system. Under certain conditions, this sorting can be omitted.
A non-production SAP system should also have the same repository status as the source system, regardless of the data transfer method chosen for the refresh. All the data that makes up an SAP system is stored in the repository. This includes, among other things, the definitions for the database fields and tables for master and transaction data.
With "Shortcut for SAP Systems" a tool is available that simplifies the SAP system copy and offers additional possibilities.
The SAP system copies required for this are quite time-consuming and complex, but also offer very great automation potential.
Nowadays, companies are required more than ever to react agilely and flexibly to the demands of the global market.