Would it not be desireable to have a failed backup retried at the next cron run until it succeedes and not wait until the next scheduled backup time?

Comments

ronan’s picture

ronan commented
Status: Active » Closed (won't fix)

I'm not sure I agree with this entirely. If backup fails during cron then it will more than likely fail the next time it tries to run. If an admin has their cron running very frequently and backup and migrate is failing frequently, there could be aborted backup files building up and that could get very bad, very quickly.

I'm going to mark this as 'won't fix'. If you feel strongly about this, reopen the issue, but I'm not making functionality changes to the 1.x branch anymore, so if it does make it into the module it'll be in 6.x-2.x which is probably no use to you anyway.

spade’s picture

spade commented

Thanks Ronan,

your reasoning makes perfect sense, but is based on an unusual situation. If cron operates the way I have it, then the admin would get a warning email imediately and could intervene. If not and if cron runs at long intervalls there wouldn't be a backup in a long time.

There could be different reasons for a failed backup; maybe you could differenciate?

Why not make it an option one could choose?

Having it in the 6.x branch is okay with me, I'll grow into it ;-)

Kind regards,

Frank