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’s primary role is to respond to specific queries about product features and functionality.com/techsupp/ Before contacting Technical Support. please have the following information available: ■ ■ ■ ■ Product release level Hardware information Available memory.symantec.symantec. disk space. 7 days a week Advanced features. and NIC information Operating system . the Technical Support group works with Product Engineering and Symantec Security Response to provide alerting services and virus definition updates. The Technical Support group also creates content for our online Knowledge Base. including Account Management Services ■ ■ ■ ■ For information about Symantec’s Maintenance Programs. you can visit our Web site at the following URL: www. When you contact Technical Support. make sure you have satisfied the system requirements that are listed in your product documentation. Also. The Technical Support group works collaboratively with the other functional areas within Symantec to answer your questions in a timely fashion. For example. you should be at the computer on which the problem occurred. Symantec’s 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.com/techsupp/ Contacting Technical Support Customers with a current maintenance agreement may access Technical Support information at the following URL: www. in case it is necessary to replicate the problem.Technical Support Symantec Technical Support maintains support centers globally.

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 . language availability.■ ■ ■ ■ Version and patch level Network topology Router. such as address or name changes General product information (features.symantec.symantec. access our technical support Web page at the following URL: www.com/techsupp/ Customer Service is available to assist with the following types of issues: ■ ■ ■ ■ ■ ■ ■ ■ ■ Questions regarding product licensing or serialization Product registration updates.com/techsupp/ Customer service Customer service information is available at the following URL: www. 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. gateway.

expertise.com semea@symantec. and countermeasures to prevent attacks before they occur.com Select your country or language from the site index. monitoring.symantec. Educational Services provide a full array of technical training. security certification. Middle-East. Symantec Consulting Services provide on-site technical expertise from Symantec and its trusted partners. and awareness communication programs. ensuring rapid response to real threats. Each is focused on establishing and maintaining the integrity and availability of your IT resources. and Africa North America and Latin America customercare_apac@symantec. Enterprise services that are available include the following: Symantec Early Warning Solutions These solutions provide early warning of cyber attacks. and management capabilities. Symantec Consulting Services offer a variety of prepackaged and customizable options that include assessment. design. Consulting Services Educational Services To access more information about Enterprise services.com supportsolutions@symantec.Maintenance agreement resources If you want to contact Symantec regarding an existing maintenance agreement. Managed Security Services These services remove the burden of managing and monitoring security devices and events. please visit our Web site at the following URL: www. security education. please contact the maintenance agreement administration team for your region as follows: Asia-Pacific and Japan Europe.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. . which enable you to manage your business risks proactively. implementation. and global insight. comprehensive threat analysis.

................ About NetBackup support utilities ........................... About Symantec OpsCenter ............................................ NetBackup deduplication ............................. NetBackup binary sizes .................................. 11 11 13 13 14 14 15 15 16 16 16 17 17 17 18 18 19 22 22 New features in NetBackup ............... About Platform proliferation for NetBackup 7............................................................................................................... About NetBackup backward compatibility ..................................................Contents Technical Support .. Improved SharePoint Granular Recovery ................................................................... 23 23 24 26 27 28 30 33 35 .... NetBackup installation and deployment enhancements .... About platform life cycles .............................................. About NetBackup for VMware ................................................................................................................................................ 23 About server and client platform support .......................................... Guided Recovery ....................................................................0 ...................................... New database features and enhancements ...................................................................................................................................... NetBackup for Hyper-V agent ................................................ About platform and operating system support changes ............................... NetBackup for Enterprise Vault agent .............................................. Platforms supporting the NetBackup Administration Consoles for UNIX ....................... Windows 7 and Windows 2008R2 client support ......................................................................................... 4 Chapter 1 New Features .......................... About media server deduplication ...................................... About Symantec OpsCenter Analytics ................ About back-level administration capabilities by the NetBackup-Java console ........... Chapter 2 Supported Platforms ............................................................................................... About NetBackup Compatibility Lists ....................... About client deduplication ............... Exchange 2010 support ................................................................................................................... About the deduplication host supported platforms ...... About Operating systems not supported as of NetBackup 7........................0 and beyond .............................................................................................

................ 45 Chapter 4 Operational Notes .................................. 39 Operating system patches and updates ........................................................................................ Internationalization and localization Notes ............................................................... 49 Operational Notes in NetBackup ................................... NetBackup database agents ........ Secure push install ............................................... Lotus Notes agent .................................................................................... NetBackup commands and utilities ......................................... NetBackup Client Deduplication .................................................0 and later .................................................................... NetBackup Documentation Notes ........ NetBackup media and rebranding changes ............................................ General installation and upgrade items ............................................................ SQL server agent .................. NetBackup java interfaces ..................................................................................................................................... NetBackup Access Control ........................................................................... Enterprise Media Manager ....................................................................................... 50 50 50 53 56 56 56 58 58 61 66 67 69 69 70 73 75 75 76 76 77 77 78 81 81 82 82 82 83 84 84 84 85 85 86 88 89 ................................................................................................................................................. NetBackup AdvancedDisk option ..... NetBackup for Microsoft SharePoint ......... NetBackup LiveUpdate ................ SAN Client and Fibre Transport .................................................... Media Sharing ................. NetBackup Snapshot Client ..................................................................................... SharedDisk support in NetBackup 7........... NetBackup Bare Metal Restore .................. PureDisk Deduplication Option (PDDO) ...................................................................................... NetBackup interfaces .......... NetBackup cluster . About the NetBackup Media Server Deduplication Option .....................................8 Contents Chapter 3 Product Dependencies ................................................................................. NetBackup Hyper-V ..................................... About Symantec OpsCenter ......................................... NetBackup media and device management ................................................. Sybase server agent ....... General NetBackup operational notes ............................................... NetBackup Administration Console for Windows ............................................................................................................................................ About NetBackup Enterprise Vault Agent ............... 39 About supported versions of VxFS and VxVM .................................................................. NetBackup OpenStorage Option ............ NetBackup for Microsoft Exchange ................................ NetBackup installation and start-up notes ............. Storage unit configuration ......................................................................................................................

........... About database functions no longer supported ........... 95 End of life notifications ...................................................................................................... 100 About installation guides .............. 104 About the Troubleshooting guide ............ 104 About the device configuration guide ........... About features....................... About general NetBackup features no longer supported .................... 100 About administrator’s guides ................................................................................................................ 105 Appendix A Windows Logo Certification information ............................ About general NetBackup notifications ......................................................... enhancements.......... 89 NetBackup Vault ....................... 95 95 96 96 97 98 Chapter 6 Related Documents ...............................................Contents 9 NetBackup Disk Storage units .... 101 About user’s guides .................................................................................................................................................. 107 About Windows Server 2008 R2 Logo Certification .................... 90 NetBackup for VMware ................................................................... 99 About related NetBackup documents ................ 100 About getting started guides ..................................... 107 .................................... 99 About NetBackup release notes .......................................................................... 92 Chapter 5 End of Life Notifications ........ and commands no longer supported .......... About NetBackup commands no longer supported ...........................................................agents and options ........................................................................................ 105 About NetBackup command documents ................

10 Contents .

The following list highlights some of the major features that comprise NetBackup 7.0 contains many new features and enhancements that increase the scalability and functionality of NetBackup for its large enterprise customers.0. ■ Integrated deduplication: ■ Client deduplication .Chapter 1 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 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 adds the following proliferation support: .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.0 databases using the Enterprise Vault Agent including the Fingerprint database. 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. FSA Reporting database. and Auditing database Enterprise Vault 8.

and NetBackup uses the PureDisk Deduplication Engine (PDDE) to deduplicate backup data. You use NetBackup interfaces to install.New Features NetBackup deduplication 13 ■ ■ ■ ■ HP-UX 11. and manage storage.1 support Java user interface support on RHEL 5 systems NetBackup Support Utility (nbsu) enhancements NetBackup deduplication NetBackup now provides integrated data deduplication within NetBackup. ■ See the NetBackup Deduplication Guide. About client deduplication This feature permits the deduplication of data from the source (a NetBackup client). Symantec packaged PureDisk into a modular engine. You do not have to use the separate PureDisk interface to deduplicate data. Because unique data segments only are transferred. See “About media server deduplication” on page 14. servers. The media server writes the data to the storage and manages the deduplicated data. NetBackup clients send their backups to a NetBackup media server.31 IA BMR master server support for NetBackup 7. backups.0 BMR WINPE 2. and deduplication. configure. The NetBackup client deduplicates its own data and then sends it directly to a storage server. You can use NetBackup deduplication at 2 points in the backup process: ■ On a NetBackup client. It allows only unique data segments to be moved across the LAN and stored upon the media server’s embedded deduplicated storage. See “About client deduplication” on page 13. this option reduces network load. which deduplicates the backup data. 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 Less impact on the LAN Reduced backup windows Can be combined with Application agents ■ ■ ■ ■ . bypassing media server processing. On a media server.

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 server’s 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, https://symiq.corp.symantec.com/crossproducts/SErotation
/NBU7-BetaR/Shared%20Rotation%20Documents/Forms/AllItems.aspx.

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.

New Features About Symantec OpsCenter Analytics

15

Direct upgrade path This feature enables you to configure direct upgrade path from existing NOM and VBR installations. Expanded and simplified deployment

OpsCenter server supports 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 such as advanced, business reporting and improved graphics. (Business reporting was previously available with VBR.) The new OpsCenter Analytics package includes the features associated wtih Symantec OpsCenter and the following features:
■ ■ ■

Historical trending and predictive forecasting Complete report customization Support for 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 VM 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, virtual center, 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 introduces support for Exchange 201, including 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.

0 databases using the Enterprise Vault Agent. In addition. the FSA Reporting database . (The Windows 2008 R2 is exclusively 64-bit from Microsoft. automated process of backing up your Enterprise Vault environment using the Enterprise Vault Agent. ■ ■ ■ NetBackup for Hyper-V agent The NetBackup for Hyper-V agent protects virtual machines (VM) by backing up the virtual hard drive (VHD) images. The following enhancements have been made to the NetBackup for Hyper-V agent for this release: ■ New file-level incremental backups . Automatic detection of all VMs within the Hyper-V server simplifies the policy setup. and the auditing database. Previously. The following enhancements have been made to the NetBackup Enterprise Vault agent for this release: ■ Inclusion of all Enterprise Vault 8.) NetBackup for Enterprise Vault agent The NetBackup for Enterprise Vault agent greatly simplifies data protection for the Enterprise Vault servers. Enterprise Vault Migrator is now included with NetBackup The Enterprise Vault migratory is now included with NetBackup 7. media server. It protects all of the Enterprise Vault partitions and their associated databases. Moreover. that was a separate download. That includes the fingerprint database.0 Support for granular quiescence You can now back up and restore using the Enterprise Vault Agent at a more granular level. From the image backup. An enhanced. That is done without any VHD staging. you can restore the entire VM or individual files within the VM. The agent supports disaster recovery of a partition and databases. Enterprise Vault 8.0.New Features New database features and enhancements 17 Windows 7 and Windows 2008R2 client support This release of NetBackup provides NetBackup client support for the Windows 7 desktop platform. the NetBackup client and agents. only the files you select are recovered from tape. and master server now support the Windows 2008 R2 operating system. it also supports recovery of individual files within a partition.

Alternatively.18 New Features About NetBackup support utilities NetBackup for Hyper-V now supports incremental backups. About NetBackup support utilities NetBackup 7. Now. Support for other VSS snapshot providers will follow. that included the following: ■ ■ ■ ■ ■ Sites and sub-sites Entire lists.1 patch or later. The following list summarizes the enhancements that have been made to each utility in this release: ■ NetBackup Support Utility (NBSU) .0. links. like calendars. or UUID when configuring policies. ■ ■ ■ Improved SharePoint Granular Recovery Starting with NetBackup 6.0. discussions. display name.5. to complement the dual purpose full backups. However. more comprehensive granular recovery capabilities. NetBackup 7.0. Flexible VM identification Use the VM hostname. ■ Two types of off-host backup NetBackup for Hyper-V now supports off-host backup of VM snapshots on CLARiiON storage arrays.0 for Hyper-V supports Hyper-V clustering.4. and others Any item(s) from a list Any version of a file Recover files to a folder on disk. you can reap the benefits of the more comprehensive granular recovery capabilities along with faster granular recovery with the metadata intact.0 includes three support utilities: nbsu. Hyper-V R2 and Cluster Shared Volumes (CSV) NetBackup for Hyper-V is now compatible with Hyper-V clusters and the new CSV capability. and NBCCR. To obtain this update contact NetBackup Technical Support. using the NetBackup Snapshot Client in the VM to perform off-host backup of volumes is also now supported. NBCC. With NetBackup 7. the NetBackup for SharePoint Agent offered additional. tasks. file-level recovery is available from both full backups and incremental backups. Hyper-V cluster support requires a NetBackup 7.

packaged. and updated: . It also analyzes the consistency state of NetBackup databases and catalogs as they relate to tape media.0. 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. Enhancements have been made to this utility to ensure that it supports NetBackup 7. ■ NBCC utility The NBCC utility uses the output from various OS and NetBackup commands to analyze the consistency state of the NetBackup configuration. The following list describes the new changes affecting how NetBackup is deployed. you can obtain information about NetBackup configuration settings about troubleshooting areas. installed. NBCC consolidates. Enhancements were made to the SLP. ■ NetBackup installation and deployment enhancements This release of NetBackup contains many enhancements in the area of installation and deployment. and packages the resulting data into a bundle that can be sent to Symantec Tech Support for analysis. EMM. This tool queries the host on which it runs and gathers diagnostic information about NetBackup and the operating system. In addition to the new enhancements. This file is created as part of the analysis of the data that the NBCC utility collects and any site specific situations. If inconsistencies are detected. This utility is now available for the Mac OS X platform. For instance. In addition. For NetBackup 7.0 this utility has been enhanced to include the following new features: ■ ■ ■ New commands line options have been added. In NetBackup 7.New Features NetBackup installation and deployment enhancements 19 The NBSU utility assists you in gathering NetBackup and operating system diagnostic information. this utility contains fixes that address the minor issues found in earlier releases. and versioninfo diagnostics. the support and support.0 functionality. or about NetBackup or media management job status codes. it provides a wide range of control over the types of diagnostic information gathered.exe diagnostic information gathering utilities are no longer included or supported beginning with this release of NetBackup.

Deploy basic product license tags. LiveUpdate Enhancements Improvements to the LiveUpdate configuration make it possible to specify the LiveUpdate server in the policy. Simplified Access Control Configuration By more tightly integrating AT support into NetBackup. Separate installation for these products is no longer needed. UNIX Package Consolidation In NetBackup 7. changes have been made that greatly simplify the installation process. That is the first step in NetBackup’s license and deployment reporting strategy. Changing the server. no longer requires client-side changes. See “About the Electronic Software Distribution (ESD) images" in the NetBackup Installation Guide for more information about how you can download these images. Electronic Software Distribution (ESD) images The DVDimage files are posted and available for download on the FileConnect Website. 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 . most of the add-on products and database agents are now installed with the NetBackup server or the client package. A feature has been added that deploys ISO 19770 standard software asset tags with NetBackup.20 New Features NetBackup installation and deployment enhancements ■ DVD Layout NetBackup is now only available on DVD. The product is no longer offered in a CD format.0. That also supports using different LiveUpdate servers in each policy.

and others. making it easier for support to find and copy the correct logs.) The Japanese and the Chinese language packages remain as separate add-ons. In addition. The process to install and upgrade these products remains the same. the older versions of any listed products here must be removed before an upgrade to NetBackup 7. VRTSnbenc. A valid license is still required to enable the product.New Features NetBackup installation and deployment enhancements 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 full configuration summary report now describes what options were selected for the install. The installation script displays a list of the packages it finds that must be removed. ■ ■ ■ ■ VxUL Log Directory Restructuring This change enhances the usability of VxUL logs by putting the logs for each service in a unique directory. If product configuration was required previously (such as db2_config). That prevents the need to individually select hundreds of clients. VRTSnbdb2. SYMCnbdb2. Preinstallation checks are run to ensure a successful installation. In addition. configuration is still required. it only opens log files for the correct OID. Improvements have been made to the error logging and reporting. Multiple simultaneous push installs greatly improve the installation performance over the previous approach of one client at a time. For example. ■ 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. the performance of the vxlogview command is improved when searching for logs by the OID since this command does not need to look at all of the VxUL log files for NetBackup. SYMCnbenc. .0. (For Solaris server upgrades. all installation logs are now captured in an HTML format for a more readable display.

This includes the packaging and the installation of the NetBackup 6.0 This section lists the various platform that are new with NetBackup 7. ■ ■ ■ Add HP-UX 11.5.1 support Java GUI on RHEL 5 . About Platform proliferation for NetBackup 7.0 provides additional ways to perform back-level administration of the supported back-level versions.0.0 MP7 and NetBackup 6.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.31 IA BMR master server for NBU 7 BMR WINPE 2.4 versions of the NetBackup-Java console on supported UNIX and Linux platforms.

Chapter 2 Supported Platforms This chapter includes the following topics: ■ ■ ■ ■ ■ About server and client platform support About Operating systems not supported as of NetBackup 7. 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 support changes This release of NetBackup contains many changes and enhancements to the supported platforms and operatings systems. These compatibility lists offer a variety of up-to-date information about the operating systems that NetBackup and NetBackup features support.0: .0 and beyond NetBackup binary sizes Platforms supporting the NetBackup Administration Consoles for UNIX About NetBackup backward compatibility About server and client platform support You can find the NetBackup-supported platform information in various compatibility lists on the Symantec Support Web site. The following list describes some of the major changes that apply the NetBackup 7.

peripherals. Linux SUSE and Linux RedHat Itanium are no longer supported for use as master or media servers.com/docs/337048 . and libraries is located in various compatibility lists on the Symantec Support Web site. To upgrade these systems to NetBackup 7. ■ ■ ■ ■ ■ ■ ■ About NetBackup Compatibility Lists The most up-to-date information on supported platforms.0 servers.symantec.x are compatible with NetBackup 7. Servers and clients with these operating systems that use NetBackup 6. However. These platforms are only supported as a client. 32-bit media servers and clients that use NetBackup 6. In addition. Windows IA64 is supported only as a client. The following compatibility lists are available on the Symantec Support Web site: ■ The NetBackup Enterprise Server and Server 7. Novell NetWare is no longer supported for use as a media server.0.x OS Software Compatibility List contains information about the operating system (OS) level and the version that is required to support a NetBackup master or media server.x are compatible with 64-bit master servers that use NetBackup 7. Predecessors and successors to the supported operating system levels may function without difficulty.x catalogs and databases to a system with a supported platform. When you upgrade a media server that is used for OpenStorage to NetBackup 7. HP-UX PA-RISC is no longer supported as a master server. you must first migrate your current NetBackup 6. IRIX and Tru64 are no longer supported. drives. All 64-bit platforms are supported except for FreeBSD clients and Mac clients. The support of Linux Red Hat IBM zSeries platforms has switched to 64-bit client support. http://entsupport. It also describes the OS level and the version that is required to support a NetBackup client. as long as the release provides binary compatibility with the supported level. NetBackup requires OpenStorage vendor plug-ins to be 64-bit. you also must update the vendor plug-in to a 64-bit version. This platform is only supported as a client. This platform is supported only as a true media server (media server without the EMM server) or a true client.0.24 Supported Platforms About server and client platform support ■ All UNIX 32-bit system support has been discontinued.0.

com/docs/337049 ■ NetBackup 7. routers. robot-types. and encryption devices http://entsupport. switches. virtual tape devices.0 hardware compatibility list includes information for supported drives. iSCSI configurations. http://entsupport.symantec. fibre-channel HBAs. and bridges. ■ The NetBackup server 7. bridges. switches.com/docs/336875 The NetBackup 7. libraries.x Software Compatibility List This compatibility list contains the most current platform support information for NetBackup database agents.x Snapshot Client compatibility lists . The platform support lists that NetBackup maintains are subject to change as vendors add and drop support for platforms or OS versions. routers.symantec.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 support for a platform or OS version requires platform vendor support for that product. robot types.Supported Platforms About server and client platform support 25 The NetBackup Enterprise Server and Server 7.x Hardware compatibility list includes information about the supported drives. 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.

Select Master Compatibility List link under the Compatibility title on the Web page .symantec.com/business/support 2 3 Select the NetBackup Enterprise Server link under the Support for Top Products title on the Web page .x BMR File System and Volume Manager compatibility lists http://entsupport. The Web page refreshes and contains a list of compatibility documents. You must have Adobe Acrobat Reader to view these documents.symantec.com/docs/286496 ■ Backup Exec Tape Reader compatibility list http://entsupport.x Cluster Compatibility List http://entsupport.symantec.symantec.com/docs/337056 See also the NetBackup Bare Metal Restore Administrator's Guide for the following additional compatibility lists: ■ ■ ■ ■ ■ BMR supported shared resource tree (SRT) versions BMR supported file systems and volume managers BMR supported cluster solutions BMR disk space requirements NetBackup7. (The compatibility list documents are in PDF format. From this Web page.com/docs/337053 ■ NetBackup Desktop/Laptop Option compatibility list http://entsupport. and Symantec cannot distribute the package.symantec.com/docs/295433 To locate supported platform information on the Symantec Support Web site 1 Go to the following URL: www. It is not part of the Solaris installation media.) About the deduplication host supported platforms The following is a list of the supported platforms for NetBackup Deduplication: ■ Solaris SPARC 10 x64 Solaris requires an encryption package (SUNWcry64). Red Hat Enterprise Linux: ■ .com/docs/337052 ■ NetBackup 7. you can refine your search to find a link to the appropriate document.26 Supported Platforms About server and client platform support http://entsupport.symantec. You must download and install the package.

database problems may affect installation and performance. deduplication processes may not start. backward compatibility cannot be guaranteed without exhaustive testing. About Removing a client platform The customer commitment for client platform version support is one version back with every effort to support all versions. See “About Removing a client platform” on page 27.5 x64 (and higher) Red Hat Enterprise Linux 5. or run correctly. About platform life cycles NetBackup software supports an ever-changing set of platforms. but no history. If swap space is less than physical memory. About adding a platform Adding support of a platform to NetBackup introduces a situation where the platform has a future.NET 3. However.x x64 (and higher) On Red Hat Linux. configure the shared memory to be at least 128MB (SHMMAX=128MB). If you do not.Supported Platforms About server and client platform support 27 ■ ■ Red Hat Enterprise Linux 4. See “About adding a platform” on page 27.5 SP1. the platform is supported in that version and subsequent versions (but not previous versions). You can mix the individual clients that are at different version levels within a NetBackup domain. Windows 2008 x64 Windows 2008 R2 x64 ■ ■ ■ Linux systems must have at least the same amount of swap space as physical memory space. When a platform is added for a NetBackup release. In this situation. it is possible that during an alternate restore. An exception is that the client version cannot be newer than the master and the media server version. the . ■ SUSE Linux Enterprise Server 10 (SLES 10) x64 The SUSE Linux system must be at patch level 2. And NetBackup must be flexible enough to handle platform life cycle issues such as adding and removing a platform from its support list. Windows 2003 x64 Windows 2003 SP2 x64 systems require Microsoft .

5 Novell OES (Linux) 1 SP2 Apple Macintosh POWERPC.26 and greater Mac OS X 10.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 support only Media server and client support only Media server and client support only Comments .5.1 AIX 5.31 HP-UX IA64 11.0 HP-UX 11.0 and beyond Table 2-1 displays the operating systems that are no longer supported at the release of NetBackup 7.28 Supported Platforms About Operating systems not supported as of NetBackup 7.2 Asianux 3.4 FreeBSD 6. i386 x86 x86 x86 Client support only Operating systems not supported as of NetBackup 7. Alternate restores should go to the same or newer versions.0 NetWare 6.0 and beyond restore is sent to an older version.23 HP-UX 11.3 Mac OS X 10. About Operating systems not supported as of NetBackup 7.00 HP-UX 11.1 NetWare 6.0 FreeBSD 5.23 IRIX 6.3 FreeBSD 5. Table 2-1 OS/Version AIX 5.0 and beyond.11 HP-UX 11.4 NetWare 5. See “About NetBackup backward compatibility” on page 35.

2 SUSE Desktop 9.Supported Platforms About Operating systems not supported as of NetBackup 7.1 Red Hat 2.1 Red Hat 3.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 SUSE Linux Enterprise Server 10 SP1 Comments .0 Solaris 8.0 Solaris 9.0 Solaris 8.0 Red Hat 5.0 Red Hat 3.0 SUSE Desktop 9.0 Solaris 10.0 and beyond 29 Table 2-1 Operating systems not supported as of NetBackup 7.0 Red Hat 3.0 x86 Solaris 10.0 x86 SUSE Desktop 9.0 Red Hat 3.0 and beyond (continued) Hardware x86 x86 x86 x64 IA64 z/Architecture IA64 IA64 SPARC x86 x86 x64 x86 x64 x86 x86 x86 x86 x64 IA64 x86 x64 IA64 IA64 Client support only Client support only Client support only Client support only OS/Version Red Flag Linux 4.0 Solaris 9.0 Red Hat 4.

30

Supported Platforms NetBackup binary sizes

Table 2-1

Operating systems not supported as of NetBackup 7.0 and beyond (continued) Hardware
Alpha Alpha x86 and x64 IA64 Client support only

OS/Version
Tru64 5.1a Tru64 5.1b and greater Windows Server 2000 Windows Server 2003 SP1 and R2

Comments

NetBackup binary sizes
The information in this section helps you determine if your NetBackup environment has the proper amount of memory 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 NetBackup supports. Table 2-2 OS/Version
AIX 5.3 AIX 6.1 FreeBSD 6.3/7.x HP-UX 11.11

NetBackp binary sizes for supported platforms 32-bit 64-bit 32-bit 64-bit Notes client client server server
928MB 928MB 16MB 632MB 1666MB 64-bit binary support. Media server or client support only. 1666MB 64-bit binary support. Media server or client support only. 1666MB 64-bit binary support. Media server or client support only. 3012MB 3083MB 64-bit binary support 3083MB 64-bit binary support

CPU Architecture
POWER POWER x86 PA-RISC

HP-UX 11.23

PA-RISC

632MB

HP-UX 11.31

PA-RISC

632MB

HP-UX 11.31 Mac OS X 10.5 Mac OS X 10.5

IA64 POWER i386 (x86) 22MB 22MB

922MB

Supported Platforms NetBackup binary sizes

31

Table 2-2 OS/Version
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 DC

NetBackp binary sizes for supported platforms (continued) 32-bit 64-bit 32-bit 64-bit Notes client client server server
16MB 16MB 16MB 16MB 16MB 16MB 16MB 16MB 16MB 16MB 16MB 510 MB 510 MB 510 MB 351 MB 351 MB 96MB 1726MB 64-bit binary support. PDDE requires an additional 157MB. 1726MB 64-bit binary support. PDDE requires an additional 157MB. Client only support

CPU Architecture
HP VAX HP VAX HP VAX HP Alpha HP Alpha HP Alpha HP Alpha HP Alpha HP IA64 HP IA64 HP IA64/Alpha x64

Red Hat Enterprise Linux 4.0 x64 (AS) Red Hat Enterprise Linux 5.0 x64 (base) 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)

