341279

Veritas NetBackup™ 6.5.
6
Release Notes
UNIX, Windows, and Linux
NetBackup 6.5.6
Veritas NetBackup 6.5.6 Release Notes
The software described in this book is furnished under a license agreement and may be used
only in accordance with the terms of the agreement.
Documentation version: 6.5.6
Legal Notice
Copyright © 2010 Symantec Corporation. All rights reserved.
Symantec, the Symantec Logo, and Veritas 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:
Before contacting Technical Support, make sure you have satisfied the system
requirements that are listed in your product documentation. Also, you should be
at the computer on which the problem occurred, in case it is necessary to replicate
the problem.
When you contact Technical Support, please have the following information
available:
■ Product release level
■ Hardware information
■ Available memory, disk space, and NIC information
■ Operating system
■ Version and patch level
■ Network topology
■ Router, gateway, and IP address information
■ Problem description:
■ Error messages and log files
■ Troubleshooting that was performed before contacting Symantec
■ Recent software configuration changes and network changes
Licensing and registration

If your Symantec product requires registration or a license key, access our technical
support web page at the following URL:
Customer service
Customer service information is available at the following URL:
Customer Service is available to assist with non-technical questions, such as the
following types of issues:
■ Questions regarding product licensing or serialization
■ Product registration updates, such as address or name changes
■ General product information (features, language availability, local dealers)
■ Latest information about product updates and upgrades
■ Information about upgrade assurance and support contracts
■ Information about the Symantec Buying Programs
■ Advice about Symantec's technical support options
■ Nontechnical presales questions
■ Issues that are related to CD-ROMs or manuals
Support agreement resources
If you want to contact Symantec regarding an existing support agreement, please
contact the support agreement administration team for your region as follows:
Asia-Pacific and Japan customercare_apac@symantec.com
Europe, Middle-East, and Africa semea@symantec.com
North America and Latin America supportsolutions@symantec.com
Additional enterprise services

Symantec offers a comprehensive set of services that allow you to maximize your
investment in Symantec products and to develop your knowledge, expertise, and
global insight, which enable you to manage your business risks proactively.
Enterprise services that are available include the following:
Managed Services Managed Services remove the burden of managing and monitoring security
devices and events, ensuring rapid response to real threats.
Consulting Services Symantec Consulting Services provide on-site technical expertise from
Symantec and its trusted partners. Symantec Consulting Services offer a variety
of prepackaged and customizable options that include assessment, design,
implementation, monitoring, and management capabilities. Each is focused on
establishing and maintaining the integrity and availability of your IT resources.
Education Services Education Services provide a full array of technical training, security education,
security certification, and awareness communication programs.
To access more information about enterprise services, please visit our web site
at the following URL:
www.symantec.com/business/services/
Select your country or language from the site index.
Contents
Technical Support ............................................................................................... 4

Chapter 1 About NetBackup 6.5.6 ...................................................... 11
About new supported platforms for NetBackup 6.5.6 .......................... 11
About new feature and enhancements for NetBackup 6.5.6 .................. 12
Decommissioning a media server ............................................. 12
About the VSP disable tool ....................................................... 12
About the catalog recovery synchronization tool ......................... 13
About name resolution and firewall configuration upgrades .......... 13
About status 800 job status enhancements .................................. 14
About NetBackup command line interface updates ....................... 14
About the new multistream_restore parameter ............................ 14
About NetBackup support utilities ............................................. 15
About end-of-life notifications for NetBackup 6.5.6 ............................ 16
Chapter 2 About known issues ............................................................ 17

About platform-specific issues ........................................................ 17
Installation, upgrade, and cluster issues ........................................... 18
NetBackup Access Control issues .................................................... 22
NetBackup Database Agent issues ................................................... 23
NetBackup Enterprise Vault Agent issues ................................... 23
Exchange Granular Recovery issues .......................................... 24
Microsoft Exchange Agent issues .............................................. 25
SharePoint Agent issues .......................................................... 27
NetBackup for SQLserver agent issues ....................................... 30
Other database agent issues ..................................................... 30
Storage-related issues ................................................................... 30
NetBackup user interface issues ...................................................... 35
General NetBackup issues .............................................................. 36
NetBackup Hyper-V issues ............................................................. 46
Bare Metal Restore (BMR) issues ..................................................... 51
NetBackup Operations Manager (NOM) issues ................................... 52
Localization issues ....................................................................... 53
General Documentation issues ....................................................... 53
UNIX-specific issues ..................................................................... 57
8 Contents
Windows-specific issues ................................................................ 58
Chapter 3 Current release content index .......................................... 61

About the NetBackup 6.5.6 master Etrack index list ............................ 61
NB_SMJ_6.5.6.winnt.x64 ......................................................... 61
NB_JAV_6.5.6.winnt.x64 .......................................................... 61
NB_JAV_6.5.6 ........................................................................ 61
NB_NOM_6.5.6.winnt.IA64 ...................................................... 61
NB_SMJ_6.5.6.winnt.x86 ......................................................... 61
NB_NOM_6.5.6 ...................................................................... 62
NB_VLT_6.5.6 ........................................................................ 62
NB_DRO_6.5.6 ....................................................................... 62
NB_SMU_6.5.6 ....................................................................... 62
NB_SAP_6.5.6 ........................................................................ 62
NBLU_6.5.6.WIN .................................................................... 62
NB_6.5.6.winnt.x86 ................................................................ 63
NB_6.5.6 ............................................................................... 64
NB_ORA_6.5.6 ....................................................................... 64
NB_NOM_6.5.6.winnt.x86 ........................................................ 64
NB_JAV_6.5.6.winnt.IA64 ........................................................ 65
NB_DMP_6.5.6 ....................................................................... 65
NB_CLT_6.5.6 ........................................................................ 65
NBLU_6.5.6.UNIX ................................................................... 65
NB_6.5.6.winnt.IA64 ............................................................... 66
NB_NOM_6.5.6.winnt.x64 ........................................................ 67
NB_JAV_6.5.6.winnt.x86 .......................................................... 67
NB_SMJ_6.5.6.winnt.IA64 ........................................................ 67
NB_BMR_6.5.6 ....................................................................... 67
NB_DB2_6.5.6 ........................................................................ 67
NB_6.5.6.winnt.x64 ................................................................ 67
NB_BBS_6.5.6 ........................................................................ 68
NB_SNC_6.5.6 ........................................................................ 68
Chapter 4 Current release content ..................................................... 69

About Release Update conventions .................................................. 69
About NetBackup 6.5.6 Release Content ........................................... 70
Appendix A About NetBackup release history ................................... 159

About previous NetBackup releases ............................................... 159
Master Etrack Index for all previous releases ................................... 160
NetBackup 6.5.5 packaged Etracks for UNIX and Windows ........... 160
Contents 9
NetBackup 6.5.4 UNIX packaged Etracks ................................... 162

NetBackup 6.5.4 Windows packaged Etracks .............................. 167
10 Contents
Chapter 1
About NetBackup 6.5.6
This chapter includes the following topics:
■ About new supported platforms for NetBackup 6.5.6
■ About new feature and enhancements for NetBackup 6.5.6
■ About end-of-life notifications for NetBackup 6.5.6
About new supported platforms for NetBackup 6.5.6

This topic describes the new UNIX and Windows platform being supported in the
NetBackup 6.5.6 release.
For additional platform support information, see the following Technote on the
Symantec Support Web site:
http://entsupport.symantec.com/docs/303344
The following is a comprehensive list of the new UNIX and Windows platforms
contained in this release of NetBackup:
■ This release contains the following new database agent support:
■ Oracle 11g R2
■ DB2 9.7
■ Windows Server 2008 R2 Core (Client Support)

■ Storage Foundation support has been added for the EMC_Timefinder_Snap
FIM, the EMC_Timefinder_Clone FIM, and the EMC_Timefinder_Mirror FIM
on Solaris 9 and 10 platforms and the HP-UX 11.31 platform.
■ This release contains a JRE upgrade for NOM.
12 About NetBackup 6.5.6
About new feature and enhancements for NetBackup 6.5.6
About new feature and enhancements for NetBackup

6.5.6
The following sections describe the NetBackup feature and enhancements that
comprise this release.
For more detailed information about these features, see the NetBackup Document
Updates book. You can use the following Technote to locate this book on the
Symantec Support Web site.
For this release, updates were made to the NetBackup Troubleshooting Guide and
the Troubleshooting Wizard. A new set of status code descriptions has been added
to the guide. In addition, a set of more granular and descriptive status codes
(2000-2104) were included to disambiguate the status code 800 job status. That
enables administrators to more easily troubleshoot allocation problems.
You can find the latest version of the NetBackup Troubleshooting Guide in the
following Technote on the Symantec Support Web site.
Decommissioning a media server

New with this release is a command to decommission a media
server,nbdecommission. The command launches a text-based wizard that guides
you through the decommission process. The wizard removes the references to a
media server from a NetBackup domain.
See the following Technote on the Symantec Support Web site for more
information about this feature:
About the VSP disable tool

NetBackup 6.5.6 automatically installs the Veritas volume snapshot Provider
(VSP) method for Open File Backups. VSP is the default Open File Backup method
in this release.
NetBackup 6.5.6 includes the VSP disable tool (bpvspdisable.exe) for
administrators to use to disable VSP on clients if it is not needed. The tool deletes
the VSP cache files from the disk of the client system. All future VSP requests on
those clients are redirected to use Microsoft native Volume Shadow Copy Service
(VSS).
About NetBackup 6.5.6 13
The VSP method for Open File Backups is not supported in NetBackup 7.0. Having
run the VSP disable tool does not affect upgrading to NetBackup 7.0.
The VSP disable tool can be used on the following operating systems:
■ Windows Server 2000
■ Windows Server 2003 with Service Pack 2 (x86 and IA64)
■ Windows XP 32-bit and 64-bit (x86 and IA64)
About the catalog recovery synchronization tool

The nbcatsync command runs a utility that resyncs the disk media IDs in the
image catalog after catalog recovery operations complete.
After bprecover restores the actual catalog files, the nbcatsync utility can do the
following:
■ Fix the disk media IDs in the fragment records.
■ Mark all recovered images as SS_COMPLETED.
■ Restore disabled functionality.
■ Prune images from the catalog which were not found on any currently
configured disk volumes. The -prune_catalog option deletes catalog entries
for the images that do not exist locally.
■ Constrain the operation to a set of images based on the catalog restore that
was performed.
About name resolution and firewall configuration upgrades

The bptestnetconn command has been added to more effectively troubleshoot
networking errors such as status code 58 errors, Cannot connect to client. This
command performs several tasks that help you analyze DNS connectivity problems
with any specified list of hosts, including the server list in the NetBackup
configuration. To help troubleshoot connectivity problems between the services
that use CORBA communications, bptestnetconn can perform and report on
CORBA connections to named services. It sends VxUL log messages to OID 112
for easy perusal. The vxlogcfg command controls the log verbosity.
About status 800 job status enhancements

In NetBackup 6.5.x, jobs that fail at resource allocation time are often assigned a
status 800 (RESOURCE UNAVAILABLE) job status. There are many underlying reasons
that cause allocations for these jobs to fail. A set of more granular and descriptive
status codes (2000-2104) were included to disambiguate the status code 800 job
status. These new error code descriptions enable the NetBackup administrator to
troubleshoot allocation problems more easily.
About NetBackup command line interface updates

This release contains updates to the following commands that you can run using
the command line interface:
■ bptestnetconn
■ bpimage
■ bplist
■ bprecover
■ bprestore
■ nbcatsync
■ NBCC
■ NBCCR
■ nbdecommission
■ nbdna
■ nbemmcmd
■ nbsu
About the new multistream_restore parameter

The multistream_restore parameter is new with NetBackup 6.5.6. This parameter
is supported for Oracle without RMAN.
For more information, see the following:
Windows http://entsupport.symantec.com/docs/340908
About NetBackup 6.5.6 15
UNIX or Linux http://entsupport.symantec.com/docs/340909
About NetBackup support utilities

NetBackup 6.5.6 includes three support utilities: nbsu, NBCC, and NBCCR. The
following list summarizes the enhancements that have been made to each utility
in this release:
■ NetBackup Support Utility (NBSU)
The NBSU utility assists you in gathering NetBackup and operating system
diagnostic information. This tool queries the host on which it runs and gathers
diagnostic information about NetBackup and the operating system. In addition,
it provides a wide range of control over the types of diagnostic information
gathered. For instance, you can obtain information about NetBackup
configuration settings about troubleshooting areas, or about NetBackup or
media management job status codes.
In NetBackup 6.5.6 this utility has been enhanced to version 1.3 and includes
the following new features:
■ New commands line options have been added.
■ Enhancements were made to the SLP, EMM, and versioninfo diagnostics.
■ This utility is now available for the Mac OS X platform.
In addition to the new enhancements, the support and support.exe diagnostic
information gathering utilities are no longer included or supported beginning
with this release of NetBackup.
■ NBCC utility
The NBCC utility uses the output from various OS and NetBackup commands
to analyze the consistency state of the NetBackup configuration. It also analyzes
the consistency state of NetBackup databases and catalogs as they relate to
tape media. If inconsistencies are detected, NBCC consolidates, and packages
the resulting data into a bundle that can be sent to Symantec Tech Support
for analysis.
This release contains the 7.0 version of this utility. In addition, enhancements
have been made to this utility to ensure that it supports NetBackup 6.5.6.
■ NBCCR utility
The NBCCR utility processes database and catalog repair actions as defined in
a file that you can generate under the guidance of Symantec Technical Support.
This file is created as part of the analysis of the data that the NBCC utility
collects and any site-specific situations.
This release contains the 7.0 version of this utility. In addition, enhancements
have been made to this utility to ensure that it supports NetBackup 6.5.6.
About end-of-life notifications for NetBackup 6.5.6
About end-of-life notifications for NetBackup 6.5.6

This release of NetBackup contains no new end-of-life announcements.
Chapter 2
About known issues
■ About platform-specific issues
■ Installation, upgrade, and cluster issues
■ NetBackup Access Control issues
■ NetBackup Database Agent issues
■ Storage-related issues
■ NetBackup user interface issues
■ General NetBackup issues
■ NetBackup Hyper-V issues
■ Bare Metal Restore (BMR) issues
■ NetBackup Operations Manager (NOM) issues
■ Localization issues
■ General Documentation issues
■ UNIX-specific issues
■ Windows-specific issues
About platform-specific issues

■ For SLES 11 support, make sure that you install PBX from the following image
before installing NetBackup:
NB_65_ICS_1.4.41.5_LinuxX86.zip
18 About known issues
Installation, upgrade, and cluster issues
■ NetBackup can fail on systems running AIX and older versions of the C++
run-time libraries. IBM has released xlC rte 9.0.0.3, a C++ Runtime
Environment Component for AIX. Symantec recommends that you download
and install the latest C++ run-time library and then reboot your server. For
more information about this issue and fix, refer to the following Technote on
the Symantec Support Web site.
■ (ET1534457) If RHEL5.3 Media (CDs) are used for shared resource tree (SRT)
creation, the SRT creation fails with an error message that is similar to the
following:
V-125-380 /var/tmp/bmrmediaDb1K6p/.discinfo(2): expected "Red Hat

Enterprise Linux Server 5", got "Red Hat Enterprise Linux Server 5.3" The
loaded media is not correct...please try again. Unmounting media...ok.
One workaround for this issue is to use the RHEL5.0, 5.1, or 5.2 operating
system media to create a shared resource tree (SRT). You can use SRTs to
restore an RHEL5.3 client. A second workaround for this issue: On the BMR
Boot server, open the /usr/openv/var/global/createsrt.conf file and search
for the string, Red Hat Enterprise Linux Server 5. Replace all the occurrences
of this string with the following string, Red Hat Enterprise Linux Server 5.3.
That should enable the creation of RHEL5.3 SRTs.
NOTE: This workaround disables the ability to create RHEL5.0/5.1/5.2 SRTs.
Because RHEL5.3 introduces the new device drivers that were not a part of the
default kernel in RHEL5.2, Symantec recommends that you use this workaround
to create a RHEL5.3 SRT for restoring RHEL5.3 clients.

■ (ET1890392) The NetBackup 6.5.5 install may hang if the following is true:
■ The $PATH variable is set to use the cp command from GNU coreutils version
7.1.
■ You have downloaded the release updates to a Solaris global files system
You should use the cp command that is a part of the base operating system,
or install the release updates from a local file system.
■ Removing NetBackup versions 6.5.6 and later
When you remove NetBackup from Windows 2008/Vista and later systems, a
dialog box appears. This dialog informs you that PBX is still running and that
it needs to be stopped. When the dialog box appears, Symantec recommends
that you click, Do not close applications. (A reboot will be required.) and
About known issues 19
continue with the NetBackup removal. PBX is stopped and restarted

automatically as needed for removal. Any other installed programs that rely
on PBX are not affected.
■ (ET1967792) If you use the BMR boot server, and you enabled the BMR boot
server option at a time after you have installed the NetBackup current patch,
you may need to install this patch using the following command-line operation.
That updates the BMR boot server files to the current release level. If you do
not install the patch using the appropriate command, the BMR boot server
files may not be patched successfully.
Open a Command window and run the appropriate command:
■ For an x86 system, use the following command operation:
msiexec /l*v c:\install.txt /i "NetBackup Update.msi" /qn
ADDLOCAL=BMR_RU_x86
Where c:\install.txt is the pathname of the installation log.
■ For an x64 system, use the following command operation:
msiexec /l*v c:\install.txt /i "NetBackup Update.msi" /qn
ADDLOCAL=BMR_RU_AMD64
Where c:\install.txt is the pathname of the installation log.
■ (ET1991719) A Windows computer would not come up after a disaster recovery

restore was performed after an ALL_LOCAL_DRIVES backup.
If you encounter an error that is related to the lsass.exe executable, you
should perform another restore first. Next, you should shut down the
NetBackup client service from the services windows and then reboot the system.
■ (ET1595854) When you uninstall NetBackup from a VCS cluster, the VCS Type
is not deleted. If you reinstall NetBackup to the same location, you are not able
to run NetBackup.)
To avoid this problem, use the following procedure to uninstall NetBackup
from a VCS cluster.
Note: The first step applies only to UNIX systems. The remaining steps apply
to UNIX and Windows systems.
■ If it exists, on UNIX systems, remove the following file from the active
node:
/usr/openv/netbackup/bin/cluster/frozen
■ Enter the following command to take the NetBackup resource offline:

hares -offline <resource name> -sys active node
■ After ensuring that all NetBackup processes and services are down, delete
all NetBackup data from the shared disk.
■ Enter the following command to take the NetBackup group offline:

hagrp -offline <group name> -sys active node
■ Enter the following command to change the VCS configuration to R/W

mode:
haconf -makerw
■ Enter the following command to delete the NetBackup group:

hagrp -delete group name
■ Enter the following command to delete the NetBackup resource type:

hatype -delete NetBackup
■ Enter the following command to change the VCS configuration back to R/O
mode:
haconf -dump -makero
■ Uninstall NetBackup from all other nodes in the cluster.
■ (ET2003460) Support for FlashBackup in a Microsoft Cluster (MSCS)

environment
Beginning in NetBackup 6.5 GA, the use of FlashBackup in a Microsoft Cluster
(MSCS) environment is supported, with the following limitation: Raw partition
restores can only be performed when the disk being restored is placed in
extended maintenance mode or removed from the MSCS resource group.
Note: Earlier versions of MSCS (such as those versions that were shipped with
Windows versions before Windows 2003 SP1) do not allow extended
maintenance mode functionality. If the cluster does not support placing disks
in extended maintenance mode, it is still possible to perform raw restores to
an alternate, non-shared disk.
■ The Veritas Private Branch Exchange (PBX) software is installed along with
NetBackup 6.5.x. Depending on how NetBackup is installed, PBX may log
messages by default to the UNIX system logs /var/adm/messages or
/var/adm/syslog, or to the Windows event log. That can cause additional
system logging. The messages that are written to the system logs are the same
as those written to the PBX logs (/opt/VRTSpbx/log on UNIX and
install_path\VxPBX\log on Windows).
To disable PBX logging to the system or the event logs after NetBackup has
been installed, enter the following commands:
UNIX:
cd /opt/VRTSicsco/bin
./vxlogcfg -a -p 50936 -o 103 -s LogToOslog=false
Windows:
cd install_path\VERITAS\VRTSicsco
vxlogcfg -a -p 50936 -o 103 -s LogToOslog=false
It should not be necessary to restart PBX for this setting to take effect. Any
future PBX log information should no longer appear in the system logs.
For more information about this issue or information on how to disable the
option, refer to the following Technote on the Symantec Support Web site.
■ During a Windows server or client installation, if there you encounter a fatal

install error, you should check the installation logs to determine the cause of
the error. If you find a return value of three in the install log similar to the
following example, then you should first open a cmd window. From the
command window, run the following command, and install NetBackup again.
regsvr32 oleaut32.dll
The following is a sample message from the install logs.
setRegistryValues.B2D5B6C9_4698_42F7_AC9D_955789A69556.
04-07-2008,14:32:36 : Action start 14:32:36:
setRegistryValues.B2D5B6C9_4698_42F7_AC9D_955789A69556.
04-07-2008,14:32:36 : Action ended 14:32:36:
setRegistryValues.B2D5B6C9_4698_42F7_AC9D_955789A69556. Return value 3.
■ (ET1917617) The database creation failed on an HP 11.31 IA64 system.

For HP virtual machine (VM) system, the base_pagesize kernel parameter
should be set to a value that is less than 64. The possible values are 4 ,8, 16,
and 64. If you encounter this issue, set this parameter to one of the documented
values and try to install NetBackup again.
■ (ET1988453) The client package may fail to extract to the root drive on
Windows 2008 R2 Server Core systems.
The Windows 2008 R2 Server Core operating system has a security issue with
creating directories on the root drive.
See the following article for more information about the issue:
http://social.msdn.microsoft.com/Forums/en-US/gametechnologiesxna/thread/
ba610c21-a823-4e46-b937-af620f981e22
Because of this issue, the NetBackup client package may not extract on to the
root directory. If you encounter this issue, create another directory on the root
directory and extract and launch the NetBackup package from that directory.
■ (ET1600692) While installing NetBackup in a cluster and making it Highly
Available (HA), if you provide a fully qualified host name (FQHN) when asked
NetBackup Access Control issues
for Virtual name, problems may occur and HA is not successful. You should
not provide a fully qualified name during the configuration. Refer to the
NetBackup High Availability Administrator's Guide for UNIX, Windows, and
Linux at the next major release of NetBackup for more information about this
known issue.
■ (ET1602744/ET1602745) Unable to configure AT after an upgrade to 4.3.42.0.
After you upgrade VRTSat to a newer version, an attempt to reconfigure VxAT
using the /opt/VRTS/install/installat -configure command failed.
To resolve this issue, remove /opt/VRTS/bin/installat and try to reconfigure
VxAT again using the following:
Location of ICSInstaller/authentication/installat
■ (ET1633604 and ET1597077) VRTSpbx is not patched with the newer version
included in NetBackup 6.5.4 package.
If you install Storage Foundation (SF) 5.0MP3 and NetBackup 6.5 on a
NetBackup master and media server, and upgrade to NetBackup 6.5.4 or newer,
the following can occur. The VRTSpbx version may not update to the version
that was packaged with NetBackup.
■ (ET1257102) Before you attempt to install a NetBackup master server on a
Tru64 system the following things must be present on the Tru64 system:
■ Install the latest Internationalization (I18N) patch.
■ Shared Memory Size greater than 60MB. If these two criteria are not met
then basic Backups fail with a status 230 and status 89 error, respectively.
NetBackup Access Control issues

■ (ET1137932) To perform NetBackup restores as a nonadministrative user
under NBAC from the Windows Backup, Archive, and Restore client console
or the Windows Administration Console; set the permissions on the following
directories to Full Control for each user of the user interfaces.
C:\ProgramFiles\Veritas\NetBackup\logs\nbwin
C:\ProgramFiles\Veritas\NetBackup\logs\nbconsole
■ If you use NBAC, you may receive the following warning after you install the
Release Update:
The NetBackup Access Control upgrade failed and must be run
manually. Make sure the Symantec Product Authorization Service is
started and then run: INSTALL_DIRProgram
Files\VERITAS\NetBackup\bin\admincmd\bpnbaz -Upgrade.
Please open up the install log and search for the following:
NetBackup Database Agent issues
NetBackup\bin\admincmd\bpnbaz.exe" -CheckUpgrade.
If you see a message similar to the following, verify the error code value:
■ 10-10-2008,20:10:16 : ERROR in running NBAC Command :
"C:\Program Files\Veritas\NetBackup\bin\admincmd\bpnbaz.exe"
-CheckUpgrade Returned error code: 0 10-10-2008,20:10:16 :
Action ended 20:10:16: NBAC_Upgrade. Return value 1.
■ If the error code is 0 you can ignore this issue altogether.

■ If the error code is something other than 0, then there is an issue and you
should run the command manually on the affected system.
■ (ET1274335) Applicability: Cluster NetBackup with NBAC (Clustered VxAT)

A Hot Catalog backup of clustered NetBackup with NBAC (Clustered VxAT)
does not protect VxAT data stores correctly. Attempting to recover VxSS data
using the command, bprecover -r -vxss -p PolicyName fails to recover the
VxSS environment.

The following sections describe known issues as they relate to the NetBackup
database agents:
■ See “NetBackup Enterprise Vault Agent issues” on page 23.
■ See “Exchange Granular Recovery issues” on page 24.
■ See “Microsoft Exchange Agent issues” on page 25.
■ See “SharePoint Agent issues” on page 27.
■ See “NetBackup for SQLserver agent issues” on page 30.
■ See “Other database agent issues” on page 30.
NetBackup Enterprise Vault Agent issues

■ (ET1500728) An issue exists that can cause the backup of an Index location to
fail if the Index location is configured on the Enterprise Vault server within
the Enterprise Vault environment and there is no enterprise vault install
folder/Reports folder present on the system. If you attempt to back up the
Index location, the backup fails because the enterprise vault install
folder/Reports folder is not present on the host. If this folder is not on the
server, then the discovery job fails and causes the entire backup job to fail.
This folder may not be present on the system if you are only running the
Enterprise Vault Indexing Service on the Enterprise Vault server.
To work around this issue, create the enterprise vault install

folder/Reports folder manually and then run the backup job again.
■ (ET1475102) If you install the Enterprise Vault Agent on a NetBackup client

that has Windows 2008 installed, the NetBackup client properties appear in
READONLYmode. If you encounter this privileges issue, perform the following
steps to disable the user account Control (UAC) check box in Windows 2008:
■ Select Start > Settings > Control Panel > user accounts > Turn
User Account Control ON or OFF.
■ Uncheck the UseUACtohelpprotectyourcomputercheck box (it is checked

by default).
■ (ET1533469 and ET1533488) The Enterprise Vault online Help has not been
updated for the NetBackup 6.5.x release. The next major release of NetBackup
contains the Enterprise Vault online Help .
■ The NetBackup Enterprise Vault agent does not support the following user
interface:
Host Properties > Master Servers > Server name > Enterprise Vault
Hosts
This user interface was created to enable the federated restore feature.
However, existing circumstances prohibit the use of this interface. This user
interface will be supported in a future release of NetBackup.
Exchange Granular Recovery issues

■ A status 1 error may occur for an Exchange Granular-enabled backup job if
the granular processing operations failed to complete successfully. The job
details under the Activity Monitor or error log should indicate one of the
following if this failure caused the status 1:
■ Look at the bpbkar debug log for more information.
■ A legacy (non-VSS) backup still truncates transaction logs if the job ended
with a status 1 because of a granular processing operation failure. In this
situation, the backup image is suitable for database recovery.
■ A Microsoft hotfix is required for "Client for NFS" for windows 2003. You can
locate and request this hotfix for either x86 or x64 platforms at:
http://support.microsoft.com/kb/947186
■ The following application event log message may appear on an Exchange server
during an Exchange granular operation (backup, browse, or restore). You can
safely ignore that message.
Event ID 16384
Description:
The remote server does not have locking support. A mount was
requested with locking enabled. The share is being mounted anyway.
Some functionality may not be available.
■ For Windows 2008 the following applies:

■ Backups and restores that use granular recovery, or Mailbox-level backups
and restores may fail with the MAPI logon error x80040115. Please refer
to the following Technote on the Symantec Support Web site for a solution
to disable IPv6 for MAPI access.
■ The following application event log message may appear on a Windows
2008 Exchange server if a user does not have the Active Directory or the
User Name Mapping identity mapping set up and configured using the
Services for NFS properties. This message occurs during an Exchange
granular operation (backup, browse, or restore) and can safely be ignored.
Event ID 16397
Description:
Windows(R) Lightweight Directory Access Protocol (LDAP) failed
a request to connect to Active Directory Domain Services(R) for
Windows user <DOMAIN\USER>.
Without the corresponding UNIX identity of the Windows user, you cannot
access Network File System (NFS) shared resources. Verify that the Windows
user is in Active Directory Domain Services and has access permissions.
■ The QLogic SAN Surfer software may need to be disabled or uninstalled because
it may conflict with the port mapped for Windows "client for NFS".
Microsoft Exchange Agent issues

■ Launching an off-host snapshot backup from the NetBackup Client or with
bpbackup:
If you attempt to initiate an Exchange off-host alternate client backup from
the NetBackup Client GUI or with the bpbackup command, the backup fails.
Instead, use the NetBackup Administration Console to initiate a manual backup
for that Exchange policy.
See the "Testing configuration settings" section in the NetBackup for Microsoft
Exchange Administrator's Guide for instructions on how to perform a manual
backup.
■ When an Exchange backup is launched from the NetBackup Client interface
and uses the Snapshot Client off-host backup capability, the progress log
window does not display the usual progress messages evident when a scheduled
backup is executed. The lack of progress logging does not affect the backup
operation. If detailed progress is desired, use the NetBackup Administration
Console to launch a manual backup operation on an Exchange policy. See the
"Testing configuration settings" section in the NetBackup for Microsoft
backup operation.
■ For NetBackup 6.5.4, the following configuration changes apply for Exchange
cluster environments:
■ To perform Continuous Cluster Replication (CCR) backups of the passive
VSS writer, you no longer need to set the "Enable Remote Streaming Backup"
registration key.
■ For Exchange 2007 SP1 or later, you no longer need to configure the
NetBackup Client Service to run as domain admin.
■ Launching an off-host snapshot backup from the NetBackup Client or with

bpbackup
If you attempt to initiate an Exchange off-host alternate client backup from
the NetBackup Client GUI or with the bpbackup command, the backup fails.
Instead, use the NetBackup Administration Console to initiate a manual backup
for that Exchange policy. See the "Testing configuration settings" section in
the NetBackup for Microsoft Exchange Administrator's Guide for instructions
on how to perform a manual backup.
■ When an Exchange backup is launched from the NetBackup Client interface
and uses the Snapshot Client off-host backup capability, the progress log
window does not display the usual progress messages evident when a scheduled
backup is executed. This lack of progress logging does not affect the backup
operation. If detailed progress is desired, use the NetBackup Administration
Console to launch a manual backup operation on an Exchange policy.
See the "Testing configuration settings" section in the NetBackup for Microsoft
backup operation.
■ (ET1278383) Exchange 6.5.2 - LCR/CCR backup support
To ensure that the CCR client attributes are set properly for both nodes in the
cluster, update the Exchange client attributes for each node individually.
Changing the attributes for the virtual CCR name only affects the active node
at the time of change.
SharePoint Agent issues

