Quantcast
Channel: Symantec Connect - Backup and Recovery - 讨论
Viewing all articles
Browse latest Browse all 3749

NDMP Verification TPAutoconf - Node-Scope

$
0
0
我需要解决方案

I am trying to setup NetBackup 7.7 (trial) and connecting to Netapp 8.2.2 cDOT mode. I believe I have everything setup but I am only able to see one node in the NetApp cluster. When I have node-scode-mode on I can see "the" node and all of its volumes. but when I turn it off I can't see anything. I believe I am using the right LIF IP, I have tried it several different ways.

When I have node-scope-mode off I get

C:\Program Files\Veritas\Volmgr\bin>tpautoconf -verify 10.5.10.107
Connecting to host "10.5.10.107" as user "admin"...
Waiting for connect notification message...
Opening session--attempting with NDMP protocol version 4...
Opening session--successful with NDMP protocol version 4
  host supports MD5 authentication
Getting MD5 challenge from host...
Logging in using MD5 method...
ndmp_connect_client_auth failed
: host "10.5.10.107" failed
NDMP failed to verify host

But when I turn it on I get

C:\Program Files\Veritas\Volmgr\bin>tpautoconf -verify 10.5.10.107
Connecting to host "10.5.10.107" as user "admin"...
Waiting for connect notification message...
Opening session--attempting with NDMP protocol version 4...
Opening session--successful with NDMP protocol version 4
  host supports MD5 authentication
Getting MD5 challenge from host...
Logging in using MD5 method...
Host info is:
  host name "jacksondr-03"
  os type "NetApp"
  os version "NetApp Release 8.2.2 Cluster-Mode"
  host id "2014569956"
Login was successful
Host supports LOCAL backup/restore
Host supports 3-way backup/restore

What am I missing? I have read the documentation and it all seems setup correctly. I am currently backing it up using Backup Exec but I want to be able to use the clustering capabilities on the NetApp side.


Viewing all articles
Browse latest Browse all 3749

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>