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/xin
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/messa
On Thu, Jul 16, 2009 at 2:32 AM, Stefan G. Weichinger 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
John Blinka schrieb:
> On Thu, Jul 16, 2009 at 2:32 AM, Stefan G. Weichinger 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?
On Sat, Jul 18, 2009 at 5:42 AM, Stefan G. Weichinger 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 lo
John Blinka schrieb:
> On Sat, Jul 18, 2009 at 5:42 AM, Stefan G. Weichinger 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
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
7 matches
Mail list logo
