DAR Changelog

What's new in DAR 2.7.14

Mar 25, 2024
  • adding safe guard in fichier_libcurl destructor to verify all data have been passed to libcurl *and* libcurl has completed the writing operation before destroying a fichier_libcurl object.
  • adding support for thread cancellation when interacting with libcurl
  • updating man page
  • fixing some error in the code documentation
  • updated FAQ

New in DAR 2.7.13 (Oct 1, 2023)

  • Fixing bug auto-reported in "slice_layout.cpp line 48" concerning isolated catalogs triggered when dar/libdar has been compiled with some version gcc (gcc >= 11) with optimizations set.
  • Fixing the configure script to not fail if libargon2 is not present unless explicitly asked by --enable-libargon2-linking
  • Added support for cppcheck to reinforce code robustness and sanity
  • Updating documentation about slice_layout structure and usage in libdar

New in DAR 2.7.12 (Sep 4, 2023)

  • Fixed bug avoid restoration fo binary patch when it was based on another binary patch Added workaround to read archive format 112 (used for releases 279 to 2711) Archive format has been updated to 113 while 2712 generated backup have the exact same format as from 112, this trick is only used to activate the workaround for badly generated backups
  • Adding new condition for overwriting policy (E letter), used to improve the decremental backup when a file only change concerns its metadata (inode information, like permission or ownership)
  • Fixing segmentation fault met when listing an archive content with
  • I option
  • Fixing bug in testing routine that lead regression unseen and released in 2711

New in DAR 2.7.11 (Aug 6, 2023)

  • Removed set_unexpected() invocation (not useful for years in libdar and incompatible with C++17)
  • Fixed generated dynamic libdar binary to include all its dependent libraries
  • Modified default block size for binary deltas, to be closer to what rsync uses (more details in man page).
  • Improved compression exclusions
  • Adding support for ronna (10^27) and quetta (10^30) new SI prefixes, R and Q respectively
  • Fixing bug in infinint class met when extending underlying storage by zero bytes
  • Avoiding delta sig block size calculation when not necessary

New in DAR 2.7.10 (Jun 26, 2023)

  • Displaying the slicing information about the archive of reference
  • Stored within a isolated catalogue when using -l and -q options
  • Cleanup code from obsolete and unused readdir_r invocation
  • Fixing display bug in dar_manager (shell_interaction class of libdar)
  • Fixing python binding build system with the John Goerzen's proposal
  • Replacing the deprecated PYBIND11_OVERLOAD_* by PYBIND11_OVERRIDE_* equivalents

New in DAR 2.7.8 (Mar 22, 2023)

  • Adapted code to workaround clang 10.0.1 bug under FreeBSD 12
  • Updating code and man page about the way to solve the conflict of sequentially reading the archive of reference when binary delta is implicitly present for differential/incremental backups added -avc option to surface libcurl verbose messages
  • Fixed bug in dar where a sanity check about slice min digit detection was applied to the local filesystem when the backup was stored remotely, this prevented the reading or remote backups
  • Exposing libcurl version to the version output (new API call added for that, leading upgrading libdar API to version 6.5.0)
  • Remove extra slash (/) found after hostname in URL passed to libcurl
  • Fixed self test reported error about mycurl_easyhandle_node.cpp line 176
  • Improved error message when libcurl fails to connect to an sftp server
  • Fixed bug in libdar in the way libcurl is called for reading a file using ftp protocol
  • Fixed bug in libdar when asking libcurl the size of the file we are writing (libcurl segfaults with ftp protocol). In addition, we now record this info during the write process (faster and more efficient).
  • Fixed bug met when creating a backup on very close and/or high bandwidth ftp and sftp repos with the --hash option set, triggering a race condition that led dar to sometime hang unexpectedly.

New in DAR 2.7.0 (Apr 26, 2021)

  • Using the truncate system call whenever possible in place of skipping back in the archive, when file need to re-save uncompressed, or when file has changed while it was read for backup
  • Improved slice name versus base name error, now substituting (rather than just asking the user) the first by the later when else it would lead to an execution error.
  • Auto-detecting min-digits at reading time in complement of the feature listed just above
  • Added the possibility to specify a gnupg key by mean of its key-id in addition to the email address it may be associated to, both for asymmetrical encryption and archive signing.
  • Added -b option to dar_split to set the I/O block size
  • Added -r option to dar_split to limit the transfer rate
  • Added -c option to dar_split to limit the number of tape to read
  • New feature: zstd compression algorithm added
  • Replaced old and experimental multi-threaded implementation by production grade one. -G option may now receive an argument on command line for fine tuning. libdar API has been updated accordingly.
  • Added multi-threaded compression when using the new per block compression mode, the legacy streaming compression mode is still available (see both -G and -z option extended syntax).
  • Added lz4 compression algorithm.
  • Removed some deprecated/duplicated old options (--gzip,...)
  • Enhanced the delta signature calculation providing mean for the user to adapt the signature block size in regard to the file's size to delta-sig. "--delta sig" option received an extended syntax.
  • Increased timestamp precision from microsecond to nanosecond when the operating system supports it. It is still possible to use configure --enable-limit-time-accuracy=us at compilation time to use microsecond or even second accuracy even if the OS can support finer precision.
  • Added argon2 hashing algorithm for key derivation function (kdf) which becomes the default if libargon2 is available, else it defaults to sha1 as for 2.6.x. When argon2 is used, kdf default iteration count is reduced to 10,000 (and stays 200,000 with sha1). This can be tuned as usual with --kdf-param option.
  • Adding support for statx() under Linux which let libdar save file's birthtime. Unfortunately unlike under BSD systems (FreeBSD, MACoS X, and so on), the utime/utimes/timensat call do not set birthtime, so you cannot restore birthtime on Linux's unlike under BSD systems
  • AES becomes the default when gnupg is used without additional algorithm.
  • New implementation of the libcurl API use for more efficient reuse of established sessions.
  • You can now exclude/include per filesystem rather than just sticking to the current filesystem or ignoring filesystem boundary. -M option can now receive arguments.
  • New feature: dar_manager can now change the compression algorithm of an existing database.
  • Added a benchmark of dar versus tar and rsync for different use cases.
  • Documentation review, update, cleanup, restructured and beautification.

New in DAR 2.6.14 (Apr 1, 2021)

  • Script used to build dar windows binary has been fixed to have the official default etc/darrc config file usable and used out of the box.
  • Fixed bug met when removing slices of an old backup located on a remote sftp server
  • Fixed bug in cache layer met when writing sliced backup to a remote ftp or sftp repository
  • Enhancement to the -[ and -] options to work as expected when "DOS" formatted text file is provided as a file listing.

New in DAR 2.6.12 (Sep 11, 2020)

  • Fixed regression met in 2.6.11 when generating encrypted archives

New in DAR 2.6.11 (Sep 5, 2020)

  • Fixing bug in dar_manager libdar part, met when the two oldest entries for a file are recorded as unchanged (differential backup).
  • Fixed typo in dar_manager man page
  • Updated lax mode to ignore encryption flag found in header and trailer
  • Fixed two opposite bugs in strong encryption code that annihilated each other, by chance
  • Fixing bug met when merging an archive an re-compressing the data with another algorithm that gives a less good result, this condition lead the merging operation to fail reporting a CRC mismatch
  • Improving archive header code to cope with unknown flags