Client only support

96MB

12MB

32

Supported Platforms NetBackup binary sizes

Table 2-2 OS/Version

NetBackp binary sizes for supported platforms (continued) 32-bit 64-bit 32-bit 64-bit Notes client client server server
12MB

CPU Architecture

Red Hat Enterprise Linux 5.0 z/Architecture (base) Red Hat Enterprise Linux Desktop 4.0 Red Hat Enterprise Linux Desktop 5.0 x64

510MB

1726MB 64-bit binary support. PDDE requires an additional 157MB. 64-bit binary support. PDDE requires an additional 157MB. 1726MB

x64

510MB

Red Hat Enterprise Linux 5.0 x64 (Advanced) Solaris 9.0 SPARC

510MB

525MB

64-bit binary support. PDDE requires an additional 157MB. 2050MB 64-bit binary support. PDDE requires an additional 157MB. 1915MB 64-bit binary support. PDDE requires an additional 157MB. Client only support

Solaris 10.0

SPARC

639MB

Solaris 10.0

x64

439MB

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) SUSE Linux Enterprise Server IA64 11 SUSE Linux Enterprise Server x64 11 SUSE Linux Enterprise Server z/Architecture 11 Windows x86 600MB

345MB

492MB

1662MB PDDE requires an additional 157MB. Client only support

101MB

12MB

Client only support

345MB

Client only support

492MB

1662MB

12MB

Client only support

1700MB

Covers all supported Windows x86 platforms

and Retore user interface in this release. And for information on how to use the NetBackup Adminstration Console. The interface can run on any NetBackup Java-capable system. see the NetBackup Installation Guides. You may encounter some user-interface anomalies when you use the various window managers that are available on UNIX platforms. and console Restore interface Yes Yes Yes Yes Yes Yes OS/Version JRE upgrade version AIX 5. Volume 1. This action refreshes the display and causes the interface to display the information correctly. In the most common cases of misplaced or shifted components within a dialog.11 POWER POWER PA-RISC Java 6 SR6 Java 6 SR6 6.3 AIX 6. For information on how to install the consoles.1 HP-UX 11. Table 2-3 Platforms that support NetBackup-Java Administration Console and Backup. Many of these problems are documented and can occur because of unusual or non-standard window manager configurations.05 . administration Archive. Note: Symantec supports the window managers in the following table when using NetBackup Java. and Retore user interface CPU Architecture NetBackup-Java Backup. see the NetBackup Administrator's Guide. resize the dialog. Archive. Archive.Supported Platforms Platforms supporting the NetBackup Administration Consoles for UNIX 33 Table 2-2 OS/Version Windows NetBackp binary sizes for supported platforms (continued) 32-bit 64-bit 32-bit 64-bit Notes client client server server 700MB 1900MB Covers all supported Windows x64 platforms Client only support CPU Architecture x64 Windows IA64 600MB Platforms supporting the NetBackup Administration Consoles for UNIX The NetBackup Administration Console provides a graphical user interface through which the administrator can manage NetBackup. Table 2-3 is a list of platforms that support the NetBackup-Java Administration Console and the Backup.0.

0 Solaris 10.0 (base) Red Hat Enterprise Linux Desktop 4.6-16 1.0.0 SUSE Linux Enterprise Server 9 SUSE Linux Enterprise Server 10 (SP1) SUSE Linux Enterprise Server 10 (SP1) SUSE Linux Enterprise Server 10 (SP1) SUSE Linux Enterprise Server 11 SUSE Linux Enterprise Server 11 SUSE Linux Enterprise Server 11 PA-RISC PA-RISC IA64 x64 x64 IA64 IA64 POWER POWER z/Architecture z/Architecture x64 x64 SPARC SPARC x64 IA64 x64 POWER z/Architecture IA64 x64 z/Architecture 6.6-16 1. 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 1. administration Archive.0.6-16 1.31 Red Hat Enterprise Linux 4.6-16 1.0 (base) Red Hat Enterprise Linux 4.31 HP-UX 11.0 (base) Red Hat Enterprise Linux 4.05 6. Archive.6-16 1.6-16 .6-16 1.0 Red Hat Enterprise Linux Desktop 5.6-16 1. and Retore user interface (continued) CPU Architecture NetBackup-Java Backup.0 Solaris 9.0 (AS) Red Hat Enterprise Linux 5.34 Supported Platforms Platforms supporting the NetBackup Administration Consoles for UNIX Table 2-3 Platforms that support NetBackup-Java Administration Console and Backup.23 HP-UX 11.0 (base) Red Hat Enterprise Linux 4.6-16 1.6-16 1.6-16 OS/Version JRE upgrade version HP-UX 11.6-16 1.6-16 1.05 6.05 1.0 (AS) Red Hat Enterprise Linux 5.0 (AS) Red Hat Enterprise Linux 5.0 Solaris 10.0 (AS) Red Hat Enterprise Linux 5.0.

6-16 Yes Yes Yes Yes Yes 1.6-16 1. Archive.6-16 1.6-16 About NetBackup backward compatibility NetBackup supports a mixture of NetBackup servers that are at various release levels in the same environment. administration Archive.6-16 1.6-16 1.6-16 Yes Yes Yes Yes Yes 1.Supported Platforms About NetBackup backward compatibility 35 Table 2-3 Platforms that support NetBackup-Java Administration Console and Backup.6-16 1. Table 2-4 shows the different server version levels that NetBackup supports in this release.6-16 1. and console Restore interface Yes Yes OS/Version JRE upgrade version 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 1. Symantec only supports certain combinations of servers and clients within a NetBackup environment that must provide backward compatibility. and Retore user interface (continued) CPU Architecture NetBackup-Java Backup.6-16 Yes Yes 1.6-16 Yes Yes Yes Yes 1.6-16 Yes Yes 1. . However.6-16 1.

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. ■ ■ . These clients are compatible with NetBackup version 7.0 master and media servers.5 (and later). 6.0 (and later) 6.0 (and later) 6.0 Client version 7.0 Media server version 70 7.5 (and later). 6.x: New NetBackup customers with Windows 2000 systems: No action is required.0 NetBackup 7. http://entsupport.0 (and later) NetBackup 7. See the following Technote on the Symantec Support Web site for more information.x on Windows 2000 clients with your NetBackup 7.com/docs/308850 For more information about upgrading NetBackup.5 (and later). 6.symantec. During an upgrade to NetBackup 7.0 6.0 servers.0 NetBackup 7. You must install NetBackup version 6. However. refer to the NetBackup Installation Guide for either UNIX or Windows. the master server must run the highest version of NetBackup in use in that configuration. you can still use NetBackup version 6.x client software on your Windows 2000 systems. 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. it is necessary to have enough free disk space to accommodate three complete copies of the NetBackup database. you must back up your NetBackup catalogs and verify that the catalog backup was successful.0.36 Supported Platforms About NetBackup backward compatibility Table 2-4 Mixed-server support for NetBackup 7. That includes all transaction logs and database files in the data directory including BMR if it is configured and in use.0 does not support Windows 2000 systems. 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.0 Master server version NetBackup 7. In a mixed-server environment.

