Free to backup software for linux

Box Backup is an FREE, completely automatic on-line backup system for UNIX.
Main features:
- All backed up data is stored on the server in files on a filesystem; no tape or archive devices are used
- The server is trusted only to make files available when they are required; all data is encrypted
- A backup daemon runs on systems to be backed up, and copies encrypted data to the server when it notices changes
- Only changes within files are sent to the server, just like rsync
- Old versions of files on the server are stored as changes from the current version
- Behaves like tape -- old versions and deleted files are available
- Choice of backup behaviour, optimised for document or server backup
- Designed to be easy and cheap to run a server. Portable implementation, and RAID implemented in userland for reliability without complex server setup or expensive hardware. (optional)
Enhancements:
- The diffing algorithm was highly optimised for speed.
- Bugs were fixed. Solaris support was added.
- Portability improvements were made, including a new autoconf based build.
- Xattrs are supported on Linux and Darwin, which backs up resource forks under Mac OS X.
- Experimental features include keep-alive on long diffing operations, saving state for non-server use, a native Win32 port, and support for MinGW and MSVC under Win32.

Backup project adds instant version control to any file on a Unix system.

Do you hate *.bak and *.20050101 and *.cjn (your initials here) and *.do.not.touch files as much as I do? They litter your filesystem any time someone (and were all guilty of it) needs to back-up a file theyre working on.

But who ever comes back and cleans the mess up? At what point is an old backed-up file no longer needed? And what about when you need that backup file only to discover that its missing, or you didnt capture one because you didnt want to add clutter? Backup is my answer to all that. It adds instantly available, reliable version control to every file in the filesystem.

Backup is a lightweight interface to the Subversion svn_fs library. It uses the powerful version control software as a backend to a simple and minimalistic (though effective) user interface. It is designed for use on Linux/Unix (including OS X) systems as a method of archiving configuration files that change semi-frequently, but do not necessarily warrent their own version control mechanism or repository. Things like "/etc/hosts" or "httpd.conf".

It can create a backup of any file without having to import it first, without worrying about setting up new repositories, and (because it speaks directly to the FS layer) without littering hidden ".svn" (or even worse, visable "CVS") directories all over the place. It does this by using a single global "archive," which contains a filesystem that mirrors your root as you add to it. You can view the archive and restore files, do diffs, and move things around as necessary. For more complex administration, the archive is a standard Subversion file system which can be administrated with any compatable client (including the svn command line tools).

The current version is knocked together in Perl. Its alpha, but it is pretty functional... at least for a proof of concept. Eventually I plan to re-write it in C... but we all know about "the best laid plans." In the mean while, the Perl version does work... mostly. The only real trick is that you need to compile and install the Subversion bindings for it Perl. There are some other modules you may need as well, but theyre all fairly standard.

Usage:

You probably shouldnt if you youre doing mission-critical work. Its still alpha code after-all. But if you do decide to give it a spin, dont blame me for any breakage (the only thing that should damage existing files is the combination of -r and -o, which will overwrite during a restore).

NVnetbackup (Not Veritas netbackup) is a simple backup system framework for data in an SMB networked environment.
NVnetbackup can also be used for backing up local data. The primary focus of this system is the simple selection of data to be backed up and the security of said data.
It is also very portable because it relies on common Linux tools and its behavior is controlled entirely by a single and simple configuration file.
Usage:
./nvnetbackup [-p|-m|-u|-b]
nvnetbackup -p
prepares a drive to be used for NVnetbackup
nvnetbackup -m
mounts all defined shares
nvnetbackup -u
unmounts all defined shares
nvnetbackup -b
runs a backup
Setup:
Setup is fairly easy, all you need to do (as root) is this:
mkdir /etc/NVnetbackup
gzip -d -c NVnetbackup-release.tar.gz | tar xvf -
cd ./NVnetbackup
cp -R * /etc/NVnetbackup
Where "xx" is the version number. After you have extracted all the files in the tarball to /etc/netbackup, then edit the backup.conf file to your liking.
Enhancements:
- This release adds more documentation to the FAQ included in the HELP file.
- This addresses the issues with NVnetbackup not being able to backup files located on shares hosted on Windows machines that are locked or in use.
- This release details the requirements for using Microsofts "Volume Shadow Service" in conjunction with NVnetbackup in order to get around this.

DVD Backup is an unix shell script providing functionality for backuping files and databases (PostgreSQL, MySQL) on DVD discs.
DVD Backup supports multisession and incremental backups. Mail notification is also supported.
Enhancements:
- This release sends email notifications using netcat instead of telnet.
- There are more details about communication with the SMTP server, and configurable excluded files patterns.

dobackup.pl is a flexible Perl script to handle unattended incremental backups of multiple servers.
It handles multiple media sets with automatic media preparation and rotation, configurable what-to-backup, global per-host exclusion patterns, and user settable dont-back-this-up metafiles.
dobackup.pl goal is zero-maintenance, nothing to do except change the media when told (if that, even!)
Getting started:
Media preparation:
Each unit of media used for dobackup must be uniquely identifiable. To this end, dobackup looks for a file named "MEDIAUNIT= " on the disk (in the mount-point really) before starting the backup. The reasons are two-fold: 1) to ensure that a media unit is really intended for backups, so you dont wipe out something important by accident, and 2) to verify that proper rotation of media units has occurred.
To prepare each unit, format and mount it as usual, then:
# touch MEDIAUNIT=< tag >
# chmod 000 MEDIAUNIT=< tag >
where < tag > is equal to the unit name, e.g. "JAZ01".
If you have 4 JAZ cartridges, use names like JAZ01, JAZ02, JAZ03, JAZ04, then put each of these names in /etc/dobackup.conf, in the appropriate section. The names are really arbitrary. You could call the units "Larry", "Curly", and "Moe", if you wanted to, but they must be listed in the config file in the order in which they will be rotated. For example:
[MediaSet=JazSetOne]
Units=<<less