Computer Associates BABWBN2900E20 Clients Agents Guide - Page 65

Check the Status of the UNIX, Linux, and Mac OS X Client Agents

Get Computer Associates BABWBN2900E20 - BRIGHTSTOR ARC BACKUP V9 CLIENT PDF manuals and user guides
UPC - 757943261059
View all Computer Associates BABWBN2900E20 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 65 highlights

Client Agent Start and Stop Procedures 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. Check the Status of the UNIX, Linux, and Mac OS X Client Agents To check the status of a UNIX, Linux, or Mac OS X client agent, log in as root and issue the following command at the command line: # uagent status If this command fails, the client agent may need to be configured. To configure the client agent, run the following script: #abuagent/uagentsetup In this example, abuagent represents the full path name of the agent home directory. The default path is /opt/CA/ABuagent. Enterprise Option for AS/400 Start and Stop Requirement You must have *JOBCTL (job control) authority to start or stop the client agent. Start the Client Agent for Enterprise Option for AS/400 To start the agent, log on to AS/400 and issue the following command at the command line: straso Stop the Client Agent for Enterprise Option for AS/400 To stop the agent, log on to AS/400 and issue the following command at the command line: endaso Enterprise Option for OpenVMS Start and Stop Requirement Ensure that you have the appropriate network credentials to operate the OpenVMS machine on which the client agent resides. Chapter 4: Using the Client Agents 65

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
Client Agent Start and Stop Procedures
Chapter 4: Using the Client Agents
65
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.
Check the Status of the UNIX, Linux, and Mac OS X Client Agents
To check the status of a UNIX, Linux, or Mac OS X client agent, log in as root and
issue the following command at the command line:
# uagent status
If this command fails, the client agent may need to be configured. To configure
the client agent, run the following script:
#
abuagent
/uagentsetup
In this example,
abuagent
represents the full path name of the agent home
directory. The default path is /opt/CA/ABuagent.
Enterprise Option for AS/400 Start and Stop Requirement
You must have *JOBCTL (job control) authority to start or stop the client agent.
Start the Client Agent for Enterprise Option for AS/400
To start the agent, log on to AS/400 and issue the following command at the
command line:
straso
Stop the Client Agent for Enterprise Option for AS/400
To stop the agent, log on to AS/400 and issue the following command at the
command line:
endaso
Enterprise Option for OpenVMS Start and Stop Requirement
Ensure that you have the appropriate network credentials to operate the
OpenVMS machine on which the client agent resides.