NB 7504 Release Notes

Symantec NetBackup 7.5.0.
4 Release Notes
NetBackup 7.5.0.4
Maintenance Release
The software described in this book is furnished under a license agreement and may be used only in accordance with the terms of the agreement. Documentation version: 7.5.0.4
Legal Notice
Copyright 2012 Symantec Corporation. All rights reserved. Symantec and the Symantec Logo are trademarks or registered trademarks of Symantec Corporation or its affiliates in the U.S. and other countries. Other names may be trademarks of their respective owners. The product described in this document is distributed under licenses restricting its use, copying, distribution, and decompilation/reverse engineering. No part of this document may be reproduced in any form by any means without prior written authorization of Symantec Corporation and its licensors, if any. THE DOCUMENTATION IS PROVIDED "AS IS" AND ALL EXPRESS OR IMPLIED CONDITIONS, REPRESENTATIONS AND WARRANTIES, INCLUDING ANY IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR NON-INFRINGEMENT, ARE DISCLAIMED, EXCEPT TO THE EXTENT THAT SUCH DISCLAIMERS ARE HELD TO BE LEGALLY INVALID. SYMANTEC CORPORATION SHALL NOT BE LIABLE FOR INCIDENTAL OR CONSEQUENTIAL DAMAGES IN CONNECTION WITH THE FURNISHING, PERFORMANCE, OR USE OF THIS DOCUMENTATION. THE INFORMATION CONTAINED IN THIS DOCUMENTATION IS SUBJECT TO CHANGE WITHOUT NOTICE. The Licensed Software and Documentation are deemed to be commercial computer software as defined in FAR 12.212 and subject to restricted rights as defined in FAR Section 52.227-19 "Commercial Computer Software - Restricted Rights" and DFARS 227.7202, "Rights in Commercial Computer Software or Commercial Computer Software Documentation", as applicable, and any successor regulations. Any use, modification, reproduction release, performance, display or disclosure of the Licensed Software and Documentation by the U.S. Government shall be solely in accordance with the terms of this Agreement. Symantec Corporation 350 Ellis Street Mountain View, CA 94043 http://www.symantec.com
Technical Support
Symantec Technical Support maintains support centers globally. Technical Supports primary role is to respond to specific queries about product features and functionality. The Technical Support group also creates content for our online Knowledge Base. The Technical Support group works collaboratively with the other functional areas within Symantec to answer your questions in a timely fashion. For example, the Technical Support group works with Product Engineering and Symantec Security Response to provide alerting services and virus definition updates. Symantecs support offerings include the following:
A range of support options that give you the flexibility to select the right amount of service for any size organization Telephone and/or Web-based support that provides rapid response and up-to-the-minute information Upgrade assurance that delivers software upgrades Global support purchased on a regional business hours or 24 hours a day, 7 days a week basis Premium service offerings that include Account Management Services
For information about Symantecs support offerings, you can visit our Web site at the following URL: www.symantec.com/business/support/ All support services will be delivered in accordance with your support agreement and the then-current enterprise technical support policy.
About Symantec Operations Readiness Tools

Symantec Operations Readiness Tools (SORT) is a set of Web-based tools that supports Symantec enterprise products. For NetBackup, SORT provides the ability to collect, analyze, and report on host configurations across UNIX/Linux or Windows environments. This data helps to assess whether your systems are ready for an initial NetBackup installation or for an upgrade from your current version. To access SORT, go to the following Web page: http://sort.symantec.com/netbackup Once you get to the SORT page, more information is available as follows:
Installation and Upgrade Checklist Use this tool to create a checklist to see if your system is ready for a NetBackup installation or an upgrade.
Hot fix and EEB Release Auditor Use this tool to find out whether a release that you plan to install contains the hot fixes that you need. Custom Reports Use this tool to get recommendations for your system and Symantec enterprise products, tips for risk assessment, and product license tracking.
Contacting Technical Support

Customers with a current support agreement may access Technical Support information at the following URL: www.symantec.com/business/support/ Before contacting Technical Support, make sure you have satisfied the system requirements that are listed in your product documentation. Also, you should be at the computer on which the problem occurred, in case it is necessary to replicate the problem. When you contact Technical Support, please have the following information available:

Product release level Hardware information Available memory, disk space, and NIC information Operating system Version and patch level Network topology Router, gateway, and IP address information Problem description:

Error messages and log files Troubleshooting that was performed before contacting Symantec Recent software configuration changes and network changes
Licensing and registration

If your Symantec product requires registration or a license key, access our technical support Web page at the following URL: www.symantec.com/business/support/
Customer service
Customer service information is available at the following URL: www.symantec.com/business/support/ Customer Service is available to assist with non-technical questions, such as the following types of issues:

Questions regarding product licensing or serialization Product registration updates, such as address or name changes General product information (features, language availability, local dealers) Latest information about product updates and upgrades Information about upgrade assurance and support contracts Information about the Symantec Buying Programs Advice about Symantec's technical support options Nontechnical presales questions Issues that are related to CD-ROMs, DVDs, or manuals
Support agreement resources

If you want to contact Symantec regarding an existing support agreement, please contact the support agreement administration team for your region as follows:
Asia-Pacific and Japan Europe, Middle-East, and Africa North America and Latin America customercare_apac@symantec.com semea@symantec.com supportsolutions@symantec.com
Contents
Technical Support ............................................................................................... 3 Chapter 1 Chapter 2 New features and enhancements ...................................... 9
About NetBackup 7.5.0.4 new features and enhancements ..................... 9
Platform compatibility ....................................................... 11

About NetBackup 7.5.0.x release compatibility .................................. About software release types .................................................... About compatibility with NetBackup 7.5 ..................................... NetBackup compatibility lists ......................................................... 11 11 12 13
Chapter 3
Product dependencies ........................................................ 17

About product dependencies .......................................................... 17 Operating system patches and updates ............................................. 17
Chapter 4
Operational notes ................................................................ 25

About operational notes in NetBackup 7.5.0.4 .................................... 25 About general NetBackup 7.5.0.4 notes ............................................ 25 About NetBackup OpsCenter notes .................................................. 26
Chapter 5 Appendix A
End-of-life notifications ..................................................... 33

About NetBackup end-of-life notifications ........................................ 33
About the current release content index ........................ 35

About the NetBackup 7.5.0.4 master Etrack index list ......................... NB_OPS_CTR_7.5.0.4.winnt.x64 ................................................ NB_OPS_CTR_7.5.0.4 .............................................................. NBLU_7.5.0.4.UNIX ................................................................ NB_OPS_CTR_7.5.0.4.winnt.x86 ................................................ NB_OPS_CTR_7.5.0.4.winnt.IA64 .............................................. NBLU_7.5.0.4.WIN ................................................................. 35 35 35 35 36 36 36
Contents
Appendix B
About the current release content ................................... 37

About release content conventions .................................................. 37 About NetBackup 7.5.0.4 release content .......................................... 38 NetBackup 7.5.0.4 Emergency Engineering Binary (EEB) listing ............ 54
Chapter
New features and enhancements

This chapter includes the following topics:
About NetBackup 7.5.0.4 new features and enhancements
About NetBackup 7.5.0.4 new features and enhancements

This release offers many enhancements to the issues and improvements from previous NetBackup releases. This release contains fixes to the known problems that pertain to the customer-specific issues that have been documented in the form of a Titan Case. Many of these fixes are available as individual engineering binaries and engineering bundles. These EEBs were created to address specific customer issues with a previous version of NetBackup. This maintenance release lists those engineering binaries and bundles. See About NetBackup 7.5.0.4 release content on page 38. See NetBackup 7.5.0.4 Emergency Engineering Binary (EEB) listing on page 54.
10
New features and enhancements About NetBackup 7.5.0.4 new features and enhancements
Chapter
Platform compatibility

About NetBackup 7.5.0.x release compatibility NetBackup compatibility lists
About NetBackup 7.5.0.x release compatibility

This release supports the platforms and binary sizes that were documented in the NetBackup 7.5 Release Notes for UNIX, Windows, and Linux document. The following sections describe how to locate the latest compatibility lists that are available on the Symantec Support Web site. In addition, the Binary Sizes table has been included for your convenience. For more information about platform compatibility, see the following:
NetBackup 7.5 Release Notes for UNIX, Windows, and Linux on the Symantec Support Web site. http://www.symantec.com/docs/DOC5041 NetBackup Enterprise Server and Server 7.x OS Software Compatibility List http://www.symantec.com/docs/TECH59978
About software release types

Symantec NetBackup maintains a policy by which they can deliver various levels of releases to accommodate customer needs. The following list defines the various release types and the version number schemes associated with each type. NetBackup products and the NetBackup Appliance products use this same process.
A major release is the first in a series of single-dot releases such as 2.5 or 7.5. This type of release contains new features, new supported platforms, and a complete set of the latest product documentation.
12
Platform compatibility About NetBackup 7.5.0.x release compatibility
A minor release is a single-dot release that follows a major release, for example, 2.1, 7.1, 7.5, and so forth. This release type contains much of the same requirements as a major release. It contains a smaller set of new features and enhancements, any platform proliferation, and a complete set of updated documentation. A release update is a double-dot release, for example, 2.5.1, 7.5.1, 7.5.2, and so forth. This release type may contain a few new features and enhancements as well as a many product fixes. Only those documents that are applicable to the new features or enhancements are updated and republished. A maintenance update is a triple-dot release, for example, 2.5.0.1, 7.5.0.1, 7.5.0.2, and so forth. This release type is comprised of a small number of fixes that are developed to address issues in either a major, minor, or release update. This release type only contains fixes to known issues and does not contain new features or enhancements to NetBackup. The only documentation that is provided is an online Readme and a NetBackup Release Notes document that is available on the Symantec Support Web site.
About compatibility with NetBackup 7.5

Symantec NetBackup has always maintained that the master server within your environment must be at a version level that is equal to or greater than the version levels of your media servers and client servers within the same environment. With NetBackup and the NetBackup Appliances, you can apply a maintenance update (for example 7.5.0.1) to a media server or client server within an environment where your master server is at a version level of 7.5. This same scenario can apply to the maintenance updates that are released under a minor release or release update. For information about NetBackup compatibility with the NetBackup appliances, see the NetBackup 5xxx Appliance Compatibility Technote on the Symantec Support Web site. Symantec NetBackup does not support any scenario where a minor release or release update is at a higher version level that the parent server. For instance, the following examples apply.
If a master server is at 7.5, then the media servers and client servers cannot be at a single-dot version level that is higher than 7.5, such as 7.6. If a master server is at 7.5, then the media servers and client servers cannot be at a double-dot version level that is higher than 7.5, such as 7.5.x. If a master server is at 7.5.1, then the media servers and client servers cannot be at a double-dot version level that is higher than 7.5.1, such as 7.5.2.
Platform compatibility NetBackup compatibility lists
13
The following table shows the various compatibility schemes that are supported with the current NetBackup 7.5 product line. Table 2-1 NetBackup release compatibility for the 7.5 product line NetBackup media server
6.0 6.5 7.0 7.0.1 7.0.2 7.1 7.1.0.1 7.1.0.2 7.1.0.3 7.1.0.4 7.5 7.5.0.1 7.5.0.2 7.5.0.3 7.5.0.4
NetBackup master server

7.5 7.5 7.5 7.5 7.5 7.5 7.5 7.5 7.5 7.5 7.5 7.5 7.5 7.5 7.5
NetBackup client
6.0 6.0, 6.5 6.0, 6.5, 7.0 6.0, 6.5, 7.0, 7.0.1 6.0, 6.5, 7.0, 7.0.1, 7.0.2 6.0, 6.5, 7.0, 7.0.x, 7.1, 7.1.0.x 6.0, 6.5, 7.0, 7.0.x, 7.1, 7.1.0.x 6.0, 6.5, 7.0, 7.0.x, 7.1, 7.1.0.x 6.0, 6.5, 7.0, 7.0.x, 7.1, 7.1.0.x 6.0, 6.5, 7.0, 7.0.x, 7.1, 7.1.0.x 6.0, 6.5, 7.0, 7.0.x, 7.1, 7.1.0.x, 7.5 6.0, 6.5, 7.0, 7.0.x, 7.1, 7.1.0.x, 7.5, 7.5.0.x 6.0, 6.5, 7.0, 7.0.x, 7.1, 7.1.0.x, 7.5, 7.5.0.x 6.0, 6.5, 7.0, 7.0.x, 7.1, 7.1.0.x, 7.5, 7.5.0.x 6.0, 6.5, 7.0, 7.0.x, 7.1, 7.1.0.x, 7.5, 7.5.0.x
Note: Support for the NetBackup 6.x product line is scheduled to end October, 2012.
NetBackup compatibility lists

The most up-to-date compatibility information on platforms, peripherals, drives, and libraries is located in various compatibility lists on the Symantec Support website. You can use the following methods to locate these lists:
The following URL guides you to a set of tools that can help you locate the latest platforms, peripherals, drives, and libraries.
14
https://sort.symantec.com/netbackup For NetBackup, SORT provides an Installation and Upgrade Checklist report as well as the ability to collect, analyze, and report on host configurations across UNIX/Linux or Windows environments. In addition, you can determine in what release whether any hot fixes or EEBs you have installed are fixed. You can use this data to assess whether your systems are ready to install or upgrade to this release.
If you want to view a specific compatibility list, you can find links to each list that is posted on the Symantec Support website: http://www.symantec.com/docs/TECH59978 The following items describe each of the compatibility lists that are available.
The NetBackup Enterprise Server and Server 7.x OS Software Compatibility List contains information about the operating system (OS) level and the version that is required to be compatible with a NetBackup master or media server. It also describes the OS level and the version that is required to be compatible with a NetBackup client. Predecessors and successors to the documented operating system levels may function without difficulty, as long as the release provides binary compatibility with the documented operating system. That list contains information about each of the following NetBackup Enterprise features:

NetBackup Enterprise servers and client Bare Metal Restore (BMR) NetBackup Access Control (NBAC) Network Data Management Protocol (NDMP) NetBackup SAN Client and Fiber Transport NetBackup Virtual System compatibility MSEO (media server encryption option) NetBackup Media Server Deduplication Option NetBackup OpsCenter File System Capability
NetBackup compatibility for a platform or OS version requires platform vendor support for that product. The platform compatibility lists that NetBackup maintains are subject to change as vendors add and drop platforms or OS versions.
15
The NetBackup server 7.x hardware compatibility list includes information for compatible drives, libraries, virtual tape devices, robot-types, fibre-channel HBAs, switches, routers, bridges, iSCSI configurations, and encryption devices That list includes information about the compatible drives, robot types, switches, routers, and bridges, and iSCSI configurations that coincide with the following hardware:

OpenStorage Virtual tape libraries (VTLs) Network Data Management Protocol (NDMP) Host bus adapters (HBAs) Encryption
NetBackup Database Agent 7.x Software Compatibility List This compatibility list contains the most current platform compatibility information for NetBackup database agents. NetBackup 7.x Snapshot Client compatibility lists NetBackup 7.x BMR File System and Volume Manager compatibility lists See also the NetBackup Bare Metal Restore Administrator's Guide for the following additional compatibility lists:

BMR compatible shared resource tree (SRT) versions BMR compatible file systems and volume managers BMR compatible cluster solutions BMR disk space requirements
NetBackup7.x Cluster Compatibility List NetBackup Desktop/Laptop Option compatibility list Backup Exec Tape Reader compatibility list
16
Chapter
Product dependencies

About product dependencies Operating system patches and updates
About product dependencies

This release requires the same product dependencies that were documented in the NetBackup 7.5 Release Notes for UNIX, Windows, and Linux document. The following sections describe the product dependencies and VxFS and VxVM compatible versions. http://www.symantec.com/docs/DOC5041
Operating system patches and updates

This topic provides information on the product dependencies of this release of NetBackup. You should verify that your operating system is up-to-date with all of the latest patches and upgrades before you install NetBackup. This section is a guide to inform you of the operating systems that require a patch or an upgrade. Table 3-1 provides the known, minimum operating system (OS) patches and updates. A vendor may have released a more recent patch that supersedes a patch that is listed in this table. Symantec recommends that you visit the Support website of that particular vendor for their latest patch information.
18
Product dependencies Operating system patches and updates
Table 3-1 Operating system type and version

AIX 5.3
Operating system patches and updates for NetBackup Notes

You may need to restart after changing to version 9.0.0.3. For the xlC.rte 8.0.0.10 fileset, you may need to install the IY91284 fix to avoid a potential issue when creating or updating the NetBackup database. The IY91284 fix is part of Maintenance Level 6. NetBackup 7.5 requires the AIX 5.3 TL12 SP2 (5300-12- 02-1036) Maintenance Pack as a minimum. (Higher patch levels should also work.) You can use the oslevel -s command to verify what Maintenance Pack level you have installed.
Patch
AIX runtime libraries 8.0.0.10 or 9.0.0.3 or later xlC.rte 8.0.0.10 fileset
AIX 5.3 TL12 SP2 (5300-1202-1036)
AIX 6.1
AIX 6.1 TL5 SP5 (6100-05-02-1034)
NetBackup 7.5 requires the AIX 6.1 TL5 SP5 (6100-05-02-1034) Maintenance Pack as a minimum. (Higher patch levels should also work.) You can use the oslevel -s command to verify what Maintenance Pack level you have installed.
AIX runtime libraries 9.0.0.3 or The runtime libraries need to be at 9.0.0.3 or later. later You may need to restart after you change to version 9.0.0.3. HP-UX COMPLIBS.LIBM-PS32 If you install AT on an HP-UX platform, this patch is required.
HP-UX IA64
Networking.NET-RUN: /usr/lib/libipv6.sl Networking.NET-RUN-64: /usr/lib/pa20_64/libipv6.1 Networking.NET-RUN-64: /usr/lib/pa20_64/libipv6.sl Networking.NET2-RUN: /usr/lib/hpux32/libipv6.so Networking.NET2-RUN: /usr/lib/hpux32/libipv6.so.1 Networking.NET2-RUN: /usr/lib/hpux64/libipv6.so
19
Table 3-1 Operating system type and version Patch
Operating system patches and updates for NetBackup (continued) Notes
Networking.NET2-RUN: /usr/lib/hpux64/libipv6.so.1 Networking.NET2-RUN: /usr/lib/libipv6.1 HP-UX PA-RISC Networking.NET-RUN: /usr/lib/libipv6.sl Networking.NET-RUN-64: /usr/lib/pa20_64/libipv6.1 Networking.NET-RUN-64: /usr/lib/pa20_64/libipv6.sl Networking.NET2-RUN: /usr/lib/libipv6.1 HP-UX 11.11 PHSS_35385 PHSS_32226 PHSS_37516 For HP-UX PA-RISC platforms, this fileset is required:
For HP-UX PA-RISC platforms, this fileset is required:
This patch is required for JAVA 6.0. This patch is a LIBCL patch. Contains fixes for the following: QXCR1000593919: purifyplus dumps core in PA32 QXCR1000589142: dld crash in LL_new_descendent_list when the aCC application is exiting. QXCR1000589142: dld crash in LL_new_descendent_list when the aCC application is exiting. QXCR1000746161: dlsym() hangs

QXCR1000593999: dld emits assert messages for chatr +mem_check enabled 64-bit executables
PHSS_26946
This patch is necessary to enable any C++ runtime code to work properly. This patch is a libc cumulative patch. This patch contains a linker tools cumulative patch.
PHSS_27740 PHSS_26560
20

PHSS_32864

That is a recommended critical patch from HP that is required for successful NetBackup client backups. This patch enables HP-UX 11.11 mmap() to use large files from 2GB to 4GB. That is a recommended critical patch from HP that is required for successful NetBackup client backups. That is a recommended critical patch from HP that is required for NetBackup to use VxSS. Allow POLL_INTERVAL to be set to zero in /var/ stm/config/tools/monitor/dm_stape.cfg. That disables the dm_stape monitor within the Event Monitoring System. Symantec recommends that you upgrade to IPR0109. This patch can cause problems with the programs that have the setuid bit set. Hewlett-Packard s IT resource center website contains information about this patch. www1.itrc.hp.com
PHKL_26233
PHSS_35379
PHCO_29029
PHSS_24045
PHSS_30970
PHCO_35743
S700_800 11.11 libc cumulative patch The above patch has dependency on the following patches: PHCO_31923 (critical patch): s700_800 11.11 libc cumulative header file patch PHKL_34805 : 700_800 11.11 JFS3.3 patch; mmap
HP-UX 11.23
PHSS_37201 PHCO_33431
This patch is required for JAVA 6.0. Symantec recommends that all customers running 11.23 install this patch. This applies to HP PARISC only because HP Itanium has moved to 11.31. That is a recommended critical patch from HP that is required so that dlopen works properly.
PHSS_34858
21

PHKL_31500

That is a recommended critical patch from HP that NetBackup requires, particularly when you attempt to run NetBackup with NetBackup Access Control (NBAC). Contains fixes for the following: QXCR1000593919: purifyplus dumps core in PA32 QXCR1000589142: dld crash in LL_new_descendent_list when the aCC application is exiting. QXCR1000746161: dlsym() hangs

PHSS_37492
QXCR1000593999: dld emits assert messages for chatr +mem_check enabled 64-bit executables
HP-UX 11.31
PHSS_37202 QPK1131 (B.11.31.0809.326) patch bundle
This patch is required for JAVA 6.0. This patch bundle is required for NetBackup media server support. This is an HP-UX September 2008 patch bundle. The operating system version must be SUSE Linux Enterprise Server 10 update 2 or greater to run NetBackup 7.0. Change Request ID - 6815915
SUSE Linux Enterprise Server 10 x64
SUSE Linux Enterprise Server 10 update 2
Solaris 9 SPARC 64-bit client
111712-11 (or greater)
111722-04 (or greater) Patch: 112908-29 (or greater) Patch: 112874-31 (or greater) 122300-53 Solaris 10 SPARC 64-bit (server and client) update 4 (08/07) and newer Change Request ID - 6723423 The server is supported on update 4 (08/07) and newer.
22

Symantec recommends that you download the recommended patch set dated June 2011 from the Oracle Support website. This patch set contains the following patches:
Recommended OS Patchset dated June 2011 or later
118777-17 (SunOS 5.10: Sun GigaSwift Ethernet 1.0 driver patch) 139555-08 (Kernel patch with C++ library updates). 142394-01 (Internet Control Message Protocol (ICMP) patch) 143513-02 (Data Link Admin command for Solaris (DLADM) patch) 141562-02 (Address Resolution Protocol (ARP) patch)
The following patches are for Solaris 10 SPARC with NXGE cards:

142909-17 (SunOS 5.10: nxge patch) 143897-03 (Distributed Link Software patch) 143135-03 (Aggregation patch) 119963-21 (Change Request ID - 6815915) 139555-08 (Change Request ID - 6723423)
23
Table 3-1 Operating system type and version

Solaris 10 x86-64

Symantec recommends that you download the recommended patch set dated 12/28/2011 from the Oracle Support website. Contains the following patches: 118778-15 (SunOS 5.10_x86: Sun GigaSwift Ethernet 1.0 driver patch) 139556-08 (Kernel patch with C++ library updates) 142395-01 (SunOS 5.10_x86: ICMP patch)
Patch
Recommended OS Patchset dated June 2011 or later
143514-02 (SunOS 5.10_x86: Data Link Admin command for Solaris patch) 147259-02 (SunOS 5.10_x86: Aggregation patch)
142910-17 (SunOS 5.10_x86 kernel patch to include NXGE fixes) 142910-17 (SunOS 5.10_x86: Distributed Link Software patch) 143136-03 (SunOS 5.10_x86: Aggregation patch)

139556-08 (Change Request ID - 6723423) 119964-21 (Change Request ID - 6815915)
Windows XP x86-32 Windows XP x86-64 Windows Vista x86-32
KB936357 KB928646 KB936357 KB952696
Microsoft microcode reliability update. Hot fix for hangs of connection attempts by PBX. Microsoft microcode reliability update. Contains the necessary updates to ensure that you can back up encrypted files. Microsoft microcode reliability update. Contains the necessary updates to ensure that you can back up encrypted files. Contains the necessary updates to run Volume Shadow Copy. Hot fix for hangs of connection attempts by PBX. Microsoft Storport hot fix.
Windows Vista x86-64
KB936357 KB952696
Windows Server 2003 IA64 KB913648 (SP1 & SP2) KB928646 Windows Server 2003 x86-32 (SP1 & SP2) KB883646
24

KB913648

Contains the necessary updates to run Volume Shadow Copy. Microsoft microcode reliability update. TCP/IP protocol driver triggers a disconnect event randomly. Required for master and media servers. Microsoft Storport hot fix.
KB936357 Windows Server 2003 x86-32 (SP2) Windows Server 2003 x86-64 (SP1 & SP2) KB971383
KB883646
KB913648
Contains the necessary updates to run Volume Shadow Copy. Hot fix for hangs of connection attempts by PBX. Microsoft microcode reliability update. TCP/IP protocol driver triggers a disconnect event randomly. Required for master and media servers. Contains the necessary updates to ensure that you can back up encrypted files. Contains the necessary updates to ensure that you can back up encrypted files. Contains the necessary updates to ensure that you can back up encrypted files. Hot fix for when a computer randomly stops responding. Hot fix for a decrease in I/O performance under a heavy disk I/O load. Update for the "Modified time" file attribute of a registry hive file. Hot fix to improve TCP loopback latency and UDP latency
KB928646 KB936357 Windows Server 2003 x86-64 (SP2) Windows Server 2008 x86-32 Windows Server 2008 x86-64 KB971383
KB952696
KB952696
Windows Server 2008 IA64 KB952696
Windows Server 2008 R2 (SP1)
KB2265716
KB982383
KB983544
KB979612
Chapter
Operational notes

About operational notes in NetBackup 7.5.0.4 About general NetBackup 7.5.0.4 notes About NetBackup OpsCenter notes
About operational notes in NetBackup 7.5.0.4

The 7.5.0.4 Maintenance Release is based on the NetBackup 7.5 release. That means the operational notes that were documented in NetBackup 7.5 may still apply to this release. Therefore, you should review that document if you have any questions or issues with this maintenance release. http://www.symantec.com/docs/DOC5041 This chapter contains the topics that explain important aspects of NetBackup 7.5.0.4 operations that may not be documented elsewhere in the NetBackup documentation set. This document is posted on the Symantec Support Web site and may be updated after the GA release of NetBackup 7.5.0.4. Therefore, Symantec recommends that you refer to the following Technote on the Symantec Support Web site to view the latest release information. http://www.symantec.com/docs/DOC5514
About general NetBackup 7.5.0.4 notes

The following items describe the known issues that exist in the NetBackup 7.5.0.4 release.
26
Operational notes About NetBackup OpsCenter notes
After an upgrade to NetBackup 7.5.0.4, changes to individual Object IDs in the nblog.conf file are not preserved. However, the major default settings are preserved. For a Linux virtual machine backup that requires file mapping, the name of an LVM volume can include any of the following special characters:

. (period) _ (underscore) - (hyphen)
No other special characters are supported. If other special characters are used in the volume name, the Enable file recovery from VM backup policy option does not work. As a result, you cannot restore individual files from that volume.
When the /etc/mke2fs.conf file is restored, the restore task is shown as partially completed on the Activity Monitor tab in the NetBackup-Java Administration Console. The issue occurs on RHEL6 Update 2 platforms and later, and it occurs even though the bare metal recovery of the client completes successfully. The issue occurs because the security properties contain some incorrect settings for the /etc/mke2fs.conf file in a Bare Metal Restore environment after the file is restored. If the backed up file system is encrypted for RHEL, then when the system is restored with the Bare Metal Restore option, the existing encryption is removed. During a Bare Metal Restore, the Zeta file system (ZFS) temporary mount fails. This issue occurs if any ZFS is not mounted or the canmount value is set to OFF during a backup. To restrict the disk or the disk pool, edit the Bare Metal Restore configurations. The edits ensure that the disk is not overwritten and the data that it contains is not erased during the restore process. For more information on how to edit the configurations, refer to the following sections of the Bare Metal Restore Administrator's Guide:

Managing Clients and Configurations Client Configuration Properties
About NetBackup OpsCenter notes

The following operational notes that pertain to NetBackup's OpsCenter include issues from this release as well as the NetBackup 7.5.0.3 Release Notes.
When an OpsCenter user is deleted, the following user-specific data is also deleted along with views, report schedules, and so on:
27
All data collectors that the user has created
All data collectors that the user has modified, irrespective of who created them Because of this behavior, there may be data collection failure as a result of user deletion. The following scenario explains the issue in detail: User A creates Data Collector D1 to collect data from NetBackup Master Server M1. User B modifies D1. OpsCenter Admin deletes User B. As a result of this user deletion, D1 is also deleted as User B had modified it. Therefore, data collection fails and User A cannot collect any data from M1. This issue will be fixed in OpsCenter 7.6.
On 64-bit Windows, if language packs are installed on top of a 7.1.0.x or a 7.5.0.x installation, an upgrade to a later version may fail. For example, if you upgrade OpsCenter 7.5 to 7.5.0.3 and install all language packs on top of 7.5.0.3, an upgrade to 7.5.0.4 may fail. To work around the issue, manually uninstall all language packs before the upgrade, and then reinstall them after the upgrade. In the SFR Timeline View, for the images that are collected in OpsCenter, the data format is shown as unknown because of the lack of data. OpsCenter does not support creating or editing multiple reports simultaneously for the same user session from different tabs or windows. You cannot open the same OpsCenter console in two or more browser tabs or windows and create or edit standard and custom reports simultaneously. That causes an exception to occur. The Deduplication reports do not show any data when you select the Report On parameter as Storage Unit Name. For VMware or Hyper-V clients, the search and restore operations work only if the client name is the same as host name. If the client name is the same as display name, UUID, or DNS name then only the Search functionality is available. You cannot perform restore operations in this case. The following table provides details on whether Search and Restore functionality is available when the client name is the host name, display name, etc.:
Client Name Type Host Name Display Name UUID DNS Name Search Yes Yes Yes Yes Restore Yes No No No
OpsCenter installation and deployment information and best practices.
28
The following list contains information about installing OpsCenter and some best practices information:
Symantec recommends that you do not cancel or interrupt the installation process once it is started. You may be unable to logon to the OpsCenter interface if it is installed on a server that has an underscore(_) in the host name. To avoid this issue, ensure that the OpsCenter Server host name does not contain any underscores like opshost. Installing OpsCenter components in a location that is mounted from a remote host is not supported.
A file selection list that contains more than 50 items does not appear in OpsCenter. For a specific job ID in an OpsCenter Analytics custom report, breakup job data is available only for 50 job directories. That is because when a NetBackup policy or job is associated with more than 50 backup selections, data is available for only 50 backup selections. The NetBackup user interface truncates data for the subsequent backup selections (greater than 50). With VBR, you can view the breakup job information for all of the job directories that are associated with a job or policy. That is because data collection in VBR happened through CLIs (and not through nbsl). OpsCenter does not provide the option to purge breakup jobs. Unlike VBR, OpsCenter does not provide the option to purge breakup jobs. In the VBR console, you can purge specific breakup jobs from the Settings > Global Settings > Data Retention section. An uninstall script is removed if an uninstall process for an OpsCenter Server or Agent is canceled or interrupted. If an uninstallation process for OpsCenter Server or Agent is canceled or interrupted on UNIX, then the uninstall script (uninstallOpsCenterServer and uninstallOpsCenterAgent) is removed from /opt/VRTS/install. If you want to uninstall the OpsCenter Server again, you can use the uninstall scripts from the OpsCenter DVD. Some result sets for a stored procedure that has multiple result sets may not appear. When you run a stored procedure that has multiple result sets, the output of only the first result set is displayed on the interface. The output of other result sets is not shown on the interface. The number of characters for a virtual name by the clustering technology on Windows is limited.
29
The virtual host name must be the short name (not FQDN) and less than 15 characters.
Some reports may only consider Full and Incremental schedule type jobs. On applying Schedule/Level Type filter with value All, the following reports consider only Full and Incremental schedule type jobs:

Advanced Success Rate All Failed Backups Consecutive Failures Report Success Rate Line
The NetBackupOpsCenter resource is offline after you have installed an OpsCenter cluster. After installing an OpsCenter cluster on a Windows 2008 R2 x64 system, you must manually bring the NetBackupOpsCenter resource online. You can bring the NetBackupOpsCenter resource online from the command line interface or by using the cluster user interface. You can use the following command:
hares -online <resource name> -sys <Name of the active node> Example: hares -online newonelatest-OpsCenter -sys OPS-CLUSTER-1
On Windows systems, the log.conf file is not created properly. That causes the vxlogview to return a No logs to be displayed message. Use the following commands to view logs for OpsCenter GUI (OID-147) and Infrastructure components (OID-761):
OpsCenter GUI:
<INSTALL_PATH>\OpsCenter\server\bin\vxlogview -p 58330 -o 147 -G
<INSTALL_PATH>\OpsCenter\gui\logs
Infrastructure components:
<INSTALL_PATH>\OpsCenter\server\bin\vxlogview -p 58330 -o 761 -G
<INSTALL_PATH>\OpsCenter\gui\logs
The object merger utility in OpsCenter fails on the master server. The object merger utility in OpsCenter (Settings > Configuration > Object merger) does not work (fails) for a master server. The object merger utility works for clients and media servers.
30
The Custom Tabular Backup and Custom-Client count report does not return data after an upgrade from VBR. The Custom Tabular Backup and Custom-Client count report does not return any data after you have upgraded from VBR to OpsCenter. To work around this issue, you must manually change the filter settings to get the correct report data after the upgrade is complete. The following steps guide you to change the filter settings:

Open the report, then select Edit Report. From the Filters section, select Job. From the Column drop-down list, select Product Type. The default operator is the equals sign character, =. From the Value drop-down list, select the same product type that you selected for VBR and click Add. Click Next to view the report. Once the changes are made, the reports display the correct data. Save the report.
The OpsCenter server can stop receiving events from the master server after a NetBackup upgrade. If all following conditions are applicable, add the OPS_CENTER_SERVER_NAME entry to the bp.conf file on UNIX or the registry on Windows to set OpsCenter's server name. Symantec recommends that you do add the entry before you attempt to upgrade.

The REQUIRED_INTERFACE is configured on the master server. The OpsCenter server monitors the master server.
The OPS_CENTER_SERVER_NAME entry is not configured on the master server If you do not add this entry, the OpsCenter server stops receiving events from the master server after the upgrade.
An enhancement has been made in OpsCenter to maintain VBR parity. You can now search for clients from the Monitor > Hosts > Clients page. You can use host names or substrings to accomplish that. However, you can only search for clients and not other attributes such as, CPU Count, CPU Speed, Discovered Agent Server, and others. An issue occurs in the Job Count Workload Analyzer: For each cell, the sum of occurrences differs from the total in the first column when the time basis that is selected is Active. That is expected because a job can be active and span across a multiple-hours time frame. Hence, the same job is counted for all the
31
hours. But the count in the first column shows the exact count of jobs that were active for these seven days. That is different from the implementation of Time basis=Start or End. In these cases, the sum of the occurrences in the cell match with the number displayed in first column.
The Master server job throughput report appears without a report output in My dashboard after a user upgrades from NOM to OpsCenter. The reason is that it is an SQL query-based report and is a part of composite report that is not migrated in the dashboard. Daylight savings time (DST) support for Historical reports in OpsCenter If data for the historical reports is synchronized during the hour when daylight savings time begins, it can cause problems in a distributed database system. The user can also lose data. A workaround is to use Universal Time (UTC) as the time zone, or use a time zone that does not have daylight savings time. To set the time zone, refer to the Symantec OpsCenter Administrator's Guide. When you upgrade from OpsCenter 7.0.x to OpsCenter 7.x, the Installation Choice screen displays the available space on the system drive. This issue occurs even if your previous installation is on a different drive (a drive other than the system drive).
32
Chapter
End-of-life notifications
About NetBackup end-of-life notifications
About NetBackup end-of-life notifications

This section lists the end-of-life notifications for the features, platforms, and devices that are no longer compatible with NetBackup beginning with the next major release.
Oracle Corporation has announced the end-of-life for Java 6 in July 2012. As a result, NetBackup does not support Java 6 in the next major release. Symantec NetBackup Server and Enterprise Server version 6.x has entered Partial Support as of August 1, 2012. The End of Support Life begins on October 3, 2012. For a detailed description of Standard Support, Partial Support, and End of Support Life, refer to the following Technote: http://www.symantec.com/docs/TECH77075 In addition, the following clients are no longer supported beginning with the next major release of NetBackup:

AIX 5.3 Red Hat Linux Itanium SLES Linux Itanium Solaris 9
For additional information on end-of-life notifications, refer to the NetBackup 7.5 Release Notes for UNIX, Windows, and Linux on the Symantec Support Web site.
34
End-of-life notifications About NetBackup end-of-life notifications
http://www.symantec.com/docs/DOC5041 Another resource that you can use to view end-of-life information is the Symantec Operations Readiness Tools (SORT). That is a Web-based tool that supports Symantec enterprise products. Part of this support is to provide users with "End of Life (EOL)" and "End of Support Life (EOSL)" information for NetBackup licensed software. To view this information, Go to the SORT > Support > Related Links page on the SORT for NetBackup Users Web site. See https://sort.symantec.com/eosl.
Appendix
About the current release content index

This appendix includes the following topics:
About the NetBackup 7.5.0.4 master Etrack index list
About the NetBackup 7.5.0.4 master Etrack index list

The following topics show the Etrack numbers that are fixed and contained in each of the following NetBackup packages for this release.
NB_OPS_CTR_7.5.0.4.winnt.x64
2727646 2751752 2763878 2776788 2784322 2785447 2806876 2809179 2811293 2811603 2814935 2818710 2824191 2829021 2835720 2836045 2839408 2851545 2867045 2870635 2871281
NB_OPS_CTR_7.5.0.4
2727646 2751752 2776788 2784322 2785447 2806876 2809179 2811293 2811603 2814935 2818710 2824191 2829021 2835720 2836045 2839408 2851545 2867045 2870635 2871281
NBLU_7.5.0.4.UNIX
2727646 2751752 2776788 2784322 2785447 2806876 2809179 2811293 2811603 2814935 2818710 2824191 2829021 2835720 2836045 2839408 2851545 2867045 2870635 2871281
36
About the current release content index About the NetBackup 7.5.0.4 master Etrack index list
NB_OPS_CTR_7.5.0.4.winnt.x86
2727646 2751752 2763878 2776788 2784322 2785447 2806876 2809179 2811293 2811603 2814935 2818710 2824191 2829021 2835720 2836045 2839408 2851545 2867045 2870635 2871281
NB_OPS_CTR_7.5.0.4.winnt.IA64
2727646 2751752 2763878 2776788 2784322 2785447 2806876 2809179 2811293 2811603 2814935 2818710 2824191 2829021 2835720 2836045 2839408 2851545 2867045 2870635 2871281
NBLU_7.5.0.4.WIN
2727646 2751752 2763878 2776788 2784322 2785447 2806876 2809179 2811293 2811603 2814935 2818710 2824191 2829021 2835720 2836045 2839408 2851545 2867045 2870635 2871281
Appendix
About the current release content

This appendix includes the following topics:

About release content conventions About NetBackup 7.5.0.4 release content NetBackup 7.5.0.4 Emergency Engineering Binary (EEB) listing
About release content conventions

The following list describes the conventions used in the subsections that follow this section. Each item listed in the "Current release content" subsection describes a feature, enhancement, or fixed issue contained in this release:
Description Describes a particular problem that has been fixed in this release. ** Description ** Describes a problem that can lead to a potential data loss. Please read the problem descriptions carefully. Workaround Any available workarounds to a problem are also listed. Workarounds can be used instead of applying the patch, however, Symantec recommends the "best practice" of being at the latest available patch level. Additional Notes Any additional information regarding a problem is included.
38
About the current release content About NetBackup 7.5.0.4 release content
About NetBackup 7.5.0.4 release content

This topic contains a list of known issues that were fixed and included in this release of NetBackup. Etrack Incident: 2682874
Description: The nbdeployutil -report -traditional function may report incorrect OpenStorage capacity values in an environment that is configured for both OpenStorage and NDMP. With this fix, NDMP backups are not included in the OpenStorage capacity calculations.
Etrack Incident: 2709576
Description: This release contains a new feature that enables the NetBackup appliance to perform backups and restores of VMware virtual machines. A separate Windows VMware backup host is no longer required.
Description: When multiple master servers are specified on an nbdeployutil report, each master server incorrectly reports the save values. This fix ensures that each master server has the correct values.
Description: When NDMP devices such as BlueArc and Hitachi filers are backed up to a Quantum DXI storage unit, a status code 85 occurs.
Description: An import or a deport fails on a busy system that attempts to perform an off host backup.
Description: A restore of millions of files is processed for many hours in bpdbm before it becomes active.
Description: With NetBackup Access Control enabled, a NetBackup Admin non-root user may be presented a Backup, Archive, and Restore interface instead of the
39
Admin interface. The user may also be denied access to operations that are granted to the user. The issue may occur if a file fails to write to the home directory even though write access is granted in the OS permissions. The issue occurs in Kerberos integrated environments where home directory write access may be denied if the user is without a valid Kerberos ticket. Etrack Incident: 2735153
Description: When a schedule is viewed or edited that has an overridden storage lifecycle policy, the policy interface freezes until the NetBackup-Java Administration Console is restarted.
Description: When a Hyper-V backup fails, snapshots are sometimes not deleted from a disk array. This issue causes the NetBackup snapshot creation job to fail with a status code 156.
Description: An issue has been fixed where scheduled exports of reports run slowly in OpsCenter.
Description: An issue has been fixed where a redirected restore of secure sites that begin with https:// fails for the SharePoint web application.
Description: The nbcatsync process does not identify the catalog files that are stored somewhere other than the default location. This issue leads to an incomplete catalog recovery.
Description: The user cannot connect to Backup Exec servers and data collection fails if a password contains an HTML character, such as &. To work around this issue, ensure that passwords do not contain HTML characters.
Description:
40
When the user tries to restore a FlashBackup or VMware incremental images for a full virtual machine restore, the restore fails. The issue occurs when the FORCE_RESTORE_MEDIA_SERVER option is set to use a different media server from the one that the images were backed up on. Etrack Incident: 2769666
Description: While NetBackup Access Control is enabled, an issue occurs in the bpdbjobs command line interface when jobs are checked for job action permissions. Individually set permissions do not work as expected. Permission for the jobclean action was checked for all job actions. This fix ensures that checks occur for corresponding permissions.
Description: This patch fixes issues with the discovery documents that are created for VIP policy jobs and with the VIP policy configuration Test Query... Button. The issue occurs if the vCenter contains objects with a name that contain characters beyond the US-ASCII range. These two areas may fail if the master server locale or the discovery host locale does not support the extended characters.
Description: An Application granular restore technology restore can fail for a VMware backup with application protection if the catalog name has an underscore in it.
Description: Calendar schedules are rerun multiple times in the backup window. The issue occurs if the backup window includes midnight, and the backup starts before midnight and finishes the next day.
Description: A backup cannot be performed during the file mapping process on a Linux virtual machine because the bpdbm process fails.
Description: When NetBackup Access Control is enabled, a non-root user who is an administrator cannot perform virtual machine restores in the NetBackup-Java Administration Console.
41
The root user may still perform restores. Etrack Incident: 2776226
Description: If PEM_USE_SAME_HOST_BY_NAME is turned off, the nbpem process should not perform alias lookups.
Description: When OpsCenter is used for reporting, an exception occurs on the Cloud tab. The issue occurs when a multi-level view is selected while the user monitors Cloud-related data.
Description: In the Appliance interface, the list of all media servers shows both appliance media servers and NetBackup media servers. This issue makes it hard for users to identify the type of media server. An enhancement has been made to identify the media server as an appliance or a classic NetBackup media.
Description: On the Change Storage Unit panel, the Reduce Fragment Size checkbox remains checked and the default size remains highlighted. The issue occurs after an upgrade from NetBackup 6.5 to 7.1 when the Reduce Fragment Size checkbox is left unchecked.
Description: A Linux guest OS fails to map if it contains a logical volume manager with a period in the name.
Description: For Exchange 2010 Data Availability Group (DAG) backups, an image is cataloged with duplicate network portions of its DAG name. For example, server.mydomain.com shows up as server.mydomain.com.mydomain.com. The issue occurs when an FQDN is entered as the client in the policy. The issue causes restores of the image to fail. This fix removes the duplicated portion of the name.
Description:
42
When ndmp devices are configured with the Device Configuration Wizard, the devices from all ndmp hosts are displayed even when only one host is selected. Etrack Incident: 2783791
Description: NDMP backups with more than one fragment fail with a status code 85 when the second fragment is duplicated. The issue occurs for the backups that are duplicated to a tape through DirectCopy.
Description: On Solaris, Linux, and AIX master servers, if /usr/openv/db/data is a symbolic link, NetBackup experiences installation failures. The issue occurs because the vendor command to install the native package replaces the symbolic link with a real directory. For more information, refer to the following Technote: http://www.symantec.com/docs/TECH189078
Description: After an upgrade to NetBackup 7.5, the user cannot create a custom tabular report for the backup success rate.
Description: When storage lifecycle policy parameters are modified, the interface does not pick up previous retention values for duplication operations.
Description: In the Drive Utilization Report, the reported drive usage is much lower than the actual usage.
Description: The MS-SQL Agent interface does not display the backup history in a sorted order.
Description: Accelerator does not work on storages with multiple logical subunits in a disk pool. The issue occurs because a previous backup can be on one logical subunit and the current backup can be on another. Accelerator tries to include the
43
previous backup, but it looks at the logical subunit of the current backup instead. The function get_lsu_name_from_frag_rec has been added to resolve the issue. Etrack Incident: 2786687
Description: A new option -RenewCred has been added to the bpnbat login to renew credentials after the default 24 hours.
Description: Since NetBackup 7.5, for users in the NetBackup Product Improvement Program, data from the master server is periodically collected and uploaded to a Symantec server. As of NetBackup 7.5.0.4, data is always collected on the master server. The data is only uploaded to a Symantec server if the user chooses to participate in the NetBackup Product Improvement Program.
Description: This fix addresses an issue where duplication jobs end with a status code 190 because images with zero-length were duplicated.
Description: A corrupt .f file causes the bpdbm process to consume CPU and memory until the bpdbm process is stopped. Although the bpdbm process can remove the corrupt .f file, the cat_convert -check command fails with the affected file.
Description: On a Linux client with an encrypted file system, a Bare Metal Restore backup fails with a status code 1.
Description: An issue has been fixed where backups can fail if more than 1 million files are in a single directory.
Description: The bpstsinfo -comparedbandstu command fails when the storage unit has PureDisk data images.
44
Description: A user with a locked account can still log in because the NetBackup-Java Administration Console does not check for locked accounts.
Description: Image verification jobs fail for the Exchange images that are backed up to a UNIX media server.
Description: Storage lifecycle policy duplication uses OpenStorage DirectCopy when the storage devices are capable.
Description: VMware incremental backups to an MSDP storage unit fail with a status code 13 or 84.
Description: When a NetBackup 7.5.0.3 client performs an accelerated client direct backup to a pre-7.5.0.3 media server, the backup fails.
Description: After an upgrade to NetBackup 7.5, incremental backups of Active Directory granular data fail.
Description: On a Linux virtual machine, backups may fail if a directory contains a large Access Control List.
Description: When the Tabular Backup Report is created with disabled or inactive policies, the report displays data for those policies.
Description: An issue has been fixed where the day window only works if 12:00 A.M. to 12:00 A.M. is selected in the OpsCenter custom reports.
45
Description: On UNIX and Linux systems, the compressed catalog image files are not deleted when the images expire.
Description: OpsCenter data collection fails when data is collected from master servers. The issue occurs because the data collection makes unnecessary calls to the bpretlevel command line interface.
Description: When a storage is corrupted, an image cleanup fo the corrupted images fails with a status code 174. The image cleanup has been modified to handle the corruption of image-related files, such as .info files.
Description: Snapshot backups appear as disk icons in the Operational Restore timeline. Now snapshot icons are displayed for snapshot backups.
Description: An issue has been fixed where NetBackup installation fails on a Windows platform because the database fails to start on the first attempt.
The nbdecommission process fails on servers of the type foreign media server.
Description: In NetBackup 7.5, the ability was removed to perform incremental backups of Distributed File System Replication data on a Windows client. This fix reenables that functionality.
Description: An issue exists where an image that is referenced in another backup is deleted from the catalog but not from storage. The result is that the image can no longer be imported.
46
Description: Policy and schedule filters in OpsCenter take a long time to load. The issue occurs when a lot of policies and schedules exist.
Description: Differential incremental catalog backups may skip recently updated configuration information. This issue can cause catalog recoveries to not recover NetBackup to the expected state.
Description: Restores fail on a virtual machine that is backup up on a datastore that begins with the name datastore. The issue has existed since NetBackup 7.5.0.1 and has now been resolved.
Description: The bprd reports cannot allocate a bitmap when an incremental restore is attempted.
Description: The number of scratch media reports in OpsCenter is higher than the scratch media numbers that NetBackup shows. This issue can cause problems when available media runs low on a master server and the user relies on OCA reports for accurate numbers.
Description: When backups run on Windows NetBackup clients and Use Change Journal is enabled, the change journal backups may not detect the files that were changed between backups. This issue may cause some files to not be backed up, which creates the risk of data loss.
Description: The Enterprise Vault Agent leaves the Vault Stores in backup mode for the entire duration of the backup.
Description:
47
AIR storage lifecycle policy import operations may fail. The error occurs when multiple volumes exist on a storage server and not all volumes are configured in a single NetBackup domain. Etrack Incident: 2820643
Description: Non-Volume Shadow Copy Service Exchange granular backup jobs fail. The error occurs if the backups are targeted to a media server deduplication pool storage unit on NetBackup clients that are higher than version 7.5.0.4.
Description: If a SharePoint 2003 farm backup is attempted with NetBackup 7.5.0.4 or later, the backup fails with a status code 16 (unsupported feature). SharePoint 2003 reaches its end-of-life in NetBackup 7.5. If backup images from SharePoint 2003 exist, the SharePoint 2003 servers should be at a NetBackup version before 7.5 to perform restores.
Description: NetBackup Exchange Policy fails if granular restore is enabled for SharePoint on Windows 2003 S2. The failure occurs because the configuration is not supported.
Description: NetBackup SharePoint Policy fails if granular restore is enabled for SharePoint on Windows 2003 S2. The failure occurs because the configuration is not supported.
Description: SAP backups that run for a long time fail if they contain a large number of files.
Description: After an upgrade to 7.5.0.1, the Capacity Licensing Report shows the wrong terabyte size for all master servers.
Description: Some cases exist where VMware policy backups fail with a status code 6 after an upgrade to 7.5.0.x.
48
Description: On AIX systems, NetBackup binaries make unnecessary Domain Name Service queries during process configuration. A fix has been added to remove those unnecessary queries.
Description: A missing Key Management Server tag in the bpimmedia output has been added.
Description: The SAN client Fibre Transport media server drivers have been added that were not included in the NetBackup Appliance 2.5 release.
Description: VMware backups fail with a status code 196 when time windows are still open. The calculation of the next backup is incorrect if the child of a VMware Intelligent Policy job is delayed until after midnight. The issue occurs because the current time is used for the seed instead of the time that the parent job calculates.
Description: When PureDisk is used as a destination storage server for AIR, an inconsistency occurs between the source server and the destination server. This issue may result in a failure to import images where no notification is given of the failure.
Description: VMware backup performance is slower than expected after an upgrade to NetBackup 7.5.0.x. The issue occurs because the host disk caches within the virtual disk development kit (VDDK). The VDDK cache has been disabled to resolve the issue.
Description: When an alert is generated for Low Available Media, it does not display information for which master server the alert applies. The issue occurs when ALL MASTER SERVERS is selected.
49
Description: Checkpoint restart backups may skip several files in the policy if wildcard-based paths are used in the backup selection.
Description: An issue occurs where SAP backups fail when files are greater than 4 gigabytes.
Description: In the Images on Media report, the interface displays the incorrect information for the Encrypted field.
Description: When a job priority of active or queued jobs is decremented on a Windows interface, the interface loses the job data and displays this message: Not connected, check if services are up.
Description: False Low Available Media alerts are generated when a Low Available Media alert policy is defined in OpsCenter. The Low Available Mediaalert only considers the media that NetBackup actively uses. If NetBackup does not yet use some media, OpsCenter should consider them as available media.
Description: Pagination does not work correctly when Hierarchical View is selected within the Jobs view under the Monitor section.
Description: In a NetBackup Access Control environment, a policy modification fails when the Use Accelerator option is checked.
Description: The nbjm process may core dump when NetBackup Access Control is enabled and many jobs are in progress.
Description:
50
The failure history logs the wrong client name. This issue causes the parent job to repeatedly restart even though the child jobs have exceeded their failure history. Etrack Incident: 2839408
Description: When a custom report that contains job directory information is exported to a .CSV file, an extra carriage return occurs after the job directory entry. The issue causes the report data to contain empty lines or some entries that span multiple lines.
Description: When removable media expiration times are updated, the number of active jobs decreases and the bpdbm process fails with a status code 97. The issue occurs after many storage lifecycle policy jobs that all target the same media are run from a disk to a tape.
Description: On an HP-UX PA-RISC platform, media server copy backups fail and the bpbkar process core dumps.
Description: When alerts are generated in OpsCenter, the source node that generates the alerts is not depicted in a separate Object ID.
Description: This fix enables Hyper-V and FlashBackup-Windows jobs to use Fibre Transport.
Description: A client directory in db/images with a link to another client directory in db/images exists. However, an alias has not been created for the linked client to the real client. This issue causes the image cleanup to prematurely prune the timestamp directories while valid images remain in the directory.
Description:
51
When a vmdk with a size in terabytes is backed up from a Windows x86 platform, a bitmap of the required size is not allocated. The backup then tries to load the bitmap in smaller chunks, which also fails. Etrack Incident: 2848419
Description: When an AIX account has been locked out, the NetBackup-Java Administration Console still allows a user to log in with NetBackup Access Control enabled.
Description: An issue has been fixed where data exports from custom reports produce inconsistent reports.
Description: A UNIX FlashBackup and a single file restore fail with a SIGBUS signal. The issue occurs on file system backups with volumes of more than 2 terabytes.
Description: When multiple processes browse the same compressed .f file, browse errors occur. The issue occurs because the bpdbm process becomes out of sync with the actual state of the file compression. The issue can be resolved if the user manually compresses and uncompresses the .f files. This code change also removes the behavior of immediately recompressing an uncompressed .f file after browsing that file. This recompression will instead occur during the next automatic image cleanup, as was the case in previous major releases of NetBackup.
Description: When SQL jobs are run, the BRMComm object may not be destroyed because of a timing problem. The issue causes a memory leak and the nbjm process shuts down.
Description: When the VXSS_CREDENTIAL_PATH environment variable is set to a path with a .crat extension and the nbac_cron -SetupCron command is run, the command fails with the following message: nbuadm.crat: No such file or directory.
52
Description: Synthetic full backups to SLP storage units can result in data loss. The issue occurs when the media expiration times are not properly set.
Description: Support has been added for PureDisk 6.6.4 data collection in OpsCenter.
Description: The pem process fails when one thread starts a child job while another thread cleans up the scheduler that allows the child job to run.
Description: The LIMIT_BANDWIDTH setting stops working on Windows client backups when a second backup starts on the same client.
Description: On an alternate client, Windows off-host snapshots back up the local drive instead of the snapshot volume. This issue occurs if the drive letters are the same on the source and the alternate client.
Description: After an upgrade to NetBackup 7.5 and higher, if an MSSQL server database backup fails, the dbbackex.exe executable freezes. The next backup then fails with a VDI timeout error.
Description: Job Data Collection may enter a queued state when many jobs and tape libraries are present and the query takes a long time.
Description: An upgrade to NetBackup 7.5.0.4 does not work because the database upgrade fails. This issue has been resolved.
Description:
53
The policy type NCR-Teradata has been changed to Teradata. Etrack Incident: 2874794
Description: The alternate client bpfis process sends a BACKUP START message, which causes a socket error. The issue has been resolved so the bpfis process does not send the message.
Description: The nbpem process core dumps during an Exchange backup with Application Protection enabled.
Description: Mapped full backups on multiple virtual machines that use SAN transport fail. The rvpntfs.dll module causes the bpbkar process to fault during the backups.
Description: Accelerator cannot be configured on an OpenStorage device. The latest device mapping file has been added to this release to resolve this issue.
Description: When a subdirectory is mounted elsewhere on its parent device, the ALL_LOCAL_DRIVES directive may incorrectly skip some directories, which can lead to data loss. This patch ensures that those directories are not skipped.
Description: A successful sub-job collection created duplicate entries in the Tabular Backup Report. The issue has been resolved so these duplicate entries are not created.
Description: After an upgrade to 7.5.0.3, if a retention mode is set to Expire after copy in a storage lifecycle policy, the nbstserv process fails. This issue causes duplication batching, replications, and disk image expirations to not execute.
Description:
54
About the current release content NetBackup 7.5.0.4 Emergency Engineering Binary (EEB) listing
A Linux guest OS fails to map if it contains a logical volume manager with a period in the name. Etrack Incident: 2898069
Description: On HP and Linux clusters, a server patch does not install successfully. The issue has been resolved.
Description: An upgrade fails if VMware jobs are left to wait for a retry.
Description: An issue occurs on Windows 32-bit systems when an Accelerator-based backup is performed with the checkpoint restart enabled. If the backup is suspended or fails and resumes from the checkpoint, the associated track log grows in size and consumes all available disk space.
Description: Restores of VMware backup images do not correctly display VMware data, such as the VM folder, datacenter, etc. This issue occurs when the data contains any characters that are beyond the US-ASCII character set. The backup process has been corrected to store the data properly in the backup image. To restore an image with these characters, you can perform an alternate location restore and select the desired destination information in the Restore Wizard.
NetBackup 7.5.0.4 Emergency Engineering Binary (EEB) listing

