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

up-to-the-minute information
Upgrade assurance that delivers software upgrades
Global support purchased on a regional business hours or 24 hours a day, 7

days a week basis
Premium service offerings that include Account Management Services
For information about Symantecs support offerings, you can visit our Web site
at the following URL:
www.symantec.com/business/support/
All support services will be delivered in accordance with your support agreement
and the then-current enterprise technical support policy.
About Symantec Operations Readiness Tools

Symantec Operations Readiness Tools (SORT) is a set of Web-based tools that
supports Symantec enterprise products. For NetBackup, SORT provides the ability
to collect, analyze, and report on host configurations across UNIX/Linux or
Windows environments. This data helps to assess whether your systems are ready
for an initial NetBackup installation or for an upgrade from your current version.
To access SORT, go to the following Web page:
http://sort.symantec.com/netbackup
Once you get to the SORT page, more information is available as follows:
Installation and Upgrade Checklist

Use this tool to create a checklist to see if your system is ready for a NetBackup
installation or an upgrade.
Hot fix and EEB Release Auditor

Use this tool to find out whether a release that you plan to install contains the
hot fixes that you need.
Custom Reports
Use this tool to get recommendations for your system and Symantec enterprise
products, tips for risk assessment, and product license tracking.
Contacting Technical Support

Customers with a current support agreement may access Technical Support
information at the following URL:
Before contacting Technical Support, make sure you have satisfied the system
requirements that are listed in your product documentation. Also, you should be
at the computer on which the problem occurred, in case it is necessary to replicate
the problem.
When you contact Technical Support, please have the following information
available:
Product release level
Hardware information
Available memory, disk space, and NIC information
Operating system
Version and patch level
Network topology
Router, gateway, and IP address information
Problem description:
Error messages and log files
Troubleshooting that was performed before contacting Symantec
Recent software configuration changes and network changes
Licensing and registration

If your Symantec product requires registration or a license key, access our technical
support Web page at the following URL:
Customer service
Customer service information is available at the following URL:
Customer Service is available to assist with non-technical questions, such as the
following types of issues:
Questions regarding product licensing or serialization
Product registration updates, such as address or name changes
General product information (features, language availability, local dealers)
Latest information about product updates and upgrades
Information about upgrade assurance and support contracts
Information about the Symantec Buying Programs
Advice about Symantec's technical support options
Nontechnical presales questions
Issues that are related to CD-ROMs, DVDs, or manuals
Support agreement resources

If you want to contact Symantec regarding an existing support agreement, please
contact the support agreement administration team for your region as follows:
Asia-Pacific and Japan
customercare_apac@symantec.com
Europe, Middle-East, and Africa
semea@symantec.com
North America and Latin America
supportsolutions@symantec.com
Contents
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 .................................. 11
About compatibility with NetBackup 7.5 ..................................... 11
NetBackup compatibility lists ......................................................... 13
Chapter 3
Product dependencies ........................................................ 17

About product dependencies .......................................................... 17
Operating system patches and updates ............................................. 17
VxFS and VxVM compatible versions ............................................... 24
Chapter 4
Operational notes ................................................................ 27

About operational notes in NetBackup 7.5.0.3 .................................... 27
About general NetBackup 7.5.0.3 notes ............................................ 27
About 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 .................................................. 39
About NetBackup 7.5.0.3 release content .......................................... 40
NetBackup 7.5.0.3 Emergency Engineering Binary (EEB) listing ............ 61
Contents
Chapter
New features and

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

enhancements
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 for
an off-host backup. Now NetBackup for VMware is supported on certain Linux
clients.
For a list of supported Linux versions for the backup host, see:
http://www.symantec.com/docs/TECH127089
For 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 the
customer-specific issues that have been documented in the form of a Titan Case.
Many of these fixes are available as individual engineering binaries and
engineering bundles. These EEBs were created to address specific customer issues
with a previous version of NetBackup. This maintenance release lists those
engineering binaries and bundles.
See About NetBackup 7.5.0.3 release content on page 40.
See NetBackup 7.5.0.3 Emergency Engineering Binary (EEB) listing on page 61.
10
New features and enhancements

About NetBackup 7.5.0.3 new features and enhancements
Chapter
Platform compatibility
About NetBackup 7.5.0.x release compatibility
NetBackup compatibility lists

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

About compatibility with NetBackup 7.5

Symantec NetBackup has always maintained that the master server within your
environment must be at a version level that is equal to or greater than the version
levels of your media servers and client servers within the same environment.
With NetBackup and the NetBackup Appliances, you can apply a maintenance
update (for example 7.5.0.1) to a media server or client server within an
environment where your master server is at a version level of 7.5. This same
scenario can apply to the maintenance updates that are released under a minor
release or release update.
12
For information about NetBackup compatibility with the NetBackup appliances,

see the NetBackup 5xxx Appliance Compatibility Technote on the Symantec
Support Web site.
Symantec NetBackup does not support any scenario where a minor release or
release update is at a higher version level that the parent server. For instance,
the following examples apply.
If a master server is at 7.1, then the media servers and client servers cannot
be 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 cannot
be 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 cannot
be 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 the
various compatibility schemes that a mature product line can support. In this
example, maintenance updates have been released. The same schemes apply with
the new NetBackup 7.5 line.
Table 2-1
NetBackup release compatibility matrix where maintenance updates

have been released
NetBackup master server NetBackup media server
NetBackup client
7.1
6.x, 7.1
6.x, 7.1
7.1
6.x, 7.1
6.x, 7.1.0.1
7.1
6.x, 7.1
6.x, 7.1.0.2
7.1
6.x, 7.1.0.1
6.x, 7.1.0.1
7.1
6.x, 7.1.0.1
6.x, 7.1.0.2
7.1
6.x, 7.1.0.2
6.x, 7.1.0.1
7.1
6.x, 7.1.0.2
6.x, 7.1.0.2
7.5
6.x, 7.1.x.x, 7.5
6.x, 7.1.x.x, 7.5
The following table shows the various compatibility schemes that are supported
with the current NetBackup 7.5 product line.
Table 2-2
NetBackup release compatibility for the 7.5 product line
NetBackup master
server
NetBackup media
server
NetBackup client
7.5
6.0
6.0
7.5
6.5
6.0, 6.5
7.5
7.0
6.0, 6.5, 7.0
7.5
7.0.1
6.0, 6.5, 7.0, 7.0.1
7.5
7.0.2
6.0, 6.5, 7.0, 7.0.1, 7.0.2
7.5
7.1
6.0, 6.5, 7.0, 7.0.x, 7.1, 7.1.0.x
7.5
7.1.0.1
6.0, 6.5, 7.0, 7.0.x, 7.1, 7.1.0.x
7.5
7.1.0.2
6.0, 6.5, 7.0, 7.0.x, 7.1, 7.1.0.x
7.5
7.1.0.3
6.0, 6.5, 7.0, 7.0.x, 7.1, 7.1.0.x
7.5
7.1.0.4
6.0, 6.5, 7.0, 7.0.x, 7.1, 7.1.0.x
7.5
7.5
6.0, 6.5, 7.0, 7.0.x, 7.1, 7.1.0.x, 7.5
7.5
7.5.0.1
6.0, 6.5, 7.0, 7.0.x, 7.1, 7.1.0.x, 7.5, 7.5.0.x
7.5
7.5.0.3
6.0, 6.5, 7.0, 7.0.x, 7.1, 7.1.0.x, 7.5, 7.5.0.x
Note: Support for the NetBackup 6.x product line is scheduled to end October,
2012.

The most up-to-date compatibility information on platforms, peripherals, drives,
and libraries is located in various compatibility lists on the Symantec Support
Web 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 the
latest platforms, peripherals, drives, and libraries.
https://sort.symantec.com/netbackup
For NetBackup, SORT provides an Installation and Upgrade Checklist report
as well as the ability to collect, analyze, and report on host configurations
across UNIX/Linux or Windows environments. In addition, you can determine
in what release whether any hot fixes or EEBs you have installed are fixed.
13
14
You can use this data to assess whether your systems are ready to install or
upgrade to this release.
If you want to view a specific compatibility list, you can find links to each list
that is posted on the Symantec Support Web site:
The following items describe each of the compatibility lists that are available.
The NetBackup Enterprise Server and Server 7.x OS Software Compatibility

List contains information about the operating system (OS) level and the
version that is required to be compatible with a NetBackup master or media
server. It also describes the OS level and the version that is required to be
compatible with a NetBackup client. Predecessors and successors to the
documented operating system levels may function without difficulty, as
long as the release provides binary compatibility with the documented
operating system.
That list contains information about each of the following NetBackup
Enterprise features:
NetBackup Enterprise servers and client
Bare Metal Restore (BMR)
NetBackup Access Control (NBAC)
Network Data Management Protocol (NDMP)
NetBackup SAN Client and Fiber Transport
NetBackup Virtual System compatibility
MSEO (media server encryption option)
NetBackup Media Server Deduplication Option
NetBackup OpsCenter
File System Capability
NetBackup compatibility for a platform or OS version requires platform

vendor support for that product. The platform compatibility lists that
NetBackup maintains are subject to change as vendors add and drop
platforms or OS versions.
The NetBackup server 7.x hardware compatibility list includes information

for compatible drives, libraries, virtual tape devices, robot-types,
fibre-channel HBAs, switches, routers, bridges, iSCSI configurations, and
encryption devices
That list includes information about the compatible drives, robot types,
switches, routers, and bridges, and iSCSI configurations that coincide with
the following hardware:
OpenStorage
Virtual tape libraries (VTLs)
Network Data Management Protocol (NDMP)
Host bus adapters (HBAs)
Encryption
NetBackup Database Agent 7.x Software Compatibility List

This compatibility list contains the most current platform compatibility
information for NetBackup database agents.
NetBackup 7.x Snapshot Client compatibility lists
NetBackup 7.x BMR File System and Volume Manager compatibility lists
See also the NetBackup Bare Metal Restore Administrator's Guide for the
following additional compatibility lists:
BMR compatible shared resource tree (SRT) versions
BMR compatible file systems and volume managers
BMR compatible cluster solutions
BMR disk space requirements
NetBackup7.x Cluster Compatibility List
NetBackup Desktop/Laptop Option compatibility list
Backup Exec Tape Reader compatibility list
15
16
Chapter
Product dependencies
About product dependencies
Operating system patches and updates
VxFS and VxVM compatible versions
About product dependencies

