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. Veritas NetBackup™ Bare Metal Restore™ Administrator's Guide
  3. Troubleshooting
  4. A restore task may remain in a finalized state in the disaster recovery domain even after the client restores successfully
  5. Communication between the master server and the client may fail even if the client has a valid host ID-based certificate
Veritas NetBackup™ Bare Metal Restore™ Administrator's Guide

Communication between the master server and the client may fail even if the client has a valid host ID-based certificate

This issue is observed primarily in the Dissimilar System Restore (DSR) on Windows platform.

This issue may occur due to a failure in the Network Settings during the cleanup operation in the first boot.

The issue may persist even after you have corrected or updated the Network Settings communication manually.

Workaround: To resolve this issue, perform the following steps:

  1. Navigate to the path on your target client system which has NetBackup installed.

    For Example:

    c:\program files\veritas\netbackup\bin
  2. Run the following command: nbcertcmd -getcrl

Feedback

Was this page helpful?
Previous

A restore task may remain in a finalized state in the disaster recovery domain even after the client restores successfully

Next

Automatic boot may fail for HP-UX after a restore

Feedback

Was this page helpful?