Free mysql backup software for linux

MySQL Backup for lazy sysadmins (mysqlblasy) is a Perl script for automating MySQL database backups. It uses "mysqldump" for dumping mysql databases to the files sytem. MySQL Backup for lazy sysadmins program was written with automated usage in mind.
For example, it is silent during operation, and only produces noise on errors/problems. It rotates backups automatically to prevent the backup disk from getting full when the administrator is on vacation (or is lazy).
Main features:
- syslog facility
- unix output (loglevels, errors to stderr)
- dump some or all databases from a database instance
- compress dumps (using gzip,bzip2 or perl modules)
- backup rotation to avoid disc overflow
- no shell on external commands!
- can be run as unpriviledged user
- perfect for cron jobs

mylvmbackup project is a Perl script for quickly creating backups of MySQL servers data files. To perform a backup, mylvmbackup obtains a read lock on all tables and flushes all server caches to disk, makes an LVM snapshot of the volume containing the MySQL data directory, and unlocks the tables again. The snapshot process takes only a small amount of time. When it is done, the server can continue normal operations, while the actual file backup proceeds.
The LVM snapshot is mounted to a temporary directory and all data is backed up using the tar program. The archive file is created using a name of the form backup-YYYYMMDD_hhmmss_mysql.tar.gz, where YYYY, MM, DD, hh, mm, and ss represent the year, month, day, hour, minute, and second of the time at which the backup occurred. The prefix backup and the date format can be modified. The use of timestamped archive names allows you to run mylvmbackup many times without danger of rewriting old archives.
It is necessary to run mylvmbackup on the same host where the MySQL server runs. If your MySQL daemon is not listening on localhost, or using the default socket location, you must specify --host or --socket. Even though mylvmbackup communicates with the server through a normal client connection to obtain the read lock and flush data, it makes the backup by accessing the file system directly. It is also necessary that the MySQL server data directory resides on an LVM volume. (It is, however, a good idea to do the LVM backup to a different partition than the one where the data directory resides. Otherwise, there is a good chance that LVM will run out of undo space for LVM snapshot maintenance and the backup will fail.)
The user who invokes mylvmbackup must have sufficient filesystem permissions to create the LVM snapshot and mount it. This includes read/write access to the backup directory.
For proper operation mylvmbackup requires that Perl as well as the DBI and DBD::mysql modules. In addition, it uses several other programs: /bin/date to construct the archive filename, tar to back up data, LVM utilities to create and remove the LVM snapshot, and the system utilities mount and umount.
Enhancements:
- The "--innodb-recover" option was added, which provides an option to run InnoDB recovery on LVM2 snapshots (which provide write access to the device) prior to creating the backup archive.
- This speeds up resuming a MySQL instance from a restored backup.
- A bug with the default value handling for command line options was fixed. In version 0.4, if a config file was specified, default values in the script were all changed to blank.
- This means that the config file had to supply values for every variable instead of just the values that need to be changed from default.

Snap Backup is The One-Click Backup Utility that makes it simple to protect your important work. Snap Backup is for individual computer users who need a simple and convenient way to backup their valuable files.
Protecting Your Data Should be Easy
How often do you backup? How much work would you lose if your hard drive crashed right now? Snap backup makes it easy to frequently backup and archive your valuable data. Protect your work with Snap Backup.
Main features:
- One Click to Perform a Backup
- Configurable Settings
- Runs on Most Platforms (Including: Mac OS X, Linux, Solaris, and Windows)
- Supports Multiple Languages
- Its Free (No adware, spyware, or any other evil stuff)
The first time you run Snap Backup, you configure where your data files reside and where to create backup files. You can also specify an archive location, such as a USB drive or an Iomega Zip drive, for storing backup files.
Snap Backup automatically puts the current date in the backup file name, alleviating you from the tedious task of renaming your backup file every time you backup. The backup file is a single compressed file that can be read by zip programs such as StuffIt, gzip, and WinZip.
Take Control
Good system administrators have backup procedures for their company servers, databases, and network files. Individual computer users, on the other hand, are usually left to fend for themselves. Snap Backup is the simple answer for individual users, in the corporation or at home, who want to protect their valuable data.
For Everyone
Snap Backup is 100% Java and designed to run on any computer with Java. Snap Backup is free and is fully internationalized (meaning we just need to translate the words to support new languages). Please see the translation page if you want to help translate Snap Backup into your favorite language.