This release requires the same product dependencies that were documented in
the NetBackup 7.5 Release Notes for UNIX, Windows, and Linux document. The
following sections describe the product dependencies and VxFS and VxVM
compatible versions.

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

and version
Patch
Notes
AIX 5.3
AIX runtime libraries 8.0.0.10

or 9.0.0.3 or later
You may need to restart after changing to version

9.0.0.3.
xlC.rte 8.0.0.10 fileset
For the xlC.rte 8.0.0.10 fileset, you may need

to install the IY91284 fix to avoid a potential issue
when creating or updating the NetBackup database.
The IY91284 fix is part of Maintenance Level 6.
AIX 5.3 TL12 SP2 (5300-1202-1036)
NetBackup 7.5 requires the AIX 5.3 TL12 SP2

(5300-12- 02-1036) Maintenance Pack as a minimum.
(Higher patch levels should also work.)
You can use the oslevel -s command to verify
what Maintenance Pack level you have installed.
AIX 6.1
AIX 6.1 TL5 SP5

(6100-05-02-1034)
NetBackup 7.5 requires the AIX 6.1 TL5 SP5

(6100-05-02-1034) Maintenance Pack as a minimum.
(Higher patch levels should also work.)
You can use the oslevel -s command to verify
what Maintenance Pack level you have installed.
AIX runtime libraries 9.0.0.3 or The runtime libraries need to be at 9.0.0.3 or later.
later
You may need to restart after you change to version
9.0.0.3.
HP-UX
COMPLIBS.LIBM-PS32
HP-UX IA64
Networking.NET-RUN:
/usr/lib/libipv6.sl
Networking.NET-RUN-64:
/usr/lib/pa20_64/libipv6.1
/usr/lib/pa20_64/libipv6.sl
Networking.NET2-RUN:
/usr/lib/hpux32/libipv6.so
/usr/lib/hpux32/libipv6.so.1
/usr/lib/hpux64/libipv6.so
If you install AT on an HP-UX platform, this patch

is required.
Table 3-1
and version
Operating system patches and updates for NetBackup (continued)
Patch
Notes
/usr/lib/hpux64/libipv6.so.1
/usr/lib/libipv6.1
HP-UX PA-RISC
HP-UX 11.11
Networking.NET-RUN:
/usr/lib/libipv6.sl
For HP-UX PA-RISC platforms, this fileset is required:
/usr/lib/pa20_64/libipv6.1
/usr/lib/pa20_64/libipv6.sl
/usr/lib/libipv6.1
PHSS_35385
This patch is required for JAVA 6.0.
PHSS_32226
This patch is a LIBCL patch.
PHSS_37516
Contains fixes for the following:

QXCR1000593919: purifyplus dumps core
in PA32
QXCR1000589142: dld crash in
LL_new_descendent_list when the aCC application
is exiting.
is exiting.
QXCR1000746161: dlsym() hangs
QXCR1000593999: dld emits assert messages

for chatr +mem_check enabled 64-bit
executables
PHSS_26946
This patch is necessary to enable any C++ runtime

code to work properly.
PHSS_27740
This patch is a libc cumulative patch.
PHSS_26560
This patch contains a linker tools cumulative patch.
19
20
Table 3-1
and version
Patch
Notes
PHSS_32864
That is a recommended critical patch from HP that

is required for successful NetBackup client backups.
PHKL_26233
This patch enables HP-UX 11.11 mmap() to use

large files from 2GB to 4GB.
PHSS_35379

is required for successful NetBackup client backups.
PHCO_29029

is required for NetBackup to use VxSS.
PHSS_24045
Allow POLL_INTERVAL to be set to zero in /var/

stm/config/tools/monitor/dm_stape.cfg.
That disables the dm_stape monitor within the
Event Monitoring System. Symantec recommends
that you upgrade to IPR0109.
PHSS_30970
This patch can cause problems with the programs

that have the setuid bit set. Hewlett-Packard s IT
resource center Web site contains information about
this patch.
www1.itrc.hp.com
PHCO_35743
S700_800 11.11 libc cumulative patch

The above patch has dependency on the following
patches:
PHCO_31923 (critical patch): s700_800 11.11 libc
cumulative header file patch
PHKL_34805 : 700_800 11.11 JFS3.3 patch; mmap
HP-UX 11.23
PHSS_37201
PHCO_33431
Symantec recommends that all customers running

11.23 install this patch. This applies to HP PARISC
only because HP Itanium has moved to 11.31.
PHSS_34858

is required so that dlopen works properly.
Table 3-1
and version
Patch
Notes
PHKL_31500

NetBackup requires, particularly when you attempt
to run NetBackup with NetBackup Access Control
(NBAC).
PHSS_37492
Contains fixes for the following:

QXCR1000593919: purifyplus dumps core
in PA32
is exiting.
QXCR1000746161: dlsym() hangs
HP-UX 11.31
QXCR1000593999: dld emits assert messages

for chatr +mem_check enabled 64-bit
executables
PHSS_37202
QPK1131 (B.11.31.0809.326)
patch bundle
This patch bundle is required for NetBackup media

server support. This is an HP-UX September 2008
patch bundle.
SUSE Linux Enterprise

Server 10 x64
SUSE Linux Enterprise Server

10 update 2
The operating system version must be SUSE Linux

Enterprise Server 10 update 2 or greater to run
NetBackup 7.0.
Solaris 9 SPARC 64-bit

client
111712-11 (or greater)
Change Request ID - 6815915
111722-04 (or greater)

Patch: 112908-29 (or greater)
Patch: 112874-31 (or greater)
Solaris 10 SPARC 64-bit

(server and client)
122300-53
Change Request ID - 6723423
update 4 (08/07) and newer
The server is supported on update 4 (08/07) and

newer.
21
22
Table 3-1
and version
Patch
Notes
Recommended OS Patchset dated June 2011 or later
Symantec recommends that you download the

recommended patch set dated June 2011 from the
Oracle Support Web site. This patch set contains the
following patches:
118777-17 (SunOS 5.10: Sun GigaSwift Ethernet

1.0 driver patch)
139555-08 (Kernel patch with C++ library
updates).
142394-01 (Internet Control Message Protocol
(ICMP) patch)
143513-02 (Data Link Admin command for Solaris
(DLADM) patch)
141562-02 (Address Resolution Protocol (ARP)
patch)
The following patches are for Solaris 10 SPARC with

NXGE cards:
142909-17 (SunOS 5.10: nxge patch)
143897-03 (Distributed Link Software patch)
143135-03 (Aggregation patch)
119963-21 (Change Request ID - 6815915)
Table 3-1

and version
Patch
Notes
Solaris 10 x86-64
Recommended OS Patchset dated June 2011 or later
Symantec recommends that you download the

recommended patch set dated 12/28/2011 from the
Oracle Support Web site.
Contains the following patches:
118778-15 (SunOS 5.10_x86: Sun GigaSwift
Ethernet 1.0 driver patch)
139556-08 (Kernel patch with C++ library
updates)
142395-01 (SunOS 5.10_x86: ICMP patch)
143514-02 (SunOS 5.10_x86: Data Link Admin

command for Solaris patch)
147259-02 (SunOS 5.10_x86: Aggregation patch)
142910-17 (SunOS 5.10_x86 kernel patch to

include NXGE fixes)
142910-17 (SunOS 5.10_x86: Distributed Link
Software patch)
143136-03 (SunOS 5.10_x86: Aggregation patch)
Windows XP x86-32
KB936357
Microsoft microcode reliability update.
Windows XP x86-64
KB928646
Hot fix for hangs of connection attempts by PBX.
Windows Vista x86-32
KB936357
KB952696
Contains the necessary updates to ensure that you

can back up encrypted files.
KB936357
KB952696

Windows Vista x86-64
Windows Server 2003 IA64 KB913648

(SP1 & SP2)
Windows Server 2003

x86-32 (SP1 & SP2)
Contains the necessary updates to run Volume

Shadow Copy.
KB928646
KB883646
Microsoft Storport hot fix.
23
24
Table 3-1
and version
Patch
Notes
KB913648

Shadow Copy.
KB936357
Windows Server 2003

x86-32 (SP2)
KB971383
TCP/IP protocol driver triggers a disconnect event

randomly. Required for master and media servers.
Windows Server 2003

x86-64 (SP1 & SP2)
KB883646
Microsoft Storport hot fix.
KB913648

Shadow Copy.
KB928646
KB936357
Windows Server 2003

x86-64 (SP2)
KB971383
TCP/IP protocol driver triggers a disconnect event

randomly. Required for master and media servers.
Windows Server 2008

x86-32
KB952696

Windows Server 2008

x86-64
KB952696

Windows Server 2008 IA64 KB952696


Table 3-2 shows the versions of VxFS and VxVM that are compatible with Symantec
NetBackup, and the corresponding operating systems for each.
Table 3-2
Versions of VxFS and VxVM that are compatible with Symantec

NetBackup
Operating system
OS Version
Version of VxFS
Version of VxVM
AIX 5L
5.3 (64 bit)
5.0 MP3 up to 5.1 SP1 up to 5.1 SP1
6.1 (64 bit)
5.0 MP3 and higher
5.0 MP3 and higher
Notes
Table 3-2
Operating system

NetBackup (continued)
OS Version
Version of VxFS
Version of VxVM
7.1 (64 bit)
5.0 MP3 and higher
5.0 MP3 and higher
11.11
3.3 and 3.5
3.5 only
11.23
3.5, 4.1, and 5.0
3.5, 4.1, and 5.0
11.31
4.1 and higher
4.1 and higher
HP-UX IA64
11.31
4.1 and higher
4.1 and higher
Red Hat Enterprise Linux 4.0

(AS)
IA64
4.1 to 4.1MP4RP4
4.1 to 4.1MP4RP4
POWER
5.0 LoP phase1,

