Symantec NetBackup 7.1.0.

1
Release Notes

UNIX, Windows, and Linux

NetBackup 7.1.0.1 Maintenance Release

The software described in this book is furnished under a license agreement and may be used
only in accordance with the terms of the agreement.

Documentation version: 7.1.0.1

Legal Notice
Copyright © 2011 Symantec Corporation. All rights reserved.

Symantec and the Symantec Logo are trademarks or registered trademarks of Symantec
Corporation or its affiliates in the U.S. and other countries. Other names may be trademarks
of their respective owners.

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

THE DOCUMENTATION IS PROVIDED "AS IS" AND ALL EXPRESS OR IMPLIED CONDITIONS,
REPRESENTATIONS AND WARRANTIES, INCLUDING ANY IMPLIED WARRANTY OF
MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR NON-INFRINGEMENT,
ARE DISCLAIMED, EXCEPT TO THE EXTENT THAT SUCH DISCLAIMERS ARE HELD TO
BE LEGALLY INVALID. SYMANTEC CORPORATION SHALL NOT BE LIABLE FOR INCIDENTAL
OR CONSEQUENTIAL DAMAGES IN CONNECTION WITH THE FURNISHING,
PERFORMANCE, OR USE OF THIS DOCUMENTATION. THE INFORMATION CONTAINED
IN THIS DOCUMENTATION IS SUBJECT TO CHANGE WITHOUT NOTICE.

The Licensed Software and Documentation are deemed to be commercial computer software
as defined in FAR 12.212 and subject to restricted rights as defined in FAR Section 52.227-19
"Commercial Computer Software - Restricted Rights" and DFARS 227.7202, "Rights in
Commercial Computer Software or Commercial Computer Software Documentation", as
applicable, and any successor regulations. Any use, modification, reproduction release,
performance, display or disclosure of the Licensed Software and Documentation by the U.S.
Government shall be solely in accordance with the terms of this Agreement.

Symantec Corporation
350 Ellis Street
Mountain View, CA 94043

http://www.symantec.com
Technical Support
Symantec Technical Support maintains support centers globally. Technical
Support’s 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.
Symantec’s 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 Symantec’s support offerings, you can visit our Web site
at the following URL:
www.symantec.com/business/support/
All support services will be delivered in accordance with your support agreement
and the then-current enterprise technical support policy.

Contacting Technical Support

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

Licensing and registration

If your Symantec product requires registration or a license key, access our technical
support Web page at the following URL:
www.symantec.com/business/support/

Customer service
Customer service information is available at the following URL:
www.symantec.com/business/support/
Customer Service is available to assist with non-technical questions, such as the
following types of issues:
■ Questions regarding product licensing or serialization
■ Product registration updates, such as address or name changes
■ General product information (features, language availability, local dealers)
■ Latest information about product updates and upgrades
■ Information about upgrade assurance and support contracts
■ Information about the Symantec Buying Programs
■ Advice about Symantec's technical support options
■ Nontechnical presales questions
■ Issues that are related to CD-ROMs, DVDs, or manuals
Support agreement resources
If you want to contact Symantec regarding an existing support agreement, please
contact the support agreement administration team for your region as follows:

Asia-Pacific and Japan [email protected]

Europe, Middle-East, and Africa [email protected]

North America and Latin America [email protected]

 Contents

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

Chapter 1 New Features and Enhancements ..................................... 9
About the NetBackup 7.1.0.1 enhancements ....................................... 9

Chapter 2 Platform Compatibility ....................................................... 11

About platform compatibility for NetBackup 7.1.0.1 ........................... 11
NetBackup compatibility lists ......................................................... 11
About NetBackup binary sizes ........................................................ 13

Chapter 3 Product Dependencies ....................................................... 19

About Product Dependencies .......................................................... 19
Operating system patches and updates ............................................. 19
VxFS and VxVM compatible versions ............................................... 27

Chapter 4 Operational Notes and Issues ........................................... 31

About NetBackup 7.1.0.1 Operational Notes ...................................... 31
About general NetBackup 7.1.0.1 notes ............................................ 32
About NetBackup OpsCenter limitations ........................................... 33
General NetBackup OpsCenter notes .......................................... 33
About uninstalling OpsCenter 7.1 before you install OpsCenter
7.1.0.1 on UNIX ................................................................ 35
Uninstalling OpsCenter Server 7.1 before uninstalling OpsCenter
Server 7.1.0.1 .................................................................. 35
Uninstalling OpsCenter Agent 7.1 before uninstalling OpsCenter
Agent 7.1.0.1 ................................................................... 37
About planning an OpsCenter Agent deployment ......................... 39
About NetBackup for VMware ........................................................ 48

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

About the NetBackup 7.1.0.1 master Etrack index list ......................... 51
8 Contents

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

About release content conventions .................................................. 53
About NetBackup 7.1.0.1 release content .......................................... 54
NetBackup 7.1.0.1 Emergency Engineering Binary (EEB) Listing ........... 69
 Chapter 1
New Features and
Enhancements
This chapter includes the following topics:

■ About the NetBackup 7.1.0.1 enhancements

About the NetBackup 7.1.0.1 enhancements

This maintenance release focuses on fixes to the known issues that include the
customer-specific issues that have been documented in the form of a Titan Case.
Many of these fixes were in the form of engineering binary bundles that were
created to address specific customer issues with previous version of NetBackup.
This maintenance release contains those engineering binary bundles.
This release contains the following OpenStorage Optimized Duplication
Performance and Stability Enhancements.
With a NetBackup 7.1.0.1 media server initiating the duplication, the following
scenarios are supported: (Note, that the initiating media server is a server that
has been configured to have an access to both the source and the target storage
units in an optimized duplication scenario. By default, NetBackup allows all media
servers to have access to all storage units.)
■ Duplications from NetBackup Media Server Deduplication Pool (MSDP) 7.1.0.1
to MSDP storage pool versions 7.0, 7.0.1, 7.0.1 with the RockSolid EEB Bundle
(ET2233961), 7.1 and 7.1.0.1
■ Duplications from NetBackup Media Server Deduplication Pool (MSDP) 7.1.0.1
to PureDisk Deduplication Option (PDDO) 6.6.0.3 with EEB 31 (ET2286421),
and PDDO 6.6.1.2 with EEB4 (ET2253079)
Please reference Article TECH161306 on the Symantec Support Web site for
additional upgrade and configuration information related to this feature.
10 New Features and Enhancements
About the NetBackup 7.1.0.1 enhancements

For a complete list of the new NetBackup 7.1 features and enhancements, refer
to the "New NetBackup Features" chapter in the NetBackup 7.1 Release Notes for
UNIX, Windows, and Linux. Use the following URL to locate this document on the
Symantec Support Web site.
http://www.symantec.com/docs/DOC3412
Before you install this release, make sure that you have installed NetBackup 7.1.
You can apply this release to any NetBackup 7.1 master, media, or client server,
in any order, and retain compatibility between the components.

Table 1-1 Mixed-server compatibility

Master server version Media server version Client version

NetBackup 7.1 7.1 7.1

NetBackup 7.1 7.1 7.1.0.1

NetBackup 7.1.0.1 7.1.0.1 7.1

NetBackup 7.1.0.1 7.1.0.1 7.1.0.1

 Chapter 2
Platform Compatibility
This chapter includes the following topics:

■ About platform compatibility for NetBackup 7.1.0.1

■ NetBackup compatibility lists

■ About NetBackup binary sizes

About platform compatibility for NetBackup 7.1.0.1

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

NetBackup compatibility lists

The most up-to-date compatibility information on platforms, peripherals, drives,
and libraries is located in various compatibility lists on the Symantec Support
Web site. The following compatibility lists are available on the Symantec Support
Web site:
http://www.symantec.com/docs/TECH59978
■ The NetBackup Enterprise Server and Server 7.x OS Software Compatibility List
contains information about the operating system (OS) level and the version
that is required to be compatible with a NetBackup master or media server. It
12 Platform Compatibility
NetBackup compatibility lists

also describes the OS level and the version that is required to be compatible
with a NetBackup client. Predecessors and successors to the documented
operating system levels may function without difficulty, as long as the release
provides binary compatibility with the documented operating system.
That list contains information about each of the following NetBackup
Enterprise features:
■ NetBackup Enterprise servers and client
■ Bare Metal Restore (BMR)
■ NetBackup Access Control (NBAC)
■ Network Data Management Protocol (NDMP)
■ NetBackup SAN Client and Fiber Transport
■ NetBackup Virtual System compatibility
■ MSEO (media server encryption option)
■ NetBackup Media Server Deduplication Option
■ NetBackup OpsCenter
■ File System Capability
NetBackup compatibility for a platform or OS version requires platform vendor
support for that product. The platform compatibility lists that NetBackup
maintains are subject to change as vendors add and drop platforms or OS
versions.
■ The NetBackup server 7.x hardware compatibility list includes information for
compatible drives, libraries, virtual tape devices, robot-types, fibre-channel
HBAs, switches, routers, bridges, iSCSI configurations, and encryption devices
That list includes information about the compatible drives, robot types,
switches, routers, and bridges, and iSCSI configurations that coincide with the
following hardware:
■ OpenStorage
■ Virtual tape libraries (VTLs)
■ Network Data Management Protocol (NDMP)
■ Host bus adapters (HBAs)
■ Encryption

■ NetBackup Database Agent 7.x Software Compatibility List

This compatibility list contains the most current platform compatibility
information for NetBackup database agents.
 Platform Compatibility 13
About NetBackup binary sizes

■ NetBackup 7.x Snapshot Client compatibility lists

■ NetBackup 7.x BMR File System and Volume Manager compatibility lists
See also the NetBackup Bare Metal Restore Administrator's Guide for the
following additional compatibility lists:
■ BMR compatible shared resource tree (SRT) versions
■ BMR compatible file systems and volume managers
■ BMR compatible cluster solutions
■ BMR disk space requirements

■ NetBackup7.x Cluster Compatibility List

■ NetBackup Desktop/Laptop Option compatibility list
■ Backup Exec Tape Reader compatibility list
To locate platform compatibility information on the Symantec Support Web site
1 Go to the following URL:
www.symantec.com/business/support
2 Select the NetBackup Enterprise Server link under the Top Products title
on the Web page .
3 Select NetBackup Master Compatibility List link under the Compatibility
List title on the Web page .
The Web page refreshes and contains a list of compatibility documents. From
this Web page, you can refine your search to find a link to the appropriate
document. (The compatibility list documents are in PDF format. You must
have Adobe Acrobat Reader to view these documents.)

About NetBackup binary sizes

The information in this section helps you determine if you have allocated the
proper amount of disk space to your servers to safely and efficiently back up and
restore all of the data in your NetBackup environment.
Table 2-1 shows the approximate binary size of the NetBackup master and media
server software, and the NetBackup client software requirements for each
operating system that is compatible with NetBackup.
14 Platform Compatibility
About NetBackup binary sizes

Table 2-1 NetBackup binary sizes for compatible platforms

OS/Version CPU 32-bit 64-bit 32-bit 64-bit Notes

Architecture client client server server

AIX 5.3 POWER 1073MB 3599MB 64-bit binary compatible.

AIX 6.1 POWER 1073MB 3599MB 64-bit binary compatible.

AIX 7.1 POWER 1073MB 3599MB New platform in this release.

Asianux 2.0, 3.0 x64 624MB 2564MB

Canonical Ubuntu 8.0 x64 624MB

Canonical Ubuntu 9.04 x64 624MB New platform in this release.

Canonical Ubuntu 10.04 x64 624MB New platform in this release.

CentOS 5.2, 5.3 x64 624MB

Debian GNU/Linux 4.0, 5.0 x64 624MB

FreeBSD 6.1, 6.2, 6.3, 7.x, 8.x x86 120MB Added the 8.x platform in this
release.

FreeBSD 8.x x64 120MB New platform in this release.

HP-UX 11.11 PA-RISC 738MB 1797MB 64-bit binary compatible.

Media server or client
compatibility only.

HP-UX 11.23 PA-RISC 738MB 1797MB 64-bit binary compatible.

Media server or client
compatibility only.

HP-UX 11.31 PA-RISC 738MB 1797MB 64-bit binary compatible.

Media server or client
compatibility only.

HP-UX 11.31 IA64 1235MB 3648MB

Mac OS X 10.5 POWER 194MB

Mac OS X 10.5, 10.6 x86 194MB

Novell Open Enterprise x64 611MB 2492MB

Server 2

OpenVMS 5.5 HP VAX 16MB

OpenVMS 6.2 HP VAX 16MB

 Platform Compatibility 15
About NetBackup binary sizes

Table 2-1 NetBackup binary sizes for compatible platforms (continued)

OS/Version CPU 32-bit 64-bit 32-bit 64-bit Notes

Architecture client client server server

OpenVMS 7.3 HP VAX 16MB

OpenVMS 6.1 HP Alpha 16MB

OpenVMS 6.2 HP Alpha 16MB

OpenVMS 7.3 HP Alpha 16MB

OpenVMS 8.2 HP Alpha 16MB

OpenVMS 8.3 HP Alpha 16MB

OpenVMS 8.2 HP IA64 16MB

OpenVMS 8.3 HP IA64 16MB

OpenVMS 8.3-1H1 HP IA64/Alpha 16MB

Oracle Enterprise Linux 4.0 x64 624MB 2564MB 64-bit binary compatible.

Oracle Enterprise Linux 5.0 x64 624MB 2564MB 64-bit binary compatible.

Red Flag Linux 5.0 x64 624MB 2564MB

Red Hat Enterprise Linux 4.0 x64 624MB 2564MB 64-bit binary compatible.
(AS)

Red Hat Enterprise Linux 5.0 x64 624MB 2564MB 64-bit binary compatible.
(base)

Red Hat Enterprise Linux 5.0 x64 625MB 2564MB

(AS)

Red Hat Enterprise Linux 6.0 x64 624MB 2564MB 64-bit binary compatible. New
(base) platform for this release.

Red Hat Enterprise Linux 6.0 x64 624MB 2564MB 64-bit binary compatible. New
(AS) platform for this release.

Red Hat Enterprise Linux x64 624MB

Desktop 4.0

Red Hat Enterprise Linux x64 624MB 64-bit binary compatible.

Desktop 5.0

Red Hat Enterprise Linux 4.0 IA64 490MB Compatible with client only.
(AS)
16 Platform Compatibility
About NetBackup binary sizes

Table 2-1 NetBackup binary sizes for compatible platforms (continued)

OS/Version CPU 32-bit 64-bit 32-bit 64-bit Notes

Architecture client client server server

Red Hat Enterprise Linux 5.0 IA64 490MB Compatible with client only.
(base)

Red Hat Enterprise Linux 4.0 POWER 228MB

(AS)

Red Hat Enterprise Linux 5.0 POWER 228MB

(base)

Red Hat Enterprise Linux 4.0 z/Architecture 447MB 1906MB Media server or client
(AS) compatibility only.

Red Hat Enterprise Linux 5.0 z/Architecture 447MB 1906MB Media server or client
(base) compatibility only.

Solaris 9 SPARC 621MB 64-bit binary compatible.

Solaris 10 SPARC 738MB 2260MB 64-bit binary compatible.

Solaris 10 x64 535MB 2133MB 64-bit binary compatible.

Solaris 11 Express SPARC 738MB 64-bit binary compatible.

Solaris 11 Express x64 535MB 64-bit binary compatible.

SUSE Linux Enterprise Server IA64 477MB Compatible with client only.
10 (SP1)

SUSE Linux Enterprise Server IA64 477MB Compatible with client only.
11

SUSE Linux Enterprise Server x64 611MB 2492MB

10 (SP1)

SUSE Linux Enterprise Server x64 611MB 2492MB

11

SUSE Linux Enterprise Server POWER 240MB Compatible with client only.
10 (SP1)

SUSE Linux Enterprise Server z/Architecture 429MB 1868MB Media server or client
10 (SP1) compatibility only.

SUSE Linux Enterprise Server z/Architecture 429MB 1868MB Media server or client
11 compatibility only.
 Platform Compatibility 17
About NetBackup binary sizes

Table 2-1 NetBackup binary sizes for compatible platforms (continued)

OS/Version CPU 32-bit 64-bit 32-bit 64-bit Notes

Architecture client client server server

Windows x86 600MB 1700MB Covers all compatible

Windows x86 platforms

Windows x64 700MB 1900MB Covers all compatible

Windows x64 platforms

Windows IA64 600MB Compatible with client only.

18 Platform Compatibility
About NetBackup binary sizes
 Chapter 3
Product Dependencies
This chapter includes the following topics:

■ About Product Dependencies

■ Operating system patches and updates

■ VxFS and VxVM compatible versions

About Product Dependencies

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

Operating system patches and updates

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

Table 3-1 Operating system patches and updates for NetBackup

Operating system type and Patch Notes

version

AIX 5.3 AIX runtime libraries 8.0.0.10 or You may need to restart after
9.0.0.3 or later changing to version 9.0.0.3.

xlC.rte 8.0.0.10 fileset For the xlC.rte 8.0.0.10 fileset,

you may need to install the IY91284
fix to avoid a potential issue when
creating or updating the NetBackup
database. The IY91284 fix is part of
Maintenance Level 6.

AIX 5.3 TL7 SP5 (5300-07-05-0831) NetBackup 7.0 requires the AIX 5.3
TL7 SP5 (5300-07-05-0831
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 IZ16878 When you start Java user interface

applications on AIX 6.1 platforms an
exception can occur. To prevent the
exception, Symantec recommends
that you install patch IZ16878 from
IBM® Support.

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

Networking.NET-RUN-64:
/usr/lib/pa20_64/libipv6.sl
 Product Dependencies 21
Operating system patches and updates

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

Operating system type and Patch Notes

version

Networking.NET2-RUN:
/usr/lib/hpux32/libipv6.so

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

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

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

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

HP-UX PA-RISC Networking.NET-RUN: For HP-UX PA-RISC platforms, this

/usr/lib/libipv6.sl fileset is required:

Networking.NET-RUN-64: For HP-UX PA-RISC platforms, this

/usr/lib/pa20_64/libipv6.1 fileset is required:

Networking.NET-RUN-64: For HP-UX PA-RISC platforms, this

/usr/lib/pa20_64/libipv6.sl fileset is required:

Networking.NET2-RUN: For HP-UX PA-RISC platforms, this

/usr/lib/libipv6.1 fileset is required:

HP-UX 11.11 PHSS_35385 This patch is required for JAVA 6.0.

PHSS_32226 This patch is a LIBCL patch.

22 Product Dependencies
Operating system patches and updates

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

Operating system type and Patch Notes

version

PHSS_37516 Contains fixes for the following:

■ QXCR1000593919: purifyplus
dumps core in PA32
■ QXCR1000589142: dld crash in
LL_new_descendent_list when the
aCC application is exiting.
■ QXCR1000589142: dld crash in
LL_new_descendent_list when the
aCC application is exiting.
■ QXCR1000746161: dlsym()
hangs
■ QXCR1000593999: dld emits
assert messages for chatr
+mem_check enabled 64-bit
executables

PHSS_26946 This patch is necessary to enable any

C++ runtime code to work properly.

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.

PHSS_35379 That is a recommended critical patch

from HP that is required for
successful NetBackup client backups.

PHCO_29029 That is a recommended critical patch

from HP that is required for
NetBackup to use VxSS.
 Product Dependencies 23
Operating system patches and updates

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

Operating system type and Patch Notes

version

PHSS_24045 Allow POLL_INTERVAL to be set to

zero in /var/stm/config/tools/
monitor/dm_stape.cfg. That
disables the dm_stape monitor
within the Event Monitoring System.
Symantec recommends that you
upgrade to IPR0109.

PHSS_30970 This patch can cause problems with

the programs that have the setuid
bit set. Hewlett-Packard ’s IT resource
center Web site contains information
about this patch.

www1.itrc.hp.com

PHCO_35743 S700_800 11.11 libc cumulative patch

The above patch has dependency on
the following patches:

■ PHCO_31923 (critical patch):

s700_800 11.11 libc cumulative
header file patch
■ PHKL_34805 : 700_800 11.11
JFS3.3 patch; mmap

HP-UX 11.23 PHSS_37201 This patch is required for JAVA 6.0.

PHCO_33431 Symantec recommends that all

customers running 11.23 install this
patch.

PHSS_34858 That is a recommended critical patch

from HP that is 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).
24 Product Dependencies
Operating system patches and updates

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

Operating system type and Patch Notes

version

PHSS_37492 Contains fixes for the following:

■ QXCR1000593919: purifyplus
dumps core in PA32
■ QXCR1000589142: dld crash in
LL_new_descendent_list when the
aCC application is exiting.
■ QXCR1000746161: dlsym()
hangs
■ QXCR1000593999: dld emits
assert messages for chatr
+mem_check enabled 64-bit
executables

HP-UX 11.31 PHSS_37202 This patch is required for JAVA 6.0.

QPK1131 (B.11.31.0809.326) patch This patch bundle is required for

bundle NetBackup media server support. This
is an HP-UX September 2008 patch
bundle.

SUSE Linux Enterprise Server 10 x64 SUSE Linux Enterprise Server 10 The operating system version must
update 2 be SUSE Linux Enterprise Server 10
update 2 or greater to run NetBackup
7.0.

Solaris 9 SPARC 64-bit client 111712-11 (or greater) Change Request ID - 6815915

111722-04 (or greater)

Patch: 112908-29 (or greater)

Patch: 112874-31 (or greater)

122300-53 Change Request ID - 6723423

Solaris 10 SPARC 64-bit (server and update 4 (08/07) and newer The server is supported on update 4
client) (08/07) and newer.

139555-08 Change Request ID - 6723423

119963-21 Change Request ID - 6815915

Solaris 10 x64 119964-21 Change Request ID - 6815915

 Product Dependencies 25
Operating system patches and updates

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

Operating system type and Patch Notes

version

139556-08 Change Request ID - 6723423

Windows XP x86-32 KB936357 Microsoft microcode reliability

update.

Windows XP x86-64 KB928646 Hot fix for hangs of connection

attempts by PBX.

Windows Vista x86-32 KB936357 Microsoft microcode reliability

update.

KB952696 Contains the necessary updates to

ensure that you can back up
encrypted files.

Windows Vista x86-64 KB936357 Microsoft microcode reliability

update.

KB952696 Contains the necessary updates to

ensure that you can back up
encrypted files.

Windows Server 2003 IA64 (SP1 & KB913648 Contains the necessary updates to run
SP2) Volume Shadow Copy.

KB928646 Hot fix for hangs of connection

attempts by PBX.

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

KB913648 Contains the necessary updates to run

Volume Shadow Copy.

KB936357 Microsoft microcode reliability

update.

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 & KB883646 Microsoft Storport hot fix.
SP2)

KB913648 Contains the necessary updates to run

Volume Shadow Copy.
26 Product Dependencies
Operating system patches and updates

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

Operating system type and Patch Notes

version

KB928646 Hot fix for hangs of connection

attempts by PBX.

KB936357 Microsoft microcode reliability

update.

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 Contains the necessary updates to

ensure that you can back up
encrypted files.

Windows Server 2008 x86-64 KB952696 Contains the necessary updates to

ensure that you can back up
encrypted files.

Windows Server 2008 IA64 KB952696 Contains the necessary updates to

ensure that you can back up
encrypted files.

The following additional product dependency information applies to this release

of NetBackup:
■ Product dependency notification for customers running Microsoft Windows
Vista or Windows 2008 server.
If you want to protect client (or server) systems that are running either
Microsoft Windows Vista or Windows 2008 server, you may need to install
Microsoft hot fix number KB952696. If you attempt to back up any protected
files that have been encrypted by the operating system, NetBackup cannot
back up these files. NetBackup reports that it is unable to access the encrypted
files and the backup continues with all of the remaining files.

Note: That does not apply to NetBackup encryption. NetBackup encryption is

separate from the file system encryption, meaning that NetBackup-encrypted
files are backed up. In addition, this hot fix is not needed for any Windows
version before Microsoft Windows Vista or Windows 2008 server. If you are
running Vista or Server 2008, please refer to KB952696 to see if this hot fix is
required for your operating system version
 Product Dependencies 27
VxFS and VxVM compatible versions

VxFS and VxVM compatible versions

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

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

Operating system OS Version Version of VxFS Version of VxVM Notes

AIX 5L 5.3 (64 bit) 5.1 SP1 and higher 5.1 SP1 and higher

6.1 (64 bit) 5.0 MP3 and higher 5.0 MP3 and higher

HP-UX PA-RISC 11.11 3.3 and 3.5 3.5 only

11.23 3.5, 4.1, and 5.0 3.5, 4.1, and 5.0

11.31 4.1 and higher 4.1 and higher

HP-UX IA64 11.23 3.5, 4.1, and 5.0 3.5, 4.1, and 5.0

11.31 4.1 and higher 4.1 and higher

Red Hat Enterprise Linux 4.0 x86-64 4.1 to 5.0MP3RP3 4.1 to 5.0MP3RP3
(AS)

IA64 4.1 to 4.1MP4RP4 4.1 to 4.1MP4RP4

POWER 5.0 LoP phase1, 5.0 LoP phase1, phase2

phase2, and phase 3
only

Red Hat Enterprise Linux 5.0 x86-64 LxRT4.1MP4 and LxRT4.1MP4RP1 and higher
(AS) higher on the 4.1 on the 4.1 line, 5.0MP3 and
line, 5.0MP3 and higher on the 5.0 line
higher on the 5.0 line

IA64 LxRT4.1MP4 and 4.1MP4RP1 and higher in

higher on the 4.1 the 4.1 code line only
code line only

POWER 5.0RU3 and 5.0RU4 5.0RU3 and higher

only

Solaris (SPARC) 9 5.1SP1 and higher 5.1SP1 and higher

10 4.1 MP2 and higher 4.1 MP2 and higher

28 Product Dependencies
VxFS and VxVM compatible versions

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

Operating system OS Version Version of VxFS Version of VxVM Notes

SUSE Linux Enterprise Server x86-64 4.1MP3 and higher in 4.1MP3 and higher in 4.1
10 4.1 codeline. 5.0MP3 codeline. 5.0MP3 and
and higher on 5.0 higher on 5.0 codeline.
codeline.

IA64 4.1MP3 and higher in 4.1MP3 and higher in 4.1

4.1 codeline only. codeline only.

POWER 5.0RU3 and 5.0RU4 5.0RU3 and higher

only

SUSE Linux Enterprise Server x86-64 5.0RU1 and higher 5.0RU1 and higher
11

IA64 NA NA

POWER 5.0RU4 and higher 5.0RU4 and higher

Windows 2003 x86-32 NA 4.3 and higher

Windows 2003 x86-64 NA 4.3 and higher

Windows 2008 x86-32 NA 5.0 and higher

Windows 2008 x86-64 NA 5.0 and higher

Windows 2008 R2 x86-64 NA 5.1 SP1 and higher

NetBackup has improved its integration with the Veritas File System (VxFS)
product to ensure interoperability on all compatible VxFS versions. If you run a
VxFS version that is older than VxFS 4.0 then y9ou need to install new VxFS
libraries on the client to back up the systems that run VxFS. You can search and
download the appropriate VxFS libraries to your system from Patch Central on
the Symantec Support Web site.
See, https://sort.symantec.com/labs/patch.
See, http://entsupport.symantec.com/docs/320193.
Table 3-3 Shows the integration improvements that were made between the
various operating systems and the Veritas File System (VxFS).
 Product Dependencies 29
VxFS and VxVM compatible versions

Table 3-3 Improved Integration with Veritas File System (VxFS)

Operating system OS Version VxFS 5.0 VxFS 4.1 VxFS 3.5

AIX 5.3 X NA NA

HP-UX PA-RISC 11.11 NA NA X

11.23 X NA NA

11.31 X NA NA

HP-UX IA64 11.23 X X NA

11.31 X NA NA

Red Hat Enterprise Linux 4.0 x86-64 X NA NA

(AS)

Red Hat Enterprise Linux 5.0 x86-64 X NA NA

(AS)

SUSE Linux Enterprise Server x86-64 X NA NA

SLES 10

IA64

SUSE Linux Enterprise Server x86-64 X NA NA

SLES 11

IA64

Solaris (SPARC) 9 X NA NA

10 X X NA
30 Product Dependencies
VxFS and VxVM compatible versions
 Chapter 4
Operational Notes and
Issues
This chapter includes the following topics:

■ About NetBackup 7.1.0.1 Operational Notes

■ About general NetBackup 7.1.0.1 notes

■ About NetBackup OpsCenter limitations

■ About NetBackup for VMware

About NetBackup 7.1.0.1 Operational Notes

This 7.1.0.1 Maintenance Release is based on the NetBackup 7.1 release. That
means the operational notes that were documented in NetBackup 7.1 may still
apply to this release. Therefore, you should review that document if you have any
questions or issues with this maintenance release.
http://www.symantec.com/docs/DOC3412
The following sections contain the known operational notes that apply to this
release.
There may be additional changes and updates to this document after it has been
released for General Availability. To see the latest information about this release,
you can download the following document from the Symantec Support Web site.
http://www.symantec.com/docs/DOC3941
32 Operational Notes and Issues
About general NetBackup 7.1.0.1 notes

About general NetBackup 7.1.0.1 notes

The following operational notes pertain to the general functionality of this release
of NetBackup.
■ A change was made to ensure that you can use THROTTLE_BANDWIDTH on
your windows master server.
With NetBackup 7.1, if you set the THROTTLE_BANDWIDTH on your windows
master server with any value, the NetBackup Job Manager (NBJM) would crash.
The result was a status 50 error code on all jobs.
A change was made to address this issue. If you were to encounter this issue,
do not configure THROTTLE_BANDWIDTH.
■ On AIX systems, you may receive an "Out of memory error" error.
On AIX systems, if you issue a java command on the installed folder you may
receive a warning that the java application that is installed encountered an,
"Out of memory error". If you receive this error message, run the ulimit -d
unlimited command resolve this issue. All of the policies are activated and
de-activated properly.
■ During an installation or upgrade to 7.1.0.1 you may encounter, "cannot access"
messages.
When you install NetBackup 7.1.0.1 or upgrade from NetBackup 7.1 to 7.1.0.1
on HP-UX, AIX, and Solaris, servers, you may encounter the following access
errors. This issue pertains to upgrades on either the master or the media
servers.

Extracting PDDE server package (/usr/openv/pddeserver.tar.gz)...

Saving configuration files.
cp: cannot access /usr/openv/pdde/pdconfigure/etc/init.d/SuSE/pdservice
cp: cannot access /tmp/pdinstall_filebackup/pdservice

You can safely ignore these messages. They do not affect the installation or
upgrade of NetBackup 7.1.0.1.
■ Optimized duplication fails between PDDO to PDDO with media write error
(84) on AIX and Solaris 10 x86_64.
That issue applies to environments that run NetBackup 7.1 with a PureDisk
6.6.1, PureDisk 6.6.1.1, and PureDisk 6.6.1.2 deduplication agent on AIX or
Solaris 10 x86_64 platforms. In these environments, optimized duplication
fails with a media write error of 84.
If you encounter this issue, contact Symantec Technical Support to request a
fix.
■ For NetBackup Deduplication Engine users:
 Operational Notes and Issues 33
About NetBackup OpsCenter limitations

Following the installation of NetBackup 7.1.0.1, you may find that some
deduplication services are not started. The services in question are “NetBackup
Deduplication Engine” and “NetBackup Deduplication Manager”. Please start
these services after the installation completes to restore deduplication
operations. You can start the services with the Windows SCM console or
through bpup.exe.
■ If you use bp.kill_all to shut down an HP-IA media server you may receive
a prompt to shut down nbrmms. If you continue and shutdown the NetBackup
services you may encounter a core-dump issue. This issue does not affect the
functionality.
■ Vault jobs can end with a status 26 error after the duplication jobs complete.
The Vault-specific functionality completes successfully. However, an error
occurs when a shared resource is shut down because two modules use it at the
same time.
■ A firewall timeout setting may cause communication problems between
NetBackup LiveUpdate processes. If you encounter communications issues
during a LiveUpdate process, manually increase the firewall timeout.
■ On AIX systems, you may encounter the following error when you extract the
NetBackup 7.1.0.1 client patch.

Cannot write data extracted with the tar command:

A file cannot be larger than the value set by ulimit.

To resolve this issue, temporarily reset the file limit to unlimited by executing
the following command:
ulimit, -f unlimited

■ When you use LiveUpdate, the nbmtrans process may core dump.
After LiveUpdate completes and a nbmtrans process is still running, you should
terminate the nbmtrans process. If you do not terminate the process, it
continues to run and eventually consumes all of the system CPU time.

About NetBackup OpsCenter limitations

The following operational notes pertain to NetBackup's OpsCenter.

General NetBackup OpsCenter notes

The following list contains the known issues that pertain to NetBackup OpsCenter
for this release.
34 Operational Notes and Issues
About NetBackup OpsCenter limitations

■ You cannot install the OpsCenter 7.1 Language Pack after you install OpsCenter
7.1.0.1. If you attempt to install the OpsCenter 7.1 Language Pack after you
have installed NetBackup 7.1.0.1 on Windows, the installer displays the
following error message and quits:
The Release Update version must be the same as Language Pack
version. You must use Language Pack 0.1.

If you have already obtained the NetBackup 7.1.0.1 Language Pack , please
perform one of the following:
■ If you have not installed 7.1 Language Pack but already installed 7.1.0.1,
you must install the 7.1.0.1 Language Pack.
■ If you have not installed 7.1.0.1 but already installed 7.1 Language Pack,
you must uninstall the 7.1 Language Pack first and then install NetBackup
7.1.0.1 followed by the 7.1.0.1 Language Pack.
If you have not obtained the 7.1.0.1 Language Pack yet, please perform one of
the following:
■ Wait to upgrade to NetBackup 7.1.0.1 until the 7.1.0.1 Language Pack is
available.
■ If you have already installed 7.1.0.1, you must uninstall it, then install the
7.1 Language Pack, and then install NetBackup 7.1.0.1 again.
A mismatch between an English base product and a language pack may result
in a fatal error.
Symantec plans to release OpsCenter 7.1.0.1 Language Pack on the Symantec
support Web site within a few weeks after OpsCenter 7.1.0.1.
Symantec strongly recommends that you wait to upgrade to 7.1.0.1 until the
7.1.0.1 Language Pack is available, unless you need to upgrade to 7.1.0.1
immediately.
■ After you configure the OpsCenter 7.1.0.1 agent, the NetBackup master server
version appears as 7.1 instead of 7.1.0.1.
■ Before upgrading to OpsCenter 7.1.0.1, ensure that the drive or volume on
which the OpsCenter database resides has three times as much free space as
the current OpsCenter database. For example if your OpsCenter 7.1 database
size (vxpmdb.db and symOpscache.db) is 1 GB and you want to upgrade to
OpsCenter 7.1.0.1, the specific drive, or volume on which the OpsCenter
database resides must have at least 3 GB of available space.

Note: Once you install and start using OpsCenter 7.1.0.1, the database grows,
and requires more space.
 Operational Notes and Issues 35
About NetBackup OpsCenter limitations

■ When you use OpsCenter to collect data from a PureDisk server and then
restart the OpsCenter services or processes, the data collection does not restart.
That applies to both Windows and UNIX.
To start data collection again after restarting the OpsCenter services, you must
edit the specific data collector and enable the data collection explicitly.
To start data collection for the PureDisk server :
■ Log on to the OpsCenter console.
■ In the OpsCenter console, click Settings > Configuration > Agent.
■ On the Agent list, expand the Integrated Agent to view the specific data
collector for the PureDisk server.
■ Select a check box in front of the data collector.
■ Click Edit Data Collector.
■ Check if the data collection status is enabled. If the data collection is
disabled, enable it. Select Enabled from the Data Collection Status
drop-down list.
■ Click Save.

About uninstalling OpsCenter 7.1 before you install OpsCenter 7.1.0.1

on UNIX
If you have installed OpsCenter 7.1.0.1 and want to uninstall OpsCenter 7.1 from
the system, Symantec recommends that you first uninstall OpsCenter 7.1.0.1.
That applies to both OpsCenter Server and OpsCenter Agent. If you uninstall
OpsCenter 7.1 before you uninstall OpsCenter 7.1.0.1, you need to perform the
steps in the following sections.
■ Uninstalling OpsCenter Server 7.1 before uninstalling OpsCenter Server 7.1.0.1
■ Uninstalling OpsCenter Agent 7.1 before uninstalling OpsCenter Agent 7.1.0.1

Uninstalling OpsCenter Server 7.1 before uninstalling OpsCenter Server

7.1.0.1
When you try to uninstall OpsCenter Server 7.1, before you uninstall OpsCenter
Server 7.1.0.1, the installer prompts you with the following message:
Do you want to uninstall package SYMCOpsCenterPatch7101 from <host_name>
which is dependent on package SYMCOpsCenterServer? [y,n,q,?] (n)
The default option is ‘n’ here. You must type ‘y’ to uninstall OpsCenter Server
7.1.0.1 before 7.1.
36 Operational Notes and Issues
About NetBackup OpsCenter limitations

Note: : In case you enter ‘n’ for this prompt, only the OpsCenter Server 7.1 gets
uninstalled and dependent 7.1.0.1 package entries are left. These package entries
must be manually removed from the system if you want to reinstall OpsCenter
Server 7.1.0.1.

The installer also prompts you about any other dependent packages if applicable.
You can select the default option (n) for any additional prompts. For example, you
may see the following prompt:
Do you want to uninstall package VRTSOpsCenterLegacyAgent from
<host_name> which is dependent on package VRTSpbx? [y,n,q,?] (n)
You can type ‘n’ and proceed as you need to uninstall the OpsCenter Agent
separately.
To remove any dependent 7.1.0.1 package entries, remove the
OpsCenterServerPatch directory. The OpsCenterServerPatch directory is located
in /var/symantec.
If you have not followed the uninstall procedure correctly, you may get the
following error message, while reinstalling OpsCenter Server 7.1.0.1.
CPI ERROR V-9-0-0 Patch entry verification failed. It looks that earlier patch
uninstallation did not completed properly.
You need to manually uninstall the OpsCenter 7.1.0.1 components. Before manually
uninstalling OpsCenter 7.1.0.1, first confirm if that the OpsCenter Server 7.1.0.1
is still installed.
 Operational Notes and Issues 37
About NetBackup OpsCenter limitations

1 Run the following commands for specific platforms, to first confirm that
OpsCenter 7.1.0.1 is still installed.

Linux rpm -q SYMCOpsCenterPatch7101

Solaris pkginfo SYMCOpsCenterPatch7101

HP-UX swlist SYMCOpsCenterPatch7101

AIX lslpp -l SYMCOpsCenterPatch7101

2 When it is confirmed that OpsCenter Server 7.1.0.1 is installed, run the

following commands for specific platforms to uninstall the patch from your
system.

Linux rpm -e SYMCOpsCenterPatch7101

rpm -e SYMCOpsCenterServer

Solaris pkgrm SYMCOpsCenterPatch7101

pkgrm SYMCOpsCenterServer

HP-UX swremove -x enforce_dependencies=false -x

mount_all_filesystems=false SYMCOpsCenterPatch7101

swremove -x enforce_dependencies=false -x
mount_all_filesystems=false SYMCOpsCenterServer

AIX installp -u SYMCOpsCenterPatch7101

installp -u SYMCOpsCenterServer

3 Then run the following command: rm -f

/var/symantec/OpsCenterServerPatch

Uninstalling OpsCenter Agent 7.1 before uninstalling OpsCenter Agent

7.1.0.1
When you try to uninstall OpsCenter Agent 7.1, before you uninstall OpsCenter
Agent 7.1.0.1, the installer prompts you with the following message:
Do you want to uninstall package SYMCOpsCenterAgentPatch7101 from
<host_name> which is dependent on package SYMCOpsCenterAgent? [y,n,q,?]
(n)
The default option is ‘n’ here. You must type ‘y’ to uninstall OpsCenter Agent
7.1.0.1 before 7.1. Note: In case you enter ‘n’ for this prompt, only the OpsCenter
38 Operational Notes and Issues
About NetBackup OpsCenter limitations

Agent 7.1 gets uninstalled and dependent 7.1.0.1 package entries remain. These
package entries must be manually removed from the system if you want to reinstall
OpsCenter Agent 7.1.0.1.
The installer also prompts you about any other dependent packages if applicable.
You can select the default option (n) for any additional prompts. For example, you
may see the following prompt:
Do you want to uninstall package VRTSOpsCenterLegacyServer from
<host_name> which is dependent on package VRTSpbx? [y,n,q,?] (n)
You can type ‘n’ and proceed as you need to uninstall the OpsCenter Agent
separately. To remove any dependent 7.1.0.1 package entries, remove the
OpsCenterAgentPatch directory. The OpsCenterAgentPatch directory is located
in /var/symantec.
If you have not followed the uninstall procedure correctly, you may get the
following error message, while installing OpsCenter 7.1.0.1 again.
CPI ERROR V-9-0-0 Patch entry verification failed
You need to manually uninstall the OpsCenter 7.1.0.1 components. Before manually
uninstalling OpsCenter 7.1.0.1, first confirm if that the OpsCenter Agent 7.1.0.1
is still installed.
 Operational Notes and Issues 39
About NetBackup OpsCenter limitations

1 Run the following commands for specific platforms, to confirm that OpsCenter
7.1.0.1 is still installed.

Linux rpm -q SYMCOpsCenterAgentPatch7101

Solaris pkginfo SYMCOpsCenterAgentPatch7101

HP-UX swlist SYMCOpsCenterAgentPatch7101

AIX lslpp -l SYMCOpsCenterAgentPatch7101

2 Once it is confirmed that OpsCenter Agent 7.1.0.1 is installed, run the

following commands for specific platforms to uninstall the patch from your
system.

Linux rpm -e SYMCOpsCenterAgentPatch7101

rpm -e SYMCOpsCenterAgent

Solaris pkgrm SYMCOpsCenterAgentPatch7101

pkgrm SYMCOpsCenterAgent

HP-UX swremove -x enforce_dependencies=false -x

mount_all_filesystems=false
SYMCOpsCenterAgentPatch7101

swremove -x enforce_dependencies=false -x
mount_all_filesystems=false SYMCOpsCenterAgent

AIX installp -u SYMCOpsCenterPatch7101

installp -u SYMCOpsCenterAgent

3 Then run the following command:rm -f

/var/symantec/OpsCenterAgentPatch

About planning an OpsCenter Agent deployment

Before deploying an OpsCenter Agent, you must decide if you need an OpsCenter
Agent. To make this decisision, you must examine the following parameters:

Do I need an Agent? See “When do you need an Agent?”

on page 40.

Can a single Agent can monitor multiple See “Can a single Agent monitor different
product versions? product versions?” on page 41.
40 Operational Notes and Issues
About NetBackup OpsCenter limitations

Should I install the Agent on the product See “Where should I install the Agent?”
host? on page 41.

Should I install the Agent on a different

platform?

Quickly glance through the Agent See “About the Agent deployment matrix”
deployment matrix on page 45.

Examples of Agent deployment scenarios See “Examples of OpsCenter Agent

deployment in a NetBackup environment”
on page 46.

When do you need an Agent?

You require an Agent based on the product that you want to collect data from.
You do not need an OpsCenter Agent to collect data from PureDisk.

NetBackup The requirement for an OpsCenter Agent

differs for each NetBackup version. Review
the following points for specific NetBackup
versions:

■ 6.0.x
Install an Agent if you want to collect
data for image, error logs, or capacity
license.
■ 6.5.x
Install an Agent if you want to collect
data for image, error log, scheduled jobs,
capacity license, or breakup jobs.
■ 7.0.x
Install an Agent if you want to collect
data for breakup jobs and capacity
license.
■ 7.1.x
Install an Agent if you want to collect
data for capacity license.

PureDisk You do not require an OpsCenter Agent to

collect data from PureDisk. If you installed
the VBR Agent only to collect PureDisk data,
you must manually uninstall it.

IBM TSM, Backup Exec, Enterprise Vault, You require OpsCenter Agent to collect data
Legato Networker from these products.
 Operational Notes and Issues 41
About NetBackup OpsCenter limitations

Can a single Agent monitor different product versions?

A single Agent can monitor multiple versions of TSM, BE, EV. For EMC Networker
and NetBackup master servers, you need separate Agents depending on the
versions.

NetBackup You need separate Agents to collect data from different

NetBackup master servers. NetBackup binaries (such as the
Remote Administration Console for Windows and a UNIX
media server) that you install on the Agent host must match
the version of the NetBackup master server.

EMC Networker You need different OpsCenter Agents for EMC Networker
servers with different versions. The OpsCenter Agent needs
to be installed on the EMC Networker server host.

PureDisk PureDisk data collection does not require a separate Agent.

You can use the Integrated Agent of the OpsCenter Server
for data collection. To create or configure the data collector,
select the Agent that is installed as the Integrated Agent.
Note: You do not require an OpsCenterAgent to collect data
from PureDisk. If you installed the VBR Agent only to collect
PureDisk data, manually uninstall the VBR Agent.

Backup Exec You can use the same Agent to collect data from Backup
Exec servers with different versions.
Note: To collect data from a Backup Exec server host, you
need to install the Agent on a compatible Windows host.

IBM TSM You can use the same OpsCenter Agent to collect data from
TSM servers with different versions.

Enterprise Vault You can use the same OpsCenter Agent to collect Enterprise
Vault data from Microsoft SQL Servers with different
versions.
Note: To collect Enterprise Vault archive data, you must
install the OpsCenter Agent on a Windows host.

Where should I install the Agent?

Installing the OpsCenter Agent has a little affect on the backup environment. The
OpsCenter Agent must be compatible with the Operating System of the backup
application host. To monitor Enterprise Vault or Backup Exec, you need to install
the Agent on a Windows host as these products support only Windows platform.
42 Operational Notes and Issues
About NetBackup OpsCenter limitations

Agents can be installed on either Windows or Solaris platforms if you want to

monitor NetBackup, Tivoli Storage Manager or EMC Networker.
You can deploy the OpsCenter Agent on any of the following: hosts:

Product host The Product host is the host where the

backup or archiving product is installed. For
example, a product host can be a NetBackup
master server, a Backup Exec host, an
Enterprise Vault host etc.
Note: To collect data from EMC Networker,
you must install the OpsCenter Agent on the
product host only.

Advantages of installing OpsCenter Agent

on a product host are the following:

■ Ease of maintenance for upgrades,

because you only service one host.
■ Minimal intrusion on backup hosts,
because only one agent is installed on a
backup host.

Disadvantages of installing OpsCenter Agent

on the product host are the following:

■ The Agent may use significant system

resources, which can affect the product
host’s performance.
 Operational Notes and Issues 43
About NetBackup OpsCenter limitations

OpsCenter Server host or a separate host

44 Operational Notes and Issues
About NetBackup OpsCenter limitations

The OpsCenter Agent can be installed on a

host different from the product host; this is
sometimes called a Remote Agent. The
different host may be the OpsCenter Server
host or a separate host.

You should deploy a Remote Agent in the

following situations:

■ When the OpsCenter Agent is not

compatible with the operating system of
the product (such as HP-UX).
■ When the product host system has
insufficient resources to support
co-location of the OpsCenter Agent and
the backup application.

In such situations, the Agent should

remotely communicate with backup
products.
Note: EMC Networker does not support
Remote Agent.

Advantages of installing OpsCenter Agent

on the Server host or a separate host are the
following:

■ You do not have to install additional

software on backup application hosts,
because the backup data is gathered
remotely.
■ If you install Agent on the OpsCenter
Server host, you need to maintain only
one host for both the OpsCenter Agent
and the Server, which avoids the
maintenance that might otherwise be
involved in upgrading the Agent.

Disadvantages of installing OpsCenter Agent

on the Server host include the following:

■ You must install a component of the

backup application on the OpsCenter
Server host.
For example, assume that you need
separate OpsCenter Agents to collect data
from different versions of NetBackup
master servers. You need to install
NetBackup binaries (the Remote
 Operational Notes and Issues 45
About NetBackup OpsCenter limitations

Administration Console for Windows, the

master server, or the media server) on
the Agent host that match the version of
the NetBackup master server.
■ In some situations, a backup application
license key is required for the component
that is installed on the OpsCenter Server
host.

Note the following points about installing an OpsCenter Agent:

■ Only one OpsCenter Agent can be installed on any host.
■ A single Agent can be configured for multiple data collectors which collect
data from the respective product hosts.
■ Agent for NetBackup needs binaries of either RAC (Remote Admin Console)
or master/media server, installed local to the Agent. The version of RAC or
master/media server binaries installed on the Agent host should match the
version of the NetBackup master server it intends to monitor.
■ If you want to collect data from EMC Networker host, you must install an Agent
locally on the EMC Networker host.

About the Agent deployment matrix

Table 4-1 compiles Agent-related information for each backup product. This can
help you in deploying the OpsCenter Agent.

Table 4-1 Agent deployment matrix

Product Is an Agent Can a single Should Agent Can Agent be

Required? Agent monitor be deployed on installed on
multiple the product any platform?
product host?
versions?

NetBackup 7.1 Required only Multiple Agents Anywhere Solaris,

for capacity Windows
licensing

NetBackup 7.0.x Required for Multiple Agents Anywhere Solaris,

breakup jobs Windows
and capacity
licensing
46 Operational Notes and Issues
About NetBackup OpsCenter limitations

Table 4-1 Agent deployment matrix (continued)

Product Is an Agent Can a single Should Agent Can Agent be

Required? Agent monitor be deployed on installed on
multiple the product any platform?
product host?
versions?

NetBackup 6.5.x Required only Multiple Agents Anywhere Solaris,

for image, Windows
error log,
scheduled
jobs, capacity
licensing, or
breakup jobs.

NetBackup 6.0.x Required only Multiple Agents Anywhere Solaris,

for image, Windows
capacity
licensing, or
error logs.

PureDisk Not Required None None Solaris,

Windows

Backup Exec Required Single Agent Anywhere Windows only

Enterprise Vault Required Single Agent Anywhere Windows only

IBM Tivoli Storage Required Single Agent Anywhere Solaris,

Manager Windows

EMC Networker Required Multiple Agents On the product Solaris,

host Windows

Examples of OpsCenter Agent deployment in a NetBackup

environment
In a NetBackup environment, the following OpsCenter deployment scenarios are
valid:
■ You install the OpsCenter Server on OpsCenterHost1, install the Agent on
AgentHost1, and install a NetBackup 7.1 master server on ProdHost1.
Install the NetBackup 7.1 Remote Administration Console or NetBackup master
server on AgentHost1 and configure a data collector to collect data from
ProdHost1.
 Operational Notes and Issues 47
About NetBackup OpsCenter limitations

■ You install the OpsCenter Server and Agent on OpsCenterHost1 and install
the NetBackup 7.0 master server on ProdHost1.
Install the NetBackup 7.0 Remote Administration Console or the NetBackup
master server on OpsCenterHost1 and configure a data collector to collect data
from ProdHost1.

■ You install the OpsCenter Server on OpsCenterHost1, and you install the
NetBackup master server and the OpsCenter Agent on ProdHost1
Configure a data collector on OpsCenterHost1 to collect data from ProdHost1.

■ You install the OpsCenter Server and Agent on OpsCenterHost1, the NetBackup
6.5 master server is installed on ProdHost1, and you install another NetBackup
6.5 master server on ProdHost2.
Install either the Remote Administration Console or master server on
OpsCenterHost1 and configure two data collectors: one to collect data from
ProdHost1 and another to collect data from ProdHost2.

■ You install the OpsCenter Server on OpsCenterHost1. You install Agent A1 on

AgentHost1, install Agent A2 on AgentHost2, and install Agent3 on
AgentHost3. A NetBackup 7.0 master server exists on ProdHost1 and you
install a NetBackup 6.5 master server on ProdHost2. Install NetBackup 6.0
MP7 on ProdHost3 and ProdHost4.
Install a NetBackup 7.0 Remote Admin Console or 7.0 master server on
AgentHost1 and configure a data collector to collect data from ProdHost1.
Install a NetBackup 6.5 Remote Administration Console or 6.5 master server
on the AgentHost2 and configure a data collector to collect data from
ProdHost2. Install a NetBackup 6.0 MP7 Remote Admin Console or 6.0 MP7
on AgentHost3 and configure a data collector from ProdHost3 and ProdHost4.

■ You install the OpsCenter Server on OpsCenterHost1. You install Agent A1 on

AgentHost1, install Agent A2 on AgentHost2, and install agent A3 on
AgentHost3. A NetBackup 7.0 master server exists on ProdHost1 and you
install a NetBackup 6.5 master server on ProdHost2. NetBackup 6.0 MP7 master
servers exist on ProdHost3 and ProdHost4.
Install a NetBackup 7.0 Remote Admin Console or 7.0 master server on
AgentHost1 and configure a data collector to collect data from ProdHost1.
Install a NetBackup 6.5 Remote Administration Console or 6.5 master server
on the AgentHost2 and configure a data collector to collect data from
ProdHost2. Install either the Remote Administration Console or master server
on AgentHost3 and configure two data collectors: one to collect data from
ProdHost3 and another to collect data from ProdHost4.
48 Operational Notes and Issues
About NetBackup for VMware

About NetBackup for VMware

The following operational notes pertain to NetBackup's VMware feature:
■ Please note the following limitations regarding VCB and VMware Converter
Standalone:
■ VMware Converter Standalone 4.0.1 is the last revision to support VCB.
■ For a virtual machine that was backed up with VCB, VMware Convertor
Standalone cannot restore the VM to a vCenter server that contains vApps.
To use Converter Standalone, you must restore the virtual machine directly
to an ESX or ESXi server. For more information, refer to the following
VMware knowledge base article:
http://kb.vmware.com/selfservice/microsites/search.do?language=en
US&cmd=displayKC&externalid=1034316

Note: NetBackup support for VCB will be discontinued in a future release.

■ Starting with NetBackup 7.0 EEB 2152331, NetBackup speeds up restores of

virtual machines over the SAN by converting a thin-provisioned virtual
machine to thick provisioned. It uses the VMware eager zeroed feature to
reduce communication overhead with the vCenter server. If you do not want
NetBackup to automatically convert every restored virtual machine to thick
provisioning, you can override that setting with the following registry change.
To prevent automatic conversion of a restored VMware virtual machine to
thick provisioning:
■ On the Windows desktop of the backup host, click Start > Run and enter
regedit.
■ To be on the safe side, make a backup of the current registry (File > Export).
■ Go to HKEY_LOCAL_MACHINE > SOFTWARE > Veritas > NetBackup >
CurrentVersion > Config and create a key called BACKUP (if the key does
not already exist).
■ Create a new DWORD under BACKUP, called NoEagerlyScrub.
This registry key causes NetBackup to retain the original provisioning when
the virtual machine is restored.

Note: If the restore is performed over a SAN, the restore may take more time
as a result of this change.
 Operational Notes and Issues 49
About NetBackup for VMware

■ If a virtual machine had an ISO file mounted on a CD when the virtual machine
was backed up, the ISO file must be available on the target ESX server when
you restore the VM. If the ISO file is not available on the ESX server, the restore
fails.
A fix for this problem was issued in NetBackup EEB 2221887 and in later EEB
bundles. You can now configure NetBackup to omit the ISO file when the VM
is restored:
■ On the Windows desktop of the backup host, click Start > Run and enter
regedit.
■ To be on the safe side, make a backup of the current registry (File > Export).
■ Go to HKEY_LOCAL_MACHINE > SOFTWARE > Veritas > NetBackup >
CurrentVersion > Config and create a key called BACKUP (if the key does
not already exist).
■ Create a new DWORD under BACKUP, called IgnoreAttachedDevices.
This registry key allows NetBackup to restore the virtual machine without
attempting to restore an ISO file that was mounted when the virtual machine
was backed up.

Note: If the virtual machine was backed up with VCB, you can use the Remove
backing information... Option on the NetBackup Restore Marked Files dialog.
You do not have to create a registry key.

■ vStorage backups of VMware virtual machines in ESX 4.0 or earlier may fail
due to a timeout issue with VMware Tools. The bpfis log may contain messages
similar to the following:

16:25:01.616 [3236.1656] <2> onlfi_vfms_logf: INF - vmwareLogger:

CreateContainerView: CreateFilter OK
16:25:01.616 [3236.1656] <2> onlfi_vfms_logf: INF - vmwareLogger:
WaitForFilterUpdates: timeout=2 secs
16:25:03.629 [3236.1656] <2> onlfi_vfms_logf: INF - vmwareLogger:
WaitForFilterUpdates: No Updates received
...
16:25:03.629 [3236.1656] <2> onlfi_vfms_logf: INF - vmwareLogger:
CheckConnection: SSL connection NULL
16:25:03.629 [3236.1656] <2> onlfi_vfms_logf: INF - vmwareLogger:
CheckConnection: Invalid soap socket
16:25:03.675 [3236.1656] <2> onlfi_vfms_logf: INF - dovSphereDisconnect:
disconnect for l1-p-ch-w-vcs01 completed with flags 0 and status 0
50 Operational Notes and Issues
About NetBackup for VMware

16:25:03.675 [3236.1656] <2> onlfi_vfms_logf: INF - find_vm_by_displayname:

vmcGetObjDetails failed with status 18

To correct this problem, make the following registry changes on the Windows
server where nbuVmwareTools runs:
■ Click Start > Run and enter regedit.
■ To be on the safe side, make a backup of the current registry (File > Export).
■ Go to HKEY_LOCAL_MACHINE\SOFTWARE\Symantec\SymVmTools.
■ Create the following DWORD values:
SymVmToolsRefreshTimeout (Set the value to 4000, and incrementally
by 1000 if 4000 is not sufficient)
SymVmToolsDisableRefresh (Set the value to 1.)
■ Re-run the backup.

■ In some cases, individual files that were restored from a backup of a VMware
virtual machine do not contain all the original data. This restore problem is
limited to the virtual machine backups that are made with the
FlashBackup-Windows policy type.
This problem can occur in the following versions of NetBackup: 7.0, 7.0.1, 7.1,
and 7.1.0.1.
To work around this issue, restore the entire virtual machine to an alternate
location and manually copy the files from the restored virtual machine.
 Appendix A
About the current release
content index
This appendix includes the following topics:

■ About the NetBackup 7.1.0.1 master Etrack index list

About the NetBackup 7.1.0.1 master Etrack index list

This section contains a master index for all fixes that this release contains. These
fixes are sorted according to the containers that they are in.
52 About the current release content index
About the NetBackup 7.1.0.1 master Etrack index list
 Appendix B
About the current release
content
This appendix includes the following topics:

■ About release content conventions

■ About NetBackup 7.1.0.1 release content

■ NetBackup 7.1.0.1 Emergency Engineering Binary (EEB) Listing

About release content conventions

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

About NetBackup 7.1.0.1 release content

Etrack Incident: 2357588
■ TITAN cases: 414-462-381
■ Contained in: NBLU_7.1.0.1.UNIX NBLU_7.1.0.1.WIN NB_7.1.0.1
NB_7.1.0.1.winnt.IA64 NB_7.1.0.1.winnt.x64 NB_7.1.0.1.winnt.x86
NB_CLT_7.1.0.1
■ Description:
With NetBackup 7.1, if you set the THROTTLE_BANDWIDTH on your windows
master server with any value, the NetBackup Job Manager (NBJM) would crash.
The result was a status 50 error code on all jobs.
■ Work around:
If you encounter this issue, do not configure any properties in the
THROTTLE_BANDWIDTH.
Etrack Incident: 2323825
■ Associated Primary Etrack: 2085582
■ TITAN cases: 412-398-163 413-376-163
■ Contained in: NBLU_7.1.0.1.WIN NB_7.1.0.1.winnt.IA64 NB_7.1.0.1.winnt.x64
NB_7.1.0.1.winnt.x86
■ Description:
In newer Windows 2008 servers, hardware vendors have made use of uEFI
partitions. This change caused System State Backups to end with a status 1
error in NetBackup.
To resolve this issue, a new switch was added to the following w2koption
command:
w2koption -backup -efi_boot_enabled 1
This enabled NetBackup to successfully backup a uEFI partition.
Etrack Incident: 2330386
■ Contained in: NBLU_7.1.0.1.UNIX NBLU_7.1.0.1.WIN NB_OPS_CTR_7.1.0.1
NB_OPS_CTR_7.1.0.1.winnt.IA64 NB_OPS_CTR_7.1.0.1.winnt.x64
NB_OPS_CTR_7.1.0.1.winnt.x86
■ Description:
A change was added to ensure that the drives are listed in the Filter selection.
Etrack Incident: 2332509 2366812
 About the current release content 55
About NetBackup 7.1.0.1 release content

■ Contained in: NBLU_7.1.0.1.UNIX NBLU_7.1.0.1.WIN NB_7.1.0.1

NB_7.1.0.1.winnt.IA64 NB_7.1.0.1.winnt.x64 NB_7.1.0.1.winnt.x86
NB_CLT_7.1.0.1
■ Description:
A fix was added to address intermittent bpcd connection failures on Windows.
■ Work around:
For more information about this issue, see the following Technote on the
Symantec Support Web site:
http://www.symantec.com/docs/TECH154279

Etrack Incident: 2336766

■ Associated Primary Etrack: 2091735
■ TITAN cases: 412-163-484 412-444-954
■ Contained in: NBLU_7.1.0.1.UNIX NB_CLT_7.1.0.1
■ Description:
A fix was made to address an issue that caused bpbkar to core dump. Running
a FlashBackup backup with the VxFS_Snapshot snapshot method on HP-UX
IA64 11.23 caused the issue.
Etrack Incident: 2330407
■ Associated Primary Etrack: 2302641
■ TITAN cases: 413-466-349
■ Contained in: NBLU_7.1.0.1.UNIX NBLU_7.1.0.1.WIN NB_OPS_CTR_7.1.0.1
NB_OPS_CTR_7.1.0.1.winnt.IA64 NB_OPS_CTR_7.1.0.1.winnt.x64
NB_OPS_CTR_7.1.0.1.winnt.x86
■ Description:
A change was made to ensure that the agent communication alert is generated
appropriately.
Etrack Incident: 2374129
■ Contained in: NBLU_7.1.0.1.UNIX NBLU_7.1.0.1.WIN NB_7.1.0.1
NB_7.1.0.1.winnt.IA64 NB_7.1.0.1.winnt.x64 NB_7.1.0.1.winnt.x86
NB_CLT_7.1.0.1
■ **Description:
If you performed a duplication to a remote master server, the source copy
cannot span disk volumes.
■ Additional Notes:
56 About the current release content
About NetBackup 7.1.0.1 release content

In general, you should use only one disk volume in a disk pool if it is the source
of a replication. The storage device may have different replication targets for
different volumes.
Etrack Incident: 2330402
■ Associated Primary Etrack: 1730578
■ TITAN cases: 312-190-408
■ Contained in: NBLU_7.1.0.1.UNIX NBLU_7.1.0.1.WIN NB_OPS_CTR_7.1.0.1
NB_OPS_CTR_7.1.0.1.winnt.IA64 NB_OPS_CTR_7.1.0.1.winnt.x64
NB_OPS_CTR_7.1.0.1.winnt.x86
■ Description:
Data collection fixes were added for the TSM agent. The fixes that added
support for SQL Backtrack jobs and corrected the ability to identify successful
jobs.
Etrack Incident: 2323835
■ Associated Primary Etrack: 2140816
■ TITAN cases: 412-488-706
■ Contained in: NBLU_7.1.0.1.WIN NB_7.1.0.1.winnt.IA64 NB_7.1.0.1.winnt.x64
NB_7.1.0.1.winnt.x86
■ Description:
A change was made to address an issue that caused the following message to
appear randomly when backing up files.

WIN32 13 The data is invalid

This issue did not seem to affect the files. Each time the files were copied from
a SAN-attached drive to a directory on the local drive (C:), they were backed
up successfully.
Etrack Incident: 2318457
■ Associated Primary Etrack: 2195085
■ TITAN cases: 413-103-601
■ Contained in: NBLU_7.1.0.1.WIN NB_7.1.0.1.winnt.IA64 NB_7.1.0.1.winnt.x64
NB_7.1.0.1.winnt.x86
■ Description:
A mapped, FullVM backup failed to define the drive letter on the three Windows
2000 VM guest computers. That caused a status 13 error. This issue generally
occurred with a guest Windows VM that was upgraded from Windows NT to
a later version of Windows. A change was added to address this issue.
 About the current release content 57
About NetBackup 7.1.0.1 release content

Etrack Incident: 2330387

■ Contained in: NBLU_7.1.0.1.UNIX NBLU_7.1.0.1.WIN NB_OPS_CTR_7.1.0.1
NB_OPS_CTR_7.1.0.1.winnt.IA64 NB_OPS_CTR_7.1.0.1.winnt.x64
NB_OPS_CTR_7.1.0.1.winnt.x86
■ Description:
Clicking the Edit button under Configuration - Settings - Tape Library caused
an unknown exception to occur.
Etrack Incident: 2330400
■ Associated Primary Etrack: 2116530
■ TITAN cases: 412-514-562
■ Contained in: NBLU_7.1.0.1.UNIX NBLU_7.1.0.1.WIN NB_OPS_CTR_7.1.0.1
NB_OPS_CTR_7.1.0.1.winnt.IA64 NB_OPS_CTR_7.1.0.1.winnt.x64
NB_OPS_CTR_7.1.0.1.winnt.x86
■ Description:
NetBackup OpsCenter would send alerts for (master server) services on a media
server that is not running.
Etrack Incident: 2333580
■ Associated Primary Etrack: 2293764
■ TITAN cases: 414-024-076
■ Contained in: NBLU_7.1.0.1.UNIX NBLU_7.1.0.1.WIN NB_7.1.0.1
NB_7.1.0.1.winnt.IA64 NB_7.1.0.1.winnt.x64 NB_7.1.0.1.winnt.x86
NB_CLT_7.1.0.1
■ Description:
A change was made to address an issue that caused bptm to core dump when
you restored the images that were created before NetBackup 7.0. Upgrading
from pre-NetBackup 7.0 versions to NetBackup 7.0.1 or 7.1 caused this issue.
The problem also occurred if multiple media servers were running different
NetBackup versions.
Etrack Incident: 2330415
■ Associated Primary Etrack: 2230003
■ TITAN cases: 413-379-510
■ Contained in: NBLU_7.1.0.1.UNIX NBLU_7.1.0.1.WIN NB_OPS_CTR_7.1.0.1
NB_OPS_CTR_7.1.0.1.winnt.IA64 NB_OPS_CTR_7.1.0.1.winnt.x64
NB_OPS_CTR_7.1.0.1.winnt.x86
■ Description:
58 About the current release content
About NetBackup 7.1.0.1 release content

A change was made to ensure that the VxUL logging turns off when the
configuration file was set to a zero.
Etrack Incident: 2364337
■ Contained in: NBLU_7.1.0.1.UNIX NBLU_7.1.0.1.WIN NB_7.1.0.1
NB_7.1.0.1.winnt.IA64 NB_7.1.0.1.winnt.x64 NB_7.1.0.1.winnt.x86
NB_CLT_7.1.0.1
■ Description:
A change was made to address an issue that caused nbsl to core dump.
Etrack Incident: 2369367 2333006
■ Associated Primary Etrack: 2217961
■ TITAN cases: 413-194-002
■ Contained in: NBLU_7.1.0.1.UNIX NBLU_7.1.0.1.WIN NB_7.1.0.1
NB_7.1.0.1.winnt.IA64 NB_7.1.0.1.winnt.x64 NB_7.1.0.1.winnt.x86
NB_CLT_7.1.0.1
■ Description:
Performing a Catalog Recovery from the second copy of an SLP-duplicated
backup failed. A change was added to address this issue.
Etrack Incident: 2278597
■ Associated Primary Etrack: 2279662
■ Contained in: NBLU_7.1.0.1.UNIX NBLU_7.1.0.1.WIN NB_7.1.0.1
NB_7.1.0.1.winnt.IA64 NB_7.1.0.1.winnt.x64 NB_7.1.0.1.winnt.x86
NB_CLT_7.1.0.1
■ Description:
A change was made to address an issue that caused NetBackup 7.1 to stop
processing storage lifecycle Policies in a high-image backlog. Refer to the
following document on the Symantec Support Web site for more information:
http://www.symantec.com/docs/TECH153976

Etrack Incident: 2330411

■ Associated Primary Etrack: 2304675
■ TITAN cases: 600-681-762
■ Contained in: NBLU_7.1.0.1.UNIX NBLU_7.1.0.1.WIN NB_OPS_CTR_7.1.0.1
NB_OPS_CTR_7.1.0.1.winnt.IA64 NB_OPS_CTR_7.1.0.1.winnt.x64
NB_OPS_CTR_7.1.0.1.winnt.x86
■ Description:
 About the current release content 59
About NetBackup 7.1.0.1 release content

A fix was made ensure that the Image Copy information was updated correctly
in the database.
Etrack Incident: 2329685
■ Associated Primary Etrack: 1932799
■ Contained in: NBLU_7.1.0.1.UNIX NBLU_7.1.0.1.WIN NB_7.1.0.1
NB_7.1.0.1.winnt.IA64 NB_7.1.0.1.winnt.x64 NB_7.1.0.1.winnt.x86
NB_CLT_7.1.0.1
■ Description:
A change was made to address an issue that caused SLP to not mark an Image
as complete. That occurred if no fragments were found for the source copy.
Etrack Incident: 2330398
■ Associated Primary Etrack: 2131583
■ TITAN cases: 412-574-912
■ Contained in: NBLU_7.1.0.1.UNIX NBLU_7.1.0.1.WIN NB_OPS_CTR_7.1.0.1
NB_OPS_CTR_7.1.0.1.winnt.IA64 NB_OPS_CTR_7.1.0.1.winnt.x64
NB_OPS_CTR_7.1.0.1.winnt.x86
■ Description:
The Viewbuilder's Locate in tree menu option always returned unassigned
tree message.
Etrack Incident: 2330406
■ Associated Primary Etrack: 2290281
■ TITAN cases: 413-850-636
■ Contained in: NBLU_7.1.0.1.UNIX NBLU_7.1.0.1.WIN NB_OPS_CTR_7.1.0.1
NB_OPS_CTR_7.1.0.1.winnt.IA64 NB_OPS_CTR_7.1.0.1.winnt.x64
NB_OPS_CTR_7.1.0.1.winnt.x86
■ Description:
The Media SubType was set incorrectly for a Tape storage unit . This caused
incorrect data to be displayed in the reports. A change was made to correct
this issue.
Etrack Incident: 2323832
■ Associated Primary Etrack: 2144387
■ TITAN cases: 412-444-133 412-782-690 413-141-944 413-504-092
■ Contained in: NBLU_7.1.0.1.WIN NB_7.1.0.1.winnt.IA64 NB_7.1.0.1.winnt.x64
NB_7.1.0.1.winnt.x86
60 About the current release content
About NetBackup 7.1.0.1 release content

■ Description:
In Windows 2008 and 2008 R2, backups of All_Local_Drives, System State,
and Shadow Copy occasionally failed with a status 156 on clusters. Microsoft
made changes to back up all targets of service which resulted in this error.
A change was made to add a new switch to the W2KOption:
w2koption -backup -ignore_unresolved_paths drive_letter:
Where drive_letter: is the drive that is inaccessible but contains a part of System
State.
Etrack Incident: 2332411
■ Associated Primary Etrack: 2207639
■ TITAN cases: 413-201-525 413-564-951 414-184-936 414-415-138
■ Contained in: NBLU_7.1.0.1.UNIX NBLU_7.1.0.1.WIN NB_7.1.0.1
NB_7.1.0.1.winnt.IA64 NB_7.1.0.1.winnt.x64 NB_7.1.0.1.winnt.x86
NB_CLT_7.1.0.1
■ Description:
NBEMM may crash on a NetBackup clustered master server with a heavy load
of backup jobs and a high number of media servers configured. A thread race
condition caused this issue.
Etrack Incident: 2321322
■ Associated Primary Etrack: 2304679
■ TITAN cases: 414-050-629 414-086-864 414-105-766 600-675-666
■ Contained in: NBLU_7.1.0.1.UNIX NBLU_7.1.0.1.WIN NB_7.1.0.1
NB_7.1.0.1.winnt.IA64 NB_7.1.0.1.winnt.x64 NB_7.1.0.1.winnt.x86
NB_CLT_7.1.0.1
■ Description:
A hot catalog backup failed with a status error 2 on Windows media servers.
The bpdbm log file contained the following entries:

00:11:05.513 [5232.5780] <2> get_long: (1) cannot read (byte 1) from network

Etrack Incident: 2330404

■ Associated Primary Etrack: 2237550
■ TITAN cases: 413-169-839
■ Contained in: NBLU_7.1.0.1.UNIX NBLU_7.1.0.1.WIN NB_OPS_CTR_7.1.0.1
NB_OPS_CTR_7.1.0.1.winnt.IA64 NB_OPS_CTR_7.1.0.1.winnt.x64
NB_OPS_CTR_7.1.0.1.winnt.x86
 About the current release content 61
About NetBackup 7.1.0.1 release content

■ Description:
An attempt to include more than 50 error codes in the All Failed Backup report
caused the following error.

An error occurred while a fetch operation ran the report output.

Etrack Incident: 2330873

■ Associated Primary Etrack: 2260072
■ TITAN cases: 413-587-150
■ Contained in: NBLU_7.1.0.1.UNIX NBLU_7.1.0.1.WIN NB_7.1.0.1.winnt.IA64
NB_7.1.0.1.winnt.x64 NB_7.1.0.1.winnt.x86 NB_CLT_7.1.0.1
■ Description:
A change was made to ensure that the connection between the client and the
bprd process on a master does not timeout when using the bparchive, command
with the -w option.
Etrack Incident: 2336768
■ Associated Primary Etrack: 2204126
■ TITAN cases: 413-170-214
■ Contained in: NBLU_7.1.0.1.UNIX NBLU_7.1.0.1.WIN NB_OPS_CTR_7.1.0.1
NB_OPS_CTR_7.1.0.1.winnt.IA64 NB_OPS_CTR_7.1.0.1.winnt.x64
NB_OPS_CTR_7.1.0.1.winnt.x86
■ Description:
The Week At A Glance reports were not presented properly or they were blank
when it was added to "My Dashboard".
Etrack Incident: 2330584 2358878
■ Contained in: NBLU_7.1.0.1.UNIX NBLU_7.1.0.1.WIN NB_7.1.0.1
NB_7.1.0.1.winnt.IA64 NB_7.1.0.1.winnt.x64 NB_7.1.0.1.winnt.x86
NB_CLT_7.1.0.1
■ **Description:
If you attempted to configure a single disk volume (OST storage server and
LSU) with more than one NetBackup Master Server, and that disk volume is a
replication target, there is a potential for the master servers to consume each
other's images.
NOTE: If the master servers that share this disk volume both have the SLP
name defined and that name is used for the Automatic Image Replication, you
could experience a data loss. This change addresses this issue to ensure that
you do not encounter a data loss.
62 About the current release content
About NetBackup 7.1.0.1 release content

■ Work around:
To avoid this issue, never share a single disk volume between multiple master
servers.
Etrack Incident: 2326390
■ Associated Primary Etrack: 2241381
■ TITAN cases: 413-389-844
■ Contained in: NBLU_7.1.0.1.UNIX NBLU_7.1.0.1.WIN NB_7.1.0.1.winnt.IA64
NB_7.1.0.1.winnt.x64 NB_7.1.0.1.winnt.x86 NB_CLT_7.1.0.1
■ **Description:
A change was made to ensure that you could restore virtual machines even if
a virtual disk (vmdk) was larger than one Terabyte.
Etrack Incident: 2375434
■ Contained in: NBLU_7.1.0.1.WIN NB_7.1.0.1.winnt.IA64 NB_7.1.0.1.winnt.x64
NB_7.1.0.1.winnt.x86
■ Description:
Using the Intelligent policy possible values button for the resource pool,
caused libpivmware to crash.

Etrack Incident: 2329585

■ Associated Primary Etrack: 2242465
■ TITAN cases: 413-521-169
■ Contained in: NBLU_7.1.0.1.UNIX NBLU_7.1.0.1.WIN NB_JAV_7.1.0.1
NB_JAV_7.1.0.1.winnt.IA64 NB_JAV_7.1.0.1.winnt.x64
NB_JAV_7.1.0.1.winnt.x86
■ Description:
If you changed the password in the Change virtual machine server field in
the NetBackup-Java administration console, the backward slash character "\",
was removed from the account name. A change was added to address this issue.
Etrack Incident: 2327022
■ Associated Primary Etrack: 2310939
■ TITAN cases: 414-131-888
■ Contained in: NBLU_7.1.0.1.UNIX NBLU_7.1.0.1.WIN NB_7.1.0.1
NB_7.1.0.1.winnt.IA64 NB_7.1.0.1.winnt.x64 NB_7.1.0.1.winnt.x86
NB_CLT_7.1.0.1
■ Description:
 About the current release content 63
About NetBackup 7.1.0.1 release content

A change was made to address an issue that caused the vxazd_debug.log log
file to grow exponentially after you enabled NBAC on a NetBackup 7.1 clustered
master server and then opened the NetBackup Administration Console .
■ Work around:
If you encounter this issue, set the debug level of the adf module (adf_debug)
of AZ to the default of zero (0).
Etrack Incident: 2347792 2343530 2341660
■ Contained in: NBLU_7.1.0.1.UNIX NBLU_7.1.0.1.WIN NB_7.1.0.1
NB_7.1.0.1.winnt.IA64 NB_7.1.0.1.winnt.x64 NB_7.1.0.1.winnt.x86
NB_CLT_7.1.0.1
■ Description:
If you use the nirvanix_e storage server type to configure Nirvanix with
encryption, the storage server cannot be created. The encryption plug-in caused
the nbrmms service to go down.
In addition, another issue existed that caused the restored data to differ from
the backed up data when the bptm SIZE_DATA_BUFFERS is changed to a value
that does not match the 16K encryption boundaries. An example of that would
be if SIZE_DATA_BUFFERS were set to 130048 (127K).
Etrack Incident: 2347050
■ Contained in: NBLU_7.1.0.1.WIN NB_7.1.0.1.winnt.IA64 NB_7.1.0.1.winnt.x64
NB_7.1.0.1.winnt.x86
■ Description:
A change was made to address an issue that caused the VM to not start after
a Full VM restore.
Etrack Incident: 2320573
■ Contained in: NBLU_7.1.0.1.WIN NB_7.1.0.1.winnt.IA64 NB_7.1.0.1.winnt.x64
NB_7.1.0.1.winnt.x86
■ **Description:
A change was made to address an issue that caused mount point resolution to
fail on an RHEL6 VM with an IDE disk attached. This issue meant that users
were not able to perform single-file restores (SFR) for the volumes whose
mount points were incorrectly resolved. The change that was made fixes this
issue and creates the proper mount points.
■ Work around:
If you encounter this issue, use the UUID in the fstab entries.
Etrack Incident: 2330420
■ Associated Primary Etrack: 2235314
64 About the current release content
About NetBackup 7.1.0.1 release content

■ TITAN cases: 413-517-604

■ Contained in: NBLU_7.1.0.1.UNIX NBLU_7.1.0.1.WIN NB_OPS_CTR_7.1.0.1
NB_OPS_CTR_7.1.0.1.winnt.IA64 NB_OPS_CTR_7.1.0.1.winnt.x64
NB_OPS_CTR_7.1.0.1.winnt.x86
■ Description:
A change was made to ensure that the Custom tabular report displays the
hardware column as numerical.
Etrack Incident: 2330384
■ Associated Primary Etrack: 2195494
■ TITAN cases: 412-772-095
■ Contained in: NBLU_7.1.0.1.UNIX NBLU_7.1.0.1.WIN NB_OPS_CTR_7.1.0.1
NB_OPS_CTR_7.1.0.1.winnt.IA64 NB_OPS_CTR_7.1.0.1.winnt.x64
NB_OPS_CTR_7.1.0.1.winnt.x86
■ Description:
Changes were added to this release of NetBackup to address the following
issues:
■ A Time Schedule with the following parameters never caused the report
to be emailed or exported. The affected schedule pattern was Daily, Every
weekday. Other parameters do not matter.
■ A server-side exception occurred whenever the weekly time schedule was
changed to daily (every weekday), or the number of days selected were
reduced in weekly time schedule. For example, create a time schedule on
a weekly basis and select Monday and Tuesday. Now, update the time
schedule and select only Monday. The report is not saved.
■ The yearly time schedule did not work properly.

Etrack Incident: 2337525

■ Contained in: NBLU_7.1.0.1.WIN NB_7.1.0.1.winnt.IA64 NB_7.1.0.1.winnt.x64
NB_7.1.0.1.winnt.x86
■ Description:
Mount point resolution on RHEL6 VM that have IDE and SCSI disks attached
failed and caused a data loss issue to occur. If one IDE disk was attached
followed by SCSI disks, volume resolution of the non-lvm volumes that reside
in SCSI disks failed. A single file restore cannot be performed from these
volumes and lead to the data loss issue.
■ Work around:
To resolve this issue, use UUID for all non-lvm volumes in fstab entries.
 About the current release content 65
About NetBackup 7.1.0.1 release content

Etrack Incident: 2330413

■ Associated Primary Etrack: 2297481
■ TITAN cases: 413-536-205
■ Contained in: NBLU_7.1.0.1.UNIX NBLU_7.1.0.1.WIN NB_OPS_CTR_7.1.0.1
NB_OPS_CTR_7.1.0.1.winnt.IA64 NB_OPS_CTR_7.1.0.1.winnt.x64
NB_OPS_CTR_7.1.0.1.winnt.x86
■ Description:
The client version information would get updated incorrectly with NULL data
if the client was not reachable.
Etrack Incident: 2318483
■ Associated Primary Etrack: 2260757
■ Contained in: NBLU_7.1.0.1.UNIX NBLU_7.1.0.1.WIN NB_7.1.0.1
NB_7.1.0.1.winnt.IA64 NB_7.1.0.1.winnt.x64 NB_7.1.0.1.winnt.x86
NB_CLT_7.1.0.1
■ Description:
The image metadata fragment for AIR images was written too late. That caused
the image to have the wrong vm_type when the image is validated.
Etrack Incident: 2330421
■ Associated Primary Etrack: 2229203
■ TITAN cases: 412-802-372
■ Contained in: NBLU_7.1.0.1.UNIX NBLU_7.1.0.1.WIN NB_OPS_CTR_7.1.0.1
NB_OPS_CTR_7.1.0.1.winnt.IA64 NB_OPS_CTR_7.1.0.1.winnt.x64
NB_OPS_CTR_7.1.0.1.winnt.x86
■ Description:
A change was made to ensure that Drive Utilization for restores displays the
appropriate data.
Etrack Incident: 2328141
■ Associated Primary Etrack: 2324501
■ TITAN cases: 414-203-357
■ Contained in: NBLU_7.1.0.1.WIN NB_OPS_CTR_7.1.0.1.winnt.IA64
NB_OPS_CTR_7.1.0.1.winnt.x64 NB_OPS_CTR_7.1.0.1.winnt.x86
■ Description:
A change was made to address an issue that caused the OpsCenter Agent service
to occasionally crash and cause the data collection to fail for some of the BE
servers.
66 About the current release content
About NetBackup 7.1.0.1 release content

Etrack Incident: 2323834

■ Associated Primary Etrack: 2118074
■ TITAN cases: 412-571-306 413-238-895
■ Contained in: NBLU_7.1.0.1.WIN NB_7.1.0.1.winnt.IA64 NB_7.1.0.1.winnt.x64
NB_7.1.0.1.winnt.x86
■ Description:
The bpbkar32.exe executable produced an Application Fault during dfsr
backups on Windows 2008 and 2008R2 systems. Full backups worked and took
about 30 minutes to complete, however, Incremental backups failed
intermittently. The Incremental backups did write some data before they failed
with a status 13 error.
A change was made to ensure that the bpbkar32.exe executable was fixed and
no longer caused the status 13 error.
Etrack Incident: 2357326
■ Contained in: NBLU_7.1.0.1.WIN NB_7.1.0.1.winnt.IA64 NB_7.1.0.1.winnt.x64
NB_7.1.0.1.winnt.x86
■ Description:
A change was made to ensure that you could perform a restore to a Clustered
ESX server.
Etrack Incident: 2273462
■ Contained in: NBLU_7.1.0.1.UNIX NB_7.1.0.1 NB_CLT_7.1.0.1
■ Description:
The bp.start_all script attempted to start a couple of daemons that are
master server only on a media server. This action showed some failure messages
that should not have occurred.
Etrack Incident: 2314618
■ Contained in: NBLU_7.1.0.1.UNIX NBLU_7.1.0.1.WIN NB_7.1.0.1
NB_7.1.0.1.winnt.IA64 NB_7.1.0.1.winnt.x64 NB_7.1.0.1.winnt.x86
NB_CLT_7.1.0.1
■ Description:
This release contains fixes to address the following issues:
■ A memory leak with vnet_fqdn() (refer also to ET2291609).
■ Problems that were identified with LIMIT_BANDWIDTH (refer also to
ET2273461).
■ Memory leak fixes for the host cache (refer also to ET2294837).
 About the current release content 67
About NetBackup 7.1.0.1 release content

Etrack Incident: 2363578

■ Contained in: NBLU_7.1.0.1.WIN NB_7.1.0.1.winnt.IA64 NB_7.1.0.1.winnt.x64
NB_7.1.0.1.winnt.x86
■ Description:
A change was made to address an issue that caused bpbkar.exe to core dump
when an attempt was made to restore a folder from an MS-Windows NAS data
mover (NDMP) snapshot backup copy.
Etrack Incident: 2330394
■ TITAN cases: 413-301-662
■ Contained in: NBLU_7.1.0.1.UNIX NBLU_7.1.0.1.WIN NB_OPS_CTR_7.1.0.1
NB_OPS_CTR_7.1.0.1.winnt.IA64 NB_OPS_CTR_7.1.0.1.winnt.x64
NB_OPS_CTR_7.1.0.1.winnt.x86
■ Description:
The runStoredQuery.bat exports report to the temp location on the server
and not in the location mentioned under Settings - Configuration - Report
Export Location tab.
Etrack Incident: 2318478
■ Associated Primary Etrack: 2281383
■ TITAN cases: 600-671-484
■ Contained in: NBLU_7.1.0.1.WIN NB_7.1.0.1.winnt.IA64 NB_7.1.0.1.winnt.x64
NB_7.1.0.1.winnt.x86
■ Description:
In some rare cases a portion of a virtual machine is cataloged as having a
zero-byte count. That occurred because the actual file is small. In those cases
a restore of the virtual machines could fail with a Status 5.
A change was added to prevent the above case from happening.
■ Additional Notes:
If you encounter an issue when attempting to restore virtual machines , please
contact Technical Support for assistance.
Etrack Incident: 2330392
■ Contained in: NBLU_7.1.0.1.UNIX NBLU_7.1.0.1.WIN NB_OPS_CTR_7.1.0.1
NB_OPS_CTR_7.1.0.1.winnt.IA64 NB_OPS_CTR_7.1.0.1.winnt.x64
NB_OPS_CTR_7.1.0.1.winnt.x86
■ Description:
A fix was added to address a server-side exception that occurred while clicking
Manage - Devices - Robot
68 About the current release content
About NetBackup 7.1.0.1 release content

Etrack Incident: 2330403

■ Associated Primary Etrack: 2290432
■ TITAN cases: 414-013-773
■ Contained in: NBLU_7.1.0.1.UNIX NBLU_7.1.0.1.WIN NB_OPS_CTR_7.1.0.1
NB_OPS_CTR_7.1.0.1.winnt.IA64 NB_OPS_CTR_7.1.0.1.winnt.x64
NB_OPS_CTR_7.1.0.1.winnt.x86
■ Description:
A change was made to address an issue that caused the nom_robotCap view to
not work.
Etrack Incident: 2330399
■ Associated Primary Etrack: 2254196
■ TITAN cases: 413-679-610
■ Contained in: NBLU_7.1.0.1.UNIX NBLU_7.1.0.1.WIN NB_OPS_CTR_7.1.0.1
NB_OPS_CTR_7.1.0.1.winnt.IA64 NB_OPS_CTR_7.1.0.1.winnt.x64
NB_OPS_CTR_7.1.0.1.winnt.x86
■ Description:
The View Builder produced a server exception when adding additional objects
to view, for example, copying a node from one tree to another.
Etrack Incident: 2330385
■ Associated Primary Etrack: 2095378
■ TITAN cases: 412-489-876
■ Contained in: NBLU_7.1.0.1.UNIX NBLU_7.1.0.1.WIN NB_OPS_CTR_7.1.0.1
NB_OPS_CTR_7.1.0.1.winnt.IA64 NB_OPS_CTR_7.1.0.1.winnt.x64
NB_OPS_CTR_7.1.0.1.winnt.x86
■ Description:
Data Collection from NetBackup 6.5.x master for Devices would never complete.
In addition, it would prevent other data collections from starting.
Etrack Incident: 2330390
■ Associated Primary Etrack: 2189560
■ TITAN cases: 412-555-864
■ Contained in: NBLU_7.1.0.1.UNIX NBLU_7.1.0.1.WIN NB_OPS_CTR_7.1.0.1
NB_OPS_CTR_7.1.0.1.winnt.IA64 NB_OPS_CTR_7.1.0.1.winnt.x64
NB_OPS_CTR_7.1.0.1.winnt.x86
■ Description:
 About the current release content 69
NetBackup 7.1.0.1 Emergency Engineering Binary (EEB) Listing

The Policy & Schedule collector would fail when an attempt was made to
connect to a master server.
Etrack Incident: 2318473 2319681 2318469 2318501
■ Associated Primary Etrack: 2221913
■ TITAN cases: 413-351-096
■ Contained in: NBLU_7.1.0.1.UNIX NBLU_7.1.0.1.WIN NB_7.1.0.1
NB_7.1.0.1.winnt.IA64 NB_7.1.0.1.winnt.x64 NB_7.1.0.1.winnt.x86
NB_CLT_7.1.0.1
■ Description:
This fix addresses the following issues: - If CD-ROM had an ISO mounted, you
could not restore it to another environment if the ISO did not exist. - The BLIB
Incremental backups would fail if you added an independent disk to a virtual
machine (VM) after full backup. - A change was added to restore performance
when attempting to restore thick-provisioned disks. - A change was made to
decrease the amount of time it took to gather the resource pool data.
Etrack Incident: 2323828
■ Associated Primary Etrack: 2302966
■ TITAN cases: 413-826-630
■ Contained in: NBLU_7.1.0.1.WIN NB_7.1.0.1.winnt.IA64 NB_7.1.0.1.winnt.x64
NB_7.1.0.1.winnt.x86
■ Description:
A fix was added to address an issue that caused the following message and log
file to be missing.
(-528/-528 The current log file is missing)

NetBackup 7.1.0.1 Emergency Engineering Binary

(EEB) Listing
This following table contains the known issues that were identified, fixed, and
available to our customers in the form of an Emergency Engineering Binary (EEB).
NetBackup 7.1.0.1 contains each of these EEBs. It is possible that additional EEBs
were released since this document was posted. If you do not see an EEB that you
expected to see in this document, contact your Symantec NetBackup Support
representative. In addition, if you require additional information about an issue
in this table, contact your Symantec NetBackup Support representative.
70 About the current release content
NetBackup 7.1.0.1 Emergency Engineering Binary (EEB) Listing

Table B-1 NetBackup 7.1.0.1 EEB Listing

Summary
Issue Etrack Number Emergency Engineering Binary Description

S2105122 2299772 This EEB is a 7.1 VMWare bundled EEB that includes changes for the following
Etracks:

■ 2318469 - If CDROM had an ISO mounted, we are unable to restore it to

another environment.
2318473 - BLIB Incremental backups failed when an independent disk was
added to VM after a full backup.
2318501 - Restored performance.
2318457 - A mapped Full VM backup on three Windows 2000 VM Guest
failed to define the drive letter and failed with a Status 13.
2318478 - VCB restore at NetBackup 7.0.1 failed in bprd on several VMs.
2319681 - Resource pool data took too long to gather.

S2316919 2256525 This is the AGENT_WINDOWS Bundle for NetBackup 7.1. This bundle
encompasses the following Etracks:

■ 2256536 - (System state backup of Windows Server 2008 (non-R2) failed

with a status 1 as the system state backup is returning FS_SKIP_OBJECT
when backing up ASR files.) This issue was caused by the implementation
of uEFI boot partition.
■ 2258750 - The bpbkar32.exe executable caused very High CPU Utilization
on Windows 2008 hosts.
■ 2302739 - (The current log file was missing.)
■ 2149421 and 2015296 caused the backup of SCC to end with a status 156
error.
■ 2118052 - The bpbkar32.exe executable produced an application fault
during dfsr backups on Windows 2008 and 2008R2 Core.
■ 2140765 - (WIN32 13 - The data is invalid.)
■ 2174275 - The bpbkar32.exe executable caused the Virtual Disk service
to stop improperly.
■ 2152911 - The Exclude List does not work since upgrading to NetBackup
7.0 or 7.0.1.
 About the current release content 71
NetBackup 7.1.0.1 Emergency Engineering Binary (EEB) Listing

Table B-1 NetBackup 7.1.0.1 EEB Listing (continued)

Summary
Issue Etrack Number Emergency Engineering Binary Description

S2296126 2274411 71/Denali EEB Bundle 1. The bundle contains the following Etracks:

■ 2274405 - Added OpsCenter installer updates.

■ 2095332 - Data Collection from 6.5.x NetBackup master for Devices never
completed and also prevented other data collections from starting.
■ 2189429 - The Policy and Schedule collector failed when trying to connect
to one master server.
■ 2170994 - OC reports invalid device information for invalid media server.
■ 2276132 - Exception occurred while clicking Manage > Devices > Robot.
■ 2276142 - Drives were not being listed in the Filter selection.
■ 2276146 - Resolved an unknown exception when the Edit button under
Configuration > Settings > Tape Library was selected.
■ 2116442 - OpsCenter sent alerts for master server services on a media
server that was not running.
72 About the current release content
NetBackup 7.1.0.1 Emergency Engineering Binary (EEB) Listing

Table B-1 NetBackup 7.1.0.1 EEB Listing (continued)

Summary
Issue Etrack Number Emergency Engineering Binary Description

S2234149 2233961
 About the current release content 73
NetBackup 7.1.0.1 Emergency Engineering Binary (EEB) Listing

Table B-1 NetBackup 7.1.0.1 EEB Listing (continued)

Summary
Issue Etrack Number Emergency Engineering Binary Description

darrieus-pdde-7.0.1-cft-rocksolid EEB delivery

If client-side deduplication is used, this EEB should be installed on the client

and MSDP server. All servers that are MSDP storage pools or can write to a
MSDP storage pool should also have this EEB installed.

■ 2125388 - Content Router queue processing hangs.

■ 2133046 - MSDP to PureDisk duplication failed with no more entries
error.
■ 2134092 - This is a bundled fix that addresses the following etracks:
2056505, 2122278, 2060486, 2064419, 2073172, 2084947, 2047655, 2103459.
■ 2149179 - Duplication jobs end with a Status 83.
■ 2158198 - spoold would not start.
■ 2158839 - Fixes for the Optimized Synthetics error 610 and VMDK
deduplication ratio.
■ 2161303 - A large number of directories in /var/tmp/ starting with pdvfs
caused the hard limit to be reached on the filesystem.
■ 2163275 - Load a fingerprint cache from all fragments of the last full backup.
■ 2175705 - Network Address Translation breaks optimized duplications.
■ 2176416 - Enables perfile deduplication stats to be available.
■ 2183861 - Fix to address status 84 errors on vStorage backups.
■ 2188614 - Low deduplication rates on PDDO backups after upgrading form
6.5.1.2 tp 6.6.1.
■ 2194243 - Duplication from MSDP to PureDisk still used [R]PDDO data
selections and MB imports on destination side.
■ 2196681 - Optimized Duplications are failing with status 84.
■ 2210083 - bptm crashed at pdvfs.
■ 2210707 - Volume Cleanup on MSDP not able to keep up causing a back log
of over 100k fragments to be deleted.
■ 2217383 - Fixed an error in plugin log.
■ 2218085 - Statue error 83 were received on NetBackup backup jobs while
PureDisk is re-routing.
■ 2218137 - MSDP backups failed with status 84 errors.
■ 2219988 - Client-side deduplication failed with the a "Bad file
descriptor" error.
■ 2222209 - tlog processing can retry for days and accumulate a huge tlog
backlog.
■ 2222453 - The tlog delay file is not syncronized to disk, fsync or _commit
was not called.
■ 2222786 - Client-side deduplication backups hang at the begin writing
74 About the current release content
NetBackup 7.1.0.1 Emergency Engineering Binary (EEB) Listing

Table B-1 NetBackup 7.1.0.1 EEB Listing (continued)

Summary
Issue Etrack Number Emergency Engineering Binary Description

process.
■ 2227064 - Restore is incomplete when restoring the synthetic backup image.
■ 2227604 - The scheduler should not exit because of database connection
problems.
■ 2233961 - If client side deduplication is used, this EEB should be installed
on the client and MSDP server. All servers that are MSDP storage pools or
can write to a MSDP storage pool should also have this EEB installed.
■ 2240566 - Optimized deduplication from deduplication storage pool to
PureDisk Deduplication Pool gives a media write error.
■ 2246884 - Byte order is incorrect when receiving MSG_B_DO_NEW at server
side.
■ 2248351 - CRC mismatch in sorted the tlog file.
■ 2248352 - After CRQP was shut down, there were still several new tlog
files arriving.
■ 2252878 - The process queue was not running to completion.
■ 2254913 - The bpdm would core dump in strcmp when the PureDisk plugin
libstspipd.so does a compare_hosts with a NULL IP address.
■ 2259881 - Deduplication storage pool to PureDisk Deduplication Pool image
duplication creates multiple agents on the Deduplication storage pool SPA.
■ 2260910 - Deduplication storage pool to PureDisk Deduplication Pool
duplication has performance issues if both are configured on same media
server.
■ 2275125 - Duplications complete successfully but the destination copy is
incomplete with 6.6.0.3.
■ 2281196 - Queue processing stops working, the tlogs created with a
mismatched filename versus internal tlogid.
■ 2290442 - Cannot restore previously optimized synthetic data.
■ 2315547 - Missing GetRemoteSPA type fails optimized duplication from
MSDP to PureDisk Deduplication Pool if remote data selection ID is not 2.

S2105122 2105102 Requesting view base api for NetBackup 7.0.1

 About the current release content 75
NetBackup 7.1.0.1 Emergency Engineering Binary (EEB) Listing

Table B-1 NetBackup 7.1.0.1 EEB Listing (continued)

Summary
Issue Etrack Number Emergency Engineering Binary Description

S2206135 2206134 AGENT_WINDOWS Bundle for 7.0.1 The bundle contains the following Etracks:

■ 2085561 - "System state backup of Windows Server 2008 (non-R2) fails

with status 1 as system state backup is returning FS_SKIP_OBJECT when
backing up ASR files" issue caused by the implementation of uEFI boot
partition.
■ 2125979 - Windows client exclude list not honored on shared drive of
Microsoft Cluster following upgrade to 7.0 / 7.01
■ 2153889 - Request for EEB with fix for both ET 2125979 and ET 2140536
■ 2146659 - C: drive backups are extremely slow for Windows 2008 Cluster
Server when VSS is enabled
■ 2149421 - ET 2015296 causes backup of SCC to end with Status 156
■ 2174275 - bpbkar32.exe causes the Virtual Disk service to stop improperly.

S2138544 2122784 NetBackup 7.0.1 EEB bundle submission. The bundle contains the following
Etracks:

2197018 2119891 2147977 2168030 2119066 2119864 2112463 2151183

2170089 2118441 2118439 2118444 2173499 2196926 2207649 2118436
2119708 2197019 2121312 2119060 2118740 2118641 2118766 2119068
2113015 2119052 2147365 2176493 2173222 2118161 2118157 2141105
2207633 2134328 2118149 2118152 2118160 2120881 2131582 2175465
2179138 2207335 2118155 2118163 2166839 2166827 2175470 2205490
2215230 2141116 2185598 2185477 2185479 2177908 2218261 2217310
2219429 2216188 2095332 2189429 2203767 2086173 2201832 2166294
2209006 2131550 2116442 2161230 2253017
76 About the current release content
NetBackup 7.1.0.1 Emergency Engineering Binary (EEB) Listing