AutoArchive Changelog

What's new in AutoArchive 1.2.0

Apr 4, 2015
  • Running arbitrary commands before and after backup creation
  • New options --command-before-backup=COMMAND_BEFORE and --command-after-backup=COMMAND_AFTER were added. If specified the corresponding command is executed before or after each backup creation.
  • Refactored to make the architecture simpler
  • Applications is composed in more straightforward way, without Mainf framework. Component structure was impoved and several uneccessary interfaces were removed.

New in AutoArchive 1.0.0 (Aug 4, 2012)

  • The newly added option --remove-obsolete-backups, when enabled, backups
  • of levels higher than the current one are removed during backup creation
  • operation.
  • New option --quiet was added.If specified, only error messages are shown.
  • It has higher priority than --verbose.So if both are specified at the same
  • level (e. g. both are passed on the command line or both are specified in
  • the configuration file) then only --quiet is taken into account.
  • The List action now shows only selected archives also in case they are
  • orphaned.Previously all orphaned archives were always listed regardless
  • of which were specified on the command line.
  • Archive type “tarlzma” which was creating “.tar.lzma” backups is no longer
  • supported and was removed.Type “tarxz” supersedes it.
  • Implemented new behaviour when reading paths from archive specification
  • file – if a path in ‘include-files’ or ‘exclude-files’ variable is an
  • absolute path then the starting “/” is ignored.Likewise, for paths that
  • points to a parent directory the “..” is ignored.
  • Tar binary is searched in directories specified in PATH environment variable.
  • If not found there then it is searched in /bin, /usr/bin and /usr/local/bin
  • directories.
  • List operation returns exit code 1 if a warning or error occurs (for example,
  • if user pass a name of non-existing archive).Purge operation returns exit
  • code 1 if requested archive was not purged or other problem occurs.
  • If the archive specifications directory (which is by default
  • ~/.config/aa/archive_specs) does not exists, it will be created.
  • If the backup operation finishes with a fatal error the backup level is not
  • raised.Also no information (such as number of restarts, etc.) is stored in
  • that case.
  • If an orphaned archive is passed as the argument for List action it no longer
  • shows the error that archive specification file can not be found.The
  • selected orphaned archive is listed without errors.
  • The List operation finished prematurely after it attempted to list
  • a non-existent archive, which caused that remaining archives were not
  • listed.This was fixed so now it shows all selected archives even if
  • there are some non-existent ones among them.
  • If ‘include-files’ contained absolute paths and internal archiver was used
  • then the backup creation failed with exception 'RuntimeError: maximum
  • recursion depth exceeded while calling a Python object'.
  • It the backup creation—for the archive with ‘full-restart-after-count’ set—
  • was interrupted (e. g. by Ctrl+C) then subsequent attempts to create the
  • backup failed because the program crashed.
  • User documentation improvements:
  • Added examples on backup restoration to the user documentation.
  • Added description of the versioning scheme to the user documentation.
  • Short description of exit codes was added to the user documentation.
  • Refactoring of Archiving component.
  • Part of the Archiving component responsibility was moved to the newly created
  • Archiver service.