01-30-2013 04:22 AM
Hi community,
I hereby request your assistance for the following issue:
Master Server:
Host- srv-netbckp-201
SO - Windows Server 2008 R2
Version - Symantec Netbackup 7.1.0.4
Media Server:
Host- srv-netbckp-101
SO - RedHat Entreprise Linux Server Release 6.3
Version - Symantec Netbackup 7.1.0.4
NDMP Filler:
Host - netapp-a
[root@srv-netbckp-101 bin]# ./tpautoconf -verify netapp-a.onitelecom.pt
Connecting to host "netapp-a.onitelecom.pt" as user "backupuser"...
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 "netapp-A"
os type "NetApp"
os version "NetApp Release 8.1P1 7-Mode"
host id "1573839639"
Login was successful
Host supports LOCAL backup/restore
Host supports 3-way backup/restore
Activity Monitor logs:
01-30-2013 04:50 AM
hi,
please check if there is a stuck tape in tape Drive, without having info in netbackup?
and also make sure if you robtest is able to mount and dismount the tapes without any issues?
01-30-2013 06:26 AM
01-31-2013 01:54 AM
Should i check for more logs? If yes, which ones?
I hope you can help me with this issue.
Thanks in Advance.
01-31-2013 03:08 AM
hi,
see you are finding anyting under the below path in NDMP host media server
/usr/openv/netbackup/db/media/tpreq
/usr/openv/netbackup/db/media/drives
if you find, delete those entires,and restart the netbackup and check how it works,
if it does not,
remove all NDMP Drives from the Netbackup, and configure them again.
01-31-2013 07:42 AM
02-04-2013 11:16 PM
02-05-2013 03:00 AM
I did what you said above but unfortunately I still have the same error and same logs on NDMP backup.
Do you have more ideas/suggestions?
Best regards
02-05-2013 05:39 AM
There seems to be some communication issues here too - mention of unexpected message from NDMP and a lot of name resolution going on - which seems to resolve host hames as IP addresses rather than names.
Worth making sure you Master and Media Servers can reolve each other and the filer by short and FQDN name - use hosts files if neccesary.
Odd to have robot / tape errors on a VTL so most likely a communications / configuration issue.
Run through you config again and to be sure of everything and ask the NDMP admin for the messages log from the filer to see if that is showing any errors - also make sure that the fibre switches involved are not showing any issues (some switches will cause a port reset if any error is detected which can disconect drives)
Finally take a look at the event log on the VTL to see if that is reporting anything
This may all be a communications or connection issue, but if it centres around the NDMP then that is where you need to look
Hope this helps
02-05-2013 08:00 AM
02-05-2013 08:57 AM
What do you mean by local or remote or 3-way? I only know that it supports:
Host supports LOCAL backup/restore
Host supports 3-way backup/restore
Yes, the backup is going to VTL.
We are investigating with the NetApp admin what Mark_Solutions suggest.
02-14-2013 09:32 AM
Any update on this issue?
02-15-2013 07:34 AM
A 98 has a lot of causes, but NBU itself is usually not one of them.
I wouldn't go insane looking at BPTM logs, or Daemon/LTID logs.. I'd rather check configurations, and HBA/FC Cables/SFPs.
The things I'd tell you to check when you get a 98 are:
1) Make sure the TLD robot inventory is up to date.
2) Make sure the drive path is correct and visible. Check "storage show tape" output on the filer, and match the serial numbers shown with the paths configured in NetBackup. ( or run "tpautoconf -probe <filer>" from your NDMP Media Server, then "tpconfig -dl" to match the devices )
3) Are you 100% possitive that the correct DRIVE INDEX is assigned on NetBackup?
NetApp VTLs start on Drive Index 0, while NetBackup starts on Drive Index 1...
So if you created drives 0 and 1 in the VTL, you need to assign robdrnum 1 and 2 in NBU =
VTL Drive 0 = NBU robdrnum 1
VTL Drive 1 = NBU robdrnum 2
.
.
VTL Drive N = NBU robdrnum N+1
Hope this helps.