■ If you use a pre-NetBackup 6.5.3 version to back up granular backups for
SharePoint, and you upgrade the media servers to 6.5.3, then you need to also
upgrade the SharePoint clients to 6.5.3.
■ (ET1595100) NetBackup can back up and restore a portal if the IP address is
used instead of the name when it is created. However, using a portal name
instead results in a site-not-being-found condition. That means you have to
perform some steps manually to complete the restore. The databases do get
restored to SQL. Use the SharePoint Central Administrator to Recover a
Portal, the IP for the URL address, and also enter the names of the databases
(SITE, SERV, and PROF) that are restored. After the portal is recreated, use the
SharePoint Central Administrator Manage Content databases for the virtual
server to add any Team Sites that are associated to the Portal Site. These sites
also get backed up and then restored to SQL.
The steps to recover the named URL portal after a restore.
1. Verify that the content databases are restore to SQL.
2. Use SharePoint Central Administrator - List and Manage Portal Sites Restore
a Portal.
3. Select the virtual server and place the names of the SITE, PROF, and SERV
databases in their respective fields.
4. Use the portal IP address for the portal URL site address.
5. If there are additional team sites associated to the portal, use SharePoint
Administrator Virtual Server Manager to Manage Content Databases to add
them back to the portal site.
6. The portal should now be available for browse.
7. Use the IP for the portal site URL address. That should void the need to have
to manually do these steps to recover the site going forward.
■ (ET1527929) Backups of the SharePoint Web applications that contain a large
number of content databases (100+) may timeout. In addition, backups of the
portals that use Granular Recovery Technology (GRT) and contain a large
number of content databases (100+) may timeout. In these situations increase
the default "Client read timeout" setting to 900 seconds.
■ NetBackup for SharePoint policies do not support multiple data streams.
■ The following issues are specific to SharePoint 2007.
■ To view a SharePoint node in Backup, Archive, and Restore user interface
for a SharePoint backup, you must install the Microsoft .NET framework
3.5 on the SharePoint servers.
■ Document-level restores fail if the string "_Granular_" is contained within
the document name. You can restore the document using a full database
restore. To avoid this issue, rename the documents that contain the string
"_Granular_" to a name without the string "_Granular_" before performing
the backing up.
■ (ET1594142) When performing a disaster recovery of a SharePoint web
application and the last restore is complete, verify that the web application
appears in the list of web applications, and then perform an iisreset . You
can perform the iisreset command by opening a command prompt window
and typing the command, iisreset /noforce.
■ (ET1588836) When restoring a Data Connection Library document from a
GRT backup, the documents in the library have the appropriate approval
status however the version history may state that 'This is the current
approved version' when it may not be. The workaround for this issue is to
have the user set the appropriate status for the item.
■ (ET1502252) Restoring a document or a picture library item when the
library or folder does not exist is not restored. The library or folder is not
recreated and the item is not restored The work around for this issue would
be to redirect the restore to a file system and then upload the items into
SharePoint.
■ (ET1485122) The application, SPSRecoveryAsst.exe, gives an application
error when you try to restore an invalid object that you select from the
Backup, Archive, and Restore user interface. The workaround for this issue
is to select the correct item to restore.
■ (ET1589445) Using AllWebs to perform a granular backup of secure and
non-secure web applications results in a status 1 error. The secure sites
can be backed up individually or together successfully
■ (ET1540667) After restoring a subsite the link is not restored in both quick
launch and top link bar. You can use an option to add a link so you can
restore a subsite.
■ (ET1539923) Special characters in item names are excluded when displayed
in the Backup, Archive, and Restore user interface. When the items are
restored, the special characters do appear in the restored item.
■ (ET1639566) Restoring a document from a NetBackup 6.5.3 image of a
SharePoint 2003 portal may be reported as successful, however the
document is not restored. To avoid this issue, restore the database or
perform a redirected database restore and access the desired document.
■ (ET1637318) Restoring a Web Application that contains web parts from a
granular image results in missing web parts. Once the restore has been
completed, you must reapply the web parts.
■ (ET1633472) Unable to browse sites after multiple db restore. The IIS

settings are not preserved when you run this restore. To resolve this issue,
restore the SharePoint Web Application from a FULL and DIFF(s) images
in one job.
■ (ET1630657) A redirected restore of granular content to the file system
(using an UNC path) from multiple content databases the restore fails and
informs the user that the restore failed to recover the requested files. The
workaround is to restore content from one db at a time.
■ (ET1653526) The SharePoint Shared Services database does not get restored.
The SharePoint farm can be recovered from backup without this database,
All the web applications can be restored successfully along with their
content. A new SSP service is created as part of the recovery.
■ (ET1640309) A redirected restore of a SharePoint Web Application using
FULL and DIFF images in separate jobs fail. The workaround is to perform
the redirected restore of a SharePoint Web Application using FULL and
DIFF images in a single job.
■ About restores of SharePoint Server and Windows SharePoint Services
When you perform restores, you should administer restore jobs from the
NetBackup master server or the SharePoint front-end server. When you
run a restore job from the master server, the jobs run but no progress log
appears. You must monitor the job status from the job details on the master
server. Symantec recommends that you run the restore jobs from the
SharePoint front-end server.
■ You can redirect SharePoint sites, documents, lists or items to a path, a
workspace, or a document library, as follows:
- Redirect to path. In the Restore to drive or UNC path box, enter the drive
letter or UNC Path. Use the following format for a UNC path:
\\servername\share. In the Restore to path box, enter the path to which
you want to direct the restore.
- Redirect to the workspace or the document library
(WebStorageSystem-based only). This option only applies to SharePoint
2001 restores.
NOTE: When you direct items to a file system, any list items you selected
are not restored and appear as 0-KB files . If you redirect list items to a file
system, the item itself is a 0-KB file but if the list item has any attachments
they get restored.
- Redirect to the Windows file system. When you use a drive letter it must
be entered C:\ (or whatever drive letter the users chooses) and the "Restore
to Path" must be entered as "restored data". The granular restore run on
the backend server.
Storage-related issues
If you do not follow this process then the granular restore fails with a status
5 and the following appears in the log:
17:14:37 (2180.001) TAR - Unable to restore. Skipping file:
SharePoint - 38951\Content-DB 1
NetBackup for SQLserver agent issues

If you perform a backup using multiple streams (stripes) and multiplexing, you
cannot restore this backup image using more than one stripe.
Other database agent issues

Granular backup:
■ Windows 2008 is also supported for Exchange 2007 granular backups:
■ The installation of the client for NFS is different than what is listed in the
NetBackup 6.5.3 documentation update. To enable Service for NFS on
Windows 2008, add the "Services for Network File System" role under File
Services within the Windows Server Manager. Confirm the "Client for NFS"
has started successfully.
■ The 8022.0 or higher version of the Microsoft Exchange Server MAPI
Client and Collaboration Data Object 1.2.1 is required on the Exchange
server for granular recoveries or mailbox level backups to function properly.
That can be downloaded from the following Web site .
http://www.microsoft.com/downloads/details.aspx?familyid=E17E7F31
-079A-43A9-BFF2- 0A110307611E&displaylang=en
■ (ET1702148) An enhancement has been made to the improve resource
allocation overhead for duplication jobs. A duplication job typically copies
multiple images. Within a duplication job, after each image is copied, the
resources to read the next image are reallocated. If read resources for each
image are re-allocated then an overhead problem can occur if you duplicate a
large number of very small images. When you duplicate small images, the
overhead to reallocate resources for each image is disproportionably large.
The overhead is large in comparison to the time it takes to copy each image.
The changes in this version of NetBackup significantly reduce the time it takes
to grant resources for read requests for each image.
■ (ET1976752)NetBackup 6.5 and later does not support SharedDisk storage as

a destination for hot catalog backups.
■ (ET1590866) When creating an offline, cold-catalog backup, do not include
the /usr/openv/db directory in the backup selection list. Upon recovery, that
causes the database files to be recovered twice.
■ (ET1829684) Any Active Directory backup is always a full backup, whether it
is a granular backup or not. That means that whenever Active Directory is in
a policy’s backup selection list, the AD portion is always backed up fully even
when the backup type is incremental, differential or cumulative. Any other
items in the Backup Selections list may use a differential backup or a
cumulative-incremental backup type as indicated. Even though a full backup
is forced for an Active Directory backup, normal incremental rules apply to
the non-AD items in the policy file list.
■ (ET1765334) When using OST or PureDisk Optimized Duplication between
two similar devices, the read side of the duplication job is not counted against
the I/O stream limit that is configured for volumes in a disk group.
If OST Optimized Duplication is used to copy an image between two similar
devices, the duplication job is not counted as an active I/O stream for the disk
volume from which the image is read. In other words, the I/O stream limit
setting does not limit the number of optimized duplication jobs that can read
images from OST/PureDisk disk volumes and cannot be used as a mechanism
to prevent these disk volumes from becoming overloaded. That can cause slow
performance for backup and duplication jobs if too many jobs are running at
one time on the same disk volume.
■ (ET1737495) When a policy writes multiple copies to disk storage units and
tape storage units, and if multiplexing is configured, the result is the lowest
multiplexed value. For a policy to create multiple copies that are multiplexed,
the storage units that the policy writes to must be all tape storage units. If the
types are mixed, multiplexing does not occur.
■ (ET1502680) When creating Active Directory objects, it is advisable to take
advantage of the schema that Microsoft provides. To place things outside of
the schema means that though it may be possible to successfully perform a
Granular backup, it is not possible to browse those Active Directory objects
that have been oddly placed. An object that cannot be browsed also cannot be
restored.
For example, the situation in which one creates a user or computer in the
Domain Controllers container. The object is included in a successful granular
backup, but is not displayed in a browse. Since it is not displayed in a browse,
it cannot be restored.
■ (ET1538745) Destinations within a storage lifecycle policy may be backup

destinations or duplication destinations.
Duplication destinations can be configured to indicate an alternate read server.
The alternate read server can read a backup image that a different media server
originally wrote.
Each destination belongs to a particular disk pool. The alternate read server
that is indicated as a duplication destination in the same storage lifecycle
policy must be a server for the disk pool of the source backup destination. Disk
pools are listed under Media and Device Management > Devices > Disk Pools.
■ (ET1543025) Both types of backup staging methods make use of capacity
management on disk storage units. That means that NetBackup automatically
removes expired images from the storage unit to create space for new images.
In either situation, NetBackup cannot manage the capacity of a storage unit
that is NFS-mounted:
■ For basic disk staging:
The disk staging storage unit is capacity-managed by default. Do not make
a DSSU out of a storage unit that is NFS-mounted. (That is, do not select
the Enable Temporary Staging Area option for that storage unit.)
■ For storage lifecycle policies:
A destination can be configured to be capacity-managed. Do not enable the
Staged Capacity Managed option for any destination that is NFS-mounted.
■ (ET1485775) OpenStorage direct-to-tape enables you to copy NetBackup backup

images from a disk appliance to NDMP hosted tape drives.
For more information, see the 6.5.4 version of the NetBackup Shared Storage
Guide contained in the following Technote on the Symantec Support Web site.
Note: The license key that activates OpenStorage must be installed on each
NetBackup media server that you use for direct to tape.
■ (ET1543384) Backups to disk may fail with status code 800
During heavy NetBackup media server activity, backups to disk may fail with
a NetBackup status code of 800. The code appears in the Administration Console
Activity Monitor Job Details display.
See the NetBackup Troubleshooting Guide description of NetBackup status
code 800 for remedial action.
Jobs may fail because the heavy load causes processes to wait longer than the
default timeout period (60 seconds). You can try to increase the timeout by
creating the following file on the media server:
UNIX: /usr/openv/netbackup/db/config/DPS_PROXYDEFAULTRECVTMO
Windows: C:\Program
Files\VERITAS\NetBackup\db\config\DPS_PROXYDEFAULTRECVTMO
If the config directory does not exist, create it.
The file should contain the new timeout value, greater than, or equal to 10 or
less than or equal to 3600 seconds.
■ The SAN Client does not support inline tape copy over Fibre Transport. Inline
tape copy jobs occur over the LAN. The SAN Client is designed for very high
speed backups and restores. Therefore, SAN Client excludes backup options
(such as inline tape copy) that require more resources to process and manage.
■ A new option that is labeled New has been added to the Add Disk Array Host
dialog box. In addition, a new dialog box titled, New Array Type has been
added. When you click the New option the New Array Type dialog box appears.
Included on this dialog box is a Help option. The online Help for this dialog
and option will be available at the next major release.
■ The NetBackup Shared Disk option does not support Windows 2008 for media
servers.
■ The following list of issues applies to AdvancedDisk .
■ Windows Common Internet File System (CIFS) is not supported.
■ For NFS, you must use manual mount points.
■ Symantec recommends that you do not span backup images across volumes
in an AdvancedDisk disk pool. File system full conditions cannot be detected
adequately. Therefore, each disk pool should be comprised of only one
volume.
■ (ET1128929) Potential free space is the amount of space on a disk staging

storage unit (DSSU) or on a lifecycle policy destination that NetBackup can
free if extra space on the volume is needed. (Use the nbdevquery command to
display the potential_free_space and the free_space value.) The potential free
space value represents the total size of the image copies that are eligible for
expiration.
To create free space, an administrator can run the bpexpdate command to
manually expire eligible image copies on the volume. That changes the potential
free space into available free space.
If nbdevquery is run after bpexpdate is used, the potential free space value
should be reduced, and the free space value should be increased. However,
that is not the case. The nbdevquery command does not display the correct
value of potential free space until one of the following update events occurs:
■ In the case of DSSUs: When the high water mark or a disk-full condition
is reached on the storage unit. The automatic expiration of eligible copies
of staged images occurs and then the potential_free_space value for that
disk is recalculated.
■ For disk destinations within lifecycle policies: When a duplication job that
writes to the disk completes, the potential_free_space value for that disk
is recalculated.
Suppose a copy of an image is beyond its try-to-keep date, and is a candidate
for removal from disk. For instance, this copy of the image is counted as a part
of the potential-free-space value. If a user uses the bpexpdate command to
manually expire this copy of the image from disk, the potential-free-space
value is not decremented to reflect the action that was taken until the whole
potential-free-space value is recalculated. Until the value is recalculated, the
user and NetBackup think that there is more available space on the disk than
there is.
The potential-free-space value is recalculated:
■ When the High Water Mark (HWM) condition forces a draining of the disk
down to Low Water Mark (LWM).
■ When an image is fully duplicated, thus being "Lifecycle complete".
The "Available space" is free space plus potential free space . The file system
increments the free space , but NetBackup does not decrement the potential
free space . Thus, the size of the image that was expired is counted twice as
both free space and potential free space . That is the reason why it looks to the
user and NetBackup like the disk has more space than there is. In addition,
that may cause NetBackup to assign jobs to the disk that have a larger,
total-estimated size than is available.
■ Dissimilar Disk Restore of a Solaris client fails if the client uses SVM
metadevices (volumes) that are created when it uses slice 2 of the Solaris Disks.
For more information on this issue, refer to the following Technote on the
Symantec Support Web site.
■ (ET1317594) To add clarity, the Load balance label in the Storage Unit Group
dialog, has been changed to read, Media server load balancing.
■ (ET1267896) When performing backups using the new Pure Deduplication
Option (PDDO) feature, Symantec suggests that users monitor their shared
memory usage as the number of jobs increases. The job-size throttling has
been turned off in NetBackup 6.5.2 to allow more PDDO backups to run
concurrently. Please consult your NetBackup Performance Tuning Guide for
additional information on NetBackup tuning parameters affecting shared
memory usage.
■ (ET1597920) Disaster recovery email and AdvancedDisk storage units
NetBackup user interface issues
If an online, hot catalog backup is directed to an AdvancedDisk storage unit

and a catalog backup policy identifies a critical policy that has a backup image
that is located on the same AdvancedDisk storage unit, the disaster recovery
email does not list that critical policy.
However, the policy is listed in the disaster recovery file. You can open the DR
file with a text editor to obtain that critical policy information (the media
server and the media ID on which the policy's backup image resides).
NetBackup user interface issues

■ The NetBackup-Java administration console on Windows (WDC) cannot connect
to a UNIX master sever with a Japanese package. When you attempt to log on
to the master server, the NetBackup-Java administration console hangs at a
point when the following status statement appears.
Checking if NBAC is configured.
For more information about this issue and a workaround solution, refer to the
■ (ET1980306) You are not able to search for backup images under the Catalog
node (Action > Verify) of the NetBackup Administration Console.
If you encounter this issue, start the user interface from the Recent Programs
list.
■ You browse for granular backups differently on the MFC user interface than
you do when you use the NetBackup-Java Administration Console. That happens
with granular backups from Microsoft Exchange, Microsoft SharePoint, or
Microsoft Active Directory. The difference occurs when you click on a granular
node to expand the node and view its contents. A noticeable delay and
unnecessary overhead can occur when you expand a granular node on the MFC
user interface. The MFC user interface may expand more than was requested
in an attempt to minimize this delay. The NetBackup-Java Administration
Console does not do that. The NetBackup-Java Console requires the user to
make additional node expansion clicks and causes an additional delay.
■ (ET1517333) To back up all local drives, Symantec recommends that you use
a scheduled backup from the master server. This method is much faster than
performing a user-directed backup of all local drives from the client in Backup,
Archive, and Restore.
■ (ET1224679) If two instances of the NetBackup Administration Console are
running on two separate remote desktop sessions on the same server, the
console may crash. This issue does not occur very often. The issue is not a
regression and is outside of the normal scope of operations.
General NetBackup issues
■ (ET1395328) When using the bp or the bpadm interface on HP-UX 11.23 or

11.31 systems on Integrity (IA-64) architecture, a DATE ERROR is returned
during attempts to change dates. For more information about this issue, refer
to the following Technote on the Symantec Support Web site.
■ (ET1231347) As a result of a security fix to handle characters like "<", ">", and
";", a user could issue UNIX commands without being a root user. Because the
NetBackup-Java Administration Console uses the command line interface (CLI)
to create policies, these characters cannot be allowed as text entries in policies.
The security fix cannot be removed. Therefore, to work around this issue, the
user should use a Java Administration Console that is running on a Windows
workstation to create policies for MSEO.

■ On a media server (stand-alone or clustered), if the media server system is
shut down or a failover occurs while the media server is involved in a restore
operation, further restore operations involving this media server do not
function. For more information about this issue, refer to the following Technote
on the Symantec Support Web site.
■ (ET1750852) The NetBackup VxFI provider does not work with IBM DS 8300
arrays. For more information, refer to the following Technote on the Symantec
Support Web site.
■ (ET1116304) To view the log messages that PBX exchange generates, use the
utility, vxlogview, that the VRTSicsco package installs. Typically, the
VRTSicsco package is installed at /opt/VRTSicsco on UNIX systems and
CommonProgramFiles\VERITAS\VRTSicsco on Windows systems. You should
not use vxlogview that another package installs. Installing the utility from
another package may cause errors because of a version and an architecture
mismatch.
■ (ET 1993115) NetBackup 6.5.6 Snapshot Client supports no more than 40 rows
of “Snapshot Resources” entries per policy for certain disk arrays
For the following disk array snapshot methods, NetBackup can support up to
40 rows of entries in the Snapshot Resources pane of the policy’s Snapshot
Options dialog. Each row consists of an array serial number, an ID for the
source device, and IDs for one or more snapshot devices.
If you specify more than 40 rows for any of the following methods, the backup
of the array may not succeed:
■ Hitachi_ShadowImage
■ Hitachi_CopyOnWrite
■ EMC_TimeFinder_Clone
■ EMC_TimeFinder_Mirror
■ EMC_TimeFinder_Snap
■ EMC_CLARiiON_Snapview_Clone
■ IBM_DiskStorage_FlashCopy
For policy configuration assistance for these array snapshot methods, refer
to the NetBackup Snapshot Client Administrator's Guide.
■ About VSS and hot to manage snapshot volume size
In the NetBackup 7.0GA, 6.5.4 and 6.5.5 releases, NetBackup attempted to
manage the size of the VSS snapshot volume. To do that, NetBackup changed
any unbounded VSS associations to a fixed size. That size was based on the
size of the disk drive. The objective was to prevent the unbounded VSS
associations that can fill a hard drive and affect the system operation. In
releases after 7.0GA and 6.5.5 that is no longer be done and that system
management setting is beyond the scope of NetBackup to alter.
A customer who has upgraded from one of these levels might have failed
backups because NetBackup has changed this setting. For that to occur all of
the following must be true:
■ Customer has upgraded from 6.5.4, 6.5.5 or 7.0GA.
■ An unlimited VSS association on a client
■ NetBackup backed up that client (and therefore modified the setting)
■ The client OS is Windows 2008 or 2008 R2 Server
■ The backups are either multistreamed, or the backups create the VSS
snapshots that overlap in time.
In this case the association is set too small and future snapshots might be
deleted before they are backed up. To correct this issue, set the association to
a larger, more appropriate value. Refer to Microsoft documentation for details
on how to set this system management setting.
■ (ET2020528) To configure array access for NetBackup hosts not named in a
policy
In the following cases, you must explicitly enable NetBackup to access disk
array credentials:
■ Certain NetBackup hosts that are not named as clients in a policy must be
explicitly enabled to access array credentials. An example is an alternate
client that is used for off-host backup processing but is not included in the
policy’s Clients list.
■ Microsoft Exchange is installed on a hardware disk array such that Windows
VSS uses the hardware snapshot provider. If you define an MS-Exchange
policy with Snapshot Client and Instant Recovery, but you accept the
defaults for Snapshot Client Options, NetBackup must be explicitly enabled
to access the array credentials. (Note: This requirement does not apply if
you set the VSS Provider Type to 3-hardware.)
To enable NetBackup to access the array credentials:
■ In the NetBackup Administration Console, click Host Properties > Master
servers > double-click name of master server > Properties > Credential
Access.
■ Click Add to enter the name of the client. Then click OK.
You can use the following as an alternative procedure:
■ UNIX:
On the NetBackup master server, add the following line to the
/usr/openv/netbackup/bp.conf file, one line for each NetBackup host:
DISK_CLIENT = host_name
Until the DISK_CLIENT entry is made to the bp.conf file, a point-in-time
rollback fails with NetBackup status 5.
■ Windows:
1 On the NetBackup master server, click Start > Run and enter regedit.
2 To be on the safe side, make a backup of the current registry (File > Export).
3 Go to
HKEY_LOCAL_MACHINE\SOFTWARE\VERITAS\NetBackup\CurrrentVersion\Config.
4 Right-click in the right pane and select New > String Value. Enter the
following: DISK_CLIENT
5 Right-click on the new DISK_CLIENT name and select Modify.
6 For the Value data field, enter the host names of the clients that are not
named in any policy. To specify multiple host names, separate the names
with a space.
7 Click OK. Until this entry is made in the Windows registry, a point-in-time
rollback fails with NetBackup status 5.
■ (ET1953216) Snapshot-only restores fail with a private provider error on a

rollback attempt.
The failure occurs because NetBackup was unable to retrieve the required disk
array credentials from the master server. The DISK_CLIENT=;client credential
should be to the NetBackup registry of the master server, so the rollback can
succeed.)
You should configure the array access for NetBackup hosts that are not named
in the policy. You must explicitly enable certain NetBackup hosts that are not
named as clients in a policy to access array credentials. An example is a media
server that is used for off-host backup processing but is not included in any
policy’s Clients list.
To allow the host to access credentials, do the following:
■ In the NetBackup Administration Console, click Host Properties > Master
servers, then double-click name of master server and choose, Properties
> Credential Access.
■ Click Add, to enter the name of the client.
■ Click OK.
■ Configuring permissions for log files

NetBackup uses the /usr/openv/netbackup/logs directory tree to record
troubleshooting information and to obtain progress and communication
updates to users and other NetBackup applications. Restrictive permissions
on these directories can not only disable the collection of troubleshooting data,
but also prevent the application itself from functioning correctly.
Back up and restore operations fail when permissions are too restrictive.
Symantec recommends that you make all of the usr/openv/netbackup/logs
directories and subdirectories readable and writeable by all users (777
permissions). However, security requirements may prohibit global read-write
access. If so, you can restrict permissions of specific directories to a single
group or user if the following is true: All backup and restore operations that
are related to that directory are initiated by the processes that run as members
of that group or as that user.
Check that the /usr/openv/netbackup/logs/user_ops directory tree has 777
permissions. The items in this directory need to be accessible for the
applications to operate correctly.
If you restrict permissions on the other directories that are located in
/usr/openv/netbackup/logs, backup and restore operations are not affected.
However, troubleshooting efforts may be hindered when processes do not have
the appropriate permissions to update the debug logs therein.
■ (ET1136915) NetBackup recognizes wildcard character usage in some areas,
such as in backup selection lists and exclude file lists. You can use curly
brackets or braces around multiple wildcard file name patterns, as described

in the Administrator's Guide.
However, since curly bracket characters are valid characters for Windows file
names, they cannot be used to indicate wildcard usage for Windows platforms.
Also, backslashes cannot be used as escape characters for curly bracket
characters.
■ (ET1720780) VMware VCB FlashBackup restores to an alternate client fail with
a status 5 error.
For more information and a work-around solution to this issue, see the
■ (ET1940490) VMware Mapped Full VM backups do not support mapping of

IDE disks.
Mapped VM backups fail if the VM contains IDE disk(s).
■ (ET1636600) Backup problem with MS-Windows-NT policy type and VMware
ESX version 3.0 and 3.0.1
Symantec identified a problem when backing up a NetBackup client that is
installed in a Windows operating system on certain versions of VMware ESX
servers. If you select the MS-Windows-NT policy type, and the ESX server is
at version 3.0 or 3.0.1, the backup job hangs.
This problem is apparently due to an issue in ESX server versions 3.0 or 3.0.1,
not in NetBackup.
Potential workarounds are the following:
■ Update your ESX server to 3.0.2 or later.
■ Or, configure a VMware backup proxy server and use NetBackup for VMware
to perform the backup. For assistance with NetBackup for VMware, see the
"NetBackup for VMware Administrator's Guide."
■ (ET1593098) An error message is issued when an attempt to validate VMware

credentials occurs.
NetBackup 6.5.4 added the ability to verify that the VMware credentials that
you entered in the NetBackup policy are valid for the VMware server. The
NetBackup Add virtual machine server dialog now contains a "Validate
Credentials" checkbox.
Note: If your VMware proxy server is running a version of NetBackup that is

earlier than 6.5.4, the credentials cannot be validated. That causes an error
message to appear. You must verify that the credentials you entered are correct
for the VMware server. If the credentials are correct, you can ignore the error
message.
■ If a virtual machine backup uses VCB and the policy is configured with the
Mapped full VM backup option, the backup fails if the virtual machine contains
an IDE disk.
To use the Mapped full VM backup option with VCB, you must reconfigure
the virtual machine so that it does not contain IDE disks.
For descriptions of other backup options, see the "Configuration parameters
for VMware" section of the NetBackup for VMware Administrator's Guide, for
NetBackup 7.0.
■ NetBackup now supports EMC Solutions Enabler 7.0 with the following
snapshot methods for EMC disk arrays:EMC_TimeFinder_Clone,
EMC_TimeFinder_Mirror, EMC_TimeFinder_Snap.
■ (ET1556112) As part of the catalog policy configuration, the administrator

indicates a path to the directory where the disaster recovery information is
saved. This path is indicated on the Disaster Recovery tab.
The path for the disaster recovery information cannot be to a directory that
is on the same partition as /usr/openv/netbackup. If the path for the disaster
recovery information is to a location on the same partition as
/usr/openv/netbackup, NetBackup displays a status 20 error message. The
message states that the disk path is invalid. The administrator needs to change
the path on the Disaster Recovery tab to a directory on a different partition.
■ In rare situations the first backup attempt after NetBackup is installed may
fail. That can happen if the backup is granular and if Microsoft Volume Shadow
Copy Services (VSS) is used. In addition, after this one failure all subsequent
backups succeed.
■ (ET1535587) The media server that was used for catalog backups must be at
the same level as the master server. That is true for hot or cold catalog backups.
■ (ET1504682) The bpbackup command is used to perform user backups from
clients and manual backups from master servers. In addition to listing
individual files or directories, bpbackup can also use directives to indicate the
files to be backed up. For example: bpbackup /Shadow Copy Components/
bpbackup /System State/.
Clients can enter the directive in the list file by using the following option:
bpbackup -f listfile.
■ (ET1536915) Do not save logs to a remote file system such as NFS or CIFS.
Logs that are stored remotely and then grow large can cause critical
performance issues.
■ (ET1539585) In this release, an administrator can resume a suspended job
until the retention period of the job is met. The retention period begins when
the job is suspended. If the administrator resumes the job after the retention
period passes, the job fails because the image has expired. The job is then
moved to the DONE state.
Note: The Clean-up host property, "Move backup job from incomplete state to
done state," does not apply to suspended jobs. Jobs are suspended manually
and must be resumed manually.
■ (ET1512562) Individual restore of mails from BE images is not supported in

NetBackup 6.5.x as mentioned in the NetBackup online Help.
■ (ET1260712) NetBackup considers the failure history of a policy when it
determines whether or not to run a scheduled backup job. The timeframe for
NetBackup to examine one of the configured settings occurs when you use the
Schedule Backup Attempts setting in the Global Attributes host properties.
This property determines the following characteristics for each policy:
■ How many preceding hours NetBackup examines before it determines
whether to allow another backup attempt (retry). By default, NetBackup
examines the past 12 hours.
■ How many times a backup can be retried within that timeframe. By default,
NetBackup allows two attempts. Attempts include the scheduled backups
that start automatically or the scheduled backups that a user initiates.
In NetBackup 6.0 and later, all backup attempts apply toward this configurable
limit, regardless of the type of backup or the schedule. In releases before 6.0,
NetBackup allowed each schedule to meet the Schedule Backup Attempts
property limit. In some cases that resulted in more backup attempts than
expected based on the property setting.
Consider the following 6.5 example scenario using the default setting: two
tries every 12 hours:
■ Policy_A runs at 6:00 P.M.; Schedule_1 fails.
■ Policy_A is user-initiated at 8:00 P.M.; Schedule_2 fails.
■ At 11:00 P.M., NetBackup looks at the previous 12 hours. It sees one attempt
at 6:00 P.M. and one attempt at 8:00 P.M. The Schedule backup attempts
setting of two has been met so NetBackup does not try again.
■ At 6:30 A.M. the next morning, NetBackup looks at the previous 12 hours.
It sees only one attempt at 8:00 P.M. The Schedule backup attempts setting
of two has not been met so NetBackup tries again. If a schedule window is
not open at this time, NetBackup waits until a window is open.
■ (ET1260712) For master servers at NetBackup version 6.5 or later, the

ALLOW_MULTIPLE_RETENTIONS_PER_MEDIA setting in the bp.conf file has
no effect. To allow mixed retention levels on media, use the nbemmcmd command
to update the nbemm database and change the
ALLOW_MULTIPLE_RETENTIONS_PER_MEDIA setting. The default
configuration does not allow multiple versions (a setting of 0 or no).
To allow multiple retention levels, use nbemmcmd -changesetting to change
the ALLOW_MULTIPLE_RETENTIONS_PER_MEDIA setting to 1 or yes.
■ (ET1364268) In 6.5.2 NetBackup introduced the ability to allow, restrict, or
prohibit reverse host name lookup for master servers, media servers, and
clients.
Administrators can configure this using several methods:
■ By changing the Network Settings host properties in the Administration
Console.
■ By editing the bp.conf file (UNIX) or the Windows Registry.
■ New in 6.5.4: By using the bpclntcmd command on UNIX or Windows
systems.
Using the bpclntcmd command:
To display the current configuration setting, enter the command: bpclntcmd
-reverse_name_lookup
To change the entry, log on to the system as root or Administrator. Enter one
of the following commands:
■ To allow reverse host name lookup (default), enter:
bpclntcmd -reverse_name_lookup allowed
This setting indicates that the host requires reverse host name lookup to
work to determine that the connection comes from a recognizable server.
■ To restrict reverse host name lookup, enter:
bpclntcmd -reverse_name_lookup restricted
This setting indicates that the NetBackup host first attempts to perform
reverse host name lookup. If the NetBackup host successfully resolves the
IP address of the connecting server to a host name (reverse lookup is
successful), it compares the host name to the list of known server host
names.
If the resolution of the IP address to a host name fails (reverse lookup fails),
based on the Restricted setting, the host converts the host names of the
known server list to IP addresses (using a forward lookup). The host
compares the IP address of the connecting server to the list of known server
IP addresses.
If the comparison fails, the host rejects the connection from server and the
connection fails.
■ To prohibit reverse host name lookup, enter:

bpclntcmd -reverse_name_lookup prohibited
This setting indicates that the NetBackup host does not try reverse host
name lookup at all. The host resolves the host names of the known server
list to IP addresses using forward lookups. The NetBackup host then
compares the IP address of the connecting server to the list of known server
IP addresses.
If the comparison fails, the NetBackup host rejects the connection from
the server and the connection fails.
■ (ET1436810) Calendar incremental backups may not run on the same day as
a calendar full backup as been scheduled.
■ (ET1199036 and ET1181074) Users may get a core dump of dbeng9 after a Full
Catalog Backup recovery. That is not a Symantec NetBackup issue. This core
dump can be deleted and ignored. Testing showed that the catalog recovery
completed successfully and that bprecover handled the core dump issue
appropriately.
■ (ET1268670) In NetBackup 6.5.2, a user cannot change the NDMP hosts in
Device Configuration Wizard on the NetBackup-Java Administration console.
You can use one of the following two workarounds to accomplish this task:
■ Using the user interface:
1. Expand Credential within the left pane of the NetBackup-Java
Administration console.
2. Select NDMP Hosts.
3. Select the NDMP host to change.
4. Right-click the NDMP host and select Change from the drop-down menu.
The Change NDMP host window appears.
■ Using the command line:
1. Run /usr/openv/volmgr/bin tpconfig -update -default_user_id
user ID.
■ (ET1281808) Point-in-Time (PIT) is not supported in NetBackup 6.5.2 for

IBM_DiskStorage_FlashCopy snapshot method.
A point-in-time rollback restore from an IBM_DiskStorage_FlashCopy snapshot
backup fails on AIX platforms for the backup resources that are built on AIX
native stacks, such as JFS2 file systems on AIX LVM volumes. The
IBM_DiskStorage_FlashCopy snapshot method is supported on the IBM DS
6000 series of storage arrays .
■ (ET1250126) To perform a point-in-time rollback restore for an IBM DS6000
system, you must modify a VxFI configuration file for the Windows x64
platform. Perform the following steps to set up and change the configuration
file:
■ Install IBM VSS 3.x.
■ Install DSCLI 5.2.2.224 at a minimum.
■ Add the following lines to the end of
%commonprogramfiles%\SymantecShared
\VxFI\4\ConfigFiles\ibmtsfi.conf.
[CLI_TOOL_INFO]
"FILEPATH"="C:\Program Files (x86)\IBM\DSCLI\"
(If DSCLI is installed to a different location, use that path in place of
C:\Program Files (x86)\IBM\DSCLI).
You can find the following Technote on this issue on the Symantec Support
Web site.
■ (ET1274002) The recovery of a catalog image that was taken in NetBackup

