NetBackup™ Release Notes
- About NetBackup 10.2
- New features, enhancements, and changes
- NetBackup 10.2 new features, changes, and enhancements
- 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 Snapshot Manager (formerly NetBackup CloudPoint)
- NetBackup for NDMP operational notes
- NetBackup for OpenStack 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
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.