Symantec NetBackup Release Notes. NetBackup 7.0.1

Transcription

1 Symantec NetBackup Release Notes NetBackup 7.0.1

2 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: Legal Notice Copyright 2010 Symantec Corporation. All rights reserved. Symantec and the Symantec Logo are trademarks or registered trademarks of Symantec Corporation or its affiliates in the U.S. and other countries. Other names may be trademarks of their respective owners. This Symantec product may contain third party software for which Symantec is required to provide attribution to the third party ( Third Party Programs ). Some of the Third Party Programs are available under open source or free software licenses. The License Agreement accompanying the Software does not alter any rights or obligations you may have under those open source or free software licenses. Please see the Third Party Legal Notice Appendix to this Documentation or TPIP ReadMe File accompanying this Symantec product for more information on the Third Party Programs. The product described in this document is distributed under licenses restricting its use, copying, distribution, and decompilation/reverse engineering. No part of this document may be reproduced in any form by any means without prior written authorization of Symantec Corporation and its licensors, if any. THE DOCUMENTATION IS PROVIDED "AS IS" AND ALL EXPRESS OR IMPLIED CONDITIONS, REPRESENTATIONS AND WARRANTIES, INCLUDING ANY IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR NON-INFRINGEMENT, ARE DISCLAIMED, EXCEPT TO THE EXTENT THAT SUCH DISCLAIMERS ARE HELD TO BE LEGALLY INVALID. SYMANTEC CORPORATION SHALL NOT BE LIABLE FOR INCIDENTAL OR CONSEQUENTIAL DAMAGES IN CONNECTION WITH THE FURNISHING, PERFORMANCE, OR USE OF THIS DOCUMENTATION. THE INFORMATION CONTAINED IN THIS DOCUMENTATION IS SUBJECT TO CHANGE WITHOUT NOTICE. The Licensed Software and Documentation are deemed to be commercial computer software as defined in FAR and subject to restricted rights as defined in FAR Section "Commercial Computer Software - Restricted Rights" and DFARS , "Rights in Commercial Computer Software or Commercial Computer Software Documentation", as applicable, and any successor regulations. Any use, modification, reproduction release, performance, display or disclosure of the Licensed Software and Documentation by the U.S. Government shall be solely in accordance with the terms of this Agreement.

3 Symantec Corporation 350 Ellis Street Mountain View, CA

4 Technical Support Contacting Technical Support Symantec Technical Support maintains support centers globally. Technical Support s primary role is to respond to specific queries about product features and functionality. The Technical Support group also creates content for our online Knowledge Base. The Technical Support group works collaboratively with the other functional areas within Symantec to answer your questions in a timely fashion. For example, the Technical Support group works with Product Engineering and Symantec Security Response to provide alerting services and virus definition updates. Symantec s support 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/or Web-based support that provides rapid response and up-to-the-minute information Upgrade assurance that delivers software upgrades Global support purchased on a regional business hours or 24 hours a day, 7 days a week basis Premium service offerings that include Account Management Services For information about Symantec s support offerings, you can visit our Web site at the following URL: All support services will be delivered in accordance with your support agreement and the then-current enterprise technical support policy. Customers with a current support agreement may access Technical Support information at the following URL: Before contacting Technical Support, make sure you have satisfied the system requirements that are listed in your product documentation. Also, you should be at the computer on which the problem occurred, in case it is necessary to replicate the problem. When you contact Technical Support, please have the following information available: Product release level

5 Hardware information Available memory, disk space, and NIC information Operating system Version and patch level Network topology Licensing and registration Customer service Router, gateway, and IP address information Problem description: Error messages and log files Troubleshooting that was performed before contacting Symantec Recent software configuration changes and network changes If your Symantec product requires registration or a license key, access our technical support Web page at the following URL: Customer service information is available at the following URL: Customer Service is available to assist with non-technical questions, such as the following types of issues: Questions regarding product licensing or serialization Product registration updates, such as address or name changes General product information (features, language availability, local dealers) Latest information about product updates and upgrades Information about upgrade assurance and support contracts Information about the Symantec Buying Programs Advice about Symantec's technical support options Nontechnical presales questions Issues that are related to CD-ROMs or manuals

6 Support agreement resources If you want to contact Symantec regarding an existing support agreement, please contact the support agreement administration team for your region as follows: Asia-Pacific and Japan Europe, Middle-East, and Africa North America and Latin America

7 Contents Technical Support... 4 Chapter 1 New Features About NetBackup New Features About remote NDMP multiplexing About NetBackup audit trail About NetBackup client option Volume GUID for Windows cluster About NetBackup BMR enhancements Creating an SRT for Windows About the supported boot media on Windows platform About the Legacy Restore function About NetBackup for SQL server agent enhancements About Symantec OpsCenter enhancements About Enterprise Vault 9.0 support About NBSU support for NetBackup About NBCC and NBCCR enhancements About NetBackup Snapshot Client About VMware vsphere About NetBackup documentation updates Chapter 2 Supported Platforms About NetBackup supported platforms About NetBackup platform proliferation support NetBackup binary sizes Chapter 3 Product Dependencies Operating system patches and updates Chapter 4 Operational Notes and Issues About NetBackup known issues About documentation issues About General NetBackup issues About NetBackup installation and upgrade issues... 41

