Thanks MattS I did check the host file on the master/media and we are already using the vif-master interface. I had thought we fixed the issue after upgrading the tape drive firmware but I received the error again today. After rerunning the job I received a new error which is leading me to believe this is still related to the tape drive. Below is the Status from the failed job. I am going to follow up with IBM again.
1/26/2010 10:47:38 AM - requesting resource ares05c-hcart-robot-tld-3-Filer300c
1/26/2010 10:47:38 AM - requesting resource ares02.NBU_CLIENT.MAXJOBS.filer300c
1/26/2010 10:47:38 AM - requesting resource ares02.NBU_POLICY.MAXJOBS.NDMP_Vol_Dotnextvirt01
1/26/2010 10:47:38 AM - granted resource ares02.NBU_CLIENT.MAXJOBS.filer300c
1/26/2010 10:47:38 AM - granted resource ares02.NBU_POLICY.MAXJOBS.NDMP_Vol_Dotnextvirt01
1/26/2010 10:47:38 AM - granted resource P00045
1/26/2010 10:47:38 AM - granted resource IBM.ULT3580-TD4.016
1/26/2010 10:47:38 AM - granted resource ares05c-hcart-robot-tld-3-Filer300c
1/26/2010 10:47:38 AM - estimated 0 kbytes needed
1/26/2010 10:47:40 AM - started process bpbrm (3520)
1/26/2010 10:47:41 AM - connecting
1/26/2010 10:47:41 AM - connected; connect time: 00:00:00
1/26/2010 10:47:46 AM - mounting P00045
1/26/2010 10:49:00 AM - mounted; mount time: 00:01:14
1/26/2010 10:49:00 AM - positioning P00045 to file 9
1/26/2010 10:50:59 AM - positioned P00045; position time: 00:01:59
1/26/2010 10:50:59 AM - begin writing
1/26/2010 11:38:14 AM - current media P00045 complete, requesting next resource Any
1/26/2010 11:38:15 AM - current media -- complete, awaiting next media Any Reason: Drives are in use, Media Server: ares05c,
Robot Number: 3, Robot Type: TLD, Media ID: N/A, Drive Name: N/A,
Volume Pool: NDMPFiler01, Storage Unit: ares05c-hcart-robot-tld-3-Filer300c, Drive Scan Host: N/A
1/26/2010 11:39:02 AM - granted resource P00079
1/26/2010 11:39:02 AM - granted resource IBM.ULT3580-TD4.016
1/26/2010 11:39:02 AM - granted resource ares05c-hcart-robot-tld-3-Filer300c
1/26/2010 11:39:02 AM - mounting P00079
1/26/2010 11:40:15 AM - mounted; mount time: 00:01:13
1/26/2010 11:40:16 AM - positioning P00079 to file 1
1/26/2010 11:40:19 AM - positioned P00079; position time: 00:00:03
1/26/2010 11:40:19 AM - begin writing
1/26/2010 11:48:31 AM - Error ndmpagent(pid=1452) NDMP backup failed, path = /vol/dotnextvirt01
1/26/2010 11:48:32 AM - Error bptm(pid=2632) io_ioctl_ndmp (MTBSF) failed on media id P00079, drive index 2, return code 7 (NDMP_IO_ERR) (bptm.c.21479)
1/26/2010 11:48:33 AM - end writing; write time: 00:08:14
1/26/2010 11:48:37 AM - Error ndmpagent(pid=1452) terminated by parent process
1/26/2010 11:48:38 AM - Error ndmpagent(pid=1452) Connection was closed but has not yet been destroyed.
1/26/2010 11:48:40 AM - Error ndmpagent(pid=1452) Connection was closed but has not yet been destroyed.
media position error(86)
1/26/2010 11:48:41 AM - Error ndmpagent(pid=1452) MoverGetState called with no session
1/26/2010 11:48:42 AM - Error ndmpagent(pid=1452) NDMP backup failed, path = /vol/dotnextvirt01
1/26/2010 11:48:43 AM - Error ndmpagent(pid=1452) Connection was closed but has not yet been destroyed.
1/26/2010 11:48:45 AM - Error ndmpagent(pid=1452) Connection was closed but has not yet been destroyed.
1/26/2010 11:48:46 AM - Error ndmpagent(pid=1452) Connection was closed but has not yet been destroyed.
1/26/2010 11:48:48 AM - Error ndmpagent(pid=1452) Connection was closed but has not yet been destroyed.
1/26/2010 11:48:49 AM - Error ndmpagent(pid=1452) MoverGetState called with no session
1/26/2010 11:48:50 AM - Error ndmpagent(pid=1452) Connection was closed but has not yet been destroyed.
1/26/2010 11:48:52 AM - Error ndmpagent(pid=1452) Connection was closed but has not yet been destroyed.