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. AIR import fails with status code 191 on target SpanFS cluster
Cohesity Data Cloud for NetBackup™ Administrator's Guide

AIR import fails with status code 191 on target SpanFS cluster

After configuring Auto Image Replication (AIR) between two SpanFS clusters, you may encounter a status code 191 during import operations at the target domain. It indicates that the disk pool and disk volume are not properly configured to recognize the replication source.

Cause:

The target domain may be missing replication metadata. If the following command shows disk volumes without a Replication Source field, it means the disk pool and disk volume need to be updated:

nbdevquery -listdv -stype SpanFS -U

Example output with the missing replication source:

Disk Pool Name             : dp
Disk Type                  : SpanFS
Disk Volume Name           : lsu4
...
Num Repl Sources           : 0
Replication Source         : [missing]

Resolution:

To resolve the issue, update both the disk volume and disk pool using the following steps:

  1. Identify the disk pool and disk volume names:

    nbdevquery -listdv -stype SpanFS -U

  2. Update the disk volume:

    nbdevconfig -updatedv -dv <disk_volume_name> -dp <disk_pool_name> -stype SpanFS

  3. Update the disk pool:

    nbdevconfig -updatedp -dp <disk_pool_name> -stype SpanFS

After these steps, run the nbdevquery command again to verify the update. You should now see the Replication Source field populated, indicating successful configuration.

Example updated output:

Disk Pool Name             : dp
Disk Volume Name           : lsu4
...
Num Repl Sources           : 1
Replication Source         : <source_cluster>:<volume_name>

Feedback

Was this page helpful?
Previous

The tpconfig utility cannot find SpanFS cluster

Next

The client direct backup fails with status code 50 due to client memory exhaustion

Feedback

Was this page helpful?