New in DAR 2.6.10 (May 31, 2020)

  • Update the configure script to handle some undocumented --enable-* options that existed but were not expected to be used.
  • Fixed spelling in darrc comments
  • Fixed bug in dar_split that could occur in very rare conditions
  • Fixed EA support build failure due to what seems to be a change in Linux kernel header
  • Fixed symbol conflict with s_host of in.h on omniOS platform

New in DAR 2.6.9 (May 31, 2020)

  • Fixed some obvious bug when running doxygen (inlined documentation)
  • Fixing configure.ac to detect xattr.h system header when it is located in /usr/include/sys like under Alpine Linux distro (musl libc)
  • Fixed typo in symbol name "libdar.archive_summary" in python binding
  • Fixed bug met when testing an archive in sequential-read mode leading dar to skip back to test deleted inode which is useless and may lead to failure if the archive is read from a pipe
  • Adding *.zst files as excluded from compression when using the predefined target "compress-exclusion"
  • Fixed text diagram alignment in documentation and spelling errors
  • Moving date_past_N_days script to doc/sample with other scripts

New in DAR 2.6.8 (Feb 8, 2020)

  • Fixing bug leading binary delta failed to be read from an archive in some quite rare condition.
  • Fixed bug that was not listing file with delta path when filtering out unsaved inodes
  • Updated source package for the python binding tutorial document be installed with the rest of the documentation
  • Adding date_past_N_days helper script to backup only files later than "today minus N days"
  • Incorporated the "args" support built script in dar source package

New in DAR 2.6.7 (Jan 13, 2020)

  • fixing shell_interaction_emulator class declaration to avoid compilation errors and warning under MacOS
  • fixed bug: dar failed creating an archive on its standard output reporting the error message "Skipping backward is not possible on a pipe"
  • new feature: added python binding to libdar!

New in DAR 2.6.6 (Sep 21, 2019)

  • Fixing script that builds windows binary packages to include missing cygwin libraries
  • Fixing bug: dar_manager batch command (-@ option) contains a inverted test in a sanity check, leading the execution to systematically abort reporting an internal error message.
  • Fixed message error type when asymmetrical encryption is requested and gpgme has not been activated at compilation time
  • Fixed dar/libdar behavior when gpg binary is not available and gpgme has been activated at compilation time. Instead of aborting, dar now signal the gpgme error and proposes to retry initialization without gpgme support. This makes sense for dar_static binary which stays usable in that context when all options have been activated

New in DAR 2.6.5 (Jul 6, 2019)

  • Ixed bug: dar crashed when the HOME environment variable was not defined (for example running dar from crontab)
  • Removed useless skip() in cache layer
  • Cache layer improvement, flushing write pending data before asking lower layer about skippability
  • Fixed bug met when several consecutive compressed files were asked to be compressed and failed getting reduced in size by libdar. In that situation as expected, libdar tries to skip backward and stores the file uncompressed.
  • However the cache layer was introducing an offset of a few bytes leading the next file to be written over the end of the previous one, which dar reported as data corruption when testing the archive.
  • Updating licensing information with the new address of the FSF
  • Clarifying message about possibly truncated filename returned by the operating system

New in DAR 2.6.4 (May 27, 2019)

  • Fixed display bug indicating delta signatures were about to be calculated even when this was not the case.
  • Updating dar man page about the fact aes256 replaced blowfish as the default strong encryption algorithm
  • Bug fix: -D option used at creation time was not adding escape mark of skipped directories. This lead the empty directories that would replace each skipped one to be inaccessible and unable to be restored only in sequential read mode (it worked as expected in direct mode)

New in DAR 2.6.3 (Mar 31, 2019)

  • feature enhancement: added option to specify the bloc size used to create delta signatures
  • feature enhancement: added the ability to provide login for sftp/ftp remote access, that contain @ and other special characters
  • fixed bugs in dar _xform, leading dar not finding source archive if destiination was not placed in the same directory as source

New in DAR 2.6.2 (Feb 9, 2019)

  • fixed incoherence in documentation
  • updating in-lined help information (-h option)
  • fixed unexpected behavior of the dar command-line filtering mechanism
  • met when the provided path to -P or -g options was ending with a slash
  • renaming 'path operator + (std::string)' as method append() to avoid
  • compiler using it when a std::string need first to be converted to path
  • before adding it to an existing path.
  • adding check test to detect when path::append() is used to add a path
  • instead of a filename to an existing path object.
  • adding a warning when restoring a Unix socket if the path to that
  • socket is larger than what the sockaddr_un system structure can handle
  • fixing bug due to Linux system removing file capabilities (stored as
  • EA) when file ownership is changed. Though restoring EA after ownership
  • may lead to the impossibility to restore them due to lack of permission
  • when dar/libdar is not run as root. Thus we try restoring EA a second
  • time after ownership restoration. This is not efficient but restores
  • the file as close as possible to their original state whatever
  • permission dar has been granted for a restoration operation.

New in DAR 2.6.1 (Feb 9, 2019)

  • fixed error in man page
  • fixing bug in the routine removing files for local filesystem, used at
  • archive creation time to remove an existing archive (after user
  • confirmation), or at restoration time used to remove file that had been
  • removed since the archive of reference was done. The file to remove was
  • always removed from the current directory (missing the path part), most
  • of the time this was leading to the error message "Error removing file
  • Not such file or directory". It could also lead to incorrectly
  • removing files (not directory) located in the directory from which
  • dar was run.
  • fixing bug met while repairing an archive containing delta signature
  • for unsaved files
  • merging patch from ballsystemlord updating list of file extension
  • not to compress (see compress-exclusion defined in /etc/darrc)
  • review cat_delta_signature implementation in order to be able to fix
  • memory consumption problem when delta signature are used
  • fixed missing mark for data CRC when the data is a delta patch, leading
  • sequential reading to fail when a delta patch was encountered
  • fixed bug in XML output about deleted entries
  • fixed XML output to be identical to the one of dar 2.5.x for deleted
  • entries.
  • Adding the deleted date in 'mtime' field for deleted entries in XML
  • output
  • fixing bug in xz/lzma routine wrongly reporting internal error when
  • corrupted data was met
  • fixed code for compilation with clang to succeed (it concerns MAC OS X
  • in particular)
  • fixed inconsistencies in libdar API that avoided gdar to compile with
  • libdar released in 2.6.0