phase2, and phase 3
only
5.0 LoP phase1, phase2
x64
LxRT4.1MP4 and
LxRT4.1MP4RP1 and higher
higher on the 4.1
on the 4.1 line, 5.0MP3 and
line, 5.0MP3 and
higher on the 5.0 line
higher on the 5.0 line
IA64
LxRT4.1MP4 and
higher on the 4.1
code line only
4.1MP4RP1 and higher in

the 4.1 code line only
POWER
5.0RU3 and 5.0RU4

only
5.0RU3 and higher
HP-UX PA-RISC

(AS)

(base)
x64
IA64
POWER
z/Architecture
(AS)
x64

(base)
x64
z/Architecture
Notes
25
26
Table 3-2

NetBackup (continued)
Operating system
OS Version
Version of VxFS
Version of VxVM
Solaris 9, 10, 11, 11 Express
SPARC
5.1SP1 and higher
5.1SP1 and higher
Solaris 10, 11, 11 Express
x64
4.1 MP2 and higher
4.1 MP2 and higher

10
x64
4.1MP3 and higher in 4.1MP3 and higher in 4.1

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

4.1 codeline only.
codeline only.
POWER
5.0RU3 and 5.0RU4

only
5.0RU3 and higher
x64
5.0RU1 and higher
5.0RU1 and higher
IA64
NA
NA
POWER
5.0RU4 and higher
5.0RU4 and higher
Windows
x86
NA
4.3 and higher
Windows
x64
NA
4.3 and higher

11
Notes
NetBackup has improved its integration with the Veritas File System (VxFS)
product to ensure interoperability on all compatible VxFS versions. If you run a
VxFS version that is older than VxFS 4.0 then you need to install new VxFS libraries
on the client to back up the systems that run VxFS. You can search and download
the appropriate VxFS libraries to your system from Patch Central on the Symantec
Support Web site.
See, https://sort.symantec.com/labs/patch.
See, http://entsupport.symantec.com/docs/320193.
Chapter
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.3

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

The following items describe the known issues that exist in the NetBackup 7.5.0.3
release.
Concurrent restores of virtual machine may fail when they use a Linux restore
host on a SAN.
28
Operational notes
When using the SAN transport mode to restore multiple virtual machines at
the same time, one or more of the restore jobs may fail. The job status log may
contain 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 for
the format of the restored virtual disks and retry the restore.
If that fails, select NBD as the transport mode on the Recovery Options
dialog box and try the restore again.
An Accelerator backup can fail with a status code 84. The error can occur for
several reasons. A possible solution is to expire backup images. Before you
expire backup images, do the following:
Identify the reason for the backup failure. If the backup failed because it
tried to copy data from a previous backup image, the backup image needs
to be examined.
If the backup image was a restarted or resumed backup, the backup image
needs to be verified.
If that backup image fails the verification, the backup header information
for that backup image needs to be examined.
If the data amount in the fragments does not match the amount of data
that there should be, then expire that backup image.
NetBackup 7.5.0.3 does not support VMware backup hosts or restore hosts on
RHEL (Red Hat). If the policy's VMware backup host option is Backup Media
Server and one media server is on RHEL, NetBackup may incorrectly select
that 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 specify
a 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, and
SUSE 10 and 11. For more details on supported platforms, refer to the following
Technote:
Operational notes
On an HP-UX platform, the installation of NetBackup versions 7.5.0.1 or later

fails 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 that
uses a Bare Metal Restore shared resource tree.
-SetupMaster sets up the master server to use NetBackup Access Control.This
setup adds the root and administrator by default to the NBU_Security Admin
group. The first time that you use -SetupMaster with the -fsa option adds
the 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 more
members.
In the case of a Windows cluster, you are prompted for the password for your
current operating system user identity.
The NetBackup Accelerator in NetBackup 7.5.0.3 does not support Client Direct
when the client NetBackup version is greater than the NetBackup media server
version. For example, a 7.5.0.1 media server does not support a client backup
that runs 7.5.0.3 when policies include both Client Direct and Accelerator
backup selections. The media server and client version mismatches in this
configuration cause the Client Direct nbostpxy process on the client to core
dump. The version incompatibility is resolved in the next NetBackup 7.5
maintenance patch.
Files that are restored as links are not renamed properly. If the hard link files
are restored to an alternate location, the files that are restored as links point
to the original location. They should point to the alternate location. The issue
occurs when the user creates a policy and takes a mapped FullVM backup of
an RHEL virtual machine.
After an upgrade to NetBackup 7.5.0.3, VMware backups may fail with a status
code 6 and the following message: the backup failed to back up the
requested files.
For more information, refer to the following Technote:
After an upgrade to 7.5.x, VMware backups may be slower than expected.

For more information, refer to the following Technote:

The following operational notes that pertain to NetBackup's OpsCenter are carried
over from the NetBackup 7.5.0.1 Release Notes.
29
30
Operational notes
In the 7.5.0.3 version, the NetBackup database has been upgraded to Sybase
EBF 11.0.1+2789. To adapt to the changes in NetBackup, the OpsCenter 7.5.0.1
database has also been upgraded to the Sybase EBF 11.0.1+2744 version.
In the case of Enterprise Vault, OpsCenter reports only on email archiving

data that pertains to Microsoft Exchange Servers. If email archiving is disabled
in Enterprise Vault, OpsCenter cannot collect the required data. Therefore,
you cannot see any data on the Enterprise Vault Archiving reports in
OpsCenter.
This limitation in Enterprise Vault reporting is not included in the NetBackup
OpsCenter Administrator Guide.
OpsCenter does not support creating or editing multiple reports simultaneously

for the same user session from different tabs or windows. You cannot open
the same OpsCenter console in two or more browser tabs or windows and create
or edit standard and custom reports simultaneously. That causes an exception
to occur.
The Deduplication reports do not show any data when you select the Report
On parameter as Storage Unit Name.
For VMware or Hyper-V clients, the search and restore operations work only
if the client name is the same as host name. If the client name is the same as
display name, UUID, or DNS name then only the Search functionality is
available. You cannot perform restore operations in this case. The following
table provides details on whether Search and Restore functionality is available
when the client name is the host name, display name, etc.:
Client Name Type
Host Name
Display Name
UUID
DNS Name
Search
Yes
Yes
Yes
Yes
Restore
Yes
No
No
No
OpsCenter installation and deployment information and best practices.

The following list contains information about installing OpsCenter and some
best practices information:
Symantec recommends that you do not cancel or interrupt the installation

process once it is started.
You may be unable to logon to the OpsCenter interface if it is installed on

a server that has an underscore(_) in the host name. To avoid this issue,
ensure that the OpsCenter Server host name does not contain any
underscores like opshost.
Operational notes
Installing OpsCenter components in a location that is mounted from a

remote host is not supported.
A file selection list that contains more than 50 items does not appear in
OpsCenter.
For a specific job ID in an OpsCenter Analytics custom report, breakup job data
is available only for 50 job directories. That is because when a NetBackup policy
or job is associated with more than 50 backup selections, data is available for
only 50 backup selections. The NetBackup user interface truncates data for
the subsequent backup selections (greater than 50).
With VBR, you can view the breakup job information for all of the job directories
that are associated with a job or policy. That is because data collection in VBR
happened through CLIs (and not through nbsl).
OpsCenter does not provide the option to purge breakup jobs.

Unlike VBR, OpsCenter does not provide the option to purge breakup jobs. In
the VBR console, you can purge specific breakup jobs from the Settings >
Global Settings > Data Retention section.
An uninstall script is removed if an uninstall process for an OpsCenter Server

or Agent is canceled or interrupted.
If an uninstallation process for OpsCenter Server or Agent is canceled or
interrupted on UNIX, then the uninstall script (uninstallOpsCenterServer
and uninstallOpsCenterAgent) is removed from /opt/VRTS/install. If you
want to uninstall the OpsCenter Server again, you can use the uninstall scripts
from the OpsCenter DVD.
Some result sets for a stored procedure that has multiple result sets may not
appear.
When you run a stored procedure that has multiple result sets, the output of
only the first result set is displayed on the interface. The output of other result
sets is not shown on the interface.
The number of characters for a virtual name by the clustering technology on

Windows is limited.
The virtual host name must be the short name (not FQDN) and less than 15
characters.
Some reports may only consider Full and Incremental schedule type jobs.
On applying Schedule/Level Type filter with value All, the following reports
consider only Full and Incremental schedule type jobs:
Advanced Success Rate
All Failed Backups
Consecutive Failures Report
31
32
Operational notes
Success Rate Line
The NetBackupOpsCenter resource is offline after you have installed an

OpsCenter cluster.
After installing an OpsCenter cluster on a Windows 2008 R2 x64 system, you
must manually bring the NetBackupOpsCenter resource online. You can bring
the NetBackupOpsCenter resource online from the command line interface or
by using the cluster user interface.
You can use the following command:
hares -online <resource name> -sys <Name of the active node>
Example: hares -online newonelatest-OpsCenter -sys OPS-CLUSTER-1
On Windows systems, the log.conf file is not created properly. That causes
the vxlogview to return a No logs to be displayed message.
Use the following commands to view logs for OpsCenter GUI (OID-147) and
Infrastructure components (OID-761):
OpsCenter GUI:
<INSTALL_PATH>\OpsCenter\server\bin\vxlogview -p 58330 -o
147 -G
<INSTALL_PATH>\OpsCenter\gui\logs
Infrastructure components:
<INSTALL_PATH>\OpsCenter\server\bin\vxlogview -p 58330 -o
761 -G
<INSTALL_PATH>\OpsCenter\gui\logs
The object merger utility in OpsCenter fails on the master server.

