How to run the Backup Exec RALUS (Remote Agent for Linux or Unix Servers) in debug mode

Article:TECH35477  |  Created: 2004-01-17  |  Updated: 2013-04-08  |  Article URL http://www.symantec.com/docs/TECH35477
Article Type
Technical Solution


Subject

Issue



How to run the Backup Exec RALUS (Remote Agent for Linux or Unix Servers) in debug mode.


Solution



The Backup Exec Remote Agent for Linux or UNIX Servers (RALUS) can be started in debug mode to create a log file of its operations. The following commands must be executed while the user is logged on as root.
Note: Be aware that UNIX and the MAC OS X console are case and space sensitive.
Stopping RALUS
The VRTSralus.init file can be used to stop the agent as shown in Figure 1.
 
Figure 1
 
   
Viewing various debug options for RALUS
At the command prompt (#) browse to the directory /opt/VRTSralus/bin.
Type the command ./beremote --help which will display all debug options (Figure 2)
 
Figure 2
 
 
Logging debug information to the console
Type the command ./beremote --log-console &  to start the agent in the debug mode and display all debug information on the console (Figure 3).
 
Figure 3
 
 
Logging the debug information to a file
Type the command ./beremote --log-file <file name> &  to start the Agent in the debug mode and log all debug output to a file which will be created in the current directory. As shown in Figure 4, the agent has been started in debug mode to log all debug output to a file called ralusdebug.
 
Figure 4
 
 
Logging the debug information to the console and a file simultaneously
Type the command ./beremote --log-console --log-file <file name> &  to start the Agent in the debug mode and log all debug output to the console and to a file.
 
Viewing the debug output
Type the command vi <file name> to view the debug output (Figure 5).
 
Figure 5
 
 
Increasing the logging level
In some cases, particularly when diagnosing connection issues, it may be necessary to increase the detail of the log file.  This can be done by editing the /etc/VRTSralus/ralus.cfg file and changing the Software\Symantec\Backup Exec for Windows\Backup Exec\Engine\Logging\RANT NDMP Debug Level setting from zero to two.  Please be aware that this greatly increases the size of the debug logs and should be reset to zero after the debug logging session has completed.
When this setting is used, it is typically useful to increase the same setting on the Backup Exec Media Server's sgmon logging tool.  This is done in sgmon by going to the Tools/Settings menu.  Then select the "Job Engine & Remote Agent" setting in the right hand pane of the window.  Then change the Engine NDMP debug level and Remote Agent NDMP debug level to the "Verbose logging" setting.  Again, this greatly increases the size of the debug logs at the media server and should be reset to the default of Log NDMP errors after the debug logging session has completed.
Note:
Please see http://www.symantec.com/docs/TECH56024 if more detailed logging of the VxMS filesystem has been requested.
Note:
If RALUS is installed on a Linux system, running the /opt/VRTSralus/bin/bediag utility creates the bediag.fax file which is useful in logging the system environment.  The bediag.fax file should be included when working with Symantec Technical Support on RALUS issues.



Legacy ID



272988


Article URL http://www.symantec.com/docs/TECH35477


Terms of use for this information are found in Legal Notices