Recently I decided to change how often my db is automatically backed up.
I changed the "Backup every: X Hour(s)" parameter in Backup Schedule from 1 to 8.

Since then, backups are done every 1:15hs.
I have tried flushing caches and resetting the parameter but to no avail.

Any help on how to solve this is much appreciated.
Thanks in advance for your time.

Comments

realOFF’s picture

realOFF commented

Trying to solve this, I reinstalled the module the latest version.
I also created new profiles, locations and schedule but to no avail.
I have set backups schedule to 8 hours but files are generated every one hour.

Furthermore, I have found now that Backup & Migrate stucks my cron job every now and then for hours.
I have tried Poormanscron and server cron but the result is the same.
I'm starting to desperate now, because it was working fine until I changed the "Backup Every X Hours" option.

Help me please.
Thanks!

jshuster@drupal.org’s picture

jshuster@drupal.org commented

This might relate to an issue just posted at http://drupal.org/node/836742, which has to do with backup frequency, but in a different specific case. You might try applying the patch there and see if that fixes the problem.

Do post what you find out ... that'll help the module maintainer.

Mike Dodd’s picture

Mike Dodd commented

this may help

http://drupal.org/node/840272

OneTwoTait’s picture

OneTwoTait commented

I have the same issue.
I'm not doing multiple backups, just one.
It is set to backup the site every 6 hours. I found that it backed up the site 49 times yesterday.
I am using Supercron, could that be an issue?

ronan’s picture

ronan commented
Version: 6.x-2.2 » 6.x-2.4
Status: Active » Postponed (maintainer needs more info)

The patch @mike dodd points to above is in the latest recommended release. Can you guys tell me if the issue still exists in 2.4?

Thanks

kevinwalsh’s picture

kevinwalsh commented

on 6.x-2.4 i have mine set to backup once a day but it's backing up once an hour.

kevinwalsh’s picture

kevinwalsh commented

Turns out cron was failing (i think DURING backup_migrate part of cron, even though the backup tar.gz is in the scheduled backup folder). Forcing the cache to clear and then running cron (successfully this time) seems to have fixed the scheduling issue.

ronan’s picture

ronan commented
Status: Postponed (maintainer needs more info) » Fixed

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.