Amanda-Users

Re: Amanda backup of Read-Only NFS shares

2005-06-01 14:20:38
Subject: Re: Amanda backup of Read-Only NFS shares
From: Frank Smith <fsmith AT hoovers DOT com>
To: Mark Hennessy <mark AT cloud9 DOT net>, amanda-users AT amanda DOT org
Date: Wed, 01 Jun 2005 13:00:55 -0500
--On Wednesday, June 01, 2005 13:26:22 -0400 Mark Hennessy <mark AT cloud9 DOT 
net> wrote:

> It looks like tar is outputting the offending error notice, and the lines I 
> provided in my original e-mail came back in the STRANGE summary for that 
> particular mount.  I will try 'record no' and see what happens.

I would like to retract my suggestion on 'record no', I replied to your 
question without
reading it carefully and thinking it through. The 'record no' will only help if 
you are
writing your amandates file onto the mounted filesystem.  Usually it would go 
in /etc
or somewhere similar, and not directly on the NFS mount.  I overlooked the fact
that you were getting stat permission errors and not write permission errors, so
Amanda is having problems reading the files, not writing something.
    I now believe you are having a root squash issue (where root on the NFS 
client
is mapped to nobody on the NFS server.

Frank

> 
> Thanks to both of you!
> 
> --
>   Mark P. Hennessy
>   mark AT cloud9 DOT net
> 
> --On Wednesday, June 01, 2005 16:49:12 +0200 Peter Mueller <peter.mueller.ls 
> AT elimpex DOT com> wrote:
> 
>> Hi Mark!
>> 
>> 
>>> I have a read-only NFS share provided by a Windows 2000 server machine
>>> and I want to back it up with my AMANDA cycle.  I keep getting these
>>> errors though:
>>> 
>>> ...
>>> ? gtar: ./foo/bar: Warning: Cannot stat: Permission denied
>>> ? gtar: ./foo/baz: Warning: Cannot stat: Permission denied
>>> ...
>>> 
>>> Is there anything I can do to effectively back up these files without
>>> getting these warnings, a tar parameter perhaps (I couldn't find on in
>>> the man page for tar)? Setting the NFS share to be read-write isn't an
>>> option.
>> 
>> As you allready wrote, its read-only so tar cant set inode dates etc.
>> So you wont be able to do propper incremental backups.
>> You could baybe do full backups every amanda run, but as I dont use
>> this, I am not aware who to propper configure this.
> 
> You can set 'record no' in your duptype so amanda won't try to update
> dumpdates, but as you note that limits you to full backups on every run.
> 
> Frank
>> 
>> 
>> Bye, Peter
>> WOTLmade

-- 
Frank Smith                                      fsmith AT hoovers DOT com
Sr. Systems Administrator                       Voice: 512-374-4673
Hoover's Online                                   Fax: 512-374-4501


<Prev in Thread] Current Thread [Next in Thread>