NB 701 Release Notes

Symantec NetBackup™ 7.0.1Release Notes

NetBackup 7.0.1

NetBackup 7.0.1 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: 7.0.1

Legal NoticeCopyright © 2010 Symantec Corporation. All rights reserved.

Symantec and the Symantec Logo are trademarks or registered trademarks of SymantecCorporation or its affiliates in theU.S. and other countries. Other namesmaybe trademarksof their respective owners.

This Symantec product may contain third party software for which Symantec is requiredto provide attribution to the third party (“Third Party Programs”). Some of the Third PartyPrograms are available under open source or free software licenses. The LicenseAgreementaccompanying the Software does not alter any rights or obligations you may have underthose open source or free software licenses. Please see theThird Party LegalNoticeAppendixto this Documentation or TPIP ReadMe File accompanying this Symantec product for moreinformation on the Third Party Programs.

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

mailto:[email protected]



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

Chapter 1 New Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

About NetBackup 7.0.1 New Features ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11About remote NDMP multiplexing .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12About NetBackup audit trail .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12About NetBackup client option .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13Volume GUID for Windows cluster ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13About NetBackup BMR enhancements ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Creating an SRT for Windows .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14About the supported boot media on Windows platform .... . . . . . . . . . . . . . 15About the Legacy Restore function .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

About NetBackup for SQL server agent enhancements ... . . . . . . . . . . . . . . . . . . . . . 17About Symantec OpsCenter enhancements ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18About Enterprise Vault 9.0 support ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18About NBSU support for NetBackup 7.0.1 ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19About NBCC and NBCCR enhancements ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19About NetBackup Snapshot Client ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20About VMware vSphere 4.1 ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20About NetBackup documentation updates ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

Chapter 2 Supported Platforms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

About NetBackup 7.0.1 supported platforms .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23About NetBackup 7.0.1 platform proliferation support ... . . . . . . . . . . . . . . . . . . . . . 23NetBackup binary sizes ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

Chapter 3 Product Dependencies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

Operating system patches and updates ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

Chapter 4 Operational Notes and Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

About NetBackup 7.0.1 known issues ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37About documentation issues ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38About General NetBackup issues ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40About NetBackup installation and upgrade issues ... . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

Contents

About Bare Metal Restore (BMR) issues ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43About port usage during a restore operation .... . . . . . . . . . . . . . . . . . . . . . . . . . . . 46About the supported boot media on a Windows platform .... . . . . . . . . . . . 47About the Legacy Restore function in BMR .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

About NetBackup database agents ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48About NetBackup DB2 database agent ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49About NetBackup for SharePoint Server issues ... . . . . . . . . . . . . . . . . . . . . . . . . . 49About NetBackup for Exchange server database agent ... . . . . . . . . . . . . . . . 52

About NetBackup Deduplication .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52About NetBackup Snapshot Client issues ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

Creating space-optimized snapshots ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54About NetBackup Hyper-V issues ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55About NetBackup NDMP issues ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55About NetBackup OpsCenter issues ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

About uninstalling Symantec OpsCenter 7.0 before OpsCenter7.0.1 on UNIX .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

About NetBackup Vault issues ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60About NetBackup VMware issues ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60

Chapter 5 End of Life Notifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

About End-of-life notifications for 7.0.1 ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

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

About the NetBackup7.0.1 master Etrack index list ... . . . . . . . . . . . . . . . . . . . . . . . . . . 69NB_JAV_7.0.1 ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69NB_CLT_7.0.1 ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69NB_7.0.1.winnt.IA64 .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70NBLU_7.0.1.WIN .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71NB_OPS_CTR_7.0.1.winnt.x64 .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72NB_7.0.1 ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73NBLU_7.0.1.UNIX .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73NB_OPS_CTR_7.0.1.winnt.IA64 .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74NB_JAV_7.0.1.winnt.IA64 .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75NB_DRO_7.0.1 ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75NB_JAV_7.0.1.winnt.x64 .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75NB_7.0.1.winnt.x86 .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75NB_7.0.1.winnt.x64 .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76NB_OPS_CTR_7.0.1 ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77NB_OPS_CTR_7.0.1.winnt.x86 .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77NB_JAV_7.0.1.winnt.x86 .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78

Contents8

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

About release content conventions .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79About the current release content ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80

9Contents

Contents10

New Features

This chapter includes the following topics:

■ About NetBackup 7.0.1 New Features

■ About remote NDMP multiplexing

■ About NetBackup audit trail

■ About NetBackup client option

■ Volume GUID for Windows cluster

■ About NetBackup BMR enhancements

■ About NetBackup for SQL server agent enhancements

■ About Symantec OpsCenter enhancements

■ About Enterprise Vault 9.0 support

■ About NBSU support for NetBackup 7.0.1

■ About NBCC and NBCCR enhancements

■ About NetBackup Snapshot Client

■ About VMware vSphere 4.1

■ About NetBackup documentation updates

About NetBackup 7.0.1 New FeaturesThe following subsections introduce the primary features of NetBackup 7.0.1.

1Chapter

Note: If you encounter an error during Beta testing, Symantec wants you to logand report the error to Symantec's technical support . Symantec appreciates yourhelp during the Beta program so that we might work towards addressing thoseissues before the final release.

About remote NDMP multiplexingRemote NDMP multiplexing enables concurrent writing of multiple backupstreams, through a NetBackup media server, to a single tape drive. The mainreason for multiplexing is to improve overall NetBackup performance by betterusing tape drives.

State of the art tape drives can typically stream data much faster than NDMPhosts can create provide backup data. That is especially true with small file sizes.

Multiplexing addresses the following:

■ It allows for a greater number of concurrent backup operations given a limitednumber of target tape drives. Because the tape drives can accept data fasterthan an NDMP host can provide data, several NDMP hosts (or NetBackupclients) can concurrently send data to the same tape drive. That reduces theoverall backup time.

■ Many tape drives require a high minimum data rate to maintain streaming.When data is not streamed fast enough, the drive must reposition and thatreduces the efficiency of the tape device. It also lengthens the backup timeand subjects the tape drive to increased wear.

About NetBackup audit trailNetBackupauditingprovides companieswith anaudit trail of user-initiated actionsin a NetBackup environment. Essentially, auditing gathers the information tohelp answer who changed what and when they changed it.

Compliance laws and various regulatory agencies require that many companieskeep track of changes made within their environment that relate to protectingdata. Because backups are performed to protect data, that means configurationchanges within backup applications must be tracked.

Customers canuseNetBackupauditing tomore efficiently resolve problemswithintheir environment.With auditing configured, they can track user-initiated actionsso that unexpected behavior can be traced back to its origin. The following listsummarizes the user-initiated actions and auditable actions that are available tothe customer.

New FeaturesAbout remote NDMP multiplexing

12

■ Policy create, update and delete

■ Restore job initiation

■ Audit configuration changes

■ Audit service start and stop

In 7.0.1, auditing is configured using a new nbemmcmd command option. Auditreports are generated using the new command, nbauditreport.

About NetBackup client optionThenewOffline option in the ClientAttributes properties lets administrators takeindividual clients offline to make the clients unavailable for backups. When aclient is offline, no backup status is listed for the client.

That is useful in a number of situations. For example, in the event of plannedmaintenance, you can take the client systems offline to avoid the unnecessaryerrors that thenneed to be investigated. This option can also be used to anticipatenew clients in the system. The clients can be listed in policies but configured asoffline until they are in place and ready to be used.

In addition, you can specify a period of time that the client is automatically enabledagain. That prevents users from forgetting about the clients thatwere in an offlinestate.

Volume GUID for Windows clusterThere are three types of volume mount points:

■ A drive letter such as, C:\.

■ A volume GUID path such as,\\?\Volume{26a21bda-a627-11d7-9931-806e6f6e6963}\.

■ A mounted folder such as, C:\MountD\.

Previous releases ofNetBackup forHyper-Vhadan issuewith volumeGUIDpathssuch as, \\?\Volume{26a21bda-a627-11d7-9931-806e6f6e6963}\. If volumeGUIDpaths exist in yourHyper-V environment, youneed to install thisNetBackuppatch or a later release.

This releaseofNetBackupsupportsVolumeGUIDpathnames forWindowsclustersas well as Hyper-V clusters. If you need assistance Contact Symantec TechnicalSupport to obtain the patch.

13New FeaturesAbout NetBackup client option

About NetBackup BMR enhancementsIn addition to the existing platforms, NetBackup BMR 7.0.1 supports restores ofHPIA-64 11.31 clients. The following section contains the exact lists of the featuresthat are supported or not supported on this platform.

Features that are supported in BMR 7.0.1 on HPIA-64 11.31 platform:

■ Full LVM volume manager support

■ VxVM volume manager support on non-bootable disk.

■ VxFS-based File Systems Restore support

■ Network and Media boot

■ Point In Time Restore

■ Latest ignite version support - C.7.9.261

■ Partial support for DDR (Dissimilar Disk Restore)Disk and partition mappingVolume length changes

Features that are not supported in BMR 7.0.1 on HPIA-64 11.31 platform:

■ BMR restore with NBAC enabled

■ Full BMRCONFIG supportVolume layout changes. For example, concatenated to mirror

■ SAN LUN-based volume restore

■ VxVM support for root and boot disk

■ SF 5.0.1 support

■ Non-bootable VxVM volume restore works using SF 5.0.

In this release of the NetBackup, the BMR feature contains an enhancement withhow shared resource trees are created.

Creating an SRT for WindowsWindows SRTs no longer require the user to supply a version of Windows. TheSRTs use a special version of Windows that is shipped with the boot server.

New FeaturesAbout NetBackup BMR enhancements

14

To create a Windows SRT

1 From the Start menu on the Windows BMR boot server that is to host theSRT, select Programs > Symantec NetBackup > Bare Metal Restore BootServer Assistant.

The Bare Metal Restore boot server Assistant appears.

2 Click Shared Resource Tree Administration Wizard.

The Shared Resource Tree Administration wizard appears.

You can use an SRT that contains the NetBackup client of 7.0 or higherversions to restore the back-level NetBackup clients.

3 Select the option to create a shared resource tree. Then follow the promptsto create a shared resource tree. Youmust provide the following information:

The name of the SRT is also used for the directorythat contains it. Only alphanumeric characters andthe underscore (_) character are allowed.

Name

Enter the description of the SRT. For example:Windows 2008 SRT

Description

When you create the 32-bit or 64-bit SRT for the firsttime a screen appears where you specify the sourcelocation of SRD.

For 32-bit SRT, specify the source location of‘srd.wim’, which is as follows:

<DVD root>\Addons\x86\BMRBS

For 64-bit SRT, specify the source location of‘srd_x64.wim’, which is as follows:

<DVD root>\Addons\x64\BMRBS

<DVDroot > is the root folder on the NetBackupWindows installation DVD.

Locations for the SRT

Enter the path of the BMR client software image.Path to the NetBackup clientsoftware image

About the supported boot media on Windows platformBoot media is used to boot a client and provide the Shared Resource Tree or theresources to mount a Shared Resource Tree. The boot media contains a smallruntime environment that includes a kernel, a RAM file system, libraries, andprograms. The client system firmware boots the kernel from the media. CD boot

15New FeaturesAbout NetBackup BMR enhancements

media also contains a Shared Resource Tree. If you use media to boot the clientsystem, youmust useBMR toprepare the appropriate bootmedia. You canprepareboot media at any time before the restore. However, a prerequisite is that theShared Resource Tree for the protected system must exist. Boot media is createdfrom the resources that are stored in an SRT. The bootmediamust be compatiblewith the commands and libraries in the SRT and the client.

The BMR restore process begins by network booting the client from a BMR bootserver or from BMR prepared boot media (CD or DVD).

Youcan restore a clientusingFastRestoreSRTsorLegacyOS-basedSRTs.Versionsolder than BMR 7.0.1 also supported floppy as a boot media if you selected theLegacy OS-based Restore option, on a Windows platform.

Note: The Legacy OS-based Restore of Windows Server 2008 SP2 systems can bedone with a Legacy OS-based SRT that is at Windows Server 2008 SP1 level. ThePrepare To Restore command allows this special scenario.

Note: In BMR 7.0.1, floppy-based restore is not supported.

In BMR 7.0.1, you can boot BMR clients only with the following options:

■ Network boot

■ CD/DVD Media boot

Note: In BMR 7.0.1, because of the elimination of PC-DOS, you do not need tocreate Boot Floppy. Therefore the Legacy Boot Floppy Wizard link on the bootserver Assistant screen is removed.

About the Legacy Restore functionIn BMR7.0.1, the LegacyRestore function ismodifiedwith the following changes:

■ PC-DOS is no longer required to run a Legacy Restore. Unlike in BMR 7.0, theLegacy Restore function in 7.0.1 boots from a WinPE boot image. This changein the boot process of the Legacy Restore option reduces maintenance andoverheads.In BMR 7.0.1, you do not need to do the following tasks:

■ Download and store DOS extensions.

■ Maintain the floppy disks, which are now outdated as media.

■ Download and maintain DOS-compatible drivers.

New FeaturesAbout NetBackup BMR enhancements

16

■ Maintain floppy disk Drives (FDDs) for BMR Restore purpose.

■ As a result of PC-DOS elimination, you do not need to create Boot Floppy.Therefore the Legacy Boot Floppy Wizard link on the boot server Assistantscreen is removed.

■ PC-DOS is replaced with WinPE, therefore the Legacy Restore can boot withthe PXE-based network option.

■ Unlike PC-DOS, WinPE does not require a 16-bit Windows Installer binary.Therefore, BMR 7.0.1 provides the Legacy Restore support also for the 64-biteditions of Windows.

■ PC-DOS-based Legacy Restore requires approximately eight reboots duringthe restore. With WinPE-based Legacy Restore, the number of reboots isreduced to approximately five.

Note:With WinPE in place of PC-DOS, the Legacy Restore requires an additionalfree space of 2 GB to 4 GB in the system’s boot partition. The boot partition is theone that contains the operating system .

AboutNetBackup for SQL server agent enhancementsThe NetBackup Database Extension graphical user interface for SQL contains anew option that enables you to use SQL server's native compression feature on abackup. That is a new feature for SQL 2008 and beyond. You can also addcompression to your backup by adding the entry, SQLCOMPRESSION TRUE, inthe SQL batch file.

The following figure shows the new option as it appears in the user interface.

17New FeaturesAbout NetBackup for SQL server agent enhancements

About Symantec OpsCenter enhancementsAnewoptionhas beenadded in theSelectViewNamedrop-down list of theReportwizard. The name of the option is None. You can see this option when you createor edit a report and specify the views that are associated with the report from theFilters section of the Select Parameters page in the Report wizard. Select theNone option from the Select View Name drop-down list if you do not want aspecific view to be associated with the report.

About Enterprise Vault 9.0 supportWithNetBackup7.0.1, theNetBackupEnterpriseVault agent supports EnterpriseVault 7.5, 8.0, and 9.0 configurations. The following lists describe the NetBackupEnterprise Vault 9.0 enhancements and the Enterprise Vault clusteringenhancements.

The following enhancements are made in Enterprise Vault 9.0:

■ Enterprise Vault partitions can use an EV Streamer API for storage, such as,partitions using Caringo Castor. NetBackup Enterprise Vault agent does notback up these partitions. This enhancement affects the following directives:

New FeaturesAbout Symantec OpsCenter enhancements

18

■ If the openpartition of the vault store uses the EV StreamerAPI for storage,backupwith theEV_OPEN_PARTITION=Vault Store namedirectivecompleteswith partial success. Only the Vault store database is backed up. In thiscase, it is recommended to use EV_VAULT_STORE_DB= Vault store name

directive.

■ The Closed partitions that use EV Streamer API for storage are notprotectedwith EV_CLOSED_PARTITIONS=Vault Store name directive. If allclosed partitions in the vault store use EV streamer API for storage, thenbackup with EV_CLOSED_PARTITIONS=Vault Store name directive fails.

■ TheReadypartitions that useEV StreamerAPI for storage arenot protectedwith EV_READY_PARTITIONS= Vault Store name directive. If all readypartitions in the vault store use EV streamer API for storage, then backupwith EV_READY_PARTITIONS= Vault Store name directive fails.

■ For Enterprise Vault 9.0, quiescence succeeds even if the Enterprise Vaultcomponent (Vault store or Index location) or its parent component is alreadyquiesced.

■ To upgrade from Enterprise Vault 8.0 to Enterprise Vault 9.0, you don't needto make any modifications in the policy.

The following Enterprise Vault clustering enhancements were made:

■ With NetBackup 7.0, the NetBackup Enterprise Vault agent supports VCS

■ When Enterprise Vault is clustered, and you want to configure NetBackupEnterprise Vault agent, make sure that the virtual cluster name on each nodeis the same as the NetBackup client name.

About NBSU support for NetBackup 7.0.1This release of NetBackup (7.0.1) includes an updated version of theNBSUutility.The version number for this utility is version 1.4.

In this release ofNetBackup theNBSU1.4utility contains support for IPv6networkaddressing and it has been ported to the zLinux platform. In addition, this releasecontains a fix for the Mac OS X platforms.

About NBCC and NBCCR enhancementsThis release of NetBackup contains updated versions of the NBCC, NBCCH, andNBCCR utilities to the NetBackup 7.0.1 version level.

19New FeaturesAbout NBSU support for NetBackup 7.0.1

NBCC was updated to ensure that it properly collects the EMM server hostnameson a clustered EMM server that does not have media servers on the same system.In addition, NBCC contains a change to ensure that it detects the exit status fromthe bpimagelist command. That produces a more consistent interpretation ofthe images in the Image Catalog.

About NetBackup Snapshot ClientWith this release of NetBackup 7.0.1, the NetBackup Snapshot Client offers thefollowing new enhancements:

■ Support for Solution Enabler 7.0 and 7.1 versions is added.

■ The EMC_Timefinder_* FIMS (snapshot methods) are supported with theVxFS+VxVM stack on Solaris.

About VMware vSphere 4.1NetBackup 7.0.1 adds support for VMware vSphere 4.1. vSphere 4.1 brings manynew features and performance enhancements to VMware environments. For adescription of vSphere 4.1, see the following:

http://www.vmware.com/support/vsphere4/doc/vsp_41_new_feat.html

About NetBackup documentation updatesMany books within the NetBackup documentation set have been updated for thisrelease. The following list shows a list of those books and the URL to where theyare posted on the Symantec Support Web site:

■ Symantec NetBackup Troubleshooting Guidehttp://entsupport.symantec.com/docs/357089

■ Symantec NetBackup Commands Guidehttp://entsupport.symantec.com/docs/357090

■ Symantec OpsCenter Administrator’s Guidehttp://entsupport.symantec.com/docs/357091

■ Symantec NetBackup Clustered Master Server Administrator’s Guidehttp://entsupport.symantec.com/docs/357103

■ SymantecNetBackup inHighly Available Environments Administrator’s Guidehttp://entsupport.symantec.com/docs/357092

■ Symantec NetBackup for SAP Administrator’s Guide for Windows

New FeaturesAbout NetBackup Snapshot Client

20

http://www.vmware.com/support/vsphere4/doc/vsp_41_new_feat.html

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

■ Symantec NetBackup for SAP Administrator’s Guide for UNIXhttp://entsupport.symantec.com/docs/357094

■ SymantecNetBackupforMicrosoftExchangeAdministrator’sGuide forWindowshttp://entsupport.symantec.com/docs/357095

■ Symantec NetBackup for Microsoft SharePoint Server Administrator’s Guidefor Windowshttp://entsupport.symantec.com/docs/357096

■ Symantec NetBackup Deduplication Guidehttp://entsupport.symantec.com/docs/357097

■ Symantec NetBackup Administrator’s Guide for Windows, Volume Ihttp://entsupport.symantec.com/docs/357098

■ Symantec NetBackup Administrator’s Guide for UNIX and Linux, Volume Ihttp://entsupport.symantec.com/docs/357099

■ Symantec NetBackup for NDMP Administrator’s Guidehttp://entsupport.symantec.com/docs/357100

■ Symantec NetBackup Security and Encryption Guidehttp://entsupport.symantec.com/docs/357101

■ Symantec NetBackup LiveUpdate Guidehttp://entsupport.symantec.com/docs/357102

■ Symantec NetBackup Release Noteshttp://entsupport.symantec.com/docs/347326

21New FeaturesAbout NetBackup documentation updates

New FeaturesAbout NetBackup documentation updates

22

Supported Platforms


■ About NetBackup 7.0.1 supported platforms

■ About NetBackup 7.0.1 platform proliferation support

■ NetBackup binary sizes

About NetBackup 7.0.1 supported platformsThis release of NetBackup supports all of the platforms that the NetBackup 7product supports in addition to the newplatforms thatwere added to this release.

To see the supported platform information that was released with NetBackup 7,see the following Technote on the Symantec Support Web site.


See “About NetBackup 7.0.1 platform proliferation support” on page 23.

AboutNetBackup7.0.1 platformproliferation supportChanges to the following list can occur before the final release ofNetBackup 7.0.1.For themost current supported platform information, see the followingTechnoteon the Symantec Support Web site:


This release adds support for the following platforms:

■ Added the following BMR platform proliferation support:

■ BMR Client AIX 6.1 x64

■ BMR Client SLES10 x64

2Chapter



■ BMR Client SLES11 x64

■ BMR Client support for Windows 2008 x32 and x64/2008 R2 x64

■ BMR Client support for Windows 7 x64 and Windows Vista x64

■ BMR client support for Solaris 10 x64

■ BMR client support for HP-UX 11 v3 (11.31) IA-64

■ BMRsupport for Oracle Enterprise Linux (RedHat 4 x64 and RedHat 5 x64with Oracle support)

■ Added OpsCenter AIX 6.1 support.

■ Added SQL Server W2008R2 support.

■ Added SQL Server W2008R2 support.

■ Added SharePoint 2010 on Windows 2008 SP2 and 2008 R2

■ Added Exchange 2010 SP1 support.

■ Added Z-Linux Oracle 10gR2/NetBackup Basic Client on RedHat 5 and SLES10 support.

■ Added Z-Linux Media Server support on RedHat5 and SLES 10.

■ Added EV9 support on Windows 2003 and 2008, 32- and 64-bit operatingsystems.

■ AddedNBSUutility support was added in preparation forNetBackup releases.

■ The version levels of NBCC, NBCCH, and NBCCR utilities are now 7.0.1.

■ Added VxFI-based EMC Symmetrix Frozen Image Methods (FIMs) on HP-UX11.31 support.

■ Added an NDMP and a PDDE stream handler with NetBackup 7.0.1.

■ Added a device qualification test suite for OST.

■ Added support for VMware vSphere 4.1.

■ The following VCS support:

■ VCS 5.0.1 support on HP-UX 11.31 IA64 with Master

■ VCS 5.0 MP3 support on Red Hat Enterprise Linux 4 x64 with Master

■ VCS 5.0 MP3 support on Solaris 10 SPARC with Master

■ VCS 5.1 support on Solaris 10 SPARC with Master

■ VCS 5.1 support on Windows Server 2003 x64 with Master

Supported PlatformsAbout NetBackup 7.0.1 platform proliferation support

24

■ VCS 5.1 SP1 AP1 support on Windows Server 2008 x64 with MicrosoftExchange Agent (Exchange 2010 support)

■ VCS 5.1 SP1 support on Windows Server 2008 R2 x64 with Master

■ Added snapshot support for HP-XP arrays for the following platforms:

■ HP-UX 11.31 IA64

■ RHEL 4.0

■ SUSE 11.0

■ Oracle Solaris Sparc 10.0

■ Windows 2008 x64

■ Added HP_XP_BusinessCopy and HP_XP_Snapshot are the new Frozen ImageMethods (FIMs).

■ Added HP_XP_BusinessCopy is used for taking mirror-based snapshots andHP_XP_Snapshot is used for taking COW-based snapshots.

■ Added HP_XP array and Hitachi array are almost the same.In NetBackup also, Hitachi_ShadowImage FIM is equivalent toHP_XP_BusinessCopy and Hitachi_CopyOnWrite is equivalent toHP_XP_Snapshot. Therefore, for the configuration and prerequisites, all thesteps applicable to Hitachi array are also applicable to the HP_XP arrays.For these steps, please refer to the Snapshot Client Administrator's Guide.These steps are similar to the Hitachi array configuration steps.

NetBackup binary sizesThe information in this section helps you determine if your NetBackupenvironment has the proper amount of disk space allocated to your servers tosafely and efficiently back up and restore all of the data.

Table 2-1 shows the approximate binary size of the NetBackup master and mediaserver software, and theNetBackup client software requirements for eachplatformand operating system that is compatible with NetBackup.

Table 2-1 NetBackp binary sizes for compatible platforms

Notes64-bitserver

32-bitserver

64-bitclient

32-bitclient

CPUArchitecture

OS/Version

64-bit binary compatible.3083MB928MBPOWERAIX 5.3

64-bit binary compatible.3083MB928MBPOWERAIX 6.1

25Supported PlatformsNetBackup binary sizes

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

Notes64-bitserver

32-bitserver

64-bitclient

32-bitclient

