341279

Veritas NetBackup™ 6.5.6Release Notes

UNIX, Windows, and Linux

NetBackup 6.5.6

Veritas NetBackup 6.5.6 Release NotesThe software described in this book is furnished under a license agreement andmay be usedonly in accordance with the terms of the agreement.

Documentation version: 6.5.6

Legal NoticeCopyright © 2010 Symantec Corporation. All rights reserved.

Symantec, the Symantec Logo, and Veritas are trademarks or registered trademarks ofSymantec Corporation or its affiliates in the U.S. and other countries. Other names may betrademarks 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 documentmay be reproduced in any form by any means without prior written authorization ofSymantec Corporation and its licensors, if any.

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

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

Symantec Corporation350 Ellis StreetMountain View, CA 94043

http://www.symantec.com

http://www.symantec.com

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

Symantec’s support offerings include the following:

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

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

■ Upgrade assurance that delivers software upgrades

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

■ Premium service offerings that include Account Management Services

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

www.symantec.com/business/support/

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

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


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

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

■ Product release level



■ Hardware information

■ Available memory, disk space, and NIC information

■ Operating system

■ Version and patch level

■ Network topology

■ Router, gateway, and IP address information

■ Problem description:

■ Error messages and log files

■ Troubleshooting that was performed before contacting Symantec

■ Recent software configuration changes and network changes

Licensing and registrationIf yourSymantecproduct requires registrationor a licensekey, access our technicalsupport web page at the following URL:


Customer serviceCustomer service information is available at the following URL:


Customer Service is available to assist with non-technical questions, such as thefollowing types of issues:

■ Questions regarding product licensing or serialization

■ Product registration updates, such as address or name changes

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

■ Latest information about product updates and upgrades

■ Information about upgrade assurance and support contracts

■ Information about the Symantec Buying Programs

■ Advice about Symantec's technical support options

■ Nontechnical presales questions

■ Issues that are related to CD-ROMs or manuals



Support agreement resourcesIf youwant to contact Symantec regarding an existing support agreement, pleasecontact the support agreement administration team for your region as follows:

[email protected] and Japan

[email protected], Middle-East, and Africa

[email protected] America and Latin America

Additional enterprise servicesSymantec offers a comprehensive set of services that allow you tomaximize yourinvestment in Symantec products and to develop your knowledge, expertise, andglobal insight, which enable you to manage your business risks proactively.

Enterprise services that are available include the following:

Managed Services remove the burden of managing and monitoring securitydevices and events, ensuring rapid response to real threats.

Managed Services

Symantec Consulting Services provide on-site technical expertise fromSymantec and its trustedpartners. SymantecConsultingServices offer a varietyof prepackaged and customizable options that include assessment, design,implementation,monitoring, andmanagement capabilities. Each is focused onestablishing andmaintaining the integrity and availability of your IT resources.

Consulting Services

EducationServices provide a full array of technical training, security education,security certification, and awareness communication programs.

Education Services

To access more information about enterprise services, please visit our web siteat the following URL:

www.symantec.com/business/services/

Select your country or language from the site index.

mailto:[email protected]



www.symantec.com/business/services/

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

Chapter 1 About NetBackup 6.5.6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

About new supported platforms for NetBackup 6.5.6 ... . . . . . . . . . . . . . . . . . . . . . . . 11About new feature and enhancements for NetBackup 6.5.6 ... . . . . . . . . . . . . . . . 12

Decommissioning a media server ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12About the VSP disable tool ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12About the catalog recovery synchronization tool ... . . . . . . . . . . . . . . . . . . . . . . 13About name resolution and firewall configuration upgrades ... . . . . . . . 13About status 800 job status enhancements ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14About NetBackup command line interface updates ... . . . . . . . . . . . . . . . . . . . . 14About the new multistream_restore parameter ... . . . . . . . . . . . . . . . . . . . . . . . . . 14About 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 ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17Installation, upgrade, and cluster issues ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18NetBackup Access Control issues ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22NetBackup Database Agent issues ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

NetBackup Enterprise Vault Agent issues ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23Exchange Granular Recovery issues ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24Microsoft Exchange Agent issues ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25SharePoint Agent issues ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27NetBackup for SQLserver agent issues ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30Other database agent issues ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

Storage-related issues ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30NetBackup user interface issues ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35General NetBackup issues ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36NetBackup Hyper-V issues ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46Bare Metal Restore (BMR) issues ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51NetBackup Operations Manager (NOM) issues ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52Localization issues ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53General Documentation issues ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53UNIX-specific issues ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

Contents

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

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

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

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

About Release Update conventions .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69About NetBackup 6.5.6 Release Content ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70

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

About previous NetBackup releases ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159Master Etrack Index for all previous releases ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160

NetBackup 6.5.5 packaged Etracks for UNIX and Windows .... . . . . . . . 160

Contents8

NetBackup 6.5.4 UNIX packaged Etracks ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162NetBackup 6.5.4 Windows packaged Etracks ... . . . . . . . . . . . . . . . . . . . . . . . . . . . 167NetBackup 6.5.3 UNIX packaged Etracks ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169NetBackup 6.5.3 Windows packaged Etracks ... . . . . . . . . . . . . . . . . . . . . . . . . . . . 172NetBackup 6.5.2 UNIX packaged Etracks ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173NetBackup 6.5.2 Windows packaged Etracks ... . . . . . . . . . . . . . . . . . . . . . . . . . . . 177NetBackup 6.5.1 UNIX packaged Etracks ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180NetBackup 6.5.1 Windows packaged Etracks ... . . . . . . . . . . . . . . . . . . . . . . . . . . . 182

9Contents

Contents10

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.6This topic describes the newUNIX andWindows platform being supported in theNetBackup 6.5.6 release.

For additional platform support information, see the following Technote on theSymantec Support Web site:

http://entsupport.symantec.com/docs/303344

The following is a comprehensive list of the new UNIX and Windows platformscontained 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_SnapFIM, the EMC_Timefinder_Clone FIM, and the EMC_Timefinder_Mirror FIMon Solaris 9 and 10 platforms and the HP-UX 11.31 platform.

■ This release contains a JRE upgrade for NOM.

1Chapter

About new feature and enhancements forNetBackup6.5.6

The following sections describe the NetBackup feature and enhancements thatcomprise this release.

Formoredetailed information about these features, see theNetBackupDocumentUpdates book. You can use the following Technote to locate this book on theSymantec Support Web site.


For this release, updates were made to theNetBackup Troubleshooting Guide andtheTroubleshootingWizard. Anew set of status code descriptions has been addedto 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. Thatenables administrators to more easily troubleshoot allocation problems.

You can find the latest version of the NetBackup Troubleshooting Guide in thefollowing Technote on the Symantec Support Web site.


Decommissioning a media serverNew with this release is a command to decommission a mediaserver,nbdecommission. The command launches a text-based wizard that guidesyou through the decommission process. The wizard removes the references to amedia server from a NetBackup domain.

See the following Technote on the Symantec Support Web site for moreinformation about this feature:


About the VSP disable toolNetBackup 6.5.6 automatically installs the Veritas volume snapshot Provider(VSP)method for Open File Backups. VSP is the default Open File Backupmethodin this release.

NetBackup 6.5.6 includes the VSP disable tool (bpvspdisable.exe) foradministrators to use to disable VSP on clients if it is not needed. The tool deletesthe VSP cache files from the disk of the client system. All future VSP requests onthose clients are redirected to useMicrosoft native Volume Shadow Copy Service(VSS).

About NetBackup 6.5.6About new feature and enhancements for NetBackup 6.5.6

12

TheVSPmethod forOpen File Backups is not supported inNetBackup 7.0. Havingrun 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 toolThe nbcatsync command runs a utility that resyncs the disk media IDs in theimage catalog after catalog recovery operations complete.

After bprecover restores the actual catalog files, the nbcatsync utility can do thefollowing:

■ 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 currentlyconfigured disk volumes. The -prune_catalog option deletes catalog entriesfor the images that do not exist locally.

■ Constrain the operation to a set of images based on the catalog restore thatwas performed.



About name resolution and firewall configuration upgradesThe bptestnetconn command has been added to more effectively troubleshootnetworking errors such as status code 58 errors, Cannot connect to client. Thiscommandperforms several tasks thathelp youanalyzeDNSconnectivity problemswith any specified list of hosts, including the server list in the NetBackupconfiguration. To help troubleshoot connectivity problems between the servicesthat use CORBA communications, bptestnetconn can perform and report on

13About NetBackup 6.5.6About new feature and enhancements for NetBackup 6.5.6

CORBA connections to named services. It sends VxUL log messages to OID 112for easy perusal. The vxlogcfg command controls the log verbosity.

About status 800 job status enhancementsIn NetBackup 6.5.x, jobs that fail at resource allocation time are often assigned astatus 800 (RESOURCE UNAVAILABLE) job status. There aremanyunderlying reasonsthat cause allocations for these jobs to fail. A set ofmore granular and descriptivestatus codes (2000-2104) were included to disambiguate the status code 800 jobstatus. These new error code descriptions enable the NetBackup administrator totroubleshoot allocation problems more easily.

About NetBackup command line interface updatesThis release contains updates to the following commands that you can run usingthe command line interface:

■ bptestnetconn

■ bpimage

■ bplist

■ bprecover

■ bprestore

■ nbcatsync

■ NBCC

■ NBCCR

■ nbdecommission

■ nbdna

■ nbemmcmd

■ nbsu

About the new multistream_restore parameterThemultistream_restore parameter is newwithNetBackup 6.5.6. This parameteris supported for Oracle without RMAN.

For more information, see the following:

http://entsupport.symantec.com/docs/340908Windows

About NetBackup 6.5.6About new feature and enhancements for NetBackup 6.5.6

14


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

About NetBackup support utilitiesNetBackup 6.5.6 includes three support utilities: nbsu, NBCC, and NBCCR. Thefollowing list summarizes the enhancements that have been made to each utilityin this release:

■ NetBackup Support Utility (NBSU)The NBSU utility assists you in gathering NetBackup and operating systemdiagnostic information. This tool queries the host onwhich it runs and gathersdiagnostic information aboutNetBackupand the operating system. In addition,it provides a wide range of control over the types of diagnostic informationgathered. For instance, you can obtain information about NetBackupconfiguration settings about troubleshooting areas, or about NetBackup ormedia management job status codes.

In NetBackup 6.5.6 this utility has been enhanced to version 1.3 and includesthe following new features:

■ New commands line options have been added.

■ Enhancements weremade to the SLP, EMM, and versioninfo diagnostics.

■ This utility is now available for the Mac OS X platform.

In addition to thenewenhancements, the support and support.exediagnosticinformation gathering utilities are no longer included or supported beginningwith this release of NetBackup.

■ NBCC utilityThe NBCC utility uses the output from various OS and NetBackup commandsto analyze the consistency state of theNetBackupconfiguration. It also analyzesthe consistency state of NetBackup databases and catalogs as they relate totape media. If inconsistencies are detected, NBCC consolidates, and packagesthe resulting data into a bundle that can be sent to Symantec Tech Supportfor analysis.This release contains the 7.0 version of this utility. In addition, enhancementshave been made to this utility to ensure that it supports NetBackup 6.5.6.

■ NBCCR utilityThe NBCCR utility processes database and catalog repair actions as defined ina file that you cangenerate under the guidance of SymantecTechnical Support.This file is created as part of the analysis of the data that the NBCC utilitycollects and any site-specific situations.This release contains the 7.0 version of this utility. In addition, enhancementshave been made to this utility to ensure that it supports NetBackup 6.5.6.

15About NetBackup 6.5.6About new feature and enhancements for NetBackup 6.5.6


About end-of-life notifications for NetBackup 6.5.6This release of NetBackup contains no new end-of-life announcements.

About NetBackup 6.5.6About end-of-life notifications for NetBackup 6.5.6

16

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

2Chapter

■ 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++ RuntimeEnvironment Component for AIX. Symantec recommends that you downloadand install the latest C++ run-time library and then reboot your server. Formore information about this issue and fix, refer to the following Technote onthe Symantec Support Web site.http://entsupport.symantec.com/docs/292450

■ (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 thefollowing:

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 operatingsystem media to create a shared resource tree (SRT). You can use SRTs torestore an RHEL5.3 client. A second workaround for this issue: On the BMRBoot server, open the/usr/openv/var/global/createsrt.conf file and searchfor the string,RedHatEnterpriseLinuxServer5. Replace all the occurrencesof 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 newdevice drivers that were not a part of thedefault kernel inRHEL5.2, Symantec recommends that youuse thisworkaroundto create a RHEL5.3 SRT for restoring RHEL5.3 clients.

Installation, upgrade, and cluster issues■ (ET1890392) The NetBackup 6.5.5 install may hang if the following is true:

■ The $PATHvariable is set to use the cp command fromGNUcoreutils version7.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 laterWhen you remove NetBackup from Windows 2008/Vista and later systems, adialog box appears. This dialog informs you that PBX is still running and thatit needs to be stopped. When the dialog box appears, Symantec recommendsthat you click, Do not close applications. (A reboot will be required.) and

About known issuesInstallation, upgrade, and cluster issues

18

continue with the NetBackup removal. PBX is stopped and restartedautomatically as needed for removal. Any other installed programs that relyon PBX are not affected.

■ (ET1967792) If you use the BMR boot server, and you enabled the BMR bootserver option at a time after you have installed the NetBackup current patch,youmayneed to install this patchusing the following command-line operation.That updates the BMR boot server files to the current release level. If you donot install the patch using the appropriate command, the BMR boot serverfiles 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)AWindows computerwouldnot comeupafter a disaster recoveryrestore was performed after an ALL_LOCAL_DRIVES backup.If you encounter an error that is related to the lsass.exe executable, youshould perform another restore first. Next, you should shut down theNetBackupclient service fromthe serviceswindowsand then reboot the system.

■ (ET1595854)When youuninstall NetBackup fromaVCS cluster, theVCSTypeis not deleted. If you reinstall NetBackup to the same location, you are not ableto run NetBackup.)To avoid this problem, use the following procedure to uninstall NetBackupfrom a VCS cluster.Note: The first step applies only to UNIX systems. The remaining steps applyto UNIX and Windows systems.

■ If it exists, on UNIX systems, remove the following file from the activenode:/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, deleteall NetBackup data from the shared disk.

19About known issuesInstallation, upgrade, and cluster issues

■ 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/Wmode: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 theVCS configuration back toR/Omode:haconf -dump -makero

■ Uninstall NetBackup from all other nodes in the cluster.

■ (ET2003460) Support for FlashBackup in a Microsoft Cluster (MSCS)environmentBeginning in NetBackup 6.5 GA, the use of FlashBackup in aMicrosoft Cluster(MSCS) environment is supported, with the following limitation: Rawpartitionrestores can only be performed when the disk being restored is placed inextended maintenance mode or removed from the MSCS resource group.

Note: Earlier versions ofMSCS (such as those versions that were shipped withWindows versions before Windows 2003 SP1) do not allow extendedmaintenancemode functionality. If the cluster does not support placing disksin extended maintenance mode, it is still possible to perform raw restores toan alternate, non-shared disk.

■ The Veritas Private Branch Exchange (PBX) software is installed along withNetBackup 6.5.x. Depending on how NetBackup is installed, PBX may logmessages by default to the UNIX system logs /var/adm/messages or/var/adm/syslog, or to the Windows event log. That can cause additionalsystem logging. Themessages that arewritten to the system logs are the sameas those written to the PBX logs (/opt/VRTSpbx/log on UNIX andinstall_path\VxPBX\log on Windows).

To disable PBX logging to the system or the event logs after NetBackup hasbeen installed, enter the following commands:UNIX:cd /opt/VRTSicsco/bin

./vxlogcfg -a -p 50936 -o 103 -s LogToOslog=false

About known issuesInstallation, upgrade, and cluster issues

20

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. Anyfuture PBX log information should no longer appear in the system logs.For more information about this issue or information on how to disable theoption, refer to the following Technote on the Symantec Support Web site.http://entsupport.symantec.com/docs/280746

■ During a Windows server or client installation, if there you encounter a fatalinstall error, you should check the installation logs to determine the cause ofthe error. If you find a return value of three in the install log similar to thefollowing example, then you should first open a cmd window. From thecommand 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 parametershould 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 documentedvalues and try to install NetBackup again.

■ (ET1988453) The client package may fail to extract to the root drive onWindows 2008 R2 Server Core systems.The Windows 2008 R2 Server Core operating system has a security issue withcreating 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 theroot directory. If you encounter this issue, create another directory on the rootdirectory and extract and launch the NetBackup package from that directory.

■ (ET1600692) While installing NetBackup in a cluster and making it HighlyAvailable (HA), if you provide a fully qualified host name (FQHN) when asked

21About known issuesInstallation, upgrade, and cluster issues

for Virtual name, problems may occur and HA is not successful. You shouldnot provide a fully qualified name during the configuration. Refer to theNetBackup High Availability Administrator's Guide for UNIX, Windows, andLinux at the next major release of NetBackup for more information about thisknown issue.

■ (ET1602744/ET1602745) Unable to configure AT after an upgrade to 4.3.42.0.After youupgradeVRTSat to a newer version, an attempt to reconfigureVxATusing the /opt/VRTS/install/installat -configure command failed.

To resolve this issue, remove/opt/VRTS/bin/installat and try to reconfigureVxAT again using the following:Location of ICSInstaller/authentication/installat

■ (ET1633604 and ET1597077) VRTSpbx is not patched with the newer versionincluded in NetBackup 6.5.4 package.If you install Storage Foundation (SF) 5.0MP3 and NetBackup 6.5 on aNetBackupmaster andmedia server, andupgrade toNetBackup6.5.4 or newer,the following can occur. The VRTSpbx version may not update to the versionthat was packaged with NetBackup.

■ (ET1257102) Before you attempt to install a NetBackup master server on aTru64 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 metthen 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 consoleor theWindows Administration Console; set the permissions on the followingdirectories 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 theRelease 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:

About known issuesNetBackup Access Control issues

22

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 youshould 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 datausing the command, bprecover -r -vxss -p PolicyName fails to recover theVxSS environment.

NetBackup Database Agent issuesThe following sections describe known issues as they relate to the NetBackupdatabase 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 withintheEnterpriseVault environment and there is noenterprise vault install

folder/Reports folder present on the system. If you attempt to back up theIndex location, the backup fails because the enterprise vault install

folder/Reports folder is not present on the host. If this folder is not on theserver, 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 theEnterprise Vault Indexing Service on the Enterprise Vault server.

23About known issuesNetBackup Database Agent issues

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 clientthat has Windows 2008 installed, the NetBackup client properties appear inREADONLYmode. If you encounter this privileges issue, perform the followingsteps 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 theUseUACtohelpprotectyourcomputercheckbox (it is checkedby default).

■ (ET1533469 and ET1533488) The Enterprise Vault online Help has not beenupdated for the NetBackup 6.5.x release. The nextmajor release of NetBackupcontains the Enterprise Vault online Help .

■ The NetBackup Enterprise Vault agent does not support the following userinterface: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 userinterface 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 jobdetails under the Activity Monitor or error log should indicate one of thefollowing 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 endedwith a status 1 because of a granular processing operation failure. In thissituation, the backup image is suitable for database recovery.

■ A Microsoft hotfix is required for "Client for NFS" for windows 2003. You canlocate and request this hotfix for either x86 or x64 platforms at:http://support.microsoft.com/kb/947186

■ The followingapplication event logmessagemayappear onanExchange serverduring an Exchange granular operation (backup, browse, or restore). You cansafely ignore that message.Event ID 16384

About known issuesNetBackup Database Agent issues

24

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, orMailbox-level backupsand restores may fail with the MAPI logon error x80040115. Please referto the following Technote on the Symantec SupportWeb site for a solutionto disable IPv6 for MAPI access.http://entsupport.symantec.com/docs/311611

■ The following application event log message may appear on a Windows2008 Exchange server if a user does not have the Active Directory or theUser Name Mapping identity mapping set up and configured using theServices for NFS properties. This message occurs during an Exchangegranular operation (backup, browse, or restore) and can safely be ignored.Event ID 16397Description: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 correspondingUNIX identity of theWindowsuser, you cannotaccessNetworkFileSystem (NFS) shared resources.Verify that theWindowsuser is in Active Directory Domain Services and has access permissions.

■ TheQLogic SANSurfer softwaremayneed to bedisabled oruninstalled becauseit 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 fromthe NetBackup Client GUI or with the bpbackup command, the backup fails.Instead, use theNetBackupAdministrationConsole to initiate amanual backupfor that Exchange policy.See the "Testing configuration settings" section in theNetBackup forMicrosoftExchange Administrator's Guide for instructions on how to perform amanualbackup.

■ When an Exchange backup is launched from the NetBackup Client interfaceand uses the Snapshot Client off-host backup capability, the progress logwindowdoesnot display theusual progressmessages evidentwhena scheduled


backup is executed. The lack of progress logging does not affect the backupoperation. If detailed progress is desired, use the NetBackup AdministrationConsole to launch a manual backup operation on an Exchange policy. See the"Testing configuration settings" section in the NetBackup for MicrosoftExchange Administrator's Guide for instructions on how to perform amanualbackup operation.

■ For NetBackup 6.5.4, the following configuration changes apply for Exchangecluster environments:

■ To perform Continuous Cluster Replication (CCR) backups of the passiveVSSwriter, youno longerneed to set the "EnableRemoteStreamingBackup"registration key.

■ For Exchange 2007 SP1 or later, you no longer need to configure theNetBackup Client Service to run as domain admin.

■ Launching an off-host snapshot backup from the NetBackup Client or withbpbackup

If you attempt to initiate an Exchange off-host alternate client backup fromthe NetBackup Client GUI or with the bpbackup command, the backup fails.Instead, use theNetBackupAdministrationConsole to initiate amanual backupfor that Exchange policy. See the "Testing configuration settings" section intheNetBackup forMicrosoft ExchangeAdministrator's Guide for instructionson how to perform a manual backup.

■ When an Exchange backup is launched from the NetBackup Client interfaceand uses the Snapshot Client off-host backup capability, the progress logwindowdoesnot display theusual progressmessages evidentwhena scheduledbackup is executed. This lack of progress logging does not affect the backupoperation. If detailed progress is desired, use the NetBackup AdministrationConsole to launch a manual backup operation on an Exchange policy.See the "Testing configuration settings" section in theNetBackup forMicrosoftExchange Administrator's Guide for instructions on how to perform amanualbackup operation.

■ (ET1278383) Exchange 6.5.2 - LCR/CCR backup supportTo ensure that the CCR client attributes are set properly for both nodes in thecluster, update the Exchange client attributes for each node individually.Changing the attributes for the virtual CCR name only affects the active nodeat the time of change.


26

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 alsoupgrade the SharePoint clients to 6.5.3.