Supported Platforms About NetBackup backward compatibility 37 ■ A master server can inter-operate with a media server that is running a level of NetBackup that is one major release lower. After startup. A media server cannot have a numerically higher version than the master server. Users that are assigned to the Administrators Group and are not the official administrator cannot install NetBackup in UAC-enabled environments. The backup images that are created under an older version of NetBackup are recoverable with a newer version of NetBackup. and console) on an individual system must be at the same version. ■ ■ ■ ■ ■ .) All components (server. you must log on as the official administrator. (Each media server must run equal or lower levels of NetBackup. To allow users in the Administrators Group to install NetBackup. client. To install NetBackup on Windows 2008/Vista/2008 R2/7 UAC-enabled environments. an upgraded media server uses the vmd service to push its version information to all servers in its master server list. Your server’s NetBackup version determines whether the version information can be pushed. An automatic update occurs every 24 hours when servers push their version information again. Servers can pull and push their version information between master and media servers. disable UAC.

38 Supported Platforms About NetBackup backward compatibility .

Table 3-1 Operating system patches and updates for NetBackup Notes You may need to reboot after changing to version 9. The IY91284 fix is part of Maintenance Level 6.0. Table 3-1 provides the known.3 or later xlC.0.0.0. This section is a guide to inform you of the operating systems that require a patch or an upgrade. You should verify that your operating system is up-to-date with all of the latest patches and upgrades before you install NetBackup.3. A vendor may have released a more recent patch that supersedes a patch that is listed in this table. Operating system type Patch and version AIX 5.rte 8.Chapter 3 Product Dependencies This chapter includes the following topics: ■ ■ Operating system patches and updates About supported versions of VxFS and VxVM Operating system patches and updates This topic provides information on the product dependencies of NetBackup 7.0. you may need to install the IY91284 fix to avoid a potential issue when creating or updating the NetBackup database. Symantec recommends that you visit the Support Web site of that particular vendor for their latest patch information.0.3 AIX runtime libraries 8.10 and 9.0.0.0. minimum operating system (OS) patches and updates.0.0.rte 8.10 fileset For the xlC.10 fileset. .

1 platforms an exception can occur.NET-RUN: /usr/lib/libipv6.3.1 . Operating system type Patch and version AIX 5.0. The runtime libraries need to be at 9.0.0.0.so.so Networking.NET2-RUN: /usr/lib/hpux64/libipv6. To prevent the exception.LIBM-PS32 HP-UX IA64 Networking.) You can use the oslevel -s command to verify what Maintenance Pack level you have installed. Symantec recommends that you install patch IZ16878 from IBM® Support.1 IZ16878 When you start Java user interface applications on AIX 6.3 TL7 SP5 (5300-07-05-0831 Maintenance Pack as a minimum.NET2-RUN: /usr/lib/hpux32/libipv6.so. AIX runtime libraries 9. If you install AT on an HP-UX platform. (Higher patch levels should also work.3 TL7 SP5 (5300-07-05-0831) AIX 6.1 Networking.sl Networking.0 requires the AIX 5.NET-RUN-64: /usr/lib/pa20_64/libipv6. this patch is required.NET2-RUN: /usr/lib/hpux32/libipv6.1 Networking.NET-RUN-64: /usr/lib/pa20_64/libipv6.3 or later.40 Product Dependencies Operating system patches and updates Table 3-1 Operating system patches and updates for NetBackup (continued) Notes NetBackup 7.sl Networking. You may need to reboot after you change to version 9.0.so Networking.0.3 or later HP-UX COMPLIBS.NET2-RUN: /usr/lib/hpux64/libipv6.

This patch is a LIBCL patch.sl For HP-UX PA-RISC platforms.NET-RUN-64: For HP-UX PA-RISC platforms.0. this /usr/lib/pa20_64/libipv6.Product Dependencies Operating system patches and updates 41 Table 3-1 Operating system patches and updates for NetBackup (continued) Notes Operating system type Patch and version Networking. This patch contains a linker tools cumulative patch.11 PHSS_35385 PHSS_32226 PHSS_37516 This patch is required for JAVA 6. ■ 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.NET2-RUN: For HP-UX PA-RISC platforms.1 HP-UX PA-RISC Networking. this /usr/lib/libipv6.sl fileset is required: Networking.1 fileset is required: Networking. 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. PHSS_27740 PHSS_26560 .NET-RUN: /usr/lib/libipv6. ■ QXCR1000589142: dld crash in LL_new_descendent_list when the aCC application is exiting.NET2-RUN: /usr/lib/libipv6. this fileset is required: Networking.NET-RUN-64: For HP-UX PA-RISC platforms. this /usr/lib/pa20_64/libipv6.1 fileset is required: HP-UX 11. This patch is a libc cumulative patch.

That is a recommended critical patch from HP that is required so that dlopen works properly.23 install this patch. Allow POLL_INTERVAL to be set to zero in /var/stm/config/tools/ monitor/dm_stape.com Operating system type Patch and version PHSS_32864 PHKL_26233 PHSS_35379 PHCO_29029 PHSS_24045 PHSS_30970 HP-UX 11. 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. This patch enables HP-UX 11. That disables the dm_stape monitor within the Event Monitoring System. Symantec recommends that you upgrade to IPR0109.11 mmap() to use large files from 2GB to 4GB. That is a recommended critical patch from HP that is required for NetBackup to use VxSS.hp.42 Product Dependencies Operating system patches and updates Table 3-1 Operating system patches and updates for NetBackup (continued) Notes That is a recommended critical patch from HP that is required for successful NetBackup client backups.cfg. www1.23 PHSS_37201 PHCO_33431 This patch is required for JAVA 6. PHSS_34858 . That is a recommended critical patch from HP that is required for successful NetBackup client backups.itrc. Symantec recommends that all customers running 11.0.

The operating system version must be SLES 10 update 2 or greater to run NetBackup 7. Contains fixes for the following: ■ Operating system type Patch and version PHKL_31500 PHSS_37492 QXCR1000593919: purifyplus dumps core in PA32 ■ QXCR1000589142: dld crash in LL_new_descendent_list when the aCC application is exiting.31 SLES10 x64 PHSS_37202 SLES 10 update 2 This patch is required for JAVA 6.Product Dependencies Operating system patches and updates 43 Table 3-1 Operating system patches and updates for NetBackup (continued) Notes That is a recommended critical patch from HP that NetBackup requires. ■ QXCR1000746161: dlsym() hangs ■ QXCR1000593999: dld emits assert messages for chatr +mem_check enabled 64-bit executables HP-UX 11. particularly when you attempt to run NetBackup with NetBackup Access Control (NBAC).0.0. . Solaris 9 SPARC 64-bit client 111711-11 (or greater) 111712-11 (or greater) 111722-04 (or greater) Patch: 112908-29 (or greater) Patch: 112874-31 (or greater) Solaris 10 SPARC 64-bit update 4 (08/07) and (server and client) newer The server is supported on update 4 (08/07) and newer.

this hotfix is not needed for any Windows version before Microsoft Windows Vista or Windows 2008 server. 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. In addition. NetBackup reports that it is unable to access the encrypted files and the backup continues with all of the remaining files. 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. meaning that NetBackup-encrypted files are backed up. Note: That does not apply to NetBackup encryption. XP. If you attempt to back up any protected files that have been encrypted by the operating system. NetBackup cannot back up these files. and Windows Vista. NetBackup encryption is separate from the file system encryption. Operating system type Patch and version Windows 2003 SP1 KB913648 Windows x64 (SP1 and SP2) Windows 2003. If you want to protect client (or server) systems that are running either Microsoft Windows Vista or Windows 2008 server. please refer to KB952696 to see if this hotfix is required for your operating system version . and Vista Microsoft storport hotfix Microsoft microcode reliability update That is a suggested fix that applies to 64-bit versions of Windows Server 2003.44 Product Dependencies Operating system patches and updates Table 3-1 Operating system patches and updates for NetBackup (continued) Notes Microsoft hotfix KB913648 contains the necessary updates to run Volume Shadow Copy. you may need to install Microsoft hotfix number KB952696. XP. If you are running Vista or Server 2008.

4. 4.0MP3RP3 Notes HP-UX PA-RISC 11.1 and higher 3.1MP4RP1 and higher on the 4.0 (AS) x86-64 5.0 and higher 5.0 LoP phase1.5.1.1.0) 5.0 MP3 and higher 3.1 and higher 4. IA64 NA POWER Solaris (SPARC) 9 10 SUSE Linux Enterprise Server 10 x86-64 5.0 MP3 and higher 3.1 codeline.1 MP2 and higher 4.1 MP2 and higher 4.31 Red Hat Enterprise Linux 4.5 3.0 and higher 5.0RU3 and higher 4. 5.1 to 4.0 codeline.5.23 11.1MP3 and higher in 4.1 and higher .0MP3 and higher on the 5.3 and 3.23 11.0 line 4.0 4.0RU3 and higher 4.Product Dependencies About supported versions of VxFS and VxVM 45 About supported versions of VxFS and VxVM Table 3-2 shows the different versions of VxFS and VxVM that Symantec NetBackup supports.0MP3 and higher on 5.1 and higher 3.0 4.1 MP3 and higher 4.1. and 5. 4.11 11.1 to 5.5 only 3.0 4.0 MP1 and higher 4.1 (64 bit) Version of VxVM 4.1 and higher 4.5. and 5.1 MP2 and higher 4. and 5. and the corresponding operating systems for each.1.1 MP2 and higher 4.0 4.3 (64 bit) 6. and 5. phase2 LxRT4.1MP4RP4 POWER Red Hat Enterprise Linux 5. 5.1 and higher Operating system AIX 5L OS Version 5.31 HP-UX IA64 11. Table 3-2 Versions VxFS and VxVM Currently Supported by Symantec NetBackup Version of VxFS 5.0 (AS) x86-64 IA64 4.5.1MP4RP1 and higher in the 4.1 MPx (support is dropped in 5.1 to 4.1 codeline only 5. 4.1 line.

11 11.0) 5.com/docs/320193.0 X NA X X X OS Version 5.1 codeline only.0 then new VxFS libraries need to be installed on the client to back up systems running VxFS.23 11.1 MP3 and higher Operating system OS Version IA64 Version of VxVM 4.1 SP1 and higher NetBackup has improved its integration with the Veritas File System (VxFS) product to ensure interoperability on all supported VxFS versions. Table 3-3 Shows the integration improvements that were made between the various operating systems and the Veritas File System (VxFS).0RU1 and higher Notes POWER SUSE Linux Enterprise Server 11 x86-64 IA64 POWER Windows 2003 Windows 2008 Windows 2008 R2 x86-64 x86-64 x86-64 NA 5.com/labs/patch.1MP3 and higher in 4.0RU3 and higher 5.0RU4 and higher 4. 5.5 NA X NA NA NA HP-UX IA64 11.31 .31 VxFS 4.symantec. See http://entsupport.0RU3 and higher 4.0RU4 and higher NA NA NA NA 5.1 MP3 (support dropped in 5.46 Product Dependencies About supported versions of VxFS and VxVM Table 3-2 Versions VxFS and VxVM Currently Supported by Symantec NetBackup (continued) Version of VxFS 4. Table 3-3 Operating system AIX HP-UX PA-RISC Improved Integration with Veritas File System (VxFS) VxFS 5.symantec.3 and higher 5.1 NA NA NA NA NA VxFS 3. https://vias.0 and higher 5.3 11. If running a VxFS version before VxFS 4. You can search and download the appropriate VxFS libraries to your system from Patch Central on the Symantec Support Web site. See.

0 (AS) Red Hat Enterprise Linux 5.1 NA VxFS 3.5 NA x86-64 X NA NA SUSE Linux Enterprise Server x86-64 SLES 10 IA64 SUSE Linux Enterprise Server x86-64 SLES 11 IA64 Solaris (SPARC) 9 10 X NA NA X NA NA X X NA X NA NA .0 X OS Version x86-64 VxFS 4.0 (AS) Improved Integration with Veritas File System (VxFS) (continued) VxFS 5.Product Dependencies About supported versions of VxFS and VxVM 47 Table 3-3 Operating system Red Hat Enterprise Linux 4.

48 Product Dependencies About supported versions of VxFS and VxVM .

Chapter 4 Operational Notes This chapter includes the following topics: ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ 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) .

http://entsupport. NetBackup installation and start-up notes The following subsections offer additional the information that can help you install NetBackup or use NetBackup. NetBackup Operations Manager (NOM) Starting with NetBackup 7. you can upgrade NOM to OpsCenter with an upgrade to NetBackup 7.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.x NetBackup environment includes NOM 6.0.com/docs/337179 Note: References to UNIX also apply to Linux.x. If your current 6. see the following online PDF titled. NOM has been replaced with OpsCenter.0 operations that may not be documented elsewhere in the NetBackup documentation set.0 See “About NetBackup Compatibility Lists” on page 24. NetBackup 7.0 Additional Operational Notes contained in Technote number 337179 on the Symantec Support Web site. 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.symantec. Platform and operating system support changes in NetBackup 7. unless otherwise stated. For additional operational note information about this release. ■ ■ .

■ Clustered media server support changes New NetBackup 7. most of the add-on products and database agents are now installed with the NetBackup server or the client package. configuration is still required.0 and remain clustered. The installation script displays a list of the packages it finds that must be removed.0 media server installations cannot be clustered. the older versions of any listed products here must be removed before an upgrade to NetBackup 7. However.x clustered media servers can be upgraded to version 7.Operational Notes NetBackup installation and start-up notes 51 ■ UNIX package consolidation In NetBackup 7. A valid license is still required to enable the product. SYMCnbenc. and others. SYMCnbdb2. For example. 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. VRTSnbdb2. For Solaris server upgrades. The process to install and upgrade these products remains the same. The Japanese and the Chinese language packages remain as separate add-ons. VRTSnbenc.0. . If product configuration was required previously (such as db2_config).0. Separate installation for these products is no longer needed. existing 6.

Technote 275107 on the Symantec Support Web site contains more information. The following instructions clarify how to install NetBackup client software in Solaris 10 non-global zones. the client push-install or local install is done normally. make sure that /usr/openv exists as a link. and gzip. ■ To provide clarification for installing NetBackup client software in Solaris 10 non-global zones 1 In the global zone. These commands must be present to have successful UNIX installations.52 Operational Notes NetBackup installation and start-up notes ■ All compressed files are compressed using gzip. the gzip and gunzip commands are expected to be in /usr/contrib/bin. use the following procedure. If the server does not have a master or a media server on the global zone. For all UNIX platforms except HP-UX. Please see the appropriate installation guide. Installation scripts add that directory to the PATH variable. The installation of these files requires that gunzip. On HP-UX systems. For example: # ls -al /usr/openv rwxrwxrwx 1 root root 10 Aug 23 15:13 /usr/openv -> /nonglobdir/openv . For example: # ln -s /nonglobdir/openv /usr/openv # ls /nonglobdir/openv /nonglobdir/openv: No such file or directory # ls -al /usr/openv rwxrwxrwx 1 root root 10 Aug 23 15:13 /usr/openv -> /nonglobdir/openv 2 In the non-global zone. On a server whose non-global zone does not use a read-only loopback device for the /usr directory. create /usr/openv as a symbolic link to the location in which you install the software to in the non-global. and has a sparse non-global zone using a read-only loopback device for the /usr directory. be installed on the machine before NetBackup is installed. That needs to be done even if the global zone does not have that directory. NetBackup server is supported only in a global zone. the binaries are expected to be in /bin or /usr/bin and that directory is a part of the root user’s PATH variable.

make sure that the directory link exists and is writable. Alternatively./ drwxr-xr-x 18 root bin 512 Aug 18 15:30 . and has a sparse non-global zone using a read-only loopback device for the /usr directory. Verify the directory that /usr/openv is linked to./ 4 Client push-install or local install can now be done normally according to guides. For example: # ls -al /usr/openv rwxrwxrwx 1 root other 10 Aug 18 11:39 /usr/openv -> /opt/openv/ 2 In the non-global zone.Operational Notes NetBackup installation and start-up notes 53 3 In the non-global zone. the /usr/openv in a default installation is a link to /opt/openv. And you can link /usr/openv to /BASEDIR/openv. create a writable directory where the /usr/openv points to.0 . If the server does have a master or a media server on the global zone. For example: # ls -al /nonglobdir/openv total 32 drwxr-xr-x 9 root bin 512 Aug 18 15:23 . the master or the media server can be installed in a base directory (BASEDIR) other than the default /opt.. 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. use the following procedure: To provide clarification for installing NetBackup client software in Solaris 10 global zones 1 In the global zone. For example: # mkdir /opt/openv 3 Client push-install or local install can now be done normally according to guides.

Users that are assigned to the Administrators Group and are not the official administrator cannot install NetBackup in UAC-enabled environments. ■ To install NetBackup on Windows 2008/Vista/2008 R2/7 UAC-enabled environments.54 Operational Notes NetBackup installation and start-up notes During an upgrade to NetBackup 7. ■ . ■ Beginning with NetBackup 7. 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. 142. you must manually delete the OIDs because the vxlogmgr cannot access them. and Solaris platforms. 113. and 157. disable UAC. You can display these log files with vxlogview in NetBackup 7. However. PDDE is non-functional.conf file that specifies the subdirectory for their log files (<oid>. This may occur for the following OIDs: 102. You must completely remove the NetBackup client and then install the NetBackup server software. That includes all transaction logs and database files in the data directory including BMR if it is configured and in use. This occurs because the OIDs do not have an OID entry in the nblog. To allow users in the Administrators Group to install NetBackup.0. Follow the instructions in the NetBackup Installation Guide for UNIX and Linux. Like the other scripts in the netbackup\bin\goodies folder. (You would then modify nbmail.cmd to the netbackup\bin folder. -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. 120. If you think you may need to report a problem in a previous release. nbmail.cmd is installed to the netbackup\bin\goodies folder.0. You can remove these OIDs after the upgrade.cmd at that location for it to take effect. If you install NetBackup server on top of an existing NetBackup client to upgrade the client to a server. it is necessary to have enough free disk space to accommodate three complete copies of the NetBackup database. then you may want to keep them for that purpose.0.LogDirectory=name). 113. 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. you must log on as the official administrator.0 if you specify the following. you now have to copy nbmail. And oid is the 102 . 153. That issue applies to SLES. Red Hat. and so on. It had previously been installed to the netbackup\bin folder. 120.

However. Symantec recommends the following Microsoft updates when you run NetBackup on Windows operating systems: ■ ■ Microsoft storport hotfix. See the NetBackup Troubleshooting Guide for UNIX.Operational Notes NetBackup installation and start-up notes 55 ■ The NetBackup Tape Device Driver Installation wizard is no longer present on the installation media.47 (required) http://support. In most cases.i386/ppc). This fix applies to Windows x86 and x64.0 than previous releases.com/support/ oem_product_detail. you can download them from the NetBackup Support Web site at the following location. you cannot upgrade those systems to 7.0.asp?oemid=65 ■ ■ ■ The default shared-memory requirements on UNIX systems are greater for NetBackup 7.x ■ .asp?p_id=253&oemid=65&oemname=QLA2340 All other Q*Logic HBAs use latest driver & BIOS (suggested)http://support. The Symevent driver updates (required).x on any 32-bit systems other than FreeBSD and Macintosh.com/support/ oem_product_detail. See the NetBackup Installation Guide for UNIX and Linux.com/docs/287850 ■ In a future release. This fix applies to 32-bit and 64-bit versions of Windows Server 2003/XP/Vista: (suggested) http://support.com/?kbid=936357 ■ ■ Symantec AntiVirus.1.veritas.2 for Corporate Edition) and latest update (required).com/?id=932755 Microsoft microcode reliability update.com/support/ oem_product_list.qlogic. the manufacturer’s device drivers or the drivers that are included with the operating system are appropriate. UNIX 32-bit system support has been discontinued for all platforms except FreeBSD and Macintosh (universal . on both SP1 and SP2: (required) http://support. Windows and Linux.microsoft.asp?p_id=253&oemid=65&oemname=QLA2340 QLA2340 Q*Logic HBA BIOS 1.microsoft. If you currently use NetBackup 6. Update to latest driver version. http://support.qlogic.15 (required) http://support. it may be required that clients connect to the master server to complete an installation. In environments where the NetBackup tape device drivers are required.qlogic.4. you can migrate the NetBackup 6. ■ ■ Symantec recommends the following third-party updates when you run NetBackup on Windows operating systems : ■ QLA2340 Q*Logic HBA driver 9. Update to latest version (10.

Symantec recommends that all customers running HP-UX 11. the installation may fail.23 install the patch (PHCO_33431). ■ ■ NetBackup LiveUpdate NetBackup LiveUpdate is not compatible with Open VMS (UNIX) or Novell operating systems. File Manager on a Solaris system. However. .23.56 Operational Notes NetBackup installation and start-up notes catalogs and databases on those systems to a supported 64-bit platform system and then upgrade to 7.0 media server installations cannot be clustered. NetBackup product dependencies. ■ Symantec recommends that you have the master server services up and available during a media server upgrade.) when the DVD is inserted into the drive.0. Any 32-bit media servers and clients that use NetBackup 6.x clustered media servers to version 7. Follow the installation instructions that are provided in the NetBackup 7.0 documentation set.x are compatible with the 64-bit master servers that use NetBackup 7.0.0 and they remain clustered. NetBackup cluster The following list shows the items that relate to NetBackup cluster: ■ New NetBackup 7. you can upgrade existing NetBackup 6. Symantec recommends that you do not use this window to install NetBackup products because unpredictable results may occur. For more information about these patches. refer to Table 3-1 in Chapter 3. See the NetBackup Installation Guides for more information about migrating NetBackup master servers from 32-bit to 64-bit. If you do not install the patch before you install NetBackup on a system with an updated version of 11. 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. 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. The operating system may open a user interface window (for example.

you should log into the server using the virtual name that is associated with NetBackup.0. ■ These changes can be accomplished using the following commands. With the need for increased security.com/docs/288471.Operational Notes NetBackup installation and start-up notes 57 ■ When a fault occurs in a cluster resource group for NetBackup in a SunCluster configuration. you may encounter Windows event log messages that indicate the Sybase service (SQLANYs) failed to start. When you install or upgrade NetBackup on Sun Clusters. When you configure disk pools or storage servers. See http://entsupport. 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. you must be able to configure NetBackup with access control (NBAC) in a clustered NetBackup server environment. failover of the NetBackup resource group does not occur. SFW-HA 4. Set the pmf Retry_count parameter to 0. You should expect these messages and know that they do not reflect a problem with the upgrade. See http://entsupport. only basic disk supports the use of application clusters. When you configure disk storage units.1. # # # # 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 .symantec.com/docs/278307 for more information. When you launch the NetBackup Administration Console. These messages are generated in a short period of time – normally a window of two to three seconds.2).symantec. you should increase the NetBackup resource offline timeout to at least 600 seconds. When you upgrade clustered NetBackup servers to NetBackup 7. application clusters are not supported. For VCS Windows (SFW-HA 4. These messages coincide with the cluster configuration portion of the upgrade.0. Note that running these commands causes shutdown and restart of NetBackup. After you install or upgrade NetBackup on UNIX clusters other than SunCluster. The failure in this situation could happen if the NIC (network) or other resources could not come online. Symantec recommends that users make sure patch 278307 is installed before you install or upgrade to NetBackup 7.

SERVICE_CMD[0]="/etc/cmcluster/netbackup/monitor" . Open the package control script /etc/cmcluster/netbackup/netbackup. Uncomment the following parameters on all of the nodes in the cluster: .18 (or 11. the NetBackup cluster resource group may become unmanageable when the NetBackup package (Virtual IP) fails to come online or offline.17) on more than one node.config). Offline and failover of the cluster package does not occur. You do not need to update the cluster because the configuration has not changed.SERVICE_NAME[0]="netbackup" . ■ ■ ■ NetBackup Documentation Notes The following information should be considered as part of the NetBackup 7.0 on the HP Service Guard v11.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: . do the following after you install NetBackup. and all cluster nodes: ■ Open the NetBackup package configuration file (/etc/cmcluster/netbackup/netbackup. Please refer to this document for information regarding the NetBackup Enterprise Vault migrator.58 Operational Notes NetBackup Documentation Notes ■ If you install 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.SERVICE_RESTART[0]="-r 2" Remove the hash symbol ('#') from the beginning of each of these three lines to uncomment the parameter. If you encounter this issue. Change the name of the configuration entry for subnet mask from MONITORED_SUBNET to SUBNET on all of the nodes in the cluster. The following new documents are packaged with NetBackup 7.

a problem can occur if you use spaces in the pathname.sun.do?bug_id=6901233 for more information about this issue. When you run on a non-English locale. For Windows and UNIX installations.com/bugdatabase/view_bug. The NetBackup – Java Administration Console does not support user-defined characters (UDC) and vendor-defined characters (VDC) because of the implementation of Java’s encoding converters. you must remove the localized contents that are installed on your system. You should install NetBackup client software to a path that does not contain spaces.0 on top of an existing localized version NetBackup. http://bugs. 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. If you encounter this issue. apply the Solaris patch that Sun provides to fix this issue 6901233. the install path must not contain multi-byte characters. 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. 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. ■ ■ ■ ■ ■ ■ ■ . without installing the localized contents in the Language package CD first.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. 6901233. If you plan to install an English version of NetBackup 7. Installation to paths that contain non-ASCII characters may cause backup or restore failures. See. This problem is caused by the Sun Microsystems™ issue.

At the time of this release. Client) Policy Name Policy KEYWORD (Windows Only) Backup. the use of localized characters (for example. Differences in operating system architecture and encodings may cause non-English file names and folder names to be displayed incorrectly within the user interface. like script. You cannot use the NetBackup-Java Administration Console to administer localized Windows and UNIX systems. EMM server. Volume Database Host. Media Host. multi-byte characters) is not supported in: ■ Any database object names. That can also cause backup and restore failures. including the use of previous versions of those NetBackup database agents with NetBackup 6. non-ASCII. 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. and functional issues may arise. filegroups. ■ ■ ■ The following NetBackup user-defined strings must not contain Multi-byte characters: ■ Hostname (master server. or batch file locations That applies to all supported platforms. and so forth The path names of database files. like instances. Localized characters are displayed incorrectly. and Restore KEYWORD (Windows Only) ■ ■ ■ . template. tablespaces.60 Operational Notes Internationalization and localization Notes ■ NetBackup does not support the mixing of Windows and UNIX platforms in foreign language environments.0 servers. data files. portals. databases. or other database storage locations The path names that are specified in the policy Backup Selections. transaction logs. directories. Archive. media server.

Operational Notes NetBackup Bare Metal Restore 61 ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ Storage Unit Name 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. This command prints the system resources limit. More specifically. use the following procedure to change the ulimit parameters to “unlimited” and run bmrsetupmaster again. Run the following commands to change the limits: ■ ■ ■ ulimit -s unlimited . this issue occurs on a 7. This issue occurs because the stack size. data seg size. Set the parameters to unlimited.3 platform. and max memory size parameters. If you encounter this issue. and max memory size ulimit parameters on the system are set too small.0 or greater BMR master server on an AIX 5. data segment size. When that happens. To change the ulimit parameters: ■ Run the ulimit -a command on the BMR master server. Check the current limit set that is used for the stack size.3 or greater platform. data parsing fails while the BMR database is populated.

x. You can permanently change the resource limits by manipulating the “/etc/security/limits” file on the system. About importing a pre-NetBackup 7. The SRT that contains NetBackup 7.0 SRT does support restores of pre-7.5.X ) clients. section in the NetBackup Bare Metal Restore Administrator’s Guide. SRT creation fails with RHEL5.0 the boot server does not support copying of 6.0 or a higher version NetBackup Client can be used to restore back-level NetBackup clients. 6. To migrate from BMR 4. got "Red Hat Enterprise Linux Server ■ ■ ■ ■ ■ ■ ■ .X and 6. However a NetBackup 7. You cannot directly upgrade an older standalone BMR product (BMR 4.5.0 the boot server does not support importing of 6. but it can be migrated to NetBackup 7. About copying a pre-NetBackup 7. SRT creation fails and the following error message appears: V-125-380 /var/temp/bmrmediaDb1K6p/.X and 6.5. BMR does not support restoring the Remote Installation Folder location of an RIS Server.X or 6.0.X and 6.62 Operational Notes NetBackup Bare Metal Restore ■ ■ ■ ulimit -d unlimited ulimit -m unlimited Run bmrsetupmaster to configure the BMR master server.X SRT. You can also restore the RIS server by editing the client configuration.discinfo(2): expected "Red Hat Enterprise Linux Server 5".0.3 If RHEL5. Upgrading and migrating from older BMR versions. About creating a shared resource tree (SRT) for Windows Starting with NetBackup 7. ■ You can upgrade to NetBackup 7.0 only from NetBackup 6.7) to NetBackup 7. You can restore an RIS Server using the System Only feature.0 SRT Starting with NetBackup 7.X SRT.3 media (CDs) is used for SRT creation.0 the boot server does not support the creation of 6.7.0 NetBackup ( for example. BMR can only support the restoration of a client back onto the original hardware.0 SRT Starting with NetBackup 7. and removing the volume that is used for the Remote Installation Folder location from the map. When EMC PowerPath software is running on the original client. The Windows Fast Restore feature requires a DNS server to be able to resolve the client and Servers.X SRT. refer to the.5.

For 64-bit versions of Windows OS. This means.2. ■ . To avoid this problem. Windows x64 client systems cannot be restored using the legacy DOS-based Restore.exe) that can be invoked from within DOS environment.Operational Notes NetBackup Bare Metal Restore 63 5. Windows x64 client systems that run VxFS for Windows (SFW) cannot be restored. however it also disables creation of a RHEL5. ■ No support for legacy DOS-based restores on Windows x64 clients. it can be used to restore a RHEL5.1. Hence. The loaded media is not corrrect.3 SRT.ok. Currently.) Symantec recommends that you use Method 2.3 client.2 OS media. When you create an SRT this way. Unmounting media. Because of this issue. Method 2: On the BMR boot server. the BMR Fast Restore is the only mechanism of BMR Restore for Windows x64 client systems. Microsoft did not ship 16-bit installers. the temporary OS installation of 64-bit OS for BMR cannot be initiated from a DOS environment. (RHEL5.conf ■ Search for the string Red Hat Enterprise Linux Server 5 and replace all occurrences with Red Hat Enterprise Linux Server 5. BMR cannot protect Windows x64 client systems that run VxFS for Windows (SFW). No support for Veritas Storage Foundation (VxFS) for Windows (SFW) on Windows x64 clients. In addition.1... use one of the following methods to create an SRT: ■ Method 1: Use RHEL5.0. the legacy DOS-based Restore mechanism cannot be used for the reasons previously stated.. Windows x64 client systems that run VxFS for Windows (SFW) cannot be restored. Hence. Windows x64 client systems cannot be restored using the legacy DOS-based Restore.2 SRT. or 5. and a 5. 5.3".3 introduces the new device drivers that are not a part of the default kernel in RHEL5.. Windows clients that run SFW can be BMR restored using only a legacy DOS-based Restore mechanism. As a result. open the following file: /usr/openv/var/global/createsrt. For Windows x64 client systems.0. This restriction exists because a DOS-based Restore requires a 16-bit OS installer application (winntsetup. This issue is valid because Windows clients that run SFW cannot be restored using Fast Restore mechanism of BMR. This change should enable creation of a RHEL5.3. there is no work-around available. 5.please try again.

However. the behavior is undefined and unknown. 16-bit code cannot be executed. when you map certain objects such as slices or volumes. a 64-bit (x64) Windows boot server at NetBackup 6.5 client into the SRT and use that SRT to restore the Solaris 10_x64 server. When you use the BMR Administration console to map an object.64 Operational Notes NetBackup Bare Metal Restore ■ No support for Legacy Boot Floppy Wizard on Windows x64 boot server. BMR informs the user that it is not supported on that particular version of the OS.5 Solaris 10_x64 client that has a NetBackup 7. install the NetBackup 6. the original object is not disabled. the Legacy Boot Floppy Wizard is not available on a 64-bit boot server .5. 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.5. a BMR boot server can be installed on a Windows x64 system as well. but BMR backup may succeed in case of such systems. For self-restores to the same physical GPT disks. On a 32-bit Boot Server.4 or greater can correctly host a 32-bit or a 64-bit SRT.5.11 client fails the following occurs while the configuration is mapped: ■ ■ ■ ■ . That does not mean that the mapping has failed. In general.5 Solaris 10_x64 client fails. although the GPT disks are implicitly restored as MBR-based disks. BMR may be able to restore the system. a 32-bit (x86) Windows boot server that is upgraded to NetBackup 6. Thus. If the backup was successful. Do that even if the boot server version is 7. Similarly. No support for GPT disks. No work-around exists to completely support GPT disks. BMR does not support Windows x64 client systems that have one or more GPT disks. If you try to run the wizard. the source object is disabled in the user interface if mapping is successful. a "System-only" restore should work correctly. The restore of a BMR 6. That indicates that it cannot be mapped again unless you un-map the object. Restore of a BMR 6.0. This limitation exists in the 64-bit Windows OS. On 64-bit boot server .0 client that is installed as part of the SRT creation process can fail intermittently. as Windows 2003 and XP do not support system or boot volumes on GPT disks.5.5. Running this wizard can involve running some 16-bit code. A BMR Restore using such a mapped configuration still completes successfully. this code executes under WOW32. A DDR restore of a BMR HP-UX 11. BMR does not distinguish between the 32-bit and 64-bit boot server on Windows. Also. even if the mapping completes successfully. For Solaris 10_x64 client configurations.4 and greater is able to correctly host a 32-bit and a 64-bit SRT. With the release of NetBackup. To avoid this issue. however.

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. perform a system-only restore or a self restore. boot loader may be installed on /dev/sda. you if remove this account. (It is not created on non-Windows boot servers. Then during the first boot. A bmradmin account is created on a Windows BMR boot server during the boot server registration.) This account is created unconditionally because at the boot server installation and registration time. . FastRestore operations do not require this account. If you determine that you do not need to perform legacy restores. it is not clear whether you may require a Legacy SRT or not. However. /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. and then decide that you need it to run a legacy restore. set the disk order in the BIOS to reflect Primary Master > Primary Slave > Secondary Master > Secondary Slave before you attempt a restore. if the disk order that is specified in BIOS is not: Primary Master > Primary Slave > Secondary Master > Secondary Slave. you must recreate the account manually. To avoid this issue. 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. For example. during a restore. Manually creating this account requires assistance from Symantec Support because it is originally created with a predefined password and other attributes. Legacy SRTs require this account to perform legacy restores that use a CD or floppy boot option. then you can remove this account. then the first boot after a successful restore may fail.Operational Notes NetBackup Bare Metal Restore 65 ■ ■ The client uses VxVM-based multiple disk groups The disks from different disk groups are swapped To avoid this issue. assuming it to be hd0. ■ On a Linux client. ■ A bmradmin user account that is created on a Windows boot server during a boot server installation is saved and not deleted later.

0 or higher restore the back-level NetBackup clients. you can identify these files by the suffix . That is due to the RH SEL system always returning the ACLs as EAs. NetBackup also trims the name to 31 characters if necessary. The database server name cannot exceed 31 characters.0 release. In NetBackup 7.x releases.0. However. the OS architecture type that you select should be 32-bit. select 64-bit as the OS architecture type.0. you must have user_xattr enabled in the mount parameters. In addition. 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. ■ ■ ■ ■ .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.0.swidtag. from VERITAS_NB_hostname.5.0. For NetBackup 7. While you install the NetBackup client into the SRT. These files do not affect NetBackup functionality. NetBackup installs two XML files on each NetBackup host. The ACL mount parameter setting has no effect.1 has been made in NetBackup 7. validation of data files that reside in raw devices may fail even though the Clone operation was successful. Functionality that is introduced with the NetBackup 6. If you want to install NetBackup client versions that are older than 7. there is a restriction within that version that requires the database server name to be less or equal to 31 characters. To back up and restore ACLs on a Red Hat SEL volume. bmrsrtadm gives the appropriate error message if there is any incompatibility between the SRT OS architecture type and the NetBackup client version. You may receive an error that states the validation failed for specific paths along with the paths.0 into the SRT.domain_name to NB_hostname in /usr/openv/db/bin/servername. NetBackup has been modified to change the server name. ■ General NetBackup operational notes The following list contains the general NetBackup information: ■ An upgrade to SQLAnywhere 11. To support software system management standards.6 or later releases may not be available in the 7. You can use a shared resource tree (SRT) that contains a version of the NetBackup client of 7. This functionality is available in later NetBackup 7.

the NetBackup services do not automatically attempt the service credential renewal. %Program_Files (x86)%\VERITAS\NetBackup\var\vxss\credentials\* If you use this workaround.veritas. if NBAC is enabled. %Program_Files%\VERITAS\NetBackup\var\vxss\credentials\* ■ For Windows (64-bit). A potential for data loss has been seen where Distributed File System Replication (DFSR) paths may be skipped on a backup. However. To avoid this issue. the NetBackup services may cause a core-dump after one week of running. The typical service credential validity period is one year. That means that the credentials expire after one year. create a cron job or scheduled task to "touch" the existing credential files that ran at intervals of fewer than seven days. Due to an error.0 host. a core dump of dbeng9 occurred.Operational Notes NetBackup Access Control 67 ■ After you perform a Full Catalog Backup Recovery with Heap Checking enabled.com/docs/336578 ■ ■ NetBackup Access Control The following list contains the items that pertain specifically to NetBackup Access Control (NBAC): ■ On a NetBackup 7. 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 . A failure in ‘Renewing’ a service credential causes this issue. http://support. You can delete and ignore this core dump. it is reported as a Status 0 if the DFSR path exceeds 256 characters and DFSR is backed up with shadow copy. Testing showed that the catalog recovery completed successfully and that bprecover handled the core dump issue appropriately. /usr/openv/var/vxss/credentials/* For Windows (32-bit). The following files are the files that need to be touched: ■ ■ For UNIX. this scheduled task can cause some of the NetBackup processes to dump core. See the following Technote on the Symantec Support Web site for more information about this issue. NetBackup attempts to renew a service credential when it is seven days old to ensure continual availability of the credential.

or the file being restored was not readable by the user at that time that it was backed up. 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. Symantec recommends that the NBAC NBU_Security Administration group never be modified. you must perform a bpnbat -login. Ad the destination client can only be the local machine. .. During the upgrade. A restore fails to recover some (or all) of the files with the message. 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.You must first calculate the number of seconds that would be.com/docs/288471.68 Operational Notes NetBackup Access Control ■ Extend the credential expiry from the default of one year to longer term. In this example. make the non-root NBU_Admin a member of the "Backup Operator’s" operating system group on Windows. "Access denied for restore of file". the installer connects to the AZ server and upgrade NBAC data. ■ .Go to /usr/opt/VRTSat/bin (UNIX) or %Program_Files%\VERITAS\Security\Authentication\bin (Windows). If the upgrade of NBAC data fails then a message appears and informs you that you must manually run bpnbaz -upgrade. Perform the following steps in an example that extends the expiry from one year to five years: . http://entsupport. The following symptoms occur: ■ ■ ■ ■ The destination client dropdown field is grayed out in the Backup. To avoid this issue. With the need for increased security. Before running this command. On a Windows system. it is critical to be able to configure NetBackup Access Control (NBAC) in a clustered NetBackup server environment.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.symantec. Archive. the total number of seconds is 157680000 (60 * 60 * 24 * 365 * 5). See. That happens if the user does not have write permission on the destination of the restore. . The user that is specified during bpnbat -login should therefore be a member of the NBU_Security Admin group. Members of this group have the necessary privileges. you should run the bpnbat -login command before you start the upgrade. and Restore (BAR) user interface.

■ The following applies to any agent that uses Granular Recovery Technology (GRT) Active Directory.Operational Notes NetBackup database agents 69 The term non-root on Windows means that you are not an Administrator. ■ ■ Add the following to the end of the notes.4 releases.1 and R6. This flag allows retries to happen if and when the operating system returns an unexpected EINTR while LN performs semaphore operations. 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. customers need to set the flag DEBUG_SEMOP_ERRNO0_EINTR in the notes.nsf/Search?SearchView&Query=JCHN5QVL3E .0 on Linux Support for Lotus R6.0 on Linux requires a hotfix to resolve the following SPR: SPR#JCHN5QVL3E (which addresses a transaction log recovery issue). or SharePoint. The last character in ERRNO0 is a zero.ini file for Domino to work properly with NetBackup.0.5.microsoft.0.com/ldd/r5fixlist.5.ini file. Windows compressed images are not restorable to Lotus Domino servers on UNIX.lotus. In these releases. See www-10.0. you must make a change to the notes. Restart the Domino server partition.5.3 and Lotus R6. NetBackup database agents This section contains the general operational notes that can apply to more than one NetBackup database agent. In addition. A hotfix is available from Microsoft to address this issue. Exchange. 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.com/kb/955012 The remaining topics within this section contain the operational notes that are specific to the individual database agents that NetBackup supports.ini file for each Domino partition: DEBUG_SEMOP_ERRNO0_EINTR=1. Requirements for Lotus r6. ■ The hotfix was integrated into the R6. http://support.3 and Lotus r6. After you install the hotfix on a Lotus Domino server.

For each Domino partition. For Lotus R6.lotus.ini file is not required.70 Operational Notes NetBackup database agents ■ Requirements for Lotus r6.ini file: DEBUG_SEMOP_ERRNO0_EINTR=1 (NOTE: The last character in ERRNO0 is a zero.com/ldd/r5fixlist. See.5.nsf/Search?SearchView&Que ry=JCHN5QVL3E. perform the following steps: ■ Add the following line to the end of the notes. See: www-10. www-10.5. These issues have been fixed in R6.0 on Windows Support for Lotus R6.3 or R6.com/ldd/r5fixlist.nsf/Search?SearchView&Que ry=JCHN5QVL3E ■ Requirements for Lotus r6 and r6.5.nsf/Search?SearchView&Que ry=THUR5LPPW9.0.) ■ Restart the Domino server partition.0.5.ini file for Domino to work properly with NetBackup. www-10.3 and Lotus R6.0.com/ldd/r5fixlist.5. which involves a transaction log recovery issue.lotus.1.3 or r6.03 and Lotus r6.0.0 requires an IBM hotfix to address SPR# JCHN5QVL3E. 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 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).0 does not support the redirection of public folder items. the setting in notes. ■ Requirements for Lotus r6. GUI initiation of an off-host snapshot backup . See.4 and R6.0.1. R7.0 on Solaris SPARC and AIX Support for Lotus R6.5.0. A single IBM hotfix is available to address both issues. You should remove the previous Lotus hotfixes before you install this new combination hotfix. and going forward.5 on Linux Support for any version of Lotus R6 or R6.4 and R6.5 on Linux requires a change to the notes.5. This issue has been fixed in R6.lotus.5.

use a NetBackup Client user interface on a NetBackup server to change the destination client value to the virtual server name. The work-around for this issue is to configure the FQDN so that it is resolved to the correct IP address. multiple “seed” emails from the backup service account may be sent to the mailbox being restored. the backup fails. you may experience failures. it may not be possible to change the destination client value to match the virtual server name. 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. 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. To resolve this issue. Instead. That problem occurs when you perform an Exchange snapshot backup attempt with Allow multiple data streams set on the policy. Modify the NetBackup server’s hosts files or correct DNS entries to resolve that. 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. instead of a node name. or with Microsoft Information Store:\* in the file list. In that case. Symantec and Microsoft are working on a solution for this problem.Operational Notes NetBackup database agents 71 When using the NetBackup Client user interface or the bpbackup command to initiate an Exchange off-host alternate client backup. During a Mailbox item restore. ■ Restoring Exchange in a Cluster When you restore data in an Exchange cluster environment. Bpresolver may return the list of Exchange servers to perform the backup in a Fully Qualified Domain Name (FQDN) format. To work around this issue. increase the value of the Client Connect Timeout in the master server Properties > Timeouts. 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. ■ ■ ■ ■ . See the "Testing Configurations Settings" section in the NetBackup for Exchange System Administrator ’s Guide for instructions regarding a manual backup operation. try the browse or restore operation again. Exchange snapshot backups fail with status 41 "Network connection failed". However. use the NetBackup Administration Console to initiate a manual backup for that Exchange policy. When you attempt to browse or restore an Exchange mailbox from a GRT image from a Windows 2008 R2 Exchange server. and with a large number of storage groups or databases in the file list.

exe memory usage grows when a snapshot of multiple storage groups or Exchange 2010 databases is processed. To resolve this issue. You should initiate the restore from the active DAG node or a NetBackup server to properly see the activity status. granular level restores may fail. ■ ■ ■ ■ ■ ■ . the restore status may be empty from the backup and restore user interface. 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.72 Operational Notes NetBackup database agents ■ Restores of Exchange 2010 database in a Database Availability Group (DAG) environment notes: ■ When you restore a database to a recovery database. Instead use the node that contains the active DB being restored to. that might happen with a roll-forward recovery. When you restore a database or databases to a different DAG than where it was backed up. Then use VShadow to make sure that the snapshot volume has been deleted. 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. The company field of task objects does not get properly restored with Exchange 2010 granular recovery. When you restore databases or granular items of a DAG backup. Instead. Selecting one backup image at a time does succeed. The problem occurs when you recover from an Exchange Instant Recovery backup and one volume is rolled back while another is not. use the node name where the RDB exists or the stand-alone Exchange 2010 server. you cannot use the DAG virtual name as the destination client. With this provider. That leaves a partial snapshot set and an invalid IR copy of the backup image in the catalog. expire Copy 1 of the backup image in the catalog. The bpfis. in which the database volume is rolled back and the log volume files are copied back. Snapshot and catalog clean-up not performed after an Instant Recovery restore rolls back some snapshot volumes and copies back of others. you cannot use the DAG virtual name as the destination client. the rollback consumes the snapshot volume. For example. The problem occurs only with the default (Microsoft System) VSS provider. The status is empty if the restore is initiated from a node in the DAG. ■ ■ When you select multiple backup images from a DAG backup with Enable Granular Recovery selected. Initiate the user backup from the active DAG node or manually start the backup from the NetBackup master to properly start the backup.

■ ■ NetBackup for Microsoft SharePoint The following topics contain the operational note information that relates to the NetBackup for Microsoft SharePoint Portal. . This issue does not impact the ability to mount after restoring only an Exchange offhost full backup. This issue will be resolved shortly after the release of NetBackup 7.exe process memory usage grows by a few megabytes per storage group or Exchange 2010 database. Exchange 2010 offhost backups are not supported in NetBackup 7. To prevent restore failures. The workaround is to make sure that you have sufficient virtual memory to accommodate this growth. or Exchange 2010 DAG). ■ Operational Issues The following operational issues exist for the Microsoft SharePoint: ■ When the SharePoint Search Index service updates the databases. Exchange 2007 CCR.0.0. A special procedure is required to mount the database after the restore. all load-balanced Web sites must be uniformly identified in IIS using either host headers or IP addresses. or to break up your backup into smaller snapshots.Operational Notes NetBackup database agents 73 In NetBackup testing. ■ Instant recovery backups are not supported for Exchange in a cluster environment (Exchange 2007 cluster. If a single snapshot job processes a large number of storage groups or Exchange 2010 databases. the bpfis. repeat the backup or restore operation until successful. 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. 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. Environments which mix host headers and IP addresses across load-balanced servers are not supported. Support will be added shortly after the release of 7. If that occurs.0. the process virtual memory size can approach or exceed one gigabyte. but not both. General Setup The following is a list of general items pertaining to the NetBackup for Microsoft SharePoint: ■ When you use SharePoint 2003 load balancing. the IIS Default Application Pool identity must be a valid SharePoint user ID .

is unequal number of parenthesis on the database name field. attempt the backup a second time. ■ When you restore the most recent version of a document. the bpfis child job gets a status 130 error on first attempt. As a workaround. The SharePoint 2003 restores to the current date and time. restore the item and any attachments that exist. The restore does recover the files names with the correct characters. You can remove these files if you are low on space. A SharePoint backup fails with a bpresolver core. however a status 5 error occurs. Some items are not handled properly using GRT with Search Center template. make sure that you have an equal number of parenthesis that match in a database name. To resolve this issue. That is intentional behavior for debugging purposes. the SharePoint debug files on the backend are created during the backup in the INSTALL_DIR\VERITAS\NetBackup\Temp\ directory. Some items are not restored using GRT with the Tabs template. As a workaround. The metadata restore is for SharePoint 2007 only. picture. The Search Center template. or attachment the restore works. ■ ■ ■ ■ ■ ■ A deleted list item that is in a Content-DB with Chinese characters may not restore to the original location. The second attempt is successful. Restoring SharePoint picture libraries to the original location may fail when there are empty containers preceding the picture library. The SharePoint GRE restore view status displays incorrect characters for i18n Simple Chinese. The cause of this issue. . To avoid this issue. These files are not removed after the backup. When you perform a SharePoint granular backup on a federated farm. To work around this issue. Discusion Board list item fails to restore. 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 data can be recovered by redirecting to a file system or restoring the sites content database. to a file system and then add it to SharePoint. As a workaround.74 Operational Notes NetBackup database agents ■ The metadata modified date is restored as the restored date. When there are no empty containers preceding the picture library. restore the content database that contains the Tabs template site. restore the content database that contains the Search Center template site. The Search Center with Tabs template has some missing items for the restore. then the restore works.

nbrb.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. Sybase has changed its name from Adaptive Server Anywhere (ASA) to SQL Anywhere. the online Help cannot be opened.On UNIX/Linux platforms: /usr/openv/var/global/server. may cause a core dump to occur on a master or remote Enterprise media server that has Sybase 11. If this issue occurs.) . AIX.conf (This is true as long as this file has not been moved to a different location. This issue affects the HP-UX. Change: tcpip(LocalOnly=Yes. This problem originates within the Windows 64-bit SDK and is expected to be resolved in a future release.0. restore. In addition. use the following procedure as a work-around: ■ ■ ■ Stop NetBackup.ServerPort=13785) To: tcpip(LocalOnly=Yes. and nbars do not function properly. It can be missed or specified as LocalOnly=NO or LocalOnly=YES. dbsrv11. The Sybase service.1 installed and IPv6 enabled. In addition.ServerPort=13785) NOTE: LocalOnly=Yes is optional. and Solaris.On Windows platforms: install_path\NetBackupDB\CONF\server. SQL server agent When you use the NetBackup for SQL Server user interface on 64-bit platforms. platforms. or list a storage unit. If you encounter this issue.conf ■ Start NetBackup. You can locate the database server configuration file at the following locations: . .0. Until then. the Windows service name has changed from ASANYs_VERITAS_NB to SQLANYs_VERITAS_NB.ipv6=NO. nbemm. you should know that the correct version of the item is restored and you can ignore the status 5 error. open the help file directly using the Windows Explorer: install_path\VERITAS\Help\nbmssql. Disable IPv6 by entering "ipv6=NO" in the database server configuration file.Operational Notes NetBackup database agents 75 If you encounter this issue. you are not able to back up. archive.

and a policy with two Enterprise Vault servers that point to the same index location.0. the files are restored to the system drive of the Hyper-V server. while . the Enterprise Vault redirected restore fails with a status 5 error. and Restore interface on Windows). ■ Backup of Virtual Machines(VM) fails if the files that represent the VM have volume GUIDs instead of a drive letter in the pathname. Archive. The following is an example of a volume GUID path: \\?\Volume{26a21bda-a627-11d7-9931-806e6f6e6963}\ If volume GUID paths exist in your Hyper-V environment. an incorrectly specified UNC path (share name) for the destination should cause the restore to fail. ■ 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. you must install NetBackup patch 7. For example.1 or later NetBackup for Hyper-V has a known problem involving volume GUID paths. Contact Symantec Technical Support to obtain the patch. with status code 5.0. 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 partial success occurs when you use an EV_INDEX_LOCATION directive. If the NetBackup/logs/AltPath folder is not present. The restore location on the system drive includes the server name and drive name as specified in the UNC path. Instead.1 or a later release.0.76 Operational Notes NetBackup Hyper-V 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. This folder must be present to perform a redirected restore. This issue will be fixed in a future NetBackup release. ■ 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.0. so that NetBackup fails the restore when a path is incorrectly specified.

