cancel
Showing results for 
Search instead for 
Did you mean: 

Error Code 129

NB_DD
Level 2

 Insufficient disk space or High Water Mark would be exceeded
Disk storage unit is full(129)

 

Please give a solution.

2 REPLIES 2

mph999
Level 6
Employee Accredited

You will need to give us much more information:

 

1.   Is this a DSSU  config ?  IF so, are the duplications working ?
2.   Which system(s) are involved? For example, Master Server, Media Server - Please provide system names
3.   What version of NetBackup are the servers running ?
4.   What type of operating system are the servers running, and what version (including patch and kernel level) 
5.   Please submit the support report from the master and any relevant Media Servers in the environment.
6.   Is this a reoccurring issue ?
7.  Please send in the contents of the details tab in the Activity Monitor for the job.
8.  What logs or screenshots are available?
9.  Has this worked previously?  If so, when was the last time it DID work?
10.  Have there been any environmental; system; or configuration changes?
11.  When did the problem begin?
12.  How often does the problem occur?
 
Thanks,
 
Martin

J_H_Is_gone
Level 6

all we can give you is the troubleshooting steps for the error

As NetBackup writes to the file system for the disk storage unit, runs out of space. Until more file system space is available, images of similar size or larger may fail with this error when written to this disk storage unit.
In a scheduled backup job that writes to a storage unit group (which contains this disk storage unit), the following occurs: the NetBackup scheduler requests the storage unit with the greatest available capacity when the job is retried.
For the retry, when the scheduler requests the storage unit with the greatest available capacity, note the following:
* A tape storage unit in the storage unit group has preference over any disk storage units since tape storage units usually have more capacity.
* If the storage unit with the most unused capacity is busy, NetBackup skips it. NetBackup then selects an available storage unit with the next largest, unused capacity.
* If the storage unit with the greatest unused capacity is the one that lacked capacity when the job first failed, the scheduler tries it again. That storage unit may have more unused capacity now than it did when the job failed.

 

Do the following, as appropriate:
* Either free sufficient space or add more space to the file system for this storage unit.
* Lower the high capacity mark for this disk storage unit. Configure the policies to access it through a storage unit group that provides alternative storage to use when this storage unit fills up. Ideally, if an image exceeds the file system's high capacity mark, it also completes successfully. This image leaves the storage unit in a "full" state (over the high capacity mark). The storage unit then is not assigned to other jobs until its capacity falls under its high capacity mark.
* If the Staging attribute is set on the disk storage unit that did not have enough capacity, it may be unable to create free space. It cannot create space because the backups that are staged to the disk are not relocated (eligible to be deleted from the staging storage unit). Ensure that staging's relocation (duplication) jobs successfully copy enough images to provide sufficient free space for new backups.