Front page

restoring backup recreates on top of destination folder all folder structure from root

05b6851e79f74950b5ca44fb81c15f68
ADULT POTATO MUSIC

From: Marcello Magaldi <magowiz@gmail.com>
Date: Mon, 30 May 2016 15:34:56 +0200

   Hi,
   I'm trying obnam to perform such test backups before putting it in 
   production to perform backups on regular basis : anyway I have an issue 
   with restore path.
   
   The backup is performed by host 1 to a repository hosted in host 2 :
   ~/.obnam.conf on host1 :
   [config]
   repository = sftp://host2/home/user/backup/
   log = /home/user/obnam.log
   
   The data I want to backup are in user's home directory, in a 
   subdirectory named data : /home/user/data
   It contains some random data file generated by dd .
   
   The backup is created and kept up to date with :
   obnam --client-name=t1 backup data
   
   Then I tried to erase data on /home/user/data to restore them using :
     obnam restore --to=data --client-name=t1
   
   The problem is that obnam creates this folder structure inside data folder:
   /home/user/data/home/user/data/
   and files are stored into that folder instead of the original position:
   /home/user/data/
   
   If I replace the --to=data with --to=/home/user/data/ nothing changes, 
   if I change it with --to=/ it tells me that / folder is not empty and 
   obnam exits.
   
   Do I miss something ? Do I need to specify further arguments or 
   configuration parameters? I know I can automatically move folder content 
   to right place and then remove directories,
   but it should be better if obnam will permit me to obtain directly what 
   I'm looking for.
   
   Best Regards
   Marcello Magaldi
   
   
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: Marcello Magaldi <magowiz@gmail.com>
Date: Mon, 30 May 2016 18:01:15 +0200

   Thank you very much for your explanation and your software, so the right
   way for me is to mount read-only with fuse and simply use cp command.
   Thanks
   Marcello
   
   2016-05-30 17:24 GMT+02:00 Lars Wirzenius <liw@liw.fi>:
   
   > On Mon, May 30, 2016 at 03:34:56PM +0200, Marcello Magaldi wrote:
   > > Do I miss something ? Do I need to specify further arguments or
   > > configuration parameters? I know I can automatically move folder content
   > to
   > > right place and then remove directories,
   > > but it should be better if obnam will permit me to obtain directly what
   > I'm
   > > looking for.
   >
   > It's working as intended, even if it sometimes confuses people a bit.
   >
   > You can achieve what you want by using "obnam mount" and then your
   > favourite file copying tools to copy what you want to where you want
   > them. This avoids having to stuff all the vast functionality and
   > special cases that people want from file copying tools into obnam
   > restore.
   >
   > --
   > Schrödinger's backup hypothesis: the condition of any backup is
   > undefined until a restore is attempted. -- andrewsh
   >
From: Lars Wirzenius <liw@liw.fi>
Date: Mon, 30 May 2016 18:24:43 +0300

   On Mon, May 30, 2016 at 03:34:56PM +0200, Marcello Magaldi wrote:
   > Do I miss something ? Do I need to specify further arguments or
   > configuration parameters? I know I can automatically move folder content to
   > right place and then remove directories,
   > but it should be better if obnam will permit me to obtain directly what I'm
   > looking for.
   
   It's working as intended, even if it sometimes confuses people a bit.
   
   You can achieve what you want by using "obnam mount" and then your
   favourite file copying tools to copy what you want to where you want
   them. This avoids having to stuff all the vast functionality and
   special cases that people want from file copying tools into obnam
   restore.