The following table contains the known issues that were identified, fixed, and available to our customers in the form of an Emergency Engineering Binary (EEB). NetBackup 7.5.0.4 resolves the addressed issues in each of these EEBs. Additional EEBs may have been released since this document was posted. If you do not see an EEB that you expected to see in this document, contact your Symantec NetBackup Support representative. You can also use SORT for NetBackup to find for which releases an issue has been resolved. See the following link: https://sort.symantec.com/netbackup If you require additional information about an issue in this table, contact your Symantec NetBackup Support representative.
55
Table B-1 Etrack Number

2901521 2748878 2798313 2632959 2811916 2806917 2820840
NetBackup 7.5.0.4 EEB Listing
EEB Description
NetBackup OpsCenter issue. Performance issues with scheduled export of report NetBackup OpsCenter issue. Added a retry that will wait 60 seconds between each retry for the Deport command. Creation of logical volume never completes on RHEL6.2 client during BMR recovery time. NetBackup OpsCenter issue. In NetBackup 7.5, a differential incremental catalog backup may not backup all data that it should In NetBackup 7.5, a differential incremental catalog backup may not backup all data that it should bpstsinfo -comparedbandstu not detecting images confirmed to be ONLY ON STORAGE because it is unable to handle PureDisk MB db basename structure. NetBackup Service Layer issue. NetBackup for VMware issue. NetBackup Service Layer issue. The Advanced Success Rate report does not include multiple stream backups. Job Data Collection goes into a queued state. NetBackup OpsCenter Custom Reports issue. NetBackup OpsCenter issue. nbjm dumps cores sometimes when operating with nbac enabled On Windows, SAP backups of files larger than 4GB fails. SAP backup of files larger than 4GB fail. PDDE package is not upgraded when 7.5.0.3 is installed. SharePoint redirected restore to another farm fails with license errors. Alternate farm restore of web app fails with tar error 0xE000FE3C Before you can back up this resource, you must purchase and install a license key for the appropriate Backup Exec agent.
2825685
2783537
2862841 2777756 2862297 2557732 2703802 2847177 2848281 2831181 2823072 2886257 2873363 2698501 2825330
56