CPUArchitecture

OS/Version

1726MB510MBx64Asianux 2.0, 3.0

510MBx64Canonical Ubuntu 8.0

510MBx64CentOS 5.2, 5.3

510MBx64Debian GNU/Linux 4.0, 5.0

16MBx86FreeBSD 6.1, 6.2, 6.3, 7.x

64-bit binary compatible.Media server or clientcompatibility only.

1666MB632MBPA-RISCHP-UX 11.11





3012MB922MBIA64HP-UX 11.31

22MBPOWERMac OS X 10.5

22MBx86Mac OS X 10.5, 10.6

1662MB492MBx64Novell Open EnterpriseServer 2

16MBHP VAXOpenVMS 5.5



16MBHP AlphaOpenVMS 6.1





Supported PlatformsNetBackup binary sizes

26


Notes64-bitserver

32-bitserver

64-bitclient

32-bitclient

CPUArchitecture

OS/Version

16MBHP IA64OpenVMS 8.2

16MBHP IA64OpenVMS 8.3

16MBHP IA64/AlphaOpenVMS 8.3-1H1

1726MB510MB

x64Red Flag Linux 5.0

64-bit binary compatible.1726MB510MB

x64Red Hat Enterprise Linux 4.0(AS)

64-bit binary compatible.1726MB510MB

x64Red Hat Enterprise Linux 5.0(base)

Compatible with client only.351MB

IA64Red Hat Enterprise Linux 4.0(AS)

Compatible with client only.351MB

IA64Red Hat Enterprise Linux 5.0(base)

96MBPOWERRed Hat Enterprise Linux 4.0(AS)

96MBPOWERRed Hat Enterprise Linux 5.0(base)

12MBz/ArchitectureRed Hat Enterprise Linux 4.0(AS)

12MBz/ArchitectureRed Hat Enterprise Linux 5.0(base)

64-bit binary compatible.1726MB510MBx64Red Hat Enterprise LinuxDesktop 4.0

64-bit binary compatible.510MBx64Red Hat Enterprise LinuxDesktop 5.0

1726MB510MBx64Red Hat Enterprise Linux 5.0(Advanced)

64-bit binary compatible.525MBSPARCSolaris 9.0

64-bit binary compatible.2050MB639MBSPARCSolaris 10.0

27Supported PlatformsNetBackup binary sizes


Notes64-bitserver

32-bitserver

64-bitclient

32-bitclient

CPUArchitecture

OS/Version

64-bit binary compatible.1915MB439MBx64Solaris 10.0

Compatible with client only.345MBIA64SUSELinuxEnterpriseServer10 (SP1)

1662MB492MBx64SUSELinuxEnterpriseServer10 (SP1)

Compatible with client only.101MBPOWERSUSELinuxEnterpriseServer10 (SP1)

Compatible with client only.12MBz/ArchitectureSUSELinuxEnterpriseServer10 (SP1)

Compatible with client only.345MBIA64SUSELinuxEnterpriseServer11

1662MB492MBx64SUSELinuxEnterpriseServer11

Compatible with client only.12MBz/ArchitectureSUSELinuxEnterpriseServer11

Covers all compatibleWindows x86 platforms

1700MB600MBx86Windows

Covers all compatibleWindows x64 platforms

1900MB700MBx64Windows

Compatible with client only.600MBIA64Windows

Supported PlatformsNetBackup binary sizes

28

Product Dependencies


■ Operating system patches and updates

Operating system patches and updatesThis topic provides information on the product dependencies of this release ofNetBackup. You should verify that your operating system is up-to-date with allof the latest patches and upgrades before you install NetBackup. This section isa guide to informyou of the operating systems that require a patch or an upgrade.

Table 3-1 provides the known, minimum operating system (OS) patches andupdates. A vendormayhave released amore recent patch that supersedes a patchthat is listed in this table. Symantec recommends that you visit the Support Website of that particular vendor for their latest patch information.

Table 3-1 Operating system patches and updates for NetBackup

NotesPatchOperating SystemType and Version

You may need to reboot afterchanging to version 9.0.0.3.

AIX runtime libraries8.0.0.10 or 9.0.0.3 orlater

AIX 5.3

For the xlC.rte 8.0.0.10 fileset,you may need to install the IY91284fix to avoid a potential issue whencreating or updating the NetBackupdatabase. The IY91284 fix is part ofMaintenance Level 6.

xlC.rte 8.0.0.10

fileset

3Chapter

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


