Backup failed
-
When halfway through the backup, the window closed, and shortly after it reopen with the “There has been a hickup”.
The debug code is: BMI-83MUSCeZ-58222
-
Hi @andersgo
Seems like you have caching plugin which deleted some files during our backup process which cancelled the backup as file which was queued to be added to archive didn’t exist.
We have alternate backup method that should automatically detect such modifications and update queue accordingly during the process.
Alternatively you can also exclude cache path in our exclusion rules under “Exclude by directory path” the path to exclude is:
***ABSPATH***/wp-content/cachein your case.Please open first section of the plugin named: “What will be backed up?”
Find subsection named: “Exclude by folder / file name (case-sensitive)”
Here add these three rules, like on image: https://prnt.sc/9oftADPd_Z7eOnce you do that, please follow these steps:
- Go to “Other options” section
- Change backup method: https://prnt.sc/1s1ofpa
- Disable PHP CLI checking: https://prnt.sc/1sljr31
- Save “Other options” section
- Force stop both processes: https://prnt.sc/1trv1tm
When you do that, try to run your backup once again..
Let me know if that worked for you 🙂
Thank you!HI iClyde.
That seemed to work. Thanks a lot. 🙂
Best regards, Anders
Hi iClyde,
When I tried to restore the backup from my local site to my production site, there were no error message, but it seems that no changes has been made in the production site. So it seems it doesn’t work. 🙁
Best regard, Anders
Hi @andersgo
Could you please generate debug log of the external website as well?
To generate debug log follow this guide: https://prnt.sc/lKbjrSAqQudmFor now my assumption is that your wp-config.php file couldn’t be modified that’s why you don’t see any effects.
If the prefix was different and it couldn’t be replaced the website will still use the same database as before (so, no visible changes).
On the new website, open wp-config.php file and make sure the $table_prefix, variable is set to “clk_aa2e47e1c4_wp_”.
Another very important thing, I just noticed that the backup you’ve made was done on multisite instance. Before you restore multisite backups you need to configure and setup the multisite instance on new website.
No matter on which sub site you restore, it will replace everything.
Let me know if one of above assumption was the cause and if resolves 🙂
Thank you!Hi iClyde,
Thanks for your reply. It seems the the plugin, for some reason, thought that the database was not included in the backup file. I checked that the database was marked to be included on the locale PC, which it was. I even made a backup, where I unchecked the files, but it still made a full backup with the files and on the server it still omitted to restore the database. In the end, I made a manual export of the database, restored it, and changed all the locale url’s to the correct ones, and then it worked. Of course it would be better, it I didn’t need to do it manual next time. 😉
[STEP] [2023-02-22 22:55:35] Initializing restore process [STEP] [2023-02-22 22:55:35] Looking for PHP CLI executable file. [INFO] [2023-02-22 22:55:36] PHP CLI Filename: php [INFO] [2023-02-22 22:55:36] PHP CLI Version: 7.4.33 (cli) [INFO] [2023-02-22 22:55:36] PHP CLI Memory limit: 2048M/512M [INFO] [2023-02-22 22:55:36] PHP CLI Execution limit: 0/0 [SUCCESS] [2023-02-22 22:55:36] We properly detected PHP CLI executable file. [SUCCESS] [2023-02-22 22:55:36] PHP CLI: Restore process initialized, restoring... [SUCCESS] [2023-02-22 22:55:36] Restore process responded [SUCCESS] [2023-02-22 22:55:36] Locking migration process [STEP] [2023-02-22 22:55:36] Initializing restore process [INFO] [2023-02-22 22:55:36] Backup & Migration version: 1.2.7 [INFO] [2023-02-22 22:55:36] Initializing custom error handler [INFO] [2023-02-22 22:55:36] Site which will be restored: ***site_url*** [INFO] [2023-02-22 22:55:36] PHP Version: 7.4.33 [INFO] [2023-02-22 22:55:36] WP Version: 6.1.1 [INFO] [2023-02-22 22:55:36] MySQL Version: 5.7.40 [INFO] [2023-02-22 22:55:36] MySQL Max Length: 104857600 [INFO] [2023-02-22 22:55:36] Web server: Not available [INFO] [2023-02-22 22:55:36] Max execution time (in seconds): 259200 [SUCCESS] [2023-02-22 22:55:36] Restore process initialized successfully. [STEP] [2023-02-22 22:55:36] Free space checking... [INFO] [2023-02-22 22:55:36] Checking if there is enough amount of free space [INFO] [2023-02-22 22:55:36] Requires at least 286235970 bytes. [272.98 MB] [INFO] [2023-02-22 22:55:36] Disk free space function is not disabled - using it... [INFO] [2023-02-22 22:55:36] Checking this path/partition: ***ABSPATH***/wp-content/***backup_path***/backups [SUCCESS] [2023-02-22 22:55:36] There is 79,670.77 MB free. [77.8 GB] [SUCCESS] [2023-02-22 22:55:36] Great! We have enough space. [SUCCESS] [2023-02-22 22:55:36] Confirmed, there is enough space on the device, checked: 286235970 bytes. [INFO] [2023-02-22 22:55:36] Making temporary directory [STEP] [2023-02-22 22:55:36] Scanning archive... [INFO] [2023-02-22 22:55:36] Scan found 12574 files inside the backup. [STEP] [2023-02-22 22:55:36] Smart memory calculation... [INFO] [2023-02-22 22:55:36] There is 2048 MBs of memory to use [SUCCESS] [2023-02-22 22:55:36] Setting the safe limit to 342 MB [STEP] [2023-02-22 22:55:36] Extracting files into temporary directory (this process can take some time)... [SUCCESS] [2023-02-22 22:55:42] Files extracted... [STEP] [2023-02-22 22:55:42] Saving wp-config file... [SUCCESS] [2023-02-22 22:55:42] File wp-config saved [STEP] [2023-02-22 22:55:42] Getting backup manifest... [SUCCESS] [2023-02-22 22:55:42] Manifest loaded [INFO] [2023-02-22 22:55:42] Backup Migration version used for that backup: 1.2.7 [STEP] [2023-02-22 22:55:42] Restoring files (this process may take a while)... [SUCCESS] [2023-02-22 22:55:42] All files restored successfully. [INFO] [2023-02-22 22:55:42] Splitting process is disabled because v3 restore engine is enabled. [STEP] [2023-02-22 22:55:42] Checking the database structure... [INFO] [2023-02-22 22:55:42] This backup does not contain database copy, omitting... [STEP] [2023-02-22 22:55:42] Cleaning temporary files... [INFO] [2023-02-22 22:55:42] Removing 12577 files [SUCCESS] [2023-02-22 22:55:43] Temporary files cleaned [INFO] [2023-02-22 22:55:43] Restore process took: 7 seconds. [SUCCESS] [2023-02-22 22:55:43] Restore process completed [STEP] [2023-02-22 22:55:43] Finalizing restored files [INFO] [2023-02-22 22:55:43] Unlocking migration [END-CODE] [2023-02-22 22:55:43] #001 [DOWNLOAD GENERATED] File downloaded on (server time): 2023-02-22 22:55:49 [DOWNLOAD GENERATED] Last update (seconds): 6 seconds ago [DOWNLOAD GENERATED] Last update (date): 2023-02-22 22:55:43Best regards
Anders
Hi @andersgo
Could you please check if any database file is included inside the ZIP file?
– It should be under directory named “db_tables”.Regarding this matter, I don’t remember any similar issue in the past.
If you could generate debug code on the website where you created the backup it will be also helpful for me to debug the issue.
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 🙂
The topic ‘Backup failed’ is closed to new replies.
