Veritas NetBackup™ Release Notes
- About NetBackup 8.1
- New features, enhancements, and changes
- About new enhancements and changes in NetBackup
- NetBackup 8.1 new features, changes, and enhancements
- About secure communications in NetBackup
- Host ID to host name mapping
- Catalog recovery with secure communications
- Communication between a NetBackup 8.1 master server and an OpsCenter 8.1 master server
- NetBackup requirements for inter-host communication
- Two-way trust for adding trusted master server for Targeted Auto Image Replication
- Secure communication between a NetBackup client in a demilitarized zone and a master server
- Introducing NetBackup CloudCatalyst to upload deduplicated data to the cloud
- Faster full backups for Isilon filers using NetBackup Accelerator
- Auto Image Replication (A.I.R.) import confirmation feature introduced to SLPs
- Accurate licensing feature and other updates with nbdeployutil
- NetBackup introduces a new BigData policy type
- End-of-life for multiple NetBackup products, features, and platforms
- NetBackup 8.1 support additions
- NetBackup BMR functionality not supported for restoring clients with NetBackup 8.1
- DHCP client support changes in NetBackup 8.1
- Support has ended for the SYMCquiesce utility for Linux virtual machines
- Several shutdown commands will be deprecated in a future release
- Localization support added for the csconfig command
- New minimum system requirements for NetBackup master servers
- Upgrade considerations regarding MSDP fingerprint algorithm changes
- NetBackup servers must use a host name that is compliant with RFC 1123 and RFC 952
- SCCM and Chef deployment tools and documentation now available
- Changes to media server and SSO device configuration procedures
- Update cloud configuration file on the master server immediately after install or upgrade to NetBackup 8.1
- Changes to Amazon cloud storage server object sizes
- Additional cloud-related enhancements
- New options to exclude disks from VMware backups
- Restore Virtual Machine Disks wizard for VMware
- Support for non-ASCII characters in VMware
- New requirements for clustered file systems, database clusters, and distributed database applications
- Configuring the Distributed Application Restore Mapping host properties
- Changes to policy and other configuration for SQL Server clusters and SQL Server AGs
- Registering authorized locations used by a NetBackup database script-based policy
- DB2 OPTIONS command update
- Late-breaking new status codes for NetBackup 8.1
- Operational notes
- About NetBackup 8.1 operational notes
- NetBackup installation and upgrade operational notes
- NetBackup administration and general operational notes
- NetBackup administration interface operational notes
- Memory requirements to run the NetBackup Administration Console
- Multiple versions of the NetBackup administration interface
- "Operation timed out" message appears when policies are accessed from the Remote Administration Console
- Using X forwarding to launch the NetBackup Administration Console can fail on certain Linux platforms
- Intermittent issues with X forwarding of NetBackup Administration Console
- Reduced functionality during the initialization of the NetBackup Administration Console
- NetBackup Administration Console may encounter a core dump issue when the Simplified Chinese UTF-8 locale is used on a Solaris SPARC 64-bit system with Solaris 10 Update 2 or later
- NetBackup Accelerator operational notes
- NetBackup Bare Metal Restore operational notes
- Shared Resource Tree (SRT) creation may fail using NetBackup 8.1 as the BMR boot server on AIX and HP-UX platforms with NetBackup 8.0 and earlier clients
- If the boot server has a base installation of Solaris 10 update 11, the creation of SRTs can fail
- Many services on Solaris 11 print warning messages during a system boot and during BMR first boot
- Solaris Zone recovery on Solaris 11 and newer takes time to reconfigure after a BMR restore during first boot
- A Solaris BMR restore operation fails if the text-installer package is not present in the customized AI ISO
- The /boot partition must be on a separate partition for a multiple device-based OS configuration
- Multiple error messages might be displayed during the first boot after the restoration of a client with ZFS storage pools
- BMR may not format or clear the ZFS metadata
- Specifying the short name of the client to protect with Auto Image Replication and BMR
- A restore task may remain in a finalized state in the disaster recovery domain even after the client restores successfully
- IPv6 support for BMR
- Automatic boot may fail for HP-UX after a restore
- Prepare to Restore may not work for a Solaris client
- NetBackup Cloud operational notes
- NetBackup cluster operational notes
- NetBackup database and application agent operational notes
- NetBackup for Exchange operational notes
- NetBackup for SharePoint operational notes
- SharePoint GRT restore can fail if the host names or IP addresses are not mapped with the host ID
- Granular restores skip versioned documents or files that are checked out
- Modified system files or ghosted files are not cataloged or restored during a site collection restore
- Restored wiki pages may not be correct
- NetBackup for Oracle operational notes
- NetBackup deduplication operational notes
- NetBackup internationalization and localization operational notes
- NetBackup for NDMP operational notes
- NetBackup virtualization operational notes
- NetBackup for VMware operational notes
- The VM's swap files are not excluded from the backup if a volume on the VM contains multiple swap files
- Using the NetBackup appliance to install the NetBackup plug-in for VMware vSphere Web Client
- VMware block-level incremental backups expire when the previous full backup expires
- A VM restore to a vCenter fails when NetBackup has credentials for a restore ESX server
- NetBackup for VMware operational notes
- Appendix A. About SORT for NetBackup Users
- Appendix B. NetBackup installation requirements
- Appendix C. NetBackup compatibility requirements
- Appendix D. Other NetBackup documentation and related documents
New requirements for clustered file systems, database clusters, and distributed database applications
For a file system or database that is clustered or for database applications that are distributed, NetBackup 8.1 requires that you review the auto-discovered mappings in Host Management. For NetBackup for SQL Server, this requirement also applies to availability groups (AGs). On the Mappings for Approval tab, approve each valid mapping that NetBackup discovered in your environment. This configuration ensures that the hosts in the cluster are recognized as secure hosts and can communicate with the master server. If you only install the NetBackup client on one node in the cluster, then this configuration is not required. Perform this configuration in the Host Management properties on the master server. See the NetBackup Security and Encryption Guide for more information.
The Exchange, SharePoint, and SQL Server agents may require that you configure host information in the Distributed Application Restore Mapping host property on the master server.
When you upgrade your master server to NetBackup 8.1, security requirements now exist that may affect your previous configurations for backups and restores of complex workloads including Exchange Server, SharePoint Server, and SQL Server. For example, a complex workload includes the following:
Exchange DAGs
Exchange clusters
SharePoint Server
SharePoint Server with a clustered back-end SQL Server
SQL Server clusters
SQL Server availability groups (AGs)
SQL Server AGs with a failover cluster instance (FCI)
Veritas recommends that you first attempt your database workload backups with your current configuration. If backups do not succeed, then configure the Distributed Application Restore Mapping host property on the master server. If restores do not succeed, configuring the Distributed Application Restore Mapping should also resolve these issues.
Note that if you chose to configure the Distributed Application Restore Mapping for SQL Server highly available environments, certain previous configuration steps are no longer needed. In this case, the SQL Server agent no longer requires a second policy that contains the cluster or AG node names. For a SQL Server cluster or AG, you also do not need to configure permissions for redirected restores for the cluster or AG nodes.
For new installations of NetBackup 8.1, follow the instructions for your agent in the agent's administrators guide. You must configure the mappings for distributed application restores. You must also review the auto-discovered mappings for the hosts in your environment.