Valeria,
I will dig into this as soon as I can. I’m sorry I didn’t notice it yesterday as I’m about to head out on vacation, but I’m putting this on top of my list.
Just to say, I have the exact same problem, and the exact same response from DreamHost support.
I have had no backups since April of this year. My Backup in Progress is grayed out.
There is no way I would have noticed this if it had not been for DreaHost changing where my buckets are.
Please, let me know if there’s anything I can do to help resolve.
FWIW, I turned on logging yesterday, and here is today’s log:
[2018/07/24 09:33:11] Beginning backup for agro.biodiver.se/2018-07-24-093311.zip ...
[2018/07/24 09:33:11] Leftover zip file found, deleting /home/wp_bewi5y/agro.biodiver.se/wp-content/upgrade/20344e3924c88bedd6485eb7667cc45a-dreamobject-backup.zip ...
[2018/07/24 09:33:11] ZipArchive found and will be used for backups.
[2018/07/24 09:33:11] Calculating backup size...
[2018/07/24 09:33:12] 1 GB of diskspace will be processed.
[2018/07/24 09:33:12] 11400 files added to backup list.
[2018/07/24 09:33:12] wp-config.php added to backup list.
[2018/07/24 09:33:12] A copy of .htaccess has been added to backup list.
[2018/07/24 09:33:14] SQL file created: /home/wp_bewi5y/agro.biodiver.se/wp-content/upgrade/85b714642a2a12c558d2433068907080-dreamobjects-backup.sql (53 MB) ...
[2018/07/24 09:33:14] SQL added to backup list.
[2018/07/24 09:33:14] Creating zip file using ZipArchive.
[2018/07/24 09:33:14] NOTICE: If the log stops here, PHP failed to create a zip of your wp-content folder. Please consider increasing the server's PHP memory, RAM, or CPU.
[2018/07/24 09:35:00] Calculating zip file size ...
[2018/07/24 09:35:00] Zip file created: agro.biodiver.se/2018-07-24-093311.zip (1 GB) ...
[2018/07/24 09:35:00] Deleting SQL file: /home/wp_bewi5y/agro.biodiver.se/wp-content/upgrade/85b714642a2a12c558d2433068907080-dreamobjects-backup.sql
[2018/07/24 09:35:00] Connecting to DreamObjects Server ...
[2018/07/24 09:35:01] Beginning upload.
[2018/07/24 09:35:01] File size is over 100megs, using Multipart uploader.
[2018/07/24 09:35:01] Preparing the upload parameters and upload parts in 25M chunks.
I’m really sorry about this. It’s related to the whole switchover to the new data center not being picked up correctly and I’m trying to make sure it works for everyone, which is much harder than it should be 🙁
I AM working on this, it’s just not going as fast as I wish it would. And yes, I’m the only developer.
Huh.
@unprocioneinansia how big is your backup?
@jeremycherfas has one over 100 megs, so I THINK that may be the same issue as someone else had.
Thread Starter
Valeria
(@unprocioneinansia)
Hi @ipstenu! thanks
1.3 GB. is it a problem? 🙁
Not your problem! Mine 🙂 Now I know what’s wrong! I’m on it!
Thanks for the update. Good to know you are working on it.
Good news! I have solved this problem. I’m going through the full barrel of testing, as the fix requires a little more re-engineering.
tl;dr? I didn’t test as fully as I should have the first time.
Longer answer. I updated the Amazon library for AWS in version 4.1.0 to make the plugin work with PHP 7 and up. In doing so, most things were deprecated but worked. Some were not, and Amazon didn’t make it very obvious what was and wasn’t. The specific function used for multi-part uploads, which is used when a backup is over 100 megs, was NOT listed as being removed.
[Picard Facepalm Meme]
Anyway, this is 100% my bad, I should have tested more, I apologize. I’ll have this fixed fully by Monday at the latest. I’m hoping to have it done by end of today.
Great news; will await further progress!
Okay! Pushed 4.2.0 this morning and it was able to backup a 700 meg file on my tests.
I’m really sorry about that. Amazon’s ‘documentation’ drives me to drink.
I have updated, but the immediate backup option is not available and I still see a message saying Backup in Progeress. It is grayed out.
I have a scheduled backup this time tomorrow. Will report back then.
The grey-out is really peculiar. I was never able to reproduce that one. I almost want to say you should reset the settings or, if you’re commandline/SQL savvy, kill the option for dh-do-backupnow
