NB 7503 Release Notes

Symantec NetBackup™7.5.0.3 Release Notes

NetBackup 7.5.0.3

Maintenance Release

The software described in this book is furnished under a license agreement andmay be usedonly in accordance with the terms of the agreement.

Documentation version: 7.5.0.3

Legal NoticeCopyright © 2012 Symantec Corporation. All rights reserved.

Symantec and the Symantec Logo are trademarks or registered trademarks of SymantecCorporation or its affiliates in theU.S. and other countries. Other namesmaybe trademarksof their respective owners.

The product described in this document is distributed under licenses restricting its use,copying, distribution, and decompilation/reverse engineering. No part of this documentmay be reproduced in any form by any means without prior written authorization ofSymantec Corporation and its licensors, if any.

THEDOCUMENTATIONISPROVIDED"ASIS"ANDALLEXPRESSORIMPLIEDCONDITIONS,REPRESENTATIONS AND WARRANTIES, INCLUDING ANY IMPLIED WARRANTY OFMERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR NON-INFRINGEMENT,ARE DISCLAIMED, EXCEPT TO THE EXTENT THAT SUCH DISCLAIMERS ARE HELD TOBELEGALLYINVALID.SYMANTECCORPORATIONSHALLNOTBELIABLEFORINCIDENTALOR CONSEQUENTIAL DAMAGES IN CONNECTION WITH THE FURNISHING,PERFORMANCE, OR USE OF THIS DOCUMENTATION. THE INFORMATION CONTAINEDIN THIS DOCUMENTATION IS SUBJECT TO CHANGE WITHOUT NOTICE.

The Licensed Software andDocumentation are deemed to be commercial computer softwareas defined in FAR12.212 and subject to restricted rights as defined in FARSection 52.227-19"Commercial Computer Software - Restricted Rights" and DFARS 227.7202, "Rights inCommercial Computer Software or Commercial Computer Software Documentation", asapplicable, and any successor regulations. Any use, modification, reproduction release,performance, display or disclosure of the Licensed Software andDocumentation by theU.S.Government shall be solely in accordance with the terms of this Agreement.

Symantec Corporation350 Ellis StreetMountain View, CA 94043

http://www.symantec.com

http://www.symantec.com

Technical SupportSymantec Technical Support maintains support centers globally. TechnicalSupport’s primary role is to respond to specific queries about product featuresand functionality. TheTechnical Support group also creates content for our onlineKnowledge Base. The Technical Support group works collaboratively with theother functional areas within Symantec to answer your questions in a timelyfashion. For example, theTechnical Support groupworkswithProductEngineeringand Symantec Security Response to provide alerting services and virus definitionupdates.

Symantec’s support offerings include the following:

■ A range of support options that give you the flexibility to select the rightamount of service for any size organization

■ Telephone and/or Web-based support that provides rapid response andup-to-the-minute information

■ Upgrade assurance that delivers software upgrades

■ Global support purchased on a regional business hours or 24 hours a day, 7days a week basis

■ Premium service offerings that include Account Management Services

For information about Symantec’s support offerings, you can visit our Web siteat the following URL:

www.symantec.com/business/support/

All support services will be delivered in accordance with your support agreementand the then-current enterprise technical support policy.

About Symantec Operations Readiness ToolsSymantec Operations Readiness Tools (SORT) is a set of Web-based tools thatsupports Symantec enterprise products. ForNetBackup, SORTprovides the abilityto collect, analyze, and report on host configurations across UNIX/Linux orWindows environments. This data helps to assesswhether your systems are readyfor an initial NetBackup installation or for an upgrade from your current version.

To access SORT, go to the following Web page:

http://sort.symantec.com/netbackup

Once you get to the SORT page, more information is available as follows:

■ Installation and Upgrade ChecklistUse this tool to create a checklist to see if your system is ready for aNetBackupinstallation or an upgrade.


http://sort.symantec.com/netbackup

■ Hot fix and EEB Release AuditorUse this tool to find out whether a release that you plan to install contains thehot fixes that you need.

■ Custom ReportsUse this tool to get recommendations for your systemandSymantec enterpriseproducts, tips for risk assessment, and product license tracking.

Contacting Technical SupportCustomers with a current support agreement may access Technical Supportinformation at the following URL:


Before contacting Technical Support, make sure you have satisfied the systemrequirements that are listed in your product documentation. Also, you should beat the computer onwhich theproblemoccurred, in case it is necessary to replicatethe problem.

When you contact Technical Support, please have the following informationavailable:

■ 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 registrationIf yourSymantecproduct requires registrationor a licensekey, access our technicalsupport Web page at the following URL:




Customer serviceCustomer service information is available at the following URL:


Customer Service is available to assist with non-technical questions, such as thefollowing 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 resourcesIf youwant to contact Symantec regarding an existing support agreement, pleasecontact the support agreement administration team for your region as follows:

[email protected] and Japan

[email protected], Middle-East, and Africa

[email protected] America and Latin America


mailto:[email protected]



Technical Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

Chapter 1 New features and enhancements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

About NetBackup 7.5.0.3 new features and enhancements ... . . . . . . . . . . . . . . . . . . 9

Chapter 2 Platform compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

About NetBackup 7.5.0.x release compatibility ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11About compatibility with NetBackup 7.5 ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

NetBackup compatibility lists ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Chapter 3 Product dependencies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

About product dependencies ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17Operating system patches and updates ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17VxFS and VxVM compatible versions .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

Chapter 4 Operational notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

About operational notes in NetBackup 7.5.0.3 ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27About general NetBackup 7.5.0.3 notes ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27About NetBackup OpsCenter notes ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

Chapter 5 End-of-life notifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

About NetBackup end-of-life notifications .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

Appendix A About the current release content index . . . . . . . . . . . . . . . . . . . . . . . . 37

About the NetBackup 7.5.0.3 master Etrack index list ... . . . . . . . . . . . . . . . . . . . . . . 37

Appendix B About the current release content . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

About release content conventions .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39About NetBackup 7.5.0.3 release content ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40NetBackup 7.5.0.3 Emergency Engineering Binary (EEB) listing .... . . . . . . . . 61

Contents

Contents8

New features andenhancements

This chapter includes the following topics:

■ About NetBackup 7.5.0.3 new features and enhancements

About NetBackup 7.5.0.3 new features andenhancements

This release offers the following enhancements:

■ NetBackup for VMware now available on Linux:Until now, NetBackup for VMware required the use of a Windows client foran off-host backup. NowNetBackup for VMware is supported on certain Linuxclients.For a list of supported Linux versions for the backup host, see:http://www.symantec.com/docs/TECH127089For the 7.5.0.x version of the NetBackup for VMware Guide, see:http://www.symantec/com/docs/DOC5605

■ This release of NetBackup offers support for Solaris 11 master servers.

This release contains fixes to the known issues that pertain to thecustomer-specific issues that have been documented in the form of a Titan Case.Many of these fixes are available as individual engineering binaries andengineering bundles. These EEBswere created to address specific customer issueswith a previous version of NetBackup. This maintenance release lists thoseengineering binaries and bundles.

See “About NetBackup 7.5.0.3 release content” on page 40.

See “NetBackup 7.5.0.3 Emergency Engineering Binary (EEB) listing” on page 61.

1Chapter

http://www.symantec.com/docs/TECH127089

http://www.symantec.com/docs/DOC5605

New features and enhancementsAbout NetBackup 7.5.0.3 new features and enhancements

10

Platform compatibility


■ About NetBackup 7.5.0.x release compatibility

■ NetBackup compatibility lists

About NetBackup 7.5.0.x release compatibilityThis release supports the platforms and binary sizes that were documented inthe NetBackup 7.5 Release Notes for UNIX, Windows, and Linux document. Thefollowing sections describe how to locate the latest compatibility lists that areavailable on the Symantec Support Web site. In addition, the Binary Sizes tablehas been included for your convenience.

For more information about platform compatibility, see the following:

■ NetBackup 7.5 Release Notes for UNIX, Windows, and Linux on the SymantecSupport Web site.http://www.symantec.com/docs/DOC5041

■ NetBackup Enterprise Server and Server 7.x OS Software Compatibility Listhttp://www.symantec.com/docs/TECH59978

About compatibility with NetBackup 7.5Symantec NetBackup has always maintained that the master server within yourenvironmentmust be at a version level that is equal to or greater than the versionlevels of your media servers and client servers within the same environment.With NetBackup and the NetBackup Appliances, you can apply a maintenanceupdate (for example 7.5.0.1) to a media server or client server within anenvironment where your master server is at a version level of 7.5. This samescenario can apply to the maintenance updates that are released under a minorrelease or release update.

2Chapter



For information about NetBackup compatibility with the NetBackup appliances,see the NetBackup 5xxx Appliance Compatibility Technote on the SymantecSupport Web site.

Symantec NetBackup does not support any scenario where a minor release orrelease update is at a higher version level that the parent server. For instance,the following examples apply.

■ If a master server is at 7.1, then the media servers and client servers cannotbe at a single-dot version level that is higher than 7.1, such as 7.2 or 7.5.

■ If a master server is at 7.1, then the media servers and client servers cannotbe at a double-dot version level that is higher than 7.1, such as 7.1.x.

■ If a master server is at 7.1.1, then the media servers and client servers cannotbe at a double-dot version level that is higher than 7.1.1, such as 7.1.2.

The following table uses only the NetBackup 7.1 product line to demonstrate thevarious compatibility schemes that a mature product line can support. In thisexample,maintenance updates have been released. The same schemes applywiththe new NetBackup 7.5 line.

Table 2-1 NetBackup release compatibility matrix where maintenance updateshave been released

NetBackup clientNetBackup media serverNetBackup master server

6.x, 7.16.x, 7.17.1

6.x, 7.1.0.16.x, 7.17.1

6.x, 7.1.0.26.x, 7.17.1

6.x, 7.1.0.16.x, 7.1.0.17.1

6.x, 7.1.0.26.x, 7.1.0.17.1

6.x, 7.1.0.16.x, 7.1.0.27.1

6.x, 7.1.0.26.x, 7.1.0.27.1

6.x, 7.1.x.x, 7.56.x, 7.1.x.x, 7.57.5

The following table shows the various compatibility schemes that are supportedwith the current NetBackup 7.5 product line.

Platform compatibilityAbout NetBackup 7.5.0.x release compatibility

12


Table 2-2 NetBackup release compatibility for the 7.5 product line

NetBackup clientNetBackup mediaserver

NetBackup masterserver

6.06.07.5

6.0, 6.56.57.5

6.0, 6.5, 7.07.07.5

6.0, 6.5, 7.0, 7.0.17.0.17.5

6.0, 6.5, 7.0, 7.0.1, 7.0.27.0.27.5

6.0, 6.5, 7.0, 7.0.x, 7.1, 7.1.0.x7.17.5

6.0, 6.5, 7.0, 7.0.x, 7.1, 7.1.0.x7.1.0.17.5

6.0, 6.5, 7.0, 7.0.x, 7.1, 7.1.0.x7.1.0.27.5

6.0, 6.5, 7.0, 7.0.x, 7.1, 7.1.0.x7.1.0.37.5

6.0, 6.5, 7.0, 7.0.x, 7.1, 7.1.0.x7.1.0.47.5

6.0, 6.5, 7.0, 7.0.x, 7.1, 7.1.0.x, 7.57.57.5

6.0, 6.5, 7.0, 7.0.x, 7.1, 7.1.0.x, 7.5, 7.5.0.x7.5.0.17.5

6.0, 6.5, 7.0, 7.0.x, 7.1, 7.1.0.x, 7.5, 7.5.0.x7.5.0.37.5

Note: Support for the NetBackup 6.x product line is scheduled to end October,2012.

