NB 7507 Release Notes

Symantec NetBackup
7.5.0.7 Release Notes

NetBackup 7.5.0.7
Maintenance Release Update
Document Version 1
Symantec NetBackup 7.5.0.7 Release Notes

Documentation version: 7.5.0.7
Legal Notice
Copyright 2013 Symantec Corporation. All rights reserved.
Symantec, the Symantec Logo, the Checkmark Logo and NetBackup are trademarks or
registered trademarks of Symantec Corporation or its affiliates in the U.S. and other countries.
Other names may be trademarks of their respective owners.
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.
Symantec Corporation
350 Ellis Street
Mountain View, CA 94043
http://www.symantec.com
Technical Support
Symantec Technical Support maintains support centers globally. Technical Supports
primary role is to respond to specific queries about product features and functionality.
The Technical Support group also creates content for our online Knowledge Base.
The Technical Support group works collaboratively with the other functional areas
within Symantec to answer your questions in a timely fashion. For example, the
Technical Support group works with Product Engineering and Symantec Security
Response to provide alerting services and virus definition updates.
Symantecs support offerings include the following:
A range of support options that give you the flexibility to select the right amount
of service for any size organization
Telephone and/or Web-based support that provides rapid response and

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

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

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

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

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

Use this tool to get information about what items Symantec intends to replace
with newer and improved functionality, and what items Symantec intends to
discontinue without replacement. Some of these items include certain NetBackup
features, functionality, 3rd-party product integration, Symantec product
integration, applications, databases, and the OS platforms.
Contacting Technical Support

Customers with a current support agreement may access Technical Support
information at the following URL:
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 ...................................... 8

About the NetBackup 7.5.0.7 release ................................................. 8
About NetBackup 7.5.0.7 new features and enhancements ..................... 9
NetBackup 7.5.0.7 new enhancements and support .............................. 9
Chapter 2
Platform compatibility ....................................................... 10

About upgrade paths to the NetBackup 7.6 line of releases ...................
About NetBackup 7.5.0.x release compatibility ...................................
About software release types ....................................................
About compatibility with NetBackup 7.5 .......................................
NetBackup compatibility lists ...........................................................
Chapter 3
Product dependencies
10
11
12
12
14
....................................................... 17
Operating system patches and updates ............................................ 17
Chapter 4
Operational notes
............................................................... 26
About NetBackup 7.5.0.7 operational notes .......................................

Installation and upgrade notes ........................................................
General NetBackup 7.5.0.7 notes ....................................................
Bare Metal Restore notes ...............................................................
Cloud storage notes ......................................................................
Database and application agent notes ..............................................
Creating a minimal NetBackup account for Exchange operations
(Exchange 2010 and 2013) ................................................
Deduplication notes ......................................................................
Seeding the fingerprint cache for MSDP ......................................
About upgrading MSDP and PureDisk deduplication solutions to
resolve case sensitivity issues .............................................
NetBackup OpsCenter notes ..........................................................
NetBackup Search notes ...............................................................
About upgrading Search to NetBackup 7.5.0.x ..............................
Virtualization notes .......................................................................
26
27
28
30
31
32
34
35
35
36
40
44
44
44
Contents
Chapter 5
End-of-life notifications ..................................................... 52

About future NetBackup end-of-life notifications .................................. 52
Appendix A
About the NetBackup 7.5.0.7 release content .............. 54

About NetBackup release content ....................................................
About release content conventions .............................................
NetBackup 7.5.0.7 release content ...................................................
NetBackup 7.5.0.7 Emergency Engineering Binary (EEB) listing ............
54
54
55
58
Chapter
New features and

enhancements
This chapter includes the following topics:
About the NetBackup 7.5.0.7 release
About NetBackup 7.5.0.7 new features and enhancements
NetBackup 7.5.0.7 new enhancements and support
About the NetBackup 7.5.0.7 release

NetBackup 7.5.0.7 represents the final release that introduces new features and
enhancements to NetBackup 7.5. All future customer-requested defect fixes for
version 7.5 will be addressed in a newer line of NetBackup releases, such as version
7.6.x.x.
Symantec recommends that customers upgrade their NetBackup 7.5 environments
to version 7.5.0.7 to take advantage of the latest product fixes and enhancements.
However, NetBackup customers that plan to upgrade to version 7.6 should review
their upgrade path options before they install version 7.5.0.7.
See About upgrade paths to the NetBackup 7.6 line of releases on page 10.
NetBackup Late Breaking News

For the most recent NetBackup news and announcements, visit the NetBackup
Late Breaking News website at the following location:
http://www.symantec.com/docs/TECH74904
Other NetBackup-specific information can be found at the following location:
go.symantec.com/nb
New features and enhancements

About NetBackup 7.5.0.7 new features and enhancements
About NetBackup 7.5.0.7 new features and

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

The NetBackup 7.5.0.7 release offers the following new enhancements and support:
Support for VMware Virtual Disk Development Kit (VDDK) 5.1 Update 1
Upgrade to Java Runtime Environment (JRE) 7
Chapter
Platform compatibility
About upgrade paths to the NetBackup 7.6 line of releases
About NetBackup 7.5.0.x release compatibility
NetBackup compatibility lists
About upgrade paths to the NetBackup 7.6 line of

releases
Note: If you do not plan to upgrade your NetBackup environment to version 7.6
within the first half of calendar year 2014, you can safely ignore this topic.
Additionally, if you are running NetBackup 7.5 and do not plan to upgrade to version
7.6 within the first half of calendar year 2014, Symantec recommends that you
upgrade to version 7.5.0.7 to take advantage of the latest bug fixes and compatibility
features.
For more information about the NetBackup 7.6 GA release: See the section called
About NetBackup 7.6.0.1 on page 11.
Upgrades to NetBackup 7.6 are supported from any release since NetBackup 6.0.
However, some of the functionality that was introduced in NetBackup 7.5.0.6 and
later is not present in the NetBackup 7.6 GA release. The difference in functionality
is limited to bug fixes and a small set of features. The following list describes the
various upgrade paths that Symantec recommends:
If you are currently running NetBackup 7.5.0.5 or earlier, your upgrade path is
to NetBackup 7.6 GA.
If you are currently running NetBackup 7.5.0.6 and you do not use Amazon S3
cloud storage buckets in regions other than US Standard, your upgrade path is
to 7.6 GA.
If you upgrade to NetBackup 7.5.0.7 or you are currently running version 7.5.0.6
with Amazon S3 cloud storage buckets in regions other than US Standard, your
upgrade path is to a release in the NetBackup 7.6 maintenance line (triple-dot)
available in the first half of calendar year 2014.
About NetBackup 7.6.0.1

NetBackup 7.6.0.1 is a full media kit release and is considered the NetBackup 7.6
GA release. NetBackup 7.6.0.1 is not considered part of the NetBackup 7.6
maintenance release line. NetBackup 7.6.0.1 does not provide the recommended
upgrade path for the functionality differences that are described in this topic.
Symantec will publicly declare the maintenance release that provides the
recommended upgrade path when that software is released to manufacturing (RTM).
Please check the following tech note periodically for updated information:
Upgrades from NetBackup 7.5.0.6

If your NetBackup environment relies on any of the following functionality that is
found in version 7.5.0.6 and later, then your upgrade path is to a release in the
NetBackup 7.6 maintenance line (triple-dot):
Amazon S3 cloud storage buckets in regions other than US Standard

See Cloud storage notes on page 31.
Installing or Upgrading from NetBackup 7.5.0.7

If you do not plan to upgrade your NetBackup 7.5 environment to version 7.6 within
the first half of calendar year 2014, Symantec recommends that you install the
7.5.0.7 maintenance release to ensure that your environment has the latest bug
fixes and compatibility features.
If your plan is to upgrade to NetBackup 7.6 GA within the first half of calendar year
2014, then Symantec recommends that you do not install the NetBackup 7.5.0.7
maintenance release.

This release supports the platforms and binary sizes that were documented in the
NetBackup 7.5 Release Notes document.
For more information about platform compatibility, refer to the following documents
available from the Symantec Support website:
11
NetBackup 7.5 Release Notes

http://www.symantec.com/docs/DOC5332
NetBackup Enterprise Server and Server 7.x OS Software Compatibility List

About software release types

Symantec maintains a policy by which NetBackup can deliver various levels of
releases to accommodate customer needs. The following list defines the various
release types and the version number schemes that are associated with each type.
The NetBackup family of software and appliance products use these release types
and number schemes.
A major release is the first in a series of releases. This type of release contains
new features, new supported platforms, and a complete set of the latest product
documentation.
A minor release is a single-dot release that follows a major release, for example
2.5 or 7.5. This release type contains much of the same requirements as a major
release. It contains a smaller set of new features and enhancements, any
platform proliferation, and a complete set of updated documentation.
A software release update is a double-dot release, for example 2.5.1 or 7.5.1.

This release type may contain a few new features and enhancements as well
as many product fixes. Only those documents that are applicable to the new
features or enhancements are updated and republished.
A maintenance release update is a triple-dot release, for example 2.5.0.1 or

7.5.0.1. This release type is primarily comprised of a number of fixes that are
developed to address issues in major, minor, and software update releases.
This release type may also include a small number of new features,
enhancements, and platform or application proliferations. The only documentation
that is provided is an online Readme and a release notes document that is
available on the Symantec Support website.
Note: NetBackup versions 2.5.0.1, 2.5.1, and 7.5.1 are used in this topic as
examples. These versions of NetBackup do not exist at the time of this document's
publication.
About compatibility with NetBackup 7.5

Symantec NetBackup has always maintained that the master server within an
environment must be at a version level that is equal to or greater than the version
levels of the media servers and clients within that environment. Symantec
12
recommends that you keep your entire NetBackup environment up-to-date with the
latest maintenance (triple-dot) releases. However, NetBackup offers the flexibility
of an environment where the clients and the media servers are running a different
triple-dot release than the master server. For example you can upgrade a media
server or client to version 7.5.0.1 in an environment where the master server is
running version 7.5. This same scenario applies to double-dot releases. For example
you can upgrade a media server or client to version 7.5.1.1 in an environment where
the master server is running version 7.5.1.
Since the NetBackup catalog resides on the master server, the master server is
considered to be the client for a catalog backup. If your NetBackup configuration
includes a media server, it must use the same NetBackup version as the master
server to perform a catalog backup. See the NetBackup Installation Guide for
information about mixed version support.
See About software release types on page 12.
For information about NetBackup compatibility with the NetBackup appliances, see
the following tech note on the Symantec Support website:
Symantec NetBackup does not support any scenario where a minor release or
software release update is at a higher version level than the parent server. For
instance, the following examples apply:
If a master server is at 7.5, then the media servers and clients cannot be at a
single-dot version level that is higher than 7.5, such as 7.6.
If a master server is at 7.5, then the media servers and client servers cannot be
at a double-dot version level that is higher than 7.5, such as 7.5.1.
If a master server is at 7.5.1, then the media servers and clients cannot be at a
double-dot version level that is higher than 7.5.1, such as 7.5.2.
Note: NetBackup versions 7.5.1, 7.5.1.1, 7.5.2, and 7.6 are used in this topic as
examples. These versions of NetBackup do not exist at the time of this document's
publication.
The following table shows the various compatibility schemes that are supported
with the current NetBackup 7.5 product line.
Table 2-1
NetBackup release compatibility for the 7.5 product line
NetBackup master
server
NetBackup media
server
NetBackup client
7.5
7.0
7.0
13
Table 2-1
NetBackup release compatibility for the 7.5 product line (continued)
NetBackup master
server
NetBackup media
server
NetBackup client
7.5
7.0.1
7.0, 7.0.1
7.5
7.1
7.0, 7.0.1, 7.1, 7.1.0.x
7.5
7.1.0.1
7.0, 7.0.1, 7.1, 7.1.0.x
7.5
7.1.0.2
7.0, 7.0.1, 7.1, 7.1.0.x
7.5
7.1.0.3
7.0, 7.0.1, 7.1, 7.1.0.x
7.5
7.1.0.4
7.0, 7.0.1, 7.1, 7.1.0.x
7.5
7.5
7.0, 7.0.1, 7.1, 7.1.0.x, 7.5, 7.5.0.x
7.5
7.5.0.1
7.0, 7.0.1, 7.1, 7.1.0.x, 7.5, 7.5.0.x
7.5
7.5.0.2
Note: NetBackup 7.5.0.2 is the version

that the NetBackup Appliance 2.5
software release is based on. NetBackup
7.5.0.2 is not a standalone version of
NetBackup.
7.5
7.5.0.3
7.0, 7.0.1, 7.1, 7.1.0.x, 7.5, 7.5.0.x
7.5
7.5.0.4
7.0, 7.0.1, 7.1, 7.1.0.x, 7.5, 7.5.0.x
7.5
7.5.0.5
7.0, 7.0.1, 7.1, 7.1.0.x, 7.5, 7.5.0.x
7.5
7.5.0.6
7.0, 7.0.1, 7.1, 7.1.0.x, 7.5, 7.5.0.x
7.5
7.5.0.7
7.0, 7.0.1, 7.1, 7.1.0.x, 7.5, 7.5.0.x
Note: Support for the NetBackup 6.x product line has ended as of 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 website.
You can use the following methods to locate these lists and information:
Symantec recommends that you use Symantec Operations Readiness Tools

(SORT) to help you locate the latest platforms, peripherals, drives, and libraries.
To access SORT, go to the following URL:
14
For NetBackup, SORT provides an Installation and Upgrade Checklist report
as well as the ability to collect, analyze, and report on host configurations across
UNIX/Linux or Windows environments. In addition, you can determine in what
release whether any hot fixes or EEBs you have installed are fixed. You can
use this data to assess whether your systems are ready to install or upgrade to
this release.
If you want to view a specific compatibility list, you can find links to each list that
is posted on the Symantec Support website:
http://www.symantec.com/docs/TECH59978 - NetBackup Master Compatibility
List
The following items describe each of the compatibility lists that are available.
NetBackup Enterprise Server and Server 7.x Hardware Compatibility List

This list includes information for compatible drives, libraries, virtual tape
devices, robot-types, fibre-channel HBAs, switches, routers, bridges, iSCSI
configurations, and encryption devices. Other compatibility information
includes the following:
NetBackup appliances
AdvancedDisk arrays
OpenStorage (OST) solutions
Tape drives
Fibre Transport media server host bus adapters (HBAs)
Virtual tape libraries (VTLs)
Network Data Management Protocol (NDMP) devices
Tape libraries
Encryption and security solutions
NetBackup 7.x Database and Application Agent Compatibility List

This list contains the most current compatibility information for the database
agents and application agents that are supported on specific operating
systems and CPU architectures.
NetBackup 7.x Snapshot Client Compatibility List

This list contains the most current server and client snapshot compatibility
information sorted arrays, agents, operating systems, and VSS providers.
NetBackup 7.x Cluster Compatibility List
15
This list contains the most current compatibility information for the cluster
types and versions that are supported on specific operating systems and
CPU architectures.
Statement of support for the importing of Backup Exec images in NetBackup

7.x using the Backup Exec Tape Reader
Support for NetBackup 7.x in virtual environments

This list contains the most current compatibility information for NetBackup
in virtual environments.
16
Chapter
Operating system patches and updates

This topic provides information on the product dependencies of this release of
NetBackup. You should verify that your operating system is up-to-date with all of
the latest patches and upgrades before you install NetBackup. This section is a
guide to inform you of the operating systems that require a minimum patch level.
For more extensive information about NetBackup compatibility including compatible
operating systems, applications, and hardware, see the NetBackup Master
Compatibility List on the Symantec Support website.
Table 3-1 provides the known, minimum operating system (OS) patches and
updates. A vendor may have released a more recent patch that supersedes a patch
that is listed in this table. Symantec recommends that you visit the Support website
of that particular vendor for their latest patch information.
Table 3-1
Operating system patches and updates for NetBackup
Operating system type

and version
Patch
AIX 5.3
AIX runtime libraries 8.0.0.10 or You may need to restart after changing to version
9.0.0.3 or later
9.0.0.3.
xlC.rte 8.0.0.10 fileset
Notes
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.
Table 3-1
and version
Operating system patches and updates for NetBackup (continued)
Patch
Notes
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 SP2

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

(6100-05-02-1034) Maintenance Pack as a minimum.
(Higher patch levels should also work.)
You can use the oslevel -s command to verify
what Maintenance Pack level you have installed.
AIX runtime libraries 9.0.0.3 or

later
The runtime libraries need to be at 9.0.0.3 or later.

You may need to restart after you change to version
9.0.0.3.
HP-UX
COMPLIBS.LIBM-PS32
If you install AT on an HP-UX platform, this patch is

required.
HP-UX IA64
Networking.NET-RUN:
/usr/lib/libipv6.sl
Networking.NET-RUN-64:
/usr/lib/pa20_64/libipv6.1
/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
/usr/lib/hpux64/libipv6.so.1
/usr/lib/libipv6.1
18
Table 3-1

and version
Patch
Notes
HP-UX PA-RISC
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:
HP-UX 11.11
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.
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.
19
Table 3-1
and version
Patch
Notes
PHSS_35379

required for successful NetBackup client backups.
PHCO_29029

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 website contains information about
this patch.
http://h20565.www2.hp.com/portal/site/hpsc/public/
PHCO_35743
S700_800 11.11 libc cumulative patch

The above patch has dependency on the following
patches:
HP-UX 11.23
PHCO_31923 (critical patch): s700_800 11.11 libc

cumulative header file patch
PHKL_34805 : 700_800 11.11 JFS3.3 patch;
mmap
PHSS_37201
PHCO_33431
Symantec recommends that all customers running

11.23 install this patch. This recommendation applies
to HP PA-RISC only because HP Itanium has moved
to 11.31.
PHSS_34858

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

NetBackup requires, particularly when you attempt to
run NetBackup with NetBackup Access Control
(NBAC).
20
Table 3-1
and version
Patch
Notes
PHSS_37492
Contains fixes for the following:
HP-UX 11.31
Solaris 9 SPARC 64-bit

client
QXCR1000593919: purifyplus dumps core

in PA32
is exiting.
QXCR1000746161: dlsym() hangs
QXCR1000593999: dld emits assert messages
for chatr +mem_check enabled 64-bit
executables
PHSS_37202
QPK1131 (B.11.31.1003.347a)
patch bundle
This patch bundle is required for NetBackup media

server support. It is an HP-UX March 2010 patch
bundle.
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
Table 3-1
and version
Patch

Notes
Recommended patch set - dated Symantec recommends that you download the patch
June 2011 or newer
set dated June 2011 (or newer) from the Oracle
Support website.
https://support.oracle.com
The patch set contains the following minimum
recommended patches:
118777-17 (SunOS 5.10: Sun GigaSwift Ethernet

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

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

and version
Patch
Notes
Solaris 10 x86-64
Recommended patch set - dated Symantec recommends that you download the patch
12/28/2011 or newer
set dated 12/28/2011 (or newer) from the Oracle
Support website.
https://support.oracle.com
The patch set contains the following minimum
recommended patches:
118778-15 (SunOS 5.10_x86: Sun GigaSwift

Ethernet 1.0 driver patch)
139556-08 (Kernel patch with C++ library updates)
142395-01 (SunOS 5.10_x86: ICMP patch)
143514-02 (SunOS 5.10_x86: Data Link Admin

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

include NXGE fixes)
142910-17 (SunOS 5.10_x86: Distributed Link
Software patch)
143136-03 (SunOS 5.10_x86: Aggregation patch)
SUSE Linux Enterprise

Server 10 x64
Service Pack 2 or newer
The operating system version must be SUSE Linux

Enterprise Server 10 SP2 or newer to run NetBackup
7.0.
Windows XP x86-32
KB936357
Microsoft microcode reliability update.
Windows XP x86-64
KB928646
Hot fix for PBX connection attempt hangs.
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)
Contains the necessary updates to run Volume

Shadow Copy.
23
Table 3-1
and version
Patch
Notes
KB928646
KB883646
Microsoft Storport hot fix.
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

Windows Server 2008 (SP2) KB979612
Hot fix to improve TCP loopback latency and UDP

latency
Windows Server 2008 R2

(SP1)
KB2265716
Hot fix for when a computer randomly stops

responding.
KB982383
Hot fix for a decrease in I/O performance under a

heavy disk I/O load.
KB983544
Update for the "Modified time" file attribute of a registry

hive file.
Windows Server 2003

x86-32 (SP1 & SP2)
24
Table 3-1
and version
Patch
Notes
KB979612
Hot fix to improve TCP loopback latency and UDP

latency
25
Chapter
Operational notes
About NetBackup 7.5.0.7 operational notes
Installation and upgrade notes
General NetBackup 7.5.0.7 notes
Bare Metal Restore notes
Cloud storage notes
Database and application agent notes
Deduplication notes
NetBackup OpsCenter notes
NetBackup Search notes
Virtualization notes
About NetBackup 7.5.0.7 operational notes

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

This section contains the operational notes and known issues that are associated
with the installation and upgrades of NetBackup in this release.
If you are a NetBackup MSDP or PureDisk user, please review the following
section before you upgrade:
See About upgrading MSDP and PureDisk deduplication solutions to resolve
case sensitivity issues on page 36.
If you are a NetBackup Search user, please review the following section before
you upgrade:
See About upgrading Search to NetBackup 7.5.0.x on page 44.
After the NetBackup installer completes the upgrade to version 7.5.0.7 on a

Windows server, it may request a restart.
A restart can be required for a variety of reasons. A restart request in this
situation is most commonly the result of the upgrade to a new version of Microsoft
Visual C++ 2010 run-time DLLs that are found in NetBackup 7.5.0.7. The new
version of Visual C++ was included to correct an issue with symbolic links on
Windows platforms. For more information on the symbolic link issue, refer to
the following articles on the Microsoft Support and Symantec Support websites:
http://support.microsoft.com/kb/2889080
Note: LiveUpdate users receive a warning status if a restart is required.
To determine if a Windows server is likely to require a restart after upgrading
to NetBackup 7.5.0.7, check the version of
\SystemRoot\System32\msvcrt100.dll. If the version is lower than
10.0.40219.455, then a restart request is very likely to occur due to the Visual
C++ upgrade.
After an upgrade to Symantec NetBackup, changes to individual Object IDs in

the nblog.conf file are not preserved. However, the major default settings are
preserved.
Windows 8/Server 2012 require a special full installation package.

For all other supported platforms (including other versions of Windows),
NetBackup 7.5 must be installed before you can upgrade to version 7.5.0.x.
27
Operational notes
However, installing NetBackup on Windows 8/Server 2012 is not supported for

versions before version 7.5.0.6. To install NetBackup on Windows 8/Server
2012, you must use the special full installation package of NetBackup. This
installation package brings the client directly to 7.5.0.6 and is not meant for any
other Windows operating system.
Note: Due to technical limitations, the regular Windows Installer (both x86 and
x64) does not prevent installation on Windows 8/Server 2012, even though this
method is not supported. The only supported method of installing NetBackup
on Windows 8/Server 2012 is to use the special 7.5.0.6 x64 full installation
package.
To install NetBackup Windows client software remotely, the system must meet
certain configuration requirements. One of the requirements is that the Remote
Registry service be started on the remote system. Starting with NetBackup
7.5.0.6, the NetBackup installer can enable and start the Remote Registry service
on the remote system.
If the Remote Registry service is not started, the installation receives the following
error message:
Attempting to connect to server server_name failed
with the following error: Unable to connect to the remote
system. One possible cause for this is the absence of the
Remote Registry service. Please ensure this service is started
on the remote host and try again.

This section contains the general operational notes and known issues that are
associated with this release of NetBackup.
NetBackup is migrating to a simplified client name for Windows clients.

The new client selection Windows will be used for all supported Windows clients,
regardless of the specific Windows version of the client. In future releases,
specific Windows version choices will be eliminated. As part of this migration,
the client selection Windows may or may not appear in the client selection
menus. Please choose the new Windows menu selection for the appropriate
architecture (x86 or x64). If the Windows selection is not available, please select
the specific Windows version.
28
Operational notes
Note: If the Windows selection is not available when adding a Windows 8/Server
2012 through any of the NetBackup interfaces, choose the Windows 7 or
Windows 2008 menu selection.
A Windows multistream backup of all locals disks may fail if Microsoft Distributed
File System Replication (DFSR) is active on the client.
Workaround: Disable multistreaming for the Windows clients that have DFSR
enabled.
An issue can occur where a newly-added NetBackup appliance media server

