Releases

SafeKeep 1.5.1 was released Nov 15, 2020, which is based on Python 3, containing the following updates:

• Adds configuration options to handle different versions of rdiff-backup.
• Allows specifications of a tempdir.
• Minor bugfixes.

SafeKeep 1.5.0 was released Feb 23, 2019. This is rebase of the source to Python 3 with the same functionality as 1.4.5.

SafeKeep 1.4.5 was released Feb 10, 2019, primarily as the final Python 2 version, contains the following main features:

• Make ssh StrictHostKeyChecking configurable in safekeep.conf with 'ask' as default if not configured.
• Add make-target debsrc again.
• Fix compatibility issue with Python 2.4.

SafeKeep 1.4.4 was released Jul 9, 2016, containing the following main features:

• Fix error with key deployment reported by Bruce Cowan.
• Cleanup up some minor issues in the build and deployment process.

SafeKeep 1.4.3 was released Jun 19, 2016, containing the following main features:

• Updated server-side scripting and general cleanups of code and documentation.
• Documentation cleanup.
• Optionally remove CREATE DATABASE statement in dumps as proposed by Marco Bozzolan.
• Added configuration option to specify ssh-keygen settings.
• Attempt normal lvremove before invoking dmsetup for cleanup.
• Correct email subject for errors during list output.
• Added locking on the server to stop overlapping runs.
• Update documentation for SSH change.
• Support for SSH ed25519 keys, switch default key type to RSA from Alexander List.
• Added server side startup hook support.
• Fixed a couple of small bugs related to:
• report errors during server cleanups,
• missing remote scripts, and
• client errors not reported by server during cleanups.
• Sort entries based on IDs as proposed by Carl Franks.
• Applied long outstanding patches from 2014.
• Fix lvremove error as reported by Eric Aslakson
• Clean up html generation with patches from Stanislav Blokhin

SafeKeep 1.4.2 was released Jun 2, 2013, containing the following main features:

• Report setup errors in summary reports.
• Added a flag to disable a backup configuration file.
• Added new targets for building Debian source packages.
• A number of bug fixes for Python compatibility and other errors.

SafeKeep 1.4.1 was released Jan 19, 2013, containing the following main features:

• A major rework of LVM snapshot handling.
• Generate MIME emails with summary reports.
• Better handling of PostgreSQL passwords.
• Added ability to use LVM snapshots with XFS filesystems.
• Allow use of ~/.safekeep for non-root users.
• Allow default and automatic snapshot sizes.

SafeKeep 1.4.0 was released Feb 12, 2012, containing the following main features:

• Add the ability to store script files on either client or server.
• Rewritten snapshot creation to remove use of "rbind".
• Automatic cleanup on next run after an abort.
• Support of LVM tagging for snapshots.
• Better handling of messages and tracebacks.
• A number of other code cleanups and bug fixes.
• Updated minimum Python support to Python 2.3.

SafeKeep 1.3.3 was released Nov 22, 2011, containing the following main features:

• More fixes for dealing with LVM snapshots.
• Better handling of other failure conditions.
• Updates for Python syntax issues and changes.
• Allow specification of a sender address in e-mail messages.
• Better handling of ionice(1).

SafeKeep 1.3.2 was released Mar 28, 2011, containing the following main features:

• Fix a few serios errors preventing safekeep from running.
• More fixes for dealing with LVN snapshots, SSH key delivery.
• Fix a new typos and errors introduced in 1.3.1.
• Improved installation from source (aka 'make install').

SafeKeep 1.3.1 was released Nov 22, 2010, containing the following main features:

• Ability to nice(1) both servers and clients for nicer CPU behaviour.
• Ability to ionice(1) the server for nicer IO behaviour.
• Portability fixes to news versions of python.
• Much better reporting or messages, errors, etc from clients.
• Many cleanups, bug fixes, and smaller improvements.

SafeKeep 1.2.1 was released May 21, 2009, containing the following main features:

