Support

Akeeba Backup for WordPress

#32015 – Akeeba Backup Site Restoration - Data Replacement Failed

Posted in ‘Akeeba Backup for WordPress’
This is a public ticket. Everybody will be able to see its contents. Do not include usernames, passwords or any other sensitive information.
Monday, 18 November 2019 03:45 CST
obios
Hi there,
I tried to restore a complete wordpress backup on an xampp installation because I have to do an update of the wordpress and I don't want to do this in the live system because there is also a woocommerce shop integrated. Akeeba Backup is working well, also the database restoration but the process of Data replacement went for hours and after that the "Data Replacement Failed".
When I went back to "Restoration and clean up" and clicked the button everything worked fine and the site seems to be ok but I am not sure now if it really is because of the error warning. Can you explain me, what it means with data replacement and how I can check if everything is really fine with the restored site?
Thanks for help, Ortrun

Custom Fields

WordPress version (in x.y.z format) 4.9.10
PHP version (in x.y.z format) 5.6
Akeeba Backup version (x.y.z format) 3.6.1
Monday, 18 November 2019 04:32 CST
nicholas
Data replacement goes through your database data and replaces any hardcoded references to the URL or file path of your old site with that of the new one. If that doesn't complete correctly your site is unusable. If your site works fine then you probably have nothing to worry about.

Go to a few of your WooCommerce products which were added at the beginning and a few added closer to when you took the backup. If they are all OK there's nothing to worry about. Most likely the data replacement stopped while going through WooCommerce's order information because of a bug in XAMPP.

Aside: XAMPP is using the non-thread safe version of the PHP executable when they should be using the thread safe one. This causes instability when running a lot of requests in a short period of time such as when taking a backup or, far more likely, when restoring a backup. You can work around that by increasing the minimum execution time in both cases. The exact reason why this works is really complicated and very technical, but a minimum execution time of around 5 to 7 seconds overcomes the reasons that cause PHP to crash on XAMPP (and WAMPServer which has a pretty similar setup). I've found that the most stable local server I can have on Windows is either IIS or a custom Apache installation but they are both more involved in setting up correctly.


Nicholas K. Dionysopoulos

Lead Developer and Director



🇬🇷Greek: native

🇬🇧English: excellent

🇫🇷French: basic



Please keep in mind my timezone and cultural differences when reading my replies. Thank you!



Monday, 18 November 2019 04:51 CST
obios
Thank you, this will help and I will check some links.
Also thank you for your assessment of the local server solutions, I will have a look for an alternative.
Kind regards, Ortrun



This ticket is closed, therefore read-only. You can no longer reply to it. If you need to provide more information, please open a new ticket and mention this ticket's number.

Support Information

Working hours: Typically we work Monday to Friday, 9am to 7pm Cyprus timezone (EEST). Support is provided by the same developers writing the software, all of which live in Europe. You can still file tickets, but we cannot respond to them, outside of our working hours.

Support policy: We would like to kindly inform you that when using our support you have already agreed to the Support Policy which is part of our Terms of Service. Thank you for your understanding and for helping us help you!