amrecover issues with linux server and solaris client dump

2001-08-07 Thread auto204958

My amanda server is a linux box mybackup.me.com 192.1.1.1
My solaris client is a solaris 7 box sun-server.me.com 192.1.1.2

The email says everything was backed up and the index file lists all
the correct files, but when I try to extract a file it asks me if I
want to restore it to a  dir instead of the proper
dir. What's wrong?

# amrecover -C Daily
AMRECOVER Version 2.4.2p2. Contacting server on
mybackup ...
220 mybackup AMANDA index server (2.4.2p2) ready.
200 Access OK
Setting restore date to today (2001-01-17)
200 Working date set to 2001-01-17.
200 Config set to Daily.
501 No index records for host: mybackup. Invalid?
Trying mybackup ...
501 No index records for host: mybackup. Invalid?
Trying localhost ...
501 No index records for host: localhost. Invalid?
amrecover> sethost sun-server
200 Dump host set to sun-server.
amrecover> ls
Must select a disk before listing files
amrecover> setdisk /mydir
Scanning /dumps/amanda...
20010117: found Amanda directory.
200 Disk set to /mydir.
amrecover> ls
shell-init: could not get current directory: getcwd: cannot access
parent directories: No such file or directory
2001-01-17 .
2001-01-17 bin/
amrecover> cd bin
amrecover> ls
shell-init: could not get current directory: getcwd:cannot access
parent directories: No such file or directory
2001-01-17 .
2001-01-17 core.html
amrecover> add core.html
Added /bin/core.html
amrecover> extract
Extracting files using tape drive /dev/nst0 on host mybackup. 
The following tapes are needed: DailySet222 
Restoring files into directory ¨yass@%^!%@#^!?

The amanda.conf on the server used a dump rather than gnu tar and
compression was enabled.

The linux versions were:
dump 0.4b19
tar (GNU tar) 1.13.17

The sun versions were:
# dump -V
dump: Software Generation Utilities (SGU) Solaris-ELF (4.0)
The gnu tar is /bin/tar which come with solaris 7

Is amrecover refusing to restore the file because it was dumped on
solaris which has compatibility issues with the linux dump?

Thanks.
Free, secure Web-based email, now OpenPGP compliant - www.hushmail.com




amrecover issues

2001-08-07 Thread auto204958

If I do amrecover on the command line,
# amrecover
AMRECOVER Version 2.4.2p2. Contacting server on mybackup ...
220 mybackup AMANDA index server (2.4.2p2) ready.
200 Access OK
Setting restore date to today (2001-01-01)
200 Working date set to 2001-01-01.
200 Working date set to 2001-01-01.
amrecover: Unexpected server end of file
#
Amanda complains of "amrecover: Unexpected server end of file" My amanda tape server 
is mybackup server 10.1.1.10. I want to restore a file from its /var backup. If I do 
this
# amrecover -C Daily
AMRECOVER Version 2.4.2p2. Contacting server on
mybackup ...
220 mybackup AMANDA index server (2.4.2p2) ready.
200 Access OK
Setting restore date to today (2001-01-01)
200 Working date set to 2001-01-01.
200 Config set to Daily.
501 No index records for host: mybackup. Invalid?
Trying mybackup ...
501 No index records for host: mybackup. Invalid?
Trying localhost ...
501 No index records for host: localhost. Invalid?
amrecover> sethost 10.1.1.10
200 Dump host set to 10.1.1.10.
amrecover> setdisk /var
Scanning /dumps/amanda...
200 Disk set to /var.
No index records for disk for specified date
If date correct, notify system administrator
amrecover> history
200- Dump history for config "Daily" host "10.1.1.10"
disk "/var"
201- 2001-01-01 0 DailySet10 1
200 Dump history for config "Daily" host "10.1.1.10"
disk "/var"
amrecover>

I know the dumps are working for /var. I get a successful backup email and amadmin 
works too except for amrecover. Weird huh? My /etc/hosts file is correct. I have index 
generation enabled too and there are files created in my index dir.

I also know daemons and hosts file are ok
# more /etc/hosts
127.0.0.1   mybackup localhost
10.1.1.10   mybackup.test.com mybackup

#more /home/amanda/.amandahosts
mybackup amanda
mybackup root
mybackup.test.com amanda
mybackup.test.com root
10.1.1.10 amanda
10.1.1.10 root

Thourgh the includedir /etc/xinetd.d directive, the 3 services also work
::
amanda
::
service amanda
{
 socket_type= dgram
 protocol   = udp
 wait   = yes
 user   =amanda
 group  =disk
 server =/usr/local/libexec/amandad
 disable=no
}
::
amandaidx
::
service amandaidx
{
socket_type = stream
protocol= tcp
wait= no
user=root
groups  =yes
server  =/usr/local/libexec/amindexd
}
::
amidxtape
::
service amidxtape
{
 socket_type = stream
protocol= tcp
wait= no
user= root
groups  = yes
server  =
/usr/local/libexec/amidxtaped
server_args = amidxtaped
}

The xinetd /var/log/messages confirm that xinet serves
the four processes just fine
mybackup xinetd[11344]: xinetd Version 2.1
mybackup xinetd[11344]: libwrap
mybackup xinetd[11344]: options compiled in.
mybackup xinetd[11344]: Started working: 3 available services
mybackup xinetd: xinetd startup succeeded
 
I also have the correct entries in /etc/services 
amanda  10080/udp #amanda backup services
kamanda 10081/tcp #amanda backup services(Kerberos)
kamanda 10081/udp #amanda backup services (Kerberos)
amandaidx   10082/tcp #amanda backup services
amidxtape   10083/tcp #amanda backup services

My /etc/hosts.allow has all:all

Here is my amanda.conf and my disklist

-
define dumptype global {
index yes
}

define dumptype myvartest {
comment "/var directory"
compress client best
holdingdisk yes
index yes
}

As for the disklist,
#more disklist
10.1.1.10 /var myvartest

The backups work, but restores using amrecover don't. What could be wrong?
Thanks.
Free, secure Web-based email, now OpenPGP compliant - www.hushmail.com