Browse by

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

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

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. language availability. gateway. and IP address information Problem description:
■ ■ ■
Error messages and log files Troubleshooting that was performed before contacting Symantec Recent software configuration changes and network changes
Licensing and registration
If your Symantec product requires registration or a license key. 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
. access our technical support Web page at the following URL: www.symantec.■ ■ ■ ■
Version and patch level Network topology Router.symantec. such as address or name changes General product information (features.

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

■
Integrated deduplication:
■
Client deduplication
.0.0
New features in NetBackup
Symantec NetBackup™ 7.0 contains many new features and enhancements that increase the scalability and functionality of NetBackup for its large enterprise customers.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. The following list highlights some of the major features that comprise NetBackup 7.

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

symantec.
■
■
Direct upgrade path
. HP-UX. 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. a restructured standard report has been added that supports single-click execution along with a quick sort and filter capability for additional detail. The following enhancements comprise the OpsCenter feature:
■
Convergence of NOM and VBR Single deployment configuration and user interface for monitoring.com/docs/337179. Example reports include drive throughput. and a professional look and feel. In addition. PureDisk. http://entsupport.14
New Features About Symantec OpsCenter
■
Supported over all Tier 1 NetBackup clients (for example. improved task efficiency. Windows. See. Improved ease-of-use Symantec corporate user interface (UI) standards for enterprise products. Benefits of media server deduplication:
■
A more simplified installation and configuration. Backup Exec. alerting. virtualization coverage. and reporting functionality previously available in NOM and VBR. and skipped files. Linux. configurable success rate. This enhancement offers simplified navigation. and Enterprise Vault products. An enhanced set of standard reports is now offered for complete operations tracking. 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. Solaris. Additional base reporting functionality:
■
■
■
Point-and-click reports are now available across NetBackup.

■
Expanded and simplified deployment:
■
OpsCenter server is compatible with all NetBackup master server platforms (such as. Moreover. Complete report customization. Windows. NetBackup now provides VMware and file-level recovery from the same set of full and incremental backups. incremental VMware backups. Linux. This feature eliminates the VCB copy of a VM snapshot to the VCB proxy staging area. business reporting and improved graphics.0:
■
Fully integrated with VMware vStorage APIs VCB is no longer required. and HP-UX Itanium). This release is compatible with third-party data protection products such as EMC Legato Networker and IBM Tivoli storage manager. Solaris. NetBackup backs up the snapshot directly from the ESX server. OpsCenter server installation on NetBackup master server for single-domain administration. New Recovery Wizard
■
■
.) The new OpsCenter Analytics package includes the features associated with Symantec OpsCenter and the following features:
■ ■ ■
Historical trending and predictive forecasting.
About NetBackup for VMware
The feature provides the following new enhancements in NetBackup 7. (Business reporting was previously available with VBR. Dedicated OpsCenter server for multi-domain visibility and management.
■
■ ■
OpsCenter installations must be made directly from the standalone OpsCenter media or image.
About Symantec OpsCenter Analytics
This feature provides a turnkey operation that provides improved reporting capabilities such as advanced. New virtual machine (VM) and file recovery from incremental backups VMware vSphere now provides block-level.New Features About Symantec OpsCenter Analytics
15
This feature enables you to configure direct upgrade path from existing NOM and VBR installations.

Exchange 2010 support
NetBackup is now compatibile with Exchange 2010. IP address. Guided Recovery uses an Oracle cloning wizard that executes on the new OpsCenter graphical user interface. In addition. datacenter. and includes the following features:
■
Backups of Exchange 2010 databases on a standalone server or in a Database Availability Group (DAG). and simplifies the process of creating a new database from backups of an existing database.
Guided Recovery
The Guided Recovery feature enhances the NetBackup Oracle agent to provide better functionality for performing Oracle Restore and Recovery operations. Dynamic allocation of a storage unit that is based on the server list and returned at the start of a backup.16
New Features Guided Recovery
This wizard simplifies the process of performing a direct VM recovery or redirected VM recovery. Supported backups include local and off-host snapshots. 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.
■
Tighter vCenter integration More VMware identifiers and attributes are available when you configure a NetBackup policy. and a new Granular Recovery for Active Directory feature.
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. VirtualCenter . backups using Granular Recovery Technology (GRT). ESX platform. Automatic detection of the preferred database copy or the active database copy in a DAG for backup and restore operations. Guided Recovery clones an Oracle database from a backup. Specifically.
. and others. That includes the VMware hostname. enhancements have been made to support new improvements to SharePoint Granular Recovery.
■
■
Non-snapshot and mailbox-level backups are limited to Exchange 2007 and Exchange 2003. UUID. display name.

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

NBCC.0 includes three support utilities: nbsu.0 for Hyper-V supports Hyper-V clustering. and others Any item(s) from a list Any version of a file Recover files to a folder on disk.
■
Two types of off-host backup NetBackup for Hyper-V now supports off-host backup of VM snapshots on CLARiiON storage arrays. and NBCCR.0. discussions. Hyper-V R2 and Cluster shared volumes (CSV) NetBackup for Hyper-V is now compatible with Hyper-V clusters and the new CSV capability. to complement the dual purpose full backups. Now.18
New Features About NetBackup support utilities
NetBackup for Hyper-V now supports incremental backups.4. you can reap the benefits of the more comprehensive granular recovery capabilities along with faster granular recovery with the metadata intact. display name. Support for other VSS snapshot providers will follow. To obtain this update contact NetBackup technical support . NetBackup 7. using the NetBackup Snapshot Client in the VM to perform off-host backup of volumes is also now supported.
With NetBackup 7.0. However.0. Flexible VM identification Use the VM hostname. that included the following:
■ ■ ■ ■ ■
Sites and sub-sites Entire lists. the NetBackup for SharePoint Agent offered additional.5. links. like calendars.
About NetBackup support utilities
NetBackup 7.
■
■
■
Improved SharePoint Granular Recovery
Starting with NetBackup 6.1 patch or later. or UUID when configuring policies. The following list summarizes the enhancements that have been made to each utility in this release:
■
NetBackup Support Utility (NBSU)
. file-level recovery is available from both full backups and incremental backups. more comprehensive granular recovery capabilities. tasks. Alternatively. Hyper-V cluster support requires a 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. you can obtain information about NetBackup configuration settings about troubleshooting areas. This tool queries the host on which it runs and gathers diagnostic information about NetBackup and the operating system. or about NetBackup or media management job status codes.
In addition to the new enhancements.0. installed.
■
NetBackup installation and deployment enhancements
This release of NetBackup contains many enhancements in the area of installation and deployment. If inconsistencies are detected. This file is created as part of the analysis of the data that the NBCC utility collects and any site specific situations. For instance. The following list describes the new changes affecting how NetBackup is deployed. 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. For NetBackup 7. This utility is now available for the Mac OS X platform. NBCC consolidates. and versioninfo diagnostics.0 functionality. this utility contains fixes that address the minor issues found in earlier releases. packaged. Enhancements have been made to this utility to ensure that it supports NetBackup 7. In addition. EMM. Enhancements were made to the SLP. It also analyzes the consistency state of NetBackup databases and catalogs as they relate to tape media. the support and support. and updated:
. and packages the resulting data into a bundle that can be sent to Symantec Tech Support for analysis.New Features NetBackup installation and deployment enhancements
19
The NBSU utility assists you in gathering NetBackup and operating system diagnostic information.0 this utility has been enhanced to include the following new features:
■ ■ ■
New commands line options have been added.exe diagnostic information gathering utilities are no longer included or supported beginning with this release of NetBackup. it provides a wide range of control over the types of diagnostic information gathered. In NetBackup 7.

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

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 valid license is still required to enable the product. If product configuration was required previously (such as db2_config), configuration is still required. (For Solaris server upgrades, the older versions of any listed products here must be removed before an upgrade to NetBackup 7.0. For example, VRTSnbdb2, SYMCnbdb2, VRTSnbenc, SYMCnbenc, and others. The installation script displays a list of the packages it finds that must be removed.) The Japanese and the Chinese language packages remain as separate add-ons. The process to install and upgrade these products remains the same.
■

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

NetBackup is now capable of importing client lists from a file. That prevents the need to individually select hundreds of clients. Multiple simultaneous push installs greatly improve the installation performance over the previous approach of one client at a time. Improvements have been made to the error logging and reporting. A full configuration summary report now describes what options were selected for the install. In addition, all installation logs are now captured in an HTML format for a more readable display. Preinstallation checks are run to ensure a successful installation.

■

■

■ ■

VxUL Log Directory Restructuring This change enhances the usability of VxUL logs by putting the logs for each service in a unique directory, making it easier for support to find and copy the correct logs. In addition, the performance of the vxlogview command is improved when you search for logs by the OID since this command does not need to look at all of the VxUL log files for NetBackup, it only opens log files for the correct OID.

22

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

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

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

Platform compatibility
This chapter includes the following topics:
■ ■ ■ ■ ■

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

About server and client platform compatibility
You can find the NetBackup platform compatibility information and other various compatibility lists on the Symantec Support Web site. These compatibility lists offer a variety of up-to-date information about the operating systems that ahat are compatible with NetBackup and NetBackup features. This topic also contains the following types of information:
■

Descriptions of the compatibility lists that are on the Symantec Support Web site Instructions on how to locate the NetBackup compatibility lists NetBackup backward compatibility information NetBackup binary sizes that include NetBackup media server software and NetBackup client software

■ ■ ■

About platform and operating system compatibility changes
This release of NetBackup contains many changes and enhancements to the compatible platforms and operatings systems. The following list describes some of the major changes that apply the NetBackup 7.0:

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

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

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

Platforms compatiblity with the NetBackup Administration Consoles for UNIX
The NetBackup Administration Console provides a graphical user interface through which the administrator can manage NetBackup. The interface can run on any NetBackup Java-capable system. For information on how to install the consoles, see the NetBackup Installation Guides. And for information on how to use the NetBackup Adminstration Console, see the NetBackup Administrator's Guide, Volume 1. Note: The window managers in the following table are compatible with NetBackup when you use NetBackup Java. You may encounter some user-interface anomalies when you use the various window managers that are available on UNIX platforms. Many of these problems are documented and can occur because of unusual or non-standard window manager configurations. In the most common cases of misplaced or shifted components within a dialog, resize the dialog. This action refreshes the display and causes the interface to display the information correctly. Table 2-3 is a list of platforms that are compatible with the NetBackup-Java Administration Console and the Backup, Archive, and Retore user interface in this release.

no version of that product is supported.36
Platform compatibility About NetBackup backward compatibility
About NetBackup backward compatibility
NetBackup is compatible with a mixture of NetBackup servers that are at various release levels in the same environment. These clients are compatible with NetBackup version 7.0
Master server version
NetBackup 7.0 NetBackup 7.com/docs/308850
.0 is not compatible with Windows 2000 systems. Note: The statements made in this topic do not override Symantec's standard End of Life policies. Table 2-4 Mixed-server compatibility for NetBackup 7.5 (and later). 6. 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.5 (and later).0 servers.x client software on your Windows 2000 systems. 6.0 NetBackup 7. http://entsupport.0 6.0 Media server version
70 7.x: New NetBackup customers with Windows 2000 systems: No action is required.0 (and later)
6. Once a NetBackup version reaches its end-of-life.0
Client version
7. Please review the following end-of-life technote on the Symatec Support Web site for more information:
http://entsupport. That includes backward compatible versions.symantec.symantec.0 master and media servers.0 (and later) 6. you can still use NetBackup version 6. Symantec validates only certain combinations of servers and clients within a NetBackup environment that must provide backward compatibility.com/docs/332616
Table 2-4 shows the different server version levels that are compatible with NetBackup in this release. However.0 (and later)
NetBackup 7.5 (and later).x on Windows 2000 clients with your NetBackup 7. However. 6. You must install NetBackup version 6. See the following Technote on the Symantec Support Web site for more information.

disable UAC. (Each media server must run equal or lower levels of NetBackup. refer to the NetBackup Installation Guide for either UNIX or Windows.0. During an upgrade to NetBackup 7. Servers can pull and push their version information between master and media servers. 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. A master server can inter-operate with a media server that is running a level of NetBackup that is one major release lower. To allow users in the Administrators Group to install NetBackup. the master server must run the highest version of NetBackup in use in that configuration. A media server cannot have a numerically higher version than the master server.Platform compatibility About NetBackup backward compatibility
37
For more information about upgrading NetBackup. To install NetBackup on Windows 2008/Vista/2008 R2/7 UAC-enabled environments. The backup images that are created under an older version of NetBackup are recoverable with a newer version of NetBackup. an upgraded media server uses the vmd service to push its version information to all servers in its master server list. An automatic update occurs every 24 hours when servers push their version information again. you must back up your NetBackup catalogs and verify that the catalog backup was successful. and console) on an individual system must be at the same version. In a mixed-server environment. you must log on as the official administrator. 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. After startup. That includes all transaction logs and database files in the data directory including BMR if it is configured and in use.
■
■
■
■
■
■
■
■
. it is necessary to have enough free disk space to accommodate three complete copies of the NetBackup database. Your server’s NetBackup version determines whether the version information can be pushed. Users that are assigned to the Administrators Group and are not the official administrator cannot install NetBackup in UAC-enabled environments. client.) All components (server.

38
Platform compatibility About NetBackup backward compatibility
.

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

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

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

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

See.1 SP1 and higher
For the most current information and patch requirements for VxFS and VxVM.3 11. refer to the NetBackup 7.11 11. You can search and download the appropriate VxFS libraries to your system from Patch Central on the Symantec Support Web site.1
NA NA NA NA
VxFS 3.46
Product Dependencies About VxFS and VxVM compatible versions
Table 3-2
Versions of VxFS and VxVM that are compatible with Symantec NetBackup (continued) Version of VxFS
5.0 then new VxFS libraries need to be installed on the client to back up systems running VxFS.0
X NA X X
OS Version
5. If running a VxFS version before VxFS 4.0RU4 and higher 4.23 11.
http://entsupport.com/docs/337179
NetBackup has improved its integration with the Veritas File System (VxFS) product to ensure interoperability on all compatible VxFS versions.com/labs/patch.0 Additional Operational Notes contained in Technote number 337179 on the Symantec Support Web site.symantec.0RU3 and higher 5.symantec.3 and higher 5. Table 3-3 Operating system
AIX HP-UX PA-RISC
Improved Integration with Veritas File System (VxFS) VxFS 5. Table 3-3 Shows the integration improvements that were made between the various operating systems and the Veritas File System (VxFS).0 and higher 5.0RU4 and higher NA NA NA
NA 5.0RU1 and higher
Notes
SUSE Linux Enterprise Server 11
x86-64
IA64 POWER Windows 2003 Windows 2008 Windows 2008 R2 x86-64 x86-64 x86-64
NA 5.31
VxFS 4.symantec. https://vias.1 MP3 and higher
Operating system
OS Version
POWER
Version of VxVM
5.0RU3 and higher 4. See http://entsupport.5
NA X NA NA
.com/docs/320193.

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

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

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

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

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

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

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

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

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

com/bugdatabase/view_bug.sun. Use of different locales across UNIX platforms can cause user interface corruption or a possible data loss. NetBackup can be installed to environments running different versions of UNIX based operating systems as long as the system locales are identical.
■
■
■
■
■
■
■
. the install path must not contain multi-byte characters. If you encounter this issue. a problem can occur if you use spaces in the pathname. 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.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. This problem is caused by the Sun Microsystems™ issue. you must remove the localized contents that are installed on your system. When you run on a non-English locale. Spaces in the pathname can cause a backup to fail.0 on top of an existing localized version NetBackup. The installation of NetBackup client to traditional Chinese paths that contain spaces such as C:\Program Files may cause backup failures. 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. 6901233. apply the Solaris patch that Sun provides to fix this issue 6901233. For Windows and UNIX installations. without installing the localized contents in the Language package CD first.do?bug_id=6901233 for more information about this issue. 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. See. You should install NetBackup client software to a path that does not contain spaces. http://bugs.

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

When that happens. This issue occurs because the stack size.3 platform. This command prints the system resources limit. data segment size.Operational Notes NetBackup Bare Metal Restore
61
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Storage Unit Disk pathname (Windows Only) Robot Name Device name Schedule Name Media ID Volume group Name Volume Pool Name Media Description Vault Policy Names Vault Report Names BMR SRT Name BMR Configuration Name
NetBackup Bare Metal Restore
The following list contains the items that relate to the NetBackup Bare Metal Restore feature:
■
An issue can occur when you use bmrsetupmaster on the command line interface (CLI) to configure a BMR master server on an AIX 5.0 or greater BMR master server on an AIX 5. To change the ulimit parameters:
■
Run the ulimit -a command on the BMR master server. More specifically. this issue occurs on a 7. data parsing fails while the BMR database is populated. Set the parameters to unlimited. and max memory size parameters. data seg size.3 or greater platform. Check the current limit set that is used for the stack size. If you encounter this issue. use the following procedure to change the ulimit parameters to “unlimited” and run bmrsetupmaster again. and max memory size ulimit parameters on the system are set too small. Run the following commands to change the limits:
■ ■
■
■
ulimit -s unlimited ulimit -d unlimited
.

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

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

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

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

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

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

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

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

0.
■
■
Add the following to the end of the notes.0 requires an IBM hotfix to address SPR# JCHN5QVL3E.5.ini file.0 on Linux requires a hotfix to resolve the following SPR: SPR#JCHN5QVL3E (which addresses a transaction log recovery issue).70
Operational Notes NetBackup database agents
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.ini file for Domino to work properly with NetBackup.0.lotus. perform the following steps:
■
Add the following line to the end of the notes. For each Domino partition.ini file for Domino to work properly with NetBackup. In addition.0.ini file for each Domino partition: DEBUG_SEMOP_ERRNO0_EINTR=1.nsf/Search?SearchView&Que ry=JCHN5QVL3E
■
Requirements for Lotus r6 and r6.0. In these releases.3 and Lotus R6. customers need to set the flag DEBUG_SEMOP_ERRNO0_EINTR in the notes. This issue has been fixed in R6.5 on Linux Support for any version of Lotus R6 or R6. After you install the hotfix on a Lotus Domino server.1 and R6. Requirements for Lotus r6.4 releases.
■
The hotfix was integrated into the R6.5. The last character in ERRNO0 is a zero.5.3 and Lotus r6. which involves a transaction log recovery issue.0 on Solaris SPARC and AIX Support for Lotus R6.lotus.5. Windows compressed images are not restorable to Lotus Domino servers on UNIX.0 on Linux Support for Lotus R6.4 and R6. See www-10.0. This flag allows retries to happen if and when the operating system returns an unexpected EINTR while LN performs semaphore operations.com/ldd/r5fixlist.ini file:
DEBUG_SEMOP_ERRNO0_EINTR=1
. you must make a change to the notes.com/ldd/r5fixlist. Restart the Domino server partition.5.1.3 or R6. See:
www-10.3 or r6.5.nsf/Search?SearchView&Query=JCHN5QVL3E
■
Requirements for Lotus r6.5 on Linux requires a change to the notes.0.

0 does not support the redirection of public folder items. use a NetBackup Client user interface on a NetBackup server to change the destination client value to the virtual server name. use the NetBackup Administration Console to initiate a manual backup for that Exchange policy.lotus.0.lotus.com/ldd/r5fixlist. www-10.1.nsf/Search?SearchView&Que ry=THUR5LPPW9.
For Lotus R6. See.
■
■
. These issues have been fixed in R6.Operational Notes NetBackup database agents
71
(NOTE: The last character in ERRNO0 is a zero. However.0.5. You can restore an Exchange database using a NetBackup client-only installation on a cluster.com/ldd/r5fixlist. R7.
■
Requirements for Lotus r6. A single IBM hotfix is available to address both issues. the backup fails. Restoring Exchange in a Cluster When you restore data in an Exchange cluster environment.3 and Lotus R6.4 and R6.)
■
Restart the Domino server partition. In that case. Instead. Exchange snapshot backups fail with status 41 "Network connection failed".0 on Windows Support for Lotus R6.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). the setting in notes. You should remove the previous Lotus hotfixes before you install this new combination hotfix. and going forward.5.5. it may not be possible to change the destination client value to match the virtual server name.0.
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. See.03 and Lotus r6. GUI initiation of an off-host snapshot backup When using the NetBackup Client user interface or the bpbackup command to initiate an Exchange off-host alternate client backup. www-10.5. one must set the destination client value to be the virtual server name.nsf/Search?SearchView&Que ry=JCHN5QVL3E.5.ini file is not required. See the "Testing Configurations Settings" section in the NetBackup for Exchange System Administrator ’s Guide for instructions regarding a manual backup operation.

or with Microsoft Information Store:\* in the file list. 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. Selecting one backup image at a time does succeed. When you restore a database or databases to a different DAG than where it was backed up. you cannot use the DAG virtual name as the destination client. To resolve this issue.72
Operational Notes NetBackup database agents
That problem occurs when you perform an Exchange snapshot backup attempt with Allow multiple data streams set on the policy.
■
Exchange 2010 DAG backups may fail with status 48 “Client hostname not found”. Restores of Exchange 2010 database in a Database Availability Group (DAG) environment notes:
■
■
■
■
When you restore a database to a recovery database. When you restore databases or granular items of a DAG backup. and with a large number of storage groups or databases in the file list. The work-around for this issue is to configure the FQDN so that it is resolved to the correct IP address. increase the value of the Client Connect Timeout in the master server Properties > Timeouts. you may experience failures.
■
■
When you select multiple backup images from a DAG backup with Enable Granular Recovery selected. Bpresolver may return the list of Exchange servers to perform the backup in a Fully Qualified Domain Name (FQDN) format. the restore status may be empty from the backup and restore user interface. you cannot use the DAG virtual name as the destination client. To work around this issue. 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. instead of a node name. Instead use the node that contains the active DB being restored to. Symantec and Microsoft are working on a solution for this problem. Instead. try the browse or restore operation again. The status is empty if the restore is initiated from a node in the DAG. You should initiate
■
. multiple “seed” emails from the backup service account may be sent to the mailbox being restored. use the node name where the RDB exists or the stand-alone Exchange 2010 server. When you attempt to browse or restore an Exchange mailbox from a GRT image from a Windows 2008 R2 Exchange server. During a Mailbox item restore. The initial step in an Exchange 2010 DAG backup is the bpresolver job on the virtual DAG node. granular level restores may fail. Modify the NetBackup server’s hosts files or correct DNS entries to resolve that.

Initiate the user backup from the active DAG node or manually start the backup from the NetBackup master to properly start the backup. or Exchange 2010 DAG). The problem occurs only with the default (Microsoft System) VSS provider. In NetBackup testing. 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. expire Copy 1 of the backup image in the catalog. 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. the bpfis. the rollback consumes the snapshot volume. If a single snapshot job processes a large number of storage groups or Exchange 2010 databases. in which the database volume is rolled back and the log volume files are copied back. the process virtual memory size can approach or exceed one gigabyte. The problem occurs when you recover from an Exchange Instant Recovery backup and one volume is rolled back while another is not. Support will be added shortly after the release of 7.Operational Notes NetBackup database agents
73
the restore from the active DAG node or a NetBackup server to properly see the activity status.exe process memory usage grows by a few megabytes per storage group or Exchange 2010 database. that might happen with a roll-forward recovery. The bpfis. Snapshot and catalog clean-up not performed after an Instant Recovery restore rolls back some snapshot volumes and copies back of others. Then use VShadow to make sure that the snapshot volume has been deleted. That leaves a partial snapshot set and an invalid IR copy of the backup image in the catalog. With this provider. Exchange 2007 CCR. Exchange 2010 offhost backups are not supported in NetBackup 7. To resolve this issue. This issue does not impact the ability to mount after restoring only an Exchange
■
■
■
■
■
■
■
. The company field of task objects does not get properly restored with Exchange 2010 granular recovery.0. Instant recovery backups are not supported for Exchange in a cluster environment (Exchange 2007 cluster.0. or to break up your backup into smaller snapshots.exe memory usage grows when a snapshot of multiple storage groups or Exchange 2010 databases is processed.
■
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. A special procedure is required to mount the database after the restore. The workaround is to make sure that you have sufficient virtual memory to accommodate this growth. For example.

■
NetBackup for Microsoft SharePoint
The following topics contain the operational note information that relates to the NetBackup for Microsoft SharePoint Portal.74
Operational Notes NetBackup database agents
offhost full backup. or under a specific policy and schedule.0. You can specify the exclude list entry under the All Policies. Entering a database is not valid. The following item applies to Exchange 2010: The exclude list entry is Microsoft Information Store:\Database_Name. and ignores it. or under a specific policy and schedule. even for the databases that exist in a DAG. You can specify the exclude list entry under the All Policies. However. If you enter a specific policy for a database in a DAG.
■
The following item applies to Exchange 2003 and 2007: You must specify the exclude list entry as Microsoft Information Store:\Storage_Group_Name.
. The entire backup finishes with an error. it causes the snapshot phase to fail with a status 69 error. if that is the only database in the bpfis job. This issue will be resolved shortly after the release of NetBackup 7. The snapshot phase detects it and ignores it. In this situation. because Exchange requires that VSS backups contain the entire storage group (for log truncation purposes). the discovery phase of the backup detects the exclude entry. if All Policies is entered for a database in a DAG. the discovery phase does not detect it.

To work around this issue. but not both. The cause of this issue. When you perform a SharePoint granular backup on a federated farm. restore the content database that contains the Tabs template site. The second attempt is successful. all load-balanced Web sites must be uniformly identified in IIS using either host headers or IP addresses. To avoid this issue. is unequal number of parenthesis on the database name field. As a workaround. Some items are not restored using GRT with the Tabs template. Environments which mix host headers and IP addresses across load-balanced servers are not supported. The SharePoint GRE restore view status displays incorrect characters for i18n Simple Chinese.
■
Operational Issues
The following operational issues exist for the Microsoft SharePoint:
■
When the SharePoint Search Index service updates the databases. To prevent restore failures. The SharePoint 2003 restores to the current date and time.Operational Notes NetBackup database agents
75
General Setup
The following is a list of general items pertaining to the NetBackup for Microsoft SharePoint:
■
When you use SharePoint 2003 load balancing. attempt the backup a second time. the bpfis child job gets a status 130 error on first attempt. Some items are not handled properly using GRT with Search Center template. restore the content database that contains the Search Center template site. The Search Center template. A SharePoint backup fails with a bpresolver core. As a workaround. The Search Center with Tabs template has some missing items for the restore. The metadata modified date is restored as the restored date. the IIS Default Application Pool identity must be a valid SharePoint user ID . it sometimes contends with NetBackup for access to the portal index database. make sure that you have an equal number of parenthesis that match in a database name. The restore does recover the files names with the correct characters. repeat the backup or restore operation until successful. That can result in a failed backup or restore operation of that database.
■
■
■
■
■
■
. If that occurs. The metadata restore is for SharePoint 2007 only. Discusion Board list item fails to restore.

1 installed and IPv6 enabled. the Windows service name has changed from ASANYs_VERITAS_NB to SQLANYs_VERITAS_NB. Until then. nbemm. restore. however a status 5 error occurs.0. When there are no empty containers preceding the picture library. You can remove these files if you are low on space. and Solaris. In addition. picture.
■
. Sybase has changed its name from Adaptive Server Anywhere (ASA) to SQL Anywhere.
SQL server agent
When you use the NetBackup for SQL Server user interface on 64-bit platforms. to a file system and then add it to SharePoint. This problem originates within the Windows 64-bit SDK and is expected to be resolved in a future release. the online Help cannot be opened. If you encounter this issue. you are not able to back up. 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. archive. dbsrv11.76
Operational Notes NetBackup database agents
■
A deleted list item that is in a Content-DB with Chinese characters may not restore to the original location.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. the SharePoint debug files on the backend are created during the backup in the INSTALL_DIR\VERITAS\NetBackup\Temp\ directory. In addition. This issue affects the HP-UX. As a workaround. the data can be recovered by redirecting to a file system or restoring the sites content database.0. may cause a core dump to occur on a master or remote Enterprise media server that has Sybase 11. then the restore works. open the help file directly using the Windows Explorer:
install_path\VERITAS\Help\nbmssql. you should know that the correct version of the item is restored and you can ignore the status 5 error. The Sybase service. platforms. These files are not removed after the backup. and nbars do not function properly. If this issue occurs. AIX. Restoring SharePoint picture libraries to the original location may fail when there are empty containers preceding the picture library. restore the item and any attachments that exist.
■
When you restore the most recent version of a document. That is intentional behavior for debugging purposes. or list a storage unit. or attachment the restore works. nbrb. To resolve this issue.

The following is an example of a volume GUID path:
\\?\Volume{26a21bda-a627-11d7-9931-806e6f6e6963}\
.conf (This is true as long as this file has not been moved to a different location.ServerPort=13785) To: tcpip(LocalOnly=Yes.
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.
■
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.On UNIX/Linux platforms: /usr/openv/var/global/server.ServerPort=13785) NOTE: LocalOnly=Yes is optional. Change: tcpip(LocalOnly=Yes. use the following procedure as a work-around:
■ ■
Stop NetBackup. and a policy with two Enterprise Vault servers that point to the same index location. The partial success occurs when you use an EV_INDEX_LOCATION directive. the Enterprise Vault redirected restore fails with a status 5 error. This folder must be present to perform a redirected restore. If the NetBackup/logs/AltPath folder is not present.0.1 or later NetBackup for Hyper-V has a known problem involving volume GUID paths. It can be missed or specified as LocalOnly=NO or LocalOnly=YES.On Windows platforms:
install_path\NetBackupDB\CONF\server.) . You can locate the database server configuration file at the following locations: .Operational Notes NetBackup Hyper-V
77
If you encounter this issue. Disable IPv6 by entering "ipv6=NO" in the database server configuration file.ipv6=NO.conf
■
Start NetBackup.0.

then the backup of the VM fails. with status code 5. Instead.
\\?\Volume{7b544c52-9cb7-11dd-a453-806e6c6e6963}\myVM\myvhd.vhd
This issue will be fixed in the first update after the NetBackup 7. This issue will be fixed in a future NetBackup release. so that NetBackup fails the restore when a path is incorrectly specified.0. an incorrectly specified UNC path (share name) for the destination should cause the restore to fail.
. The restore location on the system drive includes the server name and drive name as specified in the UNC path. For example.0 release. 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).
■
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.
NetBackup interfaces
The following subsections contain the release and operational information about the NetBackup interface.5 media server. while the VM is created.
■
Backup of Virtual Machines(VM) fails if the files that represent the VM have volume GUIDs instead of a drive letter in the pathname. such as the NetBackup Administration Console. NetBackup stores the errors in the Media log.
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. That enables you to view specific error types such as tape errors in Tape log report or disk errors in the Disk log report. you must install NetBackup patch 7.1 or a later release. Contact Symantec Technical Support to obtain the patch. and the Activity Monitor.78
Operational Notes NetBackup interfaces
If volume GUID paths exist in your Hyper-V environment. the files are restored to the system drive of the Hyper-V server. NetBackup also saves the errors into separate logs. Archive. and Restore interface on Windows). if the path of one or more of the VHD files are specified with a volume GUID.0.

