Restore takes allot of time and never finish

[2022-05-26 06:55:17] [LOG] Plugin has been activated
[2022-09-02 05:40:53] [LOG] Restoring site...
[2022-09-02 12:24:21] [LOG] Restoring site...
[2022-09-02 13:21:50] [LOG] Restoring site...
[2022-09-02 13:43:18] [ERROR] There was an error before request shutdown (but it was not logged to restore log)
[2022-09-02 13:43:18] [ERROR] Error message: mkdir(): File exists
[2022-09-02 13:43:18] [ERROR] Error file/line: ***ABSPATH***/wp-content/plugins/backup-backup/includes/extracter/extract.php|205
[2022-09-02 13:43:18] [ERROR] There was an error before request shutdown (but it was not logged to restore log)
[2022-09-02 13:43:18] [ERROR] Error message: mkdir(): File exists
[2022-09-02 13:43:18] [ERROR] Error file/line: ***ABSPATH***/wp-content/plugins/backup-backup/includes/extracter/extract.php|205
[2022-09-02 13:43:18] [ERROR] There was an error before request shutdown (but it was not logged to restore log)
[2022-09-02 13:43:18] [ERROR] Error message: mkdir(): File exists
[2022-09-02 13:43:18] [ERROR] Error file/line: ***ABSPATH***/wp-content/plugins/backup-backup/includes/extracter/extract.php|205
[2022-09-02 13:43:18] [ERROR] There was an error before request shutdown (but it was not logged to restore log)

[snip by moderator]

[2022-09-06 10:25:20] [ERROR] There was an error during restore process
[2022-09-06 10:25:20] [ERROR] Error message: Allowed memory size of 41943040 bytes exhausted (tried to allocate 1282048 bytes)
[2022-09-06 10:25:20] [ERROR] Error file/line: ***ABSPATH***/wp-includes/wp-db.php|2169
[2022-09-06 10:25:20] [LOG] There was fatal error during restore.
[2022-09-07 13:57:27] [LOG] Restoring site...

• This reply was modified 2 years, 2 months ago by Steven Stern (sterndata).

Hi @michelalshaer

My apologies for the delayed reply.

In the logs you shared, I can see only one real error:

(
[type] => 1
[message] => Allowed memory size of 41943040 bytes exhausted (tried to allocate 1282048 bytes)
[file] => ***ABSPATH***/wp-includes/wp-db.php
[line] => 2169
)

For future, please do not share your logs like that, especially when they’re long.

You can generate debug code here: https://prnt.sc/lKbjrSAqQudm
Such code will include everything that we need for debug.

In you case I assume, your server ran out of memory during search & replace step.
Solution for that would be to simply increasing memory in your php.ini config.

To confirm that I’d still need you debug code with after failed restoration.

We’re working on dedicated solution for this kind of issue, which will add batching for this step.

Otherwise, you may try to clean-up your database using some third-party plugins then making new backup or simply wait for new release that should be ready within week.

Let me know if any of above resolves your issue for now ??
Thank you!

As we didn’t hear any reply in last days.
I can assume that you resolved the issue.

Feel free to open new topic if I am wrong!
Thank you ??