Mondane/timebackup — pull request #2 by rossica (2014-08-30 21:24:36+00:00)
Title: Rossica

1. Added support for unique log files for each backup. The goal is to prevent having one giant log file after a few months of back ups. To correlate any errors experienced with the backup folder that had the error, the log file date and folder date are the same.

2. The script will now link against any previous incomplete backup. If a back up client has a lot of data to back up and a slow upload speed coupled with unreliable internet connectivity, this will enable the client to complete their back up eventually.
Previously, the client would start from scratch every attempt, which means the client needs no (connectivity) issues for the (sometimes long) duration of the backup, in order to successfully back up any data; it's all or nothing. Now, if there is an error, or if the connectivity between client and server is disrupted, the next attempt will start with any unchanged files already uploaded.

3. Added support in the -v switch to have rsync also log to the timebackup log file. This may be handy for cron scripts.

4. Added the --stats switch with to rsync when being verbose because I'm a numbers geek :smile:

5. Fixed a small typo in the error text.

6. When backing up to FreeNAS, the observed behavior of finding files that are 0 days old in the hourly folder would lead to all backups being deleted from the hourly folder. This had the effect of deleting all backups, and thus none would get rotated from the hourly folder.

All changes tested with clients:
windows (7, 8.1) with cygwin,
ArchLinux.
Targeting a FreeNAS server.

Your thoughts, @Mondane ?