Veritas NetBackup™ Release Notes
- About NetBackup 8.3.0.2
- New features, enhancements, and changes
- Operational notes
- About NetBackup 8.3.0.2 operational notes
- NetBackup installation and upgrade operational notes
- After initiating CA migration, connection errors may occur
- If NetBackup 8.3.0.2 upgrade fails on Windows, revert to previous log folder structure
- Native installation requirements
- NetBackup servers must use a host name that is compliant with RFC 1123 and RFC 952
- Do not install from the menu that appears when the installation DVD is inserted
- About support for HP-UX Itanium vPars SRP containers
- NetBackup administration and general operational notes
- The nbdeployutil utility may fail to generate usage reports for traditional licensing
- Child backup jobs may enter a queued state for workloads that use BigData policy
- Errors are shown in the jobs detail when NetBackup attempts to expire images from non-WORM capable storage
- NetBackup web server certificate renewal failure during initiation of NetBackup CA migration or upgrade
- Microsoft Azure backup fails if the resource group name contains a period (.)
- SLP does not retry multistreaming backup if child job fails or is canceled
- Granular restores require adequate available space on target
- Stale devices shown on the device tree
- NetBackup administration interface operational notes
- Search limitations for security events lists in the NetBackup web UI
- Using X forwarding to launch the NetBackup Administration Console can fail on certain Linux platforms
- Intermittent issues with X forwarding of NetBackup Administration Console
- NetBackup Administration Console fails in Simplified Chinese UTF-8 locale on Solaris SPARC 64-bit systems with Solaris 10 Update 2 or later
- NetBackup Bare Metal Restore operational notes
- NetBackup Cloud operational notes
- NetBackup with Veritas CloudPoint operational notes
- On-host agent may be unavailable after restore with a snapshot taken with NetBackup CloudPoint 8.3
- Application status of original instances may report errors for host-consistent restores to alternate locations
- Public cloud not supported with gov cloud or China region
- Indexing not supported on instances created from AWS Marketplaces AMIs
- Consistent host snapshot might fail
- Image clean-up may fail for Microsoft Azure workloads
- Configuring AWS plug-in with IAM role showed that the Authentication Method field is blank
- MongoDB create snapshot job may freeze
- Updating a cloud plug-in while a job runs causes job failure
- Permission denied error occurs if both user and password are updated
- Different source and target zones for Google Cloud Platform are not supported
- Broken files system detected
- NetBackup deduplication operational notes
- NetBackup for NDMP operational notes
- NetBackup internationalization and localization operational notes
- NetBackup Snapshot Client operational notes
- NetBackup virtualization 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
About compatibility between NetBackup versions
You can run mixed versions of NetBackup between primary servers, media servers, and clients. This back-level support lets you upgrade NetBackup one server at a time, which minimizes the effect on overall system performance.
Veritas supports only certain combinations of servers and clients. In mixed version environments, certain computers must be the highest version. Specifically, the version order is: OpsCenter server, primary server, media server, and then clients. For example, the scenario that is shown is supported: 9.0 OpsCenter server > 8.3.0.1 primary server > 8.3 media server > 8.0 client.
All NetBackup versions are four digits long. The NetBackup 9.0 release is the 9.0.0.0 release. Likewise, the NetBackup 8.3 release is the NetBackup 8.3.0.0 release. For the purposes of supportability, the fourth digit is ignored. An 8.3 primary server supports an 8.3.0.1 media server. Likewise, an 8.3.0.1 primary supports an 8.3 OpsCenter server. An example of what is not supported is an 8.3 OpsCenter server with a 9.0 primary server.
The NetBackup catalog resides on the primary server. Therefore, the primary server is considered to be the client for a catalog backup. If your NetBackup configuration includes a media server, it must use the same NetBackup version as the primary server to perform a catalog backup.
For complete information about compatibility between NetBackup versions, refer to the Veritas SORT website.
Veritas recommends that you review the End of Support Life information available online.