The system copy
Update more efficiently
Test data is important for companies to eliminate risks in ongoing operations and to optimize systems or processes. But collecting this data can be challenging in times of Big Data and increased data protection, as well as due to complex IT structures.
After shutting down the target system, the technical system copy for upgrade 1 can be created at the infrastructure level. To automate the creation of the technical system copy for upgrade, HP System Copy can be used for the following steps.
Hybrid: for example, the source systems on-premises and the target systems on cloud
Increasingly, ad hoc requests are coming from IT or SAP Basis to provide an SAP system copy as quickly as possible, for example of an SAP ERP, BW or HCM system. This often leads to special challenges due to a lack of resources or capacities.
The maturity and performance of automation tools for SAP system copying have evolved over a period of more than 15 years. The first tools for SAP system copy creation came from the mainframe environment.
"Shortcut for SAP Systems" can considerably simplify and shorten a number of activities within the scope of a system copy or a system refresh. By using this application in conjunction with the information on system-specific tables from the PCA tool, the system-specific data can be backed up and restored after the system copy / system refresh. As a result, many of the activities mentioned here regarding data backup / restore can be performed much more easily; the creation of screenshots and the subsequent manual restoration of the state documented in this way can then be completely eliminated.
Some useful tips about SAP basis can be found on www.sap-corner.de.
SAP upgrade: Before a very extensive SAP upgrade, you may want to test the run and analyze any errors that occur, especially if the development and test systems are not allowed to be down for too long.
That's why you should take a close look at delta transport lists before proceeding with the upgrade.