Plugin Support
Saransh
(@saranshwpm)
Hi,
Thank you for your feedback!
In the latest version of BackWPUp, the Backup History should indicate when a backup has completed with an error: https://shottr.cc/s/1Vi6/SCR-20260824-jjh.png.
Could you please let me know which version of BackWPUp you’re currently using?
If you’re already using the latest version, could you also share the backup log(after hiding sensitive information) where the error occurred but wasn’t reflected in the Backup History? I would appreciate it, as it will help us check whether there is a specific case where the error status is not being displayed correctly.
Best regards,
Hi,
Thank you for your answer. I am using version 5.7.5 and the backup was locally saved (not ftp). The backup failed because it reached the limit of retries. There was no indication, everything looked like it was successfully completed. Unfortunately I didn’t make a screenshot.
Plugin Support
Saransh
(@saranshwpm)
Hi,
Thank you for the clarification.
I understand now. The FTP example was just to show how the Backup History indicates a failed backup, while in your local backup case, the job failed after reaching the retry limit but appeared as successfully completed in the Backup History.
I wasn’t able to reproduce this behavior on my end so far. If you notice it again, please reach out with the related backup log and, if possible, a screenshot of how that backup appears in the Backup History.
We’ll be happy to check it further and report it to our developers if we can confirm the issue.
Thank you again for bringing this to our attention!
Best regards,
Hello,
The issue happend again:
[INFO] BackWPup 5.7.5; A project of WP Media
[INFO] WordPress 7.0.4 on ………..
[INFO] Log Level: Normal
[INFO] BackWPup job: Backup Now
[INFO] Logfile is: backwpup_log_b63c2d_2026-08-27…..html
[INFO] Backup file is located at: /home…..3_DBDUMP-FILE-WPPLUGIN.tar.gz
[27.08.2026 15:48] 1. Try to backup database …
[27.08.2026 15:48] Connected to database …. on localhost
[27.08.2026 15:49] Added database dump "….sql" with 177,96 MB to backup file list
[27.08.2026 15:49] Database backup done!
[27.08.2026 15:49] 1. Trying to make a list of folders to back up …
[27.08.2026 15:49] Added "wp-config.php" to backup file list
[27.08.2026 15:49] 3661 folders to backup.
[27.08.2026 15:49] 1. Trying to generate a file with installed plugin names …
[27.08.2026 15:49] Added plugin list file "…..2026-08-27.txt" with 3,83 KB to backup file list.
[27.08.2026 15:49] 1. Trying to generate a manifest file …
[27.08.2026 15:49] Added manifest.json file with 5,27 KB to backup file list.
[27.08.2026 15:49] 1. Trying to create backup archive …
[27.08.2026 15:49] Compressing files as TarGz. Please be patient, this may take a moment.
[27.08.2026 15:49] After restart on folder: wp-content/plugins/….
[27.08.2026 15:50] After restart on folder: wp-content/plugins/…..
[27.08.2026 15:50] After restart on folder: wp-content/plugins/….
[27.08.2026 15:51] After restart on folder: wp-content/uploads/….
[27.08.2026 15:51] After restart on folder: wp-content/uploads/….
[27.08.2026 15:57] WARNING: Job restarts due to inactivity for more than 5 minutes.
[27.08.2026 15:57] 2. Trying to create backup archive …
[27.08.2026 15:57] After restart on folder: wp-content/uploads/….
[27.08.2026 16:03] WARNING: Job restarts due to inactivity for more than 5 minutes.
[27.08.2026 16:03] ERROR: Step aborted: too many attempts!
[27.08.2026 16:03] ERROR: Job has ended with errors in 903 seconds. You must resolve the errors for correct execution.
And the Backup History does not not show any error.
Hi @ivomasterche
Thanks for sharing the log. The retries are triggered because BackWPup detects more than 5 minutes without activity while creating the backup archive.
In your case, this most probably happens while processing files in wp-content/uploads because your database is not too large (177,96 MB). This could be caused by particularly large/slow files, server resource or I/O limitations, or the hosting environment temporarily slowing down the process.
The log doesn’t show the exact underlying cause, only that the archive process stopped reporting progress for more than 5 minutes. We’d need more information about the hosting environment and the size/content of wp-content/uploads to investigate further.
Best Regards