The object merger utility in OpsCenter (Settings > Configuration > Object
merger) does not work (fails) for a master server. The object merger utility
works for clients and media servers.
The Custom Tabular Backup and Custom-Client count report does not return
data after an upgrade from VBR.
The Custom Tabular Backup and Custom-Client count report does not return
any data after you have upgraded from VBR to OpsCenter.
To work around this issue, you must manually change the filter settings to get
the correct report data after the upgrade is complete. The following steps guide
you to change the filter settings:
Open the report, then select Edit Report.
From the Filters section, select Job.
Operational notes
From the Column drop-down list, select Product Type. The default operator
is the equals sign character, =.
From the Value drop-down list, select the same product type that you
selected for VBR and click Add.
Click Next to view the report. Once the changes are made, the reports
display the correct data.
Save the report.
The OpsCenter server can stop receiving events from the master server after
a NetBackup upgrade.
If all following conditions are applicable, add the
OPS_CENTER_SERVER_NAME entry to the bp.conf file on UNIX or the
registry on Windows to set OpsCenter's server name. Symantec recommends
that you do add the entry before you attempt to upgrade.
The REQUIRED_INTERFACE is configured on the master server.
The OpsCenter server monitors the master server.
The OPS_CENTER_SERVER_NAME entry is not configured on the master

server
If you do not add this entry, the OpsCenter server stops receiving events from
the master server after the upgrade.
An enhancement has been made in OpsCenter to maintain VBR parity.

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

This section lists the end-of-life notifications for the features, platforms, and
devices that are no longer compatible with NetBackup beginning with the next
major release.
Oracle Corporation has announced the end-of-life for Java 6 in July 2012.
As a result, NetBackup does not support Java 6 in the next major release.
In addition, the following clients are no longer supported beginning with the
next major release of NetBackup:
Red Hat Linux Itanium
SLES Linux Itanium
For additional information on end-of-life notifications, refer to the NetBackup

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

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

The following topics show the Etrack numbers that are fixed and contained in
each of the following NetBackup packages for this release.
1302158 1945602 2052733 2234663 2325345 2353644 2375710 2378935 2420422
2439415 2495973 2510848 2514600 2527358 2535411 2569157 2570149 2570223
2574458 2574462 2574464 2574465 2574468 2574578 2592618 2597458 2608743
2612872 2619956 2630595 2632848 2632944 2633176 2635004 2637416 2643340
2643753 2646166 2646225 2646887 2652181 2655134 2655962 2655970 2656466
2657785 2658505 2659032 2659314 2660324 2661571 2661785 2661797 2662834
2662982 2663077 2664228 2664432 2665224 2665385 2665423 2665526 2667172
2669936 2670410 2671407 2671537 2671645 2671671 2671922 2671950 2673932
2675069 2675302 2675305 2675325 2675704 2675969 2677550 2677892 2678208
2678632 2678678 2679830 2679952 2682169 2688166 2688570 2688683 2689365
2690082 2690815 2691019 2692930 2693068 2693273 2693320 2693630 2694825
2695316 2696760 2696880 2697103 2697214 2698378 2698445 2700043 2700394
2700918 2700920 2701894 2701945 2702528 2702530 2702549 2703143 2703605
2705671 2710178 2710443 2711924 2713354 2713358 2713969 2714425 2714454
2714871 2715903 2718018 2718669 2720582 2721954 2722188 2722240 2722358
2723309 2724743 2724840 2725368 2726355 2726529 2726662 2727404 2727873
2729280 2729293 2729299 2729457 2730061 2730154 2730391 2730545 2730891
2731271 2731274 2731280 2731282 2731286 2731289 2731359 2731411 2731428
2731432 2731434 2731435 2731436 2731437 2731439 2731441 2731444 2731445
38
About the current release content index

2731446 2731447 2731450 2731452 2731453 2731455 2731458 2731460 2731461

2731462 2731464 2731466 2731467 2731468 2731469 2731471 2731474 2731475
2731481 2731482 2731484 2731485 2731486 2731487 2731488 2731489 2731490
2731492 2731494 2731495 2731497 2731499 2731500 2731501 2731502 2731503
2731504 2731507 2731508 2731509 2731511 2731512 2731513 2731516 2731517
2731518 2731519 2731520 2731522 2731523 2731524 2731525 2731528 2731531
2731532 2731534 2731535 2731536 2731538 2731542 2731544 2731551 2731554
2731559 2731561 2731562 2731564 2731566 2731567 2731568 2731594 2731616
2731621 2731623 2731625 2731629 2731631 2731632 2731637 2731639 2731640
2731647 2731649 2731654 2731657 2731662 2731665 2731667 2731671 2731673
2731674 2731677 2731680 2731684 2731688 2731693 2731697 2731698 2731699
2731700 2731701 2731702 2731806 2732145 2732703 2733313 2733581 2733982
2734009 2734151 2734274 2734280 2734835 2734841 2735017 2735265 2735363
2735554 2736254 2736479 2736522 2736534 2736675 2737514 2737778 2737785
2737909 2737911 2737926 2738018 2738123 2738161 2738220 2738899 2739172
2739391 2739527 2739570 2739614 2740561 2740830 2740874 2741286 2741592
2742045 2742107 2742128 2742152 2742194 2742267 2742269 2742328 2742765
2742775 2743159 2743184 2743223 2743594 2743933 2744629 2744645 2744647
2744898 2744900 2745185 2745623 2746866 2746931 2747203 2748327 2748342
2748615 2748863 2748871 2749550 2749781 2749805 2750140 2750157 2751634
2751738 2752909 2752923 2753324 2753385 2754155 2754245 2754840 2754848
2755318 2756551 2756763 2756988 2757195 2758151 2758292 2759841 2761066
2761115 2761149 2761154 2761217 2761225 2761326 2761569 2761735 2762066
2762544 2763332 2764092 2764508 2764522 2765680 2766299 2767568 2767571
2767592 2767597 2769313 2769917 2770003 2770580 2770903 2770995 2771165
2771258 2771345 2772464 2772883 2773103 2773176 2773605 2773717 2774039
2775222 2775298 2775415 2775534 2776131 2776313 2776672 2776792 2777242
2777502 2778008 2778114 2778693 2779184 2779210 2779219 2779744 2780684
2780839 2781062 2781474 2781491 2781957 2782023 2782125 2782434 2783199
2783633 2783682 2784010 2784508 2784543 2784625 2784663 2785084 2785232
2785516 2787061 2787758 2787769 2788380 2788474 2788938 2789538 2789907
2790082 2790221 2791060 2791069 2791120 2791149 2791390 2793915 2793967
2794282 2795018 2795614 2797146 2797507 2802935 2803622 2803629 2805070
2805893 2807747 2808551 2808751 2811099
Appendix
About the current release

content
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 conventions

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


This topic contains a list of known issues that were fixed and included in this
release 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 of
fragments that run for a long time.
Description:
A browse for certain catalog files fails with a status code 23, which causes the
bpdbm process to fail.
Description:
When a restore is performed on an alternate client, the Restore Audit record
shows the actual client. The issue has been resolved so that the record displays
the correct client.
Description:
A policy that is configured with a large number of email addresses can cause
a policy data collection failure. The issue occurs of the email addresses equate
to over 255 characters.
Description:
The File Count Variance report does not accurately calculate the average
number of files that are backed up when the backups are multistreamed.
Description:
An issue has been fixed where the media required for restore alert was
not raised.
Description:

When accelerator is enabled on a policy and a Windows client has the change
journal enabled, a changed file may not benefit from accelerator optimization.
The issue occurs when files are deleted and then recreated with the same name.
The result is that backups take longer because more data is backed up than
necessary.
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 remove
the unreferenced images that are present for placeholder purposes only.
Placeholder images contain the references that prevent the removal of a Storage
service definition. The issue persists even if it appears that all images are
removed that reference it.
Description:
A change has been made to address an issue that caused the data collection
for EMC NetWorker jobs to fail.
Description:
When accelerator-based backups are performed, backups may fail when the
new backup copies data from a previous backup to synthesize the new backup.
This problem may occur because a file that had previously contained data is
truncated to 0 bytes. Then the fingerprint that is associated with the truncated
file is incorrect. When the server attempts to verify the copied data, it uses
the 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 core
dump in some cases. The command fails with the following error message:
premature eof encountered.
41
42

Description:
The LIST_FS_IMAGE_HEADERSvalue is not visible by all nodes of a cluster
and may not be visible to the Enterprise Media Manager server. It has been
migrated to thenbdb process from the bp.conf/registry. The old value is no
longer used beyond the migration step.
Description:
An OpsCenter upgrade from version 7.0 and after fails because a primary key
constraint is violated. The failure occurs when duplicateFTM configurations
are at the same view level. A procedure has been added to remove the duplicates
before this violation occurs.
Description:
This fix enables users to view Cloud data collection status through OpsCenter.
The user can see a new entry, Cloud under the Data Collection Status tab
within Settings.
Description:
Explicit chmod and chgrp commands have been added to the move_libs script
to correct a permissions error when files are copied.
Description:
When a backup fails, the activity monitor shows that the job continues to run
after it is retried, which is false. The try file log messages have been suppressed
so that the bpjobd process does not show these false details in the activity
monitor.
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 Job Manager uses. Now the try file does not have duplicate
BEGIN OPERATION messages for the create, mount, and delete steps of snapshot
duplication.
Description:

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

Direct.
Description:
When the user reports on a large master server, the socket connection between
the 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 1
even though all data is restored.
Description:
The following fixes from NetBackup 7.1.0.4 were not in 7.5 and have been
added for this release:
A synthetics fix has been added to validate that the file offsets in the catalog
correspond to the same data on the disk. The backup fails if the data is
wrong.
A bpstsinfo -comparedbandstu command enhancement has been added

to do the same offset validation and image size check that synthetics should
do.
A bpverify enhancement has been added to validate an image with the

same synthetics offset validation.
Description:
Disk group and pool capacities are reported incorrectly. The nbdevconfig
process reports a negative number for the raw size of the disk pool. The error
can cause jobs to fail with insufficient disk space.
Description:
Incremental backups of EV_INDEX_LOCATION are partially successful with a
status code 1: WIN32 87: The parameter is incorrect. Full backups complete
with a status code 0. A case-sensitive comparison of Enterprise Vault index
file paths causes the problem. A fix has been added that compares path strings
without case sensitivity.
Description:
43
44