• Portability fixes to news versions of python.

SafeKeep 1.2.0 was released Mar 30, 2009, containing the following main features:

• Implement bandwidth limiting, based on trickle
• Add support for niced backup server (defaults to nice +10)
• External callbacks throughout the backup process
• Several minor improvements and fixes in usability
• We now backup all special files by default
• Add pass-through options for the DB dump command
• Allow passing the pgpasswd to PostgreSQL
• Avoid errors for mounts containing spaces
• Correctly handle LVM names that contain dashes
• Fix dopey MySQL dump.

SafeKeep 1.0.5 was released Oct 7, 2008, containing the following main features:

• Allow providing the password for the DB user used for the DB dump
• Add config option for passing additional flags to rdiff-backup
• Avoid backing up special files by default
• Avoid creating multiple LVM snapshots (avoids some LVM bugs)
• Add new --cleanup option to help recovery from crashes
• Make it easier to package on platforms that don't have asciidoc

SafeKeep 1.0.4 was released Feb 26, 2008, containing the following main features:

• Add options to allow the query of the backup repository
• Important fixes when dealing with snapshots
• Make it more compatible with Python 2.2 (more work remains)
• Avoid build-time dependency on asciidoc which depends on Python 2.3
• Add some clarifications to the documentation
• Add support for FreeBSD

SafeKeep 1.0.3 was released Oct 19, 2007, containing the following main features:

• Clarify licensing in lite of the new GPLv3 license;
• New --force option to handle unexpected problems with the data repository;
• Better logging and status handling when we invoke external commands;
• Clearer backup status on job end;
• A small packaging bug got fixes.

SafeKeep 1.0.1 was released Jun 17, 2007, containing the following main features:

• The safekeep user no longer requires a working shell;
• Add support for Fedora 7 to the testing script;
• Packaging improvements for integration into Fedora;
• Removed the old configuration migration scripts.

SafeKeep 1.0.0 was released May 16, 2007, containing the following main features:

• Tested support for database (MySQL and PostgreSQL) dumps;
• Small documentation improvements.

SafeKeep 0.9.3 was released Apr 27, 2007, containing the following main features:

• The safekeep account now uses /bin/bash instead of /sbin/nologin, this makes it possbile to deploy and manage the SSH keys needed for the backup process;
• Invoke rdiff-backup with the --force option when trimming old data, since there are cases where we can have multiple deltas outstanding;
• A number of logging bugs have been fixed, now the logs should look a bit better;
• Some documentation improvements.

SafeKeep 0.9.2 was released Mar 13, 2007, containing the following main features:

• Client configuration files have been moved to /etc/safekeep/backup.d, and have the extension '.backup';
• A new global configuration file has been added in /etc/safekeep/safekeep.conf;
• A number of command line options have been deprecated (-e/--email, -s/--smtp), and moved to the global configuration;
• SafeKeep now knows of the user under which the backup will execute, making it possible to better deploy keys, avoid the need to invoke safekeep(1) via sudo(8), and execute the backup as root if need be;
• Relative paths now have more intuitive behaviour;
• Some documentation improvements;
• Automatic migration of old configuration to the new format;
• A CRITICAL (e.g. data loss) race has been fixed.

SafeKeep 0.9.1 was released Feb 12, 2007, containing the following main features:

• Lots of documentation improvements;
• Prepare the RPMs for Fedora acceptance
• Automatic creation of data store directory
• A few bug fixes

SafeKeep 0.9.0 was released Feb 1, 2007, containing the following main features:

• based on rdiff-backup, a tried and tested backup solution
• fast and easy deployment, with no configuration stored on the backed-up boxes
• centralized configuration, with reasonable and useful defaults
• built-in support for LVM snapshots, PostgreSQL and MySQL dumps
• secure setup via SSH tunneling, with built-in key management
• binary packages for RPM and DEB based Linux distributions
• clean, easy to understand Python code-base