If you select. The Disk Log report does not show information for the columns Schedule. This problem is caused by the Sun Microsystems™ issue. you can only view the errors in the Media log. http://bugs. NetBackup Management > Reports > Tape reports > Tape logs.
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. The Images On Disk report does not show data for a few columns (such as. Policy. no result is produced. and Status for Disk based reports. NetBackup does not log the errors into separate error logs.
NetBackup java interfaces
This section contains operational the notes that are applicable to NetBackup-java interfaces.0 media server. These pages are applicable only for a master server. See. If you encounter this issue. 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. 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.sun. apply the Solaris patch that Sun provides to fix this issue 6901233. Number of Files and Offset) for report on any disk type.Operational Notes NetBackup interfaces
79
However. Archive. 6901233.
■
■
■
The storage unit creation pages are not available in the Disk Pool wizard if the logged on host is a media server.
■
. The Tape log report appears empty.
■
Disk-based data protection resources The following items describe limitations with the disk-based data protection reporting in this release of NetBackup:
■
Help for the Images On Disk report might not provide complete information at all times. if you attempt to log errors from a 6.com/bugdatabase/view_bug.

however the label is misleading.
http://entsupport. 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.com/docs/335933
■
A Windows Manager that is configured for auto focus is not supported. Auto focus means that windows are activated (get the focus) when you position the mouse cursor over them.
■
For more information about this issue and a workaround solution. In the CDE environment. the Restore Marked Files dialog in the NetBackup-Java Administration console displays the Skip verification and force roll-back option as Overwrite existing files.InternalError: Can’t connect to X11 window server using "host_name" as the value of the DISPLAY variable. When you attempt to log on to the master server. When you configure a Point in Time rollback restore. The NetBackup-Java administration console on Windows (WDC) cannot connect to a UNIX master sever with a Japanese package.symantec.80
Operational Notes NetBackup interfaces
■
The Skip verification and force roll-back option does not appear in Restore Marked Files dialog. the NetBackup-Java administration console hangs at a point when the following status statement appears.
Checking if NBAC is configured. Reference the man page for the xhost command for additional capabilities.
■
java. refer to the following Technote on the Symantec Support Web site.
. The names of these options will be corrected in a future release of NetBackup. If you are not set up properly to display to a machine from where you run jnbSA.
Before you start jnbSA. The following explains how to correctly set up a CDE environment. because it is probably displayed on the machine from where jnbSA was run. The command fails with no error message. one of the following happens:
■
■
Nothing. The functionality of the Overwrite existing files option is the same as the Skip verification and force roll-back option. use the Style Manager -. 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. (That means the operating system command prompt was received.lang.

multiple bpjava processes appear on the host that is specified in the logon dialog. Other problems may occur that can cause the user interface to hang because of a Java Virtual Machine (JVM) failure. Solaris x64 HP-UX AIX Red Hat and SUSE Linux Windows platforms. The NetBackup-Java Administration Console runs on the following platforms:
■ ■ ■ ■ ■
■
■
Solaris SPARC. incorrect box operations.
■
Remote display of the NetBackup-Java console in multi-byte locale environments is not supported. installation is done using the Install Java Administration Console option in the NetBackup Windows installation user interface. and table display problems with large numbers of rows).
. The JVM failures occur most often on AIX platforms. very sluggish table scrolling with large numbers of rows. the last update that is made prevails. Problems have occurred with certain user interface controls (such as.Operational Notes NetBackup interfaces
81
■
Symantec recommends that only one administrator work on an object at a time. That eliminates the possibility of configuration conflicts if more than one administrator attempts administration tasks simultaneously on the same object. The number varies depending on the tasks that you attempt in the console. Refer to Chapter 2 (Platforms Supporting the NetBackup Administration Consoles for UNIX) of this document for the supported versions of these platforms. For the Windows platform. 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. Symantec does not recommend running the NetBackup-Java Administration Console in a remote display back configuration. If this situation should occur. Remote display back of the NetBackup-Java Administration Console is not recommended.
■
Multiple bpjava processes per instance of the console For increased performance and support to multitask easier on the console. Memory requirements to run the NetBackup-Java Administration Console Symantec recommends that you run the console (jnbSA. 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). jbpSA. Therefore.

82

Operational Notes About Symantec OpsCenter

Activity monitor
The following list shows the items that relate to the NetBackup Activity Monitor:
■

The ability to delete a large number of jobs When deleting a large number of jobs, do not leave the Activity Monitor node or close the NetBackup Administration Console while any of the deleted jobs are still visible in the Jobs tab. If the Activity Monitor is shut down while jobs are deleted, some of the jobs may not be deleted. The Activity Monitor can be shut down when you leave the Activity Monitor node or when you close the NetBackup Administration Console. The following message is displayed if you stop the bpdbm daemon on the relevant server when Activity Monitor is active.
Activity Monitor failed and must be restarted. To recover, first correct the problem described below and then refresh. Connection to bpjobd on server <server_name> failed.

■

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

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

■

About Symantec OpsCenter
The following list contains the items that relate to the Symantec OpsCenter feature:
■

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

Operational Notes NetBackup media and device management

83

■

After VBR upgrade, data is not displayed under Storage and Devices tabs After a VBR upgrade, data is not displayed under the Storage and Devices tabs in Monitoring. (Storage units, Robots, Drives, and so forth.) The data is not displayed as VBR does not collect any monitoring data, only the names are provided from the Job records. This data is collected after the upgrade as part of the regular data collection. An OpsCenter installation is not supported for the versions that are older than VBR 6.5. You cannot install OpsCenter on a system that has VBR installed with a version that is lower than 6.5 (for example, 6.2.x, 6.0.x, etc.). To work around this issue, upgrade the version of VBR to 6.5 or 6.6 and then upgrade to OpsCenter. Or uninstall VBR first and then install OpsCenter. Week at a Glance Report performance declines as the data increases. Week at a Glance Report’s performance declines as the data to be displayed in the report increases. For example, running a two-month report is slower than running a two-week report. After a reboot, the OpsCenter processes are not start automatically in AIX or SUSE Linux systems. Symantec recommends that you start the OpsCenter processes after you perform a reboot. The wrong client name is displayed for canned reports. If you select Reports > Activity Planning > Job Size in the OpsCenter user interface, the report that appears displays the wrong client name. Instead of showing the client names, a list of backed up VM images is displayed in this report. In addition, the list of VM images may not be accurate. After a rollback, the keys are not recreated to display an entry in Add or Remove Programs dialog box. If a rollback occurs during an uninstall of OpsCenter, the keys are not removed from Add or Remove Programs dialog box. You must remove OpsCenter. Use setup.exe to remove OpsCenter. After you reboot a SUSE 11 Server, and even though OpsCenter server services are running, an attempt to logon may not succeed. Occasionally, OpsCenter services may not start on reboot in case of SUSE 11. That may happen some times because of the PBX taking time to start.

■

■

■

■

■

■

NetBackup media and device management
The following subsection contains the information that is pertinent to NetBackup media and device management functionality.

84

Operational Notes NetBackup media and device management

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

A new script, pending_request_notify, has been added to this version of NetBackup. The NetBackup Resource Manager calls the pending_request_notify script after a pending request is issued for a media resource (tape volume). To send an E-mail notification when a pending request is initiated, include an E-mail address in the script where indicated. (The root user must run this script.) Copy the script from the goodies directory into the bin directory on the EMM server (usually the master server):
■

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

NetBackup uses the Media ID for disk as a unique identifier that can be traced back to a volume on the array. The Media ID is an opaque string that has internal meaning to NetBackup, but to nothing else. In addition, the Media ID can be correlated to a volume by running nbdevquery -listmediaid command. SCSI persistent reserve NetBackup can use SCSI persistent reserve in and persistent reserve out to configure exclusive access protection to tape drives so that other host bus adaptors (HBAs) cannot control the drives during the reservation. SCSI persistent reserve provides more resiliency and fault tolerance than SPC-2

■

backup. 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.75 for IBM 6228 card _ AIX Oslevel 5200-07
■
■
■
For 64-bit NetBackup media servers. Not installing the following driver can result in a hung Fiber Transport (FT).2. the QLA-2344 HBA performs similarly to two QLA-2342 HBAs but uses one less PCI slot. which is the default access protection method in NetBackup. PCI-express. If you use data compression or encryption for backups. 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. 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. In some configurations. Consequently. Legacy PCI 33 and 66 Mhz slots are not supported. NetBackup SAN clients cannot also be NetBackup servers. data transfer rates are reduced and performance is degraded.
■
■
■ ■ ■
.
AIX FC driver version level 5. On the NetBackup media servers. No support for Fibre Channel arbitrated loop (FC-AL) hubs. No support for FlashBackup restores over an FT pipe.
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. compression may reduce performance by up to 95% of uncompressed performance. 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. A slower PCI card reduces the speed of the controlling bus and therefore all other cards in that bus.0. The advantage a QLA-2344 HBA offers is the ability to spread its aggregate performance over four ports instead of two. and restore Fibre Transport pipe performance may degrade significantly.Operational Notes SAN Client and Fibre Transport
85
SCSI reserve and release. 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.

NetBackup Client Deduplication
The following items pertain to NetBackup 7. the daemons cannot be started. Symantec expects Oracle database stream-based backups to achieve low deduplication rates. You can use a NetBackup 7.5 media servers. NetBackup 7. you can ignore it.0 and later
The SharedDisk option is not supported beginning with the NetBackup 7. Therefore.
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.0 and later
SharedDisk support in NetBackup 7. The error is spurious.0 Client Deduplication does not support encryption.5 release. The status 2 indicates that the script cannot start the deduplication daemons. the netbackup start script returns status 2.86
Operational Notes SharedDisk support in NetBackup 7. For information about using SharedDisk. see the documentation for your NetBackup 6. NetBackup does not support clustering of deduplication storage servers or load balancing servers.
NetBackup AdvancedDisk option
NetBackup does not support clustering of AdvancedDisk media servers. and operate SharedDisk on NetBackup 6. Stream-based backups include deduplication within a
■
■
■
■
. do not enter an NFS file system when you configure the data storage path. Because a storage server is not configured.0 release.0 Client Deduplication does not support multiple copies. manage.0 Client Deduplication:
■ ■
NetBackup 7. The NetBackup Media Server Deduplication Option does not support NFS mounted file systems.0 master server to configure. deduplication rates are low even though data has not changed since the last backup. For the Microsoft Exchange backups that use the NetBackup Exchange Agent.

do not use the same media server for both NetBackup and as a PDDO host. Therefore. the backups that were made at different times may create snapshot disk groups with the same name. NetBackup may not be able to remove the catalog images for the snapshots that have expired and been deleted. Snapshot creation fails (with final status 156). From a policy that was configured with the FlashSnap off-host backup method and with Retain snapshots for Instant Recovery enabled. In addition."
■
Instant Recovery restores may fail from a backup that a FlashSnap off-host backup policy made. NetBackup cannot create a disk array snapshot of a file system that is configured on the VxVM volume. only one snapshot can be retained at a time.
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. Snapshot Client backups of Oracle databases achieve high deduplication rates across full backups within our test environments. It appears that you can browse the expired
. and IBM_StorageManager_FlashCopy.
■
NetBackup does not support the Snapshot Client off-host method Media Server Copy on NetBackup clients that deduplicate their own data. Examples of disk array snapshot methods are EMC_CLARiiON_SnapView_Snapshot. in the chapter titled "Configuration of snapshot methods for disk arrays.
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. As a result. Oracle Snapshot Client based backups have higher deduplication because the data is aligned on consistent file or tablespace boundary. If a software-based snapshot (such as from the VxVM method) already exists of a VxVM volume on the disk array. Hitachi_CopyOnWrite. HP_EVA_Snapshot. All disk array methods are described in the NetBackup Snapshot Client Administrator's Guide. This issue will be fixed in a future release of NetBackup. However. You must delete the existing VxVM snapshot from the VxVM disk group before you run a backup with a disk array snapshot method. and the bpfis log contains a message that reports a vxmake command failure.Operational Notes PureDisk Deduplication Option (PDDO)
87
single backup and deduplication between a backup and data already backed up.

NetBackup honors the latest version of the exclude list during the restore. But the snapshots no longer exist. To restore the files. however. 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. the .jpg. NetBackup incorrectly consults the current exclude list on the client or alternate client. any files that are listed in the exclude list on the alternate client are not restored to the primary client. the . The exclude list is consulted only when a storage unit backup is created from the snapshot. For example. If the exclude list on the alternate client is different from the exclude list on the primary client. any files that were included in the exclude list are not backed up. NetBackup does not support Snapshot Client VSS off-host file backups using a Storage Foundation for Windows (SFW) VSS provider. Note: For ordinary backups (not based on snapshots). and the restore fails with status 5.jpg. and some .
■
For this release. To restore the files. all files are included in the snapshot. the exclude list on the alternate client takes precedence over the exclude list on the primary client.88
Operational Notes NetBackup Snapshot Client
snapshots and restore files from them.jpg files were included in the primary client backup. you must change the exclude list on the alternate client. Any of the files that are listed in the current exclude list are not restored. NetBackup does not support the Snapshot Client off-host method media server Copy on NetBackup clients that deduplicate their own data. If the snapshot is retained after the backup (for the Instant Recovery feature) and the snapshot is available at the time of the restore. Since all files are available in the snapshot (including those that would be excluded from a storage unit backup).jpg files can be selected for the restore but are not in fact restored. 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. For example: If the current version of the exclude list has the entry *. and some .
■
. as noted in the previous item.jpg files can be selected for the restore but are not in fact restored. if the alternate client's exclude list has the entry *. Also. Any files in the exclude list are skipped during the restore. NetBackup restores files from the snapshot. you must change the exclude list on the primary (or alternate) client. For snapshot-based backups.jpg files were included in the backup.

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 deletes all files that were created after the creation-date of the snapshot that you restore. 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. the Point in Time Rollback operation is aborted. However. Note that a rollback deletes all files that were created after the creation-date of the snapshot that you restore. 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.
■
bpclimagelist
.
■
NBCCR
See “About NetBackup support utilities” on page 18. In that case. refer to the NetBackup Commands guide:
■
NBCC
See “About NetBackup support utilities” on page 18.
NetBackup commands and utilities
This release of NetBackup contains new commands and utilities. Rollback returns a file system or volume to a given point in time.Operational Notes NetBackup commands and utilities
89
This issue will be addressed in a future release of NetBackup. the snapshot cannot be unmounted. the snapshot is mounted and in some cases. See "Instant Recovery: point in time rollback" in the NetBackup Snapshot Client Administrator's Guide for more information on rollback. during the verify operation for the rollback. the file system verification is mandatory and this issue prevents a successful rollback.
■
Problem with "Restore from Point in Time Rollback" When you start a "Restore from Point in Time Rollback" from an Instant Recovery backup. For a rollback of a file system. you can skip file verification by selecting "Skip verification and force rollback" on the restore dialog. The problem that is described here is avoided and the rollback succeeds. For a description of each of the following commands. Note: For a rollback of a database backup such as Oracle.

For that image and all subsequent images.
■
nbregopsc
You use this command to register OpsCenter.
■
bptestnetconn
This command test and analyzes various NetBackup configurations and connections. not the setting of the destination storage unit.
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.
■
nbcplogs
You can use this command to copy all NetBackup logs to a designated destination. Beginning with release 7.0. NetBackup performs a regular duplication. Therefore. you also must update the vendor plug-in to a 64-bit version.exe diagnostic information gathering utilities are no longer included or supported beginning with this release of NetBackup. NetBackup does not resize or rearrange the backup image into a different set of fragments). NetBackup copies the image fragments as is (that is.
■
nbkmsutil
This command runs the NetBackup Key Management Service utility.90
Operational Notes NetBackup OpenStorage Option
This command produces a status report on NetBackup client images or removable media.
■
■
■
.
■
bpclusterutil
You can use this command to modify and configure a NetBackup cluster. NetBackup requires OpenStorage vendor plug-ins to be 64-bit.0. When you upgrade a media server that is used for OpenStorage to NetBackup 7. NetBackup performs optimized duplication until it encounters an image for which optimized duplication is not possible. NetBackup binaries are compiled in 64-bit. NetBackup uses the fragment size setting of the source storage unit. The support and support.

the nb_updatedssu command runs. you now need to use a different command.Operational Notes NetBackup Disk Storage units
91
NetBackup Disk Storage units
The following list contains the operational information that pertains to the Disk storage unit:
■
Upon NetBackup installation or upgrade. these enhancements have the following effect on users who have upgraded from previous versions to NetBackup 7. are converted to the new tracking mechanism. Relocated data is tracked differently in the current release and the .0:
■
If pre-NetBackup 7. The command deletes the . Under some circumstances.
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. then the properties of the BasicDisk STU do not appear in the storage unit dialog that is shown in the 7. Symantec recommends that you process all these sessions (meaning that you complete all ejects and reports) before you upgrade to ensure minimal affect. If that occurs.ds file may not be deleted upon installation or upgrade. A pop-up window appears and contains the following message:
CORBA::BAD Param. Symantec recommends that you run the command again to ensure that all .ds files are removed:
install_path\netbackup\bin\admincmd\nb_updatedssu /usr/openv/netbackup/bin/admincmd/nb_updatedssu
Note. You can use the following command.0 sessions are not processed completely before an upgrade. a . you should copy the summary.0.ds files that were used in the previous releases as pointers to the relocated data. if you have any written scripts that make use of the . For example.
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. to display the potential free space for the volume.ds files to compute the amount of "potential free space" on a volume. At a minimum. These enhancements specifically target a system where NBAC is configured and the Vault service manages the important read-write data.ds files.0 user interface.log
.

■
Create a UNIX group and add the appropriate users to this group. Check with your system administration or computer security staff to ensure that you do not violate security policies.
■
The presence of the VLT_CREATE_SESSION_DEBUG_FILES touch file has no affect on the new session permissions.0 version. giving users special privileges may violate your organization’s computer and network security policies and allow access to private information. log files are written to sidxxx/logs. In addition. If you do not want non-root users to view reports and change report destinations. you must make sure that you account for the enhancements that were packaged in NetBackup 7.0. If you do not configure NetBackup Access Control. 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
■
. This group is referred to as opsgroup in the following commands. For example. then give that group permission to execute some of the executable files.
■ ■
■
■
Vault Operator Access on UNIX. you can still set permissions on UNIX systems so that non-root users can use the operational commands in the Vault Operator Menu to inject and eject tapes and generate reports.0 session directories are not modified. Giving users access to the Vault Operator Menu also gives them the capability to change report destinations. you may not want non-root users to see the Recovery Report or to be able to change to whom reports are e-mailed.0 and decide to downgrade to a pre-NetBackup 7.92
Operational Notes NetBackup Vault
from the sidxxx directory to a new sidxxx/logs directory to accommodate eject/reports eligible sessions. The most efficient way to accomplish that is to add the users to whom you want to grant access to a single user group. For example. the summary.log is now written to sidxxx/logs directory. and files and folders have restrictive permissions when they are created. If you upgrade to NetBackup 7. For example. The permissions of pre-NetBackup 7. do not give them access to the Vault Operator Menu. You may need to update the notify scripts appropriately with respect to the directory structure changes.

log on to that server and modify the . 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.Operational Notes NetBackup for VMware
93
# chmod 4550 vltrun # cd /usr/openv/netbackup/bin/admincmd # chgrp opsgroup bpimagelist bpimmedia bpmedia bpmedialist # chmod 4550 bpimagelist bpimmedia bpmedia bpmedialist
■
Log on to all systems on which NetBackup media servers are installed that control a robot and execute the following commands as root:
# cd /usr/openv/volmgr/bin # chgrp opsgroup vmchange vmquery vmupdate # chmod 4550 vmchange vmquery vmupdate
■
If you use Sun StorageTek ACSLS for robotic control. For simplicity. Modify that entry to allow all users in the opsgroup access to the Sun StorageTek ACSLS server as user acsss:
master_server_name root <user1> <user2> . The NetBackup installation process should have added an entry to the . To verify the proper operation. Use of the Full VM backup option results in a lower rate of deduplication. log on as a non-root user on the NetBackup master server system. If both servers use a naming service (such as NIS). each user should have the same user ID on both servers.
■
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.rhosts file in the home directory of user acsss.
. This option provides the best deduplication rates.rhosts file for the NetBackup master server that grants root access. . select the Mapped full VM backup option for the Virtual machine backup parameter on the VMware snapshot method. <userx>
If you use Sun StorageTek ACSLS for robotic control. . Start vltopmenu and execute each menu option. you can skip this step.

If a virtual machine with multiple network interfaces is restored to an ESX server that has fewer network interfaces. a backup that uses the hotadd transfer type may appear to succeed. VMware has identified this issue as software defect SR#1442259141. This issue will be addressed in a future release of VMware and NetBackup. However. This issue occurs when NetBackup 7. As a workaround." This problem occurs when NetBackup uses the VMware vStorage integration services. The virtual machine that you back up with the hotadd transport type cannot be a clone of the virtual machine that contains the backup host. Furthermore. If you want to use the hotadd transport type with your backup. some of the virtual machine's network interfaces are not restored. VMware has identified this problem and will address it in a future release. If the VMware backup host is in a virtual machine. the virtual machine when restored may attempt to boot from the IDE drive. If a virtual machine containing a RAID 5 volume was backed up with VMware vStorage services (not VCB) using the SAN transfer type. you can reconfigure the BIOS on the virtual machine to boot from the correct SCSI disk. and that virtual machine is a clone of the virtual machine that you backed up.94
Operational Notes NetBackup for VMware
■
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). some of the virtual machine volumes may be incorrectly mapped and cannot be restored. This issue will be addressed in a future release of NetBackup. As a workaround.
■
■
■
. In that case. NetBackup for VMware does not support backing up virtual machine RAID 5 volumes with the SAN transfer type. VMware virtual machine does not reboot after restore If a virtual machine was configured with SCSI and IDE drives at the time of backup. That ensures all of the virtual machine's original network adapters are restored when the virtual machine is restored. The converse is also true. the two virtual machines must not be clones of the same parent. Make sure the virtual machine that contains the VMware backup host and the virtual machine you back up are not clones of each other. do the following. and the guest OS resided on a SCSI drive.0 performs a restore with the VMware vStorage infrastructure services. the boot attempt fails with the message "Operating system not found. Make sure that the network connections are correctly identified and selected on the NetBackup "network connections " Restore dialog. the RAID 5 volume may not be correctly restored. you can configure additional network interfaces on the destination ESX server before you run the restore.

