Ransomware attackers specifically target and attempt to destroy backup systems to increase the probability of payment. Hardening your system is critical. Please ensure you have reviewed your platform security using the Security Hardening Checklist
Cohesity

COHESITY Documentation

Explore our documentation to get started, discover products & new features, access troubleshooting guides, register sources, platforms support.

Products
Data Security Alliance
Visit Cohesity.com
Demos
Support
Blogs
Developers
Partner Portals
Cohesity Community
© 2026 Cohesity, Inc. All Rights Reserved.
Terms of Use|
Privacy Policy|
Legal|
  1. Home
  2. NetBackup™ Release Notes
  3. Operational notes
  4. NetBackup Bare Metal Restore operational notes
  5. After PIT restore, "The host ID does not exist" error appears
NetBackup™ Release Notes

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 hostID 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.

Feedback

Was this page helpful?
Previous

NetBackup Bare Metal Restore operational notes

Next

NetBackup services may not start automatically after BMR restore on a Linux client

Feedback

Was this page helpful?