On 09/12/16 12:24 PM, Jon LaBadie wrote:
On Fri, Dec 09, 2016 at 09:48:17AM +0100, Heiko Schlittermann wrote:
Hello,
Jon LaBadie <[email protected]> (Do 08 Dez 2016 19:36:07 CET):
Is amservice a client-side program or server-side?
In Fedora packages it does not come in with the client package.
Playing with amanda_client I get this error:
amdump_client: open3: exec of /usr/sbin/amservice -f /dev/null \
-s amandahost bsdtcp amdumpd \
failed at /usr/sbin/amdump_client line 85.
"failed exec" Makes it sound like amdump_client is expecting
amservice on the client.
As far as I understand this (I may be wrong!), amdump_client just
*triggers* the backup, so the backup server needs to connect to the
backup client (amservice) to pull the backup. amdump_client doesn't push
the backup. That's what I understood 'ambackup' is for (available in
newer Amandas).
amdump_client triggers "how". Does it contact the server? What process
and port is listening on the server? Or does it initiate a local dump
that is stored locally?
Assuming amdump_client notifies the server it would like to be dumped,
the server could do "amdump --no-taper <CONFIG> <HOST> [disks]". I do
not see why a different mechanism involving amservice would be needed.
Obviously I'm missing something.
Jon
amdump_client use amservice to connect to the amdumpd service on the server.
The amdumpd service must be enable on the server.
The mechanism to enable it depend of the auth
- bsdtcp (xinetd, .amandahosts), the amanda default port (10080)
Jean-Louis