NetBackup compatibility listsThemost up-to-date compatibility information on platforms, peripherals, drives,and libraries is located in various compatibility lists on the Symantec SupportWeb site. You can use the following methods to locate these lists:

■ The following URL guides you to a set of tools that can help you locate thelatest platforms, peripherals, drives, and libraries.https://sort.symantec.com/netbackupFor NetBackup, SORT provides an Installation and Upgrade Checklist reportas well as the ability to collect, analyze, and report on host configurationsacrossUNIX/Linux orWindows environments. In addition, you can determinein what release whether any hot fixes or EEBs you have installed are fixed.

13Platform compatibilityNetBackup compatibility lists

https://sort.symantec.com/netbackup

You can use this data to assess whether your systems are ready to install orupgrade to this release.

■ If you want to view a specific compatibility list, you can find links to each listthat is posted on the Symantec Support Web site:http://www.symantec.com/docs/TECH59978

The following items describe each of the compatibility lists that are available.

■ TheNetBackup Enterprise Server and Server 7.x OS Software CompatibilityList contains information about the operating system (OS) level and theversion that is required to be compatiblewith aNetBackupmaster ormediaserver. It also describes the OS level and the version that is required to becompatible with a NetBackup client. Predecessors and successors to thedocumented operating system levels may function without difficulty, aslong as the release provides binary compatibility with the documentedoperating system.

That list contains information about each of the following NetBackupEnterprise features:

■ NetBackup Enterprise servers and client

■ Bare Metal Restore (BMR)

■ NetBackup Access Control (NBAC)

■ Network Data Management Protocol (NDMP)

■ NetBackup SAN Client and Fiber Transport

■ NetBackup Virtual System compatibility

■ MSEO (media server encryption option)

■ NetBackup Media Server Deduplication Option

■ NetBackup OpsCenter

■ File System Capability

NetBackup compatibility for a platform or OS version requires platformvendor support for that product. The platform compatibility lists thatNetBackup maintains are subject to change as vendors add and dropplatforms or OS versions.

■ TheNetBackup server 7.x hardware compatibility list includes informationfor compatible drives, libraries, virtual tape devices, robot-types,fibre-channel HBAs, switches, routers, bridges, iSCSI configurations, andencryption devices

Platform compatibilityNetBackup compatibility lists

14


That list includes information about the compatible drives, robot types,switches, routers, and bridges, and iSCSI configurations that coincidewiththe following hardware:

■ OpenStorage

■ Virtual tape libraries (VTLs)

■ Network Data Management Protocol (NDMP)

■ Host bus adapters (HBAs)

■ Encryption

■ NetBackup Database Agent 7.x Software Compatibility ListThis compatibility list contains the most current platform compatibilityinformation for NetBackup database agents.

■ NetBackup 7.x Snapshot Client compatibility lists

■ NetBackup 7.x BMR File System and VolumeManager compatibility lists

See also the NetBackup Bare Metal Restore Administrator's Guide for thefollowing additional compatibility lists:

■ BMR compatible shared resource tree (SRT) versions

■ BMR compatible file systems and volume managers

■ BMR compatible cluster solutions

■ BMR disk space requirements

■ NetBackup7.x Cluster Compatibility List

■ NetBackup Desktop/Laptop Option compatibility list

■ Backup Exec Tape Reader compatibility list

15Platform compatibilityNetBackup compatibility lists

Platform compatibilityNetBackup compatibility lists

16

Product dependencies


■ About product dependencies

■ Operating system patches and updates

■ VxFS and VxVM compatible versions

About product dependenciesThis release requires the same product dependencies that were documented inthe NetBackup 7.5 Release Notes for UNIX, Windows, and Linux document. Thefollowing sections describe the product dependencies and VxFS and VxVMcompatible versions.


Operating system patches and updatesThis topic provides information on the product dependencies of this release ofNetBackup. You should verify that your operating system is up-to-date with allof the latest patches and upgrades before you install NetBackup. This section isa guide to informyou of the operating systems that require a patch or an upgrade.

Table 3-1 provides the known, minimum operating system (OS) patches andupdates. A vendormayhave released amore recent patch that supersedes a patchthat is listed in this table. Symantec recommends that you visit the Support Website of that particular vendor for their latest patch information.

3Chapter


Table 3-1 Operating system patches and updates for NetBackup

NotesPatchOperating system typeand version

You may need to restart after changing to version9.0.0.3.

AIX runtime libraries 8.0.0.10or 9.0.0.3 or later

AIX 5.3

For the xlC.rte 8.0.0.10 fileset, you may needto install the IY91284 fix to avoid a potential issuewhen creating or updating the NetBackup database.The IY91284 fix is part of Maintenance Level 6.

xlC.rte 8.0.0.10 fileset

NetBackup 7.5 requires the AIX 5.3 TL12 SP2(5300-12- 02-1036)MaintenancePack as aminimum.(Higher patch levels should also work.)

You can use the oslevel -s command to verifywhat Maintenance Pack level you have installed.

AIX 5.3 TL12 SP2 (5300-12-02-1036)

NetBackup 7.5 requires the AIX 6.1 TL5 SP5(6100-05-02-1034)MaintenancePack as aminimum.(Higher patch levels should also work.)

You can use the oslevel -s command to verifywhat Maintenance Pack level you have installed.

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

AIX 6.1

The runtime libraries need to be at 9.0.0.3 or later.You may need to restart after you change to version9.0.0.3.

AIX runtime libraries 9.0.0.3 orlater

If you install AT on an HP-UX platform, this patchis required.

COMPLIBS.LIBM-PS32HP-UX

Networking.NET-RUN:/usr/lib/libipv6.sl

HP-UX IA64

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

Product dependenciesOperating system patches and updates

18

Table 3-1 Operating system patches and updates for NetBackup (continued)


Networking.NET2-RUN:/usr/lib/hpux64/libipv6.so.1

Networking.NET2-RUN:/usr/lib/libipv6.1

ForHP-UXPA-RISCplatforms, this fileset is required:Networking.NET-RUN:/usr/lib/libipv6.sl

HP-UX PA-RISC

ForHP-UXPA-RISCplatforms, this fileset is required:Networking.NET-RUN-64:/usr/lib/pa20_64/libipv6.1

ForHP-UXPA-RISCplatforms, this fileset is required:Networking.NET-RUN-64:/usr/lib/pa20_64/libipv6.sl

ForHP-UXPA-RISCplatforms, this fileset is required:Networking.NET2-RUN:/usr/lib/libipv6.1

This patch is required for JAVA 6.0.PHSS_35385HP-UX 11.11

This patch is a LIBCL patch.PHSS_32226

Contains fixes for the following:

■ QXCR1000593919: purifyplus dumps corein PA32

■ QXCR1000589142: dld crash inLL_new_descendent_listwhentheaCCapplicationis exiting.


■ QXCR1000746161: dlsym() hangs

■ QXCR1000593999: dld emits assert messagesfor chatr +mem_check enabled 64-bitexecutables

PHSS_37516

This patch is necessary to enable any C++ runtimecode to work properly.

PHSS_26946

This patch is a libc cumulative patch.PHSS_27740

This patch contains a linker tools cumulative patch.PHSS_26560

19Product dependenciesOperating system patches and updates



That is a recommended critical patch from HP thatis required for successful NetBackup client backups.

PHSS_32864

This patch enables HP-UX 11.11 mmap() to uselarge files from 2GB to 4GB.

PHKL_26233

That is a recommended critical patch from HP thatis required for successful NetBackup client backups.

PHSS_35379

That is a recommended critical patch from HP thatis required for NetBackup to use VxSS.

PHCO_29029

Allow POLL_INTERVAL to be set to zero in /var/stm/config/tools/monitor/dm_stape.cfg.That disables the dm_stapemonitor within theEvent Monitoring System. Symantec recommendsthat you upgrade to IPR0109.

PHSS_24045

This patch can cause problems with the programsthat have the setuid bit set. Hewlett-Packard ’s ITresource centerWeb site contains information aboutthis patch.

www1.itrc.hp.com

PHSS_30970

S700_800 11.11 libc cumulative patch

The above patch has dependency on the followingpatches:

■ PHCO_31923 (critical patch): s700_80011.11 libccumulative header file patch

■ PHKL_34805 : 700_80011.11 JFS3.3 patch;mmap

PHCO_35743


Symantec recommends that all customers running11.23 install this patch. This applies to HP PARISConly because HP Itanium has moved to 11.31.

PHCO_33431

That is a recommended critical patch from HP thatis required so that dlopen works properly.

PHSS_34858


20



That is a recommended critical patch from HP thatNetBackup requires, particularly when you attemptto run NetBackup with NetBackup Access Control(NBAC).

PHKL_31500

Contains fixes for the following:

■ QXCR1000593919: purifyplus dumps corein PA32


■ QXCR1000746161: dlsym() hangs

■ QXCR1000593999: dld emits assert messagesfor chatr +mem_check enabled 64-bitexecutables

PHSS_37492


This patch bundle is required for NetBackup mediaserver support. This is an HP-UX September 2008patch bundle.

QPK1131 (B.11.31.0809.326)patch bundle

The operating system version must be SUSE LinuxEnterprise Server 10 update 2 or greater to runNetBackup 7.0.

SUSE Linux Enterprise Server10 update 2

SUSE Linux EnterpriseServer 10 x64

Change Request ID - 6815915111712-11 (or greater)Solaris 9 SPARC 64-bitclient

111722-04 (or greater)

Patch: 112908-29 (or greater)

Patch: 112874-31 (or greater)

Change Request ID - 6723423122300-53

The server is supported on update 4 (08/07) andnewer.

update 4 (08/07) and newerSolaris 10 SPARC 64-bit(server and client)




Symantec recommends that you download therecommended patch set dated June 2011 from theOracle SupportWeb site. This patch set contains thefollowing patches:

■ 118777-17 (SunOS 5.10: Sun GigaSwift Ethernet1.0 driver patch)

■ 139555-08 (Kernel patch with C++ libraryupdates).

■ 142394-01 (Internet Control Message Protocol(ICMP) patch)

■ 143513-02 (DataLinkAdmincommand forSolaris(DLADM) patch)

■ 141562-02 (Address Resolution Protocol (ARP)patch)

The following patches are for Solaris 10 SPARCwithNXGE cards:

■ 142909-17 (SunOS 5.10: nxge patch)

■ 143897-03 (Distributed Link Software patch)

■ 143135-03 (Aggregation patch)

■ 119963-21 (Change Request ID - 6815915)


Recommended OS Patchset -dated June 2011 or later


22

https://support.oracle.com



Symantec recommends that you download therecommended patch set dated 12/28/2011 from theOracle Support Web site.

Contains the following patches:

■ 118778-15 (SunOS 5.10_x86: Sun GigaSwiftEthernet 1.0 driver patch)

■ 139556-08 (Kernel patch with C++ libraryupdates)

■ 142395-01 (SunOS 5.10_x86: ICMP patch)

■ 143514-02 (SunOS 5.10_x86: Data Link Admincommand for Solaris patch)

■ 147259-02 (SunOS 5.10_x86: Aggregation patch)

■ 142910-17 (SunOS 5.10_x86 kernel patch toinclude NXGE fixes)

■ 142910-17 (SunOS 5.10_x86: Distributed LinkSoftware patch)

■ 143136-03 (SunOS 5.10_x86: Aggregation patch)



Recommended OS Patchset -dated June 2011 or later

Solaris 10 x86-64

Microsoft microcode reliability update.KB936357Windows XP x86-32

Hot fix for hangs of connection attempts by PBX.KB928646Windows XP x86-64

Microsoft microcode reliability update.KB936357Windows Vista x86-32

