NB 7507 Release Notes

Symantec NetBackup™7.5.0.7 Release Notes

NetBackup 7.5.0.7

Maintenance Release Update

Document Version 1

Symantec NetBackup™ 7.5.0.7 Release NotesDocumentation version: 7.5.0.7

Legal NoticeCopyright © 2013 Symantec Corporation. All rights reserved.

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

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

THE DOCUMENTATION IS PROVIDED "AS IS" AND ALL EXPRESS OR IMPLIEDCONDITIONS, REPRESENTATIONS AND WARRANTIES, INCLUDING ANY IMPLIEDWARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE ORNON-INFRINGEMENT, ARE DISCLAIMED, EXCEPT TO THE EXTENT THAT SUCHDISCLAIMERSAREHELD TOBE LEGALLY INVALID. SYMANTECCORPORATIONSHALLNOT BE LIABLE FOR INCIDENTAL OR CONSEQUENTIAL DAMAGES IN CONNECTIONWITH THE FURNISHING, PERFORMANCE, OR USE OF THIS DOCUMENTATION. THEINFORMATION CONTAINED IN THIS DOCUMENTATION IS SUBJECT TO CHANGEWITHOUT NOTICE.

Symantec Corporation350 Ellis StreetMountain View, CA 94043

http://www.symantec.com

http://www.symantec.com

Technical SupportSymantec Technical Support maintains support centers globally. Technical Support’sprimary role is to respond to specific queries about product features and functionality.The Technical Support group also creates content for our online Knowledge Base.The Technical Support group works collaboratively with the other functional areaswithin Symantec to answer your questions in a timely fashion. For example, theTechnical Support group works with Product Engineering and Symantec SecurityResponse to provide alerting services and virus definition updates.

Symantec’s support offerings include the following:

■ A range of support options that give you the flexibility to select the right amountof 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 website atthe 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.

About Symantec Operations Readiness ToolsSymantec Operations Readiness Tools (SORT) is a set of web-based tools thatsupports Symantec enterprise products. For NetBackup, SORT provides the abilityto collect, analyze, and report on host configurations across UNIX/Linux or Windowsenvironments. This data helps to assess whether your systems are ready for aninitial NetBackup installation or for an upgrade from your current version.

To access SORT, go to the following webpage:

https://sort.symantec.com/netbackup

Once you get to the SORT page, more information is available as follows:

■ Installation and Upgrade ChecklistUse this tool to create a checklist to see if your system is ready for a NetBackupinstallation or an upgrade.



■ Hot fix and EEB Release AuditorUse this tool to find out whether a release that you plan to install contains thehot fixes that you need.

■ Custom ReportsUse this tool to get recommendations for your system and Symantec enterpriseproducts, tips for risk assessment, and product license tracking.

■ NetBackup Future Platform and Feature PlansUse this tool to get information about what items Symantec intends to replacewith newer and improved functionality, and what items Symantec intends todiscontinue without replacement. Some of these items include certain NetBackupfeatures, functionality, 3rd-party product integration, Symantec productintegration, applications, databases, and the OS platforms.

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 be atthe computer on which the problem occurred, 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 your Symantec product requires registration or a license key, 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, DVDs, or manuals

Support agreement resourcesIf you want 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 ............................................................................................... 3

Chapter 1 New features and enhancements ...................................... 8

About the NetBackup 7.5.0.7 release ................................................. 8About NetBackup 7.5.0.7 new features and enhancements ..................... 9NetBackup 7.5.0.7 new enhancements and support .............................. 9

Chapter 2 Platform compatibility ....................................................... 10

About upgrade paths to the NetBackup 7.6 line of releases ................... 10About NetBackup 7.5.0.x release compatibility ................................... 11

About software release types .................................................... 12About compatibility with NetBackup 7.5 ....................................... 12

NetBackup compatibility lists ........................................................... 14

Chapter 3 Product dependencies ....................................................... 17

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

Chapter 4 Operational notes ............................................................... 26

About NetBackup 7.5.0.7 operational notes ....................................... 26Installation and upgrade notes ........................................................ 27General NetBackup 7.5.0.7 notes .................................................... 28Bare Metal Restore notes ............................................................... 30Cloud storage notes ...................................................................... 31Database and application agent notes .............................................. 32

Creating a minimal NetBackup account for Exchange operations(Exchange 2010 and 2013) ................................................ 34

Deduplication notes ...................................................................... 35Seeding the fingerprint cache for MSDP ...................................... 35About upgrading MSDP and PureDisk deduplication solutions to

resolve case sensitivity issues ............................................. 36NetBackup OpsCenter notes .......................................................... 40NetBackup Search notes ............................................................... 44

About upgrading Search to NetBackup 7.5.0.x .............................. 44Virtualization notes ....................................................................... 44

Contents

Chapter 5 End-of-life notifications ..................................................... 52

About future NetBackup end-of-life notifications .................................. 52

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

About NetBackup release content .................................................... 54About release content conventions ............................................. 54

NetBackup 7.5.0.7 release content ................................................... 55NetBackup 7.5.0.7 Emergency Engineering Binary (EEB) listing ............ 58

7Contents

New features andenhancements

This chapter includes the following topics:

■ About the NetBackup 7.5.0.7 release

■ About NetBackup 7.5.0.7 new features and enhancements

■ NetBackup 7.5.0.7 new enhancements and support

About the NetBackup 7.5.0.7 releaseNetBackup 7.5.0.7 represents the final release that introduces new features andenhancements to NetBackup 7.5. All future customer-requested defect fixes forversion 7.5 will be addressed in a newer line of NetBackup releases, such as version7.6.x.x.

Symantec recommends that customers upgrade their NetBackup 7.5 environmentsto version 7.5.0.7 to take advantage of the latest product fixes and enhancements.However, NetBackup customers that plan to upgrade to version 7.6 should reviewtheir upgrade path options before they install version 7.5.0.7.

See “About upgrade paths to the NetBackup 7.6 line of releases” on page 10.

NetBackup Late Breaking NewsFor the most recent NetBackup news and announcements, visit the NetBackupLate Breaking News website at the following location:

http://www.symantec.com/docs/TECH74904

Other NetBackup-specific information can be found at the following location:

go.symantec.com/nb

1Chapter


go.symantec.com/nb

About NetBackup 7.5.0.7 new features andenhancements

In addition to a small number of new features, NetBackup 7.5.0.7 offers manyenhancements to the issues and improvements from previous NetBackup releases.Information about the new features and enhancements in this release of NetBackupcan be found in the following sections of this chapter.

This release incorporates fixes to several known issues that existed with NetBackup.Many of these issues pertain to the customer-specific issues that have beendocumented in the form of Titan or Salesforce.com (SFDC) cases. Many of thefixes that are incorporated into this release are available as individual engineeringbinaries and engineering bundles (EEBs). These EEBs were created to addressspecific customer issues with a previous version of NetBackup. This maintenancerelease document lists those engineering binaries and bundles.

See “NetBackup 7.5.0.7 release content” on page 55.

See “NetBackup 7.5.0.7 Emergency Engineering Binary (EEB) listing” on page 58.

NetBackup 7.5.0.7 new enhancements and supportThe NetBackup 7.5.0.7 release offers the following new enhancements and support:

■ Support for VMware Virtual Disk Development Kit (VDDK) 5.1 Update 1

■ Upgrade to Java Runtime Environment (JRE) 7

9New features and enhancementsAbout NetBackup 7.5.0.7 new features and enhancements

Platform compatibility


■ About upgrade paths to the NetBackup 7.6 line of releases

■ About NetBackup 7.5.0.x release compatibility

■ NetBackup compatibility lists

About upgrade paths to the NetBackup 7.6 line ofreleases

Note: If you do not plan to upgrade your NetBackup environment to version 7.6within the first half of calendar year 2014, you can safely ignore this topic.Additionally, if you are running NetBackup 7.5 and do not plan to upgrade to version7.6 within the first half of calendar year 2014, Symantec recommends that youupgrade to version 7.5.0.7 to take advantage of the latest bug fixes and compatibilityfeatures.

For more information about the NetBackup 7.6 GA release: See the section called“About NetBackup 7.6.0.1” on page 11.

Upgrades to NetBackup 7.6 are supported from any release since NetBackup 6.0.However, some of the functionality that was introduced in NetBackup 7.5.0.6 andlater is not present in the NetBackup 7.6 GA release. The difference in functionalityis limited to bug fixes and a small set of features. The following list describes thevarious upgrade paths that Symantec recommends:

■ If you are currently running NetBackup 7.5.0.5 or earlier, your upgrade path isto NetBackup 7.6 GA.

2Chapter

■ If you are currently running NetBackup 7.5.0.6 and you do not use Amazon S3cloud storage buckets in regions other than US Standard, your upgrade path isto 7.6 GA.

■ If you upgrade to NetBackup 7.5.0.7 or you are currently running version 7.5.0.6with Amazon S3 cloud storage buckets in regions other than US Standard, yourupgrade path is to a release in the NetBackup 7.6 maintenance line (triple-dot)available in the first half of calendar year 2014.

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


Upgrades from NetBackup 7.5.0.6If your NetBackup environment relies on any of the following functionality that isfound in version 7.5.0.6 and later, then your upgrade path is to a release in theNetBackup 7.6 maintenance line (triple-dot):

■ Amazon S3 cloud storage buckets in regions other than US StandardSee “Cloud storage notes” on page 31.

Installing or Upgrading from NetBackup 7.5.0.7If you do not plan to upgrade your NetBackup 7.5 environment to version 7.6 withinthe first half of calendar year 2014, Symantec recommends that you install the7.5.0.7 maintenance release to ensure that your environment has the latest bugfixes and compatibility features.

If your plan is to upgrade to NetBackup 7.6 GA within the first half of calendar year2014, then Symantec recommends that you do not install the NetBackup 7.5.0.7maintenance release.

About NetBackup 7.5.0.x release compatibilityThis release supports the platforms and binary sizes that were documented in theNetBackup 7.5 Release Notes document.

For more information about platform compatibility, refer to the following documentsavailable from the Symantec Support website:

11Platform compatibilityAbout NetBackup 7.5.0.x release compatibility


■ NetBackup 7.5 Release Noteshttp://www.symantec.com/docs/DOC5332

■ NetBackup Enterprise Server and Server 7.x OS Software Compatibility Listhttp://www.symantec.com/docs/TECH59978

About software release typesSymantec maintains a policy by which NetBackup can deliver various levels ofreleases to accommodate customer needs. The following list defines the variousrelease types and the version number schemes that are associated with each type.The NetBackup family of software and appliance products use these release typesand number schemes.

■ A major release is the first in a series of releases. This type of release containsnew features, new supported platforms, and a complete set of the latest productdocumentation.

■ Aminor release is a single-dot release that follows a major release, for example2.5 or 7.5. This release type contains much of the same requirements as a majorrelease. It contains a smaller set of new features and enhancements, anyplatform proliferation, and a complete set of updated documentation.

■ A software release update is a double-dot release, for example 2.5.1 or 7.5.1.This release type may contain a few new features and enhancements as wellas many product fixes. Only those documents that are applicable to the newfeatures or enhancements are updated and republished.

■ A maintenance release update is a triple-dot release, for example 2.5.0.1 or7.5.0.1. This release type is primarily comprised of a number of fixes that aredeveloped to address issues in major, minor, and software update releases.This release type may also include a small number of new features,enhancements, and platform or application proliferations. The only documentationthat is provided is an online Readme and a release notes document that isavailable on the Symantec Support website.

Note: NetBackup versions 2.5.0.1, 2.5.1, and 7.5.1 are used in this topic asexamples. These versions of NetBackup do not exist at the time of this document'spublication.

About compatibility with NetBackup 7.5Symantec NetBackup has always maintained that the master server within anenvironment must be at a version level that is equal to or greater than the versionlevels of the media servers and clients within that environment. Symantec


http://www.symantec.com/docs/DOC5332


recommends that you keep your entire NetBackup environment up-to-date with thelatest maintenance (triple-dot) releases. However, NetBackup offers the flexibilityof an environment where the clients and the media servers are running a differenttriple-dot release than the master server. For example you can upgrade a mediaserver or client to version 7.5.0.1 in an environment where the master server isrunning version 7.5. This same scenario applies to double-dot releases. For exampleyou can upgrade a media server or client to version 7.5.1.1 in an environment wherethe master server is running version 7.5.1.

Since the NetBackup catalog resides on the master server, the master server isconsidered to be the client for a catalog backup. If your NetBackup configurationincludes a media server, it must use the same NetBackup version as the masterserver to perform a catalog backup. See the NetBackup Installation Guide forinformation about mixed version support.

See “About software release types” on page 12.

For information about NetBackup compatibility with the NetBackup appliances, seethe following tech note on the Symantec Support website:


Symantec NetBackup does not support any scenario where a minor release orsoftware release update is at a higher version level than the parent server. Forinstance, the following examples apply:

■ If a master server is at 7.5, then the media servers and clients cannot be at asingle-dot version level that is higher than 7.5, such as 7.6.

■ If a master server is at 7.5, then the media servers and client servers cannot beat a double-dot version level that is higher than 7.5, such as 7.5.1.

■ If a master server is at 7.5.1, then the media servers and clients cannot be at adouble-dot version level that is higher than 7.5.1, such as 7.5.2.

Note: NetBackup versions 7.5.1, 7.5.1.1, 7.5.2, and 7.6 are used in this topic asexamples. These versions of NetBackup do not exist at the time of this document'spublication.

The following table shows the various compatibility schemes that are supportedwith the current NetBackup 7.5 product line.

Table 2-1 NetBackup release compatibility for the 7.5 product line

NetBackup clientNetBackup mediaserver

NetBackup masterserver

7.07.07.5



Table 2-1 NetBackup release compatibility for the 7.5 product line (continued)

NetBackup clientNetBackup mediaserver

NetBackup masterserver

7.0, 7.0.17.0.17.5

7.0, 7.0.1, 7.1, 7.1.0.x7.17.5

7.0, 7.0.1, 7.1, 7.1.0.x7.1.0.17.5

7.0, 7.0.1, 7.1, 7.1.0.x7.1.0.27.5

7.0, 7.0.1, 7.1, 7.1.0.x7.1.0.37.5

7.0, 7.0.1, 7.1, 7.1.0.x7.1.0.47.5

7.0, 7.0.1, 7.1, 7.1.0.x, 7.5, 7.5.0.x7.57.5

7.0, 7.0.1, 7.1, 7.1.0.x, 7.5, 7.5.0.x7.5.0.17.5

Note: NetBackup 7.5.0.2 is the versionthat the NetBackup Appliance 2.5software release is based on. NetBackup7.5.0.2 is not a standalone version ofNetBackup.

7.5.0.27.5

7.0, 7.0.1, 7.1, 7.1.0.x, 7.5, 7.5.0.x7.5.0.37.5

7.0, 7.0.1, 7.1, 7.1.0.x, 7.5, 7.5.0.x7.5.0.47.5

7.0, 7.0.1, 7.1, 7.1.0.x, 7.5, 7.5.0.x7.5.0.57.5

7.0, 7.0.1, 7.1, 7.1.0.x, 7.5, 7.5.0.x7.5.0.67.5

7.0, 7.0.1, 7.1, 7.1.0.x, 7.5, 7.5.0.x7.5.0.77.5

Note: Support for the NetBackup 6.x product line has ended as of October, 2012.

NetBackup compatibility listsThe most up-to-date compatibility information on platforms, peripherals, drives, andlibraries is located in various compatibility lists on the Symantec Support website.You can use the following methods to locate these lists and information:

■ Symantec recommends that you use Symantec Operations Readiness Tools(SORT) to help you locate the latest platforms, peripherals, drives, and libraries.To access SORT, go to the following URL:

14Platform compatibilityNetBackup compatibility lists

https://sort.symantec.com/netbackupFor NetBackup, SORT provides an Installation and Upgrade Checklist reportas well as the ability to collect, analyze, and report on host configurations acrossUNIX/Linux or Windows environments. In addition, you can determine in whatrelease whether any hot fixes or EEBs you have installed are fixed. You canuse this data to assess whether your systems are ready to install or upgrade tothis release.

■ If you want to view a specific compatibility list, you can find links to each list thatis posted on the Symantec Support website:http://www.symantec.com/docs/TECH59978 - NetBackup Master CompatibilityList

The following items describe each of the compatibility lists that are available.

■ NetBackup Enterprise Server and Server 7.x Hardware Compatibility ListThis list includes information for compatible drives, libraries, virtual tapedevices, robot-types, fibre-channel HBAs, switches, routers, bridges, iSCSIconfigurations, and encryption devices. Other compatibility informationincludes the following:

■ NetBackup appliances

■ AdvancedDisk arrays

■ OpenStorage (OST) solutions

■ Tape drives

■ Fibre Transport media server host bus adapters (HBAs)

■ Virtual tape libraries (VTLs)

■ Network Data Management Protocol (NDMP) devices

■ Tape libraries

■ Encryption and security solutions

■ NetBackup 7.x Database and Application Agent Compatibility ListThis list contains the most current compatibility information for the databaseagents and application agents that are supported on specific operatingsystems and CPU architectures.

■ NetBackup 7.x Snapshot Client Compatibility ListThis list contains the most current server and client snapshot compatibilityinformation sorted arrays, agents, operating systems, and VSS providers.

■ NetBackup 7.x Cluster Compatibility List




This list contains the most current compatibility information for the clustertypes and versions that are supported on specific operating systems andCPU architectures.

■ Statement of support for the importing of Backup Exec images in NetBackup7.x using the Backup Exec Tape Reader

■ Support for NetBackup 7.x in virtual environmentsThis list contains the most current compatibility information for NetBackupin virtual environments.


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 all ofthe latest patches and upgrades before you install NetBackup. This section is aguide to inform you of the operating systems that require a minimum patch level.For more extensive information about NetBackup compatibility including compatibleoperating systems, applications, and hardware, see the NetBackup MasterCompatibility List on the Symantec Support website.


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

Table 3-1 Operating system patches and updates for NetBackup

NotesPatchOperating system typeand version

You may need to restart after changing to version9.0.0.3.

AIX runtime libraries 8.0.0.10 or9.0.0.3 or later

AIX 5.3

For the xlC.rte 8.0.0.10 fileset, you may needto install the IY91284 fix to avoid a potential issuewhen creating or updating the NetBackup database.The IY91284 fix is part of Maintenance Level 6.

xlC.rte 8.0.0.10 fileset

3Chapter


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


NetBackup 7.5 requires the AIX 5.3 TL12 SP2(5300-12- 02-1036) Maintenance Pack as aminimum.(Higher patch levels should also work.)

You can use the oslevel -s command to verifywhat Maintenance Pack level you have installed.

AIX 5.3 TL12 SP2 (5300-12-02-1036)

NetBackup 7.5 requires the AIX 6.1 TL5 SP2(6100-05-02-1034) Maintenance Pack as a minimum.(Higher patch levels should also work.)

You can use the oslevel -s command to verifywhat Maintenance Pack level you have installed.

AIX 6.1 TL5 SP2(6100-05-02-1034)

AIX 6.1

The runtime libraries need to be at 9.0.0.3 or later.You may need to restart after you change to version9.0.0.3.

AIX runtime libraries 9.0.0.3 orlater

If you install AT on an HP-UX platform, this patch isrequired.

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

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

18Product dependenciesOperating system patches and updates



For HP-UX PA-RISC platforms, this fileset is required:Networking.NET-RUN:/usr/lib/libipv6.sl

HP-UX PA-RISC

For HP-UX PA-RISC platforms, this fileset is required:Networking.NET-RUN-64:/usr/lib/pa20_64/libipv6.1

For HP-UX PA-RISC platforms, this fileset is required:Networking.NET-RUN-64:/usr/lib/pa20_64/libipv6.sl

For HP-UX PA-RISC platforms, this fileset is required: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 corein PA32

■ QXCR1000589142: dld crash inLL_new_descendent_list when the aCC applicationis exiting.


■ QXCR1000746161: dlsym() hangs■ QXCR1000593999: dld emits assert messages

for chatr +mem_check enabled 64-bitexecutables

PHSS_37516

This patch is necessary to enable any C++ runtimecode to work properly.

PHSS_26946

This patch is a libc cumulative patch.PHSS_27740

This patch contains a linker tools cumulative patch.PHSS_26560

That is a recommended critical patch from HP that isrequired for successful NetBackup client backups.

PHSS_32864

This patch enables HP-UX 11.11 mmap() to uselarge files from 2GB to 4GB.

PHKL_26233




That is a recommended critical patch from HP that isrequired for successful NetBackup client backups.

PHSS_35379

That is a recommended critical patch from HP that isrequired for NetBackup to use VxSS.

PHCO_29029

Allow POLL_INTERVAL to be set to zero in /var/stm/config/tools/monitor/dm_stape.cfg.That disables the dm_stapemonitor within the EventMonitoring System. Symantec recommends that youupgrade to IPR0109.

PHSS_24045

This patch can cause problems with the programs thathave the setuid bit set. Hewlett-Packard ’s ITresource center website contains information aboutthis patch.

http://h20565.www2.hp.com/portal/site/hpsc/public/

PHSS_30970

S700_800 11.11 libc cumulative patch

The above patch has dependency on the followingpatches:

■ PHCO_31923 (critical patch): s700_800 11.11 libccumulative header file patch

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

PHCO_35743


Symantec recommends that all customers running11.23 install this patch. This recommendation appliesto HP PA-RISC only because HP Itanium has movedto 11.31.

PHCO_33431

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

PHSS_34858

That is a recommended critical patch from HP thatNetBackup requires, particularly when you attempt torun NetBackup with NetBackup Access Control(NBAC).

PHKL_31500


http://h20565.www2.hp.com/portal/site/hpsc/public/



Contains fixes for the following:

■ QXCR1000593919: purifyplus dumps corein PA32


■ QXCR1000746161: dlsym() hangs■ QXCR1000593999: dld emits assert messages

for chatr +mem_check enabled 64-bitexecutables

PHSS_37492


This patch bundle is required for NetBackup mediaserver support. It is an HP-UX March 2010 patchbundle.

QPK1131 (B.11.31.1003.347a)patch bundle

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

111722-04 (or greater)

Patch: 112908-29 (or greater)

Patch: 112874-31 (or greater)

Change Request ID - 6723423122300-53

The server is supported on Update 4 (08/07) andnewer.

Update 4 (08/07) and newerSolaris 10 SPARC 64-bit(server and client)




Symantec recommends that you download the patchset dated June 2011 (or newer) from the OracleSupport website.

https://support.oracle.com

The patch set contains the following minimumrecommended patches:

■ 118777-17 (SunOS 5.10: Sun GigaSwift Ethernet1.0 driver patch)

■ 139555-08 (Kernel patch with C++ library updates).■ 142394-01 (Internet Control Message Protocol

(ICMP) patch)■ 143513-02 (Data Link Admin command for Solaris

(DLADM) patch)■ 141562-02 (Address Resolution Protocol (ARP)

patch)

The following patches are recommended for Solaris10 SPARC with NXGE cards:

■ 142909-17 (SunOS 5.10: nxge patch)■ 143897-03 (Distributed Link Software patch)■ 143135-03 (Aggregation patch)■ 119963-21 (Change Request ID - 6815915)■ 139555-08 (Change Request ID - 6723423)

Recommended patch set - datedJune 2011 or newer





Symantec recommends that you download the patchset dated 12/28/2011 (or newer) from the OracleSupport website.


The patch set contains the following minimumrecommended patches:

■ 118778-15 (SunOS 5.10_x86: Sun GigaSwiftEthernet 1.0 driver patch)

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

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

include NXGE fixes)■ 142910-17 (SunOS 5.10_x86: Distributed Link

Software patch)■ 143136-03 (SunOS 5.10_x86: Aggregation patch)■ 139556-08 (Change Request ID - 6723423)■ 119964-21 (Change Request ID - 6815915)

Recommended patch set - dated12/28/2011 or newer

Solaris 10 x86-64

The operating system version must be SUSE LinuxEnterprise Server 10 SP2 or newer to run NetBackup7.0.

Service Pack 2 or newerSUSE Linux EnterpriseServer 10 x64

Microsoft microcode reliability update.KB936357Windows XP x86-32

Hot fix for PBX connection attempt hangs.KB928646Windows XP x86-64

Microsoft microcode reliability update.KB936357Windows Vista x86-32

Contains the necessary updates to ensure that youcan back up encrypted files.

KB952696

Microsoft microcode reliability update.KB936357Windows Vista x86-64


KB952696

Contains the necessary updates to run VolumeShadow Copy.

KB913648Windows Server 2003 IA64(SP1 & SP2)





Hot fix for PBX connection attempt hangs.KB928646

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


KB913648

Microsoft microcode reliability update.KB936357

TCP/IP protocol driver triggers a disconnect eventrandomly. Required for master and media servers.

KB971383Windows Server 2003x86-32 (SP2)

Microsoft Storport hot fix.KB883646Windows Server 2003x86-64 (SP1 & SP2)


KB913648

Hot fix for PBX connection attempt hangs.KB928646

Microsoft microcode reliability update.KB936357

TCP/IP protocol driver triggers a disconnect eventrandomly. Required for master and media servers.

KB971383Windows Server 2003x86-64 (SP2)


KB952696Windows Server 2008x86-32


KB952696Windows Server 2008x86-64


KB952696Windows Server 2008 IA64

Hot fix to improve TCP loopback latency and UDPlatency

KB979612Windows Server 2008 (SP2)

Hot fix for when a computer randomly stopsresponding.

KB2265716Windows Server 2008 R2(SP1)

Hot fix for a decrease in I/O performance under aheavy disk I/O load.

KB982383

Update for the "Modified time" file attribute of a registryhive file.

KB983544




Hot fix to improve TCP loopback latency and UDPlatency

KB979612


Operational notes


■ About NetBackup 7.5.0.7 operational notes

■ Installation and upgrade notes

■ General NetBackup 7.5.0.7 notes

■ Bare Metal Restore notes

■ Cloud storage notes

■ Database and application agent notes

■ Deduplication notes

■ NetBackup OpsCenter notes

■ NetBackup Search notes

■ Virtualization notes

About NetBackup 7.5.0.7 operational notesThe NetBackup 7.5.0.7 maintenance release update is based on the NetBackup7.5 release. That means the operational notes that were documented in NetBackup7.5 may still apply to this release. Therefore, you should review that document ifyou have any questions or issues with this maintenance release.


