(Multiple Etracks) SAN Client enhancements/fixes for 6.5.4


(Multiple Etracks) SAN Client enhancements/fixes for 6.5.4


Problem Statement:  Due to multiple issues with SAN Client option, there is a SAN Client bundle available on 6.5.4 to resolve multiple issues and is available via contacting NetBackup Technical Support.  The SAN Client Bundle is for the NetBackup master, media server, and client but can be installed independently (ie. media server package does not require client package).   The fixes noted below are contained in the current bundle.  Customers are encouraged to upgrade to 6.5.4 and request the following binaries from Symantec Support:

Troubleshooting:  Due to the numerous issues, all customers using SAN Client should be encouraged to deploy this bundle.  

Please contact Symantec technical support, referencing this TechNote ID and Etracks below to obtain a fix for these issues:

(ET1850287)  This SAN Client EEB Bundle for Master server contains fixes for:

1.     ET1722383 - nbemm memory leak
2.     ET1794501 - Client pipe being orphaned due to CORBA exception during cleanup
3.     ET1802014 - nbrbutil -releaseOrphanedPipes and -listOrphanedPipes need to consider pipes in all orphaned states 4,5 and 6

(ET1850283) This SAN Client EEB bundle for media servers contains fixes for:

1. ET1706970 - SAP Fiber Transport restore fails with exit status 83.
2. ET1717729 -  Tool to obtain FT client  target HBA information from EMM database.
3. ET1738027 - QLogic driver not getting removed on reboot on RedHat 5.2
4. ET1791534 - QLE2464 does not work for  Fibre Transport.
5. ET1829703 - SCPAL_Initialize: Error opening/running Jungo WinDriver or PCI adapter missing/failure
6. ET1836869 - nbfdrv64 dumps core on FT servers and exits with "DMA S/G Region Vectors exhausted for pool"
7. ET1651430 - unable to kill nbftsrvr when it is caught in a lengthy CORBA client timeout
8. ET1671751 - SAN Clients will not boot after setup
9. Improved logging to identify and understand error conditions better.
10. Support more than 31 client initiators per target port on a FT Media Server
11. Improved mechanisms to handle Client initiator port aliases LOGIN and LOGOUTS
12. Better error recovery mechanisms to handle IO pending requests during data transfer failures and operations aborted by ISP. This will avoid issues caused by closing pipes with outstanding I/O commands that don't complete within the time allowed.
13. Issue Terminate Exchange to identify initiators that sends a SCSI command without a PLOGI/PRLI to the target to identify the initiator
14. Restores of images with multiple fragments on disk storage unit.
15. On Linux the size of SGRV pool has been increased from (161 *  256K) to (322 * 256K). This provides enough SGRV pool space for 20 pipes of 16 buffers or 32 pipes of 10 buffers. On Solaris the pool size has been increased from (936 * 256K) to (4854 * 256K).

(ET1850314) This SAN Client EEB has nbftclnt client binary
with fix for:
1. ET1831620 - nbftclnt core dump;FATClientOpenShm And Improved logging to identify and understand error conditions better.

ETA of Fix:
Symantec has acknowledged that the above mentioned issues (multiple Etracks ) is present in the current version(s) of the product(s) mentioned at the end of this article.  Symantec is committed to product quality and satisfied customers.  This issue is currently scheduled to be addressed in the following release:

- NetBackup 6.5 Release Update 6 (6.5.6)

When NetBackup 6.5.6 is released, please visit the following link for download and readme information:

Please note that Symantec Corporation reserves the right to remove any fix from the targeted release if it does not pass quality assurance tests or introduces new risks to overall code stability. Symantec's plans are subject to change and any action taken by you based on the above information or your reliance upon the above information is made at your own risk.

Terms of use for this information are found in Legal Notices.



Did this article answer your question or resolve your issue?


Did this article save you the trouble of contacting technical support?


How can we make this article more helpful?

Email Address (Optional)