Free mysql backup for lazy sysadmins software for linux

Hydra Backup System is a full backup system for UNIX-like systems.
Main features:
- Archives directories and stores archives on one or more FTP servers
- Includes a graphical client (built with the PyQT toolkit) and a command-line client for local or remote backup administration
- Control how often directories are backed up (daily, weekly, or monthly)
- Exclude directories from backups (e.g. backup /etc/ without backing up /etc/apache)
- Uses Pyro for client-server communication

MySQL Administrator is a powerful visual administration console that enables you to easily administer your MySQL environment and gain significantly better visibility into how your databases are operating.
MySQL Administrator now integrates database management and maintenance into a single, seamless environment, with a clear and intuitive graphical user interface.
By using MySQL Administrator you will be able to:
- Achieve higher database availability through improved management
- Reduce errors through visual database administration
- Lower database administration costs through improved productivity
- Deliver a more secure environment through easier privilege management
MySQL Administrator enables developers and DBAs to easily perform all the command line operations visually including configuring servers, administering users, and dynamically monitoring database health.
Other common administrative tasks such as monitoring replication status, backup and restore, and viewing logs can also be performed through the MySQL Administrator graphical console.
User Administration in Minutes
Administering users, granting privileges and viewing user privilege information has never been easier! Now you can leverage the full power of MySQLs user management and privilege capabilities to fully protect your MySQL server host using an integrated graphical user administration console.
For example, a form-based interface provides a simple method for adding users, assigning passwords and including user profile information. Plus, assigning and revoking global, database, and table/column privileges is as easy as adding and removing privilege items from an available list. Finally, an explorer interface provides a hierarchical view allowing you to easily view user privileges by privilege type.
Single View Dynamic Health Monitoring
Dynamic health monitoring gives you an immediate view into the key indicators of the health of your MySQL environment. Dynamic graphs enable you to easily view percentage of memory usage, connection usage, hit rates, as well as the number of SQL queries on an ongoing basis, as your system runs.
The Disk Health tab gives you an overview of the amount of hard disk space, tablespace, and log files being used. You can also use the visual health monitoring feature to get a hierarchical view into status and server variables such as the number of outstanding connections, number of bytes sent and received by clients, buffer allocations size and more.
Quickly Optimize MySQL
MySQL Administrator now allows you to easily view and setup key parameters so you can quickly optimize the performance of MySQL. Using a graphical forms-based environment, you quickly fine tune general and advanced parameters. For example you can set memory usage parameters and configure server start-up parameters related to the MyISAM and InnoDB table types.
Rapid Disaster Prevention and Recovery
Now you can rapidly create consistent backups and restore data by simply visually selecting the schemas and tables you want to back/restore from your hierarchical data directory. The graphical environment gives you additional visibility into Tabletype, Rows, Data Length, and Update time.
Server Information At-a-Glance
The server information section of MySQL Administrator allows you to quickly view basic information about the server and client. This view gives you immediate visibility into items such as server status, client and server version numbers and IP address, as well as connection information.
View Replication Status
Now you can quickly set up replication to increase the robustness and speed of your MySQL environment. The replication features within MySQL Administrator allow you to easily view the network topology of your replication master and slaves. Plus, the graphical environment provides additional visibility into IP addresses and logfiles.
View Server Logs from a Centralized Administration Environment
Now you can view all the MySQL log files including error logs, binary logs, and InnoDB logs from a single, centralized administration environment so you can diagnose server problems quicker and track database changes.
Service Control
Gain complete control of service creation and overcome the time consuming task of installing and setting up services. Plus, start and stop MySQL servers and view corresponding log messages.
Browse Catalog
Browse your catalog and view corresponding tables with columns, all indices and users with privileges to access selected databases. From here you can monitor and optimize tables.
Cross Platform
MySQL Administrator will initially be available for Microsoft Windows and Linux, and be compatible with MySQL version 4.0 or later.

aB Backup Tools is a toolset for creating and maintaining backups and recoveries of important data on your system.
Enhancements:
- memory leaks fixed,
- options optimized,
- some look changes.

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.

Mysql Assistant is a MySQL viewer. Mysql Assistant requires Ruby-Gtk2 and MySQL/Ruby.

Myassistant is a MySQL viewer using, Ruby, Ruby-Gtk2, MySQL/Ruby and developed on ruby-1.8.4, Mysql-5.0.16, mysql-ruby-2.7, ruby-gtk2-0.14.1.

Currently 3 APIs are provided for MySQL, MySQL/Ruby, Ruby/MySQL, and DBI.
These are 3 different APIs, Please install proper one.

Installation:

untar package anywhere you want.

Security Issue

Myassistant create ".mydb" file which includes "Mysql server name","user name",
"password","database name" with chmod 600 on your home directory.
It could be your security hole, so please notice that.

Fonts

Currently default font is "Sans 12". If you want change it, edit row number 91.

If you have any questions or problems, please let me know.

Browseable Online Backup System (BOBS) is a complete online backup system. It uses large disks for storing backups and lets users browse and restore the files using a webbrowser.

Files are fetched from other computers and stored in directories on the computer where bobs is installed.

Two types of file stores are used:

"Current" is the files from the remote computer as they were the last time the backup was run.

"Incremental" is the files that are deleted or changed on the remote server.

When a backup is run the files that have changed or have been deleted are moved to the "incoming" dir. From here they are tagged with a date and moved to the "incremental" dir.

Users interaction:

If a user deletes or corrupts a file and need it restored they can do this by opening a browser (any browser which supports frames should be fine) and pointing it at the
backupserver where bobs is installed.

On the backupserver they can login in using a password defined by the admin. For clarity that should be the same as the one they use on the server where the file
they deleted or corrupted is/are located.

Users can browse, search and select files to restore. They cannot see the contents of the files. Only name, date and size.

When they have found the files they need and added them to the restore list, they activate the restore process and wait for files to be transferred to their server where they can access them as they would any other files.