Re: [Duplicity-talk] When restoring files on different server: Error '[Errno 1] Operation not permitted:

[Sauli Heinola]

On 10/03/13 at 14:19, address@hidden wrote:
> On 09.03.2013 07:31, Rodrigo Campos wrote:
> > On Fri, Mar 08, 2013 at 04:06:16PM -0300, Mikko Ohtamaa wrote:
> >> I am testing restoring individual backuped files on non-orignal server
> >> using Duply / Duplicity. This is the command I run to restore a SQL
> >> dump file:
> >>
> >> TMPDIR='/tmp' duplicity --name 'duply_fullbackup' --no-encryption
> >> --verbosity '4' --num-retries 15 --full-if-older-than 1M --volsize 250
> >> --exclude=**.log --exclude=**.fs.old --include=/etc --include=/home
> >> --include=/root --include=/srv --include=/var/www --include=/boot
> >> --exclude=/** --restore-time now --file-to-restore
> >> root/db_backups/opensourcehacker.sql ssh://yyy/duply/xxx
> >> opensourcehacker.sql
> >>
> >> I'll get the following error during the restore:
> >>
> >> Last full backup date: Fri Feb  8 09:11:30 2013
> >> Error '[Errno 1] Operation not permitted: 'opensourcehacker.sql'' 
> >> processing .
> >> --- Finished state OK at 19:53:40.875 - Runtime 00:05:22.773 ---
> >>
> >> Apparently the file was still restored correctly. I assume this has
> >> something to do with the fact that the server where the restoration is
> >> different and does not have the same users as the orignal server and I
> >> am not running as s root.
> >>
> >> This error is harmless?
> > 
> > Probably (if I'm not wrong)
> > 
> > This error happens to me when, for example, I backup a file owned by root 
> > and
> > try to restore it on some other server using a non-priv user. The file is
> > restored okay, but then the user can't change the owner of the file to root 
> > and
> > the error is thrown.
> > 
> > I suspect is that because I have tried restoring it as root then, the error 
> > was
> > not thrown and the file owner was set to root. Although I have not looked 
> > at the
> > code to see this.
> > 
> 
> without looking at it more detailed and from memory:
> 
> i agree. duplicity automatically tries to restore file attributes 
> (perms,ownership) _after_ restoration and can spit out these messages if it 
> fails to do so.
> generally harmless, but should probably be replaced with a more user friendly 
> warning.
> 
> ..ede/duply.net
> 
> 
> _______________________________________________
> Duplicity-talk mailing list
> address@hidden
> https://lists.nongnu.org/mailman/listinfo/duplicity-talk

-- 
"What a horrible night to have a curse."