Just to make thing as clear as possible. The file name for the backups is like so:
“datenbank_2025-05-20_03-00-40…”
This is german and translates to:
“database_2025-05-20_03-00-40…”
Why, in god’s name, do you backup the file system into the database folder?
Thank you for so absolutely nothing. Now, I have to fix 100+ sites immediately that are in a critical condition, since ALL might have this problem.
-
This reply was modified 1 year ago by
cutu234.
-
This reply was modified 1 year ago by cutu234.
Plugin Support
Saransh
(@saranshwpm)
Hi,
We completely understand your frustration, and we’re truly sorry to hear this has happened.
Could you please confirm if the affected backup was created using a separate Database backup job in the new version? This will help us isolate whether the issue is specific to the new job structure or something else.
Also, the database is included as a .sql file without any name inside the backup archive.
The file is named .sql — with no filename before the extension — which makes it a hidden file on many operating systems. Depending on your OS, you may need to enable “show hidden files” to see it after extracting the archive.
Let us know if you checked that and still don’t find the database file.
Before updating to V5 I had two wonderfully working backups jobs. One for the file system and one for the database. This was f***up after the update. I had the (wrong!) impression that both jobs were merged into one. And I am pretty sure that I checked this for some sites. But now that I really NEED a backup: no luck. I have no idea why you would backup a SQL file without any name. Anyway, there is no such file in the folder.
I can’t even reactivate the plugin to investigate it further, since it breaks the site completely.
It is a mess of epic proportions!
Plugin Support
Saransh
(@saranshwpm)
Hi,
Just checking in—do you have any updates on this? The fatal error issue has now been resolved in the latest version, so we wanted to see if everything is working fine on your end.
If you’re still running into trouble or have any questions, feel free to reach out—we’re here to help!
Best regards,
The fatal error issue is resolved. Thank you very much for getting in contact with Mainwp. However, I’m still waiting for a version of Backwpup that will restore my V4 backup jobs.
These issues are still severe:
– Former backup jobs were merged to one single job.
– It’s not clear wheter everything is included in the backups. I would have to check each and every backup job.
– External cron jobs are removed
It is not an option for me to individually check and correct 100+ sites.
Plugin Support
Saransh
(@saranshwpm)
Hi,
Thank you for your follow-up, and we’re really glad to hear the fatal error issue is resolved.
Regarding the restoration of your v4 backup jobs — we’re working on a migration feature, but not all options will be carried over due to changes in how the new system works. So the best approach remains setting up the backup jobs from the latest version.
At the moment, there’s no easy solution other than reviewing each backup job manually to ensure everything is configured as expected. We haven’t received similar reports about incomplete backups, but we’ll keep an eye on it.
Your point about external cron jobs is valid — we’ve noted it and will discuss internally to see how we can address it in the future.
Thanks again for your patience and detailed feedback — it’s truly appreciated.
Plugin Support
Saransh
(@saranshwpm)
Hi,
Hope the issue may have been sorted after the recent conversations we had and things are working more smoothly now
For now I’ll go ahead and close this thread but if you run into any other concerns in the future feel free to open a new one anytime and we’ll be happy to help