An import on a target server fails if the target server version is before 7.5. The
issue occurs when Automatic Image Replication is used to replicate Catalog
Backup images from one domain to another. The solution requires a patch on
top of 7.1 before the import is successful.
Description:
If one Exchange database is on a mount point or an independent disk, VMware
snapshot jobs do not become momentarily inactive. This issue occurs when a
VMware backup is aware of the Exchange application. The issue results in a
failure to browse or restore Exchange mailbox items.
Description:
The tar code has been fixed so that hard links and soft links are not renamed
in 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 a
large number of images.
Description:
Snapshot replication jobs fail with a status code 84 when the bpdm log indicates
that the storage server failure code is 2060046. The failure occurs when the
destination of a storage lifecycle policy replication operation is a storage unit
group that contains units from multiple storage servers. The other criteria for
this failure is a backup policy with some selections that span volumes and
exist 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 queried
across a set of clients when the result set is small.
Description:

When OpsCenter is upgraded to Windows 2008 R2 x64, Simple Network

Management Protocol traps are not sent. This issue is observed only on a few
systems.
Description:
If Application Protection and the Enable indexing options are selected for
the VMware policy type, the Policy Execution Manager fails when the backup
request submits. Indexing is not supported for application protection. Interface
changes have been made to not allow a combination of indexing and application
protection.
Description:
The bperror process reports the client name as the media server instead of
the appropriate virtual machine. This error occurs when an error occurs in a
VMware policy with a VMware Intelligent Policy query for client selection.
The nbpem process shows the backup host name as the client name for the
failed backup job for VMware Intelligent Policies. From the nbpem logs, the
object RecoverableJob logs the client name as the media server name. However,
when the job is submitted, the Policy Execution Manager passes the correct
client name to the nbjm process.
Description:
VMware backups of applications have been allowed functionality with Granular
Resource Technology. This change is so the backups can work when there are
multiple vmdk files with the same name in the backup set.
Description:
An image migration comes across an image with a corrupt or missing backup
ID field and marks the image as skipped. The image has been moved into the
db.corrupt folder.
Description:
Some jobs that should be run as DirectCopy jobs within a Network Data
Management Protocol filer instead move data through the media server.
Description:
45
46

If a schedule type is not specified, the bpimage -lastbackup command fails

with an exit status 223: An invalid entry was encountered.
Description:
Once the master database is restored, the SQL server restarts the SQL instance
services. This issue causes a problem because the SQL Agent still queries the
SQL server. A fix has been made so the SQL server is not queried once the
master database restore is complete.
Description:
An SQL query for configuration fails because it is case-sensitive. A change has
been made so the query is not case-sensitive.
Description:
Veritas Unified Logging for Windows x86 uses a 32-bit system, but NetBackup
uses a 64-bit system. As a result, Veritas Unified Logging structures are
misaligned for some variables when NetBackup accesses them.
Description:
Files cannot be restored from a non-network data management protocol (NDMP)
image that is duplicated to an NDMP storage unit through the NDMP
DirectCopy . To work around this issue, use the touch file
NMDP_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 release
happens after the snapshot removal call, which causes orphaned snapshots.
Description:
When the Loopback File System is present on a client, NetBackup now treats
it as a local file system. When the Loopback File System is not present on a
client, NetBackup now treats it as a Network File System. This fix is
implemented on the client as a touch file: TREAT_LOFS_LOCAL.

Description:
An issue occurs when an SQL server 32-bit instance is installed on a 64-bit
computer and SQLINSTANCE $ALL is specified in an SQL batch file. The MSSQL
agent skips the 32-bit default instance for backup.
Description:
During a restore, if there are a lot of orphaned or leftover snapshots, the virtual
machine XML file becomes too large and causes buffer failures. This fix adjusts
the 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 an HP system if the volume group
is larger than 64 megabytes.
Description:
When certain Linux client configurations are imported into the Bare Metal
Restore database, the bmrd process enters an infinite loop. The issue occurs
when the bmrd process evaluates disk configurations, and some disks cannot
be processed.
Description:
The Bare Metal Restore FirstBoot script fails if it cannot communicate with
the master server to update the task status and stay active for a restart.
Description:
On an AIX system, a NetBackup restore for Oracle fails after the data is restored
because no server status is given.
47
48

Description:
This fix enables the use of the touch file
USE_BACKUP_MEDIA_SERVER_FOR_RESTORE for restore jobs. The fix lets you
select the media server that was used to perform a backup operation.
Description:
Oracle tables with many columns cause export jobs through bporaexp and
bpdbsbora to fail with a status code 41.
Description:
Oracle table exports that run for a long time cause the bpdbsbora and
bporaexp64 processes to deadlock with a status code 41.
Description:
XML exports of Oracle tables fail with the following error message: ORA-00936:
missing expression. The issue occurs if the reserved words in Oracle are
used as column names in a table.
Description:
Veritas Unified Logging for x86 has been changed to remove
USER_32BIT_TIME_T because NetBackup uses 64-bit time. This change fixes
structure misalignments when NetBackup references some elements in the
Veritas Unified Logging structures.
Description:
On a Red Hat 6 Update 1 system, Fibre Transport media server configuration
fails when the /etc/init.d/nbftserver start command is executed. The
scripts in this fix can be installed to resolve the issue. Install the scripts and
retry 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 view
the first 200. The limit has been increased to 1000.

Description:
The column headers are covered up when EXPORT_MESSAGE_TEXT headers are
used 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 in
a tree of type MASTER_SERVER.
Description:
In Java ViewBuilder, the Unassigned tab and the All Objects tab are not sorted
alphabetically as they are in Veritas Backup Reporter.
Description:
In Backup Exec, OpsCenter does not process the Half-inch Cartridge media
type.
Description:
A large number of records in domain_JobArchive, Domain_TapeLibrary, and
other domains may cause Job Data Collection to enter a queued state.
Description:
When the Virtual Client Summary report is run, the same virtual client is
listed multiple times. For some or all of these replications, the client is reported
to 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 Windows
VMware policy and the values contain keywords such as AND, OR, or NOT.
The Query Builder can corrupt these entries in the interface because it
translates these keywords as new operands.
49
50

Description:
A fix has been made to the nbstserv code to check for a termination request
before images are updated. This fix avoids an issue where the nbstserv process
core dumps when NetBackup services are stopped.
Description:
In the Job Monitor, the Total Kbytes transferred field can become negative
and the kilobytes/sec field can be very large during some restore jobs.
Description:
Some images can fail to duplicate in the duplication jobs that use OpenStorage
DirectCopy to a tape of non-network data management protocol images. This
issue occurs when the buffer size that is used for the primary copy is greater
than the value of NDMP_FILE_MAX_READ_LENGTH. The default value is 64
kilobytes.
Description:
Tape drives take a long time to unload. The unload process fails if a drive is
too slow.
Description:
When the nbemmcmd -changesetting command is used to add a parameter on
a cluster name, the following error appears: invalid host name (136).
Description:
After an upgrade to NetBackup 7.1.0.3, a number of bpdbm processes use a high
amount of CPU.
Description:
During a stream discovery, the Job Manager removes all deleted schedules
before the current streams file is updated with new discovery data.
Description:
During snapshot creation, a snapshot-based database agent policy type scenario
fails with a status code 156 in the bpfis process. The issue occurs when there

are a large number of physical devices or when the SNAPSHOT_METHOD_ARGS

string is larger than 3 kilobytes.
Description:
Virtual machines with multiple Windows installations do not map 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 the
backup job completes with a status code 0.
Description:
On UNIX platforms, a process can fail if there is low free space in the file system
that contains temporary files for odbc driver communication.
Description:
During backups on a Windows client when Use change journal has been
enabled, 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 NetBackup

change journal databases.
Description:
The bpplinfo process fails because a NULL check is not in the index server.
Description:
This fix resolves an issue where the deduplication engine spoold does not start
properly in a LocalSystem account.
Description:
A restore is not in the first batch of fingerprints that is retrieved, so the restore
fails when the fingerprint is not found.
51
52

Description:
The destination container is not properly chosen during compaction, which
caused the container to not be given back to the system.
Description:
When a NetBackup Access Control permission is set through the bpnbaz
interface, granular permissions may not be set correctly.
Description:
The bpdbm process can core dump when it changes the primary copy if the
backup 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 original
location.
Description:
On Mac OS X platforms, the version of nbsl that was released with NetBackup
7.5 fails with a runtime error.
Description:
An issue in disk staging storage units has been fixed for back-level media
servers.
Description:
Incomplete storage lifecycle policy images cannot be deleted with the nbcatsync
-prune_catalog command.
Description:
An issue has been fixed where the Universally Unique ID caused a memory
leak and a file descriptor leak when it was called.
Description:

An issue has been fixed where the root and the administrator are not added
by default as Security Administrators in the Authorization Security group.
Description:
PAM authentication does not do a case-insensitive comparison of the password
prompt string.
Description:
The bprd process enters an infinite loop when the bpcd process gives it a
corrupted version string.
Description:
On Windows 2008 R2, Sybase SQL Anywhere software fails to identify available
physical processors if they are grouped. This issue causes a smaller number
of processors to be used than available. Sybase SQL Anywhere now supports
the Solaris 11 platform (SPARC and x64) with this release of NetBackup. This
release also supports Solaris 11 as a master server platform.
Description:
In the bpjobd process, the JOBDBSUSPEND command acts immediately when it
is executed as part of catalog recovery. This issue sometimes causes pending
updates to the job to be lost. The fix makes sure that the JOBDBSUSPEND
command waits for the provider queue to be empty before it suspends the
database. The fix also forces the caller to wait until the completion of the
suspend or resume command.
Description:
When an index server list is provided to nbholdrestorehelper, and it contains
shared folders from more than one index server, the process fails. The failure
happens because the process uses the incorrect path staging folder for the
second index server. This issue occurs when a user has more than one index
server.
Description:
For volumes with a size of several terabytes, the RvpBitmap process fails
because of a lack of address space in the x86 proxies.
53
54

Description:
A performance improvement to granular restore technology has been made
for PureDisk storage.
Description:
This submission does the following to fix orphaned snapshot issues for virtual
machines.
It attempts snapshot consolidation.
It provides a registry entry so the bpfis process waits according to the