New in DAR 2.6.0 (Dec 17, 2018)

  • New feature: support for binary delta in incremental/differential backups
  • New feature: support ftp/sftp to read an archive from a cloud storage.
  • reading is optimized to not transfer a whole slice but only the needed
  • part to proceed to the operation (restoration, listing, and so on)
  • New feature: support ftp/sftp to write an archive eventually with hash
  • files to a remote cloud storage
  • Modified behavior: While creating a single sliced archive, DUC file is
  • now executed unless user interrupted dar/libdar. This to stay coherent
  • with multi sliced archive behavior
  • New feature: display filters nature (-vmasks option)
  • New feature: follow some symlinks as defined by the --ignored-as-symlink
  • option
  • New feature: one can define the compression algorithm a dar_manager
  • database will use. This choice is only available at database creation
  • using the new dar_manager's -z option. In particular "-z none" can be
  • used to avoid using compression at all
  • Repair mode added to re-create a completed archive (suitable for direct
  • access mode and merging) from an interrupted one due to lack of disk
  • space, power outage or other reasons leading to similar problem.
  • Dar can now only save metadata inode change without re-saving the whole
  • file if its data has not changed. Dar_manager also handle this by
  • restoring the full backup and then the inode metadata only when
  • necessary.
  • In regard to previous point, if you want to keep having dar saving the
  • data when only metadata has changed use --modified-data-detection option
  • Moved dar_slave code into libdar as class libdar::libdar_slave
  • Moved dar_xform code into libdar as class libdar::libdar_xform
  • Added libdar_slave and libdar_xform in libdar API
  • Modified dar_xform and dar_slave to rely on new libdar API
  • API: simplified user_interface class
  • API: using std::shared_ptr and std::unique_ptr to explicitly show the
  • ownership of the given pointed objects (C++11 standard)
  • API: simplified class archive to only require user_interaction at
  • object construction time
  • API: simplified class database to only require user_interaction at
  • object construction time
  • API: making enum crypto_algo an C++11 "enum class" type
  • Security refresh: default crypto algo is now AES256. As you do not
  • need anymore since 2.5.0 to specify the -K option when reading an
  • archive this should not bring any backward compatibility issue
  • Security refresh: adding salt per archive (one is still present per
  • block inside an archive)
  • Security refresh/new feature: adding option --kdf-param to define
  • the iteration count for key derivation, which now defaults to 200,000
  • and hash algorithm used to derived key, still using sha1 by default
  • Slide effect of previous feature due to starvation of free letters
  • to add a new command, the -T option with argument is no more
  • available, one need to provide explicitly the desired argument
  • Security refresh: improving seed randomization for the pseudo-random
  • generator used in elastic buffers
  • Feature enhancement: activate needed Linux capabilities in the
  • "effective" set if it is permitted but not effective. This concerns
  • cap_chown at restoration time, cap_fchown for furtive read mode,
  • cap_linux_immutable to restore the immutable flag, and cap_sys_
  • resource to set some linux FSA. This let one set the capabilities
  • for dar binary only in the "permitted" set, capabilities will then be
  • allowed only for users having them in the "inheritable" set of their
  • calling process (usually a shell), without root privilege need.
  • The ./configure --enable-mode option now defaults to 64, which
  • will setup a libdar64 in place of infinint based libdar by default.
  • You can still build a infinint based libdar by passing
  • --enable-mode=infinint to the ./configure script.

New in DAR 2.5.18 (Dec 9, 2018)

  • Fixed compilation issue in context where EA are not supported
  • Fixed typo in dar man page (--sequential-mode in place of --sequential-read)
  • Moved the "no EA support warning" trigger when restoring an archive later in the EA restoration process, in order to have the possibility thanks to the -u "*" option to restore an archive containing EA using a dar/libdar without EA support activated at compilation time,
  • At restoration time, avoiding issuing an "EA are about to be overwritten" warning when the in place file has in fact not only one EA set.

New in DAR 2.5.17 (Sep 30, 2018)

  • Bug fix: dar failed to restore EA when file permission to restore did not included user write access. Fix consists in temporarily
  • Adding user write access in order to restore EA and removing this
  • Extra permission afterward if necessary
  • Updated FAQ
  • Fixed typos in dar man page
  • Fixed bug met when writing slices to a read-only filesystem
  • Fixed compilation problem under Solaris
  • Fixed typos in dar man page
  • Bug fix: self reporting bug in filtre.cpp line 2932 or 2925 depending
  • or dar's version (report occurs in a normal but rare condition that
  • was not imagined by developer, leading dar to abort the backup)
  • Bug fix: wrong evaluation of possibility to seek backward in the
  • escape layer (layer managing tape marks) which lead to useless but
  • harlmess skip trials in some rare conditions.

New in DAR 2.5.16 (Jul 19, 2018)

  • Bug fix: while rechecking sparse file (-ah option) during a merging operation, dar wrongly reported CRC mismatch for saved plain files
  • Fixed man page about sparse-file handling while merging: To remove sparse file datastructure during a merging operation you need to set --sparse-file-min-size to a valuer larger than all file sizes contained in the archive (for example 1E for one exabyte)
  • Bug fix: met when using compression and creating the archive to dar's standard output (ssh) and leading files to be corrupted in the archive and reported as such.
  • Optimisation of escape_sequence skippability (avoids trying skipping and failing for some corner cases, when we can detect it does even not worth trying)

New in DAR 2.5.15 (Apr 28, 2018)

  • From 2.5.14-bis to 2.5.15
  • Fixing self report bug message met when trying to create an isolated
  • catalogue into a directory that does not exist
  • Adding slice overwriting verification before creating a isolated
  • catalogue, to be coherent with other operations creating an archive
  • (backup and merging)
  • Storage size of compressed files was often wrongly stored in archive
  • (shorter than reality), the only impact took place at archive listing
  • time where the compression ratio displayed was better than reality
  • Fixed auto-detected bug condition triggered when -Tslicing is used
  • with --sequential-read. Both options are not compatible and have been
  • excluded by a nicer message than this auto-detection bug message.

New in DAR 2.5.14 bis (Dec 21, 2017)

  • Avoiding using the syncfs() in dar_split when the system do not support it (replacing it by sync() in that situation for the compilation to be successful)

New in DAR 2.5.14 (Dec 21, 2017)

  • Made libgcrypt built-in memory guard be initialized before obtaining ligcrypt version, to respect libgcrypt usage (but no problem was seen nor reported about this inconsistency)
  • Fixed syntax error in XML listing output (EA_entry and Attributes tags)
  • Fixed typos in dar man page
  • Updating Tutorial for restoration
  • Fixed bugs in dar_split: cygwin support, filedescriptors were not explicitly closed at end of execution, allocating buffer on heap rather than in the stack for better size flexibility, avoiding buffer size to be greater than SSIZE_MAX.
  • Added -s option to dar_split in order to disable the by default SYNC write that was used and which caused poor performance. To keep the same behavior as the older dar_split (and its poor performances) you need now using -s option.
  • Dar_split enhancement: added call to syncfs before closing the file descriptor in split_output mode
  • Fixed bug in dar_split that was did not lead dar_split to completely fulfill an device before asking for user to change the media when used in split_output mode, this was sometimes leading dar reporting file as corrupted at dar_split at media boundary.
  • Added feature in dar_split to show the amount of data written since the last media change

New in DAR 2.5.13 (Oct 30, 2017)

  • Added -az option to automatically nullify negative dates returned from the system in the archive under creation (filesystem is not modified)
  • Included the birthtime (HFS FSA) into the negative dates handling
  • Modified behavior: dar now fails upon unknown option instead of warning the option is unknown and thus ignored
  • Bug fix: dar 2.5.12 and below in 2.5.x branch could not read archive generated by dar 2.4.x and below (unless in infinint compilation mode) when the old archive included a file which date(s) was returned by the system as a negative integer at the time of the backup.
  • Note that if dar can now read old archive in that particular case, such date stay recorded in the dar archive as very far in the future and not in the past, because 2.4.x and below blindly assumed the system would always return a positive integer as number of second since 1970. Since 2.5.12 release, when the system provides a negative date the date is assumed as zero (Jan 1970) with user agreement.
  • Fixed missing throw in tools.cpp (exception condition was not reported)