6.5.2 is NOT supported in an earlier version of NetBackup or vice versa.
■ (ET1137932) To do NetBackup restores as a non-administrative user under
NBAC using the Windows Backup, Archive, and Restore client console or the
Windows Administration Console, the permissions on the following directories
need to be set to "Full Control" for each user of the user interfaces.
C:\ProgramFiles\Veritas\NetBackup\logs\nbwin
C:\ProgramFiles\Veritas\NetBackup\logs\nbconsole
■ (ET1174736) This release contains a 32-bit Windows memory management

limitation. Windows can only address 4GB of memory. If an attempt is made
to perform a FlashBackup of volumes that are larger than 10TB, that it requires
more than 4GB of memory to store the bitmap that needs to be created for the
restore of single files. To work around this issue, Symantec recommends that
you make smaller volumes or use a UNIX master server.
■ (ET1412544) The Windows NTFS file system supports the new junction points
feature. A junction point can be set up to provide access to files in a local
directory (similar in function to a symbolic link). For backups of a VMware
virtual machine, NetBackup for VMware does not currently support a junction
point as the snapshot mount point on the VMware backup proxy server. The
snapshot mount point must be a local directory on the proxy server, not a
junction point that refers to a local directory. Support for junction points as
the snapshot mount point on the proxy server will be added in a future release.
NetBackup Hyper-V issues
Warning: If a junction point is used as the snapshot mount point, the backup
appears to succeed, but the actual files that were backed up may be the wrong
files.
■ VMware NetBackup Integration Module (VNIM) not required.

The VMware NetBackup Integration Module (VNIM) is not required for
NetBackup for VMware. In fact, NetBackup for VMware cannot function if
VNIM is installed.
Note: NOTE: If VNIM is installed, you must uninstall it before running any
backups.
■ The following list of issues applies to AdvancedDisk .

■ Windows Common Internet File System (CIFS) is not supported.
■ For NFS, you must use manual mount points.
■ Symantec recommends that you do not span backup images across volumes
in an AdvancedDisk disk pool. File system full conditions cannot be detected
adequately. Therefore, each disk pool should be comprised of only one
volume.

■ NetBackup for Hyper-V 6.5.x does not support the use of a single policy to
protect all virtual machines that reside on all nodes of the cluster. You must
create an individual policy for each cluster node (Hyper-V host). Because virtual
machines can migrate from one node to another, you may have to update an
existing policy to ensure that virtual machines are backed up.
Please note the following:
■ For a cluster with two nodes, node A (active) and node B (passive), all the
virtual machines are on the active node A. Therefore, the Clients list of the
NetBackup policy for node A must include all the virtual machines. If node
A fails over to node B, node B becomes active and all the virtual machines
migrate to node B. In that case, you must have a policy for node B that lists
all the virtual machines, and the old policy for node A can be deactivated.
In other words, two policies are required (one for each node), but only one
policy needs to be active at any given time. Each policy's Clients list must
contain all the virtual machines in the cluster that need to be protected.
■ For a cluster with two active nodes A and B, you must have two policies
activated at the same time, one for each node. All virtual machines in the
cluster must be named in the Clients list of each policy. Since a virtual
machine could be running on either active node, a backup started for one
node (where the virtual machine happens to exist) succeeds. A backup
started for the other node (where the virtual machine does not exist) fails.
A number of backups jobs will fail, but this configuration ensures that
virtual machines are backed up as part of at least one policy.
■ For a virtual machine that is configured on a Windows volume GUID: If
cluster nodes A and B each refer to the volume GUID on a shared storage
device that is formatted with the MBR format, the volume GUID used by
node A for the virtual machine is not the same as the GUID used by node
B for the same virtual machine. In other words, the virtual machine's volume
GUID is different on different nodes. As a result, if the virtual machine is
active on the node where it was created (node A), a backup of the virtual
machine using the policy for node A succeeds. If the same virtual machine
is active on a different node (node B instead of A), a backup of the virtual
machine using the policy for node B fails. Only the policy that was created
for node A can successfully back up the virtual machine.
■ (ET1790770) Hyper-V snapshots (.avhd files) and status code 1

If a snapshot of the virtual machine (.avhd file) occurs during a NetBackup
backup of the virtual machine, the backup may be partially successful. A
message similar to the following appears in the bpbkar log:
5:02:54Hyper-V snapshot.570 PM: [10948.8980] <2>
tar_base::V_vTarMsgW: INF - VxMS Error message 1 =
translate_to_virtual_extent: ERROR Unable to locate MAP file =
\\?\GLOBALROOT\Device
\HarddiskVolumeShadowCopy89\VM1\testvm2.veritas.com\
TestVM1_diffVM1k_8275A265-BD90-4E65-94C8-C347B7228E95.avhd
Retry the backup.
Note: NetBackup does not create Hyper-V .avhd files. NetBackup creates its
own snapshots when it backs up virtual machines.
■ (ET1762911) Redirected Restore from R1 to R2 Hyper-V server fails The

following three items are associated to this same issue:
■ After a redirected-full, virtual machine restore on a Windows Server 2008
SP2 system, that virtual machine enters a saved (unexpected) state and
fails to start.
You must manually delete the spurious saved state after the restore and
then start the virtual machine . This issue can occur when the Virtual
Machine is backed up in an online state and the expected state after the
restore is OFF. However, because of the Hyper-V behavior on these this
type of platform, the virtual machine goes into a spurious SAVED state.
During the restore, Hyper-V-VMMS logs the event ID 12340. The following
is a sample event log message:
'Saved State' cannot read key
'/configuration/_ba8735ef-e3a9-4f1b-
badd-dbf3a5909915_/VideoMonitor/State' from the repository.
Error: '%%2147778581'(7864368). (Virtual machine ID
0AD8DFCC-BDC0-4218- B6DF-7A3BA0A735B)
To delete the spurious SAVED state, perform the following:
1. Open the Hyper-V server manager.
2. Right click on the restored virtual machine and then click Delete Saved
State.
■ Full virtual machine restore fails with error 5.

VM Restore Job fails with an error 5, however, the virtual machine is still
registered in the Hyper-V server. (Hyper-V-VMMS logs the following warnings
in the events log.) The Hyper-V writer encountered a Network configuration
error and that caused the failure. After the virtual machine is restored it can
be started after you reconfigure the network adapter configuration in VM
settings.
Event ID 10127, sample event log message is:
Unable to repair the network configuration for virtual machine
"Virtual Machine Display Name'. The virtual machine may not have
the same network connectivity as it did when the backup was taken.
Inspect the network settings and modify them as necessary. (Virtual
machine ID 0AD8DFCC-BDC0-4218-B6DF-7A3BA0A735BF)
Event ID 10104, sample event log message is:
One or more errors occurred while restoring the virtual machine
from backup. The virtual machine might not have registered or it
might not start. (Virtual machine ID
"0AD8DFCC-BDC0-4218-B6DF-7A3BA0A735BF ")
■ The virtual machine fails to start after a full virtual machine restore because
the virtual machine that was backed up on a Windows 2008 server was restored
on a Windows Server 2008 R2 server.
If a virtual machine was configured on a Hyper-V Server 2008 V1 when the
virtual machine was backed up a failure could occur. The failure occurs if at
the time of the backup the virtual machine was not in the Off state, the restored
virtual machine fails to start if it is restored to a Hyper-V Server 2008 R2. A

Hyper-V message states:
An error occurred while attempting to start the selected virtual
machine(s). <virtual machine name> could not initialize. Saved
state file version is incompatible.
In this case, you must delete the saved state file after the restore and then
start the virtual machine. In the Hyper-V Manager interface, right click on the
restored virtual machine and select Delete Saved State.
■ (ET1656180) NetBackup for Hyper-V has a virtual machine restore option
called "Overwrite virtual machine." This option removes a virtual machine on
the destination server before the same virtual machine is restored from its
backup. If the Overwrite virtual machine option is not selected and a virtual
machine with the same GUID exists on the destination server, the restore fails.
The failure is a NetBackup status code 5 and the failure is a normal (expected)
result.
However, if you restore a virtual machine without choosing the "Overwrite
virtual machine" option, and the virtual machine exists on the destination
Hyper-V server, the restore fails (as expected) but the existing virtual machine
is turned off.
■ (ET1663569) A minor problem occurs if you change an option in a
FlashBackup-Windows policy for Hyper-V, on the Snapshot Client Options
dialog. When you use the keyboard to enter a new configuration parameter
for an existing policy, the value is not retained when you save the policy.
■ When common (or parent) .vhd files and child .vhd files are restored to a drive
other than their original drive (such as to G:\ instead of to E:\), the
restored child .vhd files may not correctly point to the restored parent .vhd
file on the G:\ drive. As a result, the restored virtual machines that rely on
the common (parent) .vhd file are invalid. Make sure to restore the parent and
the child .vhd files to the same relative path names that they had before the
restore.
For example, assume the following:
■ The original parent was in E:\folder1\parent.vhd.
■ The original child was in E:\folder2\child.vhd.
■ The parent and the child .vhd files are restored to the G: drive.
The child .vhd file can correctly refer to the parent .vhd file on the G: drive,
if you restore the parent .vhd file to G:\restore_folder\folder1\parent.vhd
and the child to G:\restore_folder\folder2\child.vhd.
This issue may be fixed in a Windows 2008 Hyper-V update from Microsoft.
After it is fixed, you do not have to maintain the same relative paths in the
restore locations.
■ (ET1514145) If you restore the full virtual machine to a different location on
the original Hyper-V server or to a different Hyper-V server, the virtual
machine may fail to start. This failure may be due to a bug in the Microsoft
Hyper-V writer. The problem occurs when the virtual machine has two or more
levels of differencing disks. For example: A child.vhd file points to a parent.vhd
file, and that file points to a grandparent.vhd file.
After the restore, use the Hyper-V Manager to manually re-establish the
relationship between the different disks (such as child.vhd to parent.vhd to
grandparent.vhd).
A fix for this issue should be available in Windows 2008 SP2.
■ NetBackup for Hyper-V and Logical Disk Manager (LDM) If a virtual disk on a
Hyper-V virtual machine has been configured for LDM volumes, and the
NetBackup policy specifies the "2-Mapped FullVM" option, in certain cases a
backup of the virtual machine may not complete. The NetBackup job may issue
status 1, "the requested operation was partially successful." This error can
occur if the controller type of the .vhd disk was SCSI when the disk was initially
formatted, but the controller type was later changed to IDE (or vice versa).
In this case, the NetBackup progress log may contain the following message:
ERR - Unable to retrieve volumes from virtual machine, error = 1
You must restore the controller type of the .vhd disk to the controller type
originally assigned before the LDM volume was created. Then retry the backup.
■ (ET1418453) The following is a known issue for redirected restores of the
Hyper-V virtual machines that were backed up in the "Saved" or "Paused"
state.
If a Hyper-V virtual machine is in the "Saved" or "Paused" state when
NetBackup backs it up, the virtual machine is in the "Off" state after it is
restored to a different location. The current Microsoft Hyper-V writer causes
the change of state to Off.
If you restore the virtual machine to its original location on the Hyper-V server,
the state of that computer after the backup is correctly restored. If the virtual
machine was in the Saved or Paused state, it is set to Saved or Paused after
the restore.
■ (ET1847204) The following exclude list issues can occur when you restore
individual files from an instant recovery snapshot:
■ When you restore files from a snapshot that was made for an instant
recovery off-host alternate client backup: NetBackup consults the exclude
list on the alternate client even when it restores files to the primary client.
Bare Metal Restore (BMR) issues
If the exclude list on the alternate client is different from the exclude list
on the primary client, any of the files that are listed in the exclude list on
the alternate client are not restored to the primary client.
For example: If the alternate client's exclude list has the entry *.jpg, and
some .jpg files were included in the primary client backup, the .jpg files
can be selected for the restore but are not in fact restored. To restore the
files, you must change the exclude list on the alternate client.
■ When you restore files from a snapshot that was made for an instant
recovery backup (local or off-host alternate client): If the exclude list is
changed after the backup occurred, NetBackup honors the latest version
of the exclude list during the restore. Any files that are listed in the current
exclude list are not restored. Also, as noted in the previous item, the exclude
list on the alternate client takes precedence over the exclude list on the
primary client.
For example: If the current version of the exclude list has the entry *.jpg,
and some .jpg files were included in the backup, the .jpg files can be
selected for the restore but are not in fact restored. To restore the files,
you must change the exclude list on the primary (or alternate) client.
For ordinary snapshot backups, the exclude list is consulted during the
backup and any files in the exclude list are not backed up. For
snapshot-based backups, however, all files are included in the snapshot.
The exclude list is consulted only when a storage unit backup is created
from the snapshot. If the snapshot is retained after the backup (for the
instant recovery feature) and the snapshot is available at the time of the
restore, NetBackup restores files from the snapshot. Since all files are
available in the snapshot (including those that would be excluded from a
storage unit backup), NetBackup incorrectly consults the current exclude
list on the client or alternate client. Any files in the exclude list are skipped
during the restore.
This issue will be addressed in a future release of NetBackup.
Bare Metal Restore (BMR) issues

The following BMR issues are specific to UNIX systems:
■ (ET1861330) Restoring a Solaris SPARC-Sun4V client to a SAN disk using
BMR-DDR mechanism can cause a failure during the first boot. That can render
the restored system unusable.
BMR supports Dissimilar Disk Restore (DDR) of a Solaris host. You can map
system volumes or slices originally residing on a host’s local disks to SAN
Disks (LUNs). That enables the host to boot off the SAN-LUNs after the restore
is completed. In NetBackup 6.5.5, if the client system has a Solaris
NetBackup Operations Manager (NOM) issues
SPARC-Sun4V processor, then attempting this type of a restore can cause

failures during the first boot after a BMR restore. That can cause a kernel panic
and render the restored client unusable. No known workaround or solution
exists for this problem.
■ (ET1766898) Solaris10 x64 Update-5 and Solaris SPARC Update-6 client self
restore failed with a Windows 2003 x64 master server.
In the backup environment, if the NetBackup/BMR master server is a Windows
2003 (x86 or x64) host and the NetBackup/BMR client is a Solaris10_x64 or a
Solaris SPARC host, then the bare metal restore of the Solaris host fails. The
following message appears on the console of the Solaris client where the restore
failure occurred:
ERROR retrieving and/or generating disk usage data.
To avoid this issue, disable the logging from the BMR restore environment by
not selecting the Enable logging check box. You can disable the logging while
you perform a Prepare-To-Restore (PTR ) operation for a Solaris (SPARC or
x64) client with the NetBackup Administration Console. If you use the bmrprep
command line interface (CLI) to perform a PTR operation, then do not pass
the -logging parameter to the bmrprep command.
NetBackup Operations Manager (NOM) issues

■ (ET1593625) The post-installation of Data Migration failed. This issue can
happen in a rare case. To resolve this issue, restart the server.
■ (ET1557986) The Catalog not backed up alerts were not generated if the
catalog back job failed. This alert works if no catalog backup job was run in
the specified time frame. However, this alert is not generated if a catalog
backup job was run but failed.
■ (ET1463349) NOM failed to log on after the patch installation. If you encounter
this issue, restart the NOM web console services after the upgrade.
■ Before you attempt to upgrade a NOM cluster from NetBackup 6.5.2 or 6.5.3
to NetBackup 6.5.6, you should freeze the cluster node. You can do that from
the VCS user interface or use the VCS command line.
■ On Solaris, if you downgrade a NOM cluster from NetBackup 6.5.6 to a previous
version, the NOM web version appears incorrectly on the inactive node.
■ On Windows, in a NOM cluster, the NetBackup 6.5.6 installer attempts to start
the services on the inactive node after the upgrade finishes.
■ If you have clustered NOM in 6.5.6 and decide that you want to "uncluster" it,
then you must change the path in the configlocation.conf file to
Localization issues
<NOM_INSTALL_DIR> on both of the nodes. The configlocation.conf file is

located under <NOM_INSTALL_DIR>/config folder.
Localization issues
■ (ET1592679) An unexpected log conversion may occur with the vxlogview
log. The localized name of the strings that represent the backup targets were
invalid. A fix will be made in a future release that ensures vxlogview will be
able to convert the lines that contain any multibyte character.
■ (ET1556155) The Japanese vault store name becomes unreadable in the
bpresolver log.
■ (ET1556191) After selecting, Full Check including indexes an issue occurred

that caused ENTERPRISE_VAULT_DBCC_CHK_PREBKUP to be created, however
ENTERPRISE_VAULT_DBCC_CONT_ONERR was not created even though the
"Continue with backup if consistency check fails" was checked as the default
setting in the Client Properties dialog. The
ENTERPRISE_VAULT_DBCC_CONT_ONERR should have been created and set
to 1 or the Continue with backup if consistency check fails is not checked as
the default.
■ (ET1592462) The ffile of the root job is correctly encoded with UTF-8,
however, the ffile of the child jobs are incorrectly encoded with Shift-JIS.
■ (ET1592583) Unexpected log conversion with vxlogview caused invalid
localized names for the backup targets. vxlogview should be able to convert
the lines that contain any multibyte character.
■ (ET1633814) If a logon account was not raised with UAC, nothing would happen
even if an attempt was made to right-click the tracker icon. And if you
double-clicked the tracker icon the tracker.exe would crash.
If you encounter this issue, check Run this program as an administrator on
the compatibilities tab for the properties of the tracker.exe executable.
General Documentation issues

The following documents incorrectly indicate that PureDisk storage units support
Granular Recovery Technology (GRT):
■ NetBackup 6.5.3 patch readme
■ NetBackup 6.5.3 for Microsoft Exchange Server Administrator's Guide
■ NetBackup 6.5.4 for Microsoft SharePoint Server Administrator's Guide
■ NetBackup 6.5.4 Documentation Updates

■ NetBackup 7.0 for Microsoft SharePoint Server Administrator's Guide
■ NetBackup 7.0 for Microsoft Exchange Server Administrator's Guide
■ NetBackup 7.0 Administrator's Guide, Volume I
The following table indicates the disk storage units that support Granular
Recovery.
Table 2-1 Disk storage units that support Granular Recovery
Disk storage unit Granular Recovery supported
BasicDisk Yes
AdvancedDisk Yes
NearStore No
OpenStorage No
PureDisk No
SharedDisk No
SnapVault No
■ (ET1392433) The 6.5.2 documentation incorrectly states that the Expire After
Duplication option for storage lifecycle policies is available for Duplication
destinations as well as Backup destinations. This behavior was introduced in
NetBackup 6.5.4, not 6.5.2.
■ Refer to the NetBackup Bare Metal Restore (BMR) Administrator's Guide at the
next major release of NetBackup for documented corrections of the following
items:
■ In the storage area network Support section of Chapter 6, Restoring Clients,
the following text appears:
Bare Metal Restore can restore a system that is attached to a Storage Area
Network (SAN). On Windows, AIX, and Solaris systems, if the host bus
adapter (HBA) drivers are available in the restore environment, BMR
automatically restores the SAN-attached volumes. BMR does not support
the restoration of systems with SAN attached volumes on HP-UX and Linux.
The following text is the correct replacement text.
■ Bare Metal Restore can restore a system that is attached to a Storage
Area Network (SAN). If the host bus adapter (HBA) drivers are available
in the restore environment then:
- On Solaris 10, BMR automatically restores the SAN-attached boot and

data volumes.
- On Solaris 8 and 9, BMR automatically restores the SAN-attached data
volumes.
- On Windows, BMR automatically restores the SAN-attached data
volumes.
- On AIX, BMR automatically restores the SAN-attached data volumes.
- On HP-UX and Linux, BMR does not support the restoration of systems
with SAN attached volumes.
In the Configuration Summary section of Chapter 10, Managing clients and
configurations the following text should be added:
■ Client configuration can be modified to add, change, and remove a
license key for the software that is discovered for a protected system.
The license key, is also added to the protected system after restore using
the configuration to which the key was added. This facility is available
only for Veritas Storage Foundation products.
■ (ET1197993) The NetBackup 6.5 Administrator's Guide, Volume I, incorrectly

states that the Virtual Tape Option is necessary to create an NDMP storage
unit. That is incorrect. The NetBackup for NDMP license must be installed on
the media server to use a host as an NDMP storage unit.
■ The NetBackup Release Notes PDF that is available for download from the
Symantec Support Web site has been updated with the following corrections.
You can download the latest version of this document at your convenience:
■ SAN Client Platform Proliferation corrections
Page 7: Original paragraph
The following client platforms support the SAN client: AIX, HP-UX, Linux,
Solaris, and Windows, and the following media server platforms support
the SAN client: Red Hat 4 update 3 Linux x86_64 and Solaris 9/10 SPARC.
The SAN client is supported in this release with disk storage. Support for
tape storage may be added in a future release.
Page 7: Corrected paragraph for NetBackup 6.5.2
The following client platforms support the SAN client: AIX, HP-UX, Linux,
Solaris, and Windows, and the following media server platforms support
the SAN client: Red Hat 4 Update 3, Red Hat 4 Update 5 and SLES 9 SP3
Linux x86_64 and Solaris 9/10 SPARC. The SAN client is supported in this
release with disk storage. Support for tape storage may be added in a future
release.
Page 59, Table 2-19: Original paragraph
Media server:
You can use the following systems for the NetBackup media servers that
are attached to the SAN: - Linux - Red Hat 4.0 Update 3 X86_64 (EM64T or
AMD64) - Solaris 9 and 10 (SPARC)
Page 7: 59, Table 2-19: Corrected paragraph for NetBackup 6.5.2
Media server:
You can use the following systems for the NetBackup media servers that
are attached to the SAN: - Linux - Red Hat 4 Update 3, Red Hat 4 Update 5,
SLES 9 SP3 X86_64 (EM64T or AMD64) - Solaris 9 and 10 (SPARC)
■ NetBackup PureDisk Deduplication Option Naming Correction The New
Features chapter in the NetBackup 6.5 Release Notes document incorrectly
refers to the PureDisk Deduplication Option as PureDisk Storage Option
or PureDisk Optimization Option. These names and the corresponding
description have been corrected and a new updated version of the
NetBackup Release Notes document that is available for download from
the Symantec Support Web site.
■ Information that expains which policy types support the client encryption
option was not included in the NetBackup 6.5 Release Notes document. The
following list shows the policies types that support encryption in NetBackup
6.5:
■ AFS
■ DB2
■ Datastore
■ Informix-On-BAR
■ LOTUS_NOTES
■ Microsoft Exchange
■ Microsoft SharePoint
■ Microsoft SQL Server
■ Microsoft Windows
■ Oracle
■ SAP
■ Standard
■ Sybase
If you use one of the following policy types, you cannot select the encryption
check box in the policy attributes interface.
■ DataTools-SQL-BackTrk
UNIX-specific issues
■ FlashBackup
■ FlashBackup-Windows
■ NDMP
■ NetWare
■ Vault
■ (ET1268273) FlashBackup incremental backups do not operate as described

in the NetBackup 6.5 Snapshot Client Administrator's Guide, page 82.
The next revision of the Snapshot Client guide contains information similar
to the following:
■ For FlashBackup and FlashBackup-Windows full policies, all blocks in the
disk or raw partition (as selected in the Backup Selections tab) are backed
up.
■ For FlashBackup and FlashBackup-Windows incremental policies, complete
files are backed up based on changes to the file Modified Time or Create
Time since the last full or incremental backup.
■ For FlashBackup-Windows Incremental policies, the Modified Time and
Create Time changes are queried from the NTFS Master File Table (MFT)
for File entries only. Directories are not queried. Any newly created or
modified files are backed up as complete files and corresponding directories
up the tree are also backed up. Newly created but empty directories are not
considered for FlashBackup-Windows incremental backups.
Warning: During FlashBackup-Windows incremental backups, jobs complete

with status 0 but some skipped files may occur due to limitations with the
NTFS file system.
The NTFS Master File Table does not update the Create Time or Modified Time
of a file or folder when the following changes are made:
■ File or directory rename operations
■ File or directory security changes
■ File or directory attribute changes: read only, hidden, system, archive bit
UNIX-specific issues
■ (ET1258372) For Solaris 10 clients using the NAS_Snapshot snapshot method,
if backup target file systems are not mounted explicitly as NFS version 3, the
Windows-specific issues
snapshot directory on the filer volume is not accessible through NFS as required
to support snapshot restore. That may result in failed backups, or those backups
that appear to succeed, but are immediately expired during routine snapshot
image validation. For Solaris 10 clients, file system mount commands should
contain the following option:
-o vers=3
For example:
mount -F nfs -o vers=3 file1:/vol/vol2 /mnt
■ (ET1380306) The initial PBX install or version upgrade, "NetBackup 6.5 ICS
1.4.37.9 for HP", failed to install or upgrade during a NetBackup install. It fails
with the following error.
The platform type of installics (ICS-HPUX-11.00 CS-HPUX-11.23)
does not match the platform type of this machine (ICS-HPUX-11.00).
To resolve this issue, a fix was made to a new PBX install or version upgrade,
titled, "NetBackup 6.5 ICS 1.4.37.9a for HP". Note the 'a' in the image name.
You can easily denote the new image by the existence of the
./platform.txt.old file.
■ (ET1379837) An issue exists in this release update that can cause any supported
version of HP-UX (PA-RISC) to encounter memory consumption issues with
NetBackup processes. The degree of consumption varies and depends on your
usage pattern. In addition, it is likely that the NBEMM process is the first
process to stop with a core dump. For more information about this issue, refer
to the following Technote on the Symantec Support Web site.
■ (ET1320943) FAT32 file systems are not supported on Windows x86 and x64.
■ Product dependency notification for customers running Microsoft Windows
Vista or Windows 2008 server.
If you protect client (or server) systems that are running Microsoft Windows
Vista or Windows 2008 server, you may need to install Microsoft hotfix number
KB952696. If you attempt to back up any protected files that the operating
system has encrypted, NetBackup is not able to 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 hotfix 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 hotfix is
required for your operating system version
■ (ET1233823) There is a problem regarding backing up Windows 2008 encrypted
files. That is a Microsoft issue. A NetBackup fix may occur in a future 6.5
release. To avoid this issue, run NetBackup as Administrator and not as a
Backup Operator.
■ (ET1557527) When installing NetBackup on a Windows 2008 VCS cluster
configuration, the Next option on the Settings dialog is highlighted. However,
if you change data on that dialog, the Next option may become grayed out. If
you encounter this issue, navigate through each of the cluster input fields in
the dialog. After that is complete the Next option is enabled and you can select
it to continue with the install.
■ (ET1635638) On a clustered (VCS) Windows 2008 environment, a Snapshot
backup takes longer to complete as compared to a backup on a non-clustered
environment. The Snapshot technology that is used in this case was Microsoft
Volume Shadow Copy (VSS). In an engineering test environment, a substantial
time delay was noted for the VSS APIs. A single NetBackup backup job took
more than 10 minutes to complete.
Symantec is currently in discussions with Microsoft to develop a solution for
this issue. A possible fix is planned to be released in the next release of this
product.
■ (ET1530250) During a NetBackup 6.5 GA installation on a system that has
Symantec Endpoint Protection (SEP) 11.0 installed with the network threat
protection options enabled, your system can lose network connectivity during
the install. That is a known Windows-only issue with the SEP MR4-MP1
(11.0.4010) version. Symantec recommends that you upgrade to the latest SEP
11 version using the following link to the Symantec Support Web site.
http://www.symantec.com/business/support/downloads.jsp?pid=54619
■ This Release Update Windows installation sets the MaxLogFileSizeKB in

nblog.conf to a value of 51200. The value of MaxLogFileSizeKB is set to the
new value even if it was changed before the Release Update was applied.
■ If you update a clustered NetBackup server in a VCS configuration, Symantec
recommends that you run the manual patch install.
■ Configuring NOM and VxAT on the same cluster is not supported on VCS
Windows.
■ When upgrading a media server using NetBackup LiveUpdate in the
environments that have the master and the media servers that reside on
separate domains, you must stop tracker.exe on the target media server or
the LiveUpdate upgrade fails.
To avoid this issue, you must ensure that the tracker.exe is not running on the
media server before executing a LiveUpdate upgrade.
Chapter 3
Current release content
index
■ About the NetBackup 6.5.6 master Etrack index list
About the NetBackup 6.5.6 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.
NB_SMJ_6.5.6.winnt.x64
1599744
NB_JAV_6.5.6.winnt.x64
1839613 1884626 1884622 1943448
NB_JAV_6.5.6
1599744 1839613 1884626 1884622
NB_NOM_6.5.6.winnt.IA64
1831176 1907862 1933026
NB_SMJ_6.5.6.winnt.x86
1599744
62 Current release content index
NB_NOM_6.5.6
1907862 1933026
NB_VLT_6.5.6
1794468 1858013 1916126 1977134
NB_DRO_6.5.6
1866066
NB_SMU_6.5.6
1595906 1599627 1639406 1723817 1785248 1805843
NB_SAP_6.5.6
1712349
NBLU_6.5.6.WIN
1460848 1480696 1528999 1536425 1542088 1547306 1590159 1596861 1597208
1597972 1599744 1631661 1634234 1638478 1664462 1675254 1679600 1704581
1705684 1707433 1707868 1710909 1711324 1712349 1714249 1718144 1719203
1719680 1719702 1722830 1728854 1730639 1732542 1734140 1734223 1738123
1739319 1740155 1741195 1744950 1745302 1745377 1747399 1747555 1747569
1748013 1752343 1764854 1766444 1766917 1779258 1781618 1783339 1785089
1785659 1789424 1789558 1789585 1789641 1789765 1790219 1791096 1791524
1792866 1794468 1796017 1799804 1801905 1804988 1805136 1806885 1807274
1809048 1810756 1819232 1819301 1820155 1821904 1821984 1825012 1826305
1826322 1827098 1827104 1827744 1828769 1828972 1829932 1831176 1831736
1831761 1832503 1832613 1833201 1833292 1833464 1833666 1835540 1835624
1835707 1836933 1836986 1837066 1839613 1839711 1839719 1840607 1841542
1841568 1843049 1843764 1843872 1845860 1846940 1847084 1848330 1848666
1849860 1849943 1852360 1853385 1853394 1853866 1856217 1857187 1857252
1858013 1858290 1859377 1859453 1860181 1860692 1860959 1862122 1862209
1862304 1863960 1864777 1866066 1868671 1868678 1868794 1870160 1870456
1870947 1872075 1872279 1872287 1872413 1872889 1873522 1873571 1873581
1874681 1876720 1877351 1877618 1877759 1878504 1880236 1881158 1881198
1881291 1881498 1884626 1885209 1886293 1886421 1888833 1889326 1889345
1890218 1890642 1891943 1893311 1895880 1896534 1896543 1896603 1899129
1899241 1899396 1899890 1899897 1899905 1899913 1900020 1902040 1902371
Current release content index 63
1903062 1904226 1904665 1904949 1905456 1907862 1908225 1908411 1908524

1909591 1909790 1910069 1911562 1911860 1912641 1913037 1913666 1913799
1915644 1915646 1915820 1916126 1916513 1916686 1918715 1919621 1921796
1921983 1921986 1922036 1922416 1922701 1922757 1926383 1928230 1929531
1930100 1930371 1932411 1932648 1932922 1933026 1933195 1933582 1933793
1934281 1934314 1935158 1935275 1935315 1938221 1938292 1938338 1938407
1939187 1939222 1939489 1940115 1941163 1941515 1943162 1943448 1943602
1944481 1944698 1944757 1946513 1946541 1947258 1947786 1948589 1948963
1951005 1951106 1952176 1952201 1953019 1953062 1953348 1954237 1954355
1954375 1956179 1956504 1957566 1957971 1957987 1960773 1961191 1962253
1962267 1962333 1962479 1966124 1967099 1967351 1970866 1971483 1971795
1972758 1974980 1977134 1977211 1977419 1978121 1978579 1980507 1982709
1982758 1987803 1989335 1993398 1997132 1884622
NB_6.5.6.winnt.x86
1460848 1480696 1528999 1536425 1542088 1547306 1590159 1596861 1597208
1597972 1631661 1634234 1638478 1664462 1675254 1679600 1704581 1705684
1707433 1707868 1710909 1711324 1712349 1714249 1718144 1719203 1719680
1719702 1722830 1728854 1730639 1732542 1734140 1734223 1738123 1739319
1740155 1741195 1744950 1745302 1745377 1747399 1747555 1747569 1748013
1752343 1764854 1766444 1766917 1779258 1781618 1783339 1785089 1785659
1789424 1789558 1789585 1789641 1789765 1790219 1791096 1791524 1792866
1794468 1796017 1799804 1801905 1804988 1805136 1806885 1807274 1809048
1810756 1819232 1819301 1820155 1821904 1821984 1825012 1826305 1826322
1827098 1827104 1827744 1828769 1828972 1829932 1831736 1831761 1832503
1832613 1833201 1833292 1833464 1833666 1835540 1835624 1835707 1836933
1836986 1837066 1839711 1839719 1840607 1841542 1841568 1843049 1843764
1843872 1845860 1846940 1847084 1848330 1848666 1849860 1849943 1852360
1853385 1853394 1853866 1856217 1857187 1857252 1858013 1858290 1859377
1859453 1860181 1860692 1860959 1862122 1862209 1862304 1863960 1864777
1866066 1868671 1868678 1868794 1870160 1870456 1870947 1872075 1872279
1872287 1872413 1872889 1873522 1873571 1873581 1874681 1876720 1877351
1877618 1877759 1878504 1880236 1881158 1881198 1881291 1881498 1885209
1886293 1886421 1888833 1889326 1889345 1890218 1890642 1891943 1893311
1895880 1896534 1896543 1896603 1899129 1899241 1899396 1899890 1899897
1899905 1899913 1900020 1902040 1902371 1903062 1904226 1904665 1904949
1905456 1908225 1908411 1908524 1909591 1909790 1910069 1911562 1911860
1912641 1913037 1913666 1913799 1915644 1915646 1915820 1916126 1916513
1916686 1918715 1919621 1921796 1921983 1921986 1922036 1922416 1922701
1922757 1926383 1928230 1929531 1930100 1930371 1932411 1932648 1932922
1933195 1933582 1933793 1934281 1934314 1935158 1935275 1935315 1938221
1938292 1938338 1938407 1939187 1939222 1939489 1940115 1941163 1941515
1943162 1943602 1944481 1944698 1944757 1946513 1946541 1947258 1947786

