NDMP Drive Paths
Created: 14 Sep 2012 | Updated: 04 Oct 2012 | 6 comments
This issue has been solved. See solution.
I use a netapp filer as NDMP destination. Now i replaced the filer and the tape drives got new paths. The "Configure storage devices" wizard does somehow not update the drive paths in NBU (6.5.6) to the new destination. During the wizard process i can see that it is detecting the correct paths but it does not update them on the drive configuration after the wizard is finished.
Is there another way to update the paths?
Thanks
Discussion Filed Under:
Comments 6 Comments • Jump to latest comment
Did you delete the existing?
Been a long time since I managed NetApp attached tape drives, but with the installation of a new filer & its associated new paths I would be more inclined to delete & recreate the drives.
Unless you can use tpautoconf :
Regards Andy
"Have you still got the box it came in?"
Thanks Andy, i just deleted the old paths and ran the wizard again. But now i get:
NDMP Backup fails with:14.09.2012 13:19:27 - Error ndmpagent(pid=7168) NDMP_LOG_ERROR 7 DATA: Backup terminated: EVENT: INTERNAL ERROR (for /vol/b2d)
14.09.2012 13:19:27 - Error ndmpagent(pid=7168) NDMP backup failed, path = /vol/b2d
14.09.2012 13:19:27 - Error bptm(pid=6080) none of the NDMP backups for client host04 completed successfully 14.09.2012 13:19:54 - end writing; write time: 00:00:34NDMP backup failure(99)
The directory path does exist. and i can see successful ndmp logins on the filer.
Not come across that before, sorry.
I presume you've verified access to the NDMP host (tpautoconf -verify ndmp_hostname) & that NDMP is enabled on the filer.
Anything in the backup log on the filer (/vol0/etc/log/backup I think) or in the syslog messages (etc/messages)
Regards Andy
"Have you still got the box it came in?"
Is this local NDMP backups or remote NDMP Backups?
Did you try probing drives from netbackup?
tpautoconf -verify FILERNAME
tpautoconf -probe FILERNAME
Also just make sure to check the NDMP sessions on the filer end( ndmpd sesions all) If you found anything, kill them and reset the port from filer end.
Thanks, Karthikeyan Sundaram.
I have found that when the NetApp filers bounce, I can lose device path connections. But what seems to happen for me is that the filer creates new device paths, that are effectively duplicates of the old path.
I run several steps to recover the NDMP tape devices:
This process has worked every time for us. It's a pain, but it works.
Deleting the old paths solved the issue.
Thanks
Would you like to reply?
Login or Register to post your comment.