On Nov 5, 2015, at 5:21 PM, Quinn Comendant <qu...@strangecode.com> wrote:
> On Thu, 5 Nov 2015 13:36:05 -0800, Colin Percival wrote:
>> There's no built-in way to do this. Due to tarsnap's encryption, there's no
>> way to "index" the archives, so any built-in command would just do what you
>> can do manually anyway; there didn't seem much point.
>
> That makes sense.
>
> It would be pretty easy to create a local index during the backup process and
> save all file paths, upload timestamp, and archive names to a text file or
> sqlite db. This would make individual file restorations much quicker. Perhaps
> there exists a tarsnap wrapper that already has this feature?
I have one such wrapper partially written, but in it I'm trying to setup some
other features which probably don't matter to anyone else. And of course, it's
the "other features" which got implemented first, not the index.
-- garance
