NetBackup Release Notes 1-1

Symantec NetBackup Release Notes
UNIX, Windows, and Linux
NetBackup 7.0
20654069
Symantec NetBackup Release Notes

The software described in this book is furnished under a license agreement and may be used only in accordance with the terms of the agreement. Documentation version: 7.0 PN: 20654069
Legal Notice
Copyright 2009 Symantec Corporation. All rights reserved. Symantec, the Symantec Logo, Veritas and NetBackup are trademarks or registered trademarks of Symantec Corporation or its affiliates in the U.S. and other countries. Other names may be trademarks of their respective owners. This Symantec product may contain third party software for which Symantec is required to provide attribution to the third party (Third Party Programs). Some of the Third Party Programs are available under open source or free software licenses. The License Agreement accompanying the Software does not alter any rights or obligations you may have under those open source or free software licenses. Please see the Third Party Legal Notice Appendix to this Documentation or TPIP ReadMe File accompanying this Symantec product for more information 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 document may be reproduced in any form by any means without prior written authorization of Symantec Corporation and its licensors, if any. THE DOCUMENTATION IS PROVIDED "AS IS" AND ALL EXPRESS OR IMPLIED CONDITIONS, REPRESENTATIONS AND WARRANTIES, INCLUDING ANY IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR NON-INFRINGEMENT, ARE DISCLAIMED, EXCEPT TO THE EXTENT THAT SUCH DISCLAIMERS ARE HELD TO BE LEGALLY INVALID. SYMANTEC CORPORATION SHALL NOT BE LIABLE FOR INCIDENTAL OR CONSEQUENTIAL DAMAGES IN CONNECTION WITH THE FURNISHING, PERFORMANCE, OR USE OF THIS DOCUMENTATION. THE INFORMATION CONTAINED IN THIS DOCUMENTATION IS SUBJECT TO CHANGE WITHOUT NOTICE. The Licensed Software and Documentation are deemed to be commercial computer software as defined in FAR 12.212 and subject to restricted rights as defined in FAR Section 52.227-19 "Commercial Computer Software - Restricted Rights" and DFARS 227.7202, "Rights in Commercial Computer Software or Commercial Computer Software Documentation", as applicable, and any successor regulations. Any use, modification, reproduction release, performance, display or disclosure of the Licensed Software and Documentation by the U.S. Government shall be solely in accordance with the terms of this Agreement.
Symantec Corporation 350 Ellis Street Mountain View, CA 94043 http://www.symantec.com Printed in the United States of America. 10 9 8 7 6 5 4 3 2 1
Technical Support
Symantec Technical Support maintains support centers globally. Technical Supports primary role is to respond to specific queries about product features and functionality. The Technical Support group also creates content for our online Knowledge Base. The Technical Support group works collaboratively with the other functional areas within Symantec to answer your questions in a timely fashion. For example, the Technical Support group works with Product Engineering and Symantec Security Response to provide alerting services and virus definition updates. Symantecs maintenance offerings include the following:
A range of support options that give you the flexibility to select the right amount of service for any size organization Telephone and Web-based support that provides rapid response and up-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 Symantecs Maintenance Programs, you can visit our Web site at the following URL: www.symantec.com/techsupp/
Contacting Technical Support

Customers with a current maintenance agreement may access Technical Support information at the following URL: www.symantec.com/techsupp/ Before contacting Technical Support, make sure you have satisfied the system requirements that are listed in your product documentation. Also, you should be at the computer on which the problem occurred, in case it is necessary to replicate the problem. When you contact Technical Support, please have the following information available:

Product release level Hardware information Available memory, disk space, and NIC information Operating system
Version and patch level Network topology Router, gateway, and IP address information Problem description:

Error messages and log files Troubleshooting that was performed before contacting Symantec Recent software configuration changes and network changes
Licensing and registration

If your Symantec product requires registration or a license key, access our technical support Web page at the following URL: www.symantec.com/techsupp/
Customer service
Customer service information is available at the following URL: www.symantec.com/techsupp/ 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 resources

If you want to contact Symantec regarding an existing maintenance agreement, please contact the maintenance agreement administration team for your region as follows:
Asia-Pacific and Japan Europe, Middle-East, and Africa North America and Latin America customercare_apac@symantec.com semea@symantec.com supportsolutions@symantec.com
Additional enterprise services

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

....................................................................... 11 11 13 13 14 14 15 15 16 16 16 17 17 17 18 18 19 22 22
New features in NetBackup ............................................................ NetBackup deduplication ............................................................... About client deduplication ....................................................... About media server deduplication ............................................. About Symantec OpsCenter ............................................................ About Symantec OpsCenter Analytics .............................................. About NetBackup for VMware ........................................................ Guided Recovery .......................................................................... New database features and enhancements ........................................ Exchange 2010 support ........................................................... Windows 7/2008R2 client support ............................................. NetBackup for Enterprise Vault agent ........................................ NetBackup for Hyper-V agent ................................................... Improved SharePoint Granular Recovery .................................... 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 .................................
Chapter 2
Platform compatibility ....................................................... 23

About server and client platform compatibility .................................. About platform and operating system compatibility changes .......................................................................... About NetBackup Compatibility Lists ......................................... About the deduplication host platform compatibility .................... About platform life cycles ........................................................ About Operating systems no longer compatible as of NetBackup 7.0 and beyond ........................................................................... NetBackup binary sizes ................................................................. Platforms compatiblity with the NetBackup Administration Consoles for UNIX ............................................................................... 23 23 24 26 27 28 30 33
Contents
About NetBackup backward compatibility ......................................... 36
Chapter 3
Product Dependencies ....................................................... 39

Operating system patches and updates ............................................. 39 About VxFS and VxVM compatible versions ...................................... 45
Chapter 4
Operational Notes ............................................................... 49

Operational Notes in NetBackup ..................................................... NetBackup installation and start-up notes ........................................ NetBackup media and rebranding changes .................................. General installation and upgrade items ...................................... NetBackup LiveUpdate ............................................................ Secure push install ................................................................. NetBackup cluster .................................................................. NetBackup Documentation Notes .................................................... Internationalization and localization Notes ...................................... NetBackup Bare Metal Restore ........................................................ General NetBackup operational notes .............................................. NetBackup Access Control ............................................................. NetBackup database agents ............................................................ Lotus Notes agent .................................................................. NetBackup for Microsoft Exchange ............................................ NetBackup for Microsoft SharePoint .......................................... SQL server agent ................................................................... Sybase server agent ............................................................... About NetBackup Enterprise Vault Agent ................................... NetBackup Hyper-V ...................................................................... NetBackup interfaces .................................................................... NetBackup Administration Console for Windows ......................... NetBackup java interfaces ........................................................ Storage unit configuration ....................................................... About Symantec OpsCenter ............................................................ NetBackup media and device management ........................................ Media Sharing ....................................................................... Enterprise Media Manager ....................................................... 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) ............................................ NetBackup Snapshot Client ............................................................ 50 50 50 53 56 56 56 58 58 61 66 67 69 70 71 74 76 76 77 77 78 78 79 82 82 83 84 84 85 86 86 86 86 87 87
Contents
NetBackup commands and utilities .................................................. NetBackup OpenStorage Option ...................................................... NetBackup Disk Storage units ......................................................... NetBackup Vault .......................................................................... NetBackup for VMware .................................................................
89 90 91 91 93
Chapter 5
End of Life Notifications .................................................... 97

End of life notifications ................................................................. 97 About general NetBackup notifications ...................................... 97 About features, enhancements, and commands no longer supported ............................................................................. 98 About general NetBackup features no longer supported ................ 98 About database functions no longer supported ............................ 99 About NetBackup commands no longer supported ...................... 100
Chapter 6
Related Documents ........................................................... 101

About related NetBackup documents .............................................. About NetBackup release notes ..................................................... About getting started guides ......................................................... About installation guides ............................................................. About administrators guides - agents and options ............................ About users guides ..................................................................... About the device configuration guide ............................................. About the Troubleshooting guide .................................................. About NetBackup command documents .......................................... 101 102 102 102 103 106 106 107 107
Appendix A
Windows Logo Certification information ...................... 109

About Windows Server 2008 R2 Logo Certification ........................... 109
10
Contents
Chapter
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 NetBackup

Symantec NetBackup 7.0 contains many new features and enhancements that increase the scalability and functionality of NetBackup for its large enterprise customers. The following list highlights some of the major features that comprise NetBackup 7.0.
Integrated deduplication:
Client deduplication
12
New Features New features in NetBackup
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 agent Support all Enterprise Vault 8.0 databases using the Enterprise Vault Agent including the Fingerprint database, FSA Reporting database, and Auditing database Enterprise Vault 8.0 support for granular quiescence Enterprise Vault Migrator is now included with NetBackup Enhancements to the NetBackup for Hyper-V agent New file-level incremental backups Two types of off-host backup Hyper-V R2 and Cluster shared volumes (CSV) Flexible VM identification Improved SharePoint Granular Recovery
This release is compatible with the following new proliferations:
New Features NetBackup deduplication
13
HP-UX 11.31 IA BMR master server for NetBackup 7.0 BMR WINPE 2.1 Java user interface support on RHEL 5 systems
NetBackup Support Utility (nbsu) enhancements
NetBackup deduplication
NetBackup now provides integrated data deduplication within NetBackup. You do not have to use the separate PureDisk interface to deduplicate data. You use NetBackup interfaces to install, configure, and manage storage, servers, backups, and deduplication. Symantec packaged PureDisk into a modular engine, and NetBackup uses the PureDisk Deduplication Engine (PDDE) to deduplicate backup data. You can use NetBackup deduplication at 2 points in the backup process:
On a NetBackup client. The NetBackup client deduplicates its own data and then sends it directly to a storage server, bypassing media server processing. Because unique data segments only are transferred, this option reduces network load. See About client deduplication on page 13. On a media server. NetBackup clients send their backups to a NetBackup media server, which deduplicates the backup data. The media server writes the data to the storage and manages the deduplicated data. See About media server deduplication on page 14.
See the NetBackup Deduplication Guide.
About client deduplication

This feature permits the deduplication of data from the source (a NetBackup client). It allows only unique data segments to be moved across the LAN and stored upon the media servers embedded deduplicated storage. Benefits of client deduplication feature are:
Faster backups occur because only the new data or the file segments that occurred since the last backup is moved and stored Permits a real Incremental Forever approach Has less of an impact on the LAN Reduced backup windows Can be combined with Application agents
14
New Features About Symantec OpsCenter
Supported over all Tier 1 NetBackup clients (for example, Windows, Linux, HP-UX, Solaris, and AIX) Backup policy integrated
About media server deduplication

This feature enables the deduplication of streaming data on the media server and has it stored upon the media servers embedded deduplicated storage. Benefits of media server deduplication:
A more simplified installation and configuration. The deduplication software is installed together with the media server software Optimized deduplication for a number of application backup agents Usage of commodity disk for deduplication
About Symantec OpsCenter

Symantec may supply additional information for this feature after it has been released for general availability. The following Technote on the Symantec Support Web 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 VBR Single deployment configuration and user interface for monitoring, alerting, and reporting functionality previously available in NOM and VBR. Improved ease-of-use Symantec corporate user interface (UI) standards for enterprise products. This enhancement offers simplified navigation, improved task efficiency, and a professional look and feel. In addition, a restructured standard report has been added that supports single-click execution along with a quick sort and filter capability for additional detail. Additional base reporting functionality:
Point-and-click reports are now available across NetBackup, Backup Exec, PureDisk, and Enterprise Vault products. An enhanced set of standard reports is now offered for complete operations tracking. Example reports include drive throughput, virtualization coverage, configurable success rate, and skipped files.
Direct upgrade path
New Features About Symantec OpsCenter Analytics
15
This feature enables you to configure direct upgrade path from existing NOM and VBR installations.
Expanded and simplified deployment:
OpsCenter server is compatible with all NetBackup master server platforms (such as, Windows, Solaris, Linux, and HP-UX Itanium). OpsCenter server installation on NetBackup master server for single-domain administration. Dedicated OpsCenter server for multi-domain visibility and management.
OpsCenter installations must be made directly from the standalone OpsCenter media or image.
About Symantec OpsCenter Analytics

This feature provides a turnkey operation that provides improved reporting capabilities such as advanced, business reporting and improved graphics. (Business reporting was previously available with VBR.) The new OpsCenter Analytics package includes the features associated with Symantec OpsCenter and the following features:

Historical trending and predictive forecasting. Complete report customization. This release is compatible with third-party data protection products such as EMC Legato Networker and IBM Tivoli storage manager.
About NetBackup for VMware

The feature provides the following new enhancements in NetBackup 7.0:
Fully integrated with VMware vStorage APIs VCB is no longer required. This feature eliminates the VCB copy of a VM snapshot to the VCB proxy staging area. NetBackup backs up the snapshot directly from the ESX server. New virtual machine (VM) and file recovery from incremental backups VMware vSphere now provides block-level, incremental VMware backups. Moreover, NetBackup now provides VMware and file-level recovery from the same set of full and incremental backups. New Recovery Wizard
16
New Features Guided Recovery
This wizard simplifies the process of performing a direct VM recovery or redirected VM recovery.
Tighter vCenter integration More VMware identifiers and attributes are available when you configure a NetBackup policy. That includes the VMware hostname, display name, UUID, IP address, VirtualCenter , datacenter, ESX platform, and others.
Guided Recovery
The Guided Recovery feature enhances the NetBackup Oracle agent to provide better functionality for performing Oracle Restore and Recovery operations. Specifically, Guided Recovery clones an Oracle database from a backup, and simplifies the process of creating a new database from backups of an existing database. Guided Recovery uses an Oracle cloning wizard that executes on the new OpsCenter graphical user interface.
New database features and enhancements

The following subsections describe enhancements to NetBackup agents that were recently offered such as the NetBackup Enterprise Vault agent and the NetBackup for Hyper-V agent. In addition, enhancements have been made to support new improvements to SharePoint Granular Recovery, and a new Granular Recovery for Active Directory feature.
Exchange 2010 support

NetBackup is now compatibile with Exchange 2010, and includes the following features:
Backups of Exchange 2010 databases on a standalone server or in a Database Availability Group (DAG). Supported backups include local and off-host snapshots, backups using Granular Recovery Technology (GRT), and local and off-host instant recovery. Instant recovery backups can create only a snapshot or a snapshot and a create a copy on the storage unit. Automatic detection of the preferred database copy or the active database copy in a DAG for backup and restore operations. Dynamic allocation of a storage unit that is based on the server list and returned at the start of a backup.
Non-snapshot and mailbox-level backups are limited to Exchange 2007 and Exchange 2003.
New Features New database features and enhancements
17
Windows 7/2008R2 client support

This release of NetBackup provides NetBackup client support for the Windows 7 desktop platform. In addition, the NetBackup client and agents, media server, and master server now support the Windows 2008 R2 operating system. (The Windows 2008 R2 is exclusively 64-bit from Microsoft.)
NetBackup for Enterprise Vault agent

The NetBackup for Enterprise Vault agent greatly simplifies data protection for the Enterprise Vault servers. It protects all of the Enterprise Vault partitions and their associated databases. The agent supports disaster recovery of a partition and databases. Moreover, it also supports recovery of individual files within a partition. The following enhancements have been made to the NetBackup Enterprise Vault agent for this release:
Inclusion of all Enterprise Vault 8.0 databases using the Enterprise Vault Agent. That includes the fingerprint database, the FSA Reporting database , and the auditing database. An enhanced, automated process of backing up your Enterprise Vault environment using the Enterprise Vault Agent. Enterprise Vault 8.0 Support for granular quiescence You can now back up and restore using the Enterprise Vault Agent at a more granular level. Enterprise Vault Migrator is now included with NetBackup The Enterprise Vault migratory is now included with NetBackup 7.0. Previously, that was a separate download.
NetBackup for Hyper-V agent

The NetBackup for Hyper-V agent protects virtual machines (VM) by backing up the virtual hard drive (VHD) images. From the image backup, you can restore the entire VM or individual files within the VM. That is done without any VHD staging; only the files you select are recovered from tape. Automatic detection of all VMs within the Hyper-V server simplifies the policy setup. The following enhancements have been made to the NetBackup for Hyper-V agent for this release:
New file-level incremental backups
18
New Features About NetBackup support utilities
NetBackup for Hyper-V now supports incremental backups, to complement the dual purpose full backups. Now, file-level recovery is available from both full backups and incremental backups.
Two types of off-host backup NetBackup for Hyper-V now supports off-host backup of VM snapshots on CLARiiON storage arrays. Support for other VSS snapshot providers will follow. Alternatively, using the NetBackup Snapshot Client in the VM to perform off-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 new CSV capability. Flexible VM identification Use the VM hostname, display name, or UUID when configuring policies. NetBackup 7.0 for Hyper-V supports Hyper-V clustering. However, Hyper-V cluster support requires a NetBackup 7.0.0.1 patch or later. To obtain this update contact NetBackup technical support .
Improved SharePoint Granular Recovery

Starting with NetBackup 6.5.4, the NetBackup for SharePoint Agent offered additional, more comprehensive granular recovery capabilities, that included the following:

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.
With NetBackup 7.0, you can reap the benefits of the more comprehensive granular recovery capabilities along with faster granular recovery with the metadata intact.
About NetBackup support utilities