8 8 Contents About Bare Metal Restore (BMR) issues About port usage during a restore operation About the supported boot media on a Windows platform About the Legacy Restore function in BMR About NetBackup database agents About NetBackup DB2 database agent About NetBackup for SharePoint Server issues About NetBackup for Exchange server database agent About NetBackup Deduplication About NetBackup Snapshot Client issues Creating space-optimized snapshots About NetBackup Hyper-V issues About NetBackup NDMP issues About NetBackup OpsCenter issues About uninstalling Symantec OpsCenter 7.0 before OpsCenter on UNIX About NetBackup Vault issues About NetBackup VMware issues Chapter 5 End of Life Notifications About End-of-life notifications for Appendix A index About the NetBackup7.0.1 master Etrack index list NB_JAV_ NB_CLT_ NB_7.0.1.winnt.IA NBLU_7.0.1.WIN NB_OPS_CTR_7.0.1.winnt.x NB_ NBLU_7.0.1.UNIX NB_OPS_CTR_7.0.1.winnt.IA NB_JAV_7.0.1.winnt.IA NB_DRO_ NB_JAV_7.0.1.winnt.x NB_7.0.1.winnt.x NB_OPS_CTR_ NB_OPS_CTR_7.0.1.winnt.x NB_JAV_7.0.1.winnt.x

9 Contents 9 Appendix B About release content conventions

10 10 Contents

11 Chapter 1 New Features This chapter includes the following topics: About NetBackup New Features About remote NDMP multiplexing About NetBackup audit trail About NetBackup client option Volume GUID for Windows cluster About NetBackup BMR enhancements About NetBackup for SQL server agent enhancements About Symantec OpsCenter enhancements About Enterprise Vault 9.0 support About NBSU support for NetBackup About NBCC and NBCCR enhancements About NetBackup Snapshot Client About VMware vsphere 4.1 About NetBackup documentation updates About NetBackup New Features The following subsections introduce the primary features of NetBackup

12 12 New Features About remote NDMP multiplexing Note: If you encounter an error during Beta testing, Symantec wants you to log and report the error to Symantec's technical support. Symantec appreciates your help during the Beta program so that we might work towards addressing those issues before the final release. About remote NDMP multiplexing Remote NDMP multiplexing enables concurrent writing of multiple backup streams, through a NetBackup media server, to a single tape drive. The main reason for multiplexing is to improve overall NetBackup performance by better using tape drives. State of the art tape drives can typically stream data much faster than NDMP hosts can create provide backup data. That is especially true with small file sizes. Multiplexing addresses the following: It allows for a greater number of concurrent backup operations given a limited number of target tape drives. Because the tape drives can accept data faster than an NDMP host can provide data, several NDMP hosts (or NetBackup clients) can concurrently send data to the same tape drive. That reduces the overall backup time. Many tape drives require a high minimum data rate to maintain streaming. When data is not streamed fast enough, the drive must reposition and that reduces the efficiency of the tape device. It also lengthens the backup time and subjects the tape drive to increased wear. About NetBackup audit trail NetBackup auditing provides companies with an audit trail of user-initiated actions in a NetBackup environment. Essentially, auditing gathers the information to help answer who changed what and when they changed it. Compliance laws and various regulatory agencies require that many companies keep track of changes made within their environment that relate to protecting data. Because backups are performed to protect data, that means configuration changes within backup applications must be tracked. Customers can use NetBackup auditing to more efficiently resolve problems within their environment. With auditing configured, they can track user-initiated actions so that unexpected behavior can be traced back to its origin. The following list summarizes the user-initiated actions and auditable actions that are available to the customer.

13 New Features About NetBackup client option 13 Policy create, update and delete Restore job initiation Audit configuration changes Audit service start and stop In 7.0.1, auditing is configured using a new nbemmcmd command option. Audit reports are generated using the new command, nbauditreport. About NetBackup client option The new Offline option in the Client Attributes properties lets administrators take individual clients offline to make the clients unavailable for backups. When a client is offline, no backup status is listed for the client. That is useful in a number of situations. For example, in the event of planned maintenance, you can take the client systems offline to avoid the unnecessary errors that then need to be investigated. This option can also be used to anticipate new clients in the system. The clients can be listed in policies but configured as offline until they are in place and ready to be used. In addition, you can specify a period of time that the client is automatically enabled again. That prevents users from forgetting about the clients that were in an offline state. Volume GUID for Windows cluster There are three types of volume mount points: A drive letter such as, C:\. A volume GUID path such as, \\?\Volume{26a21bda-a627-11d e6f6e6963}\. A mounted folder such as, C:\MountD\. Previous releases of NetBackup for Hyper-V had an issue with volume GUID paths such as, \\?\Volume{26a21bda-a627-11d e6f6e6963}\. If volume GUID paths exist in your Hyper-V environment, you need to install this NetBackup patch or a later release. This release of NetBackup supports Volume GUID pathnames for Windows clusters as well as Hyper-V clusters. If you need assistance Contact Symantec Technical Support to obtain the patch.

