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™ Troubleshooting Guide
  3. Disaster recovery
  4. About clustered NetBackup server recovery for Windows
  5. Recovering the shared disk on a Windows VCS cluster
NetBackup™ Troubleshooting Guide

Recovering the shared disk on a Windows VCS cluster

The following procedure is applicable in situations where the configured cluster nodes remain available but the NetBackup catalog, database files, or both on the shared disk have been corrupted or lost.

Check the following conditions before you proceed with this procedure:

  • The shared storage hardware is restored to a working state, so that the shared disk resource can be brought online with an empty shared directory.

  • Valid online catalog backups exist.

To recover the shared disk on a Windows cluster that uses VCS

  1. Clear the faulted NetBackup resource group, disable monitoring, and bring up the shared disk and virtual name resources on a functioning node.
  2. Ensure that all NetBackup shared disks are assigned the same drive letters that were used when NetBackup was originally installed and configured.
  3. To reconfigure NetBackup for the cluster, initialize the database by running the following commands in sequence on the active node:
    bpclusterutil -ci
    tpext
    bpclusterutil -online
  4. Use the appropriate NetBackup catalog recovery procedure to restore the NetBackup catalog information on the shared disk.

  5. If the clustered NetBackup server is a media server, verify that the restored vm.conf file contains the correct host-specific MM_SERVER_NAME configuration entry for the active node. If MM_SERVER_NAME is different from the local host name, edit the file and change the server name to the local host name:

    MM_SERVER_NAME=<local host name>

  6. Use NetBackup to restore any data on the shared disks.
  7. Configure required devices and media and recover the NetBackup catalogs.
  8. Manually shut down and restart NetBackup on the active node.
  9. Re-enable monitoring of the NetBackup resource group.
  10. Verify that the NetBackup server can now be brought online on all configured nodes.

More Information

Recovering the primary server and Windows

Feedback

Was this page helpful?
Previous

Replacing a failed node on a Windows VCS cluster

Next

Recovering the entire Windows VCS cluster

Feedback

Was this page helpful?