Page 2 of 2 FirstFirst 12
Results 11 to 16 of 16

Thread: amrecover from Client machine

  1. #11

    Default

    ofc not

    only_from = zeus.iit.restoofdomainname 192.168.2.15
    zeus being the backup server and declared in the dns server too. 192.168 is the client.

    I've examined the xinetd logs first thing but they are not informative at all
    even when I specify (in the xinetd.conf) the full range of availabe options. One thing though. When I examine the whole process flow (when I amrecover on the server ) I see that xinetd spawns amandad which in turn spawns amindexd (parent id of amindexd is amandad).....It's a bit confusing. xinetd spawns all the am* server processes or is there a different sequence of events?

    I wish I could see more info on the xinetd logs. I tried the syslog xinetd log option in xinetd.conf but the amount of available debug info was exactly the same (I didn't persist though so that's something I have to try again).

    thx for taking the time with me.

    ps. btw Im on a SuSE 9.2 with 2.5.1p1 which I compiled.
    Last edited by taruone; October 2nd, 2006 at 02:09 PM.

  2. #12
    Join Date
    Aug 2006
    Posts
    34

    Default

    I'm having the exact same problem. I changed my auth type to bsdtcp in hopes that it would resolve other issues I was having with unpredictable client timeouts, which so far it did, but now I can't recover! Relevant files:

    .amandahosts on the server(middenheap):
    Code:
    daddy.xxx.edu root amindexd amidxtaped
    .amandahosts on the client (daddy):
    Code:
    localhost.localdomain   amandabackup amdump
    middenheap-dev.xxx.edu amandabackup amdump
    middenheap.xxx.edu amandabackup amdump
    (btw, Middenheap-dev and Middenheap point at the same IP address)

    /etc/xinetd.d/amandaserver on server:
    service amanda
    {
    disable = no
    socket_type = stream
    protocol = tcp
    wait = no
    user = amandabackup
    group = disk
    groups = yes
    server = /usr/lib/amanda/amandad
    server_args = -auth=bsdtcp amdump amindexd amidxtaped
    }



    /etc/xinetd.d/amanda on client:
    service amanda
    {
    disable = no
    socket_type = stream
    protocol = tcp
    wait = no
    user = amandabackup
    group = disk
    groups = yes
    server = /usr/lib/amanda/amandad
    server_args = -auth=bsdtcp amdump
    }

    Recovery command, run as root on client:
    amrecover ISDaily2.5 -s middenheap.xxx.edu -t middenheap.xxx.edu -d changer
    AMRECOVER Version 2.5.1. Contacting server on middenheap.iXXX ...
    [request failed: timeout waiting for ACK]

    amrecover.*.debug:
    Code:
    [root@daddy ~]# cat /tmp/amanda/client/ISDaily2.5/amrecover.20061019111119.debug
    amrecover: debug 1 pid 17915 ruid 0 euid 0: start at Thu Oct 19 11:11:19 2006
    Could not open conf file "/etc/amanda/amanda-client.conf": No such file or directory
    Could not open conf file "/etc/amanda/ISDaily2.5/amanda-client.conf": No such file or directory
    amrecover: debug 1 pid 17915 ruid 0 euid 0: rename at Thu Oct 19 11:11:19 2006
    security_getdriver(name=bsd) returns 0x1380e0
    security_handleinit(handle=0x9166b48, driver=0x1380e0 (BSD))
    amrecover: bind_portrange2: Try  port 914: Available   - Success
    amrecover: dgram_bind: socket bound to 0.0.0.0.914
    amrecover: dgram_send_addr(addr=0xbfef3f90, dgram=0x139084)
    amrecover: (sockaddr_in *)0xbfef3f90 = { 2, 24615, 130.207.169.188 }
    amrecover: dgram_send_addr: 0x139084->socket = 3
    amrecover: dgram_send_addr(addr=0xbfef3d30, dgram=0x139084)
    amrecover: (sockaddr_in *)0xbfef3d30 = { 2, 24615, 130.207.169.188 }
    amrecover: dgram_send_addr: 0x139084->socket = 3
    amrecover: dgram_send_addr(addr=0xbfef3d30, dgram=0x139084)
    amrecover: (sockaddr_in *)0xbfef3d30 = { 2, 24615, 130.207.169.188 }
    amrecover: dgram_send_addr: 0x139084->socket = 3
    security_seterror(handle=0x9166b48, driver=0x1380e0 (BSD) error=timeout waiting for ACK)
    security_close(handle=0x9166b48, driver=0x1380e0 (BSD))
    I tried setting this in xinetd.conf and restarting xinetd, but I'm not getting any more info in /var/log/messages than I usually do:
    log_type = SYSLOG authpriv info

    Even though I already have a rule allowing all traffic between client and server, I also tried stopping iptables on both client and server, this changed nothing.

    help! My backups are no good without recovery...
    Client on Daddy is amanda-backup_client-2.5.1-1.fc3 installed via RPM.
    Server is amanda-backup_server-2.5.1b2-1.rhel4 via RPM

    I'll try recovering from a RHEL4 client this afternoon...

  3. #13
    Join Date
    Oct 2005
    Posts
    1,559

    Default

    Hi Bethany,

    Are you able to recover from backup when you run amrecover on Amanda server?

    Thanks,
    Paddy

  4. #14
    Join Date
    Nov 2005
    Location
    Canada
    Posts
    1,049

    Default

    amrecover is still using bsd auth

    add
    auth "bsdtcp"
    in /opt/amanda-2.5.1/etc/amanda/amanda-client.conf

  5. #15
    Join Date
    Aug 2006
    Posts
    34

    Default

    Paddy,
    I can't recover from backup running amrecover on the Amanda server:

    Code:
    amrecover ISDaily2.5 -s middenheap.xxx.edu -t middenheap.xxx.edu -d changer
    AMRECOVER Version 2.5.1b2. Contacting server on middenheap.xxx.edu ...
    [request failed: timeout waiting for ACK]
    Martineau, do you mean on the client on server? Guess I'll try both...

  6. #16
    Join Date
    Aug 2006
    Posts
    34

    Default

    OK, Martineau had the solution: I needed a /etc/amanda/amanda-client.conf with auth "bsdtcp" on each backup client. thanks so much!
    Last edited by bethany; October 19th, 2006 at 02:09 PM.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •