symantec netbackup release notes - veritasdownload1.veritas.com/support/products/netbackup... ·...

Symantec NetBackup™Release Notes

UNIX, Windows, and Linux

NetBackup 7.0

20654069

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

Documentation version: 7.0

PN: 20654069

Legal NoticeCopyright © 2009 Symantec Corporation. All rights reserved.

Symantec, the Symantec Logo, Veritas and NetBackup are trademarks or registeredtrademarks of Symantec Corporation or its affiliates in the U.S. and other countries. Othernames may be trademarks of their respective owners.

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

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

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

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

Symantec Corporation350 Ellis StreetMountain View, CA 94043

http://www.symantec.com

Printed in the United States of America.

10 9 8 7 6 5 4 3 2 1

http://www.symantec.com

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

Symantec’s maintenance offerings include the following:

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

■ Telephone and Web-based support that provides rapid response andup-to-the-minute information

■ Upgrade assurance that delivers automatic software upgrade protection

■ Global support that is available 24 hours a day, 7 days a week

■ Advanced features, including Account Management Services

For information about Symantec’sMaintenance Programs, you can visit ourWebsite at the following URL:

www.symantec.com/techsupp/

Contacting Technical SupportCustomerswith a currentmaintenance agreementmay access Technical Supportinformation at the following URL:


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

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

■ Product release level

■ Hardware information

■ Available memory, disk space, and NIC information

■ Operating system



■ Version and patch level

■ Network topology

■ Router, gateway, and IP address information

■ Problem description:

■ Error messages and log files

■ Troubleshooting that was performed before contacting Symantec

■ Recent software configuration changes and network changes

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


Customer serviceCustomer service information is available at the following URL:


Customer Service is available to assist with the following types of issues:

■ Questions regarding product licensing or serialization

■ Product registration updates, such as address or name changes

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

■ Latest information about product updates and upgrades

■ Information about upgrade assurance and maintenance contracts

■ Information about the Symantec Buying Programs

■ Advice about Symantec's technical support options

■ Nontechnical presales questions

■ Issues that are related to CD-ROMs or manuals



Maintenance agreement resourcesIf you want to contact Symantec regarding an existing maintenance agreement,please contact the maintenance agreement administration team for your regionas follows:

[email protected] and Japan

[email protected], Middle-East, and Africa

[email protected] America and Latin America

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

Enterprise services that are available include the following:

These solutions provide early warning of cyber attacks, comprehensive threatanalysis, and countermeasures to prevent attacks before they occur.

SymantecEarlyWarningSolutions

These services remove the burdenofmanaging andmonitoring security devicesand events, ensuring rapid response to real threats.

Managed Security Services

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

Consulting Services

Educational Services provide a full array of technical training, securityeducation, security certification, and awareness communication programs.

Educational Services

To access more information about Enterprise services, please visit our Web siteat the following URL:

www.symantec.com

Select your country or language from the site index.

mailto:[email protected]



www.symantec.com

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

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

New features in NetBackup .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11NetBackup deduplication .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

About client deduplication .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13About media server deduplication .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

About Symantec OpsCenter ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14About Symantec OpsCenter Analytics ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15About NetBackup for VMware .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15Guided Recovery .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16New database features and enhancements ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Exchange 2010 support ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16Windows 7 and Windows 2008R2 client support ... . . . . . . . . . . . . . . . . . . . . . . . 17NetBackup for Enterprise Vault agent ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17NetBackup for Hyper-V agent ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17Improved SharePoint Granular Recovery .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

About NetBackup support utilities ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18NetBackup installation and deployment enhancements ... . . . . . . . . . . . . . . . . . . . . 19About back-level administration capabilities by the NetBackup-Java

console ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22About Platform proliferation for NetBackup 7.0 ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

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

About server and client platform support ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23About platform and operating system support changes ... . . . . . . . . . . . . . . 23About NetBackup Compatibility Lists ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24About the deduplication host supported platforms .... . . . . . . . . . . . . . . . . . . . 26About platform life cycles ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

About Operating systems not supported as of NetBackup 7.0 andbeyond .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

NetBackup binary sizes ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30Platforms supporting the NetBackup Administration Consoles for

UNIX .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33About NetBackup backward compatibility ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

Contents

Chapter 3 Product Dependencies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

Operating system patches and updates ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39About supported versions of VxFS and VxVM ..... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

Chapter 4 Operational Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

Operational Notes in NetBackup .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50NetBackup installation and start-up notes ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

NetBackup media and rebranding changes ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50General installation and upgrade items .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53NetBackup LiveUpdate ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56Secure push install .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56NetBackup cluster ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

NetBackup Documentation Notes ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58Internationalization and localization Notes ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58NetBackup Bare Metal Restore ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61General NetBackup operational notes ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66NetBackup Access Control ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67NetBackup database agents ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

Lotus Notes agent ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69NetBackup for Microsoft Exchange .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70NetBackup for Microsoft SharePoint ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73SQL server agent ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75Sybase server agent ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75About NetBackup Enterprise Vault Agent ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76

NetBackup Hyper-V .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76NetBackup interfaces ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77

NetBackup Administration Console for Windows .... . . . . . . . . . . . . . . . . . . . . . 77NetBackup java interfaces ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78Storage unit configuration .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81

About Symantec OpsCenter ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81NetBackup media and device management ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82

Media Sharing .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82Enterprise Media Manager ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82

SAN Client and Fibre Transport ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83SharedDisk support in NetBackup 7.0 and later ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84NetBackup AdvancedDisk option .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84NetBackup Client Deduplication .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84About the NetBackup Media Server Deduplication Option .... . . . . . . . . . . . . . . . . 85PureDisk Deduplication Option (PDDO) .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85NetBackup Snapshot Client ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86NetBackup commands and utilities ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88NetBackup OpenStorage Option .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89

Contents8

NetBackup Disk Storage units ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89NetBackup Vault ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90NetBackup for VMware .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92

Chapter 5 End of Life Notifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95

End of life notifications .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95About general NetBackup notifications .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95

About features, enhancements, and commands no longersupported .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96About general NetBackup features no longer supported .... . . . . . . . . . . . . 96About database functions no longer supported .... . . . . . . . . . . . . . . . . . . . . . . . . 97About NetBackup commands no longer supported .... . . . . . . . . . . . . . . . . . . . . 98

Chapter 6 Related Documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99

About related NetBackup documents ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99About NetBackup release notes ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100About getting started guides ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100About installation guides ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100About administrator’s guides - agents and options .... . . . . . . . . . . . . . . . . . . . . . . . . 101About user’s guides ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104About the device configuration guide .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104About the Troubleshooting guide .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105About NetBackup command documents ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105

Appendix A Windows Logo Certification information . . . . . . . . . . . . . . . . . . . . . . 107

About Windows Server 2008 R2 Logo Certification .... . . . . . . . . . . . . . . . . . . . . . . . 107

9Contents

Contents10

New Features

This chapter includes the following topics:

■ New features in NetBackup

■ NetBackup deduplication

■ About Symantec OpsCenter

■ About Symantec OpsCenter Analytics

■ About NetBackup for VMware

■ Guided Recovery

■ New database features and enhancements

■ About NetBackup support utilities

■ NetBackup installation and deployment enhancements

■ About back-level administration capabilities by the NetBackup-Java console

■ About Platform proliferation for NetBackup 7.0

New features in NetBackupSymantec NetBackup™ 7.0 contains many new features and enhancements thatincrease the scalability and functionality of NetBackup for its large enterprisecustomers.

The following list highlights some of themajor features that compriseNetBackup7.0.

■ Integrated deduplication:

■ Client deduplication

1Chapter

■ Media server deduplication

■ OpsCenter:

■ Convergence of NOM and VBR

■ Improved ease-of-use

■ Additional base reporting functionality

■ Direct upgrade path

■ Expanded and simplified deployment

■ OpsCenter Analytics:

■ Turnkey operation to enable advanced, business reporting

■ Improved reporting features

■ NetBackup for VMware:

■ Fully integrated with VMware vStorage APIs

■ New VM and file recovery from incremental backups

■ New recovery wizard

■ Tighter vCenter integration

■ Guided application recovery for Oracle databases

■ New database agents and enhancements to existing agents:

■ Exchange 2010 support

■ Windows 7/2008R2 client support

■ Enhancements to the NetBackup Enterprise Vault agentSupport all EnterpriseVault 8.0 databases using theEnterpriseVaultAgentincluding the Fingerprint database, FSAReporting database, and AuditingdatabaseEnterprise Vault 8.0 support for granular quiescenceEnterprise Vault Migrator is now included with NetBackup

■ Enhancements to the NetBackup for Hyper-V agentNew file-level incremental backupsTwo types of off-host backupHyper-V R2 and Cluster shared volumes (CSV)Flexible VM identification

■ Improved SharePoint Granular Recovery

■ This release adds the following proliferation support:

New FeaturesNew features in NetBackup

12

HP-UX 11.31 IA BMR master server support for NetBackup 7.0■

■ BMR WINPE 2.1 support

■ Java user interface support on RHEL 5 systems

■ NetBackup Support Utility (nbsu) enhancements

NetBackup deduplicationNetBackup now provides integrated data deduplication within NetBackup. Youdo not have to use the separate PureDisk interface to deduplicate data. You useNetBackup interfaces to install, configure, andmanage storage, servers, backups,and deduplication. Symantec packaged PureDisk into a modular engine, andNetBackupuses the PureDiskDeduplication Engine (PDDE) to deduplicate backupdata.

You can use NetBackup deduplication at 2 points in the backup process:

■ On a NetBackup client. The NetBackup client deduplicates its own data andthen sends it directly to a storage server, bypassing media server processing.Becauseuniquedata segmentsonly are transferred, this option reducesnetworkload.See “About client deduplication” on page 13.

■ Onamedia server. NetBackup clients send their backups to aNetBackupmediaserver, which deduplicates the backup data. The media server writes the datato the storage and manages the deduplicated data.See “About media server deduplication” on page 14.

See the NetBackup Deduplication Guide.

About client deduplicationThis feature permits the deduplication of data from the source (a NetBackupclient). It allows only unique data segments to bemoved across the LANand storedupon the media server’s embedded deduplicated storage.

Benefits of client deduplication feature are:

■ Faster backups occur because only the new data or the file segments thatoccurred since the last backup is moved and stored

■ Permits a real Incremental Forever approach

■ Less impact on the LAN

■ Reduced backup windows

■ Can be combined with Application agents

13New FeaturesNetBackup deduplication

■ Supported over all Tier 1 NetBackup clients (for example, Windows, Linux,HP-UX, Solaris, and AIX)

■ Backup policy integrated

About media server deduplicationThis feature enables the deduplication of streaming data on themedia server andhas it stored upon the media server’s embedded deduplicated storage.

Benefits of media server deduplication:

■ A more simplified installation and configuration. The deduplication softwareis installed together with the media server software

■ Optimized deduplication for a number of application backup agents

■ Usage of commodity disk for deduplication

About Symantec OpsCenterSymantec may supply additional information for this feature after it has beenreleased for general availability. The followingTechnote on the Symantec SupportWeb site contains additional information about this feature if any is necessary.

See, http://entsupport.symantec.com/docs/337179.

The following enhancements comprise the OpsCenter feature:

■ Convergence of NOM and VBRSingle deployment configuration and user interface for monitoring, alerting,and reporting functionality previously available in NOM and VBR.

■ Improved ease-of-useSymantec corporate user interface (UI) standards for enterprise products. Thisenhancement offers simplified navigation, improved task efficiency, and aprofessional look and feel. In addition, a restructured standard report has beenadded that supports single-click execution along with a quick sort and filtercapability for additional detail.

■ Additional base reporting functionality

■ Point-and-click reports are now available across NetBackup, Backup Exec,PureDisk, and Enterprise Vault products.

■ Anenhanced set of standard reports is nowoffered for complete operationstracking. Example reports includedrive throughput, virtualizationcoverage,configurable success rate, and skipped files.

■ Direct upgrade path

New FeaturesAbout Symantec OpsCenter

14

This feature enables you to configure direct upgrade path from existing NOMand VBR installations.

■ Expanded and simplified deployment

■ OpsCenter server supports all NetBackup master server platforms (suchas, Windows, Solaris, Linux, and HP-UX Itanium).

■ OpsCenter server installationonNetBackupmaster server for single-domainadministration.

■ Dedicated OpsCenter server for multi-domain visibility and management.

■ OpsCenter installationsmust bemade directly from the standaloneOpsCentermedia or image.

About Symantec OpsCenter AnalyticsThis feature provides a turnkey operation that provides improved reporting suchas advanced, business reporting and improved graphics. (Business reporting waspreviously available with VBR.)

The new OpsCenter Analytics package includes the features associated wtihSymantec OpsCenter and the following features:

■ Historical trending and predictive forecasting

■ Complete report customization

■ Support for third-partydataprotectionproducts suchasEMCLegatoNetworkerand IBM Tivoli Storage Manager

About NetBackup for VMwareThe feature provides the following new enhancements in NetBackup 7.0:

■ Fully integrated with VMware vStorage APIsVCB is no longer required. This feature eliminates the VCB copy of a VMsnapshot to the VCB proxy staging area. NetBackup backs up the snapshotdirectly from the ESX server.

■ New virtual machine (VM) and file recovery from incremental backupsVMwarevSpherenowprovides block-level incrementalVMbackups.Moreover,NetBackup now provides VMware and file-level recovery from the same set offull and incremental backups.

■ New Recovery Wizard

15New FeaturesAbout Symantec OpsCenter Analytics

This wizard simplifies the process of performing a direct VM recovery orredirected VM recovery.

■ Tighter vCenter integrationMore VMware identifiers and attributes are available when you configure aNetBackup policy. That includes the VMware hostname, display name, UUID,IP address, virtual center, datacenter, ESX platform, and others.

Guided RecoveryThe Guided Recovery feature enhances the NetBackup Oracle agent to providebetter functionality for performing Oracle Restore and Recovery operations.Specifically, Guided Recovery clones an Oracle database from a backup, andsimplifies the process of creating a new database from backups of an existingdatabase. Guided Recovery uses an Oracle cloning wizard that executes on thenew OpsCenter graphical user interface.

New database features and enhancementsThe following subsections describe enhancements toNetBackup agents thatwererecently offered such as theNetBackupEnterpriseVault agent and theNetBackupfor Hyper-V agent. In addition, enhancements have been made to support newimprovements to SharePoint Granular Recovery, and a new Granular Recoveryfor Active Directory feature.

Exchange 2010 supportNetBackup introduces support for Exchange 201, including the following features:

■ Backups of Exchange 2010 databases on a standalone server or in a DatabaseAvailability Group (DAG). Supported backups include local and off-hostsnapshots, backups usingGranular RecoveryTechnology (GRT), and local andoff-host instant recovery. Instant recovery backups can create only a snapshotor a snapshot and a create a copy on the storage unit.

■ Automatic detection of the preferred database copy or the active databasecopy in a DAG for backup and restore operations.

■ Dynamic allocationof a storageunit that is basedon the server list and returnedat the start of a backup.

Non-snapshot and mailbox-level backups are limited to Exchange 2007 andExchange 2003.

New FeaturesGuided Recovery

16

Windows 7 and Windows 2008R2 client supportThis release of NetBackup provides NetBackup client support for the Windows 7desktopplatform. In addition, theNetBackup client and agents,media server, andmaster server nowsupport theWindows2008R2operating system. (TheWindows2008 R2 is exclusively 64-bit from Microsoft.)

NetBackup for Enterprise Vault agentThe NetBackup for Enterprise Vault agent greatly simplifies data protection forthe Enterprise Vault servers. It protects all of the Enterprise Vault partitions andtheir associated databases. The agent supports disaster recovery of a partitionand databases. Moreover, it also supports recovery of individual files within apartition.

The following enhancements have been made to the NetBackup Enterprise Vaultagent for this release:

■ Inclusion of all Enterprise Vault 8.0 databases using the Enterprise VaultAgent. That includes the fingerprint database, the FSA Reporting database ,and the auditing database.

■ An enhanced, automated process of backing up your Enterprise Vaultenvironment using the Enterprise Vault Agent.

■ Enterprise Vault 8.0 Support for granular quiescenceYou can now back up and restore using the Enterprise Vault Agent at a moregranular level.

■ Enterprise Vault Migrator is now included with NetBackupTheEnterpriseVaultmigratory isnow includedwithNetBackup7.0. Previously,that was a separate download.

NetBackup for Hyper-V agentThe NetBackup for Hyper-V agent protects virtual machines (VM) by backing upthe virtual hard drive (VHD) images. From the image backup, you can restore theentireVMor individual fileswithin theVM.That is donewithout anyVHDstaging;only the files you select are recovered from tape. Automatic detection of all VMswithin the Hyper-V server simplifies the policy setup.

The following enhancements have beenmade to theNetBackup forHyper-V agentfor this release:

■ New file-level incremental backups

17New FeaturesNew database features and enhancements

NetBackup for Hyper-V now supports incremental backups, to complementthe dual purpose full backups. Now, file-level recovery is available from bothfull backups and incremental backups.

■ Two types of off-host backupNetBackup for Hyper-V now supports off-host backup of VM snapshots onCLARiiONstorage arrays. Support for otherVSS snapshot providerswill follow.Alternatively, using the NetBackup Snapshot Client in the VM to performoff-host backup of volumes is also now supported.

■ Hyper-V R2 and Cluster Shared Volumes (CSV)NetBackup for Hyper-V is now compatible with Hyper-V clusters and the newCSV capability.

■ Flexible VM identificationUse the VM hostname, display name, or UUID when configuring policies.

■ NetBackup 7.0 for Hyper-V supports Hyper-V clustering. However, Hyper-Vcluster support requires a NetBackup 7.0.0.1 patch or later. To obtain thisupdate contact NetBackup Technical Support.

Improved SharePoint Granular RecoveryStarting with NetBackup 6.5.4, the NetBackup for SharePoint Agent offeredadditional,more comprehensive granular recovery capabilities, that included thefollowing:

■ Sites and sub-sites

■ Entire lists, like calendars, tasks, links, discussions, and others

■ Any item(s) from a list

■ Any version of a file

■ Recover files to a folder on disk.

WithNetBackup7.0, you can reap thebenefits of themore comprehensive granularrecovery capabilities alongwith faster granular recoverywith themetadata intact.

About NetBackup support utilitiesNetBackup7.0 includes three support utilities:nbsu,NBCC, andNBCCR. The followinglist summarizes the enhancements that have been made to each utility in thisrelease:

■ NetBackup Support Utility (NBSU)

New FeaturesAbout NetBackup support utilities

18

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

In NetBackup 7.0 this utility has been enhanced to include the following newfeatures:

■ New commands line options have been added.

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

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

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

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

■ NBCCR utilityThe NBCCR utility processes database and catalog repair actions as defined ina special file that you can generate under the guidance of Symantec TechnicalSupport. This file is created as part of the analysis of the data that the NBCCutility collects and any site specific situations.For NetBackup 7.0, this utility contains fixes that address the minor issuesfound in earlier releases.

NetBackup installation and deploymentenhancements

This release ofNetBackup containsmany enhancements in the area of installationand deployment. The following list describes the new changes affecting howNetBackup is deployed, packaged, installed, and updated:

19New FeaturesNetBackup installation and deployment enhancements

■ DVD LayoutNetBackup is now only available on DVD. The product is no longer offered ina CD format.

■ Electronic Software Distribution (ESD) imagesThe DVDimage files are posted and available for download on the FileConnectWebsite. See “About the Electronic SoftwareDistribution (ESD) images" in theNetBackup Installation Guide for more information about how you candownload these images.

■ Deploy basic product license tags.A feature has been added that deploys ISO 19770 standard software asset tagswith NetBackup. That is the first step in NetBackup’s license and deploymentreporting strategy.

■ Simplified Access Control ConfigurationBy more tightly integrating AT support into NetBackup, changes have beenmade that greatly simplify the installation process.

■ LiveUpdate EnhancementsImprovements to the LiveUpdate configurationmake it possible to specify theLiveUpdate server in the policy. That also supports using different LiveUpdateservers in each policy. Changing the server, no longer requires client-sidechanges.

■ UNIX Package ConsolidationIn NetBackup 7.0, most of the add-on products and database agents are nowinstalledwith theNetBackup server or the client package. Separate installationfor these products is no longer needed.

The following products are now included in the NetBackup server package (ifthe platform supports the product):

■ BMR master server

■ NDMP

■ NetBackup Vault

The following products are now included in the NetBackup client package (ifthe platform supports the product):

■ BMR Boot server

■ DB2

■ NetBackup Encryption

■ Informix

■ LiveUpdate agent

New FeaturesNetBackup installation and deployment enhancements

20

■ Lotus Notes

■ Oracle

■ SAP

■ Snapshot Client

■ Sybase

The binaries for the listed products are laid down with the server or the clientpackage. A valid license is still required to enable the product. If productconfiguration was required previously (such as db2_config), configuration isstill required.(For Solaris server upgrades, the older versions of any listed products heremust be removed before an upgrade to NetBackup 7.0. For example,VRTSnbdb2,SYMCnbdb2,VRTSnbenc,SYMCnbenc, andothers.The installationscript displays a list of the packages it finds that must be removed.)The Japanese and the Chinese language packages remain as separate add-ons.The process to install and upgrade these products remains the same.

■ The following changes were a result of our internal “First 24 Hour” usabilitytests that were targeted towards Windows installation improvements:

■ NetBackup is nowcapable of importing client lists froma file. That preventsthe need to individually select hundreds of clients.

■ Multiple simultaneous push installs greatly improve the installationperformance over the previous approach of one client at a time.

■ Improvements have been made to the error logging and reporting. A fullconfiguration summary report now describes what options were selectedfor the install. In addition, all installation logs are nowcaptured in anHTMLformat for a more readable display.

■ Preinstallation checks are run to ensure a successful installation.

■ VxUL Log Directory RestructuringThis change enhances the usability of VxUL logs by putting the logs for eachservice in a unique directory, making it easier for support to find and copy thecorrect logs. In addition, the performance of the vxlogview command isimproved when searching for logs by the OID since this command does notneed to look at all of the VxUL log files for NetBackup, it only opens log filesfor the correct OID.

21New FeaturesNetBackup installation and deployment enhancements

About back-level administration capabilities by theNetBackup-Java console

NetBackup 7.0 provides additional ways to perform back-level administration ofthe supported back-level versions. This includes the packaging and the installationof the NetBackup 6.0 MP7 and NetBackup 6.5.4 versions of the NetBackup-Javaconsole on supported UNIX and Linux platforms.

About Platform proliferation for NetBackup 7.0This section lists the various platform that are new with NetBackup 7.0.

■ Add HP-UX 11.31 IA BMR master server for NBU 7

■ BMR WINPE 2.1 support

■ Java GUI on RHEL 5

New FeaturesAbout back-level administration capabilities by the NetBackup-Java console

22

Supported Platforms


■ About server and client platform support

■ About Operating systems not supported as of NetBackup 7.0 and beyond

■ NetBackup binary sizes

■ Platforms supporting the NetBackup Administration Consoles for UNIX

■ About NetBackup backward compatibility

About server and client platform supportYou can find the NetBackup-supported platform information in variouscompatibility lists on the Symantec Support Web site. These compatibility listsoffer a variety of up-to-date information about the operating systems thatNetBackup andNetBackup features support. This topic also contains the followingtypes of information:

■ Descriptions of the compatibility lists that are on the Symantec Support Website

■ Instructions on how to locate the NetBackup compatibility lists

■ NetBackup backward compatibility information

■ NetBackup binary sizes that include NetBackup media server software andNetBackup client software

About platform and operating system support changesThis release of NetBackup contains many changes and enhancements to thesupported platforms and operatings systems. The following list describes someof the major changes that apply the NetBackup 7.0:

2Chapter

■ All UNIX 32-bit system support has been discontinued. To upgrade thesesystems to NetBackup 7.0, you must first migrate your current NetBackup 6.xcatalogs and databases to a system with a supported platform.However, 32-bit media servers and clients that use NetBackup 6.x arecompatible with 64-bit master servers that use NetBackup 7.0.In addition, NetBackup requires OpenStorage vendor plug-ins to be 64-bit.When you upgrade a media server that is used for OpenStorage to NetBackup7.0, you also must update the vendor plug-in to a 64-bit version.

■ All 64-bit platforms are supported except for FreeBSD clients andMac clients.

■ IRIX and Tru64 are no longer supported.Servers and clients with these operating systems that use NetBackup 6.x arecompatible with NetBackup 7.0 servers.

■ Windows IA64 is supported only as a client.

■ Linux SUSE and Linux RedHat Itanium are no longer supported for use asmaster or media servers. These platforms are only supported as a client.

■ HP-UX PA-RISC is no longer supported as a master server. This platform issupported only as a true media server (media server without the EMM server)or a true client.

■ The support of Linux Red Hat IBM zSeries platforms has switched to 64-bitclient support.

■ Novell NetWare is no longer supported for use as amedia server. This platformis only supported as a client.

About NetBackup Compatibility ListsThe most up-to-date information on supported platforms, peripherals, drives,and libraries is located in various compatibility lists on the Symantec SupportWeb site. The following compatibility lists are available on the Symantec SupportWeb site:

■ TheNetBackupEnterpriseServerandServer7.xOSSoftwareCompatibilityListcontains information about the operating system (OS) level and the versionthat is required to support aNetBackupmaster ormedia server. It also describesthe OS level and the version that is required to support a NetBackup client.Predecessors and successors to the supported operating system levels mayfunctionwithout difficulty, as long as the release provides binary compatibilitywith the supported level.http://entsupport.symantec.com/docs/337048

Supported PlatformsAbout server and client platform support

24

TheNetBackupEnterpriseServerandServer7.xOSSoftwareCompatibilityListcontains information about each of the following NetBackup Enterprisefeatures:

■ NetBackup Enterprise servers and client

■ Bare Metal Restore (BMR)

■ NetBackup Access Control (NBAC)

■ Network Data Management Protocol (NDMP)

■ NetBackup SAN Client and Fiber Transport

■ NetBackup Virtual System compatibility

■ MSEO (Media Server Encryption Option)

■ NetBackup Media Server Deduplication Option

■ NetBackup OpsCenter

■ File System Capability

NetBackup support for a platform or OS version requires platform vendorsupport for that product. The platform support lists thatNetBackupmaintainsare subject to change as vendors add and drop support for platforms or OSversions.

■ TheNetBackup server 7.0 hardware compatibility list includes information forsupported drives, libraries, virtual tape devices, robot-types, fibre-channelHBAs, switches, routers, bridges, iSCSI configurations, and encryption deviceshttp://entsupport.symantec.com/docs/336875

TheNetBackup7.xHardware compatibility list includes information about thesupported drives, robot types, switches, routers, and bridges, and iSCSIconfigurations that coincide with the following hardware:

■ OpenStorage

■ Virtual tape libraries (VTLs)

■ Network Data Management Protocol (NDMP)

■ Host bus adapters (HBAs)

■ Encryption

■ NetBackup Database Agent 7.x Software Compatibility ListThis compatibility list contains themost current platformsupport informationfor NetBackup database agents.http://entsupport.symantec.com/docs/303344

■ NetBackup 7.x Snapshot Client compatibility lists

25Supported PlatformsAbout server and client platform support

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

■ NetBackup 7.x BMR File System and Volume Manager compatibility listshttp://entsupport.symantec.com/docs/303344

See also the NetBackup Bare Metal Restore Administrator's Guide for thefollowing additional compatibility lists:

■ BMR supported shared resource tree (SRT) versions

■ BMR supported file systems and volume managers

■ BMR supported cluster solutions

■ BMR disk space requirements

■ NetBackup7.x Cluster Compatibility Listhttp://entsupport.symantec.com/docs/303344

■ NetBackup Desktop/Laptop Option compatibility listhttp://entsupport.symantec.com/docs/286496

■ Backup Exec Tape Reader compatibility listhttp://entsupport.symantec.com/docs/295433

To locate supported platform information on the Symantec Support Web site

1 Go to the following URL:

www.symantec.com/business/support

2 Select the NetBackup Enterprise Server link under the Support for TopProducts title on the Web page .

3 Select Master Compatibility List link under the Compatibility title on theWeb page .

TheWebpage refreshes and contains a list of compatibility documents. Fromthis Web page, you can refine your search to find a link to the appropriatedocument. (The compatibility list documents are in PDF format. You musthave Adobe Acrobat Reader to view these documents.)

About the deduplication host supported platformsThe following is a list of the supported platforms for NetBackup Deduplication:

■ Solaris SPARC 10 x64Solaris requires an encryption package (SUNWcry64). Youmust download andinstall the package. It is not part of theSolaris installationmedia, andSymanteccannot distribute the package.

■ Red Hat Enterprise Linux:

Supported PlatformsAbout server and client platform support

26

www.symantec.com/enterprise/support

Red Hat Enterprise Linux 4.5 x64 (and higher)■

■ Red Hat Enterprise Linux 5.x x64 (and higher)

On Red Hat Linux, configure the shared memory to be at least 128MB(SHMMAX=128MB). If you do not, deduplication processes may not start, orrun correctly.

■ SUSE Linux Enterprise Server 10 (SLES 10) x64The SUSE Linux system must be at patch level 2.

■ Windows 2003 x64Windows 2003 SP2 x64 systems require Microsoft .NET 3.5 SP1.

■ Windows 2008 x64

■ Windows 2008 R2 x64

Linux systems must have at least the same amount of swap space as physicalmemory space. If swap space is less than physical memory, database problemsmay affect installation and performance.

About platform life cyclesNetBackup software supports an ever-changing set of platforms. And NetBackupmust be flexible enough to handle platform life cycle issues such as adding andremoving a platform from its support list.

See “About adding a platform” on page 27.

See “About Removing a client platform” on page 27.

About adding a platformAdding support of a platform to NetBackup introduces a situation where theplatform has a future, but no history. In this situation, backward compatibilitycannot be guaranteed without exhaustive testing. When a platform is added fora NetBackup release, the platform is supported in that version and subsequentversions (but not previous versions).

About Removing a client platformThe customer commitment for client platformversion support is one version backwith every effort to support all versions. An exception is that the client versioncannot be newer than the master and the media server version.

You can mix the individual clients that are at different version levels within aNetBackup domain. However, it is possible that during an alternate restore, the

27Supported PlatformsAbout server and client platform support

restore is sent to an older version. Alternate restores should go to the same ornewer versions.

See “About NetBackup backward compatibility” on page 35.

About Operating systems not supported as ofNetBackup 7.0 and beyond

Table 2-1 displays the operating systems that are no longer supported at therelease of NetBackup 7.0 and beyond.

Table 2-1 Operating systems not supported as of NetBackup 7.0 and beyond

CommentsHardwareOS/Version

PowerAIX 5.1

PowerAIX 5.2

x86Asianux 3.0

i386 (x86)FreeBSD 5.3



PA-RISCHP-UX 11.00

Media server and client support onlyPA-RISCHP-UX 11.11



IA64HP-UX IA64 11.23

IRIX 6.5.26 and greater

Apple MacintoshMac OS X 10.3

POWERPC, i386Mac OS X 10.4

x86NetWare 5.1

x86NetWare 6.0

Client support onlyx86NetWare 6.5

Novell OES (Linux) 1 SP2

Supported PlatformsAbout Operating systems not supported as of NetBackup 7.0 and beyond

28

Table 2-1 Operating systems not supported as of NetBackup 7.0 and beyond(continued)


x86Red Flag Linux 4.1

x86Red Hat 2.1

x86Red Hat 3.0

x64Red Hat 3.0

IA64Red Hat 3.0

z/ArchitectureRed Hat 3.0

Client support onlyIA64Red Hat 4.0

Client support onlyIA64Red Hat 5.0

SPARCSolaris 8.0

x86Solaris 8.0

x86Solaris 9.0

x64Solaris 9.0

x86Solaris 10.0 x86

x64Solaris 10.0 x86

x86SUSE Desktop 9.0

x86SUSE Desktop 9.2

x86SUSE Desktop 9.3

x86SUSE Linux Enterprise Server 8


IA64SUSE Linux Enterprise Server 8



Client support onlyIA64SUSE Linux Enterprise Server 9

Client support onlyIA64SUSE Linux Enterprise Server 10 SP1

29Supported PlatformsAbout Operating systems not supported as of NetBackup 7.0 and beyond

Table 2-1 Operating systems not supported as of NetBackup 7.0 and beyond(continued)


AlphaTru64 5.1a

AlphaTru64 5.1b and greater

x86 and x64Windows Server 2000

Client support onlyIA64Windows Server 2003 SP1 and R2

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

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

Table 2-2 NetBackp binary sizes for supported platforms

Notes64-bitserver

32-bitserver

64-bitclient

32-bitclient

CPUArchitecture

OS/Version

64-bit binary support3083MB928MBPOWERAIX 5.3

64-bit binary support3083MB928MBPOWERAIX 6.1

16MBx86FreeBSD 6.3/7.x

64-bit binary support. Mediaserver or client support only.

1666MB632MBPA-RISCHP-UX 11.11





3012MB922MBIA64HP-UX 11.31

22MBPOWERMac OS X 10.5

22MBi386 (x86)Mac OS X 10.5

Supported PlatformsNetBackup binary sizes

30

Table 2-2 NetBackp binary sizes for supported platforms (continued)

Notes64-bitserver

32-bitserver

64-bitclient

32-bitclient

CPUArchitecture

OS/Version

16MBHP VAXOpenVMS 5.5



16MBHP AlphaOpenVMS 6.1





16MBHP IA64OpenVMS 8.2

16MBHP IA64OpenVMS 8.3

16MBHP IA64/AlphaOpenVMS 8.3-1H1

510MB

x64Red Flag Linux 5.0 DC

64-bit binary support. PDDErequires an additional 157MB.

1726MB510MB

x64Red Hat Enterprise Linux 4.0(AS)


1726MB510MB

x64Red Hat Enterprise Linux 5.0(base)

Client only support351MB

IA64Red Hat Enterprise Linux 4.0(AS)

Client only support351MB

IA64Red Hat Enterprise Linux 5.0(base)

96MBPOWERRed Hat Enterprise Linux 4.0(AS)

96MBPOWERRed Hat Enterprise Linux 5.0(base)

12MBz/ArchitectureRed Hat Enterprise Linux 4.0(AS)

31Supported PlatformsNetBackup binary sizes


Notes64-bitserver

32-bitserver

64-bitclient

32-bitclient

CPUArchitecture

OS/Version

12MBz/ArchitectureRed Hat Enterprise Linux 5.0(base)


1726MB510MBx64Red Hat Enterprise LinuxDesktop 4.0


510MBx64Red Hat Enterprise LinuxDesktop 5.0

1726MB510MBx64Red Hat Enterprise Linux 5.0(Advanced)


525MBSPARCSolaris 9.0


2050MB639MBSPARCSolaris 10.0


1915MB439MBx64Solaris 10.0

Client only support345MBIA64SUSELinuxEnterpriseServer10 (SP1)

PDDE requires an additional157MB.

1662MB492MBx64SUSELinuxEnterpriseServer10 (SP1)

Client only support101MBPOWERSUSELinuxEnterpriseServer10 (SP1)

Client only support12MBz/ArchitectureSUSELinuxEnterpriseServer10 (SP1)

Client only support345MBIA64SUSELinuxEnterpriseServer11

1662MB492MBx64SUSELinuxEnterpriseServer11

Client only support12MBz/ArchitectureSUSELinuxEnterpriseServer11

Covers all supportedWindowsx86 platforms

1700MB600MBx86Windows

Supported PlatformsNetBackup binary sizes

32


Notes64-bitserver

32-bitserver

64-bitclient

32-bitclient

CPUArchitecture

OS/Version

Covers all supportedWindowsx64 platforms

1900MB700MBx64Windows

Client only support600MBIA64Windows

Platforms supporting the NetBackup AdministrationConsoles for UNIX

TheNetBackupAdministrationConsoleprovides agraphical user interface throughwhich the administrator can manage NetBackup. The interface can run on anyNetBackup Java-capable system. For information on how to install the consoles,see the NetBackup Installation Guides. And for information on how to use theNetBackup Adminstration Console, see the NetBackup Administrator's Guide,Volume 1.

Note: Symantec supports thewindowmanagers in the following tablewhen usingNetBackup Java. Youmayencounter someuser-interface anomalieswhenyouusethe variouswindowmanagers that are available onUNIXplatforms.Many of theseproblems are documented and can occur because of unusual or non-standardwindowmanager configurations. In themost commoncases ofmisplacedor shiftedcomponents within a dialog, resize the dialog. This action refreshes the displayand causes the interface to display the information correctly.

Table 2-3 is a list of platforms that support the NetBackup-Java AdministrationConsole and the Backup, Archive, and Retore user interface in this release.

Table 2-3 Platforms that support NetBackup-Java Administration Consoleand Backup, Archive, and Retore user interface

JRE upgradeversion

Backup,Archive, andRestoreinterface

NetBackup-Javaadministrationconsole

CPU ArchitectureOS/Version

Java 6 SR6YesYesPOWERAIX 5.3

Java 6 SR6YesYesPOWERAIX 6.1

6.0.05YesYesPA-RISCHP-UX 11.11

33Supported PlatformsPlatforms supporting the NetBackup Administration Consoles for UNIX

Table 2-3 Platforms that support NetBackup-Java Administration Consoleand Backup, Archive, and Retore user interface (continued)

JRE upgradeversion






6.0.05YesYesIA64HP-UX 11.31

1.6-16YesYesx64Red Hat Enterprise Linux 4.0 (AS)

1.6-16YesYesx64Red Hat Enterprise Linux 5.0 (base)

1.6-16YesIA64Red Hat Enterprise Linux 4.0 (AS)

1.6-16YesIA64Red Hat Enterprise Linux 5.0 (base)

YesPOWERRed Hat Enterprise Linux 4.0 (AS)

YesPOWERRed Hat Enterprise Linux 5.0 (base)

Yesz/ArchitectureRed Hat Enterprise Linux 4.0 (AS)

Yesz/ArchitectureRed Hat Enterprise Linux 5.0 (base)

1.6-16YesYesx64Red Hat Enterprise Linux Desktop 4.0

1.6-16Yesx64Red Hat Enterprise Linux Desktop 5.0

1.6-16YesSPARCSolaris 9.0

1.6-16YesYesSPARCSolaris 10.0

1.6-16YesYesx64Solaris 10.0

1.6-16YesIA64SUSE Linux Enterprise Server 9

1.6-16YesYesx64SUSE Linux Enterprise Server 10 (SP1)

YesPOWERSUSE Linux Enterprise Server 10 (SP1)

Yesz/ArchitectureSUSE Linux Enterprise Server 10 (SP1)

1.6-16YesIA64SUSE Linux Enterprise Server 11

1.6-16YesYesx64SUSE Linux Enterprise Server 11

Yesz/ArchitectureSUSE Linux Enterprise Server 11

Supported PlatformsPlatforms supporting the NetBackup Administration Consoles for UNIX

34

Table 2-3 Platforms that support NetBackup-Java Administration Consoleand Backup, Archive, and Retore user interface (continued)

JRE upgradeversion




1.6-16YesYesx86WindowsServer 2003Enterprise Edition(SP1)

1.6-16YesYesx86WindowsServer 2003Enterprise Edition(R2)

1.6-16YesYesx64WindowsServer 2003Enterprise Edition


1.6-16YesIA64WindowsServer 2003Enterprise Edition

1.6-16YesIA64WindowsServer 2003Enterprise Edition(R2)

1.6-16Yesx86WindowsServer 2008Enterprise Edition

1.6-16YesYesx64WindowsServer 2008Enterprise Edition


1.6-16Yesx86 or x64Windows XP Professional SP2

1.6-16YesIA64Windows XP Professional SP2

1.6-16Yesx86 or x64Windows Vista

1.6-16YesYesx86 or x64Windows 7 Ultimate

About NetBackup backward compatibilityNetBackup supports a mixture of NetBackup servers that are at various releaselevels in the same environment. However, Symantec only supports certaincombinations of servers and clients within a NetBackup environment that mustprovide backward compatibility.

Table 2-4 shows the different server version levels that NetBackup supports inthis release.

35Supported PlatformsAbout NetBackup backward compatibility

Table 2-4 Mixed-server support for NetBackup 7.0

Client versionMedia server versionMaster server version

7.070NetBackup 7.0

6.5 (and later), 6.0 (and later)7.0NetBackup 7.0

6.5 (and later), 6.0 (and later)6.5 (and later), 6.0 (and later)NetBackup 7.0

NetBackup 7.0 does not support Windows 2000 systems. However, you can stilluse NetBackup version 6.x on Windows 2000 clients with your NetBackup 7.0servers.

The following describes what type of action to take if you have any clients thatrun Windows 2000:

Noaction is required. These clients are compatiblewith NetBackup version 7.0 master and mediaservers.

Existing NetBackup customers withWindows 2000 clients at NetBackupversion 6.x:

You must install NetBackup version 6.x clientsoftware on your Windows 2000 systems.

See the following Technote on the SymantecSupport Web site for more information.


New NetBackup customers withWindows 2000 systems:

For more information about upgrading NetBackup, refer to the NetBackupInstallation Guide for either UNIX or Windows.

The following is a list of best-practice rules that you should consider for amixed-server environment:

■ Before you upgrade the NetBackup server software, you must back up yourNetBackup catalogs and verify that the catalog backup was successful.

■ During an upgrade to NetBackup 7.0, it is necessary to have enough free diskspace to accommodate three complete copies of theNetBackup database. Thatincludes all transaction logs and database files in the data directory includingBMR if it is configured and in use. This directory is typically/usr/openv/db/data for UNIX-based operating systems and\Veritas\NetBackupDB\data for Windows-based operating systems whenyou use default installation methods.

■ In amixed-server environment, themaster servermust run thehighest versionof NetBackup in use in that configuration.

Supported PlatformsAbout NetBackup backward compatibility

36

■ A master server can inter-operate with a media server that is running a levelof NetBackup that is one major release lower.

■ A media server cannot have a numerically higher version than the masterserver. (Each media server must run equal or lower levels of NetBackup.)

■ All components (server, client, and console) on an individual system must beat the same version.

■ The backup images that are created under an older version of NetBackup arerecoverable with a newer version of NetBackup.

■ Servers canpull andpush their version information betweenmaster andmediaservers. Your server’s NetBackup version determines whether the versioninformation can be pushed. After startup, an upgraded media server uses thevmd service to push its version information to all servers in its master serverlist. An automatic update occurs every 24 hours when servers push theirversion information again.

■ To install NetBackup on Windows 2008/Vista/2008 R2/7 UAC-enabledenvironments, you must log on as the official administrator. Users that areassigned to the Administrators Group and are not the official administratorcannot install NetBackup in UAC-enabled environments.To allowusers in theAdministratorsGroup to install NetBackup, disableUAC.

37Supported PlatformsAbout NetBackup backward compatibility

Supported PlatformsAbout NetBackup backward compatibility

38

Product Dependencies


■ Operating system patches and updates

■ About supported versions of VxFS and VxVM

Operating system patches and updatesThis topic provides information on the product dependencies of NetBackup 7.0.You should verify that your operating system is up-to-date with all of the latestpatches and upgrades before you install NetBackup. This section is a guide toinform you of the operating systems that require a patch or an upgrade.

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

Table 3-1 Operating system patches and updates for NetBackup

NotesPatchOperating systemtypeand version

You may need to reboot afterchanging to version 9.0.0.3.

AIX runtime libraries8.0.0.10 and 9.0.0.3 orlater

AIX 5.3

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

xlC.rte 8.0.0.10

fileset

3Chapter

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


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

You can use the oslevel -s

command toverifywhatMaintenancePack level you have installed.

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

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

IZ16878AIX 6.1

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

AIX runtime libraries9.0.0.3 or later

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

COMPLIBS.LIBM-PS32HP-UX

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

HP-UX IA64

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

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

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

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

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

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

Product DependenciesOperating system patches and updates

40



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

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

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

HP-UX PA-RISC


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


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


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

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

This patch is a LIBCL patch.PHSS_32226

Contains fixes for the following:

■ QXCR1000593919: purifyplus

dumps core in PA32

■ QXCR1000589142: dld crash inLL_new_descendent_listwhen theaCC application is exiting.


■ QXCR1000746161: dlsym()

hangs

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

PHSS_37516

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

PHSS_26946

This patch is a libc cumulativepatch.

PHSS_27740

This patch contains a linker toolscumulative patch.

PHSS_26560

41Product DependenciesOperating system patches and updates



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

PHSS_32864

This patch enables HP-UX 11.11

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

PHKL_26233

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

PHSS_35379

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

PHCO_29029

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

PHSS_24045

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

www1.itrc.hp.com

PHSS_30970


Symantec recommends that allcustomers running 11.23 install thispatch.

PHCO_33431

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

PHSS_34858


42



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

PHKL_31500

Contains fixes for the following:

■ QXCR1000593919: purifyplus

dumps core in PA32


■ QXCR1000746161: dlsym()

hangs

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

PHSS_37492


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

SLES 10 update 2SLES10 x64

111711-11 (or greater)Solaris 9 SPARC 64-bitclient

111712-11 (or greater)

111722-04 (or greater)

Patch: 112908-29 (orgreater)

Patch: 112874-31 (orgreater)

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

update 4 (08/07) andnewer

Solaris 10 SPARC 64-bit(server and client)

43Product DependenciesOperating system patches and updates



Microsoft hotfix KB913648 containsthe necessary updates to run VolumeShadow Copy.

KB913648Windows 2003 SP1

Microsoft storporthotfixWindows x64 (SP1 andSP2)

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

Microsoft microcodereliability update

Windows 2003, XP, andVista

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

KB952696Windows 2008 x32 andx64

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

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

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


44

About supported versions of VxFS and VxVMTable 3-2 shows the different versions of VxFS and VxVM that SymantecNetBackup supports, and the corresponding operating systems for each.

Table 3-2 Versions of VxFS and VxVM Currently Supported by SymantecNetBackup

NotesVersion of VxVMVersion of VxFSOS VersionOperating system

4.0 and higher5.0 and higher5.3 (64 bit)AIX 5L

5.0 MP3 and higher5.0 MP3 and higher6.1 (64 bit)

3.5 only3.3 and 3.511.11HP-UX PA-RISC

3.5, 4.1, and 5.03.5, 4.1, and 5.011.23

4.1 and higher4.1 and higher11.31

3.5, 4.1, and 5.03.5, 4.1, and 5.011.23HP-UX IA64

4.1 and higher4.1 and higher11.31

4.1 to 5.0MP3RP34.1 and higherx86-64Red Hat Enterprise Linux 4.0(AS)

4.1 to 4.1MP4RP44.1 to 4.1 MPx(support is droppedin 5.0)

IA64

5.0 LoP phase1, phase25.0 MP1 and higherPOWER

LxRT4.1MP4RP1andhigheron the 4.1 line, 5.0MP3 andhigher on the 5.0 line

4.1 MP3 and higherx86-64Red Hat Enterprise Linux 5.0(AS)

4.1MP4RP1 and higher inthe 4.1 codeline only

NAIA64

5.0RU3 and higher5.0RU3 and higherPOWER

4.1 MP2 and higher4.1 MP2 and higher9Solaris (SPARC)

4.1 MP2 and higher4.1 MP2 and higher10

4.1MP3 and higher in 4.1codeline. 5.0MP3 andhigher on 5.0 codeline.

4.1 and higherx86-64SUSE Linux Enterprise Server10

45Product DependenciesAbout supported versions of VxFS and VxVM

Table 3-2 Versions of VxFS and VxVM Currently Supported by SymantecNetBackup (continued)

NotesVersion of VxVMVersion of VxFSOS VersionOperating system

4.1MP3 and higher in 4.1codeline only.

4.1 MP3 (supportdropped in 5.0)

IA64


5.0RU1 and higher4.1 MP3 and higherx86-64SUSE Linux Enterprise Server11

NANAIA64


4.3 and higherNAx86-64Windows 2003

5.0 and higherNAx86-64Windows 2008

5.1 SP1 and higherNAx86-64Windows 2008 R2

For the most current information and patch requirements for VxFS and VxVM,refer to the NetBackup 7.0 Additional Operational Notes contained in Technotenumber 337179 on the Symantec Support Web site.


NetBackup has improved its integration with the Veritas File System (VxFS)product to ensure interoperability on all supported VxFS versions. If running aVxFS version before VxFS 4.0 then new VxFS libraries need to be installed on theclient to back up systems running VxFS. You can search and download theappropriate VxFS libraries to your system from Patch Central on the SymantecSupport Web site.

See, https://vias.symantec.com/labs/patch.

See http://entsupport.symantec.com/docs/320193.

Table 3-3 Shows the integration improvements that were made between thevarious operating systems and the Veritas File System (VxFS).

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

VxFS 3.5VxFS 4.1VxFS 5.0OS VersionOperating system

NANAX5.3AIX

XNANA11.11HP-UX PA-RISC

Product DependenciesAbout supported versions of VxFS and VxVM

46

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

VxFS 3.5VxFS 4.1VxFS 5.0OS VersionOperating system

NANAX11.23

NANAX11.31

NANAX11.31HP-UX IA64

NANAXx86-64Red Hat Enterprise Linux 4.0(AS)

NANAXx86-64Red Hat Enterprise Linux 5.0(AS)

NANAXx86-64SUSE Linux Enterprise ServerSLES 10

IA64

NANAXx86-64SUSE Linux Enterprise ServerSLES 11

IA64

NANAX9Solaris (SPARC)

NAXX10

47Product DependenciesAbout supported versions of VxFS and VxVM

Product DependenciesAbout supported versions of VxFS and VxVM

48

Operational Notes


■ Operational Notes in NetBackup

■ NetBackup installation and start-up notes

■ NetBackup Documentation Notes

■ Internationalization and localization Notes

■ NetBackup Bare Metal Restore

■ General NetBackup operational notes

■ NetBackup Access Control

■ NetBackup database agents

■ NetBackup Hyper-V

■ NetBackup interfaces

■ About Symantec OpsCenter

■ NetBackup media and device management

■ SAN Client and Fibre Transport

■ SharedDisk support in NetBackup 7.0 and later

■ NetBackup AdvancedDisk option

■ NetBackup Client Deduplication

■ About the NetBackup Media Server Deduplication Option

■ PureDisk Deduplication Option (PDDO)

4Chapter

■ NetBackup Snapshot Client

■ NetBackup commands and utilities

■ NetBackup OpenStorage Option

■ NetBackup Disk Storage units

■ NetBackup Vault

■ NetBackup for VMware

Operational Notes in NetBackupThe chapter contains the topics that explain important aspects of NetBackup 7.0operations thatmaynotbedocumentedelsewhere in theNetBackupdocumentationset.

For additional operational note information about this release, see the followingonline PDF titled, NetBackup 7.0 Additional Operational Notes contained inTechnote number 337179 on the Symantec Support Web site.


Note: References to UNIX also apply to Linux, unless otherwise stated.

NetBackup installation and start-up notesThe following subsections offer additional the information that can help youinstall NetBackup or use NetBackup.

NetBackup media and rebranding changesThe following list of itemsdescribe theNetBackupDVDandNetBackup rebrandingenhancements:

■ Veritas Storage Migrator (VSM)This product has reached its end of life and is no longer supported.

■ NetBackup Operations Manager (NOM)Starting with NetBackup 7.0, NOM has been replaced with OpsCenter. If yourcurrent 6.x NetBackup environment includes NOM6.x, you can upgrade NOMto OpsCenter with an upgrade to NetBackup 7.0.

■ Platform and operating system support changes in NetBackup 7.0See “About NetBackup Compatibility Lists” on page 24.

Operational NotesOperational Notes in NetBackup

50


■ UNIX package consolidationIn NetBackup 7.0, most of the add-on products and database agents are nowinstalledwith theNetBackup server or the client package. Separate installationfor these products is no longer needed.

The following products are now included in the NetBackup server package (ifthe platform supports the product):

■ BMR master server

■ NDMP

■ NetBackup Vault

The following products are now included in the NetBackup client package (ifthe platform supports the product):

■ BMR Boot server

■ DB2

■ NetBackup Encryption

■ Informix

■ LiveUpdate agent

■ Lotus Notes

■ Oracle

■ SAP

■ Snapshot Client

■ Sybase

The binaries for the listed products are laid down with the server or the clientpackage. A valid license is still required to enable the product. If productconfiguration was required previously (such as db2_config), configuration isstill required.For Solaris server upgrades, the older versions of any listed products heremust be removed before an upgrade to NetBackup 7.0. For example,VRTSnbdb2,SYMCnbdb2,VRTSnbenc,SYMCnbenc, andothers.The installationscript displays a list of the packages it finds that must be removed.The Japanese and the Chinese language packages remain as separate add-ons.The process to install and upgrade these products remains the same.

■ Clustered media server support changesNew NetBackup 7.0 media server installations cannot be clustered. However,existing 6.x clusteredmedia servers can be upgraded to version 7.0 and remainclustered.

51Operational NotesNetBackup installation and start-up notes

■ All compressed files are compressed using gzip. The installation of these filesrequires that gunzip, and gzip, be installed on the machine before NetBackupis installed. For all UNIX platforms except HP-UX, the binaries are expectedto be in /bin or /usr/bin and that directory is a part of the root user’s PATHvariable. On HP-UX systems, the gzip and gunzip commands are expected tobe in /usr/contrib/bin. Installation scripts add that directory to the PATHvariable. These commands must be present to have successful UNIXinstallations.

■ The following instructions clarify how to install NetBackup client software inSolaris 10 non-global zones.NetBackup server is supported only in a global zone. Technote 275107 on theSymantec Support Web site contains more information.On a server whose non-global zone does not use a read-only loopback devicefor the /usr directory, the client push-install or local install is done normally.Please see the appropriate installation guide.If the server does not have a master or a media server on the global zone, andhas a sparse non-global zone using a read-only loopback device for the /usrdirectory, use the following procedure.

To provide clarification for installing NetBackup client software in Solaris 10non-global zones

1 In the global zone, create /usr/openv as a symbolic link to the location inwhich you install the software to in the non-global. That needs to be doneeven if the global zone does not have that directory.

For example:

# ln -s /nonglobdir/openv /usr/openv

# ls /nonglobdir/openv

/nonglobdir/openv: No such file or directory

# ls -al /usr/openv

rwxrwxrwx 1 root root 10 Aug 23 15:13

/usr/openv -> /nonglobdir/openv

2 In the non-global zone, make sure that /usr/openv exists as a link.

For example:

# ls -al /usr/openv

rwxrwxrwx 1 root root 10 Aug 23 15:13

/usr/openv -> /nonglobdir/openv

Operational NotesNetBackup installation and start-up notes

52

3 In thenon-global zone,make sure that the directory link exists and iswritable.

For example:

# ls -al /nonglobdir/openv

total 32

drwxr-xr-x 9 root bin 512 Aug 18 15:23 ./

drwxr-xr-x 18 root bin 512 Aug 18 15:30 ../

4 Client push-install or local install can now be done normally according toguides.

If the server does have a master or a media server on the global zone, andhas a sparse non-global zone using a read-only loopback device for the /usrdirectory, use the following procedure:

To provide clarification for installing NetBackup client software in Solaris 10 globalzones

1 In the global zone, the /usr/openv in a default installation is a link to/opt/openv. Alternatively, the master or the media server can be installedin a base directory (BASEDIR) other than the default /opt. And you can link/usr/openv to/BASEDIR/openv. Verify thedirectory that/usr/openv is linkedto.

For example:

# ls -al /usr/openv

rwxrwxrwx 1 root other 10 Aug 18 11:39

/usr/openv -> /opt/openv/

2 In the non-global zone, create a writable directory where the /usr/openvpoints to.

For example:

# mkdir /opt/openv

3 Client push-install or local install can now be done normally according toguides.

General installation and upgrade itemsThe following list contains general installation and upgrade information:

■ Check for available disk space prior to upgrading to NetBackup 7.0


During an upgrade to NetBackup 7.0, it is necessary to have enough free diskspace to accommodate three complete copies of theNetBackup database. Thatincludes all transaction logs and database files in the data directory includingBMR if it is configured and in use. This directory is typically/usr/openv/db/data for UNIX-based operating systems and\Veritas\NetBackupDB\data for Windows-based operating systems whenyou use default installation methods.

■ Beginning with NetBackup 7.0, nbmail.cmd is installed to thenetbackup\bin\goodies folder. It had previously been installed to thenetbackup\bin folder. Like the other scripts in the netbackup\bin\goodiesfolder, you now have to copy nbmail.cmd to the netbackup\bin folder. (Youwould then modify nbmail.cmd at that location for it to take effect.

■ Log files for VxUL OIDs from previous releasesLog files for VxUL OIDs that were used in a previous release may be left in theroot logs directory (/usr/openv/netbackup/logs on UNIX and C:\Program

Files\Veritas\Netbackup\logsonWindows) after anupgrade toNetBackup7.0. This occurs because the OIDs do not have an OID entry in the nblog.conffile that specifies the subdirectory for their log files (<oid>.LogDirectory=name).This may occur for the following OIDs: 102, 113, 120, 142, 153, and 157. Youcan display these log files with vxlogview in NetBackup 7.0 if you specify thefollowing.-G <root log dir> -o oid

Where <root log dir> is either /usr/openv/netbackup/logs on UNIX orC:\Program Files\Veritas\Netbackup\logs onWindows. And oid is the 102, 113, 120, and so on.You can remove these OIDs after the upgrade. However, you must manuallydelete the OIDs because the vxlogmgr cannot access them. If you think youmayneed to report a problem in a previous release, then youmaywant to keepthem for that purpose.

■ To install NetBackup on Windows 2008/Vista/2008 R2/7 UAC-enabledenvironments, you must log on as the official administrator. Users that areassigned to the Administrators Group and are not the official administratorcannot install NetBackup in UAC-enabled environments.To allowusers in theAdministratorsGroup to install NetBackup, disableUAC.

■ If you install NetBackup server on top of an existing NetBackup client toupgrade the client to a server, PDDE is non-functional. That issue applies toSLES, Red Hat, and Solaris platforms. You must completely remove theNetBackup client and then install the NetBackup server software. Follow theinstructions in the NetBackup Installation Guide for UNIX and Linux.


54

■ The NetBackup Tape Device Driver Installation wizard is no longer presenton the installation media. In most cases, the manufacturer’s device drivers orthe drivers that are included with the operating system are appropriate. Inenvironments where the NetBackup tape device drivers are required, you candownload them from theNetBackupSupportWeb site at the following location.http://support.veritas.com/docs/287850

■ In a future release, itmay be required that clients connect to themaster serverto complete an installation.

■ Symantec recommends the following Microsoft updates when you runNetBackup on Windows operating systems:

■ Microsoft storport hotfix. This fix applies to Windows x86 and x64, onbothSP1andSP2: (required)http://support.microsoft.com/?id=932755

■ Microsoftmicrocode reliability update. This fix applies to 32-bit and 64-bitversions of Windows Server 2003/XP/Vista: (suggested)http://support.microsoft.com/?kbid=936357

■ Symantec AntiVirus. Update to latest version (10.2 for Corporate Edition)and latest update (required).

■ The Symevent driver updates (required). Update to latest driver version.

■ Symantec recommends the following third-party updates when you runNetBackup on Windows operating systems :

■ QLA2340 Q*Logic HBA driver 9.1.4.15 (required)http://support.qlogic.com/support/oem_product_detail.asp?p_id=253&oemid=65&oemname=QLA2340

■ QLA2340 Q*Logic HBA BIOS 1.47 (required)http://support.qlogic.com/support/oem_product_detail.asp?p_id=253&oemid=65&oemname=QLA2340

■ All other Q*Logic HBAs use latest driver & BIOS(suggested)http://support.qlogic.com/support/oem_product_list.asp?oemid=65

■ The default shared-memory requirements on UNIX systems are greater forNetBackup 7.0 than previous releases.See the NetBackup Installation Guide for UNIX and Linux.See the NetBackup Troubleshooting Guide for UNIX, Windows and Linux.

■ UNIX 32-bit system support has been discontinued for all platforms exceptFreeBSDandMacintosh (universal - i386/ppc). If you currently useNetBackup6.x on any 32-bit systems other than FreeBSD and Macintosh, you cannotupgrade those systems to 7.0. However, you can migrate the NetBackup 6.x


http://support.qlogic.com/support/oem_product_detail.asp?p_id=253&oemid=65&oemname=QLA2340




http://support.qlogic.com/support/oem_product_list.asp?oemid=65

http://support.qlogic.com/support/oem_product_list.asp?oemid=65

catalogs anddatabases on those systems to a supported 64-bit platformsystemand then upgrade to 7.0.See the NetBackup Installation Guides for more information about migratingNetBackup master servers from 32-bit to 64-bit.Any 32-bit media servers and clients that use NetBackup 6.x are compatiblewith the 64-bit master servers that use NetBackup 7.0.

■ Symantec recommends that you have the master server services up andavailable during a media server upgrade.

■ Symantec recommends that all customers running HP-UX 11.23 install thepatch (PHCO_33431). If you do not install the patch before you installNetBackup on a systemwith an updated version of 11.23, the installationmayfail.

■ The operating system may open a user interface window (for example, FileManager on a Solaris system,) when the DVD is inserted into the drive.Symantec recommends that you do not use this window to install NetBackupproducts because unpredictable results may occur. Follow the installationinstructions that are provided in the NetBackup 7.0 documentation set.

NetBackup LiveUpdateNetBackup LiveUpdate is not compatible with Open VMS (UNIX) or Novelloperating systems.

Secure push installThe installation methods (ssh and sftp) of pushing UNIX client software from aUNIX master server to a UNIX client host consist of running theinstall_client_files script on the command line. Both of these methods arebased on the usage of the SunSSH and OpenSSH products and these products mustbe at specific version and patch levels.

For more information about these patches, refer to Table 3-1 in Chapter 3,NetBackup product dependencies.

NetBackup clusterThe following list shows the items that relate to NetBackup cluster:

■ New NetBackup 7.0 media server installations cannot be clustered. However,you can upgrade existing NetBackup 6.x clustered media servers to version7.0 and they remain clustered.


56

■ When a fault occurs in a cluster resource group for NetBackup in a SunClusterconfiguration, failover of the NetBackup resource group does not occur. Thefailure in this situation could happen if the NIC (network) or other resourcescould not come online.

■ When you upgrade clustered NetBackup servers to NetBackup 7.0, you mayencounter Windows event log messages that indicate the Sybase service(SQLANYs) failed to start. These messages are generated in a short period oftime – normally a window of two to three seconds. These messages coincidewith the cluster configurationportion of the upgrade. You should expect thesemessages and know that they do not reflect a problem with the upgrade.

■ For VCS Windows (SFW-HA 4.1, SFW-HA 4.2), Symantec recommends thatusers make sure patch 278307 is installed before you install or upgrade toNetBackup 7.0.See http://entsupport.symantec.com/docs/278307 for more information.

■ When you launch the NetBackup Administration Console, you should log intothe server using the virtual name that is associated with NetBackup.

■ With theneed for increased security, youmust be able to configureNetBackupwith access control (NBAC) in a clustered NetBackup server environment.See http://entsupport.symantec.com/docs/288471.

■ When you configure disk storage units, only basic disk supports the use ofapplication clusters. When you configure disk pools or storage servers,application clusters are not supported.

■ After you install or upgradeNetBackuponUNIXclusters other thanSunCluster,you should increase the NetBackup resource offline timeout to at least 600seconds.

■ When you install or upgrade NetBackup on Sun Clusters, make the followingchanges to the NetBackup resource group tuning parameters to ensure asuccessful failover:

■ Increase the STOP_TIMEOUT parameter from the default of 300 secondsto at least 600 seconds.

■ Set the pmf Retry_count parameter to 0.

These changes can be accomplished using the following commands. Note thatrunning these commands causes shutdown and restart of NetBackup.

# scrgadm -c -j scnb-hars -y Retry_count=0

# scrgadm -c -j scnb-hars -y STOP_TIMEOUT=600

# scswitch -n -j scnb-hars

# scswitch -e -j scnb-hars


■ If you install NetBackup7.0 on theHPServiceGuard v11.18 (or 11.17) onmorethan one node, the NetBackup cluster resource group may becomeunmanageable when the NetBackup package (Virtual IP) fails to come onlineor offline. Offline and failover of the cluster package does not occur.

If you encounter this issue, do the following after you install NetBackup, andall cluster nodes:

■ Open the NetBackup package configuration file(/etc/cmcluster/netbackup/netbackup.config).

■ Change the name of the configuration entry for subnet mask fromMONITORED_SUBNET to SUBNET on all of the nodes in the cluster.You do not need to update the cluster because the configuration has notchanged.

■ Open the package control script /etc/cmcluster/netbackup/netbackup.

■ Uncomment the following parameters on all of the nodes in the cluster:- SERVICE_NAME[0]="netbackup"

- SERVICE_CMD[0]="/etc/cmcluster/netbackup/monitor"

- SERVICE_RESTART[0]="-r 2"

Remove the hash symbol ('#') from the beginning of each of these threelines to uncomment the parameter.

NetBackup Documentation NotesThe following information should be considered as part of the NetBackup 7.0documentation set:

■ NetBackup Enterprise Vault MigratorTheNetBackup Enterprise Vaultmigrator is documented inAppendixA of theNetBackup Enterprise Vault Agent Administration Guide. Please refer to thisdocument for information regarding theNetBackupEnterpriseVaultmigrator.

■ The following new documents are packaged with NetBackup 7.0:

■ NetBackup LiveUpdate Guide

■ NetBackup Installation Checklist

■ Symantec NetBackup Deduplication Guide

Internationalization and localization NotesThe following list identifies the issues that relate to Internationalization andlocalization:

Operational NotesNetBackup Documentation Notes

58

■ The NetBackup command-line menu user interfaces (MUIs) cannot input andmodify multi-byte characters and they are not localized to any language. Thefollowing list identifies the various menu user interfaces:

■ bp

■ bpadm

■ tpconfig menu

■ vmadm

■ vltadm

■ TheNetBackup-Java Administration console core dumps if you use SimplifiedChineseUTF-8 locale on a Solaris SPARC64-bit systemwith Solaris 10Update2 and above installed.This problem is caused by the Sun Microsystems™ issue, 6901233.See, http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6901233 formore information about this issue.If you encounter this issue, apply the Solaris patch that Sun provides to fixthis issue 6901233.

■ When you run on a non-English locale, a problem can occur if you use spacesin the pathname. Spaces in the pathname can cause a backup to fail.

■ The installation of NetBackup client to traditional Chinese paths that containspaces such as C:\Program Files may cause backup failures. You shouldinstall NetBackup client software to a path that does not contain spaces.

■ Installation to paths that contain non-ASCII characters may cause backup orrestore failures.

■ If you plan to install an English version of NetBackup 7.0 on top of an existinglocalized version NetBackup, without installing the localized contents in theLanguage package CD first, you must remove the localized contents that areinstalled on your system.

■ For Windows and UNIX installations, the install path must not containmulti-byte characters.

■ The NetBackup – Java Administration Console does not support user-definedcharacters (UDC) and vendor-defined characters (VDC) because of theimplementation of Java’s encoding converters.

■ NetBackup can be installed to environments running different versions ofUNIX based operating systems as long as the system locales are identical. Useof different locales acrossUNIXplatforms can cause user interface corruptionor a possible data loss.

59Operational NotesInternationalization and localization Notes

■ If you mix non-English versions of Windows and UNIX platforms, differencesin operating system architecture and encodings may cause non-English filenames and folder names to be displayed incorrectly within the user interface.That may cause functional failures.

■ On non-English versions of Windows and UNIX systems, the NetBackup-JavaAdministrationConsolemaydisplaynon-English characters incorrectly leadingto functional failures.

■ At the time of this release, the following database agents have restrictedsupport of localized environments:

■ NetBackup for DB2

■ NetBackup for Informix

■ NetBackup for Oracle

■ NetBackup for SAP

■ NetBackup for SharePoint

■ NetBackup for SQL Server with Snapshot Client

■ NetBackup for Sybase ASE

Whenyouuse any of these agents, the use of localized characters (for example,non-ASCII, multi-byte characters) is not supported in:

■ Any database object names, like instances, databases, tablespaces,filegroups, data files, portals, and so forth

■ The path names of database files, directories, transaction logs, or otherdatabase storage locations

■ The path names that are specified in the policy Backup Selections, likescript, template, or batch file locationsThat applies to all supported platforms, including the use of previousversions of those NetBackup database agents with NetBackup 6.0 servers.

■ The following NetBackup user-defined strings must not contain Multi-bytecharacters:

■ Hostname (master server, media server, EMM server, Volume DatabaseHost, Media Host, Client)

■ Policy Name

■ Policy KEYWORD (Windows Only)

■ Backup, Archive, and Restore KEYWORD (Windows Only)

■ Storage Unit Name

Operational NotesInternationalization and localization Notes

60

■ Storage Unit Disk pathname (Windows Only)

■ Robot Name

■ Device name

■ Schedule Name

■ Media ID

■ Volume group Name

■ Volume Pool Name

■ Media Description

■ Vault Policy Names

■ Vault Report Names

■ BMR SRT Name

■ BMR Configuration Name

NetBackup Bare Metal RestoreThe following list contains the items that relate to the NetBackup Bare MetalRestore feature:

■ An issue can occur when you use bmrsetupmaster on the command lineinterface (CLI) to configure a BMRmaster server on anAIX 5.3 platform.Morespecifically, this issue occurs on a 7.0 or greater BMRmaster server on an AIX5.3 or greater platform. This issue occurs because the stack size, data segmentsize, andmaxmemory size ulimitparameters on the systemare set too small.When that happens, data parsing fails while the BMR database is populated.If you encounter this issue, use the following procedure to change the ulimitparameters to “unlimited” and run bmrsetupmaster again.

To change the ulimit parameters:

■ Run the ulimit -a command on the BMR master server. This commandprints the system resources limit.

■ Check the current limit set that is used for the stack size, data seg size,and max memory size parameters.

■ Set the parameters to unlimited. Run the following commands to changethe limits:

■ ulimit -s unlimited

■ ulimit -d unlimited

61Operational NotesNetBackup Bare Metal Restore

■ ulimit -m unlimited

■ Run bmrsetupmaster to configure the BMR master server.

You can permanently change the resource limits by manipulating the“/etc/security/limits” file on the system.

■ Youcanupgrade toNetBackup7.0only fromNetBackup6.x. Youcannotdirectlyupgrade an older standalone BMR product (BMR 4.7) to NetBackup 7.0, but itcan be migrated to NetBackup 7.0.To migrate from BMR 4.7, refer to the, Upgrading and migrating from olderBMR versions, section in the NetBackup Bare Metal Restore Administrator’sGuide.

■ About creating a shared resource tree (SRT) for WindowsStarting with NetBackup 7.0 the boot server does not support the creation of6.5.X and 6.X SRT. However a NetBackup 7.0 SRT does support restores ofpre-7.0 NetBackup ( for example, 6.5.X or 6.X ) clients. The SRT that containsNetBackup 7.0 or a higher version NetBackup Client can be used to restoreback-level NetBackup clients.

■ About copying a pre-NetBackup 7.0 SRTStarting with NetBackup 7.0 the boot server does not support copying of 6.5.Xand 6.X SRT.

■ About importing a pre-NetBackup 7.0 SRTStarting with NetBackup 7.0 the boot server does not support importing of6.5.X and 6.X SRT.

■ The Windows Fast Restore feature requires a DNS server to be able to resolvethe client and Servers.

■ When EMC PowerPath software is running on the original client, BMR canonly support the restoration of a client back onto the original hardware.

■ BMR does not support restoring the Remote Installation Folder location of anRIS Server. You can restore an RIS Server using the SystemOnly feature. Youcanalso restore theRIS server by editing the client configuration, and removingthe volume that is used for the Remote Installation Folder location from themap.

■ SRT creation fails with RHEL5.3If RHEL5.3 media (CDs) is used for SRT creation, SRT creation fails and thefollowing error message appears:V-125-380 /var/temp/bmrmediaDb1K6p/.discinfo(2): expected "Red Hat

Enterprise Linux Server 5", got "Red Hat Enterprise Linux Server

5.3". The loaded media is not corrrect...please try again.

Unmounting media...ok.

Operational NotesNetBackup Bare Metal Restore

62

To avoid this problem, use one of the following methods to create an SRT:

■ Method 1:Use RHEL5.0, 5.1, or 5.2 OS media. When you create an SRT this way, itcan be used to restore a RHEL5.3 client.

■ Method 2:On the BMR boot server, open the following file:/usr/openv/var/global/createsrt.conf

Search for the string Red Hat Enterprise Linux Server 5 and replace alloccurrences with Red Hat Enterprise Linux Server 5.3.This change should enable creation of a RHEL5.3 SRT, however it alsodisables creation of a RHEL5.0, 5.1, and a 5.2 SRT. (RHEL5.3 introduces thenew device drivers that are not a part of the default kernel in RHEL5.2.)

Symantec recommends that you use Method 2.

■ No support for legacy DOS-based restores on Windows x64 clients.Windows x64 client systems cannot be restored using the legacy DOS-basedRestore.This restriction exists because a DOS-based Restore requires a 16-bit OSinstaller application (winntsetup.exe) that can be invoked from within DOSenvironment. For 64-bit versions ofWindowsOS,Microsoft didnot ship 16-bitinstallers. Hence, the temporary OS installation of 64-bit OS for BMR cannotbe initiated from aDOS environment. As a result,Windows x64 client systemscannot be restored using the legacy DOS-based Restore.In addition, the BMR Fast Restore is the only mechanism of BMR Restore forWindows x64 client systems.

■ No support for Veritas Storage Foundation (VxFS) for Windows (SFW) onWindows x64 clients.Windows x64 client systems that run VxFS for Windows (SFW) cannot berestored.This issue is valid because Windows clients that run SFW cannot be restoredusing Fast Restore mechanism of BMR. This means, Windows clients that runSFW can be BMR restored using only a legacy DOS-based Restoremechanism.For Windows x64 client systems, the legacy DOS-based Restore mechanismcannot be used for the reasons previously stated. Hence, Windows x64 clientsystems that runVxFS forWindows (SFW) cannot be restored. Because of thisissue, BMR cannot protect Windows x64 client systems that run VxFS forWindows (SFW).Currently, there is no work-around available.

■ No support for Legacy Boot Floppy Wizard on Windows x64 boot server.


With the release of NetBackup, a BMR boot server can be installed on aWindows x64 system as well. In general, BMR does not distinguish betweenthe 32-bit and 64-bit boot server on Windows.Thus, a 32-bit (x86) Windows boot server that is upgraded to NetBackup 6.5.4or greater can correctly host a 32-bit or a 64-bit SRT. Similarly, a 64-bit (x64)Windows boot server at NetBackup 6.5.4 and greater is able to correctly hosta 32-bit and a 64-bit SRT. However, the Legacy Boot Floppy Wizard is notavailable on a 64-bit boot server . If you try to run the wizard, BMR informsthe user that it is not supported on that particular version of the OS.Running this wizard can involve running some 16-bit code. On a 32-bit BootServer, this code executes under WOW32. On 64-bit boot server , however,16-bit code cannot be executed. This limitation exists in the 64-bit WindowsOS. At least one 32-bit boot server is required for the following task:If you need to create a Boot Floppy for any 32-bit Windows clients that mustbe BMR restored by using the legacy DOS-based restore.

■ No support for GPT disks.BMRdoes not supportWindows x64 client systems that have one ormoreGPTdisks.Nowork-around exists to completely supportGPTdisks; but BMRbackupmay succeed in case of such systems.If the backupwas successful, BMRmay be able to restore the system; althoughthe GPT disks are implicitly restored as MBR-based disks. Also, as Windows2003 and XP do not support system or boot volumes on GPT disks, a"System-only" restore should work correctly.For self-restores to the same physical GPT disks, the behavior is undefinedand unknown.

■ Restore of a BMR 6.5.5 Solaris 10_x64 client fails.The restore of a BMR6.5.5 Solaris 10_x64 client that has aNetBackup 7.0 clientthat is installed as part of the SRT creation process can fail intermittently. Toavoid this issue, install the NetBackup 6.5.5 client into the SRT and use thatSRT to restore the Solaris 10_x64 server. Do that even if the boot server versionis 7.0.

■ When you use the BMR Administration console to map an object, the sourceobject is disabled in the user interface if mapping is successful. That indicatesthat it cannot be mapped again unless you un-map the object. For Solaris10_x64 client configurations, when you map certain objects such as slices orvolumes, even if themapping completes successfully, the original object is notdisabled. That does not mean that the mapping has failed. A BMR Restoreusing such a mapped configuration still completes successfully.

■ A DDR restore of a BMR HP-UX 11.11 client fails the following occurs whilethe configuration is mapped:

Operational NotesNetBackup Bare Metal Restore

64

■ The client uses VxVM-based multiple disk groups

■ The disks from different disk groups are swapped

To avoid this issue, perform a system-only restore or a self restore.

■ On a Linux client, if the disk order that is specified in BIOS is not: PrimaryMaster > Primary Slave > Secondary Master > Secondary Slave, then the firstboot after a successful restore may fail. For example, the order of the disks ona live client might be:

■ /dev/sdd (hd0) [ Secondary Slave ]

■ /dev/sda (hd1) [ Primary Master ]

■ /dev/sdb (hd2) [ Primary Slave ]

■ /dev/sdc (hd3) [ Secondary Master ]

However, the disk order in the restore environmentmay look like the following:

■ /dev/sda (hd0)

■ /dev/sdb (hd1)

■ /dev/sdc (hd2)

■ /dev/sdd (hd3)

Thus, during a restore, boot loader may be installed on /dev/sda, assuming itto behd0. Thenduring the first boot, /dev/sddwould bemapped tohd0 becauseof the disk order that is specified in the BIOS and cause the first boot to fail.To avoid this issue, set the disk order in the BIOS to reflect Primary Master >Primary Slave > Secondary Master > Secondary Slave before you attempt arestore.

■ A bmradmin user account that is created on a Windows boot server during aboot server installation is saved and not deleted later.A bmradmin account is created on aWindows BMR boot server during the bootserver registration. (It is not created on non-Windows boot servers.) Thisaccount is created unconditionally because at the boot server installation andregistration time, it is not clear whether youmay require a Legacy SRT or not.Legacy SRTs require this account to perform legacy restores that use a CD orfloppy boot option. FastRestore operations do not require this account. If youdetermine that youdonotneed toperform legacy restores, thenyoucan removethis account. However, you if remove this account, and then decide that youneed it to run a legacy restore, you must recreate the account manually.Manually creating this account requires assistance from Symantec Supportbecause it is originally createdwith apredefinedpassword andother attributes.


■ The bmrsrtadm command onAIX andHP-UX prompts you to enter the desiredarchitecture (32/64) while the BMR SRT is created. If you want to installNetBackup client versions that are older than 7.0 into the SRT, the OSarchitecture type that you select should be 32-bit. For NetBackup 7.0, select64-bit as the OS architecture type.While you install the NetBackup client intothe SRT, bmrsrtadm gives the appropriate error message if there is anyincompatibility between the SRT OS architecture type and the NetBackupclient version.

■ You can use a shared resource tree (SRT) that contains a version of theNetBackup client of 7.0 or higher restore the back-level NetBackup clients.

General NetBackup operational notesThe following list contains the general NetBackup information:

■ Anupgrade to SQLAnywhere 11.0.1 has beenmade inNetBackup7.0.However,there is a restriction within that version that requires the database servername to be less or equal to 31 characters. The database server name cannotexceed 31 characters. NetBackuphas beenmodified to change the server name,from VERITAS_NB_hostname.domain_name to NB_hostname in/usr/openv/db/bin/servername. NetBackup also trims the name to 31characters if necessary.

■ To support software system management standards, NetBackup installs twoXML files on each NetBackup host. These files do not affect NetBackupfunctionality. In addition, you can identify these files by the suffix .swidtag.

■ In NetBackup 7.0, validation of data files that reside in raw devices may faileven though the Clone operation was successful. You may receive an errorthat states the validation failed for specific paths along with the paths.

■ Functionality that is introduced with the NetBackup 6.5.6 or later releasesmay not be available in the 7.0 release. This functionality is available in laterNetBackup 7.x releases.

■ When backing up and restoring a Red Hat Security-enhanced Linux (Red HatSEL) system with extended attributes (EAs) disabled and the Access ControlLists (ACLs) enabled, any file with ACLs causes the restore to complete with"partially successful" status. That is due to theRHSEL systemalways returningthe ACLs as EAs.To back up and restore ACLs on a Red Hat SEL volume, you must haveuser_xattr enabled in the mount parameters. The ACL mount parametersetting has no effect.

Operational NotesGeneral NetBackup operational notes

66

■ After youperformaFull CatalogBackupRecoverywithHeapChecking enabled,a core dump of dbeng9 occurred. Testing showed that the catalog recoverycompleted successfully and that bprecover handled the core dump issueappropriately. You can delete and ignore this core dump.

■ A potential for data loss has been seen where Distributed File SystemReplication (DFSR) paths may be skipped on a backup. However, it is reportedas a Status 0 if the DFSR path exceeds 256 characters and DFSR is backed upwith shadow copy.See the following Technote on the Symantec Support Web site for moreinformation about this issue.

■ http://support.veritas.com/docs/336578

NetBackup Access ControlThe following list contains the items that pertain specifically toNetBackupAccessControl (NBAC):

■ OnaNetBackup7.0 host, if NBAC is enabled, theNetBackup servicesmay causea core-dump after one week of running. A failure in ‘Renewing’ a servicecredential causes this issue.The typical service credential validity period is one year. NetBackup attemptsto renew a service credential when it is seven days old to ensure continualavailability of the credential. Due to an error, this scheduled task can causesome of the NetBackup processes to dump core.To avoid this issue, create a cron job or scheduled task to "touch" the existingcredential files that ran at intervals of fewer than seven days.

The following files are the files that need to be touched:

■ For UNIX, /usr/openv/var/vxss/credentials/*

■ For Windows (32-bit),%Program_Files%\VERITAS\NetBackup\var\vxss\credentials\*

■ For Windows (64-bit), %Program_Files(x86)%\VERITAS\NetBackup\var\vxss\credentials\*

If you use this workaround, the NetBackup services do not automaticallyattempt the service credential renewal. Thatmeans that the credentials expireafter one year.

You can do the following to mitigate that:

■ Run the following command to regenerate a credential before it expires(one year)./usr/openv/netbackup/bin/admincmd/bpnbaz -setupclient hostname

67Operational NotesNetBackup Access Control

■ Extend the credential expiry from the default of one year to longer term.Perform the following steps in an example that extends the expiry fromone year to five years:- You must first calculate the number of seconds that would be. In thisexample, the total number of seconds is 157680000 (60 * 60 * 24 * 365 * 5).- Go to /usr/opt/VRTSat/bin (UNIX) or%Program_Files%\VERITAS\Security\Authentication\bin (Windows).

- Execute the following:vssat setexpiryintervals --pluginname vx

--prpltype user --credexpiry 157680000

■ If you upgrade to this version of NetBackup from a previous version that hasbeen configured to use NBAC, you should run the bpnbat -login commandbefore you start the upgrade. During the upgrade, the installer connects to theAZ server and upgrade NBAC data. The user that is specified during bpnbat

-login should therefore be a member of the NBU_Security Admin group. Ifthe upgrade of NBAC data fails then a message appears and informs you thatyoumustmanually run bpnbaz -upgrade. Before running this command, youmust perform a bpnbat -login.

■ Symantec recommends that the NBAC NBU_Security Administration groupnever be modified.

■ With the need for increased security, it is critical to be able to configureNetBackup Access Control (NBAC) in a clustered NetBackup serverenvironment. You can find detailed steps on how to enable NBAC for a highlyavailableNetBackupmaster server in a clustered environment in the followingtechnote.See, http://entsupport.symantec.com/docs/288471.

■ On a Windows system, a non-root NBU_Admin member (in an NBACconfiguration) is unable to perform a task (such as a restore) that the usershould be able to perform.

The following symptoms occur:

■ The destination client dropdown field is grayed out in the Backup, Archive,and Restore (BAR) user interface. Ad the destination client can only be thelocal machine.

■ A restore fails to recover some (or all) of the fileswith themessage, "Accessdenied for restore of file". That happens if the user does not have writepermission on the destination of the restore., or the file being restoredwasnot readable by the user at that time that it was backed up.

To avoid this issue, make the non-root NBU_Admin a member of the "BackupOperator’s" operating system group onWindows.Members of this group havethe necessary privileges.

Operational NotesNetBackup Access Control

68

The term non-root on Windows means that you are not an Administrator.

NetBackup database agentsThis section contains the general operational notes that can apply to more thanone NetBackup database agent.

■ The following applies to any agent that uses Granular Recovery Technology(GRT) Active Directory, Exchange, or SharePoint.File names with more than 260 characters cause the restore operation to failwhen you perform backups and restores with Granular Recovery Technology(GRT) on Windows 2003 R2. A hotfix is available from Microsoft to addressthis issue.http://support.microsoft.com/kb/955012

The remaining topics within this section contain the operational notes that arespecific to the individual database agents that NetBackup supports.

Lotus Notes agentThe following list identifies the items that pertain specifically to the Lotus Notesagent:

■ Compression is supported only for Lotus Domino servers onWindows and notonUNIX. In addition,Windows compressed images are not restorable to LotusDomino servers on UNIX.

■ Requirements for Lotus r6.0.3 and Lotus r6.5.0 on LinuxSupport for LotusR6.0.3 and LotusR6.5.0 on Linux requires a hotfix to resolvethe following SPR: SPR#JCHN5QVL3E (which addresses a transaction logrecovery issue).

After you install the hotfix on a LotusDomino server, youmustmake a changeto the notes.ini file for Domino to work properly with NetBackup.

■ Add the following to the end of the notes.ini file for eachDomino partition:DEBUG_SEMOP_ERRNO0_EINTR=1.

The last character in ERRNO0 is a zero.

■ Restart the Domino server partition.

The hotfixwas integrated into theR6.5.1 andR6.0.4 releases. In these releases,customersneed to set the flagDEBUG_SEMOP_ERRNO0_EINTR in thenotes.inifile. This flag allows retries to happen if andwhen the operating systemreturnsan unexpected EINTR while LN performs semaphore operations.Seewww-10.lotus.com/ldd/r5fixlist.nsf/Search?SearchView&Query=JCHN5QVL3E

69Operational NotesNetBackup database agents

■ Requirements for Lotus r6.0.3 or r6.5.0 on Solaris SPARC and AIXSupport for Lotus R6.0.3 or R6.5.0 requires an IBM hotfix to address SPR#JCHN5QVL3E, which involves a transaction log recovery issue. This issue hasbeen fixed in R6.0.4 and R6.5.1.See:

www-10.lotus.com/ldd/r5fixlist.nsf/Search?SearchView&Que

ry=JCHN5QVL3E

■ Requirements for Lotus r6 and r6.5 on LinuxSupport for any version of Lotus R6 or R6.5 on Linux requires a change to thenotes.ini file for Domino to work properly with NetBackup.

For each Domino partition, perform the following steps:

■ Add the following line to the end of the notes.ini file:

DEBUG_SEMOP_ERRNO0_EINTR=1

(NOTE: The last character in ERRNO0 is a zero.)

■ Restart the Domino server partition.

For Lotus R6.5.5, R7.0, and going forward, the setting in notes.ini file is notrequired.

■ Requirements for Lotus r6.03 and Lotus r6.5.0 on WindowsSupport for LotusR6.0.3 andLotusR6.5.0 onWindows requires a combinationhotfix to resolve the following twoSPRs: SPR#THUR5LPPW9 (which addressesa file path syntax) and SPR#JCHN5QVL3E (which addresses a transaction logrecovery issue).A single IBM hotfix is available to address both issues. You should remove theprevious Lotus hotfixes before you install this new combination hotfix. Theseissues have been fixed in R6.0.4 and R6.5.1.See, www-10.lotus.com/ldd/r5fixlist.nsf/Search?SearchView&Query=JCHN5QVL3E.

See, www-10.lotus.com/ldd/r5fixlist.nsf/Search?SearchView&Query=THUR5LPPW9.

NetBackup for Microsoft ExchangeThe following list contains operational notes for the NetBackup for MicrosoftExchange database agent as they pertain to this release of NetBackup:

■ NetBackup 7.0 does not support the redirection of public folder items.

■ GUI initiation of an off-host snapshot backup

Operational NotesNetBackup database agents

70

When using the NetBackup Client user interface or the bpbackup command toinitiate an Exchange off-host alternate client backup, the backup fails. Instead,use the NetBackup Administration Console to initiate a manual backup forthat Exchange policy. See the "Testing Configurations Settings" section in theNetBackup for Exchange System Administrator ’s Guide for instructionsregarding a manual backup operation.

■ Restoring Exchange in a ClusterWhen you restore data in an Exchange cluster environment, one must set thedestination client value to be the virtual server name. You can restore anExchange database using a NetBackup client-only installation on a cluster.However, itmaynot be possible to change the destination client value tomatchthe virtual server name. In that case, use a NetBackup Client user interface onaNetBackup server to change the destination client value to the virtual servername.

■ Exchange snapshot backups fail with status 41 "Network connection failed".That problemoccurswhenyouperformanExchange snapshot backup attemptwith Allow multiple data streams set on the policy, and with a large numberof storage groups or databases in the file list, or with Microsoft InformationStore:\* in the file list.To resolve this issue, increase the value of the Client Connect Timeout in themaster server Properties > Timeouts. Increase the Client Connect Timeoutto a value that is greater than the time that it takes the client to perform thesnapshot freeze processing.

■ Exchange 2010 DAG backups may fail with status 48 “Client hostname notfound”.The initial step in an Exchange 2010DAG backup is the bpresolver job on thevirtual DAG node. Bpresolver may return the list of Exchange servers toperform the backup in a Fully Qualified DomainName (FQDN) format, insteadof a node name.The work-around for this issue is to configure the FQDN so that it is resolvedto the correct IP address. Modify the NetBackup server’s hosts files or correctDNS entries to resolve that.

■ Intermittent failures canoccurwhenyouattempt tobrowseor restore amailboxfrom an Exchange GRT image from a Windows 2008 R2 Exchange server.When you attempt to browse or restore an Exchange mailbox from a GRTimage fromaWindows2008R2Exchange server, youmayexperience failures.Towork around this issue, try the browse or restore operation again. Symantecand Microsoft are working on a solution for this problem.

■ During aMailbox item restore,multiple “seed” emails from the backup serviceaccount may be sent to the mailbox being restored.


■ Restores of Exchange 2010 database in a Database Availability Group (DAG)environment notes:

■ When you restore a database to a recovery database, you cannot use theDAG virtual name as the destination client. Instead, use the node namewhere the RDB exists or the stand-alone Exchange 2010 server.

■ When you restore a database or databases to a different DAG than whereit was backed up, you cannot use the DAG virtual name as the destinationclient. Instead use the node that contains the active DB being restored to.

■ When you select multiple backup images from a DAG backup with EnableGranular Recovery selected, granular level restores may fail. Selecting onebackup image at a time does succeed.

■ When you restore databases or granular items of a DAG backup, the restorestatus may be empty from the backup and restore user interface. The statusis empty if the restore is initiated from a node in the DAG. You should initiatethe restore from the active DAG node or a NetBackup server to properly seethe activity status.

■ User-initiated backups in a DAG environment fail if initiated from a node intheDAG that is not currently active for the virtualDAGname. Initiate the userbackup from the active DAG node or manually start the backup from theNetBackup master to properly start the backup.

■ Exchange 2010 granular item restores may result in duplicate messageattachments when you restore the mail items that were previously restoredand then backed up with granular recovery.

■ The company field of task objects doesnot get properly restoredwithExchange2010 granular recovery.

■ Snapshot and catalog clean-upnot performedafter an InstantRecovery restorerolls back some snapshot volumes and copies back of others.The problem occurs when you recover from an Exchange Instant Recoverybackup and one volume is rolled back while another is not. For example, thatmight happen with a roll-forward recovery, in which the database volume isrolled back and the log volume files are copied back. The problem occurs onlywith the default (Microsoft System) VSS provider. With this provider, therollback consumes the snapshot volume. That leaves a partial snapshot setand an invalid IR copy of the backup image in the catalog.To resolve this issue, expire Copy 1 of the backup image in the catalog. Thenuse VShadow to make sure that the snapshot volume has been deleted.

■ The bpfis.exe memory usage grows when a snapshot of multiple storagegroups or Exchange 2010 databases is processed.


72

In NetBackup testing, the bpfis.exe process memory usage grows by a fewmegabytes per storage group or Exchange 2010 database. If a single snapshotjob processes a large number of storage groups or Exchange 2010 databases,the process virtual memory size can approach or exceed one gigabyte.The workaround is to make sure that you have sufficient virtual memory toaccommodate this growth, or to break up your backup into smaller snapshots.

■ Instant recovery backups are not supported for Exchange in a clusterenvironment (Exchange 2007 cluster, Exchange 2007 CCR, or Exchange 2010DAG).

■ Exchange 2010 offhost backups are not supported in NetBackup 7.0. Supportwill be added shortly after the release of 7.0.

■ An attempt to restore from an Exchange 2003 and 2007 offhost incrementalbackupmay result in a failure tomount theExchangedatabase after the restore.A special procedure is required to mount the database after the restore. Thisissue does not impact the ability to mount after restoring only an Exchangeoffhost full backup. This issue will be resolved shortly after the release ofNetBackup 7.0.

NetBackup for Microsoft SharePointThe following topics contain the operational note information that relates to theNetBackup for Microsoft SharePoint Portal.

General SetupThe following is a list of general items pertaining to the NetBackup for MicrosoftSharePoint:

■ When you use SharePoint 2003 load balancing, all load-balanced Web sitesmust be uniformly identified in IIS using either host headers or IP addresses,but not both. Environments which mix host headers and IP addresses acrossload-balanced servers are not supported.

■ To prevent restore failures, the IIS Default Application Pool identity must bea valid SharePoint user ID .

Operational IssuesThe following operational issues exist for the Microsoft SharePoint:

■ When theSharePoint Search Index service updates the databases, it sometimescontends with NetBackup for access to the portal index database. That canresult in a failed backup or restore operation of that database. If that occurs,repeat the backup or restore operation until successful.


■ The metadata modified date is restored as the restored date.Themetadata restore is for SharePoint 2007only. TheSharePoint 2003 restoresto the current date and time.

■ TheSearchCenterwithTabs template has somemissing items for the restore.Some items are not restored using GRT with the Tabs template. As aworkaround, restore the content database that contains the Tabs templatesite.

■ The Search Center template, Discusion Board list item fails to restore.Some items are not handled properly using GRTwith Search Center template.As aworkaround, restore the content database that contains the SearchCentertemplate site.

■ TheSharePointGRE restore view status displays incorrect characters for i18nSimple Chinese. The restore does recover the files names with the correctcharacters.

■ When you perform a SharePoint granular backup on a federated farm, thebpfis child job gets a status 130 error on first attempt. The second attempt issuccessful. To work around this issue, attempt the backup a second time.

■ A SharePoint backup fails with a bpresolver core.

The cause of this issue, is unequal number of parenthesis on the databasename field. To avoid this issue, make sure that you have an equal number ofparenthesis that match in a database name.

■ A deleted list item that is in a Content-DB with Chinese characters may notrestore to the original location. To resolve this issue, restore the item and anyattachments that exist, to a file system and then add it to SharePoint.

■ Restoring SharePoint picture libraries to the original location may fail whenthere are empty containers preceding the picture library.When there are no empty containers preceding the picture library, then therestore works. As a workaround, the data can be recovered by redirecting toa file system or restoring the sites content database.

■ The SharePoint backup debug files are left inINSTALL_DIR\VERITAS\NetBackup\Temp\

If the debug level is set to a value that is greater than 0 for databases, theSharePoint debug files on the backend are created during the backup in theINSTALL_DIR\VERITAS\NetBackup\Temp\directory.These files arenot removedafter the backup. That is intentional behavior for debugging purposes. Youcan remove these files if you are low on space.

■ When you restore the most recent version of a document, picture, orattachment the restore works, however a status 5 error occurs.


74

If you encounter this issue, you should know that the correct version of theitem is restored and you can ignore the status 5 error.

SQL server agentWhen you use the NetBackup for SQL Server user interface on 64-bit platforms,the online Help cannot be opened. This problem originates within the Windows64-bit SDK and is expected to be resolved in a future release. Until then, open thehelp file directly using the Windows Explorer:

install_path\VERITAS\Help\nbmssql.chm

Sybase server agentThe following is a list of knownoperationnotes that are pertinent to theNetBackupSybase server agent:

■ With NetBackup 7.0, Sybase has changed its name from Adaptive ServerAnywhere (ASA) to SQL Anywhere. In addition, the Windows service namehas changed from ASANYs_VERITAS_NB to SQLANYs_VERITAS_NB.

■ The Sybase service, dbsrv11, may cause a core dump to occur on a master orremote Enterprise media server that has Sybase 11.0.1 installed and IPv6enabled. If this issue occurs, nbemm, nbrb, and nbars do not function properly.In addition, you are not able to back up, archive, restore, or list a storage unit.This issue affects the HP-UX, AIX, and Solaris, platforms.

If you encounter this issue, use the following procedure as a work-around:

■ Stop NetBackup.

■ Disable IPv6 by entering "ipv6=NO" in the database server configurationfile.Change: tcpip(LocalOnly=Yes;ServerPort=13785)

To: tcpip(LocalOnly=Yes;ipv6=NO;ServerPort=13785)

NOTE: LocalOnly=Yes is optional. It can be missed or specified asLocalOnly=NO or LocalOnly=YES.

You can locate the database server configuration file at the followinglocations:- On UNIX/Linux platforms:/usr/openv/var/global/server.conf (This is true as long as this file hasnot been moved to a different location.)- On Windows platforms:install_path\NetBackupDB\CONF\server.conf

■ Start NetBackup.


About NetBackup Enterprise Vault AgentThe following list contains the known operation notes that are pertinent to theNetBackup Enterprise Vault Agent:

■ AnEnterpriseVault backuppasses as apartial successunder a specific scenario.Thepartial success occurswhenyouuse an EV_INDEX_LOCATIONdirective, andapolicywith twoEnterpriseVault servers that point to the same index location.

■ If the NetBackup/logs/AltPath folder is not present, the Enterprise Vaultredirected restore fails with a status 5 error. This folder must be present toperform a redirected restore.

NetBackup Hyper-VThe following itemsdescribe operational information for theNetBackupHyper-Vagent:

■ Use of a volume GUID path requires NetBackup patch 7.0.0.1 or laterNetBackup for Hyper-V has a known problem involving volume GUID paths.The following is an example of a volume GUID path:\\?\Volume{26a21bda-a627-11d7-9931-806e6f6e6963}\

If volume GUID paths exist in your Hyper-V environment, you must installNetBackuppatch7.0.0.1 or a later release. Contact SymantecTechnical Supportto obtain the patch.

■ Data is restored to theHyper-V server systemdrive if restore path is incorrectlyspecified (Windows only)When you restore selected files by means of a shared location on the virtualmachine (using the Backup, Archive, and Restore interface on Windows), anincorrectly specified UNC path (share name) for the destination should causethe restore to fail, with status code 5. Instead, the files are restored to thesystem drive of the Hyper-V server.An example of an incorrect path is:\server_name\drive_name\directory_name (pathhas only one leading slash)

Correct path format would be:\\server_name\drive_name\directory_name

The files are restored to the Windows system drive on the Hyper-V server(such as the C drive). The restore location on the system drive includes theserver name and drive name as specified in the UNC path.This issue will be fixed in a future NetBackup release, so that NetBackup failsthe restore when a path is incorrectly specified.

■ Backup of Virtual Machines(VM) fails if the files that represent the VM havevolume GUIDs instead of a drive letter in the pathname. For example, while

Operational NotesNetBackup Hyper-V

76

the VM is created, if the path of one ormore of theVHD files are specifiedwitha volume GUID, then the backup of the VM fails.\\?\Volume{7b544c52-9cb7-11dd-a453-806e6c6e6963}\myVM\myvhd.vhd

This issue will be fixed in the first update after the NetBackup 7.0 release.

NetBackup interfacesThe following subsections contain the release and operational information aboutthe NetBackup interface, such as the NetBackup Administration Console, and theActivity Monitor.

NetBackup Administration Console for WindowsThe following list contains the items that pertain to theNetBackupAdministrationConsole for Windows:

■ When you log errors from a 6.5 media server, NetBackup stores the errors intheMedia log. NetBackup also saves the errors into separate logs. That enablesyou to view specific error types such as tape errors in Tape log report or diskerrors in the Disk log report.However, if you attempt to log errors from a 6.0 media server, you can onlyview the errors in theMedia log.NetBackupdoesnot log the errors into separateerror logs. If you select, NetBackup Management > Reports > Tape reports >Tape logs, no result is produced. The Tape log report appears empty.

■ Disk-based data protection resources

The following items describe limitations with the disk-based data protectionreporting in this release of NetBackup:

■ Help for the ImagesOnDisk reportmightnot provide complete informationat all times.

■ The Images On Disk report does not show data for a few columns (such as,Number of Files and Offset) for report on any disk type.

■ The Disk Log report does not show information for the columns Schedule,Policy, and Status for Disk based reports.

■ The storage unit creation pages are not available in the Disk Pool wizard if thelogged on host is a media server. These pages are applicable only for a masterserver.

77Operational NotesNetBackup interfaces

NetBackup java interfacesThis section contains operational the notes that are applicable toNetBackup-javainterfaces.

General NotesThe following list contains the general operational information that pertains tothe NetBackup-Java Administration Console:

■ Reduced functionality (only the Backup, Archive, and Restore componentavailable) orCannotConnect errors during initializationof theNetBackup-JavaAdministration Console occurs if one or more of the NetBackup services ordaemons on the host that is specified in the logon dialog is not running.

■ TheNetBackup-Java Administration console core dumps if you use SimplifiedChineseUTF-8 locale on a Solaris SPARC64-bit systemwith Solaris 10Update2 and above installed.This problem is caused by the Sun Microsystems™ issue, 6901233.See, http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6901233 formore information about this issue.If you encounter this issue, apply the Solaris patch that Sun provides to fixthis issue 6901233.

■ The Skip verification and force roll-back option does not appear in RestoreMarked Files dialog.When you configure a Point in Time rollback restore, the Restore MarkedFiles dialog in the NetBackup-Java Administration console displays the Skipverification and force roll-back option as Overwrite existing files. Thefunctionality of the Overwrite existing files option is the same as the Skipverification and force roll-back option, however the label is misleading. Thenames of these options will be corrected in a future release of NetBackup.

■ TheNetBackup-JavaadministrationconsoleonWindows (WDC) cannot connectto a UNIX master sever with a Japanese package. When you attempt to log onto the master server, the NetBackup-Java administration console hangs at apoint when the following status statement appears.

Checking if NBAC is configured.

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

■ A Windows Manager that is configured for auto focus is not supported. Autofocus means that windows are activated (get the focus) when you position the

Operational NotesNetBackup interfaces

78

mouse cursor over them. The following explains how to correctly set up a CDEenvironment.In the CDE environment, use the Style Manager -- Window dialog to changethewindowbehavior to Click InWindowToMakeActive. NetBackup Java doesnot run properly if the Style Manager has the following selected: Point inWindow To Make Active.

■ If you are not set up properly to display to a machine from where you runjnbSA, one of the following happens:

■ Nothing, because it is probably displayed on themachine fromwhere jnbSAwas run.

■ The command fails with no error message. (That means the operatingsystem command prompt was received.

java.lang.InternalError: Can’t connect to X11 window

server using "host_name" as the value of the DISPLAY

variable.

Before you start jnbSA, be sure to execute the xhost command on themachinewhere you intend to see the user interface and set the DISPLAY environmentvariable on themachine executing jnbSA before starting jnbSA. Reference theman page for the xhost command for additional capabilities.

■ Symantec recommends that only one administrator work on an object at atime. That eliminates the possibility of configuration conflicts if more thanone administrator attempts administration tasks simultaneously on the sameobject. If this situation should occur, the last update that is made prevails.

■ Memory requirements to run the NetBackup-Java Administration ConsoleSymantec recommends that you run the console (jnbSA,jbpSA, or JavaWindowsDisplay Console) on a machine with at least 1 gigabyte of physical memoryand 256 megabytes of memory available to the application.

■ Remote display back of the NetBackup-Java Administration Console is notrecommended.Symantec does not recommend running the NetBackup-Java AdministrationConsole in a remote display back configuration. Problems have occurred withcertain user interface controls (such as, incorrect box operations, very sluggishtable scrolling with large numbers of rows, and table display problems withlarge numbers of rows). Other problems may occur that can cause the userinterface to hang because of a Java Virtual Machine (JVM) failure. The JVMfailures occur most often on AIX platforms.

79Operational NotesNetBackup interfaces

Therefore, Symantec recommends that you run the NetBackup-JavaAdministration Console on your local desktop to administer any NetBackuphost (by specifying that remote host in the logon dialog of the user interface).

TheNetBackup-JavaAdministration Console runs on the following platforms:

■ Solaris SPARC, Solaris x64

■ HP-UX

■ AIX

■ Red Hat and SUSE Linux

■ Windows platforms.For the Windows platform, installation is done using the Install JavaAdministration Console option in the NetBackup Windows installationuser interface. Refer to Chapter 2 (Platforms Supporting the NetBackupAdministration Consoles for UNIX) of this document for the supportedversions of these platforms.

■ Multiple bpjava processes per instance of the console

For increased performance and support to multitask easier on the console,multiple bpjava processes appear on the host that is specified in the logondialog. The number varies depending on the tasks that you attempt in theconsole.

■ Remote display of the NetBackup-Java console in multi-byte localeenvironments is not supported.

Activity monitorThe following list shows the items that relate to the NetBackup Activity Monitor:

■ The ability to delete a large number of jobsWhen deleting a large number of jobs, do not leave the Activity Monitor nodeor close the NetBackup Administration Console while any of the deleted jobsare still visible in the Jobs tab. If the Activity Monitor is shut down while jobsare deleted, some of the jobs may not be deleted. The Activity Monitor can beshut down when you leave the Activity Monitor node or when you close theNetBackup Administration Console.

■ The following message is displayed if you stop the bpdbm daemon on therelevant server when Activity Monitor is active.

Activity Monitor failed and must be restarted.

To recover, first correct the problem described below and

then refresh.

Connection to bpjobd on server <server_name> failed.

Operational NotesNetBackup interfaces

80

The reason this message occurs is that stopping the bpdbm daemon also stopsthe bpjobd process. Upon a successful startup of bpdbm (which starts bpjobd),you can use the refresh option on the toolbar to refresh the Activity Monitorjob data. The refresh option is only available upon lost communications withthe job daemon, bpjobd.

Storage unit configurationThe following list shows operational notes for the Storage Unit configuration:

■ The maximum fragment size of a disk storage unit has increased from 2gigabytes to .5 terabytes.If amedia server of a previous releasehasDiskStorageUnits (DSUs) configuredwith a different maximum fragment size, the storage units are notautomatically increased to the new default of 524,288 megabytes after anupgrade. To make the best use of the storage unit, consider increasing thefragment size on upgraded storage units.

■ The bpstuadd command line option -dspath is no longer valid or supported.

About Symantec OpsCenterThe following list contains the items that relate to theSymantecOpsCenter feature:

■ If you plan to install OpsCenter on AIX, ensure that the XLC runtime versionis 9.0 or greater.

■ After VBR upgrade, data is not displayed under Storage and Devices tabsAfter aVBRupgrade, data is not displayedunder theStorage andDevices tabsin Monitoring. (Storage units, Robots, Drives, and so forth.)The data is not displayed as VBR does not collect any monitoring data, onlythe names are provided from the Job records.This data is collected after the upgrade as part of the regular data collection.

■ AnOpsCenter installation is not supported for the versions that are older thanVBR 6.5.You cannot install OpsCenter on a system that hasVBR installedwith a versionthat is lower than 6.5 (for example, 6.2.x, 6.0.x, etc.).To work around this issue, upgrade the version of VBR to 6.5 or 6.6 and thenupgrade to OpsCenter. Or uninstall VBR first and then install OpsCenter.

■ Week at a Glance Report performance declines as the data increases.Week at a Glance Report’s performance declines as the data to be displayedin the report increases. For example, running a two-month report is slowerthan running a two-week report.

81Operational NotesAbout Symantec OpsCenter

■ After a reboot, the OpsCenter processes are not start automatically in AIX orSUSE Linux systems. Symantec recommends that you start the OpsCenterprocesses after you perform a reboot.

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

■ After a rollback, the keys are not recreated to display an entry in Add orRemove Programs dialog box.If a rollback occurs during anuninstall ofOpsCenter, the keys arenot removedfrom AddorRemovePrograms dialog box. You must remove OpsCenter. Usesetup.exe to remove OpsCenter.

■ After you reboot a SUSE11 Server, and even thoughOpsCenter server servicesare running, an attempt to logon may not succeed.Occasionally, OpsCenter services may not start on reboot in case of SUSE 11.That may happen some times because of the PBX taking time to start.

NetBackup media and device managementThe following subsection contains the information that is pertinent toNetBackupmedia and device management functionality.

Media SharingThe access control feature of Sun StorageTek ACSLS controlled robots is notcurrently compatible with Media Sharing. This feature restricts volume accessusing the requesting host’s IP address. Use caution when implementing MediaSharing in an ACSLS environment.

Enterprise Media ManagerThe following list shows the operational note items that pertain to EnterpriseMedia Manager (EMM):

■ A new script, pending_request_notify, has been added to this version ofNetBackup.The NetBackup Resource Manager calls the pending_request_notify scriptafter a pending request is issued for a media resource (tape volume). To sendan E-mail notification when a pending request is initiated, include an E-mailaddress in the script where indicated. (The root user must run this script.)

Operational NotesNetBackup media and device management

82

Copy the script from the goodies directory into the bin directory on the EMMserver (usually the master server):

■ UNIX:/usr/openv/netbackup/bin/goodies/pending_request_notify

Into/usr/openv/netbackup/bin/

■ Windows:Install_path\NetBackup\bin\goodies\pending_request_notify.cmd

IntoInstall_path\NetBackup\bin\

If the script exists in the bin directory, the following parameters are passedto the script: Media ID, barcode, action code, robot type, robot number, mediaserver, volume group, and pending time (in seconds since the UNIX epoch).

■ NetBackup uses the Media ID for disk as a unique identifier that can be tracedback to a volume on the array. The Media ID is an opaque string that hasinternal meaning to NetBackup, but to nothing else. In addition, the Media IDcanbe correlated to avolumeby runningnbdevquery -listmediaid command.

■ SCSI persistent reserveNetBackup can use SCSI persistent reserve in and persistent reserve out toconfigure exclusive access protection to tape drives so that other host busadaptors (HBAs) cannot control the drives during the reservation. SCSIpersistent reserve provides more resiliency and fault tolerance than SPC-2SCSI reserve and release, which is the default access protection method inNetBackup.

SAN Client and Fibre TransportThe following list contains the operational note information that pertains to SANClient and Fiber Transport:

■ The NetBackup Client Encryption Option is not supported on UNIX and LinuxSAN clients.

■ The QLA-2344 four-port FC adapter's usable aggregate performance is notsignificantly greater than a two-port QLA-2342 when used in the same PCI-xslot for SAN Client target mode. The advantage a QLA-2344 HBA offers is theability to spread its aggregate performance over four ports instead of two. Ifyou use direct-connection (rather than FC switches or bridges) between SANclients and a Fibre Transport (FT) media server and only two ports are fullyloaded with Fibre Transport traffic at the same time, the QLA-2344 HBAperforms similarly to two QLA-2342 HBAs but uses one less PCI slot.

83Operational NotesSAN Client and Fibre Transport

■ IBM 6228 HBAs require the following version of the AIX FC driver to ensurethat the appropriate data is returnedwhen a task is aborted. Not installing thefollowing driver can result in a hung Fiber Transport (FT).AIX FC driver version level 5.2.0.75 for IBM 6228 card _ AIX

Oslevel 5200-07

■ For 64-bitNetBackupmedia servers, PCI-express, andPCI-X slots are supportedfor theQLogic Fibre Channel host bus adapters (HBAs) that are used to connectto the NetBackup SAN clients. Legacy PCI 33 and 66 Mhz slots are notsupported.

■ On the NetBackup media servers, Symantec recommends that you do not uselegacy PCI cards on the same bus as a QLogic FC HBA that is used to connectto SAN clients. A slower PCI card reduces the speed of the controlling bus andtherefore all other cards in that bus. Consequently, data transfer rates arereduced and performance is degraded.

■ If you use data compression or encryption for backups, backup, and restoreFibre Transport pipe performance may degrade significantly. In someconfigurations, compression may reduce performance by up to 95% ofuncompressed performance.

■ NetBackup SAN clients cannot also be NetBackup servers.

■ No support for FlashBackup restores over an FT pipe.

■ No support for Fibre Channel arbitrated loop (FC-AL) hubs.

SharedDisk support in NetBackup 7.0 and laterTheSharedDisk option is not supported beginningwith theNetBackup7.0 release.

You can use a NetBackup 7.0 master server to configure, manage, and operateSharedDisk on NetBackup 6.5 media servers.

For information about using SharedDisk, see the documentation for yourNetBackup 6.5 release.

NetBackup AdvancedDisk optionNetBackup does not support clustering of AdvancedDisk media servers.

NetBackup Client DeduplicationThe following items pertain to NetBackup 7.0 Client Deduplication:

Operational NotesSharedDisk support in NetBackup 7.0 and later

84

■ NetBackup 7.0 Client Deduplication does not support multiple copies.

■ NetBackup 7.0 Client Deduplication does not support encryption.

About the NetBackup Media Server DeduplicationOption

The following itemspertain to theNetBackupMedia ServerDeduplicationOption:

■ On UNIX and Linux systems on which a deduplication storage server is notconfigured, the netbackup start script returns status 2. The status 2 indicatesthat the script cannot start the deduplication daemons. Because a storageserver is not configured, the daemons cannot be started. The error is spurious;you can ignore it.

■ For theMicrosoft Exchange backups that use the NetBackup Exchange Agent,deduplication rates are low even though data has not changed since the lastbackup.

■ NetBackup does not support clustering of deduplication storage servers orload balancing servers.

■ The NetBackup Media Server Deduplication Option does not support NFSmounted file systems. Therefore, do not enter an NFS file system when youconfigure the data storage path.

■ Symantec expects Oracle database stream-based backups to achieve lowdeduplication rates. Stream-based backups include deduplication within asingle backup and deduplication between a backup and data already backedup. However, Snapshot Client backups of Oracle databases achieve highdeduplication rates across full backups within our test environments. OracleSnapshot Client based backups have higher deduplication because the data isaligned on consistent file or tablespace boundary.

■ NetBackupdoesnot support the Snapshot Client off-hostmethodMedia ServerCopy on NetBackup clients that deduplicate their own data.

PureDisk Deduplication Option (PDDO)The PureDisk plug-in that is used for NetBackup deduplication cannot reside onthe same host as a PureDisk Deduplication Option (PDDO) agent. Therefore, donot use the same media server for both NetBackup and as a PDDO host.

85Operational NotesAbout the NetBackup Media Server Deduplication Option

NetBackup Snapshot ClientThe following items pertain to the NetBackup Snapshot Client :

■ NetBackup does not support creating a disk array snapshot if a VxVM diskgroup on the array contains a software-based snapshot of the VxVM volume.If a software-based snapshot (such as from the VxVM method) already existsof a VxVM volume on the disk array, NetBackup cannot create a disk arraysnapshot of a file system that is configured on the VxVM volume. Snapshotcreation fails (with final status 156), and the bpfis log contains a messagethat reports a vxmake command failure.

Youmust delete the existingVxVMsnapshot from theVxVMdisk group beforeyou run a backup with a disk array snapshot method. This issue will be fixedin a future release of NetBackup.Examples of disk array snapshot methods areEMC_CLARiiON_SnapView_Snapshot, HP_EVA_Snapshot,Hitachi_CopyOnWrite, and IBM_StorageManager_FlashCopy. All disk arraymethods are described in theNetBackupSnapshotClientAdministrator'sGuide,in the chapter titled "Configuration of snapshot methods for disk arrays."

■ Instant Recovery restores may fail from a backup that a FlashSnap off-hostbackup policy made.Fromapolicy thatwas configuredwith the FlashSnapoff-host backupmethodand with Retain snapshots for Instant Recovery enabled, the backups thatwere made at different times may create snapshot disk groups with the samename. As a result, only one snapshot can be retained at a time. In addition,NetBackup may not be able to remove the catalog images for the snapshotsthat have expired and been deleted. It appears that you can browse the expiredsnapshots and restore files from them. But the snapshots no longer exist, andthe restore fails with status 5.

■ For this release, NetBackup does not support Snapshot Client VSS off-host filebackups using a Storage Foundation for Windows (SFW) VSS provider.

■ NetBackupdoes not support the Snapshot Client off-hostmethodmedia serverCopy on NetBackup clients that deduplicate their own data.

■ The following list of items pertain to restoring individual files froman InstantRecovery snapshot:

■ Whenyou restore files froma snapshot that ismade for an InstantRecoveryoff-host alternate client backup: NetBackup consults the exclude list onthe alternate client even when it restores files to the primary client. If theexclude list on the alternate client is different from the exclude list on theprimary client, any files that are listed in the exclude list on the alternateclient are not restored to the primary client.

Operational NotesNetBackup Snapshot Client

86

For example, if the alternate client's exclude list has the entry *.jpg, andsome .jpg files were included in the primary client backup, the .jpg filescan be selected for the restore but are not in fact restored. To restore thefiles, you must change the exclude list on the alternate client.

■ Whenyou restore files froma snapshot that ismade for an InstantRecoverybackup (local or off-host alternate client): If the exclude list is changedafter the backup occurred, NetBackup honors the latest version of theexclude list during the restore. Any of the files that are listed in the currentexclude list are not restored. Also, as noted in the previous item, the excludelist on the alternate client takes precedence over the exclude list on theprimary client.For example: If the current version of the exclude list has the entry *.jpg,and some .jpg fileswere included in the backup, the .jpg files can be selectedfor the restore but are not in fact restored. To restore the files, you mustchange the exclude list on the primary (or alternate) client.

Note: For ordinary backups (not based on snapshots), any files that wereincluded in the exclude list are not backedup. For snapshot-based backups,however, all files are included in the snapshot. The exclude list is consultedonly when a storage unit backup is created from the snapshot. If thesnapshot is retained after the backup (for the Instant Recovery feature)and the snapshot is available at the time of the restore, NetBackup restoresfiles from the snapshot. Since all files are available in the snapshot(including those that would be excluded from a storage unit backup),NetBackup incorrectly consults the current exclude list on the client oralternate client. Any files in the exclude list are skipped during the restore.

This issue will be addressed in a future release of NetBackup.

■ Problem with "Restore from Point in Time Rollback"When you start a "Restore from Point in Time Rollback" from an InstantRecovery backup, the primary file system is verified against the snapshot tomake sure that no new files were created on the primary file system after thesnapshot was taken. Note that a rollback deletes all files that were createdafter the creation-date of the snapshot that you restore. Rollback returns afile system or volume to a given point in time. Any data changes or snapshotsthat were made in the primary file system after that time are lost as a resultof the rollback.However, during the verify operation for the rollback, the snapshot ismountedand in some cases, the snapshot cannot be unmounted. In that case, the Pointin Time Rollback operation is aborted.

87Operational NotesNetBackup Snapshot Client

Note: For a rollback of a database backup such as Oracle, the file systemverification is mandatory and this issue prevents a successful rollback.

For a rollback of a file system, you can skip file verification by selecting "Skipverification and force rollback" on the restore dialog. The problem that isdescribed here is avoided and the rollback succeeds.

Caution:Use Skipverificationandforcerollback only if you are sure that youwant to replace all the files in the original locationwith the snapshot. Rollbackdeletes all files that were created after the creation-date of the snapshot thatyou restore.

See "InstantRecovery: point in time rollback" in theNetBackupSnapshotClientAdministrator's Guide for more information on rollback.

NetBackup commands and utilitiesThis release ofNetBackup containsnewcommands andutilities. For a descriptionof each of the following commands, refer to the NetBackup Commands guide:

■ NBCC

See “About NetBackup support utilities” on page 18.

■ NBCCR

See “About NetBackup support utilities” on page 18.

■ bpclimagelist

This command produces a status report on NetBackup client images orremovable media.

■ bpclusterutil

You can use this command to modify and configure a NetBackup cluster.

■ nbcplogs

You can use this command to copy all NetBackup logs to a designateddestination.

■ nbkmsutil

This command runs the NetBackup Key Management Service utility.

■ nbregopsc

You use this command to register OpsCenter.

■ bptestnetconn

Operational NotesNetBackup commands and utilities

88

This command test and analyzes various NetBackup configurations andconnections.

The support and support.exe diagnostic information gathering utilities are nolonger included or supported beginning with this release of NetBackup.

NetBackup OpenStorage OptionThe following list contains the operational note information that pertains toNetBackup OpenStorage option:

■ TheNetBackupOpenStorageOptions doesnot support clustering of themediaservers that function as data movers.

■ NetBackup performs optimized duplication until it encounters an image forwhich optimizedduplication is not possible. For that image and all subsequentimages, NetBackup performs a regular duplication.

■ NetBackup uses the fragment size setting of the source storage unit, not thesetting of the destination storage unit. NetBackup copies the image fragmentsas is (that is, NetBackup does not resize or rearrange the backup image into adifferent set of fragments).

■ Beginning with release 7.0, NetBackup binaries are compiled in 64-bit.Therefore, NetBackup requires OpenStorage vendor plug-ins to be 64-bit.When you upgrade a media server that is used for OpenStorage to NetBackup7.0, you also must update the vendor plug-in to a 64-bit version.

NetBackup Disk Storage unitsThe following list contains the operational information that pertains to the Diskstorage unit:

■ Upon NetBackup installation or upgrade, the nb_updatedssu command runs.The command deletes the .ds files that were used in the previous releases aspointers to the relocated data. Relocated data is tracked differently in thecurrent release and the .ds files, are converted to thenew trackingmechanism.Under some circumstances, a .ds file may not be deleted upon installation orupgrade. If that occurs, Symantec recommends that you run the commandagain to ensure that all .ds files are removed:

install_path\netbackup\bin\admincmd\nb_updatedssu

/usr/openv/netbackup/bin/admincmd/nb_updatedssu

Note, if you have any written scripts that make use of the .ds files to computethe amount of "potential free space" on a volume, you now need to use a

89Operational NotesNetBackup OpenStorage Option

different command. You can use the following command, to display thepotential free space for the volume.nbdevquery -listdv -D -stype BasicDisk -dp disk_volume_name

■ If you create a BasicDisk storage unit on a media server that is older than 7.0,then the properties of the BasicDisk STU do not appear in the storage unitdialog that is shown in the 7.0 user interface. A pop-up window appears andcontains the following message:CORBA::BAD Param.

NetBackup VaultThe following list contains the operational notes that pertain toNetBackupVault:

■ Enhancements have been made that enables a nonroot NBU_Admin or Vaultoperator to perform the tasks that they otherwisewould not be able to performbecause of permission problems. These enhancements specifically target asystemwhereNBAC is configured and theVault servicemanages the importantread-write data. For example, these enhancements have the following effecton users who have upgraded from previous versions to NetBackup 7.0:

■ If pre-NetBackup 7.0 sessions are not processed completely before anupgrade, Symantec recommends that you process all these sessions(meaning that you complete all ejects and reports) before you upgrade toensure minimal affect. At a minimum, you should copy the summary.logfrom the sidxxxdirectory to a new sidxxx/logsdirectory to accommodateeject/reports eligible sessions.

■ The presence of the VLT_CREATE_SESSION_DEBUG_FILES touch file hasno affect on the new session permissions.

■ The permissions of pre-NetBackup 7.0 session directories are notmodified.

■ You may need to update the notify scripts appropriately with respect tothe directory structure changes. For example, the summary.log is nowwritten to sidxxx/logs directory.

■ If you upgrade to NetBackup 7.0 and decide to downgrade to apre-NetBackup 7.0 version, you must make sure that you account for theenhancements that were packaged inNetBackup 7.0. For example, log filesare written to sidxxx/logs, and files and folders have restrictivepermissions when they are created.

■ Vault Operator Access on UNIX.If you donot configureNetBackupAccess Control, you can still set permissionson UNIX systems so that non-root users can use the operational commands

Operational NotesNetBackup Vault

90

in the Vault OperatorMenu to inject and eject tapes and generate reports. Themost efficient way to accomplish that is to add the users to whom you wantto grant access to a single user group, then give that group permission toexecute some of the executable files.Giving users access to the Vault OperatorMenu also gives them the capabilityto change report destinations. If youdonotwant non-root users to view reportsand change report destinations, do not give them access to the Vault OperatorMenu. For example, you may not want non-root users to see the RecoveryReport or to be able to change to whom reports are e-mailed.

In addition, giving users special privileges may violate your organization’scomputer andnetwork securitypolicies andallowaccess toprivate information.Check with your system administration or computer security staff to ensurethat you do not violate security policies.

■ Create a UNIX group and add the appropriate users to this group. Thisgroup is referred to as opsgroup in the following commands.

■ Log on to the system on which the NetBackup master server is installedand execute the following commands as root:

# cd /usr/openv/volmgr/bin

# chgrp opsgroup vmchange vmquery vmupdate

# chmod 4550 vmchange vmquery vmupdate

# cd /usr/openv/netbackup/bin

# chgrp opsgroup vltrun

# chmod 4550 vltrun

# cd /usr/openv/netbackup/bin/admincmd

# chgrp opsgroup bpimagelist bpimmedia bpmedia

bpmedialist

# chmod 4550 bpimagelist bpimmedia bpmedia bpmedialist

■ Log on to all systems on which NetBackup media servers are installed thatcontrol a robot and execute the following commands as root:

# cd /usr/openv/volmgr/bin

# chgrp opsgroup vmchange vmquery vmupdate

# chmod 4550 vmchange vmquery vmupdate

■ If you use Sun StorageTek ACSLS for robotic control, log on to that serverand modify the .rhosts file in the home directory of user acsss. TheNetBackup installation process should have added an entry to the .rhostsfile for the NetBackup master server that grants root access. Modify thatentry to allow all users in the opsgroup access to the SunStorageTekACSLSserver as user acsss:

91Operational NotesNetBackup Vault

master_server_name root <user1> <user2> . . . <userx>

■ If you use Sun StorageTek ACSLS for robotic control, verify that the useraccounts defined for the operations group exist on both the system onwhich the NetBackup master server is installed and on which the SunStorageTekACSLS server is installed. For simplicity, each user should havethe sameuser ID on both servers. If both servers use a naming service (suchas NIS), you can skip this step.

To verify the proper operation, log on as a non-root user on the NetBackupmaster server system. Start vltopmenu and execute each menu option.

NetBackup for VMwareThe following operational notes pertain to NetBackup's VMware feature:

■ VMware with PureDisk deduplicationFor a VMware backup to a PureDisk Deduplication Embedded (PDDE) storageunit, select theMappedfullVMbackupoption for theVirtualmachinebackupparameter on the VMware snapshot method. This option provides the bestdeduplication rates. Use of the Full VM backup option results in a lower rateof deduplication.

■ The Mapped fullVMbackup option does not work with the hotadd transporttype if the virtual machine that contains the backup host is a clone of thevirtual machine that is backed up (or vice versa).If the VMware backup host is in a virtual machine, and that virtual machineis a clone of the virtual machine that you backed up, a backup that uses thehotadd transfer type may appear to succeed. However, some of the virtualmachine volumes may be incorrectly mapped and cannot be restored. Theconverse is also true. The virtual machine that you back up with the hotaddtransport type cannot be a clone of the virtual machine that contains thebackup host. Furthermore, the two virtual machinesmust not be clones of thesame parent.VMware has identified this issue as software defect SR#1442259141.If youwant to use thehotadd transport typewith your backup, do the following.Make sure the virtual machine that contains the VMware backup host and thevirtual machine you back up are not clones of each other.

■ NetBackup for VMware does not support backing up virtual machine RAID 5volumes with the SAN transfer type.If a virtual machine containing a RAID 5 volume was backed up with VMwarevStorage services (not VCB) using the SAN transfer type, the RAID 5 volumemay not be correctly restored.

Operational NotesNetBackup for VMware

92

This issue will be addressed in a future release of VMware and NetBackup.

■ If a virtual machine with multiple network interfaces is restored to an ESXserver thathas fewernetwork interfaces, someof thevirtualmachine's networkinterfaces are not restored. This issue occurs when NetBackup 7.0 performsa restore with the VMware vStorage infrastructure services. This issue will beaddressed in a future release of NetBackup.As a workaround, you can configure additional network interfaces on thedestination ESX server before you run the restore.Make sure that the networkconnections are correctly identified and selected on the NetBackup "networkconnections "Restore dialog. That ensures all of the virtualmachine's originalnetwork adapters are restored when the virtual machine is restored.

■ VMware virtual machine does not reboot after restoreIf a virtual machine was configured with SCSI and IDE drives at the time ofbackup, and the guest OS resided on a SCSI drive, the virtual machine whenrestoredmay attempt to boot from the IDE drive. In that case, the boot attemptfails with the message "Operating system not found." This problem occurswhenNetBackup uses theVMware vStorage integration services. VMware hasidentified this problem and will address it in a future release.As aworkaround, you can reconfigure the BIOS on the virtualmachine to bootfrom the correct SCSI disk.

■ The restore of a virtualmachine failswhenyouuse thehotadd transportmodeif the VMware backup host is on a Windows 2008 virtual machine.Because of a VMware issue (SR#1438908741), restoring the virtual machinebymeans of the hotadd transfer typemay fail if youhave installed theVMwarebackup host in a virtual machine in a Windows Server 2008 guest operatingsystem. The detailed status log on the NetBackup Activity Monitor includesthe message, Virtual machine restore: file write failed. The final jobstatus code is 5, the restore failed to recover the requested files.

Until this issue is fixed, the backup host must be in a Windows 2003 virtualmachine to use the hotadd transfer type for the restore. If the backup host isin aWindows2008virtualmachine, use the nbd transfer type instead of hotadd.

■ You can use a proxy client for VMWare Consolidated backups (VCB). However,any drives that you specify to be excluded from the proxy client are alsoexcluded from the virtual machines. To avoid this issue, make sure that youdo not exclude drives on proxy clients when you perform a VCB backup.

■ Restoring a virtualmachine through a vCenter Servermaybe slowwhenusingthe SAN transfer typeWhen you use the SAN transfer type to restore a virtual machine, the restorejob may be slow if you restore to a vCenter Server. To speed up the restore,restore the virtual machine directly to an ESX server.

93Operational NotesNetBackup for VMware

■ When theNetBackup-JavaAdministrationConsole is used to restore aVMwarevirtual machine that was backed up with the block level incremental backupfeature (BLIB), only the most recent BLIB backup of that virtual machine canbe restored. If you try to restore an earlier backupmade from the same policy,the restore fails.To restore fromprevious BLIB backups of the virtualmachine, use theBackup,Archive, and Restore interface on Windows.

Operational NotesNetBackup for VMware

94

End of Life Notifications


■ End of life notifications

■ About features, enhancements, and commands no longer supported

End of life notificationsThis section contains information about the features, platforms, and devices thatwill no longer be supported in future releases of NetBackup. These notificationsencompass NetBackup commands, files, directories, utilities, tools, robots anddevices, and terminology.

About general NetBackup notificationsThe following is a list of general NetBackup end-of-life notifications that affectfuture releases of NetBackup:

■ In the nextmajor release after 7.0, support for all of the active and the passivemedia server clusters that use the NetBackup clustering agents is withdrawn.

■ The NAS SnapVault Option is not offered for sale with new NetBackup 7.0environments.However, it continues to be a supported optionwithNetBackup6.5 license keys for the remaining support life of 6.5. If you are a current NASSnapVault Option user and intend to upgrade to NetBackup 7.0, you cancontinue to use the NAS SnapVault Option and the following applies:

■ SnapVault can no longer be purchased and you cannot enable it with theNetBackup 7.0 license keys.

■ To continue to use SnapVault on 7.0, you must use your NetBackup 6.5license keys that enable SnapVault. The NetBackup 6.5 SKU for the NAS

5Chapter

SnapVault Option is available for one year after NetBackup 7.0 is released.That enables you to purchase licenses to support additional capacity.

■ Starting with the next major release of NetBackup, the NetBackup-JavaAdministration Console is no longer supported.

■ Backup Exec Tape Reader (BETR) refers to the ability within NetBackup toimport and restore fromBackup Exec (BE) backup sets (images). As of the nextmajor release, NetBackup, BETR is no longer supported.

■ At the next major release of NetBackup, the NetWare client is no longersupported.

About features, enhancements, and commands nolonger supported

Changes to how Symantec supports NetBackup features may directly affect you.Symantec is committed tonotifying youof these changes at least onemajor releasebefore support is discontinued. In some instances, notification was alreadyannounced and this document confirms that support has been removed.

The following sections describe those features, enhancements, or commands thatareno longer supported as of this release ofNetBackup. Itemswithin these sectionswere previously announced in earlier releases of NetBackup providing a warningto users that specific changes were forthcoming.

About general NetBackup features no longer supportedThe following list contains general NetBackup features that are no longersupported:

■ NetBackup no longer supports the Veritas Storage Migrator (VSM) product.Veritas Storage Migrator (VSM) 6.5 is the final release of the product and isnot supported in NetBackup 7.0. However, VSM is supported for the life ofNetBackup 6.5 and all of the NetBackup 6.5 release updates. That means thatonly NetBackup 6.5 GA and 6.5.x media servers support VSM media and thisversion ofNetBackupVaultmanages thosemedia. Startingwith thenextmajorrelease of NetBackup, NetBackup Vault no longer supports VSM media ejectand report functionality.

■ FAT file systems are not supported forWindows server (x86 and x64) systems.

■ The SharedDisk option is not supported beginning with the NetBackup 7.0release.You can use a NetBackup 7.0master server to configure, manage, and operateSharedDisk on NetBackup 6.5 media servers.

End of Life NotificationsAbout features, enhancements, and commands no longer supported

96

For information about using SharedDisk, see the documentation for yourNetBackup 6.5 release.

■ NetBackup no longer supports the NetWare Media Server Option.

■ The set_ndmp_attr file no longer exists in NetBackup. Starting with thisrelease of NetBackup, the functionality that is found in set_ndmp_attr onlyexists in tpconfig.

■ TheVERITASSnapshot Provider (VSP), for open and active files onNetBackuppre-7.0 Windows clients, is no longer supported in NetBackup 7.0.

Note: For 7.0 clients, NetBackup automatically uses VSS instead of VSP.

■ Beginningwith this release, you canno longer use the "cold" ("offline") catalogbackup method. This backup method was deprecated from NetBackup and isno longer be supported.

■ The Snapshot Client does not support Storage Foundation 3.x versions withthe exception of the OnlineJFS version 3.5MP1 on an HP-UX 11.11 system.

■ Symantec no longer provides the Windows tape device Installer or WindowsTape Drivers.

■ Cold Catalog Backup has been dropped from NetBackup 7.0.

■ Starting with this release of NetBackup, the NetBackup binaries for AIX,HP9000PA-RISC, Solaris SPARC, andLinux x86 systems arenowbuilt as 64-bitbinaries only.If you have a computer that can run a 32- or 64-bit operating system, and youstart the computer in 64-bit mode, NetBackup installs and runs as designed.If you run the computer in 32-bit mode only, then NetBackup 7.0 does notinstall.

■ The NetBackup Operations Manager (NOM) product has been replaced withthe new OpsCenter feature.

■ Starting with this release, NetBackup has merged two help sets into one. Thatmeans that the jnbSA help set has been eliminated and the jbpSA help setremains.

■ NetBackup 7.0 does not support SGI IRIX and Tru64 platforms.

About database functions no longer supportedThe following describes the functionality within the NetBackup database agentsthat are no longer supported, beginning with this release of NetBackup:

97End of Life NotificationsAbout features, enhancements, and commands no longer supported

■ NetBackup for Microsoft SharePoint Portal NotificationsNetBackup 7.0 no longer supports SharePoint Portal Server 2001 backup andrecovery.

■ NetBackup for Microsoft SQL NotificationsNetBackup no longer supports SQL Server 7.0 backup and recovery.

■ NetBackup for Microsoft Exchange ServerNetBackup 7.0 no longer supports Exchange 5.5 or Exchange 2000 backup andrecovery.

About NetBackup commands no longer supportedThe commands in the following list are no longer supported with this release ofNetBackup:

■ bpmoverinfo

■ nbnos

■ bpSALinfo

■ nbpushdata

■ nbshareddisk

■ tshd

■ odld

■ set_ndmp_attr

■ tpformat

■ bpuser

■ bpauthsync

■ Enhanced Authentication (noauth authentication methods) and EnhancedAuthorization are no longer supported.

■ The last release of the FSAnalyzer was NetBackup 6.5. The FSAnalyzer is nolonger supported in this release of NetBackup.

■ The diagnostic information gathering utilities and programs, support,andsupport.exe, are no longer supported as of this release of NetBackup. Anew utility, nbsu, introduced in NetBackup 6.5 replaced these utilities.

End of Life NotificationsAbout features, enhancements, and commands no longer supported

98

Related Documents


■ About related NetBackup documents

■ About NetBackup release notes

■ About getting started guides

■ About installation guides

■ About administrator’s guides - agents and options

■ About user’s guides

■ About the device configuration guide

■ About the Troubleshooting guide

■ About NetBackup command documents

About related NetBackup documentsThis topic lists and describes the technical manuals that relate to NetBackup.

The DVD-ROM for each NetBackup product has a copy of the related manuals inAdobe Portable Document Format (PDF). The PDF files are either in the rootdirectory or the Doc directory on the disk.

To view the PDF copies of the manuals, you need an Adobe Acrobat reader. Youcan download a copy of this product from the Adobe Web site at the followingURL:

http://www.adobe.com

Symantec assumes no responsibility for the correct installation or use of thereader.

6Chapter

http://www.adobe.com

About NetBackup release notesThe following release notes documents were released with this version ofNetBackup.

■ Symantec NetBackup Release Notes for UNIX, Linux, andWindowsNetBackup_Release_Notes.pdfThis document contains information about NetBackup on UNIX- andWindows-based servers, such as the platforms and operating systems that aresupported. It also contains any operating notes that may not be in theNetBackup manuals or the online Help .

About getting started guidesThe following getting started guideswere releasedwith this version ofNetBackup.

■ Symantec NetBackup Getting Started Guide for UNIX, Linux, andWindowsNetBackup_GettingStarted_Guide.pdfProvides ahigh-level descriptionof the latestNetBackup release.This documentalso contains the information that explains the content of theNetBackupmediakit.

■ Symantec NetBackup Backup, Archive, and Restore Getting Started GuideNetBackup_BAR_GS_Guide.pdfExplains how to use the NetBackup Backup, Archive, and Restore interface toperformbackupand restore operations forUNIX,Windows, andLinux systems.

About installation guidesThe following Installationdocumentswere releasedwith this versionofNetBackup.

■ Symantec NetBackup Installation Guide for UNIXNetBackup_Install_UNIX.pdfExplains how to install NetBackup software on UNIX-based platforms.

■ Symantec NetBackup Installation Guide for WindowsNetBackup_Install_Win.pdfExplains how to install NetBackup software on Windows-based platforms.

■ Symantec NetBackup LiveUpdate GuideNetBackup_LiveUpdate_Guide.pdfThis guide explains a feature that provides a cross-platform, policy-drivenmethod to distributeNetBackupReleaseUpdates toNetBackuphosts at version6.5 and later.

Related DocumentsAbout NetBackup release notes

100

About administrator’s guides - agents and optionsThe following administrator guides for NetBackup database agents and optionswere released with this version of NetBackup.

■ Symantec NetBackup Deduplication GuideNetBackup_Dedupe_Guide.pdfExplains how to configure and useNetBackupmedia server deduplication andNetBackup client deduplication.

■ Symantec NetBackup SAN Client and Fibre Transport GuideNetBackup_SANClient_Guide.pdfExplains how to configure and useNetBackup SANClient and Fibre Transportfor high-speed backups of important clients.

■ Symantec NetBackup Shared Storage GuideNetBackup_SharedStorage_Guide.pdfExplainshow to configure anduse shared storage inNetBackup. Shared storageincludes AdvancedDisk, OpenStorage, and the Shared Storage Option.

■ Symantec OpsCenter Administrator's GuideNetBackup_AdminGuide_OpsCenter.pdfExplains the Web-based software application that helps organizations. Itprovides visibility into their data protection environment. OpsCenter is acombination of the two Symantec products namely NetBackup OperationsManager (NOM) 6.5.4 and Veritas Backup Reporter (VBR) 6.6.

■ SymantecNetBackupEnterpriseVaultAgentAdministrator'sGuide forWindowsNetBackup_AdminGuide_EntVault.pdfExplains how to install, configure, and use the Enterprise Vault Agent so youcanprotectEnterpriseVault configuration informationanddata thatEnterpriseVault has archived.

■ Symantec NetBackup Snapshot Client Administrator’s GuideNetBackup_AdminGuide_SnapshotClient.pdfThis guide explains how to install, configure, and use Symantec NetBackupSnapshot Client. It combines the features of snapshot backup, FlashBackup,BLI Agent, off-host backup , and Instant Recovery.

■ Symantec NetBackup Snapshot Client Quick Start GuideNetBackup_QuickStart_SnapshotClient.pdfProvides the first-time instructions for installing and configuring theSnapshotClient.

■ Symantec NetBackup for Hyper-V Guide for UNIX, Windows, and LinuxNetBackup_AdminGuide_Hyper-V.pdf

101Related DocumentsAbout administrator’s guides - agents and options

NetBackup forHyper-Vprovides snapshot-basedbackupof thevirtualmachinesthat run on Windows 2008 Hyper-V servers.

■ Symantec NetBackup for VMware Administrator's Guide for UNIX, Windows,and LinuxNetBackup_AdminGuide_VMware.pdfProvides backup and restore of the VMware virtual machines that run onVMware ESX servers.

■ Symantec NetBackup for DB2 Administrator’s Guide for UNIXNetBackup_AdminGuide_DB2_Unix.pdfExplains how to install, configure, and use NetBackup for DB2.

■ Symantec NetBackup for DB2 Administrator’s Guide for WindowsNetBackup_AdminGuide_DB2_Win.pdfExplains how to install, configure, and use NetBackup for DB2.

■ Symantec NetBackup for Informix Administrator’s GuideNetBackup_AdminGuide_Informix.pdfExplains how to install, configure, and use NetBackup for Informix to back upand restore the Informix databases that are on a UNIX NetBackup client.

■ Symantec NetBackup for Lotus Notes Administrator’s Guide for WindowsNetBackup_AdminGuide_LotusNotes_Win.pdfExplains how to install, configure, and use NetBackup for Lotus Notes to backup and restore LotusNotes databases and transaction logs on aWindows client.

■ Symantec NetBackup for Lotus Notes Administrator’s Guide for UNIXNetBackup_AdminGuide_LotusNotes_Unix.pdfExplains how to install, configure, and use NetBackup for Lotus Notes to backup and restore Lotus Notes databases and transaction logs on a UNIX client.

■ Symantec NetBackup for Microsoft Exchange Server Administrator’s GuideNetBackup_AdminGuide_MSExchg_Win.pdfExplains how to configure and use NetBackup for Microsoft Exchange Serverto perform online backups and restores of Microsoft Exchange Server.

■ Symantec NetBackup for Microsoft SQL Server Administrator’s Guide forWindowsNetBackup_AdminGuide_MSSQL_Win.pdfExplains how to install, configure, anduseNetBackup forMicrosoft SQLServerto back up and restore Microsoft SQL Server databases and transaction logs.

■ Symantec NetBackup for NDMP Administrator’s GuideNetBackup_AdminGuide_NDMP.pdfExplains how to install, configure, and use NetBackup for NDMP to controlbackups on an NDMP host.

Related DocumentsAbout administrator’s guides - agents and options

102

■ Symantec NetBackup for Oracle Administrator’s Guide for UNIXNetBackup_AdminGuide_Oracle_Unix.pdfExplains how to install, configure, and use NetBackup for Oracle to back upand restore the Oracle databases that are on a UNIX NetBackup client.

■ Symantec NetBackup for Oracle Administrator’s Guide for WindowsNetBackup_AdminGuide_Oracle_Win.pdfExplains how to install, configure, and use NetBackup for Microsoft Oracle toback up and restore the Oracle databases that are on a Windows NetBackupClient.

■ Symantec NetBackup for SAP Administrator’s Guide for UNIXNetBackup_AdminGuide_SAP_Unix.pdfExplains how to install, configure, and use NetBackup for SAP on UNIX.

■ Symantec NetBackup for SAP Administrator’s Guide for WindowsNetBackup_AdminGuide_SAP_Win.pdfExplains how to install, configure, and use NetBackup for SAP onWindows-based servers.

■ Symantec NetBackup™ for Microsoft SharePoint Server Administrator’s Guidefor WindowsNetBackup_AdminGuide_SharePoint.pdfExplains how to install, configure, and use NetBackup for SharePoint PortalServer 2003 to back up and restore the Sybase databases that are on aWindowsNetBackup client.

■ Symantec NetBackup for SYBASE Administrator’s Guide for UNIXNetBackup_AdminGuide_Sybase_Unix.pdfExplains how to install, configure, and use NetBackup for Sybase to back upand restore Sybase databases that are on a UNIX NetBackup client.

■ Symantec NetBackup for SYBASE Administrator’s Guide onWindowsNetBackup_AdminGuide_Sybase_Win.pdfExplains how to install, configure, and use NetBackup for Sybase to back upand restore Sybase databases that are on a Windows NetBackup client.

■ Symantec NetBackup High Availability Administrator’s GuideNetBackup_AdminGuide_HighAvailability.pdfThis guide provides information on how to install and configure NetBackupto work with different clustering solutions.

■ Symantec NetBackup Bare Metal Restore Administrator's GuideNetBackup_AdminGuide_BMR.pdfDescribes how to install, configure, and use Bare Metal Restore to protect andrestore client systems. For UNIX, Windows, and Linux.

103Related DocumentsAbout administrator’s guides - agents and options

■ Symantec NetBackup Vault Administrator's GuideNetBackup_AdminGuide_Vault.pdfDescribes how to install, configure, and use logical vaults and profiles toduplicate backups, performcatalog backups, ejectmedia, and generate reports.For UNIX, Windows, and Linux.

■ Symantec NetBackupNetWareMedia Server Option Administrator’s Guide forUNIX andWindowsNetBackup_AdminGuide_NetWareServer.pdfThis comprehensive manual provides detailed information and proceduresfor installing, configuring, andusing the SymantecNetBackupNetWareMediaServer Option.

About user’s guidesThe following user guides were released with this version of NetBackup.

■ Symantec NetBackup Vault Operator's GuideNetBackup_OperGuide_Vault.pdfDescribes the procedures for sending tapes off site, receiving tapes on site,and running reports on off-sitemedia and vault jobs. ForUNIX,Windows, andLinux.

■ Symantec NetBackup Administrator's Guide for Novell NetWare ClientNetBackup_AdminGuide_NetWare_Client.pdfExplains how to install and use the NetBackup’s NetWare Client software.With the NetWare Client, full and incremental backups can be scheduled tooccur automatically andunattendedunder the control of theNetBackupmasterserver. The NetWare Client also provides two methods for performinguser-directed backups and restores: Target, which uses a character-based,menu-driven interface running on theNetWare server, andNonTarget, whichuses the NetBackup for NetWare NonTarget Browser that is installed and runfrom a Windows computer.

About the device configuration guideThe following device configuration guide was released with this version ofNetBackup.

■ Symantec NetBackup Device Configuration GuideNetBackup_DeviceConfig_Guide.pdfExplains how to add device drivers and perform other system-levelconfigurations for theoperating systemsofNetBackupservers thathost storage

Related DocumentsAbout user’s guides

104

devices. Also includes information about configuring several types of tapelibraries.

About the Troubleshooting guideThe following troubleshooting guidewas releasedwith this version ofNetBackup.

■ Symantec NetBackup Troubleshooting Guide for UNIX andWindowsNetBackup_Troubleshoot_Guide.pdfProvides troubleshooting information forUNIX-andWindows-basedNetBackupproducts, including Media Manager.

About NetBackup command documentsThe following commanddocumentswere releasedwith this version ofNetBackup.

■ Symantec NetBackup Commands for UNIX, Windows, and LinuxNetBackup_Commands.pdfDescribes the NetBackup and Media Manager commands and the processesthat you can run from aUNIX command line or aWindows command prompt.

105Related DocumentsAbout the Troubleshooting guide

Related DocumentsAbout NetBackup command documents

106

Windows Logo Certificationinformation

This appendix includes the following topics:

■ About Windows Server 2008 R2 Logo Certification

About Windows Server 2008 R2 Logo CertificationThis topic contains information aboutWindowsServer 2008R2LogoCertificationand how it applies to NetBackup. The tables contain the following types ofinformation:

■ Files that have invalid file version information (Company, Product Name, andProduct Version)See Table A-1 for a list of these files.

■ Third-party files and tools that do not include or create requestedExecutionLevel tagsSee Table A-2 for a list of these files and tools.

■ Files that NetBackup uses that are not signedSee Table A-3 for a list of these files.

■ Files that remain after an uninstallThe NetBackup uninstall may leave files behind that other Symantecapplications use. NetBackup 7.0 uses Veritas Authentication (VxAT) as acommon security infrastructure that is shared between applications on thesame host. For example, Veritas Storage Foundation (VxFS) and NetBackupcan reside on the same host.If you uninstall NetBackup from a Windows Server 2008 R2 host and removetheVxAT files in the commondirectory, then the remaining application ceases

AAppendix

to function. However, the following files remain in the Security folder(C:\Program Files\Veritas\Security\...) after the uninstall completes.

See Table A-4 for a list of files that remain after an uninstall has occurred.

Table A-1 NetBackup installs the following files that do not have valid fileversion information

File namesThird-party file locations

pxhpinst.exeThird-party files located in ProgramFiles\Veritas\NetBackup\bin

pxsetup.exe

vxblock.dll

diskLibPlugin.dllThird-party files located in of Program

Files\Common

Files\VERITAS\VxMS\shared\VDDK

gvmomi.dll

libcurl.dll

libeay32.dll

liblber.dll

libldap.dll

libldap_r.dll

libxml2.dll

ssleay32.dll

types.dll

zlib1.dll

_int.dllThird-party files located in any of the following paths:

■ Program Files\Veritas\pdde

■ Program Files\Veritas\pdde\pddb\bin

■ Program Files\Veritas\pdde\pddb\lib

adminpack.dll

ascii_and_mic.dll

Windows Logo Certification informationAbout Windows Server 2008 R2 Logo Certification

108

Table A-1 NetBackup installs the following files that do not have valid fileversion information (continued)


autoinc.dll

btree_gist.dll

chkpass.dll

cube.dll

cyrillic_and_mic.dll

dblink.dll

dict_int.dll

dict_snowball.dll

dict_xsyn.dll

earthdistance.dll

euc_cn_and_mic.dll

euc_jis_2004_and_shift_jis_2004.dll

euc_jp_and_sjis.dll

euc_kr_and_mic.dll

euc_tw_and_big5.dll

fuzzystrmatch.dll

hstore.dll

insert_username.dll

int_aggregate.dll

isn.dll

latin_and_mic.dll

latin2_and_win1250.dll

libecpg.dll

libecpg_compat.dll

109Windows Logo Certification informationAbout Windows Server 2008 R2 Logo Certification



libpgtypes.dll

libpq.dll

libxml2.dll

libxslt.dll

lo.dll

ltree.dll

moddatetime.dll

oid2name.exe

pageinspect.dll

pg_buffercache.dll

pg_freespacemap.dll

pg_regress.exe

pg_regress_ecpg.exe

pg_standby.exe

pg_trgm.dll

pgbench.exe

pgcrypto.dll

pgrowlocks.dll

pgstattuple.dll

pgxml.dll

plperl.dll

plpgsql.dll

plpython.dll

pltcl.dll


110



refint.dll

regress.dll

seg.dll

sslinfo.dll

tablefunc.dll

test_parser.dll

timetravel.dll

tsearch2.dll

utf8_and_ascii.dll

utf8_and_big5.dll

utf8_and_cyrillic.dll

utf8_and_euc_cn.dll

utf8_and_euc_jis_2004.dll

utf8_and_euc_jp.dll

utf8_and_euc_kr.dll

utf8_and_euc_tw.dll

utf8_and_gb18030.dll

utf8_and_gbk.dll

utf8_and_iso8859.dll

utf8_and_iso8859_1.dll

utf8_and_johab.dll

utf8_and_shift_jis_2004.dll

utf8_and_sjis.dll

utf8_and_uhc.dll




utf8_and_win.dll

uuid-ossp.dll

vacuumlo.exe

vacuumlo.exe

zlib1.dll

Table A-2 NetBackup uses the following third-party files and tools that do notinclude or create requested ExecutionLevel tags


java.exeThird-party files located in ProgramFiles\Veritas\NetBackupDB\java

javaw.exe

keytool.exe

policytool.exe

rmid.exe

rmiregistry.exe

tnameserv.exe

pxhpinst.exeThird-party files located in ProgramFiles\Veritas\NetBackup\bin

pxsetup.exe

uconv.exe

clusterdb.exeThird-party files located in any of the following paths:




createdb.exe


112

Table A-2 NetBackup uses the following third-party files and tools that do notinclude or create requested ExecutionLevel tags (continued)


createlang.exe

createuser.exe

createuser.exe

dropdb.exe

droplang.exe

dropuser.exe

ecpg.exe

initdb.exe

oid2name.exe

pg_config.exe

pg_controldata.exe

pg_ctl.exe

pg_dump.exe

pg_dumpall.exe

pg_regress.exe

pg_regress_ecpg.exe

pg_resetxlog.exe

pg_restore.exe

pg_standby.exe

pgbench.exe

postgres.exe

psql.exe

reindexdb.exe

vacuumdb.exe


Table A-2 NetBackup uses the following third-party files and tools that do notinclude or create requested ExecutionLevel tags (continued)


vacuumlo.exe

zic.exe

Table A-3 NetBackup uses and installs the following files that are not signed.


awt.dllThird-party files located in ProgramFiles\Veritas\NetBackupDB\java

cmm.dll

dcpr.dll

dt_socket.dll

fontmanager.dll

hpi.dll

hprof.dll

ioser12.dll

java.dll

java.exe

javaw.exe

jawt.dll

JdbcOdbc.dll

jdwp.dll

jpeg.dll

jsound.dll

keytool.exe

net.dll

policytool.exe


114

Table A-3 NetBackup uses and installs the following files that are not signed.(continued)


rmid.exe

rmiregistry.exe

tnameserv.exe

verify.dll

zip.dll

mfc*.dllThe following Microsoft runtime libraries

msvc*.dll

PrimoSDK.dllThird-party files located in ProgramFiles\Veritas\NetBackup\bin\x86

px.dll

pxdrv.dll

pxhpinst.exe

pxmas.dll

pxsetup.exe

pxwave.dll

vxblock.dll

diskLibPlugin.dllThird-party files located in ProgramFiles\Veritas\NetBackup\bin

glib-2.0.dll

gobject-2.0.dll

gthread-2.0.dll

gvmomi.dll

iconv.dll

intl.dll




libcurl.dll

libeay32.dll

liblber.dll

libldap.dll

libldap_r.dll

libxml2.dll

ssleay32.dll

types.dll

vixDiskLib.dll

vixDiskLibVim.dll

vixMntapi.dll

vmacore.dll

vmomi.dll

zlib1.dll

_int.dllThird-party files located in any of the following paths:




adminpack.dll

ascii_and_mic.dll

autoinc.dll

btree_gist.dll

chkpass.dll

clusterdb.exe

comerr32.dll


116



createdb.exe

createlang.exe

createuser.exe

createuser.exe

cube.dll

cyrillic_and_mic.dll

dblink.dll

dict_int.dll

dict_snowball.dll

dict_xsyn.dll

dropdb.exeS

droplang.exe

dropuser.exe

earthdistance.dll

ecpg.exe

euc_cn_and_mic.dll

euc_jis_2004_and_shift_jis_2004.dll

euc_jp_and_sjis.dll

euc_kr_and_mic.dll

euc_tw_and_big5.dll

fuzzystrmatch.dll

gssapi32.dll

hstore.dll

iconv.dll




initdb.exe

insert_username.dll

int_aggregate.dll

isn.dll

k5sprt32.dll

krb5_32.dll

latin_and_mic.dll

latin2_and_win1250.dll

libeay32.dll

libecpg.dll

libecpg_compat.dll

libiconv-2.dll

libintl-8.dll

libpgtypes.dll

libpq.dll

libxml2.dll

libxslt.dll

lo.dll

ltree.dll

moddatetime.dll

oid2name.exe

pageinspect.dll

pg_buffercache.dll

pg_config.exe


118



pg_controldata.exe

pg_ctl.exe

pg_dump.exe

pg_dumpall.exe

pg_freespacemap.dll

pg_regress.exe

pg_regress_ecpg.exe

pg_resetxlog.exe

pg_restore.exe

pg_standby.exe

pg_trgm.dll

pgbench.exe

pgcrypto.dll

pgevent.dll

pgrowlocks.dll

pgstattuple.dll

pgxml.dll

plperl.dll

plpgsql.dll

plpython.dll

pltcl.dll

postgres.exe

psql.exe

refint.dll




regress.dll

reindexdb.exe

seg.dll

ssleay32.dll

sslinfo.dll

tablefunc.dll

test_parser.dll

timetravel.dll

tsearch2.dll

utf8_and_ascii.dll

utf8_and_big5.dll

utf8_and_cyrillic.dll

utf8_and_euc_cn.dll

utf8_and_euc_jis_2004.dll

utf8_and_euc_jp.dll

utf8_and_euc_kr.dll

utf8_and_euc_tw.dll

utf8_and_gb18030.dll

utf8_and_gbk.dll

utf8_and_iso8859.dll

utf8_and_iso8859_1.dll

utf8_and_johab.dll

utf8_and_shift_jis_2004.dll

utf8_and_sjis.dll


120



utf8_and_uhc.dll

utf8_and_win.dll

uuid-ossp.dll

vacuumdb.exe

vacuumlo.exe

zic.exe

zlib1.dll

Table A-4 Files that remain after NetBackup is uninstalled

FilesFile locations

AuthenticationC:\Program Files\Veritas\Security\

SessionStore.lockC:\Program

Files\Veritas\Security\systemprofile\

VRTSatlocal.conf

CRTSatlocal.conf.lock

CertStore.lockC:\Program

Files\Veritas\Security\systemprofile\certstore\

KeyStore.lockC:\Program

Files\Veritas\Security\systemprofile\certstore\keystore\

SessionEncrKey.pem

SessionHMACKey.pem

default.dbC:\Program

Files\Veritas\Security\systemprofile\sessions\

log.0000000001

sdefault.db

__db.001


Table A-4 Files that remain after NetBackup is uninstalled (continued)

FilesFile locations

__db.002

__db.003

__db.004

__db.005

__db.006

__db.register

CertStore.lockC:\Program

Files\Veritas\Security\systemprofile\systruststore\


122