14 14 New Features About NetBackup BMR enhancements About NetBackup BMR enhancements In addition to the existing platforms, NetBackup BMR supports restores of HPIA clients. The following section contains the exact lists of the features that are supported or not supported on this platform. Features that are supported in BMR on HPIA platform: Full LVM volume manager support VxVM volume manager support on non-bootable disk. VxFS-based File Systems Restore support Network and Media boot Point In Time Restore Latest ignite version support - C Partial support for DDR (Dissimilar Disk Restore) Disk and partition mapping Volume length changes Features that are not supported in BMR on HPIA platform: BMR restore with NBAC enabled Full BMRCONFIG support Volume layout changes. For example, concatenated to mirror SAN LUN-based volume restore VxVM support for root and boot disk SF support Non-bootable VxVM volume restore works using SF 5.0. In this release of the NetBackup, the BMR feature contains an enhancement with how shared resource trees are created. Creating an SRT for Windows Windows SRTs no longer require the user to supply a version of Windows. The SRTs use a special version of Windows that is shipped with the boot server.

15 New Features About NetBackup BMR enhancements 15 To create a Windows SRT 1 From the Start menu on the Windows BMR boot server that is to host the SRT, select Programs > Symantec NetBackup > Bare Metal Restore Boot Server Assistant. The Bare Metal Restore boot server Assistant appears. 2 Click Shared Resource Tree Administration Wizard. The Shared Resource Tree Administration wizard appears. You can use an SRT that contains the NetBackup client of 7.0 or higher versions to restore the back-level NetBackup clients. 3 Select the option to create a shared resource tree. Then follow the prompts to create a shared resource tree. You must provide the following information: Name Description Locations for the SRT The name of the SRT is also used for the directory that contains it. Only alphanumeric characters and the underscore (_) character are allowed. Enter the description of the SRT. For example: Windows 2008 SRT When you create the 32-bit or 64-bit SRT for the first time a screen appears where you specify the source location of SRD. For 32-bit SRT, specify the source location of srd.wim, which is as follows: <DVD root>\addons\x86\bmrbs For 64-bit SRT, specify the source location of srd_x64.wim, which is as follows: <DVD root>\addons\x64\bmrbs <DVDroot > is the root folder on the NetBackup Windows installation DVD. Path to the NetBackup client software image Enter the path of the BMR client software image. About the supported boot media on Windows platform Boot media is used to boot a client and provide the Shared Resource Tree or the resources to mount a Shared Resource Tree. The boot media contains a small runtime environment that includes a kernel, a RAM file system, libraries, and programs. The client system firmware boots the kernel from the media. CD boot

16 16 New Features About NetBackup BMR enhancements media also contains a Shared Resource Tree. If you use media to boot the client system, you must use BMR to prepare the appropriate boot media. You can prepare boot media at any time before the restore. However, a prerequisite is that the Shared Resource Tree for the protected system must exist. Boot media is created from the resources that are stored in an SRT. The boot media must be compatible with the commands and libraries in the SRT and the client. The BMR restore process begins by network booting the client from a BMR boot server or from BMR prepared boot media (CD or DVD). You can restore a client using Fast Restore SRTs or Legacy OS-based SRTs. Versions older than BMR also supported floppy as a boot media if you selected the Legacy OS-based Restore option, on a Windows platform. Note: The Legacy OS-based Restore of Windows Server 2008 SP2 systems can be done with a Legacy OS-based SRT that is at Windows Server 2008 SP1 level. The Prepare To Restore command allows this special scenario. Note: In BMR 7.0.1, floppy-based restore is not supported. In BMR 7.0.1, you can boot BMR clients only with the following options: Network boot CD/DVD Media boot Note: In BMR 7.0.1, because of the elimination of PC-DOS, you do not need to create Boot Floppy. Therefore the Legacy Boot Floppy Wizard link on the boot server Assistant screen is removed. About the Legacy Restore function In BMR 7.0.1, the Legacy Restore function is modified with the following changes: PC-DOS is no longer required to run a Legacy Restore. Unlike in BMR 7.0, the Legacy Restore function in boots from a WinPE boot image. This change in the boot process of the Legacy Restore option reduces maintenance and overheads. In BMR 7.0.1, you do not need to do the following tasks: Download and store DOS extensions. Maintain the floppy disks, which are now outdated as media. Download and maintain DOS-compatible drivers.

17 New Features About NetBackup for SQL server agent enhancements 17 Maintain floppy disk Drives (FDDs) for BMR Restore purpose. As a result of PC-DOS elimination, you do not need to create Boot Floppy. Therefore the Legacy Boot Floppy Wizard link on the boot server Assistant screen is removed. PC-DOS is replaced with WinPE, therefore the Legacy Restore can boot with the PXE-based network option. Unlike PC-DOS, WinPE does not require a 16-bit Windows Installer binary. Therefore, BMR provides the Legacy Restore support also for the 64-bit editions of Windows. PC-DOS-based Legacy Restore requires approximately eight reboots during the restore. With WinPE-based Legacy Restore, the number of reboots is reduced to approximately five. Note: With WinPE in place of PC-DOS, the Legacy Restore requires an additional free space of 2 GB to 4 GB in the system s boot partition. The boot partition is the one that contains the operating system. About NetBackup for SQL server agent enhancements The NetBackup Database Extension graphical user interface for SQL contains a new option that enables you to use SQL server's native compression feature on a backup. That is a new feature for SQL 2008 and beyond. You can also add compression to your backup by adding the entry, SQLCOMPRESSION TRUE, in the SQL batch file. The following figure shows the new option as it appears in the user interface.

