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)" more frequently due to a change in the method of calculation of free space on the storage unit.
| Article:TECH135174 | | | Created: 2010-01-13 | | | Updated: 2011-05-18 | | | Article URL http://www.symantec.com/docs/TECH135174 |
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
NBU status: 129, EMM status: Insufficient disk space or High Water Mark would be exceeded Disk storage unit is full(129)
Solution
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.
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.
http://www.symantec.com/docs/TECH147404
Downloadable Fix: NB_6.5.6_ET2085566_1.zip is a NetBackup 6.5.6 Hotfix for NetBackup Servers using OS
http://www.symantec.com/docs/TECH147402
Please be sure to refer back to this document periodically as any changes to the status of the issue will be reflected here. A link to the patch or hotfix download will be added to this document when it becomes available. Please note that Symantec reserves the right to remove any fix from the targeted release if it does not pass quality assurance tests. Symantec's plans are subject to change and any action taken by you based on the above information or your reliance upon the above information is made at your own risk.
|
|
| Source | Error Code |
| Value | 129 |
| Description | Disk storage unit is full |
| Source | ETrack |
| Value | 2085594 |
| Description | Error 129, EMM status: Insufficient disk space or High Water Mark would be exceeded with OST plug-in 2.2.1.1 |
Legacy ID
357524
Article URL http://www.symantec.com/docs/TECH135174
Terms of use for this information are found in Legal Notices
Thank you.