cancel
Showing results for 
Search instead for 
Did you mean: 

Unable to Add NetApp 3220 filer via NDMp to Backup Exec 2016

G4v1n
Level 3

Hi,

I am trying to add a NetApp 3220 filer via NDMP to BAckup Exec 2016.  I have tried adding under both the Backup and Restore Tab - File Server or NDMP Server, and the Storage - Configure Storage - Network Storage - NDMP Storage tab

Adding via the storage option fails with the following message:-

"Unable to connect to the NDMP server, or to the remote computer that is configured as a Remote Media Agent, or to the remote computer that is configured for deduplication"

Adding via Backup and Restore fails with the following:-

"The server was unable to complete the requested operation.  Possible cause: A communication failure occurred when attempting to connect to this server. Some common causes for this error are: the computer name is typed incorrectly, the computer is not powered on, a Backup Exec agent is not installed, or the network is improperly configured"

The Backup Exec server and NetApp filer are able to ping each other without issue outside of Backup Exec. The credentials I sue to SSh to the filer have been added to Backup Exec and selected when attempting to connect.  NDMP is enabled on the NetApp filer.  I have added port 10000 to the services file in %systemdrive%\Windows\System32\drivers\etc\ folder on the Backup Exec server and restarted the services but as yet I am unable to get this to work.

The debug monitor shows the following when I attempt to make a connection via the Configure Storage method

1 BESERVER 2172 31/07/2017 16:07:51 5808 05 AdammAdminBO::Execute() - ADAMM_ADMIN_VALIDATE_NDMP_HOST.
2 PVLSVR 8532 31/07/2017 16:07:51 3992 AdammSession::Execute( ADAMM_SESSION_EXECUTE_NDMP_VALIDATE_HOST )
Session = {D8049363-B193-41FA-A98B-659512A6BE43}
Validating "xxx.xxx.xxx.xxx:10000"
3 PVLSVR 8532 31/07/2017 16:07:52 0 Retrieved "xxxx" credentials
4 PVLSVR 8532 31/07/2017 16:07:51 3992 DeviceIoBase::GetInterface: index=2147483649 ->
5 PVLSVR 8532 31/07/2017 16:07:51 3992 DeviceIoBase::GetInterface: 0 <-
6 PVLSVR 8532 31/07/2017 16:07:51 3992 DeviceIoScsi::Provider::GetIntegerValue: id=26 ->
7 PVLSVR 8532 31/07/2017 16:07:51 3992 DeviceIoScsi::Provider::GetIntegerValue: val=0
8 PVLSVR 8532 31/07/2017 16:07:51 3992 DeviceIoScsi::Provider::GetIntegerValue: 0 <-
9 PVLSVR 8532 31/07/2017 16:07:51 3992 DeviceIoBase::GetInterface: index=2147483649 ->
10 PVLSVR 8532 31/07/2017 16:07:51 3992 DeviceIoBase::GetInterface: 0 <-
11 PVLSVR 8532 31/07/2017 16:07:51 3992 DeviceIoScsi::Provider::TestNdmpServerConnection: pinfo=0x000000000A61A0E0, infosz=1260 ->
12 PVLSVR 8532 31/07/2017 16:07:51 3992 DeviceIo: ndmpCreateConnection
13 PVLSVR 8532 31/07/2017 16:07:51 3992 DeviceIo: ndmpConnect: connection=0x0000000001DD2080 host=xxx.xxx.xxx.xxx port=10000
14 PVLSVR 8532 31/07/2017 16:07:51 3992 DeviceIo: ndmp_ping: hostname: xxx.xxx.xxx.xxx
15 BESERVER 2172 31/07/2017 16:07:52 4840 -1 Client requested key (1501513856).
16 BESERVER 2172 31/07/2017 16:07:52 4840 "Cluster" key is not present in the registry
17 BESERVER 2172 31/07/2017 16:07:52 4840 Did not detect Microsoft cluster ()
18 BESERVER 2172 31/07/2017 16:07:52 4840 VCS cluster keys do not appear to be present in the registry
19 BESERVER 2172 31/07/2017 16:07:52 4840 Did not detect VCS cluster ()
20 BESERVER 2172 31/07/2017 16:07:52 4840 01 Server Configuration: Client added: 23
21 BESERVER 2172 31/07/2017 16:07:52 4840 -1 Client 'xxxx' connected('','xxxx'): 0x26b0d820
22 BESERVER 2172 31/07/2017 16:07:52 4840 01 Server Configuration: Client removed: 22
23 BESERVER 2172 31/07/2017 16:07:52 4840 -1 Client 'xxxx' Disconnected:0x26b0d820
24 BESERVER 2172 31/07/2017 16:07:57 8204 -1 SecurityBO: Successfully setup RAWS certs.
25 BESERVER 2172 31/07/2017 16:08:11 3396 -1 SetServiceStatus: state: SERVICE_RUNNING check point: 0 wait hint: 0
26 PVLSVR 8532 31/07/2017 16:08:12 3992 DeviceIo: ndmpConnect: connect error, host=xxx.xxx.xxx.xxx, port=10000, error=10060
27 PVLSVR 8532 31/07/2017 16:08:12 3992 DeviceIo: ndmpDestroyConnection
28 PVLSVR 8532 31/07/2017 16:08:12 3992 DeviceIo: NdmpVerifyHostInfo: Error connecting to NDMP server on xxx.xxx.xxx.xxx:10000.
29 PVLSVR 8532 31/07/2017 16:08:12 3992 DeviceIoScsi::Provider::TestNdmpServerConnection: DERROR_NDMP_CAN_NOT_CONNECT(0x7000003f) <-
30 PVLSVR 8532 31/07/2017 16:08:12 3992 AdammSession::Execute( ADAMM_SESSION_EXECUTE_NDMP_VALIDATE_HOST )
Session = {D8049363-B193-41FA-A98B-659512A6BE43}
ERROR = 0xA0009B21 (E_PVL_NDMP_CONNECT_FAILURE)
31 BESERVER 2172 31/07/2017 16:08:12 5808 05 AdammAdminBO::Execute() - hr = 0xa0009b21