Contains the necessary updates to ensure that youcan back up encrypted files.

KB952696

Microsoft microcode reliability update.KB936357Windows Vista x86-64


KB952696

Contains the necessary updates to run VolumeShadow Copy.

KB913648Windows Server 2003 IA64(SP1 & SP2)

Hot fix for hangs of connection attempts by PBX.KB928646

Microsoft Storport hot fix.KB883646Windows Server 2003x86-32 (SP1 & SP2)


https://support.oracle.com




KB913648

Microsoft microcode reliability update.KB936357

TCP/IP protocol driver triggers a disconnect eventrandomly. Required for master and media servers.

KB971383Windows Server 2003x86-32 (SP2)

Microsoft Storport hot fix.KB883646Windows Server 2003x86-64 (SP1 & SP2)


KB913648

Hot fix for hangs of connection attempts by PBX.KB928646

Microsoft microcode reliability update.KB936357

TCP/IP protocol driver triggers a disconnect eventrandomly. Required for master and media servers.

KB971383Windows Server 2003x86-64 (SP2)


KB952696Windows Server 2008x86-32


KB952696Windows Server 2008x86-64


KB952696Windows Server 2008 IA64

VxFS and VxVM compatible versionsTable3-2 shows theversionsofVxFSandVxVMthat are compatiblewithSymantecNetBackup, and the corresponding operating systems for each.

Table 3-2 Versions of VxFS and VxVM that are compatible with SymantecNetBackup

NotesVersion of VxVMVersion of VxFSOS VersionOperating system

up to 5.1 SP15.0MP3up to 5.1 SP15.3 (64 bit)AIX 5L

5.0 MP3 and higher5.0 MP3 and higher6.1 (64 bit)

Product dependenciesVxFS and VxVM compatible versions

24

Table 3-2 Versions of VxFS and VxVM that are compatible with SymantecNetBackup (continued)


5.0 MP3 and higher5.0 MP3 and higher7.1 (64 bit)

3.5 only3.3 and 3.511.11HP-UX PA-RISC

3.5, 4.1, and 5.03.5, 4.1, and 5.011.23

4.1 and higher4.1 and higher11.31

4.1 and higher4.1 and higher11.31HP-UX IA64

4.1 to 4.1MP4RP44.1 to 4.1MP4RP4IA64Red Hat Enterprise Linux 4.0(AS)

5.0 LoP phase1, phase25.0 LoP phase1,phase2, and phase 3only

POWER

LxRT4.1MP4RP1andhigheron the 4.1 line, 5.0MP3 andhigher on the 5.0 line

LxRT4.1MP4 andhigher on the 4.1line, 5.0MP3 andhigher on the 5.0 line

x64Red Hat Enterprise Linux 5.0(AS)

4.1MP4RP1 and higher inthe 4.1 code line only

LxRT4.1MP4 andhigher on the 4.1code line only

IA64

5.0RU3 and higher5.0RU3 and 5.0RU4only

POWER

x64Red Hat Enterprise Linux 5.0(base)

IA64

POWER

z/Architecture

x64Red Hat Enterprise Linux 6.0(AS)

x64Red Hat Enterprise Linux 6.0(base)

z/Architecture

25Product dependenciesVxFS and VxVM compatible versions

Table 3-2 Versions of VxFS and VxVM that are compatible with SymantecNetBackup (continued)


5.1SP1 and higher5.1SP1 and higherSPARCSolaris 9, 10, 11, 11 Express

4.1 MP2 and higher4.1 MP2 and higherx64Solaris 10, 11, 11 Express

4.1MP3 and higher in 4.1codeline. 5.0MP3 andhigher on 5.0 codeline.

4.1MP3andhigher in4.1 codeline. 5.0MP3and higher on 5.0codeline.

x64SUSE Linux Enterprise Server10

4.1MP3 and higher in 4.1codeline only.

4.1MP3andhigher in4.1 codeline only.

IA64

5.0RU3 and higher5.0RU3 and 5.0RU4only

POWER

5.0RU1 and higher5.0RU1 and higherx64SUSE Linux Enterprise Server11

NANAIA64

5.0RU4 and higher5.0RU4 and higherPOWER

4.3 and higherNAx86Windows

4.3 and higherNAx64Windows

NetBackup has improved its integration with the Veritas File System (VxFS)product to ensure interoperability on all compatible VxFS versions. If you run aVxFSversion that is older thanVxFS4.0 thenyouneed to install newVxFS librarieson the client to back up the systems that run VxFS. You can search and downloadthe appropriateVxFS libraries to your system fromPatchCentral on the SymantecSupport Web site.

See, https://sort.symantec.com/labs/patch.

See, http://entsupport.symantec.com/docs/320193.

Product dependenciesVxFS and VxVM compatible versions

26

Operational notes


■ About operational notes in NetBackup 7.5.0.3

■ About general NetBackup 7.5.0.3 notes

■ About NetBackup OpsCenter notes

About operational notes in NetBackup 7.5.0.3The 7.5.0.3 Maintenance Release is based on the NetBackup 7.5 release. Thatmeans the operational notes that were documented in NetBackup 7.5 may stillapply to this release. Therefore, you should review that document if you have anyquestions or issues with this maintenance release.


This chapter contains the topics that explain important aspects of NetBackup7.5.0.3 operations that may not be documented elsewhere in the NetBackupdocumentation set. This document is posted on the Symantec Support Web siteandmaybeupdatedafter theGArelease ofNetBackup7.5.0.3. Therefore, Symantecrecommends that you refer to the following Technote on the Symantec SupportWeb site to view the latest release information.


About general NetBackup 7.5.0.3 notesThe following items describe the known issues that exist in theNetBackup 7.5.0.3release.

■ Concurrent restores of virtualmachinemay fail when they use a Linux restorehost on a SAN.

4Chapter



When using the SAN transport mode to restore multiple virtual machines atthe same time, one ormore of the restore jobsmay fail. The job status logmaycontain messages similar to the following:4/19/2012 1:16:14 PM - Error bptm(pid=30649) cannot write data to

socket, Connection reset by peer

4/19/2012 1:16:14 PM - Info bptm(pid=30648) EXITING with status

24

Symantec has opened a VMware support request on this issue: 12172237605.Try the following:

■ On the virtual machine Options dialog box , select Thin Provisioning forthe format of the restored virtual disks and retry the restore.

■ If that fails, select NBD as the transport mode on the Recovery Optionsdialog box and try the restore again.

■ An Accelerator backup can fail with a status code 84. The error can occur forseveral reasons. A possible solution is to expire backup images. Before youexpire backup images, do the following:

■ Identify the reason for the backup failure. If the backup failed because ittried to copy data from a previous backup image, the backup image needsto be examined.

■ If the backup image was a restarted or resumed backup, the backup imageneeds to be verified.

■ If that backup image fails the verification, the backup header informationfor that backup image needs to be examined.

■ If the data amount in the fragments does not match the amount of datathat there should be, then expire that backup image.

■ NetBackup 7.5.0.3 does not support VMware backup hosts or restore hosts onRHEL (Red Hat). If the policy's VMware backup host option is Backup MediaServer and one media server is on RHEL, NetBackup may incorrectly selectthat server as the backup host. The backup may fail with a status code 69:invalid filelist specification.

The issue will be fixed in a future release of NetBackup.As a workaround, change the policy's VMware backup host option to specifya media server that is supported as the backup host. For NetBackup 7.5.0.3,the supported platforms for backup hosts are Windows 2003 and 2008, andSUSE10and11. Formore details on supportedplatforms, refer to the followingTechnote:http://www.symantec.com/docs/TECH127089

Operational notesAbout general NetBackup 7.5.0.3 notes

28


■ On an HP-UX platform, the installation of NetBackup versions 7.5.0.1 or laterfails when it is installed into a Bare Metal Restore shared resource tree.To work around this issue, use NetBackup 7.5 to restore the HP-UX client thatuses a Bare Metal Restore shared resource tree.

■ -SetupMaster sets up themaster server to useNetBackupAccess Control.Thissetup adds the root and administrator by default to the NBU_Security Admin

group. The first time that you use -SetupMaster with the -fsa option addsthe first security administration member to the NBU_Security Admin group.If you have configured NetBackup Access Control already with -SetupMaster

and without the -fsa option, use the -AddUser option to add any moremembers.In the case of a Windows cluster, you are prompted for the password for yourcurrent operating system user identity.

■ TheNetBackupAccelerator inNetBackup7.5.0.3 does not support ClientDirectwhen the clientNetBackup version is greater than theNetBackupmedia serverversion. For example, a 7.5.0.1 media server does not support a client backupthat runs 7.5.0.3 when policies include both Client Direct and Acceleratorbackup selections. The media server and client version mismatches in thisconfiguration cause the Client Direct nbostpxy process on the client to coredump. The version incompatibility is resolved in the next NetBackup 7.5maintenance patch.

■ Files that are restored as links are not renamed properly. If the hard link filesare restored to an alternate location, the files that are restored as links pointto the original location. They should point to the alternate location. The issueoccurs when the user creates a policy and takes a mapped FullVM backup ofan RHEL virtual machine.

■ After an upgrade toNetBackup 7.5.0.3, VMware backupsmay fail with a statuscode 6 and the following message: the backup failed to back up the

requested files.

For more information, refer to the following Technote:http://www.symantec.com/docs/TECH191198

■ After an upgrade to 7.5.x, VMware backups may be slower than expected.For more information, refer to the following Technote:http://www.symantec.com/docs/TECH191183

About NetBackup OpsCenter notesThe following operational notes that pertain toNetBackup'sOpsCenter are carriedover from the NetBackup 7.5.0.1 Release Notes.

29Operational notesAbout NetBackup OpsCenter notes



■ In the 7.5.0.3 version, the NetBackup database has been upgraded to SybaseEBF 11.0.1+2789. To adapt to the changes inNetBackup, theOpsCenter 7.5.0.1database has also been upgraded to the Sybase EBF 11.0.1+2744 version.

■ In the case of Enterprise Vault, OpsCenter reports only on email archivingdata that pertains toMicrosoft Exchange Servers. If email archiving is disabledin Enterprise Vault, OpsCenter cannot collect the required data. Therefore,you cannot see any data on the Enterprise Vault Archiving reports inOpsCenter.This limitation in Enterprise Vault reporting is not included in the NetBackupOpsCenter Administrator Guide.

■ OpsCenter doesnot support creatingor editingmultiple reports simultaneouslyfor the same user session from different tabs or windows. You cannot openthe sameOpsCenter console in twoormore browser tabs orwindows and createor edit standard and customreports simultaneously. That causes an exceptionto occur.

■ The Deduplication reports do not show any data when you select the ReportOn parameter as Storage Unit Name.

■ For VMware or Hyper-V clients, the search and restore operations work onlyif the client name is the same as host name. If the client name is the same asdisplay name, UUID, or DNS name then only the Search functionality isavailable. You cannot perform restore operations in this case. The followingtable provides details onwhether Search andRestore functionality is availablewhen the client name is the host name, display name, etc.:

Client Name Type Search Restore

Host Name Yes Yes

Display Name Yes No

UUID Yes No

DNS Name Yes No

■ OpsCenter installation and deployment information and best practices.

The following list contains information about installing OpsCenter and somebest practices information:

■ Symantec recommends that you do not cancel or interrupt the installationprocess once it is started.

■ You may be unable to logon to the OpsCenter interface if it is installed ona server that has an underscore(_) in the host name. To avoid this issue,ensure that the OpsCenter Server host name does not contain anyunderscores like opshost.

Operational notesAbout NetBackup OpsCenter notes

30

■ Installing OpsCenter components in a location that is mounted from aremote host is not supported.