and Restore interface on Windows. make sure that you do not exclude drives on proxy clients when you perform a VCB backup. only the most recent BLIB backup of that virtual machine can be restored. 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. Otherwise. For hotadd backup or restore. To speed up the restore. Archive. use the nbd transfer type instead of hotadd. If the backup host is in a Windows 2008 virtual machine. The detailed status log on the NetBackup Activity Monitor includes the message. the hotadd restore fails with NetBackup status 5. To avoid this issue. To restore from previous BLIB backups of the virtual machine. the restore job may be slow if you restore to a vCenter Server.” The same VMware restriction applies to virtual machine restore: The virtual machine to restore and the virtual machine that contains the hotadd restore host must reside in the same VMware datacenter. Until this issue is fixed. Virtual machine restore: file write failed. the restore failed to recover the requested files. If you try to restore an earlier backup made from the same policy. (ET2086326) For hotadd backup or restore.Operational Notes NetBackup for VMware
95
■
The restore of a virtual machine fails when you use the hotadd transport mode if the VMware backup host is on a Windows 2008 virtual machine. Because of a VMware issue (SR#1438908741). the hotadd backup fails with NetBackup status 6. the restore fails. use the Backup. However. any drives that you specify to be excluded from the proxy client are also excluded from the virtual machines. Otherwise. The job details log contains the message “unable to open disk error(23). 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). the backup host must be in a Windows 2003 virtual machine to use the hotadd transfer type for the restore. Restoring a virtual machine through a vCenter Server may be slow when using the SAN transfer type When you use the SAN transfer type to restore a virtual machine. the virtual machine and the hotadd backup host must reside on the same VMware datacenter To back up a virtual machine by means of the hotadd transfer type. Symantec recommends at least one hotadd backup or restore host for each datacenter. The final job status code is 5. restore the virtual machine directly to an ESX server.
■
■
■
. the VMware backup host must be installed in a virtual machine. VMware requires that the virtual machine to back up and the virtual machine that contains the hotadd backup host reside in the same VMware datacenter.
■
You can use a proxy client for VMWare Consolidated backups (VCB).

96
Operational Notes NetBackup for VMware
.

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

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

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

100
End of Life Notifications About features. are no longer supported as of this release of NetBackup. enhancements. NetBackup for Microsoft SQL Notifications NetBackup no longer supports SQL Server 7. andsupport. A new utility.0 backup and recovery.
■
■
About NetBackup commands no longer supported
The commands in the following list are no longer supported with this release of NetBackup:
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
bpmoverinfo nbnos bpSALinfo nbpushdata nbshareddisk tshd odld set_ndmp_attr tpformat bpuser bpauthsync
Enhanced Authentication (noauth authentication methods) and Enhanced Authorization are no longer supported. and commands no longer supported
■
NetBackup for Microsoft SharePoint Portal Notifications NetBackup 7. The diagnostic information gathering utilities and programs.5 replaced these utilities.
■
■
. NetBackup for Microsoft Exchange Server NetBackup 7.5. The FSAnalyzer is no longer supported in this release of NetBackup.exe.0 no longer supports Exchange 5. nbsu. support.0 no longer supports SharePoint Portal Server 2001 backup and recovery.5 or Exchange 2000 backup and recovery. introduced in NetBackup 6. The last release of the FSAnalyzer was NetBackup 6.

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

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

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

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

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

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

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

108
Related Documents About NetBackup command documents
.

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

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