NetBackup 7.0 includes three support utilities: nbsu, NBCC, and NBCCR. The following list summarizes the enhancements that have been made to each utility in this release:
NetBackup Support Utility (NBSU)
New Features NetBackup installation and deployment enhancements
19
The NBSU utility assists you in gathering NetBackup and operating system diagnostic information. This tool queries the host on which it runs and gathers diagnostic information about NetBackup and the operating system. In addition, it provides a wide range of control over the types of diagnostic information gathered. For instance, you can obtain information about NetBackup configuration settings about troubleshooting areas, or about NetBackup or media management job status codes. In NetBackup 7.0 this utility has been enhanced to include the following new features:

New commands line options have been added. Enhancements were made to the SLP, EMM, and versioninfo diagnostics. This utility is now available for the Mac OS X platform.
In addition to the new enhancements, the support and support.exe diagnostic information gathering utilities are no longer included or supported beginning with this release of NetBackup.
NBCC utility The NBCC utility uses the output from various OS and NetBackup commands to analyze the consistency state of the NetBackup configuration. It also analyzes the consistency state of NetBackup databases and catalogs as they relate to tape media. If inconsistencies are detected, NBCC consolidates, and packages the resulting data into a bundle that can be sent to Symantec Tech Support for analysis. Enhancements have been made to this utility to ensure that it supports NetBackup 7.0 functionality. NBCCR utility The NBCCR utility processes database and catalog repair actions as defined in a special file that you can generate under the guidance of Symantec Technical Support. This file is created as part of the analysis of the data that the NBCC utility collects and any site specific situations. For NetBackup 7.0, this utility contains fixes that address the minor issues found in earlier releases.
NetBackup installation and deployment enhancements

This release of NetBackup contains many enhancements in the area of installation and deployment. The following list describes the new changes affecting how NetBackup is deployed, packaged, installed, and updated:
20
DVD Layout NetBackup is now only available on DVD. The product is no longer offered in a CD format. Electronic Software Distribution (ESD) images The DVDimage files are posted and available for download on the FileConnect Website. See About the Electronic Software Distribution (ESD) images" in the NetBackup Installation Guide for more information about how you can download these images. Deploy product license tags. A feature has been added that deploys ISO 19770 standard software asset tags with NetBackup. That is the first step in NetBackups license- and deployment-reporting strategy. Simplified access control Configuration By more tightly integrating AT support into NetBackup, changes have been made that greatly simplify the installation process. LiveUpdate Enhancements Improvements to the LiveUpdate configuration make it possible to specify the LiveUpdate server in the policy. That also supports using different LiveUpdate servers in each policy. Changing the server, no longer requires client-side changes. UNIX Package Consolidation In NetBackup 7.0, most of the add-on products and database agents are now installed with the NetBackup server or the client package. Separate installation for these products is no longer needed. The following products are now included in the NetBackup server package (if the platform supports the product):

BMR master server NDMP NetBackup Vault
The following products are now included in the NetBackup client package (if the platform supports the product):

