NetBackup™ Release Notes
- About NetBackup 10.5.0.1
- New features, enhancements, and changes
- About new enhancements and changes in NetBackup
- NetBackup 10.5.0.1 new features, changes, and enhancements
- Changes in Veritas terminology
- Update cloud configuration file on the primary server immediately after install or upgrade to NetBackup 10.5.0.1
- Support for OpenStack Caracal added to NetBackup for OpenStack 10.5.0.1
- MSDP volume group (MVG) supports WORM storage
- Changes to the VRTSpddes.rpm package in 10.5.0.1 for BYO storage server
- Enhancements for Cassandra workload
- Support for backup of Azure Disk Encryption (ADE) enabled VMs
- Support for file hash search with malware search
- NetBackup 10.5.0.1 support additions and changes
- Minimum operating system versions
- Several shutdown commands to be deprecated in a future release
- Operational notes
- About NetBackup 10.5.0.1 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 for VMware 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
After PIT restore, "The host ID does not exist" error appears
After a point in time (PIT) restore operation (which may include either a Full File System restore or a BMR restore), the error message The host ID does not exist appears.
In this scenario, a full backup is taken when a SERVICE_USER as root/administrator account is configured. This account takes the backup of the NetBackup installed binaries with root/administrator ownership. Before a restore, SERVICE_USER is configured with an account other than root/administrator, and then an incremental backup is taken where the service user is backed up as part of bp.conf. In a PIT restore operation with the incremental backup, the SERVICE_USER entry gets restored. However, the binaries are restored in the root account ownership.
Workaround:
After changing the service user, you must take a full backup, whether it is a MS-Windows\Standard Policy for File System or BMR policy configuration.