Disk ARchive (aka Dar) is a filesystem independent, cross platform and command-line based utility designed to helop one backup and archive large live filesystems.
Dar does not create nor format partitions, but it can restore a full filesystem into a larger or a shorter partition, from one partition to several ones, (or the opposite from several to one partition), from a filesystem type to another filesystem type (ext2/3/4 to reiserFS for example), it can save and restore hard-linked inodes (hard linked plain files, sockets, char/block devices or even hard linked symlinks (!)), Solaris's Door files, it takes care of Posix Extended Attributes (Linux, MacOS, ...).
Dar can also detect and restore sparse files, even when the underlying filesystem does not support them: it can restore a normal file with large portions of zeroed bytes as a sparse file on another filesystem that supports it, leading to a gain in space requirement for the restoration but also for the archive size.
Disk ARchive has been tested under Mac OS X, FreeBSD, NetBSD, Linux, Windows, Solaris, and several other systems, it is released under the GNU General Public License (GPL).
How to install and run: Unarchive, open a Terminal window, go to Disk ARchive's folder and run the following commands from the command line:
./configure && make && sudo make install
Here are some key features of "Disk ARchive":
· compression and encryption
· sliced archive in files of requested size
· incremental/differential/decremental backup
· hardlink/softlink/Extended Attributes
· Apple Xcode (to buld from source)
What's New in This Release: [ read full changelog ]
· fixing libdar about dar_manager database corruption that occurred when
· deleting the first archive of a base containing a plain file only
· existing in that first archive.
· Added code to cleanup databases instead of aborting and reporting
· that previously described type of database corruption.
· Added feature when comparing archive with filesystem in order to report
· the offset of the first difference found in a file. This was necessary to
help solving the following bug:
· fixed bug in sparse file detection mechanism that could lead in some very
· particular (and rare) situations to the loss of one byte from file being
· saved. In that case testing the archive reported a CRC error for that
· file. So if you keep testing achives in your backup process and have not
· detect any problem, you can then keep relying on your old backups. This
· bug also expressed when merging archives: dar aborted and reported that a
· merged file had a different CRC than the one stored in the archive of