NB 7506 Release Notes

Symantec NetBackup 7.5.0.
6 Release Notes
NetBackup 7.5.0.6
Maintenance Release Update
Symantec NetBackup 7.5.0.6 Release Notes

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.6
Legal Notice
Copyright 2013 Symantec Corporation. All rights reserved. Symantec, the Symantec Logo, the Checkmark Logo and NetBackup 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. This Symantec product may contain third party software for which Symantec is required to provide attribution to the third party (Third Party Programs). Some of the Third Party Programs are available under open source or free software licenses. The License Agreement accompanying the Software does not alter any rights or obligations you may have under those open source or free software licenses. Please see the Third Party Legal Notice Appendix to this Documentation or TPIP ReadMe File accompanying this Symantec product for more information on the Third Party Programs. 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 website 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: https://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. NetBackup Future Platform and Feature Plans Use this tool to get information about what items Symantec intends to replace with newer and improved functionality, and what items Symantec intends to discontinue without replacement. Some of these items include certain NetBackup features, functionality, 3rd-party product integration, Symantec product integration, applications, databases, and the OS platforms.
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 ............................................................................................... 4 Chapter 1 New features and enhancements ...................................... 9

About NetBackup 7.5.0.6 new features and enhancements ..................... 9 NetBackup 7.5.0.6 new features ...................................................... 10 Date and time range option for Backup, Archive, and Restore .......................................................................... 10 NetBackup 7.5.0.6 new enhancements and support ............................. 10
Chapter 2
Platform compatibility ....................................................... 13

About NetBackup 7.5.0.x release compatibility .................................. About software release types .................................................... About compatibility with NetBackup 7.5 ..................................... NetBackup compatibility lists ......................................................... 13 13 14 16
Chapter 3 Chapter 4
Product dependencies ........................................................ 19

Operating system patches and updates ............................................. 19
Operational notes ................................................................ 29

About NetBackup 7.5.0.6 operational notes ....................................... Installation and upgrade notes ....................................................... General NetBackup 7.5.0.6 notes ..................................................... Bare Metal Restore notes ............................................................... Cloud storage notes ...................................................................... Database and application agent notes .............................................. Creating a minimal NetBackup account for Exchange operations (Exchange 2010 and later) .................................................. Deduplication notes ...................................................................... About upgrading MSDP and PureDisk deduplication solutions ........................................................................ OpsCenter notes .......................................................................... NetBackup Search notes ................................................................ About upgrading Search to NetBackup 7.5.0.x ............................. Virtualization notes ...................................................................... 29 30 32 34 35 35 37 38 39 41 45 45 45
Contents
Chapter 5 Appendix A
End-of-life notifications ..................................................... 49

About future NetBackup end-of-life notifications ............................... 49
About the NetBackup 7.5.0.6 release content .............. 51

About NetBackup release content .................................................... About release content conventions .................................................. NetBackup 7.5.0.6 release content ................................................... NetBackup 7.5.0.6 Emergency Engineering Binary (EEB) listing ............ 51 51 52 55
Chapter
New features and enhancements

This chapter includes the following topics:

About NetBackup 7.5.0.6 new features and enhancements NetBackup 7.5.0.6 new features NetBackup 7.5.0.6 new enhancements and support
About NetBackup 7.5.0.6 new features and enhancements

In addition to a small number of new features, NetBackup 7.5.0.6 offers many enhancements to the issues and improvements from previous NetBackup releases. Information about the new features and enhancements in this release of NetBackup can be found in the following sections of this chapter. This release incorporates fixes to several known issues that existed with NetBackup. Many of these issues pertain to the customer-specific issues that have been documented in the form of Titan or Salesforce.com (SFDC) cases. Many of the fixes that are incorporated into this release are available as individual engineering binaries and engineering bundles (EEBs). These EEBs were created to address specific customer issues with a previous version of NetBackup. This maintenance release document lists those engineering binaries and bundles. See NetBackup 7.5.0.6 release content on page 52. See NetBackup 7.5.0.6 Emergency Engineering Binary (EEB) listing on page 55.
10
New features and enhancements NetBackup 7.5.0.6 new features
NetBackup 7.5.0.6 new features

The following subsections describe the new features that can be found in the NetBackup 7.5.0.6 release.
Date and time range option for Backup, Archive, and Restore
A new date and time range feature has been added to the Specify NetBackup Machines and Policy Type dialog box in the Backup, Archive, and Restore interface. You can use this feature to filter the exact date and time range for backup images. The default settings are set to Oldest available and Newest available. If you leave the default settings checked, all the images available for restore are displayed. When you specify a date and a time range, you can reduce the amount of time it takes to retrieve backup images available for restore. The following description details how you can customize date and time ranges to suit your needs.
From: Select how far back in time you want to filter for backup images available for restore. If you need the filter to include all images back to the oldest image, leave Oldest available checked. Select how far forward in time you want to filter for backup images available for restore. If you need to filter up to the newest image, leave Newest available checked.
To:
NetBackup 7.5.0.6 new enhancements and support

The NetBackup 7.5.0.6 release offers the following new enhancements and support:
Platform support for the following operating systems:

Windows 8 client (x86-64 only) Windows Server 2012 client Note: The NetBackup client software can only be installed on Windows 8/Server 2012 using a special full installation package. See Installation and upgrade notes on page 30.
Support for the following database and application agents:
SAP HANA
New features and enhancements NetBackup 7.5.0.6 new enhancements and support
11
The NetBackup for SAP database agent implements the BACKINT interface for SAP HANA and integrates the backup and the recovery management capabilities of NetBackup. The agent supports single- and multi-node deployment of HANA appliances. The SAP HANA agent implementation works on all vendor HANA appliances that have HANA version 5, revision 46 or higher. See Database and application agent notes on page 35.
DB2 10.1 is supported in this release with snapshot compatibility. For the most up-to-date DB2 snapshot compatibility information, see the NetBackup 7.x Snapshot Client Compatibility List on the Symantec Support website. http://www.symantec.com/docs/TECH59978 Exchange 2013 (database only) Granular Recovery Technology (GRT) and off-host backups are not supported with this release. Note: Symantec NetBackup recommends installing Exchange 2013 Cumulative Update 1 to ensure that you have the latest software and bug fixes. SharePoint 2013 (database only) Granular Recovery Technology (GRT) is not supported with this release. Exchange 2010 SP3 on Windows 2008 R2 and Windows 2012. In this release, for NetBackup operations with Exchange 2010 or 2013 you can now use a minimal mailbox account that has local administrator rights rather than Exchange administrator rights. See Creating a minimal NetBackup account for Exchange operations (Exchange 2010 and later) on page 37.
Support for the following virtualization technologies:
Hyper-V for Windows Server 2012. Note: Hyper-V for Windows Server 2012 is supported with some limitations. See Virtualization notes on page 45.
Other new enhancements and support:
NetBackup has been enhanced to provide better integration with the PureDisk Deduplication Option (PDDO). These enhancements include:
12
New features and enhancements NetBackup 7.5.0.6 new enhancements and support
An abnormal state event is written to the NetBackup error log when a PureDisk storage pool enters an abnormal state. Better job scheduling for PDDO->PDDO Auto Image Replication and optimized duplication. Jobs are prevented from starting until the source storage pool is no longer overloaded.
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 website. For more information about platform compatibility, see the following documents on the Symantec Support website:
NetBackup 7.5 Release Notes for UNIX, Windows, and Linux 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 we 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. These release types and number scheme are used by the NetBackup products and the NetBackup Appliance products.
A major release is the first in a series of releases. This type of release contains new features, new supported platforms, and a complete set of the latest product documentation.
14
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.5 or 7.5. 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 software release update is a double-dot release, for example 2.5.1 or 7.5.x. This release type may contain a few new features and enhancements as well as many product fixes. Only those documents that are applicable to the new features or enhancements are updated and republished. A maintenance release update is a triple-dot release, for example 2.5.0.x or 7.5.0.2. This release type is primarily comprised of a number of fixes that are developed to address issues in major, minor, and software update releases. This release type may also include a small number of new features, enhancements, and platform or application proliferations. The only documentation that is provided is an online Readme and a release notes document that is available on the Symantec Support website.
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 clients within the same environment. For NetBackup and the NetBackup Appliances, you can apply a maintenance release (for example 7.5.0.1) to a media server or client within an environment where your master server is at a version level of 7.5. This same scenario can apply to the maintenance releases 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 website. http://www.symantec.com/docs/TECH136970 Symantec NetBackup does not support any scenario where a minor release or software release update is at a higher version level than the parent server. For instance, the following examples apply.
If a master server is at 7.5, then the media servers and clients 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 clients 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 (this version does not exist; it is for example only), then the media servers and clients cannot be at a double-dot version level that is higher than 7.5.1, such as 7.5.2.
Platform compatibility About NetBackup 7.5.0.x release compatibility
15
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
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
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
NetBackup client
7.0 7.0, 7.0.1 7.0, 7.0.1, 7.0.2 7.0, 7.0.x, 7.1, 7.1.0.x 7.0, 7.0.x, 7.1, 7.1.0.x 7.0, 7.0.x, 7.1, 7.1.0.x 7.0, 7.0.x, 7.1, 7.1.0.x 7.0, 7.0.x, 7.1, 7.1.0.x 7.0, 7.0.x, 7.1, 7.1.0.x, 7.5 7.0, 7.0.x, 7.1, 7.1.0.x, 7.5, 7.5.0.x Note: NetBackup 7.5.0.2 is the version that the NetBackup Appliance 2.5 software release is based on. NetBackup 7.5.0.2 is not a standalone version of NetBackup. 7.0, 7.0.x, 7.1, 7.1.0.x, 7.5, 7.5.0.x 7.0, 7.0.x, 7.1, 7.1.0.x, 7.5, 7.5.0.x 7.0, 7.0.x, 7.1, 7.1.0.x, 7.5, 7.5.0.x 7.0, 7.0.x, 7.1, 7.1.0.x, 7.5, 7.5.0.x
7.5 7.5 7.5 7.5
7.5.0.3 7.5.0.4 7.5.0.5 7.5.0.6
Note: Support for the NetBackup 6.x product line ended October, 2012.
16
Platform compatibility NetBackup compatibility lists
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 and information:
Symantec recommends that you use Symantec Operations Readiness Tools (SORT) to help you locate the latest platforms, peripherals, drives, and libraries. To access SORT, go to the following Web page: 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 - NetBackup Master Compatibility List The following items describe each of the compatibility lists that are available.
NetBackup Enterprise Server and Server 7.x Hardware Compatibility List This list includes information for compatible drives, libraries, virtual tape devices, robot-types, fibre-channel HBAs, switches, routers, bridges, iSCSI configurations, and encryption devices. Other compatibility information includes the following:

NetBackup Appliances AdvancedDisk arrays OpenStorage (OST) solutions Tape drives Fibre Transport media server host bus adapters (HBAs) Virtual tape libraries (VTLs) Network Data Management Protocol (NDMP) devices Tape libraries Encryption and security solutions
NetBackup Enterprise Server and Server 7.x Hardware Compatibility List
17
This list includes information for compatible drives, libraries, virtual tape devices, robot-types, fibre-channel HBAs, switches, routers, bridges, iSCSI configurations, and encryption devices. This list includes information about the compatible drives, robot types, switches, routers, and bridges, and iSCSI configurations that coincide with several hardware setups, including the following:

NetBackup Appliances AdvancedDisk arrays OpenStorage (OST) solutions Tape drives Fibre Transport Media Server Host bus adapters (HBAs) Virtual tape libraries (VTLs) Network Data Management Protocol (NDMP) devices Tape libraries Encryption and security solutions
NetBackup 7.x Database and Application Agent Compatibility List This list contains the most current compatibility information for the database agents and application agents that are supported on specific operating systems and CPU architectures. NetBackup 7.x Snapshot Client Compatibility List This list contains the most current server and client snapshot compatibility information that is sorted by arrays, agents, operating systems, and VSS providers. NetBackup 7.x Cluster Compatibility List This list contains the most current compatibility information for the cluster types and versions that are supported on specific operating systems and CPU architectures. Statement of support for the importing of Backup Exec images in NetBackup 7.x using the Backup Exec Tape Reader Support for NetBackup 7.x in virtual environments This list contains the most current compatibility information for NetBackup in virtual environments.
18
Chapter
Product dependencies
Operating system patches and updates
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 minimum patch level. For more extensive information about NetBackup compatibility including compatible operating systems, applications, and hardware, see the NetBackup Master Compatibility List on the Symantec Support website. http://www.symantec.com/docs/TECH59978 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. 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.
Patch
AIX runtime libraries 8.0.0.10 or 9.0.0.3 or later xlC.rte 8.0.0.10 fileset
20
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

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.
AIX 5.3 TL12 SP2 (5300-1202-1036)
AIX 6.1
AIX 6.1 TL5 SP2 (6100-05-02-1034)
NetBackup 7.5 requires the AIX 6.1 TL5 SP2 (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 Networking.NET2-RUN: /usr/lib/hpux64/libipv6.so.1 Networking.NET2-RUN: /usr/lib/libipv6.1
21
Table 3-1 Operating system type and version

HP-UX PA-RISC

For HP-UX PA-RISC platforms, this fileset is required:
Patch
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
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. 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.
PHSS_27740 PHSS_26560 PHSS_32864
PHKL_26233
22

PHSS_35379

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. http://h20565.www2.hp.com/portal/site/hpsc/public/
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 recommendation applies to HP PA-RISC 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. That is a recommended critical patch from HP that NetBackup requires, particularly when you attempt to run NetBackup with NetBackup Access Control (NBAC).
PHSS_34858
PHKL_31500
23

PHSS_37492

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

QXCR1000593999: dld emits assert messages for chatr +mem_check enabled 64-bit executables
HP-UX 11.31
PHSS_37202 QPK1131 (B.11.31.1003.347a) patch bundle
This patch is required for JAVA 6.0. This patch bundle is required for NetBackup media server support. It is an HP-UX March 2010 patch bundle. Change Request ID - 6815915
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.
24
Recommended patch set - dated Symantec recommends that you download the patch June 2011 or newer set dated June 2011 (or newer) from the Oracle Support website. https://support.oracle.com The patch set contains the following minimum recommended patches:
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 recommended 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)
25
Table 3-1 Operating system type and version

Solaris 10 x86-64
Patch
Recommended patch set - dated Symantec recommends that you download the patch 12/28/2011 or newer set dated 12/28/2011 (or newer) from the Oracle Support website. https://support.oracle.com The patch set contains the following minimum recommended 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)
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)
SUSE Linux Enterprise Server 10 x64
Service Pack 2 or newer
The operating system version must be SUSE Linux Enterprise Server 10 SP2 or newer to run NetBackup 7.0. Microsoft microcode reliability update. Hot fix for PBX connection attempt hangs. 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.
Windows XP x86-32 Windows XP x86-64 Windows Vista x86-32
KB936357 KB928646 KB936357 KB952696
Windows Vista x86-64
KB936357 KB952696
Windows Server 2003 IA64 KB913648 (SP1 & SP2)
26

KB928646 Windows Server 2003 x86-32 (SP1 & SP2) KB883646

Hot fix for PBX connection attempt hangs. Microsoft Storport hot fix.
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 PBX connection attempt hangs. 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 to improve TCP loopback latency and UDP latency 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.
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 (SP2) KB979612
Windows Server 2008 R2 (SP1)
KB2265716
KB982383
KB983544
27

KB979612

Hot fix to improve TCP loopback latency and UDP latency
28
Chapter
Operational notes

About NetBackup 7.5.0.6 operational notes Installation and upgrade notes General NetBackup 7.5.0.6 notes Bare Metal Restore notes Cloud storage notes Database and application agent notes Deduplication notes OpsCenter notes NetBackup Search notes Virtualization notes
About NetBackup 7.5.0.6 operational notes

The NetBackup 7.5.0.6 maintenance release update 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.6 operations that may not be documented elsewhere in the NetBackup documentation set. This document is posted on the Symantec Support website and may be updated after the GA release of NetBackup 7.5.0.6. Therefore, Symantec
30
Operational notes Installation and upgrade notes
recommends that you refer to the following document on the Symantec Support website to view the latest release information. http://www.symantec.com/docs/DOC6396
Installation and upgrade notes

This section contains the operational notes and known issues that are associated with the installation and upgrades of NetBackup in this release.
If you are a NetBackup MSDP or PureDisk user, please review the following section before you upgrade: See About upgrading MSDP and PureDisk deduplication solutions on page 39. If you are a NetBackup Search user, please review the following section before you upgrade: See About upgrading Search to NetBackup 7.5.0.x on page 45. Note: Additional steps are required before and after you install NetBackup 7.5.0.6 OpsCenter and OpsCenter Analytics Server on Solaris Cluster. Before you attempt installation, please review the following Technote on the Symantec Support website: http://www.symantec.com/docs/TECH207395 If the extra post-installation steps are not followed, the OpsCenter services do not start after an upgrade to NetBackup 7.5.0.6. Windows 8/Server 2012 require a special full installation package. For all other supported platforms (including other versions of Windows), NetBackup 7.5 must be installed before you can upgrade to version 7.5.0.x. However, installing NetBackup on Windows 8/Server 2012 is not supported for versions before version 7.5.0.6. To install NetBackup on Windows 8/Server 2012, you must use the special full installation package of NetBackup. This installation package brings the client directly to 7.5.0.6 and is not meant for any other Windows operating system.
The special full installation package is a client-only package for all x64 editions of Windows 8/Server 2012. Media server or master server installations are not available. Windows 32-bit OS installations are not supported. The package is to be installed on an NTFS file system. While the ReFS file system is supported as a backup entity, installing this client package on ReFS is not supported.
Operational notes Installation and upgrade notes
31
The package is to be used with server environments of NetBackup 7.5 or later. The following list contains some of the limitations that apply to this package. For more complete information on NetBackup limitations for Windows 8/Server 2012, see the NetBackup Master Compatibility List on the Symantec Support website. http://www.symantec.com/docs/TECH59978

BMR Client/Boot Server is not supported. Client Direct/Client Side Dedupe/MSDP/PDDO are not supported. Remote VSS (a new Windows Server 2012 feature) is not supported. The files on an NTFS deduplication volume are backed up in full and not in optimized form. Restoring the files that are backed up from an NTFS file system to an ReFS file system is not supported. As a workaround, it is possible to restore to an NTFS file system, remove the attributes that ReFS does not support, and then copy the files to the ReFS file system VMware Backup Host is not supported. File-level recovery from a Hyper-V backup is not supported when:

The file originates from a Resilient File System (ReFS) volume, or The virtual machine is composed of VHDX file(s).
Remote Administration Console is not supported on Windows 8/Server 2012. Java Windows Administration Console is not supported on Windows 8/Server 2012. LiveUpdate is not supported on Windows 8/Server 2012 for NetBackup 7.1.0.4 to 7.5.0.6 upgrade path.
Note: Due to technical limitations, the regular Windows Installer (both x86 and x64) does not prevent installation on Windows 8/Server 2012, even though this method is not supported. The only supported method of installing NetBackup on Windows 8/Server 2012 is to use the special 7.5.0.6 x64 full installation package. NetBackup is migrating to a simplified client name for Windows clients. The new client selection Windows will be used for all supported Windows clients, regardless of the specific Windows version of the client. In future
32
Operational notes General NetBackup 7.5.0.6 notes
releases, specific Windows version choices will be eliminated. As part of this migration, the client selection Windows may or may not appear in the client selection menus. Please choose the new Windows menu selection for the appropriate architecture (x86 or x64). If the Windows selection is not available, please select the specific Windows version. Note: If the Windows selection is not available when adding a Windows 8/Server 2012 through any of the NetBackup interfaces, choose the Windows 7 or Windows 2008 menu selection. To install NetBackup Windows client software remotely, the system must meet certain configuration requirements. One of the requirements is that the Remote Registry service be started on the remote system. Starting with NetBackup 7.5.0.6, the NetBackup installer can enable and start the Remote Registry service on the remote system. If the Remote Registry service is not started, the installation receives the following error message:
Attempting to connect to server server_name failed with the following error: Unable to connect to the remote system. One possible cause for this is the absence of the Remote Registry service. Please ensure this service is started on the remote host and try again.
General NetBackup 7.5.0.6 notes

