Re: [gentoo-user] how to amrecover in amanda-2.6.0
John Blinka schrieb: On Sat, Jul 18, 2009 at 5:42 AM, Stefan G. Weichingerli...@xunil.at wrote: Didn't the binary-paths change with 2.6 ? Yes. Check if /usr/libexec/amanda/amandad exists and adjust the xinetd-entry if necessary. Did that. The binaries exist and xinetd entries point correctly. (Sorry for the very long delay in replying. My backup machine's root partition disk started failing, and it has taken me a long time to rebuild things.) Sorry to hear. Maybe you should post your issues to the amanda-users mailing list. Some of the devs read it and may be able to help you quickly. Stefan
[RESOLVED] Re: [gentoo-user] how to amrecover in amanda-2.6.0
I'm not exactly sure what I've done to fix things, but backups and
amrecovers are now working properly.
For the record, on the backup server, the /etc/xinetd.d/amanda file contains:
service amanda
{
socket_type = dgram
protocol= udp
wait= yes
user= amanda
group = amanda
groups = yes
server = /usr/libexec/amanda/amandad
server_args = amdump amindexd amidxtaped
only_from = 192.168.1.0
disable = no
log_type= SYSLOG daemon debug
}
and, again on the backup server, the /etc/amanda/amandahosts file contains:
# Machine-name for those hosts which are permitted to back up (fully-qualified
# is best). An entry in /etc/hosts adds fail-safe against DNS death :-)
# |
# | permitted user-name
# | |
server amanda amdump
server root amindexd amidxtaped
client root amindexd amidxtaped
On the backup client, the /etc/xinetd.d/amanda file is identical to
the server's.
On the backup client, the /etc/amanda/amandahosts file contains:
# vim: ts=4 sts=4 sw=4 noexpandtab:
# Machine-name for those hosts which are permitted to back up (fully-qualified
# is best). An entry in /etc/hosts adds fail-safe against DNS death :-)
# |
# | permitted user-name
# | |
client amanda amdump
server amanda amdump
client root amindexd amidxtaped
I used the fqdn for the client and server names in the above files.
John Blinka
Re: [gentoo-user] how to amrecover in amanda-2.6.0
On Sat, Jul 18, 2009 at 5:42 AM, Stefan G. Weichingerli...@xunil.at wrote: Didn't the binary-paths change with 2.6 ? Yes. Check if /usr/libexec/amanda/amandad exists and adjust the xinetd-entry if necessary. Did that. The binaries exist and xinetd entries point correctly. (Sorry for the very long delay in replying. My backup machine's root partition disk started failing, and it has taken me a long time to rebuild things.) John
Re: [gentoo-user] how to amrecover in amanda-2.6.0
John Blinka schrieb: On Thu, Jul 16, 2009 at 2:32 AM, Stefan G. Weichingerli...@xunil.at wrote: Try amoldrecover for a start ... From what I understand, amoldrecover is for recovering files on a =2.5 client from a 2.5 server. My server and clients are all =2.6. Am I misunderstanding? hmm, no ... you're right ... Didn't the binary-paths change with 2.6 ? Check if /usr/libexec/amanda/amandad exists and adjust the xinetd-entry if necessary. S
Re: [gentoo-user] how to amrecover in amanda-2.6.0
On Thu, Jul 16, 2009 at 2:32 AM, Stefan G. Weichingerli...@xunil.at wrote: Try amoldrecover for a start ... From what I understand, amoldrecover is for recovering files on a =2.5 client from a 2.5 server. My server and clients are all =2.6. Am I misunderstanding? John
Re: [gentoo-user] how to amrecover in amanda-2.6.0
John Blinka schrieb: Running amrecover -C my_host -t my_host -s my_host -d file:/backup/my_host/vtapes produces a pause of about 30 seconds then the following output: AMRECOVER Version 2.6.0p2. Contacting server on my_host ... [request failed: timeout waiting for ACK] /var/log/messages contains nothing enlightening. Neither does /var/amanda/my_host/log.* Thanks for any ideas on how to debug this! Try amoldrecover for a start ... Stefan
[gentoo-user] how to amrecover in amanda-2.6.0
Hi, all,
I recently upgraded from amanda-2.4.5 to amanda-2.6.0_p2-r4. I think
I've been able to make backups
successfully: the backup reports amanda sends afterwards look
reasonable. However, I've not been able
to do restores. It appears that the contents of
/etc/amanda/amandahosts and /etc/xinetd.d/amanda have
changed between these two versions, and I suspect that my attempts at
updating the contents are at
fault.
My 2.4.5 amandahosts file looked like this:
my_host.my_domain amanda
my_host.my_domain root
and the 2.6.0_p2-r4 amandahosts looks like:
my_host.my_domain amanda amdump
my_host.my_domain root amindexd amidxtaped
My 2.4.5 amanda file looked like this:
service amanda
{
socket_type = dgram
protocol= udp
wait= yes
user= amanda
group = amanda
groups = yes
server = /usr/libexec/amanda/amandad
only_from = 192.168.1.0
disable = no
}
service amandaidx
{
socket_type = stream
protocol= tcp
wait= no
user= amanda
group = amanda
groups = yes
server = /usr/libexec/amanda/amindexd
only_from = 192.168.1.0
disable = no
}
service amidxtape
{
socket_type = stream
protocol= tcp
wait= no
user= amanda
group = amanda
groups = yes
server = /usr/libexec/amanda/amidxtaped
only_from = 192.168.1.0
disable = no
}
and my 2.6.0_p2-r4 amanda file looks like:
service amanda
{
disable = no
flags = IPv4
socket_type = stream
protocol= tcp
wait= no
user= amanda
group = amanda
groups = yes
server = /usr/libexec/amanda/amandad
server_args = -auth=bsdtcp amdump amindexd amidxtaped
}
The above was taken from
/usr/share/doc/amanda-2.6.0_p2-r4/example/xinetd.amandaserver.bz2.
A run of amcheck shows no errors.
Running su -c /usr/sbin/amadmin my_host find amanda produces the
expected output.
Running amrecover -C my_host -t my_host -s my_host -d
file:/backup/my_host/vtapes
produces a pause of about 30 seconds then the following output:
AMRECOVER Version 2.6.0p2. Contacting server on my_host ...
[request failed: timeout waiting for ACK]
/var/log/messages contains nothing enlightening. Neither does
/var/amanda/my_host/log.*
Thanks for any ideas on how to debug this!
John Blinka
