13 projects tagged "rsync"
luckyBackup is a powerful, fast, reliable, and fully customizable backup and sync tool. It can backup any directory (the source) to another (the destination). luckyBackup copies over only the changes you've made to the source directory and nothing more, saving a great deal of time for backups after the first one. Whatever changes you make to the source, including adding, moving, deleting, modifying files or directories, will have the same effect on the destination. Owner, group, time stamps, links, and permissions of files are preserved (unless directed otherwise). The synchronization feature works on any pair of directories, keeping the files that were most recently modified on both of them. It includes many safety checks to prevent accidental loss of data.
rocknroll (Rsync fOr baCKup and Roll) is an incremental backup maker based on rsync. It backs up a remote directory tree to a destination directory on the local host. For this backup, it manages a set of archives named tag.1, tag.2, etc. Using the famous "link-dest" option of rsync, it keeps only the difference between the different archives.
pirysncd is an attempt to write a daemon to watch a directory for kernel write notifications and then execute an rsync command to synchronize two different directories (local or remote). This is a poor man's mirroring or an alternative (not so) real data replication mechanism based on Pyinotify.
Pylsyncd is a Python implementation, similar to lsyncd, that uses rsync to synchronize local directories with several remote machines running rsyncd. Pylsyncd recursively monitors a set of directories using pyinotify, a pure Python module used for monitoring filesystems changes that relies on inotify. The main advantage of pylsyncd against lsyncd is that it uses message queues in order to synchronize several destination servers in parallel, saving up time when it is required to have more than one destination. It has been tested in heavily loaded environments.
Beaver is a simple concurrent backup system with snapshotting. It is based on a simple list of servers, a file of configuration options, and lists of things to be excluded or included. More powerful configuration options are available in the configuration files. Different copies of beaver backup can be run on the same server with different configuration files. Beaver backup is normally run by cron on a central backup box and uses keychain for remote authentication.
Simple Continuous Integration Tools (scit) is an automated build and or test system consisting of a set of Perl and expect scripts utilizing common tools that are available for most Unix-like operating systems. The intention is to keep it lightweight while still providing a full set of features. The current version has a command-line and an HTML user interface. It should be possible to make it run on very modest hardware; part of the development and testing has been done on a Nokia N900 phone with both master and slave roles running on the same unit.