IAMBACKUP provides a set of classes for backing up and restoring a MySQL database.

IAM backup is package made of two classes. One performs the backup of the selected MySQL database, and the second restores the database.

Both classes support gzip-compressed files for improved performance. When performing the backup, the user is prompted to download the backup file, straight from the browser.

Alternately, the backup can be stored on the local server at a predefined location. Restoring the database (or copying it to another server) is just as easy.

MySQL wrapped is a C++ wrapper for the MySQL database C application programming interface.
Examples:
The following example should be linked with the mysqlclient library from the MySQL distribution / build.
#include
#include
#include
#include
#include "Database.h"
#include "Query.h"
int main()
{
Database db("localhost","dbuser","","testdb");
Query q(db);
q.execute("delete from user");
q.execute("insert into user values(1,First Person)");
q.execute("insert into user values(2,Another Person)");
q.get_result("select num,name from user");
while (q.fetch_row())
{
long num = q.getval();
std::string name = q.getstr();
printf("User#%ld: %sn", num, name.c_str() );
}
q.free_result();
}
Enhancements:
- This release adds methods to access fields by name.

Lazy Backup project is intended to be so easy even lazy people will do their backups.

Everyone is encouraged to make regular backups but how many of us actually do? Not only can it take a long time, but it can be complicated with a bunch of steps. Lazybackup is all about making it easy so that people will actually do it.

Current implementation

Started as a script to make my own backups easier there is a ready to use perl application available for download via sourceforge. It is works from the command line, and prompts users to do things like change disks. It should be a lot easier to use than the various steps that would need to be used to backup manually.

Technologies

Currently used

dar - disk archiver as the archive engine
dvd+rw-tools - dvd burning tools
perl - script engine

Planned

parchive - to recover from lost or damaged disks
GTK+/ GNOME - Optional super easy front end
curses - another optional easy to use front-end
c++ - Many of the programs lazybackup depends on are written in c++, and have libraries written in c++ that could make lazybackup more streamlined if used instead of invoking the command line programs.

Goals

Lazybackup has the ambitious goal of being the defacto backup tool of the gnome desktop when GNU/Linux becomes a mainstream OS of non technical people. Lazybackup also aims to appeal to admins via advanced scritability, and full functionality via command line, and library interfaces.

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.

ESR Backup is a simple easy to use backup system for UNIX and Linux. It provides a simple, easy to configure solution for file system integrity.
ESR Backup project works on an automatic 2 week cycle to assure you have an easy to recover system.
Main features:
- Simple and easy to configure
- Automatic 2 Week File Rotation Management
- Remote Storage via FTP
- Local File Storage
- Encryption with 448 bit Keys
- Completely FREE to use
ESR Backup takes the complication out of daily back ups, it does all the work for you so you can concentrate on more interesting things. ESR Backup automatically performs regular Full and Incremental backups on the following schedule
Monday - Full Backup
Tuesday - Incremental Backup
Wednesday - Incremental Backup
Thursday - Incremental Backup
Friday - Incremental Backup
Saturday - Incremental Backup
Sunday - Full Backup
It maintains 3 directories , current-week, last-week, and weekly-archives. After the full backup is performed on Sunday, it automatically rotates the last full backup from the last-week directory to the weekly-archive for safe keeping. It then removes the other archives because they are no longer needed.
It automatically rotates all archives from the current-week directory to the last-week directory. The current-week directory is then ready to hold next weeks backups. You always maintain 2 complete sets of backups. And all your old archives are ready to be stored on tape or CD or handled any way you choose.
ESR Backup provides you with remote archive storage via FTP so you can maintain current backup sets off site easily. If you dont have access to a remote FTP server , or do not wish to use one. ESR Backup can store archives on the local file system in a directory you choose. You can also encrypt your archives with a 448 bit encryption key.