NetBackup™ Release Notes
- About NetBackup 10.1.1
- New features, enhancements, and changes
- About new enhancements and changes in NetBackup
- NetBackup 10.1.1 new features, changes, and enhancements
- Changes in Veritas terminology
- Resilient backup jobs feature is now available
- Support for agentless recovery to switch to instant access
- Activity monitor improvements in the NetBackup web UI
- Additional NetBackup Flex Scale features in the Flex Scale web UI
- Limited types of job filters can be imported into NetBackup web UI
- RESTful APIs included in NetBackup 10.1.1
- NetBackup 10.1.1 support additions and changes
- End-of-life of Enhanced Auditing (EA) authorization model
- Bare Metal Restore (BMR) operating system support additions
- Additional policy types supported in the NetBackup web UI
- Support for Oracle Copilot with multiple universal shares
- Backup and restore of Kubernetes applications with file system volumes
- Several shutdown commands to be deprecated in a future release
- NetBackupIT Analytics Data Collector installed for NetBackup 10.1.1
- Update cloud configuration file on the primary server immediately after install or upgrade to NetBackup 10.1.1
- VMware backups support for file system optimizations with XFS file systems
- Operational notes
- About NetBackup 10.1.1 operational notes
- NetBackup installation and upgrade operational notes
- NetBackup administration and general operational notes
- NetBackup administration interface operational notes
- Delay in NetBackup web UI when adding or removing columns in Catalog area
- Job actions not available for workload administrators with limited RBAC permissions on assets
- Policy name link does not work for some failed jobs in the web UI Activity Monitor
- Backup Now does not support job restart
- 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 Snapshot Manager (formerly NetBackup CloudPoint)
- NetBackup for NDMP 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
- Policy schedule start time on the Horizon UI is different than configured in the policy
- 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.