registry setting before it removes VMware snapshots. The wait helps when
disk lease release takes a long time.
It provides wait facility in the bpfis -delete process when it is called

though the bpkar process is still in progress. Registry entry controls the
wait and helps control orphaned snapshots.
Description:
In NetBackup 7.5, a fix has been made to an invalid parameter that causes
bandwidth throttling to fail.
Description:
A temporary mount of the Zeta file system root pool fails if the value for
canmount 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 the
policy, the job may fail with a status code 130. The NetBackup logs indicate
that the bpbkar process is terminated by signal 10.
Description:
The storage area network (SAN) client has been improved to minimize the
need to restart the nbftclnt service and daemon. The purpose is to
accommodate NetBackup and SAN maintenance. A new command, nbftconfig
-ra has been added to trigger a rescan of Fibre Transport target devices on all
SAN clients. The nbftclnt service no longer has to be restarted.

Description:
Granular restore technology paths with Newline characters or FFFF may not
be written properly to the catalog.
Description:
Sometimes Data Collection may not start after a failure, though the agent
reconnection time is set to 10 minutes.
Description:
For a Microsoft Exchange backup, ncflbc log files grow rapidly and create a
low disk space condition on the client. This issue occurs even when log levels
are at 0 or 1.
Description:
For Master Servers that run a NetBackup version before 7.5, the storage
lifecycle policy (SLP) status report displays an incorrect status. The report
shows that an SLP job is in progress even though it is complete. The SLP job
state for a copy is not updated for duplication to a tape. The event runs once
a 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 SharePoint
backend 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 and
bpbrm 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 than
10 minutes.
Description:
55
56

A single backup job cannot back up more than one CAB file at a time. This fix
allows multiple CAB files to be backed up at once, and improves the speed of
NBU_EV_Migrator by 22 times.
Description:
An Exchange granular browse for the backup IDs that belong to one backup
may 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 fails
intermittently with a status code 13.
Description:
When runtime data collection is enabled, the time of day for the collection can
change to a later time as collections continue. This fix keeps the collection
time within 15 minutes of its originally set time.
When runtime data collection is disabled, old collection data is never deleted
after a collection has occurred. This fix ensures that old data is deleted after
two weeks.
Description:
When a process runs that contains the string inetd, it may be incorrectly
terminated. The grep -Ew command has been added to the client_config
script to exclude those processes and avoid their termination. ps checks that
look for inetd and xinetd have been updated to use the grep -Ew command
for all platforms but Solaris. An exclusion of sesinetd has been explicitly
added for that platform.
Description:
Duplication jobs can freeze because of an invalid protocol message from a
sub-process of bpdm or bptm.
Description:

An Exchange 2010 Database Availability Group snapshot backup fails when

an Exchange policy is configured with some individual databases that are
separated with NEW_STREAM directives.
Description:
A Dynamic Host Configuration Protocol client may not browse and initiate
restores of the client. Restores have to be initialized from the server.
Description:
The nbrb process does not honor the settings that the user configures. It instead
uses the default settings if the settings are present in the database.
Description:
When the user has network data management protocol backups on a media
manager tape storage unit, restores from those backups fail.
Description:
A Secure Sockets Layer security issue is fixed with the Rackspace Cloud plug-in,
where the data that is sent to the Cloud can be compromised. Metering data
is not collected in OpsCenter if the start timestamp is from the previous year
and the end timestamp is the current year. The nbcssc Cloud service has been
fixed to search for the year that the metering data was collected.
Description:
If extra files are present under a schedule directory, any schedule updates
cause all other schedules to be deleted. The disk staging storage unit relocation
schedule is also deleted. Duplication jobs are not scheduled and the disk staging
storage unit is filled to capacity. A fix has been added to check the files under
the schedule directory.
Description:
After an upgrade from 7.1.0.3 to 7.5, the Client Risk Analysis report does not
display clients at risk if the primary job is a snapshot. The report displays rows
for clients with old backup times, even though new backups have been
completed within the specified date range.
57
58

Description:
For a backup, the transport type appears in the Detailed Status of the Activity
Monitor. For a restore, the transport type appears in the progress log.
Description:
The NetBackup-Java Administration Console fails to validate the credentials
of 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 up
if placeholder images still reference it.
Description:
In a VMware backup, Exchange or SharePoint granular restore technology
activities may fail. The issue occurs if there are 10 or more volumes from the
backed up virtual machine.
Description:
A new lookup entry has been added to show the appropriate message that is
received from NetBackup on the OpsCenter interface.
Description:
The bprd process enters an infinite loop when it receives a corrupt version
string from the bpcd process.
Description:
If the connection fails when the SQL Agent connects to the SQL server, the
Agent tries to write the error in thedbaclient logs. A NULL pointer exception
results.
Description:

When files are backed up that are larger than 2032 megabytes but smaller
than 2047 megabytes, a NetBackup Accelerator job may fail with this message:
cannot write image to disk, Invalid argument.
Description:
When the criteria for list files may include a backup ID and a client name where
the case does not match, the application can fail.
Description:
VMware Intelligent Policy backups can cause the Policy Execution Manager
to 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 the
action matrix is deleted. This fix prevents a failure from when the job history
is dumped into the logs.
Description:
The tar.exe executable fails if an invalid transport mode is selected for a
virtual machine restore.
Description:
Not all One Click variance reports are displayed.
Description:
The bpbkar DATA_STOCK process is bounced off the media server firewall when
the bpstart_notify process runs long enough for the firewall to time out.
This issue causes backups to fail for large file systems.
Description:
59
60

If a catarc image is already migrated to the NetBackup database and an image

in the db/images directory still references the catarc image, the image
relationship is lost. The issue also occurs when two images in separate client
directories 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 an XML discovery file that is larger than
256 kilobytes. This check prevents file truncation and backup job failure.
Description:
The user cannot use the Backup, Archive, and Restore interface to browse a
backup image and select files for restore. This issue occurs under the following
conditions:
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 incremental
backup.
Description:
During the OpsCenter patch upgrade process to 7.5.0.x, the symcsearchd.db
file is not backed up.
Description:
Snapshot copies that become invalid after a Point In Time rollback need to be
removed from the NetBackup catalog. This change fixes a problem where
invalid snapshot copies are left in the NetBackup catalog after a rollback. Their
presence gives the false impression that they can be used for future restores.
Description:

An issue exists where an incorrect last backup time can be calculated. The
issue occurs if the latest image expires when there is a parent-child job
hierarchy and the child image has a stream number of 0.
Description:
A VMware Intelligent Policy backup runs a full backup when it should run an
incremental backup.
Description:
During multistream jobs, incorrect data is displayed for backup duration
variance.
Description:
A problem has been corrected where too much data is backed up in incremental
VMware Intelligent Policy backups.
Description:
A problem has been corrected where too much data is backed up in incremental
VMware Intelligent Policy backups.
Description:
When Use Accelerator is enabled on the backup policy, backups may complete
successfully. However the backups may only back up a couple of items instead
of everything in the specified backup selection. This problem is only seen in
backups 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, and
available to our customers in the form of an Emergency Engineering Binary (EEB).
NetBackup 7.5.0.3 resolves the addressed issues in each of these EEBs. Additional
EEBs may have been released since this document was posted. If you do not see
61
62

an EEB that you expected to see in this document, contact your Symantec
NetBackup Support representative. You can also use SORT for NetBackup to find
for which releases an issue has been resolved. See the following link:
https://sort.symantec.com/netbackup
If you require additional information about an issue in this table, contact your
Symantec NetBackup Support representative.
Table B-1
NetBackup 7.5.0.3 EEB Listing
Etrack Number
EEB Description
2655015
The Media Required for Restore alert is not generated.
2650649
An alert is not generated when a restore job is in the waiting state because of unavailable
media.
2600512
OpsCenter does not generate Media Required For Restore alerts.
2622505
Some OpsCenter reports require the media ID field to be populated in the job database for
all child jobs of multiplexed backups and duplications. Otherwise, the reports cannot
determine the type of storage unit in use.
2416944
2650641
OpsCenter does not generate Media Required For Restore alerts.
2381571
2441838
The Tape Mount Request alert is not generated for restore jobs.
2660635
An issue occurs on a clustered master server when nbemmcmd -changesetting is run

for a setting that does not exist. If a cluster name is passed, it shows an invalid host name
and the setting is not added. The command works if an active node name passes.
2715544
The bpbkar socket gets closed by the media server firewall when the bpstart_notify
process runs for too long.
2591566
During the creation of the preview list, unnecessary string conversions can cause large
delays in NetBackup Vault jobs.
2648559
The default instance is skipped from a backup. The issue occurs when a 32-bit MSSQL
default instance is installed on a 64-bit server and an MSSQL batch file specifies
SQLINSTANCE $ALL.

Table B-1
NetBackup 7.5.0.3 EEB Listing (continued)
Etrack Number
EEB Description
2665486
This fix enables the use of the touch file, USE_BACKUP_MEDIA_SERVER_FOR_RESTORE

for restore jobs. That allows the media server that was used to perform the backup operation
to be selected.
2583566
This fix enables the use of the touch file, USE_BACKUP_MEDIA_SERVER_FOR_RESTORE

for restore jobs. That allows the media server that was used to perform the backup operation
to be selected.
2734894
The lbc process or the bpcd process may cause an exception during a granular restore
from duplicated backup images. This issue occurs because of some special characters that
the NetBackup client does not handle correctly when it sends to the catalog.
2636625
The bpdbm process can cause the duplications that run for a long time to timeout from
apparent inactivity.
2744563
After an upgrade to 7.1.0.4, snapshot completions are slower.
2782219
After an upgrade to 7.1.0.4, snapshot completions are slower.
2557732
The Advanced Success Rate report does not include multiple stream backups.
2703802
Job Data Collection goes into a queued state.
2760478
On Windows platforms, there is a performance issue when backups are run with a number
of bpdbm processes with NetBackup Access Control set to ON.
2683975
After an upgrade to NetBackup 7.1.0.3, there is high CPU utilization by a number of bpdbm
processes.
2745114
The bprd.exe file does not delete Veritas Unified Log files in a Windows x86 environment.
2597829
2732224
2761973
2719131
2794722
The nbsl process fails during a shutdown.
2732786
2684057
2762849
63
64

