Consistency of database disk blocks - stopping I/O activities or executing DATABASE BEGIN ONLINE BACKUP command, flushing cache, etc.
Solution Description
The third-party providers have adapted their tools to various special areas. For example, the "Clone & Test" tool from Pecaso, which is now part of Accenture, specializes in transferring data from SAP's HR module. In addition to HR data, the "Data Sync Manager" from the provider Epi-Use makes it possible to select additional objects from the areas of accounting and logistics. As with TDMS, "Infoshuttle" from Gamma Enterprise Technologies gives users the option of selecting any data from the SAP system. For transport, the tool uses Idocs, which, however, can only be used to transfer small amounts of test data. SNP's "Data Distillery" can either write extracted data directly into the tables of the target system via RFC or generate an export file that can be imported into target systems multiple times. In the source system, users can select by objects, processes and transactions. Further selection options, for example by organizational units or fiscal year, allow a percentage of the data to be filtered out of the system as consistent test data.
One example: In an SAP environment, a system copy must be performed for various reasons - until now manually. Such a copy is always required when the QA system of a multi-level SAP architecture has to be brought up to the status of the current production system: Be it for testing new applications or during a release upgrade, for maintenance purposes or for updating the quality assurance and test system. In principle, the task proves to be simple: All files belonging to the clean configuration and implementation of the SAP environment must be transferred from the productive systems to the quality assurance system in the correct order and in the correct directories.
Create SAP HANA system replication levels
When executing a system copy, all tables, processes, databases, etc. are taken into account when copying. Logical system names must also be converted (using the BDLS trasaction code). The process of a system copy usually does not change. If no structural changes have been made to the SAP systems involved, the process is even 100% identical. Due to the very high repeatability of the nevertheless complex process, it is advisable to automate it to a large extent.
With the definition of package groups, the parallel processing of packages can be configured beyond the definition of the order: All defined groups run in parallel to each other. For each group the parameters jobNum, taskArgs and loadArgs can be defined separately.
With "Shortcut for SAP Systems" a tool is available that simplifies the SAP system copy and offers additional possibilities.
In addition to the regular SAP infrastructure, the system copy solution requires a central management server for updates, on which the following software is installed: - HP System Copy - UC4 Automation Engine - UC4 Template libraries for UC4 Automated System Copy and HP System Copy The central management server, which can be a physical or virtual server, must be running Microsoft® Windows® Server 2003/2008.
However, after the reboot, the target system is not immediately ready for use, as additional steps must first be performed (see description below).