■ A file selection list that contains more than 50 items does not appear inOpsCenter.For a specific job ID in anOpsCenterAnalytics custom report, breakup job datais available only for 50 job directories. That is becausewhen aNetBackuppolicyor job is associated with more than 50 backup selections, data is available foronly 50 backup selections. The NetBackup user interface truncates data forthe subsequent backup selections (greater than 50).WithVBR, you canview thebreakup job information for all of the jobdirectoriesthat are associated with a job or policy. That is because data collection in VBRhappened through CLI’s (and not through nbsl).

■ OpsCenter does not provide the option to purge breakup jobs.Unlike VBR, OpsCenter does not provide the option to purge breakup jobs. Inthe VBR console, you can purge specific breakup jobs from the Settings >Global Settings > Data Retention section.

■ An uninstall script is removed if an uninstall process for an OpsCenter Serveror Agent is canceled or interrupted.If an uninstallation process for OpsCenter Server or Agent is canceled orinterrupted on UNIX, then the uninstall script (uninstallOpsCenterServerand uninstallOpsCenterAgent) is removed from /opt/VRTS/install. If youwant to uninstall theOpsCenter Server again, you canuse the uninstall scriptsfrom the OpsCenter DVD.

■ Some result sets for a stored procedure that has multiple result sets may notappear.When you run a stored procedure that has multiple result sets, the output ofonly the first result set is displayed on the interface. The output of other resultsets is not shown on the interface.

■ The number of characters for a virtual name by the clustering technology onWindows is limited.The virtual host name must be the short name (not FQDN) and less than 15characters.

■ Some reports may only consider Full and Incremental schedule type jobs.

On applying Schedule/Level Type filter with value All, the following reportsconsider only Full and Incremental schedule type jobs:

■ Advanced Success Rate

■ All Failed Backups

■ Consecutive Failures Report


■ Success Rate Line

■ The NetBackupOpsCenter resource is offline after you have installed anOpsCenter cluster.After installing an OpsCenter cluster on a Windows 2008 R2 x64 system, youmustmanually bring the NetBackupOpsCenter resource online. You can bringthe NetBackupOpsCenter resource online from the command line interface orby using the cluster user interface.You can use the following command:hares -online <resource name> -sys <Name of the active node>

Example: hares -online newonelatest-OpsCenter -sys OPS-CLUSTER-1

■ On Windows systems, the log.conf file is not created properly. That causesthe vxlogview to return a No logs to be displayed message.

Use the following commands to view logs for OpsCenter GUI (OID-147) andInfrastructure components (OID-761):

■ OpsCenter GUI:

■ <INSTALL_PATH>\OpsCenter\server\bin\vxlogview -p 58330 -o

147 -G

■ <INSTALL_PATH>\OpsCenter\gui\logs

■ Infrastructure components:

■ <INSTALL_PATH>\OpsCenter\server\bin\vxlogview -p 58330 -o

761 -G

■ <INSTALL_PATH>\OpsCenter\gui\logs

■ The object merger utility in OpsCenter fails on the master server.The object merger utility in OpsCenter (Settings > Configuration > Objectmerger) does not work (fails) for a master server. The object merger utilityworks for clients and media servers.

■ TheCustomTabularBackupandCustom-Clientcount report does not returndata after an upgrade from VBR.TheCustomTabularBackupandCustom-Clientcount report does not returnany data after you have upgraded from VBR to OpsCenter.

Towork around this issue, youmustmanually change the filter settings to getthe correct report data after the upgrade is complete. The following steps guideyou to change the filter settings:

■ Open the report, then select Edit Report.

■ From the Filters section, select Job.


32

■ FromtheColumndrop-down list, selectProductType. Thedefault operatoris the equals sign character, =.

■ From the Value drop-down list, select the same product type that youselected for VBR and click Add.

■ Click Next to view the report. Once the changes are made, the reportsdisplay the correct data.

■ Save the report.

■ The OpsCenter server can stop receiving events from the master server aftera NetBackup upgrade.

If all following conditions are applicable, add theOPS_CENTER_SERVER_NAME entry to the bp.conf file on UNIX or theregistry on Windows to set OpsCenter's server name. Symantec recommendsthat you do add the entry before you attempt to upgrade.

■ The REQUIRED_INTERFACE is configured on the master server.

■ The OpsCenter server monitors the master server.

■ TheOPS_CENTER_SERVER_NAME entry isnot configuredon themasterserver

If you do not add this entry, the OpsCenter server stops receiving events fromthe master server after the upgrade.

■ An enhancement has been made in OpsCenter to maintain VBR parity.You can now search for clients from the Monitor > Hosts > Clients page. Youcan use host names or substrings to accomplish that.However, you can only search for clients andnot other attributes such as,CPUCount, CPU Speed, Discovered Agent Server, and others.

■ An issue occurs in the Job Count Workload Analyzer: For each cell, the sumof occurrences differs from the total in the first column when the time basisthat is selected is Active. That is expected because a job can be active and spanacross a multiple-hours time frame. Hence, the same job is counted for all thehours. But the count in the first column shows the exact count of jobs thatwere active for these seven days. That is different from the implementationof Time basis=Start or End. In these cases, the sum of the occurrences in thecell match with the number displayed in first column.

■ The Master server job throughput report appears without a report output inMy dashboard after a user upgrades from NOM to OpsCenter. The reason isthat it is an SQL query-based report and is a part of composite report that isnot migrated in the dashboard.

■ Daylight savings time (DST) support for Historical reports in OpsCenter


If data for the historical reports is synchronized during the hourwhendaylightsavings time begins, it can cause problems in a distributed database system.The user can also lose data.A workaround is to use Universal Time (UTC) as the time zone, or use a timezone that does not have daylight savings time.To set the time zone, refer to the Symantec OpsCenter Administrator's Guide.

■ When you upgrade from OpsCenter 7.0.x to OpsCenter 7.x, the InstallationChoice screen displays the available space on the system drive. This issueoccurs even if your previous installation is on a different drive (a drive otherthan the system drive).


34

End-of-life notifications


■ About NetBackup end-of-life notifications

About NetBackup end-of-life notificationsThis section lists the end-of-life notifications for the features, platforms, anddevices that are no longer compatible with NetBackup beginning with the nextmajor release.

■ Oracle Corporation has announced the end-of-life for Java 6 in July 2012.As a result, NetBackup does not support Java 6 in the next major release.

■ In addition, the following clients are no longer supported beginning with thenext major release of NetBackup:

■ Red Hat Linux Itanium

■ SLES Linux Itanium

For additional information on end-of-life notifications, refer to the NetBackup7.5 Release Notes for UNIX, Windows, and Linux on the Symantec Support Website.


Another resource that you canuse to view end-of-life information is the SymantecOperations Readiness Tools (SORT). That is a Web-based tool that supportsSymantec enterprise products. Part of this support is to provide users with "Endof Life (EOL)" and "Endof Support Life (EOSL)" information forNetBackup licensedsoftware. To view this information, Go to the SORT > Support > Related Linkspage on the SORT for NetBackup Users Web site.

See, https://sort.symantec.com/eosl.

5Chapter


https://sort.symantec.com/eosl


https://sort.symantec.com/eosl

End-of-life notificationsAbout NetBackup end-of-life notifications

36

About the current releasecontent index

This appendix includes the following topics:

■ About the NetBackup 7.5.0.3 master Etrack index list

About theNetBackup 7.5.0.3master Etrack index listThe following topics show the Etrack numbers that are fixed and contained ineach of the following NetBackup packages for this release.

130215819456022052733223466323253452353644237571023789352420422243941524959732510848251460025273582535411256915725701492570223257445825744622574464257446525744682574578259261825974582608743261287226199562630595263284826329442633176263500426374162643340264375326461662646225264688726521812655134265596226559702656466265778526585052659032265931426603242661571266178526617972662834266298226630772664228266443226652242665385266542326655262667172266993626704102671407267153726716452671671267192226719502673932267506926753022675305267532526757042675969267755026778922678208267863226786782679830267995226821692688166268857026886832689365269008226908152691019269293026930682693273269332026936302694825269531626967602696880269710326972142698378269844527000432700394270091827009202701894270194527025282702530270254927031432703605270567127101782710443271192427133542713358271396927144252714454271487127159032718018271866927205822721954272218827222402722358272330927247432724840272536827263552726529272666227274042727873272928027292932729299272945727300612730154273039127305452730891273127127312742731280273128227312862731289273135927314112731428273143227314342731435273143627314372731439273144127314442731445

AAppendix

2731446273144727314502731452273145327314552731458273146027314612731462273146427314662731467273146827314692731471273147427314752731481273148227314842731485273148627314872731488273148927314902731492273149427314952731497273149927315002731501273150227315032731504273150727315082731509273151127315122731513273151627315172731518273151927315202731522273152327315242731525273152827315312731532273153427315352731536273153827315422731544273155127315542731559273156127315622731564273156627315672731568273159427316162731621273162327316252731629273163127316322731637273163927316402731647273164927316542731657273166227316652731667273167127316732731674273167727316802731684273168827316932731697273169827316992731700273170127317022731806273214527327032733313273358127339822734009273415127342742734280273483527348412735017273526527353632735554273625427364792736522273653427366752737514273777827377852737909273791127379262738018273812327381612738220273889927391722739391273952727395702739614274056127408302740874274128627415922742045274210727421282742152274219427422672742269274232827427652742775274315927431842743223274359427439332744629274464527446472744898274490027451852745623274686627469312747203274832727483422748615274886327488712749550274978127498052750140275015727516342751738275290927529232753324275338527541552754245275484027548482755318275655127567632756988275719527581512758292275984127610662761115276114927611542761217276122527613262761569276173527620662762544276333227640922764508276452227656802766299276756827675712767592276759727693132769917277000327705802770903277099527711652771258277134527724642772883277310327731762773605277371727740392775222277529827754152775534277613127763132776672277679227772422777502277800827781142778693277918427792102779219277974427806842780839278106227814742781491278195727820232782125278243427831992783633278368227840102784508278454327846252784663278508427852322785516278706127877582787769278838027884742788938278953827899072790082279022127910602791069279112027911492791390279391527939672794282279501827956142797146279750728029352803622280362928050702805893 2807747 2808551 2808751 2811099

About the current release content indexAbout the NetBackup 7.5.0.3 master Etrack index list

38

About the current releasecontent

This appendix includes the following topics:

■ About release content conventions

■ About NetBackup 7.5.0.3 release content

■ NetBackup 7.5.0.3 Emergency Engineering Binary (EEB) listing

About release content conventionsThe following list describes the conventions used in the subsections that followthis section. Each item listed in the "Current release content" subsection describesa feature, enhancement, or fixed issue contained in this release:

■ DescriptionDescribes a particular problem that has been fixed in this release.

■ ** Description **Describes a problem that can lead to a potential data loss. Please read theproblem descriptions carefully.

■ WorkaroundAny available workarounds to a problem are also listed. Workarounds can beused instead of applying the patch, however, Symantec recommends the "bestpractice" of being at the latest available patch level.

■ Additional NotesAny additional information regarding a problem is included.

BAppendix

About NetBackup 7.5.0.3 release contentThis topic contains a list of known issues that were fixed and included in thisrelease of NetBackup.

Etrack Incident: 2535411

■ Description:The Client Name column is not sorted when a Custom Report is created.


■ Description:Drive Utilization reports show invalid values for jobs with a large number offragments that run for a long time.


■ Description:A browse for certain catalog files fails with a status code 23, which causes thebpdbm process to fail.


■ Description:When a restore is performed on an alternate client, the Restore Audit recordshows the actual client. The issue has been resolved so that the record displaysthe correct client.


