2 - Have the lbs-util tool check the version number when reading a
3 snapshot, and signal an error if the format is not recognized.
4 - Include a sample script, contrib/parity-gen, for creating
5 RAID-like parity sets to recover from some segment corruption.
6 The par2 command (http://parchive.sourceforge.net/) is used to
7 actually generate the parity sets; the parity-gen script simply
8 automates maintaining the parity sets.
11 - Much improved Python interface for accessing and manipulating LBS
12 archives and local database information. The interface should not
13 yet be considered completely stable.
14 - Python implementation of lbs-util now includes most of the
15 features of the Perl implementation, plus some other new features.
16 The Perl library and utility are deprecated and have been removed
18 - Preliminary snapshot restore support in lbs-util. This is still
19 not yet extensively tested.
22 - Documentation improvements: a getting started README, and a
23 description of some of the implementation details.
24 - Include an example filter script, lbs-filter-gpg, for encrypting
25 segment data as it is written.
26 - Add support for signed snapshot descriptor files (via the
27 --signature-filter option). Due to the checksums contained in the
28 snapshot descriptor, the signature covers the entire contents of
30 - Preview release of lbs-util.py, a Python-based program for
31 managing LBS snapshots. It currently implements a very simple
32 form of automatic segment cleaning, though this isn't much tested.
33 - Improved segment repacking support; after cleaning segments,
34 objects can be written out in different groups based on age. This
35 may help with long-term segment cleaning efficiency, but probably
39 - LOCAL DATABASE CHANGE: A checksums file is now written out along
40 with the snapshot descriptor that contains checksums of segments
41 used in a snapshot. This will allow quick integrity checks of a
42 snapshot, without needing to decompress or decrypt the segment
43 files. The local database schema was modified to store the
44 checksums for segments.
45 - Build dependence on libtar has been dropped. All necessary
46 support for writing TAR files is now directly included with the
48 - The snapshot format is now documented, at least in part. See
50 - Snapshots now include link count and inode number for files with
51 multiple hard links, so that a restore program could determine
52 which files should be hard linked on restore. The reference
53 restore.pl script does not use this.
54 - Bugfix: Print a help message instead of crashing if no files are
56 - Bugfix: File descriptors of files being backed up were closed
57 twice. In some cases this might have led to an unrelated file
58 being closed (if the file descriptor was quickly re-used).
59 - Preview of a new lbs-util command for maintaining snapshots.
60 Functionality is currently limited.
63 - Update reference restore.pl script to handle octal/hexadecimal
64 (format change introduced in 0.2).
65 - Better support for mixing multiple backup schemes: the statcache
66 file is now per-scheme, so performance should be better in cases
67 where multiple different backups (of different source directories)
68 are made, all sharing the same local database directory.
71 - Bugfix: Do not print an error when only one directory is specified
75 - SNAPSHOT FORMAT CHANGE: Metadata logs in backups can now contain
76 octal and hexadecimal values. Old restore programs may not be
77 able to read these new backups. The reference restore.pl script
78 has not yet been updated.
79 - LOCAL DATABASE CHANGE: Backups may be assigned a name with the
80 --scheme= command-line option, to allow different backup sets to
81 be mixed in the same directory. The database schema for the local
83 - Improved selection (inclusion/exclusion) of files to be included
85 - Device major/minor numbers are dumped for block and character