2776387 2880341 2808669 2845830 2882702
NetBackup 7.5.0.4 EEB Listing (continued)
EEB Description
Percentage option not available for Success Rate calculation in Custom Report NetBackup OpsCenter Reports issue. NetBackup OpsCenter Reports issue. NetBackup Deployment Reporting Utilities issue. Restart jobs action is looking for permission 'delete'. Restart fails if permission 'delete' is not granted to jobs object even though a restart permission is granted. bpnbaz individually set permissions do not always work as expected When two backups start on the same Windows client, both bandwidths are halved. Throttling is sometimes not followed when it is set. LIMIT_BANDWIDTH does not work as expected. LIMIT_BANDWIDTH does not work as expected for Windows clients. LIMIT_BANDWIDTH does not work as expected for Windows clients. The bandwidth throttle freezes when a second backup starts on the same Windows client. LIMIT_BANDWIDTH not limiting as expected for Windows clients. Attempt to change vault 'media access port to use' gives status 42 Attempt to change vault 'media access port to use' gives status 42 NetBackup Java User Interface issue. NetBackup Java User Interface issue. NetBackup Java User Interface issue. HPUX 11.31 client with large bundle.dat size fails to import. NetBackup OpsCenter Alerts issue. Deduplication Appliance issue. Deduplication Appliance issue. NetBackup Service Layer issue. NetBackup Java User Interface issue.
2751496 2519076 2645285 2776687 2699258 2744407 2565104 2860482 2792244 2754769 2789162 2824058 2834967 2559533 2814178 2882210 2907550 2782418 2818297
57

2823643 2763529
EEB Description
Expiring compressed images fail to remove the compressed files file data. On a Linux client with an encrypted file system, a Bare Metal Restore backup fails with a status code 1. On a Linux client with an encrypted file system, a Bare Metal Restore backup fails with a status code 1. NetBackup Communication Protocol issue. NetBackup Enterprise Vault agent leaves the Vault Stores in backup mode for the entire duration of backup.It should be unquiesced as soon as snapshot is taken Client name contains a space (most commonly with VMWare guest names) which causes nbrmms.exe to crash (with 'STATUS_INVALID_PARAMETER_AFTER_CALL_c000000d_msvcr80.dll!output_s_l) on target MSDP media server. Consequently AIR Imports never run. Client name contains a space (most commonly found with VMWare guest names) which causes nbrmms.exe to crash every 3-5 minutes on target MSDP media server. Consequently AIR Imports never run. Client name contains a space (most commonly found with VMWare guest names) which causes nbrmms.exe to crash every 3-5 minutes on target MSDP media server. Consequently AIR Imports never run. Client name contains a space (most commonly found with VMWare guest names) which causes nbrmms.exe to crash every 3-5 minutes on target MSDP media server. Consequently AIR Imports never run. Client name contains a space, which causes nbrmms.exe to crash (with 'STATUS_INVALID_PARAMETER_AFTER_CALL_c000000d_msvcr80.dll!output_s_l) every 3-5 minutes on target MSDP media server. Consequently AIR Imports never run. PureDisk issue. Resolves AIR replication issue where during a refresh a replication ocurrs. The replication triggers an import event on the target but its payload file has not been committed to the cache due to the previous cache refresh. Resolves AIR replication issue where during a refresh a replication ocurrs. The replication triggers an import event on the target but its payload file has not been committed to the cache due to the previous cache refresh, NetBackup Deduplication issue. NetBackup OpsCenter Alerts issue.
2847745
2842356 2777715
2770628
2713034
2806900
2815697
2883301
2782901 2805156
2836564
2906797 2843138
58

2837865 2634956
EEB Description
NetBackup OpsCenter Custom Reports issue. Virtual machines with multiple Windows installs do not map all volumes. Changes have been made to allow correct mapping for multi-boot virtual machines. This fix only fixes virtual machines that use boot.ini. The bpbkar process core dumps when a FlashBackup backup is run with the VxFS_Snapshot snapshot method on an HP-UX IA64 11.23 system. The bpbkar process core dumps when a FlashBackup backup is run with the VxFS_Snapshot snapshot method on an HP-UX IA64 11.23 system. NetBackup Flashbackup issue. The bpbkar process core dumps when FlashBackup is run on HP-UX IA64 11.23, and finishes with a status code 130. NetBackup Flashbackup issue. Flashbackup restore on solaris 7.0.1 master server fails with core dump and SIGBUS due to unaligned memory access. 'Images on media' report not showing correct information when KMS/drive encryption is used. 'Images on media' report not showing correct information when KMS/drive encryption is used. 'Images on media' report not showing correct information when KMS/drive encryption is used. The Restore buttton within the Java BAR does not open the 'Restore Marked Files' when using Menu Option Active/Search or icon 'binoculars' unless the resulting directory structure is expanded. In NetBackup 7.1, the bpbkar32.exe executable faults on a Mapped Linux Virtual Machine backup with the logical volume manager (LVM) configured. The Veritas Mapping Service returns an error 4109 when Block Level incremental backups are enabled. The error occurs for incremental backups with the vStorage Application Programming Interface (API) on a large vmdk file. Cannot perform a backup with file mapping on a Linux VM due to a bpdbm crash Cannot perform a backup with file mapping on a Linux VM due to a bpdbm crash Cannot perform a backup with file mapping on a Linux VM due to a bpdbm crash.
2091100
2228059
2852225 2063802
2916430 2638897
2834231
2851032
2832647
2776319
2367085
2115317
2855910 2705452 2815287
59

2780818 2797031 2833456 2771679
EEB Description
Netbackup SQL Agent backed up images not by sorted by date. Type 2 MSDP Isssue also faced in 7.5.0.1 VMware Backups give Status 84 VERITAS Federated Mapping Service issue. VMware incremental backups fail with status 13,84 to MSDP STU only, because of reading same byteoffset for the same file more than once. The schedule tab in policy in Java Admin Console hangs whenever a user overrides the storage selection with a SLP. VMware Intelligent Policy (VIP) VMware jobs failing with 196 or 200 errors when the parent starts before midnight, and the child attempt to run after midnight. KMS backups do not update the KMS tag field in the image header in the catalog. bpimagelist of KMS encrypted backup image show KMS key tag as NULL Backup images with KMS encryption enabled does not list 'Encryption Key Tag' in reports KMS encrypted backups do not update the KMS tag field in the image header in the catalog. bpimagelist of KMS encrypted backup image show KMS key tag as NULL bpbkar crashes when mapping a Linux VM VMware Backups of 2 larger linux VMs are intermittently faulting bpbkar Current Wildcard expansion does not sort the file list. Hence a checkpoint restart job would skip files that get sorted before CPR files but not backed up. Current Wildcard expansion does not sort the file list. Hence a checkpoint restart job would skip files that get sorted before CPR but not backed up. This fix allows an ALT READ server to be included in a SLP with Opt Dupe capable devices even though the ALT READ server is not utilized. This is by design. MDS will determine which media server will run the Optimized duplication. Since upgrading to 7.5 (from 7.1.0.3) most SLPs are not running. The logs state the media servers aren't accessible. NetBackup OpsCenter issue. NetBackup OpsCenter issue. Ops Center incorrectly invokes bpretlevel CLI while collecting data from a NetBackup 6.5.x master server NetBackup OpsCenter issue.
2739820
2823451
2792796
2851012 2819788
2748575 2698601 2711805
2851888
2858615
2719194
2735618 2812351 2809569
2815395
60

2848043 2764452 2772323 2717097 2835941 2649093
EEB Description
NetBackup for VMware issue. 7.5 Upgrade fails due to bpup delays starting Sybase A non-root user cannot perform VM restores from the Java GUI with NBAC enabled. A non-root user cannot perform VM restores from the Java GUI with NBAC enabled NetBackup for VMware issue. BMR experiences occasional problems where 'bpbrm -collect_bmr_info' hangs on Windows media servers, although import process has completed successfully In NetBackup 6.5.5, Bare Metal Restore experiences problems where the 'bpbrm -collect_bmr_info' command freezes on Windows media servers, although the import process successfully completes. In Bare Metal Restore, the 'bpbrm -collect_bmr_info' command freezes on Windows media servers, although the import process successfully completes. NetBackup Accelerator issue. Corrupt .f file causes bpflist to consume CPU/memory until bpdbm process is killed. Tabular Backup Report doesn't filter on Active Policies Modifying SLP parameters in GUI does not pick up previous retention values. Modifying SLP parameters GUI does not pick up previous retention values. nbgre.exe dumps in while restoring a document in 7.5.0.1 nbgre.exe crashes while doing granular restore for a document. nbgre.exe dumps in while restoring a document in 7.5.0.1 VERITAS Federated Mapping Service issue. With NBAC enabled, unable to login and operate NetBackup with a non-root user who does not have write permission in his home directory. On a windows x86 master, processing of very large ndmp image(greater than 50 million) for verification,dup fails with underlying error 'memory map failed.' Attempting to restore from a large NDMP backup can cause bpdbm to fail with status 220 and 'memory map failed.' DSSU Relocation jobs end with a Status 190; Skipping backup id 'it does not contain data'
2331090
2414463
2817435 2780825 2798954 2857559 2780489 2825320 2807759 2771250 2867910 2675034
2882171
2603300
2785499
61