NetBackup 7.0 requires the AIX 5.3TL7 SP5 (5300-07-05-0831Maintenance Pack as a minimum.(Higherpatch levels shouldalsowork.)

You can use the oslevel -s

command toverifywhatMaintenancePack level you have installed.

AIX 5.3 TL7 SP5(5300-07-05-0831)

When you start Java user interfaceapplications on AIX 6.1 platforms anexception can occur. To prevent theexception, Symantec recommendsthat you install patch IZ16878 fromIBM® Support.

IZ16878AIX 6.1

The runtime libraries need to be at9.0.0.3 or later. You may need toreboot after you change to version9.0.0.3.

AIX runtime libraries9.0.0.3 or later

If you install AT on an HP-UXplatform, this patch is required.

COMPLIBS.LIBM-PS32HP-UX

Networking.NET-RUN:/usr/lib/libipv6.sl

HP-UX IA64

Networking.NET-RUN-64:/usr/lib/pa20_64/libipv6.1

Networking.NET-RUN-64:/usr/lib/pa20_64/libipv6.sl

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

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

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

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

Product DependenciesOperating system patches and updates

30



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

For HP-UX PA-RISC platforms, thisfileset is required:

Networking.NET-RUN:/usr/lib/libipv6.sl

HP-UX PA-RISC


Networking.NET-RUN-64:/usr/lib/pa20_64/libipv6.1


Networking.NET-RUN-64:/usr/lib/pa20_64/libipv6.sl


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

This patch is required for JAVA 6.0.PHSS_35385HP-UX 11.11

This patch is a LIBCL patch.PHSS_32226

Contains fixes for the following:

■ QXCR1000593919: purifyplus

dumps core in PA32

■ QXCR1000589142: dld crash inLL_new_descendent_listwhen theaCC application is exiting.


■ QXCR1000746161: dlsym()

hangs

■ QXCR1000593999: dld emitsassert messages for chatr+mem_check enabled 64-bitexecutables

PHSS_37516

This patch is necessary to enable anyC++ runtime code to work properly.

PHSS_26946

This patch is a libc cumulativepatch.

PHSS_27740

This patch contains a linker toolscumulative patch.

PHSS_26560

31Product DependenciesOperating system patches and updates



That is a recommended critical patchfrom HP that is required forsuccessful NetBackup client backups.

PHSS_32864

This patch enables HP-UX 11.11

mmap() to use large files from 2GB to4GB.

PHKL_26233

That is a recommended critical patchfrom HP that is required forsuccessful NetBackup client backups.

PHSS_35379

That is a recommended critical patchfrom HP that is required forNetBackup to use VxSS.

PHCO_29029

Allow POLL_INTERVAL to be set tozero in /var/stm/config/tools/monitor/dm_stape.cfg. Thatdisables the dm_stapemonitorwithin the Event Monitoring System.Symantec recommends that youupgrade to IPR0109.

PHSS_24045

This patch can cause problems withthe programs that have the setuidbit set. Hewlett-Packard ’s IT resourcecenterWeb site contains informationabout this patch.

www1.itrc.hp.com

PHSS_30970

S700_800 11.11 libc cumulative patch

The above patch has dependency onthe following patches:

■ PHCO_31923 (critical patch):s700_800 11.11 libc cumulativeheader file patch

■ PHKL_34805 : 700_800 11.11JFS3.3 patch; mmap

PHCO_35743



32



Symantec recommends that allcustomers running 11.23 install thispatch.

PHCO_33431

That is a recommended critical patchfrom HP that is required so thatdlopen works properly.

PHSS_34858

That is a recommended critical patchfrom HP that NetBackup requires,particularly when you attempt to runNetBackup with NetBackup AccessControl (NBAC).

PHKL_31500

Contains fixes for the following:

■ QXCR1000593919: purifyplus

dumps core in PA32


■ QXCR1000746161: dlsym()

hangs

■ QXCR1000593999: dld emitsassert messages for chatr+mem_check enabled 64-bitexecutables

PHSS_37492


The operating system version mustbe SLES 10 update 2 or greater to runNetBackup 7.0.

SLES 10 update 2SLES10 x64

Change Request ID - 6815915111712-11 (or greater)Solaris 9 SPARC 64-bitclient

111722-04 (or greater)

Patch: 112908-29 (orgreater)

Patch: 112874-31 (orgreater)




Change Request ID - 6723423122300-53

The server is supported on update 4(08/07) and newer.

update 4 (08/07) andnewer

Solaris 10 SPARC 64-bit(server and client)



Change Request ID - 6815915119964-21Solaris 10 x64


Microsoft hotfix KB913648 containsthe necessary updates to run VolumeShadow Copy.

KB913648Windows 2003 SP1

Microsoft storporthotfixWindows x64 (SP1 andSP2)

That is a suggested fix that applies to64-bit versions of Windows Server2003, XP, and Windows Vista.

Microsoft microcodereliability update

Windows 2003, XP, andVista

Microsoft hotfix KB952696 containsthe necessary updates to ensure thatyou can back up Windows 2008encrypted files on Windows x32 andWindows x64 systems.

KB952696Windows 2008 x32 andx64

The following additional product dependency information applies to this releaseof NetBackup:

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


34

Note: That does not apply to NetBackup encryption. NetBackup encryption isseparate from the file system encryption,meaning that NetBackup-encryptedfiles are backed up. In addition, this hotfix is not needed for any Windowsversion before Microsoft Windows Vista or Windows 2008 server. If you arerunning Vista or Server 2008, please refer to KB952696 to see if this hotfix isrequired for your operating system version



36

Operational Notes andIssues


■ About NetBackup 7.0.1 known issues

■ About documentation issues

■ About General NetBackup issues

■ About NetBackup installation and upgrade issues

■ About Bare Metal Restore (BMR) issues

■ About NetBackup database agents

■ About NetBackup Deduplication

■ About NetBackup Snapshot Client issues

■ About NetBackup Hyper-V issues

■ About NetBackup NDMP issues

■ About NetBackup OpsCenter issues

■ About NetBackup Vault issues

■ About NetBackup VMware issues

About NetBackup 7.0.1 known issuesThis section contains the new operational notes and known issues that pertainto the NetBackup 7.0.1 release. And because NetBackup 7.0.1 is an enhanced

4Chapter

progression of NetBackup 7.0 GA, you may want to refer to the NetBackup 7.0Release Notes for additional information. The NetBackup 7.0 Release Notes andNetBackupAdditionalOperationalNotes documents are available on theSymantecSupport Web site. These documents contain general information about theNetBackup 7.0 GA release.

See, NetBackup 7.0 Release Notes for UNIX, Windows, Linux on the SymantecSupport Web site.

See, NetBackup 7.0 Additional Operational Notes on the Symantec Support Website.


In addition to this release, there are hotfixes that are already available for someof the known issues described in this chapter. Please visit the NetBackup 7.0.1LateBreakingNews page for the latest updates on known issues and to downloadhotfixes that are currently posted to address the those issues.

See, http://support.veritas.com/docs/358291

About documentation issuesThe following items describe known issues or changes to the NetBackupdocumentation for this release:

■ Multiple changeshave beenmade to theNetBackupOpsCenterAdministrator'sGuide and this document has been released again with this release. Includedin themany changes are instruction onhow to install or upgrade to this versionof OpsCenter.See the following Technote on the Symantec Support Web site.http://entsupport.symantec.com/docs/357091

■ TheNetBackupSnapshotClient 7.0Administrator’sGuide states theFlashSnapsupport incorrectly.The following statement describes the FlashSnap support in Snapshot Clientappropriately:FlashSnapsupportsVxVMfull-sized instant snapshots, butnot space-optimizedsnapshot. Additionally, FlashSnap supports VxVM volumes in a shared diskgroup. For support configurations, please refer to the Snapshot Client SupportMatrix.

■ Page 90 of the Symantec NetBackup 7.0 Release Notes states the following:

Enhancements have been made that enables a nonroot NBU_Admin or Vaultoperator to perform the tasks that they otherwisewould not be able to performbecause of permission problems. These enhancements specifically target a

Operational Notes and IssuesAbout documentation issues

38

http://support.veritas.com/docs/358291


systemwhereNBAC is configured and theVault servicemanages the importantread-write data. For example, these enhancements have the following effecton users who have upgraded from previous versions to NetBackup 7.0:

■ "If pre-NetBackup 7.0 sessions are not processed completely before anupgrade, Symantec recommends that you process all these sessions(meaning that you complete all ejects and reports) before you upgrade. Ata minimum, you should copy the summary.log from the sidxxx directoryto a new sidxxx/logs directory to accommodate the eject and reportseligible sessions."

■ And so on...

These enhancements apply to a NetBackup Vault 7.0 system irrespective ofwhether NBAC is configured or not. The effects that are listed apply to bothNBAC and non-NBAC systems.

■ Page 90 of the Symantec NetBackup 7.0 Release Notes states the following:"If you upgrade toNetBackup 7.0 and decide to downgrade to a pre-NetBackup7.0 version, you must make sure that you account for the enhancements thatwere packaged in NetBackup 7.0. For example, log files are written tosidxxx/logs, and files and folders have restrictive permissionswhen they arecreated."This statement isnot applicable asdowngradingor rollingback fromNetBackup7.0 to a previous version is not supported.

■ The NetBackup Administrator’s Guide, Volume I should list additional files intheprocedureaboutmoving theNetBackupdatabase. In “Moving theNetBackupdatabase from one host to another,” the file list in steps 5, 10, and 12 shouldinclude the following files:NBDB.db, NBDB.log, EMM_INDEX.db, EMM_DATA.db, DBM_DATA.db, DBM_INDEX.db,DARS_DATA.db, DARS_INDEX.db

■ (ET2008796) The NetBackup Administrator’s Guide, Volume I contains a notein the sections that describe how to perform a full database validation:To perform a full database validation, shut down NetBackup and start onlythe database service. Although this note appears in the NetBackupdocumentation, it is not included in the onlinehelp for theNetBackupDatabaseAdministration utility.

■ TheNetBackupAdministrator’s Guide, Volume I incorrectly refers to the bprdservice as the NetBackup Request Manager. The name for bprd is now theNetBackup Request Daemon.

■ The following statement in the NetBackup 7.0 Enterprise Vault Agentadministrator's Guide is not valid and should be ignored.

39Operational Notes and IssuesAbout documentation issues

"NetBackup 7.0 does not support the Enterprise Vault agent on an EnterpriseVault 8.0 server in an Enterprise Vault cluster configuration."TheNetBackup 7.0.x Enterprise Vault agent does support bothMSCS andVCSclustered environments ofEnterpriseVault (except for the followingexception).Enterprise Vault 7.5 is not supported in VCS clustered environment.

■ The following line in the NetBackup High Availability Administrator's Guideis incorrect."Verify that you have the NetBackup Enterprise Server 7.0.1 installationprogram and a valid license key. Youmust also have a valid license key for theNetBackup OpenStorage option, if you perform backups to tape."The line should read as follows:"Verify that you have the NetBackup Enterprise Server 7.0.1 installationprogram and a valid license key. Youmust also have a valid license key for theNetBackup SharedStorage option, if you perform backups to tape."

About General NetBackup issuesThe following list contains known issues that apply to NetBackup:

■ (ET2084842) When you configure backup selections in a policy, a schedulingproblemcanoccurwith theuse of theUNSET_ALLdirective. If theUNSET_ALLdirective appears alone between NEW_STREAM directives, that can cause aschedule to run too frequently.The following is an example of a problematic directive list:

NEW_STREAM

UNSET_ALL

NEW_STREAM

File_1

NEW_STREAM

File_2

NEW_STREAM

File_3

■ HOST NAME CACHINGNetBackup 7.0.1 introduces the caching of host name to IP addressmappings,whichminimizes thedelays encounteredduring repeated lookups for annameor address that cannot be resolved. Most NetBackup processes have anin-memory cache and all NetBackup processes on the same host also share acache stored on the file system.

The cache entries have a life span of one hour, for both successful andunsuccessful resolution attempts, to suppress the otherwise repeated lookups.

Operational Notes and IssuesAbout General NetBackup issues

40

Hence, NetBackup does not recognize any changes to /etc/hosts or DNS forup to one hour. For NetBackup to recognize the change immediately, do thefollowing:

■ Correct the host name to IP address mapping in the external facility.

■ To clear the NetBackup file system cache, run the following command:bpclntcmd -clear_host_cache

■ To clear the in-memory cache, stop and restart theNetBackup process thatneeds the updated mapping.

About NetBackup installation and upgrade issuesThe following items describe known issues or changes to the NetBackup installand upgrade processes:

■ The NetBackup 7.0 Release Notes document does not specifically state that itdoes not support importing images to a back-levelmedia server. The documentstates the following:The backup images that are created under an older version of NetBackup arerecoverable with a newer version of NetBackup.The official statement should read:The backup images that are created under an older version of NetBackup arerecoverablewith a newer version ofNetBackup.However, NetBackup does notsupport importing images to a back-level media server.

■ If uninstalling 7.0.1, also remove the following directory:On UNIX: /usr/openv/var/host_cache

On Windows: Install_path\ NetBackup\var\host_cache

The directory may not exist for the following reasons:

■ The installation or upgrade to 7.0.1 failed and no processes were started.

■ The installation was a non-administrator installation.

■ The directory previously had been manually removed.

■ (ET2011773) Upgrading the NetBackup Java Console from 7.0 to 7.0.1For Windows x86 client systems, you cannot use LiveUpdate to upgrade theNetBackup Java Console from 7.0 to 7.0.1. To upgrade the console from 7.0 to7.0.1 on this platform you must perform a local, manual installation of theconsole.This problem is scheduled to be fixed in NetBackup 7.0.1.

■ (ET2057896)Whenyou installNetBackup7.0.1, youmay receive apopupdialogbox that shows the wmiprvse.exe process has control of the NetBackup DLLs

41Operational Notes and IssuesAbout NetBackup installation and upgrade issues

and interrupted the install. To resolve this issue and continue with theinstallation, youmust stop theWindowsManagement Instrumentation (WMI)service, complete the install, and restart the service.

Use the followingprocess to stop theWMIservice and complete the installation:

■ Open the Services Control Manager. Select Start > Control Panel >Administrative Tools > Services.

■ Select the Windows Management Instrumentation service.

■ Right click on the service and select Stop.

■ ClickOK in the dialog box that appeared during theNetBackup installation.That enables the NetBackup installation to continue.

■ After the installation completes, return to the Services Control Manager,and select the Windows Management Instrumentation service.

■ Right click on the service and select Start to start the WMI service again.

■ (ET2010714) Installation failure message on Windows systemsAfter you run a LiveUpdate policy on Windows systems to upgrade toNetBackup 7.0.1, the activity monitor may report an exit status 77 error. Thiserror code may indicate that the installation that the LiveUpdate policyexecutedwas unsuccessful. If this error code appears, examine the installationlog file on the remote system where the installation error occurred. The logfile is located in the following location:% ALLUSERSPROFILE%\Symantec\NetBackup\InstallLogs\

Search the installation log for the following error indications:

■ Strings that include Return Value 3.

■ Starting with NetBackup 7.0, important log messages are color coded asfollows:Yellow = warningRed = error

■ (ET2017691) The Windows 7 Installer appears to have the capability toright-click on a product entry and select repair in theAdd/RemoveProgramsconsole. That is not compatible with the NetBackup mechanism. To performrepairs, the user needs to re-launch setup.exe for the 7.0.1 release and usethe maintenance operations of the installation wizard.

■ (ET2068830) The PBX service may not restart after you upgrade NetBackup7.0 to 7.0.1 and then reboot the system on a MAC 10.5 client. If you encounterthis issue, use the following procedure to resolve this issue.

After youupgrade the clientwithNetBackup 7.0.1 perform the following steps.

Operational Notes and IssuesAbout NetBackup installation and upgrade issues

42

■ Change directories to the following directory:cd /Library/StartupItems

■ Open the directory vxpbx_exchanged.

■ Rename the directory vxpbx to vxpbx_exchanged.

■ Open the file StartupParameters.plist and change the value for Providesfrom vxpbx to vxpbx_exchanged.

■ Enter the following command to verify that the StartupParameters.plistfile has been changed.cat StartupParameters.plist

■ Reboot the computer andverify that thePBXservice is started. The contentsof the file should look similar to the following:

cat StartupParameters.plist

{

Description = "Symantec Private Branch Exchange";

Provides = ("vxpbx_exchanged");

Requires = ("Network");

Uses = ("Network");

OrderPreference = "Early";

}

Restart the PBX service manually after reboot.

■ Change directories to the following directory:/opt/VRTSpbx/bin

■ Execute the following command to start service manually../vxpbx_exchanged start

■ (ET2120189) The installerwrites the pd.conf file forMSDP/PDDOwithdefaultsettings to the media server when you install this Release Update. If you wantto preserve the previous pd.conf settings, copy the existing pd.conf file to analternate location before you install this patch, and then update thepost-upgrade pd.conf file appropriately.

About Bare Metal Restore (BMR) issuesThe following items describe known issues or changes to the NetBackup BMRfeature for this release:

■ (ET2009430) Using BMR to restore NetBackup 7.0.1 clients:

43Operational Notes and IssuesAbout Bare Metal Restore (BMR) issues

To use BMR to restore NetBackup 7.0.1 clients, you are not required to add aNetBackup 7.0.1 Hotfix in the BMR shared resource tree (SRT). You need tocreate the SRT based on the NetBackup 7.0 client and use that SRT to restorethe NetBackup 7.0.1 clients.

■ (ET2038632) In BMR7.0.1, there is an inconsistency in Java andWindowsuserinterfaces on the policy creation screen. In the Java user interface, on the AddNew Policy > Attributes tab, the Bare Metal Restore check box is by defaultselected. In the Windows user interface, the Bare Metal Restore check box isby default cleared. Ideally in both user interfaces, the Bare Metal Restorecheck box should be by default cleared.

■ With a 7.0.1 BMR master server and SuSE11_x64 clients that have multipledevices configured and /etc/mdadm.conf in place, after aDDRoperationMultiDevices fails to start. That occurredwhen the devicesweremapped to differentdisks.The result of this issue is that the user does not see the multiple devices afterthe BMR restore.If you encounter this issue update /etc/mdadm.conf file manually, after therestore. Update the file with the disk information that you mapped the MDdevices to and then scan for Multi Devices.mdadm --assemble --scan

The following example may help you understand the work-around better:If the original /etc/mdadm.conf file contains the following:

DEVICE /dev/sdc1 /dev/sdd1

ARRAY /dev/md0 devices=/dev/sdc1, /dev/sdd1

Later, during DDR md0 was mapped to /dev/sdh1 and /dev/sdi1. After therestore you need to update the /etc/mdadm.conf file as follows:

DEVICE /dev/sdh1 /dev/sdi1

ARRAY /dev/md0 devices=/dev/sdh1,/dev/sdi1

■ On an HP-UX 11.31 IA64 BMR Boot Server, the SRT creation may fail if thekernel parameter base_pagesize default value is not 4.To resolve this issue, use SAM or the following command to set the defaultvalue of the kernel parameter,base_pagesize, to4. Youmust reboot the serverto make sure the parameter gets affected and then try to create an HP-UX11.31 IA64 SRT.#/usr/sbin/kctune -B -C '' base_pagesize='4'

■ SLES10_x64 andSLES11_x64Clientswith ‘/’ onMultiDevice is not supportedin 7.0.1If you have an SLES10 or an SLES11 client configured with a slash character“/” on a Multi Device restore, it cannot be restored with a 7.0.1 BMR masterserver.

Operational Notes and IssuesAbout Bare Metal Restore (BMR) issues

44

■ During restore of SUSE 11 client (that uses LUNs), on some hardware, therestore goes into DDRmode even if the scsiLoadOrder is correct. Out-of-dateHBA firmware causes this issue.To work around this issue, ensure that the latest firmware is applied to theHBAs before you perform a BMR backup and try to restore it. If the problemstill appears, allow the discovery to occur so that the configuration isdiscovered.Thenmap theoriginal configuration to thediscovered configurationand carry out a restore and use the sameprocess as youwould normally followto do a DDR.

■ BMR restore environment may crash when you restore a BMR AIX 6.1 clientwith the BMR Shared Resource Tree that is based on AIX 6.1 TL0 SP5 or olderservice pack levels.You may encounter this issue when you set up the network and mount theSRT from the BMR Boot server.The root cause may be the network and NFS-related issues. That is becausetheAIX 6.1 SP5 or older versions cannegatively affect the BMRmini-operatingsystem-based restore environment.To avoid this situation, use a BMR Shared Resource Tree that is based on AIX6.1 TL0 SP6 level or newer service pack levels.

■ (ET2010465)ABMRRestore hangs during a SANBoot that uses a Solaris 10x64Update 7 SRT with the Emulex BIOS enabled.On aSolaris 10x64 computerwithEmulexHBAcardwith booting enabled fromSAN disks, sometimes BMR Restore hangs for Solaris 10x64 Update 7 SRT.Solaris 10x64Update 7 OS installationmedia also fails to boot while SAN bootis enabled.

If you encounter this issue, you can do the following:

■ Use the Solaris 10x64 Update 8 SRT for a restore.

■ Donot configure the SANdisk as the first, bootable disk before the restore.After a successful restore, configure it so that you can boot from acorresponding SAN disk.

■ (ET2006774) The disk names changes after a BMR restore for Solaris 10x64clients with SATA disks (with names like c?d?).

OnSolaris 10x64machineswithSATAdisks, sometimes the "target" field doesnot appear in the disknames. For example, the disknames appear in the formatc?d? instead of the usual c?t?d? format. In such a scenario, if there are SANdisks that were made available to the client after OS installation, the disknames can change in the restore environment. The change in the disk namesare handled to update the vfstab entries. But this disk name change is nothandled for other situations like, imported disk devices into Solaris local Zones.


If the client machine has Solaris zones with imported disk devices, then aftera BMR restore, update the Solaris zone configuration manually with correctthe disk names.

■ Failures in starting BMR restore of Solaris 10x64 clients.With Solaris 10 x64 clients, sometimes the network-based BareMetal Restoredoes not start after the Prepare-To-Restore step. That is because the clientmachine is not able to get the PXE/DHCP response from the Boot Server.

After the Prepare-To-Restore step, restart the DHCP server on the BMR BootServer with the command, svcadm restart dhcp-server.

■ (ET2010894) A DDR restore involving mapped RAID5 volume from a Nameddisk set of SVM fails.This issue only affects the Solaris clients that use RAID5 volumes in the SVMNamed disk sets. For these clients, if the BMR configuration is edited to mapthe RIAD 5 volumes from SAN disks to internal disks, BareMetal Restore failsbecause of problems when the named disk set is created.For this type of issue, a system-only restore works. You can then restore orimport the SVM disk set manually.

About port usage during a restore operationDuring a BMR restore, the bpcd command uses port number 13782 forcommunication. The following table lists the ports and services that are usedduring BMR restores.

Table 4-1 Port usage during a restore

WindowsLinuxUNIXPortService

XXX67, 68bootp/DHCP

Xping

XXUnreservedlockd

XXUnreservedmountd

XX2049nfsd

XX111portmapper

X (forbootparam onSolaris only)

rpcbind

XXUnreservedstatd

Operational Notes and IssuesAbout Bare Metal Restore (BMR) issues

46

Table 4-1 Port usage during a restore (continued)

WindowsLinuxUNIXPortService

XXX69tftp

XXX13724vnetd

XXX13782bpcd

X445Windows filesharing

About the supported boot media on a Windows platformBoot media is used to boot a client and provide the Shared Resource Tree or theresources to mount a Shared Resource Tree. The boot media contains a smallruntime environment that includes a kernel, a RAM file system, libraries, andprograms. The client system firmware boots the kernel from the media. CD bootmedia also contains a Shared Resource Tree. If you use media to boot the clientsystem, youmust useBMR toprepare the appropriate bootmedia. You canprepareboot media at any time before the restore. However, a prerequisite is that theShared Resource Tree for the protected system must exist. Boot media is createdfrom the resources that are stored in an SRT. The bootmediamust be compatiblewith the commands and libraries in the SRT and the client.

The BMR restore process begins by network booting the client from a BMR bootserver or from BMR prepared boot media (CD or DVD).

Youcan restore a clientusingFastRestoreSRTsorLegacyOS-basedSRTs.Versionsolder than BMR 7.0.1 also supported floppy as a boot media if you selected theLegacy OS-based Restore option, on a Windows platform.

Note: The Legacy OS-based Restore of Windows Server 2008 SP2 systems can bedone with a Legacy OS-based SRT that is at Windows Server 2008 SP1 level. ThePrepare To Restore command allows this special scenario.

Note: In BMR 7.0.1, floppy-based restore is not supported.

In BMR 7.0.1, you can boot BMR clients only with the following options:

■ Network boot

■ CD/DVD Media boot


Note: In BMR 7.0.1, because of the elimination of PC-DOS, you do not need tocreate Boot Floppy. Therefore the Legacy Boot Floppy Wizard link on the bootserver Assistant screen is removed.

About the Legacy Restore function in BMRIn BMR7.0.1, the LegacyRestore function ismodifiedwith the following changes:

■ PC-DOS is no longer required to run a Legacy Restore. Unlike in BMR 7.0, theLegacy Restore function in 7.0.1 boots from a WinPE boot image. This changein the boot process of the Legacy Restore option reduces maintenance andoverheads.In BMR 7.0.1, you do not need to do the following tasks:

■ Download and store DOS extensions.

■ Maintain the floppy disks, which are now outdated as media.

■ Download and maintain DOS-compatible drivers.

■ Maintain floppy disk Drives (FDDs) for BMR Restore purpose.

■ As a result of PC-DOS elimination, you do not need to create Boot Floppy.Therefore the Legacy Boot Floppy Wizard link on the boot server Assistantscreen is removed.

■ PC-DOS is replaced with WinPE, therefore the Legacy Restore can boot withthe PXE-based network option.

■ Unlike PC-DOS, WinPE does not require a 16-bit Windows Installer binary.Therefore, BMR 7.0.1 provides the Legacy Restore support also for the 64-biteditions of Windows.

■ PC-DOS-based Legacy Restore requires approximately eight reboots duringthe restore. With WinPE-based Legacy Restore, the number of reboots isreduced to approximately five.

Note:With WinPE in place of PC-DOS, the Legacy Restore requires an additionalfree space of 2 GB to 4 GB in the system’s boot partition. The boot partition is theone that contains the operating system .

About NetBackup database agentsThis topic contains the information that pertains to the NetBackup databaseagents for this release.

Operational Notes and IssuesAbout NetBackup database agents

48

About NetBackup DB2 database agentAbout the IBM DB2HPU utility with NetBackup for DB2

The IBMDB2HighPerformanceUpload (DB2HPU)utility performs faster databaserestores. The utility can achieve substantially higher performance by directlyaccessing the database files, bypassing the DB2 database manager.

However, an issue (ET1942214) may occur when this utility runs on a client in apartitioned database environment, where the DB2 nodes are distributed acrossmultiple clients. This scenario requires additional NetBackup configuration. Forinformation on the configuration additions that you need to make to enable thisutility to run NetBackup for DB2 in this environment see the following Technoteon the Symantec Support Web site.


About NetBackup for SharePoint Server issuesThe following operational issues exist for SharePoint Server 2010:

■ Group Work Site:subsites fail browse after parent site collections restore.Restore only one site collection at a time. If you restore more than one sitecollection in the same restore operation, you cannot browse the subsites forthat site collection.

■ Report ID is incremented after granular restore.If a deleted report is restored, the report ID is incremented upon restore. Tomaintain the original report ID value, restore the entire report container.

■ Restores are not supported for “Web Analytics Service App” and “WordAutomation.”

■ Restore of SharePoint 2010 Blog subsites results in canned items beingduplicated and comments missing.

■ Enterprise Keyword value is gone after a granular restore.The granular restore of enterprise keywords is not supported.

■ Predecessors are no longer linked for documents after a granular restore.If a document is deleted that has predecessors, the predecessors list is notrestored after a granular restore.

■ Whenyou restore aBasicMeetingWorkspace a folder iconappears indocumentand picture libraries.Restoring a document or a picture library in a Basic Meeting Workspace maycause an empty folder icon to get added. Delete this empty folder icon.

■ Document sets are not restored correctly.

49Operational Notes and IssuesAbout NetBackup database agents


After you perform a granular restore of a SharePoint 2010 document set atthe site collection level, the document set (and documents) are missing. If yourestore a document set at the subsite level, the document set is restored as afolder and themetadata is incorrect. Contact Symantec Technical Support fora fix to address this issue.

■ Document Set folder appears after a site restore that has Document Sets.After you restore a Document Center site a new folder named “Document Set”appears.

■ InfoPath service icons are missing.This issue will be fixed in a future release.

■ SharePoint 2010: Application pool gets createdwhen you restore the databaseeven though the ‘preserve existing settings’ checkbox was selected.Whenyou restore aWebapplication, a newapplicationpool is created for eachrestore. The original application also remains and can be deleted.

■ Granular backup is status 1, path is too long.SharePoint granular backup returns status 1 where the SQL server is runningon a W2K8 SP2 system. Examine the bpbkar log to determine if the followingmessage appears:nbfs_initialize_link_file(): ERR - Unable to open _nbfsd_link_list_

file

If the message appears, you may need to apply the following patch to yourW2K8 SP2 system to allow for long path names:http://support.microsoft.com/kb/955012

■ Site collection and subsite themes are not restored.Manually select the desiredtheme after you perform a restore.

The following operational issues exist for all versions of SharePoint Server:

■ Document workspace: Web part does not get restored when you restore a listor a library.Restore the list item you deleted or the library container for the list. Thenrestore the default.aspx file from the subsite or the site collection.

■ Survey container ‘Time Created’ value is not retained after a granular restore.For a SharePoint survey list, after a restore the “Time Created” value reflectsthe value at the time of the granular restore.

■ The NetBackup 7.0.1 GUI does not filter objects when granular or stream isspecified in the policy.For SharePoint 2007and later,when theSharePoint policyhas granular restoreenabled only SQL objects in the farm are backed up.

■ ‘Administrative Reports’ container does not restore.

Operational Notes and IssuesAbout NetBackup database agents

50

http://support.microsoft.com/kb/955012

Granular recovery of the SharePoint 2010 Central Administration Web siteand the Shared Services Administration Web site are not supported.

■ TheAppPool identity account is set toNetworkService after a restore of aWebapplication. Reset the AppPool identity account to the proper account.

■ Granular restore of large documents do not restore.For a granular restore of a large document (over 50MB), restore the documentto a file system. Then upload the document into SharePoint.

■ Restoring a folderwith unique permissions set results in permissions not beingset correctly.After you restore a folder that has unique permissions and that has itemswithinherited permissions, the folder has inherited permissions and the itemshaveunique permissions. The permissions must be reset.

■ Picture versions fails to restore with container restore.Redirect the restore to a file system and then upload the items to SharePoint.

■ Granular restore fails when initiated from a Solaris master.Granular restores fail when initiated from a Solarismaster server. Launch therestore operation from the SharePoint front-end server.

■ A SharePoint Content database may not be added back to an application aftera restore has completed.When you restore a single Content database from a multi-Content databaseWeb application, the restore completes successfully but the database is notlinked back to theWeb application.Use the SharePoint Central Administrationinterface to relink the database to the Web application.

■ Remote browse of SharePoint objects window does not show the database inthe right pane for the object highlighted.The remote browse window does not display the Content databases. To backup a particular content database, include the Content database name in thebackup selection list.

■ Comments on versioned documents are not restored.If you delete a versioned document that contains comments, the commentsare not restored after a granular restore.

■ The NetBackup 7.0.1 ncfgre logfile indicates a SQLSTATE ERROR: Functionsequence error.Attempt the restore again.

■ Some list items show ‘0001’, ‘0002’ rather than the list name in theNetBackupBAR GUI.

■ Redirected granular restores do not get initiated when the restore is to a UNCpath with a space in it.

51Operational Notes and IssuesAbout NetBackup database agents

A redirected granular restore to a UNC path must not contain spaces in thepath name.

About NetBackup for Exchange server database agentA restore of an Exchange database in a clustered configurationmay fail when youattempt to restore from an Exchange stream (non-VSS) backup image. Thefollowing error message appears in the detailed job status:

Error bpbrm(pid=5276) from client evs3: ERR - error writing Exchange object:

Microsoft Information Store:\Storage Group1\Log files_1278064490

Error: BEDS 0xE00002F2: Cannot restore an Exchange database or log file. Review the

resource credentials for the job, and then run the job again.

This problem occurs when you attempt to open a file in the temporary locationfor log files. You can perform the following to work around this issue:

Change the temporary location for log files in the restore GUI from the defaultlocation (C:\temp) to a location that both nodes in the cluster share.

About NetBackup DeduplicationThe following items describe known issues or changes to the SymantecDeduplication feature for this release:

■ NDMP stream handler for deduplicationNetBackup7.0.1 includesanewstreamhandler for theNetAppNDMPufs_dumpdata format. Streamhandlers improvebackupdeduplication ratesbyprocessingtheunderlyingdata stream.TheNDMPstreamhandler removesNDMPheadersso that identical files and segments onNDMPstorageandonnon-NDMPstoragededuplicate appropriately.After youupgrade toNetBackup7.0.1, deduplication rates for backups ofNDMPdata that has already been deduplicated decrease. The NDMP stream handlerprocesses the stream differently than in NetBackup 7.0. The low rate appliesonly to the first backup after you upgrade.The stream handler supports all versions of NetApp filers that NetBackupsupports.

■ Windows System State stream handler for deduplicationNetBackup 7.0.1 includes a new streamhandler for theWindows SystemState.Stream handlers improve backup deduplication rates by processing theunderlyingdata stream.SystemStatenowdeduplicates acrossmultiple backupsand between clients.

Operational Notes and IssuesAbout NetBackup Deduplication

52

After youupgrade toNetBackup7.0.1, youdonot have to backupSystemStateto non-deduplication storage. (Previously, Symantec recommended that usersdo not deduplicate Windows System State.)

■ The NetBackup 7.0 Release Notes contain an error in the "About Clientdeduplication" topic that is onpages 13 and14 of that document. The followinglist item incorrectly states support for HP-UX and AIX. Those two platformsshould not have been a part of this list."Supported over all Tier 1 NetBackup clients (for example, Windows, Linux,HP-UX, Solaris, and AIX)"For the most up-to-date information about supported platforms, refer to thefollowing Technote on the Symantec Support Web site.http://entsupport.symantec.com/docs/338123

About NetBackup Snapshot Client issuesThe following itemsdescribe known issues or changes to theNetBackupSnapshotClient feature for this release:

■ (ET2040058) File-size limit for FlashBackupFlashBackup (and FlashBackup-Windows) are NetBackup policy types thatcombine the speed of raw-partition backupwith the ability to restore individualfiles. FlashBackup technology is especially designed for the file systems thatcontain many small files, such as millions of files. Please note: For large files,the current FlashBackup file-size limit is 1 terabyte (TB). If a file is 1 TB orlarger, the backup succeeds but the large file cannot be restored individually.The large-file data is still available in the backup. You can restore large filesby restoring the backed-up, raw partition that contains the files

■ (ET2003460) Beginning in NetBackup 6.5 GA, the use of FlashBackup in aMicrosoft Cluster (MSCS) environment is supported with the followinglimitation:Raw partition restores can only be performed when the disk being restored isplaced in extended maintenance mode or removed from the MSCS resourcegroup.Earlier versions of MSCS (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.

■ Beginning in NetBackup 6.5 GA, the use of FlashBackup in aMicrosoft Cluster(MSCS) environment is supported, with the following limitation:

53Operational Notes and IssuesAbout NetBackup Snapshot Client issues

Raw partition restores can only be performed when the disk being restored isplaced in extended maintenance mode or removed from the MSCS resourcegroup.

■ A stepwasmissed in theNetBackup Snapshot Client 7.0Administrator's GuideThe 5th step in the following procedure was missed from the NetBackupSnapshot Client 7.0 Administrator's Guide.The following topic contains the correct procedure to create space-optimizedsnapshots:See “Creating space-optimized snapshots” on page 54.

■ (ET2073495)NetBackupmulti-streambackups that use an off-host datamovermethod may take too long to create the 3pc.conf file on a large media server.

NetBackup can perform two kinds of off-host backups by means of a datamover: the NetBackup Media Server method or the Third-Party Copy Devicemethod. An off-host data mover backup requires a configuration file (the3pc.conf file) to identify the following:

■ The client disks to back up

■ The devices on which to store the data

For a media server that has access to a large number of disks and storagedevices, a multi-stream data mover backup may take too long to create the3pc.conf file. If no 3pc.conf file exists on the media server, the firstmulti-stream backup that uses a data mover method may fail. The job statuscode is 103 (error occurred during initialization, check configuration file).To avoid this problem, create the 3pc.conf file manually before running thefirst multi-stream data mover backup. Use the following command to createthe 3pc.conf file:/usr/openv/netbackup/bin/bptpcinfo

The 3pc.conf file is created at /usr/openv/volmgr/database/3pc.conf.

For more information on the 3pc.conf file and how to create it, refer to"Configuring NetBackup for off-host data mover backups" in the NetBackupSnapshot Client Configuration document:http://entsupport.symantec.com/docs/288300

Creating space-optimized snapshotsA cache object that is called NBU_CACHE must be created in the disk groupcontaining the volume to be backed up. NetBackup recognizes the cache objectand uses it to create a space-optimized snapshot.

You can use the Snapshot Policy Configuration wizard for these steps when youcreate a new policy.

Operational Notes and IssuesAbout NetBackup Snapshot Client issues

54


To create space-optimized snapshots

1 Create the parent volume:

/usr/sbin/vxassist -g disk_group make volume-name size

layout=layout logtype=dco dcoversion=20 [drl=no|sequential|yes]

[ndcomirror=number] fastresync=on

2 Create the cache object:

/usr/sbin/vxassist -g disk_group make cache_volume size

layout=layout init=active

3 Label the cache object:

/usr/sbin/vxmake -g disk_group cache NBU_CACHE

cachevolname=cache_volume

4 Enable the cache object:

/usr/sbin/vxcache -g disk_group start NBU_CACHE

5 Take the initial snapshot:

/usr/sbin/vxsnap -g disk_group make

source=volume-name/newvol=snapvol-name/cache=NBU_CACHE

About NetBackup Hyper-V issuesThe following items describe known issues or changes to the NetBackupHyper-Vfeature for this release:

■ Use of a volume GUID path requires NetBackup patch 7.0.1 or laterNetBackup forHyper-Vhas aknownproblemthat involves volumeGUIDpaths.The following is an example of a volume GUID path:\\?\Volume{26a21bda-a627-11d7-9931-806e6f6e6963}\

If volume GUID paths exist in your Hyper-V environment, you must installNetBackup patch 7.0.1 or a later release. Contact Symantec Technical Supportto obtain the patch once it is formally released.

About NetBackup NDMP issuesNDMPRestore failswith the errormessage, ERROR: <n> leftover full buffers.

55Operational Notes and IssuesAbout NetBackup Hyper-V issues

This problem is a problem that is time sensitive and occurs intermittently. If youreceive this error, you should run the restore job again to receive a successful jobcompletion. Or, to ensure that the restore is successful, you can disable DAR andrun the job again. Be aware that if you disable DAR the restore can take a muchlonger time to complete.

About NetBackup OpsCenter issuesThe following items describe known issues or changes to the SymantecOpsCenterfeature for this release:

■ (ET1928415) The OpsCenter installer lets you install the OpsCenter server ona non-default location. When you specify a non-default location like /usr forthe OpsCenter server on an HP-Itanium system (64-bit), the OpsCenter serveris not installed in /usr. The OpsCenter server gets installed in the defaultlocation (/opt).

■ (ET2012675) When you add a master server to a node (n1) using the ViewAutomation option in the Java View Builder console, all newly added clientsare added to the respective viewat a child level of the correspondingnode (n1).You canaddamaster serverusing theViewAutomationoption in the followingmanner:In the JavaViewBuilder console, in theViews pane, right-click a node or objectand click View Automation > Add/Remove Master Server. On thePropertiesdialog box, select master servers from the AllMasterServers list,click >> and then click OK. The view automation is run on the selected masterservers. And all newly added clients are added at a child level of thecorresponding node (n1).

■ (ET2007702) The Week at a glance report does not display graphics when itis emailed or exported in an HTML format.

■ (ET2081666) The objectmerger utility in OpsCenter (to access select, Settings> Configuration> Object merger) does not work (fails) for a master server,media server, or client.

■ (ET2019291) After the installation of OpsCenter completes, the log level is setto a default value. To increase the log level, edit the/opt/SYMCOpsCenterServer/config/log.conf file and adjust the logginglevel to the required value. Then, restart the OpsCenter Services.

■ (ET2006776 ) If installing OpsCenter on AIX 6.1, ensure that you install theapplicable patch for AIX from the IBM Web site:http://www-01.ibm.com/support/docview.wss?uid=isg1fixinfo105097

Operational Notes and IssuesAbout NetBackup OpsCenter issues

56

■ (ET2039870) When you create or edit a report and the Report On parameteris not unique, the reportmay display incorrect data. Consider a scenariowhenyou create a custom report and select the Report On parameter as ScheduleName. In case there are multiple policies using the same schedule name (likes1), then the report displays incorrect data. Similarly if you select the ReportOn parameter as Policy Name and there aremultiplemaster servers that havethe same policy name, then the report displays incorrect data.The workaround for this issue is to ensure that the Report On parameter thatyou select is unique. For example, you must use a unique schedule name foreach policy. Similarly you must use a unique policy name for each masterserver. You can append the master server name to make the schedule name(s1) or policy name (p1) unique like s1_win2k8r2 or p1_win2k8r2 wherewin2k8r2 is the name of the master server.”

■ (ET2029135) Youmay receive the following error if you install NetBackup6.5.4on a system where OpsCenter 7.0.1 Server is already installed:ERROR: Failed to update PBX

■ (ET2010437) If you try to install OpsCenter 7.0.1 components on a systemwhere OpsCenter 7.0.1 is already installed, the installer displays an incorrectversion of OpsCenter on the Welcome screen. For example, the followingmessage appears on the Welcome screen when you install OpsCenter Server7.0.1 on a system where OpsCenter 7.0.1 is already installed:TheInstallationhasdetectedthatthefollowingsoftwareisalreadyinstalledon your system: Symantec OpsCenter Server: Version 7.0In this example, the installer should display Symantec OpsCenter Server7.0.1instead of version 7.0.

■ (ET2015069) When you install OpsCenter 7.0.1, you may see the followingwarning message in the installation log file:Unable to Extract VXLICENSING_HELPER_DLL with error code 1603

This error message is not applicable for 7.0.1 release update. You can safelyignore this error for OpsCenter 7.0.1.

■ (ET2012563) The Windows registry does not get updated when you run the7.0.1 installer in Maintenance mode. These registry entries are used only bythe installer and do not affect the functionality of OpsCenter. Symantecrecommends that you do not modify or delete these registry entries.

■ (ET2010465) A BMR restore can hang during a SAN boot process if a Solaris10 x64 Update 7 SRT with Emulex BIOS is enabled.

OnaSolaris 10x64 computerwith EmulexHBAcardwith booting enabled fromSAN disks, sometimes BMR Restore hangs for Solaris 10x64 Update 7 SRT.Solaris 10x64Update 7 OS installationmedia also fails to boot while SAN bootis enabled.

57Operational Notes and IssuesAbout NetBackup OpsCenter issues

To work around this issue, do the following:

■ Use Solaris 10x64 Update 8 SRT for restore.

■ Do not make the SAN disk as first bootable disk before restore. Aftersuccessful restore, enable the ability to boot from corresponding SANdisk.

■ (ET2006774) Disk names can change after a BMR restore for Solaris 10 x64clients with SATA disks (with names like c? or d?).

OnSolaris 10x64 computerswithSATAdisks, theTarget fieldmight bemissingin the disk name. (For example, the disk names appear in the format c?d?instead of the usual c?t?d? format). In this scenario, any SAN disks that wereavailable to the client after an OS installation, the disk names can change inthe restore environment. The disk name changes are handled for updatingvfstab entries. But this disk name change is not handled for other situationslike imported disk devices into Solaris local Zones.If the client computer has Solaris zoneswith imported disk devices, then aftera BMR restore, user needs to update the Solaris zone configuration manuallywith correct disk names.

■ Failures in starting BMR restore of Solaris 10x64 clients.With Solaris 10 x64 clients, sometimes the network-based BareMetal Restoredoes not start after the Prepare-To-Restore step. That occurs because theclient computer is not able to get the PXE and the DHCP response from theboot server .To resolve this issue, use command svcadm restart dhcp-server to restartthe DHCP server on the BMR boot server after the Prepare-To-Restore step.

■ (ET2010894) A DDR restore involving mapped RAID5 volume from a nameddisk set of SVM fails.This issue affects only the Solaris client that uses RAID5 volumes in SVMnamed disk sets. For such clients, if the BMR configuration is edited to mapthe RIAD 5 volumes from SAN disks to internal disks, bare metal restore failsowing to problems in creating the named disk set.If you encounter this issue, perform a system-only restore instead. You canthen restore or import the SVM-disk set manually.

■ (ET2042582) When you create or edit a report and the Report On parameteris not unique, the reportmay display incorrect data. Consider a scenariowhenyou create a custom report and select the Report On parameter as ScheduleName. In case there are multiple policies using the same schedule name (likes1), then the report displays incorrect data. Similarly if you select the ReportOn parameter as Policy Name and there aremultiplemaster servers that havethe same policy name, then the report displays incorrect data.

Operational Notes and IssuesAbout NetBackup OpsCenter issues

58

The workaround for this issue is to ensure that the Report On parameter thatyou select is unique. For example, you must use a unique schedule name foreach policy. Similarly you must use a unique policy name for each masterserver. You can append the master server name to make the schedule name(s1) or policy name (p1) unique like s1_win2k8r2 or p1_win2k8r2 wherewin2k8r2 is the name of the master server.

■ If you select Reports > Activity Planning > Job Size in the OpsCenter userinterface, the report that appears displays the wrong client name. Instead ofshowing the client names, a list of backed up VM images is displayed in thisreport. In addition, the list of VM images may not be accurate.

■ InOpsCenter, the JobCount report doesnot include the jobs thatwere collectedduring the image data collection. These jobs are called Sparse Jobs. That isunlike the JobCount report in VBR, which also included Sparse Jobs. Becauseof this change, you may notice a mismatch between the job count on theOpsCenter report and the corresponding VBR report.

About uninstalling Symantec OpsCenter 7.0 before OpsCenter 7.0.1on UNIX

If you have installed OpsCenter 7.0.1 andwant to uninstall OpsCenter completelyfrom your system, Symantec recommends that you first uninstall the OpsCenter7.0.1 release update and then OpsCenter 7.0 on UNIX. This applies to bothOpsCenter Server and OpsCenter Agent.

The following can occur if you uninstall OpsCenter Server or Agent 7.0 beforeyou uninstall the OpsCenter 7.0.1 Server or Agent respectively on UNIX:

■ The following happens if you uninstall Symantec OpsCenter Server 7.0 beforeuninstalling OpsCenter Server 7.0.1 on UNIX:

■ The installer prompts the following:

Do you want to uninstall package SYMCOpsCenterPatch701 from <host_name> which is dependent on package

SYMCOpsCenterServer? [y,n,q,?] (n)

The default option is (n)here. Youmust typey to uninstall OpsCenter 7.0.1before 7.0.Note: In case youhave entered (n) for this prompt and uninstall OpsCenterServer 7.0, OpsCenter Server 7.0 gets uninstalled leaving dependent 7.0.1package entries. These package entries must be manually removed fromthe system if you want to reinstall OpsCenter Server 7.0.1.

■ The installermayprompt about anyother dependent packages if applicable.You can select the default option (n) for any additional prompts. Forexample, you may see the following prompt:

59Operational Notes and IssuesAbout NetBackup OpsCenter issues

Do you want to uninstall package VRTSOpsCenterLegacyAgent from <host_name> which is dependent on package

VRTSpbx? [y,n,q,?] (n)

You can type (n) and proceed.

■ Remove the OpsCenterServerPatch directory. The OpsCenterServerPatchdirectory is located in /var/symantec.

Consult your operating system documentation for the appropriatecommands.

About NetBackup Vault issuesThe following list contains the issues that have been identified with the Vaultfeature:

■ (ET2016112) Cluster Support Issue for NetBackup Vault with a fresh created7.0 (not upgraded) clustered UNIX NetBackup master server .TheNetBackup7.0 installation and cluster configuration on themaster serverfails to enable cluster support for NetBackup Vault. This leads to thevault-sessions directory that is created on the local disk of the active node ofthe NetBackup cluster resource group. If the master server fails over, thatcould cause the sessions directory to be created on the cluster nodes.With the7.0.1 patch installer, the NetBackup Vault would be made cluster aware.Please refer to the following Technote on the Symantec Support Web site formore information:http://entsupport.symantec.com/docs/349907

■ Table B-1 on page 260 of the Symantec NetBackup Vault 7.0 Administrator'sGuide states that the eject.list file resides at the following location:

vault/sessions/vault_name/sidxxx/logs/eject.list

This location is not correct. The eject.list file resides at the following location:vault/sessions/<vault_name>/sidXXX/eject.list

About NetBackup VMware issuesThe following items describe known issues or changes to the NetBackup VMwarefeature for this release:

■ NetBackup will discontinue support for VMware Consolidated Backup (VCB)in a future NetBackup release. Symantec strongly recommends the use ofVMware vStorage APIs for data protection as soon as possible. The minimumrequirements for vStorage APIs are:

■ NetBackup 7

Operational Notes and IssuesAbout NetBackup Vault issues

60

■ VMware ESX 3.5 or vCenter 2.5

■ (ET2109450) Because of an issue that was identified in the VMware supportrequest 1557258751, NetBackup 7.0.1 does not support hotadd backup, orhotadd restore of virtual machines on ESX (or ESXi) servers at version 4.1.The NetBackup job details log may contain a message that is similar to thefollowing:

Backup failed with "Error bpbrm(pid=3484) from client Target_WindowsVM: ERR -

Error opening the snapshot disks using given transport mode: Status 23."

■ (ET2065639) Backups of aWindowsServer 2008 virtualmachine (32- or 64-bit)fail if the VMware tools 4.1 VSS provider is installed on the virtual machineand the following are true:

■ The Virtual machine backup option is set to Mapped full VM backup inthe NetBackup policy..

■ The Virtual machine quiesce option is enabled in the NetBackup policy.

■ The virtual machine is turned on .

See the following Symantec Technote for more details on this issue:http://support.veritas.com/docs/356729

■ (ET2085420) NetBackup VCB backup of a virtual machine may fail (withNetBackup status 156) if both of the following are true:

■ TheNetBackuppolicy is configured touse "VMdisplayname" for the "Clientname selection" type.

■ The virtual machine display name contains one or more spaces.

As a workaround, do either of the following:

■ On the policy's Snapshot Client Options screen, change the Client nameselection type to VM hostname or to VM UUID.

■ Delete the virtual machine display name from the Clients tab.

■ On the Clients tab, click New.

■ On the Browse forVirtualMachines screen, browse and select the virtualmachine.

■ Rerun the backup.

Or, you can do the following:

■ Remove the spaces from the virtual machine display name.

■ Delete the virtual machine display name from the NetBackup policy'sClients tab.

61Operational Notes and IssuesAbout NetBackup VMware issues

http://support.veritas.com/docs/356729

■ On the Clients tab, click New.

■ On the Browse forVirtualMachines screen, browse and select the virtualmachine by its corrected display name.

■ Rerun the backup.

■ NetBackup VCB-based, file-level backups of the virtual machines that useWindows 2008 R2 or Windows7 may fail.

Due to an error identified by VMware, NetBackup VCB file–level backups mayfail in the following case:

■ The guest OS on the virtual machine is Windows 2008 R2 or Windows 7.

■ The guest OS is not installed on the virtual machine’s first, virtual harddisk.

■ TheNetBackup Virtualmachine backup option is File level snapshot usingVCB or Full backup with file level incremental.

The backup job fails with status is 156 (snapshot creation failed), and thefollowing error may appear in the NetBackup bpfis log:

[vcbMounter 636 error] Error: Cannot query guest OS information.

The mount directory path is invalid.

For more details on this issue from the VMware perspective, refer to thefollowing VMware VCB documentation:http://www.vmware.com/support/vsphere4/doc/vsp_vcb_15_u1_rel_notes.html

http://www.vmware.com/support/vsphere4/doc/vsp_vcb_15_u2_rel_notes.html

■ (ET2086328) Sparse files that have no data are restored as zero-length files.NetBackup backs up sparse files even if they contain no data. (A sparse fileuses metadata to represent the empty space that is allocated to the file.)Note, that from a FlashBackup-Windows backup, a sparse file that containedno data is restored as zero length (0 KB). That occurs even if the original filehad a large amount of empty space that is allocated to it.

■ NetBackup for VMware supports vSphere 4.1 but not the NBDSSL transfertypeNetBackup 7.0.1 provides full support for VMware vSphere 4.1, with theexception of the NBDSSL transfer type. The NBDSSL transfer type requiresthe VMwareVDDK1.2 API, which is not expected to be available until the nextrelease of NetBackup.

Note: You can select NBDSSL as the transfer type in the NetBackup 7.0.1graphical interfaces. However, support for NBDSSL varies, as follows:

■ Backup of a virtual machine that is earlier than VMware 4.1 is supportedwith the NBDSSL transfer type.

Operational Notes and IssuesAbout NetBackup VMware issues

62

■ Backup of a 4.1 or later virtual machine is not supported with the NBDSSLtransfer type (the backup fails).

■ Restore of a virtualmachine (any VMware level) with the NBDSSL transfertype is not supported (the restore fails).

■ (ET2086323)Virtualmachine restoremay fail if thedatastore is locally attachedand the transfer type is Try all types.Avirtualmachine restoremay fail if theVMwaredatastore is onaSCSI attacheddisk and Try all types is the transfer type. Since the VMware datastore is notavailable through a SAN, NetBackup should select the nbd transfer type. Dueto an issue that was identified by VMware SR 1512877431, the SAN transfertype is selected instead of nbd. The restore fails because a SAN connection tothe datastore (Fibre Channel or iSCSI) is not available.To work around this issue, select nbd or nbdssl as the transfer type and retrythe restore.

■ (ET2086314) NetBackup may not be able to restore a virtual machine directlyto an ESX server if a vCenter server manages the ESX server.NetBackup can restore aVMwarevirtualmachine to avCenter server or directlyto an ESX server. Restoring directly to an ESX server can provide additionaldata protection by limiting restore (write) access to a single ESX server ratherthan granting NetBackup write access to vCenter servers.In NetBackup 7.0.1, a restore directly to an ESX server may fail if a vCenterserver manages the ESX server and the vCenter server is up at the time of therestore.You can either direct the restore to the vCenter server, retry the restore to theESX server when the vCenter server is down, or designate a VMware restoreESX server. If NetBackup has credentials to access a vCenter server as well asa VMware restore ESX server, NetBackup automatically passes the virtualmachine data directly to the restore ESX. Formore information on designatinga restore ESX server, see "Adding NetBackup credentials for VMware" in theNetBackup for VMware Administrator's Guide.

■ (ET2086309) Restore of VMware virtual machine continues even if the wrongtransfer type was selected for the restore.You can select from several transfer types when you restore a VMware virtualmachine. The available types areSAN,nbd,nbdssl,TrySAN thennbd,hotadd,and Try all types. These types are described in the NetBackup for VMwareAdministrator's Guide. If you select a transfer type that is not appropriate toyour network and VMware configuration, the restore job cannot succeed.In certain cases, the restore job remains active in the NetBackup ActivityMonitor even if the wrong transfer type was selected for the restore. Therestore job attempts to read data from the backup for several minutes but


eventually fails with NetBackup status 5. The job's detailed status log maycontain the message, VxMS initialization failed.

In a future NetBackup release, NetBackup determines if VxMS cannot beinitialized. If VxMS cannot be initialized, NetBackup promptly fails the restoreat that time.For the restore of virtual machines or restore of data on physical hosts, thesame VxMS initialization failure can occur if the VxMS libraries are notcorrectly installed.

■ (ET2029982)Virtualmachine restore to an internal datastore fails if the virtualmachinehas thinprovisioneddisks orCreatethinprovisioneddisks is selected

When you attempt to restore a VMware virtual machine, the restore job failsin the following case:

■ Either Trysanthennbd or Tryall types is selected as the transfer type forthe restore

■ The virtual machine that you want to restore has a thin-provisioned diskor you selectCreatethinprovisioneddiskson theRecoveryOptionsdialog

■ The target datastore is on a directly attached device (not on a networkeddevice, SAN device, or iSCSI device).

In this case, the restore job fails with NetBackup status code 5. The DetailedStatus tab contains the message Virtual machine restore: file write failed.To restore the virtual machine, select nbd or nbdssl as the transfer type onthe Recovery Options dialog in the NetBackup Backup, Archive, and Restoreinterface.VMwarehas identified the cause of this problem in its virtual diskDevelopmentKit (VDDK), as SR# 1512877431.

■ For VMware environments earlier than vSphere 4.1, VMware has published aknowledge base article titled "Reverting to a pre-existing snapshot can causeincremental backupsbasedonChangedBlockTracking tobecome inconsistent."Please refer to the VMware article for more details:http://kb.vmware.com/selfservice/documentLink.do?externalID=1021607

Please also refer to the following Symantec Tech Alert:http://support.veritas.com/docs/355390

When using NetBackup to do incremental backups of virtual machines withthe Changed Block Tracking (CBT) feature, you should set the NetBackupExistingsnapshothandlingparameter toAbort. This setting causesNetBackupto stop the backup (with NetBackup status 156) if a snapshot already exists onthe virtual machine. In the case of a pre-existing snapshot and CBT, the Abortsetting prevents NetBackup from making a backup that may containinconsistent data. The data is inconsistent if an incremental backup hadoccurred using CBT, followed by a manual revert to an earlier snapshot of the


64

virtual machine. As a result of the manual revert to an earlier snapshot, asubsequent incremental backup using CBT might contain inconsistent data.In this case, if a manual revert to an earlier snapshot occurred, you should doa full backup of the virtual machine. After a full backup, you can re-initiateincrementals and CBT. The incrementals capture consistent data as long asanother revert to an earlier snapshot does not take place.

■ (ET1944704) A change was made to remove the RenameTimeout fromNetBackup. However, changes to the ConnectionTimeout have beenmoved tothe next release of NetBackup.

■ VMware SR 1535169351 (This issue applies only to ESX 4.0.)If Changed block tracking (CBT) is enabled for the virtual machine, but theESX server or the vmware-vmx process terminates abnormally after CBT isenabled, subsequent virtual machine backups may not back up all the data onthevirtualmachine.Thebackup jobsmayreportnormal completion (NetBackupstatus 0), but the backup image may not contain all the virtual machine data.According to VMware, this issue has been fixed in VMware 4.0u1.As a workaround for VMware 4.0, you should disable and then turn on CBT onall virtual machines after any abnormal ESX or vmware-vmx termination.

■ VMware SR 1512877431

For virtual machine restores that use the Try san then nbd or Try all typestransfer type, the restore job fails with NetBackup status 5 in the followingcase:

■ If the virtual machine has thin provisioned disks, or if Create thinprovisioned disks is selected on the Recovery Options dialog

■ The restore target is a datastore that is locally attached to the ESX server.

As a workaround, select nbd or hotadd as the transfer type for the restore.Note that the hotadd type requires a restore host that is installed in a virtualmachine.



66

End of Life Notifications


■ About End-of-life notifications for 7.0.1

About End-of-life notifications for 7.0.1This topic contains the end-of-life notifications for verious products and featuresof NetBackup. It may also contain detailed information about when support fora platform has occurred.

■ NetBackup will discontinue support for VMware Consolidated Backup (VCB)in a future NetBackup release. Symantec strongly recommends the use ofVMware vStorage APIs for data protection as soon as possible. The minimumrequirements for vStorage APIs are:

■ NetBackup 7

■ VMware ESX 3.5 or vCenter 2.5

5Chapter

End of Life NotificationsAbout End-of-life notifications for 7.0.1

68

About the current releasecontent index

This appendix includes the following topics:

■ About the NetBackup7.0.1 master Etrack index list

About the NetBackup7.0.1 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_JAV_7.0.11893209 1896288 1983685

NB_CLT_7.0.1126185214248351433934146731614673321467509147260215316331533729207404717823491786798178873618314931831735184154118426751842980184315818485521854250185718518607711861583186207618631901863456186485518691631870159187093818745411879025187984018803341881464188359118846631885207188652018865981888009188817318893431890881189348418965361896544189787418980261902039190237019023781902807190419919054551905891190648219069871907096190981019099291910617191096119122971912640191300519137971914097191489119161231916291191660219167281917457191871419196181922399192241719227511922975192308119230911923210192822819285931928894192982219302361930356193130019322481932283193262719331841933320193368419338981934168193428019346511934652193514519352771935641193623219363331936335193677019370961937102193732719382501938307193831019383341938405

AAppendix

1939224193949119411481942127194286219430171943191194400219440571944776194547719469111947642194778519500381950351195065619509511950960195100719527301953018195310919557681955900195742119579151958530195865919587211959541195990419604041960678196122819618041962159196834219684871968912196892419714821971794197200519726301974185197418919758421976914197694119771611977200197803819781231979866198029319810841981856198193219827701983127198314019842451986178198714419874311987502198780519893321990026199127719918301991862199227119937331995314199568019957661996766199687919970151997026199713019974791997721199798019980651998448199868219987241998953199961819996502000855200116420016992001845200234820024042002971200306520042582004567200525420053162006955200761720085332008988200965720097642009925201158620117812012746201278520128842013015201364320142522014319201611220168472016926202057820206142021015202387820246162025757202597020266542030144203015620302022030470203063720313572034304203456920354002035567203663920367672037864203850320385952039278204018820416882042708204290420436162044016204508620454372047038204808120487492050104205046720506452050657205092420523102053888205477920558302055875205684720585762059508206027720603852060490206152420616132062690206288720630642064082 2069326 2069773 2069946

NB_7.0.1.winnt.IA64105360012618521424835143393414363941467316146733214675091531633153372920739121728851178234917867981802865182130318317351841541184267518429801843158184855218542501857185186077118609571861583186207618622081863190186345618647761864855186916318701591870455187093818728851874541187902518798401880334188146418835911884465188466318852071886520188659818880091888173188934318905281890641189088118933101893484189653618965441897874190203919023701902378190372619041991905455190568219064821906987190709619092071909517190959019098101909929191061719109611912297191264019130051913797191409719148911916123191672819174571918714191881719196181922399192241719227511922975192308119232101924088192525819253051925306192530719263821926419192822819285931928894192941819294851929822193013019302361930356193130019322481932283193318419333201933684193416819342801934316193465119346521935133193514519352771935619193564119359561936232193634319367701937092193709619371021937327193825019383071938310193833419384051939154193922419394911941148194124819412571941905194212719423661942862194301719436041944002194405719447041944768194477619454771946121194691119476011947642194770519477081947785194971519500381950045195035119506561950834

About the current release content indexAbout the NetBackup7.0.1 master Etrack index list

70

1950951195096019510071952195195273019530181953109195576819559001956563195742119579151958530195865919587211959541195990419604041960678196122819618041961824196598819683421968912196892419707951971482197179419720051974189197584219764971976914197694119769911977047197716119772001978038197812319781511979037197986619799471980293198051919810841981932198277019839151983952198424519844531985849198590219861781987144198729219875021987593198838619884731989106198933219893811989554199002619906681990797199127719918301991862199191019922711992311199291519931061993411199357319937331995314199576619967661996879199698519970151997026199713019974791998065199844819986821998724199895319996181999650199971320007262000855200095220011642001300200169920018452002348200240420029712003065200425820044212004567200525420053162005830200695520069882007062200761720081532008988200965720096972009764200992520100432011041201158620117812012746201278520128842013015201364320140532014120201424620142522014319201537220168472016860201692620177332020578202061420210152021455202387820246162024679202597020266542029204202930520301442030339203063720313572032891203342420343042034569203540020354482035567203586720358872035929203663920367672037864203850320385522038595203883720392782040188204146520416882042708204287220429042043616204401620446052044695204543720468842046917204703820480812048678204870820487112048749205010420504672050491205065720509242052310205264120535862053888205477920558302055875205684720570492058576205950820602772060385206049020606102061407206152420616132062690206288720636692064082206784220683352069326 2069773 2069946 2073853

NBLU_7.0.1.WIN105360012618521424835143393414363941467316146733214675091531633153372920739121728851178234917867981802865182130318317351841541184267518429801843158184855218542501857185186077118609571861583186207618622081863190186345618647761864855186916318701591870455187093818728851874541187902518798401880334188146418835911884465188466318852071886520188659818880091888173188934318905281890641189088118932091893310189348418962881896536189654418978741899394190203919023701902378190372619041991905455190568219064821906987190709619092071909517190959019098101909929191061719109611911065191229719126401913005191379719140971914891191492519161231916728191745719187141918817191961819220951922399192241719227511922975192308119232101924088192428119252581925305192530619253071926382192641919282281928593192889419294181929485192982219301301930236193035619305361931300193224819322831933184193332019336841934168

71About the current release content indexAbout the NetBackup7.0.1 master Etrack index list

1934280193431619346511934652193513319351451935277193548519356191935641193595619362321936343193677019370921937096193710219373271938250193830719383101938334193840519391541939224193949119411481941248194125719419051942127194236619428621943017194360419440021944057194470419447681944776194547719461211946911194760119476421947705194770819477851949715195003819500451950351195065619508341950951195096019510071952195195273019530181953109195576819559001956563195724719574211957518195791519585301958562195865919587211958962195954119599041960404196067819612281961804196182419659881968342196891219689241968972197079519714821971794197200519741891975842197649719769141976941197699119770471977161197720019780381978123197815119790371979866197994719802931980519198108419819321982770198368519839151983952198424519844531985849198590219861781987144198729219875021987593198838619884731989106198933219893811989554199002619906681990797199127719918301991862199191019922711992311199291519931061993411199357319937331995314199576619967661996879199698519970151997026199713019974791998065199844819986821998724199894819989531999618199965019997132000649200066020007262000855200095220011642001300200169920018452002348200240420028182002971200306520042582004367200442120045672005254200531620058302006264200695520069882007062200761720077022008151200815320083102008410200898820090732009595200965720096972009733200976420099252010043201071020110412011586201178120127462012785201288420130152013643201405320141202014246201425220143192015339201537220168472016860201692620174002017733202019920204042020461202057820206142020884202101520212912021331202145520215352022289202235720231762023350202387820244462024616202467920256002025970202665420292042029305203014420303392030637203135720320822032891203342420343042034367203456920354002035448203556720356602035867203588720359292036639203676720376712037864203850320385522038595203883720392782040037204018820410722041082204146520416882042708204287220429042043616204401620446052044695204543720468842046917204702420470382047884204808120486782048708204871120487492050104205034320504672050491205065720509242052310205264120535862053888205477920558302055875205684720570492057426205857620595082060277206038520604902060610206140720615242061613206269020628872063669206408220678422068335 2069299 2069326 2069773 2069946 2073853

NB_OPS_CTR_7.0.1.winnt.x64189939419110651914925192209519242811930536193548519572471957518195856219589621968972199894820006492000660200281820043672006264200770220081512008310200841020090732009595200973320107102015339


72

2017400202019920204042020461202088420212912021331202153520222892022357202317620233502024446202560020320822034367203566020376712040037 2041072 2041082 2047024 2047884 2050343 2057426 2069299

NB_7.0.11261852142483514339341467316146733214675091531633153372920740471782349178679817887361831493183173518415411842675184315818571851860771186158318620761863190186345618648551869163187015918709381874541187902518798401880334188359118846631885207188652018865981888009188817318893431890881189348418965361896544189802619020391902370190237819028071904199190545519064821906987190709619098101909929191096119122971912640191300519140971914891191612319162911916728191745719187141919618192239919224171922751192297519230811923210192822819285931928894193023619303561931300193224819331841933320193368419338981934168193428019346511934652193514519352771935641193633319363351936770193732719382501938310193833419384051939224193949119411481942127194301719431911944776194547719469111947642194778519500381950351195095119527301953018195576819559001957421195865919587211959541195990419604041960678196122819683421968912196892419714821971794197200519726301974189197584219769141976941197716119772001978038197812319798661980293198108419818561981932198277019831271983140198424519861781987144198750219893321990026199127719918301991862199227119937331995314199568019957661996766199687919970261997130199747919977211998065199844819986821998724199895319996181999650200085520011642001699200184520023482002404200297120030652004258200456720052542005316200695520076172008988200965720097642009925201158620117812012746201278520128842013015201364320142522014319201611220168472016926202057820206142024616202575720259702026654203014420302022030637203135720343042034569203540020355672036639203676720378642038503203859520401882041688204270820429042043616204401620450862045437204703820480812048749205010420504672050645205065720509242052310205388820547792055830205587520585762059508206027720603852060490206152420616132062690 2063064 2064082 2069326 2069773 2069946

NBLU_7.0.1.UNIX126185214248351433934146731614673321467509147260215316331533729207404717823491786798178873618314931831735184154118426751842980184315818485521854250185718518607711861583186207618631901863456186485518691631870159187093818745411879025187984018803341881464188359118846631885207188652018865981888009188817318893431890881


1893209189348418962881896536189654418978741898026189939419020391902370190237819028071904199190545519058911906482190698719070961909810190992919106171910961191106519122971912640191300519137971914097191489119149251916123191629119166021916728191745719187141919618192209519223991922417192275119229751923081192309119232101924281192822819285931928894192982219302361930356193053619313001932248193228319326271933184193332019336841933898193416819342801934651193465219351451935277193548519356411936232193633319363351936770193709219370961937102193732719382501938307193831019383341938405193922419394911941148194212719428621943017194319119440021944057194477619454771946911194764219477851950038195035119506561950951195096019510071952730195301819531091955768195590019572471957421195751819579151958530195856219586591958721195896219595411959904196040419606781961228196180419621591968342196848719689121968924196897219714821971794197200519726301974185197418919758421976914197694119771611977200197803819781231979866198029319810841981856198193219827701983127198314019836851984245198617819871441987431198750219878051989332199002619912771991830199186219922711993733199531419956801995766199676619968791997015199702619971301997479199772119979801998065199844819986821998724199894819989531999618199965020006492000660200085520011642001699200184520023482002404200281820029712003065200425820043672004567200525420053162006264200695520076172007702200815120083102008410200853320089882009073200959520096572009733200976420099252010710201158620117812012746201278520128842013015201364320142522014319201533920161122016847201692620174002020199202040420205782020614202088420210152021291202133120215352022289202235720231762023350202387820244462024616202560020257572025970202665420301442030156203020220304702030637203135720320822034304203436720345692035400203556720356602036639203676720376712037864203850320385952039278204003720401882041072204108220416882042708204290420436162044016204508620454372047024204703820478842048081204874920501042050343205046720506452050657205092420523102053888205477920558302055875205684720574262058576205950820602772060385206049020615242061613206269020628872063064 2064082 2069299 2069326 2069773 2069946

NB_OPS_CTR_7.0.1.winnt.IA64189939419110651914925192209519242811930536193548519572471957518195856219589621968972199894820006492000660200281820043672006264200770220081512008310200841020090732009595200973320107102015339201740020201992020404202046120208842021291202133120215352022289


74

2022357202317620233502024446202560020320822034367203566020376712040037 2041072 2041082 2047024 2047884 2050343 2057426 2069299

NB_JAV_7.0.1.winnt.IA641893209 1896288 1983685

NB_DRO_7.0.11937092

NB_JAV_7.0.1.winnt.x641893209 1896288 1983685

NB_7.0.1.winnt.x86105360012618521424835143393414363941467316146733214675091531633153372920739121728851178234917867981802865182130318317351841541184267518429801843158184855218542501857185186077118609571861583186207618622081863190186345618647761864855186916318701591870455187093818728851874541187902518798401880334188146418835911884465188466318852071886520188659818880091888173188934318905281890641189088118933101893484189653618965441897874190203919023701902378190372619041991905455190568219064821906987190709619092071909517190959019098101909929191061719109611912297191264019130051913797191409719148911916123191672819174571918714191881719196181922399192241719227511922975192308119232101924088192525819253051925306192530719263821926419192822819285931928894192941819294851929822193013019302361930356193130019322481932283193318419333201933684193416819342801934316193465119346521935133193514519352771935619193564119359561936232193634319367701937092193709619371021937327193825019383071938310193833419384051939154193922419394911941148194124819412571941905194212719423661942862194301719436041944002194405719447041944768194477619454771946121194691119476011947642194770519477081947785194971519500381950045195035119506561950834195095119509601951007195219519527301953018195310919557681955900195656319574211957915195853019586591958721195954119599041960404196067819612281961804196182419659881968342196891219689241970795197148219717941972005197418919758421976497197691419769411976991197704719771611977200197803819781231978151197903719798661979947198029319805191981084198193219827701983915198395219842451984453198584919859021986178198714419872921987502198759319883861988473


1989106198933219893811989554199002619906681990797199127719918301991862199191019922711992311199291519931061993411199357319937331995314199576619967661996879199698519970151997026199713019974791998065199844819986821998724199895319996181999650199971320007262000855200095220011642001300200169920018452002348200240420029712003065200425820044212004567200525420053162005830200695520069882007062200761720081532008988200965720096972009764200992520100432011041201158620117812012746201278520128842013015201364320140532014120201424620142522014319201537220168472016860201692620177332020578202061420210152021455202387820246162024679202597020266542029204202930520301442030339203063720313572032891203342420343042034569203540020354482035567203586720358872035929203663920367672037864203850320385522038595203883720392782040188204146520416882042708204287220429042043616204401620446052044695204543720468842046917204703820480812048678204870820487112048749205010420504672050491205065720509242052310205264120535862053888205477920558302055875205684720570492058576205950820602772060385206049020606102061407206152420616132062690206288720636692064082206784220683352069326 2069773 2069946 2073853

NB_7.0.1.winnt.x64105360012618521424835143393414363941467316146733214675091531633153372920739121728851178234917867981802865182130318317351841541184267518429801843158184855218542501857185186077118609571861583186207618622081863190186345618647761864855186916318701591870455187093818728851874541187902518798401880334188146418835911884465188466318852071886520188659818880091888173188934318905281890641189088118933101893484189653618965441897874190203919023701902378190372619041991905455190568219064821906987190709619092071909517190959019098101909929191061719109611912297191264019130051913797191409719148911916123191672819174571918714191881719196181922399192241719227511922975192308119232101924088192525819253051925306192530719263821926419192822819285931928894192941819294851929822193013019302361930356193130019322481932283193318419333201933684193416819342801934316193465119346521935133193514519352771935619193564119359561936232193634319367701937092193709619371021937327193825019383071938310193833419384051939154193922419394911941148194124819412571941905194212719423661942862194301719436041944002194405719447041944768194477619454771946121194691119476011947642194770519477081947785194971519500381950045195035119506561950834195095119509601951007195219519527301953018195310919557681955900195656319574211957915195853019586591958721195954119599041960404


76

1960678196122819618041961824196598819683421968912196892419707951971482197179419720051974189197584219764971976914197694119769911977047197716119772001978038197812319781511979037197986619799471980293198051919810841981932198277019839151983952198424519844531985849198590219861781987144198729219875021987593198838619884731989106198933219893811989554199002619906681990797199127719918301991862199191019922711992311199291519931061993411199357319937331995314199576619967661996879199698519970151997026199713019974791998065199844819986821998724199895319996181999650199971320007262000855200095220011642001300200169920018452002348200240420029712003065200425820044212004567200525420053162005830200695520069882007062200761720081532008988200965720096972009764200992520100432011041201158620117812012746201278520128842013015201364320140532014120201424620142522014319201537220168472016860201692620177332020578202061420210152021455202387820246162024679202597020266542029204202930520301442030339203063720313572032891203342420343042034569203540020354482035567203586720358872035929203663920367672037864203850320385522038595203883720392782040188204146520416882042708204287220429042043616204401620446052044695204543720468842046917204703820480812048678204870820487112048749205010420504672050491205065720509242052310205264120535862053888205477920558302055875205684720570492058576205950820602772060385206049020606102061407206152420616132062690206288720636692064082206784220683352069326 2069773 2069946 2073853

NB_OPS_CTR_7.0.11899394191106519149251922095192428119305361935485195724719575181958562195896219689721998948200064920006602002818200436720062642007702200815120083102008410200907320095952009733201071020153392017400202019920204042020884202129120213312021535202228920223572023176202335020244462025600203208220343672035660203767120400372041072 2041082 2047024 2047884 2050343 2057426 2069299

NB_OPS_CTR_7.0.1.winnt.x861899394191106519149251922095192428119305361935485195724719575181958562195896219689721998948200064920006602002818200436720062642007702200815120083102008410200907320095952009733201071020153392017400202019920204042020461202088420212912021331202153520222892022357202317620233502024446202560020320822034367203566020376712040037 2041072 2041082 2047024 2047884 2050343 2057426 2069299


NB_JAV_7.0.1.winnt.x861893209 1896288 1983685


78

About the current releasecontent

This appendix includes the following topics:

■ About release content conventions

■ About the current release content

About release content conventionsThis topic contains theNetBackup7.0.1 conventions and content that is applicableto this release.

The following list describes the conventions used in the subsections that followthis section. Each item listed in the "Current release content" subsection describesa feature, enhancement, or fixed issue contained in this release:

■ DescriptionDescribes a particular problem that has been fixed in this release.

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

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

■ Additional NotesAny additional information regarding a problem is included.

BAppendix

About the current release contentThis topic contains a list of the enhancements and the known issues that wereadded or fixed in this release of NetBackup. A workaround has been supplied forsome known issues. In other cases, the issues were fixed and no workaround isnecessary.

Etrack Incident: 1841541

■ Associated Primary Etrack: 1838371

■ TITAN cases: 281-536-554

■ Contained in:NBLU_7.0.1.UNIXNBLU_7.0.1.WINNB_7.0.1NB_7.0.1.winnt.IA64NB_7.0.1.winnt.x64 NB_7.0.1.winnt.x86 NB_CLT_7.0.1

■ Description:The Synthetic backups failed if two media servers have identical paths forBasicDisk or NearStore.



■ Description:The nbdna script analyzes the NetBackup domain and its configuration fornetwork issues, performance, and behavior. It addresses thehost name look-upand the connectivity between the NetBackup hosts and their roles within theNetBackup domain.

■ Additional Notes:You can run nbdna to help diagnose network problems within a NetBackupenvironment.



■ TITAN cases: 410-639-922


■ Description:The 5 second wait in the bptm child process at the end of a restore (when theclient is not the media server) or duplication (when the read and write mediaservers are not on the same host, or when preservemultiplexing is specified)is removed as it is no longer necessary. That occurred on Linux or Windowsmedia servers.

About the current release contentAbout the current release content

80

■ Work around:For Linuxmedia servers, there is a touch file that can disable the 5 secondwait. To disable the wait, enter "0" in the following file:/usr/openv/netbackup/WAIT_TO_CLOSE


■ Contained in: NBLU_7.0.1.WIN NB_7.0.1.winnt.IA64 NB_7.0.1.winnt.x64NB_7.0.1.winnt.x86

■ Description:A change was made to address an issue that caused the following warningwhen you selected a backup for restore.Getting warning "unable to obtain list of files using specified

search criteria.



■ Description:NBSL has a common iterator implementation. This release contains a changethat moves the catalog iterator to an existing common implementation.


■ Contained in: NBLU_7.0.1.UNIX NBLU_7.0.1.WIN NB_OPS_CTR_7.0.1NB_OPS_CTR_7.0.1.winnt.IA64 NB_OPS_CTR_7.0.1.winnt.x64NB_OPS_CTR_7.0.1.winnt.x86

■ Description:The OpsCenter reports would show no data (Job Size, Schedule jobs report,and status report ) if the operating system locale was European.



■ Description:A changewasmade to ensure that the default for snapshot handling isRemoveNBU.

■ Work around:If you encounter an issue similar to that, change the settingmanually for eachcreated policy.


81About the current release contentAbout the current release content


■ Description:Exchange GRT backups would fail with a status 1 on a Windows 2008 R2Exchange server. The bkar logs would show a number of different errors, buterrors would be related to GRT activities (create_view, roll_forward, and soforth).

■ Work around:If you encounter this issue, set the following NFS registry key to 60000:\\HKLM\Software\Microsoft\ClientForNFS\CurrentVersion\Default\SoftMountTimeout.That key is set in milliseconds and 60000 is equal to 60 seconds. Then youneed to bounce the Client For NFS service. After you stop the Client For NFSservice, you may need to run the net start nfsrdr command to restart theClient For NFS service.



■ TITAN cases: 410-650-640


■ Description:Backupswith an image fragment that was larger than 2TB cannot be restored.The bptm process would end with a status 174.

media manager - system error occurred



■ Description:On the Select Destination Parameters and Pre-Clone Check dialogs, theupper-case and lower-case characters in the labels were inconsistent.



■ Description:Sorting on the master server did not work in the Policy summary dashboardreport.


82




■ Description:A change was made to address an issue that caused PEM to shut down after11 consecutive failed attempts to send an email.



■ Description:A change was made to address a Coverity issue concerning a NULL productpointer.



■ Description:A filter that was applied for one master server would show the report for allservers at job success rate by policy type (tabular) report.



■ Description:When a resource (media/drive/STU) was reported as busy during allocationfor a job, there was no easy way to tell which job(s) used it. This change is thefirst in that process. In 7.0.1, Symantec has implemented some options in thenbrbutil command-line interface. Those options enable the user to list thejobs that use a specific resource.



■ TITAN cases: 411-924-137


■ Description:


The bpdbmprocesswould core dump if the combination of a SUSELinuxmasterserver and granular restore technology were used.The stack trace in the core file looked similar to the following:#0 0x00007f1cbff31c80 in err_cmp () from /usr/openv/lib/libnbdb.so

#1 0x00007f1cbff3ed9b in lh_insert () from

/usr/openv/lib/libnbdb.so #2 0x00007f1cbff3384e in int_err_set_item

() from /usr/openv/lib/libnbdb.so #3 0x00007f1cbff33377 in

ERR_load_strings () from /usr/openv/lib/libnbdb.so #4

0x00007f1cb87bf42e in ERR_load_BN_strings () from

/usr/openv/lib/libnbmangle.so #5 0x00007f1cb8793707 in

ERR_load_crypto_strings () from /usr/openv/lib/libnbmangle.so #6

0x00007f1cb8774ec9 in SSL_load_error_strings () from

/usr/openv/lib/libnbmangle.so #7 0x00007f1cb876ff55 in mangleAccept

() from /usr/openv/lib/libnbmangle.so #8 0x00007f1cb8770305 in

mangleAcceptWSigBlock () from /usr/openv/lib/libnbmangle.so #9

0x00007f1cbe6682b7 in send_nbfsd_credentials () from

/usr/openv/lib/libnbclientST.so #10 0x00007f1cbe8c90e7 in

bpcr_get_fileinfo_rqst () from /usr/openv/lib/libVbp.so #11

0x00000000004a9ee8 in dbm_query_client () #12 0x00000000004b398f

in get_virtual_file_rec () #13 0x00000000004b3a78 in get_file_rec

() #14 0x000000000047a708 in strcmp_match_file_list () #15

0x00000000004830d1 in list_files () #16 0x0000000000496d81 in

image_db () #17 0x000000000044b06d in process_request () #18

0x000000000044c86a in listen_loop () #19 0x000000000044f4ea in

main ()



■ TITAN cases: 411-453-834


■ Description:The nbstlutil stlilist -U -image_incomplete command produces a coredump when it finds the images that contain StorageServerState "-1 in theEMM database.

■ Work around:If you encounter this issue, run nbstlutil list -U to identify the invalidimage and expire that image.



84


■ TITAN cases: 411-451-200


■ Description:The tape drives appeared to be shared on the Drive Throughput report whenthey were not shared.



■ TITAN cases: 320-219-113


■ Description:Virtual machine credentials would break if they included the stringtwo-character string, \n. For example, the following string would cause afailure, domain\netbackup.



■ Description:An Exchange off-host instant recovery snapshot only back up, with Backuponly uncommitted logs set in the Exchange options for the client completeswith a status 0.However, during the restore, the Exchange log fileswere namedincorrectly, and caused the recovery of the Exchange database to fail.

■ Work around:To avoid this problem, select the Back up all log files option in the Exchangeoptions of the NetBackup Client Properties.



■ Description:Thehyperlink for theNumberofOccurrencesunder the Jobexitstatusdetailsdid not redirect to the correct data.




■ TITAN cases: 411-341-931


■ Description:Sorting the CustomR column by the master server name, in ascending order,did not work. The rows that were returned were not sorted.



■ Description:In certain cases, NetBackup creates a volume shadow copy association with afixed size limit. That should not be done because it can cause backup failures.A change has been made to address this issue.



■ **Description:Whenyou runphase 1 import of disk images onamedia server and intermittentconnectivity issues occur with the master server, some valid disk images didnot be imported and no warning was issued.

■ Work around:After you complete an import, run the phase 1 import again.



■ Description:A change was made to address an issue that caused nbrb to core dump.

Etrack Incident: 1960404 1995766 2016926


■ Description:A change was made to upgrade NetBackup to the most recent VxUL drop.



86


■ Description:A change wasmade to the Backup > Jobactivity > Job duration so that it onlyconsiders the parent job's execution time.



■ Description:The NetBackup Resource Broker (NBRB) would take a long time to receive arequest because of the host name resolution performance in nbpem.



■ Description:The bpdbm process would crash with a segmentation fault during bpdbm

-consistency 2 if application clusters were configured.


■ TITAN cases: 281531718 411-912-343


■ Description:The bpjobd process would not perform a restore job cleanup.



■ Description:A change was made to change the Exchange directive MS_Exchange_200x toMS_Exchange_Database.



■ Description:


AVMrestore failed if the NBU_HOME\online_util\fi_cntl folder did not existon the proxy computer.

■ Work around:If you encounter this issue, create the directory and attempt the restore again.



■ TITAN cases: 410-641-645


■ Description:Non-root user backups would not send mail with the USEMAIL setting inplace.


■ Contained in: NBLU_7.0.1.UNIX NB_7.0.1 NB_CLT_7.0.1

■ Description:A changewasmade to ensure thatNetBackup can back up or restoreExtendedAttributes on a Mac OS X platform.


■ TITAN cases: 220-706-443


■ Description:The nbemmcmd -deletealias command would fail to delete the FQ host name.In addition, the error message was improved for this issue.



■ Description:The vmdk file names and Datastore list was not populated in the MFC userinterface while a full VM restore occurred.



■ Description:


88

A changewasmade to ensure that Vault is able to purge outdated entries fromvlteject.mstr file.

The bprd process would delete the vault session directories as per the cleanupinterval you specified. After the session directory is deleted vault should purgethe corresponding session entry from the vlteject.mstr file. A change wasmade to fix this issue.



■ Description:A change was made to correct an issue that would cause Snapshot backups tofail.


■ Contained in: NBLU_7.0.1.UNIX NB_CLT_7.0.1

■ Description:Added Snapshot Client support for the HP XP array.



■ Description:Problems in the evictor for CORBAobjectswould cause a process to deadlock.Changes have been added to fix these issues.



■ Description:A change was made to correct an issue that caused a phase 2 import to failwith a timeout for some images.



■ Description:A change was made to address an issue that caused delays to occur during anSLP session cancelation.




■ Description:The filter option Disk showed a value as Not Implemented in the drop-downfield of the disk usage report.



■ Description:A change was made to address Client Coverage report data issues.If a client has more than one name in OpsCenter, all of those entries werebrought into the report. This issue occurred even if the casewas different. Thefull policies were entered into the report as incremental policies.



■ TITAN cases: 320-185-872


■ Description:A change was made to address an issue that caused NBJM to fail to connect tobpjobd. That produced a status 41 error that was reported in the error logwhen NetBackup processes were started. The nbjm process continues to try toconnect but whenever it fails it logs as ERROR/CRITICAL in error logs.



■ TITAN cases: 230-694-117


■ Description:Using bpadm or vmadm to update the volume configuration of an ACS librarymay fail.

■ Work around:Use the Windows and Java user interface to update the volume configurationinstead of bpadm or vmadm.


90



■ Description:Data was not migrated and mismatched in the database after an attempt toupgrade from7.0GA to 7.0.1 patch. A changewasmade to ensure that the treegets the migrated properly.



■ TITAN cases: 281-842-282 411-451-612 411-526-602 411-934-352


■ Description:A change was made to correct an issue that caused nbpem to core dump.



■ TITAN cases: 320-233-457


■ Description:The Disk Pool Committed Space algorithm was inappropriate to determinethe space 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:


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:A change was made to address an issue that caused the policy validation tofail for a VxVM raw device path.



■ TITAN cases: 411-345-737


■ Description:The bpdbm -consistencywould stop with core dump if there was a corruptedimage.

■ Work around:Remove the corrupted image from the image database.



■ TITAN cases: 412-177-748


■ Description:Unable to retrievedatastores if youattempted toperforma restorewithRestoreESX Server.

Etrack Incident: 1992271 1938250 1987502


■ Description:A new command-line command, nbdecommission, was added. This commandguides the user through the steps involved to decommission a media server.



92


■ Description:When you add the VxVM 5.0.3.0 in SRT 5.3.11.1 on AIX6.1 TL3 boot server,the uname was executed in the chroot environment and was given the outputof the boot server OS instead of SRT OS which was incorrect.



■ Description:MultipleWindows storage servers cannot use theAdvancedDisk disk poolwitha CIFS volume.



■ TITAN cases: 281-879-105


■ Description:Browsing the Granular Backup of an active directory can take an excessiveamount of time. The release contains an improved algorithm for browsing.



■ Description:Hyper-V, virtual machine, single-file restores failed at the volume GUIDdestination path if you selected the overwrite option.

Etrack Incident: 2017733 1890528


■ Description:Enhancements were added to increase the Exchange Granular browse and theExchange Granular restore performance.



■ TITAN cases: 411-337-395



■ Description:Adding a valid report filter caused the report to hang. A change was made tocorrect this issue.



■ TITAN cases: 411-389-387


■ Description:Snapshot backups would fail with the following message in bpbkar.

tpc_handle_sparse: ERR - tpc_handle_sparse failed: err 2067



■ Description:A backup of a SharePoint server on a pre-NetBackup 7.0 client failed with aNetBackup 7.0 master or media server.


■ Contained in: NBLU_7.0.1.UNIX NBLU_7.0.1.WIN NB_7.0.1.winnt.IA64NB_7.0.1.winnt.x64 NB_7.0.1.winnt.x86 NB_CLT_7.0.1

■ Description:A changewasmade to correct an issue that caused the bpdbsbora.exeprocessto crash on Windows platforms.



■ Description:Multistreamed jobs with manual streaming would fail with status 69 error.That occurred with NEW_STREAM directives in the file list.



■ Description:


94

If you configured NBAC on media with the bpnbaz -setupmedia

<mediaserver>, or configuredNBACona clientwith the bpnbaz -setupclient

<client> command, the following error may appear.

bprd ended in an unknown state while attempting to configure NBAC

on target host

However, the configuration of client or media would complete.



■ Description:After an Exchange database was restored, the progress log showed that thedatabase had been mounted, and then it gave an error.After an Exchange database is restored, the following is captured in theprogress log:

12:41:28 (487.001) INF - Database Mailbox Database 0733393846 mountedsuccessfully.

12:41:28 (487.001) ERR - An Exchange restore error was detected. You may need to manually

mount the Database stores to successfully finish the restore.



■ TITAN cases: 281-737-803


■ Description:Oracle Snapshot Client backupswould fail with an exceptionmessage thatwasnot handled.



■ Description:During a Windows open file backup, if the shadow storage was found asunbounded then NetBackup changed it to a value between 300-1024MB. Thisvaluewas 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: 410-595-967


■ Description:During duplication, the job may fail when it requests subsequent resources.The Activity Monitor displays a message that is similar to the following.status 96, bptm read; bpduplicate status 50; from mds allocateMedia

rc=2005000



■ Description:The restore of an Exchange 2010 database from a stand-alone server to a DAGenvironment may restore to an incorrect server and fail.



■ Description:On a Windows platform, bpfis would crash if the application verifier was onduring a backup.



■ Description:Point-in-Time (PIT) restores would fail on Solaris if you usedEMC_timefinder_Mirror and if multiple VxVM disk groups were involved inthe restore.



■ Description:Only the latest BLIB backup imagewould be restored from theNetBackup-Javauser interface and the previous image restore failed with a status 5 error.

■ Work around:


96

If you encounter this issue, use the NetBackup Administration Console forWindows.


■ Associated Primary Etrack: 1933175 2087036

■ TITAN cases: 410-659-456


■ Description:A change wasmade to the NetBackup JobManager to write the file list to a fileand pass the name of the file to nbpem. That enables nbpem to read the properfile.



■ Description:A redirected restore of an Exchange 2010 database would fail with a status 5.The redirected restorewas redirected either to a database on a different serverwithin the same DAG, or to a different DAG.



■ TITAN cases: 411-446-642


■ Description:Restores to VirtualCenter would fail with the following error message:The request refers to an object that no longer exists or has never

existed.



■ Description:Allowing the user to create LiveUpdate and normal policies with the samename would cause failures.




■ Description:This release contains a BMRclient proliferation toWindows Server 2008/2008R2.



■ Description:TheAboutSymantecNetBackupwindow showed the Copyright year as 2009.A change has been made to correct this date.


■ Contained in: NBLU_7.0.1.UNIX NBLU_7.0.1.WIN NB_JAV_7.0.1NB_JAV_7.0.1.winnt.IA64 NB_JAV_7.0.1.winnt.x64 NB_JAV_7.0.1.winnt.x86

■ Description:The NetBackup-Java Administration Console connects to the master or themedia server. PBX makes the connection on port 1556 to vnetd instead of itbeing a direct connection to vnetd on port 13724.



■ Description:Communication with the NetBackup CORBA Services would fail in theNBAC-enabled mode.



■ Description:Exchange off-host backups would fail when the backup only uncommittedlogs option was selected.




■ Description:


98

A change was made to address an issue that caused the EMC_Timefinder_*FIM to fail if the device ID is greater than 8000.



■ TITAN cases: 281-814-626


■ Description:When vault profiles come to a bad image header or a corrupt imagewhile theygo through the images database, the profile gets canceled with a status 13error. The error is a failed file read error.



■ TITAN cases: 281-893-652


■ Description:A change was made to ensure that BPRD is able to remove old log files that aregreater than 2GB in size.

Etrack Incident: 1925307 1925306 1925305


■ TITAN cases: 412-236-787


■ Description:One cannot select an ESX server within a cluster when recovering a VMwarevirtual machine to an alternate configuration by the vStorage API.

■ Work around:If you encounter this issue, set the credentials in NetBackup for the desiredcluster node as a standalone ESX server. Then select it as the ESX server inthe restore.



■ TITAN cases: 411-856-414



■ Description:The high delays occurred when alternate location restores to a vSphere cloudif there were more than 100 ESX hosts.



■ TITAN cases: 320-234-872


■ Description:AMappedFullVMbackupof twovirtualmachineswould failwith the followingerror message:bpbrm main: db_FLISTsend failed: file read failed (13)

If the primary OS disk was converted to a dynamic disk and had boot andsystem volumes on separate partitions, then the mapping of the partitions onrest of the basic disks would fail.



■ TITAN cases: 320-239-777


■ Description:Enabling VxSS on a client causes the client-side deduplication jobs to fail witherror status 83, Media Open Error.



■ TITAN cases: 230-705-186


■ Description:VSS snapshot creation would fail with a wildcard path. A change was made toaddress this issue.



100


■ Description:Cost variables that are related with a cost formula were not deleted and nomessage confirming that appears in the user interface.

■ Work around:If you encounter this issue, delete the Cost Formula that is associatedwith thecost variable. Then delete the cost variable.



■ Description:If a client was added with the bpclient command, bpclient -add -client

<clientName> the backup jobs may fail with a status 902 error.

■ Work around:If you encounter this issue, add a bpclient with all host attributes.



■ TITAN cases: 241-006-439


■ Description:TSM job collections would fail with a status A8006 Error while the job datawas collected.An error similar to the following was seen in the agent logs:TSMJobReader.setJobAttribute Exception while setting Job Attribute

java.lang.NumberFormatException: For input string: "349.010" at

java.lang.NumberFormatException.forInputString

(NumberFormatException.java:48)

■ Additional Notes:This fix is relevant only for non-English locales.




■ Description:A change has been made in OpsCenter to avoid the build breaks that audittrails core checkins caused .



■ Description:The Use drop-down list incorrectly showed VMWare backup host in thePerform offhost backup for a Hyper-V policy.



■ Description:A changewasmade to address an issue that caused a failure to de-allocate andrelease the disk volume.



■ TITAN cases: 220-706-183


■ Description:The NetBackup for MSSQL agent would add all databases in the SQL Retryscript for transaction log backup even if they were successfully backed up.



■ Description:TheNetBackup JobManager (NBJM)process crashedwhile the computer startedif it could not communicate with the NetBackup Resource Broker (NBRB).



■ TITAN cases: 220-705-174



102

■ Description:A change was made to correct an issue that caused more than one job to beassociated with a single job ID.



■ Description:Fibre Transport multiplexed backups would not work properly on Windowsplatforms with FlashBackup configured.



■ Description:The Alternate SQL database restore would fail if the database was created onthe reparse mount point.



■ Description:A fix was added to ensure that the NetBackup services would not fail to starton Windows 2008 master server.




■ Description:How the vendor-unique, library handled the bar codes caused the injectoperations to fail. This issue required the user to perform CLI operations towork around the issue. A change was made to correct this issue.



■ Description:A change wasmade to address an issue that caused policy validation to fail onHP-UX IA64 systems.




■ TITAN cases: 240-994-016


■ Description:Windows-based serversmay fail the restore of KMS-encrypted images ifmorethan one image is required.



■ Description:If an allocation request to MDS timed out, the result would be that someresources were orphaned. The user may notice that some media may appearas available and are not used.



■ Description:If you performed a backup of an Exchange Server and Enable granularrecovery was selected on the policy, the backup took a very long time tocomplete and it eventually failed.



■ TITAN cases: 320-237-675


■ Description:A Multiple VC-Proxy environment failed when if the proxy could notcommunicate to one of the VCS.



■ Description:A change was made to address an issue that caused bprd to core dump a FullVM was restored that used a transport type that was unavailable.


104



■ Description:A changewasmade to correct an issue that caused the Nbproxy to leakmemory.



■ TITAN cases: 281-881-993


■ Description:A changewasmade to ensure thatVault does not recallmedia from the volumegroups that were not associated with Vault.



■ Description:Unable to run the LiveUpdate policy with NBAC turned on.



■ Description:A special case code was added in the Tar Stream Handler processBuffermethod that handles the following case: When an Unknown Length file type isprocessed, the tar header for that Tar type is at the end of the Tar Stream

Handler.

The translation process would return from processing the TAR header andnot return a Stat block. That caused poor deduplication ratio's for PureDisk.



■ Description:A change was made to make the online AT date option optional.




■ TITAN cases: 411-336-029


■ Description:The <commmand>bpfis</commmand> would fault on the NetBackup 7vStorage Backup.

Etrack Incident: 2035929 1991910 2035887 2035867


■ Description:Provide ability to specify and use SQL Server 2008 compression.



■ Description:Changes were made to log better messages for assert conditions.



■ TITAN cases: 411-201-782


■ Description:A change was made to correct an issue that caused the Point-in-time restoreto not complete. In addition, bmrd would consume a lot of the CPU.



■ TITAN cases: 411-113-080


■ Description:The NetBackup for MSSQL server GUI would crash when the user tried tobrowse the backup images of a mirrored database from the principal node for


106

restore. In addition, it displays images of the databases that are not mirroredbut have same name as the principal node database.



■ Description:A changewasmade toNetBackup startingwith this release.Users areno longerallowed to uninstall the base version of NetBackup after NetBackup 7.0.1 hasbeen applied until all patches have been removed. Once the user has removedall of the patches, then the base version entry in the Add/Remove Programslist is selectable.This change applies only to NetBackup installs, and not to the add-on productinstalls like the NetBackup-Java Console.



■ Description:This release contains a new client offline feature.



■ TITAN cases: 281-779-110 412-353-754


■ Description:A fix was added to ensure that you can back up a share from a NetApp filer ona Windows 2008 computer.



■ Description:A change was made to ensure that client-side deduplication works with aHyper-V VM backup.



■ TITAN cases: 220-708-022



■ Description:An NDMP backup to disk created a 0-KB fragment if a volume in the policy'sbackup selection did not exist.



■ TITAN cases: 240-984-409


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

■ Additional Notes:There was DFSR.exe issue with 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. Thatcannot be prevented.



■ TITAN cases: 281-832-788 281-833-636


■ Description:A changewasmade to address an issue that caused the policies to be scheduledan hour late after a switch was made from Daylight Savings Time (Brazil).



■ TITAN cases: 241-008-818


■ **Description:Media would be deassigned incorrectly because of an incorrect number ofimages count in the EMM database.



108


■ TITAN cases: 281-891-174


■ Description:The nbdelete needs an option that enables the user to specify the bpdmmediaserver from the command line.



■ Description:A fix was added to the SharePoint differential schedule types for streamingbackups. (The change means that differential incremental backups areperformed and not transaction log backups.)



■ Description:The Legacy TimeFinder backupwould fail when PowerPathwas installedwitha Storage Foundation.



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


■ Description:A change wasmade to correct an issue that caused bpdbjob to core dumpwiththe -fast option.



■ Description:A change was made to ensure that a restore of a Configuration database for aSharePoint 2010 works appropriately.




■ Description:A change was made to address an issue that caused nbsl to crash when theNetBackup Administration Console was opened.



■ Description:TheVxFSCheckpoint snapshotmethodwould fail onHP-UXwith the followingerror:Cannot dlopen load module '/lib/pa20_64/libpthread.1' because it

contains thread-specific data.



■ Description:A problem in the NetBackup Vault module occurred when NBAC was set toAutomatic mode. In case the credentials of NBAC vault operator expire andthe NBAC mode was set to Automatic, the vault eject job would remain activeuntil it timed out. The default timeout is seven days.

■ Work around:To avoid this issue, youmust set theNBACmode toREQUIRED/PROHIBITED.



■ TITAN cases: 312-182-724


■ Description:Backing up a Hyper-V virtual machine (VM) would fail if the VMwasmountedon a GUID volume partition, as opposed to a drive letter mount.



■ Description:


110

In NBAC enabled mode, the Windows BAR user interface was not able to getthe Restore Files list.



■ Description:The following issues were fixed in the Client coverage report.- The last full job run date was shown as Dec 31, 1969 7:00 PM for all clients.

- The last incremental job run did not match the time with NetBackup.- The OpsCenter server and the NetBackup master appeared in different timezones. The OpsCenter server was shown in CDT and the NetBackup masterwas shown in IST.From theOpsCenter user interface, you can change the data display time zoneto IST+5.30 which is same as the NetBackup master server. Then you can runthe Client coverage report.Finally, you can verify that the last incremental job time is still displayedincorrectly. It is correctly stored in the database, but it is displayed incorrectlyon the OpsCenter user interface.



■ Description:Exchange VSS snapshot backups that are imported are not properly detectedas snapshot images at restore time.

■ Work around:To work around this issue, edit the SNAP_TIME field in the image catalog.



■ TITAN cases: 411090587


■ Description:The NetBackup for MSSQL agent would not close the ODBC connections afteruse. The agent left them open for the duration of the backup and caused thedatabase server to crash.




■ Description:The NBJM process would stop an active restore job on a restart. It then markedthe job as INCOMPLETE but did not make it RESUMABLE.

Etrack Incident: 2001699 1976941 2060385


■ Description:A new capability has been introduced into the SCSI Tape standard, the use ofAppend Mode. That prevents data from being overwritten by accident. IBMLTO-5 drives are an example of the drives that support this feature. See thelatest HCL for a complete list.Due to thenature of this drive capability, donot attemptmedia sharingbetweenthe servers that are running NetBackup 7.0.1 and servers running any olderversion of NetBackup. The media servers with older versions of NetBackupcannot write to the shared media (if the 7.0.1 server uses the media first andthen passed to the older server while it is still loaded). A power-cycle of thedrive may be necessary in some cases to recover the drive for use by serverswith older versions of NetBackup. The media in use at the time is the one thatis FROZEN, but it can be UNFROZEN once the media sharing configurationis corrected.The syslog on the server running the older version of NetBackup reports awrite error, that is presented as a WRITE PROTECT error.

Drive sharing (SSO) between NetBackup 7.0.1 servers and those with olderversions is not effected, and continues to work correctly.



■ Description:The properties of a BasicDisk on a NetBackup 6.5.4 server showed an errorwhen the master server had NetBackup 7.0 installed.



■ Description:A null pointer was foundwhile theHost Properties were loaded for themasterserver. This issue was corrected in this release.


112



■ TITAN cases: 410-735-774


■ Description:The bpfis query output for FIS IDs was truncated. A change has been addedto fix this issue.



■ TITAN cases: 411-352-754


■ Description:ASharePointRecoveryAssistant program (SPSRecoveryAsst) exceptionwouldoccur when the SharePoint object was selected in the Restore dialog.



■ TITAN cases: 281-776-123


■ Description:After a restart, the nbpemprocess did not read theDSSUschedules. That causedthem all to not run.



■ TITAN cases: 411-682-349


■ Description:The nbemmcmd -getemmserver reports a string for the host version that is notreadable.




■ TITAN cases: 411-684-860


■ Description:When the user specified SQLINSTANCE $ALL in backup batch file, the SQLAgent enumerated all of the hosts and instances in the network. That includedthe local host. However, sometimes it was not able to enumerate the local hostand instances even if the SQL server was installed on the local host.



■ Description:A change was made to fix an issue that caused VxFI to not work on HP-UX11.31 systems.



■ Description:While running under NBAC, if the user interface or command-line interfacecontactedmultipleAZ servers on the same system, itmight cause authorizationproblems.

■ Work around:If you encounter this issue, delete following file:- On UNIX, /usr/openv/var/vxss/AzHandleCache.data - On Windows,VERITAS\NetBackup\var\vxss\AzHandleCache.data



■ TITAN cases: 281-609-247


■ Description:Backup of a SQL-server databasemirrorwould fail with a status 2 even thoughit was not intended to back up anything.




114

■ Description:Adding support for BMR client and boot server on HP-UX Itanium 11.31platform.

The scope included is as follows:

■ Support for LVM and VxFS, hfs-based files systems.

■ Support for client configuration with only one HP-UX partition

■ Part of BMRCONFIGwhere volume length changes andmapping of volumegroups is supported.

■ Support for latest HPIA ignite version.

■ BMR Media-based restore



■ Description:In an NBAC environment, creating the Storage server would fail with a VxSSAuthentication failed (117) error.



■ **Description:A change was made to update the DR media information in the image catalogand the associatedDR filewhenan image copy is expired andwhen theprimarycopy changes.



■ TITAN cases: 281-805-383


■ Description:The NetBackup Resource Broker may not be able to grant resources to thestorage unit groups when its internal cache became invalid. That happenedwhen the drives went down unexpectedly.




■ Description:A change was made to add PFI support for the Linux platform.



■ TITAN cases: 410-830-026


■ Description:The bpdgclone process would fail with an invalid device set error for onevolume during ShadowImage backup.



■ Description:A change has been made to address an issue that caused NSL core dumps tooccur during the installation of an inactive node of a VCS cluster.



■ TITAN cases: 411-941-906


■ Description:Therunstoredquery command returned errors during a successful operation.For example, it was documented incorrectly and it wrote its output file to anunconfigured location.



■ TITAN cases: 410-976-336 411967107 412-377-546


■ Description:


116

Backing up many files with different owner and group names would lead to acore dump in bpdbm.



■ Description:If a reallocation for a span request failed on a multiplexed group NetBackupwould continue to add new requests to that group. That caused subsequentjobs to fail. A change was made to correct this issue.



■ Description:The NBAC configuration command(s) displayed an incorrect status messagewhen not logged on as NBAC administrator.

■ Work around:If you encounter this issue, ensure that the proper credentials are available atthe time you run bpnbaz -Setup[Client|Media].



■ Description:If Linux clients have a hyphen character (-) in the volume group name, anycorresponding volumes would not come up after a BMR restore. A change wasmade to correct this issue.



■ TITAN cases: 411-435-987


■ Description:The bpcdmay crash during an Exchange GRT enumeration of mailboxes thathappen to contain a new line character. That can cause the user interface tonot display all of the items or a GRT duplication that succeeds in a status 0,however, not all of the granular items are cataloged.




■ Description:Fixed a potential core dump for NetBackup services in an NBAC-configuredmode.



■ Description:On some UNIX platforms the environment variable NB_ORA_PARENT_JOBIDwould not get set in bphdb.



■ Description:In anNBAC environment, when theNetBackup 7.0.1 patch is reinstalled (afteruninstalling the previous one) the following warning was shown:The NetBackup Access Control upgrade failed and must be run

manually.



■ Description:The SharePoint GRT backup did not enumerate for a granular restore.

■ Work around:The problemwas caused by path names that were greater than 260 charactersin length.To avoid this issue, configure SharePoint with shorter names.Another workaround is to install KB 955012 forWindows 2003 SP2.Windows2008 does not have this download available yet, andWindows 2008R2 alreadycontains the fix.



■ Description:


118

The master server filter did not work as expected in the Media summary bythe media server report.



■ TITAN cases: 411-412-701


■ Description:A change was made to correct an issue that caused NRBR to hang during anupgrade. NBRB would hang at during the startup and while the allocationdatabase was validated.That caused the system to be inoperable, particularly if there were manyoutstanding allocations when the system was shut down.

■ Additional Notes:This change also improves the performance of the nbrbutil -dump process.

■ Work around:If you encounter this issue, run nbrbutil -resetAll against the previousversion before you upgrade.



■ Description:This release contains enhancements to the Deduplication report.



■ Description:Restore of an off-host backup failed if the Exchange transaction log file namesstartedwith lowercase "e". That is anunusual circumstance, because Exchangeuses an uppercase 'E' when files are created. The problem occurs becauselowercase file names cause an incomplete backup to be made.



■ Description:


A change was made to address an incorrect report description for the Jobsuccess by client.



■ Description:A VSS backup would fail while a Snapshot was taken of multiple drives.



■ Description:A change was made to address an issue that caused the NbWin.exe script tocore dump on the Backup, Archive and Restore window.



■ TITAN cases: 220-586-187 291-186-078


■ Description:NetBackup Vault shows an internal error 286 while a vault session tries tomerge batches with common media at the duplication step. If you configuredthe ALLOW_MULTIPLE_RETENTIONS_PER_MEDIA parameter to YES(bp.conf), then the media now has different RL images. Vault fails to mergethe media if the found media has different RL images.



■ TITAN cases: 281-762-843


■ Description:The NetBackup jog manager would continue to try to send resources to bptm

after one had finished.




120

■ Description:A correction was made to replace a missing Invalid Parameter Handler forWindows for the services that used the ACE ORB.




■ **Description:NDMP snapshot backups would complete with success but no image existed.



■ Description:A change was added to address an issue that caused an NBSL-HostSesssions

leak, because they were not cleaned appropriately.



■ TITAN cases: 411-275-589 411-878-859


■ Description:Exchange 2010 standalone server backups would fail with a status 103 errorand the following message would appear.FTL - snapshot preparation failed - Unable to determine Exchange

version, status 103

In addition, Exchange 2010 DAG backups would fail with a status 26 error.That type of backup was not supported on this version of Exchange.

■ Work around:If you encounter this issue, delete the following registry key on the Exchange2010 server, (it should already be empty):HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Exchange\Setup



■ Description:Exchange snapshot (VSS) backups would fail with a status 41.




■ Description:Changes were made to allow NBJM to start commands on remote servers bythe vnetd transient service (VTS).



■ Description:The trend-based historical reports export would fail if there were only twodata points.



■ TITAN cases: 320-216-005


■ Description:TheNetBackupEnterpriseMediaManagerhung in somescenarios if themanualdevice configuration is performed under heavy loads. That was because theorder of locks acquisition was not consistent.



■ Description:The NBPEM process would stop scheduling jobs for a policy if it failed to get thelast backup data from BPDBM.




■ Description:Added support for multiplexing NDMP backups.



122


■ Description:A Snapshot backup would take a very long time withIBM_DiskStorage_FlashCopy FIM.



■ Description:After editingmultiple policies that havemultiple SLPs, the jobs failed becausethe user interface saveed the wrong STU.



■ TITAN cases: 411-531-047


■ Description:The time it took to call the RetrieveHostsComputeResourceContents functionwould grow very large when there are a number of ESX hosts.



■ Description:The Group component summary for Job was missing.



■ Description:Parsing UNIX images failed when you attempted to restore on a Windowsplatform.



■ TITAN cases: 412-177-099



■ Description:A change was made to ensure that you can modify an existing schedule in thevault policy after the NetBackup-Java user interface was restarted.



■ Description:This release contains a BMRclient platformproliferation feature that supportsthe restore of an AIX 6.1 operating system-based client.



■ TITAN cases: 411-489-299


■ Description:For a restore, the job monitor would only report the KB/sec of the last writeand not the average.



■ TITAN cases: 410-630-281


■ Description:A change was made to address an issue that caused delays in the resourceallocation thatwas causedby the lackof an indexon theEMM_AllocationStatustable.

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



■ Description:


124

An error occurred with the MFC user interface when the properties of storageunit that were created on media server were check.



■ TITAN cases: 410-604-465


■ Description:A change was made to ensure that correct media server is selected for an SLPduplication. The original issue caused the wrong media server to be selectedand the following error message to appear.media write error(84):Duplication error with PDDO



■ Description:A change was made to ensure that the OpsCenter user interface does notinadvertently delete customand standards reports. That occurredwhen a usertried to delete a report while existing folders were selected.



■ Description:An enhancement wasmade to add differential and incremental schedule-typesupport with a SharePoint Agent .



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


■ Description:The bpbkar process crashed on the inactive node in a clustered 2008 clientduring a ShadowCopyComponents backup, if the backup contains an invalidpath.




■ TITAN cases: 320-227-585


■ Description:During a catalog backup, the *.ior.mgr files in /usr/openv/var may beselected for backup, but disappear before they get backed up. That causes thebackup to end with a status 1 error.



■ TITAN cases: 411-407-107


■ Description:As processor technology and operating systems evolve, they introduceout-of-order execution,memory access, and cache updates. Changes have beenmade that introduce memory barriers around some of NetBackup'sinter-process, communication methods. In this case, the data mover'sshared-memory-buffer control logic was enhanced.



■ Description:Fix memory leaks and improve performance of Exchange granular browsing,especially during the cataloging phase of a duplication operation for anExchange granular enabled image.



■ Description:The NBJM process can crash on shutdown if a backup job is started and twosockets have been established with the media server.




126

■ Description:Added the ability to use nbdssl for restores.



■ TITAN cases: 281-619-862


■ Description:A changewasmade to ensure that all drives of a given tape library are displayedin the Tape Drive Utilization report.

■ Additional Notes:This issue was seen when the drives were shared by multiple media servers.The relevant database-stored procedure was corrected to fix this issue.



■ Description:A change was made to fix UBS and client coverity errors.



■ TITAN cases: 410-990-600 411-697-192


■ Description:BMR-for-Linux requires the user to type in the scsiLoadOrder string to use aMedia-based restore. This string is very long and it is easy to make a typingerror that can cause a failed Bare Metal Recovery.This release contains an enhancement wherein the Media-based restoreemulates a network-based restore. That means that the user is not requiredto type in the scsiLoadOrder string manually.



■ TITAN cases: 412-391-498



■ **Description:A change was made to address an issue that caused the bpbkar exclude listentries tomatch the shorter file names. For example, the following fileswouldhave been considered a match with an exclude_list entry that is *.dba.

abc. -> match (However, that should not have been a match.)

abc.x -> not matched

abc.d -> matched (However, that should not have been a match.)

abc.dx -> not match

abc.db -> matched (However, that should not have been a match.)

abc.dbx -> not matched

abc.dba -> matched (that was correctly matched.)

The change that was added to this release fixes these inconsistencies.



■ Description:A change was made to address an issue that caused bptm to crash with amultistream SAN Client restore after a data transfer.



■ TITAN cases: 411-687-177


■ Description:The vSphere inventory browsingwas slow if the backuphost could not resolvethe IP addresses of the virtual machines.

■ Additional Notes:Added registry entry to disable the reverse IP resolution.



■ Description:This release contains a new audit trails feature. For a brief description of thisfeature refer to the, About New Features section.




128

■ Description:Vault configuration was not cluster-enabled after a new 7.0 clustered UNIXNetBackup master server was installed.

■ Additional Notes:For more information about this issue, refer to the following Technote on theSymantec Support Web site.http://entsupport.symantec.com/docs/349907



■ Description:A change was made to remove the include files that were already present inthe extsrc for bespsserver.



■ TITAN cases: 320-226-337


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



■ TITAN cases: 410-598-115


■ Description:A nocache option is no longer needed for a symcfg discover operation. The-nocacheoptionwas added for aShareddiskuse case and it is no longerneeded.



■ TITAN cases: 411-437-832



■ Description:A successful optimized duplication would sometimes create fragments in theimage catalog that had truncated disk media IDs.



■ TITAN cases: 411-932-352


■ Description:Snapshot backupswould fail on after a vxsnap refresh call that caused a status156 error.Ifmultistreambackupswere runwith the InstantRecovery feature bppficorrwould not update all of the image headers in themultistreams during an imagerotation. This resulted in a snapshot-creation failure for a third backup, whenthe FlashSnap/VxVM full mirror type snapshots were used.



■ TITAN cases: 411-490-895 411-596-113


■ Description:The ImageData collectiondidnotworkproperly after anupgrade toNetBackup6.5.5.The following errors were seen in the agent logs:agent.module.netbackup.NetBackupBpimagelistParser.createImage Job

of the image is Zero, hence ignoring : 0

agent.module.netbackup.NetBackupBpimagelistParser.parse Error when

parsing bpimagelist data - 'FRAG' occurred without previous 'IMAGE'

or 'IMAGE' line is malformed [FRAG 1 1 32 0 2 13 4 SDLT07 linux01

65536 21 1269522653 1 0 *NULL* 1271170201 0 65537 0 0 0 1 0

1269960631 0 *NULL* *NULL*]

■ Additional Notes:This fix is relevant only for pre-7.0 versions of NetBackup.



130


■ Description:This release adds support for the following: - BMR Support for SLES10_x64client and Boot server - BMR support for SLES11_x64 client and Boot server



■ TITAN cases: 411-783-601


■ Description:An attempt to redirect the recovery of an Exchange mailbox item did notredirect the destination if the mailbox name contained non-English letters. Ifthe specified destination was on the original Exchange server, the item wouldbe restored to the original mailbox path. If the destination was on anotherserver, the recovery would fail.



■ TITAN cases: 281-715-968


■ Description:NetBackupprovides configuration options that control the client log file cleanup and the vault session directory cleanup.NetBackupmay ignore non-defaultvalues for those options on some platforms. NetBackup performs log clean upoperations with the default values for those configuration options on theaffected platforms.



■ Description:FlashBackup single file restore of an entire volume failed with the followingbpbrm error 185:

tar did not find all the files to be restored and tar shows VxMS

error 4101 - Access denied.




■ TITAN cases: 411-696-095


■ Description:If ExpMgr failed, the disk cleanupwouldnot runagain for aDiskStagingStorageUnit (DSSU). This issue caused the jobs to hang.



■ Description:Unable to read license information for amedia serverwhenconnected remotelythrough Windows user interface.



■ TITAN cases: 411-194-165


■ Description:A change was made to prevent you from using the TapeDeleteHoursincorrectly. The result could be a data loss. The change prevents you fromextending the expiration of copy #1 such that the result is an inconsistentcatalog.



■ Description:The NBPEM process terminated if 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.




132

■ TITAN cases: 411-684-714


■ Description:The dblib process failed to detect the event log and activate the applicationlogging.




■ Description:An attempt to browse an Exchange database for mailbox names would notreturn any mailboxes. The ncflbc log contained the following error:

12/7/2009 11:27:57.961 V-309-28 [_nbfs_link_create()] ERR - fwrite

failed, error = 6

■ Work around:The browse may succeed on a retry. This was an intermittent failure.



■ Description:A Point-in-Time (PIT) restore failed with an error and the following reportwould not open, C:\ProgramFiles\Veritas\NetBackup\online_util\fi_cntl\bpfis.fim.power12cdg_1260166705.0.



■ TITAN cases: 411-532-290


■ Description:A single connection from the expirationmanager to EMMwas shared betweenmultiple threads in the expiration manager process. Closing it in one of thethreads caused a disruption or failure to occur in others. Each thread wasprocessing a high water mark (HWM) event for different volumes.




■ Description:AnExchange PFI-to-tapewould fail with a status 69 error, Invalid file list

specification. (That is the Instant Recoverywith copy snapshots to a storageunit option set.)In addition, Exchange backupswould fail with a status 200 error. (That failurewas a regression that was released with an EEB for exchange with a largeamount of snapshot data.)



■ Description:A change was made to ensure that duplicate control files are not shown in theOracle clone wizard.




■ Description:An attempt to restore from an image that an Exchange 2010 off-hostincremental backup created causes the recovery of the database to fail. Thebackup and restore jobs both finish with a status 0.An attempt to restore from an image that an Exchange off-host incrementalinstant recovery backup created causes the recovery of the database to fail.The backup and restore jobs finish with a status 0.



■ Description:Time schedules that were associated with a report schedule were not deletedand no message appeared in the user interface.

■ Work around:If you encounter this issue, delete the time schedules that are associated withthe cost variable. Then delete the report schedules.



134


■ TITAN cases: 412-021-855


■ Description:A granular restore to an Exchange 2010 standalone server that did not havethe CAS role would fail.

■ Work around:If you encounter this issue, change the destination client to be that of a serverwith the CAS role.



■ TITAN cases: 320-220-208


■ Description:TheMEDIA_SERVERoption in thebp.conf file on themaster denies theQ_DC_GET(DataClass) query 272 for a BPDBM, STATUS 37.



■ Description:NetBackupdoesnot handle vApp containers for backupor restore. vAppvirtualmachines (VMs) are not visible during the browse for VM's, and you cannotselect the target vApp during a restore.



■ Description:The bpduplicate process would crash or hang if the bptm write process sentan EXIT STATUS for a duplication before sending the DATASOCKET messagewhen preserve multiplexing was specified.




■ Description:A change was made to correct a misspelled word in a prevalent PDDEconfiguration error message.



■ Description:Fixed a coverity issue related to address free.



■ Description:AnExchange granular duplicationwould endwith a status 0when nblbc failedto run properly.



■ Description:A restore to the original location would fail for an Enterprise Vault partitionor Index location if the network share pathwas used an it contained the dollarsign character ($). Here is an example of a network path that contains a dollarsign character: \\system\admin$

■ Work around:If you encounter this issue, restore the Enterprise Vault partition or Indexlocation with the alternate location option.



■ TITAN cases: 320-225-721


■ Description:NOM would report an incorrect license utilization on an alert.




136

■ TITAN cases: 281-876-404


■ Description:The NDMP DirectCopy was not invoked during a duplication whenCONF_DISALLOW_NONNDMP_ON_NDMP_DRIVE is set to true for the media server.

TheMDSmisinterpreted the CONF_DISALLOW_NONNDMP_ON_NDMP_DRIVE settingand caused the issue.

■ Work around:If you encounter this issue, set CONF_DISALLOW_NONNDMP_ON_NDMP_DRIVE =

FALSE for all media servers.



■ Description:Assigningmultiple policies to a view a lot of time, and the timewould increasewith the number of policies that were assigned.

■ Additional Notes:This release contains performance changes and appropriate user interfacemessages to address the issues with assigning policies to views.



■ Description:Changes have been made to provide more consistent logging for errors thatare at various severity levels to make troubleshooting easier.



■ Description:Adding support for BMR client and boot server on HP-UX Itanium 11.31platform.

The scope included is as follows:

■ Support for LVM and VxFS, hfs-based files systems.


■ Support for client configuration with only one HP-UX partition.

■ Part of BMRCONFIG where volume length changes and simple mapping ofvolume groups is supported.

■ Support for latest HPIA ignite version.

■ BMR Media-based restore



■ Description:On aNetBackup7.0 host, if NBAC is enabled, theNetBackup servicesmay causea core dumpafter oneweek. This occurred because of a failure in the Renewinga service credential.

The typical service credential validity period is one year. To ensure continualavailability of a useful credential, NetBackup tries to renewa service credentialwhen it is seven days stale. Because of an issue, some of the NetBackupprocesses would dump core.

■ Work around:If you encounter an issue like this, create a cron job or scheduled task to touchthe existing credential files so they are run at an interval that is less than sevendays. Files to touch are: /usr/openv/var/vxss/credentials/* on UNIX%Program_Files%\VERITAS\NetBackup\var\vxss\credentials\*onWindows32bit%Program_Files (x86)%\VERITAS\NetBackup\var\vxss\credentials\*

on Windows 64 bitNOTE: The downside to thisworkaround is that the service credential renewalis not be attempted by the NetBackup services automatically. Thismeans thatthe credentials definitely expire after one year.

The following list shows two ways to mitigate this issue:

■ Regenerate a credential before expiry (one year) by running the followingcommand./usr/openv/netbackup/bin/admincmd/bpnbaz -setupclient hostname

■ Extend the credential expiry from the default of one year to longer term.In the following example extend the credential from one year to five years:Go to /usr/opt/VRTSat/bin (UNIX) or%Program_Files%\VERITAS\Security\Authentication\bin (Windows).

vssat setexpiryintervals --pluginname vx --prpltype user

--credexpiry 157680000


138

Where 157680000 is the number of seconds that equal five years (60 * 60* 24 * 365 * 5).


■ TITAN cases: 411-458-271


■ Description:A change was made to address an issue that caused BMR restores to hang.



■ Description:The restore requests that are initiated from a node in an Exchange 2010 DAGwere missing the restore details in the progress details.



■ Description:The bpmedialist command did not display themedia thatwas assigned to theSnap vault server.



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


■ Description:Added the capability to prompt the user to open a Diff/Tlog-based MOVE bch

file in Notepad from the NetBackup for MSSQL GUI. You encounter thisenhancement when you save a Diff/Tlog-based MOVE bch file in the MSSQLGUI.



■ Description:A redirected Exchange 2010 database did not get restored even though theredirected database restore job finished successfully with a status 0.




■ Description:A PIT rollback from a FlashSnap backup failed with an error in the commandvxassist unassign.



■ Description:NDMPbackupswould fail when client-side deduplicationwas set toPreferred.



■ Description:VxFI based FIMS are not supported with RHEL 5, RHEL 6, SUSE 10, and SUSE11. A change has been made to update the rescan logic to ensure that newlyunmasked devices are visible in device name space.



■ Description:A change was made to remove the code that tuned the unused Backup ExecVMware tools timeouts.




■ Description:A change was made to support RealTime with Snapshot Client on RHEL5 forJPMC.



■ Description:


140

A change was made that enables you to redirect an Exchange 2010 databaseto an alternate server or an alternate databasewith only theDAGvirtual namespecified as the destination host.

■ Work around:Youhave to specify the active server at the timeof the restore as the destinationhost.



■ Description:This release of NetBackup (7.0.1) includes an updated version of theNBCC andNBCCR utilities. The version number is number 7.0.1.



■ TITAN cases: 240-748-094


■ Description:Images with KEYWORD fields of exactly 128 characters would cause variousNetBackupoperations to fail. That included thebpimagelistand thebpexpdatecommands. The message, text exceeded allowed length would appear inbpdbm logs.



■ Description:A changewasmade to address an issue that caused nbsl to consume toomuchmemory.



■ Description:In a rare situation, the bptm process would core dump during a backup orduplication when writing the true image restore (TIR) fragment.




■ Description:A change was made to ensure the Cost Report are scheduled properly.



■ Description:A change was made to ensure that the View Automation puts the hosts underthe correct node.



■ Description:VxFI array providers were built only on those platforms where they weresupported.With this release, a change wasmade to build all of the VxFI-basedproviders on all of the platforms.



■ Description:Restores would fail if you selected Granular restores from multiple Exchange2010 DAG backup images.



■ Description:During the backup of an Exchange 2010 DAG, the backup history did not getupdated if the NetBackup media server was a UNIX server.



■ Description:The bpadm process did not allow the user to enter a disaster recovery (DR) filepath name with a space in it.


142



■ TITAN cases: 410-944-310


■ Description:An issue was resolved that caused vfm_open_fine_index to fail and theFlashBackup job to exit with a status 1 error.



■ Description:Unable to create a progress file from bpduplicate, bpverify, or bpimportwhile a UNIX master was remotely administered from a Windows media ormaster server.



■ Description:The SystemState directive did not include EFI for the backup and that causeissues on the restore.



■ Description:An exception would occur while the <guimenulabel>CustomTabular</guimenulabel> report for themedia datawas emailed and exported.



■ Description:bpbkarwould crash for FlashBackup andMSC snapshot backups onAIX 64-bitplatforms.




■ Description:This release contains a BMR client proliferation to Windows Server 2008 andWindows Server 2008 R2.



■ Description:A change was made to bpimport so that it supports the -drfile argumentwith AdvancedDisk types.



■ Description:A change was made to force the use of the proper directive use for Exchange2010. This change only allows DAG's to be backed up with the MicrosoftExchange Database Availability Groups:\ directive.



■ Description:Whenyouperformbackups to amedia serverDeduplicationPool or a PureDiskDeduplication Pool, the deduplication ratio may be lower than expected. Thelower-than-expected ratios have occurred during attempts to back up theSystem State, Shadow Copy Components, Exchange (stream-based andVSS-based), and SharePoint (stream-based and VSS-based).



■ Description:Changed the message that is displayed during an off-host Exchange GRTbackup if the distributed application restore mapping was not configured onthe master server.




144

■ TITAN cases: 411-523-959


■ Description:Multistreamed jobs of a client that were defined with the dynamic_addressargument failed with a status 25 error.



■ Description:The nbemmcmd -errorsdb -prune command caused nbemm to core dump onSolaris x86 and other 64-bit architectures. This issue return unreadable datafor the records that remained if it did not cause a core dump.

■ Work around:If you encounter this issue, restart nbemm after you run the command.



■ TITAN cases: 281-801-480


■ Description:The wrong (zero) media date was saved in the image fragment on an HP-UXIA-64 master server.



■ TITAN cases: 410-659-456


■ Description:A change was made to reduce the number of entries in the file list that bpfispasses to bkar during an Exchange VSS (snapshot) backup. It passes the listby passing a range of log files instead of passing an individual entry for eachlog file.




■ Description:A change was added to display the host that executes bpresolver for anExchange 2010 DAG backup.



■ Description:Hyper-V virtual machine restores failed when the path name for the .xml filecontained a volume GUID.



■ Description:A change was made to increase the inventory timeout for robotic libraries tomore than 300,000 media.



■ TITAN cases: 411-459-985


■ Description:In the cluster environment the local host name cannot be found in theenumeratedhost or instance list. This caused the backupoperation to fail withthe following error.An instance of SQL Server was not found on this client.

It also caused GetCurrentDSN fail with the following error in dbclient logs.

Error 64 has been returned from GetCurrentDSN




■ Description:


146

With a Solaris master server, Exchange 2010 DAG backups would fail with astatus 5 error in the parent job even though all of the children backup jobssucceeded.



■ Description:Optimized duplication of TIR files should attempt a retry when the pluginreturns STS_EBUSY.



■ Description:A change wasmade to address a possiblememory corruption that could causea crash in granular restores on Windows with the nbgre.exe process.



■ Description:Achangewasmade to specify an invalid argument insteadof anunimplementedfeature for a bad bpexpdate query.

Etrack Incident: 1958530 1936232 1997015


■ Description:This release contains enhancements that improve the UNIX file-refactoring,new OpenSSL code, and additional improvements to common libraries.



■ Description:nbemm would core dump while selecting Fibre Transport jobs.



■ TITAN cases: 411-807-544



■ Description:A change was made to ensure that NetBackup 7.0 supports the VMwarevNetwork distributed switches.



■ Description:A change was made to ensure that the proper file version and copyrightinformation existing in the source code.



■ Description:The list of VMware virtual machines could be empty when a folder in thevSphere hierarchy contains non-ASCII characters, with no error logged orreported.

■ Additional Notes:VMware's vStorageAPIhadan issuewhich caused foldernameswithnon-ASCIIcharacters to not be encoded with UTF-8. The bpVMutil utility failed to parsethe XML document that contained the bad data, but did not report an error.This patch is to fix the bpVMutil utility so that it detects the error and reportsit. It does not fix the underlying VMware issue with the incorrectly encodeddata.

■ Work around:To resolve this issue, obtain a fix from VMware so that the folder names thatcontain non-ASCII characters are returned encoded in UTF-8.



■ TITAN cases: 281-749-891


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


148



■ Description:The storage unit filter was not implemented in the Storage Unit Throughputreport.



■ Description:The OpsCenter user interface did not respond to an attempt to view mediawith the Hierarchical view by volume pool option.



■ Description:A change was made to the base shared resource tree (SRT) in an AIX versionof the operating system because the SRT would not be updated properly.



■ Description:While writing backup images to BasicDisk and AdvancedDisk, synchronousflushing of image data was not forced during the image close. This created asmall windowof timewhere the datawas not completely sent to disk, however,NetBackup believed that it had been sent.



■ 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: 412-160-631


■ Description:A change was made to address an issue that caused the bpfilter process tocore dump on Windows platforms.



■ Description:Added new directive set for Enterprise Vault 9.0 support.



■ Description:A change was made to ensure that Vault properly distributes reports to aJapanese folder.

■ Work around:If you encounter a similar issue, use folders that are in English.



■ TITAN cases: 240-956-981


■ Description:A changewasmade to correct a robotic unload issue that occurredwhenmediasharing and NDMP was used.



■ Description:


150

Enhancements weremade to provide backup and restore support formultipleFSA Reporting databases in the NetBackup Enterprise Vault agent.



■ Description:A change was made to remove the bmradmin account on the BMR boot server.While the boot server was set up the bmradmin user ID was created by default.In some scenarios, users may not use the user ID and account which couldcause concern by some users.



■ TITAN cases: 411-526-602


■ Description:An issuewas addressed that caused nbpem to grow in size during a long-runningjob.



■ TITAN cases: 241-000-151


■ Description:A change was made to ensure that you can restore folder and subfolders afterFull and Incremental FBU Backup images were selected in the BAR userinterface.



■ TITAN cases: 320-231-426


■ Description:


During incremental backups with TIR information enabled, the followingmessagemay appear in the error log once for eachmissing file, and the backupsucceeds.Catalog entry for [a file] indicates it is a TIR entry, but cannot

locate a previous backup containing the entry

This fix reduces the volume of messages, and it causes backups with thiscondition to fail.



■ Description:A SharePoint streaming backup to PDDE would receive a proxy error.

■ Additional Notes:A change was made to add a call to ignoreBPConfServerListmethod inconnectProxyServer() to bypass the NetBackup client server name check inthe bp.conf file.

■ Work around:If you encounter this issue, add theNetBackup client server name to the bp.conffile.



■ Description:The exception handling log-message would print a hex-number rather than alog message.



■ TITAN cases: 281-889-533


■ Description:User backups with checkpoint restart enabled would go to the DONE staterather than the INCOMPLETE state after a failure occurred. That meant thebackups cannot be manually resumed after the failure.




152

■ Description:A change was made to correct the libonline shim library check that did notwork on an HP-UX 11.31.



■ Description:This release contains a BMRclient platformproliferation feature that supportsthe restore of an AIX 6.1 operating system-based client.




■ Description:Import phase 1 would fail because of a large TIR fragment.

■ Additional Notes:An attempt to import TIR backups that are createdwith 7.0GAwould fail whenthe destination storage units were disk storage units, and the TIR files imagewas greater than 2GB in size.



■ Description:An Oracle restore would fail if there was an attempt to set the client readtimeout.

■ Additional Notes:RMAN failed with the following message:

RMAN-10002: ORACLE error: ORA-03113: end-of-file on communication

channel

The following message appears in the dbclient log:

(8) int_ReadData: WRN - Failed to set client read timeout

.




■ Description:The <guimenulabel>Custom Tabular</guimenulabel> report for a tape drivewould not display the Backup Exec data.



■ Description:A change was made to fix an issue that caused tar32 crashes after an importor verify job was canceled.



■ Description:On a Windows master server that was configured with NBAC, some executionpath would cause a process such as bpdbm to crash because of attempts to logthrough a closed file descriptor. This would trigger the Microsoft InvalidParameter handler. This issue would often occur at the end of the process.



■ Description:An incorrect fragment number would be entered in the image catalog for thetrue image restore (TIR) fragment in the following situation: - Multiple tapecopieswere being created (Inline Copy). - true image restore (TIR)was enabled.- An end ofmedia conditionwas encounteredwhile writing the backup headerfor the TIR fragment, and the TIR fragment was not written yet for othercopies. In this case, the subsequent copies would have a fragment number of-2 rather than -1. That would cause a failure to duplicate or restore from thiscopy.

■ Work around:In the image catalog, edit the image file to change the fragment line that hasthe -2 fragment number value to be -1.



154


■ Description:Because the cold catalog backup is obsolete a change was made to remove itsimplementation from nbsl andb proxy.



■ TITAN cases: 281-785-764 410-980-770


■ Description:Incremental backup would run as a full if the True ImageRestoreWithMoveDetection was set.



■ Description:If an Exchange 2010DAGbackup failed on a particular node and the preferredserver list is empty, select a different node to perform the backup with thenext attempt.



■ Description:Certain operations would fail on Windows Server 2008 when initiated fromthe system's console. A couple of examples are when you cancel certain typesof NetBackup jobs and starting a duplication operation with the preservemultiplexing option specified.Amessage similar to the followingwould appear in the debug log of the affectedprocess (often the admin or bpjobd debug log):

Could not open terminate event, ... or Could not open

MsgPendingEvent, ... or Could not set MsgPendingEvent, ...

■ Work around:If you encounter this issue, use aWindows remote desktop adminwindow thatis connected to aWindows Server 2008 system to initiate the failed operation.




■ Description:When a BMR-discovery is attempted for UNIX clients, the Discovery task doesnot get marked as completed even though the Discovery task is successful.

■ Work around:If you encounter this issue, clean the discovery task manually.



■ Description:Catalog recovery would fail from a copy if the copy was made to the same diskstorage unit as the original copy that had been expired.



■ Description:On Windows clients and servers:NetBackupclient andserver communicationwould fail to establish connections.The Vnetd and bpcd processes would fail to establish communication withrequesting services. The client backups would fail with a status 58. Mediaservers would go offline.The bpcd and vnetd logs on the Windows system would contain informationsimilar to the following:10038:An operation was attempted on something that is not a socket.

setsockopt failed: h_errno 10038network write() error: An operation

was attempted on something that is not a socket. ; socket = 360

■ Work around:If you encounter an issue like this, restart pbx_exchange, and restartNetBackup.



■ Description:Currently when bp_sts_copy_extent() returns STS_EBUSY, bpdm logs thefollowing: - A criticalmessagewhen called fromwithin copy_data_tir() - Anerror message when called from within copy_data()


156

The errors are misleading because the expected behavior is to retry thebp_sts_copy_extent call and not return an error.



■ Description:An invalid file list that contained multiple NEW_STREAM directives for amultistreamed Microsoft Windows policy can be scheduled to run toofrequently.

■ Work around:If you encounter this issue, fix the file list.



■ Description:A changewasmade to address an issue that caused the user-entered passwordto appear on the screen. That issuewould occurwhenyouattempted to changethedatabase password. If you typed apassword and thenpressed the backspacekey, the password that you entered would appear on the screen.



■ Description:For this release, a Relational database only restore option was added to thebprecover wizard.



■ TITAN cases: 411-311-539 411-809-340


■ Description:Master database restore would fail with a status 5 error in a multiple NIC(network interface card ) environment.




■ Description:While a report is emailed, if no view (history, ranking, etc.) is selected, thenan unknown reporting service exception occurs and is displayed.

■ Work around:If you encounter this issue, select a view before the email occurs.



■ Description:A change wasmade to ensure that the proper data is displayed in the AverageThroughput(KB/sec) column in the Client summary dashboard.



■ TITAN cases: 411-389-318


■ Description:The mounted partition with the NTFS volume mount points feature was notrestored correctly.


■ Contained in: NBLU_7.0.1.WIN NB_OPS_CTR_7.0.1.winnt.IA64NB_OPS_CTR_7.0.1.winnt.x64 NB_OPS_CTR_7.0.1.winnt.x86

■ Description:A change was made to ensure the heading displays the version on the log onpage of View builder.



■ Description:Added support for DB2 on Solaris_x86_10_64 platforms.



158


■ Description:An exported CSV/TSV tabular report had blank lines after every 100 rows.



■ TITAN cases: 240-954-648


■ Description:The extent flag VFM_EXT_HOLE_NULL was not processed at backup time. Therestore side has been changed to handle these extents.




■ Description:An enhancement was made to improve the Granular browse performance.



■ Description:A changewasmade to addVxMS libraries forHP Itaniumand SolarisOpteronplatforms.



■ TITAN cases: 410-825-352 411-456-139


■ Description:The nbemm thread latency and jobs would fail with an exit status 47 becausethere was no communication with nbemm.




■ Description:A change was made to address an issue that caused the nbsl memory usageto grow to more than 1GB.



■ Description:Restore jobs for UNIX/Linux clients have the following warning message inthe Detailed Status for the job in the Activity Monitor.read: unrecognized -J string spsrestoreoptions=0.

That warning message is also found in the Problems report after you run arestore to a UNIX/Linux client.

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



■ Description:Sorting on the server name did not work in the Job exit status detail report.



■ TITAN cases: 281-827-145 600-584-737


■ Description:An alternate client restore of a 1.2 TB, encrypted, SQL backup would fail withthe following SQL error.SQL Server cannot process this media family



■ TITAN cases: 240-983-030


160


■ Description:A change was made to address an issue that caused meaningless job IDs toappear in the Activity Monitor.



■ Description:The Cost Tabular report would not run for the Daily Occupancy Formula.



■ 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: - The DFSR backups that would cause files to be missing from thebrowse for restore. - Issueswere foundwith the backupofmultipleDFSR storesin that each had the same named subdirectory.



■ Description:The bpjava-susvc.exe process would crash if you closed the NetBackupConsole in NBAC mode.



■ Description:The VMware API has the ability to convert a thick provisioned disk to thinduring a restore but this was not exposed to the user.




■ Description:A changewasmade to address an issue that caused theTimeFinderMSCbackupto fail with the following error.Cannot stat /dev/rdsk/c1t5006048C5368EAA0d152s2. Errno = 2: No

such file or directory



■ Description:In custom reports, a selection of onemaster server would automatically selectall master servers when a new report was created.



■ TITAN cases: 411-529-043 411-686-900


■ Description:The database validationwould fail after anupgrade toNetBackup 7.0 occurred.

■ Additional Notes:For additional information about this issue, refer to the following Technoteon the Symantec Support Web site.http://entsupport.symantec.com/docs/347462.

■ Work around:If you encounter this issue, perform the following steps: 1. Shut down allNetBackupservices. 2. Start onlyNetBackupdatabase server. 3.Runnbdb_admin-validate -full



■ Description:The following error occurred in an NBAC-enabled mode for Vault_Operator,when Volume Pools was selected from the Tape summary reports.VxSS Authorization failed

■ Work around:


162

To resolve an issue like this, give Browse or Read permission on Storage Unitobject for Vault_Operator.



■ Description:Multiple copy job would hang or take a long time to complete if all the diskvolumes of a storage unit were down.



■ Description:Additional support has been added to the createDiskVolume API.



■ TITAN cases: 411-461-789 412-250-398


■ Description:A backup of a Microsoft Exchange 2007 CCR cluster would fail with an error69 when the cluster name was more than 12 characters long. MicrosoftWindows allows up to 15 characters in a computer name.



■ Description:A change was made to fix an issue that caused nbsl to core dump. This issueoccurred if you attempted to stop the NetBackup 7.0 services fromNetBackup-Java Administration Console on Windows.



■ Description:


In Oracle cloning, a pre-cloning error message of a previous pre-cloned checkwas not being cleared after a successful pre-cloned check was started.




■ Description:A change was made to address an issue that caused NBSL to crash. The issuewould occur if no devices were attached to the master server and all of theconnected media servers were down.



■ Description:A change was made to fix an issue that caused an Exchange VSS snapshotattempt to fail with a status 130. The following could be seen in the bpfis log:

10:10:55.562 [12184.15020] <2> onlfi_vfms_logf: INF - ERR -

ubsStart_eseutil():CreateFile() failed - 0x5.

■ Work around:If you encounter this issue, retry the Exchange VSS snapshot backup attempt.



■ Description:A change was made to ensure that you can redirect public folder items to newlocations.



■ TITAN cases: 281-795-539


■ Description:NetBackup would erroneously call vcbvmname and re-create a cache file thatcaused wasted resources.



164


■ TITAN cases: 411-146-558 412-019-951 600-565-972


■ Description:A change was made to address an issue that caused the nbpem process hangand eventually core dump.



■ Description:TheDeduplicationSizeSavings reportwouldnot include the isDeduped fieldcondition.



■ Description:If the request to get the job ID (jobid) fails because of a disk full condition,the nbpem process may crash.



■ Description:Thebpretlevel commanddidnot change the retention levelwheni,infinite,or infinity was used. In addition, no warning was given to indicate thatretention-level change did not occur.


■ TITAN cases: 412-159-362


■ Description:Backups of an Enterprise Vault partition or Index location configured with aUNC path would fail with a status 69 error. The UNC path was similar to,\\system\C$\... or \\system\E$\..., with any drive letter share.


■ Work around:If you encounter this error, create the following two registry keys on the fileserver (from where the drive is shared):

HKEY_LOCAL_MACHINE\SOFTWARE\{Wow6432Node}\KVS\Enterprise Vault\

Install\FullVersion

HKEY_LOCAL_MACHINE\SOFTWARE\{Wow6432Node}\KVS\Enterprise Vault\Install\Version

Thenpopulate the keyswith the values from theEnterpriseVault server,whichis hosting the Partition or Index location.



■ Description:A change was made to add a Reachable field in DriveInfo and PathInfo.



■ Description:Some encryption-capable drives return multiple encryption descriptors, andin some cases this is not handled correctly. A change has beenmade to correctthis issue.



■ Description:A change was made to ensure that the Windows GUI NbDbAdmin.exe lists allthe database spaces that NetBackup has.



■ TITAN cases: 320-199-474


■ Description:Three-character, 3pc.conf entries from theDevice number can cause an issueif a vendor's device returns more than FFF LUNS (4095).Currently, NetBackup uses SCSI inquiry VPD page code 80 data, and a unitserial number as a unique identifier to correlate the disks to back up between


166

the client and the media server for Media Server Copy backups. When theSymmetrix device ID number is greater than or equal to 4K (4096), the serialnumber may not be unique anymore. And if the Symmetrix device ID numberis greater than 8K, the serial number may contain numeral ASCII characters,such as the pound sign (#). That can cause aMediaServerCopy backup failurebecause the portion of the serial number after the pound sign is interpretedas a comment of the entry in the 3pc.conf.This fix uses SCSI inquiry VPD page 83 data, with a device identifier that doesnot have the issues described. One requirement for this fix is that the SPC-2flagmust be consistently set to disable or enable for the Symmetrix ports thatare used on the client and themedia server. That is necessary because differentSPC-2 settings give a different page code 83 device identifier. In addition, thisfix is backward-compatiblewith using the SCSI inquiryVPDpage code 80 serialnumber in case a customer does not have any disks with a Symmetrix ID thatis greater than 4095.



■ Description:After a downgrade to NetBackup 7 GA, a report that was created and savedwith a Level 1 of view and view groups selected as a column would cause anexception.



■ Description:If you selectedDatabase andLogs components in the right pane of theRestoreGUI of an Exchange 2010 DAG Database with bracket [] characters in it, therestore failed.

■ Work around:To avoid this issue, select the entire Database name in left pane



■ TITAN cases: 281-826-050


■ Description:


The maximum number of partially full media settings were not working asexpected.

■ Work around:If you encounter this issue, configure all drives for the robot to have drivepaths to the same set of media servers.



■ TITAN cases: 240-758-574


■ Description:A fix was made to the FlashBackup SFR restore. A status 5 and 85 errorsoccurred. All files appeared to be restored, however, only the fileswith streamsattached and specific security attributes failed to restore correctly.

■ Work around:If you encounter this issue, remove the alternate data streams from the filesbefore back up.



■ Description:A parent job for a multistreaming policy with checkpoints enabled failed andwasmoved to an INCOMPLETE state alongwith the child jobs. The parent jobwas thenmoved to a DONE state because of a timing problem that was causedby multiple NBPEM and NBJM restarts. The children were left in theINCOMPLETE state. That caused a threading issue in NBPEM.



■ TITAN cases: 412-196-678


■ Description:Unnecessary delays of two to three seconds per image in bpm, bpdm, andbpduplicate would occur while resources were allocated for a backup orduplication. This canhave anegative affect on the overall systemperformance.


168



■ Description:The bpbkar32 process would crash onWindows 2003 platforms. A change hasbeen made to address this issue.



■ TITAN cases: 412-339-841


■ Description:Reports showcorrect data in theOpsCenter user interface butwhen the reportsthat are emailed show incorrect data.

■ Additional Notes:

Etrack Incident: 2063669 2024679 2057049 2014246 2073912 2038837 19934112030339 2052641


■ Description:A change was made to move the NetBackup build environment so it buildswith the latest BEDS SDK.



■ TITAN cases: 320-237-675 410-747-859 411-943-136


■ Description:In aMultipleVCandproxy environment, a failurewould occurwhen the proxycannot talk to one of the VC's in the environment.

■ Additional Notes:A registry entry called excludeVMservers canbeused to specify a list of serversto ignore. The servers are separated by commas with no spaces. That entry


shouldbe created in theveritas\NetBackup\Currentversion\Config\BACKUPkey.



■ TITAN cases: 411-207-941


■ Description:The column operation that was saved as NONE was set to AVERAGE whenthere was an attempt to edit a custom report.


■ Contained in: NBLU_7.0.1.UNIX NBLU_7.0.1.WIN NB_7.0.1.winnt.IA64NB_7.0.1.winnt.x64 NB_7.0.1.winnt.x86 NB_DRO_7.0.1

■ Description:Use of the VxBSAGetMultipleObjects() XBSA API call could create a restorejob with the incorrect parent job ID.



■ Description:This release adds support of new ACSLS 8.0 media types that include LTO5.



■ Description:With the latest fdisk version, the fdisk -lu output sequence is not alwaysin the proper sequential order. For example, the expected sequence would be"sda sdb sdc ..." but fdisk -lu shows the output as, "sda sdc sdb...".That issue caused bmrd to go to an infinite loop.

If you reboot of client it disappears and theBMRbackup is successful. However,because bmrd goes to infinite loop, the size of the logs continue to grow andfill the file system and may eventually cause the server to crash.



170


■ Description:TheDriveSummaryByStatus report on theMonitor>Overview/Homepage,would sometimes show incorrect data if a drive (or path) was unreachable. Ifa drive was unreachable, it would not appear in the report.

■ Additional Notes:The NetBackup master should also be at 7.0.1 level for this operation to work.Back-level serversmay show incorrect data if the drive (or path) is unreachableor disabled.



■ Description:Changes were made to address memory leaks in libVdb. The memory leakscaused nbproxy to grow.



■ TITAN cases: 411-409-080


■ Description:A passive server name for an Exchange CCR cluster may appear garbled ortruncated in thebpfis log thatwas executed on the activenode. If that occurredthen the backup may fail.



■ Description:A changewasmade to ensure that theNetBackup-JavaAdministrationConsolehas a mechanism to handle partial success.





■ Description:A Snapshot backup with IBM_DiskStorage_FlashCopy would fail on AIXplatforms if the primary storage stack had Storage Foundation (SF) in it.



■ TITAN cases: 411727256


■ **Description:The calendar schedule for recurring months did not work for a UNIX master.Data was not being retrieved.



■ TITAN cases: 220-692-380 240-990-863


■ Description:NDMP DirectCopy chooses a non-NDMP drive path when source VTL mediais read. This prevents a VTL DirectCopy from occurring.

■ Work around:To avoid this issue, use single-path, VTL drives.



■ Description:A change wasmade to ensure that the VM can be browsed if created under thehierarchy of vApp.



■ TITAN cases: 281-889-342


■ Description:


172

The function that logs an error message in the log file would cause a SIGSEGVand crash the Oracle backup process because of an argument mismatch.



■ TITAN cases: 410-656-444


■ Description:User is not able to search properly for files to restore using the Searchbackupoption in the Windows BAR GUI. When the user specifies the file name witha full path in Search folder edit box and performs a search it shows all filenames instead of the one that is specified in edit box in the right pane.



■ TITAN cases: 320-219-113


■ Description:When the user specifies the user name of a virtual machine server , and theuser name contains the characters \n, the back-end stores the two charactersas an escape character. That causes the functionality to fail. For example, aname such as, domain\netbackup would cause a failure.



■ Description:A changewasmade to correct an issue that caused PITRollback restore to fail.



■ Description:The bpnbaz -GetConfiguredHosts -all command completes with anOperation completed successfully message. However, theConfiguredHosts.nbac file is empty and the error was not reported.




■ Description:This release of NetBackup (7.0.1) includes an updated version of NBSU. Theversion number is version 1.4.

■ Additional Notes:TheNBSU1.4 utility contains support for IPv6network addressing. TheNBSU1.4 utility has been ported to the Linux platform.



■ Description:In the VMware Recovery wizard, if an ESX host was selected that was in aDatacenter inside a folder (rather than one defined at the top level of thevSphere VirtualCenter hierarchy), there were no Datacenter folders shown inthat drop-down field.

■ Work around:If you encounter this issue,move theVMto the desiredDatacenter folder afterit is recovered.



■ Description:Changes have been added in this release to support Solution Enabler version7.0 with an EMC_Timefinder_* FIM.



■ TITAN cases: 410-655-329


■ Description:This release contains enhancements aimed atwhatNetBackup should dowhenRMAN runs the "Automatic backup set F=failover" feature.




174

■ Description:The bmrprep process enables you to restore Windows 2008 SP2 clients with aWindows 2008 SP1 SRT, because the Windows 2008 SP2 Full OS image wasnot always readily available.



■ Description:The catalog name for the Hyper-V vhd file names were not being constructedcorrectly.



■ Description:In the Drives view, some columns were shown incorrectly if a drive (or path)wasdisabledorunreachable.Now, theMonitor>Drivesviewshows the currentdrive status and theManage>Drives view shows the drive configuration data.If a drive (or path) is unreachable or disabled, it is not shown in the Monitor> Drives view.

Etrack Incident: 2023878 2039278 2056847 2062887 2021015 1950960 1957915


■ Description:This release of NetBackup contains enhancements to PDDE.



■ Description:The NetBackup Job Manager (NBJM) would consistently crash after youdowngraded from NetBackup 6.5.6 to 6.5.5 when jobs that were run withNetBackup 6.5.6 were cleaned up by bpjobd. The same problem would occurbetween NetBackup 7.0.1 and 7.0.

■ Work around:If you encounter this issue, remove the contents of installpath/db/jobs/restart directory.




■ TITAN cases: 411-478-615


■ Description:A change was made to address an issue that caused NDMP backups to failswith a status 99 error on an AIX system.

■ Work around:If you encounter the issue, set the NDMP_DATA_CONNECTION_HOST_NAME in/usr/openv/netbackup/db/config/ndmp.cfg as its IP address. The NDMPagent uses the address to connect to a filer. For more information, see thefollowing Technote on the Symantec Support Web site.http://entsupport.symantec.com/docs/294554



■ Description:A changewasmade to address an issue that caused the archive data collectionto fail for Enterprise Vault 8.0.



■ TITAN cases: 281-619-629 412-036-438


■ Description:Large SAP restores were incorrectly reported as failures in the brrestore log.



■ Description:Snapshot Client has a requirement to specify information about all the targetdevices in a policy. This target-device information can be very large. It waspossible that this information could be so large that someNetBackupmoduleswould truncate the information because of buffer limitations.


176

Changes have been made to the NetBackup modules to allow a large policyconfiguration to pass without being truncated.



■ Description:A change was added to address an issue that caused bpcd, vnetd, vmd, andtldcd to core dump during an upgrade from NetBackup 7.0 NetBackup 7.0.1.



■ Description:A change was made to address a status 41 Network connection failed errorforExchangeVSSbackups inExchange configurations thathavea largenumberof storage groups and databases.

■ Work around:If you encounter this status error, increase the client connect timeout to avalue that is large enough to accommodate the time that it takes for thesnapshot creation to complete. This time is dependent on the user's Exchangeenvironment.



■ TITAN cases: 230-708-303


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



■ Description:The All Local Drives nongranular full backup would fail with a status 83,always use client side deduplication.

■ Additional Notes:


Added a call to ignoreBPConfServerListmethod in connectProxyServer()

to bypass the NetBackup client server name check in the bp.conf file.

■ Work around:If you encounter this issue, add theNetBackup client server name to the bp.conffile.



■ Description:When a client in a policy is offline, the PEM log did not contain the followingmessage that shows when the client will be online:PCT for policy P, client C will go online at time



■ Description:A changewasmade to address an issue that cause nbsl to have a highmemoryusage.



■ TITAN cases: 281-745-720


■ Description:A tape that was marked as IN_TRANSIT would cause a vault eject error 224(final status 288) and an incorrect Robot Pick List report.



■ TITAN cases: 320-228-566


■ Description:Implement client-side encryption on a Tru64 5.1B client that has NetBackup6.5.3 installed.


178

Unencrypted backups are successful, but as soon as encryption was enabled,the backup job failed with an Operation would block error in bpbkar.



■ TITAN cases: 281-858-481


■ Description:Standard UNIX file metadata (such as permissions, owner, group) would notget restored on aMacOSX10.5 platformwhen you attempted to restore acrosshardware platforms (PowerPC to or from x86). This was caused by anincompatibility between platforms for the HFS attributes.This 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:If a duplication was improperly attempted from the snapshot copy (copy one)of an instant recovery backup, the duplicationwould fail with status 191. Thatwould occur after the job details similar to the following were emitted.Error bpdm(pid=496) cannot open file /C\narc_1274728321, No such

file or directory

■ Work around:Duplication from an instant recovery snapshot copy is not supported unlessthe instant recovery schedule options include the following: instant recovery

snapshots and copy snapshots to a storage unit

Theduplication source of this type of snapshot-enabled policy should bemadefrom a second copy. The first copy cannot be a source of a duplication.



■ TITAN cases: 411-478-830


■ Description:


The nbevtmgr would not run if the client port windows was configured on aWindows 2008 platform.



■ Description:For multiple copy jobs, if one multiple copy job failed, then some other copieswhose storage unit is in use would eventually be dropped as well.



■ Description:This release contains the enhancements that disambiguate the status 800 errorcodes.



■ TITAN cases: 411-691-762


■ Description:Add the ability to display EMM's deleted media table by the nbemmcmd.



■ Description:A change was made to address an issue that cause an EMC Timefinder_snap

backup to fail when it was run on fast system.



■ Description:A change was added to address an issue that cause nbsl to core dump.



180


■ Description:Duplication jobs that were submitted by SLP's would not have the correctpolicy name. In addition, the SLP-submitted duplication jobswould not respectthe MAX_KB_SIZE_PER_DUPLICATON_JOB limit within bpduplicate.



■ TITAN cases: 410-630-281


■ Description:A large EMM_AllocationStatus tablewould cause delays in resource allocation.A change was made for EMM to automatically prune the table.

■ Additional Notes:You can use the nbemmcmd -errorsdb command to view the media and driveallocation errors.By default, NBEMM automatically purges the AllocationStatus entries thatare older than 45 days.If youwould like to keep the older entries formore or less time, youmust keepa value that specifies the number of days that they should be kept in thefollowing master server configuration file: - On UNIX use,/usr/openv/var/global/emm.conf - On Windows use a corresponding path.For example, to keep these records for 90 days instead of the default 45,perform the following command:ALLOC_STATUS_KEEPTIME_DAYS = 90

■ Work around:If you encounter an issue like this, use the nemmcmd -errorsdb -prune

command to manually prune the EMM_AllocationStatus table.



■ TITAN cases: 220-692-308


■ Description:


An Exchange off-host instant recovery backup would fail with a status 130 iftheNetBackup installation directorywas different on the alternate client fromthe primary client.



■ Description:A change was made to ensure that the CSV Import for a view creation yieldsthe correct view.



■ Description:bpadm terminates with a signal 11, Segmentation fault, when the file list of apolicy wasmodified. That occurred if the user deletedmore entries than whatexisted in the policy's file list.

■ Work around:If you encounter this issue, use the Delete Files menu selection to delete thefile list entries rather than the Modify Files List menu selection.




■ Description:A backup would fail if a nonstandard SSL port was used for a VMWare server.



■ Description:A changewasmade to correct an issue that caused a SANClient job to fail witha PipeID=32 error.

■ Work around:An FT media server can support up to 32 pipes. You should configure it to usemaximum of 31 pipes. You can set the value in the user interface.




182

■ TITAN cases: 312-190-408


■ Description:A changewasmade to ensure that theTDP SQLBackTrackdata is being reported.

■ Additional Notes:The OpsCenter agent did not recognize the SQL BackTrack jobs from TSMserver, and the jobs were not being gathered.



■ Description:The View Automation in View Builder was extremely slow and seemed tofreeze or stall the application.



■ 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:This release adds support for Enterprise Vault 9.0 in NetBackup.



■ TITAN cases: 220-706-580 412-358-258



■ Description:The Vault name and the profile name are missing in Job overview tab in theJob details for vault jobs on the NetBackup Administration Console.



■ Description:An Exchange 2010DAG restore of a database or granular data, would performresolution on the destination server name to find the appropriate active serverof a database or a CAS server.



■ Description:Added the keep alive capability to bpexpdate to ensure that the image resultset does not expire while the current batch of requested images is processed.


■ TITAN cases: 411-341-073


■ Description:The bpexpdate process may terminate with an incorrect exit status.



■ TITAN cases: 320-174-136


■ Description:A change was made to allow details to be configured for more than 50 file listentries.

■ Work around:The default is 50, however you can use the following command to increase itto a maximum of 1000:MAXFILELIST_ALLOWED_FOR_DISPLAY = n



184


■ Description:The Week At A Glance report fails to export and email in HTML format.

■ Work around:If you encounter this issue, you can export or email the Week At A Glancereport in CSV format.



■ Description:During a backup of a client-side deduplication enabled policy, the extendedclient file attributes would cause nbostpxy to stop if the length of theNetBackup metadata that identified these attributes exceeded 257KB.



■ Description:Checkpointed jobs that were resumed failed to be allocated resources byMDS.

■ Work around:Restarting the EMM service may help you avoid this issue.



■ TITAN cases: 281-756-782


■ Description:A changewasmade to enforce themax_partially_full_media limit formultiplecopy jobs.

■ Additional Notes:The max partially full media limit is not enforced to be less than the numberof configured copies for a job. So if the max partially full media limit isconfigured at one for a pool, and the pool is used in a two-copy job, the limitis enforced at "2" for that job.




■ Description:Snapshot was not cleaned up after an Exchange recovery. This would leave anincomplete backup image copy in the NetBackup catalog, in addition to one ormore snapshot volumes on the client.

■ The problem would occur under the following conditions:

■ MS-Exchange InstantRecoverybackupwasperformedusing theVSSsystemprovider.

■ Exchange database was on one volume, transaction logs on another.

■ Recovery used the "roll forward" option, which prevents the log volumefrom being rolled back.

■ Work aroundIf you encounter this issue, use the NetBackup Administration Console toexpire the snapshot copy of the backup image.




■ Description:Could not create an APP_CLUSTER storage unit that used AdvancedDisk.



■ Description:Disk pool creation can fail with multiple network interfaces on the mediaserver.

■ Work aroundIf you encounter this issue, remove one of the interfaces.




■ Description:


186

A change was made to correct an issue that caused a 219 error to occur if theOverride policy storage selections was used and the override specified SLP.




■ Description:The Shared Services title would come across toManaged code as blank duringthe restore. A change was made to add a supported procedure in restoringSharedServices_DB (SSP Components).



■ Description:Disk space was not reclaimed when MSDP was used.



■ Description:Restore of individual email messages from Granular Recovery Technology(GRT)-enabled Exchange Information Store backup sets that use NetBackup7.0 failed. The failure would occur if the Exchange Client Access Server hasSecure Socket Layer (SSL) certificates installed.




■ Description:The current implementation of the bprestore -copy option requires that thespecified copy exists for all images that match the search criteria used for therestore (client, date range, etc.)This has led to confusion over the usage of the option. Users attempt to restoreusing the bprestore -copy option to restore from an alternate copy (not theprimary copy) of an image, but end up with a status 147, copy not found. Theuser is confused because the image of interest does have the specified copy,but other images that happen to match the date range, etc, search criteria donot, resulting in the 147 error.


This change modifies the behavior of the bprestore -copy alternate restorecopy number option from a "must use" to a "use if able" model. If the specifiedalternate copy number does exist, it will be used. However, if it does not exist,then theprimary copy for the imagewill be used. Since, by definition, all imageshave a primary copy this eliminates the 147 error seen in the above scenario.

■ Work around:Specify a date range or other search criteria (policy, etc.) that limit the resultset of images to only those that do have the specified alternate restore copynumber.

Etrack Incident:


■ Description:DR restores of Windows machines result in a non-bootable system.The following Status 1 restore job message appears in the Activity Monitor:

WRN - error writing object: System State:\Registry\Registry

WRN - error writing byte: 478720

WRN - desired byte count: 65536

WRN - actual byte count: 48936

The following appears in the client TAR log:

INF - Status FS_EXTENDED_ERROR (0xE000FEA9) writing

Component Registry BrUtil object stream 0x4C494645 in

SHADOW::WriteComponent

INF - AD:Status FS_EXTENDED_ERROR (0xE000FEA9) calling

FS_WriteObj in SystemState::WriteObj:226

ERR - beds_ss_access::V_Write FS_EXTENDED_ERROR on

FS_WriteObj() Result:0xE000030E Action:0x1 Error_id:0x3E88

ERR - beds_ss_access::V_Write:FS_WriteObj() Failed!

0xE000030E:Unable to swap out active registry hive with new data.

■ Additional Notes:The first boot after a full OS restore of Windows 2008 or Windows 2008 R2may take 5 to 10 minutes or longer. It may show a blank screen during thistime. The machine is not hung. Do not reboot forcefully during this time,because it may corrupt the OS and cause it not to boot. The slow boot occursbecause of a bulk file-rename for files which were restored with temporaryfile names because their production counterparts were active and locked atthe time of the restore. This also happens with Windows 2003, however the


188

file-set is much smaller and the time it takes to boot is much shorter induration.

■ Work around:If you encounter this issue, refer to the following Technote on the SymantecSupport Web site:http://entsupport.symantec.com/docs/351886




■ Description:The NetBackup-Java Administration console did not show the Limit I/OStreams option in the Change Disk Pooldialog. Select the following to get tothis dialog: Media andDeviceManagement > Devices > Diskpools > ChangeDisk Pool. The issue is visible only on NetBackup 7.0, and not on NetBackup7.0.1 or 6.5.5 and above.The Change button usually present under the Storage Servers panel was notvisible on the same dialog.




■ Description:Failed to create the SRT for a system with RHEL 4 update 8 installed.RHEL 4 update 8 contained the string "Red Hat Enterprise Linux 4.8". Inthe createsrt.conf file the entry, RHEL-4 has the following string, "Red Hat

Enterprise Linux 4". This caused the load media to fail with the followingerror:The loaded media is not correct.



■ Description:A restore of emails produced a successful report, however the emails were notrestored.Log message:


[1af4] 05/27/10 13:08:38 DBG - returning true for

SslPolicyErrors [1af4] 05/27/10 13:08:38 Exception in Commit

The extended property attribute combination is invalid.

[1 of4] 05/27/10 13:08:38 Exception in RTFsync The extended

property attribute combination is invalid.



■ Description:A change was made to address an issue that caused intermittent failure tooccur with GRT backups.

■ Additional Notes:Some versions of NFS behavior regarding file pre-allocation changed. A fixwas added to address those changes.



■ Description:An issue was fixed that caused the PostgreSQL database that PDDE uses wasnot locked down, so it could be accessed by users from different computersand possibly without credentials. This affected new PDDE configurations inNetBackup 7.0. If PDDE has already been configured, the installation ofNetBackup 7.0.1 or any other update does not fix this issue. After aconfiguration, you must perform the fix manually or you can delete the PDDEstorage server and reconfigure it.

■ Work Around:If PDDE has already been configured,modifyDB_PATH\databases\pddb\data\pg_hba.confandchange the followingfrom:

host all all 0.0.0.0/0 trust

host all all ::/0 trust

To:

host all all 0.0.0.0/0 md5

host all all ::/0 md5

Next, modifyDB_PATH\databases\pddb\data\postgresql.conf and changethe following from:


190

listen_addresses = '*'

To the following:

#listen_addresses = 'localhost'

And then restart the PostgreSQL Server 8.3 service.



192

Documents

NB 701 Release Notes