18 18 New Features About Symantec OpsCenter enhancements About Symantec OpsCenter enhancements A new option has been added in the SelectViewName drop-down list of the Report wizard. The name of the option is None. You can see this option when you create or edit a report and specify the views that are associated with the report from the Filters section of the Select Parameters page in the Report wizard. Select the None option from the Select View Name drop-down list if you do not want a specific view to be associated with the report. About Enterprise Vault 9.0 support With NetBackup 7.0.1, the NetBackup Enterprise Vault agent supports Enterprise Vault 7.5, 8.0, and 9.0 configurations. The following lists describe the NetBackup Enterprise Vault 9.0 enhancements and the Enterprise Vault clustering enhancements. The following enhancements are made in Enterprise Vault 9.0: Enterprise Vault partitions can use an EV Streamer API for storage, such as, partitions using Caringo Castor. NetBackup Enterprise Vault agent does not back up these partitions. This enhancement affects the following directives:

19 New Features About NBSU support for NetBackup If the open partition of the vault store uses the EV Streamer API for storage, backup with the EV_OPEN_PARTITION=Vault Store name directive completes with partial success. Only the Vault store database is backed up. In this case, it is recommended to use EV_VAULT_STORE_DB= Vault store name directive. The Closed partitions that use EV Streamer API for storage are not protected with EV_CLOSED_PARTITIONS=Vault Store name directive. If all closed partitions in the vault store use EV streamer API for storage, then backup with EV_CLOSED_PARTITIONS=Vault Store name directive fails. The Ready partitions that use EV Streamer API for storage are not protected with EV_READY_PARTITIONS= Vault Store name directive. If all ready partitions in the vault store use EV streamer API for storage, then backup with EV_READY_PARTITIONS= Vault Store name directive fails. For Enterprise Vault 9.0, quiescence succeeds even if the Enterprise Vault component (Vault store or Index location) or its parent component is already quiesced. To upgrade from Enterprise Vault 8.0 to Enterprise Vault 9.0, you don't need to make any modifications in the policy. The following Enterprise Vault clustering enhancements were made: With NetBackup 7.0, the NetBackup Enterprise Vault agent supports VCS When Enterprise Vault is clustered, and you want to configure NetBackup Enterprise Vault agent, make sure that the virtual cluster name on each node is the same as the NetBackup client name. About NBSU support for NetBackup This release of NetBackup (7.0.1) includes an updated version of the NBSU utility. The version number for this utility is version 1.4. In this release of NetBackup the NBSU 1.4 utility contains support for IPv6 network addressing and it has been ported to the zlinux platform. In addition, this release contains a fix for the Mac OS X platforms. About NBCC and NBCCR enhancements This release of NetBackup contains updated versions of the NBCC, NBCCH, and NBCCR utilities to the NetBackup version level.

20 20 New Features About NetBackup Snapshot Client NBCC was updated to ensure that it properly collects the EMM server hostnames on a clustered EMM server that does not have media servers on the same system. In addition, NBCC contains a change to ensure that it detects the exit status from the bpimagelist command. That produces a more consistent interpretation of the images in the Image Catalog. About NetBackup Snapshot Client With this release of NetBackup 7.0.1, the NetBackup Snapshot Client offers the following new enhancements: Support for Solution Enabler 7.0 and 7.1 versions is added. The EMC_Timefinder_* FIMS (snapshot methods) are supported with the VxFS+VxVM stack on Solaris. About VMware vsphere 4.1 NetBackup adds support for VMware vsphere 4.1. vsphere 4.1 brings many new features and performance enhancements to VMware environments. For a description of vsphere 4.1, see the following: About NetBackup documentation updates Many books within the NetBackup documentation set have been updated for this release. The following list shows a list of those books and the URL to where they are posted on the Symantec Support Web site: Symantec NetBackup Troubleshooting Guide Symantec NetBackup Commands Guide Symantec OpsCenter Administrator s Guide Symantec NetBackup Clustered Master Server Administrator s Guide Symantec NetBackup in Highly Available Environments Administrator s Guide Symantec NetBackup for SAP Administrator s Guide for Windows

21 New Features About NetBackup documentation updates 21 Symantec NetBackup for SAP Administrator s Guide for UNIX Symantec NetBackup for Microsoft Exchange Administrator s Guide for Windows Symantec NetBackup for Microsoft SharePoint Server Administrator s Guide for Windows Symantec NetBackup Deduplication Guide Symantec NetBackup Administrator s Guide for Windows, Volume I Symantec NetBackup Administrator s Guide for UNIX and Linux, Volume I Symantec NetBackup for NDMP Administrator s Guide Symantec NetBackup Security and Encryption Guide Symantec NetBackup LiveUpdate Guide Symantec NetBackup Release Notes

22 22 New Features About NetBackup documentation updates

