BUG REPORT: After an update of the OpenStorage (OST) plug-in to version 2.2.1.1, NetBackup may report status code 129 and EMM status: Insufficient disk space or High Water Mark would be exceeded Disk storage unit is full(129)

Problem

BUG REPORT: After an update of the OpenStorage (OST) plug-in, NetBackup may report status code 129 and "EMM status: Insufficient disk space or High Water Mark would be exceeded Disk storage unit is full(129)" more frequently due to a change in the method of calculation of free space on the storage unit.

Error Message

NBU status: 129, EMM status: Insufficient disk space or High Water Mark would be exceeded Disk storage unit is full(129)

Solution

Bug: 2085594

Detail/Symptom(s):
After applying version 2.x.x.x or higher of the Data Domain OST (OpenStorage) plug-in, a higher amount of used space may be reported on the storage unit due to changes in data collection and communication between NetBackup and the plug-in.   It may also apply to other vendor OST plug-in as well.

Log Files:
Messages similar to the following may be seen in the Activity Monitor:
Error nbjm(pid=10112) NBU status: 129, EMM status: Insufficient disk space or High Water Mark would be exceeded Disk storage unit is full(129)

Note: The nbjm pid will vary per master server.

Workarounds:
1. Increase the storage unit's High Water Mark (HWM).
2. Downgrade the OST plug-in to version 1.1.4.2.

ETA of Fix:

Note: If this issue is experienced, Symantec Corporation recommends upgrading to the latest version.

NetBackup 7.1 has a fix that can be enabled with the following implementation:

The new behavior must be enabled on a per storage server type basis by creating a touch file on each media and master server. The touch file is named REPLACE_LOGICAL_WITH_PHYSICAL_CAPACITY.<stype> where "<stype>" represents a specific storage server type.  Only when the touch file exists will the logical values be replaced by the physical values (physical values remain unmodified) for the specific storage server type. Create the touch file in the directory where the storage  server plugin is installed.

Unix example:
/usr/openv/lib/ost-plugins/REPLACE_LOGICAL_WITH_PHYSICAL_CAPACITY.DataDomain

Windows example:
C:\Program Files\Veritas\Netbackup\bin\ost-plugins\REPLACE_LOGICAL_WITH_PHYSICAL_CAPACITY.DataDomain

In these examples, the storage server type <stype> is "DataDomain." To determine the <stype> of a storage server, execute the admincmd nbdevquery to list the storage servers:

nbdevquery -liststs -U

In the output of that command, the Storage Server Type field is the <stype>. Note: the string is case sensitive.

Hotfixes for 6.5.6 and 7.0.1 are no longer available - please upgrade NetBackup to a version containing a resolution for this issue. 

Symantec has acknowledged that the above-mentioned issue (Etrack 2085594) is present in the current version(s) of the product(s) mentioned at the end of this article. Symantec is committed to product quality and satisfied customers.  The formal resolution for this issue is included in the following release:

  • NetBackup 7.5 GA

This release is now available.

 

 

Terms of use for this information are found in Legal Notices.

Search

Survey

Did this article answer your question or resolve your issue?

No
Yes

Did this article save you the trouble of contacting technical support?

No
Yes

How can we make this article more helpful?

Email Address (Optional)