NetBackup™ Release Notes
- About NetBackup 10.5
- New features, enhancements, and changes
- About new enhancements and changes in NetBackup
- NetBackup 10.5 new features, changes, and enhancements
- Changes in Veritas terminology
- RESTful APIs included in NetBackup 10.5
- Updates to the nbdb2adutl command
- Changes to the dashboard in the NetBackup web UI
- New features for NetBackup for VMware in the NetBackup web UI
- New features for NetBackup for DB2
- New features and changes for NetBackup for Microsoft SQL Server
- Managing policies for cloud assets
- Cloud Scale and decoupling of Cloud Scale
- Search files using a file hash in NetBackup
- Support for tape as a media option for Kubernetes workloads using Kubernetes policies
- NetBackup 10.5 support additions and changes
- Minimum operating system versions
- Several shutdown commands to be deprecated in a future release
- Multi-person authorization support for encryption key management and API key operations
- BMR support for Cloud VM Recovery in AWS
- Support for TLS 1.3 protocol
- Support for Nutanix Cloud Clusters (NC2) with Microsoft Azure and Amazon Web Services (AWS)
- Support for viewing hash values of malware infected files and malware
- Support of disk type Premium SSD v2 for NetBackup Snapshot Manager Microsoft Azure plug-in
- Support of SSL/TLS for Proxy Service
- Support for double encryption method in Azure
- Support for regional endpoint in Amazon Web Services
- End of life (EOL) for NetBackup for OpenStack - PSF
- MSDP volume group support
- Support for Cloud-Object-Store workload type for malware scanning
- Support for cross-cloud provider restore
- Client push staging area no longer populated
- About binaries installed on primary and media servers
- Update cloud configuration file on the primary server immediately after install or upgrade to NetBackup 10.5
- NetBackup protection for Oracle Cloud Infrastructure (OCI)
- Private key encryption support
- About security configuration risk
- Changes to NetBackup guide titles
- Operational notes
- About NetBackup 10.5 operational notes
- NetBackup installation and upgrade operational notes
- NetBackup administration and general operational notes
- NetBackup administration interface operational notes
- NetBackup Cloud Object Store Workload operational notes
- NetBackup Snapshot Manager (formerly NetBackup CloudPoint)
- NetBackup database and application agent operational notes
- NetBackup NAS operational notes
- NetBackup for OpenStack operational notes
- NetBackup for OpenStack Datamover API (NBOSDMAPI) service times out in the haproxy connection
- Instance volumes in the incremental backups cannot be mounted
- Restored VMs have blank metadata config_drive attached
- No operation is permitted in insecure way for SSL-enabled Keystone URL
- NBOS Backups and NBOS Backup Admin tabs disappear from Horizon UI after stack is updated
- 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.