Important Update: Cohesity Products Documentation
All Cohesity product documentation are now managed via the Cohesity Docs Portal: https://docs.cohesity.com/HomePage/Content/home.htm. Some documentation available here may not reflect the latest information or may no longer be accessible.
NetBackup™ Release Notes
- About NetBackup 11.1.0.2
- New features, enhancements, and changes
- About new enhancements and changes in NetBackup
- NetBackup 11.1.0.2 new features, changes, and enhancements
- Changes in Cohesity terminology
- Update cloud configuration file on the primary and media server immediately after install or upgrade to NetBackup 11.1.0.2
- Several shutdown commands to be deprecated in a future release
- NetBackup 11.1.0.2 support additions and changes
- NetBackup 11.1 and earlier support additions and changes
- Support for malware scanning of hypervisor backups on OST targets
- Simplified Cloud Scale upgrade
- BMR now uses Windows ADK 10.1.22621 (ADK 2022)
- Operational notes
- About NetBackup 11.1.0.2 operational notes
- NetBackup installation and upgrade operational notes
- If NetBackup 11.1.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
- About support for HP-UX Itanium vPars SRP containers
- Change in the default path for NetBackup installation
- NetBackup administration interface operational notes
- NetBackup Bare Metal Restore operational notes
- After PIT restore, "The host ID does not exist" error appears
- NetBackup services may not start automatically after BMR restore on a Linux client
- NetBackup Bare Metal Restore on AWS hangs when restoring a Windows 2025 client
- Mirrored dynamic volume may not receive a drive letter after Windows BMR DDR restore
- BMR Restore Failure for ReFS Volumes on Windows (2016 - 2025)
- Post Bare Metal Restore (BMR) operation, windows Start Menu and Search not functioning
- NetBackup Cloud Object Store Workload operational notes
- Full backup after upgrading from a version prior to NetBackup 11.1
- Supported version of RHEL media server as backup host
- Auto Image Replication (AIR) from NetBackup version 11.1.0.2 requires NetBackup 10.2 or later
- Backup jobs become unresponsive and consume significant space on the temporary staging location.
- NetBackup NAS operational notes
- NetBackup Cloud workload operational notes
- NetBackup internationalization and localization 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
NetBackup servers must use a host name that is compliant with RFC 1123 and RFC 952
Starting with NetBackup 8.0, all NetBackup server names must use a host name that is complaint with RFC 1123 ("Requirements for Internet Hosts - Application and Support") and RFC 952 ("DOD Internet Host Table Specification") standards. These standards include the supported and unsupported characters that can be used in a host name. For example, the underscore character ( _ ) is not a supported character for host names.
More information is available about these standards and about this issue:
http://www.veritas.com/docs/000125019
These standards should be applied to all computing hosts, including all NetBackup hosts. To accommodate legacy environments and functionality, features of NetBackup that were implemented before 2010 continue to allow some non-compliant characters. But newer features, as well as more recently integrated 3rd-party components, are not tested with nor expected to be compatible with host names that do not adhere to the industry standards.
In some situations, it may be possible to configure name services with a network hostname alias that is standards-compliant, and then use the alias when you configure NetBackup. But using host names that are standards-compliant is the only way to ensure compatibility with all features.