Front page

listing differences between generations / changed files

41ef23c2878f4c2cbbf840a6cc29cbcc
CRANKY UNRAVEL BLOWTORCH

From: Spike <spike@drba.org>
Date: Thu, 21 Jul 2016 07:53:51 -0700

   Hi again,
   
   per documentation, for subsequent runs of obnam backups only files that
   have changed are backed up and I'd love to have a report/something telling
   me what exactly changed.
   
   I've tried setting log-level to debug, but I get a bunch of statements
   about excludes and the normal "INFO Backing up..." which btw I find
   misleading as it doesn't seem like that file is backed up as much as
   "scanned" or something (since they haven't changed). Anyway, no trace of a
   statement saying "Changed" or something like that I can see in the log file.
   
   I've also tried --verbose, but same deal, nothing was printed about changed
   files.
   
   I'm also not seeing a command to achieve that, something like
   "generations-diff".
   
   can anybody shed some light on how I'd go about figuring this one out?
   
   thanks,
   
   Spike
From: Spike <spike@drba.org>
Date: Thu, 21 Jul 2016 08:31:27 -0700

   I'm clearly blind, my bad, "diff" command is in the manpage and does what I
   expected. It would still be nice to differentiate this in the log I think,
   so instead of saying "Backing up" for everything it could log that the file
   was scanned and if it needed to be backed up or not. Am I missing that too?
   
   On Thu, Jul 21, 2016 at 7:53 AM, Spike <spike@drba.org> wrote:
   
   > Hi again,
   >
   > per documentation, for subsequent runs of obnam backups only files that
   > have changed are backed up and I'd love to have a report/something telling
   > me what exactly changed.
   >
   > I've tried setting log-level to debug, but I get a bunch of statements
   > about excludes and the normal "INFO Backing up..." which btw I find
   > misleading as it doesn't seem like that file is backed up as much as
   > "scanned" or something (since they haven't changed). Anyway, no trace of a
   > statement saying "Changed" or something like that I can see in the log file.
   >
   > I've also tried --verbose, but same deal, nothing was printed about
   > changed files.
   >
   > I'm also not seeing a command to achieve that, something like
   > "generations-diff".
   >
   > can anybody shed some light on how I'd go about figuring this one out?
   >
   > thanks,
   >
   > Spike
   >
From: Spike <spike@drba.org>
Date: Thu, 21 Jul 2016 11:02:04 -0700

   thanks for your reply Jan. You're right, I'm new to backups doing
   deduplication so still thinking about "files". I guess I'll just script
   something to run diff after a backup job to build a daily report (that's my
   end goal, having something to review daily to ensure the backup did
   something meaningful in between testing restores - which isn't going to
   happen daily).
   
   On Thu, Jul 21, 2016 at 10:42 AM, Jan Brodda <jan@janbrodda.de> wrote:
   
   > So you have found the answer to your first question by yourself, nice! ;)
   >
   > I think you cannot say "this file doesn't need to be backed up, because it
   > exists", because deduplication is not based on files, but on small parts of
   > those files. So maybe you could say "I only had to upload 20% of this file,
   > the other 80% were deduplicated".
   >
   > But i think this would not be helpful and maybe hurt performance..
   >
   > ---------
   > janxb
   >
   > Spike <spike@drba.org> schrieb am Do., 21. Juli 2016 um 17:31 Uhr:
   >
   >> I'm clearly blind, my bad, "diff" command is in the manpage and does what
   >> I expected. It would still be nice to differentiate this in the log I
   >> think, so instead of saying "Backing up" for everything it could log that
   >> the file was scanned and if it needed to be backed up or not. Am I missing
   >> that too?
   >>
   >> On Thu, Jul 21, 2016 at 7:53 AM, Spike <spike@drba.org> wrote:
   >>
   >>> Hi again,
   >>>
   >>> per documentation, for subsequent runs of obnam backups only files that
   >>> have changed are backed up and I'd love to have a report/something telling
   >>> me what exactly changed.
   >>>
   >>> I've tried setting log-level to debug, but I get a bunch of statements
   >>> about excludes and the normal "INFO Backing up..." which btw I find
   >>> misleading as it doesn't seem like that file is backed up as much as
   >>> "scanned" or something (since they haven't changed). Anyway, no trace of a
   >>> statement saying "Changed" or something like that I can see in the log file.
   >>>
   >>> I've also tried --verbose, but same deal, nothing was printed about
   >>> changed files.
   >>>
   >>> I'm also not seeing a command to achieve that, something like
   >>> "generations-diff".
   >>>
   >>> can anybody shed some light on how I'd go about figuring this one out?
   >>>
   >>> thanks,
   >>>
   >>> Spike
   >>>
   >>
   >> _______________________________________________
   >> obnam-support mailing list
   >> obnam-support@obnam.org
   >>
   >> http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
   >>
   >
   > _______________________________________________
   > obnam-support mailing list
   > obnam-support@obnam.org
   >
   > http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
   >
   >
From: Jan Brodda <jan@janbrodda.de>
Date: Thu, 21 Jul 2016 17:42:44 +0000

   So you have found the answer to your first question by yourself, nice! ;)
   
   I think you cannot say "this file doesn't need to be backed up, because it
   exists", because deduplication is not based on files, but on small parts of
   those files. So maybe you could say "I only had to upload 20% of this file,
   the other 80% were deduplicated".
   
   But i think this would not be helpful and maybe hurt performance..
   
   ---------
   janxb
   
   Spike <spike@drba.org> schrieb am Do., 21. Juli 2016 um 17:31 Uhr:
   
   > I'm clearly blind, my bad, "diff" command is in the manpage and does what
   > I expected. It would still be nice to differentiate this in the log I
   > think, so instead of saying "Backing up" for everything it could log that
   > the file was scanned and if it needed to be backed up or not. Am I missing
   > that too?
   >
   > On Thu, Jul 21, 2016 at 7:53 AM, Spike <spike@drba.org> wrote:
   >
   >> Hi again,
   >>
   >> per documentation, for subsequent runs of obnam backups only files that
   >> have changed are backed up and I'd love to have a report/something telling
   >> me what exactly changed.
   >>
   >> I've tried setting log-level to debug, but I get a bunch of statements
   >> about excludes and the normal "INFO Backing up..." which btw I find
   >> misleading as it doesn't seem like that file is backed up as much as
   >> "scanned" or something (since they haven't changed). Anyway, no trace of a
   >> statement saying "Changed" or something like that I can see in the log file.
   >>
   >> I've also tried --verbose, but same deal, nothing was printed about
   >> changed files.
   >>
   >> I'm also not seeing a command to achieve that, something like
   >> "generations-diff".
   >>
   >> can anybody shed some light on how I'd go about figuring this one out?
   >>
   >> thanks,
   >>
   >> Spike
   >>
   >
   > _______________________________________________
   > obnam-support mailing list
   > obnam-support@obnam.org
   >
   > http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
   >