23 Chapter 2 Supported Platforms This chapter includes the following topics: About NetBackup supported platforms About NetBackup platform proliferation support NetBackup binary sizes About NetBackup supported platforms This release of NetBackup supports all of the platforms that the NetBackup 7 product supports in addition to the new platforms that were added to this release. To see the supported platform information that was released with NetBackup 7, see the following Technote on the Symantec Support Web site. See About NetBackup platform proliferation support on page 23. About NetBackup platform proliferation support Changes to the following list can occur before the final release of NetBackup For the most current supported platform information, see the following Technote on the Symantec Support Web site: This release adds support for the following platforms: Added the following BMR platform proliferation support: BMR Client AIX 6.1 x64 BMR Client SLES10 x64

24 24 Supported Platforms About NetBackup platform proliferation support BMR Client SLES11 x64 BMR Client support for Windows 2008 x32 and x64/2008 R2 x64 BMR Client support for Windows 7 x64 and Windows Vista x64 BMR client support for Solaris 10 x64 BMR client support for HP-UX 11 v3 (11.31) IA-64 BMRsupport for Oracle Enterprise Linux (Red Hat 4 x64 and Red Hat 5 x64 with Oracle support) Added OpsCenter AIX 6.1 support. Added SQL Server W2008R2 support. Added SQL Server W2008R2 support. Added SharePoint 2010 on Windows 2008 SP2 and 2008 R2 Added Exchange 2010 SP1 support. Added Z-Linux Oracle 10gR2/NetBackup Basic Client on RedHat 5 and SLES 10 support. Added Z-Linux Media Server support on RedHat5 and SLES 10. Added EV9 support on Windows 2003 and 2008, 32- and 64-bit operating systems. Added NBSU utility support was added in preparation for NetBackup releases. The version levels of NBCC, NBCCH, and NBCCR utilities are now Added VxFI-based EMC Symmetrix Frozen Image Methods (FIMs) on HP-UX support. Added an NDMP and a PDDE stream handler with NetBackup Added a device qualification test suite for OST. Added support for VMware vsphere 4.1. The following VCS support: VCS support on HP-UX IA64 with Master VCS 5.0 MP3 support on Red Hat Enterprise Linux 4 x64 with Master VCS 5.0 MP3 support on Solaris 10 SPARC with Master VCS 5.1 support on Solaris 10 SPARC with Master VCS 5.1 support on Windows Server 2003 x64 with Master

25 Supported Platforms NetBackup binary sizes 25 VCS 5.1 SP1 AP1 support on Windows Server 2008 x64 with Microsoft Exchange Agent (Exchange 2010 support) VCS 5.1 SP1 support on Windows Server 2008 R2 x64 with Master Added snapshot support for HP-XP arrays for the following platforms: HP-UX IA64 RHEL 4.0 SUSE 11.0 Oracle Solaris Sparc 10.0 Windows 2008 x64 Added HP_XP_BusinessCopy and HP_XP_Snapshot are the new Frozen Image Methods (FIMs). Added HP_XP_BusinessCopy is used for taking mirror-based snapshots and HP_XP_Snapshot is used for taking COW-based snapshots. Added HP_XP array and Hitachi array are almost the same. In NetBackup also, Hitachi_ShadowImage FIM is equivalent to HP_XP_BusinessCopy and Hitachi_CopyOnWrite is equivalent to HP_XP_Snapshot. Therefore, for the configuration and prerequisites, all the steps applicable to Hitachi array are also applicable to the HP_XP arrays. For these steps, please refer to the Snapshot Client Administrator's Guide. These steps are similar to the Hitachi array configuration steps. NetBackup binary sizes The information in this section helps you determine if your NetBackup environment has the proper amount of disk space allocated to your servers to safely and efficiently back up and restore all of the data. Table 2-1 shows the approximate binary size of the NetBackup master and media server software, and the NetBackup client software requirements for each platform and operating system that is compatible with NetBackup. Table 2-1 NetBackp binary sizes for compatible platforms OS/Version CPU Architecture 32-bit client 64-bit client 32-bit server 64-bit server Notes AIX 5.3 POWER 928MB 3083MB 64-bit binary compatible. AIX 6.1 POWER 928MB 3083MB 64-bit binary compatible.

26 26 Supported Platforms NetBackup binary sizes Table 2-1 NetBackp binary sizes for compatible platforms (continued) OS/Version CPU Architecture 32-bit client 64-bit client 32-bit server 64-bit server Notes Asianux 2.0, 3.0 x64 510MB 1726MB Canonical Ubuntu 8.0 x64 510MB CentOS 5.2, 5.3 x64 510MB Debian GNU/Linux 4.0, 5.0 x64 510MB FreeBSD 6.1, 6.2, 6.3, 7.x x86 16MB HP-UX PA-RISC 632MB 1666MB 64-bit binary compatible. Media server or client compatibility only. HP-UX PA-RISC 632MB 1666MB 64-bit binary compatible. Media server or client compatibility only. HP-UX PA-RISC 632MB 1666MB 64-bit binary compatible. Media server or client compatibility only. HP-UX IA64 922MB 3012MB Mac OS X 10.5 Mac OS X 10.5, 10.6 POWER x86 22MB 22MB Novell Open Enterprise Server 2 x64 492MB 1662MB OpenVMS 5.5 OpenVMS 6.2 OpenVMS 7.3 HP VAX HP VAX HP VAX 16MB 16MB 16MB OpenVMS 6.1 OpenVMS 6.2 OpenVMS 7.3 OpenVMS 8.2 OpenVMS 8.3 HP Alpha HP Alpha HP Alpha HP Alpha HP Alpha 16MB 16MB 16MB 16MB 16MB

