11-04-2010 03:22 AM
Netbackup 6.0MP6 on a Solaris 10 master server.
I have an NDMP back failing with 213 errors. The drives are listed as UP in the device manager
I can connect ok to the NDMP host...
bash-3.00# tpautoconf -verify xxxxxxxx212
Connecting to host "xxxxxxxx212" as user "backups"...
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 "xxxxxxx212"
os type "NetApp"
os version "NetApp Release 7.2.2P2"
host id "0101167988"
Login was successful
Host supports LOCAL backup/restore
Host supports 3-way backup/restore
Can anyone give me some ideas on what else I can check or what is wrong here? Thanks
Solved! Go to Solution.
11-04-2010 06:10 AM
The policy was set as standard and not NDMP, this resolved the problem.
-Marc
11-04-2010 03:27 AM
for the STU that this policy is utilising?
bpstulist -U (or -L)
11-04-2010 03:48 AM
Label: xxxxxxxx212-hcart2-TLD0
Storage Unit Type: NDMP
Host Connection: xxxxxxxxxxmst
Number of Drives: 2
On Demand Only: yes
Max MPX/drive: 1
Density: hcart2 - 1/2 Inch Cartridge 2
Robot Type/Number: TLD / 0
Max Fragment Size: 1048576 MB
NDMP attach host: xxxxxxxx212
11-04-2010 05:00 AM
Please double-check STU name in policy:
bppllist <policy-name> -U |grep Residence
Compare with STU label in previous output.
Because of "On Demand Only: yes" in STU config,
STU name must be specified in policy (can not be 'Any Available').
11-04-2010 06:10 AM
The policy was set as standard and not NDMP, this resolved the problem.
-Marc
11-04-2010 06:12 AM
Strange it threw a 213 tho'.... one to file away for future reference.
11-04-2010 06:29 AM
So - my suggestion to compare STU with policy pointed you in the right direction?