This section contains the general operational notes and known issues that are associated with this release of NetBackup.
An issue can occur if a NetBackup Network Data Management Protocol (NDMP) backup policy is configured with the directive set type=tar in the backup selection. Parent directories in the path of a file that an incremental NDMP backup saves may not be present in the backup image. For more information on this issue, refer to the following Technote on the Symantec Support website: http://www.symantec.com/docs/TECH202412 Network Data Management Protocol (NDMP) backup performance is adversely affected when the logging level is set to 4 or 5. The performance effect may be serious enough to cause NDMP backup failures. Symantec recommends that you set to the logging level to 3 or lower to avoid this issue. When the Rackspace plug-in is used on a host running Windows Server 2008 R2 with IPv6 enabled, NetBackup may experience network connection issues.
Operational notes General NetBackup 7.5.0.6 notes
33
Symantec recommends that you disable IPv6 on Windows Server 2008 R2 hosts that use the Rackspace plug-in.
NetBackup Windows Client backups fail when NetApp and CIFS shares are configured with certain security and access privileges. If a NetApp volume is configured with a Mixed security style and is used with a NetApp CIFS share that does not give read access to the client user, then client backups fail. This issue only occurs when the NetApp volume is configured with the Mixed security style. This issue does not affect the volumes that are configured with NTFS or UNIX styles.
A workaround for this issue is to add explicit read access on the CIFS share to the user under which the NetBackup client service is running.
If any file named "program" exists in the root directory of the Windows system drive, such as C:\, NetBackup does not function properly. Any such file must be removed or renamed before NetBackup can execute command lines and process creation options. Database configuration parameters USEREXIT and LOGRETAIN have been deprecated and are no longer valid in DB2 10.1 and later. Instead, LOGARCHMETH1 sets the user exit program settings. All session log files that are located in the sidxxx/logs directory in NetBackup Vault have public write permission. That allows all processes to write to the log files. The following is the path for the logs directory on Windows and UNIX servers:
Windows:
install_path\NetBackup\vault\sessions\vault_name\sidxxx\logs\
UNIX: /usr/openv/netbackup/vault/sessions/vault_name/sidxxx/logs/
Here vault_name is the name of the vault that is used for the session and xxx is the unique session ID.
After an upgrade to NetBackup 7.5.0.6, 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)
34
Operational notes Bare Metal Restore notes
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.
Bare Metal Restore notes

This section contains the operational notes and known issues that are associated with Bare Metal Restore in this release of NetBackup.
If the backed up file system is encrypted for RHEL, then when the system is restored with the BMR option, the existing encryption is removed. When the /etc/mke2fs.conf file is restored, the restore task is shown as partially completed on the Activity Monitor tab in the NetBackup Administration Console. The issue occurs on RHEL6 Update 2 platforms and later, and it occurs even though the BMR 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 BMR environment after the file is restored. 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
Issues may occur after BMR restore is performed on Red Hat Enterprise Linux 6. After the completion of a BMR Linux restore task, the system may display 'Kernel Panic' when it looks for a grub menu. The system may also go into maintenance mode during the first restart. These issues occur because the UDEV daemon dynamically detects devices, causing discrepancies with disk names and ordering in various configuration files across restarts. If you encounter this issue, please contact Symantec Technical Support and have your support representative reference the following technotes: TECH201332 and TECH179048.
Operational notes Cloud storage notes
35
Cloud storage notes

This section contains the operational notes and known issues that are associated with cloud storage in this release of NetBackup.
An issue occurs where only the master server gets listed in the Cloud Storage Server Configuration Wizard. The same issue causes the Cloud Storage to only be visible for the master server under media server host properties. The issue occurs when a new Windows NetBackup Administration Console session is started or if the master server NetBackup Service Layer (NBSL) service is restarted. The issue results from the media servers getting scanned for cloud support when the Cloud Storage Configuration Wizard or a media server host properties window is opened for the first time. If you have several media servers in your environment, they may not be displayed initially. To work around this issue, quit and exit the Cloud Storage Configuration Wizard or media server host properties window. Wait about 2-4 minutes (depending on how many media servers you have configured) and then reopen the wizard or the media server host properties window. The media servers should appear when it is reopened. If the media servers are still not listed upon reopening the wizard, quit the wizard again and repeat the waiting period until they appear. Beginning with this release, you can create disk pools on the Amazon Simple Storage service regardless of the region in which the storage is located. To create disk pools in regions outside of the United States, all of the NetBackup media servers that have access to the storage must be at release 7.5.0.6. Symantec recommends that you upgrade all of your NetBackup media servers to release 7.5.0.6.
Database and application agent notes

