isn't necessary to create future backups that are signed with the
same key).
- To achieve better compression, the ecnryption key can be edited to
+ To achieve better compression, the encryption key can be edited to
alter the preferred compression algorithms to list bzip2 before
zlib. Run
$ gpg --homedir /lbs.db/gpg --edit-key <encryption key>
tool for performing segment cleaning will be available in the future.
Old backup snapshots can be pruned from the snapshot directory (/lbs) to
-recover space. Deleting an old backup snapshot is a simlpe matter of
+recover space. Deleting an old backup snapshot is a simple matter of
deleting the appropriate snapshot descriptor file (snapshot-*.lbs) and
any associated checksums (snapshot-*.sha1sums). Segments used by that
snapshot, but not any other snapshots, can be identified by running the
Restoring a Snapshot
--------------------
-The restore.pl script is a simple (proof-of-concept, really) program for
-restoring the contents of an LBS snapshot. Ideally, it should be stored
-with the backup files so it is available if it is needed.
+The contrib/restore.pl script is a simple (proof-of-concept, really)
+program for restoring the contents of an LBS snapshot. Ideally, it
+should be stored with the backup files so it is available if it is
+needed.
The restore.pl script does not know how to decompress segments, so this
step must be performed manually. Create a temporary directory for
(*.lbs) in the temporary directory, and a directory where the restored
files should be written.
-A better recovery tool will be provided in the future.
+The lbs-util program also now has some preliminary support for restoring
+snapsots (documentation coming soon).