[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Listing the deltas
- To: Tom Limoncelli <tal@whatexit.org>
- Subject: Re: Listing the deltas
- From: Colin Percival <cperciva@tarsnap.com>
- Date: Wed, 06 Jun 2012 20:24:07 -0700
- Cc: tarsnap-users@tarsnap.com
- In-reply-to: <CAHVFxg=-55f8LuvjKM0-hcU4kSrL3GWvEn7JjdSm9tT1P6S9ZA@mail.gmail.com>
- References: <CAHVFxg=-55f8LuvjKM0-hcU4kSrL3GWvEn7JjdSm9tT1P6S9ZA@mail.gmail.com>
On 06/06/12 05:19, Tom Limoncelli wrote:
> On a machine where very little changes each day, there always seems to
> be 20 MB of "new data". Is there a way to list which files changed
> and were backuped?
No. The way the tarsnap code works internally, it generates a complete
archive and then figures out which blocks duplicate data previously
uploaded; the deduplication code doesn't have any way of knowing which
files data originally belonged to (and in fact there will be blocks
with data aggregated from multiple files).
> A typical --print-stats --humanize-numbers output looks like:
>
> Total size Compressed size
> All archives 408 GB 256 GB
> (unique data) 32 GB 20 GB
> This archive 40 GB 25 GB
> New data 20 MB 4.3 MB
The best way to handle this -- or at least, the way that I approached
it when I was trying to figure out why the backups of my laptop kept
having a significant amount of new data every hour -- is to run
# find / -mtime -1h
to look for recently-modified files. In my case, the culprit was in
~/.config/chromium/Default.
--
Colin Percival
Security Officer Emeritus, FreeBSD | The power to serve
Founder, Tarsnap | www.tarsnap.com | Online backups for the truly paranoid