Table B-1
Etrack Number
EEB Description
2649340
On an HP-UX 11.31 system, Bare Metal Restore shared resource tree creation fails if the
system host name is longer than eight characters.
2428117
The virtual clients that reference more than one master server appear in the Unassigned
view in ViewBuilder.
2588648
2660255
The virtual clients that reference more than one master server show up in the Unassigned
2382403
view of ViewBuilder.
2704580
If the Windows Remote Administration Console is not connected to the first server on the
list, it gives the following error message: (46) server not allowed access.
2762728
If the Windows Remote Administration Console does not connect to the first server on the
list, it gives the following error message: (46) server not allowed access.
2358033
The time that is taken to shut down NetBackup services is high if the network goes down.
1977458
2063360
2534647
NetBackup services take a long time to shut down when the IP address goes down. This
issue causes long delays in cluster failover.
2184011
2529191
The NetBackup service group does not go offline after a network link goes down.
2641589
When the IP address goes down and a cluster tries to shut down NetBackup services, it
takes a large amount of time. This issue causes a delay in failover.
2278840
2717447
NetBackup services do not shut down in a timely manner when an IP resource becomes
unavailable.
2728069
NetBackup services do not shut down in a timely manner when the IP resource becomes
unavailable.
2660588
For a VMware Intelligent Policy, the bperror process reports a client name as the media
server instead of the virtual machine that failed.

Table B-1
Etrack Number
EEB Description
2715916
The bperror process reports a client as the media server in a VMware Intelligent Policy
that uses a query for client name selection.
2659374
This fix resolves an issue where Content Router containers are not properly released to the
OS when thresholds are reached.
2653530
2658486
2654222
2657085
2690734
2660720
Disk staging storage unit schedules are deleted and scheduled relocations do not
automatically run. The issue occurs if some extra files are present in the database or the
schedule directory.
2519076
When two backups start on the same Windows client, both bandwidths are halved.
2645285
Throttling is sometimes not followed when it is set.
2776687
LIMIT_BANDWIDTH does not work as expected.
2699258
LIMIT_BANDWIDTH does not work as expected for Windows clients.
2744407
LIMIT_BANDWIDTH does not work as expected for Windows clients.
2565104
The bandwidth throttle freezes when a second backup starts on the same Windows client.
2331633
In OpsCenter 7.1, a Custom Tabular report does not sort the Client Name column.
2748607
For Solaris, a Veritas Volume Manager disk group fails to map because of a lack of available
space.
2657515
An unmap_all command fails on the configurations that have Solaris zones on Veritas
Volume Manager. Also, disk groups fail to map because of a lack of available space.
2680699
On Solaris, a Veritas Volume Manager disk group fails to map because of a lack of available
space.
65
66

Table B-1
Etrack Number
EEB Description
2637606
When the close_server command is not called for a multiplexed backup to a PureDisk
Deduplication Option storage unit, severe resource leaks result.
2567947
If multistream and multiplexing backups are configured to a deduplication storage unit, a

disk pool down situation results because too many connections are open.
2586848
Backups can cause the bpbkar32.exe executable to core dump in the MSVCR80.dll
module.
2751543
Root users on UNIX and the users that belong to local administrator groups on Windows
can modify NetBackup Security settings. They can modify the settings even when they are
not in the NBU_Security Admin group.
2557307
This Windows-only EEB enables customers to restore Storage Foundation Clients with a
Bare Metal Restore FastBoot shared resource tree. It is an alternative to the Legacy shared
resource tree for Storage Foundation Client restores.
2705855
Simple Network Management Protocol traps are no longer sent after a server upgrade to
Windows 2008 R2 x64.
2727495
Simple Network Management Protocol traps are no longer sent after a server upgrade to
Windows 2008 R2 x64.
2677632
Simple Network Management Protocol alerts are logged, but they are not seen on systems
with external tools.
2663639
An Oracle export fails with a status code 41 if there are too many columns in the table.
2595168
Column headers are covered up when EXPORT_MESSAGE_TEXT headers are used on exported
reports.
2708292
The Fibre Transport media server configuration scripts nbftsrv_config and nbftserver
have been modified to fix kernel identification issues for RHEL 5.x OS versions with patches.
2661041
You cannot restore files from the virtual machine backup images that are duplicated to the
NDMP drive (Physical tape library ) through an NDMP DirectCopy.
2662754
On an HP system, media shared resource tree creation fails if the volume group size is
greater than 64 megabytes.
2185079
The bpbrm program may freeze if BPCD_GET_NB_VERSION_RQST does not complete. Other
jobs freeze and cannot be canceled.
2682953
High CPU utilization occurs if the bpgetconfig -s client name -l A command is

called for a 6.5 client. The command waits for a response from the bprd process, which is
trapped in an infinite loop because of corrupt data from the bpcd process.

Table B-1
Etrack Number
EEB Description
2742386
High CPU utilization occurs because multiple nbproxies wait for a response from the
bprd process. The process gets stuck while it parses the version file contents of a client
host.
2660807
The bpduplicate process receives a malformed message that causes it to freeze. The
bpduplicate process properly handles the error message and stops the job. The issue
occurs because an OpenStorage plugin problem causes the bptm process to core dump.
2686819
The nbsl process does not send the image updates that are subsequent to initial data
collection for OpsCenter.
2717337
A restore on a Microsoft SQL clustered master database sporadically fails, although the
master database is restored and recovered successfully.
2687832
A restore on a Microsoft SQL clustered master database sporadically fails, although the
master database is restored and recovered successfully. The SQL Agent interface fails when
the SQL server connection properties are set.
2619988
Restore Audit Records do not contain the alternate client restore information.
2706969
Restore Audit Records should contain the alternate client restore information.
2393120
A one-time script has been created to address when a disk storage unit is full. The
nbdevquery report shows negative numbers for the raw size when the High Water Mark
is exceeded and there is insufficient disk space.
2385825
2532199
2562242
2563662
2436324
67
68

Table B-1
Etrack Number
EEB Description
2562179
2612736
2658267
2376845
2580249
2580250
2562537
2743111
After an upgrade to 7.5, Exchange granular activity logs more at a bpconfig debug level
of 0. The issue occurs even when the ncflbc folder does not exist.
2367085
In NetBackup 7.1, the bpbkar32.exe executable faults on a Mapped Linux Virtual Machine
backup with the logical volume manager (LVM) configured.
2115317
The Veritas Mapping Service returns an error 4109 when Block Level incremental backups
are enabled. The issue occurs for incremental backups with the vStorage application
programming interface (API) on a large vmdk file.
2778989
This EEB has a modified nbftsrv_config script for cases when the script creates duplicate
entries in driver_aliases. The issue causes excessively long configuration times on a
Solaris 10 SPARC Fibre Transport media server.
2355921
In the NetBackup console, the vStorage query builder corrupts queries when they consist
of operands like OR and AND.

Table B-1
Etrack Number
EEB Description
1603726
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 fix
for the client is a touch file openv/netbackup/TREAT_LOFS_LOCAL.
1077887
This fix treats the Loopback File System (LOFS) as a local drive for Solaris 10 Zone support.
1155270
This fix treats the Loopback File System (LOFS) as a local drive for Solaris 10 Zone support.
1204968
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 fix
for the client is a touch file openv/netbackup/TREAT_LOFS_LOCAL.
2138872
An issue occurs when ALL_LOCAL_DRIVES is used on Solaris 10 zones with a Loopback

File System. The file system mount is identified as a separate file system mount and as part
of the root file system. This conflicts with multiple entries for the same file.
1377572
The Zeta file system (ZFS) is not backed up when the ALL_LOCAL_DRIVES directive is used.
1165573
Zeta file systems on a Solaris 10 client are not backed up when the ALL_LOCAL_DRIVES
directive is used in the policy configuration under NetBackup. The client is modified to
treat it as a cross mount point backup.
2732347
If either UpdateBars or UpdateDatabase permissions are added to the Media Resource, a

non-existent Up permission is also added.
2726414
The Java ViewBuilder does not sort the list of unassigned objects like Veritas Backup Reporter
does.
2672447
A Sybase engine fails to use all physical processors that are available on the computer.
2780624
A Sybase engine fails to use all physical processors that are available on the computer.
2705693
The console limit is 200 collectors per agent.
2672578
The virtual client Summary report lists the same client multiple times, and with Exists
in Policy equals No.
2769980
Virtual machine data collection creates an additional entry for clients, even if the client
already exists in the database.
2676500
The Rename hard links and Rename soft links functions do not work during a
single file restore from a mapped FullVM backup.
2489363
The Drive Utilization shows lesser utilization for jobs with a large number of fragments
that run for a long time.
2651159
Performance issues occur when views are exported.
69
70

Table B-1
Etrack Number
EEB Description
2681770
Half-inch Cartridge media is not reported correctly for Backup Exec.
2694003
An unnecessary statement has been removed that causes an error message in the log file
2685232
An unnecessary statement has been removed that causes an error message in the log file.
2682994
The nbcatsync process does not recognize compressed image catalog files.
2704490
The script BMR-FirstBoot errors out to a command line. The issue occurs if it cannot
communicate with the master server to update the task status and stays active for any
restarts.
2729052
The script BMR-FirstBoot errors out to a command line. The issue occurs if it cannot
communicate with the master server to update the task status and stays active for any
restarts.
2601560
After an upgrade from 7.0 to 7.1, a browse for the SQL client fails with a status code 23 and
causes a bpdbm application fault. The following error message appears: unexpected
return value from db_FLISTreceive.
2583875
After an upgrade from 7.0 to 7.1, a browse for the SQL client fails with a status code 23 and
causes a bpdbm application fault. The following error message appears: unexpected
return value from db_FLISTreceive.
2715340
An XML export of an Oracle table fails if Oracle's reserved keywords are used as column
names.
2634978
Snapshots are sometimes not cleaned up correctly. The bpfis -delete command is called
though the bpbkar process still runs. Disk lease release happens after the snapshot removal
call.
2800797
This EEB fixes a NetBackup Catalog issue.
2724681
For the bpcd process and the bpbrm process, backups fail with the following message:
status: 229: events out of sequence - image inconsistency.
2639354
The Deduplication Engine (spad) process sometimes fails during backup and duplications
jobs.
2685598
The Commit_CallAtPostInstallDll custom action fails during a NetBackup client