■ Description:A policy that is configured with a large number of email addresses can causea policy data collection failure. The issue occurs of the email addresses equateto over 255 characters.


■ Description:The File Count Variance report does not accurately calculate the averagenumber of files that are backed up when the backups are multistreamed.


■ Description:An issue has been fixed where the media required for restore alert wasnot raised.


■ Description:

About the current release contentAbout NetBackup 7.5.0.3 release content

40

When accelerator is enabled on a policy and a Windows client has the changejournal enabled, a changed filemaynot benefit fromaccelerator optimization.The issue occurswhen files are deleted and then recreatedwith the samename.The result is that backups take longer because more data is backed up thannecessary.


■ Description:When XML data are imported, the imports fail and such errors appear as:multiple objects found and fail with object with alias does not

exist. The errors appear even if the object exists in the database.


■ Description:An issue exists where it may take numerous catalog cleanup jobs to removethe unreferenced images that are present for placeholder purposes only.Placeholder images contain the references thatprevent the removal of aStorageservice definition. The issue persists even if it appears that all images areremoved that reference it.


■ Description:A change has been made to address an issue that caused the data collectionfor EMC NetWorker jobs to fail.


■ Description:When accelerator-based backups are performed, backups may fail when thenew backup copies data froma previous backup to synthesize the new backup.This problem may occur because a file that had previously contained data istruncated to 0 bytes. Then the fingerprint that is associatedwith the truncatedfile is incorrect. When the server attempts to verify the copied data, it usesthe incorrect fingerprint, which causes the backup to fail.


■ Description:A space in the client name causes the spad process to fail.


■ Description:The bpexpdate -recalculate command can cause the bpdbm process to coredump in some cases. The command fails with the following error message:premature eof encountered.

41About the current release contentAbout NetBackup 7.5.0.3 release content


■ Description:The LIST_FS_IMAGE_HEADERSvalue is not visible by all nodes of a clusterand may not be visible to the Enterprise Media Manager server. It has beenmigrated to thenbdb process from the bp.conf/registry. The old value is nolonger used beyond the migration step.


■ Description:An OpsCenter upgrade from version 7.0 and after fails because a primary keyconstraint is violated. The failure occurs when duplicateFTM configurationsare at the sameview level. Aprocedurehas been added to remove theduplicatesbefore this violation occurs.


■ Description:This fix enables users to view Cloud data collection status throughOpsCenter.The user can see a new entry, Cloud under the Data Collection Status tabwithin Settings.


■ Description:Explicit chmod and chgrp commands have been added to the move_libs scriptto correct a permissions error when files are copied.


■ Description:When a backup fails, the activity monitor shows that the job continues to runafter it is retried, which is false. The try file logmessages have been suppressedso that the bpjobd process does not show these false details in the activitymonitor.


■ Description:The bpbrm process has been altered to log a general message to the try file.The change is necessary so that the process does not use theBEGIN OPERATION

message, which the JobManager uses. Now the try file does not have duplicateBEGIN OPERATIONmessages for the create,mount, and delete steps of snapshotduplication.


■ Description:


42

Changes have been made to support block-level accelerator backups in ClientDirect.


■ Description:When the user reports on a largemaster server, the socket connection betweenthe nbsl process and OpsCenter may fail. This issue can result in data loss.


■ Description:A restore of a system state backup with ASR data results in a status code 1even though all data is restored.


■ Description:The following fixes from NetBackup 7.1.0.4 were not in 7.5 and have beenadded for this release:

■ Asynthetics fix has been added to validate that the file offsets in the catalogcorrespond to the same data on the disk. The backup fails if the data iswrong.

■ A bpstsinfo -comparedbandstu command enhancement has been addedto do the sameoffset validation and image size check that synthetics shoulddo.

■ A bpverify enhancement has been added to validate an image with thesame synthetics offset validation.


■ Description:Disk group and pool capacities are reported incorrectly. The nbdevconfigprocess reports a negative number for the raw size of the disk pool. The errorcan cause jobs to fail with insufficient disk space.


■ Description:Incremental backups of EV_INDEX_LOCATION are partially successful with astatus code1:WIN32 87: The parameter is incorrect. Full backups completewith a status code 0. A case-sensitive comparison of Enterprise Vault indexfile paths causes the problem.A fix has been added that compares path stringswithout case sensitivity.


■ Description:


An import on a target server fails if the target server version is before 7.5. Theissue occurs when Automatic Image Replication is used to replicate CatalogBackup images from one domain to another. The solution requires a patch ontop of 7.1 before the import is successful.


■ Description:If one Exchange database is on amount point or an independent disk, VMwaresnapshot jobs do not become momentarily inactive. This issue occurs when aVMware backup is aware of the Exchange application. The issue results in afailure to browse or restore Exchange mailbox items.


■ Description:The tar code has been fixed so that hard links and soft links are not renamedin case of a single file restore.


■ Description:The nbsl process sometimes core dumps when it is shut down.


■ Description:The bpexpdate -deassignempty command can take a long time to complete.The command also puts a large load on the master server for catalogs with alarge number of images.


■ Description:Snapshot replication jobs fail with a status code 84when the bpdm log indicatesthat the storage server failure code is 2060046. The failure occurs when thedestination of a storage lifecycle policy replication operation is a storage unitgroup that contains units frommultiple storage servers. The other criteria forthis failure is a backup policy with some selections that span volumes andexist on multiple storage servers. An ordering sort problem has been fixed.


■ Description:Queries that are issued to the database can be optimized if they are queriedacross a set of clients when the result set is small.


■ Description:


44

When OpsCenter is upgraded to Windows 2008 R2 x64, Simple NetworkManagement Protocol traps are not sent. This issue is observed only on a fewsystems.


■ Description:If Application Protection and the Enable indexing options are selected forthe VMware policy type, the Policy Execution Manager fails when the backuprequest submits. Indexing is not supported for applicationprotection. Interfacechangeshavebeenmade tonot allowa combinationof indexing andapplicationprotection.


■ Description:The bperror process reports the client name as the media server instead ofthe appropriate virtual machine. This error occurs when an error occurs in aVMware policy with a VMware Intelligent Policy query for client selection.The nbpem process shows the backup host name as the client name for thefailed backup job for VMware Intelligent Policies. From the nbpem logs, theobjectRecoverableJob logs the clientnameas themedia servername.However,when the job is submitted, the Policy Execution Manager passes the correctclient name to the nbjm process.


■ Description:VMwarebackupsof applicationshavebeenallowed functionalitywithGranularResource Technology. This change is so the backups can work when there aremultiple vmdk files with the same name in the backup set.


■ Description:An image migration comes across an image with a corrupt or missing backupID field and marks the image as skipped. The image has been moved into thedb.corrupt folder.


■ Description:Some jobs that should be run as DirectCopy jobs within a Network DataManagement Protocol filer instead move data through the media server.


■ Description:


If a schedule type is not specified, the bpimage -lastbackup command failswith an exit status 223: An invalid entry was encountered.


■ Description:Once themaster database is restored, the SQL server restarts the SQL instanceservices. This issue causes a problem because the SQL Agent still queries theSQL server. A fix has been made so the SQL server is not queried once themaster database restore is complete.


■ Description:An SQL query for configuration fails because it is case-sensitive. A change hasbeen made so the query is not case-sensitive.


■ Description:Veritas Unified Logging forWindows x86 uses a 32-bit system, but NetBackupuses a 64-bit system. As a result, Veritas Unified Logging structures aremisaligned for some variables when NetBackup accesses them.


■ Description:Files cannotbe restored fromanon-networkdatamanagementprotocol (NDMP)image that is duplicated to an NDMP storage unit through the NDMPDirectCopy . To work around this issue, use the touch fileNMDP_MOVER_CLIENT_DISABLE.

■ UNIX Installed file: /usr/openv/netbackup/bin/bptm

■ Windows Installed file: VERITAS\NetBackup\Bin\bptm.exe


■ Description:VMware snapshots are sometimes not cleaned correctly. A disk lease releasehappens after the snapshot removal call, which causes orphaned snapshots.


■ Description:When the Loopback File System is present on a client, NetBackup now treatsit as a local file system. When the Loopback File System is not present on aclient, NetBackup now treats it as a Network File System. This fix isimplemented on the client as a touch file: TREAT_LOFS_LOCAL.



46

■ Description:An issue occurs when an SQL server 32-bit instance is installed on a 64-bitcomputer and SQLINSTANCE $ALL is specified in an SQL batch file. TheMSSQLagent skips the 32-bit default instance for backup.


■ Description:During a restore, if there are a lot of orphaned or leftover snapshots, the virtualmachineXML file becomes too large and causes buffer failures. This fix adjuststhe buffer sizes to a higher limit to allow for restores.


■ Description:If the NetBackup master, media, and client servers are in different gateways,restores fail because of a communication failure.


■ Description:On an HP system, if the system host name is longer than eight characters,shared resource tree creation fails.


■ Description:Media shared resource tree creation fails on anHP system if the volume groupis larger than 64 megabytes.


■ Description:When certain Linux client configurations are imported into the Bare MetalRestore database, the bmrd process enters an infinite loop. The issue occurswhen the bmrd process evaluates disk configurations, and some disks cannotbe processed.


■ Description:The Bare Metal Restore FirstBoot script fails if it cannot communicate withthe master server to update the task status and stay active for a restart.


■ Description:On anAIX system, aNetBackup restore forOracle fails after the data is restoredbecause no server status is given.



■ Description:This fix enables the use of the touch fileUSE_BACKUP_MEDIA_SERVER_FOR_RESTORE for restore jobs. The fix lets youselect the media server that was used to perform a backup operation.


■ Description:Oracle tables with many columns cause export jobs through bporaexp andbpdbsbora to fail with a status code 41.


■ Description:Oracle table exports that run for a long time cause the bpdbsbora andbporaexp64 processes to deadlock with a status code 41.


■ Description:XMLexports ofOracle tables fail with the following errormessage: ORA-00936:missing expression. The issue occurs if the reserved words in Oracle areused as column names in a table.


■ Description:Veritas Unified Logging for x86 has been changed to removeUSER_32BIT_TIME_T because NetBackup uses 64-bit time. This change fixesstructure misalignments when NetBackup references some elements in theVeritas Unified Logging structures.


■ Description:On a Red Hat 6 Update 1 system, Fibre Transport media server configurationfails when the /etc/init.d/nbftserver start command is executed. Thescripts in this fix can be installed to resolve the issue. Install the scripts andretry the Fibre Transport media server configuration.


■ Description:Apache Tomcat 6.0.35 has been provided for OpsCenter 7.1.0.3.


■ Description:When there are more than 200 Backup Exec servers, the Agent can only viewthe first 200. The limit has been increased to 1000.


48


■ Description:The column headers are covered up when EXPORT_MESSAGE_TEXT headers areused on the exported reports.


■ Description:The View Export command freezes when large views are exported.


■ Description:A ViewException occurs because a node of type GENERIC cannot be created ina tree of type MASTER_SERVER.


■ Description:In JavaViewBuilder, theUnassigned tab and theAllObjects tab are not sortedalphabetically as they are in Veritas Backup Reporter.


■ Description:In Backup Exec, OpsCenter does not process the Half-inch Cartridge mediatype.


■ Description:A large number of records in domain_JobArchive, Domain_TapeLibrary, andother domains may cause Job Data Collection to enter a queued state.


■ Description:When the Virtual Client Summary report is run, the same virtual client islistedmultiple times. For someor all of these replications, the client is reportedto not exist in a policy even though they are configured into the policy.


■ Description:An issue exists when the user creates queries for a FlashBackup WindowsVMware policy and the values contain keywords such as AND, OR, or NOT.The Query Builder can corrupt these entries in the interface because ittranslates these keywords as new operands.



