Problem/Motivation
Backup and Migrate run at arbitrary times. This can cause load on a site during a prime time.
Steps to reproduce
Set a scheduled backup. Notice the backup runs at an odd time.
Proposed resolution
Add a "Run after" time to the scheduling UI so we can set the time for Drupal cron to start including BAM tasks in the cron jobs. Add a run_after element to the config to set this. 0 would be default and this should result in no break in BC
Remaining tasks
None
User interface changes
Add a "Run after" time to the scheduling UI so we can set the time for Drupal cron to start including BAM tasks in the cron jobs
API changes
None
Data model changes
Add a run_after element to the config to set this. 0 would be default and this should result in no break in BC
Comments
Comment #2
frobThis is an issue that was brought up in the queue 12 years ago #313134: Allow setting scheduled time similar to cron job in that issue it was fixed with support for Elysa Cron.
The Ultimate Cron module has taken over for the Elysa Cron in D8 but the support over at Ultimate Cron is pretty slim --there hasn't been more than an alpha for years. And it is quite a huge module for something so simple. This can likely be solved with a few lines of code here, rather than requiring the inclusion of Ultimate Cron.
Comment #3
damienmckennaMoving 8.x-4.x issues to 5.0.x because the older branch is no longer supported.
Comment #4
danharper commentedI'm looking for something similar so that I can do weekly backups on the lowest impact time.
I have got around not having it in the UI by manually setting the last run timestamp so maybe that's an easy way around it?