Posted by shaisamuel on February 1, 2012 at 10:07am
4 followers
| Project: | Backup and Migrate |
| Version: | 7.x-3.x-dev |
| Component: | Code |
| Category: | feature request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | closed (fixed) |
Issue Summary
My backup setting contains several backup steps (1-db, 2-files x, 3-files y,...), which are separat back schedule jobs. When cron is running (elysia_cron), all the jobs are defined as one cron job. It will be much more stable and easy to support if each schedule job turns to separate cron job.
Comments
#1
Same. Subscribing. Would be very nice to be able to define custom CRON string, like 0 2 * * * for 2am and whatnot. I'm going to look into posting a patch, because I'm getting stuck.
#2
I took a different track. I created a module called backup_migrate_stagger_schedule that exists to provide an alternative cron job. It's purpose is simply to break the foreach loop that runs through all eligible schedule jobs, such that one is run at a time until they are exhausted. You may have need of this if you are backing up multiple databases or filesets of large size, relative to your server resources.
Following install of this module, in Elysia Cron, I disabled the backup_migrate_cron, and enabled the backup_migrate_stagger_schedule_cron, running it every hour.
I have added some comments in the .module to posit that perhaps this limitation of simultaneously schedule jobs might be easily made a configurable option in the core module.
#3
That's a nice approach.
Also if you have Drush on your server, you can get more nuanced control by running backups directly with cron.
ie:
0 2 * * * drush bam-backup db scheduled#4
And now you can do the same with the elysia cron module
#5
Automatically closed -- issue fixed for 2 weeks with no activity.