Hi guys. I can't see this problem in the queue anywhere or on Google but roughly 3/4 of sites' Scheduled Backups stopped backing up entirely from since the 7.x-3.0 upgrade. Is this a known problem? And will disabling and creating a new regular backup fix the issue?
All our Drupal sites are hosted on the same servers/vps set-ups and are all regularly patched etc - but from the date we patched (from 7.x-2.8 from memory) to 7.x-3.0 the scheduled back-ups possibly stopped backing up on all sites (we have roughly ten commercial sites under management) and certainly 3/4 have no current scheduled backups showing (on the restore tab, that is).
Of course, Sod's Law, this has only just come to light now we need to sort-out the mess created by latest sql injection attack scenario (PSA-2014-003 https://www.drupal.org/PSA-2014-003) and we're missing critical backups on these sites from just before October 15th.
Thanks in advance for any feedback/advice.
Q.
| Comment | File | Size | Author |
|---|---|---|---|
| #2 | Screen Shot 2015-01-06 at 10.53.35 AM.png | 30.91 KB | kbrinner |
Comments
Comment #1
tobiberlinI found the same with a project where Backup / Migrate 3.0 was newly installed... although the schedules are activated with the checkbox and a period is chosen every schedule shows "none" on the schedules overview table under "Frequency" column.
I just re-saved the schedules and now I see the right frequency under the corresponding column - I will see if the backups will be processed.
Additionally I can not access the destinations page: it is not shown in the menu and when I click on "Add new destination" on the schedules settinfs page (admin/config/system/backup_migrate/destination/add) I see the admin/config/system/backup_migrate page
Comment #2
kbrinnerI too am observing this. I had scheduled backups to AWS S3 running without any issue until I upgraded to 3.0.
When I check the schedule at admin/config/system/backup_migrate/schedule I can see that the scheduled backups haven't run since the update was performed. They used to run every week, but they haven't run since 12/14/14 (almost a month ago as of this posting). When I edit the schedule I can see it is enabled, and scheduled to run every 1 week, and to be run when cron runs. If I check the website status at admin/reports/status I see that cron has run in the last couple of days, so it's not that cron isn't running. If I tell the backups to run manually at admin/config/system/backup_migrate they backup to S3 just fine, so it's not a connection issue with Amazon. All modules and Drupal core are at the latest versions.
Let me know if there is any more information you need to figure out this issue.
Comment #3
quantos commented@Kbrinner. That's what I found and don't know what the real problem is, I never found out, but tobiberline is correct "I found the same with a project where Backup / Migrate 3.0 was newly installed... although the schedules are activated with the checkbox and a period is chosen every schedule shows "none" on the schedules overview table under "Frequency" column." I.E. If you update your existing schedules and re-save you see the frequency will update and you'll know the new schedule is working fine again.
It seems that 3.0 series needs some additional hand-handling when updating from previous versions.
Q.
Comment #4
vegardjo commentedI can confirm this: "although the schedules are activated with the checkbox and a period is chosen every schedule shows "none" on the schedules overview table under "Frequency" column."
Resaving the schedule fixes the problem. I'm setting this to critical as it breaks essential functionality.
Comment #5
seren10pity13 commentedSame here. Totally agree with vegardjo :
We have a several websites including a very active news website that have no backups for 3 months ! Hopefully, we have other server side backup schedules for files and db but every 2 weeks only. If we have had a server failure we may have lost 2 weeks of work from 5 people, at least.
I'll have to check all my websites to re-save the settings.
This is really a critical issue.
Comment #6
zwerg commented+1
Comment #8
ronan commentedI have fixed the update path so old schedules should migrate correctly now. You should definitely check the frequency of the schedules on your site after you update if you have had this issue before.