Hi,

I have cron set to run every hour via crontab. B&M is set to schedule a backup every 24 hours and keep 14 of them. After 3 days, the backup folder looks like this:

backup-2009-09-02T20-00-06.sql.gz
backup-2009-09-03T21-00-07.sql.gz
backup-2009-09-04T22-00-07.sql.gz

Which suggests backup are taking place every *25* hours. This is confirmed by the modified date stamp on the file (checked via FTP).

Not the end of the world. Thought I'd keep you posted.

Regards,

Tal

Comments

ronan’s picture

ronan commented

Backup and migrate will only run schedules when your cron is run and it will make sure a minimum of 24 hours has passed since the last run if that's the number you have in there. This means that sometimes by the time backup and migrate gets control during the cron run that it should run on, the time passed is ever so slightly less than 24 hours (by a couple of seconds, say) and then it has to wait until the next cron run to go. This may be what's happening to you.

I should maybe put in a little grace period, so if it's been 23hrs 59mins and 52 seconds since the last run, the module runs anyway to prevent the issue you describe.

Thanks
Ronan

talino’s picture

talino commented
Status: Active » Closed (works as designed)

I understand the problem. This is no big deal in my case.

Thanks.