RE: Windows domains...

2006-09-05 Thread John Clement
Thanks Gordon, its always the simple things isn't it Domain admin
oh, that might helpps.

Cheers for the help!

jc 

> -Original Message-
> From: Gordon J. Mills III [mailto:[EMAIL PROTECTED] 
> Sent: 30 August 2006 19:02
> To: John Clement; amanda-users@amanda.org
> Subject: RE: Windows domains...
> 
> I am using a domain user with success. However, my amandapass 
> entries look like your #2 entry below. Basically:
> 
> //servername/d$ user%password NETBIOSDOMAINNAME
> 
> I'm not sure what to tell you to try, but I wanted to let you 
> know I have it working. :-) Is the domain user a Domain Admin?
> 
> 
> Regards,
> Gordon
> 
> -Original Message-
> From: [EMAIL PROTECTED] 
> [mailto:[EMAIL PROTECTED]
> On Behalf Of John Clement
> Sent: Wednesday, August 30, 2006 11:16 AM
> To: amanda-users@amanda.org
> Subject: Windows domains...
> 
> We've recently been 'upgraded' to a Windows domain, part of 
> this upgrade appears to have involved removing the local 
> amanda account from each Windows server.  Is there any way of 
> getting amanda to auth using domain logon?
> 
> I've tried the following varients in amandapass (with the 
> resulting error from amcheck below, oh and yes that account 
> does exist on the domain and has the password set) but no 
> joy, any suggestions welcome!
> Thanks,
> 
> jc
> 
> 
> //server.domain.local/c$ amanda%password domain.local
> -- Domain=[READINGROOM] OS=[Windows 5.0] Server=[Windows 2000 LAN
> Manager]: tree connect failed: NT_STATUS_ACCESS_DENIED: returned 1]
> 
> //server.domain.local/c$ amanda%password domain
> -- Domain=[READINGROOM] OS=[Windows 5.0] Server=[Windows 2000 LAN
> Manager]: tree connect failed: NT_STATUS_ACCESS_DENIED: returned 1]
> 
> //server.domain.local/c$ [EMAIL PROTECTED]
> -- session setup failed: NT_STATUS_LOGON_FAILURE: returned 1]
> 
> //server.domain.local/c$ [EMAIL PROTECTED]
> -- session setup failed: NT_STATUS_LOGON_FAILURE: returned 1]
> 
> 
> 
> 



Windows domains...

2006-08-30 Thread John Clement
We've recently been 'upgraded' to a Windows domain, part of this upgrade
appears to have involved removing the local amanda account from each
Windows server.  Is there any way of getting amanda to auth using domain
logon?

I've tried the following varients in amandapass (with the resulting
error from amcheck below, oh and yes that account does exist on the
domain and has the password set) but no joy, any suggestions welcome!
Thanks,

jc


//server.domain.local/c$ amanda%password domain.local
-- Domain=[READINGROOM] OS=[Windows 5.0] Server=[Windows 2000 LAN
Manager]: tree connect failed: NT_STATUS_ACCESS_DENIED: returned 1]

//server.domain.local/c$ amanda%password domain
-- Domain=[READINGROOM] OS=[Windows 5.0] Server=[Windows 2000 LAN
Manager]: tree connect failed: NT_STATUS_ACCESS_DENIED: returned 1]

//server.domain.local/c$ [EMAIL PROTECTED]
-- session setup failed: NT_STATUS_LOGON_FAILURE: returned 1]

//server.domain.local/c$ [EMAIL PROTECTED]
-- session setup failed: NT_STATUS_LOGON_FAILURE: returned 1]



RE: Restoring windows partition written using smbclient

2006-06-09 Thread John Clement
Another one for you maybe?

Although I think this one might just be a case of it not going to work
like this and needing to change it...

DLE:
autonomy.deanst.rroom.net   /mnt_f/Websites
comp-root-tar-win

>From amanda.conf
define dumptype comp-root-tar-win {
root-tar
comment "Root partitions with compression"
compress client fast
index
#exclude list "/var/lib/amanda/exclusions.txt"
}

So I'm doing this (and version of it):

# /usr/sbin/amrestore -p /dev/nst0 autonomy.deanst.rroom.net
'/mnt_f/Websites'  | gtar --numeric-owner -xpvf -

And get

gzip: stdin: not in gzip format
Error 32 (Broken pipe) offset 32768+32768, wrote 0
amrestore: pipe reader has quit in middle of file.

Any ideas?

Thanks in advance!! - jc