This chapter contains the topics that explain important aspects of the NetBackup7.5.0.7 operations that may not be documented elsewhere in the NetBackupdocumentation set. This document is posted on the Symantec Support website andmay be updated after the GA release of NetBackup 7.5.0.7. Therefore, Symantec

4Chapter


recommends that you refer to the following document on the Symantec Supportwebsite to view the latest release information.


Installation and upgrade notesThis section contains the operational notes and known issues that are associatedwith the installation and upgrades of NetBackup in this release.

■ If you are a NetBackup MSDP or PureDisk user, please review the followingsection before you upgrade:See “About upgrading MSDP and PureDisk deduplication solutions to resolvecase sensitivity issues” on page 36.

■ If you are a NetBackup Search user, please review the following section beforeyou upgrade:See “About upgrading Search to NetBackup 7.5.0.x” on page 44.

■ After the NetBackup installer completes the upgrade to version 7.5.0.7 on aWindows server, it may request a restart.A restart can be required for a variety of reasons. A restart request in thissituation is most commonly the result of the upgrade to a new version of MicrosoftVisual C++ 2010 run-time DLLs that are found in NetBackup 7.5.0.7. The newversion of Visual C++ was included to correct an issue with symbolic links onWindows platforms. For more information on the symbolic link issue, refer tothe following articles on the Microsoft Support and Symantec Support websites:http://support.microsoft.com/kb/2889080http://www.symantec.com/docs/TECH210360

Note: LiveUpdate users receive a warning status if a restart is required.

To determine if a Windows server is likely to require a restart after upgradingto NetBackup 7.5.0.7, check the version of\SystemRoot\System32\msvcrt100.dll. If the version is lower than10.0.40219.455, then a restart request is very likely to occur due to the VisualC++ upgrade.

■ After an upgrade to Symantec NetBackup, changes to individual Object IDs inthe nblog.conf file are not preserved. However, the major default settings arepreserved.

■ Windows 8/Server 2012 require a special full installation package.For all other supported platforms (including other versions of Windows),NetBackup 7.5 must be installed before you can upgrade to version 7.5.0.x.

27Operational notesInstallation and upgrade notes


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


However, installing NetBackup on Windows 8/Server 2012 is not supported forversions before version 7.5.0.6. To install NetBackup on Windows 8/Server2012, you must use the special full installation package of NetBackup. Thisinstallation package brings the client directly to 7.5.0.6 and is not meant for anyother Windows operating system.

Note: Due to technical limitations, the regular Windows Installer (both x86 andx64) does not prevent installation on Windows 8/Server 2012, even though thismethod is not supported. The only supported method of installing NetBackupon Windows 8/Server 2012 is to use the special 7.5.0.6 x64 full installationpackage.

■ To install NetBackup Windows client software remotely, the system must meetcertain configuration requirements. One of the requirements is that the RemoteRegistry service be started on the remote system. Starting with NetBackup7.5.0.6, the NetBackup installer can enable and start the Remote Registry serviceon the remote system.If the Remote Registry service is not started, the installation receives the followingerror message:

Attempting to connect to server server_name failed

with the following error: Unable to connect to the remote

system. One possible cause for this is the absence of the

Remote Registry service. Please ensure this service is started

on the remote host and try again.

General NetBackup 7.5.0.7 notesThis section contains the general operational notes and known issues that areassociated with this release of NetBackup.

■ NetBackup is migrating to a simplified client name for Windows clients.The new client selectionWindowswill be used for all supportedWindows clients,regardless of the specific Windows version of the client. In future releases,specific Windows version choices will be eliminated. As part of this migration,the client selectionWindows may or may not appear in the client selectionmenus. Please choose the newWindows menu selection for the appropriatearchitecture (x86 or x64). If theWindows selection is not available, please selectthe specific Windows version.

28Operational notesGeneral NetBackup 7.5.0.7 notes

Note: If theWindows selection is not available when adding aWindows 8/Server2012 through any of the NetBackup interfaces, choose the Windows 7 orWindows 2008 menu selection.

■ AWindows multistream backup of all locals disks may fail if Microsoft DistributedFile System Replication (DFSR) is active on the client.Workaround: Disable multistreaming for the Windows clients that have DFSRenabled.

■ An issue can occur where a newly-added NetBackup appliance media serveralso gets added to the EMM database as a master server. Subsequent attemptsto delete the master server entry from the EMM database using the nbemmcmd

–deletehost command fail with the following error:

$ nbemmcmd -deletehost -machinename <machine_name> -machinetype

master

NBEMMCMD, Version: <NetBackup_version>

The function returned the following failure status: "Cannot

delete machine entry '<machine_name>', it has Audit entries.

Please contact Symantec support for deleting audit entries

from the database"

■ Extended attributes are lost when symbolic files are restored on UNIX clients.In particular, the security context extended attributes of symbolic files are alsolost on Security-Enhanced Linux (SELinux) clients.After performing a single file restore operation on a UNIX client, the followingerror can be found under the Task Progress tab of the Backup, Archive, andRestore interface:

08:19:05 (92.001) attr_set failed for <file_name> - Attribute

security.selinux not set. Errno = 2: No such file or directory

The error occurs when the file is a symbolic link and the target of the symboliclink no longer exists. Despite the error, the file appears to have restoredsuccessfully. However, the extended attributes of the symbolic link are lost. Thisissue applies to both virtual clients and physical clients.

Note: If the target does exist, no error is reported and the extended attributeswill get set on the target instead of the symbolic link.

■ An issue can occur if a NetBackup Network Data Management Protocol (NDMP)backup policy is configured with the directive set type=tar in the backup

29Operational notesGeneral NetBackup 7.5.0.7 notes

selection. Parent directories in the path of a file that an incremental NDMPbackup saves may not be present in the backup image. For more informationon this issue, refer to the following tech note on the Symantec Support website:http://www.symantec.com/docs/TECH202412

■ Network Data Management Protocol (NDMP) backup performance is adverselyaffected when the logging level is set to 4 or 5. The performance effect may beserious enough to cause NDMP backup failures. Symantec recommends thatyou set to the logging level to 3 or lower to avoid this issue.

■ NetBackup Windows Client backups fail when NetApp and CIFS shares areconfigured with certain security and access privileges.If a NetApp volume is configured with a “Mixed” security style and is used witha NetApp CIFS share that does not give read access to the client user, thenclient backups fail. This issue only occurs when the NetApp volume is configuredwith the “Mixed” security style. This issue does not affect the volumes that areconfigured with NTFS or UNIX styles.A workaround for this issue is to add explicit read access on the CIFS share tothe user under which the NetBackup client service is running.

■ If any file named "program" exists in the root directory of the Windows systemdrive, such as C:\, NetBackup does not function properly. Any such file must beremoved or renamed before NetBackup can execute command lines and processcreation options.

■ All session log files that are located in the sidxxx/logs directory in NetBackupVault have public write permission. That allows all processes to write to the logfiles.The following is the path for the logs directory on Windows and UNIX servers:

■ Windows:install_path\NetBackup\vault\sessions\vault_name\sidxxx\logs\

■ UNIX: /usr/openv/netbackup/vault/sessions/vault_name/sidxxx/logs/Here vault_name is the name of the vault that is used for the session and xxx

is the unique session ID.

Bare Metal Restore notesThis section contains the operational notes and known issues that are associatedwith Bare Metal Restore in this release of NetBackup.

■ If the backed up file system is encrypted for RHEL, then when the system isrestored with the BMR option, the existing encryption is removed.

30Operational notesBare Metal Restore notes


■ When the /etc/mke2fs.conf file is restored, the restore task is shown aspartially completed on theActivity Monitor tab in the NetBackup AdministrationConsole. The issue occurs on RHEL6 Update 2 platforms and later, and it occurseven though the BMR recovery of the client completes successfully. The issueoccurs because the security properties contain some incorrect settings for the/etc/mke2fs.conf file in a BMR environment after the file is restored.

■ During a Bare Metal Restore, the Zeta file system (ZFS) temporary mount fails.This issue occurs if any ZFS is not mounted or the canmount value is set to OFFduring a backup.To restrict the disk or the disk pool, edit the Bare Metal Restore configurations.The edits ensure that the disk is not overwritten and the data that it contains isnot erased during the restore process.For more information on how to edit the configurations, refer to the followingsections of the Bare Metal Restore Administrator's Guide:

■ Managing Clients and Configurations

■ Client Configuration Properties

■ Issues may occur after BMR restore is performed on Red Hat Enterprise Linux6.After the completion of a BMR Linux restore task, the systemmay display 'KernelPanic' when it looks for a grub menu. The systemmay also go into “maintenancemode” during the first restart. These issues occur because the UDEV daemondynamically detects devices, causing discrepancies with disk names and orderingin various configuration files across restarts.If you encounter this issue, please contact Symantec Technical Support andhave your support representative reference the following tech notes:TECH201332 and TECH179048.

Cloud storage notesThis section contains the operational notes and known issues that are associatedwith cloud storage in this release of NetBackup.

■ In NetBackup 7.6, you can only create or use the storage buckets that are inthe "US Standard" region. If you are using Amazon S3 cloud storage bucketsin regions other than US Standard, you may encounter failures after you upgradeto NetBackup 7.6.Starting with Version 7.5.0.6, NetBackup supported the creation of Amazon S3cloud storage buckets in regions other than US Standard. However, NetBackup7.6 cannot recognize non-US Standard buckets or use them for backups.Symantec does not support an upgrade to NetBackup 7.6 if you continue to useAmazon S3 cloud storage buckets that are in a region other than the US

31Operational notesCloud storage notes

Standard. That includes any buckets that were created outside of NetBackup,such as with the Amazon S3 web portal.

■ An issue occurs where only the master server gets listed in the Cloud StorageServer Configuration Wizard. The same issue causes the Cloud Storage toonly be visible for the master server under media server host properties.The issue occurs when a new Windows NetBackup Administration Consolesession is started or if the master server NetBackup Service Layer (NBSL)service is restarted. The issue results from the media servers getting scannedfor cloud support when the Cloud Storage Configuration Wizard or a mediaserver host properties window is opened for the first time. If you have severalmedia servers in your environment, they may not be displayed initially.To work around this issue, quit and exit the Cloud Storage ConfigurationWizard or media server host properties window. Wait about 2-4 minutes(depending on how many media servers you have configured) and then reopenthe wizard or the media server host properties window. The media serversshould appear when it is reopened. If the media servers are still not listed uponreopening the wizard, quit the wizard again and repeat the waiting period untilthey appear.

■ When the Rackspace plug-in is used on a host running Windows Server 2008R2 with IPv6 enabled, NetBackup may experience network connection issues.Symantec recommends that you disable IPv6 on Windows Server 2008 R2hosts that use the Rackspace plug-in.

Database and application agent notesThis section contains the operational notes and known issues that are associatedwith database and application agent support in this release of NetBackup.

■ Log backup fails with status 50 for SAP HANAA log backup fails if a recovery job is also initiated at the same time. A recoveryjob shuts down the database and log backups fail with error 50.When a recovery job is initiated, the SAP HANA Studio forces a shutdown ofthe system and the backup jobs fail. To avoid the shutdown and subsequentbackup failure, stop the system. You can then start the recovery job.

■ If the NetBackup bprestore log directory does not exist, a ROLLFORWARD

operation may fail for DB2 version 10 and newer.If you use the USEREXIT program to protect the DB2 archive logs and attemptto perform a restore and a ROLLFORWARD operation, the roll-forward may fail.Workaround: Manually create the NetBackup bprestore log directory(/usr/openv/netbackup/logs/bprestore).

32Operational notesDatabase and application agent notes

■ For Exchange GRT operations, the granular proxy host must be installed on aversion of Windows that is supported for that version of Exchange. For example,for Exchange 2010, the granular proxy host must be installed onWindows 2008SP2 or R2 or on Windows 2012.For more information, see the NetBackup Database and Application AgentCompatibility List at the following location:http://www.symantec.com/docs/TECH59978

■ Database configuration parameters USEREXIT and LOGRETAIN have beendeprecated and are no longer valid in DB2 10.1 and later. Instead, LOGARCHMETH1sets the user exit program settings.

■ For the VMware backups that protect SQL Server, note the following:

■ A SQL Server database name cannot contain any of the following characters:? * \ "

■ To use Replication Director to manage your VMware snapshots and snapshotreplication with SQL Server 2012, logon account changes may be required.Logon accounts for the NetBackup Client Service must have access to theCIFS shares that are created on the NetApp disk array.

■ Change the logon account for the NetBackup Legacy Network Service to anaccount that has the fixed server role “sysadmin”.

■ For SQL 2012 on Windows Server 2008/2012, the account that runs theMicrosoft SQL Server Service must have full permissions for the NetBackupLegacy Network Service temp directory. This directory isC:\Users\user\AppData\Local\Temp, where User is the account that runsthe NetBackup Legacy Network Service.

■ For Hitachi and IBM HANA appliances, you need to add an extra lib:libelf.so.0. Refer to the NetBackup for SAP Administrator's Guide for furtherdetails.

■ Backups for SAP HANA can be initiated from NetBackup. Restores are initiatedfrom the SAP HANA Studio. For more information, see the following tech noteon the Symantec Support website:http://www.symantec.com/docs/TECH209343

■ Since SharePoint metadata is stored outside of the content database, it cannotbe restored using Granular Recovery Technology (GRT). You can, however,use GRT to restore SharePoint data with metadata attached to it. As long asthe metadata resides in the same service application, SharePoint maintains thelink between the two items.

