Arcserve Backup Cannot Detect Devices Attached to Data Mover Servers

Valid on UNIX and Linux platforms.

Symptom

From the Backup Manager, Destination tab, and the Device Manager, Arcserve Backup cannot detect devices attached to data mover servers.

Solution

To troubleshoot this problem, complete the following steps:

  1. Ensure that the shared devices can be accessed from the primary server and the data mover server.
  2. Ensure that the UNIX or Linux operating system running on the data mover server can access and operate the device.
  3. Example: Linux platforms, check the devices from the following:

    4. /proc/scsi/scsi

  4. From the primary server, ensure that the device detection process completed successfully. To do this, open the following log file on the primary server:

    5. <ARCSERVE_HOME>/log/tape.log

  5. If the device detection process completed successfully, information similar to the following appears in the Primary Server tape.log file:

    6. [09/24 13:07:48 11e0 2 ] Connecting to Node UNIX-DM-01-SLES11-V1 on Port 6051

    [09/24 13:07:49 11e0 2 ] Registering Node : UNIX-DM-01-SLES11-V1

    [09/24 13:07:49 11e0 2 ] Detecting Tape devices...

    [09/24 13:07:50 11e0 2 ] Detected 12 tape drives...

    [09/24 13:07:50 11e0 2 ] Tape Drive STK 9840 1.00

    [09/24 13:07:50 11e0 2 ] b7285ec31 - Prototype: Prototype

    [09/24 13:07:50 11e0 2 ] Find a tape drive, logical Device Name set to [SCSI:b7285ec31]

  6. From the data mover server, execute the following command to ensure that the NDMP server service is running:

    7. # ps -ef | grep NDMPServer

  7. If the NDMP Server service is running, the following results appear in the command line:

    8. root 13260 1 0 05:28 ? 00:00:00 NDMPServer

    root 13484 1 0 05:28 ? 00:00:00 NDMPServer

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

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

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

    10. 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

  10. From the data mover server, open 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:

    11. /opt/Arcserve/ABcmagt/agent.cfg

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

    12. [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

  12. From the data mover server, ensure that Arcserve Backup can detect all of the devices that are accessible to the data mover server. Arcserve Backup creates links to the detected devices in the following directory:

    13. /dev/Arcserve

  13. If there are no links in /dev/ca and you are sure that the data mover server can detect the devices, execute the following script on the data mover server:

    14. /opt/Arcserve/ABdatamover/ScanDevices.sh

  14. Example:
  15. The following example illustrates links to all of the detected devices on a Linux-based data mover server:

    16. UNIX-DM-01-SLES11-V1 /]# ls -l /dev/Arcserve

    total 4

    drwxrwxrwx 2 root root 320 Sep 24 12:58 .

    drwxr-xr-x 13 root root 6060 Sep 23 15:43 ..

    -rw-rw-rw- 1 root root 515 Sep 24 12:58 DeviceSerialMap

    lrwxrwxrwx 1 root root 8 Sep 24 12:58 lib:4,0,0,0 -> /dev/sg1

    lrwxrwxrwx 1 root root 8 Sep 24 12:58 tape:4,0,0,1 -> /dev/sg2

    lrwxrwxrwx 1 root root 9 Sep 24 12:58 tape:4,0,0,10 -> /dev/sg11

    lrwxrwxrwx 1 root root 9 Sep 24 12:58 tape:4,0,0,11 -> /dev/sg12

    lrwxrwxrwx 1 root root 9 Sep 24 12:58 tape:4,0,0,12 -> /dev/sg13

    lrwxrwxrwx 1 root root 8 Sep 24 12:58 tape:4,0,0,2 -> /dev/sg3

    lrwxrwxrwx 1 root root 8 Sep 24 12:58 tape:4,0,0,3 -> /dev/sg4

    lrwxrwxrwx 1 root root 8 Sep 24 12:58 tape:4,0,0,4 -> /dev/sg5

    lrwxrwxrwx 1 root root 8 Sep 24 12:58 tape:4,0,0,5 -> /dev/sg6

    lrwxrwxrwx 1 root root 8 Sep 24 12:58 tape:4,0,0,6 -> /dev/sg7

    lrwxrwxrwx 1 root root 8 Sep 24 12:58 tape:4,0,0,7 -> /dev/sg8

    lrwxrwxrwx 1 root root 8 Sep 24 12:58 tape:4,0,0,8 -> /dev/sg9

    lrwxrwxrwx 1 root root 9 Sep 24 12:58 tape:4,0,0,9 -> /dev/sg10

  16. From the data mover server, open the NDMP Server Log file to ensure that the NDMP Server service is communicating with the devices. The log file is stored in the following directory:

    17. /opt/Arcserve/ABdatamover/logs/NDMPServer.log

  17. Messages similar to the following should appear in the log file:

    18. 20/11/2009 19:39:54.946 27897 INF [0x4004AAE0] Received Message NDMP_CONFIG_GET_TAPE_INFO

    20/11/2009 19:40:23.626 27897 INF

    20/11/2009 19:40:23.626 27897 INF Found [3] devices...

    20/11/2009 19:40:23.630 27897 INF

    20/11/2009 19:40:23.630 27897 INF Found tape drive [9210803477]

    20/11/2009 19:40:23.657 27897 INF

    20/11/2009 19:40:23.657 27897 INF Found tape drive [9210801539]

    20/11/2009 19:40:23.676 27897 INF [0x4004AAE0] Sending NDMP_CONFIG_GET_TAPE_INFO