Yahoo got a backup done. Now gotta test it

[kdlarg]

per this:
http://wiki.zmanda.com/index.php/Quick_start#Modify_amanda.conf

mkdir -p myrestoretest
# pwd
/var/tmp/myrestoretest
cd /var/tmp/myrestoretest/
mkdir data
/usr/local/sbin/ammt -f file:/var/tmp/myrestoretest rewind
ll
total 8
drwxr-xr-x 2 root root 4096 Jan 4 14:42 data
-rw------- 1 root root 15 Jan 4 14:43 info
/usr/local/sbin/amrecover test
AMRECOVER Version 2.5.1p2. Contacting server on servername.com ...
[request failed: timeout waiting for ACK]

[kdlarg]

Ignore that last post i must be completely stupid.
/usr/local/sbin/amrecover DailySet1 looks like it workin better

[kdlarg]

/usr/local/sbin/amrecover DailySet1
AMRECOVER Version 2.5.1p2. Contacting server on servnamehere ...
[request failed: timeout waiting for ACK]

]# more amrecover.20070104154136.debug
amrecover: debug 1 pid 7203 ruid 0 euid 0: start at Thu Jan 4 15:41:36 2007
Reading conf file "/usr/local/etc/amanda/amanda-client.conf".
Reading conf file "/usr/local/etc/amanda/DailySet1/amanda-client.conf".
amrecover: debug 1 pid 7203 ruid 0 euid 0: rename at Thu Jan 4 15:41:36 2007
security_getdriver(name=bsd) returns 0x84c0e0
security_handleinit(handle=0x9ff3e20, driver=0x84c0e0 (BSD))
amrecover: bind_portrange2: Try port 675: Available - Success
amrecover: dgram_bind: socket bound to 0.0.0.0.675
amrecover: dgram_send_addr(addr=0xbff76b30, dgram=0x84d024)
amrecover: (sockaddr_in *)0xbff76b30 = { 2, 10080, 192.168.0.2 }
amrecover: dgram_send_addr: 0x84d024->socket = 3
amrecover: dgram_send_addr(addr=0xbff768d0, dgram=0x84d024)
amrecover: (sockaddr_in *)0xbff768d0 = { 2, 10080, 192.168.0.2 }
amrecover: dgram_send_addr: 0x84d024->socket = 3
amrecover: dgram_send_addr(addr=0xbff768d0, dgram=0x84d024)
amrecover: (sockaddr_in *)0xbff768d0 = { 2, 10080, 192.168.0.2 }
amrecover: dgram_send_addr: 0x84d024->socket = 3
security_seterror(handle=0x9ff3e20, driver=0x84c0e0 (BSD) error=timeout waiting for ACK)
security_close(handle=0x9ff3e20, driver=0x84c0e0 (BSD))

[ppragin]

Did you create /etc/amanda/amanda-client.conf on the client system?
1. create this file as user amandabackup
/etc/amanda/amanda-client.conf:

conf "DailySet1" # your config name
index_server "backupserver" # your amindexd server
tape_server "backupserver" # your amidxtaped server
#tapedev "" # your tape device
auth "bsdtcp"

2. run "amrecover"

[kdlarg]

server and client all on single box.
# amanda.conf - sample Amanda client configuration file.
#
# This file normally goes in /usr/local/etc/amanda/amanda-client.conf.
#

conf "DailySet1" # your config name

index_server "servername.com" # your amindexd server
tape_server "servername.com" # your amidxtaped server
tapedev "/dev/nst0" # your tape device

# auth - authentication scheme to use between server and client.
# Valid values are "bsd", "krb4", "krb5" and "ssh".
# Default: [auth "bsd"]
auth "bsd"

ssh_keys "" # your ssh keys file if you use ssh auth

/usr/local/sbin/amrecover
AMRECOVER Version 2.5.1p2. Contacting server on servername.com ...
[request failed: timeout waiting for ACK]


How do I pull out a day ? dont u pull per tape label?

[ppragin]

Please change:
auth "bsd" --> auth "bsdtcp" in the amanda-client.conf file

[kdlarg]

OK that was it.

so after a little how to
http://www.amanda.org/docs/using.html#config_use_amrecover

got files back.

Thanks a ton to everyone here this forum is very helpful.

Of course if I can ever help someone feel free to ping me

[paddy]

> OK that was it.

> so after a little how to
> http://www.amanda.org/docs/using.html#config_use_amrecover

> got files back.

You can get this information from Amanda wiki (http://wiki.zmanda.com/index.php/Amanda_chapter#Configuring_and_Using_amrecover) also.

> Thanks a ton to everyone here this forum is very helpful.

> Of course if I can ever help someone feel free to ping me

You can help Amanda community by answering user queries in forums :-)

Thanks,
Paddy