Forum Discussion

sagar666's avatar
sagar666
Level 5
8 years ago

root file system full

Hi,

Root file systems i need to clean up. Most of the files are located below /usr/openv/netback has 90%.

I noticed below files are more than 2GB and shall i delete them ?

/usr/openv/netbackup/db/images/inbmaster.asicdesigners.com/1477000000/catstore/hw_home_1477060200_FULL.f_imgRecord0
/usr/openv/netbackup/db/images/inbmaster.asicdesigners.com/1462000000/catstore/hw_home_1462985420_FULL.f_imgRecord0
/usr/openv/netbackup/db/images/inbmaster.asicdesigners.com/1479000000/catstore/hw_home_1479479400_FULL.f_imgRecord0
/usr/openv/netbackup/db/images/inbmaster.asicdesigners.com/1469000000/catstore/hw_home_1469198101_FULL.f_imgRecord0
/usr/openv/netbackup/db/images/inbmaster.asicdesigners.com/1474000000/catstore/hw_home_1474641000_FULL.f_imgRecord0
/usr/openv/netbackup/db/images/inbmaster.asicdesigners.com/1454000000/catstore/hw_home_1454078158_FULL.f_imgRecord0
/usr/openv/netbackup/db/images/inbmaster.asicdesigners.com/1471000000/catstore/hw_home_1471931682_FULL.f_imgRecord0
/usr/openv/netbackup/db/images/inbmaster.asicdesigners.com/1451000000/catstore/hw_home_1451920898_FULL.f_imgRecord0
/usr/openv/netbackup/db/images/inbmaster.asicdesigners.com/1467000000/catstore/hw_home_1467008374_FULL.f_imgRecord0
/usr/openv/netbackup/db/images/inbmaster.asicdesigners.com/1456000000/catstore/hw_home_1456497343_FULL.f_imgRecord0
/usr/openv/netbackup/db/images/inbmaster.asicdesigners.com/1459000000/catstore/hw_home_1459521000_FULL.f_imgRecord0
/usr/openv/netbackup/db/images/inbmaster/1479000000/catstore/bheema_home1_1479572270_FULL.f_imgRecord0
/usr/openv/netbackup/db/images/inbmaster/1481000000/tmp/catstore/bheema_home1_1481694077_FULL.f_imgStrings0
/usr/openv/netbackup/db/images/inbmaster/1481000000/tmp/catstore/bheema_home1_1481694077_FULL.f_imgRecord0

Please advice.

  • I agree - NEVER delete anything in images folder. You won't be able to restore if you do that.
    Rather delete logs in ...openv/logs/*/* and openv/netbackup/logs/*/*

    Once you have cleaned up some space in logs, provide a separate disk for images and maybe logs too.
    You will find instructions in NBU Admin Guide I on how to move images to another filesystem.

    It is never a good idea to install NBU master server software in the root filesystem.
  • NBU should be installed in a seperate filesystem, not root, for this exact reason.

    Suggest:

    Stop NBU services

    Delete all files in :

    /usr/openv/netbackup/logs

    /usr/openv/logs

    ** Providing you don't want the old logs

    Hopefully this will give you a small amount of space

    You could then consider archiving the older part of the catalog, this will backup the .f files and then delete them.

    Long term, you need to add disk space.

10 Replies

  • No - do not delete anything!
    Call Veritas Support now.
  • I agree - NEVER delete anything in images folder. You won't be able to restore if you do that.
    Rather delete logs in ...openv/logs/*/* and openv/netbackup/logs/*/*

    Once you have cleaned up some space in logs, provide a separate disk for images and maybe logs too.
    You will find instructions in NBU Admin Guide I on how to move images to another filesystem.

    It is never a good idea to install NBU master server software in the root filesystem.
  • NBU should be installed in a seperate filesystem, not root, for this exact reason.

    Suggest:

    Stop NBU services

    Delete all files in :

    /usr/openv/netbackup/logs

    /usr/openv/logs

    ** Providing you don't want the old logs

    Hopefully this will give you a small amount of space

    You could then consider archiving the older part of the catalog, this will backup the .f files and then delete them.

    Long term, you need to add disk space.

    • Marianne's avatar
      Marianne
      Level 6

      Weird that sagar666 experienced this very serious issue 2 days ago but has not been back to look for answers... :smileysurprised:

      • mph999's avatar
        mph999
        Level 6

        May have not been working over weekend I suppose, or could have logged a call with us perhaps.

        May need suppoet as if the filesystem filled up rapidly, may have toasted the transaction log - it should shut down with 10% diskspace left, but if the filesystem fills up real quick it can still get corrupted.