On Sat, Apr 10, 2021 at 10:34:03AM -0700, Graham Percival wrote:
> In your case, I suspect that you have many archives so it's spending a lot of
> time on this step.
>
> I've added two issues: showing progress in the setupwizard, and adding an
> import / export functionality:
>
Hi Amar,
Thanks for the info!
On minor warning: in point 2, you added a name for the new laptop.
Unfortunately version 1.02 of the gui is misleading: that field doesn't do
anything. The "machine name" is only used when creating a new key; after you
have a keyfile, all archives made with that
Thank you for the detailed write up !
--
J. Hellenthal
The fact that there's a highway to Hell but only a stairway to Heaven says a
lot about anticipated traffic volume.
> On Apr 10, 2021, at 22:58, Amar via tarsnap-users
> wrote:
>
> Hey all,
>
> I was able to do that.
>
> I decided
Hey all,
I was able to do that.
I decided to go the basic route as my data set isn’t huge and I had also lost
tarsnap.db by then (I copied it and then must have “misplaced" it - it was
4am!).
So what I did was that many of you suggested exactly:
1. Launched setup wizard, skipped it.
2.
Hi Amar,
Yes, it's correct that the gui does not need the password if you already have
a keyfile.
Behind the scenes, the "verifying archive integrity" step is running
`tarsnap --fsck` to download archive metadata. That's approximately 0.1% of
the total archive size:
Skimming docs at
https://shinnok.com/rants/2016/02/19/using-tarsnap-gui-on-os-x/ , you might
have fallen through the cracks of their UI support. I'm more familiar with the
command-line interface than the third-party GUI that runs on top of it.
For the CLI, I would setup the config and run
With everything in place on the new machine as was on the old one be sure the
cachedir exists and your config file is being read, then run tarsnap —fsck.
Once that completes you should be able to —list-archives
Lmk
--
J. Hellenthal
The fact that there's a highway to Hell but only a
With everything in place on the new machine as was on the old one be sure the
cachedir exists and your config file is being read, then run tarsnap —fsck.
Once that completes you should be able to —list-archives
Lmk
--
J. Hellenthal
The fact that there's a highway to Hell but only a
I thought it’d be straightforward but I am stuck. I am sure I am doing
something wrong I just don’t know what.
I have to return my work laptop today and that’s where I had setup Tarsnap-GUI
and have been using.
I have saved the key file, I also have the tarsnap.db file. I of course have
the