> -Original Message-
> From: Paul Bijnens [mailto:[EMAIL PROTECTED] 
> Sent: 07 June 2006 14:40
> To: John Clement
> Cc: amanda-users@amanda.org
> Subject: Re: Restoring windows partition written using smbclient
> 
> On 2006-06-07 15:23, John Clement wrote:
> > I'm trying to restore the contents of
> > 
> > AMANDA: FILE 20060601 orinoco.deanst.rroom.net 
> > //tlswindev1.deanst.rroom.net/e$ lev 0 comp .gz program 
> > /usr/bin/smbclient
> > 
> > However I don't know how to get this off the tape into a 
> usable format.
> 
> The first 32K block of the file on tape contains the instructions.
> 
> Have you read:
> 
> http://wiki.zmanda.com/index.php/Restoring_files
> 
> Especially the secion about restoring with "amrestore".
> The windows tar is compatible with gnutar, so to restore on 
> the server itself, just use gnutar.
> 
> 
> 
> 
> > It was generated from the DLE
> > 
> > orinoco.deanst.rroom.net//tlswindev1.deanst.rroom.net/e$
> > comp-root-tar-win
> > 
> > And from amanda.conf
> > 
> > define dumptype comp-root-tar-win {
> > root-tar
> > comment "Root partitions with compression"
> > compress client fast
> > index
> > #exclude list "/var/lib/amanda/exclusions.txt"
> > }
> > 
> > I need to restore it to the amanda server as I'm still trying to 
> > reinstall 'tlswindev1' after its only disk (yes, I know, when its 
> > replaced I'll be insisting on RAID) died last night, and I can't 
> > afford the network traffic (the dump to tape should be about 30GB).
> 
> Something like this should work (untested):
> 
> # cd /space/tmp  # somewhere with enough free diskspace
> # mt -t /dev/st0 rewind  # fill in your tape device
> # amrestore -p /dev/nst0 orinoco.deanst.rroom.net 
> '//tlswindev1.deanst.rroom.net/e\$'  | gtar --numeric-owner -xpvf -
> 
> 
> 
> -- 
> Paul Bijnens, xplanation Technology ServicesTel  +32 
> 16 397.511
> Technologielaan 21 bus 2, B-3001 Leuven, BELGIUMFax  +32 
> 16 397.512
> http://www.xplanation.com/  email:  
> [EMAIL PROTECTED]
> **
> *
> * I think I've got the hang of it now:  exit, ^D, ^C, ^\, ^Z, 
> ^Q, ^^, *
> * F6, quit, ZZ, :q, :q!, M-Z, ^X^C, logoff, logout, close, 
> bye, /bye, *
> * stop, end, F3, ~., ^]c, +++ ATH, disconnect, halt,  abort,  
> hangup, *
> * PF4, F20, ^X^X, :D::D, KJOB, F14-f-e, F8-e,  kill -1 $$,  
> shutdown, *
> * init 0, kill -9 1, Alt-F4, Ctrl-Alt-Del, AltGr-NumLock, 
> Stop-A, ... *
> * ...  "Are you sure?"  ...   YES   ...   Phew ...   I'm out  
> *
> **
> *
> 
> 



RE: Restoring windows partition written using smbclient

2006-06-07 Thread John Clement
Thanks Paul!!! That worked a treat. 

> -Original Message-
> From: Paul Bijnens [mailto:[EMAIL PROTECTED] 
> Sent: 07 June 2006 14:40
> To: John Clement
> Cc: amanda-users@amanda.org
> Subject: Re: Restoring windows partition written using smbclient
> 
> On 2006-06-07 15:23, John Clement wrote:
> > I'm trying to restore the contents of
> > 
> > AMANDA: FILE 20060601 orinoco.deanst.rroom.net 
> > //tlswindev1.deanst.rroom.net/e$ lev 0 comp .gz program 
> > /usr/bin/smbclient
> > 
> > However I don't know how to get this off the tape into a 
> usable format.
> 
> The first 32K block of the file on tape contains the instructions.
> 
> Have you read:
> 
> http://wiki.zmanda.com/index.php/Restoring_files
> 
> Especially the secion about restoring with "amrestore".
> The windows tar is compatible with gnutar, so to restore on 
> the server itself, just use gnutar.
> 
> 
> 
> 
> > It was generated from the DLE
> > 
> > orinoco.deanst.rroom.net//tlswindev1.deanst.rroom.net/e$
> > comp-root-tar-win
> > 
> > And from amanda.conf
> > 
> > define dumptype comp-root-tar-win {
> > root-tar
> > comment "Root partitions with compression"
> > compress client fast
> > index
> > #exclude list "/var/lib/amanda/exclusions.txt"
> > }
> > 
> > I need to restore it to the amanda server as I'm still trying to 
> > reinstall 'tlswindev1' after its only disk (yes, I know, when its 
> > replaced I'll be insisting on RAID) died last night, and I can't 
> > afford the network traffic (the dump to tape should be about 30GB).
> 
> Something like this should work (untested):
> 
> # cd /space/tmp  # somewhere with enough free diskspace
> # mt -t /dev/st0 rewind  # fill in your tape device
> # amrestore -p /dev/nst0 orinoco.deanst.rroom.net 
> '//tlswindev1.deanst.rroom.net/e\$'  | gtar --numeric-owner -xpvf -
> 
> 
> 
> -- 
> Paul Bijnens, xplanation Technology ServicesTel  +32 
> 16 397.511
> Technologielaan 21 bus 2, B-3001 Leuven, BELGIUMFax  +32 
> 16 397.512
> http://www.xplanation.com/  email:  
> [EMAIL PROTECTED]
> **
> *
> * I think I've got the hang of it now:  exit, ^D, ^C, ^\, ^Z, 
> ^Q, ^^, *
> * F6, quit, ZZ, :q, :q!, M-Z, ^X^C, logoff, logout, close, 
> bye, /bye, *
> * stop, end, F3, ~., ^]c, +++ ATH, disconnect, halt,  abort,  
> hangup, *
> * PF4, F20, ^X^X, :D::D, KJOB, F14-f-e, F8-e,  kill -1 $$,  
> shutdown, *
> * init 0, kill -9 1, Alt-F4, Ctrl-Alt-Del, AltGr-NumLock, 
> Stop-A, ... *
> * ...  "Are you sure?"  ...   YES   ...   Phew ...   I'm out  
> *
> **
> *
> 
> 



Restoring windows partition written using smbclient

2006-06-07 Thread John Clement
I'm trying to restore the contents of

AMANDA: FILE 20060601 orinoco.deanst.rroom.net
//tlswindev1.deanst.rroom.net/e$ lev 0 comp .gz program
/usr/bin/smbclient

However I don't know how to get this off the tape into a usable format.
It was generated from the DLE

orinoco.deanst.rroom.net//tlswindev1.deanst.rroom.net/e$
comp-root-tar-win

And from amanda.conf

define dumptype comp-root-tar-win {
root-tar
comment "Root partitions with compression"
compress client fast
index
#exclude list "/var/lib/amanda/exclusions.txt"
}

I need to restore it to the amanda server as I'm still trying to
reinstall 'tlswindev1' after its only disk (yes, I know, when its
replaced I'll be insisting on RAID) died last night, and I can't afford
the network traffic (the dump to tape should be about 30GB).

Any suggestions much appreciated!

Thanks, John



RE: Amanda with cygwin on windows...

2006-05-24 Thread John Clement
Thanks for that... Which category is m4 in?

 - john 

> -Original Message-
> From: [EMAIL PROTECTED] 
> [mailto:[EMAIL PROTECTED] On Behalf Of rom
> Sent: 24 May 2006 14:20
> To: John Clement; amanda-users@amanda.org
> Subject: Re: Amanda with cygwin on windows...
> 
> John Clement wrote:
> > I've just started following the isntructions on the site to 
> get this 
> > working, but it suggests I should be installing ALL of the stuff in 
> > devel.  This seems rather a lot, is this really the case or just 
> > slightly old documentation and there is now a shorter list 
> of stuff I 
> > need to install?
> 
> For cygwin 1.5.19-4 the following list was sufficient:
> cygwin defaults
> gcc
> inetutils
> m4
> make
> more (if you want to use amrecover)
> readline with source
> 
> 
> Regards,
> 
> Robert
> 



Amanda with cygwin on windows...

2006-05-24 Thread John Clement
I've just started following the isntructions on the site to get this
working, but it suggests I should be installing ALL of the stuff in
devel.  This seems rather a lot, is this really the case or just
slightly old documentation and there is now a shorter list of stuff I
need to install?

Thanks as always,

John



RE: Windows clients

2006-05-22 Thread John Clement
> -Original Message-
> From: Olivier Nicole [mailto:[EMAIL PROTECTED] 
> Sent: 22 May 2006 04:37
> To: John Clement
> Cc: amanda-users@amanda.org
> Subject: Re: Windows clients
> 
> > autonomy.deanst.rroom.net /mnt_c/Autonomy comp-root-tar-win
> 
> > define dumptype comp-root-tar-win {
> >root-tar
> >comment "Root partitions with compression"
> >compress client fast
> 
> You are using a client specific for Windows, and you are 
> doing the compression on the client, that is on windows, 
> using windows software.
> 
> On the other hand:
> 
> > amrestore /dev/nst0 autonomy.deanst.rroom.net '/mnt_c/Autonomy$'
> 
> You are restoring on your server, doing the uncompress on 
> your server, on Unix. Apparently the compress software on 
> Windows is incompatible with the uncompress software on Unix...
> 
> You'd need to extract the data from the tape and then find 
> the proper uncompress client to use on Unix or push the file 
> to your Windows client and uncompress there.

OK, thanks for that, it makes sense!  And thanks to Jon for the dd
suggestions etc...

I've now dd'ed off the header of that back up and got:

AMANDA: FILE 20060519 autonomy.deanst.rroom.net /mnt_f/Websites lev 0
comp .gz program nttar
To restore, position tape at start of file and run:
  dd if= bs=32k skip=1 | /usr/bin/gzip -dc | ttar -f... -

Which confirms what you're saying.  I had a quick google for nttar and
the first hit was to a Win 32 client project on SourceForge from back in
2001!  So it looks like there is some arcane backup client on this
windows server.  Might be a good time to upgrade to something more
current!

Any suggestions? - I know its poossible through samba, cygwin etc, but
in people's experience, what's the best way of backing up Windows?

Thanks,

jc

> best regards,
> 
> Olivier
> 



Windows clients

2006-05-19 Thread John Clement
Having been reading the documentation (chapter 6 (Restoring) of the
official docs inparticular) I've got restores working for the Linux
hosts ok, deciding that restoring on the server then moving the restored
file to the client for extracting being the favoured method.  However
I've now started trying to do the same on some Windows hosts and its not
playing ball.

There's no Cygwin on the client, nor is it using samba (DLE below)

autonomy.deanst.rroom.net   /mnt_c/Autonomy
comp-root-tar-win

And the dump type

define dumptype comp-root-tar-win {
root-tar
comment "Root partitions with compression"
compress client fast
index
}

As far as I can see there is some sort of amanda client installed on the
windows machine, that lives in c:\usr\amanda

Listing of that dir (if its any use to anyone):

C:\usr\amanda>dir
 Volume in drive C is SYSTEM
 Volume Serial Number is 54A9-A4D6

 Directory of C:\usr\amanda

12/04/2006  12:44  .
12/04/2006  12:44  ..
03/03/2006  13:2524,064 amanda_svc.exe
12/04/2006  12:44  etc
12/04/2006  12:44   925 install-service.cmd
12/04/2006  12:44  libexec
   2 File(s) 24,989 bytes
   4 Dir(s)   3,028,369,408 bytes free

To restore it I'm using 

amrestore /dev/nst0 autonomy.deanst.rroom.net '/mnt_c/Autonomy$'

Which returns

amrestore:  13: restoring
autonomy.deanst.rroom.net._mnt__c_Autonomy.20060518.1

gzip: stdin: not in gzip format
Error 32 (Broken pipe) offset 32768+32768, wrote 0
amrestore: pipe reader has quit in middle of file.


So, does all this make sense to some one out there, or seeing as I don't
know how this client was installed or from what, maybe someone can
suggest a better way of getting amanda to back this machine up?  There
are quite a few hosts being backed up with samba too, but I'd like to
get away from samba if possible to reduce all those 'strange' errors in
the backup reports.

As always, any help gratefully received!!

Thanks, jc



Runspercycle?

2006-05-18 Thread John Clement
Hi list,

I've got a no brainer for you, what is runspercycle?  I've rtfmed but
the explanation just dones't make sense to me.

At the moment I've got

Dumpcycle 4
Runspercycle 1
Tapecycle 10

Its set up so it runs every Mon-Thurs night and we have two weeks worth.
I've noticed that it appears to be doing level 0 on everything every
night, pressumably because it's a 400GB tape and the total data that's
backed up at the moment is considerably less.  Is there any way of
forcing amanda to only do the level 0 once and grab incrementals the
rest of the time, I thought I'd set it up like this, but something is
obviously wrong somewhere...

Thanks, as always!

john 



RE: Backing up sub directories and interactive restores

2006-05-12 Thread John Clement
> -Original Message-
> From: [EMAIL PROTECTED] 
> [mailto:[EMAIL PROTECTED] On Behalf Of Jon LaBadie
> Sent: 11 May 2006 17:21
> To: amanda-users@amanda.org
> Subject: Re: Backing up sub directories and interactive restores
> 
> On Thu, May 11, 2006 at 02:32:41PM +0100, John Clement wrote:
> > >From what I understand amrecover runs from the client machine, and 
> > >I'd
> > rather run the restores on the server, then move what I 
> have to back 
> > to the client manually.
> > 
> > Moving on from this a little though, I've used an existing dumptype 
> > (from before I started here) and if I try to restore anything I get 
> > the following message:
> > 
> > ===
> > % /usr/sbin/amrestore -p /dev/nst0 autonomy.deanst.rroom.net 
> > /mnt_f/Websites | tar -xvf -
> > 
> > gzip: stdin: not in gzip format
> > Error 32 (Broken pipe) offset 32768+32768, wrote 0
> > amrestore: pipe reader has quit in middle of file. 
> > ===
> > 
> > The DLE:
> > autonomy.deanst.rroom.net   /mnt_f/Websites
> > comp-root-tar-win
> > 
> > And the dump type:
> > define dumptype comp-root-tar-win {
> > root-tar
> > comment "Root partitions with compression"
> > compress client fast
> > index
> > }
> > 
> > Thanks,
> > 
> > jc
> > 
> > 
> > > -Original Message-
> > > From: [EMAIL PROTECTED] 
> > > [mailto:[EMAIL PROTECTED] On Behalf Of Jon LaBadie
> > > Sent: 04 May 2006 15:05
> > > To: amanda-users@amanda.org
> > > Subject: Re: Backing up sub directories and interactive restores
> > > 
> > > On Thu, May 04, 2006 at 11:13:20AM +0100, John Clement wrote:
> > > > I've previously seen Amanda installed in such a way that
> > > you could run
> > > > something like
> > > > 
> > > > amrestore -p /dev/nst0 host /filesystem | restore ivf -
> > > > 
> > > > Which gives a basic shell on the tape so you can restore 
> > > > individual items.
> > > 
> > > Is there a reason you are unable to use amrecover?
> > > 
> 
> I presume the comment at the top was in response to this question.
> Top posting makes following a discussing so difficult.
> 
> Use of amrecover is not limited to the client.  It could be 
> run from the server or from a third-party client.  Where there 'might'
> be a limitation is the availability of the correct tools.  
> For example a backup made with ufsdump from a Solaris host 
> could not be recovered to a linux client because it lacks 
> ufsrestore.  But to another Solaris client it should be fine. 
>  Or if both used guntar it should be fine.
> 

Ahh, I may be starting to see the light (I hope).  The client is W2k3
server.  This means then that I need to use amrecover on that server to
restore from the tape? - rather than trying to use Linux tools on the
server to restore a Windows directory... 

> Just clutching at straws, the error message says something 
> about an error at 32k+32k.  Might these dumps have been 
> created with a tape block size different than the standard 32k?
> 
> 
> -- 
> Jon H. LaBadie  [EMAIL PROTECTED]
>  JG Computing
>  4455 Province Line Road(609) 252-0159
>  Princeton, NJ  08540-4322  (609) 683-7220 (fax)
> 



RE: Backing up sub directories and interactive restores

2006-05-11 Thread John Clement
>From what I understand amrecover runs from the client machine, and I'd
rather run the restores on the server, then move what I have to back to
the client manually.

Moving on from this a little though, I've used an existing dumptype
(from before I started here) and if I try to restore anything I get the
following message:

===
% /usr/sbin/amrestore -p /dev/nst0 autonomy.deanst.rroom.net
/mnt_f/Websites | tar -xvf -

gzip: stdin: not in gzip format
Error 32 (Broken pipe) offset 32768+32768, wrote 0
amrestore: pipe reader has quit in middle of file. 
===

The DLE:
autonomy.deanst.rroom.net   /mnt_f/Websites
comp-root-tar-win

And the dump type:
define dumptype comp-root-tar-win {
root-tar
comment "Root partitions with compression"
compress client fast
index
}

Thanks,

jc


> -Original Message-
> From: [EMAIL PROTECTED] 
> [mailto:[EMAIL PROTECTED] On Behalf Of Jon LaBadie
> Sent: 04 May 2006 15:05
> To: amanda-users@amanda.org
> Subject: Re: Backing up sub directories and interactive restores
> 
> On Thu, May 04, 2006 at 11:13:20AM +0100, John Clement wrote:
> > I've previously seen Amanda installed in such a way that 
> you could run 
> > something like
> > 
> > amrestore -p /dev/nst0 host /filesystem | restore ivf -
> > 
> > Which gives a basic shell on the tape so you can restore individual 
> > items.
> 
> Is there a reason you are unable to use amrecover?
> 
> -- 
> Jon H. LaBadie  [EMAIL PROTECTED]
>  JG Computing
>  4455 Province Line Road(609) 252-0159
>  Princeton, NJ  08540-4322  (609) 683-7220 (fax)
> 



Backing up sub directories and interactive restores

2006-05-04 Thread John Clement
I've previously seen Amanda installed in such a way that you could run
something like

amrestore -p /dev/nst0 host /filesystem | restore ivf -

Which gives a basic shell on the tape so you can restore individual
items.  I understand that this was possible because comp-root backup had
been used on an entire filesystem, as I've tried on a sub-directory (as
is needed here) and it returns an error which google lead me to a post
on zmanda explaining comp-root can only be used on filesystems.

So, with the current set up its using comp-root-tar:

define dumptype comp-root-tar {
root-tar
comment "Root partitions with compression"
compress client fast
index
exclude list "/var/lib/amanda/exclusions.txt"
}

Is it possible to restore from this backup interactively or is it only
possible to untar the whole dump from this particular DLE, then take
what I want then discard the rest?

If its not possible to do it interactively can anyone suggest a way of
backing up a subdirectory on a filesystem then restore particular files
from that backup?

Many thanks,

john



RE: FreeBSD client

2006-05-04 Thread John Clement
> John Clement wrote:
> > Some of you might remember I'm piecing together a previous, 
> > non-working, installation of amanda.  The help I've 
> received off here 
> > has been great, so thanks again!  The next piece in this 
> puzzle is a 
> > FreeBSD (5.4) machine that appears to have amanda already installed.
> 
> John, let us know the/some background of your "mission".
> 
> Seems you're the one to keep the wheels reelin'
> ... after someone else "has left the building".
> 

Yes indeed, I am rather picking up the pieces.  The background to this
one is it seems every time a new sys ad starts they install their own
flavour of OS, so we've got various versions of RH, some BSD, Solaris,
Windows.  Most of the clients have been installed, and its now at the
point where they're nearly all working, except the FreeBSD one.

However, results are now needed so rather than getting the few remaining
BSD machines working too, I want to get something in place so we're
actually backing stuff up.  So, on to my next post and I'll be picking
this one up again soon.

Thanks for the help,


John


> Your puzzle is ours, as it seem ;-)
> 
> Regards, Stefan.
> 



FreeBSD client

2006-04-28 Thread John Clement




Some of you might 
remember I'm piecing together a previous, non-working, installation of 
amanda.  The help I've received off here has been great, so thanks 
again!  The next piece in this puzzle is a FreeBSD (5.4) machine that 
appears to have amanda already installed.
 
I can't find any 
documentation on getting the client working on BSD so started going by all the 
information I've gleened troubleshooting the Linux machines here.  I can't 
find a .amandahosts file, do I need to create this and if so where?  Or 
should this information go somewhere else?
 
I assume /tmp/amanda 
should exist on the machine and be writable and ownder by operator:operator 
(operator being the default username the client seems to install by, and 
operator being BSD's equiv of 'disk' group), is this so?
 
Thanks,
 
john


Re: selfcheck hanging

2006-04-27 Thread John Clement

Paul Bijnens wrote:

On 2006-04-27 13:05, John Clement wrote:


but then the above processes are, once again, present.

/tmp/amanda/selfcheck.[date].debug reveals

selfcheck: time 0.006: checking disk /data
selfcheck: time 0.010: device /data
selfcheck: time 0.010: disk "/data" OK
selfcheck: time 0.010: amdevice "/data" OK
selfcheck: time 0.010: device "/data" OK
selfcheck: time 0.011: checking disk /etc

so what could be causing the selfcheck to fail checking /etc... any 
ideas?



What is the dumpprogram used for /etc? Output of:

  $ amadmin config disklist hermes.deanst.rroom.net /etc

   host hermes.deanst.rroom.net:
   interface default
   disk /etc:
   program "GNUTAR"
   exclude list "/var/lib/amanda/exclusions.txt"
   priority 0
   dumpcycle 7
   maxdumps 1
   maxpromoteday 1
   strategy STANDARD
   compress CLIENT FAST
   comprate 0.50 0.50
   auth BSD
   kencrypt NO
   holdingdisk YES
   record YES
   index YES
   skip-incr NO
   skip-full NO



There is also a amandad.*.debug program with the "selfcheck" request.
Can you post that too?

[EMAIL PROTECTED] amanda]# more amandad.20060427114339000.debug
amandad: debug 1 pid 8755 ruid 33 euid 33: start at Thu Apr 27 11:43:39 2006
amandad: version 2.4.3
amandad: build: VERSION="Amanda-2.4.3"
amandad:BUILT_DATE="Thu Feb 13 11:14:37 EST 2003"
amandad:BUILT_MACH="Linux stripples.devel.redhat.com 
2.4.20-2.41smp #1 SMP Sun Feb 9 09:47:42 EST 2003 i686 i686 i

386 GNU/Linux"
amandad:CC="gcc"
amandad:CONFIGURE_COMMAND="'./configure' 
'--host=i386-redhat-linux' '--build=i386-redhat-linux' '--target=i386-red
hat-linux-gnu' '--program-prefix=' '--prefix=/usr' '--exec-prefix=/usr' 
'--bindir=/usr/bin' '--sbindir=/usr/sbin' '--sysco
nfdir=/etc' '--datadir=/usr/share' '--includedir=/usr/include' 
'--libdir=/usr/lib' '--libexecdir=/usr/lib/amanda' '--local
statedir=/var/lib' '--sharedstatedir=/usr/com' '--mandir=/usr/share/man' 
'--infodir=/usr/share/info' '--enable-shared' '--
with-index-server=localhost' 
'--with-gnutar-listdir=/var/lib/amanda/gnutar-lists' 
'--with-smbclient=/usr/bin/smbclient' '-
-with-amandahosts' '--with-user=amanda' '--with-group=disk' 
'--with-gnutar=/bin/tar'"

amandad: paths: bindir="/usr/bin" sbindir="/usr/sbin"
amandad:libexecdir="/usr/lib/amanda" mandir="/usr/share/man"
amandad:AMANDA_TMPDIR="/tmp/amanda" AMANDA_DBGDIR="/tmp/amanda"
amandad:CONFIG_DIR="/etc/amanda" DEV_PREFIX="/dev/"
amandad:RDEV_PREFIX="/dev/r" DUMP="/sbin/dump"
amandad:RESTORE="/sbin/restore" SAMBA_CLIENT="/usr/bin/smbclient"
amandad:GNUTAR="/bin/tar" COMPRESS_PATH="/usr/bin/gzip"
amandad:UNCOMPRESS_PATH="/usr/bin/gzip" MAILER="/usr/bin/Mail"
amandad:listed_incr_dir="/var/lib/amanda/gnutar-lists"
amandad: defs:  DEFAULT_SERVER="localhost" DEFAULT_CONFIG="DailySet1"
amandad:DEFAULT_TAPE_SERVER="localhost"
amandad:DEFAULT_TAPE_DEVICE="/dev/null" HAVE_MMAP HAVE_SYSVSHM
amandad:LOCKING=POSIX_FCNTL SETPGRP_VOID DEBUG_CODE
amandad:AMANDA_DEBUG_DAYS=4 BSD_SECURITY USE_AMANDAHOSTS
amandad:CLIENT_LOGIN="amanda" FORCE_USERID HAVE_GZIP
amandad:COMPRESS_SUFFIX=".gz" COMPRESS_FAST_OPT="--fast"
amandad:COMPRESS_BEST_OPT="--best" UNCOMPRESS_OPT="-dc"
amandad: time 0.001: got packet:

Amanda 2.4 REQ HANDLE 000-90F27009 SEQ 1146134665
SECURITY USER amanda
SERVICE selfcheck
OPTIONS features=feff9ffe0f;maxdumps=1;hostname=hermes.deanst.rroom.net;
GNUTAR /data  0 OPTIONS 
|;bsd-auth;compress-fast;index;exclude-list=/var/lib/amanda/exclusions.txt;
GNUTAR /etc  0 OPTIONS 
|;bsd-auth;compress-fast;index;exclude-list=/var/lib/amanda/exclusions.txt;



amandad: time 0.001: sending ack:

Amanda 2.4 ACK HANDLE 000-90F27009 SEQ 1146134665


amandad: time 0.002: bsd security: remote host orinoco.deanst.rroom.net 
user amanda local user amanda

amandad: time 0.002: amandahosts security check passed
amandad: time 0.002: running service "/usr/lib/amanda/selfcheck"
amandad: time 29.712: got packet:

Amanda 2.4 REQ HANDLE 000-90F27009 SEQ 1146134665
SECURITY USER amanda
SERVICE selfcheck
OPTIONS features=feff9ffe0f;maxdumps=1;hostname=hermes.deanst.rroom.net;
GNUTAR /data  0 OPTIONS 
|;bsd-auth;compress-fast;i

selfcheck hanging

2006-04-27 Thread John Clement
OK, another client that was already installed this time.  I've checked 
through the client's config, file ownership, xinetd config etc and it 
all appears to be right (based on my previous postings), it was 
installed as 'amanda' so this user is the same on the server and 
client.  When I ran amcheck the first time I received 'amandad busy', so 
checked on the client and found:


amanda8755  0.0  0.2  2192  748 ?S11:43   0:00 amandad
amanda8756  0.0  0.2  1948  748 ?S11:43   0:00 
/usr/lib/amanda/selfcheck
amanda8757  0.0  0.0 00 ?Z11:43   0:00 [amandad 
]


If I kill these processes it returns

WARNING: hermes.deanst.rroom.net: selfcheck reply timed out.

but then the above processes are, once again, present.

/tmp/amanda/selfcheck.[date].debug reveals

selfcheck: time 0.006: checking disk /data
selfcheck: time 0.010: device /data
selfcheck: time 0.010: disk "/data" OK
selfcheck: time 0.010: amdevice "/data" OK
selfcheck: time 0.010: device "/data" OK
selfcheck: time 0.011: checking disk /etc

so what could be causing the selfcheck to fail checking /etc... any ideas?


Re: new linux client install

2006-04-27 Thread John Clement

Stefan G. Weichinger wrote:

Paul Bijnens schrieb:

  

I think I see the light... :-)
The /tmp/amanda directory is owned by the wrong user!



or is not writable by the amanda-user, yes ... I saw that light also ;-)
Let's see if it gets through now ...

Stefan

  
OK, yes it did get rather confusing, apologies!  But thanks to all for 
the help, it appears that it was indeed the ownership of /tmp/amanda 
that was causing the problem as my amcheck doesn't complain anymore!  
Its certainly been a learning experience!!



Much thanks, John


Re: new linux client install

2006-04-26 Thread John Clement

Stefan G. Weichinger wrote:

John Clement schrieb:
  

Paul Bijnens wrote:


On 2006-04-26 15:59, John Clement wrote:
  

Paul Bijnens wrote:


On 2006-04-26 12:03, John Clement wrote:
  

/, /var, /lib, /var/lib/amanda are all readable.


To be complete, they should also be executable.

  

Just made that change.


Do you mean that one of the directories were not executable before,
but now is?
  

Just the file wasn't executable, I didn't think it had to be, but I've
made it so now.


Oh yea, restarting xinetd, probably a good idea!  Output from
amcheck now:

WARNING: murray.deanst.rroom.net: selfcheck request timed out. 
Host down?




Now it looks like xinetd had some problem with it.
Is there something listening on port 10080/udp?

Is there a debugfile created  (/tmp/amanda/amandad.*.debug)?
What is in it?

  

Since changing the user in xinetd to 'amandabackup' there haven't
been any debug files. I checked by putting 'amanda' back in there and
restarting xinetd and I did get another debug file, complaining that
access as amandabackup is not allowed from [EMAIL PROTECTED]


The user that you put in there must exist in the system (password,
NIS,...).  And the name of that user should be the one that the program
has compiled in.  You find those defaults in the debug
file, which seems to mysteriously disappear...
You cannot make something up.
  

Checking one of the debug files it was compiled with amandabackup as the
user.


So you put "amanda" in there, and you got a debug file.
What errors did you find in that file?
  

ERROR access as amandabackup not allowed from [EMAIL PROTECTED]: cannot
open /var/lib/amanda/.amand
ahosts: Permission denied



You have to have

orinoco amandabackup

in your .amandahosts, btw (apart from the perms-problem).

The server is orinoco? And there Amanda runs as amandabackup?
And tries to contact the client on murray which runs as amandabackup as
well??

  

OK, I've re-added

orinoco   amandabackup
orinoco.deanst.rroom.net   amandabackup

to the .amandahosts file,

on orinoco (the server) it runs as 'amanda', on the client it runs as 
'amandabackup'.

When putting "amandabackup" in the xinetd.conf file, you claim there
are no debug files and you get a selfcheck timeout. Right?
That means to me that "amandabackup" is not a valid user or is not
correctly defined (for xinetd).

I strongly suspect a problem with that user?  Do you have a uid-clash
(two users with different name, but same uid-number)?
Is there a local and a NIS-user that are different?

  

Having run several times with amanda and amandabackup as the user in
xinetd, its definately not making any debug files in /tmp/amanda when
xinetd's user is set to amandabackup, I've double checked that
amandabackup is a valid user, and that there's no uid clash either.



grep amanda /etc/passwd

Different group-memberships of amanda and amandabackup?

Stefan


  

amanda and amandabackup are both members of the disk group.

Cheers



Re: new linux client install

2006-04-26 Thread John Clement

Stefan G. Weichinger wrote:

John Clement schrieb:

  

OK guys, 'amanad' was my typo copying the message into the email, here's
.amandahosts



Expected this, yes ...

  

orinoco.deanst.rroom.netamanda
orinoco amanda

and amcheck

WARNING: murray.deanst.rroom.net: selfcheck request timed out.  Host down?



Does not sound like a wrong .amandahosts ...

More details (maybe you posted them earlier ..? ):

What is your Amanda-server's fqdn?
What's the fqdn of the client?
  

server: orinoco.deanst.rroom.net
client: murray.deanst.rroom.net

and digging on both servers confirms they know who they are and who each 
other are.
  

I didn't install the server or most of the clients here, I only added a
client to this particular host yesterday using an RPM, as far as I
remember it didn't ask me to configure what user it runs under.  Can you
point me in the right direction to configuring it to run as 'amanda'
which appears to be how its set on the server...



Run "amadmin  version" and look for something like :

CONFIGURE_COMMAND="'./configure' '--with-user=amanda'
'--with-group=disk' [...]

This way you find out the user and the group it was compiled with/for.
  

server:
user: amanda
group: disk

however I can't find amadmin on the client, at all (find / -name amadmin 
-print), although one of the debug files shows the following:


user: amandabackup
group: disk

Thanks, john


Stefan

  




Re: new linux client install

2006-04-26 Thread John Clement

Paul Bijnens wrote:

On 2006-04-26 15:59, John Clement wrote:

Paul Bijnens wrote:

On 2006-04-26 12:03, John Clement wrote:

/, /var, /lib, /var/lib/amanda are all readable.


To be complete, they should also be executable.


Just made that change.


Do you mean that one of the directories were not executable before,
but now is?
Just the file wasn't executable, I didn't think it had to be, but I've 
made it so now.




Oh yea, restarting xinetd, probably a good idea!  Output from 
amcheck now:


WARNING: murray.deanst.rroom.net: selfcheck request timed out.  
Host down?





Now it looks like xinetd had some problem with it.
Is there something listening on port 10080/udp?

Is there a debugfile created  (/tmp/amanda/amandad.*.debug)?
What is in it?

Since changing the user in xinetd to 'amandabackup' there haven't 
been any debug files. I checked by putting 'amanda' back in there and 
restarting xinetd and I did get another debug file, complaining that 
access as amandabackup is not allowed from [EMAIL PROTECTED]


The user that you put in there must exist in the system (password, 
NIS,...).  And the name of that user should be the one that the program

has compiled in.  You find those defaults in the debug
file, which seems to mysteriously disappear...
You cannot make something up.
Checking one of the debug files it was compiled with amandabackup as the 
user.


So you put "amanda" in there, and you got a debug file.
What errors did you find in that file?
ERROR access as amandabackup not allowed from [EMAIL PROTECTED]: cannot 
open /var/lib/amanda/.amand

ahosts: Permission denied



When putting "amandabackup" in the xinetd.conf file, you claim there
are no debug files and you get a selfcheck timeout. Right?
That means to me that "amandabackup" is not a valid user or is not
correctly defined (for xinetd).

I strongly suspect a problem with that user?  Do you have a uid-clash
(two users with different name, but same uid-number)?
Is there a local and a NIS-user that are different?

Having run several times with amanda and amandabackup as the user in 
xinetd, its definately not making any debug files in /tmp/amanda when 
xinetd's user is set to amandabackup, I've double checked that 
amandabackup is a valid user, and that there's no uid clash either.


Thanks



Re: new linux client install

2006-04-26 Thread John Clement

Stefan G. Weichinger wrote:

John Clement schrieb:
  

Paul Bijnens wrote:


Is there a debugfile created  (/tmp/amanda/amandad.*.debug)?
What is in it?

  

Since changing the user in xinetd to 'amandabackup' there haven't been
any debug files. I checked by putting 'amanda' back in there and
restarting xinetd and I did get another debug file, complaining that
access as amandabackup is not allowed from [EMAIL PROTECTED]



amanad? Third variation now ... check for typos in there.

If ok, show us .amandahosts AND Output of amcheck again.

--

Decide for one user, amanda OR amandabackup.
What user did you configure/compile Amanda with?
Make sure that user exists on that system, add it to the disk-group.

Stefan
  
OK guys, 'amanad' was my typo copying the message into the email, here's 
.amandahosts


orinoco.deanst.rroom.netamanda
orinoco amanda

and amcheck

WARNING: murray.deanst.rroom.net: selfcheck request timed out.  Host down?

I didn't install the server or most of the clients here, I only added a 
client to this particular host yesterday using an RPM, as far as I 
remember it didn't ask me to configure what user it runs under.  Can you 
point me in the right direction to configuring it to run as 'amanda' 
which appears to be how its set on the server...


Thanks again,

John



Re: new linux client install

2006-04-26 Thread John Clement

Paul Bijnens wrote:

On 2006-04-26 12:03, John Clement wrote:


-rw---   1 amandabackup disk  109 Apr 25 14:23 .amandahosts

/, /var, /lib, /var/lib/amanda are all readable.


To be complete, they should also be executable.


Just made that change.


Oh yea, restarting xinetd, probably a good idea!  Output from amcheck 
now:


WARNING: murray.deanst.rroom.net: selfcheck request timed out.  Host 
down?





Now it looks like xinetd had some problem with it.
Is there something listening on port 10080/udp?

Is there a debugfile created  (/tmp/amanda/amandad.*.debug)?
What is in it?

Since changing the user in xinetd to 'amandabackup' there haven't been 
any debug files. I checked by putting 'amanda' back in there and 
restarting xinetd and I did get another debug file, complaining that 
access as amandabackup is not allowed from [EMAIL PROTECTED]


jc



Re: new linux client install

2006-04-26 Thread John Clement

Paul Bijnens wrote:

On 2006-04-26 12:03, John Clement wrote:


-rw---   1 amandabackup disk  109 Apr 25 14:23 .amandahosts

/, /var, /lib, /var/lib/amanda are all readable.


To be complete, they should also be executable.


Just made that change.


Oh yea, restarting xinetd, probably a good idea!  Output from amcheck 
now:


WARNING: murray.deanst.rroom.net: selfcheck request timed out.  Host 
down?





Now it looks like xinetd had some problem with it.
Is there something listening on port 10080/udp?

Is there a debugfile created  (/tmp/amanda/amandad.*.debug)?
What is in it?

Since changing the user in xinetd to 'amandabackup' there haven't been 
any debug files. I checked by putting 'amanda' back in there and 
restarting xinetd and I did get another debug file, complaining that 
access as amandabackup is not allowed from [EMAIL PROTECTED]


jc



Re: new linux client install

2006-04-26 Thread John Clement

Paul Bijnens wrote:

On 2006-04-26 11:17, John Clement wrote:
ERROR: NAK murray.deanst.rroom.net: access as amandabackup not 
allowed from [EMAIL PROTECTED]: cannot open 
/var/lib/amanda/.amandahosts: Permission denied


Any more suggestions? - thanks



What about leaving the Amanda set up alone for while, and
just trying just this:

  # su amandabackup -c "cat /var/lib/amanda/.amandahosts"

Does that work, or do you get "Permission denied"?




Hey Paul, sorry I didn't think to include the result of doing this earlier:

[EMAIL PROTECTED] amanda]# su amandabackup -c "cat /var/lib/amanda/.amandahosts"
orinoco.deanst.rroom.netamanda
orinoco amanda
[EMAIL PROTECTED] amanda]#


thanks


Re: new linux client install

2006-04-26 Thread John Clement

Stefan G. Weichinger wrote:

John Clement schrieb:

  

OK, the story continues, thanks to all those who've contributed so
far!!  Here's how things are now after all your comments.  The client is
a new install of 2.5, server is 2.4.4p3

-rw---   1 amandabackup disk  109 Apr 25 14:23 .amandahosts

/, /var, /lib, /var/lib/amanda are all readable.

xinetd.d/amanda:

=
service amanda
{
   socket_type = dgram
   protocol= udp
   wait= yes
   user= amandabackup
   group   = disk
   groups  = yes
   server  = /usr/lib/amanda/amandad
   disable = no
   only_from   = 10.10.1.8 192.168.0.1
}
=

but still I get this from amcheck:

ERROR: NAK murray.deanst.rroom.net: access as amandabackup not allowed
from [EMAIL PROTECTED]: cannot open /var/lib/amanda/.amandahosts:
Permission denied

Any more suggestions? - thanks



Was xinetd restarted after editing that file?
What if you remove the "only_from"-line for a test (and restart xinetd)?

Here it looks like

# ls -la ~amanda/.amandahosts
-rw---  1 amanda root 190 Jun 27  2005 /var/lib/amanda/.amandahosts

Stefan

  

Oh yea, restarting xinetd, probably a good idea!  Output from amcheck now:

WARNING: murray.deanst.rroom.net: selfcheck request timed out.  Host down?



Re: new linux client install

2006-04-26 Thread John Clement

Paul Bijnens wrote:

On 2006-04-26 10:12, John Clement wrote:

Pavel Pragin wrote:

John Clement wrote:

Having read through some of the documentation it seemed a fairly 
straight forward thing to install an Amanda client.  However, I 
used an rpm for it, having been forced to upgrade my tar software 
too but it appears to be running as amandabackup and in 
/var/lib...  So I'm now getting the following:



amandad: time 0.002: accept error: access as amandabackup not 
allowed from [EMAIL PROTECTED]: cannot open 
/var/lib/amanda/.amandahosts: Permission denied

amandad: time 0.002: sending NAK pkt:
<<<<<
ERROR access as amandabackup not allowed from [EMAIL PROTECTED]: 
cannot open /var/lib/amanda/.amandahosts: Permission denied

>>>>>


at the bottom of my amcheck.  I've confirmed that the file is owned 
and chmoded correctly:


-rw---   1 amandabackup disk  109 Apr 25 14:23 .amandahosts

If I change the ownership or permissions it complains, so I think 
they are correct.  In the .amandahosts file I have


server.domain.tld   amanda
server  amanda
server.domain.tld   amandabackup #added incase it made a difference
server   amandabackup #added incase it made a difference

So can anyone make any suggestions?

Thanks


make sure that /var/lib/amanda/.amandahosts is owned by amanda and 
the group is set to disk "chown amanda:disk 
/var/lib/amanda/.amandahosts"



Sorry, yes, it was infact owned by amanda:disk, the line I posted was 
from one of the 'lets just change something and hope it works' 
attempts I was having...





...
It should be owned by the user the runs the amanda software.
It seems that is "amandabackup" in your setup.

Anatomy of the errormsg:
   access as amandabackup not allowed
   from [EMAIL PROTECTED]: cannot open /var/lib/amanda/.amandahosts:
   Permission denied

"amandabackup" is the local user
"[EMAIL PROTECTED]" is the [EMAIL PROTECTED] that tries to connect.
And the errormsg is that the local user "amandabackup" has no
permission to read/access the file .amandahosts .

So try:
   # su amandabackup -c "cat /var/lib/amanda/.amandahosts"

and fix those permissions.


OK, the story continues, thanks to all those who've contributed so 
far!!  Here's how things are now after all your comments.  The client is 
a new install of 2.5, server is 2.4.4p3


-rw---   1 amandabackup disk  109 Apr 25 14:23 .amandahosts

/, /var, /lib, /var/lib/amanda are all readable.

xinetd.d/amanda:

=
service amanda
{
   socket_type = dgram
   protocol= udp
   wait= yes
   user= amandabackup
   group   = disk
   groups  = yes
   server  = /usr/lib/amanda/amandad
   disable = no
   only_from   = 10.10.1.8 192.168.0.1
}
=

but still I get this from amcheck:

ERROR: NAK murray.deanst.rroom.net: access as amandabackup not allowed 
from [EMAIL PROTECTED]: cannot open /var/lib/amanda/.amandahosts: 
Permission denied


Any more suggestions? - thanks


Re: new linux client install

2006-04-26 Thread John Clement

Pavel Pragin wrote:

John Clement wrote:

Having read through some of the documentation it seemed a fairly 
straight forward thing to install an Amanda client.  However, I used 
an rpm for it, having been forced to upgrade my tar software too but 
it appears to be running as amandabackup and in /var/lib...  So I'm 
now getting the following:



amandad: time 0.002: accept error: access as amandabackup not allowed 
from [EMAIL PROTECTED]: cannot open /var/lib/amanda/.amandahosts: 
Permission denied

amandad: time 0.002: sending NAK pkt:
<<<<<
ERROR access as amandabackup not allowed from [EMAIL PROTECTED]: cannot 
open /var/lib/amanda/.amandahosts: Permission denied

>>>>>


at the bottom of my amcheck.  I've confirmed that the file is owned 
and chmoded correctly:


-rw---   1 amandabackup disk  109 Apr 25 14:23 .amandahosts

If I change the ownership or permissions it complains, so I think 
they are correct.  In the .amandahosts file I have


server.domain.tld   amanda
server  amanda
server.domain.tld   amandabackup #added incase it made a difference
server   amandabackup #added incase it made a difference

So can anyone make any suggestions?

Thanks


make sure that /var/lib/amanda/.amandahosts is owned by amanda and the 
group is set to disk "chown amanda:disk /var/lib/amanda/.amandahosts"



Sorry, yes, it was infact owned by amanda:disk, the line I posted was 
from one of the 'lets just change something and hope it works' attempts 
I was having...


new linux client install

2006-04-25 Thread John Clement
Having read through some of the documentation it seemed a fairly 
straight forward thing to install an Amanda client.  However, I used an 
rpm for it, having been forced to upgrade my tar software too but it 
appears to be running as amandabackup and in /var/lib...  So I'm now 
getting the following:



amandad: time 0.002: accept error: access as amandabackup not allowed 
from [EMAIL PROTECTED]: cannot open /var/lib/amanda/.amandahosts: 
Permission denied

amandad: time 0.002: sending NAK pkt:
<
ERROR access as amandabackup not allowed from [EMAIL PROTECTED]: cannot 
open /var/lib/amanda/.amandahosts: Permission denied

>


at the bottom of my amcheck.  I've confirmed that the file is owned and 
chmoded correctly:


-rw---   1 amandabackup disk  109 Apr 25 14:23 .amandahosts

If I change the ownership or permissions it complains, so I think they 
are correct.  In the .amandahosts file I have


server.domain.tld   amanda
server  amanda
server.domain.tld   amandabackup #added incase it made a difference
server   amandabackup #added incase it made a difference

So can anyone make any suggestions?

Thanks


Re: linux backup problem

2006-04-24 Thread John Clement
Both files included below, they don't look bad to me, I'm not really 
sure what I'm looking for!


thanks

==
[EMAIL PROTECTED] amanda]# more selfcheck.20060424153239.debug
selfcheck: debug 1 pid 22993 ruid 33 euid 33: start at Mon Apr 24 
15:32:39 2006

/usr/lib/amanda/selfcheck: version 2.4.3
selfcheck: time 0.002: checking disk /data
selfcheck: time 0.003: device /data
selfcheck: time 0.003: disk "/data" OK
selfcheck: time 0.003: amdevice "/data" OK
selfcheck: time 0.003: device "/data" OK
selfcheck: time 0.004: checking disk /etc
==
[EMAIL PROTECTED] amanda]# more amandad.20060424153239.debug
amandad: debug 1 pid 22991 ruid 33 euid 33: start at Mon Apr 24 15:32:39 
2006

