Projects

rdiff-backup

rdiff-backup backs up one directory to another, possible over a network. The target directory ends up a copy of the source directory, but extra reverse diffs are stored in a special subdirectory of that target directory, so you can still recover files lost some time ago. The idea is to combine the ... [More] best features of a mirror and an incremental backup. rdiff-backup also preserves subdirectories, hard links, dev files, permissions, uid/gid ownership (if it is running as root), modification times, acls, eas, resource forks, etc. Finally, rdiff-backup can operate in a bandwidth efficient manner over a pipe, like rsync. Thus you can use rdiff-backup and ssh to securely back a hard drive up to a remote location, and only the differences will be transmitted. [Less]

cobbler

Cobbler is a Linux installation server that allows for rapid setup of network installation environments. With a simple series of commands, network installs can be configured for PXE, reinstallations, media-based net-installs, and virtualized installs (supporting Xen, qemu, KVM, and VMware ... [More] Server). Cobbler uses a helper program called 'koan' (which interacts with Cobbler) for reinstallation and virtualization support. Cobbler can also optionally help with managing DHCP, DNS, power, config management, and yum package mirroring infrastructure -- in this regard, it is a more generalized "batteries included" deployment server, rather than just dealing specifically with installations. It has a command line interface, a web interface, and also several API access options. [Less]

MirrorBrain

MirrorBrain automatically redirects download clients (web browsers, download programs) to a mirror server near them. It works similar to the systems employed by sourceforge.net, mozilla.com or similar large organizations, which face a number of download requests which is too high to be practically ... [More] handled by a single site. To find a mirror close to the client, the redirector "geolocates" the client by its IP address. If several mirrors are found to be suitable, the redirector load-balances requests to the mirrors based on their capabilities. [Less]

mrepo

mrepo builds a local APT/Yum RPM repository from local ISO files, downloaded updates, and extra packages from 3rd party repositories. It takes care of setting up the ISO files, downloading the RPMs, configuring HTTP access and providing PXE/TFTP resources for remote network installations.

gtkrsync

gtkrsync is a simple GUI that displays a running status display built from rsync --progress -v. This status display includes a per-file and overall status bar, overall estimated time to completion, and an expandable button that shows all rsync status output. Unlike other GUI rsync frontends such ... [More] as grsync, gtkrsync does not have any GUI tools for configuring or invoking rsync. gtkrsync is designed to be invoked from the command line or shell scripts, which already specify all the needed rsync options. It is thus ideal for scripted rsync runs that need a GUI, or for command-line users that would like a GUI to monitor their rsync progress. [Less]

lsyncd

lsyncd - Live Syncing (Mirror) DaemonDescriptionLsyncd uses rsync to synchronize local directories with a remote machine running rsyncd. Lsyncd watches multiple directories trees through inotify. The first step after adding the watches is to rsync all directories with the remote host, and then ... [More] sync single file by collecting the inotify events. So lsyncd is a light-weight live mirror solution that should be easy to install and use while blending well with your system. See lsyncd --help for detailed command line options. License: GPLv2 or any later GPL version. When to useLsyncd is designed to synchronize a local directory tree with low profile of expected changes to a remote mirror. On the receivers side rsyncd can be configured to also change the uid/gid of the file. Lsyncd is especially useful to sync data from a secure area to a not-so-secure area (e.g. as a one way connection to allow employees to publish their files to a public accessible web server). When not to use: File with active file handles (e.g. database files) Directories where many changes occur (like mail or news servers) In these cases e.g. DRBD (see http://www.linux-ha.org/DRBD) might be better for you. Comparisons:Lsyncd vs. DRBD: DRBD operates on block device level. This makes it useful for synchronizing systems that are under heavy load. Lsyncd on the other hand does not require you to change block devices and/or mount points, allows you to change uid/gid of the transferred files, separates the receiver through the one-way nature of rsync. However when using lsyncd a file change can possibly result in a full file transfer (at least for binary files) and is therefore unsuitable for databases. Also a directory rename will result in transferring the whole directory. Lsyncd vs. incron: Incron does not (yet) support recursive directory watching making it unsuitable for described needs (http://inotify.aiken.cz/?section=incron&page=about&lang=en). In fact a different approach would have been to extent incron. However, we decided to stick to the NIH principle (Not Invented Here) :-), because extending the C++ solution seemed to tedious. Lsyncd vs. FUSE: Another interesting idea is to write a daemon that provides a shadow file system through fuse. When accessing a file the data is synced to a local file as well as a remote file. With this approach inotify could be replaced. BindFS (see http://www.cs.helsinki.fi/u/partel/bindfs/) does this for local mirroring. We discarded this idea because it would affect performance of normal operations in a negative way. Lsyncd vs. cron: If you find a solution using cron to call rsync over the whole directory tree periodically after every 'X' hours/minutes/seconds more satisfying than lsyncd, please go for it ''sulking''. We don't like it! Lsyncd usage examples/usr/sbin/lsyncd /var/www/ remotehost::wwwshare/ This watches and rsycn's the local directory /var/www/ with all subdirectories and transfers them to 'remotehost' using the rsync-share 'wwwshare'. /usr/sbin/lsyncd --nodaemon --exclude-from /etc/lsycnd/exclude /var/www/ remotehost::wwwshare/ This will also rsync/watch '/var/www', but it excludes files and directories from '/etc/lsycnd/exclude'. Additionally this example lsyncd will not fork, and log to stdout/stderr instead. Some more complicated examples, tips and tricks you can find in the [HowTos] section. Source DocumentationThe only file of interest is 'lsyncd.c' which has javadoc like comments. Everything else in the tarball is packaging bushwa. DisclaimerBesides the usual disclaimer in the license, we want to specifically EMPHASIZE that NEITHER the authors NOR any organization the authors are associated with can and will hold responsible for data-loss caused by possible malfunctions of lsyncd. Especially if you run it with root privileges ;-) (we ourselves run lsyncd as www-data). [Less]

Debian Archive Mirroring Script

The Debian Archive Mirroring Script is a Perl Script for automatic mirroring of Debian GNU/Linux distributions. Downloads and maintains a partial local Debian mirror. It can mirror any combination of architectures, distributions and sections. Files are transferred by http, ftp or rsync; package pools are fully supported.

mirror-displays

Mirror Displays is two programs: 1. A simple Application to toggle between mirrored and extended desktop modes for the mac. 2. A command line tool good for giving shell-scripts the power to control display mirroring.

fastbackup

This software performs incrementals backups from a source to a destination folder on a regular basis. It is written in Java.

hotcakes

We have moved to http://www.zumastor.org