Sir;
Sorry to bother you again. But I had encountered some difficulties.
My two computers, one was set as amanda(version 2.4.4p1) server( also I
setup the client (version 2.4.4p1) software in the same computer; IP
192.168.8.12);
another I only set as amanda client (version 2.4.4p1)(configure without
server; IP 192.168.8.18). In server host I succeeded in finding the client
host which located in the server host. However I couldn't find the client
host located in another computer.
All my os are Redhat Linux 9.0, which has installed amanda 2.4.3(because I
selected all affiliated software installed when installed Redhat), that
was;, all 2 computer had installed amanda 2.4.3 when I finished Redhat
installation ; but it seems neither worked; then later I installed amanda
2.4.4p1 in the computer which now called server host; the details are just
as descriped in <http://amanda.sourceforge.net/fom-serve/cache/191.html>. I
succeeded when I backed up localhost's files in server computer; but when I
wanted to back up another computer's file, the server couldn't find the
remote client. When installed client software (version 2.4.4p1) in
192.168.8.18 I referred the article <Backing up clinic machines with AMANDA
<http://www.cs.hmc.edu/tech_docs/qref/amanda-client.html>>. I then installed
amanda client (Version: 2.4.4p1) with configureation: user=amanda group=disk
without-server;
[root@caiwc root]# vi /etc/services :
amand 10080/udp
amandaidx 10082/tcp
amidxtape 10083/tcp
vi /etc/hosts.allow:
amanda:192.168.8.12
amanda:192.168.8.18
amandad: 192.168.8.12
amandad: 192.168.8.18
# hosts.allow This file describes the names of the hosts which are
# allowed to use the local INET services, as decided
# by the '/usr/sbin/tcpd' server.
vi ~amanda/.amandahosts:
localhost amanda
localhost.localdomain amanda
192.168.8.12 amanda
192.168.8.18 amanda
find files in directory xinetd.d/:
vi amanda file:
service amanda
{
disable = no
socket_type = dgram
protocol = udp
wait = yes
user = amanda
group = disk
server = /usr/lib/amanda/amandad
}
vi amandaidx file:
service amandaidx
{
disable = no
socket_type = stream
protocol = tcp
wait = no
user = amanda
group = disk
server = /usr/lib/amanda/amindexd
}
vi amidxtape:
service amidxtape
{
disable = no
socket_type = stream
protocol = tcp
wait = no
user = amanda
group = disk
server = /usr/lib/amanda/amidxtaped
}
the above iare all edited in client computer(IP 192.168.8.18);
the following is in server computer(IP 192.168.8.12), which had installed
amanda server and client (version 2.4.4p1):
[root@cai root]#vi /etc/services :
amand 10080/udp
amandaidx 10082/tcp
amidxtape 10083/tcp
vi /etc/hosts.allow
amandad: 192.168.8.18
amandad: cai
amandad:192.168.8.12
amanda: cai
amanda: 192.168.8.12
amanda: root
amandad: root
amandad: 127.0.0.1
amanda: 192.168.8.18
amanda: 127.0.0.1
vi ~amanda/.amandahosts:
localhost amanda
localhost.localdomain amanda
192.168.8.12 amanda
cai (this is the server hostname ) amanda
192.168.8.18 amanda
127.0.0.1 amanda
~
find files in directory xinetd.d/:
vi amanda file:
service amanda
{
disable = no
socket_type = dgram
protocol = udp
wait = yes
user = amanda
group = disk
server = /usr/lib/amanda/amandad
}
vi amandaidx file:
service amandaidx
{
disable = no
socket_type = stream
protocol = tcp
wait = no
user = amanda
group = disk
server = /usr/lib/amanda/amindexd
}
vi amidxtape:
service amidxtape
{
disable = no
socket_type = stream
protocol = tcp
wait = no
user = amanda
group = disk
server = /usr/lib/amanda/amidxtaped
}
when amcheck DailySet1, the server only find the client in the same
computer(192.168.8.12), all amanda operations seemed OK in 192.168.8.12;
it couldn't find clent in 192.168.8.18;
the details are as following:
bash-2.05b$ amcheck DailySet1
Amanda Tape Server Host Check
-----------------------------
Holding disk /var/tmp: 3611336 KB disk space available, that's plenty
amcheck-server: slot 13: date 20030928 label DailySet113 (active tape)
amcheck-server: slot 14: date X label DailySet101 (first labelstr
match)
amcheck-server: slot 1: date X label DailySet101 (labelstr match)
amcheck-server: slot 2: date 20030901 label DailySet102 (active tape)
amcheck-server: slot 3: date 20030901 label DailySet103 (active tape)
amcheck-server: slot 4: date 20030902 label DailySet104 (active tape)
amcheck-server: slot 5: date 20030902 label DailySet105 (active tape)
amcheck-server: slot 6: date 20030902 label DailySet106 (active tape)
amcheck-server: slot 7: date 20030909 label DailySet107 (active tape)
amcheck-server: slot 8: date 20030909 label DailySet108 (active tape)
amcheck-server: slot 9: date 20030927 label DailySet109 (active tape)
amcheck-server: slot 10: date 20030927 label DailySet110 (active tape)
amcheck-server: slot 11: date 20030927 label DailySet111 (active tape)
amcheck-server: slot 12: date 20030928 label DailySet112 (active tape)
NOTE: skipping tape-writable test
Tape DailySet101 label ok
NOTE: info dir /var/lib/amanda/DailySet1/curinfo/192.168.8.18: does not
exist
NOTE: index dir /var/lib/amanda/DailySet1/index/192.168.8.18: does not exist
Server check took 2.048 seconds
Amanda Backup Client Hosts Check
--------------------------------
WARNING: 192.168.8.18: selfcheck request timed out. Host
down?<-########couldn't find remote client
Client check: 1 host checked in 29.995 seconds, 1 problem found
(brought to you by Amanda 2.4.4p1)
Appreciated for your answer!
Another thing:
when I tried to mount 192.168.8.18:/home/eec013 (a directory in
192.168.8.18, that is , in the remote amanda client) to 192.168.8.12:
/mnt/backup(a directory in 192.168.8.12, that is, in amanda server)
, I typed the following command:
[root@cai root]# mount 192.168.8.18:/home/eec013 /mnt/backup
but the system told me :
mount: RPC: Remote system error - Connection refused
Must I set something in 192.168.8.18 to let the remote client (192.168.8.18)
permit the server's(192.168.8.12) entry?Then how?
thanks!
A Chinese Student From Mainland
_________________________________________________________________
Share your photos without swamping your Inbox. Get Hotmail Extra Storage
today! http://join.msn.com/?PAGE=features/es
| 