also gets added to the EMM database as a master server. Subsequent attempts
to delete the master server entry from the EMM database using the nbemmcmd
deletehost command fail with the following error:
$ nbemmcmd -deletehost -machinename <machine_name> -machinetype
master
NBEMMCMD, Version: <NetBackup_version>
The function returned the following failure status: "Cannot
delete machine entry '<machine_name>', it has Audit entries.
Please contact Symantec support for deleting audit entries
from the database"
Extended attributes are lost when symbolic files are restored on UNIX clients.
In particular, the security context extended attributes of symbolic files are also
lost on Security-Enhanced Linux (SELinux) clients.
After performing a single file restore operation on a UNIX client, the following
error can be found under the Task Progress tab of the Backup, Archive, and
Restore interface:
08:19:05 (92.001) attr_set failed for <file_name> - Attribute
security.selinux not set. Errno = 2: No such file or directory
The error occurs when the file is a symbolic link and the target of the symbolic
link no longer exists. Despite the error, the file appears to have restored
successfully. However, the extended attributes of the symbolic link are lost. This
issue applies to both virtual clients and physical clients.
Note: If the target does exist, no error is reported and the extended attributes
will get set on the target instead of the symbolic link.
An issue can occur if a NetBackup Network Data Management Protocol (NDMP)

backup policy is configured with the directive set type=tar in the backup
29
Operational notes
selection. Parent directories in the path of a file that an incremental NDMP

backup saves may not be present in the backup image. For more information
on this issue, refer to the following tech note on the Symantec Support website:
Network Data Management Protocol (NDMP) backup performance is adversely

affected when the logging level is set to 4 or 5. The performance effect may be
serious enough to cause NDMP backup failures. Symantec recommends that
you set to the logging level to 3 or lower to avoid this issue.
NetBackup Windows Client backups fail when NetApp and CIFS shares are
configured with certain security and access privileges.
If a NetApp volume is configured with a Mixed security style and is used with
a NetApp CIFS share that does not give read access to the client user, then
client backups fail. This issue only occurs when the NetApp volume is configured
with the Mixed security style. This issue does not affect the volumes that are
configured with NTFS or UNIX styles.
A workaround for this issue is to add explicit read access on the CIFS share to
the user under which the NetBackup client service is running.
If any file named "program" exists in the root directory of the Windows system
drive, such as C:\, NetBackup does not function properly. Any such file must be
removed or renamed before NetBackup can execute command lines and process
creation options.
All session log files that are located in the sidxxx/logs directory in NetBackup
Vault have public write permission. That allows all processes to write to the log
files.
The following is the path for the logs directory on Windows and UNIX servers:
Windows:
install_path\NetBackup\vault\sessions\vault_name\sidxxx\logs\
UNIX: /usr/openv/netbackup/vault/sessions/vault_name/sidxxx/logs/
Here vault_name is the name of the vault that is used for the session and xxx
is the unique session ID.

with Bare Metal Restore in this release of NetBackup.
If the backed up file system is encrypted for RHEL, then when the system is
restored with the BMR option, the existing encryption is removed.
30
Operational notes
Cloud storage notes
When the /etc/mke2fs.conf file is restored, the restore task is shown as

partially completed on the Activity Monitor tab in the NetBackup Administration
Console. The issue occurs on RHEL6 Update 2 platforms and later, and it occurs
even though the BMR recovery of the client completes successfully. The issue
occurs because the security properties contain some incorrect settings for the
/etc/mke2fs.conf file in a BMR environment after the file is restored.
During a Bare Metal Restore, the Zeta file system (ZFS) temporary mount fails.
This issue occurs if any ZFS is not mounted or the canmount value is set to OFF
during a backup.
To restrict the disk or the disk pool, edit the Bare Metal Restore configurations.
The edits ensure that the disk is not overwritten and the data that it contains is
not erased during the restore process.
For more information on how to edit the configurations, refer to the following
sections of the Bare Metal Restore Administrator's Guide:
Managing Clients and Configurations
Client Configuration Properties
Issues may occur after BMR restore is performed on Red Hat Enterprise Linux
6.
After the completion of a BMR Linux restore task, the system may display 'Kernel
Panic' when it looks for a grub menu. The system may also go into maintenance
mode during the first restart. These issues occur because the UDEV daemon
dynamically detects devices, causing discrepancies with disk names and ordering
in various configuration files across restarts.
If you encounter this issue, please contact Symantec Technical Support and
have your support representative reference the following tech notes:
TECH201332 and TECH179048.
Cloud storage notes

with cloud storage in this release of NetBackup.
In NetBackup 7.6, you can only create or use the storage buckets that are in
the "US Standard" region. If you are using Amazon S3 cloud storage buckets
in regions other than US Standard, you may encounter failures after you upgrade
to NetBackup 7.6.
Starting with Version 7.5.0.6, NetBackup supported the creation of Amazon S3
cloud storage buckets in regions other than US Standard. However, NetBackup
7.6 cannot recognize non-US Standard buckets or use them for backups.
Symantec does not support an upgrade to NetBackup 7.6 if you continue to use
Amazon S3 cloud storage buckets that are in a region other than the US
31
Operational notes
Standard. That includes any buckets that were created outside of NetBackup,
such as with the Amazon S3 web portal.
An issue occurs where only the master server gets listed in the Cloud Storage
Server Configuration Wizard. The same issue causes the Cloud Storage to
only be visible for the master server under media server host properties.
The issue occurs when a new Windows NetBackup Administration Console
session is started or if the master server NetBackup Service Layer (NBSL)
service is restarted. The issue results from the media servers getting scanned
for cloud support when the Cloud Storage Configuration Wizard or a media
server host properties window is opened for the first time. If you have several
media servers in your environment, they may not be displayed initially.
To work around this issue, quit and exit the Cloud Storage Configuration
Wizard or media server host properties window. Wait about 2-4 minutes
(depending on how many media servers you have configured) and then reopen
the wizard or the media server host properties window. The media servers
should appear when it is reopened. If the media servers are still not listed upon
reopening the wizard, quit the wizard again and repeat the waiting period until
they appear.
When the Rackspace plug-in is used on a host running Windows Server 2008
R2 with IPv6 enabled, NetBackup may experience network connection issues.
Symantec recommends that you disable IPv6 on Windows Server 2008 R2
hosts that use the Rackspace plug-in.

with database and application agent support in this release of NetBackup.
Log backup fails with status 50 for SAP HANA

A log backup fails if a recovery job is also initiated at the same time. A recovery
job shuts down the database and log backups fail with error 50.
When a recovery job is initiated, the SAP HANA Studio forces a shutdown of
the system and the backup jobs fail. To avoid the shutdown and subsequent
backup failure, stop the system. You can then start the recovery job.
If the NetBackup bprestore log directory does not exist, a ROLLFORWARD

operation may fail for DB2 version 10 and newer.
If you use the USEREXIT program to protect the DB2 archive logs and attempt
to perform a restore and a ROLLFORWARD operation, the roll-forward may fail.
Workaround: Manually create the NetBackup bprestore log directory
(/usr/openv/netbackup/logs/bprestore).
32
Operational notes
For Exchange GRT operations, the granular proxy host must be installed on a
version of Windows that is supported for that version of Exchange. For example,
for Exchange 2010, the granular proxy host must be installed on Windows 2008
SP2 or R2 or on Windows 2012.
For more information, see the NetBackup Database and Application Agent
Compatibility List at the following location:
Database configuration parameters USEREXIT and LOGRETAIN have been

deprecated and are no longer valid in DB2 10.1 and later. Instead, LOGARCHMETH1
sets the user exit program settings.
For the VMware backups that protect SQL Server, note the following:
A SQL Server database name cannot contain any of the following characters:
?*\"
To use Replication Director to manage your VMware snapshots and snapshot

replication with SQL Server 2012, logon account changes may be required.
Logon accounts for the NetBackup Client Service must have access to the
CIFS shares that are created on the NetApp disk array.
Change the logon account for the NetBackup Legacy Network Service to an
account that has the fixed server role sysadmin.
For SQL 2012 on Windows Server 2008/2012, the account that runs the
Microsoft SQL Server Service must have full permissions for the NetBackup
Legacy Network Service temp directory. This directory is
C:\Users\user\AppData\Local\Temp, where User is the account that runs
the NetBackup Legacy Network Service.
For Hitachi and IBM HANA appliances, you need to add an extra lib:
libelf.so.0. Refer to the NetBackup for SAP Administrator's Guide for further
details.
Backups for SAP HANA can be initiated from NetBackup. Restores are initiated
from the SAP HANA Studio. For more information, see the following tech note
on the Symantec Support website:
Since SharePoint metadata is stored outside of the content database, it cannot

be restored using Granular Recovery Technology (GRT). You can, however,
use GRT to restore SharePoint data with metadata attached to it. As long as
the metadata resides in the same service application, SharePoint maintains the
link between the two items.
NetBackup does not support restoring mailbox items into tenant mailboxes in a
multi-tenant Exchange environment. To recover items pertaining to a tenant
33
Operational notes
mailbox, redirect the recovery to a non-tenant mailbox. Backup and recovery of

Exchange Server databases are fully supported in a multi-tenant environment.
NetBackup does not support Granular Recovery Technology (GRT) with Microsoft
SharePoint Server backups in a multi-tenant SharePoint environment. Backup
and recovery of SharePoint Server databases are fully supported in such an
environment.
The NetBackup for Exchange and NetBackup for SharePoint Agents support a
restore to the same Microsoft service pack (SP) or cumulative update (CU) on
which the backup was originally created. Microsoft sometimes introduces
database schema changes in SPs or CUs. If you restore to a different SP or CU
level, the database server may not operate correctly.
Creating a minimal NetBackup account for Exchange operations

(Exchange 2010 and 2013)
This procedure describes how to create a minimal account for NetBackup Exchange
operations for Exchange 2010 and later. This account is used for the Exchange
credentials in the Exchange client host properties, enabling NetBackup to perform
operations with Granular Recovery Technology (GRT).
Note the following:
Configure each Exchange mailbox server and the CAS server.
Configure each client that performs granular operations. To determine which

clients to configure, see the following topic:
In a cluster environment, perform the steps on each database node in the cluster.
For an Exchange DAG, perform the steps on each database node in the DAG
and the CAS server.
To create a minimal NetBackup account for Exchange 2010 and 2013 operations
In the Exchange Management Console, create a new Exchange mailbox for

