NetBackup™ Release Notes
- About NetBackup 10.3
- New features, enhancements, and changes
- About new enhancements and changes in NetBackup
- NetBackup 10.3 new features, changes, and enhancements
- Changes in Veritas terminology
- RESTful APIs included in NetBackup 10.3
- Introducing universal share accelerator
- Restore logs in the NetBackup web UI and location of restore logs
- Restore types added to NetBackup web UI for MS-Windows, Standard, and VMware policy types
- Recovery for additional policy types added to the NetBackup web UI
- NetBackup web UI new policy features
- Enhancements in system anomaly detection
- Entropy computation in NetBackup
- About multi-person authorization
- About multi-factor authentication
- Certificate-based transport layer security (TLS) authentication
- NetBackup 10.3 support additions and changes
- Support for AWS Snowball Edge
- End of life (EOL) for the Enhanced Auditing feature in NetBackup
- End of life (EOL) for the NetBackup Access Control (NBAC) authorization model in NetBackup
- Protecting assets with Snapshot Manager's agentless restore feature will require Microsoft Windows Server 2019 or later
- NetBackup for OpenStack support for CentOS has ended
- Several shutdown commands to be deprecated in a future release
- License file required for upgrade
- Upgrades to NetBackup 10.3 may take a long time
- Before upgrade, default credentials category is NONE
- Data-in-transit encryption (DTE) mode is set to 'Preferred On' by default
- Update cloud configuration file on the primary server immediately after install or upgrade to NetBackup 10.3
- Additional permissions added for new features
- Integrate MSDP Cloud credentials into NetBackup generic Credential Management System
- MSDP Cloud is now supported on SUSE Linux Enterprise Server
- Cloud Catalyst to MSDP Cloud migration is not supported on 10.3 MSDP servers
- New features for NetBackup for Microsoft SQL Server
- New features for NetBackup for Oracle
- Upgrading to Snapshot Manager for Data Center 10.3 for Qumulo plug-in users
- New D-NAS features
- Operational notes
- About NetBackup 10.3 operational notes
- NetBackup installation and upgrade operational notes
- NetBackup administration and general operational notes
- NetBackup administration interface operational notes
- NetBackup Bare Metal Restore operational notes
- NetBackup Cloud Object Store Workload operational notes
- NetBackup Snapshot Manager (formerly NetBackup CloudPoint)
- NetBackup NAS operational notes
- NetBackup for OpenStack operational notes
- CentOS repository mirror URL is updated
- NetBackup for OpenStack Datamover API (NBOSDMAPI) service times out in the haproxy connection
- Instance volumes in the incremental backups cannot be mounted
- NetBackup primary server does not re-issue the token if NetBackup VM is a 3-node cluster
- Success message appears along with the error message when you delete the policy that has snapshots
- Unable to connect to NetBackup primary server using NBCA
- Excluded Ceph Volume after restore is not mountable or formattable
- Restored VMs have blank metadata config_drive attached
- NBOSVM reconfig fails when you add new NetBackup VM to the cluster
- Database does not sync after NetBackup cluster gets new nodes
- Data on boot disk gets backed up despite exclusion
- After reinitialization and import, OpenStack certificates are missing
- CLI import changes scheduler trust value to disabled
- Unable to get node details after you reinitialize the NetBackup Appliance
- Snapshots fails with "object is not subscriptable" for many policy jobs at the exact same time
- No operation is permitted in insecure way for SSL-enabled Keystone URL
- 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.