| Age | Commit message (Collapse) | Author |
|---|
|
|
|
/etc/byteback/excludes file between runs can stop your next backup
completing.
|
|
We've switched the default from --delete-after to --delete-during.
The intention being that we'll free up space during the rsync run,
rather than having to wait until all data has transferred, hoping
it will fit before deletion.
|
|
If the /etc/byteback/pre-backup.d/ directory is present then
execute the contents.
|
|
This is required as we're essentially passing the value to the
command-line, via fork()+exec().
|
|
If the directory /etc/byteback/post-backup.d/ exists then run
all scripts in it, once we've completed our run.
|
|
Moved the functions to the top of the script, wrap the body
of the program in a test to ensure we're being invoked.
|
|
At the moment we kill the rsync if there is no I/O for the given
period (6 hours previously, 3 after this commit lands) and then
retry the rsync connection up to three times.
This meant that a backup could take no more than 3x6 = 18 hours
but that was too long. Now we'll be 3x2 = 6 hours and that should
be sufficient that transient failures are handled, but
never-gonna-complete cases fail in a timely fashion.
|
|
This is useful to speed up backups, because otherwise they will
be I/O-bound and the CPU-overhead is a net-win.
|
|
Rather than having a hard-wired value we now allow this to be
specified on the command-line:
--io-timeout=7200
Or in a file:
/etc/byteback/io_timeout
|
|
Now we use the utility classes we have to log errors to syslog.
|
|
|
|
|
|
|
|
|
|
|
|
|