This section contains the operational notes and known issues that are associated with database and application agent support in this release of NetBackup.
An issue can occur where you cannot perform a restore of a full backup plus an incremental backup (differential or cumulative). The restore of the full backup is successful, but the restore of the incremental fails with the following error in the tar32 log:
11:48:38.468 [11800.15932] <2> beds_ese_access:: V_PrepareForRestore(): ERR - Error calling RestorePrepare (0xE000FED1:A failure occurred querying the Writer status. See the job log for details about the error.
36
Operational notes Database and application agent notes
For the VMware backups that protect SQL Server, note the following:
A SQL Server database name cannot contain any of the following characters: ?*\" To use Replication Director to manage your VMware snapshots and snapshot replication with SQL Server 2012, logon account changes may be required. Logon accounts for the NetBackup Client Service must have access to the CIFS shares that are created on the NetApp disk array. Change the logon account for the NetBackup Legacy Network Service to an account that has the fixed server role sysadmin. For SQL 2012 on Windows Server 2008/2012, the account that runs the Microsoft SQL Server Service must have full permissions for the NetBackup Legacy Network Service temp directory. This directory is C:\Users\user\AppData\Local\Temp, where User is the account that runs the NetBackup Legacy Network Service.
For Hitachi and IBM HANA appliances, you need to add an extra lib: libelf.so.0. Refer to the NetBackup for SAP Administrator's Guide for further details. Backups and restores for HANA are initiated from the SAP HANA Studio and not from the NetBackup Administration Console. Since SharePoint metadata is stored outside of the content database, it cannot be restored using Granular Recovery Technology (GRT). You can, however, use GRT to restore SharePoint data with metadata attached to it. As long as the metadata resides in the same service application, SharePoint maintains the link between the two items. NetBackup does not support restoring mailbox items into tenant mailboxes in a multi-tenant Exchange environment. To recover items pertaining to a tenant mailbox, redirect the recovery to a non-tenant mailbox. Backup and recovery of Exchange Server databases are fully supported in a multi-tenant environment. NetBackup does not support Granular Recovery Technology (GRT) with Microsoft SharePoint Server backups in a multi-tenant SharePoint environment. Backup and recovery of SharePoint Server databases are fully supported in such an environment. The NetBackup for Exchange and NetBackup for SharePoint Agents support a restore to the same Microsoft service pack (SP) or cumulative update (CU) on which the backup was originally created. Microsoft sometimes introduces database schema changes in SPs or CUs. If you restore to a different SP or CU level, the database server may not operate correctly.
Operational notes Database and application agent notes
37
Creating a minimal NetBackup account for Exchange operations (Exchange 2010 and later)
This procedure describes how to create a minimal account for NetBackup Exchange operations for Exchange 2010 and later. This account is used for the Exchange credentials in the Exchange client host properties, enabling NetBackup to perform operations with Granular Recovery Technology (GRT). Note the following:

Configure each Exchange mailbox server and the CAS server. Configure each client that performs granular operations. To determine which clients to configure, see the following topic: In a cluster environment, perform the steps on each database node in the cluster. For an Exchange DAG, perform the steps on each database node in the DAG and the CAS server.
To create a minimal NetBackup account for Exchange 2010 and later operations
1 2 3 4 5
In Active Directory Users and Computers, select the Users folder. Right-click and select New > User and indicate a name for your new account. For example, NetBackupUser. Select the Member Of tab. Click Add and add Administrators to the user. Create a new Role Group, make the account a member of this group, and assign roles. Use the Exchange Management Shell to run the following commands: Note: If the account does not have the necessary privileges, an administrator needs to perform these tasks.
New-RoleGroup -Name NetBackupRoles -Roles @("Database Copies", "Databases", "Exchange Servers", "Monitoring", "Mail Recipient Creation", "Mail Recipients", "Recipient Policies" Add-RoleGroupMember -Identity NetBackupRoles -Member NetBackupUser
Where NetBackupUser is the name of the Active Directory account you created in 2.
38
Operational notes Deduplication notes
To perform restores with Granular Recovery Technology (GRT), also run the following commands with the Exchange Management shell: For Exchange 2010:
New-ManagementRole -Name SymantecEWSImpersonationRole -Parent ApplicationImpersonation New-ManagementRoleAssignment -Role SymantecEWSImpersonationRole -User NetBackupUser -Name "NetBackupUser-EWSImpersonation" New-ThrottlingPolicy -Name "SymantecEWSRestoreThrottlingPolicy" -EWSPercentTimeInCAS $null -EWSPercentTimeInAD $null -EWSMaxConcurrency $null -EWSPercentTimeInMailboxRPC $null -PowerShellMaxConcurrency $null Set-Mailbox -Identity NetBackupUser -ThrottlingPolicy "SymantecEWSRestoreThrottlingPolicy"
For Exchange 2013:

New-ManagementRole -Name SymantecEWSImpersonationRole -Parent ApplicationImpersonation New-ManagementRoleAssignment -Role SymantecEWSImpersonationRole -User NetBackupUser -Name "NetBackupUser-EWSImpersonation" Set-Mailbox -Identity NetBackupUser -ThrottlingPolicy "SymantecEWSRestoreThrottlingPolicy"
7 8
Provide the credentials for this account in the Exchange client host properties. Configure this account with the right to Replace a process level token.
Deduplication notes
This section contains the operational notes and known issues that are associated with NetBackup deduplication features (such as MSDP and PureDisk) in this release.
Before NetBackup 7.5.0.6, there was an issue with running multiple Accelerator backups to an MSDP or PureDisk storage unit. In this case, the jobs would appear to hang, the media server deduplication service would become unresponsive, and the Content Router daemon spoold (deduplication engine) would stop responding. This issue has been fixed in NetBackup 7.5.0.6 with the exception of a few rare cases. Should you encounter this issue, change the PREFETCH_SIZE and the RESTORE_DECRYPT_LOCAL settings in the pd.conf file to the following:
39
# Buffer size to use when prefetching data for restore operations (B) PREFETCH_SIZE = 16777216 # Agent side decryption and decompression on restore (0=off, 1=on) RESTORE_DECRYPT_LOCAL = 1
About upgrading MSDP and PureDisk deduplication solutions

Note: If all of your NetBackup media servers are running Windows, and you do not plan to add UNIX servers running MSDP, you may safely ignore the rest of this topic. This section applies to the following deduplication solutions:
NetBackup Media Server Deduplication Option (master server, media server, client, or VMware backup host) NetBackup Appliance deduplication (master server, media server, or VMware backup host) PureDisk deduplication PureDisk Appliance deduplication
In versions before NetBackup 7.5.0.6, a problem can occur where NetBackup cannot read an image that is stored on an MSDP or PureDisk storage unit. The issue results from the deduplication engine improperly storing client and policy names in the deduplication database on case-sensitive file systems. The types of operations that might exhibit failure due to a read error that is associated with this issue include verify, restore, duplication, and replication. For MSDP, the issue is fixed starting in NetBackup 7.5.0.6. Table 4-1 Examples of the failed operations that can result from the case sensitivity issue Activity Monitor status
(191) no images successfully processed
Operation
Activity Monitor job details

image open failed: error 2060018: file not found
Status in bpdm and bptm log files

sts_open_image failed: error 2060018
Verify
Restore
(83) media open error Image open failed: error 2060018: file not found
sts_open_image failed: error 2060018
40
Example scenario of the client name case sensitivity issue

Suppose that there is a NetBackup client named my_client running a version of NetBackup previous to Version 7.5.0.6 and that there is a corresponding policy named my_policy. Suppose also that my_client performs client-side deduplication to a UNIX-based MSDP or PureDisk storage unit. Next, suppose that the following steps occur: 1. 2. 3. A successful backup for my_policy is made to an MSDP or PureDisk storage unit. The name of the client in the policy my_policy is changed from my_client to MY_CLIENT. Another successful backup for my_policy is made to an MSDP or PureDisk storage unit.
The data for both backups is saved. However, the operations that attempt to read the data from the second backup fail if the deduplication engine is on a case-sensitive file system. The failures occur because the deduplication database entry my_client differs from MY_CLIENT.
Determining the servers and clients that can encounter the issue
The case sensitivity issue can occur if your environment performs any of the following MSDP functions on UNIX operating systems that run on NetBackup media servers or PureDisk servers (including NetBackup Appliances and PureDisk Appliances). 1. 2. 3. 4. 5. Media server deduplication to attached storage Media server deduplication to another media server Media server deduplication to a PureDisk server Client-side deduplication to a media server Client-side deduplication to a PureDisk server
Note: All of the listed operations apply to the VMware backup hosts that run the deduplication engine. All of the listed operations also apply to the master servers that function as media servers and run the deduplication engine. Symantec recomends that you upgrade all of the servers, clients, and VMware backup hosts in your environment that are involved in the listed operations. Starting with NetBackup 7.5.0.6, writing to the deduplication database has been
Operational notes OpsCenter notes
41
updated to fix the issue. The database writes are fixed so that a change in the case of the characters that are used for the NetBackup client name and policy do not cause a read of the backup images to fail. If you do not upgrade to these versions, there is a possibility that you may encounter read errors with future backup images due to this issue. Note: Consistent with NetBackup upgrade policy your media servers and clients must be running a minimum of NetBackup 7.5 before you can attempt to upgrade to 7.5.0.6.
Fixing the name case issues that exist in the MSDP and PureDisk databases
If you have already encountered image read failures due to client name or policy name case sensitivity issues, your first step should be to upgrade the affected hosts to NetBackup 7.5.0.6 or newer. After the upgrade, the name case issue still affects the images that were created before the upgrade by versions of NetBackup previous to Version 7.5.0.6. Use the following table to select the correct approach to repair client and policy name case sensitivity issues with existing NetBackup images. Table 4-2 Problematic name type
Client Client
Storage unit type

MSDP PureDisk
Required action
Repair the MSDP database Contact Symantec Technical Support Contact Symantec Technical Support Contact Symantec Technical Support
Policy
MSDP
Policy
PureDisk
A special procedure to repair an MSDP or PureDisk is available on the Symantec Support website at the following URL: http://www.symantec.com/docs/TECH207194
OpsCenter notes
This section contains the operational notes and known issues that are associated with OpsCenter in this release of NetBackup.
42
Uninstalling OpsCenter 7.5.0.6 may take a long time on the HP-UX. In certain scenarios, OpsCenter 7.5.0.6 on HP-UX may take several minutes to uninstall. Do not interrupt the uninstallation process. The Monitor > Alerts List View does not show alerts in certain scenarios. Under the Monitor > Alerts List View, if you sort the alerts by Alert Policy or Severity, the existing alerts are not displayed on the page. To work around the issue, remove the Alert Policy or Severity columns from sorting. You can then view the existing alerts appropriately under the Monitor > Alerts List View. To remove a column from sorting, do the following: 1 2
Go to the Monitor > Alerts List View and click Change Table Settings. On the Table Settings pop-up screen, clear the sorting that you may have applied to the Alert Policy and Severity columns. Select the corresponding check box.
Modify the selection for the Sort drop-down list. The Up or Down options should not be selected for these columns.
Click Ok.
The Monitor > Jobs Hierarchical View does not show correct child jobs if a master server view is selected. The following is an example scenario of the issue: 1 2 3 4
Go to Monitor > Jobs. Select the Customize time frame. Select Relative Time Frame as previous 5 days. Select a master server view from the View drop-down list. All jobs for the selected master server are displayed. Select Hierarchical View. This view shows incorrect child jobs. Parent jobs show the child jobs that are associated with other master servers.
The Monitor > Overview page does not display a NetBackup master server appropriately if it is a virtual machine. The following is an example scenario of the issue:
43
1 2 3 4
Install a NetBackup master server that is a virtual machine and that contains virtual machine data. Install OpsCenter Server. In the OpsCenter interface, add the same master server with its host name as a display name. Go to the Monitor > Overview page. It displays the display name of the virtual machine on which the master server is installed instead of the master server display name.
In certain scenarios, duplicate entries of a client are displayed on the Monitor and Views interfaces. This issue is seen in any of the following scenarios:

A NetBackup master server is used as a client in one or more policies. Some NetBackup policies refer to a NetBackup master server with a fully qualified domain name (FQDN) while others refer to it with a short name.
The actual name of the master server does not match its network name or display name that is used in OpsCenter. The following is an example scenario of the issue: The actual name of the NetBackup master server is abc.xyz.com. The network name or display name that is used in OpsCenter is xyz.
In this scenario, if abc.xyz.com is used as a client in one or more NetBackup policies, duplicate entries of this client are displayed on the following OpsCenter screens:

Monitor > Host > Client Settings > Views > Manage Nodes and Objects > Objects not in selected view
An issue can occur when you restore files and folders using OpsCenter. The backup timeline view may not show all of the images containing the selected file or folder if a snapshot backup was performed. NetBackup 7.5.x.x can only be installed on a system that is running NetBackup 7.5. However, if you upgrade to NetBackup 7.5 from a previous version, such as 7.1, the upgrade might fail with the following error message:
No primary key value for foreign key 'FK_JOB_REF_MEDIA_SERVER_ARCHIVE' in table 'domain_JobArchive
If you encounter this error, please contact Symantec Technical Support before you try to re-attempt the upgrade process.
44
Custom tabular reports may not display all jobs if the Media Barcode field is selected. If you encounter this issue, please contact Symantec Technical Support for assistance. To run a Capacity Licensing report in OpsCenter 7.5.0.5 and later, a user name and password is required for each master server. To successfully run a report for any master servers that were added to OpsCenter in versions previous to 7.5.0.5, an extra step is required. The user name and password credentials for each master server must be entered manually in the NetBackup configuration settings. If the credentials are not added in the configuration settings, a user name and password error is returned when the report is run.
Additionally, for Capacity Licensing to work correctly, please refer to the following technote and install the specified EEBs: http://www.symantec.com/docs/TECH148678
Policy view is not applicable for Restore type jobs. If you select the policy view when you create any job-related alert policy, OpsCenter does not generate alerts for restore jobs. Since restore jobs do not have a policy associated with them, they never raise alerts for policy view. If an OpenStorage alert policy is configured, then OpsCenter generates an alert (email) for each volume. To work around this issue, you can filter the volume type alert by specifying the text (for example: With volume name, not protected for any volume, and as required) in the field that is provided for the Event message contains word(s) selection. OpsCenter generates the alert only when the NTAP event contains the text that is specified in Event message contains word(s) selection. When an OpsCenter user is deleted, the following user-specific data is also deleted along with views, report schedules, and so on:

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. The OpsCenter Admin deletes User B. As a result of this user deletion, D1 is also deleted because User B had modified it. Therefore, data collection fails and User A cannot collect any data from M1.
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
Operational notes NetBackup Search notes
45
upgrade OpsCenter 7.5 to 7.5.0.4 and install all language packs on top of 7.5.0.4, an upgrade to 7.5.0.5 may fail. To work around the issue, manually uninstall all language packs before the upgrade, and then reinstall them after the upgrade.
In the Simplified File Restore (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 job collection from master servers could fail if port 1556 is not opened bi-directionally on both the NetBackup and OpsCenter sides.
NetBackup Search notes

This section contains the operational notes and known issues that are associated with Search in this release of NetBackup.
About upgrading Search to NetBackup 7.5.0.x

NetBackup Search users must follow a special procedure to upgrade from NetBackup 7.5 to any NetBackup 7.5.0.x maintenance release (for example, Version 7.5.0.6). This procedure also applies to upgrading between NetBackup 7.5 maintenance releases (for example, upgrades between Version 7.5.0.3 and Version 7.5.0.6). Symantec recommends that all NetBackup Search users review this procedure before they upgrade to a new release. The NetBackup Search upgrade procedure can be found on the Symantec Support website at the following link: http://www.symantec.com/docs/TECH207010
Virtualization notes
This section contains the operational notes and known issues that are associated with virtualization in this release of NetBackup.
The VMware policy Advanced Attributes dialog has a setting that is called Virtual disk selection that has options for excluding the boot disk or data disks from the backup. To use either of the exclude disk options before version 7.5.0.6, NetBackup required that the full swap file reside on the boot disk. The swap file is the Windows pagefile.sys file or the Linux swap partition. This restriction has been lifted in 7.5.0.6. For either of the exclude disk options, the swap file no longer needs to reside on the boot disk.
46
Operational notes Virtualization notes
Hyper-V notes
NetBackup for Hyper-V does not support the ampersand character (&) in the name of the virtual disk file (.vhd). If the name of the virtual machines vhd file contains &, the backup fails with status code 6. To work around this issue, remove the & from the .vhd file name and rerun the backup. Starting with NetBackup 7.5.0.6, you can restore a virtual machine to Hyper-V 2012 even if the virtual machine resided on a Hyper-V 2008 R2 server when it was backed up. However, to connect to the restored virtual machine, you may have to modify the virtual machines network adapter by selecting the correct virtual switch. This issue results from changes to the virtual machine XML configuration in Hyper-V 2012. Note: Restoring the virtual machine to Hyper-V 2008 R2 does not have this issue. An issue exists where you cannot add a Red Hat Enterprise Linux 6.4 VM as a client to a Hyper-V policy by its host name. To solve this issue, you need to install all the necessary OS updates that are detailed in Red Hat Bug 883306 (https://bugzilla.redhat.com/show_bug.cgi?id=883306). You can also work around this issue by adding the VM as a client to the policy using either the VM display name or UUID. The following is a list of limitations on NetBackup support for Windows 2012 Hyper-V:

Backup and restore of the Resilient File System (ReFS) is not supported. Block-level incremental backup is not supported. File-level recovery from a Hyper-V backup is not supported when:

The file originates from a Resilient File System (ReFS) volume, or The virtual machine is composed of VHDX file(s).
File-level recovery continues to be supported when the file originates from an NTFS volume and the virtual machine is composed of VHD files(s).
Backup of virtual machines within Cluster Shared Volumes (CSV) is supported. In Hyper-V Server 2008 R2, CSV has a limitation that requires serialized backups. In Hyper-V Server 2012, CSV supports concurrent backups without that limitation. Consequently, the CSV timeout setting in
47
the NetBackup Hyper-V policy is only used in Hyper-V Server 2008 R2 deployments.
The Enable file recovery from VM backup policy option is not supported for the virtual machines that are .vhdx files. If the virtual disk is in the .vhdx format, you can restore the entire virtual machine, but not individual files. If you attempt to restore individual files, the restore fails. For NetBackup 7.5.0.6 master servers, the Activity Monitor's Job Details dialog contains the following message:
This VM contains VHDX virtual disk(s). Single file restore will not be possible for such disks. You will be able to perform a full restore.
For NetBackup 7.5.0.6 and earlier master servers, the Job Details message is similar to the following:
Warning bpbrm(pid=9128) from client <hostname>: WRN - VxUL id = 34.
On Windows Server 2012, cluster nodes can back up the same cluster shared volume simultaneously. As a result, NetBackup does not use the Cluster shared volumes timeout option on the policy's Hyper-V tab if the cluster is on Windows Server 2012.
48
Chapter
End-of-life notifications
About future NetBackup end-of-life notifications
About future NetBackup end-of-life notifications

Symantec is committed to providing the best possible data protection experience for the widest variety of platforms, operating systems, databases, applications, and hardware. Symantec continuously reviews NetBackup's support of these items. This review ensures that the proper balance is made between maintaining support for existing versions of products, while also introducing new support for the following:

General Availability releases Latest versions of new software and hardware New NetBackup features and functionality
While Symantec continually adds support for new features, platforms, and applications, it may be necessary to improve, replace, or remove certain support in NetBackup. These support actions may affect older and lesser-used features and functionality. The affected features and functionality may include support for software, OS, databases, applications, hardware, and 3rd-party product integration. Other affected items may include the products that are no longer supported or nearing their end-of-support life with their manufacturer. Symantec provides advanced notification to better help its customers to plan for upcoming changes to the support status of the various features in NetBackup. Symantec intends to list older product functionality, features, hardware, OS, and the 3rd-party software products that are no longer supported in the next release of NetBackup. Symantec makes these support listings available as soon as possible with a minimum of six months where feasible before major releases.
50
End-of-life notifications About future NetBackup end-of-life notifications
Much of this support information is available through the NetBackup Symantec Operations Readiness Tools (SORT) home page widget NetBackup Future Platform and Feature Plans. Also, included in the widget are the list of platforms, databases, and applications that are not supported in a given release. You can access SORT at the following webpage: https://sort.symantec.com/netbackup Another SORT resource 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 https://sort.symantec.com/netbackup and navigate to Support > Related Links. Click on the link to End of Assisted Support information. Alternatively, you can follow the direct link to https://sort.symantec.com/eosl. Other information about what is compatible with NetBackup can be found in the various compatibility lists that are listed in the NetBackup Master Compatibility List. http://www.symantec.com/docs/TECH59978
Appendix
About the NetBackup 7.5.0.6 release content

This appendix includes the following topics:

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

This release incorporates fixes to several known issues that existed with NetBackup. Many of these issues pertain to the customer-specific issues that have been documented in the form of Titan or Salesforce.com cases. Many of the fixes that are incorporated into this release are available as individual engineering binaries and engineering bundles (EEBs). These EEBs were created to address specific customer issues with a previous version of NetBackup. The following sections contain listings of Etracks and EEBs that document known issues that have been fixed in this release of NetBackup.
About release content conventions

The following list describes the conventions used in the subsections that follow this section. Each item listed in the release content subsection describes a feature, enhancement, or fixed issue contained in this release:
Etrack Incident
52
About the NetBackup 7.5.0.6 release content NetBackup 7.5.0.6 release content
Notes the Etrack number that targets this release.
Associated Primary Etrack An additional Etrack number that exists in the incident hierarchy. Associated Service Request Etrack The Etrack that is associated with the customer support service request. Description Describes a particular issue that has been fixed in this release, as well as additional notes or workarounds. Workarounds can be used instead of applying the patch, however, Symantec recommends the "best practice" of being at the latest available patch level. **Description or **Etrack number Describes a critical issue or an issue that can lead to a potential data loss that has been fixed in this release. Please read these issue descriptions carefully. In some cases, a Tech Alert link is provided.
About current release content Etracks

For more information on the Etracks that are listed in this section, or any other service request Etrack, Symantec recommends that you use Symantec Operations Readiness Tools (SORT). To access SORT, go to the following webpage: http://sort.symantec.com/netbackup
NetBackup 7.5.0.6 release content

This section contains a list of known issues that were fixed and that are now included in this release of NetBackup. Etrack Incident: 2985639

Associated Primary Etrack: N/A Associated Service Request Etrack(s): N/A Description: An option has been added to allow the user to set the ulimit for file handles on the backup and archive program bpbkar.
Etrack Incident: 3019711

Associated Primary Etrack: N/A Associated Service Request Etrack(s): N/A Description:
53
When bplist was run with no time field specified in the end timestamp, it scanned an uninitialized area of memory, resulting in incorrect time values. Etrack Incident: 3048490

Associated Primary Etrack: N/A Associated Service Request Etrack(s): N/A Description: If the NetBackup client service or the SQL server's sysadmin security server roles didn't have enough permissions, Microsoft SQL backup jobs failed but still completed with a status code 0 instead of returning with an error code.

Associated Primary Etrack: 3082078 Associated Service Request Etrack(s): 3080554 Description: If an upgrade was interrupted while the Storage Lifecycle Policy (SLP) definitions were being updated, subsequent retries of the upgrade failed.

Associated Primary Etrack: 3065608 Associated Service Request Etrack(s): 3065565 Description: If the path name for the storage, the policy, or the client exceeded 259 characters, backup jobs failed.

Associated Primary Etrack: 3086360 Associated Service Request Etrack(s): 3085841 Description: The Encryption column on the NetBackup Administration console did not correctly display encrypted backups as yes when a report was run for either "images on media" or "images on disk."

Associated Primary Etrack: 2776572 Associated Service Request Etrack(s): 2776304 Description:
54
In certain scenarios, the default value of RBALLOC_KBYTES_THRESHOLD caused issues with the NetBackup Job Manager. The default value has been changed to alleviate this problem. Etrack Incident: 3108442

Associated Primary Etrack: 3094585 Associated Service Request Etrack(s): 3094572 Description: Attempts to delete a master server from OpsCenter failed.

Associated Primary Etrack: 3094188 Associated Service Request Etrack(s): 3094108 Description: The output of bpdbjobs was modified to accommodate different time and date formats.

Associated Primary Etrack: 3121527 Associated Service Request Etrack(s): 3121317 Description: If RESILIENT_NETWORK was enabled, the user was unable to use the update_clients command to push NetBackup software to a UNIX or Linux client.

Associated Primary Etrack: 3087451 Associated Service Request Etrack(s): 3086979 Description: A restore of a SharePoint 2010 library with multiple folders that had unique permissions resulted in incorrect permission settings.

Associated Primary Etrack: 3084768 Associated Service Request Etrack(s): 3084743 Description: On hosts with EMC Virtual Storage Integrator installed, some snapshot jobs failed or took longer than expected due to a fault with bpfis.
About the NetBackup 7.5.0.6 release content NetBackup 7.5.0.6 Emergency Engineering Binary (EEB) listing
55
Etrack Incident: 3133353 and 3133354

Associated Primary Etrack: N/A Associated Service Request Etrack(s): N/A Description: In large VMware environments, the NetBackup-Java Administration Console did not always display the VMware entities in the restore wizard.

Associated Primary Etrack: 3129526 Associated Service Request Etrack(s): 3129524 Description: An upgrade failed due an error with the eventEnableDisable process.

Associated Primary Etrack: N/A Associated Service Request Etrack(s): N/A Description: The bpimport -drfile command failed with a status code 232 if the NetBackup Database Manager found a referenced deleted image.

Associated Primary Etrack: 3137320 Associated Service Request Etrack(s): 3137180 Description: In a certain configuration, Bare Metal Restore (BMR) recovery failed with a Network Initialization error, due to an incompatible older version of a network driver.
NetBackup 7.5.0.6 Emergency Engineering Binary (EEB) listing

The following table contains the known issues that were identified, fixed, and available to customers in the form of an EEB. NetBackup 7.5.0.6 resolves the addressed issues in each of these EEBs. Additional EEBs may have been released since this document was posted. For more information on the Etracks that are listed in this section, or any other service request Etrack, Symantec recommends that you use Symantec Operations Readiness Tools (SORT). To access SORT, go to the following Web page:
56
https://sort.symantec.com/netbackup Alternatively, if you do not see an EEB that you expected to see in this document, or you require additional information about an issue in this table, contact Symantec Support. Table A-1 Etrack Number
3114410
NetBackup 7.5.0.6 EEB Listing
EEB Description
The NetBackup Vault recovery report does not include the catalog disaster recovery steps and gives an error of premature end-of-file in the vault summary.log file. Hyper-V backups would fail with a status 156 and a status 1542. Hyper-V backups would fail with a status 156 and a status 1542. The bpfis process hangs during a Hyper-V backup due to a stale snapshot. Under certain conditions, FlashBackup problems occur following 7.5.0.5 patch installation on Windows, due to VxMS binaries being moved during installation. Under certain conditions, FlashBackup problems occur following 7.5.0.5 patch installation on Windows, due to VxMS binaries being moved during installation. The pbx_exchange service aborts with a core dump if a pbx-dependent service with a heavy load from incoming client connections is terminated. The registry entries are ignored. The registry entries are ignored. NetBackup Agent for VMS issue. After an upgrade of an Open Virtual Memory System (VMS) client from version 6.5.5 to version 7.5, modifying and saving the client properties results in the error 'file read failed (23)'. VERITAS Backup Reporter issue. VERITAS Backup Reporter issue. This is a cumulative EEB bundle for TSM data collection issues in NetBackup 7.0.1. VERITAS Backup Reporter issue. VERITAS Backup Reporter issue. Improves the reporting accuracy in Capacity and Traditional reports. Improves the reporting accuracy in Capacity and Traditional reports.
2864973 2878491 3002231 3161604
3195197
3111591
3139464 3130147 3114741 3133752
2434059 2221000 2219170 1730575 2271300 2982810 2982814
57
Table A-1 Etrack Number

2982816 2982811 2982813
NetBackup 7.5.0.6 EEB Listing (continued)
EEB Description
Improves the reporting accuracy in Capacity and Traditional reports. Improves the reporting accuracy in Capacity and Traditional reports. Improves the reporting accuracy in NetBackup Deployment Utility (nbdeployutil) Capacity and Traditional reports. Improves the reporting accuracy in Capacity and Traditional reports. Improves the reporting accuracy in Capacity and Traditional reports. Improves the reporting accuracy in Capacity and Traditional reports. Improves the reporting accuracy in Capacity and Traditional reports. Improves the reporting accuracy in NetBackup Deployment Utility (nbdeployutil) Capacity and Traditional reports. Improves the reporting accuracy in Capacity and Traditional reports. Improves the reporting accuracy in Capacity and Traditional reports. Improves the reporting accuracy in Capacity and Traditional reports. Improves the reporting accuracy in NetBackup Deployment Utility (nbdeployutil) Capacity and Traditional reports. Improves the reporting accuracy in Capacity and Traditional reports. Solaris SAS-2 host bus adapters (HBAs) do not work with NetBackup. Solaris iSCSI host bus adapters (HBAs) do not work with NetBackup. SCSI pass-through driver scripts for SAS-2 drive on Solaris. Solaris SAS-2 host bus adapters (HBAs) do not work with NetBackup. A custom retention level that is less than seven days does not get honored by the Auto Image Restore target master. EEB bundle addressing storage lifecycle policy and Auto Image Replication performance, as well as a problem with frozen media that is deassigned in error. Starting with NetBackup 7.5.0.4, media which has expired can get deassigned even when it is frozen. In NetBackup 7.1, frozen media never gets deassigned. Frozen media should not get deassigned. Attempts to restore some individual files from a Hyper-V backup fail.
2982818 3024983 2982812 2982817 3123414
2982809 3027562 2982815 2982803
2982819 2980240 2792286 3128448 2871476 3051344
3093205
3009921
3193376
58

2916230 3117236
EEB Description
Attempts to restore some individual files from a Hyper-V backup fail. The 'nbdevquery -listdv' command did not show potential free space available for a given disk volume. Corrects and changes the NetBackup Storage Lifecycle Manager (nbstserv) recovery session processing. Corrects and changes Storage Lifecycle Manager service (nbstserv) recovery session processing. A one-time script was created to address thousands of storage lifecycle policy (SLP) images that are stuck in state 10 - inactive. The script will not be included in any other release vehicle. NetBackup Java User Interface issue. NetBackup Java User Interface issue. Lotus restore takes a very long time on NetBackup 7.5.x. Lotus restore takes a very long time on NetBackup 7.5.x. Unable to recover Linux clients with a bnx2x adapter (Broadcom NetXtreme II 5771x/578xx 10/20-Gigabit). NetBackup OpsCenter issue. Vmware and Hyper-V policy types are missing from the 'Capacity by Policy Type' section on the Summary tab. A Microsoft SharePoint node is not visible during enumeration. SharePoint resources are not visible in the Backup, Archive, and Restore interface during a backup. Browsing images in the Backup, Archive, and Restore interface is slow. The interface takes lot of time to load images. Using the NetBackup Administration Console to browsing for the backup images that are written to certain media servers takes too long. NetBackup Java User Interface issue. On startup, the SQL Agent interface is unable to retrieve SQL server properties from the registry to create an Open Database Connectivity (ODBC) connect string.
3157844
3160753
3153058
3077904 3158926 3031070 3034651 2966680
3142588 3068763
3055370 3178727
2970130
3019161
3019163 2918691
59

2924638
EEB Description
On startup, the SQL agent interface is unable to retrieve the SQL server properties from the registry in order to create an Open Database Connectivity (ODBC) connect string. Dbbackup.exe is unable to retrieve SQL server properties from the registry in order to create an Open Database Connectivity (ODBC) connect string. After it reads the cloudstore.conf file, the NetBackup Cloud Storage Service Container service (nbcssc) creates a log file under the root directory. After it reads the cloudstore.conf file, the NetBackup Cloud Storage Service Container service (nbcssc) creates a log file under the root directory. On a RedHat 6.X client, Bare Metal Restore enters the discovery phase with the following error: "The disks in this system do not meet the minimum requirements for recovery." NetBackup Service Layer issue. NetBackup Java User Interface issue. Phase 2 of the import using the 'fix_encrypt' option fails in tar with status code 13. NetBackup OpsCenter Alerts issue. NetBackup OpsCenter Alerts issue. NetBackup OpsCenter Data Collection issue. NetBackup OpsCenter Data Collection issue. NetBackup Java User Interface issue. When the previous snapshot is not cleaned up from the catalog, subsequent snapshot creation fails with the following error: 'pfi_find_active: Cannot find available snapshot mirror.' Multiplexed backups of VMware clients import as 'VM_Type 0' instead of 'VM_Type 2'. NetBackup Windows User Interface issue. The bpvmutil process crashes during a VMware backup. The bpvmutil process crashes. NetBackup Systems Management (Policies, Scheduling, and so forth.) issue. NetBackup Systems Management (Policies, Scheduling, and so forth.) issue. NetBackup Systems Management (Policies, Scheduling, and so forth.) issue.
3090552
3042624
3147934
3105316
3155722 3180682 2946053 3056622 3080574 3014874 2977914 3189770 3127522
2961697 3034022 2916262 3163522 3155662 2966787 3051191
60

3058454 3078609 3155883
EEB Description
NetBackup Systems Management (Policies, Scheduling, and so forth.) issue. NetBackup Systems Management (Policies, Scheduling, and so forth.) issue. A restore fails with the error 'Failed to create ZFS file systems' when the same hot spare disk is assigned to two different ZFS pools. Cannot restore from a Network Data Management Protocol backup image of more than one path - it is a duplicate copy that was written by EMC DL4200 embedded media server. The expiration time of multiplexed (MPX) media may be incorrectly changed to an earlier date. http://www.symantec.com/docs/TECH205819
3005312
**3208619
**3191336
The expiration time of multiplexed (MPX) media may be incorrectly changed to an earlier date. http://www.symantec.com/docs/TECH205819
**3185297
**3185299
**3142128
3106719
The Activity Monitor reports inconsistent results of backups and restores. It shows less than 100% completed, but the Detailed Status tab shows processes closed with a status code 0. The Job State remains Active. Incremental backups are not marked eligible for true image restore (TIR) pruning. Virtual Machine Disk (vmdk) bitmap files are not removed from /tmp following a VMware backup cancellation. A cancellation or failure of a VMware backup job leaves temporary VMDK files in /tmp. With NBAC enabled, some jobs fail intermittently and the JobID does not appear in the Activity Monitor. The NetBackup Policy Execution Manager (nbpem) logs indicate that the JobID may be lost due to communication problem with NetBackup Job Manager (nbjm).
3108642 2982308
3106690 2966284
61

3101514
EEB Description
A restore or duplication of a Network Data Management Protocol (NDMP) image fails with an error reading: 'create_ndmp_frag_info: The size of this backup image (n) xxx has been modified' or 'create_ndmp_frag_info: Internal error - count mismatch Error.' During Distributed File System Replication (DFSR) backups, bpbkar32.exe can cause an application fault issue. During VMware backups, snapshots occasionally fail with a status code 3014 after 10 attempts. During VMware backups, snapshots occasionally fail with a status code 3014 after 10 attempts. If snapshot creation fails, bpfis does not call VixDiskLib_EndAccess() to unlock the virtual machine. NetBackup Bare Metal Restore issue. Closes the transaction for each finished session and changes the snapshot isolation level. The 'bpnbaz -q -showbackuplist' command fails when you perform a hot catalog backup. NetBackup Communication Protocol issue. NetBackup OpsCenter Custom Reports issue. Image cleanup is not able to clean up the backup images that reside on the node of 'APP_CLUSTER'. Sybase hangs because of internal table growth. NetBackup Bare Metal Restore issue. A Network Data Management Protocol (NDMP) restore fails with status code 27 and a NetBackup tape manager core dump issue after the end of tape is detected. A Network Data Management Protocol (NDMP) restore of a backup that was taken with NetBackup 6.5.4 and earlier fails with status code 27 and a NetBackup Tape Manager (bptm) core dump issue. In some cases during a Network Data Management Protocol (NDMP) restore, a NetBackup Tape Manager (bptm) core dump issue occurs after end of tape is detected. A Network Data Management Protocol (NDMP) restore fails with a status code 27, and the NetBackup Tape Manager core dumps after end of tape is detected.
2985395
3133654
3079971
3192221
3065140 3084976 3119197 3135460 3001723 2961274
3123528 3019944 2690308
3024221
2886224
3209796
62

3042170
EEB Description
A VMware backup with a display name ending in a dot (.) causes all '.f' files to be deleted and results in the inability to restore from the backup. VMware Application State Capture image expires before the parent image expires. Credentials containing '\Xyy' get converted to special characters (hex equivalent) in bpVMutil and therefore they fail authentication. The bpverify command reports failure on UNIX media servers when the backed up file names include carriage returns. The bpverify command reports failure on UNIX media servers when the backed-up file names include carriage returns. Block-level backup (BLIB) incremental jobs back up as a full backup if the virtual machine has spaces in the name. The GRT phase of an Exchange backup fails if a database name contains a colon (:) character. NetBackup OpsCenter Alerts issue. NetBackup OpsCenter Alerts issue. NetBackup OpsCenter issue. Orphaned .po files in the catalog generate false 'fakeFPCheck' messages. A VMware Exchange GRT browse fails when volumes are required on a system with more than 10 volumes on the system. When trying to do a Bare Metal Restore (BMR) dissimilar disk restore of a Solaris client, the mapping utility is unable to map the system disk. Linux clients with non-system VxVM disks fail to be recovered using system-only restores. Linux clients with non-system VxVM disks fail to be recovered using system-only restores. NetBackup OpsCenter Alerts issue. A tmp file for Sybase grows too large. A one-time script was created to delete a media server and all related data records from the NetBackup database. The script will not be included in any other release vehicle. NetBackup OpsCenter Custom Reports issue. NetBackup Systems Management (Policies, Scheduling, and so forth.) issue.
3098858 2925091
3020859
2946684
3026290
3144618 2898214 3093057 2952408 2795138 3108240
3017201
3143716 3076793 3074804 2797723 3195573
3051747 3184319
63

3142835
EEB Description
Allows Common Object Request Broker Architecture (CORBA) communications across a static Network Address Translation (NAT) firewall without requiring a FIREWALL_IN configuration entry. Allows Common Object Request Broker Architecture (CORBA) communications across a static Network Address Translation (NAT) firewall without requiring a FIREWALL_IN configuration entry. Restores of images written with the NetBackup Key Management System (NBKMS) enabled may fail with a status code 85. NetBackup Bare Metal Restore issue. The bpmount utility reports duplicate mount point entries on a UNIX server if one or more mount points are excluded through an entry in the exclude_list file. GRT restore of a message that has empty attachments may fail if the Microsoft Exchange attachment table does not have the standard name. For example, this issue could occur if there has been a database schema change for a local configuration. Granular Recovery Technology (GRT) restores do not correctly restore Enterprise Vault (EV) archived stubs of messages that had attachments. When cluster node names starts with CLUSTER in all upper case, the user is unable to browse for Hyper-V virtual machines. The tapes are not imported into the robot and inventoried automatically when the AUTO_UPDATE_ROBOT touch file is set. An issue with AUTO_UPDATE_ROBOT where the robot mailslot changes would not be recognized. The NetBackup robot daemons may miss unit attentions, which causes AUTO_UPDATE_ROBOT to fail. Due to the fixed length of the 'Select Configuration for Restore' dropdown of a generic restore, the user is unable to see some lengthy client names and cannot select the desired configuration to proceed with the restore. The current NetBackup command line interface is limited in its ability to modify a VIP policy. Two new options have been added to the command line interface. The current command line interface (CLI) is limited in its ability to modify VIP policy. Two new options have been added to the CLI. NetBackup Java User Interface issue.
3142846
3093882
3027395 3045792
3073850
3195135
3132521
2909871
2957733
3138156
3055194
3039453
3125103
3191915
64

3231114 3047514
EEB Description
NetBackup Java User Interface issue. Issues reading images from the PureDisk Deduplication Option (PDDO) disk pool where the characters in a client or a policy name has had a change in case. This issue can affect backups, restores, and duplications. Issues reading images from the PureDisk Deduplication Option (PDDO) disk pool where the characters in a client or a policy name has had a change in case. This issue can affect backups, restores, and duplications. A one-time script was created to remove a Media Server Deduplication Pool (MSDP) storage server from a failed configuration attempt. The script will not be included in any other release vehicle. A one-time script was created to delete a Network Data Management Protocol (NDMP) server which cannot be deleted by using the nbemmcmd -deletehost command. The script will not be included in any other release vehicle. A one-time script was created to remove an MSDP setup on the master server that cannot be deleted by using nbemmcmd -deletehost and instead fails with error (Please Delete Disk Objects First). The script will not be included in any other release vehicle. A one-time script was created for Auto Image Replication images exiting with status 83 because the image cleanup could not find the volume. The script will not be included in any other release vehicle. NetBackup Bare Metal Restore issue. NetBackup Systems Management (Policies, Scheduling, and so forth.) issue. NetBackup Systems Management (Policies, Scheduling, and so forth.) issue. On Linux, if an extended partition is present, then after an 'unmap all and map' operation, the partition gets set to W95 Ext'd (LBA). A Client Direct backup fails when the media server is set to 'USE_VXSS = AUTOMATIC' and 'VXSS_NETWORK = media_server_name REQUIRED' when the client is set to 'USE_VXSS = PROHIBITED'. NetBackup Communication Protocol issue. During multistreamed or Volume Snapshot Service (VSS) backup jobs, a Bpfis.exe core dump is seen on Amazon virtualized Windows hosts running on Red Hat Enterprise Linux (RHEL) machines. Unable to recover from copy 2 of a catalog backup that was taken on tape created by a storage lifecycle policy.
3026132
3214313
3055227
3104818
3008786
3095239 3156374 2996317 2842657
3082881
3126195 3118240
3044188
65

3147730 **3204762
EEB Description
The bpvmutil.exe application faults intermittently. NetBackup Systems Management (Policies, Scheduling, and so forth.) issue. http://www.symantec.com/docs/TECH206911
3050260
A defunct bpfis process is created when the parent bpfis process does not read the status of the exited child process. NetBackup Java User Interface issue. NetBackup Java User Interface issue. Error messages 'JFS log was not found in volume group (vgName)' and 'A JFS log must exist in volume group (vgName) before a JFS logical volume can be created' seen when PTR or DDR are performed on AIX client's configuration with VG not having JFSlog LV. Importing images containing sparse files can result in incorrect size information. Importing images containing sparse files can result in incorrect size information. Importing images containing sparse files can result in incorrect size information. NetBackup Java User Interface issue. Restores of the databases that have curly braces can fail. Unable to switch from one NetBackup domain to the other using the Windows NetBackup Administration Console, NetBackup Access Control, and VxSS. SharePoint cross-farm redirected restore fails. An Exchange restore fails with status code 37 if a fully qualified domain name is used. The problem can be seen in the bpbkar and the bpfis process logs during the backup time where the fully qualified domain name gets appended twice. NetBackup Java User Interface issue. VMware backups fail with a status code 41. The logs show that the process hangs on the function IsSystemBootedUsingEFIFirmware. The NetBackup Enterprise Media Manager database encounters issues on a ZFS file system. A combination of performance problems on the master server result in a failure to return the media server name during resource request processing. This error is a retryable error, but a defect causes it to not be retried. NetBackup Windows User Interface issue.
2867684 3156125 3079370
3106076 3106104 3073489 3154497 3028881 3028468
2970741 2754057
3150274 3131418
3011949 3150238
2936080
66

2980571 2991262 2755281 3058395 3071572
EEB Description
NetBackup Bare Metal Restore issue. NetBackup OpsCenter Data Collection issue. NetBackup OpsCenter Data Collection issue. NetBackup Windows User Interface issue. A self-restore fails on a Sun Fire X4270 M2 server with 'ERROR Incorrect Label information for $diskLocation is written in PREP_DISKDATA File'. During a Granular Recovery Technology (GRT) browse, the modified timestamp of mail items in the Backup, Archive, and Restore interface show 5 hours off. SAP backups of the databases are taken from an ext4 file system fail to restore with the error 'Read access to .LoNg_VaLuEs.2 was denied'. The Exclude Data Disks option in a VMware policy does not work correctly for some virtual machines. The Exclude Data Disks option in a VMware policy does not work consistently for Windows 2008 virtual machines. The Exclude Data Disks option in a VMware policy does not work consistently for Windows 2008 virtual machines. VMware Backups of Linux servers using EXT4 may fail with a status code 12: db_FLISTsend failed: file open failed (12). VMware backups for various Red Hat Enterprise Linux servers fail with error 'db_FLISTsend failed'. VMware backups for various Red Hat Virtual Machine servers fail with the error 'db_FLISTsend failed.' VMware backups for various Red Hat Virtual Machine servers fail with the error: db_FLISTsend failed. The bpresolver process takes a long time to respond when backing up an Exchange 2010 Database Availability Group. During backup, the backup tape manager (bptm) times out with the following underlying error in the deuplication manager (spad): [_handle_find] catalog is busy. This error is caused by a large number of backups in a client/policy combination.
2996859
3058293
3095961
3108661
3114977
3216828
2931422
3093976
3002480
2951780
3016768
67

3105408
EEB Description
During a backup, the NetBackup Tape Manager (bptm) gets timed out with the underlying error in spad '[_handle_find] catalog is busy' caused by a large number of backups in a client and policy combination. During a backup, the NetBackup Tape Manager (bptm) gets timed out with the underlying error in spad '[_handle_find] catalog is busy' caused by a large number of backups in a client and policy combination. Estimating the size of backups during image validation takes a long time. A mapped full virtual machine backup completes with a status code 0, but the VxMS log shows: buildLdmPartitions:pLdm.cp:235 - File Recovery is not possible after backup. NetBackup Service Layer issue. The NetBackup Service Layer (nbsl) process unexpectedly stops and exits because of a memory leak issue on the HP-UX IA64 platform. On a NetBackup Appliance with Software version 2.5.1, VMWare backups sometimes fail with an error code 62 or 130. Updates OpenSSL to version 0.9.8.y. A Network Data Management Protocol (NDMP) tapes import ends with error 220. Duplicate image cleanup events can cause duplicate backup image entries in the indexing queue, resulting in problems in processing further indexing requests. Disk Staging Storage Unit (DSSU) staging fails with status code 228 due to the NetBackup Enterprise Media Manager (nbemm) returning too many entries. NetBackup Bare Metal Restore issue. Containers (.bin files) that are 4 GB or larger can affect performance and not allow the containers to shrink. In addition, data can become lost or corrupted when container hits the 4GB boundary. NetBackup Windows User Interface issue. NetBackup Windows User Interface issue. During a backup of a client that has a symbolic link in the database and images directory, the NetBackup Database Manager (bpdbm) fails to get the image key. That causes the backup to fail with status code 227. Attempts to create a client alias fail when the alias name is already assigned to a real client.
2987333
3083558 3162773
3123001 3018058
3024932
3097866 2948522 3119164
3006448
3012205 3048461
3114155 2935511 3017765
3210601
68

3048813 3066838 3113092 3102190
EEB Description
Attempts to create a client alias fail when the alias name is already assigned to a real client. NetBackup Java User Interface issue. NetBackup Java User Interface issue. When a VMware guest has many IPv6 addresses associated with it, backups sometimes fail due to a limitation. The virtual machine with P2V conversion cannot boot up after a restore and displays 'Error loading operating system'. Some Windows client logs have an extension which ends in uppercase 'LOG'. The UNIX log gathering program (bpgetdebuglog) expects and only sees lowercase 'log' extensions. Therefore, uppercase logs cannot be found. An issue occurs when incremental backups of large multi-terabyte VMs are performed using the VMware policy type to a deduplication location, which causes bptm to fault (core dump) due to an error in the pdplugin regarding a negative number in the memory. During backups of Distributed File System Replication (DFSR) data, bpbkar32.exe experiences faults. A corrupt '.f' file causes the NetBackup Database Manager (bpdbm) to consume a lot of memory. A corrupt image file causes the NetBackup Database Manager (bpdbm) process to consume CPU and memory until the bpdbm process is killed. Attempts to browse images for a client result in the database system error code 220. NetBackup OpsCenter issue. Upgrades PostgreSQL to address the following security vulnerabilities: CVE-2012-3489 and CVE-2012-3488. NetBackup OpsCenter issue. VMware backups experience long delays during the 'IsSystemBootedUsingEFIFirmware()' call, which causes backups to fail with a status code 41. Backups for a Windows client experience delays in the call to 'IsSystemBootedUsingEFIFirmware()' in bpbkar, which causes the backup jobs to fail with a status code 41.
3012773
3026227
3092538
3099258
3019537
3092156
3117858 3163213 2931017
3111229 3217366
3189560
69

3151347
EEB Description
The bpVMutil process fails to completely restore a virtual machine; only two of the three disks are created. The tar32 process core dumps when it tries to restore data to the third disk. With NetBackup Accelerator enabled, all backups of Shadow Copy Components (SCC) are forced as full backups. A Distributed File System Replication (DFSR) backup by SCC path is always a full backup. With NetBackup Accelerator enabled, all backups of Shadow Copy Components (SCC) are forced as full backups. A Distributed File System Replication (DFSR) backup by SCC path is always a full backup. True image restore (TIR) fragment files are not closed during OpenStorage (OST) Direct Copy. An issue for OpenStorage Technology (OST) DirectCopy where the true image restore (TIR) fragment file is not closed. An issue for OpenStorage Technology (OST) DirectCopy where the true image restore (TIR) fragment file is not closed. Network Data Management Protocol (NDMP) restore jobs from tape fail a status code 5. The bptm log shows the following: 'read_data: unknown ndmp_task 3; EXITING with status 5.' A Storage Lifecycle Policy with snapshots fails if the client is at back level (before 7.5). NetBackup Systems Management (Policies, Scheduling, and so forth.) issue. If simultaneous duplications of Exchange GRT backups are initiated from a staging disk storage unit (DSU), one of them fails with status 191. Backup using SQLINSTANCE $ALL on SQL2008R2 server fails; Master database restore fails on MSSQL cluster setup,"Error encountered trying to read database images" while browsing images; TRXLOG backup aborted when TRXLOG and diff backup run simultaneously. OpenStorage Technology (OST) DirectCopy duplication jobs from Quantum DXi-series to tape fail with status 85 on the second fragment. The last file of OST DirectCopy duplications of non-NDMP images can be corrupt under certain tuned buffer size settings. There are issues with VSS snapshots and 156 errors. The bpbkar process crashes doing an Oracle proxy copy VxVM snapshot backup. An SLP-based off-host snapshot fails with status 49 and 43. Snapshot creation fails with 'pfi_find_active: Cannot find available snapshot'.
2962978
3198891
3184662
3040627
3047391
3126218
2948740 3184773 2870110
2754142, version 6
2792621, version 4
2895055, version 1 2955469, version 1
70

3035621, version 1
EEB Description
Backup jobs dependent on a snapshot cause multiple queries for storage server details. Large numbers of this type of backup job cause many queries to Disk Service Manager (DSM), which can lead to all DSM threads working that task. Cluster, AppCluster, and bprd credential requests can overwhelm Disk Service Manager. NetBackup Bare Metal Restore issue. Bundle fix for storage lifecycle policy and Auto Image Replication performance. The NetBackup Deployment Utility (nbdeployutil) report fails with the error 'Can't locate utf8.pm'. A backup fails because the SQL Agent cannot get the SQL Server backup timestamp within the default wait timeout window, and Dbbackup.exe is unable to retrieve SQL server properties from the registry to create an ODBC connect string. Backups of Windows virtual machines with a 5220 2.5.1 appliance backup host fail with a status code 130. The bpbkar process core dumps during VMware backups on the NetBackup Appliance version 2.5.2. VMware backups fail with an error code 130. The bpbkar process returns an error code 130. NetBackup Agent for Windows Client issue. NetBackup NDMP issue. Incremental backups are not marked eligible for true image restore (TIR) pruning. NetBackup Systems Management (Policies, Scheduling, and so forth.) issue.
3042003, version 1 3050708, version 1 3069121, version 1 3074196, version 1
3097439, version 1
3105184, version 2, 1
3134022, version 1
3137664, version 2, 1 3137665, version 2, 1 3146364, version 1 3156212, version 1 3156426, version 1 3201791, version 1

NB 7506 Release Notes

Uploaded by

Document Information

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 7506 Release Notes

Uploaded by

Copyright:

Available Formats

Symantec NetBackup 7.5.0.

Maintenance Release Update

Symantec NetBackup 7.5.0.6 Release Notes

Symantec Corporation 350 Ellis Street Mountain View, CA 94043 http://www.symantec.com

About Symantec Operations Readiness Tools

Contacting Technical Support

Licensing and registration

Support agreement resources

Technical Support ............................................................................................... 4 Chapter 1 New features and enhancements ...................................... 9

Platform compatibility ....................................................... 13

Product dependencies ........................................................ 19

Operational notes ................................................................ 29

End-of-life notifications ..................................................... 49

About the NetBackup 7.5.0.6 release content .............. 51

New features and enhancements

About NetBackup 7.5.0.6 new features and enhancements

New features and enhancements NetBackup 7.5.0.6 new features

NetBackup 7.5.0.6 new features

NetBackup 7.5.0.6 new enhancements and support

Platform support for the following operating systems:

Support for the following database and application agents:

Support for the following virtualization technologies:

Other new enhancements and support:

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 About NetBackup 7.5.0.x release compatibility

NetBackup master server

7.5 7.5 7.5 7.5

7.5.0.3 7.5.0.4 7.5.0.5 7.5.0.6

Platform compatibility NetBackup compatibility lists

NetBackup compatibility lists

NetBackup Enterprise Server and Server 7.x Hardware Compatibility List

Platform compatibility NetBackup compatibility lists

Platform compatibility NetBackup compatibility lists

Operating system patches and updates

Operating system patches and updates

Operating system patches and updates for NetBackup 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

AIX 5.3 TL12 SP2 (5300-1202-1036)

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

Product dependencies Operating system patches and updates

Table 3-1 Operating system type and version

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:

PHSS_35385 PHSS_32226 PHSS_37516

PHSS_27740 PHSS_26560 PHSS_32864

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.1003.347a) patch bundle

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