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™ Deduplication Guide
  3. Troubleshooting
  4. Troubleshooting Cloud Catalyst issues
  5. Troubleshooting restarting ESFS after the Cloud Catalyst storage server is down
Veritas NetBackup™ Deduplication Guide

Troubleshooting restarting ESFS after the Cloud Catalyst storage server is down

If the Cloud Catalyst storage server goes down abnormally, ESFS (vxesfsd) may not restart when NetBackup is restarted.

To allow vxesfsd to start, check the following location to see if a rocksdb.log file was created:

/cache/fsdb/log

Remove the rocksdb.log file and restart the NetBackup services.

Feedback

Was this page helpful?
Previous

Media write error (84) if due to a full local cache directory

Next

Restarting the vxesfsd process

Feedback

Was this page helpful?