NetBackup also saves the errors into separate logs. Policy. if the path of one or more of the VHD files are specified with a volume GUID. If you select.0 release. Number of Files and Offset) for report on any disk type. The Images On Disk report does not show data for a few columns (such as. and Status for Disk based reports. 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. 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.5 media server. and the Activity Monitor. That enables you to view specific error types such as tape errors in Tape log report or disk errors in the Disk log report. ■ ■ ■ The storage unit creation pages are not available in the Disk Pool wizard if the logged on host is a media server.0 media server.Operational Notes NetBackup interfaces 77 the VM is created. \\?\Volume{7b544c52-9cb7-11dd-a453-806e6c6e6963}\myVM\myvhd.vhd This issue will be fixed in the first update after the NetBackup 7. NetBackup stores the errors in the Media log. NetBackup Management > Reports > Tape reports > Tape logs. The Tape log report appears empty. . if you attempt to log errors from a 6. then the backup of the VM fails. no result is produced. However. These pages are applicable only for a master server. NetBackup interfaces The following subsections contain the release and operational information about the NetBackup interface. NetBackup does not log the errors into separate error logs. you can only view the errors in the Media log. The Disk Log report does not show information for the columns Schedule. such as the NetBackup Administration Console.

refer to the following Technote on the Symantec Support Web site. This problem is caused by the Sun Microsystems™ issue.com/bugdatabase/view_bug. http://entsupport. apply the Solaris patch that Sun provides to fix this issue 6901233. 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 Restore Marked Files dialog in the NetBackup-Java Administration console displays the Skip verification and force roll-back option as Overwrite existing files. ■ ■ ■ For more information about this issue and a workaround solution.sun. 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.symantec. If you encounter this issue. The names of these options will be corrected in a future release of NetBackup. The Skip verification and force roll-back option does not appear in Restore Marked Files dialog.com/docs/335933 ■ A Windows Manager that is configured for auto focus is not supported. 6901233. When you configure a Point in Time rollback restore. When you attempt to log on to the master server.78 Operational Notes NetBackup interfaces NetBackup java interfaces This section contains operational the notes that are applicable to NetBackup-java interfaces. http://bugs. General Notes The following list contains the general operational information that pertains to the NetBackup-Java Administration Console: ■ Reduced functionality (only the Backup.do?bug_id=6901233 for more information about this issue. Archive. the NetBackup-Java administration console hangs at a point when the following status statement appears. The NetBackup-Java administration console on Windows (WDC) cannot connect to a UNIX master sever with a Japanese package. Checking if NBAC is configured. however the label is misleading. The functionality of the Overwrite existing files option is the same as the Skip verification and force roll-back option. Auto focus means that windows are activated (get the focus) when you position the . See.

Remote display back of the NetBackup-Java Administration Console is not recommended. because it is probably displayed on the machine from where jnbSA was run. use the Style Manager -. one of the following happens: ■ Nothing. If this situation should occur. the last update that is made prevails.InternalError: Can’t connect to X11 window server using "host_name" as the value of the DISPLAY variable. 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. Before you start jnbSA. jbpSA. (That means the operating system command prompt was received. That eliminates the possibility of configuration conflicts if more than one administrator attempts administration tasks simultaneously on the same object. The command fails with no error message. very sluggish table scrolling with large numbers of rows. The following explains how to correctly set up a CDE environment.lang. ■ ■ . Other problems may occur that can cause the user interface to hang because of a Java Virtual Machine (JVM) failure. ■ java.Operational Notes NetBackup interfaces 79 mouse cursor over them. ■ Symantec recommends that only one administrator work on an object at a time. NetBackup Java does not run properly if the Style Manager has the following selected: Point in Window To Make Active.Window dialog to change the window behavior to Click In Window To Make Active. ■ If you are not set up properly to display to a machine from where you run jnbSA. Problems have occurred with certain user interface controls (such as. In the CDE environment. Memory requirements to run the NetBackup-Java Administration Console Symantec recommends that you run the console (jnbSA. 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. incorrect box operations. Symantec does not recommend running the NetBackup-Java Administration Console in a remote display back configuration. and table display problems with large numbers of rows). The JVM failures occur most often on AIX platforms. Reference the man page for the xhost command for additional capabilities.

installation is done using the Install Java Administration Console option in the NetBackup Windows installation user interface. To recover. 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. The following message is displayed if you stop the bpdbm daemon on the relevant server when Activity Monitor is active. For the Windows platform. Solaris x64 HP-UX AIX Red Hat and SUSE Linux Windows platforms. ■ . some of the jobs may not be deleted. The NetBackup-Java Administration Console runs on the following platforms: ■ ■ ■ ■ ■ Solaris SPARC. 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. The Activity Monitor can be shut down when you leave the Activity Monitor node or when you close the NetBackup Administration Console. first correct the problem described below and then refresh. 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 number varies depending on the tasks that you attempt in the console. ■ Multiple bpjava processes per instance of the console For increased performance and support to multitask easier on the console. ■ Remote display of the NetBackup-Java console in multi-byte locale environments is not supported. multiple bpjava processes appear on the host that is specified in the logon dialog. If the Activity Monitor is shut down while jobs are deleted. Refer to Chapter 2 (Platforms Supporting the NetBackup Administration Consoles for UNIX) of this document for the supported versions of these platforms.80 Operational Notes NetBackup interfaces Therefore. Connection to bpjobd on server <server_name> failed. Activity Monitor failed and must be restarted.

and so forth.5 or 6.0. If a media server of a previous release has Disk Storage Units (DSUs) configured with a different maximum fragment size. running a two-month report is slower than running a two-week report. An OpsCenter installation is not supported for the versions that are older than VBR 6. Week at a Glance Report’s performance declines as the data to be displayed in the report increases.) The data is not displayed as VBR does not collect any monitoring data. For example.5. only the names are provided from the Job records. Or uninstall VBR first and then install OpsCenter. ■ About Symantec OpsCenter The following list contains the items that relate to the Symantec OpsCenter feature: ■ If you plan to install OpsCenter on AIX. bpjobd. Drives. data is not displayed under the Storage and Devices tabs in Monitoring. consider increasing the fragment size on upgraded storage units.). 6. ■ ■ ■ . To make the best use of the storage unit.5 (for example. 6.x. 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 . Week at a Glance Report performance declines as the data increases. After VBR upgrade. This data is collected after the upgrade as part of the regular data collection.0 or greater. ensure that the XLC runtime version is 9. (Storage units. upgrade the version of VBR to 6.5 terabytes. The bpstuadd command line option -dspath is no longer valid or supported.2.288 megabytes after an upgrade. etc. data is not displayed under Storage and Devices tabs After a VBR upgrade. The refresh option is only available upon lost communications with the job daemon. Robots. To work around this issue.x.6 and then upgrade to OpsCenter. the storage units are not automatically increased to the new default of 524. you can use the refresh option on the toolbar to refresh the Activity Monitor job data. You cannot install OpsCenter on a system that has VBR installed with a version that is lower than 6.Operational Notes About Symantec OpsCenter 81 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).

) . the list of VM images may not be accurate. the OpsCenter processes are not start automatically in AIX or SUSE Linux systems. an attempt to logon may not succeed. This feature restricts volume access using the requesting host’s IP address. The NetBackup Resource Manager calls the pending_request_notify script after a pending request is issued for a media resource (tape volume). the keys are not recreated to display an entry in Add or Remove Programs dialog box. has been added to this version of NetBackup. Enterprise Media Manager The following list shows the operational note items that pertain to Enterprise Media Manager (EMM): ■ A new script. That may happen some times because of the PBX taking time to start. After a rollback. the report that appears displays the wrong client name. Occasionally. Symantec recommends that you start the OpsCenter processes after you perform a reboot. and even though OpsCenter server services are running. pending_request_notify. Use setup. (The root user must run this script. Instead of showing the client names.82 Operational Notes NetBackup media and device management ■ After a reboot.exe to remove OpsCenter. In addition. If you select Reports > Activity Planning > Job Size in the OpsCenter user interface. ■ ■ ■ NetBackup media and device management The following subsection contains the information that is pertinent to NetBackup media and device management functionality. If a rollback occurs during an uninstall of OpsCenter. include an E-mail address in the script where indicated. a list of backed up VM images is displayed in this report. OpsCenter services may not start on reboot in case of SUSE 11. The wrong client name is displayed for canned reports. After you reboot a SUSE 11 Server. You must remove OpsCenter. Media Sharing The access control feature of Sun StorageTek ACSLS controlled robots is not currently compatible with Media Sharing. Use caution when implementing Media Sharing in an ACSLS environment. the keys are not removed from Add or Remove Programs dialog box. To send an E-mail notification when a pending request is initiated.

■ NetBackup uses the Media ID for disk as a unique identifier that can be traced back to a volume on the array. and pending time (in seconds since the UNIX epoch).cmd Into Install_path\NetBackup\bin\ If the script exists in the bin directory. the following parameters are passed to the script: Media ID. The Media ID is an opaque string that has internal meaning to NetBackup. the QLA-2344 HBA performs similarly to two QLA-2342 HBAs but uses one less PCI slot. robot type. 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. In addition.Operational Notes SAN Client and Fibre Transport 83 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. ■ . which is the default access protection method in NetBackup. barcode. media server. the Media ID can be correlated to a volume by running nbdevquery -listmediaid command. SCSI persistent reserve provides more resiliency and fault tolerance than SPC-2 SCSI reserve and release. 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. action code. The advantage a QLA-2344 HBA offers is the ability to spread its aggregate performance over four ports instead of two. ■ 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. but to nothing else. robot number. volume group. 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.

0. Legacy PCI 33 and 66 Mhz slots are not supported.84 Operational Notes SharedDisk support in NetBackup 7.0 Client Deduplication: . A slower PCI card reduces the speed of the controlling bus and therefore all other cards in that bus. ■ ■ ■ ■ ■ SharedDisk support in NetBackup 7.0 and later ■ 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.0 release. No support for FlashBackup restores over an FT pipe. AIX FC driver version level 5. manage. No support for Fibre Channel arbitrated loop (FC-AL) hubs.0 master server to configure. Consequently. NetBackup Client Deduplication The following items pertain to NetBackup 7. In some configurations.2. For information about using SharedDisk. PCI-express.5 release. see the documentation for your NetBackup 6. Not installing the following driver can result in a hung Fiber Transport (FT). NetBackup AdvancedDisk option NetBackup does not support clustering of AdvancedDisk media servers.75 for IBM 6228 card _ AIX Oslevel 5200-07 ■ For 64-bit NetBackup media servers. You can use a NetBackup 7. data transfer rates are reduced and performance is degraded. and restore Fibre Transport pipe performance may degrade significantly. NetBackup SAN clients cannot also be NetBackup servers. compression may reduce performance by up to 95% of uncompressed performance.5 media servers. 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. If you use data compression or encryption for backups. backup.0 and later The SharedDisk option is not supported beginning with the NetBackup 7. 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. On the NetBackup media servers. and operate SharedDisk on NetBackup 6.

NetBackup 7. ■ ■ ■ ■ ■ 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. the daemons cannot be started.Operational Notes About the NetBackup Media Server Deduplication Option 85 ■ ■ NetBackup 7. you can ignore it.0 Client Deduplication does not support multiple copies. Because a storage server is not configured. For the Microsoft Exchange backups that use the NetBackup Exchange Agent. NetBackup does not support clustering of deduplication storage servers or load balancing servers. Oracle Snapshot Client based backups have higher deduplication because the data is aligned on consistent file or tablespace boundary.0 Client Deduplication does not support encryption. . However. Therefore. do not use the same media server for both NetBackup and as a PDDO host. do not enter an NFS file system when you configure the data storage path. Stream-based backups include deduplication within a single backup and deduplication between a backup and data already backed up. The status 2 indicates that the script cannot start the deduplication daemons. NetBackup does not support the Snapshot Client off-host method Media Server Copy on NetBackup clients that deduplicate their own data. The NetBackup Media Server Deduplication Option does not support NFS mounted file systems. Symantec expects Oracle database stream-based backups to achieve low deduplication rates. Snapshot Client backups of Oracle databases achieve high deduplication rates across full backups within our test environments. Therefore. the netbackup start script returns status 2. The error is spurious. 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. deduplication rates are low even though data has not changed since the last backup.

. From a policy that was configured with the FlashSnap off-host backup method and with Retain snapshots for Instant Recovery enabled. NetBackup does not support the Snapshot Client off-host method media server Copy on NetBackup clients that deduplicate their own data. In addition. HP_EVA_Snapshot. the backups that were made at different times may create snapshot disk groups with the same name. and the restore fails with status 5.86 Operational Notes NetBackup Snapshot Client 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. Examples of disk array snapshot methods are EMC_CLARiiON_SnapView_Snapshot. only one snapshot can be retained at a time. You must delete the existing VxVM snapshot from the VxVM disk group before you run a backup with a disk array snapshot method." ■ Instant Recovery restores may fail from a backup that a FlashSnap off-host backup policy made. For this release. NetBackup does not support Snapshot Client VSS off-host file backups using a Storage Foundation for Windows (SFW) VSS provider. If the exclude list on the alternate client is different from the exclude list on the primary client. and IBM_StorageManager_FlashCopy. and the bpfis log contains a message that reports a vxmake command failure. Snapshot creation fails (with final status 156). If a software-based snapshot (such as from the VxVM method) already exists of a VxVM volume on the disk array. But the snapshots no longer exist. in the chapter titled "Configuration of snapshot methods for disk arrays. any files that are listed in the exclude list on the alternate client are not restored to the primary client. This issue will be fixed in a future release of NetBackup. 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. NetBackup may not be able to remove the catalog images for the snapshots that have expired and been deleted. As a result. Hitachi_CopyOnWrite. All disk array methods are described in the NetBackup Snapshot Client Administrator's Guide. It appears that you can browse the expired snapshots and restore files from them. NetBackup cannot create a disk array snapshot of a file system that is configured on the VxVM volume.

Any data changes or snapshots that were made in the primary file system after that time are lost as a result of the rollback. Rollback returns a file system or volume to a given point in time. If the snapshot is retained after the backup (for the Instant Recovery feature) and the snapshot is available at the time of the restore. any files that were included in the exclude list are not backed up. The exclude list is consulted only when a storage unit backup is created from the snapshot. during the verify operation for the rollback.Operational Notes NetBackup Snapshot Client 87 For example. as noted in the previous item. ■ 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. you must change the exclude list on the alternate client.jpg. Note: For ordinary backups (not based on snapshots). 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. NetBackup honors the latest version of the exclude list during the restore. Also. the snapshot is mounted and in some cases.jpg files can be selected for the restore but are not in fact restored. Any of the files that are listed in the current exclude list are not restored. Since all files are available in the snapshot (including those that would be excluded from a storage unit backup). For example: If the current version of the exclude list has the entry *. To restore the files. you must change the exclude list on the primary (or alternate) client.jpg files can be selected for the restore but are not in fact restored. the . Note that a rollback deletes all files that were created after the creation-date of the snapshot that you restore. NetBackup incorrectly consults the current exclude list on the client or alternate client. . ■ Problem with "Restore from Point in Time Rollback" When you start a "Restore from Point in Time Rollback" from an Instant Recovery backup.jpg files were included in the backup. all files are included in the snapshot.jpg files were included in the primary client backup. To restore the files. and some . In that case. NetBackup restores files from the snapshot.jpg. the exclude list on the alternate client takes precedence over the exclude list on the primary client. the snapshot cannot be unmounted. However. the Point in Time Rollback operation is aborted. the . however. For snapshot-based backups. This issue will be addressed in a future release of NetBackup. if the alternate client's exclude list has the entry *. Any files in the exclude list are skipped during the restore. and some .

refer to the NetBackup Commands guide: ■ NBCC See “About NetBackup support utilities” on page 18. ■ nbkmsutil This command runs the NetBackup Key Management Service utility. ■ bptestnetconn . ■ bpclusterutil You can use this command to modify and configure a NetBackup cluster. See "Instant Recovery: point in time rollback" in the NetBackup Snapshot Client Administrator's Guide for more information on rollback. ■ nbregopsc You use this command to register OpsCenter.88 Operational Notes NetBackup commands and utilities Note: For a rollback of a database backup such as Oracle. ■ bpclimagelist This command produces a status report on NetBackup client images or removable media. ■ NBCCR See “About NetBackup support utilities” on page 18. For a description of each of the following commands. The problem that is described here is avoided and the rollback succeeds. ■ nbcplogs You can use this command to copy all NetBackup logs to a designated destination. Rollback deletes all files that were created after the creation-date of the snapshot that you restore. For a rollback of a file system. 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. you can skip file verification by selecting "Skip verification and force rollback" on the restore dialog. NetBackup commands and utilities This release of NetBackup contains new commands and utilities. the file system verification is mandatory and this issue prevents a successful rollback.

The support and support. a . the nb_updatedssu command runs. 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. Relocated data is tracked differently in the current release and the . When you upgrade a media server that is used for OpenStorage to NetBackup 7. Symantec recommends that you run the command again to ensure that all . NetBackup binaries are compiled in 64-bit. not the setting of the destination storage unit. Beginning with release 7.ds files that were used in the previous releases as pointers to the relocated data. NetBackup performs optimized duplication until it encounters an image for which optimized duplication is not possible. If that occurs. NetBackup does not resize or rearrange the backup image into a different set of fragments).Operational Notes NetBackup OpenStorage Option 89 This command test and analyzes various NetBackup configurations and connections. NetBackup copies the image fragments as is (that is. if you have any written scripts that make use of the .ds files to compute the amount of "potential free space" on a volume.ds file may not be deleted upon installation or upgrade. NetBackup performs a regular duplication. Therefore.0. NetBackup uses the fragment size setting of the source storage unit.0. ■ ■ ■ NetBackup Disk Storage units The following list contains the operational information that pertains to the Disk storage unit: ■ Upon NetBackup installation or upgrade. NetBackup requires OpenStorage vendor plug-ins to be 64-bit. Under some circumstances. For that image and all subsequent images. you also must update the vendor plug-in to a 64-bit version.ds files. The command deletes the . are converted to the new tracking mechanism. you now need to use a .exe diagnostic information gathering utilities are no longer included or supported beginning with this release of NetBackup.ds files are removed: install_path\netbackup\bin\admincmd\nb_updatedssu /usr/openv/netbackup/bin/admincmd/nb_updatedssu Note.

The presence of the VLT_CREATE_SESSION_DEBUG_FILES touch file has no affect on the new session permissions.log from the sidxxx directory to a new sidxxx/logs directory to accommodate eject/reports eligible sessions. then the properties of the BasicDisk STU do not appear in the storage unit dialog that is shown in the 7. to display the potential free space for the volume.0 user interface. You may need to update the notify scripts appropriately with respect to the directory structure changes.0. the summary. 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.0 version. log files are written to sidxxx/logs. Symantec recommends that you process all these sessions (meaning that you complete all ejects and reports) before you upgrade to ensure minimal affect. you should copy the summary. 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. you can still set permissions on UNIX systems so that non-root users can use the operational commands . For example.0.0 sessions are not processed completely before an upgrade. If you upgrade to NetBackup 7.0: ■ If pre-NetBackup 7.90 Operational Notes NetBackup Vault different command. ■ ■ ■ ■ ■ Vault Operator Access on UNIX. A pop-up window appears and contains the following message: CORBA::BAD Param. For example. you must make sure that you account for the enhancements that were packaged in NetBackup 7. These enhancements specifically target a system where NBAC is configured and the Vault service manages the important read-write data. If you do not configure NetBackup Access Control. The permissions of pre-NetBackup 7. For example.0 session directories are not modified.0 and decide to downgrade to a pre-NetBackup 7. and files and folders have restrictive permissions when they are created. these enhancements have the following effect on users who have upgraded from previous versions to NetBackup 7. At a minimum.log is now written to sidxxx/logs directory. You can use the following command.

Giving users access to the Vault Operator Menu also gives them the capability to change report destinations. Modify that entry to allow all users in the opsgroup access to the Sun StorageTek ACSLS server as user acsss: . you may not want non-root users to see the Recovery Report or to be able to change to whom reports are e-mailed. then give that group permission to execute some of the executable files. For example. Check with your system administration or computer security staff to ensure that you do not violate security policies.rhosts file in the home directory of user acsss. The most efficient way to accomplish that is to add the users to whom you want to grant access to a single user group. ■ Create a UNIX group and add the appropriate users to this group. giving users special privileges may violate your organization’s computer and network security policies and allow access to private information. log on to that server and modify the . This group is referred to as opsgroup in the following commands. do not give them access to the Vault Operator Menu.rhosts file for the NetBackup master server that grants root access. In addition. If you do not want non-root users to view reports and change report destinations. The NetBackup installation process should have added an entry to the .Operational Notes NetBackup Vault 91 in the Vault Operator Menu to inject and eject tapes and generate reports. 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 # 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.

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. some of the virtual machine volumes may be incorrectly mapped and cannot be restored.92 Operational Notes NetBackup for VMware master_server_name root <user1> <user2> . Use of the Full VM backup option results in a lower rate of deduplication. select the Mapped full VM backup option for the Virtual machine backup parameter on the VMware snapshot method. For simplicity. do the following. . The converse is also true. you can skip this step. ■ 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. Furthermore. a backup that uses the hotadd transfer type may appear to succeed. NetBackup for VMware does not support backing up virtual machine RAID 5 volumes with the SAN transfer type. 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. To verify the proper operation. . If you want to use the hotadd transport type with your backup. the RAID 5 volume may not be correctly restored. log on as a non-root user on the NetBackup master server system. each user should have the same user ID on both servers. <userx> If you use Sun StorageTek ACSLS for robotic control. and that virtual machine is a clone of the virtual machine that you backed up. VMware has identified this issue as software defect SR#1442259141. 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. the two virtual machines must not be clones of the same parent. Start vltopmenu and execute each menu option. This option provides the best deduplication rates. Make sure the virtual machine that contains the VMware backup host and the virtual machine you back up are not clones of each other. If both servers use a naming service (such as NIS). However. If a virtual machine containing a RAID 5 volume was backed up with VMware vStorage services (not VCB) using the SAN transfer type.

Virtual machine restore: file write failed. 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 virtual machine when restored may attempt to boot from the IDE drive. That ensures all of the virtual machine's original network adapters are restored when the virtual machine is restored. some of the virtual machine's network interfaces are not restored. The final job status code is 5. Make sure that the network connections are correctly identified and selected on the NetBackup "network connections " Restore dialog. you can reconfigure the BIOS on the virtual machine to boot from the correct SCSI disk. restore the virtual machine directly to an ESX server. This issue will be addressed in a future release of NetBackup. use the nbd transfer type instead of hotadd.0 performs a restore with the VMware vStorage infrastructure services. 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.Operational Notes NetBackup for VMware 93 This issue will be addressed in a future release of VMware and NetBackup. the restore failed to recover the requested files. ■ . any drives that you specify to be excluded from the proxy client are also excluded from the virtual machines. the backup host must be in a Windows 2003 virtual machine to use the hotadd transfer type for the restore. Because of a VMware issue (SR#1438908741). VMware virtual machine does not reboot after restore If a virtual machine was configured with SCSI and IDE drives at the time of backup. The detailed status log on the NetBackup Activity Monitor includes the message. ■ ■ ■ You can use a proxy client for VMWare Consolidated backups (VCB). However. In that case. you can configure additional network interfaces on the destination ESX server before you run the restore. VMware has identified this problem and will address it in a future release. As a workaround. the boot attempt fails with the message "Operating system not found. 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. and the guest OS resided on a SCSI drive." This problem occurs when NetBackup uses the VMware vStorage integration services. make sure that you do not exclude drives on proxy clients when you perform a VCB backup. the restore job may be slow if you restore to a vCenter Server. If the backup host is in a Windows 2008 virtual machine. ■ If a virtual machine with multiple network interfaces is restored to an ESX server that has fewer network interfaces. Until this issue is fixed. To avoid this issue. As a workaround. This issue occurs when NetBackup 7. To speed up the restore.

94 Operational Notes NetBackup for VMware ■ 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). Archive. and Restore interface on Windows. only the most recent BLIB backup of that virtual machine can be restored. . use the Backup. 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.

0 environments. it continues to be a supported option with NetBackup 6. If you are a current NAS SnapVault Option user and intend to upgrade to NetBackup 7.0. These notifications encompass NetBackup commands. tools. files. and commands no longer supported End of life notifications This section contains information about the features.5. you must use your NetBackup 6. utilities. support for all of the active and the passive media server clusters that use the NetBackup clustering agents is withdrawn.5 license keys that enable SnapVault.0 license keys. and terminology. The NAS SnapVault Option is not offered for sale with new NetBackup 7. and devices that will no longer be supported in future releases of NetBackup. 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.5 license keys for the remaining support life of 6.0. enhancements. directories. However. The NetBackup 6. 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.Chapter 5 End of Life Notifications This chapter includes the following topics: ■ ■ End of life notifications About features. platforms.0.5 SKU for the NAS ■ . To continue to use SnapVault on 7. robots and devices.

NetBackup.5. At the next major release of NetBackup. and commands no longer supported Changes to how Symantec supports NetBackup features may directly affect you. As of the next major release. notification was already announced and this document confirms that support has been removed. VSM is supported for the life of NetBackup 6.0. 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. You can use a NetBackup 7. and commands no longer supported SnapVault Option is available for one year after NetBackup 7. enhancements. Items within these sections were previously announced in earlier releases of NetBackup providing a warning to users that specific changes were forthcoming.0 master server to configure. enhancements.x media servers support VSM media and this version of NetBackup Vault manages those media. NetBackup Vault no longer supports VSM media eject and report functionality. However. Symantec is committed to notifying you of these changes at least one major release before support is discontinued.96 End of Life Notifications About features.0 release.5 is the final release of the product and is not supported in NetBackup 7.5 media servers. BETR is no longer supported. Veritas Storage Migrator (VSM) 6.0 is released. the NetBackup-Java Administration Console is no longer supported. or commands that are no longer supported as of this release of NetBackup. The following sections describe those features. ■ Starting with the next major release of NetBackup.5 and all of the NetBackup 6. ■ ■ About features. That means that only NetBackup 6. enhancements. Backup Exec Tape Reader (BETR) refers to the ability within NetBackup to import and restore from Backup Exec (BE) backup sets (images). and operate SharedDisk on NetBackup 6. That enables you to purchase licenses to support additional capacity.5 release updates. FAT file systems are not supported for Windows server (x86 and x64) systems.5 GA and 6. In some instances. ■ ■ . Starting with the next major release of NetBackup. The SharedDisk option is not supported beginning with the NetBackup 7. the NetWare client is no longer supported. manage.

and commands no longer supported 97 For information about using SharedDisk. NetBackup 7. The VERITAS Snapshot Provider (VSP). NetBackup has merged two help sets into one. the NetBackup binaries for AIX.11 system. and you start the computer in 64-bit mode.End of Life Notifications About features. Starting with this release of NetBackup. NetBackup automatically uses VSS instead of VSP. see the documentation for your NetBackup 6. Starting with this release of NetBackup. ■ ■ ■ ■ ■ ■ ■ ■ ■ About database functions no longer supported The following describes the functionality within the NetBackup database agents that are no longer supported. enhancements.x versions with the exception of the OnlineJFS version 3. NetBackup installs and runs as designed. for open and active files on NetBackup pre-7. This backup method was deprecated from NetBackup and is no longer be supported. Cold Catalog Backup has been dropped from NetBackup 7. beginning with this release of NetBackup: . Beginning with this release. If you have a computer that can run a 32.0 does not support SGI IRIX and Tru64 platforms. If you run the computer in 32-bit mode only.0 does not install.0. That means that the jnbSA help set has been eliminated and the jbpSA help set remains. Solaris SPARC. is no longer supported in NetBackup 7. The set_ndmp_attr file no longer exists in NetBackup. Symantec no longer provides the Windows tape device Installer or Windows Tape Drivers.5MP1 on an HP-UX 11. The NetBackup Operations Manager (NOM) product has been replaced with the new OpsCenter feature.0. and Linux x86 systems are now built as 64-bit binaries only. The Snapshot Client does not support Storage Foundation 3. you can no longer use the "cold" ("offline") catalog backup method. the functionality that is found in set_ndmp_attr only exists in tpconfig. Note: For 7.5 release. ■ ■ NetBackup no longer supports the NetWare Media Server Option. Starting with this release.0 Windows clients.0 clients. HP9000 PA-RISC.or 64-bit operating system. then NetBackup 7.

■ ■ . andsupport.5 replaced these utilities. are no longer supported as of this release of NetBackup. support. and commands no longer supported ■ NetBackup for Microsoft SharePoint Portal Notifications NetBackup 7.exe. NetBackup for Microsoft SQL Notifications NetBackup no longer supports SQL Server 7.98 End of Life Notifications About features. A new utility. NetBackup for Microsoft Exchange Server NetBackup 7.0 backup and recovery. The diagnostic information gathering utilities and programs. introduced in NetBackup 6.0 no longer supports Exchange 5.0 no longer supports SharePoint Portal Server 2001 backup and recovery.5. The FSAnalyzer is no longer supported in this release of NetBackup. The last release of the FSAnalyzer was NetBackup 6. nbsu. ■ ■ 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.5 or Exchange 2000 backup and recovery. enhancements.

You can download a copy of this product from the Adobe Web site at the following URL: http://www.Chapter 6 Related Documents This chapter includes the following topics: ■ ■ ■ ■ ■ ■ ■ ■ ■ About related NetBackup documents About NetBackup release notes About getting started guides About installation guides About administrator’s guides . you need an Adobe Acrobat reader. .com Symantec assumes no responsibility for the correct installation or use of the reader. The DVD-ROM for each NetBackup product has a copy of the related manuals in Adobe Portable Document Format (PDF). To view the PDF copies of the manuals.agents and options About user’s 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 PDF files are either in the root directory or the Doc directory on the disk.adobe.

pdf This document contains information about NetBackup on UNIX. and Windows NetBackup_Release_Notes. and Linux systems. Linux. and Restore interface to perform backup and restore operations for UNIX.100 Related Documents About NetBackup release notes About NetBackup release notes The following release notes documents were released with this version of NetBackup. ■ ■ . Symantec NetBackup Backup. Archive. Linux. ■ About installation guides The following Installation documents were released with this version of NetBackup.pdf Explains how to use the NetBackup Backup. and Windows NetBackup_GettingStarted_Guide.and Windows-based servers. Symantec NetBackup Installation Guide for Windows NetBackup_Install_Win. ■ Symantec NetBackup Release Notes for UNIX. Windows.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.pdf Explains how to install NetBackup software on Windows-based platforms. It also contains any operating notes that may not be in the NetBackup manuals or the online Help .pdf Explains how to install NetBackup software on UNIX-based platforms. About getting started guides The following getting started guides were released with this version of NetBackup.5 and later. Archive.pdf Provides a high-level description of the latest NetBackup release. ■ Symantec NetBackup Getting Started Guide for UNIX. and Restore Getting Started Guide NetBackup_BAR_GS_Guide. Symantec NetBackup LiveUpdate Guide NetBackup_LiveUpdate_Guide. ■ Symantec NetBackup Installation Guide for UNIX NetBackup_Install_UNIX. This document also contains the information that explains the content of the NetBackup media kit. such as the platforms and operating systems that are supported.

off-host backup . Symantec NetBackup SAN Client and Fibre Transport Guide NetBackup_SANClient_Guide. It provides visibility into their data protection environment. configure. Symantec NetBackup for Hyper-V Guide for UNIX. OpenStorage. Shared storage includes AdvancedDisk.pdf Explains the Web-based software application that helps organizations.pdf Explains how to configure and use NetBackup SAN Client and Fibre Transport for high-speed backups of important clients. It combines the features of snapshot backup. and Instant Recovery.Related Documents About administrator’s guides . Symantec NetBackup Enterprise Vault Agent Administrator's Guide for Windows NetBackup_AdminGuide_EntVault. Windows. and use the Enterprise Vault Agent so you can protect Enterprise Vault configuration information and data that Enterprise Vault has archived.pdf Explains how to configure and use NetBackup media server deduplication and NetBackup client deduplication. and Linux NetBackup_AdminGuide_Hyper-V.5.pdf Explains how to configure and use shared storage in NetBackup.pdf Provides the first-time instructions for installing and configuring the Snapshot Client.6. Symantec NetBackup Snapshot Client Administrator’s Guide NetBackup_AdminGuide_SnapshotClient. and use Symantec NetBackup Snapshot Client.agents and options The following administrator guides for NetBackup database agents and options were released with this version of NetBackup.pdf This guide explains how to install.agents and options 101 About administrator’s guides . BLI Agent.pdf Explains how to install.pdf ■ ■ ■ ■ ■ ■ ■ . configure. Symantec NetBackup Shared Storage Guide NetBackup_SharedStorage_Guide. ■ Symantec NetBackup Deduplication Guide NetBackup_Dedupe_Guide. FlashBackup. Symantec OpsCenter Administrator's Guide NetBackup_AdminGuide_OpsCenter.4 and Veritas Backup Reporter (VBR) 6. Symantec NetBackup Snapshot Client Quick Start Guide NetBackup_QuickStart_SnapshotClient. OpsCenter is a combination of the two Symantec products namely NetBackup Operations Manager (NOM) 6. and the Shared Storage Option.

Windows.pdf Explains how to install. configure. Symantec NetBackup for Lotus Notes Administrator’s Guide for Windows NetBackup_AdminGuide_LotusNotes_Win. configure. configure. configure. configure.pdf Explains how to install. and use NetBackup for DB2. ■ ■ ■ ■ ■ ■ ■ ■ .pdf Explains how to install. Symantec NetBackup for DB2 Administrator’s Guide for UNIX NetBackup_AdminGuide_DB2_Unix. configure. and use NetBackup for Lotus Notes to back up and restore Lotus Notes databases and transaction logs on a Windows client.pdf Explains how to install.pdf Explains how to install.pdf Provides backup and restore of the VMware virtual machines that run on VMware ESX servers.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 NDMP Administrator’s Guide NetBackup_AdminGuide_NDMP. Symantec NetBackup for Informix Administrator’s Guide NetBackup_AdminGuide_Informix.pdf Explains how to install.pdf Explains how to install.102 Related Documents About administrator’s guides . Symantec NetBackup for Microsoft SQL Server Administrator’s Guide for Windows NetBackup_AdminGuide_MSSQL_Win. Symantec NetBackup for DB2 Administrator’s Guide for Windows NetBackup_AdminGuide_DB2_Win. and use NetBackup for Lotus Notes to back up and restore Lotus Notes databases and transaction logs on a UNIX client. and Linux NetBackup_AdminGuide_VMware. and use NetBackup for NDMP to control backups on an NDMP host. and use NetBackup for DB2.agents and options NetBackup for Hyper-V provides snapshot-based backup of the virtual machines that run on Windows 2008 Hyper-V servers. and use NetBackup for Microsoft SQL Server to back up and restore Microsoft SQL Server databases and transaction logs. configure. Symantec NetBackup for Microsoft Exchange Server Administrator’s Guide NetBackup_AdminGuide_MSExchg_Win. 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 Administrator’s Guide for UNIX NetBackup_AdminGuide_LotusNotes_Unix. ■ Symantec NetBackup for VMware Administrator's Guide for UNIX.

pdf Explains how to install.pdf Explains how to install. ■ ■ ■ ■ ■ ■ ■ ■ . configure. and Linux.pdf This guide provides information on how to install and configure NetBackup to work with different clustering solutions. and use NetBackup for Oracle to back up and restore the Oracle databases that are on a UNIX NetBackup client. and use NetBackup for Sybase to back up and restore Sybase databases that are on a Windows NetBackup client.pdf Explains how to install. Symantec NetBackup for SYBASE Administrator’s Guide on Windows NetBackup_AdminGuide_Sybase_Win. For UNIX. configure. configure. Symantec NetBackup High Availability Administrator’s Guide NetBackup_AdminGuide_HighAvailability. Symantec NetBackup for SAP Administrator’s Guide for UNIX NetBackup_AdminGuide_SAP_Unix.agents and options 103 ■ Symantec NetBackup for Oracle Administrator’s Guide for UNIX NetBackup_AdminGuide_Oracle_Unix. and use NetBackup for Microsoft Oracle to back up and restore the Oracle databases that are on a Windows NetBackup Client. configure. and use NetBackup for SAP on UNIX. Symantec NetBackup for SAP Administrator’s Guide for Windows NetBackup_AdminGuide_SAP_Win. Symantec NetBackup for SYBASE Administrator’s Guide for UNIX NetBackup_AdminGuide_Sybase_Unix. configure.pdf Explains how to install.Related Documents About administrator’s guides . and use Bare Metal Restore to protect and restore client systems. Symantec NetBackup Bare Metal Restore Administrator's Guide NetBackup_AdminGuide_BMR.pdf Explains how to install. and use NetBackup for Sybase to back up and restore Sybase databases that are on a UNIX NetBackup client.pdf Explains how to install.pdf Explains how to install. Symantec NetBackup™ for Microsoft SharePoint Server Administrator’s Guide for Windows NetBackup_AdminGuide_SharePoint. configure. and use NetBackup for SAP on Windows-based servers. Symantec NetBackup for Oracle Administrator’s Guide for Windows NetBackup_AdminGuide_Oracle_Win. and use NetBackup for SharePoint Portal Server 2003 to back up and restore the Sybase databases that are on a Windows NetBackup client. configure. configure. Windows.pdf Describes how to install.

■ About the device configuration guide The following device configuration guide was released with this version of NetBackup. and generate reports. The NetWare Client also provides two methods for performing user-directed backups and restores: Target. and running reports on off-site media and vault jobs. and use logical vaults and profiles to duplicate backups. configure.104 Related Documents About user’s guides ■ Symantec NetBackup Vault Administrator's Guide NetBackup_AdminGuide_Vault.pdf This comprehensive manual provides detailed information and procedures for installing. configuring.pdf Describes the procedures for sending tapes off site. which uses the NetBackup for NetWare NonTarget Browser that is installed and run from a Windows computer. and Linux. Windows. Symantec NetBackup NetWare Media Server Option Administrator’s Guide for UNIX and Windows NetBackup_AdminGuide_NetWareServer. Symantec NetBackup Administrator's Guide for Novell NetWare Client NetBackup_AdminGuide_NetWare_Client. receiving tapes on site.pdf Describes how to install. eject media. and using the Symantec NetBackup NetWare Media Server Option. ■ Symantec NetBackup Device Configuration Guide NetBackup_DeviceConfig_Guide. and Linux. For UNIX. and NonTarget. Windows.pdf Explains how to install and use the NetBackup’s NetWare Client software. ■ About user’s guides The following user guides were released with this version of NetBackup. full and incremental backups can be scheduled to occur automatically and unattended under the control of the NetBackup master server. perform catalog backups. ■ Symantec NetBackup Vault Operator's Guide NetBackup_OperGuide_Vault.pdf Explains how to add device drivers and perform other system-level configurations for the operating systems of NetBackup servers that host storage . menu-driven interface running on the NetWare server. For UNIX. which uses a character-based. With the NetWare Client.

and Windows-based NetBackup products.Related Documents About the Troubleshooting guide 105 devices. About the Troubleshooting guide The following troubleshooting guide was released with this version of NetBackup.pdf Provides troubleshooting information for UNIX. Also includes information about configuring several types of tape libraries. ■ Symantec NetBackup Commands for UNIX. 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. About NetBackup command documents The following command documents were released with this version of NetBackup. . including Media Manager. ■ Symantec NetBackup Troubleshooting Guide for UNIX and Windows NetBackup_Troubleshoot_Guide. Windows.

106 Related Documents About NetBackup command documents .

Appendix A 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. Product Name. Files that remain after an uninstall The NetBackup uninstall may leave files behind that other Symantec applications use. NetBackup 7. If you uninstall NetBackup from a Windows Server 2008 R2 host and remove the VxAT files in the common directory.0 uses Veritas Authentication (VxAT) as a common security infrastructure that is shared between applications on the same host. Veritas Storage Foundation (VxFS) and NetBackup can reside on the same host. 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. For example. and Product Version) See Table A-1 for a list of these files. The tables contain the following types of information: ■ Files that have invalid file version information (Company. Files that NetBackup uses that are not signed See Table A-3 for a list of these files. then the remaining application ceases ■ ■ ■ .

the following files remain in the Security folder (C:\Program Files\Veritas\Security\.) after the uninstall completes.dll libxml2.dll ■ ■ ■ Program Files\Veritas\pdde Program Files\Veritas\pdde\pddb\bin Program Files\Veritas\pdde\pddb\lib adminpack.dll libldap_r.dll liblber.exe Third-party file locations Third-party files located in Program Files\Veritas\NetBackup\bin pxsetup..dll gvmomi.dll .exe vxblock.dll Third-party files located in any of the following paths: _int. See Table A-4 for a list of files that remain after an uninstall has occurred.dll Third-party files located in of Program Files\Common Files\VERITAS\VxMS\shared\VDDK diskLibPlugin.dll libldap.dll libcurl.dll ssleay32. However.dll libeay32.108 Windows Logo Certification information About Windows Server 2008 R2 Logo Certification to function. Table A-1 NetBackup installs the following files that do not have valid file version information File names pxhpinst.dll types.dll zlib1..dll ascii_and_mic.

dll euc_jp_and_sjis.dll earthdistance.dll cyrillic_and_mic.dll chkpass.dll isn.dll fuzzystrmatch.dll btree_gist.dll cube.dll dict_xsyn.dll euc_cn_and_mic.Windows Logo Certification information About Windows Server 2008 R2 Logo Certification 109 Table A-1 NetBackup installs the following files that do not have valid file version information (continued) File names autoinc.dll latin2_and_win1250.dll insert_username.dll euc_tw_and_big5.dll dict_snowball.dll int_aggregate.dll hstore.dll euc_kr_and_mic.dll euc_jis_2004_and_shift_jis_2004.dll dict_int.dll Third-party file locations .dll libecpg.dll latin_and_mic.dll libecpg_compat.dll dblink.

dll pgbench.dll pgrowlocks.exe pageinspect.dll moddatetime.dll ltree.exe pgcrypto.exe pg_trgm.dll pgxml.dll libxml2.110 Windows Logo Certification information About Windows Server 2008 R2 Logo Certification Table A-1 NetBackup installs the following files that do not have valid file version information (continued) File names libpgtypes.dll plpgsql.dll pltcl.dll pg_freespacemap.dll libxslt.dll pgstattuple.dll pg_buffercache.dll plpython.dll lo.dll oid2name.dll libpq.exe pg_regress_ecpg.dll Third-party file locations .exe pg_standby.dll pg_regress.dll plperl.

dll sslinfo.dll test_parser.dll utf8_and_euc_jis_2004.dll regress.dll utf8_and_big5.dll utf8_and_cyrillic.dll utf8_and_gbk.dll utf8_and_ascii.dll utf8_and_iso8859.dll utf8_and_euc_tw.dll utf8_and_shift_jis_2004.dll tsearch2.dll seg.dll utf8_and_johab.dll timetravel.dll utf8_and_iso8859_1.dll tablefunc.dll utf8_and_uhc.dll utf8_and_euc_cn.dll utf8_and_gb18030.dll utf8_and_euc_kr.dll Third-party file locations .Windows Logo Certification information About Windows Server 2008 R2 Logo Certification 111 Table A-1 NetBackup installs the following files that do not have valid file version information (continued) File names refint.dll utf8_and_euc_jp.dll utf8_and_sjis.

exe ■ ■ ■ Program Files\Veritas\pdde Program Files\Veritas\pdde\pddb\bin Program Files\Veritas\pdde\pddb\lib createdb.dll Third-party file locations Table A-2 NetBackup uses the following third-party files and tools that do not include or create requested ExecutionLevel tags File names java.dll vacuumlo.exe tnameserv.exe keytool.exe policytool.exe .dll uuid-ossp.exe Third-party file locations Third-party files located in Program Files\Veritas\NetBackupDB\java javaw.exe Third-party files located in Program Files\Veritas\NetBackup\bin pxhpinst.exe vacuumlo.exe zlib1.exe Third-party files located in any of the following paths: clusterdb.112 Windows Logo Certification information About Windows Server 2008 R2 Logo Certification Table A-1 NetBackup installs the following files that do not have valid file version information (continued) File names utf8_and_win.exe pxsetup.exe uconv.exe rmid.exe rmiregistry.

exe pg_standby.exe pg_config.exe oid2name.exe droplang.exe psql.exe dropuser.exe dropdb.exe pg_regress_ecpg.exe pg_regress.exe ecpg.exe pg_resetxlog.exe pg_ctl.exe reindexdb.exe initdb.exe postgres.exe pgbench.exe Third-party file locations .exe pg_controldata.exe pg_restore.exe vacuumdb.exe createuser.exe createuser.Windows Logo Certification information About Windows Server 2008 R2 Logo Certification 113 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 pg_dump.exe pg_dumpall.

exe javaw.exe zic.dll java.exe net.114 Windows Logo Certification information About Windows Server 2008 R2 Logo Certification 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.dll fontmanager.dll jdwp.dll dt_socket.exe jawt.dll hpi.dll ioser12.exe Third-party file locations Table A-3 NetBackup uses and installs the following files that are not signed.dll hprof.dll policytool.dll keytool.dll java. File names awt.dll jsound.dll dcpr.dll JdbcOdbc.dll Third-party file locations Third-party files located in Program Files\Veritas\NetBackupDB\java cmm.dll jpeg.exe .

Windows Logo Certification information About Windows Server 2008 R2 Logo Certification

115

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

Third-party file locations

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

116

Windows Logo Certification information About Windows Server 2008 R2 Logo Certification

Table A-3

NetBackup uses and installs the following files that are not signed. (continued) File names
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 file locations

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

Windows Logo Certification information About Windows Server 2008 R2 Logo Certification

117

Table A-3

NetBackup uses and installs the following files that are not signed. (continued) File names
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

Third-party file locations

dll libpgtypes.dll libintl-8.dll libecpg_compat.dll pg_config.dll libpq.dll libiconv-2.dll libxml2.exe pageinspect.dll pg_buffercache.dll latin2_and_win1250.dll k5sprt32.dll int_aggregate.dll moddatetime.dll libecpg.dll libeay32. (continued) File names initdb.dll krb5_32.exe insert_username.dll oid2name.dll ltree.dll isn.118 Windows Logo Certification information About Windows Server 2008 R2 Logo Certification Table A-3 NetBackup uses and installs the following files that are not signed.dll libxslt.exe Third-party file locations .dll latin_and_mic.dll lo.

dll plpython.dll pgstattuple.exe pg_regress_ecpg.exe pgcrypto.dll Third-party file locations .exe pg_dumpall.exe pg_restore.exe pg_ctl.exe psql.dll plperl.dll pgxml.dll pgbench. (continued) File names pg_controldata.exe pg_freespacemap.dll pltcl.dll pgrowlocks.dll pg_regress.exe pg_resetxlog.Windows Logo Certification information About Windows Server 2008 R2 Logo Certification 119 Table A-3 NetBackup uses and installs the following files that are not signed.dll plpgsql.dll pgevent.exe pg_standby.dll postgres.exe refint.exe pg_trgm.exe pg_dump.

exe seg.dll utf8_and_sjis. (continued) File names regress.dll timetravel.dll test_parser.dll utf8_and_gb18030.dll utf8_and_iso8859_1.dll utf8_and_euc_jp.dll utf8_and_shift_jis_2004.dll utf8_and_johab.dll utf8_and_euc_jis_2004.dll utf8_and_iso8859.120 Windows Logo Certification information About Windows Server 2008 R2 Logo Certification Table A-3 NetBackup uses and installs the following files that are not signed.dll Third-party file locations .dll utf8_and_big5.dll utf8_and_euc_tw.dll utf8_and_euc_cn.dll ssleay32.dll tablefunc.dll utf8_and_gbk.dll utf8_and_ascii.dll reindexdb.dll utf8_and_cyrillic.dll utf8_and_euc_kr.dll sslinfo.dll tsearch2.

001 . (continued) File names utf8_and_uhc.lock C:\Program CertStore.dll vacuumdb.lock Files\Veritas\Security\systemprofile\certstore\ C:\Program KeyStore.exe vacuumlo.dll uuid-ossp.exe zic.pem SessionHMACKey.pem C:\Program default.db __db.dll Third-party file locations Table A-4 File locations Files that remain after NetBackup is uninstalled Files Authentication SessionStore.0000000001 sdefault.conf.lock C:\Program Files\Veritas\Security\ C:\Program Files\Veritas\Security\systemprofile\ VRTSatlocal.db Files\Veritas\Security\systemprofile\sessions\ log.dll utf8_and_win.exe zlib1.lock Files\Veritas\Security\systemprofile\certstore\keystore\ SessionEncrKey.conf CRTSatlocal.Windows Logo Certification information About Windows Server 2008 R2 Logo Certification 121 Table A-3 NetBackup uses and installs the following files that are not signed.

register C:\Program CertStore.006 __db.004 __db.lock Files\Veritas\Security\systemprofile\systruststore\ .005 __db.002 __db.122 Windows Logo Certification information About Windows Server 2008 R2 Logo Certification Table A-4 File locations Files that remain after NetBackup is uninstalled (continued) Files __db.003 __db.