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. Cohesity Data Cloud for NetBackup™ Administrator's Guide
  3. Troubleshooting
  4. Troubleshooting missing subnet whitelist for SpanFS access
Cohesity Data Cloud for NetBackup™ Administrator's Guide

Troubleshooting missing subnet whitelist for SpanFS access

NetBackup needs network access to the SpanFS file system for Direct-IO operations. If the required IP subnet isn't added to the SpanFS subnet whitelist, SpanFS rejects the RPC requests, causing backups to fail.

Issue:

When the subnet whitelist is missing or incorrect, backups fail with status 83 and logs show errors such as:

image open failed: error 2060037: access not allowed

Resolution:

To resolve this issue, add the required subnet to the SpanFS whitelist.

iris_cli cluster add-subnet-to-whitelist subnet-ip=<IPv4 address> subnet-mask-ip4=<IPv4 subnet mask>

See Configuring SpanFS subnet whitelists for NetBackup access.

Feedback

Was this page helpful?
Previous

The client direct backup fails with status code 83: media open error

Next

Duplicate replication target volumes displayed in multi‑VLAN Direct-IO configurations

Feedback

Was this page helpful?