Forum Discussion

nbustarter380's avatar
10 years ago

Netbackup code 155 occurring on an AIX client

Hello, We  have one Backup client that’s getting the code 155 disk full error   NetBackup status code: 155 Message: disk is full Explanation: The write to the catalog file failed beca...
  • RiaanBadenhorst's avatar
    10 years ago

    Hi Guys,

     

    This issue is usually seen on clients when the track log (when using accelerator) has filled up the / file system.

     

    Please show us the output of df -h

  • Jaime_Vazquez's avatar
    10 years ago

    Verify the date/time stamps of the Disk Full messages against jobs run on the NBU Master.

    Check the core files created on the client.  Delete them after you have found their cause.  Core files can get rather large.  They are created in the same directory as the executable that failed.

    Verify what your settings are for debug logs being created on the client.  The default is to keep them for 28 days, which is too large a value. This is especially true if the VERBOSE or DebugLevel configured for them is set too high. I tend to use a value of 4, a span of time sufficient to look at problems found over a long weekend. The files are written to the /usr/openv/logs or /usr/openv/netbackup/logs directories. It is possible they are taking an inordinate amount of space. Run this command to see how much space each directory/sub-directory is using:

    du -m /usr

    This should get space values, in MB, for /usr and for each sub-directory of /usr.  Use the "-s" option for file level results.