27 Supported Platforms NetBackup binary sizes 27 Table 2-1 NetBackp binary sizes for compatible platforms (continued) OS/Version CPU Architecture 32-bit client 64-bit client 32-bit server 64-bit server Notes OpenVMS 8.2 HP IA64 16MB OpenVMS 8.3 HP IA64 16MB OpenVMS 8.3-1H1 HP IA64/Alpha 16MB Oracle Enterprise Linux 4.0 x MB 1726MB 64-bit binary compatible. Oracle Enterprise Linux 5.0 x MB 1726MB 64-bit binary compatible. Red Flag Linux 5.0 x MB 1726MB Red Hat Enterprise Linux 4.0 (AS) x MB 1726MB 64-bit binary compatible. Red Hat Enterprise Linux 5.0 (base) x MB 1726MB 64-bit binary compatible. Red Hat Enterprise Linux 4.0 (AS) IA MB Compatible with client only. Red Hat Enterprise Linux 5.0 (base) IA MB Compatible with client only. Red Hat Enterprise Linux 4.0 (AS) POWER 96MB Red Hat Enterprise Linux 5.0 (base) POWER 96MB Red Hat Enterprise Linux 4.0 (AS) z/architecture 12MB Red Hat Enterprise Linux 5.0 (base) z/architecture 12MB Red Hat Enterprise Linux Desktop 4.0 x64 510MB 1726MB 64-bit binary compatible. Red Hat Enterprise Linux Desktop 5.0 x64 510MB 64-bit binary compatible.

28 28 Supported Platforms NetBackup binary sizes Table 2-1 NetBackp binary sizes for compatible platforms (continued) OS/Version CPU Architecture 32-bit client 64-bit client 32-bit server 64-bit server Notes Red Hat Enterprise Linux 5.0 (Advanced) x64 510MB 1726MB Solaris 9.0 SPARC 525MB 64-bit binary compatible. Solaris 10.0 SPARC 639MB 2050MB 64-bit binary compatible. Solaris 10.0 x64 439MB 1915MB 64-bit binary compatible. SUSE Linux Enterprise Server 10 (SP1) IA64 345MB Compatible with client only. SUSE Linux Enterprise Server 10 (SP1) x64 492MB 1662MB SUSE Linux Enterprise Server 10 (SP1) POWER 101MB Compatible with client only. SUSE Linux Enterprise Server 10 (SP1) z/architecture 12MB Compatible with client only. SUSE Linux Enterprise Server 11 IA64 345MB Compatible with client only. SUSE Linux Enterprise Server 11 x64 492MB 1662MB SUSE Linux Enterprise Server 11 z/architecture 12MB Compatible with client only. Windows x86 600MB 1700MB Covers all compatible Windows x86 platforms Windows x64 700MB 1900MB Covers all compatible Windows x64 platforms Windows IA64 600MB Compatible with client only.

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

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

31 Product Dependencies Operating system patches and updates 31 Table 3-1 Operating system patches and updates for NetBackup (continued) Operating System Type and Version Patch Notes HP-UX PA-RISC Networking.NET2-RUN: /usr/lib/libipv6.1 Networking.NET-RUN: /usr/lib/libipv6.sl For HP-UX PA-RISC platforms, this fileset is required: Networking.NET-RUN-64: /usr/lib/pa20_64/libipv6.1 Networking.NET-RUN-64: /usr/lib/pa20_64/libipv6.sl For HP-UX PA-RISC platforms, this fileset is required: For HP-UX PA-RISC platforms, this fileset is required: HP-UX Networking.NET2-RUN: /usr/lib/libipv6.1 PHSS_35385 PHSS_32226 PHSS_37516 PHSS_26946 PHSS_27740 PHSS_26560 For HP-UX PA-RISC platforms, this fileset is required: This patch is required for JAVA 6.0. This patch is a LIBCL patch. Contains fixes for the following: QXCR : purifyplus dumps core in PA32 QXCR : dld crash in LL_new_descendent_list when the acc application is exiting. QXCR : dld crash in LL_new_descendent_list when the acc application is exiting. QXCR : dlsym() hangs QXCR : dld emits assert messages for chatr +mem_check enabled 64-bit executables This patch is necessary to enable any C++ runtime code to work properly. This patch is a libc cumulative patch. This patch contains a linker tools cumulative patch.

32 32 Product Dependencies Operating system patches and updates Table 3-1 Operating system patches and updates for NetBackup (continued) Operating System Type and Version HP-UX Patch PHSS_32864 PHKL_26233 PHSS_35379 PHCO_29029 PHSS_24045 PHSS_30970 PHCO_35743 PHSS_37201 Notes That is a recommended critical patch from HP that is required for successful NetBackup client backups. This patch enables HP-UX mmap() to use large files from 2GB to 4GB. That is a recommended critical patch from HP that is required for successful NetBackup client backups. That is a recommended critical patch from HP that is required for NetBackup to use VxSS. Allow POLL_INTERVAL to be set to zero in /var/stm/config/tools/ monitor/dm_stape.cfg. That disables the dm_stape monitor within the Event Monitoring System. Symantec recommends that you upgrade to IPR0109. This patch can cause problems with the programs that have the setuid bit set. Hewlett-Packard s IT resource center Web site contains information about this patch. www1.itrc.hp.com S700_ libc cumulative patch The above patch has dependency on the following patches: PHCO_31923 (critical patch): s700_ libc cumulative header file patch PHKL_34805 : 700_ JFS3.3 patch; mmap This patch is required for JAVA 6.0.