■ Description:A fix has been made to the nbstserv code to check for a termination requestbefore images are updated. This fix avoids an issuewhere the nbstservprocesscore dumps when NetBackup services are stopped.


■ Description:In the JobMonitor, the Total Kbytes transferred field can becomenegativeand the kilobytes/sec field can be very large during some restore jobs.


■ Description:Some images can fail to duplicate in the duplication jobs that useOpenStorageDirectCopy to a tape of non-network data management protocol images. Thisissue occurs when the buffer size that is used for the primary copy is greaterthan the value of NDMP_FILE_MAX_READ_LENGTH. The default value is 64kilobytes.


■ Description:Tape drives take a long time to unload. The unload process fails if a drive istoo slow.


■ Description:When the nbemmcmd -changesetting command is used to add a parameter ona cluster name, the following error appears: invalid host name (136).


■ Description:After anupgrade toNetBackup7.1.0.3, a number of bpdbmprocesses use ahighamount of CPU.


■ Description:During a stream discovery, the Job Manager removes all deleted schedulesbefore the current streams file is updated with new discovery data.


■ Description:During snapshot creation, a snapshot-baseddatabase agentpolicy type scenariofails with a status code 156 in the bpfis process. The issue occurs when there


50

are a large number of physical devices or when the SNAPSHOT_METHOD_ARGSstring is larger than 3 kilobytes.


■ Description:VirtualmachineswithmultipleWindows installations donotmap all volumes.During a mapped FullVM backup, only the C drive is mapped.


■ Description:On a Linux virtual machine, the file system is not mapped even though thebackup job completes with a status code 0.


■ Description:OnUNIXplatforms, a process can fail if there is low free space in the file systemthat contains temporary files for odbc driver communication.


■ Description:During backups on a Windows client when Use change journal has beenenabled, the following issues may occur:

■ The bpbkar32.exe executable may fail.

■ The bpbkar32.exe executable may appear to freeze.

■ The bpinetd.exe executable may fail.

These issues have been attributed to inconsistencies within the NetBackupchange journal databases.


■ Description:The bpplinfo process fails because a NULL check is not in the index server.


■ Description:This fix resolves an issuewhere the deduplication engine spoold does not startproperly in a LocalSystem account.


■ Description:A restore is not in the first batch of fingerprints that is retrieved, so the restorefails when the fingerprint is not found.



■ Description:The destination container is not properly chosen during compaction, whichcaused the container to not be given back to the system.


■ Description:When a NetBackup Access Control permission is set through the bpnbazinterface, granular permissions may not be set correctly.


■ Description:The bpdbm process can core dump when it changes the primary copy if thebackup ID that is passed to the query is incorrectly formatted.


■ Description:A restore to an alternate path is successful, but the file is restored to its originallocation.


■ Description:OnMac OS X platforms, the version of nbsl that was released with NetBackup7.5 fails with a runtime error.


■ Description:An issue in disk staging storage units has been fixed for back-level mediaservers.


■ Description:Incomplete storage lifecyclepolicy images cannotbedeletedwith thenbcatsync-prune_catalog command.


■ Description:An issue has been fixed where the Universally Unique ID caused a memoryleak and a file descriptor leak when it was called.


■ Description:


52

An issue has been fixed where the root and the administrator are not addedby default as Security Administrators in the Authorization Security group.


■ Description:PAMauthentication does not do a case-insensitive comparison of the passwordprompt string.


■ Description:The bprd process enters an infinite loop when the bpcd process gives it acorrupted version string.


■ Description:OnWindows2008R2, Sybase SQLAnywhere software fails to identify availablephysical processors if they are grouped. This issue causes a smaller numberof processors to be used than available. Sybase SQL Anywhere now supportsthe Solaris 11 platform (SPARC and x64) with this release of NetBackup. Thisrelease also supports Solaris 11 as a master server platform.


■ Description:In the bpjobd process, the JOBDBSUSPEND command acts immediately when itis executed as part of catalog recovery. This issue sometimes causes pendingupdates to the job to be lost. The fix makes sure that the JOBDBSUSPENDcommand waits for the provider queue to be empty before it suspends thedatabase. The fix also forces the caller to wait until the completion of thesuspend or resume command.


■ Description:When an index server list is provided to nbholdrestorehelper, and it containsshared folders from more than one index server, the process fails. The failurehappens because the process uses the incorrect path staging folder for thesecond index server. This issue occurs when a user has more than one indexserver.


■ Description:For volumes with a size of several terabytes, the RvpBitmap process failsbecause of a lack of address space in the x86 proxies.



■ Description:A performance improvement to granular restore technology has been madefor PureDisk storage.


■ Description:This submission does the following to fix orphaned snapshot issues for virtualmachines.

■ It attempts snapshot consolidation.

■ It provides a registry entry so the bpfis process waits according to theregistry setting before it removesVMware snapshots. Thewait helpswhendisk lease release takes a long time.

■ It provides wait facility in the bpfis -delete process when it is calledthough the bpkar process is still in progress. Registry entry controls thewait and helps control orphaned snapshots.


■ Description:In NetBackup 7.5, a fix has been made to an invalid parameter that causesbandwidth throttling to fail.


■ Description:A temporary mount of the Zeta file system root pool fails if the value forcanmount is set to NO while other pools have it set to YES.


■ Description:When a Mac OS X client is backed up with Checkpoint Restart enabled in thepolicy, the job may fail with a status code 130. The NetBackup logs indicatethat the bpbkar process is terminated by signal 10.


■ Description:The storage area network (SAN) client has been improved to minimize theneed to restart the nbftclnt service and daemon. The purpose is toaccommodateNetBackupandSANmaintenance.Anewcommand,nbftconfig-ra has been added to trigger a rescan of Fibre Transport target devices on allSAN clients. The nbftclnt service no longer has to be restarted.



54

■ Description:Granular restore technology paths with Newline characters or FFFF may notbe written properly to the catalog.


■ Description:Sometimes Data Collection may not start after a failure, though the agentreconnection time is set to 10 minutes.


■ Description:For a Microsoft Exchange backup, ncflbc log files grow rapidly and create alow disk space condition on the client. This issue occurs even when log levelsare at 0 or 1.


■ Description:For Master Servers that run a NetBackup version before 7.5, the storagelifecycle policy (SLP) status report displays an incorrect status. The reportshows that an SLP job is in progress even though it is complete. The SLP jobstate for a copy is not updated for duplication to a tape. The event runs oncea day and updates the state of the copy based on the state of the SLP job.


■ Description:This fix ensures that ASC jobs complete successfully for the first SharePointbackend server that is on the SQL server for multiple SharePoint farms.


■ Description:After an upgrade to NetBackup 7.5, OpenVMS backups fail for the bpcd andbpbrm processes with a status code 229 and the following error message:

status: 229: events out of sequence - image inconsistency


■ Description:After an upgrade to NetBackup 7.1.0.4, snapshot completions take more than10 minutes.


■ Description:


A single backup job cannot back up more than one CAB file at a time. This fixallows multiple CAB files to be backed up at once, and improves the speed ofNBU_EV_Migrator by 22 times.


■ Description:An Exchange granular browse for the backup IDs that belong to one backupmay fail. Exchange granular restores from multiple databases may also fail.


■ Description:A typing error has been corrected on the Java ViewBuilder interface.


■ Description:During block level incremental backups on VMware, the bpbkar process failsintermittently with a status code 13.


■ Description:When runtime data collection is enabled, the time of day for the collection canchange to a later time as collections continue. This fix keeps the collectiontime within 15 minutes of its originally set time.When runtime data collection is disabled, old collection data is never deletedafter a collection has occurred. This fix ensures that old data is deleted aftertwo weeks.


■ Description:When a process runs that contains the string inetd, it may be incorrectlyterminated. The grep -Ew command has been added to the client_configscript to exclude those processes and avoid their termination. ps checks thatlook for inetd and xinetd have been updated to use the grep -Ew commandfor all platforms but Solaris. An exclusion of sesinetd has been explicitlyadded for that platform.


■ Description:Duplication jobs can freeze because of an invalid protocol message from asub-process of bpdm or bptm.


■ Description:


56

An Exchange 2010 Database Availability Group snapshot backup fails whenan Exchange policy is configured with some individual databases that areseparated with NEW_STREAM directives.


■ Description:A Dynamic Host Configuration Protocol client may not browse and initiaterestores of the client. Restores have to be initialized from the server.


■ Description:Thenbrbprocess doesnothonor the settings that theuser configures. It insteaduses the default settings if the settings are present in the database.


■ Description:When the user has network data management protocol backups on a mediamanager tape storage unit, restores from those backups fail.


■ Description:ASecure Sockets Layer security issue is fixedwith theRackspaceCloudplug-in,where the data that is sent to the Cloud can be compromised. Metering datais not collected in OpsCenter if the start timestamp is from the previous yearand the end timestamp is the current year. The nbcssc Cloud service has beenfixed to search for the year that the metering data was collected.


■ Description:If extra files are present under a schedule directory, any schedule updatescause all other schedules to be deleted. The disk staging storage unit relocationschedule is also deleted.Duplication jobs are not scheduled and the disk stagingstorage unit is filled to capacity. A fix has been added to check the files underthe schedule directory.


■ Description:After an upgrade from 7.1.0.3 to 7.5, the ClientRiskAnalysis report does notdisplay clients at risk if the primary job is a snapshot. The report displays rowsfor clients with old backup times, even though new backups have beencompleted within the specified date range.



■ Description:For a backup, the transport type appears in theDetailedStatus of theActivityMonitor. For a restore, the transport type appears in the progress log.


■ Description:The NetBackup-Java Administration Console fails to validate the credentialsof the virtual machine hosts.


■ Description:When a view is exported with Java ViewBuilder, the export takes a long time.A client merge causes clients to be deleted from views.


■ Description:A timestamp directory in the database image directory may not be cleaned upif placeholder images still reference it.


■ Description:In a VMware backup, Exchange or SharePoint granular restore technologyactivities may fail. The issue occurs if there are 10 or more volumes from thebacked up virtual machine.


■ Description:A new lookup entry has been added to show the appropriate message that isreceived from NetBackup on the OpsCenter interface.


■ Description:The bprd process enters an infinite loop when it receives a corrupt versionstring from the bpcd process.


■ Description:If the connection fails when the SQL Agent connects to the SQL server, theAgent tries to write the error in thedbaclient logs. A NULL pointer exceptionresults.


■ Description:


58

When files are backed up that are larger than 2032 megabytes but smallerthan2047megabytes, aNetBackupAccelerator jobmay failwith thismessage:cannot write image to disk, Invalid argument.


■ Description:When the criteria for list filesmay include a backup ID and a client namewherethe case does not match, the application can fail.


■ Description:VMware Intelligent Policy backups can cause the Policy Execution Managerto core dump.


■ Description:The nbpem process does not supply the policy client name in the argument-dag that is passed to the bpbrm command line.


■ Description:A reference count has been added to keep an object resident until after theaction matrix is deleted. This fix prevents a failure from when the job historyis dumped into the logs.


■ Description:The tar.exe executable fails if an invalid transport mode is selected for avirtual machine restore.


■ Description:Not all One Click variance reports are displayed.


■ Description:The bpbkar DATA_STOCKprocess is bounced off themedia server firewall whenthe bpstart_notify process runs long enough for the firewall to time out.This issue causes backups to fail for large file systems.


■ Description:


If a catarc image is alreadymigrated to theNetBackup database and an imagein the db/images directory still references the catarc image, the imagerelationship is lost. The issue also occurs when two images in separate clientdirectories reference the same catarc image.


