Updates, Patches and Late Breaking News for NetBackup 7.7.1

Updates, Patches and Late Breaking News for NetBackup 7.7.1

  • Article ID:100023651
  • Last Published:
  • Product(s):NetBackup


The Late Breaking News Bulletin has been created in order to provide customers updates on Documentation and Known Issues discovered post release.  These documents attempt to highlight the most "common" known issues and concerns reported by customers.


Guidelines regarding the availability of EEBs/Hotfixes for NetBackup can be found here:


Installation and Upgrade Checklist:

An Installation and Upgrade Checklist is available for NetBackup 7.7.1 on the SORT website to determine requirements for master, media and clients:


SORT also provides the ability to audit EEBs/Hotfixes in your environment to determine if they are resolved in a current version of NetBackup. You can access the EEB Auditor on SORT at the link below.


Known Issues: Please select the hyperlink on each topic for more information on each issue.

Appliance Issues:
Appliance-specific issues are collected in the NetBackup 5xxx Appliance series Late Breaking News:


Installation Issues:
Please review the NetBackup 7.x Upgrade Portal for additional information on how to perform a 7.7.1 upgrade: 


Latest Issues:
(ET 3866417) After upgrading Exchange 2013 to Cumulative Update 11 (CU11), Exchange backup may fail with either status code 69 or 130.

Fixed in 7.7.2: (ET 3861243) alert: Prior to Netbackup 7.7.2, when performing a backup on a Windows system where an Event Log is being redirected to a volume with little free space, the backup of the Event Log can fail, but the overall backup job will still finish with a status 0.

Fixed in 7.7.2: (ET 3867607) The Client Backups Report fails when using the NetBackup 7.7 or 7.7.1 Administration Console.

Fixed in 7.7.2: (ET 3853951) Downloadable Fix: An Emergency Engineering Binary (EEB) is available for NetBackup 7.7.1 which resolves nbsl communication issues in the Java GUI.

alert: VMware backups with Block Level Incremental or Changed Block Tracking can return incorrect changed sectors in ESXI 6.0

Was this content helpful?