Front page

Meaning of "obnam restore" output

09522f168e244838b6ebcccee421cbcd
ALGOL ENROLLMENT CEMENT

From: "W. Martin Borgert" <debacle@debian.org>
Date: Tue, 17 Jan 2017 21:10:20 +0100

   Hi,
   
   just curious: What does the first field of obnam restore mean?
   
   30538h53m13s 3519 files 3.24 MiB (0 %) 2.1 KiB/s /somefilenamehere
   
   TIA!
   
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: Dave Cottingham <dac@conceptual-analytics.com>
Date: Wed, 18 Jan 2017 13:37:48 -0500

   I often do a restore of a subset of a backup, and I have noticed that it
   never takes anywhere near as long as that "estimated remaining time." I
   speculate that the estimate is how long it would take to restore the whole
   backup. The same goes for the "percentage of whole job completed" -- it
   also seems to be referred to the entire backup, not just the part you asked
   for.
   
   On Wed, Jan 18, 2017 at 12:35 PM, Lars Wirzenius <liw@liw.fi> wrote:
   
   > On Tue, Jan 17, 2017 at 09:10:20PM +0100, W. Martin Borgert wrote:
   > > Hi,
   > >
   > > just curious: What does the first field of obnam restore mean?
   > >
   > > 30538h53m13s 3519 files 3.24 MiB (0 %) 2.1 KiB/s /somefilenamehere
   >
   > Let me break that into  pieces:
   >
   > 30538h53m13s            estimated remaining time to restore
   > 3519 files              how many files have been restored so far
   > 3.24 MiB                how  much data hass been restored so far
   > (0 %)                   percentage of the whole job completed
   > 2.1 KiB/s               speed of writing file data
   > /somefilenamehere       current file being restored
   >
   > That's a very long restore you're having, I'm afraid.
   >
   > --
   > I want to build worthwhile things that might last. --joeyh
   >
   > _______________________________________________
   > obnam-support mailing list
   > obnam-support@obnam.org
   > http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/
   > obnam-support-obnam.org
   >
   >
From: "W. Martin Borgert" <debacle@debian.org>
Date: Wed, 18 Jan 2017 19:32:01 +0100

   Quoting Lars Wirzenius <liw@liw.fi>:
   > Let me break that into  pieces:
   
   Thanks, that is helpful!
   
   > That's a very long restore you're having, I'm afraid.
   
   Yes, about 3.6 million files.
   
   At least, the estimated time corrected itself down to ~1500 h later.
   
   Anyway, I decided not to use obnam for this specific server. obnam
   is really nice and I will continue to use it for most of my systems,
   which are less demanding than this one. Here I'm going with borg.
   
   Cheers
   
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: Lars Wirzenius <liw@liw.fi>
Date: Wed, 18 Jan 2017 19:35:58 +0200

   On Tue, Jan 17, 2017 at 09:10:20PM +0100, W. Martin Borgert wrote:
   > Hi,
   > 
   > just curious: What does the first field of obnam restore mean?
   > 
   > 30538h53m13s 3519 files 3.24 MiB (0 %) 2.1 KiB/s /somefilenamehere
   
   Let me break that into  pieces:
   
   30538h53m13s            estimated remaining time to restore
   3519 files              how many files have been restored so far
   3.24 MiB                how  much data hass been restored so far
   (0 %)                   percentage of the whole job completed
   2.1 KiB/s               speed of writing file data
   /somefilenamehere       current file being restored
   
   That's a very long restore you're having, I'm afraid.