BMR Boot server DB2 NetBackup Encryption Informix LiveUpdate agent
21
Lotus Notes Oracle SAP Snapshot Client Sybase
The binaries for the listed products are laid down with the server or the client package. A valid license is still required to enable the product. If product configuration was required previously (such as db2_config), configuration is still required. (For Solaris server upgrades, the older versions of any listed products here must be removed before an upgrade to NetBackup 7.0. For example, VRTSnbdb2, SYMCnbdb2, VRTSnbenc, SYMCnbenc, and others. The installation script 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 usability tests that were targeted towards Windows installation improvements:
NetBackup is now capable of importing client lists from a file. That prevents the need to individually select hundreds of clients. Multiple simultaneous push installs greatly improve the installation performance over the previous approach of one client at a time. Improvements have been made to the error logging and reporting. A full configuration summary report now describes what options were selected for the install. In addition, all installation logs are now captured in an HTML format for a more readable display. Preinstallation checks are run to ensure a successful installation.
VxUL Log Directory Restructuring This change enhances the usability of VxUL logs by putting the logs for each service in a unique directory, making it easier for support to find and copy the correct logs. In addition, the performance of the vxlogview command is improved when you search for logs by the OID since this command does not need to look at all of the VxUL log files for NetBackup, it only opens log files for the correct OID.
22
New Features About back-level administration capabilities by the NetBackup-Java console
About back-level administration capabilities by the NetBackup-Java console

NetBackup 7.0 provides additional ways to perform back-level administration of the back-level versions that are compatible. That includes the packaging and the installation of the NetBackup 6.0 MP7 and NetBackup 6.5.4 versions of the NetBackup-Java console on compatible UNIX and Linux platforms.
About Platform proliferation for NetBackup 7.0

This 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 Java GUI on RHEL 5
Chapter
Platform compatibility

About server and client platform compatibility About Operating systems no longer compatible as of NetBackup 7.0 and beyond NetBackup binary sizes Platforms compatiblity with the NetBackup Administration Consoles for UNIX About NetBackup backward compatibility
About server and client platform compatibility

You can find the NetBackup platform compatibility information and other various compatibility lists on the Symantec Support Web site. These compatibility lists offer a variety of up-to-date information about the operating systems that ahat are compatible with NetBackup and NetBackup features. This topic also contains the following types of information:
Descriptions of the compatibility lists that are on the Symantec Support Web site Instructions on how to locate the NetBackup compatibility lists NetBackup backward compatibility information NetBackup binary sizes that include NetBackup media server software and NetBackup client software
About platform and operating system compatibility changes

This release of NetBackup contains many changes and enhancements to the compatible platforms and operatings systems. The following list describes some of the major changes that apply the NetBackup 7.0:
24
Platform compatibility About server and client platform compatibility
All UNIX 32-bit system support has been discontinued. To upgrade these systems to NetBackup 7.0, you must first migrate your current NetBackup 6.x catalogs and databases to a system with a compatible platform. However, 32-bit media servers and clients that use NetBackup 6.x are compatible 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 NetBackup 7.0, you also must update the vendor plug-in to a 64-bit version. All 64-bit platforms are compatible except for FreeBSD clients and Mac clients. IRIX and Tru64 are no longer compatible with NetBackup. Servers and clients with operating systems that use NetBackup 6.x are compatible with NetBackup 7.0 servers. Windows IA64 is supported only as a client. You can no longer use Linux SUSE and Linux RedHat Itanium server platforms as a master or a media server. These platforms are only compatible as a client. You can no longer use HP-UX PA-RISC as a master server. This platform is compatible only as a true media server (media server without the EMM server) or a true client. Linux Red Hat IBM zSeries platforms compatibility has switched to 64-bit clients. Novell NetWare is no longer compatible for use as a media server. This platform is only compatible as a client.
About NetBackup Compatibility Lists

The most up-to-date compatibility information on platforms, peripherals, drives, and libraries is located in various compatibility lists on the Symantec Support Web site. The following compatibility lists are available on the Symantec Support Web site:
The NetBackup Enterprise Server and Server 7.x OS Software Compatibility List contains information about the operating system (OS) level and the version that is required to be compatible with a NetBackup master or media server. It also describes the OS level and the version that is required to be compatible with a NetBackup client. Predecessors and successors to the documented operating system levels may function without difficulty, as long as the release provides binary compatibility with the documented operating system.
http://entsupport.symantec.com/docs/337048
25
The NetBackup Enterprise Server and Server 7.x OS Software Compatibility List contains information about each of the following NetBackup Enterprise features:

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 compatibility for a platform or OS version requires platform vendor support for that product. The platform compatibility lists that NetBackup maintains are subject to change as vendors add and drop platforms or OS versions.
The NetBackup server 7.0 hardware compatibility list includes information for compatible drives, libraries, virtual tape devices, robot-types, fibre-channel HBAs, switches, routers, bridges, iSCSI configurations, and encryption devices
The NetBackup 7.x Hardware compatibility list includes information about the compatible drives, robot types, switches, routers, and bridges, and iSCSI configurations 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 List This compatibility list contains the most current platform compatibility information for NetBackup database agents.
NetBackup 7.x Snapshot Client compatibility lists
26
NetBackup 7.x BMR File System and Volume Manager compatibility lists
See also the NetBackup Bare Metal Restore Administrator's Guide for the following additional compatibility lists:

BMR compatible shared resource tree (SRT) versions BMR compatible file systems and volume managers BMR compatible cluster solutions BMR disk space requirements
NetBackup7.x Cluster Compatibility List

NetBackup Desktop/Laptop Option compatibility list

Backup Exec Tape Reader compatibility list

To locate platform compatibility information on the Symantec Support Web site
Go to the following URL: www.symantec.com/business/support
2 3
Select the NetBackup Enterprise Server link under the Support for Top Products title on the Web page . Select Master Compatibility List link under the Compatibility title on the Web page . The Web page refreshes and contains a list of compatibility documents. From this Web page, you can refine your search to find a link to the appropriate document. (The compatibility list documents are in PDF format. You must have Adobe Acrobat Reader to view these documents.)
About the deduplication host platform compatibility

The following is a list of the compatible platforms for NetBackup Deduplication:
Solaris SPARC 10 x64 Solaris requires an encryption package (SUNWcry64). You must download and install the package. It is not part of the Solaris installation media, and Symantec cannot distribute the package. Red Hat Enterprise Linux:
27
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, or run correctly.
SUSE Linux Enterprise Server 10 (SLES 10) x64 The SUSE Linux system must be at patch level 2. Windows 2003 x64 Windows 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 physical memory space. If swap space is less than physical memory, database problems may affect installation and performance.
About platform life cycles

NetBackup software is compatible with an ever-changing set of platforms. And NetBackup must be flexible enough to handle platform life cycle issues such as adding and removing a platform from its compatibility list. See About adding a platform on page 27. See About Removing a client platform on page 27.
About adding a platform

Adding a platform that is compatibile with NetBackup introduces a situation where the platform has a future, but no history. In this situation, backward compatibility cannot be guaranteed without exhaustive testing. When a platform is added for a NetBackup release, the platform is compatible with that version and subsequent versions (but not previous versions).
About Removing a client platform

The customer commitment for client platform version support is one version back with every effort to be compatibile with all versions. An exception is that the client version cannot be newer than the master and the media server version. You can mix the individual clients that are at different version levels within a NetBackup domain. However, it is possible that during an alternate restore, the
28
Platform compatibility About Operating systems no longer compatible as of NetBackup 7.0 and beyond
restore is sent to an older version. Alternate restores should go to the same or newer versions. See About NetBackup backward compatibility on page 36.
About Operating systems no longer compatible as of NetBackup 7.0 and beyond

Table 2-1 displays the operating systems that are no longer compatible with NetBackup starting with the release of NetBackup 7.0 and beyond. Table 2-1 Operating systems no longer compatible with NetBackup as of NetBackup 7.0 and beyond Hardware
Power Power x86 i386 (x86) i386 (x86) i386 (x86) PA-RISC PA-RISC PA-RISC PA-RISC IA64 Media server and client compatible only Media server and client compatible only Media server and client compatible only
OS/Version
AIX 5.1 AIX 5.2 Asianux 3.0 FreeBSD 5.3 FreeBSD 5.4 FreeBSD 6.0 HP-UX 11.00 HP-UX 11.11 HP-UX 11.23 HP-UX 11.31 HP-UX IA64 11.23 IRIX 6.5.26 and greater Mac OS X 10.3 Mac OS X 10.4 NetWare 5.1 NetWare 6.0 NetWare 6.5
Comments
Apple Macintosh POWERPC, i386 x86 x86 x86 Client compatible only
Platform compatibility About Operating systems no longer compatible as of NetBackup 7.0 and beyond
29
Table 2-1
Operating systems no longer compatible with NetBackup as of NetBackup 7.0 and beyond (continued) Hardware Comments
OS/Version
Novell OES (Linux) 1 SP2 Red Flag Linux 4.1 Red Hat 2.1 Red Hat 3.0 Red Hat 3.0 Red Hat 3.0 Red Hat 3.0 Red Hat 4.0 Red Hat 5.0 Solaris 8.0 Solaris 8.0 Solaris 9.0 Solaris 9.0 Solaris 10.0 x86 Solaris 10.0 x86 SUSE Desktop 9.0 SUSE Desktop 9.2 SUSE Desktop 9.3 SUSE Linux Enterprise Server 8 SUSE Linux Enterprise Server 8 SUSE Linux Enterprise Server 8 SUSE Linux Enterprise Server 9 SUSE Linux Enterprise Server 9 SUSE Linux Enterprise Server 9
x86 x86 x86 x64 IA64 z/Architecture IA64 IA64 SPARC x86 x86 x64 x86 x64 x86 x86 x86 x86 x64 IA64 x86 x64 IA64 Client compatible only Client compatible only Client compatible only
30
Platform compatibility NetBackup binary sizes
Table 2-1
Operating systems no longer compatible with NetBackup as of NetBackup 7.0 and beyond (continued) Hardware
IA64 Alpha Alpha x86 and x64 IA64 Client compatible only
OS/Version
SUSE Linux Enterprise Server 10 SP1 Tru64 5.1a Tru64 5.1b and greater Windows Server 2000 Windows Server 2003 SP1 and R2
Comments
Client compatible only
NetBackup binary sizes

The information in this section helps you determine if your NetBackup environment has the proper amount of disk space allocated to your servers to safely and efficiently back up and restore all of the data. Table 2-2 shows the approximate binary size of the NetBackup master and media server software, and the NetBackup client software requirements for each platform and operating system that is compatible with NetBackup. Table 2-2 OS/Version
AIX 5.3 AIX 6.1 Asianux 2.0, 3.0 Canonical Ubuntu 8.0 CentOS 5.2, 5.3 Debian GNU/Linux 4.0, 5.0 FreeBSD 6.1, 6.2, 6.3, 7.x HP-UX 11.11
NetBackp binary sizes for compatible platforms 32-bit 64-bit 32-bit 64-bit Notes client client server server
928MB 928MB 510MB 510MB 510MB 510MB 16MB 632MB 1666MB 64-bit binary compatible. Media server or client compatibility only. 3083MB 64-bit binary compatible. 3083MB 64-bit binary compatible. 1726MB
CPU Architecture
POWER POWER x64 x64 x64 x64 x86 PA-RISC
31
Table 2-2 OS/Version

HP-UX 11.23
NetBackp binary sizes for compatible platforms (continued) 32-bit 64-bit 32-bit 64-bit Notes client client server server
632MB 1666MB 64-bit binary compatible. Media server or client compatibility only. 1666MB 64-bit binary compatible. Media server or client compatibility only. 3012MB
CPU Architecture
PA-RISC
HP-UX 11.31
PA-RISC
632MB
HP-UX 11.31 Mac OS X 10.5, 10.6 Mac OS X 10.5 Novell Open Enterprise Server 2 OpenVMS 5.5 OpenVMS 6.2 OpenVMS 7.3 OpenVMS 6.1 OpenVMS 6.2 OpenVMS 7.3 OpenVMS 8.2 OpenVMS 8.3 OpenVMS 8.2 OpenVMS 8.3 OpenVMS 8.3-1H1 Red Flag Linux 5.0
IA64 POWER i386 (x86) x64 22MB 22MB
922MB
492MB
1662MB
HP VAX HP VAX HP VAX HP Alpha HP Alpha HP Alpha HP Alpha HP Alpha HP IA64 HP IA64 HP IA64/Alpha x64
16MB 16MB 16MB 16MB 16MB 16MB 16MB 16MB 16MB 16MB 16MB 510 MB 510 MB 510 MB 1726MB
Red Hat Enterprise Linux 4.0 x64 (AS) Red Hat Enterprise Linux 5.0 x64 (base)
1726MB 64-bit binary compatible.
32
351 MB 351 MB 96MB Compatible with client only.
CPU Architecture
Red Hat Enterprise Linux 4.0 IA64 (AS) Red Hat Enterprise Linux 5.0 IA64 (base) Red Hat Enterprise Linux 4.0 POWER (AS) Red Hat Enterprise Linux 5.0 POWER (base) Red Hat Enterprise Linux 4.0 z/Architecture (AS) Red Hat Enterprise Linux 5.0 z/Architecture (base) Red Hat Enterprise Linux Desktop 4.0 Red Hat Enterprise Linux Desktop 5.0 x64
Compatible with client only.
96MB
12MB
12MB
510MB
x64
510MB
64-bit binary compatible.
Red Hat Enterprise Linux 5.0 x64 (Advanced) Solaris 9.0 Solaris 10.0 Solaris 10.0 SPARC SPARC x64
510MB
1726MB
525MB 639MB 439MB 345MB
64-bit binary compatible. 2050MB 64-bit binary compatible. 1915MB 64-bit binary compatible. Compatible with client only.
SUSE Linux Enterprise Server IA64 10 (SP1) SUSE Linux Enterprise Server x64 10 (SP1) SUSE Linux Enterprise Server POWER 10 (SP1) SUSE Linux Enterprise Server z/Architecture 10 (SP1)
492MB
1662MB
101MB
12MB
Platform compatibility Platforms compatiblity with the NetBackup Administration Consoles for UNIX
33
345MB Compatible with client only.
CPU Architecture
SUSE Linux Enterprise Server IA64 11 SUSE Linux Enterprise Server x64 11 SUSE Linux Enterprise Server z/Architecture 11 Windows x86 600MB
492MB
1662MB
12MB
1700MB
Covers all compatible Windows x86 platforms 1900MB Covers all compatible Windows x64 platforms Compatible with client only.
Windows
x64
700MB
Windows
IA64
600MB
Platforms compatiblity with the NetBackup Administration Consoles for UNIX

The NetBackup Administration Console provides a graphical user interface through which the administrator can manage NetBackup. The interface can run on any NetBackup Java-capable system. For information on how to install the consoles, see the NetBackup Installation Guides. And for information on how to use the NetBackup Adminstration Console, see the NetBackup Administrator's Guide, Volume 1. Note: The window managers in the following table are compatible with NetBackup when you use NetBackup Java. You may encounter some user-interface anomalies when you use the various window managers that are available on UNIX platforms. Many of these problems are documented and can occur because of unusual or non-standard window manager configurations. In the most common cases of misplaced or shifted components within a dialog, resize the dialog. This action refreshes the display and causes the interface to display the information correctly. Table 2-3 is a list of platforms that are compatible with the NetBackup-Java Administration Console and the Backup, Archive, and Retore user interface in this release.
34
Table 2-3
Platforms that are compatible with the NetBackup-Java Administration Console and Backup, Archive, and Retore user interface CPU Architecture NetBackup-Java Backup, administration Archive, and console Restore interface
Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes 1.6-16 1.6-16 1.6-16 1.6-16 1.6-16 1.6-16 1.6-16
OS/Version
JRE upgrade version
AIX 5.3 AIX 6.1 HP-UX 11.11 HP-UX 11.23 HP-UX 11.31 HP-UX 11.31 Red Hat Enterprise Linux 4.0 (AS) Red Hat Enterprise Linux 5.0 (base) Red Hat Enterprise Linux 4.0 (AS) Red Hat Enterprise Linux 5.0 (base) Red Hat Enterprise Linux 4.0 (AS) Red Hat Enterprise Linux 5.0 (base) Red Hat Enterprise Linux 4.0 (AS) Red Hat Enterprise Linux 5.0 (base) Red Hat Enterprise Linux Desktop 4.0 Red Hat Enterprise Linux Desktop 5.0 Solaris 9.0 Solaris 10.0 Solaris 10.0 SUSE Linux Enterprise Server 9 SUSE Linux Enterprise Server 10 (SP1) SUSE Linux Enterprise Server 10 (SP1)
POWER POWER PA-RISC PA-RISC PA-RISC IA64 x64 x64 IA64 IA64 POWER POWER z/Architecture z/Architecture x64 x64 SPARC SPARC x64 IA64 x64 POWER
Java 6 SR6 Java 6 SR6 6.0.05 6.0.05 6.0.05 6.0.05 1.6-16 1.6-16 1.6-16 1.6-16
35
Table 2-3
Platforms that are compatible with the NetBackup-Java Administration Console and Backup, Archive, and Retore user interface (continued) CPU Architecture NetBackup-Java Backup, administration Archive, and console Restore interface
Yes Yes Yes Yes Yes Yes Yes 1.6-16 1.6-16 1.6-16
OS/Version
JRE upgrade version
SUSE Linux Enterprise Server 10 (SP1) SUSE Linux Enterprise Server 11 SUSE Linux Enterprise Server 11 SUSE Linux Enterprise Server 11
z/Architecture IA64 x64 z/Architecture
Windows Server 2003 Enterprise Edition x86 (SP1) Windows Server 2003 Enterprise Edition x86 (R2) Windows Server 2003 Enterprise Edition x64 Windows Server 2003 Enterprise Edition x64 (R2) Windows Server 2003 Enterprise Edition IA64 Windows Server 2003 Enterprise Edition IA64 (R2) Windows Server 2008 Enterprise Edition x86 Windows Server 2008 Enterprise Edition x64 Windows Server 2008 Enterprise Edition x64 (R2) Windows XP Professional SP2 Windows XP Professional SP2 Windows Vista Windows 7 Ultimate x86 or x64 IA64 x86 or x64 x86 or x64
Yes
Yes
1.6-16
Yes Yes
Yes Yes
1.6-16 1.6-16
Yes Yes
1.6-16 1.6-16
Yes Yes Yes Yes Yes
1.6-16 1.6-16 1.6-16
Yes Yes Yes Yes Yes
1.6-16 1.6-16 1.6-16 1.6-16
36
Platform compatibility About NetBackup backward compatibility
About NetBackup backward compatibility

NetBackup is compatible with a mixture of NetBackup servers that are at various release levels in the same environment. However, Symantec validates only certain combinations of servers and clients within a NetBackup environment that must provide backward compatibility. Note: The statements made in this topic do not override Symantec's standard End of Life policies. Once a NetBackup version reaches its end-of-life, no version of that product is supported. That includes backward compatible versions. Please review the following end-of-life technote on the Symatec Support Web site for more information:
Table 2-4 shows the different server version levels that are compatible with NetBackup in this release. Table 2-4 Mixed-server compatibility for NetBackup 7.0 Media server version
70 7.0
Master server version

NetBackup 7.0 NetBackup 7.0 NetBackup 7.0
Client version
7.0 6.5 (and later), 6.0 (and later)
6.5 (and later), 6.0 (and later) 6.5 (and later), 6.0 (and later)
NetBackup 7.0 is not compatible with Windows 2000 systems. However, you can still use NetBackup version 6.x on Windows 2000 clients with your NetBackup 7.0 servers. The following describes what type of action to take if you have any clients that run Windows 2000:
Existing NetBackup customers with Windows 2000 clients at NetBackup version 6.x: New NetBackup customers with Windows 2000 systems: No action is required. These clients are compatible with NetBackup version 7.0 master and media servers. You must install NetBackup version 6.x client software on your Windows 2000 systems. See the following Technote on the Symantec Support Web site for more information. http://entsupport.symantec.com/docs/308850
37
For more information about upgrading NetBackup, refer to the NetBackup Installation Guide for either UNIX or Windows. The following is a list of best-practice rules that you should consider for a mixed-server environment:
Before you upgrade the NetBackup server software, you must back up your NetBackup catalogs and verify that the catalog backup was successful. During an upgrade to NetBackup 7.0, it is necessary to have enough free disk space to accommodate three complete copies of the NetBackup database. That includes all transaction logs and database files in the data directory including BMR 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 when you use default installation methods. In a mixed-server environment, the master server must run the highest version of NetBackup in use in that configuration. A master server can inter-operate with a media server that is running a level of NetBackup that is one major release lower. A media server cannot have a numerically higher version than the master server. (Each media server must run equal or lower levels of NetBackup.) All components (server, client, and console) on an individual system must be at the same version. The backup images that are created under an older version of NetBackup are recoverable with a newer version of NetBackup. Servers can pull and push their version information between master and media servers. Your servers NetBackup version determines whether the version information can be pushed. After startup, an upgraded media server uses the vmd service to push its version information to all servers in its master server list. An automatic update occurs every 24 hours when servers push their version information again. To install NetBackup on Windows 2008/Vista/2008 R2/7 UAC-enabled environments, you must log on as the official administrator. Users that are assigned to the Administrators Group and are not the official administrator cannot install NetBackup in UAC-enabled environments. To allow users in the Administrators Group to install NetBackup, disable UAC.
38
Chapter
Product Dependencies

Operating system patches and updates About VxFS and VxVM compatible versions
Operating system patches and updates

This topic provides information on the product dependencies of this release of NetBackup. You should verify that your operating system is up-to-date with all of the latest patches and upgrades before you install NetBackup. This section is a guide to inform you of the operating systems that require a patch or an upgrade. Table 3-1 provides the known, minimum operating system (OS) patches and updates. A vendor may have released a more recent patch that supersedes a patch that is listed in this table. Symantec recommends that you visit the Support Web site of that particular vendor for their latest patch information. Table 3-1 Operating system patches and updates for NetBackup Patch
AIX runtime libraries 8.0.0.10 and 9.0.0.3 or later xlC.rte 8.0.0.10 fileset
Operating System Type and Version

AIX 5.3
Notes
You may need to reboot after changing to version 9.0.0.3.
For the xlC.rte 8.0.0.10 fileset, you may need to install the IY91284 fix to avoid a potential issue when creating or updating the NetBackup database. The IY91284 fix is part of Maintenance Level 6.
40
Product Dependencies Operating system patches and updates
Table 3-1
Operating system patches and updates for NetBackup (continued) Patch

AIX 5.3 TL7 SP5 (5300-07-05-0831)
Notes
NetBackup 7.0 requires the AIX 5.3 TL7 SP5 (5300-07-05-0831 Maintenance Pack as a minimum. (Higher patch levels should also work.) You can use the oslevel -s command to verify what Maintenance Pack level you have installed.
AIX 6.1
IZ16878
When you start Java user interface applications on AIX 6.1 platforms an exception can occur. To prevent the exception, Symantec recommends that you install patch IZ16878 from IBM Support. The runtime libraries need to be at 9.0.0.3 or later. You may need to reboot after you change to version 9.0.0.3. If you install AT on an HP-UX platform, this patch is required.
AIX runtime libraries 9.0.0.3 or later
HP-UX
COMPLIBS.LIBM-PS32
HP-UX IA64
Networking.NET-RUN: /usr/lib/libipv6.sl 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
41
Table 3-1

Networking.NET2-RUN: /usr/lib/libipv6.1
Notes
HP-UX PA-RISC
Networking.NET-RUN: /usr/lib/libipv6.sl
For HP-UX PA-RISC platforms, this fileset is required:
Networking.NET-RUN-64: For HP-UX PA-RISC platforms, this /usr/lib/pa20_64/libipv6.1 fileset is required: Networking.NET-RUN-64: For HP-UX PA-RISC platforms, this /usr/lib/pa20_64/libipv6.sl fileset is required: Networking.NET2-RUN: For HP-UX PA-RISC platforms, this /usr/lib/libipv6.1 fileset is required: HP-UX 11.11 PHSS_35385 PHSS_32226 PHSS_37516 This patch is required for JAVA 6.0. This patch is a LIBCL patch. Contains fixes for the following:
QXCR1000593919: purifyplus dumps core in PA32 QXCR1000589142: dld crash in LL_new_descendent_list when the aCC application is exiting.
QXCR1000589142: dld crash in LL_new_descendent_list when the aCC application is exiting.
QXCR1000746161: dlsym() hangs QXCR1000593999: dld emits assert messages for chatr +mem_check enabled 64-bit executables PHSS_26946 This patch is necessary to enable any C++ runtime code to work properly. This patch is a libc cumulative patch. This patch contains a linker tools cumulative patch.
PHSS_27740
PHSS_26560
42
Table 3-1

PHSS_32864
Notes
That is a recommended critical patch from HP that is required for successful NetBackup client backups. This patch enables HP-UX 11.11 mmap() to use large files from 2GB to 4GB. That is a recommended critical patch from HP that is required for successful NetBackup client backups. That is a recommended critical patch from HP that is required for NetBackup to use VxSS. Allow POLL_INTERVAL to be set to zero in /var/stm/config/tools/ monitor/dm_stape.cfg. That disables the dm_stape monitor within the Event Monitoring System. Symantec recommends that you upgrade to IPR0109. This patch can cause problems with the programs that have the setuid bit set. Hewlett-Packard s IT resource center Web site contains information about this patch. www1.itrc.hp.com
PHKL_26233
PHSS_35379
PHCO_29029
PHSS_24045
PHSS_30970
HP-UX 11.23
PHSS_37201 PHCO_33431
This patch is required for JAVA 6.0. Symantec recommends that all customers running 11.23 install this patch. That is a recommended critical patch from HP that is required so that dlopen works properly.
PHSS_34858
43
Table 3-1

PHKL_31500
Notes
That is a recommended critical patch from HP that NetBackup requires, particularly when you attempt to run NetBackup with NetBackup Access Control (NBAC). Contains fixes for the following:
PHSS_37492
QXCR1000593919: purifyplus dumps core in PA32 QXCR1000589142: dld crash in LL_new_descendent_list when the aCC application is exiting.
QXCR1000746161: dlsym() hangs QXCR1000593999: dld emits assert messages for chatr +mem_check enabled 64-bit executables HP-UX 11.31 SLES10 x64 PHSS_37202 SLES 10 update 2 This patch is required for JAVA 6.0. The operating system version must be SLES 10 update 2 or greater to run NetBackup 7.0. Change Request ID - 6815915
Solaris 9 SPARC 64-bit client
111712-11 (or greater)
111722-04 (or greater) Patch: 112908-29 (or greater) Patch: 112874-31 (or greater) 122300-53 Solaris 10 SPARC 64-bit update 4 (08/07) and (server and client) newer 139555-08 119963-21 Change Request ID - 6723423 The server is supported on update 4 (08/07) and newer. Change Request ID - 6723423 Change Request ID - 6815915
44
Table 3-1

119964-21 139556-08

Solaris 10 x64
Notes
Change Request ID - 6815915 Change Request ID - 6723423 Microsoft hotfix KB913648 contains the necessary updates to run Volume Shadow Copy.
Windows 2003 SP1
KB913648
Windows x64 (SP1 and SP2) Windows 2003, XP, and Vista
Microsoft storport hotfix
Microsoft microcode reliability update
That is a suggested fix that applies to 64-bit versions of Windows Server 2003, XP, and Windows Vista. Microsoft hotfix KB952696 contains the necessary updates to ensure that you can back up Windows 2008 encrypted files on Windows x32 and Windows x64 systems.
Windows 2008 x32 and x64
KB952696
The following additional product dependency information applies to this release of NetBackup:
Product dependency notification for customers running Microsoft Windows Vista or Windows 2008 server. If you want to protect client (or server) systems that are running either Microsoft Windows Vista or Windows 2008 server, you may need to install Microsoft hotfix number KB952696. If you attempt to back up any protected files that have been encrypted by the operating system, NetBackup cannot back up these files. NetBackup reports that it is unable to access the encrypted files and the backup continues with all of the remaining files. Note: That does not apply to NetBackup encryption. NetBackup encryption is separate from the file system encryption, meaning that NetBackup-encrypted files are backed up. In addition, this hotfix is not needed for any Windows version before Microsoft Windows Vista or Windows 2008 server. If you are running Vista or Server 2008, please refer to KB952696 to see if this hotfix is required for your operating system version
Product Dependencies About VxFS and VxVM compatible versions
45
About VxFS and VxVM compatible versions

Table 3-2 shows the different versions of VxFS and VxVM that are compatible with Symantec NetBackup, and the corresponding operating systems for each. Table 3-2 Versions of VxFS and VxVM that are compatible with Symantec NetBackup Version of VxFS
5.0 and higher 5.0 MP3 and higher 3.3 and 3.5 3.5, 4.1, and 5.0 4.1 and higher 3.5, 4.1, and 5.0 4.1 and higher 4.1 and higher
Operating system
AIX 5L
OS Version
5.3 (64 bit) 6.1 (64 bit)
Version of VxVM
4.0 and higher 5.0 MP3 and higher 3.5 only 3.5, 4.1, and 5.0 4.1 and higher 3.5, 4.1, and 5.0 4.1 and higher 4.1 to 5.0MP3RP3
Notes
HP-UX PA-RISC
11.11 11.23 11.31
HP-UX IA64
11.23 11.31
Red Hat Enterprise Linux 4.0 (AS)
x86-64
IA64
4.1 to 4.1 MPx (5.0 is 4.1 to 4.1MP4RP4 not compatible) 5.0 MP1 and higher 4.1 MP3 and higher 5.0 LoP phase1, phase2 LxRT4.1MP4RP1 and higher on the 4.1 line, 5.0MP3 and higher on the 5.0 line 4.1MP4RP1 and higher in the 4.1 codeline only 5.0RU3 and higher 4.1 MP2 and higher 4.1 MP2 and higher 4.1MP3 and higher in 4.1 codeline. 5.0MP3 and higher on 5.0 codeline. 4.1MP3 and higher in 4.1 codeline only.
POWER Red Hat Enterprise Linux 5.0 (AS) x86-64
IA64
NA
POWER Solaris (SPARC) 9 10 SUSE Linux Enterprise Server 10 x86-64
5.0RU3 and higher 4.1 MP2 and higher 4.1 MP2 and higher 4.1 and higher
IA64
4.1 MP3 (5.0 is not compatible)
46
Table 3-2
Versions of VxFS and VxVM that are compatible with Symantec NetBackup (continued) Version of VxFS
5.0RU3 and higher 4.1 MP3 and higher
Operating system
OS Version
POWER
Version of VxVM
5.0RU3 and higher 5.0RU1 and higher
Notes
SUSE Linux Enterprise Server 11
x86-64
IA64 POWER Windows 2003 Windows 2008 Windows 2008 R2 x86-64 x86-64 x86-64
NA 5.0RU4 and higher NA NA NA
NA 5.0RU4 and higher 4.3 and higher 5.0 and higher 5.1 SP1 and higher
For the most current information and patch requirements for VxFS and VxVM, refer to the NetBackup 7.0 Additional Operational Notes contained in Technote number 337179 on the Symantec Support Web site.
NetBackup has improved its integration with the Veritas File System (VxFS) product to ensure interoperability on all compatible VxFS versions. If running a VxFS version before VxFS 4.0 then new VxFS libraries need to be installed on the client to back up systems running VxFS. You can search and download the appropriate VxFS libraries to your system from Patch Central on the Symantec Support 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 the various operating systems and the Veritas File System (VxFS). Table 3-3 Operating system
AIX HP-UX PA-RISC
Improved Integration with Veritas File System (VxFS) VxFS 5.0

X NA X X
OS Version
5.3 11.11 11.23 11.31
VxFS 4.1
NA NA NA NA
VxFS 3.5
NA X NA NA
47
Table 3-3 Operating system

HP-UX IA64 Red Hat Enterprise Linux 4.0 (AS) Red Hat Enterprise Linux 5.0 (AS)
Improved Integration with Veritas File System (VxFS) (continued) VxFS 5.0
X X
OS Version
11.31 x86-64
VxFS 4.1
NA NA
VxFS 3.5
NA NA
x86-64
NA
NA
SUSE Linux Enterprise Server x86-64 SLES 10 IA64 SUSE Linux Enterprise Server x86-64 SLES 11 IA64 Solaris (SPARC) 9 10
NA
NA
NA
NA
X X
NA X
NA NA
48
Chapter
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)
50
Operational Notes Operational Notes in NetBackup
NetBackup Snapshot Client NetBackup commands and utilities NetBackup OpenStorage Option NetBackup Disk Storage units NetBackup Vault NetBackup for VMware
Operational Notes in NetBackup

The chapter contains the topics that explain important aspects of NetBackup 7.0 operations that may not be documented elsewhere in the NetBackup documentation set. For additional operational note information about this release, see the following online PDF titled, NetBackup 7.0 Additional Operational Notes contained in Technote number 337179 on the Symantec Support Web site.
Note: References to UNIX also apply to Linux, unless otherwise stated.
NetBackup installation and start-up notes

The following subsections offer additional the information that can help you install NetBackup or use NetBackup.
NetBackup media and rebranding changes

The following list of items describe the NetBackup DVD and NetBackup rebranding enhancements:
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 your current 6.x NetBackup environment includes NOM 6.x, you can upgrade NOM to OpsCenter with an upgrade to NetBackup 7.0. Platform and operating system support changes in NetBackup 7.0 See About NetBackup Compatibility Lists on page 24.
Operational Notes NetBackup installation and start-up notes
51
UNIX package consolidation In NetBackup 7.0, most of the add-on products and database agents are now installed with the NetBackup server or the client package. Separate installation for these products is no longer needed. The following products are now included in the NetBackup server package (if the platform supports the product):

BMR master server NDMP NetBackup Vault
The following products are now included in the NetBackup client package (if the 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 client package. A valid license is still required to enable the product. If product configuration was required previously (such as db2_config), configuration is still required. For Solaris server upgrades, the older versions of any listed products here must be removed before an upgrade to NetBackup 7.0. For example, VRTSnbdb2, SYMCnbdb2, VRTSnbenc, SYMCnbenc, and others. The installation script 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 changes New NetBackup 7.0 media server installations cannot be clustered. However, existing 6.x clustered media servers can be upgraded to version 7.0 and remain clustered.
52
All compressed files are compressed using gzip. The installation of these files requires that gunzip, and gzip, be installed on the machine before NetBackup is installed. For all UNIX platforms except HP-UX, the binaries are expected to be in /bin or /usr/bin and that directory is a part of the root users PATH variable. On HP-UX systems, the gzip and gunzip commands are expected to be in /usr/contrib/bin. Installation scripts add that directory to the PATH variable. These commands must be present to have successful UNIX installations. The following instructions clarify how to install NetBackup client software in Solaris 10 non-global zones. NetBackup server is supported only in a global zone. Technote 275107 on the Symantec Support Web site contains more information. On a server whose non-global zone does not use a read-only loopback device for 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, and has a sparse non-global zone using a read-only loopback device for the /usr directory, use the following procedure.
To provide clarification for installing NetBackup client software in Solaris 10 non-global zones
In the global zone, create /usr/openv as a symbolic link to the location in which you install the software to in the non-global. That needs to be done even 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
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
53
In the non-global zone, make sure that the directory link exists and is writable. 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 ../
Client push-install or local install can now be done normally according to guides. If the server does have a master or a media server on the global zone, and has a sparse non-global zone using a read-only loopback device for the /usr directory, use the following procedure:
To provide clarification for installing NetBackup client software in Solaris 10 global zones
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 installed in a base directory (BASEDIR) other than the default /opt. And you can link /usr/openv to /BASEDIR/openv. Verify the directory that /usr/openv is linked to. For example:
# ls -al /usr/openv rwxrwxrwx 1 root other 10 Aug 18 11:39 /usr/openv -> /opt/openv/
In the non-global zone, create a writable directory where the /usr/openv points to. For example:
# mkdir /opt/openv
Client push-install or local install can now be done normally according to guides.
General installation and upgrade items

The following list contains general installation and upgrade information:
Check for available disk space prior to upgrading to NetBackup 7.0
54
During an upgrade to NetBackup 7.0, it is necessary to have enough free disk space to accommodate three complete copies of the NetBackup database. That includes all transaction logs and database files in the data directory including BMR 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 when you use default installation methods.
Beginning with NetBackup 7.0, nbmail.cmd is installed to the netbackup\bin\goodies folder. It had previously been installed to the netbackup\bin folder. Like the other scripts in the netbackup\bin\goodies folder, you now have to copy nbmail.cmd to the netbackup\bin folder. (You would then modify nbmail.cmd at that location for it to take effect. Log files for VxUL OIDs from previous releases Log files for VxUL OIDs that were used in a previous release may be left in the root logs directory (/usr/openv/netbackup/logs on UNIX and C:\Program Files\Veritas\Netbackup\logs on Windows) after an upgrade to NetBackup 7.0. This occurs because the OIDs do not have an OID entry in the nblog.conf file 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. You can display these log files with vxlogview in NetBackup 7.0 if you specify the following.
-G <root log dir> -o oid
Where <root log dir> is either /usr/openv/netbackup/logs on UNIX or C:\Program Files\Veritas\Netbackup\logs on Windows. And oid is the 102 , 113, 120, and so on. You can remove these OIDs after the upgrade. However, you must manually delete the OIDs because the vxlogmgr cannot access them. If you think you may need to report a problem in a previous release, then you may want to keep them for that purpose.
To install NetBackup on Windows 2008/Vista/2008 R2/7 UAC-enabled environments, you must log on as the official administrator. Users that are assigned to the Administrators Group and are not the official administrator cannot install NetBackup in UAC-enabled environments. To allow users in the Administrators Group to install NetBackup, disable UAC. If you install NetBackup server on top of an existing NetBackup client to upgrade the client to a server, PDDE is non-functional. That issue applies to SLES, Red Hat, and Solaris platforms. You must completely remove the NetBackup client and then install the NetBackup server software. Follow the instructions in the NetBackup Installation Guide for UNIX and Linux.
55
The NetBackup Tape Device Driver Installation wizard is no longer present on the installation media. In most cases, the manufacturers device drivers or the drivers that are included with the operating system are appropriate. In environments where the NetBackup tape device drivers are required, you can download them from the NetBackup Support Web site at the following location.
http://support.veritas.com/docs/287850
In a future release, it may be required that clients connect to the master server to complete an installation. Symantec recommends the following Microsoft updates when you run NetBackup on Windows operating systems:
Microsoft storport hotfix. This fix applies to Windows x86 and x64, on both SP1 and SP2: (required) http://support.microsoft.com/?id=932755 Microsoft microcode reliability update. This fix applies to 32-bit and 64-bit versions 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 run NetBackup 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 for NetBackup 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 except FreeBSD and Macintosh (universal - i386/ppc). If you currently use NetBackup 6.x on any 32-bit systems other than FreeBSD and Macintosh, you cannot upgrade those systems to 7.0. However, you can migrate the NetBackup 6.x
56
catalogs and databases on those systems to a supported 64-bit platform system and then upgrade to 7.0. See the NetBackup Installation Guides for more information about migrating NetBackup master servers from 32-bit to 64-bit. Any 32-bit media servers and clients that use NetBackup 6.x are compatible with the 64-bit master servers that use NetBackup 7.0.
Symantec recommends that you have the master server services up and available during a media server upgrade. Symantec recommends that all customers running HP-UX 11.23 install the patch (PHCO_33431). If you do not install the patch before you install NetBackup on a system with an updated version of 11.23, the installation may fail. The operating system may open a user interface window (for example, File Manager on a Solaris system,) when the DVD is inserted into the drive. Symantec recommends that you do not use this window to install NetBackup products because unpredictable results may occur. Follow the installation instructions that are provided in the NetBackup 7.0 documentation set.
NetBackup LiveUpdate
NetBackup LiveUpdate is not compatible with Open VMS (UNIX) or Novell operating systems.
Secure push install

The installation methods (ssh and sftp) of pushing UNIX client software from a UNIX master server to a UNIX client host consist of running the install_client_files script on the command line. Both of these methods are based on the usage of the SunSSH and OpenSSH products and these products must be at specific version and patch levels. For more information about these patches, refer to Table 3-1 in Chapter 3, NetBackup product dependencies.
NetBackup cluster
The 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 version 7.0 and they remain clustered.
57
When a fault occurs in a cluster resource group for NetBackup in a SunCluster configuration, failover of the NetBackup resource group does not occur. The failure in this situation could happen if the NIC (network) or other resources could not come online. When you upgrade clustered NetBackup servers to NetBackup 7.0, you may encounter Windows event log messages that indicate the Sybase service (SQLANYs) failed to start. These messages are generated in a short period of time normally a window of two to three seconds. These messages coincide with the cluster configuration portion of the upgrade. You should expect these messages 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 that users make sure patch 278307 is installed before you install or upgrade to NetBackup 7.0. See http://entsupport.symantec.com/docs/278307 for more information. When you launch the NetBackup Administration Console, you should log into the server using the virtual name that is associated with NetBackup. With the need for increased security, you must be able to configure NetBackup with 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 of application clusters. When you configure disk pools or storage servers, application clusters are not supported. After you install or upgrade NetBackup on UNIX clusters other than SunCluster, you should increase the NetBackup resource offline timeout to at least 600 seconds. When you install or upgrade NetBackup on Sun Clusters, make the following changes to the NetBackup resource group tuning parameters to ensure a successful failover:
Increase the STOP_TIMEOUT parameter from the default of 300 seconds to at least 600 seconds. Set the pmf Retry_count parameter to 0.
These changes can be accomplished using the following commands. Note that running 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
58
Operational Notes NetBackup Documentation Notes
If you install NetBackup 7.0 on the HP Service Guard v11.18 (or 11.17) on more than one node, the NetBackup cluster resource group may become unmanageable when the NetBackup package (Virtual IP) fails to come online or offline. Offline and failover of the cluster package does not occur. If you encounter this issue, do the following after you install NetBackup, and all cluster nodes:
Open the NetBackup package configuration file (/etc/cmcluster/netbackup/netbackup.config). Change the name of the configuration entry for subnet mask from MONITORED_SUBNET to SUBNET on all of the nodes in the cluster. You do not need to update the cluster because the configuration has not changed. 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 three lines to uncomment the parameter.
NetBackup Documentation Notes

The following information should be considered as part of the NetBackup 7.0 documentation set:
NetBackup Enterprise Vault Migrator The NetBackup Enterprise Vault migrator is documented in Appendix A of the NetBackup Enterprise Vault Agent Administration Guide. Please refer to this document for information regarding the NetBackup Enterprise Vault migrator. The following new documents are packaged with NetBackup 7.0:

NetBackup LiveUpdate Guide NetBackup Installation Checklist Symantec NetBackup Deduplication Guide
Internationalization and localization Notes

The following list identifies the issues that relate to Internationalization and localization:
Operational Notes Internationalization and localization Notes
59
The NetBackup command-line menu user interfaces (MUIs) cannot input and modify multi-byte characters and they are not localized to any language. The following list identifies the various menu user interfaces:

bp bpadm tpconfig menu vmadm vltadm
The NetBackup-Java Administration console core dumps if you use Simplified Chinese UTF-8 locale on a Solaris SPARC 64-bit system with Solaris 10 Update 2 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 for more information about this issue. If you encounter this issue, apply the Solaris patch that Sun provides to fix this issue 6901233. When you run on a non-English locale, a problem can occur if you use spaces in the pathname. Spaces in the pathname can cause a backup to fail. The installation of NetBackup client to traditional Chinese paths that contain spaces such as C:\Program Files may cause backup failures. You should install NetBackup client software to a path that does not contain spaces. Installation to paths that contain non-ASCII characters may cause backup or restore failures. If you plan to install an English version of NetBackup 7.0 on top of an existing localized version NetBackup, without installing the localized contents in the Language package CD first, you must remove the localized contents that are installed on your system. For Windows and UNIX installations, the install path must not contain multi-byte characters. The NetBackup Java Administration Console does not support user-defined characters (UDC) and vendor-defined characters (VDC) because of the implementation of Javas encoding converters. NetBackup can be installed to environments running different versions of UNIX based operating systems as long as the system locales are identical. Use of different locales across UNIX platforms can cause user interface corruption or a possible data loss.
60
Operational Notes Internationalization and localization Notes
If you mix non-English versions of Windows and UNIX platforms, differences in operating system architecture and encodings may cause non-English file names 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-Java Administration Console may display non-English characters incorrectly leading to functional failures. At the time of this release, the following database agents have restricted support 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
When you use 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 other database storage locations The path names that are specified in the policy Backup Selections, like script, template, or batch file locations That applies to all supported platforms, including the use of previous versions of those NetBackup database agents with NetBackup 6.0 servers.
The following NetBackup user-defined strings must not contain Multi-byte characters:
Hostname (master server, media server, EMM server, Volume Database Host, Media Host, Client) Policy Name Policy KEYWORD (Windows Only) Backup, Archive, and Restore KEYWORD (Windows Only) Storage Unit Name
Operational Notes NetBackup Bare Metal Restore
61
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 Restore

The following list contains the items that relate to the NetBackup Bare Metal Restore feature:
An issue can occur when you use bmrsetupmaster on the command line interface (CLI) to configure a BMR master server on an AIX 5.3 platform. More specifically, this issue occurs on a 7.0 or greater BMR master server on an AIX 5.3 or greater platform. This issue occurs because the stack size, data segment size, and max memory size ulimit parameters on the system are 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 ulimit parameters to unlimited and run bmrsetupmaster again. To change the ulimit parameters:
Run the ulimit -a command on the BMR master server. This command prints 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 change the limits:

ulimit -s unlimited ulimit -d unlimited
62
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.
You can upgrade to NetBackup 7.0 only from NetBackup 6.x. You cannot directly upgrade an older standalone BMR product (BMR 4.7) to NetBackup 7.0, but it can be migrated to NetBackup 7.0. To migrate from BMR 4.7, refer to the, Upgrading and migrating from older BMR versions, section in the NetBackup Bare Metal Restore Administrators Guide. About creating a shared resource tree (SRT) for Windows Starting with NetBackup 7.0 the boot server does not support the creation of 6.5.X and 6.X SRT. However a NetBackup 7.0 SRT does support restores of pre-7.0 NetBackup ( for example, 6.5.X or 6.X ) clients. The SRT that contains NetBackup 7.0 or a higher version NetBackup Client can be used to restore back-level NetBackup clients. About copying a pre-NetBackup 7.0 SRT Starting with NetBackup 7.0 the boot server does not support copying of 6.5.X and 6.X SRT. About importing a pre-NetBackup 7.0 SRT Starting with NetBackup 7.0 the boot server does not support importing of 6.5.X and 6.X SRT. The Windows Fast Restore feature requires a DNS server to be able to resolve the client and Servers. When EMC PowerPath software is running on the original client, BMR can only support the restoration of a client back onto the original hardware. BMR does not support restoring the Remote Installation Folder location of an RIS Server. You can restore an RIS Server using the System Only feature. You can also restore the RIS server by editing the client configuration, and removing the volume that is used for the Remote Installation Folder location from the map. SRT creation fails with RHEL5.3 If RHEL5.3 media (CDs) is used for SRT creation, SRT creation fails and the following 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.
63
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, it can 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 all occurrences with Red Hat Enterprise Linux Server 5.3. This change should enable creation of a RHEL5.3 SRT, however it also disables creation of a RHEL5.0, 5.1, and a 5.2 SRT. (RHEL5.3 introduces the new 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-based Restore. This restriction exists because a DOS-based Restore requires a 16-bit OS installer application (winntsetup.exe) that can be invoked from within DOS environment. For 64-bit versions of Windows OS, Microsoft did not ship 16-bit installers. Hence, the temporary OS installation of 64-bit OS for BMR cannot be initiated from a DOS environment. As a result, Windows x64 client systems cannot be restored using the legacy DOS-based Restore. In addition, the BMR Fast Restore is the only mechanism of BMR Restore for Windows x64 client systems. No support for Veritas Storage Foundation (VxFS) for Windows (SFW) on Windows x64 clients. Windows x64 client systems that run VxFS for Windows (SFW) cannot be restored. This issue is valid because Windows clients that run SFW cannot be restored using Fast Restore mechanism of BMR. This means, Windows clients that run SFW can be BMR restored using only a legacy DOS-based Restore mechanism. For Windows x64 client systems, the legacy DOS-based Restore mechanism cannot be used for the reasons previously stated. Hence, Windows x64 client systems that run VxFS for Windows (SFW) cannot be restored. Because of this issue, BMR cannot protect Windows x64 client systems that run VxFS for Windows (SFW). Currently, there is no work-around available. No support for Legacy Boot Floppy Wizard on Windows x64 boot server.
64
With the release of NetBackup, a BMR boot server can be installed on a Windows x64 system as well. In general, BMR does not distinguish between the 32-bit and 64-bit boot server on Windows. Thus, a 32-bit (x86) Windows boot server that is upgraded to NetBackup 6.5.4 or 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 host a 32-bit and a 64-bit SRT. However, the Legacy Boot Floppy Wizard is not available on a 64-bit boot server . If you try to run the wizard, BMR informs the 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 Boot Server, this code executes under WOW32. On 64-bit boot server , however, 16-bit code cannot be executed. This limitation exists in the 64-bit Windows OS. 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 must be BMR restored by using the legacy DOS-based restore.
No support for GPT disks. BMR does not support Windows x64 client systems that have one or more GPT disks. No work-around exists to completely support GPT disks; but BMR backup may succeed in case of such systems. If the backup was successful, BMR may be able to restore the system; although the GPT disks are implicitly restored as MBR-based disks. Also, as Windows 2003 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 undefined and unknown. Restore of a BMR 6.5.5 Solaris 10_x64 client fails. The restore of a BMR 6.5.5 Solaris 10_x64 client that has a NetBackup 7.0 client that is installed as part of the SRT creation process can fail intermittently. To avoid this issue, install the NetBackup 6.5.5 client into the SRT and use that SRT to restore the Solaris 10_x64 server. Do that even if the boot server version is 7.0. When you use the BMR Administration console to map an object, the source object is disabled in the user interface if mapping is successful. That indicates that it cannot be mapped again unless you un-map the object. For Solaris 10_x64 client configurations, when you map certain objects such as slices or volumes, even if the mapping completes successfully, the original object is not disabled. That does not mean that the mapping has failed. A BMR Restore using such a mapped configuration still completes successfully. A DDR restore of a BMR HP-UX 11.11 client fails the following occurs while the configuration is mapped:
65
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: Primary Master > Primary Slave > Secondary Master > Secondary Slave, then the first boot after a successful restore may fail. For example, the order of the disks on a 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 environment may 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 it to be hd0. Then during the first boot, /dev/sdd would be mapped to hd0 because of 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 a restore.
A bmradmin user account that is created on a Windows boot server during a boot server installation is saved and not deleted later. A bmradmin account is created on a Windows BMR boot server during the boot server registration. (It is not created on non-Windows boot servers.) This account is created unconditionally because at the boot server installation and registration time, it is not clear whether you may require a Legacy SRT or not. Legacy SRTs require this account to perform legacy restores that use a CD or floppy boot option. FastRestore operations do not require this account. If you determine that you do not need to perform legacy restores, then you can remove this account. However, you if remove this account, and then decide that you need it to run a legacy restore, you must recreate the account manually. Manually creating this account requires assistance from Symantec Support because it is originally created with a predefined password and other attributes.
66
Operational Notes General NetBackup operational notes
The bmrsrtadm command on AIX and HP-UX prompts you to enter the desired architecture (32/64) while the BMR SRT is created. If you want to install NetBackup client versions that are older than 7.0 into the SRT, the OS architecture type that you select should be 32-bit. For NetBackup 7.0, select 64-bit as the OS architecture type. While you install the NetBackup client into the SRT, bmrsrtadm gives the appropriate error message if there is any incompatibility between the SRT OS architecture type and the NetBackup client version. You can use a shared resource tree (SRT) that contains a version of the NetBackup client of 7.0 or higher restore the back-level NetBackup clients.
General NetBackup operational notes

The following list contains the general NetBackup information:
An upgrade to SQLAnywhere 11.0.1 has been made in NetBackup 7.0. However, there is a restriction within that version that requires the database server name to be less or equal to 31 characters. The database server name cannot exceed 31 characters. NetBackup has been modified 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 31 characters if necessary. To support software system management standards, NetBackup installs two XML files on each NetBackup host. These files do not affect NetBackup functionality. 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 fail even though the Clone operation was successful. You may receive an error that states the validation failed for specific paths along with the paths. Functionality that is introduced with the NetBackup 6.5.6 or later releases may not be available in the 7.0 release. This functionality is available in later NetBackup 7.x releases. When backing up and restoring a Red Hat Security-enhanced Linux (Red Hat SEL) system with extended attributes (EAs) disabled and the Access Control Lists (ACLs) enabled, any file with ACLs causes the restore to complete with "partially successful" status. That is due to the RH SEL system always returning the ACLs as EAs. To back up and restore ACLs on a Red Hat SEL volume, you must have user_xattr enabled in the mount parameters. The ACL mount parameter setting has no effect.
Operational Notes NetBackup Access Control
67
After you perform a Full Catalog Backup Recovery with Heap Checking enabled, a core dump of dbeng9 occurred. Testing showed that the catalog recovery completed successfully and that bprecover handled the core dump issue appropriately. You can delete and ignore this core dump. A potential for data loss has been seen where Distributed File System Replication (DFSR) paths may be skipped on a backup. However, it is reported as a Status 0 if the DFSR path exceeds 256 characters and DFSR is backed up with shadow copy. See the following Technote on the Symantec Support Web site for more information about this issue.
http://support.veritas.com/docs/336578
NetBackup Access Control

The following list contains the items that pertain specifically to NetBackup Access Control (NBAC):
On a NetBackup 7.0 host, if NBAC is enabled, the NetBackup services may cause a core-dump after one week of running. A failure in Renewing a service credential causes this issue. The typical service credential validity period is one year. NetBackup attempts to renew a service credential when it is seven days old to ensure continual availability of the credential. Due to an error, this scheduled task can cause some of the NetBackup processes to dump core. To avoid this issue, create a cron job or scheduled task to "touch" the existing credential 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 automatically attempt the service credential renewal. That means that the credentials expire after 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
68
Operational Notes NetBackup 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 from one year to five years: - You must first calculate the number of seconds that would be. In this example, 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 has been configured to use NBAC, you should run the bpnbat -login command before you start the upgrade. During the upgrade, the installer connects to the AZ server and upgrade NBAC data. The user that is specified during bpnbat -login should therefore be a member of the NBU_Security Admin group. If the upgrade of NBAC data fails then a message appears and informs you that you must manually run bpnbaz -upgrade. Before running this command, you must perform a bpnbat -login. Symantec recommends that the NBAC NBU_Security Administration group never be modified. With the need for increased security, it is critical to be able to configure NetBackup Access Control (NBAC) in a clustered NetBackup server environment. You can find detailed steps on how to enable NBAC for a highly available NetBackup master server in a clustered environment in the following technote. See, http://entsupport.symantec.com/docs/288471. On a Windows system, a non-root NBU_Admin member (in an NBAC configuration) is unable to perform a task (such as a restore) that the user should 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 the local machine.
A restore fails to recover some (or all) of the files with the message, "Access denied for restore of file". That happens if the user does not have write permission on the destination of the restore., or the file being restored was not 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 "Backup Operators" operating system group on Windows. Members of this group have the necessary privileges.
Operational Notes NetBackup database agents
69
The term non-root on Windows means that you are not an Administrator.
NetBackup database agents

This section contains the general operational notes that can apply to more than one 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 fail when you perform backups and restores with Granular Recovery Technology (GRT) on Windows 2003 R2. A hotfix is available from Microsoft to address this issue.
http://support.microsoft.com/kb/955012
Configuring permissions for log files for Oracle, SAP, Sybase, and Informix database agents. NetBackup uses the /usr/openv/netbackup/logs directory tree not only for the recording of troubleshooting information, but also for progress and communication updates to users and other NetBackup applications. Restrictive permissions on these directories can not only disable the collection of troubleshooting data, but also prevent the application itself from functioning correctly. Backup and restore operations will fail when permissions are too restrictive. We recommend that you make all of the usr/openv/netbackup/logs directories and subdirectories readable and writeable by all users (777 permissions). However, security requirements may prohibit global read-write access. If so, you can restrict permissions of specific directories to a single group or user if the following is true: All backup and restore operations related to that directory are initiated by processes that run as members of that group or as that user. Check that the /usr/openv/netbackup/logs/user_ops directory tree have 777 permissions. The items in this directory need to be accessible for the applications to operate correctly. If you restrict permissions on the other directories located in /usr/openv/netbackup/logs, backup and restore operations are not impacted. However, troubleshooting efforts may be hindered when processes do not have the appropriate permissions to update the debug logs therein.
The remaining topics within this section contain the operational notes that are specific to the individual database agents that NetBackup supports.
70
Lotus Notes agent

The following list identifies the items that pertain specifically to the Lotus Notes agent:
Compression is supported only for Lotus Domino servers on Windows and not on UNIX. In addition, Windows compressed images are not restorable to Lotus Domino servers on UNIX. Requirements for Lotus r6.0.3 and Lotus r6.5.0 on Linux Support for Lotus R6.0.3 and Lotus R6.5.0 on Linux requires a hotfix to resolve the following SPR: SPR#JCHN5QVL3E (which addresses a transaction log recovery issue). After you install the hotfix on a Lotus Domino server, you must make a change to the notes.ini file for Domino to work properly with NetBackup.
Add the following to the end of the notes.ini file for each Domino partition: DEBUG_SEMOP_ERRNO0_EINTR=1. The last character in ERRNO0 is a zero. Restart the Domino server partition.
The hotfix was integrated into the R6.5.1 and R6.0.4 releases. In these releases, customers need to set the flag DEBUG_SEMOP_ERRNO0_EINTR in the notes.ini file. This flag allows retries to happen if and when the operating system returns an unexpected EINTR while LN performs semaphore operations. See www-10.lotus.com/ldd/r5fixlist.nsf/Search?SearchView&Query=JCHN5QVL3E
Requirements for Lotus r6.0.3 or r6.5.0 on Solaris SPARC and AIX Support 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 has been 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 Linux Support for any version of Lotus R6 or R6.5 on Linux requires a change to the notes.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
71
(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 not required.
Requirements for Lotus r6.03 and Lotus r6.5.0 on Windows Support for Lotus R6.0.3 and Lotus R6.5.0 on Windows requires a combination hotfix to resolve the following two SPRs: SPR#THUR5LPPW9 (which addresses a file path syntax) and SPR#JCHN5QVL3E (which addresses a transaction log recovery issue). A single IBM hotfix is available to address both issues. You should remove the previous Lotus hotfixes before you install this new combination hotfix. These issues have been fixed in R6.0.4 and R6.5.1. See, www-10.lotus.com/ldd/r5fixlist.nsf/Search?SearchView&Que ry=JCHN5QVL3E. See, www-10.lotus.com/ldd/r5fixlist.nsf/Search?SearchView&Que ry=THUR5LPPW9.
NetBackup for Microsoft Exchange

The following list contains operational notes for the NetBackup for Microsoft Exchange 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 When using the NetBackup Client user interface or the bpbackup command to initiate an Exchange off-host alternate client backup, the backup fails. Instead, use the NetBackup Administration Console to initiate a manual backup for that Exchange policy. See the "Testing Configurations Settings" section in the NetBackup for Exchange System Administrator s Guide for instructions regarding a manual backup operation. Restoring Exchange in a Cluster When you restore data in an Exchange cluster environment, one must set the destination client value to be the virtual server name. You can restore an Exchange database using a NetBackup client-only installation on a cluster. However, it may not be possible to change the destination client value to match the virtual server name. In that case, use a NetBackup Client user interface on a NetBackup server to change the destination client value to the virtual server name. Exchange snapshot backups fail with status 41 "Network connection failed".
72
That problem occurs when you perform an Exchange snapshot backup attempt with Allow multiple data streams set on the policy, and with a large number of storage groups or databases in the file list, or with Microsoft Information Store:\* in the file list. To resolve this issue, increase the value of the Client Connect Timeout in the master server Properties > Timeouts. Increase the Client Connect Timeout to a value that is greater than the time that it takes the client to perform the snapshot freeze processing.
Exchange 2010 DAG backups may fail with status 48 Client hostname not found. The initial step in an Exchange 2010 DAG backup is the bpresolver job on the virtual DAG node. Bpresolver may return the list of Exchange servers to perform the backup in a Fully Qualified Domain Name (FQDN) format, instead of a node name. The work-around for this issue is to configure the FQDN so that it is resolved to the correct IP address. Modify the NetBackup servers hosts files or correct DNS entries to resolve that. Intermittent failures can occur when you attempt to browse or restore a mailbox from an Exchange GRT image from a Windows 2008 R2 Exchange server. When you attempt to browse or restore an Exchange mailbox from a GRT image from a Windows 2008 R2 Exchange server, you may experience failures. To work around this issue, try the browse or restore operation again. Symantec and Microsoft are working on a solution for this problem. During a Mailbox item restore, multiple seed emails from the backup service account 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 the DAG virtual name as the destination client. Instead, use the node name where the RDB exists or the stand-alone Exchange 2010 server. When you restore a database or databases to a different DAG than where it was backed up, you cannot use the DAG virtual name as the destination client. Instead use the node that contains the active DB being restored to.
When you select multiple backup images from a DAG backup with Enable Granular Recovery selected, granular level restores may fail. Selecting one backup image at a time does succeed. When you restore databases or granular items of a DAG backup, the restore status may be empty from the backup and restore user interface. The status is empty if the restore is initiated from a node in the DAG. You should initiate
73
the restore from the active DAG node or a NetBackup server to properly see the activity status.
User-initiated backups in a DAG environment fail if initiated from a node in the DAG that is not currently active for the virtual DAG name. Initiate the user backup from the active DAG node or manually start the backup from the NetBackup master to properly start the backup. Exchange 2010 granular item restores may result in duplicate message attachments when you restore the mail items that were previously restored and then backed up with granular recovery. The company field of task objects does not get properly restored with Exchange 2010 granular recovery. Snapshot and catalog clean-up not performed after an Instant Recovery restore rolls back some snapshot volumes and copies back of others. The problem occurs when you recover from an Exchange Instant Recovery backup and one volume is rolled back while another is not. For example, that might happen with a roll-forward recovery, in which the database volume is rolled back and the log volume files are copied back. The problem occurs only with the default (Microsoft System) VSS provider. With this provider, the rollback consumes the snapshot volume. That leaves a partial snapshot set and 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. Then use VShadow to make sure that the snapshot volume has been deleted. The bpfis.exe memory usage grows when a snapshot of multiple storage groups or Exchange 2010 databases is processed. In NetBackup testing, the bpfis.exe process memory usage grows by a few megabytes per storage group or Exchange 2010 database. If a single snapshot job 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 to accommodate this growth, or to break up your backup into smaller snapshots. Instant recovery backups are not supported for Exchange in a cluster environment (Exchange 2007 cluster, Exchange 2007 CCR, or Exchange 2010 DAG). Exchange 2010 offhost backups are not supported in NetBackup 7.0. Support will be added shortly after the release of 7.0. An attempt to restore from an Exchange 2003 and 2007 offhost incremental backup may result in a failure to mount the Exchange database after the restore. A special procedure is required to mount the database after the restore. This issue does not impact the ability to mount after restoring only an Exchange
74
offhost full backup. This issue will be resolved shortly after the release of NetBackup 7.0.
The following item applies to Exchange 2003 and 2007: You must specify the exclude list entry as Microsoft Information Store:\Storage_Group_Name. Entering a database is not valid, because Exchange requires that VSS backups contain the entire storage group (for log truncation purposes). You can specify the exclude list entry under the All Policies, or under a specific policy and schedule. The following item applies to Exchange 2010: The exclude list entry is Microsoft Information Store:\Database_Name, even for the databases that exist in a DAG. You can specify the exclude list entry under the All Policies, or under a specific policy and schedule. However, if All Policies is entered for a database in a DAG, the discovery phase of the backup detects the exclude entry, and ignores it. If you enter a specific policy for a database in a DAG, the discovery phase does not detect it. The snapshot phase detects it and ignores it. In this situation, if that is the only database in the bpfis job, it causes the snapshot phase to fail with a status 69 error. The entire backup finishes with an error.
NetBackup for Microsoft SharePoint

The following topics contain the operational note information that relates to the NetBackup for Microsoft SharePoint Portal.
75
General Setup
The following is a list of general items pertaining to the NetBackup for Microsoft SharePoint:
When you use SharePoint 2003 load balancing, all load-balanced Web sites must be uniformly identified in IIS using either host headers or IP addresses, but not both. Environments which mix host headers and IP addresses across load-balanced servers are not supported. To prevent restore failures, the IIS Default Application Pool identity must be a valid SharePoint user ID .
Operational Issues
The following operational issues exist for the Microsoft SharePoint:
When the SharePoint Search Index service updates the databases, it sometimes contends with NetBackup for access to the portal index database. That can result 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. The metadata restore is for SharePoint 2007 only. The SharePoint 2003 restores to the current date and time. The Search Center with Tabs template has some missing items for the restore. Some items are not restored using GRT with the Tabs template. As a workaround, restore the content database that contains the Tabs template site. The Search Center template, Discusion Board list item fails to restore. Some items are not handled properly using GRT with Search Center template. As a workaround, restore the content database that contains the Search Center template site. The SharePoint GRE restore view status displays incorrect characters for i18n Simple Chinese. The restore does recover the files names with the correct characters. When you perform a SharePoint granular backup on a federated farm, the bpfis child job gets a status 130 error on first attempt. The second attempt is successful. 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 database name field. To avoid this issue, make sure that you have an equal number of parenthesis that match in a database name.
76
A deleted list item that is in a Content-DB with Chinese characters may not restore to the original location. To resolve this issue, restore the item and any attachments that exist, to a file system and then add it to SharePoint. Restoring SharePoint picture libraries to the original location may fail when there are empty containers preceding the picture library. When there are no empty containers preceding the picture library, then the restore works. As a workaround, the data can be recovered by redirecting to a file system or restoring the sites content database. The SharePoint backup debug files are left in
INSTALL_DIR\VERITAS\NetBackup\Temp\
If the debug level is set to a value that is greater than 0 for databases, the SharePoint debug files on the backend are created during the backup in the INSTALL_DIR\VERITAS\NetBackup\Temp\ directory. These files are not removed after the backup. That is intentional behavior for debugging purposes. You can remove these files if you are low on space.
When you restore the most recent version of a document, picture, or attachment the restore works, however a status 5 error occurs. If you encounter this issue, you should know that the correct version of the item is restored and you can ignore the status 5 error.
SQL server agent

When you use the NetBackup for SQL Server user interface on 64-bit platforms, the online Help cannot be opened. This problem originates within the Windows 64-bit SDK and is expected to be resolved in a future release. Until then, open the help file directly using the Windows Explorer:
install_path\VERITAS\Help\nbmssql.chm
Sybase server agent

The following is a list of known operation notes that are pertinent to the NetBackup Sybase server agent:
With NetBackup 7.0, Sybase has changed its name from Adaptive Server Anywhere (ASA) to SQL Anywhere. In addition, the Windows service name has changed from ASANYs_VERITAS_NB to SQLANYs_VERITAS_NB. The Sybase service, dbsrv11, may cause a core dump to occur on a master or remote Enterprise media server that has Sybase 11.0.1 installed and IPv6 enabled. 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.
Operational Notes NetBackup Hyper-V
77
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 configuration file. 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 as LocalOnly=NO or LocalOnly=YES. You can locate the database server configuration file at the following locations: - On UNIX/Linux platforms: /usr/openv/var/global/server.conf (This is true as long as this file has not been moved to a different location.) - On Windows platforms:
install_path\NetBackupDB\CONF\server.conf
Start NetBackup.
About NetBackup Enterprise Vault Agent

The following list contains the known operation notes that are pertinent to the NetBackup Enterprise Vault Agent:
An Enterprise Vault backup passes as a partial success under a specific scenario. The partial success occurs when you use an EV_INDEX_LOCATION directive, and a policy with two Enterprise Vault servers that point to the same index location. If the NetBackup/logs/AltPath folder is not present, the Enterprise Vault redirected restore fails with a status 5 error. This folder must be present to perform a redirected restore.
NetBackup Hyper-V
The following items describe operational information for the NetBackup Hyper-V agent:
Use of a volume GUID path requires NetBackup patch 7.0.0.1 or later NetBackup 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}\
78
Operational Notes NetBackup interfaces
If volume GUID paths exist in your Hyper-V environment, you must install NetBackup patch 7.0.0.1 or a later release. Contact Symantec Technical Support to obtain the patch.
Data is restored to the Hyper-V server system drive if restore path is incorrectly specified (Windows only) When you restore selected files by means of a shared location on the virtual machine (using the Backup, Archive, and Restore interface on Windows), an incorrectly specified UNC path (share name) for the destination should cause the restore to fail, with status code 5. Instead, the files are restored to the system drive of the Hyper-V server. An example of an incorrect path is: \server_name\drive_name\directory_name (path has 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 the server name and drive name as specified in the UNC path. This issue will be fixed in a future NetBackup release, so that NetBackup fails the restore when a path is incorrectly specified.
Backup of Virtual Machines(VM) fails if the files that represent the VM have volume GUIDs instead of a drive letter in the pathname. For example, while the VM is created, if the path of one or more of the VHD files are specified with a 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 interfaces
The following subsections contain the release and operational information about the NetBackup interface, such as the NetBackup Administration Console, and the Activity Monitor.
NetBackup Administration Console for Windows

The following list contains the items that pertain to the NetBackup Administration Console for Windows:
When you log errors from a 6.5 media server, NetBackup stores the errors in the Media log. NetBackup also saves the errors into separate logs. That enables you to view specific error types such as tape errors in Tape log report or disk errors in the Disk log report.
79
However, if you attempt to log errors from a 6.0 media server, you can only view the errors in the Media log. NetBackup does not log the errors into separate error 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 protection reporting in this release of NetBackup:
Help for the Images On Disk report might not provide complete information at 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 the logged on host is a media server. These pages are applicable only for a master server.
NetBackup java interfaces

This section contains operational the notes that are applicable to NetBackup-java interfaces.
General Notes
The following list contains the general operational information that pertains to the NetBackup-Java Administration Console:
Reduced functionality (only the Backup, Archive, and Restore component available) or Cannot Connect errors during initialization of the NetBackup-Java Administration Console occurs if one or more of the NetBackup services or daemons on the host that is specified in the logon dialog is not running. The NetBackup-Java Administration console core dumps if you use Simplified Chinese UTF-8 locale on a Solaris SPARC 64-bit system with Solaris 10 Update 2 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 for more information about this issue. If you encounter this issue, apply the Solaris patch that Sun provides to fix this issue 6901233.
80
The Skip verification and force roll-back option does not appear in Restore Marked Files dialog. When you configure a Point in Time rollback restore, the Restore Marked Files dialog in the NetBackup-Java Administration console displays the Skip verification and force roll-back option as Overwrite existing files. The functionality of the Overwrite existing files option is the same as the Skip verification and force roll-back option, however the label is misleading. The names of these options will be corrected in a future release of NetBackup. The NetBackup-Java administration console on Windows (WDC) cannot connect to a UNIX master sever with a Japanese package. When you attempt to log on to the master server, the NetBackup-Java administration console hangs at a point when the following status statement appears.
Checking if NBAC is configured.
For more information about this issue and a workaround solution, refer to the following Technote on the Symantec Support Web site.
A Windows Manager that is configured for auto focus is not supported. Auto focus means that windows are activated (get the focus) when you position the mouse cursor over them. The following explains how to correctly set up a CDE environment. In the CDE environment, use the Style Manager -- Window dialog to change the window behavior to Click In Window To Make Active. NetBackup Java does not run properly if the Style Manager has the following selected: Point in Window To Make Active. If you are not set up properly to display to a machine from where you run jnbSA, one of the following happens:
Nothing, because it is probably displayed on the machine from where jnbSA was run. The command fails with no error message. (That means the operating system command prompt was received.
java.lang.InternalError: Cant 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 the machine where you intend to see the user interface and set the DISPLAY environment variable on the machine executing jnbSA before starting jnbSA. Reference the man page for the xhost command for additional capabilities.
81
Symantec recommends that only one administrator work on an object at a time. That eliminates the possibility of configuration conflicts if more than one administrator attempts administration tasks simultaneously on the same object. If this situation should occur, the last update that is made prevails. Memory requirements to run the NetBackup-Java Administration Console Symantec recommends that you run the console (jnbSA, jbpSA, or Java Windows Display Console) on a machine with at least 1 gigabyte of physical memory and 256 megabytes of memory available to the application. Remote display back of the NetBackup-Java Administration Console is not recommended. Symantec does not recommend running the NetBackup-Java Administration Console in a remote display back configuration. Problems have occurred with certain user interface controls (such as, incorrect box operations, very sluggish table scrolling with large numbers of rows, and table display problems with large numbers of rows). Other problems may occur that can cause the user interface to hang because of a Java Virtual Machine (JVM) failure. The JVM failures occur most often on AIX platforms. Therefore, Symantec recommends that you run the NetBackup-Java Administration Console on your local desktop to administer any NetBackup host (by specifying that remote host in the logon dialog of the user interface). The NetBackup-Java Administration 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 Java Administration Console option in the NetBackup Windows installation user interface. Refer to Chapter 2 (Platforms Supporting the NetBackup Administration Consoles for UNIX) of this document for the supported versions 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 logon dialog. The number varies depending on the tasks that you attempt in the console.
Remote display of the NetBackup-Java console in multi-byte locale environments is not supported.
82
Operational Notes About Symantec OpsCenter
Activity monitor
The following list shows the items that relate to the NetBackup Activity Monitor:
The ability to delete a large number of jobs When deleting a large number of jobs, do not leave the Activity Monitor node or close the NetBackup Administration Console while any of the deleted jobs are still visible in the Jobs tab. If the Activity Monitor is shut down while jobs are deleted, some of the jobs may not be deleted. The Activity Monitor can be shut down when you leave the Activity Monitor node or when you close the NetBackup Administration Console. The following message is displayed if you stop the bpdbm daemon on the relevant 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.
The reason this message occurs is that stopping the bpdbm daemon also stops the bpjobd process. Upon a successful startup of bpdbm (which starts bpjobd), you can use the refresh option on the toolbar to refresh the Activity Monitor job data. The refresh option is only available upon lost communications with the job daemon, bpjobd.
Storage unit configuration

The following list shows operational notes for the Storage Unit configuration:
The maximum fragment size of a disk storage unit has increased from 2 gigabytes to .5 terabytes. If a media server of a previous release has Disk Storage Units (DSUs) configured with a different maximum fragment size, the storage units are not automatically increased to the new default of 524,288 megabytes after an upgrade. To make the best use of the storage unit, consider increasing the fragment size on upgraded storage units. The bpstuadd command line option -dspath is no longer valid or supported.
About Symantec OpsCenter

The following list contains the items that relate to the Symantec OpsCenter feature:
If you plan to install OpsCenter on AIX, ensure that the XLC runtime version is 9.0 or greater.
Operational Notes NetBackup media and device management
83
After VBR upgrade, data is not displayed under Storage and Devices tabs After a VBR upgrade, data is not displayed under the Storage and Devices tabs in Monitoring. (Storage units, Robots, Drives, and so forth.) The data is not displayed as VBR does not collect any monitoring data, only the names are provided from the Job records. This data is collected after the upgrade as part of the regular data collection. An OpsCenter installation is not supported for the versions that are older than VBR 6.5. You cannot install OpsCenter on a system that has VBR installed with a version that 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 then upgrade 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 Reports performance declines as the data to be displayed in the report increases. For example, running a two-month report is slower than running a two-week report. After a reboot, the OpsCenter processes are not start automatically in AIX or SUSE Linux systems. Symantec recommends that you start the OpsCenter processes 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 user interface, the report that appears displays the wrong client name. Instead of showing the client names, a list of backed up VM images is displayed in this report. 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 or Remove Programs dialog box. If a rollback occurs during an uninstall of OpsCenter, the keys are not removed from Add or Remove Programs dialog box. You must remove OpsCenter. Use setup.exe to remove OpsCenter. After you reboot a SUSE 11 Server, and even though OpsCenter server services are 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 management

The following subsection contains the information that is pertinent to NetBackup media and device management functionality.
84
Operational Notes NetBackup media and device management
Media Sharing
The access control feature of Sun StorageTek ACSLS controlled robots is not currently compatible with Media Sharing. This feature restricts volume access using the requesting hosts IP address. Use caution when implementing Media Sharing in an ACSLS environment.
Enterprise Media Manager

The following list shows the operational note items that pertain to Enterprise Media Manager (EMM):
A new script, pending_request_notify, has been added to this version of NetBackup. The NetBackup Resource Manager calls the pending_request_notify script after a pending request is issued for a media resource (tape volume). To send an E-mail notification when a pending request is initiated, include an E-mail address in the script where indicated. (The root user must run this script.) Copy the script from the goodies directory into the bin directory on the EMM server (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
Into
Install_path\NetBackup\bin\
If the script exists in the bin directory, the following parameters are passed to the script: Media ID, barcode, action code, robot type, robot number, media server, 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 traced back to a volume on the array. The Media ID is an opaque string that has internal meaning to NetBackup, but to nothing else. In addition, the Media ID can be correlated to a volume by running nbdevquery -listmediaid command. SCSI persistent reserve NetBackup can use SCSI persistent reserve in and persistent reserve out to configure exclusive access protection to tape drives so that other host bus adaptors (HBAs) cannot control the drives during the reservation. SCSI persistent reserve provides more resiliency and fault tolerance than SPC-2
Operational Notes SAN Client and Fibre Transport
85
SCSI reserve and release, which is the default access protection method in NetBackup.
SAN Client and Fibre Transport

The following list contains the operational note information that pertains to SAN Client and Fiber Transport:
The NetBackup Client Encryption Option is not supported on UNIX and Linux SAN clients. The QLA-2344 four-port FC adapter's usable aggregate performance is not significantly greater than a two-port QLA-2342 when used in the same PCI-x slot for SAN Client target mode. The advantage a QLA-2344 HBA offers is the ability to spread its aggregate performance over four ports instead of two. If you use direct-connection (rather than FC switches or bridges) between SAN clients and a Fibre Transport (FT) media server and only two ports are fully loaded with Fibre Transport traffic at the same time, the QLA-2344 HBA performs similarly to two QLA-2342 HBAs but uses one less PCI slot. IBM 6228 HBAs require the following version of the AIX FC driver to ensure that the appropriate data is returned when a task is aborted. Not installing the following 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-bit NetBackup media servers, PCI-express, and PCI-X slots are supported for the QLogic Fibre Channel host bus adapters (HBAs) that are used to connect to the NetBackup SAN clients. Legacy PCI 33 and 66 Mhz slots are not supported. On the NetBackup media servers, Symantec recommends that you do not use legacy PCI cards on the same bus as a QLogic FC HBA that is used to connect to SAN clients. A slower PCI card reduces the speed of the controlling bus and therefore all other cards in that bus. Consequently, data transfer rates are reduced and performance is degraded. If you use data compression or encryption for backups, backup, and restore Fibre Transport pipe performance may degrade significantly. In some configurations, compression may reduce performance by up to 95% of uncompressed 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.
86
Operational Notes SharedDisk support in NetBackup 7.0 and later
SharedDisk support in NetBackup 7.0 and later

The SharedDisk option is not supported beginning with the NetBackup 7.0 release. You can use a NetBackup 7.0 master server to configure, manage, and operate SharedDisk on NetBackup 6.5 media servers. For information about using SharedDisk, see the documentation for your NetBackup 6.5 release.
NetBackup AdvancedDisk option

NetBackup does not support clustering of AdvancedDisk media servers.
NetBackup Client Deduplication

The following items pertain to NetBackup 7.0 Client Deduplication:

NetBackup 7.0 Client Deduplication does not support multiple copies. NetBackup 7.0 Client Deduplication does not support encryption.
About the NetBackup Media Server Deduplication Option

The following items pertain to the NetBackup Media Server Deduplication Option:
On UNIX and Linux systems on which a deduplication storage server is not configured, the netbackup start script returns status 2. The status 2 indicates that the script cannot start the deduplication daemons. Because a storage server is not configured, the daemons cannot be started. The error is spurious; you can ignore it. For the Microsoft Exchange backups that use the NetBackup Exchange Agent, deduplication rates are low even though data has not changed since the last backup. NetBackup does not support clustering of deduplication storage servers or load balancing servers. The NetBackup Media Server Deduplication Option does not support NFS mounted file systems. Therefore, do not enter an NFS file system when you configure the data storage path. Symantec expects Oracle database stream-based backups to achieve low deduplication rates. Stream-based backups include deduplication within a
Operational Notes PureDisk Deduplication Option (PDDO)
87
single backup and deduplication between a backup and data already backed up. However, Snapshot Client backups of Oracle databases achieve high deduplication rates across full backups within our test environments. Oracle Snapshot Client based backups have higher deduplication because the data is aligned on consistent file or tablespace boundary.
NetBackup does not support the Snapshot Client off-host method Media Server Copy on NetBackup clients that deduplicate their own data.
PureDisk Deduplication Option (PDDO)

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

The following items pertain to the NetBackup Snapshot Client :
NetBackup does not support creating a disk array snapshot if a VxVM disk group on the array contains a software-based snapshot of the VxVM volume. If a software-based snapshot (such as from the VxVM method) already exists of a VxVM volume on the disk array, NetBackup cannot create a disk array snapshot of a file system that is configured on the VxVM volume. Snapshot creation fails (with final status 156), and the bpfis log contains a message that reports a vxmake command failure. You must delete the existing VxVM snapshot from the VxVM disk group before you run a backup with a disk array snapshot method. This issue will be fixed in a future release of NetBackup. Examples of disk array snapshot methods are EMC_CLARiiON_SnapView_Snapshot, HP_EVA_Snapshot, Hitachi_CopyOnWrite, and IBM_StorageManager_FlashCopy. All disk array methods are described in the NetBackup Snapshot Client Administrator's Guide, in the chapter titled "Configuration of snapshot methods for disk arrays."
Instant Recovery restores may fail from a backup that a FlashSnap off-host backup policy made. From a policy that was configured with the FlashSnap off-host backup method and with Retain snapshots for Instant Recovery enabled, the backups that were made at different times may create snapshot disk groups with the same name. 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 snapshots that have expired and been deleted. It appears that you can browse the expired
88
Operational Notes NetBackup Snapshot Client
snapshots and restore files from them. But the snapshots no longer exist, and the restore fails with status 5.
For this release, NetBackup does not support Snapshot Client VSS off-host file backups using a Storage Foundation for Windows (SFW) VSS provider. NetBackup does not support the Snapshot Client off-host method media server Copy on NetBackup clients that deduplicate their own data. The following list of items pertain to restoring individual files from an Instant Recovery snapshot:
When you restore files from a snapshot that is made for an Instant Recovery off-host alternate client backup: NetBackup consults the exclude list on the alternate client even when it restores files to the primary client. If the exclude list on the alternate client is different from the exclude list on the primary client, any files that are listed in the exclude list on the alternate client are not restored to the primary client. For example, if the alternate client's exclude list has the entry *.jpg, and some .jpg files were included in the primary client backup, the .jpg files can be selected for the restore but are not in fact restored. To restore the files, you must change the exclude list on the alternate client. When you restore files from a snapshot that is made for an Instant Recovery backup (local or off-host alternate client): If the exclude list is changed after the backup occurred, NetBackup honors the latest version of the exclude list during the restore. Any of the files that are listed in the current exclude list are not restored. Also, as noted in the previous item, the exclude list on the alternate client takes precedence over the exclude list on the primary client. For example: If the current version of the exclude list has the entry *.jpg, and some .jpg files were included in the backup, the .jpg files can be selected for the restore but are not in fact restored. To restore the files, you must change the exclude list on the primary (or alternate) client. Note: For ordinary backups (not based on snapshots), any files that were included in the exclude list are not backed up. For snapshot-based backups, however, all files are included in the snapshot. The exclude list is consulted only when a storage unit backup is created from the snapshot. If the snapshot is retained after the backup (for the Instant Recovery feature) and the snapshot is available at the time of the restore, NetBackup restores files from the snapshot. Since all files are available in the snapshot (including those that would be excluded from a storage unit backup), NetBackup incorrectly consults the current exclude list on the client or alternate client. Any files in the exclude list are skipped during the restore.
Operational Notes NetBackup commands and utilities
89
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 Instant Recovery backup, the primary file system is verified against the snapshot to make sure that no new files were created on the primary file system after the snapshot was taken. Note that a rollback deletes all files that were created after the creation-date of the snapshot that you restore. Rollback returns a file system or volume to a given point in time. Any data changes or snapshots that were made in the primary file system after that time are lost as a result of the rollback. However, during the verify operation for the rollback, the snapshot is mounted and in some cases, the snapshot cannot be unmounted. In that case, the Point in Time Rollback operation is aborted. Note: For a rollback of a database backup such as Oracle, the file system verification is mandatory and this issue prevents a successful rollback. For a rollback of a file system, you can skip file verification by selecting "Skip verification and force rollback" on the restore dialog. The problem that is described here is avoided and the rollback succeeds. Caution: Use Skip verification and force rollback only if you are sure that you want to replace all the files in the original location with the snapshot. Rollback deletes all files that were created after the creation-date of the snapshot that you restore. See "Instant Recovery: point in time rollback" in the NetBackup Snapshot Client Administrator's Guide for more information on rollback.
NetBackup commands and utilities

This release of NetBackup contains new commands and utilities. For a description of 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
90
Operational Notes NetBackup OpenStorage Option
This command produces a status report on NetBackup client images or removable 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 designated destination.
nbkmsutil
This command runs the NetBackup Key Management Service utility.
nbregopsc
You use this command to register OpsCenter.
bptestnetconn
This command test and analyzes various NetBackup configurations and connections. The support and support.exe diagnostic information gathering utilities are no longer included or supported beginning with this release of NetBackup.
NetBackup OpenStorage Option

The following list contains the operational note information that pertains to NetBackup OpenStorage option:
The NetBackup OpenStorage Options does not support clustering of the media servers that function as data movers. NetBackup performs optimized duplication until it encounters an image for which optimized duplication is not possible. For that image and all subsequent images, NetBackup performs a regular duplication. NetBackup uses the fragment size setting of the source storage unit, not the setting of the destination storage unit. NetBackup copies the image fragments as is (that is, NetBackup does not resize or rearrange the backup image into a different 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 NetBackup 7.0, you also must update the vendor plug-in to a 64-bit version.
Operational Notes NetBackup Disk Storage units
91
NetBackup Disk Storage units

The following list contains the operational information that pertains to the Disk storage unit:
Upon NetBackup installation or upgrade, the nb_updatedssu command runs. The command deletes the .ds files that were used in the previous releases as pointers to the relocated data. Relocated data is tracked differently in the current release and the .ds files, are converted to the new tracking mechanism. Under some circumstances, a .ds file may not be deleted upon installation or upgrade. If that occurs, Symantec recommends that you run the command again 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 compute the amount of "potential free space" on a volume, you now need to use a different command. You can use the following command, to display the potential 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 unit dialog that is shown in the 7.0 user interface. A pop-up window appears and contains the following message:
CORBA::BAD Param.
NetBackup Vault
The following list contains the operational notes that pertain to NetBackup Vault:
Enhancements have been made that enables a nonroot NBU_Admin or Vault operator to perform the tasks that they otherwise would not be able to perform because of permission problems. These enhancements specifically target a system where NBAC is configured and the Vault service manages the important read-write data. For example, these enhancements have the following effect on users who have upgraded from previous versions to NetBackup 7.0:
If pre-NetBackup 7.0 sessions are not processed completely before an upgrade, Symantec recommends that you process all these sessions (meaning that you complete all ejects and reports) before you upgrade to ensure minimal affect. At a minimum, you should copy the summary.log
92
Operational Notes NetBackup Vault
from the sidxxx directory to a new sidxxx/logs directory to accommodate eject/reports eligible sessions.
The presence of the VLT_CREATE_SESSION_DEBUG_FILES touch file has no affect on the new session permissions. The permissions of pre-NetBackup 7.0 session directories are not modified. You may need to update the notify scripts appropriately with respect to the directory structure changes. For example, the summary.log is now written to sidxxx/logs directory. If you upgrade to NetBackup 7.0 and decide to downgrade to a pre-NetBackup 7.0 version, you must make sure that you account for the enhancements that were packaged in NetBackup 7.0. For example, log files are written to sidxxx/logs, and files and folders have restrictive permissions when they are created.
Vault Operator Access on UNIX. If you do not configure NetBackup Access Control, you can still set permissions on UNIX systems so that non-root users can use the operational commands in the Vault Operator Menu to inject and eject tapes and generate reports. The most efficient way to accomplish that is to add the users to whom you want to grant access to a single user group, then give that group permission to execute some of the executable files. Giving users access to the Vault Operator Menu also gives them the capability to change report destinations. If you do not want non-root users to view reports and change report destinations, do not give them access to the Vault Operator Menu. For example, you may not want non-root users to see the Recovery Report or to be able to change to whom reports are e-mailed. In addition, giving users special privileges may violate your organizations computer and network security policies and allow access to private information. Check with your system administration or computer security staff to ensure that you do not violate security policies.
Create a UNIX group and add the appropriate users to this group. This group is referred to as opsgroup in the following commands. Log on to the system on which the NetBackup master server is installed and 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
Operational Notes NetBackup for VMware
93
# 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 that control 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 server and modify the .rhosts file in the home directory of user acsss. The NetBackup installation process should have added an entry to the .rhosts file for the NetBackup master server that grants root access. Modify that entry to allow all users in the opsgroup access to the Sun StorageTek ACSLS server as user acsss:
master_server_name root <user1> <user2> . . . <userx>
If you use Sun StorageTek ACSLS for robotic control, verify that the user accounts defined for the operations group exist on both the system on which the NetBackup master server is installed and on which the Sun StorageTek ACSLS server is installed. For simplicity, each user should have the same user ID on both servers. If both servers use a naming service (such as NIS), you can skip this step. To verify the proper operation, log on as a non-root user on the NetBackup master server system. Start vltopmenu and execute each menu option.
NetBackup for VMware

The following operational notes pertain to NetBackup's VMware feature:
VMware with PureDisk deduplication For a VMware backup to a PureDisk Deduplication Embedded (PDDE) storage unit, select the Mapped full VM backup option for the Virtual machine backup parameter on the VMware snapshot method. This option provides the best deduplication rates. Use of the Full VM backup option results in a lower rate of deduplication.
94
The Mapped full VM backup option does not work with the hotadd transport type if the virtual machine that contains the backup host is a clone of the virtual machine that is backed up (or vice versa). If the VMware backup host is in a virtual machine, and that virtual machine is a clone of the virtual machine that you backed up, a backup that uses the hotadd transfer type may appear to succeed. However, some of the virtual machine volumes may be incorrectly mapped and cannot be restored. The converse is also true. The virtual machine that you back up with the hotadd transport type cannot be a clone of the virtual machine that contains the backup host. Furthermore, the two virtual machines must not be clones of the same parent. VMware has identified this issue as software defect SR#1442259141. If you want to use the hotadd transport type with your backup, do the following. Make sure the virtual machine that contains the VMware backup host and the virtual machine you back up are not clones of each other. NetBackup for VMware does not support backing up virtual machine RAID 5 volumes with the SAN transfer type. If a virtual machine containing a RAID 5 volume was backed up with VMware vStorage services (not VCB) using the SAN transfer type, the RAID 5 volume may not be correctly restored. 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 ESX server that has fewer network interfaces, some of the virtual machine's network interfaces are not restored. This issue occurs when NetBackup 7.0 performs a restore with the VMware vStorage infrastructure services. This issue will be addressed in a future release of NetBackup. As a workaround, you can configure additional network interfaces on the destination ESX server before you run the restore. Make sure that the network connections are correctly identified and selected on the NetBackup "network connections " Restore dialog. That ensures all of the virtual machine's original network adapters are restored when the virtual machine is restored. VMware virtual machine does not reboot after restore If a virtual machine was configured with SCSI and IDE drives at the time of backup, and the guest OS resided on a SCSI drive, the virtual machine when restored may attempt to boot from the IDE drive. In that case, the boot attempt fails with the message "Operating system not found." This problem occurs when NetBackup uses the VMware vStorage integration services. VMware has identified this problem and will address it in a future release. As a workaround, you can reconfigure the BIOS on the virtual machine to boot from the correct SCSI disk.
95
The restore of a virtual machine fails when you use the hotadd transport mode if the VMware backup host is on a Windows 2008 virtual machine. Because of a VMware issue (SR#1438908741), restoring the virtual machine by means of the hotadd transfer type may fail if you have installed the VMware backup host in a virtual machine in a Windows Server 2008 guest operating system. The detailed status log on the NetBackup Activity Monitor includes the message, Virtual machine restore: file write failed. The final job status 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 virtual machine to use the hotadd transfer type for the restore. If the backup host is in a Windows 2008 virtual machine, 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 also excluded from the virtual machines. To avoid this issue, make sure that you do not exclude drives on proxy clients when you perform a VCB backup. Restoring a virtual machine through a vCenter Server may be slow when using the SAN transfer type When you use the SAN transfer type to restore a virtual machine, the restore job may be slow if you restore to a vCenter Server. To speed up the restore, restore the virtual machine directly to an ESX server. When the NetBackup-Java Administration Console is used to restore a VMware virtual machine that was backed up with the block level incremental backup feature (BLIB), only the most recent BLIB backup of that virtual machine can be restored. If you try to restore an earlier backup made from the same policy, the restore fails. To restore from previous BLIB backups of the virtual machine, use the Backup, Archive, and Restore interface on Windows. (ET2086326) For hotadd backup or restore, the virtual machine and the hotadd backup host must reside on the same VMware datacenter To back up a virtual machine by means of the hotadd transfer type, the VMware backup host must be installed in a virtual machine. VMware requires that the virtual machine to back up and the virtual machine that contains the hotadd backup host reside in the same VMware datacenter. Otherwise, the hotadd backup fails with NetBackup status 6. The job details log contains the message unable to open disk error(23). The same VMware restriction applies to virtual machine restore: The virtual machine to restore and the virtual machine that contains the hotadd restore host must reside in the same VMware datacenter. Otherwise, the hotadd restore fails with NetBackup status 5. For hotadd backup or restore, Symantec recommends at least one hotadd backup or restore host for each datacenter.
96
Chapter
End of Life Notifications


End of life notifications About features, enhancements, and commands no longer supported
End of life notifications

This section contains information about the features, platforms, and devices that will no longer be supported in future releases of NetBackup. These notifications encompass NetBackup commands, files, directories, utilities, tools, robots and devices, and terminology.
About general NetBackup notifications

The following is a list of general NetBackup end-of-life notifications that affect future releases of NetBackup:
In the next major release after 7.0, support for all of the active and the passive media server clusters that use the NetBackup clustering agents is withdrawn. The NAS SnapVault Option is not offered for sale with new NetBackup 7.0 environments. However, it continues to be a supported option with NetBackup 6.5 license keys for the remaining support life of 6.5. If you are a current NAS SnapVault Option user and intend to upgrade to NetBackup 7.0, you can continue to use the NAS SnapVault Option and the following applies:
SnapVault can no longer be purchased and you cannot enable it with the NetBackup 7.0 license keys. To continue to use SnapVault on 7.0, you must use your NetBackup 6.5 license keys that enable SnapVault. The NetBackup 6.5 SKU for the NAS
98
End of Life Notifications About features, enhancements, and commands no longer supported
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-Java Administration Console is no longer supported. Backup Exec Tape Reader (BETR) refers to the ability within NetBackup to import and restore from Backup Exec (BE) backup sets (images). As of the next major release, NetBackup, BETR is no longer supported. At the next major release of NetBackup, the NetWare client is no longer supported.
About features, enhancements, and commands no longer supported

Changes to how Symantec supports NetBackup features may directly affect you. Symantec is committed to notifying you of these changes at least one major release before support is discontinued. In some instances, notification was already announced and this document confirms that support has been removed. The following sections describe those features, enhancements, or commands that are no longer supported as of this release of NetBackup. Items within these sections were previously announced in earlier releases of NetBackup providing a warning to users that specific changes were forthcoming.
About general NetBackup features no longer supported

The following list contains general NetBackup features that are no longer supported:
NetBackup no longer supports the Veritas Storage Migrator (VSM) product. Veritas Storage Migrator (VSM) 6.5 is the final release of the product and is not supported in NetBackup 7.0. However, VSM is supported for the life of NetBackup 6.5 and all of the NetBackup 6.5 release updates. That means that only NetBackup 6.5 GA and 6.5.x media servers support VSM media and this version of NetBackup Vault manages those media. Starting with the next major release of NetBackup, NetBackup Vault no longer supports VSM media eject and report functionality. FAT file systems are not supported for Windows server (x86 and x64) systems. The SharedDisk option is not supported beginning with the NetBackup 7.0 release. You can use a NetBackup 7.0 master server to configure, manage, and operate SharedDisk on NetBackup 6.5 media servers.
99
For information about using SharedDisk, see the documentation for your NetBackup 6.5 release.

NetBackup no longer supports the NetWare Media Server Option. The set_ndmp_attr file no longer exists in NetBackup. Starting with this release of NetBackup, the functionality that is found in set_ndmp_attr only exists in tpconfig. The VERITAS Snapshot Provider (VSP), for open and active files on NetBackup pre-7.0 Windows clients, is no longer supported in NetBackup 7.0. Note: For 7.0 clients, NetBackup automatically uses VSS instead of VSP. Beginning with this release, you can no longer use the "cold" ("offline") catalog backup method. This backup method was deprecated from NetBackup and is no longer be supported. The Snapshot Client does not support Storage Foundation 3.x versions with the exception of the OnlineJFS version 3.5MP1 on an HP-UX 11.11 system. Symantec no longer provides the Windows tape device Installer or Windows Tape Drivers. Cold Catalog Backup has been dropped from NetBackup 7.0. Starting with this release of NetBackup, the NetBackup binaries for AIX, HP9000 PA-RISC, Solaris SPARC, and Linux x86 systems are now built as 64-bit binaries only. If you have a computer that can run a 32- or 64-bit operating system, and you start 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 not install. The NetBackup Operations Manager (NOM) product has been replaced with the new OpsCenter feature. Starting with this release, NetBackup has merged two help sets into one. That means that the jnbSA help set has been eliminated and the jbpSA help set remains. NetBackup 7.0 does not support SGI IRIX and Tru64 platforms.
About database functions no longer supported

The following describes the functionality within the NetBackup database agents that are no longer supported, beginning with this release of NetBackup:
100
NetBackup for Microsoft SharePoint Portal Notifications NetBackup 7.0 no longer supports SharePoint Portal Server 2001 backup and recovery. NetBackup for Microsoft SQL Notifications NetBackup no longer supports SQL Server 7.0 backup and recovery. NetBackup for Microsoft Exchange Server NetBackup 7.0 no longer supports Exchange 5.5 or Exchange 2000 backup and recovery.
About NetBackup commands no longer supported

The commands in the following list are no longer supported with this release of NetBackup:

bpmoverinfo nbnos bpSALinfo nbpushdata nbshareddisk tshd odld set_ndmp_attr tpformat bpuser bpauthsync
Enhanced Authentication (noauth authentication methods) and Enhanced Authorization are no longer supported. The last release of the FSAnalyzer was NetBackup 6.5. The FSAnalyzer is no longer 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. A new utility, nbsu, introduced in NetBackup 6.5 replaced these utilities.
Chapter
Related Documents

About related NetBackup documents About NetBackup release notes About getting started guides About installation guides About administrators guides - agents and options About users guides About the device configuration guide About the Troubleshooting guide About NetBackup command documents
About related NetBackup documents

This 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 in Adobe Portable Document Format (PDF). The PDF files are either in the root directory or the Doc directory on the disk. To view the PDF copies of the manuals, you need an Adobe Acrobat reader. You can download a copy of this product from the Adobe Web site at the following URL: http://www.adobe.com Symantec assumes no responsibility for the correct installation or use of the reader.
102
Related Documents About NetBackup release notes
About NetBackup release notes

The following release notes documents were released with this version of NetBackup.
Symantec NetBackup Release Notes for UNIX, Linux, and Windows NetBackup_Release_Notes.pdf This document contains information about NetBackup on UNIX- and Windows-based servers, such as the platforms and operating systems that are supported. It also contains any operating notes that may not be in the NetBackup manuals or the online Help .
About getting started guides

The following getting started guides were released with this version of NetBackup.
Symantec NetBackup Getting Started Guide for UNIX, Linux, and Windows NetBackup_GettingStarted_Guide.pdf Provides a high-level description of the latest NetBackup release. This document also contains the information that explains the content of the NetBackup media kit. Symantec NetBackup Backup, Archive, and Restore Getting Started Guide NetBackup_BAR_GS_Guide.pdf Explains how to use the NetBackup Backup, Archive, and Restore interface to perform backup and restore operations for UNIX, Windows, and Linux systems.
About installation guides

The following Installation documents were released with this version of NetBackup.
Symantec NetBackup Installation Guide for UNIX NetBackup_Install_UNIX.pdf Explains how to install NetBackup software on UNIX-based platforms. Symantec NetBackup Installation Guide for Windows NetBackup_Install_Win.pdf Explains how to install NetBackup software on Windows-based platforms. Symantec NetBackup LiveUpdate Guide NetBackup_LiveUpdate_Guide.pdf This guide explains a feature that provides a cross-platform, policy-driven method to distribute NetBackup Release Updates to NetBackup hosts at version 6.5 and later.
Related Documents About administrators guides - agents and options
103
About administrators guides - agents and options

The following administrator guides for NetBackup database agents and options were released with this version of NetBackup.
Symantec NetBackup Deduplication Guide NetBackup_Dedupe_Guide.pdf Explains how to configure and use NetBackup media server deduplication and NetBackup client deduplication. Symantec NetBackup SAN Client and Fibre Transport Guide NetBackup_SANClient_Guide.pdf Explains how to configure and use NetBackup SAN Client and Fibre Transport for high-speed backups of important clients. Symantec NetBackup Shared Storage Guide NetBackup_SharedStorage_Guide.pdf Explains how to configure and use shared storage in NetBackup. Shared storage includes AdvancedDisk, OpenStorage, and the Shared Storage Option. Symantec OpsCenter Administrator's Guide NetBackup_AdminGuide_OpsCenter.pdf Explains the Web-based software application that helps organizations. It provides visibility into their data protection environment. OpsCenter is a combination of the two Symantec products namely NetBackup Operations Manager (NOM) 6.5.4 and Veritas Backup Reporter (VBR) 6.6. Symantec NetBackup Enterprise Vault Agent Administrator's Guide for Windows NetBackup_AdminGuide_EntVault.pdf Explains how to install, configure, and use the Enterprise Vault Agent so you can protect Enterprise Vault configuration information and data that Enterprise Vault has archived. Symantec NetBackup Snapshot Client Administrators Guide NetBackup_AdminGuide_SnapshotClient.pdf This guide explains how to install, configure, and use Symantec NetBackup Snapshot Client. It combines the features of snapshot backup, FlashBackup, BLI Agent, off-host backup , and Instant Recovery. Symantec NetBackup Snapshot Client Quick Start Guide NetBackup_QuickStart_SnapshotClient.pdf Provides the first-time instructions for installing and configuring the Snapshot Client. Symantec NetBackup for Hyper-V Guide for UNIX, Windows, and Linux NetBackup_AdminGuide_Hyper-V.pdf
104
NetBackup for Hyper-V provides snapshot-based backup of the virtual machines that run on Windows 2008 Hyper-V servers.
Symantec NetBackup for VMware Administrator's Guide for UNIX, Windows, and Linux NetBackup_AdminGuide_VMware.pdf Provides backup and restore of the VMware virtual machines that run on VMware ESX servers. Symantec NetBackup for DB2 Administrators Guide for UNIX NetBackup_AdminGuide_DB2_Unix.pdf Explains how to install, configure, and use NetBackup for DB2. Symantec NetBackup for DB2 Administrators Guide for Windows NetBackup_AdminGuide_DB2_Win.pdf Explains how to install, configure, and use NetBackup for DB2. Symantec NetBackup for Informix Administrators Guide NetBackup_AdminGuide_Informix.pdf Explains how to install, configure, and use NetBackup for Informix to back up and restore the Informix databases that are on a UNIX NetBackup client. Symantec NetBackup for Lotus Notes Administrators Guide for Windows NetBackup_AdminGuide_LotusNotes_Win.pdf Explains how to install, configure, and use NetBackup for Lotus Notes to back up and restore Lotus Notes databases and transaction logs on a Windows client. Symantec NetBackup for Lotus Notes Administrators Guide for UNIX NetBackup_AdminGuide_LotusNotes_Unix.pdf Explains how to install, configure, and use NetBackup for Lotus Notes to back up and restore Lotus Notes databases and transaction logs on a UNIX client. Symantec NetBackup for Microsoft Exchange Server Administrators Guide NetBackup_AdminGuide_MSExchg_Win.pdf Explains how to configure and use NetBackup for Microsoft Exchange Server to perform online backups and restores of Microsoft Exchange Server. Symantec NetBackup for Microsoft SQL Server Administrators Guide for Windows NetBackup_AdminGuide_MSSQL_Win.pdf Explains how to install, configure, and use NetBackup for Microsoft SQL Server to back up and restore Microsoft SQL Server databases and transaction logs. Symantec NetBackup for NDMP Administrators Guide NetBackup_AdminGuide_NDMP.pdf Explains how to install, configure, and use NetBackup for NDMP to control backups on an NDMP host.
105
Symantec NetBackup for Oracle Administrators Guide for UNIX NetBackup_AdminGuide_Oracle_Unix.pdf Explains how to install, configure, and use NetBackup for Oracle to back up and restore the Oracle databases that are on a UNIX NetBackup client. Symantec NetBackup for Oracle Administrators Guide for Windows NetBackup_AdminGuide_Oracle_Win.pdf Explains how to install, configure, and use NetBackup for Microsoft Oracle to back up and restore the Oracle databases that are on a Windows NetBackup Client. Symantec NetBackup for SAP Administrators Guide for UNIX NetBackup_AdminGuide_SAP_Unix.pdf Explains how to install, configure, and use NetBackup for SAP on UNIX. Symantec NetBackup for SAP Administrators Guide for Windows NetBackup_AdminGuide_SAP_Win.pdf Explains how to install, configure, and use NetBackup for SAP on Windows-based servers. Symantec NetBackup for Microsoft SharePoint Server Administrators Guide for Windows NetBackup_AdminGuide_SharePoint.pdf Explains how to install, configure, and use NetBackup for SharePoint Portal Server 2003 to back up and restore the Sybase databases that are on a Windows NetBackup client. Symantec NetBackup for SYBASE Administrators Guide for UNIX NetBackup_AdminGuide_Sybase_Unix.pdf Explains how to install, configure, and use NetBackup for Sybase to back up and restore Sybase databases that are on a UNIX NetBackup client. Symantec NetBackup for SYBASE Administrators Guide on Windows NetBackup_AdminGuide_Sybase_Win.pdf Explains how to install, configure, and use NetBackup for Sybase to back up and restore Sybase databases that are on a Windows NetBackup client. Symantec NetBackup High Availability Administrators Guide NetBackup_AdminGuide_HighAvailability.pdf This guide provides information on how to install and configure NetBackup to work with different clustering solutions. Symantec NetBackup Bare Metal Restore Administrator's Guide NetBackup_AdminGuide_BMR.pdf Describes how to install, configure, and use Bare Metal Restore to protect and restore client systems. For UNIX, Windows, and Linux.
106
Related Documents About users guides
Symantec NetBackup Vault Administrator's Guide NetBackup_AdminGuide_Vault.pdf Describes how to install, configure, and use logical vaults and profiles to duplicate backups, perform catalog backups, eject media, and generate reports. For UNIX, Windows, and Linux. Symantec NetBackup NetWare Media Server Option Administrators Guide for UNIX and Windows NetBackup_AdminGuide_NetWareServer.pdf This comprehensive manual provides detailed information and procedures for installing, configuring, and using the Symantec NetBackup NetWare Media Server Option.
About users guides

The following user guides were released with this version of NetBackup.
Symantec NetBackup Vault Operator's Guide NetBackup_OperGuide_Vault.pdf Describes the procedures for sending tapes off site, receiving tapes on site, and running reports on off-site media and vault jobs. For UNIX, Windows, and Linux. Symantec NetBackup Administrator's Guide for Novell NetWare Client NetBackup_AdminGuide_NetWare_Client.pdf Explains how to install and use the NetBackups NetWare Client software. With the NetWare Client, full and incremental backups can be scheduled to occur automatically and unattended under the control of the NetBackup master server. The NetWare Client also provides two methods for performing user-directed backups and restores: Target, which uses a character-based, menu-driven interface running on the NetWare server, and NonTarget, which uses the NetBackup for NetWare NonTarget Browser that is installed and run from a Windows computer.
About the device configuration guide

The following device configuration guide was released with this version of NetBackup.
Symantec NetBackup Device Configuration Guide NetBackup_DeviceConfig_Guide.pdf Explains how to add device drivers and perform other system-level configurations for the operating systems of NetBackup servers that host storage
Related Documents About the Troubleshooting guide
107
devices. Also includes information about configuring several types of tape libraries.
About the Troubleshooting guide

The following troubleshooting guide was released with this version of NetBackup.
Symantec NetBackup Troubleshooting Guide for UNIX and Windows NetBackup_Troubleshoot_Guide.pdf Provides troubleshooting information for UNIX- and Windows-based NetBackup products, including Media Manager.
About NetBackup command documents

The following command documents were released with this version of NetBackup.
Symantec NetBackup Commands for UNIX, Windows, and Linux NetBackup_Commands.pdf Describes the NetBackup and Media Manager commands and the processes that you can run from a UNIX command line or a Windows command prompt.
108
Related Documents About NetBackup command documents
Appendix
Windows Logo Certification information

This appendix includes the following topics:
About Windows Server 2008 R2 Logo Certification
About Windows Server 2008 R2 Logo Certification

This topic contains information about Windows Server 2008 R2 Logo Certification and how it applies to NetBackup. The tables contain the following types of information:
Files that have invalid file version information (Company, Product Name, and Product Version) See Table A-1 for a list of these files. Third-party files and tools that do not include or create requested ExecutionLevel tags See Table A-2 for a list of these files and tools. Files that NetBackup uses that are not signed See Table A-3 for a list of these files. Files that remain after an uninstall The NetBackup uninstall may leave files behind that other Symantec applications use. NetBackup 7.0 uses Veritas Authentication (VxAT) as a common security infrastructure that is shared between applications on the same host. For example, Veritas Storage Foundation (VxFS) and NetBackup can reside on the same host. If you uninstall NetBackup from a Windows Server 2008 R2 host and remove the VxAT files in the common directory, then the remaining application ceases
110
Windows Logo Certification information About Windows Server 2008 R2 Logo Certification
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 file version information File names
pxhpinst.exe
Third-party file locations

Third-party files located in Program Files\Veritas\NetBackup\bin
pxsetup.exe vxblock.dll Third-party files located in of Program Files\Common Files\VERITAS\VxMS\shared\VDDK diskLibPlugin.dll
gvmomi.dll libcurl.dll libeay32.dll liblber.dll libldap.dll libldap_r.dll libxml2.dll ssleay32.dll types.dll zlib1.dll Third-party files located in any of the following paths: _int.dll

Program Files\Veritas\pdde Program Files\Veritas\pdde\pddb\bin Program Files\Veritas\pdde\pddb\lib adminpack.dll ascii_and_mic.dll
111
Table A-1
NetBackup installs the following files that do not have valid file version information (continued) File names
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
112
Table A-1
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
113
Table A-1
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
114
Table A-1
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 not include or create requested ExecutionLevel tags File names
java.exe

Third-party files located in Program Files\Veritas\NetBackupDB\java
javaw.exe keytool.exe policytool.exe rmid.exe rmiregistry.exe tnameserv.exe Third-party files located in Program Files\Veritas\NetBackup\bin pxhpinst.exe
pxsetup.exe uconv.exe Third-party files located in any of the following paths: clusterdb.exe

Program Files\Veritas\pdde Program Files\Veritas\pdde\pddb\bin Program Files\Veritas\pdde\pddb\lib createdb.exe
115
Table A-2
NetBackup uses the following third-party files and tools that do not include or create requested ExecutionLevel tags (continued) File names
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
116
Table A-2
NetBackup uses the following third-party files and tools that do not include or create requested ExecutionLevel tags (continued) File names
vacuumlo.exe zic.exe
Table A-3
NetBackup uses and installs the following files that are not signed. File names
awt.dll

Third-party files located in Program Files\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
117
Table A-3
NetBackup uses and installs the following files that are not signed. (continued) File names
rmid.exe rmiregistry.exe tnameserv.exe verify.dll zip.dll
The following Microsoft runtime libraries
mfc*.dll msvc*.dll
Third-party files located in Program Files\Veritas\NetBackup\bin\x86
PrimoSDK.dll
px.dll pxdrv.dll pxhpinst.exe pxmas.dll pxsetup.exe pxwave.dll vxblock.dll Third-party files located in Program Files\Veritas\NetBackup\bin diskLibPlugin.dll
glib-2.0.dll gobject-2.0.dll gthread-2.0.dll gvmomi.dll iconv.dll intl.dll
118
Table A-3
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
Third-party files located in any of the following paths: _int.dll

Program Files\Veritas\pdde Program Files\Veritas\pdde\pddb\bin Program Files\Veritas\pdde\pddb\lib adminpack.dll ascii_and_mic.dll autoinc.dll btree_gist.dll chkpass.dll clusterdb.exe comerr32.dll
119
Table A-3
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
120
Table A-3
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
121
Table A-3
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
122
Table A-3
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
123
Table A-3
utf8_and_uhc.dll utf8_and_win.dll uuid-ossp.dll vacuumdb.exe vacuumlo.exe zic.exe zlib1.dll
Table A-4 File locations
Files that remain after NetBackup is uninstalled Files

Authentication SessionStore.lock
C:\Program Files\Veritas\Security\ C:\Program Files\Veritas\Security\systemprofile\
VRTSatlocal.conf CRTSatlocal.conf.lock C:\Program CertStore.lock Files\Veritas\Security\systemprofile\certstore\ C:\Program KeyStore.lock Files\Veritas\Security\systemprofile\certstore\keystore\ SessionEncrKey.pem SessionHMACKey.pem C:\Program default.db Files\Veritas\Security\systemprofile\sessions\ log.0000000001 sdefault.db __db.001
124
Table A-4 File locations
Files that remain after NetBackup is uninstalled (continued) Files

__db.002 __db.003 __db.004 __db.005 __db.006 __db.register
C:\Program CertStore.lock Files\Veritas\Security\systemprofile\systruststore\

NetBackup Release Notes 1-1

Încărcat de

Informații document

Descriere originală:

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

NetBackup Release Notes 1-1

Încărcat de

Drepturi de autor:

Formate disponibile

Symantec NetBackup Release Notes

UNIX, Windows, and Linux

Symantec NetBackup Release Notes

Contacting Technical Support

Licensing and registration

Maintenance agreement resources

Additional enterprise services

Technical Support ............................................................................................... 4 Chapter 1 New Features

Platform compatibility ....................................................... 23

About NetBackup backward compatibility ......................................... 36

Product Dependencies ....................................................... 39

Operational Notes ............................................................... 49

End of Life Notifications .................................................... 97

Related Documents ........................................................... 101

Windows Logo Certification information ...................... 109

New features in NetBackup

New Features New features in NetBackup

Media server deduplication

Turnkey operation to enable advanced, business reporting Improved reporting features

NetBackup for VMware:

This release is compatible with the following new proliferations:

New Features NetBackup deduplication

NetBackup Support Utility (nbsu) enhancements

See the NetBackup Deduplication Guide.

About client deduplication

New Features About Symantec OpsCenter

About media server deduplication

About Symantec OpsCenter

Direct upgrade path

New Features About Symantec OpsCenter Analytics

Expanded and simplified deployment:

About Symantec OpsCenter Analytics

About NetBackup for VMware

New Features Guided Recovery

New database features and enhancements

Exchange 2010 support

New Features New database features and enhancements

Windows 7/2008R2 client support

NetBackup for Enterprise Vault agent

NetBackup for Hyper-V agent

New file-level incremental backups

New Features About NetBackup support utilities

Improved SharePoint Granular Recovery

About NetBackup support utilities

NetBackup Support Utility (NBSU)

New Features NetBackup installation and deployment enhancements

NetBackup installation and deployment enhancements

New Features NetBackup installation and deployment enhancements

BMR master server NDMP NetBackup Vault

BMR Boot server DB2 NetBackup Encryption Informix LiveUpdate agent

New Features NetBackup installation and deployment enhancements

Lotus Notes Oracle SAP Snapshot Client Sybase

New Features About back-level administration capabilities by the NetBackup-Java console

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

About Platform proliferation for NetBackup 7.0

About server and client platform compatibility

About platform and operating system compatibility changes

Platform compatibility About server and client platform compatibility

About NetBackup Compatibility Lists

Platform compatibility About server and client platform compatibility

NetBackup 7.x Snapshot Client compatibility lists

Platform compatibility About server and client platform compatibility

NetBackup7.x Cluster Compatibility List