on 12-18-2012 08:36 AM
5220 Appliance SAN Client backup starts failing with error code 83 after firmware upgrade from 2.0.1 to 2.5.1.b
Error
From the job log, I identified:
2/17/2012 15:51:58 - Error bptm (pid=20051) Could not open FT Server pipe: pipe open failed (13369361)
12/17/2012 15:51:58 - Info bptm (pid=20051) EXITING with status 83 <----------
12/17/2012 15:52:02 - Info bpbkar (pid=2368) done. status: 83: media open error
Diagnostic:
Resolution:
> Go to 5220 CLIS shell
Ruh-nbws-01:/home/maintenance # bpps -a | grep ft
Ruh-nbws-01:/home/maintenance # bpps -a | grep nbfd*
Ruh-nbws-01:/home/maintenance #
Ruh-nbws-01:/home/maintenance #Exit
Ruh-nbws-01.Settings> FibreTransport SANClient enable
> Go to the Shell again and check if the nbftsrvr and nbfdrv64 are running now:
Ruh-nbws-01:/home/maintenance # bpps -a | grep ft
root 7133 1 10 10:03 ? 00:00:12 /usr/openv/netbackup/bin/nbftsrvr
root 8647 1 0 10:03 ? 00:00:00 /usr/openv/netbackup/bin/nbftsrvr
Ruh-nbws-01:/home/maintenance #
Ruh-nbws-01:/home/maintenance #
Ruh-nbws-01:/home/maintenance # bpps -a | grep nbfd*
root 7133 1 9 10:03 ? 00:00:12 /usr/openv/netbackup/bin/nbftsrvr
root 8647 1 0 10:03 ? 00:00:00 /usr/openv/netbackup/bin/nbftsrvr
root 8765 7133 0 10:03 ? 00:00:00 /usr/openv/netbackup/bin/nbfdrv64 -m=0xe0002 -v=1 -s=256K
After Enableing FT service from Appliance, re-discover the SAN Client from NBU Cosole and re-ran the backup. Backup should completed successfully.
Your backup will only fail if you have configured SAN client FT usage preferences to Always. If you have a Preferred setting for FT usage, you backup will go automatic to LAN rather failing with error code 83.
I am having this same issue, but the solution for us will not be to use LAN, and when using FT we keep getting the error, any fix you know of to make it work using FT?
We have the issue only with 2 clients, all other 15 clients we have work just fine.
Hi rgarcia_pi,
Do you have issue with SAN Clients backup?
What is OS platform for you SAN client?
Have you tested if the FT connection is responding for those SAN client ?
Also,, are those normal clients & SAN clients using same STU and dedupe/adv pool?