■ (ET1595100) NetBackup can back up and restore a portal if the IP address isused instead of the name when it is created. However, using a portal nameinstead results in a site-not-being-found condition. That means you have toperform some steps manually to complete the restore. The databases do getrestored to SQL. Use the SharePoint Central Administrator to Recover aPortal, 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 theSharePointCentralAdministratorManageContentdatabases for the virtualserver to add any Team Sites that are associated to the Portal Site. These sitesalso 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 andManagePortal SitesRestorea 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 SharePointAdministratorVirtualServerManagertoManageContentDatabases to addthem back to the portal site.6. The portal should now be available for browse.7. Use the IP for the portal siteURL address. That should void the need to haveto manually do these steps to recover the site going forward.

■ (ET1527929) Backups of the SharePointWeb applications that contain a largenumber of content databases (100+) may timeout. In addition, backups of theportals that use Granular Recovery Technology (GRT) and contain a largenumber of content databases (100+)may timeout. In these situations increasethe 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 interfacefor a SharePoint backup, you must install the Microsoft .NET framework3.5 on the SharePoint servers.

■ Document-level restores fail if the string "_Granular_" is contained withinthe 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 namewithout the string "_Granular_" before performingthe backing up.

■ (ET1594142) When performing a disaster recovery of a SharePoint webapplication and the last restore is complete, verify that theweb applicationappears in the list ofweb applications, and then performan iisreset . Youcanperformtheiisreset commandbyopeningacommandpromptwindowand typing the command, iisreset /noforce.

■ (ET1588836) When restoring a Data Connection Library document from aGRT backup, the documents in the library have the appropriate approvalstatus however the version history may state that 'This is the currentapproved version' when it may not be. The workaround for this issue is tohave the user set the appropriate status for the item.

■ (ET1502252) Restoring a document or a picture library item when thelibrary or folder does not exist is not restored. The library or folder is notrecreated and the item is not restoredThework around for this issuewouldbe to redirect the restore to a file system and then upload the items intoSharePoint.

■ (ET1485122) The application, SPSRecoveryAsst.exe, gives an applicationerror when you try to restore an invalid object that you select from theBackup,Archive, andRestore user interface. Theworkaround for this issueis to select the correct item to restore.

■ (ET1589445) Using AllWebs to perform a granular backup of secure andnon-secure web applications results in a status 1 error. The secure sitescan be backed up individually or together successfully

■ (ET1540667) After restoring a subsite the link is not restored in both quicklaunch and top link bar. You can use an option to add a link so you canrestore a subsite.

■ (ET1539923) Special characters in itemnames are excludedwhendisplayedin the Backup, Archive, and Restore user interface. When the items arerestored, the special characters do appear in the restored item.

■ (ET1639566) Restoring a document from a NetBackup 6.5.3 image of aSharePoint 2003 portal may be reported as successful, however thedocument is not restored. To avoid this issue, restore the database orperform a redirected database restore and access the desired document.

■ (ET1637318) Restoring a Web Application that contains web parts from agranular image results in missing web parts. Once the restore has beencompleted, you must reapply the web parts.


28

■ (ET1633472) Unable to browse sites after multiple db restore. The IISsettings are not preserved when you run this restore. To resolve this issue,restore the SharePoint Web Application from a FULL and DIFF(s) imagesin one job.

■ (ET1630657) A redirected restore of granular content to the file system(using an UNC path) from multiple content databases the restore fails andinforms the user that the restore failed to recover the requested files. Theworkaround is to restore content from one db at a time.

■ (ET1653526)TheSharePointSharedServicesdatabasedoesnotget restored.The SharePoint farm can be recovered from backupwithout this database,All the web applications can be restored successfully along with theircontent. A new SSP service is created as part of the recovery.

■ (ET1640309) A redirected restore of a SharePoint Web Application usingFULL and DIFF images in separate jobs fail. The workaround is to performthe redirected restore of a SharePoint Web Application using FULL andDIFF images in a single job.

■ About restores of SharePoint Server and Windows SharePoint ServicesWhen you perform restores, you should administer restore jobs from theNetBackup master server or the SharePoint front-end server. When yourun a restore job from the master server, the jobs run but no progress logappears. Youmustmonitor the job status from the job details on themasterserver. Symantec recommends that you run the restore jobs from theSharePoint front-end server.

■ You can redirect SharePoint sites, documents, lists or items to a path, aworkspace, or a document library, as follows:- Redirect to path. In the Restore to drive or UNC path box, enter the driveletter or UNC Path. Use the following format for a UNC path:\\servername\share. In the Restore to path box, enter the path to whichyou want to direct the restore.- Redirect to the workspace or the document library(WebStorageSystem-based only). This option only applies to SharePoint2001 restores.NOTE: When you direct items to a file system, any list items you selectedare not restored and appear as 0-KB files . If you redirect list items to a filesystem, the item itself is a 0-KB file but if the list itemhas any attachmentsthey get restored.- Redirect to the Windows file system. When you use a drive letter it mustbe entered C:\ (or whatever drive letter the users chooses) and the "Restoreto Path" must be entered as "restored data". The granular restore run onthe backend server.


If you donot follow this process then the granular restore failswith a status5 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 issuesIf you perform a backup using multiple streams (stripes) and multiplexing, youcannot restore this backup image using more than one stripe.

Other database agent issuesGranular 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 theNetBackup 6.5.3 documentation update. To enable Service for NFS onWindows 2008, add the "Services for Network File System" role under FileServiceswithin theWindows ServerManager. Confirm the "Client forNFS"has started successfully.

■ The 8022.0 or higher version of the Microsoft Exchange Server MAPIClient and Collaboration Data Object 1.2.1 is required on the Exchangeserver for granular recoveries ormailbox level backups to functionproperly.That can be downloaded from the following Web site .

http://www.microsoft.com/downloads/details.aspx?familyid=E17E7F31

-079A-43A9-BFF2- 0A110307611E&displaylang=en

Storage-related issues■ (ET1702148) An enhancement has been made to the improve resource

allocation overhead for duplication jobs. A duplication job typically copiesmultiple images. Within a duplication job, after each image is copied, theresources to read the next image are reallocated. If read resources for eachimage are re-allocated then an overhead problem can occur if you duplicate alarge number of very small images. When you duplicate small images, theoverhead 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 ofNetBackup significantly reduce the time it takesto grant resources for read requests for each image.

About known issuesStorage-related issues

30

■ (ET1976752)NetBackup 6.5 and later does not support SharedDisk storage asa destination for hot catalog backups.

■ (ET1590866) When creating an offline, cold-catalog backup, do not includethe /usr/openv/db directory in the backup selection list. Upon recovery, thatcauses the database files to be recovered twice.

■ (ET1829684) Any Active Directory backup is always a full backup, whether itis a granular backup or not. That means that whenever Active Directory is ina policy’s backup selection list, the AD portion is always backed up fully evenwhen the backup type is incremental, differential or cumulative. Any otheritems in the Backup Selections list may use a differential backup or acumulative-incremental backup type as indicated. Even though a full backupis forced for an Active Directory backup, normal incremental rules apply tothe non-AD items in the policy file list.

■ (ET1765334) When using OST or PureDisk Optimized Duplication betweentwo similar devices, the read side of the duplication job is not counted againstthe 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 similardevices, the duplication job is not counted as an active I/O stream for the diskvolume from which the image is read. In other words, the I/O stream limitsetting does not limit the number of optimized duplication jobs that can readimages from OST/PureDisk disk volumes and cannot be used as a mechanismto prevent these disk volumes frombecoming overloaded. That can cause slowperformance for backup and duplication jobs if too many jobs are running atone time on the same disk volume.

■ (ET1737495) When a policy writes multiple copies to disk storage units andtape storage units, and if multiplexing is configured, the result is the lowestmultiplexed 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 thetypes are mixed, multiplexing does not occur.

■ (ET1502680) When creating Active Directory objects, it is advisable to takeadvantage of the schema that Microsoft provides. To place things outside ofthe schema means that though it may be possible to successfully perform aGranular backup, it is not possible to browse those Active Directory objectsthat have been oddly placed. An object that cannot be browsed also cannot berestored.For example, the situation in which one creates a user or computer in theDomainControllers container. The object is included in a successful granularbackup, but is not displayed in a browse. Since it is not displayed in a browse,it cannot be restored.

31About known issuesStorage-related issues

■ (ET1538745) Destinations within a storage lifecycle policy may be backupdestinations 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 differentmedia serveroriginally wrote.Each destination belongs to a particular disk pool. The alternate read serverthat is indicated as a duplication destination in the same storage lifecyclepolicymust be a server for the disk pool of the source backup destination. Diskpools are listed under Media and Device Management > Devices > Disk Pools.

■ (ET1543025) Both types of backup staging methods make use of capacitymanagement on disk storage units. Thatmeans thatNetBackup automaticallyremoves expired images from the storage unit to create space for new images.

In either situation, NetBackup cannot manage the capacity of a storage unitthat is NFS-mounted:

■ For basic disk staging:The disk staging storage unit is capacity-managed by default. Do notmakea DSSU out of a storage unit that is NFS-mounted. (That is, do not selectthe 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 theStagedCapacityManaged option for any destination that isNFS-mounted.

■ (ET1485775)OpenStoragedirect-to-tape enables you to copyNetBackupbackupimages from a disk appliance to NDMP hosted tape drives.For more information, see the 6.5.4 version of the NetBackup Shared StorageGuide contained in the followingTechnote on the Symantec SupportWeb site.http://entsupport.symantec.com/docs/318351

Note: The license key that activates OpenStorage must be installed on eachNetBackup media server that you use for direct to tape.

■ (ET1543384) Backups to disk may fail with status code 800During heavy NetBackup media server activity, backups to disk may fail withaNetBackup status codeof 800.The codeappears in theAdministrationConsoleActivity Monitor Job Details display.See the NetBackup Troubleshooting Guide description of NetBackup statuscode 800 for remedial action.Jobs may fail because the heavy load causes processes to wait longer than thedefault timeout period (60 seconds). You can try to increase the timeout bycreating the following file on the media server:UNIX: /usr/openv/netbackup/db/config/DPS_PROXYDEFAULTRECVTMO


32

Windows: C:\ProgramFiles\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 orless than or equal to 3600 seconds.

■ The SAN Client does not support inline tape copy over Fibre Transport. Inlinetape copy jobs occur over the LAN. The SAN Client is designed for very highspeed backups and restores. Therefore, SAN Client excludes backup options(such as inline tape copy) that requiremore resources to process andmanage.

■ A new option that is labeled New has been added to the Add Disk Array Hostdialog box. In addition, a new dialog box titled, New Array Type has beenadded.Whenyou click theNewoption theNewArrayType dialog box appears.Included on this dialog box is a Help option. The online Help for this dialogand option will be available at the next major release.

■ TheNetBackup Shared Disk option does not supportWindows 2008 formediaservers.

■ 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 youdonot spanbackup images across volumesin anAdvancedDisk disk pool. File system full conditions cannot be detectedadequately. Therefore, each disk pool should be comprised of only onevolume.

■ (ET1128929) Potential free space is the amount of space on a disk stagingstorage unit (DSSU) or on a lifecycle policy destination that NetBackup canfree if extra space on the volume is needed. (Use the nbdevquery command todisplay the potential_free_space and the free_space value.) The potential freespace value represents the total size of the image copies that are eligible forexpiration.To create free space, an administrator can run the bpexpdate command tomanually expire eligible image copies on thevolume.That changes thepotentialfree space into available free space.

If nbdevquery is run after bpexpdate is used, the potential free space valueshould be reduced, and the free space value should be increased. However,that is not the case. The nbdevquery command does not display the correctvalue 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 conditionis reached on the storage unit. The automatic expiration of eligible copies

33About known issuesStorage-related issues

of staged images occurs and then the potential_free_space value for thatdisk is recalculated.

■ For disk destinations within lifecycle policies: When a duplication job thatwrites to the disk completes, the potential_free_space value for that diskis recalculated.

Suppose a copy of an image is beyond its try-to-keep date, and is a candidatefor removal fromdisk. For instance, this copy of the image is counted as a partof the potential-free-space value. If a user uses the bpexpdate command tomanually expire this copy of the image from disk, the potential-free-spacevalue is not decremented to reflect the action that was taken until the wholepotential-free-space value is recalculated. Until the value is recalculated, theuser and NetBackup think that there is more available space on the disk thanthere is.

The potential-free-space value is recalculated:

■ When the High Water Mark (HWM) condition forces a draining of the diskdown 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 systemincrements the free space , but NetBackup does not decrement the potentialfree space . Thus, the size of the image that was expired is counted twice asboth free space and potential free space . That is the reasonwhy it looks to theuser 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 SVMmetadevices (volumes) that are createdwhen it uses slice 2 of the Solaris Disks.For more information on this issue, refer to the following Technote on theSymantec Support Web site.http://entsupport.symantec.com/docs/303027

■ (ET1317594) To add clarity, the Loadbalance label in the StorageUnitGroupdialog, has been changed to read, Media server load balancing.

■ (ET1267896) When performing backups using the new Pure DeduplicationOption (PDDO) feature, Symantec suggests that users monitor their sharedmemory usage as the number of jobs increases. The job-size throttling hasbeen turned off in NetBackup 6.5.2 to allow more PDDO backups to runconcurrently. Please consult your NetBackup Performance Tuning Guide foradditional information on NetBackup tuning parameters affecting sharedmemory usage.

■ (ET1597920) Disaster recovery email and AdvancedDisk storage units


34

If an online, hot catalog backup is directed to an AdvancedDisk storage unitand a catalog backup policy identifies a critical policy that has a backup imagethat is located on the same AdvancedDisk storage unit, the disaster recoveryemail does not list that critical policy.However, the policy is listed in the disaster recovery file. You can open the DRfile with a text editor to obtain that critical policy information (the mediaserver and the media ID on which the policy's backup image resides).

NetBackup user interface issues■ TheNetBackup-JavaadministrationconsoleonWindows (WDC) cannot connect

to a UNIX master sever with a Japanese package. When you attempt to log onto the master server, the NetBackup-Java administration console hangs at apoint when the following status statement appears.Checking if NBAC is configured.

Formore information about this issue and aworkaround solution, refer to thefollowing Technote on the Symantec Support Web site.http://entsupport.symantec.com/docs/335933

■ (ET1980306) You are not able to search for backup images under the Catalognode (Action > Verify) of the NetBackup Administration Console.If you encounter this issue, start the user interface from theRecentProgramslist.

■ You browse for granular backups differently on the MFC user interface thanyoudowhenyouuse theNetBackup-JavaAdministrationConsole.Thathappenswith granular backups from Microsoft Exchange, Microsoft SharePoint, orMicrosoft ActiveDirectory. The difference occurswhen you click on a granularnode to expand the node and view its contents. A noticeable delay andunnecessary overhead can occurwhenyou expand a granular node on theMFCuser interface. The MFC user interface may expand more than was requestedin an attempt to minimize this delay. The NetBackup-Java AdministrationConsole does not do that. The NetBackup-Java Console requires the user tomake additional node expansion clicks and causes an additional delay.

■ (ET1517333) To back up all local drives, Symantec recommends that you usea scheduled backup from the master server. This method is much faster thanperforming 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 arerunning on two separate remote desktop sessions on the same server, theconsole may crash. This issue does not occur very often. The issue is not aregression and is outside of the normal scope of operations.

35About known issuesNetBackup user interface issues

■ (ET1395328) When using the bp or the bpadm interface on HP-UX 11.23 or11.31 systems on Integrity (IA-64) architecture, a DATE ERROR is returnedduring attempts to change dates. For more information about this issue, referto the following Technote on the Symantec Support Web site.http://entsupport.symantec.com/docs/308809

■ (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 theNetBackup-JavaAdministrationConsole 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, theuser should use a Java Administration Console that is running on a Windowsworkstation to create policies for MSEO.

General NetBackup issues■ 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 restoreoperation, further restore operations involving this media server do notfunction. Formore information about this issue, refer to the followingTechnoteon the Symantec Support Web site.http://entsupport.symantec.com/docs/303970

■ (ET1750852) The NetBackup VxFI provider does not work with IBM DS 8300arrays. Formore information, refer to the followingTechnote on the SymantecSupport Web site.http://entsupport.symantec.com/docs/329598

■ (ET1116304) To view the log messages that PBX exchange generates, use theutility, vxlogview, that the VRTSicsco package installs. Typically, theVRTSicsco package is installed at /opt/VRTSicsco on UNIX systems andCommonProgramFiles\VERITAS\VRTSicsco onWindows systems. You shouldnot use vxlogview that another package installs. Installing the utility fromanother package may cause errors because of a version and an architecturemismatch.

■ (ET 1993115)NetBackup 6.5.6 Snapshot Client supports nomore than 40 rowsof “Snapshot Resources” entries per policy for certain disk arraysFor the following disk array snapshot methods, NetBackup can support up to40 rows of entries in the Snapshot Resources pane of the policy’s SnapshotOptions dialog. Each row consists of an array serial number, an ID for thesource device, and IDs for one or more snapshot devices.

About known issuesGeneral NetBackup issues

36

If you specifymore than 40 rows for any of the followingmethods, the backupof 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, referto the NetBackup Snapshot Client Administrator's Guide.

■ About VSS and hot to manage snapshot volume sizeIn the NetBackup 7.0GA, 6.5.4 and 6.5.5 releases, NetBackup attempted tomanage the size of the VSS snapshot volume. To do that, NetBackup changedany unbounded VSS associations to a fixed size. That size was based on thesize of the disk drive. The objective was to prevent the unbounded VSSassociations that can fill a hard drive and affect the system operation. Inreleases after 7.0GA and 6.5.5 that is no longer be done and that systemmanagement setting is beyond the scope of NetBackup to alter.

A customer who has upgraded from one of these levels might have failedbackups because NetBackup has changed this setting. For that to occur all ofthe 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 VSSsnapshots that overlap in time.

In this case the association is set too small and future snapshots might bedeleted before they are backed up. To correct this issue, set the association toa larger,more appropriate value. Refer toMicrosoft documentation for detailson how to set this system management setting.

■ (ET2020528) To configure array access for NetBackup hosts not named in apolicy

In the following cases, you must explicitly enable NetBackup to access diskarray credentials:

37About known issuesGeneral NetBackup issues

■ Certain NetBackup hosts that are not named as clients in a policy must beexplicitly enabled to access array credentials. An example is an alternateclient that is used for off-host backup processing but is not included in thepolicy’s Clients list.

■ Microsoft Exchange is installed onahardwaredisk array such thatWindowsVSS uses the hardware snapshot provider. If you define an MS-Exchangepolicy with Snapshot Client and Instant Recovery, but you accept thedefaults for Snapshot ClientOptions, NetBackupmust be explicitly enabledto access the array credentials. (Note: This requirement does not apply ifyou set the VSS Provider Type to 3-hardware.)

To enable NetBackup to access the array credentials:

■ In the NetBackup Administration Console, click HostProperties > Masterservers > double-click name of master server > Properties > CredentialAccess.

■ 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-timerollback fails with NetBackup status 5.

■ Windows:

On the NetBackup master server, click Start > Run and enter regedit.1

To be on the safe side,make a backup of the current registry (File>Export).2

Go toHKEY_LOCAL_MACHINE\SOFTWARE\VERITAS\NetBackup\CurrrentVersion\Config.

3

Right-click in the right pane and select New > String Value. Enter thefollowing: DISK_CLIENT

4

Right-click on the new DISK_CLIENT name and select Modify.5

For the Value data field, enter the host names of the clients that are notnamed in any policy. To specify multiple host names, separate the nameswith a space.

6

Click OK. Until this entry is made in the Windows registry, a point-in-timerollback fails with NetBackup status 5.

7


38

■ (ET1953216) Snapshot-only restores fail with a private provider error on arollback attempt.The failure occurs becauseNetBackupwas unable to retrieve the required diskarray credentials fromthemaster server. TheDISK_CLIENT=;client credentialshould be to the NetBackup registry of the master server, so the rollback cansucceed.)You should configure the array access forNetBackuphosts that are not namedin the policy. You must explicitly enable certain NetBackup hosts that are notnamed as clients in a policy to access array credentials. An example is amediaserver that is used for off-host backup processing but is not included in anypolicy’s Clients list.

To allow the host to access credentials, do the following:

■ In the NetBackup Administration Console, click HostProperties > Masterservers, 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 filesNetBackup uses the /usr/openv/netbackup/logs directory tree to recordtroubleshooting information and to obtain progress and communicationupdates to users and other NetBackup applications. Restrictive permissionson these directories cannot 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/logsdirectories and subdirectories readable and writeable by all users (777permissions). However, security requirementsmay prohibit global read-writeaccess. If so, you can restrict permissions of specific directories to a singlegroup or user if the following is true: All backup and restore operations thatare related to that directory are initiated by the processes that run asmembersof that group or as that user.Check that the/usr/openv/netbackup/logs/user_opsdirectory treehas777permissions. The items in this directory need to be accessible for theapplications 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 effortsmaybehinderedwhenprocesses donot havethe 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 describedin the Administrator's Guide.However, since curly bracket characters are valid characters forWindows filenames, they cannot beused to indicatewildcardusage forWindowsplatforms.Also, backslashes cannot be used as escape characters for curly bracketcharacters.

■ (ET1720780)VMwareVCBFlashBackup restores to an alternate client fail witha status 5 error.For more information and a work-around solution to this issue, see thefollowing Technote on the Symantec Support Web site.http://entsupport.symantec.com/docs/326879

■ (ET1940490) VMware Mapped Full VM backups do not support mapping ofIDE disks.Mapped VM backups fail if the VM contains IDE disk(s).

■ (ET1636600) Backup problemwith MS-Windows-NT policy type andVMwareESX version 3.0 and 3.0.1Symantec identified a problem when backing up a NetBackup client that isinstalled in a Windows operating system on certain versions of VMware ESXservers. If you select the MS-Windows-NT policy type, and the ESX server isat 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, configureaVMwarebackupproxy server anduseNetBackup forVMwareto perform the backup. For assistancewithNetBackup for VMware, see the"NetBackup for VMware Administrator's Guide."

■ (ET1593098) An error message is issued when an attempt to validate VMwarecredentials occurs.NetBackup 6.5.4 added the ability to verify that the VMware credentials thatyou entered in the NetBackup policy are valid for the VMware server. TheNetBackup Add virtual machine server dialog now contains a "ValidateCredentials" checkbox.

Note: If your VMware proxy server is running a version of NetBackup that isearlier than 6.5.4, the credentials cannot be validated. That causes an errormessage to appear. Youmust verify that the credentials you entered are correctfor the VMware server. If the credentials are correct, you can ignore the errormessage.


40

■ If a virtual machine backup uses VCB and the policy is configured with theMappedfullVMbackupoption, the backup fails if the virtualmachine containsan IDE disk.To use the Mapped full VM backup option with VCB, you must reconfigurethe virtual machine so that it does not contain IDE disks.For descriptions of other backup options, see the "Configuration parametersfor VMware" section of theNetBackup for VMware Administrator's Guide, forNetBackup 7.0.

■ NetBackup now supports EMC Solutions Enabler 7.0 with the followingsnapshot methods for EMC disk arrays:EMC_TimeFinder_Clone,EMC_TimeFinder_Mirror, EMC_TimeFinder_Snap.

■ (ET1556112) As part of the catalog policy configuration, the administratorindicates a path to the directory where the disaster recovery information issaved. This path is indicated on the Disaster Recovery tab.The path for the disaster recovery information cannot be to a directory thatis on the same partition as /usr/openv/netbackup. If the path for the disasterrecovery information is to a location on the same partition as/usr/openv/netbackup, NetBackup displays a status 20 error message. Themessage states that the disk path is invalid. The administrator needs to changethe path on the Disaster Recovery tab to a directory on a different partition.

■ In rare situations the first backup attempt after NetBackup is installed mayfail. That canhappen if the backup is granular and ifMicrosoft VolumeShadowCopy Services (VSS) is used. In addition, after this one failure all subsequentbackups succeed.

■ (ET1535587) The media server that was used for catalog backups must be atthe same level as themaster server. That is true for hot or cold catalog backups.

■ (ET1504682) The bpbackup command is used to perform user backups fromclients and manual backups from master servers. In addition to listingindividual files or directories, bpbackup can also use directives to indicate thefiles 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 criticalperformance issues.

■ (ET1539585) In this release, an administrator can resume a suspended jobuntil the retention period of the job is met. The retention period begins whenthe 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 thenmoved to the DONE state.

Note: The Clean-up host property, "Move backup job from incomplete state todone state," does not apply to suspended jobs. Jobs are suspended manuallyand must be resumed manually.

■ (ET1512562) Individual restore of mails from BE images is not supported inNetBackup 6.5.x as mentioned in the NetBackup online Help.

■ (ET1260712) NetBackup considers the failure history of a policy when itdetermines whether or not to run a scheduled backup job. The timeframe forNetBackup to examine one of the configured settings occurs when you use theSchedule 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 determineswhether to allow another backup attempt (retry). By default, NetBackupexamines the past 12 hours.

■ Howmany times a backup can be retriedwithin that timeframe. By default,NetBackup allows two attempts. Attempts include the scheduled backupsthat start automatically or the scheduled backups that a user initiates.

InNetBackup 6.0 and later, all backup attempts apply toward this configurablelimit, regardless of the type of backup or the schedule. In releases before 6.0,NetBackup allowed each schedule to meet the Schedule Backup Attemptsproperty limit. In some cases that resulted in more backup attempts thanexpected based on the property setting.

Consider the following 6.5 example scenario using the default setting: twotries 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:00P.M., NetBackup looks at the previous 12hours. It sees one attemptat 6:00 P.M. and one attempt at 8:00 P.M. The Schedule backup attemptssetting 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 settingof two has not been met so NetBackup tries again. If a schedule window isnot open at this time, NetBackup waits until a window is open.

■ (ET1260712) For master servers at NetBackup version 6.5 or later, theALLOW_MULTIPLE_RETENTIONS_PER_MEDIA setting in the bp.conf file has


42

no effect. To allowmixed retention levels onmedia, use the nbemmcmd commandto update the nbemm database and change theALLOW_MULTIPLE_RETENTIONS_PER_MEDIA setting. The defaultconfiguration does not allow multiple versions (a setting of 0 or no).To allow multiple retention levels, use nbemmcmd -changesetting to changethe ALLOW_MULTIPLE_RETENTIONS_PER_MEDIA setting to 1 or yes.

■ (ET1364268) In 6.5.2 NetBackup introduced the ability to allow, restrict, orprohibit reverse host name lookup for master servers, media servers, andclients.

Administrators can configure this using several methods:

■ By changing the Network Settings host properties in the AdministrationConsole.

■ By editing the bp.conf file (UNIX) or the Windows Registry.

■ New in 6.5.4: By using the bpclntcmd command on UNIX or Windowssystems.

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 oneof 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 towork 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 performreverse host name lookup. If the NetBackup host successfully resolves theIP address of the connecting server to a host name (reverse lookup issuccessful), it compares the host name to the list of known server hostnames.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 theknown server list to IP addresses (using a forward lookup). The hostcompares the IP address of the connecting server to the list of known serverIP addresses.If the comparison fails, the host rejects the connection from server and theconnection fails.


■ To prohibit reverse host name lookup, enter:bpclntcmd -reverse_name_lookup prohibited

This setting indicates that the NetBackup host does not try reverse hostname lookup at all. The host resolves the host names of the known serverlist to IP addresses using forward lookups. The NetBackup host thencompares the IP address of the connecting server to the list of known serverIP addresses.If the comparison fails, the NetBackup host rejects the connection fromthe server and the connection fails.

■ (ET1436810) Calendar incremental backups may not run on the same day asa calendar full backup as been scheduled.

■ (ET1199036 and ET1181074) Usersmay get a core dump of dbeng9 after a FullCatalog Backup recovery. That is not a Symantec NetBackup issue. This coredump can be deleted and ignored. Testing showed that the catalog recoverycompleted successfully and that bprecover handled the core dump issueappropriately.

■ (ET1268670) In NetBackup 6.5.2, a user cannot change the NDMP hosts inDevice 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-JavaAdministration console.2. Select NDMP Hosts.3. Select the NDMP host to change.4. Right-click theNDMPhost and selectChange from the drop-downmenu.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 forIBM_DiskStorage_FlashCopy snapshot method.Apoint-in-time rollback restore froman IBM_DiskStorage_FlashCopy snapshotbackup fails on AIX platforms for the backup resources that are built on AIXnative stacks, such as JFS2 file systems on AIX LVM volumes. TheIBM_DiskStorage_FlashCopy snapshot method is supported on the IBM DS6000 series of storage arrays .

■ (ET1250126) To perform a point-in-time rollback restore for an IBM DS6000system, you must modify a VxFI configuration file for the Windows x64


44

platform. Perform the following steps to set up and change the configurationfile:

■ 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 ofC:\Program Files (x86)\IBM\DSCLI).

You can find the following Technote on this issue on the Symantec SupportWeb site.http://entsupport.symantec.com/docs/302962

■ (ET1274002) The recovery of a catalog image that was taken in NetBackup6.5.2 is NOT supported in an earlier version of NetBackup or vice versa.

■ (ET1137932) To do NetBackup restores as a non-administrative user underNBAC using the Windows Backup, Archive, and Restore client console or theWindowsAdministrationConsole, the permissions on the followingdirectoriesneed 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 managementlimitation. Windows can only address 4GB of memory. If an attempt is madeto performaFlashBackup of volumes that are larger than10TB, that it requiresmore than 4GB of memory to store the bitmap that needs to be created for therestore of single files. To work around this issue, Symantec recommends thatyou make smaller volumes or use a UNIX master server.

■ (ET1412544) TheWindowsNTFS file system supports the new junction pointsfeature. A junction point can be set up to provide access to files in a localdirectory (similar in function to a symbolic link). For backups of a VMwarevirtualmachine,NetBackup forVMware does not currently support a junctionpoint as the snapshot mount point on the VMware backup proxy server. Thesnapshot mount point must be a local directory on the proxy server, not ajunction point that refers to a local directory. Support for junction points asthe snapshotmount point on the proxy serverwill be added in a future release.


Warning: If a junction point is used as the snapshot mount point, the backupappears to succeed, but the actual files that were backed up may be the wrongfiles.

■ VMware NetBackup Integration Module (VNIM) not required.The VMware NetBackup Integration Module (VNIM) is not required forNetBackup for VMware. In fact, NetBackup for VMware cannot function ifVNIM is installed.

Note: NOTE: If VNIM is installed, you must uninstall it before running anybackups.

■ 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 youdonot spanbackup images across volumesin anAdvancedDisk disk pool. File system full conditions cannot be detectedadequately. Therefore, each disk pool should be comprised of only onevolume.

NetBackup Hyper-V issues■ 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 mustcreate an individual policy for each cluster node (Hyper-Vhost). Because virtualmachines can migrate from one node to another, you may have to update anexisting 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 thevirtualmachines are on the active node A. Therefore, the Clients list of theNetBackup policy for node Amust include all the virtual machines. If nodeA fails over to node B, node B becomes active and all the virtual machinesmigrate to node B. In that case, youmust have a policy for node B that listsall 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 onepolicy needs to be active at any given time. Each policy's Clients list mustcontain all the virtual machines in the cluster that need to be protected.

About known issuesNetBackup Hyper-V issues

46

■ For a cluster with two active nodes A and B, you must have two policiesactivated at the same time, one for each node. All virtual machines in thecluster must be named in the Clients list of each policy. Since a virtualmachine could be running on either active node, a backup started for onenode (where the virtual machine happens to exist) succeeds. A backupstarted for the other node (where the virtual machine does not exist) fails.A number of backups jobs will fail, but this configuration ensures thatvirtual machines are backed up as part of at least one policy.

■ For a virtual machine that is configured on a Windows volume GUID: Ifcluster nodes A and B each refer to the volume GUID on a shared storagedevice that is formatted with the MBR format, the volume GUID used bynode A for the virtual machine is not the same as the GUID used by nodeB for the samevirtualmachine. In otherwords, the virtualmachine's volumeGUID is different on different nodes. As a result, if the virtual machine isactive on the node where it was created (node A), a backup of the virtualmachine using the policy for node A succeeds. If the same virtual machineis active on a different node (node B instead of A), a backup of the virtualmachine using the policy for node B fails. Only the policy that was createdfor 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 NetBackupbackup of the virtual machine, the backup may be partially successful. Amessage 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 itsown snapshots when it backs up virtual machines.

■ (ET1762911) Redirected Restore from R1 to R2 Hyper-V server fails Thefollowing three items are associated to this same issue:

■ After a redirected-full, virtual machine restore on a Windows Server 2008SP2 system, that virtual machine enters a saved (unexpected) state andfails to start.

47About known issuesNetBackup Hyper-V issues

You must manually delete the spurious saved state after the restore andthen start the virtual machine . This issue can occur when the VirtualMachine is backed up in an online state and the expected state after therestore is OFF. However, because of the Hyper-V behavior on these thistype of platform, the virtual machine goes into a spurious SAVED state.During the restore, Hyper-V-VMMS logs the event ID 12340. The followingis 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 SavedState.

■ Full virtual machine restore fails with error 5.VM Restore Job fails with an error 5, however, the virtual machine is stillregistered in theHyper-V server. (Hyper-V-VMMS logs the followingwarningsin the events log.) The Hyper-V writer encountered a Network configurationerror and that caused the failure. After the virtual machine is restored it canbe started after you reconfigure the network adapter configuration in VMsettings.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 becausethe virtualmachine thatwas backeduponaWindows2008 serverwas restoredon a Windows Server 2008 R2 server.If a virtual machine was configured on a Hyper-V Server 2008 V1 when thevirtual machine was backed up a failure could occur. The failure occurs if atthe time of the backup the virtualmachinewasnot in theOff state, the restored


48

virtual machine fails to start if it is restored to a Hyper-V Server 2008 R2. AHyper-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 thenstart the virtualmachine. In theHyper-VManager interface, right click on therestored virtual machine and select Delete Saved State.

■ (ET1656180) NetBackup for Hyper-V has a virtual machine restore optioncalled "Overwrite virtual machine." This option removes a virtual machine onthe destination server before the same virtual machine is restored from itsbackup. If the Overwrite virtual machine option is not selected and a virtualmachinewith the sameGUID 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 "Overwritevirtual machine" option, and the virtual machine exists on the destinationHyper-V server, the restore fails (as expected) but the existing virtualmachineis turned off.

■ (ET1663569) A minor problem occurs if you change an option in aFlashBackup-Windows policy for Hyper-V, on the Snapshot Client Optionsdialog. When you use the keyboard to enter a new configuration parameterfor an existing policy, the value is not retained when you save the policy.

■ Whencommon (or parent) .vhd files and child .vhd files are restored to a driveother than their original drive (such as to G:\ instead of to E:\), therestored child .vhd files may not correctly point to the restored parent .vhdfile on the G:\ drive. As a result, the restored virtual machines that rely onthe common (parent) .vhd file are invalid.Make sure to restore the parent andthe child .vhd files to the same relative path names that they had before therestore.

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 theparent.vhd file toG:\restore_folder\folder1\parent.vhdand the child to G:\restore_folder\folder2\child.vhd.

49About known issuesNetBackup Hyper-V issues

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 therestore locations.

■ (ET1514145) If you restore the full virtual machine to a different location onthe original Hyper-V server or to a different Hyper-V server, the virtualmachine may fail to start. This failure may be due to a bug in the MicrosoftHyper-Vwriter. The problemoccurswhen the virtualmachinehas two ormorelevels of differencingdisks. For example: A child.vhd file points to a parent.vhdfile, and that file points to a grandparent.vhd file.

After the restore, use the Hyper-V Manager to manually re-establish therelationship between the different disks (such as child.vhd to parent.vhd tograndparent.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 aHyper-V virtual machine has been configured for LDM volumes, and theNetBackup policy specifies the "2-Mapped FullVM" option, in certain cases abackup of the virtualmachinemaynot complete. TheNetBackup jobmay issuestatus 1, "the requested operation was partially successful." This error canoccur if the controller type of the .vhd diskwas SCSIwhen the diskwas initiallyformatted, 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 typeoriginally assigned before the LDMvolumewas created. Then retry the backup.

■ (ET1418453) The following is a known issue for redirected restores of theHyper-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 whenNetBackup backs it up, the virtual machine is in the "Off" state after it isrestored to a different location. The current Microsoft Hyper-V writer causesthe change of state to Off.If you restore the virtualmachine to its original location on theHyper-V server,the state of that computer after the backup is correctly restored. If the virtualmachine was in the Saved or Paused state, it is set to Saved or Paused afterthe restore.

■ (ET1847204) The following exclude list issues can occur when you restoreindividual files from an instant recovery snapshot:

■ When you restore files from a snapshot that was made for an instantrecovery off-host alternate client backup: NetBackup consults the excludelist on the alternate client evenwhen it restores files to the primary client.


50

If the exclude list on the alternate client is different from the exclude liston the primary client, any of the files that are listed in the exclude list onthe alternate client are not restored to the primary client.For example: If the alternate client's exclude list has the entry *.jpg, andsome .jpg files were included in the primary client backup, the .jpg filescan be selected for the restore but are not in fact restored. To restore thefiles, you must change the exclude list on the alternate client.

■ When you restore files from a snapshot that was made for an instantrecovery backup (local or off-host alternate client): If the exclude list ischanged after the backup occurred, NetBackup honors the latest versionof the exclude list during the restore. Any files that are listed in the currentexclude list are not restored. Also, as noted in the previous item, the excludelist on the alternate client takes precedence over the exclude list on theprimary 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 beselected 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 thebackup and any files in the exclude list are not backed up. Forsnapshot-based backups, however, all files are included in the snapshot.The exclude list is consulted only when a storage unit backup is createdfrom the snapshot. If the snapshot is retained after the backup (for theinstant recovery feature) and the snapshot is available at the time of therestore, NetBackup restores files from the snapshot. Since all files areavailable in the snapshot (including those that would be excluded from astorage unit backup), NetBackup incorrectly consults the current excludelist on the client or alternate client. Any files in the exclude list are skippedduring the restore.This issue will be addressed in a future release of NetBackup.

Bare Metal Restore (BMR) issuesThe following BMR issues are specific to UNIX systems:

■ (ET1861330) Restoring a Solaris SPARC-Sun4V client to a SAN disk usingBMR-DDRmechanismcan cause a failure during the first boot. That can renderthe restored system unusable.BMR supports Dissimilar Disk Restore (DDR) of a Solaris host. You can mapsystem volumes or slices originally residing on a host’s local disks to SANDisks (LUNs). That enables the host to boot off the SAN-LUNs after the restoreis completed. In NetBackup 6.5.5, if the client system has a Solaris

51About known issuesBare Metal Restore (BMR) issues

SPARC-Sun4V processor, then attempting this type of a restore can causefailures during the first boot after a BMR restore. That can cause a kernel panicand render the restored client unusable. No known workaround or solutionexists for this problem.

■ (ET1766898) Solaris10 x64 Update-5 and Solaris SPARC Update-6 client selfrestore failed with a Windows 2003 x64 master server.In the backup environment, if theNetBackup/BMRmaster server is aWindows2003 (x86 or x64) host and the NetBackup/BMR client is a Solaris10_x64 or aSolaris SPARC host, then the bare metal restore of the Solaris host fails. Thefollowingmessage appears on the console of theSolaris clientwhere the restorefailure occurred:ERROR retrieving and/or generating disk usage data.

To avoid this issue, disable the logging from the BMR restore environment bynot selecting the Enable logging check box. You can disable the logging whileyou perform a Prepare-To-Restore (PTR ) operation for a Solaris (SPARC orx64) clientwith theNetBackupAdministration Console. If you use the bmrprepcommand line interface (CLI) to perform a PTR operation, then do not passthe -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 thecatalog back job failed. This alert works if no catalog backup job was run inthe specified time frame. However, this alert is not generated if a catalogbackup job was run but failed.

■ (ET1463349)NOM failed to log on after the patch installation. If you encounterthis 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.3to NetBackup 6.5.6, you should freeze the cluster node. You can do that fromthe VCS user interface or use the VCS command line.

■ OnSolaris, if you downgrade aNOMcluster fromNetBackup6.5.6 to a previousversion, the NOM web version appears incorrectly on the inactive node.

■ OnWindows, in aNOMcluster, theNetBackup 6.5.6 installer attempts to startthe 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

About known issuesNetBackup Operations Manager (NOM) issues

52

<NOM_INSTALL_DIR> on both of the nodes. The configlocation.conf file islocated 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 wereinvalid. A fix will be made in a future release that ensures vxlogview will beable to convert the lines that contain any multibyte character.

■ (ET1556155) The Japanese vault store name becomes unreadable in thebpresolver log.

■ (ET1556191) After selecting, Full Check including indexes an issue occurredthatcausedENTERPRISE_VAULT_DBCC_CHK_PREBKUPtobecreated,howeverENTERPRISE_VAULT_DBCC_CONT_ONERRwas not created even though the"Continue with backup if consistency check fails" was checked as the defaultsetting in the Client Properties dialog. TheENTERPRISE_VAULT_DBCC_CONT_ONERRshouldhave been created and setto 1 or the Continue with backup if consistency check fails is not checked asthe 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 invalidlocalized names for the backup targets. vxlogview should be able to convertthe lines that contain any multibyte character.

■ (ET1633814) If a logonaccountwasnot raisedwithUAC, nothingwouldhappeneven if an attempt was made to right-click the tracker icon. And if youdouble-clicked the tracker icon the tracker.exe would crash.

If you encounter this issue, check Run this program as an administrator onthe compatibilities tab for the properties of the tracker.exe executable.

General Documentation issuesThe following documents incorrectly indicate that PureDisk storage units supportGranular 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

53About known issuesLocalization issues

■ 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 GranularRecovery.

Table 2-1 Disk storage units that support Granular Recovery

Granular Recovery supportedDisk storage unit

YesBasicDisk

YesAdvancedDisk

NoNearStore

NoOpenStorage

NoPureDisk

NoSharedDisk

NoSnapVault

■ (ET1392433) The 6.5.2 documentation incorrectly states that theExpireAfterDuplication option for storage lifecycle policies is available for Duplicationdestinations as well as Backup destinations. This behavior was introduced inNetBackup 6.5.4, not 6.5.2.

■ Refer to theNetBackupBareMetal Restore (BMR)Administrator's Guide at thenext major release of NetBackup for documented corrections of the followingitems:

■ In the storage area network Support section of Chapter 6, RestoringClients,the following text appears:Bare Metal Restore can restore a system that is attached to a Storage AreaNetwork (SAN). On Windows, AIX, and Solaris systems, if the host busadapter (HBA) drivers are available in the restore environment, BMRautomatically restores the SAN-attached volumes. BMR does not supportthe restoration of systemswithSANattachedvolumes onHP-UXandLinux.

The following text is the correct replacement text.

■ Bare Metal Restore can restore a system that is attached to a StorageAreaNetwork (SAN). If the host bus adapter (HBA) drivers are availablein the restore environment then:

About known issuesGeneral Documentation issues

54

- On Solaris 10, BMR automatically restores the SAN-attached boot anddata volumes.- OnSolaris 8 and 9, BMRautomatically restores the SAN-attached datavolumes.- On Windows, BMR automatically restores the SAN-attached datavolumes.- On AIX, BMR automatically restores the SAN-attached data volumes.- OnHP-UXandLinux, BMRdoes not support the restoration of systemswith SAN attached volumes.

In the Configuration Summary section of Chapter 10,Managing clients andconfigurations the following text should be added:

■ Client configuration can be modified to add, change, and remove alicense key for the software that is discovered for a protected system.The license key, is also added to the protected systemafter restore usingthe configuration to which the key was added. This facility is availableonly for Veritas Storage Foundation products.

■ (ET1197993) The NetBackup 6.5 Administrator's Guide, Volume I, incorrectlystates that the Virtual Tape Option is necessary to create an NDMP storageunit. That is incorrect. The NetBackup for NDMP license must be installed onthe media server to use a host as an NDMP storage unit.

■ The NetBackup Release Notes PDF that is available for download from theSymantec 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 correctionsPage 7: Original paragraphThe following client platforms support the SAN client: AIX, HP-UX, Linux,Solaris, and Windows, and the following media server platforms supportthe 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 fortape storage may be added in a future release.Page 7: Corrected paragraph for NetBackup 6.5.2The following client platforms support the SAN client: AIX, HP-UX, Linux,Solaris, and Windows, and the following media server platforms supportthe SAN client: Red Hat 4 Update 3, Red Hat 4 Update 5 and SLES 9 SP3Linux x86_64 and Solaris 9/10 SPARC. The SAN client is supported in thisreleasewith disk storage. Support for tape storagemay be added in a futurerelease.Page 59, Table 2-19: Original paragraphMedia server:

55About known issuesGeneral Documentation issues

You can use the following systems for the NetBackup media servers thatare attached to the SAN: - Linux - Red Hat 4.0 Update 3 X86_64 (EM64T orAMD64) - Solaris 9 and 10 (SPARC)Page 7: 59, Table 2-19: Corrected paragraph for NetBackup 6.5.2Media server:You can use the following systems for the NetBackup media servers thatare 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 NewFeatures chapter in theNetBackup6.5ReleaseNotes document incorrectlyrefers to the PureDisk Deduplication Option as PureDisk Storage Optionor PureDisk Optimization Option. These names and the correspondingdescription have been corrected and a new updated version of theNetBackup Release Notes document that is available for download fromthe Symantec Support Web site.

■ Information that expains which policy types support the client encryptionoption was not included in the NetBackup 6.5 Release Notes document. Thefollowing list shows the policies types that support encryption in NetBackup6.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 encryptioncheck box in the policy attributes interface.

■ DataTools-SQL-BackTrk

About known issuesGeneral Documentation issues

56

■ FlashBackup

■ FlashBackup-Windows

■ NDMP

■ NetWare

■ Vault

■ (ET1268273) FlashBackup incremental backups do not operate as describedin the NetBackup 6.5 Snapshot Client Administrator's Guide, page 82.

The next revision of the Snapshot Client guide contains information similarto the following:

■ For FlashBackup and FlashBackup-Windows full policies, all blocks in thedisk or raw partition (as selected in the BackupSelections tab) are backedup.

■ ForFlashBackupandFlashBackup-Windows incremental policies, completefiles are backed up based on changes to the file Modified Time or CreateTime since the last full or incremental backup.

■ For FlashBackup-Windows Incremental policies, the Modified Time andCreate Time changes are queried from the NTFS Master File Table (MFT)for File entries only. Directories are not queried. Any newly created ormodified files are backedup as complete files and corresponding directoriesup the tree are also backed up. Newly created but empty directories are notconsidered for FlashBackup-Windows incremental backups.

Warning:DuringFlashBackup-Windows incremental backups, jobs completewith status 0 but some skipped files may occur due to limitations with theNTFS file system.

TheNTFSMaster File Table does not update the Create Time orModifiedTimeof 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 theNAS_Snapshot snapshotmethod,

if backup target file systems are not mounted explicitly as NFS version 3, the

57About known issuesUNIX-specific issues

snapshot directory on the filer volume isnot accessible throughNFSas requiredto support snapshot restore. Thatmay result in failed backups, or those backupsthat appear to succeed, but are immediately expired during routine snapshotimage validation. For Solaris 10 clients, file system mount commands shouldcontain 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 ICS1.4.37.9 forHP", failed to install or upgrade during aNetBackup install. It failswith 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 supportedversion of HP-UX (PA-RISC) to encounter memory consumption issues withNetBackup processes. The degree of consumption varies and depends on yourusage pattern. In addition, it is likely that the NBEMM process is the firstprocess to stopwith a core dump. Formore information about this issue, referto the following Technote on the Symantec Support Web site.http://entsupport.symantec.com/docs/313880

Windows-specific issues■ (ET1320943) FAT32 file systems are not supported on Windows x86 and x64.

■ Product dependency notification for customers running Microsoft WindowsVista or Windows 2008 server.If you protect client (or server) systems that are running Microsoft WindowsVista orWindows2008 server, youmayneed to installMicrosoft hotfix numberKB952696. If you attempt to back up any protected files that the operatingsystemhas encrypted, NetBackup is not able to back up these files. NetBackupreports that it is unable to access the encrypted files and the backup continueswith all of the remaining files.NOTE: That does not apply to NetBackup encryption. NetBackup encryptionis separate from the file systemencryptionmeaning thatNetBackup-encryptedfiles are backed up. In addition, this hotfix is not needed for any Windowsversion before Microsoft Windows Vista or Windows 2008 server. If you are

About known issuesWindows-specific issues

58

running Vista or Server 2008, please refer to KB952696 to see if this hotfix isrequired for your operating system version

■ (ET1233823)There is aproblemregardingbackingupWindows2008encryptedfiles. That is a Microsoft issue. A NetBackup fix may occur in a future 6.5release. To avoid this issue, run NetBackup as Administrator and not as aBackup Operator.

■ (ET1557527) When installing NetBackup on a Windows 2008 VCS clusterconfiguration, theNext option on the Settings dialog is highlighted. However,if you change data on that dialog, the Next option may become grayed out. Ifyou encounter this issue, navigate through each of the cluster input fields inthe dialog. After that is complete theNext option is enabled and you can selectit to continue with the install.

■ (ET1635638) On a clustered (VCS) Windows 2008 environment, a Snapshotbackup takes longer to complete as compared to a backup on a non-clusteredenvironment. The Snapshot technology that is used in this casewasMicrosoftVolumeShadowCopy (VSS). In an engineering test environment, a substantialtime delay was noted for the VSS APIs. A single NetBackup backup job tookmore than 10 minutes to complete.Symantec is currently in discussions with Microsoft to develop a solution forthis issue. A possible fix is planned to be released in the next release of thisproduct.

■ (ET1530250) During a NetBackup 6.5 GA installation on a system that hasSymantec Endpoint Protection (SEP) 11.0 installed with the network threatprotection options enabled, your system can lose network connectivity duringthe install. That is a known Windows-only issue with the SEP MR4-MP1(11.0.4010) version. Symantec recommends that youupgrade to the latest SEP11 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 innblog.conf to a value of 51200. The value of MaxLogFileSizeKB is set to thenew value even if it was changed before the Release Update was applied.

■ If you update a clustered NetBackup server in a VCS configuration, Symantecrecommends that you run the manual patch install.

■ Configuring NOM and VxAT on the same cluster is not supported on VCSWindows.

■ When upgrading a media server using NetBackup LiveUpdate in theenvironments that have the master and the media servers that reside onseparate domains, you must stop tracker.exe on the target media server orthe LiveUpdate upgrade fails.

59About known issuesWindows-specific issues

To avoid this issue, youmust ensure that the tracker.exe is not running on themedia server before executing a LiveUpdate upgrade.

About known issuesWindows-specific issues

60

Current release contentindex


■ About the NetBackup 6.5.6 master Etrack index list

About the NetBackup 6.5.6 master Etrack index listThis section contains amaster index for all fixes that this release contains. Thesefixes are sorted according to the containers that they are in.

NB_SMJ_6.5.6.winnt.x641599744

NB_JAV_6.5.6.winnt.x641839613 1884626 1884622 1943448

NB_JAV_6.5.61599744 1839613 1884626 1884622

NB_NOM_6.5.6.winnt.IA641831176 1907862 1933026

NB_SMJ_6.5.6.winnt.x861599744

3Chapter

NB_NOM_6.5.61907862 1933026

NB_VLT_6.5.61794468 1858013 1916126 1977134

NB_DRO_6.5.61866066

NB_SMU_6.5.61595906 1599627 1639406 1723817 1785248 1805843

NB_SAP_6.5.61712349

NBLU_6.5.6.WIN146084814806961528999153642515420881547306159015915968611597208159797215997441631661163423416384781664462167525416796001704581170568417074331707868171090917113241712349171424917181441719203171968017197021722830172885417306391732542173414017342231738123173931917401551741195174495017453021745377174739917475551747569174801317523431764854176644417669171779258178161817833391785089178565917894241789558178958517896411789765179021917910961791524179286617944681796017179980418019051804988180513618068851807274180904818107561819232181930118201551821904182198418250121826305182632218270981827104182774418287691828972182993218311761831736183176118325031832613183320118332921833464183366618355401835624183570718369331836986183706618396131839711183971918406071841542184156818430491843764184387218458601846940184708418483301848666184986018499431852360185338518533941853866185621718571871857252185801318582901859377185945318601811860692186095918621221862209186230418639601864777186606618686711868678186879418701601870456187094718720751872279187228718724131872889187352218735711873581187468118767201877351187761818777591878504188023618811581881198188129118814981884626188520918862931886421188883318893261889345189021818906421891943189331118958801896534189654318966031899129189924118993961899890189989718999051899913190002019020401902371

Current release content indexAbout the NetBackup 6.5.6 master Etrack index list

62

1903062190422619046651904949190545619078621908225190841119085241909591190979019100691911562191186019126411913037191366619137991915644191564619158201916126191651319166861918715191962119217961921983192198619220361922416192270119227571926383192823019295311930100193037119324111932648193292219330261933195193358219337931934281193431419351581935275193531519382211938292193833819384071939187193922219394891940115194116319415151943162194344819436021944481194469819447571946513194654119472581947786194858919489631951005195110619521761952201195301919530621953348195423719543551954375195617919565041957566195797119579871960773196119119622531962267196233319624791966124196709919673511970866197148319717951972758197498019771341977211197741919781211978579198050719827091982758 1987803 1989335 1993398 1997132 1884622

NB_6.5.6.winnt.x86146084814806961528999153642515420881547306159015915968611597208159797216316611634234163847816644621675254167960017045811705684170743317078681710909171132417123491714249171814417192031719680171970217228301728854173063917325421734140173422317381231739319174015517411951744950174530217453771747399174755517475691748013175234317648541766444176691717792581781618178333917850891785659178942417895581789585178964117897651790219179109617915241792866179446817960171799804180190518049881805136180688518072741809048181075618192321819301182015518219041821984182501218263051826322182709818271041827744182876918289721829932183173618317611832503183261318332011833292183346418336661835540183562418357071836933183698618370661839711183971918406071841542184156818430491843764184387218458601846940184708418483301848666184986018499431852360185338518533941853866185621718571871857252185801318582901859377185945318601811860692186095918621221862209186230418639601864777186606618686711868678186879418701601870456187094718720751872279187228718724131872889187352218735711873581187468118767201877351187761818777591878504188023618811581881198188129118814981885209188629318864211888833188932618893451890218189064218919431893311189588018965341896543189660318991291899241189939618998901899897189990518999131900020190204019023711903062190422619046651904949190545619082251908411190852419095911909790191006919115621911860191264119130371913666191379919156441915646191582019161261916513191668619187151919621192179619219831921986192203619224161922701192275719263831928230192953119301001930371193241119326481932922193319519335821933793193428119343141935158193527519353151938221193829219383381938407193918719392221939489194011519411631941515

63Current release content indexAbout the NetBackup 6.5.6 master Etrack index list

1943162194360219444811944698194475719465131946541194725819477861948589194896319510051951106195217619522011953019195306219533481954237195435519543751956179195650419575661957971195798719607731961191196225319622671962333196247919661241967099196735119708661971483197179519727581974980197713419772111977419197812119785791980507 1982709 1982758 1987803 1989335 1993398 1997132

NB_6.5.61460848148069615121771528999153642515420881543088154528415901591596861159720816316611675254167960017045811707433170786817113241714249171920317196801719721172283017246031729238173063917325421734223173812317401551741195174739917475691752343176485417850891785659178942417895581789641179021917910961791524179286617998041804988180513618072741810756182190418219841825012182709818287691828964182897218299321831736183176118334641833666183407118355401835624183570718369331836986183706618415421841568184304918438721845860184694018486661849292185136018520471852360185386618562171857187185725218579201859453185971918606921861585186230418639601866912186867118686781868794187016018709471872075187227918722871872413187352218735711873581187468118767201877351187775918799571880236188520918854251886421188883318893451890218189653418965431896603189802718991291899241190002019020401902371190466519049491905456190709719075641908411190979019100691911562191186019126411915820191651319166861916729191871519196211921796192198319219861922036192270119282301932411193292219331951933793193428119351581935275193531519353781938141193822119382921938338193840719391871939222193948919401151941163194316219446981944757194651319465411947786194858919521761953019195423719543551954375195650419575661957987196119119622531962333196247919625471966124196709919708661971483197179519727581974980197721119781211978579198050719827091982758 1987788 1987803 1989335 1993398 1997132 2008084

NB_ORA_6.5.61843171 1862242 1862252 1895880 1913799 1929531 1951005 1997002

NB_NOM_6.5.6.winnt.x861831176 1907862 1933026


64

NB_JAV_6.5.6.winnt.IA641839613 1884626 1943448 1884622

NB_DMP_6.5.61801905 1809048 1881198 1889326 1908225

NB_CLT_6.5.61460848148069615121771528999153642515420881543088154528415901591596861159720816316611675254167960017045811707433170786817113241714249171920317196801719721172283017246031729238173063917325421734223173812317401551741195174433917473991747569175234317648541785089178565917894241789558178964117902191791096179152417928661799804180498818051361807274181075618219041821984182238518250121827098182876918289641828972182993218317361831761183346418336661834071183554018356241835707183693318369861837066184154218415681843049184376418438721845860184694018486661849292185136018520471852360185386618562171857187185725218579201859453185971918606921861585186230418639601866912186867118686781868794187016018709471872075187227918722871872413187352218735711873581187468118767201877351187775918799571880236188129118852091885425188642118888331889345189021818965341896543189660318980271899129189924119000201902040190237119046651904949190545619070971907564190841119097901910069191156219118601912641191582019165131916604191668619167291917710191871519196211921796192198319219861922036192270119282301932411193292219331951933793193405319342811935158193527519353151935378193814119382211938292193833819384071939187193922219394891940115194116319431621944698194475719465131946541194778619485891952176195301919542371954355195437519565041957566195798719611911962253196233319624791962547196612419670991970866197148319717951972758197498019772111978121197857919805071982709198275819877881987803 1989335 1993398 1997132 2008084

NBLU_6.5.6.UNIX146084814806961512177152899915364251542088154308815452841547306159015915959061596861159720815996271599744163166116376101637613163940616752541679600170240017045811707433170786817113241712349171424917181441719203171968017197211722830172381717246031729238173063917325421734223173812317401551741195174433917444481745311174726317473991747569175234317648541766444178508917852481785659


1789424178955817896411790219179109617915241792866179446817960171799804180190518049881805136180584318072741809048181075618193011821904182198418223851825012182709818271041828769182896418289721829932183173618317611833201183346418336661834071183554018356241835707183693318369861837066183961318415421841568184304918431711843764184387218458601846940184866618492921851360185204718523601853866185621718571871857252185792018580131859453185971918606921861585186224218622521862304186280218639601864692186606618669121868671186867818687941870160187094718720751872279187228718724131873522187357118735811874681187672018773511877759187995718802361881198188129118846261885209188542518864211888833188932618893451890218189588018965341896543189660318980271899129189924119000201902040190237119030621904665190494919054561907097190756419078621908225190841119097901910069191156219118601912641191379919158201916126191651319166041916686191672919177101918715191962119217961921983192198619220361922701192823019295311932411193264819329221933026193319519337931934053193428119351581935275193531519353781938141193822119382921938338193840719389701939187193922219394891940115194116319431621944698194475719465131946541194778619485891951005195217619530191954237195435519543751956504195756619579871959006195975519611911962253196233319624791962547196612419670991970866197148319717951972758197498019756051977134197721119781211978579198050719827091982758198778819878031989335199339819970021997132 2008084 1884622

NB_6.5.6.winnt.IA64146084814806961528999153642515420881547306159015915968611597208159797216316611634234163847816644621675254167960017045811705684170743317078681710909171132417123491714249171814417192031719680171970217228301728854173063917325421734140173422317381231739319174015517411951744950174530217453771747399174755517475691748013175234317648541766444176691717792581781618178333917850891785659178942417895581789585178964117897651790219179109617915241792866179446817960171799804180190518049881805136180688518072741809048181075618192321819301182015518219041821984182501218263051826322182709818271041827744182876918289721829932183173618317611832503183261318332011833292183346418336661835540183562418357071836933183698618370661839711183971918406071841542184156818430491843764184387218458601846940184708418483301848666184986018499431852360185338518533941853866185621718571871857252185801318582901859377185945318601811860692186095918621221862209186230418639601864777186606618686711868678186879418701601870456187094718720751872279


66

1872287187241318728891873522187357118735811874681187672018773511877618187775918785041880236188115818811981881291188149818852091886293188642118888331889326188934518902181890642189194318933111895880189653418965431896603189912918992411899396189989018998971899905189991319000201902040190237119030621904226190466519049491905456190822519084111908524190959119097901910069191156219118601912641191303719136661913799191564419156461915820191612619165131916686191871519196211921796192198319219861922036192241619227011922757192638319282301929531193010019303711932411193264819329221933195193358219337931934281193431419351581935275193531519382211938292193833819384071939187193922219394891940115194116319415151943162194360219444811944698194475719465131946541194725819477861948589194896319510051951106195217619522011953019195306219533481954237195435519543751956179195650419575661957971195798719607731961191196225319622671962333196247919661241967099196735119708661971483197179519727581974980197713419772111977419197812119785791980507 1982709 1982758 1987803 1989335 1993398 1997132

NB_NOM_6.5.6.winnt.x641831176 1907862 1933026

NB_JAV_6.5.6.winnt.x861839613 1884626 1943448 1884622

NB_SMJ_6.5.6.winnt.IA641599744

NB_BMR_6.5.61702400 1827104 1903062

NB_DB2_6.5.61747263

NB_6.5.6.winnt.x64146084814806961528999153642515420881547306159015915968611597208159797216316611634234163847816644621675254167960017045811705684170743317078681710909171132417123491714249171814417192031719680


1719702172283017288541730639173254217341401734223173812317393191740155174119517449501745302174537717473991747555174756917480131752343176485417664441766917177925817816181783339178508917856591789424178955817895851789641178976517902191791096179152417928661794468179601717998041801905180498818051361806885180727418090481810756181923218193011820155182190418219841825012182630518263221827098182710418277441828769182897218299321831736183176118325031832613183320118332921833464183366618355401835624183570718369331836986183706618397111839719184060718415421841568184304918437641843872184586018469401847084184833018486661849860184994318523601853385185339418538661856217185718718572521858013185829018593771859453186018118606921860959186212218622091862304186396018647771866066186867118686781868794187016018704561870947187207518722791872287187241318728891873522187357118735811874681187672018773511877618187775918785041880236188115818811981881291188149818852091886293188642118888331889326188934518902181890642189194318933111895880189653418965431896603189912918992411899396189989018998971899905189991319000201902040190237119030621904226190466519049491905456190822519084111908524190959119097901910069191156219118601912641191303719136661913799191564419156461915820191612619165131916686191871519196211921796192198319219861922036192241619227011922757192638319282301929531193010019303711932411193264819329221933195193358219337931934281193431419351581935275193531519382211938292193833819384071939187193922219394891940115194116319415151943162194360219444811944698194475719465131946541194725819477861948589194896319510051951106195217619522011953019195306219533481954237195435519543751956179195650419575661957971195798719607731961191196225319622671962333196247919661241967099196735119708661971483197179519727581974980197713419772111977419197812119785791980507 1982709 1982758 1987803 1989335 1993398 1997132

NB_BBS_6.5.61637610 1637613 1938970 1959755 1975605

NB_SNC_6.5.61547306171814417444481745311176644417960171819301183320118628021864692 1932648 1959006


68

Current release content


■ About Release Update conventions

■ About NetBackup 6.5.6 Release Content

About Release Update conventionsThis section contains the Release Update conventions, content, and historicalcontent that is applicable to the release.

The following list describes the conventions used in the subsections that followingthis section. Each item listed in the Current Release Update subsection describesa feature, enhancement, or issue fixed with this Release Update:

■ DescriptionDescribes a particular problem that is contained in this Release Update.

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

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

■ Additional NotesAny additional information regarding a problem is included.

4Chapter

About NetBackup 6.5.6 Release ContentThat section contains a list of the fixes and changes that comprise the NetBackup6.5.6 release.

Etrack Incident: 1829932

■ Associated Primary Etrack: 1791855

■ TITAN cases: 320-214-099 411-446-945

■ Contained in:NBLU_6.5.6.UNIXNBLU_6.5.6.WINNB_6.5.6NB_6.5.6.winnt.IA64NB_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 wherethe NetBackup Job Manager (NBJM) cancels an active job upon notificationfrom thePolicy ExecutionManager (PEM). Thatwould cause a status 223 error.



■ TITAN cases: 281-756-782


■ Description:The max_partially_full_media limitwas not enforced formultiple copy jobs.

■ Additional Notes:The max_partially_full_media limit is not enforced to be less than thenumber of configured copies for a job. For example, if themax_partially_full_media limit is configured at one for a pool, and the poolis 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.x64NB_6.5.6.winnt.x86

■ Description:The import of OpenVMS tapes from NetBackup 5.1 would fail with a status 24error on the last fragment. That was a winsock error 10054 error.


Current release contentAbout NetBackup 6.5.6 Release Content

70


■ TITAN cases: 240-949-938


■ Description:A fix was made to correct a bpjobd core dump issue to handle the jobs thatwere 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.IA64NB_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 youattempted to add or remove device drivers while you edited a Windowsconfiguration. A fix has been made to correct this issue.



■ TITAN cases: 281-715-968


■ Description:The bp.conf entry KEEP_VAULT_SESSIONS_DAYS does notwork on 64-bit UNIXplatforms 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 restorewould fail if primary volume group containedmore than one disk.

■ Work around:To avoid this issue, you can perform normal restore.


71Current release contentAbout NetBackup 6.5.6 Release Content


■ 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 thatthe bpclntcmd -ip does not fail with an unrecoverable error.



■ TITAN cases: 320-233-457


■ Description:TheDiskPool Committed Space algorithmwas inappropriate to determine thespace allocation for user backups.

■ Additional Notes:The estimated job size of user jobs (and oracle backup jobs) is computed as thespace difference between the high water mark and full capacity. In someconfigurations that can cause jobs to be throttled even in instances wherethere is a large amount of available disk space.A change has been added that enables you to change the estimated size forthese jobs to a value of your choice. You can use the following command tomake 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 anestimated size for these jobs.

■ Work around:


72

If you encounter this issue, turn off Job Throttling on the master server usingthe following command: nbemmcmd -changesetting

-DISABLE_DISK_STU_JOB_THROTTLING yes



■ Description:The ltid -tables command did not correctly report the robotic daemoninternal states with the installation of NetBackup 6.5.4 and 6.5.5 patches. Thesupport script calls this command.



■ Description:A change was made to correct an issue that caused NBPEM to crash onshutdown when life-cycle jobs were run.



■ TITAN cases: 312-166-406


■ Description:Restores appeared to fail on HP-IA64 media servers because of misleadingmessages in the progress log.



■ TITAN cases: 320-172-288


■ Description:Point-in-time restore on an SQL server would fail. Changes were made to thepoint-in-time restore batch file to correct this issue.




■ Description:A cluster failover can leave shared memory segments in memory. A changewas made to release the shared memory segments as soon as possible tominimize the possibility that a cluster failover has any issues. The user canthen 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 screenin 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 wouldsend a resource allocation request for a job to nbrb. During this period, nbjmdid not send any jobs to nbrb for evaluation. A change was made to addressthis issue.



■ TITAN cases: 220-673-643


74


■ Description:Youcanmonitor/cancel/restart individualSAPrestore streamsof amultistreamSAP restore when single job ID represents all of the streams.



■ TITAN cases: 281-530-425


■ Description:TheHighWaterMarkwasnot used in theDiskPools for aNetBackup clusteredmaster server.



■ Description:If a LiveUpdate job was started when the client was busy doing backups orrestores, the LiveUpdate job would receive a Resources Bus, error (134). Youcannot retry LiveUpdate jobs after you receive a status 134 error, however,NBPEM would attempt to try the jobs again.That fix ensures that NBPEMdoes 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 clientwith multiplexing set to a value greater than one. That failure results in astatus 25 error, "SAN client job crossing firewall fails when multiplexing isgreater than 1".

■ Work around:To work around this issue, open the firewall between the SAN client and themedia server to all ports.




■ TITAN cases: 281-653-466


■ Description:Abackupof aWindows2008 client silently skips theShadowCopyComponentsif multiple data streams are enabled.

■ Work around:To avoid this issue, do not use Multiple Data streams. Or you can specify theShadow_Copy_Components, System_State, and each drive letter in the includelist.



■ TITAN cases: 320-144-985


■ Description:When a client and server were configured with different locales, some fileswere not visible or selectable when you browsed in the NetBackup-Java userinterface running on Windows.

■ Work around:Towork around the issue, use theWindowsuser interface or the command-lineinterface.

Etrack Incident: 1987803 1954355 1974980 1916513


■ Description:A change was made to disambiguate the status 800 error codes.



■ TITAN cases: 410-595-612


■ Description:


76

After NetBackup 6.5.5 was applied, users noticed that SLP createdmanymorebatches, 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 inthe Activity Monitor.

Etrack Incident: 1938292 1993398 1957987 1938221 1978579 1961191 1944698


■ Description:That release contains thenewcommand-line command,nbdecommission. Thatcommandguides theuser through the steps that are involvedwhenyouattemptto decommission a media server.



■ TITAN cases: 411-437-832


■ Description:A successful optimized duplication can create fragments in the image catalogwith truncated disk media IDs. A change has been added to resolve thistruncation issue.



■ TITAN cases: 220-693-188


■ Description:


A change was made to correct an issue that caused an nbrmms core dump tooccur randomly.



■ TITAN cases: 281-751-073 320-178-687


■ Description:A consolidated differed ejects process would pick up only the most recentrecord for a profile from vlteject.mstr. A change was added to ensure thata consolidated eject with the deferred eject option configured, successfullyejects all of the correct media.



■ TITAN cases: 220-704-727


■ Description:The NetBackup Resource Broker (NBRB) appeared to go into an infinite loopand hang if the RB_RESPECT_REQUEST_PRIORITY parameter is set to one inrb.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 scsiLoadOrdermanually. That approach was prone to typos and very tedious. A change wasmade that allows the BMR Restore Environment to fetch the original client'sscsiLoadOrder from theBMRmaster server. Thathappens even ifmedia-basedrestores (Virtual Media as well as Physical Media) are used. Thus, in normalmedia-based restores scenarios, the user does not have to enter thescsiLoadOrder manually.

■ Additional Notes:


78

Although it is no longer needed, you can still enter the scsiLoadOrdermanually. 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 toNetBackup. The export would fail if a new line was added to the pathname ofa file that was included in the export list.A change has been added that allows the pathname to have a new line addedto it and ensure that the operation is successful.



■ Description:A change was made to ensure that redundant messages are not printed in thebpfis command.



■ TITAN cases: 320-216-908


■ Description:Exchange backupswould fail with a Status 13when backing up Public Folders,as noted in bpbrm. Before the failure occurred, bpbkar32.exe reported a faultand stopped logging.



■ TITAN cases: 320-180-378


■ Description:


Bpduplicate received an Arithmetic Exception (core dumped) if bpdbm couldnot 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 issent 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 inIBM 6000/8000 arrays. NetBackup depends on the name of that host-connectobject to identify the volume group. That change allows better scalability inenterprise environments. The following is a list of reasons to support the needfor this change:

■ Aclientmight havemultiple volumegroups for different business reasons.As the nickname needs to be unique, it is not possible to have the samename for all the host-connect objects.

■ A client might have multiple HBAs and hence the host connections needto be defined more that once. As the nickname needs to be unique, it is notpossible 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 FlashCopyrelations.

Customers should not be constrained to have only one host connection andthat it must be the same as the hostname.



■ TITAN cases: 281-889-782



80

■ Description:A change was made to address an issue that caused nbstserv to frequentlyterminate after a NetBackup 6.5.5 patch install. That occurred when theduplication manager submitted a job that had images from different storagelifecycle Policies (SLPs).

■ Work around:If you encounter this issue, you should prevent mixing images from differentimages in a duplication job, so this log message does not get hit.In theSLPconfiguration file (netbackup/db/config/LIFECYCLE_PARAMETERS)set the following parameter as follows:DUPLICATION_GROUP_CRITERIA 0



■ TITAN cases: 220-625-050


■ Description:If theNetBackup clientwas configured to excludeExchange-related files (*.logor *.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 thevolume configuration of an ACS library may fail.

■ Work around:Use the vmupdate command line programor theWindows or JavaGUI instead.



■ TITAN cases: 281-791-148 290-460-374

■ Contained in: NBLU_6.5.6.UNIX NBLU_6.5.6.WIN NB_6.5.6.winnt.IA64NB_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 singlemount point with 53 disks.



■ Description:Anyone who used a Windows master server cannot configure a policy to useFIMs that were released in NetBackup 6.5.2 and NetBackup 6.5.3.



■ TITAN cases: 320-190-450


■ Description:A change was made to ensure that the Windows user interface filters on theStart 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 withan integrated Smart Array Controller. That issue only occurred for certainfirmware versions of the Smart Array Controllers.



■ TITAN cases: 281-762-843 410-826-062 411-367-815


■ Description:A changewasmade to address an issue that occurred because the IP addressesthat were not defined in the bp.conf with server entries were used.



82


■ Description:A change was made to address an issue that caused a BPFIS core dump on aSnap-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 numbermismatch that sometimes occurred because of coherency issues. To resolvethis issue retry the comparison after a sleep(1).



■ TITAN cases: 281-748-608 410-689-572 410-874-557


■ Description:

DFSR backups can fault in bpbkar32.exe, in addition, the following two issueswere found:

■ DFSR backups that cause missing files from the browse for restoreoperation.

■ Issues were found with the backup of multiple DFSR stores in that eachhad the same named subdirectory.


■ Contained in: NBLU_6.5.6.UNIX NBLU_6.5.6.WIN NB_NOM_6.5.6NB_NOM_6.5.6.winnt.IA64NB_NOM_6.5.6.winnt.x64NB_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 thenbstlutil 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.5and 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 installpath/db/jobs/restart directory.



■ Description:A change was made to fix an issue that caused NBJM to crash on startup if itcould not communicate with NBRB.



■ TITAN cases: 281-795-539


■ Description:The vcbvmname process was called if the name existed in the cache file.



■ TITAN cases: 230-680-297 411-041-609


84


■ Description:TheNDMPalternate restore did notwork correctlywith NbWin.exe if the pathcontains Japanese characters.

■ Work around:If you encounter this issue, you can use either of the following twoWorkarounds : - Set the volume on the filer to UTF-8. - After a restore issueoccurs, convertALTPATH.xxx fromUTF-8 toShift_JIS and then run the restoremanually with the file.



■ TITAN cases: 281-686-677

■ Contained in: NBLU_6.5.6.UNIX NBLU_6.5.6.WIN NB_6.5.6.winnt.IA64NB_6.5.6.winnt.x64 NB_6.5.6.winnt.x86 NB_CLT_6.5.6

■ Description:A restore of an Exchange 2007 backup image from Backup Exec 11d did notwork if the user used NetBackup 6.5.4 to restore this image to an Exchange2007 Recovery storage group .



■ Description:A change was made to address an issue that caused catalog backups to failwith status 124 error.



■ TITAN cases: 320-199-975


■ Description:A file read failedwhenbacking up aCIFS share onCentOS client. That occurredbecause the CentOS client did not correctly handle the listxattr system callfor the CIFSmounts. That fix allows the IGNORE_XATTR bp.conf entry to ignorethe extended attributes during the backup, and allows the following touch fileto ignore them during restore.


/usr/openv/netbackup/IGNORE_XATTR



■ TITAN cases: 220-700-187


■ Description:TheNetBackupResourceBrokerwouldde-allocate the fiber transport resourcespre-maturely after a successful span.



■ TITAN cases: 240-988-882


■ Description:A change was made to report the correct error number frombpbrm.c:readline() instead of one coming back from check_for_signal().



■ TITAN cases: 220-693-144 240-998-887


■ 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, snappedvolumes would accumulate on the intelligent disk device.



■ TITAN cases: 220-697-693


■ Description:


86

Fixed a status 13 error that occurred when an attempt was made to back upEnterprise Vault Monitoring database on a remote SQL server.



■ TITAN cases: 220-649-766

■ Contained in: NBLU_6.5.6.UNIX NBLU_6.5.6.WIN NB_6.5.6.winnt.IA64NB_6.5.6.winnt.x64 NB_6.5.6.winnt.x86 NB_SAP_6.5.6

■ Description:

If all the following conditions are true, thenmultiple jobs appear in theActivityMonitor, 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 includedin it match any of the files in the input file that the brbackup commandsupplies.

■ 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 ShadowImagesnapshot method can fail because of a command-line limitation. That issue isresolved.



■ 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 fileswere selected for backup but were removed before the backup occurred.



■ Description:The stserv script did not honor the maximum fetch limit. The result of thisissue caused a memory exhaustion and a system crash. A change was made tocorrect this issue.



■ TITAN cases: 281-737-803

■ Contained in: NBLU_6.5.6.UNIX NBLU_6.5.6.WIN NB_6.5.6.winnt.IA64NB_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 theNetBackup domain and its configuration for network issues, performance, andbehavior. It addresses hostname lookup and connectivity between NetBackuphosts and their role within the NetBackup domain.



■ Description:NetBackup Job Manager (NBJM) could deadlock if it was shut down while itinitialized with the NetBackup Resource Broker (NBRB) on a startup.



88


■ 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 notget restored on aMac OS X 10.5 platformwhen ou attempted to restore acrosshardware platforms (PowerPC to and from x86). An incompatibility betweenplatforms 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 HFSattributes 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 HatEnterprise Linux 4 (RHEL4) Update 8 and RHEL5 Updates 3 and 4.In the RHEL 5 U4, the released iso .discinfo file contained the string, RedHat Enterprise Linux 5.4 and thecreatesrt.conf file contained anRHEL-5entry with string, Red Hat Enterprise Linux 5. That caused the load mediato 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 serverto add ".4" (or .3 for 5.3) in the string. For example, the following string showsRHEL 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 enablesthe creation of RHEL5.4 SRTs. However, this change disables the creation ofRHEL5.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 fromthe NOM console.



■ TITAN cases: 312-182-724


■ Description:A FlashBackup of a Hyper-V guest virtualmachine (VM) failed if the guest VMwas specified with a volume GUID instead of a drive letter.

■ Work around:If you encounter that issue, replace the volume GUIDs with the associateddrive 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 wizardto archiveOracle, the processmay fail on an11gR2databasewith the followingtypes 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


90

To work around this issue, move bporaexp to a new location and create asymbolic link from bporaexpto bporaexp64. See the following commands:

cd /usr/openv/netbackup/bin mv bporaexp bporaexp.orig ln -s bporaexp64 bporaexp

That issue is resolved in the NetBackup 7.0 release.Please note that for 32-bit Linux x86 platforms, the oracle_link scriptmay notproperly create the necessary symbolic link to the NetBackup libobk library.

To work around this issue, go the Oracle home directory and perform thefollowing 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. Thenbrbutil commandchanges enable auser to see all thepipes that are orphaned.

■ Work around:If you encounter this type of issue, use the SQL script to view and resetorphaned pipes.



■ Description:A change was made to address a timing issue with bpbkar32 on Windows toensure that a crash does not occur at the end of hot catalog backups.



■ TITAN cases: 410-604-465


■ Description:


A change wasmade to ensure that the correct media server is selected for SLPduplication. That fix addresses an issue where the wrong media server wasselected for SLP duplication and produced the following error.

media write error(84):Duplication error with PDDO



■ Description:A change was made to ensure that you can uninstall NetBackup 6.5.6 whilethe oracle.exe executable runs.



■ TITAN cases: 281-708-675 411-752-618


■ Description:In theBackup,Archive, andRestore user interface, theSearchBackups featurewould fail to quickly locate the files to restore. That occurred primarily forthe large images that containedmany files. In addition, the followingmessageappeared.

WARNING: unable to obtain list of files using specified search



■ TITAN cases: 320-175-882


■ Description:A change was added to ensure that Type2VCBBackups no longer fail on oneCitrix VM.



■ TITAN cases: 312-232-956


92

■ Contained in: NBLU_6.5.6.UNIX NBLU_6.5.6.WIN NB_6.5.6.winnt.IA64NB_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 letterthen the BMR Prepare Restore operation of client's configuration failed. Thefollowing message would appear:

PTR fails with error that NBU volume is not included in the

restored volumes



■ TITAN cases: 281-619-629


■ Description:Large SAPRestores incorrectly reported failures in brrestore log, even thoughall 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, therestored file would have an incorrect size. A change has been added to correctthat.



■ Description:


That release contains an updated version of the embedded NIC driver for theBroadcom 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 thefirst 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 followingerror:

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



■ TITAN cases: 410-630-281


■ Description:A lackof an indexon theEMM_AllocationStatus table causeddelays in resourceallocation.

■ Work around:If you encounter this issue, prune the nbemm allocationStatus table withthe nbemm -errorsdb.



94


■ TITAN cases: 312-189-425


■ Description:MappedFullVMbackups on theweekend can cause auser to runout of nonpagepool memory.A change was made to the logging code segment to not enable logging whenan error is encountered. The code segment is disabled for Windows, andremains 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 abackup, the Oracle process failed even after all the files were backed up. Thejob 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


■ Description:Windows-based servers would fail the restore of KMS encrypted images ifmore than one image was required.




■ Description:When a refresh or refresh all is selected on the Drives tab of the ActivityMonitor, the driveswere shownasAVR control for a time.However, the correctname is shown under Control column after sometime.



■ TITAN cases: 320-231-968


■ Description:The bpcatlist command would crash on HP-UX IA64 platform when youattempted to retrieve images from a catalog archive.

■ Work around:If you encounter that issue, browse the contents of an archive backupmanuallyand restore them with the bprestore.


■ TITAN cases: 230-689-911 281-415-262


■ Description:The Drive count was zero for the Application Cluster storage units.

Etrack Incident: 1849943 1915646 1915644


■ TITAN cases: 240-954-249


96


■ Description:Changed the default behavior to back up all transaction logs for an Exchangesnapshot backup to TRUE.

■ Additional Notes:That change was made after findings from Microsoft that replication replaymay require all logs after a restore.


■ Contained in: NBLU_6.5.6.UNIX NBLU_6.5.6.WIN NB_6.5.6.winnt.IA64NB_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 sessiondirectory permission issues. Even if you configured the following file with theappropriate 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 toenable the Vault_Operator to perform ejects and reports.



■ Description:An issue was fixed that caused core files to be created when a backup was runwith open file backups enabled on IA64 platforms.



■ Description:During a Windows open file backup, if the shadow storage was found asunbounded then NetBackup changed it to a value between 300-1024MB. Thatvaluewas not sufficient to holdmultiple snapshots on aWindows Server 2008platform. That caused the snapshots to be silently deleted . The fix does notchange the shadow storage.




■ TITAN cases: 281-875-323


■ Description:A changewasmade to the ntstlutil diskful command line option to handle64-bit capacity values as input on AIX systems. That command is anundocumented command.



■ TITAN cases: 281-893-652


■ Description:A changewasmade to ensure that BPRDcan remove the old logs that are largerthan 2GB.


■ Contained in: NBLU_6.5.6.UNIX NBLU_6.5.6.WIN NB_6.5.6.winnt.IA64NB_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 tofail for TIR images.



■ TITAN cases: 411-265-740


■ Description:A full OS recovery of a Windows 2008 or 2008R2 server would result innon-bootable system.

■ Work around:To avoid that issue, do the following when you want to restore the systemdrive of a Windows 2008 or 2008R2 server. Remove the check from the boxfor the Boot folder on the system drive (for example, C:\Boot).

Etrack Incident: 1987788 1851360


98



■ Description:That release of NetBackup contains SAN Client-related fixes.



■ TITAN cases: 240-758-574


■ Description:Fixed a FlashBackup SFR-restore issue that caused a status 5/85 error eventhough 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 84error message.

Cannot write image to disk, Invalid argument.



■ Description:The EMC_Timefinder_* operation did not work onHP-UX 11.31 systems if theStorage 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 jobID.



■ TITAN cases: 320-220-208


■ Description:When disk backups are run on a MEDIA_SERVER, bptm encounters non-fatalerrors (errors that are ignored) while it gets Data Classification informationfrom bpdbm. Due to these errors, the images that are created are not taggedwith Data Classification information. That may have some undesired effectsfor later processing of the image as per storage lifecycle Policy or DataClassification.The fix gets rid of the error. It changes the bpdbm authorization table to allowMEDIA_SERVER to query for the Data Classification information.



■ TITAN cases: 281-680-774


■ Description:A change wasmade to address intermittent status 83 errors with KMS andHPLTO4.



■ TITAN cases: 320-191-828 320-211-360


■ Description:A change wasmade to correct an issue that caused vltadm to core dumpwhenyou attempt to edit the policy list on a new profile.



■ Description:


100

NBPEM terminated when an NDMP or SnapVault policy referenced anon-existent storage unit. For instance, if the storage unit was deleted afterthe 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 newACSLS8.0media types that includeLTO5.



■ TITAN cases: 312-189-247


■ Description:The timeout value in the boot loader section of boot.ini was always defaultset to 5. A BMR Restore of a Windows client would not set to its original valueafter a successful BMR restore.



■ TITAN cases: 320-217-552


■ Description:Following an Exchange GRT backup, the event log DLLs were invalid for theese process. Because of this issue the user cannot read the event log entrieswith 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 queryQueryHostsByRobotNumAndDriveType().



■ TITAN cases: 320-166-089


■ Description:Fragments for staged backups (non-SLP) were left in the EMM database whenimages 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 diskcopy had already expired.

Etrack Incident: 1947258 1941515 1930371 1953348 1948963 1957971 1891943


■ TITAN cases: 220-701-553


■ Description:The release contains the additional restore capabilities that are available inNetBackup 7.0 for SharePoint Granular restores. That enhancement enablesusers to restore SharePoint lists, sites, subsites, web parts, and theircorresponding metadata.



■ TITAN cases: 410-596-478 410-659-783


■ Description:


102

A change was made to bpdbjob to resolve a core dump issue with the -fastoption.



■ TITAN cases: 281-889-342


■ Description:

If the system gets one of the following errors, then during the Oracle backupor restore operation the log function attempted to log the error message andthe 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 imagescount in EMM database.



■ Description:An Exchange Off-host backup would sometimes fail with a message thatESEUtil is missing. That would not occur when the Exchange ManagementTools were installed on the alternate client.Without them, the problemwouldoccur occasionally.



■ Description:


A change was made to correct an issue that caused an occasional core dumpto occur with nbstrserv.


■ TITAN cases: 410-638-028


■ Description:ALegacyTimeFinder backup failedwhenPowerPathwas installedwithStorageFoundation.



■ TITAN cases: 240-910-389 281-737-126 410-599-152


■ Description:The topology view on a Windows x64 master server did not show drives aftermultiple 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 Hat5.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 imagelocally on a computer and then provide that path.



■ TITAN cases: 281-406-867


■ Description:


104

Disk imports ofVMWarebackupswere imported asVMWareType0, regardlessof the type that they were backed up as.

■ Work around:Modify the image header file after the import to reflect the correct type andto 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 incorrectmedia server, disk storage unit resources to read the component backup.In cases where there are basic disk or NearStore storage units with identicalpaths ondifferentmedia servers, aNetBackup synthetic backup fail. The failurestatus was a status 609. That would most likely happen when someincrementals for the schedule are on each storage unit.

■ Work around:Towork around this issue, give disk storage units unique pathnames. Ormakesure that a single synth policy does not use identical disk storage unit pathson 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 acrash of the associated Oracle process.



■ TITAN cases: 240-969-283



■ Description:A change was made to address a memory leak in the FatDbObject query.



■ TITANcases: 220-468-715220-598-117281-670-786290-987-471311-975-913410-882-560 411-810-478


■ Description:A change was made to ensure that NDMP backups of EMC Celerra filers onlysucceed when they are suppose to. Backups would silently succeed when theyshould 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 IncrementalFBU backup images were selected in Backup, Archie, and Restore interface.



■ TITAN cases: 320-216-005



106

■ Description:The NetBackup Enterprise Media Manager (nbemm) would hang in somescenarios 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 roboticlibraries that have more than 300,000 media.


■ TITAN cases: 411-445-411


■ Description:A change was made to correct a memory leak inServerGroupObject::createObect().



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



■ TITAN cases: 312-158-981 411-117-794


■ Description:Themailmessage restore toHebrewcharacter setmailboxes failed onWindows2003.

■ Additional Notes:That fix enables an ASCII-based mailbox compare to occur so that restoressucceed with Hebrew character mailbox accounts. A registry key needs to becreated.




■ 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 restorefailed, 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 neededto 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, youdonot receive the followingerror message.

Please Delete Disk Objects First




108

■ Description:Only one backup ID is canceled at a time from same SLP. However, if a userissued 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


■ Description:An issue with bpfis caused an Application fault when an attempt was madeto 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 underthe Active filter.



■ TITAN cases: 311-977-621


■ 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 thefollowing 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 thesource VTL media. That did not allow the VTL DirectCopy to occur.

■ Work around:If you encounter this issue, use a single pathed VTL drive.



■ Description:A change was made to address the length of time it took for the SnapshotClient 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 alsocontains Support for scalable and big volume groups introduced in AIX 5.3.Finally, this release contains the correct UDID generation for IBM DS8000arrays.



■ TITAN cases: 220-696-315

■ Contained in: NBLU_6.5.6.UNIX NB_SMU_6.5.6


110

■ 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. Thechange includes a better error message.



■ TITAN cases: 320-199-474


■ **Description:Three-character 3pc.conf entries fromDevice # and affects if a vendor's devicereturns more than FFF LUNS (4095). NetBackup would use SCSI inquiry VPDpage code 80 data, a unit serial number as a unique identifier to correlate thedisks to back up between the client, and the media server for Media ServerCopybackups.When the Symmetrix device IDnumber is greater than or equalto 4k (4096), the serial numbermay not be unique anymore. In addition, whenthe Symmetrix device ID number is greater than 8k, the serial number maycontain numeral ASCII characters, such as the pound sign (#). That can causea Media Server Copy backup failure since the portion of the serial numberafter the pound sign (#) was interpreted as a comment of the entry in the3pc.conf.

That fix uses the SCSI inquiry VPD page 83 data, device identifier which doesnot have the issues described above. For this fix towork youmust consistentlyset the SPC-2 flag to disable or enable for the Symmetrix ports. These portsare used on the client and the media server, because different SPC-2 settingsgive a different page code 83 device identifier. Also, the fix isbackward-compatible to use the SCSI inquiry VPD page code 80 serial numberin case the client does not have disks that have a Symmetrix ID greater than4095.



■ TITAN cases: 240-967-547



■ Description:A change was made to address an issue that caused NBPEM to assert in theScheduler::getLBDNoRefCnt when a single-stream job was restarted withmultistreams enabled.



■ TITAN cases: 240-988-215 281-611-743


■ Description:A backup with Hitachi_ShadowImage on an alternate host would fail with astatus 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 madeto fix an issuewith the LDEV-to-LU conversion thatwas done for the secondarydevice. That conversion was not required.


■ TITAN cases: 240-951-955


■ Description:After a reboot, the NetBackup Key Management Service (KMS) did not restartproperly. Symantec Private Branch Exchange was added to this release as aservice dependency to KMS.



■ TITAN cases: 281-637-895


■ Description:An NDMP restore would fail with an unimplemented error code 114. Theproblem occurred only with a backup that had multiple paths, and one of the


112

paths spanned fragments. In addition, the restore involved more than one ofthe 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 timethe header file is restored. However, the operating system then removes itwhen the main file is restored. That sequence of events caused an incompleterestore.

■ Work around:If you encounter this issue, run a second restore with the overwrite featuredisabled.



■ TITAN cases: 240-984-409


■ Description:A restore of the DFSR Data would not maintain the file creation andmodification dates.

■ Additional Notes:There is an issue with DFSR.exe, a Microsoft deliverable. After tar32.exerestores a DFSR file, the DFSR.exe program opens the file for GENERIC_READwhich causes the file access time to be set to shortly after the restore. Thereare no ways to prevent this from happening.



■ TITAN cases: 220-670-638


■ Description:


The exit-notify scripts were not working properly. The exit notify scriptswould only run after all streaming attempts completed. Before NetBackup6.5.2, the scripts run after every stream.A change was made that adds a new argument to the backup_exit_notifycommand that indicates if a retry is performed. In addition, an argument wasadded to theparent_end_notify command that indicates thenumber of streamsthat were started.



■ Description:Embedded files in a compressed folder on a virtual machine withnon-contiguous allocation did not map correctly.



■ Description:The import of the Exchange database images would not properly browse forgranular operations.



■ TITAN cases: 281-537-793


■ Description:A change was made to ensure that the nbstlutil utility does not receive aCORBA exception with NBAC enabled.



■ TITAN cases: 320-180-691


■ Description:A changewasmade to address an issue that caused bpbrm to core dumpduringa VM VCB backup because bpfis core dumped.



114


■ Description:The CDP FIM did not work with Storage Foundation version 5.0*. That wasdue to a change in the output of some of the VxVM commands.




■ Description:The vendor-unique, library handling of bar codes caused inject operations tofail. That issue required the user to perform CLI operations to work aroundthe issue. A change was made to correct this issue.



■ TITAN cases: 220-704-762 320-220-187


■ Description:

When SQL a database has period in the name, the image name appears to usea slash as a separator instead of a period. The following issues would occur:

■ You cannot select the database for restore inNetBackupMSSQLClient userinterface. In addition, you would receive the message, "Please enter aninteger between 1 and 31."

■ The dbbackup.exe generated a core dump if you selected a transactionbackup image to restore.

■ Work around:If you encounter this issue, you can restore if you create a batch file manuallyand run it.



■ TITAN cases: 410-645-359


■ Description:


A change was made to address an issue that caused an SLP duplication job tofail with a status 50 error, however it continued to duplicate images.



■ Description:Granular ActiveDirectory/ADAMbackupswould 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. Thatwas not a data loss issue since the full database is backed up but the granularfunctionality was not available.



■ Description:Upgrading and downgrading scripts for database were added to NetBackup6.5.6.



■ TITAN cases: 312-075-563


■ Description:The Allow Multiple Data Streams option on Windows would not work whenthe include file contained multi-byte characters before a wildcard character .




■ **Description:A change was made to address an issue with NDMP snapshot backups. Thebackups completed successfully, however the image was deleted.





116


■ Description:A change was made to ensure that you can access the FT media serverinformation in the user interface with Veritas Security Services enabled.



■ Description:Snapshot-only restores failed with a private provider error on a rollbackattempt.



■ TITAN cases: 220-506-306


■ Description:A change was added to correct a statistical problem with how the client's datawas transferred to media during multiplexed backups. An unfair number ofblocks 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 thatcontained basic disk storage units was decommissioned. That fix allowsnbdelete to honor a -force option and remove those images that remain fora 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 andhang.

■ Additional Notes:DNS delays to resolve short hostnames cause this issue. That indicates one ofthe DNS servers did not function correctly. You should isolate and fix theproblematic DNS server.



■ TITAN cases: 281-644-467


■ Description:A changewasmade to address an issue that caused the Lotus agent to complainof 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 nowcorrectly installs the CLT release update.




118

■ TITAN cases: 320-217-862 411-407-917


■ Description:FlashBackup Window restores would fail with the following message in thebprd 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 hangat startupwhile the allocation databasewas validated. That caused the systemto be inoperable, particularly if there were a large number of outstandingallocations when the system was shut down.

■ Additional Notes: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 processesin its group or session to terminate on startup .



■ TITAN cases: 281-609-247


■ Description:The Backup of SQL-Server mirror database failed with a status 2 error eventhough it was not intended to back up any data.



■ TITAN cases: 320-178-387


■ 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 whenApp_Clusters were in vault profiles.


120

■ Additional Notes:- Make sure that no vault sessions(jobs) are in progress. - Shut down thenbvault service. - Copy the original binaries for the backup. - Copy the givenbinaries 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 allstorage unitswith bpstulist -U. - Delete all StorageUnits that are associatedwith the Application Clusters. - Delete lines for app_clusters in vault.xml

file. - Start Vault by running nbvault. - Verify the nbvault-upgrade log tomake sure that it completes successfully. - Recreate all Storage Units that areassociated with the Application Clusters. - Update all policies that referencethe storage units that are associate with the Application Clusters and pick theStorage Unit to update the pointers again.



■ Description:Restores of the virtual machines that use Volume GUIDs for the path namefailed because the names were cataloged with the \\? string.





■ Description:With anOracle backup, all of the streams failed with an error 43 in bptm, error13 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 sharedresource tree (SRT)was used. The restore failedwhile amessage aboutmissinglibrt.so.1 was given.




■ Description:TheVSS snapshots thatwere taken to backupEnterpriseVault datawere takenwith the auto provider option. That created a hardware snapshot if it wasallowed. Currently, that has been modified to always take snapshots withsystem provider for Enterprise Vault backups.



■ Description:The restore of an Exchange database that has [] or {} in the database name failswhen 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:AnOracle job failedwith a status 40 after exactly twohours even though bpbrm

had previously exited with a status 0.



■ TITAN cases: 281-745-939


■ Description:DFS replication groups, on the same server, with same folder names were notbeing backed up and resulted in a loss of data.


122

In the following example, the \home folder under DataStore2 was not backedup because it shares the same name as the \home folder under DataStore1.

DataStore1\home DataStore2\home

■ Work around:To avoid this issue, donot have twodata storeswith subdirectories names thatare the same.




■ Description:The Drive Name Seed configuration did not work from the user interface orthe 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 failwith 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.6NB_NOM_6.5.6.winnt.IA64NB_NOM_6.5.6.winnt.x64NB_NOM_6.5.6.winnt.x86

■ Description:


A change was made that enables you to see the user name and password forthe 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 aPureDisk DR Backup initiated.

■ Work around:If you encounter this issue, increase the number of streams that the PureDiskDR backup uses so that it completes before the socket timeout occurs.



■ TITAN cases: 281-813-229


■ Description:The NetBackup Administration Console for Windows did not show all of thedrive 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, andRestore user interface (jbpSA), a DB2version 9.7 instance did not enumerate.


124



■ TITAN cases: 320-222-100


■ Description:Bptm and bpdm can hang when a user attempts to restore backups from whichTIR information had been pruned.

■ Work around:If you encounter this issue, restart all services or stop the hung process, andthen rerun the restore.



■ TITAN cases: 240-748-094


■ Description:Processes would fail with a status 225 (text exceeded allowed length) whileworking with the backups that were created before NetBackup 6.5.4 and hada keyword value that was exactly 128 characters long.



■ TITAN cases: 220-700-176 312-202-944 410-658-066


■ Description:An attempt to restart a suspended job with VSS and VSP did not back up theopen 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 triedto run vault commands.

■ Additional Notes:-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 specifiedlocation. - Start the nbvault service.



■ TITAN cases: 220-694-437


■ Description:On a status 96 error code the backup_exit_notify script does not run. TheBACKUP_EXIT_CALLED file does not get created.

On a status 96 error code the backup_exit_notify script does not run. TheBACKUP_EXIT_CALLED file does not get written at the end of the job with the96 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 thecorrect policy name. In addition, the Duplication jobs that were submitted bySLP's would not respect the MAX_KB_SIZE_PER_DUPLICATON_JOB limit withinbpduplicate.



■ Description:In case of a manual catalog backup, if the second child job was Canceled, theparent job remains in an active state forever.



■ TITAN cases: 312-194-510


126


■ Description:A change was made to ensure that shadow copy backups do not fail on IA64platforms.



■ Description:The EMC_Timefinder_* FIMwas not supportedwith Solution Enabler, version7.0 or higher. As EMC plans to EOL older versions of Solution Enabler,NetBackup should support newer version. A change was made to ensure thatNetBackup supports Solutions Enabler 7.0 for snapshots.


■ Contained in: NBLU_6.5.6.UNIX NBLU_6.5.6.WIN NB_6.5.6.winnt.IA64NB_6.5.6.winnt.x64 NB_6.5.6.winnt.x86 NB_CLT_6.5.6

■ Description:That release ofNetBackup contains anupdated version of the nbsuutility. Theversion number is version 1.3.

■ Additional Notes:The nbsu 1.3 utility is now available for the Mac OS X platform.



■ Description:A change was made to ensure that NetBackup does not change the VSSassociation settings.



■ Description:Jobs could be left in thewaitingforRetry state forever if NBJMwas shut downwhile NBPEM tried to expire the jobid. That caused the state to change toDone.




■ TITAN cases: 240-897-124


■ Description:The bpcd -standalone command would core dump and create defunctionalprocesses.



■ 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 userinterface.



■ TITAN cases: 230-708-303


■ Description:


128

The xbsa.dll library would free the allocated memory for the compressionbuffers twice if the backup job failed with status 96.

■ Work around:If you encounter this issue, disable the client compress attribute.



■ Description:A changewasmade to address a status 41, Network connection failed errorthat occurred with VSS backups against large Information Stores .

■ Work around:If you encounter this type of issue, increase the client read timeout to a valuelarge 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 werecreated 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 failwith the following error message.

Operation would block




■ Description:If a deactivated SLP has too many images (for example, more than 10,000) itcould prevent scheduling any duplications. A changehas beenmade to correctthis issue.



■ Description:Restore jobs for UNIX and Linux clients have the following warning messagein 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 isrun to a UNIX and Linux client.

■ Work around:If you encounter that issue, ignore the message, no other action is necessary.



■ Description:A VMWare backup can finish with a partial success. That occurs because ofan error in how embedded files are mapped in a compressed volume or folderand if the allocation is split into two extents.



■ TITAN cases: 281-782-311


■ Description:After a BMR Restore of a client system, the system's clock was set ahead orbehind by a fewhours. The exact amount of time bywhich the clockwas offset,dependedupon theTimezone of the client system. It also depended onwhetherthe client's Timezone had a DST variant.



■ TITAN cases: 410-650-640


130


■ Description:A change was made to ensure that you can restore from the fragments thatare greater than 1 TB.



■ TITAN cases: 320-218-496 411-340-481


■ Description:While savingaTransaction log/Differential-based,MOVEbatch file, thepromptdid not offer to open the file in Notepad. In addition, the Restore selectedobject or Verify backup image but do not restore option for the Transactionlog/Differential-based batch file did not show restores were set on the promptthat 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 WindowsOpen File Backup (WOFB) is in use.



■ TITAN cases: 312-167-592


■ Description:A comparison of the kilobytes value of the job database was performed. Theresult showed that the kilobytes value of a remote NDMP backup job was 1kilobyte 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 sharedresource tree (SRT). In case of BMR ISOs for Linux, if the ISO is used by thevirtual 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 restoreenvironment:

SRT: ERROR: No devices listed in /proc/sys/dev/cdrom/info

■ Work around:The traditional Media Boot mechanism still works. For example, burn the ISOon a CD-ROM and boot the system.



■ Description:A change wasmade 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 createsthe Batches for Duplication.



■ Description:A change was made to ensure that the duplication of NDMP images from Diskto Tape no longer fails.

■ Work around:If you were to encounter an issue like this, set the SIZE_DATA_BUFFERS_NDMPparameter to the size required (for example, 65536).



■ Description:A fix was added to ensure that all multiple encryption descriptors, that someencryption-capable drives produce, are handled correctly.


132



■ Description:The Jobdetails of a restore operation showed errors andwas seen as incompletein the Activity Monitor as the progress log information was not sent due to alarge 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.




■ **Description:VMWare Consolidated Backup (VCB) type 0 backups returned a status code 0even though there was no data to restore.

■ Work around:To avoid this issue, do not perform drive exclusions of affected Windowsclients.



■ 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.6NB_SMJ_6.5.6.winnt.IA64 NB_SMJ_6.5.6.winnt.x64 NB_SMJ_6.5.6.winnt.x86

■ Description:The JavaGUI file browserwould hang if you browsed a directory that containsa 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 changewasmade to ensure thatVault does not recallmedia from the volumegroups 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 letyou change the policy default volume pool directly and can cause policycorruption.



■ TITAN cases: 320-161-355


■ Description:A change was made to client-side encryption for the following:


134

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 anerror 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 wereone or more pre-NetBackup 6.0 media servers in the NetBackup domain. Insome 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 beaccepted in thepolicy. A changewasmade to the bpplifo command to addressthis issue.



■ Description:A change was made to correct an issue that caused PEM to crash when heapchecking is ON. The same problem also caused a crash during normaloperations.



■ 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 thenetwork host-name look-ups were slow.



■ TITAN cases: 240-917-933

■ Contained in: NBLU_6.5.6.UNIX NBLU_6.5.6.WIN NB_JAV_6.5.6NB_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 theDevices Monitor.The check for NB_FEATURE_PURE_DISKwasnot present inNetBackup 6.5.3, andcaused this issue. The fix in this release provides the NB_FEATURE_PURE_DISKand 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 notrenamed.



■ TITAN cases: 312-132-747


136


■ Description:The offline timeout does not clear all of the locks and causes a failover whenoffline times out.



■ Description:Backup of an invalid path caused a backup failure for NDMP 3-way. The jobshould 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 countlimit.The read side of the opt dup duplication jobs was not counted against the I/Ostream limits, and did not queue if the limit had been reached for a volume orcaused other jobs to queue.



■ TITAN cases: 281-749-891


■ Description:No file-level informationwas available on theDdrive after themappedFullVMbackup completed with a Status 0.



■ TITAN cases: 281-635-957



■ Description:Vault eject andVault reports were incorrect when only the Vault profile namewas supplied.



■ Description:A change was added to address an issue that caused NBPEM to crash on a diskfull condition while new jobs were run.



■ TITAN cases: 312-174-077


■ Description:The BasicDisk plugin gets an incorrect value forTotalCapacity and freespacein AIX for large file systems.When a basic disk storage unit with more than 128TB capacity is used, itsTotalCapacity 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 withcommon media at the duplication step. A violation of a precondition on thebatches attribute caused the error.

■ Additional Notes:Vault would fail tomerge tape batcheswith varying retention levels under thefollowing circumstances:- Common media were found between batches -ALLOW_MULTIPLE_RETENTIONS_PER_MEDIA = YES




138

■ TITAN cases: 411-184-061


■ Description:A fix has beenmade to ensure that you can export the JobSummarybyStatusreport data to CSV.



■ TITAN cases: 281-715-561 320-202-873 410-990-189


■ Description:Allows multiple simultaneous snapshots for VMWare backups, if thenoSnaplock registry entry is present.

The touch file, MaxVMWareJobs, in the root NetBackup directory controls thenumber of jobs that are submitted to the proxy. That file should contain avalue of 60 divided by the maximum number of volumes in a single virtualmachine. For example, if you have a computer with three drives the file valueis 20.



■ TITAN cases: 220-689-207


■ Description:Backupof theWindows2008ADserver failedwith aStatus 71using the backupnetwork.

■ Work around:To avoid this issue, use the client name and interface that matches thecomputer 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 status13 error if it encountered a corrupted image header.



■ Description:The bpbkar32 process crashed when throttling parameters were used for thebackup.



■ Description:During the abort process of the active session (nbstutil -force) nbstservcan continue to fetch images for processing. That issue can delay the actualcompletion of the request.



■ TITAN cases: 220-686-180


■ Description:A client-to-media server communication problem happened intermittentlyand caused a job to run forever as opposed to a failed job. bpbkar did not takeinto account that it may not receive all four bytes on the read, which causedthe problem.



■ TITAN cases: 312-139-798 320-222-394


■ Description:A changewasmade to correct and issue that caused the bprd log to fill upwithmsgbackup messages.



140


■ Description:That Release Update contains updated Sybase ASA binaries with latestengineering binary fixes (EBF).



■ TITAN cases: 320-174-755


■ Description:Duplications appeared tohangbecauseof thedelays that a large catalog cleanupprocess casued.



■ TITAN cases: 230-647-273 411-146-558 600-565-972


■ Description:PemCORBACall::invokeCall would hang and resulted in no more calls to theNBProxy queue to be processed. In addition, nbpem would no longer schedulejobs and consumed the CPU.

■ Work around:Towork around this issue, remove the include days fromall calendar schedulesthat 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, synchronousflushing of image data was not forced during an image close. That left a smallwindow of time where the data was not completely flushed (or sent) to thedisk. 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 tothe 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 returnedan RST when bprd wrote the exit status. The dbclient process then hangsendlessly on the socket read as an alarm appears not to be set forCLIENT_READ_TIMEOUT.



■ TITAN cases: 281-813-207


■ Description:A change was made to address an issue that caused SLP duplication to hangin a queued state.





■ Description:A changewas added to correct and issue that caused theNBJM to grow tomorethan 4Gb in size and then core dump.



142


■ Description:Copy-back restores failed from NAS_Snapshot because mount_frag() returnedan 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 clientencryption options enabled were backed up without encryption in NetBackup6.5GA through 6.5.5. That could have resulted in a data security issue if thephysical backup media custody were lost.Restores of LAN-encrypted backups that use SAN Client on non-Windowsclients in NetBackup 6.5GA through 6.5.5 would restore the encrypted datawithout decrypting it. That could cause a severe data loss , and corrupted therunning OS if the restored files were critical OS files.That problemdoes not exist for SANClient on theWindows operating systems.

■ Additional Notes:That fix causes backup and restore jobs that use SAN Client on non-Windowsclients that involve client encryption options in the policy to generate a status16 unimplemented error. That prevents the data security or data losspossibilities.After you install this patch, any previously generated SAN Client backup setsfromclient-side encryptionpolicies areNOTrestorablewithout removing thispatch.Attempts to restore these non-encrypted SAN Client backups from clientencryption option policies using LAN fail without restoring any data.



■ TITAN cases: 281-879-985 320-187-988


■ Description:A change was made to ensure that the SNAP_LOCK_TIMEOUT registry is notignored.




■ Description:Point-in-Time (PIT) restores would fail on Solaris whenEMC_timefinder_Mirror is used and ifmultipleVxVMdisk groups are involvedin the restore.



■ TITAN cases: 281-745-720


■ Description:

A problem existed in Vault and how it determined which tapes to eject basedon thephysical status and location of the tapes. Vaultmakes this determinationbefore 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 theyare considered for ejection.

■ For the tapes that are in the IN_DRIVE state, there is no problem, and theyare not considered for ejection.

■ For the tapes that are in the IN_TRANSIT state therewas aproblembecauseVault considered those tapes for ejection, when they should not have beenconsidered.

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 physicallyejected. The result was a status 224 (Control daemon connect or

protocol error) error.

■ Vault thinks the eject operation occurred and exited with final status288 (partially successful eject) error.


144

■ The Robot Pick List shows all tapes are EJECTED (except for the tapesthat in the IN_DRIVE state). That is not correct. The Robot Pick Listshould show no tapes ejected, and that no tapesmade it in into the CAP(physically).



■ Description:A changewasmade toupgrade JRE1.6 forNetBackup6.5.6 supportedplatforms.All platforms with the exception of Tru64 are now at version 1.6. That wasdone for two reasons: - To address and alleviate customer security concerns.- To get the latest fixes for known security vulnerabilities from the vendor.

NetBackup 6.5.6 JRE versionPlatform

1.6.0 SR 6AIX_JRE

1.6.0.05HPUX_JRE

1.6.0.05HPUX_IA64_JRE

1.6.0_17Linux_JRE

1.6.0_17Linux_IA64_JRE

1.6.0_17Solaris_SPARC_JRE

1.6.0_17Solaris_x86_JRE

1.6.0_17Windows_JRE

1.6.0_17Windows_x64_JRE

1.6.0_17Windows_IA64_JRE

1.4.2-9Tru64



■ Description:A changewasmade to address an issuewith bpbkar32 thatwould cause a crashand produce amessage on exceptions if a FlashBackupwas run and the socketdisconnected.



■ Contained in: NBLU_6.5.6.UNIX NBLU_6.5.6.WIN NB_6.5.6.winnt.IA64NB_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 aNetBackup catalog backup or a Database (Oracle, DB2, SQL, or SAP) SnapshotClient backup.



■ Description:A change wasmade to address an issue that caused the Java GUI to not handlethe Scratch pool attribute for a volume pool properly.



■ TITAN cases: 320-198-552


■ Description:All Windows 2000 and Windows XP clients complete with a Status 1 becauseit is failing to backup event logs .When performing a ALL_LOCAL_DRIVES backup of a Windows 2000 system,the event logs cannot be found. Amessage similar to the following can appearin 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



146


■ TITAN cases: 281-680-968


■ Description:During an attempt to back up CCR clusters, the bpfis on the passive nodewould fault and fail.



■ TITAN cases: 320-232-329


■ Description:That release contains multiple NetBackup 6.5.4 fixes that address previouslyreported issues.



■ TITAN cases: 230-677-886


■ Description:In a Veritas Security Services configuration, if you used the Copy tonewusergroupoption, a newgroup is created but the permissionswere not copied overto the new user group.



■ TITAN cases: 281-645-651


■ Description:Anewoptionhas been added to the nbftconfig. The -listtargets lists detailsof the FT Target ports. By default all target ports across all FT media serversare listed and you can filter the output for a media server.




■ Description:An issue existed for a FlashBackup policy with snapshots enabled andconfiguredwith inline tape copy. If the resource was not allocated for the firstcopy then the job was erroneously marked DONE in the Activity Monitor andno 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.IA64NB_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 formore information about the resolution of thisissue.



■ TITAN cases: 410-826-062


■ Description:A change has been made to ensure that NetBackup no longer creates worldwriteable files. (That change resolves a security issue).


■ Contained in: NBLU_6.5.6.WIN NB_JAV_6.5.6.winnt.IA64NB_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 beenupdated to 1.6.0_17.



■ TITAN cases: 312-189-222



148

■ Description:A change was made to address an issue that caused migvold to exit with asignal 16.



■ TITAN cases: 220-692-308


■ Description:For an Exchange off-host backup in which NetBackup was installed in adifferent folder on the off-host client than on the primary client, the snapshotjob failed with a status 130.



■ TITAN cases: 320-206-408


■ Description:An Exchange CCR cluster backup took a very long time to complete when thepassive node was down. The total amount time was directly proportional tothe number of Exchange storage groups.



■ TITAN cases: 281-743-167


■ Description:A change was made to address a performance issue that caused the userinterface to consume too much of the CPU. That issue would occur whenanything 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 readsome images.



■ TITAN cases: 220-688-523


■ Description:Oracle Recovery Manager (RMAN) backups with Hitachi_ShadowImage on analternate host took more than an hour to perform the bpfis create.



■ TITAN cases: 312-180-772


■ Description:The NetBackup Administration Console for Windows IA64 would crash whenthe user tried to open or save a file with the Open or SaveAs dialog. The issuewas found in the Catalog Recovery Wizard, more specifically, the Licensekeys Save As dialog, and the Host Properties Save As dialog.



■ TITAN cases: 240-904-318


■ Description:If you attempted to add multiple SSO Media servers with a large number ofdrives (more than128) inDeviceConfigurationWizard, the followingmessagewould appear:

The maximum number of enabled drives is 128

A change was made to correct this issue.



150


■ TITAN cases: 240-904-196 291-167-758


■ Description:A change was made to address an issue that caused the Resource Broker tohang 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


■ Description:If a batch file was created to back up a large number of databases that use theNetBackup for Microsoft SQL Server agent and specify $ALL to the databasekeyword, the database backup operation gets "silently" skipped and yet reporta success. (A status code 0 is reported in the Activity Monitor). That sameresult could occur when a large number of databases have been manuallyenumerated within the batch file through the use of multiple databasekeywords.

■ Work around:To avoid this issue, perform the following:Add the BATCHSIZE # directive to the batch file. Use a value that is equal toor less than the number of databases listed in the batch file. Or use the numberthat would be enumerated by use of the database $ALL directive.Refer to the NetBackup 6.5 for Microsoft SQL Administrator's Guide for moreinformation about the BATCHSIZE directive.



■ TITAN cases: 320-196-561


■ Description:The nbdevconfig command would break the file system list when a mountpoint ended with a dot.


When AdvancedDisk was configured, not all file systems appeared in the listof devices. Andnot all filemount points appear in the list. That issue appearedwhen 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


■ Description:A multiple VC/Proxy environment fails if the proxy could not talk to one ofthe VC's because of multiple networks.

■ Additional Notes:The change checks for a new registry entry in Config\BACKUP calledexcludeVMservers. That is a string value that contains a comma-separatedlist of VMware servers to ignore.



■ Description:A change was added to correct the display of repeated server names listed inVMware Restore Marked Files window.



■ Description:The ndmpagent process would crash on Windows x64 platforms because ofcertain 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 setDebugLevel to 4 or lower.



152


■ Description:A changewasmade to correct an issue that caused a possible crashwhendoinggranular 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 ifa non-streamed BMR job was executed.



■ Description:Changes were made to improve NetBackup's SLP query optimization.



■ TITAN cases: 281-805-383


■ Description:NetBackupResource Broker did not consistently grant resources to the storageunit groups when its internal cache became invalid. That could happen whendrives went down unexpectedly.



■ TITAN cases: 281-778-470 320222610 410-738-664


■ Description:TheNetBackup JobManager (NBJM)would core dumpduring the enumerationof snapshot details for an Exchange backup. A memory fragmentation causedthis issue.




■ TITAN cases: 312-189-219


■ Description:A change was made to ensure that immediate manual backup jobs outside ofwindow are retried.



■ TITAN cases: 320-226-967 411-220-369


■ Description:FlashBackup Single File Restores (SFR) from incremental backups could failwith 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 changewasmade to ensure that aDR email is sent after a hot catalog backupwith ITC, where one storage unit is PDDO.



■ TITAN cases: 220-695-490


■ Description:A user could encounter the following BPDBM errormessage if they attemptedto run an image cleanup at the same time as backup jobs were run.


154

"getJobExistsById: BPXMInterface.cpp.602 - CORBA::EXCEPTION on

jm connection. exception = MARSHAL"

■ Work around:That error message does not affect how NetBackup functions.



■ Description:An Exchange GRT backup failed with a status 1 error. The following errormessage 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


■ Description:FlashBackup Window restores would fail with the following message in thebprd 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 insteadof a member variable.



■ TITAN cases: 281-747-162 410-628-196 411-881-580



■ Description:Thebpbkar.exe executablewould crash if youattempted tobackup the inactivenode of a clustered Windows client at the same time as a Shadow CopyComponents or System State backup.



■ TITAN cases: 281-717-137


■ **Description:Optimized duplication using PureDisk STU (PDDO) succeeds for an ExchangeGranular 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 forthis return value resulted in ShmAddress = 0xffffffff, which led to a coredump issue.



■ Description:A change was made to ensure that after you edit a policy, the jobs do not failwith a storage unit not defined.



■ Description:An OpenStorage device returned an EBUSY message during an optimizedduplicationwould produce critical, misleading errormessaging. The expected


156

behavior was to retry the bp_sts_copy_extent call. A change was made toensure 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 notpreserve or obtain the Oracle environment in all cases.



■ TITAN cases: 220-700-176 410-658-066


■ Description:A single-stream backup that includes ShadowCopy Components can exit witha 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 causedbptm.exe to wait a very long time for a TERMINATE from bpbrm during abackup 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 thismedia server fail because it is unable to successfullymount the requested tape.

■ Bptm.exe continues to run even after bpdown is run on the media server.

■ Reboot ormanually terminatingbptm.exe is the onlyway to kill theprocess.

■ But the ...\db\media\drive\ contents remains - manually have to cleanit up to.


158

About NetBackup releasehistory

This appendix includes the following topics:

■ About previous NetBackup releases

■ Master Etrack Index for all previous releases

About previous NetBackup releasesFor additional information about the contents of what was released in a previousversion of NetBackup, refer to one of the following TechNotes on the SymantecSupport Web site:

■ NetBackup 6.5.5 Release Updatehttp://entsupport.symantec.com/docs/334986





AAppendix

Master Etrack Index for all previous releasesThis topic contains a master list of all of the Etracks fixed in each of the previousNetBackup releases. The Etracks are sorted according to the release the Etrackwas fixed in aswell as by the container. You canuse thismaster ET index to quicklylocate which version and container a particular change was made in.

NetBackup 6.5.5 packaged Etracks for UNIX and WindowsThis section contains a master index for all of the Etracks that have been fixedand were packaged in NetBackup 6.5.5. The Etracks are sorted according to thecontainers that they were fixed in.

NB_BMR_6.5.51637616 1737811

NB_JAV_6.5.5.winnt.x861679309 1835808

NB_SNC_6.5.51599687 1728862 1748009

NB_6.5.5.winnt.x86150054015021131502504150318615095411518794153561315372331538081153875215416901541691154445315451381556733158866415892911593090159681315996871599756160091316038221630735163261016327591636151163735816376161638341163847516393351664215166698416734111675851167703816806151705725170617217078621708623171074117110361719418185236117197301723707172382817239871724975172786917288621729167173074117378111739362174191517452941745631174569817458401749700175198317546511763377176426317643141779214178180217831831785238178535417866571789754180170818056971832341183704418404591843770

NB_6.5.5.winnt.x64150054015021131502504150318615095411518794153561315372331538081153875215416901541691154445315451381556733158866415892911593090159681315996871599756160091316038221630735163261016327591636151163735816376161638341163847516393351664215166698416734111675851167703816806151705725170617217078621708623171074117110361719418

About NetBackup release historyMaster Etrack Index for all previous releases

160

185236117197301723707172382817239871724975172786917288621729167173074117378111739362174191517452941745631174569817458401749700175198317546511763377176426317643141779214178180217831831785238178535417866571789754180170818056971832341183704418404591843770

NB_CLT_6.5.51502113150318615187941535613153723315380811538752154169115444531545138155673315886641589291159056015930901596813159975616009131603822163073516326101632759163615116373581639335166421516684771672567167341116770381705725170617217078621708623171074117110361719418171973017237071723872172398717249751727869173074117419151745294174569817497001763377176426317818021782070178318317852381785354178665717897541801708180569718310441832341183704418431351843594 1843770 1852361

NB_JAV_6.5.51679309 1835808

NBLU_6.5.5.UNIX1502113150318615187941535613153723315380811538752154169115444531545138155673315886641589291159056015930901596813159968715997561600913160382216307351632610163275916361511637358163761616393351664215166847716725671673411167703816793091705725170617217078621708623171074117110361719418185236117197301723707172387217239871724975172786917288621730741173781117419151745294174569817480091749700176337717642631764314178180217820701783183178523817853541786657178975418017081805697183104418323411835808183704418431351843594 1843770

NBLU_6.5.5.WIN1500540150211315025041503186150954115187941535613153723315380811538752154169015416911544453154513815567331588664158929115930901596813159968715997561600913160382216307351632610163275916361511637358163761616383411638475163933516642151666984167341116758511677038167930916806151705725170617217078621708623171074117110361719418185236117197301723707172382817239871724975172786917288621729167173074117378111739362174191517452941745631174569817458401749700175198317546511763377176426317643141779214178180217831831785238178535417866571789754180170818056971832341183580818370441840459 1843770

161About NetBackup release historyMaster Etrack Index for all previous releases

NB_JAV_6.5.5.winnt.x641679309 1835808

NB_6.5.5.winnt.IA64150054015021131502504150318615095411518794153561315372331538081153875215416901541691154445315451381556733158866415892911593090159681315996871599756160091316038221630735163261016327591636151163735816376161638341163847516393351664215166698416734111675851167703816806151705725170617217078621708623171074117110361719418185236117197301723707172382817239871724975172786917288621729167173074117378111739362174191517452941745631174569817458401749700175198317546511763377176426317643141779214178180217831831785238178535417866571789754180170818056971832341183704418404591843770

NB_BBS_6.5.51737811

NB_VLT_6.5.51764314

NB_JAV_6.5.5.winnt.IA641679309 1835808

NB_6.5.51502113150318615187941535613153723315380811538752154169115444531545138155673315886641589291159309015968131599756160091316038221630735163261016327591636151163735816393351664215166847716725671673411167703817057251706172170786217086231710741171103617194181719730172370717238721723987172497517278691730741174191517452941745698174970017633771764263178180217820701783183178523817853541786657178975418017081805697183104418323411837044184313518435941843770 1852361

NetBackup 6.5.4 UNIX packaged EtracksThis section contains a master index for all UNIX packages of Etracks that havebeen fixed in this release, sorted according to the containers that they were fixedin.


162

NB_6.5.4

1285455124709412669961274467127118112668281267706124048612752331291152126032312516561254610124824212900841281628126454312774651267880106562212988721286001127842512985511266772129579013217211151349127698312741051286092130220112539101246062131689612346831282457 1315723 1141312 1235177 700722 1316030 1269701 1221450 1301941130290312457671240580126000913654761364370126135911829491368000136117913741371274771138595612834091378098138894912560401257567138450513942941391201124376013977701397803139446413951911180431139509513788711392357112877713953881407095140085112968971386091140201613923681413113127856114133131390861141407711731001390505141079812821501415947141421114143121418051126808414129011411499140000214224761421893127447212670271370671120865413715781424207140037614242911407021128392214217241422599141300114007171473485147348614101781294340141852413977731301030141292414130631431018143327313998571425305143414614260571384805127663414318941416846143511914317581431826141784413961731383748143960711356731430950140621914062131436844143101514414981433052143925214354891323857153855314315271426014144455114276001414674144549313818061442063144705814456481430034141178814136181431088144726514471601432407144640814374251425084144819514422391418373145241611484461446653145146514472601453529144230114510231436594145360514167851379510126259914464681459294139983914653311395101146503314582261450234144917814534221458420143214814051801470340146096414638901468581144820614812501529072144640114812841446147145056414665281464016145228114215341460587143997114679001471621146887714283251469444147161314639371465258146401514766001482673148267614802861587338160279016006541474403144839614088511412268145887214738601474475146572814386451433497143882214502681475313147349914175041452344147849514789151475161146111611260651480041146970614608371468318146470114811591480280146199313001291463877144995514722341451817148140414149221437385148137314761071374989148291414779351486988148500514859461437453140232214813481486168147263314866861486807148758014875101464678148826714442361452950148171414789991470973148597714887341475372148430215002721500484148757715575781488525150104015018551450415150355515035541504217150205914754021503097150513815049871505661142972315072901505203150766315016471501118141753915021041508567150703315004511509112149942615091071508224115534714547591483007150937015089011511217144985314812241455436140699215148431502251150367415089431476060151506415187161517830151661115166581511966151537815122691515674147559515170911468310150197315207901517775151841515216091520660152131915141611519049152399115210721515697142889715237711524262152449515123071514813


150589515253071518751152439115061561526402152760115010391467372159396615298611527862146191315222731514334152776815312491523443158740915301211525375151205215319291529030153190715339861516985153381715349631535794153578015364411529377153566315397361536918153782015417221534880154168215210761541521154298115369991544193153927415459001550511154274615440101545883155784515583181542974158647415573041587307155819315904231595019159844915946791545939

NB_BBS_6.5.4

1280130 1201793 1315488 1147236

NB_BMR_6.5.4

1201738130079612358911251401120575513631191282624130070213005201409123140451014235471368029144201212260651450240142689114522561455096146387514660441469841147082614769621477173137297314771421479559 1485370 1519805 1516293 1525928

NB_CLT_6.5.4

1285455124709412669961274467127118112668281267706124048612752331291152126032312516561254610124824212900841281628126454312774651267880106562212988721286001127842512985511266772123952012957901321721115134912769831274105128609213022011316849142746914560391458931146848515021551503870150207815183311501805130104112539101246062 1316896 1234683 1282457 1315723 1141312 1235177 700722 13160301269701122145013019411302903124576712405801260009136312313654761226486124425412498111255700137073813848961377315138252213830951126594140361414310071432150142149715098751558174159097315950831598047159769716037701603922136437012613591182949136800013611791374137125087512747711385956128340913780981388949125604012575671227674138450513942941391201124376013977701397803139446413951911180431 1395095 1378871 1392357 1128777 965836 1395388 1407095 1400851129689713860911402016139236814131131278561141331313908611414077117310013905051410798128215014159471414211141431214180511268084141290114114991400002142247614218931274472126702713706711208654137157814242071400376142429114070211283922142172414225991413001140071714734851473486141017812943401418524139777313010301412924141306314310181433273139985714253051434146142605713848051276634143189414168461435119143175814318261417844139617313837481439607113567314309501406219140621314368441431015144149814330521439252143548913238571538553143152714260141444551142760014146741445493138180614420631447058144564814300341411788141361814310881447265144716014324071446408143742514250841448195144223914183731452416114844614466531451465144726014535291442301145102314365941453605141678513795101262599144646814592941399839146533113951011465033


164

1458226145023414491781453422145842014321481405180147034014609641463890146858114482061481250152907214464011481284144614714505641466528146401614522811421534146058714399711467900147162114688771428325146944414716131463937146525814640151476600148267314826761480286158733816027901600654147440314483961408851141226814588721473860146563414744751465728143864514334971475916143882214502681475313147349914175041452344147849514789151475161146111611260651480041146798914697061460837146831814647011481159148028014619931482660130012914638771449955147223414518171481404141492214373851481373147610713749891482914147793514869881485005148594614374531402322148134814861681472633148668614868071487580148751014646781488267144423614529501481714147899914709731485977148873414753721484302150027215004841487577155757814050381488525143509215010401501855145041515035551503554150421715020591475402150309715051381504987150566114297231507290150520315076631501647150111814175391502104150856714060631507033150045115091121499426150910715082241155347145475914830071509370150890115112171449853148122414554361406992151484315022511503674150894314760601515064151871615178301516611151665815119661515378151226915156741475595151709114683101501973152079015177751518415152160915206601521319151416115190491523991152107214587981515697142889715237711524262152449515123071514813150589515253071518751152439115061561526402152760115010391467372159396615298611527862146191315222731510981151433415277681531249152344315874091530121152537515120521531929152903015319071533986151698515338171534963153579415357801536441152937715356631539736153691815378201541722153488015416821521076154152115429811536999154419315392741545900155051115427461557316155731815440101545883155784515583181542974158647415573041587307155819315904231595019 1598449 1594679 1545939

NB_DB2_6.5.4

1398665 1374366 1427035 1441557

NB_DMP_6.5.4

1217098124798112755731281911120850812861721361300116714014243081421594 1442316 1469272 1462054 1479387 1505107 1502073

NB_ENC_6.5.4

1413512

NB_INX_6.5.4

1302046

NB_JAV_6.5.4


1269550138501210155901373561123164413983441398173138577013009781402954141287214115641412461142591410352761421469138807414162681439821143653314264741439070139868914476201155201145321514562211451244145429814655321252404146159314719481433549147502614758141452175147910814669961478919148347614833621483465139115514865061478018150019014838971399167150553713991741517224151918615187471524277 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 14276801315412144686814224591461305125989014324711414295144815514842031529844 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 12509281251765113061611983631317951132330012283841252585132364313634491257455113468013237581283920127639813788941366314127864514039551415117 1253140 1251337 1053635 1412947 1424138 1250759 382235 14447271448262144769214467921457644145642414282841466545146683214284081437956146147814287291460851147760314745861231756148110114831341481079146206715136661526648152994214744981532955152915815376631533275 1535789 1542470 1599601

NB_SYB_6.5.4

1321466

NB_VLT_6.5.4

1321303 1399444 294799 1453874 1461863 1449157 1465117 1486202 14607121525087


166

NetBackup 6.5.4 Windows packaged EtracksThis section contains a master index for all Windows packages of Etracks thathave been fixed in this release, sorted according to the containers that they werefixed in.

NB_6.5.4.x86, NB_6.5.4.x64, and NB_6.5.4.IA64

1285455126699612744671271181126682812017931201738126770612752331291152126032312516561275601124492212497261248242129008412816281264543128725912774651267880106562212988721286001127842513007961235891126943913008581298551126677212395201295790132172111513491287091 963688 1287123 1508246 1276983 1272183 1298900 1258356 12721571042455125092812860921253170130220113168491427469145603914589311468485150215515038701502078151833115018051253910124852412460621316896 1268978 1285995 1253909 1282457 1251765 1315723 1235177 7007221198363131603012697011195355121709813233001221450122838413176131302903125140112457671247981124058012057551252585132364312600091275573113768112819111208508136312312826241323935136344913654761250754130132812264861244254124981112557001370738138489613773151382522138309511265941403614143100714321501421497150987515581741590973159508315980471597697160377016039221290087128617213643701261359118294913680001257455136130011346801323758136117913741371276398126068512316451063955127477113213031221671137889411671401378219137428013978161366314113868413859561283409137809812188971256040125756713007021372709122767413845051394294139120113977701397803139446413951911180431139509513994441378871139235714030451128777 1402256 965836 1395388 1374366 1406164 1407095 1141109 11177381400851 1409123 294799 1296897 1386091 1402016 1392368 1413113 13743661418493127856114133131414077117310012670301415117141079814045101282150141594714142111414312141805112680841413284141330614129011414771141149914000021412947142247614218931274472142354712670271370671120865414156671371578142420714003761427035142569814242911424308142159414070211283922142172414225991413001140071714141321473485147348614101781294340141852413977731301030141292414130631431018140071314332731399857142530514354061434146143188613830411426057138480512766341416828143651714318941437623125075914168461394077137466314287681431758143182614178441424613139617314295691427179143909613837481439607143327411356731430950140621914062131436844 1431015 1442316 1441498 382235 1434748 1366169 1430370 1433052143925214354891121521144428013238571538553144344514318881443521143789914315271426014143099914452551266674144455114276001445493138180614420631426468144762314470581447946122394313685901445648136859014300341411788129668614136181431088144868614472651447160143240714464081437425122606514331671424008142508414071001428501


1450941144223914183731252553145241614476921148446144665314514651447260145352914494801446254144230114510231426891143659414536051451053141493914467921452718145427714527161452707145270214536291441557141678513795101457644140242214564241262599142746014592001447346140619214464681452256146128914132241459685145929413998391455096146387514653311395101146503314126071458226145562214618631450234146081814491781453422144915714584201458816145888014321481405180146927214703401460964146389014685811462054146604414482061481250152907214464011481284144614714505641466528146401614522811293617146800114698411470826142153414605871439971146790014716211468877144284414283251469444147161314733921463937146525814725321470771146401514766001482673148267614802861587338160279016006541474403144839614088511412268145887214738601474475146147814714381465728146874714334971475096145245814287291438822145026814512091076978147531314769621473499145031714343971417504147192814745861443130145234414784951477173114243913729731478915147938714751611461116147714214764951479559148004114697061460837146831814804111464701142107414811591480280146199314532401479474145828214397131480432144995514722341481280148313414804521481305147915613216531451817148140413206171414922143738514813731484335126843614761071374989145768114779351486988126658114692951485764148500514859461437453148134814861681247756144258514536001485370148257814847211472633148666012457711486807148305714875801487510148716614704611464678148073914882671487657148860314442361452950148171414210761478999147097314812191480521148597714887341484302148881515002721500484148757715575781416786148852514350921501868148620215020701500933148324614861071501855145041515035351501912150355515035541504217150293314517401502934150205914754021503097150513815049871500382150566114297231501282144816314524651475676150510715016471501118150433514175391507389139492015005051502104150856715051841507033150508515004511460712150014014994261509107150822411553471454759146206713990411483007147598515074351478387145779714733541509370150890115112171449853150888414812241455436150362515118141505823150207315099841509336151484315133081509793150225114684951508125151369915143771503674145779715167601474524151722715024721508943151382914406071476060151506415016221518716151783015166111516658 1511966 1515378 1512269 1515674 1507115 1475595 1517091 989955151931415145021519805151760914683101501973151754915202771519822150640815162931520790151773315177751518415152116915216091520660152293614734221521319151416115185801519049152399115210721521249151330915156971523771152426215250871524495152454215123071521067151481312467231505895139154315253071518751152439115136661526402152664815254081527601152592814673721593966152238415298611526650


168

152786214619131474498152477515300401514334152454215277681218121152995815304191531249152344315874091530121152537515120521528010153192915290301531183153295415329551529158153766315319071533986153297215169851533817153496315340051531793153379515264151485141153578015266111536441138125215293771535017152678314766191535482153788315380681504413153566315397361536918153782014861891520098153488015416821521076154152115424701539774154298115396621545112153699915441931539274154590015505111542746153770915573161557318153987815440101538891154588315578451544119153212315576561558318154297415864741557304154535215873071558193158606315908811590423159501915984491594679150520715969561599538154593915996011630537

NB_JAV_6.5.4.x86

1269550138501210155901373561123164413983441398173138577013009781402954141287214115641412461142591414122761035276142146913880741416268143982114365331426474143907013986891447620115520114532151456221145124414542981465532125240414615931471948143354914750261475814145217514791081466996147891914834761483362139115514865061478018150019014838971399167150553713991741517224151918615187471524277 1531521 1544995

NB_JAV_6.5.4.IA64

1269550138501210155901373561123164413983441398173138577013009781402954141287214115641412461142591414122761035276142146913880741416268143982114365331426474143907013986891447620115520114532151456221145124414542981465532125240414615931471948143354914750261475814145217514791081466996147891914834761483362139115514865061478018150019014838971399167150553713991741517224151918615187471524277 1531521 1544995

NB_NOM_6.5.4.x86

1167039 1255955 1240142 1245644 1275868 927989 1203966 855237 14276801315412144686814224591461305125989014324711414295144815514842031481142 1529844 1528847


NB_6.5.3

127555913029291302749131701313170081317006131720213170471276489131809112899211322984136440713644221322803136466113730191383374


1382658138358613835841184889127661313826321383839138343813834401383434138344213837331383750138354013840291375483138373613835271383523138487913850831385111138629413837571384675138351113850611382599137680513837821383502138349713834991384270138605713860601383811138380813826831384822138606413860621386073138372713837661386069138496013860751386077138401913860651386070138704613837431384952138703913836431384946138494313881491384948138374413861991384909138908813743301388180138375613881921382684138340413903351383742138376113911681382623139110913837631394025138363013921321388236138402013950571384919138379213837721393919138403213840231384966139539313835061396153139111013979841399794139381013937981397604139862713880001387827139379313962481402394139611213952331402922140392014052901402967132053013986981396083139266814091311409154141125114117761410874141233114088071412417141333814113021413269141078614135721385085141421214125571415612141364914014821413567141568314145411416768142102514250931424266142345314259001425285142809614235831426958142706414296291430825142879414312201428632143278614312171431957143215214327331431905143649214367381439637

NB_BBS_6.5.3

1386047 1383479

NB_BMR_6.5.3

1289330 1385881

NB_CLT_6.5.3

127555913029291302749131701313170081317006131720213170471276489131809112899211322984136440713644221322803136466113730191383374138265813835861383584118488912766131382632138383913834381383440138343413834421383733138375013835401384029137548313837361382523138352713835231384879138508313851111386294138375713846751383511138506113825991384892137680513837821383502138349713834991384270138605713860601383811138380813826831384822138606413860621386073138372713837661386069138496013860751386077138401913860651386070138704613837431384952138703913836431384946138494313881491384948138374413861991384909138908813743301388180138375613881921382684138340413879841390335138374213837611391168138262313911091383763139402513836301392132138823613840201395057138491913837921383772139391913840321384023138496613953931383506139615313911101397984139979413938101393798139760413986271388000138782713937931396248140239413961121395233140292214039201405290140296713205301398698139608313926681409131140915414112511411776141087414123311408807141241714133381411302141326914107861413572138508514142121412557


170

1415612141364914014821413567141568314145411416768142102514250931424266142345314259001425285142809614235831426958142706414296291430825142879414312201428632143278614312171431957143215214327331431905 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

1383447138438013900671391157139116113950921399345140992314099251423226

NB_SAP_6.5.3

1227447 1386537 1227458 1411527

NB_SMU_6.5.3

1387861 1387867

NB_SNC_6.5.3

1383582138342913825961383498138402513940391395089138351214013731398467 1410597

NB_VLT_6.5.3

1383258138576413867561385614138676013867631386750139628614029071404850



NB_6.5.3.x86, NB_6.5.3.x64, and NB_6.5.3.IA64

125074312755591289330130292912821071302749131701313170081317006131720213170471276489131809113184371289921131950013229841361367136440713644221322803136466113730191383374138265813835861383582138358411848891276613138263213838391383438138342913834401383434138325813834421383733138403113837501383540138252813848971384026137548313837361382523138352713835231384879138508313851111386294138345413834251383426138467713835561383757138467513850611383452138259913825961384892137680513825951383782138349813834661383497138605713857641386060138381113838081382683138675613856141384822138689113860641386062138607313837271384025138262213837661386069138496013826181386075138607713834721383479138588113840191386065138490413860701387046138374313849521387039138364313881321384946138494313881491384948138374413887661384909138908813880501388180122744713837561388092138819213880531388054138805713880581388060138806313865371382684138340413879841383532138374213837611391168138676013933211386763139110913837631394039139402513836301392132138675013882361384020139505713849191383792138377213939191384032138402313849661395393138350613962861227458139615313911101397984139600513917951393810139379813976041395089139862713990091388000138782713835121397582139379313962481402394139611214013731402907140304813952331402499140306914029221403920140529014029671398832140485013205301398698139608314081291392668140913114091541410597141065914112511410516141152714117761410874141233114124171413338141130214132691410786141357213850851414212141255714022331415612141477614136491401482141356714156831416768141514214166201415243142102514250931424266142345314120621382626142590014252851428096142358314269581427064142989614297211429629143082514287941431220142863214312171431957143215214327331431905143649214367381439637

NB_JAV_6.5.3.x86

1316222 1316255 1316257 1383469 1386728 1388080 1400256

NB_NOM_6.5.3.x86

138344713843801390067139116113950921399345140992314099251423226

NB_JAV_6.5.3.IA64

1316222 1316255 1316257 1383469 1386728 1388080 1400256


172


NB_6.5.2A

1072956112973811466361164956116800611671801163707121467911665351169771116630110626871161381106551111722721128543116679310667251174568116415111729721153448107312910581331241088117380811913961225254122435212243261229771123296812332201232369116231611307701149230117848211782341178268117379811752901180414114194110874121172948117539111401381158501107836211776861156305111352111738031089294118212511327451124825117079311535281175038118365010658351065761115957011974101167158113474911837101182952114512110727861169863118202111763461151267118200811036401167175115979610605751214253121681512166921217125121786812157681216893121705112131651219082121245412190201230246123024311851761146898105644311526401186863118608711884921188093118953711439161189076118909410816591099902118305411737911183182119304310816591143425118321111554361200208115807711975261129982115626511511561201126120432112119541214165122007812206951219827122169812216861222264118990111396821190785115438511578741190511118786411906561157433110161811895111176221118093911865501124933116873511928561176263119491610909331193420116444111671781051426119901811348201193176115972311596071117080112403111322951167366119170611959191107364118227411992961163525119995911951381201579120094411877781193100122557312029951194501118102710670201152607115553812032241108377118794212341581203477120090312009071168083120507912023361202335120606212008541187198120694512033491158733120323511904711207061120529612070471204443119691011973101077508120932511930641164771103325311697371209400121406212126191217901121790712169591219557121963512195261219430121943712205621222057122412712258931225770122583312214661229628122900812303961220532123096112297521228886123241810893061210332113319511939511117658120765111524971206423119373811241551177472121367011465421047988121410110458861205703119226412141501215593121548712105461201414119414611694751193751121630712175531219038120282312198981219039120238312143041220901110237012037441204493121222812083441208227122006012222121221166122006612100101220679116654911361481172024118472612267661222434122023312158311214310122129412275711229090122840212319291230782123556512307081236958123125512339791194635124200612428961237329124192212397001238896123563812369541247224120939112199621215377122385812196871147842 1224240 619166 1221669 1219679 1182185 1204359 1210921 1178113


1225918122684912155801226421121234112257551229830122823712270681229429122893712297731231401117459012291491222888117619912190011221162118554712312941225909123458612279431187087123279611932741177242123214312412351058986102350312347491223697104037911633861136975115712211579171157948114567810775681026946102127412001881211737123201812354561235005107876510572961211652120332412320831216897122531012354481170652117778912094281216741123641812214401230757116229611464751236185123707812290331032515123429512360421161380114129612001651237562122528412386311166645123461812380971235414119652612395711242510123859412426451223956124107112303341232394124307712311971241424123236211764511187803118792012447641244834124461312380661246003122147612476711249057124200312491291233754125177912386621252344125327412615081253326124470312522761255224125275412561351257773125905712588891259934126042312605021140864126150612489191259995124359312621001262650126195312609601264708126591412631851266636126683212674441268822126989712703801137172 1236242 1300823

NB_BBS_6.5.2

1173557 1181272 1149720 1198427 1194895 1222166

NB_BMR_6.5.2

1154522115951911517691155166116634611554381158002116048810362441172180115555011821441187111116965212126291213218121220112197491222715 1168789 1230522 1175887 1234202

NB_CLT_6.5.2

107295611297381146636116495611680061167180116370712146791166535116977111663011062687116138110655111168991117227211285431166793106672511745681164151117297211534481073129117470410581331241088117380811913961225254122435212243261229771123296812332201232369116231611307701103533114923011784821178234117826811737981175290118041411419411087412117294811753911140138115850110783621177686115630511135211173803108929411821251132745112482511707931153528117503811836501065835106576111595701197410116715811347491183710118295211451211072786116986311820211176346115126711820081103531110364011671751159796106057512142531216815121669212171251217868121576812168931217051121316512190821212454121902012302461230243118517611468981056443115264011868631181840118608711884921188093118953711439161189076118909410816591099902118305411737911183182119304310816591143425118321111554361200208115807711975261129982115626511511561201126120432112119541214165122007812206951219827122169812216861222264118990111396821190785115438511578741190511118786411906561157433110161811895111176221118453511256161180939


174

1186550112493311687351192856117626311949161090933119342011644411167178105142611990181134820119317611597231159607111708011240311132295116736611917061195919110736411822741199296116352511999591195138120157912009441187778119310012255731202995119450111810271067020115260711555381203224110837711879421234158120347712009031200907116808312050791202336120233512060621200854118719812069451203349115873312032351190471120706112052961207047120444311969101197310107750812093251193064116477110332531169737104049611064361209400121406212126191217901121790712169591219557121963512195261219430121943712205621222057122412712258931225770122583312214661229628122900812303961220532123096112297521228886123241810893061210332113319511939511117658120765111524971206423119373811241551177472121367011465421047988121410110458861205703119226412141501215593121548712105461201414119414611694751193751121630712175531219038120282312198981214667121903912023831214304122090111023701203744120449312122281208344120822712200601222212122116612200661210010122067911665491136148117202411847261226766122243412202331215831121431012212941227571122909012284021231929123078212355651230708123695812312551233979119463512420061242896123732912419221239700123889612356381236954124722412093911219962121537712238581219687 1147842 1224240 619166 1221669 1219679 1182185 1204359 12109211178113122591812268491215580122642112123411225755112074412298301228237122706812294291228937120256412042021229773123140111745901229149122288811761991219001122116211855471231294122590912345861227943118708712327961193274117724212321431241235105898610235031234749122369710403791163386113697511571221157917115794811456781077568102694610212741200188121173712320181235456123500510787651057296121165212033241232083121689712253101235448117065211777891209428121674112364181221440123075711622961146475123618512370781229033103251512342951236042116138011412961200165123756212252841238631116664512346181238097123541412394701196526123957112425101238594124264512239561241071123033412323941243077123119712414241232362117645111878031187920124476412448341244613123806612460031221476124767112490571242003124912912337541251779123866212523441253274126150812533261244703125227612552241252754125613512577731259057125888912599341260423126050211408641243842112685112094891212487122170812505781261506124891912599951243593126210012626501261953126096012647081265914126318512666361266832126744412688221269897 1270380 1137172 1236242 1300823

NB_DB2_6.5.2

1155324

NB_DMP_6.5.2


1173820117780711812771194321104042611355071199176112128412075881210256 1235516 1237147 1254599

NB_ENC_6.5.2

1238097

NB_INX_6.5.2

1098013

NB_JAV_6.5.2

116629911686121127780117371811248061180766114581511668911076281104574510668281189501111505910843971132128117711511899401189972118099411958771195901118388211959001199217117865711964491198943120155311996361196047111175412025961212368119604612199581209200121479812142371221478122337611539701206951111868612235281225696122581112289521181044123261211901141236368115528111799431210565115618511861411135472124349912289861249027123595212518381254388

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 11353551151560 1166243 1169437 1054146 1012739 856167 1076567 1056238 11653771142255118265211416301057217107745811894741195661115046511959391215410 1200480 1203068 1216709 1227902 1228873 1228917 1226611 4297381233705123374712255891232303123154312382941223648123951910532871240882 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 1044960115598911831721179761115775511878731204223125633511525941210310121417512181901030014120756711564811213477116368212181191201829113906911771661213181122317912108881225245122071811923041118213


176

1226750114608111730281225238122267812291511217389123151912322981232066115258612358491166821123642011861431186138123843012101961214026123464312386761239448124063412418271240218124725112472351194934 1248984 1242524 1252321 1254469 1259531 1264207 1275543

NB_SYB_6.5.2

1098013 1115047

NB_VLT_6.5.2

1051251116932811686951160349116933411662801238368125212412550131255686 1265091


NB_6.5.2A.x86, NB_6.5.2A.x64, and NB_6.5.2A.IA64

107295611297381145586114559411466361154522116718011637071214679114585210980131133233116653511150471159519115176911551661166346115543811580021036244115985411697711142841117127211761711182932116630110626871161381109801410998931128543116679311721801066725117456811709201172972117480211534481073129115532410581331241088117380811913961225254122435212243261229771123296812332201232369116861611668321095138117382011778071155550116231611307701149230117848211782341178268116647411331881180046117379811752901180414114194110874121172948117539111401381167566115850110783621177686115630511135211089294118212511327451124825117079311611671179466115352811821441170142117503811837761183650106583510657611167158113474911837101182952114512110727861044960116986311820211176346115126711559891181277118567611036401159796106057512142531216815121669212171251217868121576812168931217051121316512190821212454121902012302461230243118711111468981056443115264011868631181840105248711860871188492118809311895371143916118907611890941081659109990211830541173791118318211930431081659114342511832111155436120020811580771197526112998211562651151156120112612043211211954121416512200781220695121982712216981221686122226411899011175422119078511543851190511118786411906561157433110161811895111187936117541111762211184535112561611809391138554118655011249331178659118093711827811168735117524211321291189969109423711762631157755119491610909331193420116444111671781051426119901811348201193176115972311596071117080112403111322951185170116736611917061136909119591911073641182274119929611800781195890118993710512511195887


1187873119041910795701199959112942511981311195138119801512006071040426113550710402061201579118422611958831200944118777811931001225573116932811991761194501118102711786541194709126109111117521201601113670310247071170011113097110670201152607115553812032241108377115635211525941187942123415812034771200903120090711680831205079120233611115731200280116716411510021218472117533811970501211131122128812023351188188119489512060621200854118719812069451203349115873312032351190471120709211971161207061120529611372421133191120704712044431077508120932511930641164771103325311697371176684120904010404961106436120940012140621212619121790112179071216959121955712196351219526121943012194371220562122205712241271225893122577012258331221466122962812290081230396122053212309611229752122888612324181088494121031612350361242051125257510893061210332113319512025771225402119395111176581207651115249710639131192391120642311686951160349117285011937381124155121031012133881004177117747211465421047988121410110458861064998121262912132181205703119226412136801215593116933412086401210546120141411840201191845119184611941461166280116947511975111193751121858212190381202823121989812146671219749120592512023831214304122090111023701203744121820311411521204493121222812083441218480122151912075671220060122221211564811213477122116612093491215046121820912200661210010122067911665491136148122284411720241184726122676612181191222434122023312158311214310122129412275711229090122840212319291230782123556512307081236958123125512339791194635124200612428961237329124192212397001238896123563812369541247224120939111748831219962121537712238581219687114784212227151214420113906912242401177166 1213181 1223179 619166 1221669 1219679 1169708 1182185 1225245116368412207181192304122329112249771225173120435911182131119147121092112267501178113122664111604721226873115943612013721225918122684911730281215580122642112123411216729120526011687891225755113718212263371208589122915112298301228237122669412292491226399122706811382991229429121848212173891230522122977312315191231931117459012291491222888123205911761991121284123226212190011221162118554712312941225909123458612075881227943123206611336971210256123146412084971223132120266412327961144788117429611932741152586121302511772421232143124123512245431058986122312212289531023503123535412347491175887123420212236971040379116338611369751157122115791711579481145678107756810269461021274120018812117371232018123545612355161221244123500510787651057296121165212033241232083123559312350281212982121689712358831225310123549712354481170652123584911777891209428121674112364181169611117993312364201218489121848810269571226882122144012363861230757116229611464751236185122466512370781233474122903310325151186143123429512360421227842


178

1232787110798911861381161380105337111412961200165116519311861431187875122899512383681237562122528412386311237076123843012140261166645123461812371471229244122897412394481235414119652612097081227451124063412105951239571124182712425101240218123859412426451223956124107112303341232394124307712311971241424123236211664571176451118780311879201244764124483412446131238066124600311949341247241122147612455281247671124760912338231248519124200312486351249374125077312491291233754125177912386621252124125234412532741261508125332612480771244703125227612552241255013125275412544371255686125197212545991216714125613512577731250942125905712588891258450125993412604231260502114086412438421126851120948912124871221708125057812575431261506124891912610951259995125092612621001262650126195312609601264207126470812619161265914126318512666361265091126683212674441268822126989712703801270499109801312755431236242 1300823

NB_JAV_6.5.2.x86

1166299116861211277801173718112480611807661145815116689110762811045745106682811895011115059108439711321281177115118994011899721180994119587711959011183882119590011992171178657119644911989431201553119963611960471111754120259612123681196046121240212199581209200121479812142371221478122337611539701206951111868612235281225696122581112289521181044123261211901141236368115528111799431210565115618511861411135472124349912289861249027123595212518381254388

NB_JAV_6.5.2.IA64

1166299116861211277801173718112480611807661145815116689110762811045745106682811895011115059108439711321281177115118994011899721180994119587711959011183882119590011992171178657119644911989431201553119963611960471111754120259612123681196046121240212199581209200121479812142371221478122337611539701206951111868612235281225696122581112289521181044123261211901141236368115528111799431210565115618511861411135472124349912289861249027123595212518381254388

NB_NOM_6.5.2.x86

793178 1165266 1098900 1068620 1074452 1187013 1170294 1135355 11515601166243 1169437 1054146 1012739 856167 1076567 1056238 1165377 11422551182652114163010572171077458118947411956611150465119593912154101200480 1222109 1203068 1216709 1227902 1228873 1228917 1226611 4297381233705123374712255891232303123154312382941223648123951910532871240882 1244352 1241644 1247717 1250623 1256155



NB_6.5.1

108140410822811081354108169810772671089270109523110886071084993106089710886061100978111830210797231090571108494710886081111471866629 1039048 1041354 1046330 1050492 1076912 1096261 1003906 10886071094608110061710598621098378104727610610311100839107022010050551100685110069710562591104423108048411008811077695109628411028861072317111060510776931102521109455811026391093595110378611036001105269108860910537121106710105015511115471112392109902010961951109567109911511010441102615108506011069181094270109881510823991052425107608511097051098718109111110657731102710108227711097571098045 1082109 1016904 997644 1081452 1086598 1106385 1095098 10739051122374112213911107361112256112142711176371106502112501711191651119910112811011236181125795113049011260331090463108757111299171132942 1130566 1133603 1107693 1128957 861231 1062790 1059880 11289141136472113425311485281130915113122311377351138740107975311348171137031114120111381261100611112478011280311137782113393111388541131287113976511372701140241113998211363041141863110960811411911141195114431911418441139701114520211396211117736114674511308401146673114576811458711145731114043911473911146512114922211491641150310114079811508341143453115270711545161153517113389811553661155556115536111511721152716115343911593041145768114146911611831160463115860911598211163509116350911490561163626116283711628901163390 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 10942351109595 1115945 1119045 1125002 1131127 1143101 1148419 1161249

NB_CLT_6.5.1

1081404108228110813541081698107726710885721090440108927010952311088607108499310608971088606110097811183021079723109057110849471088608 1111471 866629 1039048 1041354 1046330 1050492 1076912 1096261100390610886071094608110061710598621098378104727610610311100839107022010050551100685110069710562591104423108048411008811077695109628411028861072317111060510776931102521109455811026391093595


180

1103786110360011052691088609105371211067101050155111154711123921098348109902010961951109567109911511010441102615108506011069181094270109881510823991052425107608511097051098718109111110657731045014 1102710 1082277 1109757 1098045 1082109 1029153 1016904 9976441081452108659811063851095098107390511223741122139111073611122561121427111763711065021125017111916511199101128110112361811257951130490112603310904631087571112991711329421130566113360311076931128957 861231 1062790 1059880 1128914 1136472 1134253 1148528 1130915113122311377351138740107975311348171137031114120111381261100611112478011280311137782113393111388541131287113976511372701140241113998211363041141863110960811411911141195114431911418441139701114520211396211117736114674511308401146673114576811458711145731114043911473911132124113211711465121149222114916411503101140798115083411434531152707115451611535171133898115536611553611151172115271611534391159304114576811414691161183116046311586091159821116350911635091149056116362611628371162890116339011673591169734

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

1105102106553610552921105104111335911141021059702112061211370091137032 1140441 1147300 1158537 1160278

NB_LOT_6.5.1

1095196

NB_NOM_6.5.1

1100710109878110958531083394109878810988471073938113611911448261142365 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 1064773936750 1122064 1116285 1122849 1121101 1132427 1133892 1136035 11338081127683112774311379751137994113797211427941139792115015311459511141888 1149082 1151817 1139712

NB_SYB_6.5.1

1082844

NB_VLT_6.5.1

1079108 1104856 1080001 1078416 1139463


NB_6.5.1.x86, NB_6.5.1.x64, and NB_6.5.1.IA64

1080505 1065640 960689 1081404 1082281 1081354 770558 1081698 10772671035399 1051387 1072077 798210 1088471 1089270 1094533 1095231 5964141052364108860710849931060897108860611009781118302107972310905711084947 1096262 1088608 1111471 996779 866629 1100827 1039048 10413541046330105049210769121096261100390610886071094608110061711025741059862109837810942361047276106103110904511079108107022011048561005055110068511006971056259110442310804841103810106802810795311118300107769510920751096284110288610723171110605107769311001791102521109455810394341093595110378611036001105269108860910537121107363111155211115521072056110671010797701098022105015511115471112392109902010951961096195110956710991151101044110261511160601085060109059610828441106918109427010988151088610108239910942351080001105242510760851065442110970510987181078416109111111095951065773109065610647731082277109804511159451082109104796311190451109693 1016904 997644 1081452 1095687 1086598 1106385 1095098 1122374112213911162851110736111225611228491121427111763711065021100849110337311008551100858112148611079861129433112501711227251119165112123410707861128110112579511250021130490112603310904631120589108757111299171132942113242711298061132824113056611346911133181112949511117561133292113360311076931135522112895711316281135746110799110598801128914113643011338921136472113425311485281133802


182

1107991113445210983961133019113785710784161137735113874010797531134817113703111412011127683113812611277431138508110061111394631124780112803111339311137975113467311379941130488113211711332631138854113128711397651137270114021711418191088611112767611402411136304114186311096081142794114119111411951139394111734911443191141844 1140803 1139701 1145202 1143244 1139621 1133928 865299 11467451139792113084011370291146673114576811458711145731114043911473911148419113212411321171146512114985911501531149222114178911503101150728114595111418881134832114602311407981150834115181711434531152707115451611535171133898115536611547371155556115536111553311139712115271611534391144481115452311566441141896115793411593041158479115976511586981145768114146911433021158550115767911475441157980108284410828441082844116046311582081162267115860911598211162160116350911614411163509114905611636261162837116289011633901144017 1165653 1167359 1169734 1169707

NB_JAV_6.5.1.x86

1105102106553610552921105104111335911141021059702112061211370091137032 1140441 1147300 1158537 1160278

NB_NOM_6.5.1.x86

1100710109878110958531083394109878810988471073938113611911448261142365 1150537 1156043 1157674

NB_JAV_6.5.1.IA64

1105102106553610552921105104111335911141021059702112061211370091137032 1140441 1147300 1158537 1160278



184

341279

Documents

Transcript of 341279