How to troubleshoot status 84 media write error while backing up NetBackup clients to PureDisk server via the PDDO plugin

How to troubleshoot status 84 media write error while backing up NetBackup clients to PureDisk server via the PDDO plugin

  • Article ID:100003494
  • Last Published:
  • Product(s):NetBackup

Problem

NetBackup clients failing with status 84 backing up to PDDO  storage server

Error Message

Status 84 media write error

Cause

When directing NetBackup clients to a PDDO storage server, the Status 84 media write error is most often caused by one or more of the following things.

  • This is a new installation of PDDO and the proper license keys have not been installed.
  • If this is not a new installation make sure the proper license keys have not expired.
  • Incorrect or missing server list entries.
  • Name and IP resolution problems between the Puredisk server and the NetBackup servers.
  • A pureDisk cleanup policy is running at the same time the backup tried to run.
  • The /Storage volume on the PureDisk server has filled past its water mark thresholds.  (/Storage has filled up).
  • Binary issues (check version of PureDisk and NetBackup to determine if fixes are available for install)

Solution

 

Below are some detailed steps on how to determine if the above situations are causing the Status 84 errors.

This is a new installation of PDDO and the proper license keys have not been installed.

Open the NetBackup Administration Console, Help, License Keys, Summary of active licensed features.  The following license keys must be installed on the NBU media server doing PDDO.  Be certain none have expired.

  • Flexible disk
  • PureDisk Option
  • Datastore Option

Incorrect or missing server list entries.

Review the NetBackup master server and media server's server list (bp.conf file on UNIX server and the Properties, SERVER tab on windows).  Be certain that the media server with the PDDO plugin is listed properly.

Name and IP resolution problems between the Puredisk server and the NetBackup servers.

PDDO is very dependent on network resolution.  Are there host files on both the NBU media / PDDO server and the PureDisk server with entries for both in each host file.

Example
PureDisk --- /etc/hosts
<ip address of PD server> <FQDN of PD server> <Shortname of PD server>
<ip address of NBU Media server> <FQDN of NBU media server> <Shortname of NBU Media server>
NetBackup -- Windows--  <install path\system32\drivers\etc\hosts -- Unix -- /etc/hosts
<ip address of NBU Media server> <FQDN of NBU media server> <Shortname of NBU Media server>
<ip address of PD server> <FQDN of PD server> <Shortname of PD server>

Check the following things on the PureDisk server which can cause the media write errors in NetBackup.

A pureDisk cleanup policy is running at the same time the backup tried to run.

1.  Log into the PureDisk Web User Interface and check to see if there are any PureDisk PDDO Data Removal, CR or MB garbage collection or CR Queue Processing jobs running at the time NetBackup was attempting the PDDO backup.  If this is the case the PDDO backup will exit with a status 84 because PureDisk will not allow any backups to be written to it when the database is being cleaned.

The CR Queue Processing jobs should never be cancelled and should be allowed to complete on its own.  The other 3 can be terminated gracefully.

2.  Check to see if there is data replicating from the Production PureDisk server to a DR PureDisk site at the time of a NBU PDDO backup. PureDisk again will not allow NetBackup to write to it during replications.

3.  If the above jobs were running on Puredisk, adjust the schedules of each so that they do not run during the NetBackup PDDO backups jobs.

4.  Check the status of the diskpool used by NetBackup for PDDO / PDDE backups.

<install path>\bin\admincmd\nbdevquery -liststs -U

If the diskpool "state" is down the <install path>\bin\admincmd/nbdevconfig -changestate -dp <PureDisk / MSDP poolname> -type PureDisk -state UP command can be used up UP the "state" of the diskpool.

Sample output

Storage Server      : nbu-media-name
Storage Server Type : PureDisk
Storage Type        : Formatted Disk, Network Attached
State               : DOWN

The /Storage volume on the PureDisk server has filled past its water mark thresholds.  (/Storage has filled up).

If the PureDisk server is running low on space in the /Storage location, the NetBackup PDDO jobs can also exit with a status 84.  If this is the situation then either add more disk space to /Storage or expire some older backup images then run the cleanup policies to free up space.

To check the available space on the PureDisk server using the following command:

/opt/pdcr/bin/crcontrol --dsstat 1

To do a detailed space usage analysis, see article https://www.veritas.com/support/en_US/article.000011025

Check the low space and very low space thresholds on the Puredisk server and adjust them if they are set too  high.

Binary issues (check version of PureDisk and NetBackup to determine if fixes are available for install)

Check the binary versions between NBU and PDDO server.

The NBU media / PDDO server was confirmed to be running version 6.5.0.2 while the PureDisk server is at version 6.5.1.

Logs of interest

1. NetBackup Media / PDDO server
Configure verbose 5 NetBackup media server bptm logging and ensure the media server's pdplugin <install_path>\NetBackup\bin\ost-plugins\pd.conf (or /usr/openv/lib/ost-plugins/pd.conf on UNIX/Linux) contains an uncommented line 'LOGLEVEL = 10' (without quotes) to provide verbose pdvfs logging within the NetBackup bptm log.

../Netbackup/logs/bptm
../Netbackup/logs/bpdm

Here is an article for the complete log listing for reference.
https://www.veritas.com/support/en_US/article.000006679

2.  Job details log showing error from the NetBackup Admin Console.

3.  Enable detailed logging on the NetBackup PDDO plugin media server.

Ensure no backups are running and enable pdplugin log at level 10. Use the procedure below:
Open /usr/openv/lib/ost-plugins/pd.conf
Uncomment the following lines:
DEBUGLOG = /var/log/puredisk/pdplugin.log (This path can be changed) 
LOGLEVEL = [0 - 10] 

4. PureDisk server log

Run the PDgetlogs.sh script and send in the output for review.  The script collects all of the support logs and puts them into a tar file for sending to Technical Services.

The script is located in the following location:
/opt/pdconfigure/scripts/support/PDgetlogs.sh
 

The output file is:  /tmp/PDgetlogs_

 

 

Applies To

NetBackup 6.5 or 7.0 master/media server(s)

NetBackup clients

Puredisk 6.5 or 6.6 SPA

PDDO is the plugin on a NetBackup media server that allows backups to be sent from NetBackup clients to an independent PureDisk server.  This is different from NetBackup clients sending backup data to a Media Server Deduplication (MSDP) storage server which does not involve an independent Puredisk server.
 

Was this content helpful?