1948589 1948963 1951005 1951106 1952176 1952201 1953019 1953062 1953348
1954237 1954355 1954375 1956179 1956504 1957566 1957971 1957987 1960773
1961191 1962253 1962267 1962333 1962479 1966124 1967099 1967351 1970866
1971483 1971795 1972758 1974980 1977134 1977211 1977419 1978121 1978579
1980507 1982709 1982758 1987803 1989335 1993398 1997132
NB_6.5.6
1460848 1480696 1512177 1528999 1536425 1542088 1543088 1545284 1590159
1596861 1597208 1631661 1675254 1679600 1704581 1707433 1707868 1711324
1714249 1719203 1719680 1719721 1722830 1724603 1729238 1730639 1732542
1734223 1738123 1740155 1741195 1747399 1747569 1752343 1764854 1785089
1785659 1789424 1789558 1789641 1790219 1791096 1791524 1792866 1799804
1804988 1805136 1807274 1810756 1821904 1821984 1825012 1827098 1828769
1828964 1828972 1829932 1831736 1831761 1833464 1833666 1834071 1835540
1835624 1835707 1836933 1836986 1837066 1841542 1841568 1843049 1843872
1845860 1846940 1848666 1849292 1851360 1852047 1852360 1853866 1856217
1857187 1857252 1857920 1859453 1859719 1860692 1861585 1862304 1863960
1866912 1868671 1868678 1868794 1870160 1870947 1872075 1872279 1872287
1872413 1873522 1873571 1873581 1874681 1876720 1877351 1877759 1879957
1880236 1885209 1885425 1886421 1888833 1889345 1890218 1896534 1896543
1896603 1898027 1899129 1899241 1900020 1902040 1902371 1904665 1904949
1905456 1907097 1907564 1908411 1909790 1910069 1911562 1911860 1912641
1915820 1916513 1916686 1916729 1918715 1919621 1921796 1921983 1921986
1922036 1922701 1928230 1932411 1932922 1933195 1933793 1934281 1935158
1935275 1935315 1935378 1938141 1938221 1938292 1938338 1938407 1939187
1939222 1939489 1940115 1941163 1943162 1944698 1944757 1946513 1946541
1947786 1948589 1952176 1953019 1954237 1954355 1954375 1956504 1957566
1957987 1961191 1962253 1962333 1962479 1962547 1966124 1967099 1970866
1971483 1971795 1972758 1974980 1977211 1978121 1978579 1980507 1982709
1982758 1987788 1987803 1989335 1993398 1997132 2008084
NB_ORA_6.5.6
1843171 1862242 1862252 1895880 1913799 1929531 1951005 1997002
NB_NOM_6.5.6.winnt.x86
1831176 1907862 1933026
NB_JAV_6.5.6.winnt.IA64
1839613 1884626 1943448 1884622
NB_DMP_6.5.6
1801905 1809048 1881198 1889326 1908225
NB_CLT_6.5.6
1460848 1480696 1512177 1528999 1536425 1542088 1543088 1545284 1590159
1596861 1597208 1631661 1675254 1679600 1704581 1707433 1707868 1711324
1714249 1719203 1719680 1719721 1722830 1724603 1729238 1730639 1732542
1734223 1738123 1740155 1741195 1744339 1747399 1747569 1752343 1764854
1785089 1785659 1789424 1789558 1789641 1790219 1791096 1791524 1792866
1799804 1804988 1805136 1807274 1810756 1821904 1821984 1822385 1825012
1827098 1828769 1828964 1828972 1829932 1831736 1831761 1833464 1833666
1834071 1835540 1835624 1835707 1836933 1836986 1837066 1841542 1841568
1843049 1843764 1843872 1845860 1846940 1848666 1849292 1851360 1852047
1852360 1853866 1856217 1857187 1857252 1857920 1859453 1859719 1860692
1861585 1862304 1863960 1866912 1868671 1868678 1868794 1870160 1870947
1872075 1872279 1872287 1872413 1873522 1873571 1873581 1874681 1876720
1877351 1877759 1879957 1880236 1881291 1885209 1885425 1886421 1888833
1889345 1890218 1896534 1896543 1896603 1898027 1899129 1899241 1900020
1902040 1902371 1904665 1904949 1905456 1907097 1907564 1908411 1909790
1910069 1911562 1911860 1912641 1915820 1916513 1916604 1916686 1916729
1917710 1918715 1919621 1921796 1921983 1921986 1922036 1922701 1928230
1932411 1932922 1933195 1933793 1934053 1934281 1935158 1935275 1935315
1935378 1938141 1938221 1938292 1938338 1938407 1939187 1939222 1939489
1940115 1941163 1943162 1944698 1944757 1946513 1946541 1947786 1948589
1952176 1953019 1954237 1954355 1954375 1956504 1957566 1957987 1961191
1962253 1962333 1962479 1962547 1966124 1967099 1970866 1971483 1971795
1972758 1974980 1977211 1978121 1978579 1980507 1982709 1982758 1987788
1987803 1989335 1993398 1997132 2008084
NBLU_6.5.6.UNIX
1460848 1480696 1512177 1528999 1536425 1542088 1543088 1545284 1547306
1590159 1595906 1596861 1597208 1599627 1599744 1631661 1637610 1637613
1639406 1675254 1679600 1702400 1704581 1707433 1707868 1711324 1712349
1714249 1718144 1719203 1719680 1719721 1722830 1723817 1724603 1729238
1730639 1732542 1734223 1738123 1740155 1741195 1744339 1744448 1745311
1747263 1747399 1747569 1752343 1764854 1766444 1785089 1785248 1785659
1789424 1789558 1789641 1790219 1791096 1791524 1792866 1794468 1796017

1799804 1801905 1804988 1805136 1805843 1807274 1809048 1810756 1819301
1821904 1821984 1822385 1825012 1827098 1827104 1828769 1828964 1828972
1829932 1831736 1831761 1833201 1833464 1833666 1834071 1835540 1835624
1835707 1836933 1836986 1837066 1839613 1841542 1841568 1843049 1843171
1843764 1843872 1845860 1846940 1848666 1849292 1851360 1852047 1852360
1853866 1856217 1857187 1857252 1857920 1858013 1859453 1859719 1860692
1861585 1862242 1862252 1862304 1862802 1863960 1864692 1866066 1866912
1868671 1868678 1868794 1870160 1870947 1872075 1872279 1872287 1872413
1873522 1873571 1873581 1874681 1876720 1877351 1877759 1879957 1880236
1881198 1881291 1884626 1885209 1885425 1886421 1888833 1889326 1889345
1890218 1895880 1896534 1896543 1896603 1898027 1899129 1899241 1900020
1902040 1902371 1903062 1904665 1904949 1905456 1907097 1907564 1907862
1908225 1908411 1909790 1910069 1911562 1911860 1912641 1913799 1915820
1916126 1916513 1916604 1916686 1916729 1917710 1918715 1919621 1921796
1921983 1921986 1922036 1922701 1928230 1929531 1932411 1932648 1932922
1933026 1933195 1933793 1934053 1934281 1935158 1935275 1935315 1935378
1938141 1938221 1938292 1938338 1938407 1938970 1939187 1939222 1939489
1940115 1941163 1943162 1944698 1944757 1946513 1946541 1947786 1948589
1951005 1952176 1953019 1954237 1954355 1954375 1956504 1957566 1957987
1959006 1959755 1961191 1962253 1962333 1962479 1962547 1966124 1967099
1970866 1971483 1971795 1972758 1974980 1975605 1977134 1977211 1978121
1978579 1980507 1982709 1982758 1987788 1987803 1989335 1993398 1997002
1997132 2008084 1884622
NB_6.5.6.winnt.IA64
1460848 1480696 1528999 1536425 1542088 1547306 1590159 1596861 1597208
1597972 1631661 1634234 1638478 1664462 1675254 1679600 1704581 1705684
1707433 1707868 1710909 1711324 1712349 1714249 1718144 1719203 1719680
1719702 1722830 1728854 1730639 1732542 1734140 1734223 1738123 1739319
1740155 1741195 1744950 1745302 1745377 1747399 1747555 1747569 1748013
1752343 1764854 1766444 1766917 1779258 1781618 1783339 1785089 1785659
1789424 1789558 1789585 1789641 1789765 1790219 1791096 1791524 1792866
1794468 1796017 1799804 1801905 1804988 1805136 1806885 1807274 1809048
1810756 1819232 1819301 1820155 1821904 1821984 1825012 1826305 1826322
1827098 1827104 1827744 1828769 1828972 1829932 1831736 1831761 1832503
1832613 1833201 1833292 1833464 1833666 1835540 1835624 1835707 1836933
1836986 1837066 1839711 1839719 1840607 1841542 1841568 1843049 1843764
1843872 1845860 1846940 1847084 1848330 1848666 1849860 1849943 1852360
1853385 1853394 1853866 1856217 1857187 1857252 1858013 1858290 1859377
1859453 1860181 1860692 1860959 1862122 1862209 1862304 1863960 1864777
1866066 1868671 1868678 1868794 1870160 1870456 1870947 1872075 1872279
1872287 1872413 1872889 1873522 1873571 1873581 1874681 1876720 1877351

1877618 1877759 1878504 1880236 1881158 1881198 1881291 1881498 1885209
1886293 1886421 1888833 1889326 1889345 1890218 1890642 1891943 1893311
1895880 1896534 1896543 1896603 1899129 1899241 1899396 1899890 1899897
1899905 1899913 1900020 1902040 1902371 1903062 1904226 1904665 1904949
1905456 1908225 1908411 1908524 1909591 1909790 1910069 1911562 1911860
1912641 1913037 1913666 1913799 1915644 1915646 1915820 1916126 1916513
1916686 1918715 1919621 1921796 1921983 1921986 1922036 1922416 1922701
1922757 1926383 1928230 1929531 1930100 1930371 1932411 1932648 1932922
1933195 1933582 1933793 1934281 1934314 1935158 1935275 1935315 1938221
1938292 1938338 1938407 1939187 1939222 1939489 1940115 1941163 1941515
1943162 1943602 1944481 1944698 1944757 1946513 1946541 1947258 1947786
1948589 1948963 1951005 1951106 1952176 1952201 1953019 1953062 1953348
1954237 1954355 1954375 1956179 1956504 1957566 1957971 1957987 1960773
1961191 1962253 1962267 1962333 1962479 1966124 1967099 1967351 1970866
1971483 1971795 1972758 1974980 1977134 1977211 1977419 1978121 1978579
1980507 1982709 1982758 1987803 1989335 1993398 1997132
NB_NOM_6.5.6.winnt.x64
1831176 1907862 1933026
1839613 1884626 1943448 1884622
NB_SMJ_6.5.6.winnt.IA64
1599744
NB_BMR_6.5.6
1702400 1827104 1903062
NB_DB2_6.5.6
1747263
NB_6.5.6.winnt.x64
1460848 1480696 1528999 1536425 1542088 1547306 1590159 1596861 1597208
1597972 1631661 1634234 1638478 1664462 1675254 1679600 1704581 1705684
1707433 1707868 1710909 1711324 1712349 1714249 1718144 1719203 1719680
1719702 1722830 1728854 1730639 1732542 1734140 1734223 1738123 1739319

1740155 1741195 1744950 1745302 1745377 1747399 1747555 1747569 1748013
1752343 1764854 1766444 1766917 1779258 1781618 1783339 1785089 1785659
1789424 1789558 1789585 1789641 1789765 1790219 1791096 1791524 1792866
1794468 1796017 1799804 1801905 1804988 1805136 1806885 1807274 1809048
1810756 1819232 1819301 1820155 1821904 1821984 1825012 1826305 1826322
1827098 1827104 1827744 1828769 1828972 1829932 1831736 1831761 1832503
1832613 1833201 1833292 1833464 1833666 1835540 1835624 1835707 1836933
1836986 1837066 1839711 1839719 1840607 1841542 1841568 1843049 1843764
1843872 1845860 1846940 1847084 1848330 1848666 1849860 1849943 1852360
1853385 1853394 1853866 1856217 1857187 1857252 1858013 1858290 1859377
1859453 1860181 1860692 1860959 1862122 1862209 1862304 1863960 1864777
1866066 1868671 1868678 1868794 1870160 1870456 1870947 1872075 1872279
1872287 1872413 1872889 1873522 1873571 1873581 1874681 1876720 1877351
1877618 1877759 1878504 1880236 1881158 1881198 1881291 1881498 1885209
1886293 1886421 1888833 1889326 1889345 1890218 1890642 1891943 1893311
1895880 1896534 1896543 1896603 1899129 1899241 1899396 1899890 1899897
1899905 1899913 1900020 1902040 1902371 1903062 1904226 1904665 1904949
1905456 1908225 1908411 1908524 1909591 1909790 1910069 1911562 1911860
1912641 1913037 1913666 1913799 1915644 1915646 1915820 1916126 1916513
1916686 1918715 1919621 1921796 1921983 1921986 1922036 1922416 1922701
1922757 1926383 1928230 1929531 1930100 1930371 1932411 1932648 1932922
1933195 1933582 1933793 1934281 1934314 1935158 1935275 1935315 1938221
1938292 1938338 1938407 1939187 1939222 1939489 1940115 1941163 1941515
1943162 1943602 1944481 1944698 1944757 1946513 1946541 1947258 1947786
1948589 1948963 1951005 1951106 1952176 1952201 1953019 1953062 1953348
1954237 1954355 1954375 1956179 1956504 1957566 1957971 1957987 1960773
1961191 1962253 1962267 1962333 1962479 1966124 1967099 1967351 1970866
1971483 1971795 1972758 1974980 1977134 1977211 1977419 1978121 1978579
1980507 1982709 1982758 1987803 1989335 1993398 1997132
NB_BBS_6.5.6
1637610 1637613 1938970 1959755 1975605
NB_SNC_6.5.6
1547306 1718144 1744448 1745311 1766444 1796017 1819301 1833201 1862802
1864692 1932648 1959006
Chapter 4
Current release content
■ About Release Update conventions
■ About NetBackup 6.5.6 Release Content
About Release Update conventions

This section contains the Release Update conventions, content, and historical
content that is applicable to the release.
The following list describes the conventions used in the subsections that following
this section. Each item listed in the Current Release Update subsection describes
a feature, enhancement, or issue fixed with this Release Update:
■ Description
Describes a particular problem that is contained in this Release Update.
■ ** Description **
Describes a problem that can lead to potential data loss. Please read these
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.
70 Current release content
About NetBackup 6.5.6 Release Content

That section contains a list of the fixes and changes that comprise the NetBackup
6.5.6 release.
Etrack Incident: 1829932
■ Associated Primary Etrack: 1791855
■ TITAN cases: 320-214-099 411-446-945
■ Contained in: NBLU_6.5.6.UNIX NBLU_6.5.6.WIN NB_6.5.6 NB_6.5.6.winnt.IA64
NB_6.5.6.winnt.x64 NB_6.5.6.winnt.x86 NB_CLT_6.5.6
■ Description:
Persistent Frozen Images that span media may encounter a condition where
the NetBackup Job Manager (NBJM) cancels an active job upon notification
from the Policy Execution Manager (PEM). That would cause a status 223 error.
■ TITAN cases: 281-756-782
■ Description:
The max_partially_full_media limit was not enforced for multiple copy jobs.
■ Additional Notes:
The max_partially_full_media limit is not enforced to be less than the
number of configured copies for a job. For example, if the
max_partially_full_media limit is configured at one for a pool, and the pool
is used in a two-copy job, the limit is enforced at two for that job.
■ TITAN cases: 320-226-337
■ Contained in: NBLU_6.5.6.WIN NB_6.5.6.winnt.IA64 NB_6.5.6.winnt.x64
NB_6.5.6.winnt.x86
■ Description:
The import of OpenVMS tapes from NetBackup 5.1 would fail with a status 24
error on the last fragment. That was a winsock error 10054 error.
Current release content 71

■ TITAN cases: 240-949-938
■ Description:
A fix was made to correct a bpjobd core dump issue to handle the jobs that
were done. That caused jobs to not display in the activity monitor.
■ TITAN cases: 220-688-894
■ Contained in: NBLU_6.5.6.UNIX NBLU_6.5.6.WIN NB_6.5.6.winnt.IA64
NB_6.5.6.winnt.x64 NB_6.5.6.winnt.x86 NB_BMR_6.5.6
■ Description:
Duplicate drivers as well as different driver versions were added if you
attempted to add or remove device drivers while you edited a Windows
configuration. A fix has been made to correct this issue.
■ TITAN cases: 281-715-968
■ Description:
The bp.conf entry KEEP_VAULT_SESSIONS_DAYS does not work on 64-bit UNIX
platforms that run HP-IA64 or Tru64.
■ Work around:
To resolve this issue, use the default value of 30 days.
■ Contained in: NBLU_6.5.6.UNIX NB_6.5.6 NB_CLT_6.5.6
■ Description:
A point-in-time rollback restore would fail if primary volume group contained
more than one disk.
■ Work around:
To avoid this issue, you can perform normal restore.

NB_6.5.6.winnt.x86
■ Description:
A change was made to correct an NbWin.exe core dump issue on the Backup,
Archive, and Restore interface.
■ TITAN cases: 320-214-699
■ Description:
NetBackup did not work with host file entries. A fix was made to ensure that
the bpclntcmd -ip does not fail with an unrecoverable error.
■ TITAN cases: 320-233-457
■ Description:
The Disk Pool Committed Space algorithm was inappropriate to determine the
space allocation for user backups.
The estimated job size of user jobs (and oracle backup jobs) is computed as the
space difference between the high water mark and full capacity. In some
configurations that can cause jobs to be throttled even in instances where
there is a large amount of available disk space.
A change has been added that enables you to change the estimated size for
these jobs to a value of your choice. You can use the following command to
make that change:
nbemmcmd -changesetting -USER_JOB_KBYTES_ESTIMATE kbytes
-machinename masterservername
If a non-zero value is set for this parameter, then that value is used as an
estimated size for these jobs.
■ Work around:
If you encounter this issue, turn off Job Throttling on the master server using
the following command: nbemmcmd -changesetting
-DISABLE_DISK_STU_JOB_THROTTLING yes

■ Description:
The ltid -tables command did not correctly report the robotic daemon
internal states with the installation of NetBackup 6.5.4 and 6.5.5 patches. The
support script calls this command.
■ Description:
A change was made to correct an issue that caused NBPEM to crash on
shutdown when life-cycle jobs were run.
■ TITAN cases: 312-166-406
■ Description:
Restores appeared to fail on HP-IA64 media servers because of misleading
messages in the progress log.
■ TITAN cases: 320-172-288
NB_6.5.6.winnt.x86
■ Description:
Point-in-time restore on an SQL server would fail. Changes were made to the
point-in-time restore batch file to correct this issue.
■ Description:
A cluster failover can leave shared memory segments in memory. A change
was made to release the shared memory segments as soon as possible to
minimize the possibility that a cluster failover has any issues. The user can
then run NetBackup.
■ TITAN cases: 281-842-282 411-451-612
■ Description:
A change was made to correct an issue that caused nbpem to core dump.
■ TITAN cases: 312-179-569
■ Description:
You can now enable the Catalog Recovery Wizard from the top of the screen
in the Windows user interface when you use the NetBackup server license.
■ TITAN cases: 320-203-156
■ Description:
Communication delays with bpjobd caused a long delay before nbjm would
send a resource allocation request for a job to nbrb. During this period, nbjm
did not send any jobs to nbrb for evaluation. A change was made to address
this issue.
■ TITAN cases: 220-673-643

■ Description:
You can monitor/cancel/restart individual SAP restore streams of a multistream
SAP restore when single job ID represents all of the streams.
■ TITAN cases: 281-530-425
■ Description:
The High Water Mark was not used in the Disk Pools for a NetBackup clustered
master server.
■ Description:
If a LiveUpdate job was started when the client was busy doing backups or
restores, the LiveUpdate job would receive a Resources Bus, error (134). You
cannot retry LiveUpdate jobs after you receive a status 134 error, however,
NBPEM would attempt to try the jobs again.
That fix ensures that NBPEM does not attempt to restart any LiveUpdate jobs.
■ TITAN cases: 320-210-627
■ Description:
Backups fail if an attempt is made to run a SAN Client backup of the client
with multiplexing set to a value greater than one. That failure results in a
status 25 error, "SAN client job crossing firewall fails when multiplexing is
greater than 1".
■ Work around:
To work around this issue, open the firewall between the SAN client and the
media server to all ports.

■ TITAN cases: 281-653-466
NB_6.5.6.winnt.x86
■ Description:
A backup of a Windows 2008 client silently skips the Shadow Copy Components
if multiple data streams are enabled.
■ Work around:
To avoid this issue, do not use Multiple Data streams. Or you can specify the
Shadow_Copy_Components, System_State, and each drive letter in the include
list.
■ TITAN cases: 320-144-985
NB_6.5.6.winnt.x86
■ Description:
When a client and server were configured with different locales, some files
were not visible or selectable when you browsed in the NetBackup-Java user
interface running on Windows.
■ Work around:
To work around the issue, use the Windows user interface or the command-line
interface.
Etrack Incident: 1987803 1954355 1974980 1916513
■ Description:
A change was made to disambiguate the status 800 error codes.

■ TITAN cases: 410-595-612
■ Description:
After NetBackup 6.5.5 was applied, users noticed that SLP created many more
batches, some with only one image.
■ Work around:
To resolve this issue, set DUPLICATION_GROUP_CRITERIA to zero.
■ TITAN cases: 240-983-030
■ Description:
A change was made to correct an issue that caused bogus job IDs to appear in
the Activity Monitor.
Etrack Incident: 1938292 1993398 1957987 1938221 1978579 1961191 1944698
■ Description:
That release contains the new command-line command, nbdecommission. That
command guides the user through the steps that are involved when you attempt
to decommission a media server.
■ TITAN cases: 411-437-832
■ Description:
A successful optimized duplication can create fragments in the image catalog
with truncated disk media IDs. A change has been added to resolve this
truncation issue.
■ TITAN cases: 220-693-188
■ Description:
A change was made to correct an issue that caused an nbrmms core dump to
occur randomly.
■ TITAN cases: 281-751-073 320-178-687
■ Description:
A consolidated differed ejects process would pick up only the most recent
record for a profile from vlteject.mstr. A change was added to ensure that
a consolidated eject with the deferred eject option configured, successfully
ejects all of the correct media.
■ TITAN cases: 220-704-727
■ Description:
The NetBackup Resource Broker (NBRB) appeared to go into an infinite loop
and hang if the RB_RESPECT_REQUEST_PRIORITY parameter is set to one in
rb.conf file.

■ TITAN cases: 410-990-600 411-697-192
■ Contained in: NBLU_6.5.6.UNIX NB_BBS_6.5.6
■ Description:
On Linux, the BMR media boot required the user to enter scsiLoadOrder
manually. That approach was prone to typos and very tedious. A change was
made that allows the BMR Restore Environment to fetch the original client's
scsiLoadOrder from the BMR master server. That happens even if media-based
restores (Virtual Media as well as Physical Media) are used. Thus, in normal
media-based restores scenarios, the user does not have to enter the
scsiLoadOrder manually.
Although it is no longer needed, you can still enter the scsiLoadOrder

manually. A user can use that in debug scenarios.
■ TITAN cases: 281-647-746
■ Contained in: NBLU_6.5.6.UNIX NB_CLT_6.5.6
■ Description:
An error 13 would occur if you attempted to export data from PureDisk to
NetBackup. The export would fail if a new line was added to the pathname of
a file that was included in the export list.
A change has been added that allows the pathname to have a new line added
to it and ensure that the operation is successful.
NB_6.5.6.winnt.x86
■ Description:
A change was made to ensure that redundant messages are not printed in the
bpfis command.

■ TITAN cases: 320-216-908
NB_6.5.6.winnt.x86
■ Description:
Exchange backups would fail with a Status 13 when backing up Public Folders,
as noted in bpbrm. Before the failure occurred, bpbkar32.exe reported a fault
and stopped logging.
■ TITAN cases: 320-180-378
■ Description:
Bpduplicate received an Arithmetic Exception (core dumped) if bpdbm could

not open dbfiles from the imageDB database.
■ TITAN cases: 320-181-184
■ Description:
The import, verify, and duplication job may not get canceled when a signal is
sent to them. A change has been added to address this issue.
■ TITAN cases: 220-696-449
■ Description:
NetBackup no longer relies on the nickname of the host connection object in
IBM 6000/8000 arrays. NetBackup depends on the name of that host-connect
object to identify the volume group. That change allows better scalability in
enterprise environments. The following is a list of reasons to support the need
for this change:
■ A client might have multiple volume groups for different business reasons.
As the nickname needs to be unique, it is not possible to have the same
name for all the host-connect objects.
■ A client might have multiple HBAs and hence the host connections need
to be defined more that once. As the nickname needs to be unique, it is not
possible to have the same name for all the host-connect objects.
■ A client may designate a few of the volumes in a group to have FlashCopy
relations.
Customers should not be constrained to have only one host connection and
that it must be the same as the hostname.
■ TITAN cases: 281-889-782
■ Description:
A change was made to address an issue that caused nbstserv to frequently
terminate after a NetBackup 6.5.5 patch install. That occurred when the
duplication manager submitted a job that had images from different storage
lifecycle Policies (SLPs).
■ Work around:
If you encounter this issue, you should prevent mixing images from different
images in a duplication job, so this log message does not get hit.
In the SLP configuration file (netbackup/db/config/LIFECYCLE_PARAMETERS)
set the following parameter as follows:
DUPLICATION_GROUP_CRITERIA 0
■ TITAN cases: 220-625-050
NB_6.5.6.winnt.x86
■ Description:
If the NetBackup client was configured to exclude Exchange-related files (*.log
or *.edb), then GRT-enabled backups would fail the granular process.
■ Work around:
To resolve this issue, remove the Exchange-related exclude lists.
■ TITAN cases: 230-694-117
■ Description:
On an HP-UX IA64 platform, an attempt to use bpadm or vmadm to update the
volume configuration of an ACS library may fail.
■ Work around:
Use the vmupdate command line program or the Windows or Java GUI instead.
■ TITAN cases: 281-791-148 290-460-374
NB_6.5.6.winnt.x64 NB_6.5.6.winnt.x86 NB_SNC_6.5.6
■ Description:
An off-host backup that used TimeFinder failed with a status 130 on a single
mount point with 53 disks.
■ Description:
Anyone who used a Windows master server cannot configure a policy to use
FIMs that were released in NetBackup 6.5.2 and NetBackup 6.5.3.
■ TITAN cases: 320-190-450
NB_6.5.6.winnt.x86
■ Description:
A change was made to ensure that the Windows user interface filters on the
Start or End time for Job details in the Jobs tab on the Activity Monitor.
■ TITAN cases: 312-171-216
■ Contained in: NBLU_6.5.6.UNIX NB_BMR_6.5.6
■ Description:
The BMR Linux client backups would fail if the client was an HP server with
an integrated Smart Array Controller. That issue only occurred for certain
firmware versions of the Smart Array Controllers.
■ TITAN cases: 281-762-843 410-826-062 411-367-815
■ Description:
A change was made to address an issue that occurred because the IP addresses
that were not defined in the bp.conf with server entries were used.

■ Description:
A change was made to address an issue that caused a BPFIS core dump on a
Snap-vault backup.
■ Work around:
To avoid this issue, make sure that the secondary filer is accessible.
■ Description:
A change was made to correct a shared memory buffer sequence number
mismatch that sometimes occurred because of coherency issues. To resolve
this issue retry the comparison after a sleep(1).
■ TITAN cases: 281-748-608 410-689-572 410-874-557
NB_6.5.6.winnt.x86
■ Description:
DFSR backups can fault in bpbkar32.exe, in addition, the following two issues
were found:
■ DFSR backups that cause missing files from the browse for restore
operation.
■ Issues were found with the backup of multiple DFSR stores in that each
had the same named subdirectory.

■ Contained in: NBLU_6.5.6.UNIX NBLU_6.5.6.WIN NB_NOM_6.5.6
NB_NOM_6.5.6.winnt.IA64 NB_NOM_6.5.6.winnt.x64 NB_NOM_6.5.6.winnt.x86
■ Description:
That is a fix for the cross-site scripting issue in the WebGUI Help component.
■ TITAN cases: 410-630-281 410-636-350

■ Description:
A change was made to ensure that new sessions can be started after the
nbstlutil inactive -force command was used to stop SLPs.
■ Work around:
To resolve this issue, restart the nbstserv process.
■ Description:
The NBJM would crash after you downgraded from NetBackup 6.5.6 to 6.5.5
and then bpjobd attempted to clean the jobs that were run at 6.5.6.
■ Work around:
To work around this issue, remove the contents of install
path/db/jobs/restart directory.

■ Description:
A change was made to fix an issue that caused NBJM to crash on startup if it
could not communicate with NBRB.
■ TITAN cases: 281-795-539
NB_6.5.6.winnt.x86
■ Description:
The vcbvmname process was called if the name existed in the cache file.
■ TITAN cases: 230-680-297 411-041-609

NB_6.5.6.winnt.x86
■ Description:
The NDMP alternate restore did not work correctly with NbWin.exe if the path
contains Japanese characters.
■ Work around:
If you encounter this issue, you can use either of the following two
Workarounds : - Set the volume on the filer to UTF-8. - After a restore issue
occurs, convert ALTPATH.xxx from UTF-8 to Shift_JIS and then run the restore
manually with the file.
■ TITAN cases: 281-686-677
■ Description:
A restore of an Exchange 2007 backup image from Backup Exec 11d did not
work if the user used NetBackup 6.5.4 to restore this image to an Exchange
2007 Recovery storage group .
NB_6.5.6.winnt.x86
■ Description:
A change was made to address an issue that caused catalog backups to fail
with status 124 error.
■ TITAN cases: 320-199-975
■ Description:
A file read failed when backing up a CIFS share on CentOS client. That occurred
because the CentOS client did not correctly handle the listxattr system call
for the CIFS mounts. That fix allows the IGNORE_XATTR bp.conf entry to ignore
the extended attributes during the backup, and allows the following touch file
to ignore them during restore.
/usr/openv/netbackup/IGNORE_XATTR

■ TITAN cases: 220-700-187
■ Description:
The NetBackup Resource Broker would de-allocate the fiber transport resources
pre-maturely after a successful span.
■ TITAN cases: 240-988-882
■ Description:
A change was made to report the correct error number from
bpbrm.c:readline() instead of one coming back from check_for_signal().

■ TITAN cases: 220-693-144 240-998-887
NB_6.5.6.winnt.x86
■ Description:
The SnapshotSetID associated with a failed job (status 130) for NBU fis ID
XXXX is still present and visible by the vshadow command. As a result, snapped
volumes would accumulate on the intelligent disk device.
■ TITAN cases: 220-697-693
NB_6.5.6.winnt.x86
■ Description:
Fixed a status 13 error that occurred when an attempt was made to back up
Enterprise Vault Monitoring database on a remote SQL server.
■ TITAN cases: 220-649-766
NB_6.5.6.winnt.x64 NB_6.5.6.winnt.x86 NB_SAP_6.5.6
■ Description:
If all the following conditions are true, then multiple jobs appear in the Activity
Monitor, but only one backs up all of the files. The remaining jobs would fail:
■ Custom sorting is enabled while SAP backups occur.
■ The custom sort file is such that none of the file names that are included
in it match any of the files in the input file that the brbackup command
supplies.
■ The drives parameter is greater than one.

■ TITAN cases: 312-189-758
■ Description:
An off-host backup in a large environment that uses the legacy ShadowImage
snapshot method can fail because of a command-line limitation. That issue is
resolved.
■ TITAN cases: 320-209-732
■ Description:
A change was made to correct an nbemmcd -listmedia -allrecords
segmentation fault.
■ TITAN cases: 320-227-585

■ Description:
Catalog backup would fail with a status 1 error because the *.ior.mgr files
were selected for backup but were removed before the backup occurred.
■ Description:
The stserv script did not honor the maximum fetch limit. The result of this
issue caused a memory exhaustion and a system crash. A change was made to
correct this issue.
■ TITAN cases: 281-737-803
NB_6.5.6.winnt.x64 NB_6.5.6.winnt.x86 NB_ORA_6.5.6
■ Description:
Oracle backups would fail with an unhandled exception message.

