Troubleshooting the Remote Media Agent for Linux
If there are issues with Remote Media Agent for Linux, review the following questions and answers.
Related information
Table: Troubleshooting the RMAL
| Question | Answer |
|---|---|
| Remote Media Agent for Linux does not detect my attached device. What should I do? | First, ensure that Backup Exec and the Remote Media Agent for Linux support the device. |
| You can find a list of compatible devices at the following URL: | |
| http://www.veritas.com/docs/000017788 | |
| If the device is listed on the hardware compatibility list, ensure the following: | |
| - The operating system detects the device | |
| - The device is listed in /proc/scsi/scsi | |
| If the operating system can detect the device, ensure that the device is listed in /etc/VRTSralus/TILDBG.TXT. | |
| My Backup Exec server does not display the devices that are attached to my Remote Media Agent. What should I do? | Try the following procedures\: |
| - Ensure that the Agent for Linux daemon is running. If it is not running, start the daemon, and check that power for the server is enabled, and that all cables are properly attached. | |
| - Ensure that the Remote Media Agent for Linux properties are set to the correct port, and that ICMP ping operations are enabled. | |
| - Ensure that the Backup Exec services are restarted after a Remote Media Agent is added to the Backup Exec server. The available devices should be displayed under the Remote Media Agent for the Linux node. | |
| See Editing properties for the Remote Media Agent for Linux . | |
| See Starting the Agent for Linux daemon . | |
| Why don't my remote devices appear in any of the storage device pools that are created by Backup Exec? | By default, Backup Exec does not include remote devices in the storage device pools it creates. Veritas recommends that you create a separate storage device pool for the devices that are attached to each Remote Media Agent. |
| See About creating storage device pools for devices attached to the Remote Media Agent for Linux . | |
| Remote Media Agent for Linux won't run on the remote computer. What should I do? | Ensure that the Remote Media Agent for Linux is installed on a supported version of Linux. |
| You can find a list of compatible operating systems, platforms, and applications at the following URL: | |
| http://www.veritas.com/docs/000017788 | |
| If you install the Remote Media Agent for Linux to an unsupported version of Linux, the Remote Media Agent for Linux is unavailable for use. You cannot create the jobs that run on the devices that are attached to the Linux server. However, you can back up the Linux server by using the Agent for Linux component. This component is installed with the Remote Media Agent for Linux. | |
| To use the Agent for Linux component to back up the Linux server, do the following: | |
| - Edit the ralus.cfg file. | |
| - In the string Software\Veritas\Backup Exec for Windows\Backup Exec\Engine\RMAL\DisableRMAL=0, change 0 to 1. See Editing configuration options for Linux computers . See Running the begather utility to troubleshoot Backup Exec components on Linux servers . | |
| I cannot load the Remote Media Agent for Linux. When I attempt to load the Remote Media Agent for Linux in console mode, /beremote --log-console shows the following message\: | This error indicates that the libstdc++.so.5 library is not in the /usr/lib directory. This library is necessary to let the Remote Media Agent for Linux start and function. To resolve this issue, install the libstdc++.so.5 package. You can install this package from the media on which your copy of Linux was provided. Or, you can run the following command from a computer that has Internet access\: |
| Error while loading shared libraries: libstdc++.so.5: cannot open shared object file: No such file or directory. | apt-get install libstdc++5 |
| What should I do? | For SUSE Linux Enterprise Server 11, run the following command: |
zypper install libstdc++5 |