installation on Windows.
2741249
No data is restored from a network data management protocol backup. The bptm process
exits with a status code 0.

Table B-1
Etrack Number
EEB Description
2749290
No data is restored from a network data management protocol backup. The bptm process
exits with a status code 0.
2787723
No data is restored from a Network Data Management Protocol (NDMP) backup with remote
NDMP. The bptm process exits with a status code 0, but the job freezes.
2665356
An import of XML data fails.
2769435
If a stream finishes more than 30 minutes before the parent job terminates, the policy
execution manager may fail.
2776251
The last file of OpenStorage DirectCopy duplications of non-network data management

protocol images can be corrupt under certain tuned buffer size settings.
2673580
OpenStorage DirectCopy duplications of non-NDMP images can be corrupt under certain

tuned buffer size settings.
2776250
The last file of an OpenStorage DirectCopy duplication of a non-NDMP image can be corrupt
under certain tuned buffer size settings.
2727602
OpenStorage DirectCopy duplications of non-network data management protocol images

can be corrupt under certain tuned buffer size settings.
2680044
Mapped FullVM backups intermittently report the following error: ERR - Unable to
read next index. VFM error = 4109. Virtual machines with multiple Windows
installs do not map all volumes.
2708814
Granular activities fail if any virtual machine disk files from the backup set share the same
name. The issue occurs for Exchange or SharePoint VMware Application protected backups
in NetBackup 7.5.
2189585
Backups of EV_INDEX_LOCATION return a partially successful status code 1 and the

following message: 'WIN32 87: The parameter is incorrect'. The issue occurs when the index
path that is configured in Enterprise Vault is manually modified.
2738043
The Zeta File System root pool fails to mount during a restore.
2718308
A NetBackup for Oracle restore fails after all the data is restored with a client read timeout.
2807345
This EEB fixes a NetBackup Agent for Oracle issue.
2655967
The File Count Variance report does not accurately calculate the average number of files
that are backed up when the backups are multistreamed.
2513073
The File Count Variance report does not accurately calculate the average number of files
that are backed up when the backups are multistreamed.
71
72

Table B-1
Etrack Number
EEB Description
2747595
A one-time script was created to clean up orphaned storage lifecycle policy images. The
script is not included in any other release.
2752754
The NetBackup Resource Broker (nbrb) process does not honor the customer-specified
nbrb settings. Instead it uses the default settings.
2663636
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 default
settings.
2788379
This EEB fixes a NetBackup Catalog issue.
2684218
On a UNIX client, Bare Metal Restore fails when the media server is on a subnet other than
the master server and the client server subnet.
2640975
On a UNIX client, Bare Metal Restore fails when the media server is on a subnet other than
the master server and the client server subnet.
2704902
Oracle exports that run for a long time fail with a status code 41. The issue occurs if the
Oracle user's .profile or .rc files have any statements that write to STDOUT.
2696992
An installation of a NetBackup 7.5 x64 client fails when the client has postgreSQL installed.
2674385
A missing field in an image database fragment record causes NetBackup Vault to core dump
because it tries to copy data from a NULL pointer.
2690849
A new synthetic schedule fails with a status code 200. The issue occurs because deleted
schedules are not removed from the streams file.
2689973
The nbstserv process fails sometimes while it stops. An ImpMgrDBPoller thread has been
fixed that polls to update the import job statuses in the database.
2660424
The nbstserv process fails sometimes while it stops. An ImpMgrDBPoller thread has been
fixed that polls to update the import job statuses in the database.
2580744
The NetBackup-Java Administration Console does not show items in some drop-down
menus.
2754186
NetBackup Enterprise Vault Migrator has improved migration performance. NetBackup

Enterprise Vault Migrator backups are 22 times faster than the previous NetBackup
Enterprise Vault Migrator.
2772490
The NetBackup Access Control configuration is erased after a 7.5.0.1 patch installation on
Windows.
2485432
Exchange granular restore technology backups end with a status code 1.

Table B-1
Etrack Number
EEB Description
2709105
The nbfsd process receives the same in-progress image multiple times from the bpdbm
process.
2769014
In NetBackup 7.5, an OpenStorage DirectCopy to a tape no longer works.
2675339
The file system of a Linux virtual machine cannot be mapped, yet backups show a status
code 0.
2738005
The file system of a Linux virtual machine cannot be mapped, yet backups show a status
code 0.
2434869
A restore of a copy 2 made from Optimized Duplication fails because the buffer size is
different than copy 1 in the image header file.
2595016
This fix resolves an issue where the deduplication engine (spoold) does not start properly
when a LocalSystem account is used.
2770016
An SQL query for retrieveDSSUMigrationState needs to be case-insensitive.
2726431
Disk staging storage units fail with a status code 228 after an upgrade to 7.5. The policy
execution manager logs report that migration is not complete even though it is.
2649695
The kilobytes per second field in the NetBackup Job Monitor shows impossibly high values.
2668324
Oracle snapshot backups that use the Hitachi_ShadowImage method fail when there are
more than 128 configured devices. The bprd process does not allocate enough buffer to
handle a complete spec string while it sends to the XBSA process.
2698895
A restore to an alternate path is successful, but the file is restored to its original location.
2657218
The NetBackup Service Layer queue gets filled up, which causes data collection to fail with
a socket 25 error. The issue occurs when a large number of events occur that fill up the
queue.
2676032
The nbsl event queue becomes full if the job update influx is too large. This issue causes
a job collection failure in OpsCenter.
2769725
During VMware backups, the nbpem process fails because an assert consistence check fails.
2700371
During VMware backups, the nbpem process fails because an assert consistence check fails.
2662992
The Job Collector fails to restart after a failure.
2788622
This bundle fixes a NetBackup Catalog issue.
2193082, version 1
This bundle contains many fixes for VMware.
73
74

Table B-1
Etrack Number
EEB Description
2207676, version 1
2299772, version 3, 2
2394770, version 1
This bundle is a 7.1 hot fix combination of ET 2299772, ET 2256525, ET 2145207, and ET
2281357.
2478683, version 1
Large virtual machines cannot be restored because of a disconnected idle socket between
the bprd process and the bpbrm process.
2535076, version 2, 1
This bundle is a NetBackup 7.1.0.2 data mover EEB Bundle.
2605325, version 2
This bundle is a SAN Client EEB bundle for the NetBackup 7.1.0.2 release.
2632895, version 2, 1
Random status 13/BPBKAR fault on differential-incremental BLIB VMware backups.
2653356, version 2, 1
BMR experiences occasional problems where bpbrm -collect_bmr_info freezes on

Windows media servers, although the import process has completed successfully.
2691423, version 1
This bundle is a 7.1.0.3 EEB bundle for VMware. The bundle contains the following Etrack
numbers: ET 2700841 ET 2670418 ET 2651598 ET 2651598 ET 2634978 ET 2694026 ET
2694027
2730113, version 1
SAN client backups fail with a status code 83. The errors report that shm cannot be allocated,
and all shared memory slots (pipes) are active.
2748951, version 1
This EEB fixes a NetBackup Fibre Transport issue.
2754142, version 2, 1
The SQL Agent 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.
2769877, version 1
This bundle contains Windows Client fixes for 7.1.0.4.
2779140, version 1
This bundle is a NetBackup 7.5.0.1 SAN Client Fibre Transport media server EEB bundle.
2785535, version 1
pem fails when it runs VMware Intelligent Policy backups.

NB 7503 Release Notes

Hochgeladen von

Dokumentinformationen

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

NB 7503 Release Notes

Hochgeladen von

Copyright:

Verfügbare Formate

Symantec NetBackup

7.5.0.3 Release Notes

Telephone and/or Web-based support that provides rapid response and

Upgrade assurance that delivers software upgrades

Global support purchased on a regional business hours or 24 hours a day, 7

Premium service offerings that include Account Management Services

About Symantec Operations Readiness Tools

Installation and Upgrade Checklist

Hot fix and EEB Release Auditor

Contacting Technical Support

Product release level

Available memory, disk space, and NIC information

Version and patch level

Router, gateway, and IP address information

Error messages and log files

Troubleshooting that was performed before contacting Symantec

Recent software configuration changes and network changes

Licensing and registration

Questions regarding product licensing or serialization

Product registration updates, such as address or name changes

General product information (features, language availability, local dealers)

Latest information about product updates and upgrades

Information about upgrade assurance and support contracts

Information about the Symantec Buying Programs

Advice about Symantec's technical support options

Nontechnical presales questions

Issues that are related to CD-ROMs, DVDs, or manuals

Support agreement resources

Europe, Middle-East, and Africa

North America and Latin America

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

New features and enhancements ...................................... 9

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

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

Operational notes ................................................................ 27

End-of-life notifications ..................................................... 35

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

About the current release content ................................... 39

New features and

About NetBackup 7.5.0.3 new features and enhancements

About NetBackup 7.5.0.3 new features and

NetBackup for VMware now available on Linux:

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

New features and enhancements

About NetBackup 7.5.0.x release compatibility

NetBackup compatibility lists

About NetBackup 7.5.0.x release compatibility

NetBackup Enterprise Server and Server 7.x OS Software Compatibility List

About compatibility with NetBackup 7.5

For information about NetBackup compatibility with the NetBackup appliances,

NetBackup release compatibility matrix where maintenance updates

NetBackup master server NetBackup media server

6.x, 7.1.x.x, 7.5

6.x, 7.1.x.x, 7.5

NetBackup release compatibility for the 7.5 product line

6.0, 6.5, 7.0

6.0, 6.5, 7.0, 7.0.1

6.0, 6.5, 7.0, 7.0.1, 7.0.2

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

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

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

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

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

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