Question about backups
-
I would like to schedule multiple backups through the day rather than my current single backup. My concern here is what happens if the backups eventually take so long the current backup is not done before the next one is scheduled to start. I backup to wasabi and my network (for now) has am upload speed of 125Mbps. I'm looking to upgrade to symmetrical gigabit but I was just curious about how this would work given my current setup.
Like to backup tasks get put in a queue for instance? Or will the second one fail or just never start?
-
I would like to schedule multiple backups through the day rather than my current single backup. My concern here is what happens if the backups eventually take so long the current backup is not done before the next one is scheduled to start. I backup to wasabi and my network (for now) has am upload speed of 125Mbps. I'm looking to upgrade to symmetrical gigabit but I was just curious about how this would work given my current setup.
Like to backup tasks get put in a queue for instance? Or will the second one fail or just never start?
@atridad said in Question about backups:
My concern here is what happens if the backups eventually take so long the current backup is not done before the next one is scheduled to start
There is a lock which prevents multiple interfering jobs from running in parallel (see this code). This lock not only ensure multiple backups cannot run but also that other things like cloudron update, platform upgrade etc cannot happen in parallel.
Also, if you follow along the code, there is a 24 hour timeout for the backup job. So, it gets killed if it gets "stuck" and then next scheduled time will start another backup.
-
@atridad said in Question about backups:
My concern here is what happens if the backups eventually take so long the current backup is not done before the next one is scheduled to start
There is a lock which prevents multiple interfering jobs from running in parallel (see this code). This lock not only ensure multiple backups cannot run but also that other things like cloudron update, platform upgrade etc cannot happen in parallel.
Also, if you follow along the code, there is a 24 hour timeout for the backup job. So, it gets killed if it gets "stuck" and then next scheduled time will start another backup.
@girish Ahhh I see. Thankfully right now backups only take 3-4 hours. I'm hoping once I'm at gigabit I can speed that up. My network is definitely a bottleneck rn.