■ Description:When the bpexpdate -recalculate command is invoked without the -d and-ret options, images may be updated with an incorrect expiration date.


■ Description:A check has been added for the size of anXMLdiscovery file that is larger than256 kilobytes. This check prevents file truncation and backup job failure.


■ Description:The user cannot use the Backup, Archive, and Restore interface to browse abackup image and select files for restore. This issue occurs under the followingconditions:

■ Use Accelerator is enabled on a policy.

■ Use Change Journal is enabled for a Windows client.

■ A file is added to Backup Selections.

■ After the new file is added, the next backup that is run is an incrementalbackup.


■ Description:During the OpsCenter patch upgrade process to 7.5.0.x, the symcsearchd.dbfile is not backed up.


■ Description:Snapshot copies that become invalid after a Point In Time rollback need to beremoved from the NetBackup catalog. This change fixes a problem whereinvalid snapshot copies are left in theNetBackup catalog after a rollback. Theirpresence gives the false impression that they can be used for future restores.


■ Description:


60

An issue exists where an incorrect last backup time can be calculated. Theissue occurs if the latest image expires when there is a parent-child jobhierarchy and the child image has a stream number of 0.


■ Description:A VMware Intelligent Policy backup runs a full backup when it should run anincremental backup.


■ Description:During multistream jobs, incorrect data is displayed for backup durationvariance.


■ Description:Aproblemhas been correctedwhere toomuchdata is backedup in incrementalVMware Intelligent Policy backups.


■ Description:Aproblemhas been correctedwhere toomuchdata is backedup in incrementalVMware Intelligent Policy backups.


■ Description:WhenUseAccelerator is enabled on the backuppolicy, backupsmay completesuccessfully. However the backupsmay only back up a couple of items insteadof everything in the specified backup selection. This problem is only seen inbackups on a Windows NetBackup client.


■ Description:The bpcatlist command can incorrectly list compressed images as offline.

NetBackup 7.5.0.3 Emergency Engineering Binary(EEB) listing

The following table contains the known issues that were identified, fixed, andavailable to our customers in the formof anEmergencyEngineeringBinary (EEB).NetBackup 7.5.0.3 resolves the addressed issues in each of these EEBs. AdditionalEEBs may have been released since this document was posted. If you do not see

61About the current release contentNetBackup 7.5.0.3 Emergency Engineering Binary (EEB) listing

an EEB that you expected to see in this document, contact your SymantecNetBackup Support representative. You can also use SORT for NetBackup to findfor which releases an issue has been resolved. See the following link:


If you require additional information about an issue in this table, contact yourSymantec NetBackup Support representative.

Table B-1 NetBackup 7.5.0.3 EEB Listing

EEB DescriptionEtrack Number

The Media Required for Restore alert is not generated.2655015

An alert is not generated when a restore job is in the waiting state because of unavailablemedia.

2650649

OpsCenter does not generate Media Required For Restore alerts.2600512

Some OpsCenter reports require the media ID field to be populated in the job database forall child jobs of multiplexed backups and duplications. Otherwise, the reports cannotdetermine the type of storage unit in use.

2622505


2416944

OpsCenter does not generate Media Required For Restore alerts.2650641


2381571

The Tape Mount Request alert is not generated for restore jobs.2441838

An issue occurs on a clustered master server when nbemmcmd -changesetting is runfor a setting that does not exist. If a cluster name is passed, it shows an invalid host nameand the setting is not added. The command works if an active node name passes.

2660635

The bpbkar socket gets closed by the media server firewall when the bpstart_notifyprocess runs for too long.

2715544

During the creation of the preview list, unnecessary string conversions can cause largedelays in NetBackup Vault jobs.

2591566

The default instance is skipped from a backup. The issue occurs when a 32-bit MSSQLdefault instance is installed on a 64-bit server and an MSSQL batch file specifiesSQLINSTANCE $ALL.

2648559

About the current release contentNetBackup 7.5.0.3 Emergency Engineering Binary (EEB) listing

62


Table B-1 NetBackup 7.5.0.3 EEB Listing (continued)


This fix enables the use of the touch file, USE_BACKUP_MEDIA_SERVER_FOR_RESTOREfor restore jobs. That allows themedia server thatwas used to perform the backup operationto be selected.

2665486

This fix enables the use of the touch file, USE_BACKUP_MEDIA_SERVER_FOR_RESTOREfor restore jobs. That allows themedia server thatwas used to perform the backup operationto be selected.

2583566

The lbc process or the bpcd process may cause an exception during a granular restorefrom duplicated backup images. This issue occurs because of some special characters thatthe NetBackup client does not handle correctly when it sends to the catalog.

2734894

The bpdbm process can cause the duplications that run for a long time to timeout fromapparent inactivity.

2636625

After an upgrade to 7.1.0.4, snapshot completions are slower.2744563

After an upgrade to 7.1.0.4, snapshot completions are slower.2782219

The Advanced Success Rate report does not include multiple stream backups.2557732

Job Data Collection goes into a queued state.2703802

On Windows platforms, there is a performance issue when backups are run with a numberof bpdbm processes with NetBackup Access Control set to ON.

2760478

After an upgrade to NetBackup 7.1.0.3, there is high CPU utilization by a number of bpdbmprocesses.

2683975

Thebprd.exe file does not deleteVeritasUnified Log files in aWindowsx86 environment.2745114





The nbsl process fails during a shutdown.2794722







On an HP-UX 11.31 system, Bare Metal Restore shared resource tree creation fails if thesystem host name is longer than eight characters.

2649340

The virtual clients that reference more than one master server appear in the Unassignedview in ViewBuilder.

2428117

The virtual clients that reference more than one master server appear in the Unassignedview in ViewBuilder.

2588648

The virtual clients that reference more than one master server show up in the Unassignedview in ViewBuilder.

2660255

The virtual clients that reference more than one master server appear in the Unassignedview of ViewBuilder.

2382403

If the Windows Remote Administration Console is not connected to the first server on thelist, it gives the following error message: (46) server not allowed access.

2704580

If the Windows Remote Administration Console does not connect to the first server on thelist, it gives the following error message: (46) server not allowed access.

2762728

The time that is taken to shut down NetBackup services is high if the network goes down.2358033



NetBackup services take a long time to shut down when the IP address goes down. Thisissue causes long delays in cluster failover.

2534647


The NetBackup service group does not go offline after a network link goes down.2529191

When the IP address goes down and a cluster tries to shut down NetBackup services, ittakes a large amount of time. This issue causes a delay in failover.

2641589


NetBackup services do not shut down in a timely manner when an IP resource becomesunavailable.

2717447

NetBackup services do not shut down in a timely manner when the IP resource becomesunavailable.

2728069

For a VMware Intelligent Policy, the bperror process reports a client name as the mediaserver instead of the virtual machine that failed.

2660588


64



The bperror process reports a client as the media server in a VMware Intelligent Policythat uses a query for client name selection.

2715916

This fix resolves an issuewhere Content Router containers are not properly released to theOS when thresholds are reached.

2659374


2653530


2658486


2654222


2657085


2690734

Disk staging storage unit schedules are deleted and scheduled relocations do notautomatically run. The issue occurs if some extra files are present in the database or theschedule directory.

2660720

When two backups start on the same Windows client, both bandwidths are halved.2519076

Throttling is sometimes not followed when it is set.2645285

LIMIT_BANDWIDTH does not work as expected.2776687

LIMIT_BANDWIDTH does not work as expected for Windows clients.2699258

LIMIT_BANDWIDTH does not work as expected for Windows clients.2744407

The bandwidth throttle freezes when a second backup starts on the same Windows client.2565104

In OpsCenter 7.1, a Custom Tabular report does not sort the Client Name column.2331633

For Solaris, a Veritas VolumeManager disk group fails tomap because of a lack of availablespace.

2748607

An unmap_all command fails on the configurations that have Solaris zones on VeritasVolume Manager. Also, disk groups fail to map because of a lack of available space.

2657515

On Solaris, a Veritas VolumeManager disk group fails tomap because of a lack of availablespace.

2680699




When the close_server command is not called for a multiplexed backup to a PureDiskDeduplication Option storage unit, severe resource leaks result.

2637606

If multistream and multiplexing backups are configured to a deduplication storage unit, adisk pool down situation results because too many connections are open.

2567947

Backups can cause the bpbkar32.exe executable to core dump in the MSVCR80.dllmodule.

2586848

Root users on UNIX and the users that belong to local administrator groups on Windowscan modify NetBackup Security settings. They can modify the settings even when they arenot in the NBU_Security Admin group.

2751543

This Windows-only EEB enables customers to restore Storage Foundation Clients with aBare Metal Restore FastBoot shared resource tree. It is an alternative to the Legacy sharedresource tree for Storage Foundation Client restores.

2557307

Simple Network Management Protocol traps are no longer sent after a server upgrade toWindows 2008 R2 x64.

2705855

Simple Network Management Protocol traps are no longer sent after a server upgrade toWindows 2008 R2 x64.

2727495

Simple Network Management Protocol alerts are logged, but they are not seen on systemswith external tools.

2677632

An Oracle export fails with a status code 41 if there are too many columns in the table.2663639

Columnheaders are coveredupwhenEXPORT_MESSAGE_TEXTheaders areusedonexportedreports.

2595168

TheFibreTransportmedia server configuration scriptsnbftsrv_configandnbftserverhave beenmodified to fix kernel identification issues forRHEL5.xOSversionswith patches.

2708292

You cannot restore files from the virtualmachine backup images that are duplicated to theNDMP drive (Physical tape library ) through an NDMP DirectCopy.

2661041

On an HP system, media shared resource tree creation fails if the volume group size isgreater than 64 megabytes.

2662754

Thebpbrmprogrammay freeze ifBPCD_GET_NB_VERSION_RQSTdoesnot complete.Otherjobs freeze and cannot be canceled.

2185079

High CPU utilization occurs if the bpgetconfig -s client name -l A command iscalled for a 6.5 client. The command waits for a response from the bprd process, which istrapped in an infinite loop because of corrupt data from the bpcd process.

2682953


66



High CPU utilization occurs because multiple nbproxies wait for a response from thebprd process. The process gets stuck while it parses the version file contents of a clienthost.

2742386

The bpduplicate process receives a malformed message that causes it to freeze. Thebpduplicate process properly handles the error message and stops the job. The issueoccurs because an OpenStorage plugin problem causes the bptm process to core dump.

2660807

The nbsl process does not send the image updates that are subsequent to initial datacollection for OpsCenter.

2686819

A restore on a Microsoft SQL clustered master database sporadically fails, although themaster database is restored and recovered successfully.

2717337

A restore on a Microsoft SQL clustered master database sporadically fails, although themaster database is restored and recovered successfully. The SQLAgent interface fails whenthe SQL server connection properties are set.

2687832

Restore Audit Records do not contain the alternate client restore information.2619988

Restore Audit Records should contain the alternate client restore information.2706969

A one-time script has been created to address when a disk storage unit is full. Thenbdevquery report shows negative numbers for the raw size when the High Water Markis exceeded and there is insufficient disk space.

2393120


2385825


2532199


2562242


2563662


2436324





2562179


2612736


2658267


2376845


2580249


2580250


2562537

After an upgrade to 7.5, Exchange granular activity logs more at a bpconfig debug levelof 0. The issue occurs even when the ncflbc folder does not exist.

2743111

InNetBackup7.1, thebpbkar32.exe executable faults on aMappedLinuxVirtualMachinebackup with the logical volume manager (LVM) configured.

2367085

The VeritasMapping Service returns an error 4109when Block Level incremental backupsare enabled. The issue occurs for incremental backups with the vStorage applicationprogramming interface (API) on a large vmdk file.

