Long downtime, high costs
It’s then a choice between two evils. Testing with old data should always be a non-starter. You may well decide to go into production based on a flawless test in development, but problems can then still occur. Because, in part due to the complexity of the SAP system, the slightest difference or an update in the live environment – when compared to the non-production system – can lead to major, and therefore unpredictable, problems. In this case, your testing would be of no use.
You may then feel like carrying out a complete refresh before you start testing. This means that your entire dataset is transferred to the test environment in one go. However, it can be a costly and time-consuming process. In some cases, it can mean downtime for your system of as much as a week. Quite apart from the inconvenience to your business operations, you’re also making a mistake by copying a whole lot of data that you don’t really need. “If an SAP system has been running for 20 years, you have 20 years of data, but likely only the data from the past three to six months will be relevant for testing. Why replicate the data from all those other years?” says Casper Messchendorp, Account Executive at EPI-USE Labs.
Ctac can offer a solution for this problem in the SAP-certified Data Sync Manager (DSM) suite from EPI-USE Labs. DSM offers powerful options for copying, cloning and anonymising data. For example, you can ask the Data Sync Manager to only copy the relevant dataset to the non-production system, which will significantly reduce downtime. Schedule the synchronisation for Friday evening, and by Saturday everything is ready. This will save your organisation a lot of time and money. In many cases, you can save as much as 60% of the storage capacity.