Forum Discussion

Stivet's avatar
Stivet
Level 4
11 years ago
Solved

NDMP Backup error: ndmp_data_connect_v3 failed

Hi All,

I have a problem with NDMP Remote Backup of NAS: DELL FS8600. When running the backup this error is displayed in ndmpagent log:

 

Connecting and authenticating to NAS server fs_user_rgb.xxxxxxx.edu.coPID:13678 File ID:134
16:05:22.782 Using credentials passed inPID:13678 File ID:134
16:05:22.782 ndmp_open_and_auth_via_host: hostname=fs_user_rgb.xxxxxxx.edu.co, via_hostname=fs_user_rgb.xxxxxxx.edu.coPID:13678 File ID:134
16:05:22.782 ndmp_connect_to_server: hostname = fs_user_rgb.xxxxxxx.edu.co, portname = 10000PID:13678 File ID:134
16:05:23.788 ndmp_authenticate_connection: using NDMP protocol version 4PID:13678 File ID:134
16:05:23.890 EmEventManager::EnableSocketEvent socket 9 type InputPID:13678 File ID:134
16:05:23.891 EmEventManager::EnableSocketEvent socket 9 type ErrorPID:13678 File ID:134
16:05:23.891 TO BRM: INF - VERSION=2PID:13678 File ID:134
16:05:23.903 ndmp_mover_set_window(0, 1073740775424)PID:13678 File ID:134
16:05:23.903 Attempting to create server to which remote host fs_user_rgb.xxxxxxx.edu.co can connect - IPv4PID:13678 File ID:134
16:05:23.903 Using hostname from config file: NDMP_DATA_CONNECTION_HOST_NAME=alcalaPID:13678 File ID:134
16:05:23.904 Using IP address: 157.253.77.49 (for configured host alcala)PID:13678 File ID:134
16:05:23.904 Creating server for 157.253.77.49 in Server Port Window 1025 to 5000PID:13678 File ID:134
16:05:23.905 Listen address = 157.253.77.49 port 2859PID:13678 File ID:134
16:05:23.905 EmEventManager::EnableSocketEvent socket 12 type InputPID:13678 File ID:134
16:08:32.953 ndmp_data_connect failed, status = 23 (NDMP_CONNECT_ERR)PID:13678 File ID:134
16:08:32.953 [Error] ndmp_data_connect_v3 failed, status = -1 (-1)PID:13678 File ID:134
16:08:33.583 ../NdmpBackupManager.cpp(778) - error code 25 (cannot connect on socket)PID:13678 File ID:134

Any idea?

 

7.6
Agents
Backing Up
Backup and Recovery
Linux
NDMP Option
NetBackup
  • mnolan's avatar
    mnolan
    11 years ago

    So first things first, this is either a remote NDMP connecting back to the media server to send data or during other NDMP backups, the meta data. I am guessing the former.

    Per the info "config file: NDMP_DATA_CONNECTION_HOST_NAME=alcala"

    Your ndmp.cfg has the info to tell the filer to come back to ALCALA to send data no matter the actual media server network interface that is talking with the filer for the managment NDMP connection.

    Per the info "Listen address = 157.253.77.49 port 2859"

    ALCALA's IP address is 157.253.77.49 and has an NDMP server listening at port 2859.

    Port 2859 is within the default range for SERVER_PORT_WINDOW, which is 1025-5000, this range is used as random to open a server for other devices to connect to without keeping it at a constant port that can be attacked.

    Per the info "ndmp_data_connect failed, status = 23 (NDMP_CONNECT_ERR)"

    Your filer attempted to connect to 157.253.77.49 port 2859 and failed.

    Please ensure that both software and hardware firewalls allow this filer to connect to that address on the TCP bidirectional port range 1025-5000

     

7 Replies

Sort By
  • RamNagalla's avatar
    RamNagalla
    Moderator
    11 years ago

    Do it have connrect authentication?

    could you check the below command output and see if that is connecting fine or not

    tpautoconf -verify <NDMPhostname>

  • Stivet's avatar
    Stivet
    Level 4
    11 years ago

    This is: tpautoconf -verify <NDMPhostname>

    Connecting to host "fs_user_rgb.xxxxxxxxx.xxx.co" as user "user_NDMP"...
    Waiting for connect notification message...
    Opening session--attempting with NDMP protocol version 4...
    Opening session--successful with NDMP protocol version 4
      host supports TEXT authentication
      host supports MD5 authentication
    Getting MD5 challenge from host...
    Logging in using MD5 method...
    Host info is:
      host name "node0.fs_user_rgb"
      os type "Dell Fluid File System"
      os version "1.3.930714"
      host id "755F7366"
    Login was successful
    Host supports LOCAL backup/restore
    Host supports 3-way backup/restore
     

    and the port 10000 is open bidirectionally. I can do telnet to this port.

    ?

  • Will_Restore's avatar
    Will_Restore
    Level 6
    11 years ago

    NetBackup requirements for Dell FS8600

    TYPE=tar environment variable must be set. TYPE=dump backups are not supported.

  • Stivet's avatar
    Stivet
    Level 4
    11 years ago

    Thanks Will,

    I have set the variable as follows, in the selection list:

    set TYPE=tar

    /NAMEVOLUME

     

    but the error is the same.

  • Marianne's avatar
    Marianne
    Level 6
    11 years ago
    Have another look at NDMP policy. Is the Client name exactly as the name you used in command above to test comms? Did you run the command from the media server specified in the STU? Difficult to try and help when you mask actual names...
  • mnolan's avatar
    mnolan
    Level 6
    11 years ago

    So first things first, this is either a remote NDMP connecting back to the media server to send data or during other NDMP backups, the meta data. I am guessing the former.

    Per the info "config file: NDMP_DATA_CONNECTION_HOST_NAME=alcala"

    Your ndmp.cfg has the info to tell the filer to come back to ALCALA to send data no matter the actual media server network interface that is talking with the filer for the managment NDMP connection.

    Per the info "Listen address = 157.253.77.49 port 2859"

    ALCALA's IP address is 157.253.77.49 and has an NDMP server listening at port 2859.

    Port 2859 is within the default range for SERVER_PORT_WINDOW, which is 1025-5000, this range is used as random to open a server for other devices to connect to without keeping it at a constant port that can be attacked.

    Per the info "ndmp_data_connect failed, status = 23 (NDMP_CONNECT_ERR)"

    Your filer attempted to connect to 157.253.77.49 port 2859 and failed.

    Please ensure that both software and hardware firewalls allow this filer to connect to that address on the TCP bidirectional port range 1025-5000