amandad: version 2.4.3
amandad: build: VERSION="Amanda-2.4.3"
amandad:BUILT_DATE="Thu Feb 13 11:14:37 EST 2003"
amandad:BUILT_MACH="Linux stripples.devel.redhat.com 
2.4.20-2.41smp #1 SMP Sun Feb 9

09:47:42 EST 2003 i686 i686 i386 GNU/Linux"
amandad:CC="gcc"
amandad:CONFIGURE_COMMAND="'./configure' 
'--host=i386-redhat-linux' '--build=i386-re
dhat-linux' '--target=i386-redhat-linux-gnu' '--program-prefix=' 
'--prefix=/usr' '--exec-pre
fix=/usr' '--bindir=/usr/bin' '--sbindir=/usr/sbin' '--sysconfdir=/etc' 
'--datadir=/usr/shar
e' '--includedir=/usr/include' '--libdir=/usr/lib' 
'--libexecdir=/usr/lib/amanda' '--localst
atedir=/var/lib' '--sharedstatedir=/usr/com' '--mandir=/usr/share/man' 
'--infodir=/usr/share
/info' '--enable-shared' '--with-index-server=localhost' 
'--with-gnutar-listdir=/var/lib/ama
nda/gnutar-lists' '--with-smbclient=/usr/bin/smbclient' 
'--with-amandahosts' '--with-user=am