33 Product Dependencies Operating system patches and updates 33 Table 3-1 Operating system patches and updates for NetBackup (continued) Operating System Type and Version HP-UX SUSE Linux Enterprise Server 10 x64 Solaris 9 SPARC 64-bit client Patch PHCO_33431 PHSS_34858 PHKL_31500 PHSS_37492 PHSS_37202 SUSE Linux Enterprise Server 10 update (or greater) Notes Symantec recommends that all customers running install this patch. That is a recommended critical patch from HP that is required so that dlopen works properly. That is a recommended critical patch from HP that NetBackup requires, particularly when you attempt to run NetBackup with NetBackup Access Control (NBAC). Contains fixes for the following: QXCR : purifyplus dumps core in PA32 QXCR : dld crash in LL_new_descendent_list when the acc application is exiting. QXCR : dlsym() hangs QXCR : dld emits assert messages for chatr +mem_check enabled 64-bit executables This patch is required for JAVA 6.0. The operating system version must be SUSE Linux Enterprise Server 10 update 2 or greater to run NetBackup 7.0. Change Request ID (or greater) Patch: (or greater)

34 34 Product Dependencies Operating system patches and updates Table 3-1 Operating system patches and updates for NetBackup (continued) Operating System Type and Version Solaris 10 SPARC 64-bit (server and client) Solaris 10 x64 Windows XP x86-32 Windows XP x86-64 Windows Vista x86-32 Windows Vista x86-64 Windows Server 2003 IA64 (SP1 & SP2) Windows Server 2003 x86-32 (SP1 & SP2) Patch Patch: (or greater) update 4 (08/07) and newer KB KB KB KB KB KB KB KB KB Notes Change Request ID The server is supported on update 4 (08/07) and newer. Change Request ID Change Request ID Change Request ID Change Request ID Microsoft microcode reliability update. Hotfix for hangs of connection attempts via PBX. Microsoft microcode reliability update. Contains the necessary updates to ensure that you can back up encrypted files. Microsoft microcode reliability update. Contains the necessary updates to ensure that you can back up encrypted files. Contains the necessary updates to run Volume Shadow Copy. Hotfix for hangs of connection attempts via PBX. Microsoft Storport Hotfix.

35 Product Dependencies Operating system patches and updates 35 Table 3-1 Operating system patches and updates for NetBackup (continued) Operating System Type and Version Windows Server 2003 x86-64 (SP1 & SP2) Windows Server 2008 x86-32 Windows Server 2008 x86-64 Windows Server 2008 IA64 Patch KB KB KB KB KB KB KB KB KB Notes Contains the necessary updates to run Volume Shadow Copy. Microsoft microcode reliability update. Microsoft Storport Hotfix. Contains the necessary updates to run Volume Shadow Copy. Hotfix for hangs of connection attempts via PBX. Microsoft microcode reliability update. Contains the necessary updates to ensure that you can back up encrypted files. Contains the necessary updates to ensure that you can back up encrypted files. Contains the necessary updates to ensure that you can back up encrypted files. The following additional product dependency information applies to this release of NetBackup: Product dependency notification for customers running Microsoft Windows Vista or Windows 2008 server. If you want to protect client (or server) systems that are running either Microsoft Windows Vista or Windows 2008 server, you may need to install Microsoft hotfix number KB If you attempt to back up any protected files that have been encrypted by the operating system, NetBackup cannot back up these files. NetBackup reports that it is unable to access the encrypted files and the backup continues with all of the remaining files.

36 36 Product Dependencies Operating system patches and updates Note: That does not apply to NetBackup encryption. NetBackup encryption is separate from the file system encryption, meaning that NetBackup-encrypted files are backed up. In addition, this hotfix is not needed for any Windows version before Microsoft Windows Vista or Windows 2008 server. If you are running Vista or Server 2008, please refer to KB to see if this hotfix is required for your operating system version

37 Chapter 4 Operational Notes and Issues This chapter includes the following topics: About NetBackup known issues About documentation issues About General NetBackup issues About NetBackup installation and upgrade issues About Bare Metal Restore (BMR) issues About NetBackup database agents About NetBackup Deduplication About NetBackup Snapshot Client issues About NetBackup Hyper-V issues About NetBackup NDMP issues About NetBackup OpsCenter issues About NetBackup Vault issues About NetBackup VMware issues About NetBackup known issues This section contains the new operational notes and known issues that pertain to the NetBackup release. And because NetBackup is an enhanced

