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 MSDP operational issues
  5. MSDP media open error (83)
Veritas NetBackup™ Deduplication Guide

MSDP media open error (83)

The media open error (83) message is a generic error for the duplication. The error appears in the NetBackup Administration Console Activity Monitor.

Often, the NetBackup Deduplication Engine (spoold) or the NetBackup Deduplication Manager (spad) were too busy to respond to the deduplication process in a timely manner. External factors may cause the Deduplication Engine or the Deduplication Manager to be unresponsive. Were they temporarily busy (such as queue processing in progress)? Do too many jobs run concurrently?

See About MSDP performance.

Usually but not always the NetBackup bpdm log provides additional information about status 83.

The following subsections describe use cases that generated an error 83.

SQL Server client-side backups fail

Client-side backups of a SQL Server database may fail in the following circumstances:

  • The Both IPv4 and IPv6 option is enabled for the master server, the media server that hosts the NetBackup Deduplication Engine, and the client. The Both IPv4 and IPv6 option is configured in the Network Settings host properties.

  • The IPv6 network is configured as a preferred network for the master server, the media server that hosts the NetBackup Deduplication Engine, and the client. The preferred network Match (Above network will be preferred for communication) property also is enabled. Preferred networks are configured in the Preferred Networks host properties.

  • The IPv6 network is chosen for the backup.

Examine the bpbrm log file for an error similar to the following:

probe_ost_plugin: sts_get_server_prop_byname failed: error 2060057

If the error message appears, the NetBackup host name cache may not contain the correct host name mapping information. The cache may be out of sync if DNS changes in your network environment were not fully propagated throughout your environment. It takes some amount of time for DNS changes to propagate throughout a network environment.

To resolve the problem, do the following on the NetBackup master server and on the MSDP storage server:

  1. Stop the NetBackup services.

  2. Run the following command:

    UNIX: /usr/openv/netbackup/bin/bpclntcmd -clearhostcache

    Windows: install_path\NetBackup\bin\bpclntcmd.exe -clearhostcache

  3. Start the NetBackup services.

For more information about client deduplication logging, see the description of "Client deduplication proxy plug-in" in the "MSDP log files" topic.

See NetBackup MSDP log files.

Restore or duplication fails

The media open error (83) message appears in the NetBackup Administration Console Activity Monitor.

Table: Case sensitivity error messages describes other messages that may appear.

Table: Case sensitivity error messages

Operation

Activity Monitor job details

Status in bpdm and bptm log files

Restore

Image open failed: error 2060018: file not found

sts_open_image failed: error 2060018

Duplication (MSDP source)

Image open failed: error 2060018: file not found

sts_open_image failed: error 2060018

Replication (MSDP source)

get image properties failed: error 2060013: no more entries

rpl_add_image_set: rpl_get_image_info() failed, error 2060013

Duplication (NetBackup 5000 series appliance source)

Image open failed: error 2060018: file not found

sts_open_image failed: error 2060018

Replication (NetBackup 5000 series appliance source)

get image properties failed: error 2060013: no more entries

rpl_add_image_set: rpl_get_image_info() failed, error 2060013

The messages may indicate a client name case sensitivity issue in your MSDP environment. For a description of the problem and the procedures to resolve it, see the following Veritas tech note:

http://www.veritas.com/docs/TECH207194

Feedback

Was this page helpful?
Previous

Cannot delete an MSDP disk pool

Next

MSDP media write error (84)

Feedback

Was this page helpful?