Hi guys!
i've got 2.4.2p2 running great on multiple linux boxes . . no problem.
just got a NAS in and need to set it up for backup.
1. i created a user on the NAS and granted it rights as needed to
backup.
2. created a share specifically for backup and set correct rights (read
only . i don't mi
ahh . . rtfm . . thanks!
Anthony
"John R. Jackson" wrote:
> >4. i have an entry in disklist as such:
> >
> >nas-1 //nas-1/back samba-comp-tar
>
> That's probably not right. The hostname (first field) should be the
> machine that will run smbclient. It looks to me like you've pointed it
> at
>4. i have an entry in disklist as such:
>
>nas-1 //nas-1/back samba-comp-tar
That's probably not right. The hostname (first field) should be the
machine that will run smbclient. It looks to me like you've pointed it
at the PC (or whatever a "NAS" is).
>Anthony
John R. Jackson, Technical Soft
hey anthony,
i had the same problem too.. found the answer at:
http://groups.yahoo.com/group/amanda-users/message/9211
-edwin
-Original Message-
From: Anthony Hardy [mailto:[EMAIL PROTECTED]]
Sent: Monday, July 16, 2001 11:37 AM
To: [EMAIL PROTECTED]
Subject: Samba problem.
Hi guys
We have had amanda and Samba working for about a year now. Mysteriously
a couple of weeks ago, the Samba (and local drive) backups stopped
working. I can SMBOUNT the shares fine from the amanda server, but the
backups fail. The error from the nightly report is:
newbackup. //NETALERT/E$ lev
I'm configuring amanda for the first time and it's almost working. I'm
getting a failure from amcheck on one of the two Samba shares I have set
up in my disklist. The only real difference I can see in the setup is
that the password (in /etc/amandapass) for the one that fails contains a
# char
Hi,
such efects have shown up in the past for samba-shares where (AFAIR)
the estimation phase took longer then the normal timeouts in amanda
would allow. I guess at the time amanda stoped working, the E$ share
has grown over the triger line for this problem.
There was a solution a few weeks/month
On Tue, Aug 12, 2003 at 05:54:43PM -0400, Archie Warnock wrote:
>
> ... . The entries in /etc/amandapass look
> like this (obviously scrambled to protect real passwords):
>
> //pommard/MyDocuments me%foo#bar
> //maranges/PrisDocs metoo%foobar
>
> Note that this command works fine:
>
> smbclie
Jon LaBadie wrote:
That appears to terminate at the octothorpe (formal name for #).
Thus your password would not be foo#bar but foo.
If I understand it correctly, this is a limitation in the "amanda-valid"
passwords and is not correctable by quoting etc.
Just to finish the thread, I managed to fine
On Wed, Aug 13, 2003 at 12:11:03PM -0400, Archie Warnock wrote:
> Jon LaBadie wrote:
> >That appears to terminate at the octothorpe (formal name for #).
> >Thus your password would not be foo#bar but foo.
> >
> >If I understand it correctly, this is a limitation in the "amanda-valid"
> >passwords a
Jon LaBadie wrote:
If I understand it correctly, this is a limitation in the "amanda-valid"
passwords and is not correctable by quoting etc.
Ugh... OK - thanks.
--
Archie
-- Archie Warnock Internet: [EMAIL PROTECTED]
-- A/WWW Enterpriseshttp://www.awcubed
11 matches
Mail list logo