38 38 Operational Notes and Issues About documentation issues progression of NetBackup 7.0 GA, you may want to refer to the NetBackup 7.0 Release Notes for additional information. The NetBackup 7.0 Release Notes and NetBackup Additional Operational Notes documents are available on the Symantec Support Web site. These documents contain general information about the NetBackup 7.0 GA release. See, NetBackup 7.0 Release Notes for UNIX, Windows, Linux on the Symantec Support Web site. See, NetBackup 7.0 Additional Operational Notes on the Symantec Support Web site. In addition to this release, there are hotfixes that are already available for some of the known issues described in this chapter. Please visit the NetBackup Late Breaking News page for the latest updates on known issues and to download hotfixes that are currently posted to address the those issues. See, About documentation issues The following items describe known issues or changes to the NetBackup documentation for this release: Multiple changes have been made to the NetBackup OpsCenter Administrator's Guide and this document has been released again with this release. Included in the many changes are instruction on how to install or upgrade to this version of OpsCenter. See the following Technote on the Symantec Support Web site. The NetBackup Snapshot Client 7.0 Administrator s Guide states the FlashSnap support incorrectly. The following statement describes the FlashSnap support in Snapshot Client appropriately: FlashSnap supports VxVM full-sized instant snapshots, but not space-optimized snapshot. Additionally, FlashSnap supports VxVM volumes in a shared disk group. For support configurations, please refer to the Snapshot Client Support Matrix. Page 90 of the Symantec NetBackup 7.0 Release Notes states the following: Enhancements have been made that enables a nonroot NBU_Admin or Vault operator to perform the tasks that they otherwise would not be able to perform because of permission problems. These enhancements specifically target a

39 Operational Notes and Issues About documentation issues 39 system where NBAC is configured and the Vault service manages the important read-write data. For example, these enhancements have the following effect on users who have upgraded from previous versions to NetBackup 7.0: "If pre-netbackup 7.0 sessions are not processed completely before an upgrade, Symantec recommends that you process all these sessions (meaning that you complete all ejects and reports) before you upgrade. At a minimum, you should copy the summary.log from the sidxxx directory to a new sidxxx/logs directory to accommodate the eject and reports eligible sessions." And so on... These enhancements apply to a NetBackup Vault 7.0 system irrespective of whether NBAC is configured or not. The effects that are listed apply to both NBAC and non-nbac systems. Page 90 of the Symantec NetBackup 7.0 Release Notes states the following: "If you upgrade to NetBackup 7.0 and decide to downgrade to a pre-netbackup 7.0 version, you must make sure that you account for the enhancements that were packaged in NetBackup 7.0. For example, log files are written to sidxxx/logs, and files and folders have restrictive permissions when they are created." This statement is not applicable as downgrading or rolling back from NetBackup 7.0 to a previous version is not supported. The NetBackup Administrator s Guide, Volume I should list additional files in the procedure about moving the NetBackup database. In Moving the NetBackup database from one host to another, the file list in steps 5, 10, and 12 should include the following files: NBDB.db, NBDB.log, EMM_INDEX.db, EMM_DATA.db, DBM_DATA.db, DBM_INDEX.db, DARS_DATA.db, DARS_INDEX.db (ET ) The NetBackup Administrator s Guide, Volume I contains a note in the sections that describe how to perform a full database validation: To perform a full database validation, shut down NetBackup and start only the database service. Although this note appears in the NetBackup documentation, it is not included in the online help for the NetBackup Database Administration utility. The NetBackup Administrator s Guide, Volume I incorrectly refers to the bprd service as the NetBackup Request Manager. The name for bprd is now the NetBackup Request Daemon. The following statement in the NetBackup 7.0 Enterprise Vault Agent administrator's Guide is not valid and should be ignored.

40 40 Operational Notes and Issues About General NetBackup issues "NetBackup 7.0 does not support the Enterprise Vault agent on an Enterprise Vault 8.0 server in an Enterprise Vault cluster configuration." The NetBackup 7.0.x Enterprise Vault agent does support both MSCS and VCS clustered environments of Enterprise Vault (except for the following exception). Enterprise Vault 7.5 is not supported in VCS clustered environment. The following line in the NetBackup High Availability Administrator's Guide is incorrect. "Verify that you have the NetBackup Enterprise Server installation program and a valid license key. You must also have a valid license key for the NetBackup OpenStorage option, if you perform backups to tape." The line should read as follows: "Verify that you have the NetBackup Enterprise Server installation program and a valid license key. You must also have a valid license key for the NetBackup SharedStorage option, if you perform backups to tape." About General NetBackup issues The following list contains known issues that apply to NetBackup: (ET ) When you configure backup selections in a policy, a scheduling problem can occur with the use of the UNSET_ALL directive. If the UNSET_ALL directive appears alone between NEW_STREAM directives, that can cause a schedule to run too frequently. The following is an example of a problematic directive list: NEW_STREAM UNSET_ALL NEW_STREAM File_1 NEW_STREAM File_2 NEW_STREAM File_3 HOST NAME CACHING NetBackup introduces the caching of host name to IP address mappings, which minimizes the delays encountered during repeated lookups for an name or address that cannot be resolved. Most NetBackup processes have an in-memory cache and all NetBackup processes on the same host also share a cache stored on the file system. The cache entries have a life span of one hour, for both successful and unsuccessful resolution attempts, to suppress the otherwise repeated lookups.