amservice(8) [debian man page]
AMSERVICE(8) System Administration Commands AMSERVICE(8) NAME
amservice - run an amanda service on a client SYNOPSIS
amservice [-f input_file [-s]] [-o configoption...] hostname auth service DESCRIPTION
Amservice execute an Amanda service on a client. It can be used without amanda server configuration (amanda.conf and disklist). It can be used to check communication between a server and a client. Amservice reads stdin to capture the REQ packet to send to the client. See the amanda(8) man page for more details about Amanda. OPTIONS
hostname The hostname of the client. auth The auth to use, one of: bsd, bsdudp, bsdtcp, ssh, rsh or krb5. The client must be configured with this auth. service The amanda service to execute on the client. One of noop, selfcheck or sendsize. -f input_file Use the file input_file instead of stdin to read the REQ packet from. -s Redirect the first connected stream to stdin/stdout. The -f argument is required for the REQ packet, the REP packet is not printed on stdout. -o configoption See the "CONFIGURATION OVERRIDE" section in amanda(8). EXAMPLE
The noop service is easy to execute because it does not require a REQ packet: amservice hostname bsdtcp noop < /dev/null The example executes the noop service on the client using bsdtcp auth. This is useful for debugging connection problems. It print an OPTIONS line upon success. It is more difficult to execute the selfcheck or sendsize service, as these require a valid REQ packet. If you have already uccessfully run amanda, you can find valid REQ packets in the amandad.*.debug files. EXIT CODE
The exit code of amservice is one of: 0 = success 1 = error executing amandad on the client. As amservice doesn't parse the REP packet, it can only detect failures in executing amandad on the client. amservice can exit with value 0 even if the user is not authorized to execute the service. An error message will be printed. SEE ALSO
amanda(8), amanda(8), amcheck(8), amdump(8), amadmin(8) The Amanda Wiki: : http://wiki.zmanda.com/ AUTHOR
Jean-Louis Martineau <martineau@zmanda.com> Zmanda, Inc. (http://www.zmanda.com) Amanda 3.3.1 02/21/2012 AMSERVICE(8)
Check Out this Related Man Page
AMANDA(8) System Administration Commands AMANDA(8) NAME
amanda - The Open Source Backup Platform DESCRIPTION
This manual page gives an overview of the Amanda commands and configuration files for quick reference. COMMANDS Here are all the Amanda commands. Each one has its own manual page. See them for all the gory details. o amaddclient(8), o amadmin(8), o amaespipe(8), o amarchiver(8), o amcheck(8), o amcheckdb(8), o amcheckdump(8), o amcleanup(8), o amcrypt-ossl-asym(8), o amcrypt-ossl(8), o amcrypt(8), o amcryptsimple(8), o amdevcheck(8), o amdump(8), o amfetchdump(8), o amflush(8), o amgetconf(8), o amgpgcrypt(8), o amgtar(8), o amlabel(8), o amoverview(8), o ampgsql(8), o amplot(8), o amraw(8), o amrecover(8), o amreport(8), o amrestore(8), o amrmtape(8), o amsamba(8), o amserverconfig(8), o amservice(8), o amstar(8), o amstatus(8), o amsuntar(8), o amtape(8), o amtapetype(8), o amtoc(8), o amvault(8), o amzfs-sendrecv(8), o amzfs-snapshot(8), o script-email(8), CONFIGURATION FILES o amanda.conf(5), o amanda-client.conf(5), o disklist(5), o tapelist(5), DATA FORMATS o amanda-archive-format(5), CONCEPTS o amanda-applications(7), o amanda-auth(7), o amanda-changers(7), o amanda-compatibility(7), o amanda-devices(7), o amanda-interactivity(7), o amanda-match(7), o amanda-scripts(7), o amanda-taperscan(7), CONFIGURATION FILES
There are four user-editable files that control the behavior of Amanda. The first two are amanda.conf(5) and amanda-client.conf(5), the main configuration files for the server and client, respectively. They contain parameters to customize Amanda for the site. Next is the disklist(5) file, which lists hosts and disk partitions to back up. Last is the seldom-edited tapelist(5) file, which lists tapes that are currently active. These files are described in more detail in the following sections. All configuration files are stored in individual configuration directories, usually under /etc/amanda/. A site will often have more than one configuration. For example, it might have a normal configuration for everyday backups and an archive configuration for infrequent full archival backups. The configuration files would be stored under directories /etc/amanda/normal/ and /etc/amanda/archive/, respectively. Part of the job of an Amanda administrator is to create, populate and maintain these directories. Most Amanda applications take a "config" parameter; this is generally the (unqualified) name of the configuration directory, e.g., normal. If the parameter is . (dot), the current directory is used. This feature is present for backward compatibility, but is not commonly used. Configuration Override Most commands allow the override of specific configuration options on the command line, using the -o option. This option has the form -oname=value. An optional space is allowed after the -o. Each configuration option should be specified in a separate command-line option. For global options, name is simply the name of the option, e.g., amdump -oruntapes=2 For options in a named section of the configuration, name has the form SECTION:section_name:name, where SECTION is one of TAPETYPE, DUMPTYPE, HOLDINGDISK, or INTERFACE, and section_name is the name of the tapetype, dumptype, holdingdisk, or interface. Examples: amdump -o TAPETYPE:HP-DAT:length=2000m amdump -o DUMPTYPE:no-compress:compress="server fast" amdump -o HOLDINGDISK:hd1:use="-100 mb" amdump -o INTERFACE:local:use="2000 kbps" When overriding device properties, one must carefully quote the command line to simulate the syntax of real configuration files. The following example should serve as a guide: amdump -o 'device-property="PROPERTY_MAX_VOLUME_USAGE" "100000"' Note that configuration overrides are not effective for tape changers, which supply a tapedev based on their own configuration. In order to override tapedev, you must also disable any changer: amdump -otapedev=/dev/nst1 -otpchanger='' AUTHORS
James da Silva <jds@amanda.org> Stefan G. Weichinger <sgw@amanda.org> Amanda 3.3.1 02/21/2012 AMANDA(8)