anda' '--with-group=disk' '--with-gnutar=/bin/tar'"
amandad: paths: bindir="/usr/bin" sbindir="/usr/sbin"
amandad:libexecdir="/usr/lib/amanda" mandir="/usr/share/man"
amandad:AMANDA_TMPDIR="/tmp/amanda" AMANDA_DBGDIR="/tmp/amanda"
amandad:CONFIG_DIR="/etc/amanda" DEV_PREFIX="/dev/"
amandad:RDEV_PREFIX="/dev/r" DUMP="/sbin/dump"
amandad:RESTORE="/sbin/restore" SAMBA_CLIENT="/usr/bin/smbclient"
amandad:GNUTAR="/bin/tar" COMPRESS_PATH="/usr/bin/gzip"
amandad:UNCOMPRESS_PATH="/usr/bin/gzip" MAILER="/usr/bin/Mail"
amandad:listed_incr_dir="/var/lib/amanda/gnutar-lists"
amandad: defs:  DEFAULT_SERVER="localhost" DEFAULT_CONFIG="DailySet1"
amandad:DEFAULT_TAPE_SERVER="localhost"
amandad:DEFAULT_TAPE_DEVICE="/dev/null" HAVE_MMAP HAVE_SYSVSHM
amandad:LOCKING=POSIX_FCNTL SETPGRP_VOID DEBUG_CODE
amandad:AMANDA_DEBUG_DAYS=4 BSD_SECURITY USE_AMANDAHOSTS
amandad:CLIENT_LOGIN="amanda" FORCE_USERID HAVE_GZIP
amandad:COMPRESS_SUFFIX=".gz" COMPRESS_FAST_OPT="--fast"
amandad:COMPRESS_BEST_OPT="--best" UNCOMPRESS_OPT="-dc"
amandad: time 0.001: got packet:

Amanda 2.4 REQ HANDLE 00A-B0609709 SEQ 1145889179
SECURITY USER amanda
SERVICE noop
OPTIONS features=feff9ffe0f;


amandad: time 0.001: sending ack:

Amanda 2.4 ACK HANDLE 00A-B0609709 SEQ 1145889179


amandad: time 0.002: bsd security: remote host orinoco.deanst.rroom.net 
user amanda local us

er amanda
amandad: time 0.002: amandahosts security check passed
amandad: time 0.002: running service "noop"
amandad: time 0.002: sending REP packet:

Amanda 2.4 REP HANDLE 00A-B0609709 SEQ 1145889179
OPTIONS features=feff9f00;


amandad: time 0.003: got packet:

Amanda 2.4 ACK HANDLE 00A-B0609709 SEQ 1145889179


amandad: time 0.003: pid 22991 finish time Mon Apr 24 15:32:39 2006
==


Paul Bijnens wrote:

On 2006-04-24 15:45, John Clement wrote:

When I run my amcheck I get

WARNING: host.domain.com: selfcheck reply timed out.

and on 'host.domain.com' I end up with the following processing:

amanda   20128  0.3  0.2  2192  752 ?S13:25   0:00 amandad
amanda   20129  0.1  0.2  1952  752 ?S13:25   0:00 
/usr/lib/amanda/selfcheck
amanda   20130  0.0  0.0 00 ?Z13:25   0:00 
[amandad ]