■ Description:
The NetBackup Domain Network Analyzer (nbdna) utility analyzes the
NetBackup domain and its configuration for network issues, performance, and
behavior. It addresses hostname lookup and connectivity between NetBackup
hosts and their role within the NetBackup domain.
■ Description:
NetBackup Job Manager (NBJM) could deadlock if it was shut down while it
initialized with the NetBackup Resource Broker (NBRB) on a startup.

■ Description:
A change was made to the Tape error recovery to support SUSE 11.
■ TITAN cases: 281-858-481
■ Description:
Standard UNIX file metadata (such as, permissions, owner, group) would not
get restored on a Mac OS X 10.5 platform when ou attempted to restore across
hardware platforms (PowerPC to and from x86). An incompatibility between
platforms for the HFS attributes caused this issue.
That release contains a new touch file
(/usr/openv/netbackup/IGNORE_HFS_ATTR) that disables the restore of HFS
attributes and enables the restore of the standard UNIX metadata.
■ Description:
A change was made to ensure that an SRT is able to be created for Red Hat
Enterprise Linux 4 (RHEL4) Update 8 and RHEL5 Updates 3 and 4.
In the RHEL 5 U4, the released iso .discinfo file contained the string, Red
Hat Enterprise Linux 5.4 and the createsrt.conf file contained an RHEL-5
entry with string, Red Hat Enterprise Linux 5. That caused the load media
to fail with the error, The loaded media is not correct.
That same issue affected RHEL4U8 as well.
■ Work around:
If you encounter that issue, modify the createsrt.conf file on the boot server
to add ".4" (or .3 for 5.3) in the string. For example, the following string shows
RHEL 5 was changed from a "5" to "5.4".
Red Hat Enterprise Linux Server 5.4
That should be done in the [media] sections for RHEL5. That change enables
the creation of RHEL5.4 SRTs. However, this change disables the creation of
RHEL5.0/5.1/5.2 SRTs.
■ TITAN cases: 410-834-770

■ Description:
A fix was added to make sure that the report schedules do not disappear from
the NOM console.
■ TITAN cases: 312-182-724
NB_6.5.6.winnt.x86
■ Description:
A FlashBackup of a Hyper-V guest virtual machine (VM) failed if the guest VM
was specified with a volume GUID instead of a drive letter.
■ Work around:
If you encounter that issue, replace the volume GUIDs with the associated
drive letters.
Etrack Incident: 1862242 1997002 1862252 1843171
■ TITAN cases: 411086109
■ Contained in: NBLU_6.5.6.UNIX NB_ORA_6.5.6
■ Description:
A change was made to add support to NetBackup for Oracle 11gr2.
On some platforms, if you use the NetBackup for Oracle XML export wizard
to archive Oracle, the process may fail on an 11gR2 database with the following
types of error messages:
■ ERR - Cannot find Oracle client library.
■ ERR - Tried to open: /db/oracle/orac112/lib/libclntsh.so
■ ERR - Verify that the correct 32-bit or 64-bit library exists and matches:
■ ERR - bporaexp
■ ERR - dlerror(): /db/oracle/orac112/lib/libclntsh.so: wrong ELF
class:ELFCLASS64
To work around this issue, move bporaexp to a new location and create a
symbolic link from bporaexpto bporaexp64. See the following commands:
cd /usr/openv/netbackup/bin mv bporaexp bporaexp.orig ln -s bporaexp64 bp
That issue is resolved in the NetBackup 7.0 release.

Please note that for 32-bit Linux x86 platforms, the oracle_link script may not
properly create the necessary symbolic link to the NetBackup libobk library.
To work around this issue, go the Oracle home directory and perform the
following commands:
cd lib
ln -s /usr/openv/netbackup/bin/libobk.so libobk.so

■ TITAN cases: 312-196-927
■ Description:
SAN client error conditions can cause pipes to go into an orphaned state. The
nbrbutil command changes enable a user to see all the pipes that are orphaned.
■ Work around:
If you encounter this type of issue, use the SQL script to view and reset
orphaned pipes.
NB_6.5.6.winnt.x86
■ Description:
A change was made to address a timing issue with bpbkar32 on Windows to
ensure that a crash does not occur at the end of hot catalog backups.
■ TITAN cases: 410-604-465
■ Description:
A change was made to ensure that the correct media server is selected for SLP
duplication. That fix addresses an issue where the wrong media server was
selected for SLP duplication and produced the following error.
media write error(84):Duplication error with PDDO

NB_6.5.6.winnt.x86
■ Description:
A change was made to ensure that you can uninstall NetBackup 6.5.6 while
the oracle.exe executable runs.
■ TITAN cases: 281-708-675 411-752-618
NB_6.5.6.winnt.x86
■ Description:
In the Backup, Archive, and Restore user interface, the Search Backups feature
would fail to quickly locate the files to restore. That occurred primarily for
the large images that contained many files. In addition, the following message
appeared.
WARNING: unable to obtain list of files using specified search

■ TITAN cases: 320-175-882
NB_6.5.6.winnt.x86
■ Description:
A change was added to ensure that Type 2 VCB Backups no longer fail on one
Citrix VM.
■ TITAN cases: 312-232-956

NB_6.5.6.winnt.x64 NB_6.5.6.winnt.x86 NB_BMR_6.5.6
■ Description:
If the install path of any NetBackup client starts with a lower case drive letter
then the BMR Prepare Restore operation of client's configuration failed. The
following message would appear:
PTR fails with error that NBU volume is not included in the
restored volumes

■ TITAN cases: 281-619-629
■ Description:
Large SAP Restores incorrectly reported failures in brrestore log, even though
all files were restored correctly.
■ TITAN cases: 220-706-020 411-182-607
■ Description:
A change was made to move Fibre Transport to BSI_sdk 1.0.4b.
■ TITAN cases: 312-054-546
■ Description:
If you restored a 20GB file that had been backed up with FlashBackup, the
restored file would have an incorrect size. A change has been added to correct
that.
NB_6.5.6.winnt.x86
■ Description:
That release contains an updated version of the embedded NIC driver for the
Broadcom NetXtreme II card from v4.4.0.0 to v5.0.0.0.
■ TITAN cases: 320-231-181
■ Description:
The bpdbjobs -quick_print command would truncate the jobid field to the
first five digits.
■ TITAN cases: 281-592-697 410-597-949 410-739-045
■ Contained in: NBLU_6.5.6.UNIX NB_SNC_6.5.6
■ Description:
Is some cases, a FlashBackup, single-file restore would fail with the following
error:
bprd.sfr: transadr: assertion failed (at sfr.c.1563)
■ Work around:
If you encounter this issue, restore from a full backup and use a raw partition
restore.
■ TITAN cases: 410-630-281
■ Description:
A lack of an index on the EMM_AllocationStatus table caused delays in resource
allocation.
■ Work around:
If you encounter this issue, prune the nbemm allocationStatus table with
the nbemm -errorsdb.

■ TITAN cases: 312-189-425
NB_6.5.6.winnt.x86
■ Description:
Mapped FullVM backups on the weekend can cause a user to run out of nonpage
pool memory.
A change was made to the logging code segment to not enable logging when
an error is encountered. The code segment is disabled for Windows, and
remains the same for UNIX.
■ TITAN cases: 240-891-166 410-997-313
■ Description:
A change was made to address a memory leak in nbemm:DAThreads.cpp.

■ TITAN cases: 281-836-378
■ Description:
A problem was identified for Oracle backups on Linux 2.4 kernels. During a
backup, the Oracle process failed even after all the files were backed up. The
job status confirmed that the job had failed.
■ Description:
That release contains an update to latest device mappings file,
external_type.txt version 1.86.

■ TITAN cases: 240-994-016

NB_6.5.6.winnt.x86
■ Description:
Windows-based servers would fail the restore of KMS encrypted images if
more than one image was required.
NB_6.5.6.winnt.x86
■ Description:
When a refresh or refresh all is selected on the Drives tab of the Activity
Monitor, the drives were shown as AVR control for a time. However, the correct
name is shown under Control column after sometime.
■ TITAN cases: 320-231-968
■ Description:
The bpcatlist command would crash on HP-UX IA64 platform when you
attempted to retrieve images from a catalog archive.
■ Work around:
If you encounter that issue, browse the contents of an archive backup manually
and restore them with the bprestore.
■ TITAN cases: 230-689-911 281-415-262
NB_6.5.6.winnt.x86
■ Description:
The Drive count was zero for the Application Cluster storage units.
Etrack Incident: 1849943 1915646 1915644
■ TITAN cases: 240-954-249

NB_6.5.6.winnt.x86
■ Description:
Changed the default behavior to back up all transaction logs for an Exchange
snapshot backup to TRUE.
That change was made after findings from Microsoft that replication replay
may require all logs after a restore.
NB_6.5.6.winnt.x64 NB_6.5.6.winnt.x86 NB_VLT_6.5.6
■ Description:
Vault_Operator-initiated ejects would fail.
Under NBAC mode, the vlteject command failed because of some session
directory permission issues. Even if you configured the following file with the
appropriate umask, Vault would fail to read the value from the touch file.
/usr/openv/netbackup/bin/"VLT_USE_UMASK_FROM_TOUCH_FILE
■ Work around:
If you encounter this issue, manually change the session directory files to
enable the Vault_Operator to perform ejects and reports.
NB_6.5.6.winnt.x86
■ Description:
An issue was fixed that caused core files to be created when a backup was run
with open file backups enabled on IA64 platforms.
NB_6.5.6.winnt.x86
■ Description:
During a Windows open file backup, if the shadow storage was found as
unbounded then NetBackup changed it to a value between 300-1024MB. That
value was not sufficient to hold multiple snapshots on a Windows Server 2008
platform. That caused the snapshots to be silently deleted . The fix does not
change the shadow storage.

■ TITAN cases: 281-875-323
■ Description:
A change was made to the ntstlutil diskful command line option to handle
64-bit capacity values as input on AIX systems. That command is an
undocumented command.

■ TITAN cases: 281-893-652
■ Description:
A change was made to ensure that BPRD can remove the old logs that are larger
than 2GB.
NB_6.5.6.winnt.x64 NB_6.5.6.winnt.x86 NB_DMP_6.5.6
■ Description:
A change was made to correct an issue that caused OST DirectCopy to tape to
fail for TIR images.

■ TITAN cases: 411-265-740
NB_6.5.6.winnt.x86
■ Description:
A full OS recovery of a Windows 2008 or 2008R2 server would result in
non-bootable system.
■ Work around:
To avoid that issue, do the following when you want to restore the system
drive of a Windows 2008 or 2008R2 server. Remove the check from the box
for the Boot folder on the system drive (for example, C:\Boot).
Etrack Incident: 1987788 1851360

■ Description:
That release of NetBackup contains SAN Client-related fixes.
■ TITAN cases: 240-758-574
NB_6.5.6.winnt.x86
■ Description:
Fixed a FlashBackup SFR-restore issue that caused a status 5/85 error even
though all of the files appeared to be restored.
■ TITAN cases: 220-366-950
■ Description:
Backups to a NearStore storage unit would fail with the following status 84
error message.
Cannot write image to disk, Invalid argument.

■ Description:
The EMC_Timefinder_* operation did not work on HP-UX 11.31 systems if the
Storage Foundation stack was present for data.
■ TITAN cases: 220-705-174
■ Description:
A change was made to ensure that only one job is associated with a single job
ID.
■ TITAN cases: 320-220-208
■ Description:
When disk backups are run on a MEDIA_SERVER, bptm encounters non-fatal
errors (errors that are ignored) while it gets Data Classification information
from bpdbm. Due to these errors, the images that are created are not tagged
with Data Classification information. That may have some undesired effects
for later processing of the image as per storage lifecycle Policy or Data
Classification.
The fix gets rid of the error. It changes the bpdbm authorization table to allow
MEDIA_SERVER to query for the Data Classification information.
■ TITAN cases: 281-680-774
■ Description:
A change was made to address intermittent status 83 errors with KMS and HP
LTO4.
■ TITAN cases: 320-191-828 320-211-360
■ Description:
A change was made to correct an issue that caused vltadm to core dump when
you attempt to edit the policy list on a new profile.
■ Description:
NBPEM terminated when an NDMP or SnapVault policy referenced a

non-existent storage unit. For instance, if the storage unit was deleted after
the policy was created.
■ Work around:
If you encounter this issue, deactivate the policy, use a different storage unit,
or re-create the original storage unit.
■ Description:
That release contains added support of new ACSLS 8.0 media types that include
LTO5.
■ TITAN cases: 312-189-247
NB_6.5.6.winnt.x86
■ Description:
The timeout value in the boot loader section of boot.ini was always default
set to 5. A BMR Restore of a Windows client would not set to its original value
after a successful BMR restore.
■ TITAN cases: 320-217-552
NB_6.5.6.winnt.x86
■ Description:
Following an Exchange GRT backup, the event log DLLs were invalid for the
ese process. Because of this issue the user cannot read the event log entries
with the full verbiage for ese.
■ Description:
A change was made to properly update the DSSU potential free space.

■ Description:
A change was made to correct the implementation of the query
QueryHostsByRobotNumAndDriveType().

■ TITAN cases: 320-166-089
■ Description:
Fragments for staged backups (non-SLP) were left in the EMM database when
images were expired after reaching the expiry date. As a result bpexpdate
-deassignempty failed with a database system error 220.
That occurred after the bpduplicate script was run to make duplicate copies.
However, a disk staging storage unit made the original backup and the disk
copy had already expired.
Etrack Incident: 1947258 1941515 1930371 1953348 1948963 1957971 1891943
■ TITAN cases: 220-701-553
NB_6.5.6.winnt.x86
■ Description:
The release contains the additional restore capabilities that are available in
NetBackup 7.0 for SharePoint Granular restores. That enhancement enables
users to restore SharePoint lists, sites, subsites, web parts, and their
corresponding metadata.
■ TITAN cases: 410-596-478 410-659-783
■ Description:
A change was made to bpdbjob to resolve a core dump issue with the -fast
option.

■ TITAN cases: 281-889-342
■ Description:
If the system gets one of the following errors, then during the Oracle backup
or restore operation the log function attempted to log the error message and
the process crashed because of a log function argument mismatch.
■ Socket read-write error
■ System event creation failure
■ Files read operation fail

■ TITAN cases: 241-008-818
■ **Description:
Media would get deassigned incorrectly due to an incorrect num of images
count in EMM database.
NB_6.5.6.winnt.x86
■ Description:
An Exchange Off-host backup would sometimes fail with a message that
ESEUtil is missing. That would not occur when the Exchange Management
Tools were installed on the alternate client. Without them, the problem would
occur occasionally.
■ Description:
A change was made to correct an issue that caused an occasional core dump
to occur with nbstrserv.
■ TITAN cases: 410-638-028
■ Description:
A Legacy TimeFinder backup failed when PowerPath was installed with Storage
Foundation.
■ TITAN cases: 240-910-389 281-737-126 410-599-152
NB_6.5.6.winnt.x86
■ Description:
The topology view on a Windows x64 master server did not show drives after
multiple SSO media servers with larger number of drives were added.
■ Description:
An attempt to create a Red Hat 5.4 Shared Resource Tree (SRT) on a Red Hat
5.4 Boot server failed. The following error appeared the Red Hat 5.4 dvd.iso
image was provided.
That is not a valid mountable path name - please try again
■ Work around:
If you encounter this issue, copy and mount the Red Hat 5.4 dvd.iso image
locally on a computer and then provide that path.
■ TITAN cases: 281-406-867
■ Description:
Disk imports of VMWare backups were imported as VMWare Type 0, regardless

of the type that they were backed up as.
■ Work around:
Modify the image header file after the import to reflect the correct type and
to ensure that the correct type of restore is done.
■ TITAN cases: 281-536-554
■ Description:
The synthetic backup failed with a status 609 when bpsynth used incorrect
media server, disk storage unit resources to read the component backup.
In cases where there are basic disk or NearStore storage units with identical
paths on different media servers, a NetBackup synthetic backup fail. The failure
status was a status 609. That would most likely happen when some
incrementals for the schedule are on each storage unit.
■ Work around:
To work around this issue, give disk storage units unique pathnames. Or make
sure that a single synth policy does not use identical disk storage unit paths
on different media servers.
■ TITAN cases: 220-649-797
■ Description:
If bprd was inaccessible during certain parts of sbtinfo2 and sbtremove2
processes, the libxbsa and libobk libraries would fail. The failure caused a
crash of the associated Oracle process.
■ TITAN cases: 240-969-283
■ Description:
A change was made to address a memory leak in the FatDbObject query.
■ TITAN cases: 220-468-715 220-598-117 281-670-786 290-987-471 311-975-913
410-882-560 411-810-478
■ Description:
A change was made to ensure that NDMP backups of EMC Celerra filers only
succeed when they are suppose to. Backups would silently succeed when they
should not have.
■ Work around:
If you encounter that issue, turn on the SnapSure feature in the backup.
■ TITAN cases: 281-851-804
■ Description:
A change was made to add TLH NDMP Linux support.
■ TITAN cases: 241-000-151
■ Description:
Could not restore a folder and the subfolders after the Full and the Incremental
FBU backup images were selected in Backup, Archie, and Restore interface.
■ TITAN cases: 320-216-005
■ Description:
The NetBackup Enterprise Media Manager (nbemm) would hang in some
scenarios if a manual device configuration was performed under heavy loads.
That occurred because the order of the locks acquisition was not consistent.
■ Description:
The inventory timeout has been increased in this release for the robotic
libraries that have more than 300,000 media.
■ TITAN cases: 411-445-411
■ Description:
A change was made to correct a memory leak in
ServerGroupObject::createObect().

NB_6.5.6.winnt.x86
■ Description:
A BMR restore would fail with a verify backup error=23 when a client has
multiple NICs and multiple IP addresses assigned.

■ TITAN cases: 312-158-981 411-117-794
NB_6.5.6.winnt.x86
■ Description:
The mail message restore to Hebrew character set mailboxes failed on Windows
2003.
That fix enables an ASCII-based mailbox compare to occur so that restores
succeed with Hebrew character mailbox accounts. A registry key needs to be
created.

■ Description:
Large configuration data in the policy did not get transferred to SNC.
■ TITAN cases: 281-536-48 411-099-078
■ Description:
After an attempt to restore an Exchange 2007 SCC storage group, the restore
failed, and the following error message was sent to the progress log.
bpbrm handle_restore: handshake failure when starting tar on xxx

■ Description:
HP-UX 11.31 has introduced the /dev/disk device name space that is needed
to support the name space to perform a snapshot backup.
■ TITAN cases: 281-609-162
■ Description:
A change was made to ensure that after you run the nbemmcmd -deletehost
-machinename -machinetype ndmp command, you do not receive the following
error message.
Please Delete Disk Objects First

■ Description:
Only one backup ID is canceled at a time from same SLP. However, if a user
issued the command, nbstlutil inactive -force to cancel the SLP,
nbstserv.exe would core dump. A change was added to correct this issue.

■ TITAN cases: 281-807-002
NB_6.5.6.winnt.x86
■ Description:
An issue with bpfis caused an Application fault when an attempt was made
to back up the Enterprise Vault Directory Database.
■ TITAN cases: 410-752-123
■ Description:
A fix was added to ensure that cleared alert messages are not displayed under
the Active filter.
■ TITAN cases: 311-977-621
NB_6.5.6.winnt.x86
■ Description:
A change was made to enable the user to achieve the equivalent of bmrprep
-policy from the NetBackup Windows Administration Console.

■ TITAN cases: 281-753-917
■ Description:
An attempt to issue a bpgetconfig command to a VMS client caused the

following error:
local_getAllBEorNBHostInfo: translation for OpenVMS 6.2 could not be found

