Tools for SAP test systems
Job logic instead of customizing
On the other hand, such a tool must ensure that traceability or transparency is always available. What happens in the smallest detail during an SAP system copy creation must be visible in whatever form in order to be able to track down possible errors, but also, for example, to optimize the actual copying process or to accelerate it even further, for example by using log files and more.
Depends on the extent of splitting and the degree of parallelization. When importing, the limiting factor is often the index structure.
Consistency of database disk blocks - stopping I/O activities or executing DATABASE BEGIN ONLINE BACKUP command, flushing cache, etc.
Administrators and SAP maintainers in the x86 world under Windows and various Unix derivatives can nowadays choose from a wealth of software solutions for system support. In contrast, administrators in the System i world and SAP support staff in this environment are often left to their own devices. Nevertheless, the special system architecture and the peculiarities of the DB2 database integrated in the operating system, as well as the specific applications, also pose challenges for system tool developers.
So much information... how can you keep it so that you can find it again when you need it? That's what Scribble Papers is great for.
A SAN enables a system copy during dialog operation. In this way, virtual copies of a logical volume, so-called snapshots, can be created. Data is only copied if it is changed in the original data volume (copy-on-write procedure). When copying from a snapshot to file level, the affected systems remain available. However, this procedure puts a strain on the storage network. If this takes several days, the response times of the productive system deteriorate.
"Shortcut for SAP Systems" offers the possibility to backup and restore any tables. Not only those that are considered in the PCA tool (Post Copy Automation) but also self-developed tables. Thanks to the simple and clear interface, backup and restore of self-developed tables can be integrated quickly and easily. The command line interface can also be used to automate the process: for example, a simple line command can be used to perform a complete backup of table contents before the system copy, and a simple line command can also be used to restore these tables after the system copy. This means that the complete backup or restore process can be integrated into any automation software.
Heterogeneous system copy (migration): During the copy, either - the operating system (OS migration) or - the database system (DB migration) or - the operating system and database system (OS/DB migration) are changed.
As a result, business processes can be made more agile, risks can be reduced, and the workload of IT administrators can be reduced.