If I now run amcheck again it reports back:

ERROR: NAK host.domain.com: amandad busy

So pressumably the selfcheck is hanging, does this sound right and 
does anyone have any idea why?


Have a look in the debug file on the client in 
/tmp/amanda/selfcheck.[datetime].debug.

(and maybe also in the amandad.[datetime].debug file itself too.)

Also check the list of problems, mentioned in:

http://wiki.zmanda.com/index.php/Amcheck:_selfcheck_request_timed_out






Thanks - jc











linux backup problem

2006-04-24 Thread John Clement

When I run my amcheck I get

WARNING: host.domain.com: selfcheck reply timed out.

and on 'host.domain.com' I end up with the following processing:

amanda   20128  0.3  0.2  2192  752 ?S13:25   0:00 amandad
amanda   20129  0.1  0.2  1952  752 ?S13:25   0:00 
/usr/lib/amanda/selfcheck
amanda   20130  0.0  0.0 00 ?Z13:25   0:00 [amandad 
]


If I now run amcheck again it reports back:

ERROR: NAK host.domain.com: amandad busy

So pressumably the selfcheck is hanging, does this sound right and does 
anyone have any idea why?


Thanks - jc





Re: problem backing up Windows host

2006-04-24 Thread John Clement

Paul Bijnens wrote:

On 2006-04-21 14:22, John Clement wrote:

Paul Bijnens wrote:

On 2006-04-21 13:28, John Clement wrote:
I've just inherited an amanda setup that has apparently never 
worked properly.  The specific problem I'm trying to sort at the 
moment is summed up below.


Amanda Backup Client Hosts Check

ERROR: NAK finn.internal.domain.com: access as amanda not allowed 
from [EMAIL PROTECTED]: cannot open 
/usr/amanda/etc/amanda/.amandahosts: Permission denied


The user "amanda" should be able to read that file.  (and the all the
upper directories too).
Just checked, 'everyone' has access to that file and its parent 
directories...


Not "everyone" but specifically user "amanda" needs to have access
(yes there is a difference).  ("...access as amanda ")


Try this as user amanda, not just looking at the permissions.


Thanks guys for all the info, I've just found out though that apparently 
there's a strange client installed on that machine which apparently 
doesn't work, so I've switched to backing up via samba and it seems ok. ;-)


Re: problem backing up Windows host

2006-04-21 Thread John Clement

Paul Bijnens wrote:

On 2006-04-21 13:28, John Clement wrote:
I've just inherited an amanda setup that has apparently never worked 
properly.  The specific problem I'm trying to sort at the moment is 
summed up below.


Amanda Backup Client Hosts Check