■ TITAN cases: 240-990-863 320-210-536
■ Description:
An NDMP DirectCopy would choose a non-NDMP drive path when it read the
source VTL media. That did not allow the VTL DirectCopy to occur.
■ Work around:
If you encounter this issue, use a single pathed VTL drive.
NB_6.5.6.winnt.x86
■ Description:
A change was made to address the length of time it took for the Snapshot
Client Option dialog box to come up.
■ TITAN cases: 220-704-015 240-972-898
■ Description:
That release adds support for storage images in IBM DS8000 arrays. It also
contains Support for scalable and big volume groups introduced in AIX 5.3.
Finally, this release contains the correct UDID generation for IBM DS8000
arrays.
■ TITAN cases: 220-696-315
■ Contained in: NBLU_6.5.6.UNIX NB_SMU_6.5.6
■ Description:
A failed cache left a file marked migrated or CACHED with no data online.
■ TITAN cases: 220-706-443
■ Description:
The nbemmcmd -deletealias command failed to delete the FQ hostname. The
change includes a better error message.
■ TITAN cases: 320-199-474
■ **Description:
Three-character 3pc.conf entries from Device # and affects if a vendor's device
returns more than FFF LUNS (4095). NetBackup would use SCSI inquiry VPD
page code 80 data, a unit serial number as a unique identifier to correlate the
disks to back up between the client, and the media server for Media Server
Copy backups. When the Symmetrix device ID number is greater than or equal
to 4k (4096), the serial number may not be unique anymore. In addition, when
the Symmetrix device ID number is greater than 8k, the serial number may
contain numeral ASCII characters, such as the pound sign (#). That can cause
a Media Server Copy backup failure since the portion of the serial number
after the pound sign (#) was interpreted as a comment of the entry in the
3pc.conf.
That fix uses the SCSI inquiry VPD page 83 data, device identifier which does
not have the issues described above. For this fix to work you must consistently
set the SPC-2 flag to disable or enable for the Symmetrix ports. These ports
are used on the client and the media server, because different SPC-2 settings
give a different page code 83 device identifier. Also, the fix is
backward-compatible to use the SCSI inquiry VPD page code 80 serial number
in case the client does not have disks that have a Symmetrix ID greater than
4095.
■ TITAN cases: 240-967-547

■ Description:
A change was made to address an issue that caused NBPEM to assert in the
Scheduler::getLBDNoRefCnt when a single-stream job was restarted with
multistreams enabled.
■ TITAN cases: 240-988-215 281-611-743
■ Description:
A backup with Hitachi_ShadowImage on an alternate host would fail with a
status 156 error with the following message.
pairvolstat error / "Host group name NOT matched
The fix was made on the following premise. If fqdn is not obtained (empty)
then only the host name comparison is done. In addition, a change was made
to fix an issue with the LDEV-to-LU conversion that was done for the secondary
device. That conversion was not required.
■ TITAN cases: 240-951-955
NB_6.5.6.winnt.x86
■ Description:
After a reboot, the NetBackup Key Management Service (KMS) did not restart
properly. Symantec Private Branch Exchange was added to this release as a
service dependency to KMS.
■ TITAN cases: 281-637-895
■ Description:
An NDMP restore would fail with an unimplemented error code 114. The
problem occurred only with a backup that had multiple paths, and one of the
paths spanned fragments. In addition, the restore involved more than one of
the backup paths and the spanned fragment was not the first to be used.
■ TITAN cases: 291-149-507
■ Description:
If bpbkar backs up the header file before the main file, then at restore time
the header file is restored. However, the operating system then removes it
when the main file is restored. That sequence of events caused an incomplete
restore.
■ Work around:
If you encounter this issue, run a second restore with the overwrite feature
disabled.
■ TITAN cases: 240-984-409
NB_6.5.6.winnt.x86
■ Description:
A restore of the DFSR Data would not maintain the file creation and
modification dates.
There is an issue with DFSR.exe, a Microsoft deliverable. After tar32.exe
restores a DFSR file, the DFSR.exe program opens the file for GENERIC_READ
which causes the file access time to be set to shortly after the restore. There
are no ways to prevent this from happening.
■ TITAN cases: 220-670-638
■ Description:
The exit-notify scripts were not working properly. The exit notify scripts
would only run after all streaming attempts completed. Before NetBackup
6.5.2, the scripts run after every stream.
A change was made that adds a new argument to the backup_exit_notify
command that indicates if a retry is performed. In addition, an argument was
added to the parent_end_notify command that indicates the number of streams
that were started.
■ Description:
Embedded files in a compressed folder on a virtual machine with
non-contiguous allocation did not map correctly.
■ Description:
The import of the Exchange database images would not properly browse for
granular operations.
■ TITAN cases: 281-537-793
■ Description:
A change was made to ensure that the nbstlutil utility does not receive a
CORBA exception with NBAC enabled.

■ TITAN cases: 320-180-691
■ Description:
A change was made to address an issue that caused bpbrm to core dump during
a VM VCB backup because bpfis core dumped.

■ Description:
The CDP FIM did not work with Storage Foundation version 5.0*. That was
due to a change in the output of some of the VxVM commands.
■ Description:
The vendor-unique, library handling of bar codes caused inject operations to
fail. That issue required the user to perform CLI operations to work around
the issue. A change was made to correct this issue.
■ TITAN cases: 220-704-762 320-220-187
NB_6.5.6.winnt.x86
■ Description:
When SQL a database has period in the name, the image name appears to use
a slash as a separator instead of a period. The following issues would occur:
■ You cannot select the database for restore in NetBackup MSSQL Client user
interface. In addition, you would receive the message, "Please enter an
integer between 1 and 31."
■ The dbbackup.exe generated a core dump if you selected a transaction
backup image to restore.
■ Work around:
If you encounter this issue, you can restore if you create a batch file manually
and run it.
■ TITAN cases: 410-645-359
■ Description:
A change was made to address an issue that caused an SLP duplication job to
fail with a status 50 error, however it continued to duplicate images.

NB_6.5.6.winnt.x86
■ Description:
Granular Active Directory/ADAM backups would sometimes give a 0 (success)
status but the granular portion of the backup would have failed. In addition,
the ability to do a granular browse and restore would not be available. That
was not a data loss issue since the full database is backed up but the granular
functionality was not available.
■ Description:
Upgrading and downgrading scripts for database were added to NetBackup
6.5.6.
■ TITAN cases: 312-075-563
NB_6.5.6.winnt.x86
■ Description:
The Allow Multiple Data Streams option on Windows would not work when
the include file contained multi-byte characters before a wildcard character .
■ **Description:
A change was made to address an issue with NDMP snapshot backups. The
backups completed successfully, however the image was deleted.

■ Description:
A change was made to ensure that you can access the FT media server
information in the user interface with Veritas Security Services enabled.
NB_6.5.6.winnt.x86
■ Description:
Snapshot-only restores failed with a private provider error on a rollback
attempt.
■ TITAN cases: 220-506-306
■ Description:
A change was added to correct a statistical problem with how the client's data
was transferred to media during multiplexed backups. An unfair number of
blocks were transferred from some clients.
■ TITAN cases: 230-708-237 281-493-054
■ Description:
Some drives returned a bad status that caused mounts to fail.
■ TITAN cases: 281-517-933
■ Description:
Image cleanup jobs would fail with a status 47 error after a media server that
contained basic disk storage units was decommissioned. That fix allows
nbdelete to honor a -force option and remove those images that remain for
a non-existent media server.
■ TITAN cases: 411-146-558 600-565-972
■ Description:
A change was made to address an issue that caused nbpem to slow down and
hang.
DNS delays to resolve short hostnames cause this issue. That indicates one of
the DNS servers did not function correctly. You should isolate and fix the
problematic DNS server.
■ TITAN cases: 281-644-467
■ Description:
A change was made to address an issue that caused the Lotus agent to complain
of a lack of free space even though free space was available on AIX platforms.
■ Work around:
If you encounter this issue, disable the log cache.
■ TITAN cases: 281-673-072 320-207-867
■ Description:
On certain Solaris 10 systems, the NB_update.install pack install script now
correctly installs the CLT release update.
■ TITAN cases: 320-217-862 411-407-917

■ Description:
FlashBackup Window restores would fail with the following message in the
bprd log.
bprd.sfr: flush_to_bptm: put_data returned -4 STATUS 175

■ TITAN cases: 411-412-701
■ Description:
On an upgrade to NetBackup 6.5.5, the Resource Broker (NBRB) would hang
at startup while the allocation database was validated. That caused the system
to be inoperable, particularly if there were a large number of outstanding
allocations when the system was shut down.
That also improves the performance of the nbrbutil -dump utility.
■ Work around:
If you encounter this issue, before you begin the upgrade, run nbrbutil
-resetAll against the previous version.

■ TITAN cases: 410-595-967
■ Description:
During duplication, the job failed when a subsequent resource was requested.
The Activity Monitor indicated something similar to the following.
status 96, bptm read; bpduplicate status 50; from mds

allocateMedia rc=2005000

■ TITAN cases: 220-690-845

■ Description:
Deleted files were not obsoleted correctly on Solaris.
■ Description:
A change was added to correct an issue with bpjobd that caused all processes
in its group or session to terminate on startup .
■ TITAN cases: 281-609-247
NB_6.5.6.winnt.x86
■ Description:
The Backup of SQL-Server mirror database failed with a status 2 error even
though it was not intended to back up any data.
■ TITAN cases: 320-178-387
NB_6.5.6.winnt.x86
■ Description:
bpcd would crash if there was an attempt to browse the Granular-enabled,
backup items that contained special characters.
■ TITAN cases: 291-181-599
■ Description:
Vault would not start after an upgrade from NetBackup 5.1 to 6.5.3.1 when
App_Clusters were in vault profiles.
- Make sure that no vault sessions(jobs) are in progress. - Shut down the
nbvault service. - Copy the original binaries for the backup. - Copy the given
binaries at the specified location. - Start the nbvault service.
■ Work around:
To work around this issue, perform the following steps:
- Get a list of all policies with bppllist -allpolicies -U. - Get a list of all
storage units with bpstulist -U. - Delete all Storage Units that are associated
with the Application Clusters. - Delete lines for app_clusters in vault.xml
file. - Start Vault by running nbvault. - Verify the nbvault-upgrade log to
make sure that it completes successfully. - Recreate all Storage Units that are
associated with the Application Clusters. - Update all policies that reference
the storage units that are associate with the Application Clusters and pick the
Storage Unit to update the pointers again.
NB_6.5.6.winnt.x86
■ Description:
Restores of the virtual machines that use Volume GUIDs for the path name
failed because the names were cataloged with the \\? string.
■ Description:
With an Oracle backup, all of the streams failed with an error 43 in bptm, error
13 in dbclient, error 63 in bpbkar, and bpfis would exit with a 0.
■ TITAN cases: 220-707-700
■ Description:
A BMR-based restore of an RHEL 5.x client failed when a RHEL5.4 shared
resource tree (SRT) was used. The restore failed while a message about missing
librt.so.1 was given.

NB_6.5.6.winnt.x86
■ Description:
The VSS snapshots that were taken to backup Enterprise Vault data were taken
with the auto provider option. That created a hardware snapshot if it was
allowed. Currently, that has been modified to always take snapshots with
system provider for Enterprise Vault backups.
■ Description:
The restore of an Exchange database that has [] or {} in the database name fails
when the Exchange granular restore feature is used to restore that database.
The restore finishes with a status 5.
The progress, log messages similar to the following may be seen:
16:41:00 (168.001) WRN - Aborting restore: Error writing to

object: (Microsoft Information Store:\Mailbox Database [1]\Database)

■ TITAN cases: 230-580-588
■ Description:
An Oracle job failed with a status 40 after exactly two hours even though bpbrm
had previously exited with a status 0.
■ TITAN cases: 281-745-939
NB_6.5.6.winnt.x86
■ Description:
DFS replication groups, on the same server, with same folder names were not
being backed up and resulted in a loss of data.
In the following example, the \home folder under DataStore2 was not backed
up because it shares the same name as the \home folder under DataStore1.
DataStore1\home DataStore2\home
■ Work around:
To avoid this issue, do not have two data stores with subdirectories names that
are the same.
■ Description:
The Drive Name Seed configuration did not work from the user interface or
the tpautoconf command line utility when NBAC was enabled.
■ TITAN cases: 281-827-145
■ Description:
An alternate client restore of a 1.2 Terabyte-encrypted SQL backup would fail
with the following SQL error:
SQL Server cannot process this media family

■ Description:
The mechanism to delete Hyper-V snapshots left bpfis to hang.
■ TITAN cases: 312-115-897
■ Contained in: NBLU_6.5.6.UNIX NBLU_6.5.6.WIN NB_NOM_6.5.6
NB_NOM_6.5.6.winnt.IA64 NB_NOM_6.5.6.winnt.x64 NB_NOM_6.5.6.winnt.x86
■ Description:
A change was made that enables you to see the user name and password for
the email server.
■ TITAN cases: 220-598-805
■ Description:
migcons errors were consolidated from an old method to a new method.

■ TITAN cases: 230-655-484 410-645-092 411-273-093
■ Description:
bpbackup failed with a socket read failed during a User Backup that a
PureDisk DR Backup initiated.
■ Work around:
If you encounter this issue, increase the number of streams that the PureDisk
DR backup uses so that it completes before the socket timeout occurs.
■ TITAN cases: 281-813-229
NB_6.5.6.winnt.x86
■ Description:
The NetBackup Administration Console for Windows did not show all of the
drive paths for a single host with multiple paths to a single drive.
■ Contained in: NBLU_6.5.6.UNIX NB_DB2_6.5.6
■ Description:
While you used the Backup, Archive, and Restore user interface (jbpSA), a DB2
version 9.7 instance did not enumerate.

■ TITAN cases: 320-222-100
■ Description:
Bptm and bpdm can hang when a user attempts to restore backups from which
TIR information had been pruned.
■ Work around:
If you encounter this issue, restart all services or stop the hung process, and
then rerun the restore.
■ TITAN cases: 240-748-094
■ Description:
Processes would fail with a status 225 (text exceeded allowed length) while
working with the backups that were created before NetBackup 6.5.4 and had
a keyword value that was exactly 128 characters long.
■ TITAN cases: 220-700-176 312-202-944 410-658-066
NB_6.5.6.winnt.x86
■ Description:
An attempt to restart a suspended job with VSS and VSP did not back up the
open files. A change was added to correct this issue.

■ TITAN cases: 220-690-210
■ Description:
Error message were misleading if a member from the NBU_User group tried
to run vault commands.
- Make sure that no vault jobs are in progress. - Shut down the nbvault service.
- Make a copy of original binaries. - Copy the given binaries at a specified
location. - Start the nbvault service.
■ TITAN cases: 220-694-437
■ Description:
On a status 96 error code the backup_exit_notify script does not run. The
BACKUP_EXIT_CALLED file does not get created.
On a status 96 error code the backup_exit_notify script does not run. The
BACKUP_EXIT_CALLED file does not get written at the end of the job with the
96 exit status.
These issues caused a failure on NetBackup 6.5.2, 6.5.3, 6.5.4, and 6.5.5.
■ Description:
Duplication jobs that were submitted by SLP's would not always have the
correct policy name. In addition, the Duplication jobs that were submitted by
SLP's would not respect the MAX_KB_SIZE_PER_DUPLICATON_JOB limit within
bpduplicate.

■ Description:
In case of a manual catalog backup, if the second child job was Canceled, the
parent job remains in an active state forever.
■ TITAN cases: 312-194-510

NB_6.5.6.winnt.x86
■ Description:
A change was made to ensure that shadow copy backups do not fail on IA64
platforms.
■ Description:
The EMC_Timefinder_* FIM was not supported with Solution Enabler, version
7.0 or higher. As EMC plans to EOL older versions of Solution Enabler,
NetBackup should support newer version. A change was made to ensure that
NetBackup supports Solutions Enabler 7.0 for snapshots.
■ Description:
That release of NetBackup contains an updated version of the nbsu utility. The
version number is version 1.3.
The nbsu 1.3 utility is now available for the Mac OS X platform.
NB_6.5.6.winnt.x86
■ Description:
A change was made to ensure that NetBackup does not change the VSS
association settings.

■ Description:
Jobs could be left in the waiting for Retry state forever if NBJM was shut down
while NBPEM tried to expire the jobid. That caused the state to change to
Done.

■ TITAN cases: 240-897-124
■ Description:
The bpcd -standalone command would core dump and create defunctional
processes.
■ TITAN cases: 220-700-032
■ Description:
A change was made to address an issue that caused the bpnbat -logout
command to report the following:
Optional VxSS libraries not initialized

■ TITAN cases: 281-776-123
■ Description:
After a restart, nbpem did not read the DSSU schedules and none of them ran.
■ Work around:
If you encounter this issue, recreate the relocation schedules by the user
interface.
■ TITAN cases: 230-708-303
■ Description:
The xbsa.dll library would free the allocated memory for the compression
buffers twice if the backup job failed with status 96.
■ Work around:
If you encounter this issue, disable the client compress attribute.
■ Description:
A change was made to address a status 41, Network connection failed error
that occurred with VSS backups against large Information Stores .
■ Work around:
If you encounter this type of issue, increase the client read timeout to a value
large enough to accommodate the time that it takes for the snapshot creation.
That time is dependent on the customer's Exchange environment.
■ TITAN cases: 281-691-277
■ Description:
A change was made to ensure that the Java GUI can handle policies that were
created on 5.x with ITC when you modify the schedule.
■ TITAN cases: 320-228-566
■ Description:
A change was made to address an issue that caused encrypted backups to fail
with the following error message.
Operation would block

■ Description:
If a deactivated SLP has too many images (for example, more than 10,000) it
could prevent scheduling any duplications. A change has been made to correct
this issue.
■ Description:
Restore jobs for UNIX and Linux clients have the following warning message
in the Detailed Status for the job in the Activity Monitor.
read: unrecognized -J string spsrestoreoptions=0
That warning message also appears in the Problems report after a restore is
run to a UNIX and Linux client.
■ Work around:
If you encounter that issue, ignore the message, no other action is necessary.
NB_6.5.6.winnt.x86
■ Description:
A VMWare backup can finish with a partial success. That occurs because of
an error in how embedded files are mapped in a compressed volume or folder
and if the allocation is split into two extents.
■ TITAN cases: 281-782-311
NB_6.5.6.winnt.x86
■ Description:
After a BMR Restore of a client system, the system's clock was set ahead or
behind by a few hours. The exact amount of time by which the clock was offset,
depended upon the Timezone of the client system. It also depended on whether
the client's Timezone had a DST variant.
■ TITAN cases: 410-650-640

■ Description:
A change was made to ensure that you can restore from the fragments that
are greater than 1 TB.
■ TITAN cases: 320-218-496 411-340-481
NB_6.5.6.winnt.x86
■ Description:
While saving a Transaction log/Differential-based, MOVE batch file, the prompt
did not offer to open the file in Notepad. In addition, the Restore selected
object or Verify backup image but do not restore option for the Transaction
log/Differential-based batch file did not show restores were set on the prompt
that offers to open the file in Notepad.
■ TITAN cases: 240-913-438
■ Description:
A change was made to ensure that users can restart child jobs when Windows
Open File Backup (WOFB) is in use.
■ TITAN cases: 312-167-592
■ Description:
A comparison of the kilobytes value of the job database was performed. The
result showed that the kilobytes value of a remote NDMP backup job was 1
kilobyte less than the value of the local NDMP backup job.
■ TITAN cases: 320-179-482

■ Description:
BMR boot server allows the creation of an ISO from a network boot shared
resource tree (SRT). In case of BMR ISOs for Linux, if the ISO is used by the
virtual device interface that the servers or remote console appliances provide,
the SRT is not recognized as a valid SRT in the BMR Restore environment.
Usually, an error message similar to the following appears in the restore
environment:
SRT: ERROR: No devices listed in /proc/sys/dev/cdrom/info
■ Work around:
The traditional Media Boot mechanism still works. For example, burn the ISO
on a CD-ROM and boot the system.
■ Description:
A change was made to ensure that Vault does not sort the tape images by size.
The change makes sure that it sorts the tape images by time while it creates
the Batches for Duplication.
■ Description:
A change was made to ensure that the duplication of NDMP images from Disk
to Tape no longer fails.
■ Work around:
If you were to encounter an issue like this, set the SIZE_DATA_BUFFERS_NDMP
parameter to the size required (for example, 65536).
■ Description:
A fix was added to ensure that all multiple encryption descriptors, that some
encryption-capable drives produce, are handled correctly.

■ Description:
The Job details of a restore operation showed errors and was seen as incomplete
in the Activity Monitor as the progress log information was not sent due to a
large buffer.
■ TITAN cases: 312-158-282
■ Description:
The Java GUI file browser would hang when the number of links in fls -l
output was greater than 99.
NB_6.5.6.winnt.x86
■ **Description:
VMWare Consolidated Backup (VCB) type 0 backups returned a status code 0
even though there was no data to restore.
■ Work around:
To avoid this issue, do not perform drive exclusions of affected Windows
clients.
■ TITAN cases: 312-208-996
■ Description:
A change was made to increase the LSM count to 126.
■ TITAN cases: 312-158-282
■ Contained in: NBLU_6.5.6.UNIX NBLU_6.5.6.WIN NB_JAV_6.5.6

NB_SMJ_6.5.6.winnt.IA64 NB_SMJ_6.5.6.winnt.x64 NB_SMJ_6.5.6.winnt.x86
■ Description:
The Java GUI file browser would hang if you browsed a directory that contains
a file that is larger than 2GB.

■ Description:
That release of NetBackup contains an updated version of NBCC and NBCCR.
The version number is version 7.0.
■ TITAN cases: 281-881-993
■ Description:
A change was made to ensure that Vault does not recall media from the volume
groups that are not associated with Vault, namely the "---" volume group.
■ TITAN cases: 281-808-888
■ Description:
The bpadm command user interface in NetBackup 6.5.3 and 6.5.4 did not let
you change the policy default volume pool directly and can cause policy
corruption.
■ TITAN cases: 320-161-355
■ Description:
A change was made to client-side encryption for the following:
AIX: bpkeyutil.c.473: main: Function call GetDecryptedKeyFile

failed. Errno = 0

■ Description:
A change was made to ensure that the ndmpagent does not core dump if an
error occurs at startup, or before shared memory has been initialized.

■ TITAN cases: 230-689-574
■ Description:
The vmscd daemon was started on the EMM server if and only if there were
one or more pre-NetBackup 6.0 media servers in the NetBackup domain. In
some case, vmscd was being started on a pure NetBackup 6.x environment.
■ Description:
A change was made to ensure that more than 45 snapshot resources can be
accepted in the policy. A change was made to the bpplifo command to address
this issue.
■ Description:
A change was made to correct an issue that caused PEM to crash when heap
checking is ON. The same problem also caused a crash during normal
operations.
■ TITAN cases: 312-208-522

■ Description:
That release of NetBackup contains multiple GRT-related changes.
■ TITAN cases: 411-146-558 600-565-972
■ Description:
A change was made to address an issue that caused nbpem to hang when the
network host-name look-ups were slow.
■ TITAN cases: 240-917-933
NB_JAV_6.5.6.winnt.IA64 NB_JAV_6.5.6.winnt.x64 NB_JAV_6.5.6.winnt.x86
■ Description:
The NetBackup Java user interface did not show a PDDO disk group on the
Devices Monitor.
The check for NB_FEATURE_PURE_DISK was not present in NetBackup 6.5.3, and
caused this issue. The fix in this release provides the NB_FEATURE_PURE_DISK
and NB_FEATURE_STS_ENABLED checks on.
■ TITAN cases: 291-082-134
■ Description:
TIR_INFO files for Solaris 10 non-global zone's LOFS file systems were not
renamed.
■ TITAN cases: 312-132-747

■ Description:
The offline timeout does not clear all of the locks and causes a failover when
offline times out.
■ Description:
Backup of an invalid path caused a backup failure for NDMP 3-way. The job
should report a status 1 (partial success) error, however, it fails.
■ Work around:
Remove the invalid path from the policy.
■ Description:
Optimized duplication jobs were not counted against the I/O stream count
limit.
The read side of the opt dup duplication jobs was not counted against the I/O
stream limits, and did not queue if the limit had been reached for a volume or
caused other jobs to queue.
■ TITAN cases: 281-749-891
NB_6.5.6.winnt.x86
■ Description:
No file-level information was available on the D drive after the mapped FullVM
backup completed with a Status 0.
■ TITAN cases: 281-635-957
■ Description:
Vault eject and Vault reports were incorrect when only the Vault profile name
was supplied.
■ Description:
A change was added to address an issue that caused NBPEM to crash on a disk
full condition while new jobs were run.
■ TITAN cases: 312-174-077
■ Description:
The BasicDisk plugin gets an incorrect value for TotalCapacity and free space
in AIX for large file systems.
When a basic disk storage unit with more than 128TB capacity is used, its
TotalCapacity and free space get an incorrect value.
■ TITAN cases: 220-586-187 291-186-078
■ Description:
A Vault internal error 286 occurred while Vault tried to merge batches with
common media at the duplication step. A violation of a precondition on the
batches attribute caused the error.
Vault would fail to merge tape batches with varying retention levels under the
following circumstances:
- Common media were found between batches -
ALLOW_MULTIPLE_RETENTIONS_PER_MEDIA = YES
■ TITAN cases: 411-184-061

■ Description:
A fix has been made to ensure that you can export the Job Summary by Status
report data to CSV.
■ TITAN cases: 281-715-561 320-202-873 410-990-189
■ Description:
Allows multiple simultaneous snapshots for VMWare backups, if the
noSnaplock registry entry is present.
The touch file, MaxVMWareJobs, in the root NetBackup directory controls the
number of jobs that are submitted to the proxy. That file should contain a
value of 60 divided by the maximum number of volumes in a single virtual
machine. For example, if you have a computer with three drives the file value
is 20.
■ TITAN cases: 220-689-207
NB_6.5.6.winnt.x86
■ Description:
Backup of the Windows 2008 AD server failed with a Status 71 using the backup
network.
■ Work around:
To avoid this issue, use the client name and interface that matches the
computer name of the AD server.
■ TITAN cases: 281-814-626
■ Description:
A change was made to correct an issue that caused Vault to fail with a status
13 error if it encountered a corrupted image header.
NB_6.5.6.winnt.x86
■ Description:
The bpbkar32 process crashed when throttling parameters were used for the
backup.
■ Description:
During the abort process of the active session (nbstutil -force) nbstserv
can continue to fetch images for processing. That issue can delay the actual
completion of the request.
■ TITAN cases: 220-686-180
NB_6.5.6.winnt.x86
■ Description:
A client-to-media server communication problem happened intermittently
and caused a job to run forever as opposed to a failed job. bpbkar did not take
into account that it may not receive all four bytes on the read, which caused
the problem.
■ TITAN cases: 312-139-798 320-222-394
■ Description:
A change was made to correct and issue that caused the bprd log to fill up with
msgbackup messages.


NB_6.5.6.winnt.x86
■ Description:
That Release Update contains updated Sybase ASA binaries with latest
engineering binary fixes (EBF).
■ TITAN cases: 320-174-755
■ Description:
Duplications appeared to hang because of the delays that a large catalog cleanup
process casued.
■ TITAN cases: 230-647-273 411-146-558 600-565-972
■ Description:
PemCORBACall::invokeCall would hang and resulted in no more calls to the
NBProxy queue to be processed. In addition, nbpem would no longer schedule
jobs and consumed the CPU.
■ Work around:
To work around this issue, remove the include days from all calendar schedules
that occurred in the past from all policies.
■ Description:
A change was added to ensure that stream discovery is working properly.
■ Description:
While writing backup images to BasicDisk and AdvancedDisk, synchronous

flushing of image data was not forced during an image close. That left a small
window of time where the data was not completely flushed (or sent) to the
disk. NetBackup however believes that all of the data was successfully flushed
(sent) in its entirety.
■ TITAN cases: 281-610-230 410-739-631
■ Description:
The dbclient process presented a bpfis -create request to bprd, but due to
the number of devices to scan it takes more than 60 minutes to complete.
During that span, the firewall drops the idle socket between the processes.
Both bpfis and bprd exit with a status 0 even though the network returned
an RST when bprd wrote the exit status. The dbclient process then hangs
endlessly on the socket read as an alarm appears not to be set for
CLIENT_READ_TIMEOUT.

■ TITAN cases: 281-813-207
■ Description:
A change was made to address an issue that caused SLP duplication to hang
in a queued state.
■ Description:
A change was added to correct and issue that caused the NBJM to grow to more
than 4Gb in size and then core dump.

■ Description:
Copy-back restores failed from NAS_Snapshot because mount_frag() returned
an incorrect mount point.
■ Work around:
To work around this issue, mount primary volumes with NFSv3.
■ Description:
SAN Client backups of non-Windows clients that used polices with client
encryption options enabled were backed up without encryption in NetBackup
6.5GA through 6.5.5. That could have resulted in a data security issue if the
physical backup media custody were lost.
Restores of LAN-encrypted backups that use SAN Client on non-Windows
clients in NetBackup 6.5GA through 6.5.5 would restore the encrypted data
without decrypting it. That could cause a severe data loss , and corrupted the
running OS if the restored files were critical OS files.
That problem does not exist for SAN Client on the Windows operating systems.
That fix causes backup and restore jobs that use SAN Client on non-Windows
clients that involve client encryption options in the policy to generate a status
16 unimplemented error. That prevents the data security or data loss
possibilities.
After you install this patch, any previously generated SAN Client backup sets
from client-side encryption policies are NOT restorable without removing this
patch.
Attempts to restore these non-encrypted SAN Client backups from client
encryption option policies using LAN fail without restoring any data.
■ TITAN cases: 281-879-985 320-187-988
NB_6.5.6.winnt.x86
■ Description:
A change was made to ensure that the SNAP_LOCK_TIMEOUT registry is not
ignored.

■ Description:
Point-in-Time (PIT) restores would fail on Solaris when
EMC_timefinder_Mirror is used and if multiple VxVM disk groups are involved
in the restore.
■ TITAN cases: 281-745-720
■ Description:
A problem existed in Vault and how it determined which tapes to eject based
on the physical status and location of the tapes. Vault makes this determination
before the ejection of the tape.
■ During the configured time for an eject, some tapes are either HOME,
IN_DRIVE and IN_TRANSIT
■ For the tapes that are in the HOME state, there is no problem, and they
are considered for ejection.
■ For the tapes that are in the IN_DRIVE state, there is no problem, and they
are not considered for ejection.
■ For the tapes that are in the IN_TRANSIT state there was a problem because
Vault considered those tapes for ejection, when they should not have been
considered.
The physical result of the vault eject for the above scenario is as follows:
■ No tapes made it into the CAP.
■ The user had to perform the ejection manually from the ACS robot.
The logical result of the vault eject for the above scenario is as follows:
■ The tapes that are in the IN_TRANSIT state could not be physically
ejected. The result was a status 224 (Control daemon connect or
protocol error) error.
■ Vault thinks the eject operation occurred and exited with final status
288 (partially successful eject) error.
■ The Robot Pick List shows all tapes are EJECTED (except for the tapes
that in the IN_DRIVE state). That is not correct. The Robot Pick List
should show no tapes ejected, and that no tapes made it in into the CAP
(physically).

■ Description:
A change was made to upgrade JRE1.6 for NetBackup 6.5.6 supported platforms.
All platforms with the exception of Tru64 are now at version 1.6. That was
done for two reasons: - To address and alleviate customer security concerns.
- To get the latest fixes for known security vulnerabilities from the vendor.
Platform NetBackup 6.5.6 JRE version
AIX_JRE 1.6.0 SR 6
HPUX_JRE 1.6.0.05
HPUX_IA64_JRE 1.6.0.05
Linux_JRE 1.6.0_17
Linux_IA64_JRE 1.6.0_17
Solaris_SPARC_JRE 1.6.0_17
Solaris_x86_JRE 1.6.0_17
Windows_JRE 1.6.0_17
Windows_x64_JRE 1.6.0_17
Windows_IA64_JRE 1.6.0_17
Tru64 1.4.2-9

NB_6.5.6.winnt.x86
■ Description:
A change was made to address an issue with bpbkar32 that would cause a crash
and produce a message on exceptions if a FlashBackup was run and the socket
disconnected.

NB_6.5.6.winnt.x64 NB_6.5.6.winnt.x86 NB_DRO_6.5.6
■ Description:
A change was made to address a core dump issue that occurred during a
NetBackup catalog backup or a Database (Oracle, DB2, SQL, or SAP) Snapshot
Client backup.
■ Description:
A change was made to address an issue that caused the Java GUI to not handle
the Scratch pool attribute for a volume pool properly.
■ TITAN cases: 320-198-552
NB_6.5.6.winnt.x86
■ Description:
All Windows 2000 and Windows XP clients complete with a Status 1 because
it is failing to backup event logs .
When performing a ALL_LOCAL_DRIVES backup of a Windows 2000 system,
the event logs cannot be found. A message similar to the following can appear
in the log file:
5/27/2009 7:53:17 PM - Warning bpbrm(pid=2756) from client

vmw2ktest: WRN - can't open file: C:\WINNT\system32\config\AppEvent.Evt
(WIN32 3: The system cannot find the path specified.) 5/27/2009 7:53:18
PM - Warning bpbrm(pid=2756) from client vmw2ktest: WRN - can't open
file: C:\WINNT\system32\config\SecEvent.Evt (WIN32 3: The system cannot
find the path specified.) 5/27/2009 7:53:18 PM - Warning bpbrm(pid=2756)
from client vmw2ktest: WRN - can't open file: C:\WINNT\system32\config\
SysEvent.Evt (WIN32 3: The system cannot find the path specified.)
■ Work around:
To work around this issue, create the following directory on the client:
c:\winnt\system32\winevt\logs


■ TITAN cases: 281-680-968
NB_6.5.6.winnt.x86
■ Description:
During an attempt to back up CCR clusters, the bpfis on the passive node
would fault and fail.
■ TITAN cases: 320-232-329
■ Description:
That release contains multiple NetBackup 6.5.4 fixes that address previously
reported issues.
■ TITAN cases: 230-677-886
NB_6.5.6.winnt.x86
■ Description:
In a Veritas Security Services configuration, if you used the Copy to new user
group option, a new group is created but the permissions were not copied over
to the new user group.
■ TITAN cases: 281-645-651
■ Description:
A new option has been added to the nbftconfig. The -listtargets lists details
of the FT Target ports. By default all target ports across all FT media servers
are listed and you can filter the output for a media server.

■ Description:
An issue existed for a FlashBackup policy with snapshots enabled and
configured with inline tape copy. If the resource was not allocated for the first
copy then the job was erroneously marked DONE in the Activity Monitor and
no more jobs were scheduled for this policy and client.
■ TITAN cases: 240-978-424
■ Contained in: NBLU_6.5.6.WIN NB_NOM_6.5.6.winnt.IA64
NB_NOM_6.5.6.winnt.x64 NB_NOM_6.5.6.winnt.x86
■ Description:
A change was made to correct an installation issue.
See Etrack incident 1704746 for more information about the resolution of this
issue.
■ TITAN cases: 410-826-062
■ Description:
A change has been made to ensure that NetBackup no longer creates world
writeable files. (That change resolves a security issue).
■ Contained in: NBLU_6.5.6.WIN NB_JAV_6.5.6.winnt.IA64
NB_JAV_6.5.6.winnt.x64 NB_JAV_6.5.6.winnt.x86
■ Description:
The Java run time (JRE) packaged in the 6.5.6 Windows_64 build has been
updated to 1.6.0_17.
■ TITAN cases: 312-189-222
■ Description:
A change was made to address an issue that caused migvold to exit with a
signal 16.
■ TITAN cases: 220-692-308
NB_6.5.6.winnt.x86
■ Description:
For an Exchange off-host backup in which NetBackup was installed in a
different folder on the off-host client than on the primary client, the snapshot
job failed with a status 130.
■ TITAN cases: 320-206-408
NB_6.5.6.winnt.x86
■ Description:
An Exchange CCR cluster backup took a very long time to complete when the
passive node was down. The total amount time was directly proportional to
the number of Exchange storage groups.
■ TITAN cases: 281-743-167
NB_6.5.6.winnt.x86
■ Description:
A change was made to address a performance issue that caused the user
interface to consume too much of the CPU. That issue would occur when
anything but the activity monitor was selected.
■ TITAN cases: 281-749-201 411-395-830

■ Description:
During a synthetic backup, the read-side media server changed after it read
some images.
■ TITAN cases: 220-688-523
■ Description:
Oracle Recovery Manager (RMAN) backups with Hitachi_ShadowImage on an
alternate host took more than an hour to perform the bpfis create.
■ TITAN cases: 312-180-772
NB_6.5.6.winnt.x86
■ Description:
The NetBackup Administration Console for Windows IA64 would crash when
the user tried to open or save a file with the Open or Save As dialog. The issue
was found in the Catalog Recovery Wizard, more specifically, the License
keys Save As dialog, and the Host Properties Save As dialog.
■ TITAN cases: 240-904-318
NB_6.5.6.winnt.x86
■ Description:
If you attempted to add multiple SSO Media servers with a large number of
drives (more than 128) in Device Configuration Wizard, the following message
would appear:
The maximum number of enabled drives is 128
A change was made to correct this issue.


■ TITAN cases: 240-904-196 291-167-758
■ Description:
A change was made to address an issue that caused the Resource Broker to
hang because of a thread re-use when it made a CORBA call.
■ TITAN cases: 281-642-467 281-725-658 281-732-149 320-218-719
NB_6.5.6.winnt.x86
■ Description:
If a batch file was created to back up a large number of databases that use the
NetBackup for Microsoft SQL Server agent and specify $ALL to the database
keyword, the database backup operation gets "silently" skipped and yet report
a success. (A status code 0 is reported in the Activity Monitor). That same
result could occur when a large number of databases have been manually
enumerated within the batch file through the use of multiple database
keywords.
■ Work around:
To avoid this issue, perform the following:
Add the BATCHSIZE # directive to the batch file. Use a value that is equal to
or less than the number of databases listed in the batch file. Or use the number
that would be enumerated by use of the database $ALL directive.
Refer to the NetBackup 6.5 for Microsoft SQL Administrator's Guide for more
information about the BATCHSIZE directive.
■ TITAN cases: 320-196-561
■ Description:
The nbdevconfig command would break the file system list when a mount
point ended with a dot.
When AdvancedDisk was configured, not all file systems appeared in the list
of devices. And not all file mount points appear in the list. That issue appeared
when there was a mount point that ended with a dot, ".".
■ Work around:
To avoid this issue, do not configure file system mount points that end with
".".
■ TITAN cases: 320-237-675 410-747-859
NB_6.5.6.winnt.x86
■ Description:
A multiple VC/Proxy environment fails if the proxy could not talk to one of
the VC's because of multiple networks.
The change checks for a new registry entry in Config\BACKUP called
excludeVMservers. That is a string value that contains a comma-separated
list of VMware servers to ignore.
NB_6.5.6.winnt.x86
■ Description:
A change was added to correct the display of repeated server names listed in
VMware Restore Marked Files window.
■ Description:
The ndmpagent process would crash on Windows x64 platforms because of
certain mtime values returned by the filer.
That only happened when the NDMP, VxUL Debug-level was set to five or six.
■ Work around:
To resolve this issue, turn off VxUL logging for NDMP (ID 151), or set
DebugLevel to 4 or lower.


NB_6.5.6.winnt.x86
■ Description:
A change was made to correct an issue that caused a possible crash when doing
granular browses and restores in the nblbc and the nbgre processes.
■ Description:
A change was made to ensure that the NetBack Job Manager does not crash if
a non-streamed BMR job was executed.
■ Description:
Changes were made to improve NetBackup's SLP query optimization.
■ TITAN cases: 281-805-383
■ Description:
NetBackup Resource Broker did not consistently grant resources to the storage
unit groups when its internal cache became invalid. That could happen when
drives went down unexpectedly.
■ TITAN cases: 281-778-470 320222610 410-738-664
■ Description:
The NetBackup Job Manager (NBJM) would core dump during the enumeration
of snapshot details for an Exchange backup. A memory fragmentation caused
this issue.


■ TITAN cases: 312-189-219
■ Description:
A change was made to ensure that immediate manual backup jobs outside of
window are retried.
■ TITAN cases: 320-226-967 411-220-369
■ Description:
FlashBackup Single File Restores (SFR) from incremental backups could fail
with a status code 5 because of a blocked position miscalculation.
Error: first XFERBLOCK indicated block number of "X" but initial

positioning was for block "X-1"

■ TITAN cases: 320-218-499
■ Description:
A change was made to ensure that a DR email is sent after a hot catalog backup
with ITC, where one storage unit is PDDO.
■ TITAN cases: 220-695-490
■ Description:
A user could encounter the following BPDBM error message if they attempted
to run an image cleanup at the same time as backup jobs were run.
"getJobExistsById: BPXMInterface.cpp.602 - CORBA::EXCEPTION on

jm connection. exception = MARSHAL"
■ Work around:
That error message does not affect how NetBackup functions.
NB_6.5.6.winnt.x86
■ Description:
An Exchange GRT backup failed with a status 1 error. The following error
message appeared in the bpbkar log file.
Recovery FAILED - ERROR::RC = -501 - -501 The log file is corrupt

■ TITAN cases: 320-217-862 411-407-917
NB_6.5.6.winnt.x86
■ Description:
FlashBackup Window restores would fail with the following message in the
bprd log.
bprd.sfr: flush_to_bptm: put_data returned -4 STATUS 175

■ TITAN cases: 312-187-267
■ Description:
A resource leak would occur if bpcompatd used an auto socket handle instead
of a member variable.
■ TITAN cases: 281-747-162 410-628-196 411-881-580

NB_6.5.6.winnt.x86
■ Description:
The bpbkar.exe executable would crash if you attempted to back up the inactive
node of a clustered Windows client at the same time as a Shadow Copy
Components or System State backup.
■ TITAN cases: 281-717-137
■ **Description:
Optimized duplication using PureDisk STU (PDDO) succeeds for an Exchange
Granular backup, however the second copy was not created.
■ TITAN cases: 281-761-365
■ Description:
The shmat() function returned a -1 when an error occurred. Not checking for
this return value resulted in ShmAddress = 0xffffffff, which led to a core
dump issue.
NB_6.5.6.winnt.x86
■ Description:
A change was made to ensure that after you edit a policy, the jobs do not fail
with a storage unit not defined.
■ Description:
An OpenStorage device returned an EBUSY message during an optimized
duplication would produce critical, misleading error messaging. The expected
behavior was to retry the bp_sts_copy_extent call. A change was made to

ensure that retried optimized duplication is not viewed as a critical error.
■ TITAN cases: 320-179-392
■ Description:
The Backup, Archive and Restore (BAR) GUI (jbpSA) and bpdbsbora did not
preserve or obtain the Oracle environment in all cases.
■ TITAN cases: 220-700-176 410-658-066
NB_6.5.6.winnt.x86
■ Description:
A single-stream backup that includes Shadow Copy Components can exit with
a Status 0 if VSS is disabled.
■ Work around:
To avoid this issue, do not disable VSS.
■ TITAN cases: 281-580-926
■ Description:
A change was made to correct a socket communication failure that caused
bptm.exe to wait a very long time for a TERMINATE from bpbrm during a
backup job.
That issue caused the following problems to happen concurrently:
■ bptm.exe runs forever while it waits for TERMINATE from bpbrm.exe.
■ the ...\media\db\drives\drivename file was never cleaned up.

■ The tape was never dismounted from the drive.

■ All following jobs to this media server fail because it is unable to successfully
mount the requested tape.
■ Bptm.exe continues to run even after bpdown is run on the media server.
■ Reboot or manually terminating bptm.exe is the only way to kill the process.
■ But the ...\db\media\drive\ contents remains - manually have to clean
it up to.
Appendix A
About NetBackup release
history
This appendix includes the following topics:
■ About previous NetBackup releases
■ Master Etrack Index for all previous releases
About previous NetBackup releases

For additional information about the contents of what was released in a previous
version of NetBackup, refer to one of the following TechNotes on the Symantec
Support Web site:
■ NetBackup 6.5.5 Release Update




160 About NetBackup release history
Master Etrack Index for all previous releases

This topic contains a master list of all of the Etracks fixed in each of the previous
NetBackup releases. The Etracks are sorted according to the release the Etrack
was fixed in as well as by the container. You can use this master ET index to quickly
locate which version and container a particular change was made in.
NetBackup 6.5.5 packaged Etracks for UNIX and Windows

This section contains a master index for all of the Etracks that have been fixed
and were packaged in NetBackup 6.5.5. The Etracks are sorted according to the
containers that they were fixed in.
NB_BMR_6.5.5
1637616 1737811
1679309 1835808
NB_SNC_6.5.5
1599687 1728862 1748009
NB_6.5.5.winnt.x86
1500540 1502113 1502504 1503186 1509541 1518794 1535613 1537233 1538081
1538752 1541690 1541691 1544453 1545138 1556733 1588664 1589291 1593090
1596813 1599687 1599756 1600913 1603822 1630735 1632610 1632759 1636151
1637358 1637616 1638341 1638475 1639335 1664215 1666984 1673411 1675851
1677038 1680615 1705725 1706172 1707862 1708623 1710741 1711036 1719418
1852361 1719730 1723707 1723828 1723987 1724975 1727869 1728862 1729167
1730741 1737811 1739362 1741915 1745294 1745631 1745698 1745840 1749700
1751983 1754651 1763377 1764263 1764314 1779214 1781802 1783183 1785238
1785354 1786657 1789754 1801708 1805697 1832341 1837044 1840459 1843770
NB_6.5.5.winnt.x64
1500540 1502113 1502504 1503186 1509541 1518794 1535613 1537233 1538081
1538752 1541690 1541691 1544453 1545138 1556733 1588664 1589291 1593090
1596813 1599687 1599756 1600913 1603822 1630735 1632610 1632759 1636151
1637358 1637616 1638341 1638475 1639335 1664215 1666984 1673411 1675851
1677038 1680615 1705725 1706172 1707862 1708623 1710741 1711036 1719418
About NetBackup release history 161
1852361 1719730 1723707 1723828 1723987 1724975 1727869 1728862 1729167

1730741 1737811 1739362 1741915 1745294 1745631 1745698 1745840 1749700
1751983 1754651 1763377 1764263 1764314 1779214 1781802 1783183 1785238
1785354 1786657 1789754 1801708 1805697 1832341 1837044 1840459 1843770
NB_CLT_6.5.5
1502113 1503186 1518794 1535613 1537233 1538081 1538752 1541691 1544453
1545138 1556733 1588664 1589291 1590560 1593090 1596813 1599756 1600913
1603822 1630735 1632610 1632759 1636151 1637358 1639335 1664215 1668477
1672567 1673411 1677038 1705725 1706172 1707862 1708623 1710741 1711036
1719418 1719730 1723707 1723872 1723987 1724975 1727869 1730741 1741915
1745294 1745698 1749700 1763377 1764263 1781802 1782070 1783183 1785238
1785354 1786657 1789754 1801708 1805697 1831044 1832341 1837044 1843135
1843594 1843770 1852361
NB_JAV_6.5.5
1679309 1835808
NBLU_6.5.5.UNIX
1502113 1503186 1518794 1535613 1537233 1538081 1538752 1541691 1544453
1545138 1556733 1588664 1589291 1590560 1593090 1596813 1599687 1599756
1600913 1603822 1630735 1632610 1632759 1636151 1637358 1637616 1639335
1664215 1668477 1672567 1673411 1677038 1679309 1705725 1706172 1707862
1708623 1710741 1711036 1719418 1852361 1719730 1723707 1723872 1723987
1724975 1727869 1728862 1730741 1737811 1741915 1745294 1745698 1748009
1749700 1763377 1764263 1764314 1781802 1782070 1783183 1785238 1785354
1786657 1789754 1801708 1805697 1831044 1832341 1835808 1837044 1843135
1843594 1843770
NBLU_6.5.5.WIN
1500540 1502113 1502504 1503186 1509541 1518794 1535613 1537233 1538081
1538752 1541690 1541691 1544453 1545138 1556733 1588664 1589291 1593090
1596813 1599687 1599756 1600913 1603822 1630735 1632610 1632759 1636151
1637358 1637616 1638341 1638475 1639335 1664215 1666984 1673411 1675851
1677038 1679309 1680615 1705725 1706172 1707862 1708623 1710741 1711036
1719418 1852361 1719730 1723707 1723828 1723987 1724975 1727869 1728862
1729167 1730741 1737811 1739362 1741915 1745294 1745631 1745698 1745840
1749700 1751983 1754651 1763377 1764263 1764314 1779214 1781802 1783183
1785238 1785354 1786657 1789754 1801708 1805697 1832341 1835808 1837044
1840459 1843770
1679309 1835808
NB_6.5.5.winnt.IA64
1500540 1502113 1502504 1503186 1509541 1518794 1535613 1537233 1538081
1538752 1541690 1541691 1544453 1545138 1556733 1588664 1589291 1593090
1596813 1599687 1599756 1600913 1603822 1630735 1632610 1632759 1636151
1637358 1637616 1638341 1638475 1639335 1664215 1666984 1673411 1675851
1677038 1680615 1705725 1706172 1707862 1708623 1710741 1711036 1719418
1852361 1719730 1723707 1723828 1723987 1724975 1727869 1728862 1729167
1730741 1737811 1739362 1741915 1745294 1745631 1745698 1745840 1749700
1751983 1754651 1763377 1764263 1764314 1779214 1781802 1783183 1785238
1785354 1786657 1789754 1801708 1805697 1832341 1837044 1840459 1843770
NB_BBS_6.5.5
1737811
NB_VLT_6.5.5
1764314
NB_JAV_6.5.5.winnt.IA64
1679309 1835808
NB_6.5.5
1502113 1503186 1518794 1535613 1537233 1538081 1538752 1541691 1544453
1545138 1556733 1588664 1589291 1593090 1596813 1599756 1600913 1603822
1630735 1632610 1632759 1636151 1637358 1639335 1664215 1668477 1672567
1673411 1677038 1705725 1706172 1707862 1708623 1710741 1711036 1719418
1719730 1723707 1723872 1723987 1724975 1727869 1730741 1741915 1745294
1745698 1749700 1763377 1764263 1781802 1782070 1783183 1785238 1785354
1786657 1789754 1801708 1805697 1831044 1832341 1837044 1843135 1843594
1843770 1852361
NetBackup 6.5.4 UNIX packaged Etracks

This section contains a master index for all UNIX packages of Etracks that have
been fixed in this release, sorted according to the containers that they were fixed
in.
NB_6.5.4
1285455 1247094 1266996 1274467 1271181 1266828 1267706 1240486 1275233
1291152 1260323 1251656 1254610 1248242 1290084 1281628 1264543 1277465
1267880 1065622 1298872 1286001 1278425 1298551 1266772 1295790 1321721
1151349 1276983 1274105 1286092 1302201 1253910 1246062 1316896 1234683
1282457 1315723 1141312 1235177 700722 1316030 1269701 1221450 1301941
1302903 1245767 1240580 1260009 1365476 1364370 1261359 1182949 1368000
1361179 1374137 1274771 1385956 1283409 1378098 1388949 1256040 1257567
1384505 1394294 1391201 1243760 1397770 1397803 1394464 1395191 1180431
1395095 1378871 1392357 1128777 1395388 1407095 1400851 1296897 1386091
1402016 1392368 1413113 1278561 1413313 1390861 1414077 1173100 1390505
1410798 1282150 1415947 1414211 1414312 1418051 1268084 1412901 1411499
1400002 1422476 1421893 1274472 1267027 1370671 1208654 1371578 1424207
1400376 1424291 1407021 1283922 1421724 1422599 1413001 1400717 1473485
1473486 1410178 1294340 1418524 1397773 1301030 1412924 1413063 1431018
1433273 1399857 1425305 1434146 1426057 1384805 1276634 1431894 1416846
1435119 1431758 1431826 1417844 1396173 1383748 1439607 1135673 1430950
1406219 1406213 1436844 1431015 1441498 1433052 1439252 1435489 1323857
1538553 1431527 1426014 1444551 1427600 1414674 1445493 1381806 1442063
1447058 1445648 1430034 1411788 1413618 1431088 1447265 1447160 1432407
1446408 1437425 1425084 1448195 1442239 1418373 1452416 1148446 1446653
1451465 1447260 1453529 1442301 1451023 1436594 1453605 1416785 1379510
1262599 1446468 1459294 1399839 1465331 1395101 1465033 1458226 1450234
1449178 1453422 1458420 1432148 1405180 1470340 1460964 1463890 1468581
1448206 1481250 1529072 1446401 1481284 1446147 1450564 1466528 1464016
1452281 1421534 1460587 1439971 1467900 1471621 1468877 1428325 1469444
1471613 1463937 1465258 1464015 1476600 1482673 1482676 1480286 1587338
1602790 1600654 1474403 1448396 1408851 1412268 1458872 1473860 1474475
1465728 1438645 1433497 1438822 1450268 1475313 1473499 1417504 1452344
1478495 1478915 1475161 1461116 1126065 1480041 1469706 1460837 1468318
1464701 1481159 1480280 1461993 1300129 1463877 1449955 1472234 1451817
1481404 1414922 1437385 1481373 1476107 1374989 1482914 1477935 1486988
1485005 1485946 1437453 1402322 1481348 1486168 1472633 1486686 1486807
1487580 1487510 1464678 1488267 1444236 1452950 1481714 1478999 1470973
1485977 1488734 1475372 1484302 1500272 1500484 1487577 1557578 1488525
1501040 1501855 1450415 1503555 1503554 1504217 1502059 1475402 1503097
1505138 1504987 1505661 1429723 1507290 1505203 1507663 1501647 1501118
1417539 1502104 1508567 1507033 1500451 1509112 1499426 1509107 1508224
1155347 1454759 1483007 1509370 1508901 1511217 1449853 1481224 1455436
1406992 1514843 1502251 1503674 1508943 1476060 1515064 1518716 1517830
1516611 1516658 1511966 1515378 1512269 1515674 1475595 1517091 1468310
1501973 1520790 1517775 1518415 1521609 1520660 1521319 1514161 1519049
1523991 1521072 1515697 1428897 1523771 1524262 1524495 1512307 1514813
1505895 1525307 1518751 1524391 1506156 1526402 1527601 1501039 1467372

1593966 1529861 1527862 1461913 1522273 1514334 1527768 1531249 1523443
1587409 1530121 1525375 1512052 1531929 1529030 1531907 1533986 1516985
1533817 1534963 1535794 1535780 1536441 1529377 1535663 1539736 1536918
1537820 1541722 1534880 1541682 1521076 1541521 1542981 1536999 1544193
1539274 1545900 1550511 1542746 1544010 1545883 1557845 1558318 1542974
1586474 1557304 1587307 1558193 1590423 1595019 1598449 1594679 1545939
NB_BBS_6.5.4
1280130 1201793 1315488 1147236
NB_BMR_6.5.4
1201738 1300796 1235891 1251401 1205755 1363119 1282624 1300702 1300520
1409123 1404510 1423547 1368029 1442012 1226065 1450240 1426891 1452256
1455096 1463875 1466044 1469841 1470826 1476962 1477173 1372973 1477142
1479559 1485370 1519805 1516293 1525928
NB_CLT_6.5.4
1285455 1247094 1266996 1274467 1271181 1266828 1267706 1240486 1275233
1291152 1260323 1251656 1254610 1248242 1290084 1281628 1264543 1277465
1267880 1065622 1298872 1286001 1278425 1298551 1266772 1239520 1295790
1321721 1151349 1276983 1274105 1286092 1302201 1316849 1427469 1456039
1458931 1468485 1502155 1503870 1502078 1518331 1501805 1301041 1253910
1246062 1316896 1234683 1282457 1315723 1141312 1235177 700722 1316030
1269701 1221450 1301941 1302903 1245767 1240580 1260009 1363123 1365476
1226486 1244254 1249811 1255700 1370738 1384896 1377315 1382522 1383095
1126594 1403614 1431007 1432150 1421497 1509875 1558174 1590973 1595083
1598047 1597697 1603770 1603922 1364370 1261359 1182949 1368000 1361179
1374137 1250875 1274771 1385956 1283409 1378098 1388949 1256040 1257567
1227674 1384505 1394294 1391201 1243760 1397770 1397803 1394464 1395191
1180431 1395095 1378871 1392357 1128777 965836 1395388 1407095 1400851
1296897 1386091 1402016 1392368 1413113 1278561 1413313 1390861 1414077
1173100 1390505 1410798 1282150 1415947 1414211 1414312 1418051 1268084
1412901 1411499 1400002 1422476 1421893 1274472 1267027 1370671 1208654
1371578 1424207 1400376 1424291 1407021 1283922 1421724 1422599 1413001
1400717 1473485 1473486 1410178 1294340 1418524 1397773 1301030 1412924
1413063 1431018 1433273 1399857 1425305 1434146 1426057 1384805 1276634
1431894 1416846 1435119 1431758 1431826 1417844 1396173 1383748 1439607
1135673 1430950 1406219 1406213 1436844 1431015 1441498 1433052 1439252
1435489 1323857 1538553 1431527 1426014 1444551 1427600 1414674 1445493
1381806 1442063 1447058 1445648 1430034 1411788 1413618 1431088 1447265
1447160 1432407 1446408 1437425 1425084 1448195 1442239 1418373 1452416
1148446 1446653 1451465 1447260 1453529 1442301 1451023 1436594 1453605
1416785 1379510 1262599 1446468 1459294 1399839 1465331 1395101 1465033
1458226 1450234 1449178 1453422 1458420 1432148 1405180 1470340 1460964

1463890 1468581 1448206 1481250 1529072 1446401 1481284 1446147 1450564
1466528 1464016 1452281 1421534 1460587 1439971 1467900 1471621 1468877
1428325 1469444 1471613 1463937 1465258 1464015 1476600 1482673 1482676
1480286 1587338 1602790 1600654 1474403 1448396 1408851 1412268 1458872
1473860 1465634 1474475 1465728 1438645 1433497 1475916 1438822 1450268
1475313 1473499 1417504 1452344 1478495 1478915 1475161 1461116 1126065
1480041 1467989 1469706 1460837 1468318 1464701 1481159 1480280 1461993
1482660 1300129 1463877 1449955 1472234 1451817 1481404 1414922 1437385
1481373 1476107 1374989 1482914 1477935 1486988 1485005 1485946 1437453
1402322 1481348 1486168 1472633 1486686 1486807 1487580 1487510 1464678
1488267 1444236 1452950 1481714 1478999 1470973 1485977 1488734 1475372
1484302 1500272 1500484 1487577 1557578 1405038 1488525 1435092 1501040
1501855 1450415 1503555 1503554 1504217 1502059 1475402 1503097 1505138
1504987 1505661 1429723 1507290 1505203 1507663 1501647 1501118 1417539
1502104 1508567 1406063 1507033 1500451 1509112 1499426 1509107 1508224
1155347 1454759 1483007 1509370 1508901 1511217 1449853 1481224 1455436
1406992 1514843 1502251 1503674 1508943 1476060 1515064 1518716 1517830
1516611 1516658 1511966 1515378 1512269 1515674 1475595 1517091 1468310
1501973 1520790 1517775 1518415 1521609 1520660 1521319 1514161 1519049
1523991 1521072 1458798 1515697 1428897 1523771 1524262 1524495 1512307
1514813 1505895 1525307 1518751 1524391 1506156 1526402 1527601 1501039
1467372 1593966 1529861 1527862 1461913 1522273 1510981 1514334 1527768
1531249 1523443 1587409 1530121 1525375 1512052 1531929 1529030 1531907
1533986 1516985 1533817 1534963 1535794 1535780 1536441 1529377 1535663
1539736 1536918 1537820 1541722 1534880 1541682 1521076 1541521 1542981
1536999 1544193 1539274 1545900 1550511 1542746 1557316 1557318 1544010
1545883 1557845 1558318 1542974 1586474 1557304 1587307 1558193 1590423
1595019 1598449 1594679 1545939
NB_DB2_6.5.4
1398665 1374366 1427035 1441557
NB_DMP_6.5.4
1217098 1247981 1275573 1281911 1208508 1286172 1361300 1167140 1424308
1421594 1442316 1469272 1462054 1479387 1505107 1502073
NB_ENC_6.5.4
1413512
NB_INX_6.5.4
1302046
NB_JAV_6.5.4
1269550 1385012 1015590 1373561 1231644 1398344 1398173 1385770 1300978

1402954 1412872 1411564 1412461 1425914 1035276 1421469 1388074 1416268
1439821 1436533 1426474 1439070 1398689 1447620 1155201 1453215 1456221
1451244 1454298 1465532 1252404 1461593 1471948 1433549 1475026 1475814
1452175 1479108 1466996 1478919 1483476 1483362 1483465 1391155 1486506
1478018 1500190 1483897 1399167 1505537 1399174 1517224 1519186 1518747
1524277 1531521 1544995
NB_LOT_6.5.4
1487594
NB_LUA_6.5.4
1363981 1513309 1158858
NB_NOM_6.5.4
1167039 1255955 1240142 1245644 1275868 927989 1203966 855237 1427680
1315412 1446868 1422459 1461305 1259890 1432471 1414295 1448155 1484203
1529844 1528847
NB_ORA_6.5.4
1374366 1402422 1452458
NB_SAP_6.5.4
1063955 1430999 1458282 1509336 1501622
NB_SMU_6.5.4
1442031 1463891 1484940 1510055
NB_SNC_6.5.4
1275601 1244922 1249726 1287259 1272183 1258356 1272157 378649 1250928
1251765 1130616 1198363 1317951 1323300 1228384 1252585 1323643 1363449
1257455 1134680 1323758 1283920 1276398 1378894 1366314 1278645 1403955
1415117 1253140 1251337 1053635 1412947 1424138 1250759 382235 1444727
1448262 1447692 1446792 1457644 1456424 1428284 1466545 1466832 1428408
1437956 1461478 1428729 1460851 1477603 1474586 1231756 1481101 1483134
1481079 1462067 1513666 1526648 1529942 1474498 1532955 1529158 1537663
1533275 1535789 1542470 1599601
NB_SYB_6.5.4
1321466
NB_VLT_6.5.4
1321303 1399444 294799 1453874 1461863 1449157 1465117 1486202 1460712
1525087
NetBackup 6.5.4 Windows packaged Etracks

This section contains a master index for all Windows packages of Etracks that
have been fixed in this release, sorted according to the containers that they were
fixed in.
NB_6.5.4.x86, NB_6.5.4.x64, and NB_6.5.4.IA64
1285455 1266996 1274467 1271181 1266828 1201793 1201738 1267706 1275233
1291152 1260323 1251656 1275601 1244922 1249726 1248242 1290084 1281628
1264543 1287259 1277465 1267880 1065622 1298872 1286001 1278425 1300796
1235891 1269439 1300858 1298551 1266772 1239520 1295790 1321721 1151349
1287091 963688 1287123 1508246 1276983 1272183 1298900 1258356 1272157
1042455 1250928 1286092 1253170 1302201 1316849 1427469 1456039 1458931
1468485 1502155 1503870 1502078 1518331 1501805 1253910 1248524 1246062
1316896 1268978 1285995 1253909 1282457 1251765 1315723 1235177 700722
1198363 1316030 1269701 1195355 1217098 1323300 1221450 1228384 1317613
1302903 1251401 1245767 1247981 1240580 1205755 1252585 1323643 1260009
1275573 1137681 1281911 1208508 1363123 1282624 1323935 1363449 1365476
1250754 1301328 1226486 1244254 1249811 1255700 1370738 1384896 1377315
1382522 1383095 1126594 1403614 1431007 1432150 1421497 1509875 1558174
1590973 1595083 1598047 1597697 1603770 1603922 1290087 1286172 1364370
1261359 1182949 1368000 1257455 1361300 1134680 1323758 1361179 1374137
1276398 1260685 1231645 1063955 1274771 1321303 1221671 1378894 1167140
1378219 1374280 1397816 1366314 1138684 1385956 1283409 1378098 1218897
1256040 1257567 1300702 1372709 1227674 1384505 1394294 1391201 1397770
1397803 1394464 1395191 1180431 1395095 1399444 1378871 1392357 1403045
1128777 1402256 965836 1395388 1374366 1406164 1407095 1141109 1117738
1400851 1409123 294799 1296897 1386091 1402016 1392368 1413113 1374366
1418493 1278561 1413313 1414077 1173100 1267030 1415117 1410798 1404510
1282150 1415947 1414211 1414312 1418051 1268084 1413284 1413306 1412901
1414771 1411499 1400002 1412947 1422476 1421893 1274472 1423547 1267027
1370671 1208654 1415667 1371578 1424207 1400376 1427035 1425698 1424291
1424308 1421594 1407021 1283922 1421724 1422599 1413001 1400717 1414132
1473485 1473486 1410178 1294340 1418524 1397773 1301030 1412924 1413063
1431018 1400713 1433273 1399857 1425305 1435406 1434146 1431886 1383041
1426057 1384805 1276634 1416828 1436517 1431894 1437623 1250759 1416846
1394077 1374663 1428768 1431758 1431826 1417844 1424613 1396173 1429569
1427179 1439096 1383748 1439607 1433274 1135673 1430950 1406219 1406213
1436844 1431015 1442316 1441498 382235 1434748 1366169 1430370 1433052
1439252 1435489 1121521 1444280 1323857 1538553 1443445 1431888 1443521
1437899 1431527 1426014 1430999 1445255 1266674 1444551 1427600 1445493
1381806 1442063 1426468 1447623 1447058 1447946 1223943 1368590 1445648
1368590 1430034 1411788 1296686 1413618 1431088 1448686 1447265 1447160
1432407 1446408 1437425 1226065 1433167 1424008 1425084 1407100 1428501
1450941 1442239 1418373 1252553 1452416 1447692 1148446 1446653 1451465

1447260 1453529 1449480 1446254 1442301 1451023 1426891 1436594 1453605
1451053 1414939 1446792 1452718 1454277 1452716 1452707 1452702 1453629
1441557 1416785 1379510 1457644 1402422 1456424 1262599 1427460 1459200
1447346 1406192 1446468 1452256 1461289 1413224 1459685 1459294 1399839
1455096 1463875 1465331 1395101 1465033 1412607 1458226 1455622 1461863
1450234 1460818 1449178 1453422 1449157 1458420 1458816 1458880 1432148
1405180 1469272 1470340 1460964 1463890 1468581 1462054 1466044 1448206
1481250 1529072 1446401 1481284 1446147 1450564 1466528 1464016 1452281
1293617 1468001 1469841 1470826 1421534 1460587 1439971 1467900 1471621
1468877 1442844 1428325 1469444 1471613 1473392 1463937 1465258 1472532
1470771 1464015 1476600 1482673 1482676 1480286 1587338 1602790 1600654
1474403 1448396 1408851 1412268 1458872 1473860 1474475 1461478 1471438
1465728 1468747 1433497 1475096 1452458 1428729 1438822 1450268 1451209
1076978 1475313 1476962 1473499 1450317 1434397 1417504 1471928 1474586
1443130 1452344 1478495 1477173 1142439 1372973 1478915 1479387 1475161
1461116 1477142 1476495 1479559 1480041 1469706 1460837 1468318 1480411
1464701 1421074 1481159 1480280 1461993 1453240 1479474 1458282 1439713
1480432 1449955 1472234 1481280 1483134 1480452 1481305 1479156 1321653
1451817 1481404 1320617 1414922 1437385 1481373 1484335 1268436 1476107
1374989 1457681 1477935 1486988 1266581 1469295 1485764 1485005 1485946
1437453 1481348 1486168 1247756 1442585 1453600 1485370 1482578 1484721
1472633 1486660 1245771 1486807 1483057 1487580 1487510 1487166 1470461
1464678 1480739 1488267 1487657 1488603 1444236 1452950 1481714 1421076
1478999 1470973 1481219 1480521 1485977 1488734 1484302 1488815 1500272
1500484 1487577 1557578 1416786 1488525 1435092 1501868 1486202 1502070
1500933 1483246 1486107 1501855 1450415 1503535 1501912 1503555 1503554
1504217 1502933 1451740 1502934 1502059 1475402 1503097 1505138 1504987
1500382 1505661 1429723 1501282 1448163 1452465 1475676 1505107 1501647
1501118 1504335 1417539 1507389 1394920 1500505 1502104 1508567 1505184
1507033 1505085 1500451 1460712 1500140 1499426 1509107 1508224 1155347
1454759 1462067 1399041 1483007 1475985 1507435 1478387 1457797 1473354
1509370 1508901 1511217 1449853 1508884 1481224 1455436 1503625 1511814
1505823 1502073 1509984 1509336 1514843 1513308 1509793 1502251 1468495
1508125 1513699 1514377 1503674 1457797 1516760 1474524 1517227 1502472
1508943 1513829 1440607 1476060 1515064 1501622 1518716 1517830 1516611
1516658 1511966 1515378 1512269 1515674 1507115 1475595 1517091 989955
1519314 1514502 1519805 1517609 1468310 1501973 1517549 1520277 1519822
1506408 1516293 1520790 1517733 1517775 1518415 1521169 1521609 1520660
1522936 1473422 1521319 1514161 1518580 1519049 1523991 1521072 1521249
1513309 1515697 1523771 1524262 1525087 1524495 1524542 1512307 1521067
1514813 1246723 1505895 1391543 1525307 1518751 1524391 1513666 1526402
1526648 1525408 1527601 1525928 1467372 1593966 1522384 1529861 1526650
1527862 1461913 1474498 1524775 1530040 1514334 1524542 1527768 1218121

1529958 1530419 1531249 1523443 1587409 1530121 1525375 1512052 1528010
1531929 1529030 1531183 1532954 1532955 1529158 1537663 1531907 1533986
1532972 1516985 1533817 1534963 1534005 1531793 1533795 1526415 1485141
1535780 1526611 1536441 1381252 1529377 1535017 1526783 1476619 1535482
1537883 1538068 1504413 1535663 1539736 1536918 1537820 1486189 1520098
1534880 1541682 1521076 1541521 1542470 1539774 1542981 1539662 1545112
1536999 1544193 1539274 1545900 1550511 1542746 1537709 1557316 1557318
1539878 1544010 1538891 1545883 1557845 1544119 1532123 1557656 1558318
1542974 1586474 1557304 1545352 1587307 1558193 1586063 1590881 1590423
1595019 1598449 1594679 1505207 1596956 1599538 1545939 1599601 1630537
NB_JAV_6.5.4.x86
1269550 1385012 1015590 1373561 1231644 1398344 1398173 1385770 1300978
1402954 1412872 1411564 1412461 1425914 1412276 1035276 1421469 1388074
1416268 1439821 1436533 1426474 1439070 1398689 1447620 1155201 1453215
1456221 1451244 1454298 1465532 1252404 1461593 1471948 1433549 1475026
1475814 1452175 1479108 1466996 1478919 1483476 1483362 1391155 1486506
1478018 1500190 1483897 1399167 1505537 1399174 1517224 1519186 1518747
1524277 1531521 1544995
NB_JAV_6.5.4.IA64
1269550 1385012 1015590 1373561 1231644 1398344 1398173 1385770 1300978
1402954 1412872 1411564 1412461 1425914 1412276 1035276 1421469 1388074
1416268 1439821 1436533 1426474 1439070 1398689 1447620 1155201 1453215
1456221 1451244 1454298 1465532 1252404 1461593 1471948 1433549 1475026
1475814 1452175 1479108 1466996 1478919 1483476 1483362 1391155 1486506
1478018 1500190 1483897 1399167 1505537 1399174 1517224 1519186 1518747
1524277 1531521 1544995
NB_NOM_6.5.4.x86
1167039 1255955 1240142 1245644 1275868 927989 1203966 855237 1427680
1315412 1446868 1422459 1461305 1259890 1432471 1414295 1448155 1484203
1481142 1529844 1528847

in.
NB_6.5.3
1275559 1302929 1302749 1317013 1317008 1317006 1317202 1317047 1276489
1318091 1289921 1322984 1364407 1364422 1322803 1364661 1373019 1383374
1382658 1383586 1383584 1184889 1276613 1382632 1383839 1383438 1383440

1383434 1383442 1383733 1383750 1383540 1384029 1375483 1383736 1383527
1383523 1384879 1385083 1385111 1386294 1383757 1384675 1383511 1385061
1382599 1376805 1383782 1383502 1383497 1383499 1384270 1386057 1386060
1383811 1383808 1382683 1384822 1386064 1386062 1386073 1383727 1383766
1386069 1384960 1386075 1386077 1384019 1386065 1386070 1387046 1383743
1384952 1387039 1383643 1384946 1384943 1388149 1384948 1383744 1386199
1384909 1389088 1374330 1388180 1383756 1388192 1382684 1383404 1390335
1383742 1383761 1391168 1382623 1391109 1383763 1394025 1383630 1392132
1388236 1384020 1395057 1384919 1383792 1383772 1393919 1384032 1384023
1384966 1395393 1383506 1396153 1391110 1397984 1399794 1393810 1393798
1397604 1398627 1388000 1387827 1393793 1396248 1402394 1396112 1395233
1402922 1403920 1405290 1402967 1320530 1398698 1396083 1392668 1409131
1409154 1411251 1411776 1410874 1412331 1408807 1412417 1413338 1411302
1413269 1410786 1413572 1385085 1414212 1412557 1415612 1413649 1401482
1413567 1415683 1414541 1416768 1421025 1425093 1424266 1423453 1425900
1425285 1428096 1423583 1426958 1427064 1429629 1430825 1428794 1431220
1428632 1432786 1431217 1431957 1432152 1432733 1431905 1436492 1436738
1439637
NB_BBS_6.5.3
1386047 1383479
NB_BMR_6.5.3
1289330 1385881
NB_CLT_6.5.3
1275559 1302929 1302749 1317013 1317008 1317006 1317202 1317047 1276489
1318091 1289921 1322984 1364407 1364422 1322803 1364661 1373019 1383374
1382658 1383586 1383584 1184889 1276613 1382632 1383839 1383438 1383440
1383434 1383442 1383733 1383750 1383540 1384029 1375483 1383736 1382523
1383527 1383523 1384879 1385083 1385111 1386294 1383757 1384675 1383511
1385061 1382599 1384892 1376805 1383782 1383502 1383497 1383499 1384270
1386057 1386060 1383811 1383808 1382683 1384822 1386064 1386062 1386073
1383727 1383766 1386069 1384960 1386075 1386077 1384019 1386065 1386070
1387046 1383743 1384952 1387039 1383643 1384946 1384943 1388149 1384948
1383744 1386199 1384909 1389088 1374330 1388180 1383756 1388192 1382684
1383404 1387984 1390335 1383742 1383761 1391168 1382623 1391109 1383763
1394025 1383630 1392132 1388236 1384020 1395057 1384919 1383792 1383772
1393919 1384032 1384023 1384966 1395393 1383506 1396153 1391110 1397984
1399794 1393810 1393798 1397604 1398627 1388000 1387827 1393793 1396248
1402394 1396112 1395233 1402922 1403920 1405290 1402967 1320530 1398698
1396083 1392668 1409131 1409154 1411251 1411776 1410874 1412331 1408807
1412417 1413338 1411302 1413269 1410786 1413572 1385085 1414212 1412557
1415612 1413649 1401482 1413567 1415683 1414541 1416768 1421025 1425093

1424266 1423453 1425900 1425285 1428096 1423583 1426958 1427064 1429629
1430825 1428794 1431220 1428632 1432786 1431217 1431957 1432152 1432733
1431905 1436492 1436738 1439637
NB_DB2_6.5.3
1388132
NB_DMP_6.5.3
1384031
NB_INX_6.5.3
1404905 1416672
NB_JAV_6.5.3
1316222 1316255 1316257 1383469 1386728 1388080 1393518 1400256
NB_LOT_6.5.3
1318437
NB_LUA_6.5.3
1380529
NB_NOM_6.5.3
1383447 1384380 1390067 1391157 1391161 1395092 1399345 1409923 1409925
1423226
NB_SAP_6.5.3
1227447 1386537 1227458 1411527
NB_SMU_6.5.3
1387861 1387867
NB_SNC_6.5.3
1383582 1383429 1382596 1383498 1384025 1394039 1395089 1383512 1401373
1398467 1410597
NB_VLT_6.5.3
1383258 1385764 1386756 1385614 1386760 1386763 1386750 1396286 1402907
1404850

fixed in.
NB_6.5.3.x86, NB_6.5.3.x64, and NB_6.5.3.IA64
1250743 1275559 1289330 1302929 1282107 1302749 1317013 1317008 1317006
1317202 1317047 1276489 1318091 1318437 1289921 1319500 1322984 1361367
1364407 1364422 1322803 1364661 1373019 1383374 1382658 1383586 1383582
1383584 1184889 1276613 1382632 1383839 1383438 1383429 1383440 1383434
1383258 1383442 1383733 1384031 1383750 1383540 1382528 1384897 1384026
1375483 1383736 1382523 1383527 1383523 1384879 1385083 1385111 1386294
1383454 1383425 1383426 1384677 1383556 1383757 1384675 1385061 1383452
1382599 1382596 1384892 1376805 1382595 1383782 1383498 1383466 1383497
1386057 1385764 1386060 1383811 1383808 1382683 1386756 1385614 1384822
1386891 1386064 1386062 1386073 1383727 1384025 1382622 1383766 1386069
1384960 1382618 1386075 1386077 1383472 1383479 1385881 1384019 1386065
1384904 1386070 1387046 1383743 1384952 1387039 1383643 1388132 1384946
1384943 1388149 1384948 1383744 1388766 1384909 1389088 1388050 1388180
1227447 1383756 1388092 1388192 1388053 1388054 1388057 1388058 1388060
1388063 1386537 1382684 1383404 1387984 1383532 1383742 1383761 1391168
1386760 1393321 1386763 1391109 1383763 1394039 1394025 1383630 1392132
1386750 1388236 1384020 1395057 1384919 1383792 1383772 1393919 1384032
1384023 1384966 1395393 1383506 1396286 1227458 1396153 1391110 1397984
1396005 1391795 1393810 1393798 1397604 1395089 1398627 1399009 1388000
1387827 1383512 1397582 1393793 1396248 1402394 1396112 1401373 1402907
1403048 1395233 1402499 1403069 1402922 1403920 1405290 1402967 1398832
1404850 1320530 1398698 1396083 1408129 1392668 1409131 1409154 1410597
1410659 1411251 1410516 1411527 1411776 1410874 1412331 1412417 1413338
1411302 1413269 1410786 1413572 1385085 1414212 1412557 1402233 1415612
1414776 1413649 1401482 1413567 1415683 1416768 1415142 1416620 1415243
1421025 1425093 1424266 1423453 1412062 1382626 1425900 1425285 1428096
1423583 1426958 1427064 1429896 1429721 1429629 1430825 1428794 1431220
1428632 1431217 1431957 1432152 1432733 1431905 1436492 1436738 1439637
NB_JAV_6.5.3.x86
1316222 1316255 1316257 1383469 1386728 1388080 1400256
NB_NOM_6.5.3.x86
1383447 1384380 1390067 1391161 1395092 1399345 1409923 1409925 1423226
NB_JAV_6.5.3.IA64
1316222 1316255 1316257 1383469 1386728 1388080 1400256

in.
NB_6.5.2A
1072956 1129738 1146636 1164956 1168006 1167180 1163707 1214679 1166535
1169771 1166301 1062687 1161381 1065511 1172272 1128543 1166793 1066725
1174568 1164151 1172972 1153448 1073129 1058133 1241088 1173808 1191396
1225254 1224352 1224326 1229771 1232968 1233220 1232369 1162316 1130770
1149230 1178482 1178234 1178268 1173798 1175290 1180414 1141941 1087412
1172948 1175391 1140138 1158501 1078362 1177686 1156305 1113521 1173803
1089294 1182125 1132745 1124825 1170793 1153528 1175038 1183650 1065835
1065761 1159570 1197410 1167158 1134749 1183710 1182952 1145121 1072786
1169863 1182021 1176346 1151267 1182008 1103640 1167175 1159796 1060575
1214253 1216815 1216692 1217125 1217868 1215768 1216893 1217051 1213165
1219082 1212454 1219020 1230246 1230243 1185176 1146898 1056443 1152640
1186863 1186087 1188492 1188093 1189537 1143916 1189076 1189094 1081659
1099902 1183054 1173791 1183182 1193043 1081659 1143425 1183211 1155436
1200208 1158077 1197526 1129982 1156265 1151156 1201126 1204321 1211954
1214165 1220078 1220695 1219827 1221698 1221686 1222264 1189901 1139682
1190785 1154385 1157874 1190511 1187864 1190656 1157433 1101618 1189511
1176221 1180939 1186550 1124933 1168735 1192856 1176263 1194916 1090933
1193420 1164441 1167178 1051426 1199018 1134820 1193176 1159723 1159607
1117080 1124031 1132295 1167366 1191706 1195919 1107364 1182274 1199296
1163525 1199959 1195138 1201579 1200944 1187778 1193100 1225573 1202995
1194501 1181027 1067020 1152607 1155538 1203224 1108377 1187942 1234158
1203477 1200903 1200907 1168083 1205079 1202336 1202335 1206062 1200854
1187198 1206945 1203349 1158733 1203235 1190471 1207061 1205296 1207047
1204443 1196910 1197310 1077508 1209325 1193064 1164771 1033253 1169737
1209400 1214062 1212619 1217901 1217907 1216959 1219557 1219635 1219526
1219430 1219437 1220562 1222057 1224127 1225893 1225770 1225833 1221466
1229628 1229008 1230396 1220532 1230961 1229752 1228886 1232418 1089306
1210332 1133195 1193951 1117658 1207651 1152497 1206423 1193738 1124155
1177472 1213670 1146542 1047988 1214101 1045886 1205703 1192264 1214150
1215593 1215487 1210546 1201414 1194146 1169475 1193751 1216307 1217553
1219038 1202823 1219898 1219039 1202383 1214304 1220901 1102370 1203744
1204493 1212228 1208344 1208227 1220060 1222212 1221166 1220066 1210010
1220679 1166549 1136148 1172024 1184726 1226766 1222434 1220233 1215831
1214310 1221294 1227571 1229090 1228402 1231929 1230782 1235565 1230708
1236958 1231255 1233979 1194635 1242006 1242896 1237329 1241922 1239700
1238896 1235638 1236954 1247224 1209391 1219962 1215377 1223858 1219687
1147842 1224240 619166 1221669 1219679 1182185 1204359 1210921 1178113
1225918 1226849 1215580 1226421 1212341 1225755 1229830 1228237 1227068

1229429 1228937 1229773 1231401 1174590 1229149 1222888 1176199 1219001
1221162 1185547 1231294 1225909 1234586 1227943 1187087 1232796 1193274
1177242 1232143 1241235 1058986 1023503 1234749 1223697 1040379 1163386
1136975 1157122 1157917 1157948 1145678 1077568 1026946 1021274 1200188
1211737 1232018 1235456 1235005 1078765 1057296 1211652 1203324 1232083
1216897 1225310 1235448 1170652 1177789 1209428 1216741 1236418 1221440
1230757 1162296 1146475 1236185 1237078 1229033 1032515 1234295 1236042
1161380 1141296 1200165 1237562 1225284 1238631 1166645 1234618 1238097
1235414 1196526 1239571 1242510 1238594 1242645 1223956 1241071 1230334
1232394 1243077 1231197 1241424 1232362 1176451 1187803 1187920 1244764
1244834 1244613 1238066 1246003 1221476 1247671 1249057 1242003 1249129
1233754 1251779 1238662 1252344 1253274 1261508 1253326 1244703 1252276
1255224 1252754 1256135 1257773 1259057 1258889 1259934 1260423 1260502
1140864 1261506 1248919 1259995 1243593 1262100 1262650 1261953 1260960
1264708 1265914 1263185 1266636 1266832 1267444 1268822 1269897 1270380
1137172 1236242 1300823
NB_BBS_6.5.2
1173557 1181272 1149720 1198427 1194895 1222166
NB_BMR_6.5.2
1154522 1159519 1151769 1155166 1166346 1155438 1158002 1160488 1036244
1172180 1155550 1182144 1187111 1169652 1212629 1213218 1212201 1219749
1222715 1168789 1230522 1175887 1234202
NB_CLT_6.5.2
1072956 1129738 1146636 1164956 1168006 1167180 1163707 1214679 1166535
1169771 1166301 1062687 1161381 1065511 1168991 1172272 1128543 1166793
1066725 1174568 1164151 1172972 1153448 1073129 1174704 1058133 1241088
1173808 1191396 1225254 1224352 1224326 1229771 1232968 1233220 1232369
1162316 1130770 1103533 1149230 1178482 1178234 1178268 1173798 1175290
1180414 1141941 1087412 1172948 1175391 1140138 1158501 1078362 1177686
1156305 1113521 1173803 1089294 1182125 1132745 1124825 1170793 1153528
1175038 1183650 1065835 1065761 1159570 1197410 1167158 1134749 1183710
1182952 1145121 1072786 1169863 1182021 1176346 1151267 1182008 1103531
1103640 1167175 1159796 1060575 1214253 1216815 1216692 1217125 1217868
1215768 1216893 1217051 1213165 1219082 1212454 1219020 1230246 1230243
1185176 1146898 1056443 1152640 1186863 1181840 1186087 1188492 1188093
1189537 1143916 1189076 1189094 1081659 1099902 1183054 1173791 1183182
1193043 1081659 1143425 1183211 1155436 1200208 1158077 1197526 1129982
1156265 1151156 1201126 1204321 1211954 1214165 1220078 1220695 1219827
1221698 1221686 1222264 1189901 1139682 1190785 1154385 1157874 1190511
1187864 1190656 1157433 1101618 1189511 1176221 1184535 1125616 1180939
1186550 1124933 1168735 1192856 1176263 1194916 1090933 1193420 1164441

1167178 1051426 1199018 1134820 1193176 1159723 1159607 1117080 1124031
1132295 1167366 1191706 1195919 1107364 1182274 1199296 1163525 1199959
1195138 1201579 1200944 1187778 1193100 1225573 1202995 1194501 1181027
1067020 1152607 1155538 1203224 1108377 1187942 1234158 1203477 1200903
1200907 1168083 1205079 1202336 1202335 1206062 1200854 1187198 1206945
1203349 1158733 1203235 1190471 1207061 1205296 1207047 1204443 1196910
1197310 1077508 1209325 1193064 1164771 1033253 1169737 1040496 1106436
1209400 1214062 1212619 1217901 1217907 1216959 1219557 1219635 1219526
1219430 1219437 1220562 1222057 1224127 1225893 1225770 1225833 1221466
1229628 1229008 1230396 1220532 1230961 1229752 1228886 1232418 1089306
1210332 1133195 1193951 1117658 1207651 1152497 1206423 1193738 1124155
1177472 1213670 1146542 1047988 1214101 1045886 1205703 1192264 1214150
1215593 1215487 1210546 1201414 1194146 1169475 1193751 1216307 1217553
1219038 1202823 1219898 1214667 1219039 1202383 1214304 1220901 1102370
1203744 1204493 1212228 1208344 1208227 1220060 1222212 1221166 1220066
1210010 1220679 1166549 1136148 1172024 1184726 1226766 1222434 1220233
1215831 1214310 1221294 1227571 1229090 1228402 1231929 1230782 1235565
1230708 1236958 1231255 1233979 1194635 1242006 1242896 1237329 1241922
1239700 1238896 1235638 1236954 1247224 1209391 1219962 1215377 1223858
1219687 1147842 1224240 619166 1221669 1219679 1182185 1204359 1210921
1178113 1225918 1226849 1215580 1226421 1212341 1225755 1120744 1229830
1228237 1227068 1229429 1228937 1202564 1204202 1229773 1231401 1174590
1229149 1222888 1176199 1219001 1221162 1185547 1231294 1225909 1234586
1227943 1187087 1232796 1193274 1177242 1232143 1241235 1058986 1023503
1234749 1223697 1040379 1163386 1136975 1157122 1157917 1157948 1145678
1077568 1026946 1021274 1200188 1211737 1232018 1235456 1235005 1078765
1057296 1211652 1203324 1232083 1216897 1225310 1235448 1170652 1177789
1209428 1216741 1236418 1221440 1230757 1162296 1146475 1236185 1237078
1229033 1032515 1234295 1236042 1161380 1141296 1200165 1237562 1225284
1238631 1166645 1234618 1238097 1235414 1239470 1196526 1239571 1242510
1238594 1242645 1223956 1241071 1230334 1232394 1243077 1231197 1241424
1232362 1176451 1187803 1187920 1244764 1244834 1244613 1238066 1246003
1221476 1247671 1249057 1242003 1249129 1233754 1251779 1238662 1252344
1253274 1261508 1253326 1244703 1252276 1255224 1252754 1256135 1257773
1259057 1258889 1259934 1260423 1260502 1140864 1243842 1126851 1209489
1212487 1221708 1250578 1261506 1248919 1259995 1243593 1262100 1262650
1261953 1260960 1264708 1265914 1263185 1266636 1266832 1267444 1268822
1269897 1270380 1137172 1236242 1300823
NB_DB2_6.5.2
1155324
NB_DMP_6.5.2
1173820 1177807 1181277 1194321 1040426 1135507 1199176 1121284 1207588

1210256 1235516 1237147 1254599
NB_ENC_6.5.2
1238097
NB_INX_6.5.2
1098013
NB_JAV_6.5.2
1166299 1168612 1127780 1173718 1124806 1180766 1145815 1166891 1076281
1045745 1066828 1189501 1115059 1084397 1132128 1177115 1189940 1189972
1180994 1195877 1195901 1183882 1195900 1199217 1178657 1196449 1198943
1201553 1199636 1196047 1111754 1202596 1212368 1196046 1219958 1209200
1214798 1214237 1221478 1223376 1153970 1206951 1118686 1223528 1225696
1225811 1228952 1181044 1232612 1190114 1236368 1155281 1179943 1210565
1156185 1186141 1135472 1243499 1228986 1249027 1235952 1251838 1254388
NB_LOT_6.5.2
1136703 1170011 1130971 1218582
NB_LUA_6.5.2
1053371
NB_NOM_6.5.2
1192883 793178 1165266 1098900 1068620 1074452 1187013 1170294 1135355
1151560 1166243 1169437 1054146 1012739 856167 1076567 1056238 1165377
1142255 1182652 1141630 1057217 1077458 1189474 1195661 1150465 1195939
1215410 1200480 1203068 1216709 1227902 1228873 1228917 1226611 429738
1233705 1233747 1225589 1232303 1231543 1238294 1223648 1239519 1053287
1240882 1244352 1241644 1247717 1250623 1256155
NB_ORA_6.5.2
1147006 1095138 1184020 1191845 1191846 1226882 1224665
NB_SAP_6.5.2
1197116 1209708 1227451 1210595
NB_SMU_6.5.2
1157025 1203304
NB_SNC_6.5.2 1145586 1145594 1133233 1159854 1060690 1166832 1044960
1155989 1183172 1179761 1157755 1187873 1204223 1256335 1152594 1210310
1214175 1218190 1030014 1207567 1156481 1213477 1163682 1218119 1201829
1139069 1177166 1213181 1223179 1210888 1225245 1220718 1192304 1118213
1226750 1146081 1173028 1225238 1222678 1229151 1217389 1231519 1232298

1232066 1152586 1235849 1166821 1236420 1186143 1186138 1238430 1210196
1214026 1234643 1238676 1239448 1240634 1241827 1240218 1247251 1247235
1194934 1248984 1242524 1252321 1254469 1259531 1264207 1275543
NB_SYB_6.5.2
1098013 1115047
NB_VLT_6.5.2
1051251 1169328 1168695 1160349 1169334 1166280 1238368 1252124 1255013
1255686 1265091

fixed in.
NB_6.5.2A.x86, NB_6.5.2A.x64, and NB_6.5.2A.IA64
1072956 1129738 1145586 1145594 1146636 1154522 1167180 1163707 1214679
1145852 1098013 1133233 1166535 1115047 1159519 1151769 1155166 1166346
1155438 1158002 1036244 1159854 1169771 1142841 1171272 1176171 1182932
1166301 1062687 1161381 1098014 1099893 1128543 1166793 1172180 1066725
1174568 1170920 1172972 1174802 1153448 1073129 1155324 1058133 1241088
1173808 1191396 1225254 1224352 1224326 1229771 1232968 1233220 1232369
1168616 1166832 1095138 1173820 1177807 1155550 1162316 1130770 1149230
1178482 1178234 1178268 1166474 1133188 1180046 1173798 1175290 1180414
1141941 1087412 1172948 1175391 1140138 1167566 1158501 1078362 1177686
1156305 1113521 1089294 1182125 1132745 1124825 1170793 1161167 1179466
1153528 1182144 1170142 1175038 1183776 1183650 1065835 1065761 1167158
1134749 1183710 1182952 1145121 1072786 1044960 1169863 1182021 1176346
1151267 1155989 1181277 1185676 1103640 1159796 1060575 1214253 1216815
1216692 1217125 1217868 1215768 1216893 1217051 1213165 1219082 1212454
1219020 1230246 1230243 1187111 1146898 1056443 1152640 1186863 1181840
1052487 1186087 1188492 1188093 1189537 1143916 1189076 1189094 1081659
1099902 1183054 1173791 1183182 1193043 1081659 1143425 1183211 1155436
1200208 1158077 1197526 1129982 1156265 1151156 1201126 1204321 1211954
1214165 1220078 1220695 1219827 1221698 1221686 1222264 1189901 1175422
1190785 1154385 1190511 1187864 1190656 1157433 1101618 1189511 1187936
1175411 1176221 1184535 1125616 1180939 1138554 1186550 1124933 1178659
1180937 1182781 1168735 1175242 1132129 1189969 1094237 1176263 1157755
1194916 1090933 1193420 1164441 1167178 1051426 1199018 1134820 1193176
1159723 1159607 1117080 1124031 1132295 1185170 1167366 1191706 1136909
1195919 1107364 1182274 1199296 1180078 1195890 1189937 1051251 1195887
1187873 1190419 1079570 1199959 1129425 1198131 1195138 1198015 1200607

1040426 1135507 1040206 1201579 1184226 1195883 1200944 1187778 1193100
1225573 1169328 1199176 1194501 1181027 1178654 1194709 1261091 1111752
1201601 1136703 1024707 1170011 1130971 1067020 1152607 1155538 1203224
1108377 1156352 1152594 1187942 1234158 1203477 1200903 1200907 1168083
1205079 1202336 1111573 1200280 1167164 1151002 1218472 1175338 1197050
1211131 1221288 1202335 1188188 1194895 1206062 1200854 1187198 1206945
1203349 1158733 1203235 1190471 1207092 1197116 1207061 1205296 1137242
1133191 1207047 1204443 1077508 1209325 1193064 1164771 1033253 1169737
1176684 1209040 1040496 1106436 1209400 1214062 1212619 1217901 1217907
1216959 1219557 1219635 1219526 1219430 1219437 1220562 1222057 1224127
1225893 1225770 1225833 1221466 1229628 1229008 1230396 1220532 1230961
1229752 1228886 1232418 1088494 1210316 1235036 1242051 1252575 1089306
1210332 1133195 1202577 1225402 1193951 1117658 1207651 1152497 1063913
1192391 1206423 1168695 1160349 1172850 1193738 1124155 1210310 1213388
1004177 1177472 1146542 1047988 1214101 1045886 1064998 1212629 1213218
1205703 1192264 1213680 1215593 1169334 1208640 1210546 1201414 1184020
1191845 1191846 1194146 1166280 1169475 1197511 1193751 1218582 1219038
1202823 1219898 1214667 1219749 1205925 1202383 1214304 1220901 1102370
1203744 1218203 1141152 1204493 1212228 1208344 1218480 1221519 1207567
1220060 1222212 1156481 1213477 1221166 1209349 1215046 1218209 1220066
1210010 1220679 1166549 1136148 1222844 1172024 1184726 1226766 1218119
1222434 1220233 1215831 1214310 1221294 1227571 1229090 1228402 1231929
1230782 1235565 1230708 1236958 1231255 1233979 1194635 1242006 1242896
1237329 1241922 1239700 1238896 1235638 1236954 1247224 1209391 1174883
1219962 1215377 1223858 1219687 1147842 1222715 1214420 1139069 1224240
1177166 1213181 1223179 619166 1221669 1219679 1169708 1182185 1225245
1163684 1220718 1192304 1223291 1224977 1225173 1204359 1118213 1119147
1210921 1226750 1178113 1226641 1160472 1226873 1159436 1201372 1225918
1226849 1173028 1215580 1226421 1212341 1216729 1205260 1168789 1225755
1137182 1226337 1208589 1229151 1229830 1228237 1226694 1229249 1226399
1227068 1138299 1229429 1218482 1217389 1230522 1229773 1231519 1231931
1174590 1229149 1222888 1232059 1176199 1121284 1232262 1219001 1221162
1185547 1231294 1225909 1234586 1207588 1227943 1232066 1133697 1210256
1231464 1208497 1223132 1202664 1232796 1144788 1174296 1193274 1152586
1213025 1177242 1232143 1241235 1224543 1058986 1223122 1228953 1023503
1235354 1234749 1175887 1234202 1223697 1040379 1163386 1136975 1157122
1157917 1157948 1145678 1077568 1026946 1021274 1200188 1211737 1232018
1235456 1235516 1221244 1235005 1078765 1057296 1211652 1203324 1232083
1235593 1235028 1212982 1216897 1235883 1225310 1235497 1235448 1170652
1235849 1177789 1209428 1216741 1236418 1169611 1179933 1236420 1218489
1218488 1026957 1226882 1221440 1236386 1230757 1162296 1146475 1236185
1224665 1237078 1233474 1229033 1032515 1186143 1234295 1236042 1227842
1232787 1107989 1186138 1161380 1053371 1141296 1200165 1165193 1186143

1187875 1228995 1238368 1237562 1225284 1238631 1237076 1238430 1214026
1166645 1234618 1237147 1229244 1228974 1239448 1235414 1196526 1209708
1227451 1240634 1210595 1239571 1241827 1242510 1240218 1238594 1242645
1223956 1241071 1230334 1232394 1243077 1231197 1241424 1232362 1166457
1176451 1187803 1187920 1244764 1244834 1244613 1238066 1246003 1194934
1247241 1221476 1245528 1247671 1247609 1233823 1248519 1242003 1248635
1249374 1250773 1249129 1233754 1251779 1238662 1252124 1252344 1253274
1261508 1253326 1248077 1244703 1252276 1255224 1255013 1252754 1254437
1255686 1251972 1254599 1216714 1256135 1257773 1250942 1259057 1258889
1258450 1259934 1260423 1260502 1140864 1243842 1126851 1209489 1212487
1221708 1250578 1257543 1261506 1248919 1261095 1259995 1250926 1262100
1262650 1261953 1260960 1264207 1264708 1261916 1265914 1263185 1266636
1265091 1266832 1267444 1268822 1269897 1270380 1270499 1098013 1275543
1236242 1300823
NB_JAV_6.5.2.x86
1166299 1168612 1127780 1173718 1124806 1180766 1145815 1166891 1076281
1045745 1066828 1189501 1115059 1084397 1132128 1177115 1189940 1189972
1180994 1195877 1195901 1183882 1195900 1199217 1178657 1196449 1198943
1201553 1199636 1196047 1111754 1202596 1212368 1196046 1212402 1219958
1209200 1214798 1214237 1221478 1223376 1153970 1206951 1118686 1223528
1225696 1225811 1228952 1181044 1232612 1190114 1236368 1155281 1179943
1210565 1156185 1186141 1135472 1243499 1228986 1249027 1235952 1251838
1254388
NB_JAV_6.5.2.IA64
1166299 1168612 1127780 1173718 1124806 1180766 1145815 1166891 1076281
1045745 1066828 1189501 1115059 1084397 1132128 1177115 1189940 1189972
1180994 1195877 1195901 1183882 1195900 1199217 1178657 1196449 1198943
1201553 1199636 1196047 1111754 1202596 1212368 1196046 1212402 1219958
1209200 1214798 1214237 1221478 1223376 1153970 1206951 1118686 1223528
1225696 1225811 1228952 1181044 1232612 1190114 1236368 1155281 1179943
1210565 1156185 1186141 1135472 1243499 1228986 1249027 1235952 1251838
1254388
NB_NOM_6.5.2.x86
793178 1165266 1098900 1068620 1074452 1187013 1170294 1135355 1151560
1166243 1169437 1054146 1012739 856167 1076567 1056238 1165377 1142255
1182652 1141630 1057217 1077458 1189474 1195661 1150465 1195939 1215410
1200480 1222109 1203068 1216709 1227902 1228873 1228917 1226611 429738
1233705 1233747 1225589 1232303 1231543 1238294 1223648 1239519 1053287
1240882 1244352 1241644 1247717 1250623 1256155

in.
NB_6.5.1
1081404 1082281 1081354 1081698 1077267 1089270 1095231 1088607 1084993
1060897 1088606 1100978 1118302 1079723 1090571 1084947 1088608 1111471
866629 1039048 1041354 1046330 1050492 1076912 1096261 1003906 1088607
1094608 1100617 1059862 1098378 1047276 1061031 1100839 1070220 1005055
1100685 1100697 1056259 1104423 1080484 1100881 1077695 1096284 1102886
1072317 1110605 1077693 1102521 1094558 1102639 1093595 1103786 1103600
1105269 1088609 1053712 1106710 1050155 1111547 1112392 1099020 1096195
1109567 1099115 1101044 1102615 1085060 1106918 1094270 1098815 1082399
1052425 1076085 1109705 1098718 1091111 1065773 1102710 1082277 1109757
1098045 1082109 1016904 997644 1081452 1086598 1106385 1095098 1073905
1122374 1122139 1110736 1112256 1121427 1117637 1106502 1125017 1119165
1119910 1128110 1123618 1125795 1130490 1126033 1090463 1087571 1129917
1132942 1130566 1133603 1107693 1128957 861231 1062790 1059880 1128914
1136472 1134253 1148528 1130915 1131223 1137735 1138740 1079753 1134817
1137031 1141201 1138126 1100611 1124780 1128031 1137782 1133931 1138854
1131287 1139765 1137270 1140241 1139982 1136304 1141863 1109608 1141191
1141195 1144319 1141844 1139701 1145202 1139621 1117736 1146745 1130840
1146673 1145768 1145871 1145731 1140439 1147391 1146512 1149222 1149164
1150310 1140798 1150834 1143453 1152707 1154516 1153517 1133898 1155366
1155556 1155361 1151172 1152716 1153439 1159304 1145768 1141469 1161183
1160463 1158609 1159821 1163509 1163509 1149056 1163626 1162837 1162890
1163390 1167359 1169734
NB_BBS_6.5.1
1103616 1113799 1128742 1134156 1094481 1159236 1157014
NB_BMR_6.5.1
1065640 596414 1052364 1100827 1094236 1100179 1039434 1116060 1094235
1109595 1115945 1119045 1125002 1131127 1143101 1148419 1161249
NB_CLT_6.5.1
1081404 1082281 1081354 1081698 1077267 1088572 1090440 1089270 1095231
1088607 1084993 1060897 1088606 1100978 1118302 1079723 1090571 1084947
1088608 1111471 866629 1039048 1041354 1046330 1050492 1076912 1096261
1003906 1088607 1094608 1100617 1059862 1098378 1047276 1061031 1100839
1070220 1005055 1100685 1100697 1056259 1104423 1080484 1100881 1077695
1096284 1102886 1072317 1110605 1077693 1102521 1094558 1102639 1093595
1103786 1103600 1105269 1088609 1053712 1106710 1050155 1111547 1112392

1098348 1099020 1096195 1109567 1099115 1101044 1102615 1085060 1106918
1094270 1098815 1082399 1052425 1076085 1109705 1098718 1091111 1065773
1045014 1102710 1082277 1109757 1098045 1082109 1029153 1016904 997644
1081452 1086598 1106385 1095098 1073905 1122374 1122139 1110736 1112256
1121427 1117637 1106502 1125017 1119165 1119910 1128110 1123618 1125795
1130490 1126033 1090463 1087571 1129917 1132942 1130566 1133603 1107693
1128957 861231 1062790 1059880 1128914 1136472 1134253 1148528 1130915
1131223 1137735 1138740 1079753 1134817 1137031 1141201 1138126 1100611
1124780 1128031 1137782 1133931 1138854 1131287 1139765 1137270 1140241
1139982 1136304 1141863 1109608 1141191 1141195 1144319 1141844 1139701
1145202 1139621 1117736 1146745 1130840 1146673 1145768 1145871 1145731
1140439 1147391 1132124 1132117 1146512 1149222 1149164 1150310 1140798
1150834 1143453 1152707 1154516 1153517 1133898 1155366 1155361 1151172
1152716 1153439 1159304 1145768 1141469 1161183 1160463 1158609 1159821
1163509 1163509 1149056 1163626 1162837 1162890 1163390 1167359 1169734
NB_DB2_6.5.1
1144481
NB_DMP_6.5.1
1103810 1111636 1162160
NB_INX_6.5.1
1082844
NB_JAV_6.5.1
1105102 1065536 1055292 1105104 1113359 1114102 1059702 1120612 1137009
1137032 1140441 1147300 1158537 1160278
NB_LOT_6.5.1
1095196
NB_NOM_6.5.1
1100710 1098781 1095853 1083394 1098788 1098847 1073938 1136119 1144826
1142365 1150537 1156043 1157674
NB_ORA_6.5.1
1082844
NB_SAP_6.5.1
1082844
NB_SMC_6.5.1
1078641
NB_SMU_6.5.1
1094368 1114250
NB_SNC_6.5.1
1096262 1079310 1007413 1107363 704750 1072303 1116293 1090596 1064773
936750 1122064 1116285 1122849 1121101 1132427 1133892 1136035 1133808
1127683 1127743 1137975 1137994 1137972 1142794 1139792 1150153 1145951
1141888 1149082 1151817 1139712
NB_SYB_6.5.1
1082844
NB_VLT_6.5.1
1079108 1104856 1080001 1078416 1139463

fixed in.
NB_6.5.1.x86, NB_6.5.1.x64, and NB_6.5.1.IA64
1080505 1065640 960689 1081404 1082281 1081354 770558 1081698 1077267
1035399 1051387 1072077 798210 1088471 1089270 1094533 1095231 596414
1052364 1088607 1084993 1060897 1088606 1100978 1118302 1079723 1090571
1084947 1096262 1088608 1111471 996779 866629 1100827 1039048 1041354
1046330 1050492 1076912 1096261 1003906 1088607 1094608 1100617 1102574
1059862 1098378 1094236 1047276 1061031 1090451 1079108 1070220 1104856
1005055 1100685 1100697 1056259 1104423 1080484 1103810 1068028 1079531
1118300 1077695 1092075 1096284 1102886 1072317 1110605 1077693 1100179
1102521 1094558 1039434 1093595 1103786 1103600 1105269 1088609 1053712
1107363 1111552 1111552 1072056 1106710 1079770 1098022 1050155 1111547
1112392 1099020 1095196 1096195 1109567 1099115 1101044 1102615 1116060
1085060 1090596 1082844 1106918 1094270 1098815 1088610 1082399 1094235
1080001 1052425 1076085 1065442 1109705 1098718 1078416 1091111 1109595
1065773 1090656 1064773 1082277 1098045 1115945 1082109 1047963 1119045
1109693 1016904 997644 1081452 1095687 1086598 1106385 1095098 1122374
1122139 1116285 1110736 1112256 1122849 1121427 1117637 1106502 1100849
1103373 1100855 1100858 1121486 1107986 1129433 1125017 1122725 1119165
1121234 1070786 1128110 1125795 1125002 1130490 1126033 1090463 1120589
1087571 1129917 1132942 1132427 1129806 1132824 1130566 1134691 1133181
1129495 1111756 1133292 1133603 1107693 1135522 1128957 1131628 1135746
1107991 1059880 1128914 1136430 1133892 1136472 1134253 1148528 1133802
1107991 1134452 1098396 1133019 1137857 1078416 1137735 1138740 1079753

1134817 1137031 1141201 1127683 1138126 1127743 1138508 1100611 1139463
1124780 1128031 1133931 1137975 1134673 1137994 1130488 1132117 1133263
1138854 1131287 1139765 1137270 1140217 1141819 1088611 1127676 1140241
1136304 1141863 1109608 1142794 1141191 1141195 1139394 1117349 1144319
1141844 1140803 1139701 1145202 1143244 1139621 1133928 865299 1146745
1139792 1130840 1137029 1146673 1145768 1145871 1145731 1140439 1147391
1148419 1132124 1132117 1146512 1149859 1150153 1149222 1141789 1150310
1150728 1145951 1141888 1134832 1146023 1140798 1150834 1151817 1143453
1152707 1154516 1153517 1133898 1155366 1154737 1155556 1155361 1155331
1139712 1152716 1153439 1144481 1154523 1156644 1141896 1157934 1159304
1158479 1159765 1158698 1145768 1141469 1143302 1158550 1157679 1147544
1157980 1082844 1082844 1082844 1160463 1158208 1162267 1158609 1159821
1162160 1163509 1161441 1163509 1149056 1163626 1162837 1162890 1163390
1144017 1165653 1167359 1169734 1169707
NB_JAV_6.5.1.x86
1105102 1065536 1055292 1105104 1113359 1114102 1059702 1120612 1137009
1137032 1140441 1147300 1158537 1160278
NB_NOM_6.5.1.x86
1100710 1098781 1095853 1083394 1098788 1098847 1073938 1136119 1144826
1142365 1150537 1156043 1157674
NB_JAV_6.5.1.IA64
1105102 1065536 1055292 1105104 1113359 1114102 1059702 1120612 1137009
1137032 1140441 1147300 1158537 1160278

341279

Uploaded by

Document Information

Original Description:

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

341279

Uploaded by

Copyright:

Available Formats

Veritas NetBackup™ 6.5.

UNIX, Windows, and Linux

Documentation version: 6.5.6

Contacting Technical Support

Licensing and registration

Asia-Pacific and Japan customercare_apac@symantec.com

Europe, Middle-East, and Africa semea@symantec.com

North America and Latin America supportsolutions@symantec.com

Additional enterprise services

Technical Support ............................................................................................... 4

Chapter 2 About known issues ............................................................ 17

Windows-specific issues ................................................................ 58

Chapter 3 Current release content index .......................................... 61

Chapter 4 Current release content ..................................................... 69

Appendix A About NetBackup release history ................................... 159

NetBackup 6.5.4 UNIX packaged Etracks ................................... 162

■ About new supported platforms for NetBackup 6.5.6

■ About new feature and enhancements for NetBackup 6.5.6

■ About end-of-life notifications for NetBackup 6.5.6

About new supported platforms for NetBackup 6.5.6

■ Windows Server 2008 R2 Core (Client Support)

About new feature and enhancements for NetBackup

Decommissioning a media server

About the VSP disable tool

About the catalog recovery synchronization tool

About name resolution and firewall configuration upgrades

About status 800 job status enhancements

About NetBackup command line interface updates

About the new multistream_restore parameter

UNIX or Linux http://entsupport.symantec.com/docs/340909

About NetBackup support utilities

About end-of-life notifications for NetBackup 6.5.6

■ About platform-specific issues

■ Installation, upgrade, and cluster issues

■ NetBackup Access Control issues

■ NetBackup Database Agent issues

■ NetBackup user interface issues

■ General NetBackup issues

■ NetBackup Hyper-V issues

■ Bare Metal Restore (BMR) issues

■ NetBackup Operations Manager (NOM) issues

■ General Documentation issues

About platform-specific issues

V-125-380 /var/tmp/bmrmediaDb1K6p/.discinfo(2): expected "Red Hat

Installation, upgrade, and cluster issues

continue with the NetBackup removal. PBX is stopped and restarted

■ (ET1991719) A Windows computer would not come up after a disaster recovery

■ Enter the following command to take the NetBackup resource offline:

■ Enter the following command to take the NetBackup group offline:

■ Enter the following command to change the VCS configuration to R/W

■ Enter the following command to delete the NetBackup group:

■ Enter the following command to delete the NetBackup resource type:

■ Uninstall NetBackup from all other nodes in the cluster.

■ (ET2003460) Support for FlashBackup in a Microsoft Cluster (MSCS)

■ During a Windows server or client installation, if there you encounter a fatal

■ (ET1917617) The database creation failed on an HP 11.31 IA64 system.

NetBackup Access Control issues

■ If the error code is 0 you can ignore this issue altogether.

■ (ET1274335) Applicability: Cluster NetBackup with NBAC (Clustered VxAT)

NetBackup Database Agent issues

NetBackup Enterprise Vault Agent issues

To work around this issue, create the enterprise vault install

■ (ET1475102) If you install the Enterprise Vault Agent on a NetBackup client