New in DAR 2.5.12 (Sep 4, 2017)

  • Documenting in man page the limitation of -[ and -] options concerning the maximum line length that could be used in a listing file. This limitation was only described in doc/Limitations.html
  • Dar now aborts if a line exceeding 20479 bytes is met in a listing file
  • Improved error message issued when a file listing (-[ or -] option) is missing for it provides the missing filename in the error message
  • Improved error message issued when a line of a file listing exceeds 20479 characters for it display the start of that line
  • Fixed bug in file listing (-[ option) leading some directories and their content to be excluded in a somehow rare condition
  • Improved behavior when dar reads a negative date. Instead of aborting it now asks the user if it can substitute such value by zero
  • Improved behavior when dar is asked to read an archive located in a directory that does not exist. DUC file passed to -E option is now properly run in that case too and has the possibility for example to create that directory and download requested file

New in DAR 2.5.11 (Jun 24, 2017)

  • Minor feature: displays the archive header which is never ciphered and aborts. This feature is activated while listing archive content and adding the -aheader option. This brings the side effect to invert twolines in the archive summary (dar -l archive -q) "catalogue size" and "user comment".
  • Adding date format info for -w option in "dar_manager -h" usage help
  • Fixed several mistakes in tools.cpp leading compilation to fail under certain environments
  • Fixed a typo in filesystem.cpp and portability issue that lead compilation to fail under openbsd 6.0
  • Fixed bug in the filtering mechanism relying on file listing (-[ and -] options) that could not find an entry in the listing upon certain condition leading a file not being excluded as requested or not included as requested

New in DAR 2.5.10 (Apr 18, 2017)

  • Fixed bug: -r option (only more recent overwriting policy) was considering a file to be more recent when it had the exact same date as the file in place.
  • Updating documentation about requirements for compiling dar from sources
  • Fixed bug: bug met when restoring of a file that has the immutable flag set. Dar/libdar failed restoring such file in the context of differential/incremental backup. The fix consists of the removal of the immutable flag from filesystem before restoring the new version of the file's data, then setting back the immutable flag afterward.updating FAQ with description of the way dar uses lzo compression compared to the lzop program
  • Fixed bug: aborting an archive was leading to an unreadable archive in direct mode, most of the time when strong encryption was used
  • Minor new feature: added two flavors of lzo algorithm: lzop-1 and lzop-3, in order to match compression levels 1 and 3 of the lzop command

New in DAR 2.5.9 (Feb 18, 2017)

  • Fixed typos in documentation about dar internal use of symmetric encryption
  • Fixed bug: merging operation could wrongly melt different unrelated hard linked inodes when merging using an archive which results from a previous merging operation.
  • Fixed bug: aborting an archive was sometimes leading to an unreadable archive in direct mode (was readable only in --sequential-read mode)
  • Fixed bug: libgpgme was only present at linking time of final binaries (dar, dar_slave, dar_xform, dar_manager, dar_cp, dar_split), not at linking time of libdar, which caused problem under Linux Rosa distro where the "no-undefined" flag is passed to the linker.
  • Minor new feature: -ay option has been added to display sizes in bytes instead of the default which uses the largest possible unit (Kio, Mio, and so on.)

New in DAR 2.5.8 (Feb 18, 2017)

  • Fixed double memory release occurring in a particular case of read error
  • Improved robustness of FSA code against data corruption
  • Fixed bug - DAR_DUC_PATH was not used with -F and -~ options
  • New features added: -aduc option to combine several -E options using the shell '&&' operator rather than the shell ';' operator. The consequence is that with -aduc option a non zero exist status of any script (and not only of the script given to the last -E option) will lead dar to report the error.
  • Main page updated about combination of several -E options
  • Fixed bug: merging partial FSA led to self reported bug in cat_inode.cpp at line 615

New in DAR 2.5.7 (Feb 18, 2017)

  • Fixed bug leading dar to not include directories given to -g option nor
  • to exclude directories given to -P option when at the same time the
  • directory given to -R option starts by a dot ("-R ./here" in place of
  • "-R here")
  • Bug fix and speed improvement - under certain circumstances dar was
  • reading several times the data at slice boundary, leading dar to ask for
  • slice N then N-1 then again N, this caused sub-optimal performance and
  • was triggering user script unnecessarily

New in DAR 2.5.6 (Sep 19, 2016)

  • Added speed optimization when comparing dates with hourshift flexibility (-H option).
  • Fixed bug met when using as reference an archive generated by dar 2.5.4 or older, bug that lead dar saving almost all file even those that did not change.

New in DAR 2.5.5 (Sep 19, 2016)

  • Fixed message displayed when reading old archives.
  • Fxed bug that avoided dar-2.5.x code to read old archive format when special allocation was set (by defaut) at compilation time.
  • Disabling special-alloc by default reducing memory footprint.
  • Fixed error in FAQ about the way ctime/atime/mtime are modified during normal operating system life.
  • New implementation of class datetime with better memory footprint avoding storing sub-microsecond part of date to preserve limiting ability to store large dates.
  • Moving field cat_inode::last_cha from pointer-to-field to plain field of the class, this slightly reduce catalogue memory footprint.
  • Fixing bug in the returned exit status when dar failed executing DUC command due to system error (now returning the expected code 6 in that.

New in DAR 2.5.4 (Sep 19, 2016)

  • Fixing missing included files for libdar API.
  • Removed extra try/catch block introduced by commit da5cad5e52f959414b3163a2e2a320c2bc721e.
  • removed sanity check that caused problem when writing an archive to a FUSE based filesystem.
  • Fixing non call of the -E script/command after last slice creation, when encryption or slice hashing was used.
  • Fixed bug in dar_manager: archive permutation in database lead libdar to check an archive number of range under certain circumstances.
  • Fixed inversion of the condition triggering a warning about archive date order in a dar_manager database while moving an archive within a database.
  • Fixed typos in documentation catalogue memory optimization, with the drawback to limit the number of entry in an archive to the max integer supported by the libdar flavor (32 bits/64 bits/infinint).
  • Fixed configure script to temporarily rely on LIBS rather LDFLAGS to check for gpgme availability.
  • Removed order dependency between -A and -9 options of dar_manager: -9 can now be specified before or after -A option.
  • Resetting to "false" the "inode_wrote" flag of hard link data-structure before testing and merging. Merging a previously tested archive or testing a second time would not include hard linked inode in the operation. This situation does not occurs with dar but could succeed with some external tools that keep the catalogue in memory to perform different operations on it.
  • Fixed bug in the routine that detects existing slices to warn the user and/or avoid overwriting, bug that lead dar to "bark" when an archive base name started by a + character.
  • Avoiding to use AM_PATH_GPGME in configure script when gpgme.m4 is not available.
  • Adding new methods in libdar API to obtain the archive offset and storage size of saved files (class list_entry).
  • Adding new method in libdar API to translate archive offset to file offset (class archive).
  • Reporting a specific error message when filename returned by the system has the maximum length supported by the system itself, assuming filename has been truncated.

New in DAR 2.5.3 (Sep 19, 2016)

  • Fixing a 2.5.x build issue met when a 2.4.x libdar library is already installed in an FreeBSD system.
  • Improving message and behavior of libdar in lax mod when a truncated archive is read.
  • Fixing self reported bug at "tronconneuse.cpp line 561" met while reading truncated/corrupted archive.
  • Fixed not closed filedescriptors, met when saving a filesystem that has not ExtX FSA available.
  • Fixing configure script to be more robust in front of system where gpgme.h is installed in a non standard path and user did not provide coherent CPPFLAGS, LDFLAGS before calling ./configure.
  • Displaying CRC values when listing isolated catalog as XML output.
  • Fixing compilation issue when system does not provide strerror_r() call.
  • Avoiding warning about FSA absence when fsa-scope is set to "none".
  • Adding --disable-fadvise option to configure script for those that want back full pressure from dar on the system cache (same behavior as 2.4.x).
  • Fixing bug, fadvise() called a wrong time making it having no effect updating FAQ about comparative performance from 2.4.x to 2.5.x.
  • Optimization: reduced the number of call to dup() at libdar startup.
  • Improvement: printing file type on verbose output.
  • New feature: added %t macro reflecting the inode type in dar's.
  • Backup-hook-execute option.

New in DAR 2.5.2 (Sep 19, 2016)

  • Fixed bug met when permission is denied while reading or writing slices.
  • Fixing bug that avoided creating an archive at the root of the filesystem.
  • Fixing bug met in rare situation while reading in sequential-read mode an archive encrypted using gnupg encryption. In that situation libdar may fail reading the archive (but succeeds in normal read mode) issuing an obscure message (message has also been fixed).
  • Code simplification, removing field reading_verion from class crypto_sym as its parent class tronconneuse already have such information.
  • Removed extra newline displayed by dar at end of execution.
  • Fixed bug avoiding dar to properly read an entry (reporting CRC error) when specific sequence of character (start of escape sequence) fall at end of the read buffer of the escape layer.
  • Speed optimization for datetime class.
  • Fixed bug that avoided dar reading archives in sequential read mode while reading from a pipe.
  • Fixed bug in non regression test routine provided beside dar/libdar.
  • Fixing display message showing not always in the correct context.
  • Fixing case inversion leading the cache layer not to be used when necessary and used when useless while reading an archive.
  • Improved heuristic in dar_manager to determine the date a file has been deleted.

New in DAR 2.5.1 (Sep 19, 2016)

  • Fixed display bug in dar_manager met when using -o option and adding options for dar that does not exist for dar_manager (like -R option).
  • Reactivating disabled (by mistake) optimization for some read-only dar manager database operations.
  • Fixing compilation issue with dar against gcc 4.9.2.
  • Fixing syntax error in dar_manager message.
  • Fixed bug that forbade dar_manager to write down modified database when only database header was modified (-o, -b, -p switches).
  • Adding dar_manager database format version information with -l option.
  • Fixed libdar inability to read dar_manager's database format version 4.
  • Adapting code to build under cygwin environment, where thread_local seems broken.
  • Fixed output to stderr in place of stdout for Licensing information.
  • Fixed bug met when permission is denied while reading or writing slices.
  • Fixing bug that avoided creating an archive at the root of the filesystem.

New in DAR 2.5.0 (Sep 19, 2016)

  • Added support for posix_fadvise().
  • Added entrepot class hierarchy to support in the future other storage types than local filesystem for slices.
  • API: added access to the entrepot through the API.
  • Modified class hash_fichier for it becomes entrepot independent.
  • API: extended libdar API with an additional and more simple way to read an archive: archive::get_children_in_table() method, see doc/API_tutorial.html for details.
  • Added support for extX (see lsattr(1)) and HFS+ (birthtime date) Filesystem Specific Attributes (FSA).
  • dar is now able to skip backward when a file is found to be "dirty" at backup time. This avoids wasting space in archive but is only possible if the backward position is located in the current slice and no slice hashing nor strong encryption is used. Of course if the archive is written to a pipe or to stdout, skipping back to retry saving data at the same place is neither possible, --retry-on-change option stays possible in that cases at the cost of data duplication (wasted bytes amount, see retry-on-change man page).
  • By default dar now performs up to 3 retries but do not allow for wasting bytes if file has changed at the time it was read for backup, this can be modied using --retry-on-change option.
  • With the same constraints as for a changing file, if a file is saved compressed but its compressed data uses more space than uncompressed, the file's data is resaved as uncompressed. However, if skipping backward is not possible, data is kept compressed.
  • Added several more specific verbosity options: -vm, -vf and -vt.
  • Added support for microsecond timestamps (atime, mtime, ctime, birthtime).
  • Using lutime() to restore atime/mtimes of symlink on systems that support it.
  • API: removed backward compatible API for old libdar 4.4.x.
  • API: simplified implementation of archive isolation thanks to isolation evolution features brought by release 2.4.0. Memory requirement is now devided by two compared to releases of previous branch (2.4.x).
  • dar has been updated to use this new API for archive isolation.
  • Added exclude-by-ea feature to avoid saving inodes that have a particular user defined EA set.
  • Added comparison of an isolated catalogue with a filesystem, relying on embedded data CRC and inode metadata in absence of the saved data.
  • The new archive format (version 9) holds the ciphering algorithm used at creation time, only the passphrase is now required at reading time and K option may be ignored which will lead dar to prompt for passphrase.
  • Adding support for public key encryption (GnuPG) supporting several encryption keys/recipients for a given archive.
  • Adding support for public key signature when public key encryption is used.
  • While listing archive contents, directories now show the size and average compression ratio of the data they contain.
  • Archive summary (-l with -q options) now reports the global compression ratio.
  • Added the -vd switch to only display current directory under process for creation, diff, test, extraction and merging operations
  • Added xz/lzma compression support.
  • Added -Tslicing listing option to show slice location of files inside an archive archive.
  • Isolated catalogues now keep a record of the slicing layout of their archive of reference in order to provide -Tslicing feature when used on the isolated catalogue alone. However if an archive has been resliced (using dar_xform) after its isolated catalogue has been generated, using -Tslicing option with the isolated catalogue would give wrong information. To overcome that, it is possible to specify what is the new slicing of the archive of reference by using the -s and -S options in conjunction with -Tslicing added dar_split command to provide on-fly multi-volume archive support for tape media experimental feature to have libdar using several threads (not activated by default due to poor performance gain).
  • dar now aborts when a given user target cannot be found in included file added sha512 hashing algorithm beside already available md5 and sha1, the generated hash file can be used with 'sha512sum -c ' command.
  • Removed useless --jog option for memory management.
  • Removed previously deprecated -y/--bzip2 command, bzip2 compression remains available using -z option (-zbzip2 or --compression=bzip2) replaced SHA1 by SHA224 to generate IV for encryption blocks, this slightly improves randomness of IV and stay available when libgcrypt is run in FIPS mode.

New in DAR 2.4.22 (Sep 19, 2016)

  • fixing bug in the returned exit status when dar failed executing DUC command due to system error (now returning the expected code 6 in that case too).

New in DAR 2.4.21 (Sep 19, 2016)

  • Removed sanity check that caused problem when writing an archive to a FUSE based filesystem.
  • Fixed bug in dar_manager: archive permutation in database lead libdar to check an archive number out of range under certain circumstances.
  • Fixed inversion of the condition triggering a warning about archive date order in a dar_manager database while moving an archive within a database removed order dependency between -A and -9 options of dar_manager: -9 can now be specified before or after -A option.
  • Resetting to "false" the "inode_wrote" flag of hard link datastructure before testing and merging. Merging a previously tested archive or testing a second time would not include hard linked inode in the operation. This situation does not occurs with dar but could succeed with some external tools that keep the catalogue in memory to perform different operations on it.
  • Fixed bug in the routine that detects existing slices to warn the user and/or avoid overwriting, bug that lead dar to "bark" when an archive base name started by a + character.

New in DAR 2.4.20 (Sep 19, 2016)

  • Fixed display bug in dar_manager met when using -o option and adding options for dar that does not exist for dar_manager (like -R option) reactivating disabled (by mistake) optimization for some read-only dar.
  • manager database operations fixing compilation issue with dar against gcc 4.9.2.
  • Fixing syntax error in dar_manager message.
  • Fixing bug that avoided creating an archive at the root of the filesystem.

New in DAR 2.4.19 (Sep 19, 2016)

  • Fixed missing quote in dar_par.dcf which is called by the par2 directive.
  • Fixed bug in dar_manager's -u option, not displaying most recent files of an archive when they have been marked as removed in a more recent archive of the same dar_manager database.
  • Fixed bug met while restoring in sequential read mode a file having several copies (was modified at the time it was saved and retry-on-change was set).

New in DAR 2.4.18 (Sep 19, 2016)

  • Initial Vector used for strong encryption was set with pseudo-random data generated using SHA1 message digest and blowfish cipher, which are not available when gcrypt is running in FIPS mode. Since 2.4.18 we now use SHA256 and AES256 for IV assignment in order to have libdar compatible with FIPS mode. For data encryption nothing changes: the cipher specified (-K, -J, -$ options on CLI) are used as before.
  • Fixing bug met when performing archive isolation in sequential-read mode, If an archive corruption or truncated archive leads an inode to not have its CRC readable, dar aborts and issues a BUG report.
  • Updating list of project relying on dar/libdar.

New in DAR 2.4.17 (Feb 11, 2015)

  • fixing issue when case insensitive comparison was requested and invalid wide char for the current local was met in a filename. In such situation the corresponding file was never saved before (considering a filesystem error for that file), while now the ASCII case insensitivity is used as fallback.

New in DAR 2.4.16 (Jan 20, 2015)

  • fixing archive listing displayed information for catalogue size when archive is read in --sequential-read mode
  • fixing bug that avoided dar releases 2.4.x up to 2.4.15 to read encrypted archive generated by dar release 2.3.x and below
  • adding informational note at the end of ./configure script execution when --enable-mode has not been used.
  • adding support for case sensitivity in filename comparison (-an option) for other character sets than POSIX/C locale like Cyrillic for example.
  • fixing bashisms in doc/samples scripts

New in DAR 2.4.15 (Sep 8, 2014)

  • fixing bug met when reading an encrypted archive in sequential mode
  • fixing bug met when reading an encrypted archive in sequential mode from an anonymous pipe
  • changed option '-;' to -9 as '-;' does not work on all systems with getopt (only long option equivalent --min-digits worked) for dar, dar_cp, dar_manager, dar_xform and dar_slave commands.
  • fixing bug met when restoring deleted files in sequential read mode and some directory where they should be "restored" are not readable or could not be restored earlier
  • adding extra buffer to handle sequential read of encrypted archive when the last crypto block contains some but not all clear data after encrypted one (the archive trailer).
  • fixing compilation issue using clang
  • fixing bug that prevents using -~ option with on-fly catalogue isolation in order to execute an user command once on-fly isolation has completed
  • added some autoconf magic to determine the correct (BSD/GNU) flag to use with sed in order to activate regular expression parsing
  • new implementation of mask_list class which is compatible with libc++
  • fixed bug met on FreeBSD with dar_xform where the system provides a standard input file descriptor in read-write instead of read-only mode.

New in DAR 2.4.14 (Jun 19, 2014)

  • limiting memory consumption of the cache layer to stay below 10 MiB, under certain circumstances (very large archive), it could grow up to an insane value like 50% or the available RAM. reducing to 10 MiB does not impact performance in a noticeable manner while it avoids system to swap out due to the libdar cache layer becoming huge.
  • added --with-pkgconfigdir to define an alternative path for libdar pkgconfig file (to ease portability to FreeBSD)
  • modified some Makefile.am for better FreeBSD support
  • fixed display bug in XML listing output concerning hard linked inodes
  • fixing typo in man page
  • fixing bug met while isolating a catalogue in --sequential-read mode. Using such isolated catalogue lead dar report an error about inaccessible EA.
  • displaying compression rate for sparse files even when they are uncompressed, sparse file detection also leads to compress files
  • fixing bug that lead libdar to fail comparing an inode having EA when comparison is done in --sequential-read mode
  • fixing display bug in in ligcrypt check of configure script for minimum required version
  • fixing 'make clean' to remove some forgotten files generated by 'make'

New in DAR 2.4.13 (Apr 22, 2014)

  • adding initialization value for two variables to avoid inappropriate warning when compiling with -Wall option
  • reducing UNIX_PATH_MAX by the system when not defined from 108 to 104 bytes to accommodate BSD systems
  • fixing assignment operator of class criterium that was not returning any value as it should
  • removing useless boolean expression that always succeeds in logical AND expression
  • adding support for back-slash of quoting characters in DCF files
  • fixed compilation issues with clang / FreeBSD, Thanks to Neil Darlow's server
  • fixed compilation warning due to deprecated symbols in libgcrypt header files
  • replaced gnu make specific rules by legacy ones to avoid automake warning about them
  • removed old unused stuff from misc sub-directory
  • adding warning at compilation time if libgcrypt used is older than 1.6.0
  • adding warning at execution time if hash computation is requested with slices greater than 256 Gio and ligbcrypt dynamically or statically linked is older than 1.6.0
  • adding alternative methods in list_entry API class to return dates as number of seconds
  • fixed bug in hour-shift (-H option) when comparing dates from an old extracted catalogue (archive format 7 or older).
  • fixed documentation bug about the meaning of the compression ratio
  • fixed a display bug about the "compression flag" wrongly displayed for uncompressed files
  • fixed unhandled exception when giving non number argument to -1 option

New in DAR 2.4.12 (Apr 22, 2014)

  • for correctness fixed delete vs delete[] on vector of char (not incidence reported)
  • fixed out of range access in routine used to read very old archive format
  • fixed error in logical expression leading a sanity test to be useless
  • removed duplicated variable assignment
  • updated FAQ
  • fixed typo and spelling errors
  • fixed bug (reported by Torsten Bronger) in the escape layer leading libdar to wrongly reporting a file as corrupted at reading time
  • fixed bug in the sparse file detection mechanism that lead the minimum size hole detection to become a multiple of the default value or specified one. This implied a less efficient reduction of sparse files because smaller holes in files were ignored
  • fixed and updated man page about --go-into option
  • updated full-from-diff target in /etc/darrc default file
  • added a debug option in hash_file class (option only used from testing tools) to troubleshoot sha1/md5 hash problem on slices larger than (2**38)+63 bytes, bug reported by Mike Lenzen and understood by Yuriy Kaminskiy at libgcrypt. Note: This bug is still open due to an integer overflow in libgcrypt.
  • backported from current development code an additional and more simple way to read an archive using the libdar API. This API extension is not used by dar command-line tools for now.
  • Fixing installation of libdar header files on Darwin, where "DARwin" macros were not filtered out from the generated libdar header files.
  • Fixing self reported bug 'generic_file.cpp line 309' met while comparing an archive with a filesystem
  • Update code in order to compile with gcc-4.8.2 in g++11 mode (partial implementation and adaptation of Fabian Stanke's patch)
  • Fixing bug met while performing a verbose archive listing in sequential read mode
  • Added Ryan Schmidt's Patch to properly display status at end of ./configure script under BSD systems (in particular Mac OS X)
  • Updating configure.ac script to fix warning reported by autoconf when generating the ./configure script
  • Addressed portability problem with BSD systems that do not provide a -d option to the 'cp' command, preventing proper installation of the Doxygen documentation. Fix based on patch provided by Jan Gosmann.

New in DAR 2.4.11 (Nov 4, 2013)

  • Modified behavior of 'dar -h' and 'dar -V', both now return 0 as exist status instead of 1 (which means syntax error)
  • Fixed bug: Q is now available with -V under the collapsed form -QV or -VQ - fixed typo in documentation
  • Fixed memory leakage met when dar fails a merging operation because the resulting archive is specified in an directory that does not exist
  • Fixed bug met when isolating a differential backup in sequential read mode
  • Fixed bug about slice file permission not taking care about umask variable when the --hash feature is used
  • Fixed performance issue when reading an archive over a pair of piles using dar_slave (possibly over ssh) when the archive makes use of escape marks and when no encryption is used
  • Added target "full-from-diff" in /etc/darrc default file
  • Aixed bug avoiding reading an truncated archive in direct access mode with the help of an external catalogue
  • New and better implementation of archive extraction in sequential read mode
  • Fixing bug (segfault) met when hitting CTRL-C while reading an archive in sequential mode
  • Fixing libdar.pc for pkg-config for the cflags given to external applications
  • Fixed memory allocation/desallocation mismatches (delete vs delete [] ) concerning four vector of chars
  • Fixed error in logical expression leading a sanity test to be useless

New in DAR 2.4.10 (Mar 11, 2013)

  • 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 reference.

New in DAR 2.4.9 (Jan 7, 2013)

  • fixed bug: during differential backup dar saved unchanged hard linked inode when a hard link on that inode was out of the -R root directory. This also has the effect to always save files with long names on NTFS filesystems (!)
  • Fixed syntax error in configure script about execinfo detection
  • Removed unused AM_ICONV macro from configure script
  • fixed bug met under Cygwin when auxiliary test command failed to link when libgcrypt was not available.
  • updated mini-howto
  • updating French message translations
  • restricted security warning for plain files and hard linked plain files
  • fixed display bug in dar_cp when manipulating files larger than 2 GB
  • fixed SEGFAULT met when adding to a dar_manager database an archive which base name is an empty string
  • improved error message, reporting the -B included file in which a syntax error has been met
  • modified dar_manager database to consider both ctime and mtime as timestamp
  • value for data of saved files. This suppresses the warning about badly ordered archives in database when at some files have been restores from a old backup.

New in DAR 2.4.8 (Jan 7, 2013)

  • documentation fixes and updates
  • improved database listing efficiency
  • reduced memory usage of the caching layer in libdar
  • fixed self reported bug caused by memory allocation failure
  • fixed a SIGSEGV caused by double free in dar_xform when syntax error is met on command-line
  • dar_xform was not able to properly transform archive generated by dar older than release 2.4.0
  • fixed bug that lead dar be unable to remove a directory at restoration time
  • replaced old remaining "bcopy" occurrence by a call to memcpy
  • fixed crash met while creating a backup with on-fly isolation
  • fixed libdar behavior when reading a strongly corrupted encrypted archive

New in DAR 2.4.7 (Jul 5, 2012)

  • fixing memory allocation bug in crc class, that lead glibc aborting dar (bug is the object of the previous notice in dar-news mailing- list).
  • reviewed code and replaced some remaining occurrences of bzero/bcopy by their recommended replacement functions (memset/memcpy)
  • fixed compilation problem under Solaris
  • fixed bug that could lead a file to be wrongly reported as different from the one on filesystem, when that file had changed while it was saved, then saved a second time but had its size modified since the first time it was saved.

New in DAR 2.4.5 (May 19, 2012)

  • updated sample scripts to be compatible with dar's --min-digit option
  • added missing included file to be able to compile with gcc-4.7.0
  • removing an unused variable in filtre.cpp
  • fixed a display bug when comparing archive with filesystem, leading to a
  • segmentation fault (%S in place of %i in mask)
  • fixed bug leading dar to not restore some directories from differential
  • backups when they are absent in the filesystem
  • fixed bug that show a "uncaught exception" message at the end of archive
  • listing for dar shared binaries only, compiled in infinint mode, under
  • ArchLinux
  • updated the configure script to link with libexecinfo when available
  • added possibility to disable the use of execinfo in libdar thanks to the
  • new --disable-execinfo option for the ./configure script
  • added Andreas Wolff patch to fix bug under Cygwin (segfault on program
  • termination).

New in DAR 2.4.4 (Mar 19, 2012)

  • fixed man pages in the NAME section: added whatis entry
  • fixed segfault: in the internal error reporting code (delete[] in place of
  • free())
  • fixed bug: dar_manager was not able to read properly the latest generated
  • databases version when having Extended Attributes recorded for some files
  • avoided reporting unreleased memory block when compilation optimization
  • have been used (dar, dar_manager, dar_cp, dar_slave, dar_xform do all
  • reported unreleased memory when gcc optimization was used in "infinint" mode)

New in DAR 2.4.3 (Mar 19, 2012)

  • fixed absurd compilation warning about possibly uninitialized variable
  • added -ai switch to dar_manager to disable warning about improper file order
  • in database.
  • fixed bug met while changing order of archives in a dar_manager database
  • avoiding concurrent use of -p and -Q options, error message shown in that
  • situation.
  • modified slice overwriting detection code to use a single atomic system call
  • to create a new slice
  • replaced delete by delete[] for conversion routine of user/group to uid/gid
  • added the possibility to disable speed optimization for large directories
  • added memory troubleshooting option --enable-debug-memory
  • simplified class CRC implementation
  • fixed failed memory release upon exception thrown in class deci
  • modified tlv, tlv_list classes and ea_filesystem routines to not require
  • any corresponding temporary objects in libdar (saves a few new/delete calls)
  • fixed silent bug in tlv class: due to the absence of copy constructor and
  • destructor, some memory was not released and referred after the corresponding
  • object's destruction
  • modified generic_file class to avoid temporary crc objects
  • fixed bug in header class that lead unreleased field (this class lacked a
  • destructor), memory impact was however little: 10 bytes per slice
  • fixing bug in class tlv: unreleased memory
  • added protection code in class deci to properly release memory against
  • exception thrown from called routines when user interrupts the operation.
  • replace previous internal stack report code by backtrace()/backtrace_symbols()
  • complete change of the implementation of the 'special-alloc' feature:
  • the old code eat too much memory not to be adapted to new features added
  • in release 2.4.0. This new implementation also bring some speed improvement

New in DAR 2.4.2 (Sep 5, 2011)

  • fixing bug met when reading an archive in sequential-read mode
  • fixing bug while filtering in sequential-read mode
  • fixing backward compatibility in dar_manager with old archives (wrong dates
  • for deleted files).
  • fixing compilation problem on certain systems (missing #include statement)
  • fixing documentation syntax and spelling

New in DAR 2.4.1 (Jul 23, 2011)

  • adding information about "Cache Directory Tagging Standard" in doc/Feature.html
  • fixing typo in doc/presentation.html
  • fixing incomplete information in doc/usage_notes.html
  • rewriting sample scripts from tcsh to bash in doc/usage_notes.html
  • updating Swedish translation
  • fixing installation problem, where src/libdar/nls_swap.hpp was not installed fixing version returned by libdar_4_4::get_version to let kdar (or other external program relying on the backward compatible API) working as expected
  • fixed bug in the code determining whether a directory is a subdirectory of another. This bug could lead dar to restore more files that just the one that were specified with -g option.
  • added -k option to dar_manager for backward compatible behavior of dar_manager
  • fixed bug in dar_manager, was recording the wrong date of EA removal (when an inode has dropped all its EA since the archive of reference was done).
  • adapted dar_par_test.duc sample script to dar-2.4.x new behavior
  • adapted libdar to MacOS X to restore mtime date after EA, as on this system, modifying some system specific EA implies updating the mtime. But dar cannot yet store and restore the "creation date", it needs specific MacOS X code, as this value is not available through Posix EA.
  • fixed backward compatibility bug where dar 2.4.0 was not able to read archive containing only a catalogue (differential backup when no change occurred, snapshot backup, extracted catalogue) generated by dar 2.3.x or older.
  • fixed self reported internal error met when dar is merging archives generated by dar 2.3.x versions.

New in DAR 2.4.0 (Jun 3, 2011)

  • hard links support for pipes, soft links, char and block devices has been
  • added (so far, only hard links on plain files were supported)
  • added rich overwriting feature for merging archives (-/ option)
  • changed default behavior of dar: it no more tries to preserve the atime of
  • read files, which had as side effect to modify the ctime. See man page for
  • aa and -ac options for details
  • simplified the use of the "sed" command in Makefiles.am files
  • integrated Wiebe Cazemier's patch for man page
  • E option has been extended to work also when generating a single sliced
  • archive (no need to have -s option to be able to use -E option).
  • slice header has been extended to store additional information (slice
  • layout is now redundant in each each slice and may be used as backup from
  • a slice to another in case of corruption).
  • dar does no more need to read the first then the last slice of an archive to
  • get its contents, it now instead only needs the last slice.
  • an isolated catalogue can now be used as backup of the original archive's
  • internal catalogue (-A option in conjunction with -x option for example)
  • added directory look-up optimization (adaptation of Erik Wasser's patch)
  • added -e option support (aka dry-run) to archive testing
  • added the possibility to set permission and ownership of generated slices
  • re-designed the libdar API to have all optional parameters carried by class
  • object in a single argument, the aim to not break backward compatibility of
  • the API upon each new feature addition. The libdar_4_4 namespace can be used
  • for backward compatibility with older applications (see API documentation)
  • added retry on change feature (-_ option).
  • changed storage for UID and GID from U_16 to infinint to support arbitrarily
  • larger UID and GID
  • added lzo compression support
  • dar_manager now uses an anonymous pipe to send configuration to dar, this
  • solves the problem due to command-line limitation.
  • dar now stores a "removal date" when a file disappeared since the archive of
  • reference was done (so far only the information that a file was removed was
  • stored). This is needed for dar_manager (see next new feature)
  • dar_manager can now better restore the status of a set of files exactly as
  • it was at any given time from a set of full and differential backups. In
  • particular, it does no more restore files that were removed at the requested
  • date.
  • added check in dar_manager to detect conditions where a file has a
  • modification date that has been set to the past. Two objectives are at the
  • root of this feature: proper restoration of files and detection of possible
  • rootkit
  • added mode for restoration that avoid restoring directory tree which do not
  • contain any saved files (in particular when restoring a differential backup)
  • see man page for -D option for more details.
  • reviewed implementation of code managing Extended Attributes (much faster now)
  • added batch feature (-@ option) to dar_manager
  • added Furtive Read Mode support (O_NOATIME + fdopendir): when the system
  • supports it, while reading data, dar does not modify any date (ctime or atime)
  • added the possibility to have sequential reading of archives (ala tar) see
  • option --sequential-read
  • added the possibility to read from a pipe (single pipe, without dar_slave)
  • (use '-' as filename in conjunction with --sequential-read)
  • added -P -g -[ and -] options to archive listing (-l option)
  • added sparse file detection mechanism (can save and restore sparse files)
  • added dirty flag in archive for file that changed while being saved. By
  • default a warning is issued when the user is about to restore a dirty file,
  • this can be changed thanks to the --dirty-behavior option
  • R option can receive an arbitrary string (still is excepted an empty string)
  • In particular dar will no more complain if the given path contains // or \\
  • however it must in a way or another point to something that exists!
  • added a short listing feature (listing only the summary), (using both -l and
  • q options)
  • extended conditional statements in included files (DCF) with user defined
  • targets (see user target paragraph at the end of dar man page) User targets
  • let the user add a set of options using a single keyword on command-line.
  • a sample /etc/darrc is now proposed with some user targets for common
  • operation like compression without compressing already compressed files.
  • dar now releases filedescriptors of archive of reference(s) before proceeding
  • to the operation (differential backup, archive isolation, etc.)
  • user can add a comment in archive header some macro are provided for common
  • options (see --user-comment in man page). This comment can be seen when
  • listing an archive in verbose mode (-l -v) or when displaying the archive's
  • summary (-l -v -q).
  • added a "security warning" feature if ctime has changed in filesystem while
  • inode has not changed at all (-asecu disables this feature). This is to target
  • possible rootkit files. Note that this may toggle false positive, if for
  • example you change EA of a file.
  • added feature: DAR_DUC_PATH environment variable, which let dar look for a DUC
  • file (see -E and -F options) in the given path.
  • added feature: DAR_DCF_PATH environment variable, same as previously but for
  • DCF files (see -B option).
  • added two targets for conditional syntax: "reference:" and "auxiliary:"
  • weak blowfish implementation has been removed (no backward compatibility as
  • it suffered of a weak Initial Vector (IV) initialization), but the normal
  • blowfish encryption stays in place.
  • Due to openssh licensing, replaced openssh by libgcrypt dependancy (which
  • stays optional).
  • added new cyphers aes256, twofish256, serpent256 and camellia256
  • added the hash feature (--hash option), supporting md5 and sha1 algorithms.
  • The hash is calculated on the fly for each slice, before its data is even
  • written to disk. This let one to check for media corruption even before a
  • multi-sliced archive is finished. However this does not prevent an archive to
  • be corrupted due to a software bug (in dar, libdar or in a external library),
  • so it is always recommended to test the archive using dar's -t option.
  • G option (on-fly isolation) has been replaced by -@ when creating an archive,
  • to reduce the number of letter used for options. This also let available the
  • usual switches associated to -@ option to define an encryption algorithm and
  • passphrase for the on-fly isolated catalogue.
  • slices number may be padded with zeros (--min-digits option) Note that if
  • using this option when creating an archive, this same option is required for
  • any operation on this archive
  • added -konly feature to only remove files recorded as suppressed at
  • differential backup restoration time.
  • dar and libdar now store keys in secure memory (with the exception that a DCF
  • is parsed in unlocked memory, having a key in a DCF file is not as secure as
  • having dar asking for password at execution time using the "-K :" syntax)
  • added hook for backup: a user command or script can be run before saving and
  • after backing up files that match a given mask all along the backup process
  • (see - and -= options).
  • added feature: -alist-ea let the user see the Extended Attributes of files
  • while listing an archive contents.
  • dar_manager can receive negative numbers to point to archive counting by the
  • end of the database.
  • dar and libdar stay released under GPL 2.1 (not under GPL 3, and not lesser
  • GPL, neither)
  • setting the "little/big endian" to usual meaning (it was inverted in the code)
  • this does not change the dar's behavior nor its compatibility with different
  • systems or older libdar versions.
  • added -ai option to avoid warning for unknown inode types
  • added support for Solaris's Door files
  • added feature: decremental backup