■ NetBackup does not support restoring mailbox items into tenant mailboxes in amulti-tenant Exchange environment. To recover items pertaining to a tenant




mailbox, redirect the recovery to a non-tenant mailbox. Backup and recovery ofExchange Server databases are fully supported in a multi-tenant environment.

■ NetBackup does not support Granular Recovery Technology (GRT) withMicrosoftSharePoint Server backups in a multi-tenant SharePoint environment. Backupand recovery of SharePoint Server databases are fully supported in such anenvironment.

■ The NetBackup for Exchange and NetBackup for SharePoint Agents support arestore to the same Microsoft service pack (SP) or cumulative update (CU) onwhich the backup was originally created. Microsoft sometimes introducesdatabase schema changes in SPs or CUs. If you restore to a different SP or CUlevel, the database server may not operate correctly.

Creating a minimal NetBackup account for Exchange operations(Exchange 2010 and 2013)

This procedure describes how to create a minimal account for NetBackup Exchangeoperations for Exchange 2010 and later. This account is used for the Exchangecredentials in the Exchange client host properties, enabling NetBackup to performoperations with Granular Recovery Technology (GRT).

Note the following:

■ Configure each Exchange mailbox server and the CAS server.

■ Configure each client that performs granular operations. To determine whichclients to configure, see the following topic:

■ In a cluster environment, perform the steps on each database node in the cluster.For an Exchange DAG, perform the steps on each database node in the DAGand the CAS server.

To create a minimal NetBackup account for Exchange 2010 and 2013 operations

1 In the Exchange Management Console, create a new Exchange mailbox forNetBackup.

This process creates a new user that is automatically a domain user. Thisprocedure refers to that user as NetBackupUser.

2 Double-click on the user account you created.

3 Select the Member Of tab.

4 Click Add and add this user to the Administrators group.


5 Create a new Role Group, make the account a member of this group, andassign roles. Use the Exchange Management Shell to run the followingcommands:

Note: If the account does not have the necessary privileges, an administratorneeds to perform these tasks.