2115317

This EEBhas amodifiednbftsrv_config script for caseswhen the script creates duplicateentries in driver_aliases. The issue causes excessively long configuration times on aSolaris 10 SPARC Fibre Transport media server.

2778989

In the NetBackup console, the vStorage query builder corrupts queries when they consistof operands like OR and AND.

2355921


68



When the Loopback file system is on a client, NetBackup treats it as a local file system.When the system is not on a client, NetBackup treats it as a Network file system. The fixfor the client is a touch file openv/netbackup/TREAT_LOFS_LOCAL.

1603726

This fix treats the Loopback File System (LOFS) as a local drive for Solaris 10 Zone support.1077887

This fix treats the Loopback File System (LOFS) as a local drive for Solaris 10 Zone support.1155270

When the Loopback file system is on a client, NetBackup treats it as a local file system.When the system is not on a client, NetBackup treats it as a Network file system. The fixfor the client is a touch file openv/netbackup/TREAT_LOFS_LOCAL.

1204968

An issue occurs when ALL_LOCAL_DRIVES is used on Solaris 10 zones with a LoopbackFile System. The file systemmount is identified as a separate file systemmount and as partof the root file system. This conflicts with multiple entries for the same file.

2138872

The Zeta file system (ZFS) is not backed upwhen theALL_LOCAL_DRIVESdirective is used.1377572

Zeta file systems on a Solaris 10 client are not backed up when the ALL_LOCAL_DRIVESdirective is used in the policy configuration under NetBackup. The client is modified totreat it as a cross mount point backup.

1165573

If either UpdateBars or UpdateDatabase permissions are added to the Media Resource, anon-existent Up permission is also added.

2732347

The JavaViewBuilder doesnot sort the list of unassignedobjects likeVeritasBackupReporterdoes.

2726414

A Sybase engine fails to use all physical processors that are available on the computer.2672447

A Sybase engine fails to use all physical processors that are available on the computer.2780624

The console limit is 200 collectors per agent.2705693

The virtual client Summary report lists the same client multiple times, and with Existsin Policy equals No.

2672578

Virtual machine data collection creates an additional entry for clients, even if the clientalready exists in the database.

2769980

The Rename hard links and Rename soft links functions do not work during asingle file restore from a mapped FullVM backup.

2676500

The Drive Utilization shows lesser utilization for jobs with a large number of fragmentsthat run for a long time.

2489363

Performance issues occur when views are exported.2651159




Half-inch Cartridge media is not reported correctly for Backup Exec.2681770

An unnecessary statement has been removed that causes an error message in the log file2694003

An unnecessary statement has been removed that causes an error message in the log file.2685232

The nbcatsync process does not recognize compressed image catalog files.2682994

The script BMR-FirstBoot errors out to a command line. The issue occurs if it cannotcommunicate with the master server to update the task status and stays active for anyrestarts.

2704490

The script BMR-FirstBoot errors out to a command line. The issue occurs if it cannotcommunicate with the master server to update the task status and stays active for anyrestarts.

2729052

After an upgrade from 7.0 to 7.1, a browse for the SQL client fails with a status code 23 andcauses a bpdbm application fault. The following error message appears: unexpectedreturn value from db_FLISTreceive.

2601560

After an upgrade from 7.0 to 7.1, a browse for the SQL client fails with a status code 23 andcauses a bpdbm application fault. The following error message appears: unexpectedreturn value from db_FLISTreceive.

2583875

An XML export of an Oracle table fails if Oracle's reserved keywords are used as columnnames.

2715340

Snapshots are sometimesnot cleanedup correctly. Thebpfis -delete command is calledthough thebpbkarprocess still runs. Disk lease release happens after the snapshot removalcall.

2634978

This EEB fixes a NetBackup Catalog issue.2800797

For the bpcd process and the bpbrm process, backups fail with the following message:status: 229: events out of sequence - image inconsistency.

2724681

The Deduplication Engine (spad) process sometimes fails during backup and duplicationsjobs.

2639354

The Commit_CallAtPostInstallDll custom action fails during a NetBackup clientinstallation on Windows.

2685598

No data is restored from a network data management protocol backup. The bptm processexits with a status code 0.

2741249


70



No data is restored from a network data management protocol backup. The bptm processexits with a status code 0.

2749290

Nodata is restored fromaNetworkDataManagement Protocol (NDMP) backupwith remoteNDMP. The bptm process exits with a status code 0, but the job freezes.

2787723

An import of XML data fails.2665356

If a stream finishes more than 30 minutes before the parent job terminates, the policyexecution manager may fail.

2769435

The last file of OpenStorage DirectCopy duplications of non-network data managementprotocol images can be corrupt under certain tuned buffer size settings.

2776251

OpenStorage DirectCopy duplications of non-NDMP images can be corrupt under certaintuned buffer size settings.

2673580

The last file of anOpenStorageDirectCopy duplication of a non-NDMP image can be corruptunder certain tuned buffer size settings.

2776250

OpenStorage DirectCopy duplications of non-network data management protocol imagescan be corrupt under certain tuned buffer size settings.

2727602

Mapped FullVM backups intermittently report the following error: ERR - Unable to

read next index. VFM error = 4109. Virtual machines with multiple Windowsinstalls do not map all volumes.

2680044

Granular activities fail if any virtualmachine disk files from the backup set share the samename. The issue occurs for Exchange or SharePointVMwareApplication protected backupsin NetBackup 7.5.

2708814

Backups of EV_INDEX_LOCATION return a partially successful status code 1 and thefollowingmessage: 'WIN3287: The parameter is incorrect'. The issue occurswhen the indexpath that is configured in Enterprise Vault is manually modified.

2189585

The Zeta File System root pool fails to mount during a restore.2738043

ANetBackup for Oracle restore fails after all the data is restoredwith a client read timeout.2718308

This EEB fixes a NetBackup Agent for Oracle issue.2807345

The File Count Variance report does not accurately calculate the average number of filesthat are backed up when the backups are multistreamed.

2655967

The File Count Variance report does not accurately calculate the average number of filesthat are backed up when the backups are multistreamed.

2513073




A one-time script was created to clean up orphaned storage lifecycle policy images. Thescript is not included in any other release.

2747595

The NetBackup Resource Broker (nbrb) process does not honor the customer-specifiednbrb settings. Instead it uses the default settings.

2752754

The nbrb call to ListMachineConfig() to read nbrb-specific configuration settings fails.The nbrb process does not honor the user-specified nbrb settings and uses the defaultsettings.

2663636

This EEB fixes a NetBackup Catalog issue.2788379

On a UNIX client, Bare Metal Restore fails when the media server is on a subnet other thanthe master server and the client server subnet.

2684218

On a UNIX client, Bare Metal Restore fails when the media server is on a subnet other thanthe master server and the client server subnet.

2640975

Oracle exports that run for a long time fail with a status code 41. The issue occurs if theOracle user's .profile or .rc files have any statements that write to STDOUT.

2704902

An installation of aNetBackup7.5 x64 client failswhen the client haspostgreSQL installed.2696992

Amissing field in an imagedatabase fragment record causesNetBackupVault to core dumpbecause it tries to copy data from a NULL pointer.

2674385

A new synthetic schedule fails with a status code 200. The issue occurs because deletedschedules are not removed from the streams file.

2690849

Thenbstservprocess fails sometimeswhile it stops. An ImpMgrDBPoller threadhas beenfixed that polls to update the import job statuses in the database.

2689973

Thenbstservprocess fails sometimeswhile it stops. An ImpMgrDBPoller threadhas beenfixed that polls to update the import job statuses in the database.

2660424

The NetBackup-Java Administration Console does not show items in some drop-downmenus.

2580744

NetBackup Enterprise Vault Migrator has improved migration performance. NetBackupEnterprise Vault Migrator backups are 22 times faster than the previous NetBackupEnterprise Vault Migrator.

2754186

The NetBackup Access Control configuration is erased after a 7.5.0.1 patch installation onWindows.

2772490

Exchange granular restore technology backups end with a status code 1.2485432


72



The nbfsd process receives the same in-progress image multiple times from the bpdbmprocess.

2709105

In NetBackup 7.5, an OpenStorage DirectCopy to a tape no longer works.2769014

The file system of a Linux virtual machine cannot be mapped, yet backups show a statuscode 0.

2675339

The file system of a Linux virtual machine cannot be mapped, yet backups show a statuscode 0.

2738005

A restore of a copy 2 made from Optimized Duplication fails because the buffer size isdifferent than copy 1 in the image header file.

2434869

This fix resolves an issue where the deduplication engine (spoold) does not start properlywhen a LocalSystem account is used.

2595016

An SQL query for retrieveDSSUMigrationState needs to be case-insensitive.2770016

Disk staging storage units fail with a status code 228 after an upgrade to 7.5. The policyexecution manager logs report that migration is not complete even though it is.

2726431

The kilobytes per second field in theNetBackup JobMonitor shows impossibly high values.2649695

Oracle snapshot backups that use the Hitachi_ShadowImage method fail when there aremore than 128 configured devices. The bprd process does not allocate enough buffer tohandle a complete spec string while it sends to the XBSA process.

2668324

A restore to an alternate path is successful, but the file is restored to its original location.2698895

The NetBackup Service Layer queue gets filled up, which causes data collection to fail witha socket 25 error. The issue occurs when a large number of events occur that fill up thequeue.

2657218

The nbsl event queue becomes full if the job update influx is too large. This issue causesa job collection failure in OpsCenter.

2676032

DuringVMware backups, thenbpemprocess fails because an assert consistence check fails.2769725

DuringVMware backups, thenbpemprocess fails because an assert consistence check fails.2700371

The Job Collector fails to restart after a failure.2662992

This bundle fixes a NetBackup Catalog issue.2788622

This bundle contains many fixes for VMware.2193082, version 1




This bundle contains many fixes for VMware.2207676, version 1

This bundle contains many fixes for VMware.2299772, version 3, 2

This bundle is a 7.1 hot fix combination of ET 2299772, ET 2256525, ET 2145207, and ET2281357.

2394770, version 1

Large virtual machines cannot be restored because of a disconnected idle socket betweenthe bprd process and the bpbrm process.

2478683, version 1

This bundle is a NetBackup 7.1.0.2 data mover EEB Bundle.2535076, version 2, 1

This bundle is a SAN Client EEB bundle for the NetBackup 7.1.0.2 release.2605325, version 2

Random status 13/BPBKAR fault on differential-incremental BLIB VMware backups.2632895, version 2, 1

BMR experiences occasional problems where bpbrm -collect_bmr_info freezes onWindows media servers, although the import process has completed successfully.

2653356, version 2, 1

This bundle is a 7.1.0.3 EEB bundle for VMware. The bundle contains the following Etracknumbers: ET 2700841 ET 2670418 ET 2651598 ET 2651598 ET 2634978 ET 2694026 ET2694027

2691423, version 1

SANclient backups fail with a status code 83. The errors report thatshm cannot be allocated,and all shared memory slots (pipes) are active.

2730113, version 1

This EEB fixes a NetBackup Fibre Transport issue.2748951, version 1

■ The SQLAgent interface fails when it attempts to set SQL server connection properties.

■ A Microsoft-SQL clustered master database restore sporadically fails.

■ When images are browsed in the SQL interface, the following error message appears:Error encountered trying to read database images.

2754142, version 2, 1

This bundle contains Windows Client fixes for 7.1.0.4.2769877, version 1

This bundle is a NetBackup 7.5.0.1 SAN Client Fibre Transport media server EEB bundle.2779140, version 1

pem fails when it runs VMware Intelligent Policy backups.2785535, version 1


74

Documents

NB 7503 Release Notes