Unfortunately, nodump only refers to single files. If you want to exclude
every single instance of .DS_Store, then you would either need to set nodump
on every single .DS_Store file on your computer, or use the "exclude" method.
My apologies for giving you imprecise advice earlier.
Instead, I
Greetings,
I'm not certain that I understand the question. If you run:
tarsnap -c -f myname ~
or maybe
tarsnap -c -f myname /Users/sa/
then it will back up all the files and directories of your user
account. Are you trying to automatically exclude all
sub-directories from being backed
On Wed, Jun 08, 2016 at 10:34:09PM -0400, Graham Percival wrote:
> Another option that might be helpful: if you use the -T (or
> --files-from) option, you can specify a file which contains a list
> of files or directories. That way, if you put this line inside
> your tarsnap.conf:
&g
The value you specified, --maxbw 2000, is 200 gigs. --maxbw should
work with values like 2G or 2M. Note that the G and M must be capital
letters.
(although if you use a lower-case letter, it will give you an error message)
To test this, I recommend setting it to a small value such as
tarsnap backend is not be used by the same key at the same time.
Yes. This is covered in:
http://www.tarsnap.com/multiple-machines.html
Cheers,
- Graham Percival
exist: archivename-2014010103
> > tarsnap: Error deleting archive
>
> Hmm, I never thought of that. Maybe we should have a --keep-going option?
> https://github.com/Tarsnap/tarsnap/issues/77
To clarify for the list archives: --keep-going was added in Tarsnap 1.0.37.
Cheers,
- Graham Percival
On Sat, Apr 16, 2016 at 10:42:40AM +0100, John wrote:
> In order to archive data when constant updating takes place, even
> just an email INBOX or a SQL database, the data has to stop
> changing. The frozen unchanging data is the source for the archive
> and an overspill area, called - very
On Sat, Apr 23, 2016 at 08:50:22AM +0100, John wrote:
> I'd have thought my problem was commonplace. The machine is a
> server. It has to remain available continuously and can be updated
> at any moment. It handles, for example, SQL updates and email, I
> can't just switch it to read-only for the
On Sun, Jul 24, 2016 at 05:20:41PM -0400, James Cass wrote:
>Is there a way to force long-iso date format when retrieving a file list
>from the Tarsnap server? By long-iso date format, I mean: -mm-dd
>hh:mm:ss. I didn't see anything in the man page, unless I overlooked it.
If
I see these lines in your config.log:
configure:6048: checking for RSA_private_encrypt in -lcrypto
configure:6073: gcc -o conftest -O2 -pipe -fomit-frame-pointer
-fno-caller-saves -Wl,-rpath=/opt/lib
-Wl,--dynamic-linker=/opt/lib/ld-linux-x86-64.so.2 -L/opt/lib conftest.c
-lcrypto -lz -lrt
arning: you do not have execution permission for
>`/opt/lib/libcrypto.so.1.0.0'
>A A A A linux-vdso.so.1 (0x7fffedb11000)
>A A A A libdl.so.2 => /opt/lib/libdl.so.2 (0x7f0a72aeb000)
>A A A A libc.so.6 => /opt/lib/libc.so.6 (0x7f0a7274c000)
>
It's not entirely clear why you want to run multiple dry runs at the same
time. Wouldn't it be simpler to create one setup, test it, then tweak the
setup if needed?
At the moment, you cannot run multiple tarsnap commands if you are using a
cache directory. If you remove cachedir from your
On Sat, Feb 18, 2017 at 03:39:10PM +0100, Philip Paeps wrote:
> I could presumably set an ACL on the cache directory but I wonder if
> this sort of thing really needs access to the cache. I know that the
> Tarsnap server doesn't know anything about the individual archives, but
> it surely knows
On Thu, Sep 29, 2016 at 10:11:57PM +0300, Nikolay Amiantov wrote:
> 1. User (me) has several tarsnap configurations with different cache
> directories and one common key file.
What are you trying to achieve with this? I mean, what usage
scenario do you have in mind?
I can imagine having
On Thu, Sep 29, 2016 at 10:38:01PM +0300, Nikolay Amiantov wrote:
> I've described the situation further in my mail ;)
I couldn't quite understand the bottom part of your initial email,
so I thought it was safer to point you towards the (new) docs.
> Anyway, your links are very helpful and I
On Sat, Dec 31, 2016 at 12:19:09AM +0100, Scott Wheeler wrote:
> bela: /tmp/foo> sudo tarsnap -xvf test --newer "Jan 1, 2016"
--newer is only specified for working with -c:
$ man tarsnap
...
--newer date
(c mode only) Only include files and directories newer than the
specified
On Thu, Oct 20, 2016 at 10:08:43AM +0100, Daniel Neades wrote:
> > Maybe we should add a --passphrase-force option which overrides tarsnap's
> > attempt to autodetect whether there's enough memory. (Does anyone have a
> > preference for what the option is named?)
>
> An option like that would be
mpiling.html
Cheers,
- Graham Percival
On Thu, Mar 02, 2017 at 11:25:26AM -0500, Steve Holmes wrote:
> Just a heads-up: tarsnap (v1.0.37) will not compile with headers from the
> openssl v1.1.0 series. This is (from what I can see) due to changes in the
> definition of “struct rsa_st” in rsa
On Wed, Jul 12, 2017 at 09:36:39AM -0400, Rob Hoelz wrote:
> I just started using tarsnap, and I was wondering if there exists an
> option (or the potential interest in developing an option) to put a cap
> on an archive size.
Not exactly what you're looking for, but it would be easy to add a
On Wed, Jul 12, 2017 at 12:57:07PM -0700, Graham Percival wrote:
> This could be wrapped into the "Receiving emails from making backups" tip:
> http://www.tarsnap.com/tips.html#receive-mail
... and I just noticed some debug code in that script that I forgot to remove
before publi
command multiple
times, once for every keyfile.
Once we know where your data is, we can work on getting the GUI to recognize
it. (I suspect that you might have multiple keyfiles, which would explain the
GUI's confusion.)
Cheers,
- Graham Percival
On Thu, Sep 21, 2017 at 06:58:43PM -, a...@sdf.org wrote:
> Sorry for the delay. Here's the file type distribution (some are unknown;
> I just shared as powershell printed):
Thanks! This looks quite reasonable to me. Just to keep the data together, in
another email you wrote:
> I am
On Thu, Sep 07, 2017 at 08:21:42AM -, a...@sdf.org wrote:
> I believe too much feedback in my last mail might have been off-putting
> and judgemental (and kinda unsolicited advice) :-) Or not.
Hi Amar,
No, your previous mail wasn't too judgemental at all! Sorry for the delay.
> > I am
t's almost certainly not worth it for for general-purpose desktop
computers.
Cheers,
- Graham Percival
On Sat, Apr 28, 2018 at 04:36:00AM -0400, Robert Bowers wrote:
> now, i want to exclude any empty.file in a first level directory (relative to
> /tmp/zzz).
> # cat /tmp/zzz.excludes
> /tmp/zzz/*/empty.file
* matches with / as well. So that will exclude any filename beginning with:
/tmp/zzz/
Hi all,
We just released Tarsnap GUI 1.0.1, which fixes some build problems with Qt
5.10 and 5.11 (both released after Tarsnap GUI 1.0). If you're already happily
using Tarsnap GUI, there's no need to upgrade.
Cheers,
- Graham
On Sat, Apr 28, 2018 at 01:35:31PM -0400, Robert Bowers wrote:
> >Unfortunately not. As noted in http://www.tarsnap.com/selecting-files.html
> >the behaviour of --include and --exclude comes from BSD tar. For example,
> >"In particular, 'a*b' will match 'foo/a/222b/bar"
> >
> >
On Mon, Feb 12, 2018 at 10:12:49PM +0530, Amar wrote:
> Say, if I lost just one folder or few files, I wanted to see if there’s a way
> in the GUI to restore “only” those particular file/folder(s) from one of the
> archive versions instead of downloading the entire archive.
Yes, you can certainly
On Fri, Aug 03, 2018 at 06:56:29AM -0500, Ed Ahlsen-Girard wrote:
> If I narrow the sieve and run a backup with it, then delete the space
> pig, will the sieved down backup retain those bytes from the deleted
> archive that are still in scope,
Yes! As long as you create the new backup first,
Hi all,
We just released Tarsnap GUI 1.0.2, which adds two new features for MacOS X:
- Adds a --check option to update the MacOS X launchd path (in case the app's
path changed, for example during a brew update).
- Automatically searches for the tarsnap CLI in /usr/local/bin (which is where
On Thu, Nov 08, 2018 at 05:20:12PM -0800, Craig Hartnett wrote:
> Just signed up
Welcome!
> (e.g., tarsnap --dry-run --print-stats --humanize-numbers
> -c /media/USER/PATH
> --exclude /media/USER/PATH/.Trash-1000 /media/USER/PATH/lost
> +found /media/USER/PATH/OTHER-EXCLUDED-DIRECTORY)
Careful
On Sun, Nov 11, 2018 at 06:02:31PM -0800, Craig Hartnett wrote:
> But I have to ask now, and it's something I think would be very useful
> to include on the "Getting started" page, how long should the first
> back-up take? I realise that's asking how long is a piece of string, but
> my first
On Thu, Nov 08, 2018 at 07:57:42PM -0800, Michael Sierchio wrote:
>envoyé par un téléphone mobile avec «autocorrect» démoniaque
>On Thu, Nov 8, 2018, 18:07 Graham Percival <[1]gperc...@tarsnap.com
>wrote:
>
> Careful there! "--exclude" only accepts a
On Fri, Nov 23, 2018 at 05:33:03PM -0800, Craig Hartnett wrote:
> Hi Graham,
>
> Thanks for your reply. Sorry for not getting back to you sooner.
No problem. I'm glad it worked out!
> The cron job has been happily running all week, so things are good.
> However, the script at
Hi Craig,
If you'd like a better understanding of deduplication, I very much recommend:
http://www.tarsnap.com/deduplication-explanation.html
(new page from 6 weeks ago, so regular tarsnap users probably haven't seen it)
I made up an example of "wordification" (where we make multiple backups of
On Thu, Apr 04, 2019 at 10:20:34PM -0400, Julian Lam wrote:
> Seems I'm running out of money on my account, so I wanted to go ahead and
> nuke what I had, except I'm unable to at this time:
>
> /usr/bin/tarsnap --key tarsnap.key --cachedir .tarsnap-cache --fsck
> tarsnap: Connection lost, waiting
On Fri, Mar 15, 2019 at 12:42:39AM -0700, Craig Hartnett wrote:
> On Thu, 2019-03-14 at 20:21 -0700, Graham Percival wrote:
> > $ tarsnap -d --archive-names todelete.txt
>
> Brilliant! Almost exactly what I was looking for and it worked
> perfectly. Thanks Graham. Only pro
On Fri, Mar 15, 2019 at 10:38:52AM -0700, Graham Percival wrote:
> I started in July of 2012, and
Correction: I started using Tarsnap before that, but I switched
email addresses in 2012 and didn't keep my older archives (I just
started making new archives with my new Tarsnap account).
Che
On Thu, Mar 14, 2019 at 05:39:42PM +0200, hvjunk wrote:
> > On 14 Mar 2019, at 17:27 , Craig Hartnett
> > wrote:
> >
> > I've skimmed the sources of some of the "helper scripts" that offer
> > archive rotation (and, of course, done a web search), but I can't seem
> > to figure out how to use
/.local/lib/:$LIBRARY_PATH
export PKG_CONFIG_PATH=$HOME/.local/lib/pkgconfig/:$PKG_CONFIG_PATH
They won't all be relevant to this case, but there's no harm in adding all
these lines to a startup file. Of course, replace $HOME/.local/lib/ with
/usr/local/ in your case.
Cheers,
- Graham Percival
every x backups. Similar idea to running deltas most of the
>time, then a full one every period.
>Cheers,
>Scott
>
>On 25 June 2019 7:09:54 am AEST, Graham Percival
>wrote:
>
> Hi Scott,
> Thanks for clarifying the use case! Colin had the idea of using
Hi Scott,
Thanks for clarifying the use case! Colin had the idea of using the Tarsnap
cache to detect disk errors. Namely, if the filesystem reports that a file
hasn't changed, there would be a random chance that the tarsnap client would
read the file anyway, and compare the chunk hashes
se packages out there.
Cheers,
- Graham Percival
libssl-1.1, and were
compiled against that instead of 1.0.2. You can see all commits which went
into this update here:
https://github.com/Tarsnap/tarsnap/commits/1.0.39-deb-2
If everything goes well, these should become the non-experimental packages in
a week or so.
Cheers,
- Graham Percival
On Tue, Oct 08, 2019 at 01:00:48PM -0700, Colin Percival wrote:
> Why your shell cares about tarsnap's exit code, I don't know; normal POSIX
> shells ignore the exit codes from processes other than the last one in a
> pipeline. Maybe systemd launches bash with some weird "don't behave the way
>
On Tue, Oct 08, 2019 at 07:28:36PM +0200, Simon Levermann wrote:
> The script itself only writes to stdout. I'm assuming systemd is trying to
> prevent some action that the tarsnap script is taking.
tarnap is trying to write to stdout (if you're curious, this is at line 238 of
On Tue, Apr 14, 2020 at 04:27:18PM -0400, Michael Jung wrote:
> Tarsnap runs as "root" via cron although it still fails if I run in
> manually.
Do you mean that Tarsnap "attempts to run as root via cron (but fails)", or
"it successfully runs as root via cron"?
Occasionally somebody will get
On Tue, Apr 14, 2020 at 03:56:05PM -0400, Michael Jung wrote:
> Tarsnap 1.0.39
> FreeBSD 12.0 r326073
Thanks for the report! At the moment I don't have any leads, but a few more
pieces of info might give a clue.
Is that installed via ports / pkg, or compiled from the official 1.0.39
tarball?
On Tue, Apr 14, 2020 at 06:54:09PM -0400, Michael Jung wrote:
> "USER ERROR" with conflicting configuration. "tarsnap --fsck" was using
> /usr/local/etc/tarsnap.conf
> and my batch file was using another cache directory.
Great, I'm glad that it worked out! ... although I'm sorry that you had to
speed"
means "with a great deal of caution". :)
Cheers,
- Graham
On Tue, Sep 01, 2020 at 09:45:42AM -0300, Mauro Ciancio wrote:
> Hi Graham! Thanks for that!
> Any idea when the next Tarsnap client will be released?
> Thanks.
>
> On Mon, Aug 31, 2020 at 2:05 PM Graham
Hi Mauro,
Not in the latest official tarball, 1.0.39. The NEWS.md file in
the git repository does list a new --passphrase-stdin option [1],
which could be used with an environment var [2].
It might be worth mentioning that scrypt 1.3.1 (released last week
[3]) added a host of new password entry
On Tue, Aug 25, 2020 at 10:57:44AM -0700, Simon Willison wrote:
> I’d like the server that I backup using Tarsnap to only host the encryption
> key needed to create the encrypted backup. I don’t want it to have the
> decryption key used when running "tarsnap -x -f” to restore a backup.
As James
Hi Arthur,
Deduplication is tied to each machine key.
If you have multiple machines using the same key, then data will
be deduplicated between all those systems [1]. If you have
multiple machine keys, then there will be no deduplication between
them.
[1] If you are sharing a machine key, then
email), then the instructions would cease the be
copy but maybe the "2019" vs. "2020" would be a clear enough
thing to change? I'll have to think about it some more.
Cheers,
- Graham Percival
Could you please send me the output of
ls -al /root/tarsnap-cache
? (if the `ls` command gives you "Permission denied", try adding
a `sudo` to it)
Cheers,
- Graham Percival
On Tue, Jul 21, 2020 at 06:01:09PM +, Brendan K. wrote:
> Hi,
> I ran into a problem I canno
keep-going -f 1 -f 2 -f 3 -f 4 -f 5 -f 6
and cancel the command after it's deleted archives 1 and 2, you
can just repeat
tarsnap -d --keep-going -f 1 -f 2 -f 3 -f 4 -f 5 -f 6
without having to remove "-f 1 -f 2" from the command. (The same
goes if you have the archive names in a file.)
Cheers,
- Graham Percival
On Tue, Aug 04, 2020 at 08:48:21AM +0200, hvjunk wrote:
> Deleting 7 archives (I at present I’m in need for pruning many more) Takes
> around 3hours?
> My traffic utilization also shot throw the roof, but I recall something that
> is how the dice rolls with tarsnap, so I’ll have to live with
hly report also has the information — how many days worth of
> balance is left?
> And yes, I would want to receive that. What should I do for that? Shall I
> wait for FAQ update, or you could share the steps here please?
>
> Amar
>
> > On 4 Aug 20, at 10:32 PM, Graham Percival
I'm adding it now.
Cheers,
- Graham Percival
On Tue, Aug 04, 2020 at 11:34:59AM +0530, Amar via tarsnap-users wrote:
> Can we add (maybe) a 30 days and another 15 days warning along with the
> existing 7 days warning?
> Before the "possible deletion" timer starts which is agai
to unauthorize the machine?
>
> Best,
> Brandon
>
> On Sun, Jul 5, 2020, at 1:01 PM, Graham Percival wrote:
> > Hi Brandon,
> >
> > When you say that --fsck has not yielded any results, what do you
> > mean? You should see something like this:
> >
Hi Brian,
I'll present three things: a workaround, an acknowledgement, and
potentially a different solution for your problem. :)
Workaround for --sort: I stumbled across this myself two weeks
ago, although I was aiming for merely "deterministic", rather than
any particular ordering.
export
inspired by
https://github.com/libarchive/libarchive/issues/1071#issuecomment-427807094))
I'll keep on playing with solution #2, so it's possible that I
might be able to send an update. FWIW, the regex is interpreted
with regcomp() using REG_BASIC.
Cheers,
- Graham Percival
On Thu, Jun 25, 202
eans that we can investigate the permission problem
> with shell commands.
>
> Could you please send me the output of
> ls -al /root/tarsnap-cache
> ? (if the `ls` command gives you "Permission denied", try adding
> a `sudo` to it)
>
> Cheers,
> - Graham Per
Hi Brandon,
When you say that --fsck has not yielded any results, what do you
mean? You should see something like this:
$ tarsnap --keyfile .test-tarsnap/tarsnap.keys --fsck
Phase 1: Verifying metadata validity
Phase 2: Verifying metadata/metaindex consistency
Phase 3: Reading
On Wed, May 26, 2021 at 10:35:37PM +0200, Scott Wheeler wrote:
>
> > On 26 May 2021, at 22:19, hvjunk wrote:
> >
> > --fast-read also not the next issue… but yeah, looks like that latency is
> > the killer for my use case ;(
>
> I don’t think latency is the issue:
Colin specifically says
The "recent usage" pages say:
(updates shortly after midnight UTC)
So if you've only just created the new key, it wouldn't show up yet.
Cheers,
- Graham
On Sun, Jun 27, 2021 at 10:29:15AM +1200, Romo Hu wrote:
> Hi,
>
> I created a new key for machine and did backup, and "tarsnap
>
Hi Romu,
The general term for this is "Backup rotation scheme", if you want to see some
approaches that other people use:
https://en.wikipedia.org/wiki/Backup_rotation_scheme
I don't recommend only keeping the last 3 days, for the reasons described on
the "First in, first out" section on the
ers,
- Graham Percival
employees access to the full tarsnap keys.
Create write-only keys so that your employees can create archives, but they
cannot read or delete them:
https://www.tarsnap.com/tips.html#write-only-keys
Cheers,
- Graham Percival
E" ?
Yes. (And even if the tarsnap binary couldn't handle such keyfiles, it would
be easy to add that text yourself during recovery.)
There's also a checksum at the end of every line. If you look at
lib/keyfile/keyfile.c, you can see the details.
Cheers,
- Graham Percival
Hi Ankit,
First, I recommend checking the list of files in the archive:
tarsnap -t -v -f
-t lists the filename, and -v also writes the file sizes. That will allow you
to confirm that the files are definitely in the archive.
Second, if the archive looks good, I recommend (temporarily)
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:
be a nice tarsnap-gui feature though.
>
> 6. Hit backup and it was done. 170kB new data was added.
>
> Thank you all :)
>
> > On 10-Apr-2021, at 11:04 PM, Graham Percival wrote:
> >
> > Hi Amar,
> >
> > Yes, it's correct that the gui does not need
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:
>
the right thing to do in this case.
Cheers,
- Graham Percival
On Tue, Aug 31, 2021 at 12:55:50PM -0500, J. Hellenthal via tarsnap-users wrote:
>
> Definitely related to the problem that seems to be a miscommunication or
> calculation on the cache directory itself.
>
> Personally I
Technically, you can't rename an archive, because they're immutable (as a
security feature) [1].
However, you can reproduce the effect of "renaming" by copying an archive [2]
and deleting the old one.
[1] https://www.tarsnap.com/usage.html
[2] https://www.tarsnap.com/tips.html#copy-archive
initial discussion:
https://github.com/Tarsnap/tarsnap/issues/475
and here's the commit in the tarsnap-public-keys repository:
https://github.com/Tarsnap/tarsnap-public-keys/commit/cc32d2b5fc2c3e955efe651dbeb65a6c708b8fab
Cheers,
- Graham Percival
it already; this paragraph is
intended for anybody who discovers this message in the mailing list archives
via a web search.)
Cheers,
- Graham Percival
at 11:45:38AM -0700, Graham Percival wrote:
> We have experimental packages and instructions for .deb packages which support
> "signed-by" repositories. This is relevant for people using Debian, Ubuntu,
> Mint, ElementaryOS, Pop!_OS, etc.
>
> The old method (using apt-key
uild it, aren't affected?
>
> - Jerry Kaidor
>
> On 2021-10-13 11:45, Graham Percival wrote:
> > We have experimental packages and instructions for .deb packages which
> > support
> > "signed-by" repositories. This is relevant for people usi
Thanks for the report! Yes, the tarsnap archive keys recently changed -- we
update them every year in January. I think that I updated all relevant parts
of the website, but I'm always willing to believe that I screwed something up.
Alternate source, if you want more confirmation than a mere
6 packages for other
distributions.)
If all goes well, these will become the official packages in a few weeks.
Cheers,
- Graham Percival
[1] there is no installation image for Ubuntu jammy on i386:
https://cdimage.ubuntu.com/releases/22.04/release/
and pbuilder requires aptitude, for which u
Hi Federico,
My first thought: do you have a computer (or user account) that you forgot
about? For example, you might have an ubuntu server that's faithfully making
an archive every night using the same keyfile as you're using on your MacOS
machine.
That's a very unlikely theory, but it's easy
e, but I don't know if it's wise to do so from a security
> perspective.
>
> Just that I understand 100% correctly, the cachedir should only change
> whenever I run an archive, right?
>
> Thank you!
>
> чт, 15 сент. 2022 г. в 21:06, Colin Percival :
>
> > On 9/15/2
At the moment, all Canadians receive invoices (which include balance
notifications) once a month. Non-Canadians can receive them upon
request (although a physical mailing address is required for the
invoice).
https://www.tarsnap.com/faq.html#monthly-invoices
I know that this isn't exactly what
d names, and auto delete any one
> that's older than a couple of years.
>
> Not really interested in paper invoices. I detest paper. Have way too
> much of it already. In fact, tarsnap is part of my general "eliminate
> paper"
> strategy.
>
> - Jerry
86 matches
Mail list logo