New-RoleGroup -Name NetBackupRoles -Roles @("Database Copies", "Databases",

"Exchange Servers", "Monitoring", "Mail Recipient Creation", "Mail Recipients",

"Recipient Policies"

Add-RoleGroupMember -Identity NetBackupRoles -Member NetBackupUser

WhereNetBackupUser is the name of the Active Directory account you createdin 1.

6 (Exchange 2010) To perform restores with Granular Recovery Technology(GRT), also run the following commands with the ExchangeManagement shell:

New-ManagementRole -Name SymantecEWSImpersonationRole -Parent ApplicationImpersonation

New-ManagementRoleAssignment -Role SymantecEWSImpersonationRole -User NetBackupUser

-Name "NetBackupUser-EWSImpersonation"

New-ThrottlingPolicy -Name "SymantecEWSRestoreThrottlingPolicy" -EWSPercentTimeInCAS

$null -EWSPercentTimeInAD $null -EWSMaxConcurrency $null -EWSPercentTimeInMailboxRPC

$null -PowerShellMaxConcurrency $null

Set-Mailbox -Identity NetBackupUser -ThrottlingPolicy "SymantecEWSRestoreThrottlingPolicy"

7 Configure the NetBackup Client Service to run as this account.

See the NetBackup for Exchange Administrator’s Guide.

Deduplication notesThis section contains the operational notes and known issues that are associatedwith NetBackup deduplication features (such asMSDP and PureDisk) in this release.

Seeding the fingerprint cache for MSDP■ To ensure that NetBackup uses the seeded backup images, the first backup of

a client after you configure seeding must be a full backup with a single stream.Specifically, the following two conditions must be met in the backup policy:

35Operational notesDeduplication notes


■ The Attributes tab Allow multiple data streams attribute must beunchecked.

■ The backup selection cannot include any NEW_STREAM directives.If these two conditions are not met, NetBackup may use multiple streams. If theAttributes tab Limit jobs per policy is set to a number less than the totalnumber of streams, only those streams use the seeded images to populate thecache. Any streams that are greater than the Limit jobs per policy value donot benefit from seeding, and their cache hit rates may be close to 0%. Afterthe first backup, you can restore the original backup policy parameter settings.For more information about seeding, see the following Symantec tech note:http://www.symantec.com/docs/TECH144437

About upgrading MSDP and PureDisk deduplication solutions toresolve case sensitivity issues

Note: If all of your NetBackup media servers are running Windows, and you do notplan to add UNIX servers running MSDP, you may safely ignore the rest of thistopic.

This section applies to the following deduplication solutions:

■ NetBackup Media Server Deduplication Option (master server, media server,client, or VMware backup host)

■ NetBackup appliance deduplication (master server, media server, or VMwarebackup host)

■ PureDisk deduplication

■ PureDisk appliance deduplication

In versions before NetBackup 7.5.0.6, a problem can occur where NetBackup cannotread an image that is stored on anMSDP or PureDisk storage unit. The issue resultsfrom inconsistencies in how entries are written and read in the deduplicationdatabase on case-sensitive file systems. The types of operations that might exhibitfailure due to a read error that is associated with this issue include verify, restore,duplication, and replication. For MSDP, the issue is fixed starting in NetBackup7.5.0.6 (appliance 2.5.3). For PureDisk, the issue is fixed starting in Version 6.6.5(appliance 1.4.4).



Table 4-1 Examples of the failed operations that can result from the casesensitivity issue

Status in bpdm andbptm log files

Activity Monitorjob details

Activity Monitorstatus

Operation

sts_open_imagefailed: error 2060018

image open failed:error 2060018: file notfound

(191) no imagessuccessfullyprocessed

Verify


Image open failed:error 2060018: file notfound

(83) media open errorRestore



(83) media open errorDuplication (MSDPsource)

rpl_add_image_set:rpl_get_image_info()failed, error 2060013

get image propertiesfailed: error 2060013:no more entries

(83) media open errorReplication (MSDPsource)



(83) media open errorDuplication (PDDOsource)

rpl_add_image_set:rpl_get_image_info()failed, error 2060013

get image propertiesfailed: error 2060013:no more entries

(83) media open errorReplication (PDDOsource)

Example scenarios of the client name case sensitivity issueThe following list contains two examples of scenarios in which the client name casesensitivity issue can occur. These example scenarios are intended to assist you inunderstanding how the issue canmanifest in a NetBackup environment. There maybe more scenarios in which this issue can occur.

■ Example 1Suppose that there is a NetBackup client named my_client running a versionof NetBackup previous to Version 7.5.0.6 and that there is a correspondingpolicy named my_policy. Suppose also that my_client performs client-sidededuplication to a UNIX-based MSDP or PureDisk storage unit. Next, supposethat the following steps occur:


1 A successful backup for my_policy is made to an MSDP or PureDisk storageunit.

2 The name of the client in the policy my_policy is changed from my_client toMY_CLIENT.

3 Another successful backup for my_policy is made to an MSDP or PureDiskstorage unit.

The data for both backups is saved. However, the operations that attempt toread the data from the second backup fail if the deduplication engine is on acase-sensitive file system. The failures occur because the deduplication databaseentry my_client differs from MY_CLIENT and the previous version of theNetBackup client writes incorrect deduplication database entries. The issues inthis specific example can be resolved by upgrading the client to NetBackup7.5.0.6 or newer.

■ Example 2Suppose that there is a UNIX media server running NetBackup 7.5.0.6 or latercalled media_A that is attached to an MSDP storage unit. Suppose also thatthere is another media server called media_B running Windows and a versionof NetBackup that is older than Version 7.5.0.6. In this example, media_B hasthe credentials that allow it to access theMSDP disk pool MSDP_POOL on media_A.Suppose that a policy named my_policy was created for a client namedmy_client (such as in the first example) and the following events occur:

1 A successful backup of my_policy for my_client is made to MSDP_POOL.

2 The policy my_policy is copied to MY_POLICY.

3 The name of the client in the policy MY_POLICY is changed from my_client toMY_CLIENT.

4 A backup of MY_POLICY is successful to MSDP_POOL.

In this example, the backups are saved and media_A can read them. However,one or more of the backup images cannot be read from MSDP_POOL by media_Bbecause media_B suffers from the name case sensitivity issue. In this situation,the issue occurs whenever the master server selects media_B as the server toperform the read operations on MSDP_POOL.This particular manifestation of the issue can be diagnosed using the followingmethods:

■ Use the bpimagelist command to verify that the images were stored on thedesired MSDP disk pool.


■ Look for the following in the granted resource line in the Activity Monitorjob details for the failed job:The host that is listed as the storage server is running NetBackup 7.5.0.6 ornewer.The host that is listed as the media server is running a version of NetBackupthat is older than Version 7.5.0.6.

The issues in this specific example can be avoided by upgrading all of your mediaservers to NetBackup 7.5.0.6 or newer.

Determining the servers and clients that can encounter theissueThe case-sensitivity issue can occur if your environment performs any of thefollowing MSDP functions on UNIX operating systems that run on NetBackup mediaservers or PureDisk servers (including NetBackup appliances and PureDiskappliances).

1. Media server deduplication to attached storage

2. Media server deduplication to another media server

3. Media server deduplication to a PureDisk server

4. Media servers for optimized MSDP duplication within the same domain

5. Client-side deduplication to a media server

6. Client-side deduplication to a PureDisk server

Note: All of the listed operations apply to the VMware backup hosts that run thededuplication engine.

All of the listed operations also apply to the master servers that function as mediaservers and run the deduplication engine.

Symantec recommends that you upgrade all of the servers, clients, and VMwarebackup hosts in your environment that are involved in the listed operations. Thatincludes any media server that uses credentials for an affected MSDP storage unit.Starting with NetBackup 7.5.0.6 (appliance 2.5.3) and PureDisk 6.6.5 (appliance1.4.4), writing to the deduplication database has been updated to fix the issue. Thedatabase writes are fixed so that a change in the case of the characters that areused for the NetBackup client name and policy do not cause a read of the backupimages to fail. If you do not upgrade to these minimum versions, there is a possibilitythat you may encounter read errors with future backup images due to this issue.


Note: Consistent with NetBackup upgrade policy your media servers and clientsmust be running a minimum of NetBackup 7.5 before you can attempt to upgradeto 7.5.0.x.

Fixing the name case sensitivity issues that exist in the MSDPand PureDisk databasesIf you have already encountered image read failures due to client name or policyname case sensitivity issues, your first step should be to upgrade the affected hoststo NetBackup 7.5.0.6 or newer. After the upgrade, the name case issue still affectsthe images that were created before the upgrade by versions of NetBackup previousto Version 7.5.0.6. Use the following table to select the correct approach to repairclient and policy name case sensitivity issues with existing NetBackup images.

Table 4-2

Required actionStorage unit typeProblematic name type

Repair the MSDP databaseMSDPClient

Repair the PureDisk databasePureDiskClient

Contact Symantec TechnicalSupport

MSDPPolicy

Contact Symantec TechnicalSupport

PureDiskPolicy

Special procedures to repair an MSDP database or a PureDisk database areavailable on the Symantec Support website at the following URL:


NetBackup OpsCenter notesThis section contains the operational notes and known issues that are associatedwith NetBackup OpsCenter in this release.

■ Uninstalling OpsCenter software may not completely uninstall maintenancereleases on Windows. OpsCenter maintenance releases may still be visible inthe Windows system program uninstaller.For more information and workaround instructions for this issue, see the followingtech note on the Symantec Support website:http://www.symantec.com/docs/TECH211299

■ Issues can occur if OpsCenter is installed in a non-default location on Windowssystems because of the Windows maximum path length limitation. If the install

40Operational notesNetBackup OpsCenter notes



directory causes OpsCenter to exceed the character limit, unpredictable behaviormay occur after installation or upgrade. For example, the OpsCenter interfacemay fail to load after an upgrade to Version 7.5.0.x.

■ A cloud metering data collection failure can occur if one or more media serverswith credentials to access a cloud storage server (data movers) is unreachablefor some reason.Workaround: From the unreachable media server, use tpconfig to remove thecredentials of that media from all cloud storage servers on the master. Cloudmetering data collection should then succeed. All the cloud metering data fromthe media servers that were missed earlier can now be collected.

■ Uninstalling OpsCenter 7.5.0.6 may take a long time on the HP-UX.In certain scenarios, OpsCenter 7.5.0.6 on HP-UX may take several minutes touninstall. Do not interrupt the uninstallation process.

■ The Monitor > Alerts List View does not show alerts in certain scenarios.Under the Monitor > Alerts List View, if you sort the alerts by Alert Policy orSeverity, the existing alerts are not displayed on the page.To work around the issue, remove the Alert Policy or Severity columns fromsorting. You can then view the existing alerts appropriately under the Monitor> Alerts List View.To remove a column from sorting, do the following:

1 Go to the Monitor > Alerts List View and click Change Table Settings.

2 On the Table Settings pop-up screen, clear the sorting that you may have appliedto the Alert Policy and Severity columns.■ Select the corresponding check box.■ Modify the selection for the Sort drop-down list. TheUp orDown options should

not be selected for these columns.

3 Click Ok.

■ The Monitor > Overview page does not display a NetBackup master serverappropriately if it is a virtual machine.The following is an example scenario of the issue:


1 Install a NetBackup master server that is a virtual machine and that contains virtualmachine data.

2 Install OpsCenter Server.

3 In the OpsCenter interface, add the same master server with its host name as adisplay name.

4 Go to the Monitor > Overview page. It displays the display name of the virtualmachine on which the master server is installed instead of the master server displayname.

■ In certain scenarios, duplicate entries of a client are displayed on the Monitorand Views interfaces.

This issue is seen in any of the following scenarios:

■ A NetBackup master server is used as a client in one or more policies.

■ Some NetBackup policies refer to a NetBackup master server with a fullyqualified domain name (FQDN) while others refer to it with a short name.

■ The actual name of the master server does not match its network name ordisplay name that is used in OpsCenter.

The following is an example scenario of the issue:The actual name of the NetBackup master server is abc.xyz.com. The networkname or display name that is used in OpsCenter is xyz.In this scenario, if abc.xyz.com is used as a client in one or more NetBackuppolicies, duplicate entries of this client are displayed on the following OpsCenterscreens:

■ Monitor > Host > Client

■ Settings > Views >Manage Nodes andObjects > Objects not in selectedview

■ NetBackup 7.5.x.x can only be installed on a system that is running NetBackup7.5. However, if you upgrade to NetBackup 7.5 from a previous version, suchas 7.1, the upgrade might fail with the following error message:No primary key value for foreign key

'FK_JOB_REF_MEDIA_SERVER_ARCHIVE' in table 'domain_JobArchive

If you encounter this error, please contact Symantec Technical Support beforeyou try to re-attempt the upgrade process.

■ Custom tabular reports may not display all jobs if the Media Barcode field isselected. If you encounter this issue, please contact Symantec Technical Supportfor assistance.


■ To run a Capacity Licensing report in NetBackup 7.5.0.7, a user name andpassword is required for each master server. To successfully run a report forany master servers that were added to OpsCenter in versions previous to 7.5.0.5,an extra step is required. The user name and password credentials for eachmaster server must be enteredmanually in the NetBackup configuration settings.If the credentials are not added in the configuration settings, a user name andpassword error is returned when the report is run.Additionally, for Capacity Licensing to work correctly, please refer to the followingtech note and install the specified EEBs:http://www.symantec.com/docs/TECH148678

■ Policy view is not applicable for Restore type jobs.If you select the policy view when you create any job-related alert policy,OpsCenter does not generate alerts for restore jobs. Since restore jobs do nothave a policy associated with them, they never raise alerts for policy view.

■ If an OpenStorage alert policy is configured, then OpsCenter generates an alert(email) for each volume.To work around this issue, you can filter the volume type alert by specifying thetext (for example: With volume name, not protected for any volume, and asrequired) in the field that is provided for the Event message contains word(s)selection. OpsCenter generates the alert only when the NTAP event containsthe text that is specified in Event message contains word(s) selection.

■ When an OpsCenter user is deleted, the following user-specific data is alsodeleted along with views, report schedules, and so on:

■ All data collectors that the user has created

■ All data collectors that the user has modified, irrespective of who createdthem

Because of this behavior, there may be data collection failure as a result of userdeletion.The following scenario explains the issue in detail:User A creates Data Collector D1 to collect data from NetBackup master serverM1. User B modifies D1. The OpsCenter Admin deletes User B. As a result ofthis user deletion, D1 is also deleted because User B had modified it. Therefore,data collection fails and User A cannot collect any data from M1.

■ On 64-bit Windows, if language packs are installed on top of a 7.1.0.x or a 7.5.0.xinstallation, an upgrade to a later version may fail. For example, if you upgradeOpsCenter 7.5 to 7.5.0.4 and install all language packs on top of 7.5.0.4, anupgrade to 7.5.0.5 may fail.To work around the issue, manually uninstall all language packs before theupgrade, and then reinstall them after the upgrade.



■ In the Simplified File Restore (SFR) Timeline View, for the images that arecollected in OpsCenter, the data format is shown as unknown because of thelack of data.

■ OpsCenter job collection frommaster servers could fail if port 1556 is not openedbi-directionally on both the NetBackup and OpsCenter sides.

NetBackup Search notesThis section contains the operational notes and known issues that are associatedwith NetBackup Search in this release.

■ Restore jobs may fail when the nbholdrestorehelper utility is used to restoreheld data. The issue occurs when the Policy type of a backup policy does notmatch the Policy type attributed to the backup in the NetBackup catalog.Workaround: Edit the <client_name>_restore.bat file that was created by thenbholdrestorehelper utility and specify the policy type for the bprestore.execommand, then run that batch file.

Note: The policy type option for the bprestore command should match thepolicy type attribute that was set when the policy was created.

About upgrading Search to NetBackup 7.5.0.xNetBackup Search users must follow a special procedure to upgrade fromNetBackup 7.5 to any NetBackup 7.5.0.x maintenance release (for example, Version7.5.0.6). This procedure also applies to upgrading between NetBackup 7.5maintenance releases (for example, upgrades between Version 7.5.0.3 and Version7.5.0.6). Symantec recommends that all NetBackup Search users review thisprocedure before they upgrade to a new release.

The NetBackup Search upgrade procedure can be found on the Symantec Supportwebsite at the following link:


Virtualization notesThis section contains the operational notes and known issues that are associatedwith virtualization technologies in this release of NetBackup.

■ For a snapshot that quiesces an application on a Windows 2008 or later VM,VMware VDDK 5.1 imposes the following disk requirements:

44Operational notesNetBackup Search notes


■ The VM's disks must be SCSI, not IDE.

■ The SCSI disks on the VM’s SCSI controller must not occupy more than halfof the total number of slots in the controller. Since the controller has a totalof 15 slots, the number of disks in that controller must not exceed 7.

If these conditions are not met and the NetBackup VMware policy enables theVirtual machine quiesce option, the backup may fail with status code 156.For more information on this VMware requirement, refer to the following articlein the VMware vSphere 5.1 Documentation Center:Working with Microsoft Shadow Copy

■ Starting with NetBackup 7.5.0.7, the SYMCquiesce utility (SYMCquiesce.iso)is included in NetBackup for Linux. However, the utility is not included in the 7.6GA release of NetBackup for Linux and is removed during an upgrade fromversion 7.5.0.7. To keep this utility for NetBackup 7.6 GA, make a copy andstore it in a safe place before upgrade. Otherwise you can retrieve the file froma Windows computer running NetBackup, or a Linux computer runningNetBackup 7.5.0.7.

The SYMCquiesce.iso file is located in the following locations:

■ Windows\NetBackup\bin\goodies\vmware-quiesce

■ Linux/usr/openv/netbackup/bin/goodies/vmware-quiesce

Warning:Multiple versions of SYMCquiesce.iso may exist in these directorieswith names such as SYMCquiesce.1.0.0-001.iso. Unless otherwise specifiedin the NetBackup documentation, only install SYMCquiesce.iso. Do not installSYMCquiesce.1.0.0-001.iso.

For more information about the SYMCquiesce utility, refer to the NetBackup forVMware Administrator's Guide, available at the following website:http://www.symantec.com/docs/DOC5332

■ For Linux VMs without persistent device naming, multiple disk controllers (suchas IDE, SCSI, and SATA) may complicate the recovery of individual files. Thisissue occurs because non-persistent device naming, such as /dev/sda and/dev/sdb, may cause unexpected mount point changes after a restart. If theVM has a SCSI disk and a SATA disk, the Backup, Archive, and Restore interfacemay show incorrect mount points for the VM's files. For example, the filesoriginally under /vol_amight appear under /vol_bwhen you browse to restorethem. The restore is successful, but the restored files may not be in their originaldirectories.

45Operational notesVirtualization notes

http://pubs.vmware.com/vsphere-51/index.jsp#com.vmware.vddk.pg.doc/vddkBkupVadp.9.6.html?resultof=%2522%2556%256f%256c%2575%256d%2565%2522%2520%2522%2576%256f%256c%2575%256d%2522%2520%2522%2553%2568%2561%2564%256f%2577%2522%2520%2522%2573%2568%2561%2564%256f%2577%2522%2520%2522%2543%256f%2570%2579%2522%2520%2522%2563%256f%2570%2569%2522%2520%2522%2553%2565%2572%2576%2569%2563%2565%2522%2520%2522%2573%2565%2572%2576%2569%2563%2522%2520%2522%2551%2575%2569%2565%2573%2563%2569%256e%2567%2522%2520%2522%2571%2575%2569%2565%2573%2563%2522%2520


As a workaround, search for the files on the restored VM and move them to theproper locations.To prevent this issue on Linux VMs with multiple disk controllers, Symantecrecommends a persistent device-naming method for mounting the file systems.When persistent naming is in place, device mounting is consistent and this issuedoes not occur when you restore files from future backups.For persistent device naming, you can mount devices by UUIDs. The followingis an example of the /etc/fstab file that contains devices that are mountedwith UUIDs:

UUID=93a21fe4-4c55-4e5a-8124-1e2e1460fece /boot ext4 defaults 1 2

UUID=55a24fe3-4c55-4e6a-8124-1e2e1460fadf /vola ext3 defaults 0 0

To find the device UUIDs, you can use either of the following commands:

■ blkid

■ ls -l /dev/disk/by-uuid/

Note: NetBackup also supports the by-LABEL method for persistent devicenaming.

■ An issue can occur for the virtual machines that are configured with a logicalvolume (LVM or LDM). A backup with theEnable file recovery fromVMbackupoption fails if the volume disk set contains a mixture of disk types, as follows:

■ Some of the disks in the logical volume set are regular virtual disks (normalVMDKs), and

■ Some of the disks in the same volume set are independent disks or arephysical disks in raw device mapping mode (RDM).

In this case, the backup job returns status 6 "the backup failed to back up therequested files". The VxMS log contains the message "bitmap read failed".Note: On the VMware backup host, the VxMS log is in the following directory:

■ Windowsinstall_path\NetBackup\logs\vxms

■ UNIX/usr/openv/netbackup/logs/vxms

For information about configuring VxMS logging, see theNetBackup for VMwareAdministrator's Guide, available from the following location:http://www.symantec.com/docs/DOC5332Workaround: Make sure that the following optimization options in the policy aredisabled:



■ Enable file recovery from VM backup

■ Exclude deleted blocks

■ Exclude swap and paging files

■ VMware has identified a VDDK issue that can prevent the restore of athin-provisioned disk that resides on local storage. When you attempt to restorethe VM, the restore job fails in the following case:

■ Neither nbd nor nbdssl is selected as the transport mode for the restore,

■ The VM that you want to restore has a thin-provisioned disk, and

■ The disk is on a directly attached device (not on a networked device, SANdevice, or iSCSI device).

To restore the VM, select nbd or nbdssl as the transport mode on theRecoveryOptions dialog in the NetBackup Backup, Archive, and Restore interface.For additional detail on this issue, see “VixDiskLib should check SAN accessibilityon disk open” in the VMware VDDK 5.1 release notes:http://www.vmware.com/support/developer/vddk/VDDK-510-ReleaseNotes.html

■ In NetBackup 7.5.0.5 and later, when you use the NetBackup AdministrationConsole to delete the credentials definition for a VMware server, the VMwarehost is automatically removed from the NetBackup Enterprise Media Manager(EMM) database. Under "Changing the host name of a VMware server inNetBackup," the 7.5 and 7.6 versions of the NetBackup for VMwareAdministrator’s Guide incorrectly state that you must remove the VMware hostmanually by means of the nbemmcmd command.

■ After the NetBackup-Java interfaces are upgraded to version 7.5.0.7, the Backup,Archive, and Restore interface may fail to show VMware vCenter servers duringan alternate location restore when the master server is at a lower version than7.5.0.7.For more information about this issue, see the following tech note on theSymantec Support website:http://www.symantec.com/docs/TECH211354

■ For backup hosts with limited memory, simultaneous backups of VMware VMsmay fail due to lack of memory. The bpbkar log contains a message that includesthe phrase “failed to allocate.”Reschedule the backups so they do not occur at the same time, or add morememory to the backup host.

■ In rare instances, the NetBackup bpbkar process may core dump (althoughbackups complete successfully). If the VMware backup host is configured forcore dump generation, the dump files may occupy too much space and affectperformance.


http://www.vmware.com/support/developer/vddk/VDDK-510-ReleaseNotes.html


As a workaround, delete the core files or disable core-dump generation.For more information on this VMware issue, see “Threads still running afterVixDiskLib_Exit call” in the VMware VDDK 5.1.1 release notes:http://www.vmware.com/support/developer/vddk/vddk-511-releasenotes.htmlhttp://www.symantec.com/docs/TECH211060

■ The following features are not supported for dual boot virtual machineconfigurations:

■ Enable file recovery from VM backup

■ Optimizations:Exclude deleted blocksExclude swapping and paging filesExclude boot diskExclude data disks

■ A restore of a VM with the hotadd transport mode or the SAN transport modemay not succeed if the VM’s disk geometry in the backup image differs from theVM’s default values. VM disk geometry refers to the layout of the virtual disk(cylinders, heads, sectors) as specified in the vmdk file.The NetBackup restore job reports partial success with status code 1 (therequested operation was partially successful). For more information about thisissue and available workarounds, see the following tech note on the SymantecSupport website:http://www.symantec.com/docs/TECH210611

Note: The restored VM may not be able to start. VMware has documented thecause of this issue in their VDDK 5.1 release notes, under Known Issues andWorkarounds: "Metadata write is not supported for HotAdd and SAN transport."


■ For a VMware backup host on Linux: If the master server is on a separate host(not on the same Linux backup host), the master server must be at NetBackup7.5.0.1 or later.

■ If a single recovery host performs multiple, simultaneous restores of the sameVM backup image, some of the restored VMsmay fail to power on. For example:host rec27.acme.com runs three restores of the same backup of VMprodvm3.acme.com, and the restore jobs occur at the same time or partiallyoverlap. In this case, an error similar to the following displays in the vSphereClient:


http://www.vmware.com/support/developer/vddk/vddk-511-releasenotes.html




An unexpected error was received from the ESX host while powering

on VM vm-xxxx.

Reason: The parent virtual disk has been modified since the child

was created.

Cannot open the disk

'/vmfs/volumes/4c3e6336-c5f64960-425c-d8d385b02700/xxxxx/yyyyy.vmdk'

or one of the snapshot disks it depends on.

To work around the issue, restore the virtual machine image sequentially: Leteach restore complete before the next restore begins. If simultaneous oroverlapping restores of the same VM backup image are required, use a differentrecovery host for each restore.

■ With VMware VDDK 5.1, backups that use the hotadd or SAN transport modesdo not include the VM's metadata changes in the backup. The status log of theNetBackup job contains messages similar to the following:

07/25/2013 12:37:29 - Info tar (pid=16257) INF - Transport Type

= hotadd

07/25/2013 12:42:41 - Warning bpbrm (pid=20895) from client

<client_address>: WRN - Cannot set metadata (key:geometry.

biosSectors, value:62) when using san or hotadd transport.

As a workaround, retry the backup with a different transport mode (nbd ornbdssl).This problem is a known VMware issue. For more details, refer to the VMwareVDDK 5.1 release notes at the following URL:http://www.vmware.com/support/developer/vddk/VDDK-510-ReleaseNotes.html#knownissues

■ VMware has identified an issue in ESXi server 5.1 that affects application-levelquiesced snapshots for incremental backups. This issue affects VMware VMsthat run Windows Server 2003, 2008, 2008 R2, and 2012. The changed blocktracking system overstates the amount of the changed data, creating a largerbackup than necessary. As a result, incremental backups may take longer thanexpected and may not complete within the backup window. This issue affectsNetBackup for VMware incremental backups.To fix this problem, update your ESXi 5.1 servers with the ESXi 5.1 Patch 02that is described in the following VMware knowledge base article:http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2052143The following VMware “VDDK 5.1 release notes” article containsmore informationon this issue. See under “With application level quiescing, Changed BlockTracking overstates changes”:


http://www.vmware.com/support/developer/vddk/VDDK-510-ReleaseNotes.html#knownissues


http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2052143

http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2052143


■ NetBackup for VMware does not support any display names that end in a periodcharacter (.). If the policy's "Primary VM identifier" option is "VM display name,"any VM with a period at the end of the name is not backed up.

■ A restore of the virtual machine can fail with status code 220 (database systemerror) if all of the following are true of the backup:

■ The backup was run from an incremental schedule and Enable block-levelincremental backup was enabled on the policy VMware tab.

■ Enable file recovery from VM backup was disabled on the policy VMwaretab.

■ At the time of the incremental backup, the data in the VM had not changedsince the previous backup.

To work around this issue, restore from the full image rather than the incrementalimage. Because there is no change of data since the full backup, a restore fromthe full image is exactly the same as a restore from the incremental backup.

■ The VMware policy Advanced Attributes dialog has a setting that is calledVirtual disk selection that has options for excluding the boot disk or data disksfrom the backup. To use either of the exclude disk options before version 7.5.0.6,NetBackup required that the full swap file reside on the boot disk. The swap fileis the Windows pagefile.sys file or the Linux swap partition. This restrictionhas been lifted in 7.5.0.6. For either of the exclude disk options, the swap fileno longer needs to reside on the boot disk.

■ For a Linux virtual machine backup that requires file mapping, the name of anLVM volume can include any of the following special characters:

■ . (period)

■ _ (underscore)

■ - (hyphen)No other special characters are supported. If other special characters are usedin the volume name, the Enable file recovery from VM backup policy optiondoes not work. As a result, you cannot restore individual files from that volume.

Hyper-V notes■ NetBackup for Hyper-V does not support the ampersand character (“&”) in the

name of the virtual disk file (.vhd). If the name of the virtual machine’s vhd filecontains “&”, the backup fails with status code 6.To work around this issue, remove the “&” from the .vhd file name and rerunthe backup.




■ Starting with NetBackup 7.5.0.6, you can restore a virtual machine to Hyper-V2012 even if the virtual machine resided on a Hyper-V 2008 R2 server when itwas backed up. However, to connect to the restored virtual machine, you mayhave to modify the virtual machine’s network adapter by selecting the correctvirtual switch.This issue results from changes to the virtual machine XML configuration inHyper-V 2012.

Note: Restoring the virtual machine to Hyper-V 2008 R2 does not have thisissue.

■ An issue exists where you cannot add a Red Hat Enterprise Linux 6.4 VM as aclient to a Hyper-V policy by its host name. To solve this issue, you need toinstall all the necessary OS updates that are detailed in Red Hat Bug 883306(https://bugzilla.redhat.com/show_bug.cgi?id=883306). You can also workaround this issue by adding the VM as a client to the policy using either the VMdisplay name or UUID.

■ Backup of virtual machines within Cluster Shared Volumes (CSV) is supported.In Hyper-V Server 2008 R2, CSV has a limitation that requires serialized backups.In Hyper-V Server 2012, CSV supports concurrent backups without that limitation.Consequently, the CSV timeout setting in the NetBackup Hyper-V policy is onlyused in Hyper-V Server 2008 R2 deployments.

■ The Enable file recovery from VM backup policy option is not supported forthe virtual machines that are .vhdx files. If the virtual disk is in the .vhdx format,you can restore the entire virtual machine, but not individual files.If you attempt to restore individual files, the restore fails. For NetBackup 7.5.0.7master servers, the Activity Monitor's Job Details dialog contains the followingmessage:

This VM contains VHDX virtual disk(s). Single file restore will

not be possible for such disks. You will be able to perform

a full restore.

For NetBackup 7.5.0.7 and earlier master servers, the Job Details message issimilar to the following:

Warning bpbrm(pid=9128) from client <hostname>: WRN - VxUL id = 34.

■ On Windows Server 2012, cluster nodes can back up the same cluster sharedvolume simultaneously. As a result, NetBackup does not use theCluster sharedvolumes timeout option on the policy's Hyper-V tab if the cluster is onWindowsServer 2012.


https://bugzilla.redhat.com/show_bug.cgi?id=883306

End-of-life notifications


■ About future NetBackup end-of-life notifications

About future NetBackup end-of-life notificationsSymantec is committed to providing the best possible data protection experiencefor the widest variety of platforms, operating systems, databases, applications, andhardware. Symantec continuously reviews NetBackup's support of these items.This review ensures that the proper balance is made between maintaining supportfor existing versions of products, while also introducing new support for the following:

■ General Availability releases

■ Latest versions of new software and hardware

■ New NetBackup features and functionality

While Symantec continually adds support for new features, platforms, andapplications, it may be necessary to improve, replace, or remove certain supportin NetBackup. These support actions may affect older and lesser-used featuresand functionality. The affected features and functionality may include support forsoftware, OS, databases, applications, hardware, and 3rd-party product integration.Other affected items may include the products that are no longer supported ornearing their end-of-support life with their manufacturer.

Symantec provides advanced notification to better help its customers to plan forupcoming changes to the support status of the various features in NetBackup.Symantec intends to list older product functionality, features, hardware, OS, andthe 3rd-party software products that are no longer supported in the next release ofNetBackup. Symantec makes these support listings available as soon as possiblewith a minimum of six months where feasible before major releases.

5Chapter

Much of this support information is available through the NetBackup SymantecOperations Readiness Tools (SORT) home page widgetNetBackup Future Platformand Feature Plans. Also, included in the widget are the list of platforms, databases,and applications that are not supported in a given release. You can access SORTat the following URL:


Another SORT resource is to provide users with End of Life (EOL) andEnd-of-Support Life (EOSL) information for NetBackup licensed software.

■ NetBackup EOL information can be found at the following URL:https://sort.symantec.com/nbufutureplans

■ To viewNetBackup EOSL information, go to https://sort.symantec.com/netbackupand navigate to Support > Related Links. Click on the link to End of AssistedSupport information. Alternatively, you can follow the direct link tohttps://sort.symantec.com/eosl.

Other information about what is compatible with NetBackup can be found in thevarious compatibility lists that are listed in the NetBackup Master Compatibility List.


53End-of-life notificationsAbout future NetBackup end-of-life notifications


https://sort.symantec.com/nbufutureplans


https://sort.symantec.com/eosl


About the NetBackup7.5.0.7 release content

This appendix includes the following topics:

■ About NetBackup release content

■ NetBackup 7.5.0.7 release content

■ NetBackup 7.5.0.7 Emergency Engineering Binary (EEB) listing

About NetBackup release contentThis release incorporates fixes to several known issues that existed with NetBackup.Many of these issues pertain to the customer-specific issues that have beendocumented in the form of Titan or Salesforce.com cases. Many of the fixes thatare incorporated into this release are available as individual engineering binariesand engineering bundles (EEBs). These EEBs were created to address specificcustomer issues with a previous version of NetBackup.

The following sections contain listings of Etracks and EEBs that document theknown issues that have been fixed in this release of NetBackup.

About release content conventionsThe following list describes the conventions used in the subsections that follow thissection. Each item listed in the release content subsection describes a feature,enhancement, or fixed issue contained in this release:

■ Etrack IncidentNotes the Etrack number that targets this release.

■ Associated Primary Etrack

AAppendix

An additional Etrack number that exists in the incident hierarchy.

■ Associated Service Request EtrackThe Etrack that is associated with the customer support service request.

■ DescriptionDescribes a particular issue that has been fixed in this release, as well asadditional notes or workarounds. Workarounds can be used instead of applyingthe patch, however, Symantec recommends the "best practice" of being at thelatest available patch level.

■ **Description or **Etrack numberDescribes a critical issue or an issue that can lead to a potential data loss thathas been fixed in this release. Please read these issue descriptions carefully.In some cases, a Tech Alert link is provided.

About current release content EtracksFor more information on the Etracks that are listed in this section, or any otherservice request Etrack, Symantec recommends that you use Symantec OperationsReadiness Tools (SORT). To access SORT, go to the following webpage:

http://sort.symantec.com/netbackup

NetBackup 7.5.0.7 release contentThis section contains a list of known issues that were fixed and that are now includedin this release of NetBackup.

Etrack Incident: 3092686

■ Associated Primary Etrack: N/A

■ Associated Service Request Etrack(s): N/A

■ Description:An administrator could not list the images that have StorageServiceName setto some SLP, but StorageServiceState set to 0 (NOT_MANAGED). As a result,the administrator was not able to delete the SLP.




■ Description:The NetBackup Backup, Archive, and Restore interface displayed an incorrectmodified date for a Lotus Notes data folder.

55About the NetBackup 7.5.0.7 release contentNetBackup 7.5.0.7 release content

http://sort.symantec.com/netbackup


■ Associated Primary Etrack: 3142944

■ Associated Service Request Etrack(s): 3142918

■ Description:If the backup IDs in the track log were wrong (for example, the index is invalid),the client would continue until the server side failed. Now the client automaticallydetermines whether to back up successfully with the affected optimization, orfail immediately and rename the track log name.




■ Description:The Success Rate Line report did not include the current day's job information.




■ Description:NDMP restores created endless read_data: waited for empty buffer

messages in the NetBackup tape management process (bptm) log. This issuecaused the Activity Monitor to freeze.




■ Description:The import of images that are replicated using Auto Image Replication couldencounter an issue. The import would never happen when users configured anMSDP storage server as an Auto Image Replication target and that storageserver also had amachine alias configured. Themachine alias would not properlyresolve.




■ Description:


If a logical volume manager (LVM) disk has a master boot record (MBR)signature, the backup fails with status 6 and status 11. However, those errormessages did not convey that the backup was unsuccessful due to amisconfiguration. Added a clearer error message if the disk is LVM and has anMBR signature.




■ Description:If any inode is corrupted in the Windows OS, then there is a chance that thereis no attribute present in the Master File Table (MFT) index. Now if there is noattribute present in any MFT index, then VxMS should return the error for thatparticular index. VxMS bypasses that particular MFT index.




■ Description:Upgraded Microsoft Visual C++ 2010 run-time DLLs. The new version of VisualC++ was included to correct an issue with symbolic links onWindows platforms.For more information on the symbolic link issue, refer to the following article onthe Microsoft Support website: http://support.microsoft.com/kb/2889080




■ Description:In the NetBackup Java Administration Console List of Media image output list,the encryption key tag indicated 0 even if the backup images were collectedwith the Key Management Service (KMS).




■ Description:Sorting by Client Name was not available for Week at a Glance reports inNetBackup OpsCenter 7.5.0.6.


NetBackup 7.5.0.7 Emergency Engineering Binary(EEB) listing

The following table contains the known issues that were identified, fixed, andavailable to customers in the form of an EEB. NetBackup 7.5.0.7 resolves theaddressed issues in each of these EEBs. Additional EEBsmay have been releasedsince this document was posted. For more information on the Etracks that are listedin this section, or any other service request Etrack, Symantec recommends thatyou use Symantec Operations Readiness Tools (SORT). To access SORT, go tothe following webpage:


Alternatively, if you do not see an EEB that you expected to see in this document,or you require additional information about an issue in this table, contact SymantecSupport.

Table A-1 NetBackup 7.5.0.7 EEB Listing

EEB DescriptionEtrack Number

Provide ability to specify media server that should be used to perform the Restore request2577067

An interface is required to display the list of media servers that are available for restoring aselected backup.

2617695

Bundle of fixes for NetBackup 7.1.0.4 SAN Client Fibre Transport media server issues.2748951, version 2

A one-time script was created to address an issue with removing image fragments. The scriptis not included in any other release vehicle.

2829356

Windows push installations fail during Virtual File Filter (VFF) driver installation.2879211


A one-time script was created to address an improperly decommissioned media server. Thescript is not included in any other release vehicle.

2961469

A one-time script was created to address an issue with deleting a disk pool. The script willnot be included in any other release vehicle.

2968146

Microsoft SQL restores fail with the following error if the media server is running Windowsand the restore takes longer than one hour: "restored image image_name - (socket readfailed (23))".

2969133

Sharepoint GRT backup of databases having non-English characters fail with file read failed- status 13.

3026930

58About the NetBackup 7.5.0.7 release contentNetBackup 7.5.0.7 Emergency Engineering Binary (EEB) listing


Table A-1 NetBackup 7.5.0.7 EEB Listing (continued)


Restore and verify operations for large SharePoint content databases fail with the followingerror: "Raw partition size gigabytes does not match".

3028111

A one-time script was created to fully remove a media server by the nbdecommission tool -Exit status 20. The script will not be included in any other release vehicle.

3029484

An Advance Success Rate report does not correctly report the number of successful andfailed jobs.

3043782

An Exchange GRT restore that is redirected to a different folder in the original mailbox failswith server status = 2810, but still works correctly when restored to the original mailboxlocation.

3044819

A one-time script was created to delete a disk pool. The script will not be included in anyother release vehicle.

3051990

A Fibre Transport (FT) media server can encounter a problem with the FT server process(nbftsrvr) stopping with the following error: "SCPALDMA Assertion failed".

3053482

The Fibre Transport (FT) client process (nbftclnt) crashes.3055406

For the SAN Client Fibre Transport client process (nbftclnt), turn on the'FTCLIENT_VALIDATE_VIA_CHECK_CONDITION' functionality by default.

3058479

Storage lifecycle policy (SLP) managed duplications fail when writing to a storage unit groupthat is set to Failover where the first storage unit was full or unavailable.

3064454

A one-time script was created to delete a disk pool which cannot be removed. The script willnot be included in any other release vehicle.

3070024

A memory issue causes the storage pool daemon (spoold) to exit abruptly when runningMSDP on the Solaris platform.

3073941

Image data collector fails on a master server with org.omg.CORBA.OBJECT_NOT_EXISTserver-side exception.

3086115

The NetBackup DatabaseManager (bpdbm) fails to connect to the database with the followingconnection error: "Found server but communication error occurred".

3091012

Image collection eventually stops and the OpsCenter web interface becomes unresponsive.3103018

The dbbackup.exe process crashes while browsing backup images on an SQL mirroringconfiguration setup.

3112672

NetBackup OpsCenter data collection for images fails with a communication exception.3115248

Image data collection fails with a "CORBA.OBJECT_NOT_EXIST" error.3116644




The Fibre Transport server process (nbftsrvr) exits abnormally. The nbfdrv64 process exitswith segmentation fault.

3122190

OpsCenter server fails and services are unavailable with Java JRE errors.3128404

A multistreamed SAP restore fails on Linux because the bprestore command is not properlyformatted.

3129891

OpsCenter does not show Appliance Hardware details for NetBackup 5220 appliance v 2.5.23130689

Bundle of fixes to resolve the various issues of jobs status not being reflected correctly in theActivity Monitor.

3134161, version 2, 1

On AIX media servers that use load balancing, MPMS avg_freemem is calculated properlywhile load_avg is calculated as 0 regardless of the actual load.

3134396

The PureDisk wrapper 'pd_getaddrinfo' does not retry on EAI_AGAIN when DNS is busy.3136591, version 1

Unable to save 'Scheduled Jobs' filters in the 'Planning Activity - Scheduled Job - All Jobs'report.

3136787

For virtual machines with greater than 10 disks, VMware Virtual Disk Development Kit (VDDK)returns unordered disk IDs. The disks are added to the catalog in an incorrect order andcause an issue when a restore to multiple datastores is performed.

3139802

Browsing for backups with the SQL agent skips backups and fails with error 'because itcontains metadata not recognized by the current version of NetBackup'

3139929

The 'Override policy volume pool' policy option is grayed-out under the 'Change Schedule -Attributes' tab and 'Media and Device Manager - Media - Volume Pools'. If 'Catalog Backup'has been selected for a volume pool, then it cannot be deselected.

3141517

A DB2 restore fails with 'SQL2062N' if the backup spans three days or more.3142388

A DB2 restore fails with 'SQL2062N' if the backup spans three days or more.3143477

A Fibre Transport (FT) media server can encounter a problem with the Fibre Transport serverprocess (nbftsrvr) stopping due to an assertion failure.

3143954

Intermittently, media server name and media server ID values are not being passed toOpsCenter for jobs that re-try.

3147647

The dbbackup.exe process crashes while browsing history.3149184

An interface is required to display the list of media servers that are available for restoring aselected backup.

3149995




The NetBackup Backup, Archive, and Restore interface does not provide a way to select amedia server to be used for a restore operation.

3150002

A one-time script was created to address the disk pool deletion issue. The script will not beincluded in any other release vehicle.

3157563

When the source database and destination database names and instance names are identical,a DB2 alternate client roll-forward fails because the backup following the roll-forward tries torun on the source client instead of the destination.

3162199

The NetBackup Domain Network Analyzer (nbdna) is unable to execute with some versionsof sudo.

3162955

Single file restore from Flashbackup image gets an assert error when restoring a WindowsSIS file.

3177452

After a Hyper-V backup, the virtual hard disk (VHD) file fails to show up in the browser andcannot be restored. Backup is successful and other files can be browsed and restored.

3177454

An Oracle snapshot backup fails with status code 31.3177858

A one-time script was created to remove an old MSDP disk pool. The script will not be includedin any other release vehicle.

3178628

The NetBackup Domain Network Analyzer (nbdna) is unable to execute with some versionsof sudo.

3179023

Hot catalog backups fail with status code 67 (client backup failed to read the file list) because.f files are larger than 4GB.

3180090

Redirected Exchange GRT fails if the Client Access Server (CAS) is not also a mailbox server.3180805

Bundle of fixes to resolve the various issues of jobs status not being reflected correctly in theNetBackup Activity Monitor.

3182935, version 2, 1

A pipe is always granted the physical node. However, when a backup with the app_clusteris registered with Enterprise Media Manager (EMM), the backup always goes by local areanetwork (LAN).

3182981

The NetBackup Policy Execution Manager (nbpem) stops scheduling jobs, but immediateand user backups still work. The nbpem process must be restarted to get scheduling started.

3184036

Backups of checkpoint files exhibit performance degradation.3184554

When VMware backups are run a message will be seen in the Activity Monitor stating thatthe snapshot will not be deleted.

3187365




The 'Apply' button is not always available on the 'Client' tab.3187497

A multistreamed SAP restore fails on SUSE Linux.3187911

A one-time script was created to remove a disk pool with the name 'dp_pddo_poc' fromEnterprise Media Manager (EMM) database. The script will not be included in any otherrelease vehicle.

3189047

Catalog backups failing with status code 67 'client backup failed to read the file list', causedby .f file is larger than 4GB.

3194255

The Front-End Terabytes (FETBs) report shows the same value for multiple master servers.3194916

Storage lifecycle policy (SLP) managed duplications fail when writing to a storage unit groupthat is set to Failover where the first storage unit was full or unavailable.

3195038

A one-time script was created to remove MSDP defined on the master server. The script willnot be included in any other release vehicle.

3195705

Alternate and self-restores of a Bare Metal Restore (BMR) Windows client in Citrix guest failwith the error message "Failed to create partition". This issue results from an incompatibilitywith Citrix Xen drivers in a BMR recovery environment.

3195898

Adding a NetBackup 7.5 client to a Solaris 10 Update 11 shared resource tree (SRT) fails.3197333

Incremental backups of 'EFI System Partition' failing with status code 1.3198816

A one-time script was created to address an issue where a media server was accidentallyadded as a master server in the Enterprise Media Manager (EMM). The script will not beincluded in any other release vehicle.

3199296

Running the bpchangeprimary command by pool name and policy name fails to changeimages.

3200294

Use secure version of tomcat3200840

A SharePoint document library restore succeeds, but the associated informational columnsare missing.

3202205

Inconsistent job data is shown in the Activity Monitor.3203750, version 2, 1

SharePoint child backups fail with status code 196 when a new stream is added.3204762

Inaccurate calculation of capacity and traditional licensing reporting in the NetBackupDeployment Utility (nbdeployutil).

3204999, version 1





3205000, version 1


3205001, version 1


3205002, version 1


3205003, version 1


3205004, version 1


3205005, version 1


3205006, version 1


3205007, version 1


3205008, version 1


3205009, version 1


3205010, version 1


3205011, version 1


3205012, version 1


3205013, version 1

There are millions of "vfm_extract_frag_info_VxFIv5: input_frag_id" messages in theNetBackup Database Manager (bpdbm) log file with VERBOSE = 0 or at default levels.

3205042

A one-time script was created to address a specific condition where a disk pool could not bedeleted by NetBackup commands. The script will not be included in any other release vehicle.

3206406




A long-running pruning phase of a cleanup job prevents catalog compression from running.3206707, version 2, 1

BMR restores of Windows Server 2008 and newer clients fail with error messages in thebmrrst log that are similar to the following: "butils.cpp:RestoreASRData() Failed to move file[C:\BMR\SCC\Automated System Recovery\e\bootmgr] --gle=2."

3206889

A one-time script was created to remove a reference to a decommissioned media server inthe database. The script will not be included in any other release vehicle.

3207282

A memory issue causes the storage pool daemon (spoold) to exit abruptly when runningMSDP on the Solaris platform.

3208195

An Advanced Success Rate report fails because of a daylight saving time (DST) effect whenthe selected time range falls within February 16th and November 21st.

3210144

Cumulative incremental backups can be much slower in NetBackup 7.5 than they were inversion 7.1.

3210493

The NetBackup Administration Console shows zero disk pools under 'Device Monitor - DiskPools' if it doesn't have an AdvancedDisk license.

3211336

A one-time script was created to address a condition where the deletion of a disk pool wasnot possible when the storage server was already removed. The script will not be includedin any other release vehicle.

3212208

Various components are slow to load and appear to hang when broken Network File System(NFS) mounts are present. This issue can cause backups to fail with status code 2106.

3212481

A large Oracle database (13TB) backup failed with status code 6 and the following errormessage: "ORA-27192: skgfcls: sbtclose2 returned error - failed to close file".

3214359

A Disk Pool Full alert gets generated only after the high water mark is reached, which resultsin failed backup jobs.

3215626

A one-time script was created to address the removal of disk pool. The script will not beincluded in any other release vehicle.

3215794

A one-time script was created to remove disk pools from an environment. The script will notbe included in any other release vehicle.

3216862

Port of fix from ET3202107 for 7.5.0.43217089

The PureDisk wrapper 'pd_getaddrinfo' does not retry on EAI_AGAIN when DNS is busy.3218048

The Fibre Transport client process (nbftclnt) on AIX does not discover the 'ARCHIVE' Pythondevices that are associated with /dev/rmtXX device paths when XX is greater than 99.

3219871




A one-time script was created to address the condition where deletion of a disk pool was notpossible when the storage server was already removed. The script will not be included inany other release vehicle.

3221316

In the NetBackup Backup, Archive, and Restore interface under the 'Restore' tab, the 'Sourceclient for restores' list only contains the master server.

3221651

During cleanup, the NetBackup Database Manager (bpdbm) process hangs or takes a greatdeal of time processing. This behavior is observed in the case of a corrupt .f file with millionsof records.

3222403

A one-time script was created to remove entries from the "DBM_DRMedia" table in order toremove the "foreign media server" entry from the database. The script will not be includedin any other release vehicle.

3224295

A one-time script was created to remove a disk pool and deleted image fragments for acustomer environment. The script will not be included in any other release vehicle.

3225647

A one-time script was created to remove a media server from the NetBackup database. Thescript will not be included in any other release vehicle.

3225929

Unable to backup the registry (NTUSER.DAT) when a user is not logged in.3226495

Restoring to original location does not restore the hardware version when the box is checkedin Backup, Archive, and Restore interface.

3226695

Enterprise Vault partition backups fail with status code 156 for mounted partitions.3227128

The NetBackup Backup-and-ArchiveManager (bpbkar) does not correctly send file informationto the NetBackup Backup-and-Restore manager (bpbrm) for the files that contain a new linein the file name. The result is a bpbrm core dump issue.

3227367

NetBackup Systems Management (Policies, Scheduling, and so forth.) issue.3228489, version 2, 1

An alternate restore of a client-side encrypted backup between an x86 computer and aSPARC computer fails with status code 11.

3229364

Even though the Bare Metal Restore (BMR) database contains compatible Windows drivers,during a 'Prepare to Restore' operation, a higher-level driver is inserted even though it isincompatible.

3229377

During replication, the NetBackup disk manager (bpdm) process intermittently exits with thefollowing message: "bpbrm is gone".

3230967

Media server reported in top left GUI does not agree with job details. Job details has correctmedia server information.

3231391






A one-time script was created to delete a PureDisk disk pool. The script will not be includedin any other release vehicle.

3234808

An Oracle Volume Shadow Copy Service (VSS) snapshot SLP fails to rotate.3236302

An Oracle snapshot backup fails with status code 31.3236304


3237136

A one-time script was created to delete old disk pool. The script will not be included in anyother release vehicle.

3237452

The Front-End Terabytes (FETBs) report displays incorrect data.3238501

Image lock files have world-writable permissions.3238748

A one-time script was created to address the media server deletion issue with thenbdecommission utility. The script will not be included in any other release vehicle.

3240151

A one-time script was created to address the media server deletion failure with thenbdecommission utility. The script will not be included in any other release vehicle.

3241035

SAP backups of files larger than 4GB fail when 'sort_type' is set to device.3242299

Backups and duplications of Windows guest VMware incrementals fail with the following errorin the PureDisk plug-in log: "fbu_scan_buf: bytesNeeded already set".

3242432

A core dump issue can occur with the NetBackup Backup-and-Archive Manager(bpbkar32.exe) during incremental backup. The logs indicate that it was in the'create_parent_entries' portion of the backup.

3243594

When running a VMWare backup, bpfis.exe can dump core and cause the backup job tofailed with status 13.

3244373

The capacity report for the NetBackup Deployment Utility (nbdeployutil) does not show thecorrect 'Flagged Capacity Figures' when reporting against multiple master servers.

3244927

The JavaWindows Administration Console is unable to browse the backup history on masterservers running earlier versions of NetBackup.

3245196

Processing Exchange files on snapshot takes too long.3248100

During backups, bpbkar can crash due to heap corruption.3251172




NetBackup Cloud issue.3251933

Oracle FRA backup to STU taken after 24+ hours fails.3252489

An alternate restore of a client-side encrypted backup between an x86 computer and aSPARC computer fails with status code 11.

3252796

A one-time script was created to delete a disk pool because image fragments still exist. Thescript will not be included in any other release vehicle.

3253362

Catalog backups fail after several hours with status codes 25 and 50 due to the imageexpiration of a client that is no longer configured in the policy, or in the event of a policychange.

3253473, version 1

A one-time script was created to address an issue with decommissioning media servers. Thescript will not be included in any other release vehicle.

3254621

linux system shows a leak of one semaphore per backup job on the backup host.3255000

Single file restores of an NDMP policy type from and OST_FIM snapshot fail with the following:'DUMP: somefile.txt: No such file or directory'.

3255087

The NetBackup Policy Execution Manager (nbpem) does not honor the 'Retries allowed afterrunday' option.

3256280, version 1

No error is reported, yet the virtual machine backup or restore operation may have failedwhen doing a VMware backup of an offline LUN or a read-only LUN.http://www.symantec.com/docs/TECH208628


** 3256506, version 7,6, 5, 4, 3, 2, 1

Image information intermittently missed for successful job records.3256665

A one-time script was created to remove a disk volume. The script will not be included in anyother release vehicle.

3257184

A Disk Pool Full alert gets generated only after the high water mark is reached, which resultsin failed backup jobs.

3258112

Backup jobs to Data Domain fail when NetBackup Accelerator is enabled.3258831

Single file restores of an NDMP policy type from and OST_FIM snapshot fail with the following:'DUMP: somefile.txt: No such file or directory'.

3260582

Added the force flag to the vxassist command to allow the SmartMove feature of VolumeManager to work with NetBackup snapshots.

3260752

Apache Tomcat upgrade for security.3260932





Deletions of images in NetBackup with SQL-BackTrack for Oracle if 'Legal Hold' is set.3262154

On an AIX client, if the lslv command output contains the 'DEVICESUBTYPE' value, thenBare Metal Restore (BMR) records the wrong file system type during backup which causesthe restore to fail with invalid temporary mount point.

3262659

Restoring to original location does not restore the hardware version when the box is checkedin Backup, Archive, and Restore interface.

3262796

Data collection fails with status code 194 when collecting the Index data type.3263385

NetBackup Fibre Transport issue.3263461

Deletions of images in NetBackup for 'Legal Hold' images for XBSA and SQL-BackTrackagents for Oracle.

3263480

Deletions of images in NetBackup and Oracle if 'Legal Hold' is set.3263484


Prevent the deletions of images in NetBackup and Oracle if Legal Hold is set.3263488


If 'metastat' command shows full device path instead of device name in the output and Solarisclient has Solaris Volume Manager installed, then restore will fails with invalid boot devicepath created for a non-default Solaris Volume Manager client s

3263564


3265176

The NetBackup Policy Execution Manager (nbpem) does not honor the 'Retries allowed afterrunday' option.

3265279

Unable to backup the registry (NTUSER.DAT) when a user is not logged in.3266917

A core dump issue occurs when the nbrbutil -dumptables command is run when the NetBackupEnterprise Media Manager (nbemm) is down.

3269849

Backups of stub files fail with status code 130. NetBackup treats these stub files as sparsefiles.

3270022

Unable to decommission an appliance server that was incorrectly added as a master server.3272381

Running the bpchangeprimary command by pool name and policy name fails to changeimages.

3273745




The 'Override policy volume pool' policy option is grayed-out under the 'Change Schedule -Attributes' tab and 'Media and Device Manager - Media - Volume Pools'. If 'Catalog Backup'has been selected for a volume pool, then it cannot be deselected.

3274072

If multiplexing is enabled in a VMware policy, the backup job can fail with status code 73.3274742

The PureDisk wrapper 'pd_getaddrinfo' does not retry on EAI_AGAIN when DNS is busy.3275166

The Backup, Archive, and Restore program for Windows crashes when the 'Backup' windowis closed using the Close button (X) on the application window.

3275765

The keyword 'VXDBMS_VALIDATION =OFF' in the vxdbms.conf file does not work correctly.It should stop validating the database for a hot catalog backup.

3277447

An Exchange granular restore fails with the following error when the mailbox name containsa forward slash (/): "no entity was found".

3277716

Oracle backup fails which causes removal of unwanted images.3277737

A one-time script was created to address the wrong master server references deletion failure.The script will not be included in any other release vehicle.

3281714

The dbbackup.exe process crashes when the user tries to browse the backup with the SQLserver agent interface.

3282319

The NetBackup Enterprise Media Manager process (nbemm) hangs due to different queriesgetting stuck.

3284351

VMware backup job fails in the backup and archive manager (bpbkar) with status code 73 ifmultiplexing is enabled.

3284494

A one-time script was created to delete a PureDisk disk pool and one remaining image. Thescript will not be included in any other release vehicle.

3284692

Some jobs missing during Job data collection


** 3286233

A catalog cleanup runs while a catalog recovery is active, causing newly restored catalogfiles to be deleted prematurely.

3286399

A catalog cleanup runs while a catalog recovery is active, causing newly restored catalogfiles to be deleted prematurely.

3286500

VMware incremental backups with block level incremental backup (BLIB) enabled fail withstatus codes 40 and 13. The VMware session timeout and read timeout occur becausecreating a bitmap for modified sectors takes more time for the virtual disk.

3287240





A one-time script was created to address an issue where an MSDP storage server could notbe deleted. The script will not be included in any other release vehicle.

3288413

Use secure version of tomcat3288749

Failed to remove a disk pool, media server, and NDMP server through commands.3289804

TIR pruning fails due to fetching invalid image information from NBDB.3289890


Various Sybase defects.3292292

VMware backups leak semaphores on Linux backup hosts.3292295

A number of data collectors show a "Not Started" status in OpsCenter.3294558

An Exchange granular restore fails with the following error when the mailbox name containsa forward slash (/): "no entity was found".

3295967

NetBackup OpsCenter does not show some of the jobs that are seen in the Activity Monitor.


** 3298566

NetBackup OpsCenter does not show some of the jobs that are seen in the Activity Monitor.


** 3298572

Snapshot backups on a Windows Server 2008 R2 computer with an EFI partition fail withstatus code 1.

3299072

Job status not being reflected correctly in the NetBackup Activity Monitor.3300058

A core dump issue occurs while running the nrbutil -dumptables command when theNetBackup Enterprise Media Manager (nbemm) is down.

3300573

A VxMS error occurs in reading a logical volume manager (LVM) disk if the disk also containsa master boot record (MBR) magic number.

3303030

Shared Resource Tree (SRT) creation fails for Solaris SPARC 10 Update 10 with the followingerror message: "[Error] V-125-447 Unable to install Symantec NetBackup Client softwareinto the SRT."

3304711



Support for GUID partition table (GPT) boot disk. This support addresses an issue with theerror "Found 0 Virtual Volumes".

3307842






The Activity Monitor continually reports "Unknown Job Type" following an upgrade of themaster server.

3308782, version 1


The "bpimage -update -keyword" command does not work with NetBackup 7.5.0.x.3309127

A one-time script was created to remove three disk pools. The script will not be included inany other release vehicle.

3310421

The 'ndmp_end_notify' script is not called when using NDMP multiplexing.3311027

When a catalog backup fails, the NetBackup Database Manager (bpdbm) crashes whilepreparing to run the disaster recovery email script.

3311495

A one-time script was created to remove an unwanted master server entry from the EnterpriseMedia Manager (EMM) database. The script will not be included in any other release vehicle.

3315572

Enterprise Vault partition backups fail with status code 156 for mounted partitions.3315839

During snapshot deletion sessions, nbdelete may start many unnecessary bpdm processesfor snapshot deletion. This issue can cause deletion performance problems.

3316213

Windows Remote Administration Console overflow displaying KBytes written to media forlarge backup(approx. 5.5 TB).

3316947

Trap recipients are being removed after a copy of alert policy has been made.3320504

The NetBackup Enterprise Media Manager (nbemm) appears to hang and stop logging.3320755

Unable to browse backup images using the MSSQL agent interface for clustered MSSQLdatabases that are configured for mirroring.

3321055

A VxMS error occurs in reading a logical volume manager (LVM) disk if the disk also containsa master boot record (MBR) magic number.

3321609, version 2, 1

Hot catalog backups fail with status code 67 (client backup failed to read the file list) because.f files are larger than 4GB.

3324604

Bundle of fixes to address TIR (True Image Restoration) catalog data pruning and theNetBackup Database Manager (bpdbm) failing to connect to the database.

3325351, version 1

Unable to browse virtual machines for selection. The following is displayed in the bpVMutillogs: "CREATE_CONTAINER_VIEW_ERROR".

3325584

Storage Unit Group set to Failover does not correctly select Storage Units.3331197




A one-time script was created to address a server that was set to the wrong type. The scriptwill not be included in any other release vehicle.

3331244

A one-time script was created to remove a disk pool that is no longer associated with anystorage server. The script will not be included in any other release vehicle.

3331462

Unable to browse or discover virtual machines on vCenter 4.1.3332354

The 'ndmp_end_notify' script does not get called when multiplexing (MPX) is selected in thepolicy schedule and on the destination storage unit has MPX greater than 1.

3333479

Failed to retrieve virtual hard disk (VHD) file during restore. However, file browsing availablethrough Normal backup type.

3333826


3335192

In 7.5.0.6, ESX Server button during Alternate Location restore fails3335725

Unable to back up the clients that have hostnames that contain a trailing dot (period).3335748

A one-time script was created to remove an orphaned disk pool. The script will not be includedin any other release vehicle.

3336238

The cache garbage collection creates a large number of events that do not get removed fromthe NetBackup Deduplication Manager (spad) events table.

3336859

A one-time script was created to decommission a media server that has contents stuck in'DBM_MAIN' and 'DBM_DRMedia'. The script will not be included in any other release vehicle.

3337097

A long-running pruning phase of a cleanup job prevents catalog compression from running.3338332, version 1

Unable to browse or discover virtual machines on vCenter 4.1. The error"CREATE_CONTAINER_VIEW_ERROR" is seen in the bpVMutil logs.

3339508

The VMware ESX server search button fails during an alternate location restore.3341375

Tar32.exe process can crash during a System State restore on Windows 2003.3342070

The "bpimage -update -keyword" command does not work with NetBackup 7.5.0.x.3348788

A one-time script was created to address a problem decommissioning media servers whendisk objects still exist. The script will not be included in any other release vehicle.

3356167

A one-time script was created to remove an MSDP NDMP storage server from three servers.The script will not be included in any other release vehicle.

3356355




A one-time script was created to address an issue where a host could not be deleted. Thescript will not be included in any other release vehicle.

3357356

A one-time script was created to remove an orphaned disk group and disk volume. The scriptwill not be included in any other release vehicle.

3357437

Restore fails in Exchange 2013 server due to a Microsoft bug that can result in backups thatcannot be restored with the roll-forward option


** 3357483

SharePoint 2010 GRT backup fails with error code 13 on the host running Chinese locale3357862

If a system has more than 25 IPv6 interfaces, then the Private Branch Exchange (PBX) serverprotocol in the PBX C library fails.

3358176

Backups may become inaccessible if the nbdecommission command is run incorrectly forthe removal of an MSDP server.

3358533


3383267

NetBackup Agent for Windows Client issue.3385162



NB 7507 Release Notes

Documents

Transcript of NB 7507 Release Notes