ERROR: NAK finn.internal.domain.com: access as amanda not allowed 
from [EMAIL PROTECTED]: cannot open 
/usr/amanda/etc/amanda/.amandahosts: Permission denied


The user "amanda" should be able to read that file.  (and the all the
upper directories too).
Just checked, 'everyone' has access to that file and its parent 
directories...



Client check: 1 host checked in 0.002 seconds, 1 problem found

finn is a Windows server, and as far as I can see the client is setup 
the same on this as on another windows machine that is backing up 
ok.  Its got 'amanda' and 'amanda_backup' as users of the machines, 
amanda is installed in c:\usr on both.  There's a .amandahosts file 
on both with the same in:


orinoco x.x.x.x
orinoco.internal.domain.com x.x.x.x


This seems to imply that "x.x.x.x" is an ip-number.
No it is not.
The second item on the line is the "remoteuser" (defaults to local user
if empty).


Yes, sorry, my bad, it is infact

orinoco amanda
orinoco.internal.domain.com amanda

not sure where I got the idea it was an IP address from!

Thanks,
jc


problem backing up Windows host

2006-04-21 Thread John Clement
I've just inherited an amanda setup that has apparently never worked 
properly.  The specific problem I'm trying to sort at the moment is 
summed up below.


Amanda Backup Client Hosts Check

ERROR: NAK finn.internal.domain.com: access as amanda not allowed from 
[EMAIL PROTECTED]: cannot open 
/usr/amanda/etc/amanda/.amandahosts: Permission denied

Client check: 1 host checked in 0.002 seconds, 1 problem found

finn is a Windows server, and as far as I can see the client is setup 
the same on this as on another windows machine that is backing up ok.  
Its got 'amanda' and 'amanda_backup' as users of the machines, amanda is 
installed in c:\usr on both.  There's a .amandahosts file on both with 
the same in:


orinoco x.x.x.x
orinoco.internal.domain.com x.x.x.x

The only difference I can see is that finn is win 2000, and the one that 
works is win 2003.  Any ideas anyone?


Thanks,

John