Arcserve Backup Cannot Detect Data Mover Servers

Introducing Arcserve Backup Agents and Options › Using Options › Arcserve Backup UNIX and Linux Data Mover › Troubleshooting › Arcserve Backup Cannot Detect Data Mover Servers

Arcserve Backup Cannot Detect Data Mover Servers

Valid on UNIX and Linux platforms.

Symptom

Arcserve Backup cannot detect data mover servers and the data mover servers are registered with the primary server.

Solution

To troubleshoot this problem, complete the following steps:

Ensure that the data mover server is registered to the primary server.
Ensure that the Tape Engine on the primary server is running.

Ensure that the Tape Engine on the primary server is communicating with the data mover server. To check the communication, open the following log:

<ARCSERVE_HOME>/log/tape.log

The tape.log file should display information that is similar to the following:

[09/24 13:07:34 11e0  2             ] -----------START LOGGING---------
[09/24 13:07:34 11e0  2             ] Loading Server and Device List 
[09/24 13:07:34 11e0  2             ] Successfully Get UUID on [UNIX-DM-01-SLES11-V1] 
[09/24 13:07:34 11e0  2             ] Successfully Get UUID on [UNIX-DM-02-RHEL5-P2] 
[09/24 13:07:34 11e0  2             ] Successfully Get UUID on [172.24.199.299] 
[09/24 13:07:34 11e0  2             ] Initializing Servers and Devices : Start  
[09/24 13:07:34 11e0  2             ] Connecting to Node UNIX-DM-01-SLES11-V1 on Port 6051

Verify the following:

The data mover server appears in the tape.log file. For example:
```
Successfully Get UUID on [UNIX-DM-01-SLES11-V1]
```
The primary server is communicating with the data mover server. For example:
```
Connecting to Node UNIX-DM-01-SLES11-V1 on Port 6051
```

Review the following log file:

<ARCSERVE_HOME>/log/umsdev.log

The log file should contain information that is similar to the following:

25/11/2009 19:01:55.849  5340 DBG CNDMPConnection using Hostname=UNIX-DM-01-SLES11-V1, IPAddress=, PortNumber=6051
25/11/2009 19:01:55.943  5340 DBG CXDRStream::CXDRStream
25/11/2009 19:01:55.943  2384 DBG [0x00F35C20] Message receive thread started
25/11/2009 19:01:55.943  3696 DBG Dispatch Thread started

Ensure that the IP address of the data mover server appears in the hosts file on the primary server. The hosts file is located in the following directory:
```
<Windows>/system32/drivers/etc/hosts
```
For example:
```
172.24.199.199	UNIX-DM-01-SLES11-V1
```
From the primary server, execute the ping command or the nslookup command to ensure that the primary server can communicate with the data mover server.
From the data mover server, execute the ping command or the nslookup command to ensure that the data mover server can communicate with the primary server.
Note: If the servers cannot communicate using ping or nslookup, ensure that you are specifying the correct host name, IP address, or both.
From the data mover server, execute the following command to ensure that the NDMP server service is running:
```
# ps -ef | grep NDMPServer
```
If the NDMP Server service is running, the following results appear in the command line:
```
root     13260     1  0 05:28 ?        00:00:00 NDMPServer
root     13484     1  0 05:28 ?        00:00:00 NDMPServer
```

From the data mover server, open the Common Agent log to ensure that the NDMP server service started. The Common Agent log file is stored in the following directory:

/opt/Arcserve/ABcmagt/logs/caagentd.log

If the NDMP Server service started, the following information appears in the log file:

10/21 05:28:51(13259) - (_AGBRSpawnMediaEngine), major=14, minor=0
10/21 05:28:51(13260) - (_AGBRSpawnMediaEngine) execv(/opt/CA/ABdatamover/NDMPServer)
10/21 05:28:51(13259) - (_AGBRSpawnMediaEngine): child pid=13260

From the data mover server, check the Agent.cfg configuration file to ensure that UNIX and Linux Data Mover is configured. The Agent.cfg configuration file is stored in the following directory:

/opt/CA/ABcmagt/agent.cfg

If UNIX and Linux Data Mover is configured, the following information appears in the configuration file:

[260]
#[Data Mover]
NAME      ABdatmov
VERSION   17.0
HOME      /opt/Arcserve/ABdatamover
#ENV      CA_ENV_DEBUG_LEVEL=4
#ENV      CA_ENV_NDMP_LOG_DEBUG=1
ENV AB_OS_TYPE=SUSE_2.6.27.19_I686
ENV       MEDIASERVER_HOME=/opt/Arcserve/ABdatamover
ENV       LD_LIBRARY_PATH=/opt/Arcserve/ABdatamover/lib:/opt/Arcserve/ABcmagt:$LD_LIBRARY_PATH:/opt/Arcserve/SharedComponents/lib
ENV       SHLIB_PATH=/opt/Arcserve/ABdatamover/lib:/opt/Arcserve/ABcmagt:$SHLIB_PATH:/opt/Arcserve/SharedComponents/lib
ENV       LIBPATH=/opt/Arcserve/ABdatamover/lib:/opt/Arcserve/ABcmagt:$LIBPATH:/opt/Arcserve/SharedComponents/lib
BROWSER   NDMPServer
AGENT     dagent