Copy only specific data
Automation of homogeneous SAP system copies
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.
The tools we use can be easily operated either in the cloud or on premise. For this, the SAP systems to be copied must allow access at operating system level. The typical cloud infrastructures, such as AWS or Azure, are not a hurdle for this service.
Consistency of database disk blocks - stopping I/O activities or executing DATABASE BEGIN ONLINE BACKUP command, flushing cache, etc.
Partial copies from SAP systems with the help of tools open up potential savings and in many cases make system copies and complete client copies superfluous. The ability to anonymize data reduces the effort required to comply with data protection regulations in training systems, for example. In addition, up-to-date, consistent test data improves the flexibility and quality of development and test environments. Users save money through reduced resource requirements.
Today, thanks to tools for creating SAP system copies, it is possible to create such system duplications practically at the push of a button, and that too in a very short time. Even several at once.
With "Shortcut for SAP Systems" a tool is available that simplifies the SAP system copy and offers additional possibilities.
A test environment that is as identical as possible to the production system is suitable for testing patches and release upgrades.
Creating a consistent storage replica - splitting a clone or creating a snapshot on the disk array.