Highlighted

SAN Client Backup

Hi All,

First of all let me give my infra details.

Master Server

OS - Windows 2012 R2 (2 nodes) Windows cluster

NBU Version - 8.1.1

Media Server

NetBackup Appliacne 5330

NBU Version - 8.1.1

We are facing multiple issue with FT client backups. Below is the list.

1. FT media server goes missing from FT client ( NBU console -  Devices ->SAN client)

2. All FT pipes will not be listed under the FT cleint and some times it shows FT pipe "not active" status. Backups running through LAN instead of SAN

3. FT backup to MSDP pool will be slow but FT backup to tape will be fast ( FT media server tape drive).

4. We see multiple times appliance port getting resetted. Many errors are logged in fabric logs.

For all the above issue we restart the nbftsrv servcie in applaince and everything come back to normal. FT media server, FT pipes come back online. Backup run through FT and speed as excepted. But after a day or 2 again issue reocurres.

We have multiple cases with support but no fix. Till now apart from restarting the applaine or restart the NBU services.

Everything fine from zoning and swtich end. We dont see any fault from farbic end.

Please let me know if any one came across such issue and any fix for same. Let me know if you require any further details.

Error Msg :

Feb 11, 2020 10:13:04 PM - Info bpbrm (pid=57157)  is the host to backup data from
Feb 11, 2020 10:13:04 PM - Info bpbrm (pid=57157) reading file list for client
Feb 11, 2020 10:13:56 PM - Info nbjm (pid=8596) starting backup job (jobid=5099673) for client , policy LD_B6_SAP_PHY, schedule Weekly_Full
Feb 11, 2020 10:13:56 PM - Info nbjm (pid=8596) requesting STANDARD_RESOURCE resources from RB for backup job (jobid=5099673, request id:{53CF6BA2-330F-4422-ABEF-5C0921511747})
Feb 11, 2020 10:13:56 PM - requesting resource  
Feb 11, 2020 10:13:56 PM - requesting resource  ISBKPPRD.NBU_CLIENT.MAXJOBS.
Feb 11, 2020 10:13:56 PM - requesting resource  .NBU_POLICY.MAXJOBS.LD_B6_SAP_PHY
Feb 11, 2020 10:13:57 PM - granted resource  .NBU_CLIENT.MAXJOBS.
Feb 11, 2020 10:13:57 PM - granted resource  .NBU_POLICY.MAXJOBS.LD_B6_SAP_PHY
Feb 11, 2020 10:13:57 PM - granted resource  MediaID=@aaac6;DiskVolume=PureDiskVolume;DiskPool=DPath=PureDiskVolume;StorageServer=;MediaServer=
Feb 11, 2020 10:13:57 PM - granted resource  
Feb 11, 2020 10:13:57 PM - granted resource  TRANSPORT
Feb 11, 2020 10:13:57 PM - estimated 108084447 kbytes needed
Feb 11, 2020 10:13:57 PM - Info nbjm (pid=8596) resumed backup (backupid=) job for client , policy LD_B6_SAP_PHY, schedule Weekly_Full on storage unit 
Feb 11, 2020 10:13:59 PM - started process bpbrm (pid=57157)
Feb 11, 2020 10:14:05 PM - Info bpbrm (pid=57157) starting bpbkar on client
Feb 11, 2020 10:14:12 PM - Info bpbkar (pid=9776) Backup started
Feb 11, 2020 10:14:12 PM - Info bptm (pid=58838) start
Feb 11, 2020 10:14:12 PM - Info bpbrm (pid=57157) bptm pid: 58838
Feb 11, 2020 10:14:12 PM - Info bpbkar (pid=9776) change time comparison:<disabled>
Feb 11, 2020 10:14:12 PM - Info bpbkar (pid=9776) archive bit processing:<enabled>
Feb 11, 2020 10:14:13 PM - Info bptm (pid=58838) using 262144 data buffer size
Feb 11, 2020 10:14:13 PM - Info bptm (pid=58838) using 16 data buffers
Feb 11, 2020 10:14:13 PM - Info bptm (pid=58838) USING 262144 data buffer size for FT
Feb 11, 2020 10:14:31 PM - Error bptm (pid=58838) Could not open FT Client pipe for client  pipe open failed (2097169 get buf length failed)
Feb 11, 2020 10:14:33 PM - Info bptm (pid=58838) EXITING with status 83 <----------
Feb 11, 2020 10:14:54 PM - Info bpbkar (pid=9776) done. status: 83: media open error
Feb 11, 2020 10:15:21 PM - connecting
Feb 11, 2020 10:16:02 PM - connected; connect time: 0:00:00
Feb 11, 2020 10:16:51 PM - end writing
media open error  (83)

 

Thanks and Regards

Hema

1 Reply
Highlighted

Re: SAN Client Backup

Not many of us use FT, and it's been three weeks since you posted with no replies here.  So, hopefully by now you have already decided to open an official Veritas Support case, and hopefully your problem is now resolved too.

If Veritas Support were able to assist you in resolving your technical issues... then I'm hoping that you might be able to explain the solution... if you are allowed to?  Thank you.