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™ Administrator's Guide, Volume II
  3. Reference topics
  4. How NetBackup reserves drives
  5. About the SPC-2 SCSI reserve process
  6. About SCSI reservation conflicts
Veritas NetBackup™ Administrator's Guide, Volume II

About SCSI reservation conflicts

The NetBackup Automatic Volume Recognition process (avrd) manages access to tape devices. A properly configured NetBackup environment and properly configured tape devices should not receive a reservation conflict message from a tape drive. When avrd starts, it issues an SPC-2 SCSI release to all configured, nondisabled tape drive paths that are currently in the Up state. The command releases all devices that were SPC-2 reserved at the time of a system restart or crash. The SCSI release command returns tape devices to general availability after a system crash.

If the avrd process receives a reservation conflict message, it changes the status of the device to PEND. It also writes the following message in the system log:

Reservation Conflict status from DRIVENAME (device NUMBER)

Also, the NetBackup Administration Console Device Monitor or the output from the vmoprcmd command shows PEND in the Control column.

If a conflict occurs, a reservation problem can exist. If the HBA that reserves the drive is unavailable (for example, due to a system crash or hardware failure), it cannot release the reservation. NetBackup cannot release or break an SPC-2 SCSI reservation automatically. Force a release or break the reservation to make the drive available, even for a failover server in a cluster environment.

When the conflict is resolved, the following message is written to the log:

Reservation Conflict status cleared from DRIVENAME (device NUMBER)

Feedback

Was this page helpful?
Previous

About SPC-2 SCSI reserve commands

Next

About forcing a release of an unavailable HBA's SPC-2 reservation

Feedback

Was this page helpful?