2827485 2818929 2824762 2776037 2810891 2836629
EEB Description
Duplication jobs end with a Status 190; Skipping backup id 'it does not contain data' Active Directory Granular Backups fail when doing Cumulative or Differential backups. Active Directory Granular Backups fail when performing Cumulative or Differential backups. Active Directory Granular Backups fail when performing Cumulative or Differential backups. Active Directory Granular Backups fail when performing Cumulative or Differential backups. Correct an issue with low dedupe rates on NDMP EMC client backups which have files with an alternative data streams(ADS) header type. Correct an issue with low dedupe rates on NDMP EMC client backups which have files with an alternative data streams(ADS) header type. Nbcatsync does not recognize images stored somewhere other than a directory named db/images. Unable to renew credential obtained by bpnbat -login Fix provides new option bpnbat -RenewCred [-cf file] Exchange restore fails with an SC 37 if a FQDN name is used. The problem can be seen in bpbkar and bpfis log during backup time that if FQDN is used then the FQDN is getting appended twice. STS reset has issues of event from PureDisk. communicating issue between PureDisk and NetBackup sts API. NetBackup Disk issue. NetBackup can have performance problems due heavy use of stat's on config and license files. Image Cleanup fails with Status 174 when 'incompatible segment size 1' is found on a corrupt DO. Deduplication Appliance issue. When the nbdeployutil Capacity report is run against multiple master servers the Summary tab has incorrect values for capacity figures. Capacity licencing report shows wrong size after upgrade to OCA 7.5.0.1 NetBackup OpsCenter issue.
2854954
2760065
2782546
2754057
2839225 2824098 2907417 2643743
2785439
2845277 2830369
2834734 2903819
62

2746427
EEB Description
Calendar schedules run multiple times if retry after run day is set and backup window spans midnight. Bpbkar crashes when backing up 3 RHEL VM machines. VERITAS Federated Mapping Service issue. Java GUI does not restore files contained in a directory with meta-character '*' in the name. A Verify of Exchange Info Store backup fails because of a raw partition size mismatch in the catalog and the tar header. A Verify of Exchange Info Store backup fails because of a raw partition size mismatch in the catalog and the tar header. This EEB will resolve an issue with the verify of Exchange images on a Unix media server when the Exchange images contain total log files for a database over 1 GB in size. VERITAS Federated Mapping Service issue. VxMS does not map one of the two volumes in a Linux VM. Restores of 2.5 million files are processed for over 17 hours in the bpdbm program before they go active. Restores of 2.5 million files are processed for over 17 hours in the bpdbm program before they go active. Customer is requesting a 7.1.0.4 EEB from ET2661839. FlashBackup restores of millions of files are queued for many hours before they go active. Restores of 2.5 million files are processed for over 17 hours in the bpdbm process before they go active. Restores of 2.5 million files are processed for over 17 hours in the bpdbm process before they go active. Restores of 2.5 million files are processed for 17+ hours in bpdbm before going active APP_2.0.2 code. Restores of 2.5 million files are processed for 17+ hours in bpdbm before going active. in some instances snapshots are left behind Intermittently nbpem will become unresponsive to nbpemreq commands and/or schedule jobs later than expected
2751253 2852917 2597039 2659936
2644017
2780752
2824075 2770725 2373499
2421597
2815601 2526473 2679107
2661839
2753077
2863127 2730066 2721045
63

2797547
EEB Description
Fix for PEM_USE_SAME_HOST_BY_NAME environment variable not being honored. Now the environment variable PEM_USE_SAME_HOST_BY_NAME can be disabled to stop the alias name lookups. SLP duplications not using NDMP direct copy. SLP duplications not using NDMP direct copy. NetBackup OpsCenter Alerts issue. Incremental DFSR backups via Windows Shadow Copy Component path are forced into FULL backups. Folders or files with non-ASCII characters (UTF8) such as German letters with umlaut will not restore properly from the Java GUI on a Windows client. Folders or files with non-ASCII characters (UTF8) such as German letters with umlaut will not restore properly from the Java GUI on a Windows client. Folders or files with non-ASCII characters (UTF8) such as German letters with umlaut fail to restore from the Java GUI. Cannot restore folders or files with non-ASCII characters (UTF8) such as German letters with umlaut Cannot restore folders or files with non-ASCII characters (UTF8) such as German letters with umlaut The 7.5 NetBackup Windows installers are unable to import hosts from a list on Windows 2008 and later. in some cases NDMP Backups to an OST device will cause restore failures NetBackup NDMP issue. NetBackup Service Layer issue. When browsing for NDMP backup entities via Java GUI, it goes into the spinning clock and hangs. NetBackup Java User Interface issue. Long running SAP backups fails with status 6 Unable to use SAN Client feature due to missing drivers during packaging. Synthetic backups using SLP storage do not use the correct image retention period.
2807509 2842910 2717950 2776057
2795505
2803245
2750024
2796782
2796777
2750798
2532142 2825785 2836252 2722564
2837758 2680782 2826987 2849844
64

2707600
EEB Description
FORCE_RESTORE_MEDIA_SERVER is not honoured when restoring VM from a set of backup images. In Device Configuration Wizard when selecting a media server and just one NDMP host to scan, resulting screen shows robots connected to all NDMP hosts. A one-time script was created to address a specific condition. The script will not be included in any other release vehicle. lifecycles using 'expire after copy' restart nbstserv,initial recovery session,'couldn't find source copy'; fault soon after The log entry couldn't find source copy, not an error; processing following is the problem After upgrade to NB 7.5.0.3 (from 7.1.0.4) multiple bpdbm processes appear to be using excessive CPU time. AIX Master server and Media servers are sending DNS-queries to the top- www.domain. AIX Master server and Media servers are sending DNS-queries to the top- www.domain. AIX Master server and Media servers are sending DNS-queries to the top- www.domain. AIX 5.3 and 6.1 see unusual DNS queries to the top domain when NetBackup is running. AIX Master server and Media servers are sending DNS-queries to the top- www.domain. Fixed the issue of Day window filter selection criteria not working correctly for some combinations for custom report. This bundle contains many fixes for VMware. This bundle contains many fixes for VMware. This bundle contains many fixes for VMware. This bundle is a 7.1 hotfix combination of ET 2299772, ET 2256525, ET 2145207, and ET 2281357. Large virtual machines cannot be restored because of a disconnected idle socket between the bprd and bpbrm processes. This is a NetBackup 7.1.0.2 Data Mover EEB Bundle. BMR experiences occasional problems were 'bpbrm -collect_bmr_info' hangs on Windows media servers, although import process has completed successfully This is a bundle of Windows client fixes for 7.1.0.4.
2740977
2865861
2860243
2832342
2732327 2765089 2875138 2839340 2703874 2745523
2193082, version 1 2207676, version 1 2299772, version 3, 2 2394770, version 1
2478683, version 1
2535076, version 3 2653356, version 2, 1
2769877, version 1
65

2785535, version 4
EEB Description
PEM crashes running vmware VIP backups.
2792621, version 3, 2, OST Direct Copy duplication jobs from Quantum DXi to tape fail with status 85 on second 1 fragment. The last file of OST Direct Copy duplications of non-Network Data Management Protocol images can be corrupt under certain tuned buffer size settings. 2820447, version 2, 1 NetBackup Service Layer issue.
2829119, version 3, 2, A differential incremental catalog backup may not backup all data that it should. Expiration 1 of catalog compressed images will not delete the compressed catalog data. 2836642, version 1 NetBackup Data Mover issue.
2838857, version 4, 3, NetBackup Systems Management (Policies, Scheduling, and so forth.) issue. 2, 1 2874026, version 1 2876501, version 1 2921761, version 1 NetBackup Systems Management (Policies, Scheduling, and so forth.) issue. SLP bundle for 7.5.0.3 NetBackup Deduplication issue.
66

NB 7504 Release Notes

Uploaded by

Document Information

Original Description:

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

NB 7504 Release Notes

Uploaded by

Copyright:

Available Formats

Symantec NetBackup 7.5.0.

About Symantec Operations Readiness Tools

Contacting Technical Support

Licensing and registration

Support agreement resources

Platform compatibility ....................................................... 11

Product dependencies ........................................................ 17

Operational notes ................................................................ 25

End-of-life notifications ..................................................... 33

About the current release content index ........................ 35

About the current release content ................................... 37

New features and enhancements

About NetBackup 7.5.0.4 new features and enhancements

About NetBackup 7.5.0.4 new features and enhancements

About NetBackup 7.5.0.x release compatibility NetBackup compatibility lists

About NetBackup 7.5.0.x release compatibility

About software release types

Platform compatibility About NetBackup 7.5.0.x release compatibility

About compatibility with NetBackup 7.5

Platform compatibility NetBackup compatibility lists

NetBackup master server

NetBackup compatibility lists

Platform compatibility NetBackup compatibility lists

Platform compatibility NetBackup compatibility lists

Platform compatibility NetBackup compatibility lists

About product dependencies Operating system patches and updates

About product dependencies

Operating system patches and updates

Product dependencies Operating system patches and updates

Table 3-1 Operating system type and version

Operating system patches and updates for NetBackup Notes

AIX 5.3 TL12 SP2 (5300-1202-1036)

AIX 6.1 TL5 SP5 (6100-05-02-1034)

Product dependencies Operating system patches and updates

Table 3-1 Operating system type and version Patch

Operating system patches and updates for NetBackup (continued) Notes

For HP-UX PA-RISC platforms, this fileset is required:

For HP-UX PA-RISC platforms, this fileset is required:

For HP-UX PA-RISC platforms, this fileset is required:

Product dependencies Operating system patches and updates

Table 3-1 Operating system type and version Patch

Operating system patches and updates for NetBackup (continued) Notes

Product dependencies Operating system patches and updates

Table 3-1 Operating system type and version Patch

Operating system patches and updates for NetBackup (continued) Notes

PHSS_37202 QPK1131 (B.11.31.0809.326) patch bundle

SUSE Linux Enterprise Server 10 x64

SUSE Linux Enterprise Server 10 update 2

Solaris 9 SPARC 64-bit client

111712-11 (or greater)

Product dependencies Operating system patches and updates

Table 3-1 Operating system type and version Patch

Operating system patches and updates for NetBackup (continued) Notes

Recommended OS Patchset dated June 2011 or later

Product dependencies Operating system patches and updates

Table 3-1 Operating system type and version

Operating system patches and updates for NetBackup (continued) Notes

139556-08 (Change Request ID - 6723423) 119964-21 (Change Request ID - 6815915)

Windows XP x86-32 Windows XP x86-64 Windows Vista x86-32

KB936357 KB928646 KB936357 KB952696

Windows Vista x86-64

Product dependencies Operating system patches and updates

Table 3-1 Operating system type and version Patch