Any ideas ??

Thanks

7 REPLIES 7

Colin_Weaver
Moderator
Moderator
Employee Accredited Certified

What version of OnTap is running on the NDMP device?

Have you fully patched BE 16 to latest updates?

Hi 

yes I believe BE16 is at the latest version.  I ran LiveUpdate and it says there are no more patches available.  The version info shows as :-

Version 16 Rev 1142 (64-bit)

The NetApp filer is running the following:-

NetApp Release 8.2P5 7-Mode

Thanks

Colin_Weaver
Moderator
Moderator
Employee Accredited Certified

Are you using the Add Storage wizard or just trying to add the filer in as a server?

I have tried both methods.  My initial post shows the errors for both which are quite similar in wording, however the BE 16 debug monitor was from the Add Storage method only.

 

Colin_Weaver
Moderator
Moderator
Employee Accredited Certified

OK so if this does nto help you

http://www.veritas.com/docs/000016219

Then you may need to log a formal support case

Thanks

I had already seen that article and evrything looked ok.  I will double check though.

By the way this is for a trial for BE16 as we are thinking of moving from our current NetBackup solution.  Would I be able to raise a support case for a trial product??

 

ok looks like we NDMP auth set to MD5 as on the filer options ndmp shows the following:-

xxx> options ndmp
ndmpd.access all
ndmpd.authtype challenge
ndmpd.connectlog.enabled off
ndmpd.data_port_range all
ndmpd.enable on
ndmpd.ignore_ctime.enabled off
ndmpd.maxversion 4
ndmpd.offset_map.enable on
ndmpd.password_length 16
ndmpd.preferred_interface vif0-36
ndmpd.tcpnodelay.enable off
ndmpd.tcpwinsize 32768

Having checked on the NetApp site here

https://library.netapp.com/ecmdocs/ECMP1155586/html/GUID-0EAD04D4-A046-4526-ADE1-6EF57C3E4965.html

ndmpd.authtype challenge indicates we are using MD5.

There is no firewall in place on the BE server or between the BE server and the Filer and I can ping both ways between the devices without issue.