STATUS CODE: 129 - Backups to disk storage units fail with a VERITAS NetBackup (tm) Status 129 because the storage unit is full.

Article:TECH44663  |  Created: 2007-01-04  |  Updated: 2013-08-23  |  Article URL http://www.symantec.com/docs/TECH44663
Article Type
Technical Solution


Environment

Issue



STATUS CODE: 129 - Backups to disk storage units fail with a VERITAS NetBackup (tm) Status 129 because the storage unit is full.


Error



<32> io_open_disk: storage unit /dsu01 is full
...
<32> io_open_disk: bp_sts_open_image failed: error 31
<2> bpdm: EXITING with status 129


Solution



Overview:
When using VERITAS NetBackup (tm) Enterprise Server, a backup to a disk storage unit will fail with a Status 129 when the disk storage unit is full.  This status code can occur for disk storage units (DSU) and disk staging storage units (DSSU).  

Troubleshooting:
The df -h command can be used to determine the available disk space for a disk storage unit.  On the media server where the disk storage resides, run the following command:
# df -h
Filesystem        size used avail capacity Mounted on
/dev/dsk/c0t0d0s0  28G  14G   13G    53%   /
/dev/dsk/c0t0d0s3 992M 990M    2M    99%   /dsu01
The above example from a Solaris 9 Media server shows a disk storage unit that is out of disk space for writing images.

Log Files:
The /usr/openv/netbackup/logs/bpdm/log.<date> file will show the following errors for the backup job:
<2> diskfull_corral: DSU IS FULL (0KB written)
<2> diskfull_corral: Released diskfull cleanup lock
<2> diskfull_corral: sleeping for 15 seconds due to disk full condition
<2> diskfull_corral: RETURNING
<16> hostname: STSBasicDisk: Caught exception in STSBasicDisk::CreateImage, FILE=STSBasicDiskImageInfo.cpp, FUNCTION=, LINE=249, ERROR=STS_ENOSPC
<32> io_open_disk: storage unit /dsu01 is full
...
<32> io_open_disk: bp_sts_open_image failed: error 31
<2> bpdm: EXITING with status 129

Resolution:
There are several methods that can be used to reclaim disk space on a disk storage unit.  Options such as, but not limited to, expiring older images, using an alternate storage unit, changing the retention level used and adding more disk space to the disk storage unit.

Expire older images from the disk storage unit to reclaim disk space on the file system.
 
1. Go to the Catalog section of the NetBackup Administration Console.
 
2. Select Pathname: and enter the disk path to the disk storage unit.
 
3. Enter the appropriate Date/Time Range for which to search for images to expire.
 
4. Click the Search Now button and a list of images in the disk storage unit will be displayed.
 
5. Select any backup id's that can be expired and then select Actions > Expire from the menu.
 
The highlighted backup id's will be expired and the disk space will be reclaimed on the file system.
 

 
Use a different disk storage unit for the backup.
 
1. Go to the Policies section of the NetBackup Administration Console.
 
2. Open the Attributes for the policy that failed with a Status 129.
 
3. Select a new storage unit from the "Policy storage unit:" drop down.
 
Once a new storage unit has been selected, manually run the backup or wait for the next scheduled backup to run.  The next backup of the policy will use a different storage unit.  The policy can be set to use the original storage unit, once disk space is available on the file system for the disk storage unit.

If the status 129 keeps reoccurring, select a smaller retention level for backups, or increase the size of the file system being used for the disk storage unit.
 

Supplemental Materials

Value129
Description

NetBackup Error 129: disk storage unit is full



Legacy ID



280005


Article URL http://www.symantec.com/docs/TECH44663


Terms of use for this information are found in Legal Notices