Subscribe

Data Ontap 9.0 NDMP backup report error when LISTEN after upgrade .


Hi all,

This is a FAS2240-2 2-node Data Ontap 9.0
Just upgraded from Ontap 8.3RC2

The volumes under vserver are having cifs/nfs exports.
cifs/nfs volumes can be mounted, data read/write works properly on them.

When I added the Ontap 9.0 into a ndmp backup software , browsing works to see all the volumes under the vserver.
But when I was performing a backup.
The netapp Data Ontap 9.0 reported error ,
Here is the log from Netapp side:

 

MGMT_RPC::rpc_msg_input: 0x81041b400 here buf 0x0x81048e000 length 140

00000006.0000c7ee 0093d17a Sat Oct 08 2016 09:09:41 +00:00 [kern_ndmpd:info:4052] [39093]  DEBUG: MGMT_RPC::msg: incoming SERVER message 0x81041b400

00000006.0000c7ef 0093d17a Sat Oct 08 2016 09:09:41 +00:00 [kern_ndmpd:info:4052] [39093]  DEBUG: MGMT_RPC::using procedure 6 (procnum 10)

00000006.0000c7f0 0093d17a Sat Oct 08 2016 09:09:41 +00:00 [kern_ndmpd:info:4052] [39093]  DEBUG: MGMT_RPC::buffer_size_check: 0x0 0 vs 100

00000006.0000c7f1 0093d17a Sat Oct 08 2016 09:09:41 +00:00 [kern_ndmpd:info:4052] [39093]  DEBUG: MGMT_RPC::buffer_size_check: growing 0x81041b4b0 from 0 to 1024

00000006.0000c7f2 0093d17a Sat Oct 08 2016 09:09:41 +00:00 [kern_ndmpd:info:4052] [39093]  DEBUG: S<BKUP (ndmp_server) BR2NDMPD_DEBUG_LOG

00000006.0000c7f3 0093d17a Sat Oct 08 2016 09:09:41 +00:00 [kern_ndmpd:info:4052] [39093]  DEBUG:      sess_handle 0xd00000000 seq 0 (0x0)

00000006.0000c7f4 0093d17a Sat Oct 08 2016 09:09:41 +00:00 [kern_ndmpd:info:4052] [39093]  DEBUG:      LOG sev (3) msg (NDMP Vserver Listen: couldn't find any appropriate IP address to listen on)

00000006.0000c7f5 0093d17a Sat Oct 08 2016 09:09:41 +00:00 [kern_ndmpd:info:4052] [39093]  DEBUG: MGMT_RPC::server_reply: 0x81041b400 start

….

 

 

DATA_ABORT pending callback

00000006.0000c844 0093d17a Sat Oct 08 2016 09:09:41 +00:00 [kern_ndmpd:info:4052] [39093]  DEBUG: DATA cb_abort_on_listen_connect_failure: errnum 0: Success or No Error

00000006.0000c845 0093d17a Sat Oct 08 2016 09:09:41 +00:00 [kern_ndmpd:info:4052] [39093]  DEBUG: DATA set_ndmp_state: data_op 1 (DATA_OP_IDLE) => 1 (DATA_OP_IDLE)

00000006.0000c846 0093d17a Sat Oct 08 2016 09:09:41 +00:00 [kern_ndmpd:info:4052] [39093]  DEBUG: cb_ndmp4_data_listen: here

00000006.0000c847 0093d17a Sat Oct 08 2016 09:09:41 +00:00 [kern_ndmpd:info:4052] [39093]  DEBUG: generic_xmit_ndmp_message: start

00000006.0000c848 0093d17a Sat Oct 08 2016 09:09:41 +00:00 [kern_ndmpd:info:4052] [39093]  DEBUG: DMA<<S V4 sequence=11 (0xb)

00000006.0000c849 0093d17a Sat Oct 08 2016 09:09:41 +00:00 [kern_ndmpd:info:4052] [39093]  DEBUG:      Time_stamp=0x57f8b7d5 (Oct  8 09:09:41 2016)

00000006.0000c84a 0093d17a Sat Oct 08 2016 09:09:41 +00:00 [kern_ndmpd:info:4052] [39093]  DEBUG:      message type=1 (NDMP4_MESSAGE_REPLY)

00000006.0000c84b 0093d17a Sat Oct 08 2016 09:09:41 +00:00 [kern_ndmpd:info:4052] [39093]  DEBUG:      message_code=0x409 (NDMP4_DATA_LISTEN)

00000006.0000c84c 0093d17a Sat Oct 08 2016 09:09:41 +00:00 [kern_ndmpd:info:4052] [39093]  DEBUG:      reply_sequence=9 (0x9)

00000006.0000c84d 0093d17a Sat Oct 08 2016 09:09:41 +00:00 [kern_ndmpd:info:4052] [39093]  DEBUG:      error_code=0 (NDMP4_NO_ERR)

00000006.0000c84e 0093d17a Sat Oct 08 2016 09:09:41 +00:00 [kern_ndmpd:info:4052] [39093]  DEBUG:      error=7 (NDMP4_IO_ERR)

00000006.0000c84f 0093d17a Sat Oct 08 2016 09:09:41 +00:00 [kern_ndmpd:info:4052] [39093]  DEBUG:      addr_type=0 (NDMP4_ADDR_LOCAL)

 

I checked all the network interface in CLI:

                    Logical    Status                 Network            Current       Current  Is

Vserver     Interface  Admin/Oper Address/Mask       Node          Port        Home

----------- ---------- ---------- ------------------ ------------- ------- ----

Cluster

            clidev-fas2246-cx-01_clus1

                         up/up    169.254.141.39/16  clidev-fas2246-cx-01

                                                                                                                                e1a     true

            clidev-fas2246-cx-01_clus2

                         up/up    169.254.195.115/16 clidev-fas2246-cx-01

                                                                                                                                e1b     true

            clidev-fas2246-cx-02_clus1

                         up/up    169.254.247.155/16 clidev-fas2246-cx-02

                                                                                                                                e1a     true

            clidev-fas2246-cx-02_clus2

                         up/up    169.254.36.24/16   clidev-fas2246-cx-02

                                                                                                                                e1b     true

clidev-fas2246-cliqa-vserver1

            clidev-fas2246-cliqa-vserver1-lif1

                         up/up    10.6.254.201/24    clidev-fas2246-cx-01

                                                                                                                                e0a     true

 

 

Does anyone know what's the possible reason for this failure?

Thanks.

 

 

 

Re: Data Ontap 9.0 NDMP backup report error when LISTEN after upgrade .

Before the upgrade , NDMP browse , backup and restore works properly .

 

There was some warning in physical ports connection , but looks doesn't related to the error as each vserver has at least one port connected to network and is at home.

Attached the ports snapshot.

 

 

 

Does anyone have any ideas.

Re: Data Ontap 9.0 NDMP backup report error when LISTEN after upgrade .

you may need to add/move a data lif for ndmp connection. 

 

Please see page 54 of the Data Protection Tape Backup and Recovery Guide: https://library.netapp.com/ecm/ecm_download_file/ECMP1196874 

This explains the expected behavior when using different types of LIFs in CAB enabled or not enabled vserer-scope NDMP.

 

hopefully helps

 

thanks

 

Jeff

Cannot find the answer you need?  No need to open a support case - just CHAT and we’ll handle it for you.