cancel
Showing results for 
Search instead for 
Did you mean: 

status 155 on veritas netbackup ver. 5.1

oland
Not applicable
Hi everyone,

I just wanted to ask about the status 155 "dsk is full" in veritas netbackup. It explains there that the write to the catalog file failed bec. the disk containing the catalog database is full. I am using solaris ver. 5.8. I actually check the disk by using the df -k. I found out that the /opt directory has already 94% capacity. Is this /opt directory has something to do with the error. What shall I do? Plase help.....
3 REPLIES 3

Taqadus_Rehman
Level 6

When the root file system runs out of disk space, it can cause the NetBackup daemons to hang. It will be necessary to stop the daemons and remove logs or other files to reclaim space on the disk. Other applications that run on the system may also be affected.

1. Stop all the NetBackup daemons. This will cancel any queued jobs in the activity monitor:

# /usr/openv/netbackup/bin/goodies/netbackup stop

2. Reclaim disk space on the root file system.

a. The vxlogmgr command can be used to delete older unified log files. This is one possible reason the system can run out of disk space. The following command will delete any log file that is older than 24 hours. If this command fails to remove any logs, then it is also possible to delete individual files from the
/usr/openv/logs directory since the NetBackup daemons have been stopped.

# cd /usr/openv/netbackup/bin

# ./vxlogmgr --del -t 24:00:00

b. NetBackup legacy logging still creates log files in the /usr/openv/netbackup/logs/<process> directory. Check these directories and remove any unneeded log files.

c. Check the system logs and other applications on the system and remove any unneeded files to reclaim space

3. Verify how much disk space is now available on the root file system:

# df -h

Filesystem size used avail capacity Mounted on

/dev/dsk/c0t0d0s0 28G 7.5G 20G 28% /

4. To help prevent this situation from occurring again, lower the logging level for any future backups by issuing the following command. This will set the logging level to one.
To reduce the logging level for unified logging:

# cd /usr/openv/netbackup/bin

# ./vxlogcfg -a -p NB -o Default -s "DebugLevel=1" -s "DiagnosticLevel=1"

To reduce the logging level for legacy logging edit the bp.conf and change the verbose level to

"VERBOSE = 1"

The bpconfig command can also be used to control how many days worth of logs are kept. By default, NetBackup will keep 28 days worth of logs. The following command will reduce this to only five days for both unified and legacy logging:

# ./bpconfig -kl 5

5. Once disk space has been reclaimed, it is recommended to restart the system. Other system processes and applications may have also encountered problems when the system ran out of disk space. A restart of the system will help verify that everything on the system will come up properly after a reboot.

scorpy_582
Level 6
Hi,

When you install netbackup on solaris, it actually gets installed on /opt filesystem.
/usr/openv is just a softlink.

There are many reasons that can account for disk full.

Two big factors in netbackup that consule a lot of space are logs and images.

logs are in /usr/openv/netbackup/logs
and images are in /usr/openv/netbackup/db/images

You can disable the logging as suggested by Taqadus. Unified logging will not be applicable to you since you are in 5.x environment. All the logs of your master server will be located at /usr/openv/netbackup/logs and verbosity will be controlled by "VERBOSE =" entry in the bp.conf

For images, please refer the Admin Guide Vol. 2 which will give you a simple math to forecast the size of your images. It mainly depends on number of clients, frequency of backups and retention level.

Things that you can do:
Either grow the /opt filesystem.
Move the images to a seperate filesystem and create a soft link at original location (not the best idea, but a possible one)
Redirect the images to another location. For this, create the following file : /usr/openv/netbackup/db/images/<client>/altpath
Populate this file with the new location catalog.

hope this helps.

Andy_Welburn
Level 6
DOCUMENTATION: The filesystem that NetBackup resides on has filled to 100% capacity, what steps can ...


Possible data loss during a catalog backup, with the ALTPATH file in place


[ In our environment we went for 'option 1' many moons ago with no issues - we actually moved the images to one new filesystem & the logs (now including unified logs as we are at 6.5.1) to yet another new filesystem some time later]