Legato NetWorker Commands Index:ansrd
* - Windows Only
hagentdhagentd - Host Agent server daemon
hagentd [ -D debug level ] [ -l log file ]
The hagentd program is the server daemon for the Legato Host Agent product. hagentd should be started on the Host Agent Server host once the nsrex- ecd and nsrd processes have been started. The server's configuration is stored in Host Agent's own RAP database, ha_srv_db.res, which will be located in the same directory as the Net- Worker RAP databases - typically /nsr/res
-D debug_level Run hagentd in a mode which causes debug information to be printed out. This option should only be used if Legato Techni- cal Support asks you to do so. The debug_level argument controls the verbosity of debug output - higher values cause more ver- bose output. Note that running in debug mode will additionally have the fol- lowing effects: (1) hagentd will stay in the foreground rather than daemonize itself. (2) Any output from hagentd will default to stdout / stderr (instead of the application log file) unless specifically over- ridden by a -l <file_name> directive appearing after the -D directive. -l log_file Allows you to specify the name of the file that hagentd will write logging information to. Normally, logging information will go to stdout / stderr if hagentd is run in debug mode, and to a default log file if not in debug mode. The default log file will be named hagentd.log, and will be located in the applogs subdi- rectory of your NetWorker installation directory.
The hagentd daemon maintains the RAP database which contains the con- figuration information for all Host Agent Clients being managed by this server, as well as all of the data collected by those clients and sub- mitted to the server (either automatically or manually) by means of the hasubmit program. for example: nsradmin -s <server_name> -p hagentd or nsradmin -s <server_name> -p 390427
Administration of the Host Agent Server may be done via nsradmin, only while the hagentd process is running. Administration is achieved by defining a number of RAP resources, as explained below: A Host Agent Client resource must be defined for every Host Agent Client that will be administered by this Host Agent Server. The primary purposes of this resource are to (i) allow clients to be enabled or disabled individually, and (ii) to make an association between a client name and a Host Agent "administration group" name. The purpose of the administration group name will become clear once the Host Agent Client Module resource is studied. A Host Agent Client Module is an executable program of some sort which may be run on a Host Agent Client in order to collect information about a particular aspect of that client. For instance, the hascsi Client Module discovers information about SCSI devices that the Host Agent Client can access. A Host Agent Client Module resource is used to define when a given Host Agent Client Module will be run on a given host, and when the results that that Client Module has collected and stored in its client-side NSRLA RAP database will be forwarded to the Host Agent Server for stor- age in the centralized Host Agent Server's RAP database. Note that no client host name is used in defining this resource - instead, an administration group name is used. Any Host Agent Client resources which defined their client as being in this administration group will now run this Client Module according to this schedule. In this way, a single Host Agent Client Module definition may be created or changed to control the way that a whole group of clients operate. The Host Agent Client Module resource also references two schedules - one for data collection, one for data submission. The collection sched- ule defines when the Client Module will be run on the client; the sub- mission schedule defines when that data will be forwarded from the client to the Host Agent Server. The schedule names in this resource are available only in terms of a selection of currently defined sched- ules, so you should either use the default schedule, or define your own schedules before defining the Host Agent Client Module resources. The data submission policy attribute indicates what should happen at the server side when the client submits new data to it. Replace means that each time the client does a data submission, all old data for that A Host Agent Schedule resource defines the data collection or submis- sion schedules as noted above. It will ultimately include detailed scheduling capabilities, but will initially allow only a repetition frequency to be defined. This means that (i) Initial data collection will happen as soon as nsrexecd comes up on the Host Agent Clients; (ii) Initial data submission will be requested by the Host Agent Server as soon as hagentd comes up on the Host Agent Server; (iii) both data collection and data submission will subsequently be repeated according to the values used in their Host Agent Schedule resources. Each Host Agent Client will obtain a copy of the above resources, for defining the client, client module, and schedule information for that client only. In this way, the Host Agent Client may continue to operate while offline. The copying from the server to the client will be done by hagetconf and will be initiated automatically by the server. The Host Agent Master resource allows you to control the data lifetime of the collected client data that is stored in the server's RAP database. The pruning frequency attributes control how often the haprune utility is fired off to clean up old data in the RAP database. The data lifetime attributes indicate what the threshold is for the pruning utility to decide whether to delete or leave each data resource instance in the database. Note that this data lifetime control is in addition to the Replace / Add data submission policy that applies in each Host Agent Client Mod- ule resource.
COLLECTED DATA RESOURCES
A number of dynamically defined resource types will be generated by Host Agent, for the purpose of storing the data that the Host Agent Clients collect and then forward to the server. One resource type is generated for each active Host Agent Client Mod- ule, and the content and type name of that resource type is defined within a Host Agent Schema File - for instance, for the hasys Client Module, a "system information" data resource type is created based on the contents of the hasys.sch schema file. Instances of this resource type are created on the Host Agent Clients according to the selected collection schedule, and are then forwarded to the Host Agent Server according to the selected submission schedule. The lifetime of these collected data resources may be managed by means of the Host Agent Master administration resource described earlier in this manual page.
hagentd will only come partially up until nsrexecd is running on the server system.
hagetconf(1) hasubmit(1) hadump(1) haprune(1) hasys(1) hascsi(1) hafs(1) nsradmin(1)
ADVERTISEMENTLegato NetWorker 7.x
Man(1) output converted with man2html, sed, awk