NetBackup.
This process creates a new user that is automatically a domain user. This
procedure refers to that user as NetBackupUser.
Double-click on the user account you created.
Select the Member Of tab.
Click Add and add this user to the Administrators group.
34
Operational notes
Deduplication notes
35
Create a new Role Group, make the account a member of this group, and
assign roles. Use the Exchange Management Shell to run the following
commands:
Note: If the account does not have the necessary privileges, an administrator
needs to perform these tasks.
New-RoleGroup -Name NetBackupRoles -Roles @("Database Copies", "Databases",

"Exchange Servers", "Monitoring", "Mail Recipient Creation", "Mail Recipients",
"Recipient Policies"
Add-RoleGroupMember -Identity NetBackupRoles -Member NetBackupUser
Where NetBackupUser is the name of the Active Directory account you created
in 1.
(Exchange 2010) To perform restores with Granular Recovery Technology

(GRT), also run the following commands with the Exchange Management shell:
New-ManagementRole -Name SymantecEWSImpersonationRole -Parent ApplicationImpersonation

New-ManagementRoleAssignment -Role SymantecEWSImpersonationRole -User NetBackupUser
-Name "NetBackupUser-EWSImpersonation"
New-ThrottlingPolicy -Name "SymantecEWSRestoreThrottlingPolicy" -EWSPercentTimeInCAS
$null -EWSPercentTimeInAD $null -EWSMaxConcurrency $null -EWSPercentTimeInMailboxRPC
$null -PowerShellMaxConcurrency $null
Set-Mailbox -Identity NetBackupUser -ThrottlingPolicy "SymantecEWSRestoreThrottlingPolicy"
Configure the NetBackup Client Service to run as this account.

See the NetBackup for Exchange Administrators Guide.
Deduplication notes
with NetBackup deduplication features (such as MSDP and PureDisk) in this release.
Seeding the fingerprint cache for MSDP
To ensure that NetBackup uses the seeded backup images, the first backup of
a client after you configure seeding must be a full backup with a single stream.
Specifically, the following two conditions must be met in the backup policy:
Operational notes
Deduplication notes
The Attributes tab Allow multiple data streams attribute must be

unchecked.
The backup selection cannot include any NEW_STREAM directives.
If these two conditions are not met, NetBackup may use multiple streams. If the
Attributes tab Limit jobs per policy is set to a number less than the total
number of streams, only those streams use the seeded images to populate the
cache. Any streams that are greater than the Limit jobs per policy value do
not benefit from seeding, and their cache hit rates may be close to 0%. After
the first backup, you can restore the original backup policy parameter settings.
For more information about seeding, see the following Symantec tech note:
About upgrading MSDP and PureDisk deduplication solutions to

resolve case sensitivity issues
Note: If all of your NetBackup media servers are running Windows, and you do not
plan to add UNIX servers running MSDP, you may safely ignore the rest of this
topic.
This section applies to the following deduplication solutions:
NetBackup Media Server Deduplication Option (master server, media server,

client, or VMware backup host)
NetBackup appliance deduplication (master server, media server, or VMware

backup host)
PureDisk deduplication
PureDisk appliance deduplication
In versions before NetBackup 7.5.0.6, a problem can occur where NetBackup cannot
read an image that is stored on an MSDP or PureDisk storage unit. The issue results
from inconsistencies in how entries are written and read in the deduplication
database on case-sensitive file systems. The types of operations that might exhibit
failure due to a read error that is associated with this issue include verify, restore,
duplication, and replication. For MSDP, the issue is fixed starting in NetBackup
7.5.0.6 (appliance 2.5.3). For PureDisk, the issue is fixed starting in Version 6.6.5
(appliance 1.4.4).
36
Operational notes
Deduplication notes
Table 4-1
Examples of the failed operations that can result from the case
sensitivity issue
Operation
Activity Monitor
status
Activity Monitor
job details
Status in bpdm and

bptm log files
Verify
(191) no images
successfully
processed
image open failed:

sts_open_image
error 2060018: file not failed: error 2060018
found
Restore
(83) media open error Image open failed:

sts_open_image
found
Duplication (MSDP
source)

sts_open_image
found
Replication (MSDP
source)
(83) media open error get image properties rpl_add_image_set:

failed: error 2060013: rpl_get_image_info()
no more entries
failed, error 2060013
Duplication (PDDO
source)

sts_open_image
found
Replication (PDDO
source)
(83) media open error get image properties rpl_add_image_set:

failed: error 2060013: rpl_get_image_info()
no more entries
failed, error 2060013
Example scenarios of the client name case sensitivity issue

The following list contains two examples of scenarios in which the client name case
sensitivity issue can occur. These example scenarios are intended to assist you in
understanding how the issue can manifest in a NetBackup environment. There may
be more scenarios in which this issue can occur.
Example 1
Suppose that there is a NetBackup client named my_client running a version
of NetBackup previous to Version 7.5.0.6 and that there is a corresponding
policy named my_policy. Suppose also that my_client performs client-side
deduplication to a UNIX-based MSDP or PureDisk storage unit. Next, suppose
that the following steps occur:
37
Operational notes
Deduplication notes
A successful backup for my_policy is made to an MSDP or PureDisk storage

unit.
The name of the client in the policy my_policy is changed from my_client to
MY_CLIENT.
Another successful backup for my_policy is made to an MSDP or PureDisk

storage unit.
The data for both backups is saved. However, the operations that attempt to
read the data from the second backup fail if the deduplication engine is on a
case-sensitive file system. The failures occur because the deduplication database
entry my_client differs from MY_CLIENT and the previous version of the
NetBackup client writes incorrect deduplication database entries. The issues in
this specific example can be resolved by upgrading the client to NetBackup
7.5.0.6 or newer.
Example 2
Suppose that there is a UNIX media server running NetBackup 7.5.0.6 or later
called media_A that is attached to an MSDP storage unit. Suppose also that
there is another media server called media_B running Windows and a version
of NetBackup that is older than Version 7.5.0.6. In this example, media_B has
the credentials that allow it to access the MSDP disk pool MSDP_POOL on media_A.
Suppose that a policy named my_policy was created for a client named
my_client (such as in the first example) and the following events occur:
1
A successful backup of my_policy for my_client is made to MSDP_POOL.
The policy my_policy is copied to MY_POLICY.
The name of the client in the policy MY_POLICY is changed from my_client to
MY_CLIENT.
A backup of MY_POLICY is successful to MSDP_POOL.
In this example, the backups are saved and media_A can read them. However,
one or more of the backup images cannot be read from MSDP_POOL by media_B
because media_B suffers from the name case sensitivity issue. In this situation,
the issue occurs whenever the master server selects media_B as the server to
perform the read operations on MSDP_POOL.
This particular manifestation of the issue can be diagnosed using the following
methods:
Use the bpimagelist command to verify that the images were stored on the
desired MSDP disk pool.
38
Operational notes
Deduplication notes
Look for the following in the granted resource line in the Activity Monitor
job details for the failed job:
The host that is listed as the storage server is running NetBackup 7.5.0.6 or
newer.
The host that is listed as the media server is running a version of NetBackup
that is older than Version 7.5.0.6.
The issues in this specific example can be avoided by upgrading all of your media
servers to NetBackup 7.5.0.6 or newer.
Determining the servers and clients that can encounter the

issue
The case-sensitivity issue can occur if your environment performs any of the
following MSDP functions on UNIX operating systems that run on NetBackup media
servers or PureDisk servers (including NetBackup appliances and PureDisk
appliances).
1.
Media server deduplication to attached storage
2.
Media server deduplication to another media server
3.
Media server deduplication to a PureDisk server
4.
Media servers for optimized MSDP duplication within the same domain
5.
Client-side deduplication to a media server
6.
Client-side deduplication to a PureDisk server
Note: All of the listed operations apply to the VMware backup hosts that run the
deduplication engine.
All of the listed operations also apply to the master servers that function as media
servers and run the deduplication engine.
Symantec recommends that you upgrade all of the servers, clients, and VMware
backup hosts in your environment that are involved in the listed operations. That
includes any media server that uses credentials for an affected MSDP storage unit.
Starting with NetBackup 7.5.0.6 (appliance 2.5.3) and PureDisk 6.6.5 (appliance
1.4.4), writing to the deduplication database has been updated to fix the issue. The
database writes are fixed so that a change in the case of the characters that are
used for the NetBackup client name and policy do not cause a read of the backup
images to fail. If you do not upgrade to these minimum versions, there is a possibility
that you may encounter read errors with future backup images due to this issue.
39
Operational notes
Note: Consistent with NetBackup upgrade policy your media servers and clients
must be running a minimum of NetBackup 7.5 before you can attempt to upgrade
to 7.5.0.x.
Fixing the name case sensitivity issues that exist in the MSDP
and PureDisk databases
If you have already encountered image read failures due to client name or policy
name case sensitivity issues, your first step should be to upgrade the affected hosts
to NetBackup 7.5.0.6 or newer. After the upgrade, the name case issue still affects
the images that were created before the upgrade by versions of NetBackup previous
to Version 7.5.0.6. Use the following table to select the correct approach to repair
client and policy name case sensitivity issues with existing NetBackup images.
Table 4-2
Problematic name type
Storage unit type
Required action
Client
MSDP
Repair the MSDP database
Client
PureDisk
Repair the PureDisk database
Policy
MSDP
Contact Symantec Technical

Support
Policy
PureDisk
Contact Symantec Technical

Support
Special procedures to repair an MSDP database or a PureDisk database are

available on the Symantec Support website at the following URL:

with NetBackup OpsCenter in this release.
Uninstalling OpsCenter software may not completely uninstall maintenance

releases on Windows. OpsCenter maintenance releases may still be visible in
the Windows system program uninstaller.
For more information and workaround instructions for this issue, see the following
tech note on the Symantec Support website:
Issues can occur if OpsCenter is installed in a non-default location on Windows

systems because of the Windows maximum path length limitation. If the install
40
Operational notes
directory causes OpsCenter to exceed the character limit, unpredictable behavior

may occur after installation or upgrade. For example, the OpsCenter interface
may fail to load after an upgrade to Version 7.5.0.x.
A cloud metering data collection failure can occur if one or more media servers
with credentials to access a cloud storage server (data movers) is unreachable
for some reason.
Workaround: From the unreachable media server, use tpconfig to remove the
credentials of that media from all cloud storage servers on the master. Cloud
metering data collection should then succeed. All the cloud metering data from
the media servers that were missed earlier can now be collected.
Uninstalling OpsCenter 7.5.0.6 may take a long time on the HP-UX.

In certain scenarios, OpsCenter 7.5.0.6 on HP-UX may take several minutes to
uninstall. Do not interrupt the uninstallation process.
The Monitor > Alerts List View does not show alerts in certain scenarios.
Under the Monitor > Alerts List View, if you sort the alerts by Alert Policy or
Severity, the existing alerts are not displayed on the page.
To work around the issue, remove the Alert Policy or Severity columns from
sorting. You can then view the existing alerts appropriately under the Monitor
> Alerts List View.
To remove a column from sorting, do the following:
1
Go to the Monitor > Alerts List View and click Change Table Settings.
On the Table Settings pop-up screen, clear the sorting that you may have applied
to the Alert Policy and Severity columns.
Select the corresponding check box.
Modify the selection for the Sort drop-down list. The Up or Down options should
not be selected for these columns.
Click Ok.
The Monitor > Overview page does not display a NetBackup master server
appropriately if it is a virtual machine.
The following is an example scenario of the issue:
41
Operational notes
Install a NetBackup master server that is a virtual machine and that contains virtual
machine data.
Install OpsCenter Server.
In the OpsCenter interface, add the same master server with its host name as a
display name.
Go to the Monitor > Overview page. It displays the display name of the virtual
machine on which the master server is installed instead of the master server display
name.
In certain scenarios, duplicate entries of a client are displayed on the Monitor

and Views interfaces.
This issue is seen in any of the following scenarios:
A NetBackup master server is used as a client in one or more policies.
Some NetBackup policies refer to a NetBackup master server with a fully

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

policies, duplicate entries of this client are displayed on the following OpsCenter
screens:
Monitor > Host > Client
Settings > Views > Manage Nodes and Objects > Objects not in selected
view
NetBackup 7.5.x.x can only be installed on a system that is running NetBackup

7.5. However, if you upgrade to NetBackup 7.5 from a previous version, such
as 7.1, the upgrade might fail with the following error message:
No primary key value for foreign key
'FK_JOB_REF_MEDIA_SERVER_ARCHIVE' in table 'domain_JobArchive
If you encounter this error, please contact Symantec Technical Support before
you try to re-attempt the upgrade process.
Custom tabular reports may not display all jobs if the Media Barcode field is
selected. If you encounter this issue, please contact Symantec Technical Support
for assistance.
42
Operational notes
To run a Capacity Licensing report in NetBackup 7.5.0.7, a user name and

password is required for each master server. To successfully run a report for
any master servers that were added to OpsCenter in versions previous to 7.5.0.5,
an extra step is required. The user name and password credentials for each
master server must be entered manually in the NetBackup configuration settings.
If the credentials are not added in the configuration settings, a user name and
password error is returned when the report is run.
Additionally, for Capacity Licensing to work correctly, please refer to the following
tech note and install the specified EEBs:
Policy view is not applicable for Restore type jobs.

If you select the policy view when you create any job-related alert policy,
OpsCenter does not generate alerts for restore jobs. Since restore jobs do not
have a policy associated with them, they never raise alerts for policy view.
If an OpenStorage alert policy is configured, then OpsCenter generates an alert

(email) for each volume.
To work around this issue, you can filter the volume type alert by specifying the
text (for example: With volume name, not protected for any volume, and as
required) in the field that is provided for the Event message contains word(s)
selection. OpsCenter generates the alert only when the NTAP event contains
the text that is specified in Event message contains word(s) selection.
When an OpsCenter user is deleted, the following user-specific data is also

deleted along with views, report schedules, and so on:
All data collectors that the user has created
All data collectors that the user has modified, irrespective of who created
them
Because of this behavior, there may be data collection failure as a result of user
deletion.
The following scenario explains the issue in detail:
User A creates Data Collector D1 to collect data from NetBackup master server
M1. User B modifies D1. The OpsCenter Admin deletes User B. As a result of
this user deletion, D1 is also deleted because User B had modified it. Therefore,
data collection fails and User A cannot collect any data from M1.
On 64-bit Windows, if language packs are installed on top of a 7.1.0.x or a 7.5.0.x

installation, an upgrade to a later version may fail. For example, if you upgrade
OpsCenter 7.5 to 7.5.0.4 and install all language packs on top of 7.5.0.4, an
upgrade to 7.5.0.5 may fail.
To work around the issue, manually uninstall all language packs before the
upgrade, and then reinstall them after the upgrade.
43
Operational notes
In the Simplified File Restore (SFR) Timeline View, for the images that are
collected in OpsCenter, the data format is shown as unknown because of the
lack of data.
OpsCenter job collection from master servers could fail if port 1556 is not opened
bi-directionally on both the NetBackup and OpsCenter sides.

with NetBackup Search in this release.
Restore jobs may fail when the nbholdrestorehelper utility is used to restore
held data. The issue occurs when the Policy type of a backup policy does not
match the Policy type attributed to the backup in the NetBackup catalog.
Workaround: Edit the <client_name>_restore.bat file that was created by the
nbholdrestorehelper utility and specify the policy type for the bprestore.exe
command, then run that batch file.
Note: The policy type option for the bprestore command should match the
policy type attribute that was set when the policy was created.
About upgrading Search to NetBackup 7.5.0.x

NetBackup Search users must follow a special procedure to upgrade from
NetBackup 7.5 to any NetBackup 7.5.0.x maintenance release (for example, Version
7.5.0.6). This procedure also applies to upgrading between NetBackup 7.5
maintenance releases (for example, upgrades between Version 7.5.0.3 and Version
7.5.0.6). Symantec recommends that all NetBackup Search users review this
procedure before they upgrade to a new release.
The NetBackup Search upgrade procedure can be found on the Symantec Support
website at the following link:
with virtualization technologies in this release of NetBackup.
For a snapshot that quiesces an application on a Windows 2008 or later VM,

VMware VDDK 5.1 imposes the following disk requirements:
44
Operational notes
The VM's disks must be SCSI, not IDE.
The SCSI disks on the VMs SCSI controller must not occupy more than half
of the total number of slots in the controller. Since the controller has a total
of 15 slots, the number of disks in that controller must not exceed 7.
If these conditions are not met and the NetBackup VMware policy enables the
Virtual machine quiesce option, the backup may fail with status code 156.
For more information on this VMware requirement, refer to the following article
in the VMware vSphere 5.1 Documentation Center:
Working with Microsoft Shadow Copy
Starting with NetBackup 7.5.0.7, the SYMCquiesce utility (SYMCquiesce.iso)

is included in NetBackup for Linux. However, the utility is not included in the 7.6
GA release of NetBackup for Linux and is removed during an upgrade from
version 7.5.0.7. To keep this utility for NetBackup 7.6 GA, make a copy and
store it in a safe place before upgrade. Otherwise you can retrieve the file from
a Windows computer running NetBackup, or a Linux computer running
NetBackup 7.5.0.7.
The SYMCquiesce.iso file is located in the following locations:
Windows
\NetBackup\bin\goodies\vmware-quiesce
Linux
/usr/openv/netbackup/bin/goodies/vmware-quiesce
Warning: Multiple versions of SYMCquiesce.iso may exist in these directories

with names such as SYMCquiesce.1.0.0-001.iso. Unless otherwise specified
in the NetBackup documentation, only install SYMCquiesce.iso. Do not install
SYMCquiesce.1.0.0-001.iso.
For more information about the SYMCquiesce utility, refer to the NetBackup for
VMware Administrator's Guide, available at the following website:
For Linux VMs without persistent device naming, multiple disk controllers (such
as IDE, SCSI, and SATA) may complicate the recovery of individual files. This
issue occurs because non-persistent device naming, such as /dev/sda and
/dev/sdb, may cause unexpected mount point changes after a restart. If the
VM has a SCSI disk and a SATA disk, the Backup, Archive, and Restore interface
may show incorrect mount points for the VM's files. For example, the files
originally under /vol_a might appear under /vol_b when you browse to restore
them. The restore is successful, but the restored files may not be in their original
directories.
45
Operational notes
46
As a workaround, search for the files on the restored VM and move them to the
proper locations.
To prevent this issue on Linux VMs with multiple disk controllers, Symantec
recommends a persistent device-naming method for mounting the file systems.
When persistent naming is in place, device mounting is consistent and this issue
does not occur when you restore files from future backups.
For persistent device naming, you can mount devices by UUIDs. The following
is an example of the /etc/fstab file that contains devices that are mounted
with UUIDs:
UUID=93a21fe4-4c55-4e5a-8124-1e2e1460fece /boot
UUID=55a24fe3-4c55-4e6a-8124-1e2e1460fadf /vola
ext4
ext3
defaults
defaults
To find the device UUIDs, you can use either of the following commands:
blkid
ls -l /dev/disk/by-uuid/
Note: NetBackup also supports the by-LABEL method for persistent device
naming.
An issue can occur for the virtual machines that are configured with a logical
volume (LVM or LDM). A backup with the Enable file recovery from VM backup
option fails if the volume disk set contains a mixture of disk types, as follows:
Some of the disks in the logical volume set are regular virtual disks (normal
VMDKs), and
Some of the disks in the same volume set are independent disks or are
physical disks in raw device mapping mode (RDM).
In this case, the backup job returns status 6 "the backup failed to back up the
requested files". The VxMS log contains the message "bitmap read failed".
Note: On the VMware backup host, the VxMS log is in the following directory:
Windows
install_path\NetBackup\logs\vxms
UNIX
/usr/openv/netbackup/logs/vxms
For information about configuring VxMS logging, see the NetBackup for VMware
Administrator's Guide, available from the following location:
Workaround: Make sure that the following optimization options in the policy are
disabled:
Operational notes
Enable file recovery from VM backup
Exclude deleted blocks
Exclude swap and paging files
VMware has identified a VDDK issue that can prevent the restore of a
thin-provisioned disk that resides on local storage. When you attempt to restore
the VM, the restore job fails in the following case:
Neither nbd nor nbdssl is selected as the transport mode for the restore,
The VM that you want to restore has a thin-provisioned disk, and
The disk is on a directly attached device (not on a networked device, SAN

device, or iSCSI device).
To restore the VM, select nbd or nbdssl as the transport mode on the Recovery
Options dialog in the NetBackup Backup, Archive, and Restore interface.
For additional detail on this issue, see VixDiskLib should check SAN accessibility
on disk open in the VMware VDDK 5.1 release notes:
http://www.vmware.com/support/developer/vddk/VDDK-510-ReleaseNotes.html
In NetBackup 7.5.0.5 and later, when you use the NetBackup Administration
Console to delete the credentials definition for a VMware server, the VMware
host is automatically removed from the NetBackup Enterprise Media Manager
(EMM) database. Under "Changing the host name of a VMware server in
NetBackup," the 7.5 and 7.6 versions of the NetBackup for VMware
Administrators Guide incorrectly state that you must remove the VMware host
manually by means of the nbemmcmd command.
After the NetBackup-Java interfaces are upgraded to version 7.5.0.7, the Backup,
Archive, and Restore interface may fail to show VMware vCenter servers during
an alternate location restore when the master server is at a lower version than
7.5.0.7.
For more information about this issue, see the following tech note on the
Symantec Support website:
For backup hosts with limited memory, simultaneous backups of VMware VMs
may fail due to lack of memory. The bpbkar log contains a message that includes
the phrase failed to allocate.
Reschedule the backups so they do not occur at the same time, or add more
memory to the backup host.
In rare instances, the NetBackup bpbkar process may core dump (although
backups complete successfully). If the VMware backup host is configured for
core dump generation, the dump files may occupy too much space and affect
performance.
47
Operational notes
As a workaround, delete the core files or disable core-dump generation.

For more information on this VMware issue, see Threads still running after
VixDiskLib_Exit call in the VMware VDDK 5.1.1 release notes:
http://www.vmware.com/support/developer/vddk/vddk-511-releasenotes.html
The following features are not supported for dual boot virtual machine
configurations:
Enable file recovery from VM backup
Optimizations:
Exclude deleted blocks
Exclude swapping and paging files
Exclude boot disk
Exclude data disks
A restore of a VM with the hotadd transport mode or the SAN transport mode
may not succeed if the VMs disk geometry in the backup image differs from the
VMs default values. VM disk geometry refers to the layout of the virtual disk
(cylinders, heads, sectors) as specified in the vmdk file.
The NetBackup restore job reports partial success with status code 1 (the
requested operation was partially successful). For more information about this
issue and available workarounds, see the following tech note on the Symantec
Support website:
Note: The restored VM may not be able to start. VMware has documented the
cause of this issue in their VDDK 5.1 release notes, under Known Issues and
Workarounds: "Metadata write is not supported for HotAdd and SAN transport."
http://www.vmware.com/support/developer/vddk/VDDK-510-ReleaseNotes.html
For a VMware backup host on Linux: If the master server is on a separate host
(not on the same Linux backup host), the master server must be at NetBackup
7.5.0.1 or later.
If a single recovery host performs multiple, simultaneous restores of the same

VM backup image, some of the restored VMs may fail to power on. For example:
host rec27.acme.com runs three restores of the same backup of VM
prodvm3.acme.com, and the restore jobs occur at the same time or partially
overlap. In this case, an error similar to the following displays in the vSphere
Client:
48
Operational notes
49
An unexpected error was received from the ESX host while powering
on VM vm-xxxx.
Reason: The parent virtual disk has been modified since the child
was created.
Cannot open the disk
'/vmfs/volumes/4c3e6336-c5f64960-425c-d8d385b02700/xxxxx/yyyyy.vmdk'
or one of the snapshot disks it depends on.
To work around the issue, restore the virtual machine image sequentially: Let
each restore complete before the next restore begins. If simultaneous or
overlapping restores of the same VM backup image are required, use a different
recovery host for each restore.
With VMware VDDK 5.1, backups that use the hotadd or SAN transport modes
do not include the VM's metadata changes in the backup. The status log of the
NetBackup job contains messages similar to the following:
07/25/2013 12:37:29 - Info tar (pid=16257) INF - Transport Type
= hotadd
07/25/2013 12:42:41 - Warning bpbrm (pid=20895) from client
<client_address>: WRN - Cannot set metadata (key:geometry.
biosSectors, value:62) when using san or hotadd transport.
As a workaround, retry the backup with a different transport mode (nbd or

nbdssl).
This problem is a known VMware issue. For more details, refer to the VMware
VDDK 5.1 release notes at the following URL:
http://www.vmware.com/support/developer/vddk/VDDK-510
-ReleaseNotes.html#knownissues
VMware has identified an issue in ESXi server 5.1 that affects application-level
quiesced snapshots for incremental backups. This issue affects VMware VMs
that run Windows Server 2003, 2008, 2008 R2, and 2012. The changed block
tracking system overstates the amount of the changed data, creating a larger
backup than necessary. As a result, incremental backups may take longer than
expected and may not complete within the backup window. This issue affects
NetBackup for VMware incremental backups.
To fix this problem, update your ESXi 5.1 servers with the ESXi 5.1 Patch 02
that is described in the following VMware knowledge base article:
http://kb.vmware.com/selfservice/microsites/search.do?language
=en_US&cmd=displayKC&externalId=2052143
The following VMware VDDK 5.1 release notes article contains more information
on this issue. See under With application level quiescing, Changed Block
Tracking overstates changes:
Operational notes
http://www.vmware.com/support/developer/vddk/VDDK-510
-ReleaseNotes.html#knownissues
NetBackup for VMware does not support any display names that end in a period
character (.). If the policy's "Primary VM identifier" option is "VM display name,"
any VM with a period at the end of the name is not backed up.
A restore of the virtual machine can fail with status code 220 (database system
error) if all of the following are true of the backup:
The backup was run from an incremental schedule and Enable block-level
incremental backup was enabled on the policy VMware tab.
Enable file recovery from VM backup was disabled on the policy VMware
tab.
At the time of the incremental backup, the data in the VM had not changed
since the previous backup.
To work around this issue, restore from the full image rather than the incremental
image. Because there is no change of data since the full backup, a restore from
the full image is exactly the same as a restore from the incremental backup.
The VMware policy Advanced Attributes dialog has a setting that is called
Virtual disk selection that has options for excluding the boot disk or data disks
from the backup. To use either of the exclude disk options before version 7.5.0.6,
NetBackup required that the full swap file reside on the boot disk. The swap file
is the Windows pagefile.sys file or the Linux swap partition. This restriction
has been lifted in 7.5.0.6. For either of the exclude disk options, the swap file
no longer needs to reside on the boot disk.
For a Linux virtual machine backup that requires file mapping, the name of an
LVM volume can include any of the following special characters:
. (period)
_ (underscore)
- (hyphen)
No other special characters are supported. If other special characters are used
in the volume name, the Enable file recovery from VM backup policy option
does not work. As a result, you cannot restore individual files from that volume.
Hyper-V notes
NetBackup for Hyper-V does not support the ampersand character (&) in the
name of the virtual disk file (.vhd). If the name of the virtual machines vhd file
contains &, the backup fails with status code 6.
To work around this issue, remove the & from the .vhd file name and rerun
the backup.
50
Operational notes
51
Starting with NetBackup 7.5.0.6, you can restore a virtual machine to Hyper-V
2012 even if the virtual machine resided on a Hyper-V 2008 R2 server when it
was backed up. However, to connect to the restored virtual machine, you may
have to modify the virtual machines network adapter by selecting the correct
virtual switch.
This issue results from changes to the virtual machine XML configuration in
Hyper-V 2012.
Note: Restoring the virtual machine to Hyper-V 2008 R2 does not have this
issue.
An issue exists where you cannot add a Red Hat Enterprise Linux 6.4 VM as a
client to a Hyper-V policy by its host name. To solve this issue, you need to
install all the necessary OS updates that are detailed in Red Hat Bug 883306
(https://bugzilla.redhat.com/show_bug.cgi?id=883306). You can also work
around this issue by adding the VM as a client to the policy using either the VM
display name or UUID.
Backup of virtual machines within Cluster Shared Volumes (CSV) is supported.

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

Symantec is committed to providing the best possible data protection experience
for the widest variety of platforms, operating systems, databases, applications, and
hardware. Symantec continuously reviews NetBackup's support of these items.
This review ensures that the proper balance is made between maintaining support
for existing versions of products, while also introducing new support for the following:
General Availability releases
Latest versions of new software and hardware
New NetBackup features and functionality
While Symantec continually adds support for new features, platforms, and
applications, it may be necessary to improve, replace, or remove certain support
in NetBackup. These support actions may affect older and lesser-used features
and functionality. The affected features and functionality may include support for
software, OS, databases, applications, hardware, and 3rd-party product integration.
Other affected items may include the products that are no longer supported or
nearing their end-of-support life with their manufacturer.
Symantec provides advanced notification to better help its customers to plan for
upcoming changes to the support status of the various features in NetBackup.
Symantec intends to list older product functionality, features, hardware, OS, and
the 3rd-party software products that are no longer supported in the next release of
NetBackup. Symantec makes these support listings available as soon as possible
with a minimum of six months where feasible before major releases.
End-of-life notifications
Much of this support information is available through the NetBackup Symantec

Operations Readiness Tools (SORT) home page widget NetBackup Future Platform
and Feature Plans. Also, included in the widget are the list of platforms, databases,
and applications that are not supported in a given release. You can access SORT
at the following URL:
Another SORT resource is to provide users with End of Life (EOL) and
End-of-Support Life (EOSL) information for NetBackup licensed software.
NetBackup EOL information can be found at the following URL:

https://sort.symantec.com/nbufutureplans
To view NetBackup EOSL information, go to https://sort.symantec.com/netbackup

and navigate to Support > Related Links. Click on the link to End of Assisted
Support information. Alternatively, you can follow the direct link to
https://sort.symantec.com/eosl.
Other information about what is compatible with NetBackup can be found in the
various compatibility lists that are listed in the NetBackup Master Compatibility List.
53
Appendix
About the NetBackup

7.5.0.7 release content
This appendix includes the following topics:
About NetBackup release content
NetBackup 7.5.0.7 release content
NetBackup 7.5.0.7 Emergency Engineering Binary (EEB) listing
About NetBackup release content

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

The following list describes the conventions used in the subsections that follow this
section. Each item listed in the release content subsection describes a feature,
enhancement, or fixed issue contained in this release:
Etrack Incident
Notes the Etrack number that targets this release.
Associated Primary Etrack
About the NetBackup 7.5.0.7 release content

An additional Etrack number that exists in the incident hierarchy.
Associated Service Request Etrack

The Etrack that is associated with the customer support service request.
Description
Describes a particular issue that has been fixed in this release, as well as
additional notes or workarounds. Workarounds can be used instead of applying
the patch, however, Symantec recommends the "best practice" of being at the
latest available patch level.
**Description or **Etrack number

Describes a critical issue or an issue that can lead to a potential data loss that
has been fixed in this release. Please read these issue descriptions carefully.
In some cases, a Tech Alert link is provided.
About current release content Etracks

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

This section contains a list of known issues that were fixed and that are now included
in this release of NetBackup.
Etrack Incident: 3092686
Associated Primary Etrack: N/A
Associated Service Request Etrack(s): N/A
Description:
An administrator could not list the images that have StorageServiceName set
to some SLP, but StorageServiceState set to 0 (NOT_MANAGED). As a result,
the administrator was not able to delete the SLP.
Description:
The NetBackup Backup, Archive, and Restore interface displayed an incorrect
modified date for a Lotus Notes data folder.
55

Associated Primary Etrack: 3142944
Associated Service Request Etrack(s): 3142918
Description:
If the backup IDs in the track log were wrong (for example, the index is invalid),
the client would continue until the server side failed. Now the client automatically
determines whether to back up successfully with the affected optimization, or
fail immediately and rename the track log name.
Description:
The Success Rate Line report did not include the current day's job information.
Description:
NDMP restores created endless read_data: waited for empty buffer
messages in the NetBackup tape management process (bptm) log. This issue
caused the Activity Monitor to freeze.
Description:
The import of images that are replicated using Auto Image Replication could
encounter an issue. The import would never happen when users configured an
MSDP storage server as an Auto Image Replication target and that storage
server also had a machine alias configured. The machine alias would not properly
resolve.
Description:
56

If a logical volume manager (LVM) disk has a master boot record (MBR)
signature, the backup fails with status 6 and status 11. However, those error
messages did not convey that the backup was unsuccessful due to a
misconfiguration. Added a clearer error message if the disk is LVM and has an
MBR signature.
Description:
If any inode is corrupted in the Windows OS, then there is a chance that there
is no attribute present in the Master File Table (MFT) index. Now if there is no
attribute present in any MFT index, then VxMS should return the error for that
particular index. VxMS bypasses that particular MFT index.
Description:
Upgraded Microsoft Visual C++ 2010 run-time DLLs. The new version of Visual
C++ was included to correct an issue with symbolic links on Windows platforms.
For more information on the symbolic link issue, refer to the following article on
the Microsoft Support website: http://support.microsoft.com/kb/2889080
Description:
In the NetBackup Java Administration Console List of Media image output list,
the encryption key tag indicated 0 even if the backup images were collected
with the Key Management Service (KMS).
Description:
Sorting by Client Name was not available for Week at a Glance reports in
NetBackup OpsCenter 7.5.0.6.
57

NetBackup 7.5.0.7 Emergency Engineering Binary

(EEB) listing
The following table contains the known issues that were identified, fixed, and
available to customers in the form of an EEB. NetBackup 7.5.0.7 resolves the
addressed issues in each of these EEBs. Additional EEBs may have been released
since this document was posted. For more information on the Etracks that are listed
in this section, or any other service request Etrack, Symantec recommends that
you use Symantec Operations Readiness Tools (SORT). To access SORT, go to
the following webpage:
Alternatively, if you do not see an EEB that you expected to see in this document,
or you require additional information about an issue in this table, contact Symantec
Support.
Table A-1
NetBackup 7.5.0.7 EEB Listing
Etrack Number
EEB Description
2577067
Provide ability to specify media server that should be used to perform the Restore request
2617695
An interface is required to display the list of media servers that are available for restoring a
selected backup.
2748951, version 2
Bundle of fixes for NetBackup 7.1.0.4 SAN Client Fibre Transport media server issues.
2829356
A one-time script was created to address an issue with removing image fragments. The script
is not included in any other release vehicle.
2879211
Windows push installations fail during Virtual File Filter (VFF) driver installation.
2912901
2961469
A one-time script was created to address an improperly decommissioned media server. The
script is not included in any other release vehicle.
2968146
A one-time script was created to address an issue with deleting a disk pool. The script will
not be included in any other release vehicle.
2969133
Microsoft SQL restores fail with the following error if the media server is running Windows
and the restore takes longer than one hour: "restored image image_name - (socket read
failed (23))".
3026930
Sharepoint GRT backup of databases having non-English characters fail with file read failed
- status 13.
58

Table A-1
NetBackup 7.5.0.7 EEB Listing (continued)
Etrack Number
EEB Description
3028111
Restore and verify operations for large SharePoint content databases fail with the following
error: "Raw partition size gigabytes does not match".
3029484
A one-time script was created to fully remove a media server by the nbdecommission tool Exit status 20. The script will not be included in any other release vehicle.
3043782
An Advance Success Rate report does not correctly report the number of successful and
failed jobs.
3044819
An Exchange GRT restore that is redirected to a different folder in the original mailbox fails
with server status = 2810, but still works correctly when restored to the original mailbox
location.
3051990
A one-time script was created to delete a disk pool. The script will not be included in any
other release vehicle.
3053482
A Fibre Transport (FT) media server can encounter a problem with the FT server process
(nbftsrvr) stopping with the following error: "SCPALDMA Assertion failed".
3055406
The Fibre Transport (FT) client process (nbftclnt) crashes.
3058479
For the SAN Client Fibre Transport client process (nbftclnt), turn on the
'FTCLIENT_VALIDATE_VIA_CHECK_CONDITION' functionality by default.
3064454
Storage lifecycle policy (SLP) managed duplications fail when writing to a storage unit group
that is set to Failover where the first storage unit was full or unavailable.
3070024
A one-time script was created to delete a disk pool which cannot be removed. The script will
3073941
A memory issue causes the storage pool daemon (spoold) to exit abruptly when running
MSDP on the Solaris platform.
3086115
Image data collector fails on a master server with org.omg.CORBA.OBJECT_NOT_EXIST

server-side exception.
3091012
The NetBackup Database Manager (bpdbm) fails to connect to the database with the following
connection error: "Found server but communication error occurred".
3103018
Image collection eventually stops and the OpsCenter web interface becomes unresponsive.
3112672
The dbbackup.exe process crashes while browsing backup images on an SQL mirroring
configuration setup.
3115248
NetBackup OpsCenter data collection for images fails with a communication exception.
3116644
Image data collection fails with a "CORBA.OBJECT_NOT_EXIST" error.
59

Table A-1
Etrack Number
EEB Description
3122190
The Fibre Transport server process (nbftsrvr) exits abnormally. The nbfdrv64 process exits
with segmentation fault.
3128404
OpsCenter server fails and services are unavailable with Java JRE errors.
3129891
A multistreamed SAP restore fails on Linux because the bprestore command is not properly
formatted.
3130689
OpsCenter does not show Appliance Hardware details for NetBackup 5220 appliance v 2.5.2
3134161, version 2, 1
Bundle of fixes to resolve the various issues of jobs status not being reflected correctly in the
Activity Monitor.
3134396
On AIX media servers that use load balancing, MPMS avg_freemem is calculated properly
while load_avg is calculated as 0 regardless of the actual load.
3136591, version 1
The PureDisk wrapper 'pd_getaddrinfo' does not retry on EAI_AGAIN when DNS is busy.
3136787
Unable to save 'Scheduled Jobs' filters in the 'Planning Activity - Scheduled Job - All Jobs'
report.
3139802
For virtual machines with greater than 10 disks, VMware Virtual Disk Development Kit (VDDK)
returns unordered disk IDs. The disks are added to the catalog in an incorrect order and
cause an issue when a restore to multiple datastores is performed.
3139929
Browsing for backups with the SQL agent skips backups and fails with error 'because it
contains metadata not recognized by the current version of NetBackup'
3141517
The 'Override policy volume pool' policy option is grayed-out under the 'Change Schedule Attributes' tab and 'Media and Device Manager - Media - Volume Pools'. If 'Catalog Backup'
has been selected for a volume pool, then it cannot be deselected.
3142388
A DB2 restore fails with 'SQL2062N' if the backup spans three days or more.
3143477
A DB2 restore fails with 'SQL2062N' if the backup spans three days or more.
3143954
A Fibre Transport (FT) media server can encounter a problem with the Fibre Transport server
process (nbftsrvr) stopping due to an assertion failure.
3147647
Intermittently, media server name and media server ID values are not being passed to
OpsCenter for jobs that re-try.
3149184
The dbbackup.exe process crashes while browsing history.
3149995
An interface is required to display the list of media servers that are available for restoring a
selected backup.
60

Table A-1
Etrack Number
EEB Description
3150002
The NetBackup Backup, Archive, and Restore interface does not provide a way to select a
media server to be used for a restore operation.
3157563
A one-time script was created to address the disk pool deletion issue. The script will not be
included in any other release vehicle.
3162199
When the source database and destination database names and instance names are identical,
a DB2 alternate client roll-forward fails because the backup following the roll-forward tries to
run on the source client instead of the destination.
3162955
The NetBackup Domain Network Analyzer (nbdna) is unable to execute with some versions
of sudo.
3177452
Single file restore from Flashbackup image gets an assert error when restoring a Windows
SIS file.
3177454
After a Hyper-V backup, the virtual hard disk (VHD) file fails to show up in the browser and
cannot be restored. Backup is successful and other files can be browsed and restored.
3177858
An Oracle snapshot backup fails with status code 31.
3178628
A one-time script was created to remove an old MSDP disk pool. The script will not be included
in any other release vehicle.
3179023
The NetBackup Domain Network Analyzer (nbdna) is unable to execute with some versions
of sudo.
3180090
Hot catalog backups fail with status code 67 (client backup failed to read the file list) because
.f files are larger than 4GB.
3180805
Redirected Exchange GRT fails if the Client Access Server (CAS) is not also a mailbox server.
3182935, version 2, 1
Bundle of fixes to resolve the various issues of jobs status not being reflected correctly in the
NetBackup Activity Monitor.
3182981
A pipe is always granted the physical node. However, when a backup with the app_cluster
is registered with Enterprise Media Manager (EMM), the backup always goes by local area
network (LAN).
3184036
The NetBackup Policy Execution Manager (nbpem) stops scheduling jobs, but immediate
and user backups still work. The nbpem process must be restarted to get scheduling started.
3184554
Backups of checkpoint files exhibit performance degradation.
3187365
When VMware backups are run a message will be seen in the Activity Monitor stating that
the snapshot will not be deleted.
61

Table A-1
Etrack Number
EEB Description
3187497
The 'Apply' button is not always available on the 'Client' tab.
3187911
A multistreamed SAP restore fails on SUSE Linux.
3189047
A one-time script was created to remove a disk pool with the name 'dp_pddo_poc' from
Enterprise Media Manager (EMM) database. The script will not be included in any other
release vehicle.
3194255
Catalog backups failing with status code 67 'client backup failed to read the file list', caused
by .f file is larger than 4GB.
3194916
The Front-End Terabytes (FETBs) report shows the same value for multiple master servers.
3195038
Storage lifecycle policy (SLP) managed duplications fail when writing to a storage unit group
that is set to Failover where the first storage unit was full or unavailable.
3195705
A one-time script was created to remove MSDP defined on the master server. The script will
3195898
Alternate and self-restores of a Bare Metal Restore (BMR) Windows client in Citrix guest fail
with the error message "Failed to create partition". This issue results from an incompatibility
with Citrix Xen drivers in a BMR recovery environment.
3197333
Adding a NetBackup 7.5 client to a Solaris 10 Update 11 shared resource tree (SRT) fails.
3198816
Incremental backups of 'EFI System Partition' failing with status code 1.
3199296
A one-time script was created to address an issue where a media server was accidentally
added as a master server in the Enterprise Media Manager (EMM). The script will not be
3200294
Running the bpchangeprimary command by pool name and policy name fails to change
images.
3200840
Use secure version of tomcat
3202205
A SharePoint document library restore succeeds, but the associated informational columns
are missing.
3203750, version 2, 1
Inconsistent job data is shown in the Activity Monitor.
3204762
SharePoint child backups fail with status code 196 when a new stream is added.
3204999, version 1
Inaccurate calculation of capacity and traditional licensing reporting in the NetBackup

Deployment Utility (nbdeployutil).
62

Table A-1
Etrack Number
EEB Description
3205000, version 1

3205001, version 1

3205002, version 1

3205003, version 1

3205004, version 1

3205005, version 1

3205006, version 1

3205007, version 1

3205008, version 1

3205009, version 1

3205010, version 1

3205011, version 1

3205012, version 1

3205013, version 1

3205042
There are millions of "vfm_extract_frag_info_VxFIv5: input_frag_id" messages in the

NetBackup Database Manager (bpdbm) log file with VERBOSE = 0 or at default levels.
3206406
A one-time script was created to address a specific condition where a disk pool could not be
deleted by NetBackup commands. The script will not be included in any other release vehicle.
63

Table A-1
Etrack Number
EEB Description
3206707, version 2, 1
A long-running pruning phase of a cleanup job prevents catalog compression from running.
3206889
BMR restores of Windows Server 2008 and newer clients fail with error messages in the
bmrrst log that are similar to the following: "butils.cpp:RestoreASRData() Failed to move file
[C:\BMR\SCC\Automated System Recovery\e\bootmgr] --gle=2."
3207282
A one-time script was created to remove a reference to a decommissioned media server in

the database. The script will not be included in any other release vehicle.
3208195
A memory issue causes the storage pool daemon (spoold) to exit abruptly when running
MSDP on the Solaris platform.
3210144
An Advanced Success Rate report fails because of a daylight saving time (DST) effect when
the selected time range falls within February 16th and November 21st.
3210493
Cumulative incremental backups can be much slower in NetBackup 7.5 than they were in
version 7.1.
3211336
The NetBackup Administration Console shows zero disk pools under 'Device Monitor - Disk
Pools' if it doesn't have an AdvancedDisk license.
3212208
A one-time script was created to address a condition where the deletion of a disk pool was
not possible when the storage server was already removed. The script will not be included
3212481
Various components are slow to load and appear to hang when broken Network File System
(NFS) mounts are present. This issue can cause backups to fail with status code 2106.
3214359
A large Oracle database (13TB) backup failed with status code 6 and the following error
message: "ORA-27192: skgfcls: sbtclose2 returned error - failed to close file".
3215626
A Disk Pool Full alert gets generated only after the high water mark is reached, which results
in failed backup jobs.
3215794
A one-time script was created to address the removal of disk pool. The script will not be
3216862
A one-time script was created to remove disk pools from an environment. The script will not
be included in any other release vehicle.
3217089
Port of fix from ET3202107 for 7.5.0.4
3218048
3219871
The Fibre Transport client process (nbftclnt) on AIX does not discover the 'ARCHIVE' Python
devices that are associated with /dev/rmtXX device paths when XX is greater than 99.
64

Table A-1
Etrack Number
EEB Description
3221316
A one-time script was created to address the condition where deletion of a disk pool was not
possible when the storage server was already removed. The script will not be included in
any other release vehicle.
3221651
In the NetBackup Backup, Archive, and Restore interface under the 'Restore' tab, the 'Source
client for restores' list only contains the master server.
3222403
During cleanup, the NetBackup Database Manager (bpdbm) process hangs or takes a great
deal of time processing. This behavior is observed in the case of a corrupt .f file with millions
of records.
3224295
A one-time script was created to remove entries from the "DBM_DRMedia" table in order to
remove the "foreign media server" entry from the database. The script will not be included
3225647
A one-time script was created to remove a disk pool and deleted image fragments for a
customer environment. The script will not be included in any other release vehicle.
3225929
A one-time script was created to remove a media server from the NetBackup database. The
script will not be included in any other release vehicle.
3226495
Unable to backup the registry (NTUSER.DAT) when a user is not logged in.
3226695
Restoring to original location does not restore the hardware version when the box is checked
in Backup, Archive, and Restore interface.
3227128
Enterprise Vault partition backups fail with status code 156 for mounted partitions.
3227367
The NetBackup Backup-and-Archive Manager (bpbkar) does not correctly send file information
to the NetBackup Backup-and-Restore manager (bpbrm) for the files that contain a new line
in the file name. The result is a bpbrm core dump issue.
3228489, version 2, 1
NetBackup Systems Management (Policies, Scheduling, and so forth.) issue.
3229364
An alternate restore of a client-side encrypted backup between an x86 computer and a

SPARC computer fails with status code 11.
3229377
Even though the Bare Metal Restore (BMR) database contains compatible Windows drivers,
during a 'Prepare to Restore' operation, a higher-level driver is inserted even though it is
incompatible.
3230967
During replication, the NetBackup disk manager (bpdm) process intermittently exits with the
following message: "bpbrm is gone".
3231391
Media server reported in top left GUI does not agree with job details. Job details has correct
media server information.
65

Table A-1
Etrack Number
EEB Description
3234665
3234668
3234808
A one-time script was created to delete a PureDisk disk pool. The script will not be included
3236302
An Oracle Volume Shadow Copy Service (VSS) snapshot SLP fails to rotate.
3236304
An Oracle snapshot backup fails with status code 31.
3237136

3237452
A one-time script was created to delete old disk pool. The script will not be included in any
3238501
The Front-End Terabytes (FETBs) report displays incorrect data.
3238748
Image lock files have world-writable permissions.
3240151
A one-time script was created to address the media server deletion issue with the
nbdecommission utility. The script will not be included in any other release vehicle.
3241035
A one-time script was created to address the media server deletion failure with the
nbdecommission utility. The script will not be included in any other release vehicle.
3242299
SAP backups of files larger than 4GB fail when 'sort_type' is set to device.
3242432
Backups and duplications of Windows guest VMware incrementals fail with the following error
in the PureDisk plug-in log: "fbu_scan_buf: bytesNeeded already set".
3243594
A core dump issue can occur with the NetBackup Backup-and-Archive Manager
(bpbkar32.exe) during incremental backup. The logs indicate that it was in the
'create_parent_entries' portion of the backup.
3244373
When running a VMWare backup, bpfis.exe can dump core and cause the backup job to
failed with status 13.
3244927
The capacity report for the NetBackup Deployment Utility (nbdeployutil) does not show the
correct 'Flagged Capacity Figures' when reporting against multiple master servers.
3245196
The Java Windows Administration Console is unable to browse the backup history on master
servers running earlier versions of NetBackup.
3248100
Processing Exchange files on snapshot takes too long.
3251172
During backups, bpbkar can crash due to heap corruption.
66

Table A-1
Etrack Number
EEB Description
3251933
NetBackup Cloud issue.
3252489
Oracle FRA backup to STU taken after 24+ hours fails.
3252796
An alternate restore of a client-side encrypted backup between an x86 computer and a

SPARC computer fails with status code 11.
3253362
A one-time script was created to delete a disk pool because image fragments still exist. The
3253473, version 1
Catalog backups fail after several hours with status codes 25 and 50 due to the image
expiration of a client that is no longer configured in the policy, or in the event of a policy
change.
3254621
A one-time script was created to address an issue with decommissioning media servers. The
3255000
linux system shows a leak of one semaphore per backup job on the backup host.
3255087
Single file restores of an NDMP policy type from and OST_FIM snapshot fail with the following:
'DUMP: somefile.txt: No such file or directory'.
3256280, version 1
The NetBackup Policy Execution Manager (nbpem) does not honor the 'Retries allowed after
runday' option.
** 3256506, version 7, No error is reported, yet the virtual machine backup or restore operation may have failed
6, 5, 4, 3, 2, 1
when doing a VMware backup of an offline LUN or a read-only LUN.
3256665
Image information intermittently missed for successful job records.
3257184
A one-time script was created to remove a disk volume. The script will not be included in any
3258112
A Disk Pool Full alert gets generated only after the high water mark is reached, which results
in failed backup jobs.
3258831
Backup jobs to Data Domain fail when NetBackup Accelerator is enabled.
3260582
Single file restores of an NDMP policy type from and OST_FIM snapshot fail with the following:
'DUMP: somefile.txt: No such file or directory'.
3260752
Added the force flag to the vxassist command to allow the SmartMove feature of Volume
Manager to work with NetBackup snapshots.
3260932
Apache Tomcat upgrade for security.
67

Table A-1
Etrack Number
EEB Description
3262154
Deletions of images in NetBackup with SQL-BackTrack for Oracle if 'Legal Hold' is set.
3262659
On an AIX client, if the lslv command output contains the 'DEVICESUBTYPE' value, then
Bare Metal Restore (BMR) records the wrong file system type during backup which causes
the restore to fail with invalid temporary mount point.
3262796
Restoring to original location does not restore the hardware version when the box is checked
in Backup, Archive, and Restore interface.
3263385
Data collection fails with status code 194 when collecting the Index data type.
3263461
NetBackup Fibre Transport issue.
3263480
Deletions of images in NetBackup for 'Legal Hold' images for XBSA and SQL-BackTrack
agents for Oracle.
3263484
Deletions of images in NetBackup and Oracle if 'Legal Hold' is set.
3263486
3263488
Prevent the deletions of images in NetBackup and Oracle if Legal Hold is set.
3263490
3263564
If 'metastat' command shows full device path instead of device name in the output and Solaris
client has Solaris Volume Manager installed, then restore will fails with invalid boot device
path created for a non-default Solaris Volume Manager client s
3265176

3265279
The NetBackup Policy Execution Manager (nbpem) does not honor the 'Retries allowed after
runday' option.
3266917
Unable to backup the registry (NTUSER.DAT) when a user is not logged in.
3269849
A core dump issue occurs when the nbrbutil -dumptables command is run when the NetBackup
Enterprise Media Manager (nbemm) is down.
3270022
Backups of stub files fail with status code 130. NetBackup treats these stub files as sparse
files.
3272381
Unable to decommission an appliance server that was incorrectly added as a master server.
3273745
Running the bpchangeprimary command by pool name and policy name fails to change
images.
68

Table A-1
Etrack Number
EEB Description
3274072
The 'Override policy volume pool' policy option is grayed-out under the 'Change Schedule Attributes' tab and 'Media and Device Manager - Media - Volume Pools'. If 'Catalog Backup'
has been selected for a volume pool, then it cannot be deselected.
3274742
If multiplexing is enabled in a VMware policy, the backup job can fail with status code 73.
3275166
3275765
The Backup, Archive, and Restore program for Windows crashes when the 'Backup' window
is closed using the Close button (X) on the application window.
3277447
The keyword 'VXDBMS_VALIDATION = OFF' in the vxdbms.conf file does not work correctly.
It should stop validating the database for a hot catalog backup.
3277716
An Exchange granular restore fails with the following error when the mailbox name contains
a forward slash (/): "no entity was found".
3277737
Oracle backup fails which causes removal of unwanted images.
3281714
A one-time script was created to address the wrong master server references deletion failure.
The script will not be included in any other release vehicle.
3282319
The dbbackup.exe process crashes when the user tries to browse the backup with the SQL
server agent interface.
3284351
The NetBackup Enterprise Media Manager process (nbemm) hangs due to different queries
getting stuck.
3284494
VMware backup job fails in the backup and archive manager (bpbkar) with status code 73 if
multiplexing is enabled.
3284692
A one-time script was created to delete a PureDisk disk pool and one remaining image. The
** 3286233
Some jobs missing during Job data collection

3286399
A catalog cleanup runs while a catalog recovery is active, causing newly restored catalog
files to be deleted prematurely.
3286500
A catalog cleanup runs while a catalog recovery is active, causing newly restored catalog
files to be deleted prematurely.
3287240
VMware incremental backups with block level incremental backup (BLIB) enabled fail with
status codes 40 and 13. The VMware session timeout and read timeout occur because
creating a bitmap for modified sectors takes more time for the virtual disk.
69

Table A-1
Etrack Number
EEB Description
3288413
A one-time script was created to address an issue where an MSDP storage server could not
be deleted. The script will not be included in any other release vehicle.
3288749
Use secure version of tomcat
3289804
Failed to remove a disk pool, media server, and NDMP server through commands.
3289890
TIR pruning fails due to fetching invalid image information from NBDB.
3290013
3292292
Various Sybase defects.
3292295
VMware backups leak semaphores on Linux backup hosts.
3294558
A number of data collectors show a "Not Started" status in OpsCenter.
3295967
An Exchange granular restore fails with the following error when the mailbox name contains
a forward slash (/): "no entity was found".
** 3298566
NetBackup OpsCenter does not show some of the jobs that are seen in the Activity Monitor.
** 3298572
NetBackup OpsCenter does not show some of the jobs that are seen in the Activity Monitor.
3299072
Snapshot backups on a Windows Server 2008 R2 computer with an EFI partition fail with
status code 1.
3300058
Job status not being reflected correctly in the NetBackup Activity Monitor.
3300573
A core dump issue occurs while running the nrbutil -dumptables command when the
NetBackup Enterprise Media Manager (nbemm) is down.
3303030
A VxMS error occurs in reading a logical volume manager (LVM) disk if the disk also contains
a master boot record (MBR) magic number.
3304711
Shared Resource Tree (SRT) creation fails for Solaris SPARC 10 Update 10 with the following
error message: "[Error] V-125-447 Unable to install Symantec NetBackup Client software
into the SRT."
3306691
3306840
3307842
Support for GUID partition table (GPT) boot disk. This support addresses an issue with the
error "Found 0 Virtual Volumes".
70

Table A-1
Etrack Number
EEB Description
3308782, version 1
The Activity Monitor continually reports "Unknown Job Type" following an upgrade of the
master server.
3308932
3309127
The "bpimage -update -keyword" command does not work with NetBackup 7.5.0.x.
3310421
A one-time script was created to remove three disk pools. The script will not be included in
any other release vehicle.
3311027
The 'ndmp_end_notify' script is not called when using NDMP multiplexing.
3311495
When a catalog backup fails, the NetBackup Database Manager (bpdbm) crashes while
preparing to run the disaster recovery email script.
3315572
A one-time script was created to remove an unwanted master server entry from the Enterprise
Media Manager (EMM) database. The script will not be included in any other release vehicle.
3315839
Enterprise Vault partition backups fail with status code 156 for mounted partitions.
3316213
During snapshot deletion sessions, nbdelete may start many unnecessary bpdm processes
for snapshot deletion. This issue can cause deletion performance problems.
3316947
Windows Remote Administration Console overflow displaying KBytes written to media for
large backup(approx. 5.5 TB).
3320504
Trap recipients are being removed after a copy of alert policy has been made.
3320755
The NetBackup Enterprise Media Manager (nbemm) appears to hang and stop logging.
3321055
Unable to browse backup images using the MSSQL agent interface for clustered MSSQL
databases that are configured for mirroring.
3321609, version 2, 1
A VxMS error occurs in reading a logical volume manager (LVM) disk if the disk also contains
a master boot record (MBR) magic number.
3324604
Hot catalog backups fail with status code 67 (client backup failed to read the file list) because
.f files are larger than 4GB.
3325351, version 1
Bundle of fixes to address TIR (True Image Restoration) catalog data pruning and the
NetBackup Database Manager (bpdbm) failing to connect to the database.
3325584
Unable to browse virtual machines for selection. The following is displayed in the bpVMutil
logs: "CREATE_CONTAINER_VIEW_ERROR".
3331197
Storage Unit Group set to Failover does not correctly select Storage Units.
71

Table A-1
Etrack Number
EEB Description
3331244
A one-time script was created to address a server that was set to the wrong type. The script
will not be included in any other release vehicle.
3331462
A one-time script was created to remove a disk pool that is no longer associated with any
storage server. The script will not be included in any other release vehicle.
3332354
Unable to browse or discover virtual machines on vCenter 4.1.
3333479
The 'ndmp_end_notify' script does not get called when multiplexing (MPX) is selected in the
policy schedule and on the destination storage unit has MPX greater than 1.
3333826
Failed to retrieve virtual hard disk (VHD) file during restore. However, file browsing available
through Normal backup type.
3335192
3335725
In 7.5.0.6, ESX Server button during Alternate Location restore fails
3335748
Unable to back up the clients that have hostnames that contain a trailing dot (period).
3336238
A one-time script was created to remove an orphaned disk pool. The script will not be included
3336859
The cache garbage collection creates a large number of events that do not get removed from
the NetBackup Deduplication Manager (spad) events table.
3337097
A one-time script was created to decommission a media server that has contents stuck in
'DBM_MAIN' and 'DBM_DRMedia'. The script will not be included in any other release vehicle.
3338332, version 1
A long-running pruning phase of a cleanup job prevents catalog compression from running.
3339508
Unable to browse or discover virtual machines on vCenter 4.1. The error

"CREATE_CONTAINER_VIEW_ERROR" is seen in the bpVMutil logs.
3341375
The VMware ESX server search button fails during an alternate location restore.
3342070
Tar32.exe process can crash during a System State restore on Windows 2003.
3348788
The "bpimage -update -keyword" command does not work with NetBackup 7.5.0.x.
3356167
A one-time script was created to address a problem decommissioning media servers when
disk objects still exist. The script will not be included in any other release vehicle.
3356355
A one-time script was created to remove an MSDP NDMP storage server from three servers.
The script will not be included in any other release vehicle.
72

Table A-1
Etrack Number
EEB Description
3357356
A one-time script was created to address an issue where a host could not be deleted. The
3357437
A one-time script was created to remove an orphaned disk group and disk volume. The script
will not be included in any other release vehicle.
** 3357483
Restore fails in Exchange 2013 server due to a Microsoft bug that can result in backups that
cannot be restored with the roll-forward option
3357862
SharePoint 2010 GRT backup fails with error code 13 on the host running Chinese locale
3358176
If a system has more than 25 IPv6 interfaces, then the Private Branch Exchange (PBX) server
protocol in the PBX C library fails.
3358533
Backups may become inaccessible if the nbdecommission command is run incorrectly for
the removal of an MSDP server.
3383267
3385162
NetBackup Agent for Windows Client issue.
73

NB 7507 Release Notes

Diunggah oleh

Informasi Dokumen

Deskripsi Asli:

Hak Cipta

Format Tersedia

Bagikan dokumen Ini

Bagikan atau Tanam Dokumen

Opsi Berbagi

Apakah menurut Anda dokumen ini bermanfaat?

Apakah konten ini tidak pantas?

Hak Cipta:

Format Tersedia

NB 7507 Release Notes

Diunggah oleh

Hak Cipta:

Format Tersedia

Symantec NetBackup

7.5.0.7 Release Notes

Maintenance Release Update

Symantec NetBackup 7.5.0.7 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

NetBackup Future Platform and Feature Plans

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 ...................................... 8

Platform compatibility ....................................................... 10

Operating system patches and updates ............................................ 17

About NetBackup 7.5.0.7 operational notes .......................................

End-of-life notifications ..................................................... 52

About the NetBackup 7.5.0.7 release content .............. 54

New features and

About the NetBackup 7.5.0.7 release

About NetBackup 7.5.0.7 new features and enhancements

NetBackup 7.5.0.7 new enhancements and support

About the NetBackup 7.5.0.7 release

NetBackup Late Breaking News

New features and enhancements

About NetBackup 7.5.0.7 new features and

NetBackup 7.5.0.7 new enhancements and support

Upgrade to Java Runtime Environment (JRE) 7

About upgrade paths to the NetBackup 7.6 line of releases

About NetBackup 7.5.0.x release compatibility

NetBackup compatibility lists

About upgrade paths to the NetBackup 7.6 line of

About NetBackup 7.6.0.1

Upgrades from NetBackup 7.5.0.6

Amazon S3 cloud storage buckets in regions other than US Standard

Installing or Upgrading from NetBackup 7.5.0.7

About NetBackup 7.5.0.x release compatibility

NetBackup 7.5 Release Notes

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

About software release types

A software release update is a double-dot release, for example 2.5.1 or 7.5.1.