Front page

First backup is stuck(?)

67640f923e584a91809c69b2be604f7f
FREEDOM GETAWAY ARTIST

From: Johannes Frölich <johannes.froelich@gmail.com>
Date: Tue, 10 Jan 2017 16:01:40 +0100

   Hey,
   
   i just did my first backup using obnam. The problem now is, that it seems to be stuck. i backed up ~170GB from a raspberry pi (USB HDD) to a network (NFS) Share (GB Lan). The output now is:
   
   "15h08m29s 25413 files 173.89 GiB scanned: removing checkpoints"
   
   so - since 15h it is „removing chekcpoints“ (btw - while consuming 100% cpu).
   
   Is this normal? If so is there any chance to know when it is ready?
   
   Thank you so much,
   
   Cheers
From: SanskritFritz <sanskritfritz@gmail.com>
Date: Tue, 10 Jan 2017 16:22:26 +0100

   On Tue, Jan 10, 2017 at 4:08 PM, Lars Wirzenius <liw@liw.fi> wrote:
   > If you don't want to wait, you can use control-c to interrupt it. By
   > the time this happening, Obnam has already finish the actual backup,
   > and interrupting should be quite safe.
   
   Which will leave lots of unnecessary generations behind I might add.
   But those can be removed later with --forget.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: Johannes Frölich <johannes.froelich@gmail.com>
Date: Tue, 10 Jan 2017 16:25:17 +0100

   I mean as far as i understand the way obnam works it will do that for the initial big backup.
   Future small changes will then not take that long, so ill give it some days to do whatever it is doing now ;)
   
   Thank you so much for your help!!
   
   Cheers
   
   
   > Am 10.01.2017 um 16:22 schrieb SanskritFritz <sanskritfritz@gmail.com>:
   > 
   > On Tue, Jan 10, 2017 at 4:08 PM, Lars Wirzenius <liw@liw.fi> wrote:
   >> If you don't want to wait, you can use control-c to interrupt it. By
   >> the time this happening, Obnam has already finish the actual backup,
   >> and interrupting should be quite safe.
   > 
   > Which will leave lots of unnecessary generations behind I might add.
   > But those can be removed later with --forget.
From: SanskritFritz <sanskritfritz@gmail.com>
Date: Tue, 10 Jan 2017 16:29:48 +0100

   My 2 cents:
   I usually start any backup with a small set and gradually build it up
   to the whole amount I actually want to backup. Takes some time and
   fiddling but the gradual process also helps discovering unnecessary
   parts in the backup which eventually land in the exclude file.
   
   
   
   
   
   On Tue, Jan 10, 2017 at 4:25 PM, Johannes Frölich
   <johannes.froelich@gmail.com> wrote:
   > I mean as far as i understand the way obnam works it will do that for the
   > initial big backup.
   > Future small changes will then not take that long, so ill give it some days
   > to do whatever it is doing now ;)
   >
   > Thank you so much for your help!!
   >
   > Cheers
   >
   >
   >
   > Am 10.01.2017 um 16:22 schrieb SanskritFritz <sanskritfritz@gmail.com>:
   >
   > On Tue, Jan 10, 2017 at 4:08 PM, Lars Wirzenius <liw@liw.fi> wrote:
   >
   > If you don't want to wait, you can use control-c to interrupt it. By
   > the time this happening, Obnam has already finish the actual backup,
   > and interrupting should be quite safe.
   >
   >
   > Which will leave lots of unnecessary generations behind I might add.
   > But those can be removed later with --forget.
   >
   >
   >
   > _______________________________________________
   > 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: Johannes Frölich <johannes.froelich@gmail.com>
Date: Tue, 10 Jan 2017 16:36:48 +0100

   That is actually pretty much what i did ;)
   I am Backupping an owncloud instance - so the thing is that there are some configuration folders (which i first backed up to see wether i can handle obnam (like recover data and so on)) and one huge folder (almost the full 170GB) user data. so i added this folder then too. Maybe i should have started with completely different data to see how long it takes, but anyway at one point i would have done this anyway… so ill just wait… something will happen ^^
   
   Cheers and thanks!
   
   
   > Am 10.01.2017 um 16:29 schrieb SanskritFritz <sanskritfritz@gmail.com>:
   > 
   > My 2 cents:
   > I usually start any backup with a small set and gradually build it up
   > to the whole amount I actually want to backup. Takes some time and
   > fiddling but the gradual process also helps discovering unnecessary
   > parts in the backup which eventually land in the exclude file.
   > 
   > 
   > 
   > 
   > 
   > On Tue, Jan 10, 2017 at 4:25 PM, Johannes Frölich
   > <johannes.froelich@gmail.com> wrote:
   >> I mean as far as i understand the way obnam works it will do that for the
   >> initial big backup.
   >> Future small changes will then not take that long, so ill give it some days
   >> to do whatever it is doing now ;)
   >> 
   >> Thank you so much for your help!!
   >> 
   >> Cheers
   >> 
   >> 
   >> 
   >> Am 10.01.2017 um 16:22 schrieb SanskritFritz <sanskritfritz@gmail.com>:
   >> 
   >> On Tue, Jan 10, 2017 at 4:08 PM, Lars Wirzenius <liw@liw.fi> wrote:
   >> 
   >> If you don't want to wait, you can use control-c to interrupt it. By
   >> the time this happening, Obnam has already finish the actual backup,
   >> and interrupting should be quite safe.
   >> 
   >> 
   >> Which will leave lots of unnecessary generations behind I might add.
   >> But those can be removed later with --forget.
   >> 
   >> 
   >> 
   >> _______________________________________________
   >> 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: Tue, 10 Jan 2017 17:08:39 +0200

   On Tue, Jan 10, 2017 at 04:01:40PM +0100, Johannes Frölich wrote:
   > Hey,
   > 
   > i just did my first backup using obnam. The problem now is, that it seems to be stuck. i backed up ~170GB from a raspberry pi (USB HDD) to a network (NFS) Share (GB Lan). The output now is:
   > 
   > "15h08m29s 25413 files 173.89 GiB scanned: removing checkpoints"
   > 
   > so - since 15h it is „removing chekcpoints“ (btw - while consuming 100% cpu).
   > 
   > Is this normal? If so is there any chance to know when it is ready?
   
   It's "normal" in that it's know  that it happens, but abnormal in that
   it  would be  nice  if  it didn't.  Obnam  doesn't  give any  progress
   reporting when  this is  going on (sorry),  and it can  take a  lot of
   time.
   
   If you don't want to wait, you can use control-c to interrupt it. By
   the time this happening, Obnam has already finish the actual backup,
   and interrupting should be quite safe.
From: SanskritFritz <sanskritfritz@gmail.com>
Date: Tue, 10 Jan 2017 17:08:44 +0100

   Another 2 cents. I usually do a local backup with obnam and then sync
   the repo up to the remote server.
   :)
   
   
   On Tue, Jan 10, 2017 at 4:36 PM, Johannes Frölich
   <johannes.froelich@gmail.com> wrote:
   > That is actually pretty much what i did ;)
   > I am Backupping an owncloud instance - so the thing is that there are some
   > configuration folders (which i first backed up to see wether i can handle
   > obnam (like recover data and so on)) and one huge folder (almost the full
   > 170GB) user data. so i added this folder then too. Maybe i should have
   > started with completely different data to see how long it takes, but anyway
   > at one point i would have done this anyway… so ill just wait… something will
   > happen ^^
   >
   > Cheers and thanks!
   >
   >
   >
   > Am 10.01.2017 um 16:29 schrieb SanskritFritz <sanskritfritz@gmail.com>:
   >
   > My 2 cents:
   > I usually start any backup with a small set and gradually build it up
   > to the whole amount I actually want to backup. Takes some time and
   > fiddling but the gradual process also helps discovering unnecessary
   > parts in the backup which eventually land in the exclude file.
   >
   >
   >
   >
   >
   > On Tue, Jan 10, 2017 at 4:25 PM, Johannes Frölich
   > <johannes.froelich@gmail.com> wrote:
   >
   > I mean as far as i understand the way obnam works it will do that for the
   > initial big backup.
   > Future small changes will then not take that long, so ill give it some days
   > to do whatever it is doing now ;)
   >
   > Thank you so much for your help!!
   >
   > Cheers
   >
   >
   >
   > Am 10.01.2017 um 16:22 schrieb SanskritFritz <sanskritfritz@gmail.com>:
   >
   > On Tue, Jan 10, 2017 at 4:08 PM, Lars Wirzenius <liw@liw.fi> wrote:
   >
   > If you don't want to wait, you can use control-c to interrupt it. By
   > the time this happening, Obnam has already finish the actual backup,
   > and interrupting should be quite safe.
   >
   >
   > Which will leave lots of unnecessary generations behind I might add.
   > But those can be removed later with --forget.
   >
   >
   >
   > _______________________________________________
   > 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
   >
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: Johannes Frölich <johannes.froelich@gmail.com>
Date: Tue, 10 Jan 2017 17:49:57 +0100

   Thats a good idea, but i guess i don’t have the space for that…
   + the network not seems to be the bottleneck since the CPU is at 100%…(?) so it wouldnt be faster anyways.
   
   Cheers
   
   
   > Am 10.01.2017 um 17:08 schrieb SanskritFritz <sanskritfritz@gmail.com>:
   > 
   > Another 2 cents. I usually do a local backup with obnam and then sync
   > the repo up to the remote server.
   > :)
   > 
   > 
   > On Tue, Jan 10, 2017 at 4:36 PM, Johannes Frölich
   > <johannes.froelich@gmail.com> wrote:
   >> That is actually pretty much what i did ;)
   >> I am Backupping an owncloud instance - so the thing is that there are some
   >> configuration folders (which i first backed up to see wether i can handle
   >> obnam (like recover data and so on)) and one huge folder (almost the full
   >> 170GB) user data. so i added this folder then too. Maybe i should have
   >> started with completely different data to see how long it takes, but anyway
   >> at one point i would have done this anyway… so ill just wait… something will
   >> happen ^^
   >> 
   >> Cheers and thanks!
   >> 
   >> 
   >> 
   >> Am 10.01.2017 um 16:29 schrieb SanskritFritz <sanskritfritz@gmail.com>:
   >> 
   >> My 2 cents:
   >> I usually start any backup with a small set and gradually build it up
   >> to the whole amount I actually want to backup. Takes some time and
   >> fiddling but the gradual process also helps discovering unnecessary
   >> parts in the backup which eventually land in the exclude file.
   >> 
   >> 
   >> 
   >> 
   >> 
   >> On Tue, Jan 10, 2017 at 4:25 PM, Johannes Frölich
   >> <johannes.froelich@gmail.com> wrote:
   >> 
   >> I mean as far as i understand the way obnam works it will do that for the
   >> initial big backup.
   >> Future small changes will then not take that long, so ill give it some days
   >> to do whatever it is doing now ;)
   >> 
   >> Thank you so much for your help!!
   >> 
   >> Cheers
   >> 
   >> 
   >> 
   >> Am 10.01.2017 um 16:22 schrieb SanskritFritz <sanskritfritz@gmail.com>:
   >> 
   >> On Tue, Jan 10, 2017 at 4:08 PM, Lars Wirzenius <liw@liw.fi> wrote:
   >> 
   >> If you don't want to wait, you can use control-c to interrupt it. By
   >> the time this happening, Obnam has already finish the actual backup,
   >> and interrupting should be quite safe.
   >> 
   >> 
   >> Which will leave lots of unnecessary generations behind I might add.
   >> But those can be removed later with --forget.
   >> 
   >> 
   >> 
   >> _______________________________________________
   >> 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
   >>