Troubleshooting the Remote Media Agent for Linux Servers

If there are issues with the Remote Media Agent, review the following questions and answers.

Table: Troubleshooting the Remote Media Agent for Linux Servers

Question

Answer

The Remote Media Agent does not detect my attached device. What should I do?

First, ensure that Backup Exec and the Remote Media Agent for Linux Servers support the device.

You can find a list of compatible devices at the following URL:

http://entsupport.symantec.com/umi/V-269-2

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 media 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 Remote Agent for Linux or UNIX Servers 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 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 media server. The available devices should be displayed under the Remote Media Agent node.

See Editing properties for the Remote Media Agent for Linux Servers .

See Starting the Remote Agent for Linux or UNIX Servers daemon.

Why don’t my remote devices appear in the All Devices device pools?

By default, Backup Exec does not include remote devices in the All Devices device pool. Symantec recommends that you create a separate device pool for the devices that are attached to each Remote Media Agent.

See About creating device pools for devices attached to the Remote Media Agent for Linux Servers .

The Remote Media Agent won’t run on the remote computer. What should I do?

Ensure that the Remote Media Agent 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://entsupport.symantec.com/umi/V-269-1

If you install the Remote Media Agent to an unsupported version of Linux, the Remote Media Agent 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 Remote Agent for Linux or UNIX Servers component. This component is installed with the Remote Media Agent.

To use the Remote Agent for Linux or UNIX Servers component to back up the Linux server, do the following:

I cannot load the Remote Media Agent. When I attempt to load the Remote Media Agent in console mode, /beremote –log-console shows the following message:

Error while loading shared libraries: libstdc++.so.5: cannot open shared object file: No such file or directory.

What should I do?

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 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:

apt-get install libstdc++5

For SUSE Linux Enterprise Server 11, run the following command:

zypper install libstdc++5

Troubleshooting the Remote Media Agent for Linux Servers