Back In Time

What if the external backup medium is offline?

Asked by buhtz

How dos BiT react (while an automatic job) if the external medium (maybe a NAS) where the snapshots should be stored is offline?

1.
Does it try it again in some minutes? Can I modify this try-again-intervall?

2.
Does it create an alarm for me about it?

Question information

Language:
English Edit question
Status:
Solved
For:
Back In Time Edit question
Assignee:
No assignee Edit question
Solved by:
Germar
Solved:
Last query:
Last reply:
Revision history for this message
Germar (germar) said : 		#1

If this is local mounted share or an external drive BIT will show a message and wait for 30sec for the drive to become available. If the drive is still missing BIT will exit and try again at the next scheduled time.

If you use an NFS through SSH mode and the remote host isn't available BIT will exit and try again next scheduled time.

Revision history for this message
buhtz (buhtz) said : 		#2

OMG. This kill the complete backup-concept.
But let me ask first

1.
Is there a way to modify the try-again-count? Maybe try it 5 times.

2.
Is there a way to modify the 30sec intervall between the tries? It is definitly to short to bring an USB and even more a NAS online (take ca 6 minutes).

If this behaveiour is not customizable it is a BUG.
When there is no success with a backup-job the BiT just restart the schedule intervall. Why? There is no reason for that.
I set BiT up (e.g.) to do a backup each 5 days. When there is no success after 5 days (no matter how often it tried!) it shouldn't never be allowed to restart that 5-day-intervall. It should try again endless (and inform the user) untill the backup-job is done.

Is there a way to setup BiT like that?

Revision history for this message
Best Germar (germar) said : 		#3

Sorry, that was only half the truth. The above behavior is only if you schedule BIT with the 'Every 2 hours' 'Every Week'... schedules. These are crontab schedules which only fire up once on the set time. Normally this shouldn't be a problem as BIT's main propose is to run e.g. every two hours.

If you set the 'Repeatedly (anacron)' schedule crontab will start BIT every hour (when set on weeks) and BIT itself will check if it is supposed to be run (check the timestamp of the last run). If a new snapshot failed for what ever reason BIT will NOT write a new timestamp and so it will try again next time (one hour later) to take a snapshot.

Revision history for this message
buhtz (buhtz) said : 		#4

Thanks Germar, that solved my question.

Revision history for this message
buhtz (buhtz) said : 		#5

Just for the future: Where can I get such detailed informations about BiT? I couldn't found something like that in the documentation.

Revision history for this message
Germar (germar) said : 		#6

Unfortunately nowhere. Documentation is one of the biggest construction site in BIT. It hasn't been updated since ~5 years. And to be honest, I'm not very interested in working on that. Still hoping, someone else would take that job ;-)