Search <book_title>...

Veritas NetBackup™ Deduplication Guide

Last Published: 2019-09-18

Product(s): NetBackup (8.1.2)

MSDP backup or duplication job fails

The following subsections describe some potential failures for backup or deduplication jobs and how to resolve them.

Disk volume is down

A message similar to the following appears in the job details:

Error 800: Disk Volume is Down

Examine the disk error logs to determine why the volume was marked DOWN.

If the storage server is busy with jobs, it may not respond to master server disk polling requests in a timely manner. A busy load balancing server also may cause this error. Consequently, the query times out and the master server marks the volume DOWN.

If the error occurs for an optimized duplication job: verify that source storage server is configured as a load balancing server for the target storage server. Also verify that the target storage server is configured as a load balancing server for the source storage server.

See Viewing MSDP disk errors and events.

Storage server is down or unavailable

Windows servers only.

A message similar to the following appears in the job details:

Error nbjm(pid=6384) NBU status: 2106, EMM status: Storage Server is down or unavailable Disk storage server is down(2106)

The NetBackup Deduplication Manager (spad.exe) and the NetBackup Deduplication Engine (spoold.exe) have different shared memory configuration values. This problem can occur when you use a command to change the shared memory value of only one of these two components.

To resolve the issue, specify the following shared memory value in the configuration file:

SharedMemoryEnabled=1

Then, restart both components. Do not change the values of the other two shared memory parameters.

The SharedMemoryEnabled parameter is stored in the following file:

storage_path\etc\puredisk\agent.cfg

Backup job: System error occurred (174)

A message similar to the following appears in the job details:

media manager - system error occurred (174)

If the job details also include errors similar to the following, it indicates that an image clean-up job failed:

Critical bpdm (pid=610364) sts_delete_image
 failed: error 2060018 file not found
Critical bpdm (pid=610364) image delete
 failed: error 2060018: file not found

This error occurs if a deduplication backup job fails after the job writes part of the backup to the Media Server Deduplication Pool. NetBackup starts an image cleanup job, but that job fails because the data necessary to complete the image clean-up was not written to the Media Server Deduplication Pool.

Deduplication queue processing cleans up the image objects, so you do not need to take corrective action. However, examine the job logs and the deduplication logs to determine why the backup job failed.

See About MSDP queue processing.

See NetBackup MSDP log files.

Failure to open storage path or to prepare CRQP transaction

Error messages similar to the following appear in one of the NetBackup Deduplication Engine (spoold) log files.

RefDBEngine::write_prepare fail to open /storage_path/databases/refdb/prepare/64.ref.prepare

RefDBManager::write_prepare fail to prepare CRQP transaction for refdb 64

See NetBackup MSDP log files.

This error occurs if the /storage_path/databases/refdb/prepare directory is deleted.

To fix this problem, do one of the following:

Create the missing directory manually.
Restart the NetBackup Deduplication Engine (spoold). First ensure that no backups are running on the storage unit on that media server.

Note:

RefDBEngine and refdb do not refer to nor are they related to the open source RefDB reference database and bibliography tool.