Common Agent Start and Stop Status
Whenever a client agent is started or stopped, the UNIX, Linux, or Mac OS X system scripts modify the agent.cfg file by marking the client agent entry in the file as enabled or disabled. The scripts also notify the Common Agent of the change. The Common Agent then determines whether to continue running, depending on the number of entries in the configuration file that are still enabled.
For example, issuing uagent stop for a UNIX client marks the ABagntux section disabled. If ABagntux is the only section of the file (that is, there is only one Arcserve Backup client agent installed), the Common Agent stops. You would then need to issue uagent start to enable the ABagntux section of the agent.cfg file.
When you enter the uagent start command, the Common Agent status changes from disabled to enabled. In summary, when a particular client agent is started or stopped, the scripts modify the agent.cfg file accordingly, and notify the Common Agent. At that point, the Common Agent decides whether to continue running, depending on the number of